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

| | | naa.600508b1001c3ea7838c0436dbe6d7a2: 16% |<br />

| | | naa.600508b1001c2ee9a6446e708105054b: 3% |<br />

| | | naa.600508b1001ccd5d506e7ed19c40a64c: 1% |<br />

| | | naa.600508b1001c16be6e256767284eaf88: 11% |<br />

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

The RDT (Reliable Datagram Transport) limits were discussed in the network<br />

troubleshooting section.<br />

For disks, each host has a limit of 3,000 components, and the current component<br />

count is also displayed. Also visible, percentage wise, is how much of the disk is<br />

being consumed.<br />

Note: The component limit per host was 3,000 for Virtual SAN version 5.5. Virtual SAN<br />

Version 6.0 increased this limit count to 9,000. However, the on-disk format needs to be<br />

updated to v2 for the new component limit to take effect.<br />

Both of these disk limits in the vsan.check_limits are worth noting regularly to<br />

ensure that the limits are not being reached.<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 3 5

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

Saved successfully!

Ooh no, something went wrong!