Hello
First one needs to remember that it is always the sender that ultimately
decides which path to use. You can use route-map or import policy to
override local pref for each matched received prefix to steer exactly which
ISP you want to use on a per prefix basis. But so can everyone else.
Say
On Friday, 21 May, 2021 16:13, "nanoguser100 via NANOG" said:
> Correct me if I'm wrong here but I *could* take full table + AS on B
> meaning
> the traffic will prefer 'B' due it it having a more specific route since I'm
> only
> taking default from A (despite local pref). That will
On Fri, 21 May 2021 at 17:13, nanoguser100 via NANOG wrote:
> If I'm unable to do that will most provider prepend on your behalf so that
> ISP-A would add the prepends for only?
For this part, you will have to investigate which BGP
standard/extended/large communities your ISP-A/B supports.
Nanog,
At my organization we historically would get T1 ISPs at our POPs and take full
table + default. BGP would simply "do it's thing" and for the most part
everything worked out. There are instances where we have had heavily lopsided
traffic even though AS path length is the same.
To make
4 matches
Mail list logo
