OID reference
1.3.6.1.4.1.8708.2.20.2.4.1.1.14
The Linux name of the PPP link, for example 'p1-1-1-1-2', where the first number indicates subrack, the second and third is slot and port number for the TX side. The fourth and fifth is slot and port for the RX side. This is the name that you will see and use in ::ip::route.
Identification
{1 3 6 1 4 1 8708 2 20 2 4 1 1 14}
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.
dcnPppRouteName OBJECT-TYPE
SYNTAX MgmtNameString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The Linux name of the PPP link, for example
'p1-1-1-1-2', where the first number indicates
subrack, the second and third is slot and port
number for the TX side. The fourth and fifth is
slot and port for the RX side.
This is the name that you will see and use in
::ip::route.
"
::= { dcnPppEntry 14 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
The Linux name of the PPP link, for example 'p1-1-1-1-2', where the first number indicates subrack, the second and third is slot and port number for the TX side. The fourth and fifth is slot and port for the RX side. This is the name that you will see and use in ::ip::route.
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: dcnPppRouteName
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"dcnPppRouteName",
"OBJECT-TYPE",
"SYNTAX",
"MgmtNameString",
"MAX-ACCESS",
"read-only",
"STATUS",
"current",
"DESCRIPTION",
"\"The Linux name of the PPP link, for example 'p1-1-1-1-2', where the first number indicates subrack, the second and third is slot and port number for the TX side. The fourth and fifth is slot and port for the RX side. This is the name that you will see and use in ::ip::route. \"",
"::=",
"{",
"dcnPppEntry",
"14",
"}"
],
"syntax_tree": [
[
"row",
"MgmtNameString"
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The Linux name of the PPP link, for example 'p1-1-1-1-2', where the first number indicates subrack, the second and third is slot and port number for the TX side. The fourth and fifth is slot and port for the RX side. This is the name that you will see and use in ::ip::route."
],
null,
null,
null,
null
]
}Vendor MIB copy from the Observium Community archive.
Module: LUM-DCN-MIB
See published definition above
{'LUM-TC': ['FaultStatus', 'MgmtNameString', 'SubrackNumber', 'SlotNumber', 'PortNumber', 'BoardOrInterfaceOperStatus', 'BoardOrInterfaceAdminStatus', 'CommandString', 'LambdaFrequency', 'ObjectProperty'], 'LUM-REG': ['lumModules', 'lumDcnMIB'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'DisplayString', 'DateAndTime'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Unsigned32', 'Counter32', 'IpAddress', 'NOTIFICATION-TYPE', 'Gauge32', 'Integer32'], 'SNMPv2-CONF': ['OBJECT-GROUP', 'MODULE-COMPLIANCE', 'NOTIFICATION-GROUP']}Related source files and packages:
Registration