Brocade Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide (Supporting R05.6.00) User Manual
Page 339
Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide
315
53-1003031-02
show mpls ldp session detail
2
Example
Brocade# show mpls ldp session detail
Number of link LDP sessions: 1
Number of Operational link LDP sessions: 1
Number of targeted LDP sessions: 0
Number of Operational targeted LDP sessions: 0
Peer LDP ID: 10.12.12.12:0, Local LDP ID: 10.14.14.14:0, State: Operational
Adj: Link, Role: Active, Next keepalive: 4 sec, Hold time left: 39 sec
Keepalive interval: 5 sec, Max hold time: 40 sec
Configured keepalive timeout: 40 sec
Peer proposed keepalive timeout: 49 sec
Up time: 17 hr 21 min 23 sec
Neighboring interfaces: e2/1
TCP connection: 10.14.14.14:9005--10.12.12.12:646, State: ESTABLISHED
Number of FECs installed from peer: 7
Number of FECs filtered for peer (in/out): 0/0
Next-hop addresses received from the peer:
10.12.12.12 10.21.21.12 10.23.23.12 10.29.29.12 192.168.1.1
192.168.1.2 192.168.1.3 192.168.1.4 192.168.1.5
IGP Sync:
Unrecognized Notification Capability: Local: Off, Remote: Off
Local State: In-sync, RemoteState: -
Receive label silence time: 1000 ms, Timer not running
Graceful restart: disabled
Number of FECs Received from peer: 7
Number of FECs installed from peer: 7
Number of FECs filtered for peer(in/out): 0/3
Outbound FEC filtering prefix-list: list-out
MD5 Authentication Key
The MD5 authentication key is displayed in an encrypted form when you do not
have the correct privileges. When you have the correct permission, it displays as
clear text.
Neighboring interfaces
The interfaces where an LDP neighbor or adjacency relationship has been
established with the peer. When there are multiple connections between two
LDP-enabled peers, there can be multiple neighboring interfaces. When
applicable, the ‘Neighboring Interface’ field displays a VE interface specified by
the vid variable.
TCP connection
The local and remote IP addresses and port numbers for the TCP connection
between the peers.
State
The state of the TCP connection between the peers.
Next-hop addresses received
from the peer
The next-hop addresses received from the peer in LDP address messages.
The LSR uses this list of addresses to determine whether the peer is the correct
next hop for a destination route. When one of the addresses in this list is the
correct next hop for the route, the label received from the peer is installed for that
route, allowing it to be used for data forwarding.
Output field
Description