As per Relevance of the word hardware, we have this rfc below:
Network Working Group B.
Request for Comments: 1659 Xyplex, Inc
Obsoletes: 1317 July 1994
Category: Standards
Definitions of Managed Objects for RS-232-like Hardware
using SMIv
Status of this
This document specifies an Internet standards track protocol for
Internet community, and requests discussion and suggestions
improvements. Please refer to the current edition of the "
Official Protocol Standards" (STD 1) for the standardization
and status 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 .............................. 3
4. Definitions ................................................. 3
5. Acknowledgements ............................................ 20
6. References .................................................. 20
7. Security Considerations ..................................... 21
8. Author's Address ............................................ 21
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
RS-232-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 1659 RS-232-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 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 Hardware Device MIB is mandatory for all systems
have such a hardware port supporting services managed through
other MIB
The MIB includes multiple similar types of hardware, and as a
contains objects not applicable to all of those types.
compliance definitions herein thus have a general group for
implementations, and separate groups for the different types
ports, such as asynchronous and synchronous
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
Stewart [Page 2]
RFC 1659 RS-232-like MIB July 1994
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
3.1. Relationship to Interface
The RS-232-like MIB is one of many MIBs designed for layered use
described in the Interface MIB [5]. In most implementations where
is present, it will be in the lowest interface sublayer, that is,
RS-232-like MIB represents the physical layer, providing service
higher layers such as the Character MIB [6] or PPP MIB [7].
The Interface MIB's ifTestTable and ifRcvAddressTable are
relevant to the RS-232-like MIB
The RS-232-like MIB is relevant for ifType values rs232(33), v35(45),
and perhaps others
The RS-232-like MIB requires the conformance groups ifGeneralGroup
and ifFixedLengthGroup
The value of ifSpeed is the same as rs232PortOutSpeed
Usefulness of error counters in this MIB depends on the
counters in ifFixedLengthGroup
4.
RS-232-MIB DEFINITIONS ::=
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE
Counter32, Integer32
FROM SNMPv2-
FROM IF-
FROM RFC1213-
MODULE-COMPLIANCE, OBJECT-
FROM SNMPv2-CONF
rs232 MODULE-
LAST-UPDATED "9405261700Z
ORGANIZATION "IETF Character MIB Working Group
CONTACT-
" Bob
Postal: Xyplex, Inc
Stewart [Page 3]
RFC 1659 RS-232-like MIB July 1994
295 Foster
Littleton, MA 01460
Tel: 508-952-4816
Fax: 508-952-4887
E-mail: rlstewart@eng.xyplex.com
"The MIB module for RS-232-like hardware devices."
::= { transmission 33 }
-- Generic RS-232-like
rs232Number OBJECT-
SYNTAX Integer32
MAX-ACCESS read-
STATUS
"The number of ports (regardless of their
state) in the RS-232-like general port table."
::= { rs232 1 }
-- RS-232-like General Port
rs232PortTable OBJECT-
SYNTAX SEQUENCE OF Rs232
MAX-ACCESS not-
STATUS
"A list of port entries. The number of entries
given by the value of rs232Number."
::= { rs232 2 }
rs232PortEntry OBJECT-
SYNTAX Rs232
MAX-ACCESS not-
STATUS
"Status and parameter values for a port."
INDEX { rs232PortIndex }
::= { rs232PortTable 1 }
Rs232PortEntry ::=
SEQUENCE {
rs232
InterfaceIndex
rs232
Stewart [Page 4]
RFC 1659 RS-232-like MIB July 1994
INTEGER
rs232
Integer32,
rs232
Integer32,
rs232
Integer32,
rs232
Integer32,
rs232
INTEGER
rs232
}
rs232PortIndex 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."
::= { rs232PortEntry 1 }
rs232PortType OBJECT-
SYNTAX INTEGER { other(1), rs232(2), rs422(3),
rs423(4), v35(5), x21(6) }
MAX-ACCESS read-
STATUS
"The port's hardware type."
::= { rs232PortEntry 2 }
rs232PortInSigNumber OBJECT-
SYNTAX Integer32
MAX-ACCESS read-
STATUS
"The number of input signals for the port in
input signal table (rs232PortInSigTable). The
contains entries only for those signals the
can detect and that are useful to observe."
::= { rs232PortEntry 3 }
Stewart [Page 5]
RFC 1659 RS-232-like MIB July 1994
rs232PortOutSigNumber OBJECT-
SYNTAX Integer32
MAX-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 and that are useful to observe."
::= { rs232PortEntry 4 }
rs232PortInSpeed OBJECT-
SYNTAX Integer32
MAX-ACCESS read-
STATUS
"The port's input speed in bits per second. Note
non-standard values, such as 9612, are probably not
on most implementations."
::= { rs232PortEntry 5 }
rs232PortOutSpeed OBJECT-
SYNTAX Integer32
MAX-ACCESS read-
STATUS
"The port's output speed in bits per second. Note
non-standard values, such as 9612, are probably not
on most implementations."
::= { rs232PortEntry 6 }
rs232PortInFlowType OBJECT-
SYNTAX INTEGER { none(1), ctsRts(2), dsrDtr(3) }
MAX-ACCESS read-
STATUS
"The port's type of input flow control. 'none
indicates no flow control at this level
'ctsRts' and 'dsrDtr' indicate use of the
hardware signals."
::= { rs232PortEntry 7 }
rs232PortOutFlowType OBJECT-
SYNTAX INTEGER { none(1), ctsRts(2), dsrDtr(3) }
MAX-ACCESS read-
STATUS
"The port's type of output flow control. 'none
Stewart [Page 6]
RFC 1659 RS-232-like MIB July 1994
indicates no flow control at this level
'ctsRts' and 'dsrDtr' indicate use of the
hardware signals."
::= { rs232PortEntry 8 }
-- RS-232-like Asynchronous Port
rs232AsyncPortTable OBJECT-
SYNTAX SEQUENCE OF Rs232
MAX-ACCESS not-
STATUS
"A list of asynchronous port entries. Entries
not exist for synchronous ports."
::= { rs232 3 }
rs232AsyncPortEntry OBJECT-
SYNTAX Rs232
MAX-ACCESS not-
STATUS
"Status and parameter values for an
port."
INDEX { rs232AsyncPortIndex }
::= { rs232AsyncPortTable 1 }
Rs232AsyncPortEntry ::=
SEQUENCE {
rs232
InterfaceIndex
rs232
INTEGER
rs232
INTEGER
rs232
INTEGER
rs232
INTEGER
rs232
Counter32,
rs232
Counter32,
rs232
Counter32
}
Stewart [Page 7]
RFC 1659 RS-232-like MIB July 1994
rs232AsyncPortIndex OBJECT-
SYNTAX
MAX-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)
MAX-ACCESS read-
STATUS
"The port's number of bits in a character."
::= { rs232AsyncPortEntry 2 }
rs232AsyncPortStopBits OBJECT-
SYNTAX INTEGER { one(1), two(2),
oneAndHalf(3), dynamic(4) }
MAX-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) }
MAX-ACCESS read-
STATUS
"The port's sense of a character parity bit."
::= { rs232AsyncPortEntry 4 }
rs232AsyncPortAutobaud OBJECT-
SYNTAX INTEGER { enabled(1), disabled(2) }
MAX-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."
Stewart [Page 8]
RFC 1659 RS-232-like MIB July 1994
::= { rs232AsyncPortEntry 5 }
rs232AsyncPortParityErrs OBJECT-
SYNTAX Counter32
MAX-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 Counter32
MAX-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 Counter32
MAX-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 }
-- RS-232-like Synchronous Port
rs232SyncPortTable OBJECT-
SYNTAX SEQUENCE OF Rs232
MAX-ACCESS not-
STATUS
"A list of asynchronous port entries. Entries
not exist for synchronous ports."
::= { rs232 4 }
rs232SyncPortEntry OBJECT-
SYNTAX Rs232
MAX-ACCESS not-
STATUS
Stewart [Page 9]
RFC 1659 RS-232-like MIB July 1994
"Status and parameter values for a
port."
INDEX { rs232SyncPortIndex }
::= { rs232SyncPortTable 1 }
Rs232SyncPortEntry ::=
SEQUENCE {
rs232
InterfaceIndex
rs232
INTEGER
rs232
Counter32,
rs232
Counter32,
rs232
Counter32,
rs232
Counter32,
rs232
Counter32,
rs232
INTEGER
rs232
INTEGER
rs232
INTEGER
rs232
Integer32,
rs232
INTEGER
rs232
INTEGER
rs232
Integer32
}
rs232SyncPortIndex OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"A unique value for each port. Its value is
same as rs232PortIndex for the port."
::= { rs232SyncPortEntry 1 }
Stewart [Page 10]
RFC 1659 RS-232-like MIB July 1994
rs232SyncPortClockSource OBJECT-
SYNTAX INTEGER { internal(1), external(2), split(3) }
MAX-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 Counter32
MAX-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 Counter32
MAX-ACCESS read-
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 Counter32
MAX-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 Counter32
MAX-ACCESS read-
STATUS
Stewart [Page 11]
RFC 1659 RS-232-like MIB July 1994
"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 Counter32
MAX-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 }
rs232SyncPortRole OBJECT-
SYNTAX INTEGER { dte(1), dce(2) }
MAX-ACCESS read-
STATUS
"The role the device is playing that is using this port
dte means the device is performing the role
data terminal
dce means the device is performing the role
data circuit-terminating equipment."
DEFVAL { dce }
::= { rs232SyncPortEntry 8 }
rs232SyncPortEncoding OBJECT-
SYNTAX INTEGER { nrz(1), nrzi(2) }
MAX-ACCESS read-
STATUS
"The bit stream encoding technique that is in
for this port
nrz for Non-Return to Zero
nrzi for Non-Return to Zero Inverted encoding."
DEFVAL { nrz }
::= { rs232SyncPortEntry 9 }
rs232SyncPortRTSControl OBJECT-
SYNTAX INTEGER { controlled(1), constant(2) }
MAX-ACCESS read-
STATUS
Stewart [Page 12]
RFC 1659 RS-232-like MIB July 1994
"The method used to control the Request To Send (RTS
signal
controlled when the DTE is asserts RTS each
data needs to be transmitted and
RTS at some point after
transmission begins
If rs232SyncPortRole is 'dte',
RTS is an output signal. The
will issue a RTS and wait for a
from the DCE before starting
transmit
If rs232SyncPortRole is 'dce',
RTS is an input signal. The
will issue a CTS only after
received RTS and waiting
rs232SyncPortRTSCTSDelay interval
constant when the DTE constantly asserts RTS."
DEFVAL { constant }
::= { rs232SyncPortEntry 10 }
rs232SyncPortRTSCTSDelay OBJECT-
SYNTAX Integer32
MAX-ACCESS read-
STATUS
"The interval (in milliseconds) that the DCE must
after it sees RTS asserted before asserting CTS.
object exists in support of older synchronous
that cannot recognize CTS within a certain
after it asserts RTS."
DEFVAL { 0 }
::= { rs232SyncPortEntry 11 }
rs232SyncPortMode OBJECT-
SYNTAX INTEGER { fdx(1), hdx(2), simplex-receive(3),
simplex-send(4) }
MAX-ACCESS read-
STATUS
"The mode of operation of the port with respect to
direction and simultaneity of data transfer
Stewart [Page 13]
RFC 1659 RS-232-like MIB July 1994
fdx when frames on the data link can
transmitted and received at the
hdx when frames can either be
from the data link or
onto the data link but not at
same time
simplex-receive when frames can only be received
this data link
simplex-send when frames can only be sent on
data link."
DEFVAL { fdx }
::= { rs232SyncPortEntry 12 }
rs232SyncPortIdlePattern OBJECT-
SYNTAX INTEGER { mark(1), space(2) }
MAX-ACCESS read-
STATUS
"The bit pattern used to indicate an idle line."
DEFVAL { space }
::= { rs232SyncPortEntry 13 }
rs232SyncPortMinFlags OBJECT-
SYNTAX Integer32
MAX-ACCESS read-
STATUS
"The minimum number of flag patterns this port needs
order to recognize the end of one frame and the
of the next. Plausible values are 1 and 2."
DEFVAL { 2 }
::= { rs232SyncPortEntry 14 }
-- Input Signal
rs232InSigTable OBJECT-
SYNTAX SEQUENCE OF Rs232
MAX-ACCESS not-
STATUS
"A list of port input control signal
implemented and visible to the software on the port
and useful to monitor."
Stewart [Page 14]
RFC 1659 RS-232-like MIB July 1994
::= { rs232 5 }
rs232InSigEntry OBJECT-
SYNTAX Rs232
MAX-ACCESS not-
STATUS
"Input control signal status for a hardware port."
INDEX { rs232InSigPortIndex, rs232InSigName }
::= { rs232InSigTable 1 }
Rs232InSigEntry ::=
SEQUENCE {
rs232
InterfaceIndex
rs232
INTEGER
rs232
INTEGER
rs232
Counter32
}
rs232InSigPortIndex OBJECT-
SYNTAX
MAX-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) }
MAX-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
Stewart [Page 15]
RFC 1659 RS-232-like MIB July 1994
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) }
MAX-ACCESS read-
STATUS
"The current signal state."
::= { rs232InSigEntry 3 }
rs232InSigChanges OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of times the signal has changed
'on' to 'off' or from 'off' to 'on'."
::= { rs232InSigEntry 4 }
-- Output Signal
rs232OutSigTable OBJECT-
SYNTAX SEQUENCE OF Rs232
MAX-ACCESS not-
STATUS
"A list of port output control signal
implemented and visible to the software on the port
and useful to monitor."
::= { rs232 6 }
rs232OutSigEntry OBJECT-
SYNTAX Rs232
MAX-ACCESS not-
STATUS
"Output control signal status for a hardware port."
INDEX { rs232OutSigPortIndex, rs232OutSigName }
::= { rs232OutSigTable 1 }
Stewart [Page 16]
RFC 1659 RS-232-like MIB July 1994
Rs232OutSigEntry ::=
SEQUENCE {
rs232
InterfaceIndex
rs232
INTEGER
rs232
INTEGER
rs232
Counter32
}
rs232OutSigPortIndex OBJECT-
SYNTAX
MAX-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) }
MAX-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 }
rs232OutSigState OBJECT-
SYNTAX INTEGER { none(1), on(2), off(3) }
Stewart [Page 17]
RFC 1659 RS-232-like MIB July 1994
MAX-ACCESS read-
STATUS
"The current signal state."
::= { rs232OutSigEntry 3 }
rs232OutSigChanges OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of times the signal has changed
'on' to 'off' or from 'off' to 'on'."
::= { rs232OutSigEntry 4 }
-- conformance
rs232Conformance OBJECT IDENTIFIER ::= { rs232 7 }
rs232Groups OBJECT IDENTIFIER ::= { rs232Conformance 1 }
rs232Compliances OBJECT IDENTIFIER ::= { rs232Conformance 2 }
-- compliance
rs232Compliance MODULE-
STATUS
"The compliance statement for SNMPv2
which have RS-232-like hardware interfaces."
MODULE -- this
MANDATORY-GROUPS { rs232Group }
GROUP rs232
"The Asynch group is mandatory only for
SNMPv2 entities which have
interfaces Rs-232-like."
GROUP rs232
"The Synch group is mandatory only for
SNMPv2 entities which have
interfaces Rs-232-like."
::= { rs232Compliances 1 }
Stewart [Page 18]
RFC 1659 RS-232-like MIB July 1994
-- units of
rs232Group OBJECT-
OBJECTS { rs232Number, rs232PortIndex, rs232PortType
rs232PortInSigNumber, rs232PortOutSigNumber
rs232PortInSpeed, rs232PortOutSpeed
rs232PortInFlowType, rs232PortOutFlowType
rs232InSigPortIndex, rs232InSigName
rs232InSigState, rs232InSigChanges
rs232OutSigPortIndex, rs232OutSigName
rs232OutSigState, rs232OutSigChanges }
STATUS
"A collection of objects providing
applicable to all RS-232-like interfaces."
::= { rs232Groups 1 }
rs232AsyncGroup OBJECT-
OBJECTS { rs232AsyncPortIndex, rs232AsyncPortBits
rs232AsyncPortStopBits, rs232AsyncPortParity
rs232AsyncPortAutobaud, rs232AsyncPortParityErrs
rs232AsyncPortFramingErrs, rs232AsyncPortOverrunErrs }
STATUS
"A collection of objects providing
applicable to asynchronous RS-232-like interfaces."
::= { rs232Groups 2 }
rs232SyncGroup OBJECT-
OBJECTS { rs232SyncPortIndex, rs232SyncPortClockSource
rs232SyncPortFrameCheckErrs
rs232SyncPortTransmitUnderrunErrs
rs232SyncPortReceiveOverrunErrs
rs232SyncPortInterruptedFrames
rs232SyncPortAbortedFrames }
STATUS
"A collection of objects providing
applicable to synchronous RS-232-like interfaces."
::= { rs232Groups 3 }
rs232SyncSDLCGroup OBJECT-
OBJECTS { rs232SyncPortRole
rs232SyncPortEncoding
rs232SyncPortRTSControl
rs232SyncPortRTSCTSDelay
rs232SyncPortMode
rs232SyncPortIdlePattern
Stewart [Page 19]
RFC 1659 RS-232-like MIB July 1994
rs232SyncPortMinFlags }
STATUS
"A collection of objects providing
applicable to synchronous RS-232-like
running SDLC."
::= { rs232Groups 4 }
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.
[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] Kastenholz, F., "The Definitions of Managed Objects for the
Control Protocol of the Point-to-Point Protocol", RFC 1471,
Software, Inc., June 1993.
Stewart [Page 20]
RFC 1659 RS-232-like MIB 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 21]
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
