EH350
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
|
EH350_107_038
06/06/11
|
Impact: Availability
Severity: ATT
New Features and Functions
- Support for the attachment of a System Director Management
Console (SDMC).
System firmware changes that affect all systems
- PARTITION-DEFERRED:
A problem was fixed that prevented virtual LANs (VLANs) in a VIOS with
partition ID of 1 from being displayed as bootable devices in the
system management services (SMS) menus.
- A problem was fixed that prevented a hardware management
console (HMC) from being permanently disconnected using the Advanced
System Management Services (ASMI) menus.
- A problem was fixed
that prevented the timed-power-on command from turning the system back
on if the service processor's clock was adjusted to an earlier
time. Adjustment of the service processor's clock could have been
done through the operating system or the Advanced System Management
Interface (ASMI). This problem could occur during the fall when
clocks are set back when daylight saving time ends, for example.
- A problem was fixed that
caused certain service processor error log entries with a severity of
"predictive", and a failing subsystem of "service processor firmware",
to be erroneously converted to "informational".
- A problem was fixed that
caused the HMC2 port on the advanced system management interface (ASMI)
to erroneously default to static IP addressing instead of dynamic.
- A problem was fixed that
caused a firmware installation to fail with SRC B181EF7C.
- A problem was
fixed that prevented processor resources from being moved to another
partition by a DLPAR (dynamic LPAR) operation.
- A problem was fixed that
prevented partitions from booting.
- The firmware was enhanced to
list the attached devices when viewing the adapter information for a
partition profile on the HMC GUI.
- A problem was fixed that could
cause the target partition to crash after a successful P6 to P7
partition migration. Possible AIX error log entries
include: label: DSI_PROC, resource: SYSVMM, with
description: "DATA STORAGE INTERRUPT, PROCESSOR". Other
partition-related crash descriptors may also be logged.
- A problem was fixed that could
cause AIX error log entries following a successful partition
migration. Possible AIX error log entries include: label:
RTAS_ERROR, resource: sysplanar0, with description: "INTERNAL ERROR
CODE". Other errors may also be logged.
- A problem was fixed that
caused a partition to crash with SRC BA330002 after several concurrent
installations of system firmware, or partition migrations, without a
reboot.
- A problem was fixed that caused multiple
DR_DMA_MIGRATE_FAIL entries in
the AIX error log.
- A problem was fixed that
caused the installation of some versions of Linux to fail.
- A problem was fixed that
caused a partition migration or partition hibernation operation to hang
with the partition left in the "suspending" state.
- The firmware was enhanced to
log SRC B1768B76 as informational instead of unrecoverable.
- A problem was fixed that
caused the platform to become unresponsive; this was indicated by an
incomplete state on the HMC. When this problem occurred, the
partitions on the managed system became unresponsive.
- A problem was fixed that
caused the managed system to go to the incomplete state on the HMC.
- The firmware was enhanced to
log a predictive SRC if the Ethernet cables are misplugged (swapped) on
a node controller.
- The firmware was enhanced such
that a call home is not made when an error logged by the system
controller or the network controller is informational, or recovered,
and the reset/reload bit is set.
- The field replaceable unit
(FRU) list for SRC B158C004, which indicates a clock card failure, was
enhanced to include additional parts.
- On systems with a F/C 5803
or 5873 I/O expansion drawer, a problem was fixed that caused SRC
B7006907 to be erroneously logged.
System firmware changes that affect certain systems
- On systems running Advanced
Memory Sharing (AMS), a problem was fixed that caused an AMS partition
to crash with SRC B700F103. This problem may occur when reducing
the size of the AMS pool (or doing a hot node repair on a model MMB or
MHB) at the same time as dynamically creating an AMS partition, or
changing an AMS partition's maximum memory.
- On systems using
logical host Ethernet adapter (LHEA) ports, a problem was fixed that
caused the activation of a partition that is using an LHEA logical port
(LPORT) to hang at C2008104, and the HMC to show an Incomplete status
for the system.
- On systems using capacity on demand
(CoD), a problem was fixed that caused multiple informational B7005300
SRCs to be logged, which caused the error log to wrap, and predictive
and unrecoverable SRC data to be lost.
- On systems running IBM i
partitions, IBM i network installation capability was not reported
correctly to the HMC after installation of the firmware service pack
that enabled this function without rebooting the managed system.
- On systems running
IBM i partitions, a problem was fixed that caused a RAID array of SCSI
disks to be exposed if an MES upgrade was done, or a system plan was
created.
- On systems and
partitions running IBM i, a problem was fixed that caused the operating
system to use excessive processor cycles.
Concurrent Maintenance (CM) firmware fixes
- On systems with
five or more nodes, and the hub numbers are consecutive, a problem was
fixed that caused B6005121 to be erroneously logged (and call home)
after a concurrent maintenance operation on a node.
|
EH350_103_038
02/21/11
|
Impact: Data
Severity: HIPER
- High Impact/PERvasive, Should be installed as soon as
possible.
System firmware changes that affect certain systems
- HIPER: IBM testing
has uncovered a
potential undetected data corruption issue when a mobility operation is
performed on an AMS (Active Memory Sharing) partition. The data
corruption can occur in rare instances due to a problem in IBM
firmware. This issue was discovered during internal IBM testing,
and has not been reported on any customer system. IBM recommends that
systems running on EH340_075 or later move to EH350_103 to pick up the
fix for this potential problem. (Firmware levels older than
EH340_075 are not exposed to the problem.)
- On systems with a F/C
5803 or 5873 I/O drawer attached, a problem was fixed that caused a
partition to crash during a page migration operation.
- A problem was fixed that
caused a partition to crash with SRC BA330002 after several concurrent
installations of system firmware, or partition migrations, without a
reboot.
- A problem was fixed that
caused AIX licensing issues when migrating a partition from a P6 to a
P7 system.
- On systems running IBM i
partitions, a problem was fixed that caused SRC BA040030 to be
erroneously logged, and a call home to be made, even though the
partition booted successfully.
|
EH350_085_038
10/26/10
|
Impact: Availability
Severity: HIPER
- High Impact/PERvasive, Should be installed as soon as
possible.
System firmware changes that affect all systems
- HIPER: A
problem was fixed that caused the HMC to show the server's status as
incomplete, and SRC B7000602 to be logged against SFLPHMCCMDTASK in
serviceable events. This problem can also cause the system to
crash when it occurs.
- HIPER: A
problem was fixed that caused repeated reset/reloads of the service
processor, and fail-overs, to occur after a hypervisor-initiated
reset/reload of the service processor was completed. That led to
loss of communication between the service processor and the hypervisor
(indicated by SRC B182951C).
- A problem was fixed that
caused a CEC node to unexpectedly lose power, and caused a system
crash. Systems that had a service processor role change at server
power off are exposed to this issue.
- A problem was fixed that
caused SRC B181440D to be erroneously logged.
- The firmware was
enhanced to log SRC B181D30B as informational instead of predictive.
- The firmware was enhanced to
list the attached devices when viewing the adapter information for a
partition profile on the HMC GUI.
- A problem was fixed that
caused the hypervisor to issue almost continuous reset/reload requests
to the service processor.
System firmware changes that affect certain systems
- The firmware was
enhanced to support the network installation of the IBM i operating
system from the hardware management console (HMC) command line
interface (CLI).
- On systems using the IPv6
protocol, a problem was fixed that caused valid link local and unique
link local addresses to be erroneously invalidated. This
prevented the port with that address from being used for network boot
or network installation.
|
EH350_071_038
06/30/10
|
Impact: Usability
Severity: SPE
System firmware changes that affect all systems
- DEFERRED: A problem
was fixed that could result in a system checkstop while running
floating point computations. Although this is a high-impact
problem, it has a very low probability of occurring.
- A problem was fixed
that caused a call home to be erroneously made with SRC B181E911, and a
service processor dump to be taken unnecessarily.
- A problem was fixed
that caused the HMC to show a status of "Incomplete" for the managed
system, and numerous service processor dumps to be generated.
- The firmware was
enhanced to improve the callouts for certain types of processor
failures that log SRC B1xxE504.
- The firmware was enhanced to
make a hidden error log visible when a failing GX adapter caused errors
to be logged by the processor run-time (PRDF) diagnostics.
- The firmware
was enhanced to improve the callouts when NVRAM corruption is detected
in the bulk power controller's (BPC's) service processor.
- On systems running EH350_xxx
firmware, a problem was fixed the prevented the reset/reload bit from
being set correctly in a service processor error log entry.
- A problem was fixed that
caused SRC B181E617 to be erroneously logged and a service processor
dump to be unnecessarily generated.
System firmware changes that affect certain systems
- On
systems running the IBM i operating system, a problem was fixed that
caused a DLPAR move operation with an IOP (I/O processor) and IOA (I/O
adapter) to fail intermittently. The DLPAR operation was
successful, but the IOA failed to power on in the new partition.
Concurrent maintenance (CM) firmware fixes
- A problem was fixed
that would cause a concurrent maintenance operation to fail if the HMC
was rebooted before the previous CM operation was complete.
- On systems with F/C 5803 or
F/C 5873 I/O drawers attached and a boot device in the drawer, a
problem was fixed that prevented a partition from booting after the
concurrent repair of the GX adapter that connects the 5803 or 5873
drawer to the system, or to the node that contains the GX adapter.
|
EH350_049_038
03/10/10
|
Impact: Serviceability
Severity: HIPER
System firmware changes that affect all systems
- HIPER: A problem was fixed that caused the system
to crash if the server was running AIX and had a F/C 5802 or 5877
drawer (in a 19" rack), or F/C 5803 or 5873 drawer (in a 24" rack),
attached.
- DEFERRED:
This fix corrects the handling of a specific processor instruction
sequence that has the potential to result in undetected data
errors. This specific instruction sequence has only been observed
in a small number of highly tuned Floating Point intensive
applications. However, it is strongly recommended that this fix
be applied to all POWER6 systems. This fix has the potential to
decrease system performance on applications that make extensive use of
floating point divide, square root, or estimate instructions.
- A problem was fixed that prevented an SRC from being
recorded in the service processor dump produced by a host-initiated
reset.
- A problem was fixed that prevented the repair of a
deconfigured system controller from being completed successfully.
- A problem was fixed that caused SRC 10009135, followed by
10009139, to be erroneously logged. These SRCs indicate a system
power control network (SPCN) loop is being broken, then re-established.
- The firmware was enhanced to allow a temporary threshold
reduction for processor unit book interconnect predictive errors.
- A problem was fixed that caused a reset/reload of a network
controller.
- A problem was fixed that, under certain rare circumstances,
caused a partition to hang when being shut down.
- A problem was fixed that caused the system to hang with
SRCs B182953C, B182954C and B17BE434 being logged.
- The firmware was enhanced to detect and handle 12X
InfiniBand I/O drawer cabling errors better.
- A problem was fixed that, under certain rare circumstances,
caused the system to become unresponsive and appear to hang when
page migration occurred on a PCIe slot.
System firmware changes that affect certain systems
- A problem was fixed that caused a virtual SCSI or virtual
fibre channel adapter to be seen by the operating system as not
bootable when it was added to a partition using a dynamic LPAR (DLPAR)
operation.
- On systems running IBM i, a problem was fixed that caused
booting the operating system from a fibre channel device to fail with
SRC 576B8301.
- On systems with a F/C 5802 or 5877 drawer attached, a
problem was fixed that could impact the performance of a 4-port
Ethernet adapter F/C 5272, 5275, 5279, 5280, 5525, 5526, or 5527
installed in that drawer.
- In partitions running AIX or Linux, a problem was fixed
that caused the addition of an I/O slot to a partition using a dynamic
LPAR (DLPAR) add operation to fail.
- On systems with shared processors, a problem was fixed that
caused the partitions to hang and become unresponsive for very short
periods of time.
- A problem was fixed that prevented the IPv6 DHCP address
from being displayed on the advanced system management interface (ASMI)
network configuration screens when IPv6 and DHCP were enabled.
This only occurred on systems with virtual LAN (VLAN) addresses (such
as eth0.30, eth0.31), and when IPv6 addresses were assigned to the
eth0.xx interface.
- On systems running redundant VIOS partitions, a problem was
fixed that prevented Ethernet traffic from being properly bridged
between the two partitions. This problem also prevented shared
Ethernet adapter failover from working correctly.
- A problem was fixed that caused the hypervisor to loop
unnecessarily and consume too many processor cycles. This
impacted the performance of the system.
Concurrent maintenance (CM) firmware fixes
- The firmware was enhanced such that if an Ethernet cable is
misplugged on a node controller during a concurrent node add operation,
the node add operation will be completed successfully.
- A problem was fixed that prevented the concurrent repair of
a redundant system controller.
- A problem was fixed that caused unpredictable system
behavior if a capacity on demand (CoD) or a virtualization engine
technology (VET) activation code was entered and accepted after a node
0 evacuation was done. The unpredictable machine behavior might
also have occurred, if a node 0 evacuation failed, a system dump was
taken, and a memory-preserving IPL was then initiated.
- A problem was fixed that caused a concurrent maintenance
operation after a node evacuation to fail. When this problem
occurred, the system erroneously states that a platform memory dump is
pending.
- A problem was fixed that prevented a concurrent maintenance
operation from completing successfully.
|
EH350_038_038
10/30/09
|
Impact:
Function
Severity: Special Attention
New Features and Functions:
- Support for the concurrent repair of a system controller.
- Support for the concurrent removal of 12X-attached 24"
I/O drawers.
- Support for a USB-attached half-high 5.25" backup device
using a
removable
hard disk drive (HDD).
- Support for a platform dump that is not disruptive.
- Support for i5/OS multipath storage I/O through VIOS
partitions.
System firmware changes that affect all systems
- A problem was fixed that might cause a concurrent
firmware maintenance
(CFM) operation to fail repeatedly, or a concurrent maintenance (CM)
operation
to fail repeatedly, when a large number of I/O loop errors were being
logged
during the CFM operation.
- The firmware was enhanced to handle system dumps
(SYSDUMPs) larger than
4GB in size.
- On systems running system firmware release EH340 EH340, a
problem was
fixed
that caused a dynamic LPAR (DLPAR) operation on memory to fail until
the
platform was rebooted.
- The firmware was enhanced to improve the performance of
the F/C 5732 ,
5735, and 5769 PCI-E adapters. The firmware was enhanced such that SRCs
B181F126, B181F127, and B181F129 are correctly logged, and no longer
calls
home unnecessarily for these SRCs.
- A problem was fixed that caused a repair and verify
(R&V) operation
on the hardware management console (HMC) to fail with the message
"Exception
encountered while rendering panel as HTML".
- The firmware was enhanced such that a generic B1817201
SRC will no
longer
be logged when a cache error occurs on a node controller (NC).
Unique
SRCs will now be logged for cache failures, and upper and lower
thresholds
have been added to the NC cache error logging scheme.
- The firmware was enhanced to improve the field
replaceable unit (FRU)
callouts
for SRCs B1xxC004 and B1xxC005.
- A problem was fixed that might cause the system to crash
with SRC
B181E504,
then SRC B1813909, being logged.
- The firmware was enhanced to more accurately describe the
reason memory
was deconfigured on the advanced system management interface (ASMI)
memory
deconfiguration screen.
- The firmware was enhanced such that when a certain type
of hardware
failure
occurs in a bulk power controller (BPC), the appropriate errors will be
logged instead of SRCs B1818601 and B1818611, which indicate a firmware
failure.
- On systems using the HEA (host Ethernet adapter), also know
as the Integrated Virtual Ethernet (IVE) function, a problem was fixed
that caused link failures if the HEA was connected to certain
third-party Ethernet switches. A problem causing an unexpected
increment in the Pxs_TXIME register, but not affecting network
performance, was also fixed.
Concurrent maintenance (CM) firmware fixes
- A problem was fixed that caused SRC B181A494 to be
erroneously logged
if
a concurrent maintenance operation took longer than 60 minutes.
- On systems with 24" I/O drawers, a problem was fixed that
might cause a
partition to crash, with a system reboot required for recovery, when a
F/C 5797 or 5798 drawer was concurrently added.
- On systems with four drawers, a problem was fixed that
caused the
system
controller to perform a reset/reload, which caused a concurrent
maintenance
operation to fail, on the fourth node (P4).
- A problem was fixed that caused the current replacement
of an
InfiniBand
GX adapter or I/O planar to fail if a partition owned an embedded
device
on the planar.
|