OID reference
1.3.6.1.4.1.6321.1.2.3.4.8.14.2.2
The managed object is for VoIP configuration. When the EMS wants to issue the desired operation, the EMS shall send SNMP-SET message to set the corresponding bit value to be 1. The various bit positions are: BIT 1: enable port BIT 2: disable port
Identification
{1 3 6 1 4 1 6321 1 2 3 4 8 14 2 2}
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.4.8.14.2.2.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.
voipPortOps OBJECT-TYPE
SYNTAX INTEGER
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The managed object is for VoIP configuration. When the EMS
wants to issue the desired operation, the EMS shall send SNMP-SET message to set
the corresponding bit value to be 1. The various bit positions are:
BIT 1: enable port
BIT 2: disable port"
::= { portOperations 2 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
The managed object is for VoIP configuration. When the EMS wants to issue the desired operation, the EMS shall send SNMP-SET message to set the corresponding bit value to be 1. The various bit positions are: BIT 1: enable port BIT 2: disable port
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: voipPortOps
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"voipPortOps",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"The managed object is for VoIP configuration. When the EMS wants to issue the desired operation, the EMS shall send SNMP-SET message to set the corresponding bit value to be 1. The various bit positions are: BIT 1: enable port BIT 2: disable port\"",
"::=",
"{",
"portOperations",
"2",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER"
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The managed object is for VoIP configuration. When the EMS wants to issue the desired operation, the EMS shall send SNMP-SET message to set the corresponding bit value to be 1. The various bit positions are: BIT 1: enable port BIT 2: disable port"
],
null,
null,
null,
null
]
}Vendor MIB copy from the LibreNMS archive.
Module: E5-121-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'], 'IEEE8021-CFMD8-MIB': ['dot1agCfmMdIndex', 'dot1agCfmMaIndex', 'dot1agCfmMepIdentifier']}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.4.8.14.2.1 | voipPortTarget | 0 | 0 |