VSAN-Troubleshooting-Reference-Manual

Diagnostics and Troubleshooting Reference Manual – Virtual SAN
This information displayed above can also be observed by using the following
command:
esxcfg-scsidevs –a
~ # esxcfg-scsidevs -a
vmhba0 ata_piix link-n/a sata.vmhba0 (0:0:31.2) Intel Corporation ICH10
4 port SATA IDE Controller
vmhba1 hpsa link-n/a sas.5001438013ebe0d0 (0:5:0.0) Hewlett-Packard Company
Smart Array P410i
vmhba32 usb-storage link-n/a usb.vmhba32 () USB
vmhba33 bnx2i unbound iscsi.vmhba33 Broadcom iSCSI Adapter
vmhba34 bnx2i unbound iscsi.vmhba34 Broadcom iSCSI Adapter
vmhba35 bnx2i unbound iscsi.vmhba35 Broadcom iSCSI Adapter
vmhba36 bnx2i unbound iscsi.vmhba36 Broadcom iSCSI Adapter
fioiom0 iomemory-vsl link-n/a unknown.fioiom0 (0:11:0.0) Fusion-io ioDrive2
vmhba37 ata_piix link-n/a sata.vmhba37 (0:0:31.2) Intel Corporation ICH10
4 port SATA IDE Controller
~ #
The commands include good descriptions of the adapters to allow administrators to
determine exactly which storage controllers and flash devices are running on a host.
The storage controller is a HP Smart Array P410i, and the PCI-E flash device is a
Fusion-IO ioDrive2. The driver used by the adapters is also shown.
Caution: Note that this HP Smart Array 410i is shown for illustration and
troubleshooting purposes only. This controller from HP is not on the Virtual SAN VCG,
as we shall see shortly.
Note also that the description field contains entries such as (0:5:0.0) and (0:11:0.0).
This refers to the adapter PCI slot location and this information can be used later
with some additional commands to verify that this is the adapter used by Virtual
SAN.
Handling multiple controllers
At this point, using the previous ESXCLI command, a list of controllers and disk
drives has been found. However, if there were multiple SCSI controllers on the host,
how would one determine which disk was associated with which controller? This
next ESXCLI command allows us to do just that.
esxcli storage core path list
Note that the adapter is listed in the output of each device:
~ # esxcli storage core path list
unknown.fioiom0-unknown.0:0-eui.a15eb52c6f4043b5002471c7886acfaa
UID: unknown.fioiom0-unknown.0:0-eui.a15eb52c6f4043b5002471c7886acfaa
Runtime Name: fioiom0:C0:T0:L0
Device: eui.a15eb52c6f4043b5002471c7886acfaa
Device Display Name: Local FUSIONIO Disk (eui.a15eb52c6f4043b5002471c7886acfaa)
Adapter: fioiom0
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 / 29