Navigation
Supported Platforms
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
Configuring the Layer 2 CPE When Running MX Series Router Cloud CPE Multiple Ethernet Interface and RVI Services
![]() | Note: This procedure uses a Juniper Networks EX Series Ethernet Switch for the Layer 2 CPE. |
To configure the Layer 2 CPE for multiple Ethernet interfaces with RVIs:
- Configure the first Ethernet
interface on the Layer 2 CPE.[edit]user@host# set interfaces ge-0/0/8 unit 0 family ethernet-switching port-mode access
- Configure the second Ethernet interface by specifying
a different physical interface. You can use the same logical interface
number, which in our example is 0.[edit]user@host# set interfaces ge-0/0/9 unit 0 family ethernet-switching port-mode access
- Configure the VLAN trunk port for a WAN link.[edit]user@host# set interfaces ge-0/0/10 unit 0 family ethernet-switching port-mode trunk
- Configure the RVIs.[edit]user@host# set interfaces vlan unit 0 family inet address 192.168.1.254/24user@host# set interfaces vlan unit 1 family inet address 192.168.2.254/24
- Configure the VLAN for the first department; for example,
Sales.
- Specify the VLAN name and VLAN ID.
- Specify the interface associated with
the VLAN.[edit vlans sales-vlan]user@host# set interface ge-0/0/8.0
- Specify the trunk port interface associated
with the VLAN.[edit vlans sales-vlan]user@host# set interface ge-0/0/10.0
- Associate a Layer 3 interface with the VLAN. Configure
Layer 3 interfaces on trunk ports to allow the interface to transfer
traffic between multiple VLANs. Within a VLAN, traffic is bridged,
whereas across VLANs, traffic is routed. [edit vlans sales-vlan]user@host# set l3-interface vlan.0
- Configure the VLAN for the second department; for example,
Engineering.
- Specify the VLAN name and VLAN ID.
- Specify the interface associated with the VLAN.[edit vlans eng-vlan]user@host# set interface ge-0/0/9.0
- Specify the trunk port interface associated with the VLAN.[edit vlans eng-vlan]user@host# set interface ge-0/0/10.0
- Associate a Layer 3 interface with the VLAN. Configure
Layer 3 interfaces on trunk ports to allow the interface to transfer
traffic between multiple VLANs. Within a VLAN, traffic is bridged,
whereas across VLANs, traffic is routed. [edit vlans eng-vlan]user@host# set l3-interface vlan.1
- Finally, configure a static route with the RVI addresses
as the gateway on the host connecting to the subscriber VLAN for inter-VLAN
traffic. If the customer host device uses DHCP to get IP addresses,
a static route can be pushed by the DHCP server through option 121;
otherwise, you must manually configure the static route.
- Add a static route for the subnet using the RVI as the
gateway.route add -net 192.168.2.0/24 gw 192.168.1.254
- Add a static route using the IRB as the gateway. route add -net 0.0.0.0/0 gw 192.168.1.1
- Add a static route for the subnet using the RVI as the
gateway.
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
Modified: 2015-10-29
Supported Platforms
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