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

Using RVC for performance monitoring<br />

There are some RVC commands that can give administrators an overview of Virtual<br />

SAN performance. Here is one such command.<br />

vsan.vm_perf_stats<br />

vsan.vm_perf_stats ~/vms/W2k12-SQL2k12 --interval 10 --show-objects<br />

output:<br />

2014-10-31 15:19:33 +0000: Got all data, computing table<br />

+--------------------------+-------------+--------------+--------------+<br />

| VM/Object | IOPS | Tput (KB/s) | Latency (ms) |<br />

+--------------------------+-------------+--------------+--------------+<br />

| W2k12-SQL2k12 | | | |<br />

| /W2k12-SQL2k12.vmx | 0.3r/0.3w | 0.2r/0.2w | 0.5r/1.2w |<br />

| /W2k12-SQL2k12.vmdk | 1.2r/6.1w | 7.7r/46.5w | 0.4r/1.8w |<br />

| /W2k12-SQL2k12_1.vmdk | 0.0r/7.7w | 0.4r/1236.7w | 0.8r/1.8w |<br />

| /W2k12-SQL2k12_2.vmdk | 0.4r/647.6w | 1.6r/4603.3w | 1.3r/1.8w |<br />

+--------------------------+-------------+--------------+--------------+<br />

By way of understanding the relationship between the metrics, the following<br />

calculations may help:<br />

IOPS = (MBps Throughput / KB per IO) * 1024<br />

MBps = (IOPS * KB per IO) / 1024<br />

Using <strong>VSAN</strong> Observer for Performance Monitoring<br />

One should take the time to familiarize oneself with <strong>VSAN</strong> Observer, even when<br />

there are no anomalies occurring on the Virtual SAN cluster. Check what is a normal<br />

value for metrics like latency, IOPS, Outstanding IO, bandwidth, etc. It may even be<br />

worth gathering offline bundles from time to time to use as reference against<br />

possible future issues.<br />

As mentioned in the <strong>VSAN</strong> Observer section, any metrics that exceed boundary<br />

thresholds will be displayed with a red underline against the chart. This can then be<br />

used as a point to start investigating the root cause. Various reasons why some of<br />

these charts may be outside their respective thresholds have been discussed, but<br />

anything from an overloaded system to poor performing devices to physical switch<br />

issues impacting the network could be a root cause. Fortunately, <strong>VSAN</strong> Observer can<br />

assist with all of this.<br />

Next some <strong>VSAN</strong> Observer case studies are examined, where there are details on<br />

what to expect from <strong>VSAN</strong> Observer when some common scenarios are encountered.<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 1

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

Saved successfully!

Ooh no, something went wrong!