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.2 or later and displayed in the Server Administrator Alert log.
Server Administrator creates events in response to sensor status changes and other monitored parameters. The Server Administrator event monitor uses these status change events to add descriptive messages to the operating system event log or the Server Administrator Alert log.
Each event message that Server Administrator adds to the Alert log consists of a unique identifier called the event ID for a specific event source category and a descriptive message. The event message includes the severity, cause of the event, and other relevant information, such as the event location and the monitored item's previous state.
Tables provided in this guide list all Server Administrator event IDs in numeric order. Each entry includes the event ID's corresponding description, severity level, and cause. Message text in angle brackets (for example, <State>) describes the event-specific information provided by the Server Administrator.
What's New in this Release
Modifications have been made to the Storage Management Service events. For more information, see "Alert Message Change History".
Messages Not Described in This Guide
This guide describes only event messages created by Server Administrator and displayed in the Server Administrator Alert log. For information on other messages produced by your system, consult one of the following sources:
Your system's Installation and Troubleshooting Guide
Other system documentation
Operating system documentation
Application program documentation
Understanding Event Messages
This section describes the various types of event messages generated by the Server Administrator. When an event occurs on your system, the Server Administrator sends information about one of the following event types to the systems management console:
Table 1-1. Understanding Event Messages
Icon
Alert Severity
Component Status
OK/Normal
An event that describes the successful operation of a unit. The alert is provided for informational purposes and does not indicate an error condition. For example, the alert may indicate the normal start or stop of an operation, such as power supply or a sensor reading returning to normal.
Warning/Non-critical
An event that is not necessarily significant, but may indicate a possible future problem. For example, a Warning/Non-critical alert may indicate that a component (such as a temperature probe in an enclosure) has crossed a warning threshold.
Critical/Failure/Error
A significant event that indicates actual or imminent loss of data or loss of function. For example, crossing a failure threshold or a hardware failure such as an array disk.
Server Administrator generates events based on status changes in the following sensors:
Temperature Sensor — Helps protect critical components by alerting the systems management console when temperatures become too high inside a chassis; also monitors a variety of locations in the chassis and in any attached systems.
Fan Sensor — Monitors fans in various locations in the chassis and in any attached systems.
Voltage Sensor — Monitors voltages across critical components in various chassis locations and in any attached systems.
Current Sensor — Monitors the current (or amperage) output from the power supply (or supplies) in the chassis and in any attached systems.
Chassis Intrusion Sensor — Monitors intrusion into the chassis and any attached systems.
Redundancy Unit Sensor — Monitors redundant units (critical units such as fans, AC power cords, or power supplies) within the chassis; also monitors the chassis and any attached systems. For example, redundancy allows a second or nth fan to keep the chassis components at a safe temperature when another fan has failed. Redundancy is normal when the intended number of critical components are operating. Redundancy is degraded when a component fails, but others are still operating. Redundancy is lost when there is one less critical redundancy device than required.
Power Supply Sensor — Monitors power supplies in the chassis and in any attached systems.
Memory Prefailure Sensor — Monitors memory modules by counting the number of Error Correction Code (ECC) memory corrections.
Fan Enclosure Sensor — Monitors protective fan enclosures by detecting their removal from and insertion into the system, and by measuring how long a fan enclosure is absent from the chassis. This sensor monitors the chassis and any attached systems.
AC Power Cord Sensor — Monitors the presence of AC power for an AC power cord.
Hardware Log Sensor — Monitors the size of a hardware log.
Processor Sensor— Monitors the processor status in the system.
Pluggable Device Sensor — Monitors the addition, removal, or configuration errors for some pluggable devices, such as memory cards.
Battery Sensor — Monitors the status of one or more batteries in the system.
Sample Event Message Text
The following example shows the format of the event messages logged by Server Administrator.
EventID: 1000
Source: Server Administrator
Category: Instrumentation Service
Type: Information
Date and Time: Mon Oct 21 10:38:00 2002
Computer: <computer name>
Description:
Server Administrator starting
Data: Bytes in Hex
Viewing Alerts and Event Messages
An event log is used to record information about important events.
Server Administrator generates alerts that are added to the operating system event log and to the Server Administrator Alert log. To view these alerts in Server Administrator:
Select the System object in the tree view.
Select the Logs tab.
Select the Alert subtab.
You can also view the event log using your operating system's event viewer. Each operating system's event viewer accesses the applicable operating system event log.
The location of the event log file depends on the operating system you are using.
In the Microsoft® Windows® 2000 Advanced Server and Windows Server™ 2003 operating systems, messages are logged to the system event log and optionally to a unicode text file, dcsys32.log (viewable using Notepad), that is located in the install_path\omsa\log directory. The default install_pathis C:\Program Files\Dell\SysMgt.
In the Red Hat® Enterprise Linux and SUSE® Linux Enterprise Server operating system, messages are logged to the system log file. The default name of the system log file is /var/log/messages. You can view the messages file using a text editor such as vi or emacs.
NOTE: Logging messages to a unicode text file is optional. By default, the feature is disabled. To enable this feature, modify the Event Manager section of the dcemdy32.inifile as follows:
In Windows, locate the file at <install_path>\dataeng\ini and set UnitextLog.enabled=True.
The default install_path is C:\Program Files\Dell\SysMgt. Restart the DSM SA Event Manager service.
In Red Hat Enterprise Linux and SUSE Linux Enterprise Server, locate the file at <install_path>/dataeng/ini and
set UnitextLog.enabled=True. The default install_path is /opt/dell/srvadmin. Issue the
"/etc/init.d/dataeng restart" command to restart the Server Administrator event manager service. This will also
restart the Server Administrator data manager and SNMP services.
The following subsections explain how to open the Windows 2000 Advanced Server, Windows Server 2003, and the Red Hat Enterprise Linux and SUSE Linux Enterprise Server event viewers.
Viewing Events in Windows 2000 Advanced Server and Windows Server 2003
Click the Start button, point to Settings, and click Control Panel.
Double-click Administrative Tools, and then double-click Event Viewer.
In the Event Viewer window, click the Tree tab and then click System Log.
The System Log window displays a list of recently logged events.
To view the details of an event, double-click one of the event items.
NOTE: You can also look up the dcsys32.log file, in the install_path\omsa\log directory, to view the separate event log file. The default install_path is C:\Program Files\Dell\SysMgt.
Viewing Events in Red Hat Enterprise Linux and SUSE Linux Enterprise Server
Log in as root.
Use a text editor such as vi or emacs to view the file named /var/log/messages.
The following example shows the Red Hat Enterprise Linux (and SUSE Linux Enterprise Server) message log, /var/log/messages. The text in boldface type indicates the message text.
NOTE: These messages are typically displayed as one long line. In the following example, the message is displayed using line breaks to help you see the message text more clearly.
...
Feb 6 14:20:51 server01 Server Administrator: Instrumentation Service EventID: 1000 Server Administrator starting
Feb 6 14:20:51 server01 Server Administrator: Instrumentation Service EventID: 1001 Server Administrator startup complete
Feb 6 14:21:21 server01 Server Administrator: Instrumentation Service EventID: 1254 Chassis intrusion detected Sensor location: Main chassis intrusion Chassis location: Main System Chassis Previous state was: OK (Normal) Chassis intrusion state: Open
Feb 6 14:21:51 server01 Server Administrator: Instrumentation Service EventID: 1252 Chassis intrusion returned to normal Sensor location: Main chassis intrusion Chassis location: Main System Chassis Previous state was: Critical (Failed) Chassis intrusion state: Closed
Viewing the Event Information
The event log for each operating system contains some or all of the following information:
Date — The date the event occurred.
Time — The local time the event occurred.
Type — A classification of the event severity: Information, Warning, or Error.
User — The name of the user on whose behalf the event occurred.
Computer — The name of the system where the event occurred.
Source — The software that logged the event.
Category — The classification of the event by the event source.
Event ID — The number identifying the particular event type.
Description — A description of the event. The format and contents of the event description vary, depending on the event type.
Understanding the Event Description
Table 1-2 lists in alphabetical order each line item that may appear in the event description.
