The vSAN cluster has been shut down and restarted. All hosts of the vSAN cluster are out of Maintenance Mode.
VMs registered on the vSAN datastore are seen as inaccessible on vCenter or ESXi inventory.
"esxcli vsan debug object health summary get", all objects may be seen as healthy. However, there are situations where objects will be seen as inaccessible as well.VMware vSAN (All versions).
The advanced parameters "/VSAN/DOMPauseAllCCPs" and/or "/VSAN/IgnoreClusterMemberListUpdates" have been changed to "1" during the shutdown task on all the hosts in the vSAN cluster. Upon starting vSAN cluster, the cluster start task is expected to change this value to "0". This would make the objects to show inaccessible and I/O to fail on the components.
This advanced setting is used for vSAN cluster shutdown for data protection, as setting this option to 1 pauses all vSAN components operations on a host, effectively making objects owned by that host inaccessible.
In other words, the vSAN objects are not available to the compute resources, resulting in inaccessible VMs in the inventory.
Modify the advanced parameter DOMPauseAllCCPs and IgnoreClusterMemberListUpdate on all the hosts in the cluster to the default setting of 0.
Run command "esxcfg-advcfg -g /VSAN/DOMPauseAllCCPs" on all hosts to get the current value:
[root@esxi#:~] esxcfg-advcfg -g /VSAN/DOMPauseAllCCPsValue of DOMPauseAllCCPs is 1
If the value is 1, this means /VSAN/DOMPauseAllCCPs is enabled and the objects owned by this host will be unavailable until the setting is reverted to the default value of 0 by running the following command on the affected hosts.:
[root@esxi#:~] esxcfg-advcfg -s 0 /VSAN/DOMPauseAllCCPs
Run command "esxcfg-advcfg -g /VSAN/on all hosts to get the current value:IgnoreClusterMemberListUpdate"
[root@esxi#:~] esxcfg-advcfg -g /VSAN/IgnoreClusterMemberListUpdateValue of IgnoreClusterMemberListUpdateis 1
If the value is 1, this means /VSAN/is enabled and vCenter will not be able to make any changes to cluster membership until the setting is reverted to the default value of 0 by running the following command on the affected hosts.:IgnoreClusterMemberListUpdate
[root@esxi#:~] esxcfg-advcfg -s 0 /VSAN/ IgnoreClusterMemberListUpdate