Edu en Vsanft7 Lab Se

azarpara.vahid@gmail.
com
VMware vSAN: Fast Track [V7]

Lab Manual
VMware vSAN™
VMware® Education Services

VMware, Inc.
www.vmware.com/education
mcse2012.blogfa.com
azarpara.vahid@gmail.com
VMware vSAN: Fast Track [V7]
Lab Manual
VMware vSAN™
Part Number EDU-EN-VSANFT7-LAB (06-AUG-2021)
Copyright © 2021 VMware, Inc. All rights reserved. This manual and its accompanying
materials are protected by U.S. and international copyright and intellectual property laws.
VMware products are covered by one or more patents listed at
http://www.vmware.com/go/patents. VMware is a registered trademark or trademark of
VMware, Inc. in the United States and/or other jurisdictions. All other marks and names
mentioned herein may be trademarks of their respective companies. VMware vSphere® High
Availability, VMware vSphere® ESXi™ Shell, VMware vSphere® Client™, VMware vSphere®
2015, VMware vSphere®, VMware vSAN™, VMware vCenter® Single Sign-On, VMware
vCenter® Server Appliance™, VMware vCenter Server®, VMware vSphere® vApp(s)™,
VMware View®, VMware Horizon® View™, VMware Verify™, VMware Skyline™ Health,
VMware vSphere® Distributed Switch™, VMware Go™, VMware ESXi™, VMware ESX®,
VMware vSphere® Distributed Resource Scheduler™, and VMware ACE™ are registered
trademarks or trademarks of VMware, Inc. in the United States and/or other jurisdictions.
The training material is provided “as is,” and all express or implied conditions, representations,
and warranties, including any implied warranty of merchantability, fitness for a particular
purpose or noninfringement, are disclaimed, even if VMware, Inc., has been advised of the
possibility of such claims. This material is designed to be used for reference purposes in
conjunction with a training course.
The training material is not a standalone training tool. Use of the training material for self-
study without class attendance is not recommended. These materials and the computer
programs to which it relates are the property of, and embody trade secrets and confidential
information proprietary to, VMware, Inc., and may not be reproduced, copied, disclosed,
transferred, adapted or modified without the express written approval of VMware, Inc.
mcse2012.blogfa.com
Typographical Conventions
The following typographical conventions are used in this course.
Conventions Usage and Examples
Monospace Identifies command names, command options, parameters, code

fragments, error messages, filenames, folder names, directory names,
and path names:
• Run the esxtop command.
• ... found in the /var/log/messages file.
Monospace Identifies user inputs:

Bold
• Enter ipconfig /release.
Boldface Identifies user interface controls:
• Click the Configuration tab.
Italic Identifies book titles:
• vSphere Virtual Machine Administration
<> Indicates placeholder variables:
• <ESXi_host_name>
• ... the Settings/<Your_Name>.txt file
Contents
Lab 1 Reviewing the Lab Environment..................................................................................... 1

Task 1: Access the Lab Environment ......................................................................................................................... 2
Task 2: Examine the Existing vSAN Cluster Details ............................................................................................. 2
Task 3: Examine the ESXi Host Configuration Details ......................................................................................... 3
Task 4: Verify the vSAN Cluster Licensing.............................................................................................................. 4
Lab 2 Configuring the Second vSAN Cluster ....................................................................... 5
Task 1: Create a Cluster .................................................................................................................................................. 6
Task 2: Configure the vSAN Cluster Using Quickstart ........................................................................................ 6
Task 3: Verify vSAN Cluster Details from the Command Line ........................................................................ 7
Lab 3 Working with vSAN Fault Domains............................................................................. 9
Task 1: Configure vSAN Fault Domains .................................................................................................................. 10
Task 2: Verify VM Compliance Status ...................................................................................................................... 11
Task 3: Prepare for the Next Lab .............................................................................................................................. 11
Lab 4 Analyzing the Impact of Storage Policy Changes ............................................... 13
Task 1: Determine the VM Storage Policy ............................................................................................................. 14
Task 2: Verify the Existing Storage Policy and Component Layout of a VM........................................... 14
Task 3: Change the VM Storage Policy and Monitor Component Layout Changes.............................. 15
Lab 5 Identifying Objects with Reduced Availability ........................................................17
Task 1: Create a Storage Policy That the Cluster Cannot Support .............................................................. 18
Task 2: Force-Provision a VM with an Invalid Storage Policy ........................................................................ 18
Task 3: Identify vSAN Objects with Reduced Availability ............................................................................... 19
Task 4: Change the VM Storage Policy ................................................................................................................. 20
Lab 6 Configuring vSAN Space Efficiency ...........................................................................21
iii
Task 1: Configure vSAN Cluster Space Efficiency .............................................................................................. 21
Task 2: Verify Space Efficiency Savings ................................................................................................................. 21
Lab 7 Managing vSAN Security Operations ...................................................................... 23
Task 1: Configure vSAN Data-at-Rest Encryption ............................................................................................. 23
Lab 8 Encryption Rekey Operations .....................................................................................25
Task 1: Generate New Encryption Keys ................................................................................................................ 26
Task 2: Verify Connectivity to the Second KMS ................................................................................................ 26
Task 3: Register the Second KMS with vCenter Server ..................................................................................27
Task 4: Change the KMS ............................................................................................................................................. 28
Lab 9 Configuring vSAN File Service ................................................................................... 29
Task 1: Configure vSAN File Service ....................................................................................................................... 30
Task 2: Create a File Share .......................................................................................................................................... 31
Task 3: Mount the NFS Share to the Student Desktop ................................................................................... 32
Task 4: View vSAN File Service Virtual Objects ................................................................................................ 35
Task 5: Verify vSAN File Service Skyline Health Details ................................................................................. 35
Task 6: Monitor vSAN File Share Performance Metrics .................................................................................. 35
Lab 10 Managing Remote vSAN Operations .....................................................................37
Task 1: Mount a Remote vSAN Datastore to a vSAN Cluster ...................................................................... 38
Task 2: Verify Connectivity to a Remote vSAN Datastore ........................................................................... 38
Task 3: Migrate VM Storage to the Remote vSAN Datastore ..................................................................... 39
Task 4: View VM Remote Objects........................................................................................................................... 39
Task 5: Prepare for the upcoming lab .................................................................................................................... 40
Task 6: Unmount a Remote vSAN Datastore ..................................................................................................... 40
Lab 11 Configuring a vSAN iSCSI Target .............................................................................. 41
Task 1: Enable the vSAN iSCSI Target Service ................................................................................................... 42
Task 2: Create an vSAN iSCSI Target and LUN ................................................................................................. 42
Task 3: Connect to the vSAN iSCSI LUN ............................................................................................................. 43
Lab 12 Verifying the vSAN Cluster Data Migration Precheck .................................... 45
Task 1: Examine the Data Migration Precheck Options.................................................................................... 45
Lab 13 Decommissioning the vSAN Cluster ....................................................................... 47
Task 1: Configure Retreat Mode for vCLS VMs .................................................................................................. 48
Task 2: Place vSAN Cluster Hosts in Maintenance Mode ............................................................................... 48
Task 3: Delete the vSAN Disk Groups ................................................................................................................... 49
iv
Task 4: Evacuate and Delete the vSAN Cluster ................................................................................................ 50
Lab 14 Scaling Out the vSAN Cluster .................................................................................... 51
Task 1: Add Hosts to the vSAN Cluster................................................................................................................. 52
Task 2: Claim Disks for a vSAN Disk Group ......................................................................................................... 52
Lab 15 Configuring the vSAN Stretched Cluster ............................................................. 53
Task 1: Configure the vSAN Stretched Cluster ................................................................................................... 54
Task 2: Verify the Health of the vSAN Stretched Cluster .............................................................................. 55
Task 3: Configure the Dual Site Mirroring VM Storage Policy ....................................................................... 55
Task 4: Examine the VM Components Placement ............................................................................................ 56
Lab 16 Monitoring vSAN Performance and Capacity .....................................................57
Task 1: View vSAN Cluster Performance Metrics .............................................................................................. 58
Task 2: View vSAN Disk Group Performance Metrics ..................................................................................... 58
Task 3: View the vSAN Storage Capacity Details ............................................................................................. 59
Lab 17 Reviewing the Troubleshooting Lab Environment ............................................. 61
Task 1: Access Your Lab Environment ................................................................................................................... 62
Task 2: Determine the Normal Cluster State ....................................................................................................... 63
Task 3: Use the vSphere Client to Examine the Lab Environment .............................................................. 64
Task 4: Use vSphere ESXi Shell to Construct ESXCLI Commands ............................................................ 65
Task 5: Use vSphere ESXi Shell to Examine the Lab Environment ............................................................. 66
Lab 18 Troubleshooting the Maintenance Mode Issue................................................... 67
Task 1: Troubleshoot the Problem ........................................................................................................................... 68
Task 2: Review Your Findings and Fix the Problem.......................................................................................... 69
Task 3: Clean Up for the Next Lab .......................................................................................................................... 69
Lab 19 Troubleshooting the vSAN Datastore Capacity Increasing Issue .................71
Task 1: Troubleshoot the Problem ............................................................................................................................72
Task 2: Review Your Findings and Fix the Problem...........................................................................................72
Lab 20 Troubleshooting the Two-Node vSAN Cluster Configuration Issue .........73
Task 1: Run the Break Script ....................................................................................................................................... 74
Task 2: Troubleshoot the Problem ...........................................................................................................................75
Lab 21 Troubleshooting the vSAN Cluster Issue............................................................... 77
v
Task 2: Troubleshoot the Problem .......................................................................................................................... 78
Lab 22 Troubleshooting the vSAN Node Configuration Issue .................................... 81
Lab 23 Troubleshooting the vSAN Cluster Configuration Issue (1) .......................... 85
Lab 24 Troubleshooting the vSAN Cluster Configuration Issue (2) ......................... 89
Task 3: Review Your Findings and Fix the Problem........................................................................................... 91
Task 4: Clean Up for the Next Lab ........................................................................................................................... 91
Lab 27 Troubleshooting the vSAN Cluster Datastore Capacity Reporting Issue
............................................................................................................................................................ 101
Task 1: Run the Break Script ..................................................................................................................................... 102
Task 2: Troubleshoot the Problem ........................................................................................................................ 102
Task 3: Review Your Findings and Fix the Problem........................................................................................ 103
vi
Task 4: Clean Up for the Next Lab ........................................................................................................................ 103
Answer Key .................................................................................................................................. 105
vii
viii
Lab 1 Reviewing the Lab Environment
Objective and Tasks

