09.03.2015 Views

VSAN-Troubleshooting-Reference-Manual

VSAN-Troubleshooting-Reference-Manual

VSAN-Troubleshooting-Reference-Manual

SHOW MORE
SHOW LESS

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 />

Network status: Misconfiguration detected<br />

Network configuration issues on Virtual SAN normally show up as a<br />

Misconfiguration detected on the main Virtual SAN screen in the vSphere Web Client.<br />

Clicking on the (i) information icon usually gives some additional detail. This can be<br />

caused by a number of issues, the most common of which are covered here.<br />

Identifying a Partitioned Cluster<br />

Consider a cluster experiencing a network partition issue. The easiest way to<br />

identify how exactly the cluster is partitioned is to navigate to the Disk Management<br />

view of Virtual SAN shown below (taken from a 5.5 environment), and look at the<br />

Network Partition Group column. If all hosts are part of the same group, then there<br />

is no partitioning. However, if hosts are in different groups, partitioning has<br />

occurred.<br />

Because some hosts appear in Group 1 and others appear in Group 2, there is a<br />

network partition. There are other ways of telling whether a cluster has been<br />

partitioned. One method is to use the esxcli vsan cluster get command on the<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 3

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!