"vSAN Cluster Configuration Consistency" Skyline health alert reports performance service enabled on cluster but not on hosts in new vSAN cluster.

Products

• VMware vSAN
• VMware vCenter Server

Issue/Introduction

Symptoms:

• Newly configured vSAN cluster has the below vSAN Skyline health alerts triggered.

• "vSAN Cluster Configuration Consistency" this vSAN Skyline health check reports that:

  • vSAN datastore is not compatible with the policy configured for vSAN performance service.

  • Performance service is turned on in cluster configuration, but it is not enabled yet.

• "Performance stats" reports that it is not enabled.

• The storage policy applied to the vSAN performance object is the vSAN Default Storage policy (RAID1), but it shows up as incompatible with the current vSAN cluster:
  

• There is no vSAN performance object created:

  

Environment

VMware vSAN 8.x

VMware vCenter 8.x

Cause

• Due to the vSAN storage policy not being compatible for the cluster, when the performance service is enabled the vSAN performance object is unable to be created.

• Due to this, the the alert "Performance stats" gets triggered as the performance service is not yet fully enabled.

• The alert "vSAN Cluster Configuration Consistency" gets triggered as the performance service is enabled on the cluster and not yet enabled on the hosts.

• The error is triggered by a false 'Datastore does not match current VM policy' report by the vCenter Storage Profile Service (SPS) regarding the vSAN datastore:

  

• This is a rare issue, for newly created vSAN clusters where the SPS service does not add the vSAN datastore to it's compatible list of datastore for the storage policy - Datastore does not match current VM policy.

Resolution

To resolve this issue:

1. SSH as root to vCenter managing the impacted vSAN cluster.

2. Restart the vCenter's vmware-sps service using command:

   service-control --restart vmware-sps

   If vCenters are in linked mode, restart vmware-sps service on all the vCenters.

If this does not resolve the issue, re-synchronize the storage providers in vCenter.