rfc-1316

Definitions of Managed Objects for Character Stream Devices

B. Stewart
date1992-04 streamIETF areamgt wgcharmib statusPROPOSED STANDARD pages17 canonicalhttps://www.rfc-editor.org/rfc/rfc1316 doi10.17487/RFC1316
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 character stream devices. [STANDARDS-TRACK]

obsoleted by

Extracted elements (26)

design-rationale §5

charSessConnectionId points to the highest available related MIB (e.g., Telnet MIB rather than TCP MIB when both exist) to give management applications the richest available protocol-specific information.

snmp

design-rationale §5

ctsRts(4) and dsrDtr(5) flow control values are included in charPortInFlowType and charPortOutFlowType despite being RS-232-specific and not architecturally pure at the Character MIB layer, explicitly for simplicity's sake.

snmp

design-rationale §4

The Character MIB is designed as one layer in a MIB stack, sitting above physical-layer MIBs (RS-232-like, Parallel-printer-like) and below or alongside application-layer MIBs (Telnet MIB, PPP MIB), enabling complementary use across layers.

snmp

design-rationale §4

The MIB intentionally contains no distinction between permanent and operational (volatile) data; handling of such distinctions is left implementation-specific to avoid over-constraining implementations.

snmp

interoperability-note §5

Session indexes may be reused across different ports (e.g., port 1 and port 3 may simultaneously have a session 2), and indexes within a port need not be sequential; the index value space is implementation-defined.

snmp

interoperability-note §4

When a character port runs a network protocol (SLIP or PPP), a corresponding Interfaces table entry must exist with ifOperStatus 'off' when not running a protocol and 'on' when running one; charPortOperStatus is 'down' during network use and Character MIB operational counters are inactive.

snmp

normative-requirement §5 MUST

charPortIndex must remain constant at least from one re-initialization of the network management agent to the next; by convention hardware port numbers come first with a direct mapping.

snmp

normative-requirement §4 REQUIRED

Implementation of the Character MIB is mandatory for all systems that offer character ports, including terminal servers, general-purpose time-sharing hosts, and systems with virtual console ports.

snmp, yang

protocol-element §5

charNumber (char 1) is a read-only INTEGER giving the total number of entries in charPortTable regardless of their current state.

snmp

protocol-element §5

charPortAdminOrigin controls allowed session origin: dynamic(1) permits network or local, network(2) permits only network-originated, local(3) permits only locally-originated, none(4) disallows all session establishment.

snmp

protocol-element §5

charPortAdminStatus controls desired port state with values: enabled (pass characters and form sessions), disabled (pass characters but not form sessions), off (no characters or sessions), maintenance (exclusive test mode).

snmp

protocol-element §5

charPortHardware is an AutonomousType OID pointing to a hardware-specific MIB sub-tree (e.g., RS-232 MIB) for the physical connector; agents without such values return nullHardware ::= { 0 0 }.

snmp

protocol-element §5

charPortInCharacters and charPortOutCharacters are Counters of total characters since system re-initialization while port is up/active/maintenance, including framing, XON/XOFF, BREAK occurrences, and all session traffic.

snmp

protocol-element §5

charPortInFlowState and charPortOutFlowState report current operational flow control state as none(1), unknown(2), stop(3), or go(4), reflecting real-time flow allowance on the port.

snmp

protocol-element §5

charPortInFlowType and charPortOutFlowType specify flow control with values: none(1), xonXoff(2), hardware(3), ctsRts(4), dsrDtr(5), controlling input and output character flow respectively.

snmp

protocol-element §5

charPortReset is a read-write control object with values ready(1) and execute(2); writing execute forces the port to a clean initial state and disconnects all sessions. GET always returns ready.

snmp

protocol-element §5

charPortSessionMaximum is a read-write INTEGER for maximum concurrent sessions; -1 indicates no maximum. Behavior when set below current session count is explicitly unspecified.

snmp

protocol-element §5

charPortTable (char 2) is the central port management table; charPortEntry is indexed by charPortIndex and contains status and parameter values for each character port.

snmp

protocol-element §5

charSessConnectionId is an InstancePointer OID referencing the highest available related MIB instance (e.g., tcpConnState for TCP); agents without such values return nullConnectionId ::= { 0 0 }.

snmp

protocol-element §5

charSessKill is a read-write control with values ready(1) and execute(2); writing execute terminates the session. GET always returns ready.

snmp

protocol-element §5

charSessProtocol is an AutonomousType OID identifying the session's network protocol. The MIB defines wellKnownProtocols (char 4) with OIDs for other, Telnet, Rlogin, LAT, X.29, and VTP.

snmp

protocol-element §5

charSessStartTime records the value of sysUpTime when the session entered the connecting state, providing session age information.

snmp

protocol-element §5

charSessTable (char 3) is indexed by {charSessPortIndex, charSessIndex} and holds status and parameter values for each character port session.

snmp

security-consideration §8

Security issues are not discussed in this memo (Section 8 explicitly states this).

security, snmp

state-machine §5

charPortOperStatus represents actual port state with five values: up (normal function), down (administrative or operational failure), maintenance (test mode), absent (hardware not present), active (up with user logged in).

snmp

state-machine §5

charSessState defines three session states: connecting(1) — moving toward connected, connected(2) — character data can flow on the network side, disconnecting(3) — moving from connected or connecting to nonexistent.

snmp