smilint output for ./RFC1231-MIB
| Message Severities |
|---|
| Severity | Count |
|---|
| error | 22 |
| Message Types |
|---|
| Type | Count |
|---|
| basetype-unknown (error) | 18 |
| index-element-no-range (error) | 3 |
| type-unknown (error) | 1 |
Messages:
RFC1231-MIB
1: -- extracted from rfc1231.txt
2: -- at Mon Nov 15 17:12:01 1999
3:
4: RFC1231-MIB DEFINITIONS ::= BEGIN
5:
6: -- IEEE 802.5 Token Ring MIB
7:
8: IMPORTS
9: experimental
10: FROM RFC1155-SMI
11: OBJECT-TYPE
12: FROM RFC-1212;
13:
14: -- This MIB Module uses the extended OBJECT-TYPE macro as
15: -- defined in [9].
16:
17:
18:
19: dot5 OBJECT IDENTIFIER ::= { experimental 4 }
20:
21: -- All representations of MAC addresses in this MIB Module
22: -- use, as a textual convention (i.e. this convention does
23: -- not affect their encoding), the data type:
24:
25: MacAddress ::= OCTET STRING (SIZE (6)) -- a 6 octet
26: -- address in the
27: -- "canonical" order
28: -- defined by IEEE 802.1a, i.e., as if it were transmitted
29: -- least significant bit first, even though 802.5 (in
30: -- contrast to other 802.x protocols) requires MAC addresses
31: -- to be transmitted most significant bit first.
32: --
33: -- 16-bit addresses, if needed, are represented by setting
34: -- their upper 4 octets to all 0's, i.e., AAFF would be
35: -- represented as 00000000AAFF.
36:
37:
38:
39: -- The Interface Table
40:
41: -- This table contains state and parameter information which
42: -- is specific to 802.5 interfaces. It is mandatory that
43: -- systems having 802.5 interfaces implement this table in
44: -- addition to the generic interfaces table [4,6] and its
45: -- generic extensions [11].
46: dot5Table OBJECT-TYPE
47: SYNTAX SEQUENCE OF Dot5Entry
48: ACCESS not-accessible
49: STATUS mandatory
50: DESCRIPTION
51: "This table contains Token Ring interface
52: parameters and state variables, one entry
53: per 802.5 interface."
54: ::= { dot5 1 }
55:
56: dot5Entry OBJECT-TYPE
57: SYNTAX Dot5Entry
58: ACCESS not-accessible
59: STATUS mandatory
60: DESCRIPTION
61: "A list of Token Ring status and parameter
62: values for an 802.5 interface."
63: INDEX { dot5IfIndex }
64: ::= { dot5Table 1 }
65:
66: Dot5Entry
67: ::= SEQUENCE {
68: dot5IfIndex
69: INTEGER,
70: dot5Commands
71: INTEGER,
72: dot5RingStatus
73: INTEGER,
74: dot5RingState
75: INTEGER,
76: dot5RingOpenStatus
77: INTEGER,
78: dot5RingSpeed
79: INTEGER,
80: dot5UpStream
81: MacAddress,
82: dot5ActMonParticipate
83: INTEGER,
84: dot5Functional
85: MacAddress
86: }
87:
88: dot5IfIndex OBJECT-TYPE
88: error -
index element `dot5IfIndex' of row `dot5Entry' must have a range restriction
89: SYNTAX INTEGER
90: ACCESS read-only
91: STATUS mandatory
92: DESCRIPTION
93: "The value of this object identifies the
94: 802.5 interface for which this entry
95: contains management information. The
96: value of this object for a particular
97: interface has the same value as the
98: ifIndex object, defined in [4,6],
99: for the same interface."
100: ::= { dot5Entry 1 }
101:
102: dot5Commands OBJECT-TYPE
103: SYNTAX INTEGER {
104: no-op(1),
105: open(2),
106: reset(3),
107: close(4)
108: }
109: ACCESS read-write
110: STATUS mandatory
111: DESCRIPTION
112: "When this object is set to the value of
113: open(2), the station should go into the
114: open state. The progress and success of
115: the open is given by the values of the
116: objects dot5RingState and
117: dot5RingOpenStatus.
118: When this object is set to the value
119: of reset(3), then the station should do
120: a reset. On a reset, all MIB counters
121: should retain their values, if possible.
122: Other side affects are dependent on the
123: hardware chip set.
124: When this object is set to the value
125: of close(4), the station should go into
126: the stopped state by removing itself
127: from the ring.
128: Setting this object to a value of
129: no-op(1) has no effect.
130: When read, this object always has a
131: value of no-op(1)."
132: ::= { dot5Entry 2 }
133:
134: dot5RingStatus OBJECT-TYPE
135: SYNTAX INTEGER
136: ACCESS read-only
137: STATUS mandatory
138: DESCRIPTION
139: "The current interface status which can
140: be used to diagnose fluctuating problems
141: that can occur on token rings, after a
142: station has successfully been added to
143: the ring.
144: Before an open is completed, this
145: object has the value for the 'no status'
146: condition. The dot5RingState and
147: dot5RingOpenStatus objects provide for
148: debugging problems when the station
149: can not even enter the ring.
150: The object's value is a sum of
151: values, one for each currently applicable
152: condition. The following values are
153: defined for various conditions:
154:
155: 0 = No Problems detected
156: 32 = Ring Recovery
157: 64 = Single Station
158: 256 = Remove Received
159: 512 = reserved
160: 1024 = Auto-Removal Error
161: 2048 = Lobe Wire Fault
162: 4096 = Transmit Beacon
163: 8192 = Soft Error
164: 16384 = Hard Error
165: 32768 = Signal Loss
166: 131072 = no status, open not completed."
167: ::= { dot5Entry 3 }
168:
169: dot5RingState OBJECT-TYPE
170: SYNTAX INTEGER {
171: opened(1),
172: closed(2),
173: opening(3),
174: closing(4),
175: openFailure(5),
176: ringFailure(6)
177: }
178: ACCESS read-only
179: STATUS mandatory
180: DESCRIPTION
181: "The current interface state with respect
182: to entering or leaving the ring."
183: ::= { dot5Entry 4 }
184:
185: dot5RingOpenStatus OBJECT-TYPE
186: SYNTAX INTEGER {
187: noOpen(1), -- no open attempted
188: badParam(2),
189: lobeFailed(3),
190: signalLoss(4),
191: insertionTimeout(5),
192: ringFailed(6),
193: beaconing(7),
194: duplicateMAC(8),
195: requestFailed(9),
196: removeReceived(10),
197: open(11) -- last open successful
198: }
199: ACCESS read-only
200: STATUS mandatory
201: DESCRIPTION
202: "This object indicates the success, or the
203: reason for failure, of the station's most
204: recent attempt to enter the ring."
205: ::= { dot5Entry 5 }
206:
207: dot5RingSpeed OBJECT-TYPE
208: SYNTAX INTEGER {
209: unknown(1),
210: oneMegabit(2),
211: fourMegabit(3),
212: sixteenMegabit(4)
213: }
214: ACCESS read-write
215: STATUS mandatory
216: DESCRIPTION
217: "The ring's bandwidth."
218: ::= { dot5Entry 6 }
219:
220: dot5UpStream OBJECT-TYPE
221: SYNTAX MacAddress
222: ACCESS read-only
223: STATUS mandatory
224: DESCRIPTION
225: "The MAC-address of the up stream neighbor
226: station in the ring."
227: ::= { dot5Entry 7 }
228:
229: dot5ActMonParticipate OBJECT-TYPE
230: SYNTAX INTEGER {
231: true(1),
232: false(2)
233: }
234: ACCESS read-write
235: STATUS mandatory
236: DESCRIPTION
237: "If this object has a value of true(1) then
238: this interface will participate in the
239: active monitor selection process. If the
240: value is false(2) then it will not.
241: Setting this object might not have an
242: effect until the next time the interface
243: is opened."
244: ::= { dot5Entry 8 }
245:
246: dot5Functional OBJECT-TYPE
247: SYNTAX MacAddress
248: ACCESS read-write
249: STATUS mandatory
250: DESCRIPTION
251: "The bit mask of all Token Ring functional
252: addresses for which this interface will
253: accept frames."
254: ::= { dot5Entry 9 }
255:
256:
257:
258: -- The Statistics Table
259:
260: -- This table contains statistics and error counter which are
261: -- specific to 802.5 interfaces. It is mandatory that systems
262: -- having 802.5 interfaces implement this table.
263:
264: dot5StatsTable OBJECT-TYPE
265: SYNTAX SEQUENCE OF Dot5StatsEntry
266: ACCESS not-accessible
267: STATUS mandatory
268: DESCRIPTION
269: "A table containing Token Ring statistics,
270: one entry per 802.5 interface.
271: All the statistics are defined using
272: the syntax Counter as 32-bit wrap around
273: counters. Thus, if an interface's
274: hardware maintains these statistics in
275: 16-bit counters, then the agent must read
276: the hardware's counters frequently enough
277: to prevent loss of significance, in order
278: to maintain 32-bit counters in software."
279: ::= { dot5 2 }
280:
281: dot5StatsEntry OBJECT-TYPE
282: SYNTAX Dot5StatsEntry
283: ACCESS not-accessible
284: STATUS mandatory
285: DESCRIPTION
286: "An entry contains the 802.5 statistics
287: for a particular interface."
288: INDEX { dot5StatsIfIndex }
289: ::= { dot5StatsTable 1 }
290:
291: Dot5StatsEntry
292: ::= SEQUENCE {
293: dot5StatsIfIndex
294: INTEGER,
295: dot5StatsLineErrors
296: Counter,
296: error -
unknown type `Counter'
297: dot5StatsBurstErrors
298: Counter,
299: dot5StatsACErrors
300: Counter,
301: dot5StatsAbortTransErrors
302: Counter,
303: dot5StatsInternalErrors
304: Counter,
305: dot5StatsLostFrameErrors
306: Counter,
307: dot5StatsReceiveCongestions
308: Counter,
309: dot5StatsFrameCopiedErrors
310: Counter,
311: dot5StatsTokenErrors
312: Counter,
313: dot5StatsSoftErrors
314: Counter,
315: dot5StatsHardErrors
316: Counter,
317: dot5StatsSignalLoss
318: Counter,
319: dot5StatsTransmitBeacons
320: Counter,
321: dot5StatsRecoverys
322: Counter,
323: dot5StatsLobeWires
324: Counter,
325: dot5StatsRemoves
326: Counter,
327: dot5StatsSingles
328: Counter,
329: dot5StatsFreqErrors
330: Counter
331: }
332:
333: dot5StatsIfIndex OBJECT-TYPE
333: error -
index element `dot5StatsIfIndex' of row `dot5StatsEntry' must have a range restriction
334: SYNTAX INTEGER
335: ACCESS read-only
336: STATUS mandatory
337: DESCRIPTION
338: "The value of this object identifies the
339: 802.5 interface for which this entry
340: contains management information. The
341: value of this object for a particular
342: interface has the same value as the
343: ifIndex object, defined in [4,6], for
344: the same interface."
345: ::= { dot5StatsEntry 1 }
346:
347: dot5StatsLineErrors OBJECT-TYPE
347: error -
type `Counter' of node `dot5StatsLineErrors' does not resolve to a known base type
348: SYNTAX Counter
349: ACCESS read-only
350: STATUS mandatory
351: DESCRIPTION
352: "This counter is incremented when a frame
353: or token is copied or repeated by a
354: station, the E bit is zero in the frame
355: or token and one of the following
356: conditions exists: 1) there is a
357: non-data bit (J or K bit) between the SD
358: and the ED of the frame or token, or
359: 2) there is an FCS error in the frame."
360: ::= { dot5StatsEntry 2 }
361:
362: dot5StatsBurstErrors OBJECT-TYPE
362: error -
type `Counter' of node `dot5StatsBurstErrors' does not resolve to a known base type
363: SYNTAX Counter
364: ACCESS read-only
365: STATUS mandatory
366: DESCRIPTION
367: "This counter is incremented when a station
368: detects the absence of transitions for five
369: half-bit timers (burst-five error)."
370: ::= { dot5StatsEntry 3 }
371:
372: dot5StatsACErrors OBJECT-TYPE
372: error -
type `Counter' of node `dot5StatsACErrors' does not resolve to a known base type
373: SYNTAX Counter
374: ACCESS read-only
375: STATUS mandatory
376: DESCRIPTION
377: "This counter is incremented when a station
378: receives an AMP or SMP frame in which A is
379: equal to C is equal to 0, and then receives
380: another SMP frame with A is equal to C is
381: equal to 0 without first receiving an AMP
382: frame. It denotes a station that cannot set
383: the AC bits properly."
384: ::= { dot5StatsEntry 4 }
385:
386: dot5StatsAbortTransErrors OBJECT-TYPE
386: error -
type `Counter' of node `dot5StatsAbortTransErrors' does not resolve to a known base type
387: SYNTAX Counter
388: ACCESS read-only
389: STATUS mandatory
390: DESCRIPTION
391: "This counter is incremented when a station
392: transmits an abort delimiter while
393: transmitting."
394: ::= { dot5StatsEntry 5 }
395:
396: dot5StatsInternalErrors OBJECT-TYPE
396: error -
type `Counter' of node `dot5StatsInternalErrors' does not resolve to a known base type
397: SYNTAX Counter
398: ACCESS read-only
399: STATUS mandatory
400: DESCRIPTION
401: "This counter is incremented when a station
402: recognizes an internal error."
403: ::= { dot5StatsEntry 6 }
404:
405: dot5StatsLostFrameErrors OBJECT-TYPE
405: error -
type `Counter' of node `dot5StatsLostFrameErrors' does not resolve to a known base type
406: SYNTAX Counter
407: ACCESS read-only
408: STATUS mandatory
409: DESCRIPTION
410: "This counter is incremented when a station
411: is transmitting and its TRR timer expires.
412: This condition denotes a condition where a
413: transmitting station in strip mode does not
414: receive the trailer of the frame before the
415: TRR timer goes off."
416: ::= { dot5StatsEntry 7 }
417:
418: dot5StatsReceiveCongestions OBJECT-TYPE
418: error -
type `Counter' of node `dot5StatsReceiveCongestions' does not resolve to a known base type
419: SYNTAX Counter
420: ACCESS read-only
421: STATUS mandatory
422: DESCRIPTION
423: "This counter is incremented when a station
424: recognizes a frame addressed to its
425: specific address, but has no available
426: buffer space indicating that the station
427: is congested."
428: ::= { dot5StatsEntry 8 }
429:
430: dot5StatsFrameCopiedErrors OBJECT-TYPE
430: error -
type `Counter' of node `dot5StatsFrameCopiedErrors' does not resolve to a known base type
431: SYNTAX Counter
432: ACCESS read-only
433: STATUS mandatory
434: DESCRIPTION
435: "This counter is incremented when a station
436: recognizes a frame addressed to its
437: specific address and detects that the FS
438: field A bits are set to 1 indicating a
439: possible line hit or duplicate address."
440: ::= { dot5StatsEntry 9 }
441:
442: dot5StatsTokenErrors OBJECT-TYPE
442: error -
type `Counter' of node `dot5StatsTokenErrors' does not resolve to a known base type
443: SYNTAX Counter
444: ACCESS read-only
445: STATUS mandatory
446: DESCRIPTION
447: "This counter is incremented when a station
448: acting as the active monitor recognizes an
449: error condition that needs a token
450: transmitted."
451: ::= { dot5StatsEntry 10 }
452:
453: dot5StatsSoftErrors OBJECT-TYPE
453: error -
type `Counter' of node `dot5StatsSoftErrors' does not resolve to a known base type
454: SYNTAX Counter
455: ACCESS read-only
456: STATUS mandatory
457: DESCRIPTION
458: "The number of Soft Errors the interface
459: has detected. It directly corresponds to
460: the number of Report Error MAC frames
461: that this interface has transmitted.
462: Soft Errors are those which are
463: recoverable by the MAC layer protocols."
464: ::= { dot5StatsEntry 11 }
465:
466: dot5StatsHardErrors OBJECT-TYPE
466: error -
type `Counter' of node `dot5StatsHardErrors' does not resolve to a known base type
467: SYNTAX Counter
468: ACCESS read-only
469: STATUS mandatory
470: DESCRIPTION
471: "The number of times this interface has
472: detected an immediately recoverable
473: fatal error. It denotes the number of
474: times this interface is either
475: transmitting or receiving beacon MAC
476: frames."
477: ::= { dot5StatsEntry 12 }
478:
479: dot5StatsSignalLoss OBJECT-TYPE
479: error -
type `Counter' of node `dot5StatsSignalLoss' does not resolve to a known base type
480: SYNTAX Counter
481: ACCESS read-only
482: STATUS mandatory
483: DESCRIPTION
484: "The number of times this interface has
485: detected the loss of signal condition from
486: the ring."
487: ::= { dot5StatsEntry 13 }
488:
489: dot5StatsTransmitBeacons OBJECT-TYPE
489: error -
type `Counter' of node `dot5StatsTransmitBeacons' does not resolve to a known base type
490: SYNTAX Counter
491: ACCESS read-only
492: STATUS mandatory
493: DESCRIPTION
494: "The number of times this interface has
495: transmitted a beacon frame."
496: ::= { dot5StatsEntry 14 }
497:
498: dot5StatsRecoverys OBJECT-TYPE
498: error -
type `Counter' of node `dot5StatsRecoverys' does not resolve to a known base type
499: SYNTAX Counter
500: ACCESS read-only
501: STATUS mandatory
502: DESCRIPTION
503: "The number of Claim Token MAC frames
504: received or transmitted after the interface
505: has received a Ring Purge MAC frame. This
506: counter signifies the number of times the
507: ring has been purged and is being recovered
508: back into a normal operating state."
509: ::= { dot5StatsEntry 15 }
510:
511: dot5StatsLobeWires OBJECT-TYPE
511: error -
type `Counter' of node `dot5StatsLobeWires' does not resolve to a known base type
512: SYNTAX Counter
513: ACCESS read-only
514: STATUS mandatory
515: DESCRIPTION
516: "The number of times the interface has
517: detected an open or short circuit in the
518: lobe data path. The adapter will be closed
519: and dot5RingState will signify this
520: condition."
521: ::= { dot5StatsEntry 16 }
522:
523: dot5StatsRemoves OBJECT-TYPE
523: error -
type `Counter' of node `dot5StatsRemoves' does not resolve to a known base type
524: SYNTAX Counter
525: ACCESS read-only
526: STATUS mandatory
527: DESCRIPTION
528: "The number of times the interface has
529: received a Remove Ring Station MAC frame
530: request. When this frame is received
531: the interface will enter the close state
532: and dot5RingState will signify this
533: condition."
534: ::= { dot5StatsEntry 17 }
535:
536: dot5StatsSingles OBJECT-TYPE
536: error -
type `Counter' of node `dot5StatsSingles' does not resolve to a known base type
537: SYNTAX Counter
538: ACCESS read-only
539: STATUS mandatory
540: DESCRIPTION
541: "The number of times the interface has
542: sensed that it is the only station on the
543: ring. This will happen if the interface
544: is the first one up on a ring, or if
545: there is a hardware problem."
546: ::= { dot5StatsEntry 18 }
547:
548: dot5StatsFreqErrors OBJECT-TYPE
548: error -
type `Counter' of node `dot5StatsFreqErrors' does not resolve to a known base type
549: SYNTAX Counter
550: ACCESS read-only
551: STATUS optional
552: DESCRIPTION
553: "The number of times the interface has
554: detected that the frequency of the
555: incoming signal differs from the expected
556: frequency by more than that specified by
557: the IEEE 802.5 standard, see chapter 7
558: in [10]."
559: ::= { dot5StatsEntry 19 }
560:
561:
562: -- The Timer Table
563:
564: -- This group contains the values of the timers defined in
565: -- [10] for 802.5 interfaces. It is optional that systems
566: -- having 802.5 interfaces implement this group.
567:
568: dot5TimerTable OBJECT-TYPE
569: SYNTAX SEQUENCE OF Dot5TimerEntry
570: ACCESS not-accessible
571: STATUS mandatory
572: DESCRIPTION
573: "This table contains Token Ring interface
574: timer values, one entry per 802.5
575: interface."
576: ::= { dot5 5 }
577:
578: dot5TimerEntry OBJECT-TYPE
579: SYNTAX Dot5TimerEntry
580: ACCESS not-accessible
581: STATUS mandatory
582: DESCRIPTION
583: "A list of Token Ring timer values for an
584: 802.5 interface."
585: INDEX { dot5TimerIfIndex }
586: ::= { dot5TimerTable 1 }
587:
588: Dot5TimerEntry
589: ::= SEQUENCE {
590: dot5TimerIfIndex
591: INTEGER,
592: dot5TimerReturnRepeat
593: INTEGER,
594: dot5TimerHolding
595: INTEGER,
596: dot5TimerQueuePDU
597: INTEGER,
598: dot5TimerValidTransmit
599: INTEGER,
600: dot5TimerNoToken
601: INTEGER,
602: dot5TimerActiveMon
603: INTEGER,
604: dot5TimerStandbyMon
605: INTEGER,
606: dot5TimerErrorReport
607: INTEGER,
608: dot5TimerBeaconTransmit
609: INTEGER,
610: dot5TimerBeaconReceive
611: INTEGER
612: }
613:
614: dot5TimerIfIndex OBJECT-TYPE
614: error -
index element `dot5TimerIfIndex' of row `dot5TimerEntry' must have a range restriction
615: SYNTAX INTEGER
616: ACCESS read-only
617: STATUS mandatory
618: DESCRIPTION
619: "The value of this object identifies the
620: 802.5 interface for which this entry
621: contains timer values. The value of
622: this object for a particular interface
623: has the same value as the ifIndex
624: object, defined in [4,6], for the same
625: interface."
626: ::= { dot5TimerEntry 1 }
627:
628: dot5TimerReturnRepeat OBJECT-TYPE
629: SYNTAX INTEGER
630: ACCESS read-only
631: STATUS mandatory
632: DESCRIPTION
633: "The time-out value used to ensure the
634: interface will return to Repeat State, in
635: units of 100 micro-seconds. The value
636: should be greater than the maximum ring
637: latency.
638: Implementors are encouraged to provide
639: read-write access to this object if that is
640: possible/useful in their system, but giving
641: due consideration to the dangers of
642: write-able timers."
643: ::= { dot5TimerEntry 2 }
644:
645: dot5TimerHolding OBJECT-TYPE
646: SYNTAX INTEGER
647: ACCESS read-only
648: STATUS mandatory
649: DESCRIPTION
650: "Maximum period of time a station is
651: permitted to transmit frames after capturing
652: a token, in units of 100 micro-seconds.
653: Implementors are encouraged to provide
654: read-write access to this object if that is
655: possible/useful in their system, but giving
656: due consideration to the dangers of
657: write-able timers."
658: ::= { dot5TimerEntry 3 }
659:
660: dot5TimerQueuePDU OBJECT-TYPE
661: SYNTAX INTEGER
662: ACCESS read-only
663: STATUS mandatory
664: DESCRIPTION
665: "The time-out value for enqueuing of an SMP
666: PDU after reception of an AMP or SMP
667: frame in which the A and C bits were
668: equal to 0, in units of 100
669: micro-seconds.
670: Implementors are encouraged to provide
671:
672: read-write access to this object if that is
673: possible/useful in their system, but giving
674: due consideration to the dangers of
675: write-able timers."
676: ::= { dot5TimerEntry 4 }
677:
678: dot5TimerValidTransmit OBJECT-TYPE
679: SYNTAX INTEGER
680: ACCESS read-only
681: STATUS mandatory
682: DESCRIPTION
683: "The time-out value used by the active
684: monitor to detect the absence of valid
685: transmissions, in units of 100
686: micro-seconds.
687: Implementors are encouraged to provide
688: read-write access to this object if that is
689: possible/useful in their system, but giving
690: due consideration to the dangers of
691: write-able timers."
692: ::= { dot5TimerEntry 5 }
693:
694: dot5TimerNoToken OBJECT-TYPE
695: SYNTAX INTEGER
696: ACCESS read-only
697: STATUS mandatory
698: DESCRIPTION
699: "The time-out value used to recover from
700: various-related error situations [9].
701: If N is the maximum number of stations on
702: the ring, the value of this timer is
703: normally:
704: dot5TimerReturnRepeat + N*dot5TimerHolding.
705: Implementors are encouraged to provide
706: read-write access to this object if that is
707: possible/useful in their system, but giving
708: due consideration to the dangers of
709: write-able timers."
710: ::= { dot5TimerEntry 6 }
711:
712: dot5TimerActiveMon OBJECT-TYPE
713: SYNTAX INTEGER
714: ACCESS read-only
715: STATUS mandatory
716: DESCRIPTION
717: "The time-out value used by the active
718: monitor to stimulate the enqueuing of an
719: AMP PDU for transmission, in units of
720: 100 micro-seconds.
721: Implementors are encouraged to provide
722: read-write access to this object if that is
723: possible/useful in their system, but giving
724: due consideration to the dangers of
725: write-able timers."
726: ::= { dot5TimerEntry 7 }
727:
728: dot5TimerStandbyMon OBJECT-TYPE
729: SYNTAX INTEGER
730: ACCESS read-only
731: STATUS mandatory
732: DESCRIPTION
733: "The time-out value used by the stand-by
734: monitors to ensure that there is an active
735: monitor on the ring and to detect a
736: continuous stream of tokens, in units of
737: 100 micro-seconds.
738: Implementors are encouraged to provide
739: read-write access to this object if that is
740: possible/useful in their system, but giving
741: due consideration to the dangers of
742: write-able timers."
743: ::= { dot5TimerEntry 8 }
744:
745: dot5TimerErrorReport OBJECT-TYPE
746: SYNTAX INTEGER
747: ACCESS read-only
748: STATUS mandatory
749: DESCRIPTION
750: "The time-out value which determines how
751: often a station shall send a Report Error
752: MAC frame to report its error counters,
753: in units of 100 micro-seconds.
754: Implementors are encouraged to provide
755: read-write access to this object if that is
756: possible/useful in their system, but giving
757: due consideration to the dangers of
758: write-able timers."
759: ::= { dot5TimerEntry 9 }
760:
761: dot5TimerBeaconTransmit OBJECT-TYPE
762: SYNTAX INTEGER
763: ACCESS read-only
764: STATUS mandatory
765: DESCRIPTION
766: "The time-out value which determines how
767: long a station shall remain in the state
768: of transmitting Beacon frames before
769: entering the Bypass state, in units of
770: 100 micro-seconds.
771: Implementors are encouraged to provide
772: read-write access to this object if that is
773: possible/useful in their system, but giving
774: due consideration to the dangers of
775: write-able timers."
776: ::= { dot5TimerEntry 10 }
777:
778: dot5TimerBeaconReceive OBJECT-TYPE
779: SYNTAX INTEGER
780: ACCESS read-only
781: STATUS mandatory
782: DESCRIPTION
783: "The time-out value which determines how
784: long a station shall receive Beacon
785: frames from its downstream neighbor
786: before entering the Bypass state, in
787: units of 100 micro-seconds.
788: Implementors are encouraged to provide
789: read-write access to this object if that is
790: possible/useful in their system, but giving
791: due consideration to the dangers of
792: write-able timers."
793: ::= { dot5TimerEntry 11 }
794:
795:
796: -- 802.5 Interface Tests
797:
798: dot5Tests OBJECT IDENTIFIER ::= { dot5 3 }
799:
800: -- The extensions to the interfaces table proposed in [11]
801: -- define a table object, ifExtnsTestTable, through which a
802: -- network manager can instruct an agent to test an interface
803: -- for various faults. A test to be performed is identified
804: -- (as the value of ifExtnsTestType) via an OBJECT IDENTIFIER.
805: --
806: -- The Full-Duplex Loop Back Test is a common test, defined
807: -- in [11] as:
808: --
809: -- testFullDuplexLoopBack
810: --
811: -- Invoking this test on a 802.5 interface causes the
812: -- interface to check the path from memory through the
813: -- chip set's internal logic and back to memory, thus
814: -- checking the proper functioning of the systems's
815: -- interface to the chip set.
816: -- The Insert Function test is defined by:
817:
818: testInsertFunc OBJECT IDENTIFIER ::= { dot5Tests 1 }
819:
820: -- Invoking this test causes the station to test the insert
821: -- ring logic of the hardware if the station's lobe media
822: -- cable is connected to a wiring concentrator. Note that
823: -- this command inserts the station into the network, and
824: -- thus, could cause problems if the station is connected
825: -- to a operational network.
826:
827: -- 802.5 Hardware Chip Sets
828:
829: dot5ChipSets OBJECT IDENTIFIER ::= { dot5 4 }
830:
831: -- The extensions to the interfaces table proposed in [11]
832: -- define an object, ifExtnsChipSet, with the syntax of
833: -- OBJECT IDENTIFIER, to identify the hardware chip set in
834: -- use by an interface. That definition specifies just
835: -- one applicable object identifier:
836: --
837: -- unknownChipSet
838: --
839: -- for use as the value of ifExtnsChipSet when the specific
840: -- chip set is unknown.
841: --
842: -- This MIB defines the following for use as values of
843: -- ifExtnsChipSet:
844:
845: -- IBM 16/4 Mb/s
846: chipSetIBM16 OBJECT IDENTIFIER ::= { dot5ChipSets 1 }
847:
848: -- TI 4Mb/s
849: chipSetTItms380 OBJECT IDENTIFIER ::= { dot5ChipSets 2 }
850:
851: -- TI 16/4 Mb/s
852: chipSetTItms380c16 OBJECT IDENTIFIER ::= { dot5ChipSets 3 }
853:
854: END