Dell Openmanage Server Administrator Version 6 0 3 Quick Reference Guide 6.0.3 Message

2014-11-13

: Dell Dell-Openmanage-Server-Administrator-Version-6-0-3-Quick-Reference-Guide-117353 dell-openmanage-server-administrator-version-6-0-3-quick-reference-guide-117353 dell pdf

Open the PDF directly: View PDF .
Page Count: 224

Download
Open PDF In Browser	View PDF

Dell™ OpenManage™
Server Administrator

Messages Reference Guide

w w w. d e l l . c o m | s u p p o r t . d e l l . c o m

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

Introduction .

. . . . . . . . . . . . . . . . . . . . . . .

What’s New in this Release .

. . . . . . . . . . . . . . .

Messages Not Described in This Guide
Understanding Event Messages
Sample Event Message Text

. . . . . . . . . . . . .

. . . . . . . . . . . .
. . . . . . . . . .

Logging Messages to a Unicode File

. . . . . . .

Viewing Events in Windows 2000 Advanced
Server and Windows Server 2003 . . . . . .
Viewing Events in Red Hat Enterprise Linux
and SUSE Linux Enterprise Server . . . . .
Viewing the Event Information

10
11
12

. . .

. . . .

. . . . . . . . . .

. . . . . . . . . . .

Viewing Events in VMware ESXi

. . . . . . .

. . . . . . . . . . .

. . . . . . . . . . . . . . .

Understanding the Event Description

Event Message Reference
Miscellaneous Messages .

. . . . . . . . .

Viewing Alerts and Event Messages

Temperature Sensor Messages

. . . . . . . . . . . . .

Cooling Device Messages

. . . . . . . . . . . . . . .

Voltage Sensor Messages

. . . . . . . . . . . . . . .

Current Sensor Messages .

. . . . . . . . . . . . . . .

Contents

Chassis Intrusion Messages

. . . . . . . . . . . . . .

Redundancy Unit Messages .

. . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

Power Supply Messages

Memory Device Messages
Fan Enclosure Messages

. . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

AC Power Cord Messages .

. . . . . . . . . . . . . . .

Hardware Log Sensor Messages

. . . . . . . . . . . .

Processor Sensor Messages

. . . . . . . . . . . . . .

Pluggable Device Messages

. . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

Battery Sensor Messages

Chassis Management Controller Messages

. . . . . .

. . . . . . . . . .

. . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

System Event Log Messages
for IPMI Systems . . . . . . . . .
Temperature Sensor Events
Voltage Sensor Events .
Fan Sensor Events

Processor Status Events .

. . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

Power Supply Events
Memory ECC Events

. . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

BMC Watchdog Events
Memory Events

Contents

Hardware Log Sensor Events
Drive Events

. . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

Intrusion Events

BIOS Generated System Events

. . . . . . . . . . . . .

. . . . . . . . . . . . . .

. . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

R2 Generated System Events
Cable Interconnect Events
Battery Events

Power And Performance Events
Entity Presence Events

. . . . . . . . . . . .

. . . . . . . . . . . . . . . . .

Storage Management
Message Reference .

Alert Message Format with
Substitution Variables . . .

. . . . . . . . . . . . . . .

Alert Monitoring and Logging .

. . . . . . . . . . . . .

. . . . . . . . . . . . . . .

Alert Message Change History

. . . . . . . . . . . . .

Alert Descriptions and Corrective Actions

Index

. . . . . . . . . . . . . . . . . . . . .

. . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

203

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, ) describes the
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.

Introduction

•

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 Installation and Troubleshooting Guide

•

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, the Server
Administrator sends information about one of the following event types to
the systems management console:

Introduction

Table 1-1.
Icon

Understanding Event Messages

Alert Severity

Component Status

OK /Normal /
Informational

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.

Warning /
Non-critical

An event that is not necessarily significant, but may indicate a
possible future problem. For example, a Warning/Non-critical
alert may indicate that a component (such as a temperature
probe in an enclosure) has crossed a warning threshold.

Critical /
Failure / Error

A significant event that indicates actual or imminent loss of
data or loss of function. For example, crossing a failure
threshold or a hardware failure such as 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

•

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

•

Processor Sensor — Monitors the processor status in the system.

•

Pluggable Device Sensor — Monitors the addition, removal,
or configuration errors for some pluggable devices, such as memory cards.

•

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

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

Introduction

Date and Time: Mon Oct 21 10:38:00 2002
Computer:
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® Windows® content mentioned in the following section do not apply to
the VMware® ESXi version 3.5 Update 4 release.

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 System object in the tree view.
2 Select the Logs tab.
3 Select the Alert subtab.
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® 2003 operating systems, messages are logged to the system event
log and optionally to a Unicode text file, dcsys32.log (viewable using
Notepad), that is located in the install_path\omsa\log directory.
The default install_path is C:\Program Files\Dell\SysMgt.

•

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 /var/log/messages. You can
view the messages file using a text editor such as vi or emacs.

Introduction

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 \dataeng\ini and set
UnitextLog.enabled=True. The default is C:\Program
Files\Dell\SysMgt. Restart the DSM SA Event Manager service.

•

In Red Hat Enterprise Linux and SUSE Linux Enterprise Server, locate the file at
/dataeng/ini and set UnitextLog.enabled=True. The
default install_path is /opt/dell/srvadmin. Issue the "/etc/init.d/dataeng restart"
command to restart the Server Administrator event manager service.

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 Start button, point to Settings, and click Control Panel.
2 Double-click Administrative Tools, and then double-click Event Viewer.
3 In the Event Viewer window, click the Tree tab and then click System Log.
The System Log window displays a list of recently logged events.
4 To view the details of an event, double-click one of the event items.
NOTE: You can find the event log file dcsys32.log, at \omsa\log
directory. The default is C:\Program Files\Dell\SysMgt.

Viewing Events in Red Hat Enterprise Linux and SUSE Linux
Enterprise Server
1 Log in as root.
2 Use a text editor such as vi or emacs to view the file named /var/log/
messages.

Introduction

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 Administration on the navigation bar.
3 Select System Logs.
4 Select Server Log [/var/log/messages] entry on the drop-down list.

Introduction

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.

•

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

•

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

•

Computer — The name of the system where the event occurred.

•

Source — The software that logged the event.

•

Category — The classification of the event by the event source.

•

Event ID — The number identifying the particular event type.

•

Description — 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:

Specifies the action that was performed,
for example:
Action performed was: Power cycle

Action requested was:

Specifies the action that was requested,
for example:
Action requested was: Reboot, shutdown OS first

Specifies additional details available for the hot
Additional Details:

Memory device: DIMM1_A Serial
number: FFFF30B1

Introduction

Table 1-2.

Event Description Reference (continued)

Description Line Item

Explanation

Specifies information pertaining to the event,
for example:

Chassis intrusion
state:

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

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

Chassis intrusion state: Open

Chassis location:
message, for example:
Chassis location: Main System
Chassis
Configuration error
type:

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

Current sensor value
(in Amps):

Specifies the current sensor value in amps,
for example:

Configuration error type: Revision
mismatch

Current sensor value (in Amps):
7.853
Specifies the date and time the action was
Date and time of
action: performed, for example:
Date and time of action: Sat Jun 12
16:20:33 2004
Device location:

Specifies the location of the device in the specified
chassis, for example:
Device location: Memory Card A

Discrete current state: Specifies the state of the current sensor, for

example:
Discrete current state: Good

Introduction

Table 1-2.

Event Description Reference (continued)

Description Line Item

Explanation

Discrete temperature
state:

Specifies the state of the temperature sensor,
for example:
Discrete temperature state: Good

Discrete voltage state: Specifies the state of the voltage sensor,

for example:
Discrete voltage state: Good
Fan sensor value:

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

Log type:

Specifies the type of hardware log, for example:
Log type: ESM

Memory device bank
Specifies the name of the memory bank in the
location:
Memory device bank location: Bank_1
Memory device location: Specifies the location of the memory module in the

Memory device location: DIMM_A
Number of devices
required for full
redundancy:

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

Peak value (in Watts):

Specifies the peak value in Watts, for example:

Possible memory module
event cause:

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

Peak value (in Watts): 125

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

Introduction

Table 1-2.

Event Description Reference (continued)

Description Line Item

Explanation

Power Supply type:
Specifies the type of power supply, for example:
Power Supply type: VRM
Previous redundancy
state was:

Specifies the status of the previous redundancy
message, for example:
Previous redundancy state was: Lost

Previous state was:

Specifies the previous state of the sensor, for
example:
Previous state was: OK (Normal)

Processor sensor
status:

Specifies the status of the processor sensor,
for example:
Processor sensor status:
Configuration error

Redundancy unit:
Specifies the location of the redundant power

Redundancy unit: Fan Enclosure
Sensor location:

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

Temperature sensor
value:

Specifies the temperature in degrees Celsius,
for example:
Temperature sensor value
(in degrees Celsius): 30

Voltage sensor value
(in Volts):

Specifies the voltage sensor value in volts,
for example:
Voltage sensor value (in Volts):
1.693

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

Severity

Cause

0000

Log was cleared

Information

User cleared the log from
Server Administrator.

0001

Log backup created

Information

The log was full, copied to
backup, and cleared.

1000

Server Administrator
starting

Information

Server Administrator is
beginning to initialize.

1001

Server Administrator
startup complete

Information

Server Administrator
completed its initialization.

1002

A system BIOS update
Information
has been scheduled for
the next reboot

The user has chosen to
update the flash basic input/
output system (BIOS).

1003

A previously scheduled Information
system BIOS update has
been canceled

The user decides to cancel
the flash BIOS update, or an
error occurs during the flash.

Event Message Reference

Table 2-1.

Miscellaneous Messages (continued)

Event Description
ID

Severity

Cause

1004

Thermal shutdown
protection has been
initiated

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.

1005

SMBIOS data is absent

Error

The system does not
contain the required systems
management BIOS
version 2.2 or higher, or the
BIOS is corrupted.

1006

Automatic System
Recovery (ASR) action
was performed

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.

Action performed was:

Date and time of
action:
1007

User initiated host
system control action
Action requested was:

Event Message Reference

Table 2-1.

Miscellaneous Messages (continued)

Event Description
ID

Severity

Cause

1008

Systems Management
Data Manager Started

Information

Systems Management
Data Manager services
were started.

1009

Systems Management
Data Manager Stopped

Information

Systems Management
Data Manager services
were stopped.

1011

RCI table is corrupt

Error

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

1012

IPMI Status

Information

This message is generated
to indicate the Intelligent
Platform Management
Interface (IPMI)) status of
the system.

Interface: ,

1013

System Peak Power
detected new peak
value
Peak value (in Watts):

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

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

Event Message Reference

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

Temperature Sensor Messages

Event Description
ID

Severity

Cause

1050

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.

Temperature sensor has failed
Sensor location:
Chassis location:
Previous state was:
If sensor type is not discrete:
Temperature sensor value
(in degrees Celsius):
If sensor type is discrete:
Discrete temperature state:

1051

Information A temperature
sensor on the
backplane board,
Sensor location:
drive carrier in the
Chassis location:
could not obtain a
reading. The sensor
If sensor type is not discrete:
location, chassis
Temperature sensor value (in
location, previous
degrees Celsius):
state, and
If sensor type is discrete:
a nominal
temperature sensor
Discrete temperature state:
value are provided.

Temperature sensor value
unknown

Event Message Reference

Table 2-2.

Temperature Sensor Messages (continued)

Event Description
ID

Severity

Cause

1052

Information A temperature
sensor on the
backplane board,
Sensor location:
drive carrier in the
Chassis location:
returned to a valid
range after crossing
Previous state was:
a failure threshold.
If sensor type is not discrete:
The sensor
Temperature sensor value (in
location, chassis
degrees Celsius):
location, previous
state, and
If sensor type is discrete:
temperature sensor
Discrete temperature state:
value are provided.

1053

Temperature sensor detected
a warning value

Temperature sensor returned
to a normal value

Warning

Sensor location:
Chassis location:
Previous state was:
If sensor type is not discrete:
Temperature sensor value (in
degrees Celsius):
If sensor type is discrete:
Discrete temperature state:

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

Table 2-2.

Temperature Sensor Messages (continued)

Event Description
ID

Severity

Cause

1054

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.

Temperature sensor detected
a failure value
Sensor location:
Chassis location:
Previous state was:
If sensor type is not discrete:
Temperature sensor value (in
degrees Celsius):
If sensor type is discrete:
Discrete temperature state:

1055

Temperature sensor detected
a non-recoverable value
Sensor location:
Chassis location:
Previous state was:
If sensor type is not discrete:
Temperature sensor value (in
degrees Celsius):
If sensor type is discrete:
Discrete temperature state:

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

Severity

Cause

1100

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.

Fan sensor has
failed
Sensor location:

Chassis location:

Previous state was:

Fan sensor value:

1101

Fan sensor value
unknown
Sensor location:

Chassis location:

Previous state was:

Fan sensor value:

Event Message Reference

Table 2-3.

Cooling Device Messages (continued)

Event Description
ID

Severity

1102

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.

Fan sensor returned
to a normal value
Sensor location:

Chassis location:

Cause

Previous state was:

Fan sensor value:

1103

Fan sensor detected
a warning value
Sensor location:

Chassis location:

Previous state was:

Fan sensor value:

Event Message Reference

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.

Table 2-3.

Cooling Device Messages (continued)

Event Description
ID

Severity

Cause

1104

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.

Fan sensor detected
a failure value
Sensor location:

Chassis location:

Previous state was:

Fan sensor value:

1105

Fan sensor detected
a
non-recoverable
value
Sensor location:

Chassis location:

Previous state was:

Fan sensor value:

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

Severity

Cause

1150 Voltage sensor has failed

Error

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

Sensor location:
Chassis location:
Previous state was:
If sensor type is not
discrete:
Voltage sensor value (in
Volts):
If sensor type is discrete:
Discrete voltage state:

1151 Voltage sensor value unknown Warning
Sensor location:
Chassis location:
Previous state was:
If sensor type is not
discrete:
Voltage sensor value
(in Volts):
If sensor type is discrete:
Discrete voltage state:

Event Message Reference

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.

Table 2-4.

Voltage Sensor Messages (continued)

Event Description
ID

Severity

1152 Voltage sensor returned to
a normal value

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.

Sensor location:
Chassis location:
Previous state was:
If sensor type is not
discrete:

Cause

Voltage sensor value
(in Volts):
If sensor type is discrete:
Discrete voltage state:

1153 Voltage sensor detected a
warning value
Sensor location:
Chassis location:
Previous state was:
If sensor type is not
discrete:

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.

Voltage sensor value
(in Volts):
If sensor type is discrete:
Discrete voltage state:

Event Message Reference

Table 2-4.

Voltage Sensor Messages (continued)

Event Description
ID

Severity

Cause

1154 Voltage sensor detected
a failure value

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.

Sensor location:
Chassis location:
Previous state was:
If sensor type is not
discrete:
Voltage sensor value
(in Volts):
If sensor type is discrete:
Discrete voltage state:

1155 Voltage sensor detected a
non-recoverable value
Sensor location:
Chassis location:
Previous state was:
If sensor type is not
discrete:
Voltage sensor value
(in Volts):
If sensor type is discrete:
Discrete voltage state:

Event Message Reference

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

Severity

Cause

1200

Error

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

Current sensor has failed
Sensor location:
Chassis location:
Previous state was:
If sensor type is not discrete:
Current sensor value
(in Amps): OR
Current sensor value
(in Watts):
If sensor type is discrete:
Discrete current state:

Event Message Reference

Table 2-5.

Current Sensor Messages (continued)

Event Description
ID

Severity

Cause

1201

Error

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

Current sensor value unknown
Sensor location:
Chassis location:
Previous state was:
If sensor type is not discrete:
Current sensor value (in Amps):
OR
Current sensor value (in
Watts):
If sensor type is discrete:
Discrete current state:

1202

Information A current sensor
in the specified
system returned
Sensor location:
after crossing a
Chassis location:
The sensor
location, chassis
Previous state was:
location, previous
If sensor type is not discrete:
state, and current
Current sensor value (in Amps):
sensor value are
OR
provided.
Current sensor value (in
Watts):
Current sensor returned to
a normal value

If sensor type is discrete:
Discrete current state:

Event Message Reference

Table 2-5.

Current Sensor Messages (continued)

Event Description
ID

Severity

Cause

1203

Warning

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

Error

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

Current sensor detected a
warning value
Sensor location:
Chassis location:
Previous state was:
If sensor type is not discrete:
Current sensor value (in Amps):
OR
Current sensor value (in
Watts):
If sensor type is discrete:
Discrete current state:

1204

Current sensor detected a
failure value
Sensor location:
Chassis location:
Previous state was:
If sensor type is not discrete:
Current sensor value (in Amps):
OR
Current sensor value (in
Watts):
If sensor type is discrete:
Discrete current state:

Event Message Reference

Table 2-5.

Current Sensor Messages (continued)

Event Description
ID

Severity

Cause

1205

Error

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

Current sensor detected a
non-recoverable value
Sensor location:
Chassis location:
Previous state was:
If sensor type is not discrete:
Current sensor value (in Amps):
OR
Current sensor value (in
Watts):
If sensor type is discrete:
Discrete current state:

Event Message Reference

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

Chassis Intrusion Messages

Event Description
ID
1250

Severity

Chassis intrusion sensor Error
has failed
Sensor location:

Chassis location:

Cause
A chassis intrusion sensor
in the specified system
failed. The sensor
location, chassis location,
previous state, and
chassis intrusion state
are provided.

Previous state was:

Chassis intrusion state:

1251

Chassis intrusion sensor Error
value unknown
Sensor location:

Chassis location:
Previous state was:

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

Chassis intrusion state:

Event Message Reference

Table 2-6.

Chassis Intrusion Messages (continued)

Event Description
ID

Severity

Cause

1252

Information

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

Warning

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

Chassis intrusion
returned to normal
Sensor location:

Chassis location:
Previous state was:

Chassis intrusion state:

1253

Chassis intrusion in
progress
Sensor location:

Chassis location:
Previous state was:

Chassis intrusion state:

Event Message Reference

Table 2-6.

Chassis Intrusion Messages (continued)

Event Description
ID

Severity

Cause

1254

Warning

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

Chassis intrusion
detected
Sensor location:

Chassis location:
Previous state was:

Chassis intrusion state:

1255

Chassis intrusion sensor Error
detected a nonrecoverable value
Sensor location:

Chassis location:
Previous state was:

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

Chassis intrusion state:

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

Event Message Reference

component fails but others are still operating. Redundancy is lost when the
number of components functioning falls below the redundancy threshold.
Table 2-7 lists the redundancy unit messages.
The number of devices required for full redundancy is provided as part of
the message, when applicable, for the redundancy unit and the platform.
For details on redundancy computation, see the respective platform
documentation.
Table 2-7.

Redundancy Unit Messages

Event Description
ID

Severity

Cause

1300

Warning

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

Warning

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

Redundancy sensor has
failed
Redundancy unit:

Chassis location:

Previous redundancy
state was:

1301

Redundancy sensor
value unknown
Redundancy unit:

Chassis location:

Previous redundancy
state was:

Event Message Reference

Table 2-7.

Redundancy Unit Messages (continued)

Event Description
ID

Severity

1302

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

Redundancy not
applicable
Redundancy unit:

Chassis location:

Previous redundancy
state was:

1303

Redundancy is offline
Redundancy unit:

Chassis location:

Previous redundancy
state was:

1304

Redundancy regained
Redundancy unit:

Chassis location:

Previous redundancy
state was:

Cause

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

Event Message Reference

Table 2-7.

Redundancy Unit Messages (continued)

Event Description
ID

Severity

Cause

1305

Warning

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

Error

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

Redundancy degraded
Redundancy unit:

Chassis location:

Previous redundancy
state was:

1306

Redundancy lost
Redundancy unit:

Chassis location:

Previous redundancy
state was:

Event Message Reference

Power Supply Messages
Power supply sensors monitor how well a power supply is functioning.
Power supply messages listed in Table 2-8 provide status and warning
information for power supplies present in a particular chassis.
Table 2-8.

Power Supply Messages

Event Description
ID

Severity

Cause

1350

Error

A power supply sensor
in the specified system
failed. The sensor
location, chassis location,
previous state, and
additional power supply
status information
are provided.

Power supply sensor has
failed Sensor location:

Chassis location:
Previous state was:

Power Supply type:

If in configuration error
state:
Configuration error type:

Event Message Reference

Table 2-8.

Power Supply Messages (continued)

Event Description
ID
1351

Severity

Power supply sensor value Warning
unknown
Sensor location:

Chassis location:
Previous state was:

Cause
A power supply sensor in
the specified system
could not obtain
a reading. The sensor
location, chassis location,
previous state, and
additional power supply
status information
are provided.

Power Supply type:

If in configuration error
state:
Configuration error type:

1352

Power supply returned to
normal Sensor location:

Chassis location:
Previous state was:

Power Supply type:

If in configuration error
state:
Configuration error type:

Event Message Reference

Information A power supply has been
reconnected or replaced.
The sensor location,
chassis location, previous
state, and additional
power supply status
information are provided.

Table 2-8.

Power Supply Messages (continued)

Event Description
ID

Severity

Cause

1353

Warning

A power supply sensor
reading in the specified
system exceeded
a user-definable warning
threshold. The sensor
location, chassis location,
previous state, and
additional power supply
status information
are provided.

Error

A power supply has been
disconnected or has
failed. The sensor
location, chassis location,
previous state, and
additional power supply
status information
are provided.

Power supply detected a
warning Sensor location:

Chassis location:
Previous state was:

Power Supply type:

If in configuration error
state:
Configuration error type:

1354

Power supply detected a
failure
Sensor location:

Chassis location:
Previous state was:

Power Supply type:

If in configuration error
state:
Configuration error type:

Event Message Reference

Table 2-8.

Power Supply Messages (continued)

Event Description
ID

Severity

Cause

1355

Error

A power supply sensor in
the specified system
detected an error from
which it cannot recover.
The sensor location,
chassis location, previous
state, and additional
power supply status
information are provided.

Power supply sensor
detected a nonrecoverable value
Sensor location:

Chassis location:
Previous state was:

Power Supply type:

If in configuration error
state:
Configuration error type:

Event Message Reference

Memory Device Messages
Memory device messages listed in Table 2-9 provide status and warning
information for memory modules present in a particular system.
Memory devices determine health status by monitoring the ECC memory
correction rate and the type of memory events that have occurred.
NOTE: A critical status does not always indicate a system failure or loss of data.
In some instances, the system has exceeded the ECC correction rate. Although
the system continues to function, you should perform system maintenance as
described in Table 2-9.
NOTE: In Table 2-9, can be either critical or non-critical.
Table 2-9.

Memory Device Messages

Event Description
ID

Severity

Cause

1403 Memory device status is Warning A memory device correction
rate exceeded an acceptable
Memory device
value. The memory device
location:
provided.
Possible memory module
event cause:
1404 Memory device status is Error
Memory device
location:

Possible memory module
event cause:

A memory device correction
rate exceeded an acceptable
value, a memory spare bank was
activated, or a multibit ECC
error occurred. The system
continues to function normally
(except for a multibit error).
Replace the memory module
identified in the message
during the system’s next
scheduled maintenance.
Clear the memory error on
multibit ECC error.
The memory device status and
location are provided.

Event Message Reference

Fan Enclosure Messages
Some systems are equipped with a protective enclosure for fans.
Fan enclosure messages listed in Table 2-10 monitor whether foreign objects
are present in an enclosure and how long a fan enclosure is missing from
a chassis.
Table 2-10. Fan Enclosure Messages
Event Description
ID

Severity

Cause

1450

Critical/
Failure /
Error

The fan enclosure sensor in
the specified system failed.
The sensor location and
chassis location are provided.

Warning

The fan enclosure sensor in
the specified system could not
obtain a reading. The sensor
location and chassis location
are provided.

Fan enclosure sensor
has failed
Sensor location:

Chassis location:

1451

Fan enclosure sensor
value unknown
Sensor location:

Chassis location:

1452

