OID reference
1.3.6.1.4.1.8708.2.32.2.2.1.1.18
Defines whether all CE-VLAN IDs will be mapped to the same EVC. no - Different CE-VLAN IDs may be mapped to different EVCs. yes - All CE-VLAN IDs will be mapped to the same EVC.
Identification
{1 3 6 1 4 1 8708 2 32 2 2 1 1 18}
| 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: mesUniIndex.
snmpwalk [connection options] DEVICE .1.3.6.1.4.1.8708.2.32.2.2.1.1.18
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.
mesUniAllToOneBundling OBJECT-TYPE
SYNTAX INTEGER {
no (1),
yes (2) }
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Defines whether all CE-VLAN IDs will be mapped to
the same EVC.
no - Different CE-VLAN IDs may be mapped to
different EVCs.
yes - All CE-VLAN IDs will be mapped to the same
EVC.
"
DEFVAL { yes }
::= { mesUniEntry 18 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Defines whether all CE-VLAN IDs will be mapped to the same EVC. no - Different CE-VLAN IDs may be mapped to different EVCs. yes - All CE-VLAN IDs will be mapped to the same EVC.
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: mesUniAllToOneBundling
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"mesUniAllToOneBundling",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"no",
"(",
"1",
")",
",",
"yes",
"(",
"2",
")",
"}",
"MAX-ACCESS",
"read-create",
"STATUS",
"current",
"DESCRIPTION",
"\"Defines whether all CE-VLAN IDs will be mapped to the same EVC. no - Different CE-VLAN IDs may be mapped to different EVCs. yes - All CE-VLAN IDs will be mapped to the same EVC. \"",
"DEFVAL",
"{",
"yes",
"}",
"::=",
"{",
"mesUniEntry",
"18",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"no",
1
],
[
"yes",
2
]
]
]
],
null,
[
"MaxAccessPart",
"read-create"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Defines whether all CE-VLAN IDs will be mapped to the same EVC. no - Different CE-VLAN IDs may be mapped to different EVCs. yes - All CE-VLAN IDs will be mapped to the same EVC."
],
null,
null,
null,
[
"DEFVAL",
"yes"
]
]
}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