Review information to become familiar with the lab environment:
1. Access the Lab Environment
2. Examine the Existing vSAN Cluster Details
3. Examine the ESXi Host Configuration Details
4. Verify the vSAN Cluster Licensing
The diagram shows the lab environment topology.
1
Task 1: Access the Lab Environment
You access and manage the lab environment from the student desktop.
The system assigned to you serves as an end-user terminal.
1. Verify that you are logged in to the student desktop.
If you are not logged in, log in to your student desktop by entering
vclass\administrator as the username and VMware1! as the password.
2. Open Google Chrome to access the vSphere Client.
a. On the taskbar, click the Google Chrome shortcut.
b. From the Google Chrome bookmarks bar, select Site-A Systems > vSphere Client (SA-
VCSA-01).
3. Proceed through the alerts and log in to the vSphere Client.
a. Proceed through any security alerts by clicking Advanced and clicking Proceed to sa-
vcsa-01.vclass.local (unsafe).
b. Log in to the vSphere Client.
• User name: administrator@vsphere.local
• Password: VMware1!
Task 2: Examine the Existing vSAN Cluster Details

You use the vSphere Client to review the pre-configured vSAN cluster details and answer
questions about your lab environment.
1. Close the vCenter Server updates notification.
2. In the left pane, expand SA-Datacenter and click the SA-vSAN-01 cluster. In the right pane,
click the Datastores tab.
Q1. What is the storage capacity listed for SA-vsanDatastore-01?

A1. 200 GB.
3. In the left pane, expand SA-Datacenter and click the SA-vSAN-01 cluster. In the right pane,
click the Hosts tab.
Q2. How many hosts are listed under the cluster SA-vSAN-01?
A2. Four.
4. In the left pane, expand the SA-vSAN-01 cluster and select the sa-esxi-01.vclass.local Host.
5. Click on the Summary tab, expand the Hardware panel and view details.
Q3. What is the CPU capacity of a host?

A3. 4 CPUs x 2.8 Ghz.
Q4. What is the memory capacity of a host?

A4. 16 GB.
2
6. In the left pane, select the sa-vm-02.vclass.local VM.
7. On the Summary tab, expand the VM Storage Policies panel.
Q5. Which VM storage policy is set on the sa-vm-02.vclass.local VM?

A5. vSAN Default Storage Policy.
8. In the left pane, select the SA-vSAN-01 cluster.
9. In the right pane, click the Configure tab.
10. In the middle pane, click Disk Management under vSAN.
Q6. How many vSAN disk groups does each ESXi host have in the SA-vSAN-01
cluster?
A6. One.
11. In the Disk Management pane, select each disk group and review the disk group
configuration.
Q7. How many capacity disks are part of each vSAN disk group?
A7. One.
Q8. What is the storage capacity offered by each vSAN disk group?
A8. 50 GB.
Q9. What type of disk groups are created in the SA-vSAN-01 cluster?
A9. All flash.
Task 3: Examine the ESXi Host Configuration Details

You use MTPuTTY to connect to sa-esxi-01.vclass.local and you answer questions about your lab
environment.
1. On the taskbar, click the MTPuTTY shortcut.
2. In the MTPuTTY window, double-click the SA-ESXI-01 connection in the left pane to open
an SSH connection.
3. Run the esxcli vsan debug controller list command.
Q1. How many controllers are listed?

A1. Four.
Q2. How many controllers are used by vSAN?

You can use esxcli vsan debug controller list -v true to filter the
list for controllers used by vSAN.
A2. One.
Q3. What is the maximum supported queue depth listed for the controller that is
used by vSAN?
A3. 1024.
Q4. What is the driver name of the controller that is used by vSAN?
A4. pvscsi .
3
4. Run the esxcli network vswitch dvs vmware list command.
Q5. How many distributed virtual switches are listed?

A5. One.
Q6. What is the name of the distributed virtual switch that is listed?
A6. The VDS named SA-VDS.
Q7. How many uplinks are connected to each distributed virtual switch?
A7. Three: vmnic1, vmnic2 , and vmnic3.
Q8. How many configured ports are available?

A8. 512.
Q9. What is the MTU size that is configured?

A9. 1500.
5. Run the df -h command.
Q10. What is the name of the vSAN datastore?

A10. SA-vsanDatastore-01.
Q11. What is the size of the vSAN datastore?

A11. 200 GB.
6. Run the vdq -qH command.
Q12. How many devices are in use for vSAN, identified by the In-use for
vSAN state value?
A12. Two.
7. Close the MTPuTTY window.
Task 4: Verify the vSAN Cluster Licensing

You use the vSphere Client to verify the vSAN Cluster licensing.
1. In the left pane, expand SA-Datacenter and click the SA-vSAN-01 cluster.
2. View vSAN Cluster Licensing Information
a. Click the Configure tab and in the middle pane click Licensing > vSAN Cluster.
b. View vSAN Cluster Licensing details.
3. Minimize the vSphere Client window.
4
Lab 2 Configuring the Second vSAN
Cluster
Objective and Tasks

Manually configure the vSAN cluster and verify cluster information using the command line:
1. Create a Cluster
2. Configure the vSAN Cluster Using Quickstart
3. Verify vSAN Cluster Details from the Command Line
5
Task 1: Create a Cluster
You use the vSphere Client to create a cluster.
1. In the vSphere Client, click Hosts and Clusters in the left pane.
2. In the left pane, right-click SA-Datacenter and select New Cluster.
3. In the New Cluster window, name the cluster SB-vSAN-01.
4. In the New Cluster window, enable vSAN and click OK.
Task 2: Configure the vSAN Cluster Using Quickstart

You use the vSphere Client to configure the vSAN cluster using Quickstart.
1. In the left pane, select cluster SB-vSAN-01.
2. In the right pane, click the Configure tab and select Quickstart under Configuration on the
left side.
3. In the middle pane, click ADD to add new hosts to cluster.
4. Enter sb-esxi-01.vclass.local in the IP address or FQDN field.
5. Enter root as the username.
6. Enter VMware1! as the password.
7. Click ADD HOST.
8. Select the Use the same credentials for all hosts check box.
9. Enter sb-esxi-02.vclass.local in the IP address or FQDN field and click ADD

HOST.
10. Enter sb-esxi-03.vclass.local in the IP address or FQDN field and click ADD
HOST.
11. Enter sb-esxi-04.vclass.local in the IP address or FQDN field and click NEXT.
12. Review the host summary and click NEXT.
13. Click FINISH.
14. View the Recent Tasks pane for the vSAN cluster configuration status.
15. In the middle-right corner of the Cluster Quickstart pane, click CONFIGURE.
16. Enter SB-VDS as the distributed switch name.

17. Scroll down to map Adapter 3 (vmnic3) as the uplink for the SB-VDS distributed switch
from the drop-down menu.
18. Click NEXT.
6
19. In the Storage traffic pane, click NEXT.
20. In the Advanced options pane, click NEXT.
21. On the Claim disks page, verify that 50 GB disks are selected for Capacity tier and 5 GB
disks are selected for Cache tier for all hosts.
22. Click NEXT.
23. On the vSAN Support Insight page, click NEXT.
24. On the Proxy settings page, click NEXT.
25. Review your selections and click FINISH.
26. Monitor the vSAN cluster configuration progress from the Recent Tasks pane.
This operation might take approximately 20 minutes to complete.
You can ignore the errors and warnings displayed for the vSAN cluster SB-vSAN-01 in the
Cluster Quickstart wizard.
27. On completion, on the Summary tab of the SB-vSAN-01 cluster reset all triggered alarm
notifications to green.
Task 3: Verify vSAN Cluster Details from the Command Line

You use some ESXCLI commands to verify cluster information.
1. On the Windows taskbar, click the MTPuTTY icon.
2. In the left pane, double-click SB-ESXi-01.
3. In the right pane, enter esxcli vsan cluster get
Q1. What is the Sub-Cluster Member Count?

A1. 4.
4. In the right pane, enter df -h
Q2. What is the storage capacity displayed for the vSAN file system?
A2. 200 GB.
5. List all disks in the vSAN cluster by entering esxcli vsan health cluster list
Q3. Are all the health checks green?

A3. Yes.
6. In the right pane, enter esxcli vsan network list
Q4. Which VMkernel adapter is used for vSAN?

A4. vmk1.
7. Close the MTPuTTY window.
7
Lab 3 Working with vSAN Fault
Domains
Objective and Tasks

Create fault domains and examine their effect on VMs:
1. Configure vSAN Fault Domains
2. Verify VM Compliance Status
3. Prepare for the Next Lab
9
Task 1: Configure vSAN Fault Domains
You use the vSphere Client to create vSAN Fault Domains.
2. In the right pane, click Configure.

3. In the middle pane, click Fault Domains under vSAN.
4. In the right pane, click the large + button to create a fault domain.
5. Create the first fault domain with the sa-esxi-01.vclass.local and sa-esxi-03.vclass.local hosts.
a. For Fault domain name, enter FD-01.
b. Select the sa-exi-01.vclass.local and sa-esxi-03.vclass.local hosts.
c. Click Create.
6. Create a second fault domain with the sa-esxi-02.vclass.local and the sa-esxi-04.vclass.local
hosts.
a. In the center pane, click the + button to create another fault domain.
b. For Fault domain name, enter FD-02.
c. Select the sa-exi-02.vclass.local and sa-esxi-04.vclass.local hosts.
d. Click Create.
7. Verify that the two fault domains are created.
10
Task 2: Verify VM Compliance Status
You use the vSphere Client to investigate virtual machine (VM) storage policy compliance after
the vSAN Fault Domain configuration.
1. Verify the VM component state.
a. In the left pane, select the sa-vm-01.vclass.local VM.
b. In the center pane, select Monitor.
c. Select Physical disk placement under vSAN.
Q1. What is the state of the VM components?

A1. Active.
2. Verify the VM storage policy compliance.
a. In the right pane, click the Configure tab.
b. In the middle pane, click Policies under Settings.
c. In the right pane, click CHECK VM STORAGE POLICY COMPLIANCE.
Q2. Why are VMs Noncompliant with the assigned storage policy despite their
components being in the Active state?
A2. The hosts are in an Implicit Fault Domain and placing two ESXi hosts in each fault domain decreases the total number of fault domains to only two. The assigned VM Storage Policy requires at least four fault domains to have compliant VMs.
Task 3: Prepare for the Next Lab

You use the vSphere Client to remove all fault domains.
1. You remove all three fault domains to prepare the lab for upcoming activities.
a. In the left pane, select the SA-vSAN-01 cluster.
b. In the right pane, click the Configure tab.
c. In the middle pane, click Fault Domains under vSAN.
d. In the center pane, click the vertical ellipsis icon on the right side of the FD-01 fault
domain.
e. Click Delete and click Delete again to confirm.
f. Similarly, delete fault domain FD-02 also.
2. Verify that all fault domains are deleted.
3. Leave the vSphere Client open for the next lab.
11
Lab 4 Analyzing the Impact of
Storage Policy Changes
Objective and Tasks

Analyze the impact of storage policy changes on VMs:
1. Determine the VM Storage Policy
2. Verify the Existing Storage Policy and Component Layout of a VM
3. Change the VM Storage Policy and Monitor Component Layout Changes
13
Task 1: Determine the VM Storage Policy
You use the vSphere Client to determine the virtual machine (VM) storage policy details.
1. Open the vSphere Client window.
2. At the top of the vSphere Client window, select Menu > Policies and Profiles.
3. In the left pane, click VM Storage Policies.
4. Under VM Storage Policies, click SA-vSAN-01_VM_RAID5_Policy.
5. In the bottom panel, click the VM Compliance tab.
Q1. Which VMs are complaint with this VM Storage Policy?

A1. sa-vm-01.vclass.local.
Task 2: Verify the Existing Storage Policy and Component Layout of

a VM
You use the vSphere Client to verify the existing storage policy and component layout of a VM.
1. At the top of the vSphere Client, select Menu > VMs and Templates.
2. In the left pane, expand SA-Datacenter and click sa-vm-01.vclass.local.
3. In the right pane, click the Configure tab and click Policies on the left side.
Q1. Are the Virtual Machine Objects complaint with the assigned VM Storage
Policy?
A1. Yes.
4. Click the Monitor tab and click Physical disk placement on the left side under vSAN.
Q2. How many components exist for each object?

A2. Four.
14
Task 3: Change the VM Storage Policy and Monitor Component
Layout Changes
You use the vSphere Client to change the VM Storage Policy assigned to virtual machines.
1. In the left pane, right-click the sa-vm-01.vclass.local VM and select VM Policies > Edit VM
Storage Policies....
2. Select vSAN Default Storage Policy from the VM storage policy drop-down menu and click
OK.
3. In the left pane, keep the sa-vm-01.vclass.local VM selected.
4. In the center pane, click the Monitor tab.
5. Click Physical disk placement under vSAN.
Q1. Were any changes made to the vSAN components layout?

A1. RAID-1 component set made up of two data components and one witness component is now applied.
15
Lab 5 Identifying Objects with
Reduced Availability
Objective and Tasks

Identify objects with reduced availability caused by an invalid storage policy:
1. Create a Storage Policy That the Cluster Cannot Support
2. Force-Provision a VM with an Invalid Storage Policy
3. Identify vSAN Objects with Reduced Availability
4. Change the VM Storage Policy
17
Task 1: Create a Storage Policy That the Cluster Cannot Support
You use the vSphere Client to create a Storage Policy that the cluster cannot support.
1. At the top of the vSphere Client, select Menu > Policies and Profiles.
2. In the left pane, click VM Storage Policies.
3. In the right pane, click CREATE.
4. Enter SA-vSAN-01_VM_FTT2_RAID1_ForceProvision in the Name text box and

click NEXT.
5. Select the Enable rules for "vSAN" storage check box and click NEXT.
6. On the Availability tab, set Failures to tolerate to 2 failures - RAID-1 (Mirroring).
7. Click the Advanced Policy Rules tab.
8. Click the toggle button to enable Force provisioning and click NEXT.
9. Verify that SA-vsanDatastore-01 is displayed as compatible and click NEXT.
10. In the Review and finish pane, verify that Failures to tolerate is set to 2 failures-RAID-
1(Mirroring) and Force Provisioning is set to Yes, click FINISH.
Task 2: Force-Provision a VM with an Invalid Storage Policy

You configure the vSphere Client to force-provision a new VM with an invalid storage policy.
1. At the top of the vSphere Client, select Menu > Hosts & Clusters.
2. In the left pane, right-click the sa-vm-01.vclass.local VM and select Clone > Clone to virtual
machine.
3. Enter sa-vm-04.vclass.local for the Virtual machine name. Click NEXT.
4. Expand SA-Datacenter and select SA-vSAN-01 cluster as the folder location for the VM.
5. Click NEXT.
6. From the VM storage policy drop-down menu, select the SA-vSAN-

01_VM_FTT2_RAID1_ForceProvision policy.
7. Select SA-vsanDatastore-01 and click NEXT.
8. Select Power on virtual machine after creation and click NEXT.
9. Review settings and click FINISH.

10. In the Recent Tasks panel, monitor the VM creation and the power-on task progress.
18
Task 3: Identify vSAN Objects with Reduced Availability
You use the vSphere Client to identify objects with reduced availability.
2. In the right pane, click the Monitor tab.

3. Select Virtual Objects under vSAN and wait for the information to load.
4. In the right pane, scroll down and review the details for the sa-vm-04.vclass.local VM.
Q1. Why is the Placement and Availability status for the sa-vm-04.vclass.local VM
showing Reduced availability with no rebuild?
A1. The existing components set cannot meet the availability requirements defined in the VM storage policy.
5. In the left pane, select the sa-vm-04.vclass.local VM.
7. In the middle pane, click Policies under Settings.
Q2. What is the Compliance Status of the VM objects?

A2. Noncompliant.
8. Click the Monitor tab.
9. Select Physical disk placement under vSAN.
Q3. Can the VM objects tolerate a failure?

A3. No. Only one complete mirror of the data exists and no redundancy exists.
Q4. How many hosts would be required to satisfy the assigned VM storage policy
settings?
A4. Five hosts are required.
Q5. Why is the VM provisioned with few components?

A5. The storage policy allowed the creation of objects even if the defined failures to tolerate cannot be satisfied by using the Force provisioning option. The Force provisioning option enables objects to be created with a minimal component set until the VM Storage Policy can be fully applied.
Q6. How can the object become compliant in the absence of the required number
of hosts?
A6. Change the VM storage policy to a policy that the current cluster configuration can support.
19
Task 4: Change the VM Storage Policy
You use the vSphere Client to change the VM storage policy to one that the current cluster
configuration can support.
1. In the left pane, right-click the sa-vm-04.vclass.local VM.
2. Select VM Policies > Edit VM Storage Policies.
3. From the VM Storage Policy drop-down menu, select vSAN Default Storage Policy and
click OK.
4. In the right pane, click the Summary tab for the sa-vm-04.vclass.local VM.
5. Scroll down and review the VM Storage Policies pane to verify that the VM is compliant with
its storage policy.
7. Select Physical Disk placement under vSAN.
Q1. How many components are displayed for each of the VM objects?
A1. Three.
Q2. Can the VM objects tolerate a failure now?

A2. Yes.
20
Lab 6 Configuring vSAN Space
Efficiency
Objective and Tasks

Configure vSAN space efficiency features:
1. Configure vSAN Cluster Space Efficiency
2. Verify Space Efficiency Savings
Task 1: Configure vSAN Cluster Space Efficiency

You use the vSphere Client to configure the space efficiency on the vSAN cluster.
3. In the middle pane, click Services under vSAN.
4. In the right pane, click EDIT next to Space Efficiency.
5. Select Compression only from the Space efficiency drop-down menu.
6. Select check box to enable Allow reduced redundancy and Click APPLY.
7. Open the Recent Tasks panel to view the disk format conversion task progress.
This task can take up to 10 minutes to complete.
Task 2: Verify Space Efficiency Savings

You use the vSphere Client to verify compression-only mode space savings.
3. In the middle pane, click Capacity under vSAN to view Compression savings information.
21
22
Lab 7 Managing vSAN Security
Operations
Objective and Tasks

Configure vSAN cluster encryption:
1. Configure vSAN Data-at-Rest Encryption
Task 1: Configure vSAN Data-at-Rest Encryption

You use the vSAN data-at-rest encryption feature to encrypt the vSAN datastore.
1. Enable the vSAN data-at-rest encryption feature on the vSAN cluster.
b. In the right pane, click the Configure tab and, in the middle pane, click Services under
vSAN.
c. In the right pane, click EDIT next to Data-At-Rest-Encryption.
d. Click the toggle button to enable Data-At-Rest-Encryption.
e. Verify that the Wipe residual data check box remains unselected.
f. Verify that SA-KMS-01 is listed as the Key Provider.
g. Select the Allow reduced redundancy check box and click APPLY.
2. Open the Recent Tasks pane and view the vSAN cluster reconfiguration progress.
a. Ignore any alarms that might appear on the vSAN cluster until the cluster encryption
task completes.
23
24
Lab 8 Encryption Rekey Operations
Objective and Tasks

Rekey encryption and replace the key provider:
1. Generate New Encryption Keys
2. Verify Connectivity to the Second KMS
3. Register the Second KMS with vCenter Server
4. Change the KMS
25
Task 1: Generate New Encryption Keys
You use the vSphere Client to generate new encryption keys.
1. Generate new encryption keys.
vSAN.
c. In the right pane, click GENERATE NEW ENCRYPTION KEYS next to Data-At-Rest-
Encryption.
d. Verify that the Also re-encrypt all data on the storage using the new keys check box is
deselected.
e. Click GENERATE.
2. Open the Recent Tasks pane and watch the progress of generating new keys for the
encrypted vSAN cluster.
Task 2: Verify Connectivity to the Second KMS

You verify that you can access the second Key Management Server (KMS).
1. Use MTPuTTY to log in to vCenter Server Appliance.
a. On the student desktop taskbar, click the MTPuTTY icon.
b. In the left pane, double-click SA-VCSA-01.
You are logged in to vCenter Server Appliance as a root user.
2. Verify the connectivity to the KMS.
a. At the command prompt, run the shell command.
b. At the shell command prompt, ping the key management server and verify that the ping
is successful.
ping sa-kms-02.vclass.local
c. Press Ctrl+c to end the ping command and close the MTPuTTY window.
26
Task 3: Register the Second KMS with vCenter Server
You register the second KMS with vCenter Server.
1. Return to the vSphere Client window and, in the left pane, click sa-vcsa-01.vclass.local.
3. In the middle pane, click Key Providers under Security.
4. Add the second KMS to vCenter Server.
a. Click ADD STANDARD KEY PROVIDER.
b. In the dialog box, enter SA-KMS-02 in the Name text box.

c. Enter SA-KMS-02 in the KMS text box.
d. Enter sa-kms-02.vclass.local in the Address text box
e. Enter 5696 in the Port text box.
f. Click ADD KEY PROVIDER.
g. Click TRUST to accept the server certificate.
5. Make the KMS trust vCenter Server.
a. In the right pane, select the SA-KMS-02.
b. In the bottom panel, select the SA-KMS-02 and select Make KMS trust vCenter from
the ESTABLISH TRUST drop-down menu.
c. Select KMS certificate and private key and click NEXT.
d. Click UPLOAD A FILE for KMS Certificate.
e. Navigate to the C:\Materials\Downloads\SA-KMS-02 Client Certs\

folder, select the client_certificate_sa_vcsa_01.pem file, and click Open.
f. Click UPLOAD A FILE for KMS Private Key.
g. Navigate to the C:\Materials\Downloads\SA-KMS-02 Client Certs\

