Back to Contents Page

Introduction

Dell OpenManage™ Server Administrator Messages Reference Guide

  Understanding Event Messages

  Viewing Event Messages

Dell OpenManage Server Administrator produces event messages stored primarily in operating system or Server Administrator event logs and sometimes in SNMP traps. This document describes the event messages created by Server Administrator version 1.1 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 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.

For information on other messages produced by your system, see your system's Installation and Troubleshooting Guide or other system 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:

• Information — An event that describes the successful operation of a unit, such as a power supply turning on or a sensor reading returning to normal.
  
  
• Warning — An event that is not necessarily significant, but may indicate a possible future problem, such as crossing a warning threshold.
  
  
• Error — A significant event that indicates actual or imminent loss of data or loss of function, such as crossing a failure threshold or a hardware failure.
  
  

The 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 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.
  
  

Viewing Event Messages

In Server Administrator, an event log is used to record information about important events. You can view the event log using an 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, Windows Server 2003, and Windows 64-bit Advanced Server operating systems, messages are logged to the system event log and to a unicode text file, dcsys32.log or dcsys64.log (viewable using Notepad), that is located in the install_path\dell\openmanage\omsa\log directory.
  
  
• In the Novell® NetWare® versions 5.x and 6.x operating systems, messages are logged to a text file, DCSYS32.LOG, (viewable using a unicode text editor from a client attached to the system), that is located in the \system\dell\omanage\omsa\log directory.
  
  
• In the Red Hat Linux version 7.x operating system, messages are logged to a text file named /var/log/messages. You can view the messages file using a text editor such as vi or emacs.
  
  

The following subsections explain how to open the Windows 2000, Windows Server 2003, 64-bit Windows Advanced Server, NetWare, and Red Hat Linux event viewers.

Viewing Events in Windows 2000, Windows Server 2003, and 64-Bit Windows Advanced Server

1. Click the Start button, point to Settings, and click Control Panel.
   
   
2. Double-click Administrative Tools, and then double-click Event Viewer.
   
   
3. In the Event Viewer window, click the Tree tab and then click System Log.
   
   

The System Log window displays a list of recently logged events.

4. To view the details of an event, double-click one of the event items.
   
   

NOTE: You can also review the separate event log file by editing the dcsys32.log or the dcsys64.log file in the install_path\dell\openmanage\omsa\log directory.

Viewing Events in NetWare

1. Using a Windows system, map a drive to the \\nwserver\sys directory, where nwserver is the name of your NetWare system.
   
   
2. From the mapped drive, locate the DCSYS32.LOG file in the \system\dell\omanage\omsa\log directory.
   
   
3. View the DCSYS32.LOG file with Notepad or any other unicode-capable text editor.
   
   

Viewing Events in Red Hat Linux

1. Log in as root.
   
   
2. Use a text editor such as vi or emacs to view the file named /var/log/messages.
   
   

The following example shows the Linux 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: EventID: 1000
Server Administrator starting

Feb 6 14:20:51 server01 Server Administrator: EventID: 1001
Server Administrator startup complete

Feb 6 14:21:21 server01 Server Administrator: 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: 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-1 lists in alphabetical order each line item that may appear in the event description.

Table 1-1. Event Description Reference 

Back to Contents Page