From: Jonathan Natale (jonatale@xxxxxxxxxxxxx)
Date: Sat Jun 08 2002 - 22:53:45 GMT-3
if you have any bgp routes then you can aggregate with the correct net/mask
(need to do some binary math. do you have any bgp rts?
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Nick Shah
Sent: Tuesday, June 04, 2002 2:03 PM
To: Rajani Deshpande; Chua, Parry; McEvoy, Joseph; David Luu;
ccielab@groupstudy.com
Subject: Re: Question: Alternative way of injecting routes into BGP?
yes, u r right,
but you need to have *network* command for atleast one matching prefix(in
order to use aggregate), and the criteria clearly states *not* to use
network or redistribute command.
rgds
Nick
-----Original Message-----
From: Rajani Deshpande <rajani_desh@yahoo.com>
To: Nick Shah <nshah@connect.com.au>; Chua, Parry <Parry.Chua@hp.com>;
McEvoy, Joseph <Joseph.McEvoy@us.didata.com>; David Luu
<wicked01@ix.netcom.com>; ccielab@groupstudy.com <ccielab@groupstudy.com>
Date: Wednesday, 5 June 2002 5:03
Subject: Re: Question: Alternative way of injecting routes into BGP?
>This can be achived by aggregate-address command, if
>he has any 135.3.0.0 route in his bgp routing table.
>
>Rajani
>--- Nick Shah <nshah@connect.com.au> wrote:
>> agreed..
>>
>> but, he states that he wants to advertise his pod's
>> topology "which is
>> 135.3.0.0/16" .. so we have to assume his router
>> knows about some/most/all
>> of 135.3.0.0/16.
>>
>> So, if the native router knows of the /16,
>> "default-originate" will help..
>> wont it ??
>>
>> rgsd
>> Nick
>> ----- Original Message -----
>> From: "Chua, Parry" <Parry.Chua@hp.com>
>> To: "Nick Shah" <nshah@connect.com.au>; "McEvoy,
>> Joseph"
>> <Joseph.McEvoy@us.didata.com>; "David Luu"
>> <wicked01@ix.netcom.com>;
>> <ccielab@groupstudy.com>
>> Sent: Saturday, June 01, 2002 1:28 PM
>> Subject: RE: Question: Alternative way of injecting
>> routes into BGP?
>>
>>
>> > May be I mis-read his requirement, if he want to
>> advertise 135.3.0.0/16 to
>> a neighour w/o
>> > knowing how to reach any subnet of 135.3.0.0/16,
>> advertise a default route
>> out is no going to help.
>> >
>> > > Parry Chua
>> > >
>> > >
>> >
>> >
>> > -----Original Message-----
>> > From: Nick Shah [mailto:nshah@connect.com.au]
>> > Sent: Saturday, June 01, 2002 11:23 AM
>> > To: Chua, Parry; McEvoy, Joseph; David Luu;
>> ccielab@groupstudy.com
>> > Subject: Re: Question: Alternative way of
>> injecting routes into BGP?
>> >
>> >
>> > Parry,
>> >
>> > I agree with you but......
>> >
>> > If you read Joseph's criteria, it states advertise
>> a network without using
>> > NETWORK or REDISTRIBUTE command plus advertise
>> only to this one peer. This
>> > would narrow down to advertising a default route
>> to the neighbor.
>> >
>> > If you chose to disagree, pl. advise an alternate
>> way to satisfy Joseph's
>> > criteria
>> >
>> > rgds
>> > Nick
>> > ----- Original Message -----
>> > From: "Chua, Parry" <Parry.Chua@hp.com>
>> > To: "Nick Shah" <nshah@connect.com.au>; "McEvoy,
>> Joseph"
>> > <Joseph.McEvoy@us.didata.com>; "David Luu"
>> <wicked01@ix.netcom.com>;
>> > <ccielab@groupstudy.com>
>> > Sent: Saturday, June 01, 2002 1:19 PM
>> > Subject: RE: Question: Alternative way of
>> injecting routes into BGP?
>> >
>> >
>> > You tell your neigh x.y.z.a that your AS is the
>> defaut route for their
>> > network. It sound like
>> > some information is missing. If you don't even
>> know such network within
>> your
>> > AS, how can you
>> > advertise and tell other how to reach that
>> network.
>> >
>> > > Parry Chua
>> > >
>> > >
>> >
>> >
>> > -----Original Message-----
>> > From: Nick Shah [mailto:nshah@connect.com.au]
>> > Sent: Saturday, June 01, 2002 10:49 AM
>> > To: McEvoy, Joseph; 'David Luu';
>> ccielab@groupstudy.com
>> > Subject: Re: Question: Alternative way of
>> injecting routes into BGP?
>> >
>> >
>> > I could be wrong. but how about...
>> >
>> > neighbor x.y.z.a remote-as <<backbone as>>
>> > neighbor x.y.z.a default-originate
>> >
>> > This *could* be a third way of injecting the
>> *route*. Of course this will
>> > inject a default route, but it is one method that
>> satisfies both of your
>> > criteria (ie. dont use network or redistribute,
>> dont use static, no other
>> > ibgp/ebgp peers should know about this route)
>> >
>> > What do you think ?
>> >
>> > Nick
>> > ----- Original Message -----
>> > From: "McEvoy, Joseph"
>> <Joseph.McEvoy@us.didata.com>
>> > To: "'David Luu'" <wicked01@ix.netcom.com>;
>> "McEvoy, Joseph"
>> > <Joseph.McEvoy@us.didata.com>;
>> <ccielab@groupstudy.com>
>> > Sent: Saturday, June 01, 2002 11:58 AM
>> > Subject: RE: Question: Alternative way of
>> injecting routes into BGP?
>> >
>> >
>> > > That is not working because I do not have any
>> subnets of 135.3.0.0 /16
>> in
>> > my
>> > > bgp table. That's because I haven't used any
>> network or redistribute
>> > > commands.
>> > >
>> > > -----Original Message-----
>> > > From: David Luu [mailto:wicked01@ix.netcom.com]
>> > > Sent: Friday, May 31, 2002 9:47 PM
>> > > To: Joseph McEvoy; ccielab@groupstudy.com
>> > > Subject: Re: Question: Alternative way of
>> injecting routes into BGP?
>> > >
>> > > aggregate-address 135.3.0.0 255.255.0.0
>> summary-only
>> > >
>> > > At 08:51 PM 5/31/2002 -0400, Joseph McEvoy
>> wrote:
>> > > >Hello,
>> > > >
>> > > >I know of two ways to get routes injected into
>> BGP. The first is the
>> > > network
>> > > >command, the second is to redistriubute. Does
>> anybody know of a third
>> > way?
>> > > >
>> > > >I am doing a lab where the directions state
>> that I need to advertize my
>> > > pod's
>> > > >topology 135.3.0.0 /16 to the backbone (in a
>> different AS) without
>> using
>> > > the
>> > > >redistribute command and without using the
>> network command. It also
>> > states
>> > > >that I can not use any static routes. Lastly it
>> sates that this route
>> > > should
>> > > >not appear on any of the routers in my pod,
>> just on the backbone. How
>> in
>> > > the
>> > > >world can this be done?
>> > > >
>> > > >TIA
>> > >
>>
This archive was generated by hypermail 2.1.4 : Tue Jul 02 2002 - 08:12:29 GMT-3