Hey Alex,
Thank you for the detailed input, greatly appreciated. AS65124 has a single EBGP peering to AS100 in the master routing instance. As far as expected next hop, great question and I didn't really put much thought in to the next hop being anything other than the egress interface of AS100.
I am just showing AS65124 in this diagram, but I have approximately 35 other AS's downstream from AS100. The end goal is for half of my locations to prefer AS65150(west) default route, while the other half prefer AS65020(east) default route based upon a policy of my choosing.
My concern with AS100 only advertising a single 0/0 would be that I don't have any control over which 0/0 they advertise where. In addition to the 0/0 being advertised I also have all sites advertising their prefix to one another through AS100, effectively creating a full mesh. My plan is to leverage LP on the import policy of AS65124 to prefer the default route from AS65150 over that of AS65020. I would like both routes in the RIB, but only a single route in the FIB.
Based upon this, it appears "accept-remote-nexthop" and having AS100 use distinctly different next hops, as well as advertising those /32 may be the way to go. Do you see any opportunity to leverage addpath on the EBGP peering from AS100 to AS65124?
↧