Create a NAS server for multiprotocol file sharing (SMB and NFS)
Prerequisites
Obtain the following information:
Networking information for the NAS server (IP interfaces, netmask, gateway, VLAN, and so on.)
VLAN ID, if the switch port supports VLAN tagging.
AD information, including the SMB system name (used to access SMB shares), and either the credentials of the domain administrator or of a user of the domain who has privileges for joining the AD. Optionally, you can specify the NetBIOS name and organizational unit. The NetBIOS name defaults to the first 15 characters of the SMB server name. The organizational unit defaults to CN=Computers.
UNIX Directory Service (UDS) information for NIS, LDAP, or other local files. The UDS provides the UNIX UID and GID for AD users.
NOTE:You can configure mappings for some users in the UDS and let the others be mapped through the default account, or use automatic mapping.
DNS server and domain information.
Protection policy (optional).
About this task
It is recommended to balance the number of NAS servers on both nodes.
In a multiprotocol configuration, it is recommended to join the SMB server to an Active Directory domain for resolving SIDs to and from Windows usernames. When connecting to a multiprotocol file system, domain users perform user mapping to create a mapping from the Windows SID to the UNIX UID and primary GID.
Standalone SMB servers only support local users (which are intended for SMB-only access and are not mapped), and would not have the necessary mappings for a proper multiprotocol configuration.
Because the UID of the local user on the file system is unlikely to match the UID configured on the UNIX client, the two UIDs are seen as two different users from the point of view of the NAS server. As a result, the same user has inconsistent permissions across different protocols.
You can use one of the following workarounds:
Manually configure UIDs to ensure that they are consistent with the local SMB server - Create all the local users on an SMB server, determine the UIDs of the local users, and then configure the UNIX clients to use those UIDs.
If security is not a concern, you can use open permissions.
If the files are accessible to everyone, then it is not required to maintain consistent permissions across protocols.
Steps
Select
Storage > NAS Servers.
On the
NAS Servers tab, click
Create.
On the
Details
page, specify the NAS server name, network interface, IP address, subnet mask, and VLAN ID.
Select
Next to open the
Sharing Protocol
page.
On the
Select Sharing Protocol
page, select
SMB and
NFSv3 and/or
NFSv4, and select
Next.
On the
Windows Server Settings
tab, in the Windows Server Type field, select
Join to the Active Directory Domain and fill the required AD information.
Optionally, select
Advanced to change the default NetBIOS name and organizational unit. Select
Save and then select
Next.
On the
UNIX Directory Services
tab, configure one of the following directory services:
Local files
NIS
LDAP
Local files and NIS or LDAP
Optionally, select
Secure NFS and then switch the
Secure NFS Settings to enable secure NFS.
On the
DNS page, select
Enable DNS Server option, and provide the following information:
DNS Transport Protocol - UDP (default), TCP
Domain
IP address of the DNS servers
On the
Protection Policy page, optionally select a protection policy for the NAS server.
Select
Finish to create the NAS server.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\