VSAN-Troubleshooting-Reference-Manual

Recommendations

Info

Diagnostics and Troubleshooting Reference Manual – Virtual SAN DOM Object: 8e802154-7ccc-2191-0b4e-001517a69c72 (owner: cs-ie-h03.ie.local, policy: hostFailuresToTolerate = 1) Context: Can't attribute object to any VM, may be swap? Witness: 5f635b54-04f5-8c08-e5f6-0010185def78 (state: ACTIVE (5), host: cs-ieh03.ie.local, md: naa.600508b1001ceefc4213ceb9b51c4be4, ssd: eui.d1ef5a5bbe864e27002471febdec3592, usage: 0.0 GB) Witness: 5f635b54-a4d2-8a08-9efc-0010185def78 (state: ACTIVE (5), host: cs-ieh02.ie.local, md: naa.600508b1001c19335174d82278dee603, ssd: eui.c68e151fed8a4fcf0024712c7cc444fe, usage: 0.0 GB) RAID_1 Component: 5f635b54-14f7-8608-a05a-0010185def78 (state: RECONFIGURING (10), host: cs-ie-h04.ie.local, md: naa.600508b1001c4b820b4d80f9f8acfa95, ssd: eui.a15eb52c6f4043b5002471c7886acfaa, dataToSync: 1.79 GB, usage: 21.5 GB) Component: ad153854-c4c4-c4d8-b7e0-001f29595f9f (state: ACTIVE (5), host: cs-ieh03.ie.local, md: naa.600508b1001ceefc4213ceb9b51c4be4, ssd: eui.d1ef5a5bbe864e27002471febdec3592, usage: 21.5 GB) Component: 8e802154-cc97-ffc1-4c85-001517a69c72 (state: ACTIVE (5), host: cs-ieh01.ie.local, md: **naa.600508b1001c79748e8465571b6f4a46**, ssd: eui.48f8681115d6416c00247172ce4df168, usage: 21.5 GB) At this point, we are able to see a state of RECONFIGURING against one component, and also a dataToSync field displaying how much data is left to sync. This will need to complete before the host can be successfully placed into maintenance mode. vsan.object_info If more information about the object is need, e.g. the name, the command vsan.object_info can be used against the DOM Object ID from the previous command output. Checking the resulting displayed object path might help in ascertaining what object it is, for example, a template. > vsan.object_info ie-vsan-01 8e802154-7ccc-2191-0b4e-001517a69c72 DOM Object: 8e802154-7ccc-2191-0b4e-001517a69c72 (owner: cs-ie-h03.ie.local, policy: hostFailuresToTolerate = 1) Witness: 3f675b54-3043-9fc5-bdb9-0010185def78 (state: ACTIVE (5), host: cs-ieh02.ie.local, md: naa.600508b1001c19335174d82278dee603, ssd: eui.c68e151fed8a4fcf0024712c7cc444fe, usage: 0.0 GB) RAID_1 Component: 5f635b54-14f7-8608-a05a-0010185def78 (state: ACTIVE (5), host: cs-ieh04.ie.local, md: naa.600508b1001c4b820b4d80f9f8acfa95, ssd: eui.a15eb52c6f4043b5002471c7886acfaa, usage: 21.5 GB) Component: ad153854-c4c4-c4d8-b7e0-001f29595f9f (state: ACTIVE (5), host: cs-ieh03.ie.local, md: naa.600508b1001ceefc4213ceb9b51c4be4, ssd: eui.d1ef5a5bbe864e27002471febdec3592, usage: 21.5 GB) Extended attributes: Address space: 53687091200B (50.00 GB) Object class: vdisk Object path: /vmfs/volumes/vsan:52dc5a95d04bcbb9-9d90f486c2f14d1d/89802154-5c14-e025- 333b-001517a69c72/ie-ora-01-clone.vmdk In this example, using the object path at the end of the output, it was determined that this was a template. By converting this template to a virtual machine temporarily, the evacuation then succeeded. Note that this is an issue that is well understood internally at VMware and something that will be addressed going forward. 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 4
Diagnostics and Troubleshooting Reference Manual – Virtual SAN Here are some other RVC commands that can help to remediate storage related issues on Virtual SAN. vsan.object_status_report This command verifies the health of the Virtual SAN cluster. When all objects are in a known good state, it is expected that this command return no issues. With absent components however, this command provides details on the missing components. The way to read the output below is that there are 96 objects in this Virtual SAN cluster that only have 3 out of 3 components currently in a healthy state. The second line can be read as the Virtual SAN cluster having 19 object where only 1 of its 3 components are currently healthy. Therefore they are listed as orphans. > vsan.obj_status_report 0 2014-11-28 12:47:04 +0000: Querying all VMs on VSAN ... 2014-11-28 12:47:04 +0000: Querying all objects in the system from cs-ie-h02.ie.local ... 2014-11-28 12:47:04 +0000: Querying all disks in the system from cs-ie-h02.ie.local ... 2014-11-28 12:47:05 +0000: Querying all components in the system from cs-ieh02.ie.local ... 2014-11-28 12:47:05 +0000: Querying all object versions in the system ... 2014-11-28 12:47:06 +0000: Got all the info, computing table ... Histogram of component health for non-orphaned objects +-------------------------------------+------------------------------+ | Num Healthy Comps / Total Num Comps | Num objects with such status | +-------------------------------------+------------------------------+ | 3/3 (OK) | 96 | +-------------------------------------+------------------------------+ Total non-orphans: 96 Histogram of component health for possibly orphaned objects +-------------------------------------+------------------------------+ | Num Healthy Comps / Total Num Comps | Num objects with such status | +-------------------------------------+------------------------------+ | 1/3 (Unavailable) | 19 | +-------------------------------------+------------------------------+ Total orphans: 19 Total v1 objects: 115 Total v2 objects: 0 If Virtual SAN doesn’t start to remediate automatically, i.e. doesn’t start to rebuild the missing components, there are a couple of possible causes. First, ensure that if the components are declared ABSENT, that 60 minutes have passed. Virtual SAN will only begin remediating ABSENT components after 60 minutes by default. Another likely issue is that there is a resource issue. If Virtual SAN does not have enough resources to auto-remediate, consider adding additional resources to the cluster, or resolving the initial problem. Once the new resources become available, Virtual SAN will remediate automatically. 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
Page 1 and 2:
Diagnostics and Troubleshooting Gui
Page 3 and 4:
Diagnostics and Troubleshooting Ref
Page 5 and 6:
Page 7 and 8:
Page 9 and 10:
Page 11 and 12:
Page 13 and 14:
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144: Diagnostics and Troubleshooting Ref
Page 193: Diagnostics and Troubleshooting Ref
Page 245 and 246:
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
Page 263 and 264:
Page 265 and 266:
Page 267 and 268:
Page 269 and 270:
Page 271 and 272:
Page 273 and 274:
Page 275 and 276:
Page 277 and 278:
Page 279 and 280:
Page 281 and 282:
Page 283 and 284:
Page 285 and 286:
Page 287 and 288:
Page 289 and 290:
Page 291 and 292:
Page 293 and 294:
Page 295:
show all

VSAN-Troubleshooting-Reference-Manual

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?