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


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


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. hwMplsLspTotalCountExceed

LSPM_1. hwMplsLspTotalCountExceed


LSPM/2/MPLSLSPTOTALCOUNTEXCEED:OID [oid] The lsp count reaches the upper limit.(hwMplsLspProtocol=[integer], hwMplsLspTotalCount=[integer])

The total number of LSPs exceeded the upper limit.


Alarm ID Alarm Severity Alarm Type




Name Meaning


Indicates the MIB object ID of the alarm.


LSP protocol type


Upper limit of supported LDP LSPs

Impact on the System

The number of hwMplsLspProtocol LSPs has reached the upper limit. If subsequent LSPs continue to be established, services of the new LSPs may be affected.

Possible Causes

The number of the current hwMplsLspProtocol LSPs reached the upper limit.


  1. Run the display mpls lsp command to check whether unwanted hwMplsLspProtocol LSPs exist on the device.
    • If no unwanted LSPs exist, go to Step 3.
    • If unwanted LSPs exist, go to Step 2.
  2. Run the lsp-trigger command to modify a policy used by LDP to establish LSPs to reduce unwanted LSPs. Alternatively, run the undo interface tunnel command to delete unwanted RSVP-TE tunnels, and run the undo static-lsp ingress, undo static-lsp transit, and undo static-lsp static-lsp egress commands to delete unwanted static LSPs. Then check whether the alarm is cleared.
    • If the alarm is cleared, go to Step 4.
    • If the alarm persists, go to Step 3.
  3. Collect alarm information and configuration information, and then contact technical support personnel..
  4. End.
Updated: 2019-03-06

Document ID: EDOC1100041475

Views: 107119

Downloads: 68

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next