09.03.2015 Views

VSAN-Troubleshooting-Reference-Manual

VSAN-Troubleshooting-Reference-Manual

VSAN-Troubleshooting-Reference-Manual

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Diagnostics and <strong>Troubleshooting</strong> <strong>Reference</strong> <strong>Manual</strong> – Virtual SAN<br />

Once the full charts view is expanded, what is notable is that the amount of data<br />

transmitted and received on the Virtual SAN network is rather small:<br />

This is taken from the host where the virtual machine resides. These hosts use 1Gb<br />

NICs, which are fully supported by Virtual SAN, but should be dedicated to Virtual<br />

SAN traffic. So why is the TxMBps and RxMBps so low when we are clearly wishing<br />

to drive far more IOPS than we are achieving?<br />

In this scenario, using the Network I/O Control feature of a distributed switch to<br />

limit the Virtual SAN network traffic produced this situation. Although somewhat<br />

contrived, it is an accurate reflection of the behavior that may be observed in Virtual<br />

SAN if the network is suffering from issues. In fact, we had a customer situation<br />

where the switch was sending excessive pause frames (in the millions) impacting<br />

Virtual SAN traffic and leading to extremely poor latency for the virtual machine<br />

workloads (observed via the client and DOM owner views) but no latency issues on<br />

the disks view.<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 7 0

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

Saved successfully!

Ooh no, something went wrong!