Operating Instructions: 28/1543-AXI 101 09/1 Uen J

LDP
Operating Instructions
28/1543-AXI 101 09/1 Uen J

Copyright
© Ericsson AB 2017. All rights reserved. No part of this document may be

reproduced in any form without the written permission of the copyright owner.
Disclaimer
The contents of this document are subject to revision without notice due to
continued progress in methodology, design and manufacturing. Ericsson shall
have no liability for any error or damage of any kind resulting from the use of
this document.
28/1543-AXI 101 09/1 Uen J | 2017-11-22

Contents
Contents
1 Overview 1
1.1 About LDP 1
1.2 Prerequisites 10
1.3 Restrictions 11
2 Configuration 12
2.1 Configuration Command Hierarchy 12
2.2 Configure Basic LDP Label Distribution 13
2.3 Set a Router ID 16
2.4 Configure Hello Messages 18
2.5 Configure the Transport Address 19
2.6 Authenticate Sessions 21
2.7 Configure Extended Neighbor Discovery 23
2.8 Configure Targeted Hello Messages 25
2.9 Advertise an Explicit-Null Label 27
2.10 Propagate the IGP Route Metric to LSPs 28
2.11 Filter Label Advertisements 30
2.12 Enable ECMP on a P Router (Transit Node) 32
2.13 Create LSP Pseudocircuits for Statistics Collection 34
2.14 Modify the Number of Allowed Sessions 37
2.15 Configure Graceful Restart 38
2.16 Disable LDP LFA for IP FRR 38
2.17 Enable Multipoint Label Distribution Protocol 39
2.18 Configure mLDP FRR Link Protection 43
3 Operations 48
4 LDP Glossary 49
Reference List 51
28/1543-AXI 101 09/1 Uen J | 2017-11-22

LDP
28/1543-AXI 101 09/1 Uen J | 2017-11-22

Overview
1 Overview
This document provides an overview of the Label Distribution Protocol (LDP)

and describes the tasks and commands used to configure, monitor,
troubleshoot, and administer LDP features.
1.1 About LDP

The Ericsson IP Operating System implementation of LDP supports the
standards listed in .
LDP enables dynamic label allocation and distribution in a Multiprotocol Label

Switching (MPLS) network. A Label-Switched Router (LSR) enabled with LDP
can establish Label-Switched Paths (LSPs) to other LSRs in the network. LDP
creates label bindings by assigning labels to connected routers and
advertising the bindings to neighbors.
LDP also assigns labels to label bindings learned from neighbors and
advertises the binding to other neighbors. When an LSR advertises a label
binding for a route, the LSR is advertising the availability of an LSP to the
destination of that route. LDP can learn several LSPs from different neighbors
for the same route. In this case, LDP activates only the path selected by the
underlying Interior Gateway Protocol (IGP). For this reason, LDP must work
together with an IGP, such as the Intermediate System-to-Intermediate System
(IS-IS) or Open Shortest Path First (OSPF) protocol.
To discover LDP peers, an LSR periodically transmits LDP Hello messages.

After two LDP peers discover each other, LDP establishes a Transmission
Control Protocol (TCP) connection between them. When the TCP connection
is complete, an LDP session is established. The Ericsson implementation
uses the LDP router ID as the LDP transport address.
During the LDP session, LSRs send LDP label mapping and withdrawal
messages. LSRs allocate labels to directly connected interfaces and learn
about labels from neighbors. If a directly connected interface is shut down, an
LSR withdraws the label and stops advertising it to neighbors. If a neighbor
stops advertising a label to an LSR, the label is withdrawn from Label
Forwarding Information Base (LFIB) of that LSR. Teardown of LDP
adjacencies or sessions results if Hello or keepalive messages are not
received within the timer interval.
The router supports a maximum of 1,024 targeted LDP sessions or a

combination of up to 128 nontargeted sessions and 896 targeted sessions.
Use the max-session command to configure the maximum number of LDP
sessions supported on the router.
28/1543-AXI 101 09/1 Uen J | 2017-11-22 1

LDP
1.1.1 LDP Neighbor Discovery

LDP has two types of neighbor discovery mechanisms: basic and extended.
Basic LDP discovery discovers immediate neighbors. Extended LDP discovery
discovers neighbors that can be multiple hops away.
1.1.2 LDP Hello Messages

LDP has two types of Hello messages: link and targeted. Link Hello messages
are multicast on an interface to immediate neighbors and are used in basic
LDP discovery. Targeted Hello messages are unicast directly to remote
neighbors and are used in extended LDP discovery. Two LDP-speaking LSRs
can form LDP adjacencies after discovering each other. LDP adjacencies
discovered by link Hello are link Hello adjacencies. LDP adjacencies
discovered by targeted Hello are targeted Hello adjacencies.
1.1.3 Label Advertisement Completion

After an LDP session is established, an LDP speaker can signal to its peer
that it has advertised all labels in its Label Information Base (LIB) (RFC
5919, ). This signaling is known as end-of-LIB notification.
Sending an end-of-LIB notification to a peer can be useful in the following

scenarios in downstream unsolicited mode:
• When LDP-IGP synchronization procedures are used (RFC 5443, ). After

receiving notification that label advertisement is complete, the LDP
speaker considers LDP to be fully operational for the link and signals the
IGP to start advertising the link with normal cost.
• Following LDP session reestablishment when graceful restart is applied

(RFC 3478, ). Receiving notification that label advertisement is complete
enables an LDP speaker to stop using stale forwarding information
learned from the peer without waiting until the recovery timer expires.
An end-of-LIB notification is sent only if the peer advertised an unrecognized

notification capability and a typed wildcard FEC capability during session
establishment.
1.1.3.1 Determine Unrecognized Notification Capability
An LDP speaker that supports end-of-LIB notification must send a capability

parameter in its initialization message indicating that it ignores notification
messages that carry a status Type-Length-Value (TLV) with an unrecognized
status code.
The unrecognized notification capability TLV must be set as follows:
• U: 1
2 28/1543-AXI 101 09/1 Uen J | 2017-11-22

Overview
• F: 0
• Unrecognized Notification: 0x0603
• S: 1
Use the show ldp neighbor command to determine the unrecognized

notification capability of a peer. If the U flag is set to Unrecognized
Notification Capable, the LDP peer is capable of unrecognized
notification. For an example of the command output, see Configure Basic LDP
Label Distribution on page 13.
Use the debug ldp message initialization command to confirm that

the unrecognized notification capability TLV is received in the initialization
message.
Example 1
10.2.250.133 recv INIT message with 'Unrecognized Notification Capability TLV' 0x050B len 1
1.1.3.2 Determine Typed Wildcard FEC Capability
The end-of-LIB notification message carries a Forward Error Correction (FEC)

TLV that identifies the FEC type for which initial label advertisements have
been completed.
An LDP speaker that supports end-of-LIB notification must send a capability

parameter in its initialization message indicating that it supports the typed
wildcard FEC element.
The typed wildcard capability TLV must be set as follows:
• U: 1
• F: 0
• Typed Wildcard FEC Cap: 0x050B
• Length: 0x0001
• S: 1
Use the show ldp neighbor command to determine typed wildcard FEC
capability. If the W flag is set to Typed wild-card FEC capable, the LDP
peer is capable of typed wildcard FEC. For an example of the command
output, see Configure Basic LDP Label Distribution on page 13.
Use the debug ldp message initialization command to confirm that

the typed wildcard FEC capability TLV is received in the initialization message.
28/1543-AXI 101 09/1 Uen J | 2017-11-22 3

LDP
Example 2
10.2.250.133 recv INIT message with 'Typed wildcard FEC capability TLV' 0x0x0603 len 1
1.1.3.3 Determine End-of-LIB Notification
The router signals LDP label advertisement completion to its peer using an
end-of-LIB notification. The notification is sent only if the peer LDP speaker
advertised an unrecognized notification capability and a typed wildcard FEC
capability during session establishment.
The end-of-LIB notification message carries:
• Status TLV (E and F bits set to 0) that carries an end-of-LIB status code
(0x0000002F)
• FEC TLV that identifies the FEC type for which initial label advertisements
have been completed
Timers are used to manage the receipt of end-of-LIB notifications. Following

session establishment, the LDP speaker starts internal IGP-sync and graceful
restart recovery timers. You can configure the length of the timers. The default
is 60 seconds. The timer is reset by label advertisement and is stopped by the
end-of-LIB notification. If the timer expires and the LDP speaker has not
received the end-of-LIB notification from the peer, it acts as though it has it. If
the notification is received after timer expiration, the notification is ignored.
Use the show ldp summary command to determine whether end-of-LIB

notification is enabled. For an example of the command output, see Create
LSP Pseudocircuits for Statistics Collection on page 34.
Use the debug ldp message notification command to confirm that the
end-of-LIB notification for a specific FEC type is received in the notification
message.
Example 3
3.3.3.3: Sending EOL notification (fec:0x80) eol_ctl_send 3
3.3.3.3: Sending EOL notification (fec:0x02) eol_ctl_send 1
1.1.4 Reduce Traffic Disruption Using LDP Loop-Free Alternates

Support for IP Fast Reroute
IP Fast Reroute (IP FRR) is a mechanism that reduces traffic disruption in a
network by repairing a failure locally when a link or node failure occurs. It does
this by calculating a Loop-Free Alternative (LFA) next hop (backup path) in
advance so that when a failure is detected, the LFA next hop can be used
immediately. LDP LFA establishes the backup LSP following the path in RIB
populated by the LFA information given by the IGP.
LDP LFA is enabled by default. Use the no form of the ipfrr command in router
LDP mode to disable LDP LFA.
4 28/1543-AXI 101 09/1 Uen J | 2017-11-22

Overview
Use the show mpls command with the lsp detail or label-mapping detail
options to display the primary and backup LSP information.
1.1.5 Targeted LDP for Remote LFA

Targeted LDP receives an endpoint (from an IGP, such as OSPF and IS-IS).
LDP uses the endpoint information to establish a targeted session to the
endpoint if the targeted session does not already exist and if the endpoint is
allowed by the dynamic-session prefix list configuration. In this way, LDP gets
the label from the endpoint in order to establish forwarding tables.
Use the ip prefix-list command to create the list of router IDs. Use the targeted
dynamic-session command in router LDP configuration mode to configure a
targeted LDP session. Use the targeted advertise command also in router
LDP configuration mode to permit targeted session advertisements on all
targeted sessions.
For an example illustrating how targeted LDP can be used with remote LFA,
see Configure IS-IS Remote LFA Protection and Configure OSPF Remote LFA
Protection.
1.1.6 Multipoint Label Distribution Protocol

Multicast Label Distribution Protocol (mLDP) allow setting up point-to-
multipoint (P2MP) Label-Switched Paths (LSPs) in MPLS networks.
Multipoint LSPs transport end-user traffic (Layer 3 multicast traffic or Layer 2

broadcast, unicast, and multicast traffic) from a single root (or ingress) node to
several leaf (or egress) nodes traversing one or more transit nodes. It also
eliminates the need to run Protocol-Independent Multicast (PIM) protocols and
optimizes bandwidth usage by reducing the number of label replications in the
MPLS core.
mLDP enables routers to exchange P2MP capability support after an LDP

session is established. Routers that support P2MP exchange the P2MP
capability parameters in a dynamic capability announcement with their LDP
peers and establish multipoint LSP to carry L2 and L3 traffic over an MPLS
network.
During an LDP session, an mVPN applications at the leaf node request LDP to
set up a P2MP LSP to receive traffic from the root node (source PE router in
MPLS network). LDP allocates a local label for the FEC corresponding to
application traffic stream and forms a label-mapping message. It then sends
this message towards the root node to establish a P2MP LSP. Similarly, if an
application does not need the P2MP LSP, it sends a request to LDP to tear
down the LSP. LDP translates this to label withdraw message and sends it
upstream towards root node to remove the LSP.
For more information about mVPN, refer to Multicast In-Band Signaling Using
MLDP (mVPN).
28/1543-AXI 101 09/1 Uen J | 2017-11-22 5

LDP
1.1.6.1 mLDP Fast Reroute
mLDP Fast Reroute (FRR) mechanism reduces the loss of connectivity in an

LDP network by enabling a router to quickly switch traffic to a pre-computed or
a pre-programmed Loop-Free Alternate (LFA) path, if the link to the
downstream Label Switching Router (LSR) fails. This path is used to switch
traffic till the router sets up new primary next-hops. mLDP FRR supports the
following:
• Supports both IPv4 and IPv6 traffic
• Supports P2MP in-band signaling
• Supports switchover time of less than 50 milliseconds
1.1.6.2 Link Protection Using mLDP FRR
mLDP link protection enables fast reroute of traffic carried over P2MP LSPs in
a link failure. In MPLS networks, the links to the LSRs are protected using
LDP LFA and LDP Remote LFA (RLFA) paths.
When the link to a downstream LSR fails, in case of non-FRR, the LSP breaks
temporarily resulting in packet loss until the LSP reconverges and a new
P2MP tree is built towards the root. In case of FRR is enabled, the traffic is
switched to the backup path within 50 milliseconds and a new primary path is
calculated, resulting in LSRs choosing a new upstream LSR to reach the root
node. To keep the duration of packet loss minimal migrated from old LSP to
the new calculated primary LSP, Make-Before-Break (MBB) mechanism is
used. By default, MBB is enabled for mLDP.
1.1.6.3 Link Protection Using LFA Backup Tunnel
The sequence of events that occur in an mLDP LFA FRR scenario is

explained with the following example:
6 28/1543-AXI 101 09/1 Uen J | 2017-11-22

Overview
LFA Backup Tunnel

for Link A
C
L20
Root mLDP
L18 L17 L16
Link A
X A B D
18 17 16
G108987A
Figure 1 Link Protection Using LFA Backup Tunnel
1. Router X is the source provider edge router, and Router B is the next Hop
router.
2. The primary path is from Router X > Router A > Router B > Router D, and
the backup path is Router X > Router A > Router C > Router B > Router
D. The backup path is pre-computed by IGP through LFA prefix-based
selection.
3. Backup tunnels are configured for Link A.
4. mLDP LSP is built from D, B, and A towards the root.
5. Router A installs a downstream forwarding replication over Link A to

Router B.
When a failure occurs on Link A:
28/1543-AXI 101 09/1 Uen J | 2017-11-22 7

LDP
LFA Backup Tunnel

for Link A
PHP
C
L20
17 17
20
Root mLDP
L18 L17 L16
Link A
X A B D
18 17 16
G108988A
Figure 2 LFA Backup Tunnel–Link Failure
1. Traffic over Link A is rerouted over the backup tunnel by imposing label 17
and then pushing label 20 on top of it.
2. Router C performs Penultimate Hop Popping (PHP) and removes the

outer label 20.
3. Router B receives the mLDP packets with label 17 and forwards to Router
D.
1.1.6.4 Link Protection Using Re-optimization
TE/LFA Backup Tunnel

for Link A
PHP
C
L20
17 17
20 L22 22 21 L21
Root mLDP
L18 L17 L16
Link A
A B D
18 16
Figure 3 Make Before Break Reoptimization

During reoptimization of the failed node:
8 28/1543-AXI 101 09/1 Uen J | 2017-11-22

Overview
1. LDP is notified that the root is reachable through router C, and LDP
converges. With this, a new mLDP LSP is built from router A to router B
through router C. The new label that router C distributed to A is 22.
2. Currently, router A sends two mLDP packets. One is with old label 20 17,
passing through the backup P2P tunnel. The other is the one with new
label 22.
3. As the MBB switchover is not start, router B will receive two mLDP
packets. However, router B only forwards the packet with old label 17 (the
outside label 20 is popped by router C), the packet with the new label 21
will be dropped.
4. After MBB switchover, router B only forwards the packet with new label
21.
5. Router B prunes off the backup tunnel with a label withdraw to router A.
1.1.6.5 Link Protection Using Remote LFA
Some topologies (for example the commonly used ring-based topology)

require protection that is not afforded by LFA FRR alone. This is because
there is no neighbor of the Point of Local Repair (PLR) that has a cost to the
destination via a path that does not traverse the failure, and that is cheaper
than the cost to the destination via the failure. RLFA extends the LFA
approach to cover many of these cases by tunneling the packets that require
FRR to a node that is both reachable from the PLR and can reach the
destination. The targeted LDP protocol (T-LDP) needed to learn the label
binding at the repair tunnel endpoint is a widely deployed technology.
The sequence of events that occur in an mLDP RLFA FRR scenario is

explained with the following diagram:
L21
Backup for Link A
L20
C Z
T-LDP
Root mLDP
L18 L17 L16
Link A
A B D
18 17 16
G108984A
Figure 4 Link Protection using RLFA
28/1543-AXI 101 09/1 Uen J | 2017-11-22 9

LDP
1. All the links in the topology are of equal cost and there is no viable LFA
protecting Link A.
2. P2P tunnel A to Z is the backup of Link A.
3. Router A establishes a Targeted LDP (T-LDP) session with router Z and

obtains the Label 21 to reach Router B from Router Z.
When an link failure occurs on Link A:
L21
Backup for Link A
L20
C Z
T-LDP
Root mLDP
L18 L17 L16
Link A
A B D
18 17 16
G108984A
Figure 5 mLDP RLFA Link Failure
1. Traffic over Link A is rerouted over the tunnel to Router Z by first imposing
Label 17, then pushing Label 21, and finally pushing Label 20 (three label
stacks).
2. Router C performs a PHP and removes the outer Label 20 and then
routes the traffic to router Z.
3. Router Z receives the traffic with outer Label 21 and inner Label 17.
4. Router Z performs a PHP and removes Label 21 and then routes the
traffic to Router B with Label 17.
5. Router B forwards mLDP packets to Router D.
1.2 Prerequisites
LDP must work together with MPLS and an IGP, such as IS-IS or OSPF. To
configure MPLS, see MPLS. To configure an IGP routing instance and
interface, see IS-IS or OSPF.
For LDP to establish sessions, the LDP transport address of an LDP instance
must be reachable. The Ericsson implementation uses the LDP router ID as
10 28/1543-AXI 101 09/1 Uen J | 2017-11-22

Overview
the LDP transport address. It is recommended that you configure a loopback

interface whose address is advertised by the underlying IGP.
1.3 Restrictions
The mLDP P2MP LSP over LAG is not supported.
Only mLDP P2MP in-band signaling is supported.
mLDP node protection is not supported.
During a LDP process restart, Non Stop Routing (NSR) and RP Switchover
are not supported.
Limiting multicast group count per VPN/PE is not supported.
28/1543-AXI 101 09/1 Uen J | 2017-11-22 11

LDP
2 Configuration
To configure LDP, refer to the examples in the following sections.
Note: The examples that follow may not show the complete command
syntax. For more information, see the Command List.
2.1 Configuration Command Hierarchy

Configure LDP in LDP configuration mode.
The hierarchy of configuration commands is:
router ldp
create-lsp-circuit
ecmp-transit
explicit-null (LDP)
graceful-restart (LDP)
hello holdtime
hello interval (LDP)
ignore config-seq-num
igp-synchronization timeout
interface (LDP)
keepalive (LDP)
label-binding
max-session
mldp
mldp link-protection
mldp mbb switchover-delay
mldp mbb timeout
neighbor explicit-null
neighbor password
neighbor targeted
router id (LDP)
targeted advertise
targeted dynamic-session
12 28/1543-AXI 101 09/1 Uen J | 2017-11-22

Configuration
targeted hello holdtime

targeted hello interval
track-igp-metric
transport-address
Note: In addition to the commands above, you can also use standard
configuration commands, such as abort, comment, commit,
default, exit, and no.
2.2 Configure Basic LDP Label Distribution

This example configures basic LDP label distribution for a network.
Figure 6 Basic LDP Label Distribution

Figure 6 shows a network of three routers using LDP to distribute labels for
label-switched routing. The routers are configured as follows:
• R1 advertises loopback address 192.0.2.211/32 and links to R2 and

R3 over subnets 192.0.2.0/29 and 192.0.2.8/29.


28/1543-AXI 101 09/1 Uen J | 2017-11-22 13

LDP
In this example, IS-IS is the IGP. For information on configuring IS-IS, see IS-
IS.
You can configure additional LDP settings using commands such as the
following:
• keepalive (LDP) to configure LDP liveliness detection and keepalive

packet transmission
• ignore config-seq-num to configure the router to ignore the change in the

configuration sequence number specified in an LDP neighbor's Hello
packets
To configure basic LDP label distribution, perform the tasks in the following
sections.
2.2.1 Configure LDP on R1

To configure LDP on R1, do the following starting in global configuration mode.
Steps
1. Enter the context, create an LDP instance, and enable LDP on the
loopback interface.
Example
[local]R1(config)#context local
[local]R1(config-ctx)#router ldp
[local]R1(config-ldp)#interface ifLB
2. Enable LDP on all R1 interfaces that route label-switched traffic in the

network.
Example
[local]R1(config-ldp)#interface if2R2
[local]R1(config-ldp)#interface if2R3
[local]R1(config-ldp)#commit
3. Confirm the configuration.
Example
[local]R1(config-ldp)#show configuration
Building configuration...
Current configuration:
context local
!
router ldp
interface if2R2
interface if2R3
interface ifLB
!
! ** End Context **
!
end
14 28/1543-AXI 101 09/1 Uen J | 2017-11-22

Configuration
2.2.2 Configure LDP on R2 and R3
Steps
1. To configure LDP on R2 and R3, repeat the procedure used to configure

R1 as follows:
• For R2, interfaces if2R1 and if2R3 route label-switched traffic in the
network.
• For R3, interfaces if2R1 and if2R2 route label-switched traffic in the
network.
2.2.3 Verify Label Distribution

To verify label distribution, check that LDP interfaces are up and distributing
labels. This example then configures MPLS on the routers (not shown) and
verifies label-switched routing based on the LDP label distribution.
To verify label distribution, do the following.
Steps
1. Confirm that LDP interfaces are up and connected to neighbors. The

State field shows a value of Oper for both R1 neighbors.
Example
[local]R1#show ldp neighbor
PeerFlags: A - LocalActiveOpen, D - Deleted, R - Reseting, E - OpenExtraDelay
N - OpenNoDelay, P - SetMD5Passwd, T - RetainRoute, F - FlushState
X - ExplicitNullEnabled, C - ExplicitNullStatusChanging
G - Graceful Restart Supported, L - Session Life Extended
U - Unrecognized Notification Capable, V - Reachable Via Tunnel-Shortcut
M - P2MP capable
W - Typed wildcard FEC capable
SHld - Session Holdtime Left, HHld - Hello Holdtime Left
NeighborAddr LDP Identifier State Flag SHld HHld Interface
192.0.2.222 192.0.2.222:0 Oper GUW 60 12 if2R2
192.0.2.233 192.0.2.233:0 Oper GUW 62 14 if2R3
2. Confirm that LDP interfaces are distributing labels. All the network
interfaces are assigned labels.
Example
[local]R1#show ldp binding
> active binding, Local/In - local/input label binding
From - source of remote label, Remote/Out - remote/output label binding
Prefix/FEC Learned-From Local/In Remote/Out Interface
> 192.0.2.0/29 local 3
192.0.2.233:0 655362
192.0.2.222:0 3
> 192.0.2.8/29 local 3
192.0.2.233:0 3
192.0.2.222:0 655362
> 192.0.2.16/29 192.0.2.233:0 655362 3 if2R3
> 192.0.2.222:0 3 if2R2
> 192.0.2.211/32 local 3
28/1543-AXI 101 09/1 Uen J | 2017-11-22 15

LDP
192.0.2.233:0 655364
192.0.2.222:0 655364
> 192.0.2.222/32 192.0.2.222:0 655365 3 if2R2
192.0.2.233:0 655365
> 192.0.2.233/32 192.0.2.233:0 655364 3 if2R3
192.0.2.222:0 655365
3. Configure MPLS for the network.

For information on configuring MPLS, see MPLS.
4. Confirm that MPLS LSPs are up. R1 displays LSPs to R2, R3, and remote
(not directly connected) subnet 192.0.2.16/29 with a value of Up in the
State field.
Example
[local]R1#show mpls lsp ldp
Codes : S - MPLS-Static, R - RSVP, L - LDP, B - BGP
Type Endpoint Direct Next-hop Out Label Adjacency Id State
L 192.0.2.16/29 192.0.2.2 3 0x300000 Up
L 192.0.2.16/29 192.0.2.10 3 0x300001 Up
L 192.0.2.222/32 192.0.2.2 3 0x300005 Up
L 192.0.2.233/32 192.0.2.10 3 0x300003 Up
5. Verify label-switched routing by sending label-switched traffic from R1 to

R3.
Example
[local]R1#ping mpls ldp 192.0.2.233/32
Sending 5 100-byte MPLS echos to LDP 192.0.2.233/32, source 192.0.2.211,
timeout is 1 second, send interval is 0 msec:
!!!!!
---- MPLS PING Statistics----
5 packets transmitted, 5 packets received no error, 0.0% packet loss/error
round-trip min/avg/max/stddev = 2.296/5.059/12.414/4.251 ms
2.3 Set a Router ID

This example sets a router ID for an LDP instance.
16 28/1543-AXI 101 09/1 Uen J | 2017-11-22

Configuration
Figure 7 Router ID
Figure 7 shows a network of three routers configured for LDP label distribution
as in Configure Basic LDP Label Distribution on page 13. This example
configures router R1 with a router ID of 192.0.2.1.
To set a router ID, do the following steps starting in global configuration mode.
Steps
1. Enter the context, access LDP configuration mode, and set a router ID.
Example
[local]R1(config-ldp)#router-id 192.0.2.1
[local]R1(config-ldp)#exit

Before the router ID is set, neighbor R2 displays the loopback IP address
for R1 (192.0.2.211).
Example
...
192.0.2.211 192.0.2.211:0 Oper AGUW 73 12 if2R1
192.0.2.233 192.0.2.233:0 Oper GUW 76 10 if2R3
28/1543-AXI 101 09/1 Uen J | 2017-11-22 17

LDP
After the router ID is set, neighbor R2 displays the configured ID

(192.0.2.1). If you set or modify the router ID for an operating LDP
session, the previous ID is displayed until the hold time expires.
Example
...
192.0.2.1 192.0.2.1:0 Oper AGUW 68 12 if2R1
192.0.2.233 192.0.2.233:0 Oper GUW 66 10 if2R3
2.4 Configure Hello Messages

This example configures the interval for the Hello messages sent to linked
LDP neighbors.
Figure 8 Hello Messages (Linked Neighbors)

Figure 8 shows a network of three routers configured for label distribution as in
Configure Basic LDP Label Distribution on page 13. This example modifies the
interval between Hello messages on router R1 from the default to a value of
10 seconds.
You can configure additional Hello parameters using commands such as hello
holdtime, which sets the time that a Hello adjacency is maintained in the
absence of messages from the neighbor. To configure Hello messages for
remote neighbors, see Configure Targeted Hello Messages on page 25.
18 28/1543-AXI 101 09/1 Uen J | 2017-11-22

Configuration
To configure Hello messages on R1, do the following steps starting in global

configuration mode.
Steps
1. Enter the context, access LDP configuration mode, and configure Hello
messages.
Example
[local]R1(config-ldp)#hello interval 10
[local]R1(config-ctx)#exit
2. Confirm the configuration. The Hello interval field displays the

configured value.
Example
[local]R1(config)#show ldp interface detail
Flag:
B - Bound, U - Up, D - Deleted, S - Stale, E - Hold expired
T - Bind Stale L - Loopback
Intf name: if2R2
IP address: 192.0.2.1/29 Flags: BU
Nbr count: 1
Neighbor LSRid: 192.0.2.222:0
Holdtime expiry: 14 Hello interval 10
Holdtime used: 15 Holdtime received: 15
...
2.5 Configure the Transport Address

This example sets the transport address that the router advertises to
neighbors.
28/1543-AXI 101 09/1 Uen J | 2017-11-22 19

LDP
Figure 9 Transport Address

Figure 9 shows a network of three routers configured for label distribution as in
Configure Basic LDP Label Distribution on page 13. This example sets IP
address 192.0.2.1 as the transport address that R1 advertises to neighbors.
To configure the transport address on R1, do the following steps starting in

global configuration mode.
Steps
1. Enter the context, access LDP configuration mode, and set the transport
address.
Example
[local]R1(config-ldp)#transport-address 192.0.2.1

Before the transport address was configured, R1 displayed a value of
192.0.2.211/646 in the TCP Conn Local field. Neighbor R2
displayed a value of 192.0.2.211/646 in the Remote field.
Example
[local]R1(config)#show ldp neighbor detail
Flag:
20 28/1543-AXI 101 09/1 Uen J | 2017-11-22

Configuration

...
Neighbor Address: 192.0.2.222 State: Oper
LDP Identifier: 192.0.2.222:0 Flags: GUW
Last Reset Reason: LDP initialized Error:
Recv Notification: End-Of-Lib Sent Notification: End-Of-Lib
FEC Ver: 199 ADDR Ver: 5
TCP Conn Local: 192.0.2.211/646 Remote: 192.0.2.222/48346
Sess Hold Expire: 62 Next KeepAlive: 2 sec
...
[local]R2#show ldp neighbor 192.0.2.211 detail
Flag:
...
LDP Identifier: 192.0.2.211:0 Flags: AGUW
Last Reset Reason: Notify received Error:
...
After the transport address is configured, R1 displays a value of

192.0.2.1/646 in the TCP Conn Local field. Neighbor R2 displays a
value of 192.0.2.1/646 in the Remote field.
Example
[local]R1(config)#show ldp neighbor detail
Flag:
...
LDP Identifier: 192.0.2.222:0 Flags: GUW
...
[local]R2#show ldp neighbor detail
Flag:
...
...
2.6 Authenticate Sessions

This example configures a password for authenticating LDP sessions.
28/1543-AXI 101 09/1 Uen J | 2017-11-22 21

LDP
Figure 10 Authentication
Figure 10 shows a network of three routers configured for label distribution as
in Configure Basic LDP Label Distribution on page 13. This example enables
Message Digest 5 (MD5) authentication of the LDP TCP session between R1
and R2.
To configure session authentication, perform the tasks in the following

sections.
2.6.1 Configure Authentication on R1

To configure authentication on R1, do the following steps starting in global
configuration mode.
Steps
1. Enter the context, access LDP configuration mode, and configure

authentication.
Example
[local]R1(config-ldp)#neighbor 192.0.2.222 password Secret35
2. Confirm the configuration. The Flag field for neighbor R2

(192.0.2.222) displays a P (defined in the command output legend as
22 28/1543-AXI 101 09/1 Uen J | 2017-11-22

Configuration
SetMD5Passwd) to show that R1 is using MD5 authentication in its TCP

session with R2. The LDP session is no longer operational (the State
field shows a value of None) because only one side of the TCP session is
configured with the required password.
Example
[local]R1(config)#show ldp neighbor
...
192.0.2.222 192.0.2.222:0 None PGUW 0 14 if2R2
192.0.2.233 192.0.2.233:0 Oper GUW 84 10 if2R3
2.6.2 Configure Authentication on R2
Steps
1. To configure R2, repeat the procedure used to configure authentication on

R1 for neighbor 192.0.2.211.
2.6.3 Confirm Session Authentication
Steps
1. Confirm that LDP neighbors are operational and authenticating LDP

sessions. The State field shows a value of Oper and the Flag field
shows a P.
Example
...
192.0.2.222 192.0.2.222:0 Oper PGUW 61 12 if2R2
192.0.2.233 192.0.2.233:0 Oper GUW 76 13 if2R3
2.7 Configure Extended Neighbor Discovery

This example enables extended neighbor discovery between a pair of routers.
28/1543-AXI 101 09/1 Uen J | 2017-11-22 23

LDP
Figure 11 Extended Neighbor Discovery

in Configure Basic LDP Label Distribution on page 13 but with no direct link
between R1 and R2. This example configures routers R1 and R2 to become
LDP neighbors through extended discovery.
To configure extended neighbor discovery, do the following steps starting in

Steps
1. On R1, enter the context, access LDP configuration mode, and configure
extended discovery.
Example
[local]R1(config-ldp)#neighbor 192.0.2.222 targeted
2. On R2, repeat the procedure used to configure R1 for neighbor IP address

192.0.2.211.

Before extended neighbor discovery was configured, neighbor R1
displayed only directly connected LDP neighbor R3 (192.0.2.233).
Likewise, R2 displayed only connected neighbor R3.
24 28/1543-AXI 101 09/1 Uen J | 2017-11-22

Configuration
Example
...
192.0.2.233 192.0.2.233:0 Oper GUW 67 14 if2R3
After extended neighbor discovery is configured, R1 displays remote

neighbor R2 (192.0.2.222) with a value of none - remote in the
Interface field. Likewise, R2 displays remote neighbor R1
(192.0.2.211).
Example
...
192.0.2.222 192.0.2.222:0 Oper GUW 75 30 none - remote
192.0.2.233 192.0.2.233:0 Oper GUW 60 12 if2R3
Example
...
192.0.2.211 192.0.2.211:0 Oper AGUW 77 31 none - remote
192.0.2.233 192.0.2.233:0 Oper GUW 69 12 if2R3
2.8 Configure Targeted Hello Messages

This example configures the holdtime for Hello messages sent to remote LDP
neighbors.
28/1543-AXI 101 09/1 Uen J | 2017-11-22 25

LDP
Figure 12 Targeted Hello Messages

in Configure Extended Neighbor Discovery on page 23. This example sets the
holdtime for targeted Hello messages that R1 sends to remote LDP neighbors.
You can configure additional Hello parameters using commands such as

targeted hello interval, which sets the interval between consecutive targeted
Hello messages. To configure Hello messages for linked neighbors, see
Configure Hello Messages on page 18.
To configure targeted Hello messages, do the following steps starting in global

configuration mode.
Steps
1. Enter the context, access LDP configuration mode, and configure the
targeted Hello holdtime.
Example
[local]R1(config-ldp)#targeted hello holdtime 50

Before the Hello holdtime was configured, neighbor R2 displayed the
default holdtime of 45 seconds.
26 28/1543-AXI 101 09/1 Uen J | 2017-11-22

