03-29-2016 10:45 AM - edited 03-05-2019 03:40 AM
I have a permanent route in my routing table but it's being ignored for actual traffic.
ip route 0.0.0.0 0.0.0.0 1.1.1.2 track 1
ip route 0.0.0.0 0.0.0.0 192.168.23.254 10
ip route 8.8.8.8 255.255.255.255 1.1.1.2 permanent
sh ip int br
Interface IP-Address OK? Method Status Protocol
GigabitEthernet0/0 192.168.23.1 YES NVRAM up up
GigabitEthernet0/0.123 192.168.123.1 YES NVRAM up up
GigabitEthernet0/1 1.1.1.1 YES NVRAM up down
sh ip route 8.8.8.8
Routing entry for 8.8.8.8/32
Known via "static", distance 1, metric 0
Routing Descriptor Blocks:
* 1.1.1.2, permanent
Route metric is 0, traffic share count is 1
traceroute 8.8.8.8
Type escape sequence to abort.
Tracing the route to 8.8.8.8
VRF info: (vrf in name/id, vrf out name/id)
1 192.168.23.254 0 msec 0 msec 0 msec
as you can see in the traceroute it is actually using the default route even though the routing table shows it should use the permanent route. The ip sla will still function because in the event the interface goes down the track-able route won't be used even though reach-ability will be up and if the interface is up but reach-ability is down the track-able route gets used as expected. But I would much prefer that the permanent route work as advertised.
(C3845-ADVENTERPRISEK9_IVS-M), Version 15.1(4)M10
03-29-2016 06:36 PM
Perhaps it has decided to use a recursive route. What does "show ip route 1.1.1.2" show?
Perhaps try:
ip route 8.8.8.8 255.255.255.255 Gigabit0/1 1.1.1.2 permanent
03-31-2016 10:45 AM
I added both of the following to no avail, still behaves the same.
ip route 1.1.1.2 255.255.255.255 GigabitEthernet0/1 1.1.1.2 permanent
ip route 8.8.8.8 255.255.255.255 GigabitEthernet0/1 1.1.1.2 permanent
sh ip route 1.1.1.2
Routing entry for 2.2.2.2/32
Known via "static", distance 1, metric 0
Routing Descriptor Blocks:
* 1.1.1.2, via GigabitEthernet0/1, permanent
Route metric is 0, traffic share count is 1
sh ip route 8.8.8.8
Routing entry for 8.8.8.8/32
Known via "static", distance 1, metric 0
Routing Descriptor Blocks:
* 1.1.1.2, via GigabitEthernet0/1, permanent
Route metric is 0, traffic share count is 1
traceroute 8.8.8.8
Type escape sequence to abort.
Tracing the route to 8.8.8.8
VRF info: (vrf in name/id, vrf out name/id)
1 192.168.23.254 0 msec 0 msec 0 msec
Looks like a bug to me.
I got around the issue by removing the permanent keyword and adding this route.
ip route 8.8.8.8 255.255.255.255 null0 254
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