Setting up the Alarm Origination Manager

Last Updated : Mar 19, 2021 |

Use this section to set up the Alarm Origination Manager (AOM) on the CMS server. The aom_tool is used to configure AOM. You can use the AOM feature to enable alarming to Avaya and this capability is available only for CMS servers with a current maintenance agreement in effect. You can optionally use AOM to send SNMP alarms to customer provided Network Management Systems (NMS). You can enable SNMP alarms to a customer provided NMS even if a current Avaya maintenance agreement is not in effect.

Note:

CMS supports only SNMP v3 in this release

Important:

There are multiple phases to completing the AOM configuration. You must configure an Alarm ID, and you must configure an Alarm ID and a Customer ID if SNMP alarming to SAL is intended. To use SNMP, you must configure an SNMP user. Finally, you must configure an Alarm Destination.

Prerequisites

Before you set up AOM, perform the following tasks:

  • Obtain an Alarm ID number and Sold To Functional Location (FL) number. You can obtain an Alarm ID by registering the CMS server. You can register a CMS server using the Avaya Global Registration Tool (GRT) tool at https://support.avaya.com/grt. If you cannot register the system using the GRT tool, call 1800-242-2121, extension 15265, for assistance. If the system does not have an Avaya maintenance agreement in effect and you are going to configure optional SNMP alarming in a customer NMS, accept the default values that are pre-populated.

    Note:

    During AOM configuration, use the Alarm ID referred to here as the Alarm ID and use the Sold To Functional Location (FL) number as the Customer ID.

  • Log on as root.

    Important:

    You cannot directly log on as root from a remote connection. You must log on using an administered CMS user ID, then use su - root to log on with root privileges.