vmware vsphere 6.0 on netapp metrocluster · vmware vsphere 6.0 on netapp metrocluster

77
VMware vSphere 6.0 on NetApp MetroCluster September 2016 | SL10214 Version 1.0.1

Upload: dodat

Post on 01-May-2018

337 views

Category:

Documents


4 download

TRANSCRIPT

Page 1: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetAppMetroCluster

September 2016 | SL10214 Version 1.0.1

Page 2: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster2 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

TABLE OF CONTENTS

1 Introduction...................................................................................................................................... 3

2 Lab Environment............................................................................................................................. 6

3 Lab Activities................................................................................................................................... 8

3.1 Tour Environment...................................................................................................................... 8

3.2 Unplanned Switchover: High Availability for Business Continuity.................................... 32

3.3 MetroCluster Healing and Switchback for Disaster Recovery............................................ 45

3.4 Planned Switchover: High Availability for Non-Disruptive Operations.............................. 60

4 Lab Limitations.............................................................................................................................. 74

5 References......................................................................................................................................75

6 Version History.............................................................................................................................. 76

Page 3: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster3 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

1 IntroductionThe combination of VMware infrastructure and NetApp MetroCluster resolves a number of customer challenagesfrom both the server and the storage perspectives. VMware infrastructure provides a robust server consolidationsolution with high application availablity. MetroCluster provides continuous access to your data in a data center,across a campus, or in a metro area.

1 Lab ObjectivesThis lab demonstrates various failure scenarios (host, network, and storage), and identifies NetApp best practicesfor vSphere on MetroCluster.

Page 4: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster4 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

Figure 1-1: VMware vSphere Stretched Cluster on replicating NetApp MetroCluster

Page 5: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster5 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

Figure 1-2: VMware vSphere Stretched Cluster on switched over NetApp MetroCluster

1 PrerequisitesThis lab assumes minimal prior experience with NetApp and VMware products.

Page 6: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster6 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

2 Lab EnvironmentAll of the servers and storage controllers presented in this lab are virtual devices, and the networks thatinterconnect them are exclusive to your lab session. The virtual storage controllers (vsims) offer nearly all thesame functionality as do physical storage controllers, but at a reduced performance profile. Currently, the mainexception between virtual and physical storage controllers is that vsims do not offer HA support.

Figure 2-1:

2 Table of Systems

Host Name Operating System Role/Function IP Address

cluster1 clustered Data ONTAP8.3.1

cluster 1 - Site A 192.168.0.101

cluster1-01 clustered Data ONTAP8.3.1

cluster 1 node 1 192.168.0.111

cluster1-02 clustered Data ONTAP8.3.1

cluster 1 node 2 192.168.0.112

cluster2 clustered Data ONTAP8.3.1

cluster 2 - Site B 192.168.0.102

cluster2-01 clustered Data ONTAP8.3.1

cluster 2 node 1 192.168.0.121

Page 7: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster7 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

Host Name Operating System Role/Function IP Address

cluster2-02 clustered Data ONTAP8.3.1

cluster 2 node 2 192.168.0.122

jumphost Windows Server 2012 R2 primary desktop entrypoint for lab

192.168.0.5

dc1 Windows Server 2008 R2 Active Directory / DNS 192.168.0.253

esx1 VMware vSphere 6.0 ESXhost

Site A host 1 192.168.0.51

esx2 VMware vSphere 6.0 ESXhost

Site A host 2 192.168.0.52

esx3 VMware vSphere 6.0 ESXhost

Site B host 1 192.168.0.53

esx4 VMware vSphere 6.0 ESXhost

Site B host 2 192.168.0.54

vc1 Windows Server 2012 R2 VMware vSphere 6.0vCenter

192.168.0.31

vasa Linux Appliance NetApp VASA Provider 192.168.0.34

ocum Linux Appliance NetApp OnCommandUnified Manager

192.168.0.71

tiebreak Red Hat Ent. Linux 6.5 linux client running NetAppTieBreaker

192.168.0.66

sitea_vm1 Debian Linux nested VM to demonstratesurvivability

192.168.0.41

2 User IDs and Passwords

Host Name User ID Password Comments

jumphost DEMO\Administrator Netapp1! Domain Administrator

