Network Working Group J. Flick
Request for Comments: 3635 Hewlett-Packard Company
Obsoletes: 2665 September 2003
Category: Standards Track
Network Working Group J. Flick
Request for Comments: 3635 Hewlett-Packard Company
Obsoletes: 2665 September 2003
Category: Standards Track
Definitions of Managed Objects for the Ethernet-like Interface Types
类以太网接口类型的托管对象定义
Status of this Memo
本备忘录的状况
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
本文件规定了互联网社区的互联网标准跟踪协议，并要求进行讨论和提出改进建议。有关本协议的标准化状态和状态，请参考当前版本的“互联网官方协议标准”（STD 1）。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2003). All Rights Reserved.
版权所有（C）互联网协会（2003年）。版权所有。
Abstract
摘要
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing Ethernet-like interfaces. This memo obsoletes RFC 2665. It updates that specification by including management information useful for the management of 10 Gigabit per second (Gb/s) Ethernet interfaces.
此备忘录定义了管理信息库（MIB）的一部分，用于Internet社区中的网络管理协议。特别是，它定义了用于管理类以太网接口的对象。本备忘录废除RFC 2665。它更新了该规范，包括了对管理每秒10千兆位（Gb/s）以太网接口有用的管理信息。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. The Internet-Standard Management Framework . . . . . . . . . . 3
3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.1. Relation to MIB-2. . . . . . . . . . . . . . . . . . . . 4
3.2. Relation to the Interfaces MIB . . . . . . . . . . . . . 4
3.2.1. Layering Model . . . . . . . . . . . . . . . . . 4
3.2.2. Virtual Circuits . . . . . . . . . . . . . . . . 4
3.2.3. ifRcvAddressTable. . . . . . . . . . . . . . . . 5
3.2.4. ifType . . . . . . . . . . . . . . . . . . . . . 5
3.2.5. ifXxxOctets. . . . . . . . . . . . . . . . . . . 5
3.2.6. ifXxxXcastPkts . . . . . . . . . . . . . . . . . 6
3.2.7. ifMtu. . . . . . . . . . . . . . . . . . . . . . 8
3.2.8. ifSpeed and ifHighSpeed. . . . . . . . . . . . . 8
3.2.9. ifPhysAddress. . . . . . . . . . . . . . . . . . 9
3.2.10. Specific Interface MIB Objects. . . . . . . . . 10
3.3. Relation to the 802.3 MAU MIB. . . . . . . . . . . . . . 13
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. The Internet-Standard Management Framework . . . . . . . . . . 3
3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.1. Relation to MIB-2. . . . . . . . . . . . . . . . . . . . 4
3.2. Relation to the Interfaces MIB . . . . . . . . . . . . . 4
3.2.1. Layering Model . . . . . . . . . . . . . . . . . 4
3.2.2. Virtual Circuits . . . . . . . . . . . . . . . . 4
3.2.3. ifRcvAddressTable. . . . . . . . . . . . . . . . 5
3.2.4. ifType . . . . . . . . . . . . . . . . . . . . . 5
3.2.5. ifXxxOctets. . . . . . . . . . . . . . . . . . . 5
3.2.6. ifXxxXcastPkts . . . . . . . . . . . . . . . . . 6
3.2.7. ifMtu. . . . . . . . . . . . . . . . . . . . . . 8
3.2.8. ifSpeed and ifHighSpeed. . . . . . . . . . . . . 8
3.2.9. ifPhysAddress. . . . . . . . . . . . . . . . . . 9
3.2.10. Specific Interface MIB Objects. . . . . . . . . 10
3.3. Relation to the 802.3 MAU MIB. . . . . . . . . . . . . . 13
3.4. dot3StatsEtherChipSet. . . . . . . . . . . . . . . . . . 13
3.5. Mapping of IEEE 802.3 Managed Objects. . . . . . . . . . 14
4. Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . 17
5. Intellectual Property Statement. . . . . . . . . . . . . . . . 55
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 56
7. Normative References . . . . . . . . . . . . . . . . . . . . . 57
8. Informative References . . . . . . . . . . . . . . . . . . . . 58
9. Security Considerations. . . . . . . . . . . . . . . . . . . . 59
10. IANA Considerations. . . . . . . . . . . . . . . . . . . . . . 60
A. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 61
A.1. Changes since RFC 2665 . . . . . . . . . . . . . . . . . 61
A.2. Changes between RFC 2358 and RFC 2665 . . . . . . . . . 62
A.3. Changes between RFC 1650 and RFC 2358. . . . . . . . . . 62
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 63
Full Copyright Statement . . . . . . . . . . . . . . . . . . . . .64
3.4. dot3StatsEtherChipSet. . . . . . . . . . . . . . . . . . 13
3.5. Mapping of IEEE 802.3 Managed Objects. . . . . . . . . . 14
4. Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . 17
5. Intellectual Property Statement. . . . . . . . . . . . . . . . 55
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 56
7. Normative References . . . . . . . . . . . . . . . . . . . . . 57
8. Informative References . . . . . . . . . . . . . . . . . . . . 58
9. Security Considerations. . . . . . . . . . . . . . . . . . . . 59
10. IANA Considerations. . . . . . . . . . . . . . . . . . . . . . 60
A. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 61
A.1. Changes since RFC 2665 . . . . . . . . . . . . . . . . . 61
A.2. Changes between RFC 2358 and RFC 2665 . . . . . . . . . 62
A.3. Changes between RFC 1650 and RFC 2358. . . . . . . . . . 62
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 63
Full Copyright Statement . . . . . . . . . . . . . . . . . . . . .64
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing Ethernet-like interfaces.
此备忘录定义了管理信息库（MIB）的一部分，用于Internet社区中的网络管理协议。特别是，它定义了用于管理类以太网接口的对象。
This memo also includes a MIB module. This MIB module updates the list of managed objects specified in the earlier version of this MIB, module, RFC 2665 [RFC2665].
此备忘录还包括一个MIB模块。此MIB模块更新此MIB早期版本模块RFC 2665[RFC2665]中指定的托管对象列表。
Ethernet technology, as defined by the 802.3 Working Group of the IEEE, continues to evolve, with scalable increases in speed, new types of cabling and interfaces, and new features. This evolution may require changes in the managed objects in order to reflect this new functionality. This document, as with other documents issued by this working group, reflects a certain stage in the evolution of Ethernet technology. In the future, this document might be revised, or new documents might be issued by the Ethernet Interfaces and Hub MIB Working Group, in order to reflect the evolution of Ethernet technology.
根据IEEE 802.3工作组的定义，以太网技术不断发展，速度不断提高，布线和接口类型不断增加，功能不断增加。这种演变可能需要对托管对象进行更改，以反映这种新功能。与本工作组发布的其他文件一样，本文件反映了以太网技术发展的某个阶段。将来，以太网接口和集线器MIB工作组可能会修订本文件，或发布新的文件，以反映以太网技术的发展。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照[RFC2119]中所述进行解释。
For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410 [RFC3410].
有关描述当前互联网标准管理框架的文件的详细概述，请参阅RFC 3410[RFC3410]第7节。
Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This memo specifies a MIB module that is compliant to the SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580].
托管对象通过虚拟信息存储（称为管理信息库或MIB）进行访问。MIB对象通常通过简单网络管理协议（SNMP）进行访问。MIB中的对象是使用管理信息结构（SMI）中定义的机制定义的。本备忘录规定了符合SMIv2的MIB模块，如STD 58、RFC 2578[RFC2578]、STD 58、RFC 2579[RFC2579]和STD 58、RFC 2580[RFC2580]所述。
Instances of these object types represent attributes of an interface to an ethernet-like communications medium. At present, ethernet-like media are identified by the value ethernetCsmacd(6) of the ifType object in the Interfaces MIB [RFC2863]. Some older implementations may return the values iso88023Csmacd(7) or starLan(11) for ifType for ethernet-like media.
这些对象类型的实例表示类以太网通信介质接口的属性。目前，类以太网介质由接口MIB[RFC2863]中ifType对象的值ethernetCsmacd（6）标识。对于类似以太网的介质，一些较旧的实现可能会返回ifType的值iso88023Csmacd（7）或starLan（11）。
The definitions presented here are based on Section 30, "10 Mb/s, 100 Mb/s 1000 Mb/s and 10 Gb/s Management", and Annex 30A, "GDMO Specification for 802.3 managed object classes" of IEEE Std. 802.3, 2002 Edition [IEEE802.3], amended by IEEE Std. 802.3ae-2002 [IEEE802.3ae], as originally interpreted by Frank Kastenholz, then of Interlan in [KASTEN]. Implementors of these MIB objects should note that IEEE Std. 802.3 [IEEE802.3] explicitly describes (in the form of Pascal pseudocode) when, where, and how various MAC attributes are measured. The IEEE document also describes the effects of MAC actions that may be invoked by manipulating instances of the MIB objects defined here.
此处给出的定义基于IEEE标准802.3，2002年版[IEEE802.3]，经IEEE标准802.3ae-2002[IEEE802.3ae]修订，最初由Frank Kastenholz解释，随后由Interlan在[KASTEN]中解释的第30节“10 Mb/s、100 Mb/s 1000 Mb/s和10 Gb/s管理”，以及附录30A“802.3受管对象类的GDMO规范”. 这些MIB对象的实现者应该注意，IEEE标准802.3[IEEE802.3]明确描述了（以Pascal伪码的形式）测量各种MAC属性的时间、地点和方式。IEEE文档还描述了MAC操作的效果，这些操作可通过操作此处定义的MIB对象实例来调用。
To the extent that some of the attributes defined in [IEEE802.3] are represented by previously defined objects in MIB-2 [RFC1213] or in the Interfaces MIB [RFC2863], such attributes are not redundantly represented by objects defined in this memo. Among the attributes represented by objects defined in other memos are the number of octets transmitted or received on a particular interface, the number of frames transmitted or received on a particular interface, the promiscuous status of an interface, the MAC address of an interface, and multicast information associated with an interface.
如果[IEEE802.3]中定义的某些属性由MIB-2[RFC1213]或接口MIB[RFC2863]中先前定义的对象表示，则此类属性不会由本备忘录中定义的对象冗余表示。其他备忘录中定义的对象表示的属性包括在特定接口上传输或接收的八位字节数、在特定接口上传输或接收的帧数、接口的混杂状态、接口的MAC地址以及与接口相关联的多播信息。
This section applies only when this MIB is used in conjunction with the "old" [RFC1213] interface group.
仅当此MIB与“旧”[RFC1213]接口组一起使用时，本节才适用。
The relationship between an ethernet-like interface and an interface in the context of MIB-2 is one-to-one. As such, the value of an ifIndex object instance can be directly used to identify corresponding instances of the objects defined herein.
类以太网接口与MIB-2上下文中的接口之间的关系是一对一的。因此，ifIndex对象实例的值可直接用于识别本文定义的对象的对应实例。
For agents which implement the (now deprecated) ifSpecific object, an instance of that object that is associated with an ethernet-like interface has the OBJECT IDENTIFIER value:
对于实现（现已弃用）ifSpecific对象的代理，与类以太网接口关联的该对象的实例具有对象标识符值：
dot3 OBJECT IDENTIFIER ::= { transmission 7 }
dot3 OBJECT IDENTIFIER ::= { transmission 7 }
The Interface MIB [RFC2863] requires that any MIB which is an adjunct of the Interface MIB clarify specific areas within the Interface MIB. These areas were intentionally left vague in the Interface MIB to avoid over constraining the MIB, thereby precluding management of certain media-types.
接口MIB[RFC2863]要求任何作为接口MIB附件的MIB澄清接口MIB内的特定区域。这些区域在接口MIB中故意保持模糊，以避免过度约束MIB，从而排除对某些媒体类型的管理。
Section 4 of [RFC2863] enumerates several areas which a media-specific MIB must clarify. Each of these areas is addressed in a following subsection. The implementor is referred to [RFC2863] in order to understand the general intent of these areas.
[RFC2863]第4节列举了媒体特定MIB必须澄清的几个方面。以下小节将介绍这些领域中的每一个领域。为了了解这些领域的总体意图，请参考[RFC2863]。
Ordinarily, there are no sublayers for an ethernet-like interface. However there may be implementation-specific requirements which require the use of sublayers. One example is the use of 802.3 link aggregation. In this case, Annex 30C of [IEEE802.3] describes the layering model and the use of the ifStackTable for representing aggregated links. Another example is the use of the 802.3 WAN Interface Sublayer. In this case, The 802.3 WIS MIB [RFC3637] describes the layering model and the use of the ifStackTable for representing the WAN sublayer.
通常，类以太网接口没有子层。但是，可能存在需要使用子层的实现特定要求。一个例子是使用802.3链路聚合。在这种情况下，[IEEE802.3]的附录30C描述了分层模型和ifStackTable用于表示聚合链路的使用。另一个例子是802.3 WAN接口子层的使用。在这种情况下，802.3 WIS MIB[RFC3637]描述了分层模型以及用于表示WAN子层的ifStackTable的使用。
This medium does not support virtual circuits and this area is not applicable to this MIB.
此介质不支持虚拟电路，此区域不适用于此MIB。
This table contains all IEEE 802.3 addresses, unicast, multicast, and broadcast, for which this interface will receive packets and forward them up to a higher layer entity for local consumption. The format of the address, contained in ifRcvAddressAddress, is the same as for ifPhysAddress.
此表包含所有IEEE 802.3地址、单播、多播和广播，此接口将接收数据包并将其转发到更高层实体以供本地使用。ifRcvAddressAddress中包含的地址格式与ifPhysAddress的格式相同。
In the event that the interface is part of a MAC bridge, this table does not include unicast addresses which are accepted for possible forwarding out some other port. This table is explicitly not intended to provide a bridge address filtering mechanism.
如果接口是MAC网桥的一部分，此表不包括单播地址，这些地址可被接受用于转发其他端口。此表明确不是为了提供网桥地址过滤机制。
This MIB applies to interfaces which have the ifType value ethernetCsmacd(6). It is REQUIRED that all ethernet-like interfaces use an ifType of ethernetCsmacd(6) regardless of the speed that the interface is running or the link-layer encapsulation in use. Use of the ifType values iso88023Csmacd(7) and starLan(11) are deprecated, however some older implementations may return these values. Management applications should be prepared to receive these deprecated ifType values from older implementations.
此MIB适用于ifType值为ethernetCsmacd（6）的接口。要求所有类似以太网的接口使用ethernetCsmacd（6）的ifType，无论接口的运行速度或使用的链路层封装。不推荐使用ifType值iso88023Csmacd（7）和starLan（11），但是一些较旧的实现可能会返回这些值。管理应用程序应该准备好从较旧的实现中接收这些弃用的ifType值。
There are three other interface types defined in the IANAifType-MIB for Ethernet. They are fastEther(62), fastEtherFX(69), and gigabitEthernet(117). These interface types were registered by individual vendors, not by any IETF working group. A requirement for compliance with this document is that all ethernet-like interfaces MUST return ethernetCsmacd(6) for ifType, and MUST NOT return fastEther(62), fastEtherFX(69), or gigabitEthernet(117). However, as there are fielded implementations that do return these obsolete ifType values, management applications SHOULD be prepared to receive them from older implementations.
IANAifType MIB中为以太网定义了三种其他接口类型。它们是FastEthernet（62）、FastEthernerFX（69）和千兆以太网（117）。这些接口类型由单个供应商注册，而不是由任何IETF工作组注册。遵守本文件的要求是，所有类似以太网的接口必须返回ifType的ethernetCsmacd（6），并且不得返回FastEthernet（62）、FastEthernerFX（69）或gigabitEthernet（117）。但是，由于存在返回这些过时ifType值的已部署实现，管理应用程序应该准备好从较旧的实现接收这些值。
Information on the particular flavor of Ethernet that an interface is running is available from ifSpeed in the Interfaces MIB, and ifMauType in the 802.3 MAU MIB [RFC3636]. Note that implementation of the 802.3 MAU MIB [RFC3636] is REQUIRED for all ethernet-like interfaces.
接口正在运行的以太网的特定风格的信息可从接口MIB中的ifSpeed和802.3 MAU MIB中的ifMauType[RFC3636]获得。请注意，所有类似以太网的接口都需要实现802.3 MAU MIB[RFC3636]。
The Interface MIB octet counters, ifInOctets, ifOutOctets, ifHCInOctets and ifHCOutOctets, MUST include all octets in valid frames sent or received on the interface, including the MAC header and FCS, but not the preamble, start of frame delimiter, or extension octets. This corresponds to the definition of frameSize/8 in section
接口MIB八位字节计数器ifInOctets、IFOUTPETS、ifHCInOctets和IFHCOUTPETS必须包括在接口上发送或接收的有效帧中的所有八位字节，包括MAC报头和FCS，但不包括前导、帧开始分隔符或扩展八位字节。这与第节中frameSize/8的定义相对应
4.2.7.1 of [IEEE802.3] (frameSize is defined in bits rather than octets, and is defined as 2 x addressSize + lengthOrTypeSize + dataSize + crcSize). They do not include the number of octets in collided or failed transmit attempts, since the MAC layer driver typically does not have visibility to count these octets. They also do not include octets in received invalid frames, since this information is normally not passed to the MAC layer, and since non-promiscuous MAC implementations cannot reliably determine whether an invalid frame was actually addressed to this station.
4.2.7.1 [IEEE802.3]（帧大小以位而不是八位字节定义，并定义为2 x addressSize+lengthOrTypeSize+dataSize+crcSize）。它们不包括冲突或失败传输尝试中的八位字节数，因为MAC层驱动程序通常不具有统计这些八位字节的可见性。它们也不包括接收到的无效帧中的八位字节，因为该信息通常不会传递到MAC层，并且非混杂MAC实现无法可靠地确定无效帧是否实际发送到该站。
Note that these counters do include octets in valid MAC control frames sent or received on the interface, as well as octets in otherwise valid received MAC frames that are discarded by the MAC layer for some reason (insufficient buffer space, unknown protocol, etc.).
注意，这些计数器包括在接口上发送或接收的有效MAC控制帧中的八位字节，以及MAC层出于某种原因（缓冲区空间不足、未知协议等）丢弃的其他有效接收MAC帧中的八位字节。
Note that the octet counters in IF-MIB do not exactly match the definition of the octet counters in IEEE 802.3. aOctetsTransmittedOK and aOctetsReceivedOK count only the octets in the clientData and Pad fields, whereas ifInOctets and ifOutOctets include the entire MAC frame, including MAC header and FCS. However, the IF-MIB counters can be derived from the IEEE 802.3 counters as follows:
请注意，IF-MIB中的八位计数器与IEEE 802.3中八位计数器的定义不完全匹配。AOCTETSTRASTIMETEDOK和aOctetsReceivedOK仅统计clientData和Pad字段中的八位字节，而ifInOctets和IFOUTPoctets包括整个MAC帧，包括MAC标头和FCS。但是，IF-MIB计数器可以从IEEE 802.3计数器派生，如下所示：
ifInOctets = aOctetsReceivedOK + (18 * aFramesReceivedOK)
ifOutOctets = aOctetsTransmittedOK + (18 * aFramesTransmittedOK)
ifInOctets = aOctetsReceivedOK + (18 * aFramesReceivedOK)
ifOutOctets = aOctetsTransmittedOK + (18 * aFramesTransmittedOK)
Another difference to keep in mind between the IF-MIB counters and IEEE 802.3 counters is that in the IEEE 802.3 document, the frame counters and octet counters are always incremented together. aOctetsTransmittedOK counts the number of octets in frames that were counted by aFramesTransmittedOK. aOctetsReceivedOK counts the number of octets in frames that were counted by aFramesReceivedOK. This is not the case with the IF-MIB counters. The IF-MIB octet counters count the number of octets sent to or received from the layer below this interface, whereas the packet counters count the number of packets sent to or received from the layer above. Therefore, received MAC Control frames, ifInDiscards, and ifInUnknownProtos are counted by ifInOctets, but not ifInXcastPkts. Transmitted MAC Control frames are counted by ifOutOctets, but not ifOutXcastPkts. ifOutDiscards and ifOutErrors are counted by ifOutXcastPkts, but not ifOutOctets.
要记住的另一个区别是IF-MIB计数器和IEEE 802.3计数器之间的区别是，在IEEE 802.3文档中，帧计数器和八位字节计数器总是一起递增。AOCTETSTRANSMITETDOK统计由AFRAMESTRANSMITETDOK统计的帧中的八位字节数。aOctetsReceivedOK统计由aFramesReceivedOK统计的帧中的八位字节数。IF-MIB计数器的情况并非如此。IF-MIB八位字节计数器统计发送到该接口下面的层或从该接口下面的层接收到的八位字节数，而数据包计数器统计发送到上面的层或从上面的层接收到的数据包数。因此，接收到的MAC控制帧、IFindiscard和IFinKnownProtos由IFinoctes计数，而不是ifInXcastPkts计数。传输的MAC控制帧按ifOutOctets计数，但不按ifOutXcastPkts计数。ifOutDiscards和ifOutErrors由ifOutXcastPkts计数，但不由ifOutOctets计数。
The packet counters in the IF-MIB do not exactly match the definition of the frame counters in IEEE 802.3. aFramesTransmittedOK counts the number of frames successfully transmitted on the interface, whereas ifOutUcastPkts, ifOutMulticastPkts and ifOutBroadcastPkts count the
IF-MIB中的数据包计数器与IEEE 802.3中的帧计数器定义不完全匹配。aframestransmitedok统计接口上成功传输的帧数，而ifOutUcastPkts、ifOutMulticastPkts和ifOutBroadcastPkts统计接口上成功传输的帧数
number of transmit requests made from a higher layer, whether or not the transmit attempt was successful. This means that packets counted by ifOutErrors or ifOutDiscards are also counted by ifOutXcastPkts, but are not counted by aFramesTransmittedOK. This also means that, since MAC Control frames are generated by a sublayer internal to the interface layer rather than by a higher layer, they are not counted by ifOutXcastPkts, but are counted by aFramesTransmittedOK. Roughly:
从更高层发出的传输请求数，无论传输尝试是否成功。这意味着由ifOutErrors或ifOutDiscards计数的数据包也由ifOutXcastPkts计数，但不由aframestransmitedok计数。这也意味着，由于MAC控制帧是由接口层内部的子层而不是更高的层生成的，因此它们不由IFOUTxCastPKT计数，而是由aFramesTransmittedOK计数。大致：
aFramesTransmittedOK = ifOutUcastPkts + ifOutMulticastPkts +
ifOutBroadcastPkts + dot3OutPauseFrames -
(ifOutErrors + ifOutDiscards)
aFramesTransmittedOK = ifOutUcastPkts + ifOutMulticastPkts +
ifOutBroadcastPkts + dot3OutPauseFrames -
(ifOutErrors + ifOutDiscards)
Similarly, aFramesReceivedOK counts the number of frames received successfully by the interface, whether or not they are passed to a higher layer, whereas ifInUcastPkts, ifInMulticastPkts and ifInBroadcastPkts count only the number of packets passed to a higher layer. This means that packets counted by ifInDiscards or ifInUnknownProtos are also counted by aFramesReceivedOK, but are not counted by ifInXcastPkts. This also means that, since MAC Control frames are consumed by a sublayer internal to the interface layer and not passed to a higher layer, they are not counted by ifInXcastPkts, but are counted by aFramesReceivedOK. Roughly:
类似地，aFramesReceivedOK统计接口成功接收的帧数，无论它们是否传递到更高层，而ifInUcastPkts、ifInMulticastPkts和ifInBroadcastPkts仅统计传递到更高层的数据包数。这意味着由ifInDiscards或ifInUnknownProtos计数的数据包也由aFramesReceivedOK计数，但不由ifInXcastPkts计数。这也意味着，由于MAC控制帧由接口层内部的子层使用，并且没有传递到更高的层，因此它们不由IFinxCastPKT计数，而是由aFramesReceivedOK计数。大致：
aFramesReceivedOK = ifInUcastPkts + ifInMulticastPkts +
ifInBroadcastPkts + dot3InPauseFrames +
ifInDiscards + ifInUnknownProtos
aFramesReceivedOK = ifInUcastPkts + ifInMulticastPkts +
ifInBroadcastPkts + dot3InPauseFrames +
ifInDiscards + ifInUnknownProtos
This specification chooses to treat MAC control frames as being originated and consumed within the interface and not counted by the IF-MIB packet counters. MAC control frames are normally sent as multicast packets. In many network environments, MAC control frames can greatly outnumber multicast frames carrying actual data. If MAC control frames were included in the ifInMulticastPkts and ifOutMulticastPkts, the count of data-carrying multicast packets would tend to be drowned out by the count of MAC control frames, rendering those counters considerably less useful.
本规范选择将MAC控制帧视为在接口内发起和使用，而不由IF-MIB数据包计数器计数。MAC控制帧通常作为多播数据包发送。在许多网络环境中，MAC控制帧的数量会大大超过承载实际数据的多播帧。如果在IFinMulticastPKT和IFoutMulticastPKT中包括MAC控制帧，则承载多播数据包的数据计数往往会被MAC控制帧的计数淹没，从而使这些计数器的用处大大降低。
To better understand the issues surrounding the mapping of the IF-MIB packet and octet counters to an Ethernet interface, it is useful to refer to a Case Diagram [CASE] for the IF-MIB counters, with modifications to show the proper interpretation for the Ethernet interface layer.
为了更好地理解将IF-MIB数据包和八位字节计数器映射到以太网接口的问题，参考IF-MIB计数器的案例图[Case]非常有用，并进行修改以显示以太网接口层的正确解释。
layer above
--------------------------------------------------------------------
ifInUcastPkts+ ^ | ifOutUcastPkts+
ifInBroadcastPkts+ ----|---- ----|---- ifOutBroadcastPkts+
ifInMulticastPkts | | ifOutMulticastPkts
| |
dot3InPauseFrames <---| |<--- dot3OutPauseFrames
| |
ifInDiscards <---| |
| |
ifInUnknownProtos <---| |---> ifOutDiscards
| |
ifInOctets ----|---- ----|---- ifOutOctets
| |
ifInErrors <---| |---> ifOutErrors
| V
--------------------------------------------------------------------
layer below
layer above
--------------------------------------------------------------------
ifInUcastPkts+ ^ | ifOutUcastPkts+
ifInBroadcastPkts+ ----|---- ----|---- ifOutBroadcastPkts+
ifInMulticastPkts | | ifOutMulticastPkts
| |
dot3InPauseFrames <---| |<--- dot3OutPauseFrames
| |
ifInDiscards <---| |
| |
ifInUnknownProtos <---| |---> ifOutDiscards
| |
ifInOctets ----|---- ----|---- ifOutOctets
| |
ifInErrors <---| |---> ifOutErrors
| V
--------------------------------------------------------------------
layer below
The defined standard MTU for ethernet-like interfaces is 1500 octets. However, many implementations today support larger packet sizes than the IEEE 802.3 standard. The value of this object MUST reflect the actual MTU in use on the interface, whether it matches the standard MTU or not.
为类以太网接口定义的标准MTU为1500个八位字节。然而，今天的许多实现支持比IEEE 802.3标准更大的数据包大小。此对象的值必须反映接口上使用的实际MTU，无论其是否与标准MTU匹配。
This value should reflect the value seen by the MAC client interface. When a higher layer protocol, like IP, is running over Ethernet framing, this is the MTU that will be seen by that higher layer protocol. However, most ethernet-like interfaces today run multiple protocols that use a mix of different framing types. For example, an IEEE 802.2 LLC type 1 client protocol will see an MTU of 1497 octets on an interface using the IEEE standard maximum packet size, and a protocol running over SNAP will see an MTU of 1492 octets on an interface using the IEEE standard maximum packet size. However, since specification mandates using the MTU as seen at the MAC client interface, the value of ifMtu would be reported as 1500 octets in these cases.
此值应反映MAC客户端接口看到的值。当更高层协议（如IP）在以太网帧上运行时，这就是该更高层协议将看到的MTU。然而，目前大多数类似以太网的接口运行多种协议，这些协议混合使用不同的帧类型。例如，IEEE 802.2 LLC 1类客户端协议将在使用IEEE标准最大数据包大小的接口上看到1497个八位字节的MTU，而在SNAP上运行的协议将在使用IEEE标准最大数据包大小的接口上看到1492个八位字节的MTU。然而，由于规范要求使用MAC客户端接口上的MTU，因此在这些情况下，ifMtu的值将报告为1500个八位字节。
For ethernet-like interfaces operating at 1000 Megabits per second (Mb/s) or less, ifSpeed will represent the current operational speed of the interface in bits per second. For current interface types, this will be equal to 1,000,000 (1 million), 10,000,000 (10 million), 100,000,000 (100 million), or 1,000,000,000 (1 billion). ifHighSpeed will represent the current operational speed in millions of bits per
对于以每秒1000兆比特（Mb/s）或更低速度运行的类似以太网的接口，ifSpeed将以每秒比特数表示接口的当前运行速度。对于当前接口类型，这将等于1000000（100万）、10000000（1000万）、100000000（1亿）或100000000（10亿）。ifHighSpeed表示当前的运行速度，单位为百万位/秒
second. For current ethernet-like interfaces, this will be equal to 1, 10, 100, or 1,000. If the interface implements auto-negotiation, auto-negotiation is enabled for this interface, and the interface has not yet negotiated to an operational speed, these objects SHOULD reflect the maximum speed supported by the interface.
第二对于当前类似以太网的接口，这将等于1、10、100或1000。如果接口实现自动协商，则此接口已启用自动协商，且接口尚未协商到操作速度，则这些对象应反映接口支持的最大速度。
For ethernet-like interfaces operating at greater than 1000 Mb/s, ifHighSpeed will represent the current operational speed of the interface in millions of bits per second. Note that for WAN implementations, this will be the payload data rate over the WAN interface sublayer. For current implementations, this will be equal to 10,000 for LAN implementations of 10 Gb/s, and 9,294 for WAN implementations of the 10 Gb/s MAC over an OC-192 PHY. For these speeds, ifSpeed should report a maximum unsigned 32-bit value of 4,294,967,295 as specified in [RFC2863].
对于运行速度大于1000 Mb/s的类以太网接口，ifHighSpeed将表示接口的当前运行速度（以百万位/秒为单位）。请注意，对于WAN实现，这将是WAN接口子层上的有效负载数据速率。对于当前的实现，对于10 Gb/s的LAN实现，这将等于10000；对于OC-192 PHY上10 Gb/s MAC的WAN实现，这将等于9294。对于这些速度，ifSpeed应报告[RFC2863]中规定的最大无符号32位值4294967295。
Note that these object MUST NOT indicate a doubled value when operating in full-duplex mode. It MUST indicate the correct line speed regardless of the current duplex mode. The duplex mode of the interface may be determined by examining either the dot3StatsDuplexStatus object in this MIB module, or the ifMauType object in the 802.3 MAU MIB [RFC3636].
请注意，在全双工模式下操作时，这些对象不得指示加倍值。无论当前的双工模式如何，它都必须指示正确的线路速度。接口的双工模式可通过检查此MIB模块中的dot3StatsDuplexStatus对象或802.3 MAU MIB[RFC3636]中的ifMauType对象来确定。
This object contains the IEEE 802.3 address which is placed in the source-address field of any Ethernet, Starlan, or IEEE 802.3 frames that originate at this interface. Usually this will be kept in ROM on the interface hardware. Some systems may set this address via software.
此对象包含IEEE 802.3地址，该地址位于源自此接口的任何以太网、Starlan或IEEE 802.3帧的源地址字段中。通常这将保存在接口硬件上的ROM中。某些系统可能通过软件设置此地址。
In a system where there are several such addresses the designer has a tougher choice. The address chosen should be the one most likely to be of use to network management (e.g. the address placed in ARP responses for systems which are primarily IP systems).
在有多个这样的地址的系统中，设计者有一个更艰难的选择。选择的地址应该是最有可能用于网络管理的地址（例如，对于主要是IP系统的系统，ARP响应中的地址）。
If the designer truly can not chose, use of the factory-provided ROM address is suggested.
如果设计者确实无法选择，建议使用工厂提供的ROM地址。
If the address can not be determined, an octet string of zero length should be returned.
如果无法确定地址，则应返回长度为零的八位字节字符串。
The address is stored in binary in this object. The address is stored in "canonical" bit order, that is, the Group Bit is positioned as the low-order bit of the first octet. Thus, the first byte of a multicast address would have the bit 0x01 set.
地址以二进制形式存储在此对象中。地址以“规范”位顺序存储，即组位定位为第一个八位字节的低位。因此，多播地址的第一个字节将设置位0x01。
The following table provides specific implementation guidelines for applying the interface group objects to ethernet-like media.
下表提供了将接口组对象应用于类似以太网的介质的具体实现指南。
Object Guidelines
对象指南
ifIndex Each ethernet-like interface is represented by an ifEntry. The dot3StatsTable in this MIB module is indexed by dot3StatsIndex. The interface identified by a particular value of dot3StatsIndex is the same interface as identified by the same value of ifIndex.
ifIndex每个类似以太网的接口由ifEntry表示。此MIB模块中的dot3StatsTable由dot3StatsIndex索引。由dot3StatsIndex的特定值标识的接口与由ifIndex的相同值标识的接口相同。
ifDescr Refer to [RFC2863].
如果需要，请参阅[RFC2863]。
ifType Refer to section 3.2.4.
如果类型不同，请参考第3.2.4节。
ifMtu Refer to section 3.2.7.
ifMtu参考第3.2.7节。
ifSpeed Refer to section 3.2.8.
如果速度过快，请参考第3.2.8节。
ifPhysAddress Refer to section 3.2.9.
如果需要，请参考第3.2.9节。
ifAdminStatus Write access is not required. Support for 'testing' is not required.
不需要ifAdminStatus写访问权限。不需要支持“测试”。
ifOperStatus The operational state of the interface. Support for 'testing' is not required. The value 'dormant' has no meaning for an ethernet-like interface.
ifOperStatus接口的操作状态。不需要支持“测试”。“休眠”值对于类似以太网的接口没有意义。
ifLastChange Refer to [RFC2863].
如果需要更改，请参阅[RFC2863]。
ifInOctets The number of octets in valid MAC frames received on this interface, including the MAC header and FCS. This does include the number of octets in valid MAC Control frames received on this interface. See section 3.2.5.
ifInOctets在该接口上接收的有效MAC帧中的八位字节数，包括MAC报头和FCS。这确实包括在该接口上接收的有效MAC控制帧中的八位字节数。见第3.2.5节。
ifInUcastPkts Refer to [RFC2863]. Note that this does not include MAC Control frames, since MAC Control frames are consumed by the interface layer and are not passed to any higher layer protocol. See section 3.2.6.
如果需要，请参阅[RFC2863]。注意，这不包括MAC控制帧，因为MAC控制帧由接口层消耗，并且不传递给任何更高层协议。见第3.2.6节。
ifInDiscards Refer to [RFC2863].
如有指示，请参阅[RFC2863]。
ifInErrors The sum for this interface of dot3StatsAlignmentErrors, dot3StatsFCSErrors, dot3StatsFrameTooLongs, and dot3StatsInternalMacReceiveErrors.
IFINERROR此接口的dot3StatsAlignmentErrors、DOT3STATSFSCSSERRORS、DOT3STATSFRAMETOLONGS和dot3StatsInternalMacReceiveErrors之和。
ifInUnknownProtos Refer to [RFC2863].
如果不知道，请参考[RFC2863]。
ifOutOctets The number of octets transmitted in valid MAC frames on this interface, including the MAC header and FCS. This does include the number of octets in valid MAC Control frames transmitted on this interface. See section 3.2.5.
ifOutOctets：此接口上有效MAC帧中传输的八位字节数，包括MAC报头和FCS。这包括在该接口上传输的有效MAC控制帧中的八位字节数。见第3.2.5节。
ifOutUcastPkts Refer to [RFC2863]. Note that this does not include MAC Control frames, since MAC Control frames are generated by the interface layer, and are not passed from any higher layer protocol. See section 3.2.6.
如有疑问，请参阅[RFC2863]。注意，这不包括MAC控制帧，因为MAC控制帧由接口层生成，并且不从任何更高层协议传递。见第3.2.6节。
ifOutDiscards Refer to [RFC2863].
如果输出丢弃，请参阅[RFC2863]。
ifOutErrors The sum for this interface of: dot3StatsSQETestErrors, dot3StatsLateCollisions, dot3StatsExcessiveCollisions, dot3StatsInternalMacTransmitErrors and dot3StatsCarrierSenseErrors.
IoutErrors此接口的总和：Dot3StatsQetestErrors、dot3StatsLateCollisions、Dot3StatsAccessiveCollisions、Dot3StatsInternalActTransmitErrors和Dot3StatsCarriersensErrors。
ifName Locally-significant textual name for the interface (e.g. lan0).
ifName接口的本地有效文本名称（例如lan0）。
ifInMulticastPkts Refer to [RFC2863]. Note that this does not include MAC Control frames, since MAC Control frames are consumed by the interface layer and are not passed to any higher layer protocol. See section 3.2.6.
如需更多信息，请参阅[RFC2863]。注意，这不包括MAC控制帧，因为MAC控制帧由接口层消耗，并且不传递给任何更高层协议。见第3.2.6节。
ifInBroadcastPkts Refer to [RFC2863]. Note that this does not include MAC Control frames, since MAC Control frames are consumed by the interface layer, and are not passed to any higher layer protocol. See section 3.2.6.
IFINBROADCASTPKT参考[RFC2863]。注意，这不包括MAC控制帧，因为MAC控制帧由接口层使用，并且不传递给任何更高层协议。见第3.2.6节。
ifOutMulticastPkts Refer to [RFC2863]. Note that this does not include MAC Control frames, since MAC Control frames are generated by the interface layer, and are not passed from any higher layer protocol. See section 3.2.6.
IfoutMulticastPKT请参阅[RFC2863]。注意，这不包括MAC控制帧，因为MAC控制帧由接口层生成，并且不从任何更高层协议传递。见第3.2.6节。
ifOutBroadcastPkts Refer to [RFC2863]. Note that this does not include MAC Control frames, since MAC Control frames are generated by the interface layer, and are not passed from any higher layer protocol. See section 3.2.6.
如果需要，请参阅[RFC2863]。注意，这不包括MAC控制帧，因为MAC控制帧由接口层生成，并且不从任何更高层协议传递。见第3.2.6节。
ifHCInOctets 64-bit versions of counters. Required ifHCOutOctets for ethernet-like interfaces that are capable of operating at 20 Mb/s or faster, even if the interface is currently operating at less than 20 Mb/s.
ifHCInOctets计数器的64位版本。对于能够以20 Mb/s或更快速度运行的类以太网接口，即使该接口当前的运行速度低于20 Mb/s，也需要IFHCOUTPOCTETS。
ifHCInUcastPkts 64-bit versions of packet counters. ifHCInMulticastPkts Required for ethernet-like interfaces ifHCInBroadcastPkts that are capable of operating at ifHCOutUcastPkts 640 Mb/s or faster, even if the ifHCOutMulticastPkts interface is currently operating at ifHCOutBroadcastPkts less than 640 Mb/s.
ifHCInUcastPkts 64位版本的数据包计数器。类以太网接口ifHCInBroadcastPkts需要ifHCInMulticastPkts，能够以640 Mb/s或更快的速度运行，即使IFHCOUTPUTMulticastPKTS接口当前以低于640 Mb/s的速度运行。
ifLinkUpDownTrapEnable Refer to [RFC2863]. Default is 'enabled'
如果链接上下可删除，请参阅[RFC2863]。默认值为“已启用”
ifHighSpeed Refer to section 3.2.8.
如果高速，请参阅第3.2.8节。
ifPromiscuousMode Refer to [RFC2863].
如果是混杂模式，请参阅[RFC2863]。
ifConnectorPresent This will normally be 'true'. It will be 'false' in the case where this interface uses the WAN Interface Sublayer. See [RFC3637] for details.
如果ConnectorPresent，则通常为“true”。如果此接口使用WAN接口子层，则为“false”。详见[RFC3637]。
ifAlias Refer to [RFC2863].
如果需要，请参阅[RFC2863]。
ifCounterDiscontinuityTime Refer to [RFC2863]. Note that a discontinuity in the Interface MIB counters may also indicate a discontinuity in some or all of the counters in this MIB that are associated with that interface.
如果需要，请参阅[RFC2863]。请注意，接口MIB计数器中的不连续性也可能表示此MIB中与该接口关联的部分或所有计数器中的不连续性。
ifStackHigherLayer Refer to section 3.2.1. ifStackLowerLayer ifStackStatus
如果是StackHigherLayer，请参考第3.2.1节。ifStackLowerLayer ifStackStatus
ifRcvAddressAddress Refer to section 3.2.3. ifRcvAddressStatus ifRcvAddressType
ifRcvAddressAddress请参阅第3.2.3节。IFRCVAddress状态IFRCVAddress类型
Support for the mauModIfCompl3 compliance statement of the MAU-MIB [RFC3636] is REQUIRED for Ethernet-like interfaces. This MIB is needed in order to allow applications to determine the current MAU type in use by the interface, and to control autonegotiation and duplex mode for the interface. Implementing this MIB module without implementing the MAU-MIB would leave applications with no standard way to determine the media type in use, and no standard way to control the duplex mode of the interface.
类以太网接口需要支持MAU-MIB[RFC3636]的mauModIfCompl3合规性声明。需要此MIB以允许应用程序确定接口使用的当前MAU类型，并控制接口的自动协商和双工模式。在不实现MAU-MIB的情况下实现此MIB模块将使应用程序无法确定使用的介质类型，也无法控制接口的双工模式。
This document defines an object called dot3StatsEtherChipSet, which is used to identify the MAC hardware used to communicate on an interface. Previous versions of this document contained a number of OID assignments for some existing Ethernet chipsets. Maintaining that list as part of this document has proven to be problematic, so the OID assignments contained in previous versions of this document have now been moved to a separate document [RFC2666].
本文档定义了一个名为dot3StateSetherChipset的对象，用于标识用于在接口上通信的MAC硬件。本文档的早期版本包含一些现有以太网芯片组的OID分配。事实证明，将该列表作为本文档的一部分进行维护是有问题的，因此本文档以前版本中包含的OID分配现在已移至单独的文档[RFC2666]。
The dot3StatsEtherChipSet object has now been deprecated. Implementation feedback indicates that this object is much more useful in theory than in practice. The object's utility in debugging network problems in the field appears to be limited. In those cases where it may be useful, it is not sufficient, since it identifies only the MAC chip, and not the PHY, PMD, or driver. The administrative overhead involved in maintaining a central registry of chipset OIDs cannot be justified for an object whose usefulness is questionable at best.
Dot3StateSetherChipset对象现已被弃用。实现反馈表明，该对象在理论上比在实践中更有用。该对象在现场调试网络问题方面的效用似乎有限。在可能有用的情况下，这是不够的，因为它只识别MAC芯片，而不识别PHY、PMD或驱动程序。维护芯片组OID的中央注册表所涉及的管理开销对于一个用途最多也值得怀疑的对象来说是不合理的。
Implementations which continue to support this object for the purpose of backwards compatibility may continue to use the values defined in [RFC2666]. For chipsets not listed in [RFC2666], implementors that wish to support this object and return a valid OBJECT IDENTIFIER value may assign OBJECT IDENTIFIERS within that part of the registration tree delegated to individual enterprises.
为了向后兼容而继续支持该对象的实现可以继续使用[RFC2666]中定义的值。对于[RFC2666]中未列出的芯片组，希望支持此对象并返回有效对象标识符值的实现者可以在委托给单个企业的注册树的该部分内分配对象标识符。
IEEE 802.3 Managed Object Corresponding SNMP Object
IEEE 802.3管理对象对应的SNMP对象
oMacEntity
.aMACID dot3StatsIndex or
IF-MIB - ifIndex
.aFramesTransmittedOK IF-MIB - ifOutUCastPkts +
ifOutMulticastPkts +
ifOutBroadcastPkts*
.aSingleCollisionFrames dot3StatsSingleCollisionFrames
.aMultipleCollisionFrames dot3StatsMultipleCollisionFrames
.aFramesReceivedOK IF-MIB - ifInUcastPkts +
ifInMulticastPkts +
ifInBroadcastPkts*
.aFrameCheckSequenceErrors dot3StatsFCSErrors
.aAlignmentErrors dot3StatsAlignmentErrors
.aOctetsTransmittedOK IF-MIB - ifOutOctets*
.aFramesWithDeferredXmissions dot3StatsDeferredTransmissions
.aLateCollisions dot3StatsLateCollisions
.aFramesAbortedDueToXSColls dot3StatsExcessiveCollisions
.aFramesLostDueToIntMACXmitError dot3StatsInternalMacTransmitErrors
.aCarrierSenseErrors dot3StatsCarrierSenseErrors
.aOctetsReceivedOK IF-MIB - ifInOctets*
.aFramesLostDueToIntMACRcvError dot3StatsInternalMacReceiveErrors
.aPromiscuousStatus IF-MIB - ifPromiscuousMode
.aReadMulticastAddressList IF-MIB - ifRcvAddressTable
.aMulticastFramesXmittedOK IF-MIB - ifOutMulticastPkts*
.aBroadcastFramesXmittedOK IF-MIB - ifOutBroadcastPkts*
.aMulticastFramesReceivedOK IF-MIB - ifInMulticastPkts*
.aBroadcastFramesReceivedOK IF-MIB - ifInBroadcastPkts*
.aFrameTooLongErrors dot3StatsFrameTooLongs
.aReadWriteMACAddress IF-MIB - ifPhysAddress
.aCollisionFrames dot3CollFrequencies
.aDuplexStatus dot3StatsDuplexStatus
.aRateControlAbility dot3StatsRateControlAbility
.aRateControlStatus dot3StatsRateControlStatus
.acAddGroupAddress IF-MIB - ifRcvAddressTable
.acDeleteGroupAddress IF-MIB - ifRcvAddressTable
.acExecuteSelfTest dot3TestLoopBack
oMacEntity
.aMACID dot3StatsIndex or
IF-MIB - ifIndex
.aFramesTransmittedOK IF-MIB - ifOutUCastPkts +
ifOutMulticastPkts +
ifOutBroadcastPkts*
.aSingleCollisionFrames dot3StatsSingleCollisionFrames
.aMultipleCollisionFrames dot3StatsMultipleCollisionFrames
.aFramesReceivedOK IF-MIB - ifInUcastPkts +
ifInMulticastPkts +
ifInBroadcastPkts*
.aFrameCheckSequenceErrors dot3StatsFCSErrors
.aAlignmentErrors dot3StatsAlignmentErrors
.aOctetsTransmittedOK IF-MIB - ifOutOctets*
.aFramesWithDeferredXmissions dot3StatsDeferredTransmissions
.aLateCollisions dot3StatsLateCollisions
.aFramesAbortedDueToXSColls dot3StatsExcessiveCollisions
.aFramesLostDueToIntMACXmitError dot3StatsInternalMacTransmitErrors
.aCarrierSenseErrors dot3StatsCarrierSenseErrors
.aOctetsReceivedOK IF-MIB - ifInOctets*
.aFramesLostDueToIntMACRcvError dot3StatsInternalMacReceiveErrors
.aPromiscuousStatus IF-MIB - ifPromiscuousMode
.aReadMulticastAddressList IF-MIB - ifRcvAddressTable
.aMulticastFramesXmittedOK IF-MIB - ifOutMulticastPkts*
.aBroadcastFramesXmittedOK IF-MIB - ifOutBroadcastPkts*
.aMulticastFramesReceivedOK IF-MIB - ifInMulticastPkts*
.aBroadcastFramesReceivedOK IF-MIB - ifInBroadcastPkts*
.aFrameTooLongErrors dot3StatsFrameTooLongs
.aReadWriteMACAddress IF-MIB - ifPhysAddress
.aCollisionFrames dot3CollFrequencies
.aDuplexStatus dot3StatsDuplexStatus
.aRateControlAbility dot3StatsRateControlAbility
.aRateControlStatus dot3StatsRateControlStatus
.acAddGroupAddress IF-MIB - ifRcvAddressTable
.acDeleteGroupAddress IF-MIB - ifRcvAddressTable
.acExecuteSelfTest dot3TestLoopBack
oPHYEntity .aPHYID dot3StatsIndex or IF-MIB - ifIndex .aSQETestErrors dot3StatsSQETestErrors .aSymbolErrorDuringCarrier dot3StatsSymbolErrors
oPHYEntity.aPHYID dot3StatsIndex或IF-MIB-ifIndex.aSQETestErrors dot3StatsSQETestErrors.asymbolerrorringcarrier dot3statsssymbolerrors
oMACControlEntity .aMACControlID dot3StatsIndex or IF-MIB - ifIndex .aMACControlFunctionsSupported dot3ControlFunctionsSupported and dot3ControlFunctionsEnabled .aUnsupportedOpcodesReceived dot3ControlInUnknownOpcodes
oMACControlEntity.aMACControlID dot3StatsIndex或IF-MIB-ifIndex.AmacControlFunctions支持的Dot3ControlFunctions支持和Dot3ControlFunctions启用。AunSupportedOpCodes接收的dot3ControlInUnknownOpcodes
oPAUSEEntity .aPAUSEMACCtrlFramesTransmitted dot3OutPauseFrames .aPAUSEMACCtrlFramesReceived dot3InPauseFrames
oPAUSEEntity.aPAUSEMACCtrlFramesTransmitted Dot3OutpuseFrames.ApauseMacCtrlFramesReceivedDot3InpuseFrames
* Note that the octet counters in IF-MIB do not exactly match the definition of the octet counters in IEEE 802.3. See section 3.2.5 for details.
* 请注意，IF-MIB中的八位计数器与IEEE 802.3中八位计数器的定义不完全匹配。详见第3.2.5节。
Also note that the packet counters in the IF-MIB do not exactly match the definition of the frame counters in IEEE 802.3. See section 3.2.6 for details.
还要注意，IF-MIB中的数据包计数器与IEEE 802.3中的帧计数器定义不完全匹配。详见第3.2.6节。
The following IEEE 802.3 managed objects have been removed from this MIB module as a result of implementation feedback:
由于实施反馈，以下IEEE 802.3受管对象已从此MIB模块中删除：
oMacEntity .aFramesWithExcessiveDeferral .aInRangeLengthErrors .aOutOfRangeLengthField .aMACEnableStatus .aTransmitEnableStatus .aMulticastReceiveStatus .acInitializeMAC
oMacEntity.aFrameswithExcessedeferal.AinRange Lengthers.aAuto-FrangelLengthField.aMACEnableStatus.aTransmitEnableStatus.aMulticastReceiveStatus.aInitializeMac
Please see [RFC1369] for the detailed reasoning on why these objects were removed.
请参阅[RFC1369]了解移除这些对象的详细原因。
In addition, the following IEEE 802.3 managed objects have not been included in this MIB for the following reasons.
此外，由于以下原因，此MIB中未包含以下IEEE 802.3受管对象。
IEEE 802.3 Managed Object Disposition
IEEE 802.3受管对象配置
oMACEntity .aMACCapabilities Can be derived from MAU-MIB - ifMauTypeListBits
omaccentity.aMACCapabilities可以从MAU-MIB-ifMauTypeListBits派生
.aStretchRatio Implementation constant.
.aStretchRatio实现常数。
oPHYEntity .aPhyType Can be derived from MAU-MIB - ifMauType
隐晶质。隐晶质可以从MAU-MIB-ifMauType派生
.aPhyTypeList Can be derived from MAU-MIB - ifMauTypeListBits
.aPhyTypeList可以从MAU-MIB-ifMauTypeListBits派生
.aMIIDetect Not considered useful.
.aMIIDetect不被认为是有用的。
.aPhyAdminState Can already obtain interface state from IF-MIB - ifAdminStatus and MAU state from MAU-MIB - ifMauStatus. Providing an additional state for the PHY was not considered useful.
.aPhyAdminState已经可以从IF-MIB-ifAdminStatus获取接口状态，从MAU-MIB-ifMauStatus获取MAU状态。为PHY提供附加状态被认为是无用的。
.acPhyAdminControl Can already control interface state from IF-MIB - ifAdminStatus and MAU state from MAU-MIB - ifMauStatus. Providing separate admin control of the PHY was not considered useful.
.acPhyAdminControl已经可以从IF-MIB-ifAdminStatus控制接口状态，从MAU-MIB-ifMauStatus控制MAU状态。对PHY提供单独的管理控制被认为是无用的。
oMACControlEntity .aMACControlFramesTransmitted Can be determined by summing the OutFrames counters for the individual control functions
oMACControlEntity.aMACControlFramesTransmitted可以通过对各个控制函数的OutFrame计数器求和来确定
.aMACControlFramesReceived Can be determined by summing the InFrames counters for the individual control functions
.A接收到的AccontrolFrames可通过对各个控制功能的InFrames计数器求和来确定
oPAUSEEntity .aPAUSELinkDelayAllowance Not considered useful.
ApauseEntity.ApauseLinkDelayAllowment被认为是无用的。
EtherLike-MIB DEFINITIONS ::= BEGIN
EtherLike-MIB DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY, Integer32, Counter32, Counter64, mib-2, transmission FROM SNMPv2-SMI MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF TruthValue FROM SNMPv2-TC ifIndex, InterfaceIndex FROM IF-MIB;
从SNMPv2导入模块标识、对象类型、对象标识、整数32、计数器32、计数器64、mib-2、从SNMPv2导入传输SMI模块符合性、从SNMPv2导入对象组、从SNMPv2导入CONF TruthValue从SNMPv2 TC iIndex导入接口索引从IF-mib导入接口索引；
etherMIB MODULE-IDENTITY LAST-UPDATED "200309190000Z" -- September 19, 2003 ORGANIZATION "IETF Ethernet Interfaces and Hub MIB Working Group" CONTACT-INFO "WG E-mail: hubmib@ietf.org To subscribe: hubmib-request@ietf.org
etherMIB模块标识最后更新的“20030919000Z”-2003年9月19日组织“IETF以太网接口和集线器MIB工作组”联系信息工作组电子邮件：hubmib@ietf.org订阅：hubmib-request@ietf.org
Chair: Dan Romascanu Postal: Avaya Inc. Atidum Technology Park, Bldg. 3 Tel Aviv 61131 Israel Tel: +972 3 645 8414 E-mail: dromasca@avaya.com
主席：Dan Romascanu邮政：Avaya Inc.Atidum科技园特拉维夫3号楼61131以色列电话：+972 3 645 8414电子邮件：dromasca@avaya.com
Editor: John Flick Postal: Hewlett-Packard Company 8000 Foothills Blvd. M/S 5557 Roseville, CA 95747-5557 USA Tel: +1 916 785 4018 Fax: +1 916 785 1199 E-mail: johnf@rose.hp.com"
编辑：约翰·弗利克邮政：惠普公司8000山麓大道。M/S 5557加利福尼亚州罗斯维尔95747-5557美国电话：+1 916 785 4018传真：+1 916 785 1199电子邮件：johnf@rose.hp.com"
DESCRIPTION "The MIB module to describe generic objects for ethernet-like network interfaces.
DESCRIPTION“MIB模块，用于描述类似以太网的网络接口的通用对象。
The following reference is used throughout this MIB module:
在整个MIB模块中使用以下参考：
[IEEE 802.3 Std] refers to: IEEE Std 802.3, 2002 Edition: 'IEEE Standard
[IEEE 802.3标准]指：IEEE标准802.3，2002版：“IEEE标准
for Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 3: Carrier sense multiple access with collision detection (CSMA/CD) access method and physical layer specifications', as amended by IEEE Std 802.3ae-2002: 'Amendment: Media Access Control (MAC) Parameters, Physical Layer, and Management Parameters for 10 Gb/s Operation', August, 2002.
信息技术.系统间远程通信和信息交换.局域网和城域网.特殊要求.第3部分：带冲突检测的载波侦听多址（CSMA/CD）访问方法和物理层规范，由IEEE Std 802.3ae-2002修订：“修订：媒体访问控制（MAC）10 Gb/s运行的参数、物理层和管理参数，2002年8月。
Of particular interest is Clause 30, '10 Mb/s, 100 Mb/s, 1000 Mb/s, and 10 Gb/s Management'.
特别令人感兴趣的是第30条，“10 Mb/s、100 Mb/s、1000 Mb/s和10 Gb/s管理”。
Copyright (C) The Internet Society (2003). This version of this MIB module is part of RFC 3635; see the RFC itself for full legal notices."
版权所有（C）互联网协会（2003年）。此版本的MIB模块是RFC 3635的一部分；有关完整的法律通知，请参见RFC本身。”
REVISION "200309190000Z" -- September 19, 2003 DESCRIPTION "Updated to include support for 10 Gb/sec interfaces. This resulted in the following revisions:
修订版“20030919000Z”-2003年9月19日“说明”更新为包括对10 Gb/sec接口的支持。这导致了以下修订：
- Updated dot3StatsAlignmentErrors and dot3StatsSymbolErrors DESCRIPTIONs to reflect behaviour at 10 Gb/s - Added dot3StatsRateControlAbility and dot3RateControlStatus for management of the Rate Control function in 10 Gb/s WAN applications - Added 64-bit versions of all counters that are used on high-speed ethernet interfaces - Added object groups to contain the new objects - Deprecated etherStatsBaseGroup and split into etherStatsBaseGroup2 and etherStatsHalfDuplexGroup, so that interfaces which can only operate at full-duplex do not need to implement half-duplex-only statistics - Deprecated dot3Compliance and replaced it with dot3Compliance2, which includes the compliance information for the new object groups
- 更新了dot3StatsAlignmentErrors和dot3StatsSymbolErrors描述，以反映10 Gb/s的行为-添加了dot3StatsRateControlAbility和dot3RateControlStatus，用于管理10 Gb/s WAN应用程序中的速率控制功能-添加了高速以太网接口上使用的所有计数器的64位版本-添加了对象组要包含新对象-弃用的EtherstStatsBaseGroup并拆分为EtherstStatsBaseGroup2和EtherstStatsHalfDuplexGroup，以便只能在全双工模式下运行的接口不需要实现仅半双工统计-弃用的dot3Compliance并将其替换为dot3Compliance2，其中包括新对象组的符合性信息
In addition, the dot3Tests and dot3Errors object identities have been deprecated, since there is no longer a standard method for using them.
此外，dot3Tests和dot3Errors对象标识已被弃用，因为不再有使用它们的标准方法。
This version published as RFC 3635."
此版本发布为RFC 3635。”
REVISION "199908240400Z" -- August 24, 1999 DESCRIPTION "Updated to include support for 1000 Mb/sec interfaces and full-duplex interfaces. This version published as RFC 2665."
修订版“199908240400Z”-1999年8月24日描述“已更新，包括对1000 Mb/s接口和全双工接口的支持。此版本发布为RFC 2665。”
REVISION "199806032150Z" -- June 3, 1998 DESCRIPTION "Updated to include support for 100 Mb/sec interfaces. This version published as RFC 2358."
修订版“199806032150Z”-1998年6月3日描述“已更新，包括对100 Mb/秒接口的支持。此版本发布为RFC 2358。”
REVISION "199402030400Z" -- February 3, 1994
DESCRIPTION "Initial version, published as RFC 1650."
::= { mib-2 35 }
REVISION "199402030400Z" -- February 3, 1994
DESCRIPTION "Initial version, published as RFC 1650."
::= { mib-2 35 }
etherMIBObjects OBJECT IDENTIFIER ::= { etherMIB 1 }
etherMIBObjects OBJECT IDENTIFIER ::= { etherMIB 1 }
dot3 OBJECT IDENTIFIER ::= { transmission 7 }
dot3 OBJECT IDENTIFIER ::= { transmission 7 }
-- the Ethernet-like Statistics group
--类以太网统计组
dot3StatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3StatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "Statistics for a collection of ethernet-like
interfaces attached to a particular system.
There will be one row in this table for each
ethernet-like interface in the system."
::= { dot3 2 }
dot3StatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3StatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "Statistics for a collection of ethernet-like
interfaces attached to a particular system.
There will be one row in this table for each
ethernet-like interface in the system."
::= { dot3 2 }
dot3StatsEntry OBJECT-TYPE
SYNTAX Dot3StatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "Statistics for a particular interface to an
ethernet-like medium."
INDEX { dot3StatsIndex }
::= { dot3StatsTable 1 }
dot3StatsEntry OBJECT-TYPE
SYNTAX Dot3StatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "Statistics for a particular interface to an
ethernet-like medium."
INDEX { dot3StatsIndex }
::= { dot3StatsTable 1 }
Dot3StatsEntry ::=
SEQUENCE {
Dot3StatsEntry ::=
SEQUENCE {
dot3StatsIndex InterfaceIndex, dot3StatsAlignmentErrors Counter32, dot3StatsFCSErrors Counter32, dot3StatsSingleCollisionFrames Counter32, dot3StatsMultipleCollisionFrames Counter32, dot3StatsSQETestErrors Counter32, dot3StatsDeferredTransmissions Counter32, dot3StatsLateCollisions Counter32, dot3StatsExcessiveCollisions Counter32, dot3StatsInternalMacTransmitErrors Counter32, dot3StatsCarrierSenseErrors Counter32, dot3StatsFrameTooLongs Counter32, dot3StatsInternalMacReceiveErrors Counter32, dot3StatsEtherChipSet OBJECT IDENTIFIER, dot3StatsSymbolErrors Counter32, dot3StatsDuplexStatus INTEGER, dot3StatsRateControlAbility TruthValue, dot3StatsRateControlStatus INTEGER }
dot3StatsIndex接口索引、dot3StatsAlignmentErrors计数器32、Dot3StatsSerrors计数器32、dot3StatsSingleCollisionFrames计数器32、dot3StatsMultipleCollisionFrames计数器32、Dot3StatsQetesterrors计数器32、Dot3StatsDerredTransmissions计数器32、Dot3StatsSlateCollisions计数器32、Dot3StatsAccessiveCollisions计数器32、，DOT3STATSINTERNALMACTRANSMITECERRORS计数器32、DOT3STATSARIERSENSEERRORS计数器32、DOT3STATSFRAMETOLONGS计数器32、dot3StatsInternalMacReceiveErrors计数器32、dot3StatsSymbolErrors计数器32、DOT3STATSADUPLEXSTATUS INTEGER、DOT3STATSRATESRATERCONTROLATABILITABILITY TRUTH值、DOT3STATSRATECONTROLATIONSTATUS INTEGER}
dot3StatsIndex OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS read-only -- read-only since originally an
-- SMIv1 index
STATUS current
DESCRIPTION "An index value that uniquely identifies an
interface to an ethernet-like medium. The
interface identified by a particular value of
this index is the same interface as identified
by the same value of ifIndex."
REFERENCE "RFC 2863, ifIndex"
::= { dot3StatsEntry 1 }
dot3StatsIndex OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS read-only -- read-only since originally an
-- SMIv1 index
STATUS current
DESCRIPTION "An index value that uniquely identifies an
interface to an ethernet-like medium. The
interface identified by a particular value of
this index is the same interface as identified
by the same value of ifIndex."
REFERENCE "RFC 2863, ifIndex"
::= { dot3StatsEntry 1 }
dot3StatsAlignmentErrors OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "A count of frames received on a particular interface that are not an integral number of octets in length and do not pass the FCS check.
dot3StatsAlignmentErrors对象类型语法计数器32 MAX-ACCESS只读状态当前描述“特定接口上接收的帧计数，其长度不是八位字节的整数，且未通过FCS检查。
The count represented by an instance of this object is incremented when the alignmentError status is returned by the MAC service to the LLC (or other MAC user). Received frames for which multiple error conditions pertain are, according to the conventions of IEEE 802.3 Layer Management, counted exclusively according
当MAC服务将alignmentError状态返回给LLC（或其他MAC用户）时，此对象实例表示的计数将增加。根据IEEE 802.3层管理的约定，与多个错误条件相关的接收帧根据
to the error status presented to the LLC.
提交给LLC的错误状态。
This counter does not increment for group encoding schemes greater than 4 bits per group.
对于大于每组4位的组编码方案，此计数器的增量不大于4位。
For interfaces operating at 10 Gb/s, this counter can roll over in less than 5 minutes if it is incrementing at its maximum rate. Since that amount of time could be less than a management station's poll cycle time, in order to avoid a loss of information, a management station is advised to poll the dot3HCStatsAlignmentErrors object for 10 Gb/s or faster interfaces.
对于以10 Gb/s速度运行的接口，如果计数器以最大速率递增，则该计数器可以在不到5分钟内翻转。由于该时间量可能小于管理站的轮询周期时间，为了避免信息丢失，建议管理站轮询Dot3HCStatSaligmentErrors对象以获得10 Gb/s或更快的接口。
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.7,
aAlignmentErrors"
::= { dot3StatsEntry 2 }
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.7,
aAlignmentErrors"
::= { dot3StatsEntry 2 }
dot3StatsFCSErrors OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "A count of frames received on a particular interface that are an integral number of octets in length but do not pass the FCS check. This count does not include frames received with frame-too-long or frame-too-short error.
dot3StatsFCSErrors对象类型语法计数器32 MAX-ACCESS只读状态当前描述“在特定接口上接收的帧计数，其长度为八位字节的整数，但未通过FCS检查。此计数不包括接收到的帧过长或帧过短错误。
The count represented by an instance of this object is incremented when the frameCheckError status is returned by the MAC service to the LLC (or other MAC user). Received frames for which multiple error conditions pertain are, according to the conventions of IEEE 802.3 Layer Management, counted exclusively according to the error status presented to the LLC.
当MAC服务向LLC（或其他MAC用户）返回frameCheckError状态时，此对象实例表示的计数将增加。根据IEEE 802.3层管理的约定，与多个错误条件相关的接收帧仅根据呈现给LLC的错误状态进行计数。
Note: Coding errors detected by the physical layer for speeds above 10 Mb/s will cause the frame to fail the FCS check.
注：当速度超过10 Mb/s时，物理层检测到的编码错误将导致帧无法通过FCS检查。
For interfaces operating at 10 Gb/s, this counter can roll over in less than 5 minutes if
对于以10 Gb/s速度运行的接口，如果
it is incrementing at its maximum rate. Since that amount of time could be less than a management station's poll cycle time, in order to avoid a loss of information, a management station is advised to poll the dot3HCStatsFCSErrors object for 10 Gb/s or faster interfaces.
它正以最大速率递增。由于该时间量可能小于管理站的轮询周期时间，为了避免信息丢失，建议管理站轮询Dot3hcsAtsCasErrors对象以获得10 Gb/s或更快的接口。
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.6,
aFrameCheckSequenceErrors."
::= { dot3StatsEntry 3 }
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.6,
aFrameCheckSequenceErrors."
::= { dot3StatsEntry 3 }
dot3StatsSingleCollisionFrames OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "A count of frames that are involved in a single collision, and are subsequently transmitted successfully.
dot3StatsSingleCollisionFrames对象类型语法计数器32 MAX-ACCESS只读状态当前描述“一次冲突中涉及并随后成功传输的帧计数。
A frame that is counted by an instance of this object is also counted by the corresponding instance of either the ifOutUcastPkts, ifOutMulticastPkts, or ifOutBroadcastPkts, and is not counted by the corresponding instance of the dot3StatsMultipleCollisionFrames object.
由此对象的实例计数的帧也由ifOutUcastPkts、IFOUTPMulticastPKTS或IFOUTProadcastPKTS的相应实例计数，而不由dot3StatsMultipleCollisionFrames对象的相应实例计数。
This counter does not increment when the interface is operating in full-duplex mode.
当接口在全双工模式下运行时，此计数器不递增。
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.3,
aSingleCollisionFrames."
::= { dot3StatsEntry 4 }
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.3,
aSingleCollisionFrames."
::= { dot3StatsEntry 4 }
dot3StatsMultipleCollisionFrames OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "A count of frames that are involved in more
dot3StatsMultipleCollisionFrames对象类型语法计数器32 MAX-ACCESS只读状态当前描述“涉及更多
than one collision and are subsequently transmitted successfully.
一次以上的碰撞，并随后成功传输。
A frame that is counted by an instance of this object is also counted by the corresponding instance of either the ifOutUcastPkts, ifOutMulticastPkts, or ifOutBroadcastPkts, and is not counted by the corresponding instance of the dot3StatsSingleCollisionFrames object.
由此对象的实例计数的帧也由ifOutUcastPkts、IFOUTPMulticastPKTS或IFOUTProadcastPKTS的相应实例计数，而不由dot3StatsSingleCollisionFrames对象的相应实例计数。
This counter does not increment when the interface is operating in full-duplex mode.
当接口在全双工模式下运行时，此计数器不递增。
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.4,
aMultipleCollisionFrames."
::= { dot3StatsEntry 5 }
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.4,
aMultipleCollisionFrames."
::= { dot3StatsEntry 5 }
dot3StatsSQETestErrors OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "A count of times that the SQE TEST ERROR is received on a particular interface. The SQE TEST ERROR is set in accordance with the rules for verification of the SQE detection mechanism in the PLS Carrier Sense Function as described in IEEE Std. 802.3, 2000 Edition, section 7.2.4.6.
DOT3StatssQETESERRORS对象类型语法计数器32 MAX-ACCESS只读状态当前说明“在特定接口上收到SQE测试错误的次数。根据IEEE标准802.3，2000版，第7.2.4.6节中描述的PLS载波检测功能中SQE检测机制的验证规则设置SQE测试错误。
This counter does not increment on interfaces operating at speeds greater than 10 Mb/s, or on interfaces operating in full-duplex mode.
在速度大于10 Mb/s的接口上，或在全双工模式下的接口上，此计数器不递增。
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 7.2.4.6, also 30.3.2.1.4,
aSQETestErrors."
::= { dot3StatsEntry 6 }
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 7.2.4.6, also 30.3.2.1.4,
aSQETestErrors."
::= { dot3StatsEntry 6 }
dot3StatsDeferredTransmissions OBJECT-TYPE SYNTAX Counter32
DOT3StatsFerredTransmissions对象类型语法计数器32
MAX-ACCESS read-only STATUS current DESCRIPTION "A count of frames for which the first transmission attempt on a particular interface is delayed because the medium is busy.
MAX-ACCESS只读状态当前描述“由于介质忙，在特定接口上的第一次传输尝试延迟的帧计数。
The count represented by an instance of this object does not include frames involved in collisions.
此对象实例表示的计数不包括碰撞中涉及的帧。
This counter does not increment when the interface is operating in full-duplex mode.
当接口在全双工模式下运行时，此计数器不递增。
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.9,
aFramesWithDeferredXmissions."
::= { dot3StatsEntry 7 }
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.9,
aFramesWithDeferredXmissions."
::= { dot3StatsEntry 7 }
dot3StatsLateCollisions OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of times that a collision is detected on a particular interface later than one slotTime into the transmission of a packet.
dot3StatsLateCollisions对象类型语法计数器32 MAX-ACCESS只读状态当前描述“在数据包传输的一个时隙之后，在特定接口上检测到冲突的次数。
A (late) collision included in a count represented by an instance of this object is also considered as a (generic) collision for purposes of other collision-related statistics.
包含在此对象实例表示的计数中的（延迟）冲突也被视为（通用）冲突，以用于其他与冲突相关的统计。
This counter does not increment when the interface is operating in full-duplex mode.
当接口在全双工模式下运行时，此计数器不递增。
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.10,
aLateCollisions."
::= { dot3StatsEntry 8 }
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.10,
aLateCollisions."
::= { dot3StatsEntry 8 }
dot3StatsExcessiveCollisions OBJECT-TYPE SYNTAX Counter32
DOT3StatsAccessiveCollisions对象类型语法计数器32
MAX-ACCESS read-only STATUS current DESCRIPTION "A count of frames for which transmission on a particular interface fails due to excessive collisions.
MAX-ACCESS只读状态当前描述“由于过度冲突，特定接口上传输失败的帧计数。
This counter does not increment when the interface is operating in full-duplex mode.
当接口在全双工模式下运行时，此计数器不递增。
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.11,
aFramesAbortedDueToXSColls."
::= { dot3StatsEntry 9 }
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.11,
aFramesAbortedDueToXSColls."
::= { dot3StatsEntry 9 }
dot3StatsInternalMacTransmitErrors OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "A count of frames for which transmission on a particular interface fails due to an internal MAC sublayer transmit error. A frame is only counted by an instance of this object if it is not counted by the corresponding instance of either the dot3StatsLateCollisions object, the dot3StatsExcessiveCollisions object, or the dot3StatsCarrierSenseErrors object.
DOT3STATSINTERNALMactTransmitErrors对象类型语法计数器32 MAX-ACCESS只读状态当前说明“由于内部MAC子层传输错误，在特定接口上传输失败的帧计数。如果帧未由dot3StatsLateCollisions对象、Dot3StatsAccessiveCollisions对象或dot3StatsCarrierSenseErrors对象的相应实例计数，则仅由该对象的实例计数。
The precise meaning of the count represented by an instance of this object is implementation-specific. In particular, an instance of this object may represent a count of transmission errors on a particular interface that are not otherwise counted.
此对象的实例表示的计数的确切含义是特定于实现的。特别地，该对象的实例可以表示特定接口上的传输错误的计数，否则这些错误不会被计数。
For interfaces operating at 10 Gb/s, this counter can roll over in less than 5 minutes if it is incrementing at its maximum rate. Since that amount of time could be less than a management station's poll cycle time, in order to avoid a loss of information, a management station is advised to poll the dot3HCStatsInternalMacTransmitErrors object for 10 Gb/s or faster interfaces.
对于以10 Gb/s速度运行的接口，如果计数器以最大速率递增，则该计数器可以在不到5分钟内翻转。由于该时间量可能小于管理站的轮询周期时间，为了避免信息丢失，建议管理站轮询Dot3HCStatsinternalActTransmitErrors对象以获得10 Gb/s或更快的接口。
Discontinuities in the value of this counter can
此计数器值的不连续性可能会导致
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.12,
aFramesLostDueToIntMACXmitError."
::= { dot3StatsEntry 10 }
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.12,
aFramesLostDueToIntMACXmitError."
::= { dot3StatsEntry 10 }
dot3StatsCarrierSenseErrors OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of times that the carrier sense condition was lost or never asserted when attempting to transmit a frame on a particular interface.
dot3StatsCarrierSenseErrors对象类型语法计数器32 MAX-ACCESS只读状态当前描述“尝试在特定接口上传输帧时，载波检测条件丢失或从未断言的次数。
The count represented by an instance of this object is incremented at most once per transmission attempt, even if the carrier sense condition fluctuates during a transmission attempt.
由该对象的实例表示的计数在每次传输尝试中最多增加一次，即使载波检测条件在传输尝试期间波动。
This counter does not increment when the interface is operating in full-duplex mode.
当接口在全双工模式下运行时，此计数器不递增。
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.13,
aCarrierSenseErrors."
::= { dot3StatsEntry 11 }
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.13,
aCarrierSenseErrors."
::= { dot3StatsEntry 11 }
-- { dot3StatsEntry 12 } is not assigned
--未分配{dot3StatsEntry 12}
dot3StatsFrameTooLongs OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "A count of frames received on a particular interface that exceed the maximum permitted frame size.
dot3StatsFrameTooLongs对象类型语法计数器32 MAX-ACCESS只读状态当前描述“在特定接口上接收到的超过最大允许帧大小的帧计数。
The count represented by an instance of this object is incremented when the frameTooLong status is returned by the MAC service to the LLC (or other MAC user). Received frames for which multiple error conditions pertain are,
当MAC服务将FrameToolLong状态返回给LLC（或其他MAC用户）时，此对象实例表示的计数将增加。与多个错误条件相关的接收帧包括：，
according to the conventions of IEEE 802.3 Layer Management, counted exclusively according to the error status presented to the LLC.
根据IEEE 802.3层管理的约定，仅根据提交给LLC的错误状态进行计数。
For interfaces operating at 10 Gb/s, this counter can roll over in less than 80 minutes if it is incrementing at its maximum rate. Since that amount of time could be less than a management station's poll cycle time, in order to avoid a loss of information, a management station is advised to poll the dot3HCStatsFrameTooLongs object for 10 Gb/s or faster interfaces.
对于以10 Gb/s速度运行的接口，如果计数器以最大速率递增，则该计数器可以在不到80分钟内翻转。由于该时间量可能小于管理站的轮询周期时间，为了避免信息丢失，建议管理站轮询dot3HCStatsFrameTooLongs对象以获得10 Gb/s或更快的接口。
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.25,
aFrameTooLongErrors."
::= { dot3StatsEntry 13 }
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.25,
aFrameTooLongErrors."
::= { dot3StatsEntry 13 }
-- { dot3StatsEntry 14 } is not assigned
--未分配{dot3StatsEntry 14}
-- { dot3StatsEntry 15 } is not assigned
--未分配{dot3StatsEntry 15}
dot3StatsInternalMacReceiveErrors OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "A count of frames for which reception on a particular interface fails due to an internal MAC sublayer receive error. A frame is only counted by an instance of this object if it is not counted by the corresponding instance of either the dot3StatsFrameTooLongs object, the dot3StatsAlignmentErrors object, or the dot3StatsFCSErrors object.
dot3StatsInternalMacReceiveErrors对象类型语法计数器32 MAX-ACCESS只读状态当前说明“由于内部MAC子层接收错误，在特定接口上接收失败的帧计数。如果帧未由dot3StatsFrameTooLongs对象、dot3StatsAlignmentErrors对象或Dot3StatsSecurErrors对象的相应实例计数，则仅由该对象的实例计数。
The precise meaning of the count represented by an instance of this object is implementation-specific. In particular, an instance of this object may represent a count of receive errors on a particular interface that are not otherwise counted.
此对象的实例表示的计数的确切含义是特定于实现的。特别地，该对象的实例可以表示特定接口上未被计数的接收错误的计数。
For interfaces operating at 10 Gb/s, this counter can roll over in less than 5 minutes if
对于以10 Gb/s速度运行的接口，如果
it is incrementing at its maximum rate. Since that amount of time could be less than a management station's poll cycle time, in order to avoid a loss of information, a management station is advised to poll the dot3HCStatsInternalMacReceiveErrors object for 10 Gb/s or faster interfaces.
它正以最大速率递增。由于该时间量可能小于管理站的轮询周期时间，为了避免信息丢失，建议管理站轮询dot3HCStatsInternalMacReceiveErrors对象以获得10 Gb/s或更快的接口。
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.15,
aFramesLostDueToIntMACRcvError."
::= { dot3StatsEntry 16 }
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.15,
aFramesLostDueToIntMACRcvError."
::= { dot3StatsEntry 16 }
dot3StatsEtherChipSet OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION "******** THIS OBJECT IS DEPRECATED ********
dot3StatsEtherChipSet OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION "******** THIS OBJECT IS DEPRECATED ********
This object contains an OBJECT IDENTIFIER which identifies the chipset used to realize the interface. Ethernet-like interfaces are typically built out of several different chips. The MIB implementor is presented with a decision of which chip to identify via this object. The implementor should identify the chip which is usually called the Medium Access Control chip. If no such chip is easily identifiable, the implementor should identify the chip which actually gathers the transmit and receive statistics and error indications. This would allow a manager station to correlate the statistics and the chip generating them, giving it the ability to take into account any known anomalies in the chip.
此对象包含一个对象标识符，用于标识用于实现接口的芯片组。类似以太网的接口通常由几个不同的芯片构成。MIB实现者将通过该对象决定识别哪个芯片。实施者应识别通常称为介质访问控制芯片的芯片。如果此类芯片不易识别，则实施者应识别实际收集发送和接收统计数据和错误指示的芯片。这将允许管理站将统计数据与生成它们的芯片关联起来，使其能够考虑芯片中的任何已知异常。
This object has been deprecated. Implementation feedback indicates that it is of limited use for debugging network problems in the field, and the administrative overhead involved in maintaining a registry of chipset OIDs is not justified."
此对象已被弃用。实施反馈表明，它在现场调试网络问题方面的用途有限，维护芯片组OID注册表所涉及的管理开销是不合理的。”
::= { dot3StatsEntry 17 }
::= { dot3StatsEntry 17 }
dot3StatsSymbolErrors OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "For an interface operating at 100 Mb/s, the number of times there was an invalid data symbol when a valid carrier was present.
dot3StatsSymbolErrors对象类型语法计数器32 MAX-ACCESS只读状态当前说明“对于以100 Mb/s速度运行的接口，存在有效载波时存在无效数据符号的次数。
For an interface operating in half-duplex mode at 1000 Mb/s, the number of times the receiving media is non-idle (a carrier event) for a period of time equal to or greater than slotTime, and during which there was at least one occurrence of an event that causes the PHY to indicate 'Data reception error' or 'carrier extend error' on the GMII.
对于以1000 Mb/s的速度在半双工模式下运行的接口，接收媒体在等于或大于时隙时间的时间段内处于非空闲状态（载波事件）的次数，并且在此期间至少发生了一次导致PHY在GMII上指示“数据接收错误”或“载波扩展错误”的事件。
For an interface operating in full-duplex mode at 1000 Mb/s, the number of times the receiving media is non-idle (a carrier event) for a period of time equal to or greater than minFrameSize, and during which there was at least one occurrence of an event that causes the PHY to indicate 'Data reception error' on the GMII.
对于以1000 Mb/s全双工模式运行的接口，接收媒体在等于或大于minFrameSize的时间段内非空闲（载波事件）的次数，并且在此期间至少发生一次导致PHY在GMII上指示“数据接收错误”的事件。
For an interface operating at 10 Gb/s, the number of times the receiving media is non-idle (a carrier event) for a period of time equal to or greater than minFrameSize, and during which there was at least one occurrence of an event that causes the PHY to indicate 'Receive Error' on the XGMII.
对于以10 Gb/s速度运行的接口，接收媒体在等于或大于minFrameSize的时间段内处于非空闲状态（载波事件）的次数，在此期间至少发生一次导致PHY在XGMII上指示“接收错误”的事件。
The count represented by an instance of this object is incremented at most once per carrier event, even if multiple symbol errors occur during the carrier event. This count does not increment if a collision is present.
此对象实例表示的计数在每个载波事件中最多增加一次，即使在载波事件期间发生多个符号错误。如果存在碰撞，此计数不会增加。
This counter does not increment when the interface is operating at 10 Mb/s.
当接口以10 Mb/s的速度运行时，此计数器不会递增。
For interfaces operating at 10 Gb/s, this counter can roll over in less than 5 minutes if it is incrementing at its maximum rate. Since that amount of time could be less than a
对于以10 Gb/s速度运行的接口，如果计数器以最大速率递增，则该计数器可以在不到5分钟内翻转。因为这段时间可能不到一分钟
management station's poll cycle time, in order to avoid a loss of information, a management station is advised to poll the dot3HCStatsSymbolErrors object for 10 Gb/s or faster interfaces.
管理站的轮询周期时间，为避免信息丢失，建议管理站轮询Dot3hcStatssSymbolErrors对象以获得10 Gb/s或更快的接口。
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.2.1.5,
aSymbolErrorDuringCarrier."
::= { dot3StatsEntry 18 }
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.2.1.5,
aSymbolErrorDuringCarrier."
::= { dot3StatsEntry 18 }
dot3StatsDuplexStatus OBJECT-TYPE
SYNTAX INTEGER {
unknown(1),
halfDuplex(2),
fullDuplex(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The current mode of operation of the MAC
entity. 'unknown' indicates that the current
duplex mode could not be determined.
dot3StatsDuplexStatus OBJECT-TYPE
SYNTAX INTEGER {
unknown(1),
halfDuplex(2),
fullDuplex(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The current mode of operation of the MAC
entity. 'unknown' indicates that the current
duplex mode could not be determined.
Management control of the duplex mode is accomplished through the MAU MIB. When an interface does not support autonegotiation, or when autonegotiation is not enabled, the duplex mode is controlled using ifMauDefaultType. When autonegotiation is supported and enabled, duplex mode is controlled using ifMauAutoNegAdvertisedBits. In either case, the currently operating duplex mode is reflected both in this object and in ifMauType.
双工模式的管理控制通过MAU MIB完成。当接口不支持自动协商或未启用自动协商时，双工模式使用ifmaudaulttype控制。当支持并启用自动协商时，使用ifMauAutoNegAdvertisedBits控制双工模式。在任何一种情况下，当前运行的双工模式都会反映在此对象和ifMauType中。
Note that this object provides redundant
information with ifMauType. Normally, redundant
objects are discouraged. However, in this
instance, it allows a management application to
determine the duplex status of an interface
without having to know every possible value of
ifMauType. This was felt to be sufficiently
valuable to justify the redundancy."
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.32,
aDuplexStatus."
::= { dot3StatsEntry 19 }
Note that this object provides redundant
information with ifMauType. Normally, redundant
objects are discouraged. However, in this
instance, it allows a management application to
determine the duplex status of an interface
without having to know every possible value of
ifMauType. This was felt to be sufficiently
valuable to justify the redundancy."
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.32,
aDuplexStatus."
::= { dot3StatsEntry 19 }
dot3StatsRateControlAbility OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION "'true' for interfaces operating at speeds above
1000 Mb/s that support Rate Control through
lowering the average data rate of the MAC
sublayer, with frame granularity, and 'false'
otherwise."
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.33,
aRateControlAbility."
::= { dot3StatsEntry 20 }
dot3StatsRateControlAbility OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION "'true' for interfaces operating at speeds above
1000 Mb/s that support Rate Control through
lowering the average data rate of the MAC
sublayer, with frame granularity, and 'false'
otherwise."
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.33,
aRateControlAbility."
::= { dot3StatsEntry 20 }
dot3StatsRateControlStatus OBJECT-TYPE
SYNTAX INTEGER {
rateControlOff(1),
rateControlOn(2),
unknown(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The current Rate Control mode of operation of
the MAC sublayer of this interface."
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.34,
aRateControlStatus."
::= { dot3StatsEntry 21 }
dot3StatsRateControlStatus OBJECT-TYPE
SYNTAX INTEGER {
rateControlOff(1),
rateControlOn(2),
unknown(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The current Rate Control mode of operation of
the MAC sublayer of this interface."
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.34,
aRateControlStatus."
::= { dot3StatsEntry 21 }
-- the Ethernet-like Collision Statistics group
--类以太网冲突统计组
-- Implementation of this group is optional; it is appropriate
-- for all systems which have the necessary metering
-- Implementation of this group is optional; it is appropriate
-- for all systems which have the necessary metering
dot3CollTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3CollEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "A collection of collision histograms for a
particular set of interfaces."
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.30,
aCollisionFrames."
::= { dot3 5 }
dot3CollTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3CollEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "A collection of collision histograms for a
particular set of interfaces."
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.30,
aCollisionFrames."
::= { dot3 5 }
dot3CollEntry OBJECT-TYPE SYNTAX Dot3CollEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A cell in the histogram of per-frame collisions for a particular interface. An
dot3CollEntry对象类型语法dot3CollEntry MAX-ACCESS不可访问状态当前描述“特定接口的每帧冲突直方图中的单元格。一个
instance of this object represents the
frequency of individual MAC frames for which
the transmission (successful or otherwise) on a
particular interface is accompanied by a
particular number of media collisions."
INDEX { ifIndex, dot3CollCount }
::= { dot3CollTable 1 }
instance of this object represents the
frequency of individual MAC frames for which
the transmission (successful or otherwise) on a
particular interface is accompanied by a
particular number of media collisions."
INDEX { ifIndex, dot3CollCount }
::= { dot3CollTable 1 }
Dot3CollEntry ::=
SEQUENCE {
dot3CollCount Integer32,
dot3CollFrequencies Counter32
}
Dot3CollEntry ::=
SEQUENCE {
dot3CollCount Integer32,
dot3CollFrequencies Counter32
}
-- { dot3CollEntry 1 } is no longer in use
--{dot3CollEntry 1}不再使用
dot3CollCount OBJECT-TYPE
SYNTAX Integer32 (1..16)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "The number of per-frame media collisions for
which a particular collision histogram cell
represents the frequency on a particular
interface."
::= { dot3CollEntry 2 }
dot3CollCount OBJECT-TYPE
SYNTAX Integer32 (1..16)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "The number of per-frame media collisions for
which a particular collision histogram cell
represents the frequency on a particular
interface."
::= { dot3CollEntry 2 }
dot3CollFrequencies OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "A count of individual MAC frames for which the transmission (successful or otherwise) on a particular interface occurs after the frame has experienced exactly the number of collisions in the associated dot3CollCount object.
dot3CollFrequencies对象类型语法计数器32 MAX-ACCESS只读状态当前描述“在特定接口上传输（成功或不成功）的单个MAC帧的计数，该帧在关联的dot3CollCount对象中经历的冲突数正好相等。
For example, a frame which is transmitted on interface 77 after experiencing exactly 4 collisions would be indicated by incrementing only dot3CollFrequencies.77.4. No other instance of dot3CollFrequencies would be incremented in this example.
例如，在经历4次碰撞后在接口77上传输的帧将仅通过增加dot3CollFrequencies.77.4来表示。在此示例中，不会增加dot3CollFrequencies的其他实例。
This counter does not increment when the interface is operating in full-duplex mode.
当接口在全双工模式下运行时，此计数器不递增。
Discontinuities in the value of this counter can
此计数器值的不连续性可能会导致
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
::= { dot3CollEntry 3 }
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
::= { dot3CollEntry 3 }
dot3ControlTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3ControlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "A table of descriptive and status information
about the MAC Control sublayer on the
ethernet-like interfaces attached to a
particular system. There will be one row in
this table for each ethernet-like interface in
the system which implements the MAC Control
sublayer. If some, but not all, of the
ethernet-like interfaces in the system implement
the MAC Control sublayer, there will be fewer
rows in this table than in the dot3StatsTable."
::= { dot3 9 }
dot3ControlTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3ControlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "A table of descriptive and status information
about the MAC Control sublayer on the
ethernet-like interfaces attached to a
particular system. There will be one row in
this table for each ethernet-like interface in
the system which implements the MAC Control
sublayer. If some, but not all, of the
ethernet-like interfaces in the system implement
the MAC Control sublayer, there will be fewer
rows in this table than in the dot3StatsTable."
::= { dot3 9 }
dot3ControlEntry OBJECT-TYPE
SYNTAX Dot3ControlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "An entry in the table, containing information
about the MAC Control sublayer on a single
ethernet-like interface."
INDEX { dot3StatsIndex }
::= { dot3ControlTable 1 }
dot3ControlEntry OBJECT-TYPE
SYNTAX Dot3ControlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "An entry in the table, containing information
about the MAC Control sublayer on a single
ethernet-like interface."
INDEX { dot3StatsIndex }
::= { dot3ControlTable 1 }
Dot3ControlEntry ::=
SEQUENCE {
dot3ControlFunctionsSupported BITS,
dot3ControlInUnknownOpcodes Counter32,
dot3HCControlInUnknownOpcodes Counter64
}
Dot3ControlEntry ::=
SEQUENCE {
dot3ControlFunctionsSupported BITS,
dot3ControlInUnknownOpcodes Counter32,
dot3HCControlInUnknownOpcodes Counter64
}
dot3ControlFunctionsSupported OBJECT-TYPE
SYNTAX BITS {
pause(0) -- 802.3 flow control
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION "A list of the possible MAC Control functions
implemented for this interface."
REFERENCE "[IEEE 802.3 Std.], 30.3.3.2,
aMACControlFunctionsSupported."
dot3ControlFunctionsSupported OBJECT-TYPE
SYNTAX BITS {
pause(0) -- 802.3 flow control
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION "A list of the possible MAC Control functions
implemented for this interface."
REFERENCE "[IEEE 802.3 Std.], 30.3.3.2,
aMACControlFunctionsSupported."
::= { dot3ControlEntry 1 }
::= { dot3ControlEntry 1 }
dot3ControlInUnknownOpcodes OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "A count of MAC Control frames received on this interface that contain an opcode that is not supported by this device.
dot3ControlInUnknownOpcodes对象类型语法计数器32 MAX-ACCESS只读状态当前描述“此接口上接收的MAC控制帧计数，其中包含此设备不支持的操作码。
For interfaces operating at 10 Gb/s, this counter can roll over in less than 5 minutes if it is incrementing at its maximum rate. Since that amount of time could be less than a management station's poll cycle time, in order to avoid a loss of information, a management station is advised to poll the dot3HCControlInUnknownOpcodes object for 10 Gb/s or faster interfaces.
对于以10 Gb/s速度运行的接口，如果计数器以最大速率递增，则该计数器可以在不到5分钟内翻转。由于该时间量可能小于管理站的轮询周期时间，为了避免信息丢失，建议管理站轮询dot3HCControlInUnknownOpcodes对象以获得10 Gb/s或更快的接口。
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.3.5,
aUnsupportedOpcodesReceived"
::= { dot3ControlEntry 2 }
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.3.5,
aUnsupportedOpcodesReceived"
::= { dot3ControlEntry 2 }
dot3HCControlInUnknownOpcodes OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "A count of MAC Control frames received on this interface that contain an opcode that is not supported by this device.
dot3HCControlInUnknownOpcodes对象类型语法计数器64 MAX-ACCESS只读状态当前描述“此接口上接收的MAC控制帧计数，其中包含此设备不支持的操作码。
This counter is a 64 bit version of dot3ControlInUnknownOpcodes. It should be used on interfaces operating at 10 Gb/s or faster.
此计数器是dot3ControlInUnknownOpcodes的64位版本。应在以10 Gb/s或更快速度运行的接口上使用。
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.3.5,
aUnsupportedOpcodesReceived"
::= { dot3ControlEntry 3 }
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.3.5,
aUnsupportedOpcodesReceived"
::= { dot3ControlEntry 3 }
dot3PauseTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3PauseEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "A table of descriptive and status information
about the MAC Control PAUSE function on the
ethernet-like interfaces attached to a
particular system. There will be one row in
this table for each ethernet-like interface in
the system which supports the MAC Control PAUSE
function (i.e., the 'pause' bit in the
corresponding instance of
dot3ControlFunctionsSupported is set). If some,
but not all, of the ethernet-like interfaces in
the system implement the MAC Control PAUSE
function (for example, if some interfaces only
support half-duplex), there will be fewer rows
in this table than in the dot3StatsTable."
::= { dot3 10 }
dot3PauseTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3PauseEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "A table of descriptive and status information
about the MAC Control PAUSE function on the
ethernet-like interfaces attached to a
particular system. There will be one row in
this table for each ethernet-like interface in
the system which supports the MAC Control PAUSE
function (i.e., the 'pause' bit in the
corresponding instance of
dot3ControlFunctionsSupported is set). If some,
but not all, of the ethernet-like interfaces in
the system implement the MAC Control PAUSE
function (for example, if some interfaces only
support half-duplex), there will be fewer rows
in this table than in the dot3StatsTable."
::= { dot3 10 }
dot3PauseEntry OBJECT-TYPE
SYNTAX Dot3PauseEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "An entry in the table, containing information
about the MAC Control PAUSE function on a single
ethernet-like interface."
INDEX { dot3StatsIndex }
::= { dot3PauseTable 1 }
dot3PauseEntry OBJECT-TYPE
SYNTAX Dot3PauseEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "An entry in the table, containing information
about the MAC Control PAUSE function on a single
ethernet-like interface."
INDEX { dot3StatsIndex }
::= { dot3PauseTable 1 }
Dot3PauseEntry ::=
Dot3PauseEntry ::=
SEQUENCE {
dot3PauseAdminMode INTEGER,
dot3PauseOperMode INTEGER,
dot3InPauseFrames Counter32,
dot3OutPauseFrames Counter32,
dot3HCInPauseFrames Counter64,
dot3HCOutPauseFrames Counter64
}
SEQUENCE {
dot3PauseAdminMode INTEGER,
dot3PauseOperMode INTEGER,
dot3InPauseFrames Counter32,
dot3OutPauseFrames Counter32,
dot3HCInPauseFrames Counter64,
dot3HCOutPauseFrames Counter64
}
dot3PauseAdminMode OBJECT-TYPE
SYNTAX INTEGER {
disabled(1),
enabledXmit(2),
enabledRcv(3),
enabledXmitAndRcv(4)
}
dot3PauseAdminMode OBJECT-TYPE
SYNTAX INTEGER {
disabled(1),
enabledXmit(2),
enabledRcv(3),
enabledXmitAndRcv(4)
}
MAX-ACCESS read-write STATUS current DESCRIPTION "This object is used to configure the default administrative PAUSE mode for this interface.
MAX-ACCESS读写状态当前描述“此对象用于配置此接口的默认管理暂停模式。
This object represents the administratively-configured PAUSE mode for this interface. If auto-negotiation is not enabled or is not implemented for the active MAU attached to this interface, the value of this object determines the operational PAUSE mode of the interface whenever it is operating in full-duplex mode. In this case, a set to this object will force the interface into the specified mode.
此对象表示此接口的管理配置的暂停模式。如果连接到此接口的活动MAU未启用或未实现自动协商，则无论何时在全双工模式下操作，此对象的值都将确定接口的操作暂停模式。在这种情况下，设置此对象将强制接口进入指定模式。
If auto-negotiation is implemented and enabled for the MAU attached to this interface, the PAUSE mode for this interface is determined by auto-negotiation, and the value of this object denotes the mode to which the interface will automatically revert if/when auto-negotiation is later disabled. Note that when auto-negotiation is running, administrative control of the PAUSE mode may be accomplished using the ifMauAutoNegCapAdvertisedBits object in the MAU-MIB.
如果为连接到此接口的MAU实现并启用了自动协商，则此接口的暂停模式由自动协商确定，并且此对象的值表示在以后禁用自动协商时接口将自动恢复到的模式。请注意，在运行自动协商时，可以使用MAU-MIB中的ifMauAutoNegCapAdvertisedBits对象来完成暂停模式的管理控制。
Note that the value of this object is ignored when the interface is not operating in full-duplex mode.
请注意，当接口未在全双工模式下运行时，将忽略此对象的值。
An attempt to set this object to
'enabledXmit(2)' or 'enabledRcv(3)' will fail
on interfaces that do not support operation
at greater than 100 Mb/s."
::= { dot3PauseEntry 1 }
An attempt to set this object to
'enabledXmit(2)' or 'enabledRcv(3)' will fail
on interfaces that do not support operation
at greater than 100 Mb/s."
::= { dot3PauseEntry 1 }
dot3PauseOperMode OBJECT-TYPE
SYNTAX INTEGER {
disabled(1),
enabledXmit(2),
enabledRcv(3),
enabledXmitAndRcv(4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION "This object reflects the PAUSE mode currently
dot3PauseOperMode OBJECT-TYPE
SYNTAX INTEGER {
disabled(1),
enabledXmit(2),
enabledRcv(3),
enabledXmitAndRcv(4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION "This object reflects the PAUSE mode currently
in use on this interface, as determined by
either (1) the result of the auto-negotiation
function or (2) if auto-negotiation is not
enabled or is not implemented for the active MAU
attached to this interface, by the value of
dot3PauseAdminMode. Interfaces operating at
100 Mb/s or less will never return
'enabledXmit(2)' or 'enabledRcv(3)'. Interfaces
operating in half-duplex mode will always return
'disabled(1)'. Interfaces on which
auto-negotiation is enabled but not yet
completed should return the value
'disabled(1)'."
::= { dot3PauseEntry 2 }
in use on this interface, as determined by
either (1) the result of the auto-negotiation
function or (2) if auto-negotiation is not
enabled or is not implemented for the active MAU
attached to this interface, by the value of
dot3PauseAdminMode. Interfaces operating at
100 Mb/s or less will never return
'enabledXmit(2)' or 'enabledRcv(3)'. Interfaces
operating in half-duplex mode will always return
'disabled(1)'. Interfaces on which
auto-negotiation is enabled but not yet
completed should return the value
'disabled(1)'."
::= { dot3PauseEntry 2 }
dot3InPauseFrames OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "A count of MAC Control frames received on this interface with an opcode indicating the PAUSE operation.
dot3InPauseFrames对象类型语法计数器32 MAX-ACCESS只读状态当前描述“此接口上接收的MAC控制帧计数，操作码指示暂停操作。
This counter does not increment when the interface is operating in half-duplex mode.
当接口在半双工模式下工作时，此计数器不递增。
For interfaces operating at 10 Gb/s, this counter can roll over in less than 5 minutes if it is incrementing at its maximum rate. Since that amount of time could be less than a management station's poll cycle time, in order to avoid a loss of information, a management station is advised to poll the dot3HCInPauseFrames object for 10 Gb/s or faster interfaces.
对于以10 Gb/s速度运行的接口，如果计数器以最大速率递增，则该计数器可以在不到5分钟内翻转。由于该时间量可能小于管理站的轮询周期时间，为了避免信息丢失，建议管理站轮询dot3HCInPauseFrames对象以获得10 Gb/s或更快的接口。
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.4.3,
aPAUSEMACCtrlFramesReceived."
::= { dot3PauseEntry 3 }
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.4.3,
aPAUSEMACCtrlFramesReceived."
::= { dot3PauseEntry 3 }
dot3OutPauseFrames OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current
dot3OutPauseFrames对象类型语法计数器32 MAX-ACCESS只读状态当前
DESCRIPTION "A count of MAC Control frames transmitted on this interface with an opcode indicating the PAUSE operation.
DESCRIPTION“此接口上传输的MAC控制帧计数，带有指示暂停操作的操作码。
This counter does not increment when the interface is operating in half-duplex mode.
当接口在半双工模式下工作时，此计数器不递增。
For interfaces operating at 10 Gb/s, this counter can roll over in less than 5 minutes if it is incrementing at its maximum rate. Since that amount of time could be less than a management station's poll cycle time, in order to avoid a loss of information, a management station is advised to poll the dot3HCOutPauseFrames object for 10 Gb/s or faster interfaces.
对于以10 Gb/s速度运行的接口，如果计数器以最大速率递增，则该计数器可以在不到5分钟内翻转。由于该时间量可能小于管理站的轮询周期时间，为了避免信息丢失，建议管理站轮询dot3HCOutPauseFrames对象以获得10 Gb/s或更快的接口。
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.4.2,
aPAUSEMACCtrlFramesTransmitted."
::= { dot3PauseEntry 4 }
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.4.2,
aPAUSEMACCtrlFramesTransmitted."
::= { dot3PauseEntry 4 }
dot3HCInPauseFrames OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "A count of MAC Control frames received on this interface with an opcode indicating the PAUSE operation.
dot3HCInPauseFrames对象类型语法计数器64 MAX-ACCESS只读状态当前描述“此接口上接收的MAC控制帧计数，操作码指示暂停操作。
This counter does not increment when the interface is operating in half-duplex mode.
当接口在半双工模式下工作时，此计数器不递增。
This counter is a 64 bit version of dot3InPauseFrames. It should be used on interfaces operating at 10 Gb/s or faster.
此计数器是dot3InPauseFrames的64位版本。应在以10 Gb/s或更快速度运行的接口上使用。
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.4.3,
aPAUSEMACCtrlFramesReceived."
::= { dot3PauseEntry 5 }
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.4.3,
aPAUSEMACCtrlFramesReceived."
::= { dot3PauseEntry 5 }
dot3HCOutPauseFrames OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "A count of MAC Control frames transmitted on this interface with an opcode indicating the PAUSE operation.
dot3HCOutPauseFrames对象类型语法计数器64 MAX-ACCESS只读状态当前描述“此接口上传输的MAC控制帧计数，带有指示暂停操作的操作码。
This counter does not increment when the interface is operating in half-duplex mode.
当接口在半双工模式下工作时，此计数器不递增。
This counter is a 64 bit version of dot3OutPauseFrames. It should be used on interfaces operating at 10 Gb/s or faster.
此计数器是dot3OutPauseFrames的64位版本。应在以10 Gb/s或更快速度运行的接口上使用。
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.4.2,
aPAUSEMACCtrlFramesTransmitted."
::= { dot3PauseEntry 6 }
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.4.2,
aPAUSEMACCtrlFramesTransmitted."
::= { dot3PauseEntry 6 }
dot3HCStatsTable OBJECT-TYPE SYNTAX SEQUENCE OF Dot3HCStatsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table containing 64-bit versions of error counters from the dot3StatsTable. The 32-bit versions of these counters may roll over quite quickly on higher speed ethernet interfaces. The counters that have 64-bit versions in this table are the counters that apply to full-duplex interfaces, since 10 Gb/s and faster ethernet-like interfaces do not support half-duplex, and very few 1000 Mb/s ethernet-like interfaces support half-duplex.
Dot3hcsAtSentry MAX-ACCESS的Dot3hcsAtStable对象类型语法序列不可访问状态当前描述“包含来自DOT3STARTABLE的错误计数器的64位版本的表。这些计数器的32位版本在更高速的以太网接口上可能会很快过渡。此表中具有64位版本的计数器是适用于全双工接口的计数器，因为10 Gb/s和更快的类以太网接口不支持半双工，很少1000 Mb/s类以太网接口支持半双工。
Entries in this table are recommended for interfaces capable of operating at 1000 Mb/s or faster, and are required for interfaces capable of operating at 10 Gb/s or faster. Lower speed ethernet-like interfaces do not need entries in this table, in which case there may be fewer entries in this table than in the dot3StatsTable. However, implementations containing interfaces with a mix of speeds may choose to implement entries in this table for
此表中的条目建议用于能够以1000 Mb/s或更高速度运行的接口，并且对于能够以10 Gb/s或更高速度运行的接口是必需的。低速以太网类接口不需要此表中的条目，在这种情况下，此表中的条目可能比dot3statable中的条目少。但是，对于包含混合速度接口的实现，可以选择实现此表中的条目
all ethernet-like interfaces."
::= { dot3 11 }
all ethernet-like interfaces."
::= { dot3 11 }
dot3HCStatsEntry OBJECT-TYPE
SYNTAX Dot3HCStatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "An entry containing 64-bit statistics for a
single ethernet-like interface."
INDEX { dot3StatsIndex }
::= { dot3HCStatsTable 1 }
dot3HCStatsEntry OBJECT-TYPE
SYNTAX Dot3HCStatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "An entry containing 64-bit statistics for a
single ethernet-like interface."
INDEX { dot3StatsIndex }
::= { dot3HCStatsTable 1 }
Dot3HCStatsEntry ::=
SEQUENCE {
dot3HCStatsAlignmentErrors Counter64,
dot3HCStatsFCSErrors Counter64,
dot3HCStatsInternalMacTransmitErrors Counter64,
dot3HCStatsFrameTooLongs Counter64,
dot3HCStatsInternalMacReceiveErrors Counter64,
dot3HCStatsSymbolErrors Counter64
}
Dot3HCStatsEntry ::=
SEQUENCE {
dot3HCStatsAlignmentErrors Counter64,
dot3HCStatsFCSErrors Counter64,
dot3HCStatsInternalMacTransmitErrors Counter64,
dot3HCStatsFrameTooLongs Counter64,
dot3HCStatsInternalMacReceiveErrors Counter64,
dot3HCStatsSymbolErrors Counter64
}
dot3HCStatsAlignmentErrors OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "A count of frames received on a particular interface that are not an integral number of octets in length and do not pass the FCS check.
dot3HCStatsAlignmentErrors对象类型语法计数器64 MAX-ACCESS只读状态当前描述“特定接口上接收的帧计数，其长度不是八位字节的整数，且未通过FCS检查。
The count represented by an instance of this object is incremented when the alignmentError status is returned by the MAC service to the LLC (or other MAC user). Received frames for which multiple error conditions pertain are, according to the conventions of IEEE 802.3 Layer Management, counted exclusively according to the error status presented to the LLC.
当MAC服务将alignmentError状态返回给LLC（或其他MAC用户）时，此对象实例表示的计数将增加。根据IEEE 802.3层管理的约定，与多个错误条件相关的接收帧仅根据呈现给LLC的错误状态进行计数。
This counter does not increment for group encoding schemes greater than 4 bits per group.
对于大于每组4位的组编码方案，此计数器的增量不大于4位。
This counter is a 64 bit version of dot3StatsAlignmentErrors. It should be used on interfaces operating at 10 Gb/s or faster.
此计数器是dot3StatsAlignmentErrors的64位版本。应在以10 Gb/s或更快速度运行的接口上使用。
Discontinuities in the value of this counter can occur at re-initialization of the management
重新初始化管理时，此计数器的值可能会出现不连续
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.7,
aAlignmentErrors"
::= { dot3HCStatsEntry 1 }
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.7,
aAlignmentErrors"
::= { dot3HCStatsEntry 1 }
dot3HCStatsFCSErrors OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "A count of frames received on a particular interface that are an integral number of octets in length but do not pass the FCS check. This count does not include frames received with frame-too-long or frame-too-short error.
dot3HCStatsFCSErrors对象类型语法计数器64 MAX-ACCESS只读状态当前描述“在特定接口上接收的帧计数，其长度为八位字节的整数，但未通过FCS检查。此计数不包括接收到的帧过长或帧过短错误。
The count represented by an instance of this object is incremented when the frameCheckError status is returned by the MAC service to the LLC (or other MAC user). Received frames for which multiple error conditions pertain are, according to the conventions of IEEE 802.3 Layer Management, counted exclusively according to the error status presented to the LLC.
当MAC服务向LLC（或其他MAC用户）返回frameCheckError状态时，此对象实例表示的计数将增加。根据IEEE 802.3层管理的约定，与多个错误条件相关的接收帧仅根据呈现给LLC的错误状态进行计数。
Note: Coding errors detected by the physical layer for speeds above 10 Mb/s will cause the frame to fail the FCS check.
注：当速度超过10 Mb/s时，物理层检测到的编码错误将导致帧无法通过FCS检查。
This counter is a 64 bit version of dot3StatsFCSErrors. It should be used on interfaces operating at 10 Gb/s or faster.
此计数器是64位版本的DOT3STATSCSERRORS。应在以10 Gb/s或更快速度运行的接口上使用。
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.6,
aFrameCheckSequenceErrors."
::= { dot3HCStatsEntry 2 }
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.6,
aFrameCheckSequenceErrors."
::= { dot3HCStatsEntry 2 }
dot3HCStatsInternalMacTransmitErrors OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "A count of frames for which transmission on a particular interface fails due to an internal MAC sublayer transmit error. A frame is only
dot3HCStatsInternalMacTransmitErrors对象类型语法计数器64 MAX-ACCESS只读状态当前描述“由于内部MAC子层传输错误，特定接口上传输失败的帧计数。一个帧仅为
counted by an instance of this object if it is not counted by the corresponding instance of either the dot3StatsLateCollisions object, the dot3StatsExcessiveCollisions object, or the dot3StatsCarrierSenseErrors object.
如果此对象的实例未被dot3StatsLateCollisions对象、Dot3StatsAccessiveCollisions对象或dot3StatsCarrierSenseErrors对象的相应实例计数，则由该对象的实例计数。
The precise meaning of the count represented by an instance of this object is implementation-specific. In particular, an instance of this object may represent a count of transmission errors on a particular interface that are not otherwise counted.
此对象的实例表示的计数的确切含义是特定于实现的。特别地，该对象的实例可以表示特定接口上的传输错误的计数，否则这些错误不会被计数。
This counter is a 64 bit version of dot3StatsInternalMacTransmitErrors. It should be used on interfaces operating at 10 Gb/s or faster.
此计数器是64位版本的dot3StatsInternalMacTransmitErrors。应在以10 Gb/s或更快速度运行的接口上使用。
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.12,
aFramesLostDueToIntMACXmitError."
::= { dot3HCStatsEntry 3 }
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.12,
aFramesLostDueToIntMACXmitError."
::= { dot3HCStatsEntry 3 }
dot3HCStatsFrameTooLongs OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "A count of frames received on a particular interface that exceed the maximum permitted frame size.
dot3HCStatsFrameTooLongs对象类型语法计数器64 MAX-ACCESS只读状态当前描述“在特定接口上接收到的超过最大允许帧大小的帧计数。
The count represented by an instance of this object is incremented when the frameTooLong status is returned by the MAC service to the LLC (or other MAC user). Received frames for which multiple error conditions pertain are, according to the conventions of IEEE 802.3 Layer Management, counted exclusively according to the error status presented to the LLC.
当MAC服务将FrameToolLong状态返回给LLC（或其他MAC用户）时，此对象实例表示的计数将增加。根据IEEE 802.3层管理的约定，与多个错误条件相关的接收帧仅根据呈现给LLC的错误状态进行计数。
This counter is a 64 bit version of dot3StatsFrameTooLongs. It should be used on interfaces operating at 10 Gb/s or faster.
此计数器是Dot3StatsFrameToolLongs的64位版本。应在以10 Gb/s或更快速度运行的接口上使用。
Discontinuities in the value of this counter can
此计数器值的不连续性可能会导致
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.25,
aFrameTooLongErrors."
::= { dot3HCStatsEntry 4 }
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.25,
aFrameTooLongErrors."
::= { dot3HCStatsEntry 4 }
dot3HCStatsInternalMacReceiveErrors OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "A count of frames for which reception on a particular interface fails due to an internal MAC sublayer receive error. A frame is only counted by an instance of this object if it is not counted by the corresponding instance of either the dot3StatsFrameTooLongs object, the dot3StatsAlignmentErrors object, or the dot3StatsFCSErrors object.
dot3HCStatsInternalMacReceiveErrors对象类型语法计数器64 MAX-ACCESS只读状态当前说明“由于内部MAC子层接收错误，在特定接口上接收失败的帧计数。如果帧未由dot3StatsFrameTooLongs对象、dot3StatsAlignmentErrors对象或Dot3StatsSecurErrors对象的相应实例计数，则仅由该对象的实例计数。
The precise meaning of the count represented by an instance of this object is implementation-specific. In particular, an instance of this object may represent a count of receive errors on a particular interface that are not otherwise counted.
此对象的实例表示的计数的确切含义是特定于实现的。特别地，该对象的实例可以表示特定接口上未被计数的接收错误的计数。
This counter is a 64 bit version of dot3StatsInternalMacReceiveErrors. It should be used on interfaces operating at 10 Gb/s or faster.
此计数器是dot3StatsInternalMacReceiveErrors的64位版本。应在以10 Gb/s或更快速度运行的接口上使用。
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.15,
aFramesLostDueToIntMACRcvError."
::= { dot3HCStatsEntry 5 }
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.15,
aFramesLostDueToIntMACRcvError."
::= { dot3HCStatsEntry 5 }
dot3HCStatsSymbolErrors OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "For an interface operating at 100 Mb/s, the number of times there was an invalid data symbol when a valid carrier was present.
dot3HCStatsSymbolErrors对象类型语法计数器64 MAX-ACCESS只读状态当前说明“对于以100 Mb/s速度运行的接口，存在有效载波时存在无效数据符号的次数。
For an interface operating in half-duplex mode at 1000 Mb/s, the number of times the receiving media is non-idle (a carrier event) for a period of time equal to or greater than slotTime, and during which there was at least one occurrence of an event that causes the PHY to indicate 'Data reception error' or 'carrier extend error' on the GMII.
对于以1000 Mb/s的速度在半双工模式下运行的接口，接收媒体在等于或大于时隙时间的时间段内处于非空闲状态（载波事件）的次数，并且在此期间至少发生了一次导致PHY在GMII上指示“数据接收错误”或“载波扩展错误”的事件。
For an interface operating in full-duplex mode at 1000 Mb/s, the number of times the receiving media is non-idle (a carrier event) for a period of time equal to or greater than minFrameSize, and during which there was at least one occurrence of an event that causes the PHY to indicate 'Data reception error' on the GMII.
对于以1000 Mb/s全双工模式运行的接口，接收媒体在等于或大于minFrameSize的时间段内非空闲（载波事件）的次数，并且在此期间至少发生一次导致PHY在GMII上指示“数据接收错误”的事件。
For an interface operating at 10 Gb/s, the number of times the receiving media is non-idle (a carrier event) for a period of time equal to or greater than minFrameSize, and during which there was at least one occurrence of an event that causes the PHY to indicate 'Receive Error' on the XGMII.
对于以10 Gb/s速度运行的接口，接收媒体在等于或大于minFrameSize的时间段内处于非空闲状态（载波事件）的次数，在此期间至少发生一次导致PHY在XGMII上指示“接收错误”的事件。
The count represented by an instance of this object is incremented at most once per carrier event, even if multiple symbol errors occur during the carrier event. This count does not increment if a collision is present.
此对象实例表示的计数在每个载波事件中最多增加一次，即使在载波事件期间发生多个符号错误。如果存在碰撞，此计数不会增加。
This counter is a 64 bit version of dot3StatsSymbolErrors. It should be used on interfaces operating at 10 Gb/s or faster.
此计数器是dot3StatsSymbolErrors的64位版本。应在以10 Gb/s或更快速度运行的接口上使用。
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.2.1.5,
aSymbolErrorDuringCarrier."
::= { dot3HCStatsEntry 6 }
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.2.1.5,
aSymbolErrorDuringCarrier."
::= { dot3HCStatsEntry 6 }
-- 802.3 Tests
--802.3测试
dot3Tests OBJECT IDENTIFIER ::= { dot3 6 }
dot3Tests OBJECT IDENTIFIER ::= { dot3 6 }
dot3Errors OBJECT IDENTIFIER ::= { dot3 7 }
dot3Errors OBJECT IDENTIFIER ::= { dot3 7 }
-- TDR Test
--TDR试验
dot3TestTdr OBJECT-IDENTITY
STATUS deprecated
DESCRIPTION "******** THIS IDENTITY IS DEPRECATED *******
dot3TestTdr OBJECT-IDENTITY
STATUS deprecated
DESCRIPTION "******** THIS IDENTITY IS DEPRECATED *******
The Time-Domain Reflectometry (TDR) test is specific to ethernet-like interfaces of type 10Base5 and 10Base2. The TDR value may be useful in determining the approximate distance to a cable fault. It is advisable to repeat this test to check for a consistent resulting TDR value, to verify that there is a fault.
时域反射仪（TDR）测试专用于10Base5和10Base2型以太网接口。TDR值可用于确定电缆故障的近似距离。建议重复此测试，以检查产生的TDR值是否一致，以验证是否存在故障。
A TDR test returns as its result the time interval, measured in 10 MHz ticks or 100 nsec units, between the start of TDR test transmission and the subsequent detection of a collision or deassertion of carrier. On successful completion of a TDR test, the result is stored as the value of an appropriate instance of an appropriate vendor specific MIB object, and the OBJECT IDENTIFIER of that instance is stored in the appropriate instance of the appropriate test result code object (thereby indicating where the result has been stored).
TDR测试返回TDR测试传输开始与随后检测到载波碰撞或分离之间的时间间隔（以10 MHz时钟或100纳秒为单位）。成功完成TDR测试后，结果存储为适当供应商特定MIB对象的适当实例的值，该实例的对象标识符存储在适当测试结果代码对象的适当实例中（从而指示结果存储的位置）。
This object identity has been deprecated, since
the ifTestTable in the IF-MIB was deprecated,
and there is no longer a standard mechanism for
initiating an interface test. This left no
standard way of using this object identity."
::= { dot3Tests 1 }
This object identity has been deprecated, since
the ifTestTable in the IF-MIB was deprecated,
and there is no longer a standard mechanism for
initiating an interface test. This left no
standard way of using this object identity."
::= { dot3Tests 1 }
-- Loopback Test
--环回测试
dot3TestLoopBack OBJECT-IDENTITY
STATUS deprecated
DESCRIPTION "******** THIS IDENTITY IS DEPRECATED *******
dot3TestLoopBack OBJECT-IDENTITY
STATUS deprecated
DESCRIPTION "******** THIS IDENTITY IS DEPRECATED *******
This test configures the MAC chip and executes an internal loopback test of memory, data paths, and the MAC chip logic. This loopback test can only be executed if the interface is offline. Once the test has completed, the MAC chip should
该测试配置MAC芯片，并执行内存、数据路径和MAC芯片逻辑的内部环回测试。此环回测试只能在接口脱机时执行。一旦测试完成，MAC芯片应
be reinitialized for network operation, but it should remain offline.
重新初始化以进行网络操作，但应保持脱机状态。
If an error occurs during a test, the appropriate test result object will be set to indicate a failure. The two OBJECT IDENTIFIER values dot3ErrorInitError and dot3ErrorLoopbackError may be used to provided more information as values for an appropriate test result code object.
如果在测试期间发生错误，将设置适当的测试结果对象以指示失败。两个对象标识符值dot3ErrorInitError和dot3ErrorLoopbackError可用于提供更多信息，作为适当测试结果代码对象的值。
This object identity has been deprecated, since
the ifTestTable in the IF-MIB was deprecated,
and there is no longer a standard mechanism for
initiating an interface test. This left no
standard way of using this object identity."
::= { dot3Tests 2 }
This object identity has been deprecated, since
the ifTestTable in the IF-MIB was deprecated,
and there is no longer a standard mechanism for
initiating an interface test. This left no
standard way of using this object identity."
::= { dot3Tests 2 }
dot3ErrorInitError OBJECT-IDENTITY
STATUS deprecated
DESCRIPTION "******** THIS IDENTITY IS DEPRECATED *******
dot3ErrorInitError OBJECT-IDENTITY
STATUS deprecated
DESCRIPTION "******** THIS IDENTITY IS DEPRECATED *******
Couldn't initialize MAC chip for test.
无法初始化MAC芯片进行测试。
This object identity has been deprecated, since
the ifTestTable in the IF-MIB was deprecated,
and there is no longer a standard mechanism for
initiating an interface test. This left no
standard way of using this object identity."
::= { dot3Errors 1 }
This object identity has been deprecated, since
the ifTestTable in the IF-MIB was deprecated,
and there is no longer a standard mechanism for
initiating an interface test. This left no
standard way of using this object identity."
::= { dot3Errors 1 }
dot3ErrorLoopbackError OBJECT-IDENTITY
STATUS deprecated
DESCRIPTION "******** THIS IDENTITY IS DEPRECATED *******
dot3ErrorLoopbackError OBJECT-IDENTITY
STATUS deprecated
DESCRIPTION "******** THIS IDENTITY IS DEPRECATED *******
Expected data not received (or not received correctly) in loopback test.
在环回测试中未收到（或未正确收到）预期数据。
This object identity has been deprecated, since
the ifTestTable in the IF-MIB was deprecated,
and there is no longer a standard mechanism for
initiating an interface test. This left no
standard way of using this object identity."
::= { dot3Errors 2 }
This object identity has been deprecated, since
the ifTestTable in the IF-MIB was deprecated,
and there is no longer a standard mechanism for
initiating an interface test. This left no
standard way of using this object identity."
::= { dot3Errors 2 }
-- { dot3 8 }, the dot3ChipSets tree, is defined in [RFC2666]
--[RFC2666]中定义了dot3ChipSets树{dot3 8}
-- conformance information
--一致性信息
etherConformance OBJECT IDENTIFIER ::= { etherMIB 2 }
etherConformance OBJECT IDENTIFIER ::= { etherMIB 2 }
etherGroups OBJECT IDENTIFIER ::= { etherConformance 1 }
etherCompliances OBJECT IDENTIFIER ::= { etherConformance 2 }
etherGroups OBJECT IDENTIFIER ::= { etherConformance 1 }
etherCompliances OBJECT IDENTIFIER ::= { etherConformance 2 }
-- compliance statements
--合规声明
etherCompliance MODULE-COMPLIANCE
STATUS deprecated
DESCRIPTION "******** THIS COMPLIANCE IS DEPRECATED ********
etherCompliance MODULE-COMPLIANCE
STATUS deprecated
DESCRIPTION "******** THIS COMPLIANCE IS DEPRECATED ********
The compliance statement for managed network entities which have ethernet-like network interfaces.
具有类似以太网的网络接口的受管网络实体的符合性声明。
This compliance is deprecated and replaced by dot3Compliance."
此合规性已被弃用，并被dot3Compliance取代。”
MODULE -- this module MANDATORY-GROUPS { etherStatsGroup }
MODULE--此模块是必需的-GROUPS{etherStatsGroup}
GROUP etherCollisionTableGroup
DESCRIPTION "This group is optional. It is appropriate
for all systems which have the necessary
metering. Implementation in such systems is
highly recommended."
::= { etherCompliances 1 }
GROUP etherCollisionTableGroup
DESCRIPTION "This group is optional. It is appropriate
for all systems which have the necessary
metering. Implementation in such systems is
highly recommended."
::= { etherCompliances 1 }
ether100MbsCompliance MODULE-COMPLIANCE
STATUS deprecated
DESCRIPTION "******** THIS COMPLIANCE IS DEPRECATED ********
ether100MbsCompliance MODULE-COMPLIANCE
STATUS deprecated
DESCRIPTION "******** THIS COMPLIANCE IS DEPRECATED ********
The compliance statement for managed network entities which have 100 Mb/sec ethernet-like network interfaces.
具有100 Mb/s以太网式网络接口的受管网络实体的合规性声明。
This compliance is deprecated and replaced by dot3Compliance."
此合规性已被弃用，并被dot3Compliance取代。”
MODULE -- this module MANDATORY-GROUPS { etherStats100MbsGroup }
MODULE——此模块为强制组{EtherstStats100MBsgroup}
GROUP etherCollisionTableGroup
DESCRIPTION "This group is optional. It is appropriate
for all systems which have the necessary
metering. Implementation in such systems is
highly recommended."
::= { etherCompliances 2 }
GROUP etherCollisionTableGroup
DESCRIPTION "This group is optional. It is appropriate
for all systems which have the necessary
metering. Implementation in such systems is
highly recommended."
::= { etherCompliances 2 }
dot3Compliance MODULE-COMPLIANCE
STATUS deprecated
DESCRIPTION "******** THIS COMPLIANCE IS DEPRECATED ********
dot3Compliance MODULE-COMPLIANCE
STATUS deprecated
DESCRIPTION "******** THIS COMPLIANCE IS DEPRECATED ********
The compliance statement for managed network entities which have ethernet-like network interfaces.
具有类似以太网的网络接口的受管网络实体的符合性声明。
This compliance is deprecated and replaced by dot3Compliance2."
此法规遵从性已被弃用，并被DOT3Compliance 2取代。”
MODULE -- this module MANDATORY-GROUPS { etherStatsBaseGroup }
MODULE--此模块是必需的-GROUPS{EtherstStatsBaseGroup}
GROUP etherDuplexGroup DESCRIPTION "This group is mandatory for all ethernet-like network interfaces which are capable of operating in full-duplex mode. It is highly recommended for all ethernet-like network interfaces."
GROUP etherDuplexGroup DESCRIPTION“此组对于能够在全双工模式下运行的所有类似以太网的网络接口是必需的。强烈建议用于所有类似以太网的网络接口。”
GROUP etherStatsLowSpeedGroup DESCRIPTION "This group is mandatory for all ethernet-like network interfaces which are capable of operating at 10 Mb/s or slower in half-duplex mode."
GROUP EtherstStatsLowSpeedGroup DESCRIPTION“此组对于所有能够在半双工模式下以10 Mb/s或更低速度运行的类似以太网的网络接口是必需的。”
GROUP etherStatsHighSpeedGroup DESCRIPTION "This group is mandatory for all ethernet-like network interfaces which are capable of operating at 100 Mb/s or faster."
GROUP EtherstStatsHighSpeedGroup DESCRIPTION“对于能够以100 Mb/s或更快速度运行的所有类似以太网的网络接口，此组是必需的。”
GROUP etherControlGroup DESCRIPTION "This group is mandatory for all ethernet-like network interfaces that support the MAC Control sublayer."
GROUP etherControlGroup DESCRIPTION“此组对于支持MAC控制子层的所有类似以太网的网络接口都是必需的。”
GROUP etherControlPauseGroup DESCRIPTION "This group is mandatory for all ethernet-like network interfaces that support the MAC Control PAUSE function."
GROUP etherControlPauseGroup DESCRIPTION“此组对于支持MAC控制暂停功能的所有类似以太网的网络接口都是必需的。”
GROUP etherCollisionTableGroup DESCRIPTION "This group is optional. It is appropriate for all ethernet-like network interfaces which are capable of operating in half-duplex mode and have the necessary metering. Implementation in systems with
GROUP etherCollisionTableGroup DESCRIPTION“此组是可选的。它适用于所有能够在半双工模式下运行并具有必要计量功能的类似以太网的网络接口。在具有
such interfaces is highly recommended."
::= { etherCompliances 3 }
such interfaces is highly recommended."
::= { etherCompliances 3 }
dot3Compliance2 MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for managed network entities which have ethernet-like network interfaces.
DOT3Compliance 2 MODULE-COMPLIANCE STATUS current DESCRIPTION“具有类似以太网的网络接口的受管网络实体的符合性声明。
Note that compliance with this MIB module requires compliance with the ifCompliance3 MODULE-COMPLIANCE statement of the IF-MIB (RFC2863). In addition, compliance with this MIB module requires compliance with the mauModIfCompl3 MODULE-COMPLIANCE statement of the MAU-MIB (RFC3636)."
请注意，符合此MIB模块要求符合IF-MIB（RFC2863）的ifCompliance3模块符合性声明。此外，符合此MIB模块要求符合MAU-MIB（RFC3636）的mauModIfCompl3模块符合性声明。”
MODULE -- this module MANDATORY-GROUPS { etherStatsBaseGroup2 }
MODULE--此模块是必需的-GROUPS{EtherstStatsBaseGroup2}
GROUP etherDuplexGroup DESCRIPTION "This group is mandatory for all ethernet-like network interfaces which are capable of operating in full-duplex mode. It is highly recommended for all ethernet-like network interfaces."
GROUP etherDuplexGroup DESCRIPTION“此组对于能够在全双工模式下运行的所有类似以太网的网络接口是必需的。强烈建议用于所有类似以太网的网络接口。”
GROUP etherRateControlGroup DESCRIPTION "This group is mandatory for all ethernet-like network interfaces which are capable of operating at speeds faster than 1000 Mb/s. It is highly recommended for all ethernet-like network interfaces."
GROUP EtherRate ControlGroup DESCRIPTION“此组对于能够以1000 Mb/s以上的速度运行的所有类似以太网的网络接口都是必需的。强烈建议将其用于所有类似以太网的网络接口。”
GROUP etherStatsLowSpeedGroup DESCRIPTION "This group is mandatory for all ethernet-like network interfaces which are capable of operating at 10 Mb/s or slower in half-duplex mode."
GROUP EtherstStatsLowSpeedGroup DESCRIPTION“此组对于所有能够在半双工模式下以10 Mb/s或更低速度运行的类似以太网的网络接口是必需的。”
GROUP etherStatsHighSpeedGroup DESCRIPTION "This group is mandatory for all ethernet-like network interfaces which are capable of operating at 100 Mb/s or faster."
GROUP EtherstStatsHighSpeedGroup DESCRIPTION“对于能够以100 Mb/s或更快速度运行的所有类似以太网的网络接口，此组是必需的。”
GROUP etherStatsHalfDuplexGroup DESCRIPTION "This group is mandatory for all ethernet-like network interfaces which are
组EtherstStatsHalfDuplexGroup DESCRIPTION“此组对于所有类似以太网的网络接口都是必需的，这些接口是
capable of operating in half-duplex mode."
能够在半双工模式下运行。”
GROUP etherHCStatsGroup DESCRIPTION "This group is mandatory for all ethernet-like network interfaces which are capable of operating at 10 Gb/s or faster. It is recommended for all ethernet-like network interfaces which are capable of operating at 1000 Mb/s or faster."
GROUP etherHCStatsGroup DESCRIPTION“对于能够以10 Gb/s或更快速度运行的所有类似以太网的网络接口，此组是必需的。对于能够以1000 Mb/s或更快速度运行的所有类似以太网的网络接口，建议使用此组。”
GROUP etherControlGroup DESCRIPTION "This group is mandatory for all ethernet-like network interfaces that support the MAC Control sublayer."
GROUP etherControlGroup DESCRIPTION“此组对于支持MAC控制子层的所有类似以太网的网络接口都是必需的。”
GROUP etherHCControlGroup DESCRIPTION "This group is mandatory for all ethernet-like network interfaces that support the MAC Control sublayer and are capable of operating at 10 Gb/s or faster."
GROUP etherHCControlGroup DESCRIPTION“对于支持MAC控制子层且能够以10 Gb/s或更快速度运行的所有类似以太网的网络接口，此组是必需的。”
GROUP etherControlPauseGroup DESCRIPTION "This group is mandatory for all ethernet-like network interfaces that support the MAC Control PAUSE function."
GROUP etherControlPauseGroup DESCRIPTION“此组对于支持MAC控制暂停功能的所有类似以太网的网络接口都是必需的。”
GROUP etherHCControlPauseGroup DESCRIPTION "This group is mandatory for all ethernet-like network interfaces that support the MAC Control PAUSE function and are capable of operating at 10 Gb/s or faster."
GROUP etherHCControlPauseGroup DESCRIPTION“对于支持MAC控制暂停功能且能够以10 Gb/s或更快速度运行的所有类似以太网的网络接口，此组是必需的。”
GROUP etherCollisionTableGroup
DESCRIPTION "This group is optional. It is appropriate
for all ethernet-like network interfaces
which are capable of operating in
half-duplex mode and have the necessary
metering. Implementation in systems with
such interfaces is highly recommended."
::= { etherCompliances 4 }
GROUP etherCollisionTableGroup
DESCRIPTION "This group is optional. It is appropriate
for all ethernet-like network interfaces
which are capable of operating in
half-duplex mode and have the necessary
metering. Implementation in systems with
such interfaces is highly recommended."
::= { etherCompliances 4 }
-- units of conformance
--一致性单位
etherStatsGroup OBJECT-GROUP OBJECTS { dot3StatsIndex, dot3StatsAlignmentErrors, dot3StatsFCSErrors,
EtherstStatsGroup对象组对象{dot3StatsIndex，dot3StatsAlignmentErrors，dot3StatsSerrors，
dot3StatsSingleCollisionFrames,
dot3StatsMultipleCollisionFrames,
dot3StatsSQETestErrors,
dot3StatsDeferredTransmissions,
dot3StatsLateCollisions,
dot3StatsExcessiveCollisions,
dot3StatsInternalMacTransmitErrors,
dot3StatsCarrierSenseErrors,
dot3StatsFrameTooLongs,
dot3StatsInternalMacReceiveErrors,
dot3StatsEtherChipSet
}
STATUS deprecated
DESCRIPTION "********* THIS GROUP IS DEPRECATED **********
dot3StatsSingleCollisionFrames,
dot3StatsMultipleCollisionFrames,
dot3StatsSQETestErrors,
dot3StatsDeferredTransmissions,
dot3StatsLateCollisions,
dot3StatsExcessiveCollisions,
dot3StatsInternalMacTransmitErrors,
dot3StatsCarrierSenseErrors,
dot3StatsFrameTooLongs,
dot3StatsInternalMacReceiveErrors,
dot3StatsEtherChipSet
}
STATUS deprecated
DESCRIPTION "********* THIS GROUP IS DEPRECATED **********
A collection of objects providing information applicable to all ethernet-like network interfaces.
提供适用于所有类似以太网的网络接口的信息的对象集合。
This object group has been deprecated and
replaced by etherStatsBaseGroup and
etherStatsLowSpeedGroup."
::= { etherGroups 1 }
This object group has been deprecated and
replaced by etherStatsBaseGroup and
etherStatsLowSpeedGroup."
::= { etherGroups 1 }
etherCollisionTableGroup OBJECT-GROUP
OBJECTS { dot3CollFrequencies
}
STATUS current
DESCRIPTION "A collection of objects providing a histogram
of packets successfully transmitted after
experiencing exactly N collisions."
::= { etherGroups 2 }
etherCollisionTableGroup OBJECT-GROUP
OBJECTS { dot3CollFrequencies
}
STATUS current
DESCRIPTION "A collection of objects providing a histogram
of packets successfully transmitted after
experiencing exactly N collisions."
::= { etherGroups 2 }
etherStats100MbsGroup OBJECT-GROUP OBJECTS { dot3StatsIndex, dot3StatsAlignmentErrors, dot3StatsFCSErrors, dot3StatsSingleCollisionFrames, dot3StatsMultipleCollisionFrames, dot3StatsDeferredTransmissions, dot3StatsLateCollisions, dot3StatsExcessiveCollisions, dot3StatsInternalMacTransmitErrors, dot3StatsCarrierSenseErrors, dot3StatsFrameTooLongs, dot3StatsInternalMacReceiveErrors, dot3StatsEtherChipSet, dot3StatsSymbolErrors
EtherstStats100MBsgroup对象组对象{dot3StatsIndex，dot3StatsAlignmentErrors，Dot3StatsSerrors，dot3StatsSingleCollisionFrames，dot3StatsMultipleCollisionFrames，Dot3StatsFerredTransmission，Dot3StatsSlateCollisions，Dot3StatsAccessiveCollisions，Dot3StatsInInternalManactTransmisters，Dot3StatsCarriersensErrors，dot3StatsFrameTooLongs，Dot3StatsStatsInInternalAcreceiveErrors，Dot3Stats设置芯片组，dot3StatsSymbolErrors
}
STATUS deprecated
DESCRIPTION "********* THIS GROUP IS DEPRECATED **********
}
STATUS deprecated
DESCRIPTION "********* THIS GROUP IS DEPRECATED **********
A collection of objects providing information applicable to 100 Mb/sec ethernet-like network interfaces.
提供适用于100 Mb/s以太网类网络接口的信息的对象集合。
This object group has been deprecated and
replaced by etherStatsBaseGroup and
etherStatsHighSpeedGroup."
::= { etherGroups 3 }
This object group has been deprecated and
replaced by etherStatsBaseGroup and
etherStatsHighSpeedGroup."
::= { etherGroups 3 }
etherStatsBaseGroup OBJECT-GROUP
OBJECTS { dot3StatsIndex,
dot3StatsAlignmentErrors,
dot3StatsFCSErrors,
dot3StatsSingleCollisionFrames,
dot3StatsMultipleCollisionFrames,
dot3StatsDeferredTransmissions,
dot3StatsLateCollisions,
dot3StatsExcessiveCollisions,
dot3StatsInternalMacTransmitErrors,
dot3StatsCarrierSenseErrors,
dot3StatsFrameTooLongs,
dot3StatsInternalMacReceiveErrors
}
STATUS deprecated
DESCRIPTION "********* THIS GROUP IS DEPRECATED **********
etherStatsBaseGroup OBJECT-GROUP
OBJECTS { dot3StatsIndex,
dot3StatsAlignmentErrors,
dot3StatsFCSErrors,
dot3StatsSingleCollisionFrames,
dot3StatsMultipleCollisionFrames,
dot3StatsDeferredTransmissions,
dot3StatsLateCollisions,
dot3StatsExcessiveCollisions,
dot3StatsInternalMacTransmitErrors,
dot3StatsCarrierSenseErrors,
dot3StatsFrameTooLongs,
dot3StatsInternalMacReceiveErrors
}
STATUS deprecated
DESCRIPTION "********* THIS GROUP IS DEPRECATED **********
A collection of objects providing information applicable to all ethernet-like network interfaces.
提供适用于所有类似以太网的网络接口的信息的对象集合。
This object group has been deprecated and
replaced by etherStatsBaseGroup2 and
etherStatsHalfDuplexGroup, to separate
objects which must be implemented by all
ethernet-like network interfaces from
objects that need only be implemented on
ethernet-like network interfaces that are
capable of half-duplex operation."
::= { etherGroups 4 }
This object group has been deprecated and
replaced by etherStatsBaseGroup2 and
etherStatsHalfDuplexGroup, to separate
objects which must be implemented by all
ethernet-like network interfaces from
objects that need only be implemented on
ethernet-like network interfaces that are
capable of half-duplex operation."
::= { etherGroups 4 }
etherStatsLowSpeedGroup OBJECT-GROUP OBJECTS { dot3StatsSQETestErrors } STATUS current DESCRIPTION "A collection of objects providing information
EtherstStatsLowSpeedGroup对象组对象{dot3StatsQetestErrors}状态当前描述“提供信息的对象集合
applicable to ethernet-like network interfaces
capable of operating at 10 Mb/s or slower in
half-duplex mode."
::= { etherGroups 5 }
applicable to ethernet-like network interfaces
capable of operating at 10 Mb/s or slower in
half-duplex mode."
::= { etherGroups 5 }
etherStatsHighSpeedGroup OBJECT-GROUP
OBJECTS { dot3StatsSymbolErrors }
STATUS current
DESCRIPTION "A collection of objects providing information
applicable to ethernet-like network interfaces
capable of operating at 100 Mb/s or faster."
::= { etherGroups 6 }
etherStatsHighSpeedGroup OBJECT-GROUP
OBJECTS { dot3StatsSymbolErrors }
STATUS current
DESCRIPTION "A collection of objects providing information
applicable to ethernet-like network interfaces
capable of operating at 100 Mb/s or faster."
::= { etherGroups 6 }
etherDuplexGroup OBJECT-GROUP
OBJECTS { dot3StatsDuplexStatus }
STATUS current
DESCRIPTION "A collection of objects providing information
about the duplex mode of an ethernet-like
network interface."
::= { etherGroups 7 }
etherDuplexGroup OBJECT-GROUP
OBJECTS { dot3StatsDuplexStatus }
STATUS current
DESCRIPTION "A collection of objects providing information
about the duplex mode of an ethernet-like
network interface."
::= { etherGroups 7 }
etherControlGroup OBJECT-GROUP
OBJECTS { dot3ControlFunctionsSupported,
dot3ControlInUnknownOpcodes
}
STATUS current
DESCRIPTION "A collection of objects providing information
about the MAC Control sublayer on ethernet-like
network interfaces."
::= { etherGroups 8 }
etherControlGroup OBJECT-GROUP
OBJECTS { dot3ControlFunctionsSupported,
dot3ControlInUnknownOpcodes
}
STATUS current
DESCRIPTION "A collection of objects providing information
about the MAC Control sublayer on ethernet-like
network interfaces."
::= { etherGroups 8 }
etherControlPauseGroup OBJECT-GROUP
OBJECTS { dot3PauseAdminMode,
dot3PauseOperMode,
dot3InPauseFrames,
dot3OutPauseFrames
}
STATUS current
DESCRIPTION "A collection of objects providing information
about and control of the MAC Control PAUSE
function on ethernet-like network interfaces."
::= { etherGroups 9 }
etherControlPauseGroup OBJECT-GROUP
OBJECTS { dot3PauseAdminMode,
dot3PauseOperMode,
dot3InPauseFrames,
dot3OutPauseFrames
}
STATUS current
DESCRIPTION "A collection of objects providing information
about and control of the MAC Control PAUSE
function on ethernet-like network interfaces."
::= { etherGroups 9 }
etherStatsBaseGroup2 OBJECT-GROUP OBJECTS { dot3StatsIndex, dot3StatsAlignmentErrors, dot3StatsFCSErrors, dot3StatsInternalMacTransmitErrors,
EtherstStatsBaseGroup2对象组对象{dot3StatsIndex，dot3StatsAlignmentErrors，dot3StatsErrors，dot3StatsInternalActTransmitErrors，
dot3StatsFrameTooLongs,
dot3StatsInternalMacReceiveErrors
}
STATUS current
DESCRIPTION "A collection of objects providing information
applicable to all ethernet-like network
interfaces."
::= { etherGroups 10 }
dot3StatsFrameTooLongs,
dot3StatsInternalMacReceiveErrors
}
STATUS current
DESCRIPTION "A collection of objects providing information
applicable to all ethernet-like network
interfaces."
::= { etherGroups 10 }
etherStatsHalfDuplexGroup OBJECT-GROUP
OBJECTS { dot3StatsSingleCollisionFrames,
dot3StatsMultipleCollisionFrames,
dot3StatsDeferredTransmissions,
dot3StatsLateCollisions,
dot3StatsExcessiveCollisions,
dot3StatsCarrierSenseErrors
}
STATUS current
DESCRIPTION "A collection of objects providing information
applicable only to half-duplex ethernet-like
network interfaces."
::= { etherGroups 11 }
etherStatsHalfDuplexGroup OBJECT-GROUP
OBJECTS { dot3StatsSingleCollisionFrames,
dot3StatsMultipleCollisionFrames,
dot3StatsDeferredTransmissions,
dot3StatsLateCollisions,
dot3StatsExcessiveCollisions,
dot3StatsCarrierSenseErrors
}
STATUS current
DESCRIPTION "A collection of objects providing information
applicable only to half-duplex ethernet-like
network interfaces."
::= { etherGroups 11 }
etherHCStatsGroup OBJECT-GROUP
OBJECTS { dot3HCStatsAlignmentErrors,
dot3HCStatsFCSErrors,
dot3HCStatsInternalMacTransmitErrors,
dot3HCStatsFrameTooLongs,
dot3HCStatsInternalMacReceiveErrors,
dot3HCStatsSymbolErrors
}
STATUS current
DESCRIPTION "A collection of objects providing high-capacity
statistics applicable to higher-speed
ethernet-like network interfaces."
::= { etherGroups 12 }
etherHCStatsGroup OBJECT-GROUP
OBJECTS { dot3HCStatsAlignmentErrors,
dot3HCStatsFCSErrors,
dot3HCStatsInternalMacTransmitErrors,
dot3HCStatsFrameTooLongs,
dot3HCStatsInternalMacReceiveErrors,
dot3HCStatsSymbolErrors
}
STATUS current
DESCRIPTION "A collection of objects providing high-capacity
statistics applicable to higher-speed
ethernet-like network interfaces."
::= { etherGroups 12 }
etherHCControlGroup OBJECT-GROUP
OBJECTS { dot3HCControlInUnknownOpcodes }
STATUS current
DESCRIPTION "A collection of objects providing high-capacity
statistics for the MAC Control sublayer on
higher-speed ethernet-like network interfaces."
::= { etherGroups 13 }
etherHCControlGroup OBJECT-GROUP
OBJECTS { dot3HCControlInUnknownOpcodes }
STATUS current
DESCRIPTION "A collection of objects providing high-capacity
statistics for the MAC Control sublayer on
higher-speed ethernet-like network interfaces."
::= { etherGroups 13 }
etherHCControlPauseGroup OBJECT-GROUP OBJECTS { dot3HCInPauseFrames, dot3HCOutPauseFrames
etherHCControlPauseGroup对象组对象{dot3HCInPauseFrames，dot3HcCoutPauseFrames
}
STATUS current
DESCRIPTION "A collection of objects providing high-capacity
statistics for the MAC Control PAUSE function on
higher-speed ethernet-like network interfaces."
::= { etherGroups 14 }
}
STATUS current
DESCRIPTION "A collection of objects providing high-capacity
statistics for the MAC Control PAUSE function on
higher-speed ethernet-like network interfaces."
::= { etherGroups 14 }
etherRateControlGroup OBJECT-GROUP
OBJECTS { dot3StatsRateControlAbility,
dot3StatsRateControlStatus
}
STATUS current
DESCRIPTION "A collection of objects providing information
about the Rate Control function on ethernet-like
interfaces."
::= { etherGroups 15 }
etherRateControlGroup OBJECT-GROUP
OBJECTS { dot3StatsRateControlAbility,
dot3StatsRateControlStatus
}
STATUS current
DESCRIPTION "A collection of objects providing information
about the Rate Control function on ethernet-like
interfaces."
::= { etherGroups 15 }
END
终止
The IETF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be found in BCP-11. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementors or users of this specification can be obtained from the IETF Secretariat.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何努力来确定任何此类权利。有关IETF在标准跟踪和标准相关文件中权利的程序信息，请参见BCP-11。可从IETF秘书处获得可供发布的权利声明副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果。
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涉及实施本标准所需技术的专有权利。请将信息发送给IETF执行董事。
This document was produced by the IETF Ethernet Interfaces and Hub MIB Working Group, whose efforts were greatly advanced by the contributions of the following people:
本文件由IETF以太网接口和集线器MIB工作组编制，以下人员的贡献极大地推动了其工作：
Ran Atkinson Mike Ayers Mike Heard Jeffrey Johnson Lynn Kubinec Kam Lam Kerry McDonald Steve McRobert K.C. Norseth Dan Romascanu Randy Presuhn Andrew Smith Kaj Tesink Geoff Thompson
阿特金森·迈克·艾尔斯迈克听到杰弗里·约翰逊·林恩·库比内克·金林·克里·麦克唐纳、史蒂夫·麦克罗伯特·K.C·诺塞斯和罗马斯坎努·兰迪·普雷森、安德鲁·史密斯·卡伊·特辛·杰夫·汤普森
This document is based on the Proposed Standard Ethernet MIB, RFC 2665 [RFC2665], edited by John Flick of Hewlett-Packard and Jeffrey Johnson of RedBack Networks and produced by the Ethernet Interfaces and Hub MIB Working Group. It extends that document by providing support for 10 Gb/s Ethernet interfaces as defined in [IEEE802.3ae].
本文件基于拟议的标准以太网MIB RFC 2665[RFC2665]，由惠普的John Flick和RedBack Networks的Jeffrey Johnson编辑，由以太网接口和集线器MIB工作组编制。它通过支持[IEEE802.3ae]中定义的10 Gb/s以太网接口扩展了该文档。
RFC 2665, in turn, is based on the Proposed Standard Ethernet MIB, RFC 2358 [RFC2358], edited by John Flick of Hewlett-Packard and Jeffrey Johnson of RedBack Networks and produced by the 802.3 Hub MIB Working Group. It extends that document by providing support for full-duplex Ethernet interfaces and 1000 Mb/sec Ethernet interfaces as outlined in [IEEE802.3].
反过来，RFC 2665基于提议的标准以太网MIB RFC 2358[RFC2358]，由惠普的John Flick和RedBack Networks的Jeffrey Johnson编辑，由802.3集线器MIB工作组制作。它通过支持[IEEE802.3]中概述的全双工以太网接口和1000 Mb/s以太网接口扩展了该文档。
RFC 2358, in turn, is almost completely based on both the Standard Ethernet MIB, RFC 1643 [RFC1643], and the Proposed Standard Ethernet MIB using the SNMPv2 SMI, RFC 1650 [RFC1650], both of which were edited by Frank Kastenholz of FTP Software and produced by the Interfaces MIB Working Group. RFC 2358 extends those documents by providing support for 100 Mb/sec ethernet interfaces.
反过来，RFC 2358几乎完全基于标准以太网MIB RFC 1643[RFC1643]，以及使用SNMPv2 SMI RFC 1650[RFC1650]的拟议标准以太网MIB，两者均由FTP软件的Frank Kastenholz编辑，并由接口MIB工作组制作。RFC2358通过支持100MB/秒的以太网接口扩展了这些文档。
RFC 1643 and RFC 1650, in turn, are based on the Draft Standard Ethernet MIB, RFC 1398 [RFC1398], also edited by Frank Kastenholz and produced by the Ethernet MIB Working Group.
RFC 1643和RFC 1650依次基于标准以太网MIB草案RFC 1398[RFC1398]，也由Frank Kastenholz编辑并由以太网MIB工作组制作。
RFC 1398, in turn, is based on the Proposed Standard Ethernet MIB, RFC 1284 [RFC1284], which was edited by John Cook of Chipcom and produced by the Transmission MIB Working Group. The Ethernet MIB Working Group gathered implementation experience of the variables specified in RFC 1284, documented that experience in RFC 1369 [RFC1369], and used that information to develop this revised MIB.
反过来，RFC 1398基于提议的标准以太网MIB RFC 1284[RFC1284]，由Chipcom的John Cook编辑，并由传输MIB工作组制作。以太网MIB工作组收集了RFC 1284中规定的变量的实施经验，在RFC 1369[RFC1369]中记录了该经验，并使用该信息开发了该修订的MIB。
RFC 1284, in turn, is based on a document written by Frank Kastenholz, then of Interlan, entitled IEEE 802.3 Layer Management Draft M compatible MIB for TCP/IP Networks [KASTEN]. This document was modestly reworked, initially by the SNMP Working Group, and then by the Transmission Working Group, to reflect the current conventions for defining objects for MIB interfaces. James Davin, of the MIT Laboratory for Computer Science, and Keith McCloghrie of Hughes LAN Systems, contributed to later drafts of this memo. Marshall Rose of Performance Systems International, Inc. converted the document into RFC 1212 [RFC1212] concise format. Anil Rijsinghani of DEC contributed text that more adequately describes the TDR test. Thanks to Frank Kastenholz of Interlan and Louis Steinberg of IBM for their experimentation.
反过来，RFC1284基于当时Interlan的Frank Kastenholz编写的一份文件，名为IEEE 802.3层管理草案M兼容TCP/IP网络MIB[KASTEN]。该文档最初由SNMP工作组，然后由传输工作组进行了适当的修改，以反映定义MIB接口对象的当前约定。麻省理工学院计算机科学实验室的詹姆斯·戴文（James Davin）和休斯局域网系统（Hughes LAN Systems）的基思·麦克洛赫里（Keith McCloghrie）为这份备忘录的后续草稿做出了贡献。Performance Systems International，Inc.的Marshall Rose将该文件转换为RFC 1212[RFC1212]简明格式。DEC的Anil Rijsinghani提供了更充分地描述TDR测试的文本。感谢因特拉的弗兰克·卡斯滕霍尔茨和IBM的路易斯·斯坦伯格的实验。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirements Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2578]McCloghrie，K.，Perkins，D.，Schoenwaeld，J.，Case，J.，Rose，M.和S.Waldbusser，“管理信息的结构版本2（SMIv2）”，STD 58，RFC 2578，1999年4月。
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2579]McCloghrie，K.，Perkins，D.，Schoenwaeld，J.，Case，J.，Rose，M.和S.Waldbusser，“SMIv2的文本约定”，STD 58，RFC 2579，1999年4月。
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999.
[RFC2580]McCloghrie，K.，Perkins，D.，Schoenwaeld，J.，Case，J.，Rose，M.和S.Waldbusser，“SMIv2的一致性声明”，STD 58，RFC 25801999年4月。
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB using SMIv2", RFC 2863, June 2000.
[RFC2863]McCloghrie，K.和F.Kastenholz，“使用SMIv2的接口组MIB”，RFC 28632000年6月。
[IEEE802.3] IEEE, IEEE Std 802.3, 2002 Edition: "Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications", March 2002.
[IEEE802.3]IEEE，IEEE标准802.3，2002年版：“带冲突检测的载波侦听多址接入（CSMA/CD）接入方法和物理层规范”，2002年3月。
[IEEE802.3ae] IEEE, IEEE Std 802.3ae-2002, "Amendment: Media Access Control (MAC) Parameters, Physical Layers, and Management Parameters for 10 Gb/s Operation", August, 2002.
[IEEE802.3ae]IEEE，IEEE标准802.3ae-2002，“修改：10 Gb/s操作的媒体访问控制（MAC）参数、物理层和管理参数”，2002年8月。
[RFC3636] Flick, J., "Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) using SMIv2", RFC 3636, September 2003.
[RFC3636]Flick，J.，“使用SMIv2的IEEE 802.3介质连接单元（MAU）的托管对象定义”，RFC 3636，2003年9月。
[RFC1212] Rose, M. and K. McCloghrie, Editors, "Concise MIB Definitions", STD 16, RFC 1212, March 1991.
[RFC1212]Rose，M.和K.McCloghrie，编辑，“简明MIB定义”，STD 16，RFC 1212，1991年3月。
[RFC1213] McCloghrie, K. and M. Rose, Editors, "Management Information Base for Network Management of TCP/IP-based internets: MIB-II", STD 17, RFC 1213, March 1991.
[RFC1213]McCloghrie，K.和M.Rose，编辑，“基于TCP/IP的互联网网络管理的管理信息库：MIB-II”，STD 17，RFC 1213，1991年3月。
[RFC1284] Cook, J., "Definitions of Managed Objects for Ethernet-Like Interface Types", RFC 1284, December 1991.
[RFC1284]Cook，J.，“类似以太网接口类型的托管对象定义”，RFC1284，1991年12月。
[RFC1369] Kastenholz, F., "Implementation Notes and Experience for The Internet Ethernet MIB", RFC 1369, October 1992.
[RFC1369]Kastenholz，F.，“互联网以太网MIB的实施说明和经验”，RFC1369，1992年10月。
[RFC1398] Kastenholz, F., "Definitions of Managed Objects for the Ethernet-like Interface Types", RFC 1398, January 1993.
[RFC1398]Kastenholz，F.，“类似以太网接口类型的托管对象定义”，RFC 1398，1993年1月。
[RFC1643] Kastenholz, F., "Definitions of Managed Objects for the Ethernet-like Interface Types", STD 50, RFC 1643, July 1994.
[RFC1643]Kastenholz，F.，“类似以太网接口类型的托管对象定义”，STD 50，RFC 1643，1994年7月。
[RFC1650] Kastenholz, F., "Definitions of Managed Objects for the Ethernet-like Interface Types using SMIv2", RFC 1650, August 1994.
[RFC1650]Kastenholz，F.，“使用SMIv2的类以太网接口类型的托管对象定义”，RFC1650，1994年8月。
[RFC2358] Flick, J. and J. Johnson, "Definitions of Managed Objects for the Ethernet-like Interface Types", RFC 2358, June 1998.
[RFC2358]Flick，J.和J.Johnson，“类似以太网接口类型的托管对象定义”，RFC 2358，1998年6月。
[RFC2665] Flick, J. and J. Johnson, "Definitions of Managed Objects for the Ethernet-like Interface Types", RFC 2665, August 1999.
[RFC2665]Flick，J.和J.Johnson，“类似以太网接口类型的托管对象定义”，RFC 2665，1999年8月。
[RFC2666] Flick, J., "Definitions of Object Identifiers for Identifying Ethernet Chip Sets", RFC 2666, August 1999.
[RFC2666]Flick，J.，“识别以太网芯片组的对象标识符的定义”，RFC 2666，1999年8月。
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction and Applicability Statements for Internet-Standard Network Management Framework", RFC 3410, December 2002.
[RFC3410]Case，J.，Mundy，R.，Partain，D.和B.Stewart，“互联网标准网络管理框架的介绍和适用性声明”，RFC 34102002年12月。
[CASE] Case, J., and C. Partridge, "Case Diagrams: A First Step to Diagrammed Management Information Bases", Computer Communications Review, 19(1):13-16, January 1989.
[案例]CASE，J.和C.Partridge，“案例图：绘制管理信息库的第一步”，计算机通信评论，19（1）：13-161989年1月。
[RFC3637] Heard, C., "Definitions of Managed Objects for the Ethernet WAN Interface Sublayer", RFC 3637, September 2003.
[RFC3637]Heard，C.，“以太网WAN接口子层受管对象的定义”，RFC 3637，2003年9月。
[KASTEN] Kastenholz, F., "IEEE 802.3 Layer Management Draft compatible MIB for TCP/IP Networks", electronic mail message to mib-wg@nnsc.nsf.net, 9 June 1989.
[KASTEN]Kastenholz，F.，“适用于TCP/IP网络的IEEE 802.3层管理草案兼容MIB”，发送至MIB的电子邮件-wg@nnsc.nsf.net，1989年6月9日。
There is one management object defined in this MIB that has a MAX-ACCESS clause of read-write. That object, dot3PauseAdminMode, may be used to change the flow control configuration on a network interface, which may result in dropped packets, or sending flow control packets on links where the link partner will not understand them. Either action could be detrimental to network performance.
此MIB中定义了一个管理对象，该对象具有读写的MAX-ACCESS子句。该对象dot3PauseAdminMode可用于更改网络接口上的流量控制配置，这可能导致数据包丢失，或在链路伙伴无法理解的链路上发送流量控制数据包。这两种操作都可能对网络性能有害。
Such objects may be considered sensitive or vulnerable in some network environments. The support for SET operations in a non-secure environment without proper protection can have a negative effect on network operations.
在某些网络环境中，此类对象可能被视为敏感或易受攻击。在没有适当保护的非安全环境中支持SET操作可能会对网络操作产生负面影响。
Some of the readable objects in this MIB module (i.e., objects with a MAX-ACCESS other than not-accessible) may be considered sensitive or vulnerable in some network environments. In particular, the dot3StatsEtherChipSet object may be considered sensitive in many environments, since it would allow an intruder to obtain information about which vendor's equipment is in use on the network. Note that this object has been deprecated. However, some implementors may still choose to implement it for backwards compatability.
在某些网络环境中，此MIB模块中的某些可读对象（即具有MAX-ACCESS而非not ACCESS的对象）可能被视为敏感或易受攻击。特别是，Dot3StateSetherChipset对象在许多环境中可能被视为敏感对象，因为它允许入侵者获取有关网络上使用的供应商设备的信息。请注意，此对象已被弃用。然而，一些实现者可能仍然选择实现它以实现向后兼容性。
Most of the objects in this MIB module contain statistical information about particular network links. In some network environments, this information may be considered sensitive.
此MIB模块中的大多数对象包含有关特定网络链接的统计信息。在某些网络环境中，此信息可能被视为敏感信息。
It is thus important to control even GET and/or NOTIFY access to these objects and possibly to even encrypt the values of these objects when sending them over the network via SNMP.
因此，在通过SNMP通过网络发送这些对象时，控制甚至获取和/或通知对这些对象的访问，甚至可能加密这些对象的值，这一点非常重要。
SNMP versions prior to SNMPv3 did not include adequate security. Even if the network itself is secure (for example by using IPSec), even then, there is no control as to who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in this MIB module.
SNMPv3之前的SNMP版本未包含足够的安全性。即使网络本身是安全的（例如通过使用IPSec），即使如此，也无法控制安全网络上的谁可以访问和获取/设置（读取/更改/创建/删除）此MIB模块中的对象。
It is recommended that the implementors consider the security features as provided by the SNMPv3 framework (see [RFC3410], section 8), including full support for the SNMPv3 cryptographic mechanisms (for authentication and privacy).
建议执行者考虑SNMPv3框架提供的安全特性（参见[RCFC310]，第8节），包括对SNMPv3加密机制的完全支持（用于身份验证和隐私）。
Furthermore, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic security. It is then a customer/operator responsibility to ensure that the SNMP entity giving access to an instance of this MIB module is properly configured to give access to the objects only to those principals (users) that have legitimate rights to indeed GET or SET (change/create/delete) them.
此外，不建议部署SNMPv3之前的SNMP版本。相反，建议部署SNMPv3并启用加密安全性。然后，客户/运营商应负责确保授予访问此MIB模块实例权限的SNMP实体已正确配置为仅授予那些拥有确实获取或设置（更改/创建/删除）对象的合法权限的主体（用户）访问对象。
This document does not define any new name space to be administered by IANA. However, section 3.2.4 does specify that some of the defined values in a current IANA-maintained name space are to be marked as deprecated or obsolete. In particular, the following enumerated values in the IANAifType TEXTUAL-CONVENTION in the IANAifType-MIB module have had an ASN.1 comment added by IANA stating that they have been deprecated:
本文档未定义IANA管理的任何新名称空间。但是，第3.2.4节确实规定，当前IANA维护的名称空间中的某些定义值将标记为不推荐使用或过时。特别是，IANAifType MIB模块中IANAifType TEXTICAL-CONVENTION中的以下枚举值已由IANA添加ASN.1注释，说明它们已被弃用：
- iso88032Csmacd(7) - starLan(11)
- iso88032Csmacd（7）-starLan（11）
In addition, the following enumerated values have had an ASN.1 comment added by IANA stating that they are obsolete:
此外，IANA还添加了一条ASN.1注释，说明下列枚举值已过时：
- fastEther(62) - fastEtherFX(69) - gigabitEthernet(117)
- FastEthernet（62）-FastEthernerFX（69）-千兆以太网（117）
In all of the above cases, the ASN.1 comment indicates that ethernetCsmacd(6) should be used instead of these values.
在上述所有情况下，ASN.1注释表明应使用ethernetCsmacd（6）而不是这些值。
A. Change Log
A.更改日志
This section enumerates changes made to RFC 2665 to produce this document.
本节列举了为编制本文件而对RFC 2665所做的更改。
(1) Updated references to the IEEE 802.3 standard to refer to the 2002 edition.
(1) 更新了对IEEE 802.3标准的参考，以参考2002年版。
(2) Added reference to IEEE 802.3ae-2002.
(2) 增加了对IEEE 802.3ae-2002的参考。
(3) Updated WG e-mail address.
(3) 更新的工作组电子邮件地址。
(4) The following DESCRIPTION clauses have been updated to reflect behaviour on 10 Gb/s interfaces: dot3StatsAlignmentErrors and dot3StatsSymbolErrors.
(4) 以下描述子句已更新，以反映10 Gb/s接口上的行为：dot3StatsAlignmentErrors和dot3StatsSymbolErrors。
(5) The following objects have been added for management of the Rate Control function in WAN applications of ethernet: dot3StatsRateControlAbility and dot3StatsRateControlStatus.
(5) 为管理以太网广域网应用中的速率控制功能，添加了以下对象：dot3StatsRateControlAbility和dot3StatsRateControlStatus。
(6) The following 64-bit counters have been added to support operation on high-speed ethernet interfaces: dot3HCControlInUnknownOpcodes, dot3HCInPauseFrames, dot3HCOutPauseFrames, dot3HCStatsAlignmentErrors, dot3HCStatsFCSErrors, dot3HCStatsFrameTooLongs, dot3HCStatsInternalMacTransmitErrors, dot3HCStatsInternalMacReceiveErrors, dot3HCStatsSymbolErrors
(6) 已添加以下64位计数器以支持在高速以太网接口上的操作：Dot3HControlinUnknowNopCodes、dot3HCInPauseFrames、Dot3HCStatsSaligmentErrors、Dot3HCStatsSerrors、Dot3HCStatsFrameToolLongs、Dot3HCStatsInternalActTransmitErrors、dot3HCStatsInternalMacReceiveErrors、，dot3HCStatsSymbolErrors
(7) Object groups and compliances have been added to contain the new objects.
(7) 已添加对象组和符合性以包含新对象。
(8) The MODULE-IDENTITY clause has been updated to reflect the changes in the MIB module.
(8) MODULE-IDENTITY子句已更新，以反映MIB模块中的更改。
(9) Use of the various ifType values for ethernet has been clarified to emphasize that all ethernet-like interfaces must use the ethernetCsmacd ifType.
(9) 以太网的各种ifType值的使用已得到澄清，以强调所有类似以太网的接口必须使用ethernetCsmacd ifType。
(10) Several clarifications were made to the section on the mapping of the Interface MIB objects to ethernet.
（10） 对接口MIB对象到以太网的映射部分进行了一些澄清。
(11) MIB boilerplate in section 2 has been updated to the latest approved text.
（11） 第2节中的MIB样板已更新为最新批准文本。
This section enumerates changes made to RFC 2358 to produce RFC 2665.
本节列举了为生成RFC 2665而对RFC 2358所做的更改。
(1) Section 2 has been replaced with the current SNMP Management Framework boilerplate.
(1) 第2节已替换为当前的SNMP管理框架样板。
(2) The ifMtu mapping has been clarified.
(2) ifMtu映射已得到澄清。
(3) The relationship between the IEEE 802.3 octet counters and the IF-MIB octet counters has been clarified.
(3) IEEE 802.3八位字节计数器和IF-MIB八位字节计数器之间的关系已经澄清。
(4) REFERENCE clauses have been updated to reflect the actual IEEE 802.3 managed object that each MIB object is based on.
(4) 参考条款已更新，以反映每个MIB对象所基于的实际IEEE 802.3托管对象。
(5) The following object DESCRIPTION clauses have been updated to reflect that they do not increment in full-duplex mode: dot3StatsSingleCollisionFrames, dot3StatsMultipleCollisionFrames, dot3StatsSQETestErrors, dot3StatsDeferredTransmissions, dot3StatsLateCollisions, dot3StatsExcessiveCollisions, dot3StatsCarrierSenseErrors, dot3CollFrequencies.
(5) 以下对象描述子句已更新，以反映它们在全双工模式下不会递增：dot3StatsSingleCollisionFrames、dot3StatsMultipleCollisionFrames、dot3StatsQetesterrors、dot3StatsFerredTransmissions、dot3StatsSlateCollisions、dot3StatsAccessiveCollisions、dot3StatsCarrierSenseErrors、dot3Collections。
(6) The following object DESCRIPTION clauses have been updated to reflect behaviour on full-duplex and 1000 Mb/s interfaces: dot3StatsAlignmentErrors, dot3StatsFCSErrors, dot3StatsSQETestErrors, dot3StatsLateCollisions, dot3StatsSymbolErrors.
(6) 以下对象描述子句已更新，以反映全双工和1000 Mb/s接口上的行为：dot3StatsAlignmentErrors、DOT3STATSFSCSERRORS、DOT3STATSQETERRORS、DOT3STATSSLATECLINSIONS、dot3StatsSymbolErrors。
(7) Two new tables, dot3ControlTable and dot3PauseTable, have been added.
(7) 添加了两个新表：dot3ControlTable和DOT3AUSETABLE。
(8) A new object, dot3StatsDuplexStatus, has been added.
(8) 添加了一个新对象dot3StatsDuplexStatus。
(9) The object groups and compliances have been restructured.
(9) 对象组和合规性已重新调整。
(10) The dot3StatsEtherChipSet object has been deprecated.
（10） Dot3StateSetherChipset对象已被弃用。
(11) The dot3ChipSets have been moved to a separate document.
（11） Dot3Chipset已移动到单独的文档中。
This section enumerates changes made to RFC 1650 to produce RFC 2358.
本节列举了为生成RFC 2358而对RFC 1650所做的更改。
(1) The MODULE-IDENTITY has been updated to reflect the changes in the MIB.
(1) 模块标识已更新，以反映MIB中的更改。
(2) A new object, dot3StatsSymbolErrors, has been added.
(2) 添加了一个新对象dot3StatssSymbolErrors。
(3) The definition of the object dot3StatsIndex has been converted to use the SMIv2 OBJECT-TYPE macro.
(3) 对象dot3StatsIndex的定义已转换为使用SMIv2对象类型宏。
(4) A new conformance group, etherStats100MbsGroup, has been added.
(4) 添加了一个新的一致性组EtherstStats100MBsgroup。
(5) A new compliance statement, ether100MbsCompliance, has been added.
(5) 添加了新的合规性声明Ether100MBCompliance。
(6) The Acknowledgements were extended to provide a more complete history of the origin of this document.
(6) 对确认书进行了扩展，以提供本文件来源的更完整历史。
(7) The discussion of ifType has been expanded.
(7) 关于ifType的讨论已经展开。
(8) A section on mapping of Interfaces MIB objects has been added.
(8) 增加了一个关于接口MIB对象映射的部分。
(9) A section defining the relationship of this MIB to the MAU MIB has been added.
(9) 已添加定义此MIB与MAU MIB关系的部分。
(10) A section on the mapping of IEEE 802.3 managed objects to this MIB and the Interfaces MIB has been added.
（10） 增加了一节，介绍IEEE 802.3受管对象到该MIB和接口MIB的映射。
(11) Converted the dot3Tests, dot3Errors, and dot3ChipSets OIDs to use the OBJECT-IDENTITY macro.
（11） 已将dot3Tests、dot3Errors和dot3ChipSets OID转换为使用OBJECT-IDENTITY宏。
(12) Added to the list of registered dot3ChipSets.
（12） 已添加到已注册的Dot3Chipset列表中。
(13) An intellectual property notice and copyright notice were added, as required by RFC 2026.
（13） 根据RFC 2026的要求，增加了知识产权声明和版权声明。
Author's Address
作者地址
John Flick Hewlett-Packard Company 8000 Foothills Blvd. M/S 5557 Roseville, CA 95747-5557
约翰·弗利克惠普公司8000山麓大道。加利福尼亚州罗斯维尔市南5557号，邮编95747-5557
Phone: +1 916 785 4018
EMail: johnf@rose.hp.com
Phone: +1 916 785 4018
EMail: johnf@rose.hp.com
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (2003). All Rights Reserved.
版权所有（C）互联网协会（2003年）。版权所有。
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.
本文件及其译本可复制并提供给他人，对其进行评论或解释或协助其实施的衍生作品可全部或部分编制、复制、出版和分发，不受任何限制，前提是上述版权声明和本段包含在所有此类副本和衍生作品中。但是，不得以任何方式修改本文件本身，例如删除版权通知或对互联网协会或其他互联网组织的引用，除非出于制定互联网标准的需要，在这种情况下，必须遵循互联网标准过程中定义的版权程序，或根据需要将其翻译成英语以外的其他语言。
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assignees.
上述授予的有限许可是永久性的，互联网协会或其继承人或受让人不会撤销。
This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。