Options
Question on IP SLA
ClapDemCheeks
Member Posts: 77 ■■□□□□□□□□
in Off-Topic
I am planning on configuring IP SLA with a floating route. I setup a lab on GNS to simulate what i am trying to do at our corporate network with the following configuration:
R1 = NYC router with ip sla and tracking enabled. The primary default route is to R3 and the secondary is to R2.
R2 = Secondary ISP.
R3 = Primary ISP.
I setup icmp echo from R1 to R3 as my SLA condition. The problem that i am having is that when i delete the link from R1 to R3 everything works fine except that the SLA comes back up because R3 is reachable via R2 > R1. Need some ideas on how to solve this issue.
R1 = NYC router with ip sla and tracking enabled. The primary default route is to R3 and the secondary is to R2.
R2 = Secondary ISP.
R3 = Primary ISP.
I setup icmp echo from R1 to R3 as my SLA condition. The problem that i am having is that when i delete the link from R1 to R3 everything works fine except that the SLA comes back up because R3 is reachable via R2 > R1. Need some ideas on how to solve this issue.
Comments
-
Options
Dieg0M
Member Posts: 861
Use the P2P endpoint for the SLA condition. (192.168.1.2) in your example.Follow my CCDE journey at www.routingnull0.com -
OptionsClapDemCheeks
Member Posts: 77 ■■□□□□□□□□
I think i know what is the problem. Even though the backup route comes up the routing table still has the directly connected link on the table. A direct conenction has an admin distance of 0 which takes precedence of a static route with an admin distance of 1.