Dell OpenManage Server Administrator Version 6.0.3 Quick Reference Guide
Dell™ OpenManage™
Server Administrator
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.
____________________
Information in this document is subject to change without notice.
© 2009 Dell Inc. All rights reserved.
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 Windows 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 trademark of Red Hat, Inc.; 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.
February 2009
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
Logging Messages to a Unicode File
. . . . . . . . . 8
. . . . . . . . . . . . . 8
. . . . . . . . . . . . 10
. . . . . . . . . . 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
Viewing Events in VMware ESXi
Viewing the Event Information
Understanding the Event Description
. . . . . . . . . 12
. . . . . . . . . . 13
. . . . . . . . . . . 14
. . . . . . . 14
2 Event Message Reference . . . . . . . . . . . 19
Miscellaneous Messages . . . . . . . . . . . . . . . . 19
Temperature Sensor Messages . . . . . . . . . . . . . 22
Cooling Device Messages
. . . . . . . . . . . . . . . 25
Voltage Sensor Messages
Current Sensor Messages
. . . . . . . . . . . . . . . 28
. . . . . . . . . . . . . . . . 31
Contents 3
Chassis Intrusion Messages . . . . . . . . . . . . . . 35
Redundancy Unit Messages
Power Supply Messages
Memory Device Messages
Fan Enclosure Messages
AC Power Cord Messages
Hardware Log Sensor Messages
. . . . . . . . . . . . . . . 37
. . . . . . . . . . . . . . . . 41
. . . . . . . . . . . . . . . 45
. . . . . . . . . . . . . . . . 46
. . . . . . . . . . . . . . . . 48
. . . . . . . . . . . . 49
Processor Sensor Messages . . . . . . . . . . . . . . 51
Pluggable Device Messages
Battery Sensor Messages
. . . . . . . . . . . . . . 54
. . . . . . . . . . . . . . . . 56
Chassis Management Controller Messages
3 System Event Log Messages
for IPMI Systems
Temperature Sensor Events . . . . . . . . . . . . . . . 59
. . . . . . . . . . . . . . . . . . . 59
. . . . . . 58
4 Contents
Voltage Sensor Events
Fan Sensor Events
. . . . . . . . . . . . . . . . . . . . 61
Processor Status Events
Power Supply Events
Memory ECC Events
. . . . . . . . . . . . . . . . . . . 66
BMC Watchdog Events
Memory Events
. . . . . . . . . . . . . . . . . . . . . 67
. . . . . . . . . . . . . . . . . . 60
. . . . . . . . . . . . . . . . . 63
. . . . . . . . . . . . . . . . . . 64
. . . . . . . . . . . . . . . . . 66
Hardware Log Sensor Events . . . . . . . . . . . . . . 68
Drive Events
Intrusion Events
. . . . . . . . . . . . . . . . . . . . . . . 69
. . . . . . . . . . . . . . . . . . . . . 71
BIOS Generated System Events
R2 Generated System Events
Cable Interconnect Events
Battery Events
. . . . . . . . . . . . . . . . . . . . . . 79
Power And Performance Events . . . . . . . . . . . . 80
Entity Presence Events
. . . . . . . . . . . . . . . . . 80
4 Storage Management
Message Reference
Alert Monitoring and Logging . . . . . . . . . . . . . . 81
Alert Message Format with
Substitution Variables
Alert Message Change History
. . . . . . . . . . . . . . . . . . 82
. . . . . . . . . . . . . 72
. . . . . . . . . . . . . . 78
. . . . . . . . . . . . . . . 79
. . . . . . . . . . . . . . . . 81
. . . . . . . . . . . . . 84
Alert Descriptions and Corrective Actions
. . . . . . . 85
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Contents 5
6 Contents
Introduction
Dell™ OpenManage™ Server Administrator produces event messages
stored primarily in the operating system or Server Administrator event logs.
This document describes the event messages created by Server Administrator
version 6.0.3 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.
What’s New in this Release
The following changes have been made for this release:
• Support for the VMware® ESXi version 3.5 Update 4 hypervisor.
• Support for the Server Administrator Web Server.
• Supports Serial Attached SCSI (SAS) controllers only for this release.
<State>
) describes the
Introduction 7
• No SNMP trap support for this release.
• No support for LRA numbers for this release.
• Added two new alerts 1013 and 2382 in the “Miscellaneous Messages” and
“Alert Descriptions and Corrective Actions” sections respectively.
• Added the POST Code Errors table in the “BIOS Generated System
Events” section.
• Support for Solid State Drives (SSD). Added new SSD alert 2370 in the
“Storage Management Message Reference” section.
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
• Operating system documentation
• Application program documentation
Installation and Troubleshooting Guide
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:
8 Introduction
Table 1-1. Understanding Event Messages
Icon Alert Severity Component Status
OK /Normal /
Informational
War n in g /
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 ex am p l e ,
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 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.
Introduction 9
•
Redundancy Unit Sensor
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
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
attached systems.
•
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 any attached systems.
•
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.
— Monitors the processor status in the system.
— Monitors the status of one or more batteries in
— Monitors redundant units (critical units
n
th fan to keep the chassis components at a
— Monitors power supplies in the chassis and in any
— 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,
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
10 Introduction
Date and Time: Mon Oct 21 10:38:00 2002
Computer:
<computer name>
Description:
Server Administrator starting
Data: Bytes in Hex
Viewing Alerts and Event Messages
NOTE: The Red Hat® Enterprise Linux®, SUSE® Linux Enterprise Server and
Microsoft
the VMware
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:
1
Select the
2
Select the
3
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.
• In the Microsoft® Windows® 2000 Advanced Server and Windows
Server
log and optionally to a Unicode text file,
Notepad), that is located in the
The default
• In the Red Hat Enterprise Linux, SUSE Linux Enterprise Server and
VMware ESXi operating systems, messages are logged to the system log
file. The default name of the system log file is
view the messages file using a text editor such as vi or emacs.
®
Windows® content mentioned in the following section do not apply to
®
ESXi version 3.5 Update 4 release.
System
Logs
Alert
®
2003 operating systems, messages are logged to the system event
object in the tree view.
tab.
subtab.
install_path
is
C:\Program Files\Dell\SysMgt
dcsys32.log
install_path
(viewable using
\omsa\log
directory.
.
/var/log/messages
. You can
Introduction 11
Logging Messages to a Unicode 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 <install_path>\dataeng\ini and set
UnitextLog.enabled=True
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 set
default install_path is /opt/dell/srvadmin. Issue the "/etc/init.d/dataeng restart"
command to restart the Server Administrator event manager service.
. The default <install_path> is C:\Program
UnitextLog.enabled=True
. The
The following subsections explain how to open the Windows 2000 Advanced
Server, Windows Server 2003, Red Hat Enterprise Linux, SUSE Linux
Enterprise Server and VMware ESXi event viewers.
Viewing Events in Windows 2000 Advanced Server and Windows Server 2003
1
Click the
2
Double-click
3
In the
The
4
To view the details of an event, double-click one of the event items.
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
.
NOTE: You can find the event log file dcsys32.log, at <install_path>\omsa\log
directory. The default <install_path> is C:\Program Files\Dell\SysMgt.
Viewing Events in Red Hat Enterprise Linux and SUSE Linux Enterprise Server
1
Log in as
2
Use a text editor such as vi or emacs to view the file named
messages
12 Introduction
root
.
.
/var/log/
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.
...
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 Events in VMware ESXi
1
Log in to the VMware ESXi system with VMware Infrastructure (VI)
Client.
2
Click
3
4
Administration
Select
System Logs
Select
Server Log [/var/log/messages
on the navigation bar.
.
] entry on the drop-down list.
Introduction 13
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
•
Category
Event ID
•
•
Description
— The name of the system where the event occurred.
— The software that logged the event.
— The classification of the event by the event source.
— The number identifying the particular event type.
— A description of the event. The format and contents of
the event description vary, depending on the event type.
Understanding the Event Description
Table 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>
Action requested was:
<Action>
Additional Details:
<Additional details for
the event>
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
14 Introduction
Table 1-2. Event Description Reference (continued)
Description Line Item Explanation
<Additional power
supply status
information>
Chassis intrusion
state:
<Intrusion
state>
Chassis location:
<Name
of chassis>
Configuration error
type:
<type of configuration
error>
Current sensor value
(in Amps):
Date and time of
action:
Device location:
<
Location in chassis
Discrete current state:
<Reading>
<Date and time>
<State>
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
Introduction 15
Table 1-2. Event Description Reference (continued)
Description Line Item Explanation
Discrete temperature
state:
Discrete voltage state:
<State>
<State>
Fan sensor value:
<Reading>
Log type:
Memory device bank
location:
<Log type>
<Bank name in
chassis>
Memory device location:
<Device name in
chassis>
Number of devices
required for full
redundancy:
Peak value (in Watts):
<Number>
<Reading>
Possible memory module
event cause:
<list of
causes>
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): 125
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
16 Introduction
Table 1-2. Event Description Reference (continued)
Description Line Item Explanation
Power Supply type:
<type of power supply>
Previous redundancy
state was:
Previous state was:
<State>
<State>
Processor sensor
status:
Redundancy unit:
<status>
<Redundancy location in
chassis>
Sensor location:
<Location in chassis>
Temperature sensor
value:
Voltage sensor value
(in Volts):
<Reading>
<Reading>
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
1006 Automatic System
Recovery (ASR) action
was performed
Action performed was:
<Action>
Date and time of
action:
time>
1007 User initiated host
system control action
Action requested was:
<Action>
<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.
contain 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>
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
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.
sensor detected a new peak
value in power consumption.
The new peak value in Watts
is provided.
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>
<Reading>
<Reading>
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>
<Reading>
<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>
<Reading>
<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>
<Reading>
<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>
<Reading>
<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:
<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 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.
Event Message Reference 25
Table 2-3. Cooling Device Messages (continued)
Event IDDescription Severity Cause
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>
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.
26 Event Message Reference
Table 2-3. Cooling Device Messages (continued)
Event IDDescription Severity Cause
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>
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 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.
Event Message Reference 27
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>
<Reading>
<Reading>
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.
28 Event Message Reference
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:
<Reading>
<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:
<Reading>
<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.
Event Message Reference 29
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:
<Reading>
<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:
<Reading>
<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.
30 Event Message Reference
Loading...