| | | | | | | | |
|
|
|
You're here: Home |
After attending PACNOG3, I had a moment of clarity and managed to fix my multihoming problem. I thought you guys might be interested in the solution even though it's not something I would usually recommend. My main problem was that I only had a T1 connection to my secondary upstream provider. However, even with as-path prepends, I was getting more inbound traffic than the T1 could provide and ran into congestion problems. This secondary link is purely used as a backup since it is much smaller than our primary path. The fix was to advertise two /21 prefixes out of my /20 on my primary provider. This would force BGP path selection to only use the primary provider since it had the longest prefix match. For redundancy, I still advertise my full /20 to both upstreams. Now, this is actually bad CIDR practice, but I would deem it a necessary evil in my case. But feel free to flame me if you have the urge. =) ------------------------------------------------------- Aloiamoa Anesi, Jr. Network Operations Engineer Blue Sky Communications 478 Laufou Shopping Ctr Pago Pago, American Samoa 96799 -- Ph: +1.684.699.2759 ext 1098 Cell: +1.684.258.1098 VoIP Business Hours: 1098@voip.bluesky.as On Feb 7, 2007, at 4:18 PM, Terry Manderson wrote:
|
