• Supported Platforms
• EX Series

• Related Topics
• Example: Configuring MPLS on EX Series Switches
• Configuring MPLS on Provider Switches (CLI Procedure)
• Configuring an OSPF Network (J-Web Procedure)
• Verifying That MPLS Is Working Correctly
• Understanding JUNOS MPLS Components for EX Series Switches

Configuring MPLS on Provider Edge Switches Using IP Over MPLS (CLI Procedure)

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 EX Series 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 the customer-edge interfaces on the PE switches of the MPLS network as either circuit cross-connect (CCC) or using IP over MPLS.

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 the PE switches are configured for MPLS over CCC or IP over MPLS. See Configuring MPLS on Provider Switches (CLI Procedure).

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

1. Configuring the Ingress PE Switch
2. Configuring the Egress PE Switch

Configuring the Ingress PE Switch

To configure the ingress PE switch:

1. 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 ge-0/0/5.0
user@switch# set ospf area 0.0.0.0 interface ge-0/0/6.0

2. Enable traffic engineering for the routing protocol:
   
   

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

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

   [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
4. Configure MPLS on the core interfaces:
   
   

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

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

   [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
6. Configure RSVP on the loopback interface and the core interfaces:
   
   

   [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

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

   [edit]
user@switch# set interfaces ge-2/0/3 unit 0 family inet 121.121.121.1/16
8. Configure this Layer 3 customer-edge interface for the routing protocol:
   
   

   [edit]
user@switch# set protocols ospf area 0.0.0 interface ge-2/0/3.0
9. 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):
   
   

   [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
10. Disable constrained-path LSP computation for this LSP:
    
    

    [edit protocols mpls]
user@switch# set label-switched-path ip_lspjavae_29 no-cspf
11. 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]
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:

1. Configure OSPF (or IS-IS) 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

2. Enable traffic engineering for the routing protocol:
   
   

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

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

   [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
4. Configure MPLS on the core interfaces:
   
   

   [edit protocols]
user@switch# set mpls interface ge-0/0/5.0
user@switch# set mpls interface ge-0/0/6.0
5. Configure family mpls on the logical units of the core interfaces, thereby identifying the interfaces that will be used for forwarding MPLS packets:
   
   

   [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
6. Configure RSVP on the loopback interface and the core interfaces:
   
   

   [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

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

   [edit]
user@switch# set interfaces ge-2/0/3 unit 0 family inet address 2.2.2.1/16
8. Configure this Layer 3 customer-edge interface for the routing protocol:
   
   

   [edit]
user@switch# set protocols ospf area 0.0.0 interface ge-2/0/3
9. 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):
   
   

   [edit protocols mpls]
user@switch# set label-switched-path ip_lsp29_javae from 208.208.208.208
user@switch# set label-switched-path ip_lspjavae_29 to 100.100.100.100
10. Disable constrained-path LSP computation for this LSP:
    
    

    [edit protocols mpls]
user@switch# set label-switched-path ip_lsp29_javae no-cspf
11. 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]
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