Link Adjacencies
Local Address
Local TCP Port
Local KA Timeout
Mesg Sent
FECs Sent
Addrs Sent
GR State
Nbr Liveness Time
Number of Restart
P2MP
Dynamic Capability
/Peer OverLoad Capab.
Advertise
Addr FEC OverLoad Sent : No
Mcast FEC Overload Sent: No
Serv FEC Overload Sent : No
-------------------------------------------------------------------------------
Base Resource Handling Procedures
Step 1
If the peer OR the local LSR does not support the Overload Protection Capability it means that the
associated adjacency [interface/peer] will be brought down as part of the base resource handling
mechanism.
The user can determine which interface or targeted peer was shut down, by applying the following
commands:
- [show router ldp interface resource-failures]
- [show router ldp targ-peer resource-failures]
show router ldp interface resource-failures
===============================================================================
LDP Interface Resource Failures
===============================================================================
srl
sru4
===============================================================================
show router ldp targ-peer resource-failures
7450 ESS MPLS Guide
: 0
Targeted Adjacencies
: 110.20.1.110
Peer Address
: 0
Peer TCP Port
: 40
Peer KA Timeout
: 0
Mesg Recv
: 0
FECs Recv
: 0
Addrs Recv
: Capable
Label Distribution
: 0
Max Recovery Time
: 0
Last Restart Time
: Not Capable
MP MBB
: Not Capable
LSR Overload
: Address/Servi*
Addr FEC OverLoad Recv : No
Mcast FEC Overload Recv: No
Serv FEC Overload Recv : No
srr
sr4-1-5-1
Label Distribution Protocol
: 1
: 10.8.100.15
: 0
: 40
: 1
: 0
: 0
: DU
: 0
: Never
: Not Capable
: Not Capable
Page 591
<---- /