Vsan 703 Monitoring Troubleshooting Guide

vSAN Monitoring and
Troubleshooting
Update 3
VMware vSphere 7.0
VMware vSAN 7.0
vSAN Monitoring and Troubleshooting
You can find the most up-to-date technical documentation on the VMware website at:
https://docs.vmware.com/
VMware, Inc.
3401 Hillview Ave.
Palo Alto, CA 94304
www.vmware.com
©
Copyright 2018-2022 VMware, Inc. All rights reserved. Copyright and trademark information.
VMware, Inc. 2
Contents
About vSAN Monitoring and Troubleshooting 5
Updated Information 6
1 Introduction to vSAN 7
2 Monitoring the vSAN Cluster 8

Monitor vSAN Capacity 8
Monitor Physical Devices 12
Monitor Devices that Participate in vSAN Datastores 13
Monitor Virtual Objects in the vSAN Cluster 13
Monitor Container Volumes in the vSAN Cluster 14
About Reserved Capacity 15
Configure Reserved Capacity 16
About vSAN Cluster Resynchronization 17
Monitor the Resynchronization Tasks in the vSAN Cluster 18
About vSAN Cluster Rebalancing 19
Configure Automatic Rebalance 19
Using the vSAN Default Alarms 20
View vSAN Default Alarms 20
View vSAN Network Alarms 20
Using the VMkernel Observations for Creating Alarms 21
Creating a vCenter Server Alarm for a vSAN Event 22
3 Monitoring vSAN Health 24

About the vSAN Health Service 24
Check vSAN Health 26
Monitor vSAN from ESXi Host Client 27
Proactive Tests 27
4 Monitoring vSAN Performance 29

About the vSAN Performance Service 29
Configure vSAN Performance Service 30
Use Saved Time Range 31
View vSAN Cluster Performance 31
View vSAN Host Performance 33
View vSAN VM Performance 34
Use IOInsight 35
VMware, Inc. 3
View IOInsight Metrics 36

Use I/O Trip Analyzer 36
Using vSAN Performance Diagnostics 37
5 Handling Failures and Troubleshooting vSAN 39

Uploading a vSAN Support Bundle 39
Using Esxcli Commands with vSAN 40
Using vsantop Command-Line Tool 43
vSAN Configuration on an ESXi Host Might Fail 43
Not Compliant Virtual Machine Objects Do Not Become Compliant Instantly 44
vSAN Cluster Configuration Issues 44
Handling Failures in vSAN 45
Failure Handling in vSAN 45
Troubleshooting vSAN 53
Replacing Existing Hardware Components 58
6 Shutting Down and Restarting the vSAN Cluster 63

Shut Down the vSAN Cluster Using the Shutdown Cluster Wizard 64
Restart the vSAN Cluster 65
Manually Shut Down and Restart the vSAN Cluster 65
VMware, Inc. 4
About vSAN Monitoring and
Troubleshooting
vSAN Monitoring and Troubleshooting describes how to monitor and troubleshoot VMware
vSAN® by using the vSphere Client, esxcli and RVC commands, and other tools.
At VMware, we value inclusion. To foster this principle within our customer, partner, and internal
community, we create content using inclusive language.
Intended Audience
This manual is intended for anyone who wants to monitor vSAN operation and performance,
or troubleshoot problems with a vSAN cluster. The information in this manual is written for
experienced system administrators who are familiar with virtual machine technology and virtual
datacenter operations. This manual assumes familiarity with VMware vSphere, including VMware
ESXi, vCenter Server, and the vSphere Client.
For more information about vSAN and how to create a vSAN cluster, see the vSAN Planning and
Deployment Guide.
For more information about vSAN features and how to configure a vSAN cluster, see
Administering VMware vSAN.
VMware, Inc. 5
Updated Information
This document is updated with each release of the product or when necessary.
This table provides the update history of vSAN Monitoring and Troubleshooting.
Revision Description
12 JUN 2023 Updated Replace a Capacity Device , Uploading a vSAN Support Bundle, and Manually Shut Down and
Restart the vSAN Cluster.
05 Dec 2022 Updated Manually Shut Down and Restart the vSAN Cluster.
08 NOV 2021 If you have a vSphere with Tanzu environment, refer the VMware Cloud Foundation Operations Guide to
shut down or startup the components. Updated Manually Shut Down and Restart the vSAN Cluster.
16 APR 2021 Updated how to replace the failed cache and capacity devices in Replace a Flash Caching Device on a
Host and Replace a Capacity Device .
21 DEC 2020 Updated the vSAN cluster shut down and restart information in Manually Shut Down and Restart the
vSAN Cluster.
06 OCT 2020 Initial release.
VMware, Inc. 6
Introduction to vSAN
1
VMware vSAN is a distributed layer of software that runs natively as a part of the ESXi
hypervisor. vSAN aggregates local or direct-attached capacity devices of a host cluster and
creates a single storage pool shared across all hosts in the vSAN cluster.
While supporting VMware features that require shared storage, such as HA, vMotion, and DRS,
vSAN eliminates the need for external shared storage and simplifies storage configuration and
virtual machine provisioning activities.
VMware, Inc. 7
Monitoring the vSAN Cluster
2
You can monitor the vSAN cluster and all the objects related to it.
You can monitor all of the objects in a vSAN environment, including hosts that participate
in a vSAN cluster and the vSAN datastore. For more information about monitoring objects
and storage resources in a vSAN cluster, see the vSphere Monitoring and Performance
documentation.
This chapter includes the following topics:
n Monitor vSAN Capacity
n Monitor Physical Devices
n Monitor Devices that Participate in vSAN Datastores
n Monitor Virtual Objects in the vSAN Cluster
n Monitor Container Volumes in the vSAN Cluster
n About Reserved Capacity
n About vSAN Cluster Resynchronization
n About vSAN Cluster Rebalancing
n Using the vSAN Default Alarms
n Using the VMkernel Observations for Creating Alarms
Monitor vSAN Capacity

You can monitor the capacity of the vSAN datastore, analyze usage, and view the capacity
breakdown at the cluster level.
The cluster Summary page includes a summary of vSAN capacity. You also can view more
detailed information in the Capacity monitor.
VMware, Inc. 8
Procedure
1 Navigate to the vSAN cluster.
2 Click the Monitor tab.
3 Under vSAN, click Capacity to view the vSAN capacity information.
Results
n The Capacity Overview displays the storage capacity of the vSAN datastore, including
total space, used space, free space, and the space that is actually written and physically
consumed on the vSAN disks. For clusters that have the deduplication and compression
enabled, you can view the deduplication and compression savings and the deduplication and
compression ratio.
Terms Description
Total space Total physical space in the cluster.
Free space Total free space in the cluster.
Used space Total written physical space in the cluster.
Actually written Actually used capacity. This capacity is displayed when

deduplication or compression are not enabled.
Object reserved Includes the reservation for objects created with a policy
that has specified object space reservation. This capacity
is not actually used by the objects.
Reserved capacity Includes the operations reserve and the host rebuild
reserve.
VMware, Inc. 9
n What if analysis enables you to estimate the free space while keeping the deduplication ratio
as 1. The effective free space is an estimation of free space available based on the storage
policy that you selected. The effective free space is smaller than the free space available on
the disks either due to the topology or the presence of fault domain in the cluster.
Oversubscription reports the vSAN capacity required if all the thin provisioned VMs and
user objects are used at full capacity. It shows a ratio of the required usage compared
with the total vSAN capacity. While calculating the oversubscription, vSAN includes all the
available VMs, user objects, and the storage policy overhead and does not consider the
vSAN namespace and swap objects.
Note Oversubscription is applicable only for vSAN hosts that are running 6.7 Update 1 or
later.
n The Usage breakdown before dedup and compression displays the usage breakdown based
on the categories such as VM usage, user objects, and system usage. You can view a pie
chart representation of the different usage categories. Click the pie chart to view the details
of the selected category.
VMware, Inc. 10
Following are the different usage categories available:
Category Description
VM usage Displays the following:

n VM home objects - Usage of VM namespace object.
n Swap objects - Usage of VM swap files.
n VMDK - Capacity consumed by VMDK objects
that reside on the vSAN datastore that can be
categorized as primary data and replica usage.
Primary data includes the actual user data written
into the physical disk which does not include any
overhead. Replica usage displays the RAID overhead
for the virtual disk.
n VM memory snapshots - Usage of memory snapshot
file for VMs.
n Block container volumes (attached to a VM) -
Capacity consumed by the container objects that are
attached to a VM.
n vSphere replication persistent state file - vSAN object
used to store the persistent state file (PSF) at source
site.
User objects Displays iSCSI objects, block container volumes that are
not attached to VM, user-created files, ISO files, VM
templates, files shares, file container volumes, and vSAN
objects used by the vSphere replication service at the
target site.
System usage Displays the following:

n Performance management objects - Capacity
consumed by objects created for storing
performance metrics when you enable the
performance service.
n File system overhead - vSAN on-disk format
overhead that may take up on the capacity drives.
n Checksum overhead - Overhead to store all the
checksums.
n Dedup & compression overhead - Overhead to get
the benefits of deduplication and compression. This
data is visible only if you enable deduplication and
compression.
n Operations usage - Temporary space usage in
a cluster. The temporary space usage includes
temporary capacity used for rebalance operations or
moving objects due to FTT changes.
When you enable deduplication and compression, it might take several minutes for capacity
updates to be reflected in the Capacity monitor, as disk space is reclaimed and reallocated.
For more information about deduplication and compression, see "Using Deduplication and
Compression" in Administering VMware vSAN.
You can check the history of capacity usage in the vSAN datastore. Click Capacity History, select
a time range, and click Show Results.
VMware, Inc. 11
The Capacity monitor displays two thresholds represented as vertical markers in the bar chart:
n Operations threshold - Displays the space vSAN requires to perform internal operations in the
cluster. If the used space reaches beyond that threshold, vSAN might not be able to operate
properly.
n Host rebuild threshold - Displays the space vSAN requires to tolerate one host failure. If the
used space reaches beyond the host rebuild threshold and the host fails, vSAN might not
successfully restore all data from the failed host.
If you enable reserved capacity, the Capacity monitor displays the following:
n Operations reserve - Reserved space in the cluster for internal operations.
n Host rebuild reserve - Reserved space for vSAN to be able to repair in case of single host
failure. The Capacity monitor displays the host rebuild threshold only when the host rebuild
reserve is enabled.
If the resynchronization of objects is in progress in a cluster, vSAN displays the capacity used in
the capacity chart as operations usage. In case there is enough free space in the cluster, vSAN
might use more space than the operations threshold for the resyncing operations to complete
faster.
Use Configure to enable the capacity reserve. You can also use Configure > vSAN > Services
to enable the capacity reserve. For more information on configuring the reserved capacity, see
Configure Reserved Capacity.
In a cluster, if there is more utilization than the host rebuild threshold and the reserved capacity
is not enabled, the capacity chart turns yellow displaying a warning state. A health alarm is
generated indicating that if the most consumed host fails, vSAN cannot recover the data. If
you enable the host rebuild reserve, the capacity chart turns yellow at 80% of the host rebuild
threshold. If the used space reaches beyond the operations threshold and the reserved capacity
is not enabled, vSAN cannot perform or complete operations such as rebalance, resync object
components due to policy changes, and so on. In that case, the bar chart turns red. A health
alarm is generated indicating that the disk usage exceeds the operations threshold. For more
information about capacity reserve, see About Reserved Capacity.
Monitor Physical Devices

You can monitor hosts, cache devices, and capacity devices used in the vSAN cluster.
Procedure
2 Click the Configure tab.
VMware, Inc. 12
3 Click Disk Management to review all hosts, cache devices, and capacity devices in the cluster.
The physical location is based on the hardware location of cache and capacity devices on
vSAN hosts. You can see the virtual objects on any selected host, disk group, or disk and
view the impact of the selected entity to the virtual objects in the cluster.
Monitor Devices that Participate in vSAN Datastores

Verify the status of the devices that back up the vSAN datastore. You can check whether the
devices experience any problems.
Procedure
1 Navigate to Storage.
2 Select the vSAN datastore.
You can view general information about the vSAN datastore, including capacity, capabilities,
and the default storage policy.
4 Display information about local devices.
a Click Disk Management and select the disk group to display local devices in the table at
the bottom of the page.
b Click Capacity to review information about the amount of capacity provisioned and used
in the cluster, and also to review a breakdown of the used capacity by object type or by
data type.
Monitor Virtual Objects in the vSAN Cluster

You can view the status of virtual objects in the vSAN cluster.
When one or more hosts are unable to communicate with the vSAN datastore, the information
about virtual objects might not displayed.
Procedure
3 Under vSAN, select Virtual Objects to view the corresponding virtual objects in the vSAN
cluster.
VMware, Inc. 13
4 Click to filter the virtual objects based on name, type, storage policy, and UUID.
a Select the check box on one of the virtual objects and click View Placement Details to
open the Physical Placement dialog box. You can view the device information, such as
name, identifier or UUID, number of devices used for each virtual machine, and how they
are mirrored across hosts.
b On the Physical Placement dialog box, select the Group components by host placement
check box to organize the objects by host and by disk.
Note At the cluster level, the Container Volumes filter displays detached container volumes.
To view attached volumes, expand the VM to which the container is attached.
5 Select the check box of the attached block type or file volumes and click View Performance.
You can use the vSAN cluster performance charts to monitor the workload in your cluster.
For more information on the vSAN cluster performance charts, see View vSAN Cluster
Performance.
6 Select the check box on one of the container volumes and click View Container Volume. For
more information about monitoring container volumes, see Monitor Container Volumes in the
vSAN Cluster.
7 Select the check box on one of the file volumes and click View File Share. For more
information about file volume, see Administering VMware vSAN.
Monitor Container Volumes in the vSAN Cluster

You can view the status of the container volumes in the vSAN cluster.
Procedure
3 Under Cloud Native Storage, select Container Volumes to view the container volumes in the
vSAN cluster. You can view information about the volume name, label, datastore, compliance
status, health status, and capacity quota.
4 Click to view the following:
n Click the Basics tab to view the volume details such as volume type, ID, datastore,
storage policy, compliance, and health status.
n Click the Kubernetes objects tab to view Kubernetes related data such as Kubernetes
cluster, namespace, pod, persistent volume claim, labels, and so on.
n Click the Physical Placement tab to view the type, host, cache, and capacity disk of the
virtual object components.
n Click the Performance tab to view the performance of the container volumes.
VMware, Inc. 14
5 Select the check box for the volumes that have an out-of-date policy status. Click Reapply
Policy to reapply the policy on the selected volumes.
6 Select the check box for the container volume you want to delete and click Delete.
7 Use the Add Filter option to add filters to the container volumes.
About Reserved Capacity

vSAN requires capacity for its internal operations. For a cluster to be able to tolerate a single
host failure, vSAN requires free space to restore the data of the failed host. The capacity
required to restore a host failure matches the total capacity of the largest host in the cluster.
These values are represented as thresholds in the Capacity Monitor page:
n Operations threshold - Displays the space vSAN requires to run its internal operations in
the cluster. If the used space exceeds the operations threshold, vSAN might not operate
properly.
n Host rebuild threshold - Displays the space vSAN requires to tolerate one host failure. If
the used space exceeds the host rebuild threshold and the host fails, vSAN might not
successfully restore all data from the failed host.
For more information on the capacity thresholds, see Monitor vSAN Capacity.
vSAN provides you the option to reserve the capacity in advance so that it has enough free
space available to perform internal operations and to repair data back to compliance following a
single host failure. By enabling reserve capacity in advance, vSAN prevents you from using the
space to create workloads and intends to save the capacity available in a cluster. By default, the
reserved capacity is disabled.
If there is enough free space in the vSAN cluster, you can enable the operations reserve and/or
the host rebuild reserve.
n Operations reserve - Reserved space in the cluster for vSAN internal operations.
n Host rebuild reserve - Reserved space for vSAN to be able to repair in case of a single host
failure.
These soft reservations prevent the creation of new VMs or powering on VMs if such operations
consume the reserved space. Once the reserved capacity is enabled, vSAN does not prevent
powered on VM operations, such as I/O from the guest operating system or applications from
consuming the space even after the threshold limits are reached. After you enable the reserved
capacity, you must monitor the disk space health alerts and capacity usage in the cluster and
take appropriate actions to keep the capacity usage below the threshold limits.
Note The reserved capacity is not supported on a stretched cluster, cluster with fault domains
and nested fault domains, ROBO cluster, or if the number of hosts in the cluster is less than four.
VMware, Inc. 15
To enable reserved capacity for the host rebuild, you must first enable the operations reserve.
When you enable operations reserve, vSAN reserves 5% additional capacity in the operations
reserve as a buffer to ensure you have time to react to the capacity fullness before the actual
threshold is reached.
vSAN indicates when the capacity usage is high in a cluster. The indications can be in the form of
health alerts, capacity chart turning yellow or red, and so on. Due to the reservation, vSAN might
not have enough free space left. This results in the inability to create VMs or VM snapshots,
creating or extending virtual disks, and so on.
Note You cannot enable reserved capacity, if the cluster is at a capacity higher than the
specified threshold.
Capacity Reservation Considerations

Following are the considerations if you enable reserved capacity:
n When you enable reserved capacity with the host rebuild reserve and a host is put into
maintenance mode, the host might not come back online. In this case, vSAN continues to
reserve capacity for another host failure. This host failure is in addition to the host that is
already in the maintenance mode. This might cause the failure of operations if the capacity
usage is above the host rebuild threshold.
n When you enable reserved capacity with the host rebuild reserve and a host fails, vSAN
might not start repairing the affected objects until the repair timer expires. During this
time, vSAN continues to reserve capacity for another host failure. This can cause failure of
operations if the capacity usage is above the current host rebuild threshold, after the first
host failure. After the repairs are complete, you can disable the reserved capacity for the
host rebuild reserve if the cluster does not have the capacity for another host failure.
Configure Reserved Capacity

You can configure reserved capacity for a vSAN cluster to reserve capacity for internal
operations or to reserve capacity for data repair following a single host failure.
Prerequisites
Ensure that you have the following required privileges: Host.Inventory.EditCluster and
Host.Config.Storage.
Verify that the vSAN cluster:
n Is not configured as a stretched cluster or ROBO cluster.
n Has no fault domains and nested fault domains created.
n Has a minimum of four hosts.
Procedure
VMware, Inc. 16
3 Under vSAN, select Services.
4 Click to edit the Reservations and Alerts.
5 Click to enable or disable the operations reserve. On enabling the operations reserve, vSAN
ensures that the cluster has enough space to complete the internal operations.
6 Click to enable or disable the host rebuild reserve. On enabling the host rebuild reserve,
vSAN provides the reservation of space to repair data back to compliance following a single
host failure. You can enable the host rebuild reserve only after you enable the operations
reserve. After enabling, if you disable the operations reserve, the host rebuild reserve gets
automatically disabled.
7 Select Customize alerts. You can set a customized threshold to receive warning and error
alerts. The threshold percentage is calculated based on the available capacity, which is
the difference between the total capacity and the reserved capacity. If you do not set a
customized value, vSAN uses the default thresholds to generate alerts.
8 Click Apply.
About vSAN Cluster Resynchronization

You can monitor the status of virtual machine objects that are being resynchronized in the vSAN
cluster.
When a hardware device, host, or network fails, or if a host is placed into maintenance mode,
vSAN initiates resynchronization in the vSAN cluster. However, vSAN might briefly wait for the
failed components to come back online before initiating resynchronization tasks.
The following events trigger resynchronization in the cluster:
n Editing a virtual machine (VM) storage policy. When you change VM storage policy settings,
vSAN might initiate object recreation and subsequent resynchronization of the objects.
Certain policy changes might cause vSAN to create another version of an object and
synchronize it with the previous version. When the synchronization is complete, the original
object is discarded.
vSAN ensures that VMs continue to run, and resynchronization does not interrupt their
operation. This process might require additional temporary capacity.
n Restarting a host after a failure.
n Recovering hosts from a permanent or long-term failure. If a host is unavailable for more than
60 minutes (by default), vSAN creates copies of data to recover the full policy compliance.
n Evacuating data by using the Full data migration mode before you place a host in
maintenance mode.
n Exceeding the capacity threshold of a capacity device. Resynchronization is triggered when a

capacity device in the vSAN cluster approaches or exceeds the threshold level of 80 percent.
VMware, Inc. 17
Monitor the Resynchronization Tasks in the vSAN Cluster

To evaluate the status of objects that are being resynchronized, you can monitor the
resynchronization tasks that are currently in progress.
Prerequisites
Verify that hosts in your vSAN cluster are running ESXi 7.0 or later.
Procedure
2 Select the Monitor tab.
3 Click vSAN.
4 Select Resyncing objects.
5 Track the progress of resynchronization of virtual machine objects.
The Object Repair Time defines the time vSAN waits before repairing a non-compliant
object after placing a host in a failed state or maintenance mode. The default setting is 60
minutes. To change the setting, edit the Object Repair Timer (Configure > vSAN > Services >
Advanced Options).
You can also view the following information about the objects that are resynchronized:
Objects Description
Total resyncing objects Total number of objects to be resynchronized in the

vSAN cluster.
Bytes left to resync Data (in bytes) that is remaining before the
resynchronization is complete.
Total resyncing ETA Estimated time left for the resynchronization to

complete.
The objects to be resynchronized are categorized as
active, queued, and suspended. The objects that are
actively synchronizing fall in the active category. The
objects that are in the queue for resynchronization are
the queued objects. The objects that were actively
synchronizing but are now in the suspended state falls
in the suspended category.
Scheduled resyncing Remaining number of objects to be resynchronized.

You can classify scheduled resyncing into two
categories: scheduled and pending. The scheduled
category displays the objects that are not
resyncing because the delay timer has not expired.
Resynchronization of objects starts once the timer
expires. The pending category displays the objects with
the expired delay timer that cannot be resynchronized.
This can be due to insufficient resources in the current
cluster or the vSAN FTT policy set on the cluster not
being met.
VMware, Inc. 18
You can also view the resynchronization objects based on various filters such as Intent and
Status. Using Show first, you can modify the view to display the number of objects.
About vSAN Cluster Rebalancing

When any capacity device in your cluster reaches 80 percent full, vSAN automatically rebalances
the cluster, until the space available on all capacity devices is below the threshold.
Cluster rebalancing evenly distributes resources across the cluster to maintain consistent
performance and availability.
The following operations can cause disk capacity to reach 80% and initiate cluster rebalancing:
n Hardware failures occur on the cluster.
n vSAN hosts are placed in maintenance mode with the Evacuate all data option.
n vSAN hosts are placed in maintenance mode with Ensure data accessibility when objects
assigned FTT=0 reside on the host.
Note To provide enough space for maintenance and reprotection, and to minimize automatic
rebalancing events in the vSAN cluster, consider keeping 30-percent capacity available at all
times.
Configure Automatic Rebalance

vSAN automatically rebalances data on the disk groups by default. You can configure settings for
automatic rebalancing.
Your vSAN cluster can become unbalanced due to uneven I/O patterns to devices, or when you
add hosts or capacity devices. If the cluster becomes unbalanced, vSAN automatically rebalances
the disks. This operation moves components from over-utilized disks to under-utilized disks.
You can enable or disable automatic rebalance, and configure the variance threshold for
triggering an automatic rebalance. If any two disks in the cluster have a capacity variance that
meets the rebalancing threshold, vSAN begins rebalancing the cluster.
Disk rebalancing can impact the I/O performance of your vSAN cluster. To avoid this
performance impact, you can turn off automatic rebalance when peak performance is required.
Procedure
4 Click to edit Advanced Options.
5 Click to enable or disable Automatic Rebalance.
You can change the variance threshold to any percentage from 20 to 75.
VMware, Inc. 19
What to do next
You can use the vSAN health service to check the disk balance. Expand the Cluster category, and
select vSAN Disk Balance.
Using the vSAN Default Alarms

You can use the default vSAN alarms to monitor the cluster, hosts, and existing vSAN licenses.
The default alarms are automatically triggered when the events corresponding to the alarms
are activated or if one or all the conditions specified in the alarms are met. You cannot edit
the conditions or delete the default alarms. To configure alarms that are specific to your
requirements, create custom alarms for vSAN. See Creating a vCenter Server Alarm for a vSAN
Event.
For information about monitoring alarms, events, and editing existing alarm settings, see the
vSphere Monitoring and Performance documentation.
View vSAN Default Alarms

Use the default vSAN alarms to monitor your cluster, hosts, analyze any new events, and assess
the overall cluster health.
Procedure
2 Click Configure and then click Alarm Definitions.
3 Click and type vSAN in the search box to display the alarms that are specific to vSAN.
Type vSAN Health Service Alarm to search for vSAN health service alarms.
The default vSAN alarms are displayed.
4 From the list of alarms, click each alarm to view the alarm definition.
View vSAN Network Alarms

