Qos Alarms; Alarm Management; Product Connect Strategies To A Services Organization - Avaya G350 Maintenance Manual

Alarming

QOS alarms

QOS alarms
An RTCP monitor using the local SNMP agent generates traps to a pre-administered trap collector. The
following alarms are generated:
•
The voip-callqos alarm is generated if a single session exceeds configured QOS levels. It can
generate a warning or an SNMP trap. Warnings are used for less severe problems. They can be
accumulated internally within Avaya VoIP Monitoring Manager for use by the alarms defined
below.
•
The voip-systemqos alarm is generated if the number of voip-callqos warnings from all terminals
exceeds a configured count over a given period (e.g. 100 alarms over 24 hours). The alarm causes
a SNMP trap to be sent.
•
The voip-terminalqos alarm is like the voip-systemqos alarm except it applies to a single
terminal. If any one terminal generates a number of voip-callqos warnings that exceed a threshold
then the alarm is generated.

Alarm management

This section describes methods to determine the source of alarms that are generated when an error occurs.
The alarm log is viewable and follows that defined in Maintenance for the Avaya S8700 Media Server
with the SCC1 or MCC1 Media Gateway, 555-233-143. Technicians can view alarms via the Web
Interface, CLI, and SAT command-line interface.
SNMP management is a function of the Avaya MultiService Network Manager. For additional
information, including information on event logs and trap logs, please refer to the Avaya P333T User's
Guide.
The Dynamic Trap Manager feature of the G350 insures that SNMP traps and alarms are always sent to
the currently active Media Gateway Controller. By default, the Dynamic Trap Manager sends all SNMP
messages to the currently active MGC. You can configure the Dynamic Trap Manager to manage only a
subset of SNMP messages using the
Alarm management for the Avaya G350 Media Gateway follows the S8700 Media Server Alarming
Architecture Design; see Maintenance for the Avaya S8700 Media Server with the SCC1 or MCC1 Media
Gateway, 555-233-143. For convenience, the following sections include some brief information.
Product connect strategies to a services
organization
A services organization, such as INADS, receives alarms from the S8300 Media Server running on the
Avaya G350 Media Gateway and connects to the product for troubleshooting. There are currently two
product-connect strategies: dialup modem access and Virtual Private Network (VPN) access over the
Internet.
To connect using dialup modem access:
1
Place a modem connected to a telephone line in front of the Media Server connecting to the USB
port on the faceplate.
288
snmp-server dynamic-trap-manager
Maintenance of the Avaya G350 Media Gateway
CLI command.
June 2004