[c-nsp] Wonky tracking?

Tuc at T-B-O-H.NET ml at t-b-o-h.net
Sat Aug 4 20:49:31 EDT 2007


Hi,

	I have both of them up to the maxes, and still running into
problems :


C3640-1#sho track   
Track 100
  Response Time Reporter 100 reachability
  Reachability is Down
    21 changes, last change 00:41:32
  Delay up 180 secs, down 30 secs
  Latest operation return code: Timeout
  Tracked by:
    STATIC-IP-ROUTING 0
Track 101
  Response Time Reporter 101 reachability
  Reachability is Down, delayed Up (162 secs remaining)
    21 changes, last change 00:41:32
  Delay up 180 secs, down 30 secs
  Latest operation return code: Timeout
Track 200
  Response Time Reporter 200 reachability
  Reachability is Up
    6 changes, last change 06:11:42
  Delay up 20 secs, down 10 secs
  Latest operation return code: OK
  Latest RTT (millisecs) 991
  Tracked by:
    STATIC-IP-ROUTING 0
Track 201 
  Response Time Reporter 201 reachability
  Reachability is Up
    4 changes, last change 06:11:34
  Delay up 20 secs, down 10 secs
  Latest operation return code: OK
  Latest RTT (millisecs) 1720

C3640-1#sho track br      
Track   Object                         Parameter        Value
100     rtr       100                  reachability     Down, delayed Up (170 secs remaining)
101     rtr       101                  reachability     Down
200     rtr       200                  reachability     Up
201     rtr       201                  reachability     Up

C3640-1#sh ip sla mon stat
Round trip time (RTT)   Index 100
        Latest RTT: 83 ms
Latest operation start time: 20:46:25.833 EDT Sat Aug 4 2007
Latest operation return code: OK
Number of successes: 40
Number of failures: 223
Operation time to live: Forever

Round trip time (RTT)   Index 101
        Latest RTT: 246 ms
Latest operation start time: 20:46:35.833 EDT Sat Aug 4 2007
Latest operation return code: OK
Number of successes: 40
Number of failures: 224
Operation time to live: Forever

Round trip time (RTT)   Index 200
        Latest RTT: 803 ms
Latest operation start time: 20:46:25.837 EDT Sat Aug 4 2007
Latest operation return code: OK
Number of successes: 263
Number of failures: 0
Operation time to live: Forever
          
Round trip time (RTT)   Index 201
        Latest RTT: 871 ms
Latest operation start time: 20:46:35.837 EDT Sat Aug 4 2007
Latest operation return code: OK
Number of successes: 264
Number of failures: 0
Operation time to live: Forever

C3640-1#sho ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area 
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2
       i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
       ia - IS-IS inter area, * - candidate default, U - per-user static route
       o - ODR, P - periodic downloaded static route

Gateway of last resort is 192.168.75.1 to network 0.0.0.0

C    192.168.75.0/24 is directly connected, Ethernet0/0
C    192.168.0.0/24 is directly connected, Ethernet1/0
C    192.168.3.0/24 is directly connected, BVI1
S*   0.0.0.0/0 [250/0] via 192.168.75.1


	My default routes are :

ip route 0.0.0.0 0.0.0.0 192.168.75.1 10 name SEABREEZE track 100
ip route 0.0.0.0 0.0.0.0 192.168.0.1 11 name HUGHES track 200
ip route 0.0.0.0 0.0.0.0 192.168.75.1 250 name SEABREEZE_FB
ip route 0.0.0.0 0.0.0.0 192.168.0.1 251 name HUGHES_FB


	So I'm totally confused why it went to the 250 weighted route, and
not the 11.

			Thanks, Tuc
