Before downloading microcode for Escala:
Please make sure you read and accept the conditions of the License Agreement for Machine Code
1.0 Overview
The following build adds fixes and new function. See corresponding Change
History document for additional information.
1.1 Build Information / Build ID
Image Name: EA350.159.074.img
Version Number: 01EA350_159_074
Version Date: 06/24/2014
1.2 Limitations
N/A
1.3 Level recommendation and prerequisites for the update
* See corresponding Change History document for additional information.
- A full backup should be completed and verified prior to running this, or any other system upgrade.
Prerequisite: AMM Level BPEO62C or later
1.4 Dependencies
N/A
2.0 Installation and setup instructions
The procedure to install the BIOS image file using the main partition are as
follows:
2.1 Send the file to the local hard drive of the operating system.
2.2 Login on the console with an ID that has root authority
2.3 Use the "update_flash" program to update the system giving it the option "-f" followed by the path to the image (.img) file on the local operating system.
2.3.0 Location of "update_flash" command:
AIX: /usr/lpp/diagnostics/bin/update_flash
Linux: /usr/sbin/update_flash
2.3.0.1 Specific packages are needed for Linux which will install the
"update_flash" command. These packages can be found at
www14.software.ibm.com/webapp/set2/sas/f/lopdiags/
2.3.1 To commit an image to the PERM side, use the "-c" option on the
"update_flash" command.
2.3.2 To reject an image on the TEMP side, use the "-r" option on the
"update_flash" command.
2.4 Use the "ldfware" command to update systems with the Virtual I/O Server operating system installed. The "--file" option followed by the path
to the image (.img) file should be provided.
2.5 For the shell script files (*.sh), the procedure to install the bundled
BIOS file using the main partition is as follows:
2.5.1 Send the file to the local hard drive of the operating system (be sure
to use the HTTP protocol option if downloading from the web).
2.5.2 Login on the console with an ID that has root authority
2.5.3 Make sure the downloaded file has the proper 'execute' permissions
chmod +x ibm_fw_bios_ea350.159.074_aix_ppc64.sh
2.5.4 Run the downloaded file as a command: /(downloaded-file-dir)/(file name).sh
This executable file will unpack the .img file and run update_flash -f (.img) for you.
./ibm_fw_bios_ea350.159.074_aix_ppc64.sh
Other options allowed on the shell script:
(file-name.sh) -v : verifies the firmware you have installed
(file-name.sh) -c : commits the image to the PERM side
(file-name.sh) -r : reject the image on the TEMP side
(file-name.sh) -x : extracts the BIOS image file from the package
Update Firmware v1.0 extracting flash code
Start Flash Process
/usr/lpp/diagnostics/bin/update_flash -q -f 01EA350_149_074.img
The image is valid and would update the temporary image to EA350_149.
The new firmware level for the permanent image would be EA350_074
The current permanent system firmware image is EA350_074.
The current temporary system firmware image is EA350_132.
BE CAREFUL THIS WILL REBOOT THE BLADE SERVER WITHOUT CONFIRMATION!
2.6 To verify the firmware you have installed, use "-v" option on the "update_flash" command.
2.7 To commit an image to the PERM side, use the "-c" option on the "update_flash" command.
2.8 To reject an image on the TEMP side, use the "-r" option on the "update_flash" command.
2.9 To extract the BIOS image file from the package, use the "-x" option on the "update_flash" command.
3.0 Change History
Note: To those customers on a release prior to Version 2.0, refer to instructions for 'Version 1.02, 01EA320_046_030' at the bottom of this document before proceeding.
Version 3.5.14 (350.E0), 01EA350_159_074 - 06/24/2014
New features and functions
SW202394: Support was dropped for Secured Socket Layer (SSL)
Version 2 and SSL weak and medium cipher suites in the service processor
web server (Ligthttpd). Unsupported web browser connections to the Advanced
System Management Interface (ASMI) secured port 443 (using https://) will now
be rejected if those browsers do not support SSL version 3. Supported web
browsers for Power6 ASMI are Netscape (version 9.0.0.4), Microsoft Internet
Explorer (version 7.0), Mozilla Firefox (version 2.0.0.11), and Opera
(version 9.24).
System firmware changes that affect all systems
SW215660: A problem was fixed that caused the system information LED to be
lit without a corresponding SRC and error log for the event. This problem
typically occurs when an operating system on a partition terminates abnormally.
99013: A security problem was fixed in the service processor Lighttpd web
server that allowed denial of service vulnerabilities for the Advanced System
Manager Interface (ASMI). The Common Vulnerabilities and Exposures issue
numbers for this problem are CVE-2011-4362 and CVE-2012-5533.
SW233425: A problem was fixed on the service processor where the Small-
Footprint CIM Broker Daemon (SFCBD) process was accessing a null pointer
and failing with a core dump, triggering a FSP dump to collect the core.
SW240235: A problem was fixed that caused a security scan of the Advanced
System Manager Interface (ASMI) to fail. The Lighttpd web server
configuration cipher list was updated to improve the security.
SW255439: A security problem in the Secure Socket Layer (SSL) protocol
on the service processor was fixed to prevent a man-in-the-middle attack.
The Common Vulnerabilities and Exposures issue number is CVE-2011-3389.
SW255449: A security problem was fixed for the Lighttpd web server that
allowed arbitrary SQL commands to be run on the service processor of the
blade server. The Common Vulnerabilities and Exposures issue number is
CVE-2014-2323.
SW255449: A security problem was fixed for the Lighttpd web server where
improperly-structured URLs could be used to view arbitrary files on the
service processor of the blade server. The Common Vulnerabilities and
Exposures issue number is CVE-2014-2324.
SW256302: HIPER/Pervasive: A security problem was fixed in the OpenSSL
Montgomery ladder implementation for the ECDSA (Elliptic Curve Digital
Signature Algorithm) to protect sensitive information from being obtained
with a flush and reload cache side-channel attack to recover ECDSA nonces
from the service processor. The Common Vulnerabilities and Exposures issue
number is CVE-2014-0076. The stolen ECDSA nonces could be used to decrypt
the SSL sessions and compromise the Hardware Management Console (HMC)
access password to the service processor. Therefore, the HMC access
password for the blade server should be changed after applying this fix.
SW256302: HIPER/Pervasive: A security problem was fixed in the OpenSSL
Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)
to not allow Heartbeat Extension packets to trigger a buffer over-read to
steal private keys for the encrypted sessions on the service processor.
The Common Vulnerabilities and Exposures issue number is CVE-2014-0160 and
it is also known as the heartbleed vulnerability. The stolen private keys
could be used to decrypt the SSL sessions and and compromise the Hardware
Management Console (HMC) access password to the service processor.
Therefore, the HMC access password for the blade server should be changed
after applying this fix.
SW166804: A problem was fixed that caused the "Disable NIC" option from the
Advanced Management Module (AMM) to corrupt the service processor host name
with invalid characters.
SW261226: A problem was fixed that caused a "code accept" during a concurrent
firmware installation from the HMC to fail with SRC E302F85C.
XB275164: A security problem was fixed in the service processor TCP/IP
stack to discard illegal TCP/IP packets that have the SYN and FIN flags set
at the same time. An explicit packet discard was needed to prevent further
processing of the packet that could result in an bypass of the iptables
firewall rules.
SW264792: HIPER/Pervasive: A security problem was fixed in the OpenSSL
(Secure Socket Layer) protocol that allowed clients and servers, via a
specially crafted handshake packet, to use weak keying material for
communication. A man-in-the-middle attacker could use this flaw to decrypt
and modify traffic between the management console and the service processor.
The Common Vulnerabilities and Exposures issue number for this problem is
CVE-2014-0224.
SW264792: HIPER/Pervasive: A security problem was fixed in OpenSSL for a
buffer overflow in the Datagram Transport Layer Security (DTLS) when handling
invalid DTLS packet fragments. This could be used to execute arbitrary code
on the service processor. The Common Vulnerabilities and Exposures issue
number for this problem is CVE-2014-0195.
SW264792: HIPER/Pervasive: Multiple security problems were fixed in the way
that OpenSSL handled read and write buffers when the SSL_MODE_RELEASE_BUFFERS
mode was enabled to prevent denial of service. These could cause the service
processor to reset or unexpectedly drop connections to the management console
when processing certain SSL commands. The Common Vulnerabilities and Exposures
issue numbers for these problems are CVE-2010-5298 and CVE-2014-0198.
SW264792: HIPER/Pervasive: A security problem was fixed in OpenSSL to prevent
a denial of service when handling certain Datagram Transport Layer Security
(DTLS) ServerHello requests. A specially crafted DTLS handshake packet could
cause the service processor to reset. The Common Vulnerabilities and Exposures
issue number for this problem is CVE-2014-0221.
SW264792: HIPER/Pervasive: A security problem was fixed in OpenSSL to prevent
a denial of service by using an exploit of a null pointer de-reference during
anonymous Elliptic Curve Diffie Hellman (ECDH) key exchange. A specially
crafted handshake packet could cause the service processor to reset. The
Common Vulnerabilities and Exposures issue number for this problem is
CVE-2014-3470.
System firmware changes that affect certain systems
SW202308: On systems using dynamic Distributed Host Control Protocol (DHCP)
IP addresses, a problem was fixed that caused communication hangs when DHCP
client processes were unable to renew their IP addresses. The iptable rules
needed to be updated to open DHCP ports 67 and 68 to prevent the DHCP network
traffic from being filtered by the service processor.
SW242028: On a system with partitions with redundant Virtual Asynchronous
Services Interface (VASI) streams, a problem was fixed that caused the system
to terminate with SRC B170E540. The affected partitions include Active Memory
Sharing (AMS), encapsulated state partitions, and hibernation-capable
partitions. The problem is triggered when the management console attempts to
change the active VASI stream in a redundant configuration. This may occur
due to a stream reconfiguration caused by Live Partition Mobility (LPM);
reconfiguring from a redundant Paging Service Partition (PSP) to a single-PSP
configuration; or conversion of a partition from AMS to dedicated memory.
SW220699: On systems involved in a series of consecutive Live Partition
Mobility (LPM) operations, a memory leak problem was fixed in the run time
abstraction service (RTAS) that caused a partition run time AIX crash with
SRC 0c20. Other possible symptoms include error logs with SRC BA330002
(RTAS memory allocation failure).
SW219936: A problem was fixed in the run-time abstraction services (RTAS)
extended error handling (EEH) for fundamental reset that caused partitions
to crash during adapter updates. The fundamental reset of adapters now
returns a valid return code. The adapter driver using fundamental reset
affected by this fix are the following:
o QLogic PCIe Fibre Channel adapters (combo card)
SW240407: On a system with a disk device with multiple boot partitions,
a problem was fixed that caused System Management Services (SMS) to list
only one boot partition. Even though only one boot partition was listed
in SMS, the AIX bootlist command could still be used to boot from any
boot partition.
SW256020: For a partition with a 256MB Real Memory Offset (RMO) region
size that has been migrated from a Power8 system to Power7 or Power6 using
Live Partition Mobility, a problem was fixed that caused a failure on the
next boot of the partition with a BA210000 log with a CA000091 checkpoint
just prior to the BA210000. The fix dynamically adjusts the memory footprint
of the partition to fit on the earlier Power systems.
Version 3.5.13 (350.D0), 01EA350_149_074 - 07/24/2013
System Firmware changes that affect all systems
SW179639: A problem was fixed that caused a service processor dump to be taken with SRC B181EF88 logged.
SW210259: A problem was fixed that caused the state of the Host Ethernet Adapter (HEA) port to be reported as down when the physical port is actually up.
SW213866: 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.
SW212564: 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
SW206630: On systems managed by a management console, the firmware was enhanced to display on the management console the correct number of concurrent live partition mobility (LPM) operations that is supported.
SW189577: On systems managed by a management console, a problem was fixed that caused the managed system to go to the incomplete state on the management console after a partition was deleted.
SW190463: 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.
SW204472: 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.
SW206630: The firmware was enhanced to display on the managementconsole the correct number of concurrent live partition mobility (LPM) operations that is supported.
SW170452: On systems managed by a management console, a problemwas fixed that caused the hypervisor to become unresponsive andthe managed system to go to the incomplete state on the managementconsole.
SW176987, SW178674: On systems running AIX or Linux, a problemwas fixed that caused a partition to fail to boot with SRCCA260203. This problem also can cause concurrent firmware updates to fail.
FW596856: On systems managed by a management console, 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.
SW167605: On systems managed by a management console, the Power Hypervisor was enhanced to insure better synchronization of vSCSI and NPIV I/O interrupts to partitions.
Version 3.5.11.1, 01EA350_136_074 - 12/12/2012
System Firmware changes that affect all systems
SW160763 : The firmware was enhanced to support the installation of POWER6 blades in an 8852/7989 BladeCenter H chassis with midplane revision 11 (FRU P/N 46C9700) or later.
Version 3.5.11, 01EA350_132_074 - 07/25/2012
System Firmware changes that affect all systems
SW149614 : 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.
FW585444 : 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.
Version 3.5.10 , 01EA350_126_074 - 05/02/2012
System Firmware changes that affect all systems
SW084368 A problem was fixed the prevented the Serial-Over-Lan
(SOL) interface from working with its default values.
XB079955 A problem was fixed that caused the service processor
to report the same interface name (eth0) and MAC address
to the Advanced Management Module (AMM) for the two
Ethernet interfaces to the blade system.
SW109759 A problem was fixed that caused the service processor
erroneously perform a reset/reload.
XB099389 A problem was fixed in the System Management Services
(SMS) boot menus that caused a boot attempt from an
Ethernet port configured for iSCSI to be attempted as
a bootp boot instead.
Version 3.5.9, 01EA350_118_074 - 10/27/2011
System Firmware changes that affect all systems
XB062709 A problem was fixed that caused the warning reset
temperature displayed on the Advanced Management
Module's (AMM's) graphical user interface (GUI)
to be incorrect.
Version 3.5.8, 01EA350_108_074 - 07/07/2011
System firmware changes that affect certain systems
SW073067 HIPER: On systems running VIOS, a problem was fixed that caused the system to crash with SRC B700F103.
SW077318 On POWER6 blades being managed by a System Director Management Console (SDMC), a problem was fixed that prevented the SDMC from discovering a blade if its IP address had been changed.
SW077502 On POWER6 blade systems that are managed by a System Director Management Console (SDMC), as well as an Advanced Management Module (AMM), a problem was fixed that prevented service processor error log entries that had been sent to the SDMC from being sent to the AMM.
Version 3.5.7, 01EA350_107_074 - 06/21/2011
System Firmware changes that affect all systems
XB053338 A problem was fixed that prevented error logs and fault LEDs from being propagated to the chassis when a fault occurred on a blade until the blade was powered down.
SW061459 A problem was fixed that caused the number of processors shown on the hardware VPD screen in the Advanced Management Module (AMM) to be incorrect.
Version 3.5.6, 01EA350_103_074 - 02/18/2011
System firmware changes that affect certain systems
FW537077 On systems running IBMi 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.
Version 3.5.5, 01EA350_085_074 - 10/26/2010
System firmware changes that affect all systems
SW017783 HIPER: On systems in dynamic power save mode using the Active Energy Manager plug-in with Systems Director, a
problem was fixed that caused SRC B1812616, then a hardware checkstop (SRC B113E504), to be logged.
SW034100 HIPER: A problem was fixed that caused repeated
reset/reloads of the service processor 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).
SW015837: The firmware was enhanced to log SRC B181D30B as informational instead of predictive.
SW034100: 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
SW037907: 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.
Version 3.5.4, 01EA350_074_074 - 07/21/10
System firmware changes that affect all systems
XB028631: A problem was fixed that prevented the gateway address
presented to the user from being updated when dynamic
addressing was selected for the service processor interface.
FW517311: A problem was fixed that caused the service processor's
IP address to be changed when the I/O module selection was
changed.
FW519472/CPS 83SCZM: 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.
SW007607: A problem was fixed that caused SRC B181A43C to be
erroneously logged.
SW037522: A problem was fixed that caused a service processor error
log entry to be repeated many times in the AMM error log.
System firmware changes that affect certain systems
FW461459: A problem was fixed that caused a system running Linux
to crash when the "serv_config -l" command was run.
Version 3.5.1, 01EA350_053_038 - 04/26/10
System firmware changes that affect all systems
740165/FW510448: 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 high performance computing
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 applicationgs that make extensive
use of floating point divide, square root or
estimate instructions.
729261/FW493426: A problem was fixed that prevented the 8G QLogic
CFFh daughter card, feature code 8271, from being
correctly detected and configured.
732759/FW499126: A problem was fixed that caused a device driver
conflict when both PCIx and PCIe cards were installed
in a blade.
745147/FW516271, 742459/FW513002, 741269/FW511748:
A problem was fixed that caused SRCs B1818A0E,
B1818A10, and B1818A1E to be erroneously logged.
System firmware changes that affect certain systems
746464/FW517579: On blade systems running EA340_xxx or EA350_038
firmware, a problem was fixed that caused the
network interface on the blade to become
unavailable if the network interface is disabled
using the AMM (advanced management module).
If this problem occurs, installing this service
pack re-enables the IPv4 network interface on
the blade.
745262/XB030248: On blade systems running EA350_038 firmware, a
problem was fixed that caused the CPU temperature
data to be displayed incorrectly for all CPUs
except #1 on the AMM (advanced management module).
Version 3.5, 01EA350_038_038 - 10/30/09
Enhancements:
- Support in Linux for the CEE/FCoCEE 10Gb Ethernet expansion card, feature code 8275
- Support for n_port ID virtualization (NPIV) for the Emulex 8Gb fibre channel expansion card, feature code 8240.
Version 3.03, 01EA340_101_039 - 09/22/09
FW481114: The firmware was enhanced such that SRCs B181F126, B181F127, and B181F129 are logged appropriately, and no longer cause an unnecessary call-home to be made.
Version 3.02, 01EA340_095_039 - 08/17/09
System firmware changes that affect all systems.
FW470230: A problem was fixed that prevented the operating system from using VLAN-2.
FW448424: A problem was fixed the prevented the advanced management module (AMM) from displaying the MAC addresses of blade systems correctly.
System firmware changes that affect certain systems
FW469524, FW473931: In telco BladeCenters, the firmware was enhanced so that the fan speed increases at a lower temperature than previously. This provides additional cooling of the disk drives in the blade systems.
Version 3.01, 01EA340_075_039 - 05/22/2009
System firmware changes that affect all systems
XB003819: A problem was fixed that caused SRC B1xx3305 to be erroneously logged.
FW252699: The firmware was enhanced such that SRC A1003000, which was being logged as an error after a successful platform dump, will now be logged as an informational message.
FW325837: A problem was fixed that prevented a customer-replaceable unit (CRU) planar and a CRU management card from being replaced at the same. In the prior firmware levels, the planar had to be powered on at least once before adding the management card, if both needed to be changed at the same time.
System firmware changes that affect certain systems
XB008096: On blades with a thermal power management device (TPMD), a problem was fixed that caused SRCs B181261D and B1812616 to be erroneously logged when a processor had been guarded out.
FW330278: On blades running system firmware level EA340_039 with a CFFh card (high speed daughter card) installed, a problem was fixed that caused the blades open fabric manager (BOFM) to set the CFFh card ports to the wrong switch bay ports.
FW456807: On the JS22 blade, a problem was fixed that was caused the maximum power that was reported to the advanced management module (AMM) to be incorrect.
Version 3.00, 01EA340_039_039 - 11/21/2008
Enhancements:
- Support for a virtual tape device.
- Support in the hypervisor for three types of hardware performance monitors.
- Support for installing AIX and Linux using the integrated virtualization manager (IVM).
- Support for enhanced power management, including dynamic voltage and frequency slewing.
- Support for the 4-port Gb Ethernet expansion card - On systems running AIX, support for an enhanced power and thermal management capability. When static power save mode is selected, AIX will "fold" processors to free processors which can then be put in the "nap" state.
- Support for the 2-port 8Gb fibre channel expansion card.
- Support for a "soft" power cap.
- Support for "calling home" when a serviceable event occurs.
Problems fixed:
- FW204523, FW204602: A problem was fixed the prevented a blade system from reporting a low or dead NVRAM battery.
- FW212754: A problem was fixed that caused the advanced management module (AMM) to show that a blade system is powered off, when in fact it is powered on, after AC power has been removed, then reapplied, to a BladeCenter chassis. SRC B181D5FF was logged when this problem occurred. This also resolved a another problem that caused SRC B181D50F to be logged, and a service processor dump to be taken.
- FW193210: A problem was fixed that, under certain rare circumstances, made it necessary to issue two power-on commands from the advanced management module (AMM) to get a blade system to power on, instead of one.
- FW201153: A problem was fixed that caused the firmware to display the potential first and second MAC addresses of the host Ethernet
adapter (HEA), instead of the potential first and last MAC addresses of the HEA. The first and second MAC addresses are normally the first
and last MAC addresses unless partitions are being created, and HEA addresses being assigned, in a virtual input/output system (VIOS).
- FW203691: A problem was fixed that caused the message "Problem communicating with BSMP" to be erroneously displayed on the advanced
management module (AMM) status page after a blade system's firmware was updated successfully.
- FW248450: A problem was fixed that caused the serial-over-LAN (SOL) connection to be intermittently dropped between the service
processor and the advanced management module (AMM).
- FW208834: A problem was fixed that prevented the "Restart blade with NMI" command on the advanced management module (AMM) console
from working correctly. When this command was issued prior to being fixed, a simple reboot was done, and no failure data was captured,
instead of performing a platform dump and then rebooting the blade system.
Note: AMM firmware level BPEO42P or later has to be installed along with this version of the blade firmware system
firmware to resolve this problem.
- FW199615: A problem was fixed that caused SRC BFE4C025 with the description "Undetermined Error" to be logged in the AIX error log.
- FW201153: A problem was fixed that caused SRC B1818A10 to be logged in the advanced management module (AMM) event log after service
data from the BladeCenter was gathered. The BladeCenter open fabric manager (BoFM) had to enabled for this problem to occur.
- FW236482: A problem was fixed that caused SRC B1819906 to be logged when the "OS shutdown and blade power off" option on the
advanced management module (AMM) was used.
Version 2.02, 01EA330_046_031 - 08/22/2008
Problems fixed:
- FW196952, FW188794, FW202372: The processor initialization settings were changed to reduce the likelihood of a processor going into an error state and causing a system crash.
- FW188952: The minimum power consumption that must be reached before power capping occurs was lowered.
- FW188952: A problem was fixed that caused the service authority partition to receive platform dump notifications when an informational
error log entry was generated. This type of log should not be presented to the service authority partition's operating system because it does
not require a service action.
- FW198910: A problem was fixed that caused the high speed daughter card (HSDC) to show up as installed on the hardware VPD page on the
advanced management module (AMM), even though it was not installed, if the blade system had a PCI-X daughter card installed.
- FW198939: A problem was fixed that caused the front panel power LED to stay in the power off state, and activations of the power button
to be interpreted as power on requests, when the advanced management module's (AMM's) "Restart Blade System Management Processor" command was used to reset the blade system.
- FW199892: The firmware was enhanced so that a thermal alert on a blade system processor will not cause the advanced management module
(AMM) to permanently ramp up the speed of the BladeCenter's fans, even if the processor that reported the condition returned to a normal
temperature.
- FW200605: A problem was fixed that prevented the vital product data (VPD) for memory DIMMs to be viewed on the hardware VPD page on
the advanced management module (AMM) interface if there were unpopulated DIMM slots.
- FW202520: A problem was fixed that caused the serial-over-LAN (SOL) connection to be dropped between the service processor and the
advanced management module (AMM).
- FW202779: A problem was fixed that could cause duplicate IP addresses to be generated if a blade system was assigned an IP address
using the blades open fabric manager (BOFM), then moved to a BladeCenter on which the advanced management module (AMM) does not support BOFM.
Version 2.01, 01EA330_031_031 - 06/01/2008
Problems fixed:
- FW195738: A problem was fixed that prevented a new blade from being set up if the graphics console (via KVM - keyboard, video,
mouse) is not explicitly selected on the first opportunity, and there is a copper passthrough module (CPM) or optical passthrough
module (OPM) switch in position 1 instead of an Ethernet switch.
- 642765: A problem was fixed that caused booting from a fibre-channel-attached device to fail if a USB keyboard was
not plugged in, or the KVM (keyboard, video, mouse) was not assigned.
- 640199: A problem was fixed that prevented graphics on local and remote terminals from being displayed correctly.
Version 1.02, 01EA320_046_030 - 06/09/2008
The 1.02 firmware version (01EA320_046_030) must be applied to the target system if you wish to perform a live partition migration from systems with v1.00 (01EA320_030_030) or v1.01 (01EA320_040_030) firmware levels. The 1.02 version also supports partition migration with any system with v2.x (01EA330_031_031) or later firmware.
Details:
Attempts to migrate directly from version 1.01 and earlier to version 2.0 and later are blocked and one of the following errors
is reported on the IVM user interface:
"[VIOSE01042049-0503] Migration of partition with ID 3 has been stopped by the managed system. Additional information: 4200243"
or
"[VIOSE0109002C-0453] The Partition Firmware versions on the source and destination managed systems are not compatible. Additional
information: 1073741835"
Problems Fixed:
- 658900/FW197279 - HIPER - A problem was fixed that may cause a partition migration to hang under certain circumstances, with SRC BA00E840 being logged.
Version 1.01, 01EA320_040_030 - 03/17/2008
Problems fixed:
- 639455 - A problem was fixed that caused the panel buttons to be unresponsive.
- 649758: A problem was fixed that prevented power blades in the new versions of the BladeCenter media tray from booting from the
CD/DVD drive.
Version 1.00, 01EA320_030_030 - 11/30/2007
- Initial release
4.0 Unattended mode
N/A
5.0 Web information
Please refer to the BULL documentation (Ref: 86 X1 EW01 [medium:CDROM] ) for the current versions of EL260/460 BL460 product documentation and any late breaking product news. Supported Blade Center and / or EL260/460 BL460 Blade code updates (in addition to this Firmware) can also be downloaded from the IBM web site.
6.0 Notices and trademarks
THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY
KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR
FITNESS FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow
disclaimer of express or implied warranties in certain transactions,
therefore, this statement may not apply to you.
7.0 Disclaimer
THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF
ANY KIND. IBM & BULL DISCLAIM ALL WARRANTIES, WHETHER EXPRESS
OR IMPLIED, INCLUDING WITHOUT LIMITATION, THE IMPLIED
WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE AND
MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS
DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM & BULL GRANTS NO
LICENSES TO ANY PATENTS OR COPYRIGHTS.
