Dell OpenManage™ Server Administrator Messages Reference Guide w w w. d e l l . c o m | s u p p o r t . d e l l .
Notes and Notices NOTE: A NOTE indicates important information that helps you make better use of your computer. NOTICE: A NOTICE indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. ____________________ Information in this document is subject to change without notice. © 2003–2007 Dell Inc. All rights reserved. Reproduction in any manner whatsoever without the written permission of Dell Inc. is strictly forbidden.
Contents 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . What’s New in this Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . Messages Not Described in This Guide . 5 . . . . . . . . . . . . . . . . . . . . . 5 Understanding Event Messages . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Sample Event Message Text . . . . . . . . . . . . . . . . . . . . . . . . . 7 Viewing Alerts and Event Messages . . . . . . . . . . . . . . . . . . . . . .
Pluggable Device Messages Battery Sensor Messages 3 . . . . . . . . . . . . . . . . . . . . . . . . . . 39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 System Event Log Messages for IPMI Systems . . . . . . . . . 43 . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Temperature Sensor Events Voltage Sensor Events .
Introduction Dell OpenManage™ Server Administrator produces event messages stored primarily in the operating system or Server Administrator event logs and sometimes in SNMP traps. This document describes the event messages created by Server Administrator version 5.3 or later and displayed in the Server Administrator Alert log. Server Administrator creates events in response to sensor status changes and other monitored parameters.
Understanding Event Messages This section describes the various types of event messages generated by the Server Administrator. When an event occurs on your system, the Server Administrator sends information about one of the following event types to the systems management console: Table 1-1. Understanding Event Messages Icon Alert Severity Component Status OK/Normal An event that describes the successful operation of a unit.
• Fan Enclosure Sensor — Monitors protective fan enclosures by detecting their removal from and insertion into the system, and by measuring how long a fan enclosure is absent from the chassis. This sensor monitors the chassis and any attached systems. • AC Power Cord Sensor — Monitors the presence of AC power for an AC power cord. • Hardware Log Sensor — Monitors the size of a hardware log. • Processor Sensor — Monitors the processor status in the system.
The location of the event log file depends on the operating system you are using. • In the Microsoft® Windows® 2000 Advanced Server and Windows Server™ 2003 operating systems, messages are logged to the system event log and optionally to a unicode text file, dcsys32.log (viewable using Notepad), that is located in the install_path\omsa\log directory. The default install_path is C:\Program Files\Dell\SysMgt.
...
Understanding the Event Description Table 1-2 lists in alphabetical order each line item that may appear in the event description. Table 1-2.
Table 1-2.
Table 1-2.
Event Message Reference The following tables lists in numerical order each event ID and its corresponding description, along with its severity and cause. NOTE: For corrective actions, see the appropriate documentation. Miscellaneous Messages Miscellaneous messages in Table 2-1 indicate that certain alert systems are up and working. Table 2-1. Miscellaneous Messages Event ID Description Severity Cause 0000 Log was cleared Information User cleared the log from Server Administrator.
Table 2-1. Miscellaneous Messages (continued) Event ID Description Severity Cause 1005 SMBIOS data is absent Warning The system does not contain the required systems management BIOS version 2.2 or higher, or the BIOS is corrupted. 1006 Automatic System Recovery (ASR) action was performed Error This message is generated when an automatic system recovery action is performed due to a hung operating system. The action performed and the time of action are provided.
Temperature Sensor Messages Temperature sensors listed in Table 2-2 help protect critical components by alerting the systems management console when temperatures become too high inside a chassis. The temperature sensor messages use additional variables: sensor location, chassis location, previous state, and temperature sensor value or state. Table 2-2.
Table 2-2. Temperature Sensor Messages (continued) Event ID Description Severity Cause 1052 Information A temperature sensor on the backplane board, system board, or drive carrier in the specified system returned to a valid range after crossing a failure threshold. The sensor location, chassis location, previous state, and temperature sensor value are provided.
Table 2-2. Temperature Sensor Messages (continued) Event ID Description Severity Cause 1054 Error A temperature sensor on the backplane board, system board, or drive carrier in the specified system exceeded its failure threshold. The sensor location, chassis location, previous state, and temperature sensor value are provided. Error A temperature sensor on the backplane board, system board, or drive carrier in the specified system detected an error from which it cannot recover.
Cooling Device Messages Cooling device sensors listed in Table 2-3 monitor how well a fan is functioning. Cooling device messages provide status and warning information for fans in a particular chassis. Table 2-3. Cooling Device Messages Event ID Description Severity Cause 1100 Information A fan sensor in the specified system is not functioning. The sensor location, chassis location, previous state, and fan sensor value are provided.
Table 2-3. Cooling Device Messages (continued) Event ID Description Severity Cause 1104 Error A fan sensor in the specified system detected the failure of one or more fans. The sensor location, chassis location, previous state, and fan sensor value are provided. Error A fan sensor detected an error from which it cannot recover. The sensor location, chassis location, previous state, and fan sensor value are provided.
Table 2-4. Voltage Sensor Messages (continued) Event ID Description Severity Cause 1151 Information A voltage sensor in the specified system could not obtain a reading. The sensor location, chassis location, previous state, and a nominal voltage sensor value are provided. Information A voltage sensor in the specified system returned to a valid range after crossing a failure threshold. The sensor location, chassis location, previous state, and voltage sensor value are provided.
Table 2-4. Voltage Sensor Messages (continued) Event ID Description Severity Cause 1154 Error A voltage sensor in the specified system exceeded its failure threshold. The sensor location, chassis location, previous state, and voltage sensor value are provided. Error A voltage sensor in the specified system detected an error from which it cannot recover. The sensor location, chassis location, previous state, and voltage sensor value are provided.
Current Sensor Messages Current sensors listed in Table 2-5 measure the amount of current (in amperes) that is traversing critical components. Current sensor messages provide status and warning information for current sensors in a particular chassis. Table 2-5. Current Sensor Messages Event ID Description Severity Cause 1200 Information A current sensor in the specified system failed. The sensor location, chassis location, previous state, and current sensor value are provided.
Table 2-5. Current Sensor Messages (continued) Event ID Description Severity Cause 1202 Information A 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 are provided. Warning A current sensor in the specified system exceeded its warning threshold. The sensor location, chassis location, previous state, and current sensor value are provided.
Table 2-5. Current Sensor Messages (continued) Event ID Description Severity Cause 1204 Error A current sensor in the specified system exceeded its failure threshold. The sensor location, chassis location, previous state, and current sensor value are provided. Error A current sensor in the specified system detected an error from which it cannot recover. The sensor location, chassis location, previous state, and current sensor value are provided.
Chassis Intrusion Messages Chassis intrusion messages listed in Table 2-6 are a security measure. Chassis intrusion means that someone is opening the cover to a system’s chassis. Alerts are sent to prevent unauthorized removal of parts from a chassis. Table 2-6. Chassis Intrusion Messages Event ID Description 1250 Severity Chassis intrusion sensor has Information failed Sensor location: Cause A chassis intrusion sensor in the specified system failed.
Table 2-6. Chassis Intrusion Messages (continued) Event ID Description Severity Cause 1253 Warning A chassis intrusion sensor in the specified system detected that a system cover is currently being opened and the system is operating. The sensor location, chassis location, previous state, and chassis intrusion state are provided. Error A chassis intrusion sensor in the specified system detected that the system cover was opened while the system was operating.
The number of devices required for full redundancy is provided as part of the message, when applicable, for the redundancy unit and the platform. For details on redundancy computation, see the respective platform documentation. Table 2-7. Redundancy Unit Messages Event ID Description Severity Cause 1300 Redundancy sensor has failed Information A redundancy sensor in the specified system failed.
Table 2-7. Redundancy Unit Messages (continued) Event ID Description Severity Cause 1304 Redundancy regained Information A redundancy sensor in the specified system detected that a “lost” redundancy device has been reconnected or replaced; full redundancy is in effect. The redundancy unit location, chassis location, previous redundancy state, and the number of devices required for full redundancy are provided.
Power Supply Messages Power supply sensors monitor how well a power supply is functioning. Power supply messages listed in Table 2-8 provide status and warning information for power supplies present in a particular chassis. Table 2-8. Power Supply Messages Event ID Description Severity Cause 1350 Information A power supply sensor in the specified system failed. The sensor location, chassis location, previous state, and additional power supply status information are provided.
Table 2-8. Power Supply Messages (continued) Event ID Description Severity Cause 1352 Information A power supply has been reconnected or replaced. The sensor location, chassis location, previous state, and additional power supply status information are provided. Warning A power supply sensor reading in the specified system exceeded a user-definable warning threshold. The sensor location, chassis location, previous state, and additional power supply status information are provided.
Table 2-8. Power Supply Messages (continued) Event ID Description 1354 Severity Power supply detected a failure Error Sensor location: Chassis location: Cause A power supply has been disconnected or has failed. The sensor location, chassis location, previous state, and additional power supply status information are provided.
Memory Device Messages Memory device messages listed in Table 2-9 provide status and warning information for memory modules present in a particular system. Memory devices determine health status by monitoring the ECC memory correction rate and the type of memory events that have occurred. NOTE: A critical status does not always indicate a system failure or loss of data. In some instances, the system has exceeded the ECC correction rate.
Fan Enclosure Messages Some systems are equipped with a protective enclosure for fans. Fan enclosure messages listed in Table 2-10 monitor whether foreign objects are present in an enclosure and how long a fan enclosure is missing from a chassis. Table 2-10. Fan Enclosure Messages Event ID Description Severity Cause 1450 Information The fan enclosure sensor in the specified system failed. The sensor location and chassis location are provided.
Table 2-10. Fan Enclosure Messages (continued) Event ID Description Severity Cause 1454 Error A fan enclosure has been removed from the specified system for a user-definable length of time. The sensor location and chassis location are provided. Error A fan enclosure sensor in the specified system detected an error from which it cannot recover. The sensor location and chassis location are provided.
Table 2-11. AC Power Cord Messages (continued) Event ID Description Severity Cause 1502 Information An AC power cord that did not have AC power has had the power restored. The sensor location and chassis location information are provided. Warning An AC power cord has lost its power, but there is sufficient redundancy to classify this as a warning. The sensor location and chassis location information are provided.
Table 2-12. Hardware Log Sensor Messages Event ID Description Severity Cause 1550 Information A hardware log sensor in the specified system is disabled. The log type information is provided. Information A hardware log sensor in the specified system could not obtain a reading. The log type information is provided. Information The 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.
Processor Sensor Messages Processor sensors monitor how well a processor is functioning. Processor messages listed in Table 2-13 provide status and warning information for processors in a particular chassis. Table 2-13. Processor Sensor Messages Event ID Description Severity Cause 1600 Information A processor sensor in the specified system is not functioning. The sensor location, chassis location, previous state and processor sensor status are provided.
Table 2-13. Processor Sensor Messages (continued) Event ID Description Severity Cause 1603 Warning A processor sensor in the specified system is in a throttled state. The sensor location, chassis location, previous state and processor sensor status are provided. Error A processor sensor in the specified system is disabled, has a configuration error, or experienced a thermal trip. The sensor location, chassis location, previous state and processor sensor status are provided.
Pluggable Device Messages The pluggable device messages listed in Table 2-14 provide status and error information when some devices, such as memory cards, are added or removed. Table 2-14. Pluggable Device Messages Event ID Description Severity Cause 1650 Information A pluggable device event message of unknown type was received. The device location, chassis location, and additional event details, if available, are provided. Information A device was added in the specified system.
Battery Sensor Messages Battery sensors monitor how well a battery is functioning. Battery messages listed in Table 2-15 provide status and warning information for batteries in a particular chassis. Table 2-15. Battery Sensor Messages Event ID Description Severity Cause 1700 Information A battery sensor in the specified system is not functioning. The sensor location, chassis location, previous state, and battery sensor status are provided.
Table 2-15. Battery Sensor Messages (continued) Event ID Description Severity Cause 1704 Error A battery sensor in the specified system detected that a battery has failed. The sensor location, chassis location, previous state, and battery sensor status are provided. Error A battery sensor in the specified system detected that a battery has failed. The sensor location, chassis location, previous state, and battery sensor status are provided.
Event Message Reference
System Event Log Messages for IPMI Systems The following tables list the system event log (SEL) messages, their severity, and cause. NOTE: For corrective actions, see the appropriate documentation. Temperature Sensor Events The temperature sensor event messages help protect critical components by alerting the systems management console when the temperature rises inside the chassis.
Voltage Sensor Events The voltage sensor event messages monitor the number of volts across critical components. These messages provide status and warning information for voltage sensors for a particular chassis. Table 3-2. Voltage Sensor Events Event Message Severity voltage Critical sensor detected a failure where is the entity that this sensor is monitoring. Cause The voltage of the monitored device has exceeded the critical threshold.
Fan Sensor Events The cooling device sensors monitor how well a fan is functioning. These messages provide status warning and failure messages for fans for a particular chassis. Table 3-3. Fan Sensor Events Event Message Severity Fan Critical sensor detected a failure where is the entity that this sensor is monitoring. For example "BMC Back Fan" or "BMC Front Fan.
Processor Status Events The processor status messages monitor the functionality of the processors in a system. These messages provide processor health and warning information of a system. Table 3-4. Processor Status Events 46 Event Message Severity Cause status processor sensor IERR, where is the processor that generated the event. For example, PROC for a single processor system and PROC # for multiprocessor system.
Power Supply Events The power supply sensors monitor the functionality of the power supplies. These messages provide status and warning information for power supplies for a particular system. Table 3-5. Power Supply Events Event Message Severity Cause power supply sensor removed. Critical This event is generated when the power supply sensor is removed. power supply sensor AC recovered.
Memory ECC Events The memory ECC event messages monitor the memory modules in a system. These messages monitor the ECC memory correction rate and the type of memory events that occurred. Table 3-6. Memory ECC Events Event Message Severity Cause ECC error correction detected on Bank # DIMM [A/B]. Information This event is generated when there is a memory error correction on a particular Dual Inline Memory Module (DIMM). ECC uncorrectable error detected on Bank # [DIMM].
Memory Events The memory modules can be configured in different ways in particular systems. These messages monitor the status, warning, and configuration information about the memory modules in the system. Table 3-8. Memory Events Event Message Severity Cause Memory RAID redundancy degraded. Information This event is generated when there is a memory failure in a RAID-configured memory configuration. Memory RAID redundancy lost.
Drive Events The drive event messages monitor the health of the drives in a system. These events are generated when there is a fault in the drives indicated. Table 3-10. Drive Events Event Message Severity Drive asserted fault Critical state. Cause This event is generated when the specified drive in the array is faulty. Drive de-asserted fault state. Information This event is generated when the specified drive recovers from a faulty condition.
Table 3-10. Drive Events (continued) Event Message Severity Cause Drive in failed array was deasserted Informational This event is generated when the drive is removed from the fail array. Drive Informational This event is generated when the drive is rebuilding. rebuild in progress was asserted Drive Warning rebuild aborted was asserted This event is generated when the drive rebuilding process is aborted.
BIOS Generated System Events The BIOS generated messages monitor the health and functionality of the chipsets, I/O channels, and other BIOS-related functions. These system events are generated by the BIOS. Table 3-12. BIOS Generated System Events Event Message Severity System Event I/O channel chk. Critical Cause This event is generated when a critical interrupt is generated in the I/O Channel. System Event PCI Parity Err.
Table 3-12. BIOS Generated System Events (continued) Event Message Severity Cause Memory Removed Information This event is generated when memory is removed from the system. Critical This event is generated when memory configuration is incorrect for the system. Information This event is generated when memory redundancy is regained. Warning This event is generated when correctable ECC errors have increased from a normal rate.
Table 3-12. BIOS Generated System Events (continued) Event Message Severity Cause Hdwr version err Information This event is generated when the earlier mismatch between the BMC firmware and the processor is corrected. Critical This event is generated when there is a mismatch between the BMC firmware and the processor in use or vice versa. Information This event is generated when an earlier hardware mismatch is corrected.
R2 Generated System Events Table 3-13. R2 Generated Events Description Severity Cause System Event: OS stop event OS graceful shutdown detected Information The OS was shutdown/restarted normally. OEM Event data record (after Information OS graceful shutdown/restart event) Comment string accompanying an OS shutdown/restart. System Event: OS stop event runtime critical stop Critical The OS encountered a critical error and was stopped abnormally.
Entity Presence Events The entity presence messages are used for detecting different hardware devices. Table 3-16. Entity Presence Events Description Severity Cause Information This event is generated when the device was detected. Critical This event is generated when the device was not detected.
Storage Management Message Reference The Dell OpenManage™ Server Administrator Storage Management’s alert or event management features let you monitor the health of storage resources such as controllers, enclosures, physical disks, and virtual disks. Alert Monitoring and Logging The Storage Management Service performs alert monitoring and logging. By default, the Storage Management Service starts when the managed system starts up.
For other alerts, the alert message text is constructed from information passed directly from the controller (or another storage component) to the Alert Log. In these cases, the variable information is represented with a % (percent sign) in the Storage Management documentation. An example of such an alert is shown for alert 2334 in Table 4-1. Table 4-1.
Table 4-2. Message Format with Variables for Each Storage Object (continued) Storage Object Message Variables A, B, C and X, Y, Z in the following examples are variables representing the storage object name or number. Virtual Disk Message Format: Virtual Disk X (Name) Controller A (Name) Message Format: Virtual Disk X Controller A Example: 2057 Virtual disk degraded: Virtual Disk 11 (Virtual Disk 11) Controller 1 (PERC 5/E Adapter) NOTE: The virtual disk and controller names are not always displayed.
Table 4-2. Message Format with Variables for Each Storage Object (continued) Storage Object Message Variables A, B, C and X, Y, Z in the following examples are variables representing the storage object name or number.
Table 4-3. Alert Message Change History Alert Message Change History 2305 Changed documentation for cause and corrective action. Changed SNMP trap number to 903. This change only made in the Dell OpenManage Server Administrator Messages Reference Guide to reflect existing Storage Management online help. 2312 Changed documentation for corrective action in the Storage Management online help. The Dell OpenManage Server Administrator Messages Reference Guide already has updated corrective action.
Table 4-3. Alert Message Change History Alert Message Change History Obsolete Alerts 2266 SNMP traps changed to 751, 801, 851, 901, 951, 1001, 1051, 1101, 1151, 1201. 2272 Severity changed to Critical. SNMP trap changed to 904. Changed corrective action information in the documentation. 2273 Changed alert message text and documentation for cause and corrective action. 2279 Changed alert message text. 2299 Changed corrective action information in the documentation.
Table 4-3. Alert Message Change History Alert Message Change History Removed alert 2345. Replaced by alert 2079. Storage Management 2.1 Documentation change only made in the Dell OpenManage Server Administrator Messages Reference Guide to reflect existing Storage Management online help. Comments Product Versions to Storage Management 2.1 which Changes Server Administrator 2.4 Apply Dell OpenManage™ 5.
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 subtab 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.
Table 4-4. Storage Management Messages (continued) Event Description ID Severity 2049 Warning / Cause: A physical disk has been Non-critical removed from the disk group. This alert can also be caused by loose or defective cables or by problems with the enclosure. Physical disk removed Cause and Action Related Alert Information SNMP Trap Numbers Clear Alert Number: 2052.
Table 4-4. Storage Management Messages (continued) Event Description ID Severity 2051 Warning / Cause: A physical disk has reported Clear Alert Number: None. Non-critical an error condition and may be Related Alert Number: 2070 degraded. The physical disk may have LRA Number: None. reported the error condition in response to a consistency check or other operation. Physical disk degraded Cause and Action Related Alert Information SNMP Trap Numbers 903 Action: Replace the degraded physical disk.
Table 4-4. Storage Management Messages (continued) Event Description ID Severity Cause and Action Related Alert Information SNMP Trap Numbers 2056 Critical / Failure / Error Cause: One or more physical disks included in the virtual disk have failed. If the virtual disk is nonredundant (does not use mirrored or parity data), then the failure of a single physical disk can cause the virtual disk to fail.
Table 4-4. Storage Management Messages (continued) Event Description ID Severity 2057 Warning / Cause 1: This alert message occurs Non-critical 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. Virtual disk degraded Cause and Action Related Alert Information SNMP Trap Numbers Clear Alert Number: None.
Table 4-4. Storage Management Messages (continued) Event Description ID Severity 2061 Virtual disk initialization started Ok / Normal Cause: This alert is for informational purposes. Physical disk initialization started Ok / Normal Cause: This alert is for informational purposes. 2062 2063 2064 Cause and Action Action: None SNMP Trap Numbers Clear Alert Number: 2088. 1201 Related Alert Number: None. LRA Number: None. Action: None. Clear Alert Number: 2089. Related Alert Number: None.
Table 4-4. Storage Management Messages (continued) Event Description ID Severity 2067 Ok / Normal Cause: The check consistency Clear Alert Number: None. operation cancelled because a Related Alert Number: None. physical disk in the array has failed or LRA Number: None. because a user cancelled the check consistency operation. Virtual disk check consistency cancelled Cause and Action Related Alert Information SNMP Trap Numbers 1201 Action: If the physical disk failed, then replace the physical disk.
Table 4-4. Storage Management Messages (continued) Event Description ID Severity Cause and Action 2076 Critical / Failure / Error Cause: A physical disk included in Clear Alert Number: None. the virtual disk failed or there is an Related Alert Number: None. error in the parity information. A failed physical disk can cause errors in LRA Number: 2081 parity information. Virtual disk check consistency failed Related Alert Information SNMP Trap Numbers 1204 Action: Replace the failed physical disk.
Table 4-4. Storage Management Messages (continued) Event Description ID 2081 Severity Virtual disk Critical / reconfiguratio Failure / n failed Error Cause and Action Related Alert Information SNMP Trap Numbers Cause: A physical disk included in the virtual disk has failed or is corrupt. A user may also have cancelled the reconfiguration. Clear Alert Number: None. 1204 Related Alert Number: None. LRA Number: 2081 Action: Replace the failed or corrupt disk.
Table 4-4. Storage Management Messages (continued) Event Description ID Severity 2086 Ok / Normal Cause: This alert is for informational purposes. Virtual disk format completed Cause and Action Related Alert Information Action: None SNMP Trap Numbers Clear Alert Status: Alert 2086 is 1201 a clear alert for alert 2059. Related Alert Number: None. LRA Number: None. 2088 Virtual disk initialization completed Ok / Normal Cause: This alert is for informational purposes.
Table 4-4. Storage Management Messages (continued) Event Description ID Severity 2094 Warning / Cause: The physical disk is predicted Clear Alert Number: None. Non-critical to fail. Many physical disks contain Related Alert Number: None. Self Monitoring Analysis and LRA Number: 2070 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. Predictive Failure reported.
Table 4-4. Storage Management Messages (continued) Event Description ID Severity 2099 Ok / Normal Cause: A user has unassigned a physical disk as a global hot spare. This alert is for informational purposes. Global hot spare unassigned Cause and Action Related Alert Information SNMP Trap Numbers Clear Alert Number: None. 901 Related Alert Number: None. LRA Number: None.
Table 4-4. Storage Management Messages (continued) Event Description ID Severity Cause and Action 2102 Critical / Failure / Error Cause: The physical disk enclosure is Clear Alert Number: None. too hot. A variety of factors can cause Related Alert Number: None. the excessive temperature. For example, a fan may have failed, the LRA Number: 2091 thermostat may be set too high, or the room temperature may be too hot.
Table 4-4. Storage Management Messages (continued) Event Description ID Severity 2106 Warning / Cause: A disk on the specified Non-critical controller has received a SMART alert (predictive failure) indicating that the disk is likely to fail in the near future. Smart FPT exceeded Cause and Action Related Alert Information SNMP Trap Numbers Clear Alert Number: None. 903 Related Alert Number: None. LRA Number: 2070 Action: Replace the disk that has received the SMART alert.
Table 4-4. Storage Management Messages (continued) Event Description ID 2108 Severity Cause and Action Smart warning Warning / Cause: A disk has received a SMART Clear Alert Number: None. Non-critical alert (predictive failure). The disk is Related Alert Number: None. likely to fail in the near future. LRA Number: 2070 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.
Table 4-4. Storage Management Messages (continued) Event Description ID Severity 2109 Warning / Cause: A disk has reached an Clear Alert Number: None. Non-critical unacceptable temperature and Related Alert Number: None. received a SMART alert (predictive failure). The disk is likely to fail in the LRA Number: 2070 near future. SMART warning temperature Cause and Action Related Alert Information SNMP Trap Numbers 903 Action 1: Determine why the physical disk has reached an unacceptable temperature.
Table 4-4. Storage Management Messages (continued) Event Description ID Severity 2110 Clear Alert Number: None. Warning / Cause: A disk is degraded and has Non-critical received a SMART alert (predictive Related Alert Number: None. failure). The disk is likely to fail in the LRA Number: 2070 near future. SMART warning degraded Cause and Action Related Alert Information SNMP Trap Numbers 903 Action: Replace the disk that has received the SMART alert.
Table 4-4. Storage Management Messages (continued) Event Description ID Severity Cause and Action Related Alert Information 2114 A consistency Ok / Normal check on a virtual disk has been paused (suspended) Cause: The check consistency Clear Alert Number: 2115. operation on a virtual disk was paused Related Alert Number: None. by a user. LRA Number: None. Action: To resume the check consistency operation, right-click the virtual disk in the tree view and select Resume Check Consistency.
Table 4-4. Storage Management Messages (continued) Event Description ID Severity 2118 Ok / Normal Cause: This alert is for informational purposes. A user has changed the write policy for a virtual disk. Change write policy Cause and Action Action: None 2120 Enclosure firmware mismatch Related Alert Information SNMP Trap Numbers Clear Alert Number: None. 1201 Related Alert Number: None. LRA Number: None. Warning / Cause: The firmware on the EMM is Clear Alert Number: None.
Table 4-4. Storage Management Messages (continued) Event Description ID Severity 2122 Warning / Cause: One or more of the enclosure Clear Alert Status: 2124. Non-critical components has failed. Related Alert Number: 2048 For example, a fan or power supply LRA Number: 2090 may have failed. Although the enclosure is currently operational, the failure of additional components could cause the enclosure to fail.
Table 4-4. Storage Management Messages (continued) Event Description ID Severity 2123 Warning / Cause: A virtual disk or an enclosure Non-critical has lost data redundancy. In the case of a virtual disk, one or more physical disks included in the virtual disk have failed. Due to the failed physical disk or disks, the virtual disk is no longer maintaining redundant (mirrored or parity) data. The failure of an additional physical disk will result in lost data.
Table 4-4. Storage Management Messages (continued) Event Description ID Severity 2124 Ok / Normal Cause: This alert is for informational purposes. Data redundancy has been restored to a virtual disk or an enclosure that previously suffered a loss of redundancy. Redundancy normal Cause and Action Related Alert Information Action: None 2126 SNMP Trap Numbers Clear Alert Number: Alert 2124 1304 is a clear alert for alerts 2122 and 2123. Related Alert Number: None. LRA Number: None.
Table 4-4. Storage Management Messages (continued) Event Description ID Severity Cause and Action Related Alert Information SNMP Trap Numbers 2128 BGI cancelled Ok / Normal Cause: BGI of a virtual disk has been Clear Alert Number: None. cancelled. A user or the firmware may Related Alert Number: None. have stopped BGI. LRA Number: None. Action: None 1201 2129 BGI failed 1204 2130 Critical / Failure / Error Cause: BGI of a virtual disk has failed. Clear Alert Number: None.
Table 4-4. Storage Management Messages (continued) Event Description ID 2132 Severity Cause and Action Driver version Warning / Cause: The controller driver is not a mismatch Non-critical supported version. Related Alert Information SNMP Trap Numbers Clear Alert Number: None. 753 Related Alert Number: None. Action: Install a supported version of LRA Number: 2060 the driver. If you do not have a supported driver version available, it can be downloaded from the Dell support site at support.dell.com.
Table 4-4. Storage Management Messages (continued) Event Description ID 2137 Severity Cause and Action Related Alert Information Communicatio Warning / Cause: The controller is unable to Clear Alert Number: 2162. n timeout Non-critical communicate with an enclosure. Related Alert Number: None. There are several reasons why LRA Number: 2090 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.
Table 4-4. Storage Management Messages (continued) Event Description ID 2139 Severity Cause and Action Enclosure Ok / Normal Cause: A user has disabled the alarm disabled enclosure alarm. Action: None 2140 Dead disk segments restored Related Alert Information SNMP Trap Numbers Clear Alert Number: None. 851 Related Alert Number: None. LRA Number: None. Ok / Normal Cause: This alert is for informational purposes.
Table 4-4. Storage Management Messages (continued) Event Description ID Severity 2145 Controller battery low Warning / Cause: The controller battery charge Clear Alert Number: None. Non-critical is low. Related Alert Number: None. Action: Recondition the battery. See LRA Number: 2100 the online help for more information 1153 2146 Bad block replacement error Warning / Cause: A portion of a physical disk is Clear Alert Number: None. Non-critical damaged. Related Alert Number: None.
Table 4-4. Storage Management Messages (continued) Event Description ID Severity 2151 Ok / Normal Cause: This alert is for informational purposes. A user has changed the enclosure asset tag. Asset tag changed Cause and Action Action: None 2152 Asset name changed Ok / Normal Cause: This alert is for informational purposes. A user has changed the enclosure asset name. Action: None 2153 Service tag changed Related Alert Information SNMP Trap Numbers Clear Alert Number: None.
Table 4-4. Storage Management Messages (continued) Event Description ID 2157 Severity Cause and Action Controller Ok / Normal Cause: This alert is for informational configuration purposes. A user has reset the has been reset controller configuration. See the online help for more information. Related Alert Information SNMP Trap Numbers Clear Alert Number: None. 751 Related Alert Number: None. LRA Number: None.
Table 4-4. Storage Management Messages (continued) Event Description ID Severity Cause and Action Related Alert Information 2163 Rebuild completed with errors Critical / Failure / Error Cause: This alert is documented in the Clear Alert Number: None. Storage Management online help. Related Alert Number: None. Action: See the online help for more LRA Number: 2071 information.
Table 4-4. Storage Management Messages (continued) Event Description ID 2166 2167 2168 94 Severity Cause and Action Related Alert Information SNMP Trap Numbers The RAID Warning / controller Non-critical firmware and driver validation was not performed. The configuration file is out of date or corrupted. Cause: Storage Management is unable to determine whether the system has the minimum required versions of the RAID controller firmware and drivers.
Table 4-4. Storage Management Messages (continued) Event Description ID 2169 Severity The controller Critical / battery needs Failure / to be replaced. Error Cause and Action Related Alert Information Cause: The controller battery cannot Clear Alert Number: None. recharge. The battery may be old or it Related Alert Number: 2118 may have been already recharged the LRA Number: 2101 maximum number of times. In addition, the battery charger may not be working.
Table 4-4. Storage Management Messages (continued) Event Description ID 2173 2174 Severity Unsupported Warning / configuration Non-critical detected. The SCSI rate of the enclosure management modules (EMMs) is not the same. EMM0 %1 EMM1 %2 Cause and Action Related Alert Information Cause: The EMMs in the enclosure Clear Alert Number: None. have a different SCSI rate. This is an Related Alert Number: None. unsupported configuration.
Table 4-4. Storage Management Messages (continued) Event Description ID 2176 2177 2178 Severity Related Alert Information SNMP Trap Numbers The controller Ok / Normal Cause: This alert is for informational battery Learn purposes. cycle has Action: None started. Clear Alert Number: 2177. 1151 The controller Ok / Normal Cause: This alert is for informational battery Learn purposes. cycle has Action: None completed. Clear Alert Status: Alert 2177 is 1151 a clear alert for alert 2176.
Table 4-4. Storage Management Messages (continued) Event Description ID 2180 Severity The controller Ok / Normal battery Learn cycle will start in %1 days. Cause and Action Related Alert Information Cause: This alert is for informational Clear Alert Number: None. purposes. The %1 indicates a Related Alert Number: None. substitution variable. The text for this substitution variable is displayed LRA Number: None. with the alert in the Alert Log and can vary depending on the situation.
Table 4-4. Storage Management Messages (continued) Event Description ID 2188 Severity The controller Ok / Normal write policy has been changed to Write Through. Cause and Action Related Alert Information Cause: The controller battery is Clear Alert Number: None. unable to maintain cached data for Related Alert Number: None. the required period of time. For LRA Number: None. example, if the required period of time is 24 hours, the battery is unable to maintain cached data for 24 hours.
Table 4-4. Storage Management Messages (continued) Event Description ID 2192 Severity The virtual Ok / Normal disk Check Consistency has made corrections and completed. Cause and Action Related Alert Information Cause: This alert is for informational Clear Alert Number: None. purposes. The virtual disk Check Related Alert Number: None. Consistency has identified errors and made corrections. For example, the LRA Number: None.
Table 4-4. Storage Management Messages (continued) Event Description ID Severity 2199 The virtual disk cache policy has changed. Ok / Normal Cause: This alert is for informational purposes. A global hot spare failed. Warning / Cause: The controller is not able to Non-critical communicate with a disk that is assigned as a dedicated hot spare. The disk may have been removed. There may also be a bad or loose cable.
Table 4-4. Storage Management Messages (continued) Event Description ID 2204 Severity Cause and Action A dedicated Ok / Normal Cause: The controller is unable to hot spare has communicate with a disk that is been removed. assigned as a dedicated hot spare. The disk may have been removed. There may also be a bad or loose cable. Related Alert Information SNMP Trap Numbers Clear Alert Number: None. 901 Related Alert Number: None. LRA Number: None.
Table 4-4. Storage Management Messages (continued) Event Description ID 2207 Severity The only hot Warning / spare available Non-critical is a SAS disk. SAS disks cannot replace SATA disks. Cause and Action Related Alert Information Cause: The only physical disk Clear Alert Number: None. available to be assigned as a hot spare Related Alert Number: None. is using SAS technology. The physical LRA Number: 2070 disks in the virtual disk are using SATA technology.
Table 4-4. Storage Management Messages (continued) Event Description ID 2215 2232 2233 2234 2235 Severity Cause and Action Related Alert Information SNMP Trap Numbers Battery charge OK/Normal Cause: This alert is for informational process purposes. interrupted Action: None. Clear Alert Number: None. 1151 The controller Ok / Normal Cause: This alert is for informational alarm is purposes. silenced. Action: None Clear Alert Number: None.
Table 4-4. Storage Management Messages (continued) Event Description ID Severity 2240 Ok / Normal Cause: This alert is for informational purposes. 2241 2242 2243 A foreign configuration has been imported. Cause and Action Action: None Related Alert Information SNMP Trap Numbers Clear Alert Number: None. 751 Related Alert Number: None. LRA Number: None. The Patrol Ok / Normal Cause: This alert is for informational Read mode has purposes. changed. Action: None Clear Alert Number: None.
Table 4-4. Storage Management Messages (continued) Event Description ID Severity Cause and Action Related Alert Information SNMP Trap Numbers 2246 The controller Warning / Cause: The controller battery charge Clear Alert Number: None. battery is Non-critical is weak. Related Alert Number: None. degraded. Action: As the charge weakens, the LRA Number: 2100 charger should automatically recharge the battery. If the battery has reached its recharge limit, replace the battery pack.
Table 4-4. Storage Management Messages (continued) Event Description ID Severity 2254 The Clear operation has cancelled. Ok / Normal Cause: This alert is for informational purposes. The physical disk has been started. Ok / Normal Cause: This alert is for informational purposes. 2255 Cause and Action Action: None Related Alert Information SNMP Trap Numbers Clear Alert Number: None. 901 Related Alert Number: None. LRA Number: None. Action: None Clear Alert Number: None.
Table 4-4. Storage Management Messages (continued) Event Description ID Severity Cause and Action 2264 A device is missing. Warning / Cause: The controller cannot Non-critical communicate with a device. The device may be removed. There may also be a bad or loose cable. Clear Alert Number: None. 2265 A device is in an unknown state. Warning / Cause: The controller cannot Non-critical communicate with a device. The state of the device cannot be determined. There may be a bad or loose cable.
Table 4-4. Storage Management Messages (continued) Event Description ID 2267 2268 2269 Severity Cause and Action The controller Ok / Normal Cause: This alert is for informational reconstruct purposes. rate has Action: None changed. %1, Storage Critical / Management Failure / has lost Error communicatio n with the controller. An immediate reboot is strongly recommended to avoid further problems. If the reboot does not restore communicatio n, then contact technical support for more information.
Table 4-4. Storage Management Messages (continued) Event Description ID Severity Cause and Action 2270 Critical / Failure / Error Cause: A Clear task was being Clear Alert Number: None. performed on a physical disk but the Related Alert Number: None. task was interrupted and did not complete successfully. The controller LRA Number: 2071 may have lost communication with the disk. The disk may have been removed or the cables may be loose or defective. The physical disk Clear operation failed.
Table 4-4. Storage Management Messages (continued) Event Description ID 2273 Severity A block on the Critical / physical disk Failure / has been Error punctured by the controller. Cause and Action Related Alert Information Cause: The controller encountered Clear Alert Number: None. an unrecoverable medium error when Related Alert Number: None. attempting to read a block on the physical disk and marked that block LRA Number: 2071 as invalid.
Table 4-4. Storage Management Messages (continued) Event Description ID 2278 Severity The controller Ok / Normal battery charge level is below a normal threshold. Cause and Action Related Alert Information Cause: The battery is discharging. A Clear Alert Number: None. battery discharge is a normal activity Related Alert Number: 2199 during the battery Learn cycle. Before completing, the battery Learn cycle LRA Number: None. recharges the battery. You should receive alert 2179 when the recharge occurs.
Table 4-4. Storage Management Messages (continued) Event Description ID Severity Cause and Action 2282 Critical / Failure / Error Cause: The controller firmware Clear Alert Number: None. attempted a SMART polling on the Related Alert Number: None. hot spare but was unable to complete LRA Number: 2071 it. The controller has lost communication with the hot spare. Hot spare SMART polling failed.
Table 4-4. Storage Management Messages (continued) Event Description ID 2286 2287 Severity Cause and Action Related Alert Information SNMP Trap Numbers A Learn cycle Ok / Normal Cause: This alert is for informational start is pending purposes. while the Action: None battery charges. Clear Alert Number: None. 1151 The Patrol Ok / Normal Cause: This alert is for informational Read is paused. purposes. Clear Alert Number: 2288.
Table 4-4. Storage Management Messages (continued) Event Description ID Severity 2290 Warning / Cause: An error involving a single bit Clear Alert Number: None. Non-critical has been encountered during a read Related Alert Number: None. or write operation. The error LRA Number: 2060 correction algorithm has corrected this error. Single-bit ECC error. Cause and Action Related Alert Information SNMP Trap Numbers 753 Action: None 2291 2292 2293 An EMM has been discovered.
Table 4-4. Storage Management Messages (continued) Event Description ID 2296 2297 2298 Severity Cause and Action An EMM has Ok / Normal Cause: This alert is for informational been inserted. purposes. An EMM has Critical / been removed. Failure / Error Related Alert Information SNMP Trap Numbers Clear Alert Number: None. 951 Related Alert Number: None. Action: None LRA Number: None. Cause: An EMM has been removed. Clear Alert Number: None. Action: Replace the EMM.
Table 4-4. Storage Management Messages (continued) Event Description ID 2300 Severity The enclosure Critical / is unstable. Failure / Error Cause and Action Related Alert Information Cause: The controller is not receiving Clear Alert Number: None. a consistent response from the Related Alert Number: None. enclosure. There could be a firmware LRA Number: 2091 problem or an invalid cabling configuration. If the cables are too long, they will degrade the signal.
Table 4-4. Storage Management Messages (continued) Event Description ID 2303 2304 2305 118 Related Alert Information SNMP Trap Numbers The enclosure Ok / Normal Cause: This alert is for informational cannot support purposes. both SAS and Action: None SATA physical disks. Physical disks may be disabled. Clear Alert Number: None. 851 An attempt to Ok / Normal Cause: This alert is for informational hot plug an purposes. EMM has been Action: None detected. This type of hot plug is not supported.
Table 4-4. Storage Management Messages (continued) Event Description ID 2306 Severity Cause and Action Bad block table Warning / Cause: The bad block table is used is 80% full. Non-critical for remapping bad disk blocks. This table fills, as bad disk blocks are remapped. When the table is full, bad disk blocks can no longer be remapped, and disk errors can no longer be corrected. At this point, data loss can occur. The bad block table is now 80% full.
Table 4-4. Storage Management Messages (continued) Event Description ID 2310 Severity A virtual disk is Critical / permanently Failure / degraded. Error Cause and Action Related Alert Information Cause: A redundant virtual disk has Clear Alert Number: None. lost redundancy. This may occur Related Alert Number: None. when the virtual disk suffers the failure of multiple physical disks. In LRA Number: 2081 this case, both the source physical disk and the target disk with redundant data have failed.
Table 4-4. Storage Management Messages (continued) Event Description ID 2314 2315 Severity The Critical / initialization Failure / sequence of Error SAS components failed during system startup. SAS management and monitoring is not possible. Diagnostic message %1 Cause and Action Related Alert Information SNMP Trap Numbers Cause: Storage Management is unable to monitor or manage SAS devices. Clear Alert Number: None. 104 Action: Reboot the system.
Table 4-4. Storage Management Messages (continued) Event Description ID Severity 2319 Single-bit ECC error. The DIMM is degrading. Warning / Cause: The DIMM is beginning to Non-critical malfunction. Single-bit ECC error. The DIMM is critically degraded. Critical / Failure / Error Single-bit ECC error. The DIMM is critically degraded. There will be no further reporting. Critical / Failure / Error 2320 2321 2322 Cause and Action Clear Alert Number: None.
Table 4-4. Storage Management Messages (continued) Event Description ID Severity 2323 Ok / Normal Cause: This alert is for informational purposes. The power supply is switched on. Cause and Action Related Alert Information Action: None SNMP Trap Numbers Clear Alert Status: Alert 2323 is 1001 a clear alert for alerts 2313 and 2322. Related Alert Number: None. LRA Number: None. 2324 The AC power Critical / supply cable Failure / has been Error removed.
Table 4-4. Storage Management Messages (continued) Event Description ID Severity 2327 The NVRAM has corrupted data. The controller is reinitializing the NVRAM. Warning / Cause: The NVRAM has corrupted Non-critical data. This may occur after a power surge, a battery failure, or for other reasons. The controller is reinitializing the NVRAM. The NVRAM has corrupt data. Warning / Cause: The NVRAM has corrupt Non-critical data. The controller is unable to correct the situation.
Table 4-4. Storage Management Messages (continued) Event Description ID Severity 2330 Ok / Normal Cause: This alert is for informational Clear Alert Number: None. purposes. The %1 indicates a Related Alert Number: None. substitution variable. The text for this substitution variable is generated LRA Number: None. by the controller and is displayed with the alert in the Alert Log. This text can vary depending on the situation.
Table 4-4. Storage Management Messages (continued) Event Description ID Severity 2335 Warning / Cause: The %1 indicates a Clear Alert Number: None. Non-critical substitution variable. The text for Related Alert Number: None. this substitution variable is generated LRA Number: 2060 by the controller and is displayed with the alert in the Alert Log. This text is from events in the controller event log that were generated while Storage Management was not running.
Table 4-4. Storage Management Messages (continued) Event Description ID 2337 2338 2339 2340 Severity Cause and Action Related Alert Information SNMP Trap Numbers Cause: The controller was unable to recover data from the cache. Clear Alert Number: None. 1154 The controller Ok / Normal Cause: This alert is for informational has recovered purposes. cached data Action: None from the BBU. Clear Alert Number: None. The factory Ok / Normal Cause: This alert is for informational default purposes.
Table 4-4. Storage Management Messages (continued) Event Description ID 2341 Severity Cause and Action The Check Ok / Normal Cause: This alert is for informational Consistency purposes. made Action: None corrections and completed. Related Alert Information SNMP Trap Numbers Clear Alert Number: None. 1201 Related Alert Number: None. LRA Number: None. 2342 The Check Consistency found inconsistent parity data. Data redundancy may be lost.
Table 4-4. Storage Management Messages (continued) Event Description ID Severity Cause and Action Related Alert Information SNMP Trap Numbers 2347 The rebuild Critical / failed due to Failure / errors on the Error source physical disk. Cause: You are attempting to rebuild Clear Alert Number: None. data that resides on a defective disk. Related Alert Number: 2195, Action: Replace the source disk and 2346 restore from backup.
Table 4-4. Storage Management Messages (continued) Event Description ID 2353 Severity Cause and Action The enclosure Ok / Normal Cause: This alert is for informational temperature purposes. has returned to Action: None. normal. Related Alert Information SNMP Trap Numbers Clear Alert Status: Alert 2353 is 851 a clear alert for alerts 2100 and 2101. Related Alert Number: None. LRA Number: None. 2356 SAS SMP Critical / communicatio Failure / ns error %1.
Table 4-4. Storage Management Messages (continued) Event Description ID Severity Cause and Action 2357 Critical / Failure / Error Cause: The %1 indicates a Clear Alert Number: None. substitution variable. The text for Related Alert Number: None. this substitution variable is generated by the firmware and is displayed with LRA Number: 2061 the alert in the Alert Log. This text can vary depending on the situation.
Table 4-4. Storage Management Messages (continued) Event Description ID 2361 2362 2364 2366 132 Severity Cause and Action Related Alert Information SNMP Trap Numbers Physical Ok / Normal Cause: This alert is for informational disk(s) that are purposes. part of a virtual Action: None. disk have been removed while the system was shut down. This removal was discovered during system start-up. Clear Alert Number: None.
Table 4-4. Storage Management Messages (continued) Event Description ID 2367 2368 2369 2371 Severity Cause and Action Related Alert Information SNMP Trap Numbers Cause: The physical disk is using an incompatible technology. Clear Alert Number: None. 903 The SCSI Ok / Normal Cause: This alert is for informational Enclosure purposes. Processor Action: None. (SEP) has been rebooted as part of the firmware download operation and will be unavailable until the operation completes.
Storage Management Message Reference
Index Symbols 1052, 16 1254, 26 %1, Storage Management has lost communication with this RAID controller and attached storage. An immediate reboot is strongly recommended to avoid further problems. If the reboot does not restore communication, there may be a hardware failure.
Index 1503, 35 2053, 66 2095, 74 1504, 35 2054, 66 2098, 74 1505, 35 2055, 66 2099, 75 1550, 36 2056, 67 2100, 75 1551, 36 2057, 68 2101, 75 1552, 36 2058, 68 2102, 76 1553, 36 2059, 68 2103, 76 1554, 36 2061, 69 2104, 76 1555, 36 2062, 69 2105, 76 1600, 37 2063, 69 2106, 77 1601, 37 2064, 69 2107, 77 1602, 37 2065, 69 2108, 78 1603, 38 2067, 70 2109, 79 1604, 38 2070, 70 2110, 80 1605, 38 2074, 70 2111, 80 1650, 39 2076, 71 2112, 80 1651, 39 2077, 71
2130, 86 2164, 93 2202, 101 2131, 86 2165, 93 2203, 101 2132, 87 2166, 94 2204, 102 2135, 87 2167, 94 2205, 102 2136, 87 2168, 94 2206, 102 2137, 88 2169, 95 2207, 103 2138, 88 2170, 95 2211, 103 2139, 89 2171, 95 2212, 103 2140, 89 2173, 96 2213, 103 2141, 89 2174, 96 2214, 103 2142, 89 2175, 96 2215, 104 2143, 89 2176, 97 2232, 104 2144, 89 2177, 97 2233, 104 2145, 90 2178, 97 2234, 104 2146, 90 2179, 97 2235, 104 2147, 90 2180, 98 2237, 104 2148, 90 2181,
Index 2254, 107 2288, 114 2320, 122 2255, 107 2289, 114 2321, 122 2259, 107 2290, 115 2322, 122 2260, 107 2291, 115 2323, 123 2261, 107 2292, 115 2324, 123 2262, 107 2293, 115 2325, 123 2263, 107 2294, 115 2326, 123 2264, 108 2295, 115 2327, 124 2265, 108 2296, 116 2328, 124 2266, 108 2297, 116 2329, 124 2267, 109 2298, 116 2330, 125 2268, 109 2299, 116 2331, 125 2269, 109 2300, 117 2332, 125 2270, 110 2301, 117 2334, 125 2271, 110 2302, 117 2335, 126 2272,
2353, 130 2356, 130 2357, 131 2358, 131 2359, 131 2360, 131 2361, 132 2362, 132 2364, 132 2366, 132 2367, 133 2368, 133 2369, 133 2371, 133 A controller rescan has been initiated., 104 A mirrored virtual disk has been unmirrored, 81 A dedicated hot spare failed., 101 A physical disk is incompatible., 119 A dedicated hot spare has been automatically unassigned., 102 A physical disk is marked as missing., 129 A dedicated hot spare has been removed., 102 A device has been inserted.
Index AC power cord is not being monitored, 34 AC power cord messages, 34 Automatic System Recovery (ASR) action was performed, 14 BMC Watchdog Events, 48 BMC watchdog messages, 48 AC power cord sensor, 7 AC power cord sensor has failed, 34, 50 bios generated system messages, 52 B AC power has been lost, 35 Background initialization cancelled, 86 AC power has been restored, 35 Background initialization completed, 86 All virtual disks are missing from the controller.
Controller battery is reconditioning, 76 Dedicated hot spare assigned. Physical disk %1, 100 Controller battery low, 90 Dedicated hot spare unassigned.
Index Global hot spare unassigned, 75 H hardware log sensor, 7 Hardware Log Sensor Events, 49 hardware log sensor messages, 49 Hot spare SMART polling failed.
R Physical disk initialize failed, 71 Power supply returned to normal, 30, 48 Physical disk inserted, 66 power supply sensor, 6 r2 generated system messages, 55 Physical disk offline, 65 Power supply sensor detected a non-recoverable value, 31 Rebuild completed with errors, 93 Physical disk online, 92 Physical disk rebuild cancelled, 70 Physical disk rebuild completed, 73 Physical disk rebuild failed, 72 Physical disk rebuild started, 69 Physical disk removed, 65 Physical disk(s) have been removed
Index SCSI sense data, 74 SCSI sense sector reassign, 85 See the Readme file for a list of validated controller driver versions, 93 sensor AC power cord, 7 chassis intrusion, 6 current, 6 fan, 6 fan enclosure, 7 hardware log, 7 memory prefailure, 6 power supply, 6 processor, 7, 37 redundancy unit, 6 temperature, 6 voltage, 6 Server Administrator starting, 13 Server Administrator startup complete, 13 Service tag changed, 91 Single-bit ECC error limit exceeded., 98 Single-bit ECC error.
The Check Consistency made corrections and completed., 128 The controller battery Learn cycle has timed out., 97 The Check Consistency rate has changed., 104 The controller battery Learn cycle will start in % days., 98 The Clear operation has cancelled., 107 The controller battery needs to be replaced., 95 The controller alarm is silenced., 104 The controller battery temperature is above normal, 95 The controller battery charge level is below a normal threshold.
Index SAS management and monitoring is not possible., 121 The non-RAID SCSI driver version is older than the minimum required level.See the Readme file for the validated driver version., 94 The NVRAM has corrupt data., 124 The NVRAM has corrupted data. The controller is reinitializing the NVRAM., 124 The physical disk blink has ceased., 106 The physical disk blink has initiated., 106 The physical disk Clear operation failed., 110 The physical disk Clear operation has completed.
U understanding event description, 10 Unsupported configuration detected. The SCSI rate of the enclosure management modules (EMMs) is not the same. EMM0 %1 EMM1 %2, 96 User initiated host system reset, 14 Virtual disk format changed, 71 Voltage sensor detected a non-recoverable value, 21 Virtual disk format completed, 73 Voltage sensor detected a warning value, 20 Virtual disk format started, 68 Voltage Sensor Events, 44 Virtual disk has inconsistent data.
Index 148 Index