vSAN network diagnostics queries the latest network metrics and compares the metrics statistics
with the defined threshold values. If the value reaches above the threshold that you have
set, vSAN network diagnostics raises an alarm. You must acknowledge and manually reset the
triggered alarms to green after fixing the network issues.
Prerequisites
The vSAN performance service must be turned on.
Procedure
1 Navigate to the host in the vSAN cluster.
VMware, Inc. 20
3 Under vSAN, select Performance.
4 Select Physical Adapters, and select a NIC. Select a time range for your query. vSAN displays
performance charts for the physical NIC (pNIC), including throughput, packets per second,
and packets loss rate.
5 Select . In the Threshold settings dialog box, enter a threshold value to receive warning
and error alert.
6 Click Save.
Results
vSAN displays the performance statistics of all the network I/Os in use. vSAN network
diagnostics result appears in the vCenter Server alerts. The redirection to the related
performance charts is available in the vSAN network alerts generated by the network diagnostics
service.
Using the VMkernel Observations for Creating Alarms

VMkernel Observations (VOBs) are system events that you can use to set up vSAN alarms for
monitoring and troubleshooting performance and networking issues in the vSAN cluster. In vSAN,
these events are known as observations.
VMware ESXi Observation IDs for vSAN

Each VOB event is associated with an identifier (ID). Before you create a vSAN alarm in the
vCenter Server, you must identify an appropriate VOB ID for the vSAN event for which you want
to create an alert. You can create alerts in the VMware ESXi Observation Log file (vobd.log). For
example, use the following VOB IDs to create alerts for any device failures in the cluster.
n esx.problem.vob.vsan.lsom.diskerror
n esx.problem.vob.vsan.pdl.offline
To review the list of VOB IDs for vSAN, open the vobd.log file located on your ESXi host in
the /var/log directory. The log file contains the following VOB IDs that you can use for creating
vSAN alarms.
Table 2-1. VOB IDs for vSAN
VOB ID Description
esx.audit.vsan.clustering.enabled The vSAN clustering service is enabled.
esx.clear.vob.vsan.pdl.online The vSAN device has come online.
esx.clear.vsan.clustering.enabled The vSAN clustering service is enabled.
esx.clear.vsan.vsan.network.available vSAN has one active network configuration.
VMware, Inc. 21
Table 2-1. VOB IDs for vSAN (continued)
VOB ID Description
esx.clear.vsan.vsan.vmknic.ready A previously reported vmknic has acquired a valid IP.
esx.problem.vob.vsan.lsom.componentthresh vSAN reaches the near node component count limit.

old
esx.problem.vob.vsan.lsom.diskerror A vSAN device is in a permanent error state.
esx.problem.vob.vsan.lsom.diskgrouplimit vSAN fails to create a disk group.
esx.problem.vob.vsan.lsom.disklimit vSAN fails to add devices to a disk group.
esx.problem.vob.vsan.lsom.diskunhealthy vSAN disk is unhealthy.
esx.problem.vob.vsan.pdl.offline A vSAN device is offline.
esx.problem.vsan.clustering.disabled vSAN clustering services are disabled.
esx.problem.vsan.lsom.congestionthreshold vSAN device memory or SSD congestion has been updated.
esx.problem.vsan.net.not.ready A vmknic is added to vSAN network configuration without a valid IP

address. This happens when the vSAN network is not ready.
esx.problem.vsan.net.redundancy.lost The vSAN network configuration does not have the required
redundancy.
esx.problem.vsan.no.network.connectivity vSAN does not have existing networking configuration, which is in use.
esx.problem.vsan.vmknic.not.ready A vmknic is added to the vSAN network configuration without a valid

IP address.
esx.problem.vob.vsan.lsom.devicerepair The vSAN device is offline and in a repaired state because of I/O
failures.
Creating a vCenter Server Alarm for a vSAN Event

You can create alarms to monitor events on the selected vSAN object, including the cluster,
hosts, datastores, networks, and virtual machines.
Prerequisites
You must have the required privilege level of Alarms.Create Alarm or Alarm.Modify Alarm
Procedure
2 On the Configure tab, select Alarm Definitions and click Add.
3 In the Name and Targets page, enter a name and description for the new alarm.
4 From the Target type drop-down menu, select the type of inventory object that you want this
alarm to monitor and click Next.
Depending on the type of target that you choose to monitor, the summary that follows the
Targets, change.
VMware, Inc. 22
5 In the Alarm Rule page, select a trigger from the drop-down menu.
The combined event triggers are displayed. You can set the rule for a single event only. You
must create multiple rules for multiple events.
6 Click Add Argument to select an argument from the drop-down menu.
a Select an operator from the drop-down menu.
b Select an option from the drop-down menu to set the threshold for triggering an alarm.
c Select severity of the alarm from the drop-down menu. You can set the condition to
either Show as Warning or Show as Critical, but not for both. You must create a separate
alarm definition for warning and critical status.
7 Select Send email notifications, to send email notifications when alarms are triggered.
8 In the Email to text box, enter recipient addresses. Use commas to separate multiple
addresses.
9 Select Send SNMP traps to send traps when alarms are triggered on a vCenter Server
instance.
10 Select Run script to run scripts when alarms are triggered.
11 In the Run this script text box, enter the following script or command:
For this type of command... Enter this...
EXE executable files Full pathname of the command. For example, to run the cmd.exe command
in the C:\tools directory, type:
c:\tools\cmd.exe
BAT batch file Full pathname of the command as an argument to the

c:\windows\system32\cmd.exe command. For example, to run the cmd.bat
command in the C:\tools directory, type:
c:\windows\system32\cmd.exe /c c:\tools\cmd.bat
12 Select an advanced action from the drop-down menu. You can define the advanced actions
for virtual machine and hosts. You can add multiple advanced actions for an alarm.
13 Click Next to set the Reset Rule.
14 Select Reset the alarm to green and click Next to review the alarm definition.
15 Select Enable this alarm to enable the alarm and click Create.
Results
The alarm is configured.
VMware, Inc. 23
Monitoring vSAN Health
3
You can check the overall health of the vSAN cluster, including hardware compatibility,
networking configuration and operations, advanced vSAN configuration options, storage device
health and virtual machine object health.
n About the vSAN Health Service
n Check vSAN Health
n Monitor vSAN from ESXi Host Client
n Proactive Tests
About the vSAN Health Service

Use the vSAN health service to monitor the health of your vSAN cluster.
You can use the vSAN health checks to monitor the status of cluster components, diagnose
issues, and troubleshoot problems. The health checks cover hardware compatibility, network
configuration and operation, advanced vSAN configuration options, storage device health, and
virtual machine objects.
VMware, Inc. 24
You can use Overview to monitor the core health issues of your vSAN cluster. You can also view
the following:
n Health check count based on the health status
n Primary issues with the nested issues. These nested issues might be caused by the primary
issue and resolving the primary issue might solve the related nested issues.
n Other standalone health issues without any dependency
The vSAN health checks are divided into categories. Each category contains individual health
checks.
Table 3-1. vSAN Health Check Categories
Health Check Category Description
Hardware Compatibility Monitor the cluster components to ensure that they are using supported
hardware, software, and drivers. To identify a device with duplicate PCI ID
in the vSAN cluster, see Examine Health Warning of an Unidentified NVMe
Device.
Performance Service Monitor the health of vSAN performance service.
Network Monitor vSAN network health.
Physical disk Monitor the health of physical disks in the vSAN cluster.
Data Monitor vSAN data health.
Cluster Monitor vSAN cluster health.
Capacity utilization Monitor vSAN cluster capacity.
Online health Monitor vSAN cluster health and send to VMware’s analytics backend
system for advanced analysis. You must participate in the Customer
Experience Improvement Program to use online health checks.
vSAN Build Recommendation Monitor vSAN build recommendations for vSphere Lifecycle Manager.
vSAN iSCSI target service Monitor the iSCSI target service, including the network configuration and
runtime status.
Data-at-rest encryption Monitor vSAN data-at-rest encryption health.
Data-in-transit encryption Monitor vSAN data-in-transit encryption health.
File Service Monitor vSAN file service health.
Stretched cluster Monitor the health of a stretched cluster, if applicable. For more information
on "Witness appliance upgrade to vSphere 7.0 or higher with caution", see
the VMware knowledge base article at https://kb.vmware.com/s/article/
76948.
Hyperconverged cluster configuration Monitor the status of hosts and settings configured through the Quickstart
compliance workflow.
vSAN periodically retests each health check and updates the results. To run the health checks
and update the results immediately, click the Retest button.
VMware, Inc. 25
If you participate in the Customer Experience Improvement Program, you can run health checks
and send the data to VMware for advanced analysis. Click the Retest with Online health button.
For more information about vSAN health checks, see the VMware knowledge base article at
https://kb.vmware.com/s/article/2114803.
Monitoring vSAN Health on a Host

The ESXi host client is a browser-based interface for managing a single ESXi host. It enables
you to manage the host when vCenter Server is not available. The host client provides tabs for
managing and monitoring vSAN at the host level.
n The vSAN tab displays basic vSAN configuration.
n The Hosts tab displays the hosts participating in the vSAN cluster.
n The Health tab displays host-level health checks.
Viewing vSAN Health History

The vSAN health history helps you examine health issues by querying the historical health
records. You can only view the historical health data of a cluster. By default, the health history is
enabled. To disable the health history, select the cluster and navigate to the Configure > vSAN
> Services > Historical Health Service and click Disable. If you disable the health history, all
the health data collected on the vCenter Server database gets purged. The database stores the
health data for up to 30 days depending on the available capacity.
Using the Skyline Health view, you can use the toggle button to view the health history and then
select a time range. The start date of the time range must not be earlier than 30 days from the
current date. The end date must not be later than the current date. Based on your selection,
you can view the aggregated health status of each health check. Click a health check to view
the history of that health check within a certain time period. The historical data is displayed as
a graphical representation with green circles, yellow triangles, and red squares showing success,
warning, and failure respectively. The detailed information about each health check result is
displayed in a table.
Check vSAN Health

You can view the status of vSAN health checks to verify the configuration and operation of your
vSAN cluster.
Prerequisites
Procedure
VMware, Inc. 26
3 Under vSAN, select Skyline Health to review the vSAN health check categories.
n If the Test Result column displays a Warning (yellow) or Failed (red) icon, expand the
category to review the results of individual check findings.
n Select an individual health check to view the detailed information.
n In the Info section, you can click the Ask VMware button to open a knowledge base
article that describes the health check and provides information about how to resolve the
issue.
n You can click SILENCE ALERT on a health check, so it does not display any warnings or
failures.
Monitor vSAN from ESXi Host Client

You can monitor vSAN health and basic configuration through the ESXi host client.
Procedure
1 Open a browser and enter the IP address of the host.
The browser redirects to the login page for the host client.
2 Enter the username and password for the host, and click Login.
3 In the host client navigator, click Storage.
4 In the main page, click the vSAN datastore to display the Monitor link in the navigator.
5 Click the tabs to view vSAN information for the host.
a Click the vSAN tab to display basic vSAN configuration.
b Click the Hosts tab to display the hosts participating in the vSAN cluster.
c Click the Health tab to display host-level health checks.
6 (Optional) On the vSAN tab, click Edit Settings to correct configuration issues at the host
level.
Select the values that match the configuration of your vSAN cluster, and click Save.
Proactive Tests
You can initiate a health test on your vSAN cluster to verify that the cluster components are
working as expected.
Note You must not conduct the proactive test in a production environment as it creates network
traffic and impacts the vSAN workload.
VMware, Inc. 27
Run the VM creation test to verify the vSAN cluster health. Running the test creates a virtual
machine on each host in the cluster. The test creates a VM and deletes it. If the VM creation and
deletion tasks are successful, assume that the cluster components are working as expected and
the cluster is functional.
Run the Network performance test to detect and diagnose connectivity issues, and to make
sure the network bandwidth between the hosts supports the requirements of vSAN. The test
is performed between the hosts in the cluster. It verifies that the network bandwidth between
hosts, and reports a warning if the bandwidth is less than 850Mbps.
To access a proactive test, select your vSAN cluster in the vSphere Client, and click the Monitor
tab. Click vSAN > Proactive Tests.
VMware, Inc. 28
Monitoring vSAN Performance
4
You can monitor the performance of your vSAN cluster. Performance charts are available for
clusters, hosts, physical disks, virtual machines, and virtual disks.
n About the vSAN Performance Service
n Configure vSAN Performance Service
n Use Saved Time Range
n View vSAN Cluster Performance
n View vSAN Host Performance
n View vSAN VM Performance
n Use IOInsight
n Use I/O Trip Analyzer
n Using vSAN Performance Diagnostics
About the vSAN Performance Service

