Chapter 1
Fibre-Channel Component Firmware Releases

These release notes contain information about the latest software distribution of source files to create firmware on the FC Host Adapters, FC Switches, and FC Bridges. Read these notes before installing any new software and downloading it to firmware. This information does not appear elsewhere in the system documentation.

Table 1-1, "Best Recipe" FC-Firmware Release Sets for DYNIX/ptx V4.4.x Systems," provides a summary listing of the latest firmware recipes qualified for individual operating systems.


1.1 For the DYNIX/ptx V4.4.8, V4.4.9, and V4.4.10 Operating Systems

The following FC software is distributed as individual packages on Volume 1 of the Operating System CD-ROMs:

As of this publication, the FC software listed above is available on one of the following CD-ROMs:


1.2 For Static Hardware Partitioning on DYNIX/ptx V4.4.4, V4.4.6, and V4.4.7 Operating Systems


ATTENTION

At the release of this document, static hardware partitioning is implemented by IBM Professional Services personnel only. That includes any activities involving Fibre Channel Switch Zoning and Static Hardware Partitioning.


Static Hardware Partitioning is a hardware connection scheme that allows a single node with several quads to be physically divided by cabling into separate partitions that each run their own instance of different operating systems. Each partition is also connected to its own SAN FC resource domain. For physical configuration details, see Chapter 7 of the Quad Installation and Service document.

Whenever DYNIX/ptx V4.4.4, V4.4.6, or V4.4.7 is running on a partition of a node, that partition and its SAN FC components must be set up with the FC firmware release-set combination that was qualified in static hardware partitioning testing. See Table 1-1.

Obtain the necessary release-set software from the CD-ROM labeled "Fibre Channel Software for DYNIX/ptx V4.4.4, V4.4.6, and V4.4.7". This CD contains the following software:


ATTENTION

OEM-supplied software versions FF2.20 for LP6000 and SF2.20 for LP7000 FC Host Adapters are also included on the distribution CD. However, they are not required for static hardware partitioning. These versions are supplied for service purposes only and should not be installed or downloaded without authorization by IBM Beaverton Customer Support.



1.3 Firmware Release Sets

Versions of firmware for the FC Host Adapter, FC Switch, and FC Bridge are normally released as a proofed set that has been tested with the newest version of the DYNIX/ptx operating system (OS). Occasionally, a release set must be upgraded with a change to a particular FC component or an operating-system component. These changes often correct a serious problem, enable newly qualified features, or support newly qualified hardware.

When a component of the release set is upgraded to fix a serious problem, the table listings are adjusted to show a later version number than the original release.

The following table lists the best firmware combinations that should be used together with the several releases of the DYNIX/ptx V4.4.x operating systems. When a component is upgraded and regression tested for compatibility with earlier releases of the operating system, the table listings are adjusted to show a later version number than the original release set. For the DYNIX/ptx V4.4.x family of operating systems, Table 1-1 lists the recommended firmware combinations that should be used.


ATTENTION

Do not mix firmware from different release sets. Unpredictable behavior may result.

For upgrading capability only, components of a release set are regression tested for compatibility with the last operating system that was deemed a mandatory upgrade.


If a replacement or expansion FC component has a different release-set firmware version level than the other FC components with which it will be working, it must be changed to be compatible with that release set. If possible, the whole system should be upgraded to the latest release set to take advantage of new features and fixes for old problems.

Table 1-1. "Best Recipe" FC-Firmware Release Sets for DYNIX/ptx V4.4.x Systems

Release Set

DYNIX/ptx Version

FC Host Adapter Firmware

FC Switch Firmware

FC Bridge Firmware

December 2001

V4.4.10

SF3.22a0a

FF2.30b

a2.2.1acd

V1.6c3e

V1.5.5

June 2001

V4.4.9

SF3.22a0

FF2.30

a2.2.1a

V1.6c3

V1.5.5

August 2000f

V4.4.8

SF3.22a0

FF2.30

a2.2.1a

V1.6c3

V1.5.5

August 2000f

V4.4.7

SF3.22a0

SF2.23g

FF2.30h

a2.2.1a

V2.1.3g

V1.6c3h

V1.5.5

V1.5.3g

August 2000f

V4.4.6

SF2.20

SF2.23g

FF2.30h

V2.0.3ag

V1.6c3h

V1.5.3g

October 1998

V4.4.4

SF2.20

SF2.23g

FF2.30g

FF2.12X1b

V2.0.3a

V2.1.3g

V1.6c3h

V1.5.2

V1.5.3g

August 1998

V4.4.2

SF2.20

FF2.12X1i

V2.0.3a

V1.6c3

V1.5.2j

V1.4.3k


a. For LP7000E (V4) type only.

b. For LP6000 (V3 and V2) type only.

c. For IBM 2109 and SilkWorm 2000 models only.

d. Always reported by DYNIX/ptx utilities as "V2.2.1."

e. For SilkWorm 1000 models only.

f. Redlight 465 mandatory upgrade to FC Host Adapter Firmware FF2.30.

g. Required when static hardware partitioning is deployed. Part of the only tested recipe for this OS version.

h. Also supports static hardware partitioning. Part of the only tested recipe for this OS version.

i. Mandatory upgrade from FF1.11. Requires OS patch Base_V4.4.2.4 and ptx/SPDRIVERS V2.1.0.1.

j. When connected to an IBM 2109 or a SilkWorm 2000 FC Switch.

k. When connected to a SilkWorm 1000 FC Switch.


1.4 System-Level Upgrade Sequence

When upgrading the whole system software stack to a new release level, the optimal order for the Fibre Channel subsystem components is different for single versus clustered xSeries 430 or IBM NUMA-Q servers:


ATTENTION

Always upgrade the operating system and layered-products software first to ensure that the latest FC Driver, FC software source files, and FC downloading utilities are in place before upgrading the firmware on any FC device.



1.4.1 Single-Node Upgrade Sequence

Upgrade system software and firmware in the following order:

  1. DYNIX/ptx operating system and essential layered products, including ptx/SPDRIVERS.

    To allow the customer access to the system as long as possible, the OS upgrade is normally performed from the multi-user level, using an alternate-disk installation method. Detailed procedures for upgrading the operating system and loading newly-distributed FC-software files can be found in the DYNIX/ptx V4.4.10 and Layered Products Software Installation Release Notes.

  2. VCS upgrade while the OS is shutdown. Detailed procedures for upgrading the VCS can be found in the Console Software Release Notes.

  3. Remaining layered products and online diagnostics from the single-user level.

  4. FC Bridge firmware from the single-user level.

  5. FC Switch firmware from the single-user level.

  6. FC Host Adapter firmware from the single-user level.

  7. OS installation clean-up and remirroring.


1.4.2 Clustered Nodes Upgrade Sequence

For a rolling upgrade of the system software stacks of clustered nodes and the firmware of the shared Fibre-Channel components, a special procedure is provided in the Clusters Rolling Upgrade to OS V4.4.10 Release Notes.

For a non-rolling upgrade of clustered nodes, use single-node methods in the following sequence to upgrade system software and FC firmware:

  1. From the multi-user level, upgrade the DYNIX/ptx operating system and layered products, including ptx/SPDRIVERS, on each node, using an alternate-disk installation method. Detailed procedures for upgrading the operating system and loading newly-distributed FC-software files can be found in the DYNIX/ptx V4.4.10 and Layered Products Software Installation Release Notes.

  2. Bring all nodes to the shutdown level, but do not reboot them.

  3. From the shutdown level of each node, install new VCS software and boot each node to the single-user level. Detailed procedures for upgrading the VCS can be found in the Console Software Release Notes.

  4. Install any remaining layered products, plus online diagnostics.

  5. A boot to single-user level will leave all shareable devices in the new naming database with temporary names. Make the names permanent at this time with the devctl -A command.

  6. From the single-user level of the first node, upgrade the firmware on all shared FC Bridges and also all unshared FC Bridges that may be connected to the first node only.

  7. From the single-user level of the first node, upgrade the firmware on all FC Switches in the dual fabrics.

  8. From the single-user level of the first node, upgrade the firmware on all of its FC Host Adapters.

  9. If there are any unshared FC Bridges on the next node, upgrade that firmware from the single-user level.

  10. From the single-user level of the next node, upgrade the firmware on all of its FC Host Adapters.

  11. Repeat the unshared FC Bridge and FC Host Adapter steps for all remaining nodes.

  12. On each node, from the single-user level, perform OS-installation clean-up and remirroring

  13. Reboot each node to multiuser and verify that the cluster is reformed.


1.5 Related Documentation

The following documentation is available on the online documentation CD or at http://webdocs.numaq.ibm.com/ :