Assess Firmware and Driver Version of devices in ESXi Host

Something that came up recently was the need for comparable information as far as drivers and firmware used in our ESXi hosts. Use case was that I wanted to know what ahci driver was being used by an internal m.2 SSD and compare it to the hardware compatibility list.Below I’ve outline the steps I took to gather this information.

The device used in my example is a 12Core MacPro(2013) with an internal 1TB SSD.

Log into the host via SSH, and at the prompt enter:

esxcli storage core adapter list

From that we have now isolated the 1TB SSD we are looking for in this case: vmhba0 using the ahci driver.

HBA Name  Driver       Link State  UID                                   Capabilities         Description

vmhba0    ahci         link-n/a    sata.vmhba0       (0000:0e:00.0) Samsung, Inc. Samsung PCIe SSD Controller

 

The next thing we will attempt to do is to look at which, ahci, in this case, driver is installed and running. In this case we will run a search for the occurrence of “ahci”

esxcli software vib list | grep ahci

The date returned is the date we installed the driver/ESXi

 

Next we will need to gather some information pertaining to vendor and device identification in order to search the vmware compatibility guide. The 4 pieces of information required are

  • Vendor ID -VID
  • Device ID -DID
  • SubVendor ID -SVID
  • SubDevice ID -SSID

Screen Shot 2017-05-03 at 4.52.51 PM

We do this by running the following to list device states:

vmkchdev -l

Screen Shot 2017-05-03 at 4.49.04 PM

The extracted information needed is next to the device, in our case “vmhba0”

0000:0e:00.0 144d:1600 0000:0000

Armed with this information we can now input the four values into the VMWare compatibility guide matrix. COMPATIBILITY MATRIX

144d = VID

1600 = DID

0000 = SVID

0000 = SSID

Screen Shot 2017-05-03 at 4.56.49 PM

 

Entered into the matrix and hitting “Update and review” results we are then presented with the recommended driver, that we can now compare to what is currently running.

Screen Shot 2017-05-03 at 4.57.08 PM

 

See VMWARE KB

 

plasebikan