VSAN-Troubleshooting-Reference-Manual

Recommendations

Info

Diagnostics and Troubleshooting Reference Manual – Virtual SAN Channel: 0 Target: 0 LUN: 0 Plugin: NMP State: active Transport: parallel Adapter Identifier: unknown.fioiom0 Target Identifier: unknown.0:0 Adapter Transport Details: Unavailable or path is unclaimed Target Transport Details: Unavailable or path is unclaimed Maximum IO Size: 1048576 sas.5001438013ebe0d0-sas.1438013ebe0d0-naa.600508b1001c258181f0a088f6e40dab UID:sas.5001438013ebe0d0-sas.1438013ebe0d0-naa.600508b1001c258181f0a088f6e40dab Runtime Name: vmhba1:C0:T0:L1 Device: naa.600508b1001c258181f0a088f6e40dab Device Display Name: HP Serial Attached SCSI Disk (naa.600508b1001c258181f0a088f6e40dab) Adapter: vmhba1 Channel: 0 Target: 0 LUN: 1 Plugin: NMP State: active Transport: sas Adapter Identifier: sas.5001438013ebe0d0 Target Identifier: sas.1438013ebe0d0 Adapter Transport Details: 5001438013ebe0d0 Target Transport Details: 1438013ebe0d0 Maximum IO Size: 4194304 There is a lot of information included in this command output. However there is a Fusion-IO adapter called fioiom0 and there is a HP adapter called vmhba1. Possibly a better way to display this information, one line at a time, is to use esxcfgscsidevs –A. The command simply displays which device is attached to which controller, without all of the other ancillary information shown above. esxcfg-scsidevs –A ~ # esxcfg-scsidevs -A fioiom0 eui.a15eb52c6f4043b5002471c7886acfaa vmhba0 mpx.vmhba0:C0:T0:L0 vmhba1 naa.600508b1001c4b820b4d80f9f8acfa95 vmhba1 naa.600508b1001c4d41121b41182fa83be4 vmhba1 naa.600508b1001c846c000c3d9114ed71b3 vmhba1 naa.600508b1001c258181f0a088f6e40dab vmhba1 naa.600508b1001cc426a15528d121bbd880 vmhba1 naa.600508b1001c51f3a696fe0bbbcb5096 vmhba1 naa.600508b1001cadff5d80ba7665b8f09a vmhba1 naa.600508b1001cd0fe479b5e81ca7ec77e vmhba32 mpx.vmhba32:C0:T0:L0 ~ # This displays which adapter a particular SCSI device is attached to. Remember that the Fusion-IO adapter is called fioiom0 and that the HP adapter is vmhba1, so here we can see the disks associated with each adapter. Either a EUI identifier, an MPX identifier or an NAA identifier, identifies the SCSI devices. Different SCSI devices from different vendors identify themselves in different ways, although all are supported. The Fusion-IO is using EUI, whereas the HP devices use an NAA identifier. 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 / 30
Diagnostics and Troubleshooting Reference Manual – Virtual SAN A note about SCSI identifiers NAA stands for Network Addressing Authority identifier. EUI stands for Extended Unique Identifier. The number is guaranteed to be unique to that LUN. The NAA or EUI identifier is the preferred method of identifying LUNs and the storage device generates the number. Since the NAA or EUI is unique to the LUN, if the LUN is presented the same way across all ESXi hosts, the NAA or EUI identifier remains the same. Some devices do not provide the NAA number described above. In these circumstances, an MPX Identifier is generated by ESXi to represent the LUN or disk. The identifier takes the form similar to that of the canonical name of previous versions of ESXi with the “mpx.” prefix. This identifier can be used in the exact same way as the NAA Identifier described above.” Refer to VMware KB article 1014953 for further information. Displaying disk drive information At this point the controllers/adapters have been identified. If more information regarding the disks drives is required, this next command lists all logical devices on the ESXi host on a single line, with limited information: esxcfg-scsidevs –c ~ # esxcfg-scsidevs -c Device UID Device Type Console Device Size Multipath PluginDisplay Name eui.a15eb52c6f4043b5002471c7886acfaa Direct-Access /vmfs/devices/disks/eui.a15eb52c6f4043b5002471c7886acfaa 1149177MB NMP Local FUSIONIO Disk (eui.a15eb52c6f4043b5002471c7886acfaa) mpx.vmhba0:C0:T0:L0 CD-ROM /vmfs/devices/cdrom/mpx.vmhba0:C0:T0:L0 0MB NMP Local hp CD- ROM (mpx.vmhba0:C0:T0:L0) mpx.vmhba32:C0:T0:L0 Direct-Access /vmfs/devices/disks/mpx.vmhba32:C0:T0:L0 1917MB NMP Local USB Direct-Access (mpx.vmhba32:C0:T0:L0) naa.600508b1001c258181f0a088f6e40dab Direct-Access /vmfs/devices/disks/naa.600508b1001c258181f0a088f6e40dab 139979MB NMP HP Serial Attached SCSI Disk (naa.600508b1001c258181f0a088f6e40dab) naa.600508b1001c4b820b4d80f9f8acfa95 Direct-Access /vmfs/devices/disks/naa.600508b1001c4b820b4d80f9f8acfa95 139979MB NMP HP Serial Attached SCSI Disk (naa.600508b1001c4b820b4d80f9f8acfa95) naa.600508b1001c4d41121b41182fa83be4 Direct-Access /vmfs/devices/disks/naa.600508b1001c4d41121b41182fa83be4 139979MB NMP HP Serial Attached SCSI Disk (naa.600508b1001c4d41121b41182fa83be4) naa.600508b1001c51f3a696fe0bbbcb5096 Direct-Access /vmfs/devices/disks/naa.600508b1001c51f3a696fe0bbbcb5096 139979MB NMP HP Serial Attached SCSI Disk (naa.600508b1001c51f3a696fe0bbbcb5096) naa.600508b1001c846c000c3d9114ed71b3 Direct-Access /vmfs/devices/disks/naa.600508b1001c846c000c3d9114ed71b3 139979MB NMP HP Serial Attached SCSI Disk (naa.600508b1001c846c000c3d9114ed71b3) naa.600508b1001cadff5d80ba7665b8f09a Direct-Access /vmfs/devices/disks/naa.600508b1001cadff5d80ba7665b8f09a 139979MB NMP HP Serial Attached SCSI Disk (naa.600508b1001cadff5d80ba7665b8f09a) ~ # This is a list of all the SCSI devices on this ESXi host, including their sizes. 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 / 31
Page 1 and 2: Diagnostics and Troubleshooting Gui
Page 3 and 4: Diagnostics and Troubleshooting Ref
Page 29: Diagnostics and Troubleshooting Ref
Page 81 and 82:
Diagnostics and Troubleshooting Ref
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:
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

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

Delete template?

Save as template?