05-30-2017 09:24 AM - edited 03-05-2019 08:37 AM
Hello everyone,
is there any way to route the traffic via secondary link if the latency through primary link reach >50ms ? In this scenario i'm using ebgp,ibgp and hsrp.
05-30-2017 09:41 AM
Might help if you indicated where you are using BGP and HSRP.
Jon
05-30-2017 09:55 AM
I'm using HSRP in LAN 192.168.1.0/24.R1 will be active and R2 will be standby mode.
ibgp is between R1 and R2 and eBGP is with Primary and Secondary service provider from R1 and R2 respectively and R3 also.
05-30-2017 09:58 AM
As Reza says you could use IP SLA for latency and then tie that with EEM to shut the BGP session on the primary which would then mean R1 would use R2 to send traffic out.
There may be an easier solution but nothing springs to mind at the moment.
Jon
05-30-2017 10:02 AM
You can setup IP SlAs with tracking.
see link:
http://packetpushers.net/using-ip-sla-delay-feature-to-safely-monitor-lossy-links/
https://supportforums.cisco.com/document/32186/dual-internet-links-nating-pbr-and-ip-sla
HTH
05-30-2017 09:48 AM
Hi,
>50ms to what destination?
If the latency is on the Internet, you can set up SLAs with multiple providers.
HTH
05-30-2017 10:03 AM
Ok both links will be 1Mbps L3VPN MPLS link and destination will be 172.16.1.0/24 network from 192.168.1.0/24.
Is there any other solution apart from SLA ?
05-30-2017 10:42 AM
Something has to monitor the latency and BGP can't do that.
You could, I suppose, just include everything in an EEM script ie. do your own latency monitoring.
Jon
05-30-2017 12:19 PM
Possibly PfR.
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