IBM System Storage N series Clustered Data ONTAP … · If the terms Cluster-Mode or clustered Data...

IBM System Storage N series

Clustered Data ONTAP 8.2 MultiprotocolServer Configuration Express Guide

SC27-6409-00

��

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vAbout this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vSupported features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vWebsites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vGetting information, help, and service . . . . . . . . . . . . . . . . . . . . . . . . . . viBefore you call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viUsing the documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viHardware service and support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viFirmware updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viHow to send your comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Deciding whether to use this guide . . . . . . . . . . . . . . . . . . . . . . . . 1

Multiprotocol server configuration workflow . . . . . . . . . . . . . . . . . . . . 3Gathering network information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Adding the CIFS and NFS licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Creating an aggregate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Creating a multiprotocol Vserver . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Creating a volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Creating an SMB share . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Mapping UNIX and Windows user names . . . . . . . . . . . . . . . . . . . . . . . . . 10Mapping entries in the DNS server . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Assigning a data failover group to the data LIF . . . . . . . . . . . . . . . . . . . . . . . 13Opening the NFS export policy to all clients . . . . . . . . . . . . . . . . . . . . . . . . 13Testing SMB access from a Windows client . . . . . . . . . . . . . . . . . . . . . . . . . 14Testing NFSv3 access from a UNIX client . . . . . . . . . . . . . . . . . . . . . . . . . 15

Where to find additional information . . . . . . . . . . . . . . . . . . . . . . . 17

Copyright and trademark information . . . . . . . . . . . . . . . . . . . . . . 19Trademark information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

© Copyright IBM Corp. 2013 iii

iv IBM System Storage N series: Clustered Data ONTAP 8.2 Multiprotocol Server Configuration Express Guide

Preface

About this guideThis document applies to IBM N series systems running Data ONTAP, includingsystems with gateway functionality. If the terms Cluster-Mode or clustered DataONTAP are used in this document, they refer to the Data ONTAP features andfunctionality designed for clusters, which are different from 7-Mode and prior DataONTAP 7.1, 7.2, and 7.3 release families.

In this document, the term gateway describes IBM N series storage systems thathave been ordered with gateway functionality. Gateways support various types ofstorage, and they are used with third-party disk storage systems—for example,disk storage systems from IBM, HP®, Hitachi Data Systems®, and EMC®. In thiscase, disk storage for customer data and the RAID controller functionality isprovided by the back-end disk storage system. A gateway might also be used withdisk storage expansion units specifically designed for the IBM N series models.

The term filer describes IBM N series storage systems that either contain internaldisk storage or attach to disk storage expansion units specifically designed for theIBM N series storage systems. Filer storage systems do not support usingthird-party disk storage systems.

Supported featuresIBM System Storage N series storage systems are driven by NetApp Data ONTAPsoftware. Some features described in the product software documentation areneither offered nor supported by IBM. Please contact your local IBM representativeor reseller for further details.

Information about supported features can also be found on the N series supportwebsite (accessed and navigated as described in Websites).

WebsitesIBM maintains pages on the World Wide Web where you can get the latesttechnical information and download device drivers and updates. The followingweb pages provide N series information:v A listing of currently available N series products and features can be found at

the following web page:www.ibm.com/storage/nas/

v The IBM System Storage N series support website requires users to register inorder to obtain access to N series support content on the web. To understandhow the N series support web content is organized and navigated, and to accessthe N series support website, refer to the following publicly accessible web page:www.ibm.com/storage/support/nseries/This web page also provides links to AutoSupport information as well as otherimportant N series product resources.

v IBM System Storage N series products attach to a variety of servers andoperating systems. To determine the latest supported attachments, go to the IBMN series interoperability matrix at the following web page:

© Copyright IBM Corp. 2013 v

http://www.ibm.com/storage/nas/

http://www.ibm.com/storage/support/nseries/

www.ibm.com/systems/storage/network/interophome.htmlv For the latest N series hardware product documentation, including planning,

installation and setup, and hardware monitoring, service and diagnostics, see theIBM N series Information Center at the following web page:publib.boulder.ibm.com/infocenter/nasinfo/nseries/index.jsp

Getting information, help, and serviceIf you need help, service, or technical assistance or just want more informationabout IBM products, you will find a wide variety of sources available from IBM toassist you. This section contains information about where to go for additionalinformation about IBM and IBM products, what to do if you experience a problemwith your IBM N series product, and whom to call for service, if it is necessary.

Before you callBefore you call, make sure you have taken these steps to try to solve the problemyourself:v Check all cables to make sure they are connected.v Check the power switches to make sure the system is turned on.v Use the troubleshooting information in your system documentation and use the

diagnostic tools that come with your system.v Refer to the N series support website (accessed and navigated as described in

Websites) for information on known problems and limitations.

Using the documentationThe latest versions of N series software documentation, including Data ONTAPand other software products, are available on the N series support website(accessed and navigated as described in Websites).

Current N series hardware product documentation is shipped with your hardwareproduct in printed documents or as PDF files on a documentation CD. For thelatest N series hardware product documentation PDFs, go to the N series supportwebsite.

Hardware documentation, including planning, installation and setup, andhardware monitoring, service, and diagnostics, is also provided in an IBM N seriesInformation Center at the following web page:

publib.boulder.ibm.com/infocenter/nasinfo/nseries/index.jsp

Hardware service and supportYou can receive hardware service through IBM Integrated Technology Services.Visit the following web page for support telephone numbers:

www.ibm.com/planetwide/

Firmware updatesIBM N series product firmware is embedded in Data ONTAP. As with all devices,ensure that you run the latest level of firmware. Any firmware updates are postedto the N series support website (accessed and navigated as described in Websites).

vi IBM System Storage N series: Clustered Data ONTAP 8.2 Multiprotocol Server Configuration Express Guide

http://www.ibm.com/systems//storage/network/interophome.html

http://publib.boulder.ibm.com/infocenter/nasinfo/nseries/index.jsp

http://publib.boulder.ibm.com/infocenter/nasinfo/nseries/index.jsp

http://www.ibm.com/planetwide/

Note: If you do not see new firmware updates on the N series support website,you are running the latest level of firmware.

Verify that the latest level of firmware is installed on your machine beforecontacting IBM for technical support.

How to send your commentsYour feedback helps us to provide the most accurate and high-quality information.If you have comments or suggestions for improving this document, please sendthem by email to [email protected].

Be sure to include the following:v Exact publication titlev Publication form number (for example, GC26-1234-02)v Page, table, or illustration numbersv A detailed description of any information that should be changed

Preface vii

mailto:[email protected]

viii IBM System Storage N series: Clustered Data ONTAP 8.2 Multiprotocol Server Configuration Express Guide

Deciding whether to use this guide

This guide describes how to quickly set up CIFS and NFS services on a Vserver, inpreparation for configuring SMB and NFSv3 client access to files contained on theVserver.

You should use this guide in the following situations:v You want a standard configuration following IBM N series best practices.v You do not want information about all the available options or a lot of

conceptual background.v The cluster is already created and the cluster time is synchronized with an NTP

server.v Name services are provided by NIS or UNIX® local users, not by LDAP or

Kerberos.

If this guide is not suitable for your situation, you should see the followingdocumentation instead:v Clustered Data ONTAP Software Setup Guide (for new systems)v Clustered Data ONTAP System Administration Guide for Cluster Administrators (for

Vserver creation)v Clustered Data ONTAP File Access and Protocols Management Guide (for access

over NFSv3, NFSv4, and SMB, as well as information about LDAP andKerberos)

v OnCommand System Manager Help

Documentation is available from the IBM N series support website (accessed andnavigated as described in Websites).Related information:

IBM N series support website: www.ibm.com/storage/support/nseries

© Copyright IBM Corp. 2013 1

http://www.ibm.com/storage/support/nseries

2 IBM System Storage N series: Clustered Data ONTAP 8.2 Multiprotocol Server Configuration Express Guide

Multiprotocol server configuration workflow

Configuring both SMB/CIFS and NFS access involves adding protocol licenses;creating an aggregate, Vserver, volume, and share; mapping UNIX and Windowsnames; creating DNS entries; assigning failover ports to the data LIF; and openingthe export policy to all NFS clients. You can then test SMB and NFSv3 access.

Gathering network informationYou can use a worksheet to collect the information that you require to set upaccess for clients. You must obtain the IP addresses and other information aboutyour cluster and network from your storage and network administrators beforeyou begin.


Names

Plan the names that you must define when adding a server configuration.

Field Description Your value

Vserver name A name that is either a fully qualifieddomain name (FQDN) or followsanother convention that ensuresunique Vserver names across a cluster

CIFS server name A name for the CIFS server that allowsSMB clients to access files on theVserver

Share name A name for the CIFS/SMB share thatSMB clients map

Volume name A unique descriptive name for thevolume

DNS information

Gather the names of your site's DNS search domains and name servers, which youmust enter when you create the Vserver.


Search domains One through five domain names in theorder that they will be searched

Name servers One through three IP addresses of thedomain controllers serving DNS for theActive Directory that the Vserver willjoin

Logical interface (LIF) for data

Gather the following information about the network connection for data access,which you must enter when you create the Vserver.


IP address The address on the cluster that will beused for data access

Network mask The network mask and gateway for theLIFGateway

Home node The data port that the LIF will beassociated with and the node where thedata port will be located

Home port

For information about data ports for each hardware model, see the IBM SystemStorage N series Introduction and Planning Guide at the IBM N series support website(accessed and navigated as described in Websites).

Active Directory information

Gather the following information about your site's Windows Active Directory (AD)domain, which you must enter when you create the Vserver.



Active Directory The Windows Active Directory (AD)Domain for the storage system to join

AD administrative credentials A user account with privileges to jointhe Windows AD domain: the username and corresponding password

Network Information Service (NIS)

If your site uses NIS as a name server or for name mapping, gather the NISdomains and servers, which you must enter when you create the Vserver.

Field Host name or IP address

Primary NIS domain

NIS servers

Secondary domains(optional)

Adding the CIFS and NFS licensesYou must ensure that the cluster has a CIFS license and an NFS license. A CIFSlicense is required to enable SMB access to the cluster. An NFS license is requiredto enable NFS access to the cluster.

Before you begin

You must have the CIFS and NFS license keys.

About this task

This procedure is performed using System Manager.

Procedure1. From the home page, double-click the appropriate storage system.2. Expand the Cluster hierarchy in the left navigation pane.3. In the navigation pane, click Configuration > System Tools > Licenses.4. In the Licenses window, click Add.5. In the Add Licenses dialog box, enter the two software license keys, separated

by commas, and click Add. The Add licenses status window displays the list oflicenses that were added successfully. The window also displays the licensekeys of the licenses that were not added and the reason why the licenses werenot added.

6. Click Close.

Creating an aggregateYou create an aggregate to provide storage to one or more FlexVol volumes.Aggregates are made up of physical storage objects, such as HDDs and SSDs.

Multiprotocol server configuration workflow 5

About this task


Procedure1. From the home page, double-click the appropriate storage system.2. Expand either the Cluster or the Nodes hierarchy in the left navigation pane.3. In the navigation pane, click Storage > Aggregates.4. Click Create.5. In the Create Aggregate wizard, click Next.6. Optional: If you want to change the default name, specify a new name, such

as aggr2. The default aggregate name ends in a date and time stamp.

7. Accept the default value for RAID Type, and click Next. You can change theRAID type later if necessary.

8. In the Aggregate Details page, click Select disks.9. In the Change Disk Selection page, select the node on which you want to

create the aggregate, specify at least 5 disks in the Number of capacity disksto use field, and click Save and Close.

10. Click Create.11. Click Finish.

Results

The aggregate is created with the specified configuration and added to the list ofaggregates in the Aggregates window.

Creating a multiprotocol VserverYou must create the Vserver to contain the volume, CIFS server, NFS server, DNSconfiguration, and the logical interface (LIF) that is used to access data using SMB.

About this task


Procedure1. From the home page, double-click the appropriate storage system.2. Expand the Vservers hierarchy in the left navigation pane.3. In the navigation pane, select the cluster.4. Click Create.5. In the Create Vserver wizard window, specify the following Vserver details:


a. Specify the Vserver name, such as vs0.example.com.b. For the Data Protocols field, select CIFS and NFS. When you select both

CIFS and NFS protocols, the security style is set to NTFS.c. Optional: Select a different language other than the default C.UTF-8. The

language of the Vserver is the default language of all volumes created onthe Vserver.

You can change the data protocols, language, and security style later ifnecessary.

6. Specify the DNS configuration:a. Enter one or more domain names in the order that they will be searched.b. Enter the IP addresses of one or more name servers. You should use the

Windows Active Directory (AD) Domain Controller as the first domainname server.

7. Click Submit & Continue. The Vserver is created with the specifiedconfiguration.

8. In the Data LIF Configuration section, specify the following network details tocreate a data LIF:v IP address, network mask, and gateway that clients will use to access the

datav Node and data port with which the LIF is associated


9. Specify the following information to create the CIFS server:v A new name if you want the CIFS server to have a name different from its

containing Vserverv The FQDN of an Active Directory (AD) domain that the CIFS server can

joinv Organizational unit (OU) within the Active Directory domain to associate

with the CIFS serverBy default, this parameter is set to CN=Computers.

v Credentials of an administrative account that has sufficient privileges to addthe CIFS server to the OU

10. If your site uses NIS for name services or name mapping, specify the domainand IP addresses of the NIS servers.

11. Click Submit & Close. The CIFS and NFS servers are created with thespecified configuration.

12. Complete the wizard by clicking Skip and then OK.13. Verify that the new Vserver is configured as required:

a. Select the Vserver in the left navigation pane and confirm that it is in“Running” status.

