Network Working Group J. Flick
Request for Comments: 2358 Hewlett-Packard Company
Obsoletes: 1650 J. Johnson
Category: Standards Track RedBack Networks
June 1998
Network Working Group J. Flick
Request for Comments: 2358 Hewlett-Packard Company
Obsoletes: 1650 J. Johnson
Category: Standards Track RedBack Networks
June 1998
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 (1998). All Rights Reserved.
版权所有（C）互联网协会（1998年）。版权所有。
Abstract
摘要
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. This memo obsoletes RFC 1650 "Definitions of Managed Objects for the Ethernet-like Interface Types using SMIv2". This memo extends that specification by including management information useful for the management of 100 Mb/s Ethernet interfaces.
此备忘录定义了管理信息库（MIB）的一部分，用于Internet社区中的网络管理协议。本备忘录废除了RFC 1650“使用SMIv2的类以太网接口类型的托管对象定义”。本备忘录扩展了该规范，包括了对管理100 Mb/s以太网接口有用的管理信息。
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, reflect 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工作组可能会修订本文件，或发布新的文件，以反映以太网技术的发展。
Table of Contents
目录
1. Introduction ................................................ 2
2. The SNMP Network Management Framework ...................... 2
2.1. Object Definitions ....................................... 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. ifTestTable ............................................ 5
3.2.4. ifRcvAddressTable ...................................... 5
3.2.5. ifPhysAddress .......................................... 5
3.2.6. ifType ................................................. 6
3.2.7. Specific Interface MIB Objects ......................... 7
3.3. Relation to the 802.3 MAU MIB ............................ 10
3.4. Mapping of IEEE 802.3 Managed Objects .................... 10
4. Definitions ................................................ 11
5. Intellectual Property ...................................... 34
6. Acknowledgements ........................................... 34
7. References ................................................. 35
8. Security Considerations .................................... 36
9. Authors' Addresses ......................................... 37
A. Change Log ................................................. 38
B. Full Copyright Statement ................................... 39
1. Introduction ................................................ 2
2. The SNMP Network Management Framework ...................... 2
2.1. Object Definitions ....................................... 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. ifTestTable ............................................ 5
3.2.4. ifRcvAddressTable ...................................... 5
3.2.5. ifPhysAddress .......................................... 5
3.2.6. ifType ................................................. 6
3.2.7. Specific Interface MIB Objects ......................... 7
3.3. Relation to the 802.3 MAU MIB ............................ 10
3.4. Mapping of IEEE 802.3 Managed Objects .................... 10
4. Definitions ................................................ 11
5. Intellectual Property ...................................... 34
6. Acknowledgements ........................................... 34
7. References ................................................. 35
8. Security Considerations .................................... 36
9. Authors' Addresses ......................................... 37
A. Change Log ................................................. 38
B. Full Copyright Statement ................................... 39
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 extends the list of managed objects specified in the earlier version of this MIB: RFC1650 [11].
此备忘录还包括一个MIB模块。此MIB模块扩展了此MIB早期版本中指定的托管对象列表：RFC1650[11]。
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 [13].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照[13]中所述进行解释。
The SNMP Network Management Framework consists of several components. For the purpose of this specification, the applicable components of the Framework are the SMI and related documents [2, 3, 4], which define the mechanisms used for describing and naming objects for the purpose of management.
SNMP网络管理框架由几个组件组成。在本规范中，框架的适用组件为SMI和相关文件[2,3,4]，这些文件定义了用于描述和命名对象以进行管理的机制。
The Framework permits new objects to be defined for the purpose of experimentation and evaluation.
该框架允许为实验和评估目的定义新对象。
Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the subset of Abstract Syntax Notation One (ASN.1) [1] defined in the SMI [2]. In particular, each object object type is named by an OBJECT IDENTIFIER, an administratively assigned name. The object type together with an object instance serves to uniquely identify a specific instantiation of the object. For human convenience, we often use a textual string, termed the descriptor, to refer to the object type.
托管对象通过虚拟信息存储（称为管理信息库或MIB）进行访问。MIB中的对象是使用SMI[2]中定义的抽象语法表示法1（ASN.1）[1]的子集定义的。特别是，每个对象类型都由一个对象标识符命名，这是一个管理分配的名称。对象类型与对象实例一起用于唯一标识对象的特定实例化。为了方便起见，我们经常使用一个称为描述符的文本字符串来引用对象类型。
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 following values of the ifType object in the Interfaces MIB [12]:
这些对象类型的实例表示类以太网通信介质接口的属性。目前，类以太网介质由接口MIB[12]中ifType对象的以下值标识：
ethernetCsmacd(6) iso88023Csmacd(7) starLan(11)
ethernetCsmacd（6）iso88023Csmacd（7）starLan（11）
The definitions presented here are based on the IEEE 802.3 Layer Management Specification [5], as originally interpreted by Frank Kastenholz then of Interlan in [7]. Implementors of these MIB objects should note that the IEEE document 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层管理规范[5]，最初由Interlan的Frank Kastenholz在[7]中解释。这些MIB对象的实现者应该注意，IEEE文档（以Pascal伪代码的形式）明确描述了测量各种MAC属性的时间、地点和方式。IEEE文档还描述了MAC操作的效果，这些操作可通过操作此处定义的MIB对象实例来调用。
To the extent that some of the attributes defined in [5] are represented by previously defined objects in MIB-2 [16] or in the Interfaces MIB [12], 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.
如果[5]中定义的某些属性由MIB-2[16]或接口MIB[12]中先前定义的对象表示，则此类属性不会由本备忘录中定义的对象冗余表示。其他备忘录中定义的对象表示的属性包括在特定接口上传输或接收的八位字节数、在特定接口上传输或接收的帧数、接口的混杂状态、接口的MAC地址以及与接口相关联的多播信息。
This section applies only when this MIB is used in conjunction with the "old" (RFC 1213) [16] interface group.
仅当此MIB与“旧”（RFC 1213）[16]接口组一起使用时，本节才适用。
The relationship between an ethernet-like interface and an interface in the context of the Internet-standard MIB 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.
类似以太网的接口与Internet标准MIB上下文中的接口之间的关系是一对一的。因此，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 IDENTIFER ::= { transmission 7 }
dot3 OBJECT IDENTIFER ::= { transmission 7 }
The Interface MIB [12] 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[12]要求作为接口MIB附属的任何MIB澄清接口MIB内的特定区域。这些区域在接口MIB中故意保持模糊，以避免过度约束MIB，从而排除对某些媒体类型的管理。
Section 3.3 of [12] 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 [12] in order to understand the general intent of these areas.
[12]第3.3节列举了媒体特定MIB必须澄清的几个方面。以下小节将介绍这些领域中的每一个领域。为了理解这些领域的总体意图，请参考[12]。
This MIB does not provide for layering. There are no sublayers.
此MIB不提供分层。没有子层。
EDITOR'S NOTE:
编者按：
One could foresee the development of an 802.2 and enet-transceiver MIB. They could be higher and lower sublayers, respectively. All that THIS document should do is allude to the possibilities and urge the implementor to be aware of the possibility and that they may have requirements which supersede the requirements in this document.
人们可以预见802.2和enet收发器MIB的发展。它们可以分别是较高和较低的亚层。本文件所要做的只是提及可能性，并敦促实施者意识到这种可能性，他们可能有取代本文件要求的要求。
This medium does not support virtual circuits and this area is not applicable to this MIB.
此介质不支持虚拟电路，此区域不适用于此MIB。
This MIB defines two tests for media which are instrumented with this MIB; TDR and Loopback. Implementation of these tests is not required. Many common interface chips do not support one or both of these tests.
此MIB定义了使用此MIB检测的媒体的两个测试；TDR和环回。不需要执行这些测试。许多通用接口芯片不支持这两种测试中的一种或两种。
These two tests are provided as a convenience, allowing a common method to invoke the test.
提供这两个测试是为了方便起见，允许一个通用方法调用该测试。
Standard MIBs do not include objects in which to return the results of the TDR test. Any needed objects MUST be provided in the vendor specific MIB.
标准MIB不包括返回TDR测试结果的对象。必须在特定于供应商的MIB中提供所需的任何对象。
Note that the ifTestTable is now deprecated. Work is underway to define a replacement MIB for system and interface testing. It is expected that the tests defined in this document will be usable in this replacement MIB.
请注意，ifTestTable现在已弃用。为系统和接口测试定义替换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 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。
This MIB applies to interfaces which have any of the following ifType values:
此MIB适用于具有以下任一ifType值的接口：
ethernetCsmacd(6) iso88023Csmacd(7) starLan(11)
ethernetCsmacd（6）iso88023Csmacd（7）starLan（11）
It is RECOMMENDED 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. iso88023Csmacd(7) and starLan(11) are supported for backwards compatability.
建议所有类似以太网的接口使用ethernetCsmacd（6）的ifType，无论接口的运行速度或使用的链路层封装如何。支持iso88023Csmacd（7）和starLan（11）以实现向后兼容性。
There are two other interface types defined in the IANAifType-MIB for 100 Mbit Ethernet. They are fastEther(62), and fastEtherFX(69). This document takes the position that an Ethernet is an Ethernet, and Ethernet interfaces SHOULD always have the same value of 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. An Ethernet-like interface SHOULD NOT use the fastEther(62) or fastEtherFX(69) ifTypes.
IANAifType MIB中为100 Mbit以太网定义了另外两种接口类型。它们是fastEther（62）和fastEtherFX（69）。本文档认为以太网就是以太网，以太网接口应始终具有相同的ifType值。接口正在运行的以太网的特定风格的信息可从接口MIB中的ifSpeed和802.3 MAU MIB中的ifMauType获得。类似以太网的接口不应使用fastEther（62）或fastEtherFX（69）IFTYPE。
Interfaces with any of the supported ifType values map to the EtherLike-MIB in the same manner. Which compliance statement an interface should implement is dependent on the maximum speed supported on the interface. The EtherLike-MIB etherCompliance compliance statement applies to all Ethernet-like interfaces whose maximum supported speed is 10 Mbit/sec or less. There are no implementation differences. Similarly, the EtherLike-MIB ether100MbsCompliance compliance statement applies to all Ethernet-like interfaces whose maximum supported speed is 100Mbit/sec.
具有任何支持的ifType值的接口都以相同的方式映射到类以太MIB。接口应实现哪种符合性声明取决于接口支持的最大速度。EtherLike MIB etherCompliance声明适用于最大支持速度为10 Mbit/sec或更低的所有类似Ethernet的接口。没有实现差异。类似地，EtherLike MIB Ether100MBCompliance符合性声明适用于最大支持速度为100Mbit/sec的所有类似Ethernet的接口。
An interface that is capable of operating at 100Mbit/sec MUST implement the ether100MbsCompliance compliance statement, even if it is currently operating at a lower speed. Counters in the ether100MbsCompliance compliance statement that only apply to 100 Mbit interfaces would simply not increment when the interface is operating at a lower speed.
能够以100Mbit/sec速度运行的接口必须实现Ether100MbCompliance符合性声明，即使它当前以较低的速度运行。Ether100MBCompliance compliance声明中仅适用于100Mbit接口的计数器在接口以较低速度运行时不会增加。
The following table provides specific implementation guidelines for applying the interface group objects to ethernet-like media.
下表提供了将接口组对象应用于类似以太网的介质的具体实现指南。
Object
对象
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 [12].
如果需要，请参阅[12]。
ifType Refer to section 3.2.6.
如果类型相同，请参考第3.2.6节。
ifMtu 1500 octets.
ifMtu 1500八位字节。
ifSpeed The current operational speed of the interface in bits per second. For current ethernet-like interfaces, this will be equal to 1,000,000 (1 million), 10,000,000 (10 million), or 100,000,000 (100 million). If the interface implements auto-negotiation, auto-negotiation is enabled for this interface, and the interface has not yet negotiated to an operational speed, this object SHOULD reflect the maximum speed supported by the interface. Note that this 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 correct object to use to determine the duplex mode of the interface is the ifMauType object in the 802.3 MAU MIB.
ifSpeed接口的当前操作速度，单位为位/秒。对于当前类似以太网的接口，这将等于1000000（100万）、10000000（1000万）或100000000（1亿）。如果接口实现自动协商，则此接口已启用自动协商，且接口尚未协商到操作速度，则此对象应反映接口支持的最大速度。请注意，在全双工模式下操作时，此对象不得指示加倍值。无论当前的双工模式如何，它都必须指示正确的线路速度。用于确定接口双工模式的正确对象是802.3 MAU MIB中的ifMauType对象。
ifPhysAddress Refer to section 3.2.5.
如果需要，请参考第3.2.5节。
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 [12].
如需更改，请参阅[12]。
ifInOctets The number of octets in valid MAC frames received on this interface, including the MAC header and FCS.
ifInOctets在该接口上接收的有效MAC帧中的八位字节数，包括MAC报头和FCS。
ifInUcastPkts Refer to [12].
如需更多信息，请参阅[12]。
ifInDiscards Refer to [12].
如有指示，请参考[12]。
ifInErrors The sum for this interface of dot3StatsAlignmentErrors, dot3StatsFCSErrors, dot3StatsFrameTooLongs, dot3StatsInternalMacReceiveErrors and dot3StatsSymbolErrors.
IFINERROR此接口的dot3StatsAlignmentErrors、dot3StatsFCSErrors、DOT3STATSFRAMETOLONGS、DOT3STATSINTERNALMACERRORS和dot3StatsSymbolErrors之和。
ifInUnknownProtos Refer to [12].
如果不知道，请参考[12]。
ifOutOctets The number of octets transmitted in valid MAC frames on this interface, including the MAC header and FCS.
ifOutOctets：此接口上有效MAC帧中传输的八位字节数，包括MAC报头和FCS。
ifOutUcastPkts Refer to [12].
如有疑问，请参阅[12]。
ifOutDiscards Refer to [12].
ifOutDiscards参考[12]。
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 [12].
如需更多信息，请参阅[12]。
ifInBroadcastPkts Refer to [12].
IFINBROADCASTPKT参考[12]。
ifOutMulticastPkts Refer to [12].
IfoutMulticastPKT请参阅[12]。
ifOutBroadcastPkts Refer to [12].
IfoutBroadcastPKT参考[12]。
ifHCInOctets 64-bit versions of counters. Required ifHCOutOctets for ethernet-like interfaces that are capable of operating at 20Mbit/sec or faster, even if the interface is currently operating at less than 20Mbit/sec.
ifHCInOctets计数器的64位版本。对于能够以20Mbit/sec或更快速度运行的以太网类接口，即使该接口当前的运行速度小于20Mbit/sec，也需要ifHCOutOctets。
ifHCInUcastPkts 64-bit versions of packet counters. ifHCInMulticastPkts Support for these counters is not ifHCInBroadcastPkts required for the interface types ifHCOutUcastPkts supported by this MIB. They are only ifHCOutMulticastPkts required for interfaces capable of ifHCOutBroadcastPkts operating at 640Mbit/sec or faster. Note that a future revision of this document may support faster interfaces, and therefore may require support for these counters.
ifHCInUcastPkts 64位版本的数据包计数器。此MIB支持的接口类型ifHCOutUcastPkts不需要ifHCInBroadcastPkts支持这些计数器。对于能够以640Mbit/s或更高速度运行的IFHCoutBroadcastPKT接口，它们仅是所需的IFHCoutMulticastPKT。请注意，本文档的未来版本可能支持更快的接口，因此可能需要对这些计数器的支持。
ifLinkUpDownTrapEnable Refer to [12]. Default is 'enabled'
如果链接上下可删除，请参阅[12]。默认值为“已启用”
ifHighSpeed The current operational speed of the interface in millions of bits per second. For current ethernet-like interfaces, this will be equal to 1, 10, or 100. If the interface implements auto-negotiation, auto-negotiation is enabled for this interface, and the interface has not yet negotiated to an operational speed, this object SHOULD reflect the maximum speed supported by the interface. Note that this 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 correct object to use to determine the duplex mode of the interface is the ifMauType object in the 802.3 MAU MIB.
ifHighSpeed接口的当前操作速度，单位为百万位/秒。对于当前类似以太网的接口，这将等于1、10或100。如果接口实现自动协商，则此接口已启用自动协商，且接口尚未协商到操作速度，则此对象应反映接口支持的最大速度。请注意，在全双工模式下操作时，此对象不得指示加倍值。无论当前的双工模式如何，它都必须指示正确的线路速度。用于确定接口双工模式的正确对象是802.3 MAU MIB中的ifMauType对象。
ifPromiscuousMode Refer to [12].
如果是混杂模式，请参阅[12]。
ifConnectorPresent This will normally be 'true'.
如果ConnectorPresent，则通常为“true”。
ifAlias Refer to [12].
如果需要，请参考[12]。
ifCounterDiscontinuityTime Refer to [12].
如果需要，请参阅[12]。
ifStackHigherLayer Refer to section 3.2.1. ifStackLowerLayer ifStackStatus
如果是StackHigherLayer，请参考第3.2.1节。ifStackLowerLayer ifStackStatus
ifRcvAddressAddress Refer to section 3.2.4. ifRcvAddressStatus ifRcvAddressType
ifRcvAddressAddress参考第3.2.4节。IFRCVAddress状态IFRCVAddress类型
Support for the mauModIfCompl compliance statement of the MAU-MIB [14] 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. The MAU type indicates not only the media type in use, but also indicates whether the interface is operating in half-duplex or full-duplex mode. Implementing this MIB module without implementing the MAU-MIB would leave applications with no standard way to determine the duplex mode of the interface.
类以太网接口需要支持MAU-MIB[14]的mauModIfCompl合规性声明。需要此MIB以允许应用程序确定接口使用的当前MAU类型。MAU类型不仅指示正在使用的媒体类型，还指示接口是在半双工还是全双工模式下运行。在不实现MAU-MIB的情况下实现此MIB模块将使应用程序无法确定接口的双工模式。
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
oMacEntity.aMACID dot3StatsIndex或IF-MIB-iIndex.aframestransmitteddok IF-MIB-ifoutucastkts+ifOutMulticastPkts+ifOutBroadcastPkts.asingcollisionframes dot3statsinglecollisionframes.aMultipleCollisionFrames dot3StatsMultipleCollisionFrames.aFramesReceivedOK IF-MIB-ifinucstpkts+ifInMulticastPkts+ifinbriadcastpkts+ifInBroadcastPkts.aFrameCheckSequenceErrors Dot3StatsSerrors.AA校准错误dot3StatsAlignmentErrors.AOCTetStratsMitteDok IF-MIB-ifOutOctets.aFramesWithDeferredXmissions Dot3StatsFerredTransmissions.aLateCollisions Dot3StatsCollisions.AFramesbortedDuetToCalls Dot3StatsAccessiveCollisions.AFramesDot3sAccessiveCollisions.AFramesLostDuetToEntMacXmiterDOT3状态内部实际传输错误。ACARIERSENSEERRORS DOT3状态内部实际传输错误。AOCTETS接收到OK IF-MIB-IFINOCETS。因INTMARCVERROR DOT3STATINSINTERNALMACRECEIVEERRORS而导致的帧。一个预先状态IF-MIB-IFPROMISCUUSMODE。区域多播地址列表IF-MIB-IFRCVADDRESTABLE。一个多播帧指定的IF-MIB-IFOUTPKTS.AbroadCastFramesXmitedok IF-MIB-ifOutBroadcastPkts
.aMulticastFramesReceivedOK IF-MIB - ifInMulticastPkts .aBroadcastFramesReceivedOK IF-MIB - ifInBroadcastPkts .aFrameTooLongErrors dot3StatsFrameTooLongs .aReadWriteMACAddress IF-MIB - ifPhysAddress .aCollisionFrames dot3CollFrequencies .acAddGroupAddress IF-MIB - ifRcvAddressTable .acDeleteGroupAddress IF-MIB - ifRcvAddressTable .acExecuteSelfTest dot3TestLoopBack
.aMulticastFramesReceivedOK IF-MIB-ifInMulticastPkts.aBroadcastFramesReceivedOK IF-MIB-ifInBroadcastPkts.aFrameToolLongErrors点3StatsFrameToolLongs.aReadWriteMACAddress IF-MIB-ifPhysAddress.aCollisionFrames点3Collections.AcadGroupAddress IF-MIB-IFRCvaAddressTable.acDeleteGroupAddress IF-MIB-IFRCvaAddressTable.acExecuteSelfTest dot3TestLoopBack
oPHYEntity .aSQETestErrors dot3StatsSQETestErrors .aSymbolErrorDuringCarrier dot3StatsSymbolErrors
oPHYEntity.aSQETestErrors dot3StatsSQETestErrors.aSymbolErrorDuringCarrier dot3statsssymbolerrors
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 [15] for the detailed reasoning on why these objects were removed.
有关移除这些对象的详细原因，请参见[15]。
EtherLike-MIB DEFINITIONS ::= BEGIN
EtherLike-MIB DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY, Counter32, mib-2, transmission FROM SNMPv2-SMI MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF ifIndex, InterfaceIndex FROM IF-MIB;
导入模块标识、对象类型、对象标识、计数器32、mib-2、来自SNMPv2 SMI模块的传输、来自SNMPv2 CONF ifIndex的对象组、来自IF-mib的接口索引；
etherMIB MODULE-IDENTITY LAST-UPDATED "9806032150Z" -- June 3, 1998 ORGANIZATION "IETF 802.3 Hub MIB Working Group" CONTACT-INFO "WG E-mail: hubmib@hprnd.rose.hp.com To subscribe: hubmib-request@hprnd.rose.hp.com
etherMIB模块标识最后更新的“9806032150Z”-1998年6月3日组织“IETF 802.3集线器MIB工作组”联系信息工作组电子邮件：hubmib@hprnd.rose.hp.com订阅：hubmib-request@hprnd.rose.hp.com
Chair: Dan Romascanu Postal: LANNET Ltd. Atidum Technology Park, Bldg. 3 Tel Aviv 61131 Israel Tel: +972 3 645 8414 E-mail: dromasca@lannet.com
主席：Dan Romascanu邮政：LANNET Ltd.Atidum科技园特拉维夫3号楼61131以色列电话：+972 3 645 8414电子邮件：dromasca@lannet.com
Editor: John Flick Postal: Hewlett-Packard Company 8000 Foothills Blvd. M/S 5556 Roseville, CA 95747-5556 USA Tel: +1 916 785 4018 Fax: +1 916 785 3583 E-mail: johnf@hprnd.rose.hp.com
编辑：约翰·弗利克邮政：惠普公司8000山麓大道。M/S 5556加利福尼亚州罗斯维尔95747-5556美国电话：+1 916 785 4018传真：+1 916 785 3583电子邮件：johnf@hprnd.rose.hp.com
Editor: Jeffrey Johnson Postal: RedBack Networks 2570 North First Street, Suite 410 San Jose, CA, 95131 USA Tel: +1 408 571 2699 Fax: +1 408 571 2698 E-Mail: jeff@redbacknetworks.com"
编辑：Jeffrey Johnson Postal:RedBack Networks 2570 North First Street，410 Suite，San Jose，CA，95131美国电话：+1 408 571 2699传真：+1 408 571 2698电子邮件：jeff@redbacknetworks.com"
DESCRIPTION "The MIB module to describe generic objects for Ethernet-like network interfaces. This MIB is an updated version of the Ethernet-like MIB in RFC 1650."
DESCRIPTION“用于描述类以太网网络接口的通用对象的MIB模块。此MIB是RFC 1650中类以太网MIB的更新版本。”
REVISION "9806032150Z" DESCRIPTION "Updated to include support for 100 Mb/sec interfaces."
修订版“9806032150Z”说明“已更新，包括对100 Mb/秒接口的支持。”
REVISION "9402030400Z"
DESCRIPTION "Version published as RFC 1650."
::= { mib-2 35 }
REVISION "9402030400Z"
DESCRIPTION "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
Dot3StatsEntry MAX-ACCESS的dot3StatsTable对象类型语法序列不可访问
STATUS current
DESCRIPTION "Statistics for a collection of ethernet-like
interfaces attached to a particular system."
::= { dot3 2 }
STATUS current
DESCRIPTION "Statistics for a collection of ethernet-like
interfaces attached to a particular 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 {
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
}
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
}
dot3StatsIndex OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS read-only
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."
::= { dot3StatsEntry 1 }
dot3StatsIndex OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS read-only
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."
::= { dot3StatsEntry 1 }
dot3StatsAlignmentErrors OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current
dot3StatsAlignmentErrors对象类型语法计数器32 MAX-ACCESS只读状态当前
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.
描述“特定接口上接收的帧计数，其长度不是八位字节的整数，且未通过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 obtain are,
according to the conventions of IEEE 802.3
Layer Management, counted exclusively according
to the error status presented to the LLC."
REFERENCE "IEEE 802.3 Layer Management"
::= { dot3StatsEntry 2 }
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 obtain are,
according to the conventions of IEEE 802.3
Layer Management, counted exclusively according
to the error status presented to the LLC."
REFERENCE "IEEE 802.3 Layer Management"
::= { 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.
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 obtain are,
according to the conventions of IEEE 802.3
Layer Management, counted exclusively according
to the error status presented to the LLC."
REFERENCE "IEEE 802.3 Layer Management"
::= { dot3StatsEntry 3 }
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 obtain are,
according to the conventions of IEEE 802.3
Layer Management, counted exclusively according
to the error status presented to the LLC."
REFERENCE "IEEE 802.3 Layer Management"
::= { dot3StatsEntry 3 }
dot3StatsSingleCollisionFrames OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "A count of successfully transmitted frames on a particular interface for which transmission is inhibited by exactly one collision.
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
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."
REFERENCE "IEEE 802.3 Layer Management"
::= { dot3StatsEntry 4 }
object."
REFERENCE "IEEE 802.3 Layer Management"
::= { dot3StatsEntry 4 }
dot3StatsMultipleCollisionFrames OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "A count of successfully transmitted frames on a particular interface for which transmission is inhibited by more than one collision.
dot3StatsMultipleCollisionFrames对象类型语法计数器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 dot3StatsSingleCollisionFrames
object."
REFERENCE "IEEE 802.3 Layer Management"
::= { dot3StatsEntry 5 }
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."
REFERENCE "IEEE 802.3 Layer Management"
::= { dot3StatsEntry 5 }
dot3StatsSQETestErrors OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "A count of times that the SQE TEST ERROR
message is generated by the PLS sublayer for a
particular interface. The SQE TEST ERROR
message is defined in section 7.2.2.2.4 of
ANSI/IEEE 802.3-1985 and its generation is
described in section 7.2.4.6 of the same
document."
REFERENCE "ANSI/IEEE Std 802.3-1985 Carrier Sense
Multiple Access with Collision Detection Access
Method and Physical Layer Specifications"
::= { dot3StatsEntry 6 }
dot3StatsSQETestErrors OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "A count of times that the SQE TEST ERROR
message is generated by the PLS sublayer for a
particular interface. The SQE TEST ERROR
message is defined in section 7.2.2.2.4 of
ANSI/IEEE 802.3-1985 and its generation is
described in section 7.2.4.6 of the same
document."
REFERENCE "ANSI/IEEE Std 802.3-1985 Carrier Sense
Multiple Access with Collision Detection Access
Method and Physical Layer Specifications"
::= { dot3StatsEntry 6 }
dot3StatsDeferredTransmissions OBJECT-TYPE SYNTAX Counter32 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.
dot3StatsDeferredTransmissions对象类型语法计数器32 MAX-ACCESS只读状态当前描述“由于介质忙，在特定接口上的第一次传输尝试延迟的帧计数。
The count represented by an instance of this
object does not include frames involved in
collisions."
REFERENCE "IEEE 802.3 Layer Management"
::= { dot3StatsEntry 7 }
The count represented by an instance of this
object does not include frames involved in
collisions."
REFERENCE "IEEE 802.3 Layer Management"
::= { 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 512 bit-times into the transmission of a packet.
dot3StatsLateCollisions对象类型语法计数器32 MAX-ACCESS只读状态当前描述“在数据包传输过程中，在特定接口上检测到冲突的次数超过512位。
Five hundred and twelve bit-times corresponds
to 51.2 microseconds on a 10 Mbit/s system. 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."
REFERENCE "IEEE 802.3 Layer Management"
::= { dot3StatsEntry 8 }
Five hundred and twelve bit-times corresponds
to 51.2 microseconds on a 10 Mbit/s system. 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."
REFERENCE "IEEE 802.3 Layer Management"
::= { dot3StatsEntry 8 }
dot3StatsExcessiveCollisions 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 excessive
collisions."
REFERENCE "IEEE 802.3 Layer Management"
::= { dot3StatsEntry 9 }
dot3StatsExcessiveCollisions 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 excessive
collisions."
REFERENCE "IEEE 802.3 Layer Management"
::= { 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."
REFERENCE "IEEE 802.3 Layer Management"
::= { dot3StatsEntry 10 }
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."
REFERENCE "IEEE 802.3 Layer Management"
::= { 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."
REFERENCE "IEEE 802.3 Layer Management"
::= { dot3StatsEntry 11 }
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."
REFERENCE "IEEE 802.3 Layer Management"
::= { 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 obtain are,
according to the conventions of IEEE 802.3
Layer Management, counted exclusively according
to the error status presented to the LLC."
REFERENCE "IEEE 802.3 Layer Management"
::= { dot3StatsEntry 13 }
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 obtain are,
according to the conventions of IEEE 802.3
Layer Management, counted exclusively according
to the error status presented to the LLC."
REFERENCE "IEEE 802.3 Layer Management"
::= { 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.
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."
REFERENCE "IEEE 802.3 Layer Management"
::= { dot3StatsEntry 16 }
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.
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."
REFERENCE "IEEE 802.3 Layer Management"
::= { dot3StatsEntry 16 }
dot3StatsEtherChipSet OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-only
STATUS current
DESCRIPTION "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."
::= { dot3StatsEntry 17 }
dot3StatsEtherChipSet OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-only
STATUS current
DESCRIPTION "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."
::= { dot3StatsEntry 17 }
dot3StatsSymbolErrors OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of times there was an invalid data symbol when a valid carrier was present on a particular interface.
dot3StatsSymbolErrors对象类型语法计数器32 MAX-ACCESS只读状态当前描述“当特定接口上存在有效载体时，存在无效数据符号的次数。
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."
REFERENCE "IEEE 802.3u-1995 10 & 100 Mb/s Management"
::= { dot3StatsEntry 18 }
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."
REFERENCE "IEEE 802.3u-1995 10 & 100 Mb/s Management"
::= { dot3StatsEntry 18 }
-- 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."
::= { 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."
::= { 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
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 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
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 INTEGER,
dot3CollFrequencies Counter32
}
Dot3CollEntry ::=
SEQUENCE {
dot3CollCount INTEGER,
dot3CollFrequencies Counter32
}
-- { dot3CollEntry 1 } is no longer in use
--{dot3CollEntry 1}不再使用
dot3CollCount OBJECT-TYPE
SYNTAX INTEGER (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 INTEGER (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."
::= { dot3CollEntry 3 }
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."
::= { dot3CollEntry 3 }
-- 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 current DESCRIPTION "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
dot3TestTdr对象标识状态当前描述“时域反射仪（TDR）测试特定于10Base5和10Base2类型的以太网类接口。TDR值可用于确定电缆故障的大致距离。建议重复此测试
this test to check for a consistent resulting TDR value, to verify that there is a fault.
本测试旨在检查产生的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)."
::= { dot3Tests 1 }
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)."
::= { dot3Tests 1 }
-- Loopback Test
--环回测试
dot3TestLoopBack OBJECT-IDENTITY STATUS current DESCRIPTION "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 be reinitialized for network operation, but it should remain offline.
dot3TestLoopBack对象标识状态当前描述“此测试配置MAC芯片，并执行内存、数据路径和MAC芯片逻辑的内部环回测试。此环回测试只能在接口脱机时执行。一旦测试完成，MAC芯片应重新初始化以进行网络操作，但应保持脱机状态。
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."
::= { dot3Tests 2 }
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."
::= { dot3Tests 2 }
dot3ErrorInitError OBJECT-IDENTITY
STATUS current
DESCRIPTION "Couldn't initialize MAC chip for test."
::= { dot3Errors 1 }
dot3ErrorInitError OBJECT-IDENTITY
STATUS current
DESCRIPTION "Couldn't initialize MAC chip for test."
::= { dot3Errors 1 }
dot3ErrorLoopbackError OBJECT-IDENTITY STATUS current DESCRIPTION "Expected data not received (or not received correctly) in loopback test."
dot3ErrorLoopbackError对象标识状态当前描述“在环回测试中未接收（或未正确接收）预期数据。”
::= { dot3Errors 2 }
::= { dot3Errors 2 }
-- 802.3 Hardware Chipsets
--802.3硬件芯片组
-- The object dot3StatsEtherChipSet is provided to
-- identify the MAC hardware used to communicate on an
-- interface. The following hardware chipsets are
-- registered:
-- The object dot3StatsEtherChipSet is provided to
-- identify the MAC hardware used to communicate on an
-- interface. The following hardware chipsets are
-- registered:
dot3ChipSets OBJECT IDENTIFIER ::= { dot3 8 }
dot3ChipSets OBJECT IDENTIFIER ::= { dot3 8 }
dot3ChipSetAMD OBJECT IDENTIFIER ::= { dot3ChipSets 1 }
dot3ChipSetAMD OBJECT IDENTIFIER ::= { dot3ChipSets 1 }
dot3ChipSetAMD7990 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Advanced
Micro Devices Am7990 Local Area Network
Controller for Ethernet (LANCE)."
::= { dot3ChipSetAMD 1 }
dot3ChipSetAMD7990 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Advanced
Micro Devices Am7990 Local Area Network
Controller for Ethernet (LANCE)."
::= { dot3ChipSetAMD 1 }
dot3ChipSetAMD79900 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Advanced
Micro Devices Am79900 chip."
::= { dot3ChipSetAMD 2 }
dot3ChipSetAMD79900 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Advanced
Micro Devices Am79900 chip."
::= { dot3ChipSetAMD 2 }
dot3ChipSetAMD79C940 OBJECT-IDENTITY
dot3ChipSetAMD79C940对象标识
STATUS current
DESCRIPTION "The authoritative identifier for the Advanced
Micro Devices Am79C940 Media Access Controller
for Ethernet (MACE)."
::= { dot3ChipSetAMD 3 }
STATUS current
DESCRIPTION "The authoritative identifier for the Advanced
Micro Devices Am79C940 Media Access Controller
for Ethernet (MACE)."
::= { dot3ChipSetAMD 3 }
dot3ChipSetAMD79C90 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Advanced
Micro Devices Am79C90 CMOS Local Area Network
Controller for Ethernet (C-LANCE)."
::= { dot3ChipSetAMD 4 }
dot3ChipSetAMD79C90 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Advanced
Micro Devices Am79C90 CMOS Local Area Network
Controller for Ethernet (C-LANCE)."
::= { dot3ChipSetAMD 4 }
dot3ChipSetAMD79C960 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Advanced
Micro Devices Am79C960 PCnet-ISA Single Chip
Ethernet Controller for ISA."
::= { dot3ChipSetAMD 5 }
dot3ChipSetAMD79C960 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Advanced
Micro Devices Am79C960 PCnet-ISA Single Chip
Ethernet Controller for ISA."
::= { dot3ChipSetAMD 5 }
dot3ChipSetAMD79C961 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Advanced
Micro Devices Am79C961 PCnet-ISA+ Single Chip
Plug & Play Full-Duplex Ethernet Controller
for ISA."
::= { dot3ChipSetAMD 6 }
dot3ChipSetAMD79C961 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Advanced
Micro Devices Am79C961 PCnet-ISA+ Single Chip
Plug & Play Full-Duplex Ethernet Controller
for ISA."
::= { dot3ChipSetAMD 6 }
dot3ChipSetAMD79C961A OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Advanced
Micro Devices Am79C961A PCnet-ISA II Single Chip
Plug & Play Full-Duplex Ethernet Controller
for ISA."
::= { dot3ChipSetAMD 7 }
dot3ChipSetAMD79C961A OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Advanced
Micro Devices Am79C961A PCnet-ISA II Single Chip
Plug & Play Full-Duplex Ethernet Controller
for ISA."
::= { dot3ChipSetAMD 7 }
dot3ChipSetAMD79C965 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Advanced
Micro Devices Am79C965 PCnet-32 Single Chip
Ethernet Controller for PCI."
::= { dot3ChipSetAMD 8 }
dot3ChipSetAMD79C965 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Advanced
Micro Devices Am79C965 PCnet-32 Single Chip
Ethernet Controller for PCI."
::= { dot3ChipSetAMD 8 }
dot3ChipSetAMD79C970 OBJECT-IDENTITY STATUS current DESCRIPTION "The authoritative identifier for the Advanced Micro Devices Am79C970 PCnet PCI Single Chip Ethernet Controller for PCI Local Bus."
dot3ChipSetAMD79C970对象标识状态当前描述“用于PCI本地总线的高级微设备Am79C970 PCnet PCI单芯片以太网控制器的权威标识符。”
::= { dot3ChipSetAMD 9 }
::= { dot3ChipSetAMD 9 }
dot3ChipSetAMD79C970A OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Advanced
Micro Devices AM79C970A PCnet PCI II Single Chip
Full-Duplex Ethernet Controller for PCI Local
Bus."
::= { dot3ChipSetAMD 10 }
dot3ChipSetAMD79C970A OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Advanced
Micro Devices AM79C970A PCnet PCI II Single Chip
Full-Duplex Ethernet Controller for PCI Local
Bus."
::= { dot3ChipSetAMD 10 }
dot3ChipSetAMD79C971 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Advanced
Micro Devices Am79C971 PCnet-FAST Single Chip
Full-Duplex 10/100 Mbps Ethernet Controller for
PCI Local Bus."
::= { dot3ChipSetAMD 11 }
dot3ChipSetAMD79C971 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Advanced
Micro Devices Am79C971 PCnet-FAST Single Chip
Full-Duplex 10/100 Mbps Ethernet Controller for
PCI Local Bus."
::= { dot3ChipSetAMD 11 }
dot3ChipSetAMD79C972 OBJECT-IDENTITY
dot3ChipSetAMD79C972对象标识
STATUS current
DESCRIPTION "The authoritative identifier for the Advanced
Micro Devices Am79C972 PCnet-FAST+ Enhanced
10/100 Mbps PCI Ethernet Controller with OnNow
Support."
::= { dot3ChipSetAMD 12 }
STATUS current
DESCRIPTION "The authoritative identifier for the Advanced
Micro Devices Am79C972 PCnet-FAST+ Enhanced
10/100 Mbps PCI Ethernet Controller with OnNow
Support."
::= { dot3ChipSetAMD 12 }
dot3ChipSetIntel OBJECT IDENTIFIER ::= { dot3ChipSets 2 }
dot3ChipSetIntel OBJECT IDENTIFIER ::= { dot3ChipSets 2 }
dot3ChipSetIntel82586 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Intel
82586 IEEE 802.3 Ethernet LAN Coprocessor."
::= { dot3ChipSetIntel 1 }
dot3ChipSetIntel82586 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Intel
82586 IEEE 802.3 Ethernet LAN Coprocessor."
::= { dot3ChipSetIntel 1 }
dot3ChipSetIntel82596 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Intel
82596 High-Performance 32-Bit Local Area Network
Coprocessor."
::= { dot3ChipSetIntel 2 }
dot3ChipSetIntel82596 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Intel
82596 High-Performance 32-Bit Local Area Network
Coprocessor."
::= { dot3ChipSetIntel 2 }
dot3ChipSetIntel82595 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Intel
82595 High Integration Ethernet Controller."
::= { dot3ChipSetIntel 3 }
dot3ChipSetIntel82595 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Intel
82595 High Integration Ethernet Controller."
::= { dot3ChipSetIntel 3 }
dot3ChipSetIntel82557 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Intel
82557 Fast Ethernet PCI Bus Lan Controller."
::= { dot3ChipSetIntel 4 }
dot3ChipSetIntel82557 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Intel
82557 Fast Ethernet PCI Bus Lan Controller."
::= { dot3ChipSetIntel 4 }
dot3ChipSetIntel82558 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Intel
82558 Fast Ethernet PCI Bus LAN Controller with
Integrated PHY."
::= { dot3ChipSetIntel 5 }
dot3ChipSetIntel82558 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Intel
82558 Fast Ethernet PCI Bus LAN Controller with
Integrated PHY."
::= { dot3ChipSetIntel 5 }
dot3ChipSetSeeq OBJECT IDENTIFIER ::= { dot3ChipSets 3 }
dot3ChipSetSeeq OBJECT IDENTIFIER ::= { dot3ChipSets 3 }
dot3ChipSetSeeq8003 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the SEEQ
8003 chip set."
::= { dot3ChipSetSeeq 1 }
dot3ChipSetSeeq8003 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the SEEQ
8003 chip set."
::= { dot3ChipSetSeeq 1 }
dot3ChipSetSeeq80C03 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the SEEQ
80C03 Full-Duplex CMOS Ethernet Data Link
Controller (MAC)."
::= { dot3ChipSetSeeq 2 }
dot3ChipSetSeeq80C03 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the SEEQ
80C03 Full-Duplex CMOS Ethernet Data Link
Controller (MAC)."
::= { dot3ChipSetSeeq 2 }
dot3ChipSetSeeq84C30 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the SEEQ
4-Port 84C30 Full-Duplex CMOS Ethernet 10
MBit/Sec Data Link Controller (MAC)."
::= { dot3ChipSetSeeq 3 }
dot3ChipSetSeeq84C30 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the SEEQ
4-Port 84C30 Full-Duplex CMOS Ethernet 10
MBit/Sec Data Link Controller (MAC)."
::= { dot3ChipSetSeeq 3 }
dot3ChipSetSeeq8431 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the SEEQ
4-Port 8431 Full-Duplex CMOS Ethernet 10
MBit/Sec Data Link Controller (MAC)."
::= { dot3ChipSetSeeq 4 }
dot3ChipSetSeeq8431 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the SEEQ
4-Port 8431 Full-Duplex CMOS Ethernet 10
MBit/Sec Data Link Controller (MAC)."
::= { dot3ChipSetSeeq 4 }
dot3ChipSetSeeq80C300 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the SEEQ
80C300 Full-Duplex CMOS Ethernet 10/100
Mbit/Sec Data Link Controller (MAC)."
::= { dot3ChipSetSeeq 5 }
dot3ChipSetSeeq80C300 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the SEEQ
80C300 Full-Duplex CMOS Ethernet 10/100
Mbit/Sec Data Link Controller (MAC)."
::= { dot3ChipSetSeeq 5 }
dot3ChipSetSeeq84C300 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the SEEQ
4-Port 84C300 Fast Ethernet Controller (MAC)."
::= { dot3ChipSetSeeq 6 }
dot3ChipSetSeeq84C300 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the SEEQ
4-Port 84C300 Fast Ethernet Controller (MAC)."
::= { dot3ChipSetSeeq 6 }
dot3ChipSetSeeq84301 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the SEEQ
4-Port 84301 Fast Ethernet Controller (MAC)."
::= { dot3ChipSetSeeq 7 }
dot3ChipSetSeeq84301 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the SEEQ
4-Port 84301 Fast Ethernet Controller (MAC)."
::= { dot3ChipSetSeeq 7 }
dot3ChipSetSeeq84302 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the SEEQ
4-Port 84302 Fast Ethernet Controller (MAC)."
::= { dot3ChipSetSeeq 8 }
dot3ChipSetSeeq84302 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the SEEQ
4-Port 84302 Fast Ethernet Controller (MAC)."
::= { dot3ChipSetSeeq 8 }
dot3ChipSetSeeq8100 OBJECT-IDENTITY STATUS current
dot3ChipSetSeeq8100对象标识状态当前
DESCRIPTION "The authoritative identifier for the SEEQ
8100 Gigabit Ethernet Controller (MAC & PCS)."
::= { dot3ChipSetSeeq 9 }
DESCRIPTION "The authoritative identifier for the SEEQ
8100 Gigabit Ethernet Controller (MAC & PCS)."
::= { dot3ChipSetSeeq 9 }
dot3ChipSetNational OBJECT IDENTIFIER ::= { dot3ChipSets 4 }
dot3ChipSetNational OBJECT IDENTIFIER ::= { dot3ChipSets 4 }
dot3ChipSetNational8390 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the National
Semiconductor DP8390 Network Interface
Controller."
::= { dot3ChipSetNational 1 }
dot3ChipSetNational8390 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the National
Semiconductor DP8390 Network Interface
Controller."
::= { dot3ChipSetNational 1 }
dot3ChipSetNationalSonic OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the National
Semiconductor DP83932 Systems-Oriented Network
Interface Controller (SONIC)."
::= { dot3ChipSetNational 2 }
dot3ChipSetNationalSonic OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the National
Semiconductor DP83932 Systems-Oriented Network
Interface Controller (SONIC)."
::= { dot3ChipSetNational 2 }
dot3ChipSetNational83901 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the National
Semiconductor DP83901 Serial Network Interface
Controller (SNIC)."
::= { dot3ChipSetNational 3 }
dot3ChipSetNational83901 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the National
Semiconductor DP83901 Serial Network Interface
Controller (SNIC)."
::= { dot3ChipSetNational 3 }
dot3ChipSetNational83902 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the National
Semiconductor DP83902 Serial Network Interface
Controller for Twisted Pair (ST-NIC)."
::= { dot3ChipSetNational 4 }
dot3ChipSetNational83902 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the National
Semiconductor DP83902 Serial Network Interface
Controller for Twisted Pair (ST-NIC)."
::= { dot3ChipSetNational 4 }
dot3ChipSetNational83905 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the National
Semiconductor DP83905 AT Local Area Network
Twisted-Pair Interface (AT/LANTIC)."
::= { dot3ChipSetNational 5 }
dot3ChipSetNational83905 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the National
Semiconductor DP83905 AT Local Area Network
Twisted-Pair Interface (AT/LANTIC)."
::= { dot3ChipSetNational 5 }
dot3ChipSetNational83907 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the National
Semiconductor DP83907 AT Twisted-Pair Enhanced
Coaxial Network Interface Controller
(AT/LANTIC II)."
::= { dot3ChipSetNational 6 }
dot3ChipSetNational83907 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the National
Semiconductor DP83907 AT Twisted-Pair Enhanced
Coaxial Network Interface Controller
(AT/LANTIC II)."
::= { dot3ChipSetNational 6 }
dot3ChipSetNational83916 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the National
Semiconductor DP83916 Systems-Oriented Network
Interface Controller (SONIC-16)."
::= { dot3ChipSetNational 7 }
dot3ChipSetNational83916 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the National
Semiconductor DP83916 Systems-Oriented Network
Interface Controller (SONIC-16)."
::= { dot3ChipSetNational 7 }
dot3ChipSetNational83934 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the National
Semiconductor DP83934 Systems-Oriented Network
Interface Controller with Twisted Pair Interface
(SONIC-T)."
::= { dot3ChipSetNational 8 }
dot3ChipSetNational83934 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the National
Semiconductor DP83934 Systems-Oriented Network
Interface Controller with Twisted Pair Interface
(SONIC-T)."
::= { dot3ChipSetNational 8 }
dot3ChipSetNational83936 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the National
Semiconductor DP83936AVUL Full-Duplex Systems-
Oriented Network Interface Controller with
Twisted Pair Interface (SONIC-T)."
::= { dot3ChipSetNational 9 }
dot3ChipSetNational83936 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the National
Semiconductor DP83936AVUL Full-Duplex Systems-
Oriented Network Interface Controller with
Twisted Pair Interface (SONIC-T)."
::= { dot3ChipSetNational 9 }
dot3ChipSetFujitsu OBJECT IDENTIFIER ::= { dot3ChipSets 5 }
dot3ChipSetFujitsu OBJECT IDENTIFIER ::= { dot3ChipSets 5 }
dot3ChipSetFujitsu86950 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Fujitsu
86950 chip."
::= { dot3ChipSetFujitsu 1 }
dot3ChipSetFujitsu86950 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Fujitsu
86950 chip."
::= { dot3ChipSetFujitsu 1 }
dot3ChipSetFujitsu86960 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Fujitsu
MB86960 Network Interface Controller with
Encoder/Decoder (NICE)."
::= { dot3ChipSetFujitsu 2 }
dot3ChipSetFujitsu86960 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Fujitsu
MB86960 Network Interface Controller with
Encoder/Decoder (NICE)."
::= { dot3ChipSetFujitsu 2 }
dot3ChipSetFujitsu86964 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Fujitsu
MB86964 Ethernet Controller with 10BASE-T
Tranceiver."
::= { dot3ChipSetFujitsu 3 }
dot3ChipSetFujitsu86964 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Fujitsu
MB86964 Ethernet Controller with 10BASE-T
Tranceiver."
::= { dot3ChipSetFujitsu 3 }
dot3ChipSetFujitsu86965A OBJECT-IDENTITY STATUS current DESCRIPTION "The authoritative identifier for the Fujitsu
dot3ChipSetFujitsu86965A对象标识状态当前描述“Fujitsu的权威标识符
MB86965A EtherCoupler Single-Chip Ethernet
Controller."
::= { dot3ChipSetFujitsu 4 }
MB86965A EtherCoupler Single-Chip Ethernet
Controller."
::= { dot3ChipSetFujitsu 4 }
dot3ChipSetFujitsu86965B OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Fujitsu
MB86965B EtherCoupler Single-Chip Ethernet
Controller (supports full-duplex)."
::= { dot3ChipSetFujitsu 5 }
dot3ChipSetFujitsu86965B OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Fujitsu
MB86965B EtherCoupler Single-Chip Ethernet
Controller (supports full-duplex)."
::= { dot3ChipSetFujitsu 5 }
dot3ChipSetDigital OBJECT IDENTIFIER ::= { dot3ChipSets 6 }
dot3ChipSetDigital OBJECT IDENTIFIER ::= { dot3ChipSets 6 }
dot3ChipSetDigitalDC21040 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Digital
Semiconductor DC21040 chip."
::= { dot3ChipSetDigital 1 }
dot3ChipSetDigitalDC21040 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Digital
Semiconductor DC21040 chip."
::= { dot3ChipSetDigital 1 }
dot3ChipSetDigital21041 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Digital
Semiconductor 21041 PCI Ethernet LAN
Controller."
::= { dot3ChipSetDigital 2 }
dot3ChipSetDigital21041 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Digital
Semiconductor 21041 PCI Ethernet LAN
Controller."
::= { dot3ChipSetDigital 2 }
dot3ChipSetDigital21140 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Digital
Semiconductor 21140 PCI Fast Ethernet LAN
Controller."
::= { dot3ChipSetDigital 3 }
dot3ChipSetDigital21140 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Digital
Semiconductor 21140 PCI Fast Ethernet LAN
Controller."
::= { dot3ChipSetDigital 3 }
dot3ChipSetDigital21143 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Digital
Semiconductor 21143 PCI/CardBus 10/100-Mb/s
Ethernet LAN Controller."
::= { dot3ChipSetDigital 4 }
dot3ChipSetDigital21143 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Digital
Semiconductor 21143 PCI/CardBus 10/100-Mb/s
Ethernet LAN Controller."
::= { dot3ChipSetDigital 4 }
dot3ChipSetDigital21340 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Digital
Semiconductor 21340 10/100-MB/s managed buffered
port switch."
::= { dot3ChipSetDigital 5 }
dot3ChipSetDigital21340 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Digital
Semiconductor 21340 10/100-MB/s managed buffered
port switch."
::= { dot3ChipSetDigital 5 }
dot3ChipSetDigital21440 OBJECT-IDENTITY
dot3ChipSetDigital21440对象标识
STATUS current
DESCRIPTION "The authoritative identifier for the Digital
Semiconductor 21440 Multiport 10/100Mbps
Ethernet Controller."
::= { dot3ChipSetDigital 6 }
STATUS current
DESCRIPTION "The authoritative identifier for the Digital
Semiconductor 21440 Multiport 10/100Mbps
Ethernet Controller."
::= { dot3ChipSetDigital 6 }
dot3ChipSetDigital21540 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Digital
Semiconductor 21540 PCI/CardBus Ethernet LAN
Controller with Modem Interface."
::= { dot3ChipSetDigital 7 }
dot3ChipSetDigital21540 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Digital
Semiconductor 21540 PCI/CardBus Ethernet LAN
Controller with Modem Interface."
::= { dot3ChipSetDigital 7 }
dot3ChipSetTI OBJECT IDENTIFIER ::= { dot3ChipSets 7 }
dot3ChipSetTI OBJECT IDENTIFIER ::= { dot3ChipSets 7 }
dot3ChipSetTIE100 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Texas
Instruments TNETE100 ThunderLAN PCI Fast
Ethernet Controller."
::= { dot3ChipSetTI 1 }
dot3ChipSetTIE100 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Texas
Instruments TNETE100 ThunderLAN PCI Fast
Ethernet Controller."
::= { dot3ChipSetTI 1 }
dot3ChipSetTIE110 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Texas
Instruments TNETE110 ThunderLAN PCI 10BASE-T
Ethernet Adapter."
::= { dot3ChipSetTI 2 }
dot3ChipSetTIE110 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Texas
Instruments TNETE110 ThunderLAN PCI 10BASE-T
Ethernet Adapter."
::= { dot3ChipSetTI 2 }
dot3ChipSetTIX3100 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Texas
Instruments TNETX3100 Desktop ThunderSWITCH
8/2."
::= { dot3ChipSetTI 3 }
dot3ChipSetTIX3100 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Texas
Instruments TNETX3100 Desktop ThunderSWITCH
8/2."
::= { dot3ChipSetTI 3 }
dot3ChipSetTIX3150 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Texas
Instruments TNETX3150 ThunderSWITCH 12/3."
::= { dot3ChipSetTI 4 }
dot3ChipSetTIX3150 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Texas
Instruments TNETX3150 ThunderSWITCH 12/3."
::= { dot3ChipSetTI 4 }
dot3ChipSetTIX3270 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Texas
Instruments TNETX3270 ThunderSWITCH 24/3."
::= { dot3ChipSetTI 5 }
dot3ChipSetTIX3270 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Texas
Instruments TNETX3270 ThunderSWITCH 24/3."
::= { dot3ChipSetTI 5 }
dot3ChipSetToshiba OBJECT IDENTIFIER ::= { dot3ChipSets 8 }
dot3ChipSetToshiba OBJECT IDENTIFIER ::= { dot3ChipSets 8 }
dot3ChipSetToshibaTC35815F OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Toshiba
TC35815F PCI-Based 100/10Mbps Ethernet
Controller."
::= { dot3ChipSetToshiba 1 }
dot3ChipSetToshibaTC35815F OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Toshiba
TC35815F PCI-Based 100/10Mbps Ethernet
Controller."
::= { dot3ChipSetToshiba 1 }
dot3ChipSetLucent OBJECT IDENTIFIER ::= { dot3ChipSets 9 }
dot3ChipSetLucent OBJECT IDENTIFIER ::= { dot3ChipSets 9 }
dot3ChipSetLucentATT1MX10 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Lucent
Technologies ATT1MX10 (Spinnaker) Quad MAC and
Tranceiver for Ethernet Frame Switching."
::= { dot3ChipSetLucent 1 }
dot3ChipSetLucentATT1MX10 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Lucent
Technologies ATT1MX10 (Spinnaker) Quad MAC and
Tranceiver for Ethernet Frame Switching."
::= { dot3ChipSetLucent 1 }
dot3ChipSetLucentLUC3M08 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Lucent
Technologies LUC3M08 Eight Ethernet MACs for
10/100 Mbits/s Frame Switching."
::= { dot3ChipSetLucent 2 }
dot3ChipSetLucentLUC3M08 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Lucent
Technologies LUC3M08 Eight Ethernet MACs for
10/100 Mbits/s Frame Switching."
::= { dot3ChipSetLucent 2 }
dot3ChipSetGalileo OBJECT IDENTIFIER ::= { dot3ChipSets 10 }
dot3ChipSetGalileo OBJECT IDENTIFIER ::= { dot3ChipSets 10 }
dot3ChipSetGalileoGT48001 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Galileo
Technology GT-48001A Switched Ethernet
Controller."
::= { dot3ChipSetGalileo 1 }
dot3ChipSetGalileoGT48001 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Galileo
Technology GT-48001A Switched Ethernet
Controller."
::= { dot3ChipSetGalileo 1 }
dot3ChipSetGalileoGT48002 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Galileo
Technology GT-48002A Switched Fast Ethernet
Controller."
::= { dot3ChipSetGalileo 2 }
dot3ChipSetGalileoGT48002 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Galileo
Technology GT-48002A Switched Fast Ethernet
Controller."
::= { dot3ChipSetGalileo 2 }
dot3ChipSetGalileoGT48004 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Galileo
Technology GT-48004A Four Port Fast Ethernet
Switch for Multiport 10/100BASE-X Systems."
::= { dot3ChipSetGalileo 3 }
dot3ChipSetGalileoGT48004 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Galileo
Technology GT-48004A Four Port Fast Ethernet
Switch for Multiport 10/100BASE-X Systems."
::= { dot3ChipSetGalileo 3 }
dot3ChipSetGalileoGT48207 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Galileo
Technology GT-48207 Low-Cost 10 Port Switched
Ethernet Controller for 10+10/100BASE-X."
::= { dot3ChipSetGalileo 4 }
dot3ChipSetGalileoGT48207 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Galileo
Technology GT-48207 Low-Cost 10 Port Switched
Ethernet Controller for 10+10/100BASE-X."
::= { dot3ChipSetGalileo 4 }
dot3ChipSetGalileoGT48208 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Galileo
Technology GT-48208 Advanced 10 Port Switched
Ethernet Controller for 10+10/100BASE-X."
::= { dot3ChipSetGalileo 5 }
dot3ChipSetGalileoGT48208 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Galileo
Technology GT-48208 Advanced 10 Port Switched
Ethernet Controller for 10+10/100BASE-X."
::= { dot3ChipSetGalileo 5 }
dot3ChipSetGalileoGT48212 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Galileo
Technology GT-48212 Advanced 14 Port Switched
Ethernet Controller for 10+10/100BASE-X."
::= { dot3ChipSetGalileo 6 }
dot3ChipSetGalileoGT48212 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Galileo
Technology GT-48212 Advanced 14 Port Switched
Ethernet Controller for 10+10/100BASE-X."
::= { dot3ChipSetGalileo 6 }
dot3ChipSetJato OBJECT IDENTIFIER ::= { dot3ChipSets 11 }
dot3ChipSetJato OBJECT IDENTIFIER ::= { dot3ChipSets 11 }
dot3ChipSetJatoJT1001 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Jato
Technologies JT1001 GigEMAC Server
10/100/1000Mbps Ethernet Controller with PCI
interface."
::= { dot3ChipSetJato 1 }
dot3ChipSetJatoJT1001 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Jato
Technologies JT1001 GigEMAC Server
10/100/1000Mbps Ethernet Controller with PCI
interface."
::= { dot3ChipSetJato 1 }
dot3ChipSetXaQti OBJECT IDENTIFIER ::= { dot3ChipSets 12 }
dot3ChipSetXaQti OBJECT IDENTIFIER ::= { dot3ChipSets 12 }
dot3ChipSetXaQtiXQ11800FP OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the XaQTI
XQ11800FP XMAC II Gigabit Ethernet Media Access
Controller."
::= { dot3ChipSetXaQti 1 }
dot3ChipSetXaQtiXQ11800FP OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the XaQTI
XQ11800FP XMAC II Gigabit Ethernet Media Access
Controller."
::= { dot3ChipSetXaQti 1 }
dot3ChipSetXaQtiXQ18110FP OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the XaQTI
XQ18110FP GigaPower Protocol Accelerator."
::= { dot3ChipSetXaQti 2 }
dot3ChipSetXaQtiXQ18110FP OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the XaQTI
XQ18110FP GigaPower Protocol Accelerator."
::= { dot3ChipSetXaQti 2 }
-- For those chipsets not represented above, OBJECT IDENTIFIER
-- assignment is required in other documentation, e.g.,
-- For those chipsets not represented above, OBJECT IDENTIFIER
-- assignment is required in other documentation, e.g.,
-- assignment within that part of the registration tree
-- delegated to individual enterprises (see RFC 1155 and
-- RFC 1902).
--
-- In the future, management of chipset registrations may be
-- delegated to the Internet Assigned Numbers Authority (IANA).
-- assignment within that part of the registration tree
-- delegated to individual enterprises (see RFC 1155 and
-- RFC 1902).
--
-- In the future, management of chipset registrations may be
-- delegated to the Internet Assigned Numbers Authority (IANA).
-- 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 current DESCRIPTION "The compliance statement for managed network entities which have ethernet-like network interfaces."
etherCompliance MODULE-COMPLIANCE STATUS当前描述“具有类似以太网的网络接口的受管网络实体的符合性声明”
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 current DESCRIPTION "The compliance statement for managed network entities which have 100 Mb/sec ethernet-like network interfaces."
Ether100MB符合性模块-符合性状态当前描述“具有100 Mb/s以太网类网络接口的受管网络实体的符合性声明”
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 }
-- units of conformance
--一致性单位
etherStatsGroup OBJECT-GROUP
OBJECTS { dot3StatsIndex,
dot3StatsAlignmentErrors,
dot3StatsFCSErrors,
dot3StatsSingleCollisionFrames,
dot3StatsMultipleCollisionFrames,
dot3StatsSQETestErrors,
dot3StatsDeferredTransmissions,
dot3StatsLateCollisions,
dot3StatsExcessiveCollisions,
dot3StatsInternalMacTransmitErrors,
dot3StatsCarrierSenseErrors,
dot3StatsFrameTooLongs,
dot3StatsInternalMacReceiveErrors,
dot3StatsEtherChipSet
}
STATUS current
DESCRIPTION "A collection of objects providing information
applicable to all ethernet-like network
interfaces."
::= { etherGroups 1 }
etherStatsGroup OBJECT-GROUP
OBJECTS { dot3StatsIndex,
dot3StatsAlignmentErrors,
dot3StatsFCSErrors,
dot3StatsSingleCollisionFrames,
dot3StatsMultipleCollisionFrames,
dot3StatsSQETestErrors,
dot3StatsDeferredTransmissions,
dot3StatsLateCollisions,
dot3StatsExcessiveCollisions,
dot3StatsInternalMacTransmitErrors,
dot3StatsCarrierSenseErrors,
dot3StatsFrameTooLongs,
dot3StatsInternalMacReceiveErrors,
dot3StatsEtherChipSet
}
STATUS current
DESCRIPTION "A collection of objects providing information
applicable to all ethernet-like network
interfaces."
::= { 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,
EtherstStats100MBsgroup对象组对象{dot3StatsIndex，dot3StatsAlignmentErrors，Dot3StatsSerrors，dot3StatsSingleCollisionFrames，dot3StatsMultipleCollisionFrames，Dot3StatsFerredTransmission，Dot3StatsSlateCollisions，Dot3StatsAccessiveCollisions，Dot3StatsInInternalManactTransmisters，dot3StatsCarrierSenseErrors，dot3StatsFrameTooLongs，Dot3StatsInInternalMaciveErrors，
dot3StatsEtherChipSet,
dot3StatsSymbolErrors
}
STATUS current
DESCRIPTION "A collection of objects providing information
applicable to 100 Mb/sec ethernet-like network
interfaces."
::= { etherGroups 3 }
dot3StatsEtherChipSet,
dot3StatsSymbolErrors
}
STATUS current
DESCRIPTION "A collection of objects providing information
applicable to 100 Mb/sec ethernet-like network
interfaces."
::= { etherGroups 3 }
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 802.3 Hub MIB Working Group.
本文件由802.3集线器MIB工作组编制。
This document is almost completely based on both the Standard Ethernet MIB, RFC 1643 [10], and the Proposed Standard Ethernet MIB using the SNMPv2 SMI, RFC 1650 [11], both of which were edited by Frank Kastenholz of FTP Software and produced by the Ethernet MIB Working Group. This document extends those documents by providing support for 100 Mb/sec ethernet interfaces as outlined in [6].
本文件几乎完全基于标准以太网MIB RFC 1643[10]和使用SNMPv2 SMI RFC 1650[11]的拟议标准以太网MIB，两者均由FTP软件的Frank Kastenholz编辑，并由以太网MIB工作组制作。本文档通过支持[6]中概述的100 Mb/s以太网接口扩展了这些文档。
RFC 1643 and RFC 1650, in turn, are based on the Draft Standard Ethernet MIB, RFC 1398 [9], also edited by Frank Kastenholz and produced by the Ethernet MIB Working Group.
RFC 1643和RFC 1650依次基于标准以太网MIB草案RFC 1398[9]，该草案也由Frank Kastenholz编辑，并由以太网MIB工作组制作。
RFC 1398, in turn, is based on the Proposed Standard Ethernet MIB, RFC 1284 [8], 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 and used that information to develop this revised MIB.
反过来，RFC 1398基于提议的标准以太网MIB RFC 1284[8]，该标准由Chipcom的John Cook编辑，并由传输MIB工作组制作。Ethernet MIB工作组收集了RFC 1284中指定变量的实施经验，并利用这些信息开发了此修订的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 [7]. This document has been 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 its current 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.
反过来，RFC 1284是基于当时Interlan的Frank Kastenholz编写的一份文件，题为IEEE 802.3层管理草案M兼容TCP/IP网络MIB[7]。本文档最初由SNMP工作组修改，然后由传输工作组修改，以反映定义MIB接口对象的当前约定。麻省理工学院计算机科学实验室的詹姆斯·戴文（James Davin）和休斯局域网系统（Hughes LAN Systems）的基思·麦克洛赫里（Keith McCloghrie）为这份备忘录的后续草稿做出了贡献。Performance Systems International，Inc.的Marshall Rose将该文件转换为当前的简明格式。DEC的Anil Rijsinghani提供了更充分地描述TDR测试的文本。感谢因特拉的弗兰克·卡斯滕霍尔茨和IBM的路易斯·斯坦伯格的实验。
[1] Information processing systems - Open Systems Interconnection - Specification of Abstract Syntax Notation One (ASN.1), International Organization for Standardization, International Standard 8824, December 1987.
[1] 信息处理系统.开放系统互连.抽象语法符号1规范（ASN.1），国际标准化组织，国际标准88241987年12月。
[2] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure of Management Information for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, January 1996.
[2] SNMPv2工作组，Case，J.，McCloghrie，K.，Rose，M.，和S.Waldbusser，“简单网络管理协议（SNMPv2）版本2的管理信息结构”，RFC 1902，1996年1月。
[3] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual Conventions for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1903, January 1996.
[3] SNMPv2工作组，Case，J.，McCloghrie，K.，Rose，M.，和S.Waldbusser，“简单网络管理协议（SNMPv2）版本2的文本约定”，RFC 1903，1996年1月。
[4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Conformance Statements for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1904, January 1996.
[4] SNMPv2工作组，Case，J.，McCloghrie，K.，Rose，M.，和S.Waldbusser，“简单网络管理协议（SNMPv2）版本2的一致性声明”，RFC 1904，1996年1月。
[5] IEEE, IEEE 802.3 Layer Management, November 1988.
[5] IEEE，IEEE 802.3层管理，1988年11月。
[6] IEEE, IEEE 802.3u-1995, "10 & 100 Mb/s Management," Section 30, Supplement to IEEE Std 802.3, October 26, 1995.
[6] IEEE，IEEE 802.3u-1995，“10和100 Mb/s管理”，第30节，IEEE标准802.3补充，1995年10月26日。
[7] 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.
[7] Kastenholz，F.，“适用于TCP/IP网络的IEEE 802.3层管理草案兼容MIB”，发送至MIB的电子邮件-wg@nnsc.nsf.net，1989年6月9日。
[8] Cook, J., "Definitions of Managed Objects for Ethernet-Like Interface Types", RFC 1284, December 1991.
[8] Cook，J.，“类似以太网接口类型的托管对象定义”，RFC 1284，1991年12月。
[9] Kastenholz, F., "Definitions of Managed Objects for the Ethernet-like Interface Types", RFC 1398, January 1993.
[9] Kastenholz，F.，“类似以太网接口类型的托管对象定义”，RFC 1398，1993年1月。
[10] Kastenholz, F., "Definitions of Managed Objects for the Ethernet-like Interface Types", RFC 1643, July 1994.
[10] Kastenholz，F.，“类似以太网接口类型的托管对象定义”，RFC 1643，1994年7月。
[11] Kastenholz, F., "Definitions of Managed Objects for the Ethernet-like Interface Types using SMIv2", RFC 1650, August 1994.
[11] Kastenholz，F.，“使用SMIv2的类以太网接口类型的托管对象定义”，RFC1650，1994年8月。
[12] McCloghrie, K., and F. Kastenholz, "The Interfaces Group MIB using SMIv2", RFC 2233, Cisco Systems, November 1997.
[12] McCloghrie，K.和F.Kastenholz，“使用SMIv2的接口组MIB”，RFC 2233，思科系统，1997年11月。
[13] Bradner, S., "Key words for use in RFCs to Indicate Requirements Levels", BCP 14, RFC 2119, March 1997.
[13] Bradner，S.“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[14] deGraaf, K., Romascanu, D., McMaster, D., McCloghrie, K., and S. Roberts, "Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) using SMIv2", RFC 2239, November 1997.
[14] deGraaf，K.，Romascan，D.，McMaster，D.，McCloghrie，K.，和S.Roberts，“使用SMIv2的IEEE 802.3介质连接单元（MAU）的受管对象定义”，RFC 2239，1997年11月。
[15] Kastenholz, F., "Implementation Notes and Experience for The Internet Ethernet MIB", RFC 1369, October 1992.
[15] Kastenholz，F.，“因特网以太网MIB的实施说明和经验”，RFC 1369，1992年10月。
[16] 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.
[16] McCloghrie，K.和M.Rose，编辑，“基于TCP/IP的互联网网络管理的管理信息库：MIB-II”，STD 17，RFC 1213，1991年3月。
[17] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 2274, January 1998.
[17] Blumenthal，U.和B.Wijnen，“简单网络管理协议（SNMPv3）第3版的基于用户的安全模型（USM）”，RFC 22741998年1月。
[18] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access Control Model for the Simple Network Management Protocol (SNMP)", RFC 2275, January 1998.
[18] Wijnen，B.，Presuhn，R.，和K.McCloghrie，“简单网络管理协议（SNMP）基于视图的访问控制模型”，RFC 22751998年1月。
There are no management objects defined in this MIB that have a MAX-ACCESS clause of read-write and/or read-create. So, if this MIB is implemented correctly, then there is no risk that an intruder can alter or create any management objects of this MIB via direct SNMP SET operations.
此MIB中未定义具有读写和/或读创建MAX-ACCESS子句的管理对象。因此，如果此MIB正确实现，则入侵者不会通过直接的SNMP集操作更改或创建此MIB的任何管理对象。
There are a number of managed objects in this MIB that may be considered to contain sensitive information. 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.
此MIB中有许多托管对象可能被认为包含敏感信息。特别是，Dot3StateSetherChipset对象在许多环境中可能被视为敏感对象，因为它允许入侵者获取有关网络上使用的供应商设备的信息。
Therefore, it may be important in some environments to control read access to these objects and possibly to even encrypt the values of these object when sending them over the network via SNMP. Not all versions of SNMP provide features for such a secure environment.
因此，在某些环境中，控制对这些对象的读取访问，甚至可能在通过SNMP通过网络发送这些对象时加密这些对象的值，这可能很重要。并非所有版本的SNMP都为这种安全环境提供功能。
SNMPv1 by itself is such an insecure environment. 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 (read) the objects in this MIB.
SNMPv1本身就是这样一个不安全的环境。即使网络本身是安全的（例如通过使用IPSec），即使如此，也无法控制安全网络上的谁可以访问和获取（读取）此MIB中的对象。
It is recommended that the implementors consider the security features as provided by the SNMPv3 framework. Specifically, the use of the User-based Security Model RFC 2274 [17] and the View-based Access Control Model RFC 2275 [18] is recommended.
建议执行者考虑SNMPv3框架提供的安全特性。具体而言，建议使用基于用户的安全模型RFC 2274[17]和基于视图的访问控制模型RFC 2275[18]。
It is then a customer/user responsibility to ensure that the SNMP entity giving access to an instance of this MIB, is properly configured to give access to those objects only to those principals (users) that have legitimate rights to access them.
然后，客户/用户有责任确保授予对此MIB实例访问权限的SNMP实体正确配置为仅授予具有合法访问权限的主体（用户）对这些对象的访问权限。
John Flick Hewlett-Packard Company 8000 Foothills Blvd. M/S 5556 Roseville, CA 95747-5556
约翰·弗利克惠普公司8000山麓大道。加利福尼亚州罗斯维尔市南5556号，邮编95747-5556
Phone: +1 916 785 4018
EMail: johnf@hprnd.rose.hp.com
Phone: +1 916 785 4018
EMail: johnf@hprnd.rose.hp.com
Jeffrey Johnson RedBack Networks 2570 North First Street, Suite 410 San Jose, CA, 95131, USA
Jeffrey Johnson RedBack Networks美国加利福尼亚州圣何塞市北第一街2570号410室，邮编95131
Phone: +1 408 571 2699
EMail: jeff@redbacknetworks.com
Phone: +1 408 571 2699
EMail: jeff@redbacknetworks.com
A. Change Log
A.更改日志
This section enumerates changes made to RFC 1650 to produce this document.
本节列举了为编制本文件而对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的要求，增加了知识产权声明和版权声明。
B. Full Copyright Statement
B.完整的版权声明
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 assigns.
上述授予的有限许可是永久性的，互联网协会或其继承人或受让人不会撤销。
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.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。