cluster1 admin Netapp1! Same for individual clusternodes

svm... vsadmin Netapp1! svm administrator

vasa vpserver Netapp1! Administrator

vc1 [email protected]! Local Admin for vCenter

ocum Administrator or admin Netapp1! OCUM Administrator

tiebreak root Netapp1! Linux Administrator

sitea_vm1 root Netapp1! Linux Administrator

Page 8: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster8 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

3 Lab ActivitiesKey NetApp capabilities will be highlighted:

• Tour Environment on page 8• Unplanned Switchover: High Availability for Business Continuity on page 32• MetroCluster Healing and Switchback for Disaster Recovery on page 45• Planned Switchover: High Availability for Non-Disruptive Operations on page 60

3.1 Tour Environment

This lab activity demonstrates a NetApp MetroCluster setup simulating two sites. This activity familiarizes you withthe various management interfaces available to users of clustered Data ONTAP with MetroCluster enabled.

1. Immediately following the first connection to the lab, there is a powershell script that runs to finishpreparing the lab for initial use. Allow this window to finish running the script before you continue.

1

Figure 3-1:

2. When prepatory script completes, the browser will open. Press Advanced to bypass the invalidcertificate warning.

Page 9: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster9 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

2

Figure 3-2:

3. Click Proceed to vc1.demo.netapp.com.

Page 10: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster10 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

3

Figure 3-3:

4. Enter credentials: DEMO\Administrator with password: Netapp1!5. Click Login.

4

5

Figure 3-4:

6. Click on Hosts and Clusters.

Page 11: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster11 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

6

Figure 3-5:

7. Right click on the VM sitea_vm1, navigate to Power > Power On.

7

Figure 3-6:

8. Select the Recommendation to start the VM on esx1.demo.netapp.com9. Click OK.

Page 12: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster12 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

Note: If you are presented with a warning, press Answer Question, and select I Moved it as ananswer.

8

9

Figure 3-7:

10. If you see a stale warning in the Alarms panel, right click and pick Reset to green to clear it.

10

Figure 3-8:

While the VM starts, note that there are 4 ESX hosts for this lab demonstration: ESX1 and ESX2providing the compute layer at Site A, while ESX3 and ESX 4 are at Site B. However, all four hostsbelong to the same VMware High Availablity (HA) Cluster. This is defined as a stretched vmwarecluster.

11. Right-click on the MCC HA Cluster > Settings .

Page 13: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster13 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

11

Figure 3-9:

12. Select VM/Host Groups under Configuration.13. Note that there are three groups defined, Host Group A, Host Group B, and a VM Group for the

“sitea_vms”.

Page 14: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster14 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

12

13

Figure 3-10:

14. Next click on VM/Host Rules.15. Select sitea_affinity, and click Edit.

Page 15: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster15 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

14

15

Figure 3-11:

16. Examine the rule, then click Cancel.

Page 16: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster16 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

16

Figure 3-12:

17. Minimize the browser with vCenter open, then double-click the link for OnCommand System Manager(NetApp OCSM Cluster1).

Figure 3-13:

18. Log in with: admin and password: Netapp1!.

Page 17: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster17 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

18

Figure 3-14:

19. Navigate to Storage Virtual Machines, click on cluster1.20. Examine the State of each SVM: svm1 is running with configuration state unlocked, while svm2-mc is

stopped and locked.

1920

Figure 3-15:

21. Minimize the browser, then double-click the link for OCSM Cluster2.

Figure 3-16:

22. Log in with: admin and password: Netapp1!

Page 18: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster18 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

22

Figure 3-17:

23. Navigate to Storage Virtual Machines, click on cluster2.24. Examine the State of each SVM: svm2 is running with configuration state Unlocked, while svm1-mc is

stopped and Locked (the opposite of cluster1).

23

24

Figure 3-18:

25. Minimize the browser, then double-click the link Log into OnCommand Unified Manager.

Figure 3-19:

26. Click Advanced to bypass the invalid certificate warning.

Page 19: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster19 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

26

Figure 3-20:

27. Click Proceed to ocum.demo.netapp.com.

Page 20: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster20 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

27

Figure 3-21:

28. Sign in with User Name Administrator(or Admin), and Password Netapp1!.

