09-07-2023 12:59 AM - last edited on 09-14-2023 10:21 PM by Translator
Hello,
I configured the CE-6 router with two different default static routes with different destinations and I could not be able to reach one of the destinations when I used multiple static routes. which routing policy do I need to use to reach both destinations?
CE-6#ping 10.10.10.10
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.10.10.10, timeout is 2 seconds:
U.U.U
Success rate is 0 percent (0/5)
CE-6#ping 70.70.70.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 70.70.70.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/2 ms
CE-6#sh run | se ip route
ip route 0.0.0.0 0.0.0.0 59.59.59.1
ip route 0.0.0.0 0.0.0.0 172.16.2.1 2
Solved! Go to Solution.
09-07-2023 10:11 AM - last edited on 09-14-2023 10:27 PM by Translator
Hi @R Manjunatha ,
Based on your configuration, the default route being installed in the routing table is the
ip route 0.0.0.0 0.0.0.0 59.59.59.1
, if this path does not have reachability to the
10.10.10.10 address
the
ping
is expected to fail.
If the path that has reachability to the
10.10.10.10 address
is via
172.16.2.1
next hop, you can add a more specific static route such as
ip route 10.0.0.0 255.0.0.0 172.16.2.1
to overcome this issue.
If the path through
59.59.59.1
next hop does not have reachability to the
10.10.10.10
this can keep failing even if you set the metric equal for both default routes.
HTH,
Julio
09-08-2023 10:17 AM - last edited on 09-14-2023 10:29 PM by Translator
ip route 70.70.70.2 255.255.255.255 59.59.59.1
ip route 10.10.10.10 255.255.255.255 172.16.2.1
09-07-2023 10:11 AM - last edited on 09-14-2023 10:27 PM by Translator
Hi @R Manjunatha ,
Based on your configuration, the default route being installed in the routing table is the
ip route 0.0.0.0 0.0.0.0 59.59.59.1
, if this path does not have reachability to the
10.10.10.10 address
the
ping
is expected to fail.
If the path that has reachability to the
10.10.10.10 address
is via
172.16.2.1
next hop, you can add a more specific static route such as
ip route 10.0.0.0 255.0.0.0 172.16.2.1
to overcome this issue.
If the path through
59.59.59.1
next hop does not have reachability to the
10.10.10.10
this can keep failing even if you set the metric equal for both default routes.
HTH,
Julio
09-07-2023 10:28 AM
For fun, try a traceroute to each destination.
09-08-2023 10:00 AM - last edited on 09-14-2023 10:28 PM by Translator
Yes. a specific static route will resolve this problem. if I need to use a route map. What will be the configuration in this scenario?
ip route 0.0.0.0 0.0.0.0 59.59.59.1 - destination ip 70.70.70.2
ip route 0.0.0.0 0.0.0.0 172.16.2.1 -destination ip 10.10.10.10
09-08-2023 10:17 AM - last edited on 09-14-2023 10:29 PM by Translator
ip route 70.70.70.2 255.255.255.255 59.59.59.1
ip route 10.10.10.10 255.255.255.255 172.16.2.1
09-11-2023 08:35 AM
Okay, there is another option I believe PBR. Anyway, thanks for the update.
09-11-2023 10:16 AM
@R Manjunatha wrote:
Okay, there is another option I believe PBR. Anyway, thanks for the update.
Perhaps. Cannot say for sure. PBR selects routes based on source information rather than destination information.
09-12-2023 06:24 AM
Thats true. Thank you for the update.
09-12-2023 02:15 AM - last edited on 09-14-2023 10:29 PM by Translator
Hello, Manjunatha
You should configure a
default gateway
with a higher administrative distance for the route you want to use as a backup. This way, if the primary route becomes unavailable, the router will automatically switch to the backup route.
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