The routing-table limit threshold-alarm command configures alarm and clear alarm thresholds for the number of BGP routes.
The undo routing-table limit threshold-alarm command restores the default configurations.
By default, the alarm threshold is 80%, and the clear alarm threshold is 70%.
routing-table limit threshold-alarm upper-limit upper-limit-value lower-limit lower-limit-value
undo routing-table limit threshold-alarm [ upper-limit upper-limit-value lower-limit lower-limit-value ]
| Parameter | Description | Value |
|---|---|---|
| upper-limit upper-limit-value | Specifies an alarm threshold. | The value is an integer ranging from 1 to 100, in percentage. The default value is 80. |
| lower-limit lower-limit-value | Specifies a clear alarm threshold. | The value is an integer ranging from 1 to 100, in percentage. The default value of is 70. lower-limit-value must be less than upper-limit-value; otherwise, alarms are generated and cleared repeatedly if route flapping occurs. |
Usage Scenario
The number of BGP routes that can be added to a routing table is limited. If the number exceeds a limit, new routes cannot be added to the routing table, which may interrupt services. To address this problem, run the routing-table limit threshold-alarm command to configure alarm and clear alarm thresholds for the number of BGP routes. With the alarm and clear alarm thresholds, alarms are generated and cleared as expected. The alarms prompt you to check whether an exception occurs and to take preventive measures.
Configuration Impact
If the routing-table limit threshold-alarm command is run more than once, the latest configuration overrides the previous one.
Precautions
In addition to the routing-table limit threshold-alarm command, the snmp-agent trap enable feature-name bgp trap-name { hwBgpRouteThresholdExceed | hwBgpRouteThresholdClear } command must be run to enable the alarm and clear alarm functions; otherwise, alarms cannot be generated and cleared as expected.