how to get two fibre controllers to use the same EFI driver

[Matthew Murdock]

I have installed 2 of the same PN# FIbre Cards (AH400A) into 2 RX2800 I4's. The Firmware on the SErvers are up to date.

I installed one Card and tried to run the firmware update for the card, The utility reported back saying the firmware was updated (which it was), and the driver was updated from 2.22 to 2.27 or so it said. When I go into EFI the first card driver still says its at 2.22.

I just installed a second PN# card and used the same utility as the first card, and it worked.

Searching for devices.
HP Smart Array P410i Controller     (version 6.42)  2 Logical Drives
Currently the controller is in RAID mode
HP PCIe 1Port 8Gb Fibre Channel Adapter (driver 2.22, firmware 5.06.006)
HP PCIe 1Port 8Gb Fibre Channel Adapter (driver 2.27, firmware 5.06.006)
Booting UEFI Internal Shell
UEFI Shell version 2.30 [2.0]
Current running mode 1.1.2

>>Shell> drivers

>>9F 00000222 D X X  1  - HP Fibre Channel Driver             MemoryMapped(0xB,0x         <== FIrst card installed and updated
>>A7 00000227 D X X  1  - HP Fibre Channel Driver             MemoryMapped(0xB,0x         <== Second card installed and updated with >>same utiltility as the first (CP022831.scexe, and even tried CP030297.scexe)

>>(I run the update again)

The following group of items will be processed at the same time:
  - rewrite rom from 05.06.06 to 5.06.06 for HP AH400A 8Gb Single Port PCIe Fibre Channel Adapter (0/0/0/3/0/0/0).
Warning: This group was rejected because rewrite was not allowed.
The following group of items will be processed at the same time:
  - upgrade efi from 2.22 to 2.27 for HP AH400A 8Gb Single Port PCIe Fibre Channel Adapter (0/0/0/3/0/0/0)
  - rewrite bios from 3.13 to 3.13 for HP AH400A 8Gb Single Port PCIe Fibre Channel Adapter (0/0/0/3/0/0/0).
Warning: This group was rejected because rewrite was not allowed. <== IT thinks the driver is updated to 2.27 which is not true, see next..

The following group of items will be processed at the same time:
  - rewrite rom from 05.06.06 to 5.06.06 for HP AH400A 8Gb Single Port PCIe Fibre Channel Adapter (0/0/0/9/0/0/0).
Warning: This group was rejected because rewrite was not allowed.
The following group of items will be processed at the same time:
  - rewrite efi from 02.27 to 2.27 for HP AH400A 8Gb Single Port PCIe Fibre Channel Adapter (0/0/0/9/0/0/0). <== This is true!!
  - rewrite bios from 03.13 to 3.13 for HP AH400A 8Gb Single Port PCIe Fibre Channel Adapter (0/0/0/9/0/0/0).
Warning: This group was rejected because rewrite was not allowed.
Nothing was done by this component.

>>How do I get the first card to use the new driver?

>>My first attempt has been to disconnect the driver then connect the new driver, but disconnect command is not functioning as described.

>>The Base OS is HPUX 11.31. There is no functional problem, but would like to get them both on the same driver. This is a Oracle RAC 2 node SG cluster.

[Matti_Kurkela · Accepted solution]

The Release Notes of the CP022831.scexe has this to say in the "Known Issues" portion:

Online firmware update may fail for newer Qlogic 8 GB FC cards with the error: "Error: ROM programming was unsuccessful".
Workaround: HP recommends updating these FC cards using the EFI bundle instead. The EFI bundle is available at http://www.hpe.com/support/hpesc; enter the card product name, select the Operating System “OS Independent”, then category "EFI".
Note: This issue exists in driver version FibrChanl-01 B.11.31.1503 or earlier and is fixed in driver version FibrChanl-01 B.11.31.1506.

The "EFI bundle" mentioned is apparently hp_qxx256xaf2.66risc5.06.06-1.zip. I got this by going to the URL mentioned in the quote above, typing "AH400A" as the product name, and then following the instructions in the quote.

The package includes the document "Efi\Efiutil.pdf" that describes the available options to efiutil.efi that performs the actual update. There is a "force" parameter that "allows user to forcefully update the driver or firmware even if flash has same driver or firmware version", which is apparently what would be needed here - and the update.nsh script included in the package appears to use that option by default.