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–2006 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 . . . . . . . . . . . . . . . . . . . . . . . 7 . . . . . . . . 8 . . . .
Processor Sensor Messages . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Pluggable Device Messages . . . . . . . . . . . . . . . . . . . . . . . . . . 39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Battery Sensor Messages 3 System Event Log Messages for IPMI Systems . . . . . . . . . 43 . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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.0 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. Warning A temperature sensor on the backplane board, system board, or drive carrier in the specified system exceeded its warning threshold.
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 on the power supply for 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 on the power supply for 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 on the power supply for the specified system exceeded its warning threshold.
Table 2-5. Current Sensor Messages (continued) Event ID Description Severity Cause 1204 Error A current sensor on the power supply for 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, connectors, array 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.
NOTE: If you have an Array Manager installation, the Array Manager console reports the status of storage components through error icons and graphical displays. When there is a change in status, Array Manager sends events to the Array Manager event log, which can be viewed from the Array Manager console. For more information, see the Array Manager User's Guide. For more information regarding alert descriptions and the appropriate corrective actions, see the online help. Table 4-1.
Table 4-1. Storage Management Messages (continued) Event ID Description Severity 2050 Warning / Cause: A physical disk in the array is offline. Non-critical A disk can be made offline during a Prepare to Remove operation or because a user manually put the disk offline. Array disk offline Cause and Action SNMP Trap Array Numbers Manager Event Number 903 502 Warning / Cause: An array disk has reported an error 903 Non-critical condition and may be degraded.
Table 4-1. Storage Management Messages (continued) Event ID Description Severity Cause and Action 2056 Critical / Failure / Error Cause: One or more physical disks included 1204 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.
Table 4-1. Storage Management Messages (continued) Event ID Description Severity 2059 Ok / Normal Cause: This alert is provided for informational 1201 purposes. Virtual disk format started Cause and Action SNMP Trap Array Numbers Manager Event Number 521 Action: None 2061 Virtual disk initialization started Ok / Normal Cause: This alert is provided for informational 1201 purposes.
Table 4-1. Storage Management Messages (continued) Event ID Description Severity 2070 Ok / Normal Cause: The virtual disk initialization cancelled 1201 because a physical disk included in the virtual disk has failed or because a user cancelled the virtual disk initialization. Virtual disk initialization cancelled Cause and Action SNMP Trap Array Numbers Manager Event Number 532 Action: If a physical disk failed, then replace the physical disk.
Table 4-1. Storage Management Messages (continued) Event ID Description Severity Cause and Action 2080 Critical / Failure / Error Cause: The array disk has failed or is corrupt. 904 2081 Array disk initialize failed Virtual disk Critical / reconfiguration failed Failure / Error SNMP Trap Array Numbers Manager Event Number 542 Action: Replace the failed or corrupt disk. You can identify a disk that has failed by locating the disk that has a red “X” for its status. Restart the initialization.
Table 4-1. Storage Management Messages (continued) Event ID Description Severity 2088 Virtual disk initialization completed Ok / Normal Cause: This alert is provided for informational purposes. Array disk initialize completed Ok / Normal Cause: This alert is provided for informational purposes. 2089 Cause and Action SNMP Trap Array Numbers Manager Event Number 1201 550 901 551 1201 552 1201 553 901 554 Cause: The array disk is predicted to fail.
Table 4-1. Storage Management Messages (continued) Event ID Description 2095 2098 Severity SCSI sense data. If Warning / this disk is part of a Non-critical redundant virtual disk, select the ‘Offline’ option and then replace the disk. Then configure a hot spare and it will start the rebuild automatically. If this disk is a hot spare, select the ‘Prepare to Remove’ option and then replace the disk. If this disk is part of a non-redundant disk, you should back up your data immediately.
Table 4-1. Storage Management Messages (continued) Event ID Description Severity 2100 Warning / Cause: The array disk enclosure is too hot. Non-critical 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. Temperature exceeded the maximum warning threshold Cause and Action SNMP Trap Array Numbers Manager Event Number 1053 591 1053 592 Cause: The array disk enclosure is too hot.
Table 4-1. Storage Management Messages (continued) Event ID Description Severity 2104 Ok / Normal Cause: This alert is provided for informational purposes. Controller battery is reconditioning Cause and Action SNMP Trap Array Numbers Manager Event Number 1151 581 1151 582 Action: None 2105 2106 Controller battery recondition is completed Ok / Normal Cause: This alert is provided for informational purposes.
Table 4-1. Storage Management Messages (continued) Event ID Description Severity 2108 Warning / Cause: A disk has received a SMART alert 903 Non-critical (predictive failure). The disk is likely to fail in the near future. Smart warning Cause and Action SNMP Trap Array Numbers Manager Event Number 587 Action: Replace the disk that has received the SMART alert. If the array disk is a member of a non-redundant virtual disk, then back up the data before replacing the disk.
Table 4-1. Storage Management Messages (continued) Event ID Description Severity 2110 Warning / Cause: A disk is degraded and has received a 903 Non-critical SMART alert (predictive failure). The disk is likely to fail in the near future. SMART warning degraded Cause and Action SNMP Trap Array Numbers Manager Event Number 589 Action: Replace the disk that has received the SMART alert. If the array disk is a member of a non-redundant virtual disk, then back up the data before replacing the disk.
Table 4-1. Storage Management Messages (continued) Event ID Description Severity 2115 Ok / Normal Cause: The check consistency operation on a 1201 virtual disk has resumed processing after being paused by a user. A consistency check on a virtual disk has been resumed Cause and Action SNMP Trap Array Numbers Manager Event Number 605 Action: This alert is provided for informational purposes.
Table 4-1. Storage Management Messages (continued) Event ID Description Severity 2120 Warning / Cause: The firmware on the enclosure 853 Non-critical management modules (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.
Table 4-1. Storage Management Messages (continued) Event ID Description Severity 2123 Warning / Cause: A virtual disk or an enclosure has lost 1306 Non-critical data redundancy. In the case of a virtual disk, one or more array disks included in the virtual disk have failed. Due to the failed array disk or disks, the virtual disk is no longer maintaining redundant (mirrored or parity) data. The failure of an additional array disk will result in lost data.
Table 4-1. Storage Management Messages (continued) Event ID Description Severity 2126 Warning / Cause: A sector of the disk is corrupted and 903 Non-critical data cannot be maintained on this portion of the disk. SCSI sense sector reassign Cause and Action SNMP Trap Array Numbers Manager Event Number None Action: If the disk is part of a non-redundant virtual disk, then replace the disk. Any data residing on the corrupt portion of the disk may be lost and you may need to restore from backup.
Table 4-1. Storage Management Messages (continued) Event ID Description Severity 2132 Warning / Cause: The controller driver is not a Non-critical supported version. Driver version mismatch Cause and Action SNMP Trap Array Numbers Manager Event Number 753 None Warning / Cause: Storage Management has been installed 103 Non-critical on a system that has an Array Manager installation. None Action: Install a supported version of the driver.
Table 4-1. Storage Management Messages (continued) Event ID Description Severity 2137 Warning / Cause: The controller is unable to communicate 853 Non-critical 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.
Table 4-1. Storage Management Messages (continued) Event ID Description Severity 2141 Ok / Normal Cause: Portions of the array disk that were formerly inaccessible have been recovered. This alert is provided for informational purposes. Array disk dead segments recovered Cause and Action SNMP Trap Array Numbers Manager Event Number 901 None 751 680 Ok / Normal Cause: A user has enabled the controller 751 alarm. This alert is provided for informational purposes.
Table 4-1. Storage Management Messages (continued) Event ID Description Severity Cause and Action SNMP Trap Array Numbers Manager Event Number 2149 Bad block extended sense error Warning / Cause: A portion of an array disk is damaged. 753 Non-critical Action: See the Dell OpenManage Storage Management Online Help for more information. 691 2150 Bad block extended medium error Warning / Cause: A portion of an array disk is damaged.
Table 4-1. Storage Management Messages (continued) Event ID Description Severity 2156 Ok / Normal Cause: The controller alarm test has run successfully. This alert is provided for informational purposes. Controller alarm has been tested Cause and Action SNMP Trap Array Numbers Manager Event Number 751 None 751 None Ok / Normal Cause: An offline array disk has been made 901 online. This alert is provided for informational purposes.
Table 4-1. Storage Management Messages (continued) Event ID Description Severity 2162 Ok / Normal Cause: Communication with an enclosure has been restored. This alert is provided for informational purposes. Communication regained Cause and Action SNMP Trap Array Numbers Manager Event Number 851 None Action: None 2163 Rebuild completed with errors Ok / Normal See the online help for more information.
Table 4-1. Storage Management Messages (continued) Event ID Description 2167 Severity The current kernel Warning / version and the non- Non-critical RAID SCSI driver version are older than the minimum required levels. See the Readme file for a list of validated kernel and driver versions. 2168 The non-RAID SCSI Warning / driver version is older Non-critical than the minimum required level. See the Readme file for the validated driver version.
Table 4-1. Storage Management Messages (continued) Event ID Description 2171 Severity Cause and Action SNMP Trap Array Numbers Manager Event Number The controller battery Warning / Cause: The battery may be recharging, the 1153 temperature is above Non-critical room temperature may be too hot, or the fan normal. in the system may be degraded or failed. None Action: If this alert was generated due to a battery recharge, the situation will correct when the recharge is complete.
Table 4-1. Storage Management Messages (continued) Event ID Description 2178 Severity Cause and Action SNMP Trap Array Numbers Manager Event Number The controller battery Warning / Cause: The controller battery must be fully 1153 Learn cycle has Non-critical charged before the Learn cycle can begin. timed out. The battery may be unable to maintain a full charge causing the Learn cycle to timeout.
Table 4-1. Storage Management Messages (continued) Event ID Description Severity Cause and Action SNMP Trap Array Numbers Manager Event Number 2181 The controller battery Ok / Normal Cause: This alert is provided for Learn cycle will start informational purposes. in % hours. Action: None NOTE: The % is a variable that will be replaced with the number of hours before which the Learn cycle will start. You can set the duration to start the Learn cycle.
Table 4-1. Storage Management Messages (continued) Event ID Description Severity 2188 Warning / Cause: The controller battery is unable to 1153 Non-critical maintain cached data for the required period of time. For example, if the required period of time is 24 hours, the battery is unable to maintain cached data for 24 hours. It is normal to receive this alert during the battery Learn cycle as the Learn cycle discharges the battery before recharging it.
Table 4-1. Storage Management Messages (continued) Event ID Description Severity 2193 Ok / Normal Cause: This alert is provided for informational purposes. 2194 The virtual disk reconfiguration has resumed. Cause and Action SNMP Trap Array Numbers Manager Event Number 1201 None 1201 None 1201 None Action: None The virtual disk Read Ok / Normal Cause: This alert is provided for policy has changed. informational purposes.
Table 4-1. Storage Management Messages (continued) Event ID Description 2204 Severity Cause and Action SNMP Trap Array Numbers Manager Event Number A dedicated hot spare Warning / Cause: The controller is unable to communicate 903 has been removed. Non-critical 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. None Action: Check if the disk is healthy and that it has not been removed. Check the cables.
Table 4-1. Storage Management Messages (continued) Event ID Description Severity 2211 Warning / Cause: The physical disk may not have a 903 Non-critical supported version of the firmware or the disk may not be supported by Dell. The physical disk is not supported. Cause and Action SNMP Trap Array Numbers Manager Event Number None Action: If the disk is supported by Dell, update the firmware to a supported version. If the disk is not supported by Dell, replace the disk with one that is supported.
Table 4-1. Storage Management Messages (continued) Event ID Description Severity 2241 Ok / Normal Cause: This alert is provided for informational purposes. The Patrol Read mode has changed. Cause and Action SNMP Trap Array Numbers Manager Event Number 751 None 751 None 751 None 1201 None 1201 None 2246 The controller battery Warning / Cause: The controller battery charge is weak. 1153 is degraded.
Table 4-1. Storage Management Messages (continued) Event ID Description Severity 2251 Ok / Normal Cause: This alert is provided for informational purposes. The array disk blink has initiated. Cause and Action SNMP Trap Array Numbers Manager Event Number 901 None 901 None 901 None 901 None 851 None 851 None 101 None 101 None 101 None Action: None 2252 The array disk blink has ceased. Ok / Normal Cause: This alert is provided for informational purposes.
Table 4-1. Storage Management Messages (continued) Event ID Description Severity 2264 Warning / Cause: The controller cannot communicate Non-critical with a device. The device may be removed. There may also be a bad or loose cable. A device is missing. Cause and Action Action: Check if the device is in and not removed. If it is in, check the cables. You should also check the connection to the controller battery and the battery health. A battery with a weak or depleted charge may cause this alert.
Table 4-1. Storage Management Messages (continued) Event ID Description 2268 2269 2270 Severity %1, Storage Critical / Management has lost Failure / communication with Error 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. NOTE: %1 is a substitution variable that will appear in the alert description for specific details about the alert.
Table 4-1. Storage Management Messages (continued) Event ID Description 2272 Severity Patrol Read found an Critical / uncorrectable media Failure / error. Error Cause and Action SNMP Trap Array Numbers Manager Event Number Cause: The Patrol Read task has faced an 903 error that cannot be corrected. There may be a bad disk block that cannot be remapped. None Action: Replace the array disk to avoid future data loss. 2273 Bad media.
Table 4-1. Storage Management Messages (continued) Event ID Description 2278 Severity Cause and Action SNMP Trap Array Numbers Manager Event Number The controller battery Ok / Normal Cause: The battery is discharging. A battery 1154 charge level is below discharge is a normal activity during the a normal threshold. battery Learn cycle. Before completing, the battery Learn cycle recharges the battery. You should receive alert 2179 when the recharge occurs.
Table 4-1. Storage Management Messages (continued) Event ID Description Severity Cause and Action 2282 Critical / Failure / Error Cause: The controller firmware attempted a 904 SMART polling on the hot spare but was unable to complete it. The controller has lost communication with the hot spare. Hot spare SMART polling failed. SNMP Trap Array Numbers Manager Event Number None Action: Check the health of the disk assigned as a hot spare. You may need to replace the disk and reassign the hot spare.
Table 4-1. Storage Management Messages (continued) Event ID Description Severity Cause and Action 2289 Critical / Failure / Error Cause: An error involving multiple bits has 754 been encountered during a read or write operation. The error correction algorithm recalculates parity data during read and write operations. If an error involves only a single bit, it may be possible for the error correction algorithm to correct the error and maintain parity data.
Table 4-1. Storage Management Messages (continued) Event ID Description 2293 Severity The EMM has failed. Critical / Failure / Error Cause and Action SNMP Trap Array Numbers Manager Event Number Cause: The failure may be caused by a loss of 854 power to the EMM. The EMM self test may also have identified a failure. There could also be a firmware problem or a multi-bit error. None Action: Replace the EMM. See the hardware documentation for information on replacing the EMM.
Table 4-1. Storage Management Messages (continued) Event ID Description Severity Cause and Action SNMP Trap Array Numbers Manager Event Number 2299 Critical / Failure / Error Cause: There is a problem with a physical connection or PHY. 854 None Critical / Failure / Error Cause: The controller is not receiving a 854 consistent response from the enclosure. There could be a firmware problem or an invalid cabling configuration. If the cables are too long, they will degrade the signal.
Table 4-1. Storage Management Messages (continued) Event ID Description Severity Cause and Action SNMP Trap Array Numbers Manager Event Number 2303 The enclosure cannot Ok / Normal Cause: This alert is provided for support both SAS and informational purposes. SATA array disks. Action: None Array disks may be disabled. 851 None 2304 An attempt to hot Ok / Normal Cause: This alert is provided for plug an EMM has informational purposes. been detected.
Table 4-1. Storage Management Messages (continued) Event ID Description Severity 2309 Warning / Cause: You have attempted to replace a disk 903 Non-critical with another disk that is using an incompatible technology. For example, you may have replaced one side of a mirror with a SAS disk when the other side of the mirror is using SATA technology. An array disk is incompatible.
Table 4-1. Storage Management Messages (continued) Event ID Description Severity Cause and Action SNMP Trap Array Numbers Manager Event Number 2314 Critical / Failure / Error Cause: Storage Management is unable to monitor or manage SAS devices. 104 None 751 None Cause: A diagnostics test failed. The text for 754 this alert is generated by the utility that ran the diagnostics. None Action: Reboot the system. If problem persists, make sure you have supported versions of the drivers and firmware.
Table 4-1. Storage Management Messages (continued) Event ID Description Severity Cause and Action SNMP Trap Array Numbers Manager Event Number 2319 Single-bit ECC error. Warning / Cause: The DIMM is beginning to 753 The DIMM is Non-critical malfunction. degrading. Action: Replace the DIMM to avoid data loss or data corruption. The DIMM is a part of the controller battery pack. See your hardware documentation for information on replacing the DIMM. None 2320 Single-bit ECC error.
Table 4-1. Storage Management Messages (continued) Event ID Description 2324 Severity The AC power supply Critical / cable has been Failure / removed. Error Cause and Action SNMP Trap Array Numbers Manager Event Number Cause: The power cable may be pulled out or removed. The power cable may also have overheated and become warped and nonfunctional. 1004 None 1001 None Action: Replace the power cable. 2325 2326 The power supply cable has been inserted.
Table 4-1. Storage Management Messages (continued) Event ID Description Severity 2329 Warning / Cause: The text for this alert is generated by 753 Non-critical the controller and can vary depending on the situation. SAS port report: %1 NOTE: %1 is a substitution variable that will appear in the alert description for specific details about the alert. 2330 SAS port report: %1 NOTE: %1 is a substitution variable that will appear in the alert description for specific details about the alert.
Table 4-1. Storage Management Messages (continued) Event ID Description Cause and Action 2334 Controller event Ok / Normal Cause: This alert is provided for log: %1 informational purposes. NOTE: %1 is a Action: None substitution variable that will appear in the alert description for specific details about the alert.
Table 4-1. Storage Management Messages (continued) Event ID Description Severity Cause and Action SNMP Trap Array Numbers Manager Event Number 2338 The controller has Ok / Normal Cause: This alert is provided for recovered cached data informational purposes. from the BBU. Action: None 1151 None 2339 The factory default settings have been restored. Ok / Normal Cause: This alert is provided for informational purposes. 751 None The BGI completed with uncorrectable errors.
Table 4-1. Storage Management Messages (continued) Event ID Description Severity 2344 The virtual disk initialization terminated. Warning / Cause: A user has cancelled the virtual disk Non-critical initialization. The virtual disk initialization failed. Critical / Failure / Error 2345 Cause and Action SNMP Trap Array Numbers Manager Event Number 1203 None 1204 None Action: Restart the initialization. Cause: The controller cannot communicate with the attached devices.
Table 4-1. Storage Management Messages (continued) Event ID Description Severity Cause and Action 2349 Critical / Failure / Error Cause: A write operation could not complete 904 because the disk contains bad disk blocks that could not be reassigned. Data loss may have occurred and data redundancy may also be lost. A bad disk block could not be reassigned during a write operation. SNMP Trap Array Numbers Manager Event Number None Action: Replace the disk.
Table 4-1. Storage Management Messages (continued) Event ID Description 2355 2356 108 Severity Cause and Action SNMP Trap Array Numbers Manager Event Number Enclosure firmware Warning / download failed.The Non-critical system was unable to download firmware to the enclosure. The controller may have lost communication with the enclosure. There may have been problems with the data transfer or the download media may be corrupt. Cause: The system was unable to download 853 firmware to the enclosure.
Table 4-1. Storage Management Messages (continued) Event ID Description 2357 2358 Severity SAS expander Critical / error: %1 Failure / Error NOTE: %1 is a substitution variable that will appear in the alert description for specific details about the alert. The battery charge cycle is complete. Cause and Action SNMP Trap Array Numbers Manager Event Number Cause: The text for this alert is generated by 754 the firmware and can vary depending on the situation.
Table 4-1. Storage Management Messages (continued) Event ID Description Cause and Action SNMP Trap Array Numbers Manager Event Number 2363 A virtual disk and all Ok / Normal Cause: This alert is provided for of its member array informational purposes. disks have been Action: None. removed while the system was shut down. This removal was discovered during system start-up. 751 None 2364 All virtual disks are missing from the controller. This situation was discovered during system start-up.
Index Numerics 1150, 19 1351, 29 0001, 13 1151, 20 1352, 30 1000, 13 1152, 20 1353, 30 1001, 13 1153, 20 1354, 31 1002, 13 1154, 21 1355, 31 1003, 13 1155, 21 1403, 32 1004, 13 1200, 22 1404, 32 1005, 14 1201, 22 1450, 33 1006, 14 1202, 23 1451, 33 1007, 14 1203, 23 1452, 33 1008, 14 1204, 24 1453, 33 1009, 14 1205, 24 1454, 34 1011, 14 1250, 25 1455, 34 1012, 14 1251, 25 1500, 34 1050, 15 1252, 25 1501, 34 1051, 15 1253, 26 1502, 35 1052, 16 1254, 26 1503,
Index 1601, 37 2065, 61 2108, 68 1602, 37 2067, 61 2109, 68 1603, 38 2070, 62 2110, 69 1604, 38 2074, 62 2111, 69 1605, 38 2076, 62 2112, 69 1650, 39 2077, 62 2114, 69 1651, 39 2079, 62 2115, 70 1652, 39 2080, 63 2116, 70 1653, 39 2081, 63 2117, 70 1700, 40 2082, 63 2118, 70 1701, 40 2083, 63 2120, 71 1702, 40 2085, 63 2121, 71 1703, 40 2086, 63 2122, 71 1704, 41 2088, 64 2123, 72 1705, 41 2089, 64 2124, 72 2048, 58 2090, 64 2126, 73 2049, 58 2091, 64
2143, 76 2175, 81 2238, 87 2144, 76 2176, 81 2239, 87 2145, 76 2177, 81 2240, 87 2146, 76 2178, 82 2241, 88 2147, 76 2179, 82 2242, 88 2148, 76 2180, 82 2243, 88 2149, 77 2181, 83 2244, 88 2150, 77 2182, 83 2245, 88 2151, 77 2186, 83 2246, 88 2152, 77 2187, 83 2247, 88 2153, 77 2188, 84 2248, 88 2154, 77 2189, 84 2249, 88 2155, 77 2191, 84 2251, 89 2156, 78 2192, 84 2252, 89 2157, 78 2193, 85 2254, 89 2158, 78 2194, 85 2255, 89 2159, 78 2199, 85 2259, 89 21
Index 2273, 92 2304, 98 2335, 104 2274, 92 2305, 98 2336, 104 2276, 92 2306, 98 2337, 104 2277, 92 2307, 98 2338, 105 2278, 93 2309, 99 2339, 105 2279, 93 2310, 99 2340, 105 2280, 93 2311, 99 2341, 105 2281, 93 2312, 99 2342, 105 2282, 94 2313, 99 2343, 105 2283, 94 2314, 100 2344, 106 2284, 94 2315, 100 2345, 106 2285, 94 2316, 100 2346, 106 2286, 94 2317, 100 2347, 106 2287, 94 2318, 100 2348, 106 2288, 94 2319, 101 2349, 107 2289, 95 2320, 101 2350, 10
2365, 110 Array Disk degraded, 59 2366, 110 Array disk initialize completed, 64 2367, 110 2368, 110 A A consistency check on a virtual disk has been paused (suspended), 69 A consistency check on a virtual disk has been resumed, 70 Array disk initialize failed, 63 Bad block extended sense error, 77 Array disk inserted, 59 Bad block medium error, 76 Array disk offline, 59 Bad block replacement error, 76 Array disk online, 78 Array disk rebuild cancelled, 62 Array disk rebuild completed, 64 Array d
Index Chassis intrusion sensor value unknown, 25, 47 Communication timeout, 75 Controller alarm disabled, 76 D Dead disk segments restored, 75 Fan enclosure removed from system for an extended amount of time, 34 fan enclosure sensor, 7 Controller alarm enabled, 76 Dedicated hotspare assigned, 78 Controller alarm has been tested, 78 Dedicated hotspare unassigned, 78 Controller battery is reconditioning, 67 Device failed, 58 Controller battery low, 76 Drive Events, 50 Fan enclosure sensor val
H hardware log sensor, 7 Hardware Log Sensor Events, 49 hardware log sensor messages, 49 Memory device ECC Correctable error count sensor crossed a failure threshold, 32 memory device messages, 32 Memory device monitoring has been disabled, 32 Memory ECC Events, 48 messages (continued) processor status, 46 r2 generated system, 55 redundancy unit, 26 storage management, 58 temperature sensor, 15, 43 voltage sensor, 19, 44 Minimum temperature probe warning threshold value changed, 77 I memory ecc messages
Index Processor sensor detected a failure value, 38, 52 Processor sensor detected a non-recoverable value, 38 Processor sensor detected a warning value, 38, 52 Processor sensor has failed, 37, 52 Processor sensor returned to a normal state, 37, 52 Processor sensor value unknown, 37, 52 Processor Status Events, 46 processor status messages, 46 S SCSI sense data, 65 SCSI sense sector reassign, 73 sensor AC power cord, 7 chassis intrusion, 6 current, 6 fan, 6 fan enclosure, 7 hardware log, 7 memory pref
Temperature sensor returned to a normal value, 16, 43 Temperature sensor value unknown, 15, 43 Thermal shutdown protection has been initiated, 13 Virtual disk deleted, 59 Virtual disk failed, 60 Virtual disk format changed, 62 Virtual disk format completed, 63 Virtual disk format started, 61 U Virtual disk initialization, 74 understanding event description, 10 Virtual disk initialization cancelled, 62 User initiated host system reset, 14 Virtual disk initialization completed, 64 Voltage sensor detec
Index 120 Index