4.1 Alarms

Use this Knowledge Script to monitor CS1000 alarms. Call Servers, Signaling Servers, Media Gateways, MGCs, ECMs, NRSs, VGMCs and SIPL send alarms to the proxy agent computer using SNMP traps.

When setting parameters for this script, you will be asked to provide a list of alarm identifiers (system messages) to include or exclude from monitoring. System messages are discussed in the CS1000 Software Input/Output System Message publication (Avaya publication number 553-3001-411). Their format consists of a multi-letter code followed by a multi-digit alarm number, such as AUD000 or SRPT194.

Running this Knowledge Script job consumes approximately 20 MB of memory, per instance, on the proxy agent computer.

This script can launch an Action Knowledge Script that triggers NetIQ Vivinet Diagnostics to diagnose the problem when QoS alarms are raised. For more information, see the Help for the Action_DiagnoseNortelIPT Knowledge Script.

4.1.1 Prerequisites

  • Install the Windows SNMP service. If you installed the service before you installed the AppManager for CS1000 module, then you do not need to do anything else. If you installed the service after you installed the module, then stop and restart the proxy agent computer before using this script.

  • Configure CS1000 devices to send SNMP traps to the proxy agent computer. For more information, see Section 4.1.6, Identifying the SNMP Trap Receiver.

  • The AppManager for Avaya CS1000 module is incompatible with the Avaya Telephony Manager application, which competes with the module for UDP port 162. AppManager will not receive SNMP traps if Telephony Manager is installed.

  • The AppManager for Avaya CS1000 module is incompatible with NetIQ SNMP Trap Receiver (Trap Receiver), which competes with the module for UDP port 162. AppManager will not receive SNMP traps if Trap Receiver is installed.

4.1.2 Resource Objects

NortelCS Call Server

NortelCS Signaling Server

NortelCS VGMC

NortelCS Media Gateway Controller

NortelCS MC32S

NortelCS Network Routing Server

NortelCS Enterprise Common Manager

NortelCS SIP Line

NOTE:In most circumstances, the Alarms Knowledge Script raises events for alarms (traps) received from the CS1000 component on which you run the job. The component ID property of each trap identifies the source of the trap. For example, a component ID of “CS” identifies the Call Server. The component ID also determines which resource object an event is raised against.

For environments in which a co-resident server hosts multiple applications, the component ID may not correctly identify the source of a trap. When the component ID incorrectly identifies the source of a trap, events are raised against the incorrect resource object.

For example, if a co-resident server hosts the Call Server, the Signaling Server, and the Network Routing Server (NRS), the component ID may indicate a trap was received from the NRS. In addition, the event will be raised against the NRS object. However, experience may tell you that the trap actually came from the Signaling Server.

To ensure events are raised for all traps received from all components on a co-resident server, run the Alarms Knowledge Script on the co-resident server parent object so that all component child objects are monitored. If you run the Alarms job on only the Signaling Server, for example, AppManager will not raise an event for the Signaling Server trap that is incorrectly identified as an NRS trap.

4.1.3 Default Schedule

By default, this script runs on an asynchronous schedule.

4.1.4 Setting Parameter Values

Set the following parameters as needed:

Parameter

How to Set It

Notes for the “critical to monitor” and QoS alarm categories:

  • If you “Include” selected alarm identifiers in a category, AppManager raises events for those alarm identifiers plus the identifiers that are, by default, included in the category.

  • If you “Include only” selected alarm identifiers in a category, AppManager raises events only for those identifiers. AppManager will not raise events for the other identifiers included in the category.

  • If you “Exclude” selected alarm identifiers from a category, AppManager raises events for all alarm identifiers included in the category except those you specifically excluded.

  • If you accept the default settings in the Alarm identifiers parameters, “Exclude” and blank, AppManager raises events for all identifiers in the category, because you excluded nothing from the category.

Monitor “critical to monitor” alarms?

Select Yes to monitor alarms in the “critical to monitor” category. The default is Yes.

Include or exclude alarms?

Select whether you want to Include, Include only, or Exclude the alarm identifiers you specify in the following parameter.

  • Select Include to add the listed identifiers to the “critical to monitor” category.

  • Select Include only to include only the listed identifiers in the “critical to monitor” category.

  • Select Exclude to exclude the listed identifiers from the “critical to monitor” category. This is the default option.

By default, the “critical to monitor” category includes all alarms designated as “critical to monitor” in the CS1000 Software Input/Output System Messages publication (Avaya publication number 553-3001-411).

