LDP/4/LDP_SSN_ABNORM_MSG

Message

LDP/4/LDP_SSN_ABNORM_MSG: Statistics about incorrect messages received by the session. (MyPid=[MyPid], PeerLsrId=[PeerLsrId], LocalLsrId=[LocalLsrId], RcvAbnormMsgType=[RcvAbnormMsgType], RcvAbnormMsgNum=[RcvAbnormMsgNum])

Description

Statistics about received LDP messages that did not comply with the LDP protocol.

Parameters

Parameter Name	Parameter Meaning
MyPid	Process ID
PeerLsrId	Peer LSR ID
LocalLsrId	Local LSR ID
RcvAbnormMsgType	Type of a message that does not comply with the LDP protocol
RcvAbnormMsgNum	Number of messages of a specified type that do not comply with the LDP protocol

Possible Causes

LDP messages that do not comply with the LDP protocol are received.

The type of LDP message that does not comply with the LDP protocol is as follows:

RcvInitAbnorm: GR Init message with the Reconnect timer value of 0
RcvWildcardFECMap: Mapping message with an wildcard FEC value
RcvInvalidLabelMap: Mapping message with an invalid label
RcvWithdrawNoFEC: Withdraw message without any FEC information
RcvWithdrawInvalidLabel: Withdraw message with an invalid label
RcvWithdrawNotmapLabel: Withdraw message with a label value different from that in the DSCB
RcvReleaseNoFEC: Release message without any FEC information
RcvReleaseNonGen: Statistics about Release messages with non-general labels
RcvWithdrawNoMap: Withdraw message in which its label does not map to any FEC
RcvMaprepeat: Duplicate Mapping message.

Procedure

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