Mismatch of driver/firmware levels

You can check the current installed firmware version with “fcinfo hba-port” command on the host.

Update firmware with Oracle procedure:

 

 

Note this will RESET the HBA and take all devices on that controller offline. Any VxVM paths via that controller will also become disabled. Time needed to re-enable the paths will depend on proper detection by vxesd and/or cycle time of the restore daemon process.

 

- you must issue a 'luxadm -e forcelip ' to trigger the firmware update (issuing a "reset" with the emlxadm utility if emlxadm installed will work as well).

- Verify driver and firmware updated version via “fcinfo hba-port” command

Applies To

 

The behavior of firmware update has changed with the Emulex HBA when used with the Oracle HBA driver (emlxs). Previous versions would install firmware automatically at boot time when the HBA driver was updated. This no longer happens with version   145098-02/ modinfo - v20100729-2.50p and later versions. After Solaris 10 patch 145098-02 and later is loaded for the Emulex HBA driver, a further manual step is required to update the firmware of the HBA. Firmware levels are specific to the driver level and are documented by Oracle as part of their FC_HBA_DRIVER_FIRMWARE_Matrix. Until the firmware is updated (manual procedure) and the host rebooted, performance may vary between disks from the same array and contention may be seen when more hosts join the cluster. This has been seen on Emulex LP11002 HBA with old firmware v2.80x5 and driver 145098-04 / modinfo - v20101022-2.60h.  Note: If the server is booted with a older Sol10 image with the older driver behavior, the older firmware level WILL be updated to the HBA automatically at boot. This can happen when switching boot images during upgrades or backing out of upgrades with disk images that are older copies with drivers previous to 145098-02.