Dell OpenManage Server Administrator Version 7.0 Messages Reference Guide

Dell OpenManage

Server Administrator

Version 7.0

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 OpenManage™ are trademarks of Dell Inc. Microsoft Microsoft Corporation in the United States and/or other countries. Red Hat Enterprise Linux Enterprise Linux countries. SUSE ™ is a trademark of Novell Inc. in the United States and other countries. Citrix Xen United States and/or other countries. VMware Inc. in the United States or 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.

, Windows®, and Windows Server® are either trademarks or registered trademarks of

are registered trademarks of Red Hat, Inc. in the United States and/or other

, and XenServer® are either registered trademarks or trademarks of Citrix Systems, Inc. in the

is registered trademarks or trademarks of VMWare,

and

2011 - 12

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

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

Messages Not Described in This Guide

. . . . . . . . . 8

Understanding Event Messages . . . . . . . . . . . . . 8

Sample Event Message Text

Viewing Alerts and Event Messages

Logging Messages to a Unicode Text File

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

. . . . . . . . . . 11

. . . . . 12

Viewing Events in

Microsoft Windows Server 2008 . . . . . . . . . . 12

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

. . . . . . . . . 13

Viewing Events in VMware ESX/ESXi . . . . . . . 14

Viewing the Event Information

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

Understanding the Event Description . . . . . . . 14

2 Server Management Messages . . . . . . . 19

Server Administrator General Messages . . . . . . . . 19

Temperature Sensor Messages

Cooling Device Messages

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

. . . . . . . . . . . . . . . 26

Voltage Sensor Messages

Current Sensor Messages

. . . . . . . . . . . . . . . 29

. . . . . . . . . . . . . . . . 32

Contents 3

Chassis Intrusion Messages . . . . . . . . . . . . . . 35

Redundancy Unit Messages

Power Supply Messages

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

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

Memory Device Messages . . . . . . . . . . . . . . . 46

Fan Enclosure Messages

AC Power Cord Messages

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

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

Hardware Log Sensor Messages . . . . . . . . . . . . 50

Processor Sensor Messages

Pluggable Device Messages

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

. . . . . . . . . . . . . . 55

Battery Sensor Messages . . . . . . . . . . . . . . . . 57

Secure Digital (SD) Card Device Messages

Chassis Management Controller Messages

3 Storage Management Message

Reference 65

. . . . . . 59

. . . . . . 63

4 Contents

Alert Monitoring and Logging . . . . . . . . . . . . . . 65

Alert Message Format with Substitution Variables

Alert Message Change History

Alert Descriptions and Corrective Actions

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

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

. . . . . . . 70

4 System Event Log Messages for

IPMI Systems 237

Temperature Sensor Events . . . . . . . . . . . . . . . 237

Voltage Sensor Events

Fan Sensor Events

. . . . . . . . . . . . . . . . . 239

. . . . . . . . . . . . . . . . . . . . 241

Processor Status Events . . . . . . . . . . . . . . . . 243

Power Supply Events

Memory ECC Events

. . . . . . . . . . . . . . . . . . 245

. . . . . . . . . . . . . . . . . . . 250

BMC Watchdog Events . . . . . . . . . . . . . . . . . 251

Memory Events

Hardware Log Sensor Events

. . . . . . . . . . . . . . . . . . . . . 252

. . . . . . . . . . . . . . 254

Drive Events . . . . . . . . . . . . . . . . . . . . . . . 255

Intrusion Events

BIOS Generated System Events

Operating System Generated System Events

Cable Interconnect Events

Battery Events

. . . . . . . . . . . . . . . . . . . . . 257

. . . . . . . . . . . . . 258

. . . . . . 268

. . . . . . . . . . . . . . . 269

. . . . . . . . . . . . . . . . . . . . . . 270

Power And Performance Events

Entity Presence Events

Miscellaneous

. . . . . . . . . . . . . . . . . 274

. . . . . . . . . . . . . . . . . . . . . . 275

. . . . . . . . . . . . 271

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279

Contents 5

6 Contents

Introduction

Dell OpenManage Server Administrator generates event messages stored primarily in the operating system or Server Administrator event logs and sometimes in Simple Network Management Protocol (SNMP) traps. This document describes the event messages that are created by Server Administrator version 7.0 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 previous state of the monitored item.

The tables in this guide list all Server Administrator event IDs in numeric order. Each entry includes the description, severity level, and cause of the event ID. The message text in angle brackets (for example, <State>) describes the event-specific information provided by the Server Administrator.

Introduction 7

What’s New in this Release

The following new alerts are added:

• 2425 - State change on Physical disk from READY to Non-RAID.

• 2426 - State change on Physical disk from Non-RAID to READY.

• 2429 - Drive Prepared for Removal.

• 2430 - Drive Log Exported.

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 generated by your system, see one of the following sources:

•The

• Operating system documentation

• Application program documentation

Installation and Troubleshooting Guide or Hardware Owner's Manual

shipped with your system

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

8 Introduction

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

sensor reading returning to normal.

Table 1-1. Understanding Event Messages

Icon Alert Severity Component Status

War n ing / Non-critical

Critical / Failure / Error

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

For example, a Warning/Non-critical

For example,

crossing a failure

an array disk.

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 the temperature in a variety of locations in the chassis and in attached system(s).

•

Fan Sensor

— Monitors fans in various locations in the chassis and in

attached system(s).

•

Volt age S enso r

— Monitors voltages across critical components in various

chassis locations and in attached system(s).

•

Current Sensor

— Monitors the current (or amperage) output from the

power supply (or supplies) in the chassis and in attached system(s).

•

Chassis Intrusion Sensor

— Monitors intrusion into the chassis and

attached system(s).

•

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 attached system(s). 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

attached system(s).

Introduction 9

•

Memory Prefailure Sensor

number of Error Correction Code (ECC) memory corrections.

•

Fan Enclosure Sensor

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 in attached system(s).

•

AC Power Cord Sensor

AC power cord.

•

Hardware Log Sensor

•

Processor Sensor

•

Pluggable Device Sensor

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

•

Battery Sensor

the system.

•

SD Card Device Sensor

card devices in the system.

— Monitors the processor status in the system.

— Monitors the status of one or more batteries in

— Monitors memory modules by counting the

— Monitors protective fan enclosures by detecting

— Monitors the presence of AC power for an

— Monitors the size of a hardware log.

— Monitors the addition, removal,

— Monitors instrumented Secure Digital (SD)

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: <computer name>

Description:

Server Administrator starting

Data: Bytes in Hex

10 Introduction

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.

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

• On systems running the Microsoft Windows operating systems, event messages are logged in the operating system event log and the Server Administrator event log.

• On systems running the Red Hat Enterprise Linux, SUSE Linux Enterprise Server, Citrix XenServer, VMware ESX, and VMware ESXi operating systems, the event messages are logged in the operating system log file and the Server Administrator event log.

System

object in the tree view.

Logs

tab.

Alert

tab.

NOTE: The Server Administrator event log file is named dcsys32.xml and is

located in the <install_path>\omsa\log directory. The default install_path is C:\Program Files\Dell\SysMgt.

NOTE: The default name of the operating system log file is /var/log/messages,

and you can view the operating system log file using a text editor such as vi or emacs. The Server Administrator event log file is named dcsys<xx>.xml, where xx is either 32 or 64 bit depending on the operating system. In the Red Hat Enterprise Linux, SUSE Linux Enterprise Server, Citrix XenServer and VMware ESX operating systems, the Server Administrator event log file is located in the /opt/dell/srvadmin/var/log/openmanage directory. In the VMware ESXi operating system, the Server Administrator event log file is located in the /etc/cim/dell/srvadmin/log/openmanage directory.

Introduction 11

Logging Messages to a Unicode Text File

Logging messages to a Unicode text file is optional. By default, the feature is disabled in the Server Administrator. To enable this feature, modify the

Event Manager section of the dcemdy<xx>.ini configuration file where xx is 32 or 64 bit depending on the operating system, as follows:

• On systems running Microsoft Windows operating systems, you can locate the configuration file in the the property

C:\Program Files\Dell\SysMgt

service to enable the setting. The Server Administrator Unicode text event log file is named <

install_path>\omsa\log directory

• On systems running the Red Hat Enterprise Linux, SUSE Linux Enterprise Server, Citrix XenServer and VMware ESX operating systems, you can locate the configuration file in the

srvadmin-deng/ini

UnitextLog.enabled=true restart

service and enable the setting. This also restarts the Server Administrator Data Manager and SNMP services. The Server Administrator Unicode text event log file is named on the operating system and is located in the

openmanage

• On systems running the in ESXi operating system the dcemdy32.ini file is located under /

dcsys<xx>.log

and is located under

The following sub-sections explain how to launch the Windows Server 2008, Red Hat Enterprise Linux, SUSE Linux Enterprise Server, VMware ESX, and VMware ESXi event viewers.

UnitextLog.enabled=true

dcsys32.log

directory and set the property

command to restart the Server Administrator Event Manager

directory.

etc/cim/dell/srvadmin/srvadmin-deng/ini/

where xx is 32 or 64 bit depending on the operating system

<install_path>\dataeng\ini

. The default

. Restart the

and is located in the

. Run the

dcsys<xx>.log

/etc/cim/dell/srvadmin/log/openmanage/

DSM SA Event Manager

/opt/dell/srvadmin/etc/

/etc/init.d/dataeng

where xx is 32 or 64 bit depending

/opt/dell/srvadmin/var/log/

directory and set

install_path

and the

Viewing Events in Microsoft Windows Server 2008

Click the

Double-click

In the

12 Introduction

Start

button, point to

Administrative Tools

Event Viewer

