ContentsPrint

SNMP Traps

Navigation: System Settings > System-SNMP > Add/Edit SNMP Trap

Click Add SNMP Trap to open the Create SNMP Trap window. Note that the SNMP Enabled field on the SNMP Settings page must be set to Yes to enable the Add SNMP Trap action.

This form is used to configure what can cause alarms to be sent using the different alarm methods.

These settings are not mergeable. Changes to these settings will require a reboot of the system.

Field Description
New Alarm This area is used to show and edit the alarm.
Destination

To use SNMP or Email the appropriate settings must be configured on the Configuration sub-tab. Note that the Destination type is grayed out if the maximum number of configurable alarms destinations of that type has been reached. Up to 2 alarm destinations can be configured for SNMP, 2 for Syslog and 3 for SMTP email. For Server Edition, 5 SNMP alarms can be configured.

Trap If selected, the details required in addition to the selected Events are:
  • Server Address: Default = Blank. The IP address or fully qualified domain name (FQDN) of the SNMP server to which trap information is sent.

  • Port: Default = 162. Range = 0 to 65535. The SNMP transmit port.

  • Community: Default = Blank The SNMP community for the transmitted traps. Must be matched by the receiving SNMP server.

  • Format: Default = IP Office.

Syslog If selected, the details required in addition to the selected Events are:
  • IP Address: Default = Blank. The IP address of the Syslog server to which trap information is sent.

  • Port: Default = 516. Range = 0 to 65535. The Syslog destination port.

  • Protocol: Default = UDP. Select UDP or TCP.

  • Format: Default = IP Office.

Email If selected, the details required in addition to the selected Events are:

Email: The destination email address.

 
Minimum Security Level Default = Warnings.

The options are:

  • Warnings: All events, from Warnings to Critical, are sent.

  • Minor: Minor, major, and critical events are sent. Warnings are not sent.

  • Major: Major and critical events are sent. Warnings and minor events will not be sent.

  • Critical: Only critical events are sent.

Events Default = None

Sets which types of system events should be collected and sent. The table below lists the alarms associated with each type of event. Text in italics in the messages is replaced with the appropriate data. Items in [] brackets are included in the message if appropriate. The subject line of SMTP email alarms takes the form "System name: IP address - System Alarm".

Alarm Types

Note the following.

Type Events Event State Message
Entity Application Voicemail operation The Voicemail server is now operational.
Voicemail Failure The Voicemail server is down.
Voicemail Event - storage OK The Voicemail server storage is OK.
Voicemail Event - storage nearly full The Voicemail server storage is nearly full.
Voicemail Event - storage full The Voicemail server storage is full.
Service All licenses in use The following licenses are all in use. License Type: <name>.
All resources in use The following system resources are all in use: <resource type> will be provided.
Authentication failure Avaya Contact Center Select data synchonization failed: authentication failure.
Clock source changed 8kHz clock source changed. Details will be provided.
CPU warning/critical
  • Warning alarm: CPU utilization near capacity.

  • Critical alarm: CPU exhausted.

Feature license missing Attempt to use a feature for which no license is installed. License Type: <name>.
Hold music file failure Failed to load Hold Music source file.
Log stamped Log Stamp #nnn created in Monitor logs.
Logon failed Logon failure reason will be provided.
Memory use warning/critical
  • Warning alarm: Memory utilization near capacity.

  • Critical alarm: Memory exhausted.

Network interconnect failure Details of the network interconnection failure will be

provided.

No free channels available No free channels were available. Outgoing group ID: <number>.
OEM card slot error System running secondary software or error description with OEM card will be provided.
SIP message too large SIP message Rx error - too large - ignored.
SIP Registration Expiry
  • Avaya IP Office Contact Contact Center SIP registration expired

  • Avaya Contact Center Select SIP registration expired.

  Sync Request Timeout Avaya Contact Center Select data synchonization failed: no response from CCMA server
Memory Card Change The PC card in name has changed.
Expansion Module Operational Expansion module name link is up.
Failure Expansion module name link is down.
Error Expansion module name link has a link error.
Change Expansion module name link has changed.
Trunk Operational Trunk number (name) [on expansion module number] is now operational.
Failure Trunk number (name) [on expansion module number] is down.
Trunk Trunk seize failure Seize failure: Channel [number] or Port [number].
Incoming call outgoing trunk failure Incoming call outgoing trunk: Channel [number] or Port [number].
CLI not delivered CLI not delivered: Channel [number] or Port [number].
DDI incomplete DDI incomplete. Expected Number of digits: <number>.
LOS LOS
OOS OOS
Red Alarm Red Alarm
Blue Alarm Blue Alarm
Yellow Alarm Yellow Alarm
IP connection failure IP connection failure. IP Trunk Line Number: <number> or Remote end IP address: <IP address>.
Small Community Network invalid connection Small Community Network invalid connection. IP trunk line number: <number> or remote end IP address: <IP address>.
Link Device changed Device changed. Home Extension Number: <number>.
LDAP server communication failure LDAP server communication failure
Resource down Link/resource down. Module type, number and name

will be provided.

SMTP server communication failure SMTP server communication failure
Voicemail Pro connection failure Voicemail Pro connection failure
VCM Operational VCM module name is now operational.
Failure VCM module name has failed.
Memory Card Invalid Card
Free Capacity
Generic Generic Non-primary location boot alarm System running backup software.
Invalid SD Card Incompatible or Invalid (System or Optional) SD Card fitted.
Network link failure Network Interface name (ip address) has been disconnected.
Network link operational Network Interface name (ip address) has been connected.
System warm start System has been restarted (warm start).
System cold start System has restarted from power fail (cold start).
SNMP Invalid community Invalid community specified in SNMP request.
License License Server Server operational The license server is now operational.
Server failure The license server is no longer operational.
License Key Failure License Key Failure
Loopback Loopback Near end line loopback Trunk number (name) [on expansion module number] is in near end loopback.
Near end payload loopback Trunk number (name) [on expansion module number] is in near end loopback with payload.
Loopback off Trunk number (name) [on expansion module number] has no loopback.
Phone Change Phone Change Phone has been unplugged The phone with id n has been removed from extension extension (unit, port number).
Phone has been plugged in The phone with type type (id number) has been plugged in for extension extension (unit, port number).
Quality of Service QoS Monitoring If Enable RTCP Monitor on Port 5005 is selected, any monitored calls that exceeds the set QoS Parameters will cause an alarm.
Syslog Basic Audit Events as written to the system Audit Trail. Available on Syslog output only.
System Configuration CCR group agent not targeted CCR Group agent not targeted as it is not an CCR Agent. Group : <name> Agents: <name1, ..., name n>.
Small Community Network dial plan conflict Small Community Network dial plan conflict
No incoming call route for call The following line had no Incoming Call Route for a call. Line: <number> or Line Group ID: <number>.
Installed hardware failure Installed hardware failure details will be provided.
System Shutdown
Running Backup
Emergency Calls Emergency call successful Successful Emergency Call | Emergency call! Location:location Dialled:dialled number Called:number sent on the line CallerID:ID Usr:user Extn:extension
Emergency call failure Failed Emergency Call | Emergency call! Location:location Dialled:dialled number FailCause:cause Usr:user Extn:extension