From: Radoslav Vasilev (deckland@gmail.com)
Date: Fri Oct 06 2006 - 13:37:11 ART
Thanks Kulcsar!
On 10/6/06, Kulcsar Andras Benjamin <Kulcsar.Andras@kfki-lnx.hu> wrote:
> Hi,
>
> It is not necessary to use "snmp-server enable traps" at all if you only want rmon events:
>
> Rack1R3#
>
> Rack1R3#sh snmp
> %SNMP agent not enabled
>
> Rack1R3#sh run | incl snmp
> Rack1R3#conf t
> Enter configuration commands, one per line. End with CNTL/Z.
>
> Rack1R3(config)#snmp-server host 145.1.37.4 COMM
> Rack1R3(config)#do debug snmp headers
> SNMP packet header debugging is on
> Rack1R3(config)#rmon event 1 trap COMM owner config
> Rack1R3(config)#rmon alarm 1 lsystem.58.0 60 absolute rising-threshold 0 1 falling-threshold 10 1 owner config
>
> *Aug 23 07:53:26.423: %RMON-5-RISINGTRAP: Rising trap is generated because the value of lsystem.58.0 exceeded the rising-threshold value 0
> *Aug 23 07:53:26.435: %RMON-5-FALLINGTRAP: Falling trap is generated because the value of lsystem.58.0 has fallen below the falling-threshold value 10
>
> Outgoing SNMP packet
> *Aug 23 07:53:26.439: v1 packet
> *Aug 23 07:53:26.439: community string: COMM
> *Aug 23 07:53:26.443:
> Outgoing SNMP packet
> *Aug 23 07:53:26.443: v1 packet
> *Aug 23 07:53:26.443: community string: COMM
> Rack1R3(config)#do deb snmp packets
> SNMP packet debugging is on
> Rack1R3(config)#rmon alarm 1 lsystem.58.0 60 absolute rising-threshold 0 1 falling-threshold 10 1 owner config
> Rack1R3(config)#
> *Aug 23 07:53:39.855: %RMON-5-RISINGTRAP: Rising trap is generated because the value of lsystem.58.0 exceeded the rising-threshold value 0
> *Aug 23 07:53:39.867: %RMON-5-FALLINGTRAP: Falling trap is generated because the value of lsystem.58.0 has fallen below the falling-threshold value 10
> *Aug 23 07:53:39.871: SNMP: Queuing packet to 145.1.37.4
> *Aug 23 07:53:39.871:
> Outgoing SNMP packet
> *Aug 23 07:53:39.871: v1 packet
> *Aug 23 07:53:39.871: community string: COMM
> *Aug 23 07:53:39.871: SNMP: V1 Trap, ent rmon, addr 150.1.3.3, gentrap 6, spectrap 1
> alarmEntry.1.1 = 1
> alarmEntry.3.1 = lsystem.58.0
> alarmEntry.4.1 = 1
> alarmEntry.5.1 = 1
> alarmEntry.7.1 = 0
> *Aug 23 07:53:39.951: SNMP: Queuing packet to 145.1.37.4
> *Aug 23 07:53:39.955:
> Outgoing SNMP packet
> *Aug 23 07:53:39.955: v1 packet
> *Aug 23 07:53:39.955: community string: COMM
> *Aug 23 07:53:39.955: SNMP: V1 Trap, ent rmon, addr 150.1.3.3, gentrap 6, spectrap 2
> alarmEntry.1.1 = 1
> Rack1R3(config)#
> alarmEntry.3.1 = lsystem.58.0
> alarmEntry.4.1 = 1
> alarmEntry.5.1 = 1
> alarmEntry.8.1 = 10
>
>
> Best regards,
> Andras
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of Radoslav Vasilev
> Sent: Friday, October 06, 2006 4:44 PM
> To: Cisco certification
> Subject: RMON && snmp-server enable traps
>
> Hi Group,
>
> Let's say we have an rmon alarm and events configured already, where the action for the event should be trap. How do we enable the trap to be sent to an snmp host, if we don't want to enable all traps at the same time?
>
> For example, if we use:
> snmp-server enable traps
>
> this would enable all traps supported (well, almost all).
>
> How do I enable only the rmon-related traps to be sent? I suspect it all depends on the monitored value for the rmon alarm, but a confirmation from someone else would be better ;)
>
> Thanks!
> Rado
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Wed Nov 01 2006 - 07:29:04 ART