table of contents - vmwaredocs.hol.vmware.com/hol-2017/hol-1708-chg-3_pdf_en.pdf · table of...

Table of ContentsLab Overview - HOL-1708-CHG-3 - Virtual SAN 6.2: Challenge Lab ..................................2

Lab Guidance .......................................................................................................... 3Module Switcher...................................................................................................... 8

Challenge 1 - Set Up a Virtual SAN Cluster (15 Mins)...................................................... 10Introduction........................................................................................................... 11Module Switcher.................................................................................................... 12Create A Virtual SAN Cluster ................................................................................. 13

Challenge 2 - Recover Host Failure (15 Mins).................................................................. 16Introduction........................................................................................................... 17Module Switcher.................................................................................................... 18Key Concepts For This Challenge .......................................................................... 19Challenge 2: Recover From Host Failure................................................................ 20

Challenge 3 - Troubleshoot VSAN Multicast Layer 2 Issues (15 Mins) .............................23Introduction........................................................................................................... 24Module Switcher.................................................................................................... 25Challenge 3: Recover From Network Partition ....................................................... 26

Challenge 4 - VSAN Stretched Cluster Creation & Optimization (15 Mins) ......................28Introduction........................................................................................................... 29Module Switcher.................................................................................................... 30Create A Stretched Cluster.................................................................................... 31

Appendix - Hints and Solutions ....................................................................................... 33Challenge 1 - Hints and Solutions ......................................................................... 34Challenge 2 - Hints and Solutions ......................................................................... 49Challenge 3 - Hints and Solutions ......................................................................... 64Challenge 4 - Hints and Solution ........................................................................... 68

HOL-1708-CHG-3

Page 1HOL-1708-CHG-3

Lab Overview -HOL-1708-CHG-3 - VirtualSAN 6.2: Challenge Lab

HOL-1708-CHG-3


Lab GuidanceNote: It will take more than 60 minutes to complete this lab,

This is a VSAN challenge lab and it consists of 4 challenges. Eachchallenge requires working knowledge of VMware Virtual SAN. Wehighly recommend taking HOL-1708-SDC-1 in case you are new toVirtual SAN.

Challenge 1 is mandatory and need to finished to be able to move toChallenge 2 or Challenge 3.

Challenge 2 or 3 can be taken in any order as you prefer. Challenge 4 should be attempted at the last.

You can use the Table of Contents to access any module of your choosing.

The Table of Contents can be accessed in the upper right-hand corner of theLab Manual.

Lab Abstract: VSAN is "radically simple" to setup and get going, but how aboutconfiguring it for advanced use-cases, troubleshooting performance and availabilityissues? In this lab you will be challenged to optimize VSAN for stretch-cluster use casesand to recover from misconfiguration issues - learn how to troubleshoot VSAN andrestore it to full health.

Lab Module List:

Challenge 1 - Set Up a VSAN Cluster (15 minutes) (Basic) Challenge 2 - Recover Host Failure (15 minutes) (Beginner) Challenge 3 - Troubleshoot VSAN Multicast Layer 2 Issues (15 minutes)

(Advanced) Challenge 4 - VSAN Stretched Cluster Creation & Optimization(15

minutes) (Beginner)

Lab Captains:

Module 1 - Mousumi Mullick, Sr MTS, Palo Alto Module 2 - Mousumi Mullick, Sr MTS, Palo Alto Module 3 - Mousumi Mullick, Sr MTS, Palo Alto Module 4 - Mousumi Mullick, Sr MTS, Palo Alto

This lab manual can be downloaded from the Hands-on Labs Document site found here:

