fibrchanl-01 (fcd) fibre channel mass storage driver for hp-ux 11i v3 release notes

FibrChanl-01 (fcd) Fibre Channel MassStorage Driver for HP-UX 11i v3 ReleaseNotesVersion Number B.11.31.1204

HP Part Number: 5900-2251Published: April 2012Edition: 1.0

ContentsFibrChanl-01 (fcd) Fibre Channel Mass Storage Driver for HP-UX 11i v3 overview..............................3New and changed features in this release...................................................................................3

New features......................................................................................................................3Changed features................................................................................................................3

Known problems fixed in this version...........................................................................................3Known problems and limitations.................................................................................................7Compatibility and installation requirements................................................................................11

Operating system and version compatibility...........................................................................11Requirements for Boot Support: 451871-B21, AH400A/AH401A, AD193A/AD194A,403619–B21, AD300A, AB378A, AB378B, AB379A, AB379B, A6826A. A9782A, A9784A,AB465A .....................................................................................................................11

Driver versions...................................................................................................................12Hardware requirements......................................................................................................13

Related information.................................................................................................................13Software availability in native languages...................................................................................13Documentation feedback.........................................................................................................13

2 Contents

This document provides information about the B.11.31.1204 release of the FibrChanl-01 (fcd)Fibre Channel Mass Storage Driver for HP-UX 11i v3.

FibrChanl-01 (fcd) Fibre Channel Mass Storage Driver for HP-UX 11i v3overview

This release of the document for the FibrChanl-01 (fcd) Fibre Channel Mass Storage Driver forHP-UX 11i v3 (version B.11.31.1204) documents version changes and defect fixes.

New and changed features in this release

New featuresThere are no new features in this release.

Changed featuresThe following feature is changed with the B.11.31.1204 version of the FibrChanl-01 (fcd) FibreChannel Mass Storage Driver for HP-UX 11i v3:• None.

Known problems fixed in this versionThe following issues have been fixed in the FibrChanl-01 (fcd) Fibre Channel Mass Storage Driverfor HP-UX 11i v3 April 2012 (WEB1204) release. To view the entire details of each issue fix, referto the HP IT Resource Center at: http://forums1.itrc.hp.com/service/forums/home.do

Table 1 HP-UX April 2012 (WEB1204) Fixes

DescriptionDefect ID

This fixes the issue where fcd device special files are not created automatically in some rare casesafter loading the fcd driver module dynamically.

QXCR1000945642

This fixes the fcd driver init script for the issue of HPVM guest boot delays caused when there ishigh number of stale IO nodes present.

QXCR1001198749

This modifies the fcd driver init script to remove the limitation of maximum 256 fcd device specificfiles that can be created at boot time.

QXCR1001201543

Table 2 HP-UX March 2012 (WEB1203) Fixes


Driver has been modified to handle FW timeout issue seen when ERASE command is issued totape drives. Maximum IO timeout value in driver has been increased from 0x1999 seconds to0xFFFF seconds to be in compliance with the change in Q-Logic ISP 24xx FW specification.

QXCR1001192329

Warning message is updated for FC Mezzanine configured in Loop Topology.QXCR1001196129

Table 3 HP-UX March 2012 (AR1203) Fixes


The fcd driver is modified to display port and node symbolic names for FlexFC ports.QXCR1001063170

This fixes an issue in the fcd driver which prevented link statistics from being retrieved using thefcmsutil stat command.

QXCR1001134924

This fixes the fcd driver to log an appropriate diagnostic message when a previously lost FCtarget device comes back online.

QXCR1001092583

FibrChanl-01 (fcd) Fibre Channel Mass Storage Driver for HP-UX 11i v3 overview 3

http://forums1.itrc.hp.com/service/forums/home.do

Table 3 HP-UX March 2012 (AR1203) Fixes (continued)


This fixes fcmsutil to print correct SFP information or print appropriate error message for thefcmsutil sfp command.

QXCR1001140465

Issue WARNING messages if FC Mezzanine is configured in loop.QXCR1001159905

Driver has been modified to handle the intermittent ioscan hangs seen in a bladed configurationwith Q-Logic FC cards due to infinite PLOGI retries to the Fabric Name Server. The PLOGI retrycount to the Name Server has been modified in the driver to a definite value.

QXCR1001169766

Table 4 HP-UX September 2011 (AR1109) Fixes


This fixes a memory leak in the fcd driver that occurs after concurrent execution of certain fcmsutildisable and ns_query_ports commands.

QXCR1001131764

fcmsutil output has been modified to display target symbolic port and node names as "None"when respective symbolic name values are not returned by the targets.

QXCR1001068587

Table 5 HP-UX May 2011 (WEB1105) Fixes


This fixes an issue in Qlogic 8Gb FC Firmware that enables it to use correct slot-specific SerDessettings for the 8Gb PCIe Dual Port Mezzanine Fibre Channel Adapter.

QXCR1001123656



SNIA: FC Instance Enumeration FCPortControllerCollection fails if port disabled.QXCR1001020559

SNIA: FC Provider dumps core during CHO test.QXCR1001073517

This fixes the issue where the fcd driver does not restore the Symbolic Names to their defaultvalues when requested through scsimgr.

QXCR1001051386

This fixes a memory leak in the fcd driver after executing certain fcmsutil echo, test, and rlscommands.

QXCR1001041080

This fixes a memory leak in the fcd driver after executing certain fcmsutil ns_query_ports commands.QXCR1001083355

This fixes the issue where the fcmsutil stat command is displaying the unneeded SBC hit counterstatistic for the 2Gb Fibre Channel Adapter.

QXCR1001060235

This fixes the issue where ioscan is displaying the wrong Part Number for the 4Gb Dual Port PCIeMezzanine Fibre Channel Adapter.

QXCR1001083067

Table 7 HP-UX September 2010 (AR1009) Fixes


This fixes the issue where rmsf can hang when trying to delete the stale device special file onthe FC port that is no longer available or waiting for a link-up. The rmsf hang can further causesubsequent hang in other commands (e.g. ioscan, olrad, network access).

QXCR1000984392

This fixes the issue where the timer list in the driver is corrupted, resulting in a panic withSpinlock held too long!!

QXCR1000924185

This fixes the issue where the fcmsutil utility returns the message Target port is ininvalid state, when the user specifies the N_Port_ID as a parameter.

QXCR1000815634

This fixes the issue where the fcd driver may panic with Bad News!, if the first open of the targetfailed because the link is down.

QXCR1001030695

4

Table 7 HP-UX September 2010 (AR1009) Fixes (continued)


This fixes the issue where the health state of the fcd instances in ioscan may incorrectly showthat it's online, even though the link is down.

QXCR1001024841

This fixes the issue where FC-4 type devices that have disappeared from the Name Server arenot logged in syslog.

QXCR1000990675

This fixes the issue where FCP targets are intermittently not being seen during boot, especiallyon a large SAN configuration.

QXCR1001008433

This fixes the fcmsutil's flash failure issue, due to the fcd driver misinterpreting a TAG field inthe Vital Product Data.

QXCR1001012664

SNIA does not provide speed for AH401A, so System Management Homepage (SMH) doesn'tdisplay speed for AH401A.

QXCR1001038471

Table 8 HP-UX May 2010 (WEB1005) Fixes


This fixes the issue where the fcmsutil fails to update the ROM firmware for the 4Gb or 8GbQlogic card if the ROM firmware version is 5 or greater.

QXCR1001021139

Table 9 HP-UX March 2010 (WEB1003) Fixes


This fixes an issue where the SNIA returns HBA_STATUS_ERROR for HBA_SendCTPassThruAPI call failure.

QXCR1000887704

This fixes a Serviceguard “safety timer” panic on a single-cpu vpar configuration, when thecommand fcmsutil_ns_query_port is executed.

QXCR1001007011

This fixes the issue in the fcd driver that can intermittently result in a mailbox timeout fatal error.QXCR1000994941

This fixes the significant drop in I/O performance encountered after installing FCD B.11.31.0903and later versions.

QXCR1001000800



There are no fixes for the AR1003 release.N/A

Table 11 HP-UX January 2010 (WEB1001) Fixes


