HTTP Logging Invalid Format Error
Sources for this description
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
OID reference
1.3.6.1.4.1.22610.2.4.10.139.6.1.19
HTTP Logging Invalid Format Error
Identification
{1 3 6 1 4 1 22610 2 4 10 139 6 1 19}
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.
httpLoggingInvalidFormat OBJECT-TYPE
SYNTAX CounterBasedGauge64
MAX-ACCESS read-only
STATUS current
DESCRIPTION "HTTP Logging Invalid Format Error"
::={ acosFwLoggingS 19 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
HTTP Logging Invalid Format Error
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: httpLoggingInvalidFormat
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"httpLoggingInvalidFormat",
"OBJECT-TYPE",
"SYNTAX",
"CounterBasedGauge64",
"MAX-ACCESS",
"read-only",
"STATUS",
"current",
"DESCRIPTION",
"\"HTTP Logging Invalid Format Error\"",
"::=",
"{",
"acosFwLoggingS",
"19",
"}"
],
"syntax_tree": [
[
"row",
"CounterBasedGauge64"
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"HTTP Logging Invalid Format Error"
],
null,
null,
null,
null
]
}Vendor MIB copy from the Observium Community archive.
Module: ACOS-FW-STATS-MIB
See published definition above
{'SNMPv2-TC': ['DisplayString', 'PhysAddress'], 'A10-AX-MIB': ['acosRootStats'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Counter32', 'Integer32', 'Counter64', 'OBJECT-IDENTITY', 'NOTIFICATION-TYPE'], 'INET-ADDRESS-MIB': ['InetAddressType']}Related source files and packages:
Registration