Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Configuring Static Route Target Filtering for VPNs

The BGP VPN route target extended community (RFC 4360, BGP Extended Communities Attribute) is used to determine VPN membership. Static route target filtering helps to prevent resources from being consumed in portions of the network where the VPN routes are not needed due to the lack of member PE routers (RFC 4684, Constrained Route Distribution for Border Gateway Protocol/MultiProtocol Label Switching (BGP/MPLS) Internet Protocol (IP) Virtual Private Networks (VPNs)). Routers can originate routes into the RT-Constrain protocol to indicate their interest in receiving VPN routes containing route targets that match the RT-Constrain NLRI.

To configure static route target filtering for VPNs:

  • Configure the route-target-filter statement at the [edit routing-options rib bgp.rtarget.0 static] hierarchy level.

    The following example illustrates how you could configure the route-target-filter statement:

  • You can display route target filtering information using the show bgp group rtf detail command.