Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

English  

English

Configuring PE1 for MX Series Router Cloud CPE Draft-Rosen Multicast VPN Services

Complete the following tasks to configure the PE1 router for draft-rosen multicast VPNs and cCPE services:

1. Configuring the VLAN Interface, IRB Interface, and Bridge Domain for MX Series Router Draft-Rosen Multicast VPN Cloud CPE Services
2. Configuring the Loopback Interface and Assigning a VPN Private Address
3. Configuring the Routing Instance
4. Configuring the BSR and RP in the Routing Instance
5. Enabling PIM Version 2 on the IRB and Loopback Interfaces

Configuring the VLAN Interface, IRB Interface, and Bridge Domain for MX Series Router Draft-Rosen Multicast VPN Cloud CPE Services

1. Configure the physical interface for VLAN tagging and flexible Ethernet services encapsulation.
   [edit]user@host# edit interfaces ge-1/0/1 user@host# set vlan-tagginguser@host# set encapsulation flexible-ethernet-services
2. Configure the subscriber VLAN.
   1. Configure the logical interface.
      [edit interfaces ge-1/0/1]user@host# edit unit 106
   2. Configure the encapsulation for the logical interface.
      [edit interfaces ge-1/2/3 unit 106]user@host# set encapsulation vlan-bridge
   3. Bind an 802.1Q VLAN tag ID to the logical interface.
      [edit interfaces ge-1/0/1 unit 106]user@host# set vlan-id 106
   4. Configure the logical interface for Layer 2 bridging.
      [edit interfaces ge-1/0/1 unit 106]user@host# set family bridge
3. Configure the IRB interface.
   1. Configure the logical interface used for internal VPN traffic as the IRB interface.
      [edit]user@host# edit interfaces irb unit 106
   2. Specify the private subnet of the VPN site on the IRB interface.
      [edit interfaces irb unit 106]user@host# set family inet address 10.132.12.1/24
4. Configure the bridge domain.
   1. Configure the bridge domain name and set the domain type to bridge.
      [edit]user@host# edit bridge-domains vlan-106 domain-type bridge
   2. Associate the subscriber’s VLAN ID with the bridge domain.
      [edit bridge-domains vlan-106]user@host# set vlan-id 106
   3. Specify the interface name for the bridge domain.
      [edit bridge-domains vlan-106]user@host# set interface ge-1/0/1.106
   4. Specify the routing interface to include in the bridge domain.
      [edit bridge-domains vlan-106]user@host# set routing-interface irb.106
5. (Optional) If there are multiple Layer 2 interfaces in the same bridge domain, enable IGMP snooping in the bridge domain.
   [edit bridge-domains vlan-106]user@host# set protocols igmp-snooping

Configuring the Loopback Interface and Assigning a VPN Private Address

• To configure the loopback interface:
  [edit ]user@host# set interfaces lo0 unit 2 family inet address 10.132.12.254/32

Configuring the Routing Instance

1. Configure the name of the routing instance.
   [edit]user@host# edit routing-instances acme
2. Configure the routing instance as a VRF instance.
   [edit routing-instances acme]user@host# set instance-type vrf
3. Reference the IRB interface in the routing instance by specifying irb.vlan-id.
   [edit routing-instances acme]user@host# set interface irb.106
4. Reference the loopback interface in the routing instance.
   [edit routing-instances acme]user@host# set interface lo0.2
5. Specify a route distinguisher that is attached to the route, enabling you to distinguish which VPN the route belongs to. Each routing instance must have a unique route distinguisher associated with it.
   [edit routing-instances acme]user@host# set route-distinguisher 65535:4
6. Specify the VPN’s community. VRF import and export policies are automatically generated.
   [edit routing-instances acme]user@host# set vrf-target target:65535:5
7. Map the inner label of a packet to a specific VRF table. This enables examination of encapsulated IP headers.
   [edit routing-instances acme]user@host# set vrf-table-label
8. Configure the group address for the Layer 3 VPN in the service provider’s network.
   [edit routing-instances acme]user@host# set protocols pim vpn-group-address 239.1.1.1

Configuring the BSR and RP in the Routing Instance

1. Configure the BSR. Make sure to set different priorities on the PE routers.
   [edit routing-instances acme]user@host# edit protocols pim rp bootstrap family inet priority 2
2. Configure a candidate RP in the VRF. Make sure to set different priorities on the PE routers.
   [edit routing-instances acme protocols pim rp]user@host# set local family inet address 10.132.12.254 user@host# set local family inet priority 2

Enabling PIM Version 2 on the IRB and Loopback Interfaces

• Enable PIM on the IRB interface and configure the PIM mode as sparse.
  [edit routing-instances acme protocols pim]user@host# set interface irb.106 mode sparseuser@host# set interface irb.106 version 2user@host# set interface lo0.2 mode sparse user@host# set interface lo0.2 version 2