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

LSPM_1. hwMplsDynamicLabelTotalCountExceed


LSPM/2/LABEL_TOTAL_EXCEED:OID [oid] The dynamic label usage exceeds the threshold. BGP, LDP, RSVP TE, or MPLS VPN will fail to be created.( hwMplsDynamicLabelTotalCount=[INTEGER], hwMplsDynamicLabelCurrentCount=[INTEGER])

Dynamic label usage reached 100%, and LSPs could not be created for BGP/LDP/RSVP-TE/MPLS VPNs.


Alarm ID Alarm Severity Alarm Type




Name Meaning


Indicates the MIB object ID of the alarm.


Total number of dynamic labels


Number of dynamic labels used

Impact on the System

All dynamic labels are used, and no subsequent LSPs can be established.

Possible Causes

A great number of LSPs were established, and all dynamic labels were used.


  1. Run the display mpls lsp statistics command to view statistics about LDP LSPs, RSVP-TE CR-LSPs, and BGP LSPs. Re-plan the services and delete unwanted LSPs that use dynamic labels.

    • For LDP LSPs, run the lsp-trigger command to modify a policy used by LDP to establish LSPs to reduce unwanted LSPs.
    • For RSVP LSPs, run the undo interface tunnel command to delete unwanted RSVP-TE tunnels.
    • For static LSPs, 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 LSPM_1. hwMplsDynamicLabelTotalCountExceedClear is generated.

    • If this clear alarm is generated, go to step 3.
    • If this clear alarm is not generated, go to step 2.
  2. Collect log messages and Collect alarm information and configuration information, and then contact technical support personnel.
  3. End.
Updated: 2019-03-06

Document ID: EDOC1100041475

Views: 107747

Downloads: 68

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next