Dell OpenManage Server Administrator Version 5.1 Messages Reference Guide

Dell OpenManage™ Server

Administrator

Messages Reference Guide

www.dell.com | support.dell.com

Notes and Notices

NOTE: A NOTE indicates important information that helps you make better use of your computer.

NOTICE: A NOTICE indicates either potential damage to hardware or loss of data and tells you how to avoid the problem.

____________________

Reproduction in any manner whatsoever without the written permission of Dell Inc. is strictly forbidden. Trademarks used in this text: The DELL logo and Dell OpenManage are trademarks of Dell Inc.; Microsoft and Windows are registered

trademarks and Windows Server is a trademark of Microsoft Corporation; Red Hat is a registered trademark of Red registered trademark of Novell, Inc. in the United States and other countries.

Other trademarks and trade names may be used in this document to refer to either the entities claiming the marks and names or their products. Dell Inc. disclaims any proprietary interest in trademarks and trade names other than its own.

July 2006

Hat, Inc.; SUSE is a

Contents

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

What’s New in this Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Messages Not Described in This Guide

Understanding Event Messages

Sample Event Message Text

Viewing Alerts and Event Messages

. . . . . . . . . . . . . . . . . . . . . . 7

. . . . . . . . . . . . . . . . . . . . . . . . . . 8

. . . . . . . . . . . . . . . . . . . . . . . . . 9

. . . . . . . . . . . . . . . . . . . . . . . 9

Viewing Events in Windows 2000 Advanced Server and Windows Server 2003

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Viewing Events in Red Hat Enterprise Linux and SUSE Linux Enterprise Server

Viewing the Event Information Understanding the Event Description

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

. . . . . . . . . . . . . . . . . . . . . . . 11

. . . . . . . . . . . . . . . . . . . 12

2 Event Message Reference . . . . . . . . . . . . . . . . . . . . . . . 15

Miscellaneous Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Temperature Sensor Messages

Cooling Device Messages

Voltage Sensor Messages

Current Sensor Messages

Chassis Intrusion Messages

. . . . . . . . . . . . . . . . . . . . . . . . . 17

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

. . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Redundancy Unit Messages

Power Supply Messages

Memory Device Messages

Fan Enclosure Messages

AC Power Cord Messages

. . . . . . . . . . . . . . . . . . . . . . . . . . . 28

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

. . . . . . . . . . . . . . . . . . . . . . . . . . . 34

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Hardware Log Sensor Messages

Processor Sensor Messages

. . . . . . . . . . . . . . . . . . . . . . . . . . 39

. . . . . . . . . . . . . . . . . . . . . . . . 37

Contents 3

Pluggable Device Messages . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Battery Sensor Messages

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

3 System Event Log Messages for IPMI Systems. . . . . . . . . 45

Temperature Sensor Events . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Voltage Sensor Events

Fan Sensor Events

Processor Status Events

Power Supply Events

Memory ECC Events

BMC Watchdog Events

Memory Events

Hardware Log Sensor Events

Drive Events

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Intrusion Events

BIOS Generated System Events

R2 Generated System Events

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

. . . . . . . . . . . . . . . . . . . . . . . . . . 51

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

. . . . . . . . . . . . . . . . . . . . . . . . . 54

. . . . . . . . . . . . . . . . . . . . . . . . . . . 57

4 Contents

Cable Interconnect Events

Battery Events

Entity Presence Events

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

4 Storage Management Message Reference . . . . . . . . . . . 59

Alert Monitoring and Logging . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Alert Message Format with Substitution Variables

Alert Message Change History

Alert Descriptions and Corrective Actions

. . . . . . . . . . . . . . . . . . . . . . . . . 62

. . . . . . . . . . . . . . . 59

. . . . . . . . . . . . . . . . . . . 63

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Contents 5

6 Contents

Introduction

Dell OpenManage™ Server Administrator produces event messages stored primarily in the operating describes the event messages created by Server Administrator version 5.1 or later and displayed in the Server Administrator Alert log.

Server Administrator creates events in response to sensor status changes and other monitored parameters. The Server Administrator event monitor uses these status change events to add descriptive messages to the operating system event log or the Server Administrator Alert log.

Each event message that Server Administrator adds to the Alert log consists of a unique identifier called the event ID for a specific event source category and a descriptive message. The event message includes the severity, cause of the event, and other relevant information, such as the event location and the monitored item’s previous state.

