Ruby vSphere Console (RVC) is deprecated for most vSAN troubleshooting

Products

• VMware vSAN

Issue/Introduction

To provide alternative methods for vSAN troubleshooting and times when RVC is still useful for troubleshooting.

Environment

VMware vSAN 7.0.x

Resolution

Use one of the alternative methods described below to gather vSAN diagnostic information

• Using Esxcli Commands with vSAN
• POWERCLI COOKBOOK FOR VMWARE VSAN

Times when RVC is still useful

• Reclaiming Space with SCSI Unmap (As of version 8.0 this can be enabled via vCenter vSAN Services Advanced options tab)
• Procedures for identifying Unassociated vSAN objects. (70726)
• vSAN -- Web Client -- VMs are showing with Path instead of their Name (= e.g. vmfs/volumes/vsan ......) (2149706)
• Configuring Stretched Cluster Results in "A specified parameter was not correct - Witness host already configured in stretched cluster" (95450)
• When there are multiple VMs showing as inaccessible/orphaned in vCenter yet all vSAN objects are healthy you can run vsan.check_state -re to refresh the VMs in vCenter

Note: The -e switch will unregister/re-register inaccessible VMs which will change the VMs MOD ID so if there are 3rd party applications that depend on these MOD IDs additional steps will need to be taken with those 3rd party applications. If dealing with just Orphaned VMs you can run just the -r switch which will just refresh the VM state.

Additional Information

VMware® Ruby vSphere Console Command Reference for vSAN