zxAnEventSyslogSeverity

ZTE-AN-EVNET-MIB · .1.3.6.1.4.1.3902.1015.190.7.2.2
Commands MIB view Table view

Object

scalar r/w Integer32 
The syslog message severity, The priority value of PRI is calculated 
by first multiplying the Facility number by 8 and then adding the 
numerical value of the Severity.             
                          
 Numerical Code       Severity          
  0             Emergency: system is unusable
  1             Alert: action must be taken immediately
  2             Critical: critical conditions
  3             Error: error conditions
  4             Warning: warning conditions
  5             Notice: normal but significant condition
  6             Informational: informational messages
  7             Debug: debug-level messages    
            
  More information, please refer to rfc3164.

Context

MIB
ZTE-AN-EVNET-MIB
OID
.1.3.6.1.4.1.3902.1015.190.7.2.2
Type
scalar
Access
readwrite
Status
current
Parent
zxAnEventSyslogGlobalObjects

Net-SNMP examples

How SNMP and these commands work

Scalars have one instance, identified by the .0 suffix.

Read the scalar instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'ZTE-AN-EVNET-MIB' -M '/opt/observium/mibs/zte:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'ZTE-AN-EVNET-MIB::zxAnEventSyslogSeverity.0'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'ZTE-AN-EVNET-MIB' -M '/opt/observium/mibs/zte:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'ZTE-AN-EVNET-MIB::zxAnEventSyslogSeverity'

Syntax

Integer32

Values & Constraints

Object Constraints
range: 0-7