Technical Documentation

Junos MPLS for EX Series Switches Overview

You can configure Junos MPLS on Juniper Networks EX Series Ethernet Switches to increase transport efficiency in the 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.

Junos MPLS for EX Series switches supports:

  • Layer 2 protocols
  • Layer 2 VPNs
  • RSVP-based label-switched paths (LSPs)
  • MPLS-based circuits cross-connect (CCCs)
  • IP over MPLS
  • Class of service (CoS)

Note: MPLS configurations on EX Series switches are compatible with configurations on other Juniper Networks devices that support MPLS and CCC.

Benefits of MPLS

MPLS has the following advantages over conventional packet forwarding:

  • Packets arriving on different ports can be assigned different labels.
  • A packet arriving at a particular provider edge switch may be assigned a label that is different from that of the same packet entering the network at a different provider edge switch. As a result, forwarding decisions that depend on the ingress provider edge switch can be easily made.
  • Sometimes it is desirable to force a packet to follow a particular route that is explicitly chosen at or before the time the packet enters the network, rather than letting it follow the route chosen by the normal dynamic routing algorithm as the packet travels through the network. In MPLS, a label can be used to represent the route so that the packet need not carry the identity of the explicit route.

Note: MPLS configurations on EX Series switches do not support:

  • LDP-based MPLS
  • Routed VLAN interfaces (RVIs)
  • Q-in-Q tunneling
  • Aggregated Ethernet interfaces (LAGs) on CCCs
  • CCCs with a beginning and ending on the same switch

Additional Benefits of MPLS and Traffic Engineering

MPLS is the packet-forwarding component of the Junos traffic engineering architecture. Traffic engineering provides the capabilities to do the following:

  • Route primary paths around known bottlenecks or points of congestion in the network.
  • Provide precise control over how traffic is rerouted when the primary path is faced with single or multiple failures.
  • Provide efficient use of available aggregate bandwidth and long-haul fiber by ensuring that certain subsets of the network are not overutilized while other subsets of the network along potential alternate paths are underutilized.
  • Maximize operational efficiency.
  • Enhance the traffic-oriented performance characteristics of the network by minimizing packet loss, minimizing prolonged periods of congestion, and maximizing throughput.
  • Enhance statistically bound performance characteristics of the network (such as loss ratio, delay variation, and transfer delay) required to support a multiservice Internet.

Published: 2010-06-25

|
|