Ah, perfect, and so obvious now that I think about it. Easy to fix too as they already have an IGP on those links.
Thanks! On 1/20/17, 12:38 PM, "Gert Doering" <[email protected]> wrote: Hi, On Fri, Jan 20, 2017 at 05:10:56PM +0000, David Hubbard wrote: > Hello all, I have a setup where one BGP AS exists at two physical locations, with an edge router at each location peered to different upstreams. The two edge routers are interconnected with a 40gig and 10gig link, each with its own interface/address, so there are two iBGP sessions between the same two routers. The intent of the 10gig is only to be used as backup, and when I first brought it up, the routers of course began treating them as equal cost paths (from BGP perspective) and used both. The way I initially worked around that was via a route map on both sides that assigns a higher non-default weight to advertisements coming in via the iBGP session on the 40gig link. "The normal way" to do iBGP is "between loopbacks" and have an IGP distribute loopback reachability across available links. Which will automatically achieve what you're asking for :-) gert -- USENET is *not* the non-clickable part of WWW! //www.muc.de/~gert/ Gert Doering - Munich, Germany [email protected] fax: +49-89-35655025 [email protected] _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