Fan enclosure inserted Information A fan enclosure has been
into system
inserted into the specified
system. The sensor location
Sensor location:
and chassis location are

provided.
Chassis location:

1453

Fan enclosure removed
from system
Sensor location:

Chassis location:

Event Message Reference

Warning

A fan enclosure has been
removed from the specified
system. The sensor location
and chassis location are
provided.

Table 2-10.

Fan Enclosure Messages (continued)

Event Description
ID

Severity

Cause

1454

Error

A fan enclosure has been
removed from the specified
system for a user-definable
length of time. The sensor
location and chassis location
are provided.

Error

A fan enclosure sensor in the
specified system detected an
error from which it cannot
recover. The sensor location
and chassis location
are provided.

Fan enclosure removed
from system for an
extended amount of
time
Sensor location:

Chassis location:

1455

Fan enclosure sensor
detected a nonrecoverable value
Sensor location:

Chassis location:

Event Message Reference

AC Power Cord Messages
AC power cord messages listed in Table 2-11 provide status and warning
information for power cords that are part of an AC power switch, if your
system supports AC switching.
Table 2-11. AC Power Cord Messages
Event Description
ID
1500

AC power cord sensor
Critical/
has failed Sensor
Failure/
location:
Chassis location:

1501

AC power cord is not
being monitored
Sensor location:

Chassis location:

1502

AC power has been
restored
Sensor location:

Chassis location:

Severity

Event Message Reference

Cause
An AC power cord sensor in
the specified system failed.
The AC power cord status
cannot be monitored. The
sensor location and chassis
location information are
provided.

Information The AC power cord status is
not being monitored. This
occurs when a system’s
expected AC power
configuration is set to
nonredundant. The sensor
location and chassis location
information are provided.
Information An AC power cord that did
not have AC power has had
the power restored.
The sensor location and
chassis location information
are provided.

Table 2-11.

AC Power Cord Messages (continued)

Event Description
ID
1503

Severity

AC power has been lost Critical/
Failure/
Sensor location:
Error
Chassis location:

1504

AC power has been lost Error
Sensor location:

Chassis location:

1505

AC power has been lost Error
Sensor location:

Chassis location:

Cause
An AC power cord has lost its
power, but there is sufficient
redundancy to classify this as
a warning. The sensor location
and chassis location
information are provided.
An AC power cord has lost its
power, and lack of redundancy
requires this to be classified as
an error. The sensor location
and chassis location
information are provided.
An AC power cord sensor in
the specified system failed.
The AC power cord status
cannot be monitored. The
sensor location and chassis
location information are
provided.

Hardware Log Sensor Messages
Hardware logs provide hardware status messages to systems management
software. On certain systems, the hardware log is implemented as a circular
queue. When the log becomes full, the oldest status messages are overwritten
when new status messages are logged. On some systems, the log is not
circular. On these systems, when the log becomes full, subsequent hardware
status messages are lost. Hardware log sensor messages listed in Table 2-12
provide status and warning information about the noncircular logs that may
fill up, resulting in lost status messages.

Event Message Reference

Table 2-12. Hardware Log Sensor Messages
Event Description
ID

Severity

Cause

1550

Warning

A hardware log sensor in the
specified system is disabled. The
log type information is provided.

Log monitoring has
been disabled
Log type:

1551

Log status is unknown Information A hardware log sensor in the
specified system could not
Log type:
obtain a reading. The log type
information is provided.

1552

Log size is no longer Information The hardware log on the
specified system is no longer near
near or at capacity
or at its capacity, usually as the
Log type:
result of clearing the log. The log
type information is provided.

1553

Log size is near
capacity

Warning

The size of a hardware log on the
specified system is near or at the
capacity of the hardware log. The
log type information is provided.

Error

The size of a hardware log on
the specified system is full. The
log type information is provided.

Log type:
1554

Log size is full
Log type:

1555

Log sensor has failed Error
Log type:

Event Message Reference

A hardware log sensor in the
specified system failed. The
hardware log status cannot be
monitored. The log type
information is provided.

Processor Sensor Messages
Processor sensors monitor how well a processor is functioning. Processor
messages listed in Table 2-13 provide status and warning information for
processors in a particular chassis.
Table 2-13.

Processor Sensor Messages

Event Description
ID

Severity

Cause

1600

Critical/
Failure/
Error

A processor sensor in the
specified system is not
functioning. The sensor
location, chassis location,
previous state and processor
sensor status are provided.

Processor sensor value Critical/
Failure/
unknown Sensor
Location:

A processor sensor in the
specified system could not
obtain a reading. The sensor
location, chassis location,
previous state and processor
sensor status are provided.

Processor sensor has
failed
Sensor Location:

Chassis Location:

Previous state was:

Processor sensor
status:

1601

Chassis Location:

Previous state was:

Processor sensor
status:

Event Message Reference

Table 2-13. Processor Sensor Messages (continued)
Event Description
ID

Severity

1602

Information A processor sensor in the
specified system transitioned
back to a normal state.
The sensor location,
chassis location, previous state
and processor sensor status
are provided.

Processor sensor
returned to a normal
value
Sensor Location:

Chassis Location:

Cause

Previous state was:

Processor sensor
status:
1603

Processor sensor
detected a warning
value
Sensor Location:

Chassis Location:

Previous state was:

Processor sensor
status:

Event Message Reference

Warning

A processor sensor in the
specified system is in a
throttled state. The sensor
location, chassis location,
previous state and processor
sensor status are provided.

Table 2-13.

Processor Sensor Messages (continued)

Event Description
ID

Severity

Cause

1604

Error

A processor sensor in the
specified system is disabled,
has a configuration error, or
experienced a thermal trip.
The sensor location, chassis
location, previous state and
processor sensor status
are provided.

Error

A processor sensor in the
specified system has failed.
The sensor location, chassis
location, previous state and
processor sensor status
are provided.

Processor sensor
detected a failure
value
Sensor Location:

Chassis Location:

Previous state was:

Processor sensor
status:

1605

Processor sensor
detected a nonrecoverable value
Sensor Location:

Chassis Location:

Previous state was:

Processor sensor
status:

Event Message Reference

Pluggable Device Messages
The pluggable device messages listed in Table 2-14 provide status and error
information when some devices, such as memory cards, are added or removed.
Table 2-14. Pluggable Device Messages
Event Description
ID
1650

Severity

Cause

Information A pluggable device event message
of unknown type was received.
The device location, chassis
Device location:
location, and additional event

Chassis location:

Additional details:

1651

Device added to
system
Device location:

Chassis location:

Additional details:

Event Message Reference

Information A device was added in the
specified system. The device
location, chassis location,
and additional event details,
if available, are provided.

Table 2-14.

Pluggable Device Messages (continued)

Event Description
ID

Severity

1652

Information A device was removed from the
specified system. The device
location, chassis location,
and additional event details,
if available, are provided.

Device removed from
system
Device location:

Cause

Chassis location:

Additional details:

1653

Device configuration
error
detected
Device location:

Error

A configuration error was
detected for a pluggable device
in the specified system.
The device may have been
added to the system incorrectly.

Chassis location:

Additional details:

Event Message Reference

Battery Sensor Messages
Battery sensors monitor how well a battery is functioning. Battery messages
listed in Table provide status and warning information for batteries in a
particular chassis.
Table 2-15. Battery Sensor Messages
Event Description
ID
1700

Severity

Critical/
Sensor location:
Battery sensor has failed

Chassis location:
Previous state was:
Battery sensor status:

1701

Battery sensor value unknown
Sensor Location:
Chassis Location:
Previous state was:
Battery sensor status:

1702

Warning

Cause
A battery sensor in
the specified system
is not functioning.
The sensor location,
chassis location,
previous state, and
battery sensor status
are provided.

A battery sensor in
the specified system
could not retrieve a
reading. The sensor
location, chassis
location, previous
state, and battery
sensor status are
provided.

Information A battery sensor in
the specified system
detected that a
Sensor Location:
back to a normal
Chassis Location:
location, chassis
location, previous
Previous state was:
state, and battery
Battery sensor status:
sensor status are

provided.
Battery sensor returned to a
normal value

Event Message Reference

Table 2-15.

Battery Sensor Messages (continued)

Event Description
ID

Severity

Cause

1703

Warning

A battery sensor in
the specified system
detected that
a battery is in
a predictive failure
state. The sensor
location, chassis
location, previous
state, and battery
sensor status are
provided.

Error

A battery sensor in
the specified system
detected that
a battery has failed.
The sensor location,
chassis location,
previous state,
and battery sensor
status are provided.

Error

A battery sensor in
the specified system
detected that a
battery has failed.
The sensor location,
chassis location,
previous state, and
battery sensor status
are provided.

Battery sensor detected a
warning value
Sensor Location:
Chassis Location:
Previous state was:
Battery sensor status:

1704

Battery sensor detected a
failure value
Sensor Location:
Chassis Location:
Previous state was:
Battery sensor status:

1705

Battery sensor detected a
non-recoverable value
Sensor Location:
Chassis Location:
Previous state was:
Battery sensor status:

Event Message Reference

Chassis Management Controller Messages
Alerts sent by Dell™ PowerEdge™ M1000e Blade Enclosure are organized by
severity. That is, the event ID of the CMC trap indicates the severity
(informational, warning, critical, or non-recoverable) of the alert. Each CMC
alert includes the originating system name, location, and event message text.
The alert message text matches the corresponding Chassis Event Log
message text that is logged by the sending CMC for that event.
Table 2-16. Chassis Management Controller Messages
EventID

Description

2000

CMC generated a Informational
test trap

A user-initiated test trap
was issued, through the
CMC GUI or RACADM
CLI.

2002

CMC reported a Informational
return-to-normal
or informational

CMC informational
event, as described in the
drsCAMessage variable
binding supplied with
the alert.

2003

CMC reported a
warning

Warning

CMC warning event, as
described in the
drsCAMessage variable
supplied with the alert.

2004

CMC reported a
critical event

Critical

CMC critical event, as
described in the
drsCAMessage variable
binding supplied with
the alert.

2005

CMC reported a
non-recoverable
event

Non-Recoverable

CMC non-recoverable
event, as described in the
drsCAMessage variable
binding supplied with
the alert.

Event Message Reference

Severity

Cause

System Event Log Messages for
IPMI Systems
The tables in this chapter list the system event log (SEL) messages,
their severity, and cause.
NOTE: For corrective actions, see the appropriate documentation.

Temperature Sensor Events
The temperature sensor event messages help protect critical components by
alerting the systems management console when the temperature rises inside
the chassis. These event messages use additional variables, such as sensor
location, chassis location, previous state, and temperature sensor value or state.
Table 3-1.

Temperature Sensor Events

Event Message

Severity

Cause

temperature sensor
detected a failure
where is the
entity that this sensor
is monitoring. For
example, "PROC Temp" or
"Planar Temp."

Critical

Temperature of the backplane
board, system board, or the carrier
in the specified system exceeded the
critical threshold.

Warning

Temperature of the backplane
board, system board, or the carrier
in the specified system exceeded the
non-critical threshold.

Reading is specified in
degree Celsius. For
example 100 C.

temperature sensor
detected a warning
.

System Event Log Messages for IPMI Systems

Table 3-1.

Temperature Sensor Events (continued)

Event Message

Severity

Warning
temperature sensor
returned to warning state
.

temperature sensor
returned to normal state
.

Cause
Temperature of the backplane
board, system board, or the carrier
in the specified system returned from
critical state to non-critical state.

Information Temperature of the backplane
board, system board, or the carrier
in the specified system returned to
normal operating range.

Voltage Sensor Events
The voltage sensor event messages monitor the number of volts across critical
components. These messages provide status and warning information for
voltage sensors for a particular chassis.
Table 3-2.

Voltage Sensor Events

Event Message

Severity

Critical
voltage sensor detected
a failure where
is
the entity that this sensor
is monitoring.

Cause
The voltage of the monitored
device has exceeded the critical
threshold.

Reading is specified in
volts.
For example, 3.860 V.

voltage sensor state
asserted.

Critical

voltage sensor state
de-asserted.

Information The voltage of a previously
reported
is
returned to normal state.

The voltage specified by
is in
critical state.

System Event Log Messages for IPMI Systems

Table 3-2.

Voltage Sensor Events (continued)

Event Message

Severity

Cause

voltage sensor detected a
warning .

Warning

Voltage of the monitored
entity

exceeded the warning
threshold.

voltage sensor returned to
normal .

Information The voltage of a previously
reported
is
returned to normal state.

Fan Sensor Events
The cooling device sensors monitor how well a fan is functioning. These
messages provide status warning and failure messages for fans for a particular
chassis.
Table 3-3.

Fan Sensor Events

Event Message

Severity

Critical
Fan sensor detected a
failure
where is the
entity that this
sensor is monitoring.
For example "BMC Back
Fan" or "BMC Front
Fan."

Cause
The speed of the specified fan is not sufficient
to provide enough cooling to the
system.

Reading is specified
in RPM. For example,
100 RPM.

Information The fan specified by has returned to its normal
Fan sensor returned to
operating speed.
normal state
.

System Event Log Messages for IPMI Systems

Table 3-3.

Fan Sensor Events (continued)

Event Message

Severity

Warning
Fan sensor detected a
warning .

Cause
The speed of the specified fan may not be
sufficient to provide enough cooling
to the system.

Information The fan specified by may have failed and hence,
redundancy degraded.
the redundancy has been degraded.
Critical
Fan Redundancy sensor
redundancy lost.

The fan specified by may have failed and hence,
the redundancy that was degraded
previously has been lost.

Information The fan specified by may have started
redundancy regained
functioning again and hence, the
redundancy has been regained.

System Event Log Messages for IPMI Systems

Processor Status Events
The processor status messages monitor the functionality of the processors in a
system. These messages provide processor health and warning information of
a system.
Table 3-4.

Processor Status Events

Event Message

Severity

status Critical
processor sensor IERR,
where
is the processor that
generated the event. For
example, PROC for a single
processor system and PROC
# for multiprocessor
system.
status
processor sensor Thermal
Trip.

Critical

Cause
IERR internal error generated
by the .
This event is generated due to
processor internal error.

The processor generates this
event before it shuts down
because of excessive heat caused
by lack of cooling or heat
synchronization.

status Information This event is generated when
processor sensor recovered
a processor recovers from
from IERR.
the internal error.
status Warning
processor sensor disabled.

This event is generated for all
processors that are disabled.

status
processor sensor
terminator not present.

Information This event is generated if the
terminator is missing on an
empty processor slot.

< Processor Entity>
presence was deasserted.

Critical

presence was asserted.

Information This event is generated when
the earlier processor detection
error was corrected.

This event is generated when
the system could not detect
the processor.

System Event Log Messages for IPMI Systems

Table 3-4.

Processor Status Events (continued)

Event Message

Severity

Cause

thermal Information This event is generated when the
tripped was deasserted.
processor has recovered from an
earlier thermal condition.

configuration error was
asserted.

Critical

This event is generated when the
processor configuration is
incorrect.

configuration error was
deasserted.

Information This event is generated when the
earlier processor configuration
error was corrected.

throttled was asserted.

Warning

This event is generated when the
processor slows down to prevent
overheating.

Information This event is generated when the
throttled was deasserted.
earlier processor throttled event
was corrected.

Power Supply Events
The power supply sensors monitor the functionality of the power supplies.
These messages provide status and warning information for power supplies
for a particular system.
Table 3-5.

Power Supply Events

Event Message

Severity

power supply sensor
removed.

Cause
This event is generated when the
power supply sensor is removed.

power supply sensor
power supply has been replaced.
AC recovered.
power supply sensor
power supply that failed or
returned to normal state.
removed was replaced and the
state has returned to normal.

System Event Log Messages for IPMI Systems

Table 3-5.

Power Supply Events (continued)

Event Message

Severity

Cause

PS
Redundancy
sensor redundancy
degraded.

Information Power supply redundancy is
degraded if one of the power
supply sources is removed or
failed.

PS
Redundancy
sensor redundancy lost.

Critical

PS
Redundancy
sensor redundancy
regained.

Information This event is generated if the
power supply has been
reconnected or replaced.

predictive failure
was asserted

Critical

This event is generated when the
power supply is about to fail.

input lost was
asserted

Critical

This event is generated when the
power supply is unplugged.

predictive failure
was deasserted

Information This event is generated when the
power supply has recovered from
an earlier predictive failure event.

input lost was
deasserted

Information This event is generated when the
power supply is plugged in.

Power supply redundancy is lost
if only one power supply is
functional.

System Event Log Messages for IPMI Systems

Memory ECC Events
The memory ECC event messages monitor the memory modules in a system.
These messages monitor the ECC memory correction rate and the type of
memory events that occurred.
Table 3-6.

Memory ECC Events

Event Message

Severity

Cause

ECC error correction
detected on Bank #
DIMM [A/B].

Information This event is generated when there is a
memory error correction on a particular
Dual Inline Memory Module (DIMM).

ECC uncorrectable
error detected on
Bank # [DIMM].

Critical

This event is generated when the
chipset is unable to correct the memory
errors. Usually, a bank number is
provided and DIMM may or may not be
identifiable, depending on the error.

Correctable memory
error logging
disabled.

Critical

This event is generated when the
chipset in the ECC error correction rate
exceeds a predefined limit.

BMC Watchdog Events
The BMC watchdog operations are performed when the system hangs or
crashes. These messages monitor the status and occurrence of these events
in a system.
Table 3-7.

BMC Watchdog Events

Event Message

Severity

BMC OS Watchdog timer
expired.

Information This event is generated when the
BMC watchdog timer expires and no
action is set.

BMC OS Watchdog
performed system
reboot.

Critical

Cause

This event is generated when the
BMC watchdog detects that the
system has crashed (timer expired
because no response was received
from Host) and the action is set
to reboot.

System Event Log Messages for IPMI Systems

Table 3-7.

BMC Watchdog Events (continued)

Event Message

Severity

Cause

BMC OS Watchdog
Critical
performed system power
off.

This event is generated when the
BMC watchdog detects that the
system has crashed (timer expired
because no response was received
from Host) and the action is set to
power off.

BMC OS Watchdog
Critical
performed system power
cycle.

This event is generated when the
BMC watchdog detects that the
system has crashed (timer expired
because no response was received
from Host) and the action is set to
power cycle.

Memory Events
The memory modules can be configured in different ways in particular
systems. These messages monitor the status, warning, and configuration
information about the memory modules in the system.
Table 3-8.

Memory Events

Event Message

Severity

Cause

Memory RAID
redundancy
degraded.

Warning

This event is generated when there is
a memory failure in a RAID-configured
memory configuration.

Memory RAID
redundancy lost.

Critical

This event is generated when redundancy
is lost in a RAID-configured memory
configuration.

Memory RAID
redundancy
regained

Information This event is generated when the
redundancy lost or degraded earlier is
regained in a RAID-configured
memory configuration.

Memory Mirrored
redundancy
degraded.

Warning

This event is generated when there is
a memory failure in a mirrored
memory configuration.

System Event Log Messages for IPMI Systems

Table 3-8.

Memory Events (continued)

Event Message

Severity

Cause

Memory Mirrored
redundancy lost.

Critical

This event is generated when redundancy is
lost in a mirrored memory configuration.

Memory Mirrored
redundancy
regained.

Information This event is generated when the
redundancy lost or degraded earlier is
regained in a mirrored
memory configuration.

Memory Spared
redundancy
degraded.

Warning

This event is generated when there is
a memory failure in a spared
memory configuration.

Memory Spared
redundancy lost.

Critical

This event is generated when redundancy is
lost in a spared memory configuration.

Memory Spared
redundancy
regained.

Information This event is generated when the
redundancy lost or degraded earlier is
regained in a spared memory configuration.

Hardware Log Sensor Events
The hardware logs provide hardware status messages to the system
management software. On particular systems, the subsequent hardware
messages are not displayed when the log is full. These messages provide status
and warning messages when the logs are full.
Table 3-9.

Hardware Log Sensor Events

Event Message

Severity

Cause

Log full
detected.

Critical

This event is generated when the SEL device
detects that only one entry can be added to
the SEL before it is full.

Log cleared.

Information This event is generated when the SEL
is cleared.

System Event Log Messages for IPMI Systems

Drive Events
The drive event messages monitor the health of the drives in a system.
These events are generated when there is a fault in the drives indicated.
Table 3-10.

Drive Events

Event Message

Severity

Cause

Drive
Critical
asserted fault state.

This event is generated when the
specified drive in the array is faulty.

Drive deInformation
asserted fault state.

This event is generated when the
specified drive recovers from a faulty
condition.

Informational This event is generated when the
drive is installed.

Drive
drive presence was
asserted

Warning

Drive
predictive failure
was asserted

This event is generated when the
drive is about to fail.

predictive failure
was deasserted

Informational This event is generated when the
drive from earlier predictive failure is
corrected.

Drive

Warning

Drive

hot spare was
asserted

This event is generated when the
drive is placed in a hot spare.

Informational This event is generated when the
drive is taken out of hot spare.

Drive
hot spare was
deasserted

Warning

Drive
consistency check in
progress was asserted
Drive
consistency check in
progress was
deasserted

This event is generated when the
drive is placed in consistency check.

Informational This event is generated when the
consistency check of the drive is
completed.

System Event Log Messages for IPMI Systems

Table 3-10. Drive Events (continued)
Event Message

Severity

Cause

Drive

Critical

This event is generated when the
drive is placed in critical array.

in critical array was
asserted
Drive
in critical array was
deasserted
Drive

Informational This event is generated when the
drive is removed from critical array.
Critical

in failed array was
asserted
Drive
in failed array was
deasserted
Drive
rebuild in progress
was asserted
Drive
rebuild aborted was
asserted

This event is generated when the
drive is placed in the fail array.

Informational This event is generated when the
drive is removed from the fail array.
Informational This event is generated when the
drive is rebuilding.
Warning

This event is generated when the
drive rebuilding process is aborted.

System Event Log Messages for IPMI Systems

Intrusion Events
The chassis intrusion messages are a security measure. Chassis intrusion
alerts are generated when the system's chassis is opened. Alerts are sent to
prevent unauthorized removal of parts from the chassis.
Table 3-11.

Intrusion Events

Event Message

Severity

Cause

sensor detected
an intrusion.

Critical

This event is generated when the
intrusion sensor detects an intrusion.

sensor returned
to normal state.

Information This event is generated when the
earlier intrusion has been corrected.

sensor intrusion
was asserted while
system was ON

This event is generated when the
intrusion sensor detects an intrusion
while the system is on.

sensor intrusion
was asserted while
system was OFF

This event is generated when the
intrusion sensor detects an intrusion
while the system is off.

System Event Log Messages for IPMI Systems

BIOS Generated System Events
The BIOS-generated messages monitor the health and functionality of the
chipsets, I/O channels, and other BIOS-related functions.
Table 3-12. BIOS Generated System Events
Event Message

Severity

Cause

System Event I/O
channel chk.

Critical

This event is generated when a
critical interrupt is generated in the
I/O Channel.

System Event PCI
Parity Err.

Critical

This event is generated when a parity
error is detected on the PCI bus.

System Event Chipset
Err.

Critical

This event is generated when a chip
error is detected.

System Event PCI
System Err.

Information This event indicates historical data,
and is generated when the system
has crashed and recovered.

System Event PCI
Fatal Err.

Critical

This error is generated when a fatal
error is detected on the PCI bus.

System Event PCIE
Fatal Err.

Critical

This error is generated when a fatal
error is detected on the PCIE bus.

POST Err

Critical

This event is generated when an error
occurs during system boot. See the
system documentation for more
information on the error code.

POST fatal error
# or

Critical

This event is generated when a fatal
error occurs during system boot.
See “Table 3-13” for more information.

Memory Spared

Critical

This event is generated when memory
spare is no longer redundant.

Critical

This event is generated when memory
mirroring is no longer redundant.

Critical

This event is generated when memory
RAID is no longer redundant.

redundancy lost
Memory Mirrored
redundancy lost
Memory RAID
redundancy lost

System Event Log Messages for IPMI Systems

Table 3-12.

BIOS Generated System Events (continued)

Event Message

Severity

Err Reg Pointer

