wwpSyslogSeverity
WWP-SYSLOG-MIB ·
.1.3.6.1.4.1.6141.2.27.1.1.1
Object
scalar r/w
Enumeration
The syslog severity is box-wide regardless of the output device
listed when actually logging a message (e.g., console, syslog,
flash), the message will ALWAYS be sent to syslog if the syslog
severity is in line with the incoming message severity
(verbosity).
Any syslog message with a severity value greater than this value
will be ignored by the agent. note: serverity level
numeric values increase as their severity
decreases, e.g. error(3) is more severe
than debug(7).
Context
- MIB
- WWP-SYSLOG-MIB
- OID
.1.3.6.1.4.1.6141.2.27.1.1.1- Type
- scalar
- Access
- readwrite
- Status
- current
- Parent
- wwpSyslog
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 'WWP-SYSLOG-MIB' -M '/opt/observium/mibs/ciena:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'WWP-SYSLOG-MIB::wwpSyslogSeverity.0'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'WWP-SYSLOG-MIB' -M '/opt/observium/mibs/ciena:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'WWP-SYSLOG-MIB::wwpSyslogSeverity'
Syntax
Enumeration
Values & Constraints
Enumerated Values
0 | logEmergency |
1 | logAlert |
2 | logCritical |
3 | logErrors |
4 | logWarnings |
5 | logNotifications |
6 | logInformational |
7 | logDebugging |