Now to get the exact device code to look the drivers up on the HCL, use “ vmkchdev -l | grep vmhba1” - this will list the Vendor, Device, Sub-vendor and Sub-device IDs:Ġ0:15:00.0 1077: 2532 1077: 0166 vmkernel vmhba1

Use “ vmkload_mod -s qla2xxx | grep Version” to locate the exact version of the driver loaded and you’ll see output similar to this: You’ll see output similar to below - the currently loaded driver is the second column, highlighted in red. Log on to the host via SSH and issue an “ esxcfg-scsidevs -a” to list installed SCSI devices. Identify the HBA and driver package requiredįirst, we need to determine the exact hardware ID of the HBA and then get the latest supported driver package from the VMware Hardware Compatibility List. This is fine to do manually for a few hosts, but would be a real pain for the 300+ hosts in the environment I manage.Įnter VMware Update Manager - we already use it to patch and upgrade our hosts, but it can also apply host extensions - driver packages as well. Analysis showed that the drivers for the HBA were over a year out of date so the suggested fix from VMware was to update the drivers. Please take care when following any guidance to ensure you have up-to-date recommendations.Ī problem reared it’s head over the weekend with one of our hosts' Fibre Channel HBAs negotiating it’s way down to 2GB, and consequently introducing massive latency for the LUNs behind it. This article is now 8 years old! It is highly likely that this information is out of date and the author will have completely forgotten about it.

Add network drivers to esxi 6 web