From: Nigel Taylor (nigel_taylor@xxxxxxxxxxx)
Date: Mon Jan 01 2001 - 16:30:16 GMT-3
Jiangg,tv
. I know from the command that you used it's suppose to
advertise the
aggregate-address based on the classfull nature of the mask that is entered
with
the command. So if you wanted to advertise the aggregate 160.10.0.0 only
you would need to the following statement;
"aggregate-address 160.10.0.0 255.255.0.0 summary-only.
Bassam Halabi's book goes into a number of scenarios on this topic. Based on
the following
output you included it tells us the route isn't being advertised to any
peers which is what
is meant by being suppressed. If the goal was to eliminate this network
from the routing
table(RIB), a route-map, distribute-list, filter-list and or prefix-list
would have been used....
show ip bgp 160.10.0.0
> > BGP routing table entry for 160.10.0.0/16, version 15
> > Paths: (1 available, best #1)
> > Advertisements of this net are suppressed by an aggregate.
> > Not advertised to any peer
<-------------------------------------------Here....!!!!!!!!!
> > Local
> > 0.0.0.0 from 0.0.0.0 (192.168.1.1)
> > Origin IGP, metric 0, localpref 100, weight 32768, valid, sourced,
> local, best, ref
> > 2
Nigel..
----- Original Message -----
From: tv <tvarriale@telocity.com>
To: Jiang <jianggx@transcentury.com.cn>
Cc: <ccielab@groupstudy.com>
Sent: Monday, January 01, 2001 1:32 PM
Subject: Re: strang thing about "aggregate-address address mask
summary-only"
> If I read that correctly, I think it means that 160.10.0.0 will be passed
in
> the update, but will not be entered into the routing table since it is
being
> suppressed.
>
> ----- Original Message -----
> From: "Jiang" <jianggx@transcentury.com.cn>
> To: <ccielab@groupstudy.com>
> Sent: Monday, January 01, 2001 12:57 AM
> Subject: strang thing about "aggregate-address address mask summary-only"
>
>
> > Hello, all
> >
> > Happy new year ^_^
> >
> > According the BGP4 Case Studies Section 4 in cco:
> > Please note that if we are aggregating a network that is injected
> > into our BGP via the network statement (ex: network 160.10.0.0 on RTB)
> > then the network entry is always injected into BGP updates even
> > though we are using "the aggregate summary-only" command.
> >
> > and I tried this in my lab and got different results, 160.10.0.0
> > was really suppressed.
> >
> > show ip bgp
> > *> 160.0.0.0/8 0.0.0.0 32768 i
> > s> 160.10.0.0/16 0.0.0.0 0 32768 i
> >
> > show ip bgp 160.10.0.0
> > BGP routing table entry for 160.10.0.0/16, version 15
> > Paths: (1 available, best #1)
> > Advertisements of this net are suppressed by an aggregate.
> > Not advertised to any peer
> > Local
> > 0.0.0.0 from 0.0.0.0 (192.168.1.1)
> > Origin IGP, metric 0, localpref 100, weight 32768, valid, sourced,
> local, best, ref
> > 2
> >
> > anyone can explain why?
> >
> > Hiler
> >
> >
> >
> > --
> > Best regards,
> > Guoxing Jiang mailto:jianggx@transcentury.com.cn
> >
> >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:27:20 GMT-3