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

Trap OID Matching

So I have had a handful of trap issues with SolarWinds where either the MIB database was corrupted or somehow an updated DB had removed or rewrote a section and I lost some definitions. What I want to know is if this is possible. Currently my trap rules match on something like this.

SNMP TRAP OID is equal to NETAPP-MIB:volumeCloneCreate

Can I instead do

SNMP TRAP OID is equal to 1.3.6.1.4.1.789.0.646 which is the raw format for the exact same trap?

Does anyone know if this will or will not work?

I'm getting increasing pressure from the teams as we keep getting issues with traps no longer matching (first after the problems in 10.1.2) and now a separate issue that support tells me a new MIB DB will fix an issue for traps that used to be defined and now are missing.

Find more posts tagged with

Accepted answers

All comments

david.templeton

Look under the Conditions tab of the Trap Rule. Add the condition where "SNMPv2MIB:snmpTrapOID is equal to 1.3.6.1.4.1.789.0.646". That might be what you're looking for.

mdriskell

That's exactly what I'm looking for...What I need to know is if that works if it is already defined and not just the raw numbers.

david.templeton

It should work. Take the "NETAPP-MIB:volumeCloneCreate" text out of the definition and give it a try.