VSAN-Troubleshooting-Reference-Manual

Recommendations

Info

Diagnostics and Troubleshooting Reference Manual – Virtual SAN 5. ESXi version check, all hosts should be above 6.0; the administrator should ensure that all hosts are upgraded to version 6.0. 6. Disk auto-claim should be disabled prior to upgrading because with autoclaim enabled, we cannot remove disk groups to evacuate data; the administrator may disable this configuration through vSphere web client UI, or via the RVC command: vsan.cluster_change_autoclaim -d 7. Detect if inaccessible objects exist in the VSAN cluster; if inaccessible swap object exists, the administrator may use the following RVC command to cleanup: vsan.purge_inaccessible_vswp_objects 8. Detect unhealthy disks used by VSAN; the administrator may use the RVC command "vsan.disks_stats" to check all in-use disks, and manually fix the issue, such as replacing broken disk with a new one; 9. Detect if there are v2 object in given VSAN cluster if the administrator specifies "downgrade" mode; v2 objects should be removed if customer really needs a v1 VSAN cluster. Downgrade is for rollback, if a user encounters an issue and needs to go back to v1 on disk format. 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
Diagnostics and Troubleshooting Reference Manual – Virtual SAN On-disk format post upgrade check: vsan.disks_limits After upgrading, the number of supported component will be 9,000 per host. This can be checked with vsan.check_limits. /ie-vcsa-03.ie.local/vsan-dc> vsan.check_limits computers/vsan/ 2014-12-10 16:54:14 +0000: Querying limit stats from all hosts ... 2014-12-10 16:54:18 +0000: Fetching VSAN disk info from cs-ie-h03.ie.local (may take a moment) ... 2014-12-10 16:54:18 +0000: Fetching VSAN disk info from cs-ie-h01.ie.local (may take a moment) ... 2014-12-10 16:54:18 +0000: Fetching VSAN disk info from cs-ie-h04.ie.local (may take a moment) ... 2014-12-10 16:54:18 +0000: Fetching VSAN disk info from cs-ie-h02.ie.local (may take a moment) ... 2014-12-10 16:54:20 +0000: Done fetching VSAN disk infos +--------------------+-------------------+-------------------------------------------+ | Host | RDT | Disks | +--------------------+-------------------+-------------------------------------------+ | cs-ie-h02.ie.local | Assocs: 156/45000 | Components: 97/9000 | | | Sockets: 26/10000 | naa.600508b1001c0cc0ba2a3866cf8e28be: 9% | | | Clients: 11 | naa.600508b1001c19335174d82278dee603: 3% | | | Owners: 12 | naa.600508b1001c10548f5105fc60246b4a: 3% | | | | naa.600508b1001c07d525259e83da9541bf: 1% | | | | naa.600508b1001c64b76c8ceb56e816a89d: 0% | | | | naa.600508b1001ca36381622ca880f3aacd: 2% | | | | naa.600508b1001cb2234d6ff4f7b1144f59: 3% | | cs-ie-h03.ie.local | Assocs: 151/45000 | Components: 97/9000 | | | Sockets: 26/10000 | naa.600508b1001c9c8b5f6f0d7a2be44433: 0% | | | Clients: 0 | naa.600508b1001cd259ab7ef213c87eaad7: 4% | | | Owners: 17 | naa.600508b1001c1a7f310269ccd51a4e83: 17% | | | | naa.600508b1001c9b93053e6dc3ea9bf3ef: 7% | | | | naa.600508b1001ceefc4213ceb9b51c4be4: 2% | | | | naa.600508b1001c2b7a3d39534ac6beb92d: 2% | | | | naa.600508b1001cb11f3292fe743a0fd2e7: 3% | | cs-ie-h04.ie.local | Assocs: 438/45000 | Components: 97/9000 | | | Sockets: 42/10000 | naa.600508b1001c846c000c3d9114ed71b3: 6% | | | Clients: 68 | naa.600508b1001c258181f0a088f6e40dab: 6% | | | Owners: 68 | naa.600508b1001cf639237aaffff152af66: 0% | | | | naa.600508b1001cadff5d80ba7665b8f09a: 15% | | | | naa.600508b1001c51f3a696fe0bbbcb5096: 8% | | | | naa.600508b1001c4b820b4d80f9f8acfa95: 20% | | | | naa.600508b1001c6a664d5d576299cec941: 4% | | cs-ie-h01.ie.local | Assocs: 1/45000 | Components: 0/9000 | | | Sockets: 4/10000 | naa.600508b1001c16be6e256767284eaf88: 0% | | | Clients: 0 | naa.600508b1001c3ea7838c0436dbe6d7a2: 0% | | | Owners: 0 | naa.600508b1001c388c92e817e43fcd5237: 0% | | | | naa.600508b1001ccd5d506e7ed19c40a64c: 0% | | | | naa.600508b1001c61cedd42b0c3fbf55132: 0% | | | | naa.600508b1001c64816271482a56a48c3c: 0% | | | | naa.600508b1001c79748e8465571b6f4a46: 0% | | | | naa.600508b1001c2ee9a6446e708105054b: 0% | +--------------------+-------------------+-------------------------------------------+ 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 3
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: Diagnostics and Troubleshooting Ref
Page 171: Diagnostics and Troubleshooting Ref
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
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

Create successful ePaper yourself

Delete template?

Save as template?