This fixes the issue where the fcd driver corrupts the card's NVRAM content, due to the currentdriver logic, which computes and writes the checksum incorrectly under certain circumstances.

QXCR1000979379

The NVRAM corruption issue occurs only if the OS Boot Mode is set to [Windows/Linux/Other],which is the default (i.e., manufacturing) setting.

The fcd driver may cause a system panic with a data TLB fault. This problem, due to a potentialrace condition, where the fcd driver receives an I/O completion interrupt from the card, while itis still processing fatal errors, has been fixed.

QXCR1000991234

This fixes an issue where the fcd driver may panic during boot, when there is an 8 Gb MezzanineHBA configured in a blade server.

QXCR1000934838

This fixes the issue where SNIA does not report more than 500 luns per HBA.QXCR1000922032

Known problems fixed in this version 5

Table 11 HP-UX January 2010 (WEB1001) Fixes (continued)


fcd panics during system dump to an EMC device. This issue, caused by sense data handling,has been fixed.

QXCR1000976060

This fixes a system hang which occurred after CPU deletion. The hang was caused by interruptmigration handling in the fcd driver.

QXCR1000966390

Table 12 HP-UX September 2009 Fixes


This fixes an issue where the fcd startup script removed the volume group directory in /dev/fcd,followed by a number and vg name, such as /dev/fcd1dbvg03.

QXCR1000914828

This fixes the issue where fcd converted an Illegal Request into SCTL_INCOMPLETE. The fixresolves the DS2405 open () performance issue, as well as the DS2405 firmware update failureissue.

QXCR1000844402

Table 13 HP-UX March 2009 Fixes


In HP-UX 11i v3, when you disable the legacy device-special files, the SNIA APIHBA_GetFcpTargetMapping() fails to report the remote targets correctly. This problem has beenfixed in the SNIA vendor library for the fcd driver.

QXCR1000876391



There are no fixes for the September 2008 release.N/A

Table 15 HP-UX March 2008 Fixes


Added Symbolic Name support. Symbolic Names are user friendly names assigned to SANcomponents, and registered with the name server of an FC switch. FC switches display the

QXCR1000754446

registered symbolic names, which can be used by users to correlate SAN components acrossmultiple servers and storage.Display fcd controller symbolic port and node names from HP-UX:# /opt/fcms/bin/fcmsutil /dev/fcdl

fcd controller symbolic port and node names are displayed as N_Port Symbolic Port Nameand N_Port Symbolic Node Name.



Enable DLKM for 11.31SR: 8606477107

Support online transceiver diagnostics – sfpSR: 8606479804

Avoid use of /tmp file for driver dumpsSR: 8606477715

Modify FCD dump driver to support > 2TB LUNsSR: 8606466124

6

Known problems and limitationsThis section provides a list of known problems and limitations as known to HP at time of publication.If workarounds are available, they are included.

• Private Loop and Public Loop topology configuration support for Fibre Channel mezzanineadaptersPrivate Loop and Public Loop topology configurations are not supported for Fibre Channelmezzanine adapters on HP Integrity Blade servers in combination with the Fibre Channel (FC)Pass Thru I/O Interconnect modules. These configurations can result in servers losing connectionto the Storage Area Network (SAN) during mezzanine adapter initialization, and SAN bootmay fail in such configurations.It is strongly recommended that customers not use loop topology configurations for mezzanineadapters in conjunction with FC Pass Thru I/O interconnect modules. Customers are advisedto use Point-to-Point Fabric topology configuration with mezzanine adapters.For additional information, please refer to HP Customer Advisory Document c02985353.

