clustered data ontap 8.3 update 2, ipspaces self-paced · pdf filenetapp university ....

NETAPP UNIVERSITY

Clustered Data ONTAP 8.3 Update 2, IPspaces Self-paced Lab Course ID: STRSW-SPL-CDOT83UPD2 Content Version: 1.0

NetApp University - Do Not Distribute

E-2 Clustered Data ONTAP 8.3 Update 2, IPspaces: Welcome

© 2014 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

© 2014 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

E2-1 Clustered Data ONTAP 8.3 Update 2: IPspaces


CLUSTERED DATA ONTAP 8.3 UPDATE 2: IPSPACES

EXERCISE

In this exercise, you explore the new multi-tenancy feature of clustered Data ONTAP 8.3 called IPspaces.

This exercise starts with two data networks that enable the Linux client to communicate over two different

networks. This scenario uses two fictional companies. 123 Company uses the CIFS (or SMB) protocol to

serve data to the Windows client over 192.168.0.100 on data network 1. XYZ Company uses the NFS version

3 protocol to serve data to the Linux client over 192.168.0.100 on data network 2.

NOTE: This is a simulated environment. The clustered Data ONTAP 8.3 Simulators are not high-availability

(HA) pairs. This is not a supported configuration. The only non-HA configuration that is supported is a

single-node cluster.

FEATURED NETAPP PRODUCTS

Clustered Data ONTAP 8.3

OnCommand System Manager

KEY FEATURES TO DEMONSTRATE

IPspaces

HIGH-LEVEL VALUE PROPOSITION

Clustered Data ONTAP 8.3 provides a feature-rich environment that is often the best fit for customers.

Clustered Data ONTAP 8.3 supports duplicate IP ranges by using IPspaces for a truly multi-tenant data

center.

OBJECTIVES

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

Explore network objects in cluster1

Explore network objects in cluster2

Create a new IPspace

Use the default IPspace to create SVM1

Use a custom IPspace to create SVM2

Use different IPspaces to access clients




EXERCISE ENVIRONMENT

This environment consists of:

Windows Server 2012 R2 Active Directory

Two-node cluster: cluster1

Single-node cluster: cluster2

Linux

HOST NAME IP ADDRESS USER NAME PASSWORD

w2k12 192.168.0.11 administrator Netapp123

linux 192.168.0.22 root NetApp123

cluster1 192.168.0.50 admin Netapp123

cluster1-01 192.168.0.51 admin Netapp123


cluster2 192.168.0.60 admin Netapp123


svm123 (CIFS LIF) 192.168.0.120 N/A N/A

svm123 192.168.0.121 vsadmin Netapp123

svmXYZ (NFS LIF) 192.168.0.120 N/A N/A

svmXYZ 192.168.0.121 vsadmin Netapp123

NOTE: This table lists only the lab components. Please refer to the tasks that follow for the detailed steps.

W2k12

e0d e0c

e0a e0b

e0d e0c

e0a e0b

e0d e0c

e0a e0b

cluster1 cluster2

Linux

eth1 eth0 Data Network 1

Data Network 2 Cluster Interconnect




TASK 1: EXPLORE NETWORK OBJECTS IN CLUSTER1

In this task, you explore the default IPspaces, configured subnets, broadcast domain, and network interfaces in

cluster1.

STEP ACTION

1. Verify that you see the Modern view of your assigned Windows server.

2. Click the Desktop tile.




STEP ACTION

3. Verify that you see the administrator desktop.

4. On your Windows desktop, double-click the “link to PuTTY” icon.

5. Verify that the PuTTY window opens.

6. Select the cluster1-mgmt saved session.




STEP ACTION

7. Click Load.

8. Click Open to start the session.

The PuTTY Security Alert should appear.

9. Click Yes to confirm the SSH fingerprint key.

10. Verify that the login prompt appears.

login as:

11. Use these credentials to authenticate with your cluster:

User Name: admin

Password: Netapp123

12. Verify that the command prompt appears.

cluster1::>

13. Enter this command to list the current IPspaces for cluster1:

cluster1::> network ipspace show

Sample output:

IPspace Vserver List Broadcast Domains

------------------- ----------------------------- ----------------------------

Cluster

Cluster Cluster

Default

cluster1, svm1 Default

2 entries were displayed.

14. Notice that the multiple-node cluster initially has two IPspaces.




STEP ACTION

15. On the administrator desktop, open Internet Explorer.

16. In the URL textbox of Internet Explorer, enter this URL: https://192.168.0.50/

17. When the Certificate Error page appears, click Continue to this website (not recommended).

18. Verify that OnCommand System Manager for your assigned cluster appears in the browser.




STEP ACTION


