ipoGTEventSeverity
IPO-MIB ·
.1.3.6.1.4.1.6889.2.2.1.2.1.1
Object
scalar deprecated
Enumeration
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:
GenEntityEvents:
Type of physical Severity
entity
container critical
module major
port major
Known transient errors for entities have a severity of minor.
LKSCommsEvents:
Severity is major
GenLoopbackEvent:
Severity is major
GenAppEvents:
Severity depends on sub-event
Failure/Operational - severity is major
Event - severity depends on event condition
ipoGenSogEvents:
Severity depends on sub-event
HostFailure - severity is Major
ModeChange:
- Mode survivable: severity is Major
- Mode subTending: severity is Minor
PhoneChangeEvents:
Severity is minor
**NOTE: This object is deprecated and replaced by
ipoGTEventStdSeverity.
Context
- MIB
- IPO-MIB
- OID
.1.3.6.1.4.1.6889.2.2.1.2.1.1- Type
- scalar
- Access
- notifyonly
- Status
- deprecated
- Parent
- ipoGTObjects
- Groups
- 1
Net-SNMP examples
How SNMP and these commands workScalars have one instance, identified by the .0 suffix.
Read the scalar instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'IPO-MIB' -M '/opt/observium/mibs/avaya:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'IPO-MIB::ipoGTEventSeverity.0'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'IPO-MIB' -M '/opt/observium/mibs/avaya:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'IPO-MIB::ipoGTEventSeverity'
Syntax
Enumeration
Values & Constraints
Enumerated Values
1 | critical |
2 | major |
3 | minor |
Conformance
Member of