• Adding a new path to a LUN seen through FibrChanl-01 (fcd) driver can cause IOs pendingwith the driver for the LUN to stop for R_A_TOV periodR_A_TOV stands for Resource Allocation Time Out Value (refer to FC-FS-3 21.3.5 for details).The default value of R_A_TOV is 10 seconds.On an 11iv3 host, when I/Os are in progress to a LUN and a new LUN path is added, themass storage stack issues a “abort-task-set” SCSI Task Management request on all existingpaths to the LUN. This causes the underlying FibrChanl-01 (fcd) driver to abort all I/Os to theLUN. The new path addition completes only after all the aborted I/Os and the SCSI TaskManagement request are returned by the underlying FibrChanl-01 (fcd) driver.In aborting an I/O that is active with a FC target device, the FibrChan-01 (fcd) driver mustwait for a period equal to the value of R_A_TOV before returning the I/O with aborted statusto the mass storage stack. This means the new path addition and subsequent retry of I/O isdelayed for a period equal to the value of R_A_TOV. This could result in applications thataccess the LUN experiencing I/O timeouts during new LUN path addition. Note that any I/Osthat are not active with the FC target are aborted immediately by the driver. To avoid aR_A_TOV delay and possible IO timeout scenarios it is necessary to ensure that there are noIOs pending to the LUN at the time of new LUN path addition. It may be necessary totemporarily suspend application(s) using the LUN in order to stop all IOs to LUN for the durationof the new LUN path addition.

• EFI boot fails when connected to an Arbitrated Loop deviceThis applies to HP 8Gb and 4Gb Dual Port QLogic Mezzanine HBAs (part numbers451871–B21 and 403619–B21). The solution is to set the HBA Connection Mode of theadapter port to Loop Preferred, Otherwise Point to Point, by using the drvcfg-s command at the EFI shell prompt:1. To view the QLogic driver handle information, type Shell> drivers at the EFI shell

prompt; a list of drivers is displayed.2. Write down the driver handle associated with the HP Fibre Channel Driver. The

first column, labeled DRV, lists the driver handles. There may be one or more driverinstances listed. Select the DRV corresponding to the adapter port connected to theArbitrated Loop device.

3. Enter the drvcfg <driver handle> command; for example, if the driver handle is20 (your driver handle may be different): Shell> drvcfg 20. Take note of the controllerhandle number inside the brackets, labeled as Ctlr[] .

4. Enter the drvcfg -s <driver handle> <controller handle> command. TheDriver Configuration Main Menu will be displayed.

Known problems and limitations 7

5. Under NVRAM Parameters section, press 1 to select Edit Adapter Settingsoption.

6. Press 7 to select the Connection Option.7. Press 3 to select Loop Preferred, Otherwise Point to Point option.8. Press 0 to go back to the previous menu.9. Under Main Menu, press 11 to write the changes to the NVRAM.10. Also under Main Menu, press 12 to quit and go back to the EFI shell.

NOTE: The HP-UX 11iv3 AR1203 FibrChanl-01 (fcd) driver will display a warning messageon detecting loop topology for HP 8Gb and 4Gb Dual Port Qlogic Mezzanine HBAs (partnumbers 451871–B21 and 403619–B21). Refer to HP customer advisory c02985353 fordetails.

• Some PCIe I/O backplanes do not support PCIe2 (5.0 GT/s) cards on slots 3 and 4PCIe I/O backplanes with product number AD295A #200 on rx3600, AD296A #200 onrx6600, and upgrade product number AD298A for both rx3600 and rx6600 Integrity servers,do not support PCIe2 (5.0 GT/s) cards on slots 3 and 4. PCIe2 cards will not be seen whenseated in these slots.PCIe I/O backplanes with the product numbers AD295A #300, AD296A #300, and AD230A,do support PCIe2 cards on slots 3 and 4. PCIe2 cards will be seen, and will run in PCIe mode(2.5 GT/s) when seated in these slots.Both backplanes will be able to support PCIe2 cards running in PCIe mode on slots 5 and 6.To determine the installed backplane using the FRU ID:1. Establish a telnet session with the iLO MP.2. Logon to the iLO MP using the Admin password.3. Type CM to enter the Command Menu.4. Type DF to enter the Display FRU Information Menu.5. Type S to display a list of specific FRUs.6. Type 05 for the I/O Assembly FRU.

◦ For AD295A #200, AD296A #200, and AD298A, the Product Name displays as:10 Slot PCI-E IOBP

◦ For AD295A #300, AD296A #300, and AD230A, the Product Name displays as:10 Slot PCI-E 1.1 IOBP

