Difference between EMMI & "regular" SNMP/MIB Traps

Hello begleysm,

Can you confirm for us which application you are using?

OpenManage Essentials  or  OpenManage Enterprise

EEMI is information about the events and error messages generated by the system firmware and agents that monitor system components and logged within the iDRAC logs.

You can then set Email alerts and SNMP trap forwarding in the IDRAC console.

Error and Event Message Reference Guide (EEMI)

https://dell.to/3pbFvWv

Begleysm,

The difference between the EEMI and "non"EEMI traps is the source, as the iDrac uses EEMI by default, where as OMSA doesn't use it by default. So basically EEMI would be idrac based, and non EEMI would be OMSA based, unless EEMI is enabled.

Let me know if this helps.

Thanks for the reply.

I'll be using OpenManage Enterprise (though I don't have the HW in-hand yet, I'm currently working on planning out our HW monitoring solution of which a PowerEdge R7625 is one of many components).

You say "EEMI is information about the events and error messages generated by the system firmware and agents that monitor system components and logged within the iDRAC logs."  But what is "non-EMMI" since there seems to be EEMI & non-EEMI versions of most of the Traps listed in dcstorag.mib?  Why would I choose to monitor the EEMI or the non-EEMI version of the Traps?

Thanks that does help.  I like iDRAC because it is an "OS-independent" source (compared to the  "software agent" OMSA source).

However many traps do not have an EEMI variant.  Are these traps only available via OMSA and not iDRAC?  Thus if I wanted to use those Traps I'd need them to come from OMSA?

Do you have a specific example, as we would need a specific example to be sure that there is no hardware type that doesn't have an SNMP trap for warning or critical errors.

My application is supposed to monitor a range of HW and mostly distill the status down to a Green/Red panel.  Some basic information should be given for an error but it doesn't need to be incredibly indepth.  My plan was to monitor relevant Traps that indicate that the HW is working or failing and then, in the event of a failure, display the Warning/Failure Trap that was received.

As you know there are A LOT of SNMP Traps available from a PowerEdge.  My first effort was to go through the available MIBs and create a list of all the traps from MIBs that seemed relevant to me.  I created this list: https://pastebin.com/5wAyiP4c

Then I tried to distill it down to Traps that are specifically relevant to HW and came up with this list (note that some rows have 2x Traps: one "normal" and one EEMI): https://pastebin.com/9cRPmkGb

Hello begleysm,

I believe OpenManage Enterprise does what you are wanting.

Make sure that the device being monitored in OME has it's SNMP alerts configured to be sent to OME.

When you discover the device make sure they are "Managed with Alerts". Check the "Enable trap reception..." check box

OpenManage Enterprise 3.10 User's Guide

Step 8 page 76

https://dell.to/3M7t3jB

What is the application you are using?

Thank you.  I should have full control over configuring the monitored PowerEdge server.

My application is custom.  There will be a C++ backend & C# GUI frontend.  A limited number of Traps will be monitored and essentially OR'd together to create a green/red status light.  If a problematic Trap is received the light will turn red and an error message displayed.  Many other (non-dell non-SNMP HW devices are also being monitored, via various Telnet/SSH APIs and DDS, as well).