smepGTEventStdSeverity
AV-SME-PLATFORM-MIB ·
.1.3.6.1.4.1.6889.2.48.1.2.1.1
Object
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).
GenAppEvents:
Severity depends on event condition
crash - severity is critical (3)
Context
- MIB
- AV-SME-PLATFORM-MIB
- OID
.1.3.6.1.4.1.6889.2.48.1.2.1.1- Type
- scalar
- Access
- notifyonly
- Status
- current
- Parent
- smepGTObjects
- 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 'AV-SME-PLATFORM-MIB' -M '/opt/observium/mibs/avaya:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'AV-SME-PLATFORM-MIB::smepGTEventStdSeverity.0'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'AV-SME-PLATFORM-MIB' -M '/opt/observium/mibs/avaya:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'AV-SME-PLATFORM-MIB::smepGTEventStdSeverity'
Syntax
- Source
- ITU-ALARM-TC-MIBItuPerceivedSeverity
- Base type
Enumeration
Values & Constraints
Type Values
1 | cleared |
2 | indeterminate |
3 | critical |
4 | major |
5 | minor |
6 | warning |
Conformance
Member of