OID reference
1.3.6.1.4.1.8708.2.32.2.25.1.1.8
An integer indicating the Primary VID of the MEP, always one of the VIDs assigned to the MA of the MEP. The value 0 indicates that either the Primary VID is that of the MEP's MA, or that the MEP's MA is associated with no VID. This attribute can be written via SNMP.
Identification
{1 3 6 1 4 1 8708 2 32 2 25 1 1 8}
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: mesCfmMepIndex.
snmpwalk [connection options] DEVICE .1.3.6.1.4.1.8708.2.32.2.25.1.1.8
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.
mesCfmMepPrimaryVid OBJECT-TYPE
SYNTAX Unsigned32 (0..4094)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"An integer indicating the Primary VID of the MEP,
always one of the VIDs assigned to the MA of the
MEP. The value 0 indicates that either the Primary
VID is that of the MEP's MA, or that the MEP's MA is
associated with no VID.
This attribute can be written via SNMP.
"
REFERENCE
"802.1ag clause 12.14.7.3.2:e"
DEFVAL { 1 }
::= { mesCfmMepEntry 8 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
An integer indicating the Primary VID of the MEP, always one of the VIDs assigned to the MA of the MEP. The value 0 indicates that either the Primary VID is that of the MEP's MA, or that the MEP's MA is associated with no VID. This attribute can be written via SNMP.
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: mesCfmMepPrimaryVid
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"mesCfmMepPrimaryVid",
"OBJECT-TYPE",
"SYNTAX",
"Unsigned32",
"(",
"0",
".",
".",
"4094",
")",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"An integer indicating the Primary VID of the MEP, always one of the VIDs assigned to the MA of the MEP. The value 0 indicates that either the Primary VID is that of the MEP's MA, or that the MEP's MA is associated with no VID. This attribute can be written via SNMP. \"",
"REFERENCE",
"\"802.1ag clause 12.14.7.3.2:e\"",
"DEFVAL",
"{",
"1",
"}",
"::=",
"{",
"mesCfmMepEntry",
"8",
"}"
],
"syntax_tree": [
[
"ApplicationSyntax",
"Unsigned32",
[
"integerSubType",
[
[
0,
4094
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"An integer indicating the Primary VID of the MEP, always one of the VIDs assigned to the MA of the MEP. The value 0 indicates that either the Primary VID is that of the MEP's MA, or that the MEP's MA is associated with no VID. This attribute can be written via SNMP."
],
[
"REFERENCE",
"802.1ag clause 12.14.7.3.2:e"
],
null,
null,
[
"DEFVAL",
1
]
]
}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