Tables provided in this guide list all Server Administrator event IDs in numeric order. Each entry includes the event ID’s corresponding description, severity level, and cause. Message text in angle brackets (for example, Server

What’s New in this Release

• Modifications have been made to the Storage Management Service events. For more information,

system or Server Administrator event logs and sometimes in SNMP traps. This document

<State>

Administrator.

see “Alert Message Change History“.

) describes the event-specific information provided by the

Messages Not Described in This Guide

This guide describes only event messages created by Server Administrator and displayed in the Server Administrator Alert log. For information on other messages produced by your system, consult one of the following sources:

• Your system’s

• Other system documentation

• Operating system documentation

• Application program documentation

Installation and Troubleshooting Guide

Introduction 7

Understanding Event Messages

This section describes the various types of event messages generated by the Server Administrator. When

an event occurs on your system, the Server Administrator sends information about one of the

following event types to the systems management console:

Table 1-1. Understanding Event Messages

Icon Alert Severity Component Status

An event that describes the successful operation of a unit.

OK/Normal

Warning/Non-critical

Critical/Failure/Error

informational purposes and does not indicate an error condition. For example, the alert may indicate the normal start or stop of an operation, such as power supply or

sensor reading returning to normal.

An event that is not necessarily significant, but may indicate a possible future problem.

component (such as a temperature probe in an enclosure) has crossed a warning threshold.

A significant event that indicates actual or imminent loss of data or loss of function.

For example,

For example, a Warning/Non-critical alert may indicate that a

crossing a failure threshold or a hardware failure such as

Server Administrator generates events based on status changes in the following sensors:

•

Temperature Sensor

— Helps protect critical components by alerting the systems management console when temperatures become too high inside a chassis; also monitors a variety of locations in the chassis and in any attached systems.

•

Fan Sensor

•

Voltage Sensor

— Monitors fans in various locations in the chassis and in any attached systems.

— Monitors voltages across critical components in various chassis locations and in any

attached systems.

•

Current Sensor

— Monitors the current (or amperage) output from the power supply (or supplies) in

the chassis and in any attached systems.

•

Chassis Intrusion Sensor

•

Redundancy Unit Sensor

— Monitors intrusion into the chassis and any attached systems.

— Monitors redundant units (critical units such as fans, AC power cords, or power supplies) within the chassis; also monitors the chassis and any attached systems. For example, redundancy allows a second or

th fan to keep the chassis components at a safe temperature when another fan has failed. Redundancy is normal when the intended number of critical components are operating. Redundancy is degraded when a component fails, but others are still operating. Redundancy is lost when there is one less critical redundancy device than required.

•

Power Supply Sensor

Memory Prefailure Sensor

•

— Monitors power supplies in the chassis and in any attached systems.

— Monitors memory modules by counting the number of Error Correction

Code (ECC) memory corrections.

The alert is provided for

an array disk.

8 Introduction

•

Fan Enclosure Sensor

insertion into the system, and by measuring how long a fan enclosure is absent from the chassis. This sensor monitors the chassis and any attached systems.

•

AC Power Cord Sensor

Hardware Log Sensor

•

Processor Sensor

Pluggable Device Sensor

• pluggable devices, such as memory cards.

•

Battery Sensor

— Monitors the status of one or more batteries in the system.

— Monitors protective fan enclosures by detecting their removal from and

— Monitors the presence of AC power for an AC power cord.

— Monitors the size of a hardware log.

— Monitors the processor status in the system.

— Monitors the addition, removal, or configuration errors for some

Sample Event Message Text

The following example shows the format of the event messages logged by Server Administrator.

EventID: 1000

Source: Server Administrator

Category: Instrumentation Service

Type: Information

Date and Time: Mon Oct 21 10:38:00 2002

Computer:

Description:

Server Administrator starting

Data: Bytes in Hex

Viewing Alerts and Event Messages

An event log is used to record information about important events.

Server Administrator generates alerts that are added to the operating system event log and to the Server

Administrator Alert log. To view these alerts in Server Administrator:

Select the

You can also view the event log using your operating system’s event viewer. Each operating system’s event viewer accesses the applicable operating system event log.

System

object in the tree view.

Logs

tab.

Alert

subtab.

Introduction 9

The location of the event log file depends on the operating system you are using.

• In the Microsoft® Windows® 2000 Advanced Server and Windows Server™ 2003 operating systems, messages are logged to the system event log and optionally to a unicode text file, using Notepad), that is located in the

C:\Program Files\Dell\SysMgt

• In the Red Hat

Enterprise Linux and SUSE® Linux Enterprise Server operating system, messages are

