Standard communities can be used and will propogate across the cloud providing both customer and provider use the neighbor x.x.x.x send-community command. Extended communities are trickier, and are generally blocked ime for security reasons (customers could potentially send alternative route-targets, so nei x.x.x.x send-community standard is used, send-community both or extended are not.
In addition to customer defined and used community values, some providers have predefined communities used in their cloud that the PE's will match and act on, usually setting local preference, etc. This behavior is a nice tool to have available when implemented uniformly by multiple upstream providers. Most follow bgp community new-format, e.g. ASN:COMMUNITY. ASN:90 usually sets LP to 90, ASN:110 sets LP to 110. John -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of danger will Sent: Sunday, February 27, 2011 9:34 AM To: [email protected] Subject: [c-nsp] bgp communities over vpn mpls Hello List, Lets say the customer wants to use his own bgp communities over a vpn mpls service. Prefixes from one site are market with some communities , and those communities have an action at another site. The question is are these communities maintained over the vpn mpls service or is there any reason for them to be deleted by the mpls provider ? Thank you very much _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
