vSAN Skyline Health Check Information

Products

• VMware vSAN

Issue/Introduction

This article provides an overview and serves as a homepage for the Knowledge Base articles for the VMware vSAN Skyline Health Checks.

Environment

VMware vSAN (All Versions)

Resolution

Table of contents

• Capacity Utilization
• Cluster
• Data
• Encryption
• File Service
• Hardware Compatibility
• Hyperconverged Cluster Configuration Compliance
• Network
• Online Health
• Performance Service
• Physical Disk
• Proactive Tests
• Stretched Cluster
• vSAN Build Recommendation
• vSAN iSCSI Target Service

Capacity Utilization

• vSAN Health Service - Capacity utilization - Disk space
• vSAN Health Service - Capacity utilization - Read cache reservations
• vSAN Health Service - Limits Health – After one additional host failure
• vSAN Health Service - Limits - Host component

Cluster

• vSAN Health Service - Cluster health – CLOMD liveness check
• vSAN Health Service - Cluster health - Advanced vSAN configuration in sync
• vSAN Health Service - Cluster health - Disk format version compatibility check
• vSAN Health Service - Cluster - Disk format version
• vSAN Health Service - Cluster - Software version compatibility
• vSAN Health Service - Cluster health - vSAN disk balance
• vSAN Host Maintenance Mode is in sync with vSAN Node Decommission State
• vSAN Health Service - Cluster Health - Resynchronization Operations Throttling Check
• vSAN Health Service - Cluster Health - Time Synchronization Across Hosts and VC
• vSAN Health Service - Cluster Health - vSAN Cluster Configuration Consistency
• vSAN Health Service - Cluster Health - vSphere and vSAN Cluster Members Match vSAN
• vSAN Health Service - Cluster health – vCenter state is authoritative

• vSAN Health Service - Cluster Health - vSAN Direct Homogenous Disk Claiming (7.0 U2 and higher)
• vSAN Health Service - Cluster health - vSAN Managed disk claim (8.0 and higher)
• vSAN Health Service - vSphere Lifecycle Manager (vLCM) configuration (8.0 and higher)
• vSAN Health Service - Cluster health - vSAN optimal datastore default policy configuration (8.0 U1 and higher)
• vSAN Health Service - Cluster - ESA prescriptive disk claim (8.0 U2 and higher)

Data

• vSAN Health Service - Data health – vSAN object health
• Skyline Health - vSAN object format health (7.0 U1 and higher)

Encryption

• vSAN Health Service - Encryption - CPU AES-NI Host Enablement Check
• vSAN Health Service - Encryption - Key Management Servers Connection Check
• Data-in-transit encryption - Configuration check for vSAN (7.0 U1 and higher)

File Service

• vSAN Health Service - File Service - File Server Health (7.0 and higher)
• vSAN Health Service - File Service - Infrastructure health (7.0 and higher)
• vSAN Skyline Health -- File Service - Share Health (7.0 and higher)

Hardware Compatibility

• vSAN Health Service - HCL Health - Host issues retrieving hardware info
  • “vsanvpd” service is running on all hosts in vSAN Cluster. To collect the h/w info for the vSAN HCL compatibility to display it in vSAN HCL GUI. 
• vSAN Health Service - vSAN HCL health - Controller driver
• vSAN Health Service - vSAN HCL health - Controller release support
• vSAN Health Service - vSAN HCL health – SCSI controller on vSAN HCL
• vSAN Health Service - vSAN HCL health – vSAN HCL DB up-to-date
• vSAN Health Service - Hardware compatibility - vSAN HCL DB Auto Update
• vSAN Health Service - Hardware Compatibility - Controller Firmware Check
• vSAN Health Service - Hardware Compatibility - Disk Group Type Check
• vSAN Health Service - vSAN HCL Health – NVMe device can be identified (7.0 U3 and higher)
• vSAN Health Service - vSAN HCL Health – NVMe device is VMware certified (7.0 U3 and higher)
• vSAN Health Service - Hardware compatibility - Physical NIC link speed is satisfied to the minimum requirements (8.0 and higher)
• vSAN Skyline Health - Network(RDMA NIC: RoCE v2) is certified for ESXi (8.0 U3 and higher)
• vSAN Skyline Health - Network(RDMA NIC: RoCE v2) is vSAN certified (8.0 U3 and higher)
• vSAN health - Network(RDMA NIC: RoCE v2) driver/firmware is vSAN certified (8.0 U3 and higher)

Hyperconverged Cluster Configuration Compliance

• vSAN -- vSAN Healthcheck -- Host compliance check for hyperconverged Cluster configuration

