Troubleshooting
Problem
Users who have a single Advanced Management Module (AMM) in an IBM BladeCenter may see instances in the AMM Event Log stating a message similar to the following: 2 I SERVPROC 07/10/12 13:15:17 0x06000201 Management Module in bay 1 is primary. This indicates that the AMM has restarted. With a two AMM configuration, users may encounter instances where the secondary AMM unexpectedly becomes primary with the following messages logged in the event log: 2 I SERVPROC 07/10/12 13:15:17 0x06000201 Management Module in bay 1 is primary. If there was no user action taken to initiate the restart/failover, then this was an unexpected restart/failover. Such events will not affect production traffic from blades, but may interrupt management activities ongoing at the time of the reset/failover, such as Remote Control of Blades or Management Web sessions to the AMM. Recovery from these events is automatic and relatively quick. Recovery is fastest if there is a secondary AMM in place.
Resolving The Problem
Source
RETAIN tip: H206507
Symptom
Users who have a single Advanced Management Module (AMM) in an IBM BladeCenter may see instances in the AMM Event Log stating a message similar to the following:
| 2 I SERVPROC 07/10/12 13:15:17 0x06000201 Management Module in bay 1 is primary. |
This indicates that the AMM has restarted.
With a two AMM configuration, users may encounter instances where the secondary AMM unexpectedly becomes primary with the following messages logged in the event log:
| 2 I SERVPROC 07/10/12 13:15:17 0x06000201 Management Module in bay 1 is primary. |
If there was no user action taken to initiate the restart/failover, then this was an unexpected restart/failover.
Such events will not affect production traffic from blades, but may interrupt management activities ongoing at the time of the reset/failover, such as Remote Control of Blades or Management Web sessions to the AMM.
Recovery from these events is automatic and relatively quick. Recovery is fastest if there is a secondary AMM in place.
Affected configurations
The system may be any of the following IBM servers:
- BladeCenter Chassis, type 7967, any model
- BladeCenter E, type 8677, any model
- BladeCenter H, type 7989, any model
- BladeCenter H, type 8852, any model
- BladeCenter HT (AC), type 8750, any model
- BladeCenter HT (DC), type 8740, any model
- BladeCenter S, type 1948, any model
- BladeCenter S, type 7779, any model
- BladeCenter S, type 8886, any model
This tip is not software specific.
This tip is not option specific.
The system has the symptom described above.
Solution
Update the AMM firmware to the latest available.
The file is or will be available by selecting the appropriate Product Group, type of System, Product name, Product machine type, and operating system on IBM Support's Fix Central web page, at the following URL:
Workaround
The AMM is designed to recover quickly from such failure issues, in particular, when there is a secondary AMM available to take over immediately.
These issues can be ignored if impact to manageability is not seen as a major issue. At an appropriate maintenance window newer code should be installed to pick up fixes as found and implemented.
Additional information
Fixes are implemented in AMM firmware to correct unexpected resets or failovers as discovered and resolved.
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
14 April 2023
UID
ibm1MIGR-5091528