G3-AVAYA-TRAP: View SNMP OID List / Download MIB

VENDOR: AVAYA COMMUNICATION


 Home MIB: G3-AVAYA-TRAP
Download as:   
SNMPv2-CONF, SNMPv2-MIB, SNMPv2-SMI, G3-AVAYA-MIB, SNMPv2-TC

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 alarmClear 1.3.6.1.4.1.6889.1.8.10.0
A Cleared Alarm Notification has been issued by the switch indicating that all alarms have been cleared.
 alarmCritical 1.3.6.1.4.1.6889.1.8.10.1
This trap is defined for future use.
 alarmMajor 1.3.6.1.4.1.6889.1.8.10.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.
 alarmMinor 1.3.6.1.4.1.6889.1.8.10.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.
 alarmWarning 1.3.6.1.4.1.6889.1.8.10.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.
 extalarmMajor 1.3.6.1.4.1.6889.1.8.10.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.
 extalarmMinor 1.3.6.1.4.1.6889.1.8.10.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.
 alarmDispatch 1.3.6.1.4.1.6889.1.8.10.7
INADS has dispatched the alarm.
 alarmClose 1.3.6.1.4.1.6889.1.8.10.8
INADS has closed the alarm.
 alarmRestart 1.3.6.1.4.1.6889.1.8.10.9
A system restart has occurred on the switch. The variables describe the location and nature of the restart.
 alarmNak 1.3.6.1.4.1.6889.1.8.10.10
A NAK was received in an attempt to forward the alarm to INADS.
 alarmNoAck 1.3.6.1.4.1.6889.1.8.10.11
A response other than an ACK or NAK was received in an attempt to forward the alarm to INADS.
 alarmResolved 1.3.6.1.4.1.6889.1.8.10.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.
 connectOther 1.3.6.1.4.1.6889.1.8.10.101
The connection status of the PBX/ECS has changed to OTHER. This status indicates that the connect is in an unknown state.
 connectOff 1.3.6.1.4.1.6889.1.8.10.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.
 connectDown 1.3.6.1.4.1.6889.1.8.10.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.
 connectInit 1.3.6.1.4.1.6889.1.8.10.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.
 connectUp 1.3.6.1.4.1.6889.1.8.10.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.
 connectIdle 1.3.6.1.4.1.6889.1.8.10.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'.
 connectMax 1.3.6.1.4.1.6889.1.8.10.110
The connection to a PBX/ECS could not be established due to the maximum allowed number of simultaneous connections already being active.
 proxyDown 1.3.6.1.4.1.6889.1.8.10.150
The user has issued a stop proxy-agent command to bring down the Proxy Agent.
 proxyUp 1.3.6.1.4.1.6889.1.8.10.151
The user has issued a start proxy-agent command to bring up the Proxy Agent.