Ring ID for the ERPv2 instance. All ERP instances must have the same ring ID throughout the ERP ring.
Sources for this description
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
OID reference
1.3.6.1.4.1.8708.2.32.2.26.1.1.31
Ring ID for the ERPv2 instance. All ERP instances must have the same ring ID throughout the ERP ring.
Identification
{1 3 6 1 4 1 8708 2 32 2 26 1 1 31}
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.31
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.
mesErpRingId OBJECT-TYPE
SYNTAX Unsigned32 (1..239)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Ring ID for the ERPv2 instance. All ERP instances
must have the same ring ID throughout the ERP ring.
"
DEFVAL { 1 }
::= { mesErpEntry 31 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Ring ID for the ERPv2 instance. All ERP instances must have the same ring ID throughout the ERP ring.
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: mesErpRingId
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"mesErpRingId",
"OBJECT-TYPE",
"SYNTAX",
"Unsigned32",
"(",
"1",
".",
".",
"239",
")",
"MAX-ACCESS",
"read-create",
"STATUS",
"current",
"DESCRIPTION",
"\"Ring ID for the ERPv2 instance. All ERP instances must have the same ring ID throughout the ERP ring. \"",
"DEFVAL",
"{",
"1",
"}",
"::=",
"{",
"mesErpEntry",
"31",
"}"
],
"syntax_tree": [
[
"ApplicationSyntax",
"Unsigned32",
[
"integerSubType",
[
[
1,
239
]
]
]
],
null,
[
"MaxAccessPart",
"read-create"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Ring ID for the ERPv2 instance. All ERP instances must have the same ring ID throughout the ERP ring."
],
null,
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