BGP and aggregation

Mon May 13 03:43:24 UTC 2002

RD> Date: Sun, 12 May 2002 22:57:42 -0400 (EDT)
RD> From: Ralph Doncaster

RD> Hmm... the default route idea sounds even easier than my iBGP
RD> over a transit link.  I think I'll try your idea first.

Assuming your upstream knows how to get to the other location.

You want city "A" with upstream "X" to send all inter-AS traffic
while your pipe to "X" is up.  When it fails, you want location
"A" traffic to go over your internal link to location "B", which
uses upstream "Y".

If your inter-city link fails, "B" should use "Y" for all
inter-AS traffic, and you _somehow_ need "A" and "B" to
communicate.

As long as this is getting messy... I'm tempted to suggest
confederations.  Or spending a few extra bucks on a second ASN,
although that doesn't scale.

--
Eddy

Brotsman & Dreger, Inc. - EverQuick Internet Division
Phone: +1 (316) 794-8922 Wichita/(Inter)national
Phone: +1 (785) 865-5885 Lawrence

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Date: Mon, 21 May 2001 11:23:58 +0000 (GMT)
From: A Trap <blacklist at brics.com>
To: blacklist at brics.com
Subject: Please ignore this portion of my mail signature.

These last few lines are a trap for address-harvesting spambots.
Do NOT send mail to <blacklist at brics.com>, or you are likely to
be blocked.