vSAN 6.6 RVC Guide

The "vSAN 6.6 RVC Guide" series explains how to manage your VMware Virtual SAN environment with the Ruby vSphere Console. RVC is an interactive command line tool to control and automate your platform. If you are new to RVC, make sure to read the Getting Started with Ruby vSphere Console Guide. All commands are from the latest vSAN 6.6 version.

The third part explains commands related to the object management in vSAN. These commands are used for troubleshooting or reconfiguration of objects. They also provide an insight on how vSAN works.

vsan.cmmds_find [-t|-u|-o] ~cluster|~host
Display information about an object or component in the vSAN, when only the UUID is known. A powerful command to find objects and detailed object information. Can be used against hosts or clusters. Usage against clusters is recommended to resolve UUID into readable names.

vsan.vm_object_info [-c|-p|-i] ~vm
Prints VSAN object information about a VM. This command is the equivalent to the Manage > VM Storage Policies tab in the vSphere Web Client and allows you to identify where stripes, mirrors and witness of virtual disks are located. The command retains information about:

vsan.disk_object_info ~cluster [disk_uuid]
Prints all objects that are located on a physical disk. This command helps during troubleshooting when you want to identify all objects on a physical disk. You have to know the disk UUID which can be identified with the vsan.cmmds_find command.

Example 1 – Get Disk UUID with vsan.cmmds_find and display all objects located on this disk:

vsan.object_info [-s|-i] ~cluster [obj_uuid]
Prints informations about objects physical location and configuration. The command output is very similar to the vsan.vm_object_info but it is used against a single object.

vsan.object_reconfigure [-p] ~cluster [obj_uuid]
Configure an object with a new policy. To use this command, you need to know the object UUID which can be identified with vsan.cmmds_find or vsan.vm_object_info.

-p, --New policy: New policy

Available policy options are:

hostFailuresToTolerate (Number of failures to tolerate)

forceProvisioning (If VSAN can't fulfill the policy requirements for an object, it will still deploy it)

stripeWidth (Number of disk stripes per object)

cacheReservation (Flash read cache reservation)

proportionalCapacity (Object space reservation)

Be careful to keep existing policies. Always specify all options. The policy has to be defined in the following format:'(("hostFailuresToTolerate" i1) ("forceProvisioning" i1))'