05-18-2016 11:14 AM - edited 03-08-2019 05:49 AM
I am trying to configure a floating route but an aggregate route already exist in the routing table. As such the floating route is more specific and gets inserted into the routing table immediately. Does anyone know of a way around this?
Here is my routing table before adding the floating static route:
D 172.16.0.0/12 [90/1290752] via 10.128.193.125, 22:56:19, GigabitEthernet1/0/14
Here it is after I have inserted the static route:
D 172.16.0.0/12 [90/1290752] via 10.128.193.125, 22:56:19, GigabitEthernet1/0/14
S 172.16.0.0 [200/0] via 10.128.193.49
Solved! Go to Solution.
05-25-2016 03:04 AM
If you want to kick in the static route when the eigrp neighbor is not reachable - you could configure the following:
I don't know if that is what you're looking for?
ip sla 10
icmp-echo 10.128.193.125
track 10 ip sla 10 reachability
ip sla schedule 10 life forever start-time now
track 1 list
object 10 not
ip route 172.16.0.0 255.255.0.0 10.128.193.49 track 1
05-24-2016 08:12 AM
When do you want the floating static to kick in? If the summary disappears? If that's case why not configuring the same subnet mask as the summary route?
There are some options - you might maybe explain what you want to achieve -
05-24-2016 08:09 PM
We do not need or want the remaining address space going that way.
05-25-2016 03:04 AM
If you want to kick in the static route when the eigrp neighbor is not reachable - you could configure the following:
I don't know if that is what you're looking for?
ip sla 10
icmp-echo 10.128.193.125
track 10 ip sla 10 reachability
ip sla schedule 10 life forever start-time now
track 1 list
object 10 not
ip route 172.16.0.0 255.255.0.0 10.128.193.49 track 1
06-15-2016 12:39 PM
This is interesting, I get how the use of ip sla ICMP and tracking are used to actively check the state of reachability for 10.128.193.125, however where I get a bit confused is that I don't see how IP SLA in and of itself overcome the issue of the static route being more specific?
06-15-2016 12:44 PM
It can't.
06-16-2016 02:13 AM
Did you test it?
object 10 not
> when the next hop is not reachable, --> true
Unless the next hop/eigrp neighbor will be reachable via the summary route.
05-24-2016 03:14 PM
Hello
I agree with Davy - Why not apply the floating static with the same subnet range then it will not be added into the rib unless the current advertised route is removed
res
Paul
06-15-2016 09:38 AM
The problem with this is that the track statement you have presented would test as true and as such it would insert the static route. We would need to track the presence of the 172.16.0.0/12 route in the routing table and insert the static 172.16.0.0/16 route only when the other route disappears from the routing table. At this point it just doesn't seem possible. The best and easiest solution to all of this is to remove the summary address which is what I have done.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: