LDP/4/hwMplsLdpMultiLinkConfigInconsistent_active

Message

LDP/4/hwMplsLdpMultiLinkConfigInconsistent_active: MPLS LDP multi-link or local-remote adjacencys configurations are inconsistent, LDP Session or LSP maybe interrupts. (VrfName=[VrfName], PeerLsrId=[PeerLsrId], LocalLsrId=[LocalLsrId], ConfigIfName=[ConfigIfName], ConfigRmtPeerIp=[ConfigRmtPeerIp], ConfigType=[ConfigType], EffectKa=[EffectKa], EffectTa=[EffectTa], EffectLam=[EffectLam])

Description

This object indicates that MPLS LDP multi-link (including local and remote coexistence sessions) configurations are inconsistent.

Parameters

Parameter Name	Parameter Meaning
VrfName	VRF name of LDP session exists.
PeerLsrId	LDP session ID.
LocalLsrId	Local LSR ID.
ConfigIfName	Configure the current interface name.
ConfigRmtPeerIp	Configure the IP address of the remote session.
ConfigType	Configuration inconsistent type.
EffectKa	KeepAlive value used by the LDP session.
EffectTa	LDP transport addresses used by the session.
EffectLam	Peer use label advertisement mode.

Possible Causes

When LDP sessions are configured with multiple links or local-remote adjacencys, link parameters may be inconsistent.

Procedure

1. If the ConfigType field value in the alarm is Keepalive Hold Timer, check whether the same Keepalive Hold time is configured on each interface and remote peer of a session.

If they are different, modify the Keepalive Hold timer value on the interface or remote peer to ensure that the same Keepalive Hold timer is used. Then, go to Step 4.
If they are the same, go to Step 5.

2. If the ConfigType field value in the alarm is Transport Address, check whether the same transport address is configured on each interface corresponding to a session.

If they are different, modify the transport address on an interface to ensure that the same transport address is used. Then, go to Step 4.
If they are the same, go to Step 5.

3. If the ConfigType field value in the alarm is Label Advertisement Mode, check whether the same label advertisement mode is configured on each interface or remote peer of a session.

If they are different, modify the label advertisement configuration on the interface or remote peer to ensure that the same label advertisement mode is used. Then, go to Step 4.
If they are the same, go to Step 5.

4. Check whether the alarm is cleared.

If the alarm is cleared, go to step 6.
If the alarm persists, go to step 5.

5. Collect alarm and configuration information and contact technical support engineers.

6. End.