Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

TechLibrary
Navigation

Example: Configuring Proxy BGP Route Target Filtering

Understanding Proxy BGP Route Target Filtering

BGP route target filtering (also known as route target constrain, or RTC) allows you to distribute VPN routes to only the devices that need them. In VPN networks without BGP route target filtering configured, BGP distributes all VPN routes to all VPN peer devices, which can strain network resources. The route target filtering feature was introduced to reduce the number of devices receiving VPN routes and VPN routing updates, thereby limiting the amount of overhead associated with running a VPN. The Junos OS implementation for BGP route target filtering is based on RFC 4684, Constrained Route Distribution for Border Gateway Protocol/MultiProtocol Label Switching (BGP/MPLS) Internet Protocol (IP) Virtual Private Networks (VPNs).

What if you have a network environment where route target filtering is not widely deployed, or what if some devices do not support route target filtering? For example, you might have a BGP speaker with route target filtering enabled that is peered with a BGP speaker that does not support or have route target filtering configured. In this case, the BGP speaker with route target filtering configured must advertise default route target membership (RT membership) on behalf of its peer. The route target filtering resource savings are unrealized because the device supporting the filtering must now send all VPN routes to the device that does not support the filter. Proxy BGP route target filtering (or Proxy RTC) permits the generation of RT membership for devices that do not support route target filtering. This eases the deployment of route target filtering in networks where it is incompletely deployed or not fully supported.

Proxy BGP route target filtering allows you to distribute proxy RT membership advertisements created from the received BGP VPN routes to other devices in the network that need them. These are known as proxy advertisements because the device creates the RT membership on behalf of its peers without the route target filtering functionality. Proxy BGP route target filtering uses BGP route target extended communities that are exported to a specific BGP speaker to generate the route targets. Generated proxy RTC routes are stored in the bgp.rtarget.0 routing table.

You can also configure a policy to control which VPN routes are used to generate the proxy RTC routes. This can help control which RT membership is generated by the proxying device. In addition, you can configure a policy to reduce the memory overhead associated with proxy RTC. Proxy RTC only uses additional memory on a per-VPN route basis when it is permitted by a policy to be used for generating RT membership.

Example: Configuring Proxy BGP Route Target Filtering

This example shows how to configure proxy BGP route target filtering (also known as proxy route target constrain, or proxy RTC).

Requirements

This example uses the following hardware and software components:

  • Four Juniper Networks devices that can be a combination of M Series, MX Series, or T Series routers.
  • Junos OS Release 12.2 or later on one or more devices configured for proxy BGP route filtering. In this example, you explicitly configure proxy BGP route filtering on the route reflectors.

Before configuring proxy BGP route target filtering, make sure that you are familiar with and understand the following concepts:

Overview

Route target filtering decreases the number of devices in a network that receive VPN routes that are not needed. Proxy BGP route target filtering allows networks to take advantage of route target filtering in locations where the feature is not currently supported. By configuring this feature, you can realize many of the same network resource savings that are available to you if your network fully supported BGP route target filtering.

To configure proxy BGP route target filtering, you include the family route-target proxy-generate statement on the devices that will distribute proxy route target membership (RT membership) advertisements for the devices that do not support BGP route target filtering. The proxy BGP route target filtering routes are then stored in the bgp.rtarget.0 routing table.

Proxy BGP route target filtering is intended to create RT membership advertisements for devices that do not support the BGP route target filtering feature. If the proxy-generate statement is present, but the route target family is negotiated with the BGP peer, the proxy-generate functionality is disabled. This allows simplified configuration of BGP peer groups where a portion of the peers in the group support route target filtering but others do not. In such an example case, the family route-target proxy-generate statement might be part of the BGP peer group configuration.

Note: When deploying proxy BGP route target filtering in your network, the advertise-default statement for BGP route target filtering causes the device to advertise the default route target route (0:0:0/0) and suppress all routes that are more specific. If you have proxy BGP route target filtering configured on one device and one or more peers have the advertise-default statement configured as part of their BGP route target filtering configuration, the advertise-default configuration is ignored.

Topology Diagram

Figure 1 shows the topology used in this example.

Figure 1: Proxy BGP Route Target Filtering Topology

Proxy BGP Route Target Filtering Topology

In this example, BGP route target filtering is configured on the route reflectors (Device RR1 and Device RR2) and the provider edge (PE) Device PE2, but the other PE, Device PE1, does not support the BGP route target filtering functionality. Device PE2 has four VPNs configured (vpn1, vpn2, vpn3, and vpn4). Device PE1 has two VPNs configured (vpn1 and vpn2), so this device is only interested in receiving route updates for vpn1 and vpn2. Currently, this is impossible because both route reflectors (Device RR1 and Device RR2) learn and share information about all of the incoming VPN routes (vpn1 through vpn4) with Device PE1. In the sample topology, all devices participate in autonomous system (AS) 200, OSPF is the configured interior gateway protocol (IGP), and LDP is the signaling protocol used by the VPNs. In this example, we use static routes in the VPN routing and forwarding (VRF) instances to generate VPN routes. This is done in place of using a PE to customer edge (CE) protocol such as OSPF or BGP.

To minimize the number of VPN route updates being processed by Device PE1, you include the family route-target proxy-generate statement to configure proxy BGP route target filtering on each route reflector. Each route reflector has a peering session with Device PE1 and supports route target filtering to the core. However, Device PE1 does not support route target filtering, so the network resource savings are unrealized by Device PE1 since it receives all of the VPN updates. By configuring proxy BGP route target filtering on the peering sessions facing Device PE1, you limit the number of VPN updates processed by Device PE1, and the route reflectors generate the proxy BGP route target routes for Device PE1 throughout the network.

Configuration

CLI Quick Configuration

To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your network configuration, and then copy and paste the commands into the CLI at the [edit] hierarchy level.

Device PE1

set interfaces ge-1/0/0 unit 0 description PE1-to-RR1set interfaces ge-1/0/0 unit 0 family inet address 10.49.0.1/30set interfaces ge-1/0/0 unit 0 family mplsset interfaces ge-1/0/1 unit 0 description PE1-to-RR2set interfaces ge-1/0/1 unit 0 family inet address 10.49.10.1/30set interfaces ge-1/0/1 unit 0 family mpls set protocols ldp interface ge-1/0/0set protocols ldp interface ge-1/0/1set protocols bgp group internal type internal set protocols bgp group internal local-address 10.255.163.58 set protocols bgp group internal neighbor 10.255.165.220 family inet-vpn unicastset protocols bgp group internal neighbor 10.255.165.28 family inet-vpn unicast set protocols ospf area 0.0.0.0 interface ge-1/0/0set protocols ospf area 0.0.0.0 interface ge-1/0/1set protocols ospf area 0.0.0.0 interface lo0.0 passiveset routing-options route-distinguisher-id 10.255.163.58set routing-options autonomous-system 200set routing-instances vpn1 instance-type vrfset routing-instances vpn1 vrf-target target:200:100set routing-instances vpn1 routing-options static route 223.1.1.2/32 discardset routing-instances vpn2 instance-type vrfset routing-instances vpn2 vrf-target target:200:101set routing-instances vpn2 routing-options static route 223.2.2.2/32 discard

