LDP_1.3.6.1.2.1.10.166.4.0.1 Session-Retry

Trap Buffer Description

The number of session initialization messages exceeds the mplsLdpEntityInitSessionThreshold. (PeerLdpId=[PeerLdpId],EntityIndex=[EntityIndex],Times=[InitSessionThreshold])

mplsLdpEntityInitSessionThreshol was not zero and the sequence number of an Initialization message exceeded mplsLdpEntityInitSessionThreshold.

Trap Attributes

Trap Attribute Description

Alarm or Event

Event

Trap Severity

Warning

Mnemonic Code

LDP_SSN_INIT_EXCEED

Trap OID

1.3.6.1.2.1.10.166.4.0.1

MIB

MPLS-LDP-STD-MIB

Alarm ID

This is an event trap and does not involve alarm ID.

Alarm Name

This is an event trap and does not involve alarm name.

Alarm Type

This is an event trap and does not involve alarm type.

Raise or Clear

This is an event trap and does not involve alarm generation or clearance.

Match trap

-

Trap Buffer Parameters

Parameter Description

PeerLdpId

LDP ID.

EntityIndex

LDP instance index.

InitSessionThreshold

Indicates the number of attempts for session negotiation through Init messages.

VB Parameters

VB OID VB Name VB Index

1.3.6.1.2.1.10.166.4.1.2.3.1.11

mplsLdpEntityInitSessionThreshold

mplsLdpEntityLdpId

mplsLdpEntityIndex

Impact on the System

The session cannot be set up. The original services or newly added ones that depend on the session are interrupted.

Possible Causes

  • Cause 1: The local end no longer supports the DoD mode but the peer supports DoD mode, leading to label advertisement mode inconsistency. Cause 2: Keepalive time negotiation fails because the Keepalive time value on the peer end is set to 0. In this version, the minimum value is 30.This means the log is displayed when the peer Keepalive time is 0s.

Procedure

1. Check that devices on both ends of the LSP are Huawei devices.

  • If both of them are Huawei devices, go to Step 2.
  • If one device is a non-Huawei device, go to Step 3.

2. Check the cause for this trap message and go to Step 5.

3. Check the Huawei device configurations. Run the display this in the MPLS LDP view to check whether other configurations exist.

  • If other configurations are displayed, go to Step 4.
  • If no other configuration is displayed, the trap message is triggered by an error in the peer device. Go to Step 6.

4. Record configuration information and go to Step 5.

5. Collect the alarm information, log information, and configuration information, and then Collect log information and configuration information, and then contact technical support personnel..

6. Ask the customer to contact technical support personnel of the vendor to troubleshoot the problem and go to Step 7.

7. End.

Copyright © Huawei Technologies Co., Ltd.
Copyright © Huawei Technologies Co., Ltd.
Next topic >