Alarm identifiers

Provide a comma-separated list of the alarm identifiers you want to include in or exclude from the “critical to monitor” category. The default is an empty list.

Monitor QoS alarms?

Select Yes to monitor the proxy agent computer for alarms in the QoS category. The default is Yes.

Include or exclude alarms?

Select whether you want to Include, Include only, or Exclude the alarm identifiers you specify in the Alarm identifiers parameter.

  • Select Include to add the listed identifiers to the QoS category.

  • Select Include only to include only the listed identifiers in the QoS category.

  • Select Exclude to exclude the listed identifiers from the QoS category. This is the default option.

By default, the QoS category includes the following alarms for CS1000 versions 4.0 and later:

ITG1028, ITG2028, ITG3028, ITG4028, ITG4043, ITG4044, QOS0012, QOS0013, QOS0014, QOS0015, QOS0017, QOS0018, QOS0019, QOS0020, QOS0022, QOS0024, QOS0026, QOS0028, QOS0030, QOS0032, QOS0034, QOS0036, QOS0038, QOS0039, QOS0040, QOS0041, QOS0042, QOS0043

Alarm identifiers

Provide a comma-separated list of the alarm identifiers you want to include in or exclude from the “QoS” category. The default is an empty list.

Phone filter

Include or exclude phones?

You can use IP addresses to further filter the results of the QoS alarm monitoring. Select whether you want to Include only or Exclude the IP addresses you specify in Phone IP addresses or Phone IP address ranges. AppManager will monitor — or exclude — QoS alarms related to the calling and called phones that belong to the IP addresses.

  • Select Include only to monitor QoS alarms only the listed phone IP addresses.

  • Select Exclude to exclude listed phone IP addresses from QoS alarm monitoring. This is the default option

Phone IP addresses

Provide a comma-separated list of the IP addresses of the phones you want to monitor for QoS alarms. For example:

10.14.2.21,10.14.3.100,10.14.1.50

Phone IP address ranges

Type a comma-separated list of IP address ranges for the phones you want to monitor for QoS alarms. For example:

10.14.2.21-10.14.3.100,10.14.1.10-10.14.1.50

Launch Diagnostics when the following alarm is received ...

Warning packet loss QOS0022?

Select Yes to launch Vivinet Diagnostics to diagnose the problem when the QOS0022 alarm is raised. The default is unselected.

Warning latency QOS0024?

Select Yes to launch Vivinet Diagnostics to diagnose the problem when the QOS0024 alarm is raised. The default is unselected.

Warning jitter QOS0026?

Select Yes to launch Vivinet Diagnostics to diagnose the problem when the QOS0026 alarm is raised. The default is unselected.

Warning R-factor QOS0028?

Select Yes to launch Vivinet Diagnostics to diagnose the problem when the QOS0028 alarm is raised. The default is Yes.

Unacceptable packet loss QOS0030?

Select Yes to launch Vivinet Diagnostics to diagnose the problem when the QOS0030 alarm is raised. The default is unselected.

Unacceptable latency QOS0032?

Select Yes to launch Vivinet Diagnostics to diagnose the problem when the QOS0032 alarm is raised. The default is unselected.

Unacceptable jitter QOS0034?

Select Yes to launch Vivinet Diagnostics to diagnose the problem when the QOS0034 alarm is raised. The default is unselected.

Note for the following alarm categories: AppManager raises an event only for those alarm identifiers you specifically include, or it raises an event for all alarm identifiers except those you specifically exclude. If you accept the default of an empty list in the Alarm identifiers parameters, AppManager raises events for all alarm identifiers.

Monitor critical alarms?

Select Yes to monitor alarms in the critical category. The default is unselected.

Include or exclude alarms?

Select whether you want to Include only or Exclude the alarm identifiers you specify in the following parameter.

  • Select Include only to include only the listed identifiers in the critical category.

  • Select Exclude to exclude the listed identifiers from the critical category. This is the default value.

By default, the critical category includes all alarms with critical severity in the SNMP trap.

Alarm identifiers

Provide a comma-separated list of the alarm identifiers you want to include in or exclude from the critical category. The default is an empty list.

Monitor major alarms?

Select Yes to monitor alarms in the major category. The default is unselected.

Include or exclude alarms?

Select whether you want to Include only or Exclude the alarm identifiers you specify in the following parameter.

  • Select Include only to include only the listed identifiers in the major category.

  • Select Exclude to exclude the listed identifiers from the major category. This is the default option.

By default, the major category includes all alarms with major severity in the SNMP trap.

