Avaya

Modular Messaging Help

Print | Back | Fwd | Close
Home | Search | Site Index
 Getting Started 
 Administration 
 Maintenance 
 Reference 
Home   >   MAS Administration   >   Serviceability - Voice Mail Domain dialog box, SNMP properties

Serviceability - Voice Mail Domain dialog box, SNMP properties

To configure SNMP-specific alarm notification settings, use the SNMP tab of the Serviceability - Voice Mail Domain dialog box.

Note: You should configure the fields on this tab only if you are using SNMP to send traps to an SNMP Network Management Station (NMS).

To display the Serviceability - Voice Mail Domain dialog box, SNMP tab:

  1. In the Voice Mail System Configuration window, click the voice mail domain.
  2. Double-click Serviceability.

    3. The system displays the Serviceability - Voice Mail Domain dialog box, with the General tab active.

  3. On the General tab, select Send alarms using: SNMP.
  4. Click the SNMP tab.

To configure general alarm notification settings:

  1. Configure the following fields on the SNMP tab:
    • Network Management Station:  Enter in this field the fully qualified domain name or IP address of the NMS to which you want to send alarm notification traps.
    • Context (Community):  Enter in this field the name of the context or community to which the NMS belongs.

      • For more information about how to configure this field, see the documentation for your SNMP NMS.

    • Acknowledgement type:  The Avaya Modular Messaging system offers two methods for you to get acknowledgement from the SNMP NMS that the alarm notification traps have been received:
      • Return trap  This acknowledgement type is potentially better and more reliable, because it means that, when an alarm trap is received by your NMS, it is configured to send a trap of its own back to the MAS, acknowledging that it has received the alarm notification. It is also more complicated to set up and requires that you configure your NMS to generate such return traps.
      • Ping surround  This acknowledgement type is easier to implement but inherently less informative and makes certain assumptions. When this option is selected, and an alarm trap is ready to be sent to the NMS, a ping command is first generated to the NMS. Only if the MAS receives a ping response does it go ahead and send the trap. Then it sends another ping request. If it receives another ping response from the NMS, the assumption is that the trap was received on the NMS.

        • If no initial ping response is received from the NMS, then the MAS waits 5 minutes before trying again. It keeps trying at 5-minute intervals, then, until it receives a response from the NMS. If after 16 tries there is still no response from the NMS, then the MAS stops trying and raises a warning alarm against the alarming system.

        If the first ping is successful and the trap is sent, but the second ping is not successful, then the assumption is that the trap was not sent successfully. In this case, the trap is rescheduled to be sent at 5-minute intervals until it is successfully sent. If after 16 tries there is still no response from the NMS, then the MAS stops trying and raises a warning alarm against the alarming system.

  2. Click OK.

Home | Search | Site Index | Print | Back | Fwd | Close

©2002 Avaya Inc. All rights reserved. Last modified: