OID reference
1.3.6.1.4.1.11.2.48.54.2.1.1
An administratively assigned Priority, which will be used for all traffic on the voice vlan, this gives the packets the requested priority (CoS) within the bridge.
Identification
{1 3 6 1 4 1 11 2 48 54 2 1 1}
At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition. The index encoding is not inferred here.
Published row index: dot1qVlanIndex.
snmpwalk [connection options] DEVICE .1.3.6.1.4.1.11.2.48.54.2.1.1
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.
vlanVoicePriority OBJECT-TYPE
SYNTAX INTEGER (0..7)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"An administratively assigned Priority, which will be used
for all traffic on the voice vlan, this gives the packets
the requested priority (CoS) within the bridge."
DEFVAL{ 6 }
::= { vlanVoiceEntry 1 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
An administratively assigned Priority, which will be used for all traffic on the voice vlan, this gives the packets the requested priority (CoS) within the bridge.
HPE networking MIB copies (LibreNMS/Observium Community)HPE Instant On official MIBs
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: vlanVoicePriority
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"vlanVoicePriority",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"(",
"0",
".",
".",
"7",
")",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"An administratively assigned Priority, which will be used for all traffic on the voice vlan, this gives the packets the requested priority (CoS) within the bridge.\"",
"DEFVAL",
"{",
"6",
"}",
"::=",
"{",
"vlanVoiceEntry",
"1",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"integerSubType",
[
[
0,
7
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"An administratively assigned Priority, which will be used for all traffic on the voice vlan, this gives the packets the requested priority (CoS) within the bridge."
],
null,
null,
null,
[
"DEFVAL",
6
]
]
}Module: HPE-vlan-MIB
See published definition above
{'IF-MIB': ['ifIndex'], 'HPE-MIB': ['nm'], 'SNMPv2-TC': ['DisplayString', 'TruthValue', 'RowStatus', 'MacAddress'], 'BRIDGE-MIB': ['dot1dBasePort'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'IpAddress'], 'Q-BRIDGE-MIB': ['VlanIndex', 'dot1qVlanIndex', 'PortList'], 'INET-ADDRESS-MIB': ['InetAddressType'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString'], 'HPE-BRIDGEMIBOBJECTS-MIB': ['VlanList1', 'VlanList2', 'VlanList3', 'VlanList4']}Same file in HPE Instant On 1960 2.6.0.73.
Same file in HPE Instant On 1830 2.5.0.48.
Same file in HPE Instant On 1960 2.7.0.103.
Same file in HPE Instant On 1930 2.6.0.73.
Vendor MIB copy from the Observium Community archive. HPE networking support.
Module: HPE-vlan-MIB
{'IF-MIB': ['ifIndex'], 'HPE-MIB': ['nm'], 'SNMPv2-TC': ['DisplayString', 'TruthValue', 'RowStatus', 'MacAddress'], 'BRIDGE-MIB': ['dot1dBasePort'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'IpAddress'], 'Q-BRIDGE-MIB': ['VlanIndex', 'dot1qVlanIndex', 'PortList'], 'INET-ADDRESS-MIB': ['InetAddressType'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString'], 'HPE-BRIDGEMIBOBJECTS-MIB': ['VlanList1', 'VlanList2', 'VlanList3', 'VlanList4']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.11.2.48.54.2.1.2 | vlanVoicePriorityRemark | 0 | 0 | |
| 1.3.6.1.4.1.11.2.48.54.2.1.3 | vlanVoiceRowStatus | 0 | 0 |