FibrChanl-02 (fclp) B.11.31.1311 Fibre Channel Mass Storage Driver for HP-UX 11i v3 Release Notes

Table 14 HP-UX September 2009 Fixes
DescriptionDefect ID
There are no fixes in the 0909 release.N/A
Table 15 HP-UX June 2009 Fixes
DescriptionDefect ID
vgchange fails to activate volume groups under the fclp driverQXCR1000886720
Table 16 HP-UX March 2009 Fixes
DescriptionDefect ID
This fix delivers the concurrent dump functionality to the driver.QXCR1000772840
Table 17 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 18 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 this address:http://
docs.hp.com/en/T1335-90091/ar01s05.html
QXCR1000753480
NOTE: AR0803 (Version B.11.31.0803) 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.
VFC deletion time
While executing “hpvmstop command the time taken to delete a single Integrity VM VFC or
Flex FC VFC depends on total number of targets mapped to the VFC. Each target node port
deletion takes approximately 2 seconds. The greater the number of targets, the higher the
time taken for total target deletion.
Incorrect speed display
On a vPars and Integrity VM Guest with NPIV VFCs configured on FC adapters, FC Provider
enumeration of FC ports(NPIV VFC ports) will display “MaxSpeed”, “Speed” values as 0.
NOTE: This issue will be solved in future HP-UX vPars and Integrity VM release. Refer to
http://www.hp.com/go/hpux-hpvm-docs for more detail about the release.
Known problems and limitations 7