Basic NetApp Configuration and Administration Part … · Basic NetApp Configuration and ... Do Not Distribute. E-2 Basic NetApp Configuration and Administration ... all of the exercise

NETAPP UNIVERSITY

Basic NetApp Configuration and Administration Part 1 Self-paced Lab Course ID: CRS-0004236-01-A Content Version: 1.0

NetApp University - Do Not Distribute

E-2 Basic NetApp Configuration and Administration Self-paced Lab, Part 1: Welcome

© 2015 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.

ATTENTION

The information contained in this course is intended only for training. This course contains information and activities that, while beneficial for the purposes of training in a closed, non-production environment, can result in downtime or other severe consequences in a production environment. This course material is not a technical reference and should not, under any circumstances, be used in production environments. To obtain reference materials, refer to the NetApp product documentation that is located at http://now.netapp.com/.

COPYRIGHT

© 2015 NetApp, Inc. All rights reserved. Printed in the U.S.A. Specifications subject to change without notice.

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

U.S. GOVERNMENT RIGHTS

Commercial Computer Software. Government users are subject to the NetApp, Inc. standard license agreement and applicable provisions of the FAR and its supplements.

TRADEMARK INFORMATION

NetApp, the NetApp logo, Go Further, Faster, ASUP, AutoSupport, Campaign Express, Customer Fitness, CyberSnap, Data ONTAP, DataFort, FilerView, Fitness, Flash Accel, Flash Cache, Flash Pool, FlashRay, FlexCache, FlexClone, FlexPod, FlexScale, FlexShare, FlexVol, GetSuccessful, LockVault, Manage ONTAP, Mars, MetroCluster, MultiStore, OnCommand, ONTAP, ONTAPI, RAID DP, SANtricity, SecureShare, Simplicity, Simulate ONTAP, Snap Creator, SnapCopy, SnapDrive, SnapIntegrator, SnapLock, SnapManager, SnapMirror, SnapMover, SnapProtect, SnapRestore, Snapshot, SnapValidator, SnapVault, StorageGRID, Tech OnTap, and WAFL are trademarks or registered trademarks of NetApp, Inc. in the United States and/or other countries.

Other product and service names might be trademarks of NetApp or other companies. A current list of NetApp trademarks is available on the Web at http://www.netapp.com/us/legal/netapptmlist.aspx.


http://www.netapp.com/us/legal/netapptmlist.aspx

E1-1 Self-Paced Lab (SPL) Part 1: Exercise 1


SELF-PACED LABS: PART 1

EXERCISE 1: GETTING TO KNOW YOUR EQUIPMENT KIT

In this exercise, you log in to your exercise environment, ensure connectivity to the Data ONTAP cluster,

and set important configurations that you use throughout the exercises.

Access the Part 1 Self-Paced Lab (SPL) exercise environment.

OBJECTIVES

By the end of this exercise, you should be able to:

Ensure connectivity to a Data ONTAP cluster

Synchronize the date and time between a Windows domain and a Data ONTAP cluster

Ensure that required licenses are installed

Add DNS host records for a Data ONTAP cluster and other hosts to a Windows DNS Manager

STUDY-AID ICONS

These four icons are used throughout the exercise to identify steps that require your special attention.

Warning

You should follow all of the exercise steps, but misconfiguring steps labeled with this icon

might cause later steps to not work properly. Check this step carefully before moving

forward.

Attention

Steps or comments labeled with this icon should be reviewed carefully to save time, learn a

best practice, or avoid errors.

Information

Comments labeled with this icon provide additional information about the topic or

procedure.

Knowledge

Comments labeled with this icon provide reference material that will give additional

context that you may find useful.




SPL PART 1 EXERCISE EQUIPMENT DIAGRAM

Part 1 of your self-paced lab (SPL) exercise environment includes several virtual machines (VMs):

one Windows 2012 Server, one Data ONTAP cluster, and one Linux server. Only the hardware of

the Data ONTAP cluster virtual machine (VM) is simulated; The Data ONTAP software is authentic.

When you access your environment, you are automatically connected to the Windows 2012 Server.

From the desktop of the Windows server, you connect to the other servers in your exercise environment.

SYSTEM HOST NAME IP ADDRESS USER NAME PASSWORD

Windows 2012 Server w2k12 192.168.0.11 LEARN\Administrator Netapp123

Data ONTAP cluster cluster1 192.168.0.101 admin (case-sensitive) Netapp123

CIFS\NFS Data LIF svm1_data 192.168.0.111 LEARN\Administrator Netapp123

node 1 cluster1-01 192.168.0.91 admin (case-sensitive) Netapp123


Linux Server CentOS64 192.168.0.10 root Netapp123




TASK 1: ENSURE CONNECTIVITY TO YOUR DATA ONTAP CLUSTER

In this task, you familiarize yourself with the Windows 2012 Server desktop. You ensure connectivity

to the Data ONTAP cluster and verify the health of the Data ONTAP cluster.

STEP ACTION

1. Ensure that you see the Start page of your assigned Windows 2012 Server.

2. On the Windows 2012 Server Start page, scroll down and click the Desktop tile.




STEP ACTION

3. Verify that you see the desktop and that it contains the NetApp OnCommand System Manager

shortcut and the PuTTY program.

4. You use the NetApp OnCommand System Manager GUI to connect to the Data

ONTAP cluster. PuTTY is the application that you use to connect to the command-

line interface (CLI) of the Data ONTAP cluster and other remote servers. PuTTY

uses the Telnet and Secure Shell (SSH) protocols.

5. Double-click the PuTTY shortcut:




STEP ACTION

6. In the PuTTY Configuration dialog box, ensure that the cluster1-mgmt saved session is listed.

You use this session to connect to the CLI of the Data ONTAP cluster.

7. You can connect to the Data ONTAP cluster through the cluster1-01-mgmt saved

session. You can also connect through cluster1-01 (node 1) or cluster1-02 (node 2).

The list of saved sessions includes one called “7Node1”; however, the Data ONTAP

7-Mode storage system is not used in this exercise.

8. Double-click cluster1-mgmt:




STEP ACTION

9. At the Data ONTAP cluster login prompt, provide the cluster1 credentials:

login as: admin

Password: Netapp123

The Data ONTAP cluster CLI prompt and cursor appear.

10. If you have any difficulty logging in to the Data ONTAP cluster CLI, refer to this

table. Ensure that you are using the correct username and password in the correct

case (both are case-sensitive).



11. Verify that both nodes of the Data ONTAP cluster are healthy and eligible:

cluster show

12. If the health or eligibility of either node is listed as false, contact NetApp University

Support for assistance.




TASK 2: SYNCHRONIZE SYSTEM TIME FOR WINDOWS DOMAINS

In this task, you manually synchronize the system date and time on the Windows 2012 Server to the

system date and time in the Data ONTAP cluster. You set the time zone, date, and time of the Data

ONTAP cluster.

Time zones can differ across Microsoft Windows domains, as long as the date and time across the time

zones are synchronized. However, you might need to configure the time zone of a Data ONTAP cluster.

STEP ACTION

1. Display the configured time zone on the Data ONTAP cluster:

timezone

2. Etc/UTC

Coordinated Universal Time (UTC) is the primary time standard by which the world

regulates clocks and time. UTC is one of several replacements for Greenwich Mean

Time (GMT).

The zoneinfo database, which is a collaborative compilation of time zone information, has a

special area called “Etc.” The Etc area is for administrative zones, particularly for “Etc/UTC.”

3. Change the time zone from Etc/UTC to US/Pacific by entering this case-sensitive command:

timezone US/Pacific

4. Display the date and time on the Windows 2012 Server desktop by clicking the time and date

display in the lower-right corner of the desktop window:

5. Windows domains must be synchronized to within five minutes of all member

servers.

If the time of the Data ONTAP cluster is not synchronized with one of the domain

controllers, then the Data ONTAP cluster cannot join or remain joined to the Windows domain.

Without synchronization, computers in the Windows domain cannot access resources in the

Data ONTAP cluster, and resources in the cluster cannot access the Windows domain.




STEP ACTION

6. Click Change date and time settings:

7. Review the date, time, and time zone on the Windows 2012 Server:




STEP ACTION

8. Display the date, time, and time zone in the Data ONTAP cluster:

date

9. Compare the date and time on the Windows 2012 Server with the date and time in the

Data ONTAP cluster.




STEP ACTION

10. If the system date and time are not synchronized to within 5 minutes, enter the date

command plus the accurate date and time. Use the 24-hour time format with the

following syntax: date [YYYY][MM][DD][HH][MM]

Example command for changing the time to January 2, 7:34 PM. (Replace the date and

time with the current system date and time of the Windows 2012 Server system.)

date 201501021934

11. The date command ensures consistency across nodes by setting the date and time

on all nodes in the Data ONTAP cluster.




TASK 3: ENSURE THAT REQUIRED LICENSE CODES ARE INSTALLED ON STORAGE SYSTEMS

Many of the advanced features of clustered Data ONTAP require licenses to work. In later exercises, you

use several licensed features of clustered Data ONTAP. In this task, you ensure that the necessary licenses

have been installed.

STEP ACTION

1. In the cluster1-mgmt CLI, enter the following command:

license show

2. Ensure that these required license codes have been installed:

NFS

CIFS

iSCSI

SnapRestore

FlexClone

SnapManager Suite

The licenses enable features of Data ONTAP that are required for later exercises.

If any of these licenses are not installed, contact NetApp University Support

for assistance.




TASK 4: ADD DNS HOST RECORDS FOR THE DATA ONTAP CLUSTER AND LINUX SERVER

In this task, you manually add the names and IP addresses for the Data ONTAP cluster and the Linux

server as host records in the Windows 2012 DNS Manager, in the learn.netapp.local domain.

STEP ACTION

1. On your Windows 2012 desktop taskbar, click the Server Manager icon:

2. On the Server Manager dashboard, click Tools.

3. On the list of tools, click DNS:




STEP ACTION

4. In the DNS Manager window, ensure that the DNS navigation pane on the left shows the host

name of the Windows 2012 Server, W2K12:

5. Under the W2K12 server, expand the Forward Lookup Zones folder and select

learn.netapp.local.

The content of the learn.netapp.local folder appears in the pane on the right:




STEP ACTION

6. Select Action, New Host:

7. In the New Host dialog box, ensure that the new host is being created for the

learn.neapp.local domain:




STEP ACTION

8. Create a host record for the Data ONTAP cluster:

Name: cluster1

IP address: 192.168.0.101

Create associated pointer: Clear (used for reverse lookups)

Click Add Host.

The cluster1 host record is created.

9. Click OK:

10. Always add the Data ONTAP cluster name and cluster management logical interface

(LIF) IP address to register the Data ONTAP cluster name with the DNS Manager in

the domain. Registering computers with the DNS Manager enables you to avoid

issues that occur due to forgotten or changed IP addresses.




STEP ACTION

11. Create a host record for the Linux Server:

Name: CentOS64

IP address: 192.168.0.10

Click Add Host.

The CentOS64 host record is created.

12. The host name of the Linux server is CentOS64: the letter “O,” not the number zero.

13. Click OK.




STEP ACTION

14. After you have created the two host records successfully, click Done.

15. Verify that the host records for cluster1 and CentOS64 are now listed in the

learn.netapp.local folder:

16. Ensure that server names can be resolved to the correct IP addresses.

On the Windows 2012 Server desktop, open the CLI:




STEP ACTION

17. In the Windows 2012 Server CLI, verify that the DNS settings are correct:

ping cluster1

ping CentOS64


Data ONTAP cluster

cluster1 192.168.0.101 admin (case-sensitive)

Netapp123






STEP ACTION

18. If the ping requests could not find the cluster1 or CentOS64 host names, recheck the

DNS host records in Server Manager.

19. If the DNS host records are correct, yet you still cannot ping the host names, then

ensure that network settings for the Windows 2012 Server are configured with the

correct DNS server (192.168.0.11). To verify network setting, run this command in

the W2K12 Server CLI:

ipconfig /all

If the DNS server listed is not 192.168.0.11, contact NetApp University Support for assistance.

END OF EXERCISE





EXERCISE 2: WORKING WITH DATA ONTAP ADMINISTRATIVE INTERFACES

In this exercise, you use the command-line interface (CLI) and NetApp OnCommand System Manager

to configure a Data ONTAP cluster.


OBJECTIVES


List basic commands for managing a Data ONTAP cluster from the CLI

Add a two-node Data ONTAP cluster to be managed by OnCommand System Manager

Use OnCommand System Manager to configure the SNMP public community name for a Data

ONTAP cluster

STUDY-AID ICONS


Warning



forward.

Attention



Information


procedure.

Knowledge






EXERCISE EQUIPMENT DIAGRAM

Part 1 of your self-paced lab (SPL) exercise environment includes several virtual machines (VMs): one

Windows 2012 Server, one Data ONTAP cluster, and one Linux server. Only the hardware of the Data

ONTAP cluster virtual machine (VM) is simulated; The Data ONTAP software is authentic.

When you access your environment, you are automatically connected to the Windows 2012 Server. From

the desktop of the Windows server, you connect to the other servers in your exercise environment.

SYSTEM HOST NAME IP ADDRESS USERNAME PASSWORD










TASK 1: ENTER COMMANDS ON THE DATA ONTAP CLUSTER CLI

In this task, you enter CLI commands to review information about your Data ONTAP cluster.

STEP ACTION

1. If you are not already on the Windows 2012 Server desktop, click the Desktop tile:

2. On the Windows 2012 Server desktop, double click the PuTTY shortcut:




STEP ACTION

3. Double-click cluster1-mgmt to connect to the CLI of the Data ONTAP cluster:

4. At the Data ONTAP cluster login prompt, enter the credentials:

login as: admin

Password: Netapp123

The Data ONTAP cluster CLI prompt and cursor appear:

5. Display the version and mode of the Data ONTAP operating system:

version




STEP ACTION

6. From the Data ONTAP cluster CLI, enter ? and then press the enter key to show help:

7. The Data ONTAP cluster CLI does not recognize the commonly used help

command; you must use the question mark.

8. Quit the list of commands and return to the CLI prompt:

q




STEP ACTION

9. Display the sub-commands for the cluster command:

cluster ?

10. To display sub-commands for a command, enter the command followed

by a question mark.

11. Verify that the CLI is now focused on the cluster command.

12. At the cluster1::cluster> prompt, enter the create subcommand followed by ? to

display the list of cluster create variables:

create ?

13. You do not create a cluster at this time because this is just a tour of the basic cluster

commands. However, note that, to create a new cluster, you would enter values for

the -license and -clustername variables.

You exit the cluster create command by entering two periods [..] followed by the Enter key.

Try exiting the cluster create command in the next step and note that you receive an error

message.




STEP ACTION

14. To exit the cluster command and return to the cluster1::> CLI prompt, enter two periods

and then press the Enter key. Ignore the error message that appears (because Data ONTAP

expected you to add values for the –license code):

..

15. Display the index of Data ONTAP manual pages:

man

16. All Data ONTAP manual pages are stored in the cluster.




STEP ACTION

17. Press Enter to scroll through the man page index:

18. Close the man page index by pressing q.

(The “q” does not appear in the CLI, but the CLI prompt appears.)




STEP ACTION

19. Review the man page for the cluster command by entering the man command and the

index name (cluster):

man cluster




STEP ACTION

20. Press q to close the man page index.

(The “q” does not appear in the CLI, but the CLI prompt appears.)

21. Display the network command and sub commands:

network ?

22. The network command displays Ethernet and Fibre Channel (FC)

network configurations.

23. At the cluster1:: network> CLI prompt enter this command to display a list of logical

interfaces (LIFs) and their configuration details:

interface show




STEP ACTION

24. The network interface show command displays the names of storage virtual

machines (called Vservers), LIF names, LIF statuses, IP addresses, physical nodes,

and physical ports.

If the value in the Is Home column for a LIF is true, the LIF has not failed over to another

node; (the current port in the table is the home port for the LIF).




TASK 2: MANAGE THE DATA ONTAP CLUSTER WITH ONCOMMAND SYSTEM MANAGER

In this task, you add the Data ONTAP cluster to OnCommand System Manager. You then familiarize

yourself with the OnCommand System Manager GUI, which you use to manage Data ONTAP clusters

and storage systems.

STEP ACTION

1. On the Windows 2012 Server desktop, double-click the NetApp OnCommand System Manager

shortcut:

OnCommand System Manager opens:




STEP ACTION

2. In System Manager, click Add:

3. In the Add a System dialog box, specify the host name of the Data ONTAP cluster that

System Manager will manage (cluster1) and click the More drop-down button:

4. When you add a system, specify the cluster’s host name, rather than its IP address.

Otherwise, issues can arise if the IP address changes.

5. Enter the cluster credentials, which OnCommand System Manager uses to authenticate with

the cluster:

a. Select Credentials.

b. Enter the Data ONTAP cluster credentials:

User name: admin

Password: Netapp123

c. Click Add.




STEP ACTION

6. Verify that the Data ONTAP cluster has been added to OnCommand System Manager and the

status of the cluster is Up. Notice that the tab is labeled NetApp OnCommand System Manager.

Then double-click cluster1:

7. In the Model and System ID columns, the values are “-NA-“ (non-applicable),

because the model and system ID values are shown at the physical-node level, rather

than at the logical-cluster level. Later in this task, you review the logical and physical

levels of cluster management.




STEP ACTION

8. Sign in to cluster1:

a. You navigate to a new tab labeled “cluster1,” which appears next to the System Manager

tab.

b. Enter the Data ONTAP cluster credentials:

User name: admin

Password: Netapp123

c. Ensure that Save my credentials is selected.

d. Click Sign in.

The management page of the Data ONTAP cluster, cluster1, opens:

9. You can add other Data ONTAP clusters and Data ONTAP 7-Mode storage systems

for OnCommand System Manager to manage simultaneously.




STEP ACTION

10. In the left pane of OnCommand System Manager, find the three levels of management.

Open a level to do the following:

Cluster: select a cluster to manage

Vservers: select one of the storage virtual machines (SVMs) of a cluster and

manage volumes and other components of the SVM

Nodes: select a node in a cluster and manage the physical components of the node




STEP ACTION

11. Expand the Cluster level again by clicking the expansion button, and then expand cluster1.

Under Cluster, the main management categories appear: Storage, Configuration,

High Availability, and Diagnostics.

12. Identify the four reports that appear in the right pane (the pane labeled “cluster1”):

1. ______________________________________________________

2. ______________________________________________________

3. ______________________________________________________

4. ______________________________________________________

1.Properties, 2. Alarms, 3. System Alerts, 4. Storage




STEP ACTION

13. In the left pane, at the Cluster level, expand Storage and Configuration:

14. Under Storage, click Aggregates.

In the right pane, the aggregates of all of the nodes in the cluster appear:

15. Under Storage, click Disks.




STEP ACTION

16. In the right pane, widen the Name column so that you can read the names of the disks,

and then use the scroll bar on the right to scroll down the list.

You can see all of the disks of all of the nodes in the cluster.

17. The name of a disk begins with the name of the node where the disk resides.

18. In the left pane, under Configuration, expand System Tools and click DateTime.

19. In the right pane, click the Edit button.

The Edit DateTime dialog box appears. From this dialog box, you can set the date, the time,

or the time zone, or add Network Time Protocol (NTP) servers.

20. Click Cancel.

The Edit DateTime dialog box closes.




STEP ACTION

21. Collapse the Vservers level.




STEP ACTION

22. Expand the Nodes level and expand cluster1.

a. How many nodes are joined to the cluster1 cluster? __________

b. What is the model name of both cluster1-01 and cluster1-02? __________

c. What is the system ID of both cluster1-01 and cluster1-02?__________

23. Still at the Nodes level, under cluster1, expand cluster1-01:

a.2 nodes; b. SIMBOX; c. 4044744




STEP ACTION

24. Expand Storage and Configuration:

25. Under Storage, click Aggregates.

You should see only the aggregate that belongs to the cluster1-01 node:

26. You can manage a Data ONTAP cluster at any of the three levels

Cluster level: All resources of all nodes can be configured.

Vservers level: SVMs, volumes, shares, policies can be configured.

Nodes level: The components of each physical node are shown separately.

27. Under Storage, click Disks.




STEP ACTION

28. Widen the Name column and scroll to the bottom of the list of disks.

You see only the disks that belong to the cluster1-01 node:

29. Under Configuration, click Ports/Adapters.

On the Ethernet Ports tab, you see the physical ports that belong to the cluster1-01 node:

30. Review the buttons on the toolbar of the Ethernet Ports tab: Create Interface Group, Create

VLAN, Edit, Delete, and Refresh.




STEP ACTION

31. An interface group is a configuration that joins physical interfaces that will be used as

a group, either to increase the bandwidth of a logical network interface or to provide

failover.

VLAN stands for virtual LAN. You can configure a switch in your network to have more than

one network address, thereby separating traffic to reduce network congestion and the number

of network errors. If you have a VLAN, click Create VLAN to create a logical interface that

is configured to belong to the network address of the VLAN.

32. In the Ports/Adapters pane, click FC/FCoE Adapters.

The built-in FC adapter cards are online and ready to be configured for a storage area network

(SAN) environment:

33. Click the NetApp OnCommand System Manager tab to return to the System Manager

home page:




TASK 3: CONFIGURE SNMP FOR THE DATA ONTAP CLUSTER

In this task, you add the SNMP community name “public.”

STEP ACTION

1. On the System Manager home page, click Refresh.

The value in the Status field is No SNMP Response:

2. OnCommand System Manager uses the SNMP protocol to discover and collect data

from storage virtual machines (SVMs) in the Data ONTAP cluster. Examples of the

data collected by SNMP are Vserver names, Vserver aggregates, allowed protocols,

and Vserver states.

3. At the top of the window, click the cluster1 tab:




STEP ACTION

4. In the navigation pane on the left, expand Cluster:

5. Expand cluster1, Configuration, and System Tools, and then click SNMP.

The SNMP management pane opens:




STEP ACTION

6. In the SNMP pane, click Edit:

7. In the Edit SNMP Settings dialog box, under Community Names, click Add:




STEP ACTION

8. In the text box that appears, enter the community name public. Then click OK.

9. In production environments, using the well-known community name “public” might

not be secure.

10. Click OK:

The Edit SNMP Settings dialog box closes.




STEP ACTION

11. Verify that in the SNMP pane, in the Community Names field, you can see the name “public.”

OnCommand System Manager can now discover and collect data from SVMs (also referred

to as Vservers).

12. You should now be able to navigate the Data ONTAP cluster CLI and the

OnCommand System Manager GUI.

The Status column on the OnCommand System Manager home page might

continue to report “No SNMP Response”. You can ignore this message.

END OF EXERCISE




SELF-PACED LAB: PART 1

EXERCISE 3: HARDWARE BASICS AND MANAGING PHYSICAL COMPONENTS

In this exercise, you use the Data ONTAP CLI and OnCommand System Manager to explore hardware

components such as storage, disks, ports, and adapters.


OBJECTIVES


Use OnCommand System Manager to display hardware components

Use CLI commands to display hardware components

STUDY-AID ICONS


Warning



forward.

Attention



Information


procedure.

Knowledge






















TASK 1: USE ONCOMMAND SYSTEM MANAGER TO INVESTIGATE HARDWARE COMPONENTS

STEP ACTION

1. If you have not yet opened the Windows 2012 Server desktop, ensure that you are on the

Windows 2012 Server Start page and click the Desktop tile:




STEP ACTION

2. If OnCommand System Manager is open and you are logged in to the Data ONTAP cluster

management page, skip to Step 5. Otherwise, on the Windows 2012 Server desktop, double-

click the NetApp OnCommand System Manager shortcut:

3. On the OnCommand System Manager home page, double-click cluster1:




STEP ACTION

4. Provide cluster1 credentials:

User name: admin

Password: Netapp123

Click Sign in.

The Data ONTAP cluster management page opens.

5. Expand Nodes:




STEP ACTION

6. Expand cluster1, cluster1-01, and then Storage. Aggregates and Disks are listed.

Click Aggregates:

7. Notice that the Details, Volumes, and Disk Layout tabs apear at the bottom of the Aggregate

pane on the right. On the Details tab, aggregate, RAID group, and disk information is displayed.

8. Aggregates are created at the Data ONTAP cluster level, but the disks that form

the aggregates are physically attached to nodes. The default RAID type that

Data ONTAP uses is RAID-DP (double-parity RAID). You can also configure

an aggregate with the RAID 4 or single-parity RAID.




STEP ACTION

9. At the bottom of the Aggregates pane, click the Volumes tab.

10. On the Volumes tab, volumes that are assigned to an aggregate are listed. In the

Vserver column for a volume is the name of the storage virtual machine (SVM)

in which the volume was created. Available space in the aggregate and available

space that was assigned to the volume are displayed. From the space information,

you can decide whether to add disks to an aggregate or change space allocation for a volume.

11. In the top part of the Aggregates pane, select aggr0. (The top of the pane and aggr0 is not shown

in the screen shot.) At the bottom of the pane, as shown, click the Disk Layout tab.

You can then review the disk layout within the aggr0 aggregate:




STEP ACTION

12. On the Disk Layout tab, you can see detailed information about disks that belong

to an aggregate.

plex0: If an aggregate is mirrored, two plexes are listed: plex0 and plex1. The aggr0

aggregate is not mirrored, so only plex0 is listed.

rg0: The disks of an aggregate are divided into RAID groups. RAID stands for Redundant Array

of independent Disks.

Each RAID group contains data disks and parity disks. RAID groups help preserve data when

disks fail. If one or two of the disks fail in a RAID group, the data is restored from the remaining

disks and the parity disks of the RAID group.

The aggr0 aggregate contains only three disks. The RAID type is RAID-DP; two of the disks in

agg0 are parity disks: parity and dparity.

13. In the navigation pane on the left, under Storage, select Disks.

All disks in shelves that are physically attached to the node are listed in the right pane:

14. Select a spare disk and review the zeroing status and broken details shown in the Properties

section:




STEP ACTION

15. In the Disks pane, you can see all of the disks by name, state, and size. Before you

create an aggregate or add disks to an existing aggregate, monitor the health of all

disks in this pane. In the Properties section, ensure that no disks are listed as broken

and that all spare disks have been zeroed.

If one disk has not been zeroed, then the operations to create an aggregate or add a disk are

delayed while the Data ONTAP operating system first writes a zero to every block of the disks.

