VSAN-Troubleshooting-Reference-Manual

Recommendations

Info

Diagnostics and Troubleshooting Reference Manual – Virtual SAN | | proportionalCapacity: 0 | | | hostFailuresToTolerate: 1 | | | forceProvisioning: 0 +-------------------------------------------+---------------------------+ | Unknown SPBM Profile. UUID: | hostFailuresToTolerate: 1 | | 5810fe86-6f0f-4718-835d-ce30ff4e0975-gen0 | | +-------------------------------------------+---------------------------+ Recreate missing SPBM Profiles using following RVC commands: spbm.profile_create --rule VSAN.hostFailuresToTolerate=1 5810fe86-6f0f-4718-835dce30ff4e0975-gen0 Do you want to create SPBM Profiles now? [Y/N] Y Running: spbm.profile_create --rule VSAN.hostFailuresToTolerate=1 5810fe86-6f0f-4718- 835d-ce30ff4e0975-gen0 Please rerun the command to fix up any missing VM SPBM Profile associations /localhost/vsan-dc/computers> The final issue relates to the use of a distributed switch. If there is a distributed switch in the configuration, then information about the switch is now lost since this is saved on the vCenter server. If the original vCenter Server is still available, you can export the distributed switch configuration and then import it on the new vCenter server. If it is not available, then distributed switch, distributed portgroups, and all of the mappings will need to be created and the host’s networking needs to be moved to the new distributed switch. Preserving Storage Policies during vCenter Backups & Restores VMware Knowledgebase Article 2072307 describes how to preserve VM Storage Policies during the back and restore of a vCenter server. 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 2
Diagnostics and Troubleshooting Reference Manual – Virtual SAN Known issue: Migration complete but Maintenance Mode not entered Note that the vsan.resync_dashboard command may not display the full information about a resynchronization activity. Therefore if a host in the Virtual SAN cluster is placed into maintenance mode, and full data migration is requested, but is still in progress when the vsan.resync_dashboard reports no bytes to sync, it could well mean that other objects, for example templates, are still resync’ing. > vsan.resync_dashboard ie-vsan-01 2014-11-06 12:07:45 +0000: Querying all VMs on VSAN ... 2014-11-06 12:07:45 +0000: Querying all objects in the system from cs-ie-h01.ie.local ... 2014-11-06 12:07:45 +0000: Got all the info, computing table ... +-----------+-----------------+---------------+ | VM/Object | Syncing objects | Bytes to sync | +-----------+-----------------+---------------+ +-----------+-----------------+---------------+ | Total | 0 | 0.00 GB | +-----------+-----------------+---------------+ The following commands will help check if this is the case: vsan.disks_stats First, use vsan.disks_stats on the host that is being placed into maintenance mode. Check for any disks that still have a significant amount of used space and a number of components greater than 0. Note that display name of the disk. In the example below, cs-ie-03.ie.local is the host placed into maintenance mode. > vsan.disks_stats 0 +--------------------------------------+--------------------+-------+------+-----------+------+----------+---------+ | | | | Num | Capacity | | | Status | | DisplayName | Host | isSSD | Comp | Total | Used | Reserved | Health | +--------------------------------------+--------------------+-------+------+-----------+------+----------+---------+ | naa.600508b1001c9c8b5f6f0d7a2be44433 | cs-ie-h03.ie.local | SSD | 0 | 186.27 GB | 0 % | 0 % | OK (v1) | | naa.600508b1001cd259ab7ef213c87eaad7 | cs-ie-h03.ie.local | MD | 1 | 136.50 GB | 16 % | 0 % | OK (v1) | | naa.600508b1001ceefc4213ceb9b51c4be4 | cs-ie-h03.ie.local | MD | 0 | 136.50 GB | 1 % | 0 % | OK (v1) | | naa.600508b1001cb11f3292fe743a0fd2e7 | cs-ie-h03.ie.local | MD | 0 | 136.50 GB | 1 % | 0 % | OK (v1) | | naa.600508b1001c9b93053e6dc3ea9bf3ef | cs-ie-h03.ie.local | MD | 0 | 136.50 GB | 1 % | 0 % | OK (v1) | | naa.600508b1001c2b7a3d39534ac6beb92d | cs-ie-h03.ie.local | MD | 0 | 136.50 GB | 1 % | 0 % | OK (v1) | | naa.600508b1001c1a7f310269ccd51a4e83 | cs-ie-h03.ie.local | MD | 0 | 136.50 GB | 1 % | 0 % | OK (v1) | +--------------------------------------+--------------------+-------+------+-----------+------+----------+--------- vsan.disk_object_info In the output above, there is only one component left on the disk in question. All other disks are empty on that host. Next, use the vsan.disk_object_info to see what objects and components are still on the disk, using the display name from the previous command as an argument. > vsan.disk_object_info ie-vsan-01 naa.600508b1001c79748e8465571b6f4a46 Physical disk naa.600508b1001c79748e8465571b6f4a46 (52191bcb-7ea5-95ff-78af- 2b14f72d95e4): 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 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:
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: Diagnostics and Troubleshooting Ref
Page 191: Diagnostics and Troubleshooting Ref
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

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

Delete template?

Save as template?