As per Relevance of the word administrative, we have this rfc below:
Network Working Group SNMPv2 Working
Request for Comments: 1901 J.
Category: Experimental SNMP Research, Inc
K.
Cisco Systems, Inc
M.
Dover Beach Consulting, Inc
S.
International Network
January 1996
Introduction to Community-based SNMPv
Status of this
This document specifies an Experimental protocol for the
community. This memo does not specify an Internet standard of
kind. Discussion and suggestions for improvement are requested
Distribution of this memo is unlimited
Table of
1. Introduction ................................................ 1
2. Components of the SNMPv2 Framework .......................... 2
2.1 Structure of Management Information ........................ 2
2.2 Textual Conventions ........................................ 3
2.3 Conformance Statements ..................................... 3
2.4 Protocol Operations ........................................ 3
2.5 Transport Mappings ......................................... 4
2.6 Protocol Instrumentation ................................... 4
3. The Community-based Administrative Framework ................ 4
4. Security Considerations ..................................... 5
5. Editor's Address ............................................ 6
6. Acknowledgements ............................................ 6
7. References .................................................. 7
1.
The purpose of this document is to define the Community-
Administrative Framework for the SNMP version 2 framework (SNMPv2).
The SNMPv2 framework is fully described in [1-6]. This framework
derived from the original Internet-standard Network
Framework (SNMPv1), which consists of these three documents
STD 16, RFC 1155 [7] which defines the Structure of
Information (SMI), the mechanisms used for describing and
objects for the purpose of management
SNMPv2 Working Group Experimental [Page 1]
RFC 1901 Introduction to Community-based SNMPv2 January 1996
STD 16, RFC 1212 [8] which defines a more concise
mechanism, which is wholly consistent with the SMI
STD 15, RFC 1157 [9] which defines the Simple Network
Protocol (SNMP), the protocol used for network access to
objects
For information on coexistence between SNMPv1 and SNMPv2,
[10].
2. Components of the SNMPv2
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
2.1. Structure of Management
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) [11]. It is the purpose of
Structure of Management Information for SNMPv2 document [1] to
that subset
The SMI is divided into three parts: module definitions,
definitions, and, trap definitions
(1) Module definitions are used when describing information modules
An ASN.1 macro, MODULE-IDENTITY, is used to concisely convey
semantics of an information module
(2) Object definitions are used when describing managed objects.
ASN.1 macro, OBJECT-TYPE, is used to concisely convey the
and semantics of a managed object
(3) Notification definitions are used when describing
transmissions of management information. An ASN.1 macro
SNMPv2 Working Group Experimental [Page 2]
RFC 1901 Introduction to Community-based SNMPv2 January 1996
NOTIFICATION-TYPE, is used to concisely convey the syntax
semantics of a notification
2.2. Textual
When designing a MIB module, it is often useful to define new
similar to those defined in the SMI. In comparison to a type
in the SMI, each of these new types has a different name, a
syntax, but a more precise semantics. These newly defined types
termed textual conventions, and are used for the convenience
humans reading the MIB module. It is the purpose of the
Conventions for SNMPv2 document [2] to define the initial set
textual conventions available to all MIB modules
Objects defined using a textual convention are always encoded
means of the rules that define their primitive type. However
textual conventions often have special semantics associated
them. As such, an ASN.1 macro, TEXTUAL-CONVENTION, is used
concisely convey the syntax and semantics of a textual convention
2.3. Conformance
It may be useful to define the acceptable lower-bounds
implementation, along with the actual level of
achieved. It is the purpose of the Conformance Statements for SNMPv
document [3] to define the notation used for these purposes.
are two kinds of notations
(1) Compliance statements are used when describing requirements
agents with respect to object definitions. An ASN.1 macro
MODULE-COMPLIANCE, is used to concisely convey such requirements
(2) Capability statements are used when describing capabilities
agents with respect to object definitions. An ASN.1 macro, AGENT
CAPABILITIES, is used to concisely convey such capabilities
Finally, collections of related objects are grouped together to
a unit of conformance. An ASN.1 macro, OBJECT-GROUP, is used
concisely convey the syntax and semantics of a group
2.4. Protocol
The management protocol provides for the exchange of messages
convey management information between the agents and the
stations. The form of these messages is a message "wrapper"
encapsulates a Protocol Data Unit (PDU).
SNMPv2 Working Group Experimental [Page 3]
RFC 1901 Introduction to Community-based SNMPv2 January 1996
It is the purpose of the Protocol Operations for SNMPv2 document [4]
to define the operations of the protocol with respect to the
and receiving of the PDUs
2.5. Transport
The management protocol, version 2 of the Simple Network
Protocol, may be used over a variety of protocol suites. It is
purpose of the Transport Mappings for SNMPv2 document [5] to
how the SNMPv2 maps onto an initial set of transport domains.
mappings may be defined in the future
Although several mappings are defined, the mapping onto UDP is
preferred mapping. As such, to provide for the greatest level
interoperability, systems which choose to deploy other
should also provide for proxy service to the UDP mapping
2.6. Protocol
It is the purpose of the Management Information Base for SNMPv
document [6] to define managed objects which describe the behavior
a SNMPv2 entity
3. The Community-based Administrative
It is the purpose of an administrative framework to define
infrastructure through which effective management can be realized
a variety of configurations and environments. Specified as a
of, or as extensions of, an administrative framework are
mechanisms used to achieve an administratively-defined level
security for protocol interactions
The administrative framework for SNMPv2 identified in this
is the same framework as was defined for SNMPv1 [9].
administrative framework associates each message with a "community
as defined in [9]. Use of this administrative framework with
Version 2 is commonly known as "Community-based SNMPv2 (SNMPv2C)."
Specifically, Section 3.2.5 of [9] defines the concept of
community, and Section 4.1 of [9] defines the Elements of
for generating and receiving messages. The following updates apply
(1) The types of access defined in Section 3.2.5 of [9] are
by [1].
(2) The Elements of Procedure defined in Section 4.1 of [9]
updated with the additional requirement of incrementing
relevant statistics counter as defined in [6].
SNMPv2 Working Group Experimental [Page 4]
RFC 1901 Introduction to Community-based SNMPv2 January 1996
(3) The requirement in the Elements of Procedure in Section 4.1
[9] that the "the source transport address that a
message is sent from shall be identical to the
transport address that the original request message was sent to
is deleted, i.e., the source transport address of a
message can be any transport address belonging to the agent
The form of a message is also taken from [9], with the exception
a new version number is used in the message "wrapper". Use of a
version number is necessary because of SNMPv2's new PDU types [4],
error codes [4], etc. With this one change, the wrapper becomes
COMMUNITY-BASED-SNMPv2 DEFINITIONS ::=
-- top-level
Message ::=
SEQUENCE {
INTEGER {
version(1) -- modified from RFC 1157
},
community -- community
OCTET STRING
data -- PDUs as defined in [4]
}
}
Note that with this administrative framework,
'authorizationError(16)' value defined for the error-status
of an SNMPv2 PDU [4] is unused. It may, however, be used with
administrative frameworks
4. Security
Security issues are not discussed in this memo
SNMPv2 Working Group Experimental [Page 5]
RFC 1901 Introduction to Community-based SNMPv2 January 1996
5. Editor's
Keith
Cisco Systems, Inc
170 West Tasman
San Jose, CA 95134-1706
Phone: +1 408 526 5260
EMail: kzm@cisco.
6.
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 Experimental [Page 6]
RFC 1901 Introduction to Community-based SNMPv2 January 1996
Bob Stewart (Cisco Systems, bstewart@cisco.com),
Kaj Tesink (Bellcore
Glenn Waters (Bell-Northern Research
Bert Wijnen (IBM
7.
[1] 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.
[2] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M.,
S. Waldbusser, "Textual Conventions for Version 2 of the
Network Management Protocol (SNMPv2)", RFC 1903, January 1996.
[3] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M.,
S. Waldbusser, "Conformance Statements for Version 2 of the
Network Management Protocol (SNMPv2)", RFC 1904, January 1996.
[4] 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.
[5] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M.,
S. Waldbusser, "Transport Mappings for Version 2 of the
Network Management Protocol (SNMPv2)", RFC 1906, January 1996.
[6] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M.,
S. Waldbusser, "Management Information Base for Version 2 of
Simple Network Management Protocol (SNMPv2)", RFC 1907,
January 1996.
[7] Rose, M., and K. McCloghrie, "Structure and Identification
Management Information for TCP/IP-based internets", STD 16,
1155, May 1990.
[8] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 16,
RFC 1212, March 1991.
[9] Case, J., Fedor, M., Schoffstall, M., Davin, J., "Simple
Management Protocol", STD 15, RFC 1157, SNMP Research,
Systems International, MIT Laboratory for Computer Science,
1990.
SNMPv2 Working Group Experimental [Page 7]
RFC 1901 Introduction to Community-based SNMPv2 January 1996
[10] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M.,
S. Waldbusser, "Coexistence between Version 1 and Version 2 of
Internet-standard Network Management Framework", RFC 1908,
January 1996.
[11] Information processing systems - Open Systems Interconnection -
Specification of Abstract Syntax Notation One (ASN.1),
International Organization for Standardization.
Standard 8824, (December, 1987).
SNMPv2 Working Group Experimental [Page 8]
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