Alarm identifiers

Provide a comma-separated list of the alarm identifiers you want to include in or exclude from the major category. The default is an empty list.

Monitor minor alarms?

Select Yes to monitor alarms in the minor category. The default is unselected.

Include or exclude alarms?

Select whether you want to Include only or Exclude the alarm identifiers you specify in the following parameter.

  • Select Include only to include only the listed identifiers in the minor category.

  • Select Exclude to exclude the listed identifiers from the minor category. This is the default option.

By default, the minor category includes all alarms with minor severity in the SNMP trap.

Alarm identifiers

Provide a comma-separated list of the alarm identifiers you want to include in or exclude from the minor category. The default is an empty list.

Monitor warning alarms?

Select Yes to monitor alarms in the warning category. The default is unselected.

Include or exclude alarms?

Select whether you want to Include only or Exclude the alarm identifiers you specify in the following parameter.

  • Select Include only to include only the listed identifiers in the warning category.

  • Select Exclude to exclude the listed identifiers from the warning category. This is the default option.

By default, the warning category includes all alarms with warning severity in the SNMP trap.

Alarm identifiers

Provide a comma-separated list of the alarm identifiers you want to include in or exclude from the warning category. The default is an empty list.

Monitor info alarms?

Select Yes to monitor alarms in the informational category. The default is unselected.

Include or exclude alarms?

Select whether you want to Include only or Exclude the alarm identifiers you specify in the following parameter.

  • Select Include only to include only the listed identifiers in the informational category.

  • Select Exclude to exclude the listed identifiers from the informational category. This is the default option.

By default, the informational category includes all alarms with informational severity in the SNMP trap.

Alarm identifiers

Provide a comma-separated list of the alarm identifiers you want to include in or exclude from the informational category. The default is an empty list.

Monitor cleared alarms?

Select Yes to monitor alarms in the cleared category. The default is unselected.

Include or exclude alarms?

Select whether you want to Include only or Exclude the alarm identifiers you specify in the following parameter.

  • Select Include only to include only the listed identifiers in the cleared category.

  • Select Exclude to exclude the listed identifiers from the cleared category. This is the default option.

By default, the cleared category includes all alarms with cleared severity in the SNMP trap.

Alarm identifiers

Provide a comma-separated list of the alarm identifiers you want to include in or exclude from the cleared category. The default is an empty list.

Monitor indeterminate alarms?

Select Yes to monitor alarms in the indeterminate category. The default is unselected.

Include or exclude alarms?

Select whether you want to Include only or Exclude the alarm identifiers you specify in the following parameter.

  • Select Include only to include only the listed identifiers in the indeterminate category.

  • Select Exclude to exclude the listed identifiers from the indeterminate category.

By default, the indeterminate category includes all alarms with indeterminate severity in the SNMP trap.

Alarm identifiers

Provide a comma-separated list of the alarm identifiers you want to include in or exclude from the indeterminate category. The default is an empty list.

Event Severities

Severity - Critical alarms

Set the severity level, between 1 and 40, to indicate the importance of an event in which a critical alarm is detected. The default is 10.

Severity - Major alarms

Set the severity level, between 1 and 40, to indicate the importance of an event in which a major alarm is detected. The default is 15.

Severity - Minor alarms

Set the severity level, between 1 and 40, to indicate the importance of an event in which a minor alarm is detected. The default is 20.

Severity - Warning alarms

Set the severity level, between 1 and 40, to indicate the importance of an event in which a warning alarm is detected. The default is 25.

Severity - Info alarms

Set the severity level, between 1 and 40, to indicate the importance of an event in which an informational alarm is detected. The default is 30.

Severity - Cleared alarms

Set the severity level, between 1 and 40, to indicate the importance of an event in which a cleared alarm is detected. The default is 30.

Severity - Indeterminate alarms

Set the severity level, between 1 and 40, to indicate the importance of an event in which an indeterminate alarm is detected. The default is 30.

4.1.5 Understanding an Alarms Event Message

The message on the Message tab of an event raised by the Alarms script provides not only a brief description of the event, but also recommends any corrective action you can take. AppManager retrieves the recommended actions from a database provided by Avaya.

In the following example, the Alarms script raised an event for the ITS2008 alarm on a Signaling Server:

NTP index: ITS2008
Nortel CS device:SIG_SERV
Alarm: Terminal connection status: 10.40.101.112 lost

The Message tab for this event provided the following “Help” and “Recommended Action” for the alarm:

