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

As we can see, the <strong>VSAN</strong> Disks view also displays the same high latency observed in<br />

the <strong>VSAN</strong> Client view. This view is the physical disks view, and is basically<br />

representative of the latency seen by Virtual SAN accessing physical disks. In a<br />

nutshell, this rules out the Virtual SAN network as the cause of the latency issue.<br />

Another cause of latency could be CPU. Perhaps the CPUs are maxed out, and not<br />

able to process I/O quickly enough. We can check the CPU utilization via ‘PCPU’<br />

view. It shows the following:<br />

The ALL PCUs chart is green, and overall the CPU utilization is not very high. Also, all<br />

of the Virtual SAN “worldlets” are showing green and none of them are maxed out.<br />

The impression from this view is that there are no CPU issues, so this also rules out<br />

CPU as being the root cause of the latency issue.<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 6 3

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

Saved successfully!

Ooh no, something went wrong!