UNSOLVED

itsmeluck

updated

10 years ago

I

itsmeluck

2 Posts

0

1977

July 3rd, 2016 20:00

Data domain share restrictions

Hi Everyone,

Good day, I just want to ask if we can still replace the restrictions of the NAS share we have with our data domain dd4200. It was initially configured to be accessible by all because it was set as with "*" as users. Can I still make the shares to be accessible by a list pf users and not by all? Thanks.

  • itsmeluck

    2 Posts

    1303

    0

    Posted July 3rd, 2016 23:00

    When the dd was initially configured the people who configured it set it to * now everyone is able to access it. Can we still change that and how? Thanks

  • gautamgp

    1 Rookie

    •

    226 Posts

    1303

    1

    Posted July 3rd, 2016 23:00

    Yes it can be done. you can modify the shares as you want.

  • gautamgp

    1 Rookie

    •

    226 Posts

    1303

    0

    Posted July 4th, 2016 22:00

    Use the below command to make the changes.

    nfs add path client-list [(option-list)]

    Add NFS clients that can access the Data Domain system. A client can be a fully qualified

    domain hostname, class-C IP addresses, IP addresses with netmasks or length, an IPV6

    address, an NIS netgroup name with the prefix @, or an asterisk wildcard for the domain

    name, such as *.yourcompany.com. Role required: admin.

    An asterisk by itself means no restrictions. A client added to a subdirectory under /

    data/col1/backup has access only to that subdirectory.

    The options-list is comma or space separated, enclosed by parentheses. If no option is

    specified, the default options are rw, root_squash, no_all_squash, and secure.

    NFS Options

    ro

    Enable read-only permission.

    rw

    Enable read and write permissions (default value).

    root_squash

    Map requests from uid or gid 0 to the anonymous uid/gid.

    no_root_squash

    Turn off root squashing.

    Note

    no_root_squash is the default value.

    all_squash

    Map all user requests to the anonymous uid/gid.

    no_all_squash

    Turn off the mapping of all user requests to the anonymous uid/gid (default value).

    secure

    Require that requests originate on an Internet port that is less than

    IPPORT_RESERVED (1024) (default value).

    insecure

    Turn off the secure option.

    anonuid=id

    Set an explicit user ID for the anonymous account. The ID is an integer bounded from

    0 to 65635.

    anongid=id

    Set an explicit group ID for the anonymous account. The ID is an integer bounded

    from 0 to 65635.

    log

    The system will log NFS requests. This option may impact performance.