install_path

\omsa\log

directory. The default

logged to the system log file. The default name of the system log file is

dcsys32.log

install_path

/var/log/messages

(viewable

. You can view

the messages file using a text editor such as vi or emacs.

NOTE: Logging messages to a unicode text file is optional. By default, the feature is disabled. To enable this

feature, modify the Event Manager section of the dcemdy32.ini file as follows:

• In Windows, locate the file at <install_path>\dataeng\ini and set

The default install_path is C:\Program Files\Dell\SysMgt. Restart the DSM SA Event Manager service.

• In Red Hat Enterprise Linux and SUSE Linux Enterprise Server, locate the file at <install_path>/dataeng/ini and

UnitextLog.enabled=True.

set "/etc/init.d/dataeng restart" command to restart the Server Administrator event manager service. This will also restart the Server Administrator data manager and SNMP services.

The default install_path is /opt/dell/srvadmin. Issue the

UnitextLog.enabled=True

The following subsections explain how to open the Windows 2000 Advanced Server, Windows Server 2003, and the Red Hat Enterprise Linux and SUSE Linux Enterprise Server event viewers.

Viewing Events in Windows 2000 Advanced Server and Windows Server 2003

Click the

Double-click

In the

The

Start

Administrative Tools

Event Viewer

System Log

button, point to

window, click the

Settings

, and click

Control Panel

, and then double-click

Tree

tab and then click

Event Viewer

window displays a list of recently logged events.

System Log

To view the details of an event, double-click one of the event items.

NOTE: You can also look up the dcsys32.log file, in the install_path\omsa\log directory, to view the separate

event log file. The default install_path is C:\Program Files\Dell\SysMgt.

Viewing Events in Red Hat Enterprise Linux and SUSE Linux Enterprise Server

Use a text editor such as vi or emacs to view the file named

The following example shows the Red Hat Enterprise Linux (and SUSE Linux Enterprise Server) message log, /var/log/messages. The

NOTE: These messages are typically displayed as one long line. In the following example, the message is

displayed using line breaks to help you see the message text more clearly.

10 Introduction

root

/var/log/messages

text in boldface type indicates the message text.

...

Feb 6 14:20:51 server01 Server Administrator: Instrumentation Service EventID: 1000

Server Administrator starting

Feb 6 14:20:51 server01 Server Administrator: Instrumentation Service EventID: 1001

Server Administrator startup complete

Feb 6 14:21:21 server01 Server Administrator: Instrumentation Service EventID: 1254 Chassis intrusion detected Sensor location: Main chassis

intrusion Chassis location: Main System Chassis Previous state was: OK (Normal) Chassis intrusion state: Open

Feb 6 14:21:51 server01 Server Administrator: Instrumentation Service EventID: 1252 Chassis intrusion returned to normal Sensor location: Main

chassis intrusion Chassis location: Main System Chassis Previous state was: Critical (Failed) Chassis intrusion state: Closed

Viewing the Event Information

The event log for each operating system contains some or all of the following information:

•

Date

— The date the event occurred.

•

Time

— The local time the event occurred.

•

Ty p e

— A classification of the event severity: Information, Warning, or Error.

User

•

— The name of the user on whose behalf the event occurred.

Computer

Source

Understanding the Event Description

Ta b l e 1-2 lists in alphabetical order each line item that may appear in the event description.

Table 1-2. Event Description Reference

Description Line Item Explanation

Action performed was:

Action requested was:

Additional Details:

details for the event>

Chassis intrusion state:

Chassis location:

chassis>

Configuration error type:

Current sensor value (in Amps):

Date and time of action:

Device location: <

chassis

Discrete current state:

Discrete temperature state:

<State>

<Additional

<Name of

Location in

<State>

Specifies the action that was performed, for example:

Action performed was: Power cycle

Specifies the action that was requested, for example:

Action requested was: Reboot, shutdown OS first

Specifies additional details available for the hot plug event, for example:

Memory device: DIMM1_A Serial number: FFFF30B1

Specifies information pertaining to the event, for example:

Power supply input AC is off, Power supply POK (power OK) signal is not normal, Power supply is turned off

Specifies the chassis intrusion state (open or closed), for example:

Chassis intrusion state: Open

Specifies name of the chassis that generated the message, for example:

Chassis location: Main System Chassis

Specifies the type of configuration error that occurred, for example:

Configuration error type: Revision mismatch

Specifies the current sensor value in amps, for example:

Current sensor value (in Amps): 7.853

Specifies the date and time the action was performed, for example:

Date and time of action: Sat Jun 12 16:20:33 2004

Specifies the location of the device in the specified chassis, for example:

Device location: Memory Card A

Specifies the state of the current sensor, for example:

Discrete current state: Good

Specifies the state of the temperature sensor, for example:

Discrete temperature state: Good

12 Introduction

Table 1-2. Event Description Reference (continued)

Description Line Item Explanation

Discrete voltage state:

Fan sensor value:

Log type:

Memory device bank location:

Memory device location:

Number of devices required for full redundancy:

Possible memory module event cause:

Power Supply type:

power supply>

Previous redundancy state was:

<State>

Previous state was:

Processor sensor status:

<State>

<type of

<State>

Specifies the state of the voltage sensor, for example:

Discrete voltage state: Good

Specifies the fan speed in revolutions per minute (RPM) or On/Off, for example:

Fan sensor value (in RPM): 2600

Fan sensor value: Off

Specifies the type of hardware log, for example:

Log type: ESM

Specifies the name of the memory bank in the system that generated the message, for example:

Memory device bank location: Bank_1

Specifies the location of the memory module in the chassis, for example:

Memory device location: DIMM_A

Specifies the number of power supply or cooling devices required to achieve full redundancy, for example:

Number of devices required for full redundancy: 4

Specifies a list of possible causes for the memory module event, for example:

Possible memory module event cause: Single bit warning error rate exceeded

Single bit error logging disabled

Specifies the type of power supply, for example:

Power Supply type: VRM

Specifies the status of the previous redundancy message, for example:

Previous redundancy state was: Lost

Specifies the previous state of the sensor, for example:

Previous state was: OK (Normal)

Specifies the status of the processor sensor, for example:

Processor sensor status: Configuration error

Introduction 13

Table 1-2. Event Description Reference (continued)

Description Line Item Explanation

Redundancy unit:

location in chassis>

Sensor location:

chassis>

Temperature sensor value:

Voltage sensor value (in Volts):

<Redundancy

<Location in

Specifies the location of the redundant power supply or cooling unit in the chassis, for example:

Redundancy unit: Fan Enclosure

Specifies the location of the sensor in the specified chassis, for example:

Sensor location: CPU1

Specifies the temperature in degrees Celsius, for example:

Temperature sensor value (in degrees Celsius): 30

Specifies the voltage sensor value in volts, for example:

Voltage sensor value (in Volts): 1.693

14 Introduction

Event Message Reference

The following tables lists in numerical order each event ID and its corresponding description, along with its severity and cause.

NOTE: For corrective actions, see the appropriate documentation.

Miscellaneous Messages

Miscellaneous messages in Table 2-1 indicate that certain alert systems are up and working.

Table 2-1. Miscellaneous Messages

Event ID Description Severity Cause

0000 Log was cleared Information User cleared the log from Server

Administrator.

0001 Log backup created Information The log was full, copied to backup, and

cleared.

1000 Server Administrator starting Information Server Administrator is beginning to

initialize.

1001 Server Administrator startup

complete

1002 A system BIOS update has been

scheduled for the next reboot

1003 A previously scheduled system

BIOS update has been canceled

1004 Thermal shutdown protection

has been initiated

Information Server Administrator completed its

initialization.

Information The user has chosen to update the flash

basic input/output system (BIOS).

Information The user decides to cancel the flash

BIOS update, or an error occurs during the flash.

Error This message is generated when a

system is configured for thermal shutdown due to an error event. If a temperature sensor reading exceeds the error threshold for which the system is configured, the operating system shuts down and the system powers off. This event may also be initiated on certain systems when a fan enclosure is removed from the system for an extended period of time.

Event Message Reference 15

Table 2-1. Miscellaneous Messages (continued)

Event ID Description Severity Cause

1005 SMBIOS data is absent Warning The system does not contain the

required systems management BIOS version 2.2 or higher, or the BIOS is corrupted.

1006 Automatic System Recovery

(ASR) action was performed

Action performed was:

Date and time of action:

and time>

1007 User initiated host system

control action

Action requested was:

1008 Systems Management Data

Manager Started

1009 Systems Management Data

Manager Stopped

1011 RCI table is corrupt Warning This message is generated when the

1012 IPMI Status

Interface: <

being used

the IPMI interface

>, <

additional

<Date

information if available and applicable

Error This message is generated when an

automatic system recovery action is

Information User requested a host system control

Information Systems Management Data Manager

Information This message is generated to indicate

performed due to a hung operating system. The action performed and the time of action are provided.

action to reboot, power off, or power cycle the system. Alternatively the user had indicated protective measures to be initiated in the event of a thermal shutdown.

services were started.

services were stopped.

BIOS Remote Configuration Interface (RCI) table is corrupted or cannot be read by the systems management software.

the Intelligent Platform Management Interface (IPMI)) status of the system.

