< Home

LDP_1.3.6.1.2.1.10.166.4.0.1 mplsLdpInitSessionThresholdExceeded

Description

LDP/4/SSNTHRESHOLDEXCEED: [oid] The number of failures in LDP session negotiation reached threshold. (LdpId=[OPAQUE], LdpEntityIndex=[GAUGE], Times=[INTEGER])

The value of mplsLdpEntityInitSesThreshold is not 0, and the number of times for session negotiation through Init messages exceeds this threshold.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.2.1.10.166.4.0.1

Warning

environmentalAlarm(6)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

LdpId

Indicates the local LDP peer ID.

LdpEntityIndex

Indicates the index of an LDP entity.

Times

Indicates the number of session initialization messages sent.

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

1. Label advertisement mode changes, and the label advertisement modes are inconsistent on the two ends of the session. The version does not support the DOD mode. The trap is generated when the peer supports the DOD mode during interworking.

2. The negotiation of the Keepalive period fails. The trap is generated when the Keepalive period of the peer is 0. In this version, the minimum value of the Keepalive period is set to 30. The trap is generated when the Keepalive period of the peer can be set to 0.

Procedure

  1. Check whether the devices at the two ends of the session are Huawei devices.

    • If so, go to Step 2.

    • If not, go to Step 3.

  2. In this case, the trap message is not generated. Go to Step 6.
  3. Check the configurations of the Huawei devices, and run the display current-configuration configuration mpls-ldp command to check whether other configurations exist in the MPLS LDP view.

    • If so, go to Step 4.

    • If not, go to Step 5.

  4. The setup of the session is not affected even if other configurations exist in the MPLS LDP view. Save the configurations, and then go to Step 6.
  5. It can be concluded that the fault is caused by the configuration of the peer. In this case, go to Step 7.
  6. Collect alarm information and configuration information, and then contact technical support personnel.
  7. Contact the technical personnel of the peer vendor, and then go to Step 8.
  8. End.

Related Information

None

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