Recently I had an issue with the VMware VSAN where the health status was listing a number of inaccessible objects .
It issue was due to an MTU mismatch on a Nexus 5k that was configured incorrectly. But prior to figuring that out I had to do some troubleshooting and that was my first introduction to RVC – Ruby vCenter Console
Logon – How do I access it ? – Pretty straight forward right .. ?
First of enable Bash Shell on the VCSA – http://bit.ly/drenablebash – See David Ring’s Post on Bash and advanced settings
Once at the shell screen type rvc firstname.lastname@example.org@localhost
where vsphere.local is your vsphere SSO domain. Do not forget the second @localhost
From here you can interact from the menu system like any Linux O/S
CD to change Directory
LS to list Directory Items
Containers are referenced with a number beside them so you can list the numbers as variables when running commands from the console. Tab works here and I used it extensively to figure out the commands.
Few Sample Command examples:
Check Cluster Status
where 1 is a vsan enabled cluster
Purge inaccessible objects
If the purge inaccessible object command doesn’t remove all the orphaned objects you will have to remove them manually. But before that you can run some cool commands to get some more detail on the objects.
vsan.cmmds_find -u guid 1
You can get futher detail by running the following commands on one of the ESX hosts in the vsan enabled cluster.
/usr/lib/vmware/osfs/bin/objtool getAttr -u guid
Finally to remove the object run this command from any host in the cluster
/usr/lib/vmware/osfs/bin/objtool delete -u ‘guid’ -f -v 10
The RVC has many other powerful capabilities and is a really cool tool to use. I really recommend you to go play with it. For more info