rfc-1381

SNMP MIB Extension for X.25 LAPB

D. Throop, F. Baker
date1992-11 streamIETF areamgt wgx25mib statusPROPOSED STANDARD pages33 canonicalhttps://www.rfc-editor.org/rfc/rfc1381 doi10.17487/RFC1381
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing the Link Layer of X.25, LAPB. [STANDARDS-TRACK]

Extracted elements (30)

design-rationale §3.3

DEFVAL clauses were added for all writable objects to allow future MIB extensions to define LAPB interface creation mechanisms without needing to deprecate the existing objects for lack of defaults. The DEFVAL values are reasonable but not mandatory.

snmp

design-rationale §5

Separate transmit and receive objects were introduced for both N1 frame size and K window size (February 1992) because ISO 7776 sections 5.7.3 and 5.7.4, and ISO 8885 Table 3, explicitly provide for asymmetric values in each direction.

snmp

design-rationale §5

The document name was changed from HDLC to LAPB (February 1992 revision) because other HDLC variants—LAPD, SDLC, and raw HDLC—differ enough that this MIB would not adequately manage them; scoping to LAPB avoids misleading implementors of those other protocols.

snmp

design-rationale §3.4

The MIB separates configuration into a read-write lapbAdmnTable and a read-only lapbOperTable because operating parameters may diverge from configured values after XID negotiation overrides them or if lapbAdmnTable is modified while the interface is already running.

snmp

design-rationale §5

Timer units were changed to milliseconds (February 1992) to align with ISO 8885 Table 3, which specifies timer values in milliseconds. The T4 idle timer uses the sentinel value 2147483647 (PositiveInteger maximum) to indicate 'no idle timer kept' rather than introducing a separate boolean.

snmp

interoperability-note §3.1

A system running X.25 over LAPB over a synchronous line will have at least two ifTable entries: one for LAPB (ifType lapb(16)) and one for the X.25 packet layer. The X.25 MIB object x25InfoDataLinkId references the lapbAdmnIndex of the LAPB interface below it; lapbOperPortId in turn references the RS-232-like interface below LAPB.

snmp

interoperability-note §4

lapbFlowChangeReason correlates with MIB-II ifOperStatus when ifOperStatus is not 'testing': ifOperStatus is 'up' when lapbFlowChangeReason is abmEntered, abmeEntered, abmReset, or abmeReset; it is 'down' for notStarted or dmReceived through n2Timeout. No correlation exists when the value is 'other'.

snmp

interoperability-note §4

MIB-II ifLastChange for a LAPB interface should reflect the last time the interface changed state; a reset is treated as an instantaneous transition to the NDM (disconnected) state and back to ABM or ABME, making it the last time lapbFlowChangeReason and lapbFlowStateChanges changed.

snmp

interoperability-note §3.5

Since LAPB interfaces appear in the MIB-II ifTable, significant state transitions should generate standard linkUp or linkDown traps. Specifically, an interface that sends or receives a Frame Reject (FRMR) frame should send a linkDown trap; subsequent recovery should send a linkUp trap.

snmp

normative-requirement §4 MUST

Support for the lapbXidTable is mandatory for all agents of systems whose LAPB implementation uses XID negotiation; agents of systems without XID negotiation support should not implement this table.

snmp

normative-requirement §4 MUST

Support of the lapbAdmnTable is mandatory for all agents of systems that implement LAPB. It is a read-write table containing configurable parameters; changes may take effect immediately or upon interface restart depending on the implementation.

snmp

normative-requirement §4 MUST

Support of the lapbFlowTable is mandatory for all agents of systems that implement LAPB. It is read-only and records state changes, busy defers, REJ/SREJ frames sent and received, T1 timeouts, and the most recent FRMR and XID frame information fields.

snmp

normative-requirement §4 MUST

Support of the lapbOperTable is mandatory for all agents of systems that implement LAPB. This read-only table reflects parameters currently in use, which may differ from lapbAdmnTable values if XID negotiation overrode them or if the admin table was changed after interface start.

snmp

protocol-element §4

Four timer objects are defined, all in milliseconds: T1 (max wait for PDU acknowledgment, default 3000), T2 (max delay before sending an acknowledgment, default 0), T3 (wait before considering the link disconnected, default 60000; zero means disconnect upon frame exchange completion), and T4 (max idle time without frame exchange, default 2147483647 indicating disabled).

snmp

protocol-element §4

lapbAdmnActionInitiate specifies how LAPB initiates link setup: sendSABM(1), sendDISC(2), sendDM(3), none(4), or other(5); default sendSABM(1). lapbAdmnActionRecvDM specifies the response to a received DM frame: sendSABM(1), sendDISC(2), or other(3); default sendSABM(1).

