FibrChanl-03 (fcoc) B.11.31.1109.02 Fibre Channel Mass Storage Driver for HP-UX 11i v3 Release Notes

Table 2 HP-UX September 2011 (AR1109) Fixes (continued)

DescriptionDefect ID

For the FlexFabric Adapter NC551m (580151-B21), the minimum firmware version required to

access this fix is 2.704.322.0.

Table 3 HP-UX March 2011 (WEB1103) Fixes

DescriptionDefect ID

This release fixes a problem in which when a port is disabled, SNIA does not display any port

or adapter attributes for other enabled ports.

QXCR1001070913

Table 4 HP-UX March 2011 (AR1103) Fixes

DescriptionDefect ID

This is the first general release.N/A

Table 5 HP-UX November 2010 (WEB1011) Fixes

DescriptionDefect ID

There are no known problems fixed in this version.N/A

NOTE: WEB1011 is the initial controlled availability release of FibrChanl-03 (fcoc) 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.

• Up to a total of eight NC551m and/or NC553m HBAs are supported in a BL890c i2 system.

Up to a total of 140 Fibre Channel ports, which can be any combination of CN1100E and

AT094A HBAs, are supported in a Superdome2 system.

• The HP-UX boot path is lost during un-assign and re-assign of the BL8x0C i2 (Blade) profile.

The scenario that leads to this is:

1. Create a profile and assign it to the blade. Install a SAN disk connected from HBA with

HP-UX on it.

2. Power off the blade.

3. Un-assign the profile from the blade.

4. Power on the blade to EFI shell (bare-metal state).

5. Power off the blade.

6. Re-assign the profile back to the same blade.

7. Power on the blade again.

At this point, the blade should be booted from HP-UX and be up and running. However, the

blade remains in Ignite-UX and waits to be re-installed again.

NOTE: In order to reproduce the problem, a power cycle is necessary between the un-assign

and re-assign profile steps. Without the power cycle between the un-assign and re-assign

profile, the problem does not occur.

• To enable booting through the fcoc driver, there are several steps that needed to be performed.

They involve invoking the Emulex Configuration Utility at the EFI level. These steps need to be

performed only once. They need to be done regardless of the VCM profile settings.

To start the Emulex Configuration Utility via the Human Interface Infrastructure (HII):