09.03.2015 Views

VSAN-Troubleshooting-Reference-Manual

VSAN-Troubleshooting-Reference-Manual

VSAN-Troubleshooting-Reference-Manual

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Diagnostics and <strong>Troubleshooting</strong> <strong>Reference</strong> <strong>Manual</strong> – Virtual SAN<br />

Channel: 0<br />

Target: 0<br />

LUN: 0<br />

Plugin: NMP<br />

State: active<br />

Transport: parallel<br />

Adapter Identifier: unknown.fioiom0<br />

Target Identifier: unknown.0:0<br />

Adapter Transport Details: Unavailable or path is unclaimed<br />

Target Transport Details: Unavailable or path is unclaimed<br />

Maximum IO Size: 1048576<br />

sas.5001438013ebe0d0-sas.1438013ebe0d0-naa.600508b1001c258181f0a088f6e40dab<br />

UID:sas.5001438013ebe0d0-sas.1438013ebe0d0-naa.600508b1001c258181f0a088f6e40dab<br />

Runtime Name: vmhba1:C0:T0:L1<br />

Device: naa.600508b1001c258181f0a088f6e40dab<br />

Device Display Name: HP Serial Attached SCSI Disk<br />

(naa.600508b1001c258181f0a088f6e40dab)<br />

Adapter: vmhba1<br />

Channel: 0<br />

Target: 0<br />

LUN: 1<br />

Plugin: NMP<br />

State: active<br />

Transport: sas<br />

Adapter Identifier: sas.5001438013ebe0d0<br />

Target Identifier: sas.1438013ebe0d0<br />

Adapter Transport Details: 5001438013ebe0d0<br />

Target Transport Details: 1438013ebe0d0<br />

Maximum IO Size: 4194304<br />

There is a lot of information included in this command output. However there is a<br />

Fusion-IO adapter called fioiom0 and there is a HP adapter called vmhba1. Possibly<br />

a better way to display this information, one line at a time, is to use esxcfgscsidevs<br />

–A. The command simply displays which device is attached to which<br />

controller, without all of the other ancillary information shown above.<br />

esxcfg-scsidevs –A<br />

~ # esxcfg-scsidevs -A<br />

fioiom0 eui.a15eb52c6f4043b5002471c7886acfaa<br />

vmhba0 mpx.vmhba0:C0:T0:L0<br />

vmhba1 naa.600508b1001c4b820b4d80f9f8acfa95<br />

vmhba1 naa.600508b1001c4d41121b41182fa83be4<br />

vmhba1 naa.600508b1001c846c000c3d9114ed71b3<br />

vmhba1 naa.600508b1001c258181f0a088f6e40dab<br />

vmhba1 naa.600508b1001cc426a15528d121bbd880<br />

vmhba1 naa.600508b1001c51f3a696fe0bbbcb5096<br />

vmhba1 naa.600508b1001cadff5d80ba7665b8f09a<br />

vmhba1 naa.600508b1001cd0fe479b5e81ca7ec77e<br />

vmhba32 mpx.vmhba32:C0:T0:L0<br />

~ #<br />

This displays which adapter a particular SCSI device is attached to. Remember that<br />

the Fusion-IO adapter is called fioiom0 and that the HP adapter is vmhba1, so here<br />

we can see the disks associated with each adapter. Either a EUI identifier, an MPX<br />

identifier or an NAA identifier, identifies the SCSI devices. Different SCSI devices<br />

from different vendors identify themselves in different ways, although all are<br />

supported. The Fusion-IO is using EUI, whereas the HP devices use an NAA identifier.<br />

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

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!