[http://docs.hol.pub/HOL-2017]

HOL-1708-CHG-3


cme-export/hol-1708-chg-3_pdf_en/[http:/docs.hol.pub/HOL-2017]

This lab may be available in other languages. To set your language preference and havea localized manual deployed with your lab, you may utilize this document to help guideyou through the process:

http://docs.hol.vmware.com/announcements/nee-default-language.pdf

Location of the Main Console

1. The area in the RED box contains the Main Console. The Lab Manual is on the tabto the Right of the Main Console.

2. A particular lab may have additional consoles found on separate tabs in the upperleft. You will be directed to open another specific console if needed.

3. Your lab starts with 90 minutes on the timer. The lab can not be saved. All yourwork must be done during the lab session. But you can click the EXTEND toincrease your time. If you are at a VMware event, you can extend your lab timetwice, for up to 30 minutes. Each click gives you an additional 15 minutes.Outside of VMware events, you can extend your lab time up to 9 hours and 30

minutes. Each click gives you an additional hour.

Activation Prompt or Watermark

When you first start your lab, you may notice a watermark on the desktop indicatingthat Windows is not activated.

One of the major benefits of virtualization is that virtual machines can be moved andrun on any platform. The Hands-on Labs utilizes this benefit and we are able to run the

HOL-1708-CHG-3


http://docs.hol.vmware.com/announcements/nee-default-language.pdf

labs out of multiple datacenters. However, these datacenters may not have identicalprocessors, which triggers a Microsoft activation check through the Internet.

Rest assured, VMware and the Hands-on Labs are in full compliance with Microsoftlicensing requirements. The lab that you are using is a self-contained pod and does nothave full access to the Internet, which is required for Windows to verify the activation.Without full access to the Internet, this automated process fails and you see this

watermark.

This cosmetic issue has no effect on your lab.

Alternate Methods of Keyboard Data Entry

During this module, you will input text into the Main Console. Besides directly typing itin, there are two very helpful methods of entering data which make it easier to entercomplex data.

Click and Drag Lab Manual Content Into Console ActiveWindow

An error occurred.Try watching this video on www.youtube.com, or enableJavaScript if it is disabled in your browser.

HOL-1708-CHG-3


You can also click and drag text and Command Line Interface (CLI) commands directlyfrom the Lab Manual into the active window in the Main Console.

Accessing the Online International Keyboard

You can also use the Online International Keyboard found in the Main Console.

1. Click on the Keyboard Icon found on the Windows Quick Launch Task Bar.

Click once in active console window

In this example, you will use the Online Keyboard to enter the "@" sign used in emailaddresses. The "@" sign is Shift-2 on US keyboard layouts.

1. Click once in the active console window.2. Click on the Shift key.

HOL-1708-CHG-3


Click on the @ key

1. Click on the "@" key.

Notice the @ sign entered in the active console window.

Look at the lower right portion of the screen

Please check to see that your lab is finished all the startup routines and is ready for youto start. If you see anything other than "Ready", please wait a few minutes. If after 5minutes you lab has not changed to "Ready", please ask for assistance.

HOL-1708-CHG-3


Module SwitcherIn the VSAN Challenge lab, Module switcher application is vital in preparing thesuccessive challenges presented in this lab.

1. VSAN Challenge lab consists of 4 Challenges.2. Challenge 1 is mandatory and a pre-requisite for the successive challenges.

That is a student MUST finish Challenge 1 in order to accept the sussesivechallenges in this lab.

3. Challenge 2 and Challenge 3 can be accepted in any order.4. Challenge 4 is recommended to be attempted at last. Once Challenge 4 is

completed, student should not go back to earlier challenges.

Start Module Switcher

Open the folder named "Module Switchers" on the desktop Double click the module named "3 HOL-1708-SDC-3 - VSAN Challenge"

HOL-1708-CHG-3


Working with Module Switcher

It is a must that the student takes Module 1 aka Challenge 1 at the beginning andthen switch to Module 2 or 3.

Switching to a specific module is as simple as clicking on "Start" button for thatmodule.

HOL-1708-CHG-3


Challenge 1 - Set Up aVirtual SAN Cluster (15

Mins)

HOL-1708-CHG-3


IntroductionVirtual SAN is a hyper-converged, software-defined storage solution for the software-defined data center. It is a distributed storage solution that enables rapid provisioning ofstorage within VMware vCenter Server as part of virtual machine creation anddeployment operations. Virtual SAN uses the concept of disk groups to pool togetherlocally attached flash devices and magnetic disks as management constructs. Diskgroups are composed of at least one cache device and one or more magnetic or flashcapacity devices.

In Hybrid architectures, flash devices are used as read cache and write buffer in front ofmagnetic disks to optimize virtual machine and application performance. In all flashVirtual SAN high endurance flash is used as cache device while leveraging lower costSSD as capacity devices. Virtual SAN datastore aggregates disk groups across all hostsin the cluster to form a single shared datastore for all hosts in the cluster.

Prerequisites

This challenge assumes a certain level of VSAN familiarity. Specifically basic experiencein the following is suggested.

VSAN configuration VSAN fault domains VSAN metro cluster VSAN networking fundamentals Storage policy based management

HOL-1708-CHG-3


Module SwitcherStart Module 1

Start Module Switcher

Open the folder named "Module Switchers" on the desktop Double click the module named "3 HOL-1708-SDC-3- VSAN Challenge"


You MUST take Module 1 before you proceed with Module 2, 3 or 4. It is amandatory that the student takes Module 1 aka Challenge 1 at the beginning andthen switch to Module 2, 3 or 4.


HOL-1708-CHG-3


Create A Virtual SAN ClusterWhat you need to know about the lab environment

This lab environment presents cluster RegionA01-COMP01 with 3 hosts (esx01a,esx02a & esx03a) equipped with all flash disks.

All three hosts have VSAN VMkernel networking already configured, meaning theVMkernel interfaces for Virtual SAN traffic has already been configured.

Log In To vSphere Web Client

Click on the Chrome browser on the desktop and it will open vSphere Web Client.

1. Check the box "Use Windows session authentication".2. Click on "Login".

HOL-1708-CHG-3


Your Challenge: Create A Virtual SAN Cluster Challenge

Perform the steps listed below in order to begin the challenge

1. Configure Virtual SAN ( Hint1HInt2)2. Add disks to storage is set to Manual (Hint)3. DO NOT enable Deduplication & Compression.(Hint)4. Choose to configure Fault Domains (Hint)5. Select disks to be claimed for cache and capacity in the VSAN cluster.(Hint)6. Create three fault domains namely FD1, FD2 & FD3 each consisting of esx-01a,

esx02a, esx03a respectively.(Hint1Hint2)7. Review your selection & complete the work flow to enable VSAN. Refresh Web

client to monitor the changes in the Virtual SAN Admin page.(Hint1Hint2)8. Check the vsanDatastore size ( Hint:Datastores > ReginA01-VSAN-COMP01 -

>Manage > Settings > VSANDatastore > General )9. Check the fault domains created in previous steps. ( Hint: Cluster

RegionA01-COMP01 -> Manage -> Settings -> Fault Domains & Stretched Cluster)10. Verify the vsanDatastore (RegionA01-VSAN-COMP01) has been created. (Hint)

Your Challenge: Enable Deduplication and Compression

Perform the following steps to enable Deduplication and Compression inRegionA01-COMP01 VSAN Cluster.

1. Edit Virtual SAN Settings ( Hint: Click on the Cluster RegionA01-COMP01 ->Manage -> Settings -> Virtual SAN -> General) (Hint)

2. Enable Deduplication and Compression. (Hint)3. DO NOT enable "Reduced Redundancy" (Hint)4. Monitor progress in Cluster RegionA01-COMP01 -> Monitor -> Task tab.(Hint)5. Confirm that deduplication and compression has been enabled. (Hint)

Your Challenge: Migrate Virtual Machine With "HOLDefault Storage Policy"

Perform the following list of steps:

1. Select VM linux-micro-01a registered in host esx05a.corp.local.(Hint1)2. Migrate the virtual machine "linux-micro-01ato host esx02a.corp.local under

Cluster "RegionA01-COMP01" to VSAN datastore "RegionA01-VSAN-COMP01" ( Hint: Right click on the virtual machine-> Migrate). (Hint1)

3. Choose"VM Storage Policy" as "Virtual SAN Default Storage Policy" (Hint:Drop Down VM Storage Policy) (Hint1)

4. Choose Destination Network as VM-RegionA01-vDS-COMP (Hint)5. Finish migration of the virtual machine. (Hint)6. Power on virtual machine "linux-micro-01a".

HOL-1708-CHG-3


7. Verify the VM Linux-micro-01a is compliant with "Virtual SAN Default StoragePolicy" (Hint: VM linux-micr0-01a -> Manage -> Policies).(Hint)

HOL-1708-CHG-3


Challenge 2 - RecoverHost Failure (15 Mins)

HOL-1708-CHG-3


IntroductionThe second challenge is a work flow divided into three steps, each highlighting veryimportant steps in setting up a functioning VSAN cluster, troubleshooting basics of VSANnetworking, and how to monitor and remediate a failure scenario.

1. Add a new host into the cluster2. Troubleshoot VSAN networking issues.3. Monitoring Virtual SAN health and Remediate.

HOL-1708-CHG-3


Module Switcher Start Module 2. It is mandatory that the student finishes Module 1 aka Challenge 1 to

proceed with Module 2.


Do not click on Start Module 2 in Module switcher, unless you havecompleted Module 1 aka Challenge 1. It is a must that the student takesModule 1 aka Challenge 1 at the beginning and then switch to Module 2, 3 or 4..


To start Challenge 2, click on Start for Module 2 button in Module Switcher.

HOL-1708-CHG-3


Key Concepts For This ChallengeFew essentials points to keep in mind before accepting this challenge to Recover A Clusterfrom Host Failure:

Virtual SAN Needs minimum of 3 hosts, each host contributing at least 1 SSD and1 MD in case of hybrid cluster ( For All Flash at least 2 SSDs for cache andcapacity tier respectively).

Minimum 3 hosts in a cluster is needed for the Virtual Machines to be compliantwith a VSAN Default Storage Policy. If one of the 3 hosts goes down, VM will stillremain accessible (HA could restart the VM if it is registered on the failed host).VM/VMs will be NONCOMPLIANT.

To form a Virtual SAN cluster the hosts must be part of a Virtual SAN network andmust be on the same subnet whether the hosts contribute storage or not. VirtualSAN requires a dedicated VMkernel port type for Virtual SAN traffic between thehosts.

Need dedicated VMkernel NIC for Virtual SAN traffic.

HOL-1708-CHG-3


Challenge 2: Recover From Host FailureRun Module 2 prep script in Module Switcher on ControlCenter Desktop

Click on Start under Module 2 and wait for it to finish.

Log Into vSphere Web Client

Login to vSphere web client by checking "Use Windows session authentication".

HOL-1708-CHG-3


Host esx01a Failure

We can see that ESXi host esx01a.corp.local is not responding. As we have understood from previous slides that VSAN cluster is not in healthy

state since it has only 2 live hosts out of the 3 hosts in the cluster.

VM Compliance

A VM in this cluster needs 3 active fault domains in order to be compliant withVirtual SAN Default Storage Policy.

Since ESXi host esx01a is down, this leaves only two active fault domains in thecluster.

Hence VM linux-micro-01a in a noncompliant state as seen in the screen shot.

HOL-1708-CHG-3


Your Challenge

Your challenge is to bring the VM back into compliance.

Here are some of the actions you may try to make the VM compliant with the existingVSAN Default Storage Policy.

Move ESXi host esx-04a into Cluster "RegionA01-COMP01". Hint1 Hint2 Hint3 Exit host esx-04a from maintenance mode. Hint1 Ensure VSAN networking on host esx04a.corp.local is configured correctly. Hint1 Add host esx-04a to fault domain FD1. Hint1 Verify host esx-04a has joined the VSAN cluster using Health UI under Cluster ->

Monitor -> Virtual SAN. Hint1 Hint2 The same can be verified using RVC command vsan.cluster_info. Hint1 Take remedial action as dictated by Health UI, if not already done. Hint1 Run "Retest" in Health UI to confirm network connectivity. Hint1 Monitor the data health in Health UI and take action to fix the Virtual SAN

object health. Hint1 Create a Disk Group on esx04a. Hint1 Retest Health UI. Hint1 Check VM compliance and ensure it is compliant with VSAN Default Storage

Policy. Hint1 Power on host esx01-a.corp.local from the console access given in the

lab environment.Hint1 Refresh vSphere web client until host esx01a.corp.local is live. Hint1 You might want to retest the VSAN Health UI and confirm the health of the cluster.

Congratulations!!! You have successfully completed Challenge 2.

Note: DO NOT forget to power on host esx-01a.corp.local at the end of thischallenge.

HOL-1708-CHG-3


Challenge 3 -Troubleshoot VSAN

Multicast Layer 2 Issues(15 Mins)

HOL-1708-CHG-3


IntroductionThis VSAN challenge lab module will focus on one of our most popular troubleshootingtopics -- Layer 2 Multicast feature. Many Virtual SAN errors can be traced back toimproperly configured multicast settings and IP Multicast is a fundamental requirementof Virtual SAN.

Virtual SAN networking requirement of Layer 2 Multicast leverages multicast forwardingfor a portion of its network traffic. The goal of this challenge is to learn the basics ofLayer 2 Multicast functionality in Virtual SAN, how they are tightly integrated with Layer2 networking.

Key Concepts

Virtual SAN employs a highly available clustered metadata database andmonitoring service (CMMDS). Keeping this database in sync with all the hosts inthe cluster would require a considerable amount of unicast network bandwidth.

By utilizing IP multicast Virtual SAN significantly reduces network bandwidthneeded for sending metadata updates to all the hosts in the cluster. Virtual SANdepends on IP multicast communication for the process of joining and leavingcluster groups as well as other intra-cluster communication services.

IP multicast must be enabled and configured in the IP Network segments that willcarry the Virtual SAN traffic service. Since multicasting allows the data to be sentonly once, this has the benefit of freeing up computing resources from the sourceESXi host.

In order to efficiently make use of IP multicast IGMP Snooping and an IGMPQuerier can be leveraged to send multicast traffic to only a subset of switch portsthat have devices attached that request it. This will avoid causing unnecessaryload on other network devices as they will not have to process packets that theyhave not solicited.

HOL-1708-CHG-3


Module Switcher It is mandatory that the student finishes Module 1 aka Challenge 1 to

proceed with Module 3.


Do not click on Start Module 3 in Module switcher, unless you havecompleted Module 1 aka Challenge 1. It is a must that the student takesModule 1 aka Challenge 1 at the beginning and then switch to Module 2, 3 or 4..

To accept Challenge 3, click on Start button for Module 3.

HOL-1708-CHG-3


Challenge 3: Recover From NetworkPartitionIf all ESXi hosts in the cluster cannot communicate with each other, a Virtual SAN clusterwill split into multiple network partitions. Hosts belonging to one partition will not beable to communicate with the hosts in another partition.

When this occurs, Virtual SAN objects may become unavailable until the networkmisconfiguration is resolved. For smooth operations of production Virtual SAN clusters, itis very important to have a stable network with no extra network partitions

Run Module 3 prep script in Module Switcher on ControlCenter Desktop

Click on Start under Module 2 and wait for it to finish.

Log Into vSphere Web Client

Login to vSphere web client by checking "Use Windows session authentication".

HOL-1708-CHG-3


Your Challenge

Your challenge is to resolve network partition and bring the cluster into a healthy state.

Here are some of the actions you may explore in order to resolve the issue:

1. Run "Retest" under VSAN Health UI to check cluster health status. Hint12. From the network health status, check if the cluster has encountered network

partition. Hint13. You may want to check multicast IP settings in VSAN Health UI. Hint14. Verify multicast IP settings on the problematic host(s) using esxcli commands and

correct it if necessary. Hint15. Run "Retest" in VSAN Health UI and verify that the cluster is healthy. Hint1

Key Concepts Gained From Challenge 3

Requirement of different multicast master/agent IP addresses in the same layer 2domain if it contains multiple VSAN clusters

The Master Group Multicast address is used for updating CMMDS between themaster and the backup nodes via port 12345. The Agent Group Multicast Addressis used for sending heartbeats to all the nodes in the cluster via port 23451

HOL-1708-CHG-3


Challenge 4 - VSANStretched Cluster

Creation & Optimization(15 Mins)

HOL-1708-CHG-3


IntroductionThis challenge focuses on the concept of Virtual SAN stretched cluster concept.Stretched cluster is similar to fault domain in some respects but the nodes are placed intwo fault domains that lie in two different sites. This ensures that Virtual Machines areavailable even in the event of a catastrophic outage in one of the sites.

In this challenge you will be responsible for creating a stretched cluster using 4 ESXinodes and a fifth witness node that lies outside the VSAN cluster.

HOL-1708-CHG-3


Module SwitcherMandatory to have finished Module 1 aka Challenge 1 to proceed with thismodule


Do not proceed with this module, unless you have completed Module 1aka Challenge 1. It is a must that the student takes Module 1 aka Challenge 1at the beginning to proceed further.

To accept Challenge 3, click on Start button for Module 3.

HOL-1708-CHG-3


Create A Stretched ClusterBefore we start off to create a Virtual SAN stretched cluster let us quickly understand afew concepts.

Key Concepts

Virtual SAN Stretched Cluster is a specific configuration implemented in environmentswhere disaster/downtime avoidance is a key requirement.

Stretched clusters build on fault domains and provide the capability of data centerawareness. Virtual SAN Stretched Clusters can now provide availability for virtualmachines even if a data center suffers a catastrophic outage.

Virtual SAN stretched clusters need a dedicated ESXi host for the role of a "witness" tohost witness component of virtual machine objects. The witness must have connectionto both the master Virtual SAN node and the backup Virtual SAN node to join the cluster.

Login To vSphere Web Client

Click on "Use Windows session authentication"

Click on "Login"

Your Challenge

Your challenge is to convert the existing All-Flash standard Virtual SAN cluster to astretched cluster with two hosts each in "Preferred Site" (esx-01a & esx-02a) and"Secondary" sites (esx-03a & esx-04a).

You would need another host outside the VSAN cluster RegionA01-COMP01 whichcan be used as a witness node. You can choose esx-07a.corp.local under cluster"VSAN-Witness-Cluster" as witness host. ( Hint.)

HOL-1708-CHG-3


Start the challenge with navigating to cluster "RegionA01-COMP01" -> Manage ->Settings. ( Hint )

Expand Virtual San drop down from the left pane and select "Fault Domain &Stretched Cluster" ( Hint )

Create Preferred and Secondary fault domains ( Hint1& Hint2 ) Select witness node and create disk group in witness node ( Hint1& Hint2 ) Create stretch cluster. ( Hint ) Please ensure that the existing VM "linux-micro-01a" is compliant after creating

the stretch Virtual SAN cluster ( Hint1& Hint2 ) Check Virtual SAn cluster health status ( Hint ) Monitor the deduplication stats ( Hint )

Conclusion

Congrats!! You have successfully completed the challenge. You should now be proficientat implementing Virtual SAN stretched cluster.

HOL-1708-CHG-3


Appendix - Hints andSolutions

HOL-1708-CHG-3


Challenge 1 - Hints and SolutionsHere are the hints and solutions for the first challenge.

Create A Virtual SAN Cluster

Once our network adapters are in place we can configure Virtual SAN at the Clusterlevel.

Select RegionA01-COMP01 then navigate to Manage > Settings > Virtual SAN >General > Configure

Back to Your Challenge: Create A Virtual SAN Cluster Challenge

HOL-1708-CHG-3


Enable Virtual SAN

Add disks to storage is set to Manual

Select Configure fault domains radio button

Click Next


HOL-1708-CHG-3


Verify Virtual SAN Network Settings

Checks have been put in to verify that there are VMKernel adapters configured and theVSAN network service is Enabled.

Click Next


HOL-1708-CHG-3


Claim Disks For Disk Groups

Select which disks should be claimed for cache and which for capacity in theVSAN cluster.

The disks are grouped by model and size or by host. The recommendedselection has been made based on the available devices in your environment.

You can expand the lists of the disks for individual disk selection.

Click Next


HOL-1708-CHG-3


Fault Domains

Click on the green + icon which will open a dialog box as shown in the screen. Create three fault domains namely FD1, FD2 & FD3 each consisting of esx-01a,

esx02a, esx03a respectively.


HOL-1708-CHG-3


Create Fault Domains

Click Next


Create Virtual SAN Cluster

Review and verify your selection.

Click Finish


HOL-1708-CHG-3


Refresh Display

Click the Refresh icon to see the changes. ( If you see Misconfiguration detectedyou may need to Refresh a couple of times )

After the refresh you should see all 3 hosts in the Virtual SAN cluster

Note : In all-flash configurations, flash devices used as capacity must be manuallytagged prior to use. This is detailed in the VSAN 6.0 Product Documentation.


HOL-1708-CHG-3


Virtual SAN - Disk Management

Select Virtual SAN ->Disk Management

The Virtual SAN Disk Groups on each of the ESXi hosts are listed.


HOL-1708-CHG-3


Fault Domains


HOL-1708-CHG-3


vsanDatastore Properties

A vsanDatastore has also been created.

To see the capacity navigate to Datastores > ReginA01-VSAN-COMP01 ->Manage> Settings > VSANDatastore > General

The capacity shown is an aggregate of the capacity devices taken from each of the ESXihosts in the cluster (less some vsanDatastore overhead). The flash devices used ascache are not considered when the capacity calculation is made.


HOL-1708-CHG-3


Enable Deduplication & Compression

Back to Your Challenge: Enable Deduplication and Compression

Enable Deduplication


HOL-1708-CHG-3


Monitor Progress


Deduplication Status


HOL-1708-CHG-3


Migrate Virtual Machine With VSAN Default Storage Policy

Back to Your Challenge: Migrate Virtual Machine With "HOL Default Storage Policy"

Choose Migration Type


HOL-1708-CHG-3


Choose Destination Host


Choose Destination Datastore


HOL-1708-CHG-3


Choose VM Network

Click Next & Finish the Operation.


Verify Virtual SAN Default Storage Policy


HOL-1708-CHG-3


Challenge 2 - Hints and SolutionsAdd A New Host to cluster RegionA01-COMP01

Right click on host esx04a.corp.local and click on "Move To..."

Back To Challenge 2

HOL-1708-CHG-3


Cluster RegionA01-COMP01

Click OK.

Back To Challenge 2

HOL-1708-CHG-3


Move Host Into VSAN Cluster

Click Ok.

Back To Challenge 2

HOL-1708-CHG-3


Exit Maintenance Mode

Right click on host esx04a.corp.local Navigate to "Maintenance Mode" Click on "Exit Maintenance Mode"

Back To Challenge 2

HOL-1708-CHG-3


Add Host to Fault Domain

Click on cluster RegionA01-COMP01 -> Manage -> Virtual SAN -> Fault Domains& Stretched Cluster

1. Click on fault domain FD12. Hover on icon tagged number 2, which shows "Move hosts into selected fault

domain". Click on the icon.3. Check the box of esx04a.corp.local to add it into fault domain FD14. Click Ok

Back To Challenge 2

HOL-1708-CHG-3


Health UI To Detect Failures

Click on cluster RegionA01-COMP01 -> Monitor -> Virtual SAN -> Health Expand "Network" health Take note of the failures

Back To Challenge 2

HOL-1708-CHG-3


Troubleshooting Network Health

Although host esx04a has joined the VSAN cluster but it in a network partitionedstate, which is evident from the "Health UI" tab under Cluster-> Monitor -> VirtualSAN -> Health.

esx04a is in "Partition 1", where as the rest of the 2 hosts are in "Partition 2".

Back To Challenge 2

HOL-1708-CHG-3


RVC Command

We can also see from the RVC command (/localhost/RegionA01> vsan.cluster_infocomputers/RegionA01-COMP01/) output that esx04a networking is not configured.

Back To Challenge 2

HOL-1708-CHG-3


Fix VMkernel Port Settings

1. Click on host esx04a.corp.local2. Click on Manage tab3. Click on Networking tab4. Click on VMkernel adapters5. Select vmk26. Click on pencil icon to edit VMkernel port settings7. Check the box corresponding to "Virtual SAN traffic"8. Click "OK" to finish

Back To Challenge 2

HOL-1708-CHG-3


Virtual SAN Health UI

Click "Retest" to see if the previously seen errors are fixed.

Back To Challenge 2

HOL-1708-CHG-3


Virtual SAN Data Health

Though we have added host esx04a into the VSAN cluster, the VSAN data healtherrors are still prevailing.

Next step shows what it takes to fix it.

Back To Challenge 2

HOL-1708-CHG-3


Create DIsk Group In esx04a

Virtual SAN Cluster RegionA01-COMP01 is in "Manual Mode" Hence we need to create a disk group on host esx04a

1. Click on cluster RegionA01-COMP01 -> Manage tab2. Click on Settings3. Select Disk Management from left panel4. Select host esx04a & click on icon with green + ""create a new disk group"5. Choose cache tier disk (5 GB)6. Choose capacity tier disk (40 GB)7. Click OK to finish

Back To Challenge 2

HOL-1708-CHG-3


Retest Health UI

Navigate to Virtual SAN Health UI Click "Retest"

Back To Challenge 2

Check VM Compliance

Select VM linux-micro-01a Navigate to Manage tab Select Policies tab Click on the highlighted icon to check compliance of all VMs

Back To Challenge 2

HOL-1708-CHG-3


Power On Host esx01a

Click on the console on the left upper most corner in your lab console Power On host esx01a

Back To Challenge 2

HOL-1708-CHG-3


Refresh vSphere Web Client

Wait for host esx01a to boot and connect in vCenter Server Refresh until it shows connected

Back To Challenge 2

HOL-1708-CHG-3


Challenge 3 - Hints and SolutionsCheck VSAN Health Status

1. Click on cluster RegionA01-COMP012. Click on Monitor tab3. Choose Virtual SAN tab4. Health5. Network

Back To Challenge 3

HOL-1708-CHG-3


Check Network Health

1. All hosts do not have matching multicast settings.2. Host esx01a multicast IP address is different from the rest of the hosts in the

Virtual Cluster.

Back To Challenge 3

Fix The Problem

Open a putty session to esx01a.corp.local ( Use Putty application on desktop).

1. Run "esxcli vsan network list". This will list the multicast settings in the host.2. Run "esxcli vsan network remove -i vmk2"

HOL-1708-CHG-3


3. Change the master/agent multicast IP addresses by running "esxcli vsan networkipv4 add -i vmk2 -d 224.2.3.4 -u 224.1.2.3

Back To Challenge 3

HOL-1708-CHG-3


Verify VSAN Health

Retest Virtual SAN Health Expand Network health to verify

Back To Challenge 3

HOL-1708-CHG-3


Challenge 4 - Hints and SolutionConfigure Stretched Cluster

1. Select Manage tab under RegionA01-COMP01 cluster2. Click on Settings tab3. Choose Fault Domain & Stretched Cluster from Virtual SAN drop down4. Click on Configure

Back To Challenge 4

HOL-1708-CHG-3


Configure Fault Domain

1. Selct host esx-04a.2. Move host to Secondary fault domain.3. Select host esx-03a and move to Secondary fault domain as well.

Back to Challenge 4

HOL-1708-CHG-3


Preferred & Secondary Site

1. Ensure esx-01a, esx-02a are in preferred fault domain.2. esx-03a and esx-04a are in secondary fault domain.3. Click Next.

Back to Challenge 4

HOL-1708-CHG-3


Witness Node

1. Select host esx-07a as witness node2. Click Next.

Back to Challenge 4

HOL-1708-CHG-3


Create DIsk Group In Witness Node

1. Select cache tier flash disk.2. Select capacity ties magnetic disk.3. Click Next

Back to Challenge 4

HOL-1708-CHG-3


Create Stretched Cluster

Click Finish.

Back to Challenge 4

Noncompliant VMs

1. Select VM linux-micro-01a and navigate to Manage -> Policies.2. Check compliance of VM linux-micro-01a.

Back to Challenge 4

HOL-1708-CHG-3


Compliant

Back to Challenge 4

Virtual SAN Health UI

1. Retest Virtual SAN Health

Back to Challenge 4

HOL-1708-CHG-3


Deduplication

Take a note of the deduplication and Compression

Back to Challenge 4

HOL-1708-CHG-3


ConclusionThank you for participating in the VMware Hands-on Labs. Be sure to visithttp://hol.vmware.com/ to continue your lab experience online.

Lab SKU: HOL-1708-CHG-3

Version: 20161106-051226

HOL-1708-CHG-3


http://hol.vmware.com/

Table of ContentsLab Overview - HOL-1708-CHG-3 - Virtual SAN 6.2: Challenge LabLab GuidanceLocation of the Main ConsoleActivation Prompt or WatermarkAlternate Methods of Keyboard Data EntryClick and Drag Lab Manual Content Into Console Active WindowAccessing the Online International KeyboardClick once in active console windowClick on the @ keyLook at the lower right portion of the screen

Module SwitcherStart Module SwitcherWorking with Module Switcher

Challenge 1 - Set Up a Virtual SAN Cluster (15 Mins)IntroductionPrerequisites

Module SwitcherStart Module SwitcherWorking with Module Switcher

Create A Virtual SAN ClusterLog In To vSphere Web ClientYour Challenge: Create A Virtual SAN Cluster ChallengeYour Challenge: Enable Deduplication and CompressionYour Challenge: Migrate Virtual Machine With "HOL Default Storage Policy"

Challenge 2 - Recover Host Failure (15 Mins)IntroductionModule SwitcherWorking with Module Switcher

Key Concepts For This ChallengeChallenge 2: Recover From Host FailureRun Module 2 prep script in Module Switcher on Control Center DesktopLog Into vSphere Web ClientHost esx01a FailureVM ComplianceYour Challenge

Challenge 3 - Troubleshoot VSAN Multicast Layer 2 Issues (15 Mins)IntroductionKey Concepts

Module SwitcherWorking with Module Switcher

Challenge 3: Recover From Network PartitionRun Module 3 prep script in Module Switcher on Control Center DesktopLog Into vSphere Web ClientYour ChallengeKey Concepts Gained From Challenge 3

Challenge 4 - VSAN Stretched Cluster Creation & Optimization (15 Mins)IntroductionModule SwitcherWorking with Module Switcher

Create A Stretched ClusterKey ConceptsLogin To vSphere Web ClientYour ChallengeConclusion

Appendix - Hints and SolutionsChallenge 1 - Hints and SolutionsCreate A Virtual SAN ClusterEnable Virtual SANVerify Virtual SAN Network SettingsClaim Disks For Disk GroupsFault DomainsCreate Fault DomainsCreate Virtual SAN ClusterRefresh DisplayVirtual SAN - Disk ManagementFault DomainsvsanDatastore PropertiesEnable Deduplication & CompressionEnable DeduplicationMonitor ProgressDeduplication StatusMigrate Virtual Machine With VSAN Default Storage PolicyChoose Migration TypeChoose Destination HostChoose Destination DatastoreChoose VM NetworkVerify Virtual SAN Default Storage Policy

Challenge 2 - Hints and SolutionsAdd A New Host to cluster RegionA01-COMP01Cluster RegionA01-COMP01Move Host Into VSAN ClusterExit Maintenance ModeAdd Host to Fault DomainHealth UI To Detect FailuresTroubleshooting Network HealthRVC CommandFix VMkernel Port SettingsVirtual SAN Health UIVirtual SAN Data HealthCreate DIsk Group In esx04aRetest Health UICheck VM CompliancePower On Host esx01aRefresh vSphere Web Client

Challenge 3 - Hints and SolutionsCheck VSAN Health StatusCheck Network HealthFix The ProblemVerify VSAN Health

Challenge 4 - Hints and SolutionConfigure Stretched ClusterConfigure Fault DomainPreferred & Secondary SiteWitness NodeCreate DIsk Group In Witness NodeCreate Stretched ClusterNoncompliant VMsCompliantVirtual SAN Health UIDeduplication

Conclusion

table of contents - vmwaredocs.hol.vmware.com/hol-2017/hol-1708-chg-3_pdf_en.pdf · table of...

Documents