OID reference
1.3.6.1.4.1.72.14.32.3.1.1.5
The Max-Slot-Id parameter that the remote node has advertised and that is in use on the link. If vj-tcp header compression is not in use on the link then the value of this object shall be 0.
Identification
{1 3 6 1 4 1 72 14 32 3 1 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.
In RETIX-RX7000-MIB, the row index pppIpIndex is declared as INTEGER. A non-negative index value is encoded as one numeric subidentifier. An instance has the form .1.3.6.1.4.1.72.14.32.3.1.1.5.<pppIpIndex>. Use an index value actually present on the device and permitted by its MIB. Other definitions can differ.
snmpwalk [connection options] DEVICE .1.3.6.1.4.1.72.14.32.3.1.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.
pppIpRemoteMaxSlotId OBJECT-TYPE
SYNTAX INTEGER(0..255)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The Max-Slot-Id parameter that the remote node
has advertised and that is in use on the link.
If vj-tcp header compression is not in use on
the link then the value of this object shall be
0."
::= { pppIpEntry 5 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
The Max-Slot-Id parameter that the remote node has advertised and that is in use on the link. If vj-tcp header compression is not in use on the link then the value of this object shall be 0.
Retix RX7000 MIB in the historical IETF archive
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: mandatory.
Names: pppIpRemoteMaxSlotId
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"pppIpRemoteMaxSlotId",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"(",
"0",
".",
".",
"255",
")",
"ACCESS",
"read-only",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"The Max-Slot-Id parameter that the remote node has advertised and that is in use on the link. If vj-tcp header compression is not in use on the link then the value of this object shall be 0.\"",
"::=",
"{",
"pppIpEntry",
"5",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"integerSubType",
[
[
0,
255
]
]
]
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"The Max-Slot-Id parameter that the remote node has advertised and that is in use on the link. If vj-tcp header compression is not in use on the link then the value of this object shall be 0."
],
null,
null,
null,
null
]
}Module: RETIX-RX7000-MIB
See published definition above
{'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['mgmt', 'experimental', 'NetworkAddress', 'IpAddress', 'Counter', 'Gauge', 'TimeTicks']}Source data warning: This is a historical Retix version 3.2 MIB dated 26 July 1995, preserved in a mirror of the IETF private MIB archive. It covers the product and software releases named in the file; the archive does not make it an IETF standard. The author states that the file includes draft MIBs. Its enterprises symbol is used without an IMPORTS declaration; its standard value is supplied from RFC 1155 for this exact reviewed file only.
· Download Retix RX7000 MIB version 3.2 — historical IETF archiveRelated source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.72.14.32.3.1.1.1 | pppIpIndex | 0 | 0 | |
| 1.3.6.1.4.1.72.14.32.3.1.1.2 | pppIpOperStatus | 0 | 0 | |
| 1.3.6.1.4.1.72.14.32.3.1.1.3 | pppIpLocalToRemoteCompressionProtocol | 0 | 0 | |
| 1.3.6.1.4.1.72.14.32.3.1.1.4 | pppIpRemoteToLocalCompressionProtocol | 0 | 0 | |
| 1.3.6.1.4.1.72.14.32.3.1.1.6 | pppIpLocalMaxSlotId | 0 | 0 |