Information This event is generated when an OEM
event occurs. OEM events can be used
by Dell™ service team to better
understand the cause of the failure.

OEM Diagnostic data
event was asserted

Cause

System Board PFault
Fail Safe state
asserted

Critical

System Board PFault
Fail Safe state
deasserted

Information This event is generated when earlier
PFault Fail Safe system voltages return
to a normal level.

Memory Add

Information This event is generated when memory
is added to the system.

(BANK# DIMM#)
presence was asserted
Memory Removed
(BANK# DIMM#)
presence was asserted
Memory Cfg Err

This event is generated when the
system board voltages are not at
normal levels.

Information This event is generated when memory
is removed from the system.
Critical

configuration error
(BANK# DIMM#) was
asserted

This event is generated when
memory configuration is incorrect for
the system.

redundancy regained

Information This event is generated when memory
redundancy is regained.

Mem ECC Warning

Warning

This event is generated when
correctable ECC errors have increased
from a normal rate.

Critical

This event is generated when
correctable ECC errors reach a
critical rate.

Critical

This event is generated when CRC
errors enter a non-recoverable state.

Mem Redun Gain

transition to noncritical from OK
Mem ECC Warning
transition to
critical from less
severe
Mem CRC Err
transition to nonrecoverable

System Event Log Messages for IPMI Systems

Table 3-12. BIOS Generated System Events (continued)
Event Message

Severity

Cause

Mem Fatal SB CRC

Critical

This event is generated when CRC
errors occur while storing to memory.

Critical

This event is generated when CRC
errors occur while removing from
memory.

Critical

This event is generated when system
memory reaches critical temperature.

Critical

This event is generated when the USB
exceeds a predefined current level.

Hdwr version err
Critical
hardware
incompatibility
(BMC/iDRAC Firmware
and CPU mismatch) was
asserted

This event is generated when there is
a mismatch between the BMC and
iDRAC firmware and the processor in
use or vice versa.

uncorrectable ECC was
asserted
Mem Fatal NB CRC
uncorrectable ECC was
asserted
Mem Overtemp
critical over
temperature
was asserted
USB Over-current
transition to nonrecoverable

Hdwr version err
Information This event is generated when the
hardware
earlier mismatch between the BMC
incompatibility(BMC /
and iDRAC firmware and the processor
iDRAC Firmware and
is corrected.
CPU mismatch) was
deasserted
SBE Log Disabled
correctable memory
error logging
disabled was asserted

Critical

This event is generated when the ECC
single bit error rate is exceeded.

System Event Log Messages for IPMI Systems

Table 3-12.

BIOS Generated System Events (continued)

Event Message

Severity

Cause

CPU Protocol Err

Critical

This event is generated when the
processor protocol enters
a non-recoverable state.

Critical

This event is generated when
the processor bus PERR enters
a non-recoverable state.

Critical

This event is generated when the
processor initialization enters
a non-recoverable state.

Critical

This event is generated when the
processor machine check enters
a non-recoverable state.

Critical

This event is generated when all event
logging is disabled.

transition to
non-recoverable
CPU Bus PERR
transition to
non-recoverable
CPU Init Err
transition to
non-recoverable
CPU Machine Chk
transition to
non-recoverable
Logging Disabled
all event logging
disabled was asserted
LinkT/FlexAddr: Link Critical
Tuning sensor, device
option ROM failed to
support link tuning
or flex address (Mezz
XX) was asserted

This event is generated when the
PCI device option ROM for a NIC
does not support link tuning or the
Flex addressing feature.

LinkT/FlexAddr: Link Critical
Tuning sensor, failed
to program virtual
MAC address
() was
asserted.

This event is generated when BIOS
fails to program virtual MAC address
on the given NIC device.

System Event Log Messages for IPMI Systems

Table 3-12. BIOS Generated System Events (continued)
Event Message

Severity

PCIE NonFatal Er: Non Warning
Fatal IO Group
sensor, PCIe
error()

Cause
This event is generated in association
with a CPU IERR.

Critical

This event is generated in association
with a CPU IERR and indicates the
PCI/PCIe device that caused the CPU
IERR.

Unknown system event Critical
sensor unknown system
hardware failure was
asserted

This event is generated when an
unknown hardware failure is detected.

I/O Fatal Err: Fatal
IO Group sensor,
fatal IO error
()

POST Code Table

Table 3-13 lists the POST Code errors that are generated when a fatal error
occurs during system boot.
Table 3-13. POST Code Errors
Fatal Error Code

Description

Cause

No memory detected

This error code implies
that no memory is
installed.

Memory detected but is not
configurable

This error code
indicates memory
configuration error
that could be result of
bad memory,
mismatched memory
or bad socket.

Memory configured but not
usable.

This error code
indicates memory subsystem failure.

System Event Log Messages for IPMI Systems

Table 3-13.

POST Code Errors (continued)

Fatal Error Code

Description

Cause

System BIOS shadow failure

This error code
indicates system BIOS
shadow failure.

CMOS failure

This error code
indicates that CMOS
RAM is not working.

DMA controller failure

This error code
indicates DMA
controller failure.

Interrupt controller failure

This error code
indicates interrupt
controller failure.

Timer refresh failure

This error code
indicates timer refresh
failure.

Programmable interval
timer error

This error code
indicates a
programmable interval
timer error.

Parity error

This error code
indicates a parity error.

SIO failure

This error code
indicates SIO failure.

Keyboard controller failure

This error code
indicates keyboard
controller failure.

SMI initialization failure

This error code
indicates SMI
initialization failure.

Shutdown test failure

This error code
indicates a shutdown
test failure.

System Event Log Messages for IPMI Systems

Table 3-13. POST Code Errors (continued)
Fatal Error Code

Description

Cause

POST Memory test failure

This error code
indicates bad memory
detection.

RAC configuration failure

Check screen for the
actual error message

CPU configuration failure

Check screen for the
actual error message

Incorrect memory
configuration

Memory population
order not correct.

General failure after video

Check screen for the
actual error message

R2 Generated System Events
Table 3-14. R2 Generated Events
Description

Severity

Cause

System Event: OS stop
event OS graceful
shutdown detected

Information

The OS was shutdown/restarted
normally.

OEM Event data record
(after OS graceful
shutdown/restart event)

Information

Comment string accompanying
an OS shutdown/restart.

System Event: OS stop
event runtime critical
stop

Critical

The OS encountered a critical
error and was stopped
abnormally.

OEM Event data record
Information
(after OS bugcheck event)

OS bugcheck code and
paremeters.

System Event Log Messages for IPMI Systems

Cable Interconnect Events
The cable interconnect messages are used for detecting errors in the hardware
cabling.
Table 3-15.

Cable Interconnect Events

Description

Severity

Cause

Cable sensor

Critical

This event is generated when
the cable is not connected or
is incorrectly connected.

Information

This event is generated when
the earlier cable connection
error was corrected.

Configuration error was
asserted.

Cable sensor
Connection was asserted.

Battery Events
Table 3-16.

Battery Events

Description

Severity

Cause

Critical

This event is generated when
the sensor detects a failed or
missing battery.

Information

This event is generated when
the earlier failed battery was
corrected.

Warning

This event is generated when
the sensor detects a low battery
condition.

Information

This event is generated when
the earlier low battery condition
was corrected.

Failed was asserted

Failed was deasserted

is low was asserted

is low was deasserted

System Event Log Messages for IPMI Systems

Power And Performance Events
The power and performance events are used to detect degradation in system
performance with change in power supply.
Table 3-17. Power And Performance Events
Description

Severity

Cause

System Board Power Normal
Optimized:
Performance status
sensor for System
Board, degraded,
was
deasserted

This event is generated when
system performance was
restored.

System Board Power Warning
Optimized:
Performance status
sensor for System
Board, degraded,
was asserted

This event is generated when
change in power supply
degrades system
performance.

Entity Presence Events
The entity presence messages are used for detecting different hardware
devices.
Table 3-18. Entity Presence Events
Description

Severity

Cause

Information

This event is generated when the device
was detected.

Critical

This event is generated when the device
was not detected.

presence was
asserted

absent was asserted

System Event Log Messages for IPMI Systems

Storage Management Message
Reference
The Dell™ OpenManage™ Server Administrator Storage Management’s alert
or event management features let you monitor the health of storage resources
such as controllers, enclosures, physical disks, and virtual disks.

Alert Monitoring and Logging
The Storage Management Service performs alert monitoring and logging.
By default, the Storage Management Service starts when the managed system
starts up. If you stop the Storage Management Service, then alert monitoring
and logging stops. Alert monitoring does the following:
•

Updates the status of the storage object that generated the alert.

•

Propagates the storage object’s status to all the related higher objects in
the storage hierarchy. For example, the status of a lower-level object will be
propagated up to the status displayed on the Health tab for the top-level
Storage object.

•

Logs an alert in the Alert log and the operating system (OS) application log.
NOTE: Dell OpenManage Server Administrator Storage Management does not log
alerts regarding the data I/O path. These alerts are logged by the respective RAID
drivers in the system alert log.

See the Storage Management Online Help for updated information.

Storage Management Message Reference

Alert Message Format with Substitution
Variables
When you view an alert in the Server Administrator alert log, the alert identifies
the specific components such as the controller name or the virtual disk name to
which the alert applies. In an actual operating environment, a storage system
can have many combinations of controllers and disks as well as user-defined
names for virtual disks and other components. Because each environment is
unique in its storage configuration and user-defined names, an accurate alert
message requires that the Storage Management Service be able to insert the
environment-specific names of storage components into an alert message.
This environment-specific information is inserted after the alert message
text as shown for alert 2127 in Table 4-1.
For other alerts, the alert message text is constructed from information
passed directly from the controller (or another storage component) to the
Alert Log. In these cases, the variable information is represented with a%
(percent sign) in the Storage Management documentation. An example of
such an alert is shown in Table 4-1.
Table 4-1.

Alert Message Format

Alert ID Message Text Displayed in the Message Text Displayed in the Alert Log with
Storage Management Service Variable Information Supplied
Documentation
2127

Background Initialization
started

Background Initialization started: Virtual
Disk 3 (Virtual Disk 3) Controller 1
(PERC 5/E Adapter)

2334

Controller event log%

Controller event log: Current capacity of the
battery is above threshold.: Controller 1
(PERC 5/E Adapter)

The variables required to complete the message vary depending on the type
of storage object and whether the storage object is in a SAS configuration.
The following table identifies the possible variables used to identify each
storage object.
NOTE: Some alert messages relating to an enclosure or an enclosure component,
such as a fan or EMM, are generated by the controller when the enclosure or
enclosure component ID cannot be determined.
82

Storage Management Message Reference

Table 4-2.

Message Format with Variables for Each Storage Object

Storage Object

Message Variables
A, B, C and X, Y, Z in the following examples are variables
representing the storage object name or number.

Controller

Message Format: Controller A (Name)
Message Format: Controller A
Example: 2326 A foreign configuration has been detected.:
Controller 1 (PERC 5/E Adapter)

NOTE: The controller name is not always displayed.
Battery

Message Format: Battery X Controller A
Example: 2174 The controller battery has been removed: Battery 0
Controller 1

Virtual Disk

Message Format: Virtual Disk X (Name) Controller A (Name)
Message Format: Virtual Disk X Controller A
Example: 2057 Virtual disk degraded: Virtual Disk 11 (Virtual Disk
11) Controller 1 (PERC 5/E Adapter)

NOTE: The virtual disk and controller names are not always displayed.
Enclosure:

Message Format: Enclosure X:Y Controller A, Connector B
Example: 2112 Enclosure shutdown: Enclosure 0:2 Controller 1,
Connector 0

SAS Power
Supply

Message Format: Power Supply X Controller A, Connector B,
Enclosure C
Example: 2312 A power supply in the enclosure has an AC failure.:
Power Supply 1, Controller 1, Connector 0, Enclosure 2

SAS
Temperature
Probe

Message Format: Temperature Probe X Controller A, Connector B,
Enclosure C
Example: 2101 Temperature dropped below the minimum warning
threshold: Temperature Probe 1, Controller 1, Connector 0,
Enclosure 2

Storage Management Message Reference

Table 4-2.

Message Format with Variables for Each Storage Object (continued)

Storage Object

Message Variables
A, B, C and X, Y, Z in the following examples are variables
representing the storage object name or number.

SAS Fan

Message Format: Fan X Controller A, Connector B, Enclosure C
Example: 2121 Device returned to normal: Fan 1, Controller 1,
Connector 0, Enclosure 2

SAS EMM

Message Format: EMM X Controller A, Connector B, Enclosure C
Example: 2121 Device returned to normal: EMM 1, Controller 1,
Connector 0, Enclosure 2

Alert Message Change History
The following table describes the changes made to the Storage Management
alerts from the previous release of Storage Management to the current release.
Table 4-3.

Alert Message Change History

Alert Message Change History
Storage Management 3.0.3

Comments

Product Versions Storage Management 3.0.3
to which
Server Administrator 6.0.3
Changes Apply
Dell OpenManage 6.0.3
New Alerts

2370

Documentation
Change

Removed SNMP Traps and LRA
numbers. Modified the Clear
Alert Number and Related Alert
Number for alert 2250.

Storage Management 3.0.2

Comments

Product Versions Storage Management 3.0.2
to which
Server Administrator 6.0.1
Changes Apply
Dell OpenManage 6.0.1
New Alerts

2382

Storage Management Message Reference

Alert Descriptions and Corrective Actions
The following sections describe alerts generated by the RAID controllers
supported by Storage Management. The alerts are displayed in the Server
Administrator Alert subtab or through Windows Event Viewer. These alerts
can also be forwarded.
To locate an alert, scroll through the following table to find the alert number
displayed on the Server Administrator Alert tab or search this file for the alert
message text or number. See "Understanding Event Messages" for more
information on severity levels.
For more information regarding alert descriptions and the appropriate
corrective actions, see the online help.
Table 4-4.

Storage Management Messages

Event ID

Description

2048

Device failed Critical /
Cause: A storage
Failure / Error component such as
a physical disk or an
enclosure has failed.
The failed component
may have been
identified by the
controller while
performing a task such
as a rescan or
a check consistency.

Severity

Cause and Action

Related Alert
Information
Clear Alert
Number:
2121.
Related Alert
Number:
2095, 2201,
2203

Action: Replace the failed
component. You can
identify which disk has
failed by locating the disk
that has a red “X” for its
status. Perform a rescan
after replacing the failed
component.

Storage Management Message Reference

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

Severity

Cause and Action

Related Alert
Information

2049

Physical disk
removed

Warning /
Non-critical

Cause: A physical disk has
been removed from the
disk group. This alert can
also be caused by loose or
defective cables or by
problems with the
enclosure.

Clear Alert
Number:
2052.

Related Alert
Number:
2054, 2057,
2056, 2076,
Action: If a physical disk
2079, 2081,
was removed from the disk 2083, 2129,
group, either replace the
2202, 2204,
disk or restore the original 2270, 2292,
disk. On some controllers, 2299, 2369
a removed disk has a red
"X" for its status. On other
controllers, a removed disk
may have an Offline
status or is not displayed
on the user interface.
Perform a rescan after
replacing or restoring the
disk. If a disk has not been
removed from the disk
group, then check for
problems with the cables.
See the online help for
more information on
checking the cables. Make
sure that the enclosure is
powered on. If the problem
persists, check the
enclosure documentation
for further diagnostic
information.

Storage Management Message Reference

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

Severity

Cause and Action

Related Alert
Information

2050

Physical disk
offline

Warning /
Non-critical

Cause: A physical disk in
the disk group is offline.
The user may have
manually put the physical
disk offline.

Clear Alert
Number:
2158.

Action: Perform a rescan.
You can also select the
offline disk and perform
a Make Online operation.
2051

Physical disk
degraded

Warning /
Non-critical

Cause: A physical disk has
reported an error condition
and may be degraded.
The physical disk may
have reported the error
condition in response to
a consistency check or
other operation.

Related Alert
Number:
2099, 2196

Clear Alert
Number:
None.
Related Alert
Number:
2070

Action: Replace the
degraded physical disk.
You can identify which disk
is degraded by locating the
disk that has a red "X" for
its status. Perform a rescan
after replacing the disk.
2052

Physical disk
inserted

OK / Normal / Cause: This alert is for
Informational informational purposes.
Action: None

Clear Alert
Number:
None.
Related Alert
Number:
2065, 2305,
2367

Storage Management Message Reference

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

Severity

2053

Virtual disk
created

OK / Normal / Cause: This alert is for
Informational informational purposes.

Cause and Action

Action: None

Related Alert
Information
Clear Alert
Number:
None.
Related Alert
Number:
None.

2054

Virtual disk
deleted

Warning /
Non-critical

Cause: A virtual disk has
been deleted. Performing a
Reset Configuration may
detect that a virtual disk
has been deleted and
generate this alert.

Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: None
2055

Virtual disk
OK / Normal / Cause: This alert is for
configuraInformational informational purposes.
tion changed
Action: None

Clear Alert
Number:
None.
Related Alert
Number:
None.

Storage Management Message Reference

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

Severity

2056

Virtual disk
failed

Critical /
Cause: One or more
Failure / Error physical disks included in
the virtual disk have failed.
If the virtual disk is
non-redundant (does not
use mirrored or parity data),
then the failure of a single
physical disk can cause the
virtual disk to fail. If the
virtual disk is redundant,
then more physical disks
have failed than can be
rebuilt using mirrored or
parity information.

Cause and Action

Related Alert
Information
Clear Alert
Number:
None.
Related Alert
Number:
2048, 2049,
2050, 2076,
2079, 2081,
2129, 2346

Action: Create a new virtual
disk and restore from a
backup.
The disk controller, rebuild
the virtual disk by first
configuring a hot spare for
the disk, and then
initiating a write operation
to the disk. The write
operation will initiate a
rebuild of the disk.

Storage Management Message Reference

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

Severity

Cause and Action

Related Alert
Information

2057

Virtual disk
degraded

Warning /
Non-critical

Cause 1: This alert
message occurs when a
physical disk included in a
redundant virtual disk fails.
Because the virtual disk is
redundant (uses mirrored
or parity information) and
only one physical disk has
failed, the virtual disk can
be rebuilt.

Clear Alert
Number:
None.

Action 1: Configure a hot
spare for the virtual disk if
one is not already
configured. Rebuild the
virtual disk. When using an
Expandable RAID
Controller (PERC) PERC
PERC 5/E, PERC 5/i or a
(SAS) 5/iR controller,
rebuild the virtual disk by
first configuring a hot spare
for the disk, and then
initiating a write operation
to the disk. The write
operation will initiate a
rebuild of the disk.

Storage Management Message Reference

Related Alert
Number:
2048, 2049,
2050, 2076,
2079, 2081,
2123, 2129,
2346

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2057
contd.

Severity

Cause and Action

Related Alert
Information

Cause 2: A physical disk in
the disk group has been
removed.
Action 2: If a physical disk
was removed from the disk
group, either replace the
disk or restore the original
disk. You can identify
which disk has been
removed by locating the
disk that has a red “X” for
its status. Perform a rescan
after replacing the disk.

2058

2059

Virtual disk
check
consistency
started

OK / Normal / Cause: This alert is for
Informational informational purposes.

Virtual disk
format
started

OK / Normal / Cause: This alert is for
Informational informational purposes.

Action: None

Clear Alert
Number:
2085.
Related Alert
Number:
None.

Action: None

Clear Alert
Number:
2086.
Related Alert
Number:
None.

2060

Copy of data OK / Normal / Cause: This alert is for
started on
Informational informational purposes.
physical disk
Action: None
1 from
physical
disk 2.

Clear Alert
Number:
None.
Related Alert
Number:
2075

Storage Management Message Reference

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2061

Virtual disk
OK / Normal / Cause: This alert is for
initializa-tion Informational informational purposes.
started
Action: None

Severity

Cause and Action

Related Alert
Information
Clear Alert
Number:
2088.
Related Alert
Number:
None.

2062

Physical disk OK / Normal / Cause: This alert is for
initializa-tion Informational informational purposes.
started
Action: None.

Clear Alert
Number:
2089.
Related Alert
Number:
None.

2063

2064

Virtual disk
reconfiguration
started

OK / Normal / Cause: This alert is for
Informational informational purposes.

Virtual disk
rebuild
started

OK / Normal / Cause: This alert is for
Informational informational purposes.

Action: None

Clear Alert
Number:
2090.
Related Alert
Number:
None.

Action: None

Clear Alert
Number:
2091.
Related Alert
Number:
None.

2065

Physical disk
rebuild
started

OK / Normal / Cause: This alert is for
Informational informational purposes.
Action: None

Clear Alert
Number:
2092.
Related Alert
Number:
2099, 2121,
2196

Storage Management Message Reference

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

Severity

2067

Virtual disk
check
consistency
cancelled

OK / Normal / Cause: The check
Informational consistency operation was
cancelled because a
physical disk in the array
has failed or because a user
cancelled the check
consistency operation.

Cause and Action

Related Alert
Information
Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: If the physical disk
failed, then replace the
physical disk. You can
identify which disk failed
by locating the disk that
has a red “X” for its status.
Perform a rescan after
replacing the disk. When
performing a consistency
check, be aware that the
consistency check can take
a long time. The time it
takes depends on the size
of the physical disk or
the virtual disk.

Storage Management Message Reference

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

Severity

2070

Virtual disk
initialization
cancelled

OK / Normal / Cause: The virtual disk
Informational initialization cancelled
because a physical disk
included in the virtual disk
has failed or because a user
cancelled the virtual disk
initialization.

Cause and Action

Related Alert
Information
Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: If a physical disk
failed, then replace the
physical disk. You can
identify which disk has
failed by locating the disk
that has a red “X” for its
status. Perform a rescan
after replacing the disk.
Restart the format physical
disk operation. Restart the
virtual disk initialization.
2074

Physical disk
rebuild
cancelled

OK / Normal / Cause: The user has
Informational cancelled the rebuild
operation.

Clear Alert
Number:
None.

Action: Restart the rebuild Related Alert
operation.
Number:
None.
2075

Copy of data OK / Normal /
completed on Informational
physical
disk %2 from
physical
disk %1

Clear Alert
Cause: This alert is
provided for informational Number:
purposes.
None.
Action: None

Storage Management Message Reference

Related Alert
Number:
2060.

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

Severity

2076

Virtual disk
Check
Consistency
failed

Critical /
Cause: A physical disk
Failure / Error included in the virtual disk
failed or there is an error in
the parity information. A
failed physical disk can
cause errors in parity
information.

Cause and Action

Related Alert
Information
Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: Replace the failed
physical disk. You can
identify which disk has
failed by locating the disk
that has a red “X” for its
status. Rebuild the physical
disk. When finished,
restart the check
consistency operation.
2077

Virtual disk
Critical /
Cause: A physical disk
Clear Alert
format failed Failure / Error included in the virtual disk Number:
failed.
None.
Action: Replace the failed Related Alert
physical disk. You can
Number:
identify which physical disk None.
has failed by locating the
disk that has a red "X" for
its status. Rebuild the
physical disk. When
finished, restart the virtual
disk format operation.

2079

Virtual disk
initialization
failed

Critical /
Cause: A physical disk
Failure / Error included in the virtual disk
has failed or a user has
cancelled the initialization.

Clear Alert
Number:
None.

Related Alert
Action: If a physical disk
Number:
has failed, then replace the None.
physical disk.

Storage Management Message Reference

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

Severity

2080

Physical disk
initialization
failed

Critical /
Cause: The physical disk
Failure / Error has failed or is corrupt.

2081

Virtual disk
Critical /
Cause: A physical disk
reconfigFailure / Error included in the virtual disk
uration failed
has failed or is corrupt.
A user may also have
cancelled
the reconfiguration.

Cause and Action

Clear Alert
Number:
Action: Replace the failed None.
or corrupt disk. You can
Related Alert
identify a disk that has
Number:
failed by locating the disk None.
that has a red “X” for its
status. Restart the
initialization.

Action: Replace the failed
or corrupt disk. You can
identify a disk that has
failed by locating the disk
that has a red “X” for
its status.
If the physical disk is part
of a redundant array, then
rebuild the physical disk.
When finished, restart
the reconfiguration.

Related Alert
Information

Storage Management Message Reference

Clear Alert
Number:
None.
Related Alert
Number:
None.

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2082

Virtual disk
Critical /
Cause: A physical disk
rebuild failed Failure / Error included in the virtual disk
has failed or is corrupt.
A user may also have
cancelled the rebuild.

Clear Alert
Number:
None.

Physical disk Critical /
Cause: A physical disk
rebuild failed Failure / Error included in the virtual disk
has failed or is corrupt.
A user may also have
cancelled the rebuild.

Clear Alert
Number:
None.

Severity

Cause and Action

Related Alert
Information

Related Alert
Number:
Action: Replace the failed 2048
or corrupt disk. You can
identify a disk that has
failed by locating the disk
that has a red “X” for its
status. Restart the virtual
disk rebuild.

2083

Related Alert
Number:
Action: Replace the failed None.
or corrupt disk. You can
identify a disk that has
failed by locating the disk
that has a red “X” for its
status. Rebuild the virtual
disk rebuild.

2085

Virtual disk
check
consistency
completed

OK / Normal / Cause: This alert is for
Informational informational purposes.
Action: None

Clear Alert
Status: Alert
2085 is a clear
alert for alert
2058.
Related Alert
Number:
None.

Storage Management Message Reference

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

Severity

2086

Virtual disk
format
completed

OK / Normal / Cause: This alert is for
Informational informational purposes.

Cause and Action

Action: None

Related Alert
Information
Clear Alert
Status: Alert
2086 is a clear
alert for alert
2059.
Related Alert
Number:
None.

2087

2088

Copy of data OK / Normal / Cause: This alert is for
resumed from Informational informational purposes.
physical disk
Action: None
%2 to physical
disk %1

Clear Alert
Status: None

Virtual disk
OK / Normal / Cause: This alert is for
initializ-ation Informational informational purposes.
completed
Action: None

Clear Alert
Status: Alert
2088 is a clear
alert for alerts
2061 and
2136.

Related Alert
Number: 260.

Related Alert
Number:
None.
2089

Physical disk
initialization
completed

OK / Normal / Cause: This alert is for
Informational informational purposes.
Action: None

Clear Alert
Status: Alert
2089 is a clear
alert for alert
2062.
Related Alert
Number:
None.

Storage Management Message Reference

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

Severity

2090

Virtual disk
reconfiguration
completed

OK / Normal / Cause: This alert is for
Informational informational purposes.

Cause and Action

Action: None

Related Alert
Information
Clear Alert
Status: Alert
2090 is a clear
alert for alert
2063.
Related Alert
Number:
None.

2091

Virtual disk
rebuild
completed

OK / Normal / Cause: This alert is for
Informational informational purposes.
Action: None

Clear Alert
Status: Alert
2091 is a clear
alert for alert
2064.
Related Alert
Number:
None.

2092

Physical disk
rebuild
completed

OK / Normal / Cause: This alert is for
Informational informational purposes.
Action: None

Clear Alert
Status: Alert
2092 is a clear
alert for alert
2065.
Related Alert
Number:
None.

Storage Management Message Reference

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

Severity

Cause and Action

Related Alert
Information

2094

Predictive
Failure
reported.

Warning /
Non-critical

Cause: The physical disk is
predicted to fail. Many
physical disks contain Self
Monitoring Analysis and
Reporting Technology
(SMART). When enabled,
SMART monitors the
health of the disk based on
indications such as the
number of write operations
that have been performed
on the disk.

Clear Alert
Number:
None.

Action: Replace the
physical disk. Even though
the disk may not have
failed yet, it is strongly
recommended that you
replace the disk.
If this disk is part of a
redundant virtual disk,
perform the Offline task
on the disk; replace the
disk; and then assign a hot
spare and the rebuild will
start automatically.

100

Storage Management Message Reference

Related Alert
Number:
None.

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2094
cond.

Severity

Cause and Action

Related Alert
Information

If this disk is a hot spare,
then unassign the hot
spare; perform the Prepare
to Remove task on the disk;
replace the disk; and assign
the new disk as a hot spare.

CAUTION: If this
disk is part of a
nonredundant disk,
back up your data
immediately. If the
disk fails, you will
not be able to recover
the data.
2095

SCSI sense
NOTE: Not data.
Applicable
for
VMware
ESXi 3.5
Update 4
2098

OK / Normal / Cause: A SCSI device
Informational experienced an error, but
may have recovered.
Action: None.

Global hot
OK / Normal / Cause: A user has assigned
spare assigned Informational a physical disk as a global
hot spare. This alert is for
informational purposes.
Action: None

2099

Global hot
spare
unassigned

OK / Normal / Cause: A user has
Informational unassigned a physical disk
as a global hot spare. This
alert is for informational
purposes.
Action: None

Clear Alert
Number:
None.
Related Alert
Number:
2273
Clear Alert
Number:
None.
Related Alert
Number:
2277
Clear Alert
Number:
None.
Related Alert
Number:
None.

Storage Management Message Reference

101

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2100

Temp-erature Warning /
exceeded the Non-critical
maximum
warning
threshold

Severity

Cause and Action

Related Alert
Information

Cause: The physical disk
enclosure is too hot.
A variety of factors can
cause the excessive
temperature. For example,
a fan may have failed,
the thermostat may be set
too high, or the room
temperature may be
too hot.

Clear Alert
Number:
2353.
Related Alert
Number:
2112

Action: Check for factors
that may cause
overheating. For example,
verify that the enclosure
fan is working. You should
also check the thermostat
settings and examine
whether the enclosure is
located near a heat source.
Make sure the enclosure
has enough ventilation and
that the room temperature
is not too hot. See the
physical disk enclosure
documentation for more
diagnostic information.
2101

102

Temp-erature Warning /
dropped
Non-critical
below the
minimum
warning
threshold

Cause: The physical disk
enclosure is too cool.
Action: Check if the
thermostat setting is too
low and if the room
temperature is too cool.

Storage Management Message Reference

Clear Alert
Number:
2353.
Related Alert
Number:
None.

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2102

Temp-erature Critical /
Cause: The physical disk
exceeded the Failure / Error enclosure is too hot.
maximum
A variety of factors can
failure
cause the excessive
threshold
temperature. For example,
a fan may have failed, the
thermostat may be set
too high, or the room
temperature may be
too hot.

Severity

Cause and Action

Related Alert
Information
Clear Alert
Number:
None.
Related Alert
Number:
None.

Temp-erature Critical /
Cause: The physical disk
dropped
Failure / Error enclosure is too cool.
below the
Action: Check if the
minimum
thermostat setting is too
failure
low and if the room
threshold
temperature is too cool.

Clear Alert
Number:
None.
Related Alert
Number:
2112

Storage Management Message Reference

103

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

Severity

2104

Controller
battery is
reconditioning

OK / Normal / Cause: This alert is for
Informational informational purposes.

2105

Cause and Action

Action: None

Related Alert
Information
Clear Alert
Number:
2105.
Related Alert
Number:
None.

Controller
OK / Normal / Cause: This alert is for
battery
Informational informational purposes.
recondition is
Action: None
completed

Clear Alert
Status: Alert
2105 is a clear
alert for alert
2104.
Related Alert
Number:
None.

2106

Smart FPT
exceeded

Warning /
Non-critical

Cause: A disk on the
specified controller has
received a SMART alert
(predictive failure)
indicating that the disk is
likely to fail in the near
future.
Action: Replace the disk
that has received the
SMART alert. If the
physical disk is a member
of a non-redundant virtual
disk, then back up the data
before replacing the disk.

CAUTION: Removing
a physical disk that
is included in a
non-redundant virtual
disk will cause the
virtual disk to fail and
may cause data loss.

104

Storage Management Message Reference

Clear Alert
Number:
None.
Related Alert
Number:
None.

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2107

Smart config- Critical /
Cause: A disk has received
uration
Failure / Error a SMART alert (predictive
change
failure) after a
configuration change.
The disk is likely to fail in
the near future.

Severity

Cause and Action

Related Alert
Information
Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: Replace the disk
that has received the
SMART alert. If the
physical disk is a member
of a nonredundant virtual
disk, then back up the data
before replacing the disk.

CAUTION: Removing
a physical disk that
is included in a
non-redundant virtual
disk will cause the
virtual disk to fail and
may cause data loss.

Storage Management Message Reference

105

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

Severity

Cause and Action

Related Alert
Information

2108

Smart
warning

Warning /
Non-critical

Cause: A disk has received
a SMART alert (predictive
failure). The disk is likely
to fail in the near future.

Clear Alert
Number:
None.

Related Alert
Action: Replace the disk
Number:
that has received the
None.
SMART alert. If the
physical disk is a member
of a non-redundant virtual
disk, then back up the data
before replacing the disk.

CAUTION: Removing
a physical disk that
is included in a
non-redundant virtual
disk will cause the
virtual disk to fail and
may cause data loss.

106

Storage Management Message Reference

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2109

SMART
Warning /
warning
Non-critical
temp-erature

Severity

Cause and Action

Related Alert
Information

Cause: A disk has reached
an unacceptable
temperature and received a
SMART alert (predictive
failure). The disk is likely
to fail in the near future.

Clear Alert
Number:
None.
Related Alert
Number:
None.

Action 1: Determine why
the physical disk has
reached an unacceptable
temperature. A variety of
factors can cause the
excessive temperature. For
example, a fan may have
failed, the thermostat may
be set too high, or the
room temperature may be
too hot or cold. Verify that
the fans in the server or
enclosure are working. If
the physical disk is in an
enclosure, you should
check the thermostat
settings and examine
whether the enclosure is
located near a heat source.

Storage Management Message Reference

107

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2109
contd

Severity

Cause and Action
Make sure the enclosure
has enough ventilation and
that the room temperature
is not too hot. See the
physical disk enclosure
documentation for more
diagnostic information.
Action 2: If you cannot
identify why the disk has
reached an unacceptable
temperature, then replace
the disk. If the physical
disk is a member of a
non-redundant virtual disk,
then back up the data
before replacing the disk.

CAUTION: Removing
a physical disk that
is included in a
non-redundant virtual
disk will cause the
virtual disk to fail and
may cause data loss.

108

Storage Management Message Reference

Related Alert
Information

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

Severity

Cause and Action

Related Alert
Information

2110

SMART
warning
degraded

Warning /
Non-critical

Cause: A disk is degraded
and has received a SMART
alert (predictive failure).
The disk is likely to fail in
the near future.

Clear Alert
Number:
None.

Action: Replace the disk
that has received the
SMART alert. If the
physical disk is a member
of a non-redundant virtual
disk, then back up the data
before replacing the disk.

Related Alert
Number:
None.

CAUTION: Removing
a physical disk that
is included in a
non-redundant virtual
disk will cause the
virtual disk to fail and
may cause data loss.
2111

Failure
Warning /
prediction
Non-critical
threshold
exceeded due
to test

Cause: A disk has
received a SMART alert
(predictive failure) due to
test conditions.
Action: None

Clear Alert
Number:
None.
Related Alert
Number:
None.

Storage Management Message Reference

109

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2112

Enclosure was Critical /
Cause: The physical disk
shut down
Failure / Error enclosure is either hotter or
cooler than the maximum
or minimum allowable
temperature range.

Severity

Cause and Action

Action: Check for factors
that may cause overheating
or excessive cooling. For
example, verify that the
enclosure fan is working.
You should also check the
thermostat settings and
examine whether the
enclosure is located near a
heat source. Make sure the
enclosure has enough
ventilation and that the
room temperature is not
too hot or too cold. See the
enclosure documentation
for more diagnostic
information.
2114

110

A consistency OK / Normal /
check on a
Informational
virtual disk
has been
paused
(suspend-ed)

Cause: The check
consistency operation on
a virtual disk was paused
by a user.

Related Alert
Information
Clear Alert
Number:
None.
Related Alert
Number:
None.

Clear Alert
Number:
2115.

Related Alert
Action: To resume the
Number:
check consistency
None.
operation, right-click the
virtual disk in the tree view
and select Resume Check
Consistency.

Storage Management Message Reference

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2115

A consistency OK / Normal /
check on a
Informational
virtual disk
has been
resumed

Severity

Cause and Action

Related Alert
Information

Cause: The check
consistency operation on a
virtual disk has resumed
processing after being
paused by a user. This alert
is for informational
purposes.

Clear Alert
Status: Alert
2115 is a clear
alert for alert
2114.

Action: None
2116

A virtual disk OK / Normal /
and its mirror Informational
have been
split

Cause: A user has caused a
mirrored virtual disk to be
split. When a virtual disk is
mirrored, its data is copied
to another virtual disk in
order to maintain
redundancy. After being
split, both virtual disks
retain a copy of the data,
although because the
mirror is no longer intact,
updates to the data are no
longer copied to the mirror.
This alert is for
informational purposes.

Related Alert
Number:
None.
Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: None

Storage Management Message Reference

111

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

Severity

2117

A mirrored
virtual disk
has been
unmirrored

OK / Normal / Cause: A user has caused a
Informational mirrored virtual disk to be
unmirrored. When a
virtual disk is mirrored, its
data is copied to another
virtual disk in order to
maintain redundancy. After
being unmirrored, the disk
formerly used as the mirror
returns to being a physical
disk and becomes available
for inclusion in another
virtual disk. This alert is for
informational purposes.

Cause and Action

Related Alert
Information
Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: None
2118

Change write OK / Normal / Cause: A user has changed
policy
Informational the write policy for a
virtual disk. This alert is for
informational purposes.
Action: None

2120

Enclosure
firmware
mismatch

Warning /
Non-critical

Cause: The firmware on
the EMM is not the same
version. It is required that
both modules have the
same version of the
firmware. This alert may be
caused when a user
attempts to insert an EMM
module that has a different
firmware version than an
existing module.
Action: Download the
same version of the
firmware to both EMM
modules.

112

Storage Management Message Reference

Clear Alert
Number:
None.
Related Alert
Number:
None.
Clear Alert
Number:
None.
Related Alert
Number:
None.

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

Severity

2121

Device
returned to
normal

OK / Normal / Cause: A device that was
Informational previously in an error state
has returned to a normal
state. For example, if an
enclosure became too hot
and subsequently cooled
down, then you may
receive this alert. This alert
is for informational
purposes.

Cause and Action

Related Alert
Information
Clear Alert
Status: Alert
2121 is a clear
alert for alert
2048.
Related Alert
Number:
2050, 2065,
2158

Action: None
2122

Redund-ancy Warning /
degraded
Non-critical

Cause: One or more of the Clear Alert
enclosure components has Status: 2124.
failed.
Related Alert
For example, a fan or power Number:
supply may have failed.
2048
Although the enclosure is
currently operational, the
failure of additional
components could cause
the enclosure to fail.
Action: Identify and replace
the failed component. To
identify the failed
component, select the
enclosure in the tree view
and click the Health
subtab. Any failed
component will be
identified with a red "X" on
the enclosure’s Health
subtab. Alternatively, you
can select the Storage
object and click the
Health subtab.

Storage Management Message Reference

113

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

Severity

2122

Cause and Action

Related Alert
Information

The controller status
displayed on the Health
subtab indicates whether
a controller has a failed or
degraded component.

contd.

See the enclosure
documentation for
information on replacing
enclosure components and
for other diagnostic
information.
2123

Redundancy
lost

Warning /
Non-critical

Cause: A virtual disk or an
enclosure has lost data
redundancy. In the case of
a virtual disk, one or more
physical disks included in
the virtual disk have failed.
Due to the failed physical
disk or disks, the virtual
disk is no longer
maintaining redundant
(mirrored or parity) data.
The failure of an additional
physical disk will result in
lost data. In the case of an
enclosure, more than one
enclosure component has
failed. For example, the
enclosure may have
suffered the loss of all fans
or all power supplies.
Action: Identify and
replace the failed
components. To identify the
failed component, select
the Storage object and
click the Health subtab.

114

Storage Management Message Reference

Clear Alert
Number:
2124.
Related Alert
Number:
2048, 2049,
2057

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2123
contd.

Severity

Cause and Action

Related Alert
Information

The controller status
displayed on the Health
subtab indicates whether a
controller has a failed or
degraded component.
Click the controller that
displays a Warning or
Failed status. This action
displays the controller
Health subtab which
displays the status of the
individual controller
components. Continue
clicking the components
with a Warning or Health
status until you identify
the failed component.
See the online help for
more information. See the
enclosure documentation
for information on
replacing enclosure
components and for other
diagnostic information.

2124

Redund-ancy OK / Normal / Cause: Data redundancy
normal
Informational has been restored to a
virtual disk or an enclosure
that previously suffered a
loss of redundancy. This
alert is for informational
purposes.
Action: None

Clear Alert
Number:
Alert 2124 is a
clear alert for
alerts 2122
and 2123.
Related Alert
Number:
None.

Storage Management Message Reference

115

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2125

2126

Severity

Cause and Action

Related Alert
Information

Controller
Warning /
cache
Non-critical
preserved for
missing or
offline virtual
disk

Cause: Virtual disk
controller was
disconnected, during IO
operation.

Clear Alert
Number: No

SCSI sense
sector
reassign

Cause: A sector of the
physical disk is corrupted
and data cannot be
maintained on this portion
of the disk. This alert is for
informational purposes.

Warning /
Non-critical

Action: Import foreign
disks, if any. Check if the
enclosure containing the
virtual disk is disconnected
from the controller.

CAUTION: Any data
residing on the
corrupt portion of the
disk may be lost and
you may need to
restore your data from
backup.
Action: If the physical disk
is part of a non-redundant
virtual disk, then back up
the data and replace the
physical disk.

CAUTION: Removing
a physical disk that is
included in a nonredundant virtual disk
will cause the virtual
disk to fail and may
cause data loss.

116

Related Alert
Number: No

Storage Management Message Reference

Clear Alert
Number:
None.
Related Alert
Number:
None.

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2126

Severity

Cause and Action

Related Alert
Information

If the disk is part of a
redundant virtual disk,
then any data residing on
the corrupt portion of
the disk will be reallocated
elsewhere in the
virtual disk.

contd.

NOTE: Not
Applicable
for
VMware
ESXi 3.5
Update 4.
2127

Back-ground OK / Normal / Cause: BGI of a virtual disk Clear Alert
initialization Informational has started. This alert is for Status: 2130.
(BGI) started
informational purposes.
Related Alert
Action: None
Number:
None.

2128

BGI cancelled OK / Normal / Cause: BGI of a virtual disk
Informational has been cancelled. A user
or the firmware may have
stopped BGI.
Action: None

2129

BGI failed

Clear Alert
Number:
None.
Related Alert
Number:
None.

Critical /
Cause: BGI of a virtual disk Clear Alert
Failure / Error has failed.
Number:
None.
Action: None
Related Alert
Number:
2340

Storage Management Message Reference

117

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

Severity

2130

BGI
completed

OK / Normal / Cause: BGI of a virtual disk Clear Alert
Informational has completed. This alert is Number:
for informational purposes. Alert 2130 is a
clear alert for
Action: None
alert 2127.

Cause and Action

Related Alert
Information

Related Alert
Number:
None.
2131

Firmware
version
mismatch

Warning /
Non-critical

Cause: The firmware on
the controller is not a
supported version.

Clear Alert
Number:
None.

Action: Install a supported Related Alert
version of the firmware. If Number:
you do not have a
None.
supported version of the
firmware available, you can
download it from the Dell
Support site at
support.dell.com or you
can check with your
support provider for
information on how to
obtain the most current
firmware.

118

Storage Management Message Reference

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2132

Driver version Warning /
mismatch
Non-critical

Severity

Cause and Action

Related Alert
Information

Cause: The controller
driver is not a supported
version.

Clear Alert
Number:
None.

Action: Install a supported Related Alert
version of the driver.. If you Number:
do not have a supported
None.
driver version available,
you can download it from
the Dell Support site at
support.dell.com or you
can check with your
support provider for
information on how to
obtain the most current
driver.
2135

Array
Manager is
installed on
the system

NOTE: Not
supported
with Dell
OpenManage
Server
Administrator
version 6.0.1.

2136

Virtual disk
initialization

Warning /
Non-critical

Cause: Storage
Management has been
installed on a system that
has an Array Manager
installation.
Action: Installing Storage
Management and Array
Manager on the same
system is not a supported
configuration. Uninstall
either Storage
Management or Array
Manager.

OK / Normal / Cause: Virtual disk
Informational initialization is in progress.
This alert is for
informational purposes.
Action: None

Clear Alert
Number:
None.
Related Alert
Number:
None.

Clear Alert
Number:
2088.
Related Alert
Number:
None.

Storage Management Message Reference

119

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2137

Comm-unica- Warning /
tion
Non-critical
timeout

Severity

Cause and Action

Related Alert
Information

Cause: The controller is
unable to communicate
with an enclosure.
There are several reasons
why communication may
be lost. For example, there
may be a bad or loose
cable. An unusual amount
of I/O may also interrupt
communication with the
enclosure. In addition,
communication loss may
be caused by software,
hardware, or firmware
problems, bad or failed
power supplies, and
enclosure shutdown.

Clear Alert
Number:
2162.

When viewed in the Alert
Log, the description for this
event displays several
variables. These variables
are: controller and enclosure
names, type of
communication problem,
return code, and
SCSI status.

120

Storage Management Message Reference

Related Alert
Number:
None.

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2137

Cause and Action

Enclosure
OK / Normal / Cause: A user has enabled
alarm enabled Informational the enclosure alarm. This
alert is for informational
purposes.
Action: None

2139

Related Alert
Information

Action: Check for
problems with the cables.
See the online help for
more information on
checking the cables.
You should also check to
see if the enclosure has
degraded or failed
components. To do so,
select the enclosure object
in the tree view and click
the Health subtab. The
Health subtab displays the
status of the enclosure
components. Verify that
the controller has
supported driver and
firmware versions installed
and that the EMMs are
each running the same
version of supported
firmware.

contd.

2138

Severity

Enclosure
alarm
disabled

Clear Alert
Number:
None.
Related Alert
Number:
None.

OK / Normal / Cause: A user has disabled Clear Alert
Informational the enclosure alarm.
Number:
None.
Action: None
Related Alert
Number:
None.

Storage Management Message Reference

121

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

Severity

2140

Dead disk
segments
restored

OK / Normal / Cause: Disk space that was
Informational formerly “dead” or
inaccessible to a redundant
virtual disk has been
restored. This alert is for
informational purposes.

Cause and Action

Related Alert
Information
Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: None
2141

Physical disk
dead
segments
recovered

OK / Normal / Cause: Portions of the
Informational physical disk were formerly
inaccessible. The disk
space from these dead
segments has been
recovered and is now
usable. Any data residing
on these dead segments
has been lost. This alert is
for informational purposes.

Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: None
2142

Controller
rebuild rate
has changed

OK / Normal / Cause: A user has changed
Informational the controller rebuild rate.
This alert is for
informational purposes.
Action: None

2143

Controller
OK / Normal / Cause: A user has enabled
alarm enabled Informational the controller alarm. This
alert is for informational
purposes.
Action: None

122

Storage Management Message Reference

Clear Alert
Number:
None.
Related Alert
Number:
None.
Clear Alert
Number:
None.
Related Alert
Number:
None.

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

Severity

2144

Controller
alarm
disabled

OK / Normal / Cause: A user has disabled
Informational the controller alarm.
This alert is for
informational purposes.

Cause and Action

Action: None
2145

Controller
battery low

Warning /
Non-critical

Cause: The controller
battery charge is low.

Related Alert
Information
Clear Alert
Number:
None.
Related Alert
Number:
None.
Clear Alert
Number:
None.

Action: Recondition the
battery. See the online help Related Alert
for more information.
Number:
None.
2146

2147

2148

Bad block
Warning /
replace-ment Non-critical
error

Bad block
sense
error

Warning /
Non-critical

Cause: A portion of a
physical disk is damaged.
Action: See the Dell
OpenManage Server
Administrator Storage
Management online help
for more information.
Cause: A portion of a
physical disk is damaged.
Action: See the Dell
OpenManage Server
Administrator Storage
Management online help
for more information.

Bad block
Warning /
medium error Non-critical

Cause: A portion of a
physical disk is damaged.
Action: See the Dell
OpenManage Server
Administrator Storage
Management online help
for more information.

Clear Alert
Number:
None.
Related Alert
Number:
None.
Clear Alert
Number:
None.
Related Alert
Number:
None.
Clear Alert
Number:
None.
Related Alert
Number:
None.

Storage Management Message Reference

123

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

Severity

Cause and Action

Related Alert
Information

2149

Bad block
extended
sense error

Warning /
Non-critical

Cause: A portion of a
physical disk is damaged.

Clear Alert
Number:
None.

2150

2151

Action: See the Dell
OpenManage Server
Administrator Storage
Management online help
for more information.

Bad block
Warning /
extended
Non-critical
medium error

Enclosure
asset tag
changed

Cause: A portion of a
physical disk is damaged.
Action: See the Dell
OpenManage Server
Administrator Storage
Management online help
for more information.

OK / Normal / Cause: A user has changed
Informational the enclosure asset tag.
This alert is for
informational purposes.
Action: None

2152

Enclosure
asset name
changed

OK / Normal / Cause: A user has changed
Informational the enclosure asset name.
This alert is for
informational purposes.
Action: None

124

Storage Management Message Reference

Related Alert
Number:
None.
Clear Alert
Number:
None.
Related Alert
Number:
None.
Clear Alert
Number:
None.
Related Alert
Number:
None.
Clear Alert
Number:
None.
Related Alert
Number:
None.

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

Severity

2153

Service tag
changed

OK / Normal / Cause: An enclosure
Informational service tag was changed.
In most circumstances,
this service tag should only
be changed by Dell support
or your service provider.

Cause and Action

Related Alert
Information
Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: Ensure that the tag
was changed under
authorized circumstances.
2154

2155

2156

Maximum
OK / Normal /
temp-erature Informational
probe
warning
threshold
value
changed

Cause: A user has changed
the value for the maximum
temperature probe warning
threshold. This alert is for
informational purposes.

Minimum
OK / Normal /
temp-erature Informational
probe
warning
threshold
value
changed

Cause: A user has changed
the value for the minimum
temperature probe warning
threshold. This alert is for
informational purposes.

Controller
alarm has
been tested

Action: None

OK / Normal / Cause: The controller
Informational alarm test has run
successfully. This alert is for
informational purposes.
Action: None

Clear Alert
Number:
None.
Related Alert
Number:
None.
Clear Alert
Number:
None.
Related Alert
Number:
None.
Clear Alert
Number:
None.
Related Alert
Number:
None.

Storage Management Message Reference

125

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

Severity

2157

Controller
configuration has
been reset

OK / Normal / Cause: A user has reset the
Informational controller configuration.
See the online help for
more information.
This alert is for
informational purposes.

Cause and Action

Related Alert
Information
Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: None
2158

Physical disk
online

OK / Normal / Cause: An offline physical
Informational disk has been made online.
This alert is for
informational purposes.
Action: None

Clear Alert
Status: Alert
2158 is a clear
alert for alert
2050.
Related Alert
Number:
2048, 2050,
2065, 2099,
2121, 2196,
2201, 2203

2159

Virtual disk
renamed

OK / Normal / Cause: A user has renamed Clear Alert
Informational a virtual disk.
Number:
None.
On the PERC 5/E,
PERC 5/i or SAS 5/iR
controller, this alert
displays the new virtual
disk name.
This alert is for
informational purposes.
Action: None

126

Storage Management Message Reference

Related Alert
Number:
None.

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

Severity

2162

Communication
regained

OK / Normal / Cause: Communication
Informational with an enclosure has been
restored. This alert is for
informational purposes.

Cause and Action

Action: None

Related Alert
Information
Clear Alert
Status: Alert
2162 is a clear
alert for alerts
2137 and
2292.
Related Alert
Number:
None.

2163

Rebuild
completed
with errors

Critical /
Cause: You might be
Failure / Error attempting a RAID
configuration that is not
supported by the
controller..
Action: See the Storage
Management online help
for more information.

2164

See the
Readme file
for a list of
validated
controller
driver
versions

OK / Normal / Cause: Storage
Informational Management is unable to
determine whether the
system has the minimum
required versions of the
RAID controller drivers.
This alert is for
informational purposes.

Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: See the Readme
file for driver and firmware
requirements. In particular,
if Storage Management
experiences performance
problems, you should verify
that you have the
minimum supported
versions of the drivers and
firmware installed.

Storage Management Message Reference

127

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2165

The RAID
Warning /
controller
Non-critical
firmware and
driver
validation was
not
performed.
The configuration file
cannot be
opened.

Severity

Cause and Action

Related Alert
Information

Cause: Storage
Management is unable to
determine whether the
system has the minimum
required versions of the
RAID controller firmware
and drivers. This situation
may occur for a variety of
reasons. For example,
the installation directory
path to the configuration
file may not be correct.
The configuration file may
also have been removed or
renamed.

Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: Reinstall Storage
Management
2166

The RAID
Warning /
controller
Non-critical
firmware and
driver
validation
was not
performed.
The configuration file is
out of date or
corrupted.

Cause: Storage
Management is unable to
determine whether the
system has the minimum
required versions of the
RAID controller firmware
and drivers. This situation
has occurred because a
configuration file is
unreadable or missing data.
The configuration file may
be corrupted.
Action: Reinstall Storage
Management.

128

Storage Management Message Reference

Clear Alert
Number:
None.
Related Alert
Number:
None.

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2167

The current Warning /
kernel version Non-critical
and the nonRAID SCSI
driver version
are older than
the minimum
required
levels. See
readme.txt
for a list of
validated
kernel and
driver
versions.

NOTE: Not
Applicable for
VMware ESXi
3.5 Update 4.

Severity

Cause and Action

Related Alert
Information

Cause: The version of the
kernel and the driver do not
meet the minimum
requirements. Storage
Management may not be
able to display the storage
or perform storage
management functions
until you have updated the
system to meet the
minimum requirements.

Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: See the Readme
file for a list of validated
kernel and driver versions.
Update the system to meet
the minimum
requirements and then
reinstall Storage
Management.

Storage Management Message Reference

129

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2168

The nonWarning /
RAID SCSI Non-critical
driver version
is older than
the minimum
required
level. See
readme.txt
for the
validated
driver version.

NOTE: Not
Applicable for
VMware ESXi
3.5 Update 4.

2169

Severity

Cause and Action

Related Alert
Information

Cause: The version of the
driver does not meet the
minimum requirements.
Storage Management may
not be able to display the
storage or perform storage
management functions
until you have updated the
system to meet the
minimum requirements.

Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: See the Readme
file for the validated driver
version. Update the system
to meet the minimum
requirements and then
reinstall Storage
Management.

The
Critical /
Cause: The controller
controller
Failure / Error battery cannot recharge.
battery needs
The battery may be old or
to be
it may have been already
replaced.
recharged the maximum
number of times.
In addition, the battery
charger may not be
working.

Clear Alert
Number:
None.
Related Alert
Number:
2118

Action: Replace the battery
pack.
2170

130

The
OK / Normal / Cause: This alert is for
controller
Informational informational purposes.
battery charge
Action: None
level is
normal.

Storage Management Message Reference

Clear Alert
Number:
None.
Related Alert
Number:
None.

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2171

The
Warning /
controller
Non-critical
battery temperature is
above normal.

Severity

Cause and Action

Related Alert
Information

Cause: The battery may
be recharging, the room
temperature may be too
hot, or the fan in the
system may be degraded
or failed.

Clear Alert
Number:
2172.
Related Alert
Number:
None.

Action: If this alert was
generated due to a battery
recharge, the situation will
correct when the recharge
is complete. You should
also check if the room
temperature is normal and
that the system
components are
functioning properly.
2172

The
OK / Normal / Cause: This alert is for
controller
Informational informational purposes.
battery tempAction: None
erature is
normal.

Clear Alert
Status: Alert
2172 is a clear
alert for alert
2171.
Related Alert
Number:
None.

Storage Management Message Reference

131

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2173

Un-supported Warning /
configNon-critical
uration
detected. The
SCSI rate of
the enclosure
man-agement
modules
(EMMs) is
not the same.
EMM0 %1
EMM1 %2.

Severity

Cause and Action

Related Alert
Information

Cause: The EMMs in the
enclosure have a different
SCSI rate. This is an
unsupported configuration.
All EMMs in the enclosure
should have the same SCSI
rate. The % (percent sign)
indicates a substitution
variable. The text for this
substitution variable is
displayed with the alert in
the Alert Log and can vary
depending on the
situation.

Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: No action required.
2174

The
controller
battery has
been
removed.

Warning /
Non-critical

Cause: The controller
cannot communicate with
the battery, the battery may
be removed, or the contact
point between the
controller and the battery
may be burnt or corroded.
Action: Replace the battery
if it has been removed. If
the contact point between
the battery and the
controller is burnt or
corroded, you will need to
replace either the battery
or the controller, or both.
See the hardware
documentation for
information on how to
safely access, remove, and
replace the battery.

132

Storage Management Message Reference

Clear Alert
Number:
None.
Related Alert
Number:
2188, 2318

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

Severity

2175

The
controller
battery has
been
replaced.

OK / Normal / Cause: This alert is for
Informational informational purposes.

2176

2177

Cause and Action

Action: None

Related Alert
Information
Clear Alert
Number:
None.
Related Alert
Number:
None.

The
OK / Normal / Cause: This alert is for
controller
Informational informational purposes.
battery Learn
Action: None
cycle has
started.

Clear Alert
Number:
2177.

The
OK / Normal / Cause: This alert is for
controller
Informational informational purposes.
battery Learn
Action: None
cycle has
completed.

Clear Alert
Status: Alert
2177 is a clear
alert for alert
2176.

Related Alert
Number:
None.

Storage Management Message Reference

133

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2178

The
Warning /
controller
Non-critical
battery Learn
cycle has
timed out.

Severity

Cause and Action

Related Alert
Information

Cause: The controller
battery must be fully
charged before the Learn
cycle can begin. The
battery may be unable to
maintain a full charge
causing the Learn cycle
to timeout. Additionally,
the battery must be able to
maintain cached data for a
specified period of time in
the event of a power loss.
For example, some
batteries maintain cached
data for 24 hours. If the
battery is unable to
maintain cached data for
the required period of
time, then the Learn cycle
will timeout.

Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: Replace the battery
pack as the battery is
unable to maintain a full
charge.
2179

134

The
OK / Normal / Cause: This alert is for
controller
Informational informational purposes.
battery Learn
Action: None
cycle has
been
postponed.

Storage Management Message Reference

Clear Alert
Number:
None.
Related Alert
Number:
None.

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2180

The
OK / Normal /
controller
Informational
battery Learn
cycle will start
in %1 days.

Severity

Cause and Action

Related Alert
Information

Cause: This alert is for
informational purposes.
The %1 indicates a
substitution variable.
The text for this
substitution variable is
displayed with the alert in
the Alert Log and can vary
depending on the
situation.

Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: None
2181

The
OK / Normal /
controller
Informational
battery Learn
cycle will start
in %1 hours.

Cause: The %1 indicates a
substitution variable.
The text for this
substitution variable is
displayed with the alert in
the Alert Log and can vary
depending on the
situation. This alert is for
informational purposes.

Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: None
2182

2183

An invalid
SAS configuration has
been
detected.

Critical /
Cause: The controller and Clear Alert
Failure / Error attached enclosures are not Number:
cabled correctly.
None.

Replace
member
operation
failed on
physical
disk %1

Critical /
Cause: The physical disk
Failure / Error being replaced has failed.

Action: See the hardware
documentation for
information on correct
cabling configurations.

Action: None

Related Alert
Number:
None.
Clear Alert
Number:
None.
Related Alert
Number:
2060.

Storage Management Message Reference

135

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

Severity

2184

Replace
member
operation
cancelled on
physical disk

OK / Normal / Cause: User cancelled the Clear Alert
Informational replace member operation. Number:
None
Action: None

2185

2186

Cause and Action

Related Alert
Information

Related Alert
Number:
2060

Replace
Warning/
member
Non-critical
operation
stopped for
rebuild of hot
spare on
physical disk

Cause: This alert is
Clear Alert
provided for informational Number:
purposes
None
Action: None

Related Alert
Number:
2060

The
controller
cache has
been
discarded.

Cause: The controller has
flushed the cache and any
data in the cache has been
lost. This may happen if
the system has memory or
battery problems that
cause the controller to
distrust the cache. Although
user data may have been
lost, this alert does not
always indicate that relevant
or user data has been lost.

Clear Alert
Number:
None.

Warning /
Non-critical

Related Alert
Number:
None.

Action: Verify that the
battery and memory are
functioning properly.
2187

136

Single-bit
ECC error
limit
exceeded.

Warning /
Non-critical

Clear Alert
Cause: The system
memory is malfunctioning. Number:
None.
Action: Replace the
battery pack.

Storage Management Message Reference

Related Alert
Number:
None.

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

Severity

2188

The
controller
write policy
has been
changed to
Write
Through.

OK / Normal / Cause: The controller
Informational battery is unable to
maintain cached data for
the required period of
time. For example, if the
required period of time is
24 hours, the battery is
unable to maintain cached
data for 24 hours. It is
normal to receive this alert
during the battery Learn
cycle as the Learn cycle
discharges the battery
before recharging it.
When discharged,
the battery cannot
maintain cached data.

Cause and Action

Related Alert
Information
Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: Check the health
of the battery. If the battery
is weak, replace the battery
pack.
2189

2190

The
controller
write policy
has been
changed to
Write Back.

OK / Normal / Cause: This alert is for
Informational informational purposes.
Action: None

Clear Alert
Number:
None.
Related Alert
Number:
None.

The
OK / Normal /
controller has Informational
detected a
hot-plugged
enclosure.

Cause: The SAS controller
with firware version 6.1 or
later has detected a
hot-plugged enclosure.
This alert is for
informational purposes.

Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: None

Storage Management Message Reference

137

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2191

Multiple
Critical /
Cause: There are too many
enclosures are Failure / Error enclosures are attached to
attached to
the controller port. When
the controller.
the enclosure limit is
This is an
exceeded, the controller
unsupported
loses contact with all
configenclosures attached to
uration.
the port.

Severity

Cause and Action

Related Alert
Information
Clear Alert
Number:
None.
Related Alert
Number:
2211

Action: Remove the last
enclosure. You must
remove the enclosure that
has been added last and is
causing the enclosure limit
to exceed.
2192

The virtual
disk Check
Consistency
has made
corrections
and
completed.

OK / Normal / Cause: The virtual disk
Informational Check Consistency has
identified errors and made
corrections. For example,
the Check Consistency
may have encountered a
bad disk block and
remapped the disk block to
restore data consistency.
This alert is for
informational purposes.
Action: This alert is for
informational purposes
only and no additional
action is required. As a
precaution, monitor the
Alert Log for other errors
related to this virtual disk.
If problems persist, contact
Dell Technical Support.

138

Storage Management Message Reference

Clear Alert
Number:
None.
Related Alert
Number:
None.

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2193

The virtual
OK / Normal / Cause: This alert is for
disk reconfig- Informational informational purposes.
uration has
Action: None
resumed.

Clear Alert
Number:
None.

The virtual
disk Read
policy has
changed.

OK / Normal / Cause: This alert is for
Informational informational purposes.

Clear Alert
Number:
None.

Dedicated
hot spare
assigned.
Physical disk
%1

OK / Normal / Cause: This alert is for
Informational informational purposes.

Dedicated
hot spare
unassigned.
Physical disk
%1

OK / Normal / Cause: This alert is for
Informational informational purposes.

2194

2195

2196

Severity

Cause and Action

Action: None

Related Alert
Information

Related Alert
Number:
None.

Action: None.

Clear Alert
Number:
2196.
Related Alert
Number:
None.

Action: None.

Clear Alert
Status: Alert
2196 is a clear
alert for alert
2195.
Related Alert
Number:
None.

2197

OK / Normal /
Replace
member
Informational
operation has
stopped for
rebuild.

Cause: This alert is
Clear Alert
provided for informational Number:
purposes.
None
Action: None

Related Alert
Number: 260.

Storage Management Message Reference

139

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

Severity

2198

The physical
disk is too
small to be
used for
Replace
member
operation

OK / Normal / Cause: Replace member
Informational operation cannot be
performed on the physical
disk as the target disk is
smaller for than the source
disk. This alert is for
informational purposes.

Cause and Action

Related Alert
Information
Clear Alert
Number:
None
Related Alert
Number:
None

Action: None
2199

2200

140

The virtual
disk cache
policy has
changed.

OK / Normal / Cause: This alert is for
Informational informational purposes.

Replace
Warning/
member
Noncritical
operation is
not possible
as combination of
SAS and
SATA
physical disks
is not
supported in
the same
virtual disk.

Action: None

Clear Alert
Number:
None.
Related Alert
Number:
None.

Cause: Replace member
operation cannot be
performed because the
target physical disk is of a
different type (SAS/SATA)
from the rest of the virtual
disk. SAS and SATA are not
supported on the same
virtual disk. This alert is for
informational purposes.
Action: None

Storage Management Message Reference

Clear Alert
Number:
None.
Related Alert
Number:
None.

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

Severity

Cause and Action

Related Alert
Information

2201

A global hot
spare failed.

Warning /
Non-critical

Cause: The controller is
not able to communicate
with a disk that is assigned
as a dedicated hot spare.
The disk may have been
removed. There may also
be a bad or loose cable.

Clear Alert
Number:
None.
Related Alert
Number:
2048

Action: Check if the disk is
healthy and that it has not
been removed. Check the
cables. If necessary, replace
the disk and reassign the
hot spare.
2202

A global hot
spare
has been
removed.

OK / Normal / Cause: The controller is
Informational unable to communicate
with a disk that is assigned
as a global hot spare.
The disk may have been
removed. There may also
be a bad or loose cable.

Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: Check if the disk is
healthy and that it has not
been removed. Check the
cables. If necessary, replace
the disk and reassign the
hot spare.

Storage Management Message Reference

141

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

Severity

Cause and Action

Related Alert
Information

2203

A dedicated
hot spare
failed.

Warning /
Non-critical

Cause: The controller is
unable to communicate
with a disk that is assigned
as a dedicated hot spare.
The disk may have failed or
been removed. There may
also be a bad or loose cable.

Clear Alert
Number:
None.
Related Alert
Number:
2048

Action: Check if the disk is
healthy and that it has not
been removed. Check the
cables. If necessary, replace
the disk and reassign the
hot spare.
2204

A dedicated OK / Normal /
hot spare has Informational
been
removed.

Cause: The controller is
unable to communicate
with a disk that is assigned
as a dedicated hot spare.
The disk may have been
removed. There may also
be a bad or loose cable.

Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: Check if the disk is
healthy and that it has not
been removed. Check the
cables. If necessary,
replace the disk and
reassign the hot spare.
2205

142

A dedicated OK / Normal /
hot spare has Informational
been automatically
unassigned.

Cause: The hot spare is no
longer required because the
virtual disk it was assigned
to has been deleted.
Action: None.

Storage Management Message Reference

Clear Alert
Number:
None.
Related Alert
Number:
2098, 2161,
2196

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2206

The only hot Warning /
spare
Non-critical
available is a
SATA disk.
SATA disks
cannot
replace
SAS disks.

Severity

Cause and Action

Related Alert
Information

Cause: The only physical
disk available to be assigned
as a hot spare is using
SATA technology.
The physical disks in the
virtual disk are using SAS
technology. Because of this
difference in technology,
the hot spare cannot
rebuild data if one of the
physical disks in the virtual
disk fails.

Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: Add a SAS disk
that is large enough to be
used as the hot spare and
assign the new disk as a hot
spare.
2207

The only hot Warning /
spare available Non-critical
is a SAS disk.
SAS disks
cannot
replace SATA
disks.

Cause: The only physical
disk available to be
assigned as a hot spare is
using SAS technology.
The physical disks in the
virtual disk are using SATA
technology. Because of this
difference in technology,
the hot spare cannot
rebuild data if one of the
physical disks in the virtual
disk fails.

Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: Add a SATA disk
that is large enough to be
used as the hot spare and
assign the new disk as a hot
spare.

Storage Management Message Reference

143

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

Severity

Cause and Action

2210

Battery
requires
reconditioning. Initiate
the battery
learn cycle.

Warning /
Non-critical

Cause: Battery requires
reconditioning.

2211

The physical
disk is not
supported.

Warning /
Non-critical

Cause: The physical disk
may not have a supported
version of the firmware or
the disk may not be
supported by Dell.

Clear Alert
Number:
Action: Initiate the battery None.
learn cycle.
Related Alert
Number:
None.

Action: If the disk is
supported by Dell,
update the firmware to a
supported version. If the
disk is not supported by
Dell, replace the disk with
one that is supported.
2212

2213

Clear Alert
Number:
None.
Related Alert
Number:
None.

The
OK / Normal / Cause: This alert is for
controller
Informational informational purposes.
battery tempAction: None
erature is
above normal.

Clear Alert
Number:
None.

Recharge
count
maximum
exceeded

Clear Alert
Number:
None.

Warning /
Non-critical

Cause: The battery has
been recharged more times
than the battery recharge
limit allows.
Action: Replace the
battery pack.

144

Related Alert
Information

Storage Management Message Reference

Related Alert
Number:
None.

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

Severity

2214

Battery
charge in
progress

OK / Normal / Cause: This alert is for
Informational informational purposes.

Cause and Action

Action: None.

Related Alert
Information
Clear Alert
Number:
None.
Related Alert
Number:
None.

2215

2216

2217

2218

Battery
charge
process
interrupted

OK / Normal / Cause: This alert is for
Informational informational purposes.

The battery
learn mode
has changed
to auto.

OK / Normal / Cause: This alert is for
Informational informational purposes.

The battery
learn mode
has changed
to warn.

OK / Normal / Cause: This alert is for
Informational informational purposes.

None of the
Controller
Property are
changed.

OK / Normal / Cause: This alert is for
Informational informational purposes.

Action: None.

Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: None

Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: None

Clear Alert
Number:
None.
Related Alert
Number:
None.

Clear Alert
Number:
Action: You should change None.
Related Alert
at least one controller
Number:
property and run the
None.
command again.

Storage Management Message Reference

145

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2219

Abort Check OK / Normal / Cause: This alert is for
Consistency Informational informational purposes.
on Error,
Action: None
Allow
Revertible
Hot Spare
and Replace
Member,
Auto Replace
Member on
Predictive
Failure, and
Load balance
changed.

Clear Alert
Number:
None.

Allow
OK / Normal / Cause: This alert is for
Revertible
Informational informational purposes.
Hot Spare
Action: None
and Replace
Member,
Auto Replace
Member
operation on
Predictive
Failure, and
Load balance
changed.

Clear Alert
Number:
None.

Auto Replace OK / Normal / Cause: This alert is for
Member
Informational informational purposes.
operation on
Action: None
Predictive
Failure, Abort
Check
Consistency
on Error, and
Load balance
changed.

Clear Alert
Number:
None.

2220

2221

146

Severity

Cause and Action

Storage Management Message Reference

Related Alert
Information

Related Alert
Number:
None.

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2222

2223

2224

2225

Severity

Cause and Action

Related Alert
Information

Load balance OK / Normal /
and Auto
Informational
Replace
Member
operation on
Predictive
Failure
changed.

Cause: This alert is
generated due to user
initiated change in
controller properties.
This alert is for
informational purposes.

Clear Alert
Number:
None.

Abort Check OK / Normal /
Consistency Informational
on Error,
Allow
Revertible
Hot Spare
and Replace
Member, and
Load balance
changed.

Cause: This alert is
generated due to user
initiated change in
controller properties.
This alert is for
informational purposes.

Allow
OK / Normal /
Revertible
Informational
Hot Spare
and Replace
Member and
Load balance
changed.

Cause: This alert is
generated due to user
initiated change in
controller properties.
This alert is for
informational purposes.

Abort Check OK / Normal /
Consistency Informational
on Error and
Load balance
changed.

Cause: This alert is
generated due to user
initiated change in
controller properties.
This alert is for
informational purposes.

Related Alert
Number:
None.

Action: None
Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: None

Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: None
Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: None

Storage Management Message Reference

147

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2226

Load balance OK / Normal / Cause: This alert is for
changed
Informational informational purposes.

Severity

Cause and Action

Action: None

Related Alert
Information
Clear Alert
Number:
None.
Related Alert
Number:
None.

2227

2228

148

Abort Check OK / Normal /
Consistency Informational
on Error,
Allow
Revertible
Hot Spare
and Replace
Member, and
Auto Replace
Member
Operation on
Predictive
Failure
changed.

Cause: This alert is
generated due to user
initiated change in
controller properties.
This alert is for
informational purposes.

Allow
OK / Normal /
Revertible
Informational
Hot Spare
and Replace
Member and
Auto Replace
Member
operation on
Predictive
Failure
changed.

Cause: This alert is
generated due to user
initiated change in
controller properties.
This alert is for
informational purposes.

Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: None

Storage Management Message Reference

Clear Alert
Number:
None.
Related Alert
Number:
None.

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2229

Abort Check OK / Normal /
Consistency Informational
on Error and
Auto Replace
Member
operation on
Predictive
Failure
changed.

2230

2231

2232

Severity

Cause and Action

Related Alert
Information

Cause: This alert is
generated due to user
initiated change in
controller properties.
This alert is for
informational purposes.

Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: None

Auto Replace OK / Normal / Cause: This alert is for
Member
Informational informational purposes.
operation on
Action: None
Predictive
Failure
changed.

Clear Alert
Number:
None.

Allow
OK / Normal / Cause: This alert is for
Revertible
Informational informational purposes.
Hot Spare
Action: None
and Replace
Member and
Abort Check
Consistency
on Error
changed.

Clear Alert
Number:
None.

The
controller
alarm is
silenced.

Clear Alert
Number:
None.

OK / Normal / Cause: This alert is for
Informational informational purposes.
Action: None

Related Alert
Number:
None.

Storage Management Message Reference

149

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2233

The BackOK / Normal / Cause: This alert is for
ground
Informational informational purposes.
initialization
Action: None
(BGI) rate
has changed.

Clear Alert
Number:
None.

The Patrol
OK / Normal / Cause: This alert is for
Read rate has Informational informational purposes.
changed.
Action: None

Clear Alert
Number:
None.

2234

Severity

Cause and Action

Related Alert
Information

Related Alert
Number:
None.

Related Alert
Number:
None.
2235

2236

2237

150

The Check
Consistency
rate has
changed.

OK / Normal / Cause: This alert is for
Informational informational purposes.

Allow
Revertible
Hot Spare
and Replace
Member
property
changed.

OK / Normal / Cause: This alert is for
Informational informational purposes.

Action: None

Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: None

Abort Check OK / Normal / Cause: This alert is for
Consistency Informational informational purposes.
on Error
Action: None
modified.

Storage Management Message Reference

Clear Alert
Number:
None.
Related Alert
Number:
None.
Clear Alert
Number:
None.
Related Alert
Number:
None.

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2238

The
OK / Normal /
controller
Informational
debug log file
has been
exported.

Severity

Cause and Action

Related Alert
Information

Cause: The user has
attempted to export the
controller debug log.
This alert is for
informational purposes.

Clear Alert
Number:
None.

Action: None
2239

A foreign
OK / Normal /
configInformational
uration has
been cleared.

Cause: The user has
attempted to clear a
foreign configuration.
This alert is for
informational purposes.
Action: None

2240

A foreign
OK / Normal /
configuration Informational
has been
imported.

Cause: The user has
attempted to import a
foreign configuration.
This alert is for
informational purposes.
Action: None

2241

The Patrol
OK / Normal / Cause: The controller has
Read mode
Informational changed the petrol read
has changed.
mode. This alert is for
informational purposes.
Action: None

2242

The Patrol
Read has
started.

OK / Normal / Cause: The controller has
Informational started the Petrol Read
operation. This alert is for
informational purposes.
Action: None

Related Alert
Number:
None.
Clear Alert
Number:
None.
Related Alert
Number:
None.
Clear Alert
Number:
None.
Related Alert
Number:
None.
Clear Alert
Number:
None.
Related Alert
Number:
None.
Clear Alert
Number:
2243.
Related Alert
Number:
None.

Storage Management Message Reference

151

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

Severity

2243

The Patrol
Read has
stopped.

OK / Normal / Cause: The controller has
Informational stopped the Petrol Read
operation. This alert is for
informational purposes.

Cause and Action

Action: None

Related Alert
Information
Clear Alert
Status: Alert
2243 is a clear
alert for alert
2242.
Related Alert
Number:
None.

2244

2245

A virtual disk OK / Normal / Cause: This alert is for
blink has
Informational informational purposes.
been
Action: None
initiated.

Clear Alert
Number:
None.

A virtual disk OK / Normal / Cause: This alert is for
blink has
Informational informational purposes.
ceased.
Action: None

Clear Alert
Number:
None.

Related Alert
Number:
None.

Related Alert
Number:
None.
2246

152

The
controller
battery is
degraded.

Warning /
Non-critical

Cause: The controller
battery charge is weak.

Clear Alert
Number:
None.

Action: As the charge
weakens, the charger
Related Alert
should automatically
Number:
recharge the battery. If the None.
battery has reached its
recharge limit, replace the
battery pack. Monitor the
battery to make sure that it
recharges successfully.
If the battery does not
recharge, replace the
battery pack.

Storage Management Message Reference

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

Severity

2247

The
controller
battery is
charging.

OK / Normal / Cause: This alert is for
Informational informational purposes.

The
controller
battery is
executing a
Learn cycle.

OK / Normal / Cause: This alert is for
Informational informational purposes.

2248

2249

2250

Cause and Action

Action: None

Clear Alert
Number:
2358.
Related Alert
Number:
None.

Action: None

Clear Alert
Number:
None.
Related Alert
Number:
None.

The physical OK / Normal / Cause: This alert is for
disk Clear
Informational informational purposes.
operation has
Action: None
started.

Redundant
Warning /
Path is broken Non-critical

Clear Alert
Number:
None.
Related Alert
Number:
None.

Cause: This alert is
Clear Alert
provided for informational Number:
purposes.
2370
Action: Check the
connection to the
enclosure, which is
degraded.

2251

Related Alert
Information

The physical OK / Normal / Cause: This alert is for
disk blink has Informational informational purposes.
initiated.
Action: None

Related Alert
Number:
2370
Clear Alert
Number:
None.
Related Alert
Number:
None.

Storage Management Message Reference

153

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2252

The physical OK / Normal / Cause: This alert is for
disk blink has Informational informational purposes.
ceased.
Action: None

Severity

Cause and Action

Related Alert
Information
Clear Alert
Number:
None.
Related Alert
Number:
None.

2253

Redundant
OK / Normal / Cause: This alert is
Clear Alert
path restored Informational provided for informational Number:
purposes.
None.
Action: None.

2254

The Clear
OK / Normal / Cause: This alert is for
operation has Informational informational purposes.
cancelled.
Action: None

Related Alert
Number:
None.
Clear Alert
Number:
None.
Related Alert
Number:
None.

2255

The physical OK / Normal / Cause: This alert is for
disk has been Informational informational purposes.
started.
Action: None

Clear Alert
Number:
None.
Related Alert
Number:
2048, 2050,
2065, 2099,
2121, 2196,
2201, 2203

2257

Controller
preserved
cache is
discarded

Warning /
Non-critical

Cause: The controller
cache is discarded by the
user. This alert is for
informational purposes.
Action: None

154

Storage Management Message Reference

Clear Alert
Number:
None.
Related Alert
Number:
None.

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2258

Controller
Warning /
has preserved Non-critical
cache

Severity

Cause and Action

Related Alert
Information

Cause: IO interrupted for a
virtual disk which is
connected to the
controller.

Clear Alert
Number:
None.

Related Alert
Action: Check for foreign Number:
configuration and import if None.
any. Check for cable fault.
Recover any virtual disk
lost by the controller.
2259

2260

An enclosure OK / Normal / Cause: This alert is for
blink
Informational informational purposes.
operation has
Action: None
initiated.

Clear Alert
Number:
2260.

An enclosure OK / Normal / Cause: This alert is for
blink has
Informational informational purposes.
ceased
Action: None.

Clear Alert
Number:
None.

Related Alert
Number:
None.

Related Alert
Number:
None.
2261

A global
rescan has
initiated.

OK / Normal / Cause: This alert is for
Informational informational purposes.
Action: None

Clear Alert
Number:
None.
Related Alert
Number:
None.

2262

SMART
thermal
shutdown is
enabled.

OK / Normal / Cause: This alert is for
Informational informational purposes.
Action: None

Clear Alert
Number:
None.
Related Alert
Number:
None.

Storage Management Message Reference

155

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

Severity

2263

SMART
thermal
shutdown is
disabled.

OK / Normal / Cause: This alert is for
Informational informational purposes.

A device is
missing.

Warning /
Non-critical

2264

Cause and Action

Action: None

Related Alert
Information
Clear Alert
Number:
None.
Related Alert
Number:
None.

Cause: The controller
cannot communicate with
a device. The device may
be removed. There may
also be a bad or loose cable.

Clear Alert
Number:
None.

Related Alert
Number:
Action: Check if the device None.
is in and not removed. If it
is in, check the cables.
You should also check the
connection to the
controller battery and the
battery health. A battery
with a weak or depleted
charge may cause this alert.

156

Storage Management Message Reference

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2265

A device is in Warning /
an unknown Non-critical
state.

Severity

Cause and Action

Related Alert
Information

Cause: The controller
cannot communicate with
a device. The state of the
device cannot be
determined. There may
be a bad or loose cable.
The system may also be
experiencing problems
with the application
programming interface
(API). There could also be
a problem with the driver
or firmware.

Clear Alert
Number:
None.
Related Alert
Number:
2048, 2050

Action: Check the cables.
Check if the controller has
a supported version of
the driver and firmware.
You can download the most
current version of the
driver and firmware from
support.dell.com.
Rebooting the system may
also resolve this problem.
2266

Controller log OK / Normal / Cause: The %1 indicates a
file entry: %1 Informational substitution variable.
The text for this
substitution variable is
generated by the controller
and is displayed with the
alert in the Alert Log.
This text can vary
depending on the
situation. This alert is for
informational purposes.

Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: None

Storage Management Message Reference

157

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

Severity

2267

The
controller
reconstruct
rate has
changed.

OK / Normal / Cause: This alert is for
Informational informational purposes.

2268

2269

158

Cause and Action

Action: None

Related Alert
Information
Clear Alert
Number:
None.
Related Alert
Number:
None.

%1, Storage Critical /
Cause: Storage
Management Failure / Error Management has lost
has lost
communication with a
communicacontroller. This may occur
tion with the
if the controller driver or
controller. An
firmware is experiencing a
immediate
problem. The %1 indicates
reboot is
a substitution variable.
strongly
The text for this
recommsubstitution variable is
ended to
displayed with the alert
avoid further
in the Alert Log and can
problems.
vary depending on
If the reboot
the situation.
does not
Action: Reboot the system.
restore
If the problem is not
communicati
resolved, contact technical
on, then
support. See your system
contact
documentation for
technical
information about
support for
contacting technical
more infosupport by using
rmation.
telephone, fax, and
Internet services.

Clear Alert
Number:
None.

The physical OK / Normal / Cause: This alert is for
Informational informational purposes.
disk Clear
operation has
Action: None
completed.

Clear Alert
Number:
None.

Storage Management Message Reference

Related Alert
Number:
None.

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

Severity

2270

The physical
disk Clear
operation
failed.

Critical /
Cause: A Clear task was
Failure / Error being performed on a
physical disk but the task
was interrupted and did
not complete successfully.
The controller may have
lost communication with
the disk. The disk may
have been removed or the
cables may be loose or
defective.

Cause and Action

Related Alert
Information
Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: Verify that the disk
is present and not in a
Failed state. Make sure the
cables are attached
securely. See the online
help for more information
on checking the cables.
Restart the Clear task.
2271

The Patrol
Read
corrected a
media error.

OK / Normal / Cause: The Patrol Read
Informational task has encountered an
error such as a bad disk
block that cannot be
remapped. This alert is for
informational purposes.

Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: None

Storage Management Message Reference

159

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2272

Patrol Read
Critical /
Cause: The Patrol Read
found an un- Failure / Error task has encountered an
correctable
error that cannot be
media error.
corrected. There may be
a bad disk block that
cannot be remapped.

Severity

Cause and Action

Related Alert
Information
Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: Back up your data.
If you are able to back up
the data successfully, then
fully initialize the disk and
then restore from back up.
2273

A block on
Critical /
Cause: The controller
the physical Failure / Error encountered an
disk has been
unrecoverable medium
punctured by
error when attempting to
the controller.
read a block on the physical
disk and marked that block
as invalid. If the controller
encountered the
unrecoverable medium
error on a source physical
disk during a rebuild or
reconfigure operation,
it will also puncture the
corresponding block on
the target physical disk.
The invalid block will
be cleared on a write
operation.
Action: Back up your data.
If you are able to back up
the data successfully, then
fully initialize the disk and
then restore from back up.

160

Storage Management Message Reference

Clear Alert
Number:
None.
Related Alert
Number:
None.

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2274

The physical OK / Normal / Cause: This alert is for
disk rebuild Informational informational purposes.
has resumed.
Action: None

Severity

Cause and Action

Related Alert
Information
Clear Alert
Number:
None.
Related Alert
Number:
None.

2276

2277

The
Warning /
dedicated hot Non-critical
spare is too
small.

Cause: The dedicated hot
spare is not large enough to
protect all virtual disks that
reside on the disk group.

Clear Alert
Number:
None.

The global
hot spare is
too small.

Cause: The global hot spare
is not large enough to
protect all virtual disks that
reside on the controller.

Clear Alert
Number:
None.

Warning /
Non-critical

Related Alert
Action: Assign a larger disk Number:
as the dedicated hot spare. None.

Related Alert
Action: Assign a larger disk Number:
as the global hot spare.
None.

Storage Management Message Reference

161

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2278

The
OK / Normal /
controller
Informational
battery charge
level is below
a normal
threshold.

Severity

Cause and Action

Related Alert
Information

Cause: The battery is
discharging. A battery
discharge is a normal
activity during the battery
Learn cycle. Before
completing, the battery
Learn cycle recharges the
battery. You should receive
alert 2179 when the
recharge occurs.

Clear Alert
Number:
None.
Related Alert
Number:
2199

Action1: Check if the
battery Learn cycle is in
progress. Alert 2176
indicates that the battery
Learn cycle has initiated.
The battery also displays
the Learn state while the
Learn cycle is in progress.
Action2: If a Learn cycle is
not in progress, replace the
battery pack.
2279

162

The
OK / Normal /
controller
Informational
battery charge
level is
operating
within normal
limits.

Cause: This alert indicates
that the battery is
recharging during the
battery Learn cycle.
This alert is provided for
informational purposes.
Action: None

Storage Management Message Reference

Clear Alert
Number:
None.
Related Alert
Number:
None.

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2280

A disk media OK / Normal / Cause: A disk media error
error has been Informational was detected while the
corrected.
controller was completing a
background task. A bad
disk block was identified.
The disk block has been
remapped.

Severity

Cause and Action

Related Alert
Information
Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: Consider replacing
the disk. If you receive this
alert frequently, be sure to
replace the disk. You
should also routinely back
up your data.
2281

Virtual
OK / Normal /
disk has
Informational
in-consistent
data.

Cause: The virtual disk has
inconsistent data. This may
be caused when a power loss
or system shutdown occurs
while data is being written
to the virtual disk. This alert
is for informational
purposes.

Clear Alert
Number:
None.
Related Alert
Number:
2127

Action: None

Storage Management Message Reference

163

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2282

Hot spare
Critical /
Cause: The controller
SMART
Failure / Error firmware attempted a
polling failed.
SMART polling on the hot
spare but was unable to
complete it. The controller
has lost communication
with the hot spare.

Severity

Cause and Action

Related Alert
Information
Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: Check the health
of the disk assigned as a
hot spare. You may need to
replace the disk and
reassign the hot spare.
Make sure the cables are
attached securely. See the
Cables Attached Correctly
section in the
Dell OpenManage Server
Administrator Storage
Management User’s Guide
for more information on
checking the cables.
2285

164

A disk media OK / Normal / Cause: This alert is for
error was
Informational informational purposes.
corrected
Action: None
during
recovery.

Storage Management Message Reference

Clear Alert
Number:
None.
Related Alert
Number:
None.

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2286

A Learn cycle OK / Normal / Cause: This alert is for
start is
Informational informational purposes.
pending while
Action: None
the battery
charges.

Clear Alert
Number:
None.

The Patrol
Read is
paused.

Clear Alert
Number:
2288.

2287

Severity

Cause and Action

OK / Normal / Cause: This alert is for
Informational informational purposes.
Action: None

Related Alert
Information

Related Alert
Number:
None.

Related Alert
Number:
None.
2288

The patrol
read has
resumed.

OK / Normal / Cause: This alert is for
Informational informational purposes.
Action: None

Clear Alert
Status: Alert
2288 is a clear
alert for alert
2287.
Related Alert
Number:
None.

Storage Management Message Reference

165

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

Severity

2289

Multi-bit
ECC error.

Critical /
Cause: An error involving
Failure / Error multiple bits has been
encountered during a read
or write operation. The
error correction algorithm
recalculates parity data
during read and write
operations. If an error
involves only a single bit, it
may be possible for the
error correction algorithm
to correct the error and
maintain parity data. An
error involving multiple
bits, however, usually
indicates data loss. In some
cases, if the multi-bit error
occurs during a read
operation, the data on the
disk may be correct/valid. If
the multi-bit error occurs
during a write operation,
data loss has occurred.

Cause and Action

Action: Replace the dual
in-line memory module
(DIMM). The DIMM is a
part of the controller
battery pack. See your
hardware documentation
for information on
replacing the DIMM. You
may need to restore data
from backup.

166

Storage Management Message Reference

Related Alert
Information
Clear Alert
Number:
None.
Related Alert
Number:
None.

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

Severity

Cause and Action

Related Alert
Information

2290

Single-bit
ECC error.

Warning /
Non-critical

Cause: An error involving a
single bit has been
encountered during a read
or write operation. The
error correction algorithm
has corrected this error.

Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: None
2291

An EMM has OK / Normal / Cause: This alert is for
been
Informational informational purposes.
discovered.
Action: None

Clear Alert
Number:
None.
Related Alert
Number:
None.

2292

2293

CommCritical /
Cause: The controller has
unication
Failure / Error lost communication with an
with the
EMM. The cables may be
enclosure has
loose or defective.
been lost.
Action: Make sure the
cables are attached
securely. Reboot the
system.

Clear Alert
Number:
2162.

The EMM
has failed.

Clear Alert
Number:
None.

Critical /
Cause: The failure may be
Failure / Error caused by a loss of power to
the EMM. The EMM self
test may also have
identified a failure.
There could also be a
firmware problem or a
multi-bit error.

Related Alert
Number:
None.

Action: Replace the EMM.
See the hardware
documentation for
information on replacing
the EMM.

Storage Management Message Reference

167

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2294

A device has OK / Normal / Cause: This alert is for
been inserted. Informational informational purposes.

Severity

Cause and Action

Action: None

Related Alert
Information
Clear Alert
Number:
None.
Related Alert
Number:
None.

2295

A device has
been
removed.

Critical /
Cause: A device has been
Failure / Error removed and the system is
no longer functioning in
optimal condition.

Clear Alert
Number:
None.

Related Alert
Action: Replace the device. Number:
None.

2296

An EMM has OK / Normal / Cause: This alert is for
been inserted. Informational informational purposes.
Action: None

Clear Alert
Number:
None.
Related Alert
Number:
None.

2297

168

An EMM has Critical /
Cause: An EMM has
been
Failure / Error been removed.
removed.
Action: Reinsert the EMM.
See the
hardware documentation
for information
on replacing the EMM.

Storage Management Message Reference

Clear Alert
Number:
None.
Related Alert
Number:
None.

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2298

There is a bad Warning /
sensor on an Non-critical
enclosure.

Severity

Cause and Action

Related Alert
Information

Cause: The enclosure has a
bad sensor. The enclosure
sensors monitor the fan
speeds, temperature
probes, etc. The
%1indicates a substitution
variable. The text for this
substitution variable is
displayed with the alerts in
the Alert Log and can vary
depending on the
situation.

Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: See the hardware
documentation for more
information.
2299

Bad PHY %1

Critical /
Cause: There is a problem
Failure / Error with a physical connection
or PHY. The %1 indicates a
substitution variable.
The text for this
substitution variable is
displayed with the alert in
the Alert Log and can vary
depending on the
situation.

Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: Contact Dell
technical support.

Storage Management Message Reference

169

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2300

The enclosure Critical /
Cause: The controller is
is unstable.
Failure / Error not receiving a consistent
response from the
enclosure. There could be
a firmware problem or an
invalid cabling
configuration. If the cables
are too long, they will
degrade the signal.

Severity

Cause and Action

Related Alert
Information
Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: Power down all
enclosures attached to the
system and reboot the
system. If the problem
persists, upgrade the
firmware to the latest
supported version. You can
download the most current
version of the driver and
firmware from
support.dell.com.
Make sure the cable
configuration is valid.
See the hardware
documentation for valid
cabling configurations.
2301

170

The enclosure Critical /
Cause: The enclosure or an
has a
Failure / Error enclosure component is in
hardware
a Failed or Degraded state.
error.
Action: Check the health
of the enclosure and its
components. Replace any
hardware that is in a Failed
state. See the hardware
documentation for more
information.

Storage Management Message Reference

Clear Alert
Number:
None.
Related Alert
Number:
None.

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2302

The enclosure Critical /
Cause: The enclosure or an Clear Alert
is not
Failure / Error enclosure component is in Number:
responding.
a Failed or Degraded state. None.

Severity

Cause and Action

Related Alert
Information

Action: Check the health Related Alert
of the enclosure and its
Number:
components. Replace any None.
hardware that is in a Failed
state. See the hardware
documentation for more
information.
2303

2304

The enclosure OK / Normal / Cause: This alert is for
cannot
Informational informational purposes.
support both
Action: None
SAS and
SATA
physical disks.
Physical disks
may be
disabled.

Clear Alert
Number:
None.

An attempt to OK / Normal / Cause: This alert is for
hot plug an
Informational informational purposes.
EMM has
Action: None
been
detected.
This type of
hot plug is
not
supported.

Clear Alert
Number:
None.

Related Alert
Number:
None.

Related Alert
Number:
2211

Storage Management Message Reference

171

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

Severity

Cause and Action

Related Alert
Information

2305

The physical
disk is too
small to be
used for a
rebuild.

Warning /
Non-critical

Cause: The physical disk
is too small to rebuild
the data.

Clear Alert
Number:
None.

172

Action: Remove the
Related Alert
physical disk and insert
Number:
a new physical disk that is 2326
the same size or larger than
the disk that is being
rebuilt. The new physical
disk must also use the same
technology (for example,
SAS or SATA) as the disk
being rebuilt. If the rebuild
does not start
automatically after you
have inserted a suitable
physical disk, then run the
Rebuild task. See the
Replacing a Failed Disk
section in the Dell
OpenManage Server
Administrator Storage
Management User’s Guide
for more information.

Storage Management Message Reference

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

Severity

Cause and Action

Related Alert
Information

2306

Bad block
table is
80% full.

Warning /
Non-critical

Cause: The bad block table
is used for remapping bad
disk blocks. This table fills,
as bad disk blocks are
remapped. When the table
is full, bad disk blocks can
no longer be remapped, and
disk errors can no longer be
corrected. At this point,
data loss can occur. The bad
block table is now 80% full.

Clear Alert
Number:
None.
Related Alert
Number:
2307

Action: Back up your data.
Replace the disk generating
this alert and restore from
back up.
2307

Bad block
Critical /
Cause: The bad block table
table is full. Failure / Error is used for remapping bad
Unable to log
disk blocks. This table fills,
block %1
as bad disk blocks are
remapped. When the table
is full, bad disk blocks can
no longer be remapped and
disk errors can no longer be
corrected. At this point,
data loss can occur. The %1
indicates a substitution
variable. The text for this
substitution variable is
displayed with the alert in
the Alert Log and can vary
depending on the
situation.

Clear Alert
Number:
None.
Related Alert
Number:
2048

Action: Replace the disk
generating this alert. If
necessary, restore your data
from backup.

Storage Management Message Reference

173

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2309

A physical
Warning /
disk is incom- Non-critical
patible.

Severity

Cause and Action

Related Alert
Information

Cause: You have attempted
to replace a disk with
another disk that is using an
incompatible technology.
For example, you may have
replaced one side of a
mirror with a SAS disk
when the other side of
the mirror is using SATA
technology.

Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: See the hardware
documentation for
information on replacing
disks.
2310

A virtual
disk is
permanently
degraded.

Critical /
Cause: A redundant virtual
Failure / Error disk has lost redundancy.
This may occur when the
virtual disk suffers the
failure of multiple physical
disks. In this case, both the
source physical disk and
the target disk with
redundant data have failed.
A rebuild is not possible
because there is no
redundancy.
Action: Replace the failed
disks and restore from
backup.

174

Storage Management Message Reference

Clear Alert
Number:
None.
Related Alert
Number:
None.

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2311

The firmware Warning /
on the EMMs Non-critical
is not the
same version.
EMM0 %1
EMM1 %2

Severity

Cause and Action

Related Alert
Information

Cause: The firmware on
the EMM modules is not
the same version. It is
required that both modules
have the same version of
the firmware. This alert
may be caused if you
attempt to insert an EMM
module that has a different
firmware version than an
existing module. The %1
and %2 indicate a
substitution variable.
The text for these
substitution variables is
displayed with the alert in
the Alert Log and can vary
depending on the
situation.

Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: Upgrade to the
same version of the
firmware on both
EMM modules.
Clear Alert
Number:
Action: Replace the power 2325.
supply.
Related Alert
Number:
2122, 2324.

2312

A power
Warning /
supply in the Non-critical
enclosure has
an AC failure.

Cause: The power supply
has an AC failure.

2313

A power
Warning /
supply in the Non-critical
enclosure has
a DC failure.

Cause: The power supply
has a DC failure.

Clear Alert
Number:
Action: Replace the power 2323.
supply.
Related Alert
Number:
2122, 2322.

Storage Management Message Reference

175

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2314

The
Critical /
Cause: Storage
initialization Failure / Error Management is unable
sequence of
to monitor or manage
SAS
SAS devices.
components
Action: Reboot the system.
failed during
If problem persists, make
system
sure you have supported
startup. SAS
versions of the drivers and
management
firmware. Also, you may
and
need to reinstall Storage
monitoring is
Management or Server
not possible.
Administrator because of
some missing installation
components.

Clear Alert
Number:
None.

Diagnostic
message %1

Clear Alert
Number:
None.

2315

Severity

Cause and Action

OK / Normal / Cause: The %1 indicates a
Informational substitution variable.
The text for this
substitution variable is
generated by the utility
that ran the diagnostics
and is displayed with the
alert in the Alert Log.
This text can vary
depending on the
situation. This alert is for
informational purposes.
Action: None

176

Storage Management Message Reference

Related Alert
Information

Related Alert
Number:
None.

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

Severity

2316

Diagnostic
message %1

Critical /
Cause: A diagnostics test
Failure / Error failed. The %1 indicates a
substitution variable.
The text for this
substitution variable is
generated by the utility
that ran the diagnostics
and is displayed with the
alert in the Alert Log.
This text can vary
depending on the
situation.

Cause and Action

Related Alert
Information
Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: See the
documentation for the
utility that ran the
diagnostics for more
information.
2318

Problems
Warning /
with the
Non-critical
battery or the
battery
charger have
been
detected.
The battery
health is poor.

Cause: The battery or the
battery charger is not
functioning properly.

Clear Alert
Number:
None.

Action: Replace the battery Related Alert
pack.
Number:
2188

Storage Management Message Reference

177

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2319

Single-bit
Warning /
ECC error.
Non-critical
The DIMM is
degrading.

2320

178

Severity

Cause and Action

Related Alert
Information

Cause: The DIMM is
Clear Alert
beginning to malfunction. Number:
None.
Action: Replace the
DIMM to avoid data loss or Related Alert
data corruption. The
Number:
DIMM is a part of the
2320
controller battery pack.
See your hardware
documentation for
information on replacing
the DIMM or contact
technical support.

Single-bit
Critical /
Cause: The DIMM is
ECC error.
Failure / Error malfunctioning. Data loss
The DIMM is
or data corruption may be
critically
imminent.
degraded.
Action: Replace the
DIMM immediately to
avoid data loss or data
corruption. The DIMM is a
part of the controller
battery pack. See your
hardware documentation
for information on
replacing the DIMM or
contact technical support.

Storage Management Message Reference

Clear Alert
Number:
None.
Related Alert
Number:
2321

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2321

Single-bit
Critical /
Cause: The DIMM is
ECC error.
Failure / Error malfunctioning. Data loss
The DIMM is
or data corruption is
critically
imminent. The DIMM
degraded.
must be replaced
There will be
immediately. No further
no further
alerts will be generated.
reporting.
Action: Replace the
DIMM immediately.
The DIMM is a part of the
controller battery pack.
See your hardware
documentation for
information on replacing
the DIMM.

Clear Alert
Number:
None.

The DC
Critical /
Cause: The power supply
power supply Failure / Error unit is switched off.
is switched
Either a user switched off
off.
the power supply unit or it
is defective.

Clear Alert
Number:
2323.

2322

Severity

Cause and Action

Related Alert
Information

Related Alert
Number:
None.

Related Alert
Number:
Action: Check if the power None.
switch is turned off. If it is
turned off, turn it on. If the
problem persists, check if
the power cord is attached
and functional. If the
problem is still not
corrected or if the power
switch is already turned on,
replace the power
supply unit.

Storage Management Message Reference

179

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

Severity

2323

The power
supply is
switched on.

OK / Normal / Cause: This alert is for
Informational informational purposes.

Cause and Action

Action: None

Related Alert
Information
Clear Alert
Status: Alert
2323 is a clear
alert for alerts
2313 and
2322.
Related Alert
Number:
None.

2324

The AC
Critical /
Cause: The power cable
power supply Failure / Error may be pulled out
cable has
or removed. The power
been
cable may also have
removed.
overheated and become
warped and nonfunctional.

Clear Alert
Number:
2325.
Related Alert
Number:
None.

Action: Replace the power
cable.
2325

The power
supply cable
has been
inserted.

OK / Normal / Cause: This alert is for
Informational informational purposes.
Action: None

Clear Alert
Status: Alert
2325 is a clear
alert for alerts
2324 and
2312.
Related Alert
Number:
None.

180

Storage Management Message Reference

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

Severity

2326

A foreign
configuration has
been
detected.

OK / Normal / Cause: This alert is for
Informational informational purposes.
The controller has physical
disks that were moved from
another controller.
These physical disks
contain virtual disks that
were created on the other
controller. See the Import
Foreign Configuration and
Clear Foreign
Configuration section in the
Dell OpenManage Server
Administrator Storage
Management User’s Guide
for more information.

Cause and Action

Related Alert
Information
Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: None
2327

The NVRAM Warning /
has corrupted Non-critical
data. The
controller is
reinitializing
the NVRAM.

Cause: The NVRAM has
corrupted data. This may
occur after a power surge, a
battery failure, or for other
reasons. The controller is
reinitializing the NVRAM.

Clear Alert
Number:
None.
Related Alert
Number:
2266

Action: None. The
controller is taking the
required corrective action.
If this alert is generated
often (such as during each
reboot), replace the
controller.
2328

The NVRAM Warning /
has corrupt
Non-critical
data.

Cause: The NVRAM
has corrupt data. The
controller is unable to
correct the situation.
Action: Replace the
controller.

Clear Alert
Number:
None.
Related Alert
Number:
None.

Storage Management Message Reference

181

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

Severity

Cause and Action

Related Alert
Information

2329

SAS port
report: %1

Warning /
Non-critical

Cause: The text for this
alert is generated by the
controller and can vary
depending on the
situation. The %1 indicates
a substitution variable.
The text for this
substitution variable is
generated by the controller
and is displayed with the
alert in the Alert Log.
This text can vary
depending on the
situation.

Clear Alert
Number:
None.

Action: Run the PHY
integrity test diagnostic.
Make sure the cables are
attached securely. If the
problem persists, replace
the cable with a valid cable
according to SAS
specifications. If the
problem still persists,
you may need to replace
some devices such as the
controller or EMM. See the
hardware documentation
for more information.

182

Storage Management Message Reference

Related Alert
Number:
None.

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

Severity

2330

SAS port
report: %1

OK / Normal / Cause: The %1 indicates
Informational a substitution variable.
The text for this
substitution variable is
generated by the controller
and is displayed with the
alert in the Alert Log.
This text can vary
depending on the
situation. This alert is for
informational purposes.

Cause and Action

Related Alert
Information
Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: None
2331

A bad disk
block has
been
reassigned.

OK / Normal / Cause: The disk has a bad
Informational block. Data has been
readdressed to another disk
block and no data loss has
occurred.
Action: Monitor the disk
for other alerts or
indications of poor health.
For example, you may
receive alert 2306. Replace
the disk if you suspect
there is a problem.

2332

A controller
hot plug has
been
detected.

OK / Normal / Cause: This alert is for
Informational informational purposes.
Action: None

Clear Alert
Number:
None.
Related Alert
Number:
None.

Storage Management Message Reference

183

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2334

Controller
OK / Normal / Cause: The %1 indicates a
event log: %1 Informational substitution variable.
The text for this
substitution variable is
generated by the controller
and is displayed with the
alert in the Alert Log.
This text is from events in
the controller event log
that were generated while
Storage Management was
not running. This text can
vary depending on the
situation. This alert is for
informational purposes.

Severity

Cause and Action

Action: None

184

Storage Management Message Reference

Related Alert
Information
Clear Alert
Number:
None.
Related Alert
Number:
None.

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2335

Controller
Warning /
event log: %1 Non-critical

Severity

Cause and Action

Related Alert
Information

Cause: The %1 indicates a
substitution variable.
The text for this
substitution variable is
generated by the controller
and is displayed with the
alert in the Alert Log.
This text is from events in
the controller event log
that were generated while
Storage Management was
not running. This text can
vary depending on the
situation.

Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: If there is a
problem, review the
controller event log and the
Server Administrator Alert
Log for significant events
or alerts that may assist in
diagnosing the problem.
Check the health of the
storage components. See
the hardware
documentation for more
information.

Storage Management Message Reference

185

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2336

Controller
Critical /
Cause: The %1 indicates a
event log: %1 Failure / Error substitution variable. The
text for this substitution
variable is generated by the
controller and is displayed
with the alert in the Alert
Log. This text is from
events in the controller
event log that were
generated while Storage
Management was not
running. This text can vary
depending on the
situation.

Severity

Cause and Action

Related Alert
Information
Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: See the hardware
documentation for more
information.
2337

186

The controller Critical /
Cause: The controller was
is unable to
Failure / Error unable to recover data from
recover
the cache. This may occur
cached data
when the system is without
from the
power for an extended
battery
period of time when the
backup
battery is discharged.
unit (BBU).
Action: Check if the
battery is charged and in
good health. When the
battery charge is
unacceptably low, it cannot
maintain cached data.
Check if the battery has
reached its recharge limit.
The battery may need to be
recharged or replaced.

Storage Management Message Reference

Clear Alert
Number:
None.
Related Alert
Number:
None.

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2338

The
OK / Normal / Cause: This alert is for
controller has Informational informational purposes.
recovered
Action: None
cached data
from the
BBU.

Clear Alert
Number:
None.

The factory
OK / Normal / Cause: This alert is for
default
Informational informational purposes.
settings have
Action: None
been restored.

Clear Alert
Number:
None.

2339

Severity

Cause and Action

Related Alert
Information

Related Alert
Number:
None.

Storage Management Message Reference

187

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2340

The BGI
Critical /
Cause: The BGI task
completed
Failure / Error encountered errors that
with
cannot be corrected.
un-correctable
The virtual disk contains
errors.
physical disks that have
unusable disk space or disk
errors that cannot be
corrected.

Severity

Cause and Action

Related Alert
Information
Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: Replace the
physical disk that contains
the disk errors. Review
other alert messages to
identify the physical disk
that has errors. If the
virtual disk is redundant,
you can replace the
physical disk and continue
using the virtual disk. If the
virtual disk is
non-redundant, you may
need to recreate the virtual
disk after replacing the
physical disk. After
replacing the physical disk,
run Check Consistency to
check the data.
2341

188

The Check
Consistency
made
corrections
and
completed.

OK / Normal / Cause: This alert is for
Informational informational purposes.
Action: None

Storage Management Message Reference

Clear Alert
Number:
None.
Related Alert
Number:
None.

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2342

2343

Severity

Cause and Action

Related Alert
Information

The Check
Warning /
Consistency Non-critical
found
inconsist-ent
parity data.
Data
redundancy
may be lost.

Cause: The data on a
source disk and the
redundant data on a target
disk is inconsistent.

Clear Alert
Number:
None.

The Check
Warning /
Consistency Non-critical
logging of
inconsistent
parity data is
disabled.

Cause: The Check
Consistency can no
longer report errors in
the parity data.

Clear Alert
Number:
None.

Related Alert
Action: Restart the Check Number:
Consistency task. If you
2341, 2343
receive this alert again,
check the health of the
physical disks included in
the virtual disk. Review the
alert messages for
significant alerts related to
the physical disks. If you
suspect that a physical disk
has a problem, replace it
and restore from backup.

Action: See the hardware
documentation for more
information.

Related Alert
Number:
None.

Storage Management Message Reference

189

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2346

Error
Warning /
occurred: %1 Non-critical

Severity

Cause and Action

Related Alert
Information

Cause: A physical device
may have an error. The %1
indicates a substitution
variable. The text for this
substitution variable is
generated by the firmware
and is displayed with the
alert in the Alert Log.
This text can vary
depending on the
situation.

Clear Alert
Number:
None.

The rebuild Critical /
Cause: You are attempting
failed due to Failure / Error to rebuild data that resides
on a defective disk.
errors on the
source
Action: Replace the source
physical disk.
disk and restore from
backup.

Clear Alert
Number:
None.

Related Alert
Number:
2048, 2050,
2056, 2057,
2076, 2079,
2081, 2083,
2095, 2129,
2201, 2203,
Action: Verify the health of 2270, 2282,
attached devices. Review 2369
the Alert Log for
significant events. Run the
PHY integrity diagnostic
tests. You may need to
replace faulty hardware.
Make sure the cables are
attached securely. See the
hardware documentation
for more information.
2347

190

Storage Management Message Reference

Related Alert
Number:
2195, 2346

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2348

The rebuild Critical /
Cause: You are attempting
failed due to Failure / Error to rebuild data on a disk
errors on the
that is defective.
target
Action: Replace the target
physical disk.
disk. If a rebuild does not
automatically start after
replacing the disk, initiate
the Rebuild task. You may
need to assign the new disk
as a hot spare to initiate
the rebuild.

Clear Alert
Number:
None.

A bad disk
Critical /
Cause: A write operation
block could
Failure / Error could not complete
not be
because the disk contains
reassigned
bad disk blocks that could
during a write
not be reassigned. Data
operation.
loss may have occurred and
data redundancy may also
be lost.

Clear Alert
Number:
None.

2349

Severity

Cause and Action

Related Alert
Information

Related Alert
Number:
2195, 2346

Related Alert
Number:
2346

Action: Replace the disk.
2350

2351

There was an Critical /
Cause: The rebuild
unrecoverable Failure / Error encountered an
disk media
unrecoverable disk
error during
media error.
the rebuild.
Action: Replace the disk.

Clear Alert
Number:
None.

A physical
OK / Normal / Cause: This alert is for
disk is marked Informational informational purposes.
as missing.
Action: None.

Clear Alert
Number:
2352.

Related Alert
Number:
2095, 2273

Related Alert
Number:
None.

Storage Management Message Reference

191

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2352

A physical
OK / Normal / Cause: This alert is for
disk that was Informational informational purposes.
marked as
Action: None.
missing has
been
replaced.

Clear Alert
Status: Alert
2352 is a clear
alert for alert
2351.

The enclosure OK / Normal / Cause: This alert is for
temp-erature Informational informational purposes.
has returned
Action: None.
to normal.

Clear Alert
Status: Alert
2353 is a clear
alert for alerts
2100 and
2101.

2353

Severity

Cause and Action

Related Alert
Information

Related Alert
Number:
None.

192

Storage Management Message Reference

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2356

SAS SMP
Critical /
Cause: The %1 indicates a
communicati Failure / Error substitution variable.
ons error %1.
The text for this
substitution variable is
generated by the firmware
and is displayed with the
alert in the Alert Log.
This text can vary
depending on the
situation. The reference to
SMP in this text refers to
SAS Management
Protocol.

Severity

Cause and Action

Related Alert
Information
Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: There may be a
SAS topology error. See the
hardware documentation
for information on correct
SAS topology
configurations. There may
be problems with the
cables such as a loose
connection or an invalid
cabling configuration.
See the hardware
documentation for
information on correct
cabling configurations.
Check if the firmware is a
supported version.

Storage Management Message Reference

193

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2357

SAS expander Critical /
Cause: The %1 indicates a
error: %1
Failure / Error substitution variable. The
text for this substitution
variable is generated by the
firmware and is displayed
with the alert in the Alert
Log. This text can vary
depending on the
situation.

Severity

Cause and Action

Related Alert
Information
Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: There may be a
problem with the
enclosure. Check the
health of the enclosure and
its components. by
selecting the enclosure
object in the tree view. The
Health subtab displays a
red "X" or yellow
exclamation point for
enclosure components that
are failed or degraded. See
the enclosure
documentation for more
information.
2358

The battery OK / Normal / Cause: This alert is for
charge cycle is Informational informational purposes.
complete.
Action: None.

Clear Alert
Number:
None.
Related Alert
Number:
None.

194

Storage Management Message Reference

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

Severity

Cause and Action

Related Alert
Information

2359

The physical
disk is not
certified.

Warning /
Non-critical

Cause: The physical disk
does not comply with the
standards set by Dell and is
not supported.

Clear Alert
Number:
None.

Action: Replace the
physical disk with a
physical disk that is
supported.
2360

2361

Related Alert
Number:
None.

A user has
OK / Normal / Cause: This alert is for
discarded
Informational informational purposes.
data from the
Action: None.
controller
cache.

Clear Alert
Number:
None.

Physical
OK / Normal / Cause: This alert is for
disk(s) that
Informational informational purposes.
are part of a
Action: None.
virtual disk
have been
removed
while the
system was
shut down.
This removal
was
discovered
during system
startup.

Clear Alert
Number:
None.

Related Alert
Number:
None.

Storage Management Message Reference

195

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2362

Physical
OK / Normal / Cause: This alert is for
disk(s) have Informational informational purposes.
been removed
Action: None.
from a
virtual disk.
The virtual
disk will be in
Failed state
during the
next system
reboot.

Clear Alert
Number:
None.

All virtual
OK / Normal / Cause: This alert is for
disks are
Informational informational purposes.
missing from
Action: None.
the controller.
This situation
was
discovered
during system
start-up.

Clear Alert
Number:
None.

Dedicated
OK / Normal / Cause: This alert is for
spare
Informational informational purposes.
imported as
Action: None.
global due to
missing arrays

Clear Alert
Number:
None.

2364

2366

196

Severity

Cause and Action

Storage Management Message Reference

Related Alert
Information

Related Alert
Number:
None.

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2367

Rebuild not Warning /
possible as
Non-critical
SAS/SATA is
not supported
in the same
virtual disk.

2368

Severity

Cause and Action

Related Alert
Information

Cause: The physical disk is Clear Alert
using an incompatible
Number:
technology.
None.
Action: All physical disks in Related Alert
the virtual disk must use
Number:
the same technology. You 2326
cannot use both SAS and
SATA physical disks in the
same virtual disk. Remove
the physical disk and insert
a new physical disk that
uses the correct technology.
If the rebuild does not start
automatically after you
have inserted a suitable
physical disk, then run the
Rebuild task.

The SCSI
OK / Normal / Cause: This alert is for
Enclosure
Informational informational purposes.
Processor
Action: None.
(SEP) has
been
rebooted as
part of the
firmware
download
operation and
will be
unavailable
until the
operation
completes.

Clear Alert
Number:
None.
Related Alert
Number:
2049, 2052,
2162, 2292

Storage Management Message Reference

197

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2369

Virtual Disk OK / Normal /
Re-dundancy Informational
has been
degraded.

Severity

Cause and Action

Related Alert
Information

Cause: A physical disk in a
RAID 6 virtual disk has
either failed or been
removed.

Clear Alert
Number:
2121.

Action: Replace the
missing or failed physical
disk.
2370

Redundant
Path View
Cleared

OK / Normal / Cause: This alert is
Clear Alert
Informational provided for informational Number:
purposes.
None.
Action: None.

2371

2372

198

Related Alert
Number:
2048, 2049,
2050, 2076,
2346

Attempted
OK / Normal / Cause: This alert is for
import of
Informational informational purposes.
Unsupported
Action: None.
Virtual Disk
type RAID%1
Attempted
OK / Normal /
import of
Informational
Virtual Disk
exceeding the
limit
supported on
the controller.

Related Alert
Number:
None.
Clear Alert
Number:
None.
Related Alert
Number:
None.

Cause: This alert is
Clear Alert
provided for informational Number:
purposes.
None.
Action: None.

Storage Management Message Reference

Related Alert
Number:
None.

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

Severity

2373

Attempted
import of
unsupported
Virtual Disk
type RAID
%1

OK / Normal / Cause: This alert is
Informational provided for informational
purposes. User is
attempting to import a
foreign virtual disk with
unsupported RAID level on
the controller

Cause and Action

Related Alert
Information
Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: None.
2374

Attempted
import of
Virtual Disk
with missing
span

OK / Normal / Cause: This alert is
Informational provided for informational
purposes. User is
attempting to import a
foreign virtual disk with a
missing span.

Clear Alert
Number:
None.
Related Alert
Number:
None.

Action: None.
2375

Attempted
import of
Virtual Disk
with missing
physical disk

OK / Normal / Cause: User is attempting
Informational to import a foreign virtual
disk with a missing physical
disk. This alert is provided
for informational purposes.
Action: None.

2376

Attempted
import of
Virtual Disk
with stale
physical disk

OK / Normal / Cause: User is attempting
Informational to import a foreign virtual
disk with a stale physical
disk. This alert is provided
for informational purposes.
Action: None.

2377

Attempted
import of an
orphan drive

OK / Normal / Cause: User is attempting
Informational to import an orphan drive.
This alert is provided for
informational purposes.
Action: None.

Clear Alert
Number:
None.
Related Alert
Number:
None.
Clear Alert
Number:
None.
Related Alert
Number:
None.
Clear Alert
Number:
None.
Related Alert
Number:
None.

Storage Management Message Reference

199

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

2378

Attempted
OK / Normal /
import of an Informational
incomp-atible
physical drive

Severity

Cause and Action

Related Alert
Information

Cause: User is attempting
to import an incompatible
physical drive. This alert is
provided for informational
purposes.

Clear Alert
Number:
None.

Action: None.
2379

2380

200

Related Alert
Number:
None.

An overflow OK / Normal /
of the foreign Informational
configuration
has occurred.
You can
import the
foreign
configuration
in multiple
attempts

Cause: This alert is
Clear Alert
provided for informational Number:
purposes.
None.

Foreign
OK / Normal /
configInformational
uration has
been partially
imported.
Some configuration failed
to import.

Cause: This alert is
Clear Alert
provided for informational Number:
purposes.
None.

Action: None.

Storage Management Message Reference

Related Alert
Number:
None.

Table 4-4.

Storage Management Messages (continued)

Event ID

Description

Severity

2381

Controller
preserved
cache is
recovered.

OK / Normal / Cause: This alert is
Clear Alert
Informational provided for informational Number:
purposes.
None.

2382

An unWarning /
supported
Non-critical
configuration was
detected.
The controlle
r does not
support
physical disks
of type Solid
State Device
(SSD):

Cause and Action

Related Alert
Information

Action: None

Related Alert
Number:
None.

Cause: A physical disk of
media type SSD is
attached to a controller
that does not support SSD
disks.

Clear Alert
Number:
None.

Action: Replace the
unsupported physical disk
with a physical disk of
media type Hard Disk
Drive.

Related Alert
Number:
None.

Storage Management Message Reference

201

202

Storage Management Message Reference

Index
Symbols

1050, 22

%1, Storage Management has
lost communication with
this RAID controller and
attached storage. An
immediate reboot is strongly
recommended to avoid
further problems. If the
reboot does not restore
communication, there may
be a hardware failure., 158

1051, 22
1052, 23
1053, 23
1054, 24
1055, 24
1100, 25
1101, 25
1102, 26
1103, 26

Numerics

1104, 27

0001, 19

1105, 27

1000, 19

1150, 28

1001, 19

1151, 28

1002, 19

1152, 29

1003, 19

1153, 29

1004, 20

1154, 30

1005, 20

1155, 30

1006, 20

1200, 31

1007, 20

1201, 32

1008, 21

1202, 32

1009, 21

1203, 33

1011, 21

1204, 33

1012, 21

1205, 34

Index

203

1250, 35

1500, 48

1251, 35

1501, 48

1252, 36

1502, 48

1253, 36

1503, 49

1254, 37

1504, 49

1255, 37

1505, 49

1300, 38

1550, 50

1301, 38

1551, 50

1302, 39

1552, 50

1303, 39

1553, 50

1304, 39

1554, 50

1305, 40

1555, 50

1306, 40

1600, 51

1350, 41

1601, 51

1351, 42

1602, 52

1352, 42

1603, 52

1353, 43

1604, 53

1354, 43

1605, 53

1355, 44

1650, 54

1403, 45

1651, 54

1404, 45

1652, 55

1450, 46

1653, 55

1451, 46

1700, 56

1452, 46

1701, 56

1453, 46

1702, 56

1454, 47

1703, 57

1455, 47

1704, 57

204

Index

1705, 57

2075, 94

2000, 58

2076, 95

2002, 58

2077, 95

2003, 58

2079, 95

2004, 58

2080, 96

2005, 58

2081, 96

2048, 85

2082, 97

2049, 86

2083, 97

2050, 87

2085, 97

2051, 87

2086, 98

2052, 87

2087, 98

2053, 88

2088, 98

2054, 88

2089, 98

2055, 88

2090, 99

2056, 89

2091, 99

2057, 90

2092, 99

2058, 91

2094, 100

2059, 91

2095, 101

2060, 91

2098, 101

2061, 92

2099, 101

2062, 92

2100, 102

2063, 92

2101, 102

2064, 92

2102, 103

2065, 92

2103, 103

2067, 93

2104, 104

2070, 94

2105, 104

2074, 94

2106, 104

Index

205

2107, 105

2138, 121

2108, 106

2139, 121

2109, 107

2140, 122

2110, 109

2141, 122

2111, 109

2142, 122

2112, 110

2143, 122

2114, 110

2144, 123

2115, 111

2145, 123

2116, 111

2146, 123

2117, 112

2147, 123

2118, 112

2148, 123

2120, 112

2149, 124

2121, 113

2150, 124

2122, 113

2151, 124

2123, 114

2152, 124

2124, 115

2153, 125

2125, 116

2154, 125

2126, 116

2155, 125

2127, 117

2156, 125

2128, 117

2157, 126

2129, 117

2158, 126

2130, 118

2159, 126

2131, 118

2162, 127

2132, 119

2163, 127

2135, 119

2164, 127

2136, 119

2165, 128

2137, 120

2166, 128

206

Index

2167, 129

2195, 139

2168, 130

2196, 139

2169, 130

2197, 139

2170, 130

2198, 140

2171, 131

2199, 140

2173, 132

2200, 140

2174, 132

2201, 141

2175, 133

2202, 141

2176, 133

2203, 142

2177, 133

2204, 142

2178, 134

2205, 142

2179, 134

2206, 143

2180, 135

2207, 143

2181, 135

2210, 144

2182, 135

2211, 144

2183, 135

2212, 144

2184, 136

2213, 144

2185, 136

2214, 145

2186, 136

2215, 145

2187, 136

2216, 145

2188, 137

2217, 145

2189, 137

2218, 145

2190, 137

2219, 146

2191, 138

2220, 146

2192, 138

2221, 146

2193, 139

2222, 147

2194, 139

2223, 147

Index

207

2224, 147

2254, 154

2226, 148

2255, 154

2227, 148

2257, 154

2228, 148

2258, 155

2229, 149

2259, 155

2230, 149

2260, 155

2231, 149

2261, 155

2232, 149

2262, 155

2233, 150

2263, 156

2234, 150

2264, 156

2235, 150

2265, 157

2236, 150

2266, 157

2237, 150

2267, 158

2238, 151

2268, 158

2239, 151

2269, 158

2240, 151

2270, 159

2241, 151

2271, 159

2242, 151

2272, 160

2243, 152

2273, 160

2244, 152

2274, 161

2245, 152

2276, 161

2246, 152

2277, 161

2247, 153

2278, 162

2248, 153

2279, 162

2249, 153

2280, 163

2251, 153

2281, 163

2252, 154

2282, 164

208

Index

2285, 164

2313, 175

2286, 165

2314, 176

2287, 165

2315, 176

2288, 165

2316, 177

2289, 166

2318, 177

2290, 167

2319, 178

2291, 167

2320, 178

2292, 167

2321, 179

2293, 167

2322, 179

2294, 168

2323, 180

2295, 168

2324, 180

2296, 168

2325, 180

2297, 168

2326, 181

2298, 169

2327, 181

2299, 169

2328, 181

2300, 170

2329, 182

2301, 170

2330, 183

2302, 171

2331, 183

2303, 171

2332, 183

2304, 171

2334, 184

2305, 172

2335, 185

2306, 173

2336, 186

2307, 173

2337, 186

2309, 174

2338, 187

2310, 174

2339, 187

2311, 175

2340, 188

2312, 175

2341, 188

Index

209

2342, 189

2375, 199

2343, 189

2376, 199

2346, 190

2377, 199

2347, 190

2378, 200

2348, 191

2379, 200

2349, 191

2380, 200

2350, 191

2381, 201

2351, 191

2382, 201

2352, 192
2353, 192
2356, 193
2357, 194
2358, 194
2359, 195
2360, 195
2361, 195
2362, 196
2364, 196
2366, 196
2367, 197
2368, 197
2369, 198
2370, 198
2371, 198
2372, 198
2373, 199
2374, 199

210

Index

A
A bad disk block could not be
reassigned during a write
operation., 191
A bad disk block has been
reassigned., 183
A block on the physical disk has
been punctured by the
controller., 160
A consistency check on a virtual
disk has been paused
(suspended), 110
A consistency check on a virtual
disk has been resumed, 111
A controller hot plug has been
detected., 183
A controller rescan has been
initiated., 150
A dedicated hot spare
failed., 142

A dedicated hot spare has been
automatically
unassigned., 142
A dedicated hot spare has been
removed., 142
A device has been inserted., 168
A device has been removed., 168
A device is in an unknown
state., 157
A device is missing., 156
A disk media error has been
corrected., 163

A physical disk is marked as
missing., 191
A physical disk that was marked
as missing has been
replaced., 192
A power supply in the enclosure
has a DC failure., 175
A power supply in the enclosure
has an AC failure., 175
A previously scheduled system
BIOS update has been
canceled, 19

A disk media error was corrected
during recovery., 164

A system BIOS update has been
scheduled for the next
reboot, 19

A foreign configuration has been
cleared., 151

A user has discarded data from
the controller cache., 195

A foreign configuration has been
detected., 181

A virtual disk and its mirror have
been split, 111

A foreign configuration has been
imported., 151

A virtual disk blink has been
initiated., 152

A global hot spare failed., 141

A virtual disk blink has
ceased., 152

A global hot spare has been
removed., 141
A global rescan has
initiated., 155
A Learn cycle start is pending
while the battery
charges., 165
A mirrored virtual disk has been
unmirrored, 112
A physical disk is
incompatible., 174

A virtual disk is permanently
degraded., 174
AC power cord is not being
monitored, 48
AC power cord messages, 48
AC power cord sensor, 10
AC power cord sensor has
failed, 48, 69
AC power has been lost, 49

Index

211

AC power has been restored, 48

All virtual disks are missing from
the controller. This situation
was discovered during
system start-up., 196

Background initialization
cancelled, 117

An attempt to hot plug an EMM
has been detected. This type
of hot plug is not
supported., 171
An EMM has been
discovered., 167
An EMM has been inserted., 168
An EMM has been removed., 168
An enclosure blink has
ceased, 155
An enclosure blink operation has
initiated., 155
An invalid SAS configuration has
been detected., 135
Array Manager is installed on the
system, 119
Asset name changed, 124
Asset tag changed, 124
Automatic System Recovery
(ASR) action was
performed, 20

Background initialization
completed, 118
Background initialization
failed, 117
Background initialization
started, 117
Bad block extended medium
error, 124
Bad block extended sense
error, 124
Bad block medium error, 123
Bad block replacement error, 123
Bad block sense error, 123
Bad block table is 80% full., 173
Bad block table is full. Unable to
log block %1, 173
Bad PHY %1, 169
Battery charge in progress, 145
Battery charge process
interrupted, 145
battery messages, 79
BIOS Generated System
Events, 72
bios generated system
messages, 72
BMC Watchdog Events, 66
BMC watchdog messages, 66

212

Index

C
cable interconnect messages, 79
Change write policy, 112
Chassis intrusion detected, 37,
65
Chassis intrusion in progress, 36,
65
chassis intrusion messages, 35
Chassis intrusion returned to
normal, 36
chassis intrusion sensor, 9
Chassis intrusion sensor
detected a non-recoverable
value, 37, 65
Chassis intrusion sensor has
failed, 35
Chassis intrusion sensor value
unknown, 35, 64
Chassis Management Controller
Messages, 37
Communication regained, 127
Communication timeout, 120
Communication with the
enclosure has been lost., 167

Controller battery recondition is
completed, 104
Controller configuration has
been reset, 126
Controller event log
%1, 184-186
Controller log file entry
%1, 157
Controller rebuild rate has
changed, 122
cooling device messages, 25
current sensor, 9
Current sensor detected a failure
value, 33
Current sensor detected a nonrecoverable value, 34
Current sensor detected a
warning value, 33
Current sensor has failed, 31, 63
current sensor messages, 31
Current sensor returned to a
normal value, 32, 63
Current sensor value
unknown, 32

Controller alarm disabled, 123
Controller alarm enabled, 122

Controller alarm has been
tested, 125

Dead disk segments
restored, 122

Controller battery is
reconditioning, 104

Dedicated hot spare assigned.
Physical disk %1, 139

Controller battery low, 123
Index

213

Dedicated hot spare unassigned.
Physical disk %1, 139
Dedicated spare imported as
global due to missing
arrays, 196

fan enclosure messages, 46
Fan enclosure removed from
system, 46

Device failed, 85

Fan enclosure removed from
system for an extended
amount of time, 47

Device returned to normal, 113

fan enclosure sensor, 10

Diagnostic message %1, 176-177

Fan enclosure sensor detected a
non-recoverable value, 47

Drive Events, 69
Driver version mismatch, 119
drives messages, 69

Fan enclosure sensor has
failed, 46
Fan enclosure sensor value
unknown, 46

fan sensor, 9

Enclosure alarm disabled, 121

Fan sensor detected a failure
value, 27

Enclosure alarm enabled, 121
Enclosure firmware
mismatch, 112

Fan sensor detected a nonrecoverable value, 27

Enclosure was shut down, 110

Fan sensor detected a warning
value, 26

entity presence messages, 80

Fan Sensor Events, 61

Error occurred
%1, 190

Fan sensor has failed, 25, 60

event description reference, 14

Fan sensor returned to a normal
value, 26

Fan sensor value unknown, 25,
60

Failure prediction threshold
exceeded due to test, 109

Firmware version mismatch, 118

Fan enclosure inserted into
system, 46

214

Index

fan sensor messages, 61

Global hot spare assigned, 101

Maximum temperature probe
warning threshold value
changed, 125

Global hot spare unassigned, 101

H
hardware log sensor, 10
Hardware Log Sensor Events, 68
hardware log sensor messages, 68
Hot spare SMART polling
failed., 164

I
Intrusion Events, 71
intrusion messages, 71

Memory device ECC Correctable
error count crossed a warning
threshold, 45
Memory device ECC Correctable
error count sensor crossed a
failure threshold, 45
memory device messages, 45
Memory device monitoring has
been disabled, 45
Memory ECC Events, 66
memory ecc messages, 66
Memory Events, 67
memory modules messages, 67
memory prefailure sensor, 10

L
Log backup created, 19
Log monitoring has been
disabled, 50, 71
Log size is near or at capacity, 50
Log size returned to a normal
level, 50
Log status is unknown, 50, 71
Log was cleared, 19

messages
AC power cord, 48, 69
battery, 79
battery sensor, 56
bios generated system, 72
BMC watchdog, 66
cable interconnect, 79
chassis intrusion, 35
cooling device, 25
current sensor, 31
drives, 69
entity presence, 80
fan enclosure, 46
fan sensor, 61
hardware log sensor, 68
Index

215

intrusion, 71
memory device, 45
memory ecc, 66
memory modules, 67
miscellaneous, 19
pluggable device, 54, 72
power supply, 41, 64
processor sensor, 51
processor status, 63
r2 generated system, 76
redundancy unit, 37
storage management, 85
temperature sensor, 22, 59
voltage sensor, 28, 60
Minimum temperature probe
warning threshold value
changed, 125
Multi-bit ECC error., 166
Multiple enclosures are attached
to the controller. This is an
unsupported
configuration., 138

P
Patrol Read found an
uncorrectable media
error., 160
Physical disk dead segments
recovered, 122

Physical disk initialize
completed, 98
Physical disk initialize failed, 96
Physical disk inserted, 87
Physical disk offline, 87
Physical disk online, 126
Physical disk rebuild
cancelled, 94
Physical disk rebuild
completed, 99
Physical disk rebuild failed, 97
Physical disk rebuild started, 92
Physical disk removed, 86
Physical disk(s) have been
removed from a virtual disk.
The virtual disk will be in
Failed state during the next
system reboot., 196
Physical disk(s) that are part of a
virtual disk have been
removed while the system
was shut down. This removal
was discovered during
system start-up., 195
pluggable device sensor, 10
Power And Performance
Events, 80

Physical disk degraded, 87

Power supply detected a
failure, 43

Physical disk initialization
started, 92

Power supply detected a
warning, 43, 67
Power Supply Events, 64

216

Index

power supply messages, 41, 64

Power supply returned to
normal, 42, 67

r2 generated system
messages, 76

power supply sensor, 10

Rebuild completed with
errors, 127

Power supply sensor detected a
non-recoverable value, 44
Power supply sensor has
failed, 41

Rebuild not possible as SAS/
SATA is not supported in the
same virtual disk., 197

Power supply sensor value
unknown, 42

Recharge count maximum
exceeded, 144

Predictive Failure reported, 100

Redundancy degraded, 40, 113

Problems with the battery or the
battery charger have been
detected. The battery health
is poor., 177

Redundancy is offline, 39

processor sensor, 10
Processor sensor detected a
failure value, 53, 72
Processor sensor detected a nonrecoverable value, 53
Processor sensor detected a
warning value, 52, 72
Processor sensor has failed, 51,
72

Redundancy lost, 40, 114
Redundancy normal, 115
Redundancy not applicable, 39,
66
Redundancy regained, 39
Redundancy sensor has failed, 38
Redundancy sensor value
unknown, 38, 66
redundancy unit messages, 37
redundancy unit sensor, 10

Processor sensor returned to a
normal state, 52, 72

Processor sensor value
unknown, 51, 72

SAS expander error
%1, 194

Processor Status Events, 63

SAS port report
%1, 182-183

processor status messages, 63

SAS SMP communications error
%1., 193
Index

217

SCSI sense data, 101
SCSI sense sector reassign, 116
See the Readme file for a list of
validated controller driver
versions, 127
sensor
AC power cord, 10
chassis intrusion, 9
current, 9
fan, 9
fan enclosure, 10
hardware log, 10
memory prefailure, 10
power supply, 10
processor, 10, 51
redundancy unit, 10
temperature, 9
voltage, 9
Server Administrator starting, 19
Server Administrator startup
complete, 19
Service tag changed, 125
Single-bit ECC error limit
exceeded., 136
Single-bit ECC error., 167
Single-bit ECC error. The
DIMM is critically
degraded., 178
Single-bit ECC error. The
DIMM is critically degraded.
There will be no further
reporting., 179

218

Index

Single-bit ECC error. The
DIMM is degrading., 178
Smart configuration change, 105
Smart FPT exceeded, 104
SMART thermal shutdown is
disabled., 156
SMART thermal shutdown is
enabled., 155
Smart warning, 106
Smart warning degraded, 109
Smart warning temperature, 107
SMBIOS data is absent, 20
System Event Log Messages, 59
system management data
manager started, 21
system management data
manager stopped, 21

T
Temperature dropped below the
minimum failure
threshold, 103
Temperature dropped below the
minimum warning
threshold, 102
Temperature exceeded the
maximum failure
threshold, 103
Temperature exceeded the
maximum warning
threshold, 102

temperature sensor, 9
Temperature sensor detected a
failure value, 24
Temperature sensor detected a
non-recoverable value, 24
Temperature sensor detected a
warning value, 23
Temperature Sensor Events, 59
Temperature sensor has
failed, 22, 59
temperature sensor
messages, 22, 59
Temperature sensor returned to a
normal value, 23, 60

The Check Consistency made
corrections and
completed., 188
The Check Consistency rate has
changed., 150
The Clear operation has
cancelled., 154
The controller alarm is
silenced., 149
The controller battery charge
level is below a normal
threshold., 162
The controller battery charge
level is normal., 130

Temperature sensor value
unknown, 22, 59

The controller battery charge
level is operating within
normal limits., 162

The AC power supply cable has
been removed., 180

The controller battery has been
removed., 132

The background initialization
(BGI) rate has changed., 150

The controller battery has been
replaced., 133

The battery charge cycle is
complete., 194

The controller battery is
charging., 153

The BGI completed with
uncorrectable errors., 188

The controller battery is
degraded., 152

The Check Consistency found
inconsistent parity data.
Data redundancy may be
lost., 189

The controller battery is
executing a Learn cycle., 153

The Check Consistency logging
of inconsistent parity data is
disabled., 189

The controller battery Learn
cycle has been
postponed., 134
The controller battery Learn
cycle has completed., 133

Index

219

The controller battery Learn
cycle has started., 133
The controller battery Learn
cycle has timed out., 134
The controller battery Learn
cycle will start in %
days., 135
The controller battery needs to
be replaced., 130
The controller battery
temperature is above
normal, 131
The controller battery
temperature is above
normal., 144
The controller battery
temperature is normal., 131
The controller cache has been
discarded., 136
The controller debug log file has
been exported., 151
The controller has recovered
cached data from the
BBU., 187
The controller is unable to
recover cached data from the
battery backup unit
(BBU)., 186
The controller reconstruct rate
has changed., 158
The controller write policy has
been changed to Write
Back., 137

220

Index

The controller write policy has
been changed to Write
Through., 137
The current kernel version and
the non-RAID SCSI driver
version are older than the
minimum required levels.See
the Readme file for a list of
validated kernel and driver
versions., 129
The DC power supply is
switched off., 179
The dedicated hot spare is too
small., 161
The EMM has failed., 167
The enclosure cannot support
both SAS and SATA physical
disks. Physical disks may be
disabled., 171
The enclosure has a hardware
error., 170
The enclosure is not
responding., 171
The enclosure is unstable., 170
The enclosure temperature has
returned to normal., 192
The factory default settings have
been restored., 187
The firmware on the EMMs is
not the same version. EMM0
%1 EMM1 %2, 175
The global hot spare is too
small., 161

The initialization sequence of
SAS components failed
during system startup. SAS
management and monitoring
is not possible., 176
The non-RAID SCSI driver
version is older than the
minimum required level.See
the Readme file for the
validated driver version., 130
The NVRAM has corrupt
data., 181

The Patrol Read rate has
changed., 150
The physical disk blink has
ceased., 154
The physical disk blink has
initiated., 153
The physical disk Clear
operation failed., 159
The physical disk Clear
operation has
completed., 158

The NVRAM has corrupted data.
The controller is
reinitializing the
NVRAM., 181

The physical disk Clear
operation has started., 153

The only hot spare available is a
SAS disk. SAS disks cannot
replace SATA disks., 143

The physical disk is not
certified., 195

The only hot spare available is a
SATA disk. SATA disks
cannot replace SAS
disks., 143

The physical disk has been
started., 154

The physical disk is not
supported., 144
The physical disk is too small to
be used for a rebuild., 172

The Patrol Read corrected a
media error., 159

The physical disk rebuild has
resumed., 161

The patrol read has
resumed., 165

The power supply cable has been
inserted., 180

The Patrol Read has started., 151

The power supply is switched
on., 180

The Patrol Read has
stopped., 152
The Patrol Read is paused., 165
The Patrol Read mode has
changed., 151

The RAID controller firmware
and driver validation was not
performed. The
configuration file cannot be
opened., 128

Index

221

The RAID controller firmware
and driver validation was not
performed. The
configuration file is out of
date or corrupted., 128
The rebuild failed due to errors
on the source physical
disk., 190
The rebuild failed due to errors
on the target physical
disk., 191
The SCSI Enclosure Processor
(SEP) has been rebooted as
part of the firmware
download operation and will
be unavailable until the
operation completes., 197
The virtual disk cache policy has
changed., 140
The virtual disk Check
Consistency has made
corrections and
completed., 138
The virtual disk Read policy has
changed., 139
The virtual disk reconfiguration
has resumed., 139
There is a bad sensor on an
enclosure., 169
There was an unrecoverable disk
media error during the
rebuild., 191
Thermal shutdown protection
has been initiated, 20

222

Index

U
understanding
event description, 14
Unsupported configuration
detected. The SCSI rate of
the enclosure management
modules (EMMs) is not the
same. EMM0 %1 EMM1
%2, 132
User initiated host system
reset, 20

V
viewing
event information, 13
event messages, 11
events in Red Hat Linux, 12
events in SUSE Linux Enterprise
Server, 12
events in Windows 2000, 12
Virtual disk check consistency
cancelled, 93
Virtual disk check consistency
completed, 97
Virtual disk check consistency
failed, 95
Virtual disk check consistency
started, 91
Virtual disk configuration
changed, 88
Virtual disk created, 88
Virtual disk degraded, 90

Virtual disk deleted, 88
Virtual disk failed, 89
Virtual disk format changed, 95
Virtual disk format
completed, 98
Virtual disk format started, 91
Virtual disk has inconsistent
data., 163
Virtual disk initialization, 119
Virtual disk initialization
cancelled, 94
Virtual disk initialization
completed, 98

Voltage sensor detected a failure
value, 30, 62
Voltage sensor detected a nonrecoverable value, 30
Voltage sensor detected a
warning value, 29
Voltage Sensor Events, 60
Voltage sensor has failed, 28, 61
voltage sensor messages, 28, 60
Voltage sensor returned to a
normal value, 29
Voltage sensor value
unknown, 28, 61

Virtual disk initialization
failed, 95
Virtual disk initialization
started, 92
Virtual disk rebuild
completed, 99
Virtual disk rebuild failed, 97
Virtual disk rebuild started, 92
Virtual disk reconfiguration
completed, 99
Virtual disk reconfiguration
failed, 96
Virtual disk reconfiguration
started, 92
Virtual Disk Redundancy has
been degraded., 198
Virtual disk renamed, 126
voltage sensor, 9
Index

223

224

Index

Dell Openmanage Server Administrator Version 6 0 3 Quick Reference Guide 6.0.3 Message

Navigation menu

Versions of this User Manual:

Views

Navigation