VSAN-Troubleshooting-Reference-Manual

Diagnostics and Troubleshooting Reference Manual – Virtual SAN
000:00b:00.0
Address: 000:00b:00.0
Segment: 0x0000
Bus: 0x0b
Slot: 0x00
Function: 0x00
VMkernel Name: fioiom0
Vendor Name: Fusion-io
Device Name: ioDrive2
Configured Owner: Unknown
Current Owner: VMkernel
Vendor ID: 0x1aed
Device ID: 0x2001
SubVendor ID: 0x1aed
SubDevice ID: 0x2001
Device Class: 0x0180
Device Class Name: Mass storage controller
Programming Interface: 0x00
Revision ID: 0x04
Interrupt Line: 0x0a
IRQ: 10
Interrupt Vector: 0x5d
PCI Pin: 0x30
Spawned Bus: 0x00
Flags: 0x0201
Module ID: 4178
Module Name: iomemory-vsl
Chassis: 0
Physical Slot: 2
Slot Description: PCI-E Slot 2
Passthru Capable: true
Parent Device: PCI 0:0:8:0
Dependent Device: PCI 0:11:0:0
Reset Method: Link reset
FPT Sharable: true
As well as PCI Address, there is the vendor id, device id, sub-vendor id and subdevice
id of the PCI adapter. If this is a rebranded device, this is the information
required to verify that it is supported via the VCG.
The other useful piece of information from this output is the device driver, referred
to as the “Module Name” above. For HP, the driver is the hpsa; for Fusion-IO it is the
iomemory-vsl.
Now that the adapter information and driver information has been retrieved, the
next step is to check that the device driver version that is running on the host is
supported. The supported version of a driver may change as issues are discovered,
and the driver version may need to be updated for reasons of reliability or
performance or both.
The driver names are already visible in the previous adapter list output, but it does
not have the version. One command, vmkload_mod –s, can provide this
information.
vmkload_mod –s
~ # vmkload_mod -s hpsa
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 / 33