Conditions that trigger TE resource threshold-reaching alarms can be configured. If the number of Auto bypass tunnel interfaces, or the number of Auto Primary Tunnels reaches the upper alarm threshold, the device can report an alarm, which facilitates operation and maintenance.
The system view is displayed.
The MPLS view is displayed.
Run mpls autobypass-tunnel-number threshold-alarm upper-limit upper-limit-value lower-limit lower-limit-value
The conditions that trigger the threshold-reaching alarm and its clear alarm for Auto bypass tunnel interfaces are configured.
Run mpls autoprimary-tunnel-number threshold-alarm upper-limit upper-limit-value lower-limit lower-limit-value
The conditions that trigger the threshold-reaching alarm and its clear alarm for Auto Primary Tunnels are configured.
Note the following issues when configuring trigger conditions:
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 { hwmplsresourcethresholdexceed | hwmplsresourcethresholdexceedclear } command is run to enable the device to generate an MPLS resource insufficiency alarm and its clear alarm.
After the snmp-agent trap enable feature-name mpls_lspm trap-name { hwmplsresourcetotalcountexceed | hwmplsresourcetotalcountexceedclear } command is run to enable the device to generate limit-reaching alarms and their clear alarms, the following situations occur:
If the number of used TE resources reaches the maximum number of TE resources supported by a device, a limit-reaching alarm is generated.
If the number of used TE resources falls below 95% of the maximum number of TE resources supported by a device, a clear alarm is generated.
The configuration is committed.