G3-AVAYA-TRAP

All MIBs › G3-AVAYA-TRAP

Category: Domain: Telephony/VoIP, Vendor: Avaya

Description: Avaya G3 communications server MIB defining SNMP traps for PBX fault and status change notifications.

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 G3-AVAYA-TRAP?

G3-AVAYA-TRAP is an Avaya-specific MIB that defines SNMP trap (notification) types for the Avaya G3 communications server, a PBX/telephony switching platform. Rather than exposing polled data tables, it is a fault/status-change notification module, meaning its purpose is to alert a management station in real time when the PBX experiences a defined fault or state transition. This makes it directly relevant to monitoring the operational health/software status of the G3 communications server, since traps are typically the fastest way to learn about card failures, trunk/line faults, or software-triggered alarms without waiting on a polling cycle. As a trap definition module it likely depends on Avaya's broader G3-series MIB family (and standard SNMPv2-TRAP/NOTIFICATION-TYPE conventions) for the object types carried in each trap's varbinds. It is deployed in enterprise/carrier telephony environments running Avaya G3 (Definity-class) communications servers, feeding alarms into an NMS or telephony management system. Engineers can download the G3-AVAYA-TRAP file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in G3-AVAYA-TRAP. 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 G3/Definity communications server (PBX)

Monitoring Examples

No concrete trap or object names were supplied for this module, so specific trap names cannot be listed; in general an operator would configure their NMS to receive Avaya G3 traps and alert staff whenever a PBX fault or status-change notification fires, since these traps are the primary payload of this MIB rather than polled counters. Because no sample objects are available, a more detailed scenario would be speculative.

What Can Be Monitored

PBX fault notifications
PBX status change notifications

Imported Objects

From G3-AVAYA-MIB

g3-products
g3alarmsAlarmNumber	OBJECT-TYPE
g3alarmsAlarmType	OBJECT-TYPE
g3alarmsMaintName	OBJECT-TYPE
g3alarmsOnBrd	OBJECT-TYPE
g3alarmsPort	OBJECT-TYPE
g3alarmsProductID	OBJECT-TYPE
g3clientExternalName	OBJECT-TYPE
g3extdevAddress	OBJECT-TYPE
g3extdevAltName	OBJECT-TYPE
g3extdevBuilding	OBJECT-TYPE
g3extdevDescription	OBJECT-TYPE
g3extdevID	OBJECT-TYPE
g3restartCarrier	OBJECT-TYPE
g3restartCause	OBJECT-TYPE
g3restartCraftDemand	OBJECT-TYPE
g3restartDateTime	OBJECT-TYPE
g3restartEscalated	OBJECT-TYPE
g3restartInterchange	OBJECT-TYPE
g3restartLevel	OBJECT-TYPE
g3restartUnavailable	OBJECT-TYPE
g3vintageSpeArelease	OBJECT-TYPE
g3vintageSpeAupID	OBJECT-TYPE
g3vintageSpeBrelease	OBJECT-TYPE
g3vintageSpeBupID	OBJECT-TYPE

From RFC-1215

TRAP-TYPE

From RFC1213-MIB

sysName

OIDs

OID symbolic	OID numeric	Description
NTF alarmClear	1.3.6.1.4.1.6889.1.8.1.0.0	A Cleared Alarm Notification has been issued by the switch indicating that all alarms have been cleared.
NTF alarmCritical	1.3.6.1.4.1.6889.1.8.1.0.1	This trap is defined for future use.
NTF alarmMajor	1.3.6.1.4.1.6889.1.8.1.0.2	A Major alarm has been issued by the switch. The MIB variables provide attributes of the alarm. The information contained in the g3alarmsPort, g3alarmsMaintName, g3alarmsOnBrd trap variables differ depending on the kind of alarm. If the alarm is a voice server alarm these fields contain, respectively, an equipment location, maintenance object name, and flag indicating whether or not the alarm was on-board. For server platform alarms and messaging alarms these fields contain, respectively, an alarm description including the source of the alarm, a string indicating the resource from which the alarm was generated, and an event ID associated with that resource. More details on the contents of these fields can be found in the appropriate product maintenance documentation.
NTF alarmMinor	1.3.6.1.4.1.6889.1.8.1.0.3	A Minor alarm has been issued by the switch. The fields in this trap type has the same differences, for g3alarmsPort, g3alarmsMaintName, and g3alarmsOnBrd, as described above for the alarmMajor trap type.
NTF alarmWarning	1.3.6.1.4.1.6889.1.8.1.0.4	A Warning alarm has been issued by the switch. The fields in this trap type has the same differences, for g3alarmsPort, g3alarmsMaintName, and g3alarmsOnBrd, as described above for the alarmMajor trap type.
NTF extalarmMajor	1.3.6.1.4.1.6889.1.8.1.0.5	An external device Major alarm has been issued by the switch. The variables describe the location and nature of the alarm. This trap type only applies to voice server alarms.
NTF extalarmMinor	1.3.6.1.4.1.6889.1.8.1.0.6	An external device Minor alarm has been issued by the switch. The variables describe the location and nature of the alarm. This trap type only applies to voice server alarms.
NTF alarmDispatch	1.3.6.1.4.1.6889.1.8.1.0.7	INADS has dispatched the alarm.
NTF alarmClose	1.3.6.1.4.1.6889.1.8.1.0.8	INADS has closed the alarm.
NTF alarmRestart	1.3.6.1.4.1.6889.1.8.1.0.9	A system restart has occurred on the switch. The variables describe the location and nature of the restart.
NTF alarmNak	1.3.6.1.4.1.6889.1.8.1.0.10	A NAK was received in an attempt to forward the alarm to INADS.
NTF alarmNoAck	1.3.6.1.4.1.6889.1.8.1.0.11	A response other than an ACK or NAK was received in an attempt to forward the alarm to INADS.
NTF alarmResolved	1.3.6.1.4.1.6889.1.8.1.0.12	An alarm has been resolved on the switch. The fields in this trap type has the same differences, for g3alarmsPort, g3alarmsMaintName, and g3alarmsOnBrd, as described above for the alarmMajor trap type.
NTF connectOther	1.3.6.1.4.1.6889.1.8.1.0.101	The connection status of the PBX/ECS has changed to OTHER. This status indicates that the connect is in an unknown state.
NTF connectOff	1.3.6.1.4.1.6889.1.8.1.0.102	The connection status of the PBX/ECS has changed to OFF. This status indicates that user set the connection state to off so that the Proxy Agent will not start up a connection with the PBX/ECS.
NTF connectDown	1.3.6.1.4.1.6889.1.8.1.0.103	The connection status of the PBX/ECS has changed to DOWN. This status indicates that the Proxy Agent attempted to establish a connection with the PBX/ECS and failed.
NTF connectInit	1.3.6.1.4.1.6889.1.8.1.0.104	The connection status of the PBX/ECS has changed to INIT. This status indicates that the Proxy Agent is in the process of attempting to connect to the PBX/ECS.
NTF connectUp	1.3.6.1.4.1.6889.1.8.1.0.105	The connection status of the PBX/ECS has changed to UP. This status indicates that the Proxy Agent has a connection established with the PBX/ECS.
NTF connectIdle	1.3.6.1.4.1.6889.1.8.1.0.106	The connection status of the PBX/ECS has changed to IDLE. This status indicates that a connection with the PBX/ECS is currently inactive due to the dynamic timeout having been reached without any activity. The connection will stay in the IDLE state until an SNMP request or alarm is received. This connection status only applies if the connection type is 'dynamic'.
NTF connectMax	1.3.6.1.4.1.6889.1.8.1.0.110	The connection to a PBX/ECS could not be established due to the maximum allowed number of simultaneous connections already being active.
NTF proxyDown	1.3.6.1.4.1.6889.1.8.1.0.150	The user has issued a stop proxy-agent command to bring down the Proxy Agent.
NTF proxyUp	1.3.6.1.4.1.6889.1.8.1.0.151	The user has issued a start proxy-agent command to bring up the Proxy Agent.

RFC description

Avaya G3 vendor-private MIB; defines SNMP traps and events for Avaya telecommunications switches and call processing systems.

Start monitoring Avaya G3/Definity communications servers 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.

Download G3-AVAYA-TRAP

What Is G3-AVAYA-TRAP?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description