OID reference
1.3.6.1.4.1.8708.2.32.2.26.1.1.10
The direction towards the Ring Protection Link (RPL) and the role of the node. For the owner the RPL is situated on the chosen port while for the neighbour the specified port is connected to the RPL owner (neighbour only valid for ERP V2).
Identification
{1 3 6 1 4 1 8708 2 32 2 26 1 1 10}
| Value | Name |
|---|---|
| 1 | none |
| 2 | left |
| 3 | right |
| 4 | leftNeighbour |
| 5 | rightNeighbour |
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: mesErpIndex.
snmpwalk [connection options] DEVICE .1.3.6.1.4.1.8708.2.32.2.26.1.1.10
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.
mesErpProtLink OBJECT-TYPE
SYNTAX INTEGER {
none (1),
left (2),
right (3),
leftNeighbour (4),
rightNeighbour (5) }
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The direction towards the Ring Protection Link (RPL) and the role of the node.
For the owner the RPL is situated on the chosen port while for the neighbour the
specified port is connected to the RPL owner (neighbour only valid for ERP V2).
"
DEFVAL { none }
::= { mesErpEntry 10 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
The direction towards the Ring Protection Link (RPL) and the role of the node. For the owner the RPL is situated on the chosen port while for the neighbour the specified port is connected to the RPL owner (neighbour only valid for ERP V2).
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: mesErpProtLink
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"mesErpProtLink",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"none",
"(",
"1",
")",
",",
"left",
"(",
"2",
")",
",",
"right",
"(",
"3",
")",
",",
"leftNeighbour",
"(",
"4",
")",
",",
"rightNeighbour",
"(",
"5",
")",
"}",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"The direction towards the Ring Protection Link (RPL) and the role of the node. For the owner the RPL is situated on the chosen port while for the neighbour the specified port is connected to the RPL owner (neighbour only valid for ERP V2). \"",
"DEFVAL",
"{",
"none",
"}",
"::=",
"{",
"mesErpEntry",
"10",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"none",
1
],
[
"left",
2
],
[
"right",
3
],
[
"leftNeighbour",
4
],
[
"rightNeighbour",
5
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The direction towards the Ring Protection Link (RPL) and the role of the node. For the owner the RPL is situated on the chosen port while for the neighbour the specified port is connected to the RPL owner (neighbour only valid for ERP V2)."
],
null,
null,
null,
[
"DEFVAL",
"none"
]
]
}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