SNMP Alarming on the G700

Setting up SNMP alarm reporting involves two main tasks:

• Configure the primary server to report alarms
• Configure the G700 to Send its Traps to the Primary Server

Configure the primary server to report alarms

The primary server may be either an S8300 Media Server or an S8700 Media Server. The Media Server supports two methods for reporting alarms. Either method, both, or no alarm-reporting method may be used at a given site.

• OSS Method. The server's software applications and hardware devices under its control can generate Operations Support System (OSS) alarms. These alarms are recorded in the server logs, and may be reported to Avaya's Initialization and Administration System (INADS) or another services support agency over the server's modem interface.
  
  To activate OSS alarm notification: The server requires a USB connection to a modem that is connected to an analog line. The modem must be configured using the Web Interface, in the Set Modem Interface screen, and enabled to send and receive calls using the Enable/Disable Modem screen. Configuration of the OSS alarming method can only be done using Linux shell commands.
• SNMP Method. SNMP traps may be sent in User Datagram Protocol (UDP) to a corporate network management system (NMS) using the Configure Trap Destinations screen. The OSS and SNMP alarm-notification methods operate independently of each other. Either or both may be used. Currently, the following NMSs are supported:
• Avaya Communication Manager Fault and Performance Manager, as a standalone application, or integrated within
• Avaya MultiService Network Manager
• HP Openview

To activate SNMP alarm notification: On the server Web Interface, use the Configure Trap Destinations screen to set up SNMP destinations in the corporate NMS.

Add INADS Phone Numbers and Enable Alarms to INADS

The following procedure using the primary server's Linux shell commands administers the dial-out modem to send alarms in the OSS method. In this example, the primary server is an S8300, and the services support agency is Avaya's Initialization and Administration System (INADS).

Perform this task after all Communication Manager administration is complete.

To add INADS phone numbers and enable alarms to INADS

Begin _____________________

1. Connect your laptop to the Services port of the S8300 Media Server

Note: Do these steps only if the S8300 is the primary controller and the customer has a maintenance contract with Avaya. Use the information acquired from the ART tool (see "Run the ART Tool for the INADS IP Address" in Chapter 3 of "Installation and Upgrades for the Avaya G700 Media Gateway Controlled by an Avaya S8300 or S8700 Media Server, 555-234-100"). Also, a USB modem must have already been installed. See "Universal Serial Bus (USB) Modems" in Chapter 7 of the same source.

1. Click Start > Run to open the Run dialog box
2. Type telnet 192.11.13.6 and press Enter.
3. Log in as craft.
4. At the prompt, type almcall -f INADS phone number -s second-number and press Enter.
5. At the prompt, type almenable -d b -s y and press Enter.
6. Type almenable and press Enter to verify that the alarms are enabled.
7. Log off.

End _______________________

Configure the G700 to Send its Traps to the Primary Server

Configuring the G700 Media Gateway to send SNMP traps to the primary server can be accomplished by two commands:

• Layer 2 Switching Processor CLI command: set snmp community trap [community string]
• Media Gateway Processor (MGP) CLI command: set snmp trap <IP address> enable

Configure an SNMP community string for traps

SNMP requires community strings to be used for each SNMP "request". You can set only three community strings on the G700 -- one each for read requests, write requests, and traps. The command for traps is set snmp community trap [community string].

To configure an SNMP community string for traps

Begin _____________________

1. Open the Run dialog box.
2. Type telnet <IP address of L2 Processor> and press Enter.
3. Log in as root.
4. At the L2 Processor CLI prompt, type set snmp community trap [community string] and press Enter.
5. Type exit

End _______________________

Configure the destination for G700 SNMP traps

Events occurring on the G700 cause SNMP traps to be generated. The G700 MGP can be configured to send SNMP traps to any network management system (NMS) in the network, including the primary server (S8300/S8700). The MGP CLI set snmp trap command is the way to configure the NMS network element that will receive those traps. The traps are sent in User Datagram Protocol (UDP) on the customer's IP network.

The command syntax is:

set SNMP trap <IP address> {enable|disable}
[{all|power|temp|app|module|config|voice|operations}]

where <IP address> is the IP address of the NMS trap receiver that will be receiving the traps from the G700, and

[{all|power|temp|app|module|config|voice|operations}] indicates the groups whose traps will be sent to the specified receiver. If no keywords follow the IP address entry, then all traps will be enabled for the specified receiver.

If "enable" or "disable" is used without a trap designation keyword, then all traps is assumed. Up to ten trap receivers can be configured.

To configure the destination for G700 SNMP traps

Begin _____________________

1. From the L2 Processor CLI, type session mgp
2. At the mg-xxx-n(super-user) prompt, type configure and press Enter.
3. At the mg-xxx-n(configure) prompt, type set snmp trap <IP address> enable and press Enter.
4. Type exit

End _______________________