Table of Contents
Advertisement
MPLS and RSVP-TE
3.18 MPLS Configuration Overview
MPLS enables routers to forward traffic based on a label embedded in the packet
header. A router examines the label to determine the next hop for the packet, instead
of router address lookups to the next node when forwarding packets.
To implement MPLS on an LSP for outer tunnel and pseudowire assignment, the
following entities must be configured:
3.18.1 Router Interface
At least one router interface and one system interface must be defined in the
config>router>interface context in order to configure MPLS on an interface.
3.18.1.1
An EXP-inferred LSP (E-LSP) is an LSP that can support a variety of VLLs or traffic
types. Up to eight types of traffic can be multiplexed over an E-LSP.
The prioritization of mission-critical traffic is handled by the settings of the three EXP
bits. The EXP bits designate the importance of a particular packet. The classification
and queuing at the Provider (P) or Provider Edge (PE) nodes typically take place
based on the value of the EXP bits. Refer to the 7705 SAR Quality of Service Guide
for more information on the use of EXP bits and differentiated services on the
7705 SAR.
3.18.2 Paths
To configure signaled LSPs, you must first create one or more named paths on the
ingress router using the config>router>mpls>path command. For each path, the
transit routers (hops) in the path are specified.
128
•
Router Interface
•
Paths
•
LSPs
•
Pseudowires
•
Signaling Protocol
(for RSVP-TE or LDP)
E-LSP for Differentiated Services
Use subject to Terms available at: www.nokia.com
© 2022 Nokia.
MPLS Guide
3HE 18686 AAAB TQZZA
Advertisement
Table of Contents
