Avaya VoIP Monitoring Manager Reference Release 3.0 Manual de usuario Pagina 93

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 142
  • Tabla de contenidos
  • SOLUCIÓN DE PROBLEMAS
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 92
85
Generating Traps & Alarms (Server)
Generating Traps & Alarms
You can set rules to generate Traps that notify you when the VoIP network QoS parameters have
reached unacceptable levels. You define the rules in the Trap dialog, which has a tab for Call
Traps and a Tab for System Traps. You open the Trap dialog from the VoIP Monitoring Manager
Server Edit > Trap Settings.
You can set more than one rule for each type of trap, and each rule can be made up of more than
one condition. When a rule has more than one condition, they have a logical AND relationship,
i.e. they must all be satisfied before a trap is sent.
The RTCP Monitor generates a Trap to a pre-configured Trap Manager when the RTCP Monitor
experiences the conditions defined. The Trap Manager is generally configured to be the Gateway
Alarm Manager (GAM) or Network Alarm Manager (NAM) but any Trap Manager application can
be used. Traps can be set for Calls (Sessions), Systems (Networks), and Terminals (endpoint).
VoIP Monitor Manager creates alarms (traps) based on two sets of rules:
Call Alarms. If a specified condition occurs anywhere in the system, a trap is sent
immediately.
System Alarms. The specified condition must occur a specified number of times before a
trap is sent. This is based on an accumulation of warnings from the entire system.
See Also
Configure SNMP Service for Sending Traps
Recommended Alarm Settings
Recommended Trap Settings
Values that you use to trigger alarms must be fine-tuned to suit your environment. Appropriate
settings may vary greatly from one country to another.
The default settings that are in place when VoIP Monitoring Manager is installed are a useful
starting point. These settings are based on an environment with high-quality telecommunications
facilities. For example, it is reasonable to expect RTT of less than 300.
Severity Jitter Delay % loss
MAJ 60 0 0
MAJ 0 500 0
MAJ 0 0 50
WRN 45 0 0
WRN 0 0 4.0
System warning interval: 100 warnings, 24 hours
Terminal warning interval: 50 warnings, 24 hours
Vista de pagina 92
1 2 ... 88 89 90 91 92 93 94 95 96 97 98 ... 141 142

Comentarios a estos manuales

Sin comentarios