[52100] in North American Network Operators' Group
Re: BGP Default Route
daemon@ATHENA.MIT.EDU (Jesper Skriver)
Sun Sep 15 11:04:18 2002
Date: Sun, 15 Sep 2002 17:03:52 +0200
From: Jesper Skriver <jesper@skriver.dk>
To: "Lupi, Guy" <Guy.Lupi@eurekaggn.com>
Cc: "'nanog@merit.edu'" <nanog@merit.edu>
Mail-Followup-To: Jesper Skriver <jesper@skriver.dk>,
"Lupi, Guy" <Guy.Lupi@eurekaggn.com>,
"'nanog@merit.edu'" <nanog@merit.edu>
In-Reply-To: <51592BEAAEE8D411A24400508B693A4E020A7E99@EXCHNYIS002>
Errors-To: owner-nanog-outgoing@merit.edu
On Sat, Sep 14, 2002 at 02:18:15PM -0400, Lupi, Guy wrote:
> I was wondering how people tend to generate default routes to
> customers running bgp.
Short answer: don't
Longer answer: To solve the exact problems you mention below,
only advertise a aggregate block of your own to this customer,
say x.x.0.0/16, then the customer will configure his device
something like
ip route 0.0.0.0 0.0.0.0 x.x.0.0
or
set routing-options static route 0.0.0.0/0 next-hop x.x.0.0 resolve
This will ensure that if the border router get's isolated, it will no
longer advertise x.x.0.0/16 to the customer, and the customer router can
choose a backup path.
/Jesper
--
Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456
Senior network engineer @ AS3292, TDC Tele Danmark
One Unix to rule them all, One Resolver to find them,
One IP to bring them all and in the zone to bind them.
