LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.69 hwMplsDynamicLabelTotalCountExceed

Description

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.

Attribute

Alarm ID	Alarm Severity	Alarm Type
1.3.6.1.4.1.2011.5.25.121.2.1.69	Major	qualityOfServiceAlarm(3)

Parameters

Name	Meaning
oid	Indicates the MIB object ID of the alarm.
hwMplsDynamicLabelTotalCount	Total number of dynamic labels
hwMplsDynamicLabelCurrentCount	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.

Procedure

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.3.6.1.4.1.2011.5.25.121.2.1.70 hwMplsDynamicLabelTotalCountExceedClear is generated.
- If this clear alarm is generated, go to step 3.
- If this clear alarm is not generated, go to step 2.
Collect log messages and Collect alarm information and configuration information, and then contact technical support personnel.
End.

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.70 hwMplsDynamicLabelTotalCountExceedClear