1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
|
<pre>Network Working Group SNMPv2 Working Group
Request for Comments: 1901 J. Case
Category: Experimental SNMP Research, Inc.
K. McCloghrie
Cisco Systems, Inc.
M. Rose
Dover Beach Consulting, Inc.
S. Waldbusser
International Network Services
January 1996
<span class="h1">Introduction to Community-based SNMPv2</span>
Status of this Memo
This document specifies an Experimental protocol for the Internet
community. This memo does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.
Table of Contents
<a href="#section-1">1</a>. Introduction ................................................ <a href="#page-1">1</a>
<a href="#section-2">2</a>. Components of the SNMPv2 Framework .......................... <a href="#page-2">2</a>
<a href="#section-2.1">2.1</a> Structure of Management Information ........................ <a href="#page-2">2</a>
<a href="#section-2.2">2.2</a> Textual Conventions ........................................ <a href="#page-3">3</a>
<a href="#section-2.3">2.3</a> Conformance Statements ..................................... <a href="#page-3">3</a>
<a href="#section-2.4">2.4</a> Protocol Operations ........................................ <a href="#page-3">3</a>
<a href="#section-2.5">2.5</a> Transport Mappings ......................................... <a href="#page-4">4</a>
<a href="#section-2.6">2.6</a> Protocol Instrumentation ................................... <a href="#page-4">4</a>
<a href="#section-3">3</a>. The Community-based Administrative Framework ................ <a href="#page-4">4</a>
<a href="#section-4">4</a>. Security Considerations ..................................... <a href="#page-5">5</a>
<a href="#section-5">5</a>. Editor's Address ............................................ <a href="#page-6">6</a>
<a href="#section-6">6</a>. Acknowledgements ............................................ <a href="#page-6">6</a>
<a href="#section-7">7</a>. References .................................................. <a href="#page-7">7</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
The purpose of this document is to define the Community-based
Administrative Framework for the SNMP version 2 framework (SNMPv2).
The SNMPv2 framework is fully described in [1-6]. This framework is
derived from the original Internet-standard Network Management
Framework (SNMPv1), which consists of these three documents:
STD 16, <a href="./rfc1155">RFC 1155</a> [<a href="#ref-7" title=""Structure and Identification of Management Information for TCP/IP-based internets"">7</a>] which defines the Structure of Management
Information (SMI), the mechanisms used for describing and naming
objects for the purpose of management.
<span class="grey">SNMPv2 Working Group Experimental [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc1901">RFC 1901</a> Introduction to Community-based SNMPv2 January 1996</span>
STD 16, <a href="./rfc1212">RFC 1212</a> [<a href="#ref-8" title=""Concise MIB Definitions"">8</a>] which defines a more concise description
mechanism, which is wholly consistent with the SMI.
STD 15, <a href="./rfc1157">RFC 1157</a> [<a href="#ref-9" title=""Simple Network Management Protocol"">9</a>] which defines the Simple Network Management
Protocol (SNMP), the protocol used for network access to managed
objects.
For information on coexistence between SNMPv1 and SNMPv2, consult
[<a href="#ref-10" title=""Coexistence between Version 1 and Version 2 of the Internet-standard Network Management Framework"">10</a>].
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Components of the SNMPv2 Framework</span>
A management system contains: several (potentially many) nodes, each
with a processing entity, termed an agent, which has access to
management instrumentation; at least one management station; and, a
management protocol, used to convey management information between
the agents and management stations. Operations of the protocol are
carried out under an administrative framework which defines
authentication, authorization, access control, and privacy policies.
Management stations execute management applications which monitor and
control managed elements. Managed elements are devices such as
hosts, routers, terminal servers, etc., which are monitored and
controlled via access to their management information.
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Structure of Management Information</span>
Management information is viewed as a collection of managed objects,
residing in a virtual information store, termed the Management
Information Base (MIB). Collections of related objects are defined
in MIB modules. These modules are written using a subset of OSI's
Abstract Syntax Notation One (ASN.1) [<a href="#ref-11" title="(December">11</a>]. It is the purpose of the
Structure of Management Information for SNMPv2 document [<a href="#ref-1" title=""Structure of Management Information for Version 2 of the Simple Network Management Protocol (SNMPv2)"">1</a>] to define
that subset.
The SMI is divided into three parts: module definitions, object
definitions, and, trap definitions.
(1) Module definitions are used when describing information modules.
An ASN.1 macro, MODULE-IDENTITY, is used to concisely convey the
semantics of an information module.
(2) Object definitions are used when describing managed objects. An
ASN.1 macro, OBJECT-TYPE, is used to concisely convey the syntax
and semantics of a managed object.
(3) Notification definitions are used when describing unsolicited
transmissions of management information. An ASN.1 macro,
<span class="grey">SNMPv2 Working Group Experimental [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc1901">RFC 1901</a> Introduction to Community-based SNMPv2 January 1996</span>
NOTIFICATION-TYPE, is used to concisely convey the syntax and
semantics of a notification.
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. Textual Conventions</span>
When designing a MIB module, it is often useful to define new types
similar to those defined in the SMI. In comparison to a type defined
in the SMI, each of these new types has a different name, a similar
syntax, but a more precise semantics. These newly defined types are
termed textual conventions, and are used for the convenience of
humans reading the MIB module. It is the purpose of the Textual
Conventions for SNMPv2 document [<a href="#ref-2" title=""Textual Conventions for Version 2 of the Simple Network Management Protocol (SNMPv2)"">2</a>] to define the initial set of
textual conventions available to all MIB modules.
Objects defined using a textual convention are always encoded by
means of the rules that define their primitive type. However,
textual conventions often have special semantics associated with
them. As such, an ASN.1 macro, TEXTUAL-CONVENTION, is used to
concisely convey the syntax and semantics of a textual convention.
<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. Conformance Statements</span>
It may be useful to define the acceptable lower-bounds of
implementation, along with the actual level of implementation
achieved. It is the purpose of the Conformance Statements for SNMPv2
document [<a href="#ref-3" title=""Conformance Statements for Version 2 of the Simple Network Management Protocol (SNMPv2)"">3</a>] to define the notation used for these purposes. There
are two kinds of notations:
(1) Compliance statements are used when describing requirements for
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 of
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 form
a unit of conformance. An ASN.1 macro, OBJECT-GROUP, is used to
concisely convey the syntax and semantics of a group.
<span class="h3"><a class="selflink" id="section-2.4" href="#section-2.4">2.4</a>. Protocol Operations</span>
The management protocol provides for the exchange of messages which
convey management information between the agents and the management
stations. The form of these messages is a message "wrapper" which
encapsulates a Protocol Data Unit (PDU).
<span class="grey">SNMPv2 Working Group Experimental [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc1901">RFC 1901</a> Introduction to Community-based SNMPv2 January 1996</span>
It is the purpose of the Protocol Operations for SNMPv2 document [<a href="#ref-4" title=""Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)"">4</a>]
to define the operations of the protocol with respect to the sending
and receiving of the PDUs.
<span class="h3"><a class="selflink" id="section-2.5" href="#section-2.5">2.5</a>. Transport Mappings</span>
The management protocol, version 2 of the Simple Network Management
Protocol, may be used over a variety of protocol suites. It is the
purpose of the Transport Mappings for SNMPv2 document [<a href="#ref-5" title=""Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2)"">5</a>] to define
how the SNMPv2 maps onto an initial set of transport domains. Other
mappings may be defined in the future.
Although several mappings are defined, the mapping onto UDP is the
preferred mapping. As such, to provide for the greatest level of
interoperability, systems which choose to deploy other mappings
should also provide for proxy service to the UDP mapping.
<span class="h3"><a class="selflink" id="section-2.6" href="#section-2.6">2.6</a>. Protocol Instrumentation</span>
It is the purpose of the Management Information Base for SNMPv2
document [<a href="#ref-6" title=""Management Information Base for Version 2 of the Simple Network Management Protocol (SNMPv2)"">6</a>] to define managed objects which describe the behavior of
a SNMPv2 entity.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. The Community-based Administrative Framework</span>
It is the purpose of an administrative framework to define an
infrastructure through which effective management can be realized in
a variety of configurations and environments. Specified as a part
of, or as extensions of, an administrative framework are security
mechanisms used to achieve an administratively-defined level of
security for protocol interactions.
The administrative framework for SNMPv2 identified in this document
is the same framework as was defined for SNMPv1 [<a href="#ref-9" title=""Simple Network Management Protocol"">9</a>]. This
administrative framework associates each message with a "community"
as defined in [<a href="#ref-9" title=""Simple Network Management Protocol"">9</a>]. Use of this administrative framework with SNMP
Version 2 is commonly known as "Community-based SNMPv2 (SNMPv2C)."
Specifically, Section 3.2.5 of [<a href="#ref-9" title=""Simple Network Management Protocol"">9</a>] defines the concept of a
community, and Section 4.1 of [<a href="#ref-9" title=""Simple Network Management Protocol"">9</a>] defines the Elements of Procedure
for generating and receiving messages. The following updates apply:
(1) The types of access defined in Section 3.2.5 of [<a href="#ref-9" title=""Simple Network Management Protocol"">9</a>] are updated
by [<a href="#ref-1" title=""Structure of Management Information for Version 2 of the Simple Network Management Protocol (SNMPv2)"">1</a>].
(2) The Elements of Procedure defined in Section 4.1 of [<a href="#ref-9" title=""Simple Network Management Protocol"">9</a>] are
updated with the additional requirement of incrementing the
relevant statistics counter as defined in [<a href="#ref-6" title=""Management Information Base for Version 2 of the Simple Network Management Protocol (SNMPv2)"">6</a>].
<span class="grey">SNMPv2 Working Group Experimental [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc1901">RFC 1901</a> Introduction to Community-based SNMPv2 January 1996</span>
(3) The requirement in the Elements of Procedure in Section 4.1 of
[<a href="#ref-9" title=""Simple Network Management Protocol"">9</a>] that the "the source transport address that a response
message is sent from shall be identical to the destination
transport address that the original request message was sent to"
is deleted, i.e., the source transport address of a response
message can be any transport address belonging to the agent.
The form of a message is also taken from [<a href="#ref-9" title=""Simple Network Management Protocol"">9</a>], with the exception that
a new version number is used in the message "wrapper". Use of a new
version number is necessary because of SNMPv2's new PDU types [<a href="#ref-4" title=""Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)"">4</a>],
error codes [<a href="#ref-4" title=""Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)"">4</a>], etc. With this one change, the wrapper becomes:
COMMUNITY-BASED-SNMPv2 DEFINITIONS ::= BEGIN
-- top-level message
Message ::=
SEQUENCE {
version
INTEGER {
version(1) -- modified from <a href="./rfc1157">RFC 1157</a>
},
community -- community name
OCTET STRING,
data -- PDUs as defined in [<a href="#ref-4" title=""Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)"">4</a>]
ANY
}
}
END
Note that with this administrative framework, the
'authorizationError(16)' value defined for the error-status component
of an SNMPv2 PDU [<a href="#ref-4" title=""Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)"">4</a>] is unused. It may, however, be used with future
administrative frameworks.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span>
Security issues are not discussed in this memo.
<span class="grey">SNMPv2 Working Group Experimental [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc1901">RFC 1901</a> Introduction to Community-based SNMPv2 January 1996</span>
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Editor's Address</span>
Keith McCloghrie
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
US
Phone: +1 408 526 5260
EMail: kzm@cisco.com
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Acknowledgements</span>
This document is the result of significant work by the four major
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 are
acknowledged. In particular, a special thanks is extended for the
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)
<span class="grey">SNMPv2 Working Group Experimental [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc1901">RFC 1901</a> Introduction to Community-based SNMPv2 January 1996</span>
Bob Stewart (Cisco Systems, bstewart@cisco.com), chair
Kaj Tesink (Bellcore)
Glenn Waters (Bell-Northern Research)
Bert Wijnen (IBM)
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. References</span>
[<a id="ref-1">1</a>] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and
S. Waldbusser, "Structure of Management Information for Version 2
of the Simple Network Management Protocol (SNMPv2)", <a href="./rfc1902">RFC 1902</a>,
January 1996.
[<a id="ref-2">2</a>] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and
S. Waldbusser, "Textual Conventions for Version 2 of the Simple
Network Management Protocol (SNMPv2)", <a href="./rfc1903">RFC 1903</a>, January 1996.
[<a id="ref-3">3</a>] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and
S. Waldbusser, "Conformance Statements for Version 2 of the Simple
Network Management Protocol (SNMPv2)", <a href="./rfc1904">RFC 1904</a>, January 1996.
[<a id="ref-4">4</a>] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and
S. Waldbusser, "Protocol Operations for Version 2 of the Simple
Network Management Protocol (SNMPv2)", <a href="./rfc1905">RFC 1905</a>, January 1996.
[<a id="ref-5">5</a>] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and
S. Waldbusser, "Transport Mappings for Version 2 of the Simple
Network Management Protocol (SNMPv2)", <a href="./rfc1906">RFC 1906</a>, January 1996.
[<a id="ref-6">6</a>] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and
S. Waldbusser, "Management Information Base for Version 2 of the
Simple Network Management Protocol (SNMPv2)", <a href="./rfc1907">RFC 1907</a>,
January 1996.
[<a id="ref-7">7</a>] Rose, M., and K. McCloghrie, "Structure and Identification of
Management Information for TCP/IP-based internets", STD 16, <a href="./rfc1155">RFC</a>
<a href="./rfc1155">1155</a>, May 1990.
[<a id="ref-8">8</a>] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 16,
<a href="./rfc1212">RFC 1212</a>, March 1991.
[<a id="ref-9">9</a>] Case, J., Fedor, M., Schoffstall, M., Davin, J., "Simple Network
Management Protocol", STD 15, <a href="./rfc1157">RFC 1157</a>, SNMP Research, Performance
Systems International, MIT Laboratory for Computer Science, May
1990.
<span class="grey">SNMPv2 Working Group Experimental [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc1901">RFC 1901</a> Introduction to Community-based SNMPv2 January 1996</span>
[<a id="ref-10">10</a>] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and
S. Waldbusser, "Coexistence between Version 1 and Version 2 of the
Internet-standard Network Management Framework", <a href="./rfc1908">RFC 1908</a>,
January 1996.
[<a id="ref-11">11</a>] Information processing systems - Open Systems Interconnection -
Specification of Abstract Syntax Notation One (ASN.1),
International Organization for Standardization. International
Standard 8824, (December, 1987).
SNMPv2 Working Group Experimental [Page 8]
</pre>
|
