All MIBs › AVAM-SNMPv1
Category: Alarm and Event Management, Telephony and VoIP, Vendor: Avaya
Description: Provides SNMPv1 trap definitions for Avaya alarm management, mapping Avaya fault codes to SNMP notification objects.
Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.
What Is AVAM-SNMPv1?
AVAM-SNMPv1 is a MIB from Availant (an Avaya-related entity, given the 'AV' naming) defining SNMPv1 trap objects for alarm management, mapping internal Avaya fault codes to standardized SNMP notification objects. It is structured around a notification-object hierarchy (avamMIB, avamVisObj, avamNotify) rather than polled data tables, focused entirely on relaying alarm/fault events. Its monitoring value is squarely on the software/fault-notification side - it lets a network management station receive and interpret Avaya equipment alarm codes as SNMP traps, enabling automated fault detection and escalation rather than continuous performance polling. It is closely tied to Avaya's broader alarm management conventions and likely depends on vendor-specific fault code definitions maintained elsewhere in the Avaya MIB family. It is deployed in enterprise voice/telephony environments using legacy Avaya/Availant equipment where SNMPv1 trap-based alarm forwarding to a central NMS is required. Engineers can download the AVAM-SNMPv1 file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in AVAM-SNMPv1. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.
Supported Devices
- Avaya/Availant telephony equipment
Monitoring Examples
A network management station would register to receive traps defined under avamNotify and avamVisObj, mapping incoming Avaya alarm codes to a readable fault description for the NOC. A burst of high-severity avamNotify traps would indicate an active equipment fault or alarm condition on the Avaya/Availant device requiring escalation, since this MIB provides no polled counters, only event-driven fault visibility.
What Can Be Monitored
- alarm/fault trap events
- alarm code mapping
Imported Objects
From HOST-RESOURCES-MIB
| DateAndTime |
From RFC-1212
| OBJECT-TYPE |
From RFC-1215
| TRAP-TYPE |
From RFC1155-SMI
| enterprises |
From RFC1213-MIB
| DisplayString |
OIDs
RFC description
Vendor-private MIB for AVAM voice/video systems; provides SNMPv1-based monitoring of AV conferencing and communication services.
Start monitoring Avaya/Availant telephony equipment (legacy) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.