OID reference
1.3.6.1.4.1.8708.2.20.2.4.1.1.17
This attribute is settable only on ppp links terminated on a specific type of boards. Namely, traffic units that may terminate more than one ppp-link. The tricky part is that the ppp-link object in the node at the other end, must have the same ID configured. For PPP over OSC, -1 is allowed as a do-not-use value.
Identification
{1 3 6 1 4 1 8708 2 20 2 4 1 1 17}
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: dcnPppIndex.
snmpwalk [connection options] DEVICE .1.3.6.1.4.1.8708.2.20.2.4.1.1.17
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.
dcnPppLogicalLinkId OBJECT-TYPE
SYNTAX Integer32 (-1..11)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This attribute is settable only on ppp links
terminated on a specific type of boards.
Namely, traffic units that may terminate more
than one ppp-link.
The tricky part is that the ppp-link
object in the node at the other end, must
have the same ID configured.
For PPP over OSC, -1 is allowed as a
do-not-use value.
"
DEFVAL { 0 }
::= { dcnPppEntry 17 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
This attribute is settable only on ppp links terminated on a specific type of boards. Namely, traffic units that may terminate more than one ppp-link. The tricky part is that the ppp-link object in the node at the other end, must have the same ID configured. For PPP over OSC, -1 is allowed as a do-not-use value.
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: dcnPppLogicalLinkId
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"dcnPppLogicalLinkId",
"OBJECT-TYPE",
"SYNTAX",
"Integer32",
"(",
"-",
"1",
".",
".",
"11",
")",
"MAX-ACCESS",
"read-create",
"STATUS",
"current",
"DESCRIPTION",
"\"This attribute is settable only on ppp links terminated on a specific type of boards. Namely, traffic units that may terminate more than one ppp-link. The tricky part is that the ppp-link object in the node at the other end, must have the same ID configured. For PPP over OSC, -1 is allowed as a do-not-use value. \"",
"DEFVAL",
"{",
"0",
"}",
"::=",
"{",
"dcnPppEntry",
"17",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"Integer32",
[
"integerSubType",
[
[
-1,
11
]
]
]
],
null,
[
"MaxAccessPart",
"read-create"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"This attribute is settable only on ppp links terminated on a specific type of boards. Namely, traffic units that may terminate more than one ppp-link. The tricky part is that the ppp-link object in the node at the other end, must have the same ID configured. For PPP over OSC, -1 is allowed as a do-not-use value."
],
null,
null,
null,
[
"DEFVAL",
0
]
]
}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