From: E Toohs (mr_fantasy_1978@yahoo.com)
Date: Thu Mar 20 2008 - 21:59:00 ART
Thanks Daniel for the reply. I got it to work...I have to kick myself for this one. I did find the following lines in my config, I was testing community delete and didn't realize they were there
ip community-list 102 permit 0:577
!
route-map COMMIN permit 5
set comm-list 102 delete
!
I still think community 0:566 would pass the list and get checked by permit 10...but I guess it doesn't.I put these statements back in and sure enough it prevents statement 10 from getting executed....then I realize I have no match on statement 5 and so it matches ALL!. grrrr, sorry for the bother!
Next time I will post entire config and not "clean it up" or at least be careful when doing so :)
Daniel Valle <danielfrvalle@gmail.com> wrote: I did a small lab for it and it worked jus fine with and without the send-community on both ends... As long you receive the community you don't need it configured in the receiving end to treat the communities from the remote-end. I posted the same example you send us... It worked just fine for me.
!
router bgp 254
no synchronization
bgp router-id 1.1.1.254
bgp log-neighbor-changes
bgp dampening
neighbor 1.1.1.6 remote-as 3
neighbor 1.1.1.6 route-map FROM-R6 in
no auto-summary
!
ip bgp-community new-format
ip community-list 101 permit .*:5..
!
!
route-map FROM-R6 permit 10
match community 101
set local-preference 555
!
route-map FROM-R6 permit 20
!
end
!
BB#sh ip bgp 200.200.200.200
BGP routing table entry for 200.200.200.200/32, version 6
Paths: (1 available, best #1, table Default-IP-Routing-Table)
Not advertised to any peer
3
1.1.1.6 from 1.1.1.6 (1.1.6.6)
Origin IGP, metric 0, localpref 555, valid, external, best
Community: 0:566
On 3/18/08, Daniel Valle <danielfrvalle@gmail.com> wrote: I didn't have time to check carefully, But I would do two tests. 1st. remove "route-map COMMIN permit 20"... after that your routes should still be there... if it's not, something is wrong with your configs. 2nd (not so sure about this one) set the send-community also in the neighbor command.. I know it's strange, but I never saw before community filtering without the sendd-community on both ends.
I'll lab this up and I'll let you know,
Daniel
On 3/15/08, E Toohs <mr_fantasy_1978@yahoo.com> wrote: WHY ISNT THE LOCAL PREFERENCE BEING SET ON THESE ROUTES?
5.6.6.6 has community 0:566 coming in
5.7.7.7 has community 0:577 coming in
community list 101 matches on .*:5..
show ip bgp community-list 101 confirms this
however route-map COMMIN does not seem to apply the LOCAL-PREF
router bgp 64600
bgp log-neighbor-changes
bgp dampening
network 172.12.35.0
neighbor 172.12.36.3 remote-as 65300
neighbor 172.12.36.3 route-map COMMIN in
neighbor 172.12.36.3 maximum-prefix 8 50 warning-only
!
ip bgp-community new-format
ip community-list 101 permit .*:5..
!
route-map COMMIN permit 10
match community 101
set local-preference 500
!
route-map COMMIN permit 20
!
R6#show ip bgp community-list 101
BGP table version is 28, local router ID is 172.12.36.6
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
*> 5.6.6.6/32 172.12.36.3 0 65300 65500 i
*> 5.7.7.7/32 172.12.36.3 0 65300 65500 i
R6#show ip bgp 5.6.6.6
BGP routing table entry for 5.6.6.6/32, version 6
Paths: (1 available, best #1, table Default-IP-Routing-Table)
Not advertised to any peer
65300 65500
172.12.36.3 from 172.12.36.3 (3.3.3.3)
Origin IGP, localpref 100, valid, external, best
Community: 0:566
R6#show ip bgp 5.7.7.7
BGP routing table entry for 5.7.7.7/32, version 7
Paths: (1 available, best #1, table Default-IP-Routing-Table)
Not advertised to any peer
65300 65500
172.12.36.3 from 172.12.36.3 (3.3.3.3)
Origin IGP, localpref 100, valid, external, best
Community: 0:577
The communities in routes 5.6.6.6 and 5.7.7.7 match list 101, but the Local Pref is not set? Anybody see why?
Thanks,
E
---------------------------------
Looking for last minute shopping deals? Find them fast with Yahoo! Search.
This archive was generated by hypermail 2.1.4 : Tue Apr 01 2008 - 07:53:54 ART