You can use vSAN performance service to monitor the performance of your vSAN environment,
and investigate potential problems.
The performance service collects and analyzes performance statistics and displays the data in a
graphical format. You can use the performance charts to manage your workload and determine
the root cause of problems.
VMware, Inc. 29
When the vSAN performance service is turned on, the cluster summary displays an overview
of vSAN performance statistics, including IOPS, throughput, and latency. You can view detailed
performance statistics for the cluster, and for each host, disk group, and disk in the vSAN cluster.
You also can view performance charts for virtual machines and virtual disks.
Configure vSAN Performance Service

Use the vSAN Performance Service to monitor the performance of vSAN clusters, hosts, disks,
and VMs.
Note When you create a vSAN cluster in the vSphere Client, the Performance Service is
disabled. You can enable and configure the Performance Service.
To support the Performance Service, vSAN uses a Stats database object to collect statistical
data. The Stats database is a namespace object in the cluster's vSAN datastore.
Prerequisites
n All hosts in the vSAN cluster must be running ESXi 7.0 or later.
n Before you configure the vSAN Performance Service, make sure that the cluster is properly
configured and has no unresolved health problems.
Procedure
4 Click the Performance Service Edit button.
VMware, Inc. 30
5 Click to enable vSAN Performance Service.
6 Select a storage policy for the Stats database object.
7 (Optional) Click to enable the verbose mode. This check box appears only after enabling
vSAN Performance Service. When enabled, vSAN collects and saves the additional
performance metrics to a Stats DB object. If you enable the verbose mode for more than
5 days, a warning message appears indicating that the verbose mode can be resource-
intensive. Ensure that you do not enable it for a longer duration.
8 (Optional) Click to enable the network diagnostic mode. This check box appears only
after enabling vSAN Performance Service. When enabled, vSAN collects and saves the
additional network performance metrics to a RAM disk stats object. If you enable the network
diagnostic mode for more than a day, a warning message appears indicating that the
network diagnostic mode can be resource-intensive. Ensure that you do not enable it for
a longer duration.
9 Click Apply.
Use Saved Time Range

You can select saved time ranges from the time range picker in performance views.
You can manually save a time range with customized name. When you run a storage
performance test, the selected time range is saved automatically. You can save a time range
for any of the performance views.
Prerequisites
n The vSAN performance service must be turned on.
n All hosts in the vSAN cluster must be running ESXi 7.0 or later.
Procedure
2 Click the Monitor tab and click Performance.
3 Select any tab, such as Backend. In the time range drop-down, select Save.
4 Enter a name for the selected time range.
5 Confirm your changes.
View vSAN Cluster Performance

You can use the vSAN cluster performance charts to monitor the workload in your cluster and
determine the root cause of problems.
VMware, Inc. 31
When the performance service is turned on, the cluster summary displays an overview of vSAN
performance statistics, including vSAN IOPS, throughput, and latency. At the cluster level, you
can view detailed statistical charts for virtual machine consumption and the vSAN back end.
Note
n To view iSCSI performance charts, all hosts in the vSAN cluster must be running ESXi 7.0 or
later.
n To view file service performance charts, you must enable vSAN File Service.
Prerequisites
The vSAN performance service must be turned on before you can view performance charts.
Procedure
4 Select VM.
Perform one of the following:
n Select Cluster level metrics to display the aggregated performance metrics for the cluster
that you selected.
n Select Show specific VMs to display metrics for all the VMs selected. If you enable Show
separate chart by VMs, vSAN displays separate metrics for all the VMs selected.
n Select Top Contributors to identify the VMs or disk groups that consume the most IOPS,
have the highest I/O throughput, or I/O latency. For example, based on the I/O latency
graph of the cluster, you can select a timestamp and get the top contributors with latency
statistics. You can also select a single contributor and view the latency graph.
Select a time range for your query. vSAN displays performance charts for clients running
on the cluster, including IOPS, throughput, latency, congestions, and outstanding I/Os. The
statistics on these charts are aggregated from the hosts within the cluster.
5 Select Backend. Select a time range for your query. vSAN displays performance charts
for the cluster back-end operations, including IOPS, throughput, latency, congestions, and
outstanding I/Os. The statistics on these charts are aggregated from the hosts within the
cluster.
6 Select File Share and choose a file. Select a time range for your query. Select NFS
performance or File system performance based on the protocol layer performance or file
system layer performance that you want to display. vSAN displays performance charts for
vSAN file services, including IOPS, throughput, and latency.
VMware, Inc. 32
7 Select iSCSI and select an iSCSI target or LUN. Select a time range for your query. vSAN
displays performance charts for iSCSI targets or LUNs, including IOPS, bandwidth, latency,
and outstanding I/O.
8 (Optional) Select IOInsight. For more information on IOInsight, see Use IOInsight.
9 Select vSAN Direct to display the performance data of the vSAN direct disks. Select a time
range for your query. vSAN displays performance charts for vSAN direct, including IOPS,
bandwidth, latency, and outstanding I/O.
10 Click Refresh or Show Results to update the display.
View vSAN Host Performance

You can use the vSAN host performance charts to monitor the workload on your hosts and
determine the root cause of problems. You can view vSAN performance charts for hosts, disk
groups, and individual storage devices.
When the performance service is turned on, the host summary displays performance statistics
for each host and its attached disks. At the host level, you can view detailed statistical charts for
virtual machine consumption and the vSAN back end, including IOPS, throughput, latency, and
congestion. Additional charts are available to view the local client cache read IOPS and hit rate.
At the disk group level, you can view statistics for the disk group. At the disk level, you can view
statistics for an individual storage device.
Prerequisites
To view the following performance charts, hosts in the vSAN cluster must be running ESXi 7.0
or later: Physical Adapters, VMkernal Adapters, VMkernal Adapters Aggregation, iSCSI, vSAN -
Backend resync I/Os, resync IOPS, resync throughput, Disk Group resync latency.
Procedure
1 Navigate to the vSAN cluster, and select a host.
4 Select VM. Select a time range for your query. vSAN displays performance charts for clients
running on the host, including IOPS, throughput, latency, congestions, and outstanding I/Os.
5 Select Backend. Select a time range for your query. vSAN displays performance charts for
the host back-end operations, including IOPS, throughput, latency, congestions, outstanding
I/Os, and resync I/Os.
VMware, Inc. 33
6 Select Disks, and select a disk group. Select a time range for your query. vSAN displays
performance charts for the disk group, including front end (Guest) IOPS, throughput,
and latency, as well as overhead IOPS and latency. It also displays the read-cached
hit rate, evictions, write-buffer free percentage, capacity and usage, cache disk destage
rate, congestions, outstanding I/O, outstanding I/O size, delayed I/O percentage, delayed
I/O average latency, internal queue IOPS, internal queue throughput, resync IOPS, resync
throughput, and resync latency.
7 Select Physical Adapters, and select a NIC. Select a time range for your query. vSAN displays
performance charts for the physical NIC (pNIC), including throughput, packets per second,
and packets loss rate.
8 Select Host Network, and select a VMkernel adapter, such as vmk1. Select a time range for
your query. vSAN displays performance charts for all network I/Os processed in the network
adapters used by vSAN, including throughput, packets per second, and packets loss rate.
9 Select iSCSI. Select a time range for your query. vSAN displays performance charts for all the
iSCSI services on the host, including IOPS, bandwidth, latency, and outstanding I/Os.
10 (Optional) Select IOInsight. For more information on IOInsight, see Use IOInsight.
11 Select vSAN Direct to display the performance data of the vSAN direct disks. Select a time
range for your query. vSAN displays performance charts for vSAN direct, including IOPS,
bandwidth, latency, and outstanding I/O.
View vSAN VM Performance

You can use the vSAN VM performance charts to monitor the workload on your virtual machines
and virtual disks.
When the performance service is turned on, you can view detailed statistical charts for virtual
machine performance and virtual disk performance. VM performance statistics cannot be
collected during migration between hosts, so you might notice a gap of several minutes in the
VM performance chart.
Note The performance service supports only virtual SCSI controllers for virtual disks. Virtual
disks using other controllers, such as IDE, are not supported.
Prerequisites
Procedure
1 Navigate to the vSAN cluster, and select a VM.
VMware, Inc. 34
4 Select VM. Select a time range for your query. vSAN displays performance charts for the VM,
including IOPS, throughput, and latency.
5 Select Virtual Disk. Select a time range for your query. vSAN displays performance charts
for the virtual disks, including IOPS, delayed normalized IOPS, virtual SCSI IOPS, virtual SCSI
throughput, and virtual SCSI latency. The virtual SCSI latency performance charts display a
highlighted area due to the IOPS limit enforcement.
6 (Optional) In the Virtual Disk, click New IOInsight Instance. For more information on IOInsight,
see Use IOInsight.
Use IOInsight
IOInsight allows you to select and view I/O performance metrics of virtual machines in a vSAN
cluster. By understanding the I/O characteristics of VMs, you can ensure better capacity planning
and performance tuning.
Procedure
1 Navigate to the vSAN cluster or host.
You can also access IOInsight from the VM. Select the VM and navigate to Monitor > vSAN >
Performance > Virtual Disks.
4 Select the IOInsight tab and click New Instance.
5 Select the required hosts or VMs that you want to monitor. You can also search for VMs.
6 Click Next.
7 Enter a name and select a duration.
8 Click Next and review the instance information.
9 Click Finish.
IOInsight instance monitors the selected VMs for the specified duration. However, you can
stop an instance before completion of the duration that you specified.
Note VMs monitored by IOInsight must not be vMotioned. vMotion stops the VMs from
being monitored and will result in an unsuccessful trace.
Results
vSAN displays performance charts for the VMs in the cluster, including IOPS, throughput, I/O size
distribution, I/O latency distribution, and so on.
VMware, Inc. 35
What to do next
You can view metrics for the IOInsight instance that you created.
View IOInsight Metrics

IOInsight performance metrics chart displays the metrics at the virtual disk level.
When IOInsight is running, vSAN collects and displays these metrics for selected VMs, for a set
duration. You can view the performance metrics for up to 90 days. The IOInsight instances are
automatically deleted after this period.
Procedure
1 Navigate to the vSAN cluster or host.
You can also access IOInsight from the VM. Select the VM and navigate to Monitor > vSAN >
Performance > Virtual Disks.
4 Select the IOInsight tab. You can organize the instances based on time or hosts.
5 To view the metrics of an instance, click and click View Metrics. You can optionally stop
a running instance before completing the specified duration.
You can rerun an instance, and rename or delete the existing instances.
Use I/O Trip Analyzer

You can use I/O trip analyzer to diagnose the virtual machine I/O latency issues. The latency
issues might be due to outstanding I/Os, network hardware issues, network congestions, or disk
slowness.
The trip analyzer allows you to get the breakdown of the latencies at each layer of the vSAN
stack. The topology diagram shows only the hosts with VM I/O traffic.
Note All the ESXi hosts and vCenter Server in the vSAN cluster must be running 7.0 Update 3 or
later.
Prerequisites
Turn on the vSAN performance service before you can run the test and view the latency issues.
Procedure
1 Navigate to the vSAN cluster, and select a VM.
3 Under vSAN, select I/O Trip Analyzer.
VMware, Inc. 36
4 Click RUN NEW TEST.
5 In the Run VM I/O Trip Analyzer Test, select the duration of the test.
6 Click RUN. The trip analyzer test data is persisted and is available only for 30 days.
Note vSAN does not support trip analyzer in the stretched cluster, two-node cluster, and
virtual disks in remote vSAN datastore.
7 Click VIEW RESULT to view the visualized I/O topology.
8 From the Virtual Disks drop-down, select the disk for which you want to view the I/O
topology. You can also view the performance details of the network and the disk groups.
Click the edge points of the topology to view the latency details.
Using vSAN Performance Diagnostics

