rfc-1317

Definitions of Managed Objects for RS-232-like Hardware Devices

B. Stewart
date1992-04 streamIETF areamgt wgcharmib statusPROPOSED STANDARD pages17 canonicalhttps://www.rfc-editor.org/rfc/rfc1317 doi10.17487/RFC1317
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 the management of RS-232-like devices. [STANDARDS-TRACK]

obsoleted by

Extracted elements (25)

design-rationale §5

By convention and if possible, rs232PortIndex hardware port numbers map directly to external connectors, improving human operability by aligning logical identifiers with physical labeling.

snmp

design-rationale §4

Objects not applicable to all hardware types (e.g., async-only or sync-only parameters) are placed in separate table branches that are required when applicable and absent otherwise, keeping the base group minimal.

snmp

design-rationale §4

The RS-232-like MIB is positioned at the physical layer and is designed for complementary use with higher-level MIBs (Character MIB, PPP MIB); the physical-level MIB represents the lowest level regardless of which higher-level application uses it.

snmp

design-rationale §5

The rs232InSigTable and rs232OutSigTable contain entries only for signals the software can detect or assert, respectively, avoiding gaps or placeholder entries for unsupported signals in the signal tables.

snmp

design-rationale §4

The usefulness of error counters in this MIB depends on the presence of non-error character counts in higher-level MIBs, since error rates are only meaningful relative to total character counts.

snmp

interoperability-note §4

The RS-232-like Hardware Port MIB covers RS-232, RS-422, RS-423, V.35, and other asynchronous or synchronous serial physical links with a similar set of control signals, not just RS-232 strictly.

snmp

interoperability-note §5

The rs232AsyncPortTable maximum entry number is given by rs232Number, but entries need not exist for synchronous ports; similarly, rs232SyncPortTable entries need not exist for asynchronous ports.

snmp

interoperability-note §5

When rs232AsyncPortAutobaud is enabled, a network management system may temporarily observe speed, parity, and character-size values different from what was previously set, due to the port autobauing to a detected input rate.

snmp

normative-requirement §4 REQUIRED

Implementation of the RS-232-like Hardware Device MIB is mandatory for all systems that have RS-232-like hardware ports supporting higher-level services such as character streams or network interfaces (e.g., Character MIB or PPP MIB).

snmp

normative-requirement §5 REQUIRED

Implementation of the rs232AsyncPortTable group is mandatory if the system has any asynchronous ports; otherwise the group is not present.

snmp

normative-requirement §5 REQUIRED

Implementation of the rs232SyncPortTable group is mandatory if the system has any synchronous ports; otherwise the group is not present.

snmp

normative-requirement §5 MUST

The value of rs232PortIndex must remain constant at least from one re-initialization of the network management agent to the next, ensuring stable port identification across restarts.

snmp

protocol-element §5

rs232AsyncPortAutobaud controls whether a port automatically senses input speed. When enabled, the port may autobaud to values different from the administratively set speed, parity, and character size.

snmp

protocol-element §5

rs232AsyncPortTable (OID rs232 3) contains per-port asynchronous parameters: rs232AsyncPortBits (INTEGER 5..8), rs232AsyncPortStopBits (one/two/one-and-half/dynamic), rs232AsyncPortParity (none/odd/even/mark/space), and rs232AsyncPortAutobaud (enabled/disabled).

snmp

protocol-element §5

rs232InSigName and rs232OutSigName enumerate 11 RS-232-C hardware signals: rts(1), cts(2), dsr(3), dtr(4), ri(5), dcd(6), sq(7), srs(8), srts(9), scts(10), sdcd(11), referencing EIA Standard RS-232-C (August 1969).

snmp

protocol-element §5

rs232InSigTable (OID rs232 5) is indexed by (rs232InSigPortIndex, rs232InSigName) and contains entries only for signals the software can detect; each entry has rs232InSigState (none/on/off) and rs232InSigChanges (Counter of on↔off transitions).

snmp

protocol-element §5

rs232Number is a read-only INTEGER scalar (OID rs232 1) reporting the total number of RS-232-like ports regardless of their current state, which determines the size of rs232PortTable.

snmp

protocol-element §5

rs232OutSigTable (OID rs232 6) mirrors rs232InSigTable in structure, indexed by (rs232OutSigPortIndex, rs232OutSigName), but contains entries only for signals the software can assert rather than detect.

snmp

protocol-element §5

rs232PortTable (OID rs232 2) is a general port table indexed by rs232PortIndex, with entries containing: rs232PortType (other/rs232/rs422/rs423/v35), rs232PortInSigNumber, rs232PortOutSigNumber, rs232PortInSpeed (read-write, bps), and rs232PortOutSpeed (read-write, bps).

snmp

protocol-element §5

rs232PortType enumerates hardware types as INTEGER: other(1), rs232(2), rs422(3), rs423(4), v35(5), covering the range of RS-232-like serial interfaces managed by this MIB.

snmp

protocol-element §5

rs232SyncPortAbortedFrames counts frames aborted due to receiving an abort sequence since re-initialization while port state was 'up' or 'test', distinct from rs232SyncPortInterruptedFrames which counts frames lost due to modem signal loss.

snmp

protocol-element §5

rs232SyncPortClockSource specifies the bit rate clock source as internal(1), external(2), or split(3), where 'split' means the transmit clock is internal and the receive clock is external.

snmp

protocol-element §5

rs232SyncPortTable (OID rs232 4) contains per-port synchronous parameters: rs232SyncPortClockSource (internal/external/split) and five error counters for frame check errors, transmit underruns, receive overruns, interrupted frames, and aborted frames.

snmp

protocol-element §5

The asynchronous port table tracks three error counters (all Counter type, read-only): rs232AsyncPortParityErrs, rs232AsyncPortFramingErrs, and rs232AsyncPortOverrunErrs, counting errors since system re-initialization while port state was 'up' or 'test'.

snmp

security-consideration §8

Security issues are not discussed in this memo; no authentication, access control, or confidentiality considerations are specified for the RS-232-like MIB objects.

snmp, security