FibrChanl-01 (fcd) B.11.23.0809 Fibre Channel Mass Storage Driver Release Notes, Edition 3.0 (September 2008)

Table 11 HP-UX 11i v2 September 2004 Fixes (continued)
DescriptionDefect ID
Online Adapter ROM update command hangsSR: 8606353003
File descriptor leak in SNIA API for TargetMapping and PersistentBindingSR: 8606364880
SNIA HBA API functions may return HBA_STATUS_ERROR_UNAVAILABLE for correctly
installed HBAs; SNIA HBA API function HBA_SendCTPassThru() may hang
SR: 8606358270
Ioscan problems with FCP array using Peripheral Device Addressing lun addressing method.SR: 8606360197
VxVM DMP interoperability problemSR: 8606368844
FCP-2 error recovery doesn't occur following a short cable breakSR: 8606369477
Driver Versions
The driver versions for each release of the FibrChanl-01 (fcd) driver:
Table 12 FibrChanl-01 (fcd) Driver Version History
RevisionRelease
B.11.23.0809September 2008
B.11.23.0807July 2008
B.11.23.0803March 2008
B.11.23.08.02December 2007
B.11.23.08.01September 2007
B.11.23.08April 2007
B.11.23.07December 2006
B.11.23.06September 2006
B.11.23.05 (64-bit)June 2006
B.11.23.04.01 (64-bit)December 2005
B.11.23.03 (64-bit)March 2005
B.11.23.02 (64-bit)September 2004
Known Problems and Limitations
This section provides a list of known problems and limitations as known to HP at time of
publication. If workarounds are available, they are included.
EFI SEARCH Causes Boot to Fail on rx7640, rx8640, and sx2000 Superdome Server Systems
Running the SEARCH command at the EFI shell on rx7640, rx8640, and HP Integrity
Superdome/SX2000 server systems can cause the system to fail to boot through a Fibre
Channel HBA. rx7640 systems have a built-in SEARCH of slot 7. Affected 2Gb Fibre Channel
HBAs are: A6826A, A9782A, A9784A, and AB465A with EFI driver version 1.47 or earlier.
Affected 4Gb Fibre Channel HBAs are: AB378A and AB379A with EFI driver version 1.01.
The boot will fail with a message similar to the following:
Load of HP-UX
Primary Boot: 1.0.1/1/0/4/0.8.0.255.0.6.0 failed: Not Found
Corrective Action: A fix in the 2Gb/4Gb drivers has been released. The following steps will
resolve the issue:
8