From: Narayan Gawas (ngawas@cisco.com)
Date: Tue Mar 23 2004 - 02:04:38 GMT-3
Thanks .
I think this command work on 3725 series router with 12.2
Regards
Narayan
  ------------------------------------------
  NARAYAN GAWAS
  Cisco Technical Assistance Center(CiscoTAC)
   ngawas@cisco.com
-------------------------------------------
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
christopher snow
Sent: Tuesday, March 23, 2004 10:56 AM
To: alsontra@hotmail.com
Cc: ccielab@groupstudy.com
Subject: Re: Bgp summary
I got is working on a MC3810 "flash:mc3810-a2jk8sv5-mz.122-15.t7.bin" 
Make sure you match the route source of the router advertsing the aggregate
in the route-map or it wont work (see bold below). I didnt do that at first
and it didnt work. 
 
***  I am going R1 to R4 to R5, original diagram was R1 to R2 to R6
********
 
router bgp 400 
no synchronization 
bgp log-neighbor-changes 
bgp inject-map INJECT exist-map EXIST 
neighbor 10.10.10.6 remote-as 100 
neighbor 172.16.45.5 remote-as 500 
neighbor 172.16.45.5 route-map R5 out 
! 
ip prefix-list 5 seq 5 permit 192.168.0.0/24 
! 
ip prefix-list EXIST seq 5 permit 192.168.0.0/16 
! 
ip prefix-list INJECT seq 5 permit 192.168.0.0/24 
! 
ip prefix-list SOURCE seq 5 permit 10.10.10.6/32 
! 
route-map INJECT permit 10 
set ip address prefix-list INJECT 
! 
route-map EXIST permit 10 
match ip address prefix-list EXIST 
match ip route-source prefix-list SOURCE 
! 
route-map R5 permit 10 
match ip address prefix-list 5 
set origin igp 
Here is the desination router 
R5#show ip bgp 
BGP table version is 26, local router ID is 150.1.5.5 
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 
*> 192.168.0.0 172.16.45.4 0 400 i 
Chris Snow 
--- alsontra@hotmail.com wrote: 
> It did not work for me either. After doing a tiny
> bit of research, I 
> concluded it was not supported 
> 
> <snip>
> The BGP Conditional Route Injection feature is 
> supported by all platforms in 
> Cisco IOS Release 12.2(14)S that support BGP: 
> 
> a.. Cisco 7200 series
> b.. Cisco 7400 series 
> c.. Cisco 7500 series 
> </snip> 
> 
> http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122new
> ft/122t/122t4/ftbgpri.htm
> 
> Alsontra-
> 
> ----- Original Message -----
> From: "SANCHEZ-MONGE,ANTONIO (HP-France,ex2)" 
> <antonio.sanchez-monge@hp.com> 
> To: "'Brian McGahan'" 
> <bmcgahan@internetworkexpert.com>; 
> <ccielab@groupstudy.com> 
> Sent: Monday, March 22, 2004 2:39 PM 
> Subject: RE: Bgp summary 
> 
> 
> > Hi Brian,
> > 
> > I have tried bgp inject-map functionality as per
> one of your labs and did
> > not succeed to get it working. I used the same
> config as in the solutions
> > guide. I have read previous posts in this list
> saying it is not supported
> in 
> > middle-low range routers. Mmm...
> > 
> > Cheers,
> > Ato. 
> > 
> > -----Original Message-----
> > From: nobody@groupstudy.com 
> [mailto:nobody@groupstudy.com] On Behalf Of
> > Brian McGahan
> > Sent: lunes, 22 de marzo de 2004 23:00 
> > To: 'Narayan Gawas'; 'Packet Man'; 
> EMoffat@fsci.com;
> ccielab@groupstudy.com 
> > Subject: RE: Bgp summary
> > 
> > 
> > The only way that 192.68.0.0 will show up as "*>
> 192.68.0.0" in the
> > BGP table is if the network is 192.68.0.0/24. The
> mask does not show up
> in 
> > the "show ip bgp" output if it is classful.
> Otherwise the mask is
> included. 
> > Therefore there are two possible ways to interpret
> this scenario:
> > 
> > 1. You are missing some key piece of the puzzle,
> and the question is not
> > asking for "*> 192.68.0.0" in the BGP table
> > 
> > Or
> > 
> > 2. 192.68.0.0/24 must be injected into the BGP
> table
> > 
> > FYI there *is* a way to inject 192.68.0.0/24
> without using:
> > 
> > 1. the network statement
> > 2. the aggregate-address statement 
> > 3. redistribution 
> > 
> > Any takers? :)
> > 
> > 
> > HTH,
> > 
> > Brian McGahan, CCIE #8593
> > bmcgahan@internetworkexpert.com 
> > 
> > Internetwork Expert, Inc.
> > http://www.InternetworkExpert.com 
> > Toll Free: 877-224-8987 x 705 
> > Outside US: 775-826-4344 x 705 
> > 
> > 
> > > -----Original Message-----
> > > From: nobody@groupstudy.com 
> [mailto:nobody@groupstudy.com] On Behalf
> > > Of Narayan Gawas
> > > Sent: Monday, March 22, 2004 10:22 AM 
> > > To: 'Packet Man'; EMoffat@fsci.com; 
> ccielab@groupstudy.com
> > > Subject: RE: Bgp summary
> > > 
> > > I am sorry ,my question was not that clear
> > > 
> > > r1-->r2.----R6
> > > r1 send following route to R2
> > > 
> > > 197.68.1.0/24,
> > > 197.68.2.0/24 
> > > 197.68.3.0/24 
> > > 197.68.0.0/19 
> > > 
> > > In R2,after summarization, In BGP table we get
> following routes
> > > 
> > > *> 192.68.0.0/16
> > > *> 192.68.1.0 
> > > *> 192.68.2.0 
> > > 
> > > Goal :
> > > Only 197.68.0.0 should be appear in Bgp table of 
> R6--without /16 We
> > > cannot use summary command,suppres route map at
> R2
> > > 
> > > i did following but it only work if we summarize
> route to /24 in r2
> > > bgp table But doest work if we summarize 197.68
> into /16.
> > > 
> > > ip prefix-list R3-OUT seq 5 permit 197.68.0.0/24
> le 25
> > > Router bgp 1
> > > Agg-add 197.68.0.0 255.255.255.0 
> > > neighbor 135.4.6.6 prefix-list R3-OUT out 
> > > 
> > > ------------------------------------------
> > > 
> > > NARAYAN GAWAS
> > > Cisco Technical Assistance Center(CiscoTAC) 
> > > ngawas@cisco.com 
> > > ------------------------------------------- 
> > > 
> > > -----Original Message-----
> > > From: Packet Man [mailto:ccie2b@hotmail.com] 
> > > Sent: Monday, March 22, 2004 12:04 PM 
> > > To: ngawas@cisco.com; EMoffat@fsci.com; 
> ccielab@groupstudy.com
> > > Subject: RE: Bgp summary
> > > 
> > > 
> > > Assuming you have "no auto sum" under your
> router bgp config, what
> > > would happen if auto-sum were enabled? Would
> that do the trick?
> > > 
> > > 
> > > >From: "Narayan Gawas" <ngawas@cisco.com>
> > > >Reply-To: "Narayan Gawas" <ngawas@cisco.com> 
> > > >To: "'Moffat, Ed'" <EMoffat@fsci.com>, 
> <ccielab@groupstudy.com>
> > > >Subject: RE: Bgp summary
> > > >Date: Mon, 22 Mar 2004 09:41:39 +0900 
> > > > 
> > > >----------------------------------------- (on
> firestar)
> > > > 
> > > >Tacsuns has scanned the file email-body and no
> virus was found.
> > > 
> >---------------------------------------------------------
> > > >That means to summarise these route ,I have to
> create loopback with
> > > >192.168.0.0 net ,mask 255.255.255.0 and
> advertise loopback net into
> > > >Bgp ? Am I right ?
> > > > 
> > > > 
> > > > ------------------------------------------
> > > > NARAYAN GAWAS 
> > > > Cisco Technical Assistance Center(CiscoTAC) 
> > > > ngawas@cisco.com 
> > > >------------------------------------------- 
> > > > 
> > > >-----Original Message-----
> > > >From: Moffat, Ed [mailto:EMoffat@fsci.com] 
> > > >Sent: Monday, March 22, 2004 9:33 AM 
> > > >To: 'Narayan Gawas'; 'ccielab@groupstudy.com' 
> > > >Subject: RE: Bgp summary 
> > > > 
> > > > 
> > > >I believe that the only way you will not see
> the /16 is if the
> > > >192.168.0.0 address is actually at /24 address
> that is announced.
> > > > 
> > > >-Ed-
> > > > 
> > > >-----Original Message-----
> > > >From: Narayan Gawas [mailto:ngawas@cisco.com] 
> 
=== message truncated === 
Do you Yahoo!?
Yahoo! Finance Tax Center - File online. File on time.
This archive was generated by hypermail 2.1.4 : Thu Apr 01 2004 - 08:15:44 GMT-3