Configuring Qos Fault And Clear Traps; Configuring The Trap Rate Limiter - Avaya G250 Administration

Configuring QoS fault and clear traps

You can configure the RTP statistics application to send QoS fault and clear traps. A QoS fault
trap is sent when a specified number of active RTP sessions have QoS indicators over the
configured thresholds. A QoS clear trap is sent after a QoS fault trap when the number of active
RTP sessions with QoS indicators over the configured thresholds reduces to a specified
number. Since some RTP sessions can be very long, and QoS traps are sent only after the
termination of the stream, QoS fault and clear traps are important for providing timely
information about QoS problems.
Note:
QoS fault traps appear in the Network Management Console Event Log Browser,
Note:
indicating to the user that there are QoS problems in a specific network device.
See the Avaya Network Management Console User Guide, 14-300169.
To enable and configure QoS fault and clear traps:
1. Use the rtp-stat fault command. For example:
G350-001(super)#
The fault trap boundary was set to 1 (default: 3)
The clear trap boundary was set to 0
With this example configuration, a QoS fault trap would be sent if and when one active RTP
session has QoS problems. A QoS clear trap would then be sent if and when the number of
active RTP sessions with QoS problems reduces to 0.

Configuring the trap rate limiter

The application features a trap rate limiter. The trap rate limiter limits the rate at which QoS
traps are sent. The rate limiter protects against overloading the trap manager with bursts of
traps when a single event causes multiple RTP sessions to terminate simultaneously.
The trap rate limiter uses a token bucket scheme, in which traps are sent only if there are
tokens in a virtual bucket. Tokens are added to the bucket every 'token interval,' which sets the
maximum long term trap rate. Each time a trap is sent, the number of tokens in the bucket
decrements. The 'bucket size' is the maximum number of tokens that the bucket can hold. The
bucket size limits the trap burst size.
To configure the trap rate limiter:
1. Use the rtp-stat qos-trap-rate-limit command. For example:
G350-001# rtp-stat qos-trap-rate-limit 2000 10
In this example configuration, the token-interval is 2000 and the bucket-size is 10. This
means that a token is added to the bucket every 2000 hundredths of a second (20 seconds)
and the bucket is limited to a maximum size of 10 tokens.
rtp-stat fault 1 0
Configuring and analyzing RTP statistics
Issue 1.1 June 2005 253