Configuration
Example
...
...
Up/Down Time Since Last Chg: 00:20:27 Reset Count: 0
# of Adjacency: 1
# Interface I/F Address Rcvd Used Left Intv
1 : none - remote none 45 45 32 15
After the Hello holdtime is configured, neighbor R2 displays the configured

holdtime of 50 seconds.
Example
...
...
Up/Down Time Since Last Chg: 00:20:27 Reset Count: 0
# of Adjacency: 1
# Interface I/F Address Rcvd Used Left Intv
1 : none - remote none 50 45 32 15
2.9 Advertise an Explicit-Null Label

This example configures an egress router to advertise the explicit-null label to
an LDP neighbor.
Figure 13 Explicit Null
28/1543-AXI 101 09/1 Uen J | 2017-11-22 27

LDP

in Configure Basic LDP Label Distribution on page 13. This example
configures egress router R2 to advertise an explicit-null label to neighbor R1.
To configure R2 to advertise an explicit-null label, do the following steps

starting in global configuration mode.
Steps
1. Enter the context, access LDP configuration mode, and enable explicit-
null advertisement.
Example
[local]R2(config-ldp)#neighbor 192.0.2.211 explicit-null

Before explicit-null advertisement was configured, neighbor R1 displayed
the default label of 3 for traffic to R2 (192.0.2.0/29, 192.0.2.16/29
through interface if2R2, and 192.0.2.222/32).
Example
[local]R1#show ldp binding neighbor 192.0.2.222 received
192.0.2.0/29 192.0.2.222:0 3 3
192.0.2.8/29 192.0.2.222:0 3 655362
> 192.0.2.16/29 192.0.2.222:0 655362 3 if2R2
192.0.2.211/32 192.0.2.222:0 3 655364
> 192.0.2.222/32 192.0.2.222:0 655365 3 if2R2
192.0.2.233/32 192.0.2.222:0 655364 655365
After explicit-null advertisement is configured, neighbor R1 displays the

label 0 for traffic to R2.
Example
[local]R1#show ldp binding neighbor 192.0.2.222 received
192.0.2.0/29 192.0.2.222:0 3 0
192.0.2.8/29 192.0.2.222:0 3 655362
> 192.0.2.16/29 192.0.2.222:0 655362 0 if2R2
192.0.2.211/32 192.0.2.222:0 3 655364
> 192.0.2.222/32 192.0.2.222:0 655365 0 if2R2
192.0.2.233/32 192.0.2.222:0 655364 655365
2.10 Propagate the IGP Route Metric to LSPs

This example sets the route metric of LDP LSPs to the value set by the
underlying IGP.
28 28/1543-AXI 101 09/1 Uen J | 2017-11-22

Configuration
Figure 14 IGP Metric Propagation

in Configure Basic LDP Label Distribution on page 13. This example
configures router R1 to set the metric of its LSPs to that of the underlying IGP
(in this case IS-IS) route metric.
To propagate the IGP metric into LSPs, do the following steps starting in
Steps
1. Enter the context, access LDP configuration mode, and enable IGP-metric
tracking.
Example
[local]R1(config-ldp)#track-igp-metric

Before R1 was configured to propagate the IGP metric, its LSP to R2
displayed the default value of 0 in the metric field. For the IS-IS route,
the metric field displays a value of 20.
28/1543-AXI 101 09/1 Uen J | 2017-11-22 29

LDP
Example
[local]R1#show ip route 192.0.2.222/32
Best match Routing entry for 192.0.2.222/32 is 192.0.2.222/32 , version 206
Route Uptime 00:00:51
Paths: total 2, best path count 2 (includes 1 lsp best path)
...
Active path :
Known via isis isis1, type-IS-IS level-1, distance 115, metric 20,
Tag 0, Next-hop 192.0.2.2, NH-ID 0x31100002, Adj ID: slot number=0, adj id
...
Active LSP path ineligible for fib, only used for recursion
Known via ldp distance 7, metric 0,
Tag 0, Next-hop 192.0.2.2, NH-ID 0x31E00028, Adj ID: slot number=0, adj id
...
After R1 is configured to propagate the IGP metric, the metric field

displays the value of 20 inherited from the IS-IS route.
Example
[local]R1#show ip route 192.0.2.222/32
Best match Routing entry for 192.0.2.222/32 is 192.0.2.222/32 , version 213
Route Uptime 00:00:07
Paths: total 2, best path count 2 (includes 1 lsp best path)
...
Active path :
Known via isis isis1, type-IS-IS level-1, distance 115, metric 20,
Tag 0, Next-hop 192.0.2.2, NH-ID 0x31100002, Adj ID: slot number=0, adj id
...
Active LSP path ineligible for fib, only used for recursion
Known via ldp distance 7, metric 20,
Tag 0, Next-hop 192.0.2.2, NH-ID 0x31E00028, Adj ID: slot number=0, adj id
...
2.11 Filter Label Advertisements

This example filters the LDP labels that a router advertises to a neighbor.
30 28/1543-AXI 101 09/1 Uen J | 2017-11-22

Configuration
Figure 15 Label Advertisement Filtering

Figure 15 shows a network configured for label distribution as in Configure
Basic LDP Label Distribution on page 13 with the additional router R0,
configured similarly, advertising loopback address 198.51.100.200/32 and
linking to R1 over subnet 198.51.100.0/29. Router R2 connects to subnets
10.0.1.0/29 and 10.0.2.0/29, and it and R3 connect to route
203.0.113.0/29. This example configures router R1 to advertise to
neighbor R0 only the labels of LDP loopback interfaces.
To filter label advertisements, do the following steps starting in global

configuration mode.
Steps
1. Enter the context and configure an IP prefix list. For information on IP

prefix lists, see Routing Policies.
Example
[local]R1(config-ctx)#ip prefix-list PL_LDP_1
[local]R1(config-prefix-list)#permit 0.0.0.0/0 eq 32
[local]R1(config-prefix-list)#exit
2. Access LDP configuration mode and configure filtering.
Example
[local]R1(config-ldp)#neighbor 198.51.100.200 label-binding prefix-list PL_LDP_1 out
28/1543-AXI 101 09/1 Uen J | 2017-11-22 31

LDP

Before R1 was configured to filter labels, neighbor R0 displayed labels
learned from R1 (192.0.2.211:0) to LDP routers 192.0.2.211/32,
192.0.2.222/32, 192.0.2.233/32, and 198.51.100.200/32 and
subnets such as 10.0.1.0/24.
Example
> 10.0.1.0/24 192.0.2.211:0 655362 655366 if2R1
> 10.0.2.0/24 192.0.2.211:0 655363 655367 if2R1
> 192.0.2.0/29 192.0.2.211:0 655364 3 if2R1
> 192.0.2.8/29 192.0.2.211:0 655365 3 if2R1
> 192.0.2.16/29 192.0.2.211:0 655366 655362 if2R1
> 192.0.2.211/32 192.0.2.211:0 655367 3 if2R1
> 192.0.2.222/32 192.0.2.211:0 655368 655365 if2R1
> 192.0.2.233/32 192.0.2.211:0 655369 655364 if2R1
> 198.51.100.0/29 local 3
192.0.2.211:0 3
> 198.51.100.200/32 local 3
192.0.2.211:0 655370
> 203.0.113.0/29 192.0.2.211:0 655370 655368 if2R1
After R1 is configured to filter labels, neighbor R0 displays only labels of

LDP loopback interfaces learned from R1 (and its own labels).
Example
> 192.0.2.211/32 192.0.2.211:0 655367 3 if2R1
> 192.0.2.222/32 192.0.2.211:0 655368 655365 if2R1
> 192.0.2.233/32 192.0.2.211:0 655369 655364 if2R1
> 198.51.100.0/29 local 3
> 198.51.100.200/32 local 3
192.0.2.211:0 655370
2.12 Enable ECMP on a P Router (Transit Node)

This example enables Equal-Cost Multiple Paths (ECMPs) on a P router
(transit node).
32 28/1543-AXI 101 09/1 Uen J | 2017-11-22

Configuration
Figure 16 Transit ECMP

Figure 16 shows an MPLS network with three P routers configured for label
distribution as in Configure Basic LDP Label Distribution on page 13. Label
Edge Router (LER) R0, configured similarly, advertises loopback address
198.51.100.200/32 and links to R1 over subnet 198.51.100.0/29. P
routers R2 and R3 connect to route 203.0.113.0/29. By enabling ECMPs
on P router R1, this example provides the LSP to route 203.0.113.0/29 on
LER R0 with two paths:
• R0 (LER) → R1 → R2 → route 203.0.113.0/29
• R0 (LER) → R1 → R3 → route 203.0.113.0/29
To enable ECMP on R1, do the following steps starting in global configuration

mode.
Steps
1. Enter the context, access LDP configuration mode, and enable ECMP.
Example
[local]R1(config-ldp)#ecmp-transit
28/1543-AXI 101 09/1 Uen J | 2017-11-22 33

LDP
Before ECMP was enabled on R1, traceroute packets sent over the LSP
from LER R0 to route 203.0.113.0/29 showed only next hop R2
(192.0.2.2) on P router R1.
Example
[local]R0#traceroute mpls ldp 203.0.113.0/29
Pkt Hop Recv Intf Down Intf Down Nbr RTT MTU RC
1 0 N/A 198.51.100.1 198.51.100.1 0 1500 Ingress
1 1 198.51.100.1 192.0.2.2 192.0.2.2 24 1500 Transit
1 2 192.0.2.2 N/A N/A 21 N/A Egress
---- MPLS Traceroute Statistics----

1 path queries, 2 packets transmitted, 2 packets received no error
0.0% packet loss/error
After ECMP is enabled on R1, traceroute packets sent over the LSP from
LER R0 to route 203.0.113.0/29 show two next hops on this P router:
R2 (192.0.2.2) and R3 (192.0.2.10).
Example
[local]R0#traceroute mpls ldp 203.0.113.0/29
Pkt Hop Recv Intf Down Intf Down Nbr RTT MTU RC
1 0 N/A 198.51.100.1 198.51.100.1 0 1500 Ingress
1 1 198.51.100.1 192.0.2.2 192.0.2.2 8 1500 Transit
192.0.2.10 192.0.2.10 1500
1 2 192.0.2.2 N/A N/A 11 N/A Egress
---- MPLS Traceroute Statistics----

1 path queries, 2 packets transmitted, 2 packets received no error
0.0% packet loss/error
2.13 Create LSP Pseudocircuits for Statistics Collection

This example creates LSP pseudocircuits, which are required for collecting
statistics on LDP LSPs.
34 28/1543-AXI 101 09/1 Uen J | 2017-11-22

Configuration
Figure 17 LSP Pseudocircuits

Figure 17 shows an MPLS network configured for label distribution as in
Configure Basic LDP Label Distribution on page 13 with the additional router
R0, configured similarly, advertising loopback address 198.51.100.200/32
and linking to R1 over subnet 198.51.100.0/29. Routers R2 and R3
connect to route 203.0.113.0/29. This example creates LSP pseudocircuits
on R0 for LDP LSP statistics collection.
To create LSP pseudocircuits on R0, do the following steps starting in global

configuration mode.
Steps
1. Enter the context, access LDP configuration mode, and create LSP
pseudocircuits.
Example
[local]R0(config-ldp)#create-lsp-circuit
[local]R0(config)#exit

Before LSP pseudocircuits were created, the Create-LSP-Circuit
field displayed a value of disabled and no MPLS circuit counters were
shown on R0.
28/1543-AXI 101 09/1 Uen J | 2017-11-22 35

LDP
Example
[local]R0#show ldp summary
LDP Identifier: 198.51.100.200:0 Config Trans Addr: None
FEC Version: 30 ADDR Version: 2
Label Manager version: 30 Operational Peers: 1
Labels Allocated: 11 Router State: Normal
NSR State: Standby not Ready Graceful restart: enabled
Fast-reroute: disabled ipfrr: enabled
Track-IGP-metric: disabled Create-LSP-Circuit: disabled
Tunnel-Shortcuts: disabled
max-session: 1024
End-of-LIB Notification enabled
Dynamic Capability Announcement: enabled
Dynamic Capabilities: nil
Example
[local]R0#show circuit counters mpls live
please wait...
[local]R0#
After LSP pseudocircuits are created, the Create-LSP-Circuit field

displays a value of enabled and MPLS circuit counters 10 to 18 are
shown.
Example
[local]R0#show ldp summary
Track-IGP-metric: disabled Create-LSP-Circuit: enabled
max-session: 1024
Example
[local]R0#show circuit counters mpls
Circuit Packets/Bytes Sent Packets/Bytes Received
MPLS LSP 10 0 0
0 0
MPLS LSP 11 0 0
0 0
MPLS LSP 12 0 0
0 0
MPLS LSP 13 0 0
0 0
MPLS LSP 14 0 0
0 0
MPLS LSP 15 0 0
0 0
MPLS LSP 16 0 0
0 0
MPLS LSP 17 0 0
0 0
MPLS LSP 18 0 0
0 0
To verify the operation of these LSP counters, this example sends traffic
from R0 to subnet 203.0.113.0/29. The counter for circuit 18 shows
the numbers of sent packets (80) and bytes (9440).
36 28/1543-AXI 101 09/1 Uen J | 2017-11-22

Configuration
Example
[local]R0#ping mpls ldp 203.0.113.0/29 80
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
---- MPLS PING Statistics----
80 packets transmitted, 80 packets received no error, 0.0% packet loss/error
round-trip min/avg/max/stddev = 3.148/5.127/15.275/2.072 ms
Example
[local]R0#show circuit counters mpls lsp 18 live
Circuit Packets/Bytes Sent Packets/Bytes Received
MPLS LSP 18 80 0
9440 0
2.14 Modify the Number of Allowed Sessions

This example reduces the maximum number of LDP sessions allowed on a
router to 800, which is below the default limit of 1024.
To modify the maximum number of sessions, do the following steps starting in

Steps
1. Enter the context, access LDP configuration mode, and set the maximum
number of allowed sessions.
Example
[local]R1(config-ldp)#max-session 800

Before the maximum number of sessions was modified, the router
displays the default (1024) limit in its max-session field.
Example
[local]R1(config)#show ldp summary
Graceful restart enabled, Fast-reroute disabled, Track-IGP-metric disabled, Crea
te-LSP-Circuit disabled, Tunnel-Shortcuts disabled, max-session 1024
After the maximum number of sessions is modified, the router displays the
configured limit in its max-session field.
Example
28/1543-AXI 101 09/1 Uen J | 2017-11-22 37

LDP

Graceful restart enabled, Fast-reroute disabled, Track-IGP-metric disabled, Crea
te-LSP-Circuit disabled, Tunnel-Shortcuts disabled, max-session 800
2.15 Configure Graceful Restart

This example disables graceful restart for LDP on a router.
You can also use the graceful-restart (LDP) command to configure graceful-
restart timers.
To disable graceful restart, do the following steps starting in global

configuration mode.
Steps
1. Enter the context, access LDP configuration mode, and disable graceful
restart.
Example
[local]R1(config-ldp)#no graceful-restart
2. Confirm the configuration. The Graceful restart field displays a value

of disabled.
Example
max-session: 1024
2.16 Disable LDP LFA for IP FRR

LDP LFA for IP FRR is enabled by default. This feature is used in topologies
that require traffic disruption to be below 50 ms when a link or node failure
occurs by enabling the precalculation of backup next hops. Disabling the
feature could result in router global repairs as high as 800 ms for a link or
node failure without a precalculated backup.
To disable LDP LFA support for IP FRR, perform the following steps starting in
38 28/1543-AXI 101 09/1 Uen J | 2017-11-22

Configuration
Steps
1. Enter the context, access LDP configuration mode, and disable IP-FRR.
Example
[local]Ericsson(config)#context local
[local]Ericsson(config-ctx)#router ldp
[local]Ericsson(config-ldp)#no ipfrr
[local]Ericsson(config-ldp)#commit
[local]Ericsson(config-ctx)#exit
2. Confirm the configuration. The Fast-reroute field displays the value

disabled.
Example
NSR State: Standby not Ready
Graceful restart enabled, Fast-reroute disabled, Track-IGP-metric disabled, Create-LSP-Circuit di →
sabled, Tunnel-Shortcuts
2.17 Enable Multipoint Label Distribution Protocol

This example enables the MLDP.
198.51.100.200/32 192.0.2.211/32 192.0.2.222/32

Source 198.51.100.0/29 192.0.2.0/29 Receiver
R0 R1 R2
LER P Router
192.0.2.9/29 192.0.2.16/29
Receiver
R3
192.0.2.233/32
G108986A
Figure 18 Enable MLDP

Figure 18 shows a network of four routers configured for mLDP.
To enable mLDP, perform the following steps starting in global configuration

mode.
28/1543-AXI 101 09/1 Uen J | 2017-11-22 39

LDP
Steps
1. Enter the context, access LDP configuration mode, and enable MLDP in
R0. Similarly, enable R1, R2 and R3 routers.
Example
[local]R0(config-ldp)#mldp
2. To confirm the configuration execute show ldp summary command

where the Dynamic Capability Announcement is enabled and Dynamic
Capabilities is P2MP.
Example
max-session: 2010
Dynamic Capabilities: p2mp
3. Execute show ldp neighbor command in the neighbor where two new
flags Y and M are available.
Example
X - ExplicitNullEnabled, C - ExplicitNullStatusChanging
G - Graceful Restart Supported, L - Session Life Extended
U - Unrecognized Notification Capable, V - Reachable Via Tunnel-Shortcut
W - Typed wildcard FEC capable, Y - Dynamic Capability announcement
M - P2MP capable
SHld - Session Holdtime Left, HHld - Hello Holdtime Left
192.0.2.211 192.0.2.211:0 Oper AGMUWY 81 10 int1
When an application (MVPN) is using in-band signaling for creating the

P2MP tree and sends muliticast traffic, where R0 is the root and R2 and
R3 is the leaf node The application triggers a tree creation in R2 towards
R0 with source address (50.1.1.1), group address (225.1.1.1) and RD
(100:1). LDP allocates a label for this FEC and sends the label mapping
message towards R1 which is the best path next hop to R0. R1
propagates this label mapping message to R0 after allocating its own local
label for this FEC. The command output for show ldp mldp binding
detail command in R2, R1 and R0 is shown below. The following
example is displayed for R2:
40 28/1543-AXI 101 09/1 Uen J | 2017-11-22

