Debian Codegraph @

rfc1748.html

raw
1 <pre>Network Working Group K. McCloghrie
2 Request for Comments: 1748 E. Decker
3 Obsoletes: <a href="./rfc1743">1743</a>, <a href="./rfc1231">1231</a> cisco Systems, Inc.
4 Category: Standards Track December 1994
5
6
7 <span class="h1">IEEE 802.5 MIB using SMIv2</span>
8
9 Status of this Memo
10
11 This document specifies an Internet standards track protocol for the
12 Internet community, and requests discussion and suggestions for
13 improvements. Please refer to the current edition of the "Internet
14 Official Protocol Standards" (STD 1) for the standardization state
15 and status of this protocol. Distribution of this memo is unlimited.
16
17 Table of Contents
18
19 <a href="#section-1">1</a>. Introduction ............................................. <a href="#page-1">1</a>
20 <a href="#section-2">2</a>. The SNMPv2 Network Management Framework .................. <a href="#page-2">2</a>
21 <a href="#section-2.1">2.1</a> Object Definitions ...................................... <a href="#page-2">2</a>
22 <a href="#section-3">3</a>. Overview ................................................. <a href="#page-2">2</a>
23 <a href="#section-3.1">3.1</a> MAC Addresses ........................................... <a href="#page-3">3</a>
24 <a href="#section-3.2">3.2</a> Relationship to <a href="./rfc1213">RFC 1213</a> ................................ <a href="#page-3">3</a>
25 <a href="#section-3.3">3.3</a> Relationship to <a href="./rfc1573">RFC 1573</a> ................................ <a href="#page-3">3</a>
26 <a href="#section-3.3.1">3.3.1</a> Layering Model ........................................ <a href="#page-3">3</a>
27 <a href="#section-3.3.2">3.3.2</a> Virtual Circuits ...................................... <a href="#page-3">3</a>
28 <a href="#section-3.3.3">3.3.3</a> ifTestTable ........................................... <a href="#page-3">3</a>
29 <a href="#section-3.3.4">3.3.4</a> ifRcvAddressTable ..................................... <a href="#page-4">4</a>
30 <a href="#section-3.3.5">3.3.5</a> ifPhysAddress ......................................... <a href="#page-4">4</a>
31 <a href="#section-3.3.6">3.3.6</a> ifType ................................................ <a href="#page-4">4</a>
32 <a href="#section-4">4</a>. Definitions .............................................. <a href="#page-4">4</a>
33 <a href="#section-5">5</a>. Acknowledgements ......................................... <a href="#page-23">23</a>
34 <a href="#section-6">6</a>. References ............................................... <a href="#page-23">23</a>
35 <a href="#appendix-A">Appendix A</a>. Changes from <a href="./rfc1231">RFC 1231</a> ........................... <a href="#page-24">24</a>
36 Security Considerations ..................................... <a href="#page-24">24</a>
37 Authors' Addresses .......................................... <a href="#page-25">25</a>
38
39 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
40
41 This memo defines a portion of the Management Information Base (MIB)
42 for use with network management protocols in the Internet community.
43 In particular, it describes managed objects used for managing
44 subnetworks which use the IEEE 802.5 Token Ring technology described
45 in 802.5 Token Ring Access Method and Physical Layer Specifications,
46 IEEE Standard 802.5-1989 [<a href="#ref-7" title="&quot;Token Ring Access Method and Physical Layer Specifications&quot;">7</a>]. This memo is a replacement for <a href="./rfc1231">RFC</a>
47 <a href="./rfc1231">1231</a>.
48
49
50
51
52 <span class="grey">McCloghrie &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="./rfc1748">RFC 1748</a> IEEE 802.5 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 three tables: the 802.5 Interface Table, which
92 contains state and parameter information which is specific to 802.5
93 interfaces, the 802.5 Statistics Table, which contains 802.5
94 interface statistics, and the 802.5 Timer Table, which contains the
95 values of 802.5-defined timers. A managed system will have one entry
96 in the 802.5 Interface Table and one entry in the 802.5 Statistics
97 Table for each of its 802.5 interfaces. The 802.5 Timer Table is
98 obsolete, but its definition has been retained in this memo for
99 backward compatibility.
100
101 This memo also defines OBJECT IDENTIFIERs, some to identify interface
102 tests for use with the ifTestTable [<a href="#ref-6" title="&quot;Evolution of the Interfaces Group of MIB-II&quot;">6</a>], and some to identify Token
103 Ring interface Chip Sets.
104
105
106
107
108 <span class="grey">McCloghrie &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="./rfc1748">RFC 1748</a> IEEE 802.5 MIB using SMIv2 December 1994</span>
111
112
113 <span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. MAC Addresses</span>
114
115 All representations of MAC addresses in this MIB Module use the
116 MacAddress textual convention [<a href="#ref-5" title="&quot;Textual Conventions for version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">5</a>] for which the address is in the
117 "canonical" order defined by IEEE 802.1a, i.e., as if it were
118 transmitted least significant bit first, even though 802.5 requires
119 MAC addresses to be transmitted most significant bit first.
120
121 16-bit addresses, if needed, are represented by setting their upper 4
122 octets to all zeros, i.e., AAFF would be represented as 00000000AAFF.
123
124 <span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Relationship to <a href="./rfc1213">RFC 1213</a></span>
125
126 When this MIB module is used in conjunction with the "old" (i.e.,
127 pre-RFC 1573) interfaces group, the relationship between an 802.5
128 interface and an interface in the context of the <a href="./rfc1213">RFC 1213</a> is one-
129 to-one. That is, the value of an ifIndex object instance for an
130 802.5 interface can be directly used to identify corresponding
131 instances of the objects defined in this memo.
132
133 <span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. Relationship to <a href="./rfc1573">RFC 1573</a></span>
134
135 <a href="./rfc1573">RFC 1573</a>, the Interface MIB Evolution, requires that any MIB module
136 which is an adjunct of the Interface MIB, clarify specific areas
137 within the Interface MIB. These areas were intentionally left vague
138 in <a href="./rfc1573">RFC 1573</a> to avoid over constraining the MIB module, thereby
139 precluding management of certain media-types.
140
141 <a href="./rfc1573#section-3.3">Section&nbsp;3.3 of RFC 1573</a> enumerates several areas which a media-
142 specific MIB module must clarify. Each of these areas is addressed
143 in a following subsection. The implementor is referred to <a href="./rfc1573">RFC 1573</a>
144 in order to understand the general intent of these areas.
145
146 <span class="h4"><a class="selflink" id="section-3.3.1" href="#section-3.3.1">3.3.1</a>. Layering Model</span>
147
148 For the typical usage of this IEEE 802.5 MIB module, there will be no
149 sub-layers "above" or "below" the 802.5 interface. However, this MIB
150 module does not preclude such layering.
151
152 <span class="h4"><a class="selflink" id="section-3.3.2" href="#section-3.3.2">3.3.2</a>. Virtual Circuits</span>
153
154 802.5 does not support virtual circuits.
155
156 <span class="h4"><a class="selflink" id="section-3.3.3" href="#section-3.3.3">3.3.3</a>. ifTestTable</span>
157
158 This MIB module defines two tests for 802.5 interfaces: Insertion and
159 Loopback. Implementation of these tests is not required.
160
161
162
163
164 <span class="grey">McCloghrie &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="./rfc1748">RFC 1748</a> IEEE 802.5 MIB using SMIv2 December 1994</span>
167
168
169 <span class="h4"><a class="selflink" id="section-3.3.4" href="#section-3.3.4">3.3.4</a>. ifRcvAddressTable</span>
170
171 The ifRcvAddressTable is defined to contains all MAC addresses,
172 unicast, multicast (group) and broadcast, for which an interface will
173 receive packets. For 802.5 interfaces, its use includes functional
174 addresses. The format of the address, contained in
175 ifRcvAddressAddress, is the same as for ifPhysAddress.
176
177 For functional addresses on a particular 802.5 interface, only one
178 ifRcvAddressTable entry is required. That entry is the one for the
179 address which has the functional address bit ANDed with the bit mask
180 of all functional addresses for which the interface will accept
181 frames.
182
183 <span class="h4"><a class="selflink" id="section-3.3.5" href="#section-3.3.5">3.3.5</a>. ifPhysAddress</span>
184
185 For an 802.5 interface, ifPhysAddress contains the interface's IEEE
186 MAC address, stored as an octet string of length 6, in IEEE 802.1a
187 "canonical" order, i.e., the Group Bit is positioned as the low-order
188 bit (0x01) of the first octet.
189
190 <span class="h4"><a class="selflink" id="section-3.3.6" href="#section-3.3.6">3.3.6</a>. ifType</span>
191
192 The objects defined in this memo apply to each interface for which
193 the ifType has the value:
194
195 iso88025-tokenRing(9)
196
197 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Definitions</span>
198
199 TOKENRING-MIB DEFINITIONS ::= BEGIN
200
201 IMPORTS
202 MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY,
203 Counter32, Integer32 FROM SNMPv2-SMI
204 transmission FROM <a href="./rfc1213">RFC1213</a>-MIB
205 MacAddress,TimeStamp FROM SNMPv2-TC
206 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF;
207
208 dot5 MODULE-IDENTITY
209 LAST-UPDATED "9410231150Z"
210 ORGANIZATION "IETF Interfaces MIB Working Group"
211 CONTACT-INFO
212 " Keith McCloghrie
213
214 Postal: cisco Systems, Inc.
215 170 West Tasman Drive,
216 San Jose, CA 95134-1706
217
218
219
220 <span class="grey">McCloghrie &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="./rfc1748">RFC 1748</a> IEEE 802.5 MIB using SMIv2 December 1994</span>
223
224
225 US
226
227 Phone: +1 408 526 5260
228 EMail: [email protected]"
229 DESCRIPTION
230 "The MIB module for IEEE Token Ring entities."
231 ::= { transmission 9 }
232
233
234 -- The 802.5 Interface Table
235
236 -- This table contains state and parameter information which
237 -- is specific to 802.5 interfaces. It is mandatory that
238 -- systems having 802.5 interfaces implement this table in
239 -- addition to the ifTable (see RFCs 1213 and 1573).
240
241 dot5Table OBJECT-TYPE
242 SYNTAX SEQUENCE OF Dot5Entry
243 MAX-ACCESS not-accessible
244 STATUS current
245 DESCRIPTION
246 "This table contains Token Ring interface
247 parameters and state variables, one entry
248 per 802.5 interface."
249 ::= { dot5 1 }
250
251 dot5Entry OBJECT-TYPE
252 SYNTAX Dot5Entry
253 MAX-ACCESS not-accessible
254 STATUS current
255 DESCRIPTION
256 "A list of Token Ring status and parameter
257 values for an 802.5 interface."
258 INDEX { dot5IfIndex }
259 ::= { dot5Table 1 }
260
261 Dot5Entry ::= SEQUENCE {
262 dot5IfIndex Integer32,
263 dot5Commands INTEGER,
264 dot5RingStatus INTEGER,
265 dot5RingState INTEGER,
266 dot5RingOpenStatus INTEGER,
267 dot5RingSpeed INTEGER,
268 dot5UpStream MacAddress,
269 dot5ActMonParticipate INTEGER,
270 dot5Functional MacAddress,
271 dot5LastBeaconSent TimeStamp
272 }
273
274
275
276 <span class="grey">McCloghrie &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="./rfc1748">RFC 1748</a> IEEE 802.5 MIB using SMIv2 December 1994</span>
279
280
281 dot5IfIndex OBJECT-TYPE
282 SYNTAX Integer32
283 MAX-ACCESS read-only
284 STATUS current
285 DESCRIPTION
286 "The value of this object identifies the
287 802.5 interface for which this entry
288 contains management information. The
289 value of this object for a particular
290 interface has the same value as the
291 ifIndex object, defined in MIB-II for
292 the same interface."
293 ::= { dot5Entry 1 }
294
295 dot5Commands OBJECT-TYPE
296 SYNTAX INTEGER {
297 noop(1),
298 open(2),
299 reset(3),
300 close(4)
301 }
302 MAX-ACCESS read-write
303 STATUS current
304 DESCRIPTION
305 "When this object is set to the value of
306 open(2), the station should go into the
307 open state. The progress and success of
308 the open is given by the values of the
309 objects dot5RingState and
310 dot5RingOpenStatus.
311 When this object is set to the value
312 of reset(3), then the station should do
313 a reset. On a reset, all MIB counters
314 should retain their values, if possible.
315 Other side affects are dependent on the
316 hardware chip set.
317 When this object is set to the value
318 of close(4), the station should go into
319 the stopped state by removing itself
320 from the ring.
321 Setting this object to a value of
322 noop(1) has no effect.
323 When read, this object always has a
324 value of noop(1).
325 The open(2) and close(4) values
326 correspond to the up(1) and down(2) values
327 of MIB-II's ifAdminStatus and ifOperStatus,
328 i.e., the setting of ifAdminStatus and
329
330
331
332 <span class="grey">McCloghrie &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="./rfc1748">RFC 1748</a> IEEE 802.5 MIB using SMIv2 December 1994</span>
335
336
337 dot5Commands affects the values of both
338 dot5Commands and ifOperStatus."
339 ::= { dot5Entry 2 }
340
341 dot5RingStatus OBJECT-TYPE
342 SYNTAX INTEGER (0..262143)
343 MAX-ACCESS read-only
344 STATUS current
345 DESCRIPTION
346 "The current interface status which can
347 be used to diagnose fluctuating problems
348 that can occur on token rings, after a
349 station has successfully been added to
350 the ring.
351 Before an open is completed, this
352 object has the value for the 'no status'
353 condition. The dot5RingState and
354 dot5RingOpenStatus objects provide for
355 debugging problems when the station
356 can not even enter the ring.
357 The object's value is a sum of
358 values, one for each currently applicable
359 condition. The following values are
360 defined for various conditions:
361
362 0 = No Problems detected
363 32 = Ring Recovery
364 64 = Single Station
365 256 = Remove Received
366 512 = reserved
367 1024 = Auto-Removal Error
368 2048 = Lobe Wire Fault
369 4096 = Transmit Beacon
370 8192 = Soft Error
371 16384 = Hard Error
372 32768 = Signal Loss
373 131072 = no status, open not completed."
374 ::= { dot5Entry 3 }
375
376 dot5RingState OBJECT-TYPE
377 SYNTAX INTEGER {
378 opened(1),
379 closed(2),
380 opening(3),
381 closing(4),
382 openFailure(5),
383 ringFailure(6)
384 }
385
386
387
388 <span class="grey">McCloghrie &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="./rfc1748">RFC 1748</a> IEEE 802.5 MIB using SMIv2 December 1994</span>
391
392
393 MAX-ACCESS read-only
394 STATUS current
395 DESCRIPTION
396 "The current interface state with respect
397 to entering or leaving the ring."
398 ::= { dot5Entry 4 }
399
400 dot5RingOpenStatus OBJECT-TYPE
401 SYNTAX INTEGER {
402 noOpen(1), -- no open attempted
403 badParam(2),
404 lobeFailed(3),
405 signalLoss(4),
406 insertionTimeout(5),
407 ringFailed(6),
408 beaconing(7),
409 duplicateMAC(8),
410 requestFailed(9),
411 removeReceived(10),
412 open(11) -- last open successful
413 }
414 MAX-ACCESS read-only
415 STATUS current
416 DESCRIPTION
417 "This object indicates the success, or the
418 reason for failure, of the station's most
419 recent attempt to enter the ring."
420 ::= { dot5Entry 5 }
421
422 dot5RingSpeed OBJECT-TYPE
423 SYNTAX INTEGER {
424 unknown(1),
425 oneMegabit(2),
426 fourMegabit(3),
427 sixteenMegabit(4)
428 }
429 MAX-ACCESS read-write
430 STATUS current
431 DESCRIPTION
432 "The ring-speed at the next insertion into
433 the ring. Note that this may or may not be
434 different to the current ring-speed which is
435 given by MIB-II's ifSpeed. For interfaces
436 which do not support changing ring-speed,
437 dot5RingSpeed can only be set to its current
438 value. When dot5RingSpeed has the value
439 unknown(1), the ring's actual ring-speed is
440 to be used."
441
442
443
444 <span class="grey">McCloghrie &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="./rfc1748">RFC 1748</a> IEEE 802.5 MIB using SMIv2 December 1994</span>
447
448
449 ::= { dot5Entry 6 }
450
451 dot5UpStream OBJECT-TYPE
452 SYNTAX MacAddress
453 MAX-ACCESS read-only
454 STATUS current
455 DESCRIPTION
456 "The MAC-address of the up stream neighbor
457 station in the ring."
458 ::= { dot5Entry 7 }
459
460 dot5ActMonParticipate OBJECT-TYPE
461 SYNTAX INTEGER {
462 true(1),
463 false(2)
464 }
465 MAX-ACCESS read-write
466 STATUS current
467 DESCRIPTION
468 "If this object has a value of true(1) then
469 this interface will participate in the
470 active monitor selection process. If the
471 value is false(2) then it will not.
472 Setting this object does not take effect
473 until the next Active Monitor election, and
474 might not take effect until the next time
475 the interface is opened."
476 ::= { dot5Entry 8 }
477
478 dot5Functional OBJECT-TYPE
479 SYNTAX MacAddress
480 MAX-ACCESS read-write
481 STATUS current
482 DESCRIPTION
483 "The bit mask of all Token Ring functional
484 addresses for which this interface will
485 accept frames."
486 ::= { dot5Entry 9 }
487
488 dot5LastBeaconSent OBJECT-TYPE
489 SYNTAX TimeStamp
490 MAX-ACCESS read-only
491 STATUS current
492 DESCRIPTION
493 "The value of MIB-II's sysUpTime object at which
494 the local system last transmitted a Beacon frame
495 on this interface."
496 ::= { dot5Entry 10 }
497
498
499
500 <span class="grey">McCloghrie &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="./rfc1748">RFC 1748</a> IEEE 802.5 MIB using SMIv2 December 1994</span>
503
504
505 -- The 802.5 Statistics Table
506
507 -- This table contains statistics and error counter which are
508 -- specific to 802.5 interfaces. It is mandatory that systems
509 -- having 802.5 interfaces implement this table.
510
511 dot5StatsTable OBJECT-TYPE
512 SYNTAX SEQUENCE OF Dot5StatsEntry
513 MAX-ACCESS not-accessible
514 STATUS current
515 DESCRIPTION
516 "A table containing Token Ring statistics,
517 one entry per 802.5 interface.
518 All the statistics are defined using
519 the syntax Counter32 as 32-bit wrap around
520 counters. Thus, if an interface's
521 hardware maintains these statistics in
522 16-bit counters, then the agent must read
523 the hardware's counters frequently enough
524 to prevent loss of significance, in order
525 to maintain 32-bit counters in software."
526 ::= { dot5 2 }
527
528 dot5StatsEntry OBJECT-TYPE
529 SYNTAX Dot5StatsEntry
530 MAX-ACCESS not-accessible
531 STATUS current
532 DESCRIPTION
533 "An entry contains the 802.5 statistics
534 for a particular interface."
535 INDEX { dot5StatsIfIndex }
536 ::= { dot5StatsTable 1 }
537
538
539 Dot5StatsEntry ::= SEQUENCE {
540 dot5StatsIfIndex Integer32,
541 dot5StatsLineErrors Counter32,
542 dot5StatsBurstErrors Counter32,
543 dot5StatsACErrors Counter32,
544 dot5StatsAbortTransErrors Counter32,
545 dot5StatsInternalErrors Counter32,
546 dot5StatsLostFrameErrors Counter32,
547 dot5StatsReceiveCongestions Counter32,
548 dot5StatsFrameCopiedErrors Counter32,
549 dot5StatsTokenErrors Counter32,
550 dot5StatsSoftErrors Counter32,
551 dot5StatsHardErrors Counter32,
552 dot5StatsSignalLoss Counter32,
553
554
555
556 <span class="grey">McCloghrie &amp; Decker [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc1748">RFC 1748</a> IEEE 802.5 MIB using SMIv2 December 1994</span>
559
560
561 dot5StatsTransmitBeacons Counter32,
562 dot5StatsRecoverys Counter32,
563 dot5StatsLobeWires Counter32,
564 dot5StatsRemoves Counter32,
565 dot5StatsSingles Counter32,
566 dot5StatsFreqErrors Counter32
567 }
568
569
570 dot5StatsIfIndex OBJECT-TYPE
571 SYNTAX Integer32
572 MAX-ACCESS read-only
573 STATUS current
574 DESCRIPTION
575 "The value of this object identifies the
576 802.5 interface for which this entry
577 contains management information. The
578 value of this object for a particular
579 interface has the same value as MIB-II's
580 ifIndex object for the same interface."
581 ::= { dot5StatsEntry 1 }
582
583 dot5StatsLineErrors OBJECT-TYPE
584 SYNTAX Counter32
585 MAX-ACCESS read-only
586 STATUS current
587 DESCRIPTION
588 "This counter is incremented when a frame
589 or token is copied or repeated by a
590 station, the E bit is zero in the frame
591 or token and one of the following
592 conditions exists: 1) there is a
593 non-data bit (J or K bit) between the SD
594 and the ED of the frame or token, or
595 2) there is an FCS error in the frame."
596 ::= { dot5StatsEntry 2 }
597
598 dot5StatsBurstErrors OBJECT-TYPE
599 SYNTAX Counter32
600 MAX-ACCESS read-only
601 STATUS current
602 DESCRIPTION
603 "This counter is incremented when a station
604 detects the absence of transitions for five
605 half-bit timers (burst-five error)."
606 ::= { dot5StatsEntry 3 }
607
608
609
610
611
612 <span class="grey">McCloghrie &amp; Decker [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc1748">RFC 1748</a> IEEE 802.5 MIB using SMIv2 December 1994</span>
615
616
617 dot5StatsACErrors OBJECT-TYPE
618 SYNTAX Counter32
619 MAX-ACCESS read-only
620 STATUS current
621 DESCRIPTION
622 "This counter is incremented when a station
623 receives an AMP or SMP frame in which A is
624 equal to C is equal to 0, and then receives
625 another SMP frame with A is equal to C is
626 equal to 0 without first receiving an AMP
627 frame. It denotes a station that cannot set
628 the AC bits properly."
629 ::= { dot5StatsEntry 4 }
630
631 dot5StatsAbortTransErrors OBJECT-TYPE
632 SYNTAX Counter32
633 MAX-ACCESS read-only
634 STATUS current
635 DESCRIPTION
636 "This counter is incremented when a station
637 transmits an abort delimiter while
638 transmitting."
639 ::= { dot5StatsEntry 5 }
640
641 dot5StatsInternalErrors OBJECT-TYPE
642 SYNTAX Counter32
643 MAX-ACCESS read-only
644 STATUS current
645 DESCRIPTION
646 "This counter is incremented when a station
647 recognizes an internal error."
648 ::= { dot5StatsEntry 6 }
649
650 dot5StatsLostFrameErrors OBJECT-TYPE
651 SYNTAX Counter32
652 MAX-ACCESS read-only
653 STATUS current
654 DESCRIPTION
655 "This counter is incremented when a station
656 is transmitting and its TRR timer expires.
657 This condition denotes a condition where a
658 transmitting station in strip mode does not
659 receive the trailer of the frame before the
660 TRR timer goes off."
661 ::= { dot5StatsEntry 7 }
662
663
664
665
666
667
668 <span class="grey">McCloghrie &amp; Decker [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc1748">RFC 1748</a> IEEE 802.5 MIB using SMIv2 December 1994</span>
671
672
673 dot5StatsReceiveCongestions OBJECT-TYPE
674 SYNTAX Counter32
675 MAX-ACCESS read-only
676 STATUS current
677 DESCRIPTION
678 "This counter is incremented when a station
679 recognizes a frame addressed to its
680 specific address, but has no available
681 buffer space indicating that the station
682 is congested."
683 ::= { dot5StatsEntry 8 }
684
685 dot5StatsFrameCopiedErrors OBJECT-TYPE
686 SYNTAX Counter32
687 MAX-ACCESS read-only
688 STATUS current
689 DESCRIPTION
690 "This counter is incremented when a station
691 recognizes a frame addressed to its
692 specific address and detects that the FS
693 field A bits are set to 1 indicating a
694 possible line hit or duplicate address."
695 ::= { dot5StatsEntry 9 }
696
697 dot5StatsTokenErrors OBJECT-TYPE
698 SYNTAX Counter32
699 MAX-ACCESS read-only
700 STATUS current
701 DESCRIPTION
702 "This counter is incremented when a station
703 acting as the active monitor recognizes an
704 error condition that needs a token
705 transmitted."
706 ::= { dot5StatsEntry 10 }
707
708 dot5StatsSoftErrors OBJECT-TYPE
709 SYNTAX Counter32
710 MAX-ACCESS read-only
711 STATUS current
712 DESCRIPTION
713 "The number of Soft Errors the interface
714 has detected. It directly corresponds to
715 the number of Report Error MAC frames
716 that this interface has transmitted.
717 Soft Errors are those which are
718 recoverable by the MAC layer protocols."
719 ::= { dot5StatsEntry 11 }
720
721
722
723
724 <span class="grey">McCloghrie &amp; Decker [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc1748">RFC 1748</a> IEEE 802.5 MIB using SMIv2 December 1994</span>
727
728
729 dot5StatsHardErrors OBJECT-TYPE
730 SYNTAX Counter32
731 MAX-ACCESS read-only
732 STATUS current
733 DESCRIPTION
734 "The number of times this interface has
735 detected an immediately recoverable
736 fatal error. It denotes the number of
737 times this interface is either
738 transmitting or receiving beacon MAC
739 frames."
740 ::= { dot5StatsEntry 12 }
741
742 dot5StatsSignalLoss OBJECT-TYPE
743 SYNTAX Counter32
744 MAX-ACCESS read-only
745 STATUS current
746 DESCRIPTION
747 "The number of times this interface has
748 detected the loss of signal condition from
749 the ring."
750 ::= { dot5StatsEntry 13 }
751
752 dot5StatsTransmitBeacons OBJECT-TYPE
753 SYNTAX Counter32
754 MAX-ACCESS read-only
755 STATUS current
756 DESCRIPTION
757 "The number of times this interface has
758 transmitted a beacon frame."
759 ::= { dot5StatsEntry 14 }
760
761 dot5StatsRecoverys OBJECT-TYPE
762 SYNTAX Counter32
763 MAX-ACCESS read-only
764 STATUS current
765 DESCRIPTION
766 "The number of Claim Token MAC frames
767 received or transmitted after the interface
768 has received a Ring Purge MAC frame. This
769 counter signifies the number of times the
770 ring has been purged and is being recovered
771 back into a normal operating state."
772 ::= { dot5StatsEntry 15 }
773
774 dot5StatsLobeWires OBJECT-TYPE
775 SYNTAX Counter32
776 MAX-ACCESS read-only
777
778
779
780 <span class="grey">McCloghrie &amp; Decker [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc1748">RFC 1748</a> IEEE 802.5 MIB using SMIv2 December 1994</span>
783
784
785 STATUS current
786 DESCRIPTION
787 "The number of times the interface has
788 detected an open or short circuit in the
789 lobe data path. The adapter will be closed
790 and dot5RingState will signify this
791 condition."
792 ::= { dot5StatsEntry 16 }
793
794 dot5StatsRemoves OBJECT-TYPE
795 SYNTAX Counter32
796 MAX-ACCESS read-only
797 STATUS current
798 DESCRIPTION
799 "The number of times the interface has
800 received a Remove Ring Station MAC frame
801 request. When this frame is received
802 the interface will enter the close state
803 and dot5RingState will signify this
804 condition."
805 ::= { dot5StatsEntry 17 }
806
807 dot5StatsSingles OBJECT-TYPE
808 SYNTAX Counter32
809 MAX-ACCESS read-only
810 STATUS current
811 DESCRIPTION
812 "The number of times the interface has
813 sensed that it is the only station on the
814 ring. This will happen if the interface
815 is the first one up on a ring, or if
816 there is a hardware problem."
817 ::= { dot5StatsEntry 18 }
818
819 dot5StatsFreqErrors OBJECT-TYPE
820 SYNTAX Counter32
821 MAX-ACCESS read-only
822 STATUS current
823 DESCRIPTION
824 "The number of times the interface has
825 detected that the frequency of the
826 incoming signal differs from the expected
827 frequency by more than that specified by
828 the IEEE 802.5 standard."
829 ::= { dot5StatsEntry 19 }
830
831
832
833
834
835
836 <span class="grey">McCloghrie &amp; Decker [Page 15]</span></pre>
837 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
838 <span class="grey"><a href="./rfc1748">RFC 1748</a> IEEE 802.5 MIB using SMIv2 December 1994</span>
839
840
841 -- The Timer Table
842
843 -- This group contains the values of timers for 802.5
844 -- interfaces. This table is obsolete, but its definition
845 -- is retained here for backwards compatibility.
846
847 dot5TimerTable OBJECT-TYPE
848 SYNTAX SEQUENCE OF Dot5TimerEntry
849 MAX-ACCESS not-accessible
850 STATUS obsolete
851 DESCRIPTION
852 "This table contains Token Ring interface
853 timer values, one entry per 802.5
854 interface."
855 ::= { dot5 5 }
856
857 dot5TimerEntry OBJECT-TYPE
858 SYNTAX Dot5TimerEntry
859 MAX-ACCESS not-accessible
860 STATUS obsolete
861 DESCRIPTION
862 "A list of Token Ring timer values for an
863 802.5 interface."
864 INDEX { dot5TimerIfIndex }
865 ::= { dot5TimerTable 1 }
866
867 Dot5TimerEntry ::= SEQUENCE {
868 dot5TimerIfIndex Integer32,
869 dot5TimerReturnRepeat Integer32,
870 dot5TimerHolding Integer32,
871 dot5TimerQueuePDU Integer32,
872 dot5TimerValidTransmit Integer32,
873 dot5TimerNoToken Integer32,
874 dot5TimerActiveMon Integer32,
875 dot5TimerStandbyMon Integer32,
876 dot5TimerErrorReport Integer32,
877 dot5TimerBeaconTransmit Integer32,
878 dot5TimerBeaconReceive Integer32
879 }
880
881 dot5TimerIfIndex OBJECT-TYPE
882 SYNTAX Integer32
883 MAX-ACCESS read-only
884 STATUS obsolete
885 DESCRIPTION
886 "The value of this object identifies the
887 802.5 interface for which this entry
888 contains timer values. The value of
889
890
891
892 <span class="grey">McCloghrie &amp; Decker [Page 16]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
894 <span class="grey"><a href="./rfc1748">RFC 1748</a> IEEE 802.5 MIB using SMIv2 December 1994</span>
895
896
897 this object for a particular interface
898 has the same value as MIB-II's ifIndex
899 object for the same interface."
900 ::= { dot5TimerEntry 1 }
901
902 dot5TimerReturnRepeat OBJECT-TYPE
903 SYNTAX Integer32
904 MAX-ACCESS read-only
905 STATUS obsolete
906 DESCRIPTION
907 "The time-out value used to ensure the
908 interface will return to Repeat State, in
909 units of 100 micro-seconds. The value
910 should be greater than the maximum ring
911 latency."
912 ::= { dot5TimerEntry 2 }
913
914 dot5TimerHolding OBJECT-TYPE
915 SYNTAX Integer32
916 MAX-ACCESS read-only
917 STATUS obsolete
918 DESCRIPTION
919 "Maximum period of time a station is
920 permitted to transmit frames after capturing
921 a token, in units of 100 micro-seconds."
922 ::= { dot5TimerEntry 3 }
923
924 dot5TimerQueuePDU OBJECT-TYPE
925 SYNTAX Integer32
926 MAX-ACCESS read-only
927 STATUS obsolete
928 DESCRIPTION
929 "The time-out value for enqueuing of an SMP
930 PDU after reception of an AMP or SMP
931 frame in which the A and C bits were
932 equal to 0, in units of 100
933 micro-seconds."
934 ::= { dot5TimerEntry 4 }
935
936 dot5TimerValidTransmit OBJECT-TYPE
937 SYNTAX Integer32
938 MAX-ACCESS read-only
939 STATUS obsolete
940 DESCRIPTION
941 "The time-out value used by the active
942 monitor to detect the absence of valid
943 transmissions, in units of 100
944 micro-seconds."
945
946
947
948 <span class="grey">McCloghrie &amp; Decker [Page 17]</span></pre>
949 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
950 <span class="grey"><a href="./rfc1748">RFC 1748</a> IEEE 802.5 MIB using SMIv2 December 1994</span>
951
952
953 ::= { dot5TimerEntry 5 }
954
955 dot5TimerNoToken OBJECT-TYPE
956 SYNTAX Integer32
957 MAX-ACCESS read-only
958 STATUS obsolete
959 DESCRIPTION
960 "The time-out value used to recover from
961 various-related error situations.
962 If N is the maximum number of stations on
963 the ring, the value of this timer is
964 normally:
965 dot5TimerReturnRepeat + N*dot5TimerHolding."
966 ::= { dot5TimerEntry 6 }
967
968 dot5TimerActiveMon OBJECT-TYPE
969 SYNTAX Integer32
970 MAX-ACCESS read-only
971 STATUS obsolete
972 DESCRIPTION
973 "The time-out value used by the active
974 monitor to stimulate the enqueuing of an
975 AMP PDU for transmission, in units of
976 100 micro-seconds."
977 ::= { dot5TimerEntry 7 }
978
979 dot5TimerStandbyMon OBJECT-TYPE
980 SYNTAX Integer32
981 MAX-ACCESS read-only
982 STATUS obsolete
983 DESCRIPTION
984 "The time-out value used by the stand-by
985 monitors to ensure that there is an active
986 monitor on the ring and to detect a
987 continuous stream of tokens, in units of
988 100 micro-seconds."
989 ::= { dot5TimerEntry 8 }
990
991 dot5TimerErrorReport OBJECT-TYPE
992 SYNTAX Integer32
993 MAX-ACCESS read-only
994 STATUS obsolete
995 DESCRIPTION
996 "The time-out value which determines how
997 often a station shall send a Report Error
998 MAC frame to report its error counters,
999 in units of 100 micro-seconds."
1000 ::= { dot5TimerEntry 9 }
1001
1002
1003
1004 <span class="grey">McCloghrie &amp; Decker [Page 18]</span></pre>
1005 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
1006 <span class="grey"><a href="./rfc1748">RFC 1748</a> IEEE 802.5 MIB using SMIv2 December 1994</span>
1007
1008
1009 dot5TimerBeaconTransmit OBJECT-TYPE
1010 SYNTAX Integer32
1011 MAX-ACCESS read-only
1012 STATUS obsolete
1013 DESCRIPTION
1014 "The time-out value which determines how
1015 long a station shall remain in the state
1016 of transmitting Beacon frames before
1017 entering the Bypass state, in units of
1018 100 micro-seconds."
1019 ::= { dot5TimerEntry 10 }
1020
1021 dot5TimerBeaconReceive OBJECT-TYPE
1022 SYNTAX Integer32
1023 MAX-ACCESS read-only
1024 STATUS obsolete
1025 DESCRIPTION
1026 "The time-out value which determines how
1027 long a station shall receive Beacon
1028 frames from its downstream neighbor
1029 before entering the Bypass state, in
1030 units of 100 micro-seconds."
1031 ::= { dot5TimerEntry 11 }
1032
1033
1034 -- 802.5 Interface Tests
1035
1036 dot5Tests OBJECT IDENTIFIER ::= { dot5 3 }
1037
1038 -- <a href="./rfc1573">RFC 1573</a> defines the ifTestTable, through which a
1039 -- network manager can instruct an agent to test an interface
1040 -- for various faults. A test to be performed is identified
1041 -- as an OBJECT IDENTIFIER.
1042
1043 -- The Insert Function test
1044
1045 dot5TestInsertFunc OBJECT-IDENTITY
1046 STATUS current
1047 DESCRIPTION
1048 "Invoking this test causes the station to test the insert
1049 ring logic of the hardware if the station's lobe media
1050 cable is connected to a wiring concentrator. Note that
1051 this command inserts the station into the network, and
1052 thus, could cause problems if the station is connected
1053 to a operational network."
1054 ::= { dot5Tests 1 }
1055
1056
1057
1058
1059
1060 <span class="grey">McCloghrie &amp; Decker [Page 19]</span></pre>
1061 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
1062 <span class="grey"><a href="./rfc1748">RFC 1748</a> IEEE 802.5 MIB using SMIv2 December 1994</span>
1063
1064
1065 -- The Full-Duplex Loop Back test
1066
1067 dot5TestFullDuplexLoopBack OBJECT-IDENTITY
1068 STATUS current
1069 DESCRIPTION
1070 "Invoking this test on a 802.5 interface causes the
1071 interface to check the path from memory through the
1072 chip set's internal logic and back to memory, thus
1073 checking the proper functioning of the system's
1074 interface to the chip set."
1075 ::= { dot5Tests 2 }
1076
1077
1078 -- 802.5 Hardware Chip Sets
1079
1080 -- <a href="./rfc1229">RFC 1229</a> specified an object, ifExtnsChipSet, with the
1081 -- syntax of OBJECT IDENTIFIER, to identify the hardware
1082 -- chip set in use by an interface. <a href="./rfc1573">RFC 1573</a> obsoletes
1083 -- the use of ifExtnsChipSet. However, the following
1084 -- definitions are retained for backwards compatibility.
1085
1086 dot5ChipSets OBJECT IDENTIFIER ::= { dot5 4 }
1087
1088 dot5ChipSetIBM16 OBJECT-IDENTITY
1089 STATUS current
1090 DESCRIPTION
1091 "IBM's 16/4 Mbs chip set."
1092 ::= { dot5ChipSets 1 }
1093
1094 dot5ChipSetTItms380 OBJECT-IDENTITY
1095 STATUS current
1096 DESCRIPTION
1097 "Texas Instruments' TMS 380 4Mbs chip-set"
1098 ::= { dot5ChipSets 2 }
1099
1100 dot5ChipSetTItms380c16 OBJECT-IDENTITY
1101 STATUS current
1102 DESCRIPTION
1103 "Texas Instruments' TMS 380C16 16/4 Mbs chip-set"
1104 ::= { dot5ChipSets 3 }
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116 <span class="grey">McCloghrie &amp; Decker [Page 20]</span></pre>
1117 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
1118 <span class="grey"><a href="./rfc1748">RFC 1748</a> IEEE 802.5 MIB using SMIv2 December 1994</span>
1119
1120
1121 -- conformance information
1122
1123 dot5Conformance OBJECT IDENTIFIER ::= { dot5 6 }
1124
1125 dot5Groups OBJECT IDENTIFIER ::= { dot5Conformance 1 }
1126 dot5Compliances OBJECT IDENTIFIER ::= { dot5Conformance 2 }
1127
1128
1129 -- compliance statements
1130
1131 dot5Compliance MODULE-COMPLIANCE
1132 STATUS current
1133 DESCRIPTION
1134 "The compliance statement for SNMPv2 entities
1135 which implement the IEEE 802.5 MIB."
1136
1137 MODULE -- this module
1138 MANDATORY-GROUPS { dot5StateGroup, dot5StatsGroup }
1139
1140 OBJECT dot5ActMonParticipate
1141 MIN-ACCESS read-only
1142 DESCRIPTION
1143 "Write access is not required."
1144
1145 OBJECT dot5Functional
1146 MIN-ACCESS read-only
1147 DESCRIPTION
1148 "Write access is not required."
1149
1150 ::= { dot5Compliances 1 }
1151
1152
1153 -- units of conformance
1154
1155 dot5StateGroup OBJECT-GROUP
1156 OBJECTS { dot5Commands, dot5RingStatus, dot5RingState,
1157 dot5RingOpenStatus, dot5RingSpeed, dot5UpStream,
1158 dot5ActMonParticipate, dot5Functional,
1159 dot5LastBeaconSent
1160 }
1161 STATUS current
1162 DESCRIPTION
1163 "A collection of objects providing state information
1164 and parameters for IEEE 802.5 interfaces."
1165 ::= { dot5Groups 1 }
1166
1167 dot5StatsGroup OBJECT-GROUP
1168 OBJECTS { dot5StatsLineErrors, dot5StatsBurstErrors,
1169
1170
1171
1172 <span class="grey">McCloghrie &amp; Decker [Page 21]</span></pre>
1173 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
1174 <span class="grey"><a href="./rfc1748">RFC 1748</a> IEEE 802.5 MIB using SMIv2 December 1994</span>
1175
1176
1177 dot5StatsACErrors, dot5StatsAbortTransErrors,
1178 dot5StatsInternalErrors, dot5StatsLostFrameErrors,
1179 dot5StatsReceiveCongestions,
1180 dot5StatsFrameCopiedErrors, dot5StatsTokenErrors,
1181 dot5StatsSoftErrors, dot5StatsHardErrors,
1182 dot5StatsSignalLoss, dot5StatsTransmitBeacons,
1183 dot5StatsRecoverys, dot5StatsLobeWires,
1184 dot5StatsRemoves, dot5StatsSingles,
1185 dot5StatsFreqErrors
1186 }
1187 STATUS current
1188 DESCRIPTION
1189 "A collection of objects providing statistics for
1190 IEEE 802.5 interfaces."
1191 ::= { dot5Groups 2 }
1192
1193 END
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228 <span class="grey">McCloghrie &amp; Decker [Page 22]</span></pre>
1229 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
1230 <span class="grey"><a href="./rfc1748">RFC 1748</a> IEEE 802.5 MIB using SMIv2 December 1994</span>
1231
1232
1233 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Acknowledgements</span>
1234
1235 The changes from <a href="./rfc1231">RFC 1231</a> are the result of discussions on the IETF's
1236 snmp mailing-list and in the Interfaces MIB Working Group.
1237
1238 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. References</span>
1239
1240 [<a id="ref-1">1</a>] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure
1241 of Management Information for version 2 of the Simple Network
1242 Management Protocol (SNMPv2)", <a href="./rfc1442">RFC 1442</a>, SNMP Research,Inc.,
1243 Hughes LAN Systems, Dover Beach Consulting, Inc., Carnegie Mellon
1244 University, April 1993.
1245
1246 [<a id="ref-2">2</a>] McCloghrie, K., and M. Rose, Editors, "Management Information
1247 Base for Network Management of TCP/IP-based internets: MIB-II",
1248 STD 17, <a href="./rfc1213">RFC 1213</a>, Hughes LAN Systems, Performance Systems
1249 International, March 1991.
1250
1251 [<a id="ref-3">3</a>] Galvin, J., and K. McCloghrie, "Administrative Model for version
1252 2 of the Simple Network Management Protocol (SNMPv2)", <a href="./rfc1445">RFC 1445</a>,
1253 Trusted Information Systems, Hughes LAN Systems, April 1993.
1254
1255 [<a id="ref-4">4</a>] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol
1256 Operations for version 2 of the Simple Network Management
1257 Protocol (SNMPv2)", <a href="./rfc1448">RFC 1448</a>, SNMP Research,Inc., Hughes LAN
1258 Systems, Dover Beach Consulting, Inc., Carnegie Mellon
1259 University, April 1993.
1260
1261 [<a id="ref-5">5</a>] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual
1262 Conventions for version 2 of the Simple Network Management
1263 Protocol (SNMPv2)", <a href="./rfc1443">RFC 1443</a>, SNMP Research,Inc., Hughes LAN
1264 Systems, Dover Beach Consulting, Inc., Carnegie Mellon
1265 University, April 1993.
1266
1267 [<a id="ref-6">6</a>] McCloghrie, K., and F. Kastenholz, "Evolution of the Interfaces
1268 Group of MIB-II", <a href="./rfc1573">RFC 1573</a>, Hughes LAN Systems, FTP Software, Jan
1269 1994
1270
1271 [<a id="ref-7">7</a>] Institute of Electrical and Electronic Engineers, "Token Ring
1272 Access Method and Physical Layer Specifications", IEEE Standard
1273 802.5-1989, 1989.
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284 <span class="grey">McCloghrie &amp; Decker [Page 23]</span></pre>
1285 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
1286 <span class="grey"><a href="./rfc1748">RFC 1748</a> IEEE 802.5 MIB using SMIv2 December 1994</span>
1287
1288
1289 APPENDIX A - Changes from <a href="./rfc1231">RFC 1231</a>
1290
1291 This memo has the following differences from <a href="./rfc1231">RFC 1231</a>:
1292
1293 (1) This memo is formatted using the SNMPv2 SMI.
1294
1295 (2) The relationship of the "open" and "close" states of
1296 dot5Commands to the value of ifAdminStatus has been
1297 clarified. In particular, the setting of one affects the
1298 value of the other.
1299
1300 (3) The relationship dot5RingSpeed and ifSpeed has been
1301 clarified. In particular, ifSpeed indicates the current
1302 ring-speed; dot5RingSpeed indicates the ring-speed at the
1303 next insertion into the ring. If the interface doesn't
1304 support changing ring-speed, then dot5RingSpeed can only be
1305 set to its current value. When dot5RingSpeed has the value
1306 'unknown(1)', the ring-speed is to be set to the ring's
1307 actual ring-speed.
1308
1309 (4) Write-access to dot5ActMonParticipate is not required, and a
1310 change to the value of dot5ActMonParticipate does not take
1311 effect until the next Active Monitor election.
1312
1313 (5) Write-access to dot5Functional is not required.
1314
1315 (6) A new object, dot5LastBeaconSent has been defined to contain
1316 the timestamp of the last beacon frame sent.
1317
1318 (7) The dot5TimerTable has been designated as obsolete.
1319
1320 (8) Text has been added describing the applicability of <a href="./rfc1573">RFC 1573</a>
1321 [<a href="#ref-6" title="&quot;Evolution of the Interfaces Group of MIB-II&quot;">6</a>] to 802.5 interfaces.
1322
1323 (9) Other minor editorial changes.
1324
1325 Security Considerations
1326
1327 Security issues are not discussed in this memo.
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340 <span class="grey">McCloghrie &amp; Decker [Page 24]</span></pre>
1341 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span>
1342 <span class="grey"><a href="./rfc1748">RFC 1748</a> IEEE 802.5 MIB using SMIv2 December 1994</span>
1343
1344
1345 Authors' Addresses
1346
1347 Keith McCloghrie
1348 cisco Systems, Inc.
1349 170 West Tasman Drive,
1350 San Jose, CA 95134-1706
1351
1352 Phone: (408) 526-5260
1353 EMail: [email protected]
1354
1355
1356 Eric B. Decker
1357 cisco Systems, Inc.
1358 1525 O'Brien Dr.
1359 Menlo Park, CA 94025
1360
1361 Phone: (415) 688-8241
1362 EMail: [email protected]
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396 McCloghrie &amp; Decker [Page 25]
1397 </pre>