Definitions of Managed Objects for Parallel-printer-like Hardware Devices using SMIv2
obsoletes
- rfc-1318 — Definitions of Managed Objects for Parallel-printer-like Hardware Devices
Extracted elements (22)
Both input and output signal tables use the same five-value enumeration (power, online, busy, paperout, fault) for signal names, providing a symmetric model for monitoring bidirectional hardware control signals on parallel printer ports.
Signal tables include entries only for signals the software can detect or assert and that are 'useful to observe', avoiding clutter from signals that are not software-accessible or operationally meaningful.
The Parallel-printer-like MIB is designed as the lowest interface sublayer in a layered MIB stack, providing the physical layer to higher layers such as the Character MIB (RFC 1658), and relates to the RS-232 MIB (RFC 1659).
The Parallel-printer-like MIB is relevant for ifType value para(34) and requires the Interface MIB conformance groups ifGeneralGroup and ifFixedLengthGroup; the ifTestTable and ifRcvAddressTable are not relevant to this MIB.
SNMPv2 entities with Parallel-printer-like hardware interfaces MUST implement the paraGroup, which is the sole MANDATORY-GROUP in the paraCompliance MODULE-COMPLIANCE statement.
The Parallel-printer-like Hardware Device MIB is mandatory for all systems that have a parallel-printer-like hardware port supporting services managed through some other MIB.
The paraPortIndex value must remain constant at least from one re-initialization of the network management agent to the next, ensuring stable port identification across agent restarts.
paraInSigChanges is a read-only Counter32 recording the cumulative number of times a hardware input signal has transitioned from 'on' to 'off' or 'off' to 'on'.
paraInSigName is a read-only INTEGER identifying a hardware input signal with values: power(1), online(2), busy(3), paperout(4), fault(5).
paraInSigState is a read-only INTEGER with values none(1), on(2), off(3) representing the current state of a hardware input control signal.
paraInSigTable contains input control signal entries indexed by (paraInSigPortIndex, paraInSigName), each row carrying paraInSigState and paraInSigChanges for monitoring hardware input signals per port.
paraNumber is a read-only Integer32 giving the total number of Parallel-printer-like ports in the system regardless of their current state, serving as the size indicator for paraPortTable.
paraOutSigName is a read-only INTEGER identifying a hardware output signal with values: power(1), online(2), busy(3), paperout(4), fault(5), mirroring the same enumeration as paraInSigName.
paraOutSigState and paraOutSigChanges provide, respectively, the current state (none/on/off) and cumulative transition count for each hardware output control signal, as read-only objects.
paraOutSigTable contains output control signal entries indexed by (paraOutSigPortIndex, paraOutSigName), each row carrying paraOutSigState and paraOutSigChanges for monitoring hardware output signals per port.
paraPortIndex is a read-only InterfaceIndex whose value corresponds to ifIndex for the port. By convention, hardware port numbers map directly to external connectors, and the value must remain constant across agent re-initializations.
paraPortInSigNumber is a read-only Integer32 giving the count of entries for a port in paraInSigTable; only signals the software can detect and that are useful to observe are included.
paraPortOutSigNumber is a read-only Integer32 giving the count of entries for a port in paraOutSigTable; only signals the software can assert and that are useful to observe are included.
paraPortTable is a sequence of ParaPortEntry rows indexed by paraPortIndex (InterfaceIndex), each carrying paraPortType, paraPortInSigNumber, and paraPortOutSigNumber. The number of entries equals paraNumber.
paraPortType is a read-only INTEGER enumerating the port's hardware type: other(1), centronics(2), or dataproducts(3), covering Centronics-like and Data-Products-like parallel physical links.
The PARALLEL-MIB module is registered under the transmission subtree at OID { transmission 34 }, corresponding to ifType para(34), establishing the OID arc for all objects defined in this MIB.
The RFC explicitly states that security issues are not discussed in this memo, providing no access-control or authentication guidance for the managed objects defined herein.