Power6 Entry Systems Firmware
Applies to: 8204-E8A, 8203-E4A, 8261-E4S, 9407-M15,
9408-M25
and 9409-M50
This document provides information about the installation of
Licensed
Machine or Licensed Internal Code, which is sometimes referred to
generically
as microcode or firmware.
Contents
1.0 Systems Affected
This package provides firmware for System p 550 (8204-E8A), System p
520
(8203-E4A), 8261-E4S, System i 550 (8204-E8A), System i 520
(8203-E4A), System i 515 (9407-M15), System i 525 (9408-M25),
System i 550 (9409-M50), Power 520 and Power 550 servers
only.
The firmware level in this package is:
This level of firmware is required on systems not managed by an HMC.
1.1 Minimum HMC Code Level
This section is intended to describe the "Minimum HMC Code Level"
required by the System Firmware to complete the firmware installation
process. When installing the System Firmware, the HMC level must be
equal to or higher than the "Minimum HMC Code Level" before starting
the system firmware update. If the HMC managing the server
targeted for the System Firmware update is running a code level lower
than the "Minimum HMC
Code Level" the firmware update will not proceed.
The Minimum HMC Code level for
this firmware is: HMC V7 R3.5.0
Service Pack 1 ( PTF
MH01212) and
MH01217.
Although the Minimum HMC Code level for this firmware is listed
above, HMC level V7 R3.5.0 with PTF MH01277
(Service Pack 4), or
higher is
suggested for
this
firmware level.
For specific fix level information on key components of IBM
Power
Systems running the AIX, IBM i and Linux operating systems, we suggest
using the Fix Level Recommendation Tool (FLRT):
http://www14.software.ibm.com/webapp/set2/flrt/home
For information concerning HMC releases and the latest PTFs,
go
to the following URL to access Fix Central.
http://www-933.ibm.com/support/fixcentral/
NOTE: You must be logged in as hscroot in order for the
firmware
installation to complete correctly.
1.2 Minimum SDMC Code
Level
This section is intended to describe the "Minimum Systems Director
Management Console (SDMC) Code Level"
required by the System Firmware to complete the firmware installation
process. When installing the System Firmware, the SDMC level must be
equal to or higher than the "Minimum SDMC Code Level" before starting
the system firmware update. If the SDMC managing the server
targeted for the System Firmware update is running a code level lower
than the "Minimum SDMC
Code Level" the firmware update will not proceed.
The Minimum SDMC Code level for
this firmware is: SDMC V6
R7.3.0 with Mandatory PTF MF53082.
Although the Minimum SDMC Code level for this firmware is listed
above, SDMC level V6 R7.3.0 with PTF MF55966
(SDMC_Update_6.730.3/Service Pack 3), or
higher is
suggested for
this
firmware level.
For information concerning SDMC releases and the latest PTFs,
go
to the following URL to access Fix Central:
http://www-933.ibm.com/support/fixcentral/
For specific fix level
information on key components of IBM
Power Systems running the AIX, IBM i and Linux operating systems, we
suggest using the Fix Level Recommendation Tool (FLRT):
http://www14.software.ibm.com/webapp/set2/flrt/home
2.0 Cautions
and Important
Information
2.1 Cautions
Downgrading firmware from any
given release level to an earlier release level is not recommended.
If you feel that it is
necessary to downgrade the firmware on
your system to an earlier release level, please contact your next level
of support.
This level of firmware is required on systems not managed by an HMC
or SDMC
For model 8203-E4A, 8261-E4S, 9407-M15, 9408-M25 systems, and 8204-E8A,
9409-M50 systems, that are not managed by an HMC, this is the required
level of EL350 firmware. This level contains a fix for the system
ports (integrated serial ports) that are not functional in
EL350_038.
ASCII terminals, modems, and the call home function are functional in
this
level.
Upgrading from EL320_031 to EL350_xxx
For 8204-E8A systems only: If your current level of firmware is
EL320_031 you must install any higher level of EL320 before upgrading
your
firmware to this level.
Service Processor flash memory errors (8204-E8A and 9409-M50
systems
running EL320_093 and earlier, or EL340_101 and
earlier only)
IBM strongly recommends updating to System Firmware level EL350_039 or
later as this firmware provides improved reliability to the 8204-E8A
and
9409-M50 servers. One enhancement prevents accumulation of single bit
errors
in the memory used to store System Firmware by periodically correcting
single bit errors automatically. If a significant number of such errors
were to accumulate, the server may not boot successfully after main
power
is lost or removed. We strongly recommend customers update both the
Temporary
and Permanent copies of System Firmware when performing this upgrade.
Updating
both the Temporary and Permanent copies allows both memory areas to be
corrected. It is critical the System Firmware update uses one of the
two
methods listed below. Updating System Firmware from the operating
system
may not correct all existing single bit errors.
Note: Do not remove main power from the server before updating the
System
Firmware.
For servers that are not managed by an HMC or SDMC
Update the System Firmware using a USB flash drive. This method will
update both the Temporary and Permanent copies of the System Firmware.
For instructions on this method of install, please use the following
link:
http://publib.boulder.ibm.com/infocenter/systems/scope/hw/index.jsp?topic=/ipha5/fix_firm_usb.htm
For servers that are HMC-managed
Note: A normal accept
operation to copy the Temporary side
contents to the Permanent side cannot be used in place of these
instructions. The update must be done using the following method
(or its command line equivalent).
IMPORTANT: Note that even if the update you are installing is
categorized as being concurrent, use of the Advanced Features option
will power off the system during this procedure.
If you are installing an update to a level within the same release (ex.
340_xxx to 340_yyy)
1) Power off the managed system.
2) Using the HMC GUI interface, click on "Updates" in the navigation
(left-hand) pane. Click in the
checkbox beside the Managed System.
a) Click on "Change Licensed Internal Code for the current release".
b) Select "Start Change Licensed Internal Code wizard" and click "OK"
c) After clicking "OK" on the readiness check panel, select the
repository where the firmware files
can be found and click "OK".
d) Click on "Next" to step through the wizard panels. Accept the
license agreement when it is
displayed, and then click "Finish" to start the update.
f) When the update completes, click on "Change Licensed Internal Code
for the current release"
g) Select "Advanced Features" and click "OK".
h) Select "Install and Activate" and click "OK".
i) After clicking "OK" on the readiness check panel, select the
repository where the firmware files
can be found and click "OK".
j) Select "Specific Levels" and click "OK".
k) Select the managed system, then select "Change Levels".
l) Select the same level chosen in step c and click "OK" and then
click "OK" again on the next panel.
m) On the "Select Installation Type" panel, ensure that the "Disruptive
install and activate" radio button is selected and click "OK".
n) Accept the license agreement when it is displayed, and then click
"OK " in the confirmation panels to start the update.
o) When the process completes, the Managed System may be powered on.
If you are installing an upgrade to a new release (ex 320_xxx to 340 or
350_xxx)
1) Power off the Managed System
2) Using the HMC GUI interface, click on "Updates" in the navigation
(left-hand) pane. Click in the
checkbox beside the Managed System.
a) Click on "Change Licensed Internal Code to a new release".
b) After clicking "OK" on the readiness check panel, select the
repository where the firmware files
can be found and click "OK". Select the new firmware level from
the selection panel displayed and click "OK".
c) Accept the license agreement and click on "OK" in the confirmation
panels to start the upgrade.
f) When the upgrade completes, both the Activate and Accepted levels
will reflect the level just installed. To effect a complete overwrite
of both sides of the Service Processor, you must continue with this
procedure.
g) Click on " Change Licensed Internal Code for the current release".
h) Select "Advanced Features" and click "OK".
i) Select "Install and Activate" and click "OK".
j) After clicking "OK" on the readiness check panel, select the
repository where the firmware files
can be found and click "OK".
k) Select "Specific Levels" and click "OK".
l) Select the managed system, then select "Change Levels".
m) Select the same level chosen in step b and click "OK" and then
click "OK" again.
n) On the "Select Installation Type" panel, ensure that the "Disruptive
install and activate" radio button is selected and click "OK".
o) Accept the license agreement when it is displayed, and then click
"OK " twice to confirm the action.
p) When the process completes, the Managed System may be powered on.
2.2 Important Information
IPv6 Support and Limitations
IPv6 (Internet Protocol version 6) is supported in the System
Management
Services (SMS) in this level of system firmware. There are several
limitations
that should be considered.
When configuring a network interface card (NIC) for remote IPL, only
the most recently configured protocol (IPv4 or IPv6) is retained. For
example,
if the network interface card was previously configured with IPv4
information
and is now being configured with IPv6 information, the IPv4
configuration
information is discarded.
A single network interface card may only be chosen once for the boot
device list. In other words, the interface cannot be configured for the
IPv6 protocol and for the IPv4 protocol at the same time.
Concurrent Firmware Updates
Concurrent system firmware update is only supported on HMC or SDMC -
Managed
Systems
only.
Memory Considerations for Firmware Upgrades
The increase in memory used by the firmware is due to the additional
functionality
in later firmware releases.
3.0 Firmware
Information
and Description
Use the following examples as a reference to determine whether your
installation
will be concurrent or disruptive.
For systems that are not managed by an HMC or SDMC, the installation
of
system
firmware is always disruptive.
Note: The concurrent levels
of system firmware may, on occasion,
contain
fixes that are known as Deferred and/or Partition-Deferred. Deferred
fixes can be installed
concurrently, but will not be activated until the next IPL.
Partition-Deferred fixes can be installed concurrently, but will not be
activated until a partition reactivate is performed. Deferred
and/or Partition-Deferred
fixes,
if any, will be identified in the "Firmware Update Descriptions" table
of this document. For these types of fixes (Deferred and/or
Partition-Deferred) within a service pack, only the
fixes
in the service pack which cannot be concurrently activated are
deferred.
Note: The file names and service pack levels used in the
following
examples are for clarification only, and are not
necessarily levels that have been, or will be released.
System firmware file naming convention:
01ELXXX_YYY_ZZZ
- XXX is the release level
- YYY is the service pack level
- ZZZ is the last disruptive service pack level
NOTE: Values of service pack and last disruptive service pack
level
(YYY and ZZZ) are only unique within a release level (XXX). For
example,
01EL320_067_045 and 01EL340_067_053 are different service
packs.
An installation is disruptive if:
- The release levels (XXX) are different.
Example: Currently installed release is EL320, new release is EL340
- The service pack level (YYY) and the last disruptive
service
pack level (ZZZ) are the same.
Example: EL320_120_120 is disruptive, no matter what level of EL320 is
currently
installed on the system
- The service pack level (YYY) currently installed on the
system
is
lower than the last disruptive service pack level (ZZZ) of the service
pack to be installed.
Example: Currently installed service pack is EL320_120_120 and
new service pack is EL320_152_130
An installation is concurrent if:
The release level (XXX) is the same, and
The service pack level (YYY) currently installed on the system
is the same or higher than the last disruptive service pack level (ZZZ)
of the service pack to be installed.
Example: Currently installed service pack is EL320_126_120,
new service pack is EL320_143_120.
Firmware Information and Update Description
For information about previous firmware release levels, see Section
7.0 Firmware History.
Filename |
Size |
Checksum |
01EL350_149_038.rpm |
24806576
|
06523
|
Note: The Checksum can be found by running the AIX sum command against the rpm file
(only the first 5 digits are listed).
ie: sum 01EL350_149_038.rpm
EL350
For Impact, Severity and other Firmware definitions, Please
refer to the below 'Glossary of firmware terms' url:
http://www14.software.ibm.com/webapp/set2/sas/f/power5cm/home.html#termdefs
The complete Firmware Fix History for this
Release Level can be
reviewed at the following url:
http://download.boulder.ibm.com/ibmdl/pub/software/server/firmware/EL-Firmware-Hist.html
|
EL350_149_038
07/25/13
|
Impact: Availability
Severity: SPE
System firmware changes that affect all
systems
- A problem was fixed that caused the managed system to go to
the incomplete state on the management console after a partition was
deleted.
- On systems managed by an HMC, a problem was fixed that
caused the managed system to go to the incomplete state on the
management console after a partition was deleted.
- A problem was fixed that caused an error log generated by
the partition firmware to show conflicting firmware levels. This
problem occurs after a firmware update or a logical partition migration
(LPM) operation on the system.
- The firmware was enhanced to display on the management
console the correct number of concurrent live partition mobility (LPM)
operations that is supported.
- A problem was fixed that caused the state of the Host
Ethernet Adapter (HEA) port of be reported as down when the physical
port is actually up.
- A problem was fixed that caused the partition target of a
logical partition migration (LPM) to have its UTC time shifted forward
from the actual time on the source partition.
- A problem was fixed that that caused a HMC code update
failure for the FSP on the accept operation with SRC B1811402 or FSP is
unable to boot on the updated side.
System firmware changes that
affect certain systems
- On systems with I/O towers attached, a problem was fixed
that caused multiple service processor reset/reloads if the tower was
continuously sending invalid System Power Control Network (SPCN) status
data.
- On systems with F/C EU07, the RDX SATA internal docking
station for removable disk cartridge, a problem was fixed that caused
SRCs BA210000 and BA210003 to be logged, and the System Management
Services (SMS) menu firmware to drop into the ok> prompt, when the
default boot list was built.
- On a partition with a large number of potentially bootable
devices, a problem was fixed that caused the partition to fail to boot
with a default catch, and SRC BA210000 may also be logged.
- On systems running AIX or Linux, a problem was fixed that
caused the operating system to halt when an InfiniBand Host Channel
Adapter (HCA) adapter fails or malfunctions.
- On systems running Active Memory Sharing (AMS) partitions,
a timing problem was fixed that may occur if the system is undergoing
AMS pool size changes.
- On systems with a F/C 5802 or 5877 I/O drawer installed,
the firmware was enhanced to guarantee that an SRC will be generated
when there is a power supply voltage fault. If no SRC is
generated, a loss of power redundancy may not be detected, which can
lead to a drawer crash if the other power supply goes down. This
also fixes a problem that causes an 8 GB Fiber channel adapter in
the drawer to log errors if the 12V level fails in the drawer.
- On systems managed by an HMC with a F/C 5802 or 5877 I/O
drawer installed, a problem was fixed that caused the hardware topology
on the management console for the managed system to show "null" instead
of "operational" for the affected I/O drawers.
- A problem was fixed that caused a migrated partition to
reboot during transfer to a VIOS 2.2.2.0, and later, target system. A
manual reboot would be required if transferred to a target system
running an earlier VIOS release. Migration recovery may also be
necessary.
|
EL350_143_038
01/09/13
|
Impact: Function
Severity: ATT
System firmware changes that affect all
systems
- A problem was fixed that caused the service processor to
fail to boot after a concurrent firmware update; this causes a system
crash.
System firmware changes that
affect certain systems
- A problem was fixed that prevented the HMC command
"lshwres" from showing any I/O adapters if any adapter name contained
the ampersand character in the VPD.
- The Power Hypervisor was enhanced to insure better
synchronization of vSCSI and NPIV I/O interrupts to partitions.
- On systems running AIX or Linux, a problem was fixed that
caused a partition to fail to boot with SRC CA260203. This
problem also can cause concurrent firmware updates to fail.
- On systems that are managed by a Hardware Management
Console (HMC), a problem was fixed that caused the hypervisor to be
left in an inconsistent state after a partition create operation failed.
- On systems that are managed by a Hardware Management
Console (HMC), a problem was fixed that caused the hypervisor to become
unresponsive and the managed system to go the incomplete state on the
management console.
|
EL350_132_038
07/27/12
|
Impact: Availability
Severity: SPE
New Features and Functions
- Support for live
partition mobility between systems running Ex350
system firmware, and 8246-L2S systems.
System firmware changes that
affect all systems
- The firmware was
enhanced to improve the isolation of the failing component when SRC
110016x1 (VRM failure) is logged.
System firmware changes that
affect certain systems
- On systems booting from an NPIV (N-port ID virtualization)
device, a problem was fixed that caused the boot to intermittently
terminate with the message "PReP-BOOT: unable to load full PReP
image.". This problem occurs more frequently on the IBM V7000
Storage System running the SAN Volume Controller (SVC), but not on
every boot.
- On systems that are not managed by an HMC, a problem was
fixed that caused SRCs B200813A and BA201002 to be erroneously logged
when the system was powered on using the Advanced System Management
Interface (ASMI). This problem only occurs after the system has
been powered on using the ASMI several hundred times.
- On systems managed by an HMC, and on which Internet
Explorer (IE) is used to access the Advanced System Management
Interface (ASMI), a problem was fixed that caused IE to hang for about
10 minutes after saving changes to network parameters on the ASMI.
- On systems running the AIX operating system, a problem was
fixed that caused the hypervisor to crash with SRC B7000103, after an
HEA (Host Ethernet Adapter) error was logged, when there is a lot of
AIX activity on the HEAs.
|
EL350_126_038
05/02/12
|
Impact: Availability
Severity: HIPER - High Impact/PERvasive, Should be installed as soon as
possible.
System firmware changes that
affect all systems
- The firmware was enhanced to log SRCs BA180030 and BA180031
as informational instead of predictive.
- The firmware was enhanced to increase the threshold of soft
NVRAM errors on the service processor to 32 before SRC B15xF109 is
logged. (Replacement of the service processor is recommended if
more than one B15xF109 is logged per week.)
System firmware changes that
affect certain systems
- The firmware resolves undetected N-mode stability problems
and improves error reporting on the feature code (F/C) 5802 and 5877
I/O drawer power subsystem.
- HIPER/Pervasive:
On systems with PCI adapters in a feature code (F/C) F/C 5802 or 5877
I/O drawer assigned to a Virtual I/O Server (VIOS), and on systems with
the I/O adapters in a CEC drawer assigned to a VIOS, a problem was
fixed that caused the system to crash with SRC B700F103.
- A problem was fixed that caused the hypervisor to hang
during a concurrent operation on a F/C 5802, 5803, 5873 or 5877 I/O
drawer. Recovering from the hypervisor hang required a platform
reboot.
- A problem was fixed that prevented the operating system
from being notified that a F/C 5802 or 5877 I/O drawer had recovered
from an input power fault (SRC 10001512 or 10001522).
- The firmware was enhanced to improve soft error recovery
and error reporting on feature code (F/C) 5802 and 5877 I/O drawers.
- On
system performing Live Partition Mobility (LPM), a problem was fixed
that caused a partition to crash if the following sequence of
operations is performed:
1. The partition is configured with, and is using,
more than 1
dedicated processor.
2. The partition is migrated using LPM from a POWER6
to a POWER7
platform.
3. At any time following the migration from POWER6
to POWER7, one
or more of the dedicated processors is removed from the partition using
a Dynamic Logical Partitioning (DLPAR) operation.
Once
these 3 steps operations have been done, a partition crash is likely if
either:
- The partition is subsequently migrated to any other
platform (POWER6
or POWER7) using LPM, or
- The partition is resumed from hibernation.
- A problem was fixed that caused the output of the AIX
command "uname -m" to be incorrect on the POWER7 system after a
successful Live Partition Migration (LPM) operation from a POWER6 to a
POWER7 system.
- A problem was fixed that caused booting from a virtual
fibre channel tape device to fail with SRC B2008105.
|
EL350_118_038
10/27/11
|
Impact: Availability
Severity: HIPER - High Impact/PERvasive, Should be installed as soon as
possible.
System firmware changes that
affect all systems
- A problem was fixed that
caused the system to terminate when rebooting after the power was
removed, then reapplied.
- A problem was fixed that
caused the message "IPL: 500 - Internal Server Error" to be displayed
when the Hardware Management Console option was selected (which is
under the System Information option) on the Advanced System Management
Interface (ASMI).
- On systems running more than
100 logical partitions, a problem was fixed that caused a concurrent
firmware installation to fail.
- A problem was fixed that caused a system's partition
dates to revert back to 1969 after the service processor or its battery
was replaced. This occurred regardless of whether or not the
service processor's time-of-day (TOD) clock was correctly set during
the service action.
- A problem was fixed that
caused a partition migration operation to abort when the partition has
more than 4096 virtual slots.
- A problem was fixed that
caused the message "500 - Internal Server Error." to be displayed when
a setting was changed on the Advanced System Management Interface's
(ASMI's) power on/off menu, when the change was attempted when the
system was powering down.
- A problem was fixed that
caused booting or installing a partition or system from a USB device to
fail with error code BA210012. This usually occurs when an
operating system (OS) other than the OS that is already on the
partition or system is being booted or installed.
- On the System Management Services (SMS) remote IPL (RIPL)
menus, a problem was fixed that caused the SMS menu to continue to show
that an Ethernet device is configured for iSCSI, even though the user
has changed it to BOOTP.
- A problem was fixed that left
the service processor in an inaccessible state after a power off or
service processor reset. When this problem occurred, SRCs
B160B73F and B1813410 were logged, and a service processor dump was
generated.
System firmware changes that
affect certain systems
- On systems
running IBM i partitions, a problem was fixed that caused changing the
processor weight on an IBM i partition to 255 to have no effect.
- On systems managed by an HMC
or SDMC, a problem was fixed that caused a firmware installation from
the HMC or SDMC with the "do not auto accept" option selected to fail.
- On 8204-E8A and 9409-M50
systems using the utility capacity on demand (COD) feature, a problem
was fixed that prevented the hypervisor from correctly crediting the
time used when the sequence number of the activation code reached
certain values.
- HIPER/Non-Pervasive:
On systems running Active Memory Sharing (AMS) with a feature code
(F/C) 5802 or 5877 I/O drawer attached, a problem was fixed that caused
the system to crash with SRC B170E540 after a warm boot or platform
dump IPL.
- On systems with an iSCSI
network, a problem was fixed that caused the system to hang when
booting from an iSCSI device in the system management services (SMS)
menus.
- On systems with an iSCSI
network, when booting a logical partition using that iSCSI network, a
problem was fixed that caused the iSCSI gateway parameter displayed on
the screen to be incorrect. It did not impact iSCSI boot
functionality.
- On systems using fibre channel
adapters, the firmware was enhanced by the addition of a new option in
the system management services (SMS) Mutliboot menu that facilitates
zoning of physical and virtual fibre channel adapters.
- On systems with
external I/O drawers, the firmware was enhanced such that SRCs 10001B02
and 1000911C place a call home.
- On systems with
external InfiniBand or PCI-E drawers or towers, a problem was fixed
that caused the system to crash with SRC B7000103 if the I/O hub
adapter crashed at the same time an external drawer or tower was being
initialized.
|
4.0
How to Determine Currently Installed Firmware Level
For HMC mangaged systems:
From the HMC, select Updates in the navigation (left-hand) pane, then
view the current levels of the desired server(s).
For SDMC managed systems:
From the SDMC Welcome page, select the desired server(s), then select
Release Management, then select Power System Firmware Management. Click
Gather Target Information, then view the current levels of the desired
server(s).
NOTE:
If Inventory has not previously been collected, a message will be
displayed indicating to "View and Collect Inventory" to proceed.
For System i systems without an HMC or
SDMC:
From a command line, issue DSPFMWSTS.
For System p systems without an HMC:
From a command line, issue lsmcode.
Alternately, use the Advanced System
Management Interface (ASMI) Welcome pane. The current server
firmware appears in the top right
corner.
Example: EL350_149.
5.0
Downloading the Firmware Package
Follow the instructions on Fix Central. You must read and agree to
the
license agreement to obtain the firmware packages.
Note: If your HMC or SDMC is not internet-connected you will need
to
download
the new firmware level to a CD-ROM or ftp server.
6.0 Installing the
Firmware
The method used to install new firmware will depend on the release
level
of firmware which is currently installed on your server. The release
level
can be determined by the prefix of the new firmware's filename.
Example: ELXXX_YYY_ZZZ
Where XXX = release level
- If the release level will stay the same (Example: Level
EL320_075_075
is
currently installed and you are attempting to install level
EL320_081_075)
this is considered an update.
- If the release level will change (Example: Level EL320_081_075 is
currently
installed and you are attempting to install level EL340_096_096) this
is
considered an upgrade.
HMC Managed Systems
Instructions for installing firmware updates and upgrades on systems
managed by an HMC can be found at
http://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/ipha1/updupdates.htm
SDMC Managed Systems:
Instructions for
installing firmware updates and upgrades
on systems
managed by an SDMC can be found at:
http://publib.boulder.ibm.com/infocenter/director/v6r2x/index.jsp?topic=/dpsm/dpsm_managing_hosts/dpsm_managing_hosts_power_firmware.html
Systems not Managed by an HMC or SDMC:
p Systems:
Instructions for installing firmware on systems that are not managed
by an HMC can be found at:
http://publib.boulder.ibm.com/infocenter/powersys/v3r1m5/index.jsp?topic=/ipha5/fix_firm_no_hmc_aix.htm
IBM i Systems:
See "Server Firmware and HMC
Wizard":
http://www-912.ibm.com/s_dir/slkbase.nsf/recommendedfixes
7.0 Firmware History
The complete Firmware Fix History for this Release level can be
reviewed at the following url:
http://download.boulder.ibm.com/ibmdl/pub/software/server/firmware/EL-Firmware-Hist.html