You can use vSAN performance diagnostics to improve the performance of your vSAN cluster,
and resolve performance issues.
The vSAN performance diagnostics tool analyzes previously run benchmarks gathered from
the vSAN performance service. It can detect issues, suggest remediation steps, and provide
supporting performance graphs for further insight.
The vSAN performance service provides the data used to analyze vSAN performance
diagnostics. vSAN uses CEIP to send data to VMware for analysis.
Note Do not use vSAN performance diagnostics for general evaluation of performance on a
production vSAN cluster.
Prerequisites
n The vSAN performance service must be turned on.
n vCenter Server requires Internet access to download ISO images and patches.
n You must participate in the Customer Experience Improvement Program (CEIP).
Procedure
3 Under vSAN, select Performance Diagnostics.
4 Select a benchmark goal from the drop-down menu.
You can select a goal based on the performance improvement that you want to achieve, such
as maximum IOPS, maximum throughput, or minimum latency.
VMware, Inc. 37
5 Select a time range for your query.
The default time range is the most recent hour. You can increase the range to include the last
24 hours, or define a custom time range within the last 90 days. If you used the HCIbench
tool to run performance benchmark tests on the vSAN cluster, the time ranges of those tests
appear in the drop-down menu.
6 Click Show Results.
Results
When you click Show Results, vSAN transmits performance data to the vSphere backend
analytics server. After analyzing the data, the vSAN performance diagnostics tool displays a list
of issues that might have affected the benchmark performance for the chosen goal.
You can click to expand each issue to view more details about each issue, such as a list of
affected items. You also can click See More or Ask VMware to display a Knowledge Base article
that describes recommendations to address the issue and achieve your performance goal.
VMware, Inc. 38
Handling Failures and
Troubleshooting vSAN 5
If you encounter problems when using vSAN, you can use troubleshooting topics. The topics help
you understand the problem and offer you a workaround, when it is available.
n Uploading a vSAN Support Bundle
n Using Esxcli Commands with vSAN
n Using vsantop Command-Line Tool
n vSAN Configuration on an ESXi Host Might Fail
n Not Compliant Virtual Machine Objects Do Not Become Compliant Instantly
n vSAN Cluster Configuration Issues
n Handling Failures in vSAN
Uploading a vSAN Support Bundle

You can upload a vSAN support bundle so VMware service personnel can analyze the diagnostic
information.
VMware Technical Support routinely requests diagnostic information from your vSAN cluster
when a support request is addressed. The support bundle is an archive that contains diagnostic
information related to the environment, such as product specific logs, configuration files, and so
on.
The log files, collected and packaged into a zip file, include the following:
n vCenter support bundle
n Host support bundle
The host support bundle in the cluster includes the following:
["Userworld:HostAgent", "Userworld:FDM",
"System:VMKernel", "System:ntp", "Storage:base", "Network:tcpip",
"Network:dvs", "Network:base", "Logs:System", "Storage:VSANMinimal",
"Storage:VSANHealth", "System:BaseMinmal", "Storage:VSANTraces"]
VMware, Inc. 39
vSAN performs an automated upload of the support bundle, and does not allow you to review,
obfuscate, or otherwise edit the contents of your support data prior to it being sent to VMware.
vSAN connects to the FTP port 21 or HTTPS port 443 of the target server with the domain name
vmware.com, to automatically upload the support bundle.
Note Data collected in the support bundle may be considered sensitive. If your support data
contains regulated data, such as personal, health care, or financial data, you may want to avoid
uploading the support bundle.
Procedure
1 Right-click the vSAN cluster in the vSphere Client.
2 Choose menu vSAN > Upload support bundle...
3 Enter your service request ID and a description of your issue.
4 Click Upload.
Using Esxcli Commands with vSAN

Use Esxcli commands to obtain information about vSAN and to troubleshoot your vSAN
environment.
The following commands are available:
Command Description
esxcli vsan network list Verify which VMkernel adapters are used for vSAN communication.
esxcli vsan storage list List storage disks claimed by vSAN.
esxcli vsan cluster get Get vSAN cluster information.
esxcli vsan health Get vSAN cluster health status.
esxcli vsan debug Get vSAN cluster debug information.
The esxcli vsan debug commands can help you debug and troubleshoot the vSAN cluster,
especially when vCenter Server is not available.
Use: esxcli vsan debug {cmd} [cmd options]
Debug commands:
Command Description
esxcli vsan debug disk Debug vSAN physical disks.
esxcli vsan debug object Debug vSAN objects.
esxcli vsan debug resync Debug vSAN resyncing objects.
esxcli vsan debug controller Debug vSAN disk controllers.
esxcli vsan debug limit Debug vSAN limits.
esxcli vsan debug vmdk Debug vSAN VMDKs.
VMware, Inc. 40
Example esxcli vsan debug commands:
esxcli vsan debug disk summary get

Overall Health: green
Component Metadata Health: green
Memory Pools (heaps): green
Memory Pools (slabs): green
esxcli vsan debug disk list

UUID: 52e1d1fa-af0e-0c6c-f219-e5e1d224b469
Name: mpx.vmhba1:C0:T1:L0
SSD: False
Overall Health: green
Congestion Health:
State: green
Congestion Value: 0
Congestion Area: none
In Cmmds: true
In Vsi: true
Metadata Health: green
Operational Health: green
Space Health:
State: green
Capacity: 107365793792 bytes
Used: 1434451968 bytes
Reserved: 150994944 bytes
esxcli vsan debug object health summary get

Health Status Number Of Objects
------------------------------------------------ -----------------
reduced-availability-with-no-rebuild-delay-timer 0
reduced-availability-with-active-rebuild 0
inaccessible 0
data-move 0
healthy 1
nonavailability-related-incompliance 0
nonavailability-related-reconfig 0
reduced-availability-with-no-rebuild 0
esxcli vsan debug object list

Object UUID: 47cbdc58-e01c-9e33-dada-020010d5dfa3
Version: 5
Health: healthy
Owner:
Policy:
stripeWidth: 1
CSN: 1
spbmProfileName: vSAN Default Storage Policy
spbmProfileId: aa6d5a82-1c88-45da-85d3-3d74b91a5bad
forceProvisioning: 0
cacheReservation: 0
proportionalCapacity: [0, 100]
spbmProfileGenerationNumber: 0
VMware, Inc. 41
hostFailuresToTolerate: 1
Configuration:
RAID_1
Component: 47cbdc58-6928-333f-0c51-020010d5dfa3
Component State: ACTIVE, Address Space(B): 273804165120 (255.00GB),
Disk UUID: 52e95956-42cf-4d30-9cbe-763c616614d5, Disk Name: mpx.vmhba1..
Votes: 1, Capacity Used(B): 373293056 (0.35GB),
Physical Capacity Used(B): 369098752 (0.34GB), Host Name: sc-rdops...
Component: 47cbdc58-eebf-363f-cf2b-020010d5dfa3
Disk UUID: 52d11301-1720-9901-eb0a-157d68b3e4fc, Disk Name: mpx.vmh...
Physical Capacity Used(B): 369098752 (0.34GB), Host Name: sc-rdops-vm..
Witness: 47cbdc58-21d2-383f-e45a-020010d5dfa3
Disk UUID: 52bfd405-160b-96ba-cf42-09da8c2d7023, Disk Name: mpx.vmh...
Physical Capacity Used(B): 4194304 (0.00GB), Host Name: sc-rdops-vm...
Type: vmnamespace
Path: /vmfs/volumes/vsan:52134fafd48ad6d6-bf03cb6af0f21b8d/New Virtual Machine
Group UUID: 00000000-0000-0000-0000-000000000000
Directory Name: New Virtual Machine
esxcli vsan debug controller list

Device Name: vmhba1
Device Display Name: LSI Logic/Symbios Logic 53c1030 PCI-X Fusion-MPT Dual Ult..
Used By VSAN: true
PCI ID: 1000/0030/15ad/1976
Driver Name: mptspi
Driver Version: 4.23.01.00-10vmw
Max Supported Queue Depth: 127
esxcli vsan debug limit get

Component Limit Health: green
Max Components: 750
Free Components: 748
Disk Free Space Health: green
Lowest Free Disk Space: 99 %
Used Disk Space: 1807745024 bytes
Used Disk Space (GB): 1.68 GB
Total Disk Space: 107365793792 bytes
Total Disk Space (GB): 99.99 GB
Read Cache Free Reservation Health: green
VMware, Inc. 42
Reserved Read Cache Size: 0 bytes

Reserved Read Cache Size (GB): 0.00 GB
Total Read Cache Size: 0 bytes
Total Read Cache Size (GB): 0.00 GB
esxcli vsan debug vmdk list

Object: 50cbdc58-506f-c4c2-0bde-020010d5dfa3
Health: healthy
Type: vdisk
Path: /vmfs/volumes/vsan:52134fafd48ad6d6-bf03cb6af0f21b8d/47cbdc58-e01c-9e33-
dada-020010d5dfa3/New Virtual Machine.vmdk
Directory Name: N/A
esxcli vsan debug resync list

Object Component Bytes Left To Resync GB Left To Resync
---------------- --------------------- -------------------- -----------------
31cfdc58-e68d... Component:23d1dc58... 536870912 0.50
Using vsantop Command-Line Tool

Use the command-line tool - vsantop - that runs on ESXi hosts to view the real time vSAN
performance metrics. You can use this tool to monitor vSAN performance.
To display the different performance views and metrics in vsantop, enter the following
commands:
Command Description
^L Redraw screen
Space Update display
h or ? Help; show this text
q Quit
f/F Add or remove fields
o/O Change the order of displayed fields
s Set the delay in seconds between updates
# Set the number of instances to display
E Change the selected entity type
L Change the length of the field
l Limit display to specific node id
. Sort by column, same number twice to change sort order
vSAN Configuration on an ESXi Host Might Fail

In certain circumstances, the task of configuring vSAN on a particular host might fail.
VMware, Inc. 43
Problem
An ESXi host that joins a vSAN cluster fails to have vSAN configured.
Cause
If a host does not meet hardware requirements or experiences other problems, vSAN might fail
to configure the host. For example, insufficient memory on the host might prevent vSAN from
being configured.
Solution
1 Place the host that causes the failure in Maintenance Mode.
2 Move the host out of the vSAN cluster.
3 Resolve the problem that prevents the host to have vSAN configured.
4 Exit Maintenance Mode.
5 Move the host back into the vSAN cluster.
Not Compliant Virtual Machine Objects Do Not Become

Compliant Instantly
When you use the Check Compliance button, a virtual machine object does not change its
status from Not Compliant to Compliant even though vSAN resources have become available and
satisfy the virtual machine profile.
Problem
When you use force provisioning, you can provision a virtual machine object even when the
policy specified in the virtual machine profile cannot be satisfied with the resources available in
the vSAN cluster. The object is created, but remains in the non-compliant status.
vSAN is expected to bring the object into compliance when storage resources in the cluster
become available, for example, when you add a host. However, the object's status does not
change to compliant immediately after you add resources.
Cause
This occurs because vSAN regulates the pace of the reconfiguration to avoid overloading the
system. The amount of time it takes for compliance to be achieved depends on the number of
objects in the cluster, the I/O load on the cluster and the size of the object in question. In most
cases, compliance is achieved within a reasonable time.
vSAN Cluster Configuration Issues

After you change the vSAN configuration, vCenter Server performs validation checks for vSAN
configuration. Validation checks are also performed as a part of a host synchronization process.
If vCenter Server detects any configuration problems, it displays error messages.
VMware, Inc. 44
Problem
Error messages indicate that vCenter Server has detected a problem with vSAN configuration.
Solution
Use the following methods to fix vSAN configuration problems.
Table 5-1. vSAN Configuration Errors and Solutions
vSAN Configuration Error Solution
Host with the vSAN service enabled is not in the vCenter Add the host to the vSAN cluster.
cluster 1 Right-click the host, and select Move To.
2 Select the vSAN cluster and click OK.
Host is in a vSAN enabled cluster but does not have vSAN Verify whether vSAN network is properly configured and
service enabled enabled on the host. See vSAN Planning and Deployment.
vSAN network is not configured Configure vSAN network. See vSAN Planning and
Deployment.
Host cannot communicate with all other nodes in the Might be caused by network isolation. See the vSAN
vSAN enabled cluster Planning and Deployment documentation.
Found another host participating in the vSAN service Make sure that the vSAN cluster configuration is correct
which is not a member of this host's vCenter cluster. and all vSAN hosts are in the same subnet. See vSAN
Planning and Deployment.
Handling Failures in vSAN

vSAN handles failures of the storage devices, hosts and network in the cluster according to the
severity of the failure. You can diagnose problems in vSAN by observing the performance of the
vSAN datastore and network.
Failure Handling in vSAN

vSAN implements mechanisms for indicating failures and rebuilding unavailable data for data
protection.
Failure States of vSAN Components

In vSAN, components that have failed can be in absent or degraded state. According to the
component state, vSAN uses different approaches for recovering virtual machine data.
vSAN also provides alerts about the type of component failure. See Using the VMkernel
Observations for Creating Alarms and Using the vSAN Default Alarms.
vSAN supports two types of failure states for components:
VMware, Inc. 45
Table 5-2. Failure States of Components in vSAN

Component
Failure State Description Recovery Cause
Degraded A component is in degraded vSAN starts rebuilding n Failure of a flash caching

