OID reference
1.3.6.1.4.1.4935.15.17.1.5
This value indicates which syslog message will be processed. Any syslog message with a severity value greater than this value will be ignored by the agent.
Identification
{1 3 6 1 4 1 4935 15 17 1 5}
| Value | Name |
|---|---|
| 0 | disabled |
| 1 | critical |
| 2 | error |
| 3 | warning |
| 4 | informational |
| 5 | debug |
At least one MIB declaration places this object in a scalar group. A scalar instance uses the suffix .0.
snmpget [connection options] DEVICE .1.3.6.1.4.1.4935.15.17.1.5.0
Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.
Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.
The displayed source records contain one distinct definition. Compare its source records.
syslogMsgMaxSeverity OBJECT-TYPE
SYNTAX INTEGER {
disabled(0),
critical(1),
error(2),
warning(3),
informational(4),
debug(5)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION "This value indicates which syslog message will be processed.
Any syslog message with a severity value greater than this
value will be ignored by the agent."
DEFVAL { informational }
::= { syslogMIBObjects 5 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
This value indicates which syslog message will be processed. Any syslog message with a severity value greater than this value will be ignored by the agent.
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: syslogMsgMaxSeverity
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"syslogMsgMaxSeverity",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"disabled",
"(",
"0",
")",
",",
"critical",
"(",
"1",
")",
",",
"error",
"(",
"2",
")",
",",
"warning",
"(",
"3",
")",
",",
"informational",
"(",
"4",
")",
",",
"debug",
"(",
"5",
")",
"}",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"This value indicates which syslog message will be processed. Any syslog message with a severity value greater than this value will be ignored by the agent.\"",
"DEFVAL",
"{",
"informational",
"}",
"::=",
"{",
"syslogMIBObjects",
"5",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"disabled",
0
],
[
"critical",
1
],
[
"error",
2
],
[
"warning",
3
],
[
"informational",
4
],
[
"debug",
5
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"This value indicates which syslog message will be processed. Any syslog message with a severity value greater than this value will be ignored by the agent."
],
null,
null,
null,
[
"DEFVAL",
"informational"
]
]
}Vendor MIB copy from the Observium Community archive.
Module: MX-SYSLOG-MIB
See published definition above
{'MX-TC': ['MxIpHostName', 'MxIpConfigSource', 'MxIpPort', 'MxEnableState', 'MxIpSelectConfigSource', 'MxIpDhcpSiteSpecificCode'], 'MX-SMI': ['ipAddressStatus', 'ipAddressConfig', 'mediatrixConfig'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Unsigned32'], 'SNMPv2-CONF': ['OBJECT-GROUP', 'MODULE-COMPLIANCE']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.4935.15.17.1.50 | syslogMsgLocalMaxSeverity | 0 | 0 | |
| 1.3.6.1.4.1.4935.15.17.1.100 | syslogMsgLocalMaxNbr | 0 | 0 | |
| 1.3.6.1.4.1.4935.15.17.1.150 | syslogLocalMsgTable | 1 | 5 | |
| 1.3.6.1.4.1.4935.15.17.1.200 | syslogMsgCustomization | 4 | 4 |