OID reference
1.3.6.1.4.1.6321.1.2.3.1.2.1
The manager sets the corresponding bit value to 1 to start the operation and the agent clears the object to zero when the operation is successfully completed. The various bit positions are: BIT 1: clear BIT 2: cutoff
Identification
{1 3 6 1 4 1 6321 1 2 3 1 2 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.2.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.
alarmOps OBJECT-TYPE
SYNTAX INTEGER
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The manager sets the corresponding bit value to 1 to start the operation
and the agent clears the object to zero when the operation is successfully completed.
The various bit positions are:
BIT 1: clear
BIT 2: cutoff"
::= { alarmconf 1 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
The manager sets the corresponding bit value to 1 to start the operation and the agent clears the object to zero when the operation is successfully completed. The various bit positions are: BIT 1: clear BIT 2: cutoff
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: alarmOps
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"alarmOps",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"The manager sets the corresponding bit value to 1 to start the operation and the agent clears the object to zero when the operation is successfully completed. The various bit positions are: BIT 1: clear BIT 2: cutoff\"",
"::=",
"{",
"alarmconf",
"1",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER"
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The manager sets the corresponding bit value to 1 to start the operation and the agent clears the object to zero when the operation is successfully completed. The various bit positions are: BIT 1: clear BIT 2: cutoff"
],
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.2.2 | alarmConfTable | 1 | 6 | |
| 1.3.6.1.4.1.6321.1.2.3.1.2.3 | alarmCurrTable | 1 | 15 | |
| 1.3.6.1.4.1.6321.1.2.3.1.2.4 | alarmSeverityPortTable | 1 | 2 |