Network

• vSAN Health Service - Network health - All hosts have a vSAN vmknic configured
• vSAN Health Service - Network health - Hosts disconnected from vCenter
• vSAN Health Service - Network health - Hosts small ping test (connectivity check) and hosts large ping test (MTU check)
• vSAN Health Service - Network health - Hosts with connectivity issues
• vSAN Health Service - Network health - Unexpected vSAN cluster members
• vSAN Health Service - Network health - vSAN Cluster partition
• vSAN Health Service - Network health – Hosts with vSAN disabled
• vSAN Health Service - Network Configuration - vMotion: Basic Connectivity Check
• vSAN Health Service - Network Configuration - vMotion: MTU Check
• vSAN Health Service - Network Health - Network Latency Check
• vSAN Health Service - Network – Server Cluster Partition (7.0 U1 and higher)
• vSAN Health Service - vSAN Network Health – Hosts with LACP issues (7.0 U3 and higher)
• vSAN Health Service - vSAN Network Health – Hosts with duplicate IP addresses (7.0 U3 and higher)
• vSAN Health Service - vSAN Network Health – Hosts with pNIC TSO issues (7.0 U3 and higher)
• vSAN Health - Cluster - Remote vCenter network connectivity (8.0 U1 and higher)
• vSAN Health - Network - vSAN: Advanced (https) connectivity check (8.0 U2 and higher)

Online Health

• vSAN Health Service - Online Health - CEIP Check
• vSAN Health Service - Online Health - Internet Connectivity Check
• vSAN Health Service - Online Health - Controller Utility Is Installed on Host
• vSAN Health Service - Online Health - Customer advisory for HPE Smart Array
• vSAN Health Service - Online Health - vSAN Advanced Configuration Check for vSphere 8.0 P02 and newer release
• vSAN Health Service - Online Health - vSAN management server system resource check
• vSAN Health Service - Online Health – HPE SAS Solid State Drives
• vSAN Health Service - Online Health – vSAN v1 disk in use
• vSAN Health Service - vSAN Storage Policy Compliance up-to-date
• vSAN Health Service – Online Health - VM storage policy is not-recommended
• vSAN Health Service – Online Health – Multiple VMs share the same VM home namespace
• vSAN Health Service – Online Health – Physical network adapter link speed consistency check
• vSAN Health Service – Online Health – Proper vSAN network traffic shaping policy is configured
• vSAN Health Service – Online Health – vCenter Server up to date check
• vSAN Health Service/Skyline Health - Online Health - Audit CEIP Collected Data
• vSAN high LLOG consumption leading to LogCongestion
• Best practices when using vSAN and non-vSAN disks with the same storage controller
• Creating vSAN clusters up to 64 nodes
• End of General Support for vSphere 6.0
• RWM Volume become inaccessible if Node Daemonset Pod which helped mount the volume is restarted.
• Recommended settings for RAID0 logical volumes on certain LSI based RAID vSAN
• Release (8.0U2 and 8.0U2b) Available to Prevent Host Failure / Inaccessible Data Risk due to Rare Snapshot-related Condition on vSAN ESA (Version 8.0, 8.0U1, 8.0U1c)
• Storing ESXi coredump and scratch partitions in vSAN
• Thick-provisioned VMs on vSAN detected on vSAN-health check
• Understanding vSAN Datastore Encryption vs. VMcrypt Encryption
• Upgrading vSAN Witness from 7.0 Update 2 fails with "New ESXi version requires a minimum of 2 processor cores."
• Urgent Patch (8.0U1c) Available to Prevent Inaccessible Data Risk for VMs on vSAN ESA (Version 8.0, 8.0 P01, 8.0 U1, 8.0U1a (EP1))
• Using small magnetic disks for vSAN might result in VM failures
  • small disks below 400 GB will not work properly in vSAN cluster ands may cause VM outage
• Virtual Machines running on VMware vSAN 7.0 U1 / 7.0 U1 P02 report in-guest data consistency following a concurrent maintenance activity and storage policy change.
• Volumes could be missing from CNS DB due to corrupted metadata in all vSphere/ESX 6.7 versions prior to 6.7 P05 and all vSphere/ESX 7.0 versions prior to 7.0 U2 MP1

Performance Service

• vSAN Health Service - Performance Service - Performance data collection check
• vSAN Health Service - Performance Service - Stats DB object check
• vSAN Health Service - Performance Service - Stats DB object conflicts check
• vSAN Health Service - Performance Service - Stats master election check
• vSAN Health Service - performance service - All hosts contributing stats check
• vSAN Health Service - Performance Service - Status Check
• vSAN Health Service - Performance service - Network diagnostic mode (7.0 and higher)