folder, select the client_key_sa_vcsa_01.pem file, and click Open.
h. Click ESTABLISH TRUST.
i. Refresh the vSphere Client and scroll to the right to verify that the KMS connection
status is Connected.
j. Verify that SA-KMS-02 has a green check mark status for vCenter Certificate and KMS
Certificate.
27
Task 4: Change the KMS
You use the vSphere Client to change the KMS that is used for encryption.
1. Change the KMS that is used for encryption.
vSAN.
c. In the right pane, click EDIT next to Data-At-Rest-Encryption.
d. Select SA-KMS-02 from the Key Provider drop-down menu.
e. Click APPLY.
2. Open the Recent Tasks panel to view the task progress.

28
Lab 9 Configuring vSAN File Service
Objective and Tasks

Configure vSAN File Service:
1. Configure vSAN File Service
2. Create a File Share
3. Mount the NFS Share to the Student Desktop
4. View vSAN File Service Virtual Objects
5. Verify vSAN File Service Skyline Health Details
6. Monitor vSAN File Share Performance Metrics
29
Task 1: Configure vSAN File Service
You use the vSphere Client to enable and configure vSAN File Service.
3. In the middle pane, click Services under vSAN.

4. In the right pane, under vSAN Services, click ENABLE next to File Service.
5. On the Configure File Service Introduction page, read the checklist and click NEXT.
6. Verify that Automatic approach is selected, select the Trust the certificate check box, and
click NEXT.
7. (Optional) If the automatic loading of the latest OVF package fails, load the OVF package
manually.
a. Select Manually load OVF and click BROWSE.
b. Navigate to the C:\Materials\Downloads\vSAN-FS-OVF\ folder.
c. Select all files and click Open.
d. Verify that six files are selected.
e. Click NEXT.
f. Wait for the OVF package import and validation to complete before continuing.
8. Enter the file service domain details.
• File service domain: vclass.local
• DNS servers: 172.20.10.10
• DNS suffix: vclass.local
a. Click NEXT.
9. From the Network drop-down menu, expand SA-vSAN-01 and select the VM Network port
group for the file service.
10. Configure the subnet mask and gateway details.
a. Enter the subnet mask and gateway details.
• Subnet mask: 255.255.255.0
• Gateway: 172.20.10.10
b. Click NEXT.
30
11. Create a pool of static IP addresses and DNS names for the file service VMs.
a. In the first empty IP address text box, enter 172.20.10.100.
b. Click AUTOFILL to populate the next three text boxes with IP addresses following in
sequence.
c. Click LOOKUP DNS to verify that each DNS entry resolves to an IP address.
d. Verify the IP address and DNS name details and click NEXT.
12. Review the details and click FINISH for the vSAN File Service Agent deployment to begin.
13. In the Recent Tasks panel, monitor the progress of enabling the vSAN file service.
14. After the vSAN file service is enabled, expand the caret to expand File Service to verify the
configuration details.
Task 2: Create a File Share

You use the vSphere Client to create a file share.
3. In the middle pane, click File Shares under vSAN.
4. In the right pane, click ADD to create a file share.
5. Enter prodfs for the file share name.
6. Define the storage space quotas.
a. Select the check box for Share warning threshold and enter 1 GB as the share warning
threshold value.
b. Select the check box for Share hard quota and enter 5 GB as the share hard quota
value.
7. Keep the default values for all other parameters and click NEXT.
8. Select Allow access from any IP and click NEXT.
9. Review the details and create the file share.
a. Review the details.
b. Click FINISH.
c. In the Recent Task pane, view the progress of the new file share creation.
31
10. Obtain the file share path details.
a. Select the prodfs file share check box and select NFS3 from the COPY PATH drop-
down menu.
The share path is copied to the clipboard.
b. Record the FSVM FQDN in the share path for use in the next task.
Task 3: Mount the NFS Share to the Student Desktop

You mount and configure the file share to the student desktop using NFS Client.
1. From the student desktop, launch a command prompt by clicking the Command Prompt icon
on the taskbar.
NOTE
The Windows NFS client is already enabled on the student desktop.
2. Mount the vSAN File Share to the Z: drive on the student desktop.
a. Enter the following command.
mount \\<fsvm FQDN>\prodfs Z:

For example, if the file share mount path uses fsvm-04.vclass.local, run the following
command.
mount \\fsvm-04.vclass.local\prodfs Z:
32
3. Click the Windows Explorer icon on the taskbar to view the NFS mount.
33
4. Verify that the NFS Mount is usable.
a. In the left pane, click prodfs (Z:).
b. In the right pane, right-click and select New > Text Document.
c. Press the Enter key to confirm the default file name.
d. Close the Windows Explorer window.
NOTE
Creating the folder confirms that NFS Mount is functioning correctly.
34
Task 4: View vSAN File Service Virtual Objects
You use the vSphere Client to view the vSAN File Service virtual objects.
1. Return to the vSphere Client and, in the left pane, select the SA-vSAN-01 cluster.
3. In the middle pane, click Virtual Objects under vSAN.
4. In the right pane, select vSAN File Shares under Affected inventory objects.
5. Select the prodfs file share check box and click VIEW PLACEMENT DETAILS.
6. View the file share component placement details and click CLOSE.
Task 5: Verify vSAN File Service Skyline Health Details

You use the vSphere Client to verify the vSAN File Service Skyline Health details.
2. In the right pane, select the Monitor tab.
3. In the middle pane, click Skyline Health under vSAN.
4. In Skyline Health section, scroll down and expand the File Service.
5. Click the Infrastructure Health, File Server Health, and Share Health tabs to view details.
Task 6: Monitor vSAN File Share Performance Metrics

You use the vSphere Client to monitor the file share performance metrics.
NOTE
Disclaimer: File Share performance graphs might not have any data to display because the file
share was recently created.
3. In the middle pane, click Performance under vSAN.
4. Click the FILE SHARE tab and click SHOW RESULTS to view file share throughput, IOPS,
and latency details.
35
36
Lab 10 Managing Remote vSAN
Operations
Objective and Tasks

Migrate and run VMs from remote vSAN datastores:
1. Mount a Remote vSAN Datastore to a vSAN Cluster
2. Verify Connectivity to a Remote vSAN Datastore
3. Migrate VM Data to the Remote vSAN Datastore
4. View VM Remote Objects
5. Prepare for the Next Lab
6. Unmount a Remote vSAN Datastore
37
Task 1: Mount a Remote vSAN Datastore to a vSAN Cluster
You use the vSphere Client to mount a remote vSAN datastore to a vSAN cluster.
1. Rename the SB-vSAN-01 cluster datastore.
a. In the left pane, select the SB-vSAN-01 cluster.

b. In the right pane, click the Datastores tab.
c. In the middle pane, right click on the vsanDatastore and select Rename.
d. Enter the new name as SB-vsanDatastore-01 and click OK.
2. Mount the SB-vsanDatastore-01 datastore to the SA-vSAN-01 cluster.
c. In the middle pane, click Datastore Sharing under vSAN.
d. In the right pane, click MOUNT REMOTE DATASTORE.
e. Select SB-vsanDatastore-01 and click NEXT.
f. Review the compatibility check list and click FINISH.
3. Open the Recent Tasks pane to monitor the progress of the vSAN cluster reconfiguration.
Task 2: Verify Connectivity to a Remote vSAN Datastore

You use the vSphere Client to verify connectivity to a remote vSAN datastore.
2. In the right pane, click the Datastores tab.
3. Verify that SB-vsanDatastore-01 is listed and that its status is Normal.
38
Task 3: Migrate VM Storage to the Remote vSAN Datastore
You use the vSphere Client to migrate virtual machine (VM) storage to the remote vSAN
datastore.
1. Migrate the VM storage to the SB-vsanDatastore-01 datastore.
a. In the left pane, right-click the VM sa-vm-01.vclass.local listed under the SA-vSAN-01
cluster.
b. Click Migrate.
c. Select Change storage only and click NEXT.
d. Select SB-vsanDatastore-01 and click NEXT.
e. Click FINISH.
2. Open the Recent Tasks pane to monitor the progress of the VM data migration.
Task 4: View VM Remote Objects

You use the vSphere Client to view VM remote objects.
1. View the physical placement details of the VM objects.
a. In the left pane, select the sa-vm-01.vclass.local VM.
b. In the right pane, click the Monitor tab.
c. In the middle pane, click Physical disk placement under vSAN.
d. Verify that all objects display Remote-accessible in the Accessibility column on

the Remote objects tab. Refresh the vSphere Client if necessary.
e. In the right pane, click the Remote objects details tab to view VM-related component
state and health details.
f. Verify that all components are stored on hosts from the SB-vSAN-01 cluster, as
indicated by the sb-esxi-XX.vclass.local naming schema.
39
Task 5: Prepare for the upcoming lab
You use the vSphere Client to migrate virtual machine (VM) storage to the remote vSAN
datastore.
1. Migrate the VM storage to the SA-vsanDatastore-01 datastore.
a. In the left pane, right-click the VM sa-vm-01.vclass.local listed under the SA-vSAN-01
cluster.
b. Click Migrate.
c. Select Change storage only and click NEXT.
d. Select SA-vsanDatastore-01 and click NEXT.
e. Click FINISH.
2. Open the Recent Tasks pane to monitor the progress of the VM data migration.
Task 6: Unmount a Remote vSAN Datastore

You use the vSphere Client to unmount a remote vSAN datastore.
1. Unmount the SB-vsanDatastore-01 from the SA-vSAN-01 cluster.
c. In the middle pane, click Datastore Sharing under vSAN.
d. In the right pane, select SB-vsanDatastore-01 and click UNMOUNT.
e. Click UNMOUNT.
2. Open the Recent Tasks pane to monitor the progress of the vSAN cluster reconfiguration.
40
Lab 11 Configuring a vSAN iSCSI
Target
Objective and Tasks

Configure an iSCSI LUN and connect to it from the student desktop:
1. Enable the vSAN iSCSI Target Service
2. Create an vSAN iSCSI Target and LUN
3. Connect to the vSAN iSCSI LUN
41
Task 1: Enable the vSAN iSCSI Target Service
You use the vSphere Client to enable the vSAN iSCSI target service.
1. In the left page, select SA-vSAN-01 cluster and click the Configure tab.
2. In the right pane, click Services under vSAN on the left side.
3. In the vSAN iSCSI Target Service row, click EDIT.
4. Click on the Enable vSAN iSCSI Target service toggle switch to enable the service.
5. From the Default iSCSI network drop-down menu, select vmk0.
6. Keep other settings to its default values and click APPLY.
7. Monitor the Recent Tasks pane until all tasks complete.
Task 2: Create an vSAN iSCSI Target and LUN

You use the vSphere Client to create an vSAN iSCSI LUN using the vSAN iSCSI Target service.
1. Click the iSCSI Target Service under vSAN.
2. In the iSCSI Target Service pane, click ADD.
3. In the New iSCSI Target window, enter SA-TARGET-01 in the Alias text box.
4. Verify that the network is set to vmk0 and click APPLY.
5. In the right pane, click ADD under vSAN iSCSI LUNs - SA-TARGET-01.
6. Configure the LUN.

ID 0
Alias SA-LUN-01
Storage Policy vSAN Default Storage Policy
Size 2 GB
a. Click ADD.
7. In the right pane, find and record the I/O Owner Host for the iSCSI target __________.
42
Task 3: Connect to the vSAN iSCSI LUN
You use the student desktop to connect to the vSAN iSCSI LUN.
1. On the student desktop taskbar, click the iSCSI Initiator icon.
2. In the Target text box, enter the FQDN of the I/O Owner Host.
3. Click the Quick Connect button.
4. In the Quick Connect window, click Done.
5. Close the iSCSI Initiator Properties window.
6. Format the disk.
a. On the Student Desktop Windows taskbar, click the Server Manager icon and wait for
the server manager to fully load.
b. In the left pane, click File and Storage Services and select Disks.
c. From the Disks list, select the 2 GB LUN with the Unknown partition.
d. Right-click the LUN, select Bring Online, and click Yes.
e. Right-click the LUN and select New Volume.
The New Volume Wizard opens.
f. On the Before You Begin page, click Next.
g. On the Server and Disk page, click Next and click OK.
h. On the Size page, accept the default values and click Next.
i. On the Drive Letter or Folder page, accept the default values and click Next.
j. On the Select file system settings page, accept the default values and click Next.
k. On the Confirm selections page, click Create.
l. On successful volume creation results page, click Close.
m. Close the Windows Server Manager window.
43
7. Verify that the new drive is usable.
a. On the Student Desktop Windows taskbar, right-click the Windows Explorer icon and
select File Explorer.
b. In the left pane, click New Volume (E:).
c. In the right pane, right-click and select New > Text Document.
d. Press the Enter key to confirm the default file name.
e. Close the Windows Explorer window.
NOTE
Creating the folder confirms that LUN is functioning correctly.
8. Close the File Explorer and leave the vSphere Client open for the next lab.
44
Lab 12 Verifying the vSAN Cluster
Data Migration Precheck
Objective and Tasks

Examine data migration options and their effect on components:
1. Examine the the Data Migration Precheck Options
Task 1: Examine the Data Migration Precheck Options

You place a host in maintenance mode and do not evacuate data.
1. In the left pane, right-click sa-esxi-02.vclass.local and select Maintenance Mode > Enter
Maintenance Mode.
2. In the Enter Maintenance Mode window, click GO TO PRE-CHECK.
3. In the right pane, select No data migration from the vSAN data migration drop-down menu.
4. Click the PRE-CHECK button, wait for test to complete.
Q1. What does the test result indicate?

A1. Some of the objects will become inaccessible and non-compliant.
5. (Optional) Examine Full data migration and Ensure accessibility pre-check test results to
assess the impact.
45
46
Lab 13 Decommissioning the vSAN
Cluster
Objective and Tasks

Evacuate and delete the vSAN cluster:
1. Configure Retreat Mode for vCLS VMs
2. Place vSAN Cluster Hosts in Maintenance Mode
3. Delete the vSAN Disk Groups
4. Evacuate and Delete the vSAN Cluster
47
Task 1: Configure Retreat Mode for vCLS VMs
You use the vSphere Client to configure retreat mode for vSphere Cluster Services (vCLS) VMs.
1. Disable vCLS feature on the SB-vSAN-01 cluster.

b. Copy the cluster domain ID from the URL of the browser.
The ID should be similar to domain-c<number>, eg. domain-c1028.
c. In the left pane, select sa-vcsa-01.vclass.local.
d. In the center pane, select Configure.
e. Click Advanced Settings and click EDIT SETTINGS.
f. Add a new entry with the name = config.vcls.clusters.domain-c<number>.enabled and

yhrvalue = False.
g. Click ADD and click SAVE.
2. Clean up the vCLS VMs.

The vCLS monitoring service initiates the cleanup of the vCLS VMs. You will start noticing
the tasks with the VM deletion.
a. Wait for all the Delete virtual machine operations to complete.
Task 2: Place vSAN Cluster Hosts in Maintenance Mode

You use the vSphere Client to decommission the SB-vSAN-01 cluster.
1. Place the SB-vSAN-01 cluster hosts in maintenance mode.

b. In the right pane, click Hosts.
c. In the center pane, select all four hosts by right-clicking them and select Maintenance
Mode > Enter Maintenance Mode.
d. Click YES.
e. For the vSAN data migration option, select No data migration.
f. Click OK.
2. Open the Recent Tasks pane to view the progress of the hosts entering maintenance mode.
a. Wait for all hosts to enter maintenance mode.
b. If any host fails to enter maintenance mode, retry the individual host with the No data
migration option selected.
c. Verify that all hosts are in maintenance mode before continuing.
48
Task 3: Delete the vSAN Disk Groups
You use the vSphere Client to delete the vSAN disk groups.
1. Delete the vSAN disk Groups from all hosts in the SB-vSAN-01 cluster.
c. In the middle pane, click Disk Management under vSAN.

d. Select the disk group under sb-esxi-01.vclass.local host, click the ellipsis, and click
Remove.
e. Click REMOVE to confirm and wait for the task to complete.
f. Remove disk groups from the sb-esxi-02.vclass.local, sb-esxi-03.vclass.local, and sb-

esxi-04.vclass.local hosts.
2. Verify that no disk groups exist before continuing.
49
Task 4: Evacuate and Delete the vSAN Cluster
You use the vSphere Client to evacuate and delete the vSAN cluster.
1. Move all hosts from the SB-vSAN-01 cluster to the SA-Datacenter data center.
b. In the right pane, click Hosts.
c. In the center pane, select all hosts, right-click them, and select Move To.
d. Click YES.
e. Select SA-Datacenter and click OK.
2. Open the Recent Tasks pane to view the progress of the vSAN cluster update.
3. Verify that SB-vSAN-01 is now empty, right-click SB-vSAN-01, and select Delete.
4. Click YES to confirm.
50
Lab 14 Scaling Out the vSAN Cluster
Objective and Tasks

Scale out a vSAN stretched cluster by adding hosts to the cluster:
1. Add Hosts to the vSAN Cluster
2. Claim Disks for a vSAN Disk Group
51
Task 1: Add Hosts to the vSAN Cluster
You use the vSphere Client to add hosts to the vSAN cluster.
1. Scale out the vSAN cluster by adding the sb-esxi-01.vclass.local, sb-esxi-02.vclass.local, sb-
esxi-03.vclass.local, and sb-esxi-04.vclass.local hosts to the SA-vSAN-01 cluster.
a. In the left pane, select SA-Datacenter.
b. In the right pane, click the Hosts & Clusters tab.
c. Select the sb-esxi-01.vclass.local, sb-esxi-02.vclass.local, sb-esxi-03.vclass.local, and

sb-esxi-04.vclass.local hosts, right-click them, and select Move To.
d. Click YES.
e. Expand SA-Datacenter and select the SA-vSAN-01 cluster.
f. Click OK.
g. Click OK for each of the hosts.
2. Open the Recent Tasks pane to view the task progress.
Task 2: Claim Disks for a vSAN Disk Group

You use the vSphere Client to claim disks and form a vSAN disk group.
3. Claim the disks on the new hosts for vSAN.

a. In the middle pane, click Disk Management under vSAN.
b. In the Disk Management pane, click CLAIM UNUSED DISKS.
c. Verify that the 5.00 GB disks are assigned to the Cache tier and that the 50.00 GB disks
are assigned to the Capacity tier.
d. Click CREATE and view the Recent Tasks pane for task progress.
4. Take the hosts out of maintenance mode.

a. In the right pane, click the Hosts tab.
b. Select all hosts with the sb-esxi prefix by pressing either Ctrl+click or Shift+click.
c. Right-click the selected hosts and select Maintenance Mode > Exit Maintenance Mode.
d. Click YES to confirm and view the Recent Tasks pane for task progress.
5. On the Summary tab of the SA-vSAN-01 cluster, reset triggered alarm notifications to
green.
52
Lab 15 Configuring the vSAN
Stretched Cluster
Objective and Tasks

Configure the vSAN stretched cluster:
1. Configure the vSAN Stretched Cluster
2. Verify the Health of the vSAN Stretched Cluster
3. Configure the Dual Site Mirroring VM Storage Policy
4. Examine the VM Components Placement
53
Task 1: Configure the vSAN Stretched Cluster
You use the vSphere Client to configure a vSAN stretched cluster.
3. In the middle pane, click Fault Domains under vSAN.
4. In the right pane, select CONFIGURE STRETCHED CLUSTER.
5. Configure the fault domains for the stretched cluster.
a. Select sb-esxi-01.vclass.local and click the >> button to move it to the secondary
domain.
b. Select sb-esxi-02.vclass.local and click the >> button to move it to the secondary
domain.
c. Select sb-esxi-03.vclass.local and click the >> button to move it to the secondary
domain.
d. Select sb-esxi-04.vclass.local and click the >> button to move it to the secondary
domain.
e. Click NEXT.
6. On the select Witness host page, expand and select sa-vcsa-01.vclass.local > SA-
Datacenter > Witness-Nodes > sc-witness-01.vclass.local.
7. Wait for the compatibility check to complete before continuing and click NEXT.
8. In the Select a single disk for the cache tier panel, select the 10.00 GB flash disk.
9. In the Select one or more disks for the capacity tier panel, select the check box for the
35.00 GB flash disk.
10. Click NEXT.
11. On the Ready to complete page, review the settings and click FINISH.
12. In the Recent Tasks pane, monitor the vSAN cluster reconfiguration.
When the tasks are complete, you can view the stretched cluster configuration in the right
pane.
54
Task 2: Verify the Health of the vSAN Stretched Cluster
You use the vSphere Client to verify the health of the vSAN stretched cluster.
1. Verify the stretched cluster health tests.
b. In the right pane, click Monitor.

c. In the middle pane, click Skyline Health under vSAN.
d. In the right pane, scroll down and expand the Stretched cluster category.
e. Verify that no stretched cluster tests failed.
Task 3: Configure the Dual Site Mirroring VM Storage Policy

You use the vSphere Client to create a custom storage policy that uses both local failure
protection and site disaster tolerance.
1. Create the vSAN_DualSiteMirroring storage policy to tolerate failures both within a site and
across sites.
a. At the top in the vSphere Client, select Menu > Policies and Profiles.
b. In the left pane, select VM Storage Policies.
c. In the right pane, click CREATE.
d. On the Name and description page, enter vSAN_DualSiteMirroring in the Name

