Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
This article explains the Network health - Hosts with connectivity issues check in the vSAN Health Service and provides details on why it might report an error.
Q: What does the Network Health - Hosts with connectivity issues check do? This check refers to situations where the vCenter Server lists the ESXi host as connected, but all of vSAN API calls from the vCenter Server to the ESXi host affected are failing. This situation should be extremely rare, but in case it happens, it leads to similar issues as the Host disconnected from vCenter situation. Q: What does it mean when it is in an error state? If this health check highlights that an ESXi host has connectivity issues, vCenter Server does not know its state. The host may be up and may be actively participating in the vSAN cluster, serving data, and being healthy and performing its storage functions as part of the vSAN cluster.However, it could also mean that either the vSAN management daemon on the ESXi host may be down and unavailable. The vCenter Server, and hence the vSAN Health check, cannot fully assess the situation as long the host is disconnected. Q: How does one troubleshoot and fix the error state? You could first check the management network between vCenter and host and make sure it's fine. If the problem is still there, you could connect to the host via SSH and check the vSAN management daemon status with the command "/etc/init.d/vsanmgmtd status" and restart it by "/etc/init.d/vsanmgmtd restart".
For more information on collecting VMware vSAN logs, seeL Collecting vSAN support logs and uploading to VMware (2072796).Also, see:VMware vSAN Diagnostics and Troubleshooting Reference ManualVMware vSAN Design and Sizing GuideSAN Health Service - Cluster Health - vSAN Health Service up-do-datevSAN Health Service - Cluster Health - Advanced vSAN configuration in syncvSAN Health Service - Network Health - Hosts disconnected from vCenter ServervSAN Health Service - Network Health - Unexpected vSAN cluster membersvSAN Health Service - Network Health - vSAN Cluster PartitionvSAN Health Service - Network Health – Hosts with vSAN disabledvSAN Health Service - Network Health - All hosts have a vSAN vmknic configuredvSAN Health Service - Network Health - All hosts have matching subnets vSAN Health Service - Network Health - All hosts have matching multicast settingsvSAN Health Service - Network Health - Hosts small ping test (connectivity check) and Hosts large ping test (MTU check)vSAN Health Service - Network Health – Multicast assessment based on other checksvSAN Health Service - Data Health – vSAN Object HealthvSAN Health Service - Physical Disk Health - Metadata HealthvSAN Health Service - Physical Disk Health - Overall Disk HealthvSAN Health Service - Limits Health – Current Cluster SituationvSAN Health Service - Limits Health – After one additional host failurevSAN Health Service - Physical Disk Health - Disk CapacityvSAN Health Service – Physical Disk Health – Software State HealthvSAN Health Service – Physical Disk Health – Component Metadata HealthvSAN Health Service - Physical Disk Health – CongestionvSAN Health Service - Physical Disk Health – Memory poolsvSAN Health Service - vSAN HCL Health - Controller Release SupportvSAN Health Service – vSAN HCL Health – Controller DrivervSAN Health Service - vSAN HCL Health – vSAN HCL DB up-to-datevSAN Health Service - vSAN HCL Health – SCSI Controller on vSAN HCLvSAN Health Service - Cluster Health – CLOMD liveness checkvSAN Health Service - Cluster Health - vSAN Health service installationvSAN Health Check InformationvSAN Health Service - Network Health - Active Multicast connectivity checkVirtual SAN 运行状况服务 - 网络运行状况 - 存在连接问题的主机vSAN 健全性サービス - ネットワークの健全性 - 接続に問題のあるホスト