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 (All VLANs in One Bridge Domain)
- 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
When you configure routed VLAN interfaces (RVIs) in the Layer 2 CPE, it creates a shortcut for inter-VLAN traffic. There is one RVI per subscriber VLAN. The RVI creates a direct route in the Layer 2 CPE for inter-VLAN traffic.
![]() | Note: To run this configuration the host connecting to the customer VLAN needs a static route with the RVI address as the gateway for inter-VLAN traffic . |
![]() | Note: This procedure uses a Juniper Networks EX Series Ethernet Switch for the Layer 2 CPE. |
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 router and Layer 2 CPE:
- Configure the PE router. 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. See Configuring the Layer 2 CPE When Running MX Series Router Cloud CPE Multiple Ethernet Interface and RVI Services
Note: This procedure uses a Juniper EX Series Ethernet Switch for the Layer 2 CPE.
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 (All VLANs in One Bridge Domain)
- Configuring MX Series Router Cloud CPE Multiple Ethernet Interface Services—Extending Subscriber VLANs to the PE Router Using a Q-in-Q Tunnel
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 (All VLANs in One Bridge Domain)
- Configuring MX Series Router Cloud CPE Multiple Ethernet Interface Services—Extending Subscriber VLANs to the PE Router Using a Q-in-Q Tunnel