As per Relevance of the word hardware, we have this rfc below:
Network Working Group B. Stewart,
Request for Comments: 1318 Xyplex, Inc
April 1992
Definitions of Managed
for Parallel-printer-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
parallel-printer-like devices
2. The Network Management
The Internet-standard Network Management Framework
of three components. They are
RFC 1155 which defines the SMI, the mechanisms used
describing and naming objects for the purpose of management
RFC 1212 defines a more concise description mechanism,
is wholly consistent with the SMI
RFC 1156 which defines MIB-I, the core set of
objects for the Internet suite of protocols. RFC 1213,
defines MIB-II, an evolution of MIB-I based
implementation experience and new operational requirements
RFC 1157 which defines the SNMP, the protocol used
network access to managed objects
The Framework permits new objects to be defined for
purpose of experimentation and evaluation
3.
Managed objects are accessed via a virtual
store, termed the Management Information Base or MIB
Character MIB Working Group [Page 1]
RFC 1318 PARALLEL-PRINTER-LIKE-MIB April 1992
Objects in the MIB are defined using the subset of
Syntax Notation One (ASN.1) [7] defined in the SMI.
particular, each object has a name, a syntax, and
encoding. The name is an object identifier,
administratively assigned name, which specifies an
type
The object type together with an object instance serves
uniquely identify a specific instantiation of the object
For human convenience, we often use a textual string,
the OBJECT DESCRIPTOR, to also refer to the object type
The syntax of an object type defines the abstract
structure corresponding to that object type. The ASN.1
language is used for this purpose. However, the SMI [3]
purposely restricts the ASN.1 constructs which may be used
These restrictions are explicitly made for simplicity
The encoding of an object type is simply how that
type is represented using the object type's syntax
Implicitly tied to the notion of an object type's syntax
encoding is how the object type is represented when
transmitted on the network
The SMI specifies the use of the basic encoding rules
ASN.1 [8], subject to the additional requirements imposed
the SNMP
3.1. Format of
Section 5 contains the specification of all object
contained in this MIB module. The object types are
using the conventions defined in the SMI, as amended by
extensions specified in [9,10].
4.
The Parallel-printer-like Hardware Device MIB applies
interface ports that might logically support the
MIB, a Transmission MIB, or the Character MIB (most
the latter). The most common example is a Centronics
Data Products type parallel printer port
The Parallel-printer-like MIB is one of a set of
designed for complementary use. At this writing, the
comprises
Character MIB Working Group [Page 2]
RFC 1318 PARALLEL-PRINTER-LIKE-MIB April 1992
Character
PPP
RS-232-like
Parallel-printer-like
The RS-232-like MIB and the Parallel-printer-like
represent the physical layer, providing service to
layers such as the Character MIB or PPP MIB. Further
may appear above these
The following diagram shows two possible "MIB stacks",
using the 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
represent the lowest level, regardless of the higher
that may be using it. In turn, separate higher level
represent specific applications, such as a terminal (
Character MIB) or a network connection (the PPP MIB).
The Parallel-printer-like MIB is mandatory for all
that have such a hardware port supporting services
through some other MIB, for example, the Character MIB
The Parallel-printer-like MIB includes multiple
types of hardware, and as a result contains objects
applicable to all of those types. Such objects are in
separate branch of the MIB, which is required
applicable and otherwise absent
The Parallel-printer-like MIB includes Centronics,
Products, and other parallel physical links with a
set of control signals
The MIB contains objects that relate to physical
connections. Such connections may provide
hardware signals (other than for basic data transfer),
as Power and PaperOut
The MIB comprises one base object and three tables,
Character MIB Working Group [Page 3]
RFC 1318 PARALLEL-PRINTER-LIKE-MIB April 1992
in the following sections. The tables contain objects
ports and input and output control signals
5.
RFC1318-MIB DEFINITIONS ::=
FROM RFC1155-
FROM RFC1213-
OBJECT-
FROM RFC-1212;
-- this is the MIB module for Parallel-printer-
-- hardware
para OBJECT IDENTIFIER ::= { transmission 34 }
-- the generic Parallel-printer-like
-- Implementation of this group is mandatory for
-- systems that have Parallel-printer-like
-- ports supporting higher level services such
-- character
paraNumber OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of ports (regardless of their
state) in the Parallel-printer-like port table."
::= { para 1 }
-- the Parallel-printer-like Port
paraPortTable OBJECT-
SYNTAX SEQUENCE OF
ACCESS not-
STATUS
"A list of port entries. The number of entries
given by the value of paraNumber."
::= { para 2 }
Character MIB Working Group [Page 4]
RFC 1318 PARALLEL-PRINTER-LIKE-MIB April 1992
paraPortEntry OBJECT-
SYNTAX
ACCESS not-
STATUS
"Status and parameter values for a port."
INDEX { paraPortIndex }
::= { paraPortTable 1 }
ParaPortEntry ::=
SEQUENCE {
INTEGER
INTEGER
INTEGER
}
paraPortIndex OBJECT-
SYNTAX
ACCESS read-
STATUS
"A unique value for each port. Its value
between 1 and the value of paraNumber.
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."
::= { paraPortEntry 1 }
paraPortType OBJECT-
SYNTAX INTEGER {
other(1),
centronics(2),
dataproducts(3)
}
ACCESS read-
STATUS
"The port's hardware type."
::= { paraPortEntry 2 }
paraPortInSigNumber OBJECT-
Character MIB Working Group [Page 5]
RFC 1318 PARALLEL-PRINTER-LIKE-MIB April 1992
SYNTAX
ACCESS read-
STATUS
"The number of input signals for the port in
input signal table (paraPortInSigTable). The
contains entries only for those signals the
can detect."
::= { paraPortEntry 3 }
paraPortOutSigNumber OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of output signals for the port in
output signal table (paraPortOutSigTable).
table contains entries only for those signals
software can assert."
::= { paraPortEntry 4 }
-- the Input Signal
paraInSigTable OBJECT-
SYNTAX SEQUENCE OF
ACCESS not-
STATUS
"A list of port input control signal entries."
::= { para 3 }
paraInSigEntry OBJECT-
SYNTAX
ACCESS not-
STATUS
"Input control signal status for a hardware port."
INDEX { paraInSigPortIndex, paraInSigName }
::= { paraInSigTable 1 }
ParaInSigEntry ::=
SEQUENCE {
INTEGER
INTEGER
Character MIB Working Group [Page 6]
RFC 1318 PARALLEL-PRINTER-LIKE-MIB April 1992
INTEGER
}
paraInSigPortIndex OBJECT-
SYNTAX
ACCESS read-
STATUS
"The value of paraPortIndex for the port to
this entry belongs."
::= { paraInSigEntry 1 }
paraInSigName OBJECT-
SYNTAX INTEGER { power(1), online(2), busy(3),
paperout(4), fault(5) }
ACCESS read-
STATUS
"Identification of a hardware signal."
::= { paraInSigEntry 2 }
paraInSigState OBJECT-
SYNTAX INTEGER { none(1), on(2), off(3) }
ACCESS read-
STATUS
"The current signal state."
::= { paraInSigEntry 3 }
paraInSigChanges OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of times the signal has changed
'on' to 'off' or from 'off' to 'on'."
::= { paraInSigEntry 4 }
-- the Output Signal
paraOutSigTable OBJECT-
SYNTAX SEQUENCE OF
ACCESS not-
STATUS
Character MIB Working Group [Page 7]
RFC 1318 PARALLEL-PRINTER-LIKE-MIB April 1992
"A list of port output control signal entries."
::= { para 4 }
paraOutSigEntry OBJECT-
SYNTAX
ACCESS not-
STATUS
"Output control signal status for a hardware port."
INDEX { paraOutSigPortIndex, paraOutSigName }
::= { paraOutSigTable 1 }
ParaOutSigEntry ::=
SEQUENCE {
INTEGER
INTEGER
INTEGER
}
paraOutSigPortIndex OBJECT-
SYNTAX
ACCESS read-
STATUS
"The value of paraPortIndex for the port to
this entry belongs."
::= { paraOutSigEntry 1 }
paraOutSigName OBJECT-
SYNTAX INTEGER { power(1), online(2), busy(3),
paperout(4), fault(5) }
ACCESS read-
STATUS
"Identification of a hardware signal."
::= { paraOutSigEntry 2 }
paraOutSigState OBJECT-
SYNTAX INTEGER { none(1), on(2), off(3) }
ACCESS read-
STATUS
"The current signal state."
Character MIB Working Group [Page 8]
RFC 1318 PARALLEL-PRINTER-LIKE-MIB April 1992
::= { paraOutSigEntry 3 }
paraOutSigChanges OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of times the signal has changed
'on' to 'off' or from 'off' to 'on'."
::= { paraOutSigEntry 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
Donald Merritt,
David Perkins, 3
Jim Reinstedler, Ungerman-
Marshall Rose,
Ron Strich,
Dean Throop,
Bill Townsend,
Jesse Walker,
David Waitzman,
Bill Westfield,
Character MIB Working Group [Page 9]
RFC 1318 PARALLEL-PRINTER-LIKE-MIB April 1992
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.
8. Security
Security issues are not discussed in this memo
Character MIB Working Group [Page 10]
RFC 1318 PARALLEL-PRINTER-LIKE-MIB April 1992
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 11]
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
