SNMP Trap OID – Test and Example Dummy OID

snmp

I want to send a test trap from a router, just to make sure SNMP is set up correctly, the server is receiving traps, etc. I could use some innocuous or irrelevant trap, but is there a specific trap OID to send in this case? One that's meant for tests, examples, or other dummy uses?

I'm using request snmp spoof-trap on Junos, but I'm curious about any standard or proprietary traps.

Best Answer

As jonathanjo said in his answer and the comments afterwards, there are no special test traps for testing connectivity. Often, one of the RFC-defined traps (like linkup, linkdown or warmstart) is used.

However, there is also MIB 1.3.6.1.4.1.8072.9999.9999, named netSnmpPlaypen. It was introduced by the net-SNMP project as a playground environment to introduce traps which only have meaning within your own network.

You could consider picking an OID within that MIB and using that to test if SNMP traps are working. However, two things are required then:

your network device needs to be able to send SNMP traps with a customized OID
your SNMP trap handler has to be configured to properly handle these customized traps

Since it's often hard to arrange these two things, one of the RFC-defined traps (like the ones jonathanjo mentioned) is commonly used.

Related Solutions

Cisco – Intermapper SNMP trap probe

If all you need is login notification and if you don't care about SNMP vs Syslog, you can use IOS built-in syslog for authentication failures and success. It also can block IP addresses with failed logins.

login block-for 300 attempts 5 within 60
login on-failure log
login on-success log

This is the message for success

Jul 18 06:55:26.408: %SEC_LOGIN-5-LOGIN_SUCCESS: Login Success [user: cisco]
 [Source: 10.10.1.5] [localport: 23] at 06:55:26 UTC Thu Jul 18 2013

This is the message for a telnet failure

Jul 18 06:56:16.963: %SEC_LOGIN-4-LOGIN_FAILED: Login failed [user: ] 
 [Source: 10.10.1.5] [localport: 23] [Reason: Login Authentication Failed] at 06:56:16 UTC 
 Thu Jul 18 2013

Bgp – SNMP OID for advertised routes by peer

Cisco

You should be able to use the OIDs under 1.3.6.1.2.1.15.5.1 (bgpPathAttrEntry) for Cisco devices. There are 2 OIDs in particular that should accomplish what you're looking for.

1.3.6.1.2.1.15.5.1.1 (bgpPathAttrPeer) - The IP address of the peer where the path information was learned.

1.3.6.1.2.1.15.5.1.2 (bgpPathAttrDestNetwork) - The address of the destination network.

Force10

This information should be obtainable under 1.3.6.1.4.1.6027.20.1.3.4.1 (f10BgpM2PathAttrEntry).

1.3.6.1.4.1.6027.20.1.3.4.1.12 (f10BgpM2AsPathString) - This is a string depicting the autonomous system path to this network which was received from the peer which advertised it. The format of the string is implementation-dependent, and should be designed for operator readability.