• If a system is low on available contiguous memory, an online addition can failThe failure will be seen with messages similar to the following:#sd10vp3 :/> olrad -A 8-0-1-5Activity : Start of Post AddTarget slot : 8-0-1-5

Addition of the card in progress...[ NOTE: Killing or otherwise aborting this olrad command may not cancel the Card Add operation. ]

H/W Path Class Description=====================================================5/0/6/0/0/0 slot PCI Slot5/0/6/0/0/0/0 fc PCIe SerialBus (10772532)

Error : ioscan failed! card not claimedTarget slot : 8-0-1-5

Error : On line ADD failed !! Attention LED may be left in blinking stateTarget slot : 8-0-1-5

-------------------------------------------------------

Additionally, syslog will contain messages similar to the following:

8

vmunix: FCD: Allocate shared memory failed, error code = -1vmunix: init of hardware not successful. id=10772532 and my_isc=2

Corrective action: Retry the operation at a time when the system has more free memoryavailable.

• DLKM infrastructure must be installedA complete Dyamically Loadable Kernel Module (DLKM) infrastructure is required forFibrChanl-01 B.11.31.0803. This requires that the following kernel patches be installed:

◦ PHKL_36387: MCA recovery/shutdown patch

◦ PHKL_36332: Cumulative GIO patch

◦ PHCO_36371: PCI OL* DLKM and Chassis DeleteThese patches and other required patches are delivered in the FEATURE11i patch bundleon the HP-UX 11i v3 (B.11.31) OEUR media for September 2007. You may also checkavailability of the patch at the HP IT Resource Center site: http://itrc.hp.com

• crashconf displays incorrect size for dump devicesFibrChanl-01 now supports dump devices that are greater than 2TB in size. However,crashconf displays an incorrect size for dump devices that are greater than 4TB.Corrective action: Install patch PHCO_36550 to fix this problem. This patch is delivered inthe HWEnable11i patch bundle on the HP-UX 11i v3 (B.11.31) OEUR media for December2007. You may also check availability of the patch at the HP IT Resource Center site: http://itrc.hpc.om

• Critical Resource Analysis (CRA) may unexpectedly failCritical Resource Analysis (CRA) may unexpectedly fail during Online Replacement (OLR),Online Deletion (OLD), or during dynamic unload of the fcd driver module, causing a coredump.OLR occurs when performing a replacement operation with the olrad command, PCI attentionbutton, or the System Management Homepage (SMH) on systems with this OLR feature.OLD occurs when performing a delete operation with the olrad command, or with the SystemsManagement Homepage (SMH) on systems with this OLD feature.A dynamic module unload can occur with kcmodule, swinstall, or swremove commands.If the CRA fails in this way during a swinstall or swremove operation, the system willautomatically reboot to complete the requested operation. If the CRA fails during a kcmodulefcd=unused operation, the unload action will not occur until the system is manually rebooted.Corrective action: Install patch PHCO_36356 to fix this problem. This patch is delivered inthe HWEnable11i patch bundle on the HP-UX 11i v3 (B.11.31) OEUR media for December2007. You may also check availability of the patch at the HP IT Resource Center site: http://itresourcecenter.hp.com

• Update to Software Distributor is requiredIf the updated or patched Software Distributor is not in place, a necessary reboot might notbe performed during installation of the I/O drivers with DLKM functionality, which includesthe FibrChanl-01 product.Corrective action: On systems prior to the HP-UX 11i v3 December 2007 OEUR, you mustinstall Software Distributor patch PHCO_36530, or install the B.11.31.0709.308 or laterrevision of the Software Distributor product from http://docs.hp.com/en/SD

• EFI SEARCH causes boot to fail on rx7640, rx8640, and sx2000 Superdome server systemsRunning the SEARCH command at the EFI shell on rx7640, rx8640, and HP IntegritySuperdome/SX2000 server systems can cause the system to fail to boot through a Fibre

Known problems and limitations 9

http://itrc.hp.com

http://itrc.hp.com

http://itrc.hp.com

http://itresourcecenter.hp.com


http://docs.hp.com/en/SD

Channel HBA. rx7640 systems have a built-in SEARCH of slot 7. Affected 2Gb Fibre ChannelHBAs 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.0failed: Not FoundCorrective action: A fix in the 2Gb/4Gb drivers has been released. The following steps willresolve the issue:1. Go to www.hp.com2. 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 or later for adapters A6826A, A9782A, A9784A, and AB465A. Look

for EFI 1.05 or later for adapters AB378A and AB379A.

• Configuring an alternate path on the same 2–Port HBA as the primary pathOn midrange and high end Integrity servers, if the primary and alternate boot devices are onthe same Fibre Channel HBA port, an attempt to manually boot from the alternate device willfail.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.0Alternate bootpath: 0/0/10/1/0/4/0.8.0.255.0.0.0This will set the primary and alternate bootpaths, but you will only be able to boot from theprimary 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 RunningWhen ioscan is run with the —fn or —Fn option, and the kernel resource monitor (krm) isnot running, there could be stale krm device files in the system, which would correspond todifferent devices, including fcd, in ioscan output. This issue has no impact on the functionalityof the Fibre Channel port; however, ioscan output may be confusing. This issue can impactany 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 stalekrm device files, or by starting krm, which will recreate the device files.

• swlist does not indicate the mezzanine HBAsswlist does not indicate the Mezzanine HBAs, and cannot be added onto because of stringsize limitation.Corrective action: Refer to Hardware Requirements later in this document for more information.

10

www.hp.com

Compatibility and installation requirementsThis section describes the compatibility information and installation requirements for this release.For specific installation instructions, refer to the installation guide specific to your FibreChannelcard.

Operating system and version compatibilityThe following software (or later versions) must be installed before installing the FibrChanl-01 (fcd)driver, version B.11.31.1204 into a system:

• PHCO_36371 (PCI OL* DLKM and Chassis Delete)

• PHKL_36332 (Cumulative GIO Patch)

• PHKL_36387 (MCA Recovery/Shutdown Patch)

• PHCO_36356 (Mass Storage Critical Resource Analysis)

• PHCO_36530 (Software Distributor Patch)

• HP-UX CommonIO 11.31 (B.11.31.0709 or later).

NOTE: The FC-COMMON.FC-SNIA fileset is part of the CommonIO bundle. IfFC-COMMON.FC-SNIA (B.11.31.0709 or later) is not present on a system, swinstall oftheFC-FCD product will display errors. If you ignore the errors and proceed with theswinstall, the FC-FCD.FC-FCD-RUN fileset will not be installed.

Driver bundles can be downloaded from the HP Software Depot at: http://www.software.hp.comPatches are available from either: http://www.software.hp.com or http://itresourcecenter.hp.comOnlineDiag is available at http://www.software.hp.com in the Enhancement releases and patchbundles section, or on the HP-UX 11i v3 OE media (December 2004 and later).

Requirements for Boot Support: 451871-B21, AH400A/AH401A, AD193A/AD194A,403619–B21, AD300A, AB378A, AB378B, AB379A, AB379B, A6826A. A9782A, A9784A,AB465A

To boot through the fibre channel ports on these adapters, HP recommends that you update theEFI driver and onboard firmware to the latest version. The following table lists the recommendedEFI and firmware versions at the release of FibrChanl-01 (fcd) driver, version B.11.31.1204:

Table 17 Recommended firmware versions (September 2011)

Firmware versionEFI driver versionFibre channel adapter

5.03.02 or later2.20 or later451871-B21

5.03.02 or later2.20 or laterAH400A/AH401A

5.03.02 or later2.20 or laterAD193A/AD194A

5.03.02 or later2.20 or later403619-B21

5.03.02 or later2.20 or later403619-B21 (with VC-FC boot 2.15or later 4.04.04 or later support inBL860c)

5.03.02 or later2.20 or laterAD300A

4.04.04 or later2.15 or laterAB378A

5.03.02 or later2.20 or laterAB378B


5.03.02 or later2.20 or laterAB379B

Compatibility and installation requirements 11

http://www.software.hp.com




Table 17 Recommended firmware versions (September 2011) (continued)

Firmware versionEFI driver versionFibre channel adapter

3.03.154 or later1.49 or laterA6826A




For current recommended firmware versions, see the HP-UX Fibre Channel (fcd and fclp) Host BusAdapter Support Matrix at http://www.hp.com/go/hpux-iocards-docs .

NOTE: Display EFI driver and ROM firmware versions using fcmsutil <fcd_device_file>vpd

EFI/firmware bundles can be downloaded from www.hp.com, in the Software and Driver Downloadssection.

Driver versionsThe following table lists all the driver versions of the fcd driver on HP-UX 11i v3 with their associatedrelease names and dates.

Table 18 Table of Driver Versions

Release DateDriver VersionRelease Name

February 2007B.11.31Initial 11.31 Support

September 2007B.11.31.0709Application Release 0709

March 2008B.11.31.0803Application Release 0803





March 2010B.11.31.1003.01Web Release 1003

May 2010B.11.31.1005Web Release 1005



May 2011B.11.31.1105Web Release 1105

September 2011B.11.31.1109.01Application Release 1109


March 2012B.11.31.1203.01Web Release 1203

April 2012B.11.31.1204Web Release 1204

12

http://www.hp.com/go/hpux-iocards-docs

www.hp.com

Hardware requirementsThis version of the FibrChanl-01 (fcd) Fibre Channel Mass Storage Driver for HP-UX 11i v3 runson HP Integrity servers and HP PA servers with the HP-UX 11i v3 (11.31) operating system. Itsupports Fibre Channel hardware products such as:

• 451871-B21 Dual Port PCIe 8 Gb Mezzanine Fibre Channel Adapter

• AH401A Dual Port PCIe 8Gb Fibre Channel Adapter

• AH400A Single Port PCIe 8Gb Fibre Channel Adapter

• AD193A/AD194A PCI-X 4Gb FC and 1000BT Combination Card

• 403619-B21 PCIe Dual Port Mezzanine Fibre Channel Adapter

• AD300A PCIe Dual Port 4Gb Fibre Channel Adapter

• AB378B PCI-X Single Port 4Gb Fibre Channel Adapter

• AB379B PCI-X Dual Port 4Gb Fibre Channel Adapter

• AB378A PCI-X Single Port 4Gb Fibre Channel Adapter

• AB379A PCI-X Dual Port 4Gb Fibre Channel Adapter

• AB6826A PCI-X Dual Port 2 Gb/1 Gb Fibre Channel Adapter

• A9782A PCI-X 2Gb Fibre Channel and 1000Base-SX (Fiber) Gigabit Ethernet CombinationCard

• A9784A PCI-X 2Gb Fibre Channel and 1000Base-T (Copper) Gigabit Ethernet CombinationCard

• AB465A PCI-X Dual Port 2Gb Fibre Channel and Dual Port 1000Base-T Gigabit EthernetCombination Card

Related informationThe latest documentation for the FibrChanl-01 (fcd) Fibre Channel Mass Storage Driver for HP-UX11i v3 is available at http://www.hp.com/go/hpux-iocards-docs, under the HP Fibre ChannelHost Bus Adapters section. Available documents include:

• Support Guide: includes an adapter overview, installation details, adapter configuration,troubleshooting and maintenance information, additional features, and regulatory information.

• Installation Guide: includes software and hardware installation information for specific HBAs.

• Support Matrix: includes a matrix of Fibre Channel adapters, supported hardware platforms,operating systems, driver bundle versions, and minimum PDC/firmware requirements.

• White Paper: white papers can also be found in this section.

Software availability in native languagesThis product is available only in the English language.

Documentation feedbackHP is committed to providing documentation that meets your needs. To help us improve thedocumentation, send any errors, suggestions, or comments to Documentation Feedback([email protected]). Include the document title and part number, version number, or the URLwhen submitting your feedback.

Related information 13

http://www.hp.com/go/hpux-iocards-docs

mailto:[email protected]

fibrchanl-01 (fcd) fibre channel mass storage driver for hp-ux 11i v3 release notes

Documents

resource center site

2gb fibre channel

part numbers 451871b21

hwenable11i patch bundle

fixesdefect id description

arbitrated loop device

pci ol dlkm

system management homepage