OID reference
1.3.6.1.4.1.5504.4.5.2.1.8
The number of padded bytes at the end of data. This is used for Self-Describing Padding, a method for placing unambiguous padding octets at the end of the PPP Information field in order to cause messages to fall on a natural boundary.
Identification
{1 3 6 1 4 1 5504 4 5 2 1 8}
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.8
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.
lcpExtMaxPad OBJECT-TYPE
SYNTAX Integer32 (1..255)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The number of padded bytes at the end of data. This is
used for Self-Describing Padding, a method for placing
unambiguous padding octets at the end of the PPP Information
field in order to cause messages to fall on a natural boundary."
REFERENCE
"See Self-Describing Padding in RFC 1570."
DEFVAL { 4 }
::= { pppLCPExtensionsEntry 8 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
The number of padded bytes at the end of data. This is used for Self-Describing Padding, a method for placing unambiguous padding octets at the end of the PPP Information field in order to cause messages to fall on a natural boundary.
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: lcpExtMaxPad
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"lcpExtMaxPad",
"OBJECT-TYPE",
"SYNTAX",
"Integer32",
"(",
"1",
".",
".",
"255",
")",
"MAX-ACCESS",
"read-create",
"STATUS",
"current",
"DESCRIPTION",
"\"The number of padded bytes at the end of data. This is used for Self-Describing Padding, a method for placing unambiguous padding octets at the end of the PPP Information field in order to cause messages to fall on a natural boundary.\"",
"REFERENCE",
"\"See Self-Describing Padding in RFC 1570.\"",
"DEFVAL",
"{",
"4",
"}",
"::=",
"{",
"pppLCPExtensionsEntry",
"8",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"Integer32",
[
"integerSubType",
[
[
1,
255
]
]
]
],
null,
[
"MaxAccessPart",
"read-create"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The number of padded bytes at the end of data. This is used for Self-Describing Padding, a method for placing unambiguous padding octets at the end of the PPP Information field in order to cause messages to fall on a natural boundary."
],
[
"REFERENCE",
"See Self-Describing Padding in RFC 1570."
],
null,
null,
[
"DEFVAL",
4
]
]
}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