From: Michael Snyder (msnyder@revolutioncomputer.com)
Date: Mon Jan 26 2004 - 00:47:09 GMT-3
So, your /24's are being withdrawn, but the /22 isn't showing up on the
other router.
Kill your route-map, and see what you get.
On other possibility is if the confederation makes the new route look
like it came from the same AS (because of the confederation) it won't
propagate. Don't think that's the case here. Had fun trouble shooting
one like that in the past.
BTW, if you would always show your bgp tables in the future.
-----Original Message-----
From: David Deng [mailto:glend_99@yahoo.com]
Sent: Sunday, January 25, 2004 9: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
--- Michael Snyder <msnyder@revolutioncomputer.com>
wrote:
> David,
>
> What is it that you wanting? You seem to be leaving
> something out.
>
> I did an ipexpert lab a week ago where I had to send
> the /22 summary to
> one neighbor; and the just some of the /24
> suppressed routes to other
> neighbor; and oh, stop the /22 from backfeeding the
> direction the /24's
> came from.
>
> My fix was prefix lists. One for each neighbor.
> You can used them just
> like route-maps for outgoing bgp routes.
>
> From memory, it looked something like this.
>
> aggregate-address 172.16.0.0 255.255.252.0
>
>
> ip prefix-list 1 seq 5 deny 172.16.0.0/22 ge 24 le
> 24
> ip prefix-list 1 seq 10 permit 0.0.0.0/0 le 32
> !
>
> ip prefix-list 2 seq 5 permit 172.16.3.0/24
> ip prefix-list 2 seq 10 deny 172.16.0.0/22 le 32
> ip prefix-list 2 seq 15 permit 0.0.0.0/0 le 32
> !
> ip prefix-list 3 seq 5 deny 172.16.0.0/22
> ip prefix-list 3 seq 10 permit 0.0.0.0/0 le 32
>
>
>
>
>
>
>
>
>
>
> -----Original Message-----
> From: David Deng [mailto:glend_99@yahoo.com]
> Sent: Sunday, January 25, 2004 8:00 PM
> To: ccielab@groupstudy.com
> Subject: BGP aggregate address summary-only suppress
> aggregated routes
>
> Hi group,
>
> I have a question on why the Aggresgate address will
>
> suppress the address being aggregated when
> summary-only key word is used, I am expecting a
> summary route
> 191.10.0.0/22 for 191.10.1-3.0 nets.
>
> Any remedy ?
>
> As soon as the aggregate command is issuedm the
> routes
> are withdrawn.
>
> r1 has 5 loopbacks from
> 191.10.1.1/24-191.10.5.1/24.
>
> lo0: 136.10.1.1 Lo0:136.10.2.2
> r1 ----------------------------r2
> .1 136.10.12.x .2
>
>
> ---------------------------------------------
> r1 config:
>
> router bgp 100
> no synchronization
> bgp router-id 136.10.1.1
> no bgp fast-external-fallover
> bgp log-neighbor-changes
> bgp scan-time 15
> network 191.10.1.0 mask 255.255.255.0
> network 191.10.2.0 mask 255.255.255.0
> network 191.10.3.0 mask 255.255.255.0
> network 191.10.4.0 mask 255.255.255.0
> network 191.10.5.0 mask 255.255.255.0
> aggregate-address 191.10.0.0 255.255.252.0
> summary-only
> neighbor 136.10.2.2 remote-as 200
> neighbor 136.10.2.2 ebgp-multihop 255
> neighbor 136.10.2.2 update-source Loopback0
> neighbor 136.10.2.2 send-community
> neighbor 136.10.2.2 route-map setcomlocal out
>
> r1-3620#sh route-map
> route-map setcomlocal, permit, sequence 10
> Match clauses:
> ip address (access-lists): 4
> Set clauses:
> community local-AS
>
> r1-3620#sh access-lists 4
> Standard IP access list 4
> 10 permit 191.10.1.0, wildcard bits 0.0.0.255
> (22
> matches)
> 20 permit 191.10.2.0, wildcard bits 0.0.0.255
> (22
> matches)
> 30 permit 191.10.3.0, wildcard bits 0.0.0.255
> (22
> matches)
> 40 permit 191.10.4.0, wildcard bits 0.0.0.255
> (18
> matches)
> 50 permit 191.10.5.0, wildcard bits 0.0.0.255
> (18
> matches)
> r1-3620#
> ------------------------------------------------
> debug ip bgp neig 136.10.1.1 update
>
> 2-2611xm#
> 3w2d: BGP(0): 136.10.1.1 rcv UPDATE about
> 191.10.1.0/24 -- withdrawn
> 3w2d: BGP(0): 136.10.1.1 rcv UPDATE about
> 191.10.2.0/24 -- withdrawn
> 3w2d: BGP(0): 136.10.1.1 rcv UPDATE about
> 191.10.3.0/24 -- withdrawn
> 3w2d: BGP(0): 136.10.1.1 computing updates, afi 0,
> neighbor version 69, table ve
> rsion 72, starting at 0.0.0.0
> 3w2d: BGP(0): 136.10.1.1 update run completed, afi
> 0,
> ran for 0ms, neighbor vers
> ion 69, start version 72, throttled to 72
>
> -------------------------------------------------
> r2 config
>
> r2-2611xm#sh run | beg bgp
> router bgp 65251
> no synchronization
> bgp router-id 136.10.2.2
> bgp log-neighbor-changes
> bgp confederation identifier 200
> neighbor 136.10.1.1 remote-as 100
> neighbor 136.10.1.1 ebgp-multihop 255
> neighbor 136.10.1.1 update-source Loopback0
> no auto-summary
> !
> ------------------------------------
> Missing the aggregated routes.
>
> r2-2611xm#sh ip bgp | in 191
> *> 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
>
> David
>
> __________________________________
> Do you Yahoo!?
> Yahoo! SiteBuilder - Free web site building tool.
> Try it!
> http://webhosting.yahoo.com/ps/sb/
>
>
This archive was generated by hypermail 2.1.4 : Mon Feb 02 2004 - 09:07:50 GMT-3