troubleshooting Question

Problem with a cisco sla monitor

Avatar of marinedepot
marinedepotFlag for United States of America asked on
RoutersNetwork Operations
5 Comments1 Solution3033 ViewsLast Modified:
I'm having a hard time figuring out why one of my sla monitors is not working correctly.  I know that if i reboot the router or delete and re-create the sla, it will start working again.
I currently have two WAN uplinks and two SLAs (one for each WAN).  The sla was workign fine up until earlier today.

!
ip sla monitor 1
 type echo protocol ipIcmpEcho 4.2.2.1
 threshold 3000
 frequency 5
ip sla monitor schedule 1 life forever start-time now
ip sla monitor 2
 type echo protocol ipIcmpEcho 4.2.2.2
 threshold 3000
 frequency 5
ip sla monitor schedule 2 life forever start-time now
!

I then have a permanent route to 4.2.2.1 out of 1 interface, and another route to 4.2.2.2 out of the other interface.
!
ip route 4.2.2.1 255.255.255.255 216.237.15.xxx permanent
ip route 4.2.2.2 255.255.255.255 216.237.30.xxx permanent
!
The trackings are pretty standard, though note that one is reachability and the other is state. (the one tracking state is the one that is shows to be down)
!
track 1 rtr 1 reachability
 delay down 15 up 15
!
track 2 rtr 2
 delay down 15 up 15
!

I can ping both 4.2.2.2 and 4.2.2.1:

Sending 5, 100-byte ICMP Echos to 4.2.2.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 4/6/8 ms
HQ_Router#ping 4.2.2.1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 4.2.2.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 40/48/80 ms

This is what track is telling me:

HQ_Router#sh track
Track 1
  Response Time Reporter 1 reachability
  Reachability is Up
    4 changes, last change 2d17h
  Delay up 15 secs, down 15 secs
  Latest operation return code: OK
  Latest RTT (millisecs) 32
  Tracked by:
    STATIC-IP-ROUTING 0
Track 2
  Response Time Reporter 2 state
  State is Down
    4 changes, last change 05:57:57
  Delay up 15 secs, down 15 secs
  Latest operation return code: Timeout
  Tracked by:
    STATIC-IP-ROUTING 0

Here is the sla monitors and notice that index 2 is in Timeout state:

HQ_Router#sh ip sla monitor statistics
Round trip time (RTT)   Index 1
        Latest RTT: 56 ms
Latest operation start time: *20:48:45.428 Pacific Thu Oct 22 2009
Latest operation return code: OK
Number of successes: 433
Number of failures: 0
Operation time to live: Forever

Round trip time (RTT)   Index 2
        Latest RTT: NoConnection/Busy/Timeout
Latest operation start time: *20:48:38.508 Pacific Thu Oct 22 2009
Latest operation return code: Timeout
Number of successes: 0
Number of failures: 205
Operation time to live: Forever
ASKER CERTIFIED SOLUTION
Faruk Onder Yerli
CTO

Our community of experts have been thoroughly vetted for their expertise and industry experience.

Join our community to see this answer!
Unlock 1 Answer and 5 Comments.
Start Free Trial
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 5 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros