HYPER-UNIFIED STORAGE. Nexsan Unity

Transcription

1 HYPER-UNIFIED STORAGE Nexsan Unity NFS Interoperability NEXSAN 325 E. Hillcrest Drive, Suite #150 Thousand Oaks, CA USA Printed Monday, December 03,

2 Copyright Nexsan Technologies, Inc. All rights reserved. Trademarks Nexsan is a trademark or registered trademark of Nexsan Technologies, Inc. The Nexsan logo is a registered trademark of Nexsan Technologies, Inc. All other trademarks and registered trademarks are the property of their respective owners. Patents This product is protected by one or more of the following patents, and other pending patent applications worldwide: United States patents US8,191,841, US8,120,922; United Kingdom patents GB B, GB B, GB B, GB B, GB B About this document Unauthorized use, duplication, or modification of this document in whole or in part without the written consent of Nexsan Corporation is strictly prohibited. Nexsan Technologies, Inc. reserves the right to make changes to this manual, as well as the equipment and software described in this manual, at any time without notice. This manual may contain links to Web sites that were current at the time of publication, but have since been moved or become inactive. It may also contain links to sites owned and operated by third parties. Nexsan is not responsible for the content of any such third-party site.

3 De s c rip tio n 1 4 Co n tro le r 1 4 Sy n ta x 1 4 Op tio n s 1 4 Ex a mp le 1 4 De s c rip tio n 1 5 Co n tro le r 1 5 Sy n ta x 1 5 Op tio n s 1 5 Ex a mp le 1 5 De s c rip tio n 1 5 Co n tro le r 1 5 Sy n ta x 1 5 Op tio n s 1 6 Ex a mp le 1 6 De s c rip tio n 1 6 Co n tro le r 1 6 Sy n ta x 1 6 Op tio n s 1 6 Ex a mp le 1 6 Contents Contents Contents iii Chapter 1: Introduction 5 NFSv3 5 NFSv4 5 NFS Interoperability 5 Chapter 2: Interoperability Matrix for NFS 7 Chapter 3: Using NIS with NFS 9 Integrating with Network Information Service (NIS) 10 Using an NFS version 4 (NFSv4) client to access an NFS share 11 domain name 14 setdefaultdomain 15 changenameservices 15 ypinit 16 Sync 17 Creating an organization 18 Joining an organization 18 Modifying an organization name 19 Modifying an organization address 19 Confirming an organization address 20 Modifying an organization password 20 Leaving an organization 20 Listing available folders 21 Listing synced folders 21 Exposing Unity folders 22 Syncing a folder to the system 22 Removing a synced folder 23 Resending an activation code 23 Resetting a password 24 Resetting the password activation code 24 Nexsan Unity iii

4 De s c rip tio n 3 1 Co n tro le r 3 1 Sy n ta x 3 1 Op tio n s 3 1 Ex a mp le 3 1 De s c rip tio n 3 1 Co n tro le r 3 1 Sy n ta x 3 1 Op tio n s 3 2 Ex a mp le Ex a mp le Ex a mp le De s c rip tio n 3 5 Co n tro le r 3 5 Sy n ta x 3 5 Op tio n s 3 5 Ex a mp le Ex a mp le Ex a mp le Ex a mp le Contents Configuring bandwidth limits 25 Listing bandwidth settings 26 Configuring resource group WAN settings 26 Listing resource group WAN settings 26 Configuring the network interface for n-way Sync 27 Listing network interface settings 27 Setting mobile access permissions 28 Setting Web file access permissions 28 Setting Weblink download permissions 29 Retrieving Web links 29 Deleting Web links 30 ypcat 30 shareacl 31 nstusermaps 35 Chapter 4: Using LDAP with NFS 39 Connecting to an LDAP Directory Service 40 Configuring the LDAP Client in AD mode 41 Initializing LDAP to Active Directory mapping 42 Setting the LDAP Client configuration 43 Chapter 5: Using Unity Authentication with NFS 45 Reverting to Unity Authentication 46 Chapter 6: Using Active Directory (AD) for NFS 47 Microsoft Active Directory domain requirements 48 Creating computer objects on the Active Directory server 49 Delegating control to a non-administrator user account 52 Joining a Microsoft Active Directory domain using Unity 55 Joining a domain using the CLI 58 Nexsan Unity NFS Interoperability Technical Guide v. 5.1 Unity iv

5 Chapter 1 Chapter Introduction 1: NFS stands for Network File System and is the distributed file system used in many UNIX-based operating systems, such as Solaris, AIX, HP-UX, Linux, and FreeBSD. It is also available for other operating systems, such as the Mac OS, OpenVMS, Microsoft Windows, Novell NetWare, and IBM AS/400. NFS allows a user on a client computer to access files over a network in a manner similar to how local storage is accessed. Nexsan Unitys can be integrated with two versions of NFS: NFSv3 and NFSv4. NFSv4.1 and NFSv4.2 are not supported at this time, and NFSv2 is not supported at all. NFSv3 NVFv3, first published in 1995, added support for 64-bit files and offsets, thus removing the 2GB file size limitation. It also added several other features, such as asynchronous writes, the READDIRPLUS operation (to fetch file handles and attributes along with file names when scanning a directory), and native support for TCP as a transport layer. NFSv4 NFSv4, first published in 2000 and updated in 2003, includes performance improvements, mandates strong security, and introduces a stateful protocol. NFSv4.1 and NFSv4.2 are not supported at this time. NFS Interoperability NFS is only one piece of the network file sharing environment. NFS must also work with the directory services of the host computers attached to the network. NFS works with UNIX services such as NIS, LDAP, and Local, and also with Microsoft services like Active Directory (AD) and Identity Management for UNIX (IDMU). Each directory service works with NFS in slightly different ways, and multiple directory services can operate with NFS at the same time. However, certain combinations require additional set up and configuration; see Interoperability Matrix for NFS on page 7. This document lists the environments, including directory services, currently supported by Unity's implementation of NFS services;. It also provides procedures for integrating Unity with NFS in these supported environments. 1 Nexsan Unity 5

6 Nexsan Unity NFS Interoperability Technical Guide v. 5.1 Unity 6

7 Chapter 2 Chapter Interoperability 2: Matrix for NFS Access control lists (ACLs) are supported when using Unitys with NFSv3 and NSFv4. Refer to the table below for the procedure required according to the authentication method used for the UNIX directory service. Table 2-1: UNIX authentication scenarios Authentication implementation Active Directory only Active Directory and IDMU Active Directory with NIS implementation Active Directory with local authentication LDAP only Procedure Join the Active Directory domain as described in Using Active Directory (AD) for NFS on page Join the Active Directory domain as described in Using Active Directory (AD) for NFS on page Add UNIX attributes to AD users using IDMU in AD. 1. Join the Active Directory domain as described in Using Active Directory (AD) for NFS on page For NFSv3, use the standard NIS procedure. See Integrating with Network Information Service (NIS) on page For NFS v4, use the standard NIS integration procedure. See Integrating with Network Information Service (NIS) on page For NFSv4, configure the domain as described in Using an NFS version 4 (NFSv4) client to access an NFS share on page Map users using the nstusermaps CLI command; see nstusermaps on page Join the Active Directory domain as described in Using Active Directory (AD) for NFS on page Add local users manually to AD. 3. Map users using the nstusermaps CLI command; see nstusermaps on page 35. Use the standard LDAP connection procedure. See Connecting to an LDAP Directory Service on page Nexsan Unity 7

