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–2005 Dell Inc. All rights reserved. Reproduction in any manner whatsoever without the written permission of Dell Inc. is strictly forbidden.
Contents 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7 What’s New in this Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . Messages Not Described in This Guide . Understanding Event Messages . . . . . . . . . . . . . . . . . . . . . . 7 . . . . . . . . . . . . . . . . . . . . . . . . . 8 Viewing Alerts and Event Messages 2 7 . . . . . . . . . . . . . . . . . . . . . . . 9 Event Message Reference . . . . . . . . . . . . . . .
3 System Event Log Messages for IPMI Systems . . . . . . . . . . . .37 Temperature Sensor Events . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Voltage Sensor Events . Fan Sensor Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 . . . . . . . . . . . . . . . . . . . . . . . . . . .
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 2.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. • In the Red Hat® Enterprise Linux operating system, messages are logged to the system log file.
...
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 list 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 management BIOS 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 non-responsive operating system. The action performed and the time of action are provided.
Table 2-2. Temperature Sensor Messages Event ID Description Severity Cause 1050 Information A temperature sensor on the backplane board, system board, or the carrier in the specified system failed. The sensor location, chassis location, previous state, and temperature sensor value are provided. Information A temperature sensor on the backplane board, system board, or drive carrier in the specified system could not obtain a reading.
Table 2-2. Temperature Sensor Messages (continued) Event ID Description Severity Cause 1053 Warning A temperature sensor on the backplane board, system board, or drive carrier in the specified system exceeded its warning 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 exceeded its failure threshold.
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 1105 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 1152 Information A voltage sensor in the specified system returned to a valid range after crossing a failure threshold. The sensor location, chassis location, previous state, and voltage sensor value are provided. Warning A voltage sensor in the specified system exceeded its warning threshold. The sensor location, chassis location, previous state, and voltage sensor value are provided.
Table 2-4. Voltage Sensor Messages (continued) Event ID Description Severity Cause 1155 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.
Table 2-5. Current Sensor Messages (continued) Event ID Description Severity Cause 1201 Information A current sensor on the power supply for the specified system could not obtain a reading. The sensor location, chassis location, previous state, and a nominal current sensor value are provided. Information A current sensor on the power supply for the specified system returned to a valid range after crossing a failure 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 Severity Cause 1250 Information A chassis intrusion sensor in the specified system failed. The sensor location, chassis location, previous state, and chassis intrusion state are provided.
Table 2-6. Chassis Intrusion Messages (continued) Event ID Description Severity Cause 1254 Error A chassis intrusion sensor in the specified system detected that the system cover was opened while the system was operating. The sensor location, chassis location, previous state, and chassis intrusion state are provided. Error A chassis intrusion sensor in the specified system detected an error from which it cannot recover.
Table 2-7. Redundancy Unit Messages (continued) Event ID Description Severity Cause 1301 Redundancy sensor value unknown Information A redundancy sensor in the specified system could not obtain a reading. The redundancy unit location, chassis location, previous redundancy state, and the number of devices required for full redundancy are provided. Information A redundancy sensor in the specified system detected that a unit was not redundant.
Table 2-7. Redundancy Unit Messages (continued) Event ID Description Severity Cause 1305 Redundancy degraded Warning A redundancy sensor in the specified system detected that one of the components of the redundancy unit has failed but the unit is still redundant. The redundancy unit location, chassis location, previous redundancy state, and the number of devices required for full redundancy are provided.
Table 2-8. Power Supply Messages (continued) Event ID Description Severity Cause 1351 Information A power supply sensor in the specified system could not obtain a reading. The sensor location, chassis location, previous state, and additional power supply status information are provided. Information A power supply has been reconnected or replaced. The sensor location, chassis location, previous state, and additional power supply status information are provided.
Table 2-8. Power Supply Messages (continued) Event ID Description Severity Cause 1354 Error A power supply has been disconnected or has failed. The sensor location, chassis location, previous state, and additional power supply status information are provided. Error A power supply sensor in the specified system detected an error from which it cannot recover. The sensor location, chassis location, previous state, and additional power supply status information are provided.
Table 2-9. Memory Device Messages Event ID Description Severity Cause 1403 Warning A memory device correction rate exceeded an acceptable value. The memory device status and location are provided. Error A memory device correction rate exceeded an acceptable value, a memory spare bank was activated, or a multibit ECC error occurred. The system continues to function normally (except for a multibit error).
Table 2-10. Fan Enclosure Messages (continued) Event ID Description Severity Cause 1453 Warning A fan enclosure has been removed from the specified system. The sensor location and chassis location are provided. 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.
Table 2-11. AC Power Cord Messages (continued) Event ID Description Severity Cause 1503 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. Error An AC power cord has lost its power, and lack of redundancy requires this to be classified as an error. The sensor location and chassis location information are provided.
Table 2-12. Hardware Log Sensor Messages (continued) Event ID Description Severity 1552 Log type: 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. Log size is near or at capacity Warning The size of a hardware log on the specified system is near or at the capacity of the hardware log. The log type information is provided.
Table 2-13. Processor Sensor Messages (continued) Event ID Description 1602 Severity Cause Information A processor sensor in the specified system transitioned back to a normal state. The sensor location, Sensor location: chassis location, previous state and Chassis location: 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 1650 Severity Cause Information A pluggable device event message of unknown type was received.
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. For example, "CMOS Battery.
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 Cause Fan 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 Event Message Severity Cause status processor Critical sensor IERR, where is the processor that generated the event. For example, PROC for a single processor system and PROC # for multiprocessor system.
Table 3-5. Power Supply Events (continued) Event Message Severity Cause PS Redundancy sensor redundancy degraded. Information Power supply redundancy is degraded if one of the power supply sources is removed or failed. PS Redundancy sensor redundancy lost. Critical Power supply redundancy is lost if only one power supply is functional. PS Redundancy sensor redundancy regained.
BMC Watchdog Events The BMC watchdog operations are performed when the system hangs or crashes. These messages monitor the status and occurrence of these events in a system. Table 3-7. BMC Watchdog Events Event Message Severity Cause BMC OS Watchdog timer expired. Information This event is generated when the BMC watchdog timer expires and no action is set. BMC OS Watchdog performed system reboot.
Table 3-8. Memory Events (continued) Event Message Severity Cause Memory Mirrored redundancy regained. Information This event is generated when the redundancy lost or degraded earlier is regained in a mirrored memory configuration. Memory Spared redundancy degraded. Information This event is generated when there is a memory failure in a spared memory configuration. Memory Spared redundancy lost. Critical This event is generated when redundancy is lost in a spared memory configuration.
Intrusion Events The chassis intrusion messages are a security measure. Chassis intrusion alerts are generated when the system's chassis is opened. Alerts are sent to prevent unauthorized removal of parts from the chassis. Table 3-11. Intrusion Events Event Message Severity Cause sensor detected an intrusion. Critical This event is generated when the intrusion sensor detects an intrusion. sensor returned to normal state.
Storage Management Message Reference 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. If you stop the Storage Management Service, then alert monitoring and logging stops.
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 Dell OpenManage™ 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. 903 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 502 Action: Perform a rescan. You can also select the offline disk and perform a Make Online operation.
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 Cause and Action SNMP Trap Array Numbers Manager Event Number 2059 Ok / Normal Cause: This alert is provided for informational purposes. 1201 521 1201 523 1201 525 1201 526 901 527 Virtual disk format started Action: None 2061 Virtual disk initialization started Ok / Normal Cause: This alert is provided for informational purposes.
Table 4-1. Storage Management Messages (continued) Event ID Description Severity Cause and Action 2070 Ok / Normal Cause: The virtual disk initialization 1201 cancelled because a physical disk included in the virtual disk has failed or because a user cancelled the virtual disk initialization. Virtual disk initialization cancelled 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 Cause and Action SNMP Trap Array Numbers Manager Event Number 2088 Virtual disk initialization completed Ok / Normal Cause: This alert is provided for informational purposes. 1201 550 Array disk initialize completed Ok / Normal 901 551 1201 552 1201 553 901 554 903 570 2089 Action: None Cause: This alert is provided for informational purposes.
Table 4-1. Storage Management Messages (continued) Event ID Description 2095 2098 Severity Cause and Action SNMP Trap Array Numbers Manager Event Number 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.
Table 4-1. Storage Management Messages (continued) Event ID Description Severity 2100 Warning / Cause: The array disk enclosure is too hot. 1053 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 591 Action: Check for factors that may cause overheating.
Table 4-1. Storage Management Messages (continued) Event ID Description Severity Cause and Action SNMP Trap Array Numbers Manager Event Number 2104 Ok / Normal Cause: This alert is provided for informational purposes. 1151 581 1151 582 Controller battery is reconditioning 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 2109 Warning / Cause: A disk has reached an unacceptable 903 Non-critical temperature and received a SMART alert (predictive failure). The disk is likely to fail in the near future. Smart warning temperature Cause and Action SNMP Trap Array Numbers Manager Event Number 588 First Action: Determine why the array disk has reached an unacceptable temperature. A variety of factors can cause the excessive temperature.
Table 4-1. Storage Management Messages (continued) Event ID Description Severity 2111 Failure prediction threshold exceeded due to test - No action needed Warning / Cause: A disk has received a SMART alert Non-critical (predictive failure) due to test conditions.
Table 4-1. Storage Management Messages (continued) Event ID Description 2116 Severity A virtual disk and its Ok / mirror have been split Normal Cause and Action SNMP Trap Array Numbers Manager Event Number Cause: A user has caused a mirrored virtual 1201 disk to be split. When a virtual disk is mirrored, its data is copied to another virtual disk in order to maintain redundancy.
Table 4-1. Storage Management Messages (continued) Event ID Description Severity Cause and Action SNMP Trap Array Numbers Manager Event Number 2121 Ok / Normal Cause: A device that was previously in an error state has returned to a normal state. For example, if an enclosure became too hot and subsequently cooled down, then you may receive this alert. 752, 802, None 852, 902, 952, 1002, 1052, 1102, 1152, 1202 Device returned to normal Action: This alert is provided for informational purposes.
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 103 None 1201 None Action: Install a supported version of 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-1. Storage Management Messages (continued) Event ID Description Severity 2137 Warning / Cause: The controller is unable to 853 Non-critical communicate with an enclosure. There are several reasons why communcation 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 Cause and Action SNMP Trap Array Numbers Manager Event Number 2141 Ok / Normal Cause: Portions of the array disk that were formerly inaccessible have been recovered. This alert is provided for informational purposes. 901 None 751 680 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 2150 Bad block extended medium error Warning / Cause: A portion of an array disk is damaged. 753 Non-critical Action: See the online help for more information. 691 2151 Asset tag changed Ok / Normal 851 None 851 None Warning / Cause: An enclosure service tag was changed.
Table 4-1. Storage Management Messages (continued) Event ID Description Severity Cause and Action SNMP Trap Array Numbers Manager Event Number 2157 Ok / Normal Cause: A user has reset the controller configuration. See the online help for more information. This alert is provided for informational purposes. 751 None 901 None Controller configuration has been reset Action: None 2158 Array disk online Ok / Normal Cause: An offline array disk has been made online.
Table 4-1. Storage Management Messages (continued) Event ID Description Severity Cause and Action SNMP Trap Array Numbers Manager Event Number 2163 Rebuild completed with errors Ok / Normal See the online help for more information. 904 690 2164 See the Readme file for a list of validated controller driver versions Ok / Normal Cause: Storage Management is unable to determine whether the system has the minimum required versions of the RAID controller drivers.
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 2181 2182 2186 Severity Cause and Action SNMP Trap Array Numbers Manager Event Number The controller battery Ok / Learn cycle will start Normal in % hours. NOTE: The %1 is a variable that will be filled in with the number of hours before which the Learn cycle will start. You can set the duration to start the Learn cycle. Cause: This alert is provided for informational purposes.
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 2192 Severity The virtual disk Ok / "Check Consistency" Normal has made corrections and completed. Cause and Action SNMP Trap Array Numbers Manager Event Number Cause: The virtual disk "Check Consistency" 1203 has identified errors and made corrections. For example, the "Check Consistency" may have encountered a bad disk block and remapped the disk block to restore data consistency.
Table 4-1. Storage Management Messages (continued) Event ID Description 2202 Severity Cause and Action SNMP Trap Array Numbers Manager Event Number A global hot spare has Warning / Cause: The controller is unable to 903 been removed. Non-critical communicate with a disk that is assigned as a global hot spare. The disk may have been removed. There may also be a bad or loose cable. 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 2206 Warning / Cause: The only array disk available to be 903 Non-critical assigned as a hot spare is using SATA technology. The array disks in the virtual disk are using SAS technology. Due to this difference in technology, the hot spare cannot rebuild data if one of the array disks in the virtual disk fails. The only hot spare available is a SATA disk. SATA disks cannot replace SAS disks.
Table 4-1. Storage Management Messages (continued) Event ID Description Severity Cause and Action SNMP Trap Array Numbers Manager Event Number 2235 The Check Consistency rate has changed. Ok / Normal Cause: This alert is provided for informational purposes. 751 None A controller rescan has been initiated. Ok / Normal 751 None 751 None 751 None 751 None 751 None 751 None 751 None 1201 None 1201 None 2237 Action: None Cause: 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 2246 The controller battery Warning / Cause: The controller battery charge is weak. 1153 is degraded. Non-critical Action: As the charge weakens, the charger should automatically recharge the battery. If the battery has reached its recharge limit, replace the battery pack. Monitor the battery to make sure that it recharges successfully.
Table 4-1. Storage Management Messages (continued) Event ID Description Severity Cause and Action SNMP Trap Array Numbers Manager Event Number 2260 Ok / Normal Cause: This alert is provided for informational purposes. 851 None 101 None 101 None 101 None An enclosure blink has ceased. Action: None 2261 A global rescan has initiated. Ok / Normal Cause: This alert is provided for informational purposes. Action: None 2262 Smart thermal Ok / shutdown is enabled.
Table 4-1. Storage Management Messages (continued) Event ID Description Severity Cause and Action SNMP Trap Array Numbers Manager Event Number 2266 Ok / Normal Cause: This alert is provided for informational purposes. 751 None 751 None Critical / %1, Storage Management has lost Failure / communication with Error this RAID controller and attached storage. An immediate reboot is strongly recommended to avoid further problems.
Table 4-1. Storage Management Messages (continued) Event ID Description 2270 Severity The array disk "Clear" Critical / operation failed. Failure / Error Cause and Action SNMP Trap Array Numbers Manager Event Number Cause: A "Clear" operation was being performed on an array disk, but it was interrupted and did not complete successfully. The controller may have lost communication with the disk. The disk may have been removed or the cables may be loose or defective.
Table 4-1. Storage Management Messages (continued) Event ID Description Severity 2277 Warning / Cause: The global hot spare is not large 903 Non-critical enough to protect all virtual disks that reside on the controller. The global hot spare is too small. Cause and Action SNMP Trap Array Numbers Manager Event Number None Action: Assign a larger disk as the global hot spare. 2278 The controller battery Critical / charge level is below a Failure / normal threshold.
Table 4-1. Storage Management Messages (continued) Event ID Description Severity Cause and Action 2282 Critical / Failure / Error Cause: The controller firmware attempted to 904 do 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.
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 2303 2304 2305 2306 Cause and Action SNMP Trap Array Numbers Manager Event Number The enclosure cannot Ok / support both SAS and Normal SATA array disks. Array disks may be disabled. Cause: This alert is provided for informational purposes. 851 None An attempt to hot Ok / plug an EMM has Normal been detected. This type of hot plug is not supported. Cause: This alert is provided for informational purposes.
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 2315 2316 2317 2318 88 The initialization sequence of SAS components failed during system startup. SAS management and monitoring is not possible. Action: Reboot the system.
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 1004 removed. The power cable may also have overheated and become warped and nonfunctional. None Action: Replace the power cable. 2325 2326 The power supply cable has been inserted. Ok / Normal A foreign configuration has been detected.
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 2331 SNMP Trap Array Numbers Manager Event Number None Action: Make sure the cables are attached securely.
Table 4-1. Storage Management Messages (continued) Event ID Description 2334 2335 2336 2337 92 Severity Cause and Action SNMP Trap Array Numbers Manager Event Number Controller event log: Ok / %1 Normal NOTE: %1 is a substitution variable that will appear in the alert description for specific details about the alert. Cause: This alert is provided for informational purposes.
Table 4-1. Storage Management Messages (continued) Event ID Description 2338 2339 2340 Severity Cause and Action SNMP Trap Array Numbers Manager Event Number The controller has Ok / recovered cached data Normal from the BBU. Cause: This alert is provided for informational purposes. 1151 None 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 2343 2344 2345 Severity The "Check Warning / Consistency" logging Non-critical of inconsistent parity data is disabled. Cause and Action SNMP Trap Array Numbers Manager Event Number Cause: The "Check Consistency" operation 1203 can no longer report errors in the parity data. None Action: See the hardware documentation for more information. The virtual disk initialization terminated.
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 96 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 Cause and Action SNMP Trap Array Numbers Manager Event Number SAS expander error: Critical / %1 Failure / Error NOTE: %1 is a substitution variable that will appear in the alert description for specific details about the alert. Cause: The text for this alert is generated by 754 the firmware and can vary depending on the situation. The battery charge cycle is complete.
Table 4-1. Storage Management Messages (continued) Event ID Description 2363 2364 2365 2366 2367 2368 98 Severity Cause and Action SNMP Trap Array Numbers Manager Event Number A virtual disk and all Ok / of its member array Normal disks have been removed while the system was shut down. This removal was discovered during system start-up. Cause: This alert is provided for informational purposes. 751 None All virtual disks are missing from the controller.
Index Numerics 1151, 20 1352, 29 0000, 15 1152, 21 1353, 29 0001, 15 1153, 21 1354, 30 1000, 15 1154, 21 1355, 30 1001, 15 1155, 22 1403, 31 1002, 15 1200, 22 1404, 31 1003, 15 1201, 23 1450, 31 1004, 15 1202, 23 1451, 31 1005, 16 1203, 23 1452, 31 1006, 16 1204, 24 1453, 32 1007, 16 1205, 24 1454, 32 1008, 16 1250, 25 1455, 32 1009, 16 1251, 25 1500, 32 1050, 17 1252, 25 1501, 32 1051, 17 1253, 25 1502, 32 1052, 17 1254, 26 1503, 33 1053, 18 1255, 26 1504,
100 Index 1602, 35 2085, 51 2121, 59 1603, 35 2086, 51 2122, 59 1604, 35 2088, 52 2123, 60 1605, 35 2089, 52 2124, 60 2048, 46 2090, 52 2126, 61 2049, 46 2091, 52 2127, 61 2050, 47 2092, 52 2128, 61 2051, 47 2094, 52 2129, 61 2052, 47 2095, 53 2130, 61 2053, 47 2098, 53 2131, 61 2054, 47 2099, 53 2132, 62 2055, 47 2100, 54 2135, 62 2056, 48 2101, 54 2136, 62 2057, 48 2102, 54 2137, 63 2058, 48 2103, 54 2138, 63 2059, 49 2104, 55 2139, 63 2061, 49 2105, 55
2154, 65 2189, 71 2249, 76 2155, 65 2191, 72 2251, 76 2156, 65 2192, 72 2252, 76 2157, 66 2193, 72 2254, 76 2158, 66 2194, 72 2255, 77 2159, 66 2199, 72 2259, 77 2160, 66 2201, 73 2260, 77 2161, 66 2202, 73 2261, 77 2162, 66 2203, 73 2262, 77 2163, 67 2204, 73 2263, 77 2164, 67 2205, 74 2264, 77 2165, 67 2206, 74 2265, 78 2166, 67 2207, 74 2266, 78 2167, 68 2211, 74 2267, 78 2168, 68 2232, 74 2268, 79 2169, 68 2233, 75 2269, 79 2170, 68 2234, 75 2270, 79 21
102 Index 2285, 82 2314, 88 2342, 93 2286, 82 2315, 88 2343, 94 2287, 82 2316, 88 2344, 94 2288, 82 2317, 88 2345, 94 2289, 83 2318, 88 2346, 94 2290, 83 2319, 89 2347, 94 2291, 83 2320, 89 2348, 94 2292, 83 2321, 89 2349, 95 2293, 84 2322, 89 2350, 95 2294, 84 2323, 89 2351, 95 2295, 84 2324, 90 2352, 95 2296, 84 2325, 90 2353, 95 2297, 84 2326, 90 2354, 95 2298, 84 2327, 90 2355, 96 2299, 85 2328, 90 2356, 96 2300, 85 2329, 91 2357, 97 2301, 85 2330, 91
A Array disk online, 66 A consistency check on a virtual disk has been paused (suspended), 57 Array disk rebuild cancelled, 50 A consistency check on a virtual disk has been resumed, 57 A mirrored virtual disk has been unmirrored, 58 Array disk rebuild completed, 52 BIOS Generated System Events, 44 BMC Watchdog Events, 42 Array disk rebuild failed, 51 C Array disk rebuild started, 49 Change write policy, 58 Array disk removed, 46 Chassis intrusion detected, 26, 41 A previously scheduled system
104 Index Controller battery recondition is completed, 55 Controller configuration has been reset, 66 Controller rebuild rate has changed, 64 cooling device messages, 19 current sensor, 8 Current sensor detected a failure value, 24 Current sensor detected a non-recoverable value, 24 Current sensor detected a warning value, 23 Current sensor has failed, 22, 40 current sensor messages, 22 Current sensor returned to a normal value, 23, 40 Current sensor value unknown, 23 E Enclosure alarm disabled, 63 Enclo
Log size returned to a normal level, 34 Log status is unknown, 33, 44 Log was cleared, 15 M Maximum temperature probe warning threshold value changed, 65 Memory device ECC Correctable error count crossed a warning threshold, 31, 42 Memory device ECC Correctable error count sensor crossed a failure threshold, 31 memory device messages, 30, 42 Memory device monitoring has been disabled, 31, 42 Memory ECC Events, 41 Memory Events, 42 memory prefailure sensor, 8 messages AC power cord, 32, 43 chassis intrusion
106 Index See readme.
Virtual disk degraded, 48 Virtual disk deleted, 47 Virtual disk failed, 48 Virtual disk format changed, 50 Virtual disk format completed, 51 Virtual disk format started, 49 Virtual disk initialization, 62 Virtual disk initialization cancelled, 50 Voltage sensor detected a non-recoverable value, 22 Voltage sensor detected a warning value, 21 Voltage Sensor Events, 38 Voltage sensor has failed, 20, 39 voltage sensor messages, 20, 39 Voltage sensor returned to a normal value, 21 Voltage sensor value unknown,
108 Index 108 Index
