Dell OpenManage Server Administrator Version 6.1 Messages Reference Guide

Dell™ OpenManage™

Server Administrator Version 6.1

Messages Reference Guide

Notes and Cautions

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

your computer.

CAUTION: A CAUTION indicates potential damage to hardware or loss of data if

instructions are not followed.

____________________

Reproduction of these materials in any manner whatsoever without the written permission of Dell Inc. is strictly forbidden.

Trademarks used in this text: Dell, the DELL logo and Dell OpenManage are trademarks of Dell Inc.; VMware is registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions; Microsoft, Windows, and W indows Server are either trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries; Red Hat and Red Hat Enterprise Linux are registered trademarks of Red Hat, Inc. in the United States and other countries; SUSE is a 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.

April 2009

Contents

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

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

Messages Not Described in This Guide

Understanding Event Messages

Sample Event Message Text

Viewing Alerts and Event Messages

Logging Messages to a Unicode Text File

. . . . . . . . . 9

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

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

. . . . . . . . . . 11

. . . . . 12

Viewing Events in Windows 2000 Advanced Server and Windows Server 2003

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

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

. . . . . . . . . 13

Viewing Events in VMware ESXi version 3.5 update 4

Viewing the Event Information

Understanding the Event Description

. . . . . . . . . . . . . . . . 14

. . . . . . . . . . . 14

. . . . . . . 14

2 Event Message Reference . . . . . . . . . . . 19

Miscellaneous Messages . . . . . . . . . . . . . . . . 19

Temperature Sensor Messages

. . . . . . . . . . . . . 22

Cooling Device Messages

Voltage Sensor Messages

. . . . . . . . . . . . . . . 25

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

Contents 3

Current Sensor Messages . . . . . . . . . . . . . . . . 30

Chassis Intrusion Messages

Redundancy Unit Messages

Power Supply Messages

Memory Device Messages

Fan Enclosure Messages

AC Power Cord Messages

. . . . . . . . . . . . . . 33

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

. . . . . . . . . . . . . . . . 38

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

. . . . . . . . . . . . . . . . 43

. . . . . . . . . . . . . . . . 45

Hardware Log Sensor Messages . . . . . . . . . . . . 46

Processor Sensor Messages

Pluggable Device Messages

Battery Sensor Messages

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

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

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

Chassis Management Controller Messages

3 System Event Log Messages

for IPMI Systems

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

. . . . . . 55

4 Contents

Temperature Sensor Events . . . . . . . . . . . . . . . 57

Voltage Sensor Events

Fan Sensor Events

Processor Status Events

Power Supply Events

Memory ECC Events

BMC Watchdog Events

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

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

. . . . . . . . . . . . . . . . . 61

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

. . . . . . . . . . . . . . . . . . . 64

. . . . . . . . . . . . . . . . . 64

Memory Events . . . . . . . . . . . . . . . . . . . . . 65

Hardware Log Sensor Events

Drive Events

Intrusion Events

. . . . . . . . . . . . . . . . . . . . . . . 67

. . . . . . . . . . . . . . . . . . . . . 68

BIOS Generated System Events

R2 Generated System Events

Cable Interconnect Events

Battery Events . . . . . . . . . . . . . . . . . . . . . . 76

Power And Performance Events

Entity Presence Events

. . . . . . . . . . . . . . . . . 77

4 Storage Management

Message Reference

Alert Monitoring and Logging . . . . . . . . . . . . . . 79

Alert Message Format with Substitution Variables

. . . . . . . . . . . . . . . . . . . . . . . . . 80

. . . . . . . . . . . . . . . . 79

. . . . . . . . . . . . . . 66

. . . . . . . . . . . . . 69

. . . . . . . . . . . . . . 75

. . . . . . . . . . . . . . . 76

. . . . . . . . . . . . 77

Alert Message Change History

Alert Descriptions and Corrective Actions

. . . . . . . . . . . . . 83

. . . . . . . 84

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

Contents 5

6 Contents

Introduction

Dell™OpenManage™ Server Administrator produces event messages stored primarily in the operating system or Server Administrator event logs and sometimes in SNMP traps. This document describes the event messages created by Server Administrator version 6.1 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, event-specific information provided by the Server Administrator.

<State>

) describes the

Introduction 7

What’s New in this Release

The following changes have been made to this guide for this release:

• Added the following new alerts in the “Storage Management Message Reference” section:

– 2370

– 2383

– 2384

– 2385

– 2386

• Updated the SNMP trap numbers for the following Storage Management alerts:

– 2060

– 2075

– 2087

– 2125

– 2287

• Deleted alerts 2206 and 2207 in the “Storage Management Message Reference” section.

• Added a new alert 2382 in the “Alert Descriptions and Corrective Actions” section.

• Added two alerts 1013 and 1014 in the “Miscellaneous Messages” section.

• Added the POST Code Errors table in the “BIOS Generated System Events” section.

• Support for the VMware® ESXi version 3.5 Update 4 hypervisor and 4.0.

• Support for the Server Administrator Web Server.

• Support for Solid State Drives (SSD).

• Supports Serial Attached SCSI (SAS) controllers.

8 Introduction

Messages Not Described in This Guide

This guide describes only event messages logged by Server Administrator and Storage Management that are displayed in the Server Administrator Alert log. For information on other messages produced by your system, see one of the following sources:

• Your system’s

Installation and Troubleshooting Guide or Hardware Owner's

Manual.

• Operating system documentation

• Application program documentation

Understanding Event Messages

This section describes the various types of event messages generated by the Server Administrator. When an event occurs on your system, 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

OK /Normal / Informational

Warning / Non-critical

Critical / Failure / Error

An event that describes the successful operation of a unit.

The alert is provided for 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 a

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

alert may indicate that a 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. threshold or a hardware failure such as

sensor reading returning to normal.

For example, a Warning/Non-critical

For exam ple,

crossing a failure

an array disk.

Introduction 9

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

— Monitors fans in various locations in the chassis and in any

attached systems.

•

Voltage Sensor

— 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

— Monitors intrusion into the chassis and any

attached systems.

•

Redundancy Unit Sensor

— 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

— Monitors power supplies in the chassis and in any

attached systems.

•

Memory Prefailure Sensor

— Monitors memory modules by counting the

number of Error Correction Code (ECC) memory corrections.

•

Fan Enclosure Sensor

— Monitors protective fan enclosures by detecting their removal from and 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

— Monitors the presence of AC power for an

AC power cord.

•

Hardware Log Sensor

— Monitors the size of a hardware log.

10 Introduction

•

Processor Sensor

•

Pluggable Device Sensor

or configuration errors for some pluggable devices, such as memory cards.

•

Battery Sensor

the system.

— Monitors the processor status in the system.

— Monitors the addition, removal,

— Monitors the status of one or more batteries in

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

Logs

tab.

Alert

subtab.

object in the tree view.

Introduction 11

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

• In the Microsoft® Windows® 2000 Advanced Server and Windows

• In the Red Hat

Server

2003 operating systems, messages are logged to the system event log and optionally to a Unicode text file, Notepad), that is located in the The default

install_path

Enterprise Linux®, SUSE® Linux Enterprise Server,

install_path

C:\Program Files\Dell\SysMgt

dcsys32.log

\omsa\log

