10-15-2014 08:09 AM - edited 03-07-2019 09:07 PM
Hello, guys
i've created a lab with 5 routers all running IOS 15.2
┌ ------- R3-----┐
R1 R4 ---- R5
└--------R2-----┘
R1 has a two routes to R5:
through R2 is weight 10
through R3 is weight 20
i configured ip sla path-echo operation from R1 to R5
When all is up the packet goes R1-R2-R4-R5 and sh ip sla statistics aggregated shows all 3 hops with it's ip addresses
When i shutdown the fa1/0 on R1 with is connected to R2 the traceroute shows that packet now goes R1-R3-R4-R5 with is right too
The ip sla operation statistics also shows successes, but the hops addresses isn't changed
It still shows R1-R2-R4-R5
im a doing something wrong, or it is a bug/feature? :)
10-15-2014 10:02 AM
Post a sanitized config with just the relevant configs for review.
10-16-2014 12:15 AM
As this is a lab environment i will attach the configs themeselves
R1:
interface FastEthernet2/0
ip address 172.16.10.1 255.255.255.0
duplex half
!
interface FastEthernet3/0
ip address 172.16.20.1 255.255.255.0
duplex half
!
ip route 172.16.30.0 255.255.255.0 172.16.10.2
ip route 172.16.40.0 255.255.255.0 172.16.20.2
ip route 172.16.50.0 255.255.255.0 172.16.10.2 10
ip route 172.16.50.0 255.255.255.0 172.16.20.2 20
!
ip sla auto discovery
ip sla 10
path-echo 172.16.50.1
frequency 30
ip sla schedule 10 life forever start-time now
R2:
interface FastEthernet1/0
ip address 172.16.10.2 255.255.255.0
duplex half
!
interface FastEthernet2/0
ip address 172.16.30.2 255.255.255.0
duplex half
!
ip route 172.16.50.0 255.255.255.0 172.16.30.1
R3:
interface FastEthernet1/0
ip address 172.16.20.2 255.255.255.0
duplex half
!
interface FastEthernet2/0
ip address 172.16.40.2 255.255.255.0
duplex half
!
ip route 172.16.10.0 255.255.255.0 172.16.20.1
ip route 172.16.50.0 255.255.255.0 172.16.40.1
R4:
interface FastEthernet1/0
ip address 172.16.30.1 255.255.255.0
duplex half
!
interface FastEthernet2/0
ip address 172.16.40.1 255.255.255.0
duplex half
!
interface FastEthernet3/0
ip address 172.16.50.2 255.255.255.0
duplex half
!
ip route 172.16.10.0 255.255.255.0 172.16.30.2
ip route 172.16.20.0 255.255.255.0 172.16.40.2
ip route 172.16.50.0 255.255.255.0 172.16.30.1
R5:
interface FastEthernet1/0
ip address 172.16.50.1 255.255.255.0
duplex auto
speed auto
!
ip route 172.16.10.0 255.255.255.0 172.16.50.2
ip route 172.16.20.0 255.255.255.0 172.16.50.2
10-16-2014 04:48 AM
Hello
It seems you have given the sla number to the primary route but not an admin distance
Try something like this:
ip route 172.16.50.0 255.255.255.0 172.16.10.2 track 10 150
ip route 172.16.50.0 255.255.255.0 172.16.20.2 200
!
ip sla 10
imcp-echo 172.16.50.1 source-ip 172.16.10.2
frequency 30
ip sla schedule 10 life forever start-time now
res
Paul
10-16-2014 04:48 AM
ip route 172.16.50.0 255.255.255.0 172.16.10.2 10 150 - this gives me an error
after the "next hop" input i may input the route "distance"
---
i dont want to set the source-ip for the ip sla operation.
i want it to switch routes whr the primary interface goes down and it does! BUT, in the statistics the hops ip addresses stays the same as before. like it goes through primary route.
10-16-2014 05:37 AM
Hello
A track command
10-16-2014 05:53 AM
and after the track i need to specify my ip sla operation index? or just a random number?
10-16-2014 05:56 AM
hello
On the primary router the Ip sla number then the admin distance -
On the secondary route just the admin distance which will need to higher than the primary route admin distance
res
Paul
10-16-2014 06:42 AM
i assume that ip sla operation will fail if packets will go the second route, after i apply this change? am i correct?
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