Additional information, when available, includes Baseboard Management Controller (BMC) not present, BMC not responding, System Event Log (SEL) not present, and SEL Data Record (SDR) not present.

16 Event Message Reference

Temperature Sensor Messages

Temperature sensors listed in Table 2-2 help protect critical components by alerting the systems management console when temperatures become too high inside a chassis. The temperature sensor messages use additional variables: sensor location, chassis location, previous state, and temperature sensor value or state.

Table 2-2. Temperature Sensor Messages

Event ID Description Severity Cause

1050 Temperature sensor has failed

Sensor location: <Location in chassis>

Chassis location: <Name of chassis>

Previous state was: <State>

If sensor type is not discrete:

Temperature sensor value (in degrees Celsius):

If sensor type is discrete:

Discrete temperature state:

<State>

1051 Temperature sensor value

unknown

Sensor location: <Location in chassis>

Chassis location: <Name of chassis>

If sensor type is not discrete:

Temperature sensor value (in degrees Celsius):

If sensor type is discrete:

Discrete temperature state:

<State>

Information A temperature sensor on the backplane

board, system board, or the carrier in the specified system failed. The sensor location, chassis location, previous state, and temperature sensor value are provided.

Information A temperature sensor on the backplane

board, system board, or drive carrier in the specified system could not obtain a reading. The sensor location, chassis location, previous state, and a nominal temperature sensor value are provided.

Event Message Reference 17

Table 2-2. Temperature Sensor Messages (continued)

Event ID Description Severity Cause

1052 Temperature sensor returned

to a normal value

Sensor location:

<Location in

chassis>

Chassis location:

<Name of

chassis>

Previous state was:

If sensor type is not discrete:

Temperature sensor value (in degrees Celsius):

If sensor type is discrete:

Discrete temperature state:

<State>

Information A temperature sensor on the backplane

board, system board, or drive carrier in the specified system returned to a valid range after crossing a failure threshold. The sensor location, chassis location, previous state, and temperature sensor value are provided.

<State>

1053 Temperature sensor detected

a warning value

Sensor location:

<Location in

chassis>

Chassis location:

<Name of

chassis>

Previous state was:

If sensor type is not discrete:

Temperature sensor value (in degrees Celsius):

If sensor type is discrete:

Discrete temperature state:

<State>

Warning A temperature sensor on the backplane

board, system board, or drive carrier in the specified system exceeded its warning threshold. The sensor location, chassis location, previous state, and temperature sensor value are provided.

<State>

18 Event Message Reference

Table 2-2. Temperature Sensor Messages (continued)

Event ID Description Severity Cause

1054 Temperature sensor detected

a failure value

Sensor location:

<Location in

chassis>

Chassis location:

<Name of

chassis>

Previous state was:

If sensor type is not discrete:

Temperature sensor value (in degrees Celsius):

If sensor type is discrete:

Discrete temperature state:

<State>

Error A temperature sensor on the backplane

board, system board, or drive carrier in the specified system exceeded its failure threshold. The sensor location, chassis location, previous state, and temperature sensor value are provided.

<State>

1055 Temperature sensor detected

a non-recoverable value

Sensor location:

<Location in

chassis>

Chassis location:

<Name of

chassis>

Previous state was:

If sensor type is not discrete:

Temperature sensor value (in degrees Celsius):

If sensor type is discrete:

Discrete temperature state:

<State>

Error A temperature sensor on the backplane

board, system board, or drive carrier in the specified system detected an error from which it cannot recover. The sensor location, chassis location, previous state, and temperature sensor value are provided.

<State>

Event Message Reference 19

Cooling Device Messages

Cooling device sensors listed in Table 2-3 monitor how well a fan is functioning. Cooling device messages provide status and warning information for fans in a particular chassis.

Table 2-3. Cooling Device Messages

Event ID Description Severity Cause

1100 Fan sensor has failed

Sensor location: <Location in chassis>

Chassis location: <Name of chassis>

Previous state was: <State>

Fan sensor value:

1101 Fan sensor value unknown

Sensor location: <Location in chassis>

Chassis location: <Name of chassis>

Previous state was: <State>

