76
Step Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter MPLS LDP view.
mpls ldp
N/A
3.
Enable MPLS LDP GR.
graceful-restart
Disabled by default.
4.
Set the FT reconnect time.
graceful-restart timer reconnect
timer
Optional.
300 seconds by default.
5.
Set the LDP neighbor liveness
time.
graceful-restart timer
neighbor-liveness
timer
Optional.
120 seconds by default.
6.
Set the LDP recovery time.
graceful-restart timer recovery
timer
Optional.
300 seconds by default.
Verifying the configuration
To test whether the MPLS LDP GR configuration has taken effect, you can perform graceful restart of MPLS
LDP. During the LDP restart process, you can see whether the packet forwarding path is changed and
whether packet forwarding is interrupted.
To restart MPLS LDP gracefully, perform the following task in user view:
Task Command
Remarks
Restart MPLS LDP gracefully.
graceful-restart mpls ldp
This command is only used to test
MPLS LDP GR function. It does not
perform active/standby
switchover. Do not perform this
operation in other cases.
Setting MPLS statistics reading interval
To use display commands to view LSP statistics, you must first set the statistics reading interval.
To set MPLS statistics reading interval:
Step Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter MPLS view.
mpls
N/A
3.
Set LSP statistics reading
interval.
statistics interval
interval-time
0 seconds by default: the system
does not read LSP statistics.
Inspecting LSPs
In MPLS, the MPLS control plane is responsible for establishing LSPs. However, when an LSP fails to
forward data, the control plane cannot detect the LSP failure or cannot do so in time. This makes network
maintenance difficult. To find LSP failures in time and locate the failed node, the device provides the
following mechanisms:
•
MPLS LSP ping
