OID reference
1.3.6.1.4.1.4935.15.20.1.2.15.2
IEEE 802.1Q Virtual LAN ID. This is the VID to be applied in the TCI field when tagging is enabled. The value 1 is the default Port VID (PVID) for bridge port. The 4095 VID (0xFFF) is reserved for implementation use and it shall not be used in tag header. NOTE: As per standard, some bridges may not support the full ra…
Identification
{1 3 6 1 4 1 4935 15 20 1 2 15 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.4935.15.20.1.2.15.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.
qosVlanIeee8021qVirtualLanID OBJECT-TYPE
SYNTAX Unsigned32 (0..4095)
MAX-ACCESS read-write
STATUS current
DESCRIPTION "IEEE 802.1Q Virtual LAN ID. This is the VID to
be applied in the TCI field when tagging is enabled.
The value 1 is the default Port VID (PVID) for bridge
port. The 4095 VID (0xFFF) is reserved for implementation
use and it shall not be used in tag header.
NOTE: As per standard, some bridges may not support
the full range of VID."
DEFVAL { 1 }
::= { qosVlanIeee8021q 2 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
IEEE 802.1Q Virtual LAN ID. This is the VID to be applied in the TCI field when tagging is enabled. The value 1 is the default Port VID (PVID) for bridge port. The 4095 VID (0xFFF) is reserved for implementation use and it shall not be used in tag header. NOTE: As per standard, some bridges may not support the full range of VID.
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: qosVlanIeee8021qVirtualLanID
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"qosVlanIeee8021qVirtualLanID",
"OBJECT-TYPE",
"SYNTAX",
"Unsigned32",
"(",
"0",
".",
".",
"4095",
")",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"IEEE 802.1Q Virtual LAN ID. This is the VID to be applied in the TCI field when tagging is enabled. The value 1 is the default Port VID (PVID) for bridge port. The 4095 VID (0xFFF) is reserved for implementation use and it shall not be used in tag header. NOTE: As per standard, some bridges may not support the full range of VID.\"",
"DEFVAL",
"{",
"1",
"}",
"::=",
"{",
"qosVlanIeee8021q",
"2",
"}"
],
"syntax_tree": [
[
"ApplicationSyntax",
"Unsigned32",
[
"integerSubType",
[
[
0,
4095
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"IEEE 802.1Q Virtual LAN ID. This is the VID to be applied in the TCI field when tagging is enabled. The value 1 is the default Port VID (PVID) for bridge port. The 4095 VID (0xFFF) is reserved for implementation use and it shall not be used in tag header. NOTE: As per standard, some bridges may not support the full range of VID."
],
null,
null,
null,
[
"DEFVAL",
1
]
]
}Vendor MIB copy from the Observium Community archive.
Module: MX-QOS-MIB
See published definition above
{'MX-TC': ['MxEnableState'], 'MX-SMI': ['mediatrixConfig'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Unsigned32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.4935.15.20.1.2.15.1 | qosVlanIeee8021qTaggingEnable | 0 | 0 | |
| 1.3.6.1.4.1.4935.15.20.1.2.15.3 | qosVlanIeee8021qDefaultUserPriority | 0 | 0 |