From: Bit Gossip (bit.gossip@chello.nl)
Date: Fri Aug 10 2007 - 00:41:18 ART
Hi Patrick,
I think this happens because the aggregate-address command looks for
contributing routes in the bgp table not in the routing table. So probably
if you redistribute the loopback it will work as well.
thanks,
bit.
----- Original Message -----
From: "Patrick Galligan" <pgalligan@gmail.com>
To: "Cisco certification" <ccielab@groupstudy.com>
Sent: Friday, August 10, 2007 5:57 AM
Subject: BGP aggregate addresses
> Hi group,
>
> My understanding of BGP aggregate addresses is that it will advertise
> the aggregate if there is at least one network within the aggregate in
> the BGP table. However, I have the following problem:
>
> I am aggregating 10.64.192.0/19 from an iBGP peer which is a route
> reflector client. It has loopbacks within this range, eg
> 10.64.200.1/24, but the aggregate only gets advertised if
> 10.64.192.0/24 is in the BGP table. Is this normal behaviour?
>
> Thanks,
> Patrick
>
> --
> You can't cheat death forever, but you can make the b!stard work for it.
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Sat Sep 01 2007 - 11:32:10 ART