No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Alarm Handling

AR100, AR120, AR160, AR1200, AR2200, AR3200, and AR3600 V300R003

This document provides the trap description, attributes, parameters, impact on the system, possible causes, procedures, and references. This document provides a complete set of traps, through which intended readers are kept of the running status of the device so as to locate faults.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
LSPM_1.3.6.1.2.1.10.166.2.0.2 mplsXCDown

LSPM_1.3.6.1.2.1.10.166.2.0.2 mplsXCDown

Description

LSPM/4/MPLSXCDOWN:OID [oid] LSP went Down. (BeginLspIndex=[octet].[octet].[octet], EndLspIndex=[octet].[octet].[octet])

A trap was generated when the LSP went Down.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.2.1.10.166.2.0.2

Warning

communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

BeginLspIndex

Index of the starting LSP, which is expressed in the format of [index of the starting LSP].[index of the inbound interface on the starting LSP].[index of the outbound interface on the starting LSP].

EndLspIndex

Index of the ending LSP, which is expressed in the format of [index of the ending LSP].[index of the inbound interface on the ending LSP].[index of the outbound interface on the ending LSP].

Impact on the System

1. If the protection function, such as FRR, is configured, services will not be affected.

2. If the protection function is not configured, all the services to be forwarded through the LSP will be interrupted.

Possible Causes

  • The interface went Down.

  • LDP LSPs went Down.

  • Static LSPs went Down.

  • In the case that the LDP LSP or BGP LSP was set Up, routes changed; or, in the case that the static LSP was bound to the tunnel, the next hop configured for the static LSP was inconsistent with the next hop in the routing table after routes changed.

  • The link was faulty.

Procedure

  1. If the snmp-agent trap enable is run and the trap functions indicating the status of LSPs are enabled in the LSPM, you can check the traps to obtain the types of the LSPs that go Down. If no trap functions indicating the status of LSPs are enabled in the LSPM, you can check the values of the BeginLspIndex and EndLspIndex fields in the traps to obtain the types of the LSPs that go Down. (Run the display mpls entry summary command in the diagnostic view to view the index ranges of LSPs of different protocols of the MPLS module.)

  2. Collect the trap information, log information, and configuration of the router, and Collect alarm information and configuration information, and then contact technical support personnel.
  3. End.
Translation
Download
Updated: 2019-03-06

Document ID: EDOC1100041475

Views: 74518

Downloads: 47

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next