Device RR1

set interfaces ge-1/0/0 unit 0 description RR1-to-PE1set interfaces ge-1/0/0 unit 0 family inet address 10.49.0.2/30set interfaces ge-1/0/0 unit 0 family mpls set interfaces ge-1/0/1 unit 0 description RR1-to-PE2set interfaces ge-1/0/1 unit 0 family inet address 10.50.0.2/30set interfaces ge-1/0/1 unit 0 family mpls set protocols ldp interface ge-1/0/0set protocols ldp interface ge-1/0/1set protocols bgp group internal type internalset protocols bgp group internal local-address 110.255.165.220set protocols bgp group internal cluster 1.1.1.1set protocols bgp group internal neighbor 10.255.163.58 description vpn1-to-pe1 family inet-vpn unicastset protocols bgp group internal neighbor 10.255.163.58 family route-target proxy-generateset protocols bgp group internal neighbor 10.255.168.42 description vpn1-to-pe2 family inet-vpn unicastset protocols bgp group internal neighbor 10.255.168.42 family route-targetset protocols ospf area 0.0.0.0 interface ge-1/0/0set protocols ospf area 0.0.0.0 interface ge-1/0/1set protocols ospf area 0.0.0.0 interface lo0.0 passiveset routing-options route-distinguisher-id 10.255.165.220set routing-options autonomous-system 200

Device RR2

set interfaces ge-1/0/0 unit 0 description RR2-to-PE1set interfaces ge-1/0/0 unit 0 family inet address 10.49.10.2/30set interfaces ge-1/0/0 unit 0 family mpls set interfaces ge-1/0/1 unit 0 description RR2-to-PE2set interfaces ge-1/0/1 unit 0 family inet address 10.50.10.2/30set interfaces ge-1/0/1 unit 0 family mpls set protocols ldp interface ge-1/0/0set protocols ldp interface ge-1/0/1set protocols bgp group internal type internalset protocols bgp group internal local-address 10.255.165.28set protocols bgp group internal cluster 1.1.1.1set protocols bgp group internal neighbor 10.255.163.58 description vpn2-to-pe1 family inet-vpn unicastset protocols bgp group internal neighbor 10.255.163.58 family route-target proxy-generateset protocols bgp group internal neighbor 10.255.168.42 description vpn2-to-pe2 family inet-vpn unicastset protocols bgp group internal neighbor 10.255.168.42 family route-target set protocols ospf area 0.0.0.0 interface ge-1/0/0set protocols ospf area 0.0.0.0 interface ge-1/0/1set protocols ospf area 0.0.0.0 interface lo0.0 passiveset routing-options route-distinguisher-id 10.255.165.28set routing-options autonomous-system 200

Device PE2

set interfaces ge-1/0/0 unit 0 description PE2-to-RR1set interfaces ge-1/0/0 unit 0 family inet address 10.50.0.1/30set interfaces ge-1/0/0 unit 0 family mplsset interfaces ge-1/0/1 unit 0 description PE2-to-RR2set interfaces ge-1/0/1 unit 0 family inet address 10.50.10.2/30set interfaces ge-1/0/1 unit 0 family mpls set protocols ldp interface ge-1/0/0set protocols ldp interface ge-1/0/1set protocols bgp group internal type internal set protocols bgp group internal local-address 10.255.168.42 set protocols bgp group internal family inet-vpn unicastset protocols bgp group internal family route-targetset protocols bgp group internal neighbor 10.255.165.220set protocols bgp group internal neighbor 10.255.165.28set protocols ospf area 0.0.0.0 interface ge-1/0/0set protocols ospf area 0.0.0.0 interface ge-1/0/1set protocols ospf area 0.0.0.0 interface lo0.0 passiveset routing-options route-distinguisher-id 10.255.168.42set routing-options autonomous-system 200set routing-instances vpn1 instance-type vrfset routing-instances vpn1 vrf-target target:200:100set routing-instances vpn1 routing-options static route 223.1.1.2/32 discardset routing-instances vpn2 instance-type vrfset routing-instances vpn2 vrf-target target:200:101set routing-instances vpn2 routing-options static route 223.2.2.2/32 discardset routing-instances vpn3 instance-type vrfset routing-instances vpn3 vrf-target target:200:103set routing-instances vpn3 routing-options static route 223.3.3.3/32 discardset routing-instances vpn4 instance-type vrfset routing-instances vpn4 vrf-target target:200:104set routing-instances vpn4 routing-options static route 223.4.4.4/32 discard

Configuring Device PE1

Step-by-Step Procedure

The following example requires you to navigate various levels in the configuration hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration Mode in the CLI User Guide.

To configure Device PE1:

  1. Configure the interfaces.
    [edit interfaces]user@PE1# set ge-1/0/0 unit 0 description PE1-to-RR1user@PE1# set ge-1/0/0 unit 0 family inet address 10.49.0.1/30user@PE1# set ge-1/0/0 unit 0 family mplsuser@PE1# set ge-1/0/1 unit 0 description PE1-to-RR2user@PE1# set ge-1/0/1 unit 0 family inet address 10.49.10.1/30user@PE1# set ge-1/0/1 unit 0 family mpls
  2. Configure the route distinguisher and the AS number.
    [edit routing-options]user@PE1# set route-distinguisher-id 10.255.163.58user@PE1# set autonomous-system 200
  3. Configure LDP as the signaling protocol used by the VPN.
    [edit protocols ldp]user@PE1# set interface ge-1/0/0user@PE1# set interface ge-1/0/1
  4. Configure BGP.
    [edit protocols bgp group internal]user@PE1# set type internaluser@PE1# set local-address 10.255.163.58user@PE1# set neighbor 10.255.165.220 family inet-vpn unicastuser@PE1# set neighbor 10.255.165.28 family inet-vpn unicast
  5. Configure OSPF.
    [edit protocols ospf area 0.0.0.0]user@PE1# set interface ge-1/0/0user@PE1# set interface ge-1/0/1user@PE1# set interface lo0.0 passive
  6. Configure the VPN routing instances.
    [edit routing-instances vpn1]user@PE1# set instance-type vrfuser@PE1# set vrf-target target:200:100user@PE1# set routing-options static route 223.1.1.2/32 discard
    [edit routing-instances vpn2]user@PE1# set instance-type vrfuser@PE1# set vrf-target target:200:101user@PE1# set routing-options static route 223.2.2.2/32 discard
  7. If you are done configuring the device, commit the configuration.
    [edit]user@PE1# commit

Results

From configuration mode, confirm your configuration by entering the show interfaces, show protocols, show routing-options, and show routing-instances commands. If the output does not display the intended configuration, repeat the instructions in this example to correct the configuration.

user@PE1# show interfacesge-1/0/0 {unit 0 {description PE1-to-RR1;family inet {address 10.49.0.1/30;}family mpls;}}ge-1/0/1 {unit 0 {description PE1-to-RR2;family inet {address 10.49.10.1/30;}family mpls;}}
user@PE1# show protocolsbgp {group internal {type internal;local-address 10.255.163.58;neighbor 10.255.165.220 {family inet-vpn {unicast;}}neighbor 10.255.165.28 {family inet-vpn {unicast;}}}}ospf {area 0.0.0.0 {interface ge-1/0/0.0;interface ge-1/0/1.0;interface lo0.0 {passive;}}}ldp {interface ge-1/0/0.0;interface ge-1/0/1.0;}
user@PE1# show routing-optionsroute-distinguisher-id 10.255.14.182;autonomous-system 200;
user@PE1# show routing-instancesvpn1 {instance-type vrf;vrf-target target:200:100;routing-options {static {route 223.1.1.2/32 discard;}}}vpn2 {instance-type vrf;vrf-target target:200:101;routing-options {static {route 223.2.2.2/32 discard;}}}

Configuring Device RR1

Step-by-Step Procedure

The following example requires you to navigate various levels in the configuration hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration Mode in the CLI User Guide.

To configure Device RR1:

  1. Configure the interfaces.
    [edit interfaces]user@RR1# set ge-1/0/0 unit 0 description RR1-to-PE1user@RR1# set ge-1/0/0 unit 0 family inet address 10.49.0.2/30user@RR1# set ge-1/0/0 unit 0 family mplsuser@RR1# set ge-1/0/1 unit 0 description RR1-to-PE2user@RR1# set ge-1/0/1 unit 0 family inet address 10.50.0.2/30user@RR1# set ge-1/0/1 unit 0 family mpls
  2. Configure the route distinguisher and the AS number.
    [edit routing-options]user@RR1# set route-distinguisher-id 10.255.165.220user@RR1# set autonomous-system 200
  3. Configure LDP as the signaling protocol used by the VPN.
    [edit protocols ldp]user@RR1# set interface ge-1/0/0user@RR1# set interface ge-1/0/1
  4. Configure BGP.
    [edit protocols bgp group internal]user@RR1# set type internaluser@RR1# set local-address 10.255.165.220user@RR1# set cluster 1.1.1.1user@RR1# set neighbor 10.255.163.58 description vpn1-to-pe1 family inet-vpn unicastuser@RR1# set neighbor 10.255.168.42 description vpn1-to-pe2 family inet-vpn unicast
  5. Configure BGP route target filtering on the peering session with Device PE2.
    [edit protocols bgp group internal]user@RR1# set neighbor 10.255.168.42 family route-target
  6. Configure proxy BGP route target filtering on the peering session with Device PE1.
    [edit protocols bgp group internal]user@RR1# set neighbor 10.255.163.58 family route-target proxy-generate
  7. Configure OSPF.
    [edit protocols ospf area 0.0.0.0]user@RR1# set interface ge-1/0/0user@RR1# set interface ge-1/0/1user@RR1# set interface lo0.0 passive
  8. If you are done configuring the device, commit the configuration.
    [edit]user@RR1# commit

Results

From configuration mode, confirm your configuration by entering the show interfaces, show protocols and show routing-options commands. If the output does not display the intended configuration, repeat the instructions in this example to correct the configuration.

user@RR1# show interfacesge-1/0/0 {unit 0 {description RR1-to-PE1;family inet {address 10.49.0.2/30;}family mpls;}}ge-1/0/1 {unit 0 {description RR1-to-PE2;family inet {address 10.50.0.2/30;}family mpls;}}
user@RR1# show protocolsbgp {group internal {type internal;local-address 110.255.165.220;cluster 1.1.1.1;neighbor 10.255.163.58 {description vpn1-to-pe1;family inet-vpn {unicast;}family route-target {proxy-generate;}}neighbor 10.255.168.42 {description vpn1-to-pe2;family inet-vpn {unicast;}family route-target;}}}ospf {area 0.0.0.0 {interface ge-1/0/0.0;interface ge-1/0/1.0;interface lo0.0 {passive;}}}ldp {interface ge-1/0/0.0;interface ge-1/0/1.0;}
user@RR1# show routing-optionsroute-distinguisher-id 10.255.165.220; autonomous-system 200;

Configuring Device RR2

Step-by-Step Procedure

The following example requires you to navigate various levels in the configuration hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration Mode in the CLI User Guide.

To configure Device RR2:

  1. Configure the interfaces.
    [edit interfaces]user@RR2# set ge-1/0/0 unit 0 description RR2-to-PE1user@RR2# set ge-1/0/0 unit 0 family inet address 10.49.10.2/30user@RR2# set ge-1/0/0 unit 0 family mplsuser@RR2# set ge-1/0/1 unit 0 description RR2-to-PE2user@RR2# set ge-1/0/1 unit 0 family inet address 10.50.10.2/30user@RR2# set ge-1/0/1 unit 0 family mpls
  2. Configure the route distinguisher and the AS number.
    [edit routing-options]user@RR2# set route-distinguisher-id 10.255.165.28user@RR2# set autonomous-system 200
  3. Configure LDP as the signaling protocol used by the VPN.
    [edit protocols ldp]user@RR2# set interface ge-1/0/0user@RR2# set interface ge-1/0/1
  4. Configure BGP.
    [edit protocols bgp group internal]user@RR2# set type internaluser@RR2# set local-address 10.255.165.28user@RR2# set cluster 1.1.1.1user@RR2# set neighbor 10.255.163.58 description vpn2-to-pe1 family inet-vpn unicastuser@RR2# set neighbor 10.255.168.42 description vpn2-to-pe2 family inet-vpn unicast
  5. Configure BGP route target filtering on the peering session with Device PE2.
    [edit protocols bgp group internal]user@RR2# set neighbor 10.255.168.42 family route-target
  6. Configure proxy BGP route target filtering on the peering session with Device PE1.
    [edit protocols bgp group internal]user@RR2# set neighbor 10.255.163.58 family route-target proxy-generate
  7. Configure OSPF.
    [edit protocols ospf area 0.0.0.0]user@RR2# set interface ge-1/0/0user@RR2# set interface ge-1/0/1user@RR2# set interface lo0.0 passive
  8. If you are done configuring the device, commit the configuration.
    [edit]user@RR2# commit

