OID reference
1.3.6.1.4.1.5504.4.5.2.1.7
The number used in Magic Number negotiation. Magic number negotiation must be enabled using pppLinkConfigMagicNumber in RFC1471. When set to zero, a random number will be used for the magic number. This allows us to better prevent having two devices with the same magic number.
Identification
{1 3 6 1 4 1 5504 4 5 2 1 7}
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 AUGMENTS row: pppInterfaceEntry. Check that row's index definition for the instance suffix.
snmpwalk [connection options] DEVICE .1.3.6.1.4.1.5504.4.5.2.1.7
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.
lcpExtMagicNumber OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The number used in Magic Number negotiation. Magic
number negotiation must be enabled using
pppLinkConfigMagicNumber in RFC1471.
When set to zero, a random number will be used for
the magic number. This allows us to better prevent
having two devices with the same magic number."
REFERENCE
"See rfc1471.mib: pppLinkConfigMagicNumber
From RFC 1661:
'This Configuration Option provides a method to detect
looped-back links and other Data Link Layer anomalies.
This Configuration Option MAY be required by some other
Configuration Options such as the Quality-Protocol
Configuration Option. By default, the Magic-Number is
not negotiated, and zero is inserted where a Magic-Number
might otherwise be used.'"
DEFVAL { 0 }
::= { pppLCPExtensionsEntry 7 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
The number used in Magic Number negotiation. Magic number negotiation must be enabled using pppLinkConfigMagicNumber in RFC1471. When set to zero, a random number will be used for the magic number. This allows us to better prevent having two devices with the same magic number.
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: lcpExtMagicNumber
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"lcpExtMagicNumber",
"OBJECT-TYPE",
"SYNTAX",
"Unsigned32",
"MAX-ACCESS",
"read-create",
"STATUS",
"current",
"DESCRIPTION",
"\"The number used in Magic Number negotiation. Magic number negotiation must be enabled using pppLinkConfigMagicNumber in RFC1471. When set to zero, a random number will be used for the magic number. This allows us to better prevent having two devices with the same magic number.\"",
"REFERENCE",
"\"See rfc1471.mib: pppLinkConfigMagicNumber From RFC 1661: 'This Configuration Option provides a method to detect looped-back links and other Data Link Layer anomalies. This Configuration Option MAY be required by some other Configuration Options such as the Quality-Protocol Configuration Option. By default, the Magic-Number is not negotiated, and zero is inserted where a Magic-Number might otherwise be used.'\"",
"DEFVAL",
"{",
"0",
"}",
"::=",
"{",
"pppLCPExtensionsEntry",
"7",
"}"
],
"syntax_tree": [
[
"ApplicationSyntax",
"Unsigned32"
],
null,
[
"MaxAccessPart",
"read-create"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The number used in Magic Number negotiation. Magic number negotiation must be enabled using pppLinkConfigMagicNumber in RFC1471. When set to zero, a random number will be used for the magic number. This allows us to better prevent having two devices with the same magic number."
],
[
"REFERENCE",
"See rfc1471.mib: pppLinkConfigMagicNumber From RFC 1661: 'This Configuration Option provides a method to detect looped-back links and other Data Link Layer anomalies. This Configuration Option MAY be required by some other Configuration Options such as the Quality-Protocol Configuration Option. By default, the Magic-Number is not negotiated, and zero is inserted where a Magic-Number might otherwise be used.'"
],
null,
null,
[
"DEFVAL",
0
]
]
}Vendor MIB copy from the Observium Community archive.
Module: ZHONE-COM-PPP-MIB
See published definition above
{'Zhone': ['zhonePpp', 'zhoneModules'], 'IF-MIB': ['ifIndex', 'InterfaceIndex', 'InterfaceIndexOrZero'], 'Zhone-TC': ['ZhoneRowStatus'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION'], 'ATM-TC-MIB': ['AtmVpIdentifier', 'AtmVcIdentifier'], 'SNMPv2-SMI': ['Integer32', 'Unsigned32', 'OBJECT-TYPE', 'MODULE-IDENTITY']}Related source files and packages:
Registration