28

Figure 3-22:

Page 21: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster21 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

29. In the “Availablity” pane in the “Quick Takes” area, click on the 2 under Clusters.

29

Figure 3-23:

30. Click on cluster1.

Page 22: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster22 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

30

Figure 3-24:

31. Click on the Configuration tab, and examine the MetroCluster details.

Page 23: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster23 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

31

Figure 3-25:

32. Click on the tab for MetroCluster Connectivity.33. Examine the map.

Note: This lab does not include bridges or the physical switches, however the switching layerwould display here if it were available.

Page 24: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster24 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

32

Figure 3-26:

34. Next click on the MetroCluster Replication tab, examine the map that identifies the Replication.35. Note that there is a error/warning on an aggregate displayed in orange.

Page 25: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster25 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

35

Figure 3-27:

36. Click on Events, or hover over the issue and click on View Details for more details.37. Select the event then click Acknowledge.

Page 26: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster26 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

3637

Figure 3-28:

38. Click on Mark As Resolved.

Page 27: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster27 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

38

Figure 3-29:

39. All events are cleared, minimize the browser.

Page 28: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster28 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

39

Figure 3-30:

40. Double-click on PuTTY on the desktop.

Figure 3-31:

41. Scroll down to the saved session for tiebreak.42. Double-click Load and Open.

Page 29: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster29 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

41

42

Figure 3-32:

43. Login as root, with password Netapp1!.44. Issue the netapp-metrocluster-tiebreaker-software-cli command: (hint: type netapp then hit tab).

Note: If after entering the command your prompt does not change, type reboot -h now andwait a few minutes. Then log back into the tiebreaker server, and try again.

netapp-metrocluster-tiebreaker-software-cli

Page 30: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster30 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

Figure 3-33:

45. Issue the monitor show -status command.

monitor show -status

46. Examine that all clusters and nodes are set to “true” for Reachable, and State is set to “normal”.

Page 31: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster31 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

46

45

Figure 3-34:

47. For additional details issue the monitor show -stats command.

monitor show -stats

Page 32: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster32 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

47

Figure 3-35:

48. Leave PuTTY open to prepare for the next part of the lab procedures.

3.2 Unplanned Switchover: High Availability for Business Continuity

In this activity you create a site failure on SiteA. This will simulate an Unplanned MetroCluster Swithover event. Inthis activity, you perform the steps to manually Switchover, however in a production environment this functionalitycould be triggered through scripting when specific events occur, and conditions are met.

1. To create the site failure, you need to temporarily move away from inside the lab, and go to the tab thatincludes the lab guide and the Lab Control Panel.

2. Click the Blue FAIL SITE A button.

Page 33: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster33 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

1

2

Figure 3-36:

3. A dialog box appears confirming that ESX1, ESX2, Cluster1-01, and Cluster1-02 nodes will be poweredoff to simulate a site failure. Click OK.

Page 34: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster34 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

3

Figure 3-37:

4. Return to the Remote Desktop tab in the lab, and double-click on PuTTY.5. Double-click on cluster2 in “Saved Sessions”, or highlight cluster2, press Load and Open.

5

Figure 3-38:

6. Login as: User Name admin and password: Netapp1!.7. Issue the metrocluster show command (Hint: type “me”, and tab for autocompletion).

metrocluster show

8. Note that from cluster2, cluster1 is now reporting as “not-reachable”.

Page 35: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster35 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

7

8

Figure 3-39:

9. Keep the PuTTY session to cluster2 open, and return to the PuTTY session to TieBreaker.10. Issue the monitor show -status command.

monitor show -status

11. Examine cluster1, and notice that the nodes in cluster1 are now listed as “false” for reachable.

Page 36: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster36 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

10

11

Figure 3-40:

12. Return to VMware vSphere Web Client, and note that ESX1 and ESX2 are not responding, andsitea_vm1 is disconnected.

Page 37: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster37 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

12

Figure 3-41:

13. Return to the PuTTY session for cluster2.14. Issue the set -privilege advanced command.

set -privilege advanced

15. Press y to continue.16. Issue the metrocluster switchover -simulate command.

metrocluster switchover -simulate

Page 38: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster38 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

14

16