Physical Disk

• vSAN Health Service - Physical Disk Health - Physical disk health retrieval issue
  • “vsanmgmtd and vsandevicemonitord” service is running on all hosts in vSAN Cluster to query and display the h/w health of disks.
• vSAN Health Service - Physical disk health - Disk capacity
• vSAN Health Service - Physical disk health - Overall disk health
• vSAN Health Service - Physical disk health – Component metadata health
• vSAN Health Service - Physical disk health – Congestion
• vSAN Health Service - Physical disk health – Memory pools
• vSAN Health Service - Physical disk - Component limit
• vSAN Health Service - Physical Disk Health - Vendor Reported Drive Health (8.0 U3 and higher)

Proactive Tests

• vSAN -- Proactive Tests -- "VM creation test" ( = Virtual Machine Creation Test )
• vSAN Health Service - Network performance test

Stretched Cluster

• vSAN Health Service - Invalid preferred fault domain on witness host
• vSAN Health Service - Invalid unicast agent test
• vSAN Health Service - No disk claimed on witness host
• vSAN Health Service - Preferred fault domain unset
• vSAN Health Service - Unexpected number of fault domains
• vSAN Health Service - Unicast agent configuration inconsistent
• vSAN Health Service - Unicast agent not configured
• vSAN Health Service - Witness host fault domain misconfigured
• vSAN Health Service - Witness host not found
• vSAN Health Service - Witness host within vCenter cluster
• vSAN Health Service - Stretched cluster - Site latency

• vSAN Health Service - Stretched cluster - Witness appliance upgrade to vSphere 7.0 or higher with caution (7.0 and higher)
• vSAN Health Service - Stretched cluster – Shared witness per cluster component limit scaled down (7.0 U1 and higher)
• vSAN Stretched cluster - Shared witness cluster number of data hosts exceed (7.0 U1 and higher)
• vSAN Health Service - Stretched cluster - Witness node is managed by vLCM (8.0 U2 and higher)

vSAN Build Recommendation

• vSAN Health Service - vSphere Update Manager - vSAN build recommendation
• vSAN Health Service - vSphere Update Manager - vSAN build recommendation engine health
• vSAN Health Service - vSAN Build Recommendation - vSAN release catalog up-to-date

vSAN iSCSI Target Service

• vSAN Health Service - vSAN iSCSI target service - Home object
• vSAN Health Service - vSAN iSCSI target service – Network configuration
• vSAN Health Service - vSAN iSCSI target service – Service runtime status
• vSAN Health - iSCSI Target Service - LUN Runtime Health (8.0 U1 and higher)

 

Additional Information

For more information about collecting VMware vSAN logs, see How to collect vSAN support logs and upload to VMware by Broadcom

• About the vSAN Health Service 7.x
• About the vSAN Skyline Health 8.x
• Best practices when using vSAN and non-vSAN disks with the same storage controller
• Deployment guidelines for running VMware vSAN and VMware vSphere VMFS datastores on a Dell H730 controller with the lsi_mr3 driver

• How to invoke the HostStartUpPrecheck task if it timed out (7.0 U3 and higher)
• Shutdown all VMs during vSAN cluster shutdown in vSphere 7.0 U3 (7.0 U3 and higher)
• vSAN Performance Graphs in the vSphere Web Client Part 1
• vSAN Performance Graphs in the vSphere Web Client Part 2.
• Performance Graphs in the vSphere Web Client Part 3 (8.0 U1 and higher)
• vSAN Performance Top Contributors (7.0 U2 and higher)
• Inconsistent thresholds between vSphere alarm Datastore usage on disk and vSAN health check Storage space (7.0 U2 and higher)
• vLCM Upgrade Precheck - vSAN Health - vSAN Advanced Configuration Check for Urgent vSAN ESA Patch (8.0 U2 and higher)
• vSAN host extended configuration status
• Using small magnetic disks for vSAN might result in VM failures
  • small disks below 400 GB will not work properly in vSAN cluster ands may cause VM outage
• Upgrading vSAN Witness from 7.0 Update 2 fails with New ESXi version requires a minimum of 2 processor cores. (7.0 U3 and higher)
• vSAN firmware version recommendation (testID:com.vmware.vsan.health.test.hcl.fwrecommendation)
• vSAN firmware provider health (com.vmware.vsan.health.test.hcl.firmwareproviderhealth)<== Deprecated since from 8.0