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 the PE Router for MX Series Router Cloud CPE Multiple Ethernet Interface Services (All VLANs in One Bridge Domain)

Configuring the Subscriber Access Link and VLANs for MX Series Router Cloud CPE Multiple Ethernet Interface Services

1. Configure the physical interface.
   [edit]user@host# edit interfaces ge-1/2/3 user@host# set vlan-tagginguser@host# set encapsulation flexible-ethernet-services
2. Configure the first logical interface and VLAN.
   [edit interfaces ge-1/2/3]user@host# edit unit 105 user@host# set encapsulation vlan-bridgeuser@host# set vlan-id 105 user@host# set family bridge
3. Configure the second logical interface and VLAN.
   [edit interfaces ge-1/2/3 unit 105]user@host# upuser@host# edit unit 106 [edit interfaces ge-1/2/3 unit 106]user@host# set encapsulation vlan-bridgeuser@host# set vlan-id 106 user@host# set family bridge
4. Review your configuration.
   [edit interfaces ge-1/2/3 unit 106]user@host# upuser@host# show

   unit 105 {
       encapsulation vlan-bridge;
       vlan-id 105;
       family bridge;
   }
   unit 106 {
       encapsulation vlan-bridge;
       vlan-id 106;
       }
   

Configuring the Bridge Domain for MX Series Router Cloud CPE Multiple Ethernet Interface Services

1. Configure the bridge domain for the first subscriber VLAN by specifying the name of the bridge domain.
   [edit]user@host# edit bridge-domains bd-105
2. Associate the subscriber’s VLAN ID with the bridge domain.
   [edit bridge-domains bd-105]user@host# set vlan-id 105
3. Specify the interface names for the bridge domain.
   [edit bridge-domains bd-105]user@host# set interface ge-1/2/3.105 user@host# set interface ge-1/2/3.106
4. Specify the routing interface to include in the bridge domain.
   [edit bridge-domains bd-105]user@host# set routing-interface irb.105
5. To control broadcast from one VLAN reaching into other VLANs, you can either enable no-local-switching in the bridge domain or configure a Layer 2 filter.
   • (Optional) To enable no-local-switching in the bridge domain:
     [edit bridge-domains bd-105]user@host# set routing-interface irb.105 no-local-switching
   • (Optional) To configure a Layer 2 filter:
     [edit bridge-domains bd-105]user@host# set forwarding-options filter input no-dhcpuser@host# topuser@host# edit firewall family bridge filter no-dhcp[edit firewall family bridge filter no-dhcp]user@host# set term dhcp from port dhcpuser@host# set term dhcp then discarduser@host# set term accept-all then accept
6. Review the configuration.
   [edit bridge-domains bd-105]user@host# show

   vlan-id 105;
   no-local-switching;
   interface ge-1/2/3.105;
   interface ge-1/2/3.106;
   routing-interface irb.105;
   

Configuring the Routing Instances for MX Series Router Cloud CPE Multiple Ethernet Interface Services

1. Configure a name for the routing instance.
   [edit]user@host# edit routing-instances ccpe1
2. Configure the VRF routing instance.
   [edit routing-instances ccpe1]user@host# set instance-type vrf
3. Reference the IRB interface by specifying irb.vlan-id.
   [edit routing-instances ccpe1]user@host# set interface irb.105
4. Review the configuration.
   [edit routing-instances ccpe1]user@host# show

   instance-type vrf;
   interface irb.105;
   

Configuring the IRB Interface for MX Series Router Cloud CPE Multiple Ethernet Interface Services

1. Configure the first subnet on the IRB interface.
   [edit]user@host# edit interfaces irb unit 105 family inet user@host# set address 192.168.1.1/24
2. Configure the second subnet on the IRB interface.
   [edit interfaces irb unit 105 family inet]user@host# set address 192.168.2.1/24
3. Review the configuration.
   [edit interfaces irb unit 106 family inet]user@host# show

   unit 105 {
       family inet {
           address 192.168.1.1/24;
           address 192.168.2.1/24;
       }
   }