SMGR - configure a SNMP agent on SMGR interface connected to an external SNMP server as ZABBIX ?

Doc ID    SOLN250637
Version:    11.0
Status:    Published
Published date:    06 Jan 2021
Created Date:    26 May 2014
Author:   
OLIVIER PIOU
 

Details

ENV: SM 6.3.8.5682

The System Manager, SMGR allow SNMP configuration, using V3 protocol.

**/ System Manager 6.3: SNMP v1 & v2 support

Follow this Avaya Mentor Video to configure SNMPv2 notifications to be sent to NMS server. Normally, NMS servers support both v1 & v2 both. *Note*: In SMGR 6.3 support for SNMPv2 will be only for sending notifications & GET/SET operations will work for only v3. http://www.youtube.com/watch?v=_-xNX6qOrZ0

 

**/ Chapter 8: SNMP support for SessionManager

Maintaining and Troubleshooting Avaya Aura® Session Manager Release 6.3 : https://downloads.avaya.com/css/P8/documents/100168156

 

**/ Chapter Multiple entries for the same Serviceability Agent

Troubleshooting Avaya Aura® System Manager : https://downloads.avaya.com/css/P8/documents/100168120

 

**/ Avaya Aura® System Manager SNMP White Paper : https://support.avaya.com/css/P8/documents/101038705

 

 

 

 

Please find below some links with regard to information on configuring SNMP

For SMGR and ASM, this information is located in the Configuration guides

https://downloads.avaya.com/css/P8/documents/100157065

Problem Clarification

The external SNMP server name, as ZABBIX application, used snmp v2,does this protocol V2 is supported on SMGR 6.3.8 ?
It's not to send "trap SNMP"but to use "agent SNMP".
On the SystemPlatform, the SNMP agent works fine. the SNMP link is UP.

Configuration done and screenshot of the SMGR and the Extrenal SNMP server name ZABBIX:

 

Cause

 “2.  SYSTEM MANAGER SNMP AGENT

As in R6.2 in R6.3 too System Manager by default does not support SNMPv1 & SNMPv2 requests for GET/SET operations from external NMS. However System Manager can receive and process SNMP v1, v2c and v3 notifications from different elements.   The SNMP master agent (Net-SNMP) comes pre-configured with seven snmpv3 users (for each combination of authentication and privacy protocol). These SNMPv3 users however get overwritten with new usernames and credentials, when the user-prefix and authentication & privacy protocol passwords are defined by the admin during System Manager deployment as shown in the screenshot below:”

 

This suggests that SNMP can only be used for getting traps on V2 and you cannot do a READ. Can you confirm you are looking to do a READ and this is what is not working. In order to do this V3 is required

 There’s also a white paper on the subject.

               https://support.avaya.com/css/P8/documents/100171596

 

Solution

The SNMP configuration on the SMGR is changed from SNMP v2 by v3 and it’s ok.

Attachment Description


 

Attachment File

Configuration SNMP V2 on SMGR.pdf
512K • 2 minute(s) @ 56k, < 1 minute @ broadband



Avaya -- Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy