Adding an NFS Share Client

Prerequisites

• You have obtained required data for configuring an NFS share.
• You have configured a DNS server or configured storage and service planes and added them to an LDAP or NIS domain if you need to add a client whose Type is Host. For details, see Configuring a DNS Server or Configuring an LDAP Domain and Configuring an NIS Domain.
• You have created a network group name available on the LDAP or NIS server if you need to add a client whose Type is Network group.
• You have refreshed the cache of all storage nodes if you need to add a client whose Type is Network group. To refresh cache, run the following command:

  nas_proto_auth -c update-namesrv-cache -s source{0:Local 1:DNS 2:AD 3:LDAP 4:NIS} -t type{0:Host 1:Netgroup 2:UnixUser 3:UnixGroup} [-z tenantid] [-a clear all{0:False 1:True}]

  Example: nas_proto_auth -c update-namesrv-cache -s 3 -t 1 -z 0 -a 1

Procedure

1. Choose Resources > Resources > Share > NFS Share.
2. Select the desired account from the Account drop-down list from the upper left corner.
3. Click More on the right of the desired NFS share and select Add Client.

   The Add Client page is displayed.

   

   You can also click the path of the desired NFS share. On the page that is displayed, click Add in the Permission area.

4. Set client properties.

   Table 1 describes related parameters.

   Table 1 Client parameters

   Parameter	Description
   Type	Indicates the client type of the NFS share. NOTE: When a client is included in multiple share permissions, the priority of share authentication from high to low is in the following sequence: host name > IP address > network segment > wildcard > network group > *.
   Name or IP Address	When Type is set to Host, enter client host names (FQDNs are recommended), IP addresses, or IP address segments, or use the asterisk (*) to represent IP addresses of all clients. When Type is set to Network group, enter the network group names configured in the LDAP or NIS domain. NOTE: You can enter multiple host names, IP addresses, or network group names separated by semicolons (;), spaces, or carriage returns. A host name: Contains 1 to 255 letters, including letters, digits, hyphens (-), periods (.), and underscores (_). Must start with a letter or digit and cannot end with a hyphen (-) or underscore (_). Cannot contain a combination of a period and underscore (_. or ._), a combination of a period and hyphen (-. or .-), consecutive periods (..), or pure digits. For IP addresses: You can enter client IP addresses, client IP address segments, or an asterisk (*) to represent IP addresses of all clients. IPv4 addresses, IPv6 addresses, or the combination of IPv4 and IPv6 addresses are supported. The mask of an IPv4 address ranges from 1 to 32. The prefix of an IPv6 address ranges from 1 to 128. A network group name: Contains 1 to 254 characters. The value can contain only letters, digits, underscores (_), periods (.), and hyphens (-).
   UNIX Permission Level	Indicates the permission level for the UNIX client to access the NFS share. Includes: Read-only: The client can only read files in the NFS share. Read/Write: The client can read and write files in the NFS share. None: No operation is allowed on the NFS share.
   Kerberos5 Permission	Indicates the permission level for the Kerberos5 client to access the NFS share. Includes: Read-only: The client can only read files in the NFS share. Read/Write: The client can read and write files in the NFS share. None: No operation is allowed on the NFS share. This parameter applies only to the scenario where the NFS Kerberos service is configured.
   Kerberos5i Permission	Indicates the permission level for the Kerberos5i client to access the NFS share. Includes: Read-only: The client can only read files in the NFS share. Read/Write: The client can read and write files in the NFS share. None: No operation is allowed on the NFS share. This parameter applies only to the scenario where the NFS Kerberos service is configured.
   Kerberos5p Permission	Indicates the permission level for the Kerberos5p client to access the NFS share. Includes: Read-only: The client can only read files in the NFS share. Read/Write: The client can read and write files in the NFS share. None: No operation is allowed on the NFS share. This parameter applies only to the scenario where the NFS Kerberos service is configured.

5. Modify advanced client parameters. Click Advanced.
   Table 2 describes related parameters.

   Table 2 Advanced client parameters

   Parameter	Description
   Write Mode	Indicates how the system writes data onto disks. Synchronous: The system writes data onto disks instantly. Asynchronous: The system writes data to the cache first. The asynchronous write mode delivers higher write performance. However, if the client and a mount node fail at the same time, data may be lost. NOTE: This parameter is displayed only when at least one of UNIX Permission Level, Kerberos5 Permission, Kerberos5i Permission, and Kerberos5p Permission is set to Read/Write.
   Permission Constraint	Indicates whether to retain the user ID (UID) and group ID (GID) of a shared directory. all_squash: The UID and GID of a shared directory are mapped to user nobody, which is applicable to public directories. no_all_squash: retains the UID and GID of a shared directory.
   root Permission Constraint	Controls the root permission of the clients. root_squash: does not allow the clients to access the share as user root. Otherwise, the client will be mapped as an anonymous user. no_root_squash: allows the clients to access the share as user root that has full control and access permissions for shared directories. NOTE: If a VM needs to be created in the NFS share, select no_root_squash. Otherwise, the VM may run abnormally.
   Source Port Verification Constraint	Indicates whether to enable source port verification. secure: allows the clients to access the NFS share using ports 1 to 1023. insecure: allows the clients to access the NFS share using any port.

6. Click OK.