Re: Redundancy & Summarization

2009-08-22 Thread Hector Herrera
On Sat, Aug 22, 2009 at 6:52 AM, Adam Greene wrote: > Another option could be to announce one /17 to each upstream provider and > use conditional BGP to announce the other /17 to the provider that's still > active in the event that one provider goes down. > Maybe I'm wrong, but I think this method

Re: Redundancy & Summarization

2009-08-22 Thread Patrick W. Gilmore
Sent from my iPhone, please excuse any errors. On Aug 22, 2009, at 9:52, Adam Greene wrote: Another option could be to announce one /17 to each upstream provider and use conditional BGP to announce the other /17 to the provider that's still active in the event that one provider goes down

Re: Redundancy & Summarization

2009-08-22 Thread Adam Greene
Another option could be to announce one /17 to each upstream provider and use conditional BGP to announce the other /17 to the provider that's still active in the event that one provider goes down. On 8/21/2009 4:08 PM, Patrick W. Gilmore wrote: On Aug 21, 2009, at 3:47 PM, Brian Dickson wrot

Re: Redundancy & Summarization

2009-08-21 Thread Patrick W. Gilmore
On Aug 21, 2009, at 3:47 PM, Brian Dickson wrote: My institution has a single /16 spread across 2 sites: the lower / 17 is used at site A, the upper /17 at site B. Sites A & B are connected internally. Currently both sites have their own ISPs and only advertise their own /17's. For redund

Re: Redundancy & Summarization

2009-08-21 Thread Brian Dickson
> My institution has a single /16 spread across 2 sites: the lower /17 is > used at site A, the upper /17 at site B. Sites A & B are connected > internally. Currently both sites have their own ISPs and only advertise > their own /17's. For redundancy we proposed that each site advertise > both t

Re: Redundancy & Summarization

2009-08-21 Thread Jack Bates
Grzegorz Janoszka wrote: No, BGP does not work this way. But you may force some carriers to have only /16. First, you may try to announce the /17's with the community no-export, so they will be seen only by your direct ISP, not by the rest of the world. Or you may try to use some other commun

Re: Redundancy & Summarization

2009-08-21 Thread Grzegorz Janoszka
Gaynor, Jonathan wrote: My institution has a single /16 spread across 2 sites: the lower /17 is used at site A, the upper /17 at site B. Sites A & B are connected internally. Currently both sites have their own ISPs and only advertise their own /17's. For redundancy we proposed that each site

RE: Redundancy & Summarization

2009-08-21 Thread Harper, Jeff
Hi Jon, If I personally saw it, I wouldn't bother since I would assume there would be a method to your madness. ;-) Jeff -Original Message- From: Gaynor, Jonathan [mailto:jonathan.gay...@fccc.edu] Sent: Friday, August 21, 2009 10:58 AM To: nanog@nanog.org Subject: Redun

Redundancy & Summarization

2009-08-21 Thread Gaynor, Jonathan
My institution has a single /16 spread across 2 sites: the lower /17 is used at site A, the upper /17 at site B. Sites A & B are connected internally. Currently both sites have their own ISPs and only advertise their own /17's. For redundancy we proposed that each site advertise both their own /