Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

What to do with SNMP Traps?

I must be missing something obvious:

SNMP Traps configured on Cisco switches, they seem to work and i get the Trap under "Traps" on the Orion Web Interface.

However, i dont understand the trap:

CISCO-CONFIG-MAN-MIB:ciscoConfigManEvent ccmHistoryEventConfigDestination.37 = 3
ccmHistoryEventConfigSource.37 = 2
ccmHistoryEventCommandSource.37 = commandLine(1)
snmpTrapOID = CISCO-CONFIG-MAN-MIB:ciscoConfigManEvent
sysUpTime = 3 days 0 hours 11 minutes 44,99 seconds

For Example, this should be link shutdown - but i have no idea how to read this from the trap above.

So - what i want to achve is a human readable information that the link was shutdown.

Please help. Thanks.

Find more posts tagged with

Accepted answers

All comments

lostinvt

My question exactly! Let me know how you make out, and if you get a response....

jblancke

You would need to have the trap collector run an external program and have the config manager send it to you. This will imidiatly send a request to download the config and compare to the last known or the baseline. Look at your documnetation and it is explained under enabling realtime config managment.

The trap only shows the event that happened not the details of the configuration changes. NCM does the details part.

Cheers

James

lostinvt

James,

This doesnt really answer the question...this has nothing to do with NCM, I think you're looking at the wrong product!

The question is how to translate/filter out the SNMP trap into a readable alert.

For example, if I use HP Systems Insight Manager as my SNMP collector, it will report if a drive fails as "drive failed" not ten lines of trap text.

michelle2

Something you can look at is the Universal Device Pollers and OID - so instead of the device sending you and alert NPM polls the status and then have alert trigger if the polled is not the expected result.

That will work for Cisco etc.

Im not sure about the HP and harddrive failure, in those cases it must be better with a snmptrap from the device..Maybe you should create a support request for what to do with the incomming snmp traps??

Vieregg

I want to bring this up again. Have there been any improvements in Orion NPM meanwhile?

Regards
Dirk

bshopp

See here for some Syslog and Trap enhancements we are working on now

thamizh85

At least Trap viewer should allow us to define some format for each kind of traps so that we can generate meaningful alerts. See this opensource SNMPTT tool for example