From: David Ham (ccieau@xxxxxxxxxxx)
Date: Mon May 27 2002 - 08:23:41 GMT-3
paul,
Yes, you must create a loopback as well as network statement to allow the
aggregate address to be put in the routing table.
David Ham
>From: Paul <p_chopin@yahoo.com>
>Reply-To: Paul <p_chopin@yahoo.com>
>To: David Ham <ccieau@hotmail.com>
>CC: ccielab@groupstudy.com
>Subject: Re: BGP aggregation
>Date: Sun, 26 May 2002 23:39:09 -0700 (PDT)
>
>If you filter all incoming routes , how are you going
>to create aggreate? You must then use network
>statement
>I guess
>Paul
>--- David Ham <ccieau@hotmail.com> wrote:
> > I don't think Table-map do the trick.
> > You might have to filter the all the incoming routes
> > before getting into R1
> > and put the aggregate statement at R1. Only problem
> > is other routers would
> > think the aggregate route is from R1 as the origin
> > of aggregate route will
> > bg IGP.
> >
> > Regards,
> >
> > David Ham
> > OPTUS
> >
> >
> > >From: Carlos G Mendioroz <tron@huapi.ba.ar>
> > >Reply-To: Carlos G Mendioroz <tron@huapi.ba.ar>
> > >To: Paul <p_chopin@yahoo.com>
> > >CC: Groupstudy ccielab list
> > <ccielab@groupstudy.com>
> > >Subject: Re: BGP aggregation
> > >Date: Sun, 26 May 2002 11:03:03 -0300
> > >
> > >How about using table-map to filter the specifics ?
> > >
> > >Paul wrote:
> > > >
> > > > Hi guy,
> > > > Here it is scenario. R1 is getting external
> > routes
> > > > from other AS. R1 is doing aggregation and
> > sending
> > > > only aggregate towards internal peers. Question
> > is how
> > > > to prevent R1 from installing specific routes
> > into its
> > > > own routing table.It should have only aggregate.
> > > > Paul
> > > >
> > > >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:59:09 GMT-3