PowerEdge Server Error Messages in System Event Log and how they can be viewed

PowerEdge Server Error Messages in System Event Log and how they can be viewed


This article will provide you with information on how to get the state of your system out of the Server Event Log (SEL) / Hardware-Log.


There are different ways to check this log, which contains chronologically sorted error messages. Here we show you how to read the information, and how to gather the log, if possible.


Overview of options to check the Server Event Log:

  1. During Systemstart (Servers of Generation 11 and earlier)

  2. During Systemstart (Servers of Generation 12 and later)

  3. When OpenManage Server Administrator (OMSA) is installed on the system

  4. When the DRAC (Dell Remote Access Controller) is configured



1. During System Start (11th Generation Servers and earlier)

The System event logs are stored in the BMC or iDRAC in your server. So they can be accessed at POST through the BMC / iDRAC configuration utility.

  1. Restart the server


  2. Press CTRL+E during system start to access the configuration utility (P.O.S.T.) (Figure 1 (English only))
    Screenshot of POST
    Figure 1 - Example of System start screen


  3. In the main menu, go down to the option "System Event Log Menu" and press Enter.


  4. You will be given 2 options for the System Event Logs. Choose" View SystemEvent Log" and press Enter (Figure 2 (English only))

    Figure 2 - iDRAC / BMC Settings in the configuration utility


  5. Using the arrow keys, you can now scroll through the single entries in the Server Event Log shown on the screen (Figure 3 (English only))

    Figure 3 - System Event Log Entry in iDRAC



2. During System start (12th Generation Servers and later)

The System event logs are stored in the BMC or iDRAC in your server. So they can be accessed at POST through the system settings.

  1. Restart the server


  2. Press F2 to enter the System Settings


  3. In the main menu, choose IDRAC Settings


  4. On the next page, choose "System Event Log" (Figure 4 (English only))

    Figure 4 - System Setup iDRAC Settings


  5. Choose "Display System Event Log" (Figure 5 (English only )) to be able to review the logs.

    Figure 5 - Event Log Display Option


  6. Using the arrow keys, you can now scroll through the single entries in the Server Event Log (Figure 6 (English only))

    Figure 6 - System Event Log Entry in Setup



3. When Dell OpenManage Server Administrator (OMSA) is installed on the system

Dell Open Manage Server Administrator (OMSA) is able to communicate with the BMC and iDRAC to retrieve information and display it in a user-friendly interface.


To access the System Event Logs in OMSA:

  1. Open OMSA


  2. Click on "System" on the left side


  3. Click on the "Logs" Tab in the middle of the page. Now the Server Event Log is shown directly (Figure 7 (English only ))

    Figure 7 - System Event Log in OMSA


  4. You can export the logs via the "save to" button in the top right corner.

  5. Click on the "Alert" under the "Logs" tab and export alert log via the "save to" button as needed.



4. When the iDRAC (Dell Remote Access Controller) is configured

When the iDRAC has been configured with an IP address, you can access the iDRAC web interface from any machine on the network.

Since the System Event Logs are stored there, you can use this interface to review the logs.

  1. Enter the iDRAC web interface using the iDRAC IP address.


  2. Click on "System" on the left side


  3. Click on on the "Logs" Tab. Now the Server Event Log is shown directly (Figure 8 (English only ))

    Figure 8 - System Event Log in the web interface of iDRAC


  4. You can export the logs via the "Save To" button at the bottom of the list.



Need more help?
Find additional PowerEdge and PowerVault articles
Watch Part Replacement Videos for Enterprise products

Visit and ask for support in our Communities

Create an online support Request





Article ID: SLN292270

Last Date Modified: 09/14/2019 05:57 AM


Rate this article

Accurate
Useful
Easy to understand
Was this article helpful?
Yes No
Send us feedback
Comments cannot contain these special characters: <>()\
Sorry, our feedback system is currently down. Please try again later.

Thank you for your feedback.