Fan sensor value:

1102 Fan sensor returned to a

normal value

Sensor location:

in chassis>

Chassis location:

chassis>

Previous state was:

Fan sensor value:

1103 Fan sensor detected a

warning value

Sensor location:

in chassis>

Chassis location:

chassis>

Previous state was:

Fan sensor value:

<Location

<Name of

<State>

<Location

<Name of

<State>

Information A fan sensor in the specified system is not

functioning. The sensor location, chassis location, previous state, and fan sensor value are provided.

Information A fan sensor in the specified system could not

obtain a reading. The sensor location, chassis location, previous state, and a nominal fan sensor value are provided.

Information A fan sensor reading on the specified system

returned to a valid range after crossing a warning threshold. The sensor location, chassis location, previous state, and fan sensor value are provided.

Warning A fan sensor reading in the specified system

exceeded a warning threshold. The sensor location, chassis location, previous state, and fan sensor value are provided.

20 Event Message Reference

Table 2-3. Cooling Device Messages (continued)

Event ID Description Severity Cause

1104 Fan sensor detected a

failure value

Sensor location:

<Location

in chassis>

Chassis location:

<Name of

Error A fan sensor in the specified system detected

the failure of one or more fans. The sensor location, chassis location, previous state, and fan sensor value are provided.

chassis>

Previous state was:

Fan sensor value:

1105 Fan sensor detected a

non-recoverable value

Sensor location:

in chassis>

Chassis location:

<State>

<Location

<Name of

Error A fan sensor detected an error from which it

cannot recover. The sensor location, chassis location, previous state, and fan sensor value are provided.

chassis>

Previous state was:

Fan sensor value:

<State>

Voltage Sensor Messages

Voltage sensors listed in Table 2-4 monitor the number of volts across critical components. Voltage sensor messages provide status and warning information for voltage sensors in a particular chassis.

Table 2-4. Voltage Sensor Messages

Event ID Description Severity Cause

1150 Voltage sensor has failed

Sensor location: <Location in chassis>

Chassis location: <Name of chassis>

Previous state was: <State>

If sensor type is not discrete:

Voltage sensor value (in Volts):

If sensor type is discrete:

Discrete voltage state:

<State>

Information A voltage sensor in the specified system

failed. The sensor location, chassis location, previous state, and voltage sensor value are provided.

Event Message Reference 21

Table 2-4. Voltage Sensor Messages (continued)

Event ID Description Severity Cause

1151 Voltage sensor value unknown

Sensor location: <Location in chassis>

Chassis location: <Name of chassis>

Previous state was: <State>

If sensor type is not discrete:

Voltage sensor value (in Volts):

If sensor type is discrete:

Discrete voltage state:

1152 Voltage sensor returned to a

normal value

Sensor location: <Location in chassis>

Chassis location: <Name of chassis>

Previous state was: <State>

If sensor type is not discrete:

Voltage sensor value (in Volts):

If sensor type is discrete:

Discrete voltage state:

1153 Voltage sensor detected a

warning value

Sensor location: <Location in chassis>

Chassis location: <Name of chassis>

Previous state was: <State>

If sensor type is not discrete:

Voltage sensor value (in Volts):

If sensor type is discrete:

Discrete voltage state:

<State>

<State>

<State>

Information A voltage sensor in the specified system

could not obtain a reading. The sensor location, chassis location, previous state, and a nominal voltage sensor value are provided.

Information A voltage sensor in the specified system

returned to a valid range after crossing a failure threshold. The sensor location, chassis location, previous state, and voltage sensor value are provided.

Warning A voltage sensor in the specified system

exceeded its warning threshold. The sensor location, chassis location, previous state, and voltage sensor value are provided.

22 Event Message Reference

Table 2-4. Voltage Sensor Messages (continued)

Event ID Description Severity Cause

1154 Voltage sensor detected a

failure value

Sensor location: <Location in chassis>

Chassis location: <Name of chassis>

Previous state was: <State>

If sensor type is not discrete:

Voltage sensor value (in Volts):

If sensor type is discrete:

Discrete voltage state:

1155 Voltage sensor detected a

non-recoverable value

Sensor location: <Location in chassis>

Chassis location: <Name of chassis>

Previous state was: <State>

If sensor type is not discrete:

Voltage sensor value (in Volts):

If sensor type is discrete:

Discrete voltage state:

<State>

<State>

Error A voltage sensor in the specified system

exceeded its failure threshold. The sensor location, chassis location, previous state, and voltage sensor value are provided.

