How to use Esxcli Commands with vSAN for Dell EMC VxRail

This video will demonstrate the how to use Esxcli Commands with vSAN to check objects and cluster health summary to obtain information about vSAN and to troubleshoot your vSAN environment.

Hi, this is Don and I'm a senior principal engineer in the VX and cloud solutions team. Today, we will look at how to check the health of the VC cluster with the Xcii commands.

The X needs space for vant includes options to monitor and control the VS SAN. Specifically, we would be looking at the network storage cluster, health and debug commands XCIV cluster get identifies the cluster information.

We could see that this cluster is enabled. The local note is normal which means it is not a witness, the local node is healthy as well as we look further down. We see that it is unica mode, not in VS mode and the mode is regular.

So it is not a stretch cluster. You sexy a lie. The ST George list identifies the drives that are members of the V sand cluster. We can see that these are identified as SDS. We can identify the two disc groups that are on this node.

We see their capacity and that encryption is not enabled SX CLI VN network list. We identify what VM KN are used for V SAN. And if it is the only type of traffic on the VM kernel part ESX CLI Fein health cluster list. We'll show all the health checks and their states.

This takes a moment to run, go as it runs through the health checks to give us a display. You sexy like health cluster list. Sw we'll show you the identifier along with a check name and states with the cluster identifiers. We can use X Vien health cluster get dash T with the check name.

In this case, we will use object health. And this is this is the stats of the objects in the cluster. For instance, there are only healthy objects in this cluster.

Now that we have the basic items looked at, we can move into ESX cli va debug commands to dive further into the state of the cluster with TSX cli vian debug disk list.

Let us see the objects for disks VM swap and the name space for the virtual machines. And for the last example, we have XC I vian debug rethink list. This will identify if there are any objects that are synchronizing between the hosts.

In this instance with nothing re syncing, we get no output. Otherwise we would have an identifier for the object, the component of that object and how many bytes and gigabytes are left to sync.

Thank you for listening and I hope this has helped