8 Authentication implementation LDAP with Active Directory Procedure 1. Join AD as described in Using Active Directory (AD) for NFS on page Open the nxadmin CLI menu. 3. Select option 6, Configure File Systems and Active Directory. 4. Select option 7, Configure the LDAP client in AD mode. See Configuring the LDAP Client in AD mode on page Select option 2, Initialize LDAP to Active Directory mapping. See Initializing LDAP to Active Directory mapping on page Select option 5, Set LDAP client configuration, and follow the steps to configure the LDAP client. See Setting the LDAP Client configuration on page Map users using the nstusermaps CLI command. See nstusermaps on page For NFSv4 only, configure the NSFv4 domain. See Using an NFS version 4 (NFSv4) client to access an NFS share on page NIS only 1. For NFSv3, use the standard NIS procedure. See Integrating with Network Information Service (NIS) on page For NFS v4, use the standard NIS integration procedure, but do NOT modify /etc/resolv.conf. See Integrating with Network Information Service (NIS) on page For NFSv4, configure the domain as described in Using an NFS version 4 (NFSv4) client to access an NFS share on page Map users using the nstusermaps CLI command; see nstusermaps on page 35. Local authentication (Nexsan Unity) 1. Standard Unity authentication process as described in Reverting to Unity Authentication on page Configure the NSFv4 domain. See Using an NFS version 4 (NFSv4) client to access an NFS share on page 11. Nexsan Unity NFS Interoperability Technical Guide v. 5.1 Unity 8

9 Chapter 3 Chapter Using3: NIS with NFS Use the following procedures when integrating NFS with the NIS directory service: Integrating with Network Information Service (NIS) 10 Using an NFS version 4 (NFSv4) client to access an NFS share 11 domain name 14 setdefaultdomain 15 changenameservices 15 ypinit 16 Sync 17 ypcat 30 shareacl 31 nstusermaps 35 3 Nexsan Unity 9

10 Integrating with Network Information Service (NIS) Integrating with Network Information Service (NIS) In UNIX environments (for connectivity to NFS file systems), the Unity Storage System supports three UNIX directory services: LDAP (Lightweight Directory Access Protocol), NIS (Network Information Service), and Unity authentication. If you have UNIX users that authenticate through NIS regardless of the authentication set up for the Unity Storage System you must run some nxadmin CLI commands in a specific order to fully integrate the Unity Storage System with NIS. 3 To integrate the Unity Storage System with NIS: 1. Create the name of the domain. Type this command: domain name <domain> Where <domain> is the name of the NIS domain used; for further details, see domain name on page Define the domain as the default NIS domain used; for further details, see setdefaultdomain on page 15. setdefaultdomain <domain> 3. Reconfigure the etc/nsswitch.conf file after changing the authentication mode so that the NIS authentication settings are added to password and group files. Type this command: changenameservices -c add -s nis For further details, see changenameservices on page To initialize the NIS server, type this command on the active controller: ypinit c For further details, see ypinit on page 16. a. You will be prompted to enter the NIS server name: In order for NIS to operate successfully, we have to construct a list of the NIS servers. Please continue to add the names for YP servers in order of preference, one per line. When you are done with the list, type a <control D> or a return on a line by itself. next host to add: nis.nisdomain2.lan next host to add: b. When prompted to confirm the NIS server name, type y and press Enter: The current list of yp servers looks like this: nis.nisdomain2.lan Is this correct? [y/n: y] y If you see svcadm messages about services missing, similar to this: svcadm: Pattern 'network/nis/server:default' doesn't match any instances you may ignore these messages. 5. Add the NIS server host to /etc/hosts on both controllers. a. Open the hosts configuration file, type: edit/etc/hosts b. Add the NIS server to the list, in this format: <server IP address> nis-p-<server name> <domain name> Nexsan Unity NFS Interoperability Technical Guide v. 5.1 Unity 10

11 Chapter 3: Using NIS with NFS 6. To start active services for the NIS client, type this command on both controllers: svc enable nis/client For further details, see. 7. To display the list of NIS users, type: ypcat -k passwd For further details, see ypcat on page To display the list of NIS groups, type: ypcat -k group What s Next: 1. Give the NIS users access to the file using the shareacl command. For information, see shareacl on page Map users using the nstusermaps command. For information, see nstusermaps on page 35. Using an NFS version 4 (NFSv4) client to access an NFS share To access or mount an NFS share from an NFS version 4 (NFSv4) client, you must perform some additional configuration steps, both on Unity where the NFS share exists and on the NFSv4 client computers where you intend to mount the NFS share. Note NSFv4 uses name-based permissions mapping. This means users must have the same name on both the client and Unity. It also requires an NFSv4 Domain to be set. This must be identical on both Unity and the client. 3 On Unity where the NFS share exists, you must: 1. Specify a domain name to enable user/group mapping between Unity and your NFSv4 clients; 2. Define NFS settings, such as the maximum number of client connections; 3. Use the nxadmin command line interface (CLI) to add user and/or group accounts, respectively, on Unity with account names that correspond to user and/or group accounts on the NFSv4 client computers where you intend to mount the NFS share. On the NFSv4 client computers where you intend to mount the NFS share, you must: 1. Add the NFSv4 domain name you specified on Unity to the /etc/idmapd.conf file; 2. Stop and then restart the idmap (Identity Mapping) service; 3. Make sure this service starts on system boot up: chkconfig rpcidmapd on; 4. Mount the NFS share. To configure NFSv4 support: 1. On the Unity navigation bar, select Storage > File Systems. 2. Click the link to the file system you need to access. 3. Select Summary > Properties. Nexsan Unity 11

12 Using an NFS version 4 (NFSv4) client to access an NFS share 4. Click the Enable NFS button Figure 3-1: File System Properties panel 3 5. Click the Apply button to save your settings. Nexsan Unity NFS Interoperability Technical Guide v. 5.1 Unity 12

13 Chapter 3: Using NIS with NFS 6. Use the nxadmin command line interface (CLI) to add user and/or group accounts to Unity with account names that correspond to user and/or group accounts on the NFSv4 client computers where you intend to mount the NFS share: a. Access the nxadmin CLI on Unity. b. Log on as nxadmin. c. In the NestOS Admin Menu, type 4 (Run a Command). d. Press the Enter key. e. At the command: prompt, type the useradd command using this syntax to add a user: useradd -u <uid> <user name> You cannot use these UID numbers because they are reserved: 0 to to If one of these IDs is already assigned to a user on your network, please contact Nexsan Technical Support to request that they free up the reserved ID. f. Press the Enter key. g. At the command: prompt, type the groupadd command using this syntax to add a group: groupadd -u <gid> <group name> You cannot use these GID numbers because they are reserved: 0 to to If one of these IDs is already assigned to a user on your network, please contact Nexsan Technical Support to request that they free up the reserved ID. h. Press the Enter key. 3 Nexsan Unity 13

14 domain name 3 7. Assign the local user and/or group accounts (that you created in the previous step) access permissions to the NFS share. You perform this step in the nxadmin Command Line Interface (CLI) using the shareacl command: a. Type the shareacl command to display its command reference and options. As an example, to assign the user bobsummers Full access permissions to the NFS share PayRollData1 in storage pool FinancePool1, type: shareacl -c append -p FinancePool1 -s PayRollData1 -u bobsummers -a full_set -d allow To assign Read-only access permissions, replace -a full_set with -a read_set; or, to assign Read/Write access permissions, replace -a full_set with -a write_set. To deny access, replace -d allow with -d deny. 8. Open the /etc/idmapd.conf file and change the value for the Domain parameter to correspond to the NFSv4 domain name you specified in Step 1; for example: Domain = NST.domain 9. Stop and start the idmap (Identity Mapping) service; for example: service rpcidmapd stop service rpcidmapd start 10. Make sure this service starts on boot up: chkconfig rpcidmapd on 11. Mount the NFS share. domain name Controller Syntax Options This command displays or sets the domain name used for NIS integration. For steps to integrate NIS, see Integrating with Network Information Service (NIS). Run this command on both controllers. domain name [<domain> -s] <domain> This is the domain name that you wish to assign for NIS integration. -s This option displays the current domain name. Example domain name -s qadomain.net Nexsan Unity NFS Interoperability Technical Guide v. 5.1 Unity 14