(viewable using

directory.

and VMware ESXi version 3.5 update 4 operating systems, messages are logged to the system log file. The default name of the system log file is

var/log/messages

. You can view the messages file using a text editor such

as vi or emacs.

Logging Messages to a Unicode Text File

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 <

UnitextLog.enabled=True

Files\Dell\SysMgt

. Restart the

• In Red Hat Enterprise Linux and SUSE Linux Enterprise Server locate the file at <

install_path>

/dataeng/ini

UnitextLog.enabled=True

srvadmin

. Issue the

"/etc/init.d/dataeng restart"

Server Administrator event manager service. This will also restart the Server Administrator data manager and SNMP services.

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

install_path>

The default

\dataeng\ini

install_path

DSM SA Event Manager

and set

The default

install_path

command to restart the

version 3.5 update 4

event viewers.

and set

C:\Program

service.

/opt/dell/

Viewing Events in Windows 2000 Advanced Server and Windows Server 2003

Click the

Double-click

12 Introduction

Start

button, point to

Administrative Tools

Settings

, and click

Control Panel

, and then double-click

Event Viewer

In the

Event Viewer

The

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.

window, click the

Tree

tab and then click

System Log

window displays a list of recently logged events.

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

messages

The following example shows the Red Hat Enterprise Linux and SUSE Linux Enterprise Server message log, /var/log/messages. The text in boldface type indicates the message text.

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.

...

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

Server Administrator starting

root

/var/log/

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

Introduction 13

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

Viewing Events in VMware ESXi version 3.5 update 4

Click

Administration

Select

System Logs

Select

Server Log [/var/log/messages

NOTE: VMware® ESXi 3.5 update 4 does not support SNMP traps for this release.

on the navigation bar.

] entry on the drop-down list.

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

Table 1-2 lists in alphabetical order each line item that may appear in the event description.

14 Introduction

Table 1-2. Event Description Reference

Description Line Item Explanation

Action performed

was:

Action requested

was:

Additional Details:

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

Chassis intrusion state:

<Intrusion

state>

Chassis location:

Configuration error type:

Current sensor value (in Amps):

Date and time of action:

<Date and

time>

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

Introduction 15

Table 1-2. Event Description Reference (continued)

Description Line Item Explanation

Device location:

Location in

chassis

Discrete current state:

Discrete temperature state:

<State>

Discrete voltage state:

Fan sensor value:

<State>

Log type:

<Log

type>

Memory device bank location:

<Bank

name in chassis>

Memory device location:

Number of devices required for full redundancy:

Peak value (in Watts): <Reading>

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

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 the peak value in Watts, for example:

Peak value (in Watts): 1.693

16 Introduction

Table 1-2. Event Description Reference (continued)

Description Line Item Explanation

Possible memory module event cause:

Power Supply type:

Previous redundancy state was:

Previous state was:

<State>

Processor sensor status:

Redundancy unit:

Sensor location:

Temperature sensor value:

Voltage sensor value (in Volts):

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

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

Introduction 17

18 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 IDDescription 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

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

Information Server Administrator is

beginning to initialize.

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.

Event Message Reference 19

Table 2-1. Miscellaneous Messages (continued)

Event IDDescription Severity Cause

1004 Thermal shutdown

protection has been initiated

1005 SMBIOS data is absent Error The system does not contain

1006 Automatic System

Recovery (ASR) action was performed

Action performed was:

Date and time of action:

time>

1007 User initiated host

system control action

Action requested was:

<Date and

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.

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

Error This message is generated

when an automatic system recovery action is performed due to a hung operating system. The action performed and the time of action are provided.

Information User requested a host system

control 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.

20 Event Message Reference

Table 2-1. Miscellaneous Messages (continued)

Event IDDescription Severity Cause

1008 Systems Management

Data Manager Started

1009 Systems Management

Data Manager Stopped

1011 RCI table is corrupt Error This message is generated

1012 IPMI Status

Interface: <

the IPMI

interface being used

additional information if available and applicable

1013 System Peak Power

detected new peak value

Peak value (in Watts):<Reading>

1014 System software

event:<

Date and time of action:<

Description

Date and time

Information Systems Management

Data Manager services were started.

Information Systems Management

Data Manager services were stopped.

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

Information This message is generated

to indicate the Intelligent

Information The system peak power sensor

Warning This event is generated when

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.

detected a new peak value in power consumption. The new peak value in Watts is provided.

the systems management agent detects a critical system software generated event in the system event log which could have been resolved.

Event Message Reference 21

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 IDDescription 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>

Error 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.

22 Event Message Reference

Table 2-2. Temperature Sensor Messages (continued)

Event IDDescription 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>

<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>

<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.

Warning A temperature

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

Event Message Reference 23

Table 2-2. Temperature Sensor Messages (continued)

Event IDDescription 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>

<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>

<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.

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.

24 Event Message Reference

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 IDDescription 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:

<Location in

chassis>

Chassis location:

<Name of

chassis>

Previous state was:

Fan sensor value:

<State>

Error A fan sensor in the

specified system is not functioning. The sensor location, chassis location, previous state, and fan sensor value are provided.

Error 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.

Event Message Reference 25

Table 2-3. Cooling Device Messages (continued)

Event IDDescription Severity Cause

1103 Fan sensor detected a warning

value

Sensor location:

<Location in

chassis>

Chassis location:

<Name of

chassis>

Previous state was:

Fan sensor value:

1104 Fan sensor detected a failure

value

Sensor location:

<State>

<Location in

chassis>

Chassis location:

<Name of

chassis>

Previous state was:

Fan sensor value:

1105 Fan sensor detected a

non-recoverable value

Sensor location:

<State>

<Location in

chassis>

Chassis location:

<Name of

chassis>

Previous state was:

Fan sensor value:

<State>

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.

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.

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.

26 Event Message Reference

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 IDDescription 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>

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:

<State>

Error A voltage sensor in

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

Warning 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.

Event Message Reference 27

Table 2-4. Voltage Sensor Messages (continued)

Event IDDescription Severity Cause

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:

<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>

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.

28 Event Message Reference

Table 2-4. Voltage Sensor Messages (continued)

Event IDDescription 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:

<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>

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 29

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 IDDescription 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):

Current sensor value (in Watts):

If sensor type is discrete:

Discrete current state:

Error A current sensor

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

<State>

30 Event Message Reference

+ 222 hidden pages