Brocade Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide (Supporting R05.6.00) - Manual (Page 384)

360 Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide
53-1003031-02
MPLS LDP-IGP synchronization
2
Graceful restart: enabled
Peer reconnect time(msec): 120000, peer recovery time(msec): 0
State: not started
IGP Sync:
Unrecognized Notification Capability: Local: On, Remote: On
Local State: In-sync, RemoteState: In-sync
EOL notification time: 60000 ms, Timer not running
EOL transmit label silence time: 1000 ms, Timer not running
Syntax: show mpls ldp session value
Use the show mpls ldp interface command to view whether or not LDP-IGP sync is enabled on the
interface.
Brocade# show mpls ldp int e2/16
e2/16, label-space ID: 0
Nbr count: 1
Hello interval: 5 sec, next hello: 2 sec
Hello timeout: 15 sec
Current IGP Sync state: In Sync
Syntax: show mpls ldp int value
Use the show mpls interface command to view the current cached LDP-IGP sync state.
Brocade# show mpls int e2/2
Admin: Up Oper: Up
Maximum BW: 0 kbps, maximum reservable BW: 0 kbps
Admin group: 0x00000000
Reservable BW [priority] kbps:
[0] 0 [1] 0 [2] 0 [3] 0
[4] 0 [5] 0 [6] 0 [7] 0
Last sent reservable BW [priority] kbps:
[0] 0 [1] 0 [2] 0 [3] 0
[4] 0 [5] 0 [6] 0 [7] 0
LDP tunnel count: 0
Current IGP Sync State: not-in-sync
Syntax: show mpls int value
LDP Graceful Restart (GR)
This section describes the functionality of the LDP Graceful Restart feature based on RFC 3478
(Graceful Restart Mechanism for Label Distribution Protocol).
LDP Graceful Restart (GR) helps minimize MPLS traffic loss when an LDP component is restarting
in a router that is capable of preserving its MPLS forwarding states across restart. LDP GR works
between a router and its neighbor and its capability must be advertised when sending an LDP
Initialization message.
An LDP restart triggered by MP failover due to a fault of the active MP or user-commanded
switchover is the only scenario where the MPLS forwarding state is preserved.