Help for ITS2008:
Terminal connection status: <terminalIP><ok/lost>.

Recommended action for ITS2008:
1. Alarm may indicate random occurrence that is not service impacting; note
occurrence time and date for further follow-up. If any service-impacting problems
occur at the same time, further analysis is required immediately.
2. If alarm persists, log into device and capture maintenance report log (if possible) and send
the text to Nortel support staff via email. Follow any steps described above for
the specific alarm.

Occasionally, more than one Help is available for an alarm. In this case, all Helps are shown first:

NTP index: XMI0002
Extra diagnostic information: 18 MGATE
Help for XMI0002 XFIL 1:
Main fiber interface (MFI) local is operational.

Help for XMI0002 XFIR 2:
Expansion fiber interface (EFI) remote is operational in first expansion cabinet.

Help for XMI0002 XFIR 3:
Expansion fiber interface (EFI) remote is operational in second expansion cabinet.

Help for XMI0002 I s c:
Card polling re-established.

Any Recommended Actions will follow the Helps. It is possible, though, for no Recommended Actions to be available.

The Event tab in an Alarms event message provides a one-line Message that briefly describes the problem detailed on the Message tab. For CS1000 version 5.x and 6.0 alarms, the message can look something like this example:

Critical alarm IOD0040: Raleigh CS1K:RTP:CS [10.42.1.11]

The format of this message is defined as follows:

<severity>alarm<index>: <navigation system name>:<navigation site 
name>:<component> [<component IP address>]

The navigation system name and navigation site name are taken from the SNMP Configuration information you set in Element Manager.

4.1.6 Identifying the SNMP Trap Receiver

Configure CS1000 to send SNMP traps to the CS1000 proxy agent computer. The configuration procedures are different for CS1000 versions 4.0 and later.

Configuring the Trap Receiver in Version 6.0 and Later

Use Unified Communications Manager or Element Manager to configure the trap receiver. To use Element Manager to configure the trap receiver, see Configuring the Trap Receiver in Version 5.x.

To configure the trap receiver using Unified Communications Manager:

  1. Navigate to Network, click CS1000 Services, and then click SNMP Profiles.

  2. Click SNMP Profile.

  3. Select the SNMP profile you want to use. Or, to create a new profile, click Add and specify a new name for an Alarm type of profile.

  4. In the Trap Destination IP address field, provide the IP address of the proxy agent computer to which the Avaya devices should sent SNMP traps.

  5. Click Save.

  6. Click SNMP Distribution, and then select all Avaya devices that should send SNMP traps to the proxy agent computer.

  7. Click Assign.

  8. In the Alarm Profile field, select the SNMP profile name from Step 3.

Configuring the Trap Receiver in Version 5.x

Use Element Manager to configure the trap receiver.

To configure the trap receiver:

  1. Navigate to System, click Alarms, and then click SNMP.

  2. In the Trap Destination IP address field, provide the IP address of the proxy agent computer to which you want to send Call Server traps.

Configuring the Trap Receiver in Version 4.50

Use Element Manager to configure the trap receiver.

To configure the trap receiver:

  1. Navigate to System and click SNMP.

    • In the SNMP trap destination address field, type the IP address of the proxy agent computer to which you want to send Call Server traps.

  2. Navigate to IP Telephony > Nodes > Configuration.

    • Select the node ID for which you want to enable SNMP traps.

    • Click Edit and then select SNMP on the Edit page.

    • Click Add to create a new IP address field, and then enter the IP address of the proxy agent computer to which you want to send SNMP traps. Repeat for each IP address you want to add.

    • Select Enable SNMP traps.

    • Click Save and Transfer.

  3. Repeat the items in Step 2 for each additional node ID you want to configure.

Configuring the Trap Receiver in Version 4.0

Use Element Manager to configure the trap receiver.

To configure the trap receiver:

  1. Navigate to Configuration, click IP Telephony, and then click SNMP Configuration.

    • In the SNMP trap destination address field, type the IP address of the proxy agent computer to which you want to send Call Server traps.

  2. Navigate to Configuration, click IP Telephony, and then click Node Summary.

    • Select the node ID for which you want to enable SNMP traps.

    • Click Edit and then click SNMP.

    • Click Add to create new IP address and Subnet mask fields, and then type the IP address and subnet mask of the proxy agent computer to which you want to send SNMP traps. Repeat for each IP address and subnet mask you want to add.

    • Select Enable SNMP traps.

    • Click Save and Transfer.

  3. Repeat the items in Step 2 for each additional node ID you want to configure.