cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
967
Views
0
Helpful
3
Replies

IP sla is not working

onlinerecharge
Level 1
Level 1

Hi i am facing a huge problem in IPSLA in cisco 3650 switch,

problem is my track is now being down at the time of link failure. thats why static route is not inappear from routing table.

here is the configuration file,

track 422 ip route 221.135.132.98 255.255.255.255 reachability

ip route 221.135.132.98 255.255.255.255 192.168.200.200 track 422                               ----- tracking route

ip route 0.0.0.0 0.0.0.0 192.168.200.200 track 422                                                          ------ primary router

ip route 0.0.0.0 0.0.0.0 192.168.200.100 200                                                                 -------secondary router

ip route 10.10.10.0 255.255.255.0 192.168.200.100

ip route 30.30.30.0 255.255.255.0 192.168.200.100

!

ip sla 422

icmp-echo 221.135.132.98

threshold 1000

timeout 1000

frequency 5

please tell me what is the misconfiguration here

1 Accepted Solution

Accepted Solutions

cadet alain
VIP Alumni
VIP Alumni

Hi,

ip sla schedule 422 life forever start now

no ip route 221.135.132.98 255.255.255.255 192.168.200.200 track 422

ip route 221.135.132.98 255.255.255.255 192.168.200.200

no track 422 ip route 221.135.132.98 255.255.255.255 reachability

track 422 rtr 422 reachability

Regards

Alain

Don't forget to rate helpful posts.

Don't forget to rate helpful posts.

View solution in original post

3 Replies 3

Bilal Nawaz
VIP Alumni
VIP Alumni

Hello, could you kindly tell us the topology, where is your 3560 connected to, how does the primary router and secondary router come in to the frame. Which IPs belong where? A running config would be good to see?

Also I noticed you have a default route with the track command and the other static route too. Both of these will be taken out of the routing table since 422 is unreachable/down.

IP SLA is working if the tracked routes gets taken out when 221.135.132.98 is unreachable... Im not sure it this is the case.

Then the Ip route 0.0.0.0 0.0.0.0 192.168.200.100 200 should come active.

You can see my working example I tested in a lab couple of days ago:

https://supportforums.cisco.com/message/3900451#3900451

I would do this, however sla and track commands vary from IOS:

ip sla monitor 422

type echo protocol ipIcmpEcho 221.135.132.98

frequency 5

ip sla monitor schedule 422 life forever start-time now

!

track 422 rtr 422 reachability

!

ip route 221.135.132.98 255.255.255.255 192.168.200.200

ip route 0.0.0.0 0.0.0.0 192.168.200.200 track 422 [Primary]

ip route 0.0.0.0 0.0.0.0 192.168.200.100 200 [Secondary]

ip route 10.10.10.0 255.255.255.0 192.168.200.100

ip route 30.30.30.0 255.255.255.0 192.168.200.100

Hope this helps

Sent from Cisco Technical Support iPhone App

Please rate useful posts & remember to mark any solved questions as answered. Thank you.

cadet alain
VIP Alumni
VIP Alumni

Hi,

ip sla schedule 422 life forever start now

no ip route 221.135.132.98 255.255.255.255 192.168.200.200 track 422

ip route 221.135.132.98 255.255.255.255 192.168.200.200

no track 422 ip route 221.135.132.98 255.255.255.255 reachability

track 422 rtr 422 reachability

Regards

Alain

Don't forget to rate helpful posts.

Don't forget to rate helpful posts.

Thank you so much problem got resolved

Only one problem i am having this track got down frequently and came up within 5 seconds. I am not able to understand why it goes down so frequently?

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:

Review Cisco Networking products for a $25 gift card