Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

MPLS LDP session protection and mpls ldp neighbor ip-addr targeted command

Hi all!

Normally LDP neighbors are found automatically by sending UDP Hello packets on Port 646 with the destination of multicast address out of each LDP enabled interface. With mpls session protection a targeted LDP session must be established.

In such case Hello packets are sent as unicast packets using UDP on port 646 and destined to the targeted peer.

But it is not required to use mpls ldp neighbor ip-addr targeted command to configure session protection.

How  is session  destination  IP address determined?

Why do I not need  to specify session destination IP with mpls ldp neighbor ip-addr targeted command?


Cisco Employee

HiPlease read below quote, I


Please read below quote, I hope this will answer your question


MPLS LDP Session Protection uses LDP Targeted Hellos to protect LDP sessions. Take, for example, two directly connected routers that have LDP enabled and can reach each other through alternate IP routes in the network. An LDP session that exists between two routers is called an LDP Link Hello Adjacency. When MPLS LDP Session Protection is enabled, an LDP Targeted Hello Adjacency is also established for the LDP session. If the link between the two routers fails, the LDP Link Adjacency also fails. However, if the LDP peer is still reachable through IP, the LDP session stays up, because the LDP Targeted Hello Adjacency still exists between the routers. When the directly connected link recovers, the session does not need to be reestablished, and LDP bindings for prefixes do not need to be relearned.


Let me know if you have further query



CreatePlease login to create content