© 2006 Cisco Systems, Inc. All rights reserved. MPLS v Label Assignment and Distribution Discovering LDP Neighbors

© 2006 Cisco Systems, Inc. All rights reserved. MPLS v Outline Overview Establishing an LDP Adjacent Session What Are LDP Hello Messages? Negotiating Label Space Discovering LDP Neighbors Negotiating LDP Sessions Discovering Nonadjacent Neighbors Summary

© 2006 Cisco Systems, Inc. All rights reserved. MPLS v LDP Neighbor Session Establishment LDP establishes a session in two steps: –Hello messages are periodically sent on all MPLS-enabled interfaces. –MPLS-enabled routers respond to received hello messages by attempting to establish a session with the source of the hello messages. LDP link hello message is a UDP packet sent to the all routers on this subnet multicast address ( ). TCP is used to establish the session. Both TCP and UDP use well-known LDP port number 646.

© 2006 Cisco Systems, Inc. All rights reserved. MPLS v LDP Link Hello Message Hello messages are sent to all routers reachable through an interface. LDP uses well-known port number 646 with UDP for hello messages. A 6-byte LDP identifier (TLV) identifies the router (first 4 bytes) and label space (last 2 bytes). The source address used for an LDP session can be set by adding the transport address TLV to the hello message.

© 2006 Cisco Systems, Inc. All rights reserved. MPLS v Label Space: Per-Platform The label forwarding information base (LFIB) on an LSR does not contain an incoming interface. The same label can be used on any interface and is announced to all adjacent LSRs. The label is announced to adjacent LSRs only once and can be used on any link. Per-platform label space is less secure than per-interface label space.

© 2006 Cisco Systems, Inc. All rights reserved. MPLS v Negotiating Label Space LSRs establish one LDP session per label space. –Per-platform label space requires only one LDP session, even if there are multiple parallel links between a pair of LSRs. Per-platform label space is announced by setting the label space ID to 0, for example: –LDP ID = :0

© 2006 Cisco Systems, Inc. All rights reserved. MPLS v LDP Neighbor Discovery An LDP session is established from the router with the higher IP address.

© 2006 Cisco Systems, Inc. All rights reserved. MPLS v LDP Session Negotiation Peers first exchange initialization messages. The session is ready to exchange label mappings after receiving the first keepalive.

© 2006 Cisco Systems, Inc. All rights reserved. MPLS v LDP Discovery of Nonadjacent Neighbors LDP neighbor discovery of nonadjacent neighbors differs from normal discovery only in the addressing of hello packets: –Hello packets use unicast IP addresses instead of multicast addresses. When a neighbor is discovered, the mechanism to establish a session is the same.

© 2006 Cisco Systems, Inc. All rights reserved. MPLS v Targeted LDP Session Applications MPLS Fast Reroute (FRR) MPLS Nonstop Forwarding (NSF) MPLS LDP Session Protection

© 2006 Cisco Systems, Inc. All rights reserved. MPLS v Summary UDP multicast is used to discover adjacent LDP neighbors, while TCP is used to establish a session. LDP hello messages contain an identifier field that uniquely identifies the neighbor and the label space. Per-platform label space requires only one LDP session. An LDP session is initiated in TCP from the higher IP address router. LDP session negotiation is a three-step process: establishing the TCP session, exchanging initialization messages, and exchanging initial keepalive messages. Nonadjacent neighbor discovery is accomplished by using unicast IP addresses instead of multicast.

© 2006 Cisco Systems, Inc. All rights reserved. MPLS v