247
Usage guidelines
LDP convergence on a link is completed when the followings occur:
The local device establishes an LDP session to at least one peer, and the LDP session is
already in Operation state.
The local device has distributed the label mappings to at least one peer.
MPLS traffic forwarding might be interrupted in one of the following scenarios:
When the peer uses the Ordered label distribution control mode, the local device needs to wait
for a label mapping from its downstream LSR after the LDP session goes into Operation state.
If LDP immediately notifies IGP of the LDP convergence completion when the label mapping
from downstream is not received, MPLS traffic forwarding might be interrupted.
When a large number of label mappings are distributed from downstream, if LDP immediately
notifies IGP of the LDP convergence completion, label advertisement might not be finished, and
MPLS traffic forwarding is interrupted.
In these scenarios, you must use this command to configure the notification delay. When LDP
convergence on a link is completed, LDP waits a delay time to notify IGP of the LDP convergence
completion to reduce the traffic interruption time.
Examples
# Configure the notification delay as 30 seconds.
<Sysname> system-view
[Sysname] mpls ldp
[Sysname-ldp] igp sync delay 30
Related commands
igp sync delay on-restart
mpls ldp igp sync disable
mpls ldp sync (IS-IS view)
mpls ldp sync (OSPF view/OSPF area view)
igp sync delay on-restart
Use igp sync delay on-restart to configure the maximum delay for LDP to notify IGP of the LDP IGP
synchronization status after an LDP restart or an active/standby switchover occurs.
Use undo igp sync delay on-restart to restore the default.
Syntax
igp sync delay on-restart time
undo igp sync delay on-restart
Default
The maximum notification delay is 90 seconds.
To Next Page
Loading...
