Configuring Qos Fault And Clear Traps - Avaya G450 Manual

Note:
When using the snmp-server host command, you can specify only to send
Note:
certain types of traps to the specified trap manager. For example, snmp-server
host 1.1.1.1 traps v1 public rtp-stat-qos rtp-stats-faults
configures only QoS traps and QoS fault and clear traps to be sent to host
1.1.1.1.
To check your current SNMP configurations, enter show snmp. Traps are automatically
sent to the active MGC by the dynamic trap manager feature. To configure the dynamic
trap manager, use the command snmp-server dynamic-trap-manager. For more
information about the dynamic trap manager, see
page 338.
4. Enter rtp-stat qos-trap to enable the traps, if not already enabled. For example:
G450-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.
Use the rtp-stat fault command. For example:
●
G450-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 is sent if and when one active RTP
session has QoS problems. A QoS clear trap is then sent if and when the number of active
RTP sessions with QoS problems reaches 0.
rtp-stat fault 1 0
Configuring and analyzing RTP statistics
Configuring dynamic trap manager
Issue 1 January 2008
on
383