MPLS on Provider and Provider Edge Devices Configuration
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:
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
To configure the ingress PE switch:
Configuring the Egress PE Switch
To configure the egress PE switch:
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
To configure the ingress PE switch:
Configuring the Egress PE Switch
To configure the egress PE switch:
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.
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.
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:
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: