What this node believes is the MRU for the node on the
other end of the link. See section 2.1, page 2, 'Maximum
Receive Unit' of RFC 1172. Changing this object will
immediately cause the local node to use the new MRU when
transmitting packets. If this number is increased, then
the sender MAY elect to use the new MRU. If the MRU is
decreased then the sender MUST use the new MRU.
Parsed from file ibm6611.mib.txt
Company: None
Module: IBM6611-MIB
What this node believes is the MRU for the node on the
other end of the link. See section 2.1, page 2, 'Maximum
Receive Unit' of RFC 1172. Changing this object will
immediately cause the local node to use the new MRU when
transmitting packets. If this number is increased, then
the sender MAY elect to use the new MRU. If the MRU is
decreased then the sender MUST use the new MRU.
Parsed from file IBM6611-MIB.mib
Module: IBM6611-MIB
Vendor: IBM
Module: IBM6611-MIB
[Automatically extracted from oidview.com]
ibmpppLinkRemoteMRU OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "What this node believes is the MRU for the node on the other end of the link. See section 2.1, page 2, 'Maximum Receive Unit' of RFC 1172. Changing this object will immediately cause the local node to use the new MRU when transmitting packets. If this number is increased, then the sender MAY elect to use the new MRU. If the MRU is decreased then the sender MUST use the new MRU." ::= { ibmpppLinkControlEntry 6 }
ibmpppLinkRemoteMRU OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "What this node believes is the MRU for the node on the other end of the link. See section 2.1, page 2, 'Maximum Receive Unit' of RFC 1172. Changing this object will immediately cause the local node to use the new MRU when transmitting packets. If this number is increased, then the sender MAY elect to use the new MRU. If the MRU is decreased then the sender MUST use the new MRU." ::= { ibmpppLinkControlEntry 6 }
OID | Name | Sub children | Sub Nodes Total | Description |
---|---|---|---|---|
1.3.6.1.4.1.2.6.2.10.1.1.1 | ibmpppLinkControlIndex | 0 | 0 | A unique value for each PPP link. Its value ranges between 1 and the value of ifNumber. The interface identified by a particular … |
1.3.6.1.4.1.2.6.2.10.1.1.2 | ibmpppLinkCRCSize | 0 | 0 | Number of bits used in the CRC on this link. See section 3.1, 'Frame Check Sequence (FCS) Field' on page 5 of RFC 1171. Setting… |
1.3.6.1.4.1.2.6.2.10.1.1.3 | ibmpppLinkRestartTimerValue | 0 | 0 | The value used for the Restart Timer. It is in units of hundredths of a second. See section 4.3, 'Timers and Counters' on page 2… |
1.3.6.1.4.1.2.6.2.10.1.1.4 | ibmpppLinkMaxRestarts | 0 | 0 | The Max-Restarts parameter described in section 4.3, 'Timers and Counters' on page 20 of RFC 1171. |
1.3.6.1.4.1.2.6.2.10.1.1.5 | ibmpppLinkLocalMRU | 0 | 0 | The MRU (Maximum Receive Unit) of this node on the link. See section 2.1, page 2, 'Maximum Receive Unit' of RFC 1172. Changing t… |
1.3.6.1.4.1.2.6.2.10.1.1.7 | ibmpppLinkLocalACCMap | 0 | 0 | The (ACC) Asynchronous-Control-Character-Map for this node. This is the ACC Map that the node on the other end of the link will … |
1.3.6.1.4.1.2.6.2.10.1.1.8 | ibmpppLinkRemoteACCMap | 0 | 0 | The (ACC) Asynchronous-Control-Character-Map that this node uses when building a packet to send to the node on the other end of t… |
1.3.6.1.4.1.2.6.2.10.1.1.9 | ibmpppLinkMagicLoopCount | 0 | 0 | The number of times that this node will do a Magic Number Configuration before deciding that the link is looped back. 0 indicate… |
1.3.6.1.4.1.2.6.2.10.1.1.10 | ibmpppLinkCommand | 0 | 0 | See section 4.14 on page 13 of RFC 1171. Reading from this variable will return no-op(1). The IBM 6611 Network Processor always p… |