Figure 3-42:

17. Issue the cluster peer show command.

cluster peer show

17

Figure 3-43:

18. Now perform the switchover by issuing the metrocluster switchover -forced-on-disaster command.

metrocluster switchover -forced-on-disaster

19. Press y to continue.

18

Figure 3-44:

Page 39: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster39 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

20. Issue the metrocluster show command.

metrocluster show

20

Figure 3-45:

21. Return to PuTTY with TieBreaker.22. Issue the monitor show -status command.

monitor show -status

23. Examine the state is listed as switchover completed.

Note: Click up and Enter to refresh the Monitor State.

Page 40: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster40 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

22

23

Figure 3-46:

24. Maximize the browser and return to the tab for cluster2, examine that both SVMs are now being servedon cluster2.

24

Figure 3-47:

Page 41: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster41 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

25. Return to VMware vSphere Web Client, and note that the VM is now running from esx3. If it poweredoff, do not attempt to power it on. Once the surviving hypervisors see the storage online they willcomplete the host affinity failure action.

26. Click the refresh button, and wait for the VM Failure Response to return the VM to a powered on state.27. Note that the VM is running from Compute at SiteB, and being served from a replicated version of the

SVM from SiteA, but running on SiteB.

26

Figure 3-48:

28. Return to the OCUM tab, click on Dashboard.

Page 42: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster42 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

28

Figure 3-49:

29. OCUM has a fast notification feature that pulls immediate critical events associated to the MetroCluster.However, other events are subject to the standard 15 minute polling interval. To address this in thedemonstration, go to the Actions dropdown menu, and select rediscover from the Storage > Clusterinventory list.

30. Navigate to cluster2’s MetroCluster Connectivity tab.

Page 43: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster43 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

30

Figure 3-50:

31. Navigate to cluster2’s MetroCluster Replication tab.

Page 44: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster44 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

31

Figure 3-51:

32. Go to “Events”, and examine the events that are being reported. Select all and click Acknowledge.

Page 45: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster45 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

32

Figure 3-52:

3.3 MetroCluster Healing and Switchback for Disaster Recovery

Following an unplanned or planned switchover event, you can perform certain steps to restore the MetroClusterto full health. You must perform healing on data aggregates, and then on the root aggregates. This processresynchronizes the data aggregat and prepares the disaster site for normal operation. In this activity you performthe healing and switchback tasks.

1. Open a PuTTY session to cluster22. Issue the metrocluster show command.

metrocluster show

3. Examine that the Mode for cluster2 is switchover.

2

3

Figure 3-53:

4. If you have an asterisk in the prompt, skip this step, otherwise issue the set -priv advanced command.5. Issue the metrocluster heal -phase aggregates command.6. After the data aggregates have been healed, you must heal the root aggregates in preparation for the

switchback operation. Issue the metrocluster heal -phase root-aggregates command.

metrocluster heal -phase aggregatesmetrocluster heal -phase root-aggregates

Page 46: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster46 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

5

6

Figure 3-54:

7. Now that healing is completed, go back to the “Lab Control Panel” and restart the nodes.8. Press the blue button labeled RESTART SITE A.

Page 47: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster47 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

7

8

Figure 3-55:

9. Click OK to acknowledge that the nodes are restarting.

Page 48: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster48 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

9

Figure 3-56:

10. Return to the lab and open the OCUM tab, select all the events, and click Mark As Resolved.

10

Figure 3-57:

11. Launch a PowerShell window.

11

Figure 3-58:

12. Issue ping -t cluster1, and let it run. Continue to the next step.

ping -t cluster1

Page 49: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster49 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

12

Figure 3-59:

13. Go to the VMware vSphere Web Client tab, click refresh a few times over about 1-2 minutes, andESX1 and ESX2 will come online. Note that the storage is still online since the VMware datastores arebeing served from the replicated copy of the SVM on SiteB.

14. Right click on sitea_vm1, click Migrate.

Page 50: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster50 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

13

14

Figure 3-60:

15. Choose Change compute resources only, click Next.

Page 51: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster51 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

15

Figure 3-61:

16. Select esx1, and click Next.

16

Figure 3-62:

17. Click Next.

Page 52: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster52 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

Figure 3-63:

18. Click Next.

Figure 3-64:

19. Click Finish.

Page 53: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster53 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

Figure 3-65:

20. The VM now relocates back to a compute host at SiteA, while the SVM is still serving the datastorefrom SiteB.

20

Figure 3-66:

21. By this point the PowerShell’s continuous ping may demonstrate that the management LIF for cluster1is available. If not, wait for it to become reachable, then close the PowerShell window.

Page 54: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster54 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

Figure 3-67:

22. Return to the TieBreaker PuTTY session, and issue the monitor show -status command.

monitor show -status

23. Examine the cluster1 state.

Page 55: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster55 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

22

Figure 3-68:

24. Return to the PuTTY session to cluster2 and issue the cluster peer show command.

cluster peer show

24

Figure 3-69:

25. Issue the metrocluster show command.

metrocluster show

Page 56: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster56 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

25

Figure 3-70:

26. If you have an asterisk in the prompt, skip this step, otherwise issue the set -priv advanced command.27. Issue the metrocluster switchback -simulate command.

set -priv advmetrocluster switchback -simulate

27

Figure 3-71:

28. After confirming that the operation was successful, issue the metrocluster switchback command.

metrocluster switchback

29. Click y.

28

Figure 3-72:

30. Issue the metrocluster show command.

metrocluster show

Page 57: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster57 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

30

Figure 3-73:

31. Return to OCSM for cluster2, refresh the SVM state, and examine that svm1-mc is now stopped.

31

Figure 3-74:

32. Log back into OCSM for cluster1, refresh the SVM state, and examine that svm1 is running.

32

Figure 3-75:

Page 58: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster58 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

33. Return to TieBreaker, and issue the monitor show -status command.

monitor show -status

34. Note the state is now “normal” and “true” for reachable.

33

34

Figure 3-76:

35. Return to OCUM, and examine any events listed.36. Select Events, and click Acknowledge.

Page 59: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster59 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

36

Figure 3-77:

37. Keep events selected, and click Mark As Resolved.

37

Figure 3-78:

Page 60: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster60 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

3.4 Planned Switchover: High Availability for Non-Disruptive Operations

A planned or negotiated switchover event can be used in Non-Disruptive Opeartions (NDO). A negotiatedswitchover cleanly shuts down processes on the partner site and then switches over operations from the partnersite. You can use negotiated switchover to perform maintenance on a MetroCluster site or test the switchoverfunctionality. If you want to test the MetroCluster functionality or to perform planned maintenance, you canperform a negotiated switchover in which one cluster is cleanly switched over to the partner cluster. You can thenheal and switch back the configuration.

Rather than a forced switchover when one of the clusters is not reachable, this event involves performing thenegotiated switchover prior to beginning the controlled power off event. In this activity you migrate the VM tocompute at SiteB, and have the NetApp MetroCluster serve storage from SiteB in a controlled manner.

1. From VMware vSphere Web Client, right-click on sitea_vm1, and select Migrate.

1

Figure 3-79:

2. Click the Change compute resource only button, and click Next.

Page 61: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster61 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

2

Figure 3-80:

3. Under the Hosts > Filter tab, select esx3.

3

Figure 3-81:

4. Click Next.

Page 62: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster62 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

Figure 3-82:

5. Click Next.

Figure 3-83:

6. Click Finish.

Page 63: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster63 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

Figure 3-84:

7. After the VM task finishes migrating, right click on ESX1, go to Power > Shut Down.

7

Figure 3-85:

8. Enter MCC Test for a reason, and click OK.

Page 64: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster64 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

8

Figure 3-86:

9. Right click on ESX2, go to Power > Shut Down.

Page 65: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster65 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

9

Figure 3-87:

10. Enter MCC Test for a reason, and click OK.

Page 66: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster66 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

10

Figure 3-88:

11. Return to PuTTY on cluster2.12. If you have an asterisk in the prompt, skip this step, otherwise issue the set -priv advanced command.13. You can use the -simulate option to preview the results of a switchover. A verification check gives you a

way to ensure that most of the preconditions for a successful run are met before you start the operation.Issue the metrocluster switchover -simulate command.

set -priv advmetrocluster switchover -simulate

13

Figure 3-89:

14. Issue the metrocluster switchover command.

metrocluster switchover

15. Enter y.

Page 67: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster67 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

14

Figure 3-90:

16. Return to the PuTTY session for TieBreaker, and issue the monitor show -status command.17. Examine the monitor state. It may state that it is unable to reach cluster “cluster1”. If so, issue the

monitor show -status command again.

monitor show -status

16

Figure 3-91:

18. After running the monitor show -status command again, examine that the monitor state changes to“MCC in switched over state”.

Page 68: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster68 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

18

Figure 3-92:

19. Return to the tab for VMware vSphere Web Client, and observe that the VM is running.

19

Figure 3-93:

20. Return to the tab for OCSM for cluster 2, click Refresh to see that “svm1-mc” is running.

Page 69: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster69 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

20

Figure 3-94:

21. Return to the OCUM tab to examine reported events.22. Note that there are fewer events being reported, because this was a negotiated switchover.

22

Figure 3-95:

23. Click on the cluster2 tab for MetroCluster Connectivity to see that Connectivity is impacted.

Page 70: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster70 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

23

Figure 3-96:

24. Check the “Last Refreshed Time” for cluster1. Optionally, you can wait to get to the “15 Mins Ago” tosee what changes occurred.

Page 71: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster71 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

24

Figure 3-97:

25. Navigate to the “cluster2” MetroCluster Connectivity tab.

Page 72: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster72 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

25

Figure 3-98:

26. Navigate to the “cluster2” MetroCluster Replication tab.

Page 73: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster73 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

26

Figure 3-99:

27. Following the switchover event the nodes for cluster1 have powered themselves down. You can confirmthis by attempting to PuTTY to cluster1, ping cluster1, or try to connect to OCSM for cluster1.

28. Go to OCUM Events, select all and click Acknowledge.

28

Figure 3-100:

Page 74: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster74 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

4 Lab LimitationsThis lab has the following limitations:

• All of the servers and storage controllers presented in this lab are virtual devices. Consequently, anyoperations involving movement of large quantities of data will not exhibit performance representative ofreal systems.

Page 75: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster75 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

5 ReferencesThe following references were used to create this lab guide.

• http://mysupport.netapp.com/documentation/docweb/index.html?productID=62093&language=en-US• http://www.netapp.com/us/media/tr-4128.pdf• https://library.netapp.com/ecm/ecm_download_file/ECMP12454947• https://library.netapp.com/ecm/ecm_download_file/ECMP12458277

Page 76: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

VMware vSphere 6.0 on NetApp MetroCluster76 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

6 Version History

Version Date Document Version History

1.0.0 Sep 2015 Initial Release

1.0.1 Oct 2015 Added more context

1.0.2 Dec 2015 Added note about nested VM andrebooting tiebreaker

Page 77: VMware vSphere 6.0 on NetApp MetroCluster · VMware vSphere 6.0 on NetApp MetroCluster

Refer to the Interoperability Matrix Tool (IMT) on the NetApp Support site to validate that the exactproduct and feature versions described in this document are supported for your specific environment.The NetApp IMT defines the product components and versions that can be used to constructconfigurations that are supported by NetApp. Specific results depend on each customer's installation inaccordance with published specifications.

NetApp provides no representations or warranties regarding the accuracy, reliability, or serviceability of anyinformation or recommendations provided in this publication, or with respect to any results that may be obtainedby the use of the information or observance of any recommendations provided herein. The information in thisdocument is distributed AS IS, and the use of this information or the implementation of any recommendations ortechniques herein is a customer’s responsibility and depends on the customer’s ability to evaluate and integratethem into the customer’s operational environment. This document and the information contained herein may beused solely in connection with the NetApp products discussed in this document.

Go further, faster®

© 2016NetApp, Inc. All rights reserved. No portions of this document may be reproduced without prior written consentof NetApp, Inc. Specifications are subject to change without notice. NetApp, the NetApp logo, Data ONTAP®,ONTAP®, OnCommand®, SANtricity®, FlexPod®, SnapCenter®, and SolidFire® are trademarks or registeredtrademarks of NetApp, Inc. in the United States and/or other countries. All other brands or products are trademarks orregistered trademarks of their respective holders and should be treated as such.