close

keyboard_arrow_left

Table of Contents Expand all

play_arrow Overview
- play_arrow Understanding MPLS
  - MPLS Overview
- play_arrow Supported Standards
  - Supported MPLS Standards
play_arrow MPLS Configuration
- play_arrow Configuring MPLS
- play_arrow Configuring MPLS Tunnels
  - IPv6-over-Ipv4 Tunnels
  - Next-Hop-Based Dynamic Tunnels
play_arrow MPLS Traffic
- play_arrow Managing MPLS Traffic
- play_arrow Protecting MPLS Traffic
  - Node and Path Protection for MPLS LSPs
  - Link Protection for MPLS LSPs
- play_arrow Measuring MPLS Traffic
  - Gather Statistics on MPLS Sessions
play_arrow MPLS LSPs
- play_arrow Understanding MPLS LSPs
- play_arrow Configuring MPLS LSPs
play_arrow MPLS Signalling Protocols
- play_arrow RSVP
  - RSVP Overview
  - RSVP Configuration
- play_arrow LDP
play_arrow MPLS Traffic Engineering
- play_arrow Configuring MPLS Traffic Engineering
play_arrow MPLS Transport Profile
- play_arrow Operation, Administration, and Maintenance (OAM) for MPLS
  - MPLS OAM Configuration
- play_arrow MPLS Pseudowires
  - MPLS Pseudowires Configuration
  - Pseudowire Headend Termination (PWHT) Configuration
- play_arrow Class-of-Service (CoS) for MPLS
  - MPLS Class-of-Service Configuration
- play_arrow Generalized MPLS (GMPLS)
  - GMPLS Configuration
play_arrow MPLS VPNs and Circuits
- play_arrow Ethernet over MPLS (L2 Circuit)
  - Understanding Ethernet-over-MPLS (L2 Circuit)
  - Configuring Ethernet over MPLS (Layer 2 Circuit)
- play_arrow CCC, TCC, and Layer 2.5 Switching
  - CCC, TCC, and Ethernet Over MPLS Configuration
play_arrow MPLS for Software Defined Networking (SDN)
- play_arrow Path Computation Element Protocol (PCEP)
  - PCEP Configuration
play_arrow MPLS Troubleshooting
- play_arrow Troubleshooting MPLS
  - Troubleshooting MPLS
play_arrow Configuration Statements and Operational Commands
- Junos CLI Reference Overview

list Table of Contents

English

MPLS on Provider and Provider Edge Devices Configuration

date_range 20-Dec-24

arrow_backward

arrow_forward

Configuring MPLS on Provider Switches

To implement MPLS, you must configure at least one provider switch as a transit switch for the MPLS packets.

MPLS requires the configuration of an interior gateway protocol (OSPF) and a signaling protocol (RSVP) on the core interfaces and the loopback interface of all the switches. This procedure includes the configuration of OSPF on the provider switch.

To configure the provider switch, complete the following tasks:

Configure OSPF on the loopback and core interfaces:

Note:

You can use the switch address as an alternative to the loopback interface.

content_copy zoom_out_map
[edit protocols ospf]
user@switch# set area 0.0.0.0 interface lo0.0
user@switch# set area 0.0.0.0 interface xe-0/0/5.0
user@switch# set area 0.0.0.0 interface xe-0/0/6.0
user@switch# set area 0.0.0.0 interface ae0

Configure MPLS on the core interfaces:

content_copy zoom_out_map
[edit protocols mpls]
user@switch# set interface xe-0/0/5.0
user@switch# set interface xe-0/0/6.0
user@switch# set interface ae0

Configure RSVP on the loopback interface and the core interfaces:

content_copy zoom_out_map
[edit protocols rsvp]
user@switch# set interface lo0.0
user@switch# set interface xe-0/0/5.0
user@switch# set interface xe-0/0/6.0
user@switch# set interface ae0

Configure an IP address for the loopback interface and the core interfaces:

content_copy zoom_out_map
[edit interfaces]
user@switch# set lo0 unit 0 family inet address 127.1.1.1/32
user@switch# set xe-0/0/5 unit 0 family inet address 10.1.5.1/24
user@switch# set xe-0/0/6 unit 0 family inet address 10.1.6.1/24
user@switch# set ae0 unit 0 family inet address 10.1.9.2/24