state if vSAN detects a the affected components device
permanent component failure immediately. n Magnetic or flash capacity
and assumes that the component device failure
is not going to recover to n Storage controller failure
working state.
Absent A component is in absent state vSAN starts rebuilding absent n Lost network connectivity
if vSAN detects a temporary components if they are not n Failure of a physical
component failure where the available within a certain network adapter
component might recover and time interval. By default, n ESXi host failure
restore its working state. vSAN starts rebuilding absent
n Unplugged flash caching
components after 60 minutes.
device
n Unplugged magnetic disk
or flash capacity device
Examine the Failure State of a Component

You can determine whether a component is in the absent or degraded failure state.
If a failure occurs in the cluster, vSAN marks the components for an object as absent or degraded
based on the failure severity.
Procedure
2 On the Monitor tab, click vSAN and select Virtual Objects.
The home directories and virtual disks of the virtual machines in the cluster appear.
3 Select the check box on one of the virtual objects and click View Placement Details to open
the Physical Placement dialog. You can view device information, such as name, identifier or
UUID, number of devices used for each virtual machine, and how they are mirrored across
hosts.
If a failure has occurred in the vSAN cluster, the Placement and Availability is equal to Absent
or Degraded.
Object States That Indicate Problems in vSAN

Examine the compliance status and the operational state of a virtual machine object to determine
how a failure in the cluster affects the virtual machine.
VMware, Inc. 46
Table 5-3. Object State
Object State Type Description
Compliance Status The compliance status of a virtual machine object indicates whether it
meets the requirements of the assigned VM storage policy.
Operational State The operational state of an object can be healthy or unhealthy. It

indicates the type and number of failures in the cluster.
An object is healthy if an intact replica is available and more than 50
percent of the object's votes are still available.
An object is unhealthy if an entire replica is not available or less than
50 percent of the object's votes are unavailable. For example, an object
might become unhealthy if a network failure occurs in the cluster and a
host becomes isolated.
To determine the overall influence of a failure on a virtual machine, examine the compliance
status and the operational state. If the operational state remains healthy although the object is
noncompliant, the virtual machine can continue using the vSAN datastore. If the operational state
is unhealthy, the virtual machine cannot use the datastore.
Examine the Health of an Object in vSAN

Use the vSphere Client to examine whether a virtual machine is healthy. A virtual machine is
considered as healthy when a replica of the VM object and more than 50 percent of the votes for
an object are available.
Procedure
2 On the Monitor tab, click vSAN and select Virtual Objects.
The home directories and virtual disks of the virtual machines in the cluster appear.
3 Select an object type in the Affected inventory objects area at the top of the page to display
information about each object, such as object state, storage policy, and vSAN UUID.
If the inventory object is Unhealthy, the vSphere Client indicates the reason for the unhealthy
state in brackets.
Examine the Compliance of a Virtual Machine in vSAN

Use the vSphere Client to examine whether a virtual machine object is compliant with the
assigned VM storage policy.
Procedure
1 Examine the compliance status of a virtual machine.
a Browse to the virtual machine in the vSphere Client navigator.
b On the Summary tab, examine the value of the VM Storage Policy Compliance property
under VM Storage Policies.
VMware, Inc. 47
2 Examine the compliance status of the objects of the virtual machine.
a Navigate to the vSAN cluster.
b On the Monitor tab, click vSAN and select Virtual Objects.
c Select an object type in the Affected inventory objects area at the top of the page to
display information about each object, such as object state, storage policy, and vSAN
UUID.
d Select the check box on one of the virtual objects and click View Placement Details to
open the Physical Placement dialog. You can view device information, such as name,
identifier or UUID, number of devices used for each virtual machine, and how they are
mirrored across hosts.
e On the Physical Placement dialog, check the Group components by host placement
check box to organize the objects by host and by disk.
Accessibility of Virtual Machines Upon a Failure in vSAN

If a virtual machine uses vSAN storage, its storage accessibility might change according to the
type of failure in the vSAN cluster.
Changes in the accessibility occur when the cluster experiences more failures than the policy for
a virtual machine object tolerates.
As a result from a failure in the vSAN cluster, a virtual machine object might become inaccessible.
An object is inaccessible if a full replica of the object is not available because the failure affects all
replicas, or when less than 50 percent of the object's votes are available.
According to the type of object that is inaccessible, virtual machines behave in the following
ways:
Table 5-4. Inaccessibility of Virtual Machine Objects
Object Type Virtual Machine State Virtual Machine Symptoms
VM Home Namespace n Inaccessible The virtual machine process might

n Orphaned if vCenter Server or the ESXi host crash and the virtual machine might
cannot access the .vmx file of the virtual be powered off.
machine.
VMDK Inaccessible The virtual machine remains powered

on but the I/O operations on the
VMDK are not being performed.
After a certain timeout passes, the
guest operating system ends the
operations.
Virtual machine inaccessibility is not a permanent state. After the underlying issue is resolved,
and a full replica and more than 50 percent of the object's votes are restored, the virtual machine
automatically becomes accessible again.
VMware, Inc. 48
Storage Device is Failing in a vSAN Cluster

vSAN monitors the performance of each storage device and proactively isolates unhealthy
devices. It detects gradual failure of a storage device and isolates the device before congestion
builds up within the affected host and the entire vSAN cluster.
If a disk experiences sustained high latencies or congestion, vSAN considers the device as a
dying disk, and evacuates data from the disk. vSAN handles the dying disk by evacuating or
rebuilding data. No user action is required, unless the cluster lacks resources or has inaccessible
objects.
Component Failure State and Accessibility

The vSAN components that reside on the magnetic disk or flash capacity device are marked as
absent.
Behavior of vSAN
vSAN responds to the storage device failure in the following ways.
Parameter Behavior
Alarms An alarm is generated from each host whenever an unhealthy device is diagnosed. A warning is issued
whenever a disk is suspected of being unhealthy.
Health check The Disk operation health check issues a warning for the dying disk.
Health status On the Disk Management page, the health status of the dying disk is listed as Unhealthy. When vSAN
completes evacuation of data, the health status is listed as DyingDiskEmpty.
Rebuilding data vSAN examines whether the hosts and the capacity devices can satisfy the requirements for space
and placement rules for the objects on the failed device or disk group. If such a host with capacity
is available, vSAN starts the recovery process immediately because the components are marked as
degraded.
If resources are available, vSAN automatically reprotects the data.
If vSAN detects a disk with a permanent error, it makes a limited number of attempts to revive
the disk by unmounting and mounting it.
Capacity Device Not Accessible in a vSAN Cluster

When a magnetic disk or flash capacity device fails, vSAN evaluates the accessibility of the
objects on the device and rebuilds them on another host if space is available and the Primary
level of failures to tolerate is set to 1 or more.

The vSAN components that reside on the magnetic disk or flash capacity device are marked as
degraded.
Behavior of vSAN
vSAN responds to the capacity device failure in the following ways.
VMware, Inc. 49
Parameter Behavior
Primary level of If the Primary level of failures to tolerate in the VM storage policy is equal to or greater than 1,
failures to tolerate the virtual machine objects are still accessible from another ESXi host in the cluster. If resources are
available, vSAN starts an automatic reprotection.
If the Primary level of failures to tolerate is set to 0, a virtual machine object is inaccessible if one of
the object's components resides on the failed capacity device.
Restore the virtual machine from a backup.
I/O operations vSAN stops all running I/O operations for 5-7 seconds until it re-evaluates whether an object is still
on the capacity available without the failed component.
device If vSAN determines that the object is available, all running I/O operations are resumed.
degraded.
If resources are available, an automatic reprotect will occur.
A Flash Caching Device Is Not Accessible in a vSAN Cluster

When a flash caching device fails, vSAN evaluates the accessibility of the objects on the disk
group that contains the cache device, and rebuilds them on another host if possible and the
Primary level of failures to tolerate is set to 1 or more.

Both cache device and capacity devices that reside in the disk group, for example, magnetic
disks, are marked as degraded. vSAN interprets the failure of a single flash caching device as a
failure of the entire disk group.
Behavior of vSAN
vSAN responds to the failure of a flash caching device in the following way:
Parameter Behavior
Primary level of If the Primary level of failures to tolerate in the VM storage policy is equal to or greater than 1,
failures to tolerate the virtual machine objects are still accessible from another ESXi host in the cluster. If resources are
available, vSAN starts an automatic reprotection.
If the Primary level of failures to tolerate is set to 0, a virtual machine object is inaccessible if one
of the object's components is on the failed disk group.
I/O operations on vSAN stops all running I/O operations for 5-7 seconds until it re-evaluates whether an object is still
the disk group available without the failed component.
If vSAN determines that the object is available, all running I/O operations are resumed.
degraded.
VMware, Inc. 50
A Host Is Not Responding in a vSAN Cluster

If a host stops responding because of a failure or reboot of the host, vSAN waits for the host to
recover before vSAN rebuilds the components on the host elsewhere in the cluster.

The vSAN components that reside on the host are marked as absent.
Behavior of vSAN
vSAN responds to the host failure in the following way:
Parameter Behavior
Primary level If the Primary level of failures to tolerate in the VM storage policy is equal to or greater than 1,
of failures to the virtual machine objects are still accessible from another ESXi host in the cluster. If resources are
tolerate available, vSAN starts an automatic reprotection.
If the Primary level of failures to tolerate is set to 0, a virtual machine object is inaccessible if the
object's components reside on the failed host.
the host available without the failed component.
Rebuilding data If the host does not rejoin the cluster within 60 minutes, vSAN examines whether some of the other
hosts in the cluster can satisfy the requirements for cache, space and placement rules for the objects
on the inaccessible host. If such a host is available, vSAN starts the recovery process.
If the host rejoins the cluster after 60 minutes and recovery has started, vSAN evaluates whether to
continue the recovery or stop it and resynchronize the original components.
Network Connectivity Is Lost in the vSAN Cluster

When the connectivity between the hosts in the cluster is lost, vSAN determines the active
partition and rebuilds the components from the isolated partition on the active partition if the
connectivity is not restored.

vSAN determines the partition where more than 50 percent of the votes of an object are
available. The components on the isolated hosts are marked as absent.
Behavior of vSAN
vSAN responds to a network failure in the following way:
VMware, Inc. 51
Parameter Behavior
object's components are on the isolated hosts.
the isolated hosts available without the failed component.
Rebuilding data If the host rejoins the cluster within 60 minutes, vSAN synchronizes the components on the host.
If the host does not rejoin the cluster within 60 minutes, vSAN examines whether some of the other
hosts in the cluster can satisfy the requirements for cache, space and placement rules for the objects
on the inaccessible host. If such a host is available, vSAN starts the recovery process.
If the host rejoins the cluster after 60 minutes and recovery has started, vSAN evaluates whether to
continue the recovery or stop it and resynchronize the original components.
A Storage Controller Fails in a vSAN Cluster

When a storage controller fails, vSAN evaluates the accessibility of the objects on the disk
groups that are attached to the controller and rebuilds them on another host.
Symptoms
If a host contains a single storage controller and multiple disk groups, and all devices in all disk
groups are failed, then you might assume that a failure in the common storage controller is the
root cause. Examine the VMkernel log messages to determine the nature of the fault.

When a storage controller fails, the components on the flash caching devices and capacity
devices in all disk groups that are connected to the controller are marked as degraded.
If a host contains multiple controllers, and only the devices that are attached to an individual
controller are inaccessible, then you might assume that this controller has failed.
Behavior of vSAN
vSAN responds to a storage controller failure in the following way:
Parameter Behavior
object's components reside on the disk groups that are connected to the storage controller.
degraded.
VMware, Inc. 52
Stretched Cluster Site Fails or Loses Network Connection

A vSAN stretched cluster manages failures that occur due to the loss of a network connection
between sites or the temporary loss of one site.
Stretched Cluster Failure Handling

In most cases, the stretched cluster continues to operate during a failure and automatically
recovers after the failure is resolved.
Table 5-5. How Stretched Cluster Handles Failures
Type of Failure Behavior
Network Connection Lost Between Active Sites If the network connection fails between the two active sites, the
witness host and the preferred site continue to service storage
operations, and keep data available. When the network connection
returns, the two active sites are resynchronized.
Secondary Site Fails or Loses Network If the secondary site goes offline or becomes isolated from the
Connection preferred site and the witness host, the witness host and the
preferred site continue to service storage operations, and keep
data available. When the secondary site returns to the cluster, the
two active sites are resynchronized.
Preferred Site Fails or Loses Network Connection If the preferred site goes offline or becomes isolated from the
secondary site and the witness host, the secondary site continues
storage operations if it remains connected to the witness host.
When the preferred site returns to the cluster, the two active sites
are resynchronized.
Witness Host Fails or Loses Network Connection If the witness host goes offline or becomes isolated from the
preferred site or the secondary site, objects become noncompliant
but data remains available. VMs that are currently running are not
affected.
Troubleshooting vSAN
Examine the performance and accessibility of virtual machines to diagnose problems in the vSAN
cluster.
Verify Drivers, Firmware, Storage I/O Controllers Against the VMware

Compatibility Guide
Use the vSAN Health Service to verify whether your hardware components, drivers, and firmware
are compatible with vSAN.
Using hardware components, drivers, and firmware that are not compatible with vSAN might
cause problems in the operation of the vSAN cluster and the virtual machines running on it.
The hardware compatibility health checks verify your hardware against the VMware Compatibility
Guide. For more information about using the vSAN health service, see Chapter 3 Monitoring
vSAN Health.
VMware, Inc. 53
Examine Health Warning of an Unidentified NVMe Device

Each PCI-e based storage I/O device in the HCL database has a unique identifier. This unique ID
allows the vSAN HCL check to locate an NVMe device in the database.
Problem
PCI ID of some NVMe devices in the HCL database is not unique. The identifier fails the vSAN
HCL check to locate the corresponding device in the database. vSAN health service cannot
differentiate the devices and can generate false alarms.
Cause
There can be multiple NVMe devices in HCL having the same PCI ID. This results in vSAN health
service unable to identify the NVMe device correctly.
Solution
2 On the Configure tab, click vSAN and select Disk Management.
3 Click EDIT UNIDENTIFIED NVME DEVICES. vSAN displays the list of unidentified NVMe
devices.
4 Select the device and then select an appropriate model from the drop-down.
Note In Monitor > vSAN > Skyline Health, verify that the vSAN HCL DB up-to-date health
check is set to green. Select Not listed here option if you are unable to find the device model
in the list.
In Skyline Health, the status of the NVME device can be identified health check is set to
green. However, the devices display the uncertified status in the NVMe device is VMware
certified health check.
5 Click Apply.
Examining Performance in a vSAN Cluster

Monitor the performance of virtual machines, hosts, and the vSAN datastore to identify potential
storage problems.
Monitor regularly the following performance indicators to identify faults in vSAN storage, for
example, by using the performance charts in the vSphere Client:
n Datastore. Rate of I/O operations on the aggregated datastore.
n Virtual Machine. I/O operations, memory and CPU usage, network throughput and bandwidth.
You can use the vSAN performance service to access detailed performance charts. For
information about using the performance service, see Chapter 4 Monitoring vSAN Performance.
For more information about using performance data in a vSAN cluster, see the vSAN
Troubleshooting Reference Manual.
VMware, Inc. 54
Network Misconfiguration Status in a vSAN Cluster

After you enable vSAN on a cluster, the datastore is not assembled correctly because of a
detected network misconfiguration.
Problem
After you enable vSAN on a cluster, on the Summary tab for the cluster the Network Status for
vSAN appears as Misconfiguration detected.
Cause
One or more members of the cluster cannot communicate because of either of the following
reasons:
n A host in the cluster does not have a VMkernel adapter for vSAN.
n The hosts cannot connect each other in the network.
Solution
Join the members of the cluster to the same network. See vSAN Planning and Deployment.
Virtual Machine Appears as Noncompliant, Inaccessible or Orphaned in vSAN

The state of a virtual machine that stores data on a vSAN datastore appears as noncompliant,
inaccessible or orphaned because of failures in the vSAN cluster.
Problem
A virtual machine on a vSAN datastore is in one of the following states that indicate a fault in the
vSAN cluster.
n The virtual machine is non-compliant and the compliance status of some of its object is
noncompliant. See Examine the Compliance of a Virtual Machine in vSAN.
n The virtual machine object is inaccessible or orphaned. See Examine the Failure State of a
Component.
If an object replica is still available on another host, vSAN forwards the I/O operations of the
virtual machine to the replica.
Cause
If the object of the virtual machine can no longer satisfy the requirement of the assigned VM
storage policy, vSAN considers it noncompliant. For example, a host might temporarily lose
connectivity. See Object States That Indicate Problems in vSAN.
If vSAN cannot locate a full replica or more than 50 percent of the votes for the object, the virtual
machine becomes inaccessible. If a vSAN detects that the .vmx file is not accessible because the
VM Home Namespace is corrupted, the virtual machine becomes orphaned. See Accessibility of
Virtual Machines Upon a Failure in vSAN.
VMware, Inc. 55
Solution
If the cluster contains enough resources, vSAN automatically recovers the corrupted objects if
the failure is permanent.
If the cluster does not have enough resources to rebuild the corrupted objects, extend the space
in the cluster. See Administering VMware vSAN.
Attempt to Create a Virtual Machine on vSAN Fails

When you try to deploy a virtual machine in a vSAN cluster, the operation fails with an error that
the virtual machine files cannot be created.
Problem
The operation for creating a virtual machine fails with an error status: Cannot complete file
creation operation.
Cause
The deployment of a virtual machine on vSAN might fail for several reasons.
n vSAN cannot allocate space for the virtual machine storage policies and virtual machine
objects. Such a failure might occur if the datastore does not have enough usable capacity, for
example, if a physical disk is temporarily disconnected from the host.
n The virtual machine has very large virtual disks and the hosts in the cluster cannot provide
storage for them based on the placement rules in the VM storage policy
For example, if the Primary level of failures to tolerate in the VM storage policy is set to
1, vSAN must store two replicas of a virtual disk in the cluster, each replica on a different
host. The datastore might have this space after aggregating the free space on all hosts in the
cluster. However, no two hosts can be available in the cluster, each providing enough space
to store a separate replica of the virtual disk.
vSAN does not move components between hosts or disks groups to free space for a new
replica, even though the cluster might contain enough space for provisioning the new virtual
machine.
Solution
u Verify the state of the capacity devices in the cluster.
a Navigate to the vSAN cluster.
b On the Monitor tab, click vSAN and select Physical Disks.
c Examine the capacity and health status of the devices on the hosts in the cluster.
Stretched Cluster Configuration Error When Adding a Host

Before adding new hosts to a stretched cluster, all current hosts must be connected. If a current
host is disconnected, the configuration of the new host is incomplete.
VMware, Inc. 56
Problem
After you add a host to a stretched cluster in which some hosts are disconnected, on the
Summary tab for the cluster the Configuration Status for vSAN appears as Unicast agent
unset on host.
Cause
When a new host joins a stretched cluster, vSAN must update the configuration on all hosts in
the cluster. If one or more hosts are disconnected from the vCenter Server, the update fails. The
new host successfully joins the cluster, but its configuration is incomplete.
Solution
Verify that all hosts are connected to vCenter Server, and click the link provided in the
Configuration Status message to update the configuration of the new host.
If you cannot rejoin the disconnected host, remove the disconnected host from the cluster, and
click the link provided in the Configuration Status message to update the configuration of the
new host.
Stretched Cluster Configuration Error When Using RVC to Add a Host

If you use the RVC tool to add a host to a stretched cluster, the configuration of the new host is
incomplete.
Problem
After you use the RVC tool to add a host to a stretched cluster, on the Summary tab for the
cluster the Configuration Status for vSAN appears as Unicast agent unset on host.
Cause
When a new host joins a stretched cluster, vSAN must update the configuration on all hosts in
the cluster. If you use the RVC tool to add the host, the update does not occur. The new host
successfully joins the cluster, but its configuration is incomplete.
Solution
Verify that all hosts are connected to vCenter Server, and click the link provided in the
Configuration Status message to update the configuration of the new host.
Cannot Add or Remove the Witness Host in a Stretched Cluster

Before adding or removing the witness host in a stretched cluster, all current hosts must be
connected. If a current host is disconnected, you cannot add or remove the witness host.
VMware, Inc. 57
Problem
When you add or remove a witness host in a stretched cluster in which some hosts are
disconnected, the operation fails with an error status: The operation is not allowed in
the current state. Not all hosts in the cluster are connected to Virtual
Center.
Cause
When the witness host joins or leaves a stretched cluster, vSAN must update the configuration
on all hosts in the cluster. If one or more hosts are disconnected from the vCenter Server, the
witness host cannot be added or removed.
Solution
Verify all hosts are connected to vCenter Server, and retry the operation. If you cannot rejoin
the disconnected host, remove the disconnected host from the cluster, and then you can add or
remove the witness host.
Disk Group Becomes Locked

In an encrypted vSAN cluster, when communication between a host and the KMS is lost, the disk
group can become locked if the host reboots.
Problem
vSAN locks a host's disk groups when the host reboots and it cannot get the KEK from the KMS.
The disks behave as if they are unmounted. Objects on the disks become inaccessible.
You can view a disk group's health status on the Disk Management page in the vSphere Client.
An Encryption health check warning notifies you that a disk is locked.
Cause
Hosts in an encrypted vSAN cluster do not store the KEK on disk. If a host reboots and cannot
get the KEK from the KMS, vSAN locks the host's disk groups.
Solution
To exit the locked state, you must restore communication with the KMS and reestablish the trust
relationship.
Replacing Existing Hardware Components

Under certain conditions, you must replace hardware components, drivers, firmware, and storage
I/O controllers in the vSAN cluster.
In vSAN, you should replace hardware devices when you encounter failures or if you must
upgrade your cluster.
VMware, Inc. 58
Replace a Flash Caching Device on a Host

You must replace a flash caching device if you detect a failure or when there is a disk group
upgrade. Removing the cache device removes the entire disk group from the vSAN cluster.
When you replace a flash caching device, the virtual machines on the disk group become
inaccessible and the components on the group are marked as degraded. See A Flash Caching
Device Is Not Accessible in a vSAN Cluster.
Prerequisites
n Verify that the storage controllers on the hosts are configured in passthrough mode and
support the hot-plug feature.
If the storage controllers are configured in RAID 0 mode, see the vendor documentation for
information about adding and removing devices.
n If you upgrade the flash caching device, verify the following requirements:
n If you upgrade the flash caching device, verify that the cluster contains enough space to
migrate the data from the disk group that is associated with the flash device.
n Place the host in maintenance mode.
Procedure
2 On the Configure tab, click Disk Management under vSAN.
3 Select the entire disk group that contains the flash caching device that you want to remove.
vSAN does not allow you to remove the cache disk. To remove the cache disk, you must
remove the entire disk group.
4 Click and click REMOVE.
5 In the Remove Disk Group dialog box, select any of the following data migration mode to
evacuate the data on the disks.
n Full data migration - Transfers all the data available on the host to other hosts in the
cluster.
n Ensure accessibility - Transfers data available on the host to the other hosts in the cluster
partially. During the data transfer, all virtual machines on the host remains accessible.
n No data migration - There is no data transfer from the host. At this time, some objects
might become inaccessible.
6 Click GO TO PRE-CHECK to find the impact on the cluster if the object is removed or placed
in maintenance mode.
7 Click REMOVE to remove the disk group.
VMware, Inc. 59
Results
vSAN removes the flash caching device along with the entire disk group from the cluster.
What to do next
1 Add a new device to the host.
The host automatically detects the device.
2 If the host is unable to detect the device, perform a device rescan.
Replace a Capacity Device

You must replace a flash capacity device or a magnetic disk if you detect a failure or when you
upgrade it. Before you physically remove the device from the host, you must manually delete the
device from vSAN.
When you unplug a capacity device without removing it from the vSAN cluster, the components
on the disk are marked as absent. If the capacity device fails, the components on the disk
are marked as degraded. When the number of failures of the object replica with the affected
components exceeds the FTT value, the virtual machines on the disk become inaccessible. See
Capacity Device Not Accessible in a vSAN Cluster.
Note If your vSAN cluster uses deduplication and compression, you must remove the entire disk
group from the cluster before you replace the device.
You can also watch the video about how to replace a failed capacity device in vSAN.
(Replacing a Failed Drive in vSAN)
Prerequisites
n Verify that the storage controllers on the hosts are configured in passthrough mode and
support the hot-plug feature.
n If you upgrade the capacity device, verify the following requirements:
n Verify that the cluster contains enough space to migrate the data from the capacity
device.
n Place the host in maintenance mode.
Procedure
2 On the Configure tab, click Disk Management under vSAN.
VMware, Inc. 60
3 Select the flash capacity device or magnetic disk, and click REMOVE DISK.
Note You cannot remove a capacity device from the cluster with enabled deduplication and
compression. You must remove the entire disk group. If you want to remove a disk group
from a vSAN cluster with deduplication and compression enabled, see "Adding or Removing
Disks with Deduplication and Compression Enabled" in Administering VMware vSAN.
4 In the Remove Disk dialog box, select any of the following data migration mode to evacuate
the data on the disks.
n Full data migration - Transfers all the data available on the host to other hosts in the
cluster.
n Ensure accessibility - Transfers data available on the host to the other hosts in the cluster
partially. During the data transfer, all virtual machines on the host remains accessible.
n No data migration - There is no data transfer from the host. At this time, some objects
can become inaccessible.
5 Click GO TO PRE-CHECK to find the impact on the cluster if the object is removed or placed
in maintenance mode.
6 Click REMOVE to remove the capacity device.
What to do next
Remove a Device from a Host by Using an ESXCLI Command

