OID reference
1.3.6.1.4.1.4526.17.59.4.1.1
Indicates how many meters can be chained in succession (ie. so that if the first meter fails, the second can be examined). The final meter in a sequence is always 'always-conform', so if the value of this parameter is 2, the platform that supports a single meter and then a second marking/action for meter failure.
Identification
{1 3 6 1 4 1 4526 17 59 4 1 1}
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.4526.17.59.4.1.1.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.
rlPolicyMeterDepth OBJECT-TYPE
SYNTAX INTEGER
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates how many meters can be chained in succession (ie. so
that if the first meter fails, the second can be examined).
The final meter in a sequence is always 'always-conform', so if
the value of this parameter is 2, the platform that supports a
single meter and then a second marking/action for meter failure."
::= { rlPolicyMeterPlatDependParams 1 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Indicates how many meters can be chained in succession (ie. so that if the first meter fails, the second can be examined). The final meter in a sequence is always 'always-conform', so if the value of this parameter is 2, the platform that supports a single meter and then a second marking/action for meter failure.
NETGEAR MIB copies (LibreNMS/Observium Community)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: rlPolicyMeterDepth
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"rlPolicyMeterDepth",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"MAX-ACCESS",
"read-only",
"STATUS",
"current",
"DESCRIPTION",
"\"Indicates how many meters can be chained in succession (ie. so that if the first meter fails, the second can be examined). The final meter in a sequence is always 'always-conform', so if the value of this parameter is 2, the platform that supports a single meter and then a second marking/action for meter failure.\"",
"::=",
"{",
"rlPolicyMeterPlatDependParams",
"1",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER"
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Indicates how many meters can be chained in succession (ie. so that if the first meter fails, the second can be examined). The final meter in a sequence is always 'always-conform', so if the value of this parameter is 2, the platform that supports a single meter and then a second marking/action for meter failure."
],
null,
null,
null,
null
]
}Vendor MIB copy from the Observium Community archive. NETGEAR support.
Module: NETGEAR-RADLAN-POLICY-MIB
See published definition above
{'IF-MIB': ['InterfaceIndexOrZero', 'InterfaceIndex'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'TruthValue', 'RowStatus', 'RowPointer', 'DisplayString'], 'SNMPv2-SMI': ['OBJECT-TYPE', 'IpAddress', 'Unsigned32', 'Counter32', 'zeroDotZero', 'MODULE-IDENTITY', 'Counter64'], 'Q-BRIDGE-MIB': ['PortList', 'VlanId'], 'DIFF-SERV-MIB': ['diffServClassifierEntry'], 'NETGEAR-RADLAN-MIB': ['Percents', 'VlanPriority', 'rnd'], 'NETGEAR-RADLAN-BRIDGEMIBOBJECTS-MIB': ['VlanList1', 'VlanList2', 'VlanList3', 'VlanList4']}Related source files and packages:
Registration