Configuring Message Rate Limiting Constraints for Threshold Monitoring

An event can cause multiple messages of different types to be generated simultaneously.

Since it is possible that multiple entries/traps can be generated for an event, options are available to rate limit the generation of these events/traps. Without rate limiting, there is a possibility that the message handling subsystem of the device getting overwhelmed while handling these messages and causing the device to crash.

Rate limiting consists of two configurable constraints:

the number of messages (X)
the duration (Y) (in seconds)

When configured, the constraints can be summed as: Generate a maximum of X messages in Y units of time. Messages can be RASLOG or SNMP or Both and this depends on the action configured for that specific monitored parameter.

To configure the rate limiting constraints:

Navigate to the Global Configuration Mode.
```
SLX# configure terminal
SLX (config)# 
```
Set the count parameter.
```
SLX (config)# threshold-monitor hardware-resources count 10
SLX (config)# 
```
The count controls the maximum number of events to be generated in the configured time interval. A maximum number of sixty (60) events can be generated for each time interval. The default is four (4).
Set the interval parameter.
```
SLX (config)# threshold-monitor hardware-resources interval 300
SLX (config)# 
```
The interval controls the time duration in seconds. In this example, a maximum of 10 messages can be generated every 300 seconds. The range is 30-900 seconds and the default is 30 seconds.

This example shows the complete configuration for the rate limiting constraints.

SLX# configure terminal
SLX (config)# threshold-monitor hardware-resources count 10
SLX (config)# threshold-monitor hardware-resources interval 300
SLX (config)#