04-11-2018 07:38 AM - last edited on 03-25-2019 03:50 PM by ciscomoderator
04-11-2018 11:55 AM
Hello,
my first thought is to simply establish a neighbor on Swindon with Bracknell, and use the 'neighbor x.x.x.x default-originate' command.
04-11-2018 12:15 PM
Hi Georg,
Many Thanks for looking into it and providing the best solution. However, I apologize for not explaining the Question properly. Basically Currently Heathrow is acting as a Head Quarter and rest all are acting as Branches. Long-term Goal is to shut down Heathrow and make Swindon as Head Quarter. Solution works if there is a single Branch office, however, there are many Branches and I do not feel to advertise default route individually for every Branch office. Hope My query is making more sense now??
04-11-2018 12:25 PM - edited 04-11-2018 12:26 PM
You can't do what Georg suggests because you do not peer between your sites, you peer with your provider PEs (unless I have misunderstood what he was suggesting).
You can't really do this without the help of your provider because basically Bracknell simply sees the PE as the next hop for the default route, it is the PE routers that choose the best default route.
You would need to advertise the default route from Heathrow with a specific community and the one from Swindon with a different community and then your provider would need to choose which default route to advertise to which site(s) based on the community, assuming your provider would do this.
Alternatively you could create a GRE tunnel directly between Swindon and Bracknell and advertise a default through the tunnel and prefer it over the default via MPLS (or simply filter that default route out).
Sorry but as you do not really control the routing within the MPLS network there is no easy way to do this, or at least none that I am aware of.
Jon
04-11-2018 01:27 PM
Jon is right, my 'solution' would only work in conjunction with a tunnel that would make direct peering possible.
How is Heathrow announcing the default route ?
04-11-2018 01:33 PM
router bgp 64521
no synchronization
bgp log-neighbor-changes
network 10.101.65.0 mask 255.255.255.0
redistribute connected
redistribute static
neighbor 172.23.24.25 remote-as 12345
neighbor 172.23.24.25 ebgp-multihop 5
neighbor 172.23.24.25 default-originate
no auto-summary
R8#
04-11-2018 01:33 PM
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