Error A voltage sensor in the specified system

detected an error from which it cannot recover. The sensor location, chassis location, previous state, and voltage sensor value are provided.

Event Message Reference 23

Current Sensor Messages

Current sensors listed in Table 2-5 measure the amount of current (in amperes) that is traversing critical components. Current sensor messages provide status and warning information for current sensors in a particular chassis.

Table 2-5. Current Sensor Messages

Event ID Description Severity Cause

1200 Current sensor has failed

Sensor location: <Location in chassis>

Chassis location: <Name of chassis>

Previous state was: <State>

If sensor type is not discrete:

Current sensor value (in Amps):

If sensor type is discrete:

Discrete current state:

<State>

1201 Current sensor value unknown

Sensor location: <Location in chassis>

Chassis location: <Name of chassis>

Previous state was: <State>

If sensor type is not discrete:

Current sensor value (in Amps):

If sensor type is discrete:

Discrete current state:

<State>

Information A current sensor on the power supply for the

specified system failed. The sensor location, chassis location, previous state, and current sensor value are provided.

Information A current sensor on the power supply for the

specified system could not obtain a reading. The sensor location, chassis location, previous state, and a nominal current sensor value are provided.

24 Event Message Reference

Table 2-5. Current Sensor Messages (continued)

Event ID Description Severity Cause

1202 Current sensor returned to

a normal value

Sensor location: <Location in chassis>

Chassis location: <Name of chassis>

Previous state was: <State>

If sensor type is not discrete:

Current sensor value (in Amps):

If sensor type is discrete:

Discrete current state:

Information A current sensor on the power supply for the

specified system returned to a valid range after crossing a failure threshold. The sensor location, chassis location, previous state, and current sensor value are provided.

<State>

1203 Current sensor detected a

warning value

Sensor location: <Location in chassis>

Chassis location: <Name of chassis>

Previous state was: <State>

If sensor type is not discrete:

Current sensor value (in Amps):

If sensor type is discrete:

Discrete current state:

Warning A current sensor on the power supply for the

specified system exceeded its warning threshold. The sensor location, chassis location, previous state, and current sensor value are provided.

<State>

Event Message Reference 25

Table 2-5. Current Sensor Messages (continued)

Event ID Description Severity Cause

1204 Current sensor detected a

failure value

Sensor location: <Location in chassis>

Chassis location: <Name of chassis>

Previous state was: <State>

If sensor type is not discrete:

Current sensor value (in Amps):

If sensor type is discrete:

Discrete current state:

Error A current sensor on the power supply for the

specified system exceeded its failure threshold. The sensor location, chassis location, previous state, and current sensor value are provided.

<State>

1205 Current sensor detected a

non-recoverable value

Sensor location: <Location in chassis>

Chassis location: <Name of chassis>

Previous state was: <State>

If sensor type is not discrete:

Current sensor value (in Amps):

If sensor type is discrete:

Discrete current state:

Error A current sensor in the specified system

detected an error from which it cannot recover. The sensor location, chassis location, previous state, and current sensor value are provided.

<State>

26 Event Message Reference

Chassis Intrusion Messages

Chassis intrusion messages listed in Table 2-6 are a security measure. Chassis intrusion means that someone is opening the cover to a system’s chassis. Alerts are sent to prevent unauthorized removal of parts from a chassis.

Table 2-6. Chassis Intrusion Messages

Event ID Description Severity Cause

1250 Chassis intrusion sensor has

failed

Sensor location: <Location in chassis>

Chassis location: <Name of chassis>

Previous state was: <State>

Chassis intrusion state:

1251 Chassis intrusion sensor

value unknown

Sensor location: <Location in chassis>

Chassis location: <Name of chassis>

Previous state was: <State>

Chassis intrusion state:

1252 Chassis intrusion returned

to normal

Sensor location: <Location in chassis>

Chassis location: <Name of chassis>

Previous state was: <State>

Chassis intrusion state:

Information A chassis intrusion sensor in the specified

system failed. The sensor location, chassis location, previous state, and chassis intrusion state are provided.

Information A chassis intrusion sensor in the specified

system could not obtain a reading. The sensor location, chassis location, previous state, and chassis intrusion state are provided.

Information A chassis intrusion sensor in the specified

system detected that a cover was opened while the system was operating but has since been replaced. The sensor location, chassis location, previous state, and chassis intrusion state are provided.

Event Message Reference 27

Table 2-6. Chassis Intrusion Messages (continued)

Event ID Description Severity Cause