> 
> Tuc,
> 
> What does 'sh ip sla mon stat' show for that probe?
> 
> What does debug track show?
> debug ip sla monitor etcc...
> 
> Also, it's confusing. But it's bet to set the track
> up/down to at least a 2x multiple of the sla probe frequency.
> 
> Meaning if you get a notification the probe is down
> and you delay it going down for 10 more seconds but that
> is right on the time the next probe should go out it's
> potentially possible I think that you could get in a race
> condition and it always show down.
> 
> Or it could be a bug. I've seen reports where the probe would
> hang until it was reconfigured. But I'd like to see if the
> probe is really reporting up/or down and the track object
> is just stuck down.
> 
> Rodney
> 
> 
> On Tue, Jul 31, 2007 at 11:20:21AM -0400, Tuc at T-B-O-H.NET wrote:
> > Hi,
> > 
> > 	3640 running c3640-jk9s-mz.124-13a.bin .
> > 
> > 	I have a set of ip sla/tracks, as such :
> > 
> > ip sla monitor 200
> >  type echo protocol ipIcmpEcho 204.107.90.128 source-ipaddr 192.168.0.3
> >  timeout 4000
> >  frequency 10
> > ip sla monitor schedule 200 life forever start-time now
> > ip sla monitor 201
> >  type echo protocol ipIcmpEcho 64.200.58.69 source-ipaddr 192.168.0.3
> >  timeout 4000
> >  frequency 10
> > ip sla monitor schedule 201 life forever start-time now
> > 
> > track 200 rtr 200 reachability
> >  delay down 10 up 20
> > !         
> > track 201 rtr 201 reachability
> >  delay down 10 up 20
> > 
> > 
> > ip local policy route-map LocalPolicy
> > 
> > ip access-list extended Ping-HUGHES-VJOFN
> >  permit icmp host 192.168.0.3 host 204.107.90.128
> > ip access-list extended Ping-HUGHES-WCGRTR
> >  permit icmp host 192.168.0.3 host 64.200.58.69
> > ip access-list extended Ping-SEABREEZE-VJOFN
> >  permit icmp host 192.168.75.49 host 204.107.90.128
> > ip access-list extended Ping-SEABREEZE-WCGRTR
> >  permit icmp host 192.168.75.49 host 64.200.58.69
> > 
> > route-map LocalPolicy permit 10
> >  match ip address Ping-SEABREEZE-VJOFN
> >  set ip next-hop 192.168.75.1
> > !         
> > route-map LocalPolicy permit 11
> >  match ip address Ping-SEABREEZE-WCGRTR
> >  set ip next-hop 192.168.75.1
> > !         
> > route-map LocalPolicy permit 20
> >  match ip address Ping-HUGHES-VJOFN
> >  set ip next-hop 192.168.0.1
> > !         
> > route-map LocalPolicy permit 21
> >  match ip address Ping-HUGHES-WCGRTR
> >  set ip next-hop 192.168.0.1
> > 
> > 
> > The problem I have is :
> > 
> > C3640-1# sho track
> > Track 200
> >   Response Time Reporter 200 reachability
> >   Reachability is Up
> >     28 changes, last change 10:47:07
> >   Delay up 20 secs, down 10 secs
> >   Latest operation return code: OK
> >   Latest RTT (millisecs) 691
> >   Tracked by:
> >     STATIC-IP-ROUTING 0
> > Track 201 
> >   Response Time Reporter 201 reachability
> >   Reachability is Down
> >     2 changes, last change 12:53:33
> >   Delay up 20 secs, down 10 secs
> >   Latest operation return code: Timeout
> > 
> > Which I don't get, since :
> > 
> > C3640-1#ping 64.200.58.69 source 192.168.0.3       
> > 
> > Type escape sequence to abort.
> > Sending 5, 100-byte ICMP Echos to 64.200.58.69, timeout is 2 seconds:
> > Packet sent with a source address of 192.168.0.3 
> > !!!!!
> > Success rate is 100 percent (5/5), round-trip min/avg/max = 768/806/856 ms
> > 
> > 
> > 	Any way to figure out whats happening (or not happening)?
> > 
> > 			Thanks, Tuc
> > _______________________________________________
> > cisco-nsp mailing list  cisco-nsp at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-nsp
> > archive at http://puck.nether.net/pipermail/cisco-nsp/
> 



More information about the cisco-nsp mailing list