OID Description in traps

I am looking to completely replace HP System Insight Manager with Orion NPM. I am able to account for 90% of SIM's function by using a combination of NPM UnDP and's the new SAM 5.x hardware health monitors. However, I am still missing 10%.

That 10% is in traps that are generates by the local HP system, captured by SIM and then forwarded to the interested parties. I attempted to create Trap Viewer alerts and rules in NPM, but there is, at least in my eyes, a glaring omission in the data that can be included in an alert notification. The OID Description. Below are examples from both SIM and NPM.

Event Name: (SNMP) Remote Insight/ Integrated LightsOut Interface Error (9006)

URL: SERVER_NAME:280/.../MxContextLaunch.jsp

Event originator: SERVER_NAME

Event Severity: Major

Event received: 27-Jun-2012, 11:47:52

Event description: Remote Insight/ Integrated Lights-Out Interface Error. The host OS has detected an error in the Remote Insight/ Integrated Lights-Out interface. The firmware is not responding.

6/27/2012 12:47:52 PM SERVER_NAME SERVER_NAME public COMPAQ-ID-REC-MIB:compaq.0.9006 sysName=SERVER_NAME

cpqHoTrapFlags=0

snmpTrapOID=COMPAQ-ID-REC-MIB:compaq.0.9006

sysUpTime=8 hours 44 minutes 35.18 seconds

experimental.1057.1.0=SERVER_IP

snmpTrapEnterprise=COMPAQ-ID-REC-MIB:compaq

The RED text is the critical information i need to make these traps useful. Just presenting the OID that generated the trap without the description to which it refers means that the NPM Trap feature is not a viable replacement for SIM.

Can someone please tell me if I am missing something that will allow me to include the RED text inside of an email notification when a trap comes in?

Find more posts tagged with

trap_viewer_alerts

Accepted answers

All comments

Detroiter

Any movement on this topic? This is the last piece that is preventing us from converting entirely form HP SIM to Orion. Any help would be greatly appreciated.

mdriskell

This is not done out of the box for any trap with solarwinds. The only way (and not really realistic way) is to create a custom rule for each OID and include the text manually in your email. This is an area that other products excel in and solarwinds could take some tips from other applications.

Detroiter

That seems very odd to me considering the fact that the UnDP app automatically populates the "Description" field with the correct data. I assume that app is getting it from the MIBS.cfg database. If that is the case, couldn't the Trap Viewer also look there for a description? And if it finds one, add it to the email or if not just say "Not Found"?

mdriskell

As far as I know it can't be done I agree it would be very valuable if it could perhaps it's stored as a variable that could be called. Maybe you could have someone review this thread?