OID reference
1.3.6.1.4.1.6321.1.2.3.1.14.1
This managed object is used for identify the target on which the counter would be cleared. The target is encoded as: Byte 1: reserved Byte 2~3: reserved Byte 4: reserved Byte 5~11:each octet specifies a set of eight ports, with the first octet specifying ports 1 through 8, etc.
Identification
{1 3 6 1 4 1 6321 1 2 3 1 14 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.6321.1.2.3.1.14.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.
counterClearTarget OBJECT-TYPE
SYNTAX OCTET STRING
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This managed object is used for identify the target on which
the counter would be cleared. The target is encoded as:
Byte 1: reserved
Byte 2~3: reserved
Byte 4: reserved
Byte 5~11:each octet specifies a set of eight ports, with the first
octet specifying ports 1 through 8, etc."
::= { clear 1 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
This managed object is used for identify the target on which the counter would be cleared. The target is encoded as: Byte 1: reserved Byte 2~3: reserved Byte 4: reserved Byte 5~11:each octet specifies a set of eight ports, with the first octet specifying ports 1 through 8, etc.
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: counterClearTarget
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"counterClearTarget",
"OBJECT-TYPE",
"SYNTAX",
"OCTET",
"STRING",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"This managed object is used for identify the target on which the counter would be cleared. The target is encoded as: Byte 1: reserved Byte 2~3: reserved Byte 4: reserved Byte 5~11:each octet specifies a set of eight ports, with the first octet specifying ports 1 through 8, etc.\"",
"::=",
"{",
"clear",
"1",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"OCTET STRING"
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"This managed object is used for identify the target on which the counter would be cleared. The target is encoded as: Byte 1: reserved Byte 2~3: reserved Byte 4: reserved Byte 5~11:each octet specifies a set of eight ports, with the first octet specifying ports 1 through 8, etc."
],
null,
null,
null,
null
]
}Vendor MIB copy from the LibreNMS archive.
Module: E5-110-MIB
See published definition above
{'SNMPv2-TC': ['RowStatus', 'TEXTUAL-CONVENTION'], 'BRIDGE-MIB': ['MacAddress', 'Timeout', 'BridgeId', 'dot1dBasePort'], 'SNMPv2-SMI': ['OBJECT-TYPE', 'Counter32', 'Gauge32', 'Unsigned32', 'Counter64', 'IpAddress', 'TimeTicks', 'NOTIFICATION-TYPE'], 'RFC1155-SMI': ['enterprises'], 'RFC1213-MIB': ['DisplayString', 'PhysAddress', 'ifIndex'], 'P-BRIDGE-MIB': ['dot1dTrafficClass'], 'Q-BRIDGE-MIB': ['VlanIndex', 'PortList', 'dot1qVlanIndex']}Related source files and packages:
Same file in Observium Community.
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.6321.1.2.3.1.14.2 | counterClearOps | 0 | 0 | |
| 1.3.6.1.4.1.6321.1.2.3.1.14.3 | counterClearVpi | 0 | 0 | |
| 1.3.6.1.4.1.6321.1.2.3.1.14.4 | counterClearVci | 0 | 0 |