vSAN Health Service - Cluster Health - vSAN cluster configuration consistency
Article ID: 326880
Updated On:
Products
Issue/Introduction
This article explains the Cluster Health - Cluster configuration consistency check in the vSAN Health Service and provides details about why it might report an error.
For more information on vSAN cluster configuration consistency, see:
- vSAN Health Service - Cluster Health - Advanced vSAN configuration in sync
- Network diagnostic mode health check warning in cluster configuration consistency check
- Network configuration is out of sync in vSAN Cluster Configuration Consistency check
Environment
Resolution
Q: What does the Cluster Health - vSAN cluster configuration consistency test do?
This health check validates that all hosts in this cluster and their disks have a configuration consistent with the configuration set at the cluster level.
For Example: dedup/compression, Data-at-Rest/Data-in-Transit encryption, performance service.
Q: What does it mean when it is in an error state?
If this check fails, it means that there are inconsistent configuration (e.g. dedup/compression, encryption) setup on hosts or disks within the cluster. The results of this health check will report the inconsistency in the cluster that can range from host and disks with issues to encryption mismatches, and will provide some remediation recommendations to resolve the issue.
If the vSAN cluster is in compute-only mode, user may see the health check trigger if there's a host with a vSAN disk-group created. This is because vSAN disk-groups are not supported in compute-only clusters.
Q: How does one troubleshoot and fix the error state?
The User can attempt to remediate the issue by clicking the "Remediate inconsistent configuration" button to run the cluster configuration remediation action to fix hosts and disks which have inconsistent configurations (e.g. dedup/compression, encryption).
Note: Exercise caution when remediating any inconsistency that has the potential to initiate a large amount of data resync (e.g., enabling/disabling deduplication/compression, or encryption on disks), as this can negatively impact cluster performance.
For performance service configuration inconsistency, user cannot manually remediate the cluster configuration by clicking the "Remediate inconsistent configuration" button. An auto-remediation will be applied to this cluster when an inconsistent configuration is detected for the vSAN performance between vCenter and ESXi hosts. Note that the configuration inconsistency health check for performance service is available since the vSphere 6.7 release.
In the case of a compute-only cluster with a host containing a vSAN disk-group, this can be remediated either by removing the host from the cluster or removing the disk-group from the host.
Feedback