Settings

, and then double-click

window, click the

, and click

Tr ee

tab and then click

Control Panel

Event Viewer

System Log

The

System Log

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

NOTE: You can also look up the dcsys<xx>.xml file, in the

<install_path>\omsa\log directory, to view the separate event log file, where the default install_path is C:\Program Files\Dell\SysMgt and xx is 32 or 64 depending on the operating system that is installed.

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

/var/log/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

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

Server Administrator startup complete

root

emacs

to view the file named

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 ESX/ESXi

Click

ViewAdministrationSystem Logs

Select

Server Log

/var/log/messages

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

•

Server Management Messages

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.

Server Administrator General Messages

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

Table 2-1. Server Administrator General Messages

Event IDDescription Severity Cause

0000 Log was cleared Information User cleared the log from

Server Administrator.

This operation does not clear the operating system event log. Therefore, this event is not logged in the operating system event log. This is logged in the OpenManage System Administrator alert log.

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

Information Server Administrator is

beginning to initialize.

Information Server Administrator

completed initialization.

Information The user has chosen to update

the flash basic input/output system (BIOS).

Server Management Messages 19

Table 2-1. Server Administrator General Messages

Event IDDescription Severity Cause

(continued)

1003 A previously scheduled

system BIOS update has been canceled

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: <Action> Date and time of action: <Date and time>

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.

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

20 Server Management Messages

Table 2-1. Server Administrator General Messages

Event IDDescription Severity Cause

(continued)

1007 User initiated host

system control action Action requested was: <Action>

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>

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.

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

Server Management Messages 21

Table 2-1. Server Administrator General Messages

Event IDDescription Severity Cause

(continued)

1013 System Peak Power

detected new peak value Peak value (in Watts):<Reading>

1014 System software

event:<Description> Date and time of action:<Date and time>

Information The system peak power sensor

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

Warning This event is generated when

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

Temperature Sensor Messages

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

22 Server Management Messages

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

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

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 anominal temperature sensor value information is provided.

Server Management Messages 23

Table 2-2. Temperature Sensor Messages

Event IDDescription Severity Cause

(continued)

1052 Temperature 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:

Temperature sensor value (in degrees Celsius): <Reading>

If sensor type is discrete:

Discrete temperature state:

<State>

1053 Temperature 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:

Temperature sensor value (in degrees Celsius): <Reading>

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

24 Server Management Messages

Table 2-2. Temperature Sensor Messages

Event IDDescription Severity Cause

(continued)

1054 Temperature 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:

Temperature sensor value (in degrees Celsius): <Reading>

If sensor type is discrete:

Discrete temperature state:

<State>

1055 Temperature 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:

Temperature sensor value (in degrees Celsius): <Reading>

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.

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 information is provided.

Server Management Messages 25

Cooling Device Messages

The 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: <Reading>

1101 Fan sensor value unknown

Sensor location: <Location in chassis>

Chassis location: <Name of chassis>

Previous state was: <State>

Fan sensor value: <Reading>

Error A fan sensor in the

specified system is not functioning. The sensor location, chassis location, previous state, and fan sensor value information is 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 information is provided.

26 Server Management Messages

Table 2-3. Cooling Device Messages

Event IDDescription Severity Cause

(continued)

1102 Fan sensor returned to a

normal value

Sensor location: <Location in

chassis>

Chassis location: <Name of chassis>

Previous state was: <State>

Fan sensor value: <Reading>

1103 Fan sensor detected a warning

value

Sensor location: <Location in

chassis>

Chassis location: <Name of chassis>

Previous state was: <State>

Fan sensor value: <Reading>

1104 Fan sensor detected a failure

value

Sensor location: <Location in

chassis>

Chassis location: <Name of chassis>

Previous state was: <State>

Fan sensor value: <Reading>

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 information is 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 information is 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 information is provided.

Server Management Messages 27

Table 2-3. Cooling Device Messages

Event IDDescription Severity Cause

(continued)

1105 Fan sensor detected a

non-recoverable value

Sensor location: <Location in

chassis>

Chassis location: <Name of chassis>

Previous state was: <State>

Fan sensor value: <Reading>

Error A fan sensor

detected an error from which it cannot recover. The sensor location, chassis location, previous state, and fan sensor value information is provided.

28 Server Management Messages

Voltage Sensor Messages

The 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): <Reading>

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

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 information is provided.

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.

Server Management Messages 29

Table 2-4. Voltage Sensor Messages

Event IDDescription Severity Cause

(continued)

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

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

If sensor type is discrete:

Discrete voltage state:

<State>

Information A voltage sensor in

the specified system returned to a valid range after crossing afailure threshold. The sensor location, chassis location, previous state, and voltage sensor value information is provided.

Warning A voltage sensor in

the specified system exceeded its warning threshold. The sensor location, chassis location, previous state, and voltage sensor value information is provided.

30 Server Management Messages

+ 252 hidden pages