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

This view also allows administrators to determine if there is any contention on any<br />

of the physical disks (and by extrapolation, any disk groups) that make up the<br />

overall Virtual SAN cluster. Note that the statistics shown are purely the physical<br />

disk layer (including the caching layer) but do not include any other Virtual SAN<br />

overhead (e.g. networking or Virtual SAN RAID). If virtual machine (<strong>VSAN</strong> Client)<br />

latency is an issue, but there is no latency visible in this <strong>VSAN</strong> Disk view, then the<br />

high latency may be due to network issues, which can be further investigated via the<br />

“Network” view.<br />

<strong>VSAN</strong> Disks – Full size graphs<br />

Click on any point in the chart to have the values displayed on the right hand side.<br />

If the <strong>VSAN</strong> Disks view shows physical disk contention across a majority of hosts,<br />

then this may indicates that the workload run by VMs is collectively higher than the<br />

<strong>VSAN</strong> cluster can handle. In that case, either reduce the storage workload, or check<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 / 2 1 1

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

Saved successfully!

Ooh no, something went wrong!