93med93

updated

26 days ago

9

93med93

1 Rookie

•

4 Posts

•

13 Points

0

82

October 15th, 2026 15:27

forward System Event Logs from IDRAC to OME

Hello,

I need your help because I’m trying to send the iDRAC System Event logs to OME but I can’t get it to work. 

 

I have onboarded my devices into OME, I can manage them for updates, and lifecycle logs for my device do appear in OME. However, I can’t find clear information on how to send the SEL. 

 

What needs to be enabled on the iDRAC so it will send these logs to my OME? The goal is then to forward these logs via syslog from OME.

 

If anyone has an idea, thanks

Med

  • DELL-Bridjet V

    Moderator

    •

    118 Posts

    •

    338 Points

    1

    0

    Posted October 21st, 2026 03:29

    Hi @93med93,

    This output reveals an important detail about how OpenManage Enterprise (OME) is currently communicating with your iDRAC:

    What the Output Means

    "Members@odata.count": 0 confirms that there is currently no active Redfish Event Subscription configured on this iDRAC.

    Why Are You Still Seeing Lifecycle Logs in OME?

    The reason you see Lifecycle Logs in OME despite having zero subscriptions is due to the difference between Pull (Polling) and Push (Alerting):

    1. Pull / Polling (What is happening now):
      • OME uses Redfish to periodically run Inventory and Health status jobs.
      • During this scheduled polling, OME executes standard Redfish GET calls to read the iDRAC’s Lifecycle Log (/redfish/v1/Managers/iDRAC.Embedded.1/LogServices/Lclog/Entries).
      • This is why the logs appear in the device details within the OME console.
    2. Push / Real-Time Alerting (What is currently missing):
      • An Event Subscription tells the iDRAC: "The second a critical event happens, make an outbound HTTPS POST to OME's listener immediately."
      • Why this matters for your goal: OME’s Alert Policies (Syslog forwarding) only trigger when an alert event is pushed into OME. OME cannot forward logs to Syslog that it simply reads during periodic inventory queries.

    How to Get OME to Register the Redfish Subscription

    To have OME automatically create the subscription so it can receive real-time push events without SNMP:

    1. In OME, navigate to Devices > Discovery.
    2. Locate the Discovery Job used for your iDRACs, select it, and click Edit.
    3. Under the discovery settings, look for the option labeled Enable trap / event reception on target devices (or Trap/Event Configuration) and ensure it is checked.
    4. Save and Run the Discovery Job.

    When the job runs with that box checked, OME will authenticate to the iDRAC via Redfish and issue an HTTP POST to register itself in the /redfish/v1/EventService/Subscriptions list.

    Once that completes, re-running your PowerShell or cURL command should return Members@odata.count: 1 with your OME appliance's webhook listed as the destination. 

    Regards,

    DELL-Bridjet V

    Social Media and Communities Professional

    Dell Technologies | Enterprise Support Services

    #IWork4Dell

    Was your query answered? Please click Thumbs Up on the post that helped to Mark it as Accepted Answer!

  • DELL-Bridjet V

    Moderator

    •

    118 Posts

    •

    338 Points

    0

    0

    Posted October 16th, 2026 08:55

    Hi @93med93,

     

    The System Event Log (SEL) in iDRAC is collected by OME through two mechanisms:

    1. SNMP Traps - For real-time alerting when events occur
    2. Hardware Log Collection - For periodic collection of the full SEL

    Configuration Steps

    Step 1: Configure iDRAC to Send SNMP Traps to OME

    This enables real-time alerting when events occur in the SEL:

    Via iDRAC Web Interface:

    1. Log in to iDRAC
    2. Navigate to Configuration > System Settings > Alert Configuration > Alerts
    3. Ensure Alerts are enabled
    4. Configure Event Filters - select the categories and severities you want (e.g., Critical, Warning)
    5. In the Alerts and Remote System Log Configuration section, enable SNMP trap
    6. Go to SNMP Traps Configuration:
      • Set the Destination Address to your OME server IP
      • Configure the Community String (e.g., "public" or your custom string)
      • Ensure the State checkbox is selected
      • Click Apply

    Via RACADM CLI:

    racadm set iDRAC.IPMiLAN.AlertEnable Enabled
    racadm set iDRAC.SNMPAlert.1.Destination <OME_IP_ADDRESS>
    racadm set iDRAC.SNMPAlert.1.State 1
    racadm eventfilters set -c idrac.alert.system.*.critical -a none -n snmp

    Step 2: Configure OME to Receive SNMP Traps

    1. In OME, go to Settings > SNMP Settings
    2. Configure SNMP community string to match what you set in iDRAC
    3. Ensure the SNMP service is running and listening on port 162
    4. Test the configuration by using the Test Event option in iDRAC to generate a test trap

    Step 3: View Hardware Logs in OME

    The SEL data is collected as Hardware Logs in OME:

    1. In OME, navigate to Manage > Devices
    2. Expand the device type and select Hardware Logs
    3. You can view the System Event Log entries here
    4. Ensure devices are discovered and inventory jobs are running periodically

    Step 4: Configure OME to Forward Logs to Remote Syslog

    To forward the logs from OME to your syslog server:

    Via OME Web Interface:

    1. Go to Settings > Alert Settings (or Application Settings > Alerts)
    2. Configure Syslog Settings:
      • Add your remote syslog server IP/FQDN
      • Set the port (default: 514 for UDP, 6514 for TLS)
      • Enable syslog forwarding
    3. Create an Alert Policy to forward logs:
      • Go to Alerts > Alert Policies > Create
      • Name the policy (e.g., "SEL Forwarding")
      • In the Category section, select the alert categories you want to forward
      • In the Target section, configure the syslog destination
      • Enable the policy

    Important Notes:

    • The SEL is also recorded in the Lifecycle Log, and OME can collect Lifecycle Logs
    • For iDRAC9 firmware 6.00.02.00 and above, you can use encrypted syslog with TLS (port 6514)
    • OME receives SNMP traps from iDRAC and can forward these to your syslog server based on alert policies

    Step 5: Verify the Configuration

    1. Generate a test event in iDRAC (use the Test Event option)
    2. Check OME Alerts > Alert Logs to confirm the trap was received
    3. Check your syslog server to confirm the forwarded log appears
    4. Verify that Hardware Logs are being collected in OME under Manage > Devices > Hardware Logs

    Summary

    The key insight is that iDRAC doesn't "send" the SEL directly to OME in real-time. Instead:

    • SNMP traps send individual event notifications to OME as they occur
    • OME collects the full SEL/Hardware Logs through periodic inventory/polling
    • OME forwards these to your syslog server via alert policies and syslog configuration

    This two-tier approach ensures you get both real-time alerts (via SNMP traps) and complete log history (via Hardware Log collection), which can then be forwarded to your syslog server.

     

    Regards,

    DELL-Bridjet V

    Social Media and Communities Professional

    Dell Technologies | Enterprise Support Services

    #IWork4Dell

    Was your query answered? Please click Thumbs Up on the post that helped to Mark it as Accepted Answer!

  • 93med93

    1 Rookie

    •

    4 Posts

    •

    13 Points

    3

    0

    Posted October 16th, 2026 11:14

    @DELL-Bridjet V​ 

    Thank you for your quick response. I followed the steps, and in Step 1 I was able to configure the SNMP section with my OME address, the community string, and activation.

    For Step 2, I cannot find any SNMP Listener section. The only two SNMP‑related areas I can find are the following:

    • Application Settings → Alerts → SNMP Alert Forwarding Configuration, which only forwards alerts from OME, so it is not applicable in this case.

    • Application Settings → Incoming Alerts, which only displays the community string and port number.

    Using the search bar, there is no Settings → SNMP Settings menu.

    For your information, I am using iDRAC9 and OME version 4.8.0 (Build 115).

     

    Just to be sure: is the feature I am trying to configure only available through SNMP? Is it impossible to achieve the same behavior using Redfish or WS‑MAN on iDRAC?

     

    Regards,

    Med

  • DELL-Bridjet V

    Moderator

    •

    118 Posts

    •

    338 Points

    0

    0

    Posted October 16th, 2026 12:01

    Hi @93med93,

    1. Clarification on Step 2 in OME 4.x (SNMP Listener)

    • I stand corrected that what you found under Application Settings → Incoming Alerts is the correct place:
      • That section defines the SNMP Community String and Port (162) that OME expects for inbound traps.
      • As long as the Community String defined there matches the Community String they set in the iDRAC in Step 1, OME will accept the traps.
      • There is nothing else to start, enable, or start up in OME to receive traps. The only requirement is ensuring firewall/network routing allows UDP port 162 inbound to OME.

     2. Can this be done via Redfish instead of SNMP?

    Yes, iDRAC9 and OME versions natively support Redfish Event Subscriptions, which is Dell’s modern replacement for SNMP traps and WS-MAN:

    • How Redfish Eventing works between iDRAC and OME:
      • When OME discovers an iDRAC9 using the Redfish protocol (configured during discovery), OME can automatically create an HTTPS-based Redfish Event Subscription on the iDRAC.
      • When a hardware or system event occurs, iDRAC sends a Redfish event over secure HTTPS (TCP 443) directly to OME’s webhook endpoint.
      • This eliminates the need for unencrypted SNMPv1/v2c traps or UDP 162 network configuration.
    • How to enable Redfish eventing in OME 4.x:
      1. In OME, go to Devices > Discovery.
      2. Edit or create a discovery job targeting the iDRAC:
        • Discovery Type: Server.
        • Ensure the protocol selected includes Redfish (with valid iDRAC administrative credentials).
      3. Under the Trap / Event Configuration option inside the discovery job, ensure "Enable trap/event reception on target devices" is checked.
      4. Run the discovery job.
      5. OME will use Redfish to automatically register an event subscription on the iDRAC, pointing back to OME over HTTPS.
    • What about WS-MAN?
      • WS-MAN was used primarily for 12G/13G (iDRAC7/8). On 14G+ (iDRAC9), WS-MAN has been deprecated in favor of Redfish. It is not recommended to use WS-MAN for event subscriptions on iDRAC9.

     3. Verification & Next Step

    To verify whether OME is already receiving the events (via SNMP or Redfish):

    1. On the iDRAC Web UI: Go to Configuration > System Settings > Alerts > SNMP Traps (or use RACADM: racadm testtrap -i 1).
    2. Send a Test Trap / Event.
    3. In OME: Go to Alerts > Alert Log.
    4. Check if the test event appears in the log table. Once it shows up here, the user's Alert Policy will automatically forward it to their Syslog destination. 

    Regards,

    DELL-Bridjet V

    Social Media and Communities Professional

    Dell Technologies | Enterprise Support Services

    #IWork4Dell

    Was your query answered? Please click Thumbs Up on the post that helped to Mark it as Accepted Answer!

  • 93med93

    1 Rookie

    •

    4 Posts

    •

    13 Points

    3

    0

    Posted October 19th, 2026 08:56

    @DELL-Bridjet V​ 

    Hello, Thank you for this information.

     

    With a few adjustments, I managed to get logs from the iDRAC into OME using only the Redfish protocol, since I do not want to use SNMP.

    The downside is that it only pulls what is found in the iDRAC LifeCycle Events. In that section, I also see my older critical alerts (the same ones as in the System Event Logs).

     

    I could leave it as is, but there is far too much INFO-level noise in the LifeCycle section. I need to look into how to reduce these logs without impacting the iDRACs.

     

    I think the topic is closed for now, and I sincerely thank you for your help. Before closing the thread, if you happen to know how to check—either from the GUI or via RACADM—whether a given iDRAC actually has a subscription configured, I would be very interested (if such a verification exists). 

     

    Regards,

    Med

    (edited)

  • DELL-Bridjet V

    Moderator

    •

    118 Posts

    •

    338 Points

    1

    1

    Posted October 19th, 2026 12:18

    Hi @93med93,

    Glad to hear you were able to establish event communication successfully using Redfish!

    Regarding your questions on verifying the subscription and managing the log noise, here are the suggestions you can try.

    1. How to Check Active Redfish Subscriptions on an iDRAC

    Because Redfish is an API-first standard, the iDRAC Web GUI does not have a dedicated visual table for Redfish Event Subscriptions. They are managed directly by the Redfish Event Service engine.

    However, you can easily view and verify existing subscriptions using a REST query (via PowerShell or cURL):

    Option A: Using PowerShell (Quickest from Windows)

    Run the following command against the iDRAC IP:

    powershell

    1. $cred = Get-Credential
    2. Invoke-RestMethod -Uri "https://<iDRAC_IP>/redfish/v1/EventService/Subscriptions" -Method Get -Credential $cred -SkipCertificateCheck

        To see the full details of a specific subscription (e.g., Subscription 1):

    powershell

    Invoke-RestMethod -Uri "https://<iDRAC_IP>/redfish/v1/EventService/Subscriptions/1" -Method Get -Credential $cred -SkipCertificateCheck | Select-Object -ExpandProperty Destination

     

    This will return the destination URL and confirm that it points directly to your OME appliance's HTTPS endpoint.

     

    Option B: Using cURL (Linux / macOS / Windows Terminal)

    bash

    1. curl -k -u <username>:<password> -X GET https://<iDRAC_IP>/redfish/v1/EventService/Subscriptions

    You will get a JSON payload listing the active subscription IDs (Members). Querying the specific member (e.g., /redfish/v1/EventService/Subscriptions/<ID>) will display:

    • Destination: The OME appliance URL listening for the events.
    • Context: Identifier set by OME.
    • EventTypes: Types of events subscribed to (e.g., Alert, ResourceAdded).

    (Note: Native racadm does not have a dedicated property tree for viewing dynamic Redfish subscriptions, making the direct Redfish API query above the authoritative method).

     

    2. Quick Tip on Handling "INFO-Level Noise"

    You do not need to modify or suppress logs on the iDRAC itself to keep your Syslog clean. Instead, filter them at the OME forwarding tier:

    1. In OME, go to Alerts > Alert Policies.
    2. Edit your Syslog forwarding policy.
    3. In the Severity tab, uncheck "Information" and leave only "Warning" and "Critical" selected.
    4. Save and enable the policy.

    This allows the iDRAC to maintain full audit fidelity in its Lifecycle Log for troubleshooting, while ensuring your central Syslog server receives only actionable Warning and Critical alerts.

    Regards,

    DELL-Bridjet V

    Social Media and Communities Professional

    Dell Technologies | Enterprise Support Services

    #IWork4Dell

    Was your query answered? Please click Thumbs Up on the post that helped to Mark it as Accepted Answer!

  • 93med93

    1 Rookie

    •

    4 Posts

    •

    13 Points

    2

    0

    Posted October 20th, 2026 15:15

    Hi @DELL-Bridjet V​ 

     

    Both commands return the same output. Without abusing your kindness, if you have any comments or insights, I would be happy to benefit from your expertise.

     

    The output of the commands are: 

     

    >curl -k -u xxxxxxxx:xxxxxxxxxx -X GET https://192.xx.xx.xx/redfish/v1/EventService/Subscriptions
    {"@odata.context":"/redfish/v1/$metadata#EventDestinationCollection.EventDestinationCollection","@odata.id":"/redfish/v1/EventService/Subscriptions","@odata.type":"#EventDestinationCollection.EventDestinationCollection","Description":"List of Event subscriptions","Members":[],"Members@odata.count":0,"Name":"Event Subscriptions Collection"}

     

    AND

     

    >Invoke-RestMethod -Uri "https://192.xx.xx.xx/redfish/v1/EventService/Subscriptions" -Method Get --Credential $cred -SkipCertificateCheck

     

    @odata.context      : /redfish/v1/$metadata#EventDestinationCollection.EventDestinationCollection
    @odata.id           : /redfish/v1/EventService/Subscriptions
    @odata.type         : #EventDestinationCollection.EventDestinationCollection
    Description         : List of Event subscriptions
    Members             : {}
    Members@odata.count : 0
    Name                : Event Subscriptions Collection

     

    Thank you again for your help.

    Regards,

    Med