| | | | | | | | |
|
|
|
You're here: Home |
Alo Anesi wrote:
All-So from everything we discusses at the previous PACNOGs, it seems splitting up prefix advertisements is the best (only?) way to split inbound traffic when dealing with two different upstreams. My question is, can I go as far as splitting at the /22 boundary for my /20? I could split at the /21 boundary, but with the way we've been allocating customer addresses 90% of my usage occurs in the first half of my /20. I realize the CIDR folks may frown on de-aggregation, but I need some way to load balance two links of different sizes from 2 different upstreams.
I'm sure others will chime in here, but I think generally de-aggregation is frowned upon, but it sometimes can be the only way.
I've had reasonable success in the past by using a combination of heavy route prepending, and taking advantage of upstream providers communities and other TE knobs.
You may be able to do some load balancing by seeing if your upstreams support communities, and what communities they support. e.g. selective prepends to some of their peers (or all peers). You might also be able to deaggregate towards an upstream but with a no-export-to-peers community, meaning only their customers will follow the more specifics, and similar such tweaks.
aj.
