[isp-bgp] Re: Will I be killed for not aggregating?

[haesu@...]

If you have same upstream at both places, you can tag the specifics with
no-export or equivalent provider-provided community tag. (Assuming the
upstream honors no-export)

That way as soon as traffic hits your upstream, it will send traffic
to appropriate noc while not propagating the specific(s) further outside.

If you have different upstreams at both sites, it gets a little trickier :)

Generally it maybe a good idea to use same sets of transit providers at both
sites so it is easier to do cold-potato routing through your provider's
backbone. But it all depends on price tag for the line at each site ofcourse..

-J

-- 
James Jun (formerly Haesu)
TowardEX Technologies, Inc.
1740 Massachusetts Ave.
Boxborough, MA 01719
Consulting, IPv4 & IPv6 colocation, web hosting, network design & implementation
http://www.towardex.com  | james@towardex.com
Cell: (978)394-2867      | Office: (978)263-3399 Ext. 170
Fax: (978)263-0033       | AIM: GigabitEthernet0
NOC: http://www.twdx.net | POC: HAESU-ARIN, HDJ1-6BONE

On Tue, Feb 17, 2004 at 11:08:44AM -0800, Rick Kunkel wrote:
> Hello all,
> 
> I've been doing some readin lately, after having gotten a fairly basic BGP
> setup going, and decided to finish up one of those RIPE slideshows that
> I'd kinda faltered through before I knew anything.
> 
> Slides 106 to 111 are about aggregation, but the one that really caught my
> eye was the last one, at:
> 
> http://www.ripe.net/ripe/meetings/archive/ripe-40/tutorials/bgp-tutorial/sld111.html
> 
> Supposing we have a /19 from ARIN, this means that they'd want us to
> announce that as one announcement, right?
> 
> The only problem is that we've currently got our address space pretty
> physically divided into two groups at two different NOCS that are
> separated by a relatively small pipe.  If we announce that block to our
> upstreams, I'm going to get a bunch of traffic that will opt for a path
> through my network, across that small pipe, right?
> 
> Ideally, we'd like to make two (or MAYBE more) announcements...each a /20.
> This way, we could make paths that traverse our network look a little
> longer by padding our AS an extra time or something.
> 
> But, as far as I can understand it, if the granularity is set to a /19, I
> just don't have that kind of flexibility, right?  (That's the THIRD
> sentence i've ended that way....ARGH...)
> 
> (Of course, in an ideal world, I've have a much larger connection between
> NOCS...)
> 
> Thanks,
> 
> Rick Kunkel
> 
> 
> 




> To unsubscribe via postal mail, please contact us at:
> Jupitermedia Corp.
> Attn: Discussion List Management
> 475 Park Avenue South
> New York, NY 10016
> 
> Please include the email address which you have been contacted with.







To unsubscribe via postal mail, please contact us at:
Jupitermedia Corp.
Attn: Discussion List Management
475 Park Avenue South
New York, NY 10016

Please include the email address which you have been contacted with.