Skip to main content

CMM event log

The CMM event log contains a list of all events that are received from all devices in the Flex System Carrier-Grade chassis.

You can view the Chassis Management Module event log by using the CMM command-line interface displaylog command or through the CMM web interface.

Communications errors from the compute nodes can take up to 20 minutes to appear in the CMM event log.

When you read the CMM event log, the most recent events are displayed first. There are user responses in each of the event messages. The user response is intended to resolve problems that are active events. However, there are cases where the problem might have recovered without intervention. If the problem is not an active event, there might be a log entry indicating that it has already recovered. Before you perform the tasks indicated in the user response, verify that the problem remains an active event. If it is not an active event, look for a log entry that indicates it has recovered.

When an error condition has recovered, the event log entry for the recovery will contain the same event id, description, and user action as the original event. You must read the event text to determine if the message is a recovery event or a problem event.

For example, the problem statement for event 000A6001 is: Fan module %s is operating in a degraded state.

The recovery statement for event 000A6001 is: Fan module %s has returned to normal speed operation.

Unresolved problems will be regenerated if they still exist. For example, if there was a CMM failover or restart, the active events list will be recreated. Note also that the CMM log does not refresh.

Before troubleshooting the Flex System Carrier-Grade chassis, make sure that the CMM firmware is the latest level available. Often problems have already been corrected and the fix is available with a firmware update. See ../com.lenovo.acc.cmm.doc/firmwareupdate.html for more information.
For each event code, the following fields are displayed:
Event identifier
An eight-character hexadecimal identifier that uniquely identifies an event or class of events. Event identifiers are displayed in the event log and in notifications (emails and SNMP alerts).
In SNMP alerts, the event identifier is displayed as a decimal number. You convert that integer into a hexadecimal number to map it to the event that is displayed in this document.
Event description
The logged message string that appears for an event. The logged message string that appears in this document is slightly different from the event string that appears in the event log.

When the event string is displayed in the event log, information such as a user ID or a specific node bay number is displayed. In this document, that additional information appears as [arg#].

Provides additional information to explain why the event occurred.
An indication of the level of concern for the condition. In the event log severity is abbreviated to the first character. The following table describes the severity levels.
Table 1. Severity levels.

The severity levels table is a two-column table that explains the severity levels of CMM events. Column 1 lists the severity level. Column 2 describes the severity level.

InformationalAn informational message is information that is recorded for audit purposes, usually a user action or a change of states that is normal behavior.
WarningA warning is not as severe as an error, but if possible, you should correct the condition before it becomes an error. It might also be a condition that requires additional monitoring or maintenance.
ErrorAn error typically indicates a failure or critical condition that impairs service or an expected function.
Alert category
Similar events are grouped together in categories. Information in the alert category field is displayed as component (severity).
Events are grouped into the following component categories:
  • Compute node
  • Chassis/System Management
  • Cooling devices
  • I/O modules
  • Inventory
  • Network change
  • Power supplies
  • Power on/off
In addition, the following categories are available:
  • Event log: Events related to the event log. For example, if the field Monitor log state events is enabled on the Event log page of the Chassis Management Module Web interface, events related to the log being 75% full and the log being 100% full are listed for this category.
  • User activity: Audit related events, such as when a user logs in to the Chassis Management Module Web interface.
Events are also grouped into the following severity levels:
  • Informational
  • Warning
  • Critical
    The severity Critical for the Alert Category field is the same as the severity Error in the Severity field.
Log source
Use the log source as an aid in determining which component has reported an event. The log source field shows one of the following sources:
  • Audit. A user action log.
  • Node_number. The compute node indicated by the bay number.
  • Cool_number. A fan module indicted by bay number.
  • IOMod_number. An I/O module indicated by the bay number.
  • Power_number . A power supply indicated by the bay number.
  • SERVPROC. The system-management processor for the CMM.
Automatically notify service
If this field is set to “Yes,” and you have enabled Electronic Service Agent on the Flex System Manager, Support will be notified automatically if the event is generated.

While waiting for Support to call, you can perform the recommended actions for the event.

If this field is a “Yes,” it indicates that the CMM can generate a message that shows the condition has recovered. This does not mean that the event is a recovery of the condition.

If the message is a recovery message, the CMM will typically prefix the message with the word “Recovery”. An example of a recoverable message is an over- temperature threshold event. A component alerts the CMM for an over-temperature condition and then recovers when the condition no longer exists.

If this field is a “No” then there is no possible recovery reported by the CMM. These are typically informational message such as a user has logged in, or a component was installed.

Chassis LEDs that are lit
Where appropriate, this field displays the chassis LEDs that are lit for an event. The front panel of a chassis provides LED indicators for power, faults, location, and a check logs indicator. Some events will cause an LED to illuminate. Other events, such as events from a compute node, are indicated through the chassis as well as through LEDs on the compute node. For example, if a compute node error LED is lit, the chassis error LED should also be lit.

For more information about chassis LEDs, see Front information panel LEDs and Chassis module LEDs.

The SNMP trap ID found in the SNMP alert management information base (MIB).
SNMP users will be notified of the alerts in the event categories via an SNMP trap. The traps are defined in mmalert.mib, which is distributed with the Chassis Management Module firmware. The following table shows the MIB Object and the Object Identifier (OID) for the selected alert category.

The SNMP trap ID table is a three-column table that shows the MIB Object and the Object Identifier (OID) for SNMP alert categories. Column 1 lists the alert categories. Column 2 identifies the associated MIB object. Column 3 lists the object identifier.

Alert categoriesMIB objectObject identifier
Chassis/System Management (Critical)mmTrapChassisC.
Cooling devices (Critical)mmTrapFanC.
Power supplies (Critical)mmTrapPsC.
Nodes (Critical)mmTrapBladeC.
I/O modules (Critical)mmTrapIOC.
Storage modules (Critical)mmTrapStorageC.
Chassis/System Management (Warning)mmTrapChassisN.
Cooling devices (Warning)mmTrapFanN.
Power supplies (Warning)mmTrapPowerN.
Nodes (Warning)mmTrapBladeN.
I/O modules (Warning)mmTrapION.
Storage Modules (Warning)mmTrapStorageN.
Event Log (Warning)mmTrapLogFullN.
Chassis/System Management (Informational)mmTrapChassisS.
Cooling devices (Informational)mmTrapFanS.
Power supplies (Informational)mmTrapPowerS.
Nodes (Informational)mmTrapBladeS.
I/O modules (Informational)mmTrapIOS.
Storage modules (Informational)mmTrapStorageS.
Event log (Informational)mmTrapSysLogS.
Power on/off (Informational)mmTrapPwrDOS.
Inventory change (Informational)mmTrapSysInvS.
Network change (Informational))mmTrapNwChangeS.
User activity (Informational)mmTrapRemoteLoginS.
Test messagemmTrapAppS.
User response
Indicates what actions you should perform to resolve the event. Perform the steps listed in this section in the order shown until the problem is resolved.

If, after performing all of the actions described in the User Response, you cannot resolve the problem, you can submit an Electronic Service Request. Submitting an Electronic Service Request will start the process of determining a solution to your problem by making the pertinent information available to Support.

If the call home capability is enabled (CMM Service Advisor or Flex System Manager Electronic Service Agent), the management device can automatically report serviceable events to Support and provide the associated system service information.

You can also go to Lenovo Data Center Support site to manually submit an Electronic Service Request.

This list includes error codes and messages that will only appear when certain chassis settings or options are installed.