As per Relevance of the word hardware, we have this rfc below:
Network Working Group B.
Request for Comments: 1660 Xyplex, Inc
Obsoletes: 1318 July 1994
Category: Standards
Definitions of Managed Objects for Parallel-printer-
Hardware Devices using SMIv
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
Table of
1. Introduction ............................................... 1
2. The SNMPv2 Network Management Framework .................... 1
2.1 Object Definitions ........................................ 2
3. Overview ................................................... 2
3.1 Relationship to Interface MIB ............................. 2
4. Definitions ................................................ 3
5. Acknowledgements ........................................... 9
6. References ................................................. 9
7. Security Considerations .................................... 10
8. Author's Address ........................................... 10
1.
This memo defines an extension to the Management Information
(MIB) for use with network management protocols in the
community. In particular, it defines objects for the management
Parallel-printer-like devices
2. The SNMPv2 Network Management
The SNMPv2 Network Management Framework consists of four
components. They are
o RFC 1442 [1] which defines the SMI, the mechanisms used
describing and naming objects for the purpose of management
o STD 17, RFC 1213 [2] defines MIB-II, the core set of
objects for the Internet suite of protocols
Stewart [Page 1]
RFC 1660 Parallel-printer-like MIB July 1994
o RFC 1445 [3] which defines the administrative and
architectural aspects of the framework
o RFC 1448 [4] which defines the protocol used for
access to managed objects
The Framework permits new objects to be defined for the purpose
experimentation and evaluation
2.1. Object
Managed objects are accessed via a virtual information store,
the Management Information Base or MIB. Objects in the MIB
defined using the subset of Abstract Syntax Notation One (ASN.1)
defined in the SMI. In particular, each object object type is
by an OBJECT IDENTIFIER, an administratively assigned name.
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,
refer to the object type
3.
The Parallel-printer-like Hardware Device MIB applies to
ports that would most probably support the Character MIB. The
common example is Centronics-like printer port
The Parallel-printer-like Hardware Device MIB is mandatory for
systems that have such a hardware port supporting services
through some other MIB
The Parallel-printer-like Hardware Port MIB includes Centronics-
and Data-Products-like parallel physical links with a similar set
control signals
The MIB contains objects that relate to physical layer connections
The MIB comprises one base object and three tables, detailed in
following sections. The tables contain objects for ports and
and output control signals
3.1. Relationship to Interface
The Parallel-printer-like MIB is one of many MIBs designed
layered use as described in the Interface MIB [5]. In
implementations where it is present, it will be in the
interface sublayer, that is, the Parallel-printer-like MIB
the physical layer, providing service to higher layers such as
Stewart [Page 2]
RFC 1660 Parallel-printer-like MIB July 1994
Character MIB [6].
Although it is unlikely that a parallel printer port will actually
used as a network interface, which is the intent of the
MIB, the Parallel-printer-like MIB is closely connected to
Character MIB, which can share hardware interfaces with
operation, and relate to the RS-232 MIB [7].
The Interface MIB's ifTestTable and ifRcvAddressTable are
relevant to the Parallel-printer-like MIB
The Parallel-printer-like MIB is relevant for ifType values para(34)
and perhaps others
The Parallel-printer-like MIB requires the conformance
ifGeneralGroup, and ifFixedLengthGroup
Usefulness of error counters in this MIB depends on the
counters in ifFixedLengthGroup
4.
PARALLEL-MIB DEFINITIONS ::=
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE
Counter32, Integer32
FROM SNMPv2-
FROM IF-
FROM RFC1213-
MODULE-COMPLIANCE, OBJECT-
FROM SNMPv2-CONF
para MODULE-
LAST-UPDATED "9405261700Z
ORGANIZATION "IETF Character MIB Working Group
CONTACT-
" Bob
Postal: Xyplex, Inc
295 Foster
Littleton, MA 01460
Tel: 508-952-4816
Fax: 508-952-4887
E-mail: rlstewart@eng.xyplex.com
Stewart [Page 3]
RFC 1660 Parallel-printer-like MIB July 1994
"The MIB module for Parallel-printer-like hardware devices."
::= { transmission 34 }
-- Generic Parallel-printer-like
paraNumber OBJECT-
SYNTAX Integer32
MAX-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
MAX-ACCESS not-
STATUS
"A list of port entries. The number of entries
given by the value of paraNumber."
::= { para 2 }
paraPortEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"Status and parameter values for a port."
INDEX { paraPortIndex }
::= { paraPortTable 1 }
ParaPortEntry ::=
SEQUENCE {
InterfaceIndex
INTEGER
Integer32,
Integer32
}
Stewart [Page 4]
RFC 1660 Parallel-printer-like MIB July 1994
paraPortIndex OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The value of ifIndex for the port. By
and if possible, hardware port numbers map
to external connectors. The value for each port
remain constant at least from one re-
of the network management agent to the next."
::= { paraPortEntry 1 }
paraPortType OBJECT-
SYNTAX INTEGER {
other(1),
centronics(2),
dataproducts(3)
}
MAX-ACCESS read-
STATUS
"The port's hardware type."
::= { paraPortEntry 2 }
paraPortInSigNumber OBJECT-
SYNTAX Integer32
MAX-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 and that are useful to observe."
::= { paraPortEntry 3 }
paraPortOutSigNumber OBJECT-
SYNTAX Integer32
MAX-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 and that are useful to observe."
::= { paraPortEntry 4 }
Stewart [Page 5]
RFC 1660 Parallel-printer-like MIB July 1994
-- Parallel-printer-like Input Signal
paraInSigTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"A list of port input control signal entries."
::= { para 3 }
paraInSigEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"Input control signal status for a hardware port."
INDEX { paraInSigPortIndex, paraInSigName }
::= { paraInSigTable 1 }
ParaInSigEntry ::=
SEQUENCE {
InterfaceIndex
INTEGER
INTEGER
Counter32
}
paraInSigPortIndex OBJECT-
SYNTAX
MAX-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) }
MAX-ACCESS read-
STATUS
"Identification of a hardware signal."
::= { paraInSigEntry 2 }
Stewart [Page 6]
RFC 1660 Parallel-printer-like MIB July 1994
paraInSigState OBJECT-
SYNTAX INTEGER { none(1), on(2), off(3) }
MAX-ACCESS read-
STATUS
"The current signal state."
::= { paraInSigEntry 3 }
paraInSigChanges OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of times the signal has changed
'on' to 'off' or from 'off' to 'on'."
::= { paraInSigEntry 4 }
-- Output Signal
paraOutSigTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"A list of port output control signal entries."
::= { para 4 }
paraOutSigEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"Output control signal status for a hardware port."
INDEX { paraOutSigPortIndex, paraOutSigName }
::= { paraOutSigTable 1 }
ParaOutSigEntry ::=
SEQUENCE {
InterfaceIndex
INTEGER
INTEGER
Counter32
}
Stewart [Page 7]
RFC 1660 Parallel-printer-like MIB July 1994
paraOutSigPortIndex OBJECT-
SYNTAX
MAX-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) }
MAX-ACCESS read-
STATUS
"Identification of a hardware signal."
::= { paraOutSigEntry 2 }
paraOutSigState OBJECT-
SYNTAX INTEGER { none(1), on(2), off(3) }
MAX-ACCESS read-
STATUS
"The current signal state."
::= { paraOutSigEntry 3 }
paraOutSigChanges OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of times the signal has changed
'on' to 'off' or from 'off' to 'on'."
::= { paraOutSigEntry 4 }
-- conformance
paraConformance OBJECT IDENTIFIER ::= { para 5 }
paraGroups OBJECT IDENTIFIER ::= { paraConformance 1 }
paraCompliances OBJECT IDENTIFIER ::= { paraConformance 2 }
Stewart [Page 8]
RFC 1660 Parallel-printer-like MIB July 1994
-- compliance
paraCompliance MODULE-
STATUS
"The compliance statement for SNMPv2
which have Parallel-printer-like
interfaces."
MODULE -- this
MANDATORY-GROUPS { paraGroup }
::= { paraCompliances 1 }
-- units of
paraGroup OBJECT-
OBJECTS { paraNumber, paraPortIndex, paraPortType
paraPortInSigNumber, paraPortOutSigNumber
paraInSigPortIndex, paraInSigName
paraInSigState, paraInSigChanges
paraOutSigPortIndex, paraOutSigName
paraOutSigState, paraOutSigChanges }
STATUS
"A collection of objects providing
applicable to all Parallel-printer-like interfaces."
::= { paraGroups 1 }
5.
This memo was produced by the IETF Character MIB Working Group
6.
[1] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "
of Management Information for version 2 of the Simple
Management Protocol (SNMPv2)", RFC 1442, SNMP Research,Inc.,
Hughes LAN Systems, Dover Beach Consulting, Inc., Carnegie
University, April 1993.
[2] McCloghrie, K., and M. Rose, Editors, "Management
Base for Network Management of TCP/IP-based internets: MIB-II",
STD 17, RFC 1213, Hughes LAN Systems, Performance
International, March 1991.
Stewart [Page 9]
RFC 1660 Parallel-printer-like MIB July 1994
[3] Galvin, J., and K. McCloghrie, "Administrative Model for
2 of the Simple Network Management Protocol (SNMPv2)", RFC 1445,
Trusted Information Systems, Hughes LAN Systems, April 1993.
[4] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "
Operations for version 2 of the Simple Network
Protocol (SNMPv2)", RFC 1448, SNMP Research,Inc., Hughes
Systems, Dover Beach Consulting, Inc., Carnegie
University, April 1993.
[5] McCloghrie, K., and F. Kastenholz, "Evolution of the
Group of MIB-II", RFC 1573, Hughes LAN Systems, FTP Software
January 1994.
[6] Stewart, B., "Definitions of Managed Objects for Character
Devices using SMIv2", RFC 1658, Xyplex, Inc., July 1994.
[7] Stewart, B., "Definitions of Managed Objects for RS-232-
Devices using SMIv2", RFC 1659, Xyplex, Inc., July 1994.
7. Security
Security issues are not discussed in this memo
8. Author's
Bob
Xyplex, Inc
295 Foster
Littleton, MA 01460
Phone: 508-952-4816
Fax: 508-952-4887
EMail: rlstewart@eng.xyplex.
Stewart [Page 10]
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
