Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

Configuring the Maximum Number of MPLS Labels

By default, the maximum number of labels is three. You can change the maximum to four labels or five labels for applications that require four or five labels. For example, suppose you configure a two-tier carrier-of-carriers VPN service for customers who provide VPN service. A carrier-of-carrier VPN is a two-tiered relationship between a provider carrier (Tier 1 ISP) and a customer carrier (Tier 2 ISP). In a carrier-of-carrier VPN, the provider carrier provides a VPN backbone network for the customer carrier. The customer carrier in turn provides Layer 3 VPN service to its end customers. The customer carrier sends labeled traffic to the provider carrier to deliver it to the next hop on the other side of the provider carrier’s network. This scenario requires a three-label stack: one label for the provider carrier VPN, another label for the customer carrier VPN, and a third label for the transport route.

If you add fast reroute service, the PE routers in the provider carrier’s network must be configured to support a fourth label (the reroute label). If the customer carrier is using LDP as its signaling protocol and the provider carrier is using RSVP, the provider carrier must support LDP over RSVP tunnel service. This additional service requires an additional label, for a total of five labels.

To the customer carrier, the router it uses to connect to the provider carrier’s VPN is a PE router. However, the provider carrier views this device as a CE router.

Table 1 summarizes the label requirements.

The system reserves label space when you configure the maximum number of labels on the interface. When you configure features that require MPLS labels, the label push is automatic. You do not need to explicitly push the labels. The transport route can be a static, LDP-signaled, or RSVP-signaled LSP.

• MX Series 3D Universal Edge Router
• M120 Multiservice Edge Router
• M320 Multiservice Edge Router with Enhanced III FPCs
• M7i Multiservice Edge Router and M10i Multiservice Edge Router with Enhanced Compact Forwarding Engine Board (CFEB-E)
• T640, T1600, TX Matrix, and TX Matrix Plus routers with Enhanced Scaling FPC1, Enhanced Scaling FP2, Enhanced Scaling FPC3, and Enhanced Scaling FPC4.

1. Specify the maximum on the logical interface. Apply this configuration to the carrier’s PE routers.
   [edit interfaces ge-0/1/3 unit 0 family mpls]
user@switch# set maximum-labels 5
2. Verify the configuration.
   [edit system]
user@switch# show interfaces ge-0/1/3.0

   Logical interface ge-0/1/3.0 (Index 77) (SNMP ifIndex 507) 
       Flags: SNMP-Traps Encapsulation: ENET2
       Input packets : 0 
       Output packets: 0
       Protocol mpls, MTU: 1480, Maximum labels: 5
         Flags: Is-Primary

   The command output includes the Maximum labels: 5 field under the logical interface unit 0.