ipoGTEventStdSeverity
IPO-MIB ·
.1.3.6.1.4.1.6889.2.2.1.2.1.9
Object
scalar
ITU-ALARM-TC-MIBItuPerceivedSeverity
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)
GenQoSMonSvcEvent:
QoSWarning - severity is Warning (6)
PhoneChangeSvcEvents:
Severity is minor (5)
ipoGenSystemRunningBackupEvent:
Severity is cleared (1)
Severity is critical (3)
ipoGenInvalidMemoryCardEvent:
Severity is cleared (1)
Severity is Major (4)
ipoGenNoLicenceKeyDongleEvent:
Severity is cleared (1)
Severity is warning (6)
Severity is critical (3)
ipoGenMemoryCardCapacityEvent:
Severity depends on sub-event
storageOkay - severity is cleared (1)
storageNearlyFull - severity is warning (6)
storageFull - severity is critical (3)
Context
- MIB
- IPO-MIB
- OID
.1.3.6.1.4.1.6889.2.2.1.2.1.9- Type
- scalar
- Access
- notifyonly
- Status
- current
- Parent
- ipoGTObjects
Syntax
ITU-ALARM-TC-MIBItuPerceivedSeverity
Values & Constraints
No enumerated values or constraints recorded.