As per Relevance of the word hardware, we have this rfc below:
Network Working Group B. Stewart,
Request for Comments: 1317 Xyplex, Inc
April 1992
Definitions of Managed Objects
RS-232-like Hardware
Status of this
This document specifies an IAB standards track protocol for
Internet community, and requests discussion and suggestions
improvements. Please refer to the current edition of the "
Official Protocol Standards" for the standardization state and
of this protocol. Distribution of this memo is unlimited
1.
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-
devices
2. The Network Management
The Internet-standard Network Management Framework consists of
components. They are
RFC 1155 which defines the SMI, the mechanisms used for
and naming objects for the purpose of management. RFC 1212 defines
more concise description mechanism, which is wholly consistent
the SMI
RFC 1156 which defines MIB-I, the core set of managed objects for
Internet suite of protocols. RFC 1213, defines MIB-II, an
of MIB-I based on implementation experience and new
requirements
RFC 1157 which defines the SNMP, the protocol used for network
to managed objects
The Framework permits new objects to be defined for the purpose
experimentation and evaluation
3.
Managed objects are accessed via a virtual information store,
the Management Information Base or MIB. Objects in the MIB
Character MIB Working Group [Page 1]
RFC 1317 RS-232-LIKE MIB April 1992
defined using the subset of Abstract Syntax Notation One (ASN.1) [7]
defined in the SMI. In particular, each object has a name, a syntax
and an encoding. The name is an object identifier,
administratively assigned name, which specifies an object type
The object type together with an object instance serves to
identify a specific instantiation of the object. For
convenience, we often use a textual string, termed the
DESCRIPTOR, to also refer to the object type
The syntax of an object type defines the abstract data
corresponding to that object type. The ASN.1 language is used
this purpose. However, the SMI [3] purposely restricts the ASN.1
constructs which may be used. These restrictions are explicitly
for simplicity
The encoding of an object type is simply how that object type
represented using the object type's syntax. Implicitly tied to
notion of an object type's syntax and encoding is how the object
is represented when being transmitted on the network
The SMI specifies the use of the basic encoding rules of ASN.1 [8],
subject to the additional requirements imposed by the SNMP
3.1. Format of
Section 5 contains the specification of all object types contained
this MIB module. The object types are defined using the
defined in the SMI, as amended by the extensions specified in [9,10].
4.
The RS-232-like Hardware Device MIB applies to interface ports
might logically support the Interface MIB, a Transmission MIB, or
Character MIB. The most common example is an RS-232 port with
signals
The RS-232-like MIB is one of a set of MIBs designed
complementary use. At this writing, the set comprises
Character
PPP
RS-232-like
Parallel-printer-like
The RS-232-like MIB and the Parallel-printer-like MIB represent
physical layer, providing service to higher layers such as
Character MIB or PPP MIB. Further MIBs may appear above these
Character MIB Working Group [Page 2]
RFC 1317 RS-232-LIKE MIB April 1992
The following diagram shows two possible "MIB stacks", each using
RS-232-like MIB
.-----------------.
.-----------------. | Standard MIB |
| Telnet MIB | | Interface Group |
|-----------------| |-----------------|
| Character MIB | | PPP MIB |
|-----------------| |-----------------|
| RS-232-like MIB | | RS-232-like MIB |
`-----------------' `-----------------'
The intent of the model is for the physical-level MIBs to
the lowest level, regardless of the higher level that may be
it. In turn, separate higher level MIBs represent
applications, such as a terminal (the Character MIB) or a
connection (the PPP MIB).
The RS-232-like Hardware Device MIB is mandatory for all systems
have such a hardware port supporting services managed through
other MIB, for example, the Character MIB or PPP MIB
The MIB includes multiple similar types of hardware, and as a
contains objects not applicable to all of those types. Such
are in a separate branch of the MIB, which is required
applicable and otherwise absent
The RS-232-like Hardware Port MIB includes RS-232, RS-422, RS-423,
V.35, and other asynchronous or synchronous, serial physical
with a similar set of control signals
The MIB contains objects that relate to physical layer connections
Such connections may provide interesting hardware signals (other
for basic data transfer), such as RNG and DCD. Hardware ports
have such attributes as speed and bits per character
Usefulness of error counters in this MIB depends on the presence
non-error character counts in higher level MIBs
The MIB comprises one base object and four tables, detailed in
following sections. The tables contain objects for all ports
asynchronous ports, and input and output control signals
Character MIB Working Group [Page 3]
RFC 1317 RS-232-LIKE MIB April 1992
5.
RFC1317-MIB DEFINITIONS ::=
FROM RFC1155-
FROM RFC1213-
OBJECT-
FROM RFC-1212;
-- this is the MIB module for RS-232-like hardware
rs232 OBJECT IDENTIFIER ::= { transmission 33 }
-- the generic RS-232-like
-- Implementation of this group is mandatory for
-- systems that have RS-232-like hardware
-- supporting higher level services such as
-- streams or network
rs232Number OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of ports (regardless of their
state) in the RS-232-like general port table."
::= { rs232 1 }
-- the RS-232-like general Port
rs232PortTable OBJECT-
SYNTAX SEQUENCE OF Rs232
ACCESS not-
STATUS
"A list of port entries. The number of entries
given by the value of rs232Number."
::= { rs232 2 }
rs232PortEntry OBJECT-
SYNTAX Rs232
ACCESS not-
Character MIB Working Group [Page 4]
RFC 1317 RS-232-LIKE MIB April 1992
STATUS
"Status and parameter values for a port."
INDEX { rs232PortIndex }
::= { rs232PortTable 1 }
Rs232PortEntry ::=
SEQUENCE {
rs232
INTEGER
rs232
INTEGER
rs232
INTEGER
rs232
INTEGER
rs232
INTEGER
rs232
INTEGER }
rs232PortIndex OBJECT-
SYNTAX
ACCESS read-
STATUS
"A unique value for each port. Its value
between 1 and the value of rs232Number.
convention and if possible, hardware port
map directly to external connectors. The value
each port must remain constant at least from
re-initialization of the network management agent
the next."
::= { rs232PortEntry 1 }
rs232PortType OBJECT-
SYNTAX INTEGER { other(1), rs232(2), rs422(3),
rs423(4), v35(5) }
ACCESS read-
STATUS
"The port's hardware type."
::= { rs232PortEntry 2 }
rs232PortInSigNumber OBJECT-
SYNTAX
ACCESS read-
STATUS
Character MIB Working Group [Page 5]
RFC 1317 RS-232-LIKE MIB April 1992
"The number of input signals for the port in
input signal table (rs232PortInSigTable). The
contains entries only for those signals the
can detect."
::= { rs232PortEntry 3 }
rs232PortOutSigNumber OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of output signals for the port in
output signal table (rs232PortOutSigTable).
table contains entries only for those signals
software can assert."
::= { rs232PortEntry 4 }
rs232PortInSpeed OBJECT-
SYNTAX
ACCESS read-
STATUS
"The port's input speed in bits per second."
::= { rs232PortEntry 5 }
rs232PortOutSpeed OBJECT-
SYNTAX
ACCESS read-
STATUS
"The port's output speed in bits per second."
::= { rs232PortEntry 6 }
-- the RS-232-like Asynchronous Port
-- Implementation of this group is mandatory if the
-- has any asynchronous ports. Otherwise it is
-- present
rs232AsyncPortTable OBJECT-
SYNTAX SEQUENCE OF Rs232
ACCESS not-
STATUS
"A list of asynchronous port entries. The
entry number is given by the value of rs232Number
Character MIB Working Group [Page 6]
RFC 1317 RS-232-LIKE MIB April 1992
Entries need not exist for synchronous ports."
::= { rs232 3 }
rs232AsyncPortEntry OBJECT-
SYNTAX Rs232
ACCESS not-
STATUS
"Status and parameter values for an
port."
INDEX { rs232AsyncPortIndex }
::= { rs232AsyncPortTable 1 }
Rs232AsyncPortEntry ::=
SEQUENCE {
rs232
INTEGER
rs232
INTEGER
rs232
INTEGER
rs232
INTEGER
rs232
INTEGER
rs232
Counter
rs232
Counter
rs232
}
rs232AsyncPortIndex OBJECT-
SYNTAX
ACCESS read-
STATUS
"A unique value for each port. Its value is
same as rs232PortIndex for the port."
::= { rs232AsyncPortEntry 1 }
rs232AsyncPortBits OBJECT-
SYNTAX INTEGER (5..8)
ACCESS read-
STATUS
Character MIB Working Group [Page 7]
RFC 1317 RS-232-LIKE MIB April 1992
"The port's number of bits in a character."
::= { rs232AsyncPortEntry 2 }
rs232AsyncPortStopBits OBJECT-
SYNTAX INTEGER { one(1), two(2),
one-and-half(3), dynamic(4) }
ACCESS read-
STATUS
"The port's number of stop bits."
::= { rs232AsyncPortEntry 3 }
rs232AsyncPortParity OBJECT-
SYNTAX INTEGER { none(1), odd(2), even(3),
mark(4), space(5) }
ACCESS read-
STATUS
"The port's sense of a character parity bit."
::= { rs232AsyncPortEntry 4 }
rs232AsyncPortAutobaud OBJECT-
SYNTAX INTEGER { enabled(1), disabled(2) }
ACCESS read-
STATUS
"A control for the port's ability to
sense input speed
When rs232PortAutoBaud is 'enabled', a port
autobaud to values different from the set values
speed, parity, and character size. As a result
network management system may temporarily
values different from what was previously set."
::= { rs232AsyncPortEntry 5 }
rs232AsyncPortParityErrs OBJECT-
SYNTAX
ACCESS read-
STATUS
"Total number of characters with a parity error
input from the port since system re-
and while the port state was 'up' or 'test'."
::= { rs232AsyncPortEntry 6 }
rs232AsyncPortFramingErrs OBJECT-
SYNTAX
Character MIB Working Group [Page 8]
RFC 1317 RS-232-LIKE MIB April 1992
ACCESS read-
STATUS
"Total number of characters with a framing error
input from the port since system re-
and while the port state was 'up' or 'test'."
::= { rs232AsyncPortEntry 7 }
rs232AsyncPortOverrunErrs OBJECT-
SYNTAX
ACCESS read-
STATUS
"Total number of characters with an overrun error
input from the port since system re-
and while the port state was 'up' or 'test'."
::= { rs232AsyncPortEntry 8 }
-- the RS-232-like Synchronous Port
-- Implementation of this group is mandatory if the
-- has any synchronous ports. Otherwise it is
-- present
rs232SyncPortTable OBJECT-
SYNTAX SEQUENCE OF Rs232
ACCESS not-
STATUS
"A list of synchronous port entries. The
entry number is given by the value of rs232Number
Entries need not exist for asynchronous ports."
::= { rs232 4 }
rs232SyncPortEntry OBJECT-
SYNTAX Rs232
ACCESS not-
STATUS
"Status and parameter values for a
port."
INDEX { rs232SyncPortIndex }
::= { rs232SyncPortTable 1 }
Rs232SyncPortEntry ::=
SEQUENCE {
rs232
Character MIB Working Group [Page 9]
RFC 1317 RS-232-LIKE MIB April 1992
INTEGER
rs232
INTEGER
rs232
Counter
rs232
Counter
rs232
Counter
rs232
Counter
rs232
}
rs232SyncPortIndex OBJECT-
SYNTAX
ACCESS read-
STATUS
"A unique value for each port. Its value is
same as rs232PortIndex for the port."
::= { rs232SyncPortEntry 1 }
rs232SyncPortClockSource OBJECT-
SYNTAX INTEGER { internal(1), external(2), split(3) }
ACCESS read-
STATUS
"Source of the port's bit rate clock. 'split'
the tranmit clock is internal and the receive
is external."
::= { rs232SyncPortEntry 2 }
rs232SyncPortFrameCheckErrs OBJECT-
SYNTAX
ACCESS read-
STATUS
"Total number of frames with an invalid frame
sequence, input from the port since
re-initialization and while the port state was 'up
or 'test'."
::= { rs232SyncPortEntry 3 }
rs232SyncPortTransmitUnderrunErrs OBJECT-
SYNTAX
ACCESS read-
Character MIB Working Group [Page 10]
RFC 1317 RS-232-LIKE MIB April 1992
STATUS
"Total number of frames that failed to
transmitted on the port since
re-initialization and while the port state was 'up
or 'test' because data was not available to
transmitter in time."
::= { rs232SyncPortEntry 4 }
rs232SyncPortReceiveOverrunErrs OBJECT-
SYNTAX
ACCESS read-
STATUS
"Total number of frames that failed to be
on the port since system re-initialization and
the port state was 'up' or 'test' because
receiver did not accept the data in time."
::= { rs232SyncPortEntry 5 }
rs232SyncPortInterruptedFrames OBJECT-
SYNTAX
ACCESS read-
STATUS
"Total number of frames that failed to be
or transmitted on the port due to loss of
signals since system re-initialization and while
port state was 'up' or 'test'."
::= { rs232SyncPortEntry 6 }
rs232SyncPortAbortedFrames OBJECT-
SYNTAX
ACCESS read-
STATUS
"Number of frames aborted on the port due
receiving an abort sequence since
re-initialization and while the port state was 'up
or 'test'."
::= { rs232SyncPortEntry 7 }
-- the Input Signal
rs232InSigTable OBJECT-
SYNTAX SEQUENCE OF Rs232
ACCESS not-
Character MIB Working Group [Page 11]
RFC 1317 RS-232-LIKE MIB April 1992
STATUS
"A list of port input control signal entries."
::= { rs232 5 }
rs232InSigEntry OBJECT-
SYNTAX Rs232
ACCESS not-
STATUS
"Input control signal status for a hardware port."
INDEX { rs232InSigPortIndex, rs232InSigName }
::= { rs232InSigTable 1 }
Rs232InSigEntry ::=
SEQUENCE {
rs232
INTEGER
rs232
INTEGER
rs232
INTEGER
rs232
}
rs232InSigPortIndex OBJECT-
SYNTAX
ACCESS read-
STATUS
"The value of rs232PortIndex for the port to
this entry belongs."
::= { rs232InSigEntry 1 }
rs232InSigName OBJECT-
SYNTAX INTEGER { rts(1), cts(2), dsr(3), dtr(4), ri(5),
dcd(6), sq(7), srs(8), srts(9),
scts(10), sdcd(11) }
ACCESS read-
STATUS
"Identification of a hardware signal, as follows
rts Request to
cts Clear to
dsr Data Set
dtr Data Terminal
Character MIB Working Group [Page 12]
RFC 1317 RS-232-LIKE MIB April 1992
ri Ring
dcd Received Line Signal
sq Signal Quality
srs Data Signaling Rate
srts Secondary Request to
scts Secondary Clear to
sdcd Secondary Received Line Signal
"
"EIA Standard RS-232-C, August 1969."
::= { rs232InSigEntry 2 }
rs232InSigState OBJECT-
SYNTAX INTEGER { none(1), on(2), off(3) }
ACCESS read-
STATUS
"The current signal state."
::= { rs232InSigEntry 3 }
rs232InSigChanges OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of times the signal has changed
'on' to 'off' or from 'off' to 'on'."
::= { rs232InSigEntry 4 }
-- the Output Signal
rs232OutSigTable OBJECT-
SYNTAX SEQUENCE OF Rs232
ACCESS not-
STATUS
"A list of port output control signal entries."
::= { rs232 6 }
rs232OutSigEntry OBJECT-
SYNTAX Rs232
ACCESS not-
STATUS
"Output control signal status for a hardware port."
INDEX { rs232OutSigPortIndex, rs232OutSigName }
::= { rs232OutSigTable 1 }
Character MIB Working Group [Page 13]
RFC 1317 RS-232-LIKE MIB April 1992
Rs232OutSigEntry ::=
SEQUENCE {
rs232
INTEGER
rs232
INTEGER
rs232
INTEGER
rs232
}
rs232OutSigPortIndex OBJECT-
SYNTAX
ACCESS read-
STATUS
"The value of rs232PortIndex for the port to
this entry belongs."
::= { rs232OutSigEntry 1 }
rs232OutSigName OBJECT-
SYNTAX INTEGER { rts(1), cts(2), dsr(3), dtr(4), ri(5),
dcd(6), sq(7), srs(8), srts(9),
scts(10), sdcd(11) }
ACCESS read-
STATUS
"Identification of a hardware signal, as follows
rts Request to
cts Clear to
dsr Data Set
dtr Data Terminal
ri Ring
dcd Received Line Signal
sq Signal Quality
srs Data Signaling Rate
srts Secondary Request to
scts Secondary Clear to
sdcd Secondary Received Line Signal
"
"EIA Standard RS-232-C, August 1969."
::= { rs232OutSigEntry 2 }
Character MIB Working Group [Page 14]
RFC 1317 RS-232-LIKE MIB April 1992
rs232OutSigState OBJECT-
SYNTAX INTEGER { none(1), on(2), off(3) }
ACCESS read-
STATUS
"The current signal state."
::= { rs232OutSigEntry 3 }
rs232OutSigChanges OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of times the signal has changed
'on' to 'off' or from 'off' to 'on'."
::= { rs232OutSigEntry 4 }
6.
Based on several private MIBs, this document was produced by
Character MIB Working Group
Anne Ambler,
Charles Bazaar,
Christopher Bucci,
Anthony Chung, Hughes LAN
George Conant,
John Cook,
James Davin, MIT-
Shawn Gallagher,
Tom Grant,
Frank Huang,
David Jordan,
Satish Joshi,
Frank Kastenholz,
Ken Key, University of
Jim Kinder,
Rajeev Kochhar, 3
John LoVerso,
Keith McCloghrie, Hughes LAN
Donalpd Merritt,
David Perkins, 3
Jim Reinstedler, Ungerman-
Marshall Rose,
Ron Strich,
Dean Throop,
Character MIB Working Group [Page 15]
RFC 1317 RS-232-LIKE MIB April 1992
Bill Townsend,
Jesse Walker,
David Waitzman,
Bill Westfield,
7.
[1] Cerf, V., "IAB Recommendations for the Development of
Network Management Standards", RFC 1052, NRI, April 1988.
[2] Cerf, V., "Report of the Second Ad Hoc Network Management
Group", RFC 1109, NRI, August 1989.
[3] Rose M., and K. McCloghrie, "Structure and Identification
Management Information for TCP/IP-based internets", RFC 1155,
Performance Systems International, Hughes LAN Systems, May 1990.
[4] McCloghrie K., and M. Rose, "Management Information Base
Network Management of TCP/IP-based internets", RFC 1156,
LAN Systems, Performance Systems International, May 1990.
[5] Case, J., Fedor, M., Schoffstall, M., and J. Davin,
Network Management Protocol", RFC 1157, SNMP Research
Performance Systems International, Performance
International, MIT Laboratory for Computer Science, May 1990.
[6] McCloghrie K., and M. Rose, Editors, "Management Information
for Network Management of TCP/IP-based internets", RFC 1213,
Performance Systems International, March 1991.
[7] Information processing systems - Open Systems Interconnection -
Specification of Abstract Syntax Notation One (ASN.1),
International Organization for Standardization,
Standard 8824, December 1987.
[8] Information processing systems - Open Systems Interconnection -
Specification of Basic Encoding Rules for Abstract Notation
(ASN.1), International Organization for Standardization
International Standard 8825, December 1987.
[9] Rose, M., and K. McCloghrie, Editors, "Concise MIB Definitions",
RFC 1212, Performance Systems International, Hughes LAN Systems
March 1991.
[10] Rose, M., Editor, "A Convention for Defining Traps for use
the SNMP", RFC 1215, Performance Systems International,
1991.
Character MIB Working Group [Page 16]
RFC 1317 RS-232-LIKE MIB April 1992
8. Security
Security issues are not discussed in this memo
9. Author's
Bob
Xyplex, Inc
330 Codman Hill
Boxborough, MA 01719
Phone: (508) 264-9900
EMail: rlstewart@eng.xyplex.
Character MIB Working Group [Page 17]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
