Related Documentation
- EX Series
- Example: Configuring MPLS on EX Series Switches
- Example: Configuring MPLS-Based Layer 2 VPNs
- Verifying That MPLS Is Working Correctly
- Understanding Junos OS MPLS Components for EX Series Switches
- M Series
- Example: Configuring MPLS-Based Layer 2 VPNs
- MX Series
- Example: Configuring MPLS-Based Layer 2 VPNs
- T Series
- Example: Configuring MPLS-Based Layer 2 VPNs
Configuring an MPLS-Based VLAN CCC Using a Layer 2 Circuit (CLI Procedure)
You can use configure an 802.1Q VLAN as an MPLS-based Layer 2 circuit using EX8200 switches to interconnect multiple customer sites with Layer 2 technology.
This topic describes configuring provider edge (PE) switches in an MPLS network using a circuit cross-connect (CCC) on a tagged VLAN interface (802.1Q VLAN) rather than a simple interface.
![]() | Note: You do not need to make any changes to existing provider switches in your MPLS network to support this type of configuration. For information on configuring provider switches, see Configuring MPLS on Provider Switches (CLI Procedure). |
![]() | Note: You can send any kind of traffic over a CCC, including nonstandard bridge protocol data units (BPDUs) generated by other vendors’ equipment. |
To configure a PE switch with a VLAN CCC and an MPLS-based Layer 2 circuit:
- Configure OSPF (or IS-IS) on the loopback (or switch address)
and core interfaces:
[edit protocols]
user@switch# set ospf area 0.0.0.0 interface lo0.0
user@switch# set ospf area 0.0.0.0 interface interface-name
user@switch# set ospf area 0.0.0.0 interface interface-name
user@switch# set ospf area 0.0.0.0 interface interface-name
- Enable traffic engineering for the routing protocol:
[edit protocols]
user@switch# set ospf traffic-engineering
- Configure an IP address for the loopback interface and
for the core interfaces:
[edit]
user@switch# set interfaces lo0 unit logical-unit-number family inet address address
user@switch# set interfaces interface-name unit logical-unit-number family inet address address
user@switch# set interfaces interface-name unit logical-unit-number family inet address address
user@switch# set interfaces interface-name unit logical-unit-number family inet address address - Enable the MPLS protocol with cspf disabled:

Note: CSPF is a shortest-path-first algorithm that has been modified to take into account specific restrictions when the shortest path across the network is calculated. You need to disable CSPF for link protection to function properly on interarea paths.
- Configure the customer edge interface as a Layer 2 circuit
from the local PE switch to the other PE switch:
[edit protocols]
user@switch# set l2circuit neighbor address interface interface-name virtual-circuit-id identifier
Tip: Use the switch address of the other switch as the neighbor address.
- Configure MPLS on the core interfaces:
[edit protocols]
user@switch# set mpls interface interface-name
user@switch# set mpls interface interface-name
user@switch# set mpls interface interface-name
- Configure LDP on the loopback interface and the core interfaces:
[edit protocols]
user@switch# set ldp interface lo0.0
user@switch# set ldp interface interface-name
user@switch# set ldp interface interface-name
user@switch# set ldp interface interface-name
- Configure family mpls on the logical units of
the core interfaces:
[edit]
user@switch# set interfaces interface-name unit logical-unit-number family mpls
user@switch# set interfaces interface-name unit logical-unit-number family mpls
user@switch# set interfaces interface-name unit logical-unit-number family mpls
Note: You can enable family mpls on either individual interfaces or aggregated Ethernet interfaces. You cannot enable it on tagged VLAN interfaces.
- Enable VLAN tagging on the customer edge interface of
the local PE switch:
[edit]
user@switch# set interfaces interface-name vlan-tagging - Configure the customer edge interface to use encapsulation vlan-ccc:
[edit]
user@switch# set interfaces interface-name encapsulation vlan-ccc - Configure the logical unit of the customer edge interface
with a VLAN ID:

Note: The VLAN ID cannot be configured on logical interface unit 0. The logical unit number must be 1 or higher.
The same VLAN ID must be used when configuring the customer edge interface on the other PE switch.
[edit ]
user@switch# set interfaces interface-name logical-unit-number vlan-id vlan-id
When you have completed configuring one PE switch, follow the same procedures to configure the other PE switch.
![]() | Note: You must use the same type of switch for the other PE switch. You cannot use an EX8200 as one PE switch and use an EX3200 or EX4200 as the other PE switch. |
Related Documentation
- EX Series
- Example: Configuring MPLS on EX Series Switches
- Example: Configuring MPLS-Based Layer 2 VPNs
- Verifying That MPLS Is Working Correctly
- Understanding Junos OS MPLS Components for EX Series Switches
- M Series
- Example: Configuring MPLS-Based Layer 2 VPNs
- MX Series
- Example: Configuring MPLS-Based Layer 2 VPNs
- T Series
- Example: Configuring MPLS-Based Layer 2 VPNs

