11-22-2013 01:56 PM - edited 03-04-2019 09:39 PM
I hope anyone can assist. I am trying to set up a secondary MPLS router at a secondary data center. Currently the primary MPLS router at the primary site injects a default route into the remote MPLS routers via default originate under its bgp proccess (i.e - neighbor X.X.X.X default-originate). I would like to set up the secondary MPLS router to be able to inject a default route as well into the MPLS cloud, maybe using the same method as the primary via default originate. But my issue is both MPLS routers (primary and secondary) would advertise their default routes to the clould (remote MPLS routers) with the same cost\metric. And I would like to make sure the secondary MPLS router's default route is never prefered unles the primary MPLS routers goes away\down, etc
MPLS-1 MPLS-2
| |
default-originate default-originate (less preferred)
| |
| |
--------------------------------------------------
| |
| |
remote MPLS remote MPLS
Any help would be greately appreciated
marramix01
11-22-2013 02:24 PM
marramix01
Part of the difficulty with your question is that BGP does not advertise any cost/metric. So there is not anything simple like that to manipulate. In advertising network prefixes you can do things like prepending to make an advertisement from the secondary less favorable than the advertisement from the primary. But I do not think that this works for default originate. Perhaps you could look into some kind of conditional advertisement that would advertise the default only when it did not see the advertisement from the primary?
HTH
Rick
04-02-2016 08:04 PM
I was facing this kind of problem in a lab I was doing. Just include a route-map in default-originate.
neighbor x.x.x.x default-originate route-map MED.
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