Network Working Group M. Squire
Request for Comments: 4878 Hatteras Networks
Category: Standards Track June 2007
Network Working Group M. Squire
Request for Comments: 4878 Hatteras Networks
Category: Standards Track June 2007
Definitions and Managed Objects for Operations, Administration, and Maintenance (OAM) Functions on Ethernet-Like Interfaces
类以太网接口上操作、管理和维护（OAM）功能的定义和托管对象
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 IETF Trust (2007).
版权所有（C）IETF信托基金（2007年）。
Abstract
摘要
This document defines objects for managing Operations, Administration, and Maintenance (OAM) capabilities on Ethernet-like interfaces conformant to the Ethernet OAM functionality defined in the Ethernet in the First Mile (EFM) clauses of the Ethernet standards. The Ethernet OAM functionality is complementary to the Simple Network Management Protocol (SNMP) in that it is focused on a small set of link-specific functions for directly connected Ethernet interfaces. This document defines objects for controlling those link OAM functions and for providing results and status of the OAM functions to management entities.
本文档定义了用于管理类以太网接口上的操作、管理和维护（OAM）功能的对象，该类接口符合以太网标准第一英里（EFM）条款中定义的以太网OAM功能。以太网OAM功能是对简单网络管理协议（SNMP）的补充，因为它主要用于直接连接的以太网接口的一小部分特定于链路的功能。本文档定义了用于控制这些链接OAM功能以及向管理实体提供OAM功能的结果和状态的对象。
Table of Contents
目录
1. Introduction ....................................................2
2. The Internet-Standard Management Framework ......................2
3. Overview ........................................................3
3.1. Remote Fault Indication ....................................4
3.2. Link Monitoring ............................................4
3.3. Remote Loopback ............................................5
3.4. Ethernet OAM Protocol Data Units ...........................5
4. Relation to the Other MIB Modules ...............................5
4.1. Relation to Other MIB Modules ..............................5
4.2. Relation to Other EFM MIB Modules ..........................6
4.3. Mapping of IEEE 802.3ah Managed Objects ....................6
5. MIB Structure ...................................................7
6. MIB Definition ..................................................8
7. Security Considerations ........................................47
8. IANA Considerations ............................................49
9. References .....................................................49
9.1. Normative References ......................................49
9.2. Informative References ....................................50
10. Acknowledgments ...............................................51
1. Introduction ....................................................2
2. The Internet-Standard Management Framework ......................2
3. Overview ........................................................3
3.1. Remote Fault Indication ....................................4
3.2. Link Monitoring ............................................4
3.3. Remote Loopback ............................................5
3.4. Ethernet OAM Protocol Data Units ...........................5
4. Relation to the Other MIB Modules ...............................5
4.1. Relation to Other MIB Modules ..............................5
4.2. Relation to Other EFM MIB Modules ..........................6
4.3. Mapping of IEEE 802.3ah Managed Objects ....................6
5. MIB Structure ...................................................7
6. MIB Definition ..................................................8
7. Security Considerations ........................................47
8. IANA Considerations ............................................49
9. References .....................................................49
9.1. Normative References ......................................49
9.2. Informative References ....................................50
10. Acknowledgments ...............................................51
The IEEE 802.3ah Ethernet in the First Mile (EFM) taskforce added new management capabilities to Ethernet-like interfaces. These management capabilities were introduced to provide some basic Ordered Aggregate (OA) function on Ethernet media. The defined functionality includes discovery, error signaling, loopback, and link monitoring. This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community to manage these new Ethernet interface capabilities.
IEEE 802.3ah第一英里以太网（EFM）工作组为类似以太网的接口添加了新的管理功能。引入这些管理功能是为了在以太网介质上提供一些基本的有序聚合（OA）功能。定义的功能包括发现、错误信号、环回和链路监视。本备忘录定义了管理信息库（MIB）的一部分，用于互联网社区中的网络管理协议，以管理这些新的以太网接口功能。
Conventions Used in This Document
本文件中使用的公约
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 RFC 2119 [RFC2119].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119[RFC2119]中所述进行解释。
For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410 [RFC3410].
有关描述当前互联网标准管理框架的文件的详细概述，请参阅RFC 3410[RFC3410]第7节。
Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP).
托管对象通过虚拟信息存储（称为管理信息库或MIB）进行访问。MIB对象通常通过简单网络管理协议（SNMP）进行访问。
Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This memo specifies a MIB module that is compliant to the SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580].
MIB中的对象是使用管理信息结构（SMI）中定义的机制定义的。本备忘录规定了符合SMIv2的MIB模块，如STD 58、RFC 2578[RFC2578]、STD 58、RFC 2579[RFC2579]和STD 58、RFC 2580[RFC2580]所述。
Ethernet networks have evolved over the past 30 years from simple LANs to a variety of other applications, including wide-area networks. To address some of these emerging markets, the IEEE 802.3ah taskforce defined additional clauses in [802.3ah] for the IEEE 802.3 standard [802.3-2002] to better address Ethernet deployments in the public-access network. Although Ethernet-access deployments were the primary motivation for the taskforce activity, the results of the taskforce are not strictly limited to that application. Ethernet OAM can be implemented on Ethernet links that are not EFM.
在过去30年中，以太网从简单的局域网发展到各种其他应用，包括广域网。为了解决这些新兴市场中的一些问题，IEEE 802.3ah工作组在[802.3ah]中为IEEE 802.3标准[802.3-2002]定义了附加条款，以更好地解决公共接入网络中的以太网部署问题。尽管以太网接入部署是工作组活动的主要动机，但工作组的结果并不严格限于该应用程序。以太网OAM可以在非EFM的以太网链路上实现。
The Ethernet in the First Mile (EFM) taskforce was focused on four somewhat independent objectives to better address Ethernet access deployments: optics, copper, Ethernet passive optical networks (Ethernet PON, or EPON), and operations, administration, and maintenance (OAM). The optics sub-taskforce developed new optical physical layers that better served the long-reach outside plant networks typically found in the access network, including developing physical layers that operate up to 20 Km and supporting the environmental conditions of access deployments. The copper sub-taskforce developed two new physical layers that run Ethernet natively over existing twisted pair wires that have been supporting voice services for decades. The EPON sub-taskforce developed a new point-to-multipoint Ethernet physical layer, utilizing Ethernet framing natively over a time-division multiple-access (TDMA) infrastructure. The OAM sub-taskforce introduced some basic management functionality into an Ethernet link to better monitor and maintain Ethernet networks in geographically disparate networks.
第一英里中的以太网（EFM）工作组专注于四个稍微独立的目标，以更好地解决以太网接入部署：光学、铜缆、以太网无源光网络（以太网PON或EPON）以及运营、管理和维护（OAM）。光学子任务组开发了新的光学物理层，可更好地服务于接入网络中通常存在的长距离外部工厂网络，包括开发运行长达20公里的物理层，并支持接入部署的环境条件。铜缆子任务组开发了两个新的物理层，在支持语音服务数十年的现有双绞线上本机运行以太网。EPON子任务组开发了一个新的点对多点以太网物理层，在时分多址（TDMA）基础设施上本地利用以太网帧。OAM子任务组在以太网链路中引入了一些基本的管理功能，以便更好地监控和维护地理位置不同的网络中的以太网。
This document defines the management objects necessary to integrate Ethernet OAM functionality into the SNMP management framework.
本文档定义了将以太网OAM功能集成到SNMP管理框架中所需的管理对象。
Ethernet OAM is composed of a core set of functions and a set of optional functional groups. The mandatory functions include discovery operations (determining if the other end of the link is OA capable and what OAM functions it supports), state machine implementation, and some critical event flows. The optional functional groups are for (a) link events, (b) remote loopback, and (c) variable retrieval and response. Each optional functional group is controlled by a separate MIB table(s).
OAM是由一组可选的核心功能组和一组可选的以太网功能组组成的。强制功能包括发现操作（确定链路的另一端是否支持OA以及它支持哪些OAM功能）、状态机实现和一些关键事件流。可选功能组用于（a）链接事件、（b）远程环回和（c）变量检索和响应。每个可选功能组由单独的MIB表控制。
Ethernet OAM is complementary with SNMP management in that it provides some basic management functions at layer two, rather than using layer three and above as required by SNMP over an IP infrastructure. Ethernet OAM provides single-hop functionality in that it works only between two directly connected Ethernet stations. SNMP can be used to manage the Ethernet OAM interactions of one Ethernet station with another.
在以太网上使用SNMP提供基本的IP管理功能，而不是在上面的三层上使用SNMP提供基本的IP管理功能。以太网OAM提供单跳功能，因为它仅在两个直接连接的以太网站之间工作。SNMP可用于管理一个以太网站与另一个以太网站之间的以太网OAM交互。
Ethernet OAM has three functional objectives, which are detailed in the next three sections. The definition of a basic Ethernet OA protocol data unit is given in Section 3.4.
以太网OAM有三个功能目标，将在下面三节中详细介绍。第3.4节给出了基本以太网OA协议数据单元的定义。
Remote fault indication provides a mechanism for one end of an Ethernet link to signal the other end that the receive path is non-operational. Some Ethernet physical layers offer mechanisms to signal this condition at the physical layer. Ethernet OAM added a mechanism so that some Ethernet physical layers can operate in unidirectional mode, allowing frames to be transmitted in one direction even when the other direction is non-operational. Traditionally, Ethernet PHYs do not allow frame transmission in one direction if the other direction is not operational. Using this mode, Ethernet OAM allows frame-based signaling of remote fault conditions while still not allowing higher-layer applications to be aware of the unidirectional capability. This document includes mechanisms for capturing that fault information and reflecting such information in objects and notifications within the SNMP management framework.
远程故障指示为以太网链路的一端提供一种机制，向另一端发出接收路径不工作的信号。一些以太网物理层提供了在物理层发出这种情况信号的机制。以太网OAM添加了一种机制，使一些以太网物理层可以在单向模式下运行，允许在一个方向上传输帧，即使在另一个方向不运行时也是如此。传统上，以太网PHY不允许在一个方向上传输帧，如果另一个方向不工作。使用此模式，以太网OAM允许基于帧的远程故障条件信令，同时仍然不允许高层应用程序意识到单向能力。本文档包括用于捕获该故障信息并在SNMP管理框架内的对象和通知中反映此类信息的机制。
Ethernet OAM includes event signaling capability so that one end of an Ethernet link can indicate the occurrence of certain important events to the other end of the link. This happens via layer two protocols. This document defines methods for incorporating the occurrence of these layer two events, both at the local end and far end of the link, into the SNMP management framework.
以太网OAM包括事件信令能力，以便以太网链路的一端可以向链路的另一端指示某些重要事件的发生。这是通过第二层协议实现的。本文档定义了将链路本地端和远端发生的第二层事件合并到SNMP管理框架中的方法。
Ethernet OAM also includes mechanisms for one Ethernet station to query another directly connected Ethernet station about the status of its Ethernet interface variables and status. This document does not include mechanisms for controlling how one Ethernet endpoint may use this functionality to query the status or statistics of a peer Ethernet entity.
以太网OAM还包括一个以太网站查询另一个直接连接的以太网站的以太网接口变量和状态的机制。本文档不包括用于控制一个以太网端点如何使用此功能查询对等以太网实体的状态或统计信息的机制。
Remote loopback is a link state where the peer Ethernet entity echoes every received packet (without modifications) back onto the link. Remote loopback is intrusive in that the other end of the link is not forwarding traffic from higher layers out over the link. This document defines objects controlling loopback operation and reading the status of the loopback state.
远程环回是一种链路状态，对等以太网实体将每个接收到的数据包（无需修改）回显到链路上。远程环回具有侵入性，因为链路的另一端没有通过链路转发来自更高层的流量。本文档定义了控制环回操作和读取环回状态的对象。
An Ethernet OAM protocol data unit is a valid Ethernet frame with a destination Media Access Control (MAC) address equal to the reserved MAC address for Slow Protocols (See 43B of [802.3ah]), a lengthOrType field equal to the reserved type for Slow Protocols, and a Slow Protocols subtype equal to that of the subtype reserved for Ethernet OAM.
以太网OAM协议数据单元是一个有效的以太网帧，其目标媒体访问控制（MAC）地址等于慢速协议的保留MAC地址（参见[802.3ah]中的43B），长度类型字段等于慢速协议的保留类型，慢速协议子类型等于为以太网OAM保留的子类型。
OAMPDU is used throughout this document as an abbreviation for Ethernet OAM protocol data unit. OAMPDUs are the mechanism by which two directly connected Ethernet interfaces exchange OA information.
OAMPDU在本文档中用作以太网OAM协议数据单元的缩写。OAMPDU是两个直接连接的以太网接口交换OA信息的机制。
The definitions presented here are based on Clauses 30 and 57 of [802.3ah]. Note that these clauses describe many of these variables and their effects on the MAC layer. In some cases, there is a one-to-one relationship between an object in this document and an object in the Clause 30 MIB of [802.3ah]. In other cases, the objects of this document reflect a more complex entity and are reflected by more than one object in the Clause 30 MIB of [802.3ah].
此处给出的定义基于[802.3ah]第30条和第57条。请注意，这些子句描述了许多这些变量及其对MAC层的影响。在某些情况下，本文档中的对象与[802.3ah]第30条MIB中的对象之间存在一对一关系。在其他情况下，本文件的对象反映了更复杂的实体，并在[802.3ah]第30条MIB中由多个对象反映。
The objects defined in this document manage OAM functionality introduced in [802.3ah] These objects do not overlap with the interfaces MIB [RFC2863], the Ethernet-like interfaces MIB [RFC3635], or any other MIB currently used to manage various aspects of an Ethernet interface. The objects defined here are defined for Ethernet-like interfaces only and use the same ifIndex as the associated Ethernet interface. Ethernet OAM can be implemented on any Ethernet-like interface.
本文档中定义的对象管理[802.3ah]中引入的OAM功能。这些对象不与接口MIB[RFC2863]、类以太网接口MIB[RFC3635]或当前用于管理以太网接口各个方面的任何其他MIB重叠。此处定义的对象仅为类似以太网的接口定义，并使用与关联以太网接口相同的ifIndex。以太网OAM可以在任何类似以太网的接口上实现。
The Ethernet OAM functionality and MIB Module is independent of the other functionality and MIB Modules derived from [802.3ah] for copper [802.3ah-copper] and EPON [802.3ah-epon]. Ethernet OAM may be implemented (or not) on the new EFM interface types, just as it can on any other Ethernet interface.
以太网OAM功能和MIB模块独立于源自[802.3ah]的铜缆[802.3ah-copper]和EPON[802.3ah-EPON]的其他功能和MIB模块。以太网OAM可以在新的EFM接口类型上实现（或不实现），就像它可以在任何其他以太网接口上实现一样。
This section contains the mapping between managed objects defined in [802.3ah] Clause 30, and managed objects defined in this document.
本节包含[802.3ah]第30条中定义的托管对象与本文档中定义的托管对象之间的映射。
IEEE 802.3 Managed Object Corresponding SNMP object
IEEE 802.3管理对象对应的SNMP对象
oOA .aOAMID IF-MIB ifIndex .aOAMAdminState dot3OamAdminState .aOAMMode dot3OamMode .aOAMDiscoveryState dot3OamOperStatus .aOAMRemoteMACAddress dot3OamPeerMacAddress .aOAMLocalConfiguration dot3OamFunctionsSupported .aOAMRemoteConfiguration dot3OamPeerFunctionsSupported, dot3OamPeerMode .aOAMLocalPDUConfiguration dot3OamMaxOamPduSize .aOAMRemotePDUConfiguration dot3OamPeerMaxOamPduSize .aOAMLocalFlagsField dot3OamOperStatus, dot3OamEventLogEntry .aOAMRemoteFlagsField dot3OamOperStatus, dot3OamEventLogEntry .aOAMLocalRevision dot3OamConfigRevision .aOAMRemoteRevision dot3OamPeerConfigRevision .aOAMLocalState dot3OamLoopbackStatus .aOAMRemoteState dot3OamLoopbackStatus .aOAMRemoteVendorOUI dot3OamPeerVendorOui .aOAMRemoteVendorSpecificInfo dot3OamPeerVendorInfo .aOAMUnsupportedCodesTx dot3OamUnsupportedCodesTx .aOAMUnsupportedCodesRx dot3OamUnsupportedCodesRx .aOAMInformationTx dot3OamInformationTx .aOAMInformationRx dot3OamInformationRx
oOA.aOAMID IF-MIB ifIndex.AOAMADIMINSTATE dot3OamAdminState.AOAMODE dot3OamMode.aOAMDiscoveryState dot3OamOperStatus.aOAMRemoteMACAddress DOT3OAAMPERCADRESS.aOAMLocalConfiguration DOT3OAM功能受支持。AOAMREMOTECURATION配置DOT3OAM功能受支持，DOT3OAMPERMODE.AOAMLOCALPEDUCTION dot3OamMaxOamPduSize.AOAMREMOTEPDUCTION DOT3OAMPERMAXOAMPDUSIZE.aOAMLocalFlagsField dot3OamOperStatus，dot3OamEventLogEntry.AOAMREMOTEGLAGSFIELD dot3OamOperStatus，Dot3OAmeventGenetry.aOAMLocalRevision Dot3OAmConfigenVision.aOAMRemoteRevision Dot3OAmPerConfigenVision.aOAMLocalState dot3OamLoopbackStatus.aOAMRemoteState dot3OamLoopbackStatus.AOAMRemoteVendorUI Dot3OAmPervendoUI.aOAMRemoteVendorSpecificInfo Dot3OAmPervendorInfo.AOAMUnsupportedDestX Dot3OAmSupportedCodeSTX.aOAMUnsupportedCodesRx dot3OamUnsupportedCodesRx.aOAMInformationTx dot3OamInformationTx.aOAMInformationRx dot3OamInformationRx
.aOAMUniqueEventNotificationTx dot3OamUniqueEventNotificationTx .aOAMUniqueEventNotificationRx dot3OamUniqueEventNotificationRx .aOAMDuplicateEventNotificationTx dot3OamDuplicateEventNotificationTx .aOAMDuplicateEventNotificationRx dot3OamDuplicateEventNotificationRx .aOAMLoopbackControlTx dot3OamLoopbackControlTx
.aoamuniqueetnotificationtx dot3oamunicqueetnotificationtx.aoamuniqueetnotificationrx dot3oamunicqueetnotificationrx.aOAMDuplicateEventNotificationTx dot3oam重复事件通知tx.aOAMDuplicateEventNotificationRx dot3oam重复事件通知rx.aOAMLoopbackControlTx dot3OamLoopbackControlTx
.aOAMLoopbackControlRx dot3OamLoopbackControlRx .aOAMVariableRequestTx dot3OamVariableRequestTx .aOAMVariableRequestRx dot3OamVariableRequestRx .aOAMVariableResponseTx dot3OamVariableResponseTx .aOAMVariableResponseRx dot3OamVariableResponseRx .aOAMOrganizationSpecificTx dot3OamOrgSpecificTx .aOAMOrganizationSpecificRx dot3OamOrgSpecificTx
.aOAMLoopbackControlRx Dot3OAMLLoopBackControlRx.aOAMVariableRequestTx dot3OamVariableRequestTx.aOAMVariableRequestRx dot3OamVariableRequestRx.aOAMVariableResponseTx dot3OamVariableResponseTx.aOAMVariableResponseRx dot3OamVariableResponseRx.aOAMVariableResponseRx dot3OamVariableResponseRx
.aOAMLocalErrSymPeriodConfig dot3OamErrSymPeriodWindow, dot3OamErrSymPeriodThreshold .aOAMLocalErrSymPeriodEvent dot3OamEventLogEntry .aOAMLocalErrFrameConfig dot3OamErrFrameWindow, dot3OamErrFrameThreshold .aOAMLocalErrFrameEvent dot3OamEventLogEntry .aOAMLocalErrFramePeriodConfig dot3OamErrFramePeriodWindow, dot3OamErrFramePeriodThreshold .aOAMLocalErrFramePeriodEvent dot3OamEventLogEntry .aOAMLocalErrFrameSecsSummaryConfig dot3OamErrFrameSecsSummaryWindow, dot3OamErrFrameSecssummaryThreshold .aOAMLocalErrFrameSecsSummaryEvent dot3OamEventLogEntry .aOAMRemoteErrSymPeriodEvent dot3OamEventLogEntry .aOAMRemoteErrFrameEvent dot3OamEventLogEntry .aOAMRemoteErrFramePeriodEvent dot3OamEventLogEntry .aOAMRemoteErrFrameSecsSummaryEvent dot3OamEventLogEntry .aFramesLostDueToOAmError dot3OamFramesLostDueToOam .acOAMAdminControl dot3OamAdminState
.AOAMLOCalerSymPeriodConfig dot3OamErrSymPeriodWindow，dot3OamErrSymPeriodThreshold.AOAMLOCalerSymPeriodEvent dot3OamEventLogEntry.aOAMLocalErrFrameConfig dot3OamErrFrameWindow，dot3OamErrFrameThreshold.AOAMLOCalerFramePeriodConfig dot3OamErrFramePeriodWindow，dot3OamErrFramePeriodThreshold.aOAMLocalErrFramePeriodEvent dot3OamEventLogEntry.aOAMLocalErrFrameSecsSummaryConfig dot3OamErrFrameSecsSummaryWindow，dot3OamErrFrameSecssummaryThreshold.aOAMLocalErrFrameSecsSummaryEvent Dot3OAmeventGentry.AOAMRemoteErrSymperiondevelent Dot3OAmeventGentry.aOAMRemoteErrFramePeriodEvent Dot3OAmeventGentry.aOAMRemoteErrFrameSecsSummaryEvent Dot3OAmeventGentry.AOAMRemoteErrFrameStreamsDueToom.acOAMAdminControl dot3OamAdminState
There are no IEEE 802.3ah managed objects that are not reflected in this MIB Module in some manner.
没有IEEE 802.3ah管理的对象不会以某种方式反映在此MIB模块中。
The Ethernet OAM MIB objects of this memo focus on the OA capabilities introduced in [802.3ah]. The MIB objects are partitioned into six different MIB groups.
本备忘录中的以太网OAM MIB对象重点介绍了[802.3ah]中引入的OA功能。MIB对象被划分为六个不同的MIB组。
The dot3OamTable group manages the primary OAM objects of the Ethernet interface. This group controls the state and status of OA as well as the mode in which it operates.
dot3OamTable组管理以太网接口的主要OAM对象。该组控制OA的状态和状态以及其运行模式。
The dot3OamPeerTable maintains the current information on the status and configuration of the peer OAM entity on the Ethernet interface. Managed information includes the capabilities and function available on the peer OAM entity.
点对点OAM实体和对等点OAM实体的当前配置状态。托管信息包括对等OAM实体上可用的功能和功能。
The dot3OamLoopbackTable manages the loopback function introduced in [802.3ah]. This table controls enabling and disabling loopback, as well as indicating the loopback status of Ethernet OAM on this interface.
dot3OamLoopbackTable管理[802.3ah]中引入的环回功能。此表控制启用和禁用环回，以及指示此接口上以太网OAM的环回状态。
The dot3OamStatsTable maintains statistics on the number and type of Ethernet OAM frames being transmitted and received on the Ethernet interface.
dot3OamStatsTable维护以太网接口上传输和接收的以太网OAM帧的数量和类型的统计信息。
The dot3OamEventConfigTable defines the objects for managing the event notification capability available in Ethernet OAM. With Ethernet OAM, one device may send notifications to its peer devices whenever an important event happens on the local device. This table provides management of which events result in notifications via Ethernet OAM notifications and/or via SNMP notifications.
dot3OamEventConfigTable定义了用于管理以太网OAM中可用的事件通知功能的对象。使用以太网OAM，当本地设备上发生重要事件时，一个设备可以向其对等设备发送通知。此表提供了通过以太网OAM通知和/或SNMP通知产生通知的事件的管理。
The dot3OamEventLogTable manages the current status of local and remote events detected via Ethernet OAM. This table is updated whenever local events are detected by Ethernet OAM or whenever Ethernet OAM Event Notifications are received from the peer OA entity.
dot3OamEventLogTable管理通过以太网OAM检测到的本地和远程事件的当前状态。每当Ethernet OAM检测到本地事件或从对等OA实体接收到Ethernet OAM事件通知时，此表就会更新。
There are two notifications defined to report Ethernet OAM events (one for threshold crossing events, one for non-threshold crossing events). Both notifications are contained within the same conformance group.
定义了两个通知来报告以太网OAM事件（一个用于阈值交叉事件，一个用于非阈值交叉事件）。这两个通知都包含在同一个一致性组中。
DOT3-OAM-MIB DEFINITIONS ::= BEGIN
DOT3-OAM-MIB DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY, mib-2, OBJECT-TYPE, Counter32, Unsigned32, Integer32, NOTIFICATION-TYPE FROM SNMPv2-SMI -- from [RFC2578] TEXTUAL-CONVENTION, MacAddress, TimeStamp, TruthValue
从SNMPv2 SMI导入模块标识、mib-2、对象类型、计数器32、无符号32、整数32、通知类型——从[RFC2578]文本约定、MacAddress、时间戳、TruthValue
FROM SNMPv2-TC
-- from [RFC2579]
CounterBasedGauge64
FROM HCNUM-TC
-- from [RFC2856]
ifIndex
FROM IF-MIB
-- from [RFC2863]
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF;
FROM SNMPv2-TC
-- from [RFC2579]
CounterBasedGauge64
FROM HCNUM-TC
-- from [RFC2856]
ifIndex
FROM IF-MIB
-- from [RFC2863]
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF;
-- from [RFC2580]
--从[RFC2580]
dot3OamMIB MODULE-IDENTITY LAST-UPDATED "200706140000Z" -- June 14,2007" ORGANIZATION "IETF Ethernet Interfaces and Hub MIB Working Group" CONTACT-INFO "WG Charter: http://www.ietf.org/html.charters/hubmib-charter.html Mailing lists: General Discussion: hubmib@ietf.org To Subscribe: hubmib-requests@ietf.org In Body: subscribe your_email_address Chair: Bert Wijnen Alcatel-Lucent Email: bwijnen at alcatel-lucent dot com Editor: Matt Squire Hatteras Networks E-mail: msquire at hatterasnetworks dot com " DESCRIPTION "The MIB module for managing the new Ethernet OAM features introduced by the Ethernet in the First Mile taskforce (IEEE 802.3ah). The functionality presented here is based on IEEE 802.3ah [802.3ah], released in October, 2004. [802.3ah] was prepared as an addendum to the standing version of IEEE 802.3 [802.3-2002]. Since then, [802.3ah] has been merged into the base IEEE 802.3 specification in [802.3-2005].
dot3OamMIB模块标识最后更新“200706140000Z”--2007年6月14日“组织”IETF以太网接口和集线器MIB工作组“联系方式”工作组章程：http://www.ietf.org/html.charters/hubmib-charter.html 邮寄名单：一般性讨论：hubmib@ietf.org订阅：hubmib-requests@ietf.org正文：订阅您的电子邮件地址主席：伯特·维恩·阿尔卡特·朗讯电子邮件：阿尔卡特·朗讯网站编辑：马特·斯奎尔·哈特拉斯网络电子邮件：哈特拉斯网络网站的msquirecom“描述”MIB模块，用于管理第一英里任务组（IEEE 802.3ah）中以太网引入的新以太网OAM功能。这里介绍的功能基于2004年10月发布的IEEE 802.3ah[802.3ah]。[802.3ah]是作为IEEE 802.3[802.3-2002]常设版本的附录编制的。此后，[802.3ah]已在[802.3-2005]中并入基本IEEE 802.3规范。
In particular, this MIB focuses on the new OAM functions introduced in Clause 57 of [802.3ah]. The OAM functionality of Clause 57 is controlled by new management attributes introduced in Clause 30 of [802.3ah]. The OAM functions are not specific to any particular Ethernet physical layer, and can be generically applied to any Ethernet interface of [802.3-2002].
特别是，本MIB侧重于[802.3ah]第57条中引入的新OAM功能。第57条的OAM功能由[802.3ah]第30条中引入的新管理属性控制。OAM功能不特定于任何特定的以太网物理层，通常可应用于[802.3-2002]的任何以太网接口。
An Ethernet OAM protocol data unit is a valid Ethernet frame with a destination MAC address equal to the reserved MAC address for Slow Protocols (See 43B of [802.3ah]), a lengthOrType field equal to the reserved type for Slow Protocols, and a Slow Protocols subtype equal to that of the subtype reserved for Ethernet OAM. OAMPDU is used throughout this document as an abbreviation for Ethernet OAM protocol data unit.
以太网OAM协议数据单元是一个有效的以太网帧，目标MAC地址等于慢速协议的保留MAC地址（参见[802.3ah]的43B），lengthOrType字段等于慢速协议的保留类型，慢速协议子类型等于为以太网OAM保留的子类型。OAMPDU在本文档中用作以太网OAM协议数据单元的缩写。
The following reference is used throughout this MIB module:
在整个MIB模块中使用以下参考：
[802.3ah] refers to: IEEE Std 802.3ah-2004: 'Draft amendment to - Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 3: Carrier sense multiple access with collision detection (CSMA/CD) access method and physical layer specifications - Media Access Control Parameters, Physical Layers and Management Parameters for subscriber access networks', October 2004.
[802.3ah]参考：IEEE Std 802.3ah-2004:“信息技术-系统间电信和信息交换-局域网和城域网-特定要求-第3部分：带冲突检测的载波侦听多址接入（CSMA/CD）的修订草案”接入方法和物理层规范-用户接入网络的媒体接入控制参数、物理层和管理参数”，2004年10月。
[802.3-2002] refers to: IEEE Std 802.3-2002: 'Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 3: Carrier sense multiple access with collision detection (CSMA/CD) access method and physical layer specifications - Media Access Control Parameters, Physical Layers and Management Parameters for subscriber access networks', March 2002.
[802.3-2002]参考：IEEE标准802.3-2002:“信息技术-系统间电信和信息交换-局域网和城域网-特定要求-第3部分：带冲突检测的载波侦听多址接入（CSMA/CD）访问方法和物理层规范-用户访问网络的媒体访问控制参数、物理层和管理参数”，2002年3月。
[802.3-2005] refers to: IEEE Std 802.3-2005: 'Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 3: Carrier sense multiple access with collision detection (CSMA/CD) access method and physical layer specifications - Media Access Control Parameters, Physical Layers and Management Parameters for subscriber access networks', December 2005.
[802.3-2005]参考：IEEE标准802.3-2005:“信息技术-系统间电信和信息交换-局域网和城域网-特定要求-第3部分：带冲突检测的载波侦听多址接入（CSMA/CD）接入方法和物理层规范-用户接入网络的媒体接入控制参数、物理层和管理参数”，2005年12月。
[802-2001] refers to: 'IEEE Standard for LAN/MAN (Local Area Network/Metropolitan Area Network): Overview and Architecture', IEEE 802, June 2001.
[802-2001]参考：“局域网/城域网的IEEE标准：概述和体系结构”，IEEE 802，2001年6月。
Copyright (c) The IETF Trust (2007). This version of this MIB module is part of RFC 4878; See the RFC itself for full legal notices. "
版权所有（c）IETF信托基金（2007年）。此版本的MIB模块是RFC 4878的一部分；有关完整的法律通知，请参见RFC本身。"
REVISION "200706140000Z" -- June 14, 2007"
DESCRIPTION "Initial version, published as RFC 4878."
::= { mib-2 158 }
REVISION "200706140000Z" -- June 14, 2007"
DESCRIPTION "Initial version, published as RFC 4878."
::= { mib-2 158 }
-- -- Sections of the Ethernet OAM MIB
----以太网OAM MIB的各个部分
--
dot3OamNotifications OBJECT IDENTIFIER ::= { dot3OamMIB 0 }
dot3OamObjects OBJECT IDENTIFIER ::= { dot3OamMIB 1 }
dot3OamConformance OBJECT IDENTIFIER ::= { dot3OamMIB 2 }
--
dot3OamNotifications OBJECT IDENTIFIER ::= { dot3OamMIB 0 }
dot3OamObjects OBJECT IDENTIFIER ::= { dot3OamMIB 1 }
dot3OamConformance OBJECT IDENTIFIER ::= { dot3OamMIB 2 }
--
-- Textual conventions for the OAM MIB
--
EightOTwoOui ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"24-bit Organizationally Unique Identifier. Information on
OUIs can be found in IEEE 802-2001 [802-2001], Clause 9."
SYNTAX OCTET STRING(SIZE(3))
--
-- Textual conventions for the OAM MIB
--
EightOTwoOui ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"24-bit Organizationally Unique Identifier. Information on
OUIs can be found in IEEE 802-2001 [802-2001], Clause 9."
SYNTAX OCTET STRING(SIZE(3))
-- ***************************************************************
--
-- Ethernet OAM Control group
--
-- ***************************************************************
--
-- Ethernet OAM Control group
--
dot3OamTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3OamEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains the primary controls and status for the
OAM capabilities of an Ethernet-like interface. There will be
one row in this table for each Ethernet-like interface in the
system that supports the OAM functions defined in [802.3ah].
"
::= { dot3OamObjects 1 }
dot3OamTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3OamEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains the primary controls and status for the
OAM capabilities of an Ethernet-like interface. There will be
one row in this table for each Ethernet-like interface in the
system that supports the OAM functions defined in [802.3ah].
"
::= { dot3OamObjects 1 }
dot3OamEntry OBJECT-TYPE SYNTAX Dot3OamEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the table that contains information on the Ethernet OAM function for a single Ethernet like interface. Entries in the table are created automatically for each interface supporting Ethernet OAM. The status of the row entry can be determined from dot3OamOperStatus.
dot3OamEntry对象类型语法dot3OamEntry MAX-ACCESS不可访问状态当前描述“表中的一个条目，包含关于单个以太网类接口的以太网OAM功能的信息。表中的条目是为每个支持以太网OAM的接口自动创建的。行条目的状态可以从dot3OamOperStatus确定。
A dot3OamEntry is indexed in the dot3OamTable by the ifIndex
object of the Interfaces MIB.
"
INDEX { ifIndex }
::= { dot3OamTable 1 }
A dot3OamEntry is indexed in the dot3OamTable by the ifIndex
object of the Interfaces MIB.
"
INDEX { ifIndex }
::= { dot3OamTable 1 }
Dot3OamEntry ::=
SEQUENCE {
dot3OamAdminState INTEGER,
dot3OamOperStatus INTEGER,
dot3OamMode INTEGER,
dot3OamMaxOamPduSize Unsigned32,
dot3OamConfigRevision Unsigned32,
dot3OamFunctionsSupported BITS
}
Dot3OamEntry ::=
SEQUENCE {
dot3OamAdminState INTEGER,
dot3OamOperStatus INTEGER,
dot3OamMode INTEGER,
dot3OamMaxOamPduSize Unsigned32,
dot3OamConfigRevision Unsigned32,
dot3OamFunctionsSupported BITS
}
dot3OamAdminState OBJECT-TYPE
SYNTAX INTEGER {
enabled(1),
disabled(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object is used to provision the default administrative
OAM mode for this interface. This object represents the
desired state of OAM for this interface.
dot3OamAdminState OBJECT-TYPE
SYNTAX INTEGER {
enabled(1),
disabled(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object is used to provision the default administrative
OAM mode for this interface. This object represents the
desired state of OAM for this interface.
The dot3OamAdminState always starts in the disabled(2) state
until an explicit management action or configuration
information retained by the system causes a transition to the
enabled(1) state. When enabled(1), Ethernet OAM will attempt
to operate over this interface.
"
REFERENCE "[802.3ah], 30.3.6.1.2"
::= { dot3OamEntry 1 }
The dot3OamAdminState always starts in the disabled(2) state
until an explicit management action or configuration
information retained by the system causes a transition to the
enabled(1) state. When enabled(1), Ethernet OAM will attempt
to operate over this interface.
"
REFERENCE "[802.3ah], 30.3.6.1.2"
::= { dot3OamEntry 1 }
dot3OamOperStatus OBJECT-TYPE
SYNTAX INTEGER {
disabled(1),
linkFault(2),
passiveWait(3),
activeSendLocal(4),
sendLocalAndRemote(5),
sendLocalAndRemoteOk(6),
oamPeeringLocallyRejected(7),
oamPeeringRemotelyRejected(8),
operational(9),
nonOperHalfDuplex(10)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"At initialization and failure conditions, two OAM entities on
dot3OamOperStatus OBJECT-TYPE
SYNTAX INTEGER {
disabled(1),
linkFault(2),
passiveWait(3),
activeSendLocal(4),
sendLocalAndRemote(5),
sendLocalAndRemoteOk(6),
oamPeeringLocallyRejected(7),
oamPeeringRemotelyRejected(8),
operational(9),
nonOperHalfDuplex(10)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"At initialization and failure conditions, two OAM entities on
the same full-duplex Ethernet link begin a discovery phase to determine what OAM capabilities may be used on that link. The progress of this initialization is controlled by the OA sublayer.
同一条全双工以太网链路开始发现阶段，以确定该链路上可以使用哪些OAM功能。此初始化的进度由OA子层控制。
This value is always disabled(1) if OAM is disabled on this interface via the dot3OamAdminState.
如果通过dot3OamAdminState在此接口上禁用OAM，则此值始终处于禁用状态（1）。
If the link has detected a fault and is transmitting OAMPDUs with a link fault indication, the value is linkFault(2). Also, if the interface is not operational (ifOperStatus is not up(1)), linkFault(2) is returned. Note that the object ifOperStatus may not be up(1) as a result of link failure or administrative action (ifAdminState being down(2) or testing(3)).
如果链路检测到故障并正在传输带有链路故障指示的OAMPDU，则该值为linkFault（2）。此外，如果接口不可操作（ifOperStatus为not up（1）），则返回linkFault（2）。请注意，由于链路故障或管理操作（ifAdminState为down（2）或testing（3））的原因，对象IFOperateStatus可能不会处于up（1）状态。
The passiveWait(3) state is returned only by OAM entities in passive mode (dot3OamMode) and reflects the state in which the OAM entity is waiting to see if the peer device is OA capable. The activeSendLocal(4) value is used by active mode devices (dot3OamMode) and reflects the OAM entity actively trying to discover whether the peer has OAM capability but has not yet made that determination.
被动wait（3）状态仅由处于被动模式（dot3OamMode）的OAM实体返回，并反映OAM实体等待查看对等设备是否具有OA能力的状态。activeSendLocal（4）值由活动模式设备（dot3OamMode）使用，反映了OAM实体正在积极尝试发现对等方是否具有OAM功能，但尚未做出该确定。
The state sendLocalAndRemote(5) reflects that the local OA entity has discovered the peer but has not yet accepted or rejected the configuration of the peer. The local device can, for whatever reason, decide that the peer device is unacceptable and decline OAM peering. If the local OAM entity rejects the peer OAM entity, the state becomes oamPeeringLocallyRejected(7). If the OAM peering is allowed by the local device, the state moves to sendLocalAndRemoteOk(6). Note that both the sendLocalAndRemote(5) and oamPeeringLocallyRejected(7) states fall within the state SEND_LOCAL_REMOTE of the Discovery state diagram [802.3ah, Figure 57-5], with the difference being whether the local OAM client has actively rejected the peering or has just not indicated any decision yet. Whether a peering decision has been made is indicated via the local flags field in the OAMPDU (reflected in the aOAMLocalFlagsField of 30.3.6.1.10).
状态sendLocalAndRemote（5）反映本地OA实体已发现对等方，但尚未接受或拒绝对等方的配置。无论出于何种原因，本地设备都可以确定对等设备不可接受并拒绝OAM对等。如果本地OAM实体拒绝对等OAM实体，则状态变为oamPeeringLocallyRejected（7）。如果本地设备允许OAM对等，则状态移动到sendLocalAndRemoteOk（6）。请注意，sendLocalAndRemote（5）和OamperingLocalyRejected（7）状态都属于发现状态图[802.3ah，图57-5]的状态SEND_LOCAL_REMOTE]，区别在于本地OAM客户端是否已主动拒绝对等，或者只是尚未指示任何决定。是否已做出对等决定通过OAMPDU中的local flags字段表示（反映在30.3.6.1.10的aOAMLocalFlagsField中）。
If the remote OAM entity rejects the peering, the state becomes oamPeeringRemotelyRejected(8). Note that both the sendLocalAndRemoteOk(6) and oamPeeringRemotelyRejected(8) states fall within the state SEND_LOCAL_REMOTE_OK of the Discovery state diagram [802.3ah, Figure 57-5], with the difference being whether the remote OAM client has rejected
如果远程OAM实体拒绝对等，则状态变为oamPeeringRemotelyRejected（8）。请注意，sendLocalAndRemoteOk（6）和OamperingRemoteLyrejected（8）状态都属于发现状态图[802.3ah，图57-5]的状态SEND_LOCAL_REMOTE_OK，区别在于远程OAM客户端是否已拒绝
the peering or has just not yet decided. This is indicated via the remote flags field in the OAMPDU (reflected in the aOAMRemoteFlagsField of 30.3.6.1.11).
窥视者还没有决定。这通过OAMPDU中的远程标志字段来表示（反映在30.3.6.1.11的aOAMRemoteFlagsField中）。
When the local OAM entity learns that both it and the remote OAM entity have accepted the peering, the state moves to operational(9) corresponding to the SEND_ANY state of the Discovery state diagram [802.3ah, Figure 57-5].
当本地OAM实体得知它和远程OAM实体都已接受对等时，状态移动到与发现状态图的任何状态对应的操作（9）[802.3ah，图57-5]。
Since Ethernet OAM functions are not designed to work
completely over half-duplex interfaces, the value
nonOperHalfDuplex(10) is returned whenever Ethernet OAM is
enabled (dot3OamAdminState is enabled(1)), but the interface
is in half-duplex operation.
"
REFERENCE "[802.3ah], 30.3.6.1.4, 30.3.6.1.10, 30.3.6.1.11"
::= { dot3OamEntry 2 }
Since Ethernet OAM functions are not designed to work
completely over half-duplex interfaces, the value
nonOperHalfDuplex(10) is returned whenever Ethernet OAM is
enabled (dot3OamAdminState is enabled(1)), but the interface
is in half-duplex operation.
"
REFERENCE "[802.3ah], 30.3.6.1.4, 30.3.6.1.10, 30.3.6.1.11"
::= { dot3OamEntry 2 }
dot3OamMode OBJECT-TYPE
SYNTAX INTEGER {
passive(1),
active(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object configures the mode of OAM operation for this
Ethernet-like interface. OAM on Ethernet interfaces may be in
'active' mode or 'passive' mode. These two modes differ in
that active mode provides additional capabilities to initiate
monitoring activities with the remote OAM peer entity, while
passive mode generally waits for the peer to initiate OA
actions with it. As an example, an active OAM entity can put
the remote OAM entity in a loopback state, where a passive OA
entity cannot.
dot3OamMode OBJECT-TYPE
SYNTAX INTEGER {
passive(1),
active(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object configures the mode of OAM operation for this
Ethernet-like interface. OAM on Ethernet interfaces may be in
'active' mode or 'passive' mode. These two modes differ in
that active mode provides additional capabilities to initiate
monitoring activities with the remote OAM peer entity, while
passive mode generally waits for the peer to initiate OA
actions with it. As an example, an active OAM entity can put
the remote OAM entity in a loopback state, where a passive OA
entity cannot.
The default value of dot3OamMode is dependent on the type of system on which this Ethernet-like interface resides. The default value should be 'active(2)' unless it is known that this system should take on a subservient role to the other device connected over this interface.
dot3OamMode的默认值取决于该类以太网接口所在的系统类型。默认值应为“active（2）”，除非已知此系统应承担通过此接口连接的其他设备的从属角色。
Changing this value results in incrementing the configuration revision field of locally generated OAMPDUs (30.3.6.1.12) and potentially re-doing the OAM discovery process if the dot3OamOperStatus was already operational(9). " REFERENCE "[802.3ah], 30.3.6.1.3"
更改此值将导致本地生成的OAMPDU（30.3.6.1.12）的配置修订字段增加，并且如果dot3OamOperStatus已经运行，则可能会重新执行OAM发现过程（9）。“参考”[802.3ah]，30.3.6.1.3”
::= { dot3OamEntry 3 }
::= { dot3OamEntry 3 }
dot3OamMaxOamPduSize OBJECT-TYPE
SYNTAX Unsigned32 (64..1518)
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The largest OAMPDU that the OAM entity supports. OA
entities exchange maximum OAMPDU sizes and negotiate to use
the smaller of the two maximum OAMPDU sizes between the peers.
This value is determined by the local implementation.
"
REFERENCE "[802.3ah], 30.3.6.1.8"
::= { dot3OamEntry 4 }
dot3OamMaxOamPduSize OBJECT-TYPE
SYNTAX Unsigned32 (64..1518)
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The largest OAMPDU that the OAM entity supports. OA
entities exchange maximum OAMPDU sizes and negotiate to use
the smaller of the two maximum OAMPDU sizes between the peers.
This value is determined by the local implementation.
"
REFERENCE "[802.3ah], 30.3.6.1.8"
::= { dot3OamEntry 4 }
dot3OamConfigRevision OBJECT-TYPE
SYNTAX Unsigned32(0..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The configuration revision of the OAM entity as reflected in
the latest OAMPDU sent by the OAM entity. The config revision
is used by OAM entities to indicate that configuration changes
have occurred, which might require the peer OAM entity to
re-evaluate whether OAM peering is allowed.
"
REFERENCE "[802.3ah], 30.3.6.1.12"
::= { dot3OamEntry 5 }
dot3OamConfigRevision OBJECT-TYPE
SYNTAX Unsigned32(0..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The configuration revision of the OAM entity as reflected in
the latest OAMPDU sent by the OAM entity. The config revision
is used by OAM entities to indicate that configuration changes
have occurred, which might require the peer OAM entity to
re-evaluate whether OAM peering is allowed.
"
REFERENCE "[802.3ah], 30.3.6.1.12"
::= { dot3OamEntry 5 }
dot3OamFunctionsSupported OBJECT-TYPE
SYNTAX BITS {
unidirectionalSupport (0),
loopbackSupport(1),
eventSupport(2),
variableSupport(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The OAM functions supported on this Ethernet-like interface.
OAM consists of separate functional sets beyond the basic
discovery process that is always required. These functional
groups can be supported independently by any implementation.
These values are communicated to the peer via the local
configuration field of Information OAMPDUs.
dot3OamFunctionsSupported OBJECT-TYPE
SYNTAX BITS {
unidirectionalSupport (0),
loopbackSupport(1),
eventSupport(2),
variableSupport(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The OAM functions supported on this Ethernet-like interface.
OAM consists of separate functional sets beyond the basic
discovery process that is always required. These functional
groups can be supported independently by any implementation.
These values are communicated to the peer via the local
configuration field of Information OAMPDUs.
Setting 'unidirectionalSupport(0)' indicates that the OA
设置“单向支持（0）”表示OA
entity supports the transmission of OAMPDUs on links that are
operating in unidirectional mode (traffic flowing in one
direction only). Setting 'loopbackSupport(1)' indicates that
the OAM entity can initiate and respond to loopback commands.
Setting 'eventSupport(2)' indicates that the OAM entity can
send and receive Event Notification OAMPDUs. Setting
'variableSupport(3)' indicates that the OAM entity can send
and receive Variable Request and Response OAMPDUs.
"
REFERENCE "[802.3ah], 30.3.6.1.6"
::= { dot3OamEntry 6 }
entity supports the transmission of OAMPDUs on links that are
operating in unidirectional mode (traffic flowing in one
direction only). Setting 'loopbackSupport(1)' indicates that
the OAM entity can initiate and respond to loopback commands.
Setting 'eventSupport(2)' indicates that the OAM entity can
send and receive Event Notification OAMPDUs. Setting
'variableSupport(3)' indicates that the OAM entity can send
and receive Variable Request and Response OAMPDUs.
"
REFERENCE "[802.3ah], 30.3.6.1.6"
::= { dot3OamEntry 6 }
-- ***************************************************************
--
-- Ethernet OAM Peer group
--
-- ***************************************************************
--
-- Ethernet OAM Peer group
--
dot3OamPeerTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3OamPeerEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains information about the OAM peer for a
particular Ethernet-like interface. OAM entities communicate
with a single OAM peer entity on Ethernet links on which OA
is enabled and operating properly. There is one entry in this
table for each entry in the dot3OamTable for which information
on the peer OAM entity is available.
"
::= { dot3OamObjects 2 }
dot3OamPeerTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3OamPeerEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains information about the OAM peer for a
particular Ethernet-like interface. OAM entities communicate
with a single OAM peer entity on Ethernet links on which OA
is enabled and operating properly. There is one entry in this
table for each entry in the dot3OamTable for which information
on the peer OAM entity is available.
"
::= { dot3OamObjects 2 }
dot3OamPeerEntry OBJECT-TYPE SYNTAX Dot3OamPeerEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the table containing information on the peer OA entity for a single Ethernet-like interface.
DOT3OAMPERENTRY对象类型语法DOT3OAMPERENTRY MAX-ACCESS not ACCESS STATUS current DESCRIPTION“表中的一个条目，包含单个以太网类接口的对等OA实体的信息。
Note that there is at most one OAM peer for each Ethernet-like interface. Entries are automatically created when information about the OAM peer entity becomes available, and automatically deleted when the OAM peer entity is no longer in communication. Peer information is not available when dot3OamOperStatus is disabled(1), linkFault(2), passiveWait(3), activeSendLocal(4), or nonOperHalfDuplex(10). " INDEX { ifIndex }
请注意，每个类似以太网的接口最多有一个OAM对等点。当有关OAM对等实体的信息可用时，条目会自动创建，当OAM对等实体不再通信时，条目会自动删除。当dot3OamOperStatus被禁用（1）、链路故障（2）、被动WAIT（3）、activeSendLocal（4）或非操作半双工（10）时，对等信息不可用。“索引{ifIndex}
::= { dot3OamPeerTable 1 }
::= { dot3OamPeerTable 1 }
Dot3OamPeerEntry ::=
SEQUENCE {
dot3OamPeerMacAddress MacAddress,
dot3OamPeerVendorOui EightOTwoOui,
dot3OamPeerVendorInfo Unsigned32,
dot3OamPeerMode INTEGER,
dot3OamPeerMaxOamPduSize Unsigned32,
dot3OamPeerConfigRevision Unsigned32,
dot3OamPeerFunctionsSupported BITS
}
Dot3OamPeerEntry ::=
SEQUENCE {
dot3OamPeerMacAddress MacAddress,
dot3OamPeerVendorOui EightOTwoOui,
dot3OamPeerVendorInfo Unsigned32,
dot3OamPeerMode INTEGER,
dot3OamPeerMaxOamPduSize Unsigned32,
dot3OamPeerConfigRevision Unsigned32,
dot3OamPeerFunctionsSupported BITS
}
dot3OamPeerMacAddress OBJECT-TYPE
SYNTAX MacAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The MAC address of the peer OAM entity. The MAC address is
derived from the most recently received OAMPDU.
"
REFERENCE "[802.3ah], 30.3.6.1.5."
::= { dot3OamPeerEntry 1 }
dot3OamPeerMacAddress OBJECT-TYPE
SYNTAX MacAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The MAC address of the peer OAM entity. The MAC address is
derived from the most recently received OAMPDU.
"
REFERENCE "[802.3ah], 30.3.6.1.5."
::= { dot3OamPeerEntry 1 }
dot3OamPeerVendorOui OBJECT-TYPE
SYNTAX EightOTwoOui
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The OUI of the OAM peer as reflected in the latest
Information OAMPDU received with a Local Information TLV. The
OUI can be used to identify the vendor of the remote OA
entity. This value is initialized to three octets of zero
before any Local Information TLV is received.
"
REFERENCE "[802.3ah], 30.3.6.1.16."
::= { dot3OamPeerEntry 2 }
dot3OamPeerVendorOui OBJECT-TYPE
SYNTAX EightOTwoOui
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The OUI of the OAM peer as reflected in the latest
Information OAMPDU received with a Local Information TLV. The
OUI can be used to identify the vendor of the remote OA
entity. This value is initialized to three octets of zero
before any Local Information TLV is received.
"
REFERENCE "[802.3ah], 30.3.6.1.16."
::= { dot3OamPeerEntry 2 }
dot3OamPeerVendorInfo OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "The Vendor Info of the OAM peer as reflected in the latest Information OAMPDU received with a Local Information TLV. The semantics of the Vendor Information field is proprietary and specific to the vendor (identified by the dot3OamPeerVendorOui). This information could, for example,
DOT3OAMPERVENDORINFO对象类型语法Unsigned32 MAX-ACCESS只读状态当前描述“OAM对等方的供应商信息，反映在OAMPDU随本地信息TLV接收的最新信息中。供应商信息字段的语义是专有的，特定于供应商（由DOT3OAMPERVENDOROUI标识）。例如，该信息可能，
be used to identify a specific product or product family.
This value is initialized to zero before any Local
Information TLV is received.
"
REFERENCE "[802.3ah], 30.3.6.1.17."
::= { dot3OamPeerEntry 3 }
be used to identify a specific product or product family.
This value is initialized to zero before any Local
Information TLV is received.
"
REFERENCE "[802.3ah], 30.3.6.1.17."
::= { dot3OamPeerEntry 3 }
dot3OamPeerMode OBJECT-TYPE
SYNTAX INTEGER {
passive(1),
active(2),
unknown(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The mode of the OAM peer as reflected in the latest
Information OAMPDU received with a Local Information TLV. The
mode of the peer can be determined from the Configuration
field in the Local Information TLV of the last Information
OAMPDU received from the peer. The value is unknown(3)
whenever no Local Information TLV has been received. The
values of active(2) and passive(1) are returned when a Local
Information TLV has been received indicating that the peer is
in active or passive mode, respectively.
"
REFERENCE "[802.3ah], 30.3.6.1.7."
::= { dot3OamPeerEntry 4 }
dot3OamPeerMode OBJECT-TYPE
SYNTAX INTEGER {
passive(1),
active(2),
unknown(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The mode of the OAM peer as reflected in the latest
Information OAMPDU received with a Local Information TLV. The
mode of the peer can be determined from the Configuration
field in the Local Information TLV of the last Information
OAMPDU received from the peer. The value is unknown(3)
whenever no Local Information TLV has been received. The
values of active(2) and passive(1) are returned when a Local
Information TLV has been received indicating that the peer is
in active or passive mode, respectively.
"
REFERENCE "[802.3ah], 30.3.6.1.7."
::= { dot3OamPeerEntry 4 }
dot3OamPeerMaxOamPduSize OBJECT-TYPE
SYNTAX Unsigned32 (0 | 64..1518)
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum size of OAMPDU supported by the peer as reflected
in the latest Information OAMPDU received with a Local
Information TLV. Ethernet OAM on this interface must not use
OAMPDUs that exceed this size. The maximum OAMPDU size can be
determined from the PDU Configuration field of the Local
Information TLV of the last Information OAMPDU received from
the peer. A value of zero is returned if no Local Information
TLV has been received. Otherwise, the value of the OAM peer's
maximum OAMPDU size is returned in this value.
"
REFERENCE "[802.3ah], 30.3.6.1.9."
::= { dot3OamPeerEntry 5 }
dot3OamPeerMaxOamPduSize OBJECT-TYPE
SYNTAX Unsigned32 (0 | 64..1518)
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum size of OAMPDU supported by the peer as reflected
in the latest Information OAMPDU received with a Local
Information TLV. Ethernet OAM on this interface must not use
OAMPDUs that exceed this size. The maximum OAMPDU size can be
determined from the PDU Configuration field of the Local
Information TLV of the last Information OAMPDU received from
the peer. A value of zero is returned if no Local Information
TLV has been received. Otherwise, the value of the OAM peer's
maximum OAMPDU size is returned in this value.
"
REFERENCE "[802.3ah], 30.3.6.1.9."
::= { dot3OamPeerEntry 5 }
dot3OamPeerConfigRevision OBJECT-TYPE
SYNTAX Unsigned32(0..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The configuration revision of the OAM peer as reflected in
the latest OAMPDU. This attribute is changed by the peer
whenever it has a local configuration change for Ethernet OA
on this interface. The configuration revision can be
determined from the Revision field of the Local Information
TLV of the most recently received Information OAMPDU with
a Local Information TLV. A value of zero is returned if
no Local Information TLV has been received.
"
REFERENCE "[802.3ah], 30.3.6.1.13."
::= { dot3OamPeerEntry 6 }
dot3OamPeerConfigRevision OBJECT-TYPE
SYNTAX Unsigned32(0..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The configuration revision of the OAM peer as reflected in
the latest OAMPDU. This attribute is changed by the peer
whenever it has a local configuration change for Ethernet OA
on this interface. The configuration revision can be
determined from the Revision field of the Local Information
TLV of the most recently received Information OAMPDU with
a Local Information TLV. A value of zero is returned if
no Local Information TLV has been received.
"
REFERENCE "[802.3ah], 30.3.6.1.13."
::= { dot3OamPeerEntry 6 }
dot3OamPeerFunctionsSupported OBJECT-TYPE
SYNTAX BITS {
unidirectionalSupport (0),
loopbackSupport(1),
eventSupport(2),
variableSupport(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The OAM functions supported on this Ethernet-like interface.
OAM consists of separate functionality sets above the basic
discovery process. This value indicates the capabilities of
the peer OAM entity with respect to these functions. This
value is initialized so all bits are clear.
dot3OamPeerFunctionsSupported OBJECT-TYPE
SYNTAX BITS {
unidirectionalSupport (0),
loopbackSupport(1),
eventSupport(2),
variableSupport(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The OAM functions supported on this Ethernet-like interface.
OAM consists of separate functionality sets above the basic
discovery process. This value indicates the capabilities of
the peer OAM entity with respect to these functions. This
value is initialized so all bits are clear.
If unidirectionalSupport(0) is set, then the peer OAM entity supports sending OAM frames on Ethernet interfaces when the receive path is known to be inoperable. If loopbackSupport(1) is set, then the peer OAM entity can send and receive OAM loopback commands. If eventSupport(2) is set, then the peer OAM entity can send and receive event OAMPDUs to signal various error conditions. If variableSupport(3) is set, then the peer OAM entity can send and receive variable requests to monitor the attribute value as described in Clause 57 of [802.3ah].
如果设置了单向支持（0），则当已知接收路径不可用时，对等OAM实体支持在以太网接口上发送OAM帧。如果设置了loopbackSupport（1），则对等OAM实体可以发送和接收OAM环回命令。如果设置了eventSupport（2），则对等OAM实体可以发送和接收事件OAMPDU以发出各种错误条件的信号。如果设置了variableSupport（3），则对等OAM实体可以发送和接收可变请求，以监控属性值，如[802.3ah]第57条所述。
The capabilities of the OAM peer can be determined from the configuration field of the Local Information TLV of the most recently received Information OAMPDU with a Local Information TLV. All zeros are returned if no Local Information TLV has
OAM对等方的能力可以从具有本地信息TLV的最近接收的信息OAMPDU的本地信息TLV的配置字段来确定。如果TLV没有本地信息，则返回所有零
yet been received.
"
REFERENCE "[802.3ah], REFERENCE 30.3.6.1.7."
::= { dot3OamPeerEntry 7 }
yet been received.
"
REFERENCE "[802.3ah], REFERENCE 30.3.6.1.7."
::= { dot3OamPeerEntry 7 }
-- ***************************************************************
--
-- Ethernet OAM Loopback group
--
-- ***************************************************************
--
-- Ethernet OAM Loopback group
--
dot3OamLoopbackTable OBJECT-TYPE SYNTAX SEQUENCE OF Dot3OamLoopbackEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains controls for the loopback state of the local link as well as indicates the status of the loopback function. There is one entry in this table for each entry in dot3OamTable that supports loopback functionality (where dot3OamFunctionsSupported includes the loopbackSupport bit set).
Dot3OamLoopbackEntry MAX-ACCESS的dot3OamLoopbackTable对象类型语法序列不可访问状态当前说明“此表包含本地链路环回状态的控件，并指示环回功能的状态。对于支持环回功能的dot3OamTable中的每个条目，此表中有一个条目（其中dot3OamFunctionsSupported包括环回支持位集）。
Loopback can be used to place the remote OAM entity in a state
where every received frame (except OAMPDUs) is echoed back
over the same interface on which they were received. In this
state, at the remote entity, 'normal' traffic is disabled as
only the looped back frames are transmitted on the interface.
Loopback is thus an intrusive operation that prohibits normal
data flow and should be used accordingly.
"
::= { dot3OamObjects 3 }
Loopback can be used to place the remote OAM entity in a state
where every received frame (except OAMPDUs) is echoed back
over the same interface on which they were received. In this
state, at the remote entity, 'normal' traffic is disabled as
only the looped back frames are transmitted on the interface.
Loopback is thus an intrusive operation that prohibits normal
data flow and should be used accordingly.
"
::= { dot3OamObjects 3 }
dot3OamLoopbackEntry OBJECT-TYPE
SYNTAX Dot3OamLoopbackEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the table, containing information on the loopback
status for a single Ethernet-like interface. Entries in the
table are automatically created whenever the local OAM entity
supports loopback capabilities. The loopback status on the
interface can be determined from the dot3OamLoopbackStatus
object.
"
INDEX { ifIndex }
::= { dot3OamLoopbackTable 1 }
dot3OamLoopbackEntry OBJECT-TYPE
SYNTAX Dot3OamLoopbackEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the table, containing information on the loopback
status for a single Ethernet-like interface. Entries in the
table are automatically created whenever the local OAM entity
supports loopback capabilities. The loopback status on the
interface can be determined from the dot3OamLoopbackStatus
object.
"
INDEX { ifIndex }
::= { dot3OamLoopbackTable 1 }
Dot3OamLoopbackEntry ::=
Dot3OamLoopbackEntry ::=
SEQUENCE {
dot3OamLoopbackStatus INTEGER,
dot3OamLoopbackIgnoreRx INTEGER
}
SEQUENCE {
dot3OamLoopbackStatus INTEGER,
dot3OamLoopbackIgnoreRx INTEGER
}
dot3OamLoopbackStatus OBJECT-TYPE
SYNTAX INTEGER {
-- all values, except where noted, can be read
-- but cannot be written
noLoopback (1),
dot3OamLoopbackStatus OBJECT-TYPE
SYNTAX INTEGER {
-- all values, except where noted, can be read
-- but cannot be written
noLoopback (1),
-- initiatingLoopback can be read or written initiatingLoopback (2), remoteLoopback (3),
--initiatingLoopback可以读或写initiatingLoopback（2）、remoteLoopback（3），
-- terminatingLoopback can be read or written terminatingLoopback (4), localLoopback (5), unknown (6) } MAX-ACCESS read-write STATUS current DESCRIPTION "The loopback status of the OAM entity. This status is determined by a combination of the local parser and multiplexer states, the remote parser and multiplexer states, as well as by the actions of the local OAM client. When operating in normal mode with no loopback in progress, the status reads noLoopback(1).
--TerminationLoopback可以读或写TerminationLoopback（4）、localLoopback（5）、unknown（6）}MAX-ACCESS读写状态当前描述“OAM实体的环回状态。此状态由本地解析器和多路复用器状态、远程解析器和多路复用器状态以及本地OAM客户端的操作的组合确定。在正常模式下运行且没有进行环回时，状态为noLoopback（1）。
The values initiatingLoopback(2) and terminatingLoopback(4) can be read or written. The other values can only be read - they can never be written. Writing initiatingLoopback causes the local OAM entity to start the loopback process with its peer. This value can only be written when the status is noLoopback(1). Writing the value initiatingLoopback(2) in any other state has no effect. When in remoteLoopback(3), writing terminatingLoopback(4) causes the local OAM entity to initiate the termination of the loopback state. Writing terminatingLoopack(4) in any other state has no effect.
可以读取或写入启动环回（2）和终止环回（4）的值。其他值只能读取-它们永远无法写入。写入initiatingLoopback会导致本地OAM实体与其对等实体启动环回进程。仅当状态为noLoopback（1）时，才能写入此值。在任何其他状态下写入值initiatingLoopback（2）无效。在remoteLoopback（3）中，写入terminatingLoopback（4）会导致本地OAM实体启动环回状态的终止。在任何其他状态下写入terminatingLoopack（4）无效。
If the OAM client initiates a loopback and has sent a Loopback OAMPDU and is waiting for a response, where the local parser and multiplexer states are DISCARD (see [802.3ah, 57.2.11.1]), the status is 'initiatingLoopback'. In this case, the local OAM entity has yet to receive any acknowledgment that the remote OAM entity has received its loopback command request.
如果OAM客户端发起环回并发送了环回OAMPDU，并且正在等待响应，其中本地解析器和多路复用器状态为丢弃（参见[802.3ah，57.2.11.1]），则状态为“initiatingLoopback”。在这种情况下，本地OAM实体尚未收到远程OAM实体已收到其环回命令请求的任何确认。
If the local OAM client knows that the remote OAM entity is in loopback mode (via the remote state information as described in [802.3ah, 57.2.11.1, 30.3.6.1.15]), the status is remoteLoopback(3). If the local OAM client is in the process of terminating the remote loopback [802.3ah, 57.2.11.3, 30.3.6.1.14] with its local multiplexer and parser states in DISCARD, the status is terminatingLoopback(4). If the remote OAM client has put the local OAM entity in loopback mode as indicated by its local parser state, the status is localLoopback(5).
如果本地OAM客户端知道远程OAM实体处于环回模式（通过[802.3ah，57.2.11.1，30.3.6.1.15]中所述的远程状态信息），则状态为remoteLoopback（3）。如果本地OAM客户端正在终止远程环回[802.3ah，57.2.11.3，30.3.6.1.14]，且其本地多路复用器和解析器状态为DISCARD，则状态为terminatingLoopback（4）。如果远程OAM客户端已将本地OAM实体置于由其本地解析器状态指示的环回模式，则状态为localLoopback（5）。
The unknown(6) status indicates that the parser and multiplexer combination is unexpected. This status may be returned if the OAM loopback is in a transition state but should not persist.
未知（6）状态表示解析器和多路复用器的组合是意外的。如果OAM环回处于转换状态但不应持续，则可能会返回此状态。
The values of this attribute correspond to the following values of the local and remote parser and multiplexer states.
此多路复用器的本地和远程属性值对应于此多路复用器的值。
value LclPrsr LclMux RmtPrsr RmtMux
noLoopback FWD FWD FWD FWD
initLoopback DISCARD DISCARD FWD FWD
rmtLoopback DISCARD FWD LPBK DISCARD
tmtngLoopback DISCARD DISCARD LPBK DISCARD
lclLoopback LPBK DISCARD DISCARD FWD
unknown *** any other combination ***
"
REFERENCE "[802.3ah], REFERENCE 57.2.11, 30.3.61.14,
30.3.6.1.15"
::= { dot3OamLoopbackEntry 1 }
value LclPrsr LclMux RmtPrsr RmtMux
noLoopback FWD FWD FWD FWD
initLoopback DISCARD DISCARD FWD FWD
rmtLoopback DISCARD FWD LPBK DISCARD
tmtngLoopback DISCARD DISCARD LPBK DISCARD
lclLoopback LPBK DISCARD DISCARD FWD
unknown *** any other combination ***
"
REFERENCE "[802.3ah], REFERENCE 57.2.11, 30.3.61.14,
30.3.6.1.15"
::= { dot3OamLoopbackEntry 1 }
dot3OamLoopbackIgnoreRx OBJECT-TYPE
SYNTAX INTEGER { ignore(1), process(2) }
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Since OAM loopback is a disruptive operation (user traffic
does not pass), this attribute provides a mechanism to provide
controls over whether received OAM loopback commands are
processed or ignored. When the value is ignore(1), received
loopback commands are ignored. When the value is process(2),
OAM loopback commands are processed. The default value is to
ignore loopback commands (ignore(1)).
"
REFERENCE "[802.3ah], REFERENCE 57.2.11, 30.3.61.14,
30.3.6.1.15"
::= { dot3OamLoopbackEntry 2 }
dot3OamLoopbackIgnoreRx OBJECT-TYPE
SYNTAX INTEGER { ignore(1), process(2) }
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Since OAM loopback is a disruptive operation (user traffic
does not pass), this attribute provides a mechanism to provide
controls over whether received OAM loopback commands are
processed or ignored. When the value is ignore(1), received
loopback commands are ignored. When the value is process(2),
OAM loopback commands are processed. The default value is to
ignore loopback commands (ignore(1)).
"
REFERENCE "[802.3ah], REFERENCE 57.2.11, 30.3.61.14,
30.3.6.1.15"
::= { dot3OamLoopbackEntry 2 }
-- ***************************************************************
--
-- Ethernet OAM Statistics group
--
-- ***************************************************************
--
-- Ethernet OAM Statistics group
--
dot3OamStatsTable OBJECT-TYPE SYNTAX SEQUENCE OF Dot3OamStatsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains statistics for the OAM function on a particular Ethernet-like interface. There is an entry in the table for every entry in the dot3OamTable.
dot3OamStatsTable Dot3OamStatsEntry MAX-ACCESS的对象类型语法序列不可访问状态当前描述“此表包含特定类以太网接口上OAM函数的统计信息。表中有一个条目对应于dot3OamTable中的每个条目。
The counters in this table are defined as 32-bit entries to
match the counter size as defined in [802.3ah]. Given that
the OA protocol is a slow protocol, the counters increment at
a slow rate.
"
::= { dot3OamObjects 4 }
The counters in this table are defined as 32-bit entries to
match the counter size as defined in [802.3ah]. Given that
the OA protocol is a slow protocol, the counters increment at
a slow rate.
"
::= { dot3OamObjects 4 }
dot3OamStatsEntry OBJECT-TYPE
SYNTAX Dot3OamStatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the table containing statistics information on
the Ethernet OAM function for a single Ethernet-like
interface. Entries are automatically created for every entry
in the dot3OamTable. Counters are maintained across
transitions in dot3OamOperStatus.
"
INDEX { ifIndex }
::= { dot3OamStatsTable 1 }
dot3OamStatsEntry OBJECT-TYPE
SYNTAX Dot3OamStatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the table containing statistics information on
the Ethernet OAM function for a single Ethernet-like
interface. Entries are automatically created for every entry
in the dot3OamTable. Counters are maintained across
transitions in dot3OamOperStatus.
"
INDEX { ifIndex }
::= { dot3OamStatsTable 1 }
Dot3OamStatsEntry ::=
SEQUENCE {
dot3OamInformationTx Counter32,
dot3OamInformationRx Counter32,
dot3OamUniqueEventNotificationTx Counter32,
dot3OamUniqueEventNotificationRx Counter32,
dot3OamDuplicateEventNotificationTx Counter32,
dot3OamDuplicateEventNotificationRx Counter32,
dot3OamLoopbackControlTx Counter32,
dot3OamLoopbackControlRx Counter32,
dot3OamVariableRequestTx Counter32,
dot3OamVariableRequestRx Counter32,
dot3OamVariableResponseTx Counter32,
Dot3OamStatsEntry ::=
SEQUENCE {
dot3OamInformationTx Counter32,
dot3OamInformationRx Counter32,
dot3OamUniqueEventNotificationTx Counter32,
dot3OamUniqueEventNotificationRx Counter32,
dot3OamDuplicateEventNotificationTx Counter32,
dot3OamDuplicateEventNotificationRx Counter32,
dot3OamLoopbackControlTx Counter32,
dot3OamLoopbackControlRx Counter32,
dot3OamVariableRequestTx Counter32,
dot3OamVariableRequestRx Counter32,
dot3OamVariableResponseTx Counter32,
dot3OamVariableResponseRx Counter32, dot3OamOrgSpecificTx Counter32, dot3OamOrgSpecificRx Counter32, dot3OamUnsupportedCodesTx Counter32, dot3OamUnsupportedCodesRx Counter32, dot3OamFramesLostDueToOam Counter32 }
dot3OamVariableResponseRx计数器32、dot3OamOrgSpecificTx计数器32、dot3OamOrgSpecificRx计数器32、dot3OamUnsupportedCodesTx计数器32、dot3OamUnsupportedCodesRx计数器32、dot3OamFramesLostDueToOam计数器32}
dot3OamInformationTx OBJECT-TYPE SYNTAX Counter32 UNITS "frames" MAX-ACCESS read-only STATUS current DESCRIPTION "A count of the number of Information OAMPDUs transmitted on this interface.
dot3OamInformationTx对象类型语法计数器32个单元“帧”MAX-ACCESS只读状态当前描述“此接口上传输的信息OAMPDU数。
Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime. "
REFERENCE "[802.3ah], 30.3.6.1.20."
::= { dot3OamStatsEntry 1 }
Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime. "
REFERENCE "[802.3ah], 30.3.6.1.20."
::= { dot3OamStatsEntry 1 }
dot3OamInformationRx OBJECT-TYPE SYNTAX Counter32 UNITS "frames" MAX-ACCESS read-only STATUS current DESCRIPTION "A count of the number of Information OAMPDUs received on this interface.
dot3OamInformationRx对象类型语法计数器32个单元“帧”MAX-ACCESS只读状态当前描述“OAMPDU在此接口上接收的信息数量计数。
Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime.
"
REFERENCE "[802.3ah], 30.3.6.1.21."
::= { dot3OamStatsEntry 2 }
Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime.
"
REFERENCE "[802.3ah], 30.3.6.1.21."
::= { dot3OamStatsEntry 2 }
dot3OamUniqueEventNotificationTx OBJECT-TYPE SYNTAX Counter32 UNITS "frames" MAX-ACCESS read-only STATUS current DESCRIPTION "A count of the number of unique Event OAMPDUs transmitted on this interface. Event Notifications may be sent in duplicate to increase the probability of successfully being received,
dot3OamUniqueEventNotificationTx对象类型语法计数器32个单元“帧”最大访问只读状态当前描述“此接口上传输的唯一事件OAMPDU数。可以发送两次事件通知，以增加成功接收的概率，
given the possibility that a frame may be lost in transit. Duplicate Event Notification transmissions are counted by dot3OamDuplicateEventNotificationTx.
考虑到帧可能在传输过程中丢失。重复事件通知传输由dot3OamDuplicateEventNotificationTx统计。
A unique Event Notification OAMPDU is indicated as an Event Notification OAMPDU with a Sequence Number field that is distinct from the previously transmitted Event Notification OAMPDU Sequence Number.
唯一事件通知OAMPDU被指示为具有序列号字段的事件通知OAMPDU，该序列号字段不同于先前传输的事件通知OAMPDU序列号。
Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime.
"
REFERENCE "[802.3ah], 30.3.6.1.22."
::= { dot3OamStatsEntry 3 }
Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime.
"
REFERENCE "[802.3ah], 30.3.6.1.22."
::= { dot3OamStatsEntry 3 }
dot3OamUniqueEventNotificationRx OBJECT-TYPE SYNTAX Counter32 UNITS "frames" MAX-ACCESS read-only STATUS current DESCRIPTION "A count of the number of unique Event OAMPDUs received on this interface. Event Notification OAMPDUs may be sent in duplicate to increase the probability of successfully being received, given the possibility that a frame may be lost in transit. Duplicate Event Notification receptions are counted by dot3OamDuplicateEventNotificationRx.
dot3OamUniqueEventNotificationRx对象类型语法计数器32个单元“帧”最大访问只读状态当前说明“此接口上接收的唯一事件OAMPDU数的计数。考虑到帧在传输过程中可能丢失的可能性，事件通知oampdu可以一式两份发送，以增加成功接收的概率。重复事件通知接收由dot3OamDuplicateEventNotificationRx统计。
A unique Event Notification OAMPDU is indicated as an Event Notification OAMPDU with a Sequence Number field that is distinct from the previously received Event Notification OAMPDU Sequence Number.
唯一事件通知OAMPDU表示为事件通知OAMPDU，其序列号字段不同于先前接收到的事件通知OAMPDU序列号。
Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime.
"
REFERENCE "[802.3ah], 30.3.6.1.24."
::= { dot3OamStatsEntry 4 }
Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime.
"
REFERENCE "[802.3ah], 30.3.6.1.24."
::= { dot3OamStatsEntry 4 }
dot3OamDuplicateEventNotificationTx OBJECT-TYPE SYNTAX Counter32 UNITS "frames" MAX-ACCESS read-only STATUS current DESCRIPTION "A count of the number of duplicate Event OAMPDUs transmitted
DotOatx-EventOatx-count当前发送的事件状态“DotOatx-EventOatus-count”的重复事件状态
on this interface. Event Notification OAMPDUs may be sent in duplicate to increase the probability of successfully being received, given the possibility that a frame may be lost in transit.
在这个界面上。考虑到帧在传输过程中可能丢失的可能性，事件通知oampdu可以一式两份发送，以增加成功接收的概率。
A duplicate Event Notification OAMPDU is indicated as an Event Notification OAMPDU with a Sequence Number field that is identical to the previously transmitted Event Notification OAMPDU Sequence Number.
重复事件通知OAMPDU被指示为事件通知OAMPDU，其序列号字段与先前发送的事件通知OAMPDU序列号相同。
Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime.
"
REFERENCE "[802.3ah], 30.3.6.1.23."
::= { dot3OamStatsEntry 5 }
Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime.
"
REFERENCE "[802.3ah], 30.3.6.1.23."
::= { dot3OamStatsEntry 5 }
dot3OamDuplicateEventNotificationRx OBJECT-TYPE SYNTAX Counter32 UNITS "frames" MAX-ACCESS read-only STATUS current DESCRIPTION "A count of the number of duplicate Event OAMPDUs received on this interface. Event Notification OAMPDUs may be sent in duplicate to increase the probability of successfully being received, given the possibility that a frame may be lost in transit.
DOT3OAMDupplicateEventNotificationRX对象类型语法计数器32个单元“帧”最大访问只读状态当前说明“此接口上接收的重复事件OAMPDU数的计数。考虑到帧在传输过程中可能丢失的可能性，事件通知oampdu可以一式两份发送，以增加成功接收的概率。
A duplicate Event Notification OAMPDU is indicated as an Event Notification OAMPDU with a Sequence Number field that is identical to the previously received Event Notification OAMPDU Sequence Number.
重复事件通知OAMPDU被指示为事件通知OAMPDU，其序列号字段与先前接收到的事件通知OAMPDU序列号相同。
Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime.
"
REFERENCE "[802.3ah], 30.3.6.1.25."
::= { dot3OamStatsEntry 6 }
Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime.
"
REFERENCE "[802.3ah], 30.3.6.1.25."
::= { dot3OamStatsEntry 6 }
dot3OamLoopbackControlTx OBJECT-TYPE SYNTAX Counter32 UNITS "frames" MAX-ACCESS read-only STATUS current DESCRIPTION "A count of the number of Loopback Control OAMPDUs transmitted
dot3OamLoopbackControlTx对象类型语法计数器32个单元“帧”MAX-ACCESS只读状态当前描述“发送的环回控制OAMPDU数的计数
on this interface.
在这个界面上。
Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime.
"
REFERENCE "[802.3ah], 30.3.6.1.26."
::= { dot3OamStatsEntry 7 }
Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime.
"
REFERENCE "[802.3ah], 30.3.6.1.26."
::= { dot3OamStatsEntry 7 }
dot3OamLoopbackControlRx OBJECT-TYPE SYNTAX Counter32 UNITS "frames" MAX-ACCESS read-only STATUS current DESCRIPTION "A count of the number of Loopback Control OAMPDUs received on this interface.
DOT3OAMLOOPBACKCONTROLX对象类型语法计数器32个单元“帧”MAX-ACCESS只读状态当前描述“此接口上接收的环回控制OAMPDU数的计数。
Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime.
"
REFERENCE "[802.3ah], 30.3.6.1.27."
::= { dot3OamStatsEntry 8 }
Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime.
"
REFERENCE "[802.3ah], 30.3.6.1.27."
::= { dot3OamStatsEntry 8 }
dot3OamVariableRequestTx OBJECT-TYPE SYNTAX Counter32 UNITS "frames" MAX-ACCESS read-only STATUS current DESCRIPTION "A count of the number of Variable Request OAMPDUs transmitted on this interface.
dot3OamVariableRequestTx对象类型语法计数器32个单元“帧”最大访问只读状态当前描述“在此接口上传输的可变请求OAMPDU数的计数。
Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime.
"
REFERENCE "[802.3ah], 30.3.6.1.28."
::= { dot3OamStatsEntry 9 }
Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime.
"
REFERENCE "[802.3ah], 30.3.6.1.28."
::= { dot3OamStatsEntry 9 }
dot3OamVariableRequestRx OBJECT-TYPE SYNTAX Counter32 UNITS "frames" MAX-ACCESS read-only STATUS current DESCRIPTION "A count of the number of Variable Request OAMPDUs received on
dot3OamVariableRequestRx对象类型语法计数器32个单元“帧”MAX-ACCESS只读状态当前描述“上接收的可变请求OAMPDU数的计数”
this interface.
这个界面。
Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime.
"
REFERENCE "[802.3ah], 30.3.6.1.29."
::= { dot3OamStatsEntry 10 }
Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime.
"
REFERENCE "[802.3ah], 30.3.6.1.29."
::= { dot3OamStatsEntry 10 }
dot3OamVariableResponseTx OBJECT-TYPE SYNTAX Counter32 UNITS "frames" MAX-ACCESS read-only STATUS current DESCRIPTION "A count of the number of Variable Response OAMPDUs transmitted on this interface.
dot3OamVariableResponseTx对象类型语法计数器32个单元“帧”最大访问只读状态当前描述“在此接口上传输的可变响应OAMPDU数的计数。
Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime.
"
REFERENCE "[802.3ah], 30.3.6.1.30."
::= { dot3OamStatsEntry 11 }
Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime.
"
REFERENCE "[802.3ah], 30.3.6.1.30."
::= { dot3OamStatsEntry 11 }
dot3OamVariableResponseRx OBJECT-TYPE SYNTAX Counter32 UNITS "frames" MAX-ACCESS read-only STATUS current DESCRIPTION "A count of the number of Variable Response OAMPDUs received on this interface.
dot3OamVariableResponseRx对象类型语法计数器32个单元“帧”最大访问只读状态当前描述“此接口上接收的可变响应OAMPDU数的计数。
Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime.
"
REFERENCE "[802.3ah], 30.3.6.1.31."
::= { dot3OamStatsEntry 12 }
Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime.
"
REFERENCE "[802.3ah], 30.3.6.1.31."
::= { dot3OamStatsEntry 12 }
dot3OamOrgSpecificTx OBJECT-TYPE SYNTAX Counter32 UNITS "frames" MAX-ACCESS read-only STATUS current DESCRIPTION "A count of the number of Organization Specific OAMPDUs
DOT3OAMORGSPECICTX对象类型语法计数器32个单元“帧”MAX-ACCESS只读状态当前描述“特定于组织的OAMPDU数的计数
transmitted on this interface.
在这个接口上传输。
Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime.
"
REFERENCE "[802.3ah], 30.3.6.1.32."
::= { dot3OamStatsEntry 13 }
Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime.
"
REFERENCE "[802.3ah], 30.3.6.1.32."
::= { dot3OamStatsEntry 13 }
dot3OamOrgSpecificRx OBJECT-TYPE SYNTAX Counter32 UNITS "frames" MAX-ACCESS read-only STATUS current DESCRIPTION "A count of the number of Organization Specific OAMPDUs received on this interface.
DOT3OAMORGSPECICRX对象类型语法计数器32个单元“帧”MAX-ACCESS只读状态当前描述“此接口上接收的特定于组织的OAMPDU数的计数。
Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime.
"
REFERENCE "[802.3ah], 30.3.6.1.33."
::= { dot3OamStatsEntry 14 }
Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime.
"
REFERENCE "[802.3ah], 30.3.6.1.33."
::= { dot3OamStatsEntry 14 }
dot3OamUnsupportedCodesTx OBJECT-TYPE SYNTAX Counter32 UNITS "frames" MAX-ACCESS read-only STATUS current DESCRIPTION "A count of the number of OAMPDUs transmitted on this interface with an unsupported op-code.
dot3OamUnsupportedCodesTx对象类型语法计数器32个单元“帧”MAX-ACCESS只读状态当前描述“使用不支持的操作码在此接口上传输的OAMPDU数的计数。
Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime.
"
REFERENCE "[802.3ah], 30.3.6.1.18."
::= { dot3OamStatsEntry 15 }
Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime.
"
REFERENCE "[802.3ah], 30.3.6.1.18."
::= { dot3OamStatsEntry 15 }
dot3OamUnsupportedCodesRx OBJECT-TYPE SYNTAX Counter32 UNITS "frames" MAX-ACCESS read-only STATUS current DESCRIPTION "A count of the number of OAMPDUs received on this interface
dot3OamUnsupportedCodesRx对象类型语法计数器32个单元“帧”最大访问只读状态当前描述“此接口上接收的OAMPDU数的计数
with an unsupported op-code.
使用不支持的操作代码。
Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime.
"
REFERENCE "[802.3ah], 30.3.6.1.19."
::= { dot3OamStatsEntry 16 }
Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime.
"
REFERENCE "[802.3ah], 30.3.6.1.19."
::= { dot3OamStatsEntry 16 }
dot3OamFramesLostDueToOam OBJECT-TYPE SYNTAX Counter32 UNITS "frames" MAX-ACCESS read-only STATUS current DESCRIPTION "A count of the number of frames that were dropped by the OA multiplexer. Since the OAM multiplexer has multiple inputs and a single output, there may be cases where frames are dropped due to transmit resource contention. This counter is incremented whenever a frame is dropped by the OAM layer. Note that any Ethernet frame, not just OAMPDUs, may be dropped by the OAM layer. This can occur when an OAMPDU takes precedence over a 'normal' frame resulting in the 'normal' frame being dropped.
dot3OamFramesLostDueToOam对象类型语法计数器32个单元“帧”最大访问只读状态当前说明“OA多路复用器丢弃的帧数计数。由于OAM多路复用器具有多个输入和单个输出，因此可能存在由于传输资源争用而丢弃帧的情况。每当OAM层丢弃一个帧时，该计数器就会递增。请注意，任何以太网帧（不仅仅是OAMPDU）都可能被OAM层丢弃。当OAMPDU优先于“正常”帧导致“正常”帧被丢弃时，可能会发生这种情况。
When this counter is incremented, no other counters in this MIB are incremented.
当此计数器递增时，此MIB中的其他计数器不会递增。
Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime.
"
REFERENCE "[802.3ah], 30.3.6.1.46."
::= { dot3OamStatsEntry 17 }
Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime.
"
REFERENCE "[802.3ah], 30.3.6.1.46."
::= { dot3OamStatsEntry 17 }
-- ***************************************************************
--
-- Ethernet OAM Event Configuration group
--
-- ***************************************************************
--
-- Ethernet OAM Event Configuration group
--
dot3OamEventConfigTable OBJECT-TYPE SYNTAX SEQUENCE OF Dot3OamEventConfigEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Ethernet OAM includes the ability to generate and receive Event Notification OAMPDUs to indicate various link problems. This table contains the mechanisms to enable Event
DOT3OAMEVENTCONFIG对象类型Dot3OamEventConfigEntry MAX-ACCESS的语法序列不可访问状态当前描述“以太网OAM包括生成和接收事件通知OAMPDU的能力，以指示各种链路问题。此表包含启用事件通知的机制
Notifications and configure the thresholds to generate the standard Ethernet OAM events. There is one entry in the table for every entry in dot3OamTable that supports OAM events (where dot3OamFunctionsSupported includes the eventSupport bit set). The values in the table are maintained across changes to dot3OamOperStatus.
通知并配置阈值以生成标准以太网OAM事件。对于支持OAM事件的dot3OamTable中的每个条目，表中都有一个条目（其中dot3OamFunctionsSupported包括eventSupport位集）。表中的值在对dot3OamOperStatus的更改中保持不变。
The standard threshold crossing events are:
- Errored Symbol Period Event. Generated when the number of
symbol errors exceeds a threshold within a given window
defined by a number of symbols (for example, 1,000 symbols
out of 1,000,000 had errors).
- Errored Frame Period Event. Generated when the number of
frame errors exceeds a threshold within a given window
defined by a number of frames (for example, 10 frames out
of 1000 had errors).
- Errored Frame Event. Generated when the number of frame
errors exceeds a threshold within a given window defined
by a period of time (for example, 10 frames in 1 second
had errors).
- Errored Frame Seconds Summary Event. Generated when the
number of errored frame seconds exceeds a threshold within
a given time period (for example, 10 errored frame seconds
within the last 100 seconds). An errored frame second is
defined as a 1 second interval which had >0 frame errors.
There are other events (dying gasp, critical events) that are
not threshold crossing events but which can be
enabled/disabled via this table.
"
::= { dot3OamObjects 5 }
The standard threshold crossing events are:
- Errored Symbol Period Event. Generated when the number of
symbol errors exceeds a threshold within a given window
defined by a number of symbols (for example, 1,000 symbols
out of 1,000,000 had errors).
- Errored Frame Period Event. Generated when the number of
frame errors exceeds a threshold within a given window
defined by a number of frames (for example, 10 frames out
of 1000 had errors).
- Errored Frame Event. Generated when the number of frame
errors exceeds a threshold within a given window defined
by a period of time (for example, 10 frames in 1 second
had errors).
- Errored Frame Seconds Summary Event. Generated when the
number of errored frame seconds exceeds a threshold within
a given time period (for example, 10 errored frame seconds
within the last 100 seconds). An errored frame second is
defined as a 1 second interval which had >0 frame errors.
There are other events (dying gasp, critical events) that are
not threshold crossing events but which can be
enabled/disabled via this table.
"
::= { dot3OamObjects 5 }
dot3OamEventConfigEntry OBJECT-TYPE SYNTAX Dot3OamEventConfigEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Entries are automatically created and deleted from this table, and exist whenever the OAM entity supports Ethernet OA events (as indicated by the eventSupport bit in dot3OamFunctionsSuppported). Values in the table are maintained across changes to the value of dot3OamOperStatus.
dot3OamEventConfigEntry对象类型语法dot3OamEventConfigEntry MAX-ACCESS not ACCESS STATUS current DESCRIPTION“条目将自动创建并从此表中删除，并在OAM实体支持以太网OA事件时存在（如DOT3OAMFunctionsSupported中的eventSupport位所示）。表中的值在dot3OamOperStatus值的更改期间保持不变。
Event configuration controls when the local management entity
sends Event Notification OAMPDUs to its OAM peer, and when
certain event flags are set or cleared in OAMPDUs.
"
INDEX { ifIndex }
::= { dot3OamEventConfigTable 1 }
Event configuration controls when the local management entity
sends Event Notification OAMPDUs to its OAM peer, and when
certain event flags are set or cleared in OAMPDUs.
"
INDEX { ifIndex }
::= { dot3OamEventConfigTable 1 }
Dot3OamEventConfigEntry ::=
SEQUENCE {
dot3OamErrSymPeriodWindowHi Unsigned32,
dot3OamErrSymPeriodWindowLo Unsigned32,
dot3OamErrSymPeriodThresholdHi Unsigned32,
dot3OamErrSymPeriodThresholdLo Unsigned32,
dot3OamErrSymPeriodEvNotifEnable TruthValue,
dot3OamErrFramePeriodWindow Unsigned32,
dot3OamErrFramePeriodThreshold Unsigned32,
dot3OamErrFramePeriodEvNotifEnable TruthValue,
dot3OamErrFrameWindow Unsigned32,
dot3OamErrFrameThreshold Unsigned32,
dot3OamErrFrameEvNotifEnable TruthValue,
dot3OamErrFrameSecsSummaryWindow Integer32,
dot3OamErrFrameSecsSummaryThreshold Integer32,
dot3OamErrFrameSecsEvNotifEnable TruthValue,
dot3OamDyingGaspEnable TruthValue,
dot3OamCriticalEventEnable TruthValue
}
Dot3OamEventConfigEntry ::=
SEQUENCE {
dot3OamErrSymPeriodWindowHi Unsigned32,
dot3OamErrSymPeriodWindowLo Unsigned32,
dot3OamErrSymPeriodThresholdHi Unsigned32,
dot3OamErrSymPeriodThresholdLo Unsigned32,
dot3OamErrSymPeriodEvNotifEnable TruthValue,
dot3OamErrFramePeriodWindow Unsigned32,
dot3OamErrFramePeriodThreshold Unsigned32,
dot3OamErrFramePeriodEvNotifEnable TruthValue,
dot3OamErrFrameWindow Unsigned32,
dot3OamErrFrameThreshold Unsigned32,
dot3OamErrFrameEvNotifEnable TruthValue,
dot3OamErrFrameSecsSummaryWindow Integer32,
dot3OamErrFrameSecsSummaryThreshold Integer32,
dot3OamErrFrameSecsEvNotifEnable TruthValue,
dot3OamDyingGaspEnable TruthValue,
dot3OamCriticalEventEnable TruthValue
}
dot3OamErrSymPeriodWindowHi OBJECT-TYPE
SYNTAX Unsigned32
UNITS "2^32 symbols"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The two objects dot3OamErrSymPeriodWindowHi and
dot3OamErrSymPeriodLo together form an unsigned 64-bit
integer representing the number of symbols over which this
threshold event is defined. This is defined as
dot3OamErrSymPeriodWindow = ((2^32)*dot3OamErrSymPeriodWindowHi)
+ dot3OamErrSymPeriodWindowLo
dot3OamErrSymPeriodWindowHi OBJECT-TYPE
SYNTAX Unsigned32
UNITS "2^32 symbols"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The two objects dot3OamErrSymPeriodWindowHi and
dot3OamErrSymPeriodLo together form an unsigned 64-bit
integer representing the number of symbols over which this
threshold event is defined. This is defined as
dot3OamErrSymPeriodWindow = ((2^32)*dot3OamErrSymPeriodWindowHi)
+ dot3OamErrSymPeriodWindowLo
If dot3OamErrSymPeriodThreshold symbol errors occur within a window of dot3OamErrSymPeriodWindow symbols, an Event Notification OAMPDU should be generated with an Errored Symbol Period Event TLV indicating that the threshold has been crossed in this window.
如果Dot3OamerSymPeriodThreshold符号错误发生在Dot3OamerSymPeriodWindow符号窗口内，则应生成事件通知OAMPDU，其中错误符号周期事件TLV指示此窗口中已越过阈值。
The default value for dot3OamErrSymPeriodWindow is the number
of symbols in one second for the underlying physical layer.
"
REFERENCE "[802.3ah], 30.3.6.1.34"
::= { dot3OamEventConfigEntry 1 }
The default value for dot3OamErrSymPeriodWindow is the number
of symbols in one second for the underlying physical layer.
"
REFERENCE "[802.3ah], 30.3.6.1.34"
::= { dot3OamEventConfigEntry 1 }
dot3OamErrSymPeriodWindowLo OBJECT-TYPE SYNTAX Unsigned32 UNITS "symbols"
dot3OamErrSymPeriodWindowLo对象类型语法无符号32个单位“符号”
MAX-ACCESS read-write STATUS current DESCRIPTION "The two objects dot3OamErrSymPeriodWindowHi and dot3OamErrSymPeriodWindowLo together form an unsigned 64-bit integer representing the number of symbols over which this threshold event is defined. This is defined as
MAX-ACCESS读写状态当前描述“两个对象dot3OamErrSymPeriodWindowHi和dot3OamErrSymPeriodWindowLo共同构成一个无符号64位整数，表示定义此阈值事件的符号数。定义为
dot3OamErrSymPeriodWindow = ((2^32)*dot3OamErrSymPeriodWindowHi)
+ dot3OamErrSymPeriodWindowLo
dot3OamErrSymPeriodWindow = ((2^32)*dot3OamErrSymPeriodWindowHi)
+ dot3OamErrSymPeriodWindowLo
If dot3OamErrSymPeriodThreshold symbol errors occur within a window of dot3OamErrSymPeriodWindow symbols, an Event Notification OAMPDU should be generated with an Errored Symbol Period Event TLV indicating that the threshold has been crossed in this window.
如果Dot3OamerSymPeriodThreshold符号错误发生在Dot3OamerSymPeriodWindow符号窗口内，则应生成事件通知OAMPDU，其中错误符号周期事件TLV指示此窗口中已越过阈值。
The default value for dot3OamErrSymPeriodWindow is the number
of symbols in one second for the underlying physical layer.
"
REFERENCE "[802.3ah], 30.3.6.1.34"
::= { dot3OamEventConfigEntry 2 }
The default value for dot3OamErrSymPeriodWindow is the number
of symbols in one second for the underlying physical layer.
"
REFERENCE "[802.3ah], 30.3.6.1.34"
::= { dot3OamEventConfigEntry 2 }
dot3OamErrSymPeriodThresholdHi OBJECT-TYPE SYNTAX Unsigned32 UNITS "2^32 symbols" MAX-ACCESS read-write STATUS current DESCRIPTION "The two objects dot3OamErrSymPeriodThresholdHi and dot3OamErrSymPeriodThresholdLo together form an unsigned 64-bit integer representing the number of symbol errors that must occur within a given window to cause this event.
DOT3OAMERRSYMPORIDTHERNOLDHI对象类型语法无符号32个单位“2^32个符号”最大访问读写状态当前说明“两个对象dot3oamerrsymperiodsthresholdhi和dot3oamerrsymperiodsthresholdlo一起构成一个无符号64位整数，表示在给定窗口内必须发生的符号错误数，以导致此事件。
This is defined as
这被定义为
dot3OamErrSymPeriodThreshold =
((2^32) * dot3OamErrSymPeriodThresholdHi)
+ dot3OamErrSymPeriodThresholdLo
dot3OamErrSymPeriodThreshold =
((2^32) * dot3OamErrSymPeriodThresholdHi)
+ dot3OamErrSymPeriodThresholdLo
If dot3OamErrSymPeriodThreshold symbol errors occur within a window of dot3OamErrSymPeriodWindow symbols, an Event Notification OAMPDU should be generated with an Errored Symbol Period Event TLV indicating that the threshold has been crossed in this window.
如果Dot3OamerSymPeriodThreshold符号错误发生在Dot3OamerSymPeriodWindow符号窗口内，则应生成事件通知OAMPDU，其中错误符号周期事件TLV指示此窗口中已越过阈值。
The default value for dot3OamErrSymPeriodThreshold is one symbol errors. If the threshold value is zero, then an Event
Dot3OamerSymPeriodThreshold的默认值是一个符号错误。如果阈值为零，则事件
Notification OAMPDU is sent periodically (at the end of every
window). This can be used as an asynchronous notification to
the peer OAM entity of the statistics related to this
threshold crossing alarm.
"
REFERENCE "[802.3ah], 30.3.6.1.34"
::= { dot3OamEventConfigEntry 3 }
Notification OAMPDU is sent periodically (at the end of every
window). This can be used as an asynchronous notification to
the peer OAM entity of the statistics related to this
threshold crossing alarm.
"
REFERENCE "[802.3ah], 30.3.6.1.34"
::= { dot3OamEventConfigEntry 3 }
dot3OamErrSymPeriodThresholdLo OBJECT-TYPE SYNTAX Unsigned32 UNITS "symbols" MAX-ACCESS read-write STATUS current DESCRIPTION "The two objects dot3OamErrSymPeriodThresholdHi and dot3OamErrSymPeriodThresholdLo together form an unsigned 64-bit integer representing the number of symbol errors that must occur within a given window to cause this event.
dot3oamerrsymperiodsthresholdlo对象类型语法Unsigned32单元“symbols”MAX-ACCESS读写状态当前描述“两个对象dot3oamerrsymperiodsthresholdhi和dot3oamerrsymperiodsthresholdlo一起构成一个无符号64位整数，表示在给定窗口内必须发生的符号错误数，以导致此事件。
This is defined as
这被定义为
dot3OamErrSymPeriodThreshold =
((2^32) * dot3OamErrSymPeriodThresholdHi)
+ dot3OamErrSymPeriodThresholdLo
dot3OamErrSymPeriodThreshold =
((2^32) * dot3OamErrSymPeriodThresholdHi)
+ dot3OamErrSymPeriodThresholdLo
If dot3OamErrSymPeriodThreshold symbol errors occur within a window of dot3OamErrSymPeriodWindow symbols, an Event Notification OAMPDU should be generated with an Errored Symbol Period Event TLV indicating that the threshold has been crossed in this window.
如果Dot3OamerSymPeriodThreshold符号错误发生在Dot3OamerSymPeriodWindow符号窗口内，则应生成事件通知OAMPDU，其中错误符号周期事件TLV指示此窗口中已越过阈值。
The default value for dot3OamErrSymPeriodThreshold is one
symbol error. If the threshold value is zero, then an Event
Notification OAMPDU is sent periodically (at the end of every
window). This can be used as an asynchronous notification to
the peer OAM entity of the statistics related to this
threshold crossing alarm.
"
REFERENCE "[802.3ah], 30.3.6.1.34"
::= { dot3OamEventConfigEntry 4 }
The default value for dot3OamErrSymPeriodThreshold is one
symbol error. If the threshold value is zero, then an Event
Notification OAMPDU is sent periodically (at the end of every
window). This can be used as an asynchronous notification to
the peer OAM entity of the statistics related to this
threshold crossing alarm.
"
REFERENCE "[802.3ah], 30.3.6.1.34"
::= { dot3OamEventConfigEntry 4 }
dot3OamErrSymPeriodEvNotifEnable OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "If true, the OAM entity should send an Event Notification OAMPDU when an Errored Symbol Period Event occurs.
dot3OamErrSymPeriodEvNotifEnable对象类型语法TruthValue MAX-ACCESS读写状态当前描述“如果为true，则当发生错误符号周期事件时，OAM实体应发送事件通知OAMPDU。
By default, this object should have the value true for
Ethernet-like interfaces that support OAM. If the OAM layer
does not support Event Notifications (as indicated via the
dot3OamFunctionsSupported attribute), this value is ignored.
"
::= { dot3OamEventConfigEntry 5 }
By default, this object should have the value true for
Ethernet-like interfaces that support OAM. If the OAM layer
does not support Event Notifications (as indicated via the
dot3OamFunctionsSupported attribute), this value is ignored.
"
::= { dot3OamEventConfigEntry 5 }
dot3OamErrFramePeriodWindow OBJECT-TYPE SYNTAX Unsigned32 UNITS "frames" MAX-ACCESS read-write STATUS current DESCRIPTION "The number of frames over which the threshold is defined. The default value of the window is the number of minimum size Ethernet frames that can be received over the physical layer in one second.
dot3OamErrFramePeriodWindow对象类型语法Unsigned32 UNITS“frames”MAX-ACCESS read-write STATUS current DESCRIPTION“定义阈值的帧数。该窗口的默认值是每秒可通过物理层接收的最小大小以太网帧数。
If dot3OamErrFramePeriodThreshold frame errors occur within a
window of dot3OamErrFramePeriodWindow frames, an Event
Notification OAMPDU should be generated with an Errored Frame
Period Event TLV indicating that the threshold has been
crossed in this window.
"
REFERENCE "[802.3ah], 30.3.6.1.38"
::= { dot3OamEventConfigEntry 6 }
If dot3OamErrFramePeriodThreshold frame errors occur within a
window of dot3OamErrFramePeriodWindow frames, an Event
Notification OAMPDU should be generated with an Errored Frame
Period Event TLV indicating that the threshold has been
crossed in this window.
"
REFERENCE "[802.3ah], 30.3.6.1.38"
::= { dot3OamEventConfigEntry 6 }
dot3OamErrFramePeriodThreshold OBJECT-TYPE SYNTAX Unsigned32 UNITS "frames" MAX-ACCESS read-write STATUS current DESCRIPTION "The number of frame errors that must occur for this event to be triggered. The default value is one frame error. If the threshold value is zero, then an Event Notification OAMPDU is sent periodically (at the end of every window). This can be used as an asynchronous notification to the peer OAM entity of the statistics related to this threshold crossing alarm.
dot3OamErrFramePeriodThreshold对象类型语法Unsigned32个单位“frames”MAX-ACCESS读写状态当前描述“要触发此事件必须发生的帧错误数。默认值为一个帧错误。如果阈值为零，则会定期发送事件通知OAMPDU（在每个窗口的末尾）。这可以用作向对等OAM实体发送与此阈值交叉警报相关的统计信息的异步通知。
If dot3OamErrFramePeriodThreshold frame errors occur within a window of dot3OamErrFramePeriodWindow frames, an Event Notification OAMPDU should be generated with an Errored Frame Period Event TLV indicating that the threshold has been crossed in this window. " REFERENCE "[802.3ah], 30.3.6.1.38"
如果Dot3OamerFramePeriodThreshold帧错误发生在Dot3OamerFramePeriodWindow帧的窗口内，则应生成事件通知OAMPDU，其中错误帧周期事件TLV指示此窗口中已越过阈值。“参考”[802.3ah]，30.3.6.1.38”
::= { dot3OamEventConfigEntry 7 }
::= { dot3OamEventConfigEntry 7 }
dot3OamErrFramePeriodEvNotifEnable OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "If true, the OAM entity should send an Event Notification OAMPDU when an Errored Frame Period Event occurs.
dot3OamErrFramePeriodEvNotifEnable对象类型语法TruthValue MAX-ACCESS读写状态当前描述“如果为true，则OAM实体应在发生错误帧周期事件时发送事件通知OAMPDU。
By default, this object should have the value true for
Ethernet-like interfaces that support OAM. If the OAM layer
does not support Event Notifications (as indicated via the
dot3OamFunctionsSupported attribute), this value is ignored.
"
::= { dot3OamEventConfigEntry 8 }
By default, this object should have the value true for
Ethernet-like interfaces that support OAM. If the OAM layer
does not support Event Notifications (as indicated via the
dot3OamFunctionsSupported attribute), this value is ignored.
"
::= { dot3OamEventConfigEntry 8 }
dot3OamErrFrameWindow OBJECT-TYPE SYNTAX Unsigned32 UNITS "tenths of a second" MAX-ACCESS read-write STATUS current DESCRIPTION "The amount of time (in 100ms increments) over which the threshold is defined. The default value is 10 (1 second).
dot3OamErrFrameWindow对象类型语法无符号32单位“十分之一秒”最大访问读写状态当前描述定义阈值的时间量（以100ms为增量）。默认值为10（1秒）。
If dot3OamErrFrameThreshold frame errors occur within a window
of dot3OamErrFrameWindow seconds (measured in tenths of
seconds), an Event Notification OAMPDU should be generated
with an Errored Frame Event TLV indicating that the threshold
has been crossed in this window.
"
REFERENCE "[802.3ah], 30.3.6.1.36"
DEFVAL { 10 }
::= { dot3OamEventConfigEntry 9 }
If dot3OamErrFrameThreshold frame errors occur within a window
of dot3OamErrFrameWindow seconds (measured in tenths of
seconds), an Event Notification OAMPDU should be generated
with an Errored Frame Event TLV indicating that the threshold
has been crossed in this window.
"
REFERENCE "[802.3ah], 30.3.6.1.36"
DEFVAL { 10 }
::= { dot3OamEventConfigEntry 9 }
dot3OamErrFrameThreshold OBJECT-TYPE SYNTAX Unsigned32 UNITS "frames" MAX-ACCESS read-write STATUS current DESCRIPTION "The number of frame errors that must occur for this event to be triggered. The default value is one frame error. If the threshold value is zero, then an Event Notification OAMPDU is sent periodically (at the end of every window). This can be used as an asynchronous notification to the peer OAM entity of the statistics related to this threshold crossing alarm.
dot3OamErrFrameThreshold对象类型语法Unsigned32 UNITS“frames”MAX-ACCESS read-write STATUS current DESCRIPTION“要触发此事件必须发生的帧错误数。默认值为一个帧错误。如果阈值为零，则定期发送事件通知OAMPDU（在每个窗口结束时）。这可以用作向对等OAM实体发送与此阈值交叉警报相关的统计信息的异步通知。
If dot3OamErrFrameThreshold frame errors occur within a window
of dot3OamErrFrameWindow (in tenths of seconds), an Event
Notification OAMPDU should be generated with an Errored Frame
Event TLV indicating the threshold has been crossed in this
window.
"
REFERENCE "[802.3ah], 30.3.6.1.36"
DEFVAL { 1 }
::= { dot3OamEventConfigEntry 10 }
If dot3OamErrFrameThreshold frame errors occur within a window
of dot3OamErrFrameWindow (in tenths of seconds), an Event
Notification OAMPDU should be generated with an Errored Frame
Event TLV indicating the threshold has been crossed in this
window.
"
REFERENCE "[802.3ah], 30.3.6.1.36"
DEFVAL { 1 }
::= { dot3OamEventConfigEntry 10 }
dot3OamErrFrameEvNotifEnable OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "If true, the OAM entity should send an Event Notification OAMPDU when an Errored Frame Event occurs.
dot3OamErrFrameEvNotifEnable对象类型语法TruthValue MAX-ACCESS读写状态当前描述“如果为true，则当发生错误帧事件时，OAM实体应发送事件通知OAMPDU。
By default, this object should have the value true for
Ethernet-like interfaces that support OAM. If the OAM layer
does not support Event Notifications (as indicated via the
dot3OamFunctionsSupported attribute), this value is ignored.
"
DEFVAL { true }
::= { dot3OamEventConfigEntry 11 }
By default, this object should have the value true for
Ethernet-like interfaces that support OAM. If the OAM layer
does not support Event Notifications (as indicated via the
dot3OamFunctionsSupported attribute), this value is ignored.
"
DEFVAL { true }
::= { dot3OamEventConfigEntry 11 }
dot3OamErrFrameSecsSummaryWindow OBJECT-TYPE SYNTAX Integer32 (100..9000) UNITS "tenths of a second" MAX-ACCESS read-write STATUS current DESCRIPTION "The amount of time (in 100 ms intervals) over which the threshold is defined. The default value is 100 (10 seconds).
DOT3OAMERRFRAMESECSSUMARYWindow对象类型语法整数32（100..9000）单位“十分之一秒”最大访问读写状态当前描述定义阈值的时间量（以100毫秒为间隔）。默认值为100（10秒）。
If dot3OamErrFrameSecsSummaryThreshold frame errors occur
within a window of dot3OamErrFrameSecsSummaryWindow (in tenths
of seconds), an Event Notification OAMPDU should be generated
with an Errored Frame Seconds Summary Event TLV indicating
that the threshold has been crossed in this window.
"
REFERENCE "[802.3ah], 30.3.6.1.40"
DEFVAL { 100 }
::= { dot3OamEventConfigEntry 12 }
If dot3OamErrFrameSecsSummaryThreshold frame errors occur
within a window of dot3OamErrFrameSecsSummaryWindow (in tenths
of seconds), an Event Notification OAMPDU should be generated
with an Errored Frame Seconds Summary Event TLV indicating
that the threshold has been crossed in this window.
"
REFERENCE "[802.3ah], 30.3.6.1.40"
DEFVAL { 100 }
::= { dot3OamEventConfigEntry 12 }
dot3OamErrFrameSecsSummaryThreshold OBJECT-TYPE SYNTAX Integer32 (1..900)
DOT3OAMERRFRAMESCSUMmarySThreshold对象类型语法整数32（1..900）
UNITS "errored frame seconds" MAX-ACCESS read-write STATUS current DESCRIPTION "The number of errored frame seconds that must occur for this event to be triggered. The default value is one errored frame second. If the threshold value is zero, then an Event Notification OAMPDU is sent periodically (at the end of every window). This can be used as an asynchronous notification to the peer OAM entity of the statistics related to this threshold crossing alarm.
UNITS“errored frame seconds”MAX-ACCESS read-write STATUS current DESCRIPTION“触发此事件必须发生的错误帧数秒数。默认值为一个错误帧数秒。如果阈值为零，则定期发送事件通知OAMPDU（在每个窗口结束时）。这可以用作向对等OAM实体发送与此阈值交叉警报相关的统计信息的异步通知。
If dot3OamErrFrameSecsSummaryThreshold frame errors occur
within a window of dot3OamErrFrameSecsSummaryWindow (in tenths
of seconds), an Event Notification OAMPDU should be generated
with an Errored Frame Seconds Summary Event TLV indicating
that the threshold has been crossed in this window.
"
REFERENCE "[802.3ah], 30.3.6.1.40"
DEFVAL { 1 }
::= { dot3OamEventConfigEntry 13 }
If dot3OamErrFrameSecsSummaryThreshold frame errors occur
within a window of dot3OamErrFrameSecsSummaryWindow (in tenths
of seconds), an Event Notification OAMPDU should be generated
with an Errored Frame Seconds Summary Event TLV indicating
that the threshold has been crossed in this window.
"
REFERENCE "[802.3ah], 30.3.6.1.40"
DEFVAL { 1 }
::= { dot3OamEventConfigEntry 13 }
dot3OamErrFrameSecsEvNotifEnable OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "If true, the local OAM entity should send an Event Notification OAMPDU when an Errored Frame Seconds Event occurs.
dot3OamErrFrameSecsEvNotifEnable对象类型语法TruthValue MAX-ACCESS读写状态当前描述“如果为true，则本地OAM实体应在发生错误帧秒事件时发送事件通知OAMPDU。
By default, this object should have the value true for
Ethernet-like interfaces that support OAM. If the OAM layer
does not support Event Notifications (as indicated via the
dot3OamFunctionsSupported attribute), this value is ignored.
"
DEFVAL { true }
::= { dot3OamEventConfigEntry 14 }
By default, this object should have the value true for
Ethernet-like interfaces that support OAM. If the OAM layer
does not support Event Notifications (as indicated via the
dot3OamFunctionsSupported attribute), this value is ignored.
"
DEFVAL { true }
::= { dot3OamEventConfigEntry 14 }
dot3OamDyingGaspEnable OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "If true, the local OAM entity should attempt to indicate a dying gasp via the OAMPDU flags field to its peer OAM entity when a dying gasp event occurs. The exact definition of a dying gasp event is implementation dependent. If the system
dot3OamDyingGaspEnable对象类型语法TruthValue MAX-ACCESS读写状态当前描述“如果为true，则当发生濒死喘息事件时，本地OAM实体应尝试通过OAMPDU标志字段向其对等OAM实体指示濒死喘息。濒死喘息事件的确切定义取决于实现。如果系统
does not support dying gasp capability, setting this object has no effect, and reading the object should always result in 'false'.
不支持垂死喘息功能，设置此对象无效，读取对象应始终导致“false”。
By default, this object should have the value true for
Ethernet-like interfaces that support OAM. If the OAM layer
does not support Event Notifications (as indicated via the
dot3OamFunctionsSupported attribute), this value is ignored.
"
DEFVAL { true }
::= { dot3OamEventConfigEntry 15 }
By default, this object should have the value true for
Ethernet-like interfaces that support OAM. If the OAM layer
does not support Event Notifications (as indicated via the
dot3OamFunctionsSupported attribute), this value is ignored.
"
DEFVAL { true }
::= { dot3OamEventConfigEntry 15 }
dot3OamCriticalEventEnable OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "If true, the local OAM entity should attempt to indicate a critical event via the OAMPDU flags to its peer OAM entity when a critical event occurs. The exact definition of a critical event is implementation dependent. If the system does not support critical event capability, setting this object has no effect, and reading the object should always result in 'false'.
dot3OamCriticalEventEnable对象类型语法TruthValue MAX-ACCESS读写状态当前说明“如果为true，则本地OAM实体应尝试在关键事件发生时通过OAMPDU标志向其对等OAM实体指示关键事件。关键事件的确切定义取决于实现。如果系统不支持关键事件功能，则设置此对象无效，读取该对象应始终导致“false”。
By default, this object should have the value true for
Ethernet-like interfaces that support OAM. If the OAM layer
does not support Event Notifications (as indicated via the
dot3OamFunctionsSupported attribute), this value is ignored.
"
DEFVAL { true }
::= { dot3OamEventConfigEntry 16 }
By default, this object should have the value true for
Ethernet-like interfaces that support OAM. If the OAM layer
does not support Event Notifications (as indicated via the
dot3OamFunctionsSupported attribute), this value is ignored.
"
DEFVAL { true }
::= { dot3OamEventConfigEntry 16 }
-- **************************************************************
--
-- Ethernet OAM Event Log group
--
-- **************************************************************
--
-- Ethernet OAM Event Log group
--
dot3OamEventLogTable OBJECT-TYPE SYNTAX SEQUENCE OF Dot3OamEventLogEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table records a history of the events that have occurred at the Ethernet OAM level. These events can include locally detected events, which may result in locally generated OAMPDUs, and remotely detected events, which are detected by the OAM peer entity and signaled to the local entity via
dot3OamEventLogTable对象类型语法Dot3OamEventLogEntry MAX-ACCESS的序列不可访问状态当前描述“此表记录在以太网OAM级别发生的事件的历史记录。这些事件可以包括本地检测到的事件（其可能导致本地生成的oampdu）和远程检测到的事件（其由OAM对等实体检测并通过发送信号通知本地实体）
Ethernet OAM. Ethernet OAM events can be signaled by Event Notification OAMPDUs or by the flags field in any OAMPDU.
以太网OAM。以太网OAM事件可以通过事件通知OAMPDU或任何OAMPDU中的标志字段发出信号。
This table contains both threshold crossing events and non-threshold crossing events. The parameters for the threshold window, threshold value, and actual value (dot3OamEventLogWindowXX, dot3OamEventLogThresholdXX, dot3OamEventLogValue) are only applicable to threshold crossing events, and are returned as all F's (2^32 - 1) for non-threshold crossing events.
此表包含阈值交叉事件和非阈值交叉事件。阈值窗口、阈值和实际值（dot3OamEventLogWindowXX、dot3OamEventLogThresholdXX、dot3OamEventLogValue）的参数仅适用于阈值交叉事件，并作为非阈值交叉事件的所有F（2^32-1）返回。
Entries in the table are automatically created when such
events are detected. The size of the table is implementation
dependent. When the table reaches its maximum size, older
entries are automatically deleted to make room for newer
entries.
"
::= { dot3OamObjects 6 }
Entries in the table are automatically created when such
events are detected. The size of the table is implementation
dependent. When the table reaches its maximum size, older
entries are automatically deleted to make room for newer
entries.
"
::= { dot3OamObjects 6 }
dot3OamEventLogEntry OBJECT-TYPE
SYNTAX Dot3OamEventLogEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the dot3OamEventLogTable. Entries are
automatically created whenever Ethernet OAM events occur at
the local OAM entity, and when Event Notification OAMPDUs are
received at the local OAM entity (indicating that events have
occurred at the peer OAM entity). The size of the table is
implementation dependent, but when the table becomes full,
older events are automatically deleted to make room for newer
events. The table index dot3OamEventLogIndex increments for
each new entry, and when the maximum value is reached, the
value restarts at zero.
"
INDEX { ifIndex, dot3OamEventLogIndex }
::= { dot3OamEventLogTable 1 }
dot3OamEventLogEntry OBJECT-TYPE
SYNTAX Dot3OamEventLogEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the dot3OamEventLogTable. Entries are
automatically created whenever Ethernet OAM events occur at
the local OAM entity, and when Event Notification OAMPDUs are
received at the local OAM entity (indicating that events have
occurred at the peer OAM entity). The size of the table is
implementation dependent, but when the table becomes full,
older events are automatically deleted to make room for newer
events. The table index dot3OamEventLogIndex increments for
each new entry, and when the maximum value is reached, the
value restarts at zero.
"
INDEX { ifIndex, dot3OamEventLogIndex }
::= { dot3OamEventLogTable 1 }
Dot3OamEventLogEntry ::=
SEQUENCE {
dot3OamEventLogIndex Unsigned32,
dot3OamEventLogTimestamp TimeStamp,
dot3OamEventLogOui EightOTwoOui,
dot3OamEventLogType Unsigned32,
dot3OamEventLogLocation INTEGER,
dot3OamEventLogWindowHi Unsigned32,
dot3OamEventLogWindowLo Unsigned32,
dot3OamEventLogThresholdHi Unsigned32,
Dot3OamEventLogEntry ::=
SEQUENCE {
dot3OamEventLogIndex Unsigned32,
dot3OamEventLogTimestamp TimeStamp,
dot3OamEventLogOui EightOTwoOui,
dot3OamEventLogType Unsigned32,
dot3OamEventLogLocation INTEGER,
dot3OamEventLogWindowHi Unsigned32,
dot3OamEventLogWindowLo Unsigned32,
dot3OamEventLogThresholdHi Unsigned32,
dot3OamEventLogThresholdLo Unsigned32, dot3OamEventLogValue CounterBasedGauge64, dot3OamEventLogRunningTotal CounterBasedGauge64, dot3OamEventLogEventTotal Unsigned32 }
dot3OamEventLogThresholdLo Unsigned32，dot3OamEventLogValue CounterBasedGauge64，dot3OamEventLogRunningTotal CounterBasedGauge64，dot3OamEventLogEventTotal Unsigned32}
dot3OamEventLogIndex OBJECT-TYPE
SYNTAX Unsigned32(1..4294967295)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An arbitrary integer for identifying individual events
within the event log. "
::= { dot3OamEventLogEntry 1 }
dot3OamEventLogIndex OBJECT-TYPE
SYNTAX Unsigned32(1..4294967295)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An arbitrary integer for identifying individual events
within the event log. "
::= { dot3OamEventLogEntry 1 }
dot3OamEventLogTimestamp OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime at the time of the logged event. For
locally generated events, the time of the event can be
accurately retrieved from sysUpTime. For remotely generated
events, the time of the event is indicated by the reception of
the Event Notification OAMPDU indicating that the event
occurred on the peer. A system may attempt to adjust the
timestamp value to more accurately reflect the time of the
event at the peer OAM entity by using other information, such
as that found in the timestamp found of the Event Notification
TLVs, which provides an indication of the relative time
between events at the peer entity. "
::= { dot3OamEventLogEntry 2 }
dot3OamEventLogTimestamp OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime at the time of the logged event. For
locally generated events, the time of the event can be
accurately retrieved from sysUpTime. For remotely generated
events, the time of the event is indicated by the reception of
the Event Notification OAMPDU indicating that the event
occurred on the peer. A system may attempt to adjust the
timestamp value to more accurately reflect the time of the
event at the peer OAM entity by using other information, such
as that found in the timestamp found of the Event Notification
TLVs, which provides an indication of the relative time
between events at the peer entity. "
::= { dot3OamEventLogEntry 2 }
dot3OamEventLogOui OBJECT-TYPE
SYNTAX EightOTwoOui
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The OUI of the entity defining the object type. All IEEE
802.3 defined events (as appearing in [802.3ah] except for the
Organizationally Unique Event TLVs) use the IEEE 802.3 OUI of
0x0180C2. Organizations defining their own Event Notification
TLVs include their OUI in the Event Notification TLV that
gets reflected here. "
::= { dot3OamEventLogEntry 3 }
dot3OamEventLogOui OBJECT-TYPE
SYNTAX EightOTwoOui
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The OUI of the entity defining the object type. All IEEE
802.3 defined events (as appearing in [802.3ah] except for the
Organizationally Unique Event TLVs) use the IEEE 802.3 OUI of
0x0180C2. Organizations defining their own Event Notification
TLVs include their OUI in the Event Notification TLV that
gets reflected here. "
::= { dot3OamEventLogEntry 3 }
dot3OamEventLogType OBJECT-TYPE SYNTAX Unsigned32
dot3OamEventLogType对象类型语法未签名32
MAX-ACCESS read-only STATUS current DESCRIPTION "The type of event that generated this entry in the event log. When the OUI is the IEEE 802.3 OUI of 0x0180C2, the following event types are defined: erroredSymbolEvent(1), erroredFramePeriodEvent(2), erroredFrameEvent(3), erroredFrameSecondsEvent(4), linkFault(256), dyingGaspEvent(257), criticalLinkEvent(258) The first four are considered threshold crossing events, as they are generated when a metric exceeds a given value within a specified window. The other three are not threshold crossing events.
MAX-ACCESS只读状态当前描述“在事件日志中生成此项的事件类型。当OUI是0x0180C2的IEEE 802.3 OUI时，定义了以下事件类型：erroredSymbolEvent（1）、erroredFramePeriodEvent（2）、erroredFrameEvent（3）、erroredFrameSecondsEvent（4）、linkFault（256）、dyingGaspEvent（257），criticalLinkEvent（258）前四个事件被视为阈值交叉事件，因为它们是在指定窗口内度量超过给定值时生成的。其他三个事件不是阈值交叉事件。
When the OUI is not 71874 (0x0180C2 in hex), then some other
organization has defined the event space. If event subtyping
is known to the implementation, it may be reflected here.
Otherwise, this value should return all F's (2^32 - 1).
"
REFERENCE "[802.3ah], 30.3.6.1.10 and 57.5.3."
::= { dot3OamEventLogEntry 4 }
When the OUI is not 71874 (0x0180C2 in hex), then some other
organization has defined the event space. If event subtyping
is known to the implementation, it may be reflected here.
Otherwise, this value should return all F's (2^32 - 1).
"
REFERENCE "[802.3ah], 30.3.6.1.10 and 57.5.3."
::= { dot3OamEventLogEntry 4 }
dot3OamEventLogLocation OBJECT-TYPE
SYNTAX INTEGER { local(1), remote(2) }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Whether this event occurred locally (local(1)), or was
received from the OAM peer via Ethernet OAM (remote(2)).
"
::= { dot3OamEventLogEntry 5 }
dot3OamEventLogLocation OBJECT-TYPE
SYNTAX INTEGER { local(1), remote(2) }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Whether this event occurred locally (local(1)), or was
received from the OAM peer via Ethernet OAM (remote(2)).
"
::= { dot3OamEventLogEntry 5 }
dot3OamEventLogWindowHi OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "If the event represents a threshold crossing event, the two objects dot3OamEventWindowHi and dot3OamEventWindowLo, form an unsigned 64-bit integer yielding the window over which the value was measured for the threshold crossing event (for example, 5, when 11 occurrences happened in 5 seconds while the threshold was 10). The two objects are combined as:
dot3OamEventLogWindowHi对象类型语法Unsigned32 MAX-ACCESS只读状态当前描述“如果事件表示阈值交叉事件，则两个对象Dot3OameVentWinDoHi和dot3OamEventWindowLo将形成一个无符号64位整数，生成测量阈值交叉事件值的窗口（例如，5，当阈值为10时，5秒内发生11次事件）。这两个对象组合为：
dot3OamEventLogWindow = ((2^32) * dot3OamEventLogWindowHi)
+ dot3OamEventLogWindowLo
dot3OamEventLogWindow = ((2^32) * dot3OamEventLogWindowHi)
+ dot3OamEventLogWindowLo
Otherwise, this value is returned as all F's (2^32 - 1) and
adds no useful information.
"
REFERENCE "[802.3ah], 30.3.6.1.37 and 57.5.3.2."
::= { dot3OamEventLogEntry 6 }
Otherwise, this value is returned as all F's (2^32 - 1) and
adds no useful information.
"
REFERENCE "[802.3ah], 30.3.6.1.37 and 57.5.3.2."
::= { dot3OamEventLogEntry 6 }
dot3OamEventLogWindowLo OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "If the event represents a threshold crossing event, the two objects dot3OamEventWindowHi and dot3OamEventWindowLo form an unsigned 64-bit integer yielding the window over which the value was measured for the threshold crossing event (for example, 5, when 11 occurrences happened in 5 seconds while the threshold was 10). The two objects are combined as:
dot3OamEventLogWindowLo对象类型语法Unsigned32 MAX-ACCESS只读状态当前说明“如果事件表示阈值交叉事件，则两个对象dot3OamEventWindowHi和dot3OamEventWindowLo形成一个无符号64位整数，生成为阈值交叉事件测量值的窗口（例如，5，当阈值为10时，5秒内发生11次事件）。这两个对象组合为：
dot3OamEventLogWindow = ((2^32) * dot3OamEventLogWindowHi)
+ dot3OamEventLogWindowLo
dot3OamEventLogWindow = ((2^32) * dot3OamEventLogWindowHi)
+ dot3OamEventLogWindowLo
Otherwise, this value is returned as all F's (2^32 - 1) and
adds no useful information.
"
REFERENCE "[802.3ah], 30.3.6.1.37 and 57.5.3.2."
::= { dot3OamEventLogEntry 7 }
Otherwise, this value is returned as all F's (2^32 - 1) and
adds no useful information.
"
REFERENCE "[802.3ah], 30.3.6.1.37 and 57.5.3.2."
::= { dot3OamEventLogEntry 7 }
dot3OamEventLogThresholdHi OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "If the event represents a threshold crossing event, the two objects dot3OamEventThresholdHi and dot3OamEventThresholdLo form an unsigned 64-bit integer yielding the value that was crossed for the threshold crossing event (for example, 10, when 11 occurrences happened in 5 seconds while the threshold was 10). The two objects are combined as:
dot3OamEventLogThresholdHi对象类型语法Unsigned32 MAX-ACCESS只读状态当前描述“如果事件表示阈值交叉事件，则两个对象dot3OamEventThresholdHi和dot3OamEventThresholdLo形成一个无符号64位整数，生成阈值交叉事件的交叉值（例如，10，当阈值为10时，5秒内发生11次事件）。这两个对象组合为：
dot3OamEventLogThreshold = ((2^32) * dot3OamEventLogThresholdHi)
+ dot3OamEventLogThresholdLo
dot3OamEventLogThreshold = ((2^32) * dot3OamEventLogThresholdHi)
+ dot3OamEventLogThresholdLo
Otherwise, this value is returned as all F's (2^32 -1) and adds no useful information. "
否则，该值将作为所有F（2^32-1）返回，并且不会添加任何有用的信息。"
REFERENCE "[802.3ah], 30.3.6.1.37 and 57.5.3.2."
::= { dot3OamEventLogEntry 8 }
REFERENCE "[802.3ah], 30.3.6.1.37 and 57.5.3.2."
::= { dot3OamEventLogEntry 8 }
dot3OamEventLogThresholdLo OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "If the event represents a threshold crossing event, the two objects dot3OamEventThresholdHi and dot3OamEventThresholdLo form an unsigned 64-bit integer yielding the value that was crossed for the threshold crossing event (for example, 10, when 11 occurrences happened in 5 seconds while the threshold was 10). The two objects are combined as:
dot3OamEventLogThresholdLo对象类型语法Unsigned32 MAX-ACCESS只读状态当前描述“如果事件表示阈值交叉事件，则两个对象dot3OamEventThresholdHi和dot3OamEventThresholdLo形成一个无符号64位整数，生成阈值交叉事件的交叉值（例如，10，当阈值为10时，5秒内发生11次事件）。这两个对象组合为：
dot3OamEventLogThreshold = ((2^32) * dot3OamEventLogThresholdHi)
+ dot3OamEventLogThresholdLo
dot3OamEventLogThreshold = ((2^32) * dot3OamEventLogThresholdHi)
+ dot3OamEventLogThresholdLo
Otherwise, this value is returned as all F's (2^32 - 1) and
adds no useful information.
"
REFERENCE "[802.3ah], 30.3.6.1.37 and 57.5.3.2."
::= { dot3OamEventLogEntry 9 }
Otherwise, this value is returned as all F's (2^32 - 1) and
adds no useful information.
"
REFERENCE "[802.3ah], 30.3.6.1.37 and 57.5.3.2."
::= { dot3OamEventLogEntry 9 }
dot3OamEventLogValue OBJECT-TYPE SYNTAX CounterBasedGauge64 MAX-ACCESS read-only STATUS current DESCRIPTION "If the event represents a threshold crossing event, this value indicates the value of the parameter within the given window that generated this event (for example, 11, when 11 occurrences happened in 5 seconds while the threshold was 10).
dot3OamEventLogValue对象类型语法CounterBasedGauge64 MAX-ACCESS只读状态当前描述“如果事件表示阈值交叉事件，此值表示生成此事件的给定窗口内的参数值（例如，11，当阈值为10时，5秒内发生11次）。
Otherwise, this value is returned as all F's
(2^64 - 1) and adds no useful information.
"
REFERENCE "[802.3ah], 30.3.6.1.37 and 57.5.3.2."
::= { dot3OamEventLogEntry 10 }
Otherwise, this value is returned as all F's
(2^64 - 1) and adds no useful information.
"
REFERENCE "[802.3ah], 30.3.6.1.37 and 57.5.3.2."
::= { dot3OamEventLogEntry 10 }
dot3OamEventLogRunningTotal OBJECT-TYPE SYNTAX CounterBasedGauge64 MAX-ACCESS read-only STATUS current DESCRIPTION "Each Event Notification TLV contains a running total of the number of times an event has occurred, as well as the number of times an Event Notification for the event has been
dot3OamEventLogRunningTotal对象类型语法CounterBasedGauge64 MAX-ACCESS只读状态当前描述“每个事件通知TLV包含事件发生次数的运行总数，以及事件的事件通知发出的次数
transmitted. For non-threshold crossing events, the number of events (dot3OamLogRunningTotal) and the number of resultant Event Notifications (dot3OamLogEventTotal) should be identical.
传送。对于非阈值交叉事件，事件数（dot3OamLogRunningTotal）和结果事件通知数（dot3OamLogEventTotal）应相同。
For threshold crossing events, since multiple occurrences may
be required to cross the threshold, these values are likely
different. This value represents the total number of times
this event has happened since the last reset (for example,
3253, when 3253 symbol errors have occurred since the last
reset, which has resulted in 51 symbol error threshold
crossing events since the last reset).
"
REFERENCE "[802.3ah], 30.3.6.1.37 and 57.5.3.2."
::= { dot3OamEventLogEntry 11 }
For threshold crossing events, since multiple occurrences may
be required to cross the threshold, these values are likely
different. This value represents the total number of times
this event has happened since the last reset (for example,
3253, when 3253 symbol errors have occurred since the last
reset, which has resulted in 51 symbol error threshold
crossing events since the last reset).
"
REFERENCE "[802.3ah], 30.3.6.1.37 and 57.5.3.2."
::= { dot3OamEventLogEntry 11 }
dot3OamEventLogEventTotal OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "Each Event Notification TLV contains a running total of the number of times an event has occurred, as well as the number of times an Event Notification for the event has been transmitted. For non-threshold crossing events, the number of events (dot3OamLogRunningTotal) and the number of resultant Event Notifications (dot3OamLogEventTotal) should be identical.
dot3OamEventLogEventTotal对象类型语法Unsigned32 MAX-ACCESS只读状态当前描述“每个事件通知TLV包含事件发生次数的运行总数，以及事件的事件通知的传输次数。对于非阈值交叉事件，事件数（dot3OamLogRunningTotal）和结果事件通知数（dot3OamLogEventTotal）应相同。
For threshold crossing events, since multiple occurrences may
be required to cross the threshold, these values are likely
different. This value represents the total number of times
one or more of these occurrences have resulted in an Event
Notification (for example, 51 when 3253 symbol errors have
occurred since the last reset, which has resulted in 51 symbol
error threshold crossing events since the last reset).
"
REFERENCE "[802.3ah], 30.3.6.1.37 and 57.5.3.2."
::= { dot3OamEventLogEntry 12 }
For threshold crossing events, since multiple occurrences may
be required to cross the threshold, these values are likely
different. This value represents the total number of times
one or more of these occurrences have resulted in an Event
Notification (for example, 51 when 3253 symbol errors have
occurred since the last reset, which has resulted in 51 symbol
error threshold crossing events since the last reset).
"
REFERENCE "[802.3ah], 30.3.6.1.37 and 57.5.3.2."
::= { dot3OamEventLogEntry 12 }
-- ***************************************************************
--
-- Ethernet OAM Notifications
--
-- ***************************************************************
--
-- Ethernet OAM Notifications
--
dot3OamThresholdEvent NOTIFICATION-TYPE OBJECTS { dot3OamEventLogTimestamp, dot3OamEventLogOui,
dot3OamThresholdEvent通知类型对象{dot3OamEventLogTimestamp，dot3OamEventLogOui，
dot3OamEventLogType, dot3OamEventLogLocation, dot3OamEventLogWindowHi, dot3OamEventLogWindowLo, dot3OamEventLogThresholdHi, dot3OamEventLogThresholdLo, dot3OamEventLogValue, dot3OamEventLogRunningTotal, dot3OamEventLogEventTotal } STATUS current DESCRIPTION "A dot3OamThresholdEvent notification is sent when a local or remote threshold crossing event is detected. A local threshold crossing event is detected by the local entity, while a remote threshold crossing event is detected by the reception of an Ethernet OAM Event Notification OAMPDU that indicates a threshold event.
dot3OamEventLogType、dot3OamEventLogLocation、dot3OamEventLogWindowHi、dot3OamEventLogWindowLo、dot3OamEventLogThresholdHi、dot3OamEventLogThresholdLo、dot3OamEventLogValue、dot3OamEventLogRunningTotal、dot3oameventlogetottal}状态当前说明“当检测到本地或远程阈值交叉事件时，将发送dot3OamThresholdEvent通知。本地实体检测到本地阈值跨越事件，而通过接收指示阈值事件的以太网OAM事件通知OAMPDU检测到远程阈值跨越事件。
This notification should not be sent more than once per second.
此通知每秒发送不应超过一次。
The OAM entity can be derived from extracting the ifIndex from the variable bindings. The objects in the notification correspond to the values in a row instance in the dot3OamEventLogTable.
OAM实体可以通过从变量绑定中提取ifIndex来派生。通知中的对象对应于dot3OamEventLogTable中的行实例中的值。
The management entity should periodically check
dot3OamEventLogTable to detect any missed events."
::= { dot3OamNotifications 1 }
The management entity should periodically check
dot3OamEventLogTable to detect any missed events."
::= { dot3OamNotifications 1 }
dot3OamNonThresholdEvent NOTIFICATION-TYPE OBJECTS { dot3OamEventLogTimestamp, dot3OamEventLogOui, dot3OamEventLogType, dot3OamEventLogLocation, dot3OamEventLogEventTotal } STATUS current DESCRIPTION "A dot3OamNonThresholdEvent notification is sent when a local or remote non-threshold crossing event is detected. A local event is detected by the local entity, while a remote event is detected by the reception of an Ethernet OAM Event Notification OAMPDU that indicates a non-threshold crossing event.
dot3OamNonThresholdEvent通知类型对象{dot3OamEventLogTimestamp、DOT3OAMEVENTLOGUI、dot3OamEventLogType、dot3OamEventLogLocation、DOT3OAMEVENTLOGOTTAL}状态当前说明“当检测到本地或远程非阈值交叉事件时，将发送dot3OamNonThresholdEvent通知。本地实体检测本地事件，而通过接收指示非阈值跨越事件的以太网OAM事件通知OAMPDU检测远程事件。
This notification should not be sent more than once per
每次发送此通知不应超过一次
second.
第二
The OAM entity can be derived from extracting the ifIndex from the variable bindings. The objects in the notification correspond to the values in a row instance of the dot3OamEventLogTable.
OAM实体可以通过从变量绑定中提取ifIndex来派生。通知中的对象对应于dot3OamEventLogTable的行实例中的值。
The management entity should periodically check
dot3OamEventLogTable to detect any missed events."
::= { dot3OamNotifications 2 }
The management entity should periodically check
dot3OamEventLogTable to detect any missed events."
::= { dot3OamNotifications 2 }
-- ***************************************************************
--
-- Ethernet OAM Compliance group
--
-- ***************************************************************
--
-- Ethernet OAM Compliance group
--
dot3OamGroups OBJECT IDENTIFIER ::= { dot3OamConformance 1 }
dot3OamCompliances OBJECT IDENTIFIER ::= { dot3OamConformance 2 }
dot3OamGroups OBJECT IDENTIFIER ::= { dot3OamConformance 1 }
dot3OamCompliances OBJECT IDENTIFIER ::= { dot3OamConformance 2 }
-- Compliance statements
--合规声明
dot3OamCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for managed entities supporting OAM on Ethernet-like interfaces. " MODULE -- this module MANDATORY-GROUPS { dot3OamControlGroup, dot3OamPeerGroup, dot3OamStatsBaseGroup }
dot3OamCompliance MODULE-COMPLIANCE STATUS当前描述“支持类以太网接口上的OAM的受管实体的符合性声明”。MODULE--此模块必须包含-GROUPS{dot3OamControlGroup，DOT3OAMPERGROUP，dot3OamStatsBaseGroup}
GROUP dot3OamLoopbackGroup DESCRIPTION "This group is mandatory for all IEEE 802.3 OA implementations that support loopback functionality. "
GROUP dot3OamLoopbackGroup DESCRIPTION“此组对于支持环回功能的所有IEEE 802.3 OA实现都是必需的。”
GROUP dot3OamErrSymbolPeriodEventGroup DESCRIPTION "This group is mandatory for all IEEE 802.3 OA implementations that support event functionality. "
GROUP Dot3OamerSymbolPeriodEventGroup DESCRIPTION“此组对于所有支持事件功能的IEEE 802.3 OA实现都是必需的。”
GROUP dot3OamErrFramePeriodEventGroup DESCRIPTION "This group is mandatory for all IEEE 802.3 OA implementations that support event functionality. "
GROUP dot3OamErrFramePeriodEventGroup DESCRIPTION“此组对于所有支持事件功能的IEEE 802.3 OA实现都是必需的。”
GROUP dot3OamErrFrameEventGroup
点群事件组
DESCRIPTION "This group is mandatory for all IEEE 802.3 OA implementations that support event functionality. "
DESCRIPTION“此组对于支持事件功能的所有IEEE 802.3 OA实现都是必需的。”
GROUP dot3OamErrFrameSecsSummaryEventGroup DESCRIPTION "This group is mandatory for all IEEE 802.3 OA implementations that support event functionality. "
GROUP Dot3OAmerrFrameSecSSumaryEventGroup DESCRIPTION“此组对于所有支持事件功能的IEEE 802.3 OA实现都是必需的。”
GROUP dot3OamFlagEventGroup DESCRIPTION "This group is optional for all IEEE 802.3 OA implementations. The ability to send critical events or dying gasp events is not required in any system."
GROUP dot3OamFlagEventGroup DESCRIPTION“此组对于所有IEEE 802.3 OA实现都是可选的。任何系统都不需要发送关键事件或垂死喘息事件的功能。”
GROUP dot3OamEventLogGroup DESCRIPTION "This group is optional for all IEEE 802.3 OA implementations. Entries in this table are dependent on what event functionality is supported in the local OA implementation. At least one type of event must be supported for entries to appear in this table. "
GROUP dot3OamEventLogGroup DESCRIPTION“此组对于所有IEEE 802.3 OA实现都是可选的。此表中的条目取决于本地OA实现中支持的事件功能。必须至少支持一种类型的事件，才能使条目显示在此表中。”
GROUP dot3OamNotificationGroup DESCRIPTION "This group is optional for all IEEE 802.3 OA implementations. Since the information in the notifications is dependent on the dot3OamEventLogTable, that table must be implemented for notifications. "
GROUP dot3OamNotificationGroup DESCRIPTION“此组对于所有IEEE 802.3 OA实现都是可选的。由于通知中的信息依赖于dot3OamEventLogTable，因此必须为通知实现该表。”
::= { dot3OamCompliances 1}
::= { dot3OamCompliances 1}
dot3OamControlGroup OBJECT-GROUP
OBJECTS { dot3OamAdminState,
dot3OamOperStatus,
dot3OamMode,
dot3OamMaxOamPduSize,
dot3OamConfigRevision,
dot3OamFunctionsSupported
}
STATUS current
DESCRIPTION
"A collection of objects providing the abilities,
configuration, and status of an Ethernet OAM entity. "
::= { dot3OamGroups 1 }
dot3OamControlGroup OBJECT-GROUP
OBJECTS { dot3OamAdminState,
dot3OamOperStatus,
dot3OamMode,
dot3OamMaxOamPduSize,
dot3OamConfigRevision,
dot3OamFunctionsSupported
}
STATUS current
DESCRIPTION
"A collection of objects providing the abilities,
configuration, and status of an Ethernet OAM entity. "
::= { dot3OamGroups 1 }
dot3OamPeerGroup OBJECT-GROUP OBJECTS { dot3OamPeerMacAddress,
DOT3OAMPERGROUP对象组对象{DOT3OAMPERMACADRESS，
dot3OamPeerVendorOui,
dot3OamPeerVendorInfo,
dot3OamPeerMode,
dot3OamPeerFunctionsSupported,
dot3OamPeerMaxOamPduSize,
dot3OamPeerConfigRevision
}
STATUS current
DESCRIPTION
"A collection of objects providing the abilities,
configuration, and status of a peer Ethernet OAM entity. "
::= { dot3OamGroups 2 }
dot3OamPeerVendorOui,
dot3OamPeerVendorInfo,
dot3OamPeerMode,
dot3OamPeerFunctionsSupported,
dot3OamPeerMaxOamPduSize,
dot3OamPeerConfigRevision
}
STATUS current
DESCRIPTION
"A collection of objects providing the abilities,
configuration, and status of a peer Ethernet OAM entity. "
::= { dot3OamGroups 2 }
dot3OamStatsBaseGroup OBJECT-GROUP
OBJECTS { dot3OamInformationTx,
dot3OamInformationRx,
dot3OamUniqueEventNotificationTx,
dot3OamUniqueEventNotificationRx,
dot3OamDuplicateEventNotificationTx,
dot3OamDuplicateEventNotificationRx,
dot3OamLoopbackControlTx,
dot3OamLoopbackControlRx,
dot3OamVariableRequestTx,
dot3OamVariableRequestRx,
dot3OamVariableResponseTx,
dot3OamVariableResponseRx,
dot3OamOrgSpecificTx,
dot3OamOrgSpecificRx,
dot3OamUnsupportedCodesTx,
dot3OamUnsupportedCodesRx,
dot3OamFramesLostDueToOam
}
STATUS current
DESCRIPTION
"A collection of objects providing the statistics for the
number of various transmit and receive events for OAM on an
Ethernet-like interface. Note that all of these counters must
be supported even if the related function (as described in
dot3OamFunctionsSupported) is not supported. "
::= { dot3OamGroups 3 }
dot3OamStatsBaseGroup OBJECT-GROUP
OBJECTS { dot3OamInformationTx,
dot3OamInformationRx,
dot3OamUniqueEventNotificationTx,
dot3OamUniqueEventNotificationRx,
dot3OamDuplicateEventNotificationTx,
dot3OamDuplicateEventNotificationRx,
dot3OamLoopbackControlTx,
dot3OamLoopbackControlRx,
dot3OamVariableRequestTx,
dot3OamVariableRequestRx,
dot3OamVariableResponseTx,
dot3OamVariableResponseRx,
dot3OamOrgSpecificTx,
dot3OamOrgSpecificRx,
dot3OamUnsupportedCodesTx,
dot3OamUnsupportedCodesRx,
dot3OamFramesLostDueToOam
}
STATUS current
DESCRIPTION
"A collection of objects providing the statistics for the
number of various transmit and receive events for OAM on an
Ethernet-like interface. Note that all of these counters must
be supported even if the related function (as described in
dot3OamFunctionsSupported) is not supported. "
::= { dot3OamGroups 3 }
dot3OamLoopbackGroup OBJECT-GROUP OBJECTS { dot3OamLoopbackStatus, dot3OamLoopbackIgnoreRx } STATUS current DESCRIPTION "A collection of objects for controlling the OAM remote
dot3OamLoopbackGroup OBJECT-GROUP OBJECTS{dot3OamLoopbackStatus，dot3OamLoopbackIgnoreRx}状态当前描述“用于控制OAM远程服务器的对象集合
loopback function. "
::= { dot3OamGroups 4 }
loopback function. "
::= { dot3OamGroups 4 }
dot3OamErrSymbolPeriodEventGroup OBJECT-GROUP OBJECTS { dot3OamErrSymPeriodWindowHi, dot3OamErrSymPeriodWindowLo, dot3OamErrSymPeriodThresholdHi, dot3OamErrSymPeriodThresholdLo, dot3OamErrSymPeriodEvNotifEnable } STATUS current DESCRIPTION "A collection of objects for configuring the thresholds for an Errored Symbol Period Event.
dot3OamErrSymbolPeriodEventGroup对象组对象{dot3OamErrSymPeriodWindowHi、dot3OamErrSymPeriodWindowLo、dot3OamErrSymPeriodThresholdHi、dot3OamErrSymPeriodThresholdLo、dot3OamErrSymPeriodEvNotifEnable}状态当前描述“用于配置错误符号周期事件阈值的对象集合。
Each [802.3ah] defined Event Notification TLV has its own
conformance group because each event can be implemented
independently of any other. "
::= { dot3OamGroups 5 }
Each [802.3ah] defined Event Notification TLV has its own
conformance group because each event can be implemented
independently of any other. "
::= { dot3OamGroups 5 }
dot3OamErrFramePeriodEventGroup OBJECT-GROUP OBJECTS { dot3OamErrFramePeriodWindow, dot3OamErrFramePeriodThreshold, dot3OamErrFramePeriodEvNotifEnable } STATUS current DESCRIPTION "A collection of objects for configuring the thresholds for an Errored Frame Period Event.
dot3OamErrFramePeriodEventGroup对象组对象{dot3OamErrFramePeriodWindow，dot3OamErrFramePeriodThreshold，dot3OamErrFramePeriodEvNotifEnable}状态当前描述“用于配置错误帧周期事件阈值的对象集合。
Each [802.3ah] defined Event Notification TLV has its own
conformance group because each event can be implemented
independently of any other. "
::= { dot3OamGroups 6 }
Each [802.3ah] defined Event Notification TLV has its own
conformance group because each event can be implemented
independently of any other. "
::= { dot3OamGroups 6 }
dot3OamErrFrameEventGroup OBJECT-GROUP OBJECTS { dot3OamErrFrameWindow, dot3OamErrFrameThreshold, dot3OamErrFrameEvNotifEnable } STATUS current DESCRIPTION "A collection of objects for configuring the thresholds for an Errored Frame Event.
dot3OamErrFrameEventGroup对象组对象{dot3OamErrFrameWindow，dot3OamErrFrameThreshold，dot3OamErrFrameEvNotifEnable}状态当前描述“用于配置错误帧事件阈值的对象集合。
Each [802.3ah] defined Event Notification TLV has its own conformance group because each event can be implemented independently of any other. "
每个[802.3ah]定义的事件通知TLV都有自己的一致性组，因为每个事件都可以独立于任何其他事件来实现。"
::= { dot3OamGroups 7 }
::= { dot3OamGroups 7 }
dot3OamErrFrameSecsSummaryEventGroup OBJECT-GROUP OBJECTS { dot3OamErrFrameSecsSummaryWindow, dot3OamErrFrameSecsSummaryThreshold, dot3OamErrFrameSecsEvNotifEnable } STATUS current DESCRIPTION "A collection of objects for configuring the thresholds for an Errored Frame Seconds Summary Event.
DOT3OAMERRFRAMESECSSUMARYEVENTGROUP对象组对象{DOT3OAMERRFRAMESECSSUMARYWindow、DOT3OAMERRFRAMESECSSUMARYThreshold、DOT3OAMERRFRAMESECESEVENTIFENABLE}状态当前描述“用于配置错误帧秒摘要事件阈值的对象集合。
Each [802.3ah] defined Event Notification TLV has its own
conformance group because each event can be implemented
independently of any other. "
::= { dot3OamGroups 8 }
Each [802.3ah] defined Event Notification TLV has its own
conformance group because each event can be implemented
independently of any other. "
::= { dot3OamGroups 8 }
dot3OamFlagEventGroup OBJECT-GROUP
OBJECTS { dot3OamDyingGaspEnable,
dot3OamCriticalEventEnable
}
STATUS current
DESCRIPTION
"A collection of objects for configuring the sending OAMPDUs
with the critical event flag or dying gasp flag enabled. "
::= { dot3OamGroups 9 }
dot3OamFlagEventGroup OBJECT-GROUP
OBJECTS { dot3OamDyingGaspEnable,
dot3OamCriticalEventEnable
}
STATUS current
DESCRIPTION
"A collection of objects for configuring the sending OAMPDUs
with the critical event flag or dying gasp flag enabled. "
::= { dot3OamGroups 9 }
dot3OamEventLogGroup OBJECT-GROUP
OBJECTS { dot3OamEventLogTimestamp,
dot3OamEventLogOui,
dot3OamEventLogType,
dot3OamEventLogLocation,
dot3OamEventLogWindowHi,
dot3OamEventLogWindowLo,
dot3OamEventLogThresholdHi,
dot3OamEventLogThresholdLo,
dot3OamEventLogValue,
dot3OamEventLogRunningTotal,
dot3OamEventLogEventTotal
}
STATUS current
DESCRIPTION
"A collection of objects for configuring the thresholds for an
Errored Frame Seconds Summary Event and maintaining the event
information. "
::= { dot3OamGroups 10 }
dot3OamEventLogGroup OBJECT-GROUP
OBJECTS { dot3OamEventLogTimestamp,
dot3OamEventLogOui,
dot3OamEventLogType,
dot3OamEventLogLocation,
dot3OamEventLogWindowHi,
dot3OamEventLogWindowLo,
dot3OamEventLogThresholdHi,
dot3OamEventLogThresholdLo,
dot3OamEventLogValue,
dot3OamEventLogRunningTotal,
dot3OamEventLogEventTotal
}
STATUS current
DESCRIPTION
"A collection of objects for configuring the thresholds for an
Errored Frame Seconds Summary Event and maintaining the event
information. "
::= { dot3OamGroups 10 }
dot3OamNotificationGroup NOTIFICATION-GROUP
dot3OamNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS {
dot3OamThresholdEvent,
dot3OamNonThresholdEvent
}
STATUS current
DESCRIPTION
"A collection of notifications used by Ethernet OAM to signal
to a management entity that local or remote events have
occurred on a specified Ethernet link. "
::= { dot3OamGroups 11 }
NOTIFICATIONS {
dot3OamThresholdEvent,
dot3OamNonThresholdEvent
}
STATUS current
DESCRIPTION
"A collection of notifications used by Ethernet OAM to signal
to a management entity that local or remote events have
occurred on a specified Ethernet link. "
::= { dot3OamGroups 11 }
END
终止
The readable objects in this module can provide information about network traffic, and therefore may be considered sensitive. In particular, OAM provides mechanisms for reading the IEEE 802.3 Clause 30 MIB attributes from a link partner via a specialized layer two protocol. Unlike SNMP, IEEE P802.3ah OAM does not include encryption or authentication mechanisms. It should be used in environments where either this interface information is not considered sensitive, or where the facility terminations are protected. By default, OAM is disabled on Ethernet-like interfaces and is therefore not a risk.
该模块中的可读对象可以提供有关网络流量的信息，因此可能被认为是敏感的。尤其是，OAM提供了通过专用的第二层协议从链路伙伴读取IEEE 802.3第30条MIB属性的机制。与SNMP不同，IEEE P802.3ah OAM不包括加密或身份验证机制。它应用于接口信息不敏感或设施终端受到保护的环境中。默认情况下，在类似以太网的接口上禁用OAM，因此不存在风险。
IEEE 802.3ah OAM is designed to support deployment in access and enterprise networks. In access networks, one end of a link is the CO-side, and the other is the CPE-side, and the facilities are often protected in wiring cages or closets. In such deployments, it is often the case that the CO-side is protected from access from the CPE-side. Within IEEE P802.3ah OAM, this protection from remote access is accomplished by configuring the CPE-side in passive mode using the dot3OamMode attribute. This prevents the CPE from accessing functions and information at the CO-side of the connection. In enterprise networks, read-only interface information is often considered non-sensitive.
IEEE 802.3ah OAM旨在支持在接入和企业网络中的部署。在接入网络中，链路的一端是CO端，另一端是CPE端，设施通常在接线盒或机柜中进行保护。在这种部署中，通常情况下，CO侧受到保护，不受来自CPE侧的访问。在IEEE P802.3ah OAM中，通过使用dot3OamMode属性在被动模式下配置CPE端来实现远程访问保护。这防止CPE访问连接的CO端的功能和信息。在企业网络中，只读接口信息通常被认为是不敏感的。
The frequency of OAM PDUs on an Ethernet interface does not adversely affect data traffic, as OAM is a slow protocol with very limited bandwidth potential, and it is not required for normal link operation. And although there are a number of objects in this module with read-write or read-create MAX-ACCESS, they have limited effects on user data.
以太网接口上的OAM PDU的频率不会对数据流量产生不利影响，因为OAM是一种具有非常有限带宽潜力的慢速协议，并且正常链路操作不需要它。尽管此模块中有许多对象具有读写或读创建最大访问权限，但它们对用户数据的影响有限。
The loopback capability of OAM can have potentially disruptive effects in that the when enabling remote loopback, the remote station automatically transmits all received traffic back to the local station except for OAM traffic. This completely disrupts all higher
OAM的环回功能可能具有潜在的破坏性影响，因为当启用远程环回时，远程站自动将所有接收到的流量发送回本地站，OAM流量除外。这完全扰乱了更高层次的生活
layer protocols such as bridging, IP, and SNMP. Therefore an attribute (dot3OamLoopbackIgnoreRx) was introduced to control whether the local station processes or ignores received loopback commands.
层协议，如桥接、IP和SNMP。因此，引入了一个属性（dot3oamloopbackignorex）来控制本地站是否处理或忽略接收到的环回命令。
The administrative state and mode are also read-write objects. Disabling OAM can interrupt management activities between peer devices, potentially causing serious problems. Setting the dot3OamMode to an undesired value can allow access to Ethernet monitoring, events, and functions that may not be acceptable in a particular deployment scenario. In addition to loopback functionality, Ethernet interface statistics and events can be accessed via the OAM protocol, which may not be desired in some circumstances.
管理状态和模式也是读写对象。禁用OAM会中断对等设备之间的管理活动，可能导致严重问题。将dot3OamMode设置为不需要的值可以允许访问在特定部署场景中可能不可接受的以太网监视、事件和功能。除了环回功能外，还可以通过OAM协议访问以太网接口统计信息和事件，这在某些情况下可能不需要。
OAM event configuration also contains read-write objects. These objects control whether events are sent, and at what thresholds. Note that the frequency of event communication is limited by the frequency limits of Slow Protocols on Ethernet interfaces. Also, the information available via OAM events is also available via OA Variable Requests. Access to this information via either OAM events or Variable Requests is controlled by the dot3OamAdminState and dot3OamMode objects. As mentioned previously, inadequate protection of these variables can result in access to link information and functions.
OAM事件配置还包含读写对象。这些对象控制是否发送事件以及发送阈值。请注意，事件通信的频率受以太网接口上慢速协议的频率限制。此外，通过OAM事件获得的信息也可以通过OA变量请求获得。通过OAM事件或变量请求访问此信息由dot3OamAdminState和dot3OamMode对象控制。如前所述，对这些变量的保护不足可能导致访问链接信息和功能。
SNMP versions prior to SNMPv3 did not include adequate security. Even if the network itself is secure (for example by using IPsec), even then, there is no control as to who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in this MIB module.
SNMPv3之前的SNMP版本未包含足够的安全性。即使网络本身是安全的（例如通过使用IPsec），即使如此，也无法控制安全网络上的谁可以访问和获取/设置（读取/更改/创建/删除）此MIB模块中的对象。
It is RECOMMENDED that implementers consider the security features as provided by the SNMPv3 framework (see [RFC3410], section 8), including full support for the SNMPv3 cryptographic mechanisms (for authentication and privacy).
建议实施者考虑SNMPv3框架所提供的安全特性（参见[RCFC310]，第8节），包括对SNMPv3加密机制的完全支持（用于身份验证和隐私）。
Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic security. It is then a customer/operator responsibility to ensure that the SNMP entity giving access to an instance of this MIB module is properly configured to give access to the objects only to those principals (users) that have legitimate rights to indeed GET or SET (change/create/delete) them.
此外，不建议部署SNMPv3之前的SNMP版本。相反，建议部署SNMPv3并启用加密安全性。然后，客户/运营商应负责确保授予访问此MIB模块实例权限的SNMP实体已正确配置为仅授予那些拥有确实获取或设置（更改/创建/删除）对象的合法权限的主体（用户）访问对象。
The Ethernet OAM MIB requires the allocation of a single object identifier for its MODULE-IDENTITY under the MIB-2 tree.
以太网OAM MIB需要在MIB-2树下为其模块标识分配单个对象标识符。
The MIB module in this document uses the following IANA-assigned OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
本文档中的MIB模块使用SMI编号注册表中记录的以下IANA分配的对象标识符值：
Descriptor OBJECT IDENTIFIER
---------- -----------------
dot3OamMIB { mib-2 158 }
Descriptor OBJECT IDENTIFIER
---------- -----------------
dot3OamMIB { mib-2 158 }
[802.3ah] Institute of Electrical and Electronic Engineers, IEEE Std 802.3ah-2004, "Part 3: Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications - Amendment: Media Access Control Parameters, Physical Layers and Management Parameters for Subscriber Access Networks", October 2004.
[802.3ah]电气和电子工程师协会，IEEE标准802.3ah-2004，“第3部分：带冲突检测的载波侦听多址（CSMA/CD）接入方法和物理层规范-修订：用户接入网络的媒体接入控制参数、物理层和管理参数”，2004年10月。
[802.3-2002] Institute of Electrical and Electronic Engineers, IEEE Std 802.3-2003, "IEEE Standard for Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications - Draft amendment to - Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 3: Carrier sense multiple access with collision detection (CSMA/CD) access method and physical layer specifications - Media Access Control Parameters, Physical Layers and Management Parameters", March 2002.
[802.3-2002]电气和电子工程师协会，IEEE标准802.3-2003，“带冲突检测的载波侦听多址接入IEEE标准（CSMA/CD）存取方法和物理层规范.信息技术.系统间远程通信和信息交换.局域网和城域网.特殊要求.第3部分：带冲突检测的载波侦听多路存取（CSMA/CD）访问方法和物理层规范-媒体访问控制参数、物理层和管理参数”，2002年3月。
[802.3-2005] Institute of Electrical and Electronic Engineers, IEEE Std 802.3-2005, "IEEE Standard for Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications - Draft amendment to - Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 3: Carrier sense multiple access with collision detection (CSMA/CD) access method and physical layer specifications - Media Access Control Parameters, Physical Layers and Management Parameters", December 2005.
[802.3-2005]电气和电子工程师协会，IEEE标准802.3-2005，“带冲突检测的载波侦听多址接入IEEE标准（CSMA/CD）存取方法和物理层规范.信息技术.系统间远程通信和信息交换.局域网和城域网.特殊要求.第3部分：带冲突检测的载波侦听多路存取（CSMA/CD）访问方法和物理层规范-媒体访问控制参数、物理层和管理参数”，2005年12月。
[802-2001] Institute of Electrical and Electronic Engineers, IEEE Std 802-2001, "Standard for Local and Metropolitan Area Networks: Architecture and Overview", March 2002.
[802-2001]电气和电子工程师协会，IEEE标准802-2001，“局域网和城域网标准：体系结构和概述”，2002年3月。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2578]McCloghrie，K.，Perkins，D.，和J.Schoenwaeld，“管理信息的结构版本2（SMIv2）”，STD 58，RFC 2578，1999年4月。
[RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2579]McCloghrie，K.，Perkins，D.，和J.Schoenwaeld，“SMIv2的文本约定”，STD 58，RFC 2579，1999年4月。
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999.
[RFC2580]McCloghrie，K.，Perkins，D.，和J.Schoenwaeld，“SMIv2的一致性声明”，STD 58，RFC 25801999年4月。
[RFC2856] Bierman, A., McCloghrie, K., and R. Presuhn, "Textual Conventions for Additional High Capacity Data Types", RFC 2856, June 2000.
[RFC2856]Bierman，A.，McCloghrie，K.，和R.Presohn，“附加高容量数据类型的文本约定”，RFC 28562000年6月。
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", RFC 2863, June 2000.
[RFC2863]McCloghrie，K.和F.Kastenholz，“接口组MIB”，RFC 28632000年6月。
[802.3ah-copper] Beili, Ed, "Ethernet in the First Mile Copper (EFMCu) Interfaces MIB", Work in Progress, February 2007.
[802.3ah-copper]Beili，Ed，“第一英里铜缆中的以太网（EFMCu）接口MIB”，正在进行的工作，2007年2月。
[802.3ah-epon] Khermosh, L., "Managed Objects of Ethernet Passive Optical Networks (EPON)", RFC 4837, June 2007.
[802.3ah-epon]Khermosh，L.“以太网无源光网络（epon）的管理对象”，RFC 4837，2007年6月。
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction and Applicability Statements for Internet-Standard Management Framework", RFC 3410, December 2002.
[RFC3410]Case，J.，Mundy，R.，Partain，D.，和B.Stewart，“互联网标准管理框架的介绍和适用性声明”，RFC 34102002年12月。
[RFC3635] Flick, J., "Definitions of Managed Objects for the Ethernet-like Interface Types", RFC 3635, September 2003.
[RFC3635]Flick，J.，“类似以太网接口类型的托管对象定义”，RFC 3635，2003年9月。
The author is grateful to all of the participants in the IEEE 802.3ah EFM (Ethernet in the First Mile) taskforce. In particular, the strong leadership and dedication of the following individuals is noted:
作者感谢IEEE 802.3ah EFM（第一英里中的以太网）工作组的所有参与者。特别值得注意的是，以下个人的坚强领导和献身精神：
Kevin Daines (Editor, IEEE 802.3ah OAM clauses) Ben Brown (Editor, IEEE 802.3ah Logic clauses) David Law (Editor, IEEE 802.3ah Management clauses) Scott Simon (Editor, IEEE 802.3ah Clause 45) Howard Frazier (Chair, IEEE 802.3ah) Hugh Barass (Vice-Chair, IEEE 802.3ah) Wael Diab (Editor, IEEE 802.3ah)
Kevin Daines（IEEE 802.3ah OAM条款编辑）Ben Brown（IEEE 802.3ah逻辑条款编辑）David Law（IEEE 802.3ah管理条款编辑）Scott Simon（IEEE 802.3ah第45条编辑）Howard Frazier（IEEE 802.3ah主席）Hugh Barass（IEEE 802.3ah副主席）Wael Diab（IEEE 802.3ah编辑）
Additionally, certain devoted attendees and contributors to the IEEE 802.3ah OAM sub-taskforce deserve recognition. Although there were many contributors, the following individuals contributed heavily over a long period of time.
此外，IEEE 802.3ah OAM子任务组的某些热心与会者和贡献者值得认可。虽然有许多贡献者，但以下个人在很长一段时间内做出了重大贡献。
Brian Arnold Brad Booth Al Braga Floyd Gerhardt Bob Grow Eric Lynskey David Martin John Messenger Dan Romascanu (Ex-Chair, IETF HUBMIB WG) Jonathan Thatcher Geoff Thompson
Brian Arnold Brad Booth Al Braga Floyd Gerhardt Bob Grow Eric Lynskey David Martin John Messenger Dan Romascanu（IETF HUBMIB WG前主席）Jonathan Thatcher Geoff Thompson
Author's Address
作者地址
Matt Squire Hatteras Networks 529 Davis Drive Durham, NC 27713 EMail: msquire@hatterasnetworks.com
Matt Squire Hatteras Networks 529 Davis Drive Durham，NC 27713电子邮件：msquire@hatterasnetworks.com
Full Copyright Statement
完整版权声明
Copyright (C) The IETF Trust (2007).
版权所有（C）IETF信托基金（2007年）。
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM 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.
本文件及其包含的信息以“原样”为基础提供，贡献者、他/她所代表或赞助的组织（如有）、互联网协会、IETF信托基金和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Intellectual Property
知识产权
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights 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; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息，请参见BCP 78和BCP 79。
Copies of IPR disclosures made to the IETF Secretariat 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 implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。