1 EtherLike-MIB DEFINITIONS ::= BEGIN
4 MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY,
5 Counter32, mib-2, transmission
7 MODULE-COMPLIANCE, OBJECT-GROUP
9 ifIndex, InterfaceIndex
12 etherMIB MODULE-IDENTITY
13 LAST-UPDATED "9908240400Z" -- August 24, 1999
14 ORGANIZATION "IETF Ethernet Interfaces and Hub MIB
17 "WG E-mail: hubmib@hprnd.rose.hp.com
18 To subscribe: hubmib-request@hprnd.rose.hp.com
21 Postal: Lucent Technologies
22 Atidum Technology Park, Bldg. 3
26 E-mail: dromasca@lucent.com
29 Postal: Hewlett-Packard Company
30 8000 Foothills Blvd. M/S 5557
31 Roseville, CA 95747-5557
35 E-mail: johnf@rose.hp.com
37 Editor: Jeffrey Johnson
38 Postal: RedBack Networks
39 2570 North First Street, Suite 410
44 E-Mail: jeff@redbacknetworks.com"
45 DESCRIPTION "The MIB module to describe generic objects for
47 Ethernet-like network interfaces.
49 The following reference is used throughout this
52 [IEEE 802.3 Std] refers to:
53 IEEE Std 802.3, 1998 Edition: 'Information
54 technology - Telecommunications and
55 information exchange between systems -
56 Local and metropolitan area networks -
57 Specific requirements - Part 3: Carrier
58 sense multiple access with collision
59 detection (CSMA/CD) access method and
60 physical layer specifications',
63 Of particular interest is Clause 30, '10Mb/s,
64 100Mb/s and 1000Mb/s Management'."
66 REVISION "9908240400Z" -- August 24, 1999
67 DESCRIPTION "Updated to include support for 1000 Mb/sec
68 interfaces and full-duplex interfaces.
69 This version published as RFC 2665."
71 REVISION "9806032150Z"
72 DESCRIPTION "Updated to include support for 100 Mb/sec
74 This version published as RFC 2358."
76 REVISION "9402030400Z"
77 DESCRIPTION "Initial version, published as RFC 1650."
80 etherMIBObjects OBJECT IDENTIFIER ::= { etherMIB 1 }
82 dot3 OBJECT IDENTIFIER ::= { transmission 7 }
84 -- the Ethernet-like Statistics group
86 dot3StatsTable OBJECT-TYPE
87 SYNTAX SEQUENCE OF Dot3StatsEntry
88 MAX-ACCESS not-accessible
90 DESCRIPTION "Statistics for a collection of ethernet-like
91 interfaces attached to a particular system.
92 There will be one row in this table for each
94 ethernet-like interface in the system."
97 dot3StatsEntry OBJECT-TYPE
99 MAX-ACCESS not-accessible
101 DESCRIPTION "Statistics for a particular interface to an
102 ethernet-like medium."
103 INDEX { dot3StatsIndex }
104 ::= { dot3StatsTable 1 }
108 dot3StatsIndex InterfaceIndex,
109 dot3StatsAlignmentErrors Counter32,
110 dot3StatsFCSErrors Counter32,
111 dot3StatsSingleCollisionFrames Counter32,
112 dot3StatsMultipleCollisionFrames Counter32,
113 dot3StatsSQETestErrors Counter32,
114 dot3StatsDeferredTransmissions Counter32,
115 dot3StatsLateCollisions Counter32,
116 dot3StatsExcessiveCollisions Counter32,
117 dot3StatsInternalMacTransmitErrors Counter32,
118 dot3StatsCarrierSenseErrors Counter32,
119 dot3StatsFrameTooLongs Counter32,
120 dot3StatsInternalMacReceiveErrors Counter32,
121 dot3StatsEtherChipSet OBJECT IDENTIFIER,
122 dot3StatsSymbolErrors Counter32,
123 dot3StatsDuplexStatus INTEGER
126 dot3StatsIndex OBJECT-TYPE
127 SYNTAX InterfaceIndex
130 DESCRIPTION "An index value that uniquely identifies an
131 interface to an ethernet-like medium. The
132 interface identified by a particular value of
133 this index is the same interface as identified
134 by the same value of ifIndex."
135 REFERENCE "RFC 2233, ifIndex"
136 ::= { dot3StatsEntry 1 }
138 dot3StatsAlignmentErrors OBJECT-TYPE
142 DESCRIPTION "A count of frames received on a particular
143 interface that are not an integral number of
144 octets in length and do not pass the FCS check.
146 The count represented by an instance of this
147 object is incremented when the alignmentError
148 status is returned by the MAC service to the
149 LLC (or other MAC user). Received frames for
150 which multiple error conditions obtain are,
151 according to the conventions of IEEE 802.3
152 Layer Management, counted exclusively according
153 to the error status presented to the LLC.
155 This counter does not increment for 8-bit wide
156 group encoding schemes.
158 Discontinuities in the value of this counter can
159 occur at re-initialization of the management
160 system, and at other times as indicated by the
161 value of ifCounterDiscontinuityTime."
162 REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.7,
164 ::= { dot3StatsEntry 2 }
166 dot3StatsFCSErrors OBJECT-TYPE
170 DESCRIPTION "A count of frames received on a particular
171 interface that are an integral number of octets
172 in length but do not pass the FCS check. This
173 count does not include frames received with
174 frame-too-long or frame-too-short error.
176 The count represented by an instance of this
177 object is incremented when the frameCheckError
178 status is returned by the MAC service to the
179 LLC (or other MAC user). Received frames for
180 which multiple error conditions obtain are,
181 according to the conventions of IEEE 802.3
182 Layer Management, counted exclusively according
183 to the error status presented to the LLC.
185 Note: Coding errors detected by the physical
186 layer for speeds above 10 Mb/s will cause the
187 frame to fail the FCS check.
188 Discontinuities in the value of this counter can
189 occur at re-initialization of the management
191 system, and at other times as indicated by the
192 value of ifCounterDiscontinuityTime."
193 REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.6,
194 aFrameCheckSequenceErrors."
195 ::= { dot3StatsEntry 3 }
197 dot3StatsSingleCollisionFrames OBJECT-TYPE
201 DESCRIPTION "A count of successfully transmitted frames on
202 a particular interface for which transmission
203 is inhibited by exactly one collision.
205 A frame that is counted by an instance of this
206 object is also counted by the corresponding
207 instance of either the ifOutUcastPkts,
208 ifOutMulticastPkts, or ifOutBroadcastPkts,
209 and is not counted by the corresponding
210 instance of the dot3StatsMultipleCollisionFrames
213 This counter does not increment when the
214 interface is operating in full-duplex mode.
216 Discontinuities in the value of this counter can
217 occur at re-initialization of the management
218 system, and at other times as indicated by the
219 value of ifCounterDiscontinuityTime."
220 REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.3,
221 aSingleCollisionFrames."
222 ::= { dot3StatsEntry 4 }
224 dot3StatsMultipleCollisionFrames OBJECT-TYPE
228 DESCRIPTION "A count of successfully transmitted frames on
229 a particular interface for which transmission
230 is inhibited by more than one collision.
232 A frame that is counted by an instance of this
233 object is also counted by the corresponding
234 instance of either the ifOutUcastPkts,
235 ifOutMulticastPkts, or ifOutBroadcastPkts,
236 and is not counted by the corresponding
237 instance of the dot3StatsSingleCollisionFrames
240 This counter does not increment when the
241 interface is operating in full-duplex mode.
243 Discontinuities in the value of this counter can
244 occur at re-initialization of the management
245 system, and at other times as indicated by the
246 value of ifCounterDiscontinuityTime."
247 REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.4,
248 aMultipleCollisionFrames."
249 ::= { dot3StatsEntry 5 }
251 dot3StatsSQETestErrors OBJECT-TYPE
255 DESCRIPTION "A count of times that the SQE TEST ERROR
256 message is generated by the PLS sublayer for a
257 particular interface. The SQE TEST ERROR
258 is set in accordance with the rules for
259 verification of the SQE detection mechanism in
260 the PLS Carrier Sense Function as described in
261 IEEE Std. 802.3, 1998 Edition, section 7.2.4.6.
263 This counter does not increment on interfaces
264 operating at speeds greater than 10 Mb/s, or on
265 interfaces operating in full-duplex mode.
267 Discontinuities in the value of this counter can
268 occur at re-initialization of the management
269 system, and at other times as indicated by the
270 value of ifCounterDiscontinuityTime."
271 REFERENCE "[IEEE 802.3 Std.], 7.2.4.6, also 30.3.2.1.4,
273 ::= { dot3StatsEntry 6 }
275 dot3StatsDeferredTransmissions OBJECT-TYPE
279 DESCRIPTION "A count of frames for which the first
280 transmission attempt on a particular interface
281 is delayed because the medium is busy.
282 The count represented by an instance of this
283 object does not include frames involved in
286 This counter does not increment when the
287 interface is operating in full-duplex mode.
289 Discontinuities in the value of this counter can
290 occur at re-initialization of the management
291 system, and at other times as indicated by the
292 value of ifCounterDiscontinuityTime."
293 REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.9,
294 aFramesWithDeferredXmissions."
295 ::= { dot3StatsEntry 7 }
297 dot3StatsLateCollisions OBJECT-TYPE
301 DESCRIPTION "The number of times that a collision is
302 detected on a particular interface later than
303 one slotTime into the transmission of a packet.
305 A (late) collision included in a count
306 represented by an instance of this object is
307 also considered as a (generic) collision for
308 purposes of other collision-related
311 This counter does not increment when the
312 interface is operating in full-duplex mode.
314 Discontinuities in the value of this counter can
315 occur at re-initialization of the management
316 system, and at other times as indicated by the
317 value of ifCounterDiscontinuityTime."
318 REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.10,
320 ::= { dot3StatsEntry 8 }
322 dot3StatsExcessiveCollisions OBJECT-TYPE
326 DESCRIPTION "A count of frames for which transmission on a
327 particular interface fails due to excessive
329 This counter does not increment when the
330 interface is operating in full-duplex mode.
332 Discontinuities in the value of this counter can
333 occur at re-initialization of the management
334 system, and at other times as indicated by the
335 value of ifCounterDiscontinuityTime."
336 REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.11,
337 aFramesAbortedDueToXSColls."
338 ::= { dot3StatsEntry 9 }
340 dot3StatsInternalMacTransmitErrors OBJECT-TYPE
344 DESCRIPTION "A count of frames for which transmission on a
345 particular interface fails due to an internal
346 MAC sublayer transmit error. A frame is only
347 counted by an instance of this object if it is
348 not counted by the corresponding instance of
349 either the dot3StatsLateCollisions object, the
350 dot3StatsExcessiveCollisions object, or the
351 dot3StatsCarrierSenseErrors object.
353 The precise meaning of the count represented by
354 an instance of this object is implementation-
355 specific. In particular, an instance of this
356 object may represent a count of transmission
357 errors on a particular interface that are not
360 Discontinuities in the value of this counter can
361 occur at re-initialization of the management
362 system, and at other times as indicated by the
363 value of ifCounterDiscontinuityTime."
364 REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.12,
365 aFramesLostDueToIntMACXmitError."
366 ::= { dot3StatsEntry 10 }
368 dot3StatsCarrierSenseErrors OBJECT-TYPE
372 DESCRIPTION "The number of times that the carrier sense
373 condition was lost or never asserted when
374 attempting to transmit a frame on a particular
377 The count represented by an instance of this
378 object is incremented at most once per
379 transmission attempt, even if the carrier sense
380 condition fluctuates during a transmission
383 This counter does not increment when the
384 interface is operating in full-duplex mode.
386 Discontinuities in the value of this counter can
387 occur at re-initialization of the management
388 system, and at other times as indicated by the
389 value of ifCounterDiscontinuityTime."
390 REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.13,
391 aCarrierSenseErrors."
392 ::= { dot3StatsEntry 11 }
394 -- { dot3StatsEntry 12 } is not assigned
396 dot3StatsFrameTooLongs OBJECT-TYPE
400 DESCRIPTION "A count of frames received on a particular
401 interface that exceed the maximum permitted
404 The count represented by an instance of this
405 object is incremented when the frameTooLong
406 status is returned by the MAC service to the
407 LLC (or other MAC user). Received frames for
408 which multiple error conditions obtain are,
409 according to the conventions of IEEE 802.3
410 Layer Management, counted exclusively according
411 to the error status presented to the LLC.
413 Discontinuities in the value of this counter can
414 occur at re-initialization of the management
415 system, and at other times as indicated by the
416 value of ifCounterDiscontinuityTime."
417 REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.25,
418 aFrameTooLongErrors."
419 ::= { dot3StatsEntry 13 }
421 -- { dot3StatsEntry 14 } is not assigned
423 -- { dot3StatsEntry 15 } is not assigned
425 dot3StatsInternalMacReceiveErrors OBJECT-TYPE
429 DESCRIPTION "A count of frames for which reception on a
430 particular interface fails due to an internal
431 MAC sublayer receive error. A frame is only
432 counted by an instance of this object if it is
433 not counted by the corresponding instance of
435 either the dot3StatsFrameTooLongs object, the
436 dot3StatsAlignmentErrors object, or the
437 dot3StatsFCSErrors object.
439 The precise meaning of the count represented by
440 an instance of this object is implementation-
441 specific. In particular, an instance of this
442 object may represent a count of receive errors
443 on a particular interface that are not
446 Discontinuities in the value of this counter can
447 occur at re-initialization of the management
448 system, and at other times as indicated by the
449 value of ifCounterDiscontinuityTime."
450 REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.15,
451 aFramesLostDueToIntMACRcvError."
452 ::= { dot3StatsEntry 16 }
454 dot3StatsEtherChipSet OBJECT-TYPE
455 SYNTAX OBJECT IDENTIFIER
458 DESCRIPTION "******** THIS OBJECT IS DEPRECATED ********
460 This object contains an OBJECT IDENTIFIER
461 which identifies the chipset used to
462 realize the interface. Ethernet-like
463 interfaces are typically built out of
464 several different chips. The MIB implementor
465 is presented with a decision of which chip
466 to identify via this object. The implementor
467 should identify the chip which is usually
468 called the Medium Access Control chip.
469 If no such chip is easily identifiable,
470 the implementor should identify the chip
471 which actually gathers the transmit
472 and receive statistics and error
473 indications. This would allow a
474 manager station to correlate the
475 statistics and the chip generating
476 them, giving it the ability to take
477 into account any known anomalies
479 ::= { dot3StatsEntry 17 }
481 dot3StatsSymbolErrors OBJECT-TYPE
485 DESCRIPTION "For an interface operating at 100 Mb/s, the
486 number of times there was an invalid data symbol
487 when a valid carrier was present.
489 For an interface operating in half-duplex mode
490 at 1000 Mb/s, the number of times the receiving
491 media is non-idle (a carrier event) for a period
492 of time equal to or greater than slotTime, and
493 during which there was at least one occurrence
494 of an event that causes the PHY to indicate
495 'Data reception error' or 'carrier extend error'
498 For an interface operating in full-duplex mode
499 at 1000 Mb/s, the number of times the receiving
500 media is non-idle a carrier event) for a period
501 of time equal to or greater than minFrameSize,
502 and during which there was at least one
503 occurrence of an event that causes the PHY to
504 indicate 'Data reception error' on the GMII.
506 The count represented by an instance of this
507 object is incremented at most once per carrier
508 event, even if multiple symbol errors occur
509 during the carrier event. This count does
510 not increment if a collision is present.
512 Discontinuities in the value of this counter can
513 occur at re-initialization of the management
514 system, and at other times as indicated by the
515 value of ifCounterDiscontinuityTime."
516 REFERENCE "[IEEE 802.3 Std.], 30.3.2.1.5,
517 aSymbolErrorDuringCarrier."
518 ::= { dot3StatsEntry 18 }
520 dot3StatsDuplexStatus OBJECT-TYPE
528 DESCRIPTION "The current mode of operation of the MAC
529 entity. 'unknown' indicates that the current
530 duplex mode could not be determined.
532 Management control of the duplex mode is
533 accomplished through the MAU MIB. When
534 an interface does not support autonegotiation,
535 or when autonegotiation is not enabled, the
536 duplex mode is controlled using
537 ifMauDefaultType. When autonegotiation is
538 supported and enabled, duplex mode is controlled
539 using ifMauAutoNegAdvertisedBits. In either
540 case, the currently operating duplex mode is
541 reflected both in this object and in ifMauType.
543 Note that this object provides redundant
544 information with ifMauType. Normally, redundant
545 objects are discouraged. However, in this
546 instance, it allows a management application to
547 determine the duplex status of an interface
548 without having to know every possible value of
549 ifMauType. This was felt to be sufficiently
550 valuable to justify the redundancy."
551 REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.32,
553 ::= { dot3StatsEntry 19 }
555 -- the Ethernet-like Collision Statistics group
557 -- Implementation of this group is optional; it is appropriate
558 -- for all systems which have the necessary metering
560 dot3CollTable OBJECT-TYPE
561 SYNTAX SEQUENCE OF Dot3CollEntry
562 MAX-ACCESS not-accessible
564 DESCRIPTION "A collection of collision histograms for a
565 particular set of interfaces."
566 REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.30,
570 dot3CollEntry OBJECT-TYPE
572 MAX-ACCESS not-accessible
574 DESCRIPTION "A cell in the histogram of per-frame
575 collisions for a particular interface. An
576 instance of this object represents the
577 frequency of individual MAC frames for which
578 the transmission (successful or otherwise) on a
579 particular interface is accompanied by a
581 particular number of media collisions."
582 INDEX { ifIndex, dot3CollCount }
583 ::= { dot3CollTable 1 }
587 dot3CollCount INTEGER,
588 dot3CollFrequencies Counter32
591 -- { dot3CollEntry 1 } is no longer in use
593 dot3CollCount OBJECT-TYPE
594 SYNTAX INTEGER (1..16)
595 MAX-ACCESS not-accessible
597 DESCRIPTION "The number of per-frame media collisions for
598 which a particular collision histogram cell
599 represents the frequency on a particular
601 ::= { dot3CollEntry 2 }
603 dot3CollFrequencies OBJECT-TYPE
607 DESCRIPTION "A count of individual MAC frames for which the
608 transmission (successful or otherwise) on a
609 particular interface occurs after the
610 frame has experienced exactly the number
611 of collisions in the associated
612 dot3CollCount object.
614 For example, a frame which is transmitted
615 on interface 77 after experiencing
616 exactly 4 collisions would be indicated
617 by incrementing only dot3CollFrequencies.77.4.
618 No other instance of dot3CollFrequencies would
619 be incremented in this example.
621 This counter does not increment when the
622 interface is operating in full-duplex mode.
624 Discontinuities in the value of this counter can
625 occur at re-initialization of the management
626 system, and at other times as indicated by the
627 value of ifCounterDiscontinuityTime."
628 ::= { dot3CollEntry 3 }
630 dot3ControlTable OBJECT-TYPE
631 SYNTAX SEQUENCE OF Dot3ControlEntry
632 MAX-ACCESS not-accessible
634 DESCRIPTION "A table of descriptive and status information
635 about the MAC Control sublayer on the
636 ethernet-like interfaces attached to a
637 particular system. There will be one row in
638 this table for each ethernet-like interface in
639 the system which implements the MAC Control
640 sublayer. If some, but not all, of the
641 ethernet-like interfaces in the system implement
642 the MAC Control sublayer, there will be fewer
643 rows in this table than in the dot3StatsTable."
646 dot3ControlEntry OBJECT-TYPE
647 SYNTAX Dot3ControlEntry
648 MAX-ACCESS not-accessible
650 DESCRIPTION "An entry in the table, containing information
651 about the MAC Control sublayer on a single
652 ethernet-like interface."
653 INDEX { dot3StatsIndex }
654 ::= { dot3ControlTable 1 }
658 dot3ControlFunctionsSupported BITS,
659 dot3ControlInUnknownOpcodes Counter32
662 dot3ControlFunctionsSupported OBJECT-TYPE
664 pause(0) -- 802.3x flow control
668 DESCRIPTION "A list of the possible MAC Control functions
669 implemented for this interface."
670 REFERENCE "[IEEE 802.3 Std.], 30.3.3.2,
671 aMACControlFunctionsSupported."
672 ::= { dot3ControlEntry 1 }
674 dot3ControlInUnknownOpcodes OBJECT-TYPE
678 DESCRIPTION "A count of MAC Control frames received on this
679 interface that contain an opcode that is not
680 supported by this device.
682 Discontinuities in the value of this counter can
683 occur at re-initialization of the management
684 system, and at other times as indicated by the
685 value of ifCounterDiscontinuityTime."
686 REFERENCE "[IEEE 802.3 Std.], 30.3.3.5,
687 aUnsupportedOpcodesReceived"
688 ::= { dot3ControlEntry 2 }
690 dot3PauseTable OBJECT-TYPE
691 SYNTAX SEQUENCE OF Dot3PauseEntry
692 MAX-ACCESS not-accessible
694 DESCRIPTION "A table of descriptive and status information
695 about the MAC Control PAUSE function on the
696 ethernet-like interfaces attached to a
697 particular system. There will be one row in
698 this table for each ethernet-like interface in
699 the system which supports the MAC Control PAUSE
700 function (i.e., the 'pause' bit in the
701 corresponding instance of
702 dot3ControlFunctionsSupported is set). If some,
703 but not all, of the ethernet-like interfaces in
704 the system implement the MAC Control PAUSE
705 function (for example, if some interfaces only
706 support half-duplex), there will be fewer rows
707 in this table than in the dot3StatsTable."
710 dot3PauseEntry OBJECT-TYPE
711 SYNTAX Dot3PauseEntry
712 MAX-ACCESS not-accessible
714 DESCRIPTION "An entry in the table, containing information
715 about the MAC Control PAUSE function on a single
716 ethernet-like interface."
717 INDEX { dot3StatsIndex }
718 ::= { dot3PauseTable 1 }
722 dot3PauseAdminMode INTEGER,
723 dot3PauseOperMode INTEGER,
724 dot3InPauseFrames Counter32,
725 dot3OutPauseFrames Counter32
729 dot3PauseAdminMode OBJECT-TYPE
736 MAX-ACCESS read-write
738 DESCRIPTION "This object is used to configure the default
739 administrative PAUSE mode for this interface.
741 This object represents the
742 administratively-configured PAUSE mode for this
743 interface. If auto-negotiation is not enabled
744 or is not implemented for the active MAU
745 attached to this interface, the value of this
746 object determines the operational PAUSE mode
747 of the interface whenever it is operating in
748 full-duplex mode. In this case, a set to this
749 object will force the interface into the
752 If auto-negotiation is implemented and enabled
753 for the MAU attached to this interface, the
754 PAUSE mode for this interface is determined by
755 auto-negotiation, and the value of this object
756 denotes the mode to which the interface will
757 automatically revert if/when auto-negotiation is
758 later disabled. Note that when auto-negotiation
759 is running, administrative control of the PAUSE
760 mode may be accomplished using the
761 ifMauAutoNegCapAdvertisedBits object in the
764 Note that the value of this object is ignored
765 when the interface is not operating in
768 An attempt to set this object to
769 'enabledXmit(2)' or 'enabledRcv(3)' will fail
770 on interfaces that do not support operation
771 at greater than 100 Mb/s."
772 ::= { dot3PauseEntry 1 }
774 dot3PauseOperMode OBJECT-TYPE
783 DESCRIPTION "This object reflects the PAUSE mode currently
784 in use on this interface, as determined by
785 either (1) the result of the auto-negotiation
786 function or (2) if auto-negotiation is not
787 enabled or is not implemented for the active MAU
788 attached to this interface, by the value of
789 dot3PauseAdminMode. Interfaces operating at
790 100 Mb/s or less will never return
791 'enabledXmit(2)' or 'enabledRcv(3)'. Interfaces
792 operating in half-duplex mode will always return
793 'disabled(1)'. Interfaces on which
794 auto-negotiation is enabled but not yet
795 completed should return the value
797 ::= { dot3PauseEntry 2 }
799 dot3InPauseFrames OBJECT-TYPE
803 DESCRIPTION "A count of MAC Control frames received on this
804 interface with an opcode indicating the PAUSE
807 This counter does not increment when the
808 interface is operating in half-duplex mode.
809 Discontinuities in the value of this counter can
810 occur at re-initialization of the management
811 system, and at other times as indicated by the
812 value of ifCounterDiscontinuityTime."
813 REFERENCE "[IEEE 802.3 Std.], 30.3.4.3,
814 aPAUSEMACCtrlFramesReceived."
815 ::= { dot3PauseEntry 3 }
817 dot3OutPauseFrames OBJECT-TYPE
821 DESCRIPTION "A count of MAC Control frames transmitted on
822 this interface with an opcode indicating the
826 This counter does not increment when the
827 interface is operating in half-duplex mode.
829 Discontinuities in the value of this counter can
830 occur at re-initialization of the management
831 system, and at other times as indicated by the
832 value of ifCounterDiscontinuityTime."
833 REFERENCE "[IEEE 802.3 Std.], 30.3.4.2,
834 aPAUSEMACCtrlFramesTransmitted."
835 ::= { dot3PauseEntry 4 }
839 dot3Tests OBJECT IDENTIFIER ::= { dot3 6 }
841 dot3Errors OBJECT IDENTIFIER ::= { dot3 7 }
845 dot3TestTdr OBJECT-IDENTITY
847 DESCRIPTION "The Time-Domain Reflectometry (TDR) test is
848 specific to ethernet-like interfaces of type
849 10Base5 and 10Base2. The TDR value may be
850 useful in determining the approximate distance
851 to a cable fault. It is advisable to repeat
852 this test to check for a consistent resulting
853 TDR value, to verify that there is a fault.
855 A TDR test returns as its result the time
856 interval, measured in 10 MHz ticks or 100 nsec
857 units, between the start of TDR test
858 transmission and the subsequent detection of a
859 collision or deassertion of carrier. On
860 successful completion of a TDR test, the result
861 is stored as the value of an appropriate
862 instance of an appropriate vendor specific MIB
863 object, and the OBJECT IDENTIFIER of that
864 instance is stored in the appropriate instance
865 of the appropriate test result code object
866 (thereby indicating where the result has been
872 dot3TestLoopBack OBJECT-IDENTITY
874 DESCRIPTION "This test configures the MAC chip and executes
875 an internal loopback test of memory, data paths,
876 and the MAC chip logic. This loopback test can
877 only be executed if the interface is offline.
878 Once the test has completed, the MAC chip should
879 be reinitialized for network operation, but it
880 should remain offline.
882 If an error occurs during a test, the
883 appropriate test result object will be set
884 to indicate a failure. The two OBJECT
885 IDENTIFIER values dot3ErrorInitError and
886 dot3ErrorLoopbackError may be used to provided
887 more information as values for an appropriate
888 test result code object."
891 dot3ErrorInitError OBJECT-IDENTITY
893 DESCRIPTION "Couldn't initialize MAC chip for test."
896 dot3ErrorLoopbackError OBJECT-IDENTITY
898 DESCRIPTION "Expected data not received (or not received
899 correctly) in loopback test."
902 -- { dot3 8 }, the dot3ChipSets tree, is defined in [28]
904 -- conformance information
906 etherConformance OBJECT IDENTIFIER ::= { etherMIB 2 }
908 etherGroups OBJECT IDENTIFIER ::= { etherConformance 1 }
909 etherCompliances OBJECT IDENTIFIER ::= { etherConformance 2 }
911 -- compliance statements
913 etherCompliance MODULE-COMPLIANCE
915 DESCRIPTION "******** THIS COMPLIANCE IS DEPRECATED ********
917 The compliance statement for managed network
918 entities which have ethernet-like network
921 This compliance is deprecated and replaced by
924 MODULE -- this module
925 MANDATORY-GROUPS { etherStatsGroup }
927 GROUP etherCollisionTableGroup
928 DESCRIPTION "This group is optional. It is appropriate
929 for all systems which have the necessary
930 metering. Implementation in such systems is
932 ::= { etherCompliances 1 }
934 ether100MbsCompliance MODULE-COMPLIANCE
936 DESCRIPTION "******** THIS COMPLIANCE IS DEPRECATED ********
938 The compliance statement for managed network
939 entities which have 100 Mb/sec ethernet-like
942 This compliance is deprecated and replaced by
945 MODULE -- this module
946 MANDATORY-GROUPS { etherStats100MbsGroup }
948 GROUP etherCollisionTableGroup
949 DESCRIPTION "This group is optional. It is appropriate
950 for all systems which have the necessary
951 metering. Implementation in such systems is
953 ::= { etherCompliances 2 }
955 dot3Compliance MODULE-COMPLIANCE
957 DESCRIPTION "The compliance statement for managed network
958 entities which have ethernet-like network
961 MODULE -- this module
962 MANDATORY-GROUPS { etherStatsBaseGroup }
964 GROUP etherDuplexGroup
965 DESCRIPTION "This group is mandatory for all
966 ethernet-like network interfaces which are
967 capable of operating in full-duplex mode.
968 It is highly recommended for all
970 ethernet-like network interfaces."
972 GROUP etherStatsLowSpeedGroup
973 DESCRIPTION "This group is mandatory for all
974 ethernet-like network interfaces which are
975 capable of operating at 10 Mb/s or slower in
978 GROUP etherStatsHighSpeedGroup
979 DESCRIPTION "This group is mandatory for all
980 ethernet-like network interfaces which are
981 capable of operating at 100 Mb/s or faster."
983 GROUP etherControlGroup
984 DESCRIPTION "This group is mandatory for all
985 ethernet-like network interfaces that
986 support the MAC Control sublayer."
988 GROUP etherControlPauseGroup
989 DESCRIPTION "This group is mandatory for all
990 ethernet-like network interfaces that
991 support the MAC Control PAUSE function."
993 GROUP etherCollisionTableGroup
994 DESCRIPTION "This group is optional. It is appropriate
995 for all ethernet-like network interfaces
996 which are capable of operating in
997 half-duplex mode and have the necessary
998 metering. Implementation in systems with
999 such interfaces is highly recommended."
1000 ::= { etherCompliances 3 }
1002 -- units of conformance
1004 etherStatsGroup OBJECT-GROUP
1005 OBJECTS { dot3StatsIndex,
1006 dot3StatsAlignmentErrors,
1008 dot3StatsSingleCollisionFrames,
1009 dot3StatsMultipleCollisionFrames,
1010 dot3StatsSQETestErrors,
1011 dot3StatsDeferredTransmissions,
1012 dot3StatsLateCollisions,
1013 dot3StatsExcessiveCollisions,
1014 dot3StatsInternalMacTransmitErrors,
1015 dot3StatsCarrierSenseErrors,
1016 dot3StatsFrameTooLongs,
1017 dot3StatsInternalMacReceiveErrors,
1018 dot3StatsEtherChipSet
1021 DESCRIPTION "********* THIS GROUP IS DEPRECATED **********
1023 A collection of objects providing information
1024 applicable to all ethernet-like network
1027 This object group has been deprecated and
1028 replaced by etherStatsBaseGroup and
1029 etherStatsLowSpeedGroup."
1030 ::= { etherGroups 1 }
1032 etherCollisionTableGroup OBJECT-GROUP
1033 OBJECTS { dot3CollFrequencies
1036 DESCRIPTION "A collection of objects providing a histogram
1037 of packets successfully transmitted after
1038 experiencing exactly N collisions."
1039 ::= { etherGroups 2 }
1041 etherStats100MbsGroup OBJECT-GROUP
1042 OBJECTS { dot3StatsIndex,
1043 dot3StatsAlignmentErrors,
1045 dot3StatsSingleCollisionFrames,
1046 dot3StatsMultipleCollisionFrames,
1047 dot3StatsDeferredTransmissions,
1048 dot3StatsLateCollisions,
1049 dot3StatsExcessiveCollisions,
1050 dot3StatsInternalMacTransmitErrors,
1051 dot3StatsCarrierSenseErrors,
1052 dot3StatsFrameTooLongs,
1053 dot3StatsInternalMacReceiveErrors,
1054 dot3StatsEtherChipSet,
1055 dot3StatsSymbolErrors
1058 DESCRIPTION "********* THIS GROUP IS DEPRECATED **********
1060 A collection of objects providing information
1061 applicable to 100 Mb/sec ethernet-like network
1064 This object group has been deprecated and
1066 replaced by etherStatsBaseGroup and
1067 etherStatsHighSpeedGroup."
1068 ::= { etherGroups 3 }
1070 etherStatsBaseGroup OBJECT-GROUP
1071 OBJECTS { dot3StatsIndex,
1072 dot3StatsAlignmentErrors,
1074 dot3StatsSingleCollisionFrames,
1075 dot3StatsMultipleCollisionFrames,
1076 dot3StatsDeferredTransmissions,
1077 dot3StatsLateCollisions,
1078 dot3StatsExcessiveCollisions,
1079 dot3StatsInternalMacTransmitErrors,
1080 dot3StatsCarrierSenseErrors,
1081 dot3StatsFrameTooLongs,
1082 dot3StatsInternalMacReceiveErrors
1085 DESCRIPTION "A collection of objects providing information
1086 applicable to all ethernet-like network
1088 ::= { etherGroups 4 }
1090 etherStatsLowSpeedGroup OBJECT-GROUP
1091 OBJECTS { dot3StatsSQETestErrors }
1093 DESCRIPTION "A collection of objects providing information
1094 applicable to ethernet-like network interfaces
1095 capable of operating at 10 Mb/s or slower in
1097 ::= { etherGroups 5 }
1099 etherStatsHighSpeedGroup OBJECT-GROUP
1100 OBJECTS { dot3StatsSymbolErrors }
1102 DESCRIPTION "A collection of objects providing information
1103 applicable to ethernet-like network interfaces
1104 capable of operating at 100 Mb/s or faster."
1105 ::= { etherGroups 6 }
1107 etherDuplexGroup OBJECT-GROUP
1108 OBJECTS { dot3StatsDuplexStatus }
1110 DESCRIPTION "A collection of objects providing information
1111 about the duplex mode of an ethernet-like
1113 ::= { etherGroups 7 }
1115 etherControlGroup OBJECT-GROUP
1116 OBJECTS { dot3ControlFunctionsSupported,
1117 dot3ControlInUnknownOpcodes
1120 DESCRIPTION "A collection of objects providing information
1121 about the MAC Control sublayer on ethernet-like
1122 network interfaces."
1123 ::= { etherGroups 8 }
1125 etherControlPauseGroup OBJECT-GROUP
1126 OBJECTS { dot3PauseAdminMode,
1132 DESCRIPTION "A collection of objects providing information
1133 about and control of the MAC Control PAUSE
1134 function on ethernet-like network interfaces."
1135 ::= { etherGroups 9 }