text box and click NEXT.
e. On the Policy structure page, select the Enable rules for “vSAN” storage check box
and click NEXT.
f. Select Dual site mirroring (stretched cluster) from the Site disaster tolerance drop-
down menu.
g. Select 1 failure - RAID-5 (Erasure Coding) from the Failures to tolerate drop-down
menu and click NEXT.
h. Verify that SA-vsanDatastore-01 is listed under compatible storage and click NEXT.
i. Review the storage policy configuration and click FINISH.
55
2. Apply the vSAN_DualSiteMirroring storage policy to the virtual machines.
a. At the top in the vSphere Client, select Menu > Hosts and Clusters.
b. In the left pane, select the SA-vSAN-01 cluster.
c. In the right pane, click the VMs tab.
d. Select all VMs with the sa-vm prefix, right-click the selected VMs, and select VM Policies
> Edit VM Storage Policies.
e. Click YES.
f. Select the vSAN_DualSiteMirroring storage policy and click OK.
g. Open the Recent Tasks pane to view the VM reconfiguration.
Task 4: Examine the VM Components Placement

You use the vSphere Client to examine the VM components placement.
1. Examine the VM storage policy compliance status.
a. In the left pane, select the sa-vm-01.vclass.local VM under the SA-vSAN-01 cluster.
b. In the right pane, click the Summary tab and scroll down to the VM Storage Policies
pane.
c. Click the Check VM Storage Policy Compliance link and verify that the storage policy is
compliant. Refresh the vSphere Client if necessary.
d. In the center pane, click the Monitor tab and select Physical disk placement under
vSAN.
e. Verify the Component State, Host, and Fault Domain details for the VM objects.
56
Lab 16 Monitoring vSAN Performance
and Capacity
Objective and Tasks

Monitor the vSAN cluster performance and capacity details:
1. View vSAN Cluster Performance Metrics
2. View vSAN Disk Group Performance Metrics
3. View the vSAN Storage Capacity Details
57
Task 1: View vSAN Cluster Performance Metrics
You use the vSphere Client to view the vSAN cluster performance metrics.
1. In the left pane, click SA-vSAN-01 Cluster.
4. In the right pane, click SHOW RESULTS to view the metrics about the vSAN cluster, from
the virtual machine (VM) storage activities perspective.
5. Record the VM throughput value.
6. In the Performance pane, click BACKEND and click SHOW RESULTS to view the SAN back-
end performance metrics.
7. Verifying the vSAN back-end throughput value.
Q1. Why is the vSAN back-end throughput much higher than the VM throughput?
A1. vSAN back-end throughput is higher than the VM throughput because of the additional I/O that is generated for writing data to mirror copies and objects repair/rebuild traffic.
Task 2: View vSAN Disk Group Performance Metrics

You use the vSphere Client to view the vSAN node performance metrics.
1. In the left pane, select the sa-esxi-02.vclass.local host.
4. In the right pane, select DISKS and click SHOW RESULTS.
5. Scroll through and view the detailed performance metrics related to the vSAN disk group.
58
Task 3: View the vSAN Storage Capacity Details
You use the vSphere Client to view the vSAN storage capacity utilization details.
3. In the middle pane, click Capacity under vSAN.
4. In the right pane, select CAPACITY USAGE to review the storage details for the following
items.
• Capacity overview
• Usable capacity analysis
• Usage breakdown
5. Close the vSphere Client and disconnect from the student desktop's remote session.
59
Lab 17 Reviewing the Troubleshooting
Lab Environment
Objective and Tasks

Review information to become familiar with the troubleshooting lab environment:
1. Access Your Lab Environment
2. Determine the Normal Cluster State
3. Use the vSphere Client to Examine the Lab Environment
4. Use vSphere ESXi Shell to Construct ESXCLI Commands
5. Use vSphere ESXi Shell to Examine the Lab Environment
The diagram shows the lab environment.
61
Task 1: Access Your Lab Environment
You access and manage the lab environment from the student desktop.
The system assigned to you serves as an end-user terminal.
1. Verify that you are logged in to the student desktop.
If you are not logged in, log in to your student desktop by entering
vclass\administrator as the username and VMware1! as the password.
2. Log in to vCenter Server.
a. On the student desktop taskbar, click the Google Chrome web browser icon.
b. Select Site-A vSphere Client (SA-VCSA-01) from the bookmarks.
3. On the VMware vCenter Single Sign-On page, log in.
User name: administrator@vsphere.local

Password: VMware1!
4. Close the notification, "New vCenter server updates are available" at top.
62
Task 2: Determine the Normal Cluster State
You use the vSphere Client to determine the normal state of the lab cluster.
1. Clear any alerts.
a. Select SA-DC-01 > Monitor tab > Issues and Alarms and select All Issues.
b. If any alerts are listed, select them and click Reset To Green.
c. In the Reset To Green dialog box, click Yes.

2. In the left pane, expand SA-DC-01 and select the SA-vSAN-01 cluster.
3. In the center pane, click the Monitor tab and select Skyline Health under vSAN.
The hardware compatibility category shows a warning because the SCSI controller is not
certified by VMware for vSAN and the environment is nested.
The online health category shows a warning stating that vSAN support insight is
not configured.
The vSAN build recommendation also shows a warning.
4. Navigate through all the metrics that are listed under Skyline Health and verify that each is in
a healthy state.
63
Task 3: Use the vSphere Client to Examine the Lab Environment
You use the vSphere Client to review the vSAN cluster and answer questions about your lab
environment.
1. Review the vSAN clusters SA-vSAN-01 details.
Q1. Is the SA-vSAN-01 cluster enabled for vSAN only?

A1. The cluster is also enabled for DRS and vSphere HA.
Q2. Which VM storage policy is set on the sa-vm-01 VM?

A2. Custom-vSAN-Storage-Policy
Q3. How many vSAN components are created for the sa-vm-02 VM home object?
A3. Four
Q4. Can any VMs in the SA-vSAN-01 cluster tolerate two host failures?
A4. No
Q5. How many vSAN disk groups does each ESXi host have in the SA-vSAN-01
cluster?
A5. One
A6. Two
Q7. What is the storage capacity that is offered by individual vSAN disk groups?
A7. 40 GB
64
Task 4: Use vSphere ESXi Shell to Construct ESXCLI Commands
You use vSphere ESXCLI Shell to attempt to build the requested ESXCLI commands.
1. Connect MTPuTTY to sa-esxi-01.vclass.local.
a. From the student desktop taskbar, click the MTPuTTY icon.

b. In the left pane, expand Site-A Systems and double-click SA-ESXi-01.
You are now logged in to sa-esxi-01.vclass.local as root.
2. Construct an ESXCLI command that lists all the core storage devices.
a. Run the esxcli command.
b. Examine the list of additional command parameters.
c. Continue building the command.
The command uses a total of four command operators after the initial esxcli
command.
Q1. Which command parameter should come after esxcli to properly build the
entire command?
A1. Storage
Q2. What command did you construct?

A2. esxcli storage core device list
3. Construct an ESXCLI command that lists debug information for any controller used by
vSAN.
a. Run the esxcli command.
b. Examine the list of additional command parameters.
c. Continue building the command.
The command uses a total of four command operators after the initial esxcli
command:
esxcli Option1 Option2 Option3 Option4

Q3. Which command parameter should come after esxcli to properly build the entire
command?
A3. vsan

A4. esxcli vsan debug controller list
65
Task 5: Use vSphere ESXi Shell to Examine the Lab Environment
You use MTPuTTY to connect to sa-esxi-01.vclass.local and you answer questions about your lab
environment.
1. Run the first command that you constructed in the previous task.
esxcli storage core device list

Q1. What is the Device Max Queue Depth listed for the storage devices?
A1. 1024
2. Run the second command that you constructed in the previous task.
esxcli vsan debug controller list

A2. Three

A3. One
Q4. What Maximum Supported Queue Depth is listed for the controller used by
vSAN?
A4. 1024
Q5. What is the driver name of the controller used by vSAN?

A5. pvscsi
3. Run the esxcli network vswitch dvs vmware list command.

A6. One
Q7. What is the name of the distributed virtual switch listed?

A7. SA-VDS
Q8. How many uplinks are connected to the distributed virtual switch?
A8. Three
Q9. Are jumbo frames enabled?

A9. No
Q10. How many configured ports are there on the distributed virtual switch?
A10. 512
4. Run the df -h command.

A11. SA-vsanDatastore

A12. Approximately 160 GB
5. Run the vdq -q command.
Q13. How many devices are in use for vSAN?

A13. Three
6. Close the ESXi Shell session.
66
Lab 18 Troubleshooting the
Maintenance Mode Issue
Objective and Tasks

Diagnose and fix the vSAN cluster problem:
1. Troubleshoot the Problem
2. Review Your Findings and Fix the Problem
3. Clean Up for the Next Lab
67
Task 1: Troubleshoot the Problem
You troubleshoot the problem that is described in the lab scenario.
1. Read the lab scenario.
At your customer's company, a server hardware vendor requests a maintenance window to

replace a hardware component for the SA-ESXi-04 host in the SA-vSAN-01 cluster. Your
customer places the SA-ESXi-04 host in maintenance mode with the full data migration
option, but the operation fails. The customer wants you to troubleshoot this problem.
2. Access information about the problem by using the available tools.
• VMware Skyline Health for vSAN
• ESXi host and vCenter Server log files
• VMware knowledge base articles
3. View alarm notifications for the SA-vSAN-01 cluster.
a. Return to the vSphere Client and select SA-vSAN-01 in the left pane.
b. Select the Summary tab to view any triggered alarm notifications.
4. Review the cluster configuration details.
Q1. Do any alarm notifications appear on the SA-vSAN-01 cluster?

A1. No
Q2. Are any alarm notifications triggered for the customer-reported host sa-esxi-
04.vclass.local?
A2. No
5. Simulate the customer-reported problem to investigate further.
a. In the left pane, expand the SA-vSAN-01 cluster and select the sa-esxi-04.vclass.local
host.
b. Right-click the selected host and select Maintenance Mode > Enter Maintenance Mode.
c. Select Full data migration from the drop-down menu for the vSAN data migration type.
d. Click the GO TO PRE-CHECK button.
e. Ensure that Full data migration is selected for the vSAN data migration type.
f. Click the PRE-CHECK button and wait for the test to complete.
Q3. What does the PRE-CHECK conclude?

A3. The host cannot enter maintenance mode.
68
Task 2: Review Your Findings and Fix the Problem
You review your findings and identify a solution to fix the problem in the vSAN cluster.
1. Review your findings and outline a solution that fixes the problem.
2. Implement your solution.
Task 3: Clean Up for the Next Lab

You clean up the lab environment in preparation for the next lab.
1. Take the host out of maintenance mode.
a. In the left pane, expand the SA-vSAN-01 cluster and select the sa-esxi-04.vclass.local
host.
b. Right-click the selected host and select Maintenance Mode > Exit Maintenance Mode.
2. Verify that alerts are cleared.
a. Navigate to the SA-vSAN-01 cluster, click the Monitor tab, and expand Issues and
Alarms.
b. Select All Issues.
c. If any alerts are listed, select them and click Reset To Green.
d. Minimize the vSphere Client window.
69
Lab 19 Troubleshooting the vSAN
Datastore Capacity Increasing Issue
Objective and Tasks

