Enum Description

Enum Constants

Name	Description
datamove	Objects in this state are fully compliant with their policy and are healthy, but vSAN is actively rebuilding them.
healthy	The object is in perfect condition, exactly aligned with its policy, and is not currently being moved or otherwise worked on.
inaccessible	An object has suffered more failures (permanent or temporary) than it was configured to tolerate, and is currently unavailable and inaccessible.
nonavailabilityrelatedincompliance	This is a catch all state when none of the other states apply. An object with this state is not compliant with its current policy, but is meeting the availablity (NumberOfFailuresToTolerate) policy. The object might be in this state because vSAN is not able to meet a non-availability related policy such as NumberOfDiskStripesPerObject because of lack of available resources. User need check the vSAN system resources like the number of fault domains and hosts, free capacity to make it compliant.
nonavailabilityrelatedincompliancewithpausedrebuild	The object is not compliant with its current policy, but is meeting the availablity (NumberOfFailuresToTolerate) policy. However, the object rebuild is paused because of lack of available resources.
nonavailabilityrelatedincompliancewithpolicypending	Object policy was recently changed and has not yet been applied. The object is still fully compliant with the new availability policy, but not compliant the new non-availability related policies. Note it's a transient status and will either transit to 'healthy' or 'nonavailabilityrelatedincompliancewithpolicypendingfailed' status eventually depending on if the new policy can be accepted or not due to resource limitation. And depending on how much transient capacity is being used in the cluster, the object will stay in the status from minutes to hours. No user action needed for this status.
nonavailabilityrelatedincompliancewithpolicypendingfailed	Object policy was recently changed but failed to apply to the object because of lacking of resource. The object is still fully compliant with the new availability policy. User need add more resource to the cluster so that vSAN can re-apply the new non-availability related policy to the object automatically to make it fully compliant.
nonavailabilityrelatedreconfig	The object is fully in compliance with the NumberOfFailuresToTolerate policy and the data movement is to satisfy another policy change.
reducedavailabilitywithactiverebuild	The object has suffered a failure, but it was configured to be able to tolerate the failure.
reducedavailabilitywithnorebuild	The object has suffered a failure or its policy was recently changed to have higher availability requirement but vSAN was able to tolerate it. The object is accessible and I/O is flowing.
reducedavailabilitywithnorebuilddelaytimer	The object has suffered a failure, but vSAN was able to tolerate it. However, vSAN is not yet working on re-protecting the object, as it is waiting for the 60-minute (default) delay timer to expire before issuing the re-protect.
reducedavailabilitywithpausedrebuild	The object has suffered a failure or its policy was recently changed to have higher availability requirement. However, the object rebuild is paused because of lack of available resources.
reducedavailabilitywithpolicypending	Object policy was recently changed but has not yet been applied to the object. The object current availability is less than what is expected by the new policy. Note it's a transient status and will either transit to 'healthy' or 'reducedavailabilitywithpolicypendingfailed' eventually depending on if the new policy can be accepted or not due to resource limitation. And depending on how much transient capacity is being used in the cluster, the object will stay in the status from minutes to hours. No user action needed for this status.
reducedavailabilitywithpolicypendingfailed	Object policy has been changed but failed to apply to the object because of lack of available resources. User need add more resource to the cluster so that vSAN can re-apply the new availability policy to the object automatically to make it full compliant.
VsanObjectHealthState_Unknown	Represent the value when the lower version client cannot recognize the enum value

Name

Description

datamove

Objects in this state are fully compliant with their policy and are healthy, but vSAN is actively rebuilding them.

healthy

The object is in perfect condition, exactly aligned with its policy, and is not currently being moved or otherwise worked on.

inaccessible

An object has suffered more failures (permanent or temporary) than it was configured to tolerate, and is currently unavailable and inaccessible.

nonavailabilityrelatedincompliance

This is a catch all state when none of the other states apply. An object with this state is not compliant with its current policy, but is meeting the availablity (NumberOfFailuresToTolerate) policy. The object might be in this state because vSAN is not able to meet a non-availability related policy such as NumberOfDiskStripesPerObject because of lack of available resources. User need check the vSAN system resources like the number of fault domains and hosts, free capacity to make it compliant.

