On 5/19/2011 3:53 AM, Phil Mayers wrote: > On 05/18/2011 07:01 PM, Jeff Kell wrote: >> If you have VRF-enabled a router (well, a 6500), does this affect BGP >> community >> processing at all? (Suspecting community overlap with VRF route >> distinguishers?) >> >> Trying to get a new BGP peer up that has VRF-enabled, but BGP running in >> global, and a >> matching community / route-map configuration in the legacy side (no VRFs) >> doesn't appear >> to be working on the VRF-enabled one. > > We use as:xx-style communities on BGP peerings inside MPLS VPNs with no > issues.
Odd. I managed to get it to work, just not as expected. Legacy (no VRF enabled, 12.2(18)SXF17) "ip community-list 10 permit 65532:888 no-export" is accepted, but on VRF-enabled 12.2(33)SXI3 becomes "permit 4281598840 no-export". An "ip community-list 100 permit 65532:888" stays in that format, but matching on an incoming route-map doesn't match 100, it matches 10. And yes, it's the cymru bogon feed, if that community looks familiar :) Jeff _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
