SNMP Configuration

Last Updated : Nov 22, 2024 |
Prolog information
Avaya Aura® MS contains a bilingual SNMP agent that supports SNMPv1, SNMPv2c, and SNMPv3. The media server SNMP agent also acts as a proxy to the Operating System SNMP agent and supports the following RFC’s:
RFC
Title
2741
Agent Extensibility (AgentX) Protocol Version 1
Note for TCP and Linux ports.
2742
Definitions of Managed Objects for Extensible SNMP Agents.
3411
An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks.
3412
Message Processing and Dispatching for the Simple Network Management Protocol (SNMP).
3413
Simple Network Management Protocol Applications.
3414
User Based Security Model (USM) for SNMPv3.
3415
View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP).
3416
Version 2 of the Protocol Operations for the Simple Network Management Protocol (SNMP).
3417
Transport Mappings for the Simple Network Management Protocol (SNMP).
Note:
UDP transport only.
3418
Management Information Base (MIB) for the Simple Network Management Protocol (SNMP).
3584
Coexistence between Version 1, Version 2, and Version 3 of the Internet-standard Network Management Framework.
3826
The Advanced Encryption Standard (AES) Cipher Algorithm in the SNMP User-based Security Model.
3877
Alarm Management Information Base (MIB).
7630
HMAC-SHA-2 Authentication Protocols in the User-based Security Model (USM) for SNMPv3.
The Avaya Aura® Media Server 10.2 MIB can be downloaded from support.avaya.com or PLDS using download publication ID MSR000000041. This download is a zip file that contains the AVMediaServer-MIB and the AVAYAGEN-MIB. The AVAYAGEN-MIB must be imported into the Network Management Station (NMS) before importing AVMediaServer-MIB
The following configuration is required before an NMS can issue SNMP requests to the media server:
  • Define SNMP Users
  • Enable the SNMP Agent and specify the SNMP Users that may issue SNMP requests to this device
This procedure is described in detail in the section called Configuring SNMP Agent.
The following configuration is required before an NMS can receive SNMP traps from the media server:
  • Define SNMP Users
  • Define SNMP Trap Destinations
  • Define SNMP Routes
  • Enable SNMP trap notifications for Alarms and/or Event logs.
This procedure is described in detail in section called Enabling SNMP Traps.
Note:
Avaya Aura® Media Server will send traps using Coordinated Universal Time (UTC) rather than local system time.
Important:
You can only update SNMP configuration on the Primary server. Configuration changes applied to the primary server will be replicated to all servers within the cluster.