OID reference
1.3.6.1.4.1.8708.2.27.2.5.1.1.2
The management name of the Lanes, e.g. Lane:1:2:1:4 where the first number indicates sub-rack, the second slot number and the third is the interface number. The last number is the lane id within the Client frame.
Identification
{1 3 6 1 4 1 8708 2 27 2 5 1 1 2}
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.
clientLanesName OBJECT-TYPE
SYNTAX MgmtNameString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The management name of the Lanes,
e.g. Lane:1:2:1:4 where the first number
indicates sub-rack, the second slot number and
the third is the interface number. The last
number is the lane id within the Client frame.
"
::= { clientLanesEntry 2 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
The management name of the Lanes, e.g. Lane:1:2:1:4 where the first number indicates sub-rack, the second slot number and the third is the interface number. The last number is the lane id within the Client frame.
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: clientLanesName
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"clientLanesName",
"OBJECT-TYPE",
"SYNTAX",
"MgmtNameString",
"MAX-ACCESS",
"read-create",
"STATUS",
"current",
"DESCRIPTION",
"\"The management name of the Lanes, e.g. Lane:1:2:1:4 where the first number indicates sub-rack, the second slot number and the third is the interface number. The last number is the lane id within the Client frame. \"",
"::=",
"{",
"clientLanesEntry",
"2",
"}"
],
"syntax_tree": [
[
"row",
"MgmtNameString"
],
null,
[
"MaxAccessPart",
"read-create"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The management name of the Lanes, e.g. Lane:1:2:1:4 where the first number indicates sub-rack, the second slot number and the third is the interface number. The last number is the lane id within the Client frame."
],
null,
null,
null,
null
]
}Vendor MIB copy from the Observium Community archive.
Module: LUM-CLIENT-MIB
See published definition above
{'LUM-TC': ['FaultStatus', 'MgmtNameString', 'SubrackNumber', 'SlotNumber', 'PortNumber', 'BoardOrInterfaceOperStatus', 'BoardOrInterfaceAdminStatus', 'CommandString', 'LambdaFrequency', 'SignalFormat', 'TrxMedia', 'ObjectProperty', 'BerLevelMTOSI', 'OpticalLayerMappingType', 'LaneFrequency', 'TrxRxState', 'TrxTxState', 'PhysicalLayerMappingType', 'SignalDirection', 'SignalStatusWithNA', 'EnableDisable', 'OnOff', 'InterfaceType'], 'LUM-REG': ['lumModules', 'lumClientMIB'], 'SNMPv2-TC': ['DisplayString', 'DateAndTime'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Unsigned32', 'Integer32', 'NOTIFICATION-TYPE', 'Gauge32'], 'SNMPv2-CONF': ['OBJECT-GROUP', 'MODULE-COMPLIANCE', 'NOTIFICATION-GROUP']}Related source files and packages:
Registration