07-13-2013 04:33 AM
Hello Community,
I have been evaluating a Tcl Script posted here sometime ago, designed to help monitor track interfaces and routes, see attached.
I believe I have applied the configurations correctly, however when I test the script by shutting down interfaces nothing happens.
I'm sure its something very simple that I'm missing.
I wonder if someone could take a look at the configs and let me know what I'm doing wrong. I have also attached a diagram.
Cheers
Carlton
07-13-2013 09:51 AM
Keep reading the help text the author wrote in is Tcl policy. You didn't configure any of the NOTIFY-foo applets he talks about there. Those are the things that actually do the notifications.
07-14-2013 02:41 AM
Joseph,
I did read again and I got it to work :-)
Cheers
On a slightly different topic, is it possible to 'track' a static ip address?
For example, I have the following tracking configured:
!
track 1 ip route 0.0.0.0 0.0.0.0 reachability
!
track 2 interface FastEthernet0/0 ip routing
!
track 3 interface FastEthernet0/1 ip routing
!
track 4 ip route 180.80.8.4 255.255.255.255 reachability
!
track 5 ip route 170.70.7.4 255.255.255.255 reachability
!
!
R3#show track brie
Track Object Parameter Value
1 ip route 0.0.0.0/0 reachability Up (static)
2 interface FastEthernet0/0 ip routing Up
3 interface FastEthernet0/1 ip routing Up
4 ip route 180.80.8.4/32 reachability Down (no route)
5 ip route 170.70.7.4/32 reachability Down (no route)
However, you will see that track 4 and 5 are down. This is because, although I can ping 180.80.8.4 and 170.70.7.4 the actual ip addresses don't appear in the routing table:
Gateway of last resort is 0.0.0.0 to network 0.0.0.0
170.70.0.0/24 is subnetted, 1 subnets
C 170.70.7.0 is directly connected, FastEthernet0/0
10.0.0.0/24 is subnetted, 1 subnets
C 10.1.1.0 is directly connected, FastEthernet1/0
180.80.0.0/24 is subnetted, 1 subnets
C 180.80.8.0 is directly connected, FastEthernet0/1
150.50.0.0/24 is subnetted, 1 subnets
C 150.50.5.0 is directly connected, Ethernet2/0
S* 0.0.0.0/0 is directly connected, FastEthernet1/0
R3#
Therefore, is there way of creating a track for /32 ip addresses?
I hope that makes sense.
Cheers
07-14-2013 08:46 AM
You can use IP SLA to ping the hosts and track the state of the IP SLA operation.
ip sla 1
icmp-echo 170.70.7.4
ip sla schedule 1 start now life forever
!
track 1 ip sla 1 reachability
07-14-2013 12:05 PM
Hi Joseph,
Thanks for responding.
That does seem like an ideal solution.
Can you let me know what version allows me to
track 1 ip sla 1 reachability?
At the moment, I only have the following option
R3(config)#track 4 ip ?
route IP route
Cheers
07-14-2013 12:24 PM
Hi Joseph,
I managed to configure ip sla with old method - using rtr.
Everything is working fine:
R3#show track brie
Track Object Parameter Value
1 ip route 0.0.0.0/0 reachability Up (static)
2 interface FastEthernet0/0 ip routing Up
3 interface FastEthernet0/1 ip routing Up
4 rtr 1 reachability Down
R3#
The problem I'm having is that the script doesn't recognise track 4. As you can see track 4 shows 'Down', but the script still thinks everything is up and working.
Any thoughts?
Cheers mate.
07-14-2013 01:07 PM
From what I can tell this script doesn't discriminate from the track types. It should see track 4 and recognize it is down. Provided you have conditions and other applets setup accordingly the script should work. But since this isn't my work, I cannot say for certain.
07-14-2013 01:26 PM
07-14-2013 02:28 PM
07-14-2013 02:35 PM
To me it looks like the script would work with any number of tracks provided you use the right $X variable to represent the track value (e.g., $4).
07-14-2013 03:09 PM
Brilliant. I will try it tomorrow
Cheers mate
Sent from Cisco Technical Support iPad App
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide