This section will explain you, How we can use RTR for link tracing and use track function to manage static routing in Maipu routers. RTR and track is basically used in this kind of senario,When you want to track different subnet IP. Which is located in your HQ or somewhere in network. This RTR destination IP can be anything, which is reachable all the time from router.
Here we are defining a condition, If destination IP is not reachable that time the failover should occur or Which link should be active. Since in Fastethernet last mile, most of the time the interface will not go down. Since it could be some backbone issue from ISP or ring issue. In that case if you are using static routing. The static route will be active in routing table because the interface is up.
See the topology and configuration to deal with this kind of situation.You can use the situation and apply to any such kind of requirement. Example like if you have 2 ISP and you want to track the connectivity, Whichever is reachable that route will be in routing table.
Maipu Router A
Configuration:
rtr 1 icmpecho
set 192.168.2.1 2 70 1 5 extend 10.2.2.1
log type local 100
exit
### Configure RTR for your requirement to check the connectivity to destination IP with source IP ###
rtr 2 icmpecho
set 192.168.1.1 2 70 1 5 extend 10.1.1.1
log type local 100
exit
rtr group 1
member 1
exit
### Bind RTR entity with group ###
rtr group 2
member 2
exit
rtr schedule 1 group 1 start now ageout 600 life forever
rtr schedule 2 group 2 start now ageout 600 life forever
### Checking the connectivity to destination IP mentioned in RTR by enabling RTR ####
### Bind RTR with track to check static ip route###
track 1
rtr 1
logic operator AND
exit
### Match all the parameters mentioned in track , IF it is OR then any one is ok###
track 2
rtr 2
logic operator AND
exit
ip route 0.0.0.0 0.0.0.0 10.2.2.2 track 1
### When 10.2.2.1 of Router A is reachable to 192.168.2.1,then only this route will work, Otherwise it will be removed from routing table ###
ip route 0.0.0.0 0.0.0.0 10.1.1.2 track 2
### When 10.1.1.1 of Router A is reachable to 192.168.1.1 ,then only this route will work, Otherwise it will be removed from routing table ###
But, if both routes are working fine, that time it will do per destination base load sharing.
Second solution is of Keepalive, Which is already explained in :
For any queries Plz put comments with your mail id. Will reply you soon...