71
1. Read the lab scenario.
Your customer increases the storage capacity for the two-node SB-vSAN-01 cluster. The
customer installs 20 GB capacity disks on the sb-esxi-01 and sb-esxi02 hosts.
After the disks are installed, the customer tries to claim disks to increase the storage
capacity of the SB-vsanDatastore datastore but is unsuccessful. The customer wants you to
troubleshoot this problem.
3. Examine the host for an extra disk.
a. Return to the vSphere Client.
b. In the left pane, expand SB-vSAN-01 and select sb-esxi-01.vclass.local.
c. In the center pane, click the Configure tab and select Storage Devices.
Q1. What status is shown in the datastore column for the 20 GB disk detected
under path mpx.vmhba0:C0:T4:L0?
A1. Not Consumed
4. In the left pane, select the SB-vSAN-01 cluster.

5. In the center pane, click the Configure tab and select Disk Management under vSAN.
6. In the center pane, select the Disk Group under the sb-esxi-01.vclass.local host.
7. Click ADD DISKS.
Q2. Is the new 20 GB disk listed in the Add Capacity Disks window?
A2. No
8. Click Cancel.
9. Repeat these steps to verify the availability of the disk on the sb-esxi02.vclass.local host.

Review your findings and identify a solution to fix the problem in the vSAN cluster.
72
Lab 20 Troubleshooting the Two-
Node vSAN Cluster Configuration
Issue
Objective and Tasks

1. Run the Break Script
Lab Scenario
The customer reports that the VMs in the Two-Node vSAN Cluster SB-vSAN-01 are no longer
compliant with the assigned VM storage policy. The VMs are non-compliant for an extended
period that is beyond normal expectations. The customer is concerned and wants you to fix the
problem.
73
Task 1: Run the Break Script
You set up the lab environment by running the break script.
1. Double-click the vSAN7_TSW.bat file on the student desktop.
The vSAN7_TSW.bat file is used to configure the vSAN troubleshooting labs.
2. On the vSAN7_TSW dashboard, click Start under Break/Fix 1.
3. Press Enter.
4. When the script completes, close the script execution window.
74
NOTE
For all break-fix labs, take notes as you identify alarm notifications to help you isolate and
diagnose the reported problems.
1. Review the scenario description of the problem.
The customer reports that the VMs in the two-node cluster SB-vSAN-01 are no longer
compliant with the assigned VM storage policy. The VMs are noncompliant for an extended
period that is beyond normal expectations.
3. View and assess triggered alarm notifications related to the problem that the customer
reports.
a. Return to the vSphere Client and select the SB-vSAN-01 cluster in the left pane.
b. On the right, click the Summary tab to view any triggered alarm notifications.
c. Assess the cluster situation using the triggered alarm notifications, refresh vSphere
Client.
Q1. Which VM storage policy is applied for the VM sb-vm-01?

A1. vSAN Default Storage Policy
Q2. What is the VM storage policy compliance status for sb-vm-01?

A2. Noncompliant
4. Use VMware Skyline Health for vSAN to investigate the problem.
a. In the left pane, select SB-vSAN-01.
b. On the right, click the Monitor tab and select vSAN > Skyline Health.
c. Click RETEST and wait for the process to complete.
d. Expand each metric and assess the available information.
75
You review your findings and identify a solution for the problem in the vSAN cluster.

1. Clear alarm notifications.
a. In the left pane of the vSphere Client, select SB-vSAN-01.
b. Click the Monitor tab and select Issues and Alarms > All Issues.
c. If any alarms are listed, select them and click Reset To Green.
2. Verify the health status of the vSAN cluster.
a. Select SB-vSAN-01 in the left pane.
b. Click the Monitor tab and select vSAN > Skyline Health.
d. Verify that the cluster has a health status of normal.
4. On the vSAN7_TSW dashboard, click Stop under Break/Fix 1.
5. Press Enter.
6. Wait for the cleanup to complete and then close the script execution window.
76
Cluster Issue
Objective and Tasks

Lab Scenario
The customer reports a significant decrease in the total storage space that is available on the SA-
vSAN-01 cluster. In addition, VMs are not compliant with their assigned VM storage policy. The
customer wants you to troubleshoot and resolve this problem.
77
1. Open the vSAN7_TSW dashboard and click Start under Break/Fix 2.
2. Press Enter.
3. When the script completes, close the window.

The customer reports a significant decrease in the total storage space that is available on the
SA-vSAN-01 cluster.
In addition, VMs are not compliant with their assigned VM storage policy.
reports.
c. Assess the cluster situation using the triggered alarm notifications.
4. On the Summary tab, review the cluster configuration details.
Q1. Does the number of ESXi hosts in the cluster match your previous observation?
A1. Yes
Q2. Are any alarm notifications triggered for the hosts in the cluster?
A2. Yes
Q3. Has the SA-vsanDatastore storage capacity decreased?

A3. Yes
a. In the left pane, select SA-vSAN-01.
78

a. In the vSphere Client, select SA-vSAN-01 in the left pane.
a. Select SA-vSAN-01 in the left pane.
d. Verify that the cluster is in a normal state.
5. Press Enter.
79
Node Configuration Issue
Objective and Tasks

Lab Scenario
Your customer decides to clone additional VMs from the existing ones. Whenever the host SA-
ESXi-02 is selected as the target, the clone operation fails. The customer asks you to
troubleshoot this problem.
81
1. Run break script 5 from the vSAN7_TSW dashboard.
a. Open the vSAN7_TSW dashboard and click Start under Break/Fix 3.
b. Press Enter.
c. When the script completes, close the window.

Your customer decides to clone additional VMs from the existing ones. Whenever the host
SA-ESXi-02 is selected as the target, the clone operation fails.
reports.
b. Click the Summary tab to view any triggered alarm notifications.
Q1. Are any alarm notifications triggered for the SA-ESXi-02 host?
A1. No
82
5. Recreate the customer problem to investigate it further.
a. In the left pane, right-click sa-vm-01 and select Clone > Clone to Virtual Machine.
b. Enter the name of the VM as sa-vm-05 and click Next.
c. On the Select a Compute Resource page, select SA-DC-01 > SA-vSAN-01 > sa-esxi-
02.vclass.local and click Next.
d. Select SA-vsanDatastore and click Next.
e. On the Select Clone Options page, select Power on virtual machine after creation and
click Next.
f. Click Finish.
Q2. Did you successfully clone the VM?

A2. No

83
5. Press Enter.
84
Cluster Configuration Issue (1)
Objective and Tasks

Lab Scenario
The customer reports that vSAN configuration-related notifications are triggered for the SA-
vSAN-01 cluster in VMware Skyline Health for vSAN. The customer wants you to address and
resolve the notifications immediately to avoid any future downtime.
85
b. Press Enter.

The customer reports that vSAN configuration-related notifications are triggered for the SA-
vSAN-01 cluster in VMware Skyline Health for vSAN. You must address and resolve the
notifications to avoid any future downtime.
3. View and assess the triggered alarm notifications for the cluster.
b. On the right, click the Summary tab to view the triggered alarm notifications.
86

5. Press Enter.
87
Objective and Tasks

Lab Scenario
Your customer reports a decrease in the total storage capacity of SA-vsanDatastore and that
VMs are not compliant with the assigned VM storage policy. How do you troubleshoot this
problem?
89
b. Press Enter.

Your customer reports that the total storage capacity of SA-vsanDatastore decreased and
that VMs are not compliant with the assigned VM storage policy.
reports.
Q1. Has the storage capacity of the SA-vsanDatastore decreased?

A1. Yes.
Q2. Are any hosts experiencing problems in the cluster?

A2. Yes.
Q3. Do any errors or warnings appear on the ESXi host?

A3. Yes.
90

a. In the left pane of the vSphere Client, select SA-vSAN-01.
5. Press Enter.
91
92
Objective and Tasks

Lab Scenario
The customer has noticed the vSAN cluster configuration issue on Skyline Health and wants you
to troubleshoot this problem to avoid any future downtime.
93
b. Press Enter.

The customer has noticed the vSAN cluster configuration issue on Skyline Health and wants
you to troubleshoot this problem to avoid any future downtime.
reports.
94

5. Press Enter.
95
Objective and Tasks

Lab Scenario
The customer reports a decrease in the total storage capacity of SA-vsanDatastore. In addition,
VMs are not compliant with the assigned VM storage policy. You must troubleshoot this problem.
97
b. Press Enter.

The customer reports that one of the ESXi hosts in the cluster often fails. The customer
wants to replace the host and restore the cluster to its normal state.
reports.
b. Click the Summary tab to view the triggered alarm notifications.
4. Review the cluster configuration details on the Summary tab.
Q1. Do any alerts appear on the ESXi hosts?

A1. Yes
Q2. Has the SA-vsanDatastore capacity decreased?

A2. Yes
98

5. Press Enter.
99
Cluster Datastore Capacity Reporting
Issue
Objective and Tasks

Lab Scenario
The application testing team at your customer's company recently commissioned and
decommissioned several VMs in a Two-Node vSAN Cluster SB-vSAN-01. Since then, the ratio of
total storage capacity to consumed capacity is not been as per the expectations. Your goal is to
troubleshoot and resolve the customer problem.
101

b. Press Enter.


The application testing team at your customer's company recently commissioned and
decommissioned several VMs in a two-node cluster SB-vSAN-01.
Now the ratio of total storage capacity to consumed capacity is not as per the expectations
on the SB-vsanDatastore.

reports.
a. Return to the vSphere Client and select the SB-vSAN-01 cluster in the left pane.

Q1. What is the total storage capacity of SB-vsanDatastore?
Q2. How many VMs are running in the SB-vSAN-01 cluster?

A2. None
Q3. What is the current used storage capacity on SB-vsanDatastore?

A3. Answer varies.
5. Open the vSAN Virtual Objects window to review further details.

a. Select the SB-vSAN-01 cluster.
b. Click the Monitor tab and select vSAN > Virtual Objects.
Q4. Are there any Unknown object types listed?
A4. Yes
102
You review your findings and identify a solution to fix the problem in the vSAN cluster.

You clean up the lab environment.
4. Disconnect remote student desktop session.
103
104
Answer Key
Lab 1 Reviewing the Lab Environment

Q1. What is the storage capacity listed for SA-vsanDatastore-01?
A1. 200 GB.
Q2. How many hosts are listed under the cluster SA-vSAN-01?
A2. Four.
Q3. What is the CPU capacity of a host?
A3. 4 CPUs x 2.8 Ghz.
Q4. What is the memory capacity of a host?
A4. 16 GB.
Q5. Which VM storage policy is set on the sa-vm-02.vclass.local VM?
A5. vSAN Default Storage Policy.
Q6. How many vSAN disk groups does each ESXi host have in the SA-vSAN-01 cluster?
A6. One.
A7. One.
Q8. What is the storage capacity offered by each vSAN disk group?
A8. 50 GB.
Q9. What type of disk groups are created in the SA-vSAN-01 cluster?
A9. All flash.
A1. Four.
Q2. How many controllers are used by vSAN? You can use esxcli vsan debug
controller list -v true to filter the list for controllers used by vSAN.
A2. One.
105
Q3. What is the maximum supported queue depth listed for the controller that is used by
vSAN?
A3. 1024.
Q4. What is the driver name of the controller that is used by vSAN?
A4. pvscsi.
A5. One.
Q6. What is the name of the distributed virtual switch that is listed?
A6. The VDS named SA-VDS.
Q7. How many uplinks are connected to each distributed virtual switch?
A7. Three: vmnic1, vmnic2 , and vmnic3.
Q8. How many configured ports are available?
A8. 512.
Q9. What is the MTU size that is configured?
A9. 1500.
A10. SA-vsanDatastore-01.
A11. 200 GB.
Q12. How many devices are in use for vSAN, identified by the In-use for vSAN state
value?
A12. Two.
Lab 2 Configuring the Second vSAN Cluster
Q1. What is the Sub-Cluster Member Count?
A1. 4.
Q2. What is the storage capacity displayed for the vSAN file system?
A2. 200 GB.
Q3. Are all the health checks green?
A3. Yes.
Q4. Which VMkernel adapter is used for vSAN?
A4. vmk1.
106
Lab 3 Working with vSAN Fault Domains
Q1. What is the state of the VM components?
A1. Active.
Q2. Why are VMs Noncompliant with the assigned storage policy despite their components
being in the Active state?
A2. The hosts are in an Implicit Fault Domain and placing two ESXi hosts in each fault domain
decreases the total number of fault domains to only two. The assigned VM Storage
Policy requires at least four fault domains to have compliant VMs.
Lab 4 Analyzing the Impact of Storage Policy Changes
Q1. Which VMs are complaint with this VM Storage Policy?
A1. sa-vm-01.vclass.local.
Q1. Are the Virtual Machine Objects complaint with the assigned VM Storage Policy?
A1. Yes.
Q2. How many components exist for each object?
A2. Four.
Q1. Were any changes made to the vSAN components layout?
A1. RAID-1 component set made up of two data components and one witness component is
now applied.
Lab 5 Identifying Objects with Reduced Availability
Q1. Why is the Placement and Availability status for the sa-vm-04.vclass.local VM showing
Reduced availability with no rebuild?
A1. The existing components set cannot meet the availability requirements defined in the VM
storage policy.
Q2. What is the Compliance Status of the VM objects?
A2. Noncompliant.
Q3. Can the VM objects tolerate a failure?
A3. No. Only one complete mirror of the data exists and no redundancy exists.
Q4. How many hosts would be required to satisfy the assigned VM storage policy settings?
A4. Five hosts are required.
Q5. Why is the VM provisioned with few components?
A5. The storage policy allowed the creation of objects even if the defined failures to tolerate
cannot be satisfied by using the Force provisioning option. The Force provisioning option
107
enables objects to be created with a minimal component set until the VM Storage Policy
can be fully applied.
Q6. How can the object become compliant in the absence of the required number of hosts?
A6. Change the VM storage policy to a policy that the current cluster configuration can
support.
Q1. How many components are displayed for each of the VM objects?
A1. Three.
Q2. Can the VM objects tolerate a failure now?
A2. Yes.
Lab 12 Verifying the vSAN Cluster Data Migration Precheck
Q1. What does the test result indicate?
A1. Some of the objects will become inaccessible and non-compliant.
Lab 16 Monitoring vSAN Performance and Capacity
Q1. Why is the vSAN back-end throughput much higher than the VM throughput?
A1. vSAN back-end throughput is higher than the VM throughput because of the additional
I/O that is generated for writing data to mirror copies and objects repair/rebuild traffic.
Lab 17 Reviewing the Troubleshooting Lab Environment
Q1. Is the SA-vSAN-01 cluster enabled for vSAN only?
A1. The cluster is also enabled for DRS and vSphere HA.
Q2. Which VM storage policy is set on the sa-vm-01 VM?
A2. Custom-vSAN-Storage-Policy
Q3. How many vSAN components are created for the sa-vm-02 VM home object?
A3. Four
Q4. Can any VMs in the SA-vSAN-01 cluster tolerate two host failures?
A4. No
Q5. How many vSAN disk groups does each ESXi host have in the SA-vSAN-01 cluster?
A5. One
A6. Two
Q7. What is the storage capacity that is offered by individual vSAN disk groups?
A7. 40 GB
108
command?
A1. Storage
A2. esxcli storage core device list
command?
A3. vsan
A4. esxcli vsan debug controller list
Q1. What is the Device Max Queue Depth listed for the storage devices?
A1. 1024
A2. Three
A3. One
Q4. What Maximum Supported Queue Depth is listed for the controller used by vSAN?
A4. 1024
Q5. What is the driver name of the controller used by vSAN?
A5. pvscsi
A6. One
Q7. What is the name of the distributed virtual switch listed?
A7. SA-VDS
Q8. How many uplinks are connected to the distributed virtual switch?
A8. Three
Q9. Are jumbo frames enabled?
A9. No
Q10. How many configured ports are there on the distributed virtual switch?
A10. 512
109
A11. SA-vsanDatastore
Q13. How many devices are in use for vSAN?
A13. Three
Lab 18 Troubleshooting the Maintenance Mode Issue
Q1. Do any alarm notifications appear on the SA-vSAN-01 cluster?
A1. No
Q2. Are any alarm notifications triggered for the customer-reported host sa-esxi-
04.vclass.local?
A2. No
Q3. What does the PRE-CHECK conclude?
A3. The host cannot enter maintenance mode.
Lab 19 Troubleshooting the vSAN Datastore Capacity Increasing Issue
Q1. What status is shown in the datastore column for the 20 GB disk detected under path
mpx.vmhba0:C0:T4:L0?
A1. Not Consumed
Q2. Is the new 20 GB disk listed in the Add Capacity Disks window?
A2. No
Lab 20 Troubleshooting the Two-Node vSAN Cluster Configuration Issue
Q1. Which VM storage policy is applied for the VM sb-vm-01?
A1. vSAN Default Storage Policy
Q2. What is the VM storage policy compliance status for sb-vm-01?
A2. Noncompliant
Lab 21 Troubleshooting the vSAN Cluster Issue
Q1. Does the number of ESXi hosts in the cluster match your previous observation?
A1. Yes
Q2. Are any alarm notifications triggered for the hosts in the cluster?
A2. Yes
Q3. Has the SA-vsanDatastore storage capacity decreased?
A3. Yes
110
Lab 22 Troubleshooting the vSAN Node Configuration Issue
Q1. Are any alarm notifications triggered for the SA-ESXi-02 host?
A1. No
Q2. Did you successfully clone the VM?
A2. No
Lab 24 Troubleshooting the vSAN Cluster Configuration Issue (2)
Q1. Has the storage capacity of the SA-vsanDatastore decreased?
A1. Yes.
Q2. Are any hosts experiencing problems in the cluster?
A2. Yes.
Q3. Do any errors or warnings appear on the ESXi host?
A3. Yes.
Lab 26 Troubleshooting the vSAN Cluster Configuration Issue (4)
Q1. Do any alerts appear on the ESXi hosts?
A1. Yes
Q2. Has the SA-vsanDatastore capacity decreased?
A2. Yes
Lab 27 Troubleshooting the vSAN Cluster Datastore Capacity Reporting
Issue
Q1. What is the total storage capacity of SB-vsanDatastore?
Q2. How many VMs are running in the SB-vSAN-01 cluster?
A2. None
Q3. What is the current used storage capacity on SB-vsanDatastore?
A3. Answer varies.
Q4. Are there any Unknown object types listed?
A4. Yes
111

Edu en Vsanft7 Lab Se

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Edu en Vsanft7 Lab Se

Uploaded by

Copyright:

Available Formats

azarpara.vahid@gmail.

VMware vSAN: Fast Track [V7]

VMware® Education Services

VMware vSAN: Fast Track [V7]

Part Number EDU-EN-VSANFT7-LAB (06-AUG-2021)

The following typographical conventions are used in this course.

Conventions Usage and Examples

Monospace Identifies command names, command options, parameters, code

• Run the esxtop command.

• ... found in the /var/log/messages file.

Monospace Identifies user inputs:

Boldface Identifies user interface controls:

• Click the Configuration tab.

Italic Identifies book titles:

• vSphere Virtual Machine Administration

<> Indicates placeholder variables:

• ... the Settings/<Your_Name>.txt file

Lab 1 Reviewing the Lab Environment..................................................................................... 1

Objective and Tasks

1. Access the Lab Environment

2. Examine the Existing vSAN Cluster Details

3. Examine the ESXi Host Configuration Details

4. Verify the vSAN Cluster Licensing

The diagram shows the lab environment topology.

The system assigned to you serves as an end-user terminal.

1. Verify that you are logged in to the student desktop.

a. On the taskbar, click the Google Chrome shortcut.

3. Proceed through the alerts and log in to the vSphere Client.

b. Log in to the vSphere Client.

• User name: administrator@vsphere.local

Task 2: Examine the Existing vSAN Cluster Details

1. Close the vCenter Server updates notification.

Q1. What is the storage capacity listed for SA-vsanDatastore-01?

Q3. What is the CPU capacity of a host?

Q4. What is the memory capacity of a host?

7. On the Summary tab, expand the VM Storage Policies panel.

Q5. Which VM storage policy is set on the sa-vm-02.vclass.local VM?

8. In the left pane, select the SA-vSAN-01 cluster.

9. In the right pane, click the Configure tab.

10. In the middle pane, click Disk Management under vSAN.

Task 3: Examine the ESXi Host Configuration Details

1. On the taskbar, click the MTPuTTY shortcut.

3. Run the esxcli vsan debug controller list command.

Q1. How many controllers are listed?

Q2. How many controllers are used by vSAN?

Q5. How many distributed virtual switches are listed?

Q8. How many configured ports are available?

Q9. What is the MTU size that is configured?

5. Run the df -h command.

Q10. What is the name of the vSAN datastore?

Q11. What is the size of the vSAN datastore?

6. Run the vdq -qH command.

7. Close the MTPuTTY window.

Task 4: Verify the vSAN Cluster Licensing

2. View vSAN Cluster Licensing Information

b. View vSAN Cluster Licensing details.

3. Minimize the vSphere Client window.

Objective and Tasks

2. Configure the vSAN Cluster Using Quickstart

3. Verify vSAN Cluster Details from the Command Line

2. In the left pane, right-click SA-Datacenter and select New Cluster.

3. In the New Cluster window, name the cluster SB-vSAN-01.

4. In the New Cluster window, enable vSAN and click OK.