[47766] in North American Network Operators' Group
Re: BGP and aggregation
daemon@ATHENA.MIT.EDU (E.B. Dreger)
Sun May 12 23:44:14 2002
Date: Mon, 13 May 2002 03:43:24 +0000 (GMT)
From: "E.B. Dreger" <eddy+public+spam@noc.everquick.net>
To: Ralph Doncaster <ralph@istop.com>
Cc: PS <pschultz@pschultz.com>, "nanog@merit.edu" <nanog@merit.edu>
In-Reply-To: <Pine.LNX.4.21.0205122255430.9713-100000@cpu1693.adsl.bellglobal.com>
Message-ID: <Pine.LNX.4.20.0205130335090.32238-100000@www.everquick.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Errors-To: owner-nanog-outgoing@merit.edu
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@brics.com>
To: blacklist@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@brics.com>, or you are likely to
be blocked.