16. Review the information at the Nodes level and answer the following question:

Which of the two components under Storage (Aggregates or Disks) is the physical component

and which is the logical component?

Physical: ___________

Logical: __________

17. Examine the information in the Disks pane and answer these questions:

a. Which disk states are reported for the disks in cluster1-01? (Select all that apply.)

parity

dparity

data

spare

broken

b. Which of the four types of disks are attached to the cluster nodes? (Select all that apply.)

SAS

ATA

SSD

FC-AL

18. You can review the physical network ports and adapters at the Node level; however,

you create logical interfaces (LIFs) at the Cluster level. LIFs are located at the

physical network ports or adapters of physical nodes.

Answer: Physical: Disks; Logical: Aggregates

Answer: a. all except “broken”; b. FC-AL and SSD




STEP ACTION

19. At the Nodes level, in cluster1, Configuration, click Ports/Adapters:




STEP ACTION

20. On the Ethernet Ports tab, note the physical names of the Ethernet ports: e0a, e0b, and so on.

21. Ethernet port names include the slot number and the letter of the port on the

adapter. For example, e0a is a motherboard port and e3b is a port on an adapter

in expansion slot 3.

22. In the Ports/Adapters pane, click the FC/CoE Adapters tab.




STEP ACTION

23. Answer these questions:

Which two types of network adapters are on the two tabs in the Ports/Adapters pane?

__________

__________

a. How many Ethernet ports are available on the cluster1-01 node? ______

b. How many FC adapters are available on the cluster1-01 node? _____

c. Which role has been assigned to physical port e0f? ______________________________

Answers: a. Ethernet ports and Fibre Channel (FC) or Fibre Channel over Ethernet (FCoE) adapters; b. 6 Ethernet ports; c. 5 FC adapters; d. Node Management




TASK 2: USE CLI COMMANDS TO INVESTIGATE HARDWARE COMPONENTS

In this task, you use cluster-level CLI commands to explore hardware components such as storage,

disks, ports, and adapters.

STEP ACTION

1. On the Windows 2012 Desktop, double-click PuTTY.

Double-click cluster1-mgmt to connect to the Data ONTAP cluster CLI:

2. At the Data ONTAP cluster login prompt, enter the cluster1 credentials:

login as: admin

Password: Netapp123




STEP ACTION

3. Enter this command:

cluster show

The values in the Health and Eligibility columns for all nodes should be true, indicating that

the nodes are joined to the cluster.

4. Display the serial number of the cluster:

cluster identity show

5. Enter the storage command with a “?” and then press the Enter key to display its sub

commands:

storage ?

6. In the CLI of Data ONTAP clusters, there are cluster-level and node-level

commands. These exercises focus exclusively on cluster-level CLI commands.

Notice that the CLI prompt is now focused on the storage command: cluster1:: storage>




STEP ACTION

7. At the CLI storage prompt, use the disk show command to list all of the disks on all of

the nodes of the Data ONTAP cluster:

cluster1::storage> disk show

8. When you run the storage disk show command this information is shown

for all disks:

Disk name

Usable size

Shelf

Bay

Disk type

Position in the RAID group

Node that owns the disk

Aggregate to which the disk belongs (if the disk is not a spare)




STEP ACTION

9. Press Enter to scroll down the list of disks one line at a time until you see disks that belong

to cluster1-02:

10. Press q:

11. Return from the cluster1::storage> prompt to the regular cluster1::> prompt by

entering this command:

..

12. Initialize all of the spares of the cluster:

storage disk zerospares




STEP ACTION

13. You should use the storage disk zerospares command to periodically

initialize spares.

When you destroy an aggregate, the disks that were formerly a part of the

aggregate still have data written to them. To use the disks in a different aggregate, you

must initialize them.

To initialize disks, the system writes a zero in every block on the disk. The process is

referred to as “zeroing” the disks. Zero disks to prepare for adding disks to aggregates

in a Data ONTAP cluster.

14. List physical and logical interface information for the Data ONTAP cluster:

cluster1::> network interface show

15. In clustered Data ONTAP, the physical network interfaces are not directly configured

with IP addresses. Instead, you create a logical interface (LIF) and assign it to the

physical network adapter.

16. In this exercise, you used OnCommand System Manager and Data ONTAP cluster-

level commands to locate hardware information about Data ONTAP cluster nodes.

END OF EXERCISE





EXERCISE 4: CREATING AND MANAGING AGGREGATES

In this exercise, you create aggregates: logical collections of disks that store data. Disks are physically

located on the nodes of the cluster, but aggregates are at the cluster level (they are owned by the

Data ONTAP cluster).


OBJECTIVE


Use OnCommand System Manager to create an aggregate for a Data ONTAP cluster

Use the command-line interface (CLI) to create an aggregate for a Data ONTAP cluster

Delete an aggregate and initialize disks

STUDY-AID ICONS


Warning



forward.

Attention



Information


procedure.

Knowledge





















TASK 1: CREATE AN AGGREGATE USING ONCOMMAND SYSTEM MANAGER

In this task, you use OnCommand System Manager to create an aggregate in a Data ONTAP cluster.

STEP ACTION






STEP ACTION

2. If OnCommand System Manager is already open and you are logged in to the Data ONTAP

cluster-management page, skip to Step 5. Otherwise, on the Windows 2012 Server desktop,

double-click the NetApp OnCommand System Manager shortcut:

3. On the OnCommand System Manager home page, double-click cluster1:




STEP ACTION

4. In OnCommand System Manager, expand Cluster, cluster1, and Storage;

then click Aggregates:

5. Click Create.

The Create Aggregate Wizard starts.

6. On the Welcome page, click Next:




STEP ACTION

7. On the Aggregate Details page, enter the aggregate name aggr1 and click Next:

8. The Flash Pool feature enables you accelerate performance by creating aggregates

that include RAID groups of flash drives.

The Data ONTAP storage system in the self-paced lab has simulated flash drives,

which do not act the same way that physical flash drives do. You do not enable the Flash Pool

feature, because doing so would affect network performance.




STEP ACTION

9. Click Select disks:




STEP ACTION

10. On the Change Disk Selection page, review the types of disks that are physically attached to

all nodes of the cluster:

11. Disk Types and Disk Count

The recommended number of spare disks are excluded from the disks that are

shown as available. All disks that are included in an aggregate must reside on

the same node, but not necessarily on the same shelf.

Aggregates can include disks of different sizes. However, OnCommand System Manager

currently supports only disks of the same size on an aggregate.




STEP ACTION

12. Specify the node on which the aggregate will be located, the type of disks to use, and

the number of disks to add to the aggregate:

Node: cluster1-01; Effective Disk Type: FCAL

Number of capacity disks to use: 16

13. Click Save and Close:




STEP ACTION

14. Review the settings of your aggregate and click Create:




STEP ACTION

15. On the confirmation page, verify that the aggregate was created successfully and click Finish:

16. Verify that the new aggregate is listed in the Aggregates pane:




TASK 2: CREATE AN AGGREGATE USING THE CLI

In this task, you use the CLI to create an aggregate in a Data ONTAP cluster.

STEP ACTION

1. If the Data ONTAP CLI is already connected, skip to Step 4; otherwise, double-click the

PuTTY shortcut:




STEP ACTION

2. Double-click cluster1-mgmt to connect to the CLI of the Data ONTAP cluster:

3. At the Data ONTAP cluster login prompt, enter these credentials:

login as: admin

Password: Netapp123

The Data ONTAP cluster CLI prompt and cursor appear.




STEP ACTION

4. Review the parameters of the storage aggregate create command:

storage aggregate create ?

5. Create a 16-disk aggregate named aggr2 on cluster1-02:

storage aggregate create –aggregate aggr2 –nodes cluster1-02 –disktype

FCAL –diskcount 16 –raidtype raid_dp

6. If you do not supply -node, -disktype, or -raidtype parameters in the storage

aggregate create command, Data ONTAP automatically selects them. The only

required parameter for the command is the –diskcount parameter.

The command storage aggregate create –diskcount 16 creates an aggregate on the

node with the optimum number of available disks, taking into consideration disk type and other

performance parameters.




STEP ACTION

7. Review the aggregates in the Data ONTAP cluster:

stor aggr show

8. The Data ONTAP operating system recognizes the first few unique characters

of commands. The storage aggregate show command can be abbreviated

to stor aggr show.

9. Return to OnCommand System Manager and verify that the aggregates that you created are

in the Data ONTAP cluster:




TASK 3: USE THE CLI TO DELETE AN AGGREGATE

In this task, you use the CLI to create an aggregate, take the aggregate offline, and then delete it,

which returns the disks of the aggregate to the spare-disk pool.

After deleting the aggregate, you see that the spare disks are not initialized, so you use the storage

disk zerospares command to initialize the spare disks.

STEP ACTION

1. In the CLI, create a test aggregate:

storage aggregate create –aggregate aggr_test –diskcount 5

