From: Igor Manassypov (imanassypov@rogers.com)
Date: Thu Aug 14 2008 - 12:19:12 ART
Hey Steve,
I agree with you, good thing we sorted it out.
I am with CI Investments...
support@ccie.com.au wrote:
Correct, in other words you can not tag/set/advertize a route in BGP unless it exsists in BGP routing table first, so, "sh ip rote bgp" what ever is in there you may modify and do what ever you wish and it will work , however in your case when using bgp advertise-map, there are two things you can do. 1. if condition in "exsist-map" is met then "default-originate and set community tag" else no default-route, meaning no default route in your "sh ip bgp" command...
are you a engineer at peopletelecom...? i used to work there years ago when it was SWIFTTEL, didnt have any MPLS backbone back then ..:)
Steve K
www.ccie.com.au
------- Original Message ------- On 8/14/2008 2:26 PM Igor Manassypov wrote:
Your condition is not really a condition - it will originate a default no matter what. idea was that in that CONDITION route-map you watch for a specific route present in routing tabl e, and only then do you originate the 0/0.
It wont work if you set the community in the 'neighbor x.x.x.x route-map SETCOMM out' scenario because apparently the SETCOMM happens before the default is originated, thus default route is not getting labelled
Arunas Baltrunas wrote: i have tried this in my lab and it works:
#R5
router bgp 200
bgp router-id 20.1.5.5
no bgp default ipv4-unicast
bgp log-neighbor-changes
neighbor 20.1.1.1 remote-as 200
neighbor 20.1.1.1 update-source Loopback0
!
address-family ipv4
neighbor 20.1.1.1 activate
neighbor 20.1.1.1 send-community
neighbor 20.1.1.1 default-originate route-map SET-COM
exit-address-family
!
route-map SET-COM permit 10
set community 1111:1111
!
on R1
R1#sho ip bgp 0.0.0.0
BGP routing table entry for 0.0.0.0/0, version 27
Paths: (1 available, best #1, table Default-IP-Routing-Table)
Advertised to update-groups:
1 2
Local, (Received from a RR-client)
20.1.5.5 (metric 66) from 20.1.5.5 (20.1.5.5)
Origin IGP, metric 0, localpref 100, valid, internal, best
Community: 1111:1111
i confirm that neighbor route map does nothing to defaul route originate
On 8/14/08, Igor Manassypov wrote: Hey Huan,
- I agree with you, although it is somewhat counter-intuitive. By the looks of it, 'route-map' out happens before the default origination...
Would be great if someone shared any ideas,
Thanks
Huan Pham wrote:
It looks like that the default route originated conditionally is subject
to the CONDITION route-map only. It does not go through the route-map
SET-COMMUNITY.
You can use set community (or whatever other set statements) under the
route-map CONDITION to change the attributes for the default route.
I cannot find the info in Cisco DOC about the BGP behavior in this case.
Would be great if someone can shed some more light.
Cheers,
Huan
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Igor Manassypov
Sent: Thursday, 14 August 2008 5:55 AM
To: ccielab@groupstudy.com
Subject: setting community on originated default routes
Hello,
I am trying to set a community on all routes originated in my as,
including a default which I am conditionally pushing out. However, the
conditionally-originated default never gets any community tag... a
portion of my community-setting router is below. Any suggestions why the
originated default does not get the community setting?
router bgp ccc
neighbor 1.2.3.4 send-community
neighbor 1.2.3.4 default-originate route-map CONDITION
neighbor 1.2.3.4 route-map SET-COMMUNITY out
route-map SET-COMMUNITY permit 10
set community 1111:11
Blogs and organic groups at http://www.ccie.net
This archive was generated by hypermail 2.1.4 : Mon Sep 01 2008 - 08:15:30 ART