Showing results for 
Search instead for 
Did you mean: 

Floating Static Route Taking Precedence Over BGP Route

Dan Man

Here's my situation.  We have about 80 sites that are on MPLS.  These sites backhaul through our main data center.  We have around 150 SDWAN sites.  In order for the SDWAN sites to reach the MPLS sites, they come back through the head end SDWAN router that is also in our data center.  The SDWAN routing uses static routes, on our core DC switches.  I have BGP setup, on our core DC switches, which peer with our DC MPLS router.  Our DC BGP configuration advertises these static routes so that our MPLS sites can route to our SDWAN sites. 


A few of our sites have a hybrid setup with a primary MPLS circuit, and a backup SDWAN circuit.  At these sites, i'm not using a routing protocol.  I'm simply using IP SLA with tracking and a default route with tracking, as well as a weighted floating static.  Let's say that MPLS fails at this site.  The tracking reachability goes down, so the static default is removed from the routing table, while the floating static is injected into the routing table.  In our DC, we also have a floating static for the SDWAN backup for this site(with a 200). Again, when this site MPLS circuit/router go down, it removes the route from BGP, so that the floating static, in our DC, is injected into the routing table.  Now when the MPLS side comes up again, the site tracking comes up, removing the floating static, and injecting the tracked default route.  However, in our DC, the BGP route is never injected into the routing table.  The route with the 200 stays as the primary route.  The only way BGP updates with the BGP route, is if I manually remove the static 200.  I'm assuming that I would have to setup local pref to change the behavior, but wanted to run this by you.  Let me know what you think.  Thanks!

1 Reply 1

Jon Marshall
VIP Community Legend VIP Community Legend
VIP Community Legend


It’s weight you need to modify not local preference. 


EBGP route learnt from EBGP peer has weight of 0 (MPLS routes) whereas EBGP route learnt from local redistribution has weight of 32768.


MPLS route lost and you use static which is redistributed into BGP so has weight of 32768. 


When MPLS link back the EBGP route from the peer is received but has weight of 0 and as the higher weight wins the redistributed static stays in routing table. 


Usual solution modify weight of MPLS routes to be > 32768.



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:

Recognize Your Peers