2. You might create an aggregate for a data migration project. The final step of the

project, after the data has been migrated to the new aggregate, might be to destroy

the original aggregate.

In this example, you create an aggregate for a test scenario.

3. Show the new aggregate, aggr_test:

storage aggregate show

4. Take aggr_test offline:

storage aggregate offline –aggregate aggr_test

5. Enter these two commands to delete aggr_test and then confirm the deletion:

storage aggregate delete –aggregate aggr_test

y




STEP ACTION

6. The disks that were a part of the aggr_test aggregate have been returned to the

spare pool. You can view uninitialized disks in OnCommand System Manager

at the Nodes level in the Disks pane.

7. Find an uninitialized spare disk:

a. In OnCommand System Manager, expands Nodes, cluster1, cluster1-01, and Storage.

b. Click Disks.

c. Scroll down to the spare disks and select the disk named: cluster1-01:v5.28

d. Note in the Properties pane that this spare, which was a member of the aggregate that you

deleted, is not zeroed:

8. Whenever you delete an aggregate, you should immediately initialize the disks that

have been added back to the spare disk pool. You must use the Data ONTAP cluster

CLI to initialize disks.

9. From the CLI, initialize spare disks:

storage disk zerospares




STEP ACTION

10. Return to the cluster1-01:v5.28 disk in OnCommand System Manager. Verify that you can

see the progress of the disk zeroing process:

11. Use OnCommand System Manager to ensure that you have deleted aggr_test and that

you have only two new aggregates: aggr1 in cluster1-01 and aggr2 in cluster1-02.

END OF EXERCISE





EXERCISE 5: SETTING UP A STORAGE VIRTUAL MACHINE

To access storage on the Data ONTAP cluster from a client, you must create a storage virtual machine

(SVM). (SVMs are referred to as “Vservers” in the OnCommand System Manager UI and the CLI.)

While creating an SVM, you can allow and configure protocols that are licensed on the Data ONTAP

cluster.

In this exercise, you use the Vserver Setup wizard in OnCommand System Manager to create an SVM

for the CIFS, NFS, and iSCSI protocols.


OBJECTIVES


Use the System Manager Vserver Setup wizard to create an SVM (called a Vserver by the UI)

Use the Vserver Setup wizard to configure CIFS and NFS settings and create a logical interface (LIF)

for CIFS and NFS data

Use the Vserver Setup wizard to configure a data LIF for the iSCSI protocol

Use the Vserver Setup wizard to configure the SVM administrator

Add DNS host records for the SVM management LIF, CIFS data LIF, and NFS data LIF

STUDY-AID ICONS


Warning



forward.

Attention



Information


procedure.

Knowledge






















TASK 1: CREATE A VSERVER

In this task, you complete part one of the three-part Vserver Setup wizard: creating an SVM.

STEP ACTION






STEP ACTION

2. If OnCommand System Manager is already open and you are logged in to Data ONTAP cluster

management, skip to Step 6. Otherwise, on the Windows 2012 Server desktop, double-click the

NetApp OnCommand System Manager shortcut:

3. On the Run Network Configuration Checker page, click Cancel.




STEP ACTION

4. On the OnCommand System Manager home page, select cluster1 and click Login.

5. Provide cluster1 credentials:

User name: admin

Password: Netapp123

Click Sign in.




STEP ACTION

6. On the Data ONTAP cluster-management page, expand Vservers:

7. In the cluster1 pane, click Create:

8. The Vserver Setup Wizard

The Vserver Setup wizard helps you complete the four parts of SVM creation:

1. Create the SVM.

2. Configure the allowed protocols (CIFS and NFS for NAS data, or iSCSI and Fibre Channel

for SAN data).

3. Create the data LIFs for transporting NAS or SAN data (as opposed to the management LIF,

which is for administrative communication).

You can also use the Data ONTAP cluster CLI to create an SVM. From the CLI, use the

Vserver create and Vserver setup commands. In this exercise, you use OnCommand

System Manager to create and configure the SVM.




STEP ACTION

9. On the Vserver Details page, configure the new SVM:

Vserver Name: svm1

Data Protocols: CIFS, NFS, and iSCSI

Language: C.UTF-8

Security Style: NTFS

Root Aggregate: aggr1

Ensure the search domain is learn.netap.local

Ensure that the Name Server is 192.168.0.11

Ensure that the settings are correct and then click Submit & Continue.




STEP ACTION

10. If the CIFS, NFS, or iSCSI protocol does not appear as a Data Protocols

option, the license code for the missing protocol has not been installed on

the Data ONTAP cluster.

Your screen should not look like this:

11. Under DNS Configuration, the Search Domains field must include the CIFS domain

name that the SVM is to join as a member server. The Search Domains and Name

Servers fields are pre-configured based on the configuration of the Windows server

that OnCommand System Manager is installed on.

12. The Vserver Details page closes and the Vserver Setup wizard completes part 1

of configuring the SVM: the creation of the SVM. If you were to make the mistake

of closing the Vserver Setup wizard, you would have to configure the protocols and

create the data LIFs manually for the newly created SVM.

The next page of the wizard is the “Configure CIFS protocol” page. Continue with the CIFS

protocol page in the next task.




TASK 2: CONFIGURE CIFS PROTOCOL

The Vserver Setup wizard now shows the “Configure CIFS protocol” page. In this task, you configure the

logical interface (LIF), specify the CIFS server name, and join the CIFS server to the Windows domain.

STEP ACTION

1. On the Configure CIFS/NFS protocol page, enter the Data LIF settings:

Retain the CIFS data LIFs configuration for NFS clients: Selected

IP Address: 192.168.0.111

Netmask: 255.255.255.0

Gateway: 192.168.0.1

Home Node: cluster1-01

Home Port: e0d




STEP ACTION

2. In the lower part of the Configure CIFS/NFS protocol page, enter the CIFS server configuration

settings:

CIFS Server Name: svm1_data

Active Directory: learn.netapp.local

Administrator Name: administrator

Administrator Password: Netapp123

NIS Configuration: do not expand

Ensure that all settings are correct, and then click Submit & Continue.

3. System time between the Windows domain controller and the Data ONTAP cluster

must be synchronized to within 5 minutes. If not, this step of the Vserver

Configuration wizard fails. The error message informs you that CIFS setup could

not be completed.

4. The Configure CIFS/NFS Protocol page closes and the Vserver Setup wizard

completes task 2: configuring the data LIF, CIFS server name, and Windows

domain membership. The next page that you see is the “Configure iSCSI protocol”

page. Continue with the iSCSI protocol page in the next task.




TASK 3: CONFIGURE ISCSI PROTOCOL

In this task, you configure a data LIF for the iSCSI protocol.

STEP ACTION

1. On the “Configure iSCSI protocol” page, enter these settings:

Target Alias: svm1_iscsi

Starting IP Address: 192.168.0.114

Netmask: 255.255.255.0

Gateway: 192.168.0.1

Ensure that all settings are correct, and then click Submit & Continue.

2. NAS and SAN Protocols

The CIFS and NFS protocols for NAS configurations can share a LIF. The iSCSI

and Fibre Channel (FC) protocols for SAN configurations cannot share a data LIF

with NAS protocols.

3. The “Configure iSCSI protocol” page closes and the Vserver Setup wizard configures

the iSCSI data LIF. The next page of the Vserver Setup wizard is the Vserver

Administration page. Continue with the Vserver Administration page in the next task.




TASK 4: CONFIGURE THE SVM ADMINISTRATOR

In this task, use the Vserver Setup wizard to configure the SVM (Vserver) administrator.

STEP ACTION

1. In this environment, the Vserver Administration page is optional. The page is

required in environments that require separate credentials for SVMs and the cluster.

2. On the Vserver Administration page, enter and confirm the password Netapp123 and

then complete the “Management Interface (LIF) Configuration for Vserver” section:

IP Address: 192.168.0.110

Netmask: 255.255.255.0

Gateway: 192.168.0.1

Home Node: cluster1-01

Home Port: e0e

Ensure that all settings are correct, and then click Submit & Continue:




STEP ACTION

3. The next page is the New Vserver Summary page. Record these values from

the Summary page

SVM (Vserver) host name: svm1

Name Server and Domain Controller: 192.168.0.11

CIFS server name: svm1_data

CIFS data LIF IP address: 192.168.0.111

You must use these values when you add host records for the SVM and CIFS server to the

DNS Manager. (This information is provided for you in the text of Task 5.)

4. Review the information on the New Vserver Summary page and click OK.




STEP ACTION

5. In OnCommand System Manager, at the Vservers level, ensure that svm1 is listed and that

the Quick Links section appears in the right pane.

6. Verify that the CIFS server name is “svm1_data” (case-insensitive) by expanding svm1,

Configuration, and Protocols, and then clicking CIFS:




STEP ACTION

7. The svm1 SVM has been configured with a system name for the Windows

domain. Notice that the CIFS service has started.

If the time is not synchronized between the Windows domain controller and the

