Related Documentation
- EX, MX Series
- MX Series Router Cloud CPE Multiple Ethernet Interface Services Overview
- Configuring MX Series Router Cloud CPE Multiple Ethernet Interface Services—Extending Subscriber VLANs to the PE Router (One Bridge Domain per VLAN)
- Configuring MX Series Router Cloud CPE Multiple Ethernet Interface Services—Extending Subscriber VLANs to the PE Router Using a Q-in-Q Tunnel
- Configuring MX Series Router Cloud CPE Multiple Ethernet Interface and Routed VLAN Interface Services
Configuring MX Series Router Cloud CPE Multiple Ethernet Interface Services—Extending Subscriber VLANs to the PE Router (All VLANs in One Bridge Domain)
This procedure configures all subscriber VLANs in the same bridge domain, so only one IRB interface is required per subscriber. You need to configure multiple IP addresses (one per subnet) on the IRB interface. The bridge domain joins multiple VLANs together. To control broadcasts from one VLAN reaching into other VLANs, do not enable local switching in the bridge domain. Alternatively, you can control selected broadcast traffic with a Layer 2 forwarding filter.
 | Note: To avoid VLAN ID conflicts between subscribers, you can configure VLAN ID translation on the Layer 2 CPE or the aggregation router. |
Before you begin, make sure you have completed the steps for the cCPE common configuration. See Configuring the Common Configuration for MX Series Router Cloud CPE Services.
Then complete the following tasks to configure the PE routers and Layer 2 CPE:
- Configure the PE routers. See Configuring the PE Router for MX Series Router Cloud CPE Multiple Ethernet Interface Services (All VLANs in One Bridge Domain)
- Configure the Layer 2 CPE. This procedure uses a Juniper EX Series Ethernet Switch for the Layer 2 CPE. See Configuring the Layer 2 CPE for MX Series Router Cloud CPE Multiple Ethernet Interface Services
Related Documentation
- EX, MX Series
- MX Series Router Cloud CPE Multiple Ethernet Interface Services Overview
- Configuring MX Series Router Cloud CPE Multiple Ethernet Interface Services—Extending Subscriber VLANs to the PE Router (One Bridge Domain per VLAN)
- Configuring MX Series Router Cloud CPE Multiple Ethernet Interface Services—Extending Subscriber VLANs to the PE Router Using a Q-in-Q Tunnel
- Configuring MX Series Router Cloud CPE Multiple Ethernet Interface and Routed VLAN Interface Services
Modified: 2015-11-04
Related Documentation
- EX, MX Series
- MX Series Router Cloud CPE Multiple Ethernet Interface Services Overview
- Configuring MX Series Router Cloud CPE Multiple Ethernet Interface Services—Extending Subscriber VLANs to the PE Router (One Bridge Domain per VLAN)
- Configuring MX Series Router Cloud CPE Multiple Ethernet Interface Services—Extending Subscriber VLANs to the PE Router Using a Q-in-Q Tunnel
- Configuring MX Series Router Cloud CPE Multiple Ethernet Interface and Routed VLAN Interface Services
