LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.65 hwMplsLspTotalCountExceed

Description

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.

Attribute

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

Parameters

Name	Meaning
oid	Indicates the MIB object ID of the alarm.
hwMplsLspProtocol	LSP protocol type
hwMplsLspTotalCount	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.

Procedure

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.
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.
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.66 hwMplsLspTotalCountExceedClear