From: Henk de Tombe (henk.de.Tombe@qi.nl)
Date: Tue Apr 24 2007 - 15:53:03 ART
Hi,
I've labbed up your config and It doesn't work. The reason is probably
that the output of 'show ip sla stat 1' shows a timout for the Latest
operation return code.
I've changed the react from connection-loss to timeout.
After changing that I've forced a timeout by shutting down an interface
making the destination unreachable:
Apr 24 20:36:15.543: SNMP: V2 Trap, reqid 7, errstat 0, erridx 0
sysUpTime.0 = 167920
snmpTrapOID.0 = rttMonTimeoutNotification
rttMonCtrlAdminTag.1 =
rttMonHistoryCollectionAddress.1 = 0A 00 00 01
rttMonCtrlOperTimeoutOccurred.1 = 1
Apr 24 20:36:15.639: SNMP: Queuing packet to 2.2.2.2
Apr 24 20:36:15.639: SNMP: V2 Trap, reqid 8, errstat 0, erridx 0
sysUpTime.0 = 167929
snmpTrapOID.0 = rttMonNotifications.5
rttMonCtrlAdminTag.1 =
rttMonHistoryCollectionAddress.1 = 0A 00 00 01
rttMonCtrl.19.1.2.1 = 7
rttMonCtrl.19.1.10.1 = 1
rttMonCtrl.19.1.9.1 = 1
rttMonCtrl.19.1.5.1 = 0
rttMonCtrl.19.1.6.1 = 0
rttMonEchoAdminEntry.33.1 = 00 00 00 00
Apr 24 20:36:15.795: SNMP: Packet sent via UDP to 2.2.2.2
R1#sh ip sla stat 1
Round Trip Time (RTT) for Index 1
Latest RTT: NoConnection/Busy/Timeout
Latest operation start time: 20:51:30.587 UTC Tue Apr 24 2007
Latest operation return code: Timeout
Number of successes: 153
Number of failures: 158
Operation time to live: Forever
I'm still looking for a the sla statistics to display connectionloss as
the latest operation return code.
Regards,
Henk
Met vriendelijke groet,
Q&I
Henk de Tombe
Network Engineer
Q&I NEDERLAND BV
Delftech Park 35 - 37
P.O. Box 402 - 2600 AK DELFT
Phone [+31] 15-8880444 - Fax [+31] 15-8880445
info@qi.nl - www.qi.nl
-----Oorspronkelijk bericht-----
Van: nobody@groupstudy.com [mailto:nobody@groupstudy.com] Namens Hafizur
Rahman
Verzonden: maandag 23 april 2007 23:00
Aan: ccielab@groupstudy.com
Onderwerp: IP SLA
Hi Group,
I wonder if you could help me.
I am trying to achieve followings
R1 ------ R2 ----------- R3 -- PC(10.0.0.1)
R1 will ping PC(10.0.0.1) using ip sla for reachability if ping fails
then
R1 will send SNMP trap.
R1 ping PC(10.0.0.1) every 5 seconds which is working. But when it can
not
ping, not generating any SNMP trap or log
IS this at all possible. Followings are my config on R1 ( but not
working)
--------------
ip sla monitor responder
ip sla monitor logging traps
ip sla monitor 1
type echo protocol ipIcmpEcho 10.0.0.1 source-ipaddr 60.0.0.1
owner admin
frequency 5
ip sla monitor reaction-configuration 1 connection-loss-enable
threshold-falling 5000 action-type trapAndTrigger
ip sla monitor reaction-trigger 1 3
ip sla monitor schedule 1 life forever start-time now
!
snmp-server enable traps rtr
snmp-server enable traps syslog
snmp-server host 1.1.1.1 cisco rtr
_____________--
I have done "debug Snmp packets" but can not see any match.
Your help will be highly appreciated.
Thanks
hafi
This archive was generated by hypermail 2.1.4 : Tue May 01 2007 - 08:28:37 ART