OID reference
1.3.6.1.4.1.8708.2.32.2.12.1.1.14
Defines whether VLAN tagged frames are accepted. The port must be VLAN aware to understand tagged frames. Access ports (UNI) admit all frames (untagged and tagged), whereas trunk ports (NNI) admit only tagged frames. no - VLAN tagged frames are discarded. yes - VLAN tagged frames are accepted.
Identification
{1 3 6 1 4 1 8708 2 32 2 12 1 1 14}
| Value | Name |
|---|---|
| 1 | no |
| 2 | yes |
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: mesPortIndex.
snmpwalk [connection options] DEVICE .1.3.6.1.4.1.8708.2.32.2.12.1.1.14
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.
mesPortVlanTagged OBJECT-TYPE
SYNTAX INTEGER {
no (1),
yes (2) }
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Defines whether VLAN tagged frames are
accepted. The port must be VLAN aware to understand
tagged frames.
Access ports (UNI) admit all frames (untagged and
tagged), whereas trunk ports (NNI) admit only tagged
frames.
no - VLAN tagged frames are discarded.
yes - VLAN tagged frames are accepted.
"
DEFVAL { no }
::= { mesPortEntry 14 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Defines whether VLAN tagged frames are accepted. The port must be VLAN aware to understand tagged frames. Access ports (UNI) admit all frames (untagged and tagged), whereas trunk ports (NNI) admit only tagged frames. no - VLAN tagged frames are discarded. yes - VLAN tagged frames are accepted.
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: mesPortVlanTagged
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"mesPortVlanTagged",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"no",
"(",
"1",
")",
",",
"yes",
"(",
"2",
")",
"}",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"Defines whether VLAN tagged frames are accepted. The port must be VLAN aware to understand tagged frames. Access ports (UNI) admit all frames (untagged and tagged), whereas trunk ports (NNI) admit only tagged frames. no - VLAN tagged frames are discarded. yes - VLAN tagged frames are accepted. \"",
"DEFVAL",
"{",
"no",
"}",
"::=",
"{",
"mesPortEntry",
"14",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"no",
1
],
[
"yes",
2
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Defines whether VLAN tagged frames are accepted. The port must be VLAN aware to understand tagged frames. Access ports (UNI) admit all frames (untagged and tagged), whereas trunk ports (NNI) admit only tagged frames. no - VLAN tagged frames are discarded. yes - VLAN tagged frames are accepted."
],
null,
null,
null,
[
"DEFVAL",
"no"
]
]
}Vendor MIB copy from the Observium Community archive.
Module: LUM-MES-MIB
See published definition above
{'LUM-TC': ['MgmtNameString', 'SubrackNumber', 'SlotNumber', 'PortNumber', 'BoardOrInterfaceOperStatus', 'BoardOrInterfaceAdminStatus', 'ObjectProperty', 'CommandString', 'FaultStatus', 'ServiceIdWithNotUsed'], 'LUM-REG': ['lumModules', 'lumMesMIB'], 'SNMPv2-TC': ['DisplayString', 'DateAndTime', 'RowStatus', 'MacAddress', 'TEXTUAL-CONVENTION'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Unsigned32', 'Integer32', 'IpAddress', 'Counter64'], 'SNMPv2-CONF': ['OBJECT-GROUP', 'MODULE-COMPLIANCE']}Related source files and packages:
Registration