Configure family mpls on the logical units of the core interfaces, thereby identifying the interfaces that will be used for forwarding MPLS packets:
```
[edit interfaces]
user@switch# set xe-0/0/5 unit 0 family mpls
user@switch# set xe-0/0/6 unit 0 family mpls
user@switch# set ae0 unit 0 family mpls
```

Configuring MPLS on Provider Edge Switches

To implement MPLS, you must configure two provider edge (PE) switches—an ingress PE switch and an egress PE switch—and at least one provider switch. You can configure the customer edge (CE) interfaces on the PE switches of the MPLS network using IP over MPLS.

This topic describes how to configure an ingress PE switch and an egress PE switch using IP over MPLS:

Configuring the Ingress PE Switch
Configuring the Egress PE Switch

Configuring the Ingress PE Switch

To configure the ingress PE switch:

Configure an IP address for the loopback interface and the core interfaces:

content_copy zoom_out_map
[edit interfaces]
user@switch# set lo0 unit 0 family inet address 192.168.10.1/32
user@switch# set xe-0/0/5 unit 0 family inet address 10.1.5.1/24
user@switch# set xe-0/0/6 unit 0 family inet address 10.1.6.1/24

Note:

You cannot use routed VLAN interfaces (RVIs) or Layer 3 subinterfaces as core interfaces.

Configure OSPF on the loopback interface and the core interfaces:

Note:

You can use the switch address as an alternative to the loopback interface.

content_copy zoom_out_map
[edit protocols ospf]
user@switch# set area 0.0.0.0 interface lo0.0
user@switch# set area 0.0.0.0 interface xe-0/0/5.0
user@switch# set area 0.0.0.0 interface xe-0/0/6.0
                         

Configure OSPF traffic engineering:

content_copy zoom_out_map
[edit protocols ospf]
user@switch# set traffic-engineering

Configure RSVP on the loopback interface and the core interfaces:

content_copy zoom_out_map
[edit protocols rsvp]
user@switch# set interface lo0.0
user@switch# set interface xe-0/0/5.0
user@switch# set interface xe-0/0/6.0
                         

Configure MPLS traffic engineering.

content_copy zoom_out_map
[edit protocols mpls]
user@switch# set traffic-engineering

Configure MPLS on the core interfaces:

content_copy zoom_out_map
[edit protocols mpls]
user@switch# set interface xe-0/0/5.0
user@switch# set interface xe-0/0/6.0
                         

Configure family mpls on the logical units of the core interfaces, thereby identifying the interfaces that will be used for forwarding MPLS packets:
```
[edit interfaces]
user@switch# set xe-0/0/5 unit 0 family mpls
user@switch# set xe-0/0/6 unit 0 family mpls
```

Configure a customer edge interface as a Layer 3 routed interface, specifying an IP address:

content_copy zoom_out_map
[edit interfaces]
user@switch# set xe-0/0/3 unit 0 family inet address 121.100.10.1/16                         

Configure this Layer 3 customer edge interface for the routing protocol:
```
[edit]
user@switch# set protocols ospf area 0.0.0 interface xe-0/0/3.0
```
Configure an LSP on the ingress PE switch (192.168.10.1) to send IP packets over MPLS to the egress PE switch (192.168.12.1):
```
[edit protocols mpls]
user@switch# set label-switched-path lsp_1 to 192.168.12.1
```
Disable constrained-path LSP computation for this LSP:
```
[edit protocols mpls]
user@switch# set label-switched-path lsp_1 no-cspf
```
Configure a static route from the ingress PE switch to the egress PE switch, thereby indicating to the routing protocol that the packets will be forwarded over the MPLS LSP that has been set up to that destination:
```
[edit routing-options]
user@switch# set static route 2.2.2.0/24 next-hop 192.168.10.1
user@switch# set static route 2.2.2.0/24 resolve  
```

Configuring the Egress PE Switch

To configure the egress PE switch:

Configure an IP address for the loopback interface and the core interfaces:

content_copy zoom_out_map
[edit interfaces]
user@switch# set lo0 unit 0 family inet address 192.168.12.1/32
user@switch# set xe-0/0/5 unit 0 family inet address 10.1.20.1/24
user@switch# set xe-0/0/6 unit 0 family inet address 10.1.21.1/24   

Note:

You cannot use routed VLAN interfaces (RVIs) or Layer 3 subinterfaces as core interfaces.

Configure OSPF on the loopback interface and the core interfaces:

Note:

You can use the switch address as an alternative to the loopback interface.

