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

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.
• Increased Boot Time with Unconnected fcd HBA Ports
System boot time will be increased if there are unconnected fcd HBA ports (i.e., HBA ports
controlled by the fcd driver).
This happens because an ioscan is performed as a part of the boot process for HP-UX .
When an ioscan is performed for the first time for an fcd HBA port, the fcd driver waits
for 21 seconds before declaring the port offline.
This is only an issue during boot, because at boot time the HBA ports are scanned
sequentially. After boot, the HBA ports are scanned in parallel, using kernel threads.
The delay observed during boot will be around N*21 seconds, where N is the number of
unconnected fcd HBA ports.
Corrective Action:Two workarounds are available for this issue:
Known Problems and Limitations 9