This section describes how to set the dynamic label thresholds for triggering an alarm. If the number of dynamic labels that the system uses reaches a specific threshold, the system generates an alarm, which facilitates operation and maintenance.
If dynamic labels run out but the system receives new dynamic label requests, the system fails to satisfy the requests because the dynamic labels are insufficient. The module that fails to be assigned labels works abnormally. The modules that apply for labels include MPLS TE, MPLS LDP, BGP, L3VPN and L2VPN.
To help facilitate operation and maintenance, you can set dynamic label thresholds for triggering alarms to alert users.
The system view is displayed.
The MPLS view is displayed.
The thresholds for triggering dynamic label alarms are set.
You can set the following parameters:
Each command only configures the trigger conditions for an alarm and its clear alarm. Although trigger conditions are met, the alarm and its clear alarm can be generated only after the snmp-agent trap enable feature-name mpls_lspm trap-name { hwMplsDynamicLabelThresholdExceed | hwMplsDynamicLabelThresholdExceedClear } command is run to enable the device to generate a dynamic label insufficiency alarm and its clear alarm.
After the snmp-agent trap enable feature-name mpls_lspm trap-name { hwMplsDynamicLabelTotalCountExceed | hwMplsDynamicLabelTotalCountExceedClear } command is run to enable the device to generate limit-reaching alarms and their clear alarms, the following situations occur:
If the number of dynamic labels reaches the maximum number of dynamic labels supported by a device, a limit-reaching alarm is generated.
If the number of dynamic labels falls below 95% of the maximum number of dynamic labels supported by the device, a clear alarm is generated.
The configuration is committed.