OID reference
1.3.6.1.4.1.10002.1.1.1.1.3
Number of entries in the red light table.
Identification
{1 3 6 1 4 1 10002 1 1 1 1 3}
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.10002.1.1.1.1.3.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.
memBuffer OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Physical memory used by buffers (in KB)"
::= { memory 3 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Description 1
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)Common and standard MIB copies (LibreNMS/Observium Community)
Description 2
Parsed from vossysmgr.mib.txt · comtek · COMTEK-MIB
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: memBuffer
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"memBuffer",
"OBJECT-TYPE",
"SYNTAX",
"Gauge32",
"MAX-ACCESS",
"read-only",
"STATUS",
"current",
"DESCRIPTION",
"\"Physical memory used by buffers (in KB)\"",
"::=",
"{",
"memory",
"3",
"}"
],
"syntax_tree": [
[
"ApplicationSyntax",
"Gauge32"
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Physical memory used by buffers (in KB)"
],
null,
null,
null,
null
]
}Vendor MIB copy from the Observium Community archive.
Module: FROGFOOT-RESOURCES-MIB
See published definition above
{'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'DisplayString'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'Gauge32', 'enterprises'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP']}Related source files and packages:
Vendor MIB copy from the LibreNMS archive.
Module: FROGFOOT-RESOURCES-MIB
{'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'DisplayString'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'Gauge32', 'enterprises'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP']}Related source files and packages:
Historical records
vosNumRedLights OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Number of entries in the red light table."
::= { vos 3 }
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.10002.1.1.1.1.1 | memTotal, os400SysName, vosNumModules | 0 | 0 | Number of modules. |
| 1.3.6.1.4.1.10002.1.1.1.1.2 | memFree, os400SysModel, vosTable | 1 | 7 | A simplified version of what is read from s$get_module_usage(). |
| 1.3.6.1.4.1.10002.1.1.1.1.4 | memCache, os400QHistoryTable, vosRedLightTable | 1 | 4 | A table of messages from the >system>hardware_log.*. |
| 1.3.6.1.4.1.10002.1.1.1.1.5 | os400UtcOffset, vosConfigFileName | 0 | 0 | Full path name of current configuration file used by agent. The agent always uses the file snmpd.config as its configuration file… |
| 1.3.6.1.4.1.10002.1.1.1.1.6 | vosInputQueueMessage | 0 | 0 | Most recent remote console message sent by NMS to agent. This MIB item is the method in which remote console commands are entered… |
| 1.3.6.1.4.1.10002.1.1.1.1.7 | vosInputQueueName | 0 | 0 | Input Queue name where the agent is to write remote console messages for processing by NM*Console. This name is specified in the… |
| 1.3.6.1.4.1.10002.1.1.1.1.8 | vosTrapCommFileName | 0 | 0 | Full path name of the current trap destination file being used by the agent. The agent always starts up using the file snmpd.trap… |
| 1.3.6.1.4.1.10002.1.1.1.1.9 | vosUserTrapCommFileName | 0 | 0 | Full path name of the current user trap destination file being used by the agent. If the file snmpd.user_trap exists when the ag… |