--- alo.anesi@bluesky.as wrote:
From: Aloiamoa Anesi alo.anesi@bluesky.as
On another note, I played with AS prepends a while ago in order to try
and force inbound route selection over our primary link (20Mb versus
our 1.5Mb backup link). After much reading and fudging, I abandoned it
and split our allocation instead. Advertising two /21s in addition to
our /20 over the primary link and only the /20 on our backup link. The
CIDR guys probably wouldn't be too happy if we went around doing this
with anything smaller than a /23, but it's a good tradeoff IMO if you
really need to force inbound route selection.
-------------------------------------------------------
I recall that list conversation a while back and I always wondered how you resolved it... :-) I actually went the same way. I used to do AS path prepends, but it was a struggle. One of our upstreams has better paths to the destinations our customers get the most traffic from and we have smaller pipes to them. We're (Hawaiian Telcom) an eyeball network not a content network, for the most part, so our inbound traffic is way higher than our outbound traffic. The pipes to the more preferred upstream were getting saturated while the provider we had big pipes with was being underutilized. Now, I just announce our aggregates to all upstreams and a more specific to the one I want to attract the higher level of traffic from. I believe you should be able to advertise a more specific as small as a /24 and have no troubles, though, just in case you need more granularity in your traffic balancing.
scott
=================================
================================
pacnog mailing list
pacnog@pacnog.org
http://mailman.apnic.net/mailman/listinfo/pacnog
