As per Relevance of the word obsolete, we have this rfc below:
Network Working Group SNMPv2 Working
Request for Comments: 1907 J.
Obsoletes: 1450 SNMP Research, Inc
Category: Standards Track K.
Cisco Systems, Inc
M.
Dover Beach Consulting, Inc
S.
International Network
January 1996
Management Information
for Version 2 of
Simple Network Management Protocol (SNMPv2)
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 ................................................ 2
1.1 A Note on Terminology ...................................... 2
2. Definitions ................................................. 2
2.1 The System Group ........................................... 3
2.2 The SNMP Group ............................................. 7
2.4 Information for Notifications .............................. 9
2.4.1 Well-known Traps ......................................... 10
2.5 The Set Group .............................................. 11
2.6 Conformance Information .................................... 11
2.6.1 Compliance Statements .................................... 11
2.6.2 Units of Conformance ..................................... 12
2.6.3 Obsolete Definitions ..................................... 13
3. Security Considerations ..................................... 18
4. Editor's Address ............................................ 19
5. Acknowledgements ............................................ 19
6. References .................................................. 20
SNMPv2 Working Group Standards Track [Page 1]
RFC 1907 Management Information Base for SNMPv2 January 1996
1.
A management system contains: several (potentially many) nodes,
with a processing entity, termed an agent, which has access
management instrumentation; at least one management station; and,
management protocol, used to convey management information
the agents and management stations. Operations of the protocol
carried out under an administrative framework which
authentication, authorization, access control, and privacy policies
Management stations execute management applications which monitor
control managed elements. Managed elements are devices such
hosts, routers, terminal servers, etc., which are monitored
controlled via access to their management information
Management information is viewed as a collection of managed objects
residing in a virtual information store, termed the
Information Base (MIB). Collections of related objects are
in MIB modules. These modules are written using a subset of OSI'
Abstract Syntax Notation One (ASN.1) [1], termed the Structure
Management Information (SMI) [2].
The management protocol, SNMPv2 [3], provides for the exchange
messages which convey management information between the agents
the management stations. It is the purpose of this document
define managed objects which describe the behavior of a SNMPv
entity
1.1. A Note on
For the purpose of exposition, the original Internet-standard
Management Framework, as described in RFCs 1155 (STD 16), 1157 (
15), and 1212 (STD 16), is termed the SNMP version 1
(SNMPv1). The current framework is termed the SNMP version 2
framework (SNMPv2).
2.
SNMPv2-MIB DEFINITIONS ::=
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE
TimeTicks, Counter32, snmpModules, mib-2
FROM SNMPv2-
DisplayString, TestAndIncr,
FROM SNMPv2-
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-
FROM SNMPv2-CONF
SNMPv2 Working Group Standards Track [Page 2]
RFC 1907 Management Information Base for SNMPv2 January 1996
snmpMIB MODULE-
LAST-UPDATED "9511090000Z
ORGANIZATION "IETF SNMPv2 Working Group
CONTACT-
" Marshall T.
Postal: Dover Beach Consulting, Inc
420 Whisman
Mountain View, CA 94043-2186
Tel: +1 415 968 1052
E-mail: mrose@dbc.mtview.ca.us
"The MIB module for SNMPv2 entities."
REVISION "9304010000Z
"The initial revision of this MIB module was published
RFC 1450."
::= { snmpModules 1 }
snmpMIBObjects OBJECT IDENTIFIER ::= { snmpMIB 1 }
-- ::= { snmpMIBObjects 1 } this OID is
-- ::= { snmpMIBObjects 2 } this OID is
-- ::= { snmpMIBObjects 3 } this OID is
-- the System
--
-- a collection of objects common to all managed systems
system OBJECT IDENTIFIER ::= { mib-2 1 }
sysDescr OBJECT-
SYNTAX DisplayString (SIZE (0..255))
MAX-ACCESS read-
STATUS
"A textual description of the entity. This value
include the full name and version identification of
system's hardware type, software operating-system,
networking software."
::= { system 1 }
sysObjectID OBJECT-
SNMPv2 Working Group Standards Track [Page 3]
RFC 1907 Management Information Base for SNMPv2 January 1996
SYNTAX OBJECT
MAX-ACCESS read-
STATUS
"The vendor's authoritative identification of the
management subsystem contained in the entity. This value
allocated within the SMI enterprises subtree (1.3.6.1.4.1)
and provides an easy and unambiguous means for
`what kind of box' is being managed. For example, if
`Flintstones, Inc.' was assigned the
1.3.6.1.4.1.4242, it could assign the
1.3.6.1.4.1.4242.1.1 to its `Fred Router'."
::= { system 2 }
sysUpTime OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The time (in hundredths of a second) since the
management portion of the system was last re-initialized."
::= { system 3 }
sysContact OBJECT-
SYNTAX DisplayString (SIZE (0..255))
MAX-ACCESS read-
STATUS
"The textual identification of the contact person for
managed node, together with information on how to
this person. If no contact information is known, the
is the zero-length string."
::= { system 4 }
sysName OBJECT-
SYNTAX DisplayString (SIZE (0..255))
MAX-ACCESS read-
STATUS
"An administratively-assigned name for this managed node
By convention, this is the node's fully-qualified
name. If the name is unknown, the value is the zero-
string."
::= { system 5 }
sysLocation OBJECT-
SYNTAX DisplayString (SIZE (0..255))
MAX-ACCESS read-
SNMPv2 Working Group Standards Track [Page 4]
RFC 1907 Management Information Base for SNMPv2 January 1996
STATUS
"The physical location of this node (e.g., `
closet, 3rd floor'). If the location is unknown, the
is the zero-length string."
::= { system 6 }
sysServices OBJECT-
SYNTAX INTEGER (0..127)
MAX-ACCESS read-
STATUS
"A value which indicates the set of services that
entity may potentially offers. The value is a sum.
sum initially takes the value zero, Then, for each layer, L
in the range 1 through 7, that this node
transactions for, 2 raised to (L - 1) is added to the sum
For example, a node which performs only routing
would have a value of 4 (2^(3-1)). In contrast, a
which is a host offering application services would have
value of 72 (2^(4-1) + 2^(7-1)). Note that in the
of the Internet suite of protocols, values should
calculated accordingly
layer
1 physical (e.g., repeaters
2 datalink/subnetwork (e.g., bridges
3 internet (e.g., supports the IP
4 end-to-end (e.g., supports the TCP
7 applications (e.g., supports the SMTP
For systems including OSI protocols, layers 5 and 6 may
be counted."
::= { system 7 }
-- object resource
--
-- a collection of objects which describe the SNMPv2 entity'
-- (statically and dynamically configurable) support
-- various MIB modules
sysORLastChange OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The value of sysUpTime at the time of the most
SNMPv2 Working Group Standards Track [Page 5]
RFC 1907 Management Information Base for SNMPv2 January 1996
change in state or value of any instance of sysORID."
::= { system 8 }
sysORTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"The (conceptual) table listing the capabilities of
local SNMPv2 entity acting in an agent role with respect
various MIB modules. SNMPv2 entities having dynamically
configurable support of MIB modules will have
dynamically-varying number of conceptual rows."
::= { system 9 }
sysOREntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"An entry (conceptual row) in the sysORTable."
INDEX { sysORIndex }
::= { sysORTable 1 }
SysOREntry ::= SEQUENCE {
sysORIndex INTEGER
sysORID OBJECT IDENTIFIER
sysORDescr DisplayString
sysORUpTime
sysORIndex OBJECT-
SYNTAX INTEGER (1..2147483647)
MAX-ACCESS not-
STATUS
"The auxiliary variable used for identifying instances
the columnar objects in the sysORTable."
::= { sysOREntry 1 }
sysORID OBJECT-
SYNTAX OBJECT
MAX-ACCESS read-
STATUS
"An authoritative identification of a capabilities
with respect to various MIB modules supported by the
SNMPv2 entity acting in an agent role."
SNMPv2 Working Group Standards Track [Page 6]
RFC 1907 Management Information Base for SNMPv2 January 1996
::= { sysOREntry 2 }
sysORDescr OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"A textual description of the capabilities identified by
corresponding instance of sysORID."
::= { sysOREntry 3 }
sysORUpTime OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The value of sysUpTime at the time this conceptual row
last instanciated."
::= { sysOREntry 4 }
-- the SNMP
--
-- a collection of objects providing basic instrumentation
-- control of an SNMP entity
snmp OBJECT IDENTIFIER ::= { mib-2 11 }
snmpInPkts OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The total number of messages delivered to the SNMP
from the transport service."
::= { snmp 1 }
snmpInBadVersions OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The total number of SNMP messages which were delivered
the SNMP entity and were for an unsupported SNMP version."
::= { snmp 3 }
snmpInBadCommunityNames OBJECT-
SYNTAX Counter32
SNMPv2 Working Group Standards Track [Page 7]
RFC 1907 Management Information Base for SNMPv2 January 1996
MAX-ACCESS read-
STATUS
"The total number of SNMP messages delivered to the
entity which used a SNMP community name not known to
entity."
::= { snmp 4 }
snmpInBadCommunityUses OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The total number of SNMP messages delivered to the
entity which represented an SNMP operation which was
allowed by the SNMP community named in the message."
::= { snmp 5 }
snmpInASNParseErrs OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The total number of ASN.1 or BER errors encountered by
SNMP entity when decoding received SNMP messages."
::= { snmp 6 }
snmpEnableAuthenTraps OBJECT-
SYNTAX INTEGER { enabled(1), disabled(2) }
MAX-ACCESS read-
STATUS
"Indicates whether the SNMP entity is permitted to
authenticationFailure traps. The value of this
overrides any configuration information; as such,
provides a means whereby all authenticationFailure traps
be disabled
Note that it is strongly recommended that this object
stored in non-volatile memory so that it remains
across re-initializations of the network management system."
::= { snmp 30 }
snmpSilentDrops OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
SNMPv2 Working Group Standards Track [Page 8]
RFC 1907 Management Information Base for SNMPv2 January 1996
"The total number of GetRequest-PDUs, GetNextRequest-PDUs
GetBulkRequest-PDUs, SetRequest-PDUs, and InformRequest-
delivered to the SNMP entity which were silently
because the size of a reply containing an
Response-PDU with an empty variable-bindings field
greater than either a local constraint or the
message size associated with the originator of the request."
::= { snmp 31 }
snmpProxyDrops OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The total number of GetRequest-PDUs, GetNextRequest-PDUs
GetBulkRequest-PDUs, SetRequest-PDUs, and InformRequest-
delivered to the SNMP entity which were silently
because the transmission of the (possibly translated
message to a proxy target failed in a manner (other than
time-out) such that no Response-PDU could be returned."
::= { snmp 32 }
-- information for
--
-- a collection of objects which allow the SNMPv2 entity,
-- acting in an agent role, to be configured to
-- SNMPv2-Trap-PDUs
snmpTrap OBJECT IDENTIFIER ::= { snmpMIBObjects 4 }
snmpTrapOID OBJECT-
SYNTAX OBJECT
MAX-ACCESS accessible-for-
STATUS
"The authoritative identification of the
currently being sent. This variable occurs as the
varbind in every SNMPv2-Trap-PDU and InformRequest-PDU."
::= { snmpTrap 1 }
-- ::= { snmpTrap 2 } this OID is
snmpTrapEnterprise OBJECT-
SYNTAX OBJECT
MAX-ACCESS accessible-for-
STATUS
SNMPv2 Working Group Standards Track [Page 9]
RFC 1907 Management Information Base for SNMPv2 January 1996
"The authoritative identification of the
associated with the trap currently being sent. When
SNMPv2 proxy agent is mapping an RFC1157 Trap-PDU into
SNMPv2-Trap-PDU, this variable occurs as the last varbind."
::= { snmpTrap 3 }
-- ::= { snmpTrap 4 } this OID is
-- well-known
snmpTraps OBJECT IDENTIFIER ::= { snmpMIBObjects 5 }
coldStart NOTIFICATION-
STATUS
"A coldStart trap signifies that the SNMPv2 entity,
in an agent role, is reinitializing itself and that
configuration may have been altered."
::= { snmpTraps 1 }
warmStart NOTIFICATION-
STATUS
"A warmStart trap signifies that the SNMPv2 entity,
in an agent role, is reinitializing itself such that
configuration is unaltered."
::= { snmpTraps 2 }
-- Note the linkDown NOTIFICATION-TYPE ::= { snmpTraps 3 }
-- and the linkUp NOTIFICATION-TYPE ::= { snmpTraps 4 }
-- are defined in RFC 1573
authenticationFailure NOTIFICATION-
STATUS
"An authenticationFailure trap signifies that the SNMPv
entity, acting in an agent role, has received a
message that is not properly authenticated. While
implementations of the SNMPv2 must be capable of
this trap, the snmpEnableAuthenTraps object
whether this trap will be generated."
::= { snmpTraps 5 }
-- Note the egpNeighborLoss NOTIFICATION-TYPE ::= { snmpTraps 6 }
-- is defined in RFC 1213
SNMPv2 Working Group Standards Track [Page 10]
RFC 1907 Management Information Base for SNMPv2 January 1996
-- the set
--
-- a collection of objects which allow several
-- SNMPv2 entities, all acting in a manager role,
-- coordinate their use of the SNMPv2 set operation
snmpSet OBJECT IDENTIFIER ::= { snmpMIBObjects 6 }
snmpSetSerialNo OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"An advisory lock used to allow several cooperating SNMPv
entities, all acting in a manager role, to coordinate
use of the SNMPv2 set operation
This object is used for coarse-grain coordination.
achieve fine-grain coordination, one or more similar
might be defined within each MIB group, as appropriate."
::= { snmpSet 1 }
-- conformance
OBJECT IDENTIFIER ::= { snmpMIB 2 }
OBJECT IDENTIFIER ::= { snmpMIBConformance 1 }
snmpMIBGroups OBJECT IDENTIFIER ::= { snmpMIBConformance 2 }
-- compliance
-- ::= { snmpMIBCompliances 1 } this OID is
snmpBasicCompliance MODULE-
STATUS
"The compliance statement for SNMPv2 entities
implement the SNMPv2 MIB."
MODULE -- this
MANDATORY-GROUPS { snmpGroup, snmpSetGroup, systemGroup
snmpBasicNotificationsGroup }
GROUP
SNMPv2 Working Group Standards Track [Page 11]
RFC 1907 Management Information Base for SNMPv2 January 1996
"This group is mandatory for SNMPv2 entities
support community-based authentication."
::= { snmpMIBCompliances 2 }
-- units of
-- ::= { snmpMIBGroups 1 } this OID is
-- ::= { snmpMIBGroups 2 } this OID is
-- ::= { snmpMIBGroups 3 } this OID is
-- ::= { snmpMIBGroups 4 } this OID is
snmpGroup OBJECT-
OBJECTS { snmpInPkts
snmpInBadVersions
snmpInASNParseErrs
snmpSilentDrops
snmpProxyDrops
snmpEnableAuthenTraps }
STATUS
"A collection of objects providing basic instrumentation
control of an SNMPv2 entity."
::= { snmpMIBGroups 8 }
snmpCommunityGroup OBJECT-
OBJECTS { snmpInBadCommunityNames
snmpInBadCommunityUses }
STATUS
"A collection of objects providing basic instrumentation
a SNMPv2 entity which supports community-
authentication."
::= { snmpMIBGroups 9 }
snmpSetGroup OBJECT-
OBJECTS { snmpSetSerialNo }
STATUS
"A collection of objects which allow several
SNMPv2 entities, all acting in a manager role, to
their use of the SNMPv2 set operation."
::= { snmpMIBGroups 5 }
systemGroup OBJECT-
OBJECTS { sysDescr, sysObjectID, sysUpTime
SNMPv2 Working Group Standards Track [Page 12]
RFC 1907 Management Information Base for SNMPv2 January 1996
sysContact, sysName, sysLocation
sysServices
sysORLastChange, sysORID
sysORUpTime, sysORDescr }
STATUS
"The system group defines objects which are common to
managed systems."
::= { snmpMIBGroups 6 }
snmpBasicNotificationsGroup NOTIFICATION-
NOTIFICATIONS { coldStart, authenticationFailure }
STATUS
"The two notifications which an SNMPv2 entity is required
implement."
::= { snmpMIBGroups 7 }
-- definitions in RFC 1213 made obsolete by the inclusion of
-- subset of the snmp group in this
snmpOutPkts OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The total number of SNMP Messages which
passed from the SNMP protocol entity to
transport service."
::= { snmp 2 }
-- { snmp 7 } is not
snmpInTooBigs OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The total number of SNMP PDUs which
delivered to the SNMP protocol entity and
which the value of the error-status field
`tooBig'."
::= { snmp 8 }
snmpInNoSuchNames OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
SNMPv2 Working Group Standards Track [Page 13]
RFC 1907 Management Information Base for SNMPv2 January 1996
STATUS
"The total number of SNMP PDUs which
delivered to the SNMP protocol entity and
which the value of the error-status field
`noSuchName'."
::= { snmp 9 }
snmpInBadValues OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The total number of SNMP PDUs which
delivered to the SNMP protocol entity and
which the value of the error-status field
`badValue'."
::= { snmp 10 }
snmpInReadOnlys OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The total number valid SNMP PDUs which
delivered to the SNMP protocol entity and
which the value of the error-status field
`readOnly'. It should be noted that it is
protocol error to generate an SNMP PDU
contains the value `readOnly' in the error-
field, as such this object is provided as a
of detecting incorrect implementations of
SNMP."
::= { snmp 11 }
snmpInGenErrs OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The total number of SNMP PDUs which
delivered to the SNMP protocol entity and
which the value of the error-status field
`genErr'."
::= { snmp 12 }
snmpInTotalReqVars OBJECT-
SYNTAX Counter32
SNMPv2 Working Group Standards Track [Page 14]
RFC 1907 Management Information Base for SNMPv2 January 1996
MAX-ACCESS read-
STATUS
"The total number of MIB objects which have
retrieved successfully by the SNMP protocol
as the result of receiving valid SNMP Get-
and Get-Next PDUs."
::= { snmp 13 }
snmpInTotalSetVars OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The total number of MIB objects which have
altered successfully by the SNMP protocol
as the result of receiving valid SNMP Set-
PDUs."
::= { snmp 14 }
snmpInGetRequests OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The total number of SNMP Get-Request PDUs
have been accepted and processed by the
protocol entity."
::= { snmp 15 }
snmpInGetNexts OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The total number of SNMP Get-Next PDUs which
been accepted and processed by the SNMP
entity."
::= { snmp 16 }
snmpInSetRequests OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The total number of SNMP Set-Request PDUs
have been accepted and processed by the
protocol entity."
SNMPv2 Working Group Standards Track [Page 15]
RFC 1907 Management Information Base for SNMPv2 January 1996
::= { snmp 17 }
snmpInGetResponses OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The total number of SNMP Get-Response PDUs
have been accepted and processed by the
protocol entity."
::= { snmp 18 }
snmpInTraps OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The total number of SNMP Trap PDUs which
been accepted and processed by the SNMP
entity."
::= { snmp 19 }
snmpOutTooBigs OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The total number of SNMP PDUs which
generated by the SNMP protocol entity and
which the value of the error-status field
`tooBig.'"
::= { snmp 20 }
snmpOutNoSuchNames OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The total number of SNMP PDUs which
generated by the SNMP protocol entity and
which the value of the error-status
`noSuchName'."
::= { snmp 21 }
snmpOutBadValues OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
SNMPv2 Working Group Standards Track [Page 16]
RFC 1907 Management Information Base for SNMPv2 January 1996
"The total number of SNMP PDUs which
generated by the SNMP protocol entity and
which the value of the error-status field
`badValue'."
::= { snmp 22 }
-- { snmp 23 } is not
snmpOutGenErrs OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The total number of SNMP PDUs which
generated by the SNMP protocol entity and
which the value of the error-status field
`genErr'."
::= { snmp 24 }
snmpOutGetRequests OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The total number of SNMP Get-Request PDUs
have been generated by the SNMP protocol entity."
::= { snmp 25 }
snmpOutGetNexts OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The total number of SNMP Get-Next PDUs which
been generated by the SNMP protocol entity."
::= { snmp 26 }
snmpOutSetRequests OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The total number of SNMP Set-Request PDUs
have been generated by the SNMP protocol entity."
::= { snmp 27 }
SNMPv2 Working Group Standards Track [Page 17]
RFC 1907 Management Information Base for SNMPv2 January 1996
snmpOutGetResponses OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The total number of SNMP Get-Response PDUs
have been generated by the SNMP protocol entity."
::= { snmp 28 }
snmpOutTraps OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The total number of SNMP Trap PDUs which
been generated by the SNMP protocol entity."
::= { snmp 29 }
snmpObsoleteGroup OBJECT-
OBJECTS { snmpOutPkts, snmpInTooBigs, snmpInNoSuchNames
snmpInBadValues, snmpInReadOnlys, snmpInGenErrs
snmpInTotalReqVars, snmpInTotalSetVars
snmpInGetRequests, snmpInGetNexts, snmpInSetRequests
snmpInGetResponses, snmpInTraps, snmpOutTooBigs
snmpOutNoSuchNames, snmpOutBadValues, snmpOutGenErrs
snmpOutGetRequests, snmpOutGetNexts, snmpOutSetRequests
snmpOutGetResponses, snmpOutTraps }
STATUS
"A collection of objects from RFC 1213 made obsolete by
MIB."
::= { snmpMIBGroups 10 }
3. Security
Security issues are not discussed in this memo
SNMPv2 Working Group Standards Track [Page 18]
RFC 1907 Management Information Base for SNMPv2 January 1996
4. Editor's
Keith
Cisco Systems, Inc
170 West Tasman
San Jose, CA 95134-1706
Phone: +1 408 526 5260
EMail: kzm@cisco.
5.
This document is the result of significant work by the four
contributors
Jeffrey D. Case (SNMP Research, case@snmp.com
Keith McCloghrie (Cisco Systems, kzm@cisco.com
Marshall T. Rose (Dover Beach Consulting, mrose@dbc.mtview.ca.us
Steven Waldbusser (International Network Services, stevew@uni.ins.com
In addition, the contributions of the SNMPv2 Working Group
acknowledged. In particular, a special thanks is extended for
contributions of
Alexander I. Alten (Novell
Dave Arneson (Cabletron
Uri Blumenthal (IBM
Doug Book (Chipcom
Kim Curran (Bell-Northern Research
Jim Galvin (Trusted Information Systems
Maria Greene (Ascom Timeplex
Iain Hanson (Digital
Dave Harrington (Cabletron
Nguyen Hien (IBM
Jeff Johnson (Cisco Systems
Michael Kornegay (Object Quest
Deirdre Kostick (AT&T Bell Labs
David Levi (SNMP Research
Daniel Mahoney (Cabletron
Bob Natale (ACE*COMM
Brian O'Keefe (Hewlett Packard
Andrew Pearson (SNMP Research
Dave Perkins (Peer Networks
Randy Presuhn (Peer Networks
Aleksey Romanov (Quality Quorum
Shawn Routhier (Epilogue
Jon Saperia (BGS Systems
SNMPv2 Working Group Standards Track [Page 19]
RFC 1907 Management Information Base for SNMPv2 January 1996
Bob Stewart (Cisco Systems, bstewart@cisco.com),
Kaj Tesink (Bellcore
Glenn Waters (Bell-Northern Research
Bert Wijnen (IBM
6.
[1] Information processing systems - Open Systems Interconnection -
Specification of Abstract Syntax Notation One (ASN.1),
International Organization for Standardization.
Standard 8824, (December, 1987).
[2] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M.,
S. Waldbusser, "Structure of Management Information for Version 2
of the Simple Network Management Protocol (SNMPv2)", RFC 1902,
January 1996.
[3] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M.,
S. Waldbusser, "Protocol Operations for Version 2 of the
Network Management Protocol (SNMPv2)", RFC 1905, January 1996.
[4] J.D. Case, C. Partridge, Case Diagrams: A First Step to
Management Information Bases. Computer Communications Review
Volume 19, Number 1, (January, 1989).
SNMPv2 Working Group Standards Track [Page 20]
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
