In a new two node vsan cluster, Skyline health reports object health error.

Products

• VMware vSAN

Issue/Introduction

Symptoms:

• In a newly deployed vSAN two-node cluster, the vSAN Skyline health check reports an error: Object Health.

Environment

VMware vSAN 6.x
VMware vSAN 7.x
VMware vSAN 8.x

Cause

• Witness node not configured
• VM created using force provisioning option.

Cause validation:

• Run the command "esxcli vsan debug object health summary get" to check the object health.
  esxcli vsan debug object health summary get
Health Status                                              Number Of Objects
---------------------------------------------------------  -----------------
remoteAccessible                                                           0
inaccessible                                                               0
reduced-availability-with-no-rebuild                                      43
reduced-availability-with-no-rebuild-delay-timer                           0
reducedavailabilitywithpolicypending                                       0
reducedavailabilitywithpolicypendingfailed                                 0
reduced-availability-with-active-rebuild                                   0
reducedavailabilitywithpausedrebuild                                       0
data-move                                                                  0
nonavailability-related-reconfig                                           0
nonavailabilityrelatedincompliancewithpolicypending                        0
nonavailabilityrelatedincompliancewithpolicypendingfailed                  0
nonavailability-related-incompliance                                       0
nonavailabilityrelatedincompliancewithpausedrebuild                        0
  
  From the above output, it is confirmed that all the vSAN objects are in "reduced-availability-with-no-rebuild” state.
  
  
• Run the command "esxcli vsan debug object list". Validate the FTT and the VM provisioning option used for all the objects.
  

  esxcli vsan debug object list
Object UUID: ########-####-####-####-############
   Version: 19
   Health: reduced-availability-with-no-rebuild
   Owner: HOST-##
   Size: 10.00 GB
   Used: 0.00 GB
   Used 4K Blocks: 0.00 GB
   Policy:
      proportionalCapacity: [0, 100]
      hostFailuresToTolerate: 1
      forceProvisioning: 1
      CSN: 2

     Configuration:

        Component: ########-####-####-####-############
        Component State: ACTIVE,  Address Space(B): 10737418240 (10.00GB),  Disk UUID: ########-####-####-####-############,  Disk Name: naa.################:2
        Votes: 1,  Capacity Used(B): 12582912 (0.01GB),  Physical Capacity Used(B): 4194304 (0.00GB),  Total 4K Blocks Used(B): 0 (0.00GB),  Host Name: HOST-##

     Type: vdisk
   Path: /vmfs/volumes/vsan:################-################/########-####-####-####-############/VM.vmdk (Exists)
   Group UUID: ########-####-####-####-############
  
  From the above output it is confirmed that the object configured using FTT1 and force Provisioning option and FTT1.

• Confirm from vCenter that the witness node is still not configured.

Resolution

• Deploy the vSAN witness host
• Configure the fault domains.
• Apply the appropriate vSAN storage policy to the VMs.