Configuration
Example
[local]R2(config)#show ldp mldp binding
Local/In - local/input label binding, Remote/Out - remote/output label binding
Oif - Outgoing Interface
Fec-Root Opq-tlv-type Upstream Node Local/In Remote/Out Downstream Node Oif
198.51.100.200 Transit-vpnv4 192.0.2.211 719360
Example
[local]R2(config)#show ldp mldp binding detail
Fec Root Node : 198.51.100.200 Type : P2MP
Opaque TLV Data:
Type : Transit-vpnv4 Length : 16
Source : 50.1.1.1
Group : 225.1.1.1
RD : 429496729601
Local Label : 719360 Local Label alloc_time : Apr 4 05:53:07.038
Upstream Node : 192.0.2.211 Label upstream adv_time : Apr 4 05:53:07.038
Flags : adv-up-peer, local-rec, sent-to-lrm
No of Oifs : 0
Oif(s
The following example is displayed for R1:
Example
198.51.100.200 Transit-vpnv4 198.51.100.200 719360 719360 192.0.2.222 int2
Example
Opaque TLV Data:
Source : 50.1.1.1
Group : 225.1.1.1
RD : 429496729601
Flags : adv-up-peer, sent-to-lrm, downstream-mapping-rcved
No of Oifs : 1
Oif(s) :
Label : 719360 Outgoing cct : 3/5:511:63:31/1/1/7
Interface : int2 Down_peer : 192.0.2.222
Uptime : 00:00:39 Label received time : Apr 4 05:53:10.438
Oif-Flags :
The following example is displayed for R0:
Example
198.51.100.200 Transit-vpnv4 0.0.0.0 0 719360 192.0.2.211 int1
Example
Opaque TLV Data:
Source : 50.1.1.1
Group : 225.1.1.1
RD : 429496729601
Local Label : 0 Local Label alloc_time :
Upstream Node : 0.0.0.0 Label upstream adv_time :
Flags : sent-to-lrm, local-root, downstream-mapping-rcved
28/1543-AXI 101 09/1 Uen J | 2017-11-22 41

LDP
No of Oifs : 1
Oif(s) :
Oif-Flags :
When a new receiver joins at R3 for the same source at R0 with source
address (50.1.1.1), group address (225.1.1.1) and RD (100:1), LDP
reuses the P2MP tree which is already created from R0. This creates a
new branch at R1 towards R3, which means that R1 has the new oif
towards R3. The command output for show ldp mldp binding detail
command in R3, R2, R1 and R0 is displayed below: The following
Example
198.51.100.200 Transit-vpnv4 192.0.2.211 719362
Example
Opaque TLV Data:
Source : 50.1.1.1
Group : 225.1.1.1
RD : 429496729601
No of Oifs : 0
Oif(s)
The following example is displayed for R2 which do not have an update:
Example
198.51.100.200 Transit-vpnv4 192.0.2.211 719360
Example
Opaque TLV Data:
Source : 50.1.1.1
Group : 225.1.1.1
RD : 429496729601
No of Oifs : 0
Oif(s
The following example is displayed for R1 with new oif to R3.
Example
42 28/1543-AXI 101 09/1 Uen J | 2017-11-22

Configuration

198.51.100.200 Transit-vpnv4 198.51.100.200 719360 719360 192.0.2.222 int2
719362 192.0.2.233 int3
Example
Opaque TLV Data:
Source : 50.1.1.1
Group : 225.1.1.1
RD : 429496729601
Flags : adv-up-peer, sent-to-lrm, downstream-mapping-rcved
No of Oifs : 2
Oif(s) :
Oif-Flags :
Oif-Flags :
The following example is displayed for R0 which do not have an update.
Example
198.51.100.200 Transit-vpnv4 0.0.0.0 0 719360 192.0.2.211 int1
Example
Opaque TLV Data:
Source : 50.1.1.1
Group : 225.1.1.1
RD : 429496729601
Local Label : 0 Local Label alloc_time :
Upstream Node : 0.0.0.0 Label upstream adv_time :
Flags : sent-to-lrm, local-root, downstream-mapping-rcved
No of Oifs : 1
Oif(s) :
Oif-Flags :
2.18 Configure mLDP FRR Link Protection

mLDP link protection enables fast reroute of traffic carried over P2MP LSPs in
a link failure. In MPLS networks, the links to the LSRs are protected using
LDP LFA and LDP Remote LFA (RLFA) paths.
2.18.1 mLDP FRR Link Protection by LFA
This example configures mLDP FRR link protection by using LFA backup
tunnel. To configure LFA, perform the following steps starting in global
28/1543-AXI 101 09/1 Uen J | 2017-11-22 43

LDP
configuration mode. Make sure that mLDP is configured. For instructions on

how to enable mLDP, see Enable Multipoint Label Distribution Protocol.
(1.1.1.1) (2.2.2.2) (3.3.3.3) (4.4.4.4)

Source Receiver
R1 R2 R3 R4
(5.5.5.5)
R5
G108980A
Figure 19 mLDP FRR Link Protection by LFA
Steps
1. On R2, enter the context, enable LFA under OSPF. Similarily, enable R3
and R5. The following example is displayed for R2:
Example
[local]R2(config-ctx)#router ospf 1
[local]R2(config-ospf)#area 0.0.0.0
[local]R2(config-ospf-area)#interface 2to3
[local]R2(config-ospf-if)#network-type point-to-point
[local]R2(config-ospf-if)#lfa
2. Configure BFD on both sides of the protected Link A. Similarily, configure

BFD on R3. The following example is displayed for R2:
Example
[local]R2>context local
[local]R2(config-ctx)#router bfd
[local]R2(config-bfd)#interface 2to3
[local]R2(config-bfd-if)#minimum transmit-interval 3.3
[local]R2(config-bfd-if)#minimum receive-interval 3.3
3. Enable FRR on PLR router R2. It's enabled by default. The following
44 28/1543-AXI 101 09/1 Uen J | 2017-11-22

Configuration
Example
[local]R2(config-ldp)#ipfrr
[local]R2(config-ldp)#mldp link-protection
4. Confirm the configuration. The following example is displayed for R2:
Example
[local]R2>show mpls lsp p2mp
Codes : S - MPLS-Static, R - RSVP, L - LDP, I - ISIS, O - OSPF, B - BGP, T - SR-
STATIC, P - PCC, PW - Pseudowire, ML - MLDP
Type In Label Action Direct Next hop Out Label Adjacency Id
ML 0 push 2.3.1.2 716803 0x400008
push 2.5.1.2 655366 716803 0x400009
[local]R2>show ldp mldp binding
2.2.2.2 Transit-v4 0.0.0.0 0 716803 3.3.3.3 2to3
2.18.2 Configure mLDP FRR Link Protection by RLFA
This example configures mLDP FRR link protection by using RLFA backup
tunnel. To configure RLFA, perform the following steps starting in global
configuration mode. Make sure that mLDP is configured. For instructions on
how to enable mLDP, see Enable Multipoint Label Distribution Protocol.
(1.1.1.1) (2.2.2.2) (3.3.3.3) (4.4.4.4)

Link A
Source Receiver
R1 R2 R3 R4
(RLFA for
R5 R6 link A)
(5.5.5.5) (6.6.6.6)
G108981A
Figure 20 mLDP FRR Link Protection by RLFA
28/1543-AXI 101 09/1 Uen J | 2017-11-22 45

LDP
Steps
1. On R2, enter the context, enable RLFA under OSPF. Similarily, enable R3,
R5 and R6. The following example is displayed for R2:
Example
[local]R2(config-ctx)#router ospf 1
[local]R2(config-ospf)#area 0.0.0.0
[local]R2(config-ospf-area)#interface 2to3
[local]R2(config-ospf-if)#network type point-to-point
[local]R2(config-ospf-if)#lfa remote-lfa
2. Configure BFD on both sides of the protected Link A. In this topology,

that's R2 and R3. The following example is displayed for R2:
Example
[local]R2>context local
[local]R2(config-ctx)#router bfd
[local]R2(config-bfd)#interface 2to3
[local]R2(config-bfd-if)#minimum transmit-interval 3.3
[local]R2(config-bfd-if)#minimum receive-interval 3.3
3. Enable FRR on the protected router R2 and R6, which is the RLFA for
Link A. It's enabled by default. Then configure the target LDP as well.
Following example is displayed for R2.
Example
[local]R2(config-ldp)#ipfrr
[local]R2(config-ctx)#targeted advertise ipv4
[local]R2(config-ldp)#mldp link-protection
[local]R2(config-ldp)#neighbour 6.6.6.6 targeted
4. Confirm the configuration. Following example is displayed for R2.
Example
[local]R2>show mpls lsp p2mp
Codes : S - MPLS-Static, R - RSVP, L - LDP, I - ISIS, O - OSPF, B - BGP, T - SR-
STATIC, P - PCC, PW - Pseudowire, ML - MLDP
Type In Label Action Direct Next hop Out Label Adjacency Id
ML 0 push 2.3.1.2 716803 0x400008
push 2.5.1.2 655381 655365 716805 0x40000c
46 28/1543-AXI 101 09/1 Uen J | 2017-11-22

Configuration
[local]R2>show ldp mldp binding

2.2.2.2 Transit-v4 0.0.0.0 0 716803 3.3.3.3 2to3
28/1543-AXI 101 09/1 Uen J | 2017-11-22 47

LDP
3 Operations
To monitor, troubleshoot, and administer LDP, perform the operations tasks

described in Table 1. Enter the clear and debug commands in exec mode.
You can enter the show commands in any mode. The command syntax in the
table displays only the root command. For the complete command syntax, see
the Command List.
Table 1 LDP Operations Tasks
Task Root Command

Enable the generation of debug messages for all LDP events. debug ldp all
Limit the generation of LDP debug messages to specific interfaces, debug ldp filter
neighbor IP addresses, or IP prefixes.
Enable the generation of debug messages for LDP messages. debug ldp message
Enable the generation of debug messages for mLDP messages. debug ldp mldp
Enable the generation of debug messages for LDP protocol debug ldp protocol
interaction.
Initiate an MPLS ping across an LDP LSP. ping mpls ldp
Display the LDP commands configured in the current context. show configuration ldp
Display the LDP interface IP address-to-LSR ID mappings. show ldp address
Display LDP label binding information. show ldp binding
Display LDP interface information. show ldp interface
Display information about an MPLS LSP. show mpls
Display LDP neighbor information. show ldp neighbor
Display a summary of LDP information. show ldp summary
Display mLDP binding information. show ldp mldp binding
Display information of point-to-multipoint MPLS label mapping. show mpls label-mapping
p2mp detail
48 28/1543-AXI 101 09/1 Uen J | 2017-11-22

LDP Glossary
4 LDP Glossary
ECMPs
Equal-Cost Multiple Paths
FEC
Forward Error Correction
FRR
Fast Reroute
IGP
Interior Gateway Protocol
IS-IS
Intermediate System-to-Intermediate System
LDP
Label Distribution Protocol
LER
Label Edge Router
LFA
Loop-Free Alternate
LFIB
Label Forwarding Information Base
LIB
Label Information Base
28/1543-AXI 101 09/1 Uen J | 2017-11-22 49

LDP
LSPs
Label-Switched Paths
LSR
Label-Switched Router
MD5
Message Digest 5
mLDP
Multipoint Label Distribution Protocol
MBB
Make Before Break
MPLS
Multiprotocol Label Switching
OSPF
Open Shortest Path First
TCP
Transmission Control Protocol
TLV
Type-Length-Value
50 28/1543-AXI 101 09/1 Uen J | 2017-11-22

Reference List
Reference List
RFCs
• RFC 5919, Signaling LDP Label Advertisement Completion
• RFC 5443, LDP IGP Synchronization
• RFC 3612, Applicability Statement for Restart Mechanisms for the Label
Distribution Protocol (LDP)
• RFC 3478, Graceful Restart Mechanism for LDP
• RFC 3215, LDP State Machine
• RFC 6388, Label Distribution Protocol Extensions for Point-to-Multipoint

and Multipoint-to-Multipoint Label Switched Paths
• RFC 7438, Multipoint LDP (mLDP) In-Band Signaling with Wildcards
28/1543-AXI 101 09/1 Uen J | 2017-11-22 51

Operating Instructions: 28/1543-AXI 101 09/1 Uen J

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Operating Instructions: 28/1543-AXI 101 09/1 Uen J

Uploaded by

Copyright:

Available Formats

LDP

28/1543-AXI 101 09/1 Uen J

© Ericsson AB 2017. All rights reserved. No part of this document may be

28/1543-AXI 101 09/1 Uen J | 2017-11-22

28/1543-AXI 101 09/1 Uen J | 2017-11-22

28/1543-AXI 101 09/1 Uen J | 2017-11-22

This document provides an overview of the Label Distribution Protocol (LDP)

1.1 About LDP

LDP enables dynamic label allocation and distribution in a Multiprotocol Label

To discover LDP peers, an LSR periodically transmits LDP Hello messages.

The router supports a maximum of 1,024 targeted LDP sessions or a

28/1543-AXI 101 09/1 Uen J | 2017-11-22 1

1.1.1 LDP Neighbor Discovery

1.1.2 LDP Hello Messages

1.1.3 Label Advertisement Completion

Sending an end-of-LIB notification to a peer can be useful in the following

• When LDP-IGP synchronization procedures are used (RFC 5443, ). After

• Following LDP session reestablishment when graceful restart is applied

An end-of-LIB notification is sent only if the peer advertised an unrecognized

1.1.3.1 Determine Unrecognized Notification Capability

An LDP speaker that supports end-of-LIB notification must send a capability

The unrecognized notification capability TLV must be set as follows:

2 28/1543-AXI 101 09/1 Uen J | 2017-11-22

• Unrecognized Notification: 0x0603

Use the show ldp neighbor command to determine the unrecognized

Use the debug ldp message initialization command to confirm that

1.1.3.2 Determine Typed Wildcard FEC Capability

The end-of-LIB notification message carries a Forward Error Correction (FEC)

An LDP speaker that supports end-of-LIB notification must send a capability

The typed wildcard capability TLV must be set as follows:

• Typed Wildcard FEC Cap: 0x050B

Use the debug ldp message initialization command to confirm that

28/1543-AXI 101 09/1 Uen J | 2017-11-22 3

1.1.3.3 Determine End-of-LIB Notification

The end-of-LIB notification message carries:

Timers are used to manage the receipt of end-of-LIB notifications. Following

Use the show ldp summary command to determine whether end-of-LIB

1.1.4 Reduce Traffic Disruption Using LDP Loop-Free Alternates

4 28/1543-AXI 101 09/1 Uen J | 2017-11-22

1.1.5 Targeted LDP for Remote LFA

1.1.6 Multipoint Label Distribution Protocol

Multipoint LSPs transport end-user traffic (Layer 3 multicast traffic or Layer 2

mLDP enables routers to exchange P2MP capability support after an LDP

28/1543-AXI 101 09/1 Uen J | 2017-11-22 5

1.1.6.1 mLDP Fast Reroute

mLDP Fast Reroute (FRR) mechanism reduces the loss of connectivity in an

• Supports both IPv4 and IPv6 traffic

• Supports P2MP in-band signaling

• Supports switchover time of less than 50 milliseconds

1.1.6.2 Link Protection Using mLDP FRR

1.1.6.3 Link Protection Using LFA Backup Tunnel

The sequence of events that occur in an mLDP LFA FRR scenario is

6 28/1543-AXI 101 09/1 Uen J | 2017-11-22

LFA Backup Tunnel

Figure 1 Link Protection Using LFA Backup Tunnel

3. Backup tunnels are configured for Link A.

4. mLDP LSP is built from D, B, and A towards the root.

5. Router A installs a downstream forwarding replication over Link A to

When a failure occurs on Link A:

28/1543-AXI 101 09/1 Uen J | 2017-11-22 7

LFA Backup Tunnel

Figure 2 LFA Backup Tunnel–Link Failure

2. Router C performs Penultimate Hop Popping (PHP) and removes the