1253 Chassis intrusion in

progress

Sensor location: <Location in chassis>

Chassis location: <Name of chassis>

Previous state was: <State>

Chassis intrusion state:

1254 Chassis intrusion detected

Sensor location: <Location in chassis>

Chassis location: <Name of chassis>

Previous state was: <State>

Chassis intrusion state:

1255 Chassis intrusion sensor

detected a non-recoverable value

Sensor location: <Location in chassis>

Chassis location: <Name of chassis>

Previous state was: <State>

Chassis intrusion state:

Warning A chassis intrusion sensor in the specified

system detected that a system cover is currently being opened and the system is operating. The sensor location, chassis location, previous state, and chassis intrusion state are provided.

Error A chassis intrusion sensor in the specified

system detected that the system cover was opened while the system was operating. The sensor location, chassis location, previous state, and chassis intrusion state are provided.

Error A chassis intrusion sensor in the specified

system detected an error from which it cannot recover. The sensor location, chassis location, previous state, and chassis intrusion state are provided.

Redundancy Unit Messages

Redundancy means that a system chassis has more than one of certain critical components. Fans and power supplies, for example, are so important for preventing damage or disruption of a computer system that a chassis may have “extra” fans or power supplies installed. Redundancy allows a second or nth fan to keep the chassis components at a safe temperature when the primary fan has failed. Redundancy is normal when the intended number of critical components are operating. Redundancy is degraded when a component fails but others are still operating. Redundancy is lost when the number of components functioning falls below the redundancy threshold.

28 Event Message Reference

Ta b l e 2-7 lists the redundancy unit messages.

The number of devices required for full redundancy is provided as part of the message, when applicable, for the redundancy unit and the platform. For details on redundancy computation, see the respective platform documentation.

Table 2-7. Redundancy Unit Messages

Event ID Description Severity Cause

1300 Redundancy sensor has failed

Redundancy unit:

<Redundancy

location in chassis>

Chassis location: <Name of chassis>

Previous redundancy state was:

<State>

1301 Redundancy sensor value

unknown

Redundancy unit:

<Redundancy

location in chassis>

Chassis location: <Name of chassis>

Previous redundancy state was:

<State>

1302 Redundancy not applicable

Redundancy unit:

<Redundancy

location in chassis>

Chassis location: <Name of chassis>

Previous redundancy state was:

<State>

1303 Redundancy is offline

Redundancy unit:

<Redundancy

location in chassis>

Chassis location: <Name of chassis>

Previous redundancy state was:

<State>

Information A redundancy sensor in the specified system

failed. The redundancy unit location, chassis location, previous redundancy state, and the number of devices required for full redundancy are provided.

Information A redundancy sensor in the specified system

could not obtain a reading. The redundancy unit location, chassis location, previous redundancy state, and the number of devices required for full redundancy are provided.

Information A redundancy sensor in the specified system

detected that a unit was not redundant. The redundancy location, chassis location, previous redundancy state, and the number of devices required for full redundancy are provided.

Information A redundancy sensor in the specified system

detected that a redundant unit is offline. The redundancy unit location, chassis location, previous redundancy state, and the number of devices required for full redundancy are provided.

Event Message Reference 29

Table 2-7. Redundancy Unit Messages (continued)

Event ID Description Severity Cause

1304 Redundancy regained

Redundancy unit:

<Redundancy

location in chassis>

Chassis location: <Name of chassis>

Previous redundancy state was:

Information A redundancy sensor in the specified system

detected that a “lost” redundancy device has been reconnected or replaced; full redundancy is in effect. The redundancy unit location, chassis location, previous redundancy state, and the number of devices required for full redundancy are provided.

<State>

1305 Redundancy degraded

Redundancy unit:

<Redundancy

location in chassis>

Chassis location: <Name of chassis>

Previous redundancy state was:

Warning A redundancy sensor in the specified system

detected that one of the components of the redundancy unit has failed but the unit is still redundant. The redundancy unit location, chassis location, previous redundancy state, and the number of devices required for full redundancy are provided.

<State>

1306 Redundancy lost

Redundancy unit:

location in chassis>

Chassis location: <Name of chassis>

Previous redundancy state was:

<Redundancy

Warning or Error (depending on the number of units that are functional)

A redundancy sensor in the specified system detected that one of the components in the redundant unit has been disconnected, has failed, or is not present. The redundancy unit location, chassis location, previous redundancy state, and the number of devices required for full redundancy are provided.

<State>

30 Event Message Reference

+ 102 hidden pages