cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1001
Views
0
Helpful
8
Replies

Floating Route Not Floating

gchevalley
Beginner
Beginner

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

1 Accepted Solution

Accepted Solutions

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

View solution in original post

8 Replies 8

davy.timmermans
Enthusiast
Enthusiast

 

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 -

We do not need or want the remaining address space going that way.

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

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?

It can't.

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.

paul driver
VIP Expert VIP Expert
VIP Expert

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


Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul

gchevalley
Beginner
Beginner

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.

Getting Started

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:

Recognize Your Peers