All MIBs › AVAYAGEN-MIB
Organization: Avaya Inc.
Last Updated: 2004-01-27
Category: SNMP Framework, Telephony and VoIP, Vendor: Avaya
Description:
Defines general Avaya enterprise OID roots and system identification objects shared across all Avaya product MIBs.
Imported Objects
From SNMPv2-SMI
| MODULE-IDENTITY | |
| enterprises |
What Is AVAYAGEN-MIB?
AVAYAGEN-MIB defines the top-level Avaya enterprise OID tree, establishing the organizational namespace (avayaProducts, avayaMibs, gateway product/mib branches, topology root) under which all other Avaya product-specific MIBs register their object identifiers. It is purely structural/registration in nature and contains no live counters, tables, or traps of its own -- it exists so that Avaya development teams can obtain and import consistent organization and group OIDs when building their actual product MIBs. It therefore has no direct role in monitoring hardware or software status; any monitoring capability comes entirely from the specific Avaya product MIBs (voice gateways, PBX systems, contact center systems, etc.) that root themselves under this tree. Virtually every other Avaya MIB module has an implicit dependency on this module for its OID assignment, so MIB packages distributed for Avaya equipment typically bundle the AVAYAGEN-MIB download as a prerequisite file that must be compiled first. It is relevant wherever Avaya telephony/UC equipment is present, purely as the naming backbone underlying those devices' actual monitoring MIBs.
IPNetwork Monitor allows you to monitor SNMP objects defined in AVAYAGEN-MIB. 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 J179 — current-generation J100-series IP desk phone
- Avaya Communication and Collaboration Suite (2024) — Avaya's current unified-communications platform
Monitoring Examples
AVAYAGEN-MIB defines only OID-tree placeholder nodes such as avayaProducts, avayaMibs, avGatewayProducts, and avGatewayMibs with no OBJECT-TYPE instances carrying runtime data, so there is nothing to poll from this module directly. A management tool would instead use these root OIDs to identify and navigate to the specific Avaya product MIB registered beneath them. Any real monitoring scenario is carried out through those dependent product MIBs.
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| avaya | 1.3.6.1.4.1.6889 | Avaya top-level OID tree. This MIB module deals defines the Avaya enterprise-specific tree. Development organizations within Avaya who wish to register MIBs under the Avaya enterprise OID, should: a. Contact the maintainer of this module, and get an organization OID and group OID. b. Import the definition of their Organization OID from this MIB. | ||
| avayaProducts | 1.3.6.1.4.1.6889.1 | |||
| avGatewayProducts | 1.3.6.1.4.1.6889.1.6 | |||
| avayaMibs | 1.3.6.1.4.1.6889.2 | |||
| lsg | 1.3.6.1.4.1.6889.2.1 | |||
| avayaEISTopology | 1.3.6.1.4.1.6889.2.1.10 | |||
| avayaSystemStats | 1.3.6.1.4.1.6889.2.1.11 | |||
| avGatewayMibs | 1.3.6.1.4.1.6889.2.6 |
RFC description
Vendor-private generic MIB for Avaya telecommunications equipment and devices.
Start monitoring Avaya J179 IP desk phone / Avaya Communication and Collaboration Suite 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.