If you detect a failed storage device or if you upgrade a device, you can manually remove it from
a host by using an ESXCLI command.
If you remove a flash caching device, vSAN deletes the disk group that is associated with the
flash device and all its member devices.
Prerequisites
Verify that the storage controllers on the hosts are configured in passthrough mode and support
the hot-plug feature.
Procedure
1 Open an SSH connection to the ESXi host.
VMware, Inc. 61
2 To identify the device ID of the failed device, run this command and learn the device ID from
the output.
esxcli vsan storage list
3 To remove the device from vSAN, run this command.
esxcli vsan storage remove -d device_id
What to do next
VMware, Inc. 62
Shutting Down and Restarting the
vSAN Cluster 6
You can shut down the entire vSAN cluster to perform maintenance or troubleshooting.
Use the Shutdown Cluster wizard to shutdown the vSAN cluster. The wizard performs the
necessary steps and alerts you when it requires user action. You also can manually shut down
the cluster, if necessary.
Note When you shut down a stretched cluster, the witness host remains active.
n Shut Down the vSAN Cluster Using the Shutdown Cluster Wizard
n Restart the vSAN Cluster
n Manually Shut Down and Restart the vSAN Cluster
VMware, Inc. 63
Shut Down the vSAN Cluster Using the Shutdown Cluster

Wizard
Use the Shutdown cluster wizard to gracefully shut down the vSAN cluster for maintenance or
troubleshooting. The Shutdown Cluster Wizard is available with vSAN 7.0 Update 3 and later
releases.
Note If you have a vSphere with Tanzu environment, you must follow the specified order when
shutting down or starting up the components. For more information, see "Shutdown and Startup
of VMware Cloud Foundation" in the VMware Cloud Foundation Operations Guide.
Procedure
1 Prepare the vSAN cluster for shutdown.
a Check the vSAN health service to confirm that the cluster is healthy.
b Power off all virtual machines (VMs) stored in the vSAN cluster, except for vCenter Server
VMs, vCLS VMs and file service VMs. If vCenter Server is hosted in the vSAN cluster, do
not power off the vCenter Server VM.
c If this is an HCI Mesh server cluster, power off all client VMs stored on the cluster. If the
client cluster's vCenter Server VM is stored in this cluster, either migrate or power off the
VM. Once this server cluster is shutdown, it's shared datastore is inaccessible to clients.
d Verify that all resynchronization tasks are complete.
Click the Monitor tab and select vSAN > Resyncing Objects.
Note If any member hosts are in lockdown mode, add the host's root account to the security
profile Exception User list. For more information, see Lockdown Mode in vSphere Security.
2 Right-click the vSAN cluster in the vSphere Client, and select menu Shutdown cluster.
You also can click Shutdown Cluster on the vSAN Services page.
3 On the Shutdown cluster wizard, verify that the Shutdown pre-checks are green checks.
Resolve any issues that are red exclamations. Click Next.
If vCenter Server appliance is deployed on the vSAN cluster, the Shutdown wizard displays
the vCenter Server notice. Note the IP address of the orchestration host, in case you need it
during the cluster restart. Click Next.
4 Enter a reason for performing the shutdown, and click Shutdown.
The vSAN Services page changes to display information about the shutdown process.
5 Monitor the shutdown process.
vSAN performs the steps to shutdown the cluster, powers off the system VMs, and powers
off the hosts.
VMware, Inc. 64
Restart the vSAN Cluster

You can restart a vSAN cluster that is shut down for maintenance or troubleshooting.
Procedure
1 Power on the cluster hosts.
If the vCenter Server is hosted on the vSAN cluster, wait for vCenter Server to restart.
2 Right-click the vSAN cluster in the vSphere Client, and select menu Restart cluster.
You also can click Restart Cluster on the vSAN Services page.
3 On the Restart Cluster dialog, click Restart.
The vSAN Services page changes to display information about the restart process.
4 After the cluster has restarted, check the vSAN health service and resolve any outstanding
issues.
Manually Shut Down and Restart the vSAN Cluster

You can manually shut down the entire vSAN cluster to perform maintenance or troubleshooting.
Use the Shutdown Cluster wizard unless your workflow requires a manual shut down. When you
manually shut down the vSAN cluster, do not disable vSAN on the cluster.
Note If you have a vSphere with Tanzu environment, you must follow the specified order when
shutting down or starting up the components. For more information, see "Shutdown and Startup
of VMware Cloud Foundation" in the VMware Cloud Foundation Operations Guide.
Procedure
1 Shut down the vSAN cluster.
a Check the vSAN health service to confirm that the cluster is healthy.
b Power off all virtual machines (VMs) running in the vSAN cluster, if vCenter Server is not
hosted on the cluster. If vCenter Server is hosted in the vSAN cluster, do not power off
the vCenter Server VM or service VMs (such as DNS, Active Directory) used by vCenter
Server. If file service is enabled in the vSAN cluster, do not power off "vSAN File Service
Node (x)" VM.
c Click the Configure tab and turn off HA. As a result, the cluster does not register host
shutdowns as failures.
For vSphere 7.0 U1 and later, enable vCLS retreat mode. For more information, see the
VMware knowledge base article at https://kb.vmware.com/s/article/80472.
d Verify that all resynchronization tasks are complete.
Click the Monitor tab and select vSAN > Resyncing Objects.
VMware, Inc. 65
e If vCenter Server is hosted on the vSAN cluster, power off the vCenter Server VM.
Make a note of the host that runs the vCenter Server VM. It is the host where you must
restart the vCenter Server VM.
f Disable cluster member updates from vCenter Server by running the following command
on the ESXi hosts in the cluster. Ensure that you run the following command on all the
hosts.
esxcfg-advcfg -s 1 /VSAN/IgnoreClusterMemberListUpdates
g Log in to any host in the cluster other than the witness host.
h Run the following command only on that host. If you run the command on multiple hosts
concurrently, it may cause a race condition causing unexpected results.
python /usr/lib/vmware/vsan/bin/reboot_helper.py prepare
The command returns and prints the following:
Cluster preparation is done.
Note
n The cluster is fully partitioned after the successful completion of the command.
n If you encounter an error, resolve the issue based on the error message and try
enabling vCLS retreat mode again.
n If there are unhealthy or disconnected hosts in the cluster, remove the hosts and retry
the command.
i Place all the hosts into maintenance mode with No Action. If the vCenter Server is
powered off, use the following command to place the ESXi hosts into maintenance mode
with No Action.
esxcli system maintenanceMode set -e true -m noAction
Perform this step on all the hosts.

To avoid the risk of data unavailability while using No Action at the same time on multiple
hosts, followed by a reboot of multiple hosts, see the VMware knowledge base article
at https://kb.vmware.com/s/article/60424. To perform simultaneous reboot of all hosts
in the cluster using a built-in tool, see the VMware knowledge base article at https://
kb.vmware.com/s/article/70650.
j After all hosts have successfully entered maintenance mode, perform any necessary
maintenance tasks and power off the hosts.
VMware, Inc. 66
2 Restart the vSAN cluster.
a Power on the ESXi hosts.
Power on the physical box where ESXi is installed. The ESXi host starts, locates the VMs,
and functions normally.
If any hosts fail to restart, you must manually recover the hosts or move the bad hosts
out of the vSAN cluster.
b When all the hosts are back after powering on, exit all hosts from maintenance mode. If
the vCenter Server is powered off, use the following command on the ESXi hosts to exit
maintenance mode.
esxcli system maintenanceMode set -e false
Perform this step on all the hosts.
c Log in to one of the hosts in the cluster other than the witness host.
d Run the following command only on that host. If you run the command on multiple hosts
concurrently, it may cause a race condition causing unexpected results.
python /usr/lib/vmware/vsan/bin/reboot_helper.py recover
The command returns and prints the following:
Cluster reboot/power-on is completed successfully!
e Verify that all the hosts are available in the cluster by running the following command on
each host.
esxcli vsan cluster get
f Enable cluster member updates from vCenter Server by running the following command
on the ESXi hosts in the cluster. Ensure that you run the following command on all the
hosts.
esxcfg-advcfg -s 0 /VSAN/IgnoreClusterMemberListUpdates
g Restart the vCenter Server VM if it is powered off. Wait for the vCenter Server VM to be
powered up and running. To disable vCLS retreat mode, see the VMware knowledge base
article at https://kb.vmware.com/s/article/80472.
h Verify again that all the hosts are participating in the vSAN cluster by running the
following command on each host.
esxcli vsan cluster get
i Restart the remaining VMs through vCenter Server.
VMware, Inc. 67
j Check the vSAN health service and resolve any outstanding issues.
k (Optional) If the vSAN cluster has vSphere Availability enabled, you must manually restart
vSphere Availability to avoid the following error: Cannot find vSphere HA master
agent.
To manually restart vSphere Availability, select the vSAN cluster and navigate to:
1 Configure > Services > vSphere Availability > EDIT > Disable vSphere HA
2 Configure > Services > vSphere Availability > EDIT > Enable vSphere HA
3 If there are unhealthy or disconnected hosts in the cluster, recover or remove the hosts from
the vSAN cluster. Retry the above commands only after the vSAN health service shows all
available hosts in the green state.
If you have a three-node vSAN cluster, the command reboot_helper.py recover cannot
work in a one host failure situation. As an administrator, do the following:
a Temporarily remove the failure host information from the unicast agent list.
b Add the host after running the following command.
reboot_helper.py recover
Following are the commands to remove and add the host to a vSAN cluster:
#esxcli vsan cluster unicastagent remove -a <IP Address> -t node -u <NodeUuid>
#esxcli vsan cluster unicastagent add -t node -u <NodeUuid> -U true -a <IP Address> -p
12321
VMware, Inc. 68

Vsan 703 Monitoring Troubleshooting Guide

Uploaded by

Copyright:

Available Formats

Vsan 703 Monitoring Troubleshooting Guide

Uploaded by

Document Information

Original Description:

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

Vsan 703 Monitoring Troubleshooting Guide

Uploaded by

Copyright:

Available Formats

vSAN Monitoring and

About vSAN Monitoring and Troubleshooting 5

2 Monitoring the vSAN Cluster 8

3 Monitoring vSAN Health 24

4 Monitoring vSAN Performance 29

View IOInsight Metrics 36

5 Handling Failures and Troubleshooting vSAN 39

6 Shutting Down and Restarting the vSAN Cluster 63

06 OCT 2020 Initial release.

This chapter includes the following topics:

n Monitor vSAN Capacity

n Monitor Physical Devices

n Monitor Devices that Participate in vSAN Datastores

n Monitor Virtual Objects in the vSAN Cluster

n Monitor Container Volumes in the vSAN Cluster

n About Reserved Capacity

n About vSAN Cluster Resynchronization

n About vSAN Cluster Rebalancing

n Using the vSAN Default Alarms

n Using the VMkernel Observations for Creating Alarms

Monitor vSAN Capacity

1 Navigate to the vSAN cluster.

2 Click the Monitor tab.

3 Under vSAN, click Capacity to view the vSAN capacity information.

Total space Total physical space in the cluster.

Free space Total free space in the cluster.

Used space Total written physical space in the cluster.

Actually written Actually used capacity. This capacity is displayed when

Following are the different usage categories available:

VM usage Displays the following:

System usage Displays the following:

n Operations reserve - Reserved space in the cluster for internal operations.

Monitor Physical Devices

1 Navigate to the vSAN cluster.

2 Click the Configure tab.

Monitor Devices that Participate in vSAN Datastores

2 Select the vSAN datastore.

3 Click the Configure tab.

4 Display information about local devices.

Monitor Virtual Objects in the vSAN Cluster

1 Navigate to the vSAN cluster.

2 Click the Monitor tab.

Monitor Container Volumes in the vSAN Cluster

1 Navigate to the vSAN cluster.

2 Click the Monitor tab.

4 Click to view the following:

About Reserved Capacity

These values are represented as thresholds in the Capacity Monitor page:

Capacity Reservation Considerations

Configure Reserved Capacity

Verify that the vSAN cluster:

n Is not configured as a stretched cluster or ROBO cluster.

n Has no fault domains and nested fault domains created.

n Has a minimum of four hosts.

1 Navigate to the vSAN cluster.

2 Click the Configure tab.

3 Under vSAN, select Services.

4 Click to edit the Reservations and Alerts.