The redundant management module is not failing over - IBM eServer BladeCenter (Type 8677)

Resolving The Problem

RETAIN tip H181093

The redundant management module is not failing over. The redundant management module is not the same firmware level as the primary.

The system may be any of the following IBM e(logo)servers:

• a BladeCenter, Type 8677, any model.

The system is configured with the following option(s):

• Redundant Management Module, option p/n 48P7055, FRU 73P9326.

Follow these steps to correctly upgrade to a redundant management module chassis. Do the following for each chassis:

1. With a single MM in the chassis, update the MM firmware to 1.04 release (or later), and reset it.
2. Allow the new code to run on the primary MM for approximately 2 minutes. This will allow the new MM time to copy some of the system parameters (e.g. the MM IP address) to an EEPROM on the midplane.
3. When new firmware is running on primary MM, insert the redundant MM into the chassis. The primary MM may note some warnings if it tries to contact the redundant MM and is unsuccessful. These should go away once the redundant MM firmware is brought up to date.
    
   Note: Depending upon the age of the firmware that comes preinstalled on the redundant MM, the MM may or may not know how to get its IP address from the midplane.
    
   The user may have to access the redundant MM using an address assigned by the DHCP server (or the default static IP 192.168.70.125) until the redundant MM is
   flashed with the latest firmware.
    
   Also be sure to flash all three MM packet files CNETBRUS.PKT, CNETMNUS.PKT, and CNETRGUS.PKT before restarting the MM.
    
   Note: Redundant MM's may come with BRET50,1.04, or later firmware - then only steps 1-3 need to be followed. If the redundant MM is below BRET50 or version 1.04 the following steps (4-6) must also be taken:
   
   
4. From same web page used to restart the primary MM, select the "Switch Over to Redundant MM" option. This will make the redundant MM prime.
5. Update the firmware on this MM to the same release as the original primary MM was updated to, then reset it.
6. When the new MM comes back up, switch back to the original primary MM. As soon as the redundant MM is inserted, the primary MM will copy its firmware revision to the redundant MM (assuming the revs are different). It will also copy its user and alert configuration information, and its event log to the redundant MM. The config and event information takes about two minutes to copy over. The firmware revs take about 10 minutes to copy over. Most of that time is used updating the main application.