15 Chapter 3: Using NIS with NFS setdefaultdomain Controller Syntax This command defines the default domain used with your the Unity Storage System. You can create, remove, or show the default domain. This command can also be used for NIS domain integration. For steps to integrate NIS, see Integrating with Network Information Service (NIS). You can run this command on any controller. setdefaultdomain [-d] [-s] [<domain name>] Options -d This option deletes the current default domain. -s This option displays the current default domain. domain name This command sets the default domain to the domain name you specify. 3 Example We change the default domain to qadomain.net. setdefaultdomain qadomain.net changenameservices Controller Syntax This command defines the properties of naming services. You can add or remove switches, or show if the switch is configured. For NIS integration, this command reconfigures the etc/nsswitch.conf file after changing the authentication mode in the user interface so that the NIS authentication settings are added to the password and group files. For steps to integrate NIS, see Integrating with Network Information Service (NIS). Run this command on both controllers. changenameservices -c <command> -s <switch> Nexsan Unity 15

16 ypinit Options -c This option lets you run one of the following commands: -s add: Adds the specified switch to nameservices. remove: Removes the specified switch from nameservices. show: Shows whether or not the switch is configured. This option lets you specify a switch to run a command on. Currently, the only supported switch is nis, which is used for NIS integration. Example changenameservices -c add -s nis Setting the current node... Setting the peer node... ypinit 3 Controller Syntax This command initializes the NIS client, including building a master NIS server database and a slave database on the NIS server. For steps to integrate NIS, see Integrating with Network Information Service (NIS). Run this command on the active controller. (The active controller has the System Management component running on it.) ypinit [-c] [-m] [-s <master server>] Options -c This command sets an NIS client. You must run the ypinit -c command whenever a new NIS server is added to the network or when an existing one is decommissioned. Note: The ypinit -c command must be run on both controllers. This is required if you are integrating NIS with the Unity Storage System. ypinit -m This command builds a master server NIS database. ypinit -s <master server> This command builds a slave database on the NIS server. The Master Server must be the same server map name (or map nick name) returned by the ipwhich command. Example We create a slave database on the NIS master server. ypinit - s nis.nisdomain2.lan Nexsan Unity NFS Interoperability Technical Guide v. 5.1 Unity 16

17 Chapter 3: Using NIS with NFS Sync The nxcmd Sync command queries the status of the n-way Sync subsystem. This section explains how to use n-way Sync on the Unity Storage System using the nxcmd CLI. Before you set up the Unity System using the nxcmd CLI, you must make sure that all network settings are configured on the system. Note If this is the first time you are using the nxcmd CLI, you must specify connectivity parameters for the system as you run these commands. For more information, see "Accessing the nxadmin CLI" in the Nexsan nxadmin Command Line Interface Guide on the Nexsan Documentation & Downloads page. You can perform these actions with the Sync option: Createorganization creates an organization with Nexsan Central Services for the n-way Sync mechanism on this Unity Storage System. Joinorganization joins this Unity Storage System to an existing organization on Nexsan Central Services. ModifyorganizationName modifies the organization name. Modifyorganization modifies the organization account address. Confirm confirms the account for the organization. ModifyorganizationPassword modifies the organization password. LeaveOrganization unjoins the Unity Storage System from the organization. ListAvailableFolders lists all available folders in the organization that can be synced with this Unity Storage System. ListSyncedFolders lists all the folders that are currently synced in the organization. ExposeFolder exposes a folder on this Unity Storage System to the organization. SyncFolder syncs an exposed folder to this Unity Storage System. RemoveSyncedFolder removes a synced folder on Unity appliance. ResendActivationCode resends the activation code. ResetPassword resets the password for the account associated with the organization. ResetPasswordActivationCode enables you to specify the activation code to confirm the password reset. ConfigureBandwidth1 enables bandwidth limits for data syncing. ListBandwidthSettings displays the current bandwidth settings for each resource group. ConfigureWan configures WAN settings for each pool resource group. ListWanSettings displays the WAN settings for each resource group. NetworkInterface configures the network interface to use for the n-way Sync mechanism on this Unity Storage System. An interface must be specified for each resource group. ListNetworkInterfaceSettings displays the network interface configured for each pool resource group. MobilePermissions controls the access of the Unity mobile apps to content of this folder. WebAccessPermissions controls the Web file access to the contents of the folder. 3 Nexsan Unity 17

18 Sync WebLinkPermissions enables the creation and use of download links to files in this folder. RetrieveWebLinks displays Web links and their properties. You can search for specific user's link. To do so, you have to provide AD Admin Credentials. DeleteWebLinks deletes a specified link. Creating an organization The nxcmd Sync Createorganization command creates an organization with Nexsan Central Services for the n-way Sync mechanism on this Unity Storage System. nxcmd Sync Createorganization /Name:<name> / < address> 3 Createorganization parameters /Name / /Password Specify the organization name. Specify the address for the organization. Specify the organization account password. Example: nxcmd sync Createorganization /Name:MyOrgName / MyOrg @domain.com /Password:MyOrgPassword create a new organization with Nexsan Central Services for the n-way Sync mechanism on this Unity Storage System. Joining an organization The nxcmd Sync Joinorganization joins this Unity Storage System to an existing organization on Nexsan Central Se rvices. nxcmd Sync Joinorganization /Name:<name> / < address> Joinorganization parameters /Name / /Password Specify the organization name. Specify the address for the organization. Specify the organization account password. Nexsan Unity NFS Interoperability Technical Guide v. 5.1 Unity 18

19 Chapter 3: Using NIS with NFS Example: nxcmd sync Joinorganization /Name:MyOrgName /Password:MyOrgPassword Modifying an organization name The nxcmd Sync ModifyorganizationName command modifies the organization name. nxcmd Sync ModifyorganizationName /Name:<name> / < address> ModifyorganizationName parameters /Name / Specify the organization name. Specify the address for the organization. /Password Example: Specify the organization account password. nxcmd sync ModifyorganizationName /Name:MyOrgName /Password:MyOrgPassword Modifying an organization address The nxcmd Sync Modifyorganization command modifies the organization account address. 3 nxcmd Sync Modifyorganization /Name:<name> / < address> Modifyorganization parameters /Name / /Password Specify the organization name. Specify the address for the organization. Specify the organization account password. Example: nxcmd sync Modifyorganization /Name:MyOrgName / MyOrg @domain.com /Password:MyOrgPassword Nexsan Unity 19

20 Sync Confirming an organization address The nxcmd Sync Confirm command confirms the account for the organization. nxcmd Sync Confirm /Name:<name> / < address> Confirm parameters /Name / /Password Specify the organization name. Specify the address for the organization. Specify the organization account password. 3 Example: nxcmd sync Confirm /Name:MyOrgName / MyOrg @domain.com /Password:MyOrgPassword Modifying an organization password The nxcmd Sync ModifyOrganizationPassword command modifies the organization password. nxcmd Sync ModifyOrganizationPassword /Name:<name> / < address> ModifyOrganizationPassword parameters /Name / /Password Specify the organization name. Specify the address for the organization. Specify the organization account password. Example: nxcmd sync ModifyOrganizationPassword /Name:MyOrgName / MyOrg @domain.com /Password:MyOrgPassword Leaving an organization The nxcmd Sync LeaveOrganization command unjoins the Unity appliance from the organization. Nexsan Unity NFS Interoperability Technical Guide v. 5.1 Unity 20

21 Chapter 3: Using NIS with NFS nxcmd Sync LeaveOrganization /Name:<name> / < address> LeaveOrganization parameters /Name / /Password Specify the organization name. Specify the address for the organization. Specify the organization account password. Example: nxcmd sync LeaveOrganization /Name:MyOrgName /Password:MyOrgPassword Listing available folders The nxcmd Sync ListAvailableFolders command lists all available folders in the organization that can be synced with this Unity Storage System. nxcmd Sync ListAvailableFolders /Name:<name> / < address> 3 ListAvailableFolders parameters /Name / /Password Specify the organization name. Specify the address for the organization. Specify the organization account password. Example: nxcmd sync ListAvailableFolders /Name:MyOrgName / MyOrg @domain.com /Password:MyOrgPassword Listing synced folders The nxcmd Sync ListSyncedFolders command lists all the folders that are currently synced in the organization. Nexsan Unity 21

