OID reference
1.3.6.1.4.1.34751.18.2.1.2.2.1.5
The maximum size message that this PEP is capable of receiving in bytes. A value of zero means that the maximum message size is unspecified (but does not mean it is unlimited). A message greater than this maximum results in a MessageTooBig error on a 'no commit' REP.
Identification
{1 3 6 1 4 1 34751 18 2 1 2 2 1 5}
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: qosDeviceAttributeId.
snmpwalk [connection options] DEVICE .1.3.6.1.4.1.34751.18.2.1.2.2.1.5
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.
qosDeviceMaxMessageSize OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum size message that this PEP is capable of
receiving in bytes. A value of zero means that the maximum
message size is unspecified (but does not mean it is
unlimited). A message greater than this maximum results in a
MessageTooBig error on a 'no commit' REP."
::= { qosDeviceAttributeEntry 5 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
The maximum size message that this PEP is capable of receiving in bytes. A value of zero means that the maximum message size is unspecified (but does not mean it is unlimited). A message greater than this maximum results in a MessageTooBig error on a 'no commit' REP.
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: qosDeviceMaxMessageSize
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"qosDeviceMaxMessageSize",
"OBJECT-TYPE",
"SYNTAX",
"Unsigned32",
"MAX-ACCESS",
"read-only",
"STATUS",
"current",
"DESCRIPTION",
"\"The maximum size message that this PEP is capable of receiving in bytes. A value of zero means that the maximum message size is unspecified (but does not mean it is unlimited). A message greater than this maximum results in a MessageTooBig error on a 'no commit' REP.\"",
"::=",
"{",
"qosDeviceAttributeEntry",
"5",
"}"
],
"syntax_tree": [
[
"ApplicationSyntax",
"Unsigned32"
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The maximum size message that this PEP is capable of receiving in bytes. A value of zero means that the maximum message size is unspecified (but does not mean it is unlimited). A message greater than this maximum results in a MessageTooBig error on a 'no commit' REP."
],
null,
null,
null,
null
]
}Vendor MIB copy from the Observium Community archive.
Module: QTECH-NMS-QOS-PIB-MIB
See published definition above
{'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'DisplayString', 'MacAddress', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Counter64', 'IpAddress'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP'], 'QTECH-NMS-TC': ['Unsigned32'], 'QTECH-NMS-SMI': ['nmsPibToMib']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.34751.18.2.1.2.2.1.1 | qosDeviceAttributeId | 0 | 0 | |
| 1.3.6.1.4.1.34751.18.2.1.2.2.1.2 | qosDevicePepDomain | 0 | 0 | |
| 1.3.6.1.4.1.34751.18.2.1.2.2.1.3 | qosDevicePrimaryPdp | 0 | 0 | |
| 1.3.6.1.4.1.34751.18.2.1.2.2.1.4 | qosDeviceSecondaryPdp | 0 | 0 | |
| 1.3.6.1.4.1.34751.18.2.1.2.2.1.6 | qosDeviceCapabilities | 0 | 0 |