intellectual property laws. Dell™ and the Dell logo are trademarks of Dell Inc. in the United States and/or other
jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies.
Dell OpenManage Server Administrator generates event messages stored primarily in the operating
system or Server Administrator event logs and sometimes in Simple Network Management Protocol
(SNMP) traps. This document describes the event messages that are created by Server Administrator
version 7.1.2 and displayed in the Server Administrator alert log.
Server Administrator creates events in response to sensor status changes and other monitored
parameters. The Server Administrator event monitor uses these status change events to add descriptive
messages to the operating system event log or the Server Administrator alert log.
Each event message that Server Administrator adds to the alert log consists of a unique identifier called
the event ID for a specific event source category and a descriptive message. The event message includes
the severity, cause of the event, and other relevant information, such as the event location and the
previous state of the monitored item.
The tables in this guide list all Server Administrator event IDs in numeric order. Each entry includes the
description, severity level, and cause of the event ID. The message text in angle brackets (for example,
(for example, <State>) describes the event-specific information provided by the Server Administrator.
What’s New in this Release
New Alert messages for Instrumentation Service — 1015 and 1016.
New Alert messages for Non-Volatile Memory Express (NVMe) — 2440, 2441, 2442, 2443 and 2445.
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 1. Alert Message Change History
Storage Management 4.4
Product Versions to which changes
apply
New Alerts
Deleted Alerts
Modified AlertsNone
Storage Management 4.3
Product Versions to which changes
apply
New Alerts
Storage Management 4.4.0
Server Administrator 7.4.0
Storage Management 3.2.0
Server Administrator 6.2.0
2387, 2388, 2389, 2390, 2392, 2393
Messages Not Described in This Guide
This guide describes only event messages logged by Server Administrator and Storage Management that
are displayed in the Server Administrator alert log. For information on other messages generated by your
system, see one of the following sources:
•The Installation and Troubleshooting Guide or Hardware Owner's Manual shipped with your system
•Operating system documentation
•Application program documentation
Understanding Event Messages
Add your section content here.This section describes the various types of event messages generated by
the Server Administrator. When an event occurs on your system, Server Administrator sends information
about one of the following event types to the systems management console:
Table 2. Understanding Event Messages
IconAlert SeverityComponent Status
OK /Normal /
Informational
Warning / Noncritical
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.
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
19
IconAlert SeverityComponent Status
temperature probe in an enclosure) has crossed
a warning threshold.
Critical / Failure /
Error
Server Administrator generates events based on status changes in the following sensors:
•Temperature Sensor — Helps protect critical components by alerting the systems management
console when temperatures become too high inside a chassis; also monitors the temperature in a
variety of locations in the chassis and in attached system(s).
•Fan Sensor — Monitors fans in various locations in the chassis and in attached system(s).
•Voltage Sensor — Monitors voltages across critical components in various chassis locations and in
attached system(s).
•Current Sensor — Monitors the current (or amperage) output from the power supply (or supplies) in
the chassis and in attached system(s).
•Chassis Intrusion Sensor — Monitors intrusion into the chassis and attached system(s).
•Redundancy Unit Sensor — Monitors redundant units (critical units such as fans, AC power cords, or
power supplies) within the chassis; also monitors the chassis and attached system(s). For example,
redundancy allows a second or 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 attached system(s).
•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 in attached system(s).
•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.
•SD Card Device Sensor — Monitors instrumented Secure Digital (SD) card devices in the system.
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.
Sample Event Message Text
The following example shows the format of the event messages logged by Server Administrator.
EventID: 1000
Source: Server Administrator
Category: Instrumentation Service
Type: Information
Date and Time: Mon Oct 21 10:38:00 2002
Computer: <computer name>
Description: Server Administrator starting
20
Data: Bytes in Hex
Viewing Alerts and Event Messages
An event log is used to record information about important events.
Server Administrator generates alerts that are added to the operating system event log and to the Server
Administrator alert log. To view these alerts in Server Administrator:
1.Select the System object in the tree view.
2.Select the Logs tab.
3.Select the Alert tab.
You can also view the event log using your operating system’s event viewer. Each operating system’s
event viewer accesses the applicable operating system event log.
The location of the event log file depends on the operating system you are using.
•On systems running the Microsoft Windows operating systems, event messages are logged in the
operating system event log and the Server Administrator event log.
NOTE: The Server Administrator event log file is named dcsys32.xml and is located in the
<install_path>\omsa\log directory. The default install_path is C:\Program Files\Dell\SysMgt.
•On systems running the Red Hat Enterprise Linux, SUSE Linux Enterprise Server, Citrix XenServer,
VMware ESX, and VMware ESXi operating systems, the event messages are logged in the operating
system log file and the Server Administrator event log.
NOTE: The default name of the operating system log file is /var/log/messages, and you can view
the operating system log file using a text editor such as vi or emacs. The Server Administrator
event log file is named dcsys<xx>.xml,where xx is either 32 or 64 bit depending on the operating
system. In the Red Hat Enterprise Linux, SUSE Linux Enterprise Server, Citrix XenServer and
VMware ESX operating systems, the Server Administrator event log file is located in the /opt/dell/srvadmin/var/log/openmanage directory. In the VMware ESXi operating system, the Server
Administrator event log file is located in the /etc/cim/dell/srvadmin/log/openmanage directory.
Logging Messages to a Unicode Text File
Logging messages to a Unicode text file is optional. By default, the feature is disabled in the Server
Administrator. To enable this feature, modify the Event Manager section of the dcemdy <xx>.ini
configuration file where xx is 32 or 64 bit depending on the operating system, as follows:
•On systems running Microsoft Windows operating systems, you can locate the configuration file in
the <install_path> \dataeng\ini directory and set the property UnitextLog.enabled=true. The
default install_path is C:\Program Files\Dell\SysMgt. Restart the DSM SA Event Manager service to
enable the setting. The Server Administrator Unicode text event log file is named dcsys32.log and is
located in the <install_path>\omsa\log directory.
•On systems running the Red Hat Enterprise Linux, SUSE Linux Enterprise Server, Citrix XenServer and
VMware ESX operating systems, you can locate the configuration file in the /opt/dell/srvadmin/etc/
srvadmin-deng/ini directory and set the property UnitextLog.enabled=true. Run the /etc/init.d/
dataeng restart command to restart the Server Administrator Event Manager service and enable the
setting. This also restarts the Server Administrator Data Manager and SNMP services. The Server
Administrator Unicode text event log file is named dcsys <xx>.log where xx is 32 or 64 bit depending
on the operating system and is located in the /opt/dell/srvadmin/var/log/ openmanage directory.
•On systems running the in ESXi operating system the dcemdy32.ini file is located under /etc/cim/dell/srvadmin/srvadmin-deng/ini/ and the dcsys <xx>.log where xx is 32 or 64 bit depending on the
operating system and is located under /etc/cim/dell/srvadmin/log/openmanage/
The following sub-sections explain how to launch the Windows Server 2008, Red Hat Enterprise Linux,
SUSE Linux Enterprise Server, VMware ESX, and VMware ESXi event viewers.
21
Viewing Events in Microsoft Windows Server 2008
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 also look up the dcsys <xx>.xml file, in the <install_path> \omsa\log directory,
to view the separate event log file, where the default install_path is C:\Program Files\Dell
\SysMgt and xx is 32 or 64 depending on the operating system that is installed.
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.
The following example shows the Red Hat Enterprise Linux and SUSE Linux Enterprise Server message
log, /var/log/messages. The text in boldface type indicates the message text.
NOTE: These messages are typically displayed as one long line. In the following example, the
message is displayed using line breaks to help you see the message text more clearly.
Feb 6 14:20:51 server01 Server Administrator: Instrumentation Service EventID:
1000
Server Administrator starting
Feb 6 14:20:51 server01 Server Administrator: Instrumentation Service EventID:
1001
Server Administrator startup complete
Feb 6 14:21:21 server01 Server Administrator: Instrumentation Service EventID:
1254Chassis 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:
1252Chassis 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 ESX/ESXi
1.Log in to the system running VMware ESX/ESXi with VMware vSphere Client.
2.Click View → Administration → System Logs.
3.Select Server Log → /var/log/messages entry from the drop-down list.
Viewing the Event Information
The event log for each operating system contains some or all of the following information:
•Date — The date the event occurred.
22
•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 below lists in alphabetical order each line item that may appear in the event description.
Description
Line Item
ExplanationSpecifies the action that was performed, for example: Action performed was:
Description
Line Item
ExplanationSpecifies the action that was requested, for example: Action requested was:
Description
Line Item
ExplanationSpecifies additional details available for the hot plug event, for example: Memory
Description
Line Item
ExplanationSpecifies information pertaining to the event, for example: Power supply input
Description
Line Item
Action performed was: <Action>
Power cycle
Action requested was: <Action>
Reboot, shutdown OS first
Additional Details: <Additional details for the event>
device: DIMM1_A Serial number: FFFF30B1
<Additional power supply status information>
AC is off, Power supply POK (power OK) signal is not normal,
Power supply is turned off
Chassis intrusion state: <Intrusion state>
ExplanationSpecifies whether the chassis intrusion state is Open or Closed. For example:
Chassis intrusion state: Open
Description
Line Item
ExplanationSpecifies name of the chassis that generated the message, for example: Chassis
Description
Line Item
Chassis location: <Name of chassis>
location: Main System Chassis
Configuration error type: <type of configuration error>
23
ExplanationSpecifies the type of configuration error that occurred, for example:
Configuration error type: Revision mismatch
Description
Line Item
ExplanationSpecifies the current sensor value in amps, for example: Current sensor value
Description
Line Item
ExplanationSpecifies the date and time the action was performed, for example: Date and
Description
Line Item
ExplanationSpecifies the location of the device in the specified chassis, for example: Device
Description
Line Item
ExplanationSpecifies the state of the current sensor, for example: Discrete current
Description
Line Item
Current sensor value (in Amps): <Reading>
(in Amps): 7.853
Date and time of action: <Date and time>
time of action: Sat Jun 12 16:20:33 2004
Device location: <Location in chassis>
location: Memory Card A
Discrete current state: <State>
state: Good
Discrete temperature state: <State>
ExplanationSpecifies the state of the temperature sensor, for example: Discrete
temperature state: Good
Description
Line Item
ExplanationSpecifies the state of the voltage sensor, for example: Discrete voltage
Description
Line Item
ExplanationSpecifies the fan speed in revolutions per minute (RPM) or On/Off, for example:
Description
Line Item
ExplanationSpecifies the type of hardware log, for example: Log type: ESM
Description
Line Item
Discrete voltage state: <State>
state: Good
Fan sensor value: <Reading>
Fan sensor value (in RPM): 2600
Fan sensor value: Off
Log type: <Log type>
Memory device bank location: <Bank name in chassis>
24
ExplanationSpecifies the name of the memory bank in the system that generated the message,
for example: Memory device bank location: Bank_1
Description
Line Item
ExplanationSpecifies the location of the memory module in the chassis, for example: Memory
Description
Line Item
ExplanationSpecifies the number of power supply or cooling devices required to achieve full
Description
Line Item
ExplanationSpecifies the peak value in Watts, for example: Peak value (in Watts):
Description
Line Item
ExplanationSpecifies a list of possible causes for the memory module event, for example:
Memory device location: <Device name in chassis>
device location: DIMM_A
Number of devices required for full redundancy: <Number>
redundancy, for example: Number of devices required for full
redundancy: 4
Peak value (in Watts):<Reading>
1.693
Possible memory module event cause: <list of causes>
Possible memory module event cause:
Single bit warning error rate exceeded
Single bit error logging disabled
Description
Line Item
ExplanationSpecifies the type of power supply, for example: Power Supply type: VRM
Description
Line Item
ExplanationSpecifies the status of the previous redundancy message, for example: Previous
Description
Line Item
ExplanationSpecifies the previous state of the sensor, for example: Previous state was:
Description
Line Item
ExplanationSpecifies the status of the processor sensor, for example: Processor sensor
Power Supply type: <type of power supply>
Previous redundancy state was: <State>
redundancy state was: Lost
Previous state was:<State>
OK (Normal)
Processor sensor status: <status>
status: Configuration error
25
Description
Line Item
ExplanationSpecifies the location of the redundant power supply or cooling unit in the chassis,
Redundancy unit: <Redundancy location in chassis>
for example: Redundancy unit: Fan Enclosure
Description
Line Item
ExplanationSpecifies the type of SD card device, for example: SD card device type:
Description
Line Item
ExplanationSpecifies the state of the SD card, for example: SD card state: Present,
Description
Line Item
ExplanationSpecifies the location of the sensor in the specified chassis, for example: Sensor
Description
Line Item
ExplanationSpecifies the temperature in degrees Celsius, for example: Temperature sensor
Description
Line Item
SD card device type: <Type of SD card device>
Hypervisor
SD card state: <State of SD card>
Active
Sensor location: <Location in chassis>
location: CPU1
Temperature sensor value: <Reading>
value (in degrees Celsius): 30
Voltage sensor value (in Volts):<Reading>
ExplanationSpecifies the voltage sensor value in volts, for example: Voltage sensor value
(in Volts): 1.693
26
2
Server Management Messages
The following tables lists in numerical order each event ID and its corresponding description, along with
its severity and cause.
NOTE: For corrective actions, see the appropriate documentation.
Server Administrator General Messages
The messages below indicate that certain alert systems are up and working.
Event ID — 0000
Description
SeverityInformation
CauseUser cleared the log from Server Administrator.
Log was cleared
This operation does not clear the operating system event log. Therefore, this event
is not logged in the operating system event log. This is logged in the System
Administrator alert log.
Event ID — 0001
Description
SeverityInformation
CauseThe log was full, copied to backup, and cleared.
Log backup created
Event ID — 1000
Description
SeverityInformation
CauseServer Administrator is beginning to initialize.
CauseThe user has chosen to update the flash basic input/output system (BIOS).
A system BIOS update has been scheduled for the next reboot
Event ID – 1003
Description
SeverityInformation
CauseThe user decides to cancel the flash BIOS update, or an error occurs during the
A previously scheduled system BIOS update has been canceled
flash.
Event ID — 1004
Description
SeverityError
CauseThis message is generated when a system is configured for thermal shutdown due
Thermal shutdown protection has been initiated
to an error event. If a temperature sensor reading exceeds the error threshold for
which the system is configured, the operating system shuts down and the system
powers off. This event may also be initiated on certain systems when a fan
enclosure is removed from the system for an extended period of time.
Event ID — 1005
Description
SeverityError
CauseThe system does not contain the required systems management BIOS version 2.2
SMBIOS data is absent
or higher, or the BIOS is corrupted.
Event ID — 1006
Description
SeverityError
CauseThis message is generated when an automatic system recovery action is performed
Automatic System Recovery (ASR) action was performed Action
performed was: <Action>
Date and time of action:<Date and time>
due to a hung operating system. The action performed and the time of action is
provided.
28
Event ID — 1007
Description
SeverityInformation
CauseUser requested a host system control action to reboot, power off, or power cycle
User initiated host system control action Action requested was:
<Action>
the system. Alternatively, the user had indicated protective measures to be initiated
in the event of a thermal shutdown.
Event ID — 1008
Description
SeverityInformation
CauseSystems Management Data Manager services were started.
Systems Management Data Manager Started
Event ID — 1009
Description
SeverityInformation
CauseSystems Management Data Manager services were stopped.
Systems Management Data Manager Stopped
Event ID — 1011
Description
SeverityError
CauseThis message is generated when the BIOS Remote Configuration Interface (RCI)
RCI table is corrupt
table is corrupted or cannot be read by the systems management software.
Event ID — 1012
Description
SeverityInformation
Cause
IPMI Status Interface: <the IPMI interface being used>,
<additional information if available and applicable >
This message is generated to indicate the Intelligent Platform Management
Interface (IPMI) status of the system.
Additional information, when available, includes Baseboard Management
Controller (BMC) not present, BMC not responding, System Event Log (SEL) not
present, and SEL Data Record (SDR) not present.
29
Event ID — 1013
Description
SeverityInformation
CauseThe system peak power sensor detected a new peak value in power consumption.
System Peak Power detected new peak value Peak value (in
Watts): <Reading>
The new peak value in Watts is provided.
Event ID — 1014
Description
SeverityWarning
CauseThis event is generated when the systems management agent detects a critical
System software event: <Description>
Date and time of action: <Date and time>
system software generated event in the system event log which could have been
resolved.
Event ID — 1015
Description
SeverityInformation
CauseThis event is generated when the server-based management mode is enabled.
Server Based Management Mode is enabled
Event ID — 1016
Description
SeverityInformation
CauseThis event is generated when the server-based management mode is disabled.
Server Based Management Mode is disabled
Temperature Sensor Messages
The temperature sensors listed help protect critical components by alerting the systems management
console when temperatures become too high inside a chassis. The temperature sensor messages use
more variables: sensor location, chassis location, previous state, and temperature sensor value or state.
Event ID — 1050
Description
30
Temperature sensor has failed Sensor location: <Location in
chassis>
Chassis location: <Name of chassis>
Previous state was: <State>
If sensor type is not discrete:
Temperature sensor value (in degrees Celsius): <Reading>
If sensor type is discrete:
Discrete temperature state: <State>
SeverityError
CauseA 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.
Event ID — 1051
Description
SeverityWarning
CauseA temperature sensor on the backplane board, system board, or drive carrier in the
Temperature sensor value unknown Sensor location: <Location in
chassis>
Chassis location: <Name of chassis>
If sensor type is not discrete:
Temperature sensor value (in degrees Celsius): <Reading>
If sensor type is discrete:
Discrete temperature state: <State>
specified system could not obtain a reading. The sensor location, chassis location,
previous state, and a nominal temperature sensor value information is provided.
Event ID — 1052
Description
Temperature sensor returned to a normal value Sensor location:
<Location in chassis>
Chassis location: <Name of chassis>
Previous state was: <State>
If sensor type is not discrete:
Temperature sensor value (in degrees Celsius): <Reading>
If sensor type is discrete:
Discrete temperature state: <State>
SeverityInformation
CauseA temperature sensor on the backplane board, system board, or drive carrier in the
specified system returned to a valid range after crossing a failure threshold. The
sensor location, chassis location, previous state, and temperature sensor value are
provided.
Event ID — 1053
Description
Temperature sensor detected a warning value Sensor location:
<Location in chassis>
Chassis location: <Name of chassis>
31
Previous state was: <State>
If sensor type is not discrete:
Temperature sensor value (in degrees Celsius): <Reading>
If sensor type is discrete:
Discrete temperature state: <State>
SeverityWarning
CauseA 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 ID — 1054
Description
SeverityError
CauseA temperature sensor on the backplane board, system board, or drive carrier in the
Temperature sensor detected a failure value Sensor location:
<Location in chassis>
Chassis location: <Name of chassis>
Previous state was: <State>
If sensor type is not discrete:
Temperature sensor value (in degrees Celsius): <Reading>
If sensor type is discrete:
Discrete temperature state: <State>
specified system exceeded its failure threshold. The sensor location, chassis
location, previous state, and temperature sensor value are provided.
Event ID — 1055
Description
Temperature sensor detected a non-recoverable value Sensor
location: <Location in chassis>
Chassis location: <Name of chassis>
Previous state was: <State>
If sensor type is not discrete:
Temperature sensor value (in degrees Celsius): <Reading>
If sensor type is discrete:
Discrete temperature state: <State>
SeverityError
CauseA temperature sensor on the backplane board, system board, or drive carrier in the
specified system detected an error from which it cannot recover. The sensor
location, chassis location, previous state, and temperature sensor value information
is provided.
32
Cooling Device Messages
The cooling device sensors listed monitor how well a fan is functioning. Cooling device messages
provide status and warning information for fans in a particular chassis.
Event ID — 1100
Description
SeverityError
CauseA fan sensor in the specified system is not functioning. The sensor location, chassis
Fan sensor has failed Sensor location: <Location in chassis>
Chassis location: <Name of chassis>
Previous state was: <State>
Fan sensor value: <Reading>
location, previous state, and fan sensor value information is provided.
Event ID — 1101
Description
SeverityError
CauseA fan sensor in the specified system could not obtain a reading. The sensor
Fan sensor value unknown Sensor location: <Location in chassis>
Chassis location: <Name of chassis>
Previous state was: <State>
Fan sensor value: <Reading>
location, chassis location, previous state, and a nominal fan sensor value
information is provided.
Event ID — 1102
Description
SeverityInformation
CauseA fan sensor reading on the specified system returned to a valid range after
Fan sensor returned to a normal value Sensor location:
<Location in chassis>
Chassis location: <Name of chassis>
Previous state was: <State>
Fan sensor value: <Reading>
crossing a warning threshold. The sensor location, chassis location, previous state,
and fan sensor value information is provided.
Event ID — 1103
Description
Fan sensor detected a warning value Sensor location: <Location
in chassis>
33
Chassis location: <Name of chassis>
Previous state was: <State>
Fan sensor value: <Reading>
SeverityWarning
CauseA fan sensor reading in the specified system exceeded a warning threshold. The
sensor location, chassis location, previous state, and fan sensor value information is
provided.
Event ID — 1104
Description
SeverityError
CauseA fan sensor in the specified system detected the failure of one or more fans. The
Fan sensor detected a failure value Sensor location: <Location
in chassis>
Chassis location: <Name of chassis>
Previous state was: <State>
Fan sensor value: <Reading>
sensor location, chassis location, previous state, and fan sensor value information is
provided.
Event ID — 1105
Description
SeverityError
CauseA fan sensor detected an error from which it cannot recover. The sensor location,
Fan sensor detected a non-recoverable value Sensor location:
<Location in chassis>
Chassis location: <Name of chassis>
Previous state was: <State>
Fan sensor value: <Reading>
chassis location, previous state, and fan sensor value information is provided.
Voltage Sensor Messages
The voltage sensors listed monitor the number of volts across critical components. Voltage sensor
messages provide status and warning information for voltage sensors in a particular chassis.
Event ID — 1150
Description
34
Voltage sensor has failed Sensor location: <Location in
chassis>
Chassis location: <Name of chassis>
Previous state was: <State>
If sensor type is not discrete:
Voltage sensor value (in Volts): <Reading>
If sensor type is discrete:
Discrete voltage state: <State>
SeverityError
CauseA voltage sensor in the specified system failed. The sensor location, chassis
location, previous state, and voltage sensor value information is provided.
Event ID — 1151
Description
SeverityWarning
CauseA voltage sensor in the specified system could not obtain a reading. The sensor
Voltage sensor value unknown Sensor location: <Location in
chassis>
Chassis location: <Name of chassis>
Previous state was: <State>
If sensor type is not discrete:
Voltage sensor value (in Volts): <Reading>
If sensor type is discrete:
Discrete voltage state: <State>
location, chassis location, previous state, and a nominal voltage sensor value are
provided.
Event ID — 1152
Description
Voltage sensor returned to a normal value Sensor location:
<Location in chassis>
Chassis location: <Name of chassis>
Previous state was: <State>
If sensor type is not discrete:
Voltage sensor value (in Volts): <Reading>
If sensor type is discrete:
Discrete voltage state: <State>
SeverityInformation
CauseA 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 information is provided.
Event ID — 1153
Description
Voltage sensor detected a warning value Sensor location:
<Location in chassis>
Chassis location: <Name of chassis>
35
Previous state was: <State>
If sensor type is not discrete:
Voltage sensor value (in Volts): <Reading>
If sensor type is discrete:
Discrete voltage state: <State>
SeverityWarning
CauseA voltage sensor in the specified system exceeded its warning threshold. The
sensor location, chassis location, previous state, and voltage sensor value
information is provided.
Event ID — 1154
Description
SeverityError
CauseA voltage sensor in the specified system exceeded its failure threshold. The sensor
Voltage sensor detected a failure value Sensor location:
<Location in chassis>
Chassis location: <Name of chassis>
Previous state was: <State>
If sensor type is not discrete:
Voltage sensor value (in Volts): <Reading>
If sensor type is discrete:
Discrete voltage state: <State>
location, chassis location, previous state, and voltage sensor value information is
provided.
Event ID — 1155
Description
Voltage sensor detected a non-recoverable value Sensor
location: <Location in chassis>
Chassis location: <Name of chassis>
Previous state was: <State>
If sensor type is not discrete:
Voltage sensor value (in Volts): <Reading>
If sensor type is discrete:
Discrete voltage state: <State>
SeverityError
CauseA 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 information is provided.
36
Current Sensor Messages
The current sensors listed 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.
Event ID – 1200
Description
SeverityError
CauseA current sensor in the specified system failed. The sensor location, chassis
Current sensor has failed Sensor location: <Location in
chassis>
Chassis location: <Name of chassis>
Previous state was: <State>
If sensor type is not discrete:
Current sensor value (in Amps): <Reading> OR
Current sensor value (in Watts): <Reading>
If sensor type is discrete:
Discrete voltage state: <State>
location, previous state, and current sensor value are provided.
Event ID — 1201
Description
Current sensor value unknown Sensor location: <Location in
chassis>
Chassis location: <Name of chassis>
Previous state was: <State>
If sensor type is not discrete:
Current sensor value (in Amps): <Reading> OR
Current sensor value (in Watts): <Reading>
If sensor type is discrete:
Discrete voltage state: <State>
SeverityWarning
CauseA current sensor in the specified system could not obtain a reading. The sensor
location, chassis location, previous state, and a nominal current sensor value
information is provided.
Event ID — 1202
Description
Current sensor returned to a normal value Sensor location:
<Location in chassis>
Chassis location: <Name of chassis>
37
Previous state was: <State>
If sensor type is not discrete:
Current sensor value (in Amps): <Reading> OR
Current sensor value (in Watts): <Reading>
If sensor type is discrete:
Discrete voltage state: <State>
SeverityInformation
CauseA current sensor in the specified system returned to a valid range after crossing a
failure threshold. The sensor location, chassis location, previous state, and current
sensor value information is provided.
Event ID — 1203
Description
SeverityWarning
CauseA current sensor in the specified system exceeded its warning threshold. The
Current sensor detected a warning value Sensor location:
<Location in chassis>
Chassis location: <Name of chassis>
Previous state was: <State>
If sensor type is not discrete:
Current sensor value (in Amps): <Reading> OR
Current sensor value (in Watts): <Reading>
If sensor type is discrete:
Discrete voltage state: <State>
sensor location, chassis location, previous state, and current sensor value are
provided.
Event ID — 1204
Description
Current sensor detected a failure value Sensor location:
<Location in chassis>
Chassis location: <Name of chassis>
Previous state was: <State>
If sensor type is not discrete:
Current sensor value (in Amps): <Reading> OR
Current sensor value (in Watts): <Reading>
If sensor type is discrete:
Discrete voltage state: <State>
SeverityError
38
CauseA current sensor in the specified system exceeded its failure threshold. The sensor
location, chassis location, previous state, and current sensor value are provided.
Event ID — 1205
Description
SeverityError
CauseA current sensor in the specified system detected an error from which it cannot
Current sensor detected a non-recoverable value Sensor
location: <Location in chassis>
Chassis location: <Name of chassis>
Previous state was: <State>
If sensor type is not discrete:
Current sensor value (in Amps): <Reading> OR
Current sensor value (in Watts): <Reading>
If sensor type is discrete:
Discrete voltage state: <State>
recover. The sensor location, chassis location, previous state, and current sensor
value are provided.
Chassis Intrusion Messages
The chassis intrusion messages listed 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.
Event ID — 1251
Description
SeverityWarning
CauseA chassis intrusion sensor in the specified system could not obtain a reading. The
Chassis intrusion sensor value unknown Sensor location:
<Location in chassis>
Chassis location: <Name of chassis>
Previous state was: <State>
Chassis intrusion state: <Intrusion state>
sensor location, chassis location, previous state, and chassis intrusion state are
provided.
Event ID — 1252
Description
Chassis intrusion returned to normal Sensor location: <Location
in chassis>
Chassis location: <Name of chassis>
Previous state was: <State>
39
Chassis intrusion state: <Intrusion state>
SeverityInformation
CauseA 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 information is
provided.
Event ID — 1254
Description
SeverityCritical
CauseA chassis intrusion sensor in the specified system detected that the system cover
Chassis intrusion detected Sensor location: <Location in
chassis>
Chassis location: <Name of chassis>
Previous state was: <State>
Chassis intrusion state: <Intrusion state>
was opened while the system was operating. The sensor location, chassis location,
previous state, and chassis intrusion state information is provided.
Redundancy Unit Messages
Redundancy means that a system chassis has more than one of certain critical components. Fans and
power supplies, for example, are so important for preventing damage or disruption of a computer system
that a chassis may have “extra” fans or power supplies installed. Redundancy allows a second or nth fan
to keep the chassis components at a safe temperature when the primary fan has failed. Redundancy is
normal when the intended number of critical components are operating. Redundancy is degraded when
a component fails but others are still operating. Redundancy is lost when the number of components
functioning falls below the redundancy threshold. 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.
Event ID — 1300
Description
SeverityError
CauseA redundancy sensor in the specified system failed. The redundancy unit location,
40
Redundancy sensor has failed Redundancy unit: <Redundancy
Location in chassis>
Chassis location: <Name of chassis>
Previous redundancy state was: <State>
chassis location, previous redundancy state, and the number of devices required
for full redundancy are provided.
Event ID — 1301
Description
SeverityWarning
CauseA redundancy sensor in the specified system could not obtain a reading. The
Redundancy sensor value unknown Redundancy unit: <Redundancy
Location in chassis>
Chassis location: <Name of chassis>
Previous redundancy state was: <State>
redundancy unit location, chassis location, previous redundancy state, and the
number of devices required for full redundancy are provided.
Event ID — 1302
Description
SeverityInformation
CauseA redundancy sensor in the specified system detected that a unit was not
Redundancy not applicable Redundancy unit: <Redundancy Location
in chassis>
Chassis location: <Name of chassis>
Previous redundancy state was: <State>
redundant. The redundancy location, chassis location, previous redundancy state,
and the number of devices required for full redundancy information is provided.
Event ID — 1303
Description
SeverityInformation
CauseA redundancy sensor in the specified system detected that a redundant unit is
Redundancy is offline Redundancy unit: <Redundancy Location in
chassis>
Chassis location: <Name of chassis>
Previous redundancy state was: <State>
offline. The redundancy unit location, chassis location, previous redundancy state,
and the number of devices required for full redundancy information is provided.
Event ID — 1304
Description
SeverityInformation
CauseA redundancy sensor in the specified system detected that a “lost” redundancy
Redundancy regained Redundancy unit: <Redundancy Location in
chassis>
Chassis location: <Name of chassis>
Previous redundancy state was: <State>
device has been reconnected or replaced; full redundancy is in effect. The
41
Event ID — 1305
redundancy unit location, chassis location, previous redundancy state, and the
number of devices required for full redundancy information is provided.
Description
SeverityWarning
CauseA redundancy sensor in the specified system detected that one of the components
Redundancy degraded Redundancy unit: <Redundancy Location in
chassis>
Chassis location: <Name of chassis>
Previous redundancy state was: <State>
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 information is provided.
Event ID — 1306
Description
SeverityError
CauseA redundancy sensor in the specified system detected that one of the components
Redundancy lost Redundancy unit: <Redundancy Location in
chassis>
Chassis location: <Name of chassis>
Previous redundancy state was: <State>
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.
Power Supply Messages
The power supply sensors monitor how well a power supply is functioning. The power supply messages
listed provides status and warning information for power supplies present in a particular chassis.
Event ID — 1351
Description
SeverityWarning
42
Power supply sensor value unknown Sensor Location: <Location in
chassis>
Chassis location: <Name of chassis>
Previous redundancy state was: <State>
Power Supply type: <type of power supply>
<Additional power supply status information>
If in configuration error state:
Configuration error type:<type of configuration error>
CauseA power supply sensor in the specified system could not obtain a reading. The
sensor location, chassis location, previous state, power supply type, additional
power supply status, and configuration error type information are provided.
Event ID — 1352
Description
SeverityInformation
CauseA power supply has been reconnected or replaced. The sensor location, chassis
Power supply returned to normal Sensor Location: <Location in
chassis>
Chassis location: <Name of chassis>
Previous redundancy state was: <State>
Power Supply type: <type of power supply>
<Additional power supply status information>
If in configuration error state:
Configuration error type:<type of configuration error>
location, previous state, power supply type, additional power supply status, and
configuration error type information are provided.
Event ID — 1353
Description
Power supply detected a warning Sensor Location: <Location in
chassis>
Chassis location: <Name of chassis>
Previous redundancy state was: <State>
Power Supply type: <type of power supply>
<Additional power supply status information>
If in configuration error state:
Configuration error type:<type of configuration error>
SeverityWarning
CauseA power supply sensor reading in the specified system exceeded a user-definable
warning threshold. The sensor location, chassis location, previous state, power
supply type, additional power supply status, and configuration error type
information are provided.
Event ID — 1354
Description
Power supply detected a failure Sensor Location: <Location in
chassis>
Chassis location: <Name of chassis>
Previous redundancy state was: <State>
Power Supply type: <type of power supply>
<Additional power supply status information>
43
If in configuration error state:
Configuration error type:<type of configuration error>
SeverityError
CauseA power supply has been disconnected or has failed. The sensor location, chassis
location, previous state, power supply type, additional power supply status, and
configuration error type information are provided.
Memory Device Messages
The memory device messages listed provides 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.
NOTE: The <status> can be either critical or non-critical.
Event ID — 1400
Description
SeverityInformational
CauseMemory device monitoring has been disabled. The memory module may not be
Memory device status is <status>
Memory device location: <location in chassis>
Possible memory module event cause: <list of causes>
correctly seated, wrongly configured, or has failed.
Event ID — 1401
Description
SeverityInformational
CauseMemory device status is unknown. The memory module may not be correctly
Memory device status is <status>
Memory device location: <location in chassis>
Possible memory module event cause: <list of causes>
seated, wrongly configured, or has failed.
Event ID — 1402
Description
Memory device status is <status>
Memory device location: <location in chassis>
Possible memory module event cause: <list of causes>
SeverityInformational
44
CauseMemory device status is normal. The memory device identified in the message has
returned to a normal state.
Event ID — 1403
Description
SeverityWarning
CauseA memory device correction rate exceeded an acceptable value. The memory
Memory device status is <status>
Memory device location: <location in chassis>
Possible memory module event cause: <list of causes>
device status and possible memory module event cause information is provided.
Event ID — 1404
Description
SeverityError
CauseA memory device correction rate exceeded an acceptable value, a memory spare
Memory device status is <status>
Memory device location: <location in chassis>
Possible memory module event cause: <list of causes>
bank was activated, or a multi-bit ECC error occurred. The system continues to
function normally (except for a multi-bit error). Replace the memory module
identified in the message during the system’s next scheduled maintenance. Clear
the memory error on multi-bit ECC error. The memory device status and possible
memory module event cause information is provided.
Event ID — 1405
Description
SeverityInformational
CauseMemory device status is nonrecoverable. The memory module failed because of an
Memory device status is <status>
Memory device location: <location in chassis>
Possible memory module event cause: <list of causes>
irrecoverable error.
Hardware Log Sensor Messages
The 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 provides status and warning information about the noncircular logs
that may fill up, resulting in lost status messages.
45
Event ID — 1550
Description
SeverityWarning
CauseA hardware log sensor in the specified system is disabled. The log type information
Log monitoring has been disabled
Log type: <Log type>
is provided.
Event ID — 1551
Description
SeverityInformation
CauseA hardware log sensor in the specified system could not obtain a reading. The log
Log status is unknown
Log type: <Log type>
type information is provided.
Event ID — 1552
Description
SeverityInformation
Log size is no longer near or at capacity
Log type: <Log type>
CauseThe hardware log on the specified system is no longer near or at its capacity,
usually as the result of clearing the log. The log type information is provided.
Event ID — 1553
Description
SeverityWarning
CauseThe size of a hardware log on the specified system is near or at the capacity of the
Log size is near capacity
Log type: <Log type>
hardware log. The log type information is provided.
Event ID — 1554
Description
SeverityError
CauseThe size of a hardware log on the specified system is full. The log type information
Log status is full
Log type: <Log type>
is provided.
46
Event ID — 1555
Description
SeverityError
CauseA hardware log sensor in the specified system failed. The hardware log status
Log sensor has failed
Log type: <Log type>
cannot be monitored. The log type information is provided.
Processor Sensor Messages
The processor sensors monitor how well a processor is functioning. Processor messages listed provides
status and warning information for processors in a particular chassis.
Event ID — 1601
Description
SeverityWarning
CauseA processor sensor in the specified system could not obtain a reading. The sensor
Processor sensor value unknown Sensor Location: <Location in
chassis>
Chassis Location: <Name of chassis>
Previous state was: <State>
Processor sensor status: <status>
location, chassis location, previous state and processor sensor status information is
provided.
Event ID — 1602
Description
SeverityInformation
CauseA processor sensor in the specified system transitioned back to a normal state. The
Processor sensor returned to a normal value Sensor Location:
<Location in chassis>
Chassis Location: <Name of chassis>
Previous state was: <State>
Processor sensor status: <status>
sensor location, chassis location, previous state and processor sensor status are
provided.
Event ID — 1603
Description
Processor sensor detected a warning value Sensor Location:
<Location in chassis>
Chassis Location: <Name of chassis>
47
Previous state was: <State>
Processor sensor status: <status>
SeverityWarning
CauseA processor sensor in the specified system is in a throttled state. The sensor
location, chassis location, previous state and processor sensor status information is
provided.
Event ID — 1604
Description
SeverityError
CauseA processor sensor in the specified system is disabled, has a configuration error, or
Processor sensor detected a failure value Sensor Location:
<Location in chassis>
Chassis Location: <Name of chassis>
Previous state was: <State>
Processor sensor status: <status>
experienced a thermal trip. The sensor location, chassis location, previous state and
processor sensor status are provided.
Pluggable Device Messages
The pluggable device messages listed provides status and error information when some devices, such as
memory cards, are added or removed.
Event ID — 1650
Description
Device plug event type unknown Device location: <Location in
chassis, if available>
Chassis Location: <Name of chassis, if available>
Additional details: <Additional details for the events, if
available>
SeverityInformation
CauseA pluggable device event message of unknown type was received. The device
location, chassis location, and additional event details, if available, are provided.
Event ID — 1651
Description
SeverityInformation
48
Device added to system Device location: <Location in chassis>
Chassis Location: <Name of chassis>
Additional details: <Additional details for the events>
CauseA device was added in the specified system. The device location, chassis location,
and additional event details, if available, are provided.
Event ID — 1652
Description
SeverityInformation
CauseA device was removed from the specified system. The device location, chassis
Device removed from system Device location: <Location in
chassis>
Chassis Location: <Name of chassis>
Additional details: <Additional details for the events>
location, and additional event details, if available, are provided.
Event ID — 1653
Description
SeverityError
CauseA configuration error was detected for a pluggable device in the specified system.
Device configuration error detected Device location: <Location
in chassis>
Chassis Location: <Name of chassis>
Additional details: <Additional details for the events>
The device may have been added to the system incorrectly.
Battery Sensor Messages
The battery sensors monitor how well a battery is functioning. The battery messages listed provides status
and warning information for batteries in a particular chassis.
Event ID — 1700
Description
SeverityCritical/ Failure/Error
CauseA battery sensor in the specified system is not functioning. The sensor location,
Battery sensor has failed Sensor location: <Location in
chassis>
Chassis Location: <Name of chassis>
Previous state was: <State>
Battery sensor status: <status>
chassis location, previous state, and battery sensor status information is provided.
Event ID — 1701
Description
Battery sensor value unknown Sensor location: <Location in
chassis>
49
Chassis Location: <Name of chassis>
Previous state was: <State>
Battery sensor status: <status>
SeverityWarning
CauseA battery sensor in the specified system could not retrieve a reading. The sensor
location, chassis location, previous state, and battery sensor status information is
provided.
Event ID — 1702
Description
SeverityInformation
CauseA battery sensor in the specified system detected that a battery transitioned back to
Battery sensor returned to a normal value Sensor location:
<Location in chassis>
Chassis Location: <Name of chassis>
Previous state was: <State>
Battery sensor status: <status>
a normal state. The sensor location, chassis location, previous state, and battery
sensor status information is provided.
Event ID — 1703
Description
SeverityWarning
CauseA battery sensor in the specified system detected that a battery is in a predictive
Battery sensor detected a warning value Sensor location:
<Location in chassis>
Chassis Location: <Name of chassis>
Previous state was: <State>
Battery sensor status: <status>
failure state. The sensor location, chassis location, previous state, and battery
sensor status information is provided.
Event ID — 1704
Description
SeverityError
50
Battery sensor detected a failure value Sensor location:
<Location in chassis>
Chassis Location: <Name of chassis>
Previous state was: <State>
Battery sensor status: <status>
CauseA battery sensor in the specified system detected that a battery has failed. The
sensor location, chassis location, previous state, and battery sensor status
information is provided.
Event ID — 1705
Description
SeverityError
CauseA battery sensor in the specified system could not retrieve a value. The sensor
Battery sensor detected a non-recoverable value Sensor
location: <Location in chassis>
Chassis Location: <Name of chassis>
Previous state was: <State>
Battery sensor status: <status>
location, chassis location, previous state, and battery sensor status information is
provided.
Secure Digital (SD) Card Device Messages
The SD card device sensors monitor instrumented SD card devices in the system. The messages provide
the status and error information for SD card devices present in a chassis.
Event ID — 1750
Description
SD card device sensor has failed Sensor location: <Location in
chassis>
Chassis Location: <Name of chassis>
Previous state was: <State>
SD card device type: <Type of SD card device>
SD card state: <State of SD card>
SeverityError
CauseAn SD card device sensor in the specified system failed. The sensor location,
chassis location, previous state, and SD card device type information is provided.
The SD card state is provided if an SD card is present in the SD card device.
Event ID — 1751
Description
SD card device sensor value unknown Sensor location: <Location
in chassis>
Chassis Location: <Name of chassis>
Previous state was: <State>
SD card device type: <Type of SD card device>
SD card state: <State of SD card>
51
SeverityInformation
CauseAn SD card device sensor in the specified system could not obtain a reading. The
sensor location, chassis location, previous state, and SD card device type
information is provided. The SD card state is provided if an SD card is present in the
SD card device.
Event ID — 1752
Description
SeverityInformation
CauseAn SD card device sensor in the specified system detected that an SD card
SD card device returned to normal Sensor location: <Location in
chassis>
Chassis Location: <Name of chassis>
Previous state was: <State>
SD card device type: <Type of SD card device>
SD card state: <State of SD card>
transitioned back to a normal state. The sensor location, chassis location, previous
state, and SD card device type information is provided. The SD card state is
provided if an SD card is present in the SD card device.
Event ID — 1753
Description
SD card device detected a warning Sensor location: <Location in
chassis>
Chassis Location: <Name of chassis>
Previous state was: <State>
SD card device type: <Type of SD card device>
SD card state: <State of SD card>
SeverityWarning
CauseAn SD card device sensor in the specified system detected a warning condition.
The sensor location, chassis location, previous state, and SD card device type
information is provided. The SD card state is provided if an SD card is present in the
SD card device.
Event ID — 1754
Description
52
SD card device detected a failure Sensor location: <Location in
chassis>
Chassis Location: <Name of chassis>
Previous state was: <State>
SD card device type: <Type of SD card device>
SD card state: <State of SD card>
SeverityError
CauseAn SD card device sensor in the specified system detected an error. The sensor
location, chassis location, previous state, and SD card device type information is
provided. The SD card state is provided if an SD card is present in the SD card
device.
Event ID — 1755
Description
SeverityError
CauseAn SD card device sensor in the specified system detected an error from which it
SD card device sensor detected a non-recoverable value Sensor
location: <Location in chassis>
Chassis Location: <Name of chassis>
Previous state was: <State>
SD card device type: <Type of SD card device>
SD card state: <State of SD card>
cannot recover. The sensor location, chassis location, previous state, and SD card
device type information is provided. The SD card state is provided if an SD card is
present in the SD card device.
Chassis Management Controller Messages
The Alerts sent by M1000e Chassis Management Controller (CMC) 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.
Event ID — 2000
DescriptionCMC generated a test trap.
SeverityInformational
CauseA user-initiated test trap was issued, through the CMC GUI or RACADM CLI.
Event ID — 2002
DescriptionCMC reported a return-to-normal or informational event.
SeverityInformational
CauseCMC informational event, as described in the drsCAMessage variable binding
supplied with the alert.
53
Event ID — 2003
DescriptionCMC reported a warning.
SeverityWarning
CauseCMC warning event, as described in the drsCAMessage variable supplied with the
alert.
Event ID — 2004
DescriptionCMC reported a critical event.
SeverityCritical
CauseCMC critical event, as described in the drsCAMessage variable binding supplied
with the alert.
Event ID — 2005
DescriptionCMC reported a non-recoverable event.
SeverityNon-Recoverable
CauseCMC non-recoverable event, as described in the drsCAMessage variable binding
supplied with the alert.
54
3
Storage Management Message Reference
The 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 is 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 application log.
•Sends an SNMP trap if the operating system’s SNMP service is installed and enabled.
NOTE: 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 Server Administrator Storage Management Online Help for updated information.
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 userdefined names for virtual disks and other components. Each environment is unique in its storage
configuration and user-defined names. To receive an accurate alert message, that the Storage
Management service must 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.
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 symbol in the Storage Management documentation. An example of such an
alert is shown for alert 2334.
55
Table 3. Alert Message Format
Alert IDMessage Text Displayed in the Storage
Management Service Documentation
Message Text Displayed in the Alert Log
with Variable Information Supplied
2127Background Initialization startedBackground Initialization started: Virtual Disk
3 (Virtual Disk 3) Controller 1 (PERC 5/E
Adapter)
2334Controller 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 SCSI or 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.
NOTE: A, B, C and X, Y, Z in the following examples are variables representing the storage object
name or number.
Table 4. Message Format with Variables for Each Storage Object
Storage ObjectMessage Variables
Controller
Message Format: Controller A (Name)
Message Format: Controller A
For example, 2326 A foreign configuration has been detected: Controller 1
(PERC 5/E Adapter)
NOTE: The controller name is not always displayed.
Battery
SCSI Physical Disk
SAS Physical Disk
Virtual Disk
Enclosure
SCSI Power Supply
56
Message Format: Battery X Controller A
For example, 2174 The controller battery has been removed: Battery 0
Controller 1
Message Format: Physical Disk X:Y Controller A, Connector B
For example, 2049 Physical disk removed: Physical Disk 0:14 Controller 1,
Connector 0
Message Format: Physical Disk X:Y:Z Controller A, Connector B
For example, 2049 Physical disk removed: Physical Disk 0:0:14 Controller 1,
Connector 0
Message Format: Virtual Disk X (Name) Controller A (Name)
Message Format: Virtual Disk X Controller A
For 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.
Message Format: Enclosure X:Y Controller A, Connector B
For example, 2112 Enclosure shutdown: Enclosure 0:2 Controller 1,
Connector 0
Message Format: Power Supply X Controller A, Connector B, Target ID C
Storage ObjectMessage Variables
where "C" is the SCSI ID number of the enclosure management module
(EMM) managing the power supply.
For example, 2122 Redundancy degraded: Power Supply 1, Controller 1,
Connector 0, Target ID 6
SAS Power Supply
SCSI Temperature Probe
SAS Temperature Probe
SCSI Fan
SAS Fan
SCSI EMM
SAS EMM
Message Format: Power Supply X Controller A, Connector B, Enclosure C
For example, 2312 A power supply in the enclosure has an AC failure: Power
Supply 1, Controller 1, Connector 0, Enclosure 2
Message Format: Temperature Probe X Controller A, Connector B, Target ID
C
where C is the SCSI ID number of the EMM managing the temperature probe.
For example, 2101 Temperature dropped below the minimum warning
threshold: Temperature Probe 1, Controller 1, Connector 0, Target ID 6
Message Format: Temperature Probe X Controller A, Connector B, Enclosure
C
For example, 2101 Temperature dropped below the minimum warning
threshold: Temperature Probe 1, Controller 1, Connector 0, Enclosure 2
Message Format: Fan X Controller A, Connector B, Target ID C
where C is the SCSI ID number of the EMM managing the fan.
For example, 2121 Device returned to normal: Fan 1, Controller 1, Connector
0, Target ID 6
Message Format: Fan X Controller A, Connector B, Enclosure C
For example, 2121 Device returned to normal: Fan 1, Controller 1, Connector
0, Enclosure 2
Message Format: EMM X Controller A, Connector B, Target ID C
where C is the SCSI ID number of the EMM.
For example, 2121 Device returned to normal: EMM 1, Controller 1,
Connector 0, Target ID 6
Message Format: EMM X Controller A, Connector B, Enclosure C
For example, 2121 Device returned to normal: EMM 1, Controller 1,
Connector 0, Enclosure 2
Alert Descriptions and Corrective Actions
The following sections describe alerts generated by the RAID or SCSI controllers supported by Storage
Management. The alerts are displayed in the Server Administrator Alert tab or through Windows Event
Viewer. These alerts can also be forwarded as SNMP traps to other applications.
SNMP traps are generated for the alerts listed in the following sections. These traps are included in the
Server Administrator Storage Management, management information base (MIB). The SNMP traps for
these alerts use all of the SNMP trap variables. For more information on SNMP support and the MIB, see
the SNMP Reference Guide.
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.
57
Event ID — 2048
DescriptionDevice failed.
SeverityCritical / Failure / Error
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
Cause: A storage 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.
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.
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.
Action: If a physical disk was removed from the disk group, either replace the disk
or restore the original disk. On some controllers, 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.
Ensure that the enclosure is powered on. If the problem persists, check the
enclosure documentation for further diagnostic information.
Cause: A physical disk in the disk group is offline. The user may have manually put
the physical disk offline.
Action: Perform a rescan. You can also select the offline disk and perform a Make
Online operation.
Related Alert
Information
SNMP Trap
Numbers
Clear Alert Number: 2158
Related Alert Number: 2099, 2196
Local Response Agent (LRA) Number: 2070
903
Event ID — 2051
DescriptionPhysical disk degraded.
SeverityWarning / Non-critical
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
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 SMART Trip
(Predictive Failure).
Action: Replace the degraded physical disk. You can identify which disk is
degraded by locating the disk that has a Yellow Triangle for its status. Perform a
rescan after replacing the disk.
Clear Alert Number: None
Related Alert Number: 2094
Local Response Agent (LRA) Number: 2070
903
Event ID — 2052
DescriptionPhysical disk inserted.
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
Cause: This alert is for informational purposes.
Action: None
Clear Alert Number: None
Related Alert Number: 2065, 2305, 2367
Local Response Agent (LRA) Number: None
901
59
Event ID — 2053
DescriptionVirtual disk created.
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
Cause: This alert is for informational purposes.
Action: None
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: None
1201
Event ID — 2054
DescriptionVirtual disk deleted.
SeverityInformational
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
Cause: A virtual disk has been deleted. Performing a Reset Configuration may
detect that a virtual disk has been deleted.
Action: None
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: 2080
1201
Event ID — 2055
DescriptionVirtual disk configuration changed.
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
60
Cause: This alert is for informational purposes.
Action: None
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: None
1201
Event ID — 2056
DescriptionVirtual disk failed.
SeverityCritical / Failure / Error
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
Cause: One or more 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.
Action: Create a new virtual disk and restore from a backup.
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.
Action 1: Replace the failed drive. Rebuild of the virtual disk starts automatically.
Related Alert
Information
SNMP Trap
Numbers
NOTE: If you put the drive in a different slot, you need to assign it as a hot
spare for the rebuild to start automatically.
If you put the drive in a different slot, you need to assign it as a hot spare for the
rebuild to start automatically.
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.
DescriptionVirtual disk check consistency started.
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
Cause: This alert is for informational purposes.
Action: None
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: None
1201
Event ID — 2059
DescriptionVirtual disk format started.
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
Cause: This alert is for informational purposes.
Action: None
Clear Alert Number: 2086
Related Alert Number: None
Local Response Agent (LRA) Number: None
1201
Event ID — 2060
DescriptionCopy of data started from physical disk % 2 to physical disk % 1.
SeverityOK / Normal /Informational
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
62
Cause: This alert is for informational purposes.
Action: None
Clear Alert Number: None
Related Alert Number: 2075
Local Response Agent (LRA) Number: None
1201
Event ID — 2061
DescriptionVirtual disk initialization started.
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
Cause: This alert is for informational purposes.
Action: None
Clear Alert Number: 2088
Related Alert Number: None
Local Response Agent (LRA) Number: None
1201
Event ID — 2062
DescriptionPhysical disk initialization started.
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
Cause: This alert is for informational purposes.
Action: None
Clear Alert Number: 2089
Related Alert Number: None
Local Response Agent (LRA) Number: None
901
Event ID — 2063
DescriptionVirtual disk reconfiguration started.
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
Cause: This alert is for informational purposes.
Action: None
Clear Alert Number: 2090
Related Alert Number: None
Local Response Agent (LRA) Number: None
1201
63
Event ID — 2064
DescriptionVirtual disk rebuild started.
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
Cause: This alert is for informational purposes.
Action: None
Clear Alert Number: 2091
Related Alert Number: None
Local Response Agent (LRA) Number: None
1201
Event ID — 2065
DescriptionPhysical disk rebuild started.
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
Cause: This alert is for informational purposes.
Action: None
Clear Alert Number: 2092
Related Alert Number: 2099, 2121, 2196
Local Response Agent (LRA) Number: None
901
Event ID — 2067
DescriptionVirtual disk check consistency cancelled.
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
64
Cause: The check consistency operation was cancelled because a physical disk in
the array has failed or because a user cancelled the check consistency operation.
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. The consistency check can take a long time. The
time it takes depends on the size of the physical disk or the virtual disk.
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: None
SNMP Trap
Numbers
1201
Event ID — 2070
DescriptionVirtual disk initialization cancelled.
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
Cause: The virtual disk initialization cancelled because a physical disk included in
the virtual disk has failed or because a user cancelled the virtual disk initialization.
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.
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: None
1201
Event ID — 2074
DescriptionPhysical disk rebuild cancelled.
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
Cause: The user has cancelled the rebuild operation.
Action: Restart the rebuild operation.
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: None
SNMP Trap
Numbers
901
Event ID — 2075
DescriptionCopy of data completed from physical disk % 2 to physical disk % 1.
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
Cause: This alert is provided for informational purposes.
Action: None
Clear Alert Number: None
Related Alert Number: 2060
Local Response Agent (LRA) Number: None
65
SNMP Trap
Numbers
1201
Event ID — 2076
DescriptionVirtual disk Check Consistency failed.
SeverityCritical / Failure / Error
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
Cause: AA physical disk 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.
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.
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: 2081
1204
Event ID — 2077
DescriptionVirtual disk format failed.
SeverityCritical / Failure / Error
Cause and
Action
Related Alert
Information
Cause: A physical disk included in the virtual disk failed.
Action: Replace the failed physical disk. You can identify which physical disk 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.
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: 2081
SNMP Trap
Numbers
1204
Event ID — 2079
DescriptionVirtual disk initialization failed.
SeverityCritical / Failure / Error
Cause and
Action
66
Cause: A physical disk included in the virtual disk has failed or a user has cancelled
the initialization.
Action: If a physical disk has failed, then replace the physical disk
Related Alert
Information
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: 2081
SNMP Trap
Numbers
1204
Event ID — 2080
DescriptionPhysical disk initialization failed.
SeverityCritical / Failure / Error
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
Cause: The physical disk has failed or is not functioning.
Action: Replace the failed or non-functional disk. You can identify a disk that has
failed by locating the disk that has a red “X” for its status. Restart the initialization.
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: 2071
904
Event ID — 2081
DescriptionVirtual disk reconfiguration failed.
SeverityCritical / Failure / Error
Cause and
Action
Related Alert
Information
Hardware RAID:
Cause: A physical disk included in the virtual disk has failed or is not functioning. A
user may also have cancelled the reconfiguration.
Action: Replace the failed or non-functional disk. You can identify a disk that has
failed by locating the disk that displays a red X in the status field.
If the physical disk is part of a redundant array, then rebuild the physical disk. When
finished, restart the reconfiguration.
Software RAID:
•Perform a backup with the Verify option.
•If the file backup fails, try to restore the failed file from a previous backup.
•When the backup with the Verify option is complete without any errors, delete
the Virtual Disk.
•Recreate a new Virtual Disk with new drives.
•Restore the data from backup.
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: 2081
67
SNMP Trap
Numbers
1204
Event ID — 2082
DescriptionVirtual disk rebuild failed.
SeverityCritical / Failure / Error
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
Cause: A physical disk included in the virtual disk has failed or is not functioning. A
user may also have cancelled the rebuild.
Action: Replace the failed or non-functional 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.
Clear Alert Number: None
Related Alert Number: 2048
Local Response Agent (LRA) Number: 2081
1204
Event ID — 2083
DescriptionPhysical disk rebuild failed.
SeverityCritical / Failure / Error
Cause and
Action
Cause: A physical disk included in the virtual disk has failed or is not functioning. A
user may also have cancelled the rebuild.
Action: Replace the failed or non-functional 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.
Related Alert
Information
SNMP Trap
Numbers
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: 2071
904
Event ID — 2085
DescriptionVirtual disk check consistency completed.
SeverityOK / Normal / Informational
Cause and
Action
68
Cause: This alert is for informational purposes.
Action: None
Related Alert
Information
Clear Alert Number: Alert 2085 is a clear alert for alert 2058.
Related Alert Number: None
Local Response Agent (LRA) Number: None
SNMP Trap
Numbers
1201
Event ID — 2086
DescriptionVirtual disk format completed.
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
Cause: This alert is for informational purposes.
Action: None
Clear Alert Number: Alert 2086 is a clear alert for alert 2059.
Related Alert Number: None
Local Response Agent (LRA) Number: None
1201
Event ID — 2087
DescriptionCopy of data resumed from physical disk % 2 to physical disk % 1.
SeverityOK / Normal / Informational
Cause and
Action
Cause: This alert is for informational purposes.
Action: None
Related Alert
Information
SNMP Trap
Numbers
Clear Alert Number: None
Related Alert Number: 2060
Local Response Agent (LRA) Number: None
901
Event ID — 2088
DescriptionVirtual disk initialization completed.
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
Cause: This alert is for informational purposes.
Action: None
Clear Alert Number: Alert 2088 is a clear alert for alerts 2061 and 2136.
Related Alert Number: None
Local Response Agent (LRA) Number: None
69
SNMP Trap
Numbers
1201
Event ID — 2089
DescriptionPhysical disk initialization completed.
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
Cause: This alert is for informational purposes.
Action: None
Clear Alert Number: Alert 2089 is a clear alert for alert 2062.
Related Alert Number: None
Local Response Agent (LRA) Number: None
901
Event ID — 2090
DescriptionVirtual disk reconfiguration completed
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
Cause: This alert is for informational purposes.
Action: None
Clear Alert Number: Alert 2090 is a clear alert for alert 2063.
Related Alert Number: None
Local Response Agent (LRA) Number: None
1201
Event ID — 2091
DescriptionVirtual disk rebuild completed.
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
70
Cause: This alert is for informational purposes.
Action: None
Clear Alert Number: Alert 2091 is a clear alert for alert 2064.
Related Alert Number: None
Local Response Agent (LRA) Number: None
1201
Event ID — 2092
DescriptionPhysical disk rebuild completed.
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
Cause: This alert is for informational purposes.
Action: None
Clear Alert Number: Alert 2092 is a clear alert for alert 2065.
Related Alert Number: None
Local Response Agent (LRA) Number: None
901
Event ID — 2094
DescriptionPredictive Failure reported.
SeverityWarning / Non-critical
Cause and
Action
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.
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; the rebuild starts automatically.
NOTE: If you put the drive in a different slot, you need to assign it as a hot
spare for the rebuild to start automatically.
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 non-redundant disk, back up your data
immediately. If the disk fails, you cannot recover the data.
Related Alert
Information
SNMP Trap
Numbers
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: 2070
903
Event ID — 2095
DescriptionSCSI sense data %1.
71
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
Cause: A SCSI device experienced an error, but may have recovered.
Action: None
Clear Alert Number: None
Related Alert Number: 2273
Local Response Agent (LRA) Number: None
751, 851, 901
Event ID — 2098
DescriptionGlobal hot spare assigned.
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
Cause: A user has assigned a physical disk as a global hot spare. This alert is for
informational purposes.
Action: None
Clear Alert Number: None
Related Alert Number: 2277
Local Response Agent (LRA) Number: None
901
Event ID — 2099
DescriptionGlobal hot spare unassigned.
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
72
Cause: A physical disk that was assigned as a hot spare has been unassigned and is
no longer functioning as a hot spare. The physical disk may have been unassigned
by a user or automatically unassigned by Storage Management. Storage
Management unassigns hot spares that have been used to rebuild data. Once data
is rebuilt, the hot spare becomes a member of the virtual disk and is no longer
assigned as a hot spare. You need to assign a new hot spare to maintain data
protection in this situation. On the CERC SATA1.5/6 ch, and CERC SATA1.5/2s
controllers, if you use another application such as the BIOS to include a hot spare
in a virtual disk, then Storage Management unassigns the physical disk as a hot
spare.
Action: Although this alert is provided for informational purposes, you may need to
assign a new hot spare to the virtual disk.
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: None
SNMP Trap
Numbers
901
Event ID — 2100
DescriptionTemperature exceeded the maximum warning threshold.
SeverityWarning / Non-critical
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
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.
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.
Clear Alert Number: 2353
Related Alert Number: 2112
Local Response Agent (LRA) Number: 2090
1053
Event ID — 2101
DescriptionTemperature exceeded the maximum warning threshold.
SeverityWarning / Non-critical
Cause and
Action
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.
Related Alert
Information
SNMP Trap
Numbers
Clear Alert Number: 2353
Related Alert Number: None
Local Response Agent (LRA) Number: 2090
1053
Event ID — 2102
DescriptionTemperature exceeded the maximum failure threshold.
SeverityCritical / Failure / Error
Cause and
Action
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.
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
73
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.
Related Alert
Information
SNMP Trap
Numbers
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: 2091
1054
Event ID — 2103
DescriptionTemperature dropped below the minimum failure threshold.
SeverityCritical / Failure / Error
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
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.
Clear Alert Number: None
Related Alert Number: 2112
Local Response Agent (LRA) Number: 2091
1054
Event ID — 2104
DescriptionController battery is reconditioning.
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
Cause: This alert is for informational purposes.
Action: None
Clear Alert Number: 2105
Related Alert Number: None
Local Response Agent (LRA) Number: None
1151
Event ID — 2105
DescriptionController battery recondition is completed.
SeverityOK / Normal / Informational
74
Cause and
Action
Cause: This alert is for informational purposes.
Action: None
Related Alert
Information
SNMP Trap
Numbers
Clear Alert Number: Alert 2105 is a clear alert for alert 2104.
Related Alert Number: None
Local Response Agent (LRA) Number: None
1151
Event ID — 2106
DescriptionSMART FPT exceeded.
SeverityWarning / Non-critical
Cause and
Action
Related Alert
Information
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 causes the virtual disk to fail and may cause data loss.
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: 2070
SNMP Trap
Numbers
903
Event ID — 2107
DescriptionSMART configuration change.
SeverityCritical / Failure / Error
Cause and
Action
Related Alert
Information
Cause: A disk has received a SMART alert (predictive failure) after a configuration
change. 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 causes the virtual disk to fail and may cause data loss.
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: 2071
75
SNMP Trap
Numbers
904
Event ID — 2108
DescriptionSMART warning.
SeverityWarning / Non-critical
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
Cause: A disk has received a SMART alert (predictive failure). 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 causes the virtual disk to fail and may cause data loss.
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: 2070
903
Event ID — 2109
DescriptionSMART warning temperature.
SeverityWarning / Non-critical
Cause and
Action
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.
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.
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 nonredundant virtual disk, then back up the data before replacing the disk.
76
CAUTION: Removing a physical disk that is included in a non-redundant
virtual disk causes the virtual disk to fail and may cause data loss.
Related Alert
Information
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: 2070
SNMP Trap
Numbers
903
Event ID — 2110
DescriptionSMART warning degraded.
SeverityWarning / Non-critical
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
Cause: A disk is degraded and has received a SMART alert (predictive failure). 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 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 causes the virtual disk to fail and may cause data loss.
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: 2070
903
Event ID — 2111
DescriptionFailure prediction threshold exceeded due to test.
SeverityWarning / Non-critical
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
Cause: A disk has received a SMART alert (predictive failure) due to test conditions.
Action: None
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: 2070
903
Event ID — 2112
DescriptionEnclosure was shut down.
SeverityCritical / Failure / Error
77
Cause and
Action
Cause: The physical disk enclosure is either hotter or cooler than the maximum or
minimum allowable temperature range.
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.
Related Alert
Information
SNMP Trap
Numbers
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: 2091
854
Event ID — 2114
DescriptionA consistency check on a virtual disk has been paused (suspended).
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
Cause: The check consistency operation on a virtual disk was paused by a user.
Action: To resume the check consistency operation, right-click the virtual disk in
the tree view and select Resume Check Consistency.
Clear Alert Number: 2115
Related Alert Number: None
Local Response Agent (LRA) Number: None
1201
Event ID — 2115
DescriptionA consistency check on a virtual disk has been resumed.
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
78
Cause: The check consistency operation on a virtual disk has resumed processing
after being paused by a user. This alert is for informational purposes.
Action: None
Clear Alert Number: Alert 2115 is a clear alert for alert 2114.
Related Alert Number: None
Local Response Agent (LRA) Number: None
1201
Event ID — 2116
DescriptionA virtual disk and its mirror have been split.
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
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 the mirror is
no longer intact. The updates to the data are no longer copied to the mirror. This
alert is for informational purposes.
Action: None
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: None
1201
Event ID — 2117
DescriptionA mirrored virtual disk has been unmirrored.
SeverityOK / Normal / Informational
Cause and
Action
Cause: A user has caused a 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.
Action: None
Related Alert
Information
SNMP Trap
Numbers
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: None
1201
Event ID — 2118
DescriptionChange write policy.
SeverityOK / Normal / Informational
Cause and
Action
Cause: A user has changed the write policy for a virtual disk. This alert is for
informational purposes.
Action: None
79
Related Alert
Information
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: None
SNMP Trap
Numbers
1201
Event ID — 2120
DescriptionEnclosure firmware mismatch.
SeverityWarning / Non-critical
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
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.
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: 2090
853
Event ID — 2121
DescriptionDevice returned to normal.
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
Cause: A device that was previously in an error state has returned to a normal state.
For example, if an enclosure became too hot and subsequently cooled down, you
may receive this alert. This alert is for informational purposes.
Action: None
Clear Alert Number: Alert 2121 is a clear alert for alert 2048.
Related Alert Number: 2050, 2065, 2158
Local Response Agent (LRA) Number: None
Cause: One or more of the enclosure components has failed.
For example, a fan or power supply may have failed. 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 is identified with a red X on the enclosure’s Health subtab.
Alternatively, you can select the Storage object and click the Health subtab.
The controller status displayed on the Health subtab indicates whether a controller
has a Failed or Degraded component.
See the enclosure documentation for information on replacing enclosure
components and for other diagnostic information.
Related Alert
Information
SNMP Trap
Numbers
Clear Alert Number: 2124
Related Alert Number: 2048
Local Response Agent (LRA) Number: 2090
1305
Event ID — 2123
DescriptionRedundancy lost.
SeverityWarning / Non-critical
Cause and
Action
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 results
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. 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.
Related Alert
Information
Clear Alert Number: 2353
Related Alert Number: 2112
Local Response Agent (LRA) Number: 2090
81
SNMP Trap
Numbers
1053
Event ID — 2124
DescriptionRedundancy normal.
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
Cause: Data redundancy 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
Local Response Agent (LRA) Number: None
1304
Event ID — 2125
DescriptionController cache preserved for missing or offline virtual disk.
SeverityWarning / Non-critical
Cause and
Action
Related Alert
Information
Cause: Virtual disk controller was disconnected, during I/O operation.
Action: Import foreign disks, if any. Check if the enclosure containing the virtual
disk is disconnected from the controller.
Clear Alert Number: 2186, 2240
Related Alert Number: None
Local Response Agent (LRA) Number: None
SNMP Trap
Numbers
1203
Event ID — 2126
DescriptionSCSI sense sector reassign.
SeverityWarning / Non-critical
Cause and
Action
82
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.
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 non-redundant
virtual disk causes the virtual disk to fail and may cause data loss.
If the disk is part of a redundant virtual disk, then any data residing on the corrupt
portion of the disk is reallocated elsewhere in the virtual disk.
Related Alert
Information
SNMP Trap
Numbers
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: None
Cause: BGI of a virtual disk has started. This alert is for informational purposes.
Action: None
Clear Alert Number: 2130
Related Alert Number: None
Local Response Agent (LRA) Number: None
1201
Event ID — 2128
DescriptionBGI cancelled.
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
Cause: BGI of a virtual disk has been cancelled. A user or the firmware may have
stopped BGI.
Action: None
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: None
1201
Event ID — 2129
DescriptionBGI failed.
SeverityCritical / Failure / Error
83
Cause and
Action
Cause: BGI of a virtual disk has failed.
Action: None
Related Alert
Information
SNMP Trap
Numbers
Clear Alert Number: None
Related Alert Number: 2340
Local Response Agent (LRA) Number: 2081
1204
Event ID — 2130
DescriptionBGI completed.
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
Cause: BGI of a virtual disk has completed. This alert is for informational purposes.
Action: None
Clear Alert Number: Alert 2130 is a clear alert for alert 2127.
Related Alert Number: None
Local Response Agent (LRA) Number: None
1201
Event ID — 2131
DescriptionFirmware version mismatch.
SeverityWarning / Non-critical
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
Cause: The firmware on the controller is not a supported version.
Action: Install a supported version of the firmware. If you do not have a supported
version of the firmware available, check with your support provider for information
on how to obtain the most current firmware.
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: 2060
753
Event ID — 2132
DescriptionDriver version mismatch.
SeverityWarning / Non-critical
84
Cause and
Action
Cause: The controller driver is not a supported version.
Action: Install a supported version of the driver. If you do not have a supported
driver version available, you can check with your support provider for information
on how to obtain the most current driver.
Related Alert
Information
SNMP Trap
Numbers
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: 2060
753
Event ID — 2135
DescriptionArray Manager is installed on the system.
NOTE: This is not supported on Server Administrator version 6.0.1.
SeverityWarning / Non-critical
Cause and
Action
Related Alert
Information
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.
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: 2050
SNMP Trap
Numbers
103
Event ID — 2136
DescriptionVirtual disk initialization.
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
Cause: Virtual disk initialization is in progress. This alert is for informational
purposes.
Action: None
Clear Alert Number: 2088
Related Alert Number: None
Local Response Agent (LRA) Number: None
1201
85
Event ID — 2137
DescriptionCommunication time-out.
SeverityWarning / Non-critical
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
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.
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.
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.
Clear Alert Number: 2162
Related Alert Number: None
Local Response Agent (LRA) Number: 2090
853
Event ID — 2138
DescriptionEnclosure alarm enabled.
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
86
Cause: A user has enabled the enclosure alarm. This alert is for informational
purposes.
Action: None
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: None
851
Event ID — 2139
DescriptionEnclosure alarm disabled.
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
Cause: A user has disabled the enclosure alarm.
Action: None
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: None
851
Event ID — 2140
DescriptionDead disk segments restored.
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
Cause: Disk space that was formerly “dead” or inaccessible to a redundant virtual
disk has been restored. This alert is for informational purposes.
Action: None
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: None
1201
Event ID — 2141
DescriptionPhysical disk dead segments removed.
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
Cause: Portions of the 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.
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.
Clear Alert Number: None
Related Alert Number: None
87
Local Response Agent (LRA) Number: None
SNMP Trap
Numbers
901
Event ID — 2142
DescriptionController rebuild rate has changed.
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
Cause: A user has changed the controller rebuild rate. This alert is for informational
purposes.
Action: None
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: None
751
Event ID — 2143
DescriptionController alarm enabled.
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
Cause: A user has enabled the controller alarm. This alert is for informational
purposes.
Action: None
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: None
751
Event ID — 2144
DescriptionController alarm disabled.
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
Cause: A user has disabled the controller alarm. This alert is for informational
purposes.
Action: None
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: None
88
SNMP Trap
Numbers
751
Event ID — 2145
DescriptionController battery low.
SeverityWarning / Non-critical
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
Cause: The controller battery charge is low.
Action: Recondition the battery. See the online help for more information.
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: 2100
1153
Event ID — 2146
DescriptionBad block replacement error.
SeverityWarning / Non-critical
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
Cause: A portion of a physical disk is damaged.
Action: See the Server Administrator Storage Management online help for more
information.
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: 2060
753
Event ID — 2147
DescriptionBad block sense error.
SeverityWarning / Non-critical
Cause and
Action
Related Alert
Information
Cause: A portion of a physical disk is damaged.
Action: See the Server Administrator Storage Management online help for more
information.
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: 2060
89
SNMP Trap
Numbers
753
Event ID — 2148
DescriptionBad block medium error.
SeverityWarning / Non-critical
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
Cause: A portion of a physical disk is damaged.
Action: See the Server Administrator Storage Management online help for more
information.
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: 2060
753
Event ID — 2149
DescriptionBad block extended sense error.
SeverityWarning / Non-critical
Cause and
Action
Related Alert
Information
Cause: A portion of a physical disk is damaged.
Action: See the Server Administrator Storage Management online help for more
information.
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: 2060
SNMP Trap
Numbers
753
Event ID — 2150
DescriptionBad block extended medium error.
SeverityWarning / Non-critical
Cause and
Action
Related Alert
Information
90
Cause: A portion of a physical disk is damaged.
Action: See the Server Administrator Storage Management online help for more
information.
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: 2060
SNMP Trap
Numbers
753
Event ID — 2151
DescriptionEnclosure asset tag changed
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
Cause: A user has changed the enclosure asset tag. This alert is for informational
purposes.
Action: None
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: None
851
Event ID — 2152
DescriptionEnclosure asset name changed.
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
Cause: A user has changed the enclosure asset name. This alert is for informational
purposes.
Action: None
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: None
SNMP Trap
Numbers
851
Event ID — 2153
DescriptionEnclosure service tag changed.
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
Cause: An enclosure service tag was changed. In most circumstances, this service
tag should only be changed by your service provider.
Action: Ensure that the tag was changed under authorized circumstances.
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: None
91
SNMP Trap
Numbers
851
Event ID — 2154
DescriptionMaximum temperature probe warning threshold value changed.
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
Cause: A user has changed the value for the maximum temperature probe warning
threshold. This alert is for informational purposes.
Action: None
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: None
1051
Event ID — 2155
DescriptionMinimum temperature probe warning threshold value changed.
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
Cause: A user has changed the value for the minimum temperature probe warning
threshold. This alert is for informational purposes.
Action: None
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: None
SNMP Trap
Numbers
1051
Event ID — 2156
DescriptionController alarm has been tested.
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
92
Cause: The controller alarm test has run successfully. This alert is for informational
purposes.
Action: None
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: None
SNMP Trap
Numbers
751
Event ID — 2157
DescriptionController configuration has been reset.
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
Cause: A user has reset the controller configuration. See the online help for more
information. This alert is for informational purposes.
Action: None
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: None
751
Event ID — 2158
DescriptionPhysical disk online.
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
Cause: An offline physical disk has been made online. This alert is for informational
purposes.
Action: None
Clear Alert Number: Alert 2158 is a clear alert for alert 2050.
Related Alert Number: 2048, 2050, 2065, 2099, 2121, 2196, 2201, 2203
Local Response Agent (LRA) Number: None
SNMP Trap
Numbers
901
Event ID — 2159
DescriptionVirtual disk renamed.
SeverityOK / Normal / Informational
Cause and
Action
Cause: A user has renamed a virtual disk.
When renaming a virtual disk on a PERC 4/SC, 4/DC, 4e/DC, 4/Di, CERC
ATA100/4ch, PERC 5/E, PERC 5/i or SAS 5/iR controller, this alert displays the new
virtual disk name.
On the PERC 4/SC, 4/DC, 4e/DC, 4/Di, 4/IM, 4e/Si, 4e/Di, and CERC ATA 100/4ch
controllers, this alert displays the original virtual disk name. This alert is for
informational purposes.
Action: None
93
Related Alert
Information
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: None
SNMP Trap
Numbers
1201
Event ID — 2160
DescriptionDedicated hot spare assigned.
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
Cause: A user has assigned a physical disk as a dedicated hot spare to a virtual disk.
This alert is provided for informational purposes.
Action: None
Clear Alert Number: 2161
Related Alert Number: None
Local Response Agent (LRA) Number: None
901
Event ID — 2161
DescriptionDedicated hot spare unassigned.
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
94
Cause: A physical disk that was assigned as a hot spare has been unassigned and is
no longer functioning as a hot spare. The physical disk may have been unassigned
by a user or automatically unassigned by Storage Management. Storage
Management unassigns hot spares that have been used to rebuild data. Once data
is rebuilt onto the hot spare, the hot spare becomes a member of the virtual disk
and is no longer assigned as a hot spare. You need to assign a new hot spare to
maintain data protection in this situation. On the CERC SATA1.5/6ch, and CERC
SATA1.5/2s controllers, if you use another application such as the BIOS to include a
hot spare in a virtual disk, then Storage Management unassigns the physical disk as
a hot spare.
Action: Although this alert is provided for informational purposes, you may need to
assign a new hot spare to the virtual disk.
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: None
901
Event ID — 2162
DescriptionCommunication regained.
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
Cause: Communication with an enclosure has been restored. This alert is for
informational purposes.
Action: None
Clear Alert Number: Alert 2162 is a clear alert for alerts 2137 and 2292.
Related Alert Number: None
Local Response Agent (LRA) Number: None
851
Event ID — 2163
DescriptionRebuild completed with errors.
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
Cause: During a rebuild one or more blocks of data was not recoverable due to
missing parity information. Some data loss may have occurred.
Action: Perform a check to verify the built array. Any files that are impacted should
be restored from a backup. See the Storage Management online help for more
information.
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: 2071
SNMP Trap
Numbers
904
Event ID — 2164
DescriptionSee the Readme file for a list of validated controller driver versions.
SeverityOK / Normal / Informational
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 drivers. This alert is for
informational purposes.
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.
Clear Alert Number: None
Related Alert Number: None
95
Local Response Agent (LRA) Number: None
SNMP Trap
Numbers
101
Event ID — 2165
DescriptionThe RAID controller firmware and driver validation was not performed. The
configuration file cannot be opened.
SeverityWarning / Non-critical
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
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.
Action: Reinstall Storage Management
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: 2060
753
Event ID — 2166
DescriptionThe RAID controller firmware and driver validation was not performed. The
configuration file is out of date, missing the required information, or not properly
formatted to complete the comparison.
SeverityWarning / Non-critical
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
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 out of date, missing the
required information, or not properly formatted to complete the comparison.
Action: Reinstall Storage Management.
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: 2060
753
Event ID — 2167
DescriptionThe current kernel version and the non-RAID SCSI driver version are older than the
minimum required levels. See readme.txt for a list of validated kernel and driver
versions.
96
SeverityWarning / Non-critical
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
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.
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.
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: 2050
103
Event ID — 2168
DescriptionThe non-RAID SCSI driver version is older than the minimum required level. See
readme.txt for the validated driver version.
SeverityWarning / Non-critical
Cause and
Action
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.
Action: See the Readme file for the validated driver version. Update the system to
meet the minimum requirements and then reinstall Storage Management.
Related Alert
Information
SNMP Trap
Numbers
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: 2050
103
Event ID — 2169
DescriptionThe controller battery needs to be replaced.
SeverityCritical / Failure / Error
Cause and
Action
Related Alert
Information
Cause: The controller battery cannot be recharged. The battery may be old or it
may have been already recharged the maximum number of times. In addition, the
battery charger may not be working.
Action: Replace the battery pack.
Clear Alert Number: None
Related Alert Number: 2118
Local Response Agent (LRA) Number: 2101
97
SNMP Trap
Numbers
1154
Event ID — 2170
DescriptionThe controller battery charge level is normal.
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
Cause: This alert is for informational purposes.
Action: None
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: None
1151
Event ID — 2171
DescriptionThe controller battery temperature is above normal.
SeverityWarning / Non-critical
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.
Action: If this alert was generated due to a battery recharge, the situation is
corrected when the recharge is complete. You should also check if the room
temperature is normal and that the system components are functioning properly.
Clear Alert Number: 2172
Related Alert Number: None
Local Response Agent (LRA) Number: 2100
SNMP Trap
Numbers
1153
Event ID — 2172
DescriptionThe controller battery temperature is normal.
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
98
Cause: This alert is for informational purposes.
Action: None
Clear Alert Number: Alert 2172 is a clear alert for alert 2171.
Related Alert Number: None
Local Response Agent (LRA) Number: None
SNMP Trap
Numbers
1151
Event ID — 2173
DescriptionUnsupported configuration detected. The SCSI rates of the enclosure management
modules (EMMs) are not the same. EMM 0 % 1 EMM 1 % 2
SeverityWarning / Non-critical
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
Cause: An unsupported configuration was detected.
Action: Replace one of the EMMs with the matching SCSI rate EMM.
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: 2090
853
Event ID — 2174
DescriptionThe controller battery has been removed.
SeverityWarning / Non-critical
Cause and
Action
Related Alert
Information
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 must 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.
Clear Alert Number: None
Related Alert Number: 2188, 2318
Local Response Agent (LRA) Number: 2100
SNMP Trap
Numbers
1153
Event ID — 2175
DescriptionThe controller battery has been replaced.
SeverityOK / Normal / Informational
Cause and
Action
Cause: This alert is for informational purposes.
Action: None
99
Related Alert
Information
Clear Alert Number: None
Related Alert Number: None
Local Response Agent (LRA) Number: None
SNMP Trap
Numbers
1151
Event ID — 2176
DescriptionThe controller battery Learn cycle has started.
SeverityOK / Normal / Informational
Cause and
Action
Related Alert
Information
SNMP Trap
Numbers
Cause: This alert is for informational purposes.
Action: None
Clear Alert Number: 2177
Related Alert Number: None
Local Response Agent (LRA) Number: None
1151
Event ID — 2177
DescriptionThe controller battery Learn cycle has completed.
SeverityOK / Normal / Informational
Cause and
Action
Cause: This alert is for informational purposes.
Action: None
Related Alert
Information
SNMP Trap
Numbers
Clear Alert Number: Alert 2177 is a clear alert for alert 2176.
Related Alert Number: None
Local Response Agent (LRA) Number: None
1151
Event ID — 2178
DescriptionThe controller battery Learn cycle has timed out.
SeverityWarning / Non-critical
Cause and
Action
100
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 timeout occurs.
Action: Replace the battery pack as the battery is unable to maintain a full charge.
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.