22 Sync nxcmd Sync ListSyncedFolders /Name:<name> / < address> ListSyncedFolders parameters /Name / /Password Specify the organization name. Specify the address for the organization. Specify the organization account password. 3 Example: nxcmd sync ListSyncedFolders /Name:MyOrgName / MyOrg @domain.com /Password:MyOrgPassword Exposing Unity folders The nxcmd Sync ExposeFolder command exposes a folder on this Unity Storage System to the organization. nxcmd Sync ExposeFolder /Name:<name> / < address> ExposeFolder parameters /Name / /Password Specify the organization name. Specify the address for the organization. Specify the organization account password. Example: nxcmd sync ExposeFolder /Name:MyOrgName / MyOrg @domain.com /Password:MyOrgPassword Syncing a folder to the system The nxcmd Sync SyncFolder command syncs an exposed folder to this Unity Storage System. Nexsan Unity NFS Interoperability Technical Guide v. 5.1 Unity 22

23 Chapter 3: Using NIS with NFS nxcmd Sync SyncFolder /Name:<name> / < address> SyncFolder parameters /Name / /Password Specify the organization name. Specify the address for the organization. Specify the organization account password. Example: nxcmd sync SyncFolder /Name:MyOrgName /Password:MyOrgPassword Removing a synced folder The nxcmd Sync RemoveSyncedFolder command removes a synced folder on Unity Storage System. nxcmd Sync RemoveSyncedFolder /Name:<name> / < address> 3 RemoveSyncedFolder parameters /Name / /Password Specify the organization name. Specify the address for the organization. Specify the organization account password. Example: nxcmd sync RemoveSyncedFolder /Name:MyOrgName / MyOrg @domain.com /Password:MyOrgPassword Resending an activation code The nxcmd Sync ResendActivationCode command resends the activation code. nxcmd Sync ResendActivationCode /Name:<name> / < address> Nexsan Unity 23

24 Sync ResendActivationCode parameters /Name / /Password Specify the organization name. Specify the address for the organization. Specify the organization account password. Example: nxcmd sync ResendActivationCode /Name:MyOrgName /Password:MyOrgPassword Resetting a password The nxcmd Sync ResetPassword command resets the password for the account associated with the organization. 3 nxcmd Sync ResetPassword /Name:<name> / < address> ResetPassword parameters /Name / /Password Specify the organization name. Specify the address for the organization. Specify the organization account password. Example: nxcmd sync ResetPassword /Name:MyOrgName / MyOrg @domain.com /Password:MyOrgPassword Resetting the password activation code The nxcmd Sync ResetPasswordActivationCode command enables you to specify the activation code to confirm the password reset. nxcmd Sync ResetPasswordActivationCode /Name:<name> / < address> Nexsan Unity NFS Interoperability Technical Guide v. 5.1 Unity 24

25 Chapter 3: Using NIS with NFS ResetPasswordActivationCode parameters /Name / /Password Specify the organization name. Specify the address for the organization. Specify the organization account password. Example: nxcmd sync ResetPasswordActivationCode /Name:MyOrgName /Password:MyOrgPassword Configuring bandwidth limits The nxcmd Sync ConfigureBandwidth command enables bandwidth limits for data syncing. nxcmd Sync ConfigureBandwidth /downstreamlimit<limit> /upstreamlimit <limit> [/upstreamlimitrg1:<upstream limit for RG1; format: KB MB GB TB or 0 for unlimited>] [/upstreamlimitrg2:<upstream limit for RG2; format: KB MB GB TB or 0 for unlimited>] [/downstreamlimitrg1:<downstream limit for RG1; format: KB MB GB TB or 0 for unlimited>] [/downstreamlimitrg2:<downstream limit for RG2; format: KB MB GB TB or 0 for unlimited>] 3 ConfigureBandwidth parameters /upstreamlimitrg1 Upstream limit in megabytes for resource group 1 /upstreamlimitrg2 Upstream limit in megabytes for resource group 2 /downstreamlimitrg1 Downstream limit in megabytes for resource group 1 /downstreamlimitrg2 Downstream limit in megabytes for resource group 2 Example nxcmd sync ConfigureBandwidth /upstreamlimitrg1:10mb /downstreamlimitrg1:100mb In this example, you are setting the upstream limit for RG1 to 10 Megabytes, the downstream limit for RG1 to 100 Megabyte. Nexsan Unity 25

26 Sync Listing bandwidth settings The nxcmd Sync ListBandwidthSettings command displays the current bandwidth settings for each resource group. nxcmd Sync ListBandwidthSettings /Name:<name> / < address> ListBandwidthSettings parameters /Name / /Password Specify the organization name. Specify the address for the organization. Specify the organization account password. 3 Example: nxcmd sync ListBandwidthSettings /Name:MyOrgName / MyOrg @domain.com /Password:MyOrgPassword Configuring resource group WAN settings The nxcmd Sync ConfigureWan command configures WAN settings for each pool resource group. nxcmd Sync ConfigureWan /Name:<name> / < address> ConfigureWan parameters /Name / /Password Specify the organization name. Specify the address for the organization. Specify the organization account password. Example: nxcmd sync ConfigureWan /Name:MyOrgName / MyOrg @domain.com /Password:MyOrgPassword Listing resource group WAN settings The nxcmd Sync ListWanSettings command displays the WAN settings for each resource group. Nexsan Unity NFS Interoperability Technical Guide v. 5.1 Unity 26

27 Chapter 3: Using NIS with NFS nxcmd Sync ListWanSettings /Name:<name> / < address> ListWanSettings parameters /Name / /Password Specify the organization name. Specify the address for the organization. Specify the organization account password. Example: nxcmd sync ListWanSettings /Name:MyOrgName /Password:MyOrgPassword Configuring the network interface for n-way Sync The nxcmd Sync NetworkInterface command configures the network interface to use for the n-way Sync mechanism on the Unity Storage System. An interface must be specified for each resource group. nxcmd Sync NetworkInterface /Name:<name> / < address> 3 Createorganization parameters /Name / /Password Specify the organization name. Specify the address for the organization. Specify the organization account password. Example: nxcmd sync NetworkInterface /Name:MyOrgName / MyOrg @domain.com /Password:MyOrgPassword Listing network interface settings The nxcmd Sync ListNetworkInterfaceSettings command displays the network interface configured for each pool resource group. Nexsan Unity 27

28 Sync nxcmd Sync ListNetworkInterfaceSettings /Name:<name> / < address> ListNetworkInterfaceSettings parameters /Name / /Password Specify the organization name. Specify the address for the organization. Specify the organization account password. 3 Example: nxcmd sync ListNetworkInterfaceSettings /Name:MyOrgName / MyOrg @domain.com /Password:MyOrgPassword Setting mobile access permissions The nxcmd Sync MobilePermissions command controls the access of the Unity mobile apps to content of this folder. nxcmd Sync MobilePermissions /Name:<name> / < address> MobilePermissions parameters /Name / /Password Specify the organization name. Specify the address for the organization. Specify the organization account password. Example: nxcmd sync MobilePermissions /Name:MyOrgName / MyOrg @domain.com /Password:MyOrgPassword Setting Web file access permissions The nxcmd Sync WebAccessPermissions command controls the Web file access to the contents of the folder. Nexsan Unity NFS Interoperability Technical Guide v. 5.1 Unity 28

29 Chapter 3: Using NIS with NFS nxcmd Sync WebAccessPermissions /Name:<name> / < address> WebAccessPermissions parameters /Name / /Password Specify the organization name. Specify the address for the organization. Specify the organization account password. Example: nxcmd sync WebAccessPermissions /Name:MyOrgName /Password:MyOrgPassword Setting Weblink download permissions The nxcmd Sync WebLinkPermissions command enables the creation and use of download links to files in this folder. nxcmd Sync /Name:<name> / < address> 3 WebLinkPermissions parameters /Name / /Password Specify the organization name. Specify the address for the organization. Specify the organization account password. Example: nxcmd sync WebLinkPermissions /Name:MyOrgName / MyOrg @domain.com /Password:MyOrgPassword Retrieving Web links The nxcmd Sync RetrieveWebLinks command retrieves Web links and their properties. You can search for specific user's link. To do so, you have to provide AD Admin Credentials. Nexsan Unity 29

30 ypcat nxcmd Sync RetrieveWebLinks /Name:<name> / < address> RetrieveWebLinks parameters /Name / /Password Specify the organization name. Specify the address for the organization. Specify the organization account password. 3 Example: nxcmd sync RetrieveWebLinks /Name:MyOrgName / MyOrg @domain.com /Password:MyOrgPassword Deleting Web links The nxcmd Sync DeleteWebLinks command deletes a specified link. nxcmd Sync DeleteWebLinks /Name:<name> / < address> DeleteWebLinks parameters /Name / /Password Specify the organization name. Specify the address for the organization. Specify the organization account password. Example: nxcmd sync DeleteWebLinks /Name:MyOrgName / MyOrg @domain.com /Password:MyOrgPassword ypcat Nexsan Unity NFS Interoperability Technical Guide v. 5.1 Unity 30

31 Chapter 3: Using NIS with NFS Controller Syntax Options This command displays values from a NIS database in an NIS integration. Since ypcat uses the NIS network, you do not need to specify a NIS server. For steps to integrate NIS, see Integrating with Network Information Service (NIS). Run this command on the active controller. (The active controller has the System Management component running on it.) ypcat [-k <key>] [-d <domain name>] [-t <map name>] [-x] -k <key> This option displays the database values for the specified key. Example shareacl -d <domain name> This option specifies the domain name of the NIS server. -t <map name> This option inhibits the translation of database map nick names for the specified name. The name can be a map name or map nickname. -x This option displays the translation table for map nick names. We display the list of NIS users. ypcat -k passwd 3 Controller Syntax This command enables you to assign local user and/or group accounts (that you added to the Unity Storage System) access permissions (Read, Read/Write, or Full) to NFS file systems on the system. TIP: If you only have CIFS file systems in your environment, you can set the file systems for both CIFS and NFS sharing in Nexsan Unity. The file system will be accessible from the CLI and you will be able to configure the CIFS file systems using the shareacl command. Run this command on the controller hosting the file systems. shareacl [-c shares get resetall deleteindex replaceall replace insert append help] [-i <index name>] [-p <pool name>] [-s <file system name>] Nexsan Unity 31

32 shareacl [-u <user name>] [-g <group name>] [-a permission] [-d allow deny] [-f inheritance] Options -c shares This option lists existing file systems on the Unity Storage System, along with their type and the pool name. -c get This option displays permissions and the indexes. You must provide the: pool name (with the -p option) and file systems name (with the -s option). 3 -c resetall This option resets all permissions for the specified file systems. You must provide the: pool name (with the -p option), and file systems name (with the -s option). -c deleteindex This option removes a permission entry from the file systems access index. You must provide the: pool name (with the -p option), file systems name (with the -s option), and index name (with the -i option). -c replaceall This option replaces all access control lists with the specified list. You must provide the: pool name (with the -p option), file systems name (with the -s option), user name (with the -u option) or group name (with the -g option), and permission status (with the -d option). Optionally, you can provide the inheritance using the -f option. -c insert This option inserts a permission entry at the specified index. You must provide the: pool name (with the -p option), file systems name (with the -s option), user name (with the -u option) or group name (with the -g option), and permission status (with the -d option). Optionally, you can provide the inheritance using the -f option. Nexsan Unity NFS Interoperability Technical Guide v. 5.1 Unity 32

33 Chapter 3: Using NIS with NFS -c append This option adds a permission for the specified entry, which can be the: pool name (with the -p option), file systems name (with the -s option), user name (with the -u option) or group name (with the -g option), or permission status (with the -d option). Optionally, you can provide the inheritance using the -f option. -c help This option display help content for the shareacl command. -i <index name> This option specifies the index name of a permission entry. -p <pool name> This option specifies the name of the pool where the file system resides. -s <file system name> This option specifies the name of the file systems to which we grant or revoke permissions. -u <user name> This option specifies the name of the user to whom we grant or revoke permissions. 3 -g <group name> This option specifies the name of the group to which we grant or revoke permissions. -a permission This option specifies which permissions to grant or revoke. These permission arguments are supported: read_data (r): Permission to read the data of a file. list_directory (r): Permission to list the contents of a directory. write_data (w): Permission to modify a file's data anywhere in the file's offset range. add_file (w): Permission to add a new file to a directory. add_subdirectory (p): Permission to create a subdirectory to a directory. read_xattr (R): Permission to read the extended attributes of a file. write_xattr (W): Permission to create extended attributes or write to the extended attribute directory. execute (x): Permission to execute a file. read_attributes (a): Permission to read basic attributes (non-acls) of a file. write_attributes (A): Permission to change the times associated with a file or directory to an arbitrary value. Nexsan Unity 33

34 shareacl delete (d): Permission to delete a file. delete_child (D): Permission to delete a file within a directory. read_acl (c): Permission to read the ACL of a file. write_acl (C): Permission to write the ACL of a file. write_owner (o): Permission to change the owner of a file. These permission aliases are supported; they allow you so set multiple permissions concurrently: full_set: All permissions. modify_set: All permissions except write_acl and write_owner. read_set: read_data, read_acl, read_attributes, and read_xattr. write_set: write_data, append_data, write_attributes, and write_ xattr. -d allow deny This option gives or removes the permissions specified with the -a option. 3 -f inheritance This option provides inheritance settings based on a file or directory. These inheritance arguments are supported: file_inherit (f): Inherit to all newly created files. dir_inherit (d): Inherit to all newly created directories. inherit_only (i): When placed on a directory, do not apply to the directory, only to newly created files and directories. This flag requires that either file_inherit or dir_inherit be also specified. no_propagate (n): Indicates that ACL entries should be inherited to objects in a directory, but inheritance should stop after descending one level. This flag requires that either file_inherit or dir_inherit is also specified. Example 1 Example 2 Example 3 We provide user Bob full access to a file systems named PayRollData in a storage pool named FinancePool1, with an index number of 5. shareacl -c insert -p FinancePool1 -s PayRollData -u Bob -d allow -i 5 -a full_set We disable the file and directory inheritance for user Bob in storage pool poola, for file systems file systems3 at index number 4. The other permissions, which are listed in the command, remain the same. shareacl -c replace -p poola -s file systems3-i 4 -u bob -a list_directory/read_data/add_file/write_data/add_ subdirectory/append_data/read_xattr/write_xattr/execute/delete_ child/read_attributes/write_attributes/delete/read_acl/write_ acl/write_owner/synchronize -d allow We enable the file and directory inheritance for user bob in storage pool poola, for c3 at index number 4. Nexsan Unity NFS Interoperability Technical Guide v. 5.1 Unity 34

35 Chapter 3: Using NIS with NFS nstusermaps shareacl -c replace -p poola -s filesystem3 -i 4 -u bob -a list_ directory/read_data/add_file/write_data/add_subdirectory/append_ data/read_xattr/write_xattr/execute/delete_child/read_ attributes/write_attributes/delete/read_acl/write_acl/write_ owner/synchronize -d allow -f file_inherit/dir_inherit Controller Syntax Options This command enables you to map local users to Microsoft Active Directory users. Run this command on both controllers for changes to take effect. nstusermaps [-f <command file>] [add [-d] <name 1> <name 2>... [dump [-n] [-v] [export [-f <file name>] <format>] [flush [-a]] [get-namemap <name>] [help] [import [-F] [-f <file name>] <format>] [list] [remove [-a] [-f -t <name>] [-d <name 1> <name2>...]] [set-namemap [-a <authentication method>] [-D <bind DN>] [-j <password file>] <name 1> <name 2> [show [-c] [-v] identity <target type>] [unset-namemap [-a <authentication method>] [-D <bind DN>] [-j <password file>] [-f <command file>] This option reads and executes sub-commands from the specified command file. The nstusermaps -f command reads from standard input. add [-d] <name 1> <name 2> This command creates a mapping to the corresponding user or group account in the Microsoft Active Directory domain. nstusermaps add -d <windowsuser@ad.net> <unixusername> dump [-n] [-v] This command displays identity mapping information for users and groups existing on the 3 Nexsan Unity 35

36 nstusermaps Unity Storage System. It show the user or group SID (security ID) and the corresponding GID and UID. -n displays the Windows group maps. -v displays Windows group security IDs (SID) and their corresponding GIDs. export [-f <file name>] <format> This command exports user maps to the specified file and format. flush [-a] Flushes the identity mapping cache so that future mapping requests will be fully processed based on the current rules and directory information. This is a non-disruptive operation. A rule change automatically flushes the cache; this manual operation can be used to force newly changed directory information to take effect. get-namemap <name> This option displays the directory-based name mapping information from the specified name. The name can be a AD or native LDAP user or group object. 3 help This command displays the help for the nstusermaps command. import [-F] [-f <file name>] <format> This command imports user maps from the specified file and format. The -f file option reads the rules from the specified file. The -F option flushes existing name-based mapping rules before adding new ones. list This command displays existing user idmaps. If there is no idmap, there is no output. remove [-a] [-f -t <name>] [-d <windowsuser@ad.net> <unixusername>] This command removes a mapping from the corresponding user or group account in the Microsoft Active Directory domain. Use -a to remove all mapping information. set-namemap [-a <authentication method>] [-D <bind DN>] [-j <password file>] <windowsusername> <unixusername> This option sets name mapping information in the AD or native LDAP user or group object. You can use these arguments with set-namemap: -a specifies the authentication method when modifying native LDAP entry. The default value is sasl/gssapi. -D uses the distinguished name to bind to the directory. -j specifies the file containing the password for authentication to the directory. show [-c] [-v] identity <target type> This option shows the identity of type, target-type, that the specified name maps to. If you do not specify the target type, the non-diagonal mapping is shown. By default, it shows only mappings that have been established already. Nexsan Unity NFS Interoperability Technical Guide v. 5.1 Unity 36

37 Chapter 3: Using NIS with NFS -c forces the evaluation of name-based mapping configurations or the dynamic allocation of IDs. -v shows how the mapping was generated and also whether the mapping was just generated or was retrieved from the cache. unset-namemap [-a <authentication method>] [-D <bind DN>] [-j <password file>] This option unsets directory-based name mapping information from the specified name and optional target type. The name can be AD or native LDAP user or group object. Example 1 Example 2 Example 3 Example 4 We map Bob Summer's Microsoft Active Directory domain account to the account created for Bob on the Unity Storage System nstusermaps add winuser:<bob.summers@ad.net> unixuser:<bsummers> We display user maps to view GIDs and UIDs. nstusermaps dump usid:s == gid: usid:s == uid: gsid:s == gid: gsid:s == gid: We display Windows group GID and UID. nstusermaps dump -n wingroup:domain Users@ES == gid: wingroup:network == gid: wingroup:guests@builtin == gid: winuser:guest@es qadomain.net == gid: winuser:guest@es == uid: We display Windows group security IDs (SID) and their corresponding GIDs. nstusermaps dump -v gsid:s == gid: Method: Ephemeral gsid:s == gid: Method: Ephemeral gsid:s == gid: Method: Ephemeral usid:s == gid: Method: Ephemeral 3 Nexsan Unity 37

38 nstusermaps usid:s == uid: Method: Ephemeral 3 Nexsan Unity NFS Interoperability Technical Guide v. 5.1 Unity 38

39 Chapter 4 Chapter Using4: LDAP with NFS Use the following procedures when integrating NFS with the LDAP directory service: Connecting to an LDAP Directory Service 40 Configuring the LDAP Client in AD mode 41 4 Nexsan Unity 39

40 Connecting to an LDAP Directory Service For the standard LDAP connection procedure, follow the steps under Connecting to an LDAP Directory Service below. If you are using LDAP in an Active Directory environment, follow the steps under Configuring the LDAP Client in AD mode on the facing page. Connecting to an LDAP Directory Service The Unity Authentication service is preconfigured by default during initial system setup. Use this procedure if you want to instead connect to an LDAP Directory Service. To connect to an LDAP Directory Service: 1. If you are managing multiple Unity Storage Systems, log on to the Unity system that you want to connect to LDAP. 2. From the System menu, select Unity Systems. 3. Click Summary > User Authentication. Figure 4-1: Connecting to an LDAP Directory Service 4 4. Select LDAP Directory Service. The settings display for connecting to an LDAP Directory service on the network. 5. In the LDAP Domain Name field, type the name of the LDAP domain that you want Unity to connect to. Nexsan Unity NFS Interoperability Technical Guide v. 5.1 Unity 40

41 Chapter 4: Using LDAP with NFS 6. (Optionally) In the LDAP Host Name field, type the host name of the LDAP Directory server that you want Unity to connect to. This step is only required if: the domain name you specify in the LDAP Domain Name field does not resolve to the IP address of the LDAP Directory server, or the LDAP domain name you specify is an identification label for multiple resources in your LDAP implementation. If you do not specify an LDAP host name, Unity automatically connects to the LDAP Directory server that you specify in the LDAP Domain Name field. 7. Optionally, in the Time Server field, type the IP address or the fully qualified domain name of the time server that you want Unity to synchronize its date and time with. A time server is required to ensure that the date and time settings on Unity are synchronized with the LDAP Directory server that the system connects to. By default, a time server is already defined. Note Unity supports multiple time servers: if you specify a time server in the Time Server field, as opposed to using the LDAP Directory server for date and time synchronization for Unity, we highly recommend that you specify at least two time servers; this ensures that date and time synchronization on Unity continues in the event that one of the time servers you specify is no longer available. Note To specify multiple time servers, use a comma to separate each entry, for example: tick.utoronto.ca,time.nrc.ca. 8. In the Proxy DN field, type the Proxy identity's distinguished name (DN) configured on your LDAP Directory server. The Proxy identity is a user on the LDAP Directory server that has restricted authority to required information on the server. Nexsan Unity binds to the LDAP Directory server using the Proxy user's DN. Note The LDAP Directory server must have a Proxy identity configured before you connect Unity to the server. 9. Type the Proxy identity's password in the Password field. 10. Click the Apply button. 11. When the Confirm DNS Settings prompt appears, do one of the following: a. If the new domain server is in a different network domain, specify the IP addresses of the corresponding DNS servers, and click the Apply button, or b. If the new domain server is in the same network domain as the previous domain server, click the Apply button to keep the current DNS settings. 12. The wizard applies your settings and if all are successful, prompts you to click OK. Configuring the LDAP Client in AD mode A UNIX environment can use either a Local directory service, or use the NIS or LDAP protocol to access the directory service and the data stored on any UNIX server on the network. If the UNIX environment also communicates with a Windows environment, other directory services must be taken into account for proper access to directory services. For example, if Active Directory is used as the main directory service in your environment, you must join the Active Directory domain in addition to using your current UNIX directory service. Figure 4-2: NestOS LDAP Client in AD Mode menu 1 - Show current information 4 Nexsan Unity 41

42 Configuring the LDAP Client in AD mode 2 - Initialize LDAP to Active Directory mapping 3 - Upload a CA Certificate 4 - Remove a CA Certificate 5 - Set LDAP Client configuration 6 - Configure file systems group lookup 7 - Reset the LDAP Client configuration 8 - Clear the nstusermaps cache 9 - View instructions on using nstusermaps for LDAP to AD mapping 10 - Show ACLs on file systems 11 - Set ACLs on file systems 12 - Restart the LDAP Client Service q - Exit Select an option: 4 This section covers these topics: Showing current LDAP client information on page 1 Initializing LDAP to Active Directory mapping below Uploading a Certification Authority (CA) certificate on page 1 Removing a Certification Authority (CA) certificate on page 1 Setting the LDAP Client configuration on the facing page Configuring the file system group lookup on page 1 Resetting the LDAP Client configuration on page 1 Clearing the nstusermaps cache on page 1 Viewing instructions on using nstusermaps for LDAP to AD mapping on page 1 Showing ACLs on file systems on page 1 Setting ACLs on file systems on page 1 Restarting the LDAP Client service on page 1 Initializing LDAP to Active Directory mapping To initialize LDAP: 1. In the NestOS Admin Menu, type 6 (Configure Shares and Active Directory) and press Enter. 2. This displays the Shares submenu. Type 7 (Configure the LDAP Client in AD Mode) and press Enter. 3. This displays the LDAP Client in AD Mode menu. Type 2 (Initialize LDAP to Active Directory mapping) and press Enter. The Unity Storage System initializes the mapping on both the current cluster node and the other cluster node. Nexsan Unity NFS Interoperability Technical Guide v. 5.1 Unity 42

43 Chapter 4: Using LDAP with NFS Setting the LDAP Client configuration To configure the LDAP client: 1. In the NestOS Admin Menu, type 6 (Configure File Systems and Active Directory) and press Enter. 2. This displays the File Systems submenu. Type 7 (Configure the LDAP Client in AD Mode) and press Enter. 3. This displays the LDAP Client in AD Mode menu. Type 5 (Set LDAP Client configuration) and press Enter. 4. Select one of the two options: 1 - anonymous: a. Type 1 and press Enter to set the LDAP Client configuration to anonymous. b. Select one of the two credential options (tls or none) by typing its number and pressing Enter. 2 - simple bind: a. Type 2 and press Enter to set the LDAP Client configuration to simple bind. b. Enter the proxy DN and press Enter. 4 Nexsan Unity 43

44 Configuring the LDAP Client in AD mode Nexsan Unity NFS Interoperability Technical Guide v. 5.1 Unity 44

45 Chapter 5 Chapter Using5: Unity Authentication with NFS Use the following procedure when integrating NFS with the LDAP directory service: Reverting to Unity Authentication 46 5 Nexsan Unity 45

46 Reverting to Unity Authentication Reverting to Unity Authentication Use this procedure if you have the Microsoft Active Directory Service or LDAP Directory Service, and want to revert to the default Unity Authentication for your Unity Storage System. Unity is not connected to a user directory or authentication service on the network; you must manually create user and group accounts on Unity for user authentication. With Unity authentication, you create Unity user and group accounts for user authentication for operations with file systems and CIFS shares. CAUTION: If Unity is currently connected to a domain, and you subsequently configure Unity authentication for the system, all file system-level access permissions are removed, although fileand folder-level ACLs (CIFS) and permissions (NFS) remain unchanged. When you rejoin the previous domain that Unity was connected to, Unity restores all file systemlevel access permissions on the system. 5 To revert to Unity Authentication: 1. On the Unity navigation bar, select System > Unity Systems. 2. Select the Unity System you want to change the authentication method for. 3. Select Summary > User Authentication. 4. Select Unity Authentication Service. Figure 5-1: Unity Systems panel User Authentication view 5. Optionally, specify a time server in the Time Server field. 6. Click the Apply button. 7. When prompted confirm your DNS settings. If the new domain server is in a different network domain, please specify the IP addresses of the corresponding DNS servers, and then click the Apply button, or If the new domain server is in the same network domain as the previous domain server, click the Apply button to keep the current DNS settings. 8. Click OK to confirm. Nexsan Unity NFS Interoperability Technical Guide v. 5.1 Unity 46

47 Chapter 6 Chapter Using6: Active Directory (AD) for NFS Use the following procedures when integrating NFS with Microsoft Active Directory: Microsoft Active Directory domain requirements 48 Creating computer objects on the Active Directory server 49 Delegating control to a non-administrator user account 52 Joining a Microsoft Active Directory domain using Unity 55 Joining a domain using the CLI 58 6 Nexsan Unity 47

48 Microsoft Active Directory domain requirements To integrate NFS with Microsoft Active Directory: 1. Join an Active Directory Domain. To join an Active Directory domain through Unity, see. To join an Active Directory domain using the CLI, see Joining a domain using the CLI on page Map users using the nstusermaps CLI command. See nstusermaps on page 35. Microsoft Active Directory domain requirements This section describes the Microsoft Active Directory support requirements for Unity. Carefully review this table before joining Unity to a Microsoft Active Directory domain. Requirement 6 Operating Systems Windows Server 2016 Reverse DNS Windows Server 2012 Windows Server 2008 R2 Windows Server 2008 x86 or x64, including: Windows Server 2008 with Service Pack 1 Windows Server 2008 with Service Pack 2 Window Server 2003 R2 x86 or x64 The Microsoft Active Directory implementation must be configured with a reverse DNS lookup zone. Global catalog and LDAP catalog ports Time server Domain administrator privileges DNS alias for nonstandard domain names The primary domain controller that Unity connects to must have both the global catalog port (3268) and the LDAP catalog port (389) open. In a Microsoft Active Directory forest implementation, all domain controllers must have these ports open. The primary domain controller that Unity connects to must be configured as a reliable time source (time server capability) for the domain. In a Microsoft Active Directory forest implementation, all domain controllers must have this capability. If the Microsoft Active Directory implementation does not provide, or is not configured for, time server capability, you must specify a valid Network Time Protocol (NTP) source for Unity to synchronize its date and time with. You will need to provide domain credentials for a domain administrator, or of a user who has full domain administrative privileges. If the user account does not have domain administrator privileges, you must create computer objects for Unity in the Active directory domain, and give the corresponding user account management access to the objects before joining the domain. Use a DNS alias if the domain controller name starts with a digit, or contains nonstandard characters. If the name of the primary domain controller that you configure Unity to connect to starts with a digit, or contains nonstandard Nexsan Unity NFS Interoperability Technical Guide v. 5.1 Unity 48

49 Chapter 6: Using Active Directory (AD) for NFS Requirement LM Manager authentication level Creation of machine accounts characters, you must set up an alias made up of only standard characters for the domain controller on the DNS server; standard characters include: (A-Z, a- z), digits (0-9), and hyphens (-). You must also add a resource record for the alias in the reverse DNS lookup zone. Later, when you configure the Unity Storage System to join the Microsoft Active Directory domain, you must specify the domain controller s alias, including its fully qualified domain name (FQDN), in the Domain Controller (optional) field. As an example, if the domain controller uses this name: 1MYDC_ 001.mydomain.lan, 1. Create this alias for the domain controller on the DNS server: MYDC Add a resource record for the alias in the reverse DNS lookup zone. 3. During the Site Setup process, when configuring Unity to join the Microsoft Active Directory domain, specify the domain controller s alias, including its fully qualified domain name (FQDN), in the Domain Controller (optional) field: MYDC-001.mydomain.lan By default, Unity uses NTML level 2 authentication. If your Active Directory Domain Controller uses a different authentication level, you must change this setting by selecting another LM Compatibility Level. The Microsoft Active Directory implementation must support the creation of machine accounts in the default Organizational Unit (OU).. 6 Creating computer objects on the Active Directory server In a typical deployment, Unity requires Domain Administrator privileges to join a Microsoft Active Directory domain. This process allows Unity to automatically create and configure computer objects for Unity on the Microsoft Active Directory server, without any manual intervention from a network administrator. In some environments, specifying Domain Administrator credentials to integrate Unity with the Microsoft Active Directory Domain is not desirable, or possible. For these deployments, a network administrator can join Unity to a Microsoft Active Directory Domain using a user account with limited domain administrative privileges. To allow this, you must manually perform configuration steps for creating and configuring computer objects for Unity on the Microsoft Active Directory server: Create a computer object(s) for Unity on the corresponding Active Directory Server for each controller node, as described in this procedure. Configure the attributes for the computer object(s) according to the settings described in this procedure. CAUTION: RISK OF OUTAGE Do not join Unity with Active Directory to Domain Controllers hosted on VMware. Domain Controllers used with Unity and Active Directory must either be a physical device or hosted externally to Unity. Nexsan Unity 49

50 Creating computer objects on the Active Directory server To create a computer object for a non-administrator user account: 1. On the relevant Active Directory Server, add a new computer object for Unity, using each controller node s host name. CAUTION: When creating the computer object, make sure to enter the host name exactly as it is configured on Unity, or on each of its controller nodes. 6 To obtain the host name for Unity controller nodes: a. Access the nxadmin CLI on Unity via SSH or remote console. Download and install an SSH client of your choice on a client machine that has network connectivity to Unity. You can use Putty, which is a (free) open source telnet and SSH client, available for download at this URL: b. Once you download and install an SSH client, launch it, and enter the IP address of a controller node. c. When the login prompt displays, type nxadmin, and press Enter. d. When you are prompted for the password, type the nxadmin (Nexsan Unity Administrator) password configured on Unity, and then press Enter. If you are connecting to a system that has not yet been configured using the Nexsan Unity System Configuration wizard that is, an uninitialized Unity you must type the default password for the nxadmin (Nexsan Unity Administrator) account: PASSWORD (all upper-case). e. On each controller node, run the hostname command. f. Take note of Unity host name; for example, ES Give the non-administrator domain user account the ability to perform the operation for integrating Unity with the Active Directory Domain. You must give the non-administrator domain user account the ability to join each controller node to the Active Directory Domain. It is important that you perform this step, since, by default, the privileges for joining a new computer object to the Active Directory Domain are automatically assigned to the Domain Administrator user/group account. Here is an example: Nexsan Unity NFS Interoperability Technical Guide v. 5.1 Unity 50

51 Chapter 6: Using Active Directory (AD) for NFS 3. Set the following attributes for the computer object that you added for Unity to the Active Directory Server. You must set these attributes separately for each controller node. CAUTION: Use the Active Directory Service Interfaces Editor (ADSI Edit) to set the attributes for the computer object(s). For each attribute, make sure to specify the value using the exact letter case, as shown. Table 6-1: Computer object attributes Attribute dnshostname msds- SupportedEncryptionTypes serviceprincipalname userprincipalname Value to set... <NESTHOSTNAME>.<domain name> For example: ES qadomain.net 31 cifs/<nesthostname>.<domain name> For example: cifs/es qadomain.net host/<nesthostname>.<domain name> For example: host/es qadomain.net HTTP/<NESTHOSTNAME>.<domain name> For example: HTTP/ES qadomain.net nfs/<nesthostname>.<domain name> For example: nfs/es qadomain.net root/<nesthostname>.<domain name> For example: root/es qadomain.net host/<nesthostname> For example: host/es host/<nesthostname>.<domain For example: 6 useraccountcontrol 4130 Note If the domain you are joining is department.company.com, make sure to use that whole name in Step 7. Nexsan Unity 51

52 Delegating control to a non-administrator user account 4. In the distinguishedname attribute of the computer object, take note of the Organizational Unit names, in this format: OU=name1,OU=name2, etc. You will need this for Step 7. Note You can create a new OU at the root of the domain tree or use an existing user-defined OU. In the example below, you would use OU=Finance,OU=OU Repeat step 3 above for the computer object that you added for the 2nd controller node. 6. Configure Unity using the Nexsan Unity System Configuration wizard (if not already configured). 7. Join Unity to the Microsoft Active Directory Domain in Nexsan Unity. Make sure to use the same (whole) domain name as in Step 3. a. At the Configure User Authentication Mode step, click the Advanced button. b. Enter the Organizational Unit (OU) names obtained in Step 4. c. Select the Use pre-defined computer objects option. d. Click the Apply button. 8. After configuring Unity and successfully joining the system to the Microsoft Active Directory Domain, reset the useraccountcontrol attribute to for each Unity computer object that you added to the Active Directory Server: DONT_EXPIRE_PASSWORD WORKSTATION_TRUST_ACCOUNT. Delegating control to a non-administrator user account After creating a computer object in the Active Directory server, you must give full control to the non- Administrator user account for the selected Organization Unit (OU), so that this user can operate Unity in your Active Directory environment. Nexsan Unity NFS Interoperability Technical Guide v. 5.1 Unity 52

53 Chapter 6: Using Active Directory (AD) for NFS To delegate control: 1. To open Active Directory Users and Computers: a. Click Start then select Control Panel. b. Double-click Administrative Tools. c. Double-click Active Directory Users and Computers. To open Active Directory Users and Computers in Windows Server 2012, click Start, and type dsa.msc. 2. In the console tree, right-click the organizational unit (OU) for which you want to delegate control, under Active Directory Users and Computers\ domain node. 3. Click Delegate Control to start the Delegation of Control wizard. 4. Click Add and select the non-administrator user account used in the previous section. Click the Next button. Figure 6-1: Active Directory - Delegation of Control wizard: select a user 6 Nexsan Unity 53

54 Delegating control to a non-administrator user account 5. Select Create a custom task to delegate and click the Next button. Figure 6-2: Active Directory - Delegation of Control wizard: select tasks to delegate 6 6. Select This folder... and click the Next button. Figure 6-3: Active Directory - Delegation of Control wizard: select the task scope Nexsan Unity NFS Interoperability Technical Guide v. 5.1 Unity 54

55 Chapter 6: Using Active Directory (AD) for NFS 7. Give Full Control access to the non-administrator user account and click Next. Figure 6-4: Active Directory - Delegation of Control wizard: select permissions 8. Click Finish. Joining a Microsoft Active Directory domain using Unity The Unity Authentication service is preconfigured by default during initial system setup. Use this procedure if you want to instead join a Microsoft Active Directory domain. CAUTION: If Unity is currently connected to a domain, and you subsequently join Unity to a new domain, all file system-level access permissions are also removed, although file- and folder-level ACLs (CIFS) and permissions (NFS) remain unchanged. However, when you rejoin the previous domain that Unity was connected to, or if the new domain has the same set of user and/or group accounts as the previous domain, Unity restores Site and Storage Pool Administrators, as well as all file system-level access permissions on the system. CAUTION: Joining a new domain or rejoining a former domain If Kerberos is configured to access file systems, the Kerberos configuration gets disabled when unjoining a domain. After joining a new domain or rejoining an old domain, you must reconfigure Kerberos as described in Enabling Kerberos for accessing CIFS file systems on page 1. 6 Before you begin: Read the Microsoft Active Directory domain requirements on page 48. Nexsan Unity 55

56 Joining a Microsoft Active Directory domain using Unity Figure 6-5: Joining a Microsoft Active Directory domain 6 To join a Microsoft Windows Active Directory domain: 1. From the System menu, select Unity Systems. 2. Click Summary > User Authentication. 3. Select Microsoft Active Directory. The connection settings for Microsoft Active Directory display. 4. In the Active Directory Domain Name field, type the fully qualified domain name (FQDN) of the Microsoft Active Directory domain server that you want Unity to connect to. Note If you are integrating Unity in a multiple domain environment (Microsoft Active Directory forest implementation), and you want Nexsan Unity to display all users and groups from all domains, make sure to specify the domain name of the root, or top-level domain server of your network s Microsoft Active Directory implementation. 5. Optionally, in the Time Server field, type the IP address or the fully qualified domain name of the time server that you want Unity to synchronize its date and time with. A default time server is already defined. Note Unity supports multiple time servers: if you specify a time server in the Time Server field, we highly recommend that you specify at least two time servers; this ensures that date and time synchronization on Unity continues in the event that one of the time servers you specify is no longer available. To specify multiple time servers, use a comma to separate each entry, for example: tick.utoronto.ca,time.nrc.ca. 6. In the Domain user name and Domain password fields, type the user name and password of the domain administrator, or of a user that has administrative access to the Microsoft Active Directory server. For LM compatibility level, we recommend that you use the recommended level (2). The security level allows NTLMv1 client authentication, or NTLMv2 session security if the NFS server supports it. The Domain Controller accepts LM, NTLM, and NTLMv2 authentication. Nexsan Unity NFS Interoperability Technical Guide v. 5.1 Unity 56