VSAN-Troubleshooting-Reference-Manual
VSAN-Troubleshooting-Reference-Manual
VSAN-Troubleshooting-Reference-Manual
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 />
Here are some other RVC commands that can help to remediate storage related<br />
issues on Virtual SAN.<br />
vsan.object_status_report<br />
This command verifies the health of the Virtual SAN cluster. When all objects are in<br />
a known good state, it is expected that this command return no issues. With absent<br />
components however, this command provides details on the missing components.<br />
The way to read the output below is that there are 96 objects in this Virtual SAN<br />
cluster that only have 3 out of 3 components currently in a healthy state. The second<br />
line can be read as the Virtual SAN cluster having 19 object where only 1 of its 3<br />
components are currently healthy. Therefore they are listed as orphans.<br />
> vsan.obj_status_report 0<br />
2014-11-28 12:47:04 +0000: Querying all VMs on <strong>VSAN</strong> ...<br />
2014-11-28 12:47:04 +0000: Querying all objects in the system from cs-ie-h02.ie.local ...<br />
2014-11-28 12:47:04 +0000: Querying all disks in the system from cs-ie-h02.ie.local ...<br />
2014-11-28 12:47:05 +0000: Querying all components in the system from cs-ieh02.ie.local<br />
...<br />
2014-11-28 12:47:05 +0000: Querying all object versions in the system ...<br />
2014-11-28 12:47:06 +0000: Got all the info, computing table ...<br />
Histogram of component health for non-orphaned objects<br />
+-------------------------------------+------------------------------+<br />
| Num Healthy Comps / Total Num Comps | Num objects with such status |<br />
+-------------------------------------+------------------------------+<br />
| 3/3 (OK) | 96 |<br />
+-------------------------------------+------------------------------+<br />
Total non-orphans: 96<br />
Histogram of component health for possibly orphaned objects<br />
+-------------------------------------+------------------------------+<br />
| Num Healthy Comps / Total Num Comps | Num objects with such status |<br />
+-------------------------------------+------------------------------+<br />
| 1/3 (Unavailable) | 19 |<br />
+-------------------------------------+------------------------------+<br />
Total orphans: 19<br />
Total v1 objects: 115<br />
Total v2 objects: 0<br />
If Virtual SAN doesn’t start to remediate automatically, i.e. doesn’t start to rebuild<br />
the missing components, there are a couple of possible causes. First, ensure that if<br />
the components are declared ABSENT, that 60 minutes have passed. Virtual SAN will<br />
only begin remediating ABSENT components after 60 minutes by default.<br />
Another likely issue is that there is a resource issue. If Virtual SAN does not have<br />
enough resources to auto-remediate, consider adding additional resources to the<br />
cluster, or resolving the initial problem. Once the new resources become available,<br />
Virtual SAN will remediate automatically.<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 9 5
Change language