content_copy zoom_out_map
[edit protocols ospf]
user@switch# set area 0.0.0.0 interface lo0.0
user@switch# set area 0.0.0.0 interface xe-0/0/5.0
user@switch# set area 0.0.0.0 interface xe-0/0/6.0
                         

Configure RSVP on the loopback interface and the core interfaces:

content_copy zoom_out_map
[edit protocols rsvp]
user@switch# set rsvp interface lo0.0
user@switch# set rsvp interface xe-0/0/5.0
user@switch# set rsvp interface xe-0/0/6.0
                         

Configure MPLS on the core interfaces:

content_copy zoom_out_map
[edit protocols mpls]
user@switch# set interface xe-0/0/5.0
user@switch# set interface xe-0/0/6.0

Configure family mpls on the logical units of the core interfaces, thereby identifying the interfaces that will be used for forwarding MPLS packets:
```
[edit interfaces]
user@switch# set xe-0/0/5 unit 0 family mpls
user@switch# set xe-0/0/6 unit 0 family mpls                         
```
Configure a customer edge interface as a Layer 3 routed interface, specifying an IP address:
```
[edit interfaces]
user@switch# set xe-0/0/3 unit 0 family inet address 2.2.2.1/16
```
Configure this Layer 3 customer edge interface for the routing protocol:
```
[edit]
user@switch# set protocols ospf area 0.0.0 interface xe-0/0/3
```
Configure an LSP on the egress PE switch (192.168.12.1) to send IP packets over MPLS to the ingress PE switch (192.168.10.1):
```
[edit protocols mpls]
user@switch# set label-switched-path lsp_2 to 192.168.10.1
```
Disable constrained-path LSP computation for this LSP:
```
[edit protocols mpls]
user@switch# set label-switched-path lsp_2 no-cspf 
```
Configure a static route from the ingress PE switch to the egress PE switch, thereby indicating to the routing protocol that the packets will be forwarded over the MPLS LSP that has been set up to that destination:
```
[edit routing-options]
user@switch# set static route 121.121.121.0/24 next-hop 192.168.12.1 
user@switch# set static route 121.121.121.0/24 resolve
```

Configuring MPLS on Provider Edge Switches Using IP-Over-MPLS

You can configure MPLS on EX Series switches to increase transport efficiency in your network. MPLS services can be used to connect various sites to a backbone network or to ensure better performance for low-latency applications such as VoIP and other business-critical functions.

To implement MPLS on switches, you must configure two provider edge (PE) switches—an ingress PE switch and an egress PE switch—and at least one provider switch. You can configure customer edge (CE) interfaces on the PE switches of the MPLS network by using either IP over MPLS or MPLS over circuit cross-connect (CCC).

The main differences between configuring IP over MPLS and configuring MPLS over CCC are that for IP over MLPS you configure the customer edge interfaces to belong to family inet (rather than family ccc) and you configure a static route for the label-switched path (LSP). The configuration of the provider switch is the same regardless of whether you have used IP over MPLS or MPLS over CCC. See Configuring MPLS on EX8200 and EX4500 Provider Switches.

This topic describes how to configure an ingress PE switch and an egress PE switch using IP over MPLS:

Configuring the Ingress PE Switch
Configuring the Egress PE Switch

Configuring the Ingress PE Switch

To configure the ingress PE switch:

Configure an IP address for the loopback interface and for the core interfaces:

content_copy zoom_out_map
[edit]
user@switch# set interfaces lo0 unit 0 family inet address 100.100.100.100/32
user@switch# set interfaces ge-0/0/5 unit 0 family inet address 10.1.5.1/24
user@switch# set interfaces ge-0/0/6 unit 0 family inet address 10.1.6.1/24                         

Configure OSPF on the loopback 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 ge-0/0/5.0
user@switch# set ospf area 0.0.0.0 interface ge-0/0/6.0
                         
```
Note:
If you want to use routed VLAN interfaces (RVIs) or Layer 3 subinterfaces as the core interfaces, replace ge-0/0/5.0 and ge-0/0/6 each with an RVI name (for example, vlan.logical-interface-number) or a subinterface name (for example, interface-name.logical-unit-number).

RVIs function as logical routers, eliminating the need to have both a switch and a router. Layer 3 subinterfaces allow you to route traffic among multiple VLANs along a single trunk line that connects an EX Series switch to a Layer 2 switch.

Enable traffic engineering for the routing protocol:

content_copy zoom_out_map
[edit protocols]
user@switch# set ospf traffic-engineering
                         

Configure RSVP on the loopback interface and the core interfaces:

content_copy zoom_out_map
[edit protocols]
user@switch# set rsvp interface lo0.0
user@switch# set rsvp interface ge-0/0/5.0
user@switch# set rsvp interface ge-0/0/6.0
                         

Configure MPLS traffic engineering:

content_copy zoom_out_map
[edit protocols]
user@switch# set protocols mpls traffic-engineering bgp-igp

Configure MPLS on the core interfaces:

content_copy zoom_out_map
[edit protocols]
user@switch# set mpls interface ge-0/0/5.0
user@switch# set mpls interface ge-0/0/6.0
                         

Configure family mpls on the logical units of the core interfaces, thereby identifying the interfaces that will be used for forwarding MPLS packets:

content_copy zoom_out_map
[edit]
user@switch# set interfaces ge-0/0/5 unit 0 family mpls                            
user@switch# set interfaces ge-0/0/6 unit 0 family mpls                         

Configure a customer edge interface as a Layer 3 routed interface, specifying an IP address:

content_copy zoom_out_map
[edit]
user@switch# set interfaces ge-2/0/3 unit 0 family inet 121.121.121.1/16                         

Configure this Layer 3 customer edge interface for the routing protocol:

content_copy zoom_out_map
[edit]
user@switch# set protocols ospf area 0.0.0 interface ge-2/0/3.0                                                

Configure an LSP on the ingress PE switch (100.100.100.100) to send IP packets over MPLS to the egress PE switch (208.208.208.208):

content_copy zoom_out_map
[edit protocols mpls]
user@switch# set label-switched-path ip_lspjavae_29 from 100.100.100.100 
user@switch# set label-switched-path ip_lspjavae_29 to 208.208.208.208

Disable constrained-path LSP computation for this LSP:

content_copy zoom_out_map
[edit protocols mpls]
user@switch# set label-switched-path ip_lspjavae_29 no-cspf

Configure a static route from the ingress PE switch to the egress PE switch, thereby indicating to the routing protocol that the packets will be forwarded over the MPLS LSP that has been set up to that destination:
Note:
Do not configure a static route if you are using this procedure to configure an MPLS-based Layer 3 VPN.
```
[edit]
user@switch# set routing-options static route 2.2.2.0/24 next-hop 100.100.100.100
user@switch# set routing-options static route 2.2.2.0/24 resolve  
```

Configuring the Egress PE Switch

To configure the egress PE switch:

Configure an IP address for the loopback interface and for the core interfaces:

content_copy zoom_out_map
[edit]
user@switch# set interfaces lo0 unit 0 family inet address 208.208.208.208/32
user@switch# set interfaces ge-0/0/5 unit 0 family inet address 10.1.20.1/24
user@switch# set interfaces ge-0/0/6 unit 0 family inet address 10.1.21.1/24   

Configure OSPF on the loopback interface (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 ge-0/0/5.0
user@switch# set ospf area 0.0.0.0 interface ge-0/0/6.0
                         
```
Note:
If you want to use routed VLAN interfaces (RVIs) or Layer 3 subinterfaces as the core interfaces, replace ge-0/0/5.0 and ge-0/0/6 each with an RVI name (for example, vlan.logical-interface-number) or a subinterface name (for example, interface-name.logical-unit-number).

RVIs function as logical routers, eliminating the need to have both a switch and a router. Layer 3 subinterfaces allow you to route traffic among multiple VLANs along a single trunk line that connects an EX Series switch to a Layer 2 switch.

Enable traffic engineering for the routing protocol:

content_copy zoom_out_map
[edit protocols]
user@switch# set ospf traffic-engineering
                         

Configure RSVP on the loopback interface and the core interfaces:

content_copy zoom_out_map
[edit protocols]
user@switch# set rsvp interface lo0.0
user@switch# set rsvp interface ge-0/0/5.0
user@switch# set rsvp interface ge-0/0/6.0
                         

Configure MPLS traffic engineering on both BGP and IGP destinations:
```
[edit protocols]
user@switch# set protocols mpls traffic-engineering bgp-igp
```

Configure MPLS on the core interfaces:

content_copy zoom_out_map
[edit protocols]
user@switch# set mpls interface ge-0/0/5.0
user@switch# set mpls interface ge-0/0/6.0                         

