From: Ovidiu Neghina (o.neghina@gmail.com)
Date: Fri Jul 27 2007 - 07:16:07 ART
Hi dear all,
I did a lab now and I had a question related to subject but doing a debug I
realised that the solution is correct. I thought to share that with you.
In the lab I configured the rmon event + alarm and snmp-server +
snmp-server enable traps:
rmon event 1 trap IETRAP description "five minute cpu avrage above 75%"
owner config
rmon event 2 trap IETRAP description "five minute cpu avrage bellow 40"
owner config
rmon alarm 1 lsystem.58.0 60 absolute rising-threshold 75 1
falling-threshold 40 2 owner confi
snmp-server enable traps cpu threshold - this was not neccesary
snmp-server host 132.8.33.100 IETRAP
I thought that if we want to generata trap is it neccessary to enable traps
for the snmp-server .
I thought like that because of config guide (look at the italics) for
snmp-server host command :
The *snmp-server host** *command is used in conjunction with the *snmp-server
enable** *command. Use the *snmp-server enable* command to specify which
SNMP notifications are sent globally.
For a host to receive most notifications, at least one *snmp-server
enable*command and the
*snmp-server host** *command for that host must be enabled.
The solution from the the vendor book does not include snmp-server enable
traps which is fine.
Doing a debug snmp packets without *snmp-server enable** traps *showed what
exacly is happening :
Rack8R5#
*Jul 27 10:13:29: %RMON-5-FALLINGTRAP: Falling trap is generated because the
value of lsystem.58.0 has fallen below the falling-threshold value 40
SNMP: Queuing packet to 132.8.33.100
SNMP: V1 Trap, ent rmon, addr 150.8.5.5, gentrap 6, spectrap 2
alarmEntry.1.1 = 1
alarmEntry.3.1 = lsystem.58.0
alarmEntry.4.1 = 1
alarmEntry.5.1 = 1
alarmEntry.8.1 = 40
Rack8R5#
All the best
Ovidiu
This archive was generated by hypermail 2.1.4 : Sat Aug 18 2007 - 08:17:42 ART