nonavailabilityrelatedincompliancewithpausedrebuild

The object is not compliant with its current policy, but is meeting the availablity (NumberOfFailuresToTolerate) policy. However, the object rebuild is paused because of lack of available resources.

nonavailabilityrelatedincompliancewithpolicypending

Object policy was recently changed and has not yet been applied. The object is still fully compliant with the new availability policy, but not compliant the new non-availability related policies. Note it's a transient status and will either transit to 'healthy' or 'nonavailabilityrelatedincompliancewithpolicypendingfailed' status eventually depending on if the new policy can be accepted or not due to resource limitation. And depending on how much transient capacity is being used in the cluster, the object will stay in the status from minutes to hours. No user action needed for this status.

nonavailabilityrelatedincompliancewithpolicypendingfailed

Object policy was recently changed but failed to apply to the object because of lacking of resource. The object is still fully compliant with the new availability policy. User need add more resource to the cluster so that vSAN can re-apply the new non-availability related policy to the object automatically to make it fully compliant.

nonavailabilityrelatedreconfig

The object is fully in compliance with the NumberOfFailuresToTolerate policy and the data movement is to satisfy another policy change.

reducedavailabilitywithactiverebuild

The object has suffered a failure, but it was configured to be able to tolerate the failure.

reducedavailabilitywithnorebuild

The object has suffered a failure or its policy was recently changed to have higher availability requirement but vSAN was able to tolerate it. The object is accessible and I/O is flowing.

reducedavailabilitywithnorebuilddelaytimer

The object has suffered a failure, but vSAN was able to tolerate it. However, vSAN is not yet working on re-protecting the object, as it is waiting for the 60-minute (default) delay timer to expire before issuing the re-protect.

reducedavailabilitywithpausedrebuild

The object has suffered a failure or its policy was recently changed to have higher availability requirement. However, the object rebuild is paused because of lack of available resources.

reducedavailabilitywithpolicypending

Object policy was recently changed but has not yet been applied to the object. The object current availability is less than what is expected by the new policy. Note it's a transient status and will either transit to 'healthy' or 'reducedavailabilitywithpolicypendingfailed' eventually depending on if the new policy can be accepted or not due to resource limitation. And depending on how much transient capacity is being used in the cluster, the object will stay in the status from minutes to hours. No user action needed for this status.

reducedavailabilitywithpolicypendingfailed

Object policy has been changed but failed to apply to the object because of lack of available resources. User need add more resource to the cluster so that vSAN can re-apply the new availability policy to the object automatically to make it full compliant.

VsanObjectHealthState_Unknown

Represent the value when the lower version client cannot recognize the enum value

Show WSDL type definition

         <simpleType xmlns="http://www.w3.org/2001/XMLSchema" xmlns:vsan="urn:vsan" name="VsanObjectHealthVsanObjectHealthState">
            <restriction base="xsd:string">
               <enumeration value="VsanObjectHealthState_Unknown"/>
               <enumeration value="inaccessible"/>
               <enumeration value="datamove"/>
               <enumeration value="nonavailabilityrelatedincompliancewithpolicypending"/>
               <enumeration value="nonavailabilityrelatedincompliancewithpolicypendingfailed"/>
               <enumeration value="nonavailabilityrelatedincompliance"/>
               <enumeration value="reducedavailabilitywithpolicypending"/>
               <enumeration value="reducedavailabilitywithpolicypendingfailed"/>
               <enumeration value="reducedavailabilitywithnorebuilddelaytimer"/>
               <enumeration value="reducedavailabilitywithpausedrebuild"/>
               <enumeration value="nonavailabilityrelatedincompliancewithpausedrebuild"/>
               <enumeration value="healthy"/>
               <enumeration value="reducedavailabilitywithactiverebuild"/>
               <enumeration value="nonavailabilityrelatedreconfig"/>
               <enumeration value="reducedavailabilitywithnorebuild"/>
            </restriction>
         </simpleType>

Enum - VsanObjectHealthVsanObjectHealthState(vim.host.VsanObjectHealth.VsanObjectHealthState)

Enum Description