etsysSyslogServerSeverity

ENTERASYS-SYSLOG-CLIENT-MIB · .1.3.6.1.4.1.5624.1.2.14.2.4.1.7
Commands MIB view Table view

Object

column r/w SyslogSeverity 
The maximum severity level of the messages that should
be forwarded to the syslog server.  The higher the level,
the lower the severity.
              
If an entity only supports filtering based on a single
severity level for all servers then this may optionally
be implemented read-only, in which case the current value
of etsysSyslogServerDefaultSeverity will be used.

Context

MIB
ENTERASYS-SYSLOG-CLIENT-MIB
OID
.1.3.6.1.4.1.5624.1.2.14.2.4.1.7
Type
column
Access
readwrite
Status
current
Parent
etsysSyslogServerEntry
Groups
3

Net-SNMP examples

How SNMP and these commands work

Walk the column to discover its indexed instances, or supply every index to read one instance.

Walk the column
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'ENTERASYS-SYSLOG-CLIENT-MIB' -M '/opt/observium/mibs/enterasys:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'ENTERASYS-SYSLOG-CLIENT-MIB::etsysSyslogServerSeverity'
More examples
Read one indexed instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'ENTERASYS-SYSLOG-CLIENT-MIB' -M '/opt/observium/mibs/enterasys:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'ENTERASYS-SYSLOG-CLIENT-MIB::etsysSyslogServerSeverity.<etsysSyslogServerIndex>'
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'ENTERASYS-SYSLOG-CLIENT-MIB' -M '/opt/observium/mibs/enterasys:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'ENTERASYS-SYSLOG-CLIENT-MIB::etsysSyslogServerSeverity'

Syntax

SyslogSeverity
Source
SyslogSeverity
Base type
Enumeration

Values & Constraints

Type Values
1emergency
2alert
3critical
4error
5warning
6notice
7info
8debug

Conformance

Member of
etsysSyslogServerGroup etsysSyslogServerGroup2 etsysSyslogServerGroup3
Compliance refinements
etsysSyslogClientCompliance readonly
Write access is not required for implementations that
do not support configuring the message severity level
on a per server basis.
etsysSyslogClientCompliance2 readonly
Write access is not required for implementations that
do not support configuring the message severity level
on a per server basis.
etsysSyslogClientCompliance3 readonly
Write access is not required for implementations that
do not support configuring the message severity level
on a per server basis.