rfc-1318

Definitions of Managed Objects for Parallel-printer-like Hardware Devices

B. Stewart
date1992-04 streamIETF areamgt wgcharmib statusPROPOSED STANDARD pages11 canonicalhttps://www.rfc-editor.org/rfc/rfc1318 doi10.17487/RFC1318
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 parallel-printer- like devices. [STANDARDS-TRACK]

obsoleted by

Extracted elements (24)

design-rationale §4

Objects not applicable to all hardware types covered by this MIB are placed in a separate optional MIB branch, which is required only when applicable and otherwise absent, to avoid mandating irrelevant objects.

snmp

design-rationale §5

The MIB signal tables include only those signals the software can detect (input) or assert (output), so paraInSigNumber and paraOutSigNumber may be less than the full set of physical signals on the connector.

snmp

design-rationale §4

The Parallel-printer-like MIB is designed as a physical-layer MIB intended to be stacked beneath higher-level MIBs such as the Character MIB or PPP MIB, mirroring the way the RS-232-like MIB functions, so that physical and logical management concerns are separated.

snmp

interoperability-note §4

The Parallel-printer-like MIB is one of a complementary set including the Character MIB, PPP MIB, and RS-232-like MIB; it covers Centronics, Data Products, and similar parallel physical links with comparable control signal sets.

snmp

interoperability-note §4

The Parallel-printer-like MIB may logically support the Interface MIB, a Transmission MIB, or the Character MIB at higher layers; the most common use case is as a physical-layer substrate for the Character MIB.

snmp

normative-requirement §4 REQUIRED

Implementation of the Parallel-printer-like MIB is mandatory for all systems that have such a hardware port supporting higher level services such as character streams.

snmp

normative-requirement §5 MUST

The value of paraPortIndex for each port must remain constant at least from one re-initialization of the network management agent to the next.

snmp

protocol-element §5

paraInSigChanges is a Counter tracking the number of times an input signal has transitioned from 'on' to 'off' or 'off' to 'on'.

snmp

protocol-element §5

paraInSigName identifies individual input hardware signals with enumerated values: power(1), online(2), busy(3), paperout(4), fault(5).

snmp

protocol-element §5

paraInSigState represents the current state of an input signal with values: none(1), on(2), off(3).

snmp

protocol-element §5

paraInSigTable (para 3) is a mandatory table of input control signal entries, indexed by { paraInSigPortIndex, paraInSigName }, describing per-port input hardware signals.

snmp

protocol-element §5

paraNumber is a read-only INTEGER giving the total number of parallel-printer-like ports (regardless of current state) in the paraPortTable.

snmp

protocol-element §5

paraOutSigChanges is a Counter tracking the number of times an output signal has transitioned from 'on' to 'off' or 'off' to 'on'.

snmp

protocol-element §5

paraOutSigName identifies individual output hardware signals with the same enumerated set as input signals: power(1), online(2), busy(3), paperout(4), fault(5).

snmp

protocol-element §5

paraOutSigState represents the current state of an output signal with values: none(1), on(2), off(3).

snmp

protocol-element §5

paraOutSigTable (para 4) is a mandatory table of output control signal entries, indexed by { paraOutSigPortIndex, paraOutSigName }, describing per-port output hardware signals.

snmp

protocol-element §5

paraPortEntry contains four fields: paraPortIndex (INTEGER), paraPortType (INTEGER), paraPortInSigNumber (INTEGER), and paraPortOutSigNumber (INTEGER), describing each parallel port's identity and signal counts.

snmp

protocol-element §5

paraPortIndex is a unique read-only INTEGER per port, ranging from 1 to paraNumber. By convention, hardware port numbers map directly to external connectors where possible.

snmp

protocol-element §5

paraPortInSigNumber is a read-only INTEGER count of input signals present in paraInSigTable for a given port; only signals the software can detect are included.

snmp

protocol-element §5

paraPortOutSigNumber is a read-only INTEGER count of output signals present in paraOutSigTable for a given port; only signals the software can assert are included.

snmp

protocol-element §5

paraPortTable (para 2) is a mandatory table of port entries; the number of entries equals paraNumber. Each row is a ParaPortEntry indexed by paraPortIndex.

snmp

protocol-element §5

paraPortType identifies the port's hardware type with enumerated values: other(1), centronics(2), and dataproducts(3).

snmp

protocol-element §5

The top-level OID for this MIB module is 'para', assigned as { transmission 34 }, under the transmission subtree from RFC 1213.

snmp

security-consideration §8

The RFC explicitly states that security issues are not discussed in this memo.

snmp, security