packet loss monitoring and automatic rerouting
marcusaureliusbrutus
Member Posts: 73 ■■□□□□□□□□
in CCNP
Hi,
I need an expert recommendation on the best way to monitor routes for packet loss and implement a failover mechanism should packet loss be encountered.
I am a bit familiar with sla and object tracking however I am not sure whether these options would allow the below scenario.
scenario:
5 pings to a remote IP
3 out of 5 ping failures or more would activate track applied on static route.
Also, is there a dynamic protocol that covers packet loss as well and not just a link failure?
Thanks in advance.
I need an expert recommendation on the best way to monitor routes for packet loss and implement a failover mechanism should packet loss be encountered.
I am a bit familiar with sla and object tracking however I am not sure whether these options would allow the below scenario.
scenario:
5 pings to a remote IP
3 out of 5 ping failures or more would activate track applied on static route.
Also, is there a dynamic protocol that covers packet loss as well and not just a link failure?
Thanks in advance.
Comments
-
Cucumber Member Posts: 192I would not call myself an expert, but you might want to take a look at Cisco's IOS Embedded Event Manager technology (EEM) for things like that.
Good luck.I hate pandas -
ilcram19-2 Banned Posts: 436marcusaureliusbrutus wrote: »Hi,
I need an expert recommendation on the best way to monitor routes for packet loss and implement a failover mechanism should packet loss be encountered.
I am a bit familiar with sla and object tracking however I am not sure whether these options would allow the below scenario.
scenario:
5 pings to a remote IP
3 out of 5 ping failures or more would activate track applied on static route.
Also, is there a dynamic protocol that covers packet loss as well and not just a link failure?
Thanks in advance.
yes it would with sla tracking you can set up a back up route,
like below
ip route 1.1.1.1 255.255.255.255 192.168.1.1 track 1
ip sla 1
icmp-echo 1.1.1.1 source-ip 10.1.2.1
timeout 1000
frequency 30
ip sla schedule 1 life forever start-time now
so if the host stops responding it will use that new route.
im not an expert but i've done this a few time an it works