Data ONTAP cluster, you might not notice the issue until you attempt to configure CIFS. At

this point, you would receive an error message. The error message says that Windows domain

authentication and the CIFS service did not start.

8. Verify that the data LIF accepts both CIFS and NFS data by expanding svm1 and

Configuration, and then clicking Network Interfaces.

9. The data LIFE, svm1_cifs_nfs_lif1, accepts NFS and CIFS protocol data. The

management LIF, svm1_admin_lif1, accepts only administrative communication.




TASK 5: ADD HOST RECORDS IN DNS FOR THE SVM

In this task, you add two DNS host records: svm1 with the SVM management LIF IP address and

svm1_data with the data LIF IP address.

STEP ACTION

1. If you know how to open the DNS Manager and add new host records, skip to Step 8.

Otherwise, on your Windows 2012 desktop, click the Server Manager shortcut:

2. On the Server Manager dashboard, click Tools:

3. On the list of tools, click DNS:




STEP ACTION

4. In the DNS Manager dialog box, ensure that the DNS navigation pane on the left shows the

host name of the Windows 2012 Server, W2K12.

Expand the Forward Lookup Zones folder:

5. Select the learn.netapp.local domain:




STEP ACTION

6. Ensure that there is a DNS host record for cluster1 and the cluster management LIF IP address:

7. With learn.netapp.local still selected, click Action and select New Host:




STEP ACTION

8. Configure a host record for smv1 and the management LIF IP address.

Name: svm1

IP address: 192.168.0.110

Click Add Host.

9. At the “host record was successfully created” prompt, click OK.




STEP ACTION

10. Create a host record for the SVM CIFS server name, svm1_data, and the data LIF IP address:

Name: svm1_data

IP address: 192.168.0.111

Click Add Host.

11. At the “host record was successfully created” dialog box, click OK.

12. The host name, svm1_data, and the data LIF IP address, 192.168.0.111,

are the network information of the CIFS and NFS protocol for svm1.




STEP ACTION

13. Click Done:

14. Ensure that host records were created for svm1 and svm1_data in the

learn.netapp.local folder:




STEP ACTION

15. To verify a second time that the svm1 and svm1_data names can be resolved to the correct

IP addresses, on the Windows 2012 Server desktop, open the CLI:

You can use either the nslookup command or the ping command for this verification.

16. In the CLI, enter these two commands:

ping svm1

ping svm1_data




STEP ACTION

17. If you cannot ping the SVM or the SVM CIFS server by name and the DNS records

are correct, the Windows 2012 Server might not have the correct DNS server. If the

DNS server for the Windows 2012 Server is not 192.168.0.11, then you must stop

and contact NetApp University Support.

Ensure that the local DNS server has been specified in the network settings of the Windows

2012 Server by entering this command at the Windows Server command prompt:

ipconfig /all

18. In this exercise, you created an SVM named “svm1” with LIFs and IP addresses

for the CIFS, NFS, and iSCSI data protocols.

END OF EXERCISE





EXERCISE 6: CREATING AND MANAGING VOLUMES ON AN SVM

In this exercise, you delegate volume creation to the storage virtual machine (SVM) administrator, create

volumes, and manage the SVM namespace.

OBJECTIVES


Delegate volume creation to the SVM administrator (vsadmin)

Create volumes on the SVM

Organize the SVM namespace

STUDY-AID ICONS


Warning



forward.

Attention



Information


procedure.

Knowledge






















TASK 1: DELEGATE VOLUME CREATION TO THE SVM ADMINISTRATOR

The SVM administrator (vsadmin) does not automatically have the authority to create volumes

in aggregates, so in this task, you delegate volume creation to vsadmin for svm1.

STEP ACTION

1. If you have not yet opened the Windows 2012 Server desktop, ensure that you are on

the Windows 2012 Server Start page and click the Desktop tile:




STEP ACTION




3. In the Run Network Configuration Checker dialog box, click Cancel:




STEP ACTION

4. On the OnCommand System Manager home page, select cluster1 and click Login:

5. On the Data ONTAP cluster-management page, expand the Vservers level.

6. At the Vservers level, select cluster1.

In the cluster1 pane on the right, notice that svm1 is automatically selected as the SVM

to be edited:




STEP ACTION

7. In the cluster1 toolbar, click Edit:

8. In the Edit Vserver dialog box, click the Resource Allocation tab:

9. The Data ONTAP cluster administrator has permission to create volumes on any

aggregate and on any SVM in the cluster. The Data ONTAP cluster administrator

can delegate permission to the SVM administrator.




STEP ACTION

10. On the Resource Allocation tab, select Delegate volume creation, which enables other settings.

Select aggr1 and aggr2, and then click Save and Close:

11. The SVM administrator now has permission to create volumes in aggr1 and aggr2.




TASK 2: CREATE VOLUMES ON THE SVM

In this task, you create four volumes on the SVM: vol1, project_y, project_z, and teams.

STEP ACTION

1. In OnCommand System Manager, expand Vservers, select svm1 and then, under Quick Links,

click Create Volume:

2. Another way to initiate the volume creation process is to expand Vservers, cluster1,

svm1, and Storage, and then click Volumes, Create.

The configuration of a volume includes its name, assigned aggregate, storage type,

size, thin-provisioning setting, and storage-efficiency setting.




STEP ACTION

3. In the Create Volume dialog box, specify these settings:

Name: vol1

Aggregate: aggr1

Storage Type: NAS

Total Size: 1 GB

4. Thin Provisioning

If you select the Thin Provisioned checkbox, you can specify a total size for the

volume that is greater than the available disk space on the aggregate. If you enable

thin provisioning, you must monitor space utilization on the volume. If the aggregate runs out

of space, then writes to the thin provisioned volume fail.




STEP ACTION

5. Click the Storage Efficiency tab.

On this tab, you can select the checkboxes to enable daily volume deduplication and

enable compression. Do not enable storage efficiency for this exercise.

6. Click Create to create vol1.




STEP ACTION

7. Repeat the steps to create the three more volumes:

a. Under Vservers, click svm1.

b. In the Quick Links section, click Create Volume.

8. When you create a volume in aggr1 (without enabling thin provisioning), space is

reserved for the volume and the available space in aggr1 is reduced.

(The Available Size value that you see might differ from this one, depending on

how many volumes you have created.)




STEP ACTION

9. Create three more 1-GB volumes on aggr1. Give them these names:

project_y

project_z

teams




STEP ACTION

10. Ensure that four volumes have been created:

a. Expand Vservers, cluster1, svm1, and Storage, and then click Volumes.

b. In the Volumes pane, find the four volumes: project_y, project_z, teams, and vol1.




TASK 3: ORGANIZE VOLUMES IN THE SVM NAMESPACE

The diagram represents the SVM namespace. Clients in the network map to the root volume, vol1. From

there, they use junction paths to access volumes linked to vol1. For example, from vol1, clients can access

the teams volume. The teams volume appears as a linked subdirectory of vol1.

SVM Namespace

Junction Path for team: /vol1/teams/

The four volumes that you created are all mounted to the root of the SVM namespace. In this task, you

rearrange namespace junction paths so that clients can map to the vol1 volume, access the teams volume,

and then access the project_y and project_z volumes.

STEP ACTION

1. Expand Vservers, cluster1, svm1, and Storage. Click Namespace and examine the structure

of the namespace.

Notice that the root of the namespace is indicated with the forward slash (“/”).

2. The Namespace

Each Data ONTAP cluster SVM has a namespace. The namespace begins with the

name of the SVM and then the names of the volumes that are being shared, starting

at the root of the namespace. All of the volumes that you created have been automatically

mounted to the root of the namespace.

To change the hierarchy of the volumes, you must change the junction paths. To change the

junction paths, you must unmount the volume.




STEP ACTION

3. In the Namespace pane, select the teams volume and click Unmount.

4. In the Unmount Volume dialog box, click Unmount.

5. Verify that the teams volume is no longer mounted in the namespace:




STEP ACTION

6. Click Mount:

7. In the Mount Volume dialog box, click the Volume Name drop-down arrow and select teams:

8. Next to the Junciton Path field, click Browse.




STEP ACTION

9. In the Browse For Junction Path dialog box, expand the root directory to view all of the volumes

that are mounted at the root of the namespace.

10. Select the vol1 junction path and ensure that /vol1 appears in the Selected Path field, then click

OK:




STEP ACTION

11. Click Mount:

12. The junction path for the teams volume is now /vol1/teams.

13. Select project_y, click Unmount, and in the dialog box that appears, click Unmount again.

Do the same to unmount project_z.

14. Ensure that project_y and project_z are no longer mounted in the namespace:

15. In the Namespace pane, click Mount.

16. In the Mount Volume dialog box, click the Volume Name drop-down arrow and select

project_y. Then next to the Junction Path field, click Browse.




STEP ACTION

17. Expand the root directory, select the /vol1/teams junction path, and ensure that /vol1/teams

appears in the the Selected Path field.Then click OK:

