VSAN-Troubleshooting-Reference-Manual

Recommendations

Info

Diagnostics and Troubleshooting Reference Manual – Virtual SAN Note the use of numeric reference for short cuts. Also note that the first part of the vsan command can be typed, and then by hitting the key twice, commandcompletion occurs. This method provides a list of all commands that begin with “vsan.”. The first output is the set of commands taken from a 5.5U2 distribution. > vsan. vsan.apply_license_to_cluster vsan.host_info vsan.check_limits vsan.host_wipe_vsan_disks vsan.check_state vsan.lldpnetmap vsan.clear_disks_cache vsan.obj_status_report vsan.cluster_change_autoclaim vsan.object_info vsan.cluster_info vsan.object_reconfigure vsan.cluster_set_default_policy vsan.observer vsan.cmmds_find vsan.reapply_vsan_vmknic_config vsan.disable_vsan_on_cluster vsan.recover_spbm vsan.disk_object_info vsan.resync_dashboard vsan.disks_info vsan.support_information vsan.disks_stats vsan.vm_object_info vsan.enable_vsan_on_cluster vsan.vm_perf_stats vsan.enter_maintenance_mode vsan.vmdk_stats vsan.fix_renamed_vms vsan.whatif_host_failures vsan.host_consume_disks > This next set of commands comes from a 6.0 distribution: vsan.apply_license_to_cluster vsan.host_wipe_non_vsan_disk vsan.check_limits vsan.host_wipe_vsan_disks vsan.check_state vsan.lldpnetmap vsan.clear_disks_cache vsan.obj_status_report vsan.cluster_change_autoclaim vsan.object_info vsan.cluster_change_checksum vsan.object_reconfigure vsan.cluster_info vsan.observer vsan.cluster_set_default_policy vsan.observer_process_statsfile vsan.cmmds_find vsan.proactive_rebalance vsan.disable_vsan_on_cluster vsan.proactive_rebalance_info vsan.disk_object_info vsan.reapply_vsan_vmknic_config vsan.disks_info vsan.recover_spbm vsan.disks_stats vsan.resync_dashboard vsan.enable_vsan_on_cluster vsan.scrubber_info vsan.enter_maintenance_mode vsan.support_information vsan.fix_renamed_vms vsan.v2_ondisk_upgrade vsan.host_claim_disks_differently vsan.vm_object_info vsan.host_consume_disks vsan.vm_perf_stats vsan.host_evacuate_data vsan.vmdk_stats vsan.host_exit_evacuation vsan.whatif_host_failures vsan.host_info 6.0 versions have a number of additional commands. These additional commands will be discussed throughout the course of this reference guide. One may also reference the Virtual SAN and SPBM RVC Command Reference Guide for additional information. At this point, the first few characters of the rest of the vsan command may be typed, and by hitting the key once again, the command will complete. 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 / 80
Diagnostics and Troubleshooting Reference Manual – Virtual SAN Using RVC to display adapter information In an earlier chapter, ESXi commands that were used to gather adapter information were examined. This was done with a view to using this information to check the VMware Compatibility Guide (VCG) and ensuring that the Virtual SAN components are supported. There is also a way to display useful information about adapters using RVC by using the following command. vsan.disks_info –show-adapters The RVC command, vsan.disks_info --show-adapters, is useful for displaying information about your disks and flash devices. It also displays information about the adapter and drivers used by the ESXi hosts. Here is an output taken from a host with a PCI-E FusionIO adapter. The device shows up as an SSD in the output (this is from the 5.5 version of the command): +-------------------------------------------------------------+-----+--------+-----------------------+ | Local FUSIONIO Disk (eui.48f8681115d6416c00247172ce4df168) | SSD | 1122GB | inUse | | FUSIONIO IODRIVE | | | | | | | | Adapters: | | | | | fioiom0 (iomemory-vsl )| | | | | Fusion-io ioDrive2 | +------------------------------------------------------------+-----+--------+------------------------+ Here is a sample output form a host with uses HP’s P410i controller. The driver is “hpsa” and the disk device size (MD is short for magnetic disk) is 136GB that is actually a relatively small disk drive; this is from the 6.0 version of the command. +-----------------------------------------+-------+---------+----------------------------------------+ | HP Serial Attached SCSI Disk | MD | 136 GB | inUse (The disk resides on a | | (naa.600508b1001c64816271482a56a48c3c) | | | non-local storage transport: | | HP LOGICAL VOLUME | | |'naa.600508b1001c0cc0ba2a3866cf8e28be'.)| | | | | | | | | | Adapters | | | | | vmhba1 (hpsa) | | | | | | | | | | Hewlett-Packard Company | | | | | Smart Array P410i | | | | | | | | | | Checksum Enabled: false | +-----------------------------------------+-------+---------+----------------------------------------+ Using RVC to verify Virtual SAN functionality At this point, the most common RVC commands will be run to check Virtual SAN state and verify functionality. Other commands will be looked at in the later sections of this troubleshooting reference manual. On a Virtual SAN cluster that has just been deployed, the vSphere web client may report everything functioning normally, but it is low on detail. This next set of commands will display detailed information about the state of the Virtual SAN cluster, and confirm that the cluster is fully operational. This first command is very useful for getting an overview of the cluster state. 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 / 81
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: Diagnostics and Troubleshooting Ref
Page 79: Diagnostics and Troubleshooting Ref
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:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
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?