MPLS Basic MPLS Configuration Guide

First Published: 2013-07-24

Last Modified: 2013-07-24

Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS,
INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH
THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY,
CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version of
the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS" WITH ALL FAULTS.
CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT
LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS
HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network
topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional
and coincidental.

All printed copies and duplicate soft copies of this document are considered uncontrolled. See the current online version for the latest version.

Cisco has more than 200 offices worldwide. Addresses and phone numbers are listed on the Cisco website at www.cisco.com/go/offices.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL:
https://www.cisco.com/c/en/us/about/legal/trademarks.html. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a
partnership relationship between Cisco and any other company. (1721R)
© 2013 Cisco Systems, Inc. All rights reserved.
 CONTENTS

CHAPTER 1 Read Me First 1

Short Description 2

CHAPTER 2 MPLS Transport Profile 3

Finding Feature Information 3

Restrictions for MPLS Transport Profile 3
Information About MPLS-TP 5
How MPLS Transport Profile Works 5
MPLS-TP Path Protection 5
Bidirectional LSPs 5
Support for MPLS Transport Profile OAM 6
MPLS Transport Profile Static and Dynamic Multisegment Pseudowires 7
MPLS-TP OAM Status for Static and Dynamic Multisegment Pseudowires 7
MPLS Transport Profile Links and Physical Interfaces 7
Tunnel Midpoints 7
How to Configure MPLS Transport Profile 8
Configuring the MPLS Label Range 8
Configuring the Router ID and Global ID 9
Configuring Bidirectional Forwarding Detection Templates 10
Configuring Pseudowire OAM Attributes 11
Configuring the Pseudowire Class 12
Configuring the Pseudowire 13
Configuring the MPLS-TP Tunnel 15
Configuring MPLS-TP LSPs at Midpoints 17
Configuring MPLS-TP Links and Physical Interfaces 19
Configuring Static-to-Static Multisegment Pseudowires for MPLS-TP 21

MPLS Basic MPLS Configuration Guide

iii
 Contents

Configuring a Template with Pseudowire Type-Length-Value Parameters 23

Configuring Static-to-Dynamic Multisegment Pseudowires for MPLS-TP 23
Verifying the MPLS-TP Configuration 26
Configuration Examples for MPLS Transport Profile 27
Example: Configuring Static-to-dynamic Multisegment Pseudowires for MPLS-TP 27
Additional References for MPLS Transport Profile 27
Feature Information for MPLS Transport Profile 28

CHAPTER 3 Multiprotocol Label Switching (MPLS) on Cisco Routers 29

Information About MPLS 29

MPLS Overview 29
Functional Description of MPLS 30
Label Switching Functions 30
Distribution of Label Bindings 30
Benefits of MPLS 31
How to Configure MPLS 32
Configuring a Router for MPLS Switching 32
Verifying Configuration of MPLS Switching 32
Configuring a Router for MPLS Forwarding 33
Verifying Configuration of MPLS Forwarding 34
Additional References 35
Feature Information for MPLS on Cisco Routers 36
Glossary 36

CHAPTER 4 MPLS Infrastructure Changes Introduction of MFI and Removal of MPLS LSC and LC-ATM
Features 39

Finding Feature Information 39

Information About MPLS Infrastructure Changes 39
Introduction of the MPLS Forwarding Infrastructure 39
Introduction of IP Rewrite Manager 40
MPLS LSC and LC-ATM Configurations 40
Additional References 40
Feature Information for MPLS Infrastructure Changes 41

MPLS Basic MPLS Configuration Guide

iv
 Contents

CHAPTER 5 MPLS Static Labels 43

Finding Feature Information 43

Restrictions for MPLS Static Labels 43
Prerequisites for MPLS Static Labels 44
Information About MPLS Static Labels 44
MPLS Static Labels Overview 44
Benefits of MPLS Static Labels 44
How to Configure MPLS Static Labels 45
Configuring MPLS Static Prefix Label Bindings 45
Verifying MPLS Static Prefix Label Bindings 46
Configuring MPLS Static Crossconnects 47
Verifying MPLS Static Crossconnect Configuration 47
Monitoring and Maintaining MPLS Static Labels 48
Configuration Examples for MPLS Static Labels 49
Example Configuring MPLS Static Prefixes Labels 49
Example Configuring MPLS Static Crossconnects 50
Additional References 50
Feature Information for MPLS Static Labels 51
Glossary 52

CHAPTER 6 MPLS Multilink PPP Support 53

Finding Feature Information 53

Prerequisites for MPLS Multilink PPP Support 53
Information About MPLS Multilink PPP Support 54
MPLS Layer 3 Virtual Private Network Features Supported for Multilink PPP 54
MPLS Quality of Service Features Supported for Multilink PPP 55
MPLS Multilink PPP Support and PE-to-CE Links 55
MPLS Multilink PPP Support and Core Links 56
MPLS Multilink PPP Support in a CSC Network 57
MPLS Multilink PPP Support in an Interautonomous System 58
How to Configure MPLS Multilink PPP Support 58
Enabling Cisco Express Forwarding 58
Creating a Multilink Bundle 59

MPLS Basic MPLS Configuration Guide

v
 Contents

Assigning an Interface to a Multilink Bundle 61

Disabling PPP Multilink Fragmentation 63
Verifying the Multilink PPP Configuration 64
Configuration Examples for MPLS Multilink PPP Support 67
Example: Configuring Multilink PPP on an MPLS CSC PE Device 67
Example: Enabling Cisco Express Forwarding 68
Example: Creating a Multilink Bundle 69
Example: Assigning an Interface to a Multilink Bundle 69
Additional References for MPLS Multilink PPP Support 70
Feature Information for MPLS Multilink PPP Support 70
Glossary 71

CHAPTER 7 6PE Multipath 73

Finding Feature Information 73
Information About 6PE Multipath 73
6PE Multipath 73
How to Configure 6PE Multipath 74
Configuring IBGP Multipath Load Sharing 74
Configuration Examples for 6PE Multipath 75
Example: Configuring 6PE Multipath 75
Additional References 75
Feature Information for 6PE Multipath 76

CHAPTER 8 IPv6 Switching: Provider Edge Router over MPLS 77

Finding Feature Information 77

Prerequisites for IPv6 Switching: Provider Edge Router over MPLS 77
Information About IPv6 Switching: Provider Edge Router over MPLS 78
Benefits of Deploying IPv6 over MPLS Backbones 78
IPv6 on the Provider Edge Devices 78
How to Deploy IPv6 Switching: Provider Edge Router over MPLS 79
Deploying IPv6 on the Provider Edge Devices (6PE) 79
Specifying the Source Address Interface on a 6PE Device 79
Binding and Advertising the 6PE Label to Advertise Prefixes 81
Configuring IBGP Multipath Load Sharing 83

MPLS Basic MPLS Configuration Guide

vi
 Contents

Configuration Examples for IPv6 Switching: Provider Edge Router over MPLS 84
Example: Provider Edge Device 84
Example: Core Device 84
Example: Monitoring 6PE 85
Additional References for IPv6 Switching: Provider Edge Router over MPLS 86
Feature Information for IPv6 Switching: Provider Edge Router over MPLS 87

MPLS Basic MPLS Configuration Guide

vii
Contents

MPLS Basic MPLS Configuration Guide

viii
 CHAPTER 1
Read Me First
Important Information

Note For CUBE feature support information in Cisco IOS XE Bengaluru 17.6.1a and later releases, see Cisco
Unified Border Element IOS-XE Configuration Guide.

Note The documentation set for this product strives to use bias-free language. For purposes of this documentation
set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial
identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be
present in the documentation due to language that is hardcoded in the user interfaces of the product software,
language used based on standards documentation, or language that is used by a referenced third-party product.

Feature Information
Use Cisco Feature Navigator to find information about feature support, platform support, and Cisco software
image support. An account on Cisco.com is not required.

Related References
• Cisco IOS Command References, All Releases

Obtaining Documentation and Submitting a Service Request

• To receive timely, relevant information from Cisco, sign up at Cisco Profile Manager.
• To get the business impact you’re looking for with the technologies that matter, visit Cisco Services.
• To submit a service request, visit Cisco Support.
• To discover and browse secure, validated enterprise-class apps, products, solutions and services, visit
Cisco Marketplace.
• To obtain general networking, training, and certification titles, visit Cisco Press.
• To find warranty information for a specific product or product family, access Cisco Warranty Finder.

MPLS Basic MPLS Configuration Guide

1
 Read Me First
Short Description

• Short Description, on page 2

Short Description
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and
other countries. To view a list of Cisco trademarks, go to this URL: https://www.cisco.com/c/en/us/about/
legal/trademarks.html. Third-party trademarks mentioned are the property of their respective owners. The use
of the word partner does not imply a partnership relationship between Cisco and any other company. (1721R)

MPLS Basic MPLS Configuration Guide

2
 CHAPTER 2
MPLS Transport Profile
Multiprotocol Label Switching (MPLS) Transport Profile (TP) enables you to create tunnels that provide the
transport network service layer over which IP and MPLS traffic traverses. MPLS-TP tunnels enable a transition
from Synchronous Optical Networking (SONET) and Synchronous Digital Hierarchy (SDH) time-division
multiplexing (TDM) technologies to packet switching to support services with high bandwidth requirements,
such as video.
• Finding Feature Information, on page 3
• Restrictions for MPLS Transport Profile, on page 3
• Information About MPLS-TP, on page 5
• How to Configure MPLS Transport Profile, on page 8
• Configuration Examples for MPLS Transport Profile, on page 27
• Additional References for MPLS Transport Profile, on page 27
• Feature Information for MPLS Transport Profile, on page 28

Finding Feature Information

Your software release may not support all the features documented in this module. For the latest caveats and
feature information, see Bug Search Tool and the release notes for your platform and software release. To
find information about the features documented in this module, and to see a list of the releases in which each
feature is supported, see the feature information table at the end of this module.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support.
To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.

Restrictions for MPLS Transport Profile

• Multiprotocol Label Switching Transport Profile (MPLS-TP) penultimate hop popping is not supported.
Only ultimate hop popping is supported, because label mappings are configured at the MPLS-TP endpoints.
• Ethernet subinterfaces are not supported.
• IPv6 addressing is not supported.

L2VPN Restrictions
• Layer 2 Virtual Private Network (L2VPN) interworking is not supported.

MPLS Basic MPLS Configuration Guide

3
 MPLS Transport Profile
Restrictions for MPLS Transport Profile

• Local switching with Any Transport over MPLS (AToM) pseudowire as a backup is not supported.
• L2VPN pseudowire redundancy to an AToM pseudowire by one or more attachment circuits is not
supported.
• Pseudowire ID Forward Equivalence Class (FEC) type 128 is supported, but generalized ID FEC type
129 is not supported.
• Static pseudowire Operations, Administration, and Maintenance (OAM) protocol and BFD VCCV
attachment circuit (AC) status signaling are mutually exclusive protocols. Bidirectional Forwarding
Detection (BFD) and Virtual Circuit Connectivity Verification (VCCV) in failure detection mode can
be used with Static Pseudowire OAM protocol.
• BFD VCCV AC status signaling cannot be used in pseudowire redundancy configurations. You can use
Static Pseudowire OAM instead.

Ping and Trace Restrictions

• Ping for static pseudowires over MPLS-TP tunnels is not supported.
• Pseudowire ping and traceroute functionality for multisegment pseudowires that have one or more static
pseudowire segments is not supported.
• The following packet format is supported:
• A labeled packet with Generic Associated Channel Label (GAL) at the bottom of the label stack.
• ACH channel is IP (0x21).
• RFC-4379-based IP, UDP packet payload with valid source.
• Destination IP address and UDP port 3503.
• Default reply mode for (1) is 4—Reply via application level control channel is supported. An echo reply
consists of the following elements:
• A labeled packet with a GAL label at the bottom of the label stack.
• Associated Channel (ACh) is IP (0x21).
• RFC-4379-based IP, UDP packet payload with valid source.
• Destination IP address and UDP port 3503.
• The optional “do not reply” mode may be set.
• The following reply modes are not allowed and are disabled in CLI:
• 2—Reply via an IPv4/IPv6 UDP packet
• 3—Reply via an IPv4/IPv6 UDP packet with router alert
• Force-explicit-null is not supported with ping and trace.
• Optional Reverse Path Connectivity verification is not supported.

MPLS Basic MPLS Configuration Guide

4
 MPLS Transport Profile
Information About MPLS-TP

Information About MPLS-TP

How MPLS Transport Profile Works
Multiprotocol Label Switching Transport Profile (MPLS-TP) tunnels provide the transport network service
layer over which IP and MPLS traffic traverses. MPLS-TP tunnels help transition from Synchronous Optical
Network/Synchronous Digital Hierarchy (SONET/SDH) and Time Division Multiplexing (TDM) technologies
to packet switching to support services with high bandwidth utilization and lower cost. Transport networks
are connection-oriented, statically provisioned, and have long-lived connections. Transport networks usually
avoid control protocols that change identifiers (like labels). MPLS-TP tunnels provide this functionality
through statically provisioned bidirectional label switched paths (LSPs), as shown in the figure below.

MPLS-TP Path Protection

MPLS-TP label switched paths (LSPs) support 1-to-1 path protection. There are two types of LSPs: protect
LSPs and working LSPs. You can configure the both types of LSPs when configuring the MPLS-TP tunnel.
The working LSP is the primary LSP used to route traffic. The protect LSP acts as a backup for a working
LSP. If the working LSP fails, traffic is switched to the protect LSP until the working LSP is restored, at
which time forwarding reverts back to the working LSP.

Bidirectional LSPs
Multiprotocol Label Switching Transport Profile (MPLS-TP) label switched paths (LSPs) are bidirectional
and co-routed. They comprise of two unidirectional LSPs that are supported by the MPLS forwarding
infrastructure. A TP tunnel consists of a pair of unidirectional tunnels that provide a bidirectional LSP. Each
unidirectional tunnel can be optionally protected with a protect LSP that activates automatically upon failure
conditions.

MPLS Basic MPLS Configuration Guide

5
 MPLS Transport Profile
Support for MPLS Transport Profile OAM

Support for MPLS Transport Profile OAM

Several Operations, Administration, and Maintenance (OAM) protocols and messages support the provisioning
and maintenance of Multiprotocol Label Switching Transport Profile (MPLS-TP) tunnels and bidirectional
label switched paths (LSPs).
The following OAM messages are forwarded along the specified MPLS LSP:
• OAM Fault Management—Alarm Indication Signal (AIS), Link Down Indication (LDI), and Lock Report
(LKR) messages (GAL with BFD messages).
• OAM Connection Verification—Ping and traceroute messages (GAL with IP channel by default).
• OAM Continuity Check—Bidirectional Forwarding Detection (BFD) messages—non-IP BFD and IP
BFD (GAL with non-IP BFD channel or IP BFD channel depending on message format).
• The following messages are forwarded along the specified pseudowire:
• Static pseudowire OAM messages
• Pseudowire ping and traceroute messages
• BFD messages

• MPLS-TP OAM Fault Management (LDI, AIS, and LKR messages)—LDI messages are AIS messages
whose L-flags are set. The LDI messages are generated at midpoint nodes when a failure is detected.
From the midpoint, an LDI message is sent to the endpoint that is reachable with the existing failure.
Similarly, LKR messages are sent from a midpoint node to the reachable endpoint when an interface is
administratively shut down. By default, the reception of LDI and LKR messages on the active LSP at
an endpoint will cause a path protection switchover, whereas the reception of an AIS message will not.
• MPLS-TP OAM Fault Management with Emulated Protection Switching for LSP Lockout—Cisco
implements a form of Emulated Protection Switching to support LSP Lockout using customized Fault
messages. When a Lockout message is sent, it does not cause the LSP to be administratively down. The
Cisco Lockout message causes a path protection switchover and prevents data traffic from using the LSP.
The LSP remains administratively up so that BFD and other OAM messages can continue to traverse it
and so that maintenance of the LSP can take place (such as reconfiguring or replacing a midpoint LSR).
After OAM verifies the LSP connectivity, the Lockout is removed and the LSP is brought back to service.
Lockout of the working LSP is not allowed if a protect LSP is not configured. Conversely, the Lockout
of a protect LSP is allowed if a working LSP is not configured.
• LSP ping and trace—To verify MPLS-TP connectivity, use the ping mpls tp and trace mpls tp commands.
You can specify that echo requests be sent along the working LSP, the protect LSP, or the active LSP.
You can also specify that echo requests be sent on a locked-out MPLS-TP tunnel LSP (either working
or protected) if the working or protected LSP is explicitly specified. You can also specify ping/trace
messages with or without IP.
• MPLS-TP OAM Continuity Check (CC) via BFD and Remote Defect Indication (RDI)—RDI is
communicated via the BFD diagnostic field in BFD CC messages. BFD sessions run on both the working
LSP and the protect LSP. To perform a path protection switchover within 60 milliseconds on an MPLS-TP
endpoint, use the BFD Hardware Offload feature, which enables the router hardware to construct and
send BFD messages, removing the task from the software path. The BFD Hardware Offload feature is
enabled automatically on supported platforms.

MPLS-TP OAM GACH—Generic Associated Channel (G-ACh) is the control channel mechanism associated
with Multiprotocol Label Switching (MPLS) LSPs in addition to MPLS pseudowire. The G-ACh Label (GAL)
(Label 13) is a generic alert label to identify the presence of the G-ACh in the label packet. It is taken from

MPLS Basic MPLS Configuration Guide

6
 MPLS Transport Profile
MPLS Transport Profile Static and Dynamic Multisegment Pseudowires

the reserved MPLS label space. G-ACh/GAL supports OAMs of LSPs and in-band OAMs of pseudowires
(PWs). OAM messages are used for fault management, connection verification, continuity check, and so on.

MPLS Transport Profile Static and Dynamic Multisegment Pseudowires

Multiprotocol Label Switching Transport Profile (MPLS-TP) supports the following combinations of static
and dynamic multisegment pseudowires:
• Dynamic-static
• Static-dynamic
• Static-static

MPLS-TP OAM Status for Static and Dynamic Multisegment Pseudowires

With static pseudowires, status notifications can be provided by BFD over VCCV or by the static pseudowire
OAM protocol. However, BFD over VCCV sends only attachment circuit status code notifications. Hop-by-hop
notifications of other pseudowire status codes are not supported. Therefore, the static pseudowire OAM
protocol is preferred. You can acquire per pseudowire OAM for attachment circuit/pseudowire notification
over the VCCV channel with or without the control word.

MPLS Transport Profile Links and Physical Interfaces

Multiprotocol Label Switching Transport Profile (MPLS-TP) link numbers may be assigned to physical
interfaces only. Bundled interfaces and virtual interfaces are not supported for MPLS-TP link numbers.
The MPLS-TP link creates a layer of indirection between the MPLS-TP tunnel and midpoint LSP configuration
and the physical interface. The mpls tp link command is used to associate an MPLS-TP link number with a
physical interface and next-hop node. On point-to-point interfaces or Ethernet interfaces designated as
point-to-point using the medium p2p command, the next-hop can be implicit, so the mpls tp link command
just associates a link number to the interface.
Multiple tunnels and LSPs may then refer to the MPLS-TP link to indicate that they are traversing that interface.
You can move the MPLS-TP link from one interface to another without reconfiguring all the MPLS-TP tunnels
and LSPs that refer to the link.
Link numbers must be unique on the router or node.
See the section Configuring MPLS-TP Links and Physical Interfaces, on page 19, for more information.

Tunnel Midpoints
Tunnel LSPs, whether endpoint or midpoint, use the same identifying information. However, it is entered
differently.
• At the midpoint, all information for the LSP is specified with the mpls tp lsp command for configuring
forward and reverse information for forwarding.
• At the midpoint, determining which end is source and which is destination is arbitrary. That is, if you
are configuring a tunnel between your device and a coworker’s device, then your device is the source.
However, your coworker considers his or her device to be the source. At the midpoint, either device

MPLS Basic MPLS Configuration Guide

7
 MPLS Transport Profile
How to Configure MPLS Transport Profile

could be considered the source. At the midpoint, the forward direction is from source to destination, and
the reverse direction is from destination to source.
• At the endpoint, the local information (source) either comes from the global device ID and global ID, or
from the locally configured information using the tp source command.
• At the endpoint, the remote information (destination) is configured using the tp destination command
after you enter the interface tunnel-tp number command. The tp destination command includes the
destination node ID, and optionally the global ID and the destination tunnel number. If you do not specify
the destination tunnel number, the source tunnel number is used.
• At the endpoint, the LSP number is configured in working-lsp or protect-lsp submode. The default is 0
for the working LSP and 1 for the protect LSP.
• When configuring LSPs at midpoint devices, ensure that the configuration does not deflect traffic back
to the originating node.

How to Configure MPLS Transport Profile

Configuring the MPLS Label Range
You must specify a static range of Multiprotocol Label Switching (MPLS) labels using the mpls label range
command with the static keyword.

SUMMARY STEPS
1. enable
2. configure terminal
3. mpls label range minimum-value maximum-value static minimum-static-value maximum-static-value
4. end

DETAILED STEPS

Command or Action Purpose

Step 1 enable Enables privileged EXEC mode.
Example: • Enter your password if prompted.

Device> enable

Step 2 configure terminal Enters global configuration mode.

Example:

Device# configure terminal

Step 3 mpls label range minimum-value maximum-value static Specifies a static range of MPLS labels.
minimum-static-value maximum-static-value
Example:

MPLS Basic MPLS Configuration Guide

8
 MPLS Transport Profile
Configuring the Router ID and Global ID

Command or Action Purpose

Device(config)# mpls label range 1001 1003 static

10000 25000

Step 4 end Exits global configuration mode and returns to privileged

EXEC mode.
Example:

Device(config)# end

Configuring the Router ID and Global ID

SUMMARY STEPS
1. enable
2. configure terminal
3. mpls tp
4. router-id node-id
5. global-id num
6. end

DETAILED STEPS

Command or Action Purpose

Step 1 enable Enables privileged EXEC mode.
Example: • Enter your password if prompted.

Device> enable

Step 2 configure terminal Enters global configuration mode.

Example:

Device# configure terminal

Step 3 mpls tp Enters MPLS-TP configuration mode, from which you can
configure MPLS-TP parameters for the device.
Example:

Device(config)# mpls tp

Step 4 router-id node-id Specifies the default MPLS-TP router ID, which is used as
the default source node ID for all MPLS-TP tunnels
Example:
configured on the device.
Device(config-mpls-tp)# router-id 10.10.10.10

MPLS Basic MPLS Configuration Guide

9
 MPLS Transport Profile
Configuring Bidirectional Forwarding Detection Templates

Command or Action Purpose

Step 5 global-id num (Optional) Specifies the default global ID used for all
endpoints and midpoints.
Example:
• This command makes the router ID globally unique
Device(config-mpls-tp)# global-id 1 in a multiprovider tunnel. Otherwise, the router ID is
only locally meaningful.
• The global ID is an autonomous system number, which
is a controlled number space by which providers can
identify each other.
• The router ID and global ID are also included in fault
messages sent by devices from the tunnel midpoints
to help isolate the location of faults.

Step 6 end Exits MPLS-TP configuration mode and returns to

privileged EXEC mode.
Example:

Device(config-mpls-tp)# end

Configuring Bidirectional Forwarding Detection Templates

The bfd-template command allows you to create a BFD template and enter BFD configuration mode. The
template can be used to specify a set of BFD interval values. You invoke the template as part of the MPLS-TP
tunnel. On platforms that support the BFD Hardware Offload feature and that can provide a 60-ms cutover
for MPLS-TP tunnels, it is recommended to use the higher resolution timers in the BFD template.

SUMMARY STEPS
1. enable
2. configure terminal
3. bfd-template single-hop template-name
4. interval [microseconds] {both time | min-tx time min-rx time} [multiplier multiplier-value]
5. end

DETAILED STEPS

Command or Action Purpose

Step 1 enable Enables privileged EXEC mode.
Example: • Enter your password if prompted.

Device> enable

Step 2 configure terminal Enters global configuration mode.

Example:

Device# configure terminal

MPLS Basic MPLS Configuration Guide

10
 MPLS Transport Profile
Configuring Pseudowire OAM Attributes

Command or Action Purpose

Step 3 bfd-template single-hop template-name Creates a BFD template and enter BFD configuration mode.
Example:

Device(config)# bfd-template single-hop mpls-bfd-1

Step 4 interval [microseconds] {both time | min-tx time min-rx Specifies a set of BFD interval values.
time} [multiplier multiplier-value]
Example:

Device(config-bfd)# interval min-tx 99 min-rx 99

multiplier 3

Step 5 end Exits BFD configuration mode and returns to privileged

EXEC mode.
Example:

Device(config-bfd)# exit

Configuring Pseudowire OAM Attributes

SUMMARY STEPS
1. enable
2. configure terminal
3. pseudowire-static-oam class class-name
4. timeout refresh send seconds
5. exit

DETAILED STEPS

Command or Action Purpose

Step 1 enable Enables privileged EXEC mode.
Example: • Enter your password if prompted.

Device> enable

Step 2 configure terminal Enters global configuration mode.

Example:

Device# configure terminal

Step 3 pseudowire-static-oam class class-name Creates a pseudowire OAM class and enters pseudowire
OAM class configuration mode.
Example:

Device(config)# pseudowire-static-oam class

oam-class1

MPLS Basic MPLS Configuration Guide

11
 MPLS Transport Profile
Configuring the Pseudowire Class

Command or Action Purpose

Step 4 timeout refresh send seconds Specifies the OAM timeout refresh interval.
Example:

Device(config-st-pw-oam-class)# timeout refresh

send 20

Step 5 exit Exits pseudowire OAM configuration mode and returns to

privileged EXEC mode.
Example:

Device(config-st-pw-oam-class)# exit

Configuring the Pseudowire Class

When you create a pseudowire class, you specify the parameters of the pseudowire, such as the use of the
control word, preferred path, OAM class, and VCCV BFD template.

SUMMARY STEPS
1. enable
2. configure terminal
3. pseudowire-class class-name
4. encapsulation mpls
5. control-word
6. protocol {l2tpv2 | l2tpv3 | none} [l2tp-class-name]
7. preferred-path {interface tunnel tunnel-number | peer {ip-address | host-name}} [disable-fallback]
8. status protocol notification static class-name
9. vccv bfd template name [udp | raw-bfd]
10. end

DETAILED STEPS

Command or Action Purpose

Step 1 enable Enables privileged EXEC mode.
Example: • Enter your password if prompted.

Device> enable

Step 2 configure terminal Enters global configuration mode.

Example:

Device# configure terminal

Step 3 pseudowire-class class-name Creates a pseudowire class and enters pseudowire class
configuration mode.
Example:

MPLS Basic MPLS Configuration Guide

12
 MPLS Transport Profile
Configuring the Pseudowire

Command or Action Purpose

Device(config)# pseudowire-class mpls-tp-class1

Step 4 encapsulation mpls Specifies the encapsulation type.

Example:

Device(config-pw-class)# encapsulation mpls

Step 5 control-word Enables the use of the control word.

Example:

Device(config-pw-class)# control-word

Step 6 protocol {l2tpv2 | l2tpv3 | none} [l2tp-class-name] Specifies the type of protocol.
Example:

Device(config-pw-class)# protocol none

Step 7 preferred-path {interface tunnel tunnel-number | peer Specifies the tunnel to use as the preferred path.
{ip-address | host-name}} [disable-fallback]
Example:

Device(config-pw-class)# preferred-path interface

tunnel-tp2

Step 8 status protocol notification static class-name Specifies the OAM class to use.
Example:

Device(config-pw-class)# status protocol

notification static oam-class1

Step 9 vccv bfd template name [udp | raw-bfd] Specifies the VCCV BFD template to use.
Example:

Device(config-pw-class)# vccv bfd template

bfd-temp1 raw-bfd

Step 10 end Exits pseudowire class configuration mode and returns to

privileged EXEC mode.
Example:

Device(config-pw-class)# end

Configuring the Pseudowire

SUMMARY STEPS
1. enable
2. configure terminal

MPLS Basic MPLS Configuration Guide

13
 MPLS Transport Profile
Configuring the Pseudowire

3. interface type number

4. xconnect peer-ip-address vc-id {encapsulation {l2tpv3 [manual] | mpls [manual]} | pw-class
pw-class-name} [pw-class pw-class-name] [sequencing {transmit | receive | both}]
5. mpls label local-pseudowire-label remote-pseudowire-label
6. mpls control-word
7. backup delay {enable-delay-period | never} {disable-delay-period | never}
8. backup peer peer-router-ip-addr vcid [pw-class pw-class-name] [priority value]
9. end

DETAILED STEPS

Command or Action Purpose

Step 1 enable Enables privileged EXEC mode.
Example: • Enter your password if prompted.

Device> enable

Step 2 configure terminal Enters global configuration mode.

Example:

Device# configure terminal

Step 3 interface type number Specifies the interface and enters interface configuration
mode.
Example:

Device(config)# interface Ethernet 1/0

Step 4 xconnect peer-ip-address vc-id {encapsulation {l2tpv3 Binds the attachment circuit to a pseudowire VC and enters
[manual] | mpls [manual]} | pw-class pw-class-name} xconnect interface configuration mode.
[pw-class pw-class-name] [sequencing {transmit | receive
| both}]
Example:

Device(config-if)# xconnect 10.131.191.251 100

encapsulation mpls manual pw-class mpls-tp-class1

Step 5 mpls label local-pseudowire-label Configures the static pseudowire connection by defining
remote-pseudowire-label local and remote circuit labels.
Example:

Device(config-if-xconn)# mpls label 100 150

Step 6 mpls control-word Specifies the control word.

Example:

Device(config-if-xconn)# no mpls control-word

MPLS Basic MPLS Configuration Guide

14
 MPLS Transport Profile
Configuring the MPLS-TP Tunnel

Command or Action Purpose

Step 7 backup delay {enable-delay-period | never} Specifies how long a backup pseudowire virtual circuit
{disable-delay-period | never} (VC) should wait before resuming operation after the
primary pseudowire VC goes down.
Example:

Device(config-if-xconn)# backup delay 0 never

Step 8 backup peer peer-router-ip-addr vcid [pw-class Specifies a redundant peer for a pseudowire virtual circuit
pw-class-name] [priority value] (VC).
Example:

Device(config-if-xconn)# backup peer 10.0.0.2 50

Step 9 end Exits xconn interface connection mode and returns to

privileged EXEC mode.
Example:

Device(config)# end

Configuring the MPLS-TP Tunnel

On the endpoint devices, create an MPLS TP tunnel and configure its parameters. See the interface tunnel-tp
command for information on the parameters.

SUMMARY STEPS
1. enable
2. configure terminal
3. interface tunnel-tp number
4. description tunnel-description
5. tp tunnel-name name
6. tp bandwidth num
7. tp source node-id [global-id num]
8. tp destination node-id [tunnel-tp num[ global-id num]]
9. bfd bfd-template
10. working-lsp
11. in-label num
12. out-label num out-link num
13. exit
14. protect-lsp
15. in-label num
16. out-label num out-link num
17. end

MPLS Basic MPLS Configuration Guide

15
 MPLS Transport Profile
Configuring the MPLS-TP Tunnel

DETAILED STEPS

Command or Action Purpose

Step 1 enable Enables privileged EXEC mode.
Example: • Enter your password if prompted.

Device> enable

Step 2 configure terminal Enters global configuration mode.

Example:

Device# configure terminal

Step 3 interface tunnel-tp number Enters tunnel interface configuration mode. Tunnel
numbers from 0 to 999 are supported.
Example:

Device(config)# interface tunnel-tp

Step 4 description tunnel-description (Optional) Specifies a tunnel description.

Example:

Device(config-if)# description headend tunnel

Step 5 tp tunnel-name name Specifies the name of the MPLS-TP tunnel.

Example:

Device(config-if)# tp tunnel-name tunnel 122

Step 6 tp bandwidth num Specifies the tunnel bandwidth.

Example:

Device(config-if)# tp bandwidth 10000

Step 7 tp source node-id [global-id num] (Optional) Specifies the tunnel source and endpoint.
Example:

Device(config-if)# tp source 10.11.11.11 global-id

10

Step 8 tp destination node-id [tunnel-tp num[ global-id num]] Specifies the destination node of the tunnel.
Example:

Device(config-if)# tp destination 10.10.10.10

Step 9 bfd bfd-template Specifies the BFD template.

Example:

Device(config-if)# bfd mpls-tp-bfd-2

MPLS Basic MPLS Configuration Guide

16
 MPLS Transport Profile
Configuring MPLS-TP LSPs at Midpoints

Command or Action Purpose

Step 10 working-lsp Specifies a working LSP, also known as the primary LSP.
Example:

Device(config-if)# working-lsp

Step 11 in-label num Specifies the in-label number.

Example:

Device(config-if-working)# in-label 111

Step 12 out-label num out-link num Specifies the out-label number and out-link.
Example:

Device(config-if-working)# out-label 112 out-link

Step 13 exit Exits working LSP interface configuration mode and

returns to interface configuration mode.
Example:

Device(config-if-working)# exit

Step 14 protect-lsp Specifies a backup for a working LSP.

Example:

Device(config-if)# protect-lsp

Step 15 in-label num Specifies the in label.

Example:

Device(config-if-protect)# in-label 100

Step 16 out-label num out-link num Specifies the out label and out link.
Example:

Device(config-if-protect)# out-label 113 out-link

Step 17 end Exits the interface configuration mode and returns to

privileged EXEC mode.
Example:

Device(config-if-protect)# end

Configuring MPLS-TP LSPs at Midpoints

Note When configuring LSPs at midpoint devices, ensure that the configuration does not deflect traffic back to the
originating node.

MPLS Basic MPLS Configuration Guide

17
 MPLS Transport Profile
Configuring MPLS-TP LSPs at Midpoints

SUMMARY STEPS
1. enable
2. configure terminal
3. mpls tp lsp source node-id [global-id num] tunnel-tp num lsp{lsp-num | protect | working} destination
node-id [global-id num] tunnel-tp num
4. forward-lsp
5. bandwidth num
6. in-label num out-label num out-link num
7. exit
8. reverse-lsp
9. bandwidth num
10. in-label num out-label num out-link num
11. end

DETAILED STEPS

Command or Action Purpose

Step 1 enable Enables privileged EXEC mode.
Example: • Enter your password if prompted.

Device> enable

Step 2 configure terminal Enters global configuration mode.

Example:

Device# configure terminal

Step 3 mpls tp lsp source node-id [global-id num] tunnel-tp Enables MPLS-TP midpoint connectivity and enters MPLS
num lsp{lsp-num | protect | working} destination node-id TP LSP configuration mode.
[global-id num] tunnel-tp num
Example:

Device(config)# mpls tp lsp source 10.10.10.10

global-id 2 tunnel-tp 4 lsp protect destination
10.11.11.11 global-id 11 tunnel-tp 12

Step 4 forward-lsp Enters MPLS-TP LSP forward LSP configuration mode.

Example:

Device(config-mpls-tp-lsp)# forward-lsp

Step 5 bandwidth num Specifies the bandwidth.

Example:

Device(config-mpls-tp-lsp-forw)# bandwidth 100

MPLS Basic MPLS Configuration Guide

18
 MPLS Transport Profile
Configuring MPLS-TP Links and Physical Interfaces

Command or Action Purpose

Step 6 in-label num out-label num out-link num Specifies the in label, out label, and out link numbers.
Example:

Device(config-mpls-tp-lsp-forw)# in-label 53
out-label 43 out-link 41

Step 7 exit Exits MPLS-TP LSP forward LSP configuration mode.

Example:

Device(config-mpls-tp-lsp-forw)# exit

Step 8 reverse-lsp Enters MPLS-TP LSP reverse LSP configuration mode.

Example:

Device(config-mpls-tp-lsp)# reverse-lsp

Step 9 bandwidth num Specifies the bandwidth.

Example:

Device(config-mpls-tp-lsp-rev)# bandwidth 100

Step 10 in-label num out-label num out-link num Specifies the in-label, out-label, and out-link numbers.
Example:

Device(config-mpls-tp-lsp-rev)# in-label 33
out-label 23 out-link 44

Step 11 end Exits the MPLS TP LSP configuration mode and returns
to privileged EXEC mode.
Example:

Device(config-mpls-tp-lsp-rev)# end

Configuring MPLS-TP Links and Physical Interfaces

MPLS-TP link numbers may be assigned to physical interfaces only. Bundled interfaces and virtual interfaces
are not supported for MPLS-TP link numbers.

SUMMARY STEPS
1. enable
2. configure terminal
3. interface type number
4. ip address ip-address mask
5. mpls tp link link-num {ipv4 ip-address | tx-mac mac-address} rx-mac mac-address
6. ip rsvp bandwidth [rdm [bc0 interface-bandwidth] [[single-flow-bandwidth [bc1 bandwidth | sub-pool
bandwidth]]] [interface-bandwidth [single-flow-bandwidth [bc1 bandwidth | sub-pool bandwidth]] | mam

MPLS Basic MPLS Configuration Guide

19
 MPLS Transport Profile
Configuring MPLS-TP Links and Physical Interfaces

max-reservable-bw [interface-bandwidth [single-flow-bandwidth] [bc0 interface-bandwidth [bc1

bandwidth]]] | percent percent-bandwidth [single-flow-bandwidth]]
7. end
8. show mpls tp link-numbers

DETAILED STEPS

Command or Action Purpose

Step 1 enable Enables privileged EXEC mode.
Example: • Enter your password if prompted.

Device> enable

Step 2 configure terminal Enters global configuration mode.

Example:

Device# configure terminal

Step 3 interface type number Specifies the interface and enters interface configuration
mode.
Example:

Device(config)# interface ethernet 1/0

Step 4 ip address ip-address mask Assigns an IP address to the interface.

Example:

Device(config-if)# ip address 10.10.10.10

255.255.255.0

Step 5 mpls tp link link-num {ipv4 ip-address | tx-mac Associates an MPLS-TP link number with a physical
mac-address} rx-mac mac-address interface and next-hop node. On point-to-point interfaces
or Ethernet interfaces designated as point-to-point using
Example:
the medium p2p command, the next-hop can be implicit,
so the mpls tp link command just associates a link number
Device(config-if)# mpls tp link 1 ipv4 10.0.0.2
to the interface.
Multiple tunnels and LSPs can refer to the MPLS-TP link
to indicate they are traversing that interface. You can move
the MPLS-TP link from one interface to another without
reconfiguring all the MPLS-TP tunnels and LSPs that refer
to the link.
Link numbers must be unique on the device or node.

Step 6 ip rsvp bandwidth [rdm [bc0 interface-bandwidth] Enables Resource Reservation Protocol (RSVP) bandwidth
[[single-flow-bandwidth [bc1 bandwidth | sub-pool for IP on an interface.
bandwidth]]] [interface-bandwidth [single-flow-bandwidth
For the Cisco 7600 platform, if you configure non-zero
[bc1 bandwidth | sub-pool bandwidth]] | mam
bandwidth for the TP tunnel or at a midpoint LSP, make
max-reservable-bw [interface-bandwidth
sure that the interface to which the output link is attached
[single-flow-bandwidth] [bc0 interface-bandwidth [bc1
has enough bandwidth available. For example, if three

MPLS Basic MPLS Configuration Guide

20
 MPLS Transport Profile
Configuring Static-to-Static Multisegment Pseudowires for MPLS-TP

Command or Action Purpose

bandwidth]]] | percent percent-bandwidth tunnel LSPs run over link 1 and each LSP was assigned
[single-flow-bandwidth]] 1000 with the tp bandwidth command, the interface
associated with link 1 needs bandwidth of 3000 with the ip
Example:
rsvp bandwidth command.
Device(config-if)# ip rsvp bandwidth 1158 100

Step 7 end Exits interface configuration mode and returns to privileged

EXEC mode.
Example:

Device(config-if)# end

Step 8 show mpls tp link-numbers Displays the configured links.

Example:

Device# show mpls tp link-numbers

Configuring Static-to-Static Multisegment Pseudowires for MPLS-TP

SUMMARY STEPS
1. enable
2. configure terminal
3. l2 vfi name point-to-point
4. neighbor ip-address vc-id {encapsulation mpls | pw-class pw-class-name}
5. mpls label local-pseudowire-label remote-pseudowire-label
6. mpls control-word
7. neighbor ip-address vc-id {encapsulation mpls | pw-class pw-class-name}
8. mpls label local-pseudowire-label remote-pseudowire-label
9. mpls control-word
10. end

DETAILED STEPS

Command or Action Purpose

Step 1 enable Enables privileged EXEC mode.
Example: • Enter your password if prompted.

Device> enable

Step 2 configure terminal Enters global configuration mode.

Example:

Device# configure terminal

MPLS Basic MPLS Configuration Guide

21
 MPLS Transport Profile
Configuring Static-to-Static Multisegment Pseudowires for MPLS-TP

Command or Action Purpose

Step 3 l2 vfi name point-to-point Creates a point-to-point Layer 2 virtual forwarding
interface (VFI) and enters VFI configuration mode.
Example:

Device(config)# l2 vfi atom point-to-point

Step 4 neighbor ip-address vc-id {encapsulation mpls | Sets up an emulated VC. Specify the IP address, the VC
pw-class pw-class-name} ID of the remote device, and the pseudowire class to use
for the emulated VC.
Example:
Note Only two neighbor commands are allowed for
Device(config-vfi)# neighbor 10.111.111.111 123 each Layer 2 VFI point-to-point command.
pw-class atom

Step 5 mpls label local-pseudowire-label Configures the static pseudowire connection by defining
remote-pseudowire-label local and remote circuit labels.
Example:

Device(config-vfi)# mpls label 101 201

Step 6 mpls control-word Specifies the control word.

Example:

Device(config-vfi)# mpls control-word

Step 7 neighbor ip-address vc-id {encapsulation mpls | Sets up an emulated VC. Specify the IP address, the VC
pw-class pw-class-name} ID of the remote device, and the pseudowire class to use
for the emulated VC.
Example:

Device(config-vfi)# neighbor 10.10.10.11 123

pw-class atom

Step 8 mpls label local-pseudowire-label Configures the static pseudowire connection by defining
remote-pseudowire-label local and remote circuit labels.
Example:

Device(config-vfi)# mpls label 102 202

Step 9 mpls control-word Specifies the control word.

Example:

Example:

Device(config-vfi)# mpls control-word

Step 10 end Exits VFI configuration mode and returns to privileged

EXEC mode.
Example:

Device(config)# end

MPLS Basic MPLS Configuration Guide

22
 MPLS Transport Profile
Configuring a Template with Pseudowire Type-Length-Value Parameters

Configuring a Template with Pseudowire Type-Length-Value Parameters

SUMMARY STEPS
1. enable
2. configure terminal
3. pseudowire-tlv template template-name
4. tlv [type-name] type-value length [dec | hexstr | str] value
5. end

DETAILED STEPS

Command or Action Purpose

Step 1 enable Enables privileged EXEC mode.
Example: • Enter your password if prompted.

Device> enable

Step 2 configure terminal Enters global configuration mode.

Example:

Device# configure terminal

Step 3 pseudowire-tlv template template-name Creates a template of pseudowire type-length-value (TLV)

parameters and enters pseudowire TLV template
Example:
configuration mode.
Device(config)# pseudowire-tlv template statictemp

Step 4 tlv [type-name] type-value length [dec | hexstr | str] value Specifies the TLV parameters.
Example:

Device(config-pw-tlv-template)# tlv statictemp 2

4 hexstr 1

Step 5 end Exits pseudowire TLV template configuration mode and

returns to privileged EXEC mode.
Example:

Device(config-pw-tlv-template)# end

Configuring Static-to-Dynamic Multisegment Pseudowires for MPLS-TP

When you configure static-to-dynamic pseudowires, you configure the static pseudowire class with the protocol
none command, create a dynamic pseudowire class, and then invoke those pseudowire classes with the
neighbor commands.

SUMMARY STEPS
1. enable

MPLS Basic MPLS Configuration Guide

23
 MPLS Transport Profile
Configuring Static-to-Dynamic Multisegment Pseudowires for MPLS-TP

2. configure terminal
3. pseudowire-class class-name
4. encapsulation mpls
5. control-word
6. protocol {l2tpv2 | l2tpv3 | none} [l2tp-class-name]
7. exit
8. pseudowire-class class-name
9. encapsulation mpls
10. exit
11. l2 vfi name point-to-point
12. neighbor ip-address vc-id {encapsulation mpls | pw-class pw-class-name}
13. neighbor ip-address vc-id {encapsulation mpls | pw-class pw-class-name}
14. mpls label local-pseudowire-label remote-pseudowire-label
15. mpls control-word
16. local interface pseudowire-type
17. Do one of the following:
• tlv [type-name] type-value length [dec | hexstr | str] value
• tlv template template-name
18. end

DETAILED STEPS

Command or Action Purpose

Step 1 enable Enables privileged EXEC mode.
Example: • Enter your password if prompted.

Device> enable

Step 2 configure terminal Enters global configuration mode.

Example:

Device# configure terminal

Step 3 pseudowire-class class-name Creates a pseudowire class and enters pseudowire class
configuration mode.
Example:

Device(config)# pseudowire-class mpls-tp-class1

Step 4 encapsulation mpls Specifies the encapsulation type.

Example:

Device(config-pw-class)# encapsulation mpls

Step 5 control-word Enables the use of the control word.

Example:

MPLS Basic MPLS Configuration Guide

24
 MPLS Transport Profile
Configuring Static-to-Dynamic Multisegment Pseudowires for MPLS-TP

Command or Action Purpose

Device(config-pw-class)# control-word

Step 6 protocol {l2tpv2 | l2tpv3 | none} [l2tp-class-name] Specifies the type of protocol. Use the protocol none
command to specify a static pseudowire.
Example:

Device(config-pw-class)# protocol none

Step 7 exit Exits pseudowire class configuration mode and returns to

global configuration mode.
Example:

Device(config-pw-class)# exit

Step 8 pseudowire-class class-name Creates a pseudowire class and enters pseudowire class
configuration mode.
Example:

Device(config)# pseudowire-class mpls-tp-class1

Step 9 encapsulation mpls Specifies the encapsulation type.

Example:

Device(config-pw-class)# encapsulation mpls

Step 10 exit Exits pseudowire class configuration mode and returns to

global configuration mode.
Example:

Device(config-pw-class)# exit

Step 11 l2 vfi name point-to-point Creates a point-to-point Layer 2 virtual forwarding

interface (VFI) and enters VFI configuration mode.
Example:

Device(config)# l2 vfi atom point-to-point

Step 12 neighbor ip-address vc-id {encapsulation mpls | Sets up an emulated VC and enters VFI neighbor
pw-class pw-class-name} configuration mode.
Example: Note Note: Only two neighbor commands are
allowed for each l2 vfi point-to-point
Device(config-vfi)# neighbor 10.111.111.111 123 command.
pw-class atom

Step 13 neighbor ip-address vc-id {encapsulation mpls | Sets up an emulated VC.

pw-class pw-class-name}
Note Only two neighbor commands are allowed for
Example: each l2 vfi point-to-point command.

Device(config-vfi-neighbor)# neighbor
10.111.111.111 123 pw-class atom

MPLS Basic MPLS Configuration Guide

25
 MPLS Transport Profile
Verifying the MPLS-TP Configuration

Command or Action Purpose

Step 14 mpls label local-pseudowire-label Configures the static pseudowire connection by defining
remote-pseudowire-label local and remote circuit labels.
Example:

Device(config-vfi-neighbor)# mpls label 101 201

Step 15 mpls control-word Specifies the control word.

Example:

Device(config-vfi-neighbor)# mpls control-word

Step 16 local interface pseudowire-type Specifies the pseudowire type.

Example:

Device(config-vfi-neighbor)# local interface 4

Step 17 Do one of the following: Specifies the TLV parameters or invokes a previously
configured TLV template.
• tlv [type-name] type-value length [dec | hexstr | str]
value
• tlv template template-name
Example:

Device(config-vfi-neighbor)# tlv statictemp 2 4

hexstr 1

Step 18 end Ends the session.

Example:

Device(config-vfi-neighbor)# end

Verifying the MPLS-TP Configuration

Use the following commands to verify and help troubleshoot your MPLS-TP configuration:
• debug mpls tp—Enables the logging of MPLS-TP error messages.
• logging (MPLS-TP)—Displays configuration or state change logging messages.
• show bfd neighbors mpls-tp—Displays the BFD state, which must be up in order for the endpoint LSPs
to be up.
• show mpls l2transport static-oam l2transport static-oam—Displays MPLS-TP messages related to
pseudowires.
• show mpls tp tunnel-tp number detail—Displays the number and details of the tunnels that are not
functioning.
• show mpls tp tunnel-tp lsps—Displays the status of the LSPs, and helps you ensure that both LSPs are
up and working from a tunnel endpoint.

MPLS Basic MPLS Configuration Guide

26
 MPLS Transport Profile
Configuration Examples for MPLS Transport Profile

• traceroute mpls tp and ping mpls tp—Helps you identify connectivity issues along the MPLS-TP
tunnel path.

Configuration Examples for MPLS Transport Profile

Example: Configuring Static-to-dynamic Multisegment Pseudowires for
MPLS-TP
The following example shows how to configure static-to-dynamic multisegment pseudowires for
Layer 2 VFI.

l2 vfi atom point-to-point (static-dynamic MSPW)

neighbor 10.116.116.116 4294967295 pw-class dypw (dynamic)
neighbor 10.111.111.111 123 pw-class stpw (static)
mpls label 101 201
mpls control-word
local interface 4
tlv mtu 1 4 1500
tlv description 3 6 str abcd
tlv descr C 4 hexstr 0505

Additional References for MPLS Transport Profile

Related Documents

Related Topic Document Title

Cisco IOS commands Cisco IOS Master Command List, All Releases

MPLS commands Cisco IOS Multiprotocol Label Switching Command Reference

Standards and RFCs

Standard/RFC Title

draft-ietf-mpls-tp-gach-gal-xx MPLS Generic Associated Channel

RFC 5586 MPLS Generic Associated Channel

RFC 5885 Bidirectional Forwarding Detection (BFD) for the Pseudowire Virtual Circuit
Connectivity Verification (VCCV)

RFC 5921 A Framework for MPLS in Transport Networks

MPLS Basic MPLS Configuration Guide

27
 MPLS Transport Profile
Feature Information for MPLS Transport Profile

Technical Assistance

Description Link

The Cisco Support and Documentation website provides http://www.cisco.com/cisco/web/support/index.html

online resources to download documentation, software,
and tools. Use these resources to install and configure
the software and to troubleshoot and resolve technical
issues with Cisco products and technologies. Access to
most tools on the Cisco Support and Documentation
website requires a Cisco.com user ID and password.

Feature Information for MPLS Transport Profile

The following table provides release information about the feature or features described in this module. This
table lists only the software release that introduced support for a given feature in a given software release
train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support.
To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.

MPLS Basic MPLS Configuration Guide

28
 CHAPTER 3
Multiprotocol Label Switching (MPLS) on Cisco
Routers
This document describes commands for configuring and monitoring Multiprotocol Label Switching (MPLS)
functionality on Cisco routers and switches. This document is a companion to other feature modules describing
other MPLS applications.
• Information About MPLS, on page 29
• How to Configure MPLS, on page 32
• Additional References, on page 35
• Feature Information for MPLS on Cisco Routers, on page 36
• Glossary, on page 36

Information About MPLS

MPLS Overview
Multiprotocol label switching (MPLS) combines the performance and capabilities of Layer 2 (data link layer)
switching with the proven scalability of Layer 3 (network layer) routing. MPLS enables service providers to
meet the challenges of explosive growth in network utilization while providing the opportunity to differentiate
services without sacrificing the existing network infrastructure. The MPLS architecture is flexible and can be
employed in any combination of Layer 2 technologies. MPLS support is offered for all Layer 3 protocols,
and scaling is possible well beyond that typically offered in today’s networks.
MPLS efficiently enables the delivery of IP services over an ATM switched network. MPLS supports the
creation of different routes between a source and a destination on a purely router-based Internet backbone.
By incorporating MPLS into their network architecture, service providers can save money, increase revenue
and productivity, provide differentiated services, and gain competitive advantages.

Note In the Cisco IOS XE Release 16.x, the ASR 1000 routers only support fragmentation of the MPLS packets
from the IP to MPLS direction.

MPLS Basic MPLS Configuration Guide

29
 Multiprotocol Label Switching (MPLS) on Cisco Routers
Functional Description of MPLS

Functional Description of MPLS

Label switching is a high-performance packet forwarding technology that integrates the performance and
traffic management capabilities of data link layer (Layer 2) switching with the scalability, flexibility, and
performance of network layer (Layer 3) routing.

Label Switching Functions

In conventional Layer 3 forwarding mechanisms, as a packet traverses the network, each router extracts all
the information relevant to forwarding the packet from the Layer 3 header. This information is then used as
an index for a routing table lookup to determine the next hop for the packet.
In the most common case, the only relevant field in the header is the destination address field, but in some
cases, other header fields might also be relevant. As a result, the header analysis must be done independently
at each router through which the packet passes. In addition, a complicated table lookup must also be done at
each router.
In label switching, the analysis of the Layer 3 header is done only once. The Layer 3 header is then mapped
into a fixed length, unstructured value called a label .
Many different headers can map to the same label, as long as those headers always result in the same choice
of next hop. In effect, a label represents a forwarding equivalence class --that is, a set of packets which,
however different they may be, are indistinguishable by the forwarding function.
The initial choice of a label need not be based exclusively on the contents of the Layer 3 packet header; for
example, forwarding decisions at subsequent hops can also be based on routing policy.
Once a label is assigned, a short label header is added at the front of the Layer 3 packet. This header is carried
across the network as part of the packet. At subsequent hops through each MPLS router in the network, labels
are swapped and forwarding decisions are made by means of MPLS forwarding table lookup for the label
carried in the packet header. Hence, the packet header does not need to be reevaluated during packet transit
through the network. Because the label is of fixed length and unstructured, the MPLS forwarding table lookup
process is both straightforward and fast.

Distribution of Label Bindings

Each label switching router (LSR) in the network makes an independent, local decision to determine a label
value to represent a forwarding equivalence class. This association is known as a label binding. Each LSR
informs its neighbors of the label bindings it has made.
When a labeled packet is being sent from LSR A to the neighboring LSR B, the label value carried by the IP
packet is the label value that LSR B assigned to represent the forwarding equivalence class of the packet.
Thus, the label value changes as the IP packet traverses the network.
The awareness of label bindings by neighbouring routers is facilitated using the following protocols:
• Label Distribution Protocol (LDP) - Enables peer LSRs in an MPLS network to exchange label binding
information for supporting hop-by-hop forwarding in an MPLS network.
• Tag Distribution Protocol (TDP) - Supports MPLS forwarding along normally routed paths.
• Resource Reservation Protocol (RSVP) - Supports MPLS traffic engineering.
• Border Gateway Protocol (BGP) - Supports MPLS virtual private networks (VPNs) .

MPLS Basic MPLS Configuration Guide

30
 Multiprotocol Label Switching (MPLS) on Cisco Routers
Benefits of MPLS

Benefits of MPLS
MPLS provides the following major benefits to service provider networks:
Scalable support for Virtual Private Networks (VPNs)--MPLS enables VPN services to be supported in
service provider networks, thereby greatly accelerating Internet growth.
The use of MPLS for VPNs provides an attractive alternative to the building of VPNs by means of either
ATM or Frame Relay permanent virtual circuits (PVCs) or various forms of tunneling to interconnect routers
at customer sites.
Unlike the PVC VPN model, the MPLS VPN model is highly scalable and can accommodate increasing
numbers of sites and customers. The MPLS VPN model also supports “any-to-any” communication among
VPN sites without requiring a full mesh of PVCs or the backhauling (suboptimal routing) of traffic across the
service provider network. For each MPLS VPN user, the service provider’s network appears to function as a
private IP backbone over which the user can reach other sites within the VPN organization, but not the sites
of any other VPN organization.
From a user perspective, the MPLS VPN model enables network routing to be dramatically simplified. For
example, rather than having to manage routing over a topologically complex virtual backbone composed of
many PVCs, an MPLS VPN user can generally employ the service provider’s backbone as the default route
in communicating with all of the other VPN sites.
Explicit routing capabilities (also called constraint-based routing or traffic engineering)--Explicit routing
employs “constraint-based routing,” in which the path for a traffic flow is the shortest path that meets the
resource requirements (constraints) of the traffic flow.
In MPLS traffic engineering, factors such as bandwidth requirements, media requirements, and the priority
of one traffic flow versus another can be taken into account. These traffic engineering capabilities enable the
administrator of a service provider network to
• Control traffic flow in the network
• Reduce congestion in the network
• Make best use of network resources

Thus, the network administrator can specify the amount of traffic expected to flow between various points in
the network (thereby establishing a traffic matrix), while relying on the routing system to
• Calculate the best paths for network traffic
• Set up the explicit paths to carry the traffic

Support for IP routing on ATM switches (also called IP and ATM integration)--MPLS enables an ATM
switch to perform virtually all of the functions of an IP router. This capability of an ATM switch stems from
the fact that the MPLS forwarding paradigm, namely, label swapping, is exactly the same as the forwarding
paradigm provided by ATM switch hardware.
The key difference between a conventional ATM switch and an ATM label switch is the control software
used by the latter to establish its virtual channel identifier (VCI) table entries. An ATM label switch uses IP
routing protocols and the Tag Distribution Protocol (TDP) to establish VCI table entries.
An ATM label switch can function as a conventional ATM switch. In this dual mode, the ATM switch resources
(such as VCI space and bandwidth) are partitioned between the MPLS control plane and the ATM control
plane. The MPLS control plane provides IP-based services, while the ATM control plane supports ATM-oriented
functions, such as circuit emulation or PVC services.

MPLS Basic MPLS Configuration Guide

31
 Multiprotocol Label Switching (MPLS) on Cisco Routers
How to Configure MPLS

How to Configure MPLS

This section explains how to perform the basic configuration required to prepare a router for MPLS switching
and forwarding.
Configuration tasks for other MPLS applications are described in the feature module documentation for the
application.

Configuring a Router for MPLS Switching

MPLS switching on Cisco routers requires that Cisco Express Forwarding be enabled.
For more information about Cisco Express Forwarding commands, see the Cisco IOS Switching Command
Reference.

SUMMARY STEPS
1. enable
2. configure terminal
3. ip cef distributed

DETAILED STEPS

Command or Action Purpose

Step 1 enable Enables privileged EXEC mode.
Example: • Enter your password if prompted.

Device> enable

Step 2 configure terminal Enters global configuration mode.

Example:

Device# configure terminal

Step 3 ip cef distributed Enables Cisco Express Forwarding on the route processor
card.
Example:

Device(config)# ip cef distributed

Verifying Configuration of MPLS Switching

To verify that Cisco Express Forwarding has been configured properly, issue the show ip cef summary
command, which generates output similar to that shown below:

SUMMARY STEPS
1. show ip cef summary

MPLS Basic MPLS Configuration Guide

32
 Multiprotocol Label Switching (MPLS) on Cisco Routers
Configuring a Router for MPLS Forwarding

DETAILED STEPS

show ip cef summary

Example:

Router# show ip cef summary

IP CEF with switching (Table Version 49), flags=0x0
43 routes, 0 resolve, 0 unresolved (0 old, 0 new)
43 leaves, 49 nodes, 56756 bytes, 45 inserts, 2 invalidations
2 load sharing elements, 672 bytes, 2 references
1 CEF resets, 4 revisions of existing leaves
4 in-place modifications
refcounts: 7241 leaf, 7218 node
Adjacency Table has 18 adjacencies
Router#

Configuring a Router for MPLS Forwarding

MPLS forwarding on Cisco routers requires that forwarding of IPv4 packets be enabled.
For more information about MPLS forwarding commands, see the Multiprotocol Label Switching Command
Reference.

SUMMARY STEPS
1. enable
2. configure terminal
3. interface type slot/subslot /port [. subinterface]
4. mpls ip
5. end

DETAILED STEPS

Command or Action Purpose

Step 1 enable Enables privileged EXEC mode.
Example: • Enter your password if prompted.

Device> enable

Step 2 configure terminal Enters global configuration mode.

Example:

Device# configure terminal

Step 3 interface type slot/subslot /port [. subinterface] Specifies the Gigabit Ethernet interface and enters interface
configuration mode.
Example:

Device(config)# interface gigabitethernet 4/0/0

MPLS Basic MPLS Configuration Guide

33
 Multiprotocol Label Switching (MPLS) on Cisco Routers
Verifying Configuration of MPLS Forwarding

Command or Action Purpose

Step 4 mpls ip Enables MPLS forwarding of IPv4 packets along normally
routed paths for the Gigabit Ethernet interface.
Example:

Device(config-if)# mpls ip

Step 5 end Exits interface configuration mode and returns to privileged

EXEC mode.
Example:

Device(config-if)# end

What to do next
Configure either of the following:
• MPLS Label Distribution Protocol (LDP). For information about configuring MPLS LDP, see the MPLS
Label Distribution Protocol Configuration Guide.
• Static labels. For information about configuring static labels, see MPLS Static Labels.

Verifying Configuration of MPLS Forwarding

To verify that MPLS forwarding has been configured properly, issue the show mpls interfaces detail command,
which generates output similar to that shown below:

SUMMARY STEPS
1. show mpls interfaces detail

DETAILED STEPS

show mpls interfaces detail

Example:

Device# show mpls interfaces detail

Interface GigabitEthernet1/0/0:
IP labeling enabled (ldp)
LSP Tunnel labeling not enabled
MPLS operational
MTU = 1500
Interface POS2/0/0:
IP labeling enabled (ldp)
LSP Tunnel labeling not enabled
MPLS not operational
MTU = 4470

MPLS Basic MPLS Configuration Guide

34
 Multiprotocol Label Switching (MPLS) on Cisco Routers
Additional References

Additional References
Related Documents

Related Topic Document Title

Cisco IOS commands Cisco IOS Master Commands List, All Releases

MPLS commands Cisco IOS Multiprotocol Label Switching Command Reference

Standards

Standard Title

The supported standards applicable to the MPLS applications appear in the respective feature module --
for the application.

MIBs

MIB MIBs Link

The supported MIBs applicable to the MPLS To locate and download MIBs for selected platforms, Cisco
applications appear in the respective feature software releases, and feature sets, use Cisco MIB Locator
module for the application. found at the following URL:
http://www.cisco.com/go/mibs

RFCs

RFC Title

The supported RFCs applicable to the MPLS applications appear in the respective feature module for --
the application.

Technical Assistance

Description Link

The Cisco Support and Documentation website provides online resources to download Support & Downloads
documentation, software, and tools. Use these resources to install and configure the
software and to troubleshoot and resolve technical issues with Cisco products and
technologies. Access to most tools on the Cisco Support and Documentation website
requires a Cisco.com user ID and password.

MPLS Basic MPLS Configuration Guide

35
 Multiprotocol Label Switching (MPLS) on Cisco Routers
Feature Information for MPLS on Cisco Routers

Feature Information for MPLS on Cisco Routers

The following table provides release information about the feature or features described in this module. This
table lists only the software release that introduced support for a given feature in a given software release
train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support.
To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.

Glossary
BGP --Border Gateway Protocol. The predominant interdomain routing protocol used in IP networks.
Border Gateway Protocol --See BGP.
FIB --Forwarding Information Base. A table that contains a copy of the forwarding information in the IP
routing table.
Forwarding Information Base --See FIB.
label --A short, fixed-length identifier that tells switching nodes how the data (packets or cells) should be
forwarded.
label binding --An association between a label and a set of packets, which can be advertised to neighbors so
that a label switched path can be established.
Label Distribution Protocol --See LDP.
Label Forwarding Information Base --See LFIB.
label imposition --The act of putting the first label on a packet.
label switching router --See LSR.
LDP --Label Distribution Protocol. The protocol that supports MPLS hop-by-hop forwarding by distributing
bindings between labels and network prefixes.
LFIB --Label Forwarding Information Base. A data structure in which destinations and incoming labels are
associated with outgoing interfaces and labels.
LSR --label switching router. A Layer 3 router that forwards a packet based on the value of an identifier
encapsulated in the packet.
MPLS --Multiprotocol Label Switching. An industry standard on which label switching is based.
MPLS hop-by-hop forwarding --The forwarding of packets along normally routed paths using MPLS
forwarding mechanisms.
Multiprotocol Label Switching --See MPLS.
Resource Reservation Protocol --See RSVP.
RIB --Routing Information Base. A common database containing all the routing protocols running on a router.
Routing Information Base --See RIB.
RSVP --Resource Reservation Protocol. A protocol for reserving network resources to provide quality of
service guarantees to application flows.

MPLS Basic MPLS Configuration Guide

36
Multiprotocol Label Switching (MPLS) on Cisco Routers
Glossary

traffic engineering --Techniques and processes used to cause routed traffic to travel through the network on
a path other than the one that would have been chosen if standard routing methods were used.
Virtual Private Network --See VPN.
VPN --Virtual Private Network. A network that enables IP traffic to use tunneling to travel securely over a
public TCP/IP network.

MPLS Basic MPLS Configuration Guide

37
 Multiprotocol Label Switching (MPLS) on Cisco Routers
Glossary

MPLS Basic MPLS Configuration Guide

38
 CHAPTER 4
MPLS Infrastructure Changes Introduction of MFI
and Removal of MPLS LSC and LC-ATM Features
This document explains the new MPLS Forwarding Infrastructure (MFI) and removal of support for MPLS
label switch controller (LSC) and label-controlled ATM (LC-ATM) features and commands.
• Finding Feature Information, on page 39
• Information About MPLS Infrastructure Changes, on page 39
• Additional References, on page 40
• Feature Information for MPLS Infrastructure Changes, on page 41

Finding Feature Information

Your software release may not support all the features documented in this module. For the latest caveats and
feature information, see Bug Search Tool and the release notes for your platform and software release. To
find information about the features documented in this module, and to see a list of the releases in which each
feature is supported, see the feature information table at the end of this module.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support.
To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.

Information About MPLS Infrastructure Changes

Introduction of the MPLS Forwarding Infrastructure
The MPLS control plane software is enhanced to make MPLS more scalable and flexible. The MFI, which
manages MPLS data structures used for forwarding, replaces the Label Forwarding Information Base (LFIB).

Note The MFI and LFIB do not coexist in the same image. For a list of supported releases, see the "Feature
Information for MPLS Forwarding Infrastructure."

MPLS Basic MPLS Configuration Guide

39
 MPLS Infrastructure Changes Introduction of MFI and Removal of MPLS LSC and LC-ATM Features
Introduction of IP Rewrite Manager

Introduction of IP Rewrite Manager

Cisco software introduces a module called the MPLS IP Rewrite Manager (IPRM) that manages the interactions
between Cisco Express Forwarding, the IP Label Distribution Modules (LDMs), and the MFI. MPLS IPRM
is enabled by default. You need not configure or customize the IPRM. These commands are related to IPRM:
• clear mpls ip iprm counters
• debug mpls ip iprm
• debug mpls ip iprm cef
• debug mpls ip iprm events
• debug mpls ip iprm ldm
• debug mpls ip iprm mfi
• show mpls ip iprm counters
• show mpls ip iprm ldm

For information about these commands, see the Cisco IOS Debug Command Reference and the Cisco IOS
MPLS Command Reference.

MPLS LSC and LC-ATM Configurations

Before upgrading to Cisco IOS Release 12.4(20)T, remove all the MPLS LSC and LC-ATM configurations
from the routers in your network. If your core network has ATM links, you can use packet-based MPLS. See
the MPLS Label Distribution Protocol Overview for more information. If you provide ATM access to customers,
you can use the Any Transport over MPLS: ATM over MPLS feature. See Any Transport over MPLS for
more information.
If you have MPLS LSC or LC-ATM features configured and you upgrade to Cisco IOS Release 12.4(20)T,
the configuration is not accepted. The system displays “unrecognized command” errors for any commands
that are no longer supported.

Additional References
Related Documents

Related Topic Document Title

MPLS commands Cisco IOS MPLS Command Reference

MPLS Label Distribution Protocol MPLS Label Distribution Protocol Overview

Layer 2 VPN features over MPLS Any Transport over MPLS

MPLS Basic MPLS Configuration Guide

40
 MPLS Infrastructure Changes Introduction of MFI and Removal of MPLS LSC and LC-ATM Features
Feature Information for MPLS Infrastructure Changes

Technical Assistance

Description Link

The Cisco Support website provides extensive online resources, including http://www.cisco.com/techsupport
documentation and tools for troubleshooting and resolving technical issues
with Cisco products and technologies.
To receive security and technical information about your products, you
can subscribe to various services, such as the Product Alert Tool (accessed
from Field Notices), the Cisco Technical Services Newsletter, and Really
Simple Syndication (RSS) Feeds.
Access to most tools on the Cisco Support website requires a Cisco.com
user ID and password.

Feature Information for MPLS Infrastructure Changes

The following table provides release information about the feature or features described in this module. This
table lists only the software release that introduced support for a given feature in a given software release
train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support.
To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.

MPLS Basic MPLS Configuration Guide

41
 MPLS Infrastructure Changes Introduction of MFI and Removal of MPLS LSC and LC-ATM Features
Feature Information for MPLS Infrastructure Changes

MPLS Basic MPLS Configuration Guide

42
 CHAPTER 5
MPLS Static Labels
This document describes the Cisco MPLS Static Labels feature. The MPLS Static Labels feature provides the
means to configure statically:
• The binding between a label and an IPv4 prefix
• The contents of an LFIB crossconnect entry

• Finding Feature Information, on page 43

• Restrictions for MPLS Static Labels, on page 43
• Prerequisites for MPLS Static Labels, on page 44
• Information About MPLS Static Labels, on page 44
• How to Configure MPLS Static Labels, on page 45
• Configuration Examples for MPLS Static Labels, on page 49
• Additional References, on page 50
• Feature Information for MPLS Static Labels, on page 51
• Glossary, on page 52

Finding Feature Information

Your software release may not support all the features documented in this module. For the latest caveats and
feature information, see Bug Search Tool and the release notes for your platform and software release. To
find information about the features documented in this module, and to see a list of the releases in which each
feature is supported, see the feature information table at the end of this module.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support.
To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.

Restrictions for MPLS Static Labels

• The trouble shooting process for MPLS static labels is complex.
• On a provider edge (PE) router for MPLS VPNs, there is no mechanism for statically binding a label to
a customer network prefix (VPN IPv4 prefix).
• MPLS static crossconnect labels remain in the LFIB even if the router to which the entry points goes
down.

MPLS Basic MPLS Configuration Guide

43
 MPLS Static Labels
Prerequisites for MPLS Static Labels

• MPLS static crossconnect mappings remain in effect even with topology changes.
• MPLS static labels are not supported for label-controlled Asynchronous Transfer Mode (lc-atm).
• MPLS static bindings are not supported for local prefixes.

Prerequisites for MPLS Static Labels

The network must support the following Cisco IOS features before you enable MPLS static labels:
• Multiprotocol Label Switching (MPLS)
• Cisco Express Forwarding

Information About MPLS Static Labels

MPLS Static Labels Overview
Generally, label switching routers (LSRs) dynamically learn the labels they should use to label-switch packets
by means of label distribution protocols that include:
• Label Distribution Protocol (LDP), the Internet Engineering Task Force (IETF) standard, used to bind
labels to network addresses
• Resource Reservation Protocol (RSVP) used to distribute labels for traffic engineering (TE)
• Border Gateway Protocol (BGP) used to distribute labels for Multiprotocol Label Switching (MPLS)
Virtual Private Networks (VPNs)

To use a learned label to label-switch packets, an LSR installs the label into its Label Forwarding Information
Base (LFIB).
The MPLS Static Labels feature provides the means to configure statically:
• The binding between a label and an IPv4 prefix
• The contents of an LFIB crossconnect entry

Benefits of MPLS Static Labels

Static Bindings Between Labels and IPv4 Prefixes
Static bindings between labels and IPv4 prefixes can be configured to support MPLS hop-by-hop forwarding
through neighbor routers that do not implement LDP label distribution.

MPLS Basic MPLS Configuration Guide

44
 MPLS Static Labels
How to Configure MPLS Static Labels

Static Crossconnects
Static crossconnects can be configured to support MPLS Label Switched Path (LSP) midpoints when neighbor
routers do not implement either the LDP or RSVP label distribution, but do implement an MPLS forwarding
path.

How to Configure MPLS Static Labels

Configuring MPLS Static Prefix Label Bindings
To configure MPLS static prefix/label bindings, use the following commands beginning in global configuration
mode:

SUMMARY STEPS
1. enable
2. configure terminal
3. mpls label range min-label max-label [static min-static-label max-static-label]
4. mpls static binding ipv4 prefix mask [input| output nexthop] label

DETAILED STEPS

Command or Action Purpose

Step 1 enable Enables privileged EXEC mode.
Example: • Enter your password if prompted.

Router> enable

Step 2 configure terminal Enters global configuration mode.

Example:

Router# configure terminal

Step 3 mpls label range min-label max-label [static Specifies a range of labels for use with MPLS Static Labels
min-static-label max-static-label] feature.
Example: (Default is no labels reserved for static assignment.)

Router(config)# mpls label range 200 100000 static

16 199

Step 4 mpls static binding ipv4 prefix mask [input| output Specifies static binding of labels to IPv4 prefixes.
nexthop] label
Bindings specified are installed automatically in the MPLS
Example: forwarding table as routing demands.

Router(config)# mpls static binding ipv4 10.0.0.0

255.0.0.0 55

MPLS Basic MPLS Configuration Guide

45
 MPLS Static Labels
Verifying MPLS Static Prefix Label Bindings

Verifying MPLS Static Prefix Label Bindings

To verify the configuration for MPLS static prefix/label bindings, use this procedure:

SUMMARY STEPS
1. Enter show mpls label range command. The output shows that the new label ranges do not take effect
until a reload occurs:
2. Enter the show mpls static binding ipv4 command to show the configured static prefix/label bindings:
3. Use the show mpls forwarding-table command to determine which static prefix/label bindings are
currently in use for MPLS forwarding.

DETAILED STEPS

Step 1 Enter show mpls label range command. The output shows that the new label ranges do not take effect until a reload
occurs:
Example:

Router# show mpls label range

Downstream label pool: Min/Max label: 16/100000

[Configured range for next reload: Min/Max label: 200/100000]
Range for static labels: Min/Max/Number: 16/199

The following output from the show mpls label range command, executed after a reload, indicates that the new label
ranges are in effect:
Example:

Router# show mpls label range

Downstream label pool: Min/Max label: 200/100000

Range for static labels: Min/Max/Number: 16/199

Step 2 Enter the show mpls static binding ipv4 command to show the configured static prefix/label bindings:
Example:

Router# show mpls static binding ipv4

10.17.17.17/32: Incoming label: 251 (in LIB)
Outgoing labels:
10.0.0.1 18
10.18.18.18/32: Incoming label: 201 (in LIB)
Outgoing labels:
10.0.0.1 implicit-null

Step 3 Use the show mpls forwarding-table command to determine which static prefix/label bindings are currently in use for
MPLS forwarding.
Example:

Router# show mpls forwarding-table

Local Outgoing Prefix Bytes tag Outgoing Next Hop
tag tag or VC or Tunnel Id switched interface
201 Pop tag 10.18.18.18/32 0 PO1/1/0 point2point

MPLS Basic MPLS Configuration Guide

46
 MPLS Static Labels
Configuring MPLS Static Crossconnects

2/35 10.18.18.18/32 0 AT4/1/0.1 point2point

251 18 10.17.17.17/32 0 PO1/1/0 point2point

Configuring MPLS Static Crossconnects

To configure MPLS static crossconnects, use the following command beginning in global configuration mode:

SUMMARY STEPS
1. enable
2. configure terminal
3. mpls label range min-label max-label [static min-static-label max-static-label]
4. mpls static binding ipv4 prefix mask [input| output nexthop] label

DETAILED STEPS

Command or Action Purpose

Step 1 enable Enables privileged EXEC mode.
Example: • Enter your password if prompted.

Router> enable

Step 2 configure terminal Enters global configuration mode.

Example:

Router# configure terminal

Step 3 mpls label range min-label max-label [static Specifies a range of labels for use with MPLS Static Labels
min-static-label max-static-label] feature.
Example: (Default is no labels reserved for static assignment.)

Router(config)# mpls label range 200 100000 static

16 199

Step 4 mpls static binding ipv4 prefix mask [input| output Specifies static binding of labels to IPv4 prefixes.
nexthop] label
Bindings specified are installed automatically in the MPLS
Example: forwarding table as routing demands.

Router(config)# Router(config)# mpls static binding

ipv4 10.0.0.0 255.0.0.0 55

Verifying MPLS Static Crossconnect Configuration

To verify the configuration for MPLS static crossconnects, use this procedure:

MPLS Basic MPLS Configuration Guide

47
 MPLS Static Labels
Monitoring and Maintaining MPLS Static Labels

SUMMARY STEPS
1. Use the show mpls static crossconnect command to display information about crossconnects that have
been configured:

DETAILED STEPS

Use the show mpls static crossconnect command to display information about crossconnects that have been configured:
Example:

Router# show mpls static crossconnect

Local Outgoing Outgoing Next Hop
label label interface
34 22 pos3/0/0 point2point (in LFIB)

Monitoring and Maintaining MPLS Static Labels

To monitor and maintain MPLS static labels, use one or more of the following commands:

SUMMARY STEPS
1. enable
2. show mpls forwarding-table
3. show mpls label range
4. show mpls static binding ipv4
5. show mpls static crossconnect

DETAILED STEPS

Command or Action Purpose

Step 1 enable Enables privileged EXEC mode.
Example: • Enter your password if prompted.

Router> enable

Step 2 show mpls forwarding-table Displays the contents of the MPLS LFIB.
Example:

Router# show mpls forwarding-table

Step 3 show mpls label range Displays information about the static label range.
Example:

Router# show mpls label range

MPLS Basic MPLS Configuration Guide

48
 MPLS Static Labels
Configuration Examples for MPLS Static Labels

Command or Action Purpose

Step 4 show mpls static binding ipv4 Displays information about the configured static prefix/label
bindings.
Example:

Router# show mpls static binding ipv4

Step 5 show mpls static crossconnect Displays information about the configured crossconnects.
Example:

Router# show mpls static crossconnect

Configuration Examples for MPLS Static Labels

Example Configuring MPLS Static Prefixes Labels
In the following output, the mpls label range command reconfigures the range used for dynamically assigned
labels from 16 to 100000 to 200 to 100000 and configures a static label range of 16 to 199.

Router# configure terminal

Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# mpls label range 200 100000 static 16 199
% Label range changes take effect at the next reload.
Router(config)# end

In the following output, the show mpls label range command indicates that the new label ranges do not take
effect until a reload occurs:

Router# show mpls label range

Downstream label pool: Min/Max label: 16/100000

[Configured range for next reload: Min/Max label: 200/100000]
Range for static labels: Min/Max/Number: 16/199

In the following output, the show mpls label range command, executed after a reload, indicates that the new
label ranges are in effect:

Router# show mpls label range

Downstream label pool: Min/Max label: 200/100000

Range for static labels: Min/Max/Number: 16/199

In the following output, the mpls static binding ipv4 commands configure static prefix/label bindings. They
also configure input (local) and output (remote) labels for various prefixes:

Router# configure terminal

Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# mpls static binding ipv4 10.0.0.0 255.0.0.0 55
Router(config)# mpls static binding ipv4 10.0.0.0 255.0.0.0 output 10.0.0.66 2607
Router(config)# mpls static binding ipv4 10.6.0.0 255.255.0.0 input 17
Router(config)# mpls static binding ipv4 10.0.0.0 255.0.0.0 output 10.13.0.8 explicit-null
Router(config)# end

MPLS Basic MPLS Configuration Guide

49
 MPLS Static Labels
Example Configuring MPLS Static Crossconnects

In the following output, the show mpls static binding ipv4 command displays the configured static prefix/label
bindings:

Router# show mpls static binding ipv4

10.0.0.0/8: Incoming label: none;

Outgoing labels:
10.13.0.8 explicit-null
10.0.0.0/8: Incoming label: 55 (in LIB)
Outgoing labels:
10.0.0.66 2607
10.66.0.0/16: Incoming label: 17 (in LIB)
Outgoing labels: None

Example Configuring MPLS Static Crossconnects

In the following output, the mpls static crossconnect command configures a crossconnect from incoming
label 34 to outgoing label 22 out interface pos3/0/0:

Router# configure terminal

Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# mpls static crossconnect 34 pos3/0/0 22
Router(config)# end

In the following output, the show mpls static crossconnect command displays the configured crossconnect:

Router# show mpls static crossconnect

Local Outgoing Outgoing Next Hop
label label interface
34 22 pos3/0/0 point2point (in LFIB)

Additional References
Related Documents

Related Topic Document Title

Cisco IOS commands Cisco IOS Master Commands List, All Releases

MPLS commands Multiprotocol Label Switching Command Reference

Standards

Standard Title

No new or modified standards are supported by this feature, and support for existing standards has not --
been modified by this feature.

MPLS Basic MPLS Configuration Guide

50
 MPLS Static Labels
Feature Information for MPLS Static Labels

MIBs

MIB MIBs Link

No new or modified MIBs are supported by this To locate and download MIBs for selected platforms, Cisco
feature, and support for existing MIBs has not software releases, and feature sets, use Cisco MIB Locator
been modified by this feature. found at the following URL:
http://www.cisco.com/go/mibs

RFCs

RFC Title

No new or modified RFCs are supported by this feature, and support for existing RFCs has not been --
modified by this feature.

Technical Assistance

Description Link

The Cisco Support and Documentation website provides http://www.cisco.com/cisco/web/support/index.html

online resources to download documentation, software,
and tools. Use these resources to install and configure
the software and to troubleshoot and resolve technical
issues with Cisco products and technologies. Access to
most tools on the Cisco Support and Documentation
website requires a Cisco.com user ID and password.

Feature Information for MPLS Static Labels

The following table provides release information about the feature or features described in this module. This
table lists only the software release that introduced support for a given feature in a given software release
train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support.
To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.

Table 1: Feature Information for MPLS Static Labels

Feature Name Releases Feature Information

MPLS Static Labels Cisco IOS XE Amsterdam The MPLS Static Labels feature provides the means to
17.3.2 configure the following items statically:
• The binding between a label and an IPv4 prefix
• The contents of an LFIB crossconnect entry

MPLS Basic MPLS Configuration Guide

51
 MPLS Static Labels
Glossary

Glossary
BGP --Border Gateway Protocol. The predominant interdomain routing protocol used in IP networks.
Border Gateway Protocol --See BGP.
FIB --Forwarding Information Base. A table that contains a copy of the forwarding information in the IP
routing table.
Forwarding Information Base --See FIB.
label --A short, fixed-length identifier that tells switching nodes how the data (packets or cells) should be
forwarded.
label binding --An association between a label and a set of packets, which can be advertised to neighbors so
that a label switched path can be established.
Label Distribution Protocol --See LDP.
Label Forwarding Information Base --See LFIB.
label imposition --The act of putting the first label on a packet.
label switching router --See LSR.
LDP --Label Distribution Protocol. The protocol that supports MPLS hop-by-hop forwarding by distributing
bindings between labels and network prefixes.
LFIB --Label Forwarding Information Base. A data structure in which destinations and incoming labels are
associated with outgoing interfaces and labels.
LSR --label switching router. A Layer 3 router that forwards a packet based on the value of an identifier
encapsulated in the packet.
MPLS --Multiprotocol Label Switching. An industry standard on which label switching is based.
MPLS hop-by-hop forwarding --The forwarding of packets along normally routed paths using MPLS
forwarding mechanisms.
Multiprotocol Label Switching --See MPLS.
Resource Reservation Protocol --See RSVP.
RIB --Routing Information Base. A common database containing all the routing protocols running on a router.
Routing Information Base --See RIB.
RSVP --Resource Reservation Protocol. A protocol for reserving network resources to provide quality of
service guarantees to application flows.
traffic engineering --Techniques and processes used to cause routed traffic to travel through the network on
a path other than the one that would have been chosen if standard routing methods were used.
Virtual Private Network --See VPN.
VPN --Virtual Private Network. A network that enables IP traffic to use tunneling to travel securely over a
public TCP/IP network.

MPLS Basic MPLS Configuration Guide

52
 CHAPTER 6
MPLS Multilink PPP Support
The MPLS Multilink PPP Support feature ensures that MPLS Layer 3 Virtual Private Networks (VPNs) with
quality of service (QoS) can be enabled for bundled links. This feature supports Multiprotocol Label Switching
(MPLS) over Multilink PPP (MLP) links in the edge (provider edge [PE]-to-customer edge [CE]) or in the
MPLS core (PE-to-PE and PE-to-provider [P] device).
Service providers that use relatively low-speed links can use MLP to spread traffic across them in their MPLS
networks. Link fragmentation and interleaving (LFI) should be deployed in the CE-to-PE link for efficiency,
where traffic uses a lower link bandwidth (less than 768 kbps). The MPLS Multilink PPP Support feature can
reduce the number of Interior Gateway Protocol (IGP) adjacencies and facilitate load sharing of traffic.
• Finding Feature Information, on page 53
• Prerequisites for MPLS Multilink PPP Support, on page 53
• Information About MPLS Multilink PPP Support, on page 54
• How to Configure MPLS Multilink PPP Support, on page 58
• Configuration Examples for MPLS Multilink PPP Support, on page 67
• Additional References for MPLS Multilink PPP Support, on page 70
• Feature Information for MPLS Multilink PPP Support, on page 70
• Glossary, on page 71

Finding Feature Information

Your software release may not support all the features documented in this module. For the latest caveats and
feature information, see Bug Search Tool and the release notes for your platform and software release. To
find information about the features documented in this module, and to see a list of the releases in which each
feature is supported, see the feature information table at the end of this module.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support.
To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.

Prerequisites for MPLS Multilink PPP Support

• Cisco Express Forwarding must be enabled.
• Multiprotocol Label Switching (MPLS) must be enabled on provider edge (PE) and provider (P) devices.

MPLS Basic MPLS Configuration Guide

53
 MPLS Multilink PPP Support
Information About MPLS Multilink PPP Support

• Cisco Express Forwarding switching must be enabled on the interface by using the ip route-cache cef
command.

Information About MPLS Multilink PPP Support

MPLS Layer 3 Virtual Private Network Features Supported for Multilink PPP
The table below lists Multiprotocol Label Switching (MPLS) Layer 3 Virtual Private Network (VPN) features
supported for Multilink PPP (MLP) and indicates if the feature is supported on customer edge-to-provider
edge (CE-to-PE) links, PE-to-provider (P) links, and Carrier Supporting Carrier (CSC) CE-to-PE links.

Table 2: MPLS Layer 3 VPN Features Supported for MLP

MPLS L3 VPN Feature CE-to-PE Links PE-to-P Links CSC CE-to-PE Links

Static routes Supported Not supported Not supported

External Border Gateway Supported Not applicable to this Supported

Protocol (eBGP) configuration

Intermediate Not supported Supported Not supported

System-to-Intermediate System
(IS-IS)

Open Shortest Path First (OSPF) Supported Supported Not supported

Enhanced Interior Gateway Supported Supported Not supported

Routing Protocol (EIGRP)

Interprovider interautonomous Not applicable to this Supported (MLP between Not applicable to this
(Inter-AS) VPNs (with Label configuration Autonomous System configuration
Distribution Protocol [LDP]) Boundary Routers
[ASBRs])

Inter-AS VPNs with IPv4 Label Not applicable to this Supported (MLP between Not applicable to this
Distribution configuration ASBRs) configuration

CSC VPNs (with LDP) Not supported Not applicable to this Supported
configuration

CSC VPNs with IPv4 label Supported Not applicable to this Supported
distribution configuration

External and internal BGP Not supported Not supported Not applicable to this
(eiBGP) Multipath configuration

Internal BGP (iBGP) Multipath Not applicable to this Not supported Not applicable to this
configuration configuration

eBGP Multipath Not supported Not supported Not supported

MPLS Basic MPLS Configuration Guide

54
 MPLS Multilink PPP Support
MPLS Quality of Service Features Supported for Multilink PPP

MPLS Quality of Service Features Supported for Multilink PPP

The table below lists the Multiprotocol Label Switching (MPLS) quality of service (QoS) features supported
for Multilink PPP (MLP) and indicates if the feature is supported on customer edge-to-provider edge (CE-to-PE)
links, PE-to-provider (P) links, and Carrier Supporting Carrier (CSC) CE-to-PE links.

Table 3: MPLS QoS Features Supported for MLP

MPLS QoS Feature CE-to-PE Links PE-to-P Links CSC CE-to-PE Links

Default copy of IP Precedence to EXP bits and the Supported Not supported Not supported
reverse

Set MPLS EXP bits using the modular QoS Supported Supported Supported
Command-Line Interface (MQC)

Matching on MPLS EXP using MQC Supported Supported Supported

Low Latency Queueing (LLQ)/Class-Based Weighted Supported Supported Supported

Fair Queueing (CBWFQ) support

Weighted Random Early Detection (WRED) based on Supported Supported Supported

EXP bits using MQC

Policer with EXP bit-marking using MQC-3 action Supported Supported Supported

Support for EXP bits in MPLS accounting Supported Supported Supported

MPLS Multilink PPP Support and PE-to-CE Links

The figure below shows a typical Multiprotocol Label Switching (MPLS) network in which the provider edge
(PE) device is responsible for label imposition (at ingress) and disposition (at egress) of the MPLS traffic.
In this topology, Multilink PPP (MLP) is deployed on the PE-to-customer edge (CE) links. The Virtual Private
Network (VPN) routing and forwarding instance (VRF) interface is in a multilink bundle. There is no MPLS
interaction with MLP; all packets coming into the MLP bundle are IP packets.

MPLS Basic MPLS Configuration Guide

55
 MPLS Multilink PPP Support
MPLS Multilink PPP Support and Core Links

Figure 1: MLP and Traditional PE-to-CE Links

The PE-to-CE routing protocols that are supported for the MPLS Multilink PPP Support feature are external
BGP (eBGP), Open Shortest Path First (OSPF), and Enhanced Interior Gateway Routing Protocol (EIGRP).
Static routes are also supported between the CE and PE device.
Quality of service (QoS) features that are supported for the MPLS Multilink PPP Support feature on CE-to-PE
links are link fragmentation and interleaving (LFI), header compression, policing, marking, and classification.

MPLS Multilink PPP Support and Core Links

The figure below shows a sample topology in which Multiprotocol Label Switching (MPLS) is deployed over
Multilink PPP (MLP) on provider edge-to-provider (PE-to-P) and P-to-P links. Enabling MPLS on MLP for
PE-to-P links is similar to enabling MPLS on MLP for P-to-P links.
Figure 2: MLP on PE-to-P and P-to-P Links

You employ MLP in the PE-to-P or P-to-P links primarily so that you can reduce the number of Interior
Gateway Protocol (IGP) adjacencies and facilitate the load sharing of traffic.

MPLS Basic MPLS Configuration Guide

56
 MPLS Multilink PPP Support
MPLS Multilink PPP Support in a CSC Network

In addition to requiring MLP on the PE-to-P links, the MPLS Multilink PPP Support feature requires the
configuration of an IGP routing protocol and the Label Distribution Protocol (LDP).

MPLS Multilink PPP Support in a CSC Network

The figure below shows a typical Multiprotocol Label Switching (MPLS) Virtual Private Network (VPN)
Carrier Supporting Carrier (CSC) network where Multilink PPP (MLP) is configured on the CSC customer
edge (CE)-to-provider edge (PE) links.
Figure 3: MLP on CSC CE-to-PE Links with MPLS VPN Carrier Supporting Carrier

The MPLS Multilink PPP Support feature supports MLP between CSC-CE and CSC-PE links with the Label
Distribution Protocol (LDP) or with external Border Gateway Protocol (eBGP) IPv4 label distribution. This
feature also supports link fragmentation and interleaving (LFI) for an MPLS VPN CSC configuration. The
figure below shows all MLP links that this feature supports for CSC configurations.
Figure 4: MLP Supported Links with MPLS VPN Carrier Supporting Carrier

MPLS Basic MPLS Configuration Guide

57
 MPLS Multilink PPP Support
MPLS Multilink PPP Support in an Interautonomous System

MPLS Multilink PPP Support in an Interautonomous System

The figure below shows a typical Multiprotocol Label Switching (MPLS) Virtual Private Network (VPN)
interautonomous system (Inter-AS) network where Multilink PPP (MLP) is configured on the provider
edge-to-customer edge (PE-to-CE) links.
Figure 5: MLP on ASBR-to-PE Links in an MPLS VPN Inter-AS Network

The MPLS Multilink PPP Support feature supports MLP between Autonomous System Boundary Router
(ASBR) links for Inter-AS VPNs with Label Distribution Protocol (LDP) and with external Border Gateway
Protocol (eBGP) IPv4 label distribution.

How to Configure MPLS Multilink PPP Support

The tasks in this section can be performed on customer edge-to-provider edge (CE-to-PE) links, PE-to-provider
(P) links, P-to-P links, and Carrier Supporting Carrier (CSC) CE-to-PE links.

Enabling Cisco Express Forwarding

Perform the following task to enable Cisco Express Forwarding. Cisco Express Forwarding is required for
the forwarding of MLP traffic.

Before you begin

Multilink PPP requires the configuration of Cisco Express Forwarding. To find out if Cisco Express Forwarding
is enabled on your device, enter theshow ip cef command. If Cisco Express Forwarding is enabled, you receive
output that looks like the following:

Device# show ip cef

Prefix Next Hop Interface
10.2.61.8/24 192.168.100.1 FastEthernet1/0/0
192.168.101.1 FastEthernet6/1/0

MPLS Basic MPLS Configuration Guide

58
 MPLS Multilink PPP Support
Creating a Multilink Bundle

If Cisco Express Forwarding is not enabled on your platform, the output for the show ip cef command looks
like the following:

Device# show ip cef

%CEF not running

SUMMARY STEPS
1. enable
2. configure terminal
3. ip cef
4. exit

DETAILED STEPS

Command or Action Purpose

Step 1 enable Enables privileged EXEC mode.
Example: • Enter your password if prompted.

Device> enable

Step 2 configure terminal Enters global configuration mode.

Example:

Device# configure terminal

Step 3 ip cef Enables Cisco Express Forwarding.

Example:

Device(config)# ip cef

Step 4 exit Returns to privileged EXEC mode.

Example:

Device(config)# exit

Creating a Multilink Bundle

Perform this task to create a multilink bundle for the MPLS Multilink PPP Support feature. This multilink
bundle can reduce the number of Interior Gateway Protocol (IGP) adjacencies and facilitate load sharing of
traffic.

SUMMARY STEPS
1. enable
2. configure terminal
3. interface multilink group-number
4. ip address address mask [secondary]

MPLS Basic MPLS Configuration Guide

59
 MPLS Multilink PPP Support
Creating a Multilink Bundle

5. encapsulation encapsulation-type
6. ppp multilink
7. end

DETAILED STEPS

Command or Action Purpose

Step 1 enable Enables privileged EXEC mode.
Example: • Enter your password if prompted.

Device> enable

Step 2 configure terminal Enters global configuration mode.

Example:

Device# configure terminal

Step 3 interface multilink group-number Creates a multilink bundle and enters multilink interface
configuration mode.
Example:
• The group-number argument is the number of the
Device(config)# interface multilink 1 multilink bundle (a nonzero number).

Step 4 ip address address mask [secondary] Sets a primary or secondary IP address for an interface.
Example: • The address argument is the IP address.

Device(config-if)# ip address 10.0.0.0 255.255.0.0

• The mask argument is the mask for the associated IP
subnet.
• The secondary keyword specifies that the configured
address is a secondary IP address. If this keyword is
omitted, the configured address is the primary IP
address.

This command is used to assign an IP address to the

multilink interface.

Step 5 encapsulation encapsulation-type Sets the encapsulation method as PPP to be used by the
interface.
Example:
• The encapsulation-type argument specifies the
Device(config-if)# encapsulation ppp encapsulation type.

Step 6 ppp multilink Enables MLP on an interface.

Example:

Device(config-if)# ppp multilink

Step 7 end Returns to privileged EXEC mode.

Example:

MPLS Basic MPLS Configuration Guide

60
 MPLS Multilink PPP Support
Assigning an Interface to a Multilink Bundle

Command or Action Purpose

Device(config-if)# end

Assigning an Interface to a Multilink Bundle

SUMMARY STEPS
1. enable
2. configure terminal
3. controller {t1 | e1} slot/port
4. channel-group channel-number timeslots range
5. exit
6. interface serial slot/subslot/port[.subinterface]
7. ip route-cache [cef]
8. no ip address
9. keepalive [period [retries]]
10. encapsulation encapsulation-type
11. ppp multilink group group-number
12. ppp multilink
13. ppp authentication chap
14. end

DETAILED STEPS

Command or Action Purpose

Step 1 enable Enables privileged EXEC mode.
Example: • Enter your password if prompted.

Device> enable

Step 2 configure terminal Enters global configuration mode.

Example:

Device# configure terminal

Step 3 controller {t1 | e1} slot/port Configures a T1 or E1 controller and enters controller
configuration mode.
Example:
• The t1 keyword indicates a T1 line card.
Device# controller t1 1/3
• The e1 keyword indicates an E1 line card.
• The slot/port arguments are the backplane slot number
and port number on the interface. Refer to your
hardware installation manual for the specific slot
numbers and port numbers.

MPLS Basic MPLS Configuration Guide

61
 MPLS Multilink PPP Support
Assigning an Interface to a Multilink Bundle

Command or Action Purpose

Step 4 channel-group channel-number timeslots range Defines the time slots that belong to each T1 or E1 circuit.
Example: • The channel-number argument is the channel-group
number. When a T1 data line is configured,
Device(config-controller)# channel-group 1 channel-group numbers can be values from 0 to 23.
timeslots 1 When an E1 data line is configured, channel-group
numbers can be values from 0 to 30.
• The timeslots range keyword and argument specifies
one or more time slots or ranges of time slots
belonging to the channel group. The first time slot is
numbered 1. For a T1 controller, the time slot range
is from 1 to 24. For an E1 controller, the time slot
range is from 1 to 31. You can specify a time slot
range (for example, 1-29), individual time slots
separated by commas (for example 1, 3, 5), or a
combination of the two (for example 1-14, 15, 17-31).

Step 5 exit Returns to global configuration mode.

Example:

Device(config-controller)# exit

Step 6 interface serial slot/subslot/port[.subinterface] Configures a serial interface and enters interface
configuration mode.
Example:

Device(config)# interface serial 1/0/0:1

Step 7 ip route-cache [cef] Controls the use of switching methods for forwarding IP
packets.
Example:
• The cef keyword enables Cisco Express Forwarding
Device(config-if)# ip route-cache cef operation on an interface after Cisco Express
Forwarding operation was disabled.

Step 8 no ip address Removes any specified IP address.

Example:

Device(config-if)# no ip address

Step 9 keepalive [period [retries]] Enables keepalive packets and specifies the number of
times that the Cisco software tries to send keepalive packets
Example:
without a response before bringing down the interface or
before bringing the tunnel protocol down for a specific
Device(config-if)# keepalive
interface.
• The period argument is an integer value, in seconds,
greater than 0. The default is 10.

MPLS Basic MPLS Configuration Guide

62
 MPLS Multilink PPP Support
Disabling PPP Multilink Fragmentation

Command or Action Purpose

• The retries argument specifies the number of times
that the device continues to send keepalive packets
without a response before bringing the interface down.
Enter an integer value greater than 1 and less than
255. If you do not enter a value, the value that was
previously set is used; if no value was specified
previously, the default of 5 is used.

If you are using this command with a tunnel interface, the

command specifies the number of times that the device
continues to send keepalive packets without a response
before bringing the tunnel interface protocol down.

Step 10 encapsulation encapsulation-type Sets the encapsulation method used by the interface.
Example: • The encapsulation-type argument specifies the
encapsulation type. The example specifies PPP
Device(config-if)# encapsulation ppp encapsulation.

Step 11 ppp multilink group group-number Restricts a physical link to join only one designated
multilink group interface.
Example:
• The group-number argument is the number of the
Device(config-if)# ppp multilink group 1 multilink bundle (a nonzero number).

Step 12 ppp multilink Enables MLP on the interface.

Example:

Device(config-if)# ppp multilink

Step 13 ppp authentication chap (Optional) Enables Challenge Handshake Authentication

Protocol (CHAP) authentication on the serial interface.
Example:

Device(config-if)# ppp authentication chap

Step 14 end Returns to privileged EXEC mode.

Example:

Device(config-if)# end

Disabling PPP Multilink Fragmentation

Perform this task to disable PPP multilink fragmentation. PPP multilink fragmentation is enabled by default.
Enabling fragmentation reduces the delay latency among bundle links, but adds some load to the CPU.
Disabling fragmentation might produce better throughput.
If your data traffic is consistently of a similar size, we recommend disabling fragmentation. In this case, the
benefits of fragmentation can be outweighed by the added load on the CPU.

MPLS Basic MPLS Configuration Guide

63
 MPLS Multilink PPP Support
Verifying the Multilink PPP Configuration

SUMMARY STEPS
1. enable
2. configure terminal
3. interface type number
4. ppp multilink fragmentation disable
5. end

DETAILED STEPS

Command or Action Purpose

Step 1 enable Enables privileged EXEC mode.
Example: • Enter your password if prompted.

Device> enable

Step 2 configure terminal Enters global configuration mode.

Example:

Device# configure terminal

Step 3 interface type number Configures an interface type and enters interface
configuration mode.
Example:
• The type argument indicates the type of interface to
Device(config)# interface serial 1/0/0 be configured.
• The number argument specifies the port, connector,
or interface card number. The numbers are assigned
at the factory at the time of installation or when the
interface is added to a system, and they can be
displayed with the show interfaces command.

Step 4 ppp multilink fragmentation disable Disables packet fragmentation.

Example:

Device(config-if)# ppp multilink fragmentation

disable

Step 5 end Returns to privileged EXEC mode.

Example:

Device(config-if)# end

Verifying the Multilink PPP Configuration

SUMMARY STEPS
1. enable

MPLS Basic MPLS Configuration Guide

64
 MPLS Multilink PPP Support
Verifying the Multilink PPP Configuration

2. show ip interface brief

3. show ppp multilink
4. show ppp multilink interface interface-bundle
5. show interface type number
6. show mpls forwarding-table
7. exit

DETAILED STEPS

Step 1 enable
Enables privileged EXEC mode. Enter your password if prompted.
Example:

Device> enable
Device#

Step 2 show ip interface brief

Verifies logical and physical Multilink PPP (MLP) interfaces.
Example:
Step 3 show ppp multilink
Verifies that you have created a multilink bundle.
Example:
Step 4 show ppp multilink interface interface-bundle
Displays information about a specific MLP interface.
Example:
Step 5 show interface type number
Displays information about serial interfaces in your configuration.
Example:

Device#

Hardware is Multichannel T1
MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation PPP, LCP Open, multilink Open, crc 16, Data non-inverted
Last input 00:00:01, output 00:00:01, output hang never
Last clearing of "show interface" counters 00:47:13
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
722 packets input, 54323 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort

MPLS Basic MPLS Configuration Guide

65
 MPLS Multilink PPP Support
Verifying the Multilink PPP Configuration

697 packets output, 51888 bytes, 0 underruns

0 output errors, 0 collisions, 1 interface resets
0 output buffer failures, 0 output buffers swapped out
1 carrier transitions no alarm present
Timeslot(s) Used:1, subrate: 64Kb/s, transmit delay is 0 flags
Transmit queue length 25

Device#

Hardware is Multichannel T1
MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation PPP, LCP Open, multilink Open, crc 16, Data non-inverted
Last input 00:00:03, output 00:00:03, output hang never
Last clearing of "show interface" counters 00:47:16
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
725 packets input, 54618 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
693 packets output, 53180 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
0 output buffer failures, 0 output buffers swapped out
1 carrier transitions no alarm present
Timeslot(s) Used:2, subrate: 64Kb/s, transmit delay is 0 flags
Transmit queue length 26

You can also use the show interface command to display information about the multilink interface:
Example:

Device# show interface multilink6

Multilink6 is up, line protocol is up

Hardware is multilink group interface
Internet address is 10.30.0.2/8
MTU 1500 bytes, BW 128 Kbit, DLY 100000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation PPP, LCP Open, multilink Open
Open: CDPCP, IPCP, TAGCP, loopback not set
DTR is pulsed for 2 seconds on reset
Last input 00:00:00, output never, output hang never
Last clearing of "show interface" counters 00:48:43
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
30 second input rate 0 bits/sec, 0 packets/sec
30 second output rate 0 bits/sec, 0 packets/sec
1340 packets input, 102245 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
1283 packets output, 101350 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions

Step 6 show mpls forwarding-table

Displays contents of the Multiprotocol Label Switching (MPLS) Label Forwarding Information Base (LFIB). Look for
information on multilink interfaces associated with a point2point next hop.

MPLS Basic MPLS Configuration Guide

66
 MPLS Multilink PPP Support
Configuration Examples for MPLS Multilink PPP Support

Example:

Device# show mpls forwarding-table

Local Outgoing Prefix Bytes tag Outgoing Next Hop

tag tag or VC or Tunnel Id switched interface
16 Untagged 10.30.0.1/32 0 Mu6 point2point
17 Pop tag 10.0.0.3/32 0 Mu6 point2point
18 Untagged 10.0.0.9/32[V] 0 Mu10 point2point
19 Untagged 10.0.0.11/32[V] 6890 Mu10 point2point
20 Untagged 10.32.0.0/8[V] 530 Mu10 point2point
21 Aggregate 10.34.0.0/8[V] 0
22 Untagged 10.34.0.1/32[V] 0 Mu10 point2point

Use the show ip bgp vpnv4 command to display VPN address information from the Border Gateway Protocol (BGP)
table.
Example:

Device# show ip bgp vpnv4 all summary

BGP router identifier 10.0.0.1, local AS number 100

BGP table version is 21, main routing table version 21
10 network entries using 1210 bytes of memory
10 path entries using 640 bytes of memory
2 BGP path attribute entries using 120 bytes of memory
1 BGP extended community entries using 24 bytes of memory
0 BGP route-map cache entries using 0 bytes of memory
0 BGP filter-list cache entries using 0 bytes of memory
BGP using 1994 total bytes of memory
BGP activity 10/0 prefixes, 10/0 paths, scan interval 5 secs
10.0.0.3 4 100 MsgRc52 MsgSe52 TblV21 0 0 00:46:35 State/P5xRcd

Step 7 exit
Returns to user EXEC mode.
Example:

Device# exit
Device>

Configuration Examples for MPLS Multilink PPP Support

Example: Configuring Multilink PPP on an MPLS CSC PE Device
The following example shows how to configure for Multiprotocol Label Switching (MPLS) Carrier Supporting
Carrier (CSC) provider edge (PE) device.

!
mpls label protocol ldp
ip cef
ip vrf vpn2
rd 200:1
route-target export 200:1

MPLS Basic MPLS Configuration Guide

67
 MPLS Multilink PPP Support
Example: Enabling Cisco Express Forwarding

route-target import 200:1

!

no ip address
encapsulation ppp

ppp multilink
ppp multilink group 1

interface Multilink1
ip vrf forwarding vpn2
ip address 10.35.0.2 255.0.0.0
no peer neighbor-route
load-interval 30
ppp multilink
ppp multilink interleave
ppp multilink group 1

!
!
router ospf 200
log-adjacency-changes
auto-cost reference-bandwidth 1000
redistribute connected subnets
passive-interface Multilink1
network 10.0.0.7 0.0.0.0 area 200
network 10.31.0.0 0.255.255.255 area 200
!
!
router bgp 200
no bgp default ipv4-unicast
bgp log-neighbor-changes
neighbor 10.0.0.11 remote-as 200
neighbor 10.0.0.11 update-source Loopback0
!
address-family vpnv4
neighbor 10.0.0.11 activate
neighbor 10.0.0.11 send-community extended
bgp scan-time import 5
exit-address-family
!
address-family ipv4 vrf vpn2
redistribute connected
neighbor 10.35.0.1 remote-as 300
neighbor 10.35.0.1 activate
neighbor 10.35.0.1 as-override
neighbor 10.35.0.1 advertisement-interval 5
no auto-summary
no synchronization
exit-address-family

Example: Enabling Cisco Express Forwarding

The following example shows how to enable Cisco Express Forwarding for Multilink PPP (MLP)
configurations:

Device> enable
Device# configure terminal
Device(config)# ip cef

MPLS Basic MPLS Configuration Guide

68
 MPLS Multilink PPP Support
Example: Creating a Multilink Bundle

Example: Creating a Multilink Bundle

The following example shows how to create a multilink bundle for the MPLS Multilink PPP Support feature:

Device(config)# interface multilink 1

Device(config-if)# ip address 10.0.0.0 10.255.255.255
Device(config-if)# encapsulation ppp
Device(config-if)# ppp chap hostname group 1
Device(config-if)# ppp multilink
Device(config-if)# ppp multilink group 1

Example: Assigning an Interface to a Multilink Bundle

The following example shows how to create four multilink interfaces with Cisco Express Forwarding switching
and Multilink PPP (MLP) enabled. Each of the newly created interfaces is added to a multilink bundle.

interface multilink1
ip address 10.0.0.0 10.255.255.255
ppp chap hostname group 1
ppp multilink
ppp multilink group 1

no ip address
encapsulation ppp
ip route-cache cef
no keepalive
ppp multilink
ppp multilink group 1

no ip address
encapsulation ppp
ip route-cache cef
no keepalive
ppp chap hostname group 1
ppp multilink
ppp multilink group 1

no ip address
encapsulation ppp
ip route-cache cef
no keepalive
ppp chap hostname group 1
ppp multilink
ppp multilink group 1

no ip address
encapsulation ppp
ip route-cache cef
no keepalive
ppp chap hostname group 1
ppp multilink
ppp multilink group 1

MPLS Basic MPLS Configuration Guide

69
 MPLS Multilink PPP Support
Additional References for MPLS Multilink PPP Support

Additional References for MPLS Multilink PPP Support

Related Documents

Related Topic Document Title

Cisco IOS commands Cisco IOS Master Commands List, All Releases

MPLS commands Cisco IOS Multiprotocol Label Switching Command Reference

Basic MPLS VPNs “MPLS Virtual Private Networks” chapter in the MPLS Layer 3 VPNs Configuration
Guide

RFCs

RFCs Title

RFC 1990 The PPP Multilink Protocol (MP)

Technical Assistance

Description Link

The Cisco Support and Documentation website provides http://www.cisco.com/cisco/web/support/index.html

online resources to download documentation, software,
and tools. Use these resources to install and configure
the software and to troubleshoot and resolve technical
issues with Cisco products and technologies. Access to
most tools on the Cisco Support and Documentation
website requires a Cisco.com user ID and password.

Feature Information for MPLS Multilink PPP Support

The following table provides release information about the feature or features described in this module. This
table lists only the software release that introduced support for a given feature in a given software release
train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support.
To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.

MPLS Basic MPLS Configuration Guide

70
 MPLS Multilink PPP Support
Glossary

Table 4: Feature Information for MPLS Multilink PPP Support

Feature Name Releases Feature Information

MPLS Multilink PPP The MPLS Multilink PPP Support feature ensures that MPLS Layer 3
Support Virtual Private Networks (VPNs) with quality of service (QoS) can be
enabled for bundled links. This feature supports Multiprotocol Label
Switching (MPLS) over Multilink PPP (MLP) links in the edge (provider
edge [PE]-to-customer edge [CE]) or in the MPLS core (PE-to-PE and
PE-to-provider [P]device).

Glossary
bundle—A group of interfaces connected by parallel links between two systems that have agreed to use
Multilink PPP (MLP) over those links.
CBWFQ—class-based weighted fair queueing. A queueing option that extends the standard Weighted Fair
Queueing (WFQ) functionality to provide support for user-defined traffic classes.
Cisco Express Forwarding—A proprietary form of switching that optimizes network performance and
scalability for networks with large and dynamic traffic patterns, such as the Internet, and for networks
characterized by intensive web-based applications or interactive sessions. Although you can use Cisco Express
Forwarding in any part of a network, it is designed for high-performance, highly resilient Layer 3 IP backbone
switching.
EIGRP—Enhanced Interior Gateway Routing Protocol. An advanced version of the Interior Gateway Routing
Protocol (IGRP) developed by Cisco. It provides superior convergence properties and operating efficiency,
and combines the advantages of link-state protocols with those of distance vector protocols.
IGP—Interior Gateway Protocol. An Internet protocol used to exchange routing information within an
autonomous system. Examples of common Internet IGPs include Interior Gateway Routing Protocol (IGRP),
Open Shortest Path First (OSPF), and Routing Information Protocol (RIP).
IGRP—Interior Gateway Routing Protocol. An Interior Gateway Protocol (IGP) developed by Cisco to
address the issues associated with routing in large, heterogeneous networks. Compare with Enhanced Interior
Gateway Routing Protocol (EIGRP).
IS-IS—Intermediate System-to-Intermediate System. An Open Systems Interconnection (OSI) link-state
hierarchical routing protocol, based on DECnet Phase V routing, in which IS-IS devices exchange routing
information based on a single metric to determine network topology.
LCP—Link Control Protocol. A protocol that establishes, configures, and tests data link connections for use
by PPP.
LFI—ink fragmentation and interleaving. The LFI feature reduces delay on slower-speed links by breaking
up large datagrams and interleaving low-delay traffic packets with the smaller packets resulting from the
fragmented datagram. LFI allows reserve queues to be set up so that Real-Time Protocol (RTP) streams can
be mapped into a higher priority queue in the configured weighted fair queue set.
link—One of the interfaces in a bundle.
LLQ—low latency queueing. A quality of service QoS queueing feature that provides a strict priority queue
(PQ) for voice traffic and weighted fair queues for other classes of traffic. It is also called priority
queueing/class-based weighted fair queueing (PQ/CBWFQ).

MPLS Basic MPLS Configuration Guide

71
 MPLS Multilink PPP Support
Glossary

MLP—Multilink PPP. A method of splitting, recombining, and sequencing datagrams across multiple logical
links. The use of MLP increases throughput between two sites by grouping interfaces and then load balancing
packets over the grouped interfaces (called a bundle). Splitting packets at one end, sending them over the
bundled interfaces, and recombining them at the other end achieves load balancing.
MQC—Modular QoS CLI. MQC is a CLI structure that allows users to create traffic polices and attach these
polices to interfaces. MQC allows users to specify a traffic class independently of QoS policies.
NCP—Network Control Protocol. A series of protocols for establishing and configuring different network
layer protocols (such as for AppleTalk) over PPP.
OSPF—Open Shortest Path First. A link-state, hierarchical Interior Gateway Protocol (IGP) routing algorithm
proposed as a successor to Routing Information Protocol (RIP) in the Internet community. OSPF features
include least-cost routing, multipath routing, and load balancing. OSPF was derived from an early version of
the IS-IS protocol.
PPP—Point-to-Point Protocol. A successor to the Serial Line Interface Protocol (SLIP) that provides
device-to-device and host-to-network connections over synchronous and asynchronous circuits. PPP works
with several network layer protocols (such as IP, Internetwork Packet Exchange [IPX], and AppleTalk Remote
Access [ARA]). PPP also has built-in security mechanisms (such as Challenge Handshake Authentication
Protocol [CHAP] and Password Authentication Protocol [PAP]). PPP relies on two protocols: Link Control
Protocol (LCP) and Network Control Protocol (NCP).
RIP—Routing Information Protocol. A version of Interior Gateway Protocol (IGP) that is supplied with UNIX
Berkeley Standard Distribution (BSD) systems. Routing Information Protocol (RIP) is the most common IGP
in the Internet. It uses hop count as a routing metric.
Virtual bundle interface—An interface that represents the master link of a bundle. It is not tied to any
physical interface. Data going over the bundle is transmitted and received through the master link.
WFQ—weighted fair queueing. A congestion management algorithm that identifies conversations (in the
form of traffic streams), separates packets that belong to each conversation, and ensures that capacity is shared
fairly among the individual conversations. WFQ is an automatic way of stabilizing network behavior during
congestion and results in improved performance and reduced retransmission.
WRED—weighted random early detection. A queueing method that ensures that high-precedence traffic has
lower loss rates than other traffic during times of congestion.

MPLS Basic MPLS Configuration Guide

72
 CHAPTER 7
6PE Multipath
The 6PE multipath feature uses multiprotocol internal BGP (MP-iBGP) to distribute IPv6 routes over the
MPLS IPv4 core network and to attach an MPLS label to each route
• Finding Feature Information, on page 73
• Information About 6PE Multipath, on page 73
• How to Configure 6PE Multipath, on page 74
• Configuration Examples for 6PE Multipath, on page 75
• Additional References, on page 75
• Feature Information for 6PE Multipath, on page 76

Finding Feature Information

Your software release may not support all the features documented in this module. For the latest caveats and
feature information, see Bug Search Tool and the release notes for your platform and software release. To
find information about the features documented in this module, and to see a list of the releases in which each
feature is supported, see the feature information table at the end of this module.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support.
To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.

Information About 6PE Multipath

6PE Multipath
Internal and external BGP multipath for IPv6 allows the IPv6 device to load balance between several paths
(for example, the same neighboring autonomous system or subautonomous system, or the same metric) to
reach its destination. The 6PE multipath feature uses MP-iBGP to distribute IPv6 routes over the MPLS IPv4
core network and to attach an MPLS label to each route.
When MP-iBGP multipath is enabled on the 6PE device, all labeled paths are installed in the forwarding table
with MPLS information (label stack) when MPLS information is available. This functionality enables 6PE
to perform load balancing.

MPLS Basic MPLS Configuration Guide

73
 6PE Multipath
How to Configure 6PE Multipath

How to Configure 6PE Multipath

Configuring IBGP Multipath Load Sharing
Perform this task to configure IBGP multipath load sharing and control the maximum number of parallel
IBGP routes that can be installed in a routing table.

SUMMARY STEPS
1. enable
2. configure terminal
3. router bgp as-number
4. address-family ipv6 [unicast]
5. maximum-paths ibgp number-of-paths

DETAILED STEPS

Command or Action Purpose

Step 1 enable Enables privileged EXEC mode.
Example: • Enter your password if prompted.

Device> enable

Step 2 configure terminal Enters global configuration mode.

Example:

Device# configure terminal

Step 3 router bgp as-number Enters router configuration mode for the specified routing
process.
Example:

Device(config)# router bgp 65000

Step 4 address-family ipv6 [unicast] Specifies the IPv6 address family and enters address family
configuration mode.
Example:
• The unicast keyword specifies the IPv6 unicast address
Device(config-router)# address-family ipv6 family. By default, the device is placed in configuration
mode for the IPv6 unicast address family if the unicast
keyword is not specified with the address-family ipv6
command.

Step 5 maximum-paths ibgp number-of-paths Controls the maximum number of parallel IBGP routes that
can be installed in a routing table.
Example:

Device(config-router)# maximum-paths ibgp 3

MPLS Basic MPLS Configuration Guide

74
 6PE Multipath
Configuration Examples for 6PE Multipath

Configuration Examples for 6PE Multipath

Example: Configuring 6PE Multipath
Device# show ipv6 cef internals
IPv6 CEF is enabled and running
Slow processing intvl = 1 seconds backoff level current/max 0/0
0 unresolved prefixes, 0 requiring adjacency update
IPv6 CEF default table
14 prefixes tableid 0
table version 17
root 6283F5D0

Additional References
Related Documents

Related Topic Document Title

IPv6 addressing and connectivity IPv6 Configuration Guide

Cisco IOS commands Master Commands List, All

Releases

IPv6 commands IPv6 Command Reference

Cisco IOS IPv6 features IPv6 Feature Mapping

Standards and RFCs

Standard/RFC Title

RFCs for IPv6 RFCs

IPv6

Technical Assistance

Description Link

The Cisco Support and Documentation website provides http://www.cisco.com/cisco/web/support/index.html

online resources to download documentation, software,
and tools. Use these resources to install and configure
the software and to troubleshoot and resolve technical
issues with Cisco products and technologies. Access to
most tools on the Cisco Support and Documentation
website requires a Cisco.com user ID and password.

MPLS Basic MPLS Configuration Guide

75
 6PE Multipath
Feature Information for 6PE Multipath

Feature Information for 6PE Multipath

The following table provides release information about the feature or features described in this module. This
table lists only the software release that introduced support for a given feature in a given software release
train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support.
To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.

Table 5: Feature Information for 6PE Multipath

Feature Name Releases Feature Information

6PE Multipath The 6PE multipath feature uses

MP-iBGP to distribute IPv6 routes
over the MPLS IPv4 core network
and to attach an MPLS label to each
route.
The following commands were
introduced or modified:
maximum-paths ibgp, router bgp,
show ipv6 cef internals.

MPLS Basic MPLS Configuration Guide

76
 CHAPTER 8
IPv6 Switching: Provider Edge Router over MPLS
Multiprotocol Label Switching (MPLS) is deployed by many service providers in their IPv4 networks. Service
providers want to introduce IPv6 services to their customers, but changes to their existing IPv4 infrastructure
can be expensive and the cost benefit for a small amount of IPv6 traffic does not make economic sense. Several
integration scenarios have been developed to leverage an existing IPv4 MPLS infrastructure and add IPv6
services without requiring any changes to the network backbone. This document describes how to implement
IPv6 over MPLS.
• Finding Feature Information, on page 77
• Prerequisites for IPv6 Switching: Provider Edge Router over MPLS, on page 77
• Information About IPv6 Switching: Provider Edge Router over MPLS, on page 78
• How to Deploy IPv6 Switching: Provider Edge Router over MPLS, on page 79
• Configuration Examples for IPv6 Switching: Provider Edge Router over MPLS, on page 84
• Additional References for IPv6 Switching: Provider Edge Router over MPLS, on page 86
• Feature Information for IPv6 Switching: Provider Edge Router over MPLS, on page 87

Finding Feature Information

Your software release may not support all the features documented in this module. For the latest caveats and
feature information, see Bug Search Tool and the release notes for your platform and software release. To
find information about the features documented in this module, and to see a list of the releases in which each
feature is supported, see the feature information table at the end of this module.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support.
To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.

Prerequisites for IPv6 Switching: Provider Edge Router over

MPLS
Before the IPv6 Provider Edge Router over MPLS (6PE) feature can be implemented, MPLS must be running
over the core IPv4 network. If Cisco devices are used, Cisco Express Forwarding or distributed Cisco Express
Forwarding must be enabled for both IPv4 and IPv6 protocols. This module assumes that you are familiar
with MPLS.

MPLS Basic MPLS Configuration Guide

77
 IPv6 Switching: Provider Edge Router over MPLS
Information About IPv6 Switching: Provider Edge Router over MPLS

Information About IPv6 Switching: Provider Edge Router over

MPLS
Benefits of Deploying IPv6 over MPLS Backbones
IPv6 over MPLS backbones enables isolated IPv6 domains to communicate with each other over an MPLS
IPv4 core network. This implementation requires only a few backbone infrastructure upgrades and no
reconfiguration of core devices because forwarding is based on labels rather than the IP header itself, providing
a very cost-effective strategy for the deployment of IPv6.
Additionally, the inherent Virtual Private Network (VPN) and MPLS traffic engineering (MPLS-TE) services
available within an MPLS environment allow IPv6 networks to be combined into IPv4 VPNs or extranets
over an infrastructure supporting IPv4 VPNs and MPLS-TE.

IPv6 on the Provider Edge Devices

The Cisco implementation of IPv6 Provider Edge Router over MPLS is called 6PE, and it enables IPv6 sites
to communicate with each other over an MPLS IPv4 core network using MPLS label switched paths (LSPs).
This feature relies on multiprotocol Border Gateway Protocol (BGP) extensions in the IPv4 network
configuration on the provider edge (PE) device to exchange IPv6 reachability information in addition to an
MPLS label for each IPv6 address prefix to be advertised. Edge devices are configured to be dual stack running
both IPv4 and IPv6, and use the IPv4 mapped IPv6 address for IPv6 prefix reachability exchange.
A hierarchy of labels is imposed on the 6PE ingress device to keep the IPv6 traffic transparent to all the core
devices. The top label provides connectivity inside the IPv4 MPLS core network and the label is distributed
by Label Distribution Protocol (LDP), Tag Distribution Protocol (TDP), or Resource Reservation Protocol
(RSVP). TDP and LDP can both be used for label distribution, but RSVP is used only in the context of
MPLS-TE label exchange. The bottom label, automatically assigned to the IPv6 prefix of the destination, is
distributed by multiprotocol BGP and used at each 6PE egress device for IPv6 forwarding.
In the figure below the 6PE devices are configured as dual stack devices able to route both IPv4 and IPv6
traffic. Each 6PE device is configured to run LDP, TDP, or RSVP (if traffic engineering is configured) to
bind the IPv4 labels. The 6PE devices use multiprotocol BGP to exchange reachability information with the
other 6PE devices within the MPLS domain, and to distribute IPv6 labels between them. All 6PE and core
devices--P devices in Figure 3--within the MPLS domain share a common IPv4 Interior Gateway Protocol
(IGP) such as Open Shortest Path First (OSPF) or Integrated Intermediate System-to-Intermediate System
(IS-IS).

MPLS Basic MPLS Configuration Guide

78
 IPv6 Switching: Provider Edge Router over MPLS
How to Deploy IPv6 Switching: Provider Edge Router over MPLS

Figure 6: 6PE Device Topology

The interfaces on the 6PE devices connecting to the CE device can be configured to forward IPv6 traffic, IPv4
traffic, or both types of traffic depending on the customer requirements. 6PE devices advertise IPv6 reachability
information learned from their 6PE peers over the MPLS cloud. Service providers can delegate an IPv6 prefix
from their registered IPv6 prefixes over the 6PE infrastructure; otherwise, there is no impact on the CE device.
The P devices in the core of the network are not aware that they are switching IPv6 packets. Core devices are
configured to support MPLS and the same IPv4 IGP as the PE devices to establish internal reachability inside
the MPLS cloud. Core devices also use LDP, TDP, or RSVP for binding IPv4 labels. Implementing the Cisco
6PE feature does not have any impact on the MPLS core devices.
Within the MPLS network, IPv6 traffic is forwarded using label switching, making the IPv6 traffic transparent
to the core of the MPLS network. No IPv6 over IPv4 tunnels or Layer 2 encapsulation methods are required.

How to Deploy IPv6 Switching: Provider Edge Router over MPLS

Deploying IPv6 on the Provider Edge Devices (6PE)
Specifying the Source Address Interface on a 6PE Device
Two configuration tasks using the network shown in the figure below are required at the 6PE1 device to enable
the 6PE feature.
The customer edge device--CE1 in the figure below--is configured to forward its IPv6 traffic to the 6PE1
device. The P1 device in the core of the network is assumed to be running MPLS, a label distribution protocol,
an IPv4 IGP, and Cisco Express Forwarding or distributed Cisco Express Forwarding, and does not require
any new configuration to enable the 6PE feature.

MPLS Basic MPLS Configuration Guide

79
 IPv6 Switching: Provider Edge Router over MPLS
Specifying the Source Address Interface on a 6PE Device

Figure 7: 6PE Configuration Example

Before you begin

• The 6PE devices--the 6PE1 and 6PE2 devices in the figure below--must be members of the core IPv4
network. The 6PE device interfaces attached to the core network must be running MPLS, the same label
distribution protocol, and the same IPv4 IGP, as in the core network.
• The 6PE devices must also be configured to be dual stack to run both IPv4 and IPv6.

SUMMARY STEPS
1. enable
2. configure terminal
3. ipv6 unicast-routing
4. ipv6 cef
5. interface type number
6. ipv6 address ipv6-address / prefix-length | prefix-name sub-bits / prefix-length

DETAILED STEPS

Command or Action Purpose

Step 1 enable Enables privileged EXEC mode.
Example: • Enter your password if prompted.

Device> enable

Step 2 configure terminal Enters global configuration mode.

Example:

Device# configure terminal

Step 3 ipv6 unicast-routing Enables the forwarding of IPv6 unicast datagrams.

Example:

Device(config)# ipv6 unicast-routing

Step 4 ipv6 cef Enables IPv6 Cisco Express Forwarding.

Example:

MPLS Basic MPLS Configuration Guide

80
 IPv6 Switching: Provider Edge Router over MPLS
Binding and Advertising the 6PE Label to Advertise Prefixes

Command or Action Purpose

Device(config)# ipv6 cef

Step 5 interface type number Specifies an interface type and number and enters interface
configuration mode.
Example:
• In the context of this feature, the interface to be
Device(config)# interface configured is the interface communicating with the
CE device.

Step 6 ipv6 address ipv6-address / prefix-length | prefix-name Configures an IPv6 address based on an IPv6 general prefix
sub-bits / prefix-length and enable IPv6 processing on an interface.
Example:

Device(config-if)# ipv6 address 2001:DB8:FFFF::2/64

Binding and Advertising the 6PE Label to Advertise Prefixes

Perform this task to enable the binding and advertising of labels when advertising IPv6 prefixes to a specified
BGP neighbor.

SUMMARY STEPS
1. enable
2. configure terminal
3. router bgp as-number
4. no bgp default ipv4-unicast
5. neighbor {ip-address | ipv6-address | peer-group-name} remote-as as-number
6. neighbor { ip-address | ipv6-address | peer-group-name} update-source interface-type interface-number
7. address-family ipv6 [unicast]
8. neighbor {ip-address | peer-group-name| ipv6-address} activate
9. neighbor {ip-address | ipv6-address} send-label

DETAILED STEPS

Command or Action Purpose

Step 1 enable Enables privileged EXEC mode.
Example: • Enter your password if prompted.

Device> enable

Step 2 configure terminal Enters global configuration mode.

Example:

Device# configure terminal

MPLS Basic MPLS Configuration Guide

81
 IPv6 Switching: Provider Edge Router over MPLS
Binding and Advertising the 6PE Label to Advertise Prefixes

Command or Action Purpose

Step 3 router bgp as-number Enters router configuration mode for the specified routing
process.
Example:

Device(config)# router bgp 65000

Step 4 no bgp default ipv4-unicast Disables the IPv4 unicast address family for the BGP
routing process specified in the previous step.
Example:
Note Routing information for the IPv4 unicast address
Device(config-router)# no bgp default ipv4-unicast family is advertised by default for each BGP
routing session configured with the neighbor
remote-as command unless you configure the
no bgp default ipv4-unicastcommand before
configuring the neighbor remote-as command.

Step 5 neighbor {ip-address | ipv6-address | peer-group-name} Adds the IP address of the neighbor in the specified
remote-as as-number autonomous system to the BGP neighbor table of the local
device.
Example:

Device(config-router)# neighbor 192.168.99.70

remote-as 65000

Step 6 neighbor { ip-address | ipv6-address | peer-group-name} Specifies the interface whose IPv4 address is to be used as
update-source interface-type interface-number the source address for the peering.
Example: • In the context of this task, the interface must have an
IPv4 address with a 32-bit mask configured. Use of a
Device(config-router)# neighbor 192.168.99.70 loopback interface is recommended. This address is
update-source Loopback 0 used to determine the IPv6 next hop by the peer 6PE.

Step 7 address-family ipv6 [unicast] Specifies the IPv6 address family and enters address family
configuration mode.
Example:
• The unicast keyword specifies the IPv6 unicast address
Device(config-router)# address-family ipv6 family. By default, the device is placed in configuration
mode for the IPv6 unicast address family if the unicast
keyword is not specified with the address-family ipv6
command.

Step 8 neighbor {ip-address | peer-group-name| ipv6-address} Enables the neighbor to exchange prefixes for the IPv6
activate address family with the local device.
Example:

Device(config-router-af)# neighbor 192.168.99.70

activate

Step 9 neighbor {ip-address | ipv6-address} send-label Advertises the capability of the device to send MPLS labels
with BGP routes.
Example:

MPLS Basic MPLS Configuration Guide

82
 IPv6 Switching: Provider Edge Router over MPLS
Configuring IBGP Multipath Load Sharing

Command or Action Purpose

• In IPv6 address family configuration mode this
Device(config-router-af)# neighbor 192.168.99.70
command enables binding and advertisement of labels
send-label
when advertising IPv6 prefixes in BGP.

Configuring IBGP Multipath Load Sharing

Perform this task to configure IBGP multipath load sharing and control the maximum number of parallel
IBGP routes that can be installed in a routing table.

SUMMARY STEPS
1. enable
2. configure terminal
3. router bgp as-number
4. address-family ipv6 [unicast]
5. maximum-paths ibgp number-of-paths

DETAILED STEPS

Command or Action Purpose

Step 1 enable Enables privileged EXEC mode.
Example: • Enter your password if prompted.

Device> enable

Step 2 configure terminal Enters global configuration mode.

Example:

Device# configure terminal

Step 3 router bgp as-number Enters router configuration mode for the specified routing
process.
Example:

Device(config)# router bgp 65000

Step 4 address-family ipv6 [unicast] Specifies the IPv6 address family and enters address family
configuration mode.
Example:
• The unicast keyword specifies the IPv6 unicast address
Device(config-router)# address-family ipv6 family. By default, the device is placed in configuration
mode for the IPv6 unicast address family if the unicast
keyword is not specified with the address-family ipv6
command.

Step 5 maximum-paths ibgp number-of-paths Controls the maximum number of parallel IBGP routes that
can be installed in a routing table.
Example:

MPLS Basic MPLS Configuration Guide

83
 IPv6 Switching: Provider Edge Router over MPLS
Configuration Examples for IPv6 Switching: Provider Edge Router over MPLS

Command or Action Purpose

Device(config-router)# maximum-paths ibgp 3

Configuration Examples for IPv6 Switching: Provider Edge

Router over MPLS
Example: Provider Edge Device
The 6PE device is configured for both IPv4 and IPv6 traffic. Gigabit Ethernet interface 0/0/0 is configured
with an IPv4 address and is connected to a device in the core of the network. Integrated IS-IS and TDP
configurations on this device are similar to the P1 device.
Device 6PE1 exchanges IPv6 routing information with another 6PE device using internal BGP (IBGP)
established over an IPv4 connection so that all the neighbor commands use the IPv4 address of the 6PE2
device. All the BGP peers are within autonomous system 65000, so synchronization with IGP is turned off
for IPv4. In IPv6 address family configuration mode, synchronization is disabled by default.
IPv6 and Cisco Express Forwarding for IPv6 are enabled, the 6PE2 neighbor is activated, and label binding
and advertisement is enabled for IPv6 prefixes using the neighbor send-label command. Connected and static
IPV6 routes are redistributed using BGP.

Note MPLS is not supported on IPv6.

Example: Core Device

In the following example, the device in the core of the network is running MPLS, IS-IS, and IPv4 only. The
Gigabit Ethernet interfaces are configured with IPv4 address and are connected to the 6PE devices. IS-IS is
the IGP for this network and the P1 and 6PE devices are in the same IS-IS area 49.0001. Tag Distribution
Protocol (TDP) and tag switching are enabled on both the Gigabit Ethernet interfaces. Cisco Express Forwarding
is enabled in global configuration mode.

ip cef
!
tag-switching tdp router-id Loopback0
!
interface Loopback0
ip address 192.168.99.200 255.255.255.255
!
interface GigabitEthernet0/0/0
description to_6PE1
ip address 192.168.99.2 255.255.255.252
ip router isis
tag-switching ip
!
interface GigabitEthernet0/1/0
description to_6PE2
ip address 192.168.99.66 255.255.255.252

MPLS Basic MPLS Configuration Guide

84
 IPv6 Switching: Provider Edge Router over MPLS
Example: Monitoring 6PE

ip router isis
tag-switching ip
router isis
passive-interface Loopback0
net 49.0001.1921.6809.9200.00

Example: Monitoring 6PE

In the following example, output information about an IPv6 route is displayed using the show bgp
ipv6 command with an IPv6 prefix:
Device# show bgp ipv6 2001:DB8:DDDD::/48

BGP routing table entry for 2001:DB8:DDDD::/48, version 15

Paths: (1 available, best #1, table Global-IPv6-Table)
Not advertised to any peer
Local
::FFFF:192.168.99.70 (metric 20) from 192.168.99.70 (192.168.99.70)
Origin IGP, localpref 100, valid, internal, best

In the following example, output information about a BGP peer including the IPv6 label capability
is displayed using the show bgp ipv6 neighbors command with an IP address:
Device# show bgp ipv6 neighbors 192.168.99.70

BGP neighbor is 192.168.99.70, remote AS 65000, internal link

BGP version 4, remote router ID 192.168.99.70
BGP state = Established, up for 00:05:17
Last read 00:00:09, hold time is 0, keepalive interval is 60 seconds
Neighbor capabilities:
Route refresh: advertised and received
Address family IPv6 Unicast: advertised and received
ipv6 MPLS Label capability: advertised and received
Received 54 messages, 0 notifications, 0 in queue
Sent 55 messages, 1 notifications, 0 in queue
Default minimum time between advertisement runs is 5 seconds

For address family: IPv6 Unicast

BGP table version 21880, neighbor version 21880
Index 1, Offset 0, Mask 0x2
Route refresh request: received 0, sent 0
77 accepted prefixes consume 4928 bytes
Prefix advertised 4303, suppressed 0, withdrawn 1328
Number of NLRIs in the update sent: max 1, min 0

In the following example, output information linking the MPLS label with prefixes is displayed using
the show mpls forwarding-table command. If the 6PE feature is configured, the labels are aggregated
because there are several prefixes for one local label, and the prefix column contains IPv6 instead
of a target prefix.
Device# show mpls forwarding-table

Local Outgoing Prefix Bytes Label Outgoing Next Hop

Label Label or Tunnel Id Switched interface
16 Pop Label 1.1.1.1/32 0 Et0/0 10.0.0.1
18 No Label nh-id(1) 0 Et2/0 10.0.2.2
19 No Label nh-id(2) 0 Et1/0 10.0.1.2
20 No Label nh-id(3) 0 Et1/0 10.0.1.2
22 No Label nh-id(5) 0 Et1/0 10.0.1.2
24 No Label nh-id(5) 0 Et2/0 10.0.2.2

MPLS Basic MPLS Configuration Guide

85
 IPv6 Switching: Provider Edge Router over MPLS
Additional References for IPv6 Switching: Provider Edge Router over MPLS

In the following example, output information about the top of the stack label with label switching
information is displayed using the show bgp ipv6 command with the labels keyword:
Device# show bgp ipv6 labels

Network Next Hop In tag/Out tag

2001:DB8:DDDD::/64 ::FFFF:192.168.99.70 notag/20

In the following example, output information about labels from the Cisco Express Forwarding table
is displayed using the show ipv6 cef command with an IPv6 prefix:
Device# show ipv6 cef 2001:DB8:DDDD::/64

2001:DB8:DDDD::/64
nexthop ::FFFF:192.168.99.70
fast tag rewrite with Se0/0, point2point, tags imposed {19 20}

In the following example, output information from the IPv6 routing table is displayed using the show
ipv6 route command. The output shows the IPv6 MPLS virtual interface as the output interface of
IPv6 routes forwarded across the MPLS cloud. This example shows output from the 6PE1 router.
The 6PE2 router has advertised the IPv6 prefix of 2001:DB8:dddd::/48 configured for the CE2 router
and the next-hop address is the IPv4-compatible IPv6 address ::ffff:192.168.99.70, where
192.168.99.70 is the IPv4 address of the 6PE2 router.
Device# show ipv6 route

IPv6 Routing Table - 10 entries

Codes: C - Connected, L - Local, S - Static, R - RIP, B - BGP
I1 - ISIS L1, I2 - ISIS L2, IA - ISIS interarea
B 2001:DB8:DDDD::/64 [200/0]
via ::FFFF:192.168.99.70, IPv6-mpls
B 2001:DB8:DDDD::/64 [200/0]
via ::FFFF:192.168.99.70, IPv6-mpls
L 2001:DB8:FFFF::1/128 [0/0]
via ::, GigabitEthernet0/0/0
C 2001:DB8:FFFF::/64 [0/0]
via ::, GigabitEthernet0/0/0
S 2001:DB8:FFFF::/48 [1/0]
via 2001:DB8:B00:FFFF::2, GigabitEthernet0/0/0

Additional References for IPv6 Switching: Provider Edge Router

over MPLS
Related Documents

Related Topic Document Title

IPv6 addressing and connectivity IPv6 Configuration Guide

Cisco IOS commands Master Commands List, All

Releases

IPv6 commands IPv6 Command Reference

Cisco IOS IPv6 features IPv6 Feature Mapping

MPLS Basic MPLS Configuration Guide

86
 IPv6 Switching: Provider Edge Router over MPLS
Feature Information for IPv6 Switching: Provider Edge Router over MPLS

Standards and RFCs

Standard/RFC Title

RFCs for IPv6 RFCs

IPv6

Technical Assistance

Description Link

The Cisco Support and Documentation website provides http://www.cisco.com/cisco/web/support/index.html

online resources to download documentation, software,
and tools. Use these resources to install and configure
the software and to troubleshoot and resolve technical
issues with Cisco products and technologies. Access to
most tools on the Cisco Support and Documentation
website requires a Cisco.com user ID and password.

Feature Information for IPv6 Switching: Provider Edge Router

over MPLS
The following table provides release information about the feature or features described in this module. This
table lists only the software release that introduced support for a given feature in a given software release
train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support.
To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.

Table 6: Feature Information for IPv6 Switching: Provider Edge Router over MPLS

Feature Name Releases Feature Information

IPv6 Switching: Provider Edge Cisco IOS XE Amsterdam 17.3.2 The Cisco implementation of IPv6
Router over MPLS Provider Edge Router over MPLS
enables IPv6 sites to communicate
with each other over an MPLS IPv4
core network using MPLS LSPs.

MPLS Basic MPLS Configuration Guide

87
 IPv6 Switching: Provider Edge Router over MPLS
Feature Information for IPv6 Switching: Provider Edge Router over MPLS

MPLS Basic MPLS Configuration Guide

88