Static route target filtering

Route target extended communities (see RFC 4360, BGP Extended Communities Attribute) prevent networks from receiving information about VPNs that is not relevant. For example, a network that does not include any PE routers that are a part of a VPN does not need to receive any network updates related to that VPN. The route target extended community feature has been extended to allow you to add static entries to the bgp.rtarget.0 routing table. This can be particularly useful for VPN hub-and-spoke topologies. Specify the target community for static route target filtering using the route-target-filter statement at the [edit routing-options rib bgp.rtarget.0 static] hierarchy level.