LDP Global Tasks

Typically, you do not configure anything for LDP at the global level, but you can perform the following optional tasks.

1. (Optional) Enable LDP and topology-driven LSP. Any LDP-related command creates LDP implicitly, negating the need to issue this command.

   host1(config)#mpls ldp

2. (Optional) Configure the redistribution of IGP routes to LDP.

   host1(config)#mpls ldp redistribute ospf route-map boston5

3. (Optional) Configure a global LDP profile that specifies how long an LSR maintains link hello records before another link hello is sent, the interval between link hellos, or both.

   host1(config)#mpls ldp interface profile ldp1

   host1(config-ldp)#hello hold-time 55

   host1(config-ldp)#hello interval 10

4. (Optional) Configure lists of peer addresses that targeted hello messages are sent to or accepted from.

   host1(config)#mpls ldp targeted-hello send list 10.21.5.87

   host1(config)#mpls ldp targeted-hello receive list 192.168.45.25

   Note: The mpls ldp targeted-hello receive list command is unnecessary if you configure the mpls ldp targeted-hello send list command.

5. (Optional) Configure the hold time and interval values for targeted hello messages used in LDP extended discovery.

   host1(config)#mpls ldp targeted-hello holdtime 90

   host1(config)#mpls ldp targeted-hello interval 30

6. (Optional) Configure LDP session retry values.

   host1(config)#mpls ldp session retry-time 2

   host1(config)#mpls ldp session retries 1800

7. (Optional) Configure the period that LDP negotiates with its peer for which the LDP session is maintained in the absence of any LDP messages.

   host1(config)#mpls ldp session holdtime 1800

8. (Optional) Configure the interval at which LDP sends session keepalive messages.

   host1(config)#mpls ldp session keepalive-time 180

9. (Optional) Specify an IP address to be advertised to peers as the transport address in discovery hello messages.

   host1(config)#mpls ldp discovery transport-address 192.168.34.2

10. (Optional) Configure independent control as the method of label distribution that LDP uses.

    host1(config)#mpls ldp independent-control

11. (Optional) Configure LDP to advertise the explicit null label or a non-null label for the egress router to achieve ultimate hop popping.

    host1(config)#mpls ldp egress-label explicit-null

For topology-driven LSPs, perform the following LDP configuration tasks.

1. (Optional) Configure the LSR to create topology-driven LSPs. Enabling LDP automatically creates topology-driven LSPs.

   host1(config)#mpls topology-driven-lsp

2. (Optional) Specify filters for the routes and peers to which the labels are advertised.

   host1(config)#mpls ldp advertise-labels host-only

3. (Optional) Specify the LSPs to be put into the IP routing table for forwarding plain IP traffic.

   Note: This step is not optional if you are using a topology-driven network to forward plain IP packets.

   host1(config)#ldp ip-forwarding host-only

4. (Optional) Establish a policy governing the distribution of incoming LDP labels.

   host1(config)#mpls ldp advertise-labels for boston1

5. (Optional) Remove and then reestablish existing LDP LSPs and to restart topology-driven LDP. Use this command when you have modified or created policies or access lists (with the mpls ldp-ip-forwarding and mpls ldp advertise-labels commands) and want them to be applied to LDP LSPs that are already in an up state.

   host1#clear mpls ldp

Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice.