Re: BGP summary

From: John Underhill (stepnwlf@magma.ca)
Date: Wed Jan 08 2003 - 22:21:07 GMT-3


Why not use community to stop the specific updates at the first hop? You
could use aggregate address then match with a prefix list, or create the
route to null0, advertise as network statement, match with prefix list, then
use community to control updates out of the neighbors AS.. like so...

router bgp 100
 no synchronization
 network 10.1.1.0 mask 255.255.255.0
 network 10.1.2.0 mask 255.255.255.0
 network 10.1.3.0 mask 255.255.255.0
 aggregate-address 10.1.0.0 255.255.252.0
 neighbor 150.50.17.2 remote-as 200
 neighbor 150.50.17.2 send-community
 neighbor 150.50.17.2 route-map COMMUNITY out
 no auto-summary

ip prefix-list LIST1 seq 5 permit 10.1.0.0/22
route-map COMMUNITY permit 10
 match ip address prefix-list LIST1
 set community none
!
route-map COMMUNITY permit 20
 set community no-export

r2#sh ip bgp
BGP table version is 21, local router ID is 150.50.17.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
*> 10.1.0.0/22 150.50.17.1 0 100 i
*> 10.1.1.0/24 150.50.17.1 0 0 100 i
*> 10.1.2.0/24 150.50.17.1 0 0 100 i
*> 10.1.3.0/24 150.50.17.1 0 0 100 i

r7#sh ip bgp
BGP table version is 8, local router ID is 192.168.7.7
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
*> 10.1.0.0/22 150.50.17.1 0 200 100 i

----- Original Message -----
From: "Aidan Marks" <amarks@cisco.com>
To: "Mahmud, Yasser" <YMahmud@Solutions.UK.ATT.com>
Cc: "'Evgeny Tantsura'" <ivgen@castel.nl>; <ccielab@groupstudy.com>
Sent: Wednesday, January 08, 2003 2:44 PM
Subject: RE: BGP summary

> maybe "auto-summary" ?
>
> At 06:14 AM 9/01/2003, Mahmud, Yasser wrote:
>
> >If I've interpreted it correctly
> >
> >On R3 use the aggregate address command
> >aggregate-address 122.160.0.0 255.224.0.0
> >
> >as not allowed to use the summary-only keyword, and can't supress any
routes
> >
> >so would use route-maps on neighbor routers.
> >
> > < route-map in >on R1 &R2 and filter the specifics using extended
> >access-list to avoid using all the specifics indiviually
> >
> >access-list 101 deny ip 192.160.0.0 0.31.255.255 host 255.255.255.0
> >access-list 101 permit ip any any
> >
> >on r4 in filter the summary coming back in.
> >
> >Yasser
> >
> > > -----Original Message-----
> > > From: Evgeny Tantsura [SMTP:ivgen@castel.nl]
> > > Sent: Wednesday, January 08, 2003 2:11 PM
> > > To: ccielab@groupstudy.com
> > > Subject: BGP summary
> > >
> > > AS1 | AS 2
> > > R1-----\ |
> > > R2-----R3|-----R4 BGP - 122.168.1.0 - 122.157.10.0
> > > |
> > > |
> > >
> > > R3 receives 10 /24 networs from R4
> > >
> > > R1 and R2 should receive only 1 summary route, not /16
> > > Summary word can't be used.
> > >
> > > Routes on R3 can't be suppressed.
> > >
> > >
> > > With kind regards/ met vriendelijke groeten,
> > > ------------------------------------------------
> > > E. Tantsura
> > > Network Developer
> > > Essent Kabelcom N.V.
> > > Dr.van Deenweg 84
> > > 8025BN Zwolle, The Netherlands
> > > Tel: +31-(0)38-850-7642
> > > Fax: +31-(0)38-850-7410
> > > Mob: +31-(0)6-290-80458
> > > ------------------------------------------------
> >.
> .
.



This archive was generated by hypermail 2.1.4 : Sat Feb 01 2003 - 07:33:45 GMT-3