Network Working Group E. Beili
Request for Comments: 5066 Actelis Networks
Category: Standards Track November 2007
Network Working Group E. Beili
Request for Comments: 5066 Actelis Networks
Category: Standards Track November 2007
Ethernet in the First Mile Copper (EFMCu) Interfaces MIB
第一英里铜缆（EFMCu）接口MIB中的以太网
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）。本备忘录的分发不受限制。
Abstract
摘要
This document defines Management Information Base (MIB) modules for use with network management protocols in TCP/IP-based internets. This document describes extensions to the Ethernet-like Interfaces MIB and Medium Attachment Unit (MAU) MIB modules with a set of objects for managing Ethernet in the First Mile Copper (EFMCu) interfaces 10PASS-TS and 2BASE-TL, defined in IEEE Std 802.3ah-2004 (note: IEEE Std 802.3ah-2004 has been integrated into IEEE Std 802.3- 2005). In addition, a set of objects is defined, describing cross-connect capability of a managed device with multi-layer (stacked) interfaces, extending the stack management objects in the Interfaces Group MIB and the Inverted Stack Table MIB modules.
本文档定义了管理信息库（MIB）模块，用于基于TCP/IP的Internet中的网络管理协议。本文档描述了对以太网类接口MIB和媒体连接单元（MAU）MIB模块的扩展，这些模块具有一组对象，用于管理第一英里铜缆（EFMCu）接口10PASS-TS和2BASE-TL中的以太网，这些接口在IEEE Std 802.3ah-2004中定义（注：IEEE Std 802.3ah-2004已集成到IEEE Std 802.3-2005中）。此外，定义了一组对象，描述了具有多层（堆叠）接口的受管设备的交叉连接能力，扩展了接口组MIB和反向堆栈表MIB模块中的堆栈管理对象。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . . 3
3. Relation to Other MIB Modules . . . . . . . . . . . . . . . . 4
3.1. Relation to Interfaces Group MIB Module . . . . . . . . . 4
3.1.1. Layering Model . . . . . . . . . . . . . . . . . . . . 4
3.1.2. PME Aggregation Function (PAF) . . . . . . . . . . . . 7
3.1.3. Discovery Operation . . . . . . . . . . . . . . . . . 7
3.1.4. EFMCu Ports Initialization . . . . . . . . . . . . . . 9
3.1.5. Usage of ifTable . . . . . . . . . . . . . . . . . . . 10
3.2. Relation to SHDSL MIB Module . . . . . . . . . . . . . . . 11
3.3. Relation to VDSL MIB Module . . . . . . . . . . . . . . . 12
3.4. Relation to Ethernet-Like and MAU MIB Modules . . . . . . 12
4. MIB Structure . . . . . . . . . . . . . . . . . . . . . . . . 13
4.1. EFM Copper MIB Overview . . . . . . . . . . . . . . . . . 13
4.2. Interface Stack Capability MIB Overview . . . . . . . . . 13
4.3. PME Profiles . . . . . . . . . . . . . . . . . . . . . . . 14
4.4. Mapping of IEEE 802.3ah Managed Objects . . . . . . . . . 14
5. Interface Stack Capability MIB Definitions . . . . . . . . . . 16
6. EFM Copper MIB Definitions . . . . . . . . . . . . . . . . . . 22
7. Security Considerations . . . . . . . . . . . . . . . . . . . 84
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 86
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 86
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 86
10.1. Normative References . . . . . . . . . . . . . . . . . . . 86
10.2. Informative References . . . . . . . . . . . . . . . . . . 88
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . . 3
3. Relation to Other MIB Modules . . . . . . . . . . . . . . . . 4
3.1. Relation to Interfaces Group MIB Module . . . . . . . . . 4
3.1.1. Layering Model . . . . . . . . . . . . . . . . . . . . 4
3.1.2. PME Aggregation Function (PAF) . . . . . . . . . . . . 7
3.1.3. Discovery Operation . . . . . . . . . . . . . . . . . 7
3.1.4. EFMCu Ports Initialization . . . . . . . . . . . . . . 9
3.1.5. Usage of ifTable . . . . . . . . . . . . . . . . . . . 10
3.2. Relation to SHDSL MIB Module . . . . . . . . . . . . . . . 11
3.3. Relation to VDSL MIB Module . . . . . . . . . . . . . . . 12
3.4. Relation to Ethernet-Like and MAU MIB Modules . . . . . . 12
4. MIB Structure . . . . . . . . . . . . . . . . . . . . . . . . 13
4.1. EFM Copper MIB Overview . . . . . . . . . . . . . . . . . 13
4.2. Interface Stack Capability MIB Overview . . . . . . . . . 13
4.3. PME Profiles . . . . . . . . . . . . . . . . . . . . . . . 14
4.4. Mapping of IEEE 802.3ah Managed Objects . . . . . . . . . 14
5. Interface Stack Capability MIB Definitions . . . . . . . . . . 16
6. EFM Copper MIB Definitions . . . . . . . . . . . . . . . . . . 22
7. Security Considerations . . . . . . . . . . . . . . . . . . . 84
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 86
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 86
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 86
10.1. Normative References . . . . . . . . . . . . . . . . . . . 86
10.2. Informative References . . . . . . . . . . . . . . . . . . 88
New Ethernet-like interfaces have been defined in the Institute of Electrical and Electronics Engineers (IEEE) Standard 802.3ah-2004 [802.3ah], a.k.a. Ethernet in the First Mile (EFM), which is now a part of the base IEEE Standard 802.3-2005 [802.3]. In particular, 2BASE-TL and 10PASS-TS physical interfaces (PHYs), defined over voice-grade copper pairs, have been specified for the long and short reach, respectively. These interfaces, collectively called EFM Copper (EFMCu), are based on Single-pair High-speed Digital Subscriber Line (SHDSL) [G.991.2] and Very High speed Digital Subscriber Line (VDSL) [G.993.1] technology, supporting optional Physical Medium Entity (PME) aggregation (a.k.a. multi-pair bonding) with variable rates.
电气和电子工程师协会（IEEE）标准802.3ah-2004[802.3ah]定义了新的类以太网接口，即第一英里以太网（EFM），它现在是基本IEEE标准802.3-2005[802.3]的一部分。特别是，在语音级铜对上定义的2BASE-TL和10PASS-TS物理接口（PHY）已分别指定用于长距离和短距离。这些接口统称为EFM铜缆（EFMCu），基于单对高速数字用户线（SHDSL）[G.991.2]和超高速数字用户线（VDSL）[G.993.1]技术，支持可变速率的可选物理介质实体（PME）聚合（也称为多对键合）。
2BASE-TL PHY is capable of providing at least 2 Mbps over a 2700 m long single copper pair with a mean Bit Error Rate (BER) of 10^-7 (using 5 dB target noise margin).
2BASE-TL PHY能够在2700米长的单铜对上提供至少2 Mbps的平均误比特率（BER）为10^-7（使用5 dB目标噪声容限）。
10PASS-TS PHY is capable of providing at least 10 Mbps over a 750 m long single copper pair with a mean BER of 10^-7 (using 6 dB target noise margin).
10PASS-TS PHY能够在平均误码率为10^-7（使用6 dB目标噪声容限）的750 m长的单铜对上提供至少10 Mbps。
This memo defines a Management Information Base (MIB) module for use with network management protocols in the Internet community to manage EFMCu interfaces. In addition, a MIB module is defined describing the cross-connect capability of a stacked interface.
本备忘录定义了一个管理信息库（MIB）模块，该模块与Internet社区中的网络管理协议一起使用，以管理EFMCu接口。此外，定义了描述堆叠接口交叉连接能力的MIB模块。
Note that managed objects for Operation, Administration and Maintenance (OAM) and Ethernet over Passive Optical Networks (EPON) clauses of IEEE 802.3ah are defined in EFM-COMMON-MIB [RFC4878] and EFM-EPON-MIB [RFC4837], respectively.
请注意，IEEE 802.3ah的操作、管理和维护（OAM）和无源光网络以太网（EPON）条款中的托管对象分别在EFM-COMMON-MIB[RFC4878]和EFM-EPON-MIB[RFC4837]中定义。
For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410 [RFC3410].
有关描述当前互联网标准管理框架的文件的详细概述，请参阅RFC 3410[RFC3410]第7节。
Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This memo specifies MIB modules that are compliant to the SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580].
托管对象通过虚拟信息存储（称为管理信息库或MIB）进行访问。MIB对象通常通过简单网络管理协议（SNMP）进行访问。MIB中的对象是使用管理信息结构（SMI）中定义的机制定义的。本备忘录规定了符合SMIv2的MIB模块，如STD 58、RFC 2578[RFC2578]、STD 58、RFC 2579[RFC2579]和STD 58、RFC 2580[RFC2580]所述。
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]中所述进行解释。
This section outlines the relationship of the MIB modules defined in this document with other MIB modules described in the relevant RFCs. Specifically, the Interfaces Group MIB (IF-MIB), Ethernet-Like (EtherLike-MIB), MAU (MAU-MIB), SHDSL (HDSL2-SHDSL-LINE-MIB), and VDSL (VDSL-LINE-EXT-MCM-MIB) modules are discussed.
本节概述了本文档中定义的MIB模块与相关RFC中描述的其他MIB模块之间的关系。具体而言，讨论了接口组MIB（IF-MIB）、类以太网MIB（类以太网MIB）、MAU（MAU-MIB）、SHDSL（HDSL2-SHDSL-LINE-MIB）和VDSL（VDSL-LINE-EXT-MCM-MIB）模块。
2BASE-TL and 10PASS-TS PHYs specified in the EFM-CU-MIB module are stacked (a.k.a. aggregated or bonded) Ethernet interfaces and as such are managed using generic interface management objects defined in the IF-MIB [RFC2863].
EFM-CU-MIB模块中指定的2 BASE-TL和10 PASS-TS PHY堆叠（也称为聚合或绑定）以太网接口，因此使用IF-MIB[RFC2863]中定义的通用接口管理对象进行管理。
The stack management (i.e., actual connection of the sub-layers to the top-layer interface) is done via the ifStackTable, as defined in the IF-MIB [RFC2863], and its inverse ifInvStackTable, as defined in the IF-INVERTED-STACK-MIB [RFC2864].
堆栈管理（即子层与顶层接口的实际连接）通过IF-MIB[RFC2863]中定义的ifStackTable和IF-Inversed-stack-MIB[RFC2864]中定义的逆ifInvStackTable完成。
The new tables ifCapStackTable and its inverse ifInvCapStackTable defined in the IF-CAP-STACK-MIB module below, extend the stack management with an ability to describe possible connections or cross-connect capability, when a flexible cross-connect matrix is present between the interface layers.
下面的IF-CAP-STACK-MIB模块中定义的新表ifCapStackTable及其逆ifInvCapStackTable扩展了堆栈管理，当接口层之间存在灵活的交叉连接矩阵时，可以描述可能的连接或交叉连接能力。
An EFMCu interface can aggregate up to 32 Physical Medium Entity (PME) sub-layer devices (modems), using the so-called PME Aggregation Function (PAF).
EFMCu接口可以使用所谓的PME聚合功能（PAF）聚合多达32个物理介质实体（PME）子层设备（调制解调器）。
A generic EFMCu device can have a number of Physical Coding Sublayer (PCS) ports, each connected to a Media Access Controller (MAC) via a Medium Independent Interface (MII) at the upper layer, and cross-connected to a number of underlying PMEs, with a single PCS per PME relationship. See clause 61.1 of [802.3ah] for more details.
通用EFMCu设备可以具有多个物理编码子层（PCS）端口，每个端口通过上层的媒体独立接口（MII）连接到媒体访问控制器（MAC），并交叉连接到多个底层PME，每个PME具有一个PCS关系。详见[802.3ah]第61.1条。
Each PME in the aggregated EFMCu port is represented in the Interface table (ifTable) as a separate interface with ifType of shdsl(169) for 2BASE-TL or vdsl(97) for 10PASS-TS. The ifType values are defined in [IANAifType-MIB].
聚合EFMCu端口中的每个PME在接口表（ifTable）中表示为单独的接口，2BASE-TL的ifType为shdsl（169），10PASS-TS的ifType为vdsl（97）。ifType值在[IANAifType MIB]中定义。
ifSpeed for each PME SHALL return the actual data bitrate of the active PME (e.g., for 2BaseTL PMEs it is a multiple of 64 Kbps). A zero value SHALL be returned when the PME is Initializing or Down.
每个PME的ifSpeed应返回活动PME的实际数据比特率（例如，对于2BaseTL PME，它是64 Kbps的倍数）。当PME初始化或关闭时，应返回零值。
The ifSpeed of the PCS is the sum of the current operating data rates of all PMEs in the aggregation group, without the 64/65-octet encapsulation overhead and PAF overhead, but accounting for the Inter-Frame Gaps (IFGs).
PCS的ifSpeed是聚合组中所有PME的当前运行数据速率之和，不考虑64/65八位字节封装开销和PAF开销，但考虑帧间间隙（IFG）。
When using the stated definition of ifSpeed for the PCS, there would be no frame loss in the following configuration (the test-sets are configured to generate 100% of back-to-back traffic, i.e., minimal IFG, at 10 or 100 Mbps, with min and max frame sizes; the EFM interfaces are aggregated, to achieve the shown speed):
当对PCS使用规定的ifSpeed定义时，在以下配置中不会出现帧丢失（测试集配置为以10或100 Mbps的速度生成100%的背对背通信量，即最小IFG，最小和最大帧大小；EFM接口聚合，以达到所示速度）：
.-------. .--. .---. .-------.
|testset|--10BaseT--|CO|--2BaseTL--|CPE|--10BaseT--|testset|
'-------' '--' '---' '-------'
ifSpeed= 10 Mbps 10 Mbps 10 Mbps
.-------. .--. .---. .-------.
|testset|--10BaseT--|CO|--2BaseTL--|CPE|--10BaseT--|testset|
'-------' '--' '---' '-------'
ifSpeed= 10 Mbps 10 Mbps 10 Mbps
.-------. .--. .---. .-------.
|testset|--100BaseT--|CO|--10PassTS--|CPE|--100BaseT--|testset|
'-------' '--' '---' '-------'
ifSpeed= 100 Mbps 100 Mbps 100 Mbps
.-------. .--. .---. .-------.
|testset|--100BaseT--|CO|--10PassTS--|CPE|--100BaseT--|testset|
'-------' '--' '---' '-------'
ifSpeed= 100 Mbps 100 Mbps 100 Mbps
Figure 1: Example configuration with no frame loss
图1：无帧丢失的示例配置
The following figure shows the IEEE 802.3 layering diagram and corresponding use of ifTable and ifMauTable:
下图显示了IEEE 802.3分层图以及ifTable和ifMauTable的相应用法：
.-------------------------. -
| LLC | ^
+-------------------------+ | 1 ifEntry
| MAC | | ifType: ethernetCsmacd(6)
+-------------------------+ ) ifMauEntry
| Reconsiliation | | ifMauType: dot3MauType2BaseTL or
+-------------------------+ | dot3MauType10PassTS
| PCS | v
+-------------+---+-------+ -
| TC \ | | | ^
+-----\ | | | |
| PMA )PME 1 |...| PME N | ) N ifEntry (N=1..32)
+-----/ | | | | ifType: shdsl(169) or vdsl(97)
| PMD/ | | | v
'-------------+---+-------' -
.-------------------------. -
| LLC | ^
+-------------------------+ | 1 ifEntry
| MAC | | ifType: ethernetCsmacd(6)
+-------------------------+ ) ifMauEntry
| Reconsiliation | | ifMauType: dot3MauType2BaseTL or
+-------------------------+ | dot3MauType10PassTS
| PCS | v
+-------------+---+-------+ -
| TC \ | | | ^
+-----\ | | | |
| PMA )PME 1 |...| PME N | ) N ifEntry (N=1..32)
+-----/ | | | | ifType: shdsl(169) or vdsl(97)
| PMD/ | | | v
'-------------+---+-------' -
LLC - Logical Link Control PMA - Physical Medium Attachment
MAC - Media Access Control PMD - Physical Medium Dependent
PCS - Physical Coding Sub-layer PME - Physical Medium Entity
TC - Transmission Convergence
LLC - Logical Link Control PMA - Physical Medium Attachment
MAC - Media Access Control PMD - Physical Medium Dependent
PCS - Physical Coding Sub-layer PME - Physical Medium Entity
TC - Transmission Convergence
Figure 2: Use of ifTable and ifMauTable for EFMCu ports
图2:EFMCu端口的ifTable和ifMauTable的使用
The ifStackTable is indexed by the ifIndex values of the aggregated EFMCu port (PCS) and the PMEs connected to it. ifStackTable allows a Network Management application to determine which PMEs are connected to a particular PCS and change connections (if supported by the application). The ifInvStackTable, being an inverted version of the ifStackTable, provides an efficient means for a Network Management application to read a subset of the ifStackTable and thereby determine which PCS runs on top of a particular PME.
ifStackTable由聚合的EFMCu端口（PCS）及其连接的PME的ifIndex值索引。ifStackTable允许网络管理应用程序确定哪些PME连接到特定PC并更改连接（如果应用程序支持）。ifInvStackTable是ifStackTable的反向版本，它为网络管理应用程序提供了一种有效的方法来读取ifStackTable的子集，从而确定哪些PC在特定PME上运行。
A new table ifCapStackTable, defined in the IF-CAP-STACK-MIB module, specifies for each higher-layer interface (e.g., PCS port) a list of lower-layer interfaces (e.g., PMEs), which can possibly be cross-connected to that higher-layer interface, determined by the cross-connect capability of the device. This table, modeled after ifStackTable, is read-only, reflecting current cross-connect capability of stacked interface, which can be dynamic in some implementations (e.g., if PMEs are located on a pluggable module and the module is pulled out). Note that PME availability per PCS, described by ifCapStackTable, can be constrained by other parameters, for example, by aggregation capacity of a PCS or by the PME in question being already connected to another PCS. So, in order to
IF-CAP-STACK-MIB模块中定义的新表ifCapStackTable为每个高层接口（例如，PCS端口）指定一个下层接口（例如，PME）列表，这些接口可能交叉连接到该高层接口，由设备的交叉连接能力确定。该表以ifStackTable为模型，是只读的，反映了堆叠接口的当前交叉连接能力，在某些实现中可能是动态的（例如，如果PME位于可插拔模块上，并且模块被拔出）。请注意，ifCapStackTable所描述的每台PC的PME可用性可能受到其他参数的约束，例如，PC的聚合容量或已连接到另一台PC的相关PME。因此
ensure that a particular PME can be connected to the PCS, all respective parameters (e.g., ifCapStackTable, ifStackTable, and efmCuPAFCapacity) SHALL be inspected.
确保特定PME可连接至PCS，应检查所有相关参数（如ifCapStackTable、ifStackTable和efmCuPAFCapacity）。
The ifInvCapStackTable, also defined in the IF-CAP-STACK-MIB module, describes which higher-layer interfaces (e.g., PCS ports) can possibly be connected to a particular lower-layer interface (e.g., PME), providing an inverted mapping of the ifCapStackTable. While it contains no additional information beyond that already contained in the ifCapStackTable, the ifInvCapStackTable has the ifIndex values in its INDEX clause in the reverse order, i.e., the lower-layer interface first, and the higher-layer interface second, providing an efficient means for a Network Management application to read a subset of the ifCapStackTable and thereby determine which interfaces can be connected to run on top of a particular interface.
ifInvCapStackTable（也在IF-CAP-STACK-MIB模块中定义）描述了哪些高层接口（例如，PCS端口）可能连接到特定的底层接口（例如，PME），提供了ifCapStackTable的反向映射。虽然它不包含ifCapStackTable中已经包含的信息以外的其他信息，但ifInvCapStackTable在其索引子句中的ifIndex值顺序相反，即先是较低层接口，然后是较高层接口，为网络管理应用程序提供一种有效的方法，以读取ifCapStackTable的子集，从而确定哪些接口可以连接到特定接口上运行。
The PME Aggregation Function (PAF) allows a number of PMEs to be aggregated onto a PCS port, by fragmenting the Ethernet frames, transmitting the fragments over multiple PMEs, and assembling the original frames at the remote port. PAF is OPTIONAL, meaning that a device with a single PME MAY perform fragmentation and re-assembly if this function is supported by the device. Note however that the agent is REQUIRED to report on the PAF capability for all EFMCu ports (2BASE-TL and 10PASS-TS).
PME聚合功能（PAF）允许将多个PME聚合到一个PCS端口上，方法是对以太网帧进行分段，通过多个PME传输片段，并在远程端口组装原始帧。PAF是可选的，这意味着如果设备支持此功能，则具有单个PME的设备可以执行碎片和重新组装。但是请注意，代理需要报告所有EFMCu端口（2BASE-TL和10PASS-TS）的PAF能力。
The EFM-CU-MIB module allows a Network Management application to query the PAF capability and enable/disable it if supported. Note that enabling PAF effectively turns on fragmentation and re-assembly, even on a single-PME port.
EFM-CU-MIB模块允许网络管理应用程序查询PAF能力，并在支持的情况下启用/禁用PAF能力。请注意，启用PAF可以有效地打开碎片和重新组装，即使在单个PME端口上也是如此。
The EFMCu ports may optionally support discovery operation, whereby PMEs, during initialization, exchange information about their respective aggregation groups (PCS). This information can then be used to detect copper misconnections or for an automatic assignment of the local PMEs into aggregation groups instead of a fixed pre-configuration.
EFMCu端口可选择性地支持发现操作，由此，PME在初始化期间交换关于其各自聚合组（PC）的信息。然后，该信息可用于检测铜缆错误连接，或用于将本地PME自动分配到聚合组，而不是固定的预配置。
The MIB modules defined in this document allow a Network Management application to control the EFM Discovery mechanism and query its results. Note that the Discovery mechanism can work only if PAF is supported and enabled.
本文档中定义的MIB模块允许网络管理应用程序控制EFM发现机制并查询其结果。请注意，只有在支持并启用PAF的情况下，发现机制才能工作。
Two tables are used by the EFM Discovery mechanism: ifStackTable and ifCapStackTable. The following pseudo-code gives an example of the Discovery and automatic PME assignment for a generic PAF-enabled multi-PCS EFMCu device, located at Central Office (CO), using objects defined in these MIB modules and in the IF-MIB (Note that automatic PME assignment is only shown here for the purposes of the example. Fixed PME pre-assignment, manual assignment, or auto-assignment using an alternative internal algorithm may be chosen by a particular implementation):
EFM发现机制使用两个表：ifStackTable和ifCapStackTable。以下伪代码给出了使用这些MIB模块和IF-MIB中定义的对象为位于中央办公室（CO）的支持PAF的通用多PC EFMCu设备发现和自动PME分配的示例（注意，此处显示的自动PME分配仅用于示例目的。固定PME预分配、手动分配或使用替代内部算法的自动分配可由特定实现选择）：
// Go over all PCS ports in the CO device
FOREACH pcs[i] IN CO_device
{ // Perform discovery and auto-assignment only on PAF enabled ports
// with room for more PMEs
IF ( pcs[i].PAFSupported AND pcs[i].NumPMEs < pcs[i].PAFCapacity )
{ // Assign a unique 6-octet local discovery code to the PCS
// e.g., MAC address
dc = pcs[i].DiscoveryCode = MAC[i];
// Go over all disconnected PMEs, which can
// potentially be connected to the PCS
FOREACH pme[j] IN ifCapStackTable[pcs[i]] AND
NOT IN ifStackTable[pcs[i]] // not connected
{ // Try to grab the remote RT_device, by writing the value
// of the local 6-octet discovery code to the remote
// discovery code register (via handshake mechanism).
// This operation is atomic Set-if-Clear action, i.e., it
// would succeed only if the remote discovery register was
// zero. Read the remote discovery code register via Get
// operation to see if the RT_device, attached via the PME
// is indeed marked as being the CO_device peer.
pme[j].RemoteDiscoveryCode = dc; // Set-if-Clear
r = pme[j].RemoteDiscoveryCode; // Get
IF ( r == dc AND pcs[i].NumPMEs < pcs[i].PAFCapacity)
{ // Remote RT_device connected via PME[j] is/was a peer
// for PCS[i] and there is room for another PME in the
// PCS[i] aggregation group (max. PAF capacity is not
// reached yet).
// Connect this PME to the PCS (via ifStackTable,
// ifInvStackTable being inverse of ifStackTable is
// updated automatically, i.e., pcs[i] is auto-added
// to ifInvStackTable[pme[j]])
ADD pme[j] TO ifStackTable[pcs[i]];
pcs[i].NumPMEs = pcs[i].NumPMEs + 1;
// Discover all other disconnected PMEs,
// attached to the same RT_device and connect them to
// the PCS provided there is enough room for more PMEs.
FOREACH pme[k] IN ifCapStackTable[pcs[i]] AND
NOT IN ifStackTable[pcs[i]]
// Go over all PCS ports in the CO device
FOREACH pcs[i] IN CO_device
{ // Perform discovery and auto-assignment only on PAF enabled ports
// with room for more PMEs
IF ( pcs[i].PAFSupported AND pcs[i].NumPMEs < pcs[i].PAFCapacity )
{ // Assign a unique 6-octet local discovery code to the PCS
// e.g., MAC address
dc = pcs[i].DiscoveryCode = MAC[i];
// Go over all disconnected PMEs, which can
// potentially be connected to the PCS
FOREACH pme[j] IN ifCapStackTable[pcs[i]] AND
NOT IN ifStackTable[pcs[i]] // not connected
{ // Try to grab the remote RT_device, by writing the value
// of the local 6-octet discovery code to the remote
// discovery code register (via handshake mechanism).
// This operation is atomic Set-if-Clear action, i.e., it
// would succeed only if the remote discovery register was
// zero. Read the remote discovery code register via Get
// operation to see if the RT_device, attached via the PME
// is indeed marked as being the CO_device peer.
pme[j].RemoteDiscoveryCode = dc; // Set-if-Clear
r = pme[j].RemoteDiscoveryCode; // Get
IF ( r == dc AND pcs[i].NumPMEs < pcs[i].PAFCapacity)
{ // Remote RT_device connected via PME[j] is/was a peer
// for PCS[i] and there is room for another PME in the
// PCS[i] aggregation group (max. PAF capacity is not
// reached yet).
// Connect this PME to the PCS (via ifStackTable,
// ifInvStackTable being inverse of ifStackTable is
// updated automatically, i.e., pcs[i] is auto-added
// to ifInvStackTable[pme[j]])
ADD pme[j] TO ifStackTable[pcs[i]];
pcs[i].NumPMEs = pcs[i].NumPMEs + 1;
// Discover all other disconnected PMEs,
// attached to the same RT_device and connect them to
// the PCS provided there is enough room for more PMEs.
FOREACH pme[k] IN ifCapStackTable[pcs[i]] AND
NOT IN ifStackTable[pcs[i]]
{ // Get Remote Discovery Code from the PME to see if
// it belongs to a connected RT_device "grabbed" by
// the CO_device.
r = pme[k].RemoteDiscoveryCode;
IF ( r == dc AND pcs[i].NumPMEs < pcs[i].PAFCapacity)
{ // Physically connect the PME to the PCS
// (pcs[i] is auto-added TO ifInvStackTable[pme[k]])
ADD pme[k] TO ifStackTable[pcs[i]];
pcs[i].NumPMEs = pcs[i].NumPMEs + 1;
}
}
}
// At this point we have discovered all local PMEs which
// are physically connected to the same remote RT_device
// and connected them to PCS[i]. Go to the next PCS.
BREAK;
}
}
}
{ // Get Remote Discovery Code from the PME to see if
// it belongs to a connected RT_device "grabbed" by
// the CO_device.
r = pme[k].RemoteDiscoveryCode;
IF ( r == dc AND pcs[i].NumPMEs < pcs[i].PAFCapacity)
{ // Physically connect the PME to the PCS
// (pcs[i] is auto-added TO ifInvStackTable[pme[k]])
ADD pme[k] TO ifStackTable[pcs[i]];
pcs[i].NumPMEs = pcs[i].NumPMEs + 1;
}
}
}
// At this point we have discovered all local PMEs which
// are physically connected to the same remote RT_device
// and connected them to PCS[i]. Go to the next PCS.
BREAK;
}
}
}
An SNMP Agent for an EFMCu device builds the ifCapStackTable and its inverse ifInvCapStackTable according to the information contained in the Clause 45 PME_Available_register (see [802.3ah] 61.1.5.3 and 45.2.3.20).
EFMCu设备的SNMP代理根据第45条PME_Available_寄存器中包含的信息（参见[802.3ah]61.1.5.3和45.2.3.20）构建ifCapStackTable及其逆IFNVCAPStackTable。
Adding a PME to the ifStackTable row for a specific PCS involves actual connection of the PME to the PCS, which can be done by modifying Clause 45 PME_Aggregate_register (see [802.3ah] 61.1.5.3 and 45.2.3.21).
将PME添加到特定PCS的ifStackTable行涉及PME与PCS的实际连接，这可以通过修改第45条PME_Aggregate_寄存器来实现（请参见[802.3ah]61.1.5.3和45.2.3.21）。
Note that the PCS port does not have to be operationally 'down' for the connection to succeed. In fact, a dynamic PME addition (and removal) MAY be implemented with an available PME being initialized first (by setting its ifAdminStatus to 'up') and then added to an operationally 'up' PCS port, by modifying a respective ifStackTable (and respective ifInvStackTable) entry.
请注意，PCS端口不必在操作上“关闭”，连接才能成功。事实上，动态PME添加（和删除）可以通过以下方式实现：首先初始化可用PME（通过将其ifAdminStatus设置为“up”），然后通过修改相应的ifStackTable（和相应的ifInvStackTable）条目将其添加到操作上的“up”PCS端口。
It is RECOMMENDED that a removal of the last operationally 'up' PME from an operationally 'up' PCS would be rejected by the implementation, as this action would completely drop the link.
建议实施部门拒绝将最后一个运行“正常”的PME从运行“正常”的PCS中移除，因为此操作将完全中断链接。
EFMCu ports being built on top of xDSL technology require a lengthy initialization or 'training' process, before any data can pass. During this initialization, both ends of a link (peers) work cooperatively to achieve the required data rate on a particular
建立在xDSL技术之上的EFMCu端口需要一个漫长的初始化或“训练”过程，然后才能传递任何数据。在此初始化过程中，链路的两端（对等方）协同工作，以在特定网络上实现所需的数据速率
copper pair. Sometimes, when the copper line is too long or the noise on the line is too high, that 'training' process may fail to achieve a specific target rate with required characteristics.
铜对。有时，当铜线过长或线路上的噪声过高时，“培训”过程可能无法达到具有所需特性的特定目标速率。
The ifAdminStatus object from the IF-MIB controls the desired state of a PCS with all the PMEs connected to it or of an individual PME port. Setting this object to 'up' instructs a particular PCS or PME to start the initialization process, which may take tens of seconds for EFMCu ports, especially if PAF is involved. The ifOperStatus object shows the operational state of an interface (extended by the ifMauMediaAvailable object from MAU-MIB for PCS and efmCuPmeOperStatus defined in the EFM-CU-MIB module for PME interfaces).
IF-MIB中的ifAdminStatus对象控制连接有所有PME的PC或单个PME端口的所需状态。将此对象设置为“up”将指示特定的PC或PME启动初始化过程，EFMCu端口可能需要数十秒的时间，尤其是在涉及PAF的情况下。IfOperaStatus对象显示接口的操作状态（由PC的MAU-MIB中的ifMauMediaAvailable对象和PME接口的EFM-CU-MIB模块中定义的EFMCupMeOperaStatus扩展）。
A disconnected PME may be initialized by changing the ifAdminState from 'down' to 'up'. Changing the ifAdminState to 'up' on the PCS initializes all PMEs connected to that particular PCS. Note that in case of PAF some interfaces may fail to initialize while others succeed. The PCS is considered operationally 'up' if at least one PME aggregated by its PAF is operationally 'up'. When all PMEs connected to the PCS are 'down', the PCS SHALL be considered operationally 'lowerLayerDown'. The PCS SHALL be considered operationally 'notPresent' if it is not connected to any PME. The PCS/PME interface SHALL remain operationally 'down' during initialization.
断开的PME可以通过将IFAdminInstate从“向下”更改为“向上”来初始化。将PCS上的ifAdminState更改为“up”将初始化连接到该特定PCS的所有PME。请注意，在PAF情况下，某些接口可能无法初始化，而其他接口则成功初始化。如果至少有一个由其PAF聚合的PME在操作上“向上”，则PCS在操作上被视为“向上”。当连接至PCS的所有PME“停机”时，PCS应被视为运行“较低层停机”。如果PCS未连接到任何PME，则应认为其在操作上“不存在”。初始化期间，PCS/PME接口应保持操作“关闭”。
The efmCuPmeOperStatus defined in the EFM-CU-MIB module expands PME's ifOperStatus value of 'down' to 'downReady', 'downNotReady', and 'init' values, indicating various EFMCu PME-specific states.
EFM-CU-MIB模块中定义的efmCuPmeOperStatus将PME的ifOperStatus值“down”扩展为“downReady”、“downNotReady”和“init”值，表示EFMCu PME的各种特定状态。
Both PME and PCS interfaces of the EFMCu PHY are managed using interface-specific management objects defined in the EFM-CU-MIB module and generic interface objects from the ifTable of IF-MIB, with all management table entries referenced by the interface index ifIndex.
EFMCu PHY的PME和PCS接口均使用EFM-CU-MIB模块中定义的接口特定管理对象和IF-MIB ifTable中的通用接口对象进行管理，接口索引ifIndex引用了所有管理表项。
The following table summarizes EFMCu-specific interpretations for some of the ifTable objects specified in the mandatory ifGeneralInformationGroup:
下表总结了强制IFGeneralInformation组中指定的某些ifTable对象的EFMCu特定解释：
+---------------+---------------------------------------------------+
| IF-MIB object | EFMCu interpretation |
+---------------+---------------------------------------------------+
| ifIndex | Interface index. Note that each PME and each PCS |
| | in the EFMCu PHY MUST have a unique index, as |
| | there are some PCS- and PME-specific attributes |
| | accessible only on the PCS or PME level. |
+---------------+---------------------------------------------------+
| ifType | ethernetCsmacd(6) for PCS, shdsl(169) for |
| | 2BASE-TL PME, vdsl(97) for 10PASS-TS PME. |
| ifSpeed | Operating data rate for the PME. For the PCS, it |
| | is the sum of the current operating data rates of |
| | all PMEs in the aggregation group, without the |
| | 64/65-octet encapsulation overhead and PAF |
| | overhead, but accounting for the Inter-Frame Gaps |
| | (IFGs). |
+---------------+---------------------------------------------------+
| ifAdminStatus | Setting this object to 'up' instructs a |
| | particular PCS (with all PMEs connected to it) or |
| | PME to start initialization process. |
+---------------+---------------------------------------------------+
| ifOperStatus | efmCuPmeOperStatus supplements the 'down' value |
| | of ifOperStatus for PMEs. |
+---------------+---------------------------------------------------+
+---------------+---------------------------------------------------+
| IF-MIB object | EFMCu interpretation |
+---------------+---------------------------------------------------+
| ifIndex | Interface index. Note that each PME and each PCS |
| | in the EFMCu PHY MUST have a unique index, as |
| | there are some PCS- and PME-specific attributes |
| | accessible only on the PCS or PME level. |
+---------------+---------------------------------------------------+
| ifType | ethernetCsmacd(6) for PCS, shdsl(169) for |
| | 2BASE-TL PME, vdsl(97) for 10PASS-TS PME. |
| ifSpeed | Operating data rate for the PME. For the PCS, it |
| | is the sum of the current operating data rates of |
| | all PMEs in the aggregation group, without the |
| | 64/65-octet encapsulation overhead and PAF |
| | overhead, but accounting for the Inter-Frame Gaps |
| | (IFGs). |
+---------------+---------------------------------------------------+
| ifAdminStatus | Setting this object to 'up' instructs a |
| | particular PCS (with all PMEs connected to it) or |
| | PME to start initialization process. |
+---------------+---------------------------------------------------+
| ifOperStatus | efmCuPmeOperStatus supplements the 'down' value |
| | of ifOperStatus for PMEs. |
+---------------+---------------------------------------------------+
Table 1: EFMCu interpretation of IF-MIB objects
表1:IF-MIB对象的EFMCu解释
G.SHDSL.bis modems, similar to PMEs comprising a 2BASE-TL port, are described in the HDSL2-SHDSL-LINE-MIB module [RFC4319]. Note that not all attributes of G.SHDSL modems reflected in the HDSL2-SHDSL-LINE-MIB module have adequate management objects (Clause 30 attributes and Clause 45 registers) in the EFM standard.
HDSL2-SHDSL-LINE-MIB模块[RFC4319]中描述了类似于包含2BASE-TL端口的PME的G.SHDSL.bis调制解调器。请注意，并非HDSL2-SHDSL-LINE-MIB模块中反映的G.SHDSL调制解调器的所有属性在EFM标准中都具有足够的管理对象（第30条属性和第45条寄存器）。
Because of these differences and for the purposes of simplicity, unification of attributes common to both 2BASE-TL and 10PASS-TS PMEs, and name consistency (e.g., prefixing the 2BASE-TL PME related objects with 'efmCuPme2B' instead of 'hdsl2shdsl'), it was decided not to reference HDSL2-SHDSL-LINE-MIB objects, but define all the relevant objects in the EFM-CU-MIB module.
由于这些差异，并且为了简单、统一2BASE-TL和10PASS-TS PME共有的属性以及名称一致性（例如，在2BASE-TL PME相关对象前加上“efmCuPme2B”而不是“hdsl2shdsl”），决定不引用HDSL2-SHDSL-LINE-MIB对象，但在EFM-CU-MIB模块中定义所有相关对象。
However, if some functionality not available in the EFM-CU-MIB module is required and supported by the PME, e.g., performance monitoring, relevant HDSL2-SHDSL-LINE-MIB groups MAY be included and applied for PMEs of 2BASE-TL subtype.
但是，如果PME需要并支持EFM-CU-MIB模块中不可用的某些功能，例如性能监控，则可包括相关HDSL2-SHDSL-LINE-MIB组，并将其应用于2BASE-TL子类型的PME。
VDSL modems, similar to the PME(s) comprising a 10PASS-TS port, are described in the VDSL-LINE-EXT-MCM-MIB module [RFC4070]. Note that not all attributes of VDSL modems reflected in the VDSL-LINE-EXT-MCM-MIB module have adequate management objects (Clause 30 attributes and Clause 45 registers) in the EFM standard.
VDSL调制解调器类似于包含10PASS-TS端口的PME，在VDSL-LINE-EXT-MCM-MIB模块[RFC4070]中描述。请注意，并非VDSL-LINE-EXT-MCM-MIB模块中反映的所有VDSL调制解调器属性在EFM标准中都有足够的管理对象（第30条属性和第45条寄存器）。
Because of these differences and for the purposes of simplicity, unification of attributes common to both 2BASE-TL and 10PASS-TS PMEs, and name consistency, it was decided not to reference VDSL-LINE-EXT-MCM-MIB objects, but define all the relevant objects in the EFM-CU-MIB module.
由于这些差异，为了简单、统一2BASE-TL和10PASS-TS PME共有的属性以及名称一致性，决定不引用VDSL-LINE-EXT-MCM-MIB对象，而是定义EFM-CU-MIB模块中的所有相关对象。
However, if some functionality not available in the EFM-CU-MIB module is required and supported by the PME, relevant VDSL-LINE-EXT-MCM-MIB groups MAY be included and applied for PMEs of 10PASS-TS subtype.
但是，如果PME需要并支持EFM-CU-MIB模块中不可用的某些功能，则可包括相关VDSL-LINE-EXT-MCM-MIB组，并将其应用于10PASS-TS子类型的PME。
The implementation of the EtherLike-MIB [RFC3635] and MAU-MIB [RFC4836] modules is REQUIRED for EFMCu interfaces.
EFMCu接口需要实现以太式MIB[RFC3635]和MAU-MIB[RFC4836]模块。
Two new values of ifMauType (OBJECT-IDENTITIES of dot3MauType) and corresponding bit definitions of ifMauTypeListBits (IANAifMauTypeListBits) have been defined in the IANA-MAU-MIB module [RFC4836] for EFMCu MAUs:
EFMCu MAU的IANA-MAU-MIB模块[RFC4836]中定义了两个新的ifMauType值（dot3MauType的对象标识）和相应的ifMauTypeListBits位定义（IANAifMauTypeListBits）：
o dot3MauType2BaseTL and b2BaseTL - for 2BASE-TL MAU
o dot3MauType2BaseTL和b2BaseTL-用于2BASE-TL MAU
o dot3MauType10PassTS and b10PassTS - for 10PASS-TS MAU
o dot3MauType10PassTS and b10PassTS - for 10PASS-TS MAUtranslate error, please retry
Additionally, the IANA-MAU-MIB module defines two new values of ifMauMediaAvailable, specifically for EFMCu ports: availableReduced and ready (in textual convention IANAifMauMediaAvailable). Due to the PME aggregation, the EFMCu interpretation of some possible ifMauMediaAvailable values differs from other MAUs as follows:
此外，IANA-MAU-MIB模块定义了ifMauMediaAvailable的两个新值，专门用于EFMCu端口：availableReduced和ready（在文本约定IANAifMauMediaAvailable中）。由于PME聚合，EFMCu对某些可能的ifMauMediaAvailable值的解释与其他MAU不同，如下所示：
o unknown - the EFMCu interface (PCS with connected PMEs) is Initializing
o 未知-EFMCu接口（已连接PME的PC）正在初始化
o ready - the interface is Down, at least one PME in the aggregation group (all PMEs connected to the PCS) is ready for handshake
o 就绪-接口关闭，聚合组中至少有一个PME（所有连接到PC的PME）准备好握手
o available - the interface is Up, all PMEs in the aggregation group are up
o 可用-接口已启动，聚合组中的所有PME均已启动
o notAvailable - the interface is Down, all PMEs in the aggregation group are Down, no handshake tones are detected by any PME
o notAvailable-接口已关闭，聚合组中的所有PME均已关闭，任何PME均未检测到握手音
o availableReduced - the interface is Up, a link fault is detected at the receive direction by one or more PMEs in the aggregation group, but at least one PME is Up
o availableReduced-接口启动，聚合组中的一个或多个PME在接收方向检测到链路故障，但至少有一个PME启动
o pmdLinkFault - a link fault is detected at the receive direction by all PMEs in the aggregation group
o pmdLinkFault-聚合组中的所有PME在接收方向检测到链路故障
As an EtherLike interface, every EFMCu port (an ifEntry representing a consolidation of LLC, MAC, and PCS (sub)layers) SHALL return an ifType of ethernetCsmacd(6). While most of the MAU characteristics are not applicable to the EFMCu ports (no auto-negotiation, false carriers, or jabber), they SHALL return an appropriate ifMauType (dot3MauType2BaseTL or dot3mauType10PassTS) in order to direct the management software to look in the EFM-CU-MIB module for the desired information. For example, the information on the particular EFMCu flavor that an EFMCu port is running is available from efmCuOperSubType, defined in the EFM-CU-MIB module.
作为以太接口，每个EFMCu端口（表示LLC、MAC和PC（子）层合并的ifEntry）应返回ethernetCsmacd（6）的ifType。虽然大多数MAU特征不适用于EFMCu端口（无自动协商、假载波或jabber），但它们应返回适当的ifMauType（dot3MauType2BaseTL或DOT3MAUTYPE10PASTS），以便指导管理软件在EFM-CU-MIB模块中查找所需信息。例如，有关EFMCu端口正在运行的特定EFMCu风格的信息可从EFM-CU-MIB模块中定义的efmCuOperSubType获得。
Since EFMCu PMEs are not EtherLike interfaces, they cannot be instantiated as MAU interface objects.
由于EFMCu PME不是以太式接口，因此不能将其实例化为MAU接口对象。
The main management objects defined in the EFM-CU-MIB module are split into 2 groups:
EFM-CU-MIB模块中定义的主要管理对象分为两组：
o efmCuPort - containing objects for configuration, capabilities, status, and notifications, common to all EFMCu PHYs.
o efmCuPort-包含所有EFMCu物理所共有的配置、功能、状态和通知对象。
o efmCuPme - containing objects for configuration, capabilities, status, and notifications of EFMCu PMEs.
o efmCuPme-包含EFMCu PME的配置、功能、状态和通知的对象。
The efmCuPme group in turn contains efmCuPme2B and efmCuPme10P groups, which define PME profiles specific to 2BASE-TL and 10PASS-TS PMEs, respectively, as well as PME-specific status information.
efmCuPme组依次包含efmCuPme2B和efmCuPme10P组，它们分别定义了2BASE-TL和10PASS-TS PME的PME配置文件以及PME的特定状态信息。
The IF-CAP-STACK-MIB module contains 2 tables:
IF-CAP-STACK-MIB模块包含两个表：
o ifCapStackTable - containing objects that define possible relationships among the sub-layers of an interface with flexible cross-connect (cross-connect capability).
o ifCapStackTable-包含定义接口子层之间可能关系的对象，具有灵活的交叉连接（交叉连接功能）。
o ifInvCapStackTable - an inverse of the ifCapstackTable.
o ifInvCapStackTable-ifCapstackTable的逆项。
Since a managed node can have a large number of EFMCu PHYs, provisioning every parameter on every EFMCu PHY may become burdensome. Moreover, most PMEs are provisioned identically with the same set of parameters. To simplify the provisioning process, the EFM-CU-MIB module makes use of configuration profiles, similar to the HDSL2-SHDSL-LINE-MIB and VDSL-LINE-EXT-MCM-MIB modules. A profile is a set of parameters, used either for configuration or representation of a PME. The same profile can be shared by multiple PME ports using the same configuration.
由于受管节点可能有大量EFMCu PHY，因此在每个EFMCu PHY上设置每个参数可能会变得很麻烦。此外，大多数PME都以相同的参数集提供。为了简化配置过程，EFM-CU-MIB模块使用了与HDSL2-SHDSL-LINE-MIB和VDSL-LINE-EXT-MCM-MIB模块类似的配置配置文件。配置文件是一组参数，用于配置或表示PME。使用相同配置的多个PME端口可以共享相同的配置文件。
The PME profiles are defined in the efmCuPme2BProfileTable and efmCuPme10PProfileTable for 2BASE-TL and 10PASS-TS PMEs, respectively. There are 12 predefined standard profiles for 2BASE-TL and 22 standard profiles for 10PASS-TS, defined in 802.3ah and dedicated for rapid provisioning of EFMCu PHYs in most scenarios. In addition, the EFM-CU-MIB defines two additional predefined profiles for "best-effort" provisioning of 2BASE-TL PMEs. An ability to define new configuration profiles is also provided to allow for EFMCu deployment tailored to specific copper environments and spectral regulations.
PME配置文件分别在2BASE-TL和10PASS-TS PME的efmCuPme2BProfileTable和efmCuPme10PProfileTable中定义。有12个预定义的2BASE-TL标准配置文件和22个10PASS-TS标准配置文件，在802.3ah中定义，专门用于在大多数场景中快速配置EFMCu物理。此外，EFM-CU-MIB为2BASE-TL PME的“尽力而为”供应定义了两个额外的预定义配置文件。还提供了定义新配置配置文件的能力，以允许根据特定铜缆环境和频谱法规定制EFMCu部署。
A specific configuration or administrative profile is assigned to a specific PME via the efmCuPmeAdminProfile object. If efmCuPmeAdminProfile is zero, then the efmCuAdminProfile object of the PCS port connected to the PME determines the configuration profile (or a list of possible profiles) for that PME. This mechanism allows specifying a common profile for all PMEs connected to the PCS port, with an ability to change individual PME profiles by setting efmCuPmeAdminProfile object, which overwrites the profile set by efmCuAdminProfile.
通过efmCuPmeAdminProfile对象将特定配置或管理配置文件分配给特定PME。如果efmCuPmeAdminProfile为零，则连接到PME的PCS端口的efmCuAdminProfile对象确定该PME的配置配置文件（或可能的配置文件列表）。此机制允许为连接到PCS端口的所有PME指定公共配置文件，并能够通过设置efmCuPmeAdminProfile对象更改单个PME配置文件，该对象覆盖efmCuAdminProfile设置的配置文件。
A current operating PME profile is pointed to by the efmCuPmeOperProfile object. Note that this profile entry can be created automatically to reflect achieved parameters in adaptive (not fixed) initialization.
efmCuPmeOperProfile对象指向当前运行的PME配置文件。请注意，可以自动创建此配置文件条目，以反映自适应（非固定）初始化中实现的参数。
This section contains the mapping between relevant managed objects (attributes) defined in [802.3ah] Clause 30, and managed objects defined in this document and in associated MIB modules, i.e., the IF-MIB [RFC2863].
本节包含[802.3ah]第30条中定义的相关托管对象（属性）与本文档和相关MIB模块（即IF-MIB[RFC2863]）中定义的托管对象之间的映射。
Note that the majority of the objects defined in the EFM-CU-MIB module do not have direct counterparts in Clause 30 and instead refer to Clause 45 registers.
请注意，EFM-CU-MIB模块中定义的大多数对象在第30条中没有直接对应项，而是参考第45条寄存器。
+---------------------------------+---------------------------------+
| IEEE 802.3 Managed Object | Corresponding SNMP Object |
+---------------------------------+---------------------------------+
| oMAU - Basic Package | |
| (Mandatory) | |
+---------------------------------+---------------------------------+
| aMAUType | ifMauType (MAU-MIB) |
+---------------------------------+---------------------------------+
| aMAUTypeList | ifMauTypeListBits (MAU-MIB) |
+---------------------------------+---------------------------------+
| aMediaAvailable | ifMediaAvailable (MAU-MIB) |
+---------------------------------+---------------------------------+
| oPAF - Basic Package | |
| (Mandatory) | |
+---------------------------------+---------------------------------+
| aPAFID | ifIndex (IF-MIB) |
+---------------------------------+---------------------------------+
| aPhyEnd | efmCuPhySide |
+---------------------------------+---------------------------------+
| aPHYCurrentStatus | efmCuStatus |
+---------------------------------+---------------------------------+
| aPAFSupported | efmCuPAFSupported |
+---------------------------------+---------------------------------+
| oPAF - PME Aggregation Package | |
| (Optional) | |
+---------------------------------+---------------------------------+
| aPAFAdminState | efmCuPAFAdminState |
+---------------------------------+---------------------------------+
| aLocalPAFCapacity | efmCuPAFCapacity |
+---------------------------------+---------------------------------+
| aLocalPMEAvailable | ifCapStackTable |
+---------------------------------+---------------------------------+
| aLocalPMEAggregate | ifStackTable (IF-MIB) |
+---------------------------------+---------------------------------+
| aRemotePAFSupported | efmCuRemotePAFSupported |
+---------------------------------+---------------------------------+
| aRemotePAFCapacity | efmCuRemotePAFCapacity |
+---------------------------------+---------------------------------+
| aRemotePMEAggregate | |
+---------------------------------+---------------------------------+
| oPME - 10P/2B Package | |
| (Mandatory) | |
+---------------------------------+---------------------------------+
| aPMEID | ifIndex (IF-MIB) |
+---------------------------------+---------------------------------+
| IEEE 802.3 Managed Object | Corresponding SNMP Object |
+---------------------------------+---------------------------------+
| oMAU - Basic Package | |
| (Mandatory) | |
+---------------------------------+---------------------------------+
| aMAUType | ifMauType (MAU-MIB) |
+---------------------------------+---------------------------------+
| aMAUTypeList | ifMauTypeListBits (MAU-MIB) |
+---------------------------------+---------------------------------+
| aMediaAvailable | ifMediaAvailable (MAU-MIB) |
+---------------------------------+---------------------------------+
| oPAF - Basic Package | |
| (Mandatory) | |
+---------------------------------+---------------------------------+
| aPAFID | ifIndex (IF-MIB) |
+---------------------------------+---------------------------------+
| aPhyEnd | efmCuPhySide |
+---------------------------------+---------------------------------+
| aPHYCurrentStatus | efmCuStatus |
+---------------------------------+---------------------------------+
| aPAFSupported | efmCuPAFSupported |
+---------------------------------+---------------------------------+
| oPAF - PME Aggregation Package | |
| (Optional) | |
+---------------------------------+---------------------------------+
| aPAFAdminState | efmCuPAFAdminState |
+---------------------------------+---------------------------------+
| aLocalPAFCapacity | efmCuPAFCapacity |
+---------------------------------+---------------------------------+
| aLocalPMEAvailable | ifCapStackTable |
+---------------------------------+---------------------------------+
| aLocalPMEAggregate | ifStackTable (IF-MIB) |
+---------------------------------+---------------------------------+
| aRemotePAFSupported | efmCuRemotePAFSupported |
+---------------------------------+---------------------------------+
| aRemotePAFCapacity | efmCuRemotePAFCapacity |
+---------------------------------+---------------------------------+
| aRemotePMEAggregate | |
+---------------------------------+---------------------------------+
| oPME - 10P/2B Package | |
| (Mandatory) | |
+---------------------------------+---------------------------------+
| aPMEID | ifIndex (IF-MIB) |
+---------------------------------+---------------------------------+
| aPMEAdminState | ifAdminState (IF-MIB) |
+---------------------------------+---------------------------------+
| aPMEStatus | efmCuPmeStatus |
| aPMESNRMgn | efmCuPmeSnrMgn |
+---------------------------------+---------------------------------+
| aTCCodingViolations | efmCuPmeTCCodingErrors |
+---------------------------------+---------------------------------+
| aTCCRCErrors | efmCuPmeTCCrcErrors |
+---------------------------------+---------------------------------+
| aProfileSelect | efmCuAdminProfile, |
| | efmCuPmeAdminProfile |
+---------------------------------+---------------------------------+
| aOperatingProfile | efmCuPmeOperProfile |
+---------------------------------+---------------------------------+
| aPMEFECCorrectedBlocks | efmCuPme10PFECCorrectedBlocks |
+---------------------------------+---------------------------------+
| aPMEFECUncorrectableBlocks | efmCuPme10PFECUncorrectedBlocks |
+---------------------------------+---------------------------------+
+---------------------------------+---------------------------------+
| aPMEAdminState | ifAdminState (IF-MIB) |
+---------------------------------+---------------------------------+
| aPMEStatus | efmCuPmeStatus |
| aPMESNRMgn | efmCuPmeSnrMgn |
+---------------------------------+---------------------------------+
| aTCCodingViolations | efmCuPmeTCCodingErrors |
+---------------------------------+---------------------------------+
| aTCCRCErrors | efmCuPmeTCCrcErrors |
+---------------------------------+---------------------------------+
| aProfileSelect | efmCuAdminProfile, |
| | efmCuPmeAdminProfile |
+---------------------------------+---------------------------------+
| aOperatingProfile | efmCuPmeOperProfile |
+---------------------------------+---------------------------------+
| aPMEFECCorrectedBlocks | efmCuPme10PFECCorrectedBlocks |
+---------------------------------+---------------------------------+
| aPMEFECUncorrectableBlocks | efmCuPme10PFECUncorrectedBlocks |
+---------------------------------+---------------------------------+
Table 2: Mapping of IEEE 802.3 Managed Objects
表2:IEEE 802.3托管对象的映射
IF-CAP-STACK-MIB DEFINITIONS ::= BEGIN
IF-CAP-STACK-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, mib-2
FROM SNMPv2-SMI -- [RFC2578]
TruthValue
FROM SNMPv2-TC -- [RFC2579]
MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF -- [RFC2580]
ifStackGroup2, ifStackHigherLayer, ifStackLowerLayer
FROM IF-MIB -- [RFC2863]
ifInvStackGroup
FROM IF-INVERTED-STACK-MIB -- [RFC2864]
;
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, mib-2
FROM SNMPv2-SMI -- [RFC2578]
TruthValue
FROM SNMPv2-TC -- [RFC2579]
MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF -- [RFC2580]
ifStackGroup2, ifStackHigherLayer, ifStackLowerLayer
FROM IF-MIB -- [RFC2863]
ifInvStackGroup
FROM IF-INVERTED-STACK-MIB -- [RFC2864]
;
ifCapStackMIB MODULE-IDENTITY
LAST-UPDATED "200711070000Z" -- November 07, 2007
ORGANIZATION "IETF Ethernet Interfaces and Hub MIB Working Group"
CONTACT-INFO
"WG charter:
http://www.ietf.org/html.charters/OLD/hubmib-charter.html
ifCapStackMIB MODULE-IDENTITY
LAST-UPDATED "200711070000Z" -- November 07, 2007
ORGANIZATION "IETF Ethernet Interfaces and Hub MIB Working Group"
CONTACT-INFO
"WG charter:
http://www.ietf.org/html.charters/OLD/hubmib-charter.html
Mailing Lists: General Discussion: hubmib@ietf.org
邮寄名单：一般性讨论：hubmib@ietf.org
To Subscribe: hubmib-request@ietf.org In Body: subscribe your_email_address
订阅：hubmib-request@ietf.org正文：订阅您的电子邮件地址
Chair: Bert Wijnen Postal: Alcatel-Lucent Schagen 33 3461 GL Linschoten Netherlands Phone: +31-348-407-775 EMail: bwijnen@alcatel-lucent.com
主席：Bert Wijnen邮政：阿尔卡特朗讯夏根33 3461德国劳埃德林肖顿荷兰电话：+31-348-407-775电子邮件：bwijnen@alcatel-朗讯网
Editor: Edward Beili Postal: Actelis Networks Inc. 25 Bazel St., P.O.B. 10173 Petach-Tikva 10173 Israel Phone: +972-3-924-3491 EMail: edward.beili@actelis.com"
编辑：Edward Beili Postal:Actelis Networks Inc.巴泽尔街25号，邮编：10173 Petach Tikva 10173以色列电话：+972-3-924-3491电子邮件：Edward。beili@actelis.com"
DESCRIPTION "The objects in this MIB module are used to describe cross-connect capabilities of stacked (layered) interfaces, complementing ifStackTable and ifInvStackTable defined in IF-MIB and IF-INVERTED-STACK-MIB, respectively.
DESCRIPTION“此MIB模块中的对象用于描述堆叠（分层）接口的交叉连接功能，分别补充IF-MIB和IF-INVERTED-STACK-MIB中定义的ifStackTable和ifInvStackTable。
Copyright (C) The IETF Trust (2007). This version of this MIB module is part of RFC 5066; see the RFC itself for full legal notices."
版权所有（C）IETF信托基金（2007年）。此版本的MIB模块是RFC 5066的一部分；有关完整的法律通知，请参见RFC本身。”
REVISION "200711070000Z" -- November 07, 2007 DESCRIPTION "Initial version, published as RFC 5066."
修订版“200711070000Z”-2007年11月7日描述“初始版本，发布为RFC 5066。”
::= { mib-2 166 }
::= { mib-2 166 }
-- Sections of the module
-- Structured as recommended by [RFC4181], see
-- Appendix D: Suggested OID Layout
-- Sections of the module
-- Structured as recommended by [RFC4181], see
-- Appendix D: Suggested OID Layout
ifCapStackObjects OBJECT IDENTIFIER ::= { ifCapStackMIB 1 }
ifCapStackObjects OBJECT IDENTIFIER ::= { ifCapStackMIB 1 }
ifCapStackConformance OBJECT IDENTIFIER ::= { ifCapStackMIB 2 }
ifCapStackConformance OBJECT IDENTIFIER ::= { ifCapStackMIB 2 }
-- Groups in the module
--模块中的组
-- -- ifCapStackTable group --
----ifCapStackTable组--
ifCapStackTable OBJECT-TYPE SYNTAX SEQUENCE OF IfCapStackEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table, modeled after ifStackTable from IF-MIB, contains information on the possible 'on-top-of' relationships between the multiple sub-layers of network interfaces (as opposed to actual relationships described in ifStackTable). In particular, it contains information on which sub-layers MAY possibly run 'on top of' which other sub-layers, as determined by cross-connect capability of the device, where each sub-layer corresponds to a conceptual row in the ifTable. For example, when the sub-layer with ifIndex value x can be connected to run on top of the sub-layer with ifIndex value y, then this table contains:
ifCapStackTable对象类型IfCapStackEntry MAX-ACCESS不可访问状态当前描述的语法序列“此表以IF-MIB中的ifStackTable为模型，包含关于网络接口多个子层之间可能的“顶部”关系的信息（与ifStackTable中描述的实际关系相反）。特别是，它包含关于哪些子层可能“在”哪些其他子层上运行的信息，由设备的交叉连接能力确定，其中每个子层对应于ifTable中的概念行。例如，当ifIndex值为x的子层可以连接到ifI的子层上运行时ndex值y，则此表包含：
ifCapStackStatus.x.y=true
ifCapStackStatus.x.y=true
The ifCapStackStatus.x.y row does not exist if it is impossible to connect between the sub-layers x and y.
如果无法在子层x和y之间连接，则ifCapStackStatus.x.y行不存在。
Note that for most stacked interfaces (e.g., 2BASE-TL) there's always at least one higher-level interface (e.g., PCS port) for each lower-level interface (e.g., PME) and at least one lower-level interface for each higher-level interface, that is, there is at least a single row with a 'true' status for any such existing value of x or y.
请注意，对于大多数堆叠接口（例如2BASE-TL），每个较低级别接口（例如PME）至少有一个较高级别的接口（例如PCS端口），每个较高级别接口至少有一个较低级别的接口，也就是说，对于任何这样的现有值x或y，至少有一行具有“真”状态。
This table is read-only as it describes device capabilities."
REFERENCE
"IF-MIB, ifStackTable"
::= { ifCapStackObjects 1 }
This table is read-only as it describes device capabilities."
REFERENCE
"IF-MIB, ifStackTable"
::= { ifCapStackObjects 1 }
ifCapStackEntry OBJECT-TYPE
SYNTAX IfCapStackEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information on a particular relationship between two
sub-layers, specifying that one sub-layer MAY possibly run
on 'top' of the other sub-layer. Each sub-layer corresponds
to a conceptual row in the ifTable (interface index for
lower and higher layer, respectively)."
INDEX {
ifStackHigherLayer,
ifStackLowerLayer
}
ifCapStackEntry OBJECT-TYPE
SYNTAX IfCapStackEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information on a particular relationship between two
sub-layers, specifying that one sub-layer MAY possibly run
on 'top' of the other sub-layer. Each sub-layer corresponds
to a conceptual row in the ifTable (interface index for
lower and higher layer, respectively)."
INDEX {
ifStackHigherLayer,
ifStackLowerLayer
}
::= { ifCapStackTable 1 }
::= { ifCapStackTable 1 }
IfCapStackEntry ::= SEQUENCE {
ifCapStackStatus TruthValue
}
IfCapStackEntry ::= SEQUENCE {
ifCapStackStatus TruthValue
}
ifCapStackStatus OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "The status of the 'cross-connect capability' relationship between two sub-layers. The following values can be returned: true(1) - indicates that the sub-layer interface, identified by the ifStackLowerLayer MAY be connected to run 'below' the sub-layer interface, identified by the ifStackHigherLayer index. false(2) - the sub-layer interfaces cannot be connected temporarily due to unavailability of the interface(s), e.g., one of the interfaces is located on an absent pluggable module.
ifCapStackStatus对象类型语法TruthValue MAX-ACCESS只读状态当前描述“两个子层之间“交叉连接能力”关系的状态。可以返回以下值：true（1）-表示由ifStackLowerLayer标识的子层接口可以连接到由ifStackHigherLayer索引标识的子层接口的“下方”。false（2）-由于接口不可用，子层接口暂时无法连接例如，其中一个接口位于不存在的可插拔模块上。
Note that lower-layer interface availability per higher-layer, indicated by the value of 'true', can be constrained by other parameters, for example, by the aggregation capacity of a higher-layer interface or by the lower-layer interface in question being already connected to another higher-layer interface. In order to ensure that a particular sub-layer can be connected to another sub-layer, all respective objects (e.g., ifCapStackTable, ifStackTable, and efmCuPAFCapacity for EFMCu interfaces) SHALL be inspected.
请注意，由“true”值表示的每更高层的下层接口可用性可受其他参数的约束，例如，受更高层接口的聚合容量或已连接到另一更高层接口的相关下层接口的约束。为了确保特定子层可以连接到另一个子层，应检查所有相应的对象（例如，ifCapStackTable、ifStackTable和EFMCu接口的efmCuPAFCapacity）。
This object is read-only, unlike ifStackStatus, as it
describes a cross-connect capability."
::= { ifCapStackEntry 1 }
This object is read-only, unlike ifStackStatus, as it
describes a cross-connect capability."
::= { ifCapStackEntry 1 }
ifInvCapStackTable OBJECT-TYPE SYNTAX SEQUENCE OF IfInvCapStackEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table containing information on the possible relationships between the multiple sub-layers of network interfaces. This table, modeled after ifInvStackTable from IF-INVERTED-STACK-MIB, is an inverse of the ifCapStackTable defined in this MIB module.
ifInvCapStackTable对象类型IfInvCapStackEntry的语法序列MAX-ACCESS不可访问状态当前描述“包含网络接口多个子层之间可能关系的信息的表。此表以IF-INVERTED-STACK-MIB中的ifInvStackTable为模型，与此MIB模块中定义的ifCapStackTable相反。
In particular, this table contains information on which sub-layers MAY run 'underneath' which other sub-layers, where each sub-layer corresponds to a conceptual row in the ifTable. For example, when the sub-layer with ifIndex value x MAY be connected to run underneath the sub-layer with ifIndex value y, then this table contains:
特别是，此表包含关于哪些子层可能“在”哪些其他子层下运行的信息，其中每个子层对应于ifTable中的一个概念行。例如，当ifIndex值为x的子层连接到ifIndex值为y的子层下方时，此表包含：
ifInvCapStackStatus.x.y=true
ifInvCapStackStatus.x.y=true
This table contains exactly the same number of rows as the ifCapStackTable, but the rows appear in a different order.
此表包含的行数与ifCapStackTable完全相同，但行的显示顺序不同。
This table is read-only as it describes a cross-connect
capability."
REFERENCE
"IF-INVERTED-STACK-MIB, ifInvStackTable"
::= { ifCapStackObjects 2 }
This table is read-only as it describes a cross-connect
capability."
REFERENCE
"IF-INVERTED-STACK-MIB, ifInvStackTable"
::= { ifCapStackObjects 2 }
ifInvCapStackEntry OBJECT-TYPE
SYNTAX IfInvCapStackEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information on a particular relationship between two sub-
layers, specifying that one sub-layer MAY run underneath the
other sub-layer. Each sub-layer corresponds to a conceptual
row in the ifTable."
INDEX { ifStackLowerLayer, ifStackHigherLayer }
::= { ifInvCapStackTable 1 }
ifInvCapStackEntry OBJECT-TYPE
SYNTAX IfInvCapStackEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information on a particular relationship between two sub-
layers, specifying that one sub-layer MAY run underneath the
other sub-layer. Each sub-layer corresponds to a conceptual
row in the ifTable."
INDEX { ifStackLowerLayer, ifStackHigherLayer }
::= { ifInvCapStackTable 1 }
IfInvCapStackEntry ::= SEQUENCE {
ifInvCapStackStatus TruthValue
}
IfInvCapStackEntry ::= SEQUENCE {
ifInvCapStackStatus TruthValue
}
ifInvCapStackStatus OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "The status of the possible 'cross-connect capability' relationship between two sub-layers.
ifInvCapStackStatus对象类型语法TruthValue MAX-ACCESS只读状态当前描述“两个子层之间可能的“交叉连接能力”关系的状态。
An instance of this object exists for each instance of the ifCapStackStatus object, and vice versa. For example, if the variable ifCapStackStatus.H.L exists, then the variable ifInvCapStackStatus.L.H must also exist, and vice versa. In addition, the two variables always have the same value.
ifCapStackStatus对象的每个实例都存在此对象的实例，反之亦然。例如，如果变量ifCapStackStatus.H.L存在，那么变量ifInvCapStackStatus.L.H也必须存在，反之亦然。此外，这两个变量始终具有相同的值。
The ifInvCapStackStatus object is read-only, as it describes
a cross-connect capability."
REFERENCE
"ifCapStackStatus"
::= { ifInvCapStackEntry 1 }
The ifInvCapStackStatus object is read-only, as it describes
a cross-connect capability."
REFERENCE
"ifCapStackStatus"
::= { ifInvCapStackEntry 1 }
-- -- Conformance Statements --
----一致性声明--
ifCapStackGroups OBJECT IDENTIFIER ::=
{ ifCapStackConformance 1 }
ifCapStackGroups OBJECT IDENTIFIER ::=
{ ifCapStackConformance 1 }
ifCapStackCompliances OBJECT IDENTIFIER ::=
{ ifCapStackConformance 2 }
ifCapStackCompliances OBJECT IDENTIFIER ::=
{ ifCapStackConformance 2 }
-- Units of Conformance
--一致性单位
ifCapStackGroup OBJECT-GROUP
OBJECTS {
ifCapStackStatus,
ifInvCapStackStatus
}
STATUS current
DESCRIPTION
"A collection of objects providing information on the
cross-connect capability of multi-layer (stacked) network
interfaces."
::= { ifCapStackGroups 1 }
ifCapStackGroup OBJECT-GROUP
OBJECTS {
ifCapStackStatus,
ifInvCapStackStatus
}
STATUS current
DESCRIPTION
"A collection of objects providing information on the
cross-connect capability of multi-layer (stacked) network
interfaces."
::= { ifCapStackGroups 1 }
-- Compliance Statements
--合规声明
ifCapStackCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for SNMP entities, which provide information on the cross-connect capability of multi-layer (stacked) network interfaces, with flexible cross-connect between the sub-layers."
ifCapStackCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION“SNMP实体的符合性声明，该声明提供关于多层（堆叠）网络接口的交叉连接能力的信息，以及子层之间的灵活交叉连接。”
MODULE -- this module
MANDATORY-GROUPS {
ifCapStackGroup
}
MODULE -- this module
MANDATORY-GROUPS {
ifCapStackGroup
}
OBJECT ifCapStackStatus
对象状态
SYNTAX TruthValue { true(1) } DESCRIPTION "Support for the false(2) value is OPTIONAL for implementations supporting pluggable interfaces."
语法TruthValue{true（1）}DESCRIPTION“对于支持可插拔接口的实现，对false（2）值的支持是可选的。”
OBJECT ifInvCapStackStatus SYNTAX TruthValue { true(1) } DESCRIPTION "Support for the false(2) value is OPTIONAL for implementations supporting pluggable interfaces."
对象ifInvCapStackStatus语法TruthValue{true（1）}说明“对于支持可插拔接口的实现，对false（2）值的支持是可选的。”
MODULE IF-MIB
MANDATORY-GROUPS {
ifStackGroup2
}
MODULE IF-MIB
MANDATORY-GROUPS {
ifStackGroup2
}
MODULE IF-INVERTED-STACK-MIB
MANDATORY-GROUPS {
ifInvStackGroup
}
MODULE IF-INVERTED-STACK-MIB
MANDATORY-GROUPS {
ifInvStackGroup
}
::= { ifCapStackCompliances 1 }
END
::= { ifCapStackCompliances 1 }
END
EFM-CU-MIB DEFINITIONS ::= BEGIN
EFM-CU-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Integer32,
Unsigned32, Counter32, mib-2
FROM SNMPv2-SMI -- [RFC2578]
TEXTUAL-CONVENTION, TruthValue, RowStatus, PhysAddress
FROM SNMPv2-TC -- [RFC2579]
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF -- [RFC2580]
SnmpAdminString
FROM SNMP-FRAMEWORK-MIB -- [RFC3411]
ifIndex, ifSpeed
FROM IF-MIB -- [RFC2863]
;
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Integer32,
Unsigned32, Counter32, mib-2
FROM SNMPv2-SMI -- [RFC2578]
TEXTUAL-CONVENTION, TruthValue, RowStatus, PhysAddress
FROM SNMPv2-TC -- [RFC2579]
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF -- [RFC2580]
SnmpAdminString
FROM SNMP-FRAMEWORK-MIB -- [RFC3411]
ifIndex, ifSpeed
FROM IF-MIB -- [RFC2863]
;
efmCuMIB MODULE-IDENTITY
LAST-UPDATED "200711140000Z" -- November 14, 2007
ORGANIZATION "IETF Ethernet Interfaces and Hub MIB Working Group"
CONTACT-INFO
"WG charter:
http://www.ietf.org/html.charters/OLD/hubmib-charter.html
efmCuMIB MODULE-IDENTITY
LAST-UPDATED "200711140000Z" -- November 14, 2007
ORGANIZATION "IETF Ethernet Interfaces and Hub MIB Working Group"
CONTACT-INFO
"WG charter:
http://www.ietf.org/html.charters/OLD/hubmib-charter.html
Mailing Lists:
General Discussion: hubmib@ietf.org
To Subscribe: hubmib-request@ietf.org
In Body: subscribe your_email_address
Mailing Lists:
General Discussion: hubmib@ietf.org
To Subscribe: hubmib-request@ietf.org
In Body: subscribe your_email_address
Chair: Bert Wijnen Postal: Alcatel-Lucent Schagen 33 3461 GL Linschoten Netherlands Phone: +31-348-407-775 EMail: bwijnen@alcatel-lucent.com
主席：Bert Wijnen邮政：阿尔卡特朗讯夏根33 3461德国劳埃德林肖顿荷兰电话：+31-348-407-775电子邮件：bwijnen@alcatel-朗讯网
Editor: Edward Beili Postal: Actelis Networks Inc. 25 Bazel St., P.O.B. 10173 Petach-Tikva 10173 Israel Phone: +972-3-924-3491 Email: edward.beili@actelis.com"
编辑：Edward Beili Postal:Actelis Networks Inc.巴泽尔街25号，邮编：10173 Petach Tikva 10173以色列电话：+972-3-924-3491电子邮件：Edward。beili@actelis.com"
DESCRIPTION "The objects in this MIB module are used to manage the Ethernet in the First Mile (EFM) Copper (EFMCu) Interfaces 2BASE-TL and 10PASS-TS, defined in IEEE Std. 802.3ah-2004, which is now a part of IEEE Std. 802.3-2005.
描述“此MIB模块中的对象用于管理第一英里（EFM）铜缆（EFMCu）接口2BASE-TL和10PASS-TS中的以太网，这些接口在IEEE标准802.3ah-2004中定义，现在是IEEE标准802.3-2005的一部分。
The following references are used throughout this MIB module:
此MIB模块中使用了以下参考：
[802.3ah] refers to: IEEE Std 802.3ah-2004: 'IEEE Standard for Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 3: Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications - Amendment: Media Access Control Parameters, Physical Layers and Management Parameters for Subscriber Access Networks', 07 September 2004.
[802.3ah]参考：IEEE标准802.3ah-2004:“IEEE信息技术标准-系统间电信和信息交换-局域网和城域网-特殊要求-第3部分：带冲突检测的载波侦听多址接入（CSMA/CD）接入方法和物理层规范.修改件：用户接入网络的媒体接入控制参数，物理层和管理参数，2004年9月7日。
Of particular interest are Clause 61, 'Physical Coding Sublayer (PCS) and common specifications, type 10PASS-TS and type 2BASE-TL', Clause 30, 'Management', Clause 45, 'Management Data Input/Output (MDIO) Interface', Annex 62A, 'PMD profiles for 10PASS-TS' and Annex 63A, 'PMD profiles for 2BASE-TL'.
特别令人感兴趣的是第61条“物理编码子层（PCS）和通用规范、10PASS-TS类型和2BASE-TL类型”、第30条“管理”、第45条“管理数据输入/输出（MDIO）接口”、附件62A“10PASS-TS的PMD配置文件”和附件63A“2BASE-TL的PMD配置文件”。
[G.991.2] refers to: ITU-T Recommendation G.991.2: 'Single-pair High-speed Digital Subscriber Line (SHDSL) transceivers', December 2003.
[G.991.2]参考：ITU-T建议G.991.2:“单对高速数字用户线（SHDSL）收发器”，2003年12月。
[ANFP] refers to: NICC Document ND1602:2005/08: 'Specification of the Access Network Frequency Plan (ANFP) applicable to transmission systems used on the BT Access Network,' August 2005.
[ANFP]参考：NICC文件ND1602:2005/08：“适用于BT接入网络上使用的传输系统的接入网络频率计划（ANFP）规范”，2005年8月。
The following normative documents are quoted by the DESCRIPTION clauses in this MIB module:
本MIB模块中的描述条款引用了以下规范性文件：
[G.993.1] refers to: ITU-T Recommendation G.993.1: 'Very High speed Digital Subscriber Line transceivers', June 2004.
[G.993.1]参考：ITU-T建议G.993.1:“超高速数字用户线收发器”，2004年6月。
[T1.424] refers to: ANSI T1.424-2004: 'Interface Between Networks and Customer Installation Very-high-bit-rate Digital Subscriber Lines (VDSL) Metallic Interface (DMT Based)', June 2004.
[T1.424]参考：ANSI T1.424-2004：“网络与客户安装之间的接口甚高速数字用户线（VDSL）金属接口（基于DMT）”，2004年6月。
[TS 101 270-1] refers to:
ETSI TS 101 270-1: 'Transmission and Multiplexing (TM);
Access transmission systems on metallic access cables;
Very high speed Digital Subscriber Line (VDSL); Part 1:
Functional requirements', October 2005.
[TS 101 270-1] refers to:
ETSI TS 101 270-1: 'Transmission and Multiplexing (TM);
Access transmission systems on metallic access cables;
Very high speed Digital Subscriber Line (VDSL); Part 1:
Functional requirements', October 2005.
Naming Conventions: Atn - Attenuation CO - Central Office CPE - Customer Premises Equipment EFM - Ethernet in the First Mile EFMCu - EFM Copper MDIO - Management Data Input/Output Mgn - Margin PAF - PME Aggregation Function PBO - Power Back-Off PCS - Physical Coding Sublayer PMD - Physical Medium Dependent PME - Physical Medium Entity PSD - Power Spectral Density SNR - Signal to Noise Ratio TCPAM - Trellis Coded Pulse Amplitude Modulation
命名约定：Atn-衰减协同-中央办公室CPE-客户场所设备EFM-第一英里以太网EFMCu-EFM铜质MDIO-管理数据输入/输出Mgn-余量PAF-PME聚合功能PBO-电源回退PC-物理编码子层PMD-物理介质相关PME-物理介质实体PSD-电源谱密度信噪比TCPAM格形编码脉冲幅度调制
Copyright (C) The IETF Trust (2007). This version of this MIB module is part of RFC 5066; see the RFC itself for full legal notices."
版权所有（C）IETF信托基金（2007年）。此版本的MIB模块是RFC 5066的一部分；有关完整的法律通知，请参见RFC本身。”
REVISION "200711140000Z" -- November 14, 2007 DESCRIPTION "Initial version, published as RFC 5066."
修订版“200711140000Z”-2007年11月14日描述“初始版本，发布为RFC 5066。”
::= { mib-2 167 }
::= { mib-2 167 }
-- Sections of the module
--模块的各个部分
efmCuObjects OBJECT IDENTIFIER ::= { efmCuMIB 1 }
efmCuObjects OBJECT IDENTIFIER ::= { efmCuMIB 1 }
efmCuConformance OBJECT IDENTIFIER ::= { efmCuMIB 2 }
efmCuConformance OBJECT IDENTIFIER ::= { efmCuMIB 2 }
-- Groups in the module
--模块中的组
efmCuPort OBJECT IDENTIFIER ::= { efmCuObjects 1 }
efmCuPort OBJECT IDENTIFIER ::= { efmCuObjects 1 }
efmCuPme OBJECT IDENTIFIER ::= { efmCuObjects 2 }
efmCuPme OBJECT IDENTIFIER ::= { efmCuObjects 2 }
-- Textual Conventions
--文本约定
EfmProfileIndex ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"A unique value, greater than zero, for each PME configuration
profile in the managed EFMCu port. It is RECOMMENDED that
values are assigned contiguously starting from 1. The value
for each profile MUST remain constant at least from one
re-initialization of the entity's network management system
to the next re-initialization."
SYNTAX Unsigned32 (1..255)
EfmProfileIndex ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"A unique value, greater than zero, for each PME configuration
profile in the managed EFMCu port. It is RECOMMENDED that
values are assigned contiguously starting from 1. The value
for each profile MUST remain constant at least from one
re-initialization of the entity's network management system
to the next re-initialization."
SYNTAX Unsigned32 (1..255)
EfmProfileIndexOrZero ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"This textual convention is an extension of the
EfmProfileIndex convention. The latter defines a greater than
zero value used to identify a PME profile in the managed EFMCu
port. This extension permits the additional value of zero.
The value of zero is object-specific and MUST therefore be
defined as part of the description of any object that uses
this syntax.
Examples of the usage of zero value might include situations
where the current operational profile is unknown."
SYNTAX Unsigned32 (0..255)
EfmProfileIndexOrZero ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"This textual convention is an extension of the
EfmProfileIndex convention. The latter defines a greater than
zero value used to identify a PME profile in the managed EFMCu
port. This extension permits the additional value of zero.
The value of zero is object-specific and MUST therefore be
defined as part of the description of any object that uses
this syntax.
Examples of the usage of zero value might include situations
where the current operational profile is unknown."
SYNTAX Unsigned32 (0..255)
EfmProfileIndexList ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1d:"
EfmProfileIndexList ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1d:"
STATUS current DESCRIPTION "This textual convention represents a list of up to 6 EfmProfileIndex values, any of which can be chosen for configuration of a PME in a managed EFMCu port. The EfmProfileIndex textual convention defines a greater than zero value used to identify a PME profile. The value of this object is a concatenation of zero or more (up to 6) octets, where each octet contains an 8-bit EfmProfileIndex value. A zero-length octet string is object-specific and MUST therefore be defined as part of the description of any object that uses this syntax. Examples of the usage of a zero-length value might include situations where an object using this textual convention is irrelevant for a specific EFMCu port type." SYNTAX OCTET STRING (SIZE(0..6))
STATUS current DESCRIPTION“此文本约定表示最多6个EfmProfileIndex值的列表，可以选择其中任何一个值来配置托管EFMCu端口中的PME。EfmProfileIndex文本约定定义了一个大于零的值，用于标识PME配置文件。此对象的值是零或多个值的串联（最多6个）八位字节，其中每个八位字节包含一个8位EfmProfileIndex值。零长度八位字节字符串是特定于对象的，因此必须定义为使用此语法的任何对象描述的一部分。使用零长度值的示例可能包括使用此文本约定的对象与说明符无关的情况ic EFMCu端口类型。“语法八位字节字符串（大小（0..6））
EfmTruthValueOrUnknown ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual convention is an extension of the TruthValue
convention. The latter defines a boolean value with possible
values of true(1) and false(2). This extension permits the
additional value of unknown(0), which can be returned as the
result of a GET operation when an exact true or false value
of the object cannot be determined."
SYNTAX INTEGER { unknown(0), true(1), false(2) }
EfmTruthValueOrUnknown ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual convention is an extension of the TruthValue
convention. The latter defines a boolean value with possible
values of true(1) and false(2). This extension permits the
additional value of unknown(0), which can be returned as the
result of a GET operation when an exact true or false value
of the object cannot be determined."
SYNTAX INTEGER { unknown(0), true(1), false(2) }
-- Port Notifications Group
--端口通知组
efmCuPortNotifications OBJECT IDENTIFIER ::= { efmCuPort 0 }
efmCuPortNotifications OBJECT IDENTIFIER ::= { efmCuPort 0 }
efmCuLowRateCrossing NOTIFICATION-TYPE
OBJECTS {
ifSpeed,
efmCuThreshLowRate
}
STATUS current
DESCRIPTION
"This notification indicates that the EFMCu port's data rate
has reached/dropped below or exceeded the low rate threshold,
specified by efmCuThreshLowRate.
efmCuLowRateCrossing NOTIFICATION-TYPE
OBJECTS {
ifSpeed,
efmCuThreshLowRate
}
STATUS current
DESCRIPTION
"This notification indicates that the EFMCu port's data rate
has reached/dropped below or exceeded the low rate threshold,
specified by efmCuThreshLowRate.
This notification MAY be sent for the -O subtype ports (2BaseTL-O/10PassTS-O) while the port is Up, on the crossing event in both directions: from normal (rate is above the threshold) to low (rate equals the threshold or below it) and
当端口启动时，可在交叉事件的两个方向上为-O子类型端口（2BaseTL-O/10PassTS-O）发送此通知：从正常（速率高于阈值）到低（速率等于阈值或低于阈值）以及
from low to normal. This notification is not applicable to the -R subtypes.
从低到正常。此通知不适用于-R子类型。
It is RECOMMENDED that a small debouncing period of 2.5 sec, between the detection of the condition and the notification, is implemented to prevent simultaneous LinkUp/LinkDown and efmCuLowRateCrossing notifications to be sent.
建议在检测到状况和通知之间实施2.5秒的小去抖动周期，以防止同时发送链路上升/链路下降和efmCuLowRateCrossing通知。
The adaptive nature of the EFMCu technology allows the port to adapt itself to the changes in the copper environment, e.g., an impulse noise, alien crosstalk, or a micro-interruption may temporarily drop one or more PMEs in the aggregation group, causing a rate degradation of the aggregated EFMCu link. The dropped PMEs would then try to re-initialize, possibly at a lower rate than before, adjusting the rate to provide required target SNR margin.
EFMCu技术的自适应特性允许端口自身适应铜缆环境的变化，例如，脉冲噪声、外来串扰或微中断可能会暂时降低聚合组中的一个或多个PME，从而导致聚合EFMCu链路的速率降低。然后，丢弃的PME将尝试重新初始化，可能以比以前更低的速率，调整速率以提供所需的目标SNR裕度。
Generation of this notification is controlled by the
efmCuLowRateCrossingEnable object."
::= { efmCuPortNotifications 1 }
Generation of this notification is controlled by the
efmCuLowRateCrossingEnable object."
::= { efmCuPortNotifications 1 }
-- PCS Port group
--PCS端口组
efmCuPortConfTable OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPortConfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Table for Configuration of EFMCu 2BASE-TL/10PASS-TS (PCS)
Ports. Entries in this table MUST be maintained in a
persistent manner."
::= { efmCuPort 1 }
efmCuPortConfTable OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPortConfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Table for Configuration of EFMCu 2BASE-TL/10PASS-TS (PCS)
Ports. Entries in this table MUST be maintained in a
persistent manner."
::= { efmCuPort 1 }
efmCuPortConfEntry OBJECT-TYPE
SYNTAX EfmCuPortConfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the EFMCu Port Configuration table.
Each entry represents an EFMCu port indexed by the ifIndex.
Note that an EFMCu PCS port runs on top of a single
or multiple PME port(s), which are also indexed by ifIndex."
INDEX { ifIndex }
::= { efmCuPortConfTable 1 }
efmCuPortConfEntry OBJECT-TYPE
SYNTAX EfmCuPortConfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the EFMCu Port Configuration table.
Each entry represents an EFMCu port indexed by the ifIndex.
Note that an EFMCu PCS port runs on top of a single
or multiple PME port(s), which are also indexed by ifIndex."
INDEX { ifIndex }
::= { efmCuPortConfTable 1 }
EfmCuPortConfEntry ::=
SEQUENCE {
efmCuPAFAdminState INTEGER,
EfmCuPortConfEntry ::=
SEQUENCE {
efmCuPAFAdminState INTEGER,
efmCuPAFDiscoveryCode PhysAddress, efmCuAdminProfile EfmProfileIndexList, efmCuTargetDataRate Unsigned32, efmCuTargetSnrMgn Unsigned32, efmCuAdaptiveSpectra TruthValue, efmCuThreshLowRate Unsigned32, efmCuLowRateCrossingEnable TruthValue }
efmCuPAFDiscoveryCode PHYSADRESS、efmCuAdminProfile EfmProfileIndexList、efmCuTargetDataRate Unsigned32、efmCuTargetSnrMgn Unsigned32、EFMCUAAdaptiveSpectra TruthValue、efmCuThreshLowRate Unsigned32、EFMCUlowrateCrossingable TruthValue}
efmCuPAFAdminState OBJECT-TYPE
SYNTAX INTEGER {
enabled(1),
disabled(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Administrative (desired) state of the PAF of the EFMCu port
(PCS).
When 'disabled', PME aggregation will not be performed by the
PCS. No more than a single PME can be assigned to this PCS in
this case.
When 'enabled', PAF will be performed by the PCS when the link
is Up, even on a single attached PME, if PAF is supported.
efmCuPAFAdminState OBJECT-TYPE
SYNTAX INTEGER {
enabled(1),
disabled(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Administrative (desired) state of the PAF of the EFMCu port
(PCS).
When 'disabled', PME aggregation will not be performed by the
PCS. No more than a single PME can be assigned to this PCS in
this case.
When 'enabled', PAF will be performed by the PCS when the link
is Up, even on a single attached PME, if PAF is supported.
PCS ports incapable of supporting PAF SHALL return a value of 'disabled'. Attempts to 'enable' such ports SHALL be rejected.
无法支持PAF的PCS端口应返回“禁用”值。应拒绝“启用”此类端口的尝试。
A PAF 'enabled' port with multiple PMEs assigned cannot be 'disabled'. Attempts to 'disable' such port SHALL be rejected, until at most one PME is left assigned.
不能“禁用”分配了多个PME的PAF“已启用”端口。应拒绝“禁用”此类端口的尝试，直到最多分配一个PME。
Changing PAFAdminState is a traffic-disruptive operation and as such SHALL be done when the link is Down. Attempts to change this object SHALL be rejected if the link is Up or Initializing.
更改PAFAdminState是一种交通中断操作，因此应在链路断开时进行。如果链接已启动或正在初始化，则更改此对象的尝试将被拒绝。
This object maps to the Clause 30 attribute aPAFAdminState.
此对象映射到子句30属性aPAFAdminState。
If a Clause 45 MDIO Interface to the PCS is present, then this object maps to the PAF enable bit in the 10P/2B PCS control register.
如果存在到PCS的第45条MDIO接口，则该对象映射到10P/2B PCS控制寄存器中的PAF启用位。
This object MUST be maintained in a persistent manner."
REFERENCE
"[802.3ah] 61.2.2, 45.2.3.18.3"
::= { efmCuPortConfEntry 1 }
This object MUST be maintained in a persistent manner."
REFERENCE
"[802.3ah] 61.2.2, 45.2.3.18.3"
::= { efmCuPortConfEntry 1 }
efmCuPAFDiscoveryCode OBJECT-TYPE SYNTAX PhysAddress (SIZE(0|6)) MAX-ACCESS read-write STATUS current DESCRIPTION "PAF Discovery Code of the EFMCu port (PCS). A unique 6-octet code used by the Discovery function, when PAF is supported. PCS ports incapable of supporting PAF SHALL return a zero-length octet string on an attempt to read this object. An attempt to write to this object SHALL be rejected for such ports. This object MUST be instantiated for the -O subtype PCS before writing operations on the efmCuPAFRemoteDiscoveryCode (Set_if_Clear and Clear_if_Same) are performed by PMEs associated with the PCS. The initial value of this object for -R subtype ports after reset is all zeroes. For -R subtype ports, the value of this object cannot be changed directly. This value may be changed as a result of writing operation on the efmCuPAFRemoteDiscoveryCode object of remote PME of -O subtype, connected to one of the local PMEs associated with the PCS.
efmCuPAFDiscoveryCode对象类型语法PhysAddress（大小（0 | 6））MAX-ACCESS读写状态当前描述“EFMCu端口（PCS）的PAF发现代码”。当支持PAF时，发现功能使用的唯一6个八位字节代码。无法支持PAF的PCS端口在尝试读取此对象时应返回零长度八位字节字符串。对于此类端口，将拒绝尝试写入此对象。在写入操作之前，必须为-O子类型PCS实例化此对象efmCuPAFRemoteDiscoveryCode（清除时设置，如果清除时清除）由与PC关联的PME执行。重置后-R子类型端口的此对象的初始值均为零。对于-R子类型端口，此对象的值不能直接更改。此值可能会由于对连接到on的-O子类型远程PME的efmCuPAFRemoteDiscoveryCode对象的写入操作而更改e与PCS相关的本地PME。
Discovery MUST be performed when the link is Down. Attempts to change this object MUST be rejected (in case of SNMP with the error inconsistentValue), if the link is Up or Initializing.
必须在链路断开时执行发现。如果链接已启动或正在初始化，则必须拒绝更改此对象的尝试（如果SNMP的错误值不一致）。
The PAF Discovery Code maps to the local Discovery code
variable in PAF (note that it does not have a corresponding
Clause 45 register)."
REFERENCE
"[802.3ah] 61.2.2.8.3, 61.2.2.8.4, 45.2.6.6.1, 45.2.6.8,
61A.2"
::= { efmCuPortConfEntry 2 }
The PAF Discovery Code maps to the local Discovery code
variable in PAF (note that it does not have a corresponding
Clause 45 register)."
REFERENCE
"[802.3ah] 61.2.2.8.3, 61.2.2.8.4, 45.2.6.6.1, 45.2.6.8,
61A.2"
::= { efmCuPortConfEntry 2 }
efmCuAdminProfile OBJECT-TYPE SYNTAX EfmProfileIndexList MAX-ACCESS read-write STATUS current DESCRIPTION "Desired configuration profile(s), common for all PMEs in the EFMCu port. This object is a list of pointers to entries in either efmCuPme2BProfileTable or efmCuPme10PProfileTable, depending on the current operating SubType of the EFMCu port as indicated by efmCuPortSide.
efmCuAdminProfile对象类型语法EfmProfileIndexList MAX-ACCESS读写状态当前描述“所需配置配置文件”，对于EFMCu端口中的所有PME通用。此对象是指向efmCuPme2BProfileTable或efmCuPme10PProfileTable中条目的指针列表，具体取决于EFMCu端口的当前操作子类型，如efmCuPortSide所示。
The value of this object is a list of up to 6 indices of profiles. If this list consists of a single profile index, then all PMEs assigned to this EFMCu port SHALL be configured according to the profile referenced by that index, unless it is overwritten by a corresponding non-zero efmCuPmeAdminProfile instance, which takes precedence over efmCuAdminProfile. A list consisting of more than one index allows each PME in the port to be configured according to any profile specified in the list. By default, this object has a value of 0x01, referencing the 1st entry in efmCuPme2BProfileTable or efmCuPme10PProfileTable.
此对象的值是一个最多包含6个纵断面索引的列表。如果此列表由单个配置文件索引组成，则分配给此EFMCu端口的所有PME应根据该索引引用的配置文件进行配置，除非它被相应的非零efmCuPmeAdminProfile实例覆盖，该实例优先于EFMCUAAdminProfile。由多个索引组成的列表允许根据列表中指定的任何配置文件配置端口中的每个PME。默认情况下，此对象的值为0x01，引用efmCuPme2BProfileTable或efmCuPme10PProfileTable中的第一个条目。
This object is writable and readable for the -O subtype (2BaseTL-O or 10PassTS-O) EFMCu ports. It is irrelevant for the -R subtype (2BaseTL-R or 10PassTS-R) ports -- a zero-length octet string SHALL be returned on an attempt to read this object and an attempt to change this object MUST be rejected in this case.
对于-O子类型（2BaseTL-O或10PassTS-O）EFMCu端口，此对象可写且可读。它与-R子类型（2BaseTL-R或10PassTS-R）端口无关——在尝试读取此对象时，应返回零长度的八位字节字符串，在这种情况下，更改此对象的尝试必须被拒绝。
Note that the current operational profile value is available via the efmCuPmeOperProfile object.
请注意，当前操作配置文件值可通过efmCuPmeOperProfile对象获得。
Any modification of this object MUST be performed when the link is Down. Attempts to change this object MUST be rejected, if the link is Up or Initializing. Attempts to set this object to a list with a member value that is not the value of the index for an active entry in the corresponding profile table MUST be rejected.
此对象的任何修改都必须在链接关闭时执行。如果链接已启动或正在初始化，则必须拒绝更改此对象的尝试。必须拒绝尝试将此对象设置为成员值不是相应配置文件表中活动项的索引值的列表。
This object maps to the Clause 30 attribute aProfileSelect.
此对象映射到子句30属性aProfileSelect。
This object MUST be maintained in a persistent manner."
REFERENCE
"[802.3ah] 30.11.2.1.6"
DEFVAL { '01'H }
::= { efmCuPortConfEntry 3 }
This object MUST be maintained in a persistent manner."
REFERENCE
"[802.3ah] 30.11.2.1.6"
DEFVAL { '01'H }
::= { efmCuPortConfEntry 3 }
efmCuTargetDataRate OBJECT-TYPE SYNTAX Unsigned32(1..100000|999999) UNITS "Kbps" MAX-ACCESS read-write STATUS current DESCRIPTION "Desired EFMCu port 'net' (as seen across MII) Data Rate in Kbps, to be achieved during initialization, under spectral restrictions placed on each PME via efmCuAdminProfile or
efmCuTargetDataRate对象类型语法Unsigned32（1..100000 | 999999）单位“Kbps”最大访问读写状态当前描述“所需EFMCu端口‘净’（如MII中所示）数据速率，以Kbps为单位，在初始化期间通过efmCuAdminProfile或
efmCuPmeAdminProfile, with the desired SNR margin specified by efmCuTargetSnrMgn. In case of PAF, this object represents a sum of individual PME data rates, modified to compensate for fragmentation and 64/65-octet encapsulation overhead (e.g., target data rate of 10 Mbps SHALL allow lossless transmission of a full-duplex 10 Mbps Ethernet frame stream with minimal inter-frame gap).
efmCuPmeAdminProfile，具有efmCuTargetSnrMgn指定的所需SNR裕度。在PAF的情况下，该对象表示单个PME数据速率的总和，经过修改以补偿碎片和64/65八位字节封装开销（例如，10 Mbps的目标数据速率应允许以最小帧间间隙无损传输全双工10 Mbps以太网帧流）。
The value is limited above by 100 Mbps as this is the max burst rate across MII for EFMCu ports.
该值限制在100 Mbps以上，因为这是EFMCu端口跨MII的最大突发速率。
The value between 1 and 100000 indicates that the total data rate (ifSpeed) of the EFMCu port after initialization SHALL be equal to the target data rate or less, if the target data rate cannot be achieved under spectral restrictions specified by efmCuAdminProfile/efmCuPmeAdminProfile and with the desired SNR margin. In case the copper environment allows a higher total data rate to be achieved than that specified by the target, the excess capability SHALL be either converted to additional SNR margin or reclaimed by minimizing transmit power as controlled by efmCuAdaptiveSpectra.
如果在efmCuAdminProfile/efmCuPmeAdminProfile规定的频谱限制下无法达到目标数据速率，且具有所需的SNR裕度，则1到100000之间的值表示初始化后EFMCu端口的总数据速率（ifSpeed）应等于或小于目标数据速率。如果铜缆环境允许实现比目标指定的更高的总数据速率，则应将多余的容量转换为额外的SNR余量，或通过efmCuAdaptiveSpectra控制的最小化发射功率来回收。
The value of 999999 means that the target data rate is not fixed and SHALL be set to the maximum attainable rate during initialization (Best Effort), under specified spectral restrictions and with the desired SNR margin.
9999999的值表示目标数据速率不是固定的，并且应在指定的频谱限制下，在初始化期间（尽最大努力）设置为可达到的最大速率，并具有所需的SNR裕度。
This object is read-write for the -O subtype EFMCu ports (2BaseTL-O/10PassTS-O) and not available for the -R subtypes.
此对象对于-O子类型EFMCu端口（2BaseTL-O/10PassTS-O）是读写的，不适用于-R子类型。
Changing of the Target Data Rate MUST be performed when the link is Down. Attempts to change this object MUST be rejected (in case of SNMP with the error inconsistentValue), if the link is Up or Initializing.
必须在链路断开时更改目标数据速率。如果链接已启动或正在初始化，则必须拒绝更改此对象的尝试（如果SNMP的错误值不一致）。
Note that the current Data Rate of the EFMCu port is represented by the ifSpeed object of IF-MIB.
请注意，EFMCu端口的当前数据速率由IF-MIB的ifSpeed对象表示。
This object MUST be maintained in a persistent manner."
::= { efmCuPortConfEntry 4 }
This object MUST be maintained in a persistent manner."
::= { efmCuPortConfEntry 4 }
efmCuTargetSnrMgn OBJECT-TYPE SYNTAX Unsigned32(0..21) UNITS "dB" MAX-ACCESS read-write STATUS current DESCRIPTION "Desired EFMCu port SNR margin to be achieved on all PMEs
efmCuTargetSnrMgn对象类型语法Unsigned32（0..21）单元“dB”最大访问读写状态当前描述“所有PME上要达到的所需EFMCu端口SNR余量
assigned to the port, during initialization. (The SNR margin is the difference between the desired SNR and the actual SNR).
在初始化期间分配给端口。（信噪比裕度是期望信噪比和实际信噪比之间的差值）。
Note that 802.3ah recommends using a default target SNR margin of 5 dB for 2BASE-TL ports and 6 dB for 10PASS-TS ports in order to achieve a mean Bit Error Rate (BER) of 10^-7 at the PMA service interface.
请注意，802.3ah建议对2BASE-TL端口使用5 dB的默认目标SNR余量，对10PASS-TS端口使用6 dB的默认目标SNR余量，以便在PMA服务接口上实现10^-7的平均误码率（BER）。
This object is read-write for the -O subtype EFMCu ports (2BaseTL-O/10PassTS-O) and not available for the -R subtypes.
此对象对于-O子类型EFMCu端口（2BaseTL-O/10PassTS-O）是读写的，不适用于-R子类型。
Changing of the target SNR margin MUST be performed when the link is Down. Attempts to change this object MUST be rejected (in case of SNMP with the error inconsistentValue), if the link is Up or Initializing.
当链路断开时，必须改变目标SNR裕度。如果链接已启动或正在初始化，则必须拒绝更改此对象的尝试（如果SNMP的错误值不一致）。
Note that the current SNR margin of the PMEs comprising the EFMCu port is represented by efmCuPmeSnrMgn.
注意，包括EFMCu端口的pme的当前SNR裕度由efmCuPmeSnrMgn表示。
This object MUST be maintained in a persistent manner."
REFERENCE
"[802.3ah] 61.1.2"
::= { efmCuPortConfEntry 5 }
This object MUST be maintained in a persistent manner."
REFERENCE
"[802.3ah] 61.1.2"
::= { efmCuPortConfEntry 5 }
efmCuAdaptiveSpectra OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "Indicates how to utilize excess capacity when the copper environment allows a higher total data rate to be achieved than that specified by the efmCuTargetDataRate.
EFMCuadAdaptiveSpectra对象类型语法TruthValue MAX-ACCESS读写状态当前描述”表示当铜缆环境允许实现高于efmCuTargetDataRate指定的总数据速率时，如何利用过剩容量。
A value of true(1) indicates that the excess capability SHALL be reclaimed by minimizing transmit power, e.g., using higher constellations and Power Back-Off, in order to reduce interference to other copper pairs in the binder and the adverse impact to link/system performance.
真（1）值表示应通过最小化发射功率（例如，使用更高的星座和功率回退）回收多余容量，以减少对绑定器中其他铜对的干扰以及对链路/系统性能的不利影响。
A value of false(2) indicates that the excess capability SHALL be converted to additional SNR margin and spread evenly across all active PMEs assigned to the (PCS) port, to increase link robustness.
false（2）值表示多余的容量应转换为额外的SNR裕度，并均匀分布在分配给（PCS）端口的所有活动PME上，以提高链路鲁棒性。
This object is read-write for the -O subtype EFMCu ports (2BaseTL-O/10PassTS-O) and not available for the -R subtypes.
此对象对于-O子类型EFMCu端口（2BaseTL-O/10PassTS-O）是读写的，不适用于-R子类型。
Changing of this object MUST be performed when the link is
必须在链接打开时更改此对象
Down. Attempts to change this object MUST be rejected (in case of SNMP with the error inconsistentValue), if the link is Up or Initializing.
向下如果链接已启动或正在初始化，则必须拒绝更改此对象的尝试（如果SNMP的错误值不一致）。
This object MUST be maintained in a persistent manner."
::= { efmCuPortConfEntry 6 }
This object MUST be maintained in a persistent manner."
::= { efmCuPortConfEntry 6 }
efmCuThreshLowRate OBJECT-TYPE SYNTAX Unsigned32(1..100000) UNITS "Kbps" MAX-ACCESS read-write STATUS current DESCRIPTION "This object configures the EFMCu port low-rate crossing alarm threshold. When the current value of ifSpeed for this port reaches/drops below or exceeds this threshold, an efmCuLowRateCrossing notification MAY be generated if enabled by efmCuLowRateCrossingEnable.
efmCuThreshLowRate对象类型语法Unsigned32（1..100000）单位“Kbps”最大访问读写状态当前说明“此对象配置EFMCu端口低速率穿越报警阈值。当此端口的ifSpeed当前值达到/低于或超过此阈值时，如果efmCuLowRateCrossingEnable启用，则可能会生成efmCuLowRateCrossing通知。
This object is read-write for the -O subtype EFMCu ports (2BaseTL-O/10PassTS-O) and not available for the -R subtypes.
此对象对于-O子类型EFMCu端口（2BaseTL-O/10PassTS-O）是读写的，不适用于-R子类型。
This object MUST be maintained in a persistent manner."
::= { efmCuPortConfEntry 7 }
This object MUST be maintained in a persistent manner."
::= { efmCuPortConfEntry 7 }
efmCuLowRateCrossingEnable OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "Indicates whether efmCuLowRateCrossing notifications should be generated for this interface.
efmCuLowRateCrossingEnable对象类型语法TruthValue MAX-ACCESS读写状态当前描述”指示是否应为此接口生成efmCuLowRateCrossing通知。
A value of true(1) indicates that efmCuLowRateCrossing notification is enabled. A value of false(2) indicates that the notification is disabled.
值为true（1）表示已启用EFMCULOWRATECROSING通知。值false（2）表示通知已禁用。
This object is read-write for the -O subtype EFMCu ports (2BaseTL-O/10PassTS-O) and not available for the -R subtypes.
此对象对于-O子类型EFMCu端口（2BaseTL-O/10PassTS-O）是读写的，不适用于-R子类型。
This object MUST be maintained in a persistent manner."
::= { efmCuPortConfEntry 8 }
This object MUST be maintained in a persistent manner."
::= { efmCuPortConfEntry 8 }
efmCuPortCapabilityTable OBJECT-TYPE SYNTAX SEQUENCE OF EfmCuPortCapabilityEntry MAX-ACCESS not-accessible STATUS current
efmCuPortCapabilityTable对象类型EfmCuPortCapabilityEntry的语法序列MAX-ACCESS不可访问状态当前
DESCRIPTION
"Table for Capabilities of EFMCu 2BASE-TL/10PASS-TS (PCS)
Ports. Entries in this table MUST be maintained in a
persistent manner"
::= { efmCuPort 2 }
DESCRIPTION
"Table for Capabilities of EFMCu 2BASE-TL/10PASS-TS (PCS)
Ports. Entries in this table MUST be maintained in a
persistent manner"
::= { efmCuPort 2 }
efmCuPortCapabilityEntry OBJECT-TYPE
SYNTAX EfmCuPortCapabilityEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the EFMCu Port Capability table.
Each entry represents an EFMCu port indexed by the ifIndex.
Note that an EFMCu PCS port runs on top of a single
or multiple PME port(s), which are also indexed by ifIndex."
INDEX { ifIndex }
::= { efmCuPortCapabilityTable 1 }
efmCuPortCapabilityEntry OBJECT-TYPE
SYNTAX EfmCuPortCapabilityEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the EFMCu Port Capability table.
Each entry represents an EFMCu port indexed by the ifIndex.
Note that an EFMCu PCS port runs on top of a single
or multiple PME port(s), which are also indexed by ifIndex."
INDEX { ifIndex }
::= { efmCuPortCapabilityTable 1 }
EfmCuPortCapabilityEntry ::=
SEQUENCE {
efmCuPAFSupported TruthValue,
efmCuPeerPAFSupported EfmTruthValueOrUnknown,
efmCuPAFCapacity Unsigned32,
efmCuPeerPAFCapacity Unsigned32
}
EfmCuPortCapabilityEntry ::=
SEQUENCE {
efmCuPAFSupported TruthValue,
efmCuPeerPAFSupported EfmTruthValueOrUnknown,
efmCuPAFCapacity Unsigned32,
efmCuPeerPAFCapacity Unsigned32
}
efmCuPAFSupported OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "PME Aggregation Function (PAF) capability of the EFMCu port (PCS). This object has a value of true(1) when the PCS can perform PME aggregation on the available PMEs. Ports incapable of PAF SHALL return a value of false(2).
efmCuPAFSupported对象类型语法TruthValue MAX-ACCESS只读状态当前描述“EFMCu端口（PCS）的PME聚合功能（PAF）功能。当PCS可以在可用PME上执行PME聚合时，此对象的值为true（1）。无法PAF的端口应返回false（2）。
This object maps to the Clause 30 attribute aPAFSupported.
此对象映射到第30条属性aPAFSupported。
If a Clause 45 MDIO Interface to the PCS is present,
then this object maps to the PAF available bit in the
10P/2B capability register."
REFERENCE
"[802.3ah] 61.2.2, 30.11.1.1.4, 45.2.3.17.1"
::= { efmCuPortCapabilityEntry 1 }
If a Clause 45 MDIO Interface to the PCS is present,
then this object maps to the PAF available bit in the
10P/2B capability register."
REFERENCE
"[802.3ah] 61.2.2, 30.11.1.1.4, 45.2.3.17.1"
::= { efmCuPortCapabilityEntry 1 }
efmCuPeerPAFSupported OBJECT-TYPE SYNTAX EfmTruthValueOrUnknown
EFMCupeerpafs支持的对象类型语法EfmTruthValueOrUnknown
MAX-ACCESS read-only STATUS current DESCRIPTION "PME Aggregation Function (PAF) capability of the EFMCu port (PCS) link partner. This object has a value of true(1) when the remote PCS can perform PME aggregation on its available PMEs. Ports whose peers are incapable of PAF SHALL return a value of false(2). Ports whose peers cannot be reached because of the link state SHALL return a value of unknown(0).
MAX-ACCESS只读状态当前描述“EFMCu端口（PCS）链路伙伴的PME聚合功能（PAF）能力。当远程PC可以对其可用PME执行PME聚合时，此对象的值为true（1）。对等方不能进行PAF的端口应返回值false（2）.由于链路状态而无法访问对等端口的端口应返回未知值（0）。
This object maps to the Clause 30 attribute aRemotePAFSupported.
此对象映射到子句30属性aRemotePAFSupported。
If a Clause 45 MDIO Interface to the PCS is present, then
this object maps to the Remote PAF supported bit in the
10P/2B capability register."
REFERENCE
"[802.3ah] 61.2.2, 30.11.1.1.9, 45.2.3.17.2"
::= { efmCuPortCapabilityEntry 2 }
If a Clause 45 MDIO Interface to the PCS is present, then
this object maps to the Remote PAF supported bit in the
10P/2B capability register."
REFERENCE
"[802.3ah] 61.2.2, 30.11.1.1.9, 45.2.3.17.2"
::= { efmCuPortCapabilityEntry 2 }
efmCuPAFCapacity OBJECT-TYPE SYNTAX Unsigned32 (1..32) MAX-ACCESS read-only STATUS current DESCRIPTION "Number of PMEs that can be aggregated by the local PAF. The number of PMEs currently assigned to a particular EFMCu port (efmCuNumPMEs) is never greater than efmCuPAFCapacity.
efmCuPAFCapacity对象类型语法Unsigned32（1..32）MAX-ACCESS只读状态当前描述“可由本地PAF聚合的PME数。当前分配给特定EFMCu端口（efmCuNumPMEs）的PME数永远不会大于efmCuPAFCapacity。
This object maps to the Clause 30 attribute
aLocalPAFCapacity."
REFERENCE
"[802.3ah] 61.2.2, 30.11.1.1.6"
::= { efmCuPortCapabilityEntry 3 }
This object maps to the Clause 30 attribute
aLocalPAFCapacity."
REFERENCE
"[802.3ah] 61.2.2, 30.11.1.1.6"
::= { efmCuPortCapabilityEntry 3 }
efmCuPeerPAFCapacity OBJECT-TYPE SYNTAX Unsigned32 (0|1..32) MAX-ACCESS read-only STATUS current DESCRIPTION "Number of PMEs that can be aggregated by the PAF of the peer PHY (PCS port). A value of 0 is returned when peer PAF capacity is unknown (peer cannot be reached).
EFMCUPEERPAFCAPITY对象类型语法Unsigned32（0 | 1..32）MAX-ACCESS只读状态当前描述“可由对等PHY（PCS端口）的PAF聚合的PME数。当对等PAF容量未知（无法达到对等PAF）时，返回值0。
This object maps to the Clause 30 attribute
aRemotePAFCapacity."
REFERENCE
"[802.3ah] 61.2.2, 30.11.1.1.10"
::= { efmCuPortCapabilityEntry 4 }
This object maps to the Clause 30 attribute
aRemotePAFCapacity."
REFERENCE
"[802.3ah] 61.2.2, 30.11.1.1.10"
::= { efmCuPortCapabilityEntry 4 }
efmCuPortStatusTable OBJECT-TYPE SYNTAX SEQUENCE OF EfmCuPortStatusEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table provides overall status information of EFMCu 2BASE-TL/10PASS-TS ports, complementing the generic status information from the ifTable of IF-MIB and ifMauTable of MAU-MIB. Additional status information about connected PMEs is available from the efmCuPmeStatusTable.
efmCuPortStatusTable EfmCuPortStatusEntry的对象类型语法序列MAX-ACCESS不可访问状态当前描述“此表提供了EFMCu 2BASE-TL/10PASS-TS端口的总体状态信息，补充了IF-MIB的ifTable和MAU-MIB的ifMauTable中的通用状态信息。有关连接的PME的其他状态信息可从efmCuPmeStatusTable获得。
This table contains live data from the equipment. As such,
it is NOT persistent."
::= { efmCuPort 3 }
This table contains live data from the equipment. As such,
it is NOT persistent."
::= { efmCuPort 3 }
efmCuPortStatusEntry OBJECT-TYPE
SYNTAX EfmCuPortStatusEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the EFMCu Port Status table.
Each entry represents an EFMCu port indexed by the ifIndex.
Note that an EFMCu PCS port runs on top of a single
or multiple PME port(s), which are also indexed by ifIndex."
INDEX { ifIndex }
::= { efmCuPortStatusTable 1 }
efmCuPortStatusEntry OBJECT-TYPE
SYNTAX EfmCuPortStatusEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the EFMCu Port Status table.
Each entry represents an EFMCu port indexed by the ifIndex.
Note that an EFMCu PCS port runs on top of a single
or multiple PME port(s), which are also indexed by ifIndex."
INDEX { ifIndex }
::= { efmCuPortStatusTable 1 }
EfmCuPortStatusEntry ::=
SEQUENCE {
efmCuFltStatus BITS,
efmCuPortSide INTEGER,
efmCuNumPMEs Unsigned32,
efmCuPAFInErrors Counter32,
efmCuPAFInSmallFragments Counter32,
efmCuPAFInLargeFragments Counter32,
efmCuPAFInBadFragments Counter32,
efmCuPAFInLostFragments Counter32,
efmCuPAFInLostStarts Counter32,
efmCuPAFInLostEnds Counter32,
efmCuPAFInOverflows Counter32
}
EfmCuPortStatusEntry ::=
SEQUENCE {
efmCuFltStatus BITS,
efmCuPortSide INTEGER,
efmCuNumPMEs Unsigned32,
efmCuPAFInErrors Counter32,
efmCuPAFInSmallFragments Counter32,
efmCuPAFInLargeFragments Counter32,
efmCuPAFInBadFragments Counter32,
efmCuPAFInLostFragments Counter32,
efmCuPAFInLostStarts Counter32,
efmCuPAFInLostEnds Counter32,
efmCuPAFInOverflows Counter32
}
efmCuFltStatus OBJECT-TYPE
SYNTAX BITS {
noPeer(0),
peerPowerLoss(1),
pmeSubTypeMismatch(2),
lowRate(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"EFMCu (PCS) port Fault Status. This is a bitmap of possible
conditions. The various bit positions are:
noPeer - the peer PHY cannot be reached (e.g.,
no PMEs attached, all PMEs are Down,
etc.). More info is available in
efmCuPmeFltStatus.
peerPowerLoss - the peer PHY has indicated impending
unit failure due to loss of local
power ('Dying Gasp').
pmeSubTypeMismatch - local PMEs in the aggregation group
are not of the same subtype, e.g.,
some PMEs in the local device are -O
while others are -R subtype.
lowRate - ifSpeed of the port reached or dropped
below efmCuThreshLowRate.
efmCuFltStatus OBJECT-TYPE
SYNTAX BITS {
noPeer(0),
peerPowerLoss(1),
pmeSubTypeMismatch(2),
lowRate(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"EFMCu (PCS) port Fault Status. This is a bitmap of possible
conditions. The various bit positions are:
noPeer - the peer PHY cannot be reached (e.g.,
no PMEs attached, all PMEs are Down,
etc.). More info is available in
efmCuPmeFltStatus.
peerPowerLoss - the peer PHY has indicated impending
unit failure due to loss of local
power ('Dying Gasp').
pmeSubTypeMismatch - local PMEs in the aggregation group
are not of the same subtype, e.g.,
some PMEs in the local device are -O
while others are -R subtype.
lowRate - ifSpeed of the port reached or dropped
below efmCuThreshLowRate.
This object is intended to supplement the ifOperStatus object in IF-MIB and ifMauMediaAvailable in MAU-MIB.
此对象旨在补充IF-MIB中的ifOperaStatus对象和MAU-MIB中可用的ifMaumedia对象。
Additional information is available via the efmCuPmeFltStatus
object for each PME in the aggregation group (single PME if
PAF is disabled)."
REFERENCE
"IF-MIB, ifOperStatus; MAU-MIB, ifMauMediaAvailable;
efmCuPmeFltStatus"
::= { efmCuPortStatusEntry 1 }
Additional information is available via the efmCuPmeFltStatus
object for each PME in the aggregation group (single PME if
PAF is disabled)."
REFERENCE
"IF-MIB, ifOperStatus; MAU-MIB, ifMauMediaAvailable;
efmCuPmeFltStatus"
::= { efmCuPortStatusEntry 1 }
efmCuPortSide OBJECT-TYPE
SYNTAX INTEGER {
subscriber(1),
office(2),
unknown(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"EFM port mode of operation (subtype).
The value of 'subscriber' indicates that the port is
efmCuPortSide OBJECT-TYPE
SYNTAX INTEGER {
subscriber(1),
office(2),
unknown(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"EFM port mode of operation (subtype).
The value of 'subscriber' indicates that the port is
designated as '-R' subtype (all PMEs assigned to this port are of subtype '-R'). The value of the 'office' indicates that the port is designated as '-O' subtype (all PMEs assigned to this port are of subtype '-O'). The value of 'unknown' indicates that the port has no assigned PMEs yet or that the assigned PMEs are not of the same side (subTypePMEMismatch).
指定为'-R'子类型（分配给此端口的所有PME都属于'-R'子类型）。“office”的值表示端口被指定为“-O”子类型（分配给此端口的所有PME都是“-O”子类型）。值“unknown”表示端口尚未分配PME，或者分配的PME不在同一侧（子类型PME匹配）。
This object partially maps to the Clause 30 attribute
aPhyEnd."
REFERENCE
"[802.3ah] 61.1, 30.11.1.1.2"
::= { efmCuPortStatusEntry 2 }
This object partially maps to the Clause 30 attribute
aPhyEnd."
REFERENCE
"[802.3ah] 61.1, 30.11.1.1.2"
::= { efmCuPortStatusEntry 2 }
efmCuNumPMEs OBJECT-TYPE SYNTAX Unsigned32 (0..32) MAX-ACCESS read-only STATUS current DESCRIPTION "The number of PMEs that is currently aggregated by the local PAF (assigned to the EFMCu port using the ifStackTable). This number is never greater than efmCuPAFCapacity.
efmCuNumPMEs对象类型语法Unsigned32（0..32）MAX-ACCESS只读状态current DESCRIPTION“当前由本地PAF聚合（使用ifStackTable分配给EFMCu端口）的PME数。此数永远不会大于efmCuPAFCapacity。
This object SHALL be automatically incremented or decremented
when a PME is added or deleted to/from the EFMCu port using
the ifStackTable."
REFERENCE
"[802.3ah] 61.2.2, 30.11.1.1.6"
::= { efmCuPortStatusEntry 3 }
This object SHALL be automatically incremented or decremented
when a PME is added or deleted to/from the EFMCu port using
the ifStackTable."
REFERENCE
"[802.3ah] 61.2.2, 30.11.1.1.6"
::= { efmCuPortStatusEntry 3 }
efmCuPAFInErrors OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of fragments that have been received across the gamma interface with RxErr asserted and discarded. This read-only counter is inactive (not incremented) when the PAF is unsupported or disabled. Upon disabling the PAF, the counter retains its previous value.
efmCuPAFInErrors对象类型语法计数器32 MAX-ACCESS只读状态当前描述“已通过gamma接口接收并断言并丢弃RXER的片段数。此只读计数器处于非活动状态（未递增）不支持或禁用PAF时。禁用PAF后，计数器将保留其以前的值。
If a Clause 45 MDIO Interface to the PCS is present, then this object maps to the 10P/2B PAF RX error register.
如果存在到PCS的第45条MDIO接口，则该对象映射到10P/2B PAF RX错误寄存器。
Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime,
该计数器值的不连续性可能在管理系统重新初始化时发生，也可能在IFCounterInterruptionTime值指示的其他时间发生，
defined in IF-MIB."
REFERENCE
"[802.3ah] 45.2.3.21"
::= { efmCuPortStatusEntry 4 }
defined in IF-MIB."
REFERENCE
"[802.3ah] 45.2.3.21"
::= { efmCuPortStatusEntry 4 }
efmCuPAFInSmallFragments OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of fragments smaller than minFragmentSize (64 bytes) that have been received across the gamma interface and discarded. This read-only counter is inactive when the PAF is unsupported or disabled. Upon disabling the PAF, the counter retains its previous value.
efmCuPAFInSmallFragments对象类型语法计数器32 MAX-ACCESS只读状态当前说明“小于minFragmentSize（64字节）的片段数”已通过gamma接口接收并丢弃的。当PAF不受支持或禁用时，此只读计数器处于非活动状态。禁用PAF后，计数器保留其以前的值。
If a Clause 45 MDIO Interface to the PCS is present, then this object maps to the 10P/2B PAF small fragments register.
如果存在到PCS的第45条MDIO接口，则该对象映射到10P/2B PAF小碎片寄存器。
Discontinuities in the value of this counter can occur at
re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime,
defined in IF-MIB."
REFERENCE
"[802.3ah] 45.2.3.22"
::= { efmCuPortStatusEntry 5 }
Discontinuities in the value of this counter can occur at
re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime,
defined in IF-MIB."
REFERENCE
"[802.3ah] 45.2.3.22"
::= { efmCuPortStatusEntry 5 }
efmCuPAFInLargeFragments OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of fragments larger than maxFragmentSize (512 bytes) that have been received across the gamma interface and discarded. This read-only counter is inactive when the PAF is unsupported or disabled. Upon disabling the PAF, the counter retains its previous value.
efmCuPAFInLargeFragments对象类型语法计数器32 MAX-ACCESS只读状态当前说明“大于maxFragmentSize（512字节）的片段数”已通过gamma接口接收并丢弃的。当PAF不受支持或禁用时，此只读计数器处于非活动状态。禁用PAF后，计数器保留其以前的值。
If a Clause 45 MDIO Interface to the PCS is present, then this object maps to the 10P/2B PAF large fragments register.
如果存在到PCS的第45条MDIO接口，则该对象映射到10P/2B PAF大片段寄存器。
Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime, defined in IF-MIB." REFERENCE
在重新初始化管理系统时，以及在IF-MIB中定义的IFCOUNTERINTERFACTIONYTIME值指示的其他时间，该计数器的值可能会出现不连续。“参考
"[802.3ah] 45.2.3.23"
::= { efmCuPortStatusEntry 6 }
"[802.3ah] 45.2.3.23"
::= { efmCuPortStatusEntry 6 }
efmCuPAFInBadFragments OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of fragments that do not fit into the sequence expected by the frame assembly function and that have been received across the gamma interface and discarded (the frame buffer is flushed to the next valid frame start). This read-only counter is inactive when the PAF is unsupported or disabled. Upon disabling the PAF, the counter retains its previous value.
efmCuPAFInBadFragments对象类型语法计数器32 MAX-ACCESS只读状态当前描述“不符合帧汇编函数预期序列且已通过gamma接口接收并丢弃的片段数（帧缓冲区刷新到下一个有效帧开始）。当PAF不受支持或被禁用时，此只读计数器处于非活动状态。禁用PAF后，计数器将保留其以前的值。
If a Clause 45 MDIO Interface to the PCS is present, then this object maps to the 10P/2B PAF bad fragments register.
如果存在到PCS的第45条MDIO接口，则该对象映射到10P/2B PAF坏片段寄存器。
Discontinuities in the value of this counter can occur at
re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime,
defined in IF-MIB."
REFERENCE
"[802.3ah] 45.2.3.25"
::= { efmCuPortStatusEntry 7 }
Discontinuities in the value of this counter can occur at
re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime,
defined in IF-MIB."
REFERENCE
"[802.3ah] 45.2.3.25"
::= { efmCuPortStatusEntry 7 }
efmCuPAFInLostFragments OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of gaps in the sequence of fragments that have been received across the gamma interface (the frame buffer is flushed to the next valid frame start, when fragment/fragments expected by the frame assembly function is/are not received). This read-only counter is inactive when the PAF is unsupported or disabled. Upon disabling the PAF, the counter retains its previous value.
efmCuPAFInLostFragments对象类型语法计数器32 MAX-ACCESS只读状态当前描述“已通过gamma接口接收的片段序列中的间隙数（当帧汇编函数预期的片段/片段被接收/未接收时，帧缓冲区被刷新到下一个有效帧开始）。当PAF不受支持或被禁用时，此只读计数器处于非活动状态。禁用PAF后，计数器将保留其以前的值。
If a Clause 45 MDIO Interface to the PCS is present, then this object maps to the 10P/2B PAF lost fragment register.
如果存在到PCS的第45条MDIO接口，则该对象映射到10P/2B PAF丢失片段寄存器。
Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime, defined in IF-MIB." REFERENCE
在重新初始化管理系统时，以及在IF-MIB中定义的IFCOUNTERINTERFACTIONYTIME值指示的其他时间，该计数器的值可能会出现不连续。“参考
"[802.3ah] 45.2.3.26"
::= { efmCuPortStatusEntry 8 }
"[802.3ah] 45.2.3.26"
::= { efmCuPortStatusEntry 8 }
efmCuPAFInLostStarts OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of missing StartOfPacket indicators expected by the frame assembly function. This read-only counter is inactive when the PAF is unsupported or disabled. Upon disabling the PAF, the counter retains its previous value.
efmCuPAFInLostStarts对象类型语法计数器32 MAX-ACCESS只读状态当前描述“帧汇编函数预期的缺少StartOfPacket指示器的数量。当PAF不受支持或禁用时，此只读计数器处于非活动状态。禁用PAF后，计数器保留其以前的值。
If a Clause 45 MDIO Interface to the PCS is present, then this object maps to the 10P/2B PAF lost start of fragment register.
如果存在到PCS的第45条MDIO接口，则该对象映射到10P/2B PAF丢失的片段起始寄存器。
Discontinuities in the value of this counter can occur at
re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime,
defined in IF-MIB."
REFERENCE
"[802.3ah] 45.2.3.27"
::= { efmCuPortStatusEntry 9 }
Discontinuities in the value of this counter can occur at
re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime,
defined in IF-MIB."
REFERENCE
"[802.3ah] 45.2.3.27"
::= { efmCuPortStatusEntry 9 }
efmCuPAFInLostEnds OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of missing EndOfPacket indicators expected by the frame assembly function. This read-only counter is inactive when the PAF is unsupported or disabled. Upon disabling the PAF, the counter retains its previous value.
efmCuPAFInLostEnds对象类型语法计数器32 MAX-ACCESS只读状态当前说明“帧汇编函数预期缺少的EndofPack指示符的数量。当PAF不受支持或禁用时，此只读计数器处于非活动状态。禁用PAF后，计数器保留其以前的值。
If a Clause 45 MDIO Interface to the PCS is present, then this object maps to the 10P/2B PAF lost start of fragment register.
如果存在到PCS的第45条MDIO接口，则该对象映射到10P/2B PAF丢失的片段起始寄存器。
Discontinuities in the value of this counter can occur at
re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime,
defined in IF-MIB."
REFERENCE
"[802.3ah] 45.2.3.28"
::= { efmCuPortStatusEntry 10 }
Discontinuities in the value of this counter can occur at
re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime,
defined in IF-MIB."
REFERENCE
"[802.3ah] 45.2.3.28"
::= { efmCuPortStatusEntry 10 }
efmCuPAFInOverflows OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of fragments, received across the gamma interface and discarded, which would have caused the frame assembly buffer to overflow. This read-only counter is inactive when the PAF is unsupported or disabled. Upon disabling the PAF, the counter retains its previous value.
efmCuPAFInOverflows对象类型语法计数器32 MAX-ACCESS只读状态当前说明“通过gamma接口接收并丢弃的碎片数，这将导致帧程序集缓冲区溢出。当PAF不受支持或禁用时，此只读计数器处于非活动状态。禁用PAF后，计数器将保留其以前的值。
If a Clause 45 MDIO Interface to the PCS is present, then this object maps to the 10P/2B PAF overflow register.
如果存在到PCS的第45条MDIO接口，则该对象映射到10P/2B PAF溢出寄存器。
Discontinuities in the value of this counter can occur at
re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime,
defined in IF-MIB."
REFERENCE
"[802.3ah] 45.2.3.24"
::= { efmCuPortStatusEntry 11 }
Discontinuities in the value of this counter can occur at
re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime,
defined in IF-MIB."
REFERENCE
"[802.3ah] 45.2.3.24"
::= { efmCuPortStatusEntry 11 }
-- PME Notifications Group
--PME通知组
efmCuPmeNotifications OBJECT IDENTIFIER ::= { efmCuPme 0 }
efmCuPmeNotifications OBJECT IDENTIFIER ::= { efmCuPme 0 }
efmCuPmeLineAtnCrossing NOTIFICATION-TYPE
OBJECTS {
efmCuPmeLineAtn,
efmCuPmeThreshLineAtn
}
STATUS current
DESCRIPTION
"This notification indicates that the loop attenuation
threshold (as per the efmCuPmeThreshLineAtn
value) has been reached/exceeded for the 2BASE-TL/10PASS-TS
PME. This notification MAY be sent on the crossing event in
both directions: from normal to exceeded and from exceeded
to normal.
efmCuPmeLineAtnCrossing NOTIFICATION-TYPE
OBJECTS {
efmCuPmeLineAtn,
efmCuPmeThreshLineAtn
}
STATUS current
DESCRIPTION
"This notification indicates that the loop attenuation
threshold (as per the efmCuPmeThreshLineAtn
value) has been reached/exceeded for the 2BASE-TL/10PASS-TS
PME. This notification MAY be sent on the crossing event in
both directions: from normal to exceeded and from exceeded
to normal.
It is RECOMMENDED that a small debouncing period of 2.5 sec, between the detection of the condition and the notification, is implemented to prevent intermittent notifications from being sent.
建议在检测到状况和通知之间实施2.5秒的小去抖动周期，以防止发送间歇性通知。
Generation of this notification is controlled by the efmCuPmeLineAtnCrossingEnable object."
此通知的生成由efmCuPmeLineAtnCrossingEnable对象控制。“
::= { efmCuPmeNotifications 1 }
::= { efmCuPmeNotifications 1 }
efmCuPmeSnrMgnCrossing NOTIFICATION-TYPE
OBJECTS {
efmCuPmeSnrMgn,
efmCuPmeThreshSnrMgn
}
STATUS current
DESCRIPTION
"This notification indicates that the SNR margin threshold
(as per the efmCuPmeThreshSnrMgn value) has been
reached/exceeded for the 2BASE-TL/10PASS-TS PME.
This notification MAY be sent on the crossing event in
both directions: from normal to exceeded and from exceeded
to normal.
efmCuPmeSnrMgnCrossing NOTIFICATION-TYPE
OBJECTS {
efmCuPmeSnrMgn,
efmCuPmeThreshSnrMgn
}
STATUS current
DESCRIPTION
"This notification indicates that the SNR margin threshold
(as per the efmCuPmeThreshSnrMgn value) has been
reached/exceeded for the 2BASE-TL/10PASS-TS PME.
This notification MAY be sent on the crossing event in
both directions: from normal to exceeded and from exceeded
to normal.
It is RECOMMENDED that a small debouncing period of 2.5 sec, between the detection of the condition and the notification, is implemented to prevent intermittent notifications from being sent.
建议在检测到状况和通知之间实施2.5秒的小去抖动周期，以防止发送间歇性通知。
Generation of this notification is controlled by the
efmCuPmeSnrMgnCrossingEnable object."
::= { efmCuPmeNotifications 2 }
Generation of this notification is controlled by the
efmCuPmeSnrMgnCrossingEnable object."
::= { efmCuPmeNotifications 2 }
efmCuPmeDeviceFault NOTIFICATION-TYPE
OBJECTS {
efmCuPmeFltStatus
}
STATUS current
DESCRIPTION
"This notification indicates that a fault in the PME has been
detected by a vendor-specific diagnostic or a self-test.
efmCuPmeDeviceFault NOTIFICATION-TYPE
OBJECTS {
efmCuPmeFltStatus
}
STATUS current
DESCRIPTION
"This notification indicates that a fault in the PME has been
detected by a vendor-specific diagnostic or a self-test.
Generation of this notification is controlled by the
efmCuPmeDeviceFaultEnable object."
::= { efmCuPmeNotifications 3 }
Generation of this notification is controlled by the
efmCuPmeDeviceFaultEnable object."
::= { efmCuPmeNotifications 3 }
efmCuPmeConfigInitFailure NOTIFICATION-TYPE
OBJECTS {
efmCuPmeFltStatus,
efmCuAdminProfile,
efmCuPmeAdminProfile
}
STATUS current
DESCRIPTION
"This notification indicates that PME initialization has
failed, due to inability of the PME link to achieve the
efmCuPmeConfigInitFailure NOTIFICATION-TYPE
OBJECTS {
efmCuPmeFltStatus,
efmCuAdminProfile,
efmCuPmeAdminProfile
}
STATUS current
DESCRIPTION
"This notification indicates that PME initialization has
failed, due to inability of the PME link to achieve the
requested configuration profile.
请求的配置配置文件。
Generation of this notification is controlled by the
efmCuPmeConfigInitFailEnable object."
::= { efmCuPmeNotifications 4 }
Generation of this notification is controlled by the
efmCuPmeConfigInitFailEnable object."
::= { efmCuPmeNotifications 4 }
efmCuPmeProtocolInitFailure NOTIFICATION-TYPE
OBJECTS {
efmCuPmeFltStatus,
efmCuPmeOperSubType
}
STATUS current
DESCRIPTION
"This notification indicates that the peer PME was using
an incompatible protocol during initialization.
efmCuPmeProtocolInitFailure NOTIFICATION-TYPE
OBJECTS {
efmCuPmeFltStatus,
efmCuPmeOperSubType
}
STATUS current
DESCRIPTION
"This notification indicates that the peer PME was using
an incompatible protocol during initialization.
Generation of this notification is controlled by the
efmCuPmeProtocolInitFailEnable object."
::= { efmCuPmeNotifications 5 }
Generation of this notification is controlled by the
efmCuPmeProtocolInitFailEnable object."
::= { efmCuPmeNotifications 5 }
-- The PME group
--PME集团
efmCuPmeConfTable OBJECT-TYPE SYNTAX SEQUENCE OF EfmCuPmeConfEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Table for Configuration of common aspects for EFMCu 2BASE-TL/10PASS-TS PME ports (modems). Configuration of aspects specific to 2BASE-TL or 10PASS-TS PME types is represented in efmCuPme2BConfTable and efmCuPme10PConfTable, respectively.
efmCuPmeConfTable EfmCuPmeConfEntry MAX-ACCESS的对象类型语法序列不可访问状态当前描述“EFMCu 2BASE-TL/10PASS-TS PME端口（调制解调器）通用配置表”.特定于2BASE-TL或10PASS-TS PME类型的方面配置分别在EFMCUPME2BContable和efmCuPme10PConfTable中表示。
Entries in this table MUST be maintained in a persistent
manner."
::= { efmCuPme 1 }
Entries in this table MUST be maintained in a persistent
manner."
::= { efmCuPme 1 }
efmCuPmeConfEntry OBJECT-TYPE SYNTAX EfmCuPmeConfEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the EFMCu PME Configuration table. Each entry represents common aspects of an EFMCu PME port indexed by the ifIndex. Note that an EFMCu PME port can be stacked below a single PCS port, also indexed by ifIndex, possibly together with other PME ports if PAF is enabled." INDEX { ifIndex }
efmCuPmeConfEntry对象类型语法efmCuPmeConfEntry MAX-ACCESS不可访问状态当前说明“EFMCu PME配置表中的条目。每个条目表示ifIndex索引的EFMCu PME端口的公共方面。请注意，如果启用PAF，EFMCu PME端口可以堆叠在单个PCS端口下方，也可以由ifIndex索引，如果启用PAF，则可能与其他PME端口一起。“索引{ifIndex}”
::= { efmCuPmeConfTable 1 }
::= { efmCuPmeConfTable 1 }
EfmCuPmeConfEntry ::=
SEQUENCE {
efmCuPmeAdminSubType INTEGER,
efmCuPmeAdminProfile EfmProfileIndexOrZero,
efmCuPAFRemoteDiscoveryCode PhysAddress,
efmCuPmeThreshLineAtn Integer32,
efmCuPmeThreshSnrMgn Integer32,
efmCuPmeLineAtnCrossingEnable TruthValue,
efmCuPmeSnrMgnCrossingEnable TruthValue,
efmCuPmeDeviceFaultEnable TruthValue,
efmCuPmeConfigInitFailEnable TruthValue,
efmCuPmeProtocolInitFailEnable TruthValue
}
EfmCuPmeConfEntry ::=
SEQUENCE {
efmCuPmeAdminSubType INTEGER,
efmCuPmeAdminProfile EfmProfileIndexOrZero,
efmCuPAFRemoteDiscoveryCode PhysAddress,
efmCuPmeThreshLineAtn Integer32,
efmCuPmeThreshSnrMgn Integer32,
efmCuPmeLineAtnCrossingEnable TruthValue,
efmCuPmeSnrMgnCrossingEnable TruthValue,
efmCuPmeDeviceFaultEnable TruthValue,
efmCuPmeConfigInitFailEnable TruthValue,
efmCuPmeProtocolInitFailEnable TruthValue
}
efmCuPmeAdminSubType OBJECT-TYPE
SYNTAX INTEGER {
ieee2BaseTLO(1),
ieee2BaseTLR(2),
ieee10PassTSO(3),
ieee10PassTSR(4),
ieee2BaseTLor10PassTSR(5),
ieee2BaseTLor10PassTSO(6),
ieee10PassTSor2BaseTLO(7)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Administrative (desired) subtype of the PME.
Possible values are:
ieee2BaseTLO - PME SHALL operate as 2BaseTL-O
ieee2BaseTLR - PME SHALL operate as 2BaseTL-R
ieee10PassTSO - PME SHALL operate as 10PassTS-O
ieee10PassTSR - PME SHALL operate as 10PassTS-R
ieee2BaseTLor10PassTSR - PME SHALL operate as 2BaseTL-R or
10PassTS-R. The actual value will
be set by the -O link partner
during initialization (handshake).
ieee2BaseTLor10PassTSO - PME SHALL operate as 2BaseTL-O
(preferred) or 10PassTS-O. The
actual value will be set during
initialization depending on the -R
link partner capability (i.e., if
-R is incapable of the preferred
2BaseTL mode, 10PassTS will be
used).
ieee10PassTSor2BaseTLO - PME SHALL operate as 10PassTS-O
efmCuPmeAdminSubType OBJECT-TYPE
SYNTAX INTEGER {
ieee2BaseTLO(1),
ieee2BaseTLR(2),
ieee10PassTSO(3),
ieee10PassTSR(4),
ieee2BaseTLor10PassTSR(5),
ieee2BaseTLor10PassTSO(6),
ieee10PassTSor2BaseTLO(7)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Administrative (desired) subtype of the PME.
Possible values are:
ieee2BaseTLO - PME SHALL operate as 2BaseTL-O
ieee2BaseTLR - PME SHALL operate as 2BaseTL-R
ieee10PassTSO - PME SHALL operate as 10PassTS-O
ieee10PassTSR - PME SHALL operate as 10PassTS-R
ieee2BaseTLor10PassTSR - PME SHALL operate as 2BaseTL-R or
10PassTS-R. The actual value will
be set by the -O link partner
during initialization (handshake).
ieee2BaseTLor10PassTSO - PME SHALL operate as 2BaseTL-O
(preferred) or 10PassTS-O. The
actual value will be set during
initialization depending on the -R
link partner capability (i.e., if
-R is incapable of the preferred
2BaseTL mode, 10PassTS will be
used).
ieee10PassTSor2BaseTLO - PME SHALL operate as 10PassTS-O
(preferred) or 2BaseTL-O. The actual value will be set during initialization depending on the -R link partner capability (i.e., if -R is incapable of the preferred 10PassTS mode, 2BaseTL will be used).
（首选）或2BaseTL-O。实际值将在初始化过程中根据-R链路伙伴能力进行设置（即，如果-R无法使用首选10PassTS模式，则将使用2BaseTL）。
Changing efmCuPmeAdminSubType is a traffic-disruptive operation and as such SHALL be done when the link is Down. Attempts to change this object SHALL be rejected if the link is Up or Initializing. Attempts to change this object to an unsupported subtype (see efmCuPmeSubTypesSupported) SHALL be rejected.
更改efmCuPmeAdminSubType属于流量中断操作，因此应在链路断开时进行。如果链接已启动或正在初始化，则更改此对象的尝试将被拒绝。将此对象更改为不受支持的子类型的尝试（请参阅efmCuPmeSubTypesSupported）将被拒绝。
The current operational subtype is indicated by the efmCuPmeOperSubType variable.
当前操作子类型由EFMCUPMEOPERSUBYPE变量指示。
If a Clause 45 MDIO Interface to the PMA/PMD is present, then
this object combines values of the Port subtype select bits
and the PMA/PMD type selection bits in the 10P/2B PMA/PMD
control register."
REFERENCE
"[802.3ah] 61.1, 45.2.1.11.4, 45.2.1.11.7"
::= { efmCuPmeConfEntry 1 }
If a Clause 45 MDIO Interface to the PMA/PMD is present, then
this object combines values of the Port subtype select bits
and the PMA/PMD type selection bits in the 10P/2B PMA/PMD
control register."
REFERENCE
"[802.3ah] 61.1, 45.2.1.11.4, 45.2.1.11.7"
::= { efmCuPmeConfEntry 1 }
efmCuPmeAdminProfile OBJECT-TYPE SYNTAX EfmProfileIndexOrZero MAX-ACCESS read-write STATUS current DESCRIPTION "Desired PME configuration profile. This object is a pointer to an entry in either the efmCuPme2BProfileTable or the efmCuPme10PProfileTable, depending on the current operating SubType of the PME. The value of this object is the index of the referenced profile. The value of zero (default) indicates that the PME is configured via the efmCuAdminProfile object for the PCS port to which this PME is assigned. That is, the profile referenced by efmCuPmeAdminProfile takes precedence over the profile(s) referenced by efmCuAdminProfile.
efmCuPmeAdminProfile对象类型语法EfmProfileIndexOrZero MAX-ACCESS读写状态当前说明“所需的PME配置配置文件。此对象是指向efmCuPme2BProfileTable或efmCuPme10PProfileTable中的条目的指针，具体取决于PME的当前操作子类型。此对象的值是引用的配置文件的索引。零值（默认值）表示PME是通过efmCuAdminProfile对象为该PME分配到的PCS端口配置的。也就是说，efmCuPmeAdminProfile引用的配置文件优先于efmCuAdminProfile引用的配置文件。
This object is writable and readable for the CO subtype PMEs (2BaseTL-O or 10PassTS-O). It is irrelevant for the CPE subtype (2BaseTL-R or 10PassTS-R) -- a zero value SHALL be returned on an attempt to read this object and any attempt to change this object MUST be rejected in this case.
对于CO子类型PMEs（2BaseTL-O或10PassTS-O），此对象可写且可读。它与CPE子类型（2BaseTL-R或10PassTS-R）无关——尝试读取此对象时应返回零值，在这种情况下，任何更改此对象的尝试都必须被拒绝。
Note that the current operational profile value is available via efmCuPmeOperProfile object.
请注意，当前操作配置文件值可通过efmCuPmeOperProfile对象获得。
Any modification of this object MUST be performed when the link is Down. Attempts to change this object MUST be rejected, if the link is Up or Initializing.
此对象的任何修改都必须在链接关闭时执行。如果链接已启动或正在初始化，则必须拒绝更改此对象的尝试。
Attempts to set this object to a value that is not the value of the index for an active entry in the corresponding profile table MUST be rejected.
必须拒绝尝试将此对象设置为不是相应配置文件表中活动项的索引值的值。
This object maps to the Clause 30 attribute aProfileSelect.
此对象映射到子句30属性aProfileSelect。
This object MUST be maintained in a persistent manner."
REFERENCE
"[802.3ah] 30.11.2.1.6"
DEFVAL { 0 }
::= { efmCuPmeConfEntry 2 }
This object MUST be maintained in a persistent manner."
REFERENCE
"[802.3ah] 30.11.2.1.6"
DEFVAL { 0 }
::= { efmCuPmeConfEntry 2 }
efmCuPAFRemoteDiscoveryCode OBJECT-TYPE SYNTAX PhysAddress (SIZE(0|6)) MAX-ACCESS read-write STATUS current DESCRIPTION "PAF Remote Discovery Code of the PME port at the CO. The 6-octet Discovery Code of the peer PCS connected via the PME. Reading this object results in a Discovery Get operation. Setting this object to all zeroes results in a Discovery Clear_if_Same operation (the value of efmCuPAFDiscoveryCode at the peer PCS SHALL be the same as efmCuPAFDiscoveryCode of the local PCS associated with the PME for the operation to succeed). Writing a non-zero value to this object results in a Discovery Set_if_Clear operation. A zero-length octet string SHALL be returned on an attempt to read this object when PAF aggregation is not enabled.
efmCuPAFRemoteDiscoveryCode对象类型语法physadress（大小（0 | 6））MAX-ACCESS读写状态当前说明“公司PME端口的PAF远程发现代码。通过PME连接的对等PC的6-octet发现代码。读取此对象将导致发现获取操作。如果相同操作，将此对象设置为全零将导致发现清除（对等PC上的efmCuPAFDiscoveryCode值应与与PME关联的本地PC的efmCuPAFDiscoveryCode值相同，以便操作成功）。将非零值写入此对象将导致发现集\u if\u清除操作。当PAF聚合未启用时，尝试读取此对象时应返回长度为零的八位字节字符串。
This object is irrelevant in CPE port (-R) subtypes: in this case, a zero-length octet string SHALL be returned on an attempt to read this object; writing to this object SHALL be rejected.
此对象在CPE端口（-R）子类型中不相关：在这种情况下，尝试读取此对象时应返回零长度的八位字节字符串；对该对象的书写将被拒绝。
Discovery MUST be performed when the link is Down. Attempts to change this object MUST be rejected (in case of SNMP with the error inconsistentValue), if the link is Up or Initializing.
必须在链路断开时执行发现。如果链接已启动或正在初始化，则必须拒绝更改此对象的尝试（如果SNMP的错误值不一致）。
If a Clause 45 MDIO Interface to the PMA/PMD is present, then
this object is a function of 10P/2B aggregation discovery
control register, Discovery operation result bits in 10P/2B
aggregation and discovery status register and
10P/2B aggregation discovery code register."
REFERENCE
"[802.3ah] 61.2.2.8.4, 45.2.6.6-45.2.6.8"
::= { efmCuPmeConfEntry 3 }
If a Clause 45 MDIO Interface to the PMA/PMD is present, then
this object is a function of 10P/2B aggregation discovery
control register, Discovery operation result bits in 10P/2B
aggregation and discovery status register and
10P/2B aggregation discovery code register."
REFERENCE
"[802.3ah] 61.2.2.8.4, 45.2.6.6-45.2.6.8"
::= { efmCuPmeConfEntry 3 }
efmCuPmeThreshLineAtn OBJECT-TYPE SYNTAX Integer32(-127..128) UNITS "dB" MAX-ACCESS read-write STATUS current DESCRIPTION "Desired Line Attenuation threshold for the 2B/10P PME. This object configures the line attenuation alarm threshold. When the current value of Line Attenuation reaches or exceeds this threshold, an efmCuPmeLineAtnCrossing notification MAY be generated, if enabled by efmCuPmeLineAtnCrossingEnable.
efmCuPmeThreshLineAtn对象类型语法整数32（-127..128）单位“dB”最大访问读写状态当前说明“2B/10P PME所需的线路衰减阈值。此对象配置线路衰减报警阈值。当线路衰减的当前值达到或超过此阈值时，如果EFMCUPMELINEATNCROSSINGEABLE启用，则可能会生成EFMCUPMELINEATNCROSSINGEABLE通知。
This object is writable for the CO subtype PMEs (-O). It is read-only for the CPE subtype (-R).
此对象对于CO子类型PMEs（-O）是可写的。对于CPE子类型（-R），它是只读的。
Changing of the Line Attenuation threshold MUST be performed when the link is Down. Attempts to change this object MUST be rejected (in case of SNMP with the error inconsistentValue), if the link is Up or Initializing.
链路断开时，必须更改线路衰减阈值。如果链接已启动或正在初始化，则必须拒绝更改此对象的尝试（如果SNMP的错误值不一致）。
If a Clause 45 MDIO Interface to the PME is present, then this
object maps to the loop attenuation threshold bits in
the 2B PMD line quality thresholds register."
REFERENCE
"[802.3ah] 45.2.1.36"
::= { efmCuPmeConfEntry 4 }
If a Clause 45 MDIO Interface to the PME is present, then this
object maps to the loop attenuation threshold bits in
the 2B PMD line quality thresholds register."
REFERENCE
"[802.3ah] 45.2.1.36"
::= { efmCuPmeConfEntry 4 }
efmCuPmeThreshSnrMgn OBJECT-TYPE SYNTAX Integer32(-127..128) UNITS "dB" MAX-ACCESS read-write STATUS current DESCRIPTION "Desired SNR margin threshold for the 2B/10P PME. This object configures the SNR margin alarm threshold. When the current value of SNR margin reaches or exceeds this threshold, an efmCuPmeSnrMgnCrossing notification MAY be generated, if enabled by efmCuPmeSnrMgnCrossingEnable.
efmCuPmeThreshSnrMgn对象类型语法整数32（-127..128）单位“dB”最大访问读写状态当前说明“2B/10P PME所需的信噪比裕度阈值。此对象配置SNR余量报警阈值。当SNR余量的当前值达到或超过此阈值时，如果efmCuPmeSnrMgnCrossingEnable启用，则可能会生成efmCuPmeSnrMgnCrossing通知。
This object is writable for the CO subtype PMEs (2BaseTL-O/10PassTS-O). It is read-only for the CPE subtype (2BaseTL-R/10PassTS-R).
对于CO子类型PMEs（2BaseTL-O/10PassTS-O），此对象是可写的。对于CPE子类型（2BaseTL-R/10PassTS-R），它是只读的。
Changing of the SNR margin threshold MUST be performed when the link is Down. Attempts to change this object MUST be rejected (in case of SNMP with the error inconsistentValue), if the link is Up or Initializing.
当链路断开时，必须改变SNR裕度阈值。如果链接已启动或正在初始化，则必须拒绝更改此对象的尝试（如果SNMP的错误值不一致）。
If a Clause 45 MDIO Interface to the PME is present, then this
object maps to the SNR margin threshold bits in the 2B PMD
line quality thresholds register."
REFERENCE
"[802.3ah] 45.2.1.36"
::= { efmCuPmeConfEntry 5 }
If a Clause 45 MDIO Interface to the PME is present, then this
object maps to the SNR margin threshold bits in the 2B PMD
line quality thresholds register."
REFERENCE
"[802.3ah] 45.2.1.36"
::= { efmCuPmeConfEntry 5 }
efmCuPmeLineAtnCrossingEnable OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "Indicates whether efmCuPmeLineAtnCrossing notifications should be generated for this interface.
EFMCUPMELINEATNCROSSINGEABLE对象类型语法TruthValue MAX-ACCESS读写状态当前描述”指示是否应为此接口生成efmCuPmeLineAtnCrossing通知。
A value of true(1) indicates that efmCuPmeLineAtnCrossing
notification is enabled. A value of false(2) indicates that
the notification is disabled."
::= { efmCuPmeConfEntry 6 }
A value of true(1) indicates that efmCuPmeLineAtnCrossing
notification is enabled. A value of false(2) indicates that
the notification is disabled."
::= { efmCuPmeConfEntry 6 }
efmCuPmeSnrMgnCrossingEnable OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "Indicates whether efmCuPmeSnrMgnCrossing notifications should be generated for this interface.
EFMCUPMESNRMGNCrossingeable对象类型语法TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION”指示是否应为此接口生成efmCuPmeSnrMgnCrossing通知。
A value of true(1) indicates that efmCuPmeSnrMgnCrossing
notification is enabled. A value of false(2) indicates that
the notification is disabled."
::= { efmCuPmeConfEntry 7 }
A value of true(1) indicates that efmCuPmeSnrMgnCrossing
notification is enabled. A value of false(2) indicates that
the notification is disabled."
::= { efmCuPmeConfEntry 7 }
efmCuPmeDeviceFaultEnable OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "Indicates whether efmCuPmeDeviceFault notifications
efmCuPmeDeviceFaultEnable对象类型语法TruthValue MAX-ACCESS读写状态当前描述”指示efmCuPmeDeviceFault通知
should be generated for this interface.
应为此接口生成。
A value of true(1) indicates that efmCuPmeDeviceFault
notification is enabled. A value of false(2) indicates that
the notification is disabled."
::= { efmCuPmeConfEntry 8 }
A value of true(1) indicates that efmCuPmeDeviceFault
notification is enabled. A value of false(2) indicates that
the notification is disabled."
::= { efmCuPmeConfEntry 8 }
efmCuPmeConfigInitFailEnable OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "Indicates whether efmCuPmeConfigInitFailure notifications should be generated for this interface.
efmCuPmeConfigInitFailEnable对象类型语法TruthValue MAX-ACCESS读写状态当前描述”指示是否应为此接口生成efmCuPmeConfigInitFailure通知。
A value of true(1) indicates that efmCuPmeConfigInitFailure
notification is enabled. A value of false(2) indicates that
the notification is disabled."
::= { efmCuPmeConfEntry 9 }
A value of true(1) indicates that efmCuPmeConfigInitFailure
notification is enabled. A value of false(2) indicates that
the notification is disabled."
::= { efmCuPmeConfEntry 9 }
efmCuPmeProtocolInitFailEnable OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "Indicates whether efmCuPmeProtocolInitFailure notifications should be generated for this interface.
efmCuPmeProtocolInitFailEnable对象类型语法TruthValue MAX-ACCESS读写状态当前描述”指示是否应为此接口生成efmCuPmeProtocolInitFailure通知。
A value of true(1) indicates that efmCuPmeProtocolInitFailure
notification is enabled. A value of false(2) indicates that
the notification is disabled."
::= { efmCuPmeConfEntry 10 }
A value of true(1) indicates that efmCuPmeProtocolInitFailure
notification is enabled. A value of false(2) indicates that
the notification is disabled."
::= { efmCuPmeConfEntry 10 }
efmCuPmeCapabilityTable OBJECT-TYPE SYNTAX SEQUENCE OF EfmCuPmeCapabilityEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Table for the configuration of common aspects for EFMCu 2BASE-TL/10PASS-TS PME ports (modems). The configuration of aspects specific to 2BASE-TL or 10PASS-TS PME types is represented in the efmCuPme2BConfTable and the efmCuPme10PConfTable, respectively.
efmCuPmeCapabilityTable EfmCuPmeCapabilityEntry MAX-ACCESS不可访问状态的对象类型语法序列当前描述“EFMCu 2BASE-TL/10PASS-TS PME端口（调制解调器）通用配置表”。特定于2BASE-TL或10PASS-TS PME类型的方面配置分别在EFMCUPME2BConTable和efmCuPme10PConfTable中表示。
Entries in this table MUST be maintained in a persistent
manner."
::= { efmCuPme 2 }
Entries in this table MUST be maintained in a persistent
manner."
::= { efmCuPme 2 }
efmCuPmeCapabilityEntry OBJECT-TYPE
SYNTAX EfmCuPmeCapabilityEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the EFMCu PME Capability table.
Each entry represents common aspects of an EFMCu PME port
indexed by the ifIndex. Note that an EFMCu PME port can be
stacked below a single PCS port, also indexed by ifIndex,
possibly together with other PME ports if PAF is enabled."
INDEX { ifIndex }
::= { efmCuPmeCapabilityTable 1 }
efmCuPmeCapabilityEntry OBJECT-TYPE
SYNTAX EfmCuPmeCapabilityEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the EFMCu PME Capability table.
Each entry represents common aspects of an EFMCu PME port
indexed by the ifIndex. Note that an EFMCu PME port can be
stacked below a single PCS port, also indexed by ifIndex,
possibly together with other PME ports if PAF is enabled."
INDEX { ifIndex }
::= { efmCuPmeCapabilityTable 1 }
EfmCuPmeCapabilityEntry ::=
SEQUENCE {
efmCuPmeSubTypesSupported BITS
}
EfmCuPmeCapabilityEntry ::=
SEQUENCE {
efmCuPmeSubTypesSupported BITS
}
efmCuPmeSubTypesSupported OBJECT-TYPE
SYNTAX BITS {
ieee2BaseTLO(0),
ieee2BaseTLR(1),
ieee10PassTSO(2),
ieee10PassTSR(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"PME supported subtypes. This is a bitmap of possible
subtypes. The various bit positions are:
ieee2BaseTLO - PME is capable of operating as 2BaseTL-O
ieee2BaseTLR - PME is capable of operating as 2BaseTL-R
ieee10PassTSO - PME is capable of operating as 10PassTS-O
ieee10PassTSR - PME is capable of operating as 10PassTS-R
efmCuPmeSubTypesSupported OBJECT-TYPE
SYNTAX BITS {
ieee2BaseTLO(0),
ieee2BaseTLR(1),
ieee10PassTSO(2),
ieee10PassTSR(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"PME supported subtypes. This is a bitmap of possible
subtypes. The various bit positions are:
ieee2BaseTLO - PME is capable of operating as 2BaseTL-O
ieee2BaseTLR - PME is capable of operating as 2BaseTL-R
ieee10PassTSO - PME is capable of operating as 10PassTS-O
ieee10PassTSR - PME is capable of operating as 10PassTS-R
The desired mode of operation is determined by efmCuPmeAdminSubType, while efmCuPmeOperSubType reflects the current operating mode.
所需的操作模式由efmCuPmeAdminSubType确定，而efmCuPmeOperSubType反映当前的操作模式。
If a Clause 45 MDIO Interface to the PCS is present, then this
object combines the 10PASS-TS capable and 2BASE-TL capable
bits in the 10P/2B PMA/PMD speed ability register and the
CO supported and CPE supported bits in the 10P/2B PMA/PMD
status register."
REFERENCE
"[802.3ah] 61.1, 45.2.1.4.1, 45.2.1.4.2, 45.2.1.12.2,
45.2.1.12.3"
::= { efmCuPmeCapabilityEntry 1 }
If a Clause 45 MDIO Interface to the PCS is present, then this
object combines the 10PASS-TS capable and 2BASE-TL capable
bits in the 10P/2B PMA/PMD speed ability register and the
CO supported and CPE supported bits in the 10P/2B PMA/PMD
status register."
REFERENCE
"[802.3ah] 61.1, 45.2.1.4.1, 45.2.1.4.2, 45.2.1.12.2,
45.2.1.12.3"
::= { efmCuPmeCapabilityEntry 1 }
efmCuPmeStatusTable OBJECT-TYPE SYNTAX SEQUENCE OF EfmCuPmeStatusEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table provides common status information of EFMCu 2BASE-TL/10PASS-TS PME ports. Status information specific to 10PASS-TS PME is represented in efmCuPme10PStatusTable.
EFMCUPMESTATUSTATUSTABLE EfmCuPmeStatusEntry MAX-ACCESS的对象类型语法序列不可访问状态当前描述“此表提供EFMCu 2BASE-TL/10PASS-TS PME端口的常见状态信息。10PASS-TS PME的特定状态信息在efmCuPme10PStatusTable中表示。
This table contains live data from the equipment. As such,
it is NOT persistent."
::= { efmCuPme 3 }
This table contains live data from the equipment. As such,
it is NOT persistent."
::= { efmCuPme 3 }
efmCuPmeStatusEntry OBJECT-TYPE
SYNTAX EfmCuPmeStatusEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the EFMCu PME Status table.
Each entry represents common aspects of an EFMCu PME port
indexed by the ifIndex. Note that an EFMCu PME port can be
stacked below a single PCS port, also indexed by ifIndex,
possibly together with other PME ports if PAF is enabled."
INDEX { ifIndex }
::= { efmCuPmeStatusTable 1 }
efmCuPmeStatusEntry OBJECT-TYPE
SYNTAX EfmCuPmeStatusEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the EFMCu PME Status table.
Each entry represents common aspects of an EFMCu PME port
indexed by the ifIndex. Note that an EFMCu PME port can be
stacked below a single PCS port, also indexed by ifIndex,
possibly together with other PME ports if PAF is enabled."
INDEX { ifIndex }
::= { efmCuPmeStatusTable 1 }
EfmCuPmeStatusEntry ::=
SEQUENCE {
efmCuPmeOperStatus INTEGER,
efmCuPmeFltStatus BITS,
efmCuPmeOperSubType INTEGER,
efmCuPmeOperProfile EfmProfileIndexOrZero,
efmCuPmeSnrMgn Integer32,
efmCuPmePeerSnrMgn Integer32,
efmCuPmeLineAtn Integer32,
efmCuPmePeerLineAtn Integer32,
efmCuPmeEquivalentLength Unsigned32,
efmCuPmeTCCodingErrors Counter32,
efmCuPmeTCCrcErrors Counter32
}
EfmCuPmeStatusEntry ::=
SEQUENCE {
efmCuPmeOperStatus INTEGER,
efmCuPmeFltStatus BITS,
efmCuPmeOperSubType INTEGER,
efmCuPmeOperProfile EfmProfileIndexOrZero,
efmCuPmeSnrMgn Integer32,
efmCuPmePeerSnrMgn Integer32,
efmCuPmeLineAtn Integer32,
efmCuPmePeerLineAtn Integer32,
efmCuPmeEquivalentLength Unsigned32,
efmCuPmeTCCodingErrors Counter32,
efmCuPmeTCCrcErrors Counter32
}
efmCuPmeOperStatus OBJECT-TYPE
SYNTAX INTEGER {
up(1),
downNotReady(2),
downReady(3),
init(4)
}
efmCuPmeOperStatus OBJECT-TYPE
SYNTAX INTEGER {
up(1),
downNotReady(2),
downReady(3),
init(4)
}
MAX-ACCESS read-only STATUS current DESCRIPTION "Current PME link Operational Status. Possible values are: up(1) - The link is Up and ready to pass 64/65-octet encoded frames or fragments. downNotReady(2) - The link is Down and the PME does not detect Handshake tones from its peer. This value may indicate a possible problem with the peer PME. downReady(3) - The link is Down and the PME detects Handshake tones from its peer. init(4) - The link is Initializing, as a result of ifAdminStatus being set to 'up' for a particular PME or a PCS to which the PME is connected.
MAX-ACCESS只读状态当前描述“当前PME链路运行状态。可能的值为：up（1）-链路已启动并准备好传递64/65八位字节编码的帧或片段。downNotReady（2）-链路断开，PME未检测到来自其对等方的握手音。此值可能表示对等方PME可能存在问题。downReady（3）-链路断开，PME检测到来自其对等方的握手音。init（4）-由于特定PME或PME所连接的PC的ifAdminStatus设置为“启动”，链路正在初始化。
This object is intended to supplement the Down(2) state of ifOperStatus.
此对象用于补充iOperaStatus的关闭（2）状态。
This object partially maps to the Clause 30 attribute aPMEStatus.
此对象部分映射到子句30属性aPMEStatus。
If a Clause 45 MDIO Interface to the PME is present, then this
object partially maps to PMA/PMD link status bits in 10P/2B
PMA/PMD status register."
REFERENCE
"[802.3ah] 30.11.2.1.3, 45.2.1.12.4"
::= { efmCuPmeStatusEntry 1 }
If a Clause 45 MDIO Interface to the PME is present, then this
object partially maps to PMA/PMD link status bits in 10P/2B
PMA/PMD status register."
REFERENCE
"[802.3ah] 30.11.2.1.3, 45.2.1.12.4"
::= { efmCuPmeStatusEntry 1 }
efmCuPmeFltStatus OBJECT-TYPE
SYNTAX BITS {
lossOfFraming(0),
snrMgnDefect(1),
lineAtnDefect(2),
deviceFault(3),
configInitFailure(4),
protocolInitFailure(5)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Current/Last PME link Fault Status. This is a bitmap of
possible conditions. The various bit positions are:
efmCuPmeFltStatus OBJECT-TYPE
SYNTAX BITS {
lossOfFraming(0),
snrMgnDefect(1),
lineAtnDefect(2),
deviceFault(3),
configInitFailure(4),
protocolInitFailure(5)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Current/Last PME link Fault Status. This is a bitmap of
possible conditions. The various bit positions are:
lossOfFraming - Loss of Framing for 10P or Loss of Sync word for 2B PMD or Loss of 64/65-octet framing.
lossOfFraming-10P的帧丢失或2B PMD的同步字丢失或64/65八位组帧丢失。
snrMgnDefect - SNR margin dropped below the threshold. lineAtnDefect - Line Attenuation exceeds the threshold. deviceFault - Indicates a vendor-dependent diagnostic or self-test fault has been detected. configInitFailure - Configuration initialization failure, due to inability of the PME link to support the configuration profile, requested during initialization. protocolInitFailure - Protocol initialization failure, due to an incompatible protocol used by the peer PME during init (that could happen if a peer PMD is a regular G.SDHSL/VDSL modem instead of a 2BASE-TL/10PASS-TS PME).
snrMgnDefect-信噪比裕度降至阈值以下。LinetDefect-线路衰减超过阈值。deviceFault（设备故障）-表示检测到供应商相关的诊断或自检故障。configInitFailure—由于PME链路无法支持初始化期间请求的配置配置文件，导致配置初始化失败。protocolInitFailure—协议初始化失败，原因是对等PME在初始化期间使用的协议不兼容（如果对等PMD是常规G.SDHSL/VDSL调制解调器而不是2BASE-TL/10PASS-TS PME，则可能发生这种情况）。
This object is intended to supplement ifOperStatus in IF-MIB.
此对象旨在补充IF-MIB中的ifOperStatus。
This object holds information about the last fault.
efmCuPmeFltStatus is cleared by the device restart.
In addition, lossOfFraming, configInitFailure, and
protocolInitFailure are cleared by PME init;
deviceFault is cleared by successful diagnostics/test;
snrMgnDefect and lineAtnDefect are cleared by SNR margin
and Line attenuation, respectively, returning to norm and by
PME init.
This object holds information about the last fault.
efmCuPmeFltStatus is cleared by the device restart.
In addition, lossOfFraming, configInitFailure, and
protocolInitFailure are cleared by PME init;
deviceFault is cleared by successful diagnostics/test;
snrMgnDefect and lineAtnDefect are cleared by SNR margin
and Line attenuation, respectively, returning to norm and by
PME init.
This object partially maps to the Clause 30 attribute aPMEStatus.
此对象部分映射到子句30属性aPMEStatus。
If a Clause 45 MDIO Interface to the PME is present, then this
object consolidates information from various PMA/PMD
registers, namely: Fault bit in PMA/PMD status 1 register,
10P/2B PMA/PMD link loss register,
10P outgoing indicator bits status register,
10P incoming indicator bits status register,
2B state defects register."
REFERENCE
"[802.3ah] 30.11.2.1.3, 45.2.1.2.1, 45.2.1.38,
45.2.1.39, 45.2.1.54"
::= { efmCuPmeStatusEntry 2 }
If a Clause 45 MDIO Interface to the PME is present, then this
object consolidates information from various PMA/PMD
registers, namely: Fault bit in PMA/PMD status 1 register,
10P/2B PMA/PMD link loss register,
10P outgoing indicator bits status register,
10P incoming indicator bits status register,
2B state defects register."
REFERENCE
"[802.3ah] 30.11.2.1.3, 45.2.1.2.1, 45.2.1.38,
45.2.1.39, 45.2.1.54"
::= { efmCuPmeStatusEntry 2 }
efmCuPmeOperSubType OBJECT-TYPE SYNTAX INTEGER { ieee2BaseTLO(1), ieee2BaseTLR(2),
EFMCUPMEOPERSUBYPE对象类型语法整数{ieee2BaseTLO（1），ieee2BaseTLR（2），
ieee10PassTSO(3), ieee10PassTSR(4) } MAX-ACCESS read-only STATUS current DESCRIPTION "Current operational subtype of the PME. Possible values are: ieee2BaseTLO - PME operates as 2BaseTL-O ieee2BaseTLR - PME operates as 2BaseTL-R ieee10PassTSO - PME operates as 10PassTS-O ieee10PassTSR - PME operates as 10PassTS-R
ieee10PassTSO（3），ieee10PassTSR（4）}MAX-ACCESS只读状态当前描述“PME的当前操作子类型。可能的值为：ieee2BaseTLO-PME操作为2BaseTL-O ieee2BaseTLR-PME操作为2BaseTL-R ieee10PassTSO-PME操作为10PassTS-O ieee10PassTSR-PME操作为10PassTS-R
The desired operational subtype of the PME can be configured via the efmCuPmeAdminSubType variable.
可通过efmCuPmeAdminSubType变量配置PME的所需操作子类型。
If a Clause 45 MDIO Interface to the PMA/PMD is present, then
this object combines values of the Port subtype select
bits, the PMA/PMD type selection bits in the 10P/2B
PMA/PMD control register, and the PMA/PMD link status bits in
the 10P/2B PMA/PMD status register."
REFERENCE
"[802.3ah] 61.1, 45.2.1.11.4, 45.2.1.11.7, 45.2.1.12.4"
::= { efmCuPmeStatusEntry 3 }
If a Clause 45 MDIO Interface to the PMA/PMD is present, then
this object combines values of the Port subtype select
bits, the PMA/PMD type selection bits in the 10P/2B
PMA/PMD control register, and the PMA/PMD link status bits in
the 10P/2B PMA/PMD status register."
REFERENCE
"[802.3ah] 61.1, 45.2.1.11.4, 45.2.1.11.7, 45.2.1.12.4"
::= { efmCuPmeStatusEntry 3 }
efmCuPmeOperProfile OBJECT-TYPE SYNTAX EfmProfileIndexOrZero MAX-ACCESS read-only STATUS current DESCRIPTION "PME current operating profile. This object is a pointer to an entry in either the efmCuPme2BProfileTable or the efmCuPme10PProfileTable, depending on the current operating SubType of the PME as indicated by efmCuPmeOperSubType. Note that a profile entry to which efmCuPmeOperProfile is pointing can be created automatically to reflect achieved parameters in adaptive (not fixed) initialization, i.e., values of efmCuPmeOperProfile and efmCuAdminProfile or efmCuPmeAdminProfile may differ. The value of zero indicates that the PME is Down or Initializing.
efmCuPmeOperProfile对象类型语法EfmProfileIndexOrZero MAX-ACCESS只读状态当前说明“PME当前运行状况。此对象是指向efmCuPme2BProfileTable或efmCuPme10PProfileTable中的条目的指针，具体取决于EFMCUPMEOPERSUPERTYPE所指示的PME的当前操作子类型。请注意，可以自动创建efmCuPmeOperProfile指向的配置文件条目，以反映自适应（非固定）初始化中实现的参数，即efmCuPmeOperProfile和efmCuAdminProfile或EFMCUPMEDMINPROFILE的值可能不同。值为零表示PME停机或正在初始化。
This object partially maps to the aOperatingProfile attribute
in Clause 30."
REFERENCE
"[802.3ah] 30.11.2.1.7"
::= { efmCuPmeStatusEntry 4 }
This object partially maps to the aOperatingProfile attribute
in Clause 30."
REFERENCE
"[802.3ah] 30.11.2.1.7"
::= { efmCuPmeStatusEntry 4 }
efmCuPmeSnrMgn OBJECT-TYPE SYNTAX Integer32(-127..128|65535) UNITS "dB" MAX-ACCESS read-only STATUS current DESCRIPTION "The current Signal to Noise Ratio (SNR) margin with respect to the received signal as perceived by the local PME. The value of 65535 is returned when the PME is Down or Initializing.
efmCuPmeSnrMgn对象类型语法整数32（-127..128 | 65535）单位“dB”最大访问只读状态当前描述“本地PME感知到的相对于接收信号的当前信噪比（SNR）裕度。当PME关闭或初始化时返回65535的值。
This object maps to the aPMESNRMgn attribute in Clause 30.
此对象映射到第30条中的aPMESNRMgn属性。
If a Clause 45 MDIO Interface is present, then this
object maps to the 10P/2B RX SNR margin register."
REFERENCE
"[802.3ah] 30.11.2.1.4, 45.2.1.16"
::= { efmCuPmeStatusEntry 5 }
If a Clause 45 MDIO Interface is present, then this
object maps to the 10P/2B RX SNR margin register."
REFERENCE
"[802.3ah] 30.11.2.1.4, 45.2.1.16"
::= { efmCuPmeStatusEntry 5 }
efmCuPmePeerSnrMgn OBJECT-TYPE SYNTAX Integer32(-127..128|65535) UNITS "dB" MAX-ACCESS read-only STATUS current DESCRIPTION "The current SNR margin in dB with respect to the received signal, as perceived by the remote (link partner) PME. The value of 65535 is returned when the PME is Down or Initializing.
efmCuPmePeerSnrMgn对象类型语法整数32（-127..128 | 65535）单位“dB”最大访问只读状态当前描述“远程（链路伙伴）PME感知到的与接收信号相关的当前SNR裕度，单位为dB。当PME关闭或初始化时，返回65535值。
This object is irrelevant for the -R PME subtypes. The value of 65535 SHALL be returned in this case.
此对象与-R PME子类型无关。在这种情况下，应返回65535的值。
If a Clause 45 MDIO Interface is present, then this
object maps to the 10P/2B link partner RX SNR margin
register."
REFERENCE
"[802.3ah] 45.2.1.17"
::= { efmCuPmeStatusEntry 6}
If a Clause 45 MDIO Interface is present, then this
object maps to the 10P/2B link partner RX SNR margin
register."
REFERENCE
"[802.3ah] 45.2.1.17"
::= { efmCuPmeStatusEntry 6}
efmCuPmeLineAtn OBJECT-TYPE SYNTAX Integer32(-127..128|65535) UNITS "dB" MAX-ACCESS read-only STATUS current DESCRIPTION "The current Line Attenuation in dB as perceived by the local PME.
efmCuPmeLineAtn对象类型语法整数32（-127..128 | 65535）单位“dB”最大访问只读状态当前描述“本地PME感知的当前线路衰减（dB）。
The value of 65535 is returned when the PME is Down or Initializing.
PME停机或初始化时返回值65535。
If a Clause 45 MDIO Interface is present, then this
object maps to the Line Attenuation register."
REFERENCE
"[802.3ah] 45.2.1.18"
::= { efmCuPmeStatusEntry 7 }
If a Clause 45 MDIO Interface is present, then this
object maps to the Line Attenuation register."
REFERENCE
"[802.3ah] 45.2.1.18"
::= { efmCuPmeStatusEntry 7 }
efmCuPmePeerLineAtn OBJECT-TYPE SYNTAX Integer32(-127..128|65535) UNITS "dB" MAX-ACCESS read-only STATUS current DESCRIPTION "The current Line Attenuation in dB as perceived by the remote (link partner) PME. The value of 65535 is returned when the PME is Down or Initializing.
efmCuPmePeerLineAtn对象类型语法整数32（-127..128 | 65535）单位“dB”最大访问只读状态当前描述“远程（链路伙伴）PME感知到的以dB为单位的当前线路衰减。PME关闭或初始化时返回值65535。
This object is irrelevant for the -R PME subtypes. The value of 65535 SHALL be returned in this case.
此对象与-R PME子类型无关。在这种情况下，应返回65535的值。
If a Clause 45 MDIO Interface is present, then this
object maps to the 20P/2B link partner Line Attenuation
register."
REFERENCE
"[802.3ah] 45.2.1.19"
::= { efmCuPmeStatusEntry 8 }
If a Clause 45 MDIO Interface is present, then this
object maps to the 20P/2B link partner Line Attenuation
register."
REFERENCE
"[802.3ah] 45.2.1.19"
::= { efmCuPmeStatusEntry 8 }
efmCuPmeEquivalentLength OBJECT-TYPE SYNTAX Unsigned32(0..8192|65535) UNITS "m" MAX-ACCESS read-only STATUS current DESCRIPTION "An estimate of the equivalent loop's physical length in meters, as perceived by the PME after the link is established. An equivalent loop is a hypothetical 26AWG (0.4mm) loop with a perfect square root attenuation characteristic, without any bridged taps. The value of 65535 is returned if the link is Down or Initializing or the PME is unable to estimate the equivalent length.
EFMCupMeeEquivalentLength对象类型语法Unsigned32（0..8192 | 65535）单位“m”最大访问只读状态当前描述“PME在建立链路后感知到的等效环路物理长度的估计值（以米为单位）。等效环路是假设的26AWG（0.4mm）具有完美平方根衰减特性的环路，无任何桥接抽头。如果链路断开或初始化，或PME无法估计等效长度，则返回65535值。
For a 10BASE-TL PME, if a Clause 45 MDIO Interface to the PME is present, then this object maps to the 10P Electrical Length register."
对于10BASE-TL PME，如果存在到PME的第45条MDIO接口，则该对象映射到10P电长度寄存器。”
REFERENCE
"[802.3ah] 45.2.1.21"
::= { efmCuPmeStatusEntry 9 }
REFERENCE
"[802.3ah] 45.2.1.21"
::= { efmCuPmeStatusEntry 9 }
efmCuPmeTCCodingErrors OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of 64/65-octet encapsulation errors. This counter is incremented for each 64/65-octet encapsulation error detected by the 64/65-octet receive function.
efmCuPmeTCCodingErrors对象类型语法计数器32 MAX-ACCESS只读状态当前说明“64/65八位字节封装错误的数量。对于64/65八位字节接收函数检测到的每个64/65八位字节封装错误，此计数器将递增。
This object maps to aTCCodingViolations attribute in Clause 30.
此对象映射到第30条中的aTCCodingViolations属性。
If a Clause 45 MDIO Interface to the PME TC is present, then this object maps to the TC coding violations register (see 45.2.6.12).
如果存在PME TC的第45条MDIO接口，则该对象映射到TC编码违规寄存器（见45.2.6.12）。
Discontinuities in the value of this counter can occur at
re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime,
defined in IF-MIB."
REFERENCE
"[802.3ah] 61.3.3.1, 30.11.2.1.5, 45.2.6.12"
::= { efmCuPmeStatusEntry 10 }
Discontinuities in the value of this counter can occur at
re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime,
defined in IF-MIB."
REFERENCE
"[802.3ah] 61.3.3.1, 30.11.2.1.5, 45.2.6.12"
::= { efmCuPmeStatusEntry 10 }
efmCuPmeTCCrcErrors OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of TC-CRC errors. This counter is incremented for each TC-CRC error detected by the 64/65-octet receive function (see 61.3.3.3 and Figure 61-19).
EFMCUPMETCRCERRORS对象类型语法计数器32 MAX-ACCESS只读状态当前描述“TC-CRC错误数。对于64/65八位字节接收函数检测到的每个TC-CRC错误，此计数器递增（参见61.3.3.3和图61-19）。
This object maps to aTCCRCErrors attribute in Clause 30.
此对象映射到第30条中的aTCCRCErrors属性。
If a Clause 45 MDIO Interface to the PME TC is present, then this object maps to the TC CRC error register (see 45.2.6.11).
如果存在PME TC的第45条MDIO接口，则该对象映射到TC CRC错误寄存器（见45.2.6.11）。
Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime, defined in IF-MIB."
在重新初始化管理系统时，以及在IF-MIB中定义的IFCOUNTERINTERFACTIONYTIME值指示的其他时间，该计数器的值可能出现不连续。”
REFERENCE
"[802.3ah] 61.3.3.3, 30.11.2.1.10, 45.2.6.11"
::= { efmCuPmeStatusEntry 11 }
REFERENCE
"[802.3ah] 61.3.3.3, 30.11.2.1.10, 45.2.6.11"
::= { efmCuPmeStatusEntry 11 }
-- 2BASE-TL specific PME group
--2BASE-TL特定PME组
efmCuPme2B OBJECT IDENTIFIER ::= { efmCuPme 5 }
efmCuPme2B OBJECT IDENTIFIER ::= { efmCuPme 5 }
efmCuPme2BProfileTable OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPme2BProfileEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table supports definitions of administrative and
operating profiles for 2BASE-TL PMEs.
The first 14 entries in this table SHALL always be defined as
follows (see 802.3ah Annex 63A):
-------+-------+-------+-----+------+-------------+-----------
Profile MinRate MaxRate Power Region Constellation Comment
index (Kbps) (Kbps) (dBm)
-------+-------+-------+-----+------+-------------+-----------
1 5696 5696 13.5 1 32-TCPAM default
2 3072 3072 13.5 1 32-TCPAM
3 2048 2048 13.5 1 16-TCPAM
4 1024 1024 13.5 1 16-TCPAM
5 704 704 13.5 1 16-TCPAM
6 512 512 13.5 1 16-TCPAM
7 5696 5696 14.5 2 32-TCPAM
8 3072 3072 14.5 2 32-TCPAM
9 2048 2048 14.5 2 16-TCPAM
10 1024 1024 13.5 2 16-TCPAM
11 704 704 13.5 2 16-TCPAM
12 512 512 13.5 2 16-TCPAM
13 192 5696 0 1 0 best effort
14 192 5696 0 2 0 best effort
-------+-------+-------+-----+------+-------------+-----------
efmCuPme2BProfileTable OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPme2BProfileEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table supports definitions of administrative and
operating profiles for 2BASE-TL PMEs.
The first 14 entries in this table SHALL always be defined as
follows (see 802.3ah Annex 63A):
-------+-------+-------+-----+------+-------------+-----------
Profile MinRate MaxRate Power Region Constellation Comment
index (Kbps) (Kbps) (dBm)
-------+-------+-------+-----+------+-------------+-----------
1 5696 5696 13.5 1 32-TCPAM default
2 3072 3072 13.5 1 32-TCPAM
3 2048 2048 13.5 1 16-TCPAM
4 1024 1024 13.5 1 16-TCPAM
5 704 704 13.5 1 16-TCPAM
6 512 512 13.5 1 16-TCPAM
7 5696 5696 14.5 2 32-TCPAM
8 3072 3072 14.5 2 32-TCPAM
9 2048 2048 14.5 2 16-TCPAM
10 1024 1024 13.5 2 16-TCPAM
11 704 704 13.5 2 16-TCPAM
12 512 512 13.5 2 16-TCPAM
13 192 5696 0 1 0 best effort
14 192 5696 0 2 0 best effort
-------+-------+-------+-----+------+-------------+-----------
These default entries SHALL be created during agent initialization and MUST NOT be deleted.
这些默认条目应在代理初始化期间创建，不得删除。
Entries following the first 14 can be dynamically created and deleted to provide custom administrative (configuration) profiles and automatic operating profiles.
可以动态创建和删除前14项之后的条目，以提供自定义管理（配置）配置文件和自动操作配置文件。
This table MUST be maintained in a persistent manner."
REFERENCE
"[802.3ah] Annex 63A, 30.11.2.1.6"
::= { efmCuPme2B 2 }
This table MUST be maintained in a persistent manner."
REFERENCE
"[802.3ah] Annex 63A, 30.11.2.1.6"
::= { efmCuPme2B 2 }
efmCuPme2BProfileEntry OBJECT-TYPE SYNTAX EfmCuPme2BProfileEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Each entry corresponds to a single 2BASE-TL PME profile. Each profile contains a set of parameters, used either for configuration or representation of a 2BASE-TL PME. In case a particular profile is referenced via the efmCuPmeAdminProfile object (or efmCuAdminProfile if efmCuPmeAdminProfile is zero), it represents the desired parameters for the 2BaseTL-O PME initialization. If a profile is referenced via an efmCuPmeOperProfile object, it represents the current operating parameters of an operational PME.
efmCuPme2BProfileEntry对象类型语法efmCuPme2BProfileEntry MAX-ACCESS不可访问状态当前说明“每个条目对应一个2BASE-TL PME配置文件。每个配置文件包含一组参数，用于配置或表示2BASE-TL PME。如果通过efmCuPmeAdminProfile对象引用特定配置文件（如果efmCuPmeAdminProfile为零，则为efmCuAdminProfile），则它表示2BaseTL-O PME初始化所需的参数。如果通过efmCuPmeOperProfile对象引用配置文件，则它表示操作PME的当前操作参数。
Profiles may be created/deleted using the row creation/
deletion mechanism via efmCuPme2BProfileRowStatus. If an
active entry is referenced, the entry MUST remain 'active'
until all references are removed.
Default entries MUST NOT be removed."
INDEX { efmCuPme2BProfileIndex }
::= { efmCuPme2BProfileTable 1 }
Profiles may be created/deleted using the row creation/
deletion mechanism via efmCuPme2BProfileRowStatus. If an
active entry is referenced, the entry MUST remain 'active'
until all references are removed.
Default entries MUST NOT be removed."
INDEX { efmCuPme2BProfileIndex }
::= { efmCuPme2BProfileTable 1 }
EfmCuPme2BProfileEntry ::=
SEQUENCE {
efmCuPme2BProfileIndex EfmProfileIndex,
efmCuPme2BProfileDescr SnmpAdminString,
efmCuPme2BRegion INTEGER,
efmCuPme2BsMode EfmProfileIndexOrZero,
efmCuPme2BMinDataRate Unsigned32,
efmCuPme2BMaxDataRate Unsigned32,
efmCuPme2BPower Unsigned32,
efmCuPme2BConstellation INTEGER,
efmCuPme2BProfileRowStatus RowStatus
}
EfmCuPme2BProfileEntry ::=
SEQUENCE {
efmCuPme2BProfileIndex EfmProfileIndex,
efmCuPme2BProfileDescr SnmpAdminString,
efmCuPme2BRegion INTEGER,
efmCuPme2BsMode EfmProfileIndexOrZero,
efmCuPme2BMinDataRate Unsigned32,
efmCuPme2BMaxDataRate Unsigned32,
efmCuPme2BPower Unsigned32,
efmCuPme2BConstellation INTEGER,
efmCuPme2BProfileRowStatus RowStatus
}
efmCuPme2BProfileIndex OBJECT-TYPE
SYNTAX EfmProfileIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"2BASE-TL PME profile index.
This object is the unique index associated with this profile.
Entries in this table are referenced via efmCuAdminProfile or
efmCuPmeAdminProfile objects."
::= { efmCuPme2BProfileEntry 1 }
efmCuPme2BProfileIndex OBJECT-TYPE
SYNTAX EfmProfileIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"2BASE-TL PME profile index.
This object is the unique index associated with this profile.
Entries in this table are referenced via efmCuAdminProfile or
efmCuPmeAdminProfile objects."
::= { efmCuPme2BProfileEntry 1 }
efmCuPme2BProfileDescr OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"A textual string containing information about a 2BASE-TL PME
profile. The string may include information about the data
rate and spectral limitations of this particular profile."
::= { efmCuPme2BProfileEntry 2 }
efmCuPme2BProfileDescr OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"A textual string containing information about a 2BASE-TL PME
profile. The string may include information about the data
rate and spectral limitations of this particular profile."
::= { efmCuPme2BProfileEntry 2 }
efmCuPme2BRegion OBJECT-TYPE
SYNTAX INTEGER {
region1(1),
region2(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Regional settings for a 2BASE-TL PME, as specified in the
relevant Regional Annex of [G.991.2].
Regional settings specify the Power Spectral Density (PSD)
mask and the Power Back-Off (PBO) values, and place
limitations on the max allowed data rate, power, and
constellation.
efmCuPme2BRegion OBJECT-TYPE
SYNTAX INTEGER {
region1(1),
region2(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Regional settings for a 2BASE-TL PME, as specified in the
relevant Regional Annex of [G.991.2].
Regional settings specify the Power Spectral Density (PSD)
mask and the Power Back-Off (PBO) values, and place
limitations on the max allowed data rate, power, and
constellation.
Possible values for this object are: region1 - Annexes A and F (e.g., North America) region2 - Annexes B and G (e.g., Europe)
该对象的可能值为：区域1-附件A和F（如北美）区域2-附件B和g（如欧洲）
Annex A/B specify regional settings for data rates 192-2304 Kbps using 16-TCPAM encoding. Annex F/G specify regional settings for rates 2320-3840 Kbps using 16-TCPAM encoding and 768-5696 Kbps using 32-TCPAM encoding.
附录A/B规定了使用16-TCPAM编码的192-2304 Kbps数据速率的区域设置。附录F/G规定了使用16-TCPAM编码的2320-3840 Kbps速率和使用32-TCPAM编码的768-5696 Kbps速率的区域设置。
If a Clause 45 MDIO Interface to the PME is present, then this
object partially maps to the Region bits in the 2B general
parameter register."
REFERENCE
"[802.3ah] 45.2.1.42; [G.991.2] Annexes A, B, F and G"
::= { efmCuPme2BProfileEntry 3 }
If a Clause 45 MDIO Interface to the PME is present, then this
object partially maps to the Region bits in the 2B general
parameter register."
REFERENCE
"[802.3ah] 45.2.1.42; [G.991.2] Annexes A, B, F and G"
::= { efmCuPme2BProfileEntry 3 }
efmCuPme2BsMode OBJECT-TYPE SYNTAX EfmProfileIndexOrZero MAX-ACCESS read-create STATUS current DESCRIPTION "Desired custom Spectral Mode for a 2BASE-TL PME. This object
efmCuPme2BsMode对象类型语法EfmProfileIndexOrZero MAX-ACCESS read create STATUS current DESCRIPTION“2BASE-TL PME所需的自定义光谱模式。此对象
is a pointer to an entry in efmCuPme2BsModeTable and a block of entries in efmCuPme2BRateReachTable, which together define (country-specific) reach-dependent rate limitations in addition to those defined by efmCuPme2BRegion.
是指向efmCuPme2BsModeTable中的一个条目和EFMCUPME2BRATEACHTABLE中的一个条目块的指针，它们共同定义了（特定于国家/地区的）到达相关利率限制，以及efmCuPme2BsModeTable定义的利率限制。
The value of this object is the index of the referenced spectral mode. The value of zero (default) indicates that no specific spectral mode is applicable.
此对象的值是参考光谱模式的索引。零值（默认值）表示不适用特定的光谱模式。
Attempts to set this object to a value that is not the value
of the index for an active entry in the corresponding spectral
mode table MUST be rejected."
REFERENCE
"efmCuPme2BsModeTable, efmCuPme2BRateReachTable"
DEFVAL { 0 }
::= { efmCuPme2BProfileEntry 4 }
Attempts to set this object to a value that is not the value
of the index for an active entry in the corresponding spectral
mode table MUST be rejected."
REFERENCE
"efmCuPme2BsModeTable, efmCuPme2BRateReachTable"
DEFVAL { 0 }
::= { efmCuPme2BProfileEntry 4 }
efmCuPme2BMinDataRate OBJECT-TYPE SYNTAX Unsigned32(192..5696) UNITS "Kbps" MAX-ACCESS read-create STATUS current DESCRIPTION "Minimum Data Rate for the 2BASE-TL PME. This object can take values of (n x 64)Kbps, where n=3..60 for 16-TCPAM and n=12..89 for 32-TCPAM encoding.
EFMCUPME2BMINDATAATE对象类型语法Unsigned32（192..5696）单位“Kbps”MAX-ACCESS read create STATUS current DESCRIPTION“2BASE-TL PME的最小数据速率。此对象的值可以为（n x 64）Kbps，其中n=3..60表示16-TCPAM，n=12..89表示32-TCPAM编码。
The data rate of the 2BASE-TL PME is considered 'fixed' when the value of this object equals that of efmCuPme2BMaxDataRate. If efmCuPme2BMinDataRate is less than efmCuPme2BMaxDataRate in the administrative profile, the data rate is considered 'adaptive', and SHALL be set to the maximum attainable rate not exceeding efmCuPme2BMaxDataRate, under the spectral limitations placed by the efmCuPme2BRegion and efmCuPme2BsMode.
当2BASE-TL PME的值等于efmCuPme2BMaxDataRate的值时，该对象的数据速率被视为“固定”。如果管理配置文件中的efmCuPme2BMinDataRate小于efmCuPme2BMaxDataRate，则数据速率被视为“自适应”，并应根据EFMCUPME2BRION和EFMCUPME2BMOSMODE设置的频谱限制，设置为不超过efmCuPme2BMaxDataRate的最大可达到速率。
Note that the current operational data rate of the PME is represented by the ifSpeed object of IF-MIB.
请注意，PME的当前操作数据速率由IF-MIB的ifSpeed对象表示。
If a Clause 45 MDIO Interface to the PME is present, then this object maps to the Min Data Rate1 bits in the 2B PMD parameters register.
如果存在到PME的子句45 MDIO接口，则此对象映射到2B PMD参数寄存器中的最小数据速率1位。
This object MUST be maintained in a persistent manner."
REFERENCE
"[802.3ah] 45.2.1.43"
::= { efmCuPme2BProfileEntry 5 }
This object MUST be maintained in a persistent manner."
REFERENCE
"[802.3ah] 45.2.1.43"
::= { efmCuPme2BProfileEntry 5 }
efmCuPme2BMaxDataRate OBJECT-TYPE SYNTAX Unsigned32(192..5696) UNITS "Kbps" MAX-ACCESS read-create STATUS current DESCRIPTION "Maximum Data Rate for the 2BASE-TL PME. This object can take values of (n x 64)Kbps, where n=3..60 for 16-TCPAM and n=12..89 for 32-TCPAM encoding.
efmCuPme2BMaxDataRate对象类型语法Unsigned32（192..5696）单位“Kbps”MAX-ACCESS read create STATUS current DESCRIPTION“2BASE-TL PME的最大数据速率。此对象的值可以为（n x 64）Kbps，其中n=3..60表示16-TCPAM，n=12..89表示32-TCPAM编码。
The data rate of the 2BASE-TL PME is considered 'fixed' when the value of this object equals that of efmCuPme2BMinDataRate. If efmCuPme2BMinDataRate is less than efmCuPme2BMaxDataRate in the administrative profile, the data rate is considered 'adaptive', and SHALL be set to the maximum attainable rate not exceeding efmCuPme2BMaxDataRate, under the spectral limitations placed by the efmCuPme2BRegion and efmCuPme2BsMode.
当2BASE-TL PME的值等于EFMCUPME2BMINDATAATE的值时，该对象的数据速率被视为“固定”。如果管理配置文件中的efmCuPme2BMinDataRate小于efmCuPme2BMaxDataRate，则数据速率被视为“自适应”，并应根据EFMCUPME2BRION和EFMCUPME2BMOSMODE设置的频谱限制，设置为不超过efmCuPme2BMaxDataRate的最大可达到速率。
Note that the current operational data rate of the PME is represented by the ifSpeed object of IF-MIB.
请注意，PME的当前操作数据速率由IF-MIB的ifSpeed对象表示。
If a Clause 45 MDIO Interface to the PME is present, then this object maps to the Max Data Rate1 bits in the 2B PMD parameters register.
如果存在到PME的子句45 MDIO接口，则此对象映射到2B PMD参数寄存器中的最大数据速率1位。
This object MUST be maintained in a persistent manner."
REFERENCE
"[802.3ah] 45.2.1.43"
::= { efmCuPme2BProfileEntry 6 }
This object MUST be maintained in a persistent manner."
REFERENCE
"[802.3ah] 45.2.1.43"
::= { efmCuPme2BProfileEntry 6 }
efmCuPme2BPower OBJECT-TYPE SYNTAX Unsigned32(0|10..42) UNITS "0.5 dBm" MAX-ACCESS read-create STATUS current DESCRIPTION "Signal Transmit Power. Multiple of 0.5 dBm. The value of 0 in the administrative profile means that the signal transmit power is not fixed and SHALL be set to maximize the attainable rate, under the spectral limitations placed by the efmCuPme2BRegion and efmCuPme2BsMode.
efmCuPme2BPower对象类型语法Unsigned32（0 | 10..42）单位“0.5 dBm”最大读取创建状态当前说明“信号发射功率。0.5 dBm的倍数。管理配置文件中的值0表示信号发射功率不是固定的，应在efmCuPme2BRegion和efmCuPme2BsMode设置的频谱限制下设置为最大可达到的速率。
If a Clause 45 MDIO Interface to the PME is present, then this object maps to the Power1 bits in the 2B PMD parameters register." REFERENCE "[802.3ah] 45.2.1.43"
如果存在到PME的第45条MDIO接口，则该对象映射到2B PMD参数寄存器中的Power1位。“参考”[802.3ah]45.2.1.43
::= { efmCuPme2BProfileEntry 7 }
::= { efmCuPme2BProfileEntry 7 }
efmCuPme2BConstellation OBJECT-TYPE
SYNTAX INTEGER {
adaptive(0),
tcpam16(1),
tcpam32(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"TCPAM Constellation of the 2BASE-TL PME.
The possible values are:
adaptive(0) - either 16- or 32-TCPAM
tcpam16(1) - 16-TCPAM
tcpam32(2) - 32-TCPAM
efmCuPme2BConstellation OBJECT-TYPE
SYNTAX INTEGER {
adaptive(0),
tcpam16(1),
tcpam32(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"TCPAM Constellation of the 2BASE-TL PME.
The possible values are:
adaptive(0) - either 16- or 32-TCPAM
tcpam16(1) - 16-TCPAM
tcpam32(2) - 32-TCPAM
The value of adaptive(0) in the administrative profile means that the constellation is not fixed and SHALL be set to maximize the attainable rate, under the spectral limitations placed by the efmCuPme2BRegion and efmCuPme2BsMode.
管理配置文件中的自适应（0）值意味着星座不是固定的，并且应设置为在efmCuPme2BRegion和efmCuPme2BsMode设置的频谱限制下最大化可达到的速率。
If a Clause 45 MDIO Interface to the PME is present, then this
object maps to the Constellation1 bits in the 2B general
parameter register."
REFERENCE
"[802.3ah] 45.2.1.43"
::= { efmCuPme2BProfileEntry 8 }
If a Clause 45 MDIO Interface to the PME is present, then this
object maps to the Constellation1 bits in the 2B general
parameter register."
REFERENCE
"[802.3ah] 45.2.1.43"
::= { efmCuPme2BProfileEntry 8 }
efmCuPme2BProfileRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This object controls the creation, modification, or deletion of the associated entry in the efmCuPme2BProfileTable per the semantics of RowStatus.
EFMCUPME2BProwStatus对象类型语法RowStatus MAX-ACCESS read create STATUS current DESCRIPTION“此对象根据RowStatus的语义控制efmCuPme2BProfileTable中关联项的创建、修改或删除。
If an 'active' entry is referenced via efmCuAdminProfile or efmCuPmeAdminProfile instance(s), the entry MUST remain 'active'.
如果通过efmCuAdminProfile或efmCuPmeAdminProfile实例引用了“活动”条目，则该条目必须保持“活动”。
An 'active' entry SHALL NOT be modified. In order to modify
an existing entry, it MUST be taken out of service (by setting
this object to 'notInService'), modified, and set 'active'
again."
::= { efmCuPme2BProfileEntry 9 }
An 'active' entry SHALL NOT be modified. In order to modify
an existing entry, it MUST be taken out of service (by setting
this object to 'notInService'), modified, and set 'active'
again."
::= { efmCuPme2BProfileEntry 9 }
efmCuPme2BsModeTable OBJECT-TYPE SYNTAX SEQUENCE OF EfmCuPme2BsModeEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table, together with efmCu2BReachRateTable, supports definition of administrative custom spectral modes for 2BASE-TL PMEs, describing spectral limitations in addition to those specified by efmCuPme2BRegion.
efmCuPme2BsModeTable EfmCuPme2BsModeEntry MAX-ACCESS不可访问状态当前描述的对象类型语法序列“此表与EFMCU2BSMODEENTRY RATETABLE一起，支持定义2BASE-TL PME的管理自定义频谱模式，除EFMCUPME2BRIGENT指定的模式外，还描述频谱限制。
In some countries, spectral regulations (e.g., UK ANFP) limit the length of the loops for certain data rates. This table allows these country-specific limitations to be specified.
在一些国家，频谱法规（如英国ANFP）限制了某些数据速率下环路的长度。此表允许指定这些特定于国家/地区的限制。
Entries in this table referenced by the efmCuPme2BsMode MUST NOT be deleted until all the active references are removed.
在删除所有活动引用之前，不得删除efmCuPme2BsMode引用的此表中的条目。
This table MUST be maintained in a persistent manner."
REFERENCE
"efmCu2BReachRateTable"
::= { efmCuPme2B 3 }
This table MUST be maintained in a persistent manner."
REFERENCE
"efmCu2BReachRateTable"
::= { efmCuPme2B 3 }
efmCuPme2BsModeEntry OBJECT-TYPE SYNTAX EfmCuPme2BsModeEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Each entry specifies a spectral mode description and its index, which is used to reference corresponding entries in the efmCu2BReachRateTable.
efmCuPme2BsModeEntry对象类型语法efmCuPme2BsModeEntry MAX-ACCESS not ACCESS STATUS current DESCRIPTION“每个条目指定频谱模式描述及其索引，用于引用EFMCU2BSMODEENTRY RATETable中的相应条目。
Entries may be created/deleted using the row creation/
deletion mechanism via efmCuPme2BsModeRowStatus."
INDEX { efmCuPme2BsModeIndex }
::= { efmCuPme2BsModeTable 1 }
Entries may be created/deleted using the row creation/
deletion mechanism via efmCuPme2BsModeRowStatus."
INDEX { efmCuPme2BsModeIndex }
::= { efmCuPme2BsModeTable 1 }
EfmCuPme2BsModeEntry ::=
SEQUENCE {
efmCuPme2BsModeIndex EfmProfileIndex,
efmCuPme2BsModeDescr SnmpAdminString,
efmCuPme2BsModeRowStatus RowStatus
}
EfmCuPme2BsModeEntry ::=
SEQUENCE {
efmCuPme2BsModeIndex EfmProfileIndex,
efmCuPme2BsModeDescr SnmpAdminString,
efmCuPme2BsModeRowStatus RowStatus
}
efmCuPme2BsModeIndex OBJECT-TYPE SYNTAX EfmProfileIndex MAX-ACCESS not-accessible STATUS current
efmCuPme2BsModeIndex对象类型语法EfmProfileIndex MAX-ACCESS不可访问状态当前
DESCRIPTION
"2BASE-TL PME Spectral Mode index.
This object is the unique index associated with this spectral
mode.
Entries in this table are referenced via the efmCuPme2BsMode
object."
::= { efmCuPme2BsModeEntry 1 }
DESCRIPTION
"2BASE-TL PME Spectral Mode index.
This object is the unique index associated with this spectral
mode.
Entries in this table are referenced via the efmCuPme2BsMode
object."
::= { efmCuPme2BsModeEntry 1 }
efmCuPme2BsModeDescr OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"A textual string containing information about a 2BASE-TL PME
spectral mode. The string may include information about
corresponding (country-specific) spectral regulations
and rate/reach limitations of this particular spectral mode."
::= { efmCuPme2BsModeEntry 2 }
efmCuPme2BsModeDescr OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"A textual string containing information about a 2BASE-TL PME
spectral mode. The string may include information about
corresponding (country-specific) spectral regulations
and rate/reach limitations of this particular spectral mode."
::= { efmCuPme2BsModeEntry 2 }
efmCuPme2BsModeRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This object controls creation, modification, or deletion of the associated entry in efmCuPme2BsModeTable per the semantics of RowStatus.
efmCuPme2BsModeRowStatus对象类型语法RowStatus MAX-ACCESS read create STATUS current DESCRIPTION“此对象根据RowStatus的语义控制efmCuPme2BsModeTable中关联项的创建、修改或删除。
If an 'active' entry is referenced via efmCuPme2BsMode instance(s), the entry MUST remain 'active'.
如果通过efmCuPme2BsMode实例引用了“活动”条目，则该条目必须保持“活动”。
An 'active' entry SHALL NOT be modified. In order to modify
an existing entry, it MUST be taken out of service (by setting
this object to 'notInService'), modified, and set 'active'
again."
::= { efmCuPme2BsModeEntry 3 }
An 'active' entry SHALL NOT be modified. In order to modify
an existing entry, it MUST be taken out of service (by setting
this object to 'notInService'), modified, and set 'active'
again."
::= { efmCuPme2BsModeEntry 3 }
efmCuPme2BReachRateTable OBJECT-TYPE SYNTAX SEQUENCE OF EfmCuPme2BReachRateEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table supports the definition of administrative custom spectral modes for 2BASE-TL PMEs, providing spectral limitations in addition to those specified by efmCuPme2BRegion.
efmCuPme2BReachRateTable EFMCUPME2BREACHRATENTRY MAX-ACCESS不可访问状态当前描述的对象类型语法序列“此表支持2BASE-TL PME管理自定义频谱模式的定义，除了EFMCUPME2BREACHRATENTRY指定的频谱限制外，还提供频谱限制。
The spectral regulations in some countries (e.g., UK ANFP) limit the length of the loops for certain data rates. This table allows these country-specific limitations to be specified.
一些国家（如英国ANFP）的频谱法规限制了某些数据速率下环路的长度。此表允许指定这些特定于国家/地区的限制。
Below is an example of this table for [ANFP]:
----------+-------+-------
Equivalent MaxRate MaxRate
Length PAM16 PAM32
(m) (Kbps) (Kbps)
----------+-------+-------
975 2304 5696
1125 2304 5504
1275 2304 5120
1350 2304 4864
1425 2304 4544
1500 2304 4288
1575 2304 3968
1650 2304 3776
1725 2304 3520
1800 2304 3264
1875 2304 3072
1950 2048 2688
2100 1792 2368
2250 1536 0
2400 1408 0
2550 1280 0
2775 1152 0
2925 1152 0
3150 1088 0
3375 1024 0
----------+-------+-------
Below is an example of this table for [ANFP]:
----------+-------+-------
Equivalent MaxRate MaxRate
Length PAM16 PAM32
(m) (Kbps) (Kbps)
----------+-------+-------
975 2304 5696
1125 2304 5504
1275 2304 5120
1350 2304 4864
1425 2304 4544
1500 2304 4288
1575 2304 3968
1650 2304 3776
1725 2304 3520
1800 2304 3264
1875 2304 3072
1950 2048 2688
2100 1792 2368
2250 1536 0
2400 1408 0
2550 1280 0
2775 1152 0
2925 1152 0
3150 1088 0
3375 1024 0
----------+-------+-------
Entries in this table referenced by an efmCuPme2BsMode instance MUST NOT be deleted.
不能删除efmCuPme2BsMode实例引用的此表中的条目。
This table MUST be maintained in a persistent manner."
REFERENCE
"[ANFP]"
::= { efmCuPme2B 4 }
This table MUST be maintained in a persistent manner."
REFERENCE
"[ANFP]"
::= { efmCuPme2B 4 }
efmCuPme2BReachRateEntry OBJECT-TYPE SYNTAX EfmCuPme2BReachRateEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Each entry specifies maximum 2BASE-TL PME data rates allowed for a certain equivalent loop length, when using
EFMCUPME2BREACHRATENTRY对象类型语法EFMCUPME2BREACHRATENTRY MAX-ACCESS not ACCESS STATUS current DESCRIPTION“每个条目指定在使用
16-TCPAM or 32-TCPAM encoding.
16-TCPAM或32-TCPAM编码。
When a 2BASE-TL PME is initialized, its data rate MUST NOT exceed one of the following limitations: - the value of efmCuPme2BMaxDataRate - maximum data rate allowed by efmCuPme2BRegion and efmCuPme2BPower - maximum data rate for a given encoding specified in the efmCuPme2BsModeEntry, corresponding to the equivalent loop length, estimated by the PME
初始化2BASE-TL PME时，其数据速率不得超过以下限制之一：-efmCuPme2BMaxDataRate的值-EFMCUPME2BRAGION和efmCuPme2BPower允许的最大数据速率-EFMCUPME2BMODENTRY中指定的给定编码的最大数据速率，对应于等效循环长度，由PME估算
It is RECOMMENDED that the efmCuPme2BEquivalentLength values are assigned in increasing order, starting from the minimum value.
建议从最小值开始，按递增顺序分配EFMCUPME2B等效长度值。
Entries may be created/deleted using the row creation/
deletion mechanism via efmCuPme2ReachRateRowStatus."
INDEX { efmCuPme2BsModeIndex, efmCuPme2BReachRateIndex }
::= { efmCuPme2BReachRateTable 1 }
Entries may be created/deleted using the row creation/
deletion mechanism via efmCuPme2ReachRateRowStatus."
INDEX { efmCuPme2BsModeIndex, efmCuPme2BReachRateIndex }
::= { efmCuPme2BReachRateTable 1 }
EfmCuPme2BReachRateEntry ::=
SEQUENCE {
efmCuPme2BReachRateIndex EfmProfileIndex,
efmCuPme2BEquivalentLength Unsigned32,
efmCuPme2BMaxDataRatePam16 Unsigned32,
efmCuPme2BMaxDataRatePam32 Unsigned32,
efmCuPme2BReachRateRowStatus RowStatus
}
EfmCuPme2BReachRateEntry ::=
SEQUENCE {
efmCuPme2BReachRateIndex EfmProfileIndex,
efmCuPme2BEquivalentLength Unsigned32,
efmCuPme2BMaxDataRatePam16 Unsigned32,
efmCuPme2BMaxDataRatePam32 Unsigned32,
efmCuPme2BReachRateRowStatus RowStatus
}
efmCuPme2BReachRateIndex OBJECT-TYPE
SYNTAX EfmProfileIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"2BASE-TL custom spectral mode Reach-Rate table index.
This object is the unique index associated with each entry."
::= { efmCuPme2BReachRateEntry 1 }
efmCuPme2BReachRateIndex OBJECT-TYPE
SYNTAX EfmProfileIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"2BASE-TL custom spectral mode Reach-Rate table index.
This object is the unique index associated with each entry."
::= { efmCuPme2BReachRateEntry 1 }
efmCuPme2BEquivalentLength OBJECT-TYPE SYNTAX Unsigned32(0..8192) UNITS "m" MAX-ACCESS read-create STATUS current DESCRIPTION "Maximum allowed equivalent loop's physical length in meters for the specified data rates. An equivalent loop is a hypothetical 26AWG (0.4mm) loop with a perfect square root attenuation characteristic, without any
EFMCUPME2B等效长度对象类型语法Unsigned32（0..8192）单位“m”MAX-ACCESS read create STATUS current DESCRIPTION“指定数据速率下允许的最大等效环路物理长度（以米为单位）。等效环路是一个假设的26AWG（0.4mm）环路，具有完美的平方根衰减特性，没有任何
bridged taps."
::= { efmCuPme2BReachRateEntry 2 }
bridged taps."
::= { efmCuPme2BReachRateEntry 2 }
efmCuPme2BMaxDataRatePam16 OBJECT-TYPE
SYNTAX Unsigned32(0|192..5696)
UNITS "Kbps"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Maximum data rate for a 2BASE-TL PME at the specified
equivalent loop's length using TC-PAM16 encoding.
The value of zero means that TC-PAM16 encoding should not be
used at this distance."
::= { efmCuPme2BReachRateEntry 3 }
efmCuPme2BMaxDataRatePam16 OBJECT-TYPE
SYNTAX Unsigned32(0|192..5696)
UNITS "Kbps"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Maximum data rate for a 2BASE-TL PME at the specified
equivalent loop's length using TC-PAM16 encoding.
The value of zero means that TC-PAM16 encoding should not be
used at this distance."
::= { efmCuPme2BReachRateEntry 3 }
efmCuPme2BMaxDataRatePam32 OBJECT-TYPE
SYNTAX Unsigned32(0|192..5696)
UNITS "Kbps"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Maximum data rate for a 2BASE-TL PME at the specified
equivalent loop's length using TC-PAM32 encoding.
The value of zero means that TC-PAM32 encoding should not be
used at this distance."
::= { efmCuPme2BReachRateEntry 4 }
efmCuPme2BMaxDataRatePam32 OBJECT-TYPE
SYNTAX Unsigned32(0|192..5696)
UNITS "Kbps"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Maximum data rate for a 2BASE-TL PME at the specified
equivalent loop's length using TC-PAM32 encoding.
The value of zero means that TC-PAM32 encoding should not be
used at this distance."
::= { efmCuPme2BReachRateEntry 4 }
efmCuPme2BReachRateRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This object controls the creation, modification, or deletion of the associated entry in the efmCuPme2BReachRateTable per the semantics of RowStatus.
efmCuPme2BReachRateRowStatus对象类型语法RowStatus MAX-ACCESS read create STATUS current DESCRIPTION“此对象根据RowStatus的语义控制efmCuPme2BReachRateTable中关联项的创建、修改或删除。
If an 'active' entry is referenced via efmCuPme2BsMode instance(s), the entry MUST remain 'active'.
如果通过efmCuPme2BsMode实例引用了“活动”条目，则该条目必须保持“活动”。
An 'active' entry SHALL NOT be modified. In order to modify
an existing entry, it MUST be taken out of service (by setting
this object to 'notInService'), modified, and set 'active'
again."
::= { efmCuPme2BReachRateEntry 5 }
An 'active' entry SHALL NOT be modified. In order to modify
an existing entry, it MUST be taken out of service (by setting
this object to 'notInService'), modified, and set 'active'
again."
::= { efmCuPme2BReachRateEntry 5 }
-- 10PASS-TS specific PME group
--10PASS-TS特定PME组
efmCuPme10P OBJECT IDENTIFIER ::= { efmCuPme 6 }
efmCuPme10P OBJECT IDENTIFIER ::= { efmCuPme 6 }
efmCuPme10PProfileTable OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPme10PProfileEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table supports definitions of configuration profiles for
10PASS-TS PMEs.
The first 22 entries in this table SHALL always be defined as
follows (see 802.3ah Annex 62B.3, table 62B-1):
-------+--------+----+---------+-----+-----+---------------
Profile Bandplan UPBO BandNotch DRate URate Comment
Index PSDMask# p# p# p# p#
-------+--------+----+---------+-----+-----+---------------
1 1 3 2,6,10,11 20 20 default profile
2 13 5 0 20 20
3 1 1 0 20 20
4 16 0 0 100 100
5 16 0 0 70 50
6 6 0 0 50 10
7 17 0 0 30 30
8 8 0 0 30 5
9 4 0 0 25 25
10 4 0 0 15 15
11 23 0 0 10 10
12 23 0 0 5 5
13 16 0 2,5,9,11 100 100
14 16 0 2,5,9,11 70 50
15 6 0 2,6,10,11 50 10
16 17 0 2,5,9,11 30 30
17 8 0 2,6,10,11 30 5
18 4 0 2,6,10,11 25 25
19 4 0 2,6,10,11 15 15
20 23 0 2,5,9,11 10 10
21 23 0 2,5,9,11 5 5
22 30 0 0 200 50
-------+--------+----+---------+-----+-----+---------------
efmCuPme10PProfileTable OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPme10PProfileEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table supports definitions of configuration profiles for
10PASS-TS PMEs.
The first 22 entries in this table SHALL always be defined as
follows (see 802.3ah Annex 62B.3, table 62B-1):
-------+--------+----+---------+-----+-----+---------------
Profile Bandplan UPBO BandNotch DRate URate Comment
Index PSDMask# p# p# p# p#
-------+--------+----+---------+-----+-----+---------------
1 1 3 2,6,10,11 20 20 default profile
2 13 5 0 20 20
3 1 1 0 20 20
4 16 0 0 100 100
5 16 0 0 70 50
6 6 0 0 50 10
7 17 0 0 30 30
8 8 0 0 30 5
9 4 0 0 25 25
10 4 0 0 15 15
11 23 0 0 10 10
12 23 0 0 5 5
13 16 0 2,5,9,11 100 100
14 16 0 2,5,9,11 70 50
15 6 0 2,6,10,11 50 10
16 17 0 2,5,9,11 30 30
17 8 0 2,6,10,11 30 5
18 4 0 2,6,10,11 25 25
19 4 0 2,6,10,11 15 15
20 23 0 2,5,9,11 10 10
21 23 0 2,5,9,11 5 5
22 30 0 0 200 50
-------+--------+----+---------+-----+-----+---------------
These default entries SHALL be created during agent initialization and MUST NOT be deleted.
这些默认条目应在代理初始化期间创建，不得删除。
Entries following the first 22 can be dynamically created and deleted to provide custom administrative (configuration) profiles and automatic operating profiles.
可以动态创建和删除前22条之后的条目，以提供自定义管理（配置）配置文件和自动操作配置文件。
This table MUST be maintained in a persistent manner." REFERENCE
必须以持久的方式维护此表。”参考
"[802.3ah] Annex 62B.3, 30.11.2.1.6"
::= { efmCuPme10P 1 }
"[802.3ah] Annex 62B.3, 30.11.2.1.6"
::= { efmCuPme10P 1 }
efmCuPme10PProfileEntry OBJECT-TYPE SYNTAX EfmCuPme10PProfileEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Each entry corresponds to a single 10PASS-TS PME profile.
efmCuPme10PProfileEntry对象类型语法efmCuPme10PProfileEntry MAX-ACCESS不可访问状态当前描述“每个条目对应于单个10PASS-TS PME配置文件。
Each profile contains a set of parameters, used either for configuration or representation of a 10PASS-TS PME. In case a particular profile is referenced via the efmCuPmeAdminProfile object (or efmCuAdminProfile if efmCuPmeAdminProfile is zero), it represents the desired parameters for the 10PassTS-O PME initialization. If a profile is referenced via an efmCuPmeOperProfile object, it represents the current operating parameters of the PME.
每个配置文件包含一组参数，用于配置或表示10PASS-TS PME。如果通过efmCuPmeAdminProfile对象引用特定配置文件（如果efmCuPmeAdminProfile为零，则为efmCuAdminProfile），则它表示10PassTS-O PME初始化所需的参数。如果通过efmCuPmeOperProfile对象引用配置文件，则它表示PME的当前操作参数。
Profiles may be created/deleted using the row creation/
deletion mechanism via efmCuPme10PProfileRowStatus. If an
'active' entry is referenced, the entry MUST remain 'active'
until all references are removed.
Default entries MUST NOT be removed."
INDEX { efmCuPme10PProfileIndex }
::= { efmCuPme10PProfileTable 1 }
Profiles may be created/deleted using the row creation/
deletion mechanism via efmCuPme10PProfileRowStatus. If an
'active' entry is referenced, the entry MUST remain 'active'
until all references are removed.
Default entries MUST NOT be removed."
INDEX { efmCuPme10PProfileIndex }
::= { efmCuPme10PProfileTable 1 }
EfmCuPme10PProfileEntry ::=
SEQUENCE {
efmCuPme10PProfileIndex EfmProfileIndex,
efmCuPme10PProfileDescr SnmpAdminString,
efmCuPme10PBandplanPSDMskProfile INTEGER,
efmCuPme10PUPBOReferenceProfile INTEGER,
efmCuPme10PBandNotchProfiles BITS,
efmCuPme10PPayloadDRateProfile INTEGER,
efmCuPme10PPayloadURateProfile INTEGER,
efmCuPme10PProfileRowStatus RowStatus
}
EfmCuPme10PProfileEntry ::=
SEQUENCE {
efmCuPme10PProfileIndex EfmProfileIndex,
efmCuPme10PProfileDescr SnmpAdminString,
efmCuPme10PBandplanPSDMskProfile INTEGER,
efmCuPme10PUPBOReferenceProfile INTEGER,
efmCuPme10PBandNotchProfiles BITS,
efmCuPme10PPayloadDRateProfile INTEGER,
efmCuPme10PPayloadURateProfile INTEGER,
efmCuPme10PProfileRowStatus RowStatus
}
efmCuPme10PProfileIndex OBJECT-TYPE SYNTAX EfmProfileIndex MAX-ACCESS not-accessible STATUS current DESCRIPTION "10PASS-TS PME profile index. This object is the unique index associated with this profile. Entries in this table are referenced via efmCuAdminProfile or efmCuPmeAdminProfile."
efmCuPme10PProfileIndex对象类型语法EfmProfileIndex MAX-ACCESS不可访问状态当前描述“10PASS-TS PME配置文件索引。此对象是与此配置文件关联的唯一索引。此表中的项通过efmCuAdminProfile或EFMCUPMEDMINPROFILE引用。”
::= { efmCuPme10PProfileEntry 1 }
::= { efmCuPme10PProfileEntry 1 }
efmCuPme10PProfileDescr OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"A textual string containing information about a 10PASS-TS PME
profile. The string may include information about data rate
and spectral limitations of this particular profile."
::= { efmCuPme10PProfileEntry 2 }
efmCuPme10PProfileDescr OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"A textual string containing information about a 10PASS-TS PME
profile. The string may include information about data rate
and spectral limitations of this particular profile."
::= { efmCuPme10PProfileEntry 2 }
efmCuPme10PBandplanPSDMskProfile OBJECT-TYPE
SYNTAX INTEGER {
profile1(1),
profile2(2),
profile3(3),
profile4(4),
profile5(5),
profile6(6),
profile7(7),
profile8(8),
profile9(9),
profile10(10),
profile11(11),
profile12(12),
profile13(13),
profile14(14),
profile15(15),
profile16(16),
profile17(17),
profile18(18),
profile19(19),
profile20(20),
profile21(21),
profile22(22),
profile23(23),
profile24(24),
profile25(25),
profile26(26),
profile27(27),
profile28(28),
profile29(29),
profile30(30)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
efmCuPme10PBandplanPSDMskProfile OBJECT-TYPE
SYNTAX INTEGER {
profile1(1),
profile2(2),
profile3(3),
profile4(4),
profile5(5),
profile6(6),
profile7(7),
profile8(8),
profile9(9),
profile10(10),
profile11(11),
profile12(12),
profile13(13),
profile14(14),
profile15(15),
profile16(16),
profile17(17),
profile18(18),
profile19(19),
profile20(20),
profile21(21),
profile22(22),
profile23(23),
profile24(24),
profile25(25),
profile26(26),
profile27(27),
profile28(28),
profile29(29),
profile30(30)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The 10PASS-TS PME Bandplan and PSD Mask Profile, as specified
in 802.3ah Annex 62A, table 62A-1. Possible values are:
--------------+------------------------+------------+--------
Profile Name PSD Mask Bands G.993.1
0/1/2/3/4/5 Bandplan
--------------+------------------------+------------+--------
profile1(1) T1.424 FTTCab.M1 x/D/U/D/U A
profile2(2) T1.424 FTTEx.M1 x/D/U/D/U A
profile3(3) T1.424 FTTCab.M2 x/D/U/D/U A
profile4(4) T1.424 FTTEx.M2 x/D/U/D/U A
profile5(5) T1.424 FTTCab.M1 D/D/U/D/U A
profile6(6) T1.424 FTTEx.M1 D/D/U/D/U A
profile7(7) T1.424 FTTCab.M2 D/D/U/D/U A
profile8(8) T1.424 FTTEx.M2 D/D/U/D/U A
profile9(9) T1.424 FTTCab.M1 U/D/U/D/x A
profile10(10) T1.424 FTTEx.M1 U/D/U/D/x A
profile11(11) T1.424 FTTCab.M2 U/D/U/D/x A
profile12(12) T1.424 FTTEx.M2 U/D/U/D/x A
profile13(13) TS 101 270-1 Pcab.M1.A x/D/U/D/U B
profile14(14) TS 101 270-1 Pcab.M1.B x/D/U/D/U B
profile15(15) TS 101 270-1 Pex.P1.M1 x/D/U/D/U B
profile16(16) TS 101 270-1 Pex.P2.M1 x/D/U/D/U B
profile17(17) TS 101 270-1 Pcab.M2 x/D/U/D/U B
profile18(18) TS 101 270-1 Pex.P1.M2 x/D/U/D/U B
profile19(19) TS 101 270-1 Pex.P2.M2 x/D/U/D/U B
profile20(20) TS 101 270-1 Pcab.M1.A U/D/U/D/x B
profile21(21) TS 101 270-1 Pcab.M1.B U/D/U/D/x B
profile22(22) TS 101 270-1 Pex.P1.M1 U/D/U/D/x B
profile23(23) TS 101 270-1 Pex.P2.M1 U/D/U/D/x B
profile24(24) TS 101 270-1 Pcab.M2 U/D/U/D/x B
profile25(25) TS 101 270-1 Pex.P1.M2 U/D/U/D/x B
profile26(26) TS 101 270-1 Pex.P2.M2 U/D/U/D/x B
profile27(27) G.993.1 F.1.2.1 x/D/U/D/U Annex F
profile28(28) G.993.1 F.1.2.2 x/D/U/D/U Annex F
profile29(29) G.993.1 F.1.2.3 x/D/U/D/U Annex F
profile30(30) T1.424 FTTCab.M1 (ext.) x/D/U/D/U/D Annex A
--------------+------------------------+------------+--------
"
REFERENCE
"[802.3ah] Annex 62A"
::= { efmCuPme10PProfileEntry 3 }
"The 10PASS-TS PME Bandplan and PSD Mask Profile, as specified
in 802.3ah Annex 62A, table 62A-1. Possible values are:
--------------+------------------------+------------+--------
Profile Name PSD Mask Bands G.993.1
0/1/2/3/4/5 Bandplan
--------------+------------------------+------------+--------
profile1(1) T1.424 FTTCab.M1 x/D/U/D/U A
profile2(2) T1.424 FTTEx.M1 x/D/U/D/U A
profile3(3) T1.424 FTTCab.M2 x/D/U/D/U A
profile4(4) T1.424 FTTEx.M2 x/D/U/D/U A
profile5(5) T1.424 FTTCab.M1 D/D/U/D/U A
profile6(6) T1.424 FTTEx.M1 D/D/U/D/U A
profile7(7) T1.424 FTTCab.M2 D/D/U/D/U A
profile8(8) T1.424 FTTEx.M2 D/D/U/D/U A
profile9(9) T1.424 FTTCab.M1 U/D/U/D/x A
profile10(10) T1.424 FTTEx.M1 U/D/U/D/x A
profile11(11) T1.424 FTTCab.M2 U/D/U/D/x A
profile12(12) T1.424 FTTEx.M2 U/D/U/D/x A
profile13(13) TS 101 270-1 Pcab.M1.A x/D/U/D/U B
profile14(14) TS 101 270-1 Pcab.M1.B x/D/U/D/U B
profile15(15) TS 101 270-1 Pex.P1.M1 x/D/U/D/U B
profile16(16) TS 101 270-1 Pex.P2.M1 x/D/U/D/U B
profile17(17) TS 101 270-1 Pcab.M2 x/D/U/D/U B
profile18(18) TS 101 270-1 Pex.P1.M2 x/D/U/D/U B
profile19(19) TS 101 270-1 Pex.P2.M2 x/D/U/D/U B
profile20(20) TS 101 270-1 Pcab.M1.A U/D/U/D/x B
profile21(21) TS 101 270-1 Pcab.M1.B U/D/U/D/x B
profile22(22) TS 101 270-1 Pex.P1.M1 U/D/U/D/x B
profile23(23) TS 101 270-1 Pex.P2.M1 U/D/U/D/x B
profile24(24) TS 101 270-1 Pcab.M2 U/D/U/D/x B
profile25(25) TS 101 270-1 Pex.P1.M2 U/D/U/D/x B
profile26(26) TS 101 270-1 Pex.P2.M2 U/D/U/D/x B
profile27(27) G.993.1 F.1.2.1 x/D/U/D/U Annex F
profile28(28) G.993.1 F.1.2.2 x/D/U/D/U Annex F
profile29(29) G.993.1 F.1.2.3 x/D/U/D/U Annex F
profile30(30) T1.424 FTTCab.M1 (ext.) x/D/U/D/U/D Annex A
--------------+------------------------+------------+--------
"
REFERENCE
"[802.3ah] Annex 62A"
::= { efmCuPme10PProfileEntry 3 }
efmCuPme10PUPBOReferenceProfile OBJECT-TYPE SYNTAX INTEGER { profile0(0), profile1(1), profile2(2), profile3(3),
efmCuPme10PUPBOReferenceProfile对象类型语法整数{profile0（0）、profile1（1）、profile2（2）、profile3（3），
profile4(4),
profile5(5),
profile6(6),
profile7(7),
profile8(8),
profile9(9)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The 10PASS-TS PME Upstream Power Back-Off (UPBO) Reference
PSD Profile, as specified in 802.3 Annex 62A, table 62A-3.
Possible values are:
------------+-----------------------------
Profile Name Reference PSD
------------+-----------------------------
profile0(0) no profile
profile1(1) T1.424 Noise A M1
profile2(2) T1.424 Noise A M2
profile3(3) T1.424 Noise F M1
profile4(4) T1.424 Noise F M2
profile5(5) TS 101 270-1 Noise A&B
profile6(6) TS 101 270-1 Noise C
profile7(7) TS 101 270-1 Noise D
profile8(8) TS 101 270-1 Noise E
profile9(9) TS 101 270-1 Noise F
------------+-----------------------------
"
REFERENCE
"[802.3ah] Annex 62A.3.5"
::= { efmCuPme10PProfileEntry 4 }
profile4(4),
profile5(5),
profile6(6),
profile7(7),
profile8(8),
profile9(9)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The 10PASS-TS PME Upstream Power Back-Off (UPBO) Reference
PSD Profile, as specified in 802.3 Annex 62A, table 62A-3.
Possible values are:
------------+-----------------------------
Profile Name Reference PSD
------------+-----------------------------
profile0(0) no profile
profile1(1) T1.424 Noise A M1
profile2(2) T1.424 Noise A M2
profile3(3) T1.424 Noise F M1
profile4(4) T1.424 Noise F M2
profile5(5) TS 101 270-1 Noise A&B
profile6(6) TS 101 270-1 Noise C
profile7(7) TS 101 270-1 Noise D
profile8(8) TS 101 270-1 Noise E
profile9(9) TS 101 270-1 Noise F
------------+-----------------------------
"
REFERENCE
"[802.3ah] Annex 62A.3.5"
::= { efmCuPme10PProfileEntry 4 }
efmCuPme10PBandNotchProfiles OBJECT-TYPE
SYNTAX BITS {
profile0(0),
profile1(1),
profile2(2),
profile3(3),
profile4(4),
profile5(5),
profile6(6),
profile7(7),
profile8(8),
profile9(9),
profile10(10),
profile11(11)
}
MAX-ACCESS read-create
efmCuPme10PBandNotchProfiles OBJECT-TYPE
SYNTAX BITS {
profile0(0),
profile1(1),
profile2(2),
profile3(3),
profile4(4),
profile5(5),
profile6(6),
profile7(7),
profile8(8),
profile9(9),
profile10(10),
profile11(11)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The 10PASS-TS PME Egress Control Band Notch Profile bitmap,
as specified in 802.3 Annex 62A, table 62A-4. Possible values
are:
--------------+--------+------+------------+------+------
Profile Name G.991.3 T1.424 TS 101 270-1 StartF EndF
table table table (MHz) (MHz)
--------------+--------+------+------------+------+------
profile0(0) no profile
profile1(1) F-5 #01 - - 1.810 1.825
profile2(2) 6-2 15-1 17 1.810 2.000
profile3(3) F-5 #02 - - 1.907 1.912
profile4(4) F-5 #03 - - 3.500 3.575
profile5(5) 6-2 - 17 3.500 3.800
profile6(6) - 15-1 - 3.500 4.000
profile7(7) F-5 #04 - - 3.747 3.754
profile8(8) F-5 #05 - - 3.791 3.805
profile9(9) 6-2 - 17 7.000 7.100
profile10(10) F-5 #06 15-1 - 7.000 7.300
profile11(11) 6-2 15-1 1 10.100 10.150
--------------+--------+------+------------+------+------
STATUS current
DESCRIPTION
"The 10PASS-TS PME Egress Control Band Notch Profile bitmap,
as specified in 802.3 Annex 62A, table 62A-4. Possible values
are:
--------------+--------+------+------------+------+------
Profile Name G.991.3 T1.424 TS 101 270-1 StartF EndF
table table table (MHz) (MHz)
--------------+--------+------+------------+------+------
profile0(0) no profile
profile1(1) F-5 #01 - - 1.810 1.825
profile2(2) 6-2 15-1 17 1.810 2.000
profile3(3) F-5 #02 - - 1.907 1.912
profile4(4) F-5 #03 - - 3.500 3.575
profile5(5) 6-2 - 17 3.500 3.800
profile6(6) - 15-1 - 3.500 4.000
profile7(7) F-5 #04 - - 3.747 3.754
profile8(8) F-5 #05 - - 3.791 3.805
profile9(9) 6-2 - 17 7.000 7.100
profile10(10) F-5 #06 15-1 - 7.000 7.300
profile11(11) 6-2 15-1 1 10.100 10.150
--------------+--------+------+------------+------+------
Any combination of profiles can be specified by ORing
individual profiles, for example, a value of 0x2230 selects
profiles 2, 6, 10, and 11."
REFERENCE
"[802.3ah] Annex 62A.3.5"
::= { efmCuPme10PProfileEntry 5 }
Any combination of profiles can be specified by ORing
individual profiles, for example, a value of 0x2230 selects
profiles 2, 6, 10, and 11."
REFERENCE
"[802.3ah] Annex 62A.3.5"
::= { efmCuPme10PProfileEntry 5 }
efmCuPme10PPayloadDRateProfile OBJECT-TYPE
SYNTAX INTEGER {
profile5(5),
profile10(10),
profile15(15),
profile20(20),
profile25(25),
profile30(30),
profile50(50),
profile70(70),
profile100(100),
profile140(140),
profile200(200)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The 10PASS-TS PME Downstream Payload Rate Profile, as
efmCuPme10PPayloadDRateProfile OBJECT-TYPE
SYNTAX INTEGER {
profile5(5),
profile10(10),
profile15(15),
profile20(20),
profile25(25),
profile30(30),
profile50(50),
profile70(70),
profile100(100),
profile140(140),
profile200(200)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The 10PASS-TS PME Downstream Payload Rate Profile, as
specified in 802.3 Annex 62A. Possible values are:
profile5(5) - 2.5 Mbps
profile10(10) - 5 Mbps
profile15(15) - 7.5 Mbps
profile20(20) - 10 Mbps
profile25(25) - 12.5 Mbps
profile30(30) - 15 Mbps
profile50(50) - 25 Mbps
profile70(70) - 35 Mbps
profile100(100) - 50 Mbps
profile140(140) - 70 Mbps
profile200(200) - 100 Mbps
specified in 802.3 Annex 62A. Possible values are:
profile5(5) - 2.5 Mbps
profile10(10) - 5 Mbps
profile15(15) - 7.5 Mbps
profile20(20) - 10 Mbps
profile25(25) - 12.5 Mbps
profile30(30) - 15 Mbps
profile50(50) - 25 Mbps
profile70(70) - 35 Mbps
profile100(100) - 50 Mbps
profile140(140) - 70 Mbps
profile200(200) - 100 Mbps
Each value represents a target for the PME's Downstream
Payload Bitrate as seen at the MII. If the payload rate of
the selected profile cannot be achieved based on the loop
environment, bandplan, and PSD mask, the PME initialization
SHALL fail."
REFERENCE
"[802.3ah] Annex 62A.3.6"
::= { efmCuPme10PProfileEntry 6 }
Each value represents a target for the PME's Downstream
Payload Bitrate as seen at the MII. If the payload rate of
the selected profile cannot be achieved based on the loop
environment, bandplan, and PSD mask, the PME initialization
SHALL fail."
REFERENCE
"[802.3ah] Annex 62A.3.6"
::= { efmCuPme10PProfileEntry 6 }
efmCuPme10PPayloadURateProfile OBJECT-TYPE
SYNTAX INTEGER {
profile5(5),
profile10(10),
profile15(15),
profile20(20),
profile25(25),
profile30(30),
profile50(50),
profile70(70),
profile100(100)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The 10PASS-TS PME Upstream Payload Rate Profile, as specified
in 802.3 Annex 62A. Possible values are:
profile5(5) - 2.5 Mbps
profile10(10) - 5 Mbps
profile15(15) - 7.5 Mbps
profile20(20) - 10 Mbps
profile25(25) - 12.5 Mbps
profile30(30) - 15 Mbps
profile50(50) - 25 Mbps
profile70(70) - 35 Mbps
profile100(100) - 50 Mbps
efmCuPme10PPayloadURateProfile OBJECT-TYPE
SYNTAX INTEGER {
profile5(5),
profile10(10),
profile15(15),
profile20(20),
profile25(25),
profile30(30),
profile50(50),
profile70(70),
profile100(100)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The 10PASS-TS PME Upstream Payload Rate Profile, as specified
in 802.3 Annex 62A. Possible values are:
profile5(5) - 2.5 Mbps
profile10(10) - 5 Mbps
profile15(15) - 7.5 Mbps
profile20(20) - 10 Mbps
profile25(25) - 12.5 Mbps
profile30(30) - 15 Mbps
profile50(50) - 25 Mbps
profile70(70) - 35 Mbps
profile100(100) - 50 Mbps
Each value represents a target for the PME's Upstream Payload
Bitrate as seen at the MII. If the payload rate of the
selected profile cannot be achieved based on the loop
environment, bandplan, and PSD mask, the PME initialization
SHALL fail."
REFERENCE
"[802.3ah] Annex 62A.3.6"
::= { efmCuPme10PProfileEntry 7 }
Each value represents a target for the PME's Upstream Payload
Bitrate as seen at the MII. If the payload rate of the
selected profile cannot be achieved based on the loop
environment, bandplan, and PSD mask, the PME initialization
SHALL fail."
REFERENCE
"[802.3ah] Annex 62A.3.6"
::= { efmCuPme10PProfileEntry 7 }
efmCuPme10PProfileRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This object controls creation, modification, or deletion of the associated entry in efmCuPme10PProfileTable per the semantics of RowStatus.
efmCuPme10PProfileRowStatus对象类型语法RowStatus MAX-ACCESS read create STATUS current DESCRIPTION“此对象根据RowStatus的语义控制efmCuPme10PProfileTable中关联项的创建、修改或删除。
If an active entry is referenced via efmCuAdminProfile or efmCuPmeAdminProfile, the entry MUST remain 'active' until all references are removed.
如果通过efmCuAdminProfile或efmCuPmeAdminProfile引用活动条目，则该条目必须保持“活动”，直到删除所有引用。
An 'active' entry SHALL NOT be modified. In order to modify
an existing entry, it MUST be taken out of service (by setting
this object to 'notInService'), modified, and set 'active'
again."
::= { efmCuPme10PProfileEntry 8 }
An 'active' entry SHALL NOT be modified. In order to modify
an existing entry, it MUST be taken out of service (by setting
this object to 'notInService'), modified, and set 'active'
again."
::= { efmCuPme10PProfileEntry 8 }
efmCuPme10PStatusTable OBJECT-TYPE SYNTAX SEQUENCE OF EfmCuPme10PStatusEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table provides status information of EFMCu 10PASS-TS PMEs (modems).
efmCuPme10PStatusTable EfmCuPme10PStatusEntry MAX-ACCESS不可访问状态当前说明“此表提供EFMCu 10PASS-TS PME（调制解调器）的状态信息。
This table contains live data from the equipment. As such,
it is NOT persistent."
::= { efmCuPme10P 2 }
This table contains live data from the equipment. As such,
it is NOT persistent."
::= { efmCuPme10P 2 }
efmCuPme10PStatusEntry OBJECT-TYPE SYNTAX EfmCuPme10PStatusEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the EFMCu 10PASS-TS PME Status table." INDEX { ifIndex }
efmCuPme10PStatusEntry对象类型语法efmCuPme10PStatusEntry MAX-ACCESS不可访问状态当前描述“EFMCu 10PASS-TS PME状态表中的一个条目。”索引{ifIndex}
::= { efmCuPme10PStatusTable 1 }
::= { efmCuPme10PStatusTable 1 }
EfmCuPme10PStatusEntry ::=
SEQUENCE {
efmCuPme10PFECCorrectedBlocks Counter32,
efmCuPme10PFECUncorrectedBlocks Counter32
}
EfmCuPme10PStatusEntry ::=
SEQUENCE {
efmCuPme10PFECCorrectedBlocks Counter32,
efmCuPme10PFECUncorrectedBlocks Counter32
}
efmCuPme10PFECCorrectedBlocks OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of received and corrected Forward Error Correction (FEC) codewords in this 10PASS-TS PME.
efmCuPme10PFECCorrectedBlocks对象类型语法计数器32 MAX-ACCESS只读状态当前描述“此10PASS-TS PME中接收和更正的前向纠错（FEC）码字数。
This object maps to the aPMEFECCorrectedBlocks attribute in Clause 30.
此对象映射到第30条中的apmefectcorrectedblocks属性。
If a Clause 45 MDIO Interface to the PMA/PMD is present, then this object maps to the 10P FEC correctable errors register.
如果存在PMA/PMD的第45条MDIO接口，则该对象映射到10P FEC可纠正错误寄存器。
Discontinuities in the value of this counter can occur at
re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime,
defined in IF-MIB."
REFERENCE
"[802.3ah] 45.2.1.22, 30.11.2.1.8"
::= { efmCuPme10PStatusEntry 1 }
Discontinuities in the value of this counter can occur at
re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime,
defined in IF-MIB."
REFERENCE
"[802.3ah] 45.2.1.22, 30.11.2.1.8"
::= { efmCuPme10PStatusEntry 1 }
efmCuPme10PFECUncorrectedBlocks OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of received uncorrectable FEC codewords in this 10PASS-TS PME.
efmCuPme10PFECUncorrectedBlocks对象类型语法计数器32 MAX-ACCESS只读状态当前描述“此10PASS-TS PME中接收到的不可纠正FEC码字数。
This object maps to the aPMEFECUncorrectableBlocks attribute in Clause 30.
此对象映射到第30条中的apmefecnorrectableblocks属性。
If a Clause 45 MDIO Interface to the PMA/PMD is present, then this object maps to the 10P FEC uncorrectable errors register.
如果存在PMA/PMD的第45条MDIO接口，则该对象映射到10P FEC不可纠正错误寄存器。
Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times
在管理系统重新初始化时，以及在其他时间，可能会出现此计数器值的不连续性
as indicated by the value of ifCounterDiscontinuityTime,
defined in IF-MIB."
REFERENCE
"[802.3ah] 45.2.1.23, 30.11.2.1.9"
::= { efmCuPme10PStatusEntry 2 }
as indicated by the value of ifCounterDiscontinuityTime,
defined in IF-MIB."
REFERENCE
"[802.3ah] 45.2.1.23, 30.11.2.1.9"
::= { efmCuPme10PStatusEntry 2 }
-- -- Conformance Statements --
----一致性声明--
efmCuGroups OBJECT IDENTIFIER ::= { efmCuConformance 1 }
efmCuGroups OBJECT IDENTIFIER ::= { efmCuConformance 1 }
efmCuCompliances OBJECT IDENTIFIER ::= { efmCuConformance 2 }
efmCuCompliances OBJECT IDENTIFIER ::= { efmCuConformance 2 }
-- Object Groups
--对象组
efmCuBasicGroup OBJECT-GROUP
OBJECTS {
efmCuPAFSupported,
efmCuAdminProfile,
efmCuTargetDataRate,
efmCuTargetSnrMgn,
efmCuAdaptiveSpectra,
efmCuPortSide,
efmCuFltStatus
}
STATUS current
DESCRIPTION
"A collection of objects representing management information
common for all types of EFMCu ports."
::= { efmCuGroups 1 }
efmCuBasicGroup OBJECT-GROUP
OBJECTS {
efmCuPAFSupported,
efmCuAdminProfile,
efmCuTargetDataRate,
efmCuTargetSnrMgn,
efmCuAdaptiveSpectra,
efmCuPortSide,
efmCuFltStatus
}
STATUS current
DESCRIPTION
"A collection of objects representing management information
common for all types of EFMCu ports."
::= { efmCuGroups 1 }
efmCuPAFGroup OBJECT-GROUP
OBJECTS {
efmCuPeerPAFSupported,
efmCuPAFCapacity,
efmCuPeerPAFCapacity,
efmCuPAFAdminState,
efmCuPAFDiscoveryCode,
efmCuPAFRemoteDiscoveryCode,
efmCuNumPMEs
}
STATUS current
DESCRIPTION
"A collection of objects supporting OPTIONAL PME
Aggregation Function (PAF) and PAF discovery in EFMCu ports."
::= { efmCuGroups 2 }
efmCuPAFGroup OBJECT-GROUP
OBJECTS {
efmCuPeerPAFSupported,
efmCuPAFCapacity,
efmCuPeerPAFCapacity,
efmCuPAFAdminState,
efmCuPAFDiscoveryCode,
efmCuPAFRemoteDiscoveryCode,
efmCuNumPMEs
}
STATUS current
DESCRIPTION
"A collection of objects supporting OPTIONAL PME
Aggregation Function (PAF) and PAF discovery in EFMCu ports."
::= { efmCuGroups 2 }
efmCuPAFErrorsGroup OBJECT-GROUP
OBJECTS {
efmCuPAFInErrors,
efmCuPAFInSmallFragments,
efmCuPAFInLargeFragments,
efmCuPAFInBadFragments,
efmCuPAFInLostFragments,
efmCuPAFInLostStarts,
efmCuPAFInLostEnds,
efmCuPAFInOverflows
}
STATUS current
DESCRIPTION
"A collection of objects supporting OPTIONAL error counters
of PAF on EFMCu ports."
::= { efmCuGroups 3 }
efmCuPAFErrorsGroup OBJECT-GROUP
OBJECTS {
efmCuPAFInErrors,
efmCuPAFInSmallFragments,
efmCuPAFInLargeFragments,
efmCuPAFInBadFragments,
efmCuPAFInLostFragments,
efmCuPAFInLostStarts,
efmCuPAFInLostEnds,
efmCuPAFInOverflows
}
STATUS current
DESCRIPTION
"A collection of objects supporting OPTIONAL error counters
of PAF on EFMCu ports."
::= { efmCuGroups 3 }
efmCuPmeGroup OBJECT-GROUP
OBJECTS {
efmCuPmeAdminProfile,
efmCuPmeOperStatus,
efmCuPmeFltStatus,
efmCuPmeSubTypesSupported,
efmCuPmeAdminSubType,
efmCuPmeOperSubType,
efmCuPAFRemoteDiscoveryCode,
efmCuPmeOperProfile,
efmCuPmeSnrMgn,
efmCuPmePeerSnrMgn,
efmCuPmeLineAtn,
efmCuPmePeerLineAtn,
efmCuPmeEquivalentLength,
efmCuPmeTCCodingErrors,
efmCuPmeTCCrcErrors,
efmCuPmeThreshLineAtn,
efmCuPmeThreshSnrMgn
}
STATUS current
DESCRIPTION
"A collection of objects providing information about
a 2BASE-TL/10PASS-TS PME."
::= { efmCuGroups 4 }
efmCuPmeGroup OBJECT-GROUP
OBJECTS {
efmCuPmeAdminProfile,
efmCuPmeOperStatus,
efmCuPmeFltStatus,
efmCuPmeSubTypesSupported,
efmCuPmeAdminSubType,
efmCuPmeOperSubType,
efmCuPAFRemoteDiscoveryCode,
efmCuPmeOperProfile,
efmCuPmeSnrMgn,
efmCuPmePeerSnrMgn,
efmCuPmeLineAtn,
efmCuPmePeerLineAtn,
efmCuPmeEquivalentLength,
efmCuPmeTCCodingErrors,
efmCuPmeTCCrcErrors,
efmCuPmeThreshLineAtn,
efmCuPmeThreshSnrMgn
}
STATUS current
DESCRIPTION
"A collection of objects providing information about
a 2BASE-TL/10PASS-TS PME."
::= { efmCuGroups 4 }
efmCuAlarmConfGroup OBJECT-GROUP OBJECTS { efmCuThreshLowRate, efmCuLowRateCrossingEnable, efmCuPmeThreshLineAtn,
efmCuAlarmConfGroup对象组对象{efmCuThreshLowRate，efmCuLowRateCrossingEnable，efmCuPmeThreshLineAtn，
efmCuPmeLineAtnCrossingEnable,
efmCuPmeThreshSnrMgn,
efmCuPmeSnrMgnCrossingEnable,
efmCuPmeDeviceFaultEnable,
efmCuPmeConfigInitFailEnable,
efmCuPmeProtocolInitFailEnable
}
STATUS current
DESCRIPTION
"A collection of objects supporting configuration of alarm
thresholds and notifications in EFMCu ports."
::= { efmCuGroups 5 }
efmCuPmeLineAtnCrossingEnable,
efmCuPmeThreshSnrMgn,
efmCuPmeSnrMgnCrossingEnable,
efmCuPmeDeviceFaultEnable,
efmCuPmeConfigInitFailEnable,
efmCuPmeProtocolInitFailEnable
}
STATUS current
DESCRIPTION
"A collection of objects supporting configuration of alarm
thresholds and notifications in EFMCu ports."
::= { efmCuGroups 5 }
efmCuNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS {
efmCuLowRateCrossing,
efmCuPmeLineAtnCrossing,
efmCuPmeSnrMgnCrossing,
efmCuPmeDeviceFault,
efmCuPmeConfigInitFailure,
efmCuPmeProtocolInitFailure
}
STATUS current
DESCRIPTION
"This group supports notifications of significant conditions
associated with EFMCu ports."
::= { efmCuGroups 6 }
efmCuNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS {
efmCuLowRateCrossing,
efmCuPmeLineAtnCrossing,
efmCuPmeSnrMgnCrossing,
efmCuPmeDeviceFault,
efmCuPmeConfigInitFailure,
efmCuPmeProtocolInitFailure
}
STATUS current
DESCRIPTION
"This group supports notifications of significant conditions
associated with EFMCu ports."
::= { efmCuGroups 6 }
efmCuPme2BProfileGroup OBJECT-GROUP
OBJECTS {
efmCuPme2BProfileDescr,
efmCuPme2BRegion,
efmCuPme2BsMode,
efmCuPme2BMinDataRate,
efmCuPme2BMaxDataRate,
efmCuPme2BPower,
efmCuPme2BConstellation,
efmCuPme2BProfileRowStatus,
efmCuPme2BsModeDescr,
efmCuPme2BsModeRowStatus,
efmCuPme2BEquivalentLength,
efmCuPme2BMaxDataRatePam16,
efmCuPme2BMaxDataRatePam32,
efmCuPme2BReachRateRowStatus
}
STATUS current
DESCRIPTION
"A collection of objects that constitute a configuration
efmCuPme2BProfileGroup OBJECT-GROUP
OBJECTS {
efmCuPme2BProfileDescr,
efmCuPme2BRegion,
efmCuPme2BsMode,
efmCuPme2BMinDataRate,
efmCuPme2BMaxDataRate,
efmCuPme2BPower,
efmCuPme2BConstellation,
efmCuPme2BProfileRowStatus,
efmCuPme2BsModeDescr,
efmCuPme2BsModeRowStatus,
efmCuPme2BEquivalentLength,
efmCuPme2BMaxDataRatePam16,
efmCuPme2BMaxDataRatePam32,
efmCuPme2BReachRateRowStatus
}
STATUS current
DESCRIPTION
"A collection of objects that constitute a configuration
profile for configuration of 2BASE-TL ports."
::= { efmCuGroups 7}
profile for configuration of 2BASE-TL ports."
::= { efmCuGroups 7}
efmCuPme10PProfileGroup OBJECT-GROUP
OBJECTS {
efmCuPme10PProfileDescr,
efmCuPme10PBandplanPSDMskProfile,
efmCuPme10PUPBOReferenceProfile,
efmCuPme10PBandNotchProfiles,
efmCuPme10PPayloadDRateProfile,
efmCuPme10PPayloadURateProfile,
efmCuPme10PProfileRowStatus
}
STATUS current
DESCRIPTION
"A collection of objects that constitute a configuration
profile for configuration of 10PASS-TS ports."
::= { efmCuGroups 8 }
efmCuPme10PProfileGroup OBJECT-GROUP
OBJECTS {
efmCuPme10PProfileDescr,
efmCuPme10PBandplanPSDMskProfile,
efmCuPme10PUPBOReferenceProfile,
efmCuPme10PBandNotchProfiles,
efmCuPme10PPayloadDRateProfile,
efmCuPme10PPayloadURateProfile,
efmCuPme10PProfileRowStatus
}
STATUS current
DESCRIPTION
"A collection of objects that constitute a configuration
profile for configuration of 10PASS-TS ports."
::= { efmCuGroups 8 }
efmCuPme10PStatusGroup OBJECT-GROUP
OBJECTS {
efmCuPme10PFECCorrectedBlocks,
efmCuPme10PFECUncorrectedBlocks
}
STATUS current
DESCRIPTION
"A collection of objects providing status information
specific to 10PASS-TS PMEs."
::= { efmCuGroups 9 }
efmCuPme10PStatusGroup OBJECT-GROUP
OBJECTS {
efmCuPme10PFECCorrectedBlocks,
efmCuPme10PFECUncorrectedBlocks
}
STATUS current
DESCRIPTION
"A collection of objects providing status information
specific to 10PASS-TS PMEs."
::= { efmCuGroups 9 }
-- Compliance Statements
--合规声明
efmCuCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for 2BASE-TL/10PASS-TS interfaces. Compliance with the following external compliance statements is REQUIRED:
efmCuCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION“2BASE-TL/10PASS-TS接口的符合性声明。需要符合以下外部符合性声明：
MIB Module Compliance Statement
---------- --------------------
IF-MIB ifCompliance3
EtherLike-MIB dot3Compliance2
MAU-MIB mauModIfCompl3
MIB Module Compliance Statement
---------- --------------------
IF-MIB ifCompliance3
EtherLike-MIB dot3Compliance2
MAU-MIB mauModIfCompl3
Compliance with the following external compliance statements is OPTIONAL for implementations supporting PME Aggregation Function (PAF) with flexible cross-connect between the PCS
对于支持具有PC间灵活交叉连接的PME聚合功能（PAF）的实施，遵守以下外部合规性声明是可选的
and PME ports:
和港口及港口设备：
MIB Module Compliance Statement
---------- --------------------
IF-INVERTED-STACK-MIB ifInvCompliance
IF-CAP-STACK-MIB ifCapStackCompliance"
MIB Module Compliance Statement
---------- --------------------
IF-INVERTED-STACK-MIB ifInvCompliance
IF-CAP-STACK-MIB ifCapStackCompliance"
MODULE -- this module
MANDATORY-GROUPS {
efmCuBasicGroup,
efmCuPmeGroup,
efmCuAlarmConfGroup,
efmCuNotificationGroup
}
MODULE -- this module
MANDATORY-GROUPS {
efmCuBasicGroup,
efmCuPmeGroup,
efmCuAlarmConfGroup,
efmCuNotificationGroup
}
GROUP efmCuPme2BProfileGroup DESCRIPTION "Support for this group is only required for implementations supporting 2BASE-TL PHY."
组efmCuPme2BProfileGroup DESCRIPTION“仅支持2BASE-TL PHY的实现需要对此组的支持。”
GROUP efmCuPme10PProfileGroup DESCRIPTION "Support for this group is only required for implementations supporting 10PASS-TS PHY."
组efmCuPme10PProfileGroup DESCRIPTION“仅支持10PASS-TS PHY的实现需要对此组的支持。”
GROUP efmCuPAFGroup DESCRIPTION "Support for this group is only required for implementations supporting PME Aggregation Function (PAF)."
组efmCuPAFGroup DESCRIPTION“仅支持PME聚合功能（PAF）的实现需要对该组的支持。”
GROUP efmCuPAFErrorsGroup DESCRIPTION "Support for this group is OPTIONAL for implementations supporting PME Aggregation Function (PAF)."
组efmCuPAFErrorsGroup DESCRIPTION“对于支持PME聚合功能（PAF）的实现，对该组的支持是可选的。”
GROUP efmCuPme10PStatusGroup DESCRIPTION "Support for this group is OPTIONAL for implementations supporting 10PASS-TS PHY."
组efmCuPme10PStatusGroup DESCRIPTION“对于支持10PASS-TS PHY的实现，对该组的支持是可选的。”
OBJECT efmCuPmeSubTypesSupported
SYNTAX BITS {
ieee2BaseTLO(0),
ieee2BaseTLR(1),
ieee10PassTSO(2),
ieee10PassTSR(3)
}
DESCRIPTION
OBJECT efmCuPmeSubTypesSupported
SYNTAX BITS {
ieee2BaseTLO(0),
ieee2BaseTLR(1),
ieee10PassTSO(2),
ieee10PassTSR(3)
}
DESCRIPTION
"Support for all subtypes is not required. However, at least one value SHALL be supported."
不需要支持所有子类型。但是，至少应支持一个值
OBJECT efmCuPmeAdminSubType MIN-ACCESS read-only DESCRIPTION "Write access is not required (needed only for PMEs supporting more than a single subtype, e.g., ieee2BaseTLO and ieee2BaseTLR or ieee10PassTSO and ieee10PassTSR)."
对象efmCuPmeAdminSubType MIN-ACCESS只读说明“不需要写访问权限（仅支持多个子类型的PME需要，例如ieee2BaseTLO和ieee2BaseTLR或ieee10PassTSO和ieee10PassTSR）。”
OBJECT efmCuTargetSnrMgn MIN-ACCESS read-only DESCRIPTION "Write access is OPTIONAL. For PHYs without write access, the target SNR margin SHALL be fixed at 5dB for 2BASE-TL and 6dB for 10PASS-TS."
对象efmCuTargetSnrMgn MIN-ACCESS只读说明“写访问是可选的。对于没有写访问的PHY，2BASE-TL的目标SNR裕度应固定为5dB，10PASS-TS的目标SNR裕度应固定为6dB。”
OBJECT efmCuAdaptiveSpectra MIN-ACCESS read-only DESCRIPTION "Write access is OPTIONAL. For PHYs without write access, the default value SHOULD be false."
对象efmCuAdaptiveSpectra MIN-ACCESS只读说明“写访问是可选的。对于没有写访问的PHY，默认值应为false。”
::= { efmCuCompliances 1 }
END
::= { efmCuCompliances 1 }
END
There is a number of managed objects defined in the EFM-CU-MIB module that have a MAX-ACCESS clause of read-write or read-create. Most objects are writeable only when the link is Down. Writing to these objects can have potentially disruptive effects on network operation, for example:
EFM-CU-MIB模块中定义了许多托管对象，这些对象的MAX-ACCESS子句为read-write或read-create。大多数对象只有在链接关闭时才可写。写入这些对象可能会对网络运行产生潜在的破坏性影响，例如：
o Changing of efmCuPmeAdminSubType may lead to a potential locking of the link, as peer PMEs of the same subtype cannot exchange handshake messages.
o 更改efmCuPmeAdminSubType可能会导致链路锁定，因为相同子类型的对等PME无法交换握手消息。
o Changing of efmCuPAFAdminState to enabled may lead to a potential locking of the link, if the peer PHY does not support PAF.
o 如果对等PHY不支持PAF，将efmCuPAFAdminState更改为enabled可能会导致链路锁定。
o Changing of efmCuPAFDiscoveryCode, before the discovery operation, may lead to a wrongful discovery, for example, when two -O ports are connected to the same multi-PME -R port and both -O ports have the same Discovery register value.
o 在发现操作之前更改efmCuPAFDiscoveryCode可能会导致错误发现，例如，当两个-O端口连接到同一个多PME-R端口并且两个-O端口具有相同的发现寄存器值时。
o Changing PCS or PME configuration parameters (e.g., profile of a PCS or PME via efmCuAdminProfile or efmCuPmeAdminProfile) may lead to anything from link quality and rate degradation to a complete link initialization failure, as ability of an EFMCu port to support a particular configuration depends on the copper environment.
o 更改PCS或PME配置参数（例如，通过efmCuAdminProfile或efmCuPmeAdminProfile更改PCS或PME的配置文件）可能会导致从链路质量和速率降低到完全链路初始化失败的任何情况，因为EFMCu端口支持特定配置的能力取决于铜缆环境。
o Activation of a PME can cause a severe degradation of service for another EFMCu PHY, whose PME(s) may be affected by the cross-talk from the newly activated PME.
o PME的激活可导致另一EFMCu PHY的服务严重降级，其PME可能受到来自新激活PME的串扰的影响。
o Removal of a PME from an operationally 'up' EFMCu port, aggregating several PMEs, may cause port's rate degradation.
o 从操作上“向上”的EFMCu端口移除PME（聚合多个PME）可能会导致端口速率降低。
The user of the EFM-CU-MIB module must therefore be aware that support for SET operations in a non-secure environment without proper protection can have a negative effect on network operations.
因此，EFM-CU-MIB模块的用户必须意识到，在没有适当保护的非安全环境中支持SET操作可能会对网络操作产生负面影响。
The readable objects in the EFM-CU-MIB module (i.e., those with MAX-ACCESS other than not-accessible) may be considered sensitive in some environments since, collectively, they provide information about the performance of network interfaces and can reveal some aspects of their configuration. In particular, since EFMCu can be carried over Unshielded Twisted Pair (UTP) voice-grade copper in a bundle with other pairs belonging to another operator/customer, it is theoretically possible to eavesdrop to an EFMCu transmission simply by "listening" to a cross-talk from the EFMCu pairs, especially if the parameters of the EFMCu link in question are known.
EFM-CU-MIB模块中的可读对象（即具有MAX-ACCESS而非不可访问的对象）在某些环境中可能被视为敏感对象，因为它们共同提供有关网络接口性能的信息，并且可以揭示其配置的某些方面。特别是，由于EFMCu可以与属于另一运营商/客户的其他线对捆绑在一起，通过非屏蔽双绞线（UTP）语音级铜缆进行传输，因此理论上可以通过简单地“监听”来自EFMCu线对的串扰来窃听EFMCu传输，特别是当已知EFMCu链路的参数时。
In such environments, it is important to control also GET and NOTIFY access to these objects and possibly even to encrypt their values when sending them over the network via SNMP.
在这样的环境中，通过SNMP通过网络发送对象时，控制、获取和通知对这些对象的访问，甚至可能加密它们的值，这一点很重要。
SNMP versions prior to SNMPv3 did not include adequate security. Even if the network itself is secure (for example by using IPsec), even then, there is no control as to who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in these MIB modules.
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
此外，不建议部署SNMPv3之前的SNMP版本。相反，建议部署SNMPv3并启用加密安全性。然后，客户/运营商有责任确保允许访问网络的SNMP实体
instance of these MIB modules 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.
这些MIB模块的实例被正确配置为仅允许那些拥有合法权限来获取或设置（更改/创建/删除）对象的主体（用户）访问这些对象。
Object identifiers for the efmCuMIB MODULE-IDENTITY and ifCapStackMIB MODULE-IDENTITY have been allocated by IANA in the MIB-2 sub-tree.
IANA已在MIB-2子树中为efmCuMIB MODULE-IDENTITY和ifCapStackMIB MODULE-IDENTITY分配了对象标识符。
This document was produced by the [HUBMIB] working group, whose efforts were greatly advanced by the contributions of the following people (in alphabetical order):
本文件由[HUBMIB]工作组编制，以下人员（按字母顺序）的贡献极大地推动了工作组的工作：
Udi Ashkenazi (Actelis)
阿什肯纳齐人（阿克泰利斯）
Mike Heard
迈克听说
Alfred Hoenes (TR-Sys)
阿尔弗雷德·霍恩斯（TR系统）
Marina Popilov (Actelis)
玛丽娜·波皮洛夫（阿克泰利斯）
Mathias Riess (Infineon)
Mathias Riess（英飞凌）
Dan Romascanu (Avaya)
丹·罗马斯坎努（阿瓦亚）
Matt Squire (Hatteras)
马特·斯奎尔（哈特拉斯）
Bert Wijnen (Alcatel)
伯特·维恩（阿尔卡特）
[802.3] IEEE, "IEEE Standard for Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 3: Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications", IEEE Std 802.3-2005, December 2005.
[802.3]IEEE，“IEEE信息技术标准-系统间电信和信息交换-局域网和城域网-特定要求-第3部分：带冲突检测的载波侦听多址（CSMA/CD）接入方法和物理层规范”，IEEE标准802.3-2005，2005年12月。
[802.3ah] IEEE, "IEEE Standard for Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 3: Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications - Amendment: Media Access Control Parameters, Physical Layers and Management Parameters for Subscriber Access Networks", IEEE Std 802.3ah-2004, September 2004.
[802.3ah]IEEE，“IEEE信息技术标准-系统间电信和信息交换-局域网和城域网-特殊要求-第3部分：带冲突检测的载波侦听多址接入（CSMA/CD）接入方法和物理层规范.修改件：用户接入网络的媒体接入控制参数、物理层和管理参数”，IEEE标准802.3ah-2004，2004年9月。
[G.991.2] ITU-T, "Single-pair High-speed Digital Subscriber Line (SHDSL) transceivers", ITU-T Recommendation G.991.2, December 2003, <http://www.itu.int/rec/T-REC-G.991.2/en>.
[G.991.2]ITU-T，“单对高速数字用户线（SHDSL）收发器”，ITU-T建议G.991.2，2003年12月<http://www.itu.int/rec/T-REC-G.991.2/en>.
[G.993.1] ITU-T, "Very High speed Digital Subscriber Line transceivers", ITU-T Recommendation G.993.1, June 2004, <http://www.itu.int/rec/T-REC-G.993.1/en>.
[G.993.1]ITU-T，“超高速数字用户线收发器”，ITU-T建议G.993.1，2004年6月<http://www.itu.int/rec/T-REC-G.993.1/en>.
[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., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2578]McCloghrie，K.，Ed.，Perkins，D.，Ed.，和J.Schoenwaeld，Ed.“管理信息的结构版本2（SMIv2）”，STD 58，RFC 2578，1999年4月。
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2579]McCloghrie，K.，Ed.，Perkins，D.，Ed.，和J.Schoenwaeld，Ed.“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月。
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", RFC 2863, June 2000.
[RFC2863]McCloghrie，K.和F.Kastenholz，“接口组MIB”，RFC 28632000年6月。
[RFC2864] McCloghrie, K. and G. Hanson, "The Inverted Stack Table Extension to the Interfaces Group MIB", RFC 2864, June 2000.
[RFC2864]McCloghrie，K.和G.Hanson，“接口组MIB的反向堆栈表扩展”，RFC 2864，2000年6月。
[RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, December 2002.
[RFC3411]Harrington，D.，Presohn，R.，和B.Wijnen，“描述简单网络管理协议（SNMP）管理框架的体系结构”，STD 62，RFC 3411，2002年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月。
[RFC4836] Beili, E., "Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs)", RFC 4836, April 2007.
[RFC4836]Beili，E.“IEEE 802.3介质连接单元（MAU）受管对象的定义”，RFC 4836，2007年4月。
[T1.424] ANSI, "Interface Between Networks and Customer Installation Very-high-bit-rate Digital Subscriber Lines (VDSL) Metallic Interface (DMT Based)", American National Standard T1.424-2004, June 2004.
[T1.424]ANSI，“网络和客户安装之间的接口甚高速数字用户线（VDSL）金属接口（基于DMT）”，美国国家标准T1.424-2004，2004年6月。
[TS 101 270-1] ETSI, "Transmission and Multiplexing (TM); Access
transmission systems on metallic access cables;
Very high speed Digital Subscriber Line (VDSL);
Part 1: Functional requirements", Technical
Specification TS 101 270-1, October 2005.
[TS 101 270-1] ETSI, "Transmission and Multiplexing (TM); Access
transmission systems on metallic access cables;
Very high speed Digital Subscriber Line (VDSL);
Part 1: Functional requirements", Technical
Specification TS 101 270-1, October 2005.
[ANFP] Network Interoperability Consultative Committee (NICC), "Specification of the Access Network Frequency Plan (ANFP) applicable to transmission systems used on the BT Access Network", NICC Document ND1602:2005/08, August 2005.
[ANFP]网络互操作性咨询委员会（NICC），“适用于BT接入网络上使用的传输系统的接入网络频率计划（ANFP）规范”，NICC文件ND1602:2005/08，2005年8月。
[HUBMIB] IETF, "Ethernet Interfaces and Hub MIB (hubmib) Charter", <http://www.ietf.org/html.charters/OLD/ hubmib-charter.html>.
[HUBMIB]IETF，“以太网接口和集线器MIB（HUBMIB）章程”<http://www.ietf.org/html.charters/OLD/ hubmib charter.html>。
[IANAifType-MIB] Internet Assigned Numbers Authority (IANA), "IANAifType Textual Convention definition", <http://www.iana.org/assignments/ianaiftype-mib>.
[IANAifType MIB]互联网分配号码管理局（IANA），“IANAifType文本约定定义”<http://www.iana.org/assignments/ianaiftype-mib>.
[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月。
[RFC4070] Dodge, M. and B. Ray, "Definitions of Managed Object Extensions for Very High Speed Digital Subscriber Lines (VDSL) Using Multiple Carrier Modulation (MCM) Line Coding", RFC 4070, May 2005.
[RFC4070]Dodge，M.和B.Ray，“使用多载波调制（MCM）线路编码的超高速数字用户线路（VDSL）管理对象扩展的定义”，RFC 4070，2005年5月。
[RFC4181] Heard, C., "Guidelines for Authors and Reviewers of MIB Documents", BCP 111, RFC 4181, September 2005.
[RFC4181]Heard，C.，“MIB文件的作者和评审者指南”，BCP 111，RFC 41812005年9月。
[RFC4319] Sikes, C., Ray, B., and R. Abbi, "Definitions of Managed Objects for High Bit-Rate DSL - 2nd generation (HDSL2) and Single-Pair High-Speed Digital Subscriber Line (SHDSL) Lines", RFC 4319, December 2005.
[RFC4319]Sikes，C.，Ray，B.，和R.Abbi，“高速数字用户线的管理对象定义-第二代（HDSL2）和单对高速数字用户线（SHDSL）线路”，RFC 4319，2005年12月。
[RFC4837] Khermosh, L., "Managed Objects of Ethernet Passive Optical Networks (EPON)", RFC 4837, July 2007.
[RFC4837]Khermosh，L.“以太网无源光网络（EPON）的管理对象”，RFC 4837，2007年7月。
[RFC4878] Squire, M., "Definitions and Managed Objects for Operations, Administration, and Maintenance (OAM) Functions on Ethernet-Like Interfaces", RFC 4878, June 2007.
[RFC4878]Squire，M.“类以太网接口上操作、管理和维护（OAM）功能的定义和托管对象”，RFC 4878，2007年6月。
Author's Address
作者地址
Edward Beili Actelis Networks Bazel 25 Petach-Tikva Israel
Edward Beili Actelis Networks Bazel 25 Petach Tikva以色列
Phone: +972-3-924-3491
EMail: edward.beili@actelis.com
Phone: +972-3-924-3491
EMail: edward.beili@actelis.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.