Results

From configuration mode, confirm your configuration by entering the show interfaces, show protocols, and show routing-options commands. If the output does not display the intended configuration, repeat the instructions in this example to correct the configuration.

user@RR2# show interfacesge-1/0/0 {unit 0 {description RR2-to-PE1;family inet {address 10.49.10.2/30;}family mpls;}}ge-1/0/1 {unit 0 {description RR2-to-PE2;family inet {address 10.50.10.2/30;}family mpls;}}
user@RR2# show protocolsbgp {group internal {local-address 10.255.165.28;cluster 1.1.1.1;neighbor 10.255.163.58 {description vpn2-to-pe1;family inet-vpn {unicast;}family route-target {proxy-generate;}}neighbor 10.255.168.42 {description vpn2-to-pe2;family inet-vpn {unicast;}family route-target;}}}ospf {area 0.0.0.0 {interface ge-1/0/0.0;interface ge-1/0/1.0;interface lo0.0 {passive;}}}ldp {interface ge-1/0/0.0;interface ge-1/0/1.0;}
user@RR2# show routing-optionsroute-distinguisher-id 10.255.165.28; autonomous-system 200;

Configuring Device PE2

Step-by-Step Procedure

The following example requires you to navigate various levels in the configuration hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration Mode in the CLI User Guide.

To configure Device PE2:

  1. Configure the interfaces.
    [edit interfaces]user@PE2# set ge-1/0/0 unit 0 description PE2-to-RR1user@PE2# set ge-1/0/0 unit 0 family inet address 10.50.0.1/30user@PE2# set ge-1/0/0 unit 0 family mplsuser@PE2# set ge-1/0/1 unit 0 description PE2-to-RR2user@PE2# set ge-1/0/1 unit 0 family inet address 10.50.10.2/30user@PE2# set ge-1/0/1 unit 0 family mpls
  2. Configure the route distinguisher and the AS number.
    [edit routing-options]user@PE2# set route-distinguisher-id 10.255.168.42user@PE2# set autonomous-system 200
  3. Configure LDP as the signaling protocol used by the VPN.
    [edit protocols ldp]user@PE2# set interface ge-1/0/0user@PE2# set interface ge-1/0/1
  4. Configure BGP.
    [edit protocols bgp group internal]user@PE2# set type internaluser@PE2# set local-address 10.255.168.42user@PE2# set family inet-vpn unicastuser@PE2# set family route-targetuser@PE2# set neighbor 10.255.165.220user@PE2# set neighbor 10.255.165.28
  5. Configure OSPF.
    [edit protocols ospf area 0.0.0.0]user@PE2# set interface ge-1/0/0user@PE2# set interface ge-1/0/1user@PE2# set interface lo0.0 passive
  6. Configure the VPN routing instances.
    [edit routing-instances vpn1]user@PE2# set instance-type vrfuser@PE2# set vrf-target target:200:100user@PE2# set routing-options static route 223.1.1.2/32 discard
    [edit routing-instances vpn2]user@PE2# set instance-type vrfuser@PE2# set vrf-target target:200:101user@PE2# set routing-options static route 223.2.2.2/32 discard
    [edit routing-instances vpn3]user@PE2# set instance-type vrfuser@PE2# set vrf-target target:200:103user@PE2# set routing-options static route 223.3.3.3/32 discard
    [edit routing-instances vpn4]user@PE2# set instance-type vrfuser@PE2# set vrf-target target:200:104user@PE2# set routing-options static route 223.4.4.4/32 discard
  7. If you are done configuring the device, commit the configuration.
    [edit]user@PE2# commit

Results

From configuration mode, confirm your configuration by entering the show interfaces, show protocols, show routing-options, and show routing-instances commands. If the output does not display the intended configuration, repeat the instructions in this example to correct the configuration.

user@PE2# show interfacesge-1/0/0 {unit 0 {description PE2-to-RR1;family inet {address 10.50.0.1/30;}family mpls;}}ge-1/0/1 {unit 0 {description PE2-to-RR2;family inet {address 10.50.10.2/30;}family mpls;}}
user@PE2# show protocolsbgp {group internal {type internal;local-address 10.255.168.42;family inet-vpn {unicast;}family route-target;neighbor 10.255.165.220;neighbor 10.255.165.28;}}ospf {area 0.0.0.0 {interface ge-1/0/0.0;interface ge-1/0/1.0;interface lo0.0 {passive;}}}ldp {interface ge-1/0/0.0;interface ge-1/0/1.0;}
user@PE2# show routing-optionsroute-distinguisher-id 10.255.168.42;autonomous-system 200;
user@PE2# show routing-instancesvpn1 {instance-type vrf;vrf-target target:200:100;routing-options {static {route 223.1.1.2/32 discard;}}}vpn2 {instance-type vrf;vrf-target target:200:101;routing-options {static {route 223.2.2.2/32 discard;}}}vpn3 {instance-type vrf;vrf-target target:200:103;routing-options {static {route 223.3.3.3/32 discard;}}}vpn4 {instance-type vrf;vrf-target target:200:104;routing-options {static {route 223.4.4.4/32 discard;}}}

Verification

Confirm that the configuration is working properly.

Verifying the Proxy BGP Route Target Routes

Purpose

Verify that the proxy BGP route target routes are displayed in the bgp.rtarget.0 table on Device RR1.

Action

From operational mode, enter the show route table bgp.rtartget.0 command to display the proxy BGP route targets.

user@RR1# show route table bgp.rtarget.0
4 destinations, 6 routes (4 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

200:200:100/96                
                   *[RTarget/5] 00:01:22
                      Type Proxy
                        for 10.255.163.58
                         Local
                    [BGP/170] 00:04:55, localpref 100, from 10.255.168.42
                      AS path: I, validation-state: unverified
                    > to 10.50.0.1 via ge-1/0/1
200:200:101/96                
                   *[RTarget/5] 00:01:22
                      Type Proxy
                        for 10.255.163.58
                         Local
                    [BGP/170] 00:04:55, localpref 100, from 10.255.168.42
                      AS path: I, validation-state: unverified
                    > to 10.50.0.1 via ge-1/0/1
200:200:103/96                
                   *[BGP/170] 00:04:55, localpref 100, from 10.255.168.42
                      AS path: I, validation-state: unverified
                    > to 10.50.0.1 via ge-1/0/1
200:200:104/96                
                   *[BGP/170] 00:04:55, localpref 100, from 10.255.168.42
                      AS path: I, validation-state: unverified
                    > to 10.50.0.1 via ge-1/0/1

Meaning

Device RR1 is generating the proxy BGP route target routes on behalf of its peer Device PE1. The proxy BGP route target routes are identified with the protocol and preference [RTarget/5] and the route target type of Proxy.

Example: Configuring an Export Policy for BGP Route Target Filtering

This example shows how to configure an export routing policy for BGP route target filtering (also known as route target constrain, or RTC).

Requirements

This example uses the following hardware and software components:

  • Four Juniper Networks devices that support BGP route target filtering.
  • Junos OS Release 12.2 or later on one or more devices configured for proxy BGP route filtering. In this example, you explicitly configure proxy BGP route filtering on the route reflectors.

Before configuring an export policy for BGP route target filtering, make sure that you are familiar with and understand the following concepts:

Overview

BGP route target filtering allows you to reduce network resource consumption by distributing route target membership (RT membership) advertisements throughout the network. BGP uses the RT membership information to send VPN routes only to the devices that need them in the network. Similar to other types of BGP reachability, you can apply a routing policy to route target filtering routes to influence the network. When route target filtering is configured, restricting the flow of route target filtering routes also restricts the VPN routes that might be attracted by this RT membership. Configuring this policy involves:

  • Creating a filter that defines the list of route target prefixes.
  • Creating a policy to select a subset of the route target filters to use for BGP route target filtering.

To define the list of route target prefixes:

  • You configure the rtf-prefix-list statement at the [edit policy-options] hierarchy level to specify the name of the route target prefix list and one or more route target prefixes to use. This configuration allows you to specify the incoming route target filtering routes that the device will use and then distribute them throughout the network.

To configure the routing policy and apply the route target prefix list to that policy, you can specify the following policy options:

  • family route-target—(Optional) The route-target family match condition specifies matching BGP route target filtering routes. You define this criteria in the from statement. This example shows how to create an export policy using the family route-target match condition.
  • protocol route-target—(Optional) The route-target protocol match condition defines the criteria that an incoming route must match. You define this criteria in the from statement. This statement is primarily useful for restricting the policy to locally generated route target filtering routes.

    Note: When you use the show route table bgp.rtarget.0 command to view proxy BGP route target filtering routes, you will see the BGP protocol for received routes and the route target protocol routes for local route target filtering routes.

  • rtf-prefix-list name—The rtf-prefix-list statement applies the list of route target prefixes that you already configured to the policy. You define this criteria in the from statement.

Topology Diagram

Figure 2 shows the topology used in this example.

Figure 2: BGP Route Target Filtering Export Policy Topology

BGP Route Target Filtering Export Policy Topology

In this example, BGP route target filtering is configured on the route reflectors (Device RR1 and Device RR2) and provider edge (PE) Device PE2. The other PE, Device PE1, does not support BGP route target filtering. Proxy BGP route target filtering is also configured on the peering sessions between the route reflectors and Device PE1 to minimize the number of VPN route updates processed by Device PE1. Device PE2 has four VPNs configured (vpn1, vpn2, vpn3, and vpn4), and Device PE1 has two VPNs configured (vpn1 and vpn2). In the sample topology, all devices participate in autonomous system (AS) 200, OSPF is the configured interior gateway protocol (IGP), and LDP is the signaling protocol used by the VPNs. In this example, we use static routes in the VPN routing and forwarding (VRF) instances to generate VPN routes. This is done in place of using a PE to customer edge (CE) protocol such as OSPF or BGP.

In this example, you further control the routes being advertised from Device PE2 to Device PE1 by configuring an export policy on Device PE2 to prevent vpn3 routes from being advertised to Device RR1. You create a policy that specifies the family route-target match condition, defines the list of route target prefixes, and applies the list of route target prefixes by defining the rtf-prefix-list criteria.

Configuration

CLI Quick Configuration

To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your network configuration, and then copy and paste the commands into the CLI at the [edit] hierarchy level.

Device PE1

set interfaces ge-1/0/0 unit 0 description PE1-to-RR1set interfaces ge-1/0/0 unit 0 family inet address 10.49.0.1/30set interfaces ge-1/0/0 unit 0 family mplsset interfaces ge-1/0/1 unit 0 description PE1-to-RR2set interfaces ge-1/0/1 unit 0 family inet address 10.49.10.1/30set interfaces ge-1/0/1 unit 0 family mpls set protocols ldp interface ge-1/0/0set protocols ldp interface ge-1/0/1set protocols bgp group internal type internal set protocols bgp group internal local-address 10.255.163.58 set protocols bgp group internal neighbor 10.255.165.220 family inet-vpn unicastset protocols bgp group internal neighbor 10.255.165.28 family inet-vpn unicast set protocols ospf area 0.0.0.0 interface ge-1/0/0set protocols ospf area 0.0.0.0 interface ge-1/0/1set protocols ospf area 0.0.0.0 interface lo0.0 passiveset routing-options route-distinguisher-id 10.255.163.58set routing-options autonomous-system 200set routing-instances vpn1 instance-type vrfset routing-instances vpn1 vrf-target target:200:100set routing-instances vpn1 routing-options static route 223.1.1.2/32 discardset routing-instances vpn2 instance-type vrfset routing-instances vpn2 vrf-target target:200:101set routing-instances vpn2 routing-options static route 223.2.2.2/32 discard

Device RR1

set interfaces ge-1/0/0 unit 0 description RR1-to-PE1set interfaces ge-1/0/0 unit 0 family inet address 10.49.0.2/30set interfaces ge-1/0/0 unit 0 family mpls set interfaces ge-1/0/1 unit 0 description RR1-to-PE2set interfaces ge-1/0/1 unit 0 family inet address 10.50.0.2/30set interfaces ge-1/0/1 unit 0 family mpls set protocols ldp interface ge-1/0/0set protocols ldp interface ge-1/0/1set protocols bgp group internal type internalset protocols bgp group internal local-address 110.255.165.220set protocols bgp group internal cluster 1.1.1.1set protocols bgp group internal neighbor 10.255.163.58 description vpn1-to-pe1 family inet-vpn unicastset protocols bgp group internal neighbor 10.255.163.58 family route-target proxy-generateset protocols bgp group internal neighbor 10.255.168.42 description vpn1-to-pe2 family inet-vpn unicastset protocols ospf area 0.0.0.0 interface ge-1/0/0set protocols ospf area 0.0.0.0 interface ge-1/0/1set protocols ospf area 0.0.0.0 interface lo0.0 passiveset routing-options route-distinguisher-id 10.255.165.220set routing-options autonomous-system 200

Device RR2

set interfaces ge-1/0/0 unit 0 description RR2-to-PE1set interfaces ge-1/0/0 unit 0 family inet address 10.49.10.2/30set interfaces ge-1/0/0 unit 0 family mpls set interfaces ge-1/0/1 unit 0 description RR2-to-PE2set interfaces ge-1/0/1 unit 0 family inet address 10.50.10.2/30set interfaces ge-1/0/1 unit 0 family mpls set protocols ldp interface ge-1/0/0set protocols ldp interface ge-1/0/1set protocols bgp group internal type internalset protocols bgp group internal local-address 10.255.165.28set protocols bgp group internal cluster 1.1.1.1set protocols bgp group internal neighbor 10.255.163.58 description vpn2-to-pe1 family inet-vpn unicastset protocols bgp group internal neighbor 10.255.163.58 family route-target proxy-generateset protocols bgp group internal neighbor 10.255.168.42 description vpn2-to-pe2 family inet-vpn unicastset protocols bgp group internal neighbor 10.255.163.58 family route-target set protocols ospf area 0.0.0.0 interface ge-1/0/0set protocols ospf area 0.0.0.0 interface ge-1/0/1set protocols ospf area 0.0.0.0 interface lo0.0 passiveset routing-options route-distinguisher-id 10.255.165.28set routing-options autonomous-system 200

Device PE2

set interfaces ge-1/0/0 unit 0 description PE2-to-RR1set interfaces ge-1/0/0 unit 0 family inet address 10.50.0.1/30set interfaces ge-1/0/0 unit 0 family mplsset interfaces ge-1/0/1 unit 0 description PE2-to-RR2set interfaces ge-1/0/1 unit 0 family inet address 10.50.10.2/30set interfaces ge-1/0/1 unit 0 family mpls set protocols ldp interface ge-1/0/0set protocols ldp interface ge-1/0/1set protocols bgp group internal type internal set protocols bgp group internal local-address 10.255.168.42 set protocols bgp group internal family inet-vpn unicastset protocols bgp group internal family route-targetset protocols bgp group internal neighbor 10.255.165.220 export filter-rtcset protocols bgp group internal neighbor 10.255.165.28set protocols ospf area 0.0.0.0 interface ge-1/0/0set protocols ospf area 0.0.0.0 interface ge-1/0/1set protocols ospf area 0.0.0.0 interface lo0.0 passiveset policy-options rtf-prefix-list exclude-103 200:200:103/96set policy-options policy-statement filter-rtc from family route-targetset policy-options policy-statement filter-rtc from rtf-prefix-list exclude-103set policy-options policy-statement filter-rtc then rejectset routing-options route-distinguisher-id 10.255.168.42set routing-options autonomous-system 200set routing-instances vpn1 instance-type vrfset routing-instances vpn1 vrf-target target:200:100set routing-instances vpn1 routing-options static route 223.1.1.2/32 discardset routing-instances vpn2 instance-type vrfset routing-instances vpn2 vrf-target target:200:101set routing-instances vpn2 routing-options static route 223.2.2.2/32 discardset routing-instances vpn3 instance-type vrfset routing-instances vpn3 vrf-target target:200:103set routing-instances vpn3 routing-options static route 223.3.3.3/32 discardset routing-instances vpn4 instance-type vrfset routing-instances vpn4 vrf-target target:200:104set routing-instances vpn4 routing-options static route 223.4.4.4/32 discard

Configuring Device PE1

Step-by-Step Procedure

The following example requires you to navigate various levels in the configuration hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration Mode in the CLI User Guide.

To configure Device PE1:

  1. Configure the interfaces.
    [edit interfaces]user@PE1# set ge-1/0/0 unit 0 description PE1-to-RR1user@PE1# set ge-1/0/0 unit 0 family inet address 10.49.0.1/30user@PE1# set ge-1/0/0 unit 0 family mplsuser@PE1#set ge-1/0/1 unit 0 description PE1-to-RR2user@PE1#set ge-1/0/1 unit 0 family inet address 10.49.10.1/30user@PE1# set ge-1/0/1 unit 0 family mpls
  2. Configure the route distinguisher and the AS number.
    [edit routing-options]user@PE1# set route-distinguisher-id 10.255.163.58user@PE1# set autonomous-system 200
  3. Configure LDP as the signaling protocol used by the VPN.
    [edit protocols ldp]user@PE1# set interface ge-1/0/0user@PE1# set interface ge-1/0/1
  4. Configure BGP.
    [edit protocols bgp group internal]user@PE1# set type internaluser@PE1# set local-address 10.255.163.58user@PE1# set neighbor 10.255.165.220 family inet-vpn unicastuser@PE1# set neighbor 10.255.165.28 family inet-vpn unicast
  5. Configure OSPF.
    [edit protocols ospf area 0.0.0.0]user@PE1# set interface ge-1/0/0user@PE1# set interface ge-1/0/1user@PE1# set interface lo0.0 passive
  6. Configure the VPN routing instances.
    [edit routing-instances vpn1]user@PE1# set instance-type vrfuser@PE1# set vrf-target target:200:100user@PE1# set routing-options static route 223.1.1.2/32 discard
    [edit routing-instances vpn2]user@PE1# set instance-type vrfuser@PE1# set vrf-target target:200:101user@PE1# set routing-options static route 223.2.2.2/32 discard
  7. If you are done configuring the device, commit the configuration.
    [edit]user@PE1# commit

Results

From configuration mode, confirm your configuration by entering the show interfaces, show protocols, show routing-options, and show routing-instances commands. If the output does not display the intended configuration, repeat the instructions in this example to correct the configuration.

user@PE1# show interfacesge-1/0/0 {unit 0 {description PE1-to-RR1;family inet {address 10.49.0.1/30;}family mpls;}}ge-1/0/1 {unit 0 {description PE1-to-RR2;family inet {address 10.49.10.1/30;}family mpls;}}
user@PE1# show protocolsbgp {group internal {type internal;local-address 10.255.163.58;neighbor 10.255.165.220 {family inet-vpn {unicast;}}neighbor 10.255.165.28 {family inet-vpn {unicast;}}}}ospf {area 0.0.0.0 {interface ge-1/0/0.0;interface ge-1/0/1.0;interface lo0.0 {passive;}}}ldp {interface ge-1/0/0.0;interface ge-1/0/1.0;}
user@PE1# show routing-optionsroute-distinguisher-id 10.255.14.182;autonomous-system 200;
user@PE1# show routing-instancesvpn1 {instance-type vrf;vrf-target target:200:100;routing-options {static {route 223.1.1.2/32 discard;}}}vpn2 {instance-type vrf;vrf-target target:200:101;routing-options {static {route 223.2.2.2/32 discard;}}}

Configuring Device RR1

Step-by-Step Procedure

The following example requires you to navigate various levels in the configuration hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration Mode in the CLI User Guide.

To configure Device RR1:

  1. Configure the interfaces.
    [edit interfaces]user@RR1# set ge-1/0/0 unit 0 description RR1-to-PE1user@RR1# set ge-1/0/0 unit 0 family inet address 10.49.0.2/30user@RR1# set ge-1/0/0 unit 0 family mplsuser@RR1# set ge-1/0/1 unit 0 description RR1-to-PE2user@RR1# set ge-1/0/1 unit 0 family inet address 10.50.0.2/30user@RR1# set ge-1/0/1 unit 0 family mpls
  2. Configure the route distinguisher and the AS number.
    [edit routing-options]user@RR1# set route-distinguisher-id 10.255.165.220user@RR1# set autonomous-system 200
  3. Configure LDP as the signaling protocol used by the VPN.
    [edit protocols ldp]user@RR1# set interface ge-1/0/0user@RR1# set interface ge-1/0/1
  4. Configure BGP.
    [edit protocols bgp group internal]user@RR1# set type internaluser@RR1# set local-address 10.255.165.220user@RR1# set cluster 1.1.1.1user@RR1# set neighbor 10.255.163.58 description vpn1-to-pe1 family inet-vpn unicastuser@RR1# set neighbor 10.255.168.42 description vpn1-to-pe2 family inet-vpn unicast
  5. Configure BGP route target filtering on the peering session with Device PE2.
    [edit protocols bgp group internal]user@RR1# set neighbor 10.255.168.42 family route-target
  6. Configure proxy BGP route target filtering on the peering session with Device PE1.
    [edit protocols bgp group internal]user@RR1# set neighbor 10.255.163.58 family route-target proxy-generate
  7. Configure OSPF.
    [edit protocols ospf area 0.0.0.0]user@RR1# set interface ge-1/0/0user@RR1# set interface ge-1/0/1user@RR1# set interface lo0.0 passive
  8. If you are done configuring the device, commit the configuration.
    [edit]user@RR1# commit

Results

From configuration mode, confirm your configuration by entering the show interfaces, show protocols, and show routing-options commands. If the output does not display the intended configuration, repeat the instructions in this example to correct the configuration.

user@RR1# show interfacesge-1/0/0 {unit 0 {description RR1-to-PE1;family inet {address 10.49.0.2/30;}family mpls;}}ge-1/0/1 {unit 0 {description RR1-to-PE2;family inet {address 10.50.0.2/30;}family mpls;}}
user@RR1# show protocolsbgp {group internal {type internal;local-address 110.255.165.220;cluster 1.1.1.1;neighbor 10.255.163.58 {description vpn1-to-pe1;family inet-vpn {unicast;}family route-target {proxy-generate;}}neighbor 10.255.168.42 {description vpn1-to-pe2;family inet-vpn {unicast;}family route-target;}}}ospf {area 0.0.0.0 {interface ge-1/0/0.0;interface ge-1/0/1.0;interface lo0.0 {passive;}}}ldp {interface ge-1/0/0.0;interface ge-1/0/1.0;}ospf {area 0.0.0.0 {interface ge-1/0/0.0;interface ge-1/0/1.0;interface lo0.0 {passive;}}}ldp {interface ge-1/0/0.0;interface ge-1/0/1.0;}
user@RR1# show routing-optionsroute-distinguisher-id 10.255.165.220; autonomous-system 200;

Configuring Device RR2

Step-by-Step Procedure

The following example requires you to navigate various levels in the configuration hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration Mode in the CLI User Guide.

To configure Device RR2:

  1. Configure the interfaces.
    [edit interfaces]user@RR2# set ge-1/0/0 unit 0 description RR2-to-PE1user@RR2# set ge-1/0/0 unit 0 family inet address 10.49.10.2/30user@RR2# set ge-1/0/0 unit 0 family mplsuser@RR2# set ge-1/0/1 unit 0 description RR2-to-PE2user@RR2# set ge-1/0/1 unit 0 family inet address 10.50.10.2/30user@RR2# set ge-1/0/1 unit 0 family mpls
  2. Configure the route distinguisher and the AS number.
    [edit routing-options]user@RR2# set route-distinguisher-id 10.255.165.28user@RR2# set autonomous-system 200
  3. Configure LDP as the signaling protocol used by the VPN.
    [edit protocols ldp]user@RR2# set interface ge-1/0/0user@RR2# set interface ge-1/0/1
  4. Configure BGP.
    [edit protocols bgp group internal]user@RR2# set type internaluser@RR2# set local-address 10.255.165.28user@RR2# set cluster 1.1.1.1user@RR2# set neighbor 10.255.163.58 description vpn2-to-pe1 family inet-vpn unicastuser@RR2# set neighbor 10.255.168.42 description vpn2-to-pe2 family inet-vpn unicast
  5. Configure BGP route target filtering on the peering session with Device PE2.
    [edit protocols bgp group internal]user@RR2# set neighbor 10.255.168.42 family route-target
  6. Configure proxy BGP route target filtering on the peering session with Device PE1.
    [edit protocols bgp group internal]user@RR2# set neighbor 10.255.163.58 family route-target proxy-generate
  7. Configure OSPF.
    [edit protocols ospf area 0.0.0.0]user@RR2# set interface ge-1/0/0user@RR2# set interface ge-1/0/1user@RR2# set interface lo0.0 passive
  8. If you are done configuring the device, commit the configuration.
    [edit]user@RR2# commit

Results

From configuration mode, confirm your configuration by entering the show interfaces, show protocols, and show routing-options commands. If the output does not display the intended configuration, repeat the instructions in this example to correct the configuration.

user@RR2# show interfacesge-1/0/0 {unit 0 {description RR2-to-PE1;family inet {address 10.49.10.2/30;}family mpls;}}ge-1/0/1 {unit 0 {description RR2-to-PE2;family inet {address 10.50.10.2/30;}family mpls;}}
user@RR2# show protocolsbgp {group internal {local-address 10.255.165.28;cluster 1.1.1.1;neighbor 10.255.163.58 {description vpn2-to-pe1;family inet-vpn {unicast;}family route-target {proxy-generate;}}neighbor 10.255.168.42 {description vpn2-to-pe2;family inet-vpn {unicast;}family route-target;}}}ospf {area 0.0.0.0 {interface ge-1/0/0.0;interface ge-1/0/1.0;interface lo0.0 {passive;}}}ldp {interface ge-1/0/0.0;interface ge-1/0/1.0;}
user@RR2# show routing-optionsroute-distinguisher-id 10.255.165.28; autonomous-system 200;

Configuring Device PE2

Step-by-Step Procedure

The following example requires you to navigate various levels in the configuration hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration Mode in the CLI User Guide.

To configure Device PE2:

  1. Configure the interfaces.
    [edit interfaces]user@PE2# set ge-1/0/0 unit 0 description PE2-to-RR1user@PE2# set ge-1/0/0 unit 0 family inet address 10.50.0.1/30user@PE2# set ge-1/0/0 unit 0 family mplsuser@PE2#set ge-1/0/1 unit 0 description PE2-to-RR2user@PE2#set ge-1/0/1 unit 0 family inet address 10.50.10.2/30user@PE2# set ge-1/0/1 unit 0 family mpls
  2. Configure the route distinguisher and the AS number.
    [edit routing-options]user@PE2# set route-distinguisher-id 10.255.168.42user@PE2# set autonomous-system 200
  3. Configure LDP as the signaling protocol used by the VPN.
    [edit protocols ldp]user@PE2# set interface ge-1/0/0user@PE2# set interface ge-1/0/1
  4. Configure BGP.
    [edit protocols bgp group internal]user@PE2# set type internaluser@PE2# set local-address 10.255.168.42user@PE2# set family inet-vpn unicastuser@PE2# set family route-targetuser@PE2# set neighbor 10.255.165.220user@PE2# set neighbor 10.255.165.28
  5. Configure OSPF.
    [edit protocols ospf area 0.0.0.0]user@PE2# set interface ge-1/0/0user@PE2# set interface ge-1/0/1user@PE2# set interface lo0.0 passive
  6. Configure the VPN routing instances.
    [edit routing-instances vpn1]user@PE2# set instance-type vrfuser@PE2# set vrf-target target:200:100user@PE2# set routing-options static route 223.1.1.2/32 discard
    [edit routing-instances vpn2]user@PE2# set instance-type vrfuser@PE2# set vrf-target target:200:101user@PE2# set routing-options static route 223.2.2.2/32 discard
    [edit routing-instances vpn3]user@PE2# set instance-type vrfuser@PE2# set vrf-target target:200:103user@PE2# set routing-options static route 223.3.3.3/32 discard
    [edit routing-instances vpn4]user@PE2# set instance-type vrfuser@PE2# set vrf-target target:200:104user@PE2# set routing-options static route 223.4.4.4/32 discard
  7. Configure and apply the export routing policy.
    [edit policy-options]user@PE2# set rtf-prefix-list exclude-103 200:200:103/96[edit policy-options policy-statement filter-rtc]user@PE2# set from family route-targetuser@PE2# set from rtf-prefix-list exclude-103user@PE2# set then reject[edit protocols bgp group internal]user@PE2# set neighbor 10.255.165.220 export filter-rtc
  8. If you are done configuring the device, commit the configuration.
    [edit]user@PE2# commit

Results

From configuration mode, confirm your configuration by entering the show interfaces, show protocols, show policy-options, show routing-options, and show routing-instances commands. If the output does not display the intended configuration, repeat the instructions in this example to correct the configuration.

user@PE2# show interfacesge-1/0/0 {unit 0 {description PE2-to-RR1;family inet {address 10.50.0.1/30;}family mpls;}}ge-1/0/1 {unit 0 {description PE2-to-RR2;family inet {address 10.50.10.2/30;}family mpls;}}
user@PE2# show protocolsbgp {group internal {type internal;local-address 10.255.168.42;family inet-vpn {unicast;}family route-target;neighbor 10.255.165.220 {export filter-rtc;}neighbor 10.255.165.28;}}ospf {area 0.0.0.0 {interface ge-1/0/0.0;interface ge-1/0/1.0;interface lo0.0 {passive;}}}ldp {interface ge-1/0/0.0;interface ge-1/0/1.0;}
user@PE2# show routing-optionsroute-distinguisher-id 10.255.168.42;autonomous-system 200;
user@PE2# show policy-optionspolicy-statement filter-rtc {from {family route-target;rtf-prefix-list exclude-103;}then reject;}rtf-prefix-list exclude-103 {200:200:103/96;}
user@PE2# show routing-instancesvpn1 {instance-type vrf;vrf-target target:200:100;routing-options {static {route 223.1.1.2/32 discard;}}}vpn2 {instance-type vrf;vrf-target target:200:101;routing-options {static {route 223.2.2.2/32 discard;}}}vpn3 {instance-type vrf;vrf-target target:200:103;routing-options {static {route 223.3.3.3/32 discard;}}}vpn4 {instance-type vrf;vrf-target target:200:104;routing-options {static {route 223.4.4.4/32 discard;}}}

Verification

Confirm that the configuration is working properly.

Verifying the Route Target Filtering Routes in the bgp.rtarget.0 Routing Table for Device RR1

Purpose

Verify that the route prefix for vpn3 is not in Device RR1’s bgp.rtarget.0 table. Since an export policy on Device PE2 was applied to prevent the advertisement of vpn3 routes to Device RR1, Device RR1 should not receive those advertisements.

Action

From operational mode, enter the show route advertising-protocol bgp 10.255.165.220 table bgp.rtarget.0 command.

user@PE2# show route advertising-protocol bgp 10.255.165.220 table bgp.rtarget.0
bgp.rtarget.0: 4 destinations, 11 routes 
(4 active, 0 holddown, 0 hidden)
  Prefix                  Nexthop              MED     Lclpref    AS path
  200:200:100/96          *                    Self      100        I
  200:200:101/96          *                    Self      100        I
  200:200:104/96          *                    Self      100        I

Meaning

The bgp.rtartget.0 table does not display 200:200:103/96, which is the route prefix for vpn3. That means the export policy was applied correctly.

Verifying the Route Target Filtering Routes in the bgp.rtarget.0 Routing Table for Device RR2

Purpose

Verify that the route prefix for vpn3 is in Device RR2’s bgp.rtarget.0 table. Since an export policy was not applied on Device PE2 to prevent the advertisement of vpn3 routes to Device RR2, Device RR2 should receive advertisements from all of the VPNs.

Action

From operational mode, enter the show route advertising-protocol bgp 10.255.165.28 table bgp.rtarget.0 command.

user@PE2# show route advertising-protocol bgp 10.255.165.28 table bgp.rtarget.0
bgp.rtarget.0: 4 destinations, 11 routes (4 active, 0 holddown, 0 hidden)
(4 active, 0 holddown, 0 hidden)
  Prefix                  Nexthop              MED     Lclpref    AS path
  200:200:100/96          *                    Self      100        I
  200:200:101/96          *                    Self      100        I
  200:200:103/96          *                    Self      100        I
  200:200:104/96          *                    Self      100        I

Meaning

The bgp.rtartget.0 table displays the route prefixes for all of the VPNs.

Published: 2012-11-29

Supported Platforms

Published: 2012-11-29

Previous Page Next Page