From: Christopher Van Heuveln (cvanheuv@xxxxxxxxx)
Date: Wed Aug 16 2000 - 08:49:17 GMT-3
Doh!
Yeah, you're right. I stand corrected. Although the syntax should be:
neigh x.x.x.x default-originate
Note that you won't see it in the advertisement list on this router
when you:
sh ip bgp nei x.x.x.x adv
...but you will see it in the received routes on the peer when you:
sh ip bgp nei x.x.x.y rou
Chris
On Tue, Aug 15, 2000 at 10:27:04PM -0700, Kenny Sallee wrote:
> I thought you could originate a default to an EBGP neighbor like this:
>
> neigh x.x.x.x default-info originate
>
> And that it didn't matter wether there was a default in the local RIB or
> not....
>
> Kenny
>
> ----- Original Message -----
> From: "Christopher Van Heuveln" <cvanheuv@cisco.com>
> To: "Mark H. Degner" <mark@degner.org>
> Cc: <ccielab@groupstudy.com>
> Sent: Tuesday, August 15, 2000 5:05 AM
> Subject: Re: BGP default network
>
>
> >
> >
> > On Mon, Aug 14, 2000 at 08:54:40PM -0500, Mark H. Degner wrote:
> > > Brian,
> > >
> > > BGP CAN generate a default route. Note the 'default-information
> originate' command that is
> >
> > Mark,
> >
> > I may be taking your statement out of context but let me clarify it
> anyway.
> > BGP "default-info originate" does not work the same as with some of the
> > other routing protocols. BGP will not *create* a default route just
> because
> > you use this command (like OSPF can do). There are two ways to get a
> > default route into the BGP RIB:
> >
> > 1.
> >
> > router bgp 1
> > redist <protocol>
> > default-information originate
> >
> > (if you leave either statement out it will not go in the RIB)
> >
> > 2.
> >
> > router bgp 1
> > network 0.0.0.0 <-- puts it in the RIB *and* advertises it
> >
> > But both methods require you to have a 0.0.0.0 route already in
> > the local routing table.
> >
> > Chris
> >
> >
> >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:24:26 GMT-3