VSAN-Troubleshooting-Reference-Manual
VSAN-Troubleshooting-Reference-Manual
VSAN-Troubleshooting-Reference-Manual
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Diagnostics and <strong>Troubleshooting</strong> <strong>Reference</strong> <strong>Manual</strong> – Virtual SAN<br />
various hosts in the cluster. If no host can communicate to any other host, each host<br />
will be in its own partition, and will be designated its own “master” node. When<br />
multiple hosts are reporting themselves as “master”, there is a partition.<br />
If there is only one host in its own partition, and all other hosts are in their own<br />
partition, then the scope of the issue would appear to be just that host. If all hosts<br />
were in their own unique partition, then it would suggest a network-wide problem.<br />
esxcli vsan cluster get<br />
Here is an example of a partition with a single node. It is designated “master” but<br />
there is no backup node, or are there any additional members in the cluster.<br />
~ # esxcli vsan cluster get<br />
Cluster Information<br />
Enabled: true<br />
Current Local Time: 2012-12-18T10:35:19Z<br />
Local Node UUID: 507e7bd5-ad2f-6424-66cb-1cc1de253de4<br />
Local Node State: MASTER<br />
Local Node Health State: HEALTHY<br />
Sub-Cluster Master UUID: 507e7bd5-ad2f-6424-66cb-1cc1de253de4<br />
Sub-Cluster Backup UUID:<br />
Sub-Cluster UUID: 52e4fbe6-7fe4-9e44-f9eb-c2fc1da77631<br />
Sub-Cluster Membership Entry Revision: 7<br />
Sub-Cluster Member UUIDs: 507e7bd5-ad2f-6424-66cb-1cc1de253de4<br />
Sub-Cluster Membership UUID: ba45d050-2e84-c490-845f-1cc1de253de4<br />
~ #<br />
Compare the above output to one taken from a 4-node cluster that has formed<br />
correctly and is not partitioned in any way. Note the Sub-Cluster Member UUIDs in<br />
this list.<br />
~ # esxcli vsan cluster get<br />
Cluster Information<br />
Enabled: true<br />
Current Local Time: 2014-11-28T09:05:29Z<br />
Local Node UUID: 54188e3a-84fd-9a38-23ba-001b21168828<br />
Local Node State: MASTER<br />
Local Node Health State: HEALTHY<br />
Sub-Cluster Master UUID: 54188e3a-84fd-9a38-23ba-001b21168828<br />
Sub-Cluster Backup UUID: 545ca9af-ff4b-fc84-dcee-001f29595f9f<br />
Sub-Cluster UUID: 529ccbe4-81d2-89bc-7a70-a9c69bd23a19<br />
Sub-Cluster Membership Entry Revision: 3<br />
Sub-Cluster Member UUIDs: 54188e3a-84fd-9a38-23ba-001b21168828, 545ca9af-ff4bfc84-dcee-001f29595f9f,<br />
5460b129-4084-7550-46e1-0010185def78, 54196e13-7f5f-cba8-<br />
5bac-001517a69c72<br />
Sub-Cluster Membership UUID: 80757454-2e11-d20f-3fb0-001b21168828<br />
One additional way of checking for partitions is to use RVC commands. Some<br />
examples are show here.<br />
V M W A R E S T O R A G E B U D O C U M E N T A T I O N / 1 1 4
Change language