A Distributed Virtual Switch(DVS) failed and had to be replaced.
After replacing the vSAN Cluster Skyline Health Score has at 56% Healthy score.
The Skyline Health Alarm reports that 9 Virtual objects showing inaccessible. These objects a causing the alarm.
vSAN 7.0x
vSAN 8.0x
Without logs from the DVS failure events we cannot absolutely say why the inaccessible objects existed, and cannot explain here why the objects were not cleaned up when broken DVS was removed from vCenter.
Based on VCF Support expertise/experience with inaccessible objects, that the unassociated objects did not exist before the failure of the DVS, that the objects only appeared after the new DVS was implemented.
The inaccessible objects were identified as "config status" objects from the broken DVS.
"uuid": "########-####-####-####-############",
"owner": "########-####-####-####-############",
"health": "Healthy",
"revision": "4",
"type": "CONFIG_STATUS",
"flag": "2",
"minHostVersion": "3",
"md5sum": "8aefdd6dbf7e######8c7#####e4",
"valueLen": "280",
"content": "{\"state\": 45, \"CSN\": 10945, \"SCSN\": 10947, \"highestDiskVersion\": 15, \"objectVersion\": 15, \"objectClass\": 3, \"muxGroup\": 73381561997718996, \"addressSpace\": 4294967296}",
"errorStr": "(null)"
Using vCenter > CLI > RVC (See attachment for the RVC use guide on the reference RVC KB )
RVC tool allowed VCF Support to identify the inaccessible objects.
Once the 9 objects were identified, with the help of VCF Support Engineer, Support was able to remove the objects with specialized support tool.