Generating RMON SNMP Traps

Answered Question
Jul 20th, 2010

I am trying to generate SNMP traps from RMON events but they won't work.  I have the following test configuration:

snmp-server host 10.1.1.1 version 2c TEST

snmp-server enable traps

rmon event 1 log trap PUBLIC description "TEST TEST TEST" owner config

rmon alarm 1 ifOutUcastPkts.6 5 delta rising-threshold 100 1 falling-threshold 50 1 owner config

When I enable 'debug snmp packet' I see don't see any packets being generated.  I do see %RMON-5 syslog messages but I don't see any "TEST TEST TEST" messages in the console, although I do see them here:

show rmon events
Event 1 is active, owned by config
Description is TEST TEST TEST
Event firing causes log and trap to community PUBLIC,
last event fired at  0y0w0d,01:03:09,
Current uptime       0y0w0d,01:05:58
Current log entries:
  index  uptime              description
  1      0y0w0d,01:02:59     TEST TEST TEST
  2      0y0w0d,01:03:04     TEST TEST TEST
  3      0y0w0d,01:03:09     TEST TEST TEST

Am I missing something?  Thanks

I have this problem too.
0 votes
Correct Answer by Joe Clarke about 6 years 4 months ago

Your RMON event community is PUBLIC, but your trap host is using community TEST.  Set these two so that they agree.  You will not see

the description on the console.  You will only see that a rising or falling condition has occurred.

If you want more flexibility on these syslogs or traps, consider using EEM instead of RMON.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Correct Answer
Joe Clarke Tue, 07/20/2010 - 14:54

Your RMON event community is PUBLIC, but your trap host is using community TEST.  Set these two so that they agree.  You will not see

the description on the console.  You will only see that a rising or falling condition has occurred.

If you want more flexibility on these syslogs or traps, consider using EEM instead of RMON.

Actions

This Discussion

Related Content