FibrChanl-01 (fcd) Fibre Channel Mass Storage Driver for HP-UX 11i v2 Release Notes (September 2009)

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:
1. Go to www.hp.com
2. Click Software & Driver Downloads.
3. In the white text box, type the name of the I/O card, such as A6826A.
4. Click the >> button.
5. Click the Cross Operating System button.
6. Look for EFI 1.49 for adapters A6826A, A9782A, A9784A, and AB465A. Look for EFI
1.05 for adapters AB378A and AB379A.
• Configuring an Alternate Path on the Same 2–Port HBA as the Primary Path
On midrange and high end Integrity servers, if the primary and alternate boot devices are
on the same Fibre Channel HBA port, an attempt to manually boot from the alternate device
will fail.
For example, if your primary and alternate paths are set as follows:
Primary bootpath:
0/0/10/1/0/4/0.8.0.255.0.7.0 Alternate bootpath: 0/0/10/1/0/4/0.8.0.255.0.0.0
This will set the primary and alternate bootpaths, but you will only be able to boot from the
primary path.
Corrective Action:The issue can be resolved by following one of the following scenarios:
1. From the EFI shell: Manually issue the EFI shell command reconnect —r, before
attempting to boot from the alternate path.
2. Online: Use the HP-UX setboot command to swap the primary and alternate boot
devices.
3. Hardware configuration: Reconfigure by moving the alternate boot device to a different
HBA.
• Using ioscan with krm Not Running
When ioscan is run with the —fn or —Fn option, and the kernel resource monitor (krm) is
not running, there could be stale krm device files in the system, which would correspond
to different devices, including fcd, in ioscan output. This issue has no impact on the
functionality of the Fibre Channel port; however, ioscan output may be confusing. This
issue can impact any card accessible with ioscan, and is not specific to the cards supported
by the fcd driver.
Corrective Action:The ioscan output can be returned to normal by either deleting the stale
krm device files, or by starting krm, which will recreate the device files.
Known Problems and Limitations 9