vSAN Skyline Health Service - Cluster health – vCenter state is authoritative
Article ID: 326957
Updated On:
Products
VMware vSAN
Issue/Introduction
This article explains the Cluster Health alert: – vCenter State Is Authoritative check in the vSAN Skyline Health Service and provides details about why it might report an error.
Environment
VMware vSAN 8.0.x
VMware vSAN 7.0.x
VMware vSAN 6.6.x
VMware vSAN 6.7.x
VMware vSAN 7.0.x
VMware vSAN 6.6.x
VMware vSAN 6.7.x
Resolution
Q: What does the Cluster Health – vCenter State Is Authoritative check do?
This check verifies that all hosts in the vSAN cluster are using the current managing vCenter Server as the source of truth for the cluster configuration, including the vSAN cluster membership list. During normal operation, the vCenter Server can publish the latest host membership list and update the configuration for all hosts in the cluster. This health check reports an error if vCenter Server configuration is not synchronized with a member host, and is no longer accepted as the source of truth.
This issue can lead to auto-update failures for the configuration, including the vSAN cluster membership list.
Q: What does it mean when it is in an error state?
If this check is red, it means that the hosts listed in the out-of-sync table are not using this vCenter Server as the source of truth for vSAN cluster configuration. This problem can occur when you replace and recover a managing vCenter Server. The hosts with configuration problems are configured to be managed by the previous vCenter Server.
The problem hosts are listed with information for the previous managing vCenter Server.
Q: How does one troubleshoot and fix the error state?
To fix this problem, go to Cluster > Monitor > vSAN > Health. Select Cluster > vCenter state is authoritative, and click Update ESXi configuration.
This action synchronizes all hosts in the cluster with the current vCenter Server, and forces the vCenter Server configuration, including the vSAN cluster membership list, to all member hosts.
If clicking Update ESXi configuration doesn't resolve the issue run esxcfg-advcfg -g /VSAN/IgnoreClusterMemberListupdates on all hosts in the cluster to confirm the value is set to 0. If the value is 1 set it back to the default of 0 by running esxcfg-advcfg -s 0 /VSAN/IgnoreClusterMemberListupdates.
Q: What are the potential side effects of clicking Update ESXi configuration?
This action overrides the existing vSAN cluster configuration on all hosts in this vCenter Server cluster. Verify that all ESXi hosts from the vSAN cluster are added to the vCenter Server cluster. Any host that is not part of this vCenter Server cluster are removed from the cluster.
Incorrect configuration settings can be pushed to all hosts in the vSAN cluster, and can cause problems. Before you take action, verify that all vSAN configuration settings in vCenter Server are correct, such as fault domains, deduplication, encryption, and so on.
This check verifies that all hosts in the vSAN cluster are using the current managing vCenter Server as the source of truth for the cluster configuration, including the vSAN cluster membership list. During normal operation, the vCenter Server can publish the latest host membership list and update the configuration for all hosts in the cluster. This health check reports an error if vCenter Server configuration is not synchronized with a member host, and is no longer accepted as the source of truth.
This issue can lead to auto-update failures for the configuration, including the vSAN cluster membership list.
Q: What does it mean when it is in an error state?
If this check is red, it means that the hosts listed in the out-of-sync table are not using this vCenter Server as the source of truth for vSAN cluster configuration. This problem can occur when you replace and recover a managing vCenter Server. The hosts with configuration problems are configured to be managed by the previous vCenter Server.
The problem hosts are listed with information for the previous managing vCenter Server.
Q: How does one troubleshoot and fix the error state?
To fix this problem, go to Cluster > Monitor > vSAN > Health. Select Cluster > vCenter state is authoritative, and click Update ESXi configuration.
This action synchronizes all hosts in the cluster with the current vCenter Server, and forces the vCenter Server configuration, including the vSAN cluster membership list, to all member hosts.
If clicking Update ESXi configuration doesn't resolve the issue run esxcfg-advcfg -g /VSAN/IgnoreClusterMemberListupdates on all hosts in the cluster to confirm the value is set to 0. If the value is 1 set it back to the default of 0 by running esxcfg-advcfg -s 0 /VSAN/IgnoreClusterMemberListupdates.
Q: What are the potential side effects of clicking Update ESXi configuration?
This action overrides the existing vSAN cluster configuration on all hosts in this vCenter Server cluster. Verify that all ESXi hosts from the vSAN cluster are added to the vCenter Server cluster. Any host that is not part of this vCenter Server cluster are removed from the cluster.
Incorrect configuration settings can be pushed to all hosts in the vSAN cluster, and can cause problems. Before you take action, verify that all vSAN configuration settings in vCenter Server are correct, such as fault domains, deduplication, encryption, and so on.
Feedback
Yes
No
Powered by
