G3-AVAYA-TRAP

File: G3-AVAYA-TRAP.mib (13547 bytes)

Imported modules

G3-AVAYA-MIB RFC1213-MIB RFC-1215

Imported symbols

g3-products g3alarmsPort g3alarmsMaintName
g3alarmsOnBrd g3alarmsAlarmType g3extdevAltName
g3extdevDescription g3extdevID g3extdevBuilding
g3extdevAddress g3clientExternalName g3alarmsAlarmNumber
g3alarmsProductID g3restartDateTime g3restartLevel
g3restartCarrier g3restartCraftDemand g3restartEscalated
g3restartInterchange g3restartUnavailable g3restartCause
g3vintageSpeArelease g3vintageSpeBrelease g3vintageSpeAupID
g3vintageSpeBupID g3alarmsIPAddress g3alarmsCategory
g3alarmsErrorCodes g3alarmsSrcIPAddr g3alarmsSrcMACAddr
g3alarmsDestIPAddr g3alarmsDestPort g3alarmsProtocol
g3alarmsCount g3alarmsViolationType g3alarmsCode
g3alarmsData g3alarmsICMPType g3alarmsEventID
g3alarmsStatus sysName TRAP-TYPE

Defined Values

alarmClear 0
A Cleared Alarm Notification has been issued by the switch indicating that all alarms have been cleared.
TRAP-TYPE    

alarmCritical 1
This trap is defined for future use.
TRAP-TYPE    

alarmMajor 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.
TRAP-TYPE    

alarmMinor 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.
TRAP-TYPE    

alarmWarning 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.
TRAP-TYPE    

alarmResolved 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.
TRAP-TYPE    

alarmRMS 13
An alarm associated with security related events has been issued by the server.
TRAP-TYPE    

extalarmMajor 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.
TRAP-TYPE    

extalarmMinor 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.
TRAP-TYPE    

extalarmWarning 14
An external device Warning 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.
TRAP-TYPE    

extalarmResolved 15
An external device alarm has been resolved by the switch. The variables describe the location and nature of the alarm. This trap type only applies to voice server alarms.
TRAP-TYPE    

alarmDispatch 7
INADS has dispatched the alarm.
TRAP-TYPE    

alarmClose 8
INADS has closed the alarm.
TRAP-TYPE    

alarmRestart 9
A system restart has occurred on the switch. The variables describe the location and nature of the restart.
TRAP-TYPE    

alarmNak 10
A NAK was received in an attempt to forward the alarm to INADS.
TRAP-TYPE    

alarmNoAck 11
A response other than an ACK or NAK was received in an attempt to forward the alarm to INADS.
TRAP-TYPE    

connectOther 101
The connection status of the PBX/ECS has changed to OTHER. This status indicates that the connect is in an unknown state.
TRAP-TYPE    

connectOff 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.
TRAP-TYPE    

connectDown 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.
TRAP-TYPE    

connectInit 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.
TRAP-TYPE    

connectUp 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.
TRAP-TYPE    

connectIdle 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'.
TRAP-TYPE    

connectMax 110
The connection to a PBX/ECS could not be established due to the maximum allowed number of simultaneous connections already being active.
TRAP-TYPE    

proxyDown 150
The user has issued a stop proxy-agent command to bring down the Proxy Agent.
TRAP-TYPE    

proxyUp 151
The user has issued a start proxy-agent command to bring up the Proxy Agent.
TRAP-TYPE