b. In the navigation pane, click Storage > Volumes, select the root volume,and click Edit to verify the security style and default permissions. The rootvolume has NTFS security style; the UNIX permissions area is notrelevant. New volumes created on this Vserver will inherit the NTFSsecurity style of this root volume.


c. Verify that a network path exists to the data LIF on the Vserver byopening a command prompt on a client and pinging the IP address of thedata LIF. In a command window, enter ping 192.0.2.130, and confirm thatyou receive a reply.

Results

The Vserver is created with the following:v A CIFS server that belongs to the specified Active Directory domainv An NFS server that supports NFSv3v DNS configuredv A data LIF for client access to data over NFS and SMBv The default CIFS shares admin$ and ipc$.v A Windows local user (Administrator) and four Windows local groups

(BUILTIN\Administrators, BUILTIN\Backup Operators, BUILTIN\Power users,and BUILTIN\users)

v Three UNIX local users (nobody, pcuser, and root) and four UNIX local groups(daemon, nobody, pcuser, and root)The UNIX user “pcuser” is the default UNIX user for the CIFS server.

Creating a volumeYou must create a FlexVol volume to contain your data. Data must not be stored inthe root volume of the Vserver.

About this task


Procedure1. From the home page, double-click the appropriate storage system.2. Expand the Vservers hierarchy in the left navigation pane.3. In the navigation pane, select the Vserver and click Storage > Volumes.4. Click Create. The Create Volume dialog box is displayed.5. If you want to change the default name, specify a new name, such as vol1. By

default, the volume name ends in a date and time stamp.6. Select the aggregate that you created earlier for the volume.7. Specify the size of the volume.


8. Accept the default value for the Snapshot reserve.The default space reserved for Snapshot copies is five percent for NASvolumes.

9. Ensure that Storage Type is set to NAS.10. Click Create. The volume inherits the security style of the Vserver root

volume.11. In the Volume window, verify that the new volume is in the list.

Creating an SMB shareBefore SMB clients can access a volume, you must create an SMB share on thevolume.

About this task


Procedure1. From the home page, double-click the appropriate storage system.2. Expand the Vservers hierarchy in the left navigation pane.3. In the navigation pane, select the Vserver and click Storage > Shares.4. Click Create Share.5. Click Browse and select the volume that you created earlier.6. Specify a name for the new share.7. Provide a description for the share and click Create.

Results

The share is created with the access permissions set to Full Control for theEveryone group. You can modify the share permissions later if required.

Mapping UNIX and Windows user namesIf your site has both Windows and UNIX user accounts, you should use namemapping to ensure that Windows users can access files with UNIX file permissionsand to ensure that UNIX users can access files with NTFS file permissions. Namemapping can involve conversion rules and default users.


About this taskv You should use this procedure only if your site does not have Windows and

UNIX users that map implicitly.Implicit name mappings exist when you maintain two sets of user accounts—aset of Windows users and a set of UNIX users—for the same set of users. Thiscan be done using NIS, LDAP, or local users. As long as the lowercase version ofthe Windows user name matches the corresponding UNIX user name, DataONTAP can translate between the two sets of accounts.

v This procedure is performed using System Manager.

Procedure1. Navigate to the Vserver:

a. From the home page, double-click the appropriate storage system.b. Expand the Vservers hierarchy in the left navigation pane.c. In the navigation pane, select the Vserver.

2. If you want to control or track access at an individual level, createname-mapping conversion rules that convert UNIX user accounts to Windowsuser accounts, and vice versa:a. Select Configuration > Local Users and Groups > Name Mapping.b. Click Add, retain the default Windows to UNIX direction, and then create a

mapping that produces a UNIX credential when a Windows user tries toaccess a file that uses UNIX file permissions. Mappings use regularexpressions to convert one user name to another. For information aboutname mapping conversion rules, see the OnCommand System Manager Help.

c. Click Add, select UNIX to Windows direction, and then create thecorresponding mapping that produces a Windows credential when a UNIXuser tries to access a file that has NTFS file permissions.

d. Repeat steps 2b and 2c to map all of the domains and names on theselected Vserver. The position of each rule determines the order in whichthe rules are applied.

The following example converts any Windows user in the ENG domain to aUNIX user with the same name, and vice versa.

3. Define a default Windows user that is used as the Windows credential when aUNIX user accesses a file with NTFS file permissions and neither implicit namemapping nor name-mapping conversion rules map the user to a specificWindows user:a. If you use a name service, use the name service to create a Windows user

account for unmapped UNIX users.


b. If you use Windows users that are local to the Vserver, select Configuration> Local Users and Groups > Windows and create a user account forunmapped UNIX users.

c. Set the default Windows user by selecting Configuration > Protocols >NFS > Edit, and entering the user name that you created for unmappedUNIX users.

You can create a local Windows user named “unixusers” and set it as thedefault Windows user.

4. Define a default UNIX user that is used as the UNIX credential when aWindows user accesses a file with UNIX file permissions and neither implicitname mapping nor name-mapping conversion rules map the user to a specificUNIX user:a. If you use a name service, use the name service to create a UNIX user

account for unmapped Windows users.b. If you use UNIX users that are local to the Vserver, select Configuration >

Local Users and Groups > UNIX and then create a user account forunmapped Windows users.

c. Set the default UNIX user by selecting Configuration > Protocols > CIFS >Options and entering the user name that you created for unmappedWindows users.

Alternatively, you can use the default value for the default UNIX user, which isthe “pcuser” user. You can create a local UNIX user named “winusers” and setit as the default UNIX user.

What to do nextv If you set NTFS file permissions on files or folders, you should set permissions

for the default Window user.v If you set UNIX file permissions on files or folders, you should set permissions

for the default UNIX user.

Mapping entries in the DNS serverYour site's DNS server must have an entry pointing the CIFS server name to the IPaddress of the data LIF so that Windows users can map a drive to the CIFS servername.

Before you beginv You must know the IP address of the data LIF and the name of the CIFS server.v You must have administrative access to your site's DNS server.

If you do not have administrative access, you must ask the DNS administratorto perform this task.

About this task

This procedure is performed on your site's DNS server.

Procedure

Create forward (A - Address record) and reverse (PTR - Pointer record) lookupentries to map the CIFS server name and the IP address of the data LIF.


Assigning a data failover group to the data LIFYou must assign a failover group to the LIF for the Vserver so that an appropriateport is automatically associated with the LIF if its existing port has acommunication failure.

Before you beginv You must know the name of the Vserver and its LIF.

A LIF that is created in System Manager is automatically given a name thatmatches the name of the Vserver followed by the “_cifs_nfs_lif1” string. You cansee the LIFs of a Vserver by selecting Configuration > Network > NetworkInterfaces.

v The cluster must already have a user-defined failover group for data ports, andyou must know the name of the failover group.For instructions about how to create such a failover group, see the NAS ExpressSetup Guide for N6200 Systems or NAS Express Setup Guide for N7x50T Systems.To see existing failover groups, you can use the network interfacefailover-groups show command.

About this task

This procedure is performed from the Data ONTAP command line.

Procedure1. Enable the data LIF to use the data failover group by using the network

interface modify command with the -vserver and -lif parameters. Thefollowing command enables the data failover group for thevs0.example.com_cifs_lif1 LIF of the vs0.example.com Vserver:

cluster1::> network interface modify -vserver vs0.example.com -lifvs0.example.com_cifs_lif1 -failover-group data

2. Verify that the failover group is enabled on the LIF by using the networkinterface show command with the -vserver and -failover parameters. Thefollowing output displays the ports in the “data” failover group for thevs0.example.com Vserver:

cluster1::> network interface show -vserver vs0.example.com -failoverLogical Home Failover Failover

Vserver Interface Node:Port Policy Group-------- --------------- --------------------- --------------- ---------------vs0.example.com

vs0.example.com_cifs_lif1 cluster1-01:e1bnextavail data

Failover Targets: cluster1-01:e1b, cluster1-01:e2bcluster1-02:e1b, cluster1-02:e2bcluster1-03:e1b, cluster1-03:e2bcluster1-04:e1b, cluster1-04:e2b

Opening the NFS export policy to all clientsYou must add a rule to the default export policy to allow all clients access throughNFSv3. Without such a rule, all NFS clients are denied access to the Vserver andits volumes.


About this taskv You should open all NFS access in the default export policy, and later restrict

access to individual volumes by creating custom export policies for individualvolumes.

v This procedure is performed using System Manager.

Procedure1. From the home page, double-click the appropriate storage system.2. Expand the Vservers hierarchy in the left navigation pane.3. In the navigation pane, select the Vserver and click Policies > Export Policies.4. Select the default export policy and click Add Rule.5. In the Create Export Rule dialog box, create a rule that opens access to all

clients for NFS clients:a. In the Client Specification field, enter 0.0.0.0/0 so that the rule applies to

all clients.b. Retain the default value as 1 for the rule index.c. Select NFSv3.d. Retain the default permissions, which allow all users all levels of access.e. Click OK.

Results

NFSv3 clients can now access any volumes created on the Vserver.

Testing SMB access from a Windows clientYou should verify that you have configured SMB correctly by using a Windowsclient to access the SMB share and write data to the share.


Before you begin

You must be logged in as a Windows user that is authenticated to the ActiveDirectory domain that includes the Vserver.

About this task

This procedure is performed on a Windows client.

Procedure1. Use Windows Explorer to map a drive to the CIFS server name followed by the

name of share that you created. If the CIFS server is named vs0.example.comand the share is named Test, you should enter the following command:\\vs0.example.com\Test

2. On the newly created drive, create a test file. Use Notepad to create a text filecalled test.txt. The file is saved successfully to the SMB share.

3. Delete the test file.

Testing NFSv3 access from a UNIX clientAfter you configure NFSv3 access to a Vserver, you should verify the configurationby logging in to an NFSv3 client and reading data from and writing data to theVserver.

Before you beginv You must have the login information for the root user.v You must have the name of the volume that you want to access.v You must have the IP address of the data LIF that you configured when

enabling NFS for the Vserver.v You must have the DNS name for the data LIF, if you created a DNS name

earlier.

Procedure1. Log in as the root user to a client system that you have configured for NFS

access.2. Enter cd /mnt/ to change the directory to the mount folder.3. Create and mount a new folder using the IP address of the Vserver:

a. Enter mkdir /mnt/folder to create a new folder.b. Enter mount -t nfs -o nfsvers=3,hard IPAddress:/volume_name

/mnt/folder to mount the volume at this new directory.c. Enter cd folder to change the directory to the new folder.

The following commands create a folder named test1, mount the vol1 volumeat the 192.0.2.130 IP address on the test1 mount folder, and change to the newtest1 directory:

host# mkdir /mnt/test1host# mount -t nfs -o nfsvers=3,hard 192.0.2.130:/vol1 /mnt/test1host# cd test1

4. Create a new file, verify that it exists, and write text to it:a. Enter touch filename to create a test file.b. Enter ls -l filename to verify that the file exists.


c. Enter cat >filename, type some text, and then press Ctrl+D to write text tothe test file.

d. Enter cat filename to display the content of the test file.e. Enter rm filename to remove the test file.f. Enter cd .. to return to the parent directory.

host# touch myfile1host# ls -l myfile1-rw-r--r-- 1 root root 0 Sep 18 15:58 myfile1host# cat >myfile1This text inside the first filehost# cat myfile1This text inside the first filehost# rm -r myfile1host# cd ..

5. If you created a DNS entry for the data LIF of the Vserver, repeat the previoustests with a folder that is mounted using the DNS name. The followingcommands create a folder named test2, mount it using the name of the Vserver,and test access by creating and writing to a file named myfile2:

host# mkdir /mnt/test2host# mount -t nfs -o nfsvers=3,hard vs0.example.com:/vol1 /mnt/test2host# cd test2host# touch myfile2host# ls -l myfile2-rw-r--r-- 1 root root 0 Sep 23 15:58 myfile2host# cat >myfile2This text inside the second filehost# cat myfile2This text inside the second filehost# rm rmyfile2

Results

You have confirmed that you have enabled NFS access to the Vserver.


Where to find additional information

After you have successfully tested SMB and NFS access from a client, you areready to configure file access. There are express guides to help you configure fileaccess, as well as additional reference guides and technical reports.

Express guides

You should continue to set up file access by using the following express guide,which is available from the IBM N series support website (accessed and navigatedas described in Websites).

Multiprotocol File Access Express GuideDescribes how to quickly configure SMB and NFSv3 access to the sameUNIX or NTFS security-style volume.

Reference guides

The following reference documentation, which is available from the IBM N seriessupport website (accessed and navigated as described in Websites), can help youfurther configure client access.

OnCommand System Manager HelpDescribes how to use System Manager to complete typical tasks.

Clustered Data ONTAP File Access and Protocols Management GuideDescribes how to configure and manage file access using SMB and NFSprotocols.

Clustered Data ONTAP Logical Storage Management GuideDescribes how to efficiently manage your logical storage resources usingvolumes, FlexClone volumes, files and LUNs, deduplication, compression,qtrees, and quotas.

Clustered Data ONTAP Network Management GuideDescribes how to connect your cluster to your Ethernet networks and howto manage logical interfaces (LIFs).

Clustered Data ONTAP System Administration Guide for Cluster AdministratorsDescribes general system administration, including how to manage nodesand Vservers.

Technical Reports

Note: These technical reports contain information about NetApp products thatIBM licenses and in some cases customizes. Technical reports might containinformation about models and features that are not supported by IBM.

Technical Report 4191: Best Practices Guide for Data ONTAP 8.2 Windows File ServicesDescribes setting up CIFS/SMB, including best practices andtroubleshooting information.

Technical Report 4067: Clustered Data ONTAP NFS Implementation GuideServes as an NFSv3 and NFSv4 operational guide and provides anoverview of the clustered Data ONTAP 8.2 operating system with a focuson NFSv4.


Technical Report 4073: Secure Unified Authentication with N series Storage Systems:Kerberos, NFSv4, and LDAP for User Authentication over NFS

Explains how to configure clustered Data ONTAP for use with UNIX-basedKerberos version 5 (krb5) servers for NFS storage authentication andWindows Server Active Directory (AD) as the KDC and LightweightDirectory Access Protocol (LDAP) identity provider.

Technical Report 3580: NFSv4 Enhancements and Best Practices Guide: Data ONTAPImplementation

Describes the best practices that should be followed while implementingNFSv4 components on AIX, Linux®, or Solaris clients attached to systemsrunning Data ONTAP.

Related information:

IBM N series support website: www.ibm.com/storage/support/nseries

Technical Report 4191: Best Practices Guide for Data ONTAP 8.2 Windows FileServices

Technical Report 4067: Clustered Data ONTAP NFS Implementation Guide

Technical Report 4073: Secure Unified Authentication with N series StorageSystems: Kerberos, NFSv4, and LDAP for User Authentication over NFS

Technical Report 3580: NFSv4 Enhancements and Best Practices Guide: DataONTAP Implementation


http://www.ibm.com/storage/support/nseries

http://www.netapp.com/us/media/tr-4191.pdf







Copyright and trademark information

This section includes copyright and trademark information, and important notices.

Copyright information

Copyright ©1994 - 2013 NetApp, Inc. All rights reserved. Printed in the U.S.A.

Portions copyright © 2013 IBM Corporation. All rights reserved.

US Government Users Restricted Rights - Use, duplication or disclosure restrictedby GSA ADP Schedule Contract with IBM Corp.

No part of this document covered by copyright may be reproduced in any form orby any means—graphic, electronic, or mechanical, including photocopying,recording, taping, or storage in an electronic retrieval system—without priorwritten permission of the copyright owner.

References in this documentation to IBM products, programs, or services do notimply that IBM intends to make these available in all countries in which IBMoperates. Any reference to an IBM product, program, or service is not intended tostate or imply that only IBM's product, program, or service may be used. Anyfunctionally equivalent product, program, or service that does not infringe any ofIBM's or NetApp's intellectual property rights may be used instead of the IBM orNetApp product, program, or service. Evaluation and verification of operation inconjunction with other products, except those expressly designated by IBM andNetApp, are the user's responsibility.

No part of this document covered by copyright may be reproduced in any form orby any means—graphic, electronic, or mechanical, including photocopying,recording, taping, or storage in an electronic retrieval system—without priorwritten permission of the copyright owner.

Software derived from copyrighted NetApp material is subject to the followinglicense and disclaimer:

THIS SOFTWARE IS PROVIDED BY NETAPP “AS IS” AND WITHOUT ANYEXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR APARTICULAR PURPOSE, WHICH ARE HEREBY DISCLAIMED. IN NO EVENTSHALL NETAPP BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUTNOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVERCAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IFADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

NetApp reserves the right to change any products described herein at any time,and without notice. NetApp assumes no responsibility or liability arising from theuse of products described herein, except as expressly agreed to in writing by


NetApp. The use or purchase of this product does not convey a license under anypatent rights, trademark rights, or any other intellectual property rights of NetApp.

The product described in this manual may be protected by one or more U.S.A.patents, foreign patents, or pending applications.

RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by thegovernment is subject to restrictions as set forth in subparagraph (c)(1)(ii) of theRights in Technical Data and Computer Software clause at DFARS 252.277-7103(October 1988) and FAR 52-227-19 (June 1987).

Trademark information

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks ofInternational Business Machines Corporation in the United States, other countries,or both. A complete and current list of other IBM trademarks is available on theWeb at http://www.ibm.com/legal/copytrade.shtml

Linux is a registered trademark of Linus Torvalds in the United States, othercountries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks ofMicrosoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and othercountries.

NetApp, the NetApp logo, Network Appliance, the Network Appliance logo,Akorri, ApplianceWatch, ASUP, AutoSupport, BalancePoint, BalancePoint Predictor,Bycast, Campaign Express, ComplianceClock, Cryptainer, CryptoShred, CyberSnap,Data Center Fitness, Data ONTAP, DataFabric, DataFort, Decru, Decru DataFort,DenseStak, Engenio, Engenio logo, E-Stack, ExpressPod, FAServer, FastStak,FilerView, Flash Accel, Flash Cache, Flash Pool, FlashRay, FlexCache, FlexClone,FlexPod, FlexScale, FlexShare, FlexSuite, FlexVol, FPolicy, GetSuccessful, gFiler, Gofurther, faster, Imagine Virtually Anything, Lifetime Key Management, LockVault,Mars, Manage ONTAP, MetroCluster, MultiStore, NearStore, NetCache, NOW(NetApp on the Web), Onaro, OnCommand, ONTAPI, OpenKey, PerformanceStak,RAID-DP, ReplicatorX, SANscreen, SANshare, SANtricity, SecureAdmin,SecureShare, Select, Service Builder, Shadow Tape, Simplicity, Simulate ONTAP,SnapCopy, Snap Creator, SnapDirector, SnapDrive, SnapFilter, SnapIntegrator,SnapLock, SnapManager, SnapMigrator, SnapMirror, SnapMover, SnapProtect,SnapRestore, Snapshot, SnapSuite, SnapValidator, SnapVault, StorageGRID,StoreVault, the StoreVault logo, SyncMirror, Tech OnTap, The evolution of storage,Topio, VelocityStak, vFiler, VFM, Virtual File Manager, VPolicy, WAFL, Web Filer,and XBB are trademarks or registered trademarks of NetApp, Inc. in the UnitedStates, other countries, or both.

All other brands or products are trademarks or registered trademarks of theirrespective holders and should be treated as such.

NetApp is a licensee of the CompactFlash and CF Logo trademarks.

NetApp NetCache is certified RealSystem compatible.


Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe on any IBM intellectual property rightmay be used instead. However, it is the user's responsibility to evaluate and verifythe operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not give youany license to these patents. You can send license inquiries, in writing to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, N.Y. 10504-1785U.S.A.

For additional information, visit the web at:http://www.ibm.com/ibm/licensing/contact/

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of expressor implied warranties in certain transactions, therefore, this statement may notapply to you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM web sites are provided forconvenience only and do not in any manner serve as an endorsement of those websites. The materials at those web sites are not part of the materials for this IBMproduct and use of those web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environments may


vary significantly. Some measurements may have been made on development-levelsystems and there is no guarantee that these measurements will be the same ongenerally available systems. Furthermore, some measurement may have beenestimated through extrapolation. Actual results may vary. Users of this documentshould verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

If you are viewing this information in softcopy, the photographs and colorillustrations may not appear.


Index

Aabout this guide

deciding whether to use 1access

testing SMB configuration 15verifying for NFSv3 15

additional informationoptional tasks 17

aggregatescreating 6

audiencefor the guide 1

authenticationverifying 15

CCIFS

adding license 5additional documentation on 17mapping user names 11optional tasks 17setup overview 3worksheet to gather setup information 4

CIFS servermapping in the DNS server 12

CIFS sharescreating 10

client accessallowing access through NFSv3 14

copyright and trademark information 19copyright information 19creating

aggregates 6CIFS/SMB shares 10FlexVol volumes 9Vservers 6

Ddata LIFs

assigning failover groups 13DNS

creating entries 12mapping the data LIF 12

documentationadditional information about file access 17file access

additional documentation on 17

Eexport policies

adding rules 14express guides

additional documentation 17CIFS/SMB server configuration workflow 3NFS server configuration workflow 3requirements for setting up NFS service 1

express guides (continued)requirements for setting up SMB service 1requirements for using Multiprotocol Server Configuration

Express Guide 1

Ffailover groups

assigning to LIFs 13FlexVol volumes

creating 9

Llicenses

adding for CIFS 5adding for NFS 5

LIFsassigning failover groups 13mapping the data LIF on the DNS server 12

Mmapping

data LIF on the DNS server 12user names on different platforms 11

multiprotocol accessadditional documentation on 17enabling 17

Nnext steps

optional tasks 17NFS

adding license 5additional documentation on 17mapping user names 11optional tasks 17requirements for using Multiprotocol Server Configuration

Express Guide to set up the NFS service 1setup overview 3verifying access with authentication 15worksheet to gather setup information 4

NFSv3allowing client access 14

notices 21Notices 21

Pports

failing over 13

Ssetup

CIFS, overview of 3


setup (continued)NFS, overview of 3

sharescreating, CIFS/SMB 10

SMBadditional documentation on 17requirements for using Multiprotocol Server Configuration

Express Guide to set up the SMB service 1SMB shares

creating 10verifying access to 15

Ttechnical reports

additional documentation 17testing

SMB share access 15trademark information 20

UUNIX

mapping users to Windows 11users

mapping names to different platforms 11

Vvolumes

creating 9Vservers

creating to support NFS 6creating to support SMB 6worksheet to gather configuration information 4

WWindows

mapping users to UNIX 11worksheets

to gather cluster and network information 4


��

NA 210-06365_A0, Printed in USA

SC27-6409-00

Date post:	21-Aug-2018
Category:	Documents
Upload:	phamcong
View:	225 times
Download:	4 times

IBM System Storage N series Clustered Data ONTAP … · If the terms Cluster-Mode or clustered Data...

Documents