Severity of the event that has occurred.
The event severity depends upon the type of
entity/notification that the operational state change event
relates to. The severity values that are normally used are
detailed below:
The enterprise versions of standard SNMP traps all have a
severity of major (4).
Operational events which notify the transition back to an
operational state from a failure state have a severity of
cleared (1).
GenEntityEvents:
Operational - severity is cleared (1)
Failure event severity levels
Type of physical Severity for failure
entity
container critical (3)
module major (4)
port major (4)
Error
Known transient errors for entities have a severity of
warning (6).
Change - severity is major (4)
LKSCommsSvcEvents:
Operational - severity is cleared (1)
Failure - severity is major (4)
GenLoopbackSvcEvent:
Severity is major (4)
GenAppSvcEvents:
Severity depends on sub-event
Operational - severity is cleared (1)
Failure - severity is major (4)
Event - severity depends on event condition
For voicemail storage conditions the severity is as
follows:
storageOkay - severity is cleared (1)
storageNearlyFull - severity is warning (6)
(Only warning severity as it could be transitory.)
storageFull - severity is critical (3)
GenSogSvcEvents:
Severity depends on sub-event
HostFailure - severity is Major (4)
ModeChange:
- Mode survivable: severity is Major (4)
- Mode subTending: severity is Minor (5)
GenUPriLicSvcEvents:
Severity depends on sub-event
ChansReduced - severity is Major (4)
CallRejected - severity is Minor (5)
PhoneChangeSvcEvents:
Severity is minor (5)
Parsed from file IPO-MIB.mib
Module: IPO-MIB
Vendor: Avaya Communication
Module: IPO-MIB
[Automatically extracted from oidview.com]
ipoGTEventStdSeverity OBJECT-TYPE SYNTAX ItuPerceivedSeverity MAX-ACCESS accessible-for-notify STATUS current DESCRIPTION "Severity of the event that has occurred. The event severity depends upon the type of entity/notification that the operational state change event relates to. The severity values that are normally used are detailed below: The enterprise versions of standard SNMP traps all have a severity of major (4). Operational events which notify the transition back to an operational state from a failure state have a severity of cleared (1). GenEntityEvents: Operational - severity is cleared (1) Failure event severity levels Type of physical Severity for failure entity container critical (3) module major (4) port major (4) Error Known transient errors for entities have a severity of warning (6). Change - severity is major (4) LKSCommsSvcEvents: Operational - severity is cleared (1) Failure - severity is major (4) GenLoopbackSvcEvent: Severity is major (4) GenAppSvcEvents: Severity depends on sub-event Operational - severity is cleared (1) Failure - severity is major (4) Event - severity depends on event condition For voicemail storage conditions the severity is as follows: storageOkay - severity is cleared (1) storageNearlyFull - severity is warning (6) (Only warning severity as it could be transitory.) storageFull - severity is critical (3) GenSogSvcEvents: Severity depends on sub-event HostFailure - severity is Major (4) ModeChange: - Mode survivable: severity is Major (4) - Mode subTending: severity is Minor (5) GenUPriLicSvcEvents: Severity depends on sub-event ChansReduced - severity is Major (4) CallRejected - severity is Minor (5) PhoneChangeSvcEvents: Severity is minor (5)" ::= { ipoGTObjects 9 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.6889.2.2.1.2.1.1 | ipoGTEventSeverity | 0 | 0 | Severity of the event that has occurred. The event severity depends upon the type of entity/notification that the operational sta… |
| 1.3.6.1.4.1.6889.2.2.1.2.1.2 | ipoGTEventDateTime | 0 | 0 | Date and time of the occurence of the event. |
| 1.3.6.1.4.1.6889.2.2.1.2.1.3 | ipoGTEventEntity | 0 | 0 | A reference, by entPhysicalIndex value, to the EntPhysicalEntry representing the physical entity that an event is associated with… |
| 1.3.6.1.4.1.6889.2.2.1.2.1.4 | ipoGTEventLoopbackStatus | 0 | 0 | This variable represents the current state of the loopback on the DS1 interface. It contains information about loopbacks establi… |
| 1.3.6.1.4.1.6889.2.2.1.2.1.5 | ipoGTEventAppEntity | 0 | 0 | The IP Office application to which a notification/trap relates. |
| 1.3.6.1.4.1.6889.2.2.1.2.1.6 | ipoGTEventAppEvent | 0 | 0 | IP Office application event states. The associated event severity of the notification/trap the object is carried in varies depen… |
| 1.3.6.1.4.1.6889.2.2.1.2.1.7 | ipoGTEventHostAddress | 0 | 0 | Address of an IP Office Small Office Gateway Subtending Host. |
| 1.3.6.1.4.1.6889.2.2.1.2.1.8 | ipoGTEventSOGMode | 0 | 0 | IP Office Small Office Gateway operating modes. survivable(1) indicates the control unit has no current host, either through conf… |
| 1.3.6.1.4.1.6889.2.2.1.2.1.10 | ipoGTEventDevID | 0 | 0 | A unique textual identifier of the alarming device. |
| 1.3.6.1.4.1.6889.2.2.1.2.1.11 | ipoGTEventEntityName | 0 | 0 | The textual name of the alarming physical entity. The contents of this object is made of concatenated entPhysicalName values that… |
| 1.3.6.1.4.1.6889.2.2.1.2.1.12 | ipoGTEventLoopbackStatusBits | 0 | 0 | This variable represents the current state of the loopback on the DS1 interface. It contains information about loopbacks establi… |