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

5. ESXi version check, all hosts should be above 6.0; the administrator should<br />

ensure that all hosts are upgraded to version 6.0.<br />

6. Disk auto-claim should be disabled prior to upgrading because with autoclaim<br />

enabled, we cannot remove disk groups to evacuate data; the<br />

administrator may disable this configuration through vSphere web client UI,<br />

or via the RVC command:<br />

vsan.cluster_change_autoclaim -d<br />

7. Detect if inaccessible objects exist in the <strong>VSAN</strong> cluster; if inaccessible swap<br />

object exists, the administrator may use the following RVC command to<br />

cleanup:<br />

vsan.purge_inaccessible_vswp_objects<br />

8. Detect unhealthy disks used by <strong>VSAN</strong>; the administrator may use the RVC<br />

command "vsan.disks_stats" to check all in-use disks, and manually fix<br />

the issue, such as replacing broken disk with a new one;<br />

9. Detect if there are v2 object in given <strong>VSAN</strong> cluster if the administrator<br />

specifies "downgrade" mode; v2 objects should be removed if customer<br />

really needs a v1 <strong>VSAN</strong> cluster. Downgrade is for rollback, if a user<br />

encounters an issue and needs to go back to v1 on disk format.<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 7 2

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

Saved successfully!

Ooh no, something went wrong!