From: Jonathan Hays (nomad@gfoyle.org)
Date: Mon Jan 26 2004 - 01:06:05 GMT-3
you wrote:
>-----Original Message-----
>From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On
>Behalf Of David Deng
>Sent: Sunday, January 25, 2004 10:34 PM
>To: Michael Snyder; ccielab@groupstudy.com
>Cc: 'David Deng'
>Subject: RE: BGP aggregate address summary-only suppress
>aggregated routes
>
>
>Michael,
>
>What I am expecting is from the summary-only key word
>of aggregate-address, the 191.10.0.0/22 is expected.
>
>This is a straight forward question, let me know if
>any information is needed, I just don't know enough
>of aggregate-address to say if there is a problem or
>not ?
>
>Thanks,
>David
= = =
David,
You are correct in your understanding of the "aggregate-address
summary-only" command. As long as there is one of the specific routes of
the aggregate in the BGP table the aggregate will be advertised to your
neighbor and the individual specific routes will be suppressed. You
should see this on r2 (I recreated your scenario in my lab):
r2#sh ip bgp
BGP table version is 4, local router ID is 136.10.2.2
Status codes: s suppressed, d damped, h history, * valid, > best, i -
internal
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
*> 191.10.0.0/22 136.10.1.1 0 100 i
*> 191.10.4.0/24 136.10.1.1 0 0 100 i
*> 191.10.5.0/24 136.10.1.1 0 0 100 i
r2#
The reason you are not seeing the 191.10.0.0/22 aggregate route is
because access-list 4 is blocking it. You need to change access-list 4
to allow the aggregate route.
HTH,
Jonathan
This archive was generated by hypermail 2.1.4 : Mon Feb 02 2004 - 09:07:50 GMT-3