User Name: admin

Password: Netapp123

20. Click Sign In.

21. Verify that the System Manager interface appears.

22. In the left pane, select Cluster > cluster1 > Configuration > Network.




STEP ACTION

23. Examine the System Manager Network page, where you can manage all network configuration.




STEP ACTION

24. Click the Ethernet Ports tab.




STEP ACTION

25. Notice that node 1 and node 2 within cluster1 have e0c, e0d, e0e and e0f assigned to the default

broadcast domain.

This broadcast domain is associated with the Default IPspace, which is available for data traffic.

The Cluster IPspace is used only for cluster interconnect traffic. This means that the Cluster

broadcast domain, and its associated e0a and e0b ports on each node of the cluster, is available

only for cluster interconnect communication.




STEP ACTION

26. Click the Broadcast Domains tab.

27. Notice the broadcast domains, which are named Cluster and Default.




STEP ACTION

28. Click the Subnets tab.

The existing subnet was created during the previous exercise: Clustered Data ONTAP 8.3

Update 1: System Manager. This subnet uses the Default IPspace and the Default broadcast

domain’s ports.




TASK 2: EXPLORE NETWORK OBJECTS IN CLUSTER2

In this task, you explore default IPspaces and subnets, the broadcast domain, and the network interfaces in

cluster2.

STEP ACTION

1. On your Windows desktop, double-click the “link to PuTTY” icon.


3. Select the cluster2-mgmt saved session.

4. Click Load.





login as:




STEP ACTION


User Name: admin

Password: Netapp123


cluster2::>



Sample output:


------------------- ----------------------------- ----------------------------

Cluster

Cluster Cluster

Default

cluster2 Default


11. Notice that the single-node cluster initially has two IPspaces.

12. On the administrator desktop, open Internet Explorer.

13. In the URL textbox of Internet Explorer, enter this URL: https://192.168.0.60/

14. When the Certificate Error page appears, click Continue to this website (not recommended).




STEP ACTION

15. Verify that OnCommand System Manager for your assigned cluster appears in the browser.


User Name: admin

Password: Netapp123

17. Click Sign In.




STEP ACTION

18. Verify that the System Manager interface appears.

19. Select Cluster > cluster2 > Configuration > Network.




STEP ACTION

20. Click the Ethernet Ports tab.

21. Notice that, initially, all ports on a single-node cluster are on the Default IPspace and on the

Default broadcast domain, and that there are no ports on the Cluster IPspace.




STEP ACTION

22. Click the Broadcast Domains tab and notice the broadcast domains named Cluster and Default.

No ports are associated with the Cluster broadcast domain.

23. Select the Default broadcast domain.

24. Notice that all six ports are associated with this domain.




TASK 3: CREATE A NEW IPSPACE

In this task, you create a new IPspace for the fictional company XYZ. Then you create a new broadcast

domain and subnet for this company.

STEP ACTION

1. Enter this command to create a new IPspace for cluster2:

cluster2::> network ipspace create -ipspace ip-XYZ



Sample output:


------------------- ----------------------------- ----------------------------

Cluster

Cluster Cluster

Default

cluster2 Default

ip-XYZ

ip-XYZ -


3. Although you could run the rest of the commands with the CLI, switch back to System Manager

for cluster2.





STEP ACTION

5. Click the Broadcast Domains tab.

6. Select the Default domain.

7. Click Edit.




STEP ACTION

8. Clear the checkboxes for e0a and e0b.

In this environment, e0a and e0b are on a separate network, along with eth1 for the Linux client.

9. Click Save and Close.




STEP ACTION

10. Verify that only e0c, e0d, e0e and e0f are now on the Default broadcast domain.

11. Click Create.




STEP ACTION

12. Create a new broadcast domain with these attributes:

Name: bn-XYZ

MTU: 1500

IP Space: ip-XYZ

Ports: e0a and e0b

13. Click Create.




STEP ACTION

14. Verify that the new broadcast domain was created.

15. Click the Subnets tab.

16. Click Create.




STEP ACTION

17. Create a subnet with these attributes for the Default broadcast domain:

Name: sn-Default

Subnet IP/Subnet mask: 192.168.0.0/255.255.255.0

IP Addresses: 192.168.0.120-192.168.0.129

Gateway: 192.168.0.1

Broadcast Domain: Default (Click the Browse button.)

18. Click Create.




STEP ACTION

19. Verify that the subnet was created.

20. Click Create.




STEP ACTION

21. Create a subnet for the bn-XYZ broadcast domain with the same IP range and subnet IP address

as the first subnet object:

Name: sn-XYZ

Subnet IP/Subnet mask: 192.168.0.0/255.255.255.0

IP Addresses: 192.168.0.120-192.168.0.129

Gateway: 192.168.0.1

Broadcast Domain: bn-XYZ (Click the Browse button.)

22. Click Create.




STEP ACTION

23. Verify that the subnet was created.




TASK 4: CREATE SVM2, WHICH USES THE DEFAULT IPSPACE

In this task, you create a storage virtual machine (SVM) that uses the CIFS protocol through the ports that are

associated with the Default IPspace.

STEP ACTION

1. Select Cluster > cluster2 > Storage > Aggregate.

2. Click Create.




STEP ACTION

3. Create an aggregate with these attributes:

Name: n1_aggr1

Disk Type: FCAL

Number of Disks: 14

4. Click Create.




STEP ACTION

5. Verify that the aggregate was created.

6. Using System Manager, navigate to Storage Virtual Machine.

7. Verify that the cluster2 SVM list appears.

It is currently empty.




STEP ACTION

8. Click Create.

9. In the Storage Virtual Machine (SVM) setup, Step 1 SVM basic details dialog, enter these

settings:

SVM Name: svm123

IPspace: Default

Volume Type: FlexVol volumes

Data Protocols: CIFS

Default Language: C.UTF-8

Security Style: NTFS

Root Aggregate: n1_aggr1

Search Domains: learn.netapp.local

Name Servers: 192.168.0.11

10. Click Submit & Continue.




STEP ACTION

11. In the Step 2, enter these settings:

Subnet: sn-Default

Port: cluster2-01:e0c (Click the Browse button.)

CIFS Server Name: svm123

Active Directory: learn.netapp.local

Organizational Unit: CN=Computers

Administrator Name: Administrator

Administrator Password: Netapp123

Share Name: 123Data

Size: 1 GB

Permission: Everyone - Full Control





STEP ACTION

13. In Step 3, enter these settings:

User Name: vsadmin

Password: Netapp123

Confirm Password: Netapp123

Create a new LIF for SVM management: Select checkbox

Subnet: sn-Default

Port: cluster2-01:e0d (Click the Browse button.)





STEP ACTION

15. Verify that the configuration is correct.

16. Click OK.




TASK 5: CREATE SVMXYZ, WHICH USES A CUSTOM IPSPACE

In this task, you use System Manager to create an SVM named svmXYZ that uses the NFS version 3 protocol

to serve data across a custom IPspace.

STEP ACTION

1. Using System Manager, select Storage Virtual Machines > cluster2.

2. Click Create.




STEP ACTION

3. In the Storage Virtual Machine (SVM) setup, Step 1 SVM basic details dialog, enter these

settings:

SVM Name: svmXYZ

IPspace: ip-XYZ

Volume Type: FlexVol volumes

Data Protocols: NFS

Default Language: C.UTF-8

Security Style: UNIX

Root Aggregate: n1_aggr1

Search Domains: learn.netapp.local

Name Servers: 192.168.0.11





STEP ACTION

5. In the Step 2, enter these settings:

Subnet: sn-XYZ

Port: cluster2-01:e0a (Click the Browse button.)

Domain Names: Leave blank

IP Addresses: Leave blank

Export Name: XYZData

Size: 1 GB

Permission: 0.0.0.0/0





STEP ACTION

7. In Step 3, enter these settings:

User name: vsadmin

Password: Netapp123

Confirm Password: Netapp123

Create a new LIF for SVM management: Select checkbox

Subnet: sn-XYZ

Port: cluster2-01:e0b (Click the Browse button.)





STEP ACTION

9. Verify that the configuration is correct.

10. Click OK.

11. Select Storage Virtual Machines > cluster2.

12. Verify that both SVMs were created and are running.




STEP ACTION

13. Select Storage Virtual Machines > cluster2 > svmXYZ > Configuration > Protocols > NFS.

14. Select Enable to start the NFS service.




STEP ACTION

15. Select Storage Virtual Machines > cluster2 > svmXYZ > Policies > Export Policies.

16. At the bottom of the page, click Edit to change the first rule.

17. Select the Read-Only checkbox.




STEP ACTION

18. Select the Allow Superuser Access checkbox.

19. Click OK.

20. Verify the characteristics of the updated rule.




STEP ACTION

21. Select the default export policy.

22. In the Export Rules panel click Add.




STEP ACTION

23. In the Create Export Rule dialog, enter these settings:

Client Specification: 0.0.0.0/0

Rule Index: 1

Access Protocol: NFS

Read-Only: Select checkbox

Read/Write: Select checkbox

Allow Superuser Access: Select checkbox

24. Click OK.




STEP ACTION

25. Verify the characteristics of the updated rule.


27. Select Network Interfaces.




STEP ACTION

28. Notice the following settings:

The LIF svm123_cifs_lif1 is using the sn-Default subnet and has the IP address

192.168.0.120.

The LIF svmXYZ_nfs_lif1 is using the sn-XYZ subnet and has the IP address

192.168.0.120.

These two LIFs have the same IP address on two different networks.




TASK 6: ACCESS CLIENTS USING DIFFERENT IPSPACES

In this task, you access the 123 Company’s data by way of the CIFS (or SMB) protocol by using the default

IPspace on the Windows client. You then access the XYZ Company’s data by way of the NFS protocol by

using the XYZ IPspace on the Linux client.

STEP ACTION

1. On the administrator desktop, open Windows Explorer.

2. Verify that Windows Explorer is open.

3. Select Computer > Map a Drive.




STEP ACTION

4. In the Map Network Drive dialog, enter these settings:

Drive: Z

Folder: \\svm123\123Data

5. Click Finish.

The share location should appear.




STEP ACTION

6. Create a file in this location to verify write and read access.

7. Next, you will launch the Linux client and access the svmXYZ data by using the XYZ IPspace.

On your Windows desktop, double-click the “link to PuTTY” icon.


9. Select the Linux saved session.




STEP ACTION

10. Click Load.





login as:


User Name: root

Password: Netapp123


#

16. Within Red Hat 6 and later, portmapper is part of rpcbind.

Verify that rpcbind is started.

# service rpcbind status

Sample output:

rpcbind (pid 1060) is running...

17. Verify that the NFS services are running.

# service nfs status

Sample output:

rpc.svcgssd is stopped

rpc.mountd is stopped

nfsd is stopped

rpc.rquotad is stopped




STEP ACTION

18. Start the NFS services.

# service nfs start

Sample output:

Starting NFS services: [ OK ]

Starting NFS quotas: [ OK ]

Starting NFS mountd: [ OK ]

Stopping RPC idmapd: [ OK ]

Starting RPC idmapd: [ OK ]

Starting NFS daemon: [ OK ]

19. Enter this command to verify that the current interface configuration is correct:

# ifconfig -a

Sample output:

eth0 Link encap:Ethernet HWaddr 00:50:56:01:10:BF

inet addr:192.168.0.21 Bcast:192.168.0.255 Mask:255.255.255.0

inet6 addr: fe80::250:56ff:fe01:10bf/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:1256 errors:0 dropped:0 overruns:0 frame:0

TX packets:64 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:103973 (101.5 KiB) TX bytes:7482 (7.3 KiB)

eth1 Link encap:Ethernet HWaddr 00:50:56:01:31:5A

BROADCAST MULTICAST MTU:1500 Metric:1




RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

lo Link encap:Local Loopback

inet addr:127.0.0.1 Mask:255.0.0.0

inet6 addr: ::1/128 Scope:Host

UP LOOPBACK RUNNING MTU:16436 Metric:1





20. Enter this command to configure eth1:

# ifconfig eth1 192.168.0.22 netmask 255.255.255.0 up




STEP ACTION

21. Enter this command to verify that the current interface configuration of eth1 is correct:

# ifconfig –a eth1

Sample output:

eth1 Link encap:Ethernet HWaddr 00:50:56:01:31:5A

inet addr:192.168.0.22 Bcast:192.168.0.255 Mask:255.255.255.0

inet6 addr: fe80::250:56ff:fe01:315a/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1





22. Enter this command to create a static route so that Linux uses eth1 to communicate with svm2:

# ip route add 192.168.0.120/32 dev eth1

23. Enter this command to verify that the static route was created:

# route

Sample output:

Kernel IP routing table

Destination Gateway Genmask Flags Metric Ref Use Iface

192.168.0.120 * 255.255.255.255 UH 0 0 0 eth1

192.168.0.0 * 255.255.255.0 U 0 0 0 eth0

192.168.0.0 * 255.255.255.0 U 0 0 0 eth1

link-local * 255.255.0.0 U 1002 0 0 eth0

24. Enter this command to create a mount point:

# mkdir /mnt/XYZData

25. Enter this command to change directory to the new mount directory:

# cd /mnt

26. Enter this command to mount the export created on SVM2:

# mount 192.168.0.120:/XYZData_NFS_volume /mnt/XYZData

27. Enter this command to change directory to the new mount directory:

# cd XYZData

28. Enter this command to verify that you have write access to the export:

# touch foo

29. Enter this command to verify that you have read access to the export:

# cat foo




STEP ACTION

30. Enter this command to view the contents of the export:

# ls

Sample output:

foo

END OF EXERCISE


clustered data ontap 8.3 update 2, ipspaces self-paced · pdf filenetapp university ....

Documents