FibrChanl-02 (fclp) B.11.31.1003.02 Fibre Channel Mass Storage Driver Release Notes, Edition 2.0 (March 2010)

Table 4 HP-UX September 2009 Fixes
DescriptionDefect ID
There are no fixes in the 0909 release.N/A
Table 5 HP-UX June 2009 Fixes
DescriptionDefect ID
vgchange fails to activate volume groups under the fclp driver
QXCR1000886720
Table 6 HP-UX March 2009 Fixes
DescriptionDefect ID
This fix delivers the concurrent dump functionality to the driver.QXCR1000772840
Table 7 HP-UX December 2008 Fixes
DescriptionDefect ID
The fix delivers the SNIA API HBA_GetFcpTargetMappingV2(), which is used to oormation
about the targets mapped through a port on a multiport Fibre Channel card.btain inf
QXCR1000867632
vPars boot panic with AD222 HBA has been fixed.QXCR1000841117
System panic due to spinlock being held too long in a tracing loop has been fixed.QXCR1000869847
The case where the fclp driver did not recognize a device with a loop ID of zero on a private
loop has been fixed.
QXCR1000886304
Table 8 HP-UX September 2008 Fixes
DescriptionDefect ID
Fixed an issue which caused system dump failure to an fclp attached device, if base page size
was set to a value other than 4 KB.
QXCR1000799018
Long hardware path from AD221A (PCIe 1 port 4Gb FC and 1 port GigE HBA) card not
recognized by vparmodify. The workaround for this issue is located at the following
address:http://docs.hp.com/en/T1335-90091/ar01s05.html
QXCR1000753480
NOTE: AR0803 was the initial release of FibrChanl-02 (fclp) on HP-UX 11i v3.
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.
• A voltage degradation alert message is shown in the System Events Logs upon system
boot up
This is only an alert message for the 456972-B21 HBA. Functionality and performance on
the Mezzanine card are not adversely affected. No actions are needed. This message can
only be found through the SL command under the MP menu.
• EFI is only bootable from the first boot entry device
This applies to the first boot entry device that is connected to an AD221, AD222A, AD393A,
AD299A, or AD355A.
Corrective action: The workaround for this issue is to re-arrange the boot list that is connected
to the adapters:
6