Configure family mpls on the logical units of the core interfaces, thereby identifying the interfaces that will be used for forwarding MPLS packets:

content_copy zoom_out_map
[edit]
user@switch# set interfaces ge-0/0/5 unit 0 family mpls
user@switch# set interfaces ge-0/0/6 unit 0 family mpls                         

Configure a customer edge interface as a Layer 3 routed interface, specifying an IP address:

content_copy zoom_out_map
[edit]
user@switch# set interfaces ge-2/0/3 unit 0 family inet address 2.2.2.1/16                           

Configure this Layer 3 customer edge interface for the routing protocol:

content_copy zoom_out_map
[edit]
user@switch# set protocols ospf area 0.0.0 interface ge-2/0/3                         

Configure an LSP on the egress PE switch (208.208.208.208) to send IP packets over MPLS to the ingress PE switch (100.100.100.100):

content_copy zoom_out_map
[edit protocols mpls]
user@switch# set label-switched-path ip_lsp29_javae from 208.208.208.208 
user@switch# set label-switched-path ip_lsp29_javae to 100.100.100.100

Disable constrained-path LSP computation for this LSP:

content_copy zoom_out_map
[edit protocols mpls]
user@switch# set label-switched-path ip_lsp29_javae no-cspf 

Configure a static route from the ingress PE switch to the egress PE switch, thereby indicating to the routing protocol that the packets will be forwarded over the MPLS LSP that has been set up to that destination:
Note:
Do not configure a static route if you are using this procedure to configure an MPLS-based Layer 3 VPN.
```
[edit]
user@switch# set routing-options static route 121.121.121.0/24 next-hop 208.208.208.208 
user@switch# set routing-options static route 121.121.121.0/24 resolve
```

Configuring MPLS on Provider Edge EX8200 and EX4500 Switches Using Circuit Cross-Connect

Junos OS MPLS for EX8200 and EX4500 switches supports Layer 2 protocols and Layer 2 virtual private networks (VPNs). You can configure MPLS on switches to increase transport efficiency in your network. MPLS services can be used to connect various sites to a backbone network and to ensure better performance for low-latency applications such as VoIP and other business-critical functions.

This topic describes configuring provider edge (PE) switches in an MPLS network using a circuit cross-connect (CCC). The customer edge interface can be either a simple interface or a tagged VLAN interface.

Note:

If you are configuring a CCC on a tagged VLAN interface, you do not specify family ccc. See Configuring an MPLS-Based VLAN CCC Using a Layer 2 VPN and Configuring an MPLS-Based VLAN CCC Using a Layer 2 Circuit.

Note:

If you are going through this procedure in preparation for configuring an MPLS-based Layer 2 VPN, you do not need to configure the association of the label-switched path (LSP) with the customer edge interface. The BGP signaling automates the connections, so manual configuration of the connections is not required.

The following guidelines apply to CCC configurations:

When an interface is configured to belong to family ccc, it cannot belong to any other family.
You can send any kind of traffic over a CCC, including nonstandard bridge protocol data units (BPDUs) generated by other vendors’ equipment.
If you are configuring a CCC on a tagged VLAN interface, you must explicitly enable VLAN tagging and specify a VLAN ID. The VLAN ID cannot be configured on logical interface unit 0. The logical unit number must be 1 or higher. See Configuring an MPLS-Based VLAN CCC Using a Layer 2 VPN and Configuring an MPLS-Based VLAN CCC Using a Layer 2 Circuit.

This procedure shows how to set up two CCCs:

If you are configuring a CCC on a simple interface (ge-0/0/1), you do not need to enable VLAN tagging or specify a VLAN ID, so you skip those steps.
If you are configuring a CCC on a tagged VLAN interface (ge-0/0/2), include all the steps in this procedure.

To configure a PE switch with a CCC:

Configure OSPF (or IS-IS) on the loopback (or switch address) and core interfaces:

content_copy zoom_out_map
[edit protocols]
user@switch# set ospf area 0.0.0.0 interface lo0.0
user@switch# set ospf area 0.0.0.0 interface ge-0/0/5.0
user@switch# set ospf area 0.0.0.0 interface ge-0/0/6.0
user@switch# set ospf area 0.0.0.0 interface ae0
                         

Enable traffic engineering for the routing protocol:

content_copy zoom_out_map
[edit protocols]
user@switch# set ospf traffic-engineering
                         

Configure an IP address for the loopback interface and for the core interfaces:

content_copy zoom_out_map
[edit]
user@switch# set interfaces lo0 unit 0 family inet address 127.1.1.1/32
user@switch# set interfaces ge-0/0/5 unit 0 family inet address 10.1.5.1/24
user@switch# set interfaces ge-0/0/6 unit 0 family inet address 10.1.6.1/24
user@switch# set interfaces ae0 unit 0 family inet address 10.1.9.1/24                         

Enable MPLS and define the LSP:

content_copy zoom_out_map
[edit protocols]
user@switch# set mpls                                 label-switched-path lsp_to_pe2_ge1 to 127.1.1.3
                         

Tip:

lsp_to_pe2_ge1 is the LSP name. You will need to use the specified name again when configuring the CCC.

Configure MPLS on the core interfaces:

content_copy zoom_out_map
[edit protocols]
user@switch# set mpls interface ge-0/0/5.0
user@switch# set mpls interface ge-0/0/6.0
user@switch# set mpls interface ae0
                         

Configure RSVP on the loopback interface and the core interfaces:

content_copy zoom_out_map
[edit protocols]
user@switch# set rsvp interface lo0.0
user@switch# set rsvp interface ge-0/0/5.0
user@switch# set rsvp interface ge-0/0/6.0
user@switch# set rsvp interface ae0
                         

Configure family mpls on the logical units of the core interfaces:
```
[edit]
user@switch# set interfaces ge-0/0/5 unit 0 family mpls
user@switch# set interfaces ge-0/0/6 unit 0 family mpls
user@switch# set interfaces ae0 unit 0 family mpls                         
```
Note:
You can enable family mpls on either individual interfaces or aggregated Ethernet interfaces. You cannot enable it on tagged VLAN interfaces.
If you are configuring a CCC on a tagged VLAN interface, enable VLAN tagging on the customer edge interface ge-0/0/2 of the local PE switch:
```
[edit interfaces ge-0/0/2]
user@switch# set vlan-tagging                                                      
```
If you are configuring a CCC on a simple interface (ge-0/0/1), omit this step.
If you are configuring a CCC on a tagged VLAN interface, configure the logical unit of the customer edge interface with a VLAN ID:
```
[edit interfaces ge-0/0/2 unit 1]
user@switch# set vlan-id 100                         
```
If you are configuring a CCC on a simple interface (ge-0/0/1), omit this step.

Configure the logical unit of the customer edge interface to belong to family ccc:

On a simple interface:

content_copy zoom_out_map
[edit interfaces ge-0/0/1 unit 0]
user@switch# set family ccc                         

On a tagged VLAN interface:

content_copy zoom_out_map
[edit interfaces ge-0/0/2 unit 1]
user@switch# set family ccc                         

Associate the CCC interface with two LSPs, one for transmitting MPLS packets and the other for receiving MPLS packets:
Note:
If you are configuring a Layer 2 VPN, omit this step. The BGP signaling automates the connections, so manual configuration of the connections is not required.
- On a simple interface:
  [edit protocols] user@switch# set connections remote-interface-switch ge-1-to-pe2 interface ge-0/0/1.0 user@switch# set connections remote-interface-switch ge-1-to-pe2 transmit-lsp lsp_to_pe2_ge1 user@switch# set connections remote-interface-switch ge-1-to-pe2 receive-lsp lsp_to_pe1_ge1
- On a tagged VLAN interface:
  [edit protocols] user@switch# set connections remote-interface-switch ge-1-to-pe2 interface ge-0/0/2.1 user@switch# set connections remote-interface-switch ge-1-to-pe2 transmit-lsp lsp_to_pe2_ge1 user@switch# set connections remote-interface-switch ge-1-to-pe2 receive-lsp lsp_to_pe1_ge1
Tip:
The transmit-lsp option specifies the LSP name that was configured on PE-1 (the local PE switch) by the label-switched-path statement within the [edit protocols mpls] hierarchy. The receive-lsp option specifies the LSP name that was configured on PE-2 (the remote PE switch) by the label-switched-path statement within the [edit protocols mpls] hierarchy.

When you have completed configuring one PE switch, follow the same procedures to configure the other PE switch.

Configuring MPLS on EX8200 and EX4500 Provider Switches

You can configure MPLS on EX8200 and EX4500 switches to increase transport efficiency in your network. MPLS services can be used to connect various sites to a backbone network and to ensure better performance for low-latency applications such as VoIP and other business-critical functions.

To implement MPLS on EX Series switches, you must configure at least one provider switch as a transit switch for the MPLS packets. The configuration of all the provider switches remains the same regardless of whether the provider edge (PE) switches are using circuit cross-connect (CCC) or using MPLS over IP for the customer edge interfaces. Likewise, you do not need to change the configuration of the provider switches if you implement an MPLS-based Layer 2 VPN, Layer 3 VPN, or a Layer 2 circuit configuration.

MPLS requires the configuration of a routing protocol (OSPF or IS-IS) on the core interfaces and the loopback interface of all the switches. This procedure includes the configuration of OSPF on the provider switch. For information on configuring IS-IS as the routing protocol, see Junos OS Routing Protocols Configuration Guide.

To configure the provider switch, complete the following tasks:

Enable the routing protocol (OSPF or IS-IS) on the loopback interface and on the core interfaces:

Note:

You can use the switch address as an alternative to the loopback interface.

content_copy zoom_out_map
[edit protocols]
user@switch# set ospf area 0.0.0.0  interface lo0.0
user@switch# set ospf area 0.0.0.0  interface ge-0/0/5.0
user@switch# set ospf area 0.0.0.0 interface ge-0/0/6.0
user@switch# set ospf area 0.0.0.0  interface ae0

Enable traffic engineering for the routing protocol (traffic engineering must be explicitly enabled for OSPF):
```
[edit protocols]
user@switch# set ospf traffic-engineering 
```

Enable MPLS within the protocols stanza and apply it to the core interfaces:

content_copy zoom_out_map
[edit protocols]
user@switch# set mpls interface ge-0/0/5.0
user@switch# set mpls interface ge-0/0/6.0
user@switch# set mpls interface ae0

Configure RSVP on the loopback interface and the core interfaces:

content_copy zoom_out_map
[edit protocols]
user@switch# set rsvp interface lo0.0
user@switch# set rsvp interface ge-0/0/5.0
user@switch# set rsvp interface ge-0/0/6.0
user@switch# set rsvp interface ae0

Configure an IP address for the loopback interface and for the core interfaces:

content_copy zoom_out_map
[edit]
user@switch# set interfaces lo0 unit 0 family inet address 127.1.1.1/32
user@switch# set interfaces ge-0/0/5 unit 0 family inet address 10.1.5.1/24
user@switch# set interfaces ge-0/0/6 unit 0 family inet address 10.1.6.1/24
user@switch# set interfaces ae0 unit 0 family inet address 10.1.9.2/24

Configure family mpls on the logical units of the core interfaces:
```
[edit]
user@switch# set interfaces ge-0/0/5 unit 0 family mpls
user@switch# set interfaces ge-0/0/6 unit 0 family mpls
user@switch# set interfaces ae0 unit 0 family mpls
```
Note:
You can enable family mpls on either individual interfaces or aggregated Ethernet interfaces. You cannot enable it on tagged VLAN interfaces.

arrow_backward PREVIOUS Basic MPLS Configuration

NEXT arrow_forward MPLS Configuration on IRB Interfaces

MPLS Applications User Guide

ON THIS PAGE

MPLS on Provider and Provider Edge Devices Configuration

Configuring MPLS on Provider Switches

Configuring MPLS on Provider Edge Switches

Configuring the Ingress PE Switch

Configuring the Egress PE Switch

Configuring MPLS on Provider Edge Switches Using IP-Over-MPLS

Configuring the Ingress PE Switch

Configuring the Egress PE Switch

Configuring MPLS on Provider Edge EX8200 and EX4500 Switches Using Circuit Cross-Connect

Configuring MPLS on EX8200 and EX4500 Provider Switches

Stay in touch

Helped me install or use the product
Accelerated my deployment

Discuss the product with a co-worker
Make a purchase inquiry

MPLS Applications User Guide

ON THIS PAGE

MPLS on Provider and Provider Edge Devices Configuration

Configuring MPLS on Provider Switches

Configuring MPLS on Provider Edge Switches

Configuring the Ingress PE Switch

Configuring the Egress PE Switch

Configuring MPLS on Provider Edge Switches Using IP-Over-MPLS

Configuring the Ingress PE Switch

Configuring the Egress PE Switch

Configuring MPLS on Provider Edge EX8200 and EX4500 Switches Using Circuit Cross-Connect

Configuring MPLS on EX8200 and EX4500 Provider Switches

Related Documentation

Stay in touch