snmp

protocol-element §4

lapbAdmnControlField and lapbOperControlField specify the sequence-number modulus: modulo8(1) for 3-bit numbers or modulo128(2) for 7-bit extended numbers (ISO 8885 HDLC Option 10). The configured default is modulo8(1).

snmp

protocol-element §4

lapbAdmnN2RxmitCount specifies the number of times a PDU is retransmitted after T1 expires without acknowledgment. Range is 0..65535; default is 20.

snmp

protocol-element §4

lapbAdmnStationType specifies the desired station type: dte(1), dce(2), or dxe(3), defaulting to dte(1). The corresponding lapbOperStationType reflects the currently active type and shows dxe(3) when XID negotiation has not yet determined the role.

snmp

protocol-element §4

lapbOperPortId is an OBJECT IDENTIFIER identifying an instance of the index object of the physical-interface MIB below LAPB (e.g., rs232PortIndex). If no such object is supported, agents return nullSpec OBJECT IDENTIFIER {0 0}.

snmp

protocol-element §4

lapbOperProtocolVersionId is an OBJECT IDENTIFIER identifying the LAPB protocol version in use. Three version OIDs are defined: lapbProtocolIso7776v1986, lapbProtocolCcittV1980, and lapbProtocolCcittV1984.

snmp, registry

protocol-element §4

lapbXidTable supplies XID negotiation parameters not present in lapbAdmnTable: lapbXidAdRIdentifier (Address Resolution Identifier), lapbXidAdRAddress, lapbXidParameterUniqueIdentifier, lapbXidGroupAddress, lapbXidPortNumber, and lapbXidUserDataSubfield. All are read-write OCTET STRINGs defaulting to empty.

snmp

protocol-element §4

Separate transmit and receive K window-size objects (lapbAdmnTransmitKWindowSize, lapbAdmnReceiveKWindowSize) define the maximum number of unacknowledged sequenced PDUs outstanding at once. Range is 1..127; default is 7.

snmp

protocol-element §4

Separate transmit and receive N1 frame-size objects (lapbAdmnTransmitN1FrameSize, lapbAdmnReceiveN1FrameSize) specify the maximum frame size in bits, excluding flags and zero-bit fill for transparency. Default is 36000 bits (4500 octets, matching the 802.5 frame size).

snmp

protocol-element §3.2

Two textual conventions are introduced: PositiveInteger (INTEGER 0..2147483647), used for frame sizes and timers, and IfIndexType (INTEGER 1..2147483647), used as an index whose values match MIB-II ifIndex. Their introduction does not alter SMI or SNMP encoding rules.

snmp

registry §3.3

The LAPB MIB occupies the OID lapb OBJECT IDENTIFIER ::= { transmission 16 }, with LAPB interfaces identified in MIB-II by ifType lapb(16). This document defines four tables under that arc: lapbAdmnTable, lapbOperTable, lapbFlowTable, and lapbXidTable, plus a lapbProtocolVersion sub-tree.

snmp, registry

security-consideration §8

Security issues are not discussed in this memo.

security, snmp

state-machine §4

lapbFlowChangeReason records the cause of the most recent lapbFlowStateChanges increment with 13 values: notStarted, abmEntered, abmeEntered, abmReset, abmeReset, dmReceived, dmSent, discReceived, discSent, frmrReceived, frmrSent, n2Timeout, other. A DM or DISC generated to initiate link setup does not alter this object.

snmp

state-machine §4

lapbFlowCurrentMode defines 17 LAPB link states: disconnected, linkSetup (SABM sent), frameReject (FRMR sent), disconnectRequest (DISC sent), informationTransfer (normal operation after SABM(E)/UA exchange), rejFrameSent, waitingAcknowledgement (T1 expired, RR sent), stationBusy (RNR sent), remoteStationBusy (RNR received), bothStationsBusy, waitingAckStationBusy, waitingAckRemoteBusy, waitingAckBothBusy, rejFrameSentRemoteBusy, xidFrameSent, error, and other.

snmp

wire-format §4

lapbFlowFrmrSent and lapbFlowFrmrReceived each hold the Information Field of the most recently sent or received FRMR frame as an OCTET STRING of SIZE(0..7). Zero length indicates no FRMR has occurred. Defined per ISO 7776 Section 4.3.9, tables 7 and 8.

snmp

wire-format §4

lapbFlowXidReceived and lapbXidUserDataSubfield both use OCTET STRING SIZE(0..8206) to carry XID frame information. lapbXidUserDataSubfield must include both the User Data Identifier and the User Data Field as shown in ISO 8885 figures 1 and 4.

snmp