From: Brian McGahan (bmcgahan@internetworkexpert.com)
Date: Thu Nov 04 2004 - 11:31:24 GMT-3
Tim,
The prefix-list ends in an implicit deny just like an
access-list. You need to do the following:
ip prefix-list AGG deny 129.3.0.0/16
ip prefix-list AGG permit 0.0.0.0/0 le 32
HTH,
Brian McGahan, CCIE #8593
bmcgahan@internetworkexpert.com
Internetwork Expert, Inc.
http://www.InternetworkExpert.com
Toll Free: 877-224-8987 x 705
Outside US: 775-826-4344 x 705
24/7 Support: http://forum.internetworkexpert.com
Live Chat: http://www.internetworkexpert.com/chat/
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
Of
> ccie2be
> Sent: Thursday, November 04, 2004 8:24 AM
> To: Group Study
> Subject: Filtering BGP aggragates (IEWB lab 12 task 6.26 - 6.27)
>
> Hi guys,
>
> I'm trying to filter an aggregate by using a neighbor x.x.x.x
prefix-list
> statement. But, it seems like it's not working as expected. So far,
I've
> been unable to figure out what I'm doing wrong.
>
> Essentially, the task requirement is to advertise an aggregate to some
> neighbors, but not to other neighbors. And, with the prefix filter I
want
> to
> filter just the aggregate - nothing more and nothing less.
>
> Here's the config:
> ******************************
> ip prefix-list AGG deny 129.3.0.0/16
>
> router bgp 200
> aggregate-address 129.3.0.0 255.255.0.0
>
> neighbor x.x.x.x prefix-list AGG out
>
>
> *******************************
>
> It seems simple enough but after configuring this, the bgp tables are
> missing
> much more than just the AGGregate.
>
> I also tried using this prefix:
>
> ip prefix-list AGG permit 129.3.0.0/16 but that was worse.
>
> Can anyone tell me how I'm screwing up?
>
> TIA, Tim
>
>
This archive was generated by hypermail 2.1.4 : Thu Dec 02 2004 - 06:57:38 GMT-3