The MPLS-OPS Archive

Cell Relay Retreat>MPLS-OPS Archive>month:2006-Dec> msg00026



[Date Prev][Date Next][Thread Prev][Thread Next]  
  [Date Index][Thread Index][Author Index][Subject Index]

Re: Tagging of BGP extended community

  • From: Truman Boyes <truman@suspicious.org>
  • Date: Wed, 6 Dec 2006 08:42:39 +1300
  • Cc: mpls-ops@mplsrc.com, mpls@lists.ietf.org
  • Resent-Date: Tue, 5 Dec 2006 15:41:08 -0500
  • X-Scanned-By: MIMEDefang 2.53 on 209.239.41.31
  • X-Security: MIME headers sanitized on host.secure4-hosting.netSee http://www.impsec.org/email-tools/sanitizer-intro.htmlfor details. $Revision: 1.138 $Date: 2003-01-26 11:25:54-08
  • X-SpamProbe: GOOD 0.0000000 ca16b18edc4af6af905f19b83b6b6205

Hello,

The tagging of MBGP extended communities for VPNv4 routes is controlled within the BGP task by policy. Keep in mind that prefixes may have single extended communities for VPNs, or additive policy may allow multiple communities to be associated with the prefix. All of this policy is completely interface agnostic. For example, an operator may wish to export (redistribute) a set of static routes with multiple extended communities. 

Each extended community may be associated with a different VPN, thus allowing the exported route to be received and installed in the different VRFs.

Say for example that prefix 10.10.10/24 has the following communities: 'target:65009:100' and 'target:65009:200'. Assuming there are two VRFs configured (RED and BLUE), and RED is importing all prefixes with extended community 'target:65009:100' and BLUE is importing 'target:65009:200'. 

The 10.10.10/24 prefix would be imported into both BLUE and RED VRFs.

You might want to read the following:



Cheers,
Truman



On 6/12/2006, at 2:28 AM, Mohammed Shahnawaz wrote:

-->

 

Hi,

 

Can someone explain how routers support tagging of multiple BGP extended communities for VPN4 routes using a single interface between PE and CE.  Please provide some documents as well, if possible.

 

 

Thanks & Regards,

 

Shahnawaz