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

Configuring monitoring applications
4. Use the rtp-stat qos-trap command to enable the traps, if not enabled already. For
example:
G350-001# rtp-stat qos-trap
The RTP statistics QoS trap is enabled
QoS traps are now enabled.

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.
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.
342 Administration for the Avaya G250 and Avaya G350 Media Gateways
rtp-stat fault 1 0