LDP/4/LDP_SESSION_DOWN

Message

LDP/4/LDP_SESSION_DOWN: MPLS LDP session went down. (PID=[hPid], CID=[hCid], SessionUpTime=[SessionUpTime], SessionDownTime=[SessionDownTime], GRSessionFlag=[FTFlag], PeerID=[PeerID], DiscoverySource=[DiscoverySourceIndex], LocalAddr=[LocalAddress], PeerAddr=[PeerAddress], SessionRole=[SessionRole], SessionType=[SessionType], KASendCount=[KaSendCount], KARecvCount=[KaRecvCount], VrfName=[VrfName], TCPConnSocket=([TcpFD]FD,[TcpPipeId]PipeID), TCPLsnSocket=([LsFD]FD,[LsPipeId]PipeID), FlowCount=[FlowCount], FlowRelCount=[FlowRelCount], DetailReason=[SubReason], Reason=[Reason], GR-helperFlag=[GRHelperFlag], LastKaSendTime=[LastKaSendTime], LastKaRecvTime=[LastKaRecvTime])

Description

The reason of the LDP session Down event and help information were displayed.

Parameters

Parameter Name	Parameter Meaning
hPid	Local PID
hCid	Local CID
SessionUpTime	Time when the session was established
SessionDownTime	Time when the session went Down
FTFlag	Whether the session is enabled with GR
PeerID	Peer ID
DiscoverySourceIndex	Index of an interface
LocalAddress	Local address
PeerAddress	Peer address
SessionRole	Role in a session
SessionType	LDP session type
KaSendCount	Number of sent Keepalive messages
KaRecvCount	Number of received Keepalive messages
VrfName	VPN name
TcpFD	TCP socket ID
TcpPipeId	TCP pipe ID
LsFD	TCP listening socket ID
LsPipeId	TCP listening socket pipe ID
FlowCount	Number of flows
FlowRelCount	Number of parsed flows
SubReason	Subreason for an LDP session disconnection
Reason	Reason for an LDP session disconnection
GRHelperFlag	Whether the LSR is a GR Helper
LastKaSendTime	Time when the last Keepalive message was sent
LastKaRecvTime	Time when the last Keepalive message was received

Possible Causes

1-The Hello Hold timer of the LDP session expired.
2-The Keepalive Hold timer of the LDP session expired.
3-The reset mpls ldp command was run.
4-The undo mpls ldp command was run.
5-The undo mpls command was run.
6-The undo mpls ldp remote-peer command was run.
7-GR was enabled for the LDP session.
8-The value of the GR timer was changed.
9-The value of the Keepalive Hold timer was changed.
10-LDP MD5 was enabled for the LDP session.
11-The role of the LDP session changed.
12-The value of MTU was changed.
13-The transport address of the LDP session was changed.
14-An LSR ID of the LDP session was changed.
15-A Notification message was received.
16-The transport address of the LDP session was mismatched.
17-The protocol GR was configed for the LDP session.
18-The interface state was changed.
19-The TCP session was down.
20-Other.
21-A notification message was sent.
22-The LDP session cannot be set up.
23-An error message was received from a peer.
24-A socket error was received.
25-The LDP session was deleted.
26-The Capability configuration was changed.
28-The P2MP Capability configuration was changed.
29-An LSR ID of the LDP session was deleted.
30-The LDP session Protection time expired.
31-IGP delete RLFA iid.
32-Super large quantity messages were received.

Procedure

1. Collect the trap information, log information, and configuration information, and Collect log information and configuration information, and then contact technical support personnel.