Debian Codegraph @

rfc1749.html

raw
1 <pre>Network Working Group K. McCloghrie
2 Request for Comments: 1749 F. Baker
3 Updates: <a href="./rfc1748">1748</a> E. Decker
4 Category: Standards Track cisco Systems, Inc.
5 December 1994
6
7
8 <span class="h1">IEEE 802.5 Station Source Routing MIB using SMIv2</span>
9
10 Status of this Memo
11
12 This document specifies an Internet standards track protocol for the
13 Internet community, and requests discussion and suggestions for
14 improvements. Please refer to the current edition of the "Internet
15 Official Protocol Standards" (STD 1) for the standardization state
16 and status of this protocol. Distribution of this memo is unlimited.
17
18 Table of Contents
19
20 <a href="#section-1">1</a>. Introduction ............................................. <a href="#page-1">1</a>
21 <a href="#section-2">2</a>. The SNMPv2 Network Management Framework .................. <a href="#page-2">2</a>
22 <a href="#section-2.1">2.1</a> Object Definitions ...................................... <a href="#page-2">2</a>
23 <a href="#section-3">3</a>. Overview ................................................. <a href="#page-2">2</a>
24 <a href="#section-3.1">3.1</a> Source Routing .......................................... <a href="#page-2">2</a>
25 <a href="#section-3.2">3.2</a> Relationship to <a href="./rfc1748">RFC 1748</a> ................................ <a href="#page-3">3</a>
26 <a href="#section-3.3">3.3</a> Relationship to <a href="./rfc1525">RFC 1525</a> ................................ <a href="#page-3">3</a>
27 <a href="#section-3.4">3.4</a> Static Source Routes .................................... <a href="#page-4">4</a>
28 <a href="#section-3.5">3.5</a> Destinations on the Local Ring .......................... <a href="#page-4">4</a>
29 <a href="#section-4">4</a>. Definitions .............................................. <a href="#page-4">4</a>
30 <a href="#section-5">5</a>. Acknowledgements ......................................... <a href="#page-8">8</a>
31 <a href="#section-6">6</a>. References ............................................... <a href="#page-8">8</a>
32 <a href="#section-7">7</a>. Security Considerations .................................. <a href="#page-9">9</a>
33 <a href="#section-8">8</a>. Authors' Addresses ....................................... <a href="#page-10">10</a>
34
35 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
36
37 This memo defines a portion of the Management Information Base (MIB)
38 for use with network management protocols in the Internet community.
39 In particular, it describes managed objects used by IEEE 802.5 end-
40 stations for managing source routes on a Token Ring network where
41 IEEE source-routing is in use. IEEE source-routing is described in
42 802.5 Token Ring Access Method and Physical Layer Specifications [<a href="#ref-8" title="&quot;Token Ring Access Method and Physical Layer Specifications&quot;">8</a>]
43 and related ISO publications [<a href="#ref-9" title="&quot;Information technology - Local and metropolitan area networks - Part 5: Token ring access method and physical layer specifications&quot;">9</a>, <a href="#ref-10" title="&quot;Information technology - Telecommunications and information exchange between systems - Local area networks - Media access control (MAC) bridges&quot;">10</a>, <a href="#ref-11" title="&quot;Source Routing Operation by End Systems&quot;">11</a>].
44
45 This memo is an incremental update to <a href="./rfc1748">RFC 1748</a> [<a href="#ref-6" title="&quot;IEEE 802.5 Token Ring MIB using SMIv2&quot;">6</a>]. It is documented
46 separately from the <a href="./rfc1748">RFC 1748</a> solely due to the latter's maturity
47 within the Internet standardization process.
48
49
50
51
52 <span class="grey">McCloghrie, Baker &amp; Decker [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc1749">RFC 1749</a> 802.5 Station Source Routing MIB using SMIv2 December 1994</span>
55
56
57 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. The SNMPv2 Network Management Framework</span>
58
59 The SNMPv2 Network Management Framework consists of four major
60 components. They are:
61
62 o <a href="./rfc1442">RFC 1442</a> [<a href="#ref-1" title="&quot;Structure of Management Information for version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">1</a>] which defines the SMI, the mechanisms used for
63 describing and naming objects for the purpose of management.
64
65 o STD 17, <a href="./rfc1213">RFC 1213</a> [<a href="#ref-2" title="&quot;Management Information Base for Network Management of TCP/IP-based internets: MIB- II&quot;">2</a>] defines MIB-II, the core set of managed
66 objects for the Internet suite of protocols.
67
68 o <a href="./rfc1445">RFC 1445</a> [<a href="#ref-3" title="&quot;Administrative Model for version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">3</a>] which defines the administrative and other
69 architectural aspects of the framework.
70
71 o <a href="./rfc1448">RFC 1448</a> [<a href="#ref-4" title="&quot;Protocol Operations for version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">4</a>] which defines the protocol used for network
72 access to managed objects.
73
74 The Framework permits new objects to be defined for the purpose of
75 experimentation and evaluation.
76
77 <span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Object Definitions</span>
78
79 Managed objects are accessed via a virtual information store, termed
80 the Management Information Base or MIB. Objects in the MIB are
81 defined using the subset of Abstract Syntax Notation One (ASN.1)
82 defined in the SMI. In particular, each object type is named by an
83 OBJECT IDENTIFIER, an administratively assigned name. The object
84 type together with an object instance serves to uniquely identify a
85 specific instantiation of the object. For human convenience, we
86 often use a textual string, termed the descriptor, to refer to the
87 object type.
88
89 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Overview</span>
90
91 This memo defines a single table: the 802.5 Station Source Routing
92 Table, which contains the source routes known by a end-station on an
93 IEEE 802.5 Token Ring network in which IEEE source-routing is in use.
94
95 <span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Source Routing</span>
96
97 Source routing extends the 802.5 protocol [<a href="#ref-8" title="&quot;Token Ring Access Method and Physical Layer Specifications&quot;">8</a>] by assigning a unique
98 ring number to each ring within the extended LAN, and a bridge number
99 to each source routing bridge's connection to a ring. A Routing
100 Information Field (RIF) must be included in frames which need to
101 traverse multiple rings. The format of the RIF is:
102
103
104
105
106
107
108 <span class="grey">McCloghrie, Baker &amp; Decker [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc1749">RFC 1749</a> 802.5 Station Source Routing MIB using SMIv2 December 1994</span>
111
112
113 octets octets octets octets
114 1&amp;2 3&amp;4 5&amp;6 17&amp;18
115 +------+------+------+-------+------+
116 | RC | RD | RD | ... | RD |
117 +------+------+------+-------+------+
118 &lt;---- 0 to 8 RD fields ----&gt;
119
120 The format of the Routing Control (RC) field is:
121
122 octet 1 octet 2
123 +---------------+---------------+
124 |b b b l l l l l|d f f f 0 0 0 0|
125 +---------------+---------------+
126 ^ ^ ^ ^
127 | | | |
128 Explorer indicator --+ | | +-- Max frame length*
129 Length of RIF field --+ +-- Direction to use RDs
130
131 * Note that the length of the Maximum frame length subfield
132 has recently been extended to 6 bits.
133
134 The format of each Routing Descriptor (RD) field is:
135
136 octet 1 octet 2
137 +---------------+---------------+
138 |r r r r r r r r r r r r i i i i|
139 +---------------+---------------+
140 &lt;---- ring number ----&gt; &lt;-----&gt;
141 ^
142 |
143 bridge number --+
144
145 <span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Relationship to <a href="./rfc1748">RFC 1748</a></span>
146
147 <a href="./rfc1748">RFC 1748</a> [<a href="#ref-6" title="&quot;IEEE 802.5 Token Ring MIB using SMIv2&quot;">6</a>], the IEEE 802.5 MIB, defines managed objects used for
148 interfaces to IEEE 802.5 Token Ring subnetworks. This memo is an
149 incremental update to <a href="./rfc1748">RFC 1748</a>, and is documented independently
150 solely due to the maturity of the definitions contained within <a href="./rfc1748">RFC</a>
151 <a href="./rfc1748">1748</a>.
152
153 <span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. Relationship to <a href="./rfc1525">RFC 1525</a></span>
154
155 <a href="./rfc1525">RFC 1525</a> [<a href="#ref-7" title="&quot;Definitions of Managed Objects for Source Routing Bridges&quot;">7</a>] defines the MIB objects specific to source-routing for
156 source-routing and SRT bridges. This memo defines the MIB objects
157 specific to source-routing for source-routing end-stations.
158
159
160
161
162
163
164 <span class="grey">McCloghrie, Baker &amp; Decker [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc1749">RFC 1749</a> 802.5 Station Source Routing MIB using SMIv2 December 1994</span>
167
168
169 <span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. Static Source Routes</span>
170
171 It is unclear how many, if any, existing systems allow the creation
172 or deletion of "static" 802.5 source routes by network management.
173 However, SNMPv2 SMI defines that the MAX-ACCESS clause as specifying
174 the maximal level of access which makes "protocol sense". Thus, this
175 memo provides support for static source routes through the
176 dot5SrRouteStatus object, but the conformance statements allow for
177 stations which do not support static source routes, by requiring that
178 compliant agents only need provide read-access to dot5SrRouteStatus.
179
180 <span class="h3"><a class="selflink" id="section-3.5" href="#section-3.5">3.5</a>. Destinations on the Local Ring</span>
181
182 Entries should be included in the dot5SrRouteTable for destination
183 MAC addresses which are on the same ring as the instrumented 802.5
184 interface. For such entries, dot5SrRouteDescr has the value of the
185 zero-length string, and dot5SrRouteControl has the corresponding
186 value.
187
188 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Definitions</span>
189
190 TOKENRING-STATION-SR-MIB DEFINITIONS ::= BEGIN
191
192 IMPORTS
193 MODULE-IDENTITY, OBJECT-TYPE
194 FROM SNMPv2-SMI
195 TEXTUAL-CONVENTION, RowStatus, MacAddress
196 FROM SNMPv2-TC
197 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF
198 mib-2, ifIndex FROM <a href="./rfc1213">RFC1213</a>-MIB;
199
200 dot5SrMIB MODULE-IDENTITY
201 LAST-UPDATED "9412161000Z"
202 ORGANIZATION "IETF Interfaces MIB Working Group"
203 CONTACT-INFO
204 " Keith McCloghrie
205 Postal: Cisco Systems, Inc.
206 170 West Tasman Drive
207 San Jose, CA 95134-1706
208 US
209
210 Phone: +1 408 526 5260
211 Email: [email protected]"
212 DESCRIPTION
213 "The MIB module for managing source routes in
214 end-stations on IEEE 802.5 Token Ring networks."
215 ::= { mib-2 42 }
216
217
218
219
220 <span class="grey">McCloghrie, Baker &amp; Decker [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc1749">RFC 1749</a> 802.5 Station Source Routing MIB using SMIv2 December 1994</span>
223
224
225 dot5SrMIBObjects OBJECT IDENTIFIER ::= { dot5SrMIB 1 }
226
227 SourceRoute ::= TEXTUAL-CONVENTION
228 DISPLAY-HINT "1x:"
229 STATUS current
230 DESCRIPTION
231 "Represents a Source Route, containing an
232 embedded sequence of bridge and ring ID's,
233 as used by 802.5 Source Routing."
234 REFERENCE "Annex C of ISO/IEC 10038: 1993,
235 [ANSI/IEEE Std 802.1D, 1993]"
236 SYNTAX OCTET STRING (SIZE(0..30))
237
238
239 -- The 802.5 Station Source Route Table
240 --
241
242 dot5SrRouteTable OBJECT-TYPE
243 SYNTAX SEQUENCE OF Dot5SrRouteEntry
244 MAX-ACCESS not-accessible
245 STATUS current
246 DESCRIPTION
247 "The table of source-routing routes.
248 This represents the 802.5 RIF database."
249 ::= { dot5SrMIBObjects 1 }
250
251 dot5SrRouteEntry OBJECT-TYPE
252 SYNTAX Dot5SrRouteEntry
253 MAX-ACCESS not-accessible
254 STATUS current
255 DESCRIPTION
256 "Information on a specific route.
257
258 An entry is created whenever a 'Single Path
259 Explorer' or an 'All Paths Explorer' discovers
260 a route to a neighbor not currently in the table,
261 or whenever an 'All Paths Explorer' discovers a
262 better (e.g., shorter) route than the route currently
263 stored in the table. This is done on behalf of
264 any network layer client.
265
266 The ifIndex value in the INDEX clause refers to
267 the value of MIB-II's ifIndex object for the
268 interface on which the route is in effect."
269 INDEX { ifIndex, dot5SrRouteDestination }
270 ::= { dot5SrRouteTable 1 }
271
272 Dot5SrRouteEntry ::= SEQUENCE {
273
274
275
276 <span class="grey">McCloghrie, Baker &amp; Decker [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc1749">RFC 1749</a> 802.5 Station Source Routing MIB using SMIv2 December 1994</span>
279
280
281 dot5SrRouteDestination MacAddress,
282 dot5SrRouteControl OCTET STRING,
283 dot5SrRouteDescr SourceRoute,
284 dot5SrRouteStatus RowStatus
285 }
286
287 dot5SrRouteDestination OBJECT-TYPE
288 SYNTAX MacAddress
289 MAX-ACCESS not-accessible
290 STATUS current
291 DESCRIPTION
292 "The destination of this route."
293 ::= { dot5SrRouteEntry 2 }
294
295 dot5SrRouteControl OBJECT-TYPE
296 SYNTAX OCTET STRING (SIZE(2))
297 MAX-ACCESS read-create
298 STATUS current
299 DESCRIPTION
300 "The value of Routing Control field for this
301 route."
302 REFERENCE "Annex C of ISO/IEC 10038: 1993,
303 [ANSI/IEEE Std 802.1D, 1993]"
304 ::= { dot5SrRouteEntry 3 }
305
306 dot5SrRouteDescr OBJECT-TYPE
307 SYNTAX SourceRoute
308 MAX-ACCESS read-create
309 STATUS current
310 DESCRIPTION
311 "The embedded sequence of bridge and ring ID's
312 for this route. For destinations on the
313 local ring, the value of this object is
314 the zero-length string."
315 REFERENCE "Annex C of ISO/IEC 10038: 1993,
316 [ANSI/IEEE Std 802.1D, 1993]"
317 ::= { dot5SrRouteEntry 4 }
318
319 dot5SrRouteStatus OBJECT-TYPE
320 SYNTAX RowStatus
321 MAX-ACCESS read-create
322 STATUS current
323 DESCRIPTION
324 "The status of this row. Values of the instances
325 of dot5SrRouteControl and dot5SrRouteDescr can be
326 modified while the row's status is 'active."
327 ::= { dot5SrRouteEntry 5 }
328
329
330
331
332 <span class="grey">McCloghrie, Baker &amp; Decker [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc1749">RFC 1749</a> 802.5 Station Source Routing MIB using SMIv2 December 1994</span>
335
336
337 -- conformance information
338
339 dot5SrConformance OBJECT IDENTIFIER ::= { dot5SrMIB 2 }
340
341 dot5SrGroups OBJECT IDENTIFIER ::= { dot5SrConformance 1 }
342 dot5SrCompliances OBJECT IDENTIFIER ::= { dot5SrConformance 2 }
343
344
345 -- compliance statements
346
347 dot5SrCompliance MODULE-COMPLIANCE
348 STATUS current
349 DESCRIPTION
350 "The compliance statement for SNMPv2 entities
351 which implement the IEEE 802.5 Station Source Route
352 MIB."
353
354 MODULE -- this module
355 MANDATORY-GROUPS { dot5SrRouteGroup }
356
357 OBJECT dot5SrRouteStatus
358 SYNTAX INTEGER { active(1) } -- subset of values
359 MIN-ACCESS read-only
360 DESCRIPTION
361 "Write access is not required, and only the 'active'
362 value need be supported."
363
364 OBJECT dot5SrRouteControl
365 MIN-ACCESS read-only
366 DESCRIPTION
367 "Write access is not required."
368
369 OBJECT dot5SrRouteDescr
370 MIN-ACCESS read-only
371 DESCRIPTION
372 "Write access is not required."
373
374 ::= { dot5SrCompliances 1 }
375
376
377 -- units of conformance
378
379 dot5SrRouteGroup OBJECT-GROUP
380 OBJECTS { dot5SrRouteControl,
381 dot5SrRouteDescr,
382 dot5SrRouteStatus
383 }
384 STATUS current
385
386
387
388 <span class="grey">McCloghrie, Baker &amp; Decker [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc1749">RFC 1749</a> 802.5 Station Source Routing MIB using SMIv2 December 1994</span>
391
392
393 DESCRIPTION
394 "A collection of objects providing for the management of
395 source routes in stations on IEEE 802.5 source-routing
396 networks."
397 ::= { dot5SrGroups 1 }
398
399 END
400
401 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Acknowledgements</span>
402
403 The need for this MIB module was agreed upon by the members of the
404 IETF Interfaces Working Group, and the definitions were derived from
405 experience with enterprise-specific MIBs presented to the Working
406 Group.
407
408 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. References</span>
409
410 [<a id="ref-1">1</a>] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure
411 of Management Information for version 2 of the Simple Network
412 Management Protocol (SNMPv2)", <a href="./rfc1442">RFC 1442</a>, SNMP Research,Inc.,
413 Hughes LAN Systems, Dover Beach Consulting, Inc., Carnegie Mellon
414 University, April 1993.
415
416 [<a id="ref-2">2</a>] McCloghrie, K., and M. Rose, Editors, "Management Information
417 Base for Network Management of TCP/IP-based internets: MIB- II",
418 STD 17, <a href="./rfc1213">RFC 1213</a>, Hughes LAN Systems, Performance Systems
419 International, March 1991.
420
421 [<a id="ref-3">3</a>] Galvin, J., and K. McCloghrie, "Administrative Model for version
422 2 of the Simple Network Management Protocol (SNMPv2)", <a href="./rfc1445">RFC 1445</a>,
423 Trusted Information Systems, Hughes LAN Systems, April 1993.
424
425 [<a id="ref-4">4</a>] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol
426 Operations for version 2 of the Simple Network Management
427 Protocol (SNMPv2)", <a href="./rfc1448">RFC 1448</a>, SNMP Research,Inc., Hughes LAN
428 Systems, Dover Beach Consulting, Inc., Carnegie Mellon
429 University, April 1993.
430
431 [<a id="ref-5">5</a>] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual
432 Conventions for version 2 of the Simple Network Management
433 Protocol (SNMPv2)", <a href="./rfc1443">RFC 1443</a>, SNMP Research Inc., Hughes LAN
434 Systems, Dover Beach Consulting, Inc., Carnegie Mellon
435 University, April 1993.
436
437 [<a id="ref-6">6</a>] McCloghrie, K., and E. Decker, "IEEE 802.5 Token Ring MIB using
438 SMIv2", <a href="./rfc1748">RFC 1748</a> cisco Systems, Inc., December 1994.
439
440
441
442
443
444 <span class="grey">McCloghrie, Baker &amp; Decker [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc1749">RFC 1749</a> 802.5 Station Source Routing MIB using SMIv2 December 1994</span>
447
448
449 [<a id="ref-7">7</a>] McCloghrie, K., Decker, E., Langville, P., and A. Rijsinghani,
450 "Definitions of Managed Objects for Source Routing Bridges", <a href="./rfc1525">RFC</a>
451 <a href="./rfc1525">1525</a>, Hughes LAN Systems, cisco Systems, Inc., Digital Equipment
452 Corporation, September 1993.
453
454 [<a id="ref-8">8</a>] "Token Ring Access Method and Physical Layer Specifications",
455 IEEE Standard 802.5-1989, 1989.
456
457 [<a id="ref-9">9</a>] "Information technology - Local and metropolitan area networks -
458 Part 5: Token ring access method and physical layer
459 specifications", ISO/IEC 8802-5, 1992.
460
461 [<a id="ref-10">10</a>] "Information technology - Telecommunications and information
462 exchange between systems - Local area networks - Media access
463 control (MAC) bridges", ISO/IEC 10038, 1993 [ANSI/IEEE Std
464 802.1D, 1993 Edition].
465
466 [<a id="ref-11">11</a>] "Source Routing Operation by End Systems", ISO/IEC 8802-2 PDAM5.3
467 (6N7721).
468
469 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Security Considerations</span>
470
471 Security issues are not discussed in this memo.
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500 <span class="grey">McCloghrie, Baker &amp; Decker [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc1749">RFC 1749</a> 802.5 Station Source Routing MIB using SMIv2 December 1994</span>
503
504
505 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Authors' Addresses</span>
506
507 Keith McCloghrie
508 cisco Systems, Inc.
509 170 West Tasman Drive,
510 San Jose CA 95134-1706.
511
512 Phone: (408) 526-5260
513 EMail: [email protected]
514
515
516 Fred Baker
517 cisco Systems, Inc.
518 519 Lado Drive
519 Santa Barbara, CA 93111
520
521 Phone: (805) 681-0115
522 EMail: [email protected]
523
524
525 Eric B. Decker
526 cisco Systems, Inc.
527 1525 O'Brien Dr.
528 Menlo Park, California 94025
529
530 Phone: (415) 688-8241
531 EMail: [email protected]
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556 McCloghrie, Baker &amp; Decker [Page 10]
557 </pre>