VSAN-Troubleshooting-Reference-Manual
VSAN-Troubleshooting-Reference-Manual
VSAN-Troubleshooting-Reference-Manual
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 />
The interesting parts are highlighted in bold. There are two objects visible, the VM<br />
Home Namespace and the VMDK (referred to as Disk backing in the above output).<br />
Again, the VM Home is using a StripeWidth=1, where the VMDK is using a<br />
StripeWidth=2. Therefore the VMDK has RAID_0 configurations in each replica,<br />
whereas the VM Home does not.<br />
Another important point is that all components are ACTIVE. There are no<br />
components in an STALE, ABSENT or DEGRADED state.<br />
vsan.object_info<br />
If you note the outputs from vsan.vm_object_info, a “DOM object” reference is<br />
displayed. DOM is short for Distributed Object Manager and is a core component of<br />
Virtual SAN that implements the RAID configuration. Using this “DOM object”<br />
information, one can ask Virtual SAN to display similar information about the object<br />
via a different RVC command called vsan.object_info. Note that this command<br />
must be run against a cluster and not against a virtual machine as was the case with<br />
the previous command.<br />
/localhost/ie-datacenter-01> cd 1<br />
/localhost/ie-datacenter-01/computers> ls<br />
0 ie-vsan-01 (cluster): cpu 109 GHz, memory 330 GB<br />
/localhost/ie-d atacenter-01/computers> vsan.object_info 0 fdeb4354-40f7-bace-a8f5-<br />
001f29595f9f<br />
DOM Object: fdeb4354-40f7-bace-a8f5-001f29595f9f (owner: cs-ie-h01.ie.local, policy:<br />
hostFailuresToTolerate = 1, stripeWidth = 1, spbmProfileId = c1421e53-ded2-4ea1-843dff6149e03525,<br />
proportionalCapacity = [0, 100], spbmProfileGenerationNumber = 0)<br />
Witness: feeb4354-e85e-c34b-ef73-001f29595f9f (state: ACTIVE (5), host: cs-ieh01.ie.local,<br />
md: naa.600508b1001c16be6e256767284eaf88, ssd:<br />
eui.48f8681115d6416c00247172ce4df168, usage: 0.0 GB)<br />
RAID_1<br />
Component: feeb4354-58c7-c24b-ef14-001f29595f9f (state: ACTIVE (5), host: cs-ieh03.ie.local,<br />
md: naa.600508b1001cd259ab7ef213c87eaad7, ssd:<br />
eui.d1ef5a5bbe864e27002471febdec3592, usage: 0.1 GB)<br />
Component: feeb4354-ccba-c14b-2af4-001f29595f9f (state: ACTIVE (5), host: cs-ieh04.ie.local,<br />
md: naa.600508b1001cadff5d80ba7665b8f09a, ssd:<br />
eui.a15eb52c6f4043b5002471c7886acfaa, usage: 0.1 GB)<br />
Extended attributes:<br />
Address space: 273804165120B (255.00 GB)<br />
Object class: vmnamespace<br />
Object path: /vmfs/volumes/vsan:52dc5a95d04bcbb9-9d90f486c2f14d1d/<br />
/localhost/ie-datacenter-01/computers><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 / 93