18. In the Mount Volume dialog box for project_y, click Mount:




STEP ACTION

19. Repeat Steps 15 to 18 to mount project_z in the /vol1/teams junction path:

20. The root of the SVM namespace has been rearranged. The vol1 volume is at the root

of the namespace. The teams volume is in the vol1 junction path, and the project_y

and project_z volumes are in the /vol1/teams junction path.

21. You have delegated volume creation to the SVM administrator, created volumes,

and rearranged the namespace; however, the volumes that you created are not yet

accessible to clients.

END OF EXERCISE





EXERCISE 7: SHARING VOLUMES WITH WINDOWS CLIENTS

The storage virtual machine (SVM) in the Data ONTAP cluster is a member server in a Windows domain.

To make volumes on the SVM accessible to Windows clients, you must create CIFS shares for the

volumes.

In this exercise, you create a CIFS share for vol1 and project_y and then map a disk to these shared

volumes.


OBJECTIVES


Create a CIFS share for a volume at the root of the namespace

Change the default access control settings

Map a disk to a shared volume and view other volumes that are in the junction path

Create a CIFS share with share-specific permissions for a volume in a junction path

Map a disk to a volume, and give that disk individual permissions

STUDY-AID ICONS


Warning



forward.

Attention



Information


procedure.

Knowledge








Windows 2012 Server, one Data ONTAP cluster, and one Linux server. Only the hardware of the

Data ONTAP cluster virtual machine (VM) is simulated; The Data ONTAP software is authentic.



SYSTEM HOST NAME IP ADDRESSES USER NAME PASSWORD



CIFS, NFS Data LIF svm1_data 192.168.0.111 LEARN\Administrator Netapp123







TASK 1: CREATE A CIFS SHARE FOR A VOLUME AT THE ROOT OF THE NAMESPACE

In this task, you create a CIFS share for the vol1 volume. The vol1 volume is at the root of the

namespace and so other volumes in the junction path will also be accessible.

STEP ACTION






STEP ACTION




3. In the Run Network Configuration Checker dialog box, click Cancel.




STEP ACTION

4. On the OnCommand System Manager home page, select cluster1, and then click Login.

5. In OnCommand System Manager, expand Vservers and cluster1, and then click svm1. The

Quick Links section appears.

In the Quick Links section, click Create Share:

6. In the Create Share dialog box, click Browse.




STEP ACTION

7. In the Browse for Folder dialog box, Expand the root directory (“/”), select vol1and ensure that

/vol1 appears in the the Selected Path field at the bottom of the dialog box. Then click OK:

8. In the Create Share dialog box, click Create:




STEP ACTION

9. Select the vol1 share. Verify that in the Share Access Control section, the default permissions

of Everyone and Full Control are selected:

10. For most volumes, you must change the default permissions to be more restrictive

than the default permission: Everyone/Full Control.




TASK 2: CHANGE THE DEFAULT ACCESS CONTROL SETTINGS

In this task, you change the access control permissions of a CIFS share.

STEP ACTION

1. In the Shares pane, select vol1 and click Edit:

2. In the “Edit vol1 Settings” dialog box, click the Permissions tab:




STEP ACTION

3. On the Permissions tab, verify that the vol1 share has the default permissions of Everyone

and Full Control, and then click Add:

4. In the Add Users and Groups dialog box, enter the username of the Learn domain, which is

learn\administrator. Then click OK:




STEP ACTION

5. On the Permissions tab, select learn\administrator, and then select Full Control permissions.




STEP ACTION

6. Select Everyone, click Remove, and then click Save and Close:




STEP ACTION

7. Verify that learn\administrator has full control and that no other users or groups are listed:




TASK 3: MAP A DISK TO A SHARED VOLUME

Now that you have shared a volume, you can access the share from a Windows client.

In this task, you map a disk from the desktop of the Windows 2012 Server to the shared volume.

STEP ACTION

1. On the Windows 2012 Server desktop taskbar, click the folders icon:

2. In the navigation pane of File Explorer, right-click Computer and select Map network drive.




STEP ACTION

3. In the Map Network Drive dialog box, enter the CIFS Server system name and share name

\\SVM1_DATA\vol1, accept the default drive letter, and then click Finish.

4. SVM System Name

The system name was configured when you configured the CIFS protocol from the

Vserver Setup wizard. When you configure the system name on an SVM, you should

add a DNS host record for the system name and data LIF IP address.

If you do not have connectivity to the svm1_data system name, verify that a DNS host record

has been added to the DNS Manager or connect to the vol1 share with the CIFS data LIF IP

address and share name: \\192.168.0.111\vol1.




STEP ACTION

5. The share \\SVM1_DATA\vol1 opens on disk Z:\. Notice the shortcut to the “teams” volume:

6. Double-click teams and verify that there are shortcuts to the project_y and project_z volumes.




STEP ACTION

7. Double-click the project_y volume and verify that the volume is empty:

8. Rght click within project_y, click New, and select Folder.




STEP ACTION

9. Name the folder Project_y_directory1.

10. Verify that you successfully wrote to project_y:




TASK 4: CREATE CIFS SHARES FOR VOLUMES IN THE NAMESPACE

In this task, you share individual volumes of a namespace with volume-specific permissions.

STEP ACTION

1. In OnCommand System Manager, expand Vservers, cluster1, and svm1. Then click Shares:

2. Click Create Share:

3. In the Create Share dialog box, click Browse.




STEP ACTION

4. Expand vol1 and teams, select project_y, and click OK:

5. In the Create Share dialog box, enter the comment: Read-only access for contractors.

Then click Create:




STEP ACTION

6. In the Shares pane, verify that the project_y share has the default share access control

of Everyone and Full Control. Then select the project_y share and click Edit:




STEP ACTION

7. In the “Edit project_y Settings” dialog box, click the Permissions tab:

8. Change the permissions of Everyone to Read and click Save and Close:




STEP ACTION

9. Verify that the project_y share permission for everyone is set to Read:




TASK 5: MAP A DISK TO A SHARED VOLUME

In this task, you map a disk to the read-only shared volume and test access permission.

STEP ACTION

1. On the Windows 2012 Server desktop taskbar, click the folders icon.

2. In the navigation pane of File Explorer, right click Computer and select Map network drive:




STEP ACTION

3. In the Map Network Drive dialog box, enter the CIFS Server system name and share name

\\SVM1_DATA\project_y and click Finish:

4. Verify that the share \\SVM1_DATA\project_y opens on disk Y:\. Verify also that

Project_y_directory1 is on the \\SVM1_DATA\vol1 shared disk:




STEP ACTION

5. Right-click in the project_y mapped disk and attempt to create a folder:

6. Verify that you are unable to create the folder (because you set access-control permission

to Read):

7. If you create a share for a volume that is at the root of a junction path, users can

connect to the root volume and any volume in the junction path with the same

permissions.

If you want each volume in a junction path to have its own permissions, create a separate share

for each volume. Users can then map to each volume individually, with volume-specific

permissions.

END OF EXERCISE





EXERCISE 8: EXPORTING VOLUMES TO UNIX AND LINUX CLIENTS

In this exercise, you ensure that the NFS protocol is enabled, ensure that the data logical interface (LIF)

enables use of the NFS protocol, configure multiprotocol access, and configure export policies.


OBJECTIVES


Confirm that the NFS protocol is allowed on a storage virtual machine (SVM)

Confirm that the data LIF enables the use of the NFS protocol

Configure multiprotocol access for Windows and UNIX users

Add a rule to the default export policy

Create export policies

Assign an export policy to a volume

STUDY-AID ICONS


Warning



forward.

Attention



Information


procedure.

Knowledge












SYSTEM HOST NAME IP ADDRESSES USER NAME PASSWORD


Data ONTAP cluster cluster1 192.168.0.101 admin (case sensitive) Netapp123


node 1 cluster1-01 192.168.0.91 admin (case sensitive) Netapp123

node 2 cluster1-02 192.168.0.92 admin (case sensitive) Netapp123





TASK 1: CONFIRM THAT THE NFS PROTOCOL IS ENABLED ON AN SVM

In this task, you ensure that the NFS protocol is allowed and enabled on an SVM.

STEP ACTION

1. If you have not yet opened the Windows 2012 Server desktop, ensure that you are on

the Windows 2012 Server Start page and click the Desktop tile:




STEP ACTION




3. In the Run Network Configuration Checker dialog box, click Cancel:




STEP ACTION

4. On the OnCommand System Manager home page, select cluster1, and then click Login.

5. In the cluster1 management pane, expand Vservers, select cluster1, and click Edit.




STEP ACTION

6. In the Edit Vserver dialog box, click the Protocols tab and verify that NFS is selected as

a protocol that can serve data. Then click Cancel:




STEP ACTION

7. NFS might be allowed, but not enabled.

Open Configuration, Protocols, and click NFS. Ensure that Server Status

and Version 3 Support are both marked Enabled:

If the NFS protocol is not configured, click Enable.

8. The versions and features of NFS that you configure depend on the versions of

NFS that are operating on the UNIX and Linux clients in your network.




TASK 2: CONFIRM THAT THE DATA LIF ALLOWS THE NFS PROTOCOL

In this task, you confirm that there is a LIF that supports the NFS protocol. You also use the ping

command to test connectivity from the Linux server to the SVM.

STEP ACTION

1. Open Configuration and click Network Interfaces. Ensure that there is a data LIF that

supports the NFS protocol and that the data LIF is listed as Enabled.

2. In the lower section of the Network Interfaces pane, review the detailed information about

the CIFS and NFS data LIF.




STEP ACTION

3. Although the NFS protocol is allowed, you must also ensure that a data LIF

is available that allows the NFS protocol.

Because CIFS and NFS were both licensed and allowed from the Vserver Setup

wizard, the NFS protocol was allowed on the data LIF along with the CIFS protocol.

If you do not allow the NFS protocol from the Vserver Setup wizard, then you must use the

Network Interface Create Wizard to create a separate NFS data LIF. After a LIF has been

created, it cannot be changed.

4. From the desktop of the Windows 2012 Server, use PuTTY to connect to the Linux server.

Log in with the username root and password Netapp123:

5. Ensure that the Linux server can use the system name of the SVM to resolve the data LIF IP

address, by entering this command in the Linux server CLI:

ping svm1_data

6. If the Linux server cannot resolve the system name of the SVM, then check the

svm1_data host record in the DNS Manager.




TASK 3: CONFIGURE MULTIPROTOCOL ACCESS FOR WINDOWS AND UNIX USERS

In this task, you use OnCommand System Manager to ensure that the pcuser account was created. From

the Name Mapping pane, you also map the UNIX root account to the Windows domain administrator.

STEP ACTION

1. In OnCommand System Manager, expand Vservers and cluster1, and then click svm1. In the

Quick Links section, click UNIX Local Users and Groups:

2. In the UNIX pane, click the Users tab and ensure that pcuser is listed:

3. Windows users who attempt to access NFS volumes or qtrees are automatically

mapped to the UNIX user named pcuser.

The Vserver Setup wizard automatically creates pcuser.

4. If NFS is not licensed at the time that the Vserver is created, or if multiprotocol is not

selected, pcuser is not automatically created. If pcuser is not created, multiprotocol

access does not work.




STEP ACTION

5. Navigate to svm1, Configuration, Local Users and Groups. Then click Name Mapping:

6. Data ONTAP uses name-mapping patterns to obtain correct user credentials. Data

ONTAP then changes the Windows or UNIX username to match the security style

of the data that a client wants to access.

7. Click Add to add a name mapping rule.




STEP ACTION

8. In the Add Name Mapping Entry dialog box, configure a rule that converts the UNIX root

account to the LEARN domain administrator user account:

Direction: UNIX to Windows

Pattern: root

Replacement: learn\\administrator

9. The first backslash “\” in the “domain\\user” replacement pattern is used as an escape

so that Data ONTAP can properly parse the domain\user account statement.

Whenever you enter a Windows domain and username, use the double-backslash

domain\\<username> format.

10. The position number gives priority to a user with multiple matches due to the use of

wildcards in name-mapping patterns. However, Data ONTAP uses the first name-

mapping pattern that matches, without regard to priority.

To avoid issues, first remove existing name mappings. Then add new name mappings to the

SVM in the order that you want them to be processed.

11. Click Add:

12. Verify that the UNIX root user is mapped to the Windows domain administrator user account:

13. In the Name Mapping pane, click Add again.




STEP ACTION

14. In the Add Name Mapping Entry dialog box, configure a rule that converts the LEARN domain

administrator user account back to the UNIX root account:

Direction: Windows to UNIX

Position: 2

Pattern: learn\\administrator

Replacement: root

15. Data ONTAP can now map the UNIX root user to the Windows learn\administration

user. Data ONTAP can also grant the UNIX root user permissions to volumes

that are configured in the NTFS security and require Windows access control

lists (ACLs) to access.

You can now export the NTFS volumes that you created in earlier exercises. Proceed to the

next task to add a rule to the default export policy.




TASK 4: ADD A RULE TO THE DEFAULT EXPORT POLICY

Data ONTAP automatically assigns the default export policy to new volumes. However, the default

export policy of a new SVM has no rules and therefore grants no access to clients.

In this task, you add a rule to the default export policy and test access to volumes that are assigned the

default export policy.

STEP ACTION

1. On the Vservers page, click svm1. In the Quick Links section, click Policies:

2. In the Policies pane, click Export Policies:




STEP ACTION

3. In the Export Policies pane, expand the default policy. No rules are configured for the policy:

4. Click Add Rule:

The rules area is blank because the default export policy has no rules.




STEP ACTION

5. In the Create Export Rule dialog box, set the parameters of the new export rule:

Client Specification: CentOS64 (the host name of the Linux server)

Access Protocols: CIFS, NFS

All access rules: accept default values

Click OK:

6. Verify that the default export policy has an access rule:




STEP ACTION

7. Open Storage and click Namespace.

All volumes are automatically exported to the default export policy:

8. If you are not already logged in to the Linux server, from the desktop of the Windows 2012

Server, use PuTTY to connect to the Linux server. Log in with the username root and

password Netapp123:

9. Ensure that the Linux server can mount vol1:

mkdir /mount_point

mount svm1_data:/vol1 /mount_point




STEP ACTION

10. Ensure that you have read access to the vol1 volume and the other volumes in the junction

path from the Linux server:

cd /mount_point

ls

cd teams

ls

11. Ensure that you have write access by creating and displaying a directory in the teams volume:

mkdir linux_dir

ls

12. In this task, all volumes are automatically exported to the default export policy. In

production, you would create several export policies and assign each volume to the

appropriate export policy.




TASK 5: CREATE EXPORT POLICIES

In this task, you create an export policy with restrictive access rules, create a volume with a

UNIX security style, and then test access to this volume from the Linux server.

STEP ACTION

1. At the Vservers level, click svm1. In the Quick Links section, click Policies:

2. In the Policies pane, click Export Policies:

3. In the Export Policies pane, click Create Policy:




STEP ACTION

4. In the Create Export Policy dialog box, enter the policy name SecureData and click Add:




STEP ACTION

5. In the Create Export Rule dialog box, enter the settings for the SecureData export policy:

Client Specification: CentOS64

Access Protocols: NFS

All access rules: accept default values

Then click OK:




STEP ACTION

6. In the Create Export Policy dialog box, verify the settings and click Create:

7. Ensure that the SecureData export policy is listed in the Export Policies pane:

8. Although the SVM has been configured for multiprotocol access, this is an export

policy that you can assign to a volume that restricts access to only one UNIX server.




TASK 6: ASSIGN AN EXPORT POLICY TO A VOLUME

In this task, you create a volume, assign an export policy, and test access from the Windows client

and from the Linux client.

STEP ACTION

1. At the Vservers level, click svm1. In the Quick Links section, click Create Volume:




STEP ACTION

2. In the Create Volume dialog box, create a volume with this configuration:

Name: SecureData_vol1

Aggregate: aggr1

Then click Create:

3. In the Volumes pane, select the SecureData_vol1 volume and click Edit:




STEP ACTION

4. In the Edit Volume dialog box, change the security style to UNIX:

5. Complete the UNIX permissions setting for owner and group access:

Owner: Read, Write, Execute

Group: Read, Write, Execute

6. Click Save and Close:

7. At the Vserver level open svm1 and Storage. Then click Namespace.




STEP ACTION

8. In the Namespace pane, select SecureData_vol1 and click Change Export Policy:

9. In the Change Export Policy dialog box, click the Export Policy drop-down arrow and

select the SecureData export policy. Then click Change.

10. In the Namespace pane, verify that the export policy assigned to the SecureData_vol1

volume has changed:




STEP ACTION

11. If you are not already logged in to the Linux server, from the desktop of the Windows 2012

Server, use PuTTY to connect to the Linux server. Log in with the username root and

password Netapp123:

12. Test access to the SecureData_vol1 volume from the Linux server:

mkdir /mount_secure

mount –o nolock svm1_data:/SecureData_vol1 /mount_secure

cd /mount_secure

ls

mkdir test

ls




STEP ACTION

13. You have completed the configurations required to access a volume on the SVM

from a Linux server.

The SVM and data LIF must allow the NFS protocol.

If the volumes were created with NTFS security style, you must configure multiprotocol

access by mapping UNIX users to the equivalent Windows users.

You must configure an export policy with rules that allow access to UNIX users.

Your SVM serves your Windows, UNIX, and Linux users. However, you can use the

volume security type and export policies to restrict access to CIFS or NFS.

END OF EXERCISE


Documents

Basic NetApp Configuration and Administration Part … · Basic NetApp Configuration and ... Do Not Distribute. E-2 Basic NetApp Configuration and Administration ... all of the exercise