Internet Engineering Task Force (IETF) E. Beili
Request for Comments: 6765 Actelis Networks
Category: Standards Track M. Morgenstern
ISSN: 2070-1721 ECI Telecom
February 2013
Internet Engineering Task Force (IETF) E. Beili
Request for Comments: 6765 Actelis Networks
Category: Standards Track M. Morgenstern
ISSN: 2070-1721 ECI Telecom
February 2013
xDSL Multi-Pair Bonding (G.Bond) MIB
xDSL多对键合（G键合）MIB
Abstract
摘要
This document defines a Management Information Base (MIB) module for use with network management protocols in TCP/IP-based internets. This document defines an extension to the Interfaces Group MIB with a set of common objects for managing multi-pair bonded Digital Subscriber Line (xDSL) interfaces, as defined in ITU-T Recommendations G.998.1, G.998.2, and G.998.3. The textual conventions defining the bonding schemes are contained in a separate MIB module maintained by Internet Assigned Numbers Authority (IANA). The MIB modules specific to each bonding technology are defined in G9981-MIB, G9982-MIB, and G9983-MIB, respectively.
本文档定义了一个管理信息库（MIB）模块，用于基于TCP/IP的Internet中的网络管理协议。本文档定义了接口组MIB的扩展，其中包含一组用于管理多对绑定数字用户线（xDSL）接口的通用对象，如ITU-T建议G.998.1、G.998.2和G.998.3中所定义。定义绑定方案的文本约定包含在由互联网分配号码管理局（IANA）维护的单独MIB模块中。G9981-MIB、G9982-MIB和G9983-MIB中分别定义了特定于每种键合技术的MIB模块。
Status of This Memo
关于下段备忘
This is an Internet Standards Track document.
这是一份互联网标准跟踪文件。
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。有关互联网标准的更多信息，请参见RFC 5741第2节。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6765.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc6765.
Copyright Notice
版权公告
Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2013 IETF信托基金和确定为文件作者的人员。版权所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
Table of Contents
目录
1. Introduction ....................................................3
2. The Internet-Standard Management Framework ......................4
3. The Broadband Forum Management Framework for xDSL Bonding .......4
4. Relationship to Other MIB Modules ...............................5
4.1. Relationship to Interfaces Group MIB Module ................5
4.1.1. Layering Model ......................................5
4.1.2. xDSL Bonding ........................................7
4.1.3. Discovery Operation .................................8
4.1.4. Initialization of G.Bond Ports .....................10
4.1.5. Usage of the ifTable ...............................11
4.2. Relationship to G.Bond ATM, ETH, and TDIM MIB Modules .....13
4.3. Relationship to xDSL MIB Modules ..........................13
4.4. Addition of New Bonding Schemes ...........................13
5. MIB Structure ..................................................13
5.1. Overview ..................................................13
5.2. Performance Monitoring ....................................14
5.3. Mapping of Broadband Forum TR-159 Managed Objects .........14
6. xDSL Multi-Pair Bonding MIB Definitions ........................19
7. IANA-Maintained G.Bond TC Definitions ..........................65
8. Security Considerations ........................................67
9. IANA Considerations ............................................69
10. Acknowledgments ...............................................69
11. References ....................................................70
11.1. Normative References .....................................70
11.2. Informative References ...................................71
1. Introduction ....................................................3
2. The Internet-Standard Management Framework ......................4
3. The Broadband Forum Management Framework for xDSL Bonding .......4
4. Relationship to Other MIB Modules ...............................5
4.1. Relationship to Interfaces Group MIB Module ................5
4.1.1. Layering Model ......................................5
4.1.2. xDSL Bonding ........................................7
4.1.3. Discovery Operation .................................8
4.1.4. Initialization of G.Bond Ports .....................10
4.1.5. Usage of the ifTable ...............................11
4.2. Relationship to G.Bond ATM, ETH, and TDIM MIB Modules .....13
4.3. Relationship to xDSL MIB Modules ..........................13
4.4. Addition of New Bonding Schemes ...........................13
5. MIB Structure ..................................................13
5.1. Overview ..................................................13
5.2. Performance Monitoring ....................................14
5.3. Mapping of Broadband Forum TR-159 Managed Objects .........14
6. xDSL Multi-Pair Bonding MIB Definitions ........................19
7. IANA-Maintained G.Bond TC Definitions ..........................65
8. Security Considerations ........................................67
9. IANA Considerations ............................................69
10. Acknowledgments ...............................................69
11. References ....................................................70
11.1. Normative References .....................................70
11.2. Informative References ...................................71
xDSL Multi-pair bonding allows a service provider to provide high-bandwidth services to business and residential customers over multiple xDSL lines, with greater speed and resiliency than service over a single xDSL line, bridging the gap between xDSL and fiber-based transport.
xDSL多线对连接允许服务提供商通过多条xDSL线路向商业和住宅客户提供高带宽服务，其速度和弹性比单条xDSL线路上的服务更高，从而弥合了xDSL和光纤传输之间的差距。
Currently, there are three xDSL Multi-pair bonding schemes, also known under the collective name "G.Bond":
目前，有三种xDSL多对键合方案，也称为“G.Bond”：
o ATM-Based Multi-pair bonding, as specified in ITU-T Recommendation G.998.1 [G.998.1], which defines a method for the bonding (or aggregating) of multiple xDSL lines (or individual bearer channels in multiple xDSL lines) into a single bidirectional logical link carrying an ATM stream. This specification can be viewed as an evolution of the legacy Inverse Multiplexing for ATM (IMA) technology [AF-PHY-0086], applied to xDSL with variable rates on each line/bearer channel.
o ITU-T建议G.998.1[G.998.1]中规定的基于ATM的多对连接，该建议定义了将多条xDSL线路（或多条xDSL线路中的单个承载信道）连接（或聚合）到承载ATM流的单个双向逻辑链路的方法。本规范可视为ATM（IMA）传统反向多路复用技术[AF-PHY-0086]的发展，适用于在每条线路/承载信道上具有可变速率的xDSL。
o Ethernet-Based Multi-pair bonding, as specified in ITU-T Recommendation G.998.2 [G.998.2], which defines a method for the bonding (or aggregating) of multiple xDSL lines (or individual bearer channels in multiple xDSL lines) into a single bidirectional logical link carrying an Ethernet stream. This specification can be viewed as IEEE 802.3-2005 [802.3] Clause 61, Physical Medium Entity (PME) Aggregation, generalized to work over any xDSL technology (2Base-TL and 10Pass-TS interfaces defined by IEEE use G.SHDSL (Single-pair High-speed DSL) and VDSL (Very high speed DSL) technology, respectively).
o ITU-T建议G.998.2[G.998.2]中规定的基于以太网的多对连接，该建议定义了将多条xDSL线路（或多条xDSL线路中的单个承载信道）连接（或聚合）到承载以太网流的单个双向逻辑链路的方法。本规范可视为IEEE 802.3-2005[802.3]第61条，物理介质实体（PME）聚合，通用于任何xDSL技术（IEEE定义的2个基本TL和10个通过TS接口分别使用G.SHDSL（单对高速DSL）和VDSL（甚高速DSL）技术）。
o Multi-pair bonding using Time-Division Inverse Multiplexing (TDIM), specified in ITU-T Recommendation G.998.3 [G.998.3], which defines a method for the bonding (or aggregating) of multiple xDSL lines into a single bidirectional logical link carrying a mix of various traffic streams (e.g., Ethernet, ATM, TDM).
o ITU-T建议G.998.3[G.998.3]中规定的使用时分反向多路复用（TDIM）的多对连接，该建议定义了一种将多条xDSL线路连接（或聚合）到单个双向逻辑链路的方法，该链路承载各种业务流的混合（例如，以太网、ATM、TDM）。
Architecturally, all three bonding schemes define a new "bonded" Transport Protocol Specific - Transmission Convergence (TPS-TC) sub-layer, stacked above multiple ATM-TC, Ethernet/Packet Transfer Mode-TC (PTM-TC), or Synchronous Transfer Mode-TC (STM-TC) (clear channel) sub-layers for the ATM, Ethernet, or TDIM bonding, respectively. Each underlying TPS-TC sub-layer represents a protocol-specific interface to an xDSL line or an individual bearer channel of an xDSL line. Bonding of multiple bearer channels in the same xDSL line is not allowed.
在体系结构上，所有三种绑定方案都定义了一个新的“绑定”传输协议特定的传输汇聚（TPS-TC）子层，分别堆叠在多个ATM-TC、以太网/分组传输模式TC（PTM-TC）或同步传输模式TC（STM-TC）（透明通道）子层之上，用于ATM、以太网或TDIM绑定。每个底层TPS-TC子层表示到xDSL线路或xDSL线路的单个承载信道的特定于协议的接口。不允许在同一xDSL线路中连接多个承载信道。
All schemes allow bonding of up to 32 individual line/channel sub-layers with variable rates, providing common functionality for the configuration, initialization, operation, and monitoring of the bonded link.
所有方案都允许以可变速率连接多达32个单独的线路/通道子层，为连接链路的配置、初始化、操作和监控提供通用功能。
This document defines a MIB module common to all 3 schemes. Additional managed objects specific to each bonding technology are defined in the G9981-MIB [RFC6768], G9982-MIB [RFC6767], and G9983-MIB [RFC6766] modules.
本文档定义了所有3个方案共用的MIB模块。G9981-MIB[RFC6768]、G9982-MIB[RFC6767]和G9983-MIB[RFC6766]模块中定义了特定于每种绑定技术的其他托管对象。
The textual conventions listing the bonding schemes are defined in a separate, IANA-maintained MIB module, the first version of which is provided in this document. This arrangement would allow for future bonding schemes to be easily supported, without the need to update the common GBOND-MIB module.
列出绑定方案的文本约定在独立的IANA维护的MIB模块中定义，本文档中提供了该模块的第一个版本。这种安排将使未来的键合方案易于支持，而无需更新通用GBOND-MIB模块。
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 document specifies a MIB module that is compliant to the SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580].
托管对象通过虚拟信息存储（称为管理信息库或MIB）进行访问。MIB对象通常通过简单网络管理协议（SNMP）进行访问。MIB中的对象是使用管理信息结构（SMI）中定义的机制定义的。本文件规定了符合SMIv2的MIB模块，如STD 58、RFC 2578[RFC2578]、STD 58、RFC 2579[RFC2579]和STD 58、RFC 2580[RFC2580]所述。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14, RFC 2119 [RFC2119].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“建议”、“不建议”、“可”和“可选”应按照BCP 14、RFC 2119[RFC2119]中的说明进行解释。
This document makes use of the Broadband Forum technical report "Management Framework for xDSL Bonding" [TR-159], defining a management model and a hierarchy of management objects for the bonded xDSL interfaces.
本文件利用宽带论坛技术报告“xDSL绑定管理框架”[TR-159]，定义了绑定xDSL接口的管理模型和管理对象层次结构。
This section outlines the relationship of the MIB modules defined in this document with other MIB modules described in the relevant RFCs. Specifically, the following MIB modules are discussed: the Interfaces Group MIB (IF-MIB), Inverse Stack Table MIB (IF-INVERTED-STACK-MIB), and Interface Stack Capability MIB (IF-CAP-STACK-MIB); G.Bond scheme-specific modules G.Bond/ATM (G9981-MIB), G.Bond/Ethernet (G9982-MIB), and G.Bond/TDIM (G9983-MIB); and DSL-specific MIB modules ADSL (ADSL-LINE-EXT-MIB), ADSL2 (ADSL2-LINE-MIB), SHDSL (HDSL2-SHDSL-LINE-MIB), VDSL (VDSL-LINE-MIB), and VDSL2 (VDSL2-LINE-MIB).
本节概述了本文档中定义的MIB模块与相关RFC中描述的其他MIB模块之间的关系。具体来说，讨论了以下MIB模块：接口组MIB（IF-MIB）、反向堆栈表MIB（IF-INVERTED-Stack-MIB）和接口堆栈能力MIB（IF-CAP-Stack-MIB）；G.键合方案专用模块G.Bond/ATM（G9981-MIB）、G.Bond/Ethernet（G9982-MIB）和G.Bond/TDIM（G9983-MIB）；以及DSL专用MIB模块ADSL（ADSL-LINE-EXT-MIB）、ADSL2（ADSL2-LINE-MIB）、SHDSL（HDSL2-SHDSL-LINE-MIB）、VDSL（VDSL-LINE-MIB）和VDSL2（VDSL2-LINE-MIB）。
A bonded xDSL port is a stacked (a.k.a. aggregated or bonded) interface and as such is managed using generic interface management objects defined in the IF-MIB [RFC2863].
绑定的xDSL端口是堆叠（也称聚合或绑定）接口，因此使用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 -- the ifInvStackTable, as defined in the IF-INVERTED-STACK-MIB [RFC2864].
堆栈管理，即子层与顶层接口的实际连接，通过IF-MIB[RFC2863]中定义的ifStackTable及其逆项——IF-Inversed-stack-MIB[RFC2864]中定义的ifInvStackTable完成。
The ifCapStackTable and its inverse -- the ifInvCapStackTable, as defined in the IF-CAP-STACK-MIB [RFC5066] -- 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.
当接口层之间存在灵活的交叉连接矩阵时，ifCapStackTable及其逆项ifInvCapStackTable（如IF-CAP-STACK-MIB[RFC5066]中所定义）扩展堆栈管理，使其能够描述可能的连接或交叉连接能力。
A G.Bond interface can aggregate up to 32 channel sub-layers, with each channel representing an xDSL line or an xDSL bearer channel. For the purpose of brevity we will refer to the bonded interface as the Generic Bonding Sub-layer (GBS) and to the channel sub-layer as the Bonding Channel Entity (BCE).
G.Bond接口最多可聚合32个通道子层，每个通道代表一条xDSL线路或一个xDSL承载通道。为简洁起见，我们将粘结界面称为通用粘结子层（GBS），将沟道子层称为粘结沟道实体（BCE）。
A generic G.Bond device can have a number of GBS ports, each connected to a particular upper layer (e.g., a Media Access Control (MAC) interface for the G.998.2 scheme), while simultaneously cross-connected to a number of underlying BCEs, with a single-GBS-per-BCE relationship.
通用G.Bond设备可具有多个GBS端口，每个端口连接到特定的上层（例如，G.998.2方案的媒体访问控制（MAC）接口），同时交叉连接到多个基础BCE，每个BCE具有单个GBS关系。
A GBS port is represented in the Interfaces table (ifTable) as a separate interface with an ifType reflecting a particular bonding scheme, e.g., g9981(263), g9982(264), or g9983(265).
GBS端口在接口表（ifTable）中表示为单独的接口，ifType反映了特定的连接方案，例如g9981（263）、g9982（264）或g9983（265）。
Each BCE in the aggregated GBS port is represented in the ifTable as a separate interface with an ifType relevant to a particular xDSL technology, e.g., shdsl(169) or vdsl(97). The ifType values are defined in [IANAifType-MIB].
聚合GBS端口中的每个BCE在ifTable中表示为一个单独的接口，该接口具有与特定xDSL技术相关的ifType，例如shdsl（169）或vdsl（97）。ifType值在[IANAifType MIB]中定义。
The following figure shows the layering diagram and corresponding use of the ifTable for the bonded xDSL interfaces:
下图显示了绑定xDSL接口的分层图和ifTable的相应用法：
.-----------------------------. -
| GBS | ^ 1 ifEntry
| (TPS-TC) | v ifType: g9981(263), g9982(264),
+-----------------+---+-------+ - g9983(265), etc.
| TPS-TC \ | | | ^
+---------\ | | | | N ifEntry (N=1..32)
| PMS-TC )BCE 1 |...| BCE N | ) ifType: adsl(94), shdsl(169),
+---------/ | | | | vdsl(97), vdsl2(251),
| PMD / | | | v etc.
'-----------------+---+-------' -
.-----------------------------. -
| GBS | ^ 1 ifEntry
| (TPS-TC) | v ifType: g9981(263), g9982(264),
+-----------------+---+-------+ - g9983(265), etc.
| TPS-TC \ | | | ^
+---------\ | | | | N ifEntry (N=1..32)
| PMS-TC )BCE 1 |...| BCE N | ) ifType: adsl(94), shdsl(169),
+---------/ | | | | vdsl(97), vdsl2(251),
| PMD / | | | v etc.
'-----------------+---+-------' -
BCE - Bonding Channel Entity
GBS - Generic Bonding Sub-layer
PMD - Physical Medium Dependent
TPS-TC - Transport Protocol Specific - Transmission Convergence
PMS-TC - Physical Media Specific - Transmission Convergence
BCE - Bonding Channel Entity
GBS - Generic Bonding Sub-layer
PMD - Physical Medium Dependent
TPS-TC - Transport Protocol Specific - Transmission Convergence
PMS-TC - Physical Media Specific - Transmission Convergence
Figure 1: Use of ifTable for Bonded xDSL Interfaces
图1：对绑定的xDSL接口使用ifTable
The ifStackTable is indexed by the ifIndex values of the aggregated G.Bond port (GBS) and the BCEs connected to it. The ifStackTable allows a network management application to determine which BCEs are connected to a particular GBS 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 GBS runs on top of a particular BCE.
ifStackTable由聚合的G.Bond端口（GBS）和连接到它的BCE的ifIndex值索引。ifStackTable允许网络管理应用程序确定哪些BCE连接到特定GBS并更改连接（如果应用程序支持）。ifInvStackTable是ifStackTable的反向版本，它为网络管理应用程序提供了一种有效的方法来读取ifStackTable的子集，从而确定哪个GBS运行在特定BCE之上。
The ifCapStackTable, defined in the IF-CAP-STACK-MIB module, specifies for each higher-layer interface (e.g., GBS port) a list of lower-layer interfaces (e.g., BCEs), which can possibly be cross-connected to that higher-layer interface, determined by the cross-connect capability of the device. This table, modeled after the ifStackTable, is read only, reflecting current cross-connect capability of a stacked interface, which can be dynamic in some implementations (e.g., if xDSL lines are located on a pluggable module and the module is pulled out). Note that BCE availability per GBS, described by the ifCapStackTable, can be constrained by other parameters -- for example, by the aggregation capacity of a GBS or by the BCE in question being already connected to another GBS. So, in
在IF-CAP-STACK-MIB模块中定义的ifCapStackTable为每个高层接口（例如，GBS端口）指定一个下层接口（例如，BCE）列表，这些接口可能会交叉连接到该高层接口，由设备的交叉连接能力确定。该表以ifStackTable为模型，是只读的，反映了堆叠接口的当前交叉连接能力，在某些实现中可能是动态的（例如，如果xDSL线路位于可插拔模块上，并且模块被拔出）。请注意，ifCapStackTable中描述的每GB的BCE可用性可能受到其他参数的约束——例如，受一个GBS的聚合容量或已连接到另一个GBS的相关BCE的约束。那么在
order to ensure that a particular BCE can be connected to the GBS, all respective parameters (e.g., ifCapStackTable, ifStackTable, and gBondPortCapCapacity) SHALL be inspected.
为确保特定BCE可连接至GBS，应检查所有相关参数（如ifCapStackTable、ifStackTable和GBondPortCapCapCapCapCapCapCapacity）。
The ifInvCapStackTable, also defined in the IF-CAP-STACK-MIB module, describes which higher-layer interfaces (e.g., GBS ports) can possibly be connected to a particular lower-layer interface (e.g., BCE), providing 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 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.
同样在IF-CAP-STACK-MIB模块中定义的ifInvCapStackTable描述了哪些高层接口（如GBS端口）可以连接到特定的底层接口（如BCE），从而提供ifCapStackTable的反向映射。虽然它不包含ifCapStackTable中已经包含的信息以外的其他信息，但ifInvCapStackTable在其索引子句中的ifIndex值顺序相反，即先是较低层接口，然后是较高层接口，为网络管理应用程序提供读取ifCapStackTable子集的有效方法，从而确定可以连接哪些接口以在特定接口上运行。
The G.998.x Bonding allows a number of BCEs to be aggregated onto a single logical GBS port by splitting the incoming traffic into multiple streams, transmitting each stream over a specific BCE, and combining the streams at the remote GBS port, preserving the original traffic order.
G.998.x绑定允许将多个BCE聚合到单个逻辑GBS端口上，方法是将传入流量拆分为多个流，通过特定BCE传输每个流，并在远程GBS端口组合流，保留原始流量顺序。
The Ethernet frames MAY be fragmented before the transmission and reassembled at the remote end to minimize transportation delay. The G.998.2 (G.Bond/Ethernet) ports with multiple BCEs MUST perform the fragmentation and reassembly of the Ethernet frames. However, for single-BCE G.998.2 ports this function MAY be omitted (a.k.a. bonding bypass), to minimize fragmentation overhead and additional processing delay as well as to be able to interoperate with non-G.998 DSL equipment.
以太网帧可以在传输之前进行分段，并在远程端重新组装，以最小化传输延迟。带有多个BCE的G.998.2（G.Bond/Ethernet）端口必须执行以太网帧的分段和重新组装。但是，对于单个BCE G.998.2端口，可以省略此功能（也称为绑定旁路），以最小化碎片开销和额外的处理延迟，并能够与非G.998 DSL设备进行互操作。
The agent is REQUIRED to indicate all supported bonding schemes (for example, ATM, Ethernet, and TDIM), including OPTIONAL support for the bonding bypass in G.998.2 single-BCE ports.
要求代理指明所有受支持的连接方案（例如，ATM、以太网和TDIM），包括G.998.2单BCE端口中对连接旁路的可选支持。
The GBOND-MIB module allows a network management application to query Bonding capability and enable/disable it if supported. Note that enabling Bonding (by setting the value of the gBondPortConfAdminScheme and gBondPortConfPeerAdminScheme objects to any supported bonding scheme other than 'none') effectively turns on the fragmentation and reassembly function, even on a single-BCE port.
GBOND-MIB模块允许网络管理应用程序查询绑定能力，并在支持的情况下启用/禁用它。请注意，启用绑定（通过将gBondPortConfAdminScheme和gBondPortConfPeerAdminScheme对象的值设置为除“无”之外的任何受支持的绑定方案）可以有效地启用碎片和重新组装功能，即使在单个BCE端口上也是如此。
The G.Bond ports may optionally support a discovery operation whereby BCEs, during initialization, exchange information about their respective aggregation groups (GBS), via the [G.994.1] handshake (G.hs) protocol. This information can then be used to detect copper misconnections or for an automatic assignment of the local BCEs into aggregation groups instead of a fixed preconfiguration.
G.Bond端口可以可选地支持发现操作，其中bce在初始化期间通过[G.994.1]握手（G.hs）协议交换关于其各自聚合组（GBS）的信息。然后，该信息可用于检测铜缆错误连接，或用于将本地BCE自动分配到聚合组中，而不是固定的预配置。
The MIB module defined in this document allows a network management application to control the G.Bond discovery mechanism and query its results.
本文档中定义的MIB模块允许网络管理应用程序控制G.Bond发现机制并查询其结果。
Two tables are used by the G.Bond discovery mechanism: the ifStackTable and the ifCapStackTable. The following pseudocode gives an example of the discovery and automatic BCE assignment for a generic multi-GBS G.Bond device, located at the Central Office (CO), using objects defined in this MIB module as well as the IF-CAP-STACK-MIB and IF-MIB modules [Note that automatic BCE assignment is only shown here for the purposes of the example. Fixed BCE pre-assignment, manual assignment, or auto-assignment using an alternative internal algorithm may be chosen by a particular implementation]:
G.Bond发现机制使用两个表：ifStackTable和ifCapStackTable。以下伪代码给出了位于中央局（CO）的通用多GBS G.Bond设备的发现和自动BCE分配示例，该设备使用此MIB模块以及IF-CAP-STACK-MIB和IF-MIB模块中定义的对象[请注意，此处仅出于示例目的显示自动BCE分配。特定实现可选择固定BCE预分配、手动分配或使用替代内部算法的自动分配]：
// Go over all GBS ports in the CO device
FOREACH gbs[i] IN CO_device
{ // Perform discovery and auto-assignment on GBS ports
// with room for more channels.
IF ( gbs[i].NumBCEs < gbs[i].BondCapacity )
{ // Assign a unique 6-octet local discovery code to the GBS,
// e.g., MAC address of the associated port or some other
// unique number specifically allocated for this purpose.
dc = gbs[i].DiscoveryCode = MAC[i];
// Go over all disconnected channels, which can
// potentially be connected to the GBS.
FOREACH bce[j] IN ifCapStackTable[gbs[i]] AND
NOT IN ifStackTable[gbs[i]] // not connected
{ // Try to grab the Remote Terminal device (RT) by writing the
// value of the local 6-byte discovery code to the remote
// discovery code register (via a handshake mechanism).
// This operation is an 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 a Get
// operation to see if the RT, attached via the BCE,
// is indeed marked as being the CO_device peer.
bce[j].RemoteDiscoveryCode = dc; // Set-if-Clear
r = bce[j].RemoteDiscoveryCode; // Get
// Go over all GBS ports in the CO device
FOREACH gbs[i] IN CO_device
{ // Perform discovery and auto-assignment on GBS ports
// with room for more channels.
IF ( gbs[i].NumBCEs < gbs[i].BondCapacity )
{ // Assign a unique 6-octet local discovery code to the GBS,
// e.g., MAC address of the associated port or some other
// unique number specifically allocated for this purpose.
dc = gbs[i].DiscoveryCode = MAC[i];
// Go over all disconnected channels, which can
// potentially be connected to the GBS.
FOREACH bce[j] IN ifCapStackTable[gbs[i]] AND
NOT IN ifStackTable[gbs[i]] // not connected
{ // Try to grab the Remote Terminal device (RT) by writing the
// value of the local 6-byte discovery code to the remote
// discovery code register (via a handshake mechanism).
// This operation is an 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 a Get
// operation to see if the RT, attached via the BCE,
// is indeed marked as being the CO_device peer.
bce[j].RemoteDiscoveryCode = dc; // Set-if-Clear
r = bce[j].RemoteDiscoveryCode; // Get
IF ( r == dc AND gbs[i].NumBCEs < gbs[i].BondCapacity )
{ // RT connected via BCE[j] is/was a peer
// for GBS[i], and there is room for another BCE in the
// GBS[i] aggregation group (max. Bonding capacity is
// not reached yet).
// Connect this BCE to the GBS (via the ifStackTable; the
// ifInvStackTable, which is the inverse of the ifStackTable,
// is updated automatically; i.e., gbs[i] is auto-added
// to ifInvStackTable[bce[j]]).
ADD bce[j] TO ifStackTable[gbs[i]];
gbs[i].NumBCEs = gbs[i].NumBCEs + 1;
// Discover all other disconnected BCEs
// attached to the same RT and connect them to
// the GBS, provided there is enough room for more BCEs.
FOREACH bce[k] IN ifCapStackTable[gbs[i]] and
NOT IN ifStackTable[gbs[i]]
{ // Get the remote discovery code from the BCE to see if
// it belongs to a connected RT "grabbed" by
// the CO_device.
r = bce[k].RemoteDiscoveryCode;
IF ( r == dc AND gbs[i].NumBCEs < gbs[i].BondCapacity )
{ // Physically connect the BCE to the GBS.
// (gbs[i] is auto-added TO ifInvStackTable[bce[k]]).
ADD bce[k] TO ifStackTable[gbs[i]];
gbs[i].NumBCEs = gbs[i].NumBCEs + 1;
}
}
}
// At this point we have discovered all local BCEs that
// are physically connected to the same RT and
// connected them to GBS[i]. Go to the next GBS.
BREAK;
}
}
}
IF ( r == dc AND gbs[i].NumBCEs < gbs[i].BondCapacity )
{ // RT connected via BCE[j] is/was a peer
// for GBS[i], and there is room for another BCE in the
// GBS[i] aggregation group (max. Bonding capacity is
// not reached yet).
// Connect this BCE to the GBS (via the ifStackTable; the
// ifInvStackTable, which is the inverse of the ifStackTable,
// is updated automatically; i.e., gbs[i] is auto-added
// to ifInvStackTable[bce[j]]).
ADD bce[j] TO ifStackTable[gbs[i]];
gbs[i].NumBCEs = gbs[i].NumBCEs + 1;
// Discover all other disconnected BCEs
// attached to the same RT and connect them to
// the GBS, provided there is enough room for more BCEs.
FOREACH bce[k] IN ifCapStackTable[gbs[i]] and
NOT IN ifStackTable[gbs[i]]
{ // Get the remote discovery code from the BCE to see if
// it belongs to a connected RT "grabbed" by
// the CO_device.
r = bce[k].RemoteDiscoveryCode;
IF ( r == dc AND gbs[i].NumBCEs < gbs[i].BondCapacity )
{ // Physically connect the BCE to the GBS.
// (gbs[i] is auto-added TO ifInvStackTable[bce[k]]).
ADD bce[k] TO ifStackTable[gbs[i]];
gbs[i].NumBCEs = gbs[i].NumBCEs + 1;
}
}
}
// At this point we have discovered all local BCEs that
// are physically connected to the same RT and
// connected them to GBS[i]. Go to the next GBS.
BREAK;
}
}
}
An SNMP agent for a G.Bond device builds the ifCapStackTable and its inverse -- the ifInvCapStackTable -- on device initialization, according to the cross-connect capabilities of the device.
G.Bond设备的SNMP代理根据设备的交叉连接功能，在设备初始化时构建ifCapStackTable及其逆项ifInvCapStackTable。
Adding a BCE to the ifStackTable row for a specific GBS involves actual connection of the BCE to the GBS.
将BCE添加到特定GBS的ifStackTable行涉及BCE与GBS的实际连接。
Note that a GBS port does not have to be operationally 'down' for the connection to succeed. In fact, a dynamic BCE addition (and removal) MAY be implemented with an available BCE being initialized first (by setting its ifAdminStatus to 'up') and then added to an operationally 'up' GBS port, by modifying a respective ifStackTable (and respective ifInvStackTable) entry.
请注意，GBS端口不必在操作上“关闭”，连接才能成功。事实上，动态BCE添加（和删除）可以通过以下方式实现：首先初始化可用BCE（通过将其ifAdminStatus设置为“up”），然后通过修改相应的ifStackTable（和相应的ifInvStackTable）条目将其添加到操作上的“up”GBS端口。
It is RECOMMENDED that removal of the last operationally 'up' BCE from an operationally 'up' GBS, i.e., modification of a respective entry in the ifStackTable, and a corresponding entry in the ifInvStackTable, would be rejected by the implementation (in the case of SNMP, with the error inconsistentValue), as this action would completely drop the link.
建议实施拒绝从操作“向上”GBS中删除最后一个操作“向上”BCE，即修改ifStackTable中的相应条目和ifInvStackTable中的相应条目（对于SNMP，错误值不一致），因为此操作将完全删除链接。
In addition to the standard handshake-based discovery described above, [G.998.2] defines an optional frame-based discovery and pair management. These frame-based methods are discussed in [RFC6767].
除了上述标准的基于握手的发现外，[G.998.2]还定义了可选的基于帧的发现和对管理。[RFC6767]中讨论了这些基于帧的方法。
G.Bond ports 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 a required data rate on a particular 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.
G.建立在xDSL技术之上的Bond端口需要一个漫长的初始化或“培训”过程，才能传递任何数据。在此初始化过程中，链路的两端（对等方）协同工作，以在特定铜对上实现所需的数据速率。有时，当铜线过长或线路上的噪声过高时，“培训”过程可能无法达到具有所需特性的特定目标速率。
The ifAdminStatus object from the IF-MIB controls the desired state of a GBS with all the BCEs connected to it or of an individual BCE port. Setting this object to 'up' instructs a particular GBS or a BCE to start the initialization process, which may take tens of seconds for G.Bond ports. The ifOperStatus object from the IF-MIB shows the operational state of an interface for the GBS, extended by the gBondPortStatFltStatus object defined in this document, and a corresponding *Status object from a relevant xDSL line MIB for BCE interfaces.
IF-MIB中的ifAdminStatus对象控制连接有所有BCE的GBS或单个BCE端口的所需状态。将此对象设置为“up”将指示特定的GBS或BCE启动初始化过程，这可能需要数十秒的时间才能完成G.Bond端口。IF-MIB中的ifOperStatus对象显示GBS接口的操作状态，该接口由本文档中定义的gBondPortStatFltStatus对象扩展，并显示BCE接口的相关xDSL行MIB中相应的*状态对象。
A disconnected BCE may be initialized by changing the ifAdminStatus from 'down' to 'up'. Changing the ifAdminStatus to 'up' on the GBS initializes all BCEs connected to that particular GBS. Note that in the case of bonding, some interfaces may fail to initialize while others succeed. The GBS is considered operationally 'up' if at least one bonded BCE is operationally 'up'. When all BCEs connected to the GBS are 'down', the GBS SHALL be considered operationally 'lowerLayerDown'. The GBS SHALL be considered operationally
断开的BCE可以通过将ifAdminStatus从“向下”更改为“向上”来初始化。将GBS上的ifAdminStatus更改为“up”将初始化连接到该特定GBS的所有BCE。注意，在绑定的情况下，一些接口可能无法初始化，而另一些接口则成功初始化。如果至少有一家保税BCE在运营上处于“上升”状态，则认为GBS在运营上处于“上升”状态。当所有连接到GBS的BCE都“关闭”时，GBS应被视为操作上的“较低层向下”。应在操作上考虑GBS
'notPresent' if it is not connected to any BCE. The GBS/BCE interface SHALL remain operationally 'down' during initialization, indicated by the 'init' value of the gBondPortStatFltStatus object.
如果未连接到任何BCE，“不存在”。GBS/BCE接口在初始化期间应保持操作“关闭”，由gBondPortStatFltStatus对象的“init”值指示。
Both BCE and GBS interfaces are managed using interface-specific management objects defined in the GBOND-MIB module and generic interface objects from the ifTable of the IF-MIB, with all management table entries referenced by the interface index ifIndex.
BCE和GBS接口均使用GBOND-MIB模块中定义的接口特定管理对象和IF-MIB ifTable中的通用接口对象进行管理，所有管理表项均由接口索引ifIndex引用。
The following table summarizes G.Bond-specific interpretations for some of the ifTable objects specified by the mandatory ifGeneralInformationGroup:
下表总结了强制IFGeneralInformation Group指定的某些ifTable对象的G.Bond特定解释：
+---------------+---------------------------------------------------+
| IF-MIB Object | G.Bond Interpretation |
+---------------+---------------------------------------------------+
| ifIndex | Interface index. Note that each BCE and each GBS |
| | in the G.Bond PHY MUST have a unique index, as |
| | there are some GBS- and BCE-specific attributes |
| | accessible only on the GBS or BCE level. |
+---------------+---------------------------------------------------+
| ifType | g9981(263), g9982(264), or g9983(265) for the |
| | ATM, Ethernet, or TDIM GBS, respectively; |
| | shdsl(169) for the G.SHDSL BCE, vdsl(97) for the |
| | VDSL BCE, etc. |
+---------------+---------------------------------------------------+
| ifSpeed | Operating data rate for the BCE. For the GBS, it |
| | is the sum of the current operating data rates of |
| | all BCEs in the aggregation group, without the |
| | encapsulation overhead and G.Bond overhead, but |
| | accounting for Inter-Frame Gaps (IFG). When a |
| | GBS or a BCE is operating in an asymmetrical |
| | fashion (the upstream data rate differs from the |
| | downstream one), the lowest of the values is |
| | shown. |
+---------------+---------------------------------------------------+
| ifAdminStatus | Setting this object to 'up' instructs a |
| | particular GBS (with all BCEs connected to it) or |
| | a BCE to start the initialization process. |
+---------------+---------------------------------------------------+
| ifOperStatus | A relevant *Status object from a particular line |
| | MIB supplements the value of ifOperStatus for |
| | BCEs. gBondPortStatFltStatus supplements the |
| | value of ifOperStatus for a GBS. Note that both |
| | relevant objects shall be inspected to determine |
| | the real operational status of a BCE/GBS port, |
| | e.g., a GBS port may be operationally 'up' with |
| | gBondPortStatFltStatus indicating lowRate(4) |
| | fault condition, or 'down' with no gBond faults. |
+---------------+---------------------------------------------------+
+---------------+---------------------------------------------------+
| IF-MIB Object | G.Bond Interpretation |
+---------------+---------------------------------------------------+
| ifIndex | Interface index. Note that each BCE and each GBS |
| | in the G.Bond PHY MUST have a unique index, as |
| | there are some GBS- and BCE-specific attributes |
| | accessible only on the GBS or BCE level. |
+---------------+---------------------------------------------------+
| ifType | g9981(263), g9982(264), or g9983(265) for the |
| | ATM, Ethernet, or TDIM GBS, respectively; |
| | shdsl(169) for the G.SHDSL BCE, vdsl(97) for the |
| | VDSL BCE, etc. |
+---------------+---------------------------------------------------+
| ifSpeed | Operating data rate for the BCE. For the GBS, it |
| | is the sum of the current operating data rates of |
| | all BCEs in the aggregation group, without the |
| | encapsulation overhead and G.Bond overhead, but |
| | accounting for Inter-Frame Gaps (IFG). When a |
| | GBS or a BCE is operating in an asymmetrical |
| | fashion (the upstream data rate differs from the |
| | downstream one), the lowest of the values is |
| | shown. |
+---------------+---------------------------------------------------+
| ifAdminStatus | Setting this object to 'up' instructs a |
| | particular GBS (with all BCEs connected to it) or |
| | a BCE to start the initialization process. |
+---------------+---------------------------------------------------+
| ifOperStatus | A relevant *Status object from a particular line |
| | MIB supplements the value of ifOperStatus for |
| | BCEs. gBondPortStatFltStatus supplements the |
| | value of ifOperStatus for a GBS. Note that both |
| | relevant objects shall be inspected to determine |
| | the real operational status of a BCE/GBS port, |
| | e.g., a GBS port may be operationally 'up' with |
| | gBondPortStatFltStatus indicating lowRate(4) |
| | fault condition, or 'down' with no gBond faults. |
+---------------+---------------------------------------------------+
Table 1: G.Bond Interpretation of IF-MIB Objects
表1:G.IF-MIB对象的键解释
The MIB module defined in this document is common to all G.998 bonding schemes. It MUST be used in conjunction with a bonding scheme-specific MIB module:
本文件中定义的MIB模块是所有G.998键合方案的通用模块。它必须与特定于绑定方案的MIB模块结合使用：
o G9981-MIB [RFC6768] for a G.998.1 bonded interface.
o G9981-MIB[RFC6768]用于G.998.1粘结界面。
o G9982-MIB [RFC6767] for a G.998.2 bonded interface.
o G9982-MIB[RFC6767]用于G.998.2粘结界面。
o G9983-MIB [RFC6766] for a G.998.3 bonded interface.
o G9983-MIB[RFC6766]用于G.998.3粘结界面。
Each xDSL technology is described in a relevant xDSL line MIB module: e.g., the HDSL2-SHDSL-LINE-MIB [RFC4319] for G.SHDSL, ADSL-LINE-EXT-MIB [RFC3440] for ADSL, ADSL2-LINE-MIB [RFC4706] for ADSL2, VDSL-LINE-MIB [RFC3728] for VDSL, or VDSL2-LINE-MIB [RFC5650] for VDSL2.
每个xDSL技术都在相关的xDSL线路MIB模块中描述：例如，用于g.SHDSL的HDSL2-SHDSL-line-MIB[RFC4319]，用于ADSL的ADSL-line-EXT-MIB[RFC3440]，用于ADSL2的ADSL2-line-MIB[RFC4706]，用于VDSL的VDSL-line-MIB[RFC3728]，或用于VDSL2的VDSL2-line-MIB[RFC5650]。
These MIB modules are used to manage individual xDSL lines/channels (BCEs).
这些MIB模块用于管理各个xDSL线路/通道（BCE）。
In case a new bonding scheme is introduced in a revision of G.998, IANA can update the IANA-maintained MIB module, adding the corresponding new value to the IANAgBondScheme and IANAgBondSchemeList textual conventions, as well as listing the new scheme-specific MIB module's name (e.g., G998x-MIB).
如果G.998版本中引入了新的绑定方案，IANA可以更新IANA维护的MIB模块，向IANAgBondScheme和IANAgBondSchemeList文本约定添加相应的新值，并列出新方案特定的MIB模块的名称（例如G998x MIB）。
Any scheme-specific aspect of an existing GBOND-MIB object SHALL be described in the corresponding G998x-MIB module, to prevent an unnecessary reissue of the GBOND-MIB module. For example, an exact definition of an Errored Second (ES) or a Severely Errored Second (SES) can be bonding-scheme specific; see the definitions for the gBondPortPmCurES and gBondPortPmCurSES objects.
应在相应的G998x MIB模块中描述现有GBOND-MIB对象的任何方案特定方面，以防止不必要地重新发布GBOND-MIB模块。例如，错误秒（ES）或严重错误秒（SES）的准确定义可以是特定于键合方案的；请参见gBondPortPmCurES和gBondPortPmCurSES对象的定义。
The main management objects defined in the GBOND-MIB module are split into 2 groups, structured as recommended by RFC 4181 [RFC4181]:
GBOND-MIB模块中定义的主要管理对象分为2个组，按照RFC 4181[RFC4181]的建议进行结构：
o gBondPort - containing objects for configuration, capabilities, status, historical Performance Monitoring, and notifications, common to all G.Bond ports (GBS).
o gBondPort-包含配置、功能、状态、历史性能监视和通知的对象，所有G.Bond端口（GBS）通用。
o gBondBce - containing a single common object for configuration of the remote discovery code per BCE. Note that the rest of the objects for BCE configuration, capabilities, status, and notifications are located in relevant xDSL line MIB modules as well as in the bonding scheme-specific MIB modules.
o gBondBce—包含单个公共对象，用于配置每个BCE的远程发现代码。请注意，BCE配置、功能、状态和通知的其余对象位于相关xDSL线路MIB模块以及特定于绑定方案的MIB模块中。
The OPTIONAL Performance Monitoring counters, thresholds, and history buckets (interval-counters) defined in [TR-159] are implemented using the textual conventions defined in the HC-PerfHist-TC-MIB [RFC3705]. The HC-PerfHist-TC-MIB defines 64-bit versions of the textual conventions found in the PerfHist-TC-MIB [RFC3593].
[TR-159]中定义的可选性能监控计数器、阈值和历史存储桶（间隔计数器）使用HC PerfHist TC MIB[RFC3705]中定义的文本约定实现。HC PerfHist TC MIB定义了PerfHist TC MIB[RFC3593]中的文本约定的64位版本。
The agent SHOULD align the beginning of each interval to a fifteen-minute boundary of a wall clock. Likewise, the beginning of each one-day interval SHOULD be aligned with the start of a day.
代理应将每个间隔的开始与挂钟的15分钟边界对齐。同样，每一天间隔的开始应该与一天的开始保持一致。
The rationale behind this is to simplify collection and analysis of Performance Monitoring (PM) from multiple agents by a network management system (NMS) -- each PM interval can be "time-stamped" using the gBond*IntervalIndex object, from the fact that the 1-day interval starts at 00:00 and the 15-minute intervals are aligned with each 1/4 hour and the network-wide "wall clock", typically distributed via NTP or the Simple Network Time Protocol (SNTP) [RFC5905]. If the agent does not have access to the wall clock, a local clock can be used. In this case, as well as when coping with multiple time zones, the NMS would have to correlate the difference between the agent's local clock (available, for example, via the hrSystemDate object from the HOST-RESOURCES-MIB [RFC2790]) and the wall clock.
其基本原理是简化网络管理系统（NMS）从多个代理收集和分析性能监控（PM）——每个PM间隔可以使用gBond*IntervalIndex对象“时间戳”，1天的时间间隔从00:00开始，15分钟的时间间隔与每1/4小时和网络范围的“挂钟”一致，通常通过NTP或简单网络时间协议（SNTP）[RFC5905]分发。如果代理无法访问挂钟，则可以使用本地时钟。在这种情况下，以及在处理多个时区时，NMS必须关联代理的本地时钟（例如，通过HOST-RESOURCES-MIB[RFC2790]中的hrSystemDate对象可用）和挂钟之间的差异。
Counters are not reset when a GBS is re-initialized, but rather only when the agent is reset or re-initialized.
当GBS重新初始化时，计数器不会重置，而仅当代理重置或重新初始化时才会重置。
Note that the accumulation of certain performance events for a monitored entity is inhibited (counting stops) during periods of service unavailability on that monitored entity. The DESCRIPTION clause of Performance Monitoring counters in this MIB module specifies which of the counters are inhibited during periods of service unavailability.
请注意，受监控实体的某些性能事件的累积在该受监控实体的服务不可用期间被禁止（计数停止）。此MIB模块中性能监视计数器的DESCRIPTION子句指定在服务不可用期间禁止哪些计数器。
This section contains the mapping between relevant managed objects (attributes) defined in [TR-159] and managed objects defined in this document and in associated MIB modules, i.e., the IF-MIB [RFC2863].
本节包含[TR-159]中定义的相关托管对象（属性）与本文档和相关MIB模块（即IF-MIB[RFC2863]）中定义的托管对象之间的映射。
+--------------------------------+------------------------------------+
| G.Bond Managed Object | Corresponding SNMP Object |
+--------------------------------+------------------------------------+
| oBondingGroup - Basic Package | |
| (Mandatory) | |
+--------------------------------+------------------------------------+
| aGroupID | ifIndex (IF-MIB) |
+--------------------------------+------------------------------------+
| aGroupBondSchemesSupported | gBondPortCapSchemesSupported |
+--------------------------------+------------------------------------+
| aGroupPeerBondSchemesSupported | gBondPortCapPeerSchemesSupported |
+--------------------------------+------------------------------------+
| aGroupAdminBondScheme | gBondPortConfAdminScheme |
+--------------------------------+------------------------------------+
| aGroupPeerAdminBondScheme | gBondPortConfPeerAdminScheme |
+--------------------------------+------------------------------------+
| aGroupOperBondScheme | gBondPortStatOperScheme |
+--------------------------------+------------------------------------+
| aGroupPeerOperBondScheme | gBondPortStatPeerOperScheme |
+--------------------------------+------------------------------------+
| aGroupEnd | gBondPortStatSide |
+--------------------------------+------------------------------------+
| aGroupOperState | ifOperStatus (IF-MIB) |
+--------------------------------+------------------------------------+
| aGroupAdminState | ifAdminStatus (IF-MIB) |
+--------------------------------+------------------------------------+
| aGroupStatus | gBondPortStatFltStatus |
+--------------------------------+------------------------------------+
| aGroupCapacity | gBondPortCapCapacity |
+--------------------------------+------------------------------------+
| aGroupPeerCapacity | gBondPortCapPeerCapacity |
+--------------------------------+------------------------------------+
| aGroupNumChannels | gBondPortStatNumBCEs |
+--------------------------------+------------------------------------+
| aGroupName | ifName (IF-MIB) |
+--------------------------------+------------------------------------+
| aGroupDiscoveryCode | gBondPortConfDiscoveryCode |
+--------------------------------+------------------------------------+
| aGroupUpRate | gBondPortStatUpDataRate |
+--------------------------------+------------------------------------+
| aGroupDownRate | gBondPortStatDnDataRate |
+--------------------------------+------------------------------------+
| aGroupTargetUpRate | gBondPortConfTargetUpDataRate |
+--------------------------------+------------------------------------+
| aGroupTargetDownRate | gBondPortConfTargetDnDataRate |
+--------------------------------+------------------------------------+
| aGroupThreshLowUpRate | gBondPortConfThreshLowUpRate |
+--------------------------------+------------------------------------+
+--------------------------------+------------------------------------+
| G.Bond Managed Object | Corresponding SNMP Object |
+--------------------------------+------------------------------------+
| oBondingGroup - Basic Package | |
| (Mandatory) | |
+--------------------------------+------------------------------------+
| aGroupID | ifIndex (IF-MIB) |
+--------------------------------+------------------------------------+
| aGroupBondSchemesSupported | gBondPortCapSchemesSupported |
+--------------------------------+------------------------------------+
| aGroupPeerBondSchemesSupported | gBondPortCapPeerSchemesSupported |
+--------------------------------+------------------------------------+
| aGroupAdminBondScheme | gBondPortConfAdminScheme |
+--------------------------------+------------------------------------+
| aGroupPeerAdminBondScheme | gBondPortConfPeerAdminScheme |
+--------------------------------+------------------------------------+
| aGroupOperBondScheme | gBondPortStatOperScheme |
+--------------------------------+------------------------------------+
| aGroupPeerOperBondScheme | gBondPortStatPeerOperScheme |
+--------------------------------+------------------------------------+
| aGroupEnd | gBondPortStatSide |
+--------------------------------+------------------------------------+
| aGroupOperState | ifOperStatus (IF-MIB) |
+--------------------------------+------------------------------------+
| aGroupAdminState | ifAdminStatus (IF-MIB) |
+--------------------------------+------------------------------------+
| aGroupStatus | gBondPortStatFltStatus |
+--------------------------------+------------------------------------+
| aGroupCapacity | gBondPortCapCapacity |
+--------------------------------+------------------------------------+
| aGroupPeerCapacity | gBondPortCapPeerCapacity |
+--------------------------------+------------------------------------+
| aGroupNumChannels | gBondPortStatNumBCEs |
+--------------------------------+------------------------------------+
| aGroupName | ifName (IF-MIB) |
+--------------------------------+------------------------------------+
| aGroupDiscoveryCode | gBondPortConfDiscoveryCode |
+--------------------------------+------------------------------------+
| aGroupUpRate | gBondPortStatUpDataRate |
+--------------------------------+------------------------------------+
| aGroupDownRate | gBondPortStatDnDataRate |
+--------------------------------+------------------------------------+
| aGroupTargetUpRate | gBondPortConfTargetUpDataRate |
+--------------------------------+------------------------------------+
| aGroupTargetDownRate | gBondPortConfTargetDnDataRate |
+--------------------------------+------------------------------------+
| aGroupThreshLowUpRate | gBondPortConfThreshLowUpRate |
+--------------------------------+------------------------------------+
+--------------------------------+------------------------------------+
| aGroupThreshLowDownRate | gBondPortConfThreshLowDnRate |
+--------------------------------+------------------------------------+
| aGroupLowRateCrossingEnable | gBondPortConfLowRateCrossingEnable |
+--------------------------------+------------------------------------+
| nGroupLowUpRateCrossing | gBondLowUpRateCrossing |
+--------------------------------+------------------------------------+
| nGroupLowDownRateCrossing | gBondLowDnRateCrossing |
+--------------------------------+------------------------------------+
| aGroupLinkUpDownEnable | ifLinkUpDownTrapEnable (IF-MIB) |
+--------------------------------+------------------------------------+
| nGroupLinkUp | linkUp (IF-MIB) |
+--------------------------------+------------------------------------+
| nGroupLinkDown | linkDown (IF-MIB) |
+--------------------------------+------------------------------------+
| oBondingGroup - PM Package | |
| (Optional) | |
+--------------------------------+------------------------------------+
| aGroupPerfES | gBondPortPmCurES |
+--------------------------------+------------------------------------+
| aGroupPerfSES | gBondPortPmCurSES |
+--------------------------------+------------------------------------+
| aGroupPerfUAS | gBondPortPmCurUAS |
+--------------------------------+------------------------------------+
| aGroupPerf15MinValidIntervals | gBondPortPmCur15MinValidIntervals |
+--------------------------------+------------------------------------+
| aGroupPerf15MinInvalidIntervals| gBondPortPmCur15MinInvalidIntervals|
+--------------------------------+------------------------------------+
| aGroupPerfCurr15MinTimeElapsed | gBondPortPmCur15MinTimeElapsed |
+--------------------------------+------------------------------------+
| aGroupPerfCurr15MinES | gBondPortPmCur15MinES |
+--------------------------------+------------------------------------+
| aGroupPerfCurr15MinSES | gBondPortPmCur15MinSES |
+--------------------------------+------------------------------------+
| aGroupPerfCurr15MinUAS | gBondPortPmCur15MinUAS |
+--------------------------------+------------------------------------+
| aGroupPerfTcaEnable | gBondPortConfPmTcaEnable |
+--------------------------------+------------------------------------+
| aGroupPerfThreshold15MinES | gBondPortPmTcaProfileThresh15MinES |
+--------------------------------+------------------------------------+
| aGroupPerfThreshold15MinSES | gBondPortPmTcaProfileThresh15MinSES|
+--------------------------------+------------------------------------+
| aGroupPerfThreshold15MinUAS | gBondPortPmTcaProfileThresh15MinUAS|
+--------------------------------+------------------------------------+
| nGroupPerfTca15MinES | gBondPmTca15MinESCrossing |
+--------------------------------+------------------------------------+
| nGroupPerfTca15MinSES | gBondPmTca15MinSESCrossing |
+--------------------------------+------------------------------------+
+--------------------------------+------------------------------------+
| aGroupThreshLowDownRate | gBondPortConfThreshLowDnRate |
+--------------------------------+------------------------------------+
| aGroupLowRateCrossingEnable | gBondPortConfLowRateCrossingEnable |
+--------------------------------+------------------------------------+
| nGroupLowUpRateCrossing | gBondLowUpRateCrossing |
+--------------------------------+------------------------------------+
| nGroupLowDownRateCrossing | gBondLowDnRateCrossing |
+--------------------------------+------------------------------------+
| aGroupLinkUpDownEnable | ifLinkUpDownTrapEnable (IF-MIB) |
+--------------------------------+------------------------------------+
| nGroupLinkUp | linkUp (IF-MIB) |
+--------------------------------+------------------------------------+
| nGroupLinkDown | linkDown (IF-MIB) |
+--------------------------------+------------------------------------+
| oBondingGroup - PM Package | |
| (Optional) | |
+--------------------------------+------------------------------------+
| aGroupPerfES | gBondPortPmCurES |
+--------------------------------+------------------------------------+
| aGroupPerfSES | gBondPortPmCurSES |
+--------------------------------+------------------------------------+
| aGroupPerfUAS | gBondPortPmCurUAS |
+--------------------------------+------------------------------------+
| aGroupPerf15MinValidIntervals | gBondPortPmCur15MinValidIntervals |
+--------------------------------+------------------------------------+
| aGroupPerf15MinInvalidIntervals| gBondPortPmCur15MinInvalidIntervals|
+--------------------------------+------------------------------------+
| aGroupPerfCurr15MinTimeElapsed | gBondPortPmCur15MinTimeElapsed |
+--------------------------------+------------------------------------+
| aGroupPerfCurr15MinES | gBondPortPmCur15MinES |
+--------------------------------+------------------------------------+
| aGroupPerfCurr15MinSES | gBondPortPmCur15MinSES |
+--------------------------------+------------------------------------+
| aGroupPerfCurr15MinUAS | gBondPortPmCur15MinUAS |
+--------------------------------+------------------------------------+
| aGroupPerfTcaEnable | gBondPortConfPmTcaEnable |
+--------------------------------+------------------------------------+
| aGroupPerfThreshold15MinES | gBondPortPmTcaProfileThresh15MinES |
+--------------------------------+------------------------------------+
| aGroupPerfThreshold15MinSES | gBondPortPmTcaProfileThresh15MinSES|
+--------------------------------+------------------------------------+
| aGroupPerfThreshold15MinUAS | gBondPortPmTcaProfileThresh15MinUAS|
+--------------------------------+------------------------------------+
| nGroupPerfTca15MinES | gBondPmTca15MinESCrossing |
+--------------------------------+------------------------------------+
| nGroupPerfTca15MinSES | gBondPmTca15MinSESCrossing |
+--------------------------------+------------------------------------+
+--------------------------------+------------------------------------+
| nGroupPerfTca15MinUAS | gBondPmTca15MinUASCrossing |
+--------------------------------+------------------------------------+
| aGroupPerf1DayValidIntervals | gBondPortPmCur1DayValidIntervals |
+--------------------------------+------------------------------------+
| aGroupPerf1DayInvalidIntervals | gBondPortPmCur1DayInvalidIntervals |
+--------------------------------+------------------------------------+
| aGroupPerfCurr1DayTimeElapsed | gBondPortPmCur1DayTimeElapsed |
+--------------------------------+------------------------------------+
| aGroupPerfCurr1DayES | gBondPortPmCur1DayIntervalES |
+--------------------------------+------------------------------------+
| aGroupPerfCurr1DaySES | gBondPortPmCur1DayIntervalSES |
+--------------------------------+------------------------------------+
| aGroupPerfCurr1DayUAS | gBondPortPmCur1DayIntervalUAS |
+--------------------------------+------------------------------------+
| aGroupPerfThreshold1DayES | gBondPortPmTcaProfileThresh1DayES |
+--------------------------------+------------------------------------+
| aGroupPerfThreshold1DaySES | gBondPortPmTcaProfileThresh1DaySES |
+--------------------------------+------------------------------------+
| aGroupPerfThreshold1DayUAS | gBondPortPmTcaProfileThresh1DayUAS |
+--------------------------------+------------------------------------+
| nGroupPerfTca1DayES | gBondPmTca1DayESCrossing |
+--------------------------------+------------------------------------+
| nGroupPerfTca1DaySES | gBondPmTca1DaySESCrossing |
+--------------------------------+------------------------------------+
| nGroupPerfTca1DayUAS | gBondPmTca1DayUASCrossing |
+--------------------------------+------------------------------------+
| aGroupPerf15MinIntervalNumber | gBondPortPm15MinIntervalIndex |
+--------------------------------+------------------------------------+
| aGroupPerf15MinIntervalValid | gBondPortPm15MinIntervalValid |
+--------------------------------+------------------------------------+
| aGroupPerf15MinIntervalES | gBondPortPm15MinIntervalES |
+--------------------------------+------------------------------------+
| aGroupPerf15MinIntervalSES | gBondPortPm15MinIntervalSES |
+--------------------------------+------------------------------------+
| aGroupPerf15MinIntervalUAS | gBondPortPm15MinIntervalUAS |
+--------------------------------+------------------------------------+
| aGroupPerf1DayIntervalNumber | gBondPortPm1DayIntervalIndex |
+--------------------------------+------------------------------------+
| aGroupPerf1DayIntervalValid | gBondPortPm1DayIntervalValid |
+--------------------------------+------------------------------------+
| aGroupPerf1DayIntervalMoniSecs | gBondPortPm1DayIntervalMoniTime |
+--------------------------------+------------------------------------+
| aGroupPerf1DayIntervalES | gBondPortPm1DayIntervalES |
+--------------------------------+------------------------------------+
| aGroupPerf1DayIntervalSES | gBondPortPm1DayIntervalSES |
+--------------------------------+------------------------------------+
+--------------------------------+------------------------------------+
| nGroupPerfTca15MinUAS | gBondPmTca15MinUASCrossing |
+--------------------------------+------------------------------------+
| aGroupPerf1DayValidIntervals | gBondPortPmCur1DayValidIntervals |
+--------------------------------+------------------------------------+
| aGroupPerf1DayInvalidIntervals | gBondPortPmCur1DayInvalidIntervals |
+--------------------------------+------------------------------------+
| aGroupPerfCurr1DayTimeElapsed | gBondPortPmCur1DayTimeElapsed |
+--------------------------------+------------------------------------+
| aGroupPerfCurr1DayES | gBondPortPmCur1DayIntervalES |
+--------------------------------+------------------------------------+
| aGroupPerfCurr1DaySES | gBondPortPmCur1DayIntervalSES |
+--------------------------------+------------------------------------+
| aGroupPerfCurr1DayUAS | gBondPortPmCur1DayIntervalUAS |
+--------------------------------+------------------------------------+
| aGroupPerfThreshold1DayES | gBondPortPmTcaProfileThresh1DayES |
+--------------------------------+------------------------------------+
| aGroupPerfThreshold1DaySES | gBondPortPmTcaProfileThresh1DaySES |
+--------------------------------+------------------------------------+
| aGroupPerfThreshold1DayUAS | gBondPortPmTcaProfileThresh1DayUAS |
+--------------------------------+------------------------------------+
| nGroupPerfTca1DayES | gBondPmTca1DayESCrossing |
+--------------------------------+------------------------------------+
| nGroupPerfTca1DaySES | gBondPmTca1DaySESCrossing |
+--------------------------------+------------------------------------+
| nGroupPerfTca1DayUAS | gBondPmTca1DayUASCrossing |
+--------------------------------+------------------------------------+
| aGroupPerf15MinIntervalNumber | gBondPortPm15MinIntervalIndex |
+--------------------------------+------------------------------------+
| aGroupPerf15MinIntervalValid | gBondPortPm15MinIntervalValid |
+--------------------------------+------------------------------------+
| aGroupPerf15MinIntervalES | gBondPortPm15MinIntervalES |
+--------------------------------+------------------------------------+
| aGroupPerf15MinIntervalSES | gBondPortPm15MinIntervalSES |
+--------------------------------+------------------------------------+
| aGroupPerf15MinIntervalUAS | gBondPortPm15MinIntervalUAS |
+--------------------------------+------------------------------------+
| aGroupPerf1DayIntervalNumber | gBondPortPm1DayIntervalIndex |
+--------------------------------+------------------------------------+
| aGroupPerf1DayIntervalValid | gBondPortPm1DayIntervalValid |
+--------------------------------+------------------------------------+
| aGroupPerf1DayIntervalMoniSecs | gBondPortPm1DayIntervalMoniTime |
+--------------------------------+------------------------------------+
| aGroupPerf1DayIntervalES | gBondPortPm1DayIntervalES |
+--------------------------------+------------------------------------+
| aGroupPerf1DayIntervalSES | gBondPortPm1DayIntervalSES |
+--------------------------------+------------------------------------+
+--------------------------------+------------------------------------+
| aGroupPerf1DayIntervalUAS | gBondPortPm1DayIntervalUAS |
+--------------------------------+------------------------------------+
| oLine - Basic Package | |
| (Mandatory) | |
+--------------------------------+------------------------------------+
| aLineID | ifIndex (IF-MIB) |
+--------------------------------+------------------------------------+
| aLineType | ifType (IF-MIB) |
+--------------------------------+------------------------------------+
| aLineOperState | ifOperStatus (IF-MIB) |
+--------------------------------+------------------------------------+
| aLineStatus | *dsl*CurrStatus (*DSL-LINE-MIB) |
+--------------------------------+------------------------------------+
| aLineEnd | *dsl*Side (*DSL-LINE-MIB) |
+--------------------------------+------------------------------------+
| aLineAdminState | ifAdminStatus (IF-MIB) |
+--------------------------------+------------------------------------+
| aLineRemoteDiscoveryCode | gBondBceConfRemoteDiscoveryCode |
+--------------------------------+------------------------------------+
| aLineUpDownEnable | ifLinkUpDownTrapEnable (IF-MIB) |
+--------------------------------+------------------------------------+
| nLineUp | LinkUp (IF-MIB) |
+--------------------------------+------------------------------------+
| nLineDown | LinkDown (IF-MIB) |
+--------------------------------+------------------------------------+
| oChannel - Basic Package | |
| (Mandatory) | |
+--------------------------------+------------------------------------+
| aChannelID | ifIndex (IF-MIB) |
+--------------------------------+------------------------------------+
| aChannelGroupID | |
+--------------------------------+------------------------------------+
| aChannelType | ifType (IF-MIB) |
+--------------------------------+------------------------------------+
| aChannelOperState | ifOperStatus (IF-MIB) |
+--------------------------------+------------------------------------+
| aChannelStatus | *dsl*CurrStatus (*DSL-LINE-MIB), |
| | xdsl2ChStatus*Status |
| | (VDSL2-LINE-MIB) |
+--------------------------------+------------------------------------+
+--------------------------------+------------------------------------+
| aGroupPerf1DayIntervalUAS | gBondPortPm1DayIntervalUAS |
+--------------------------------+------------------------------------+
| oLine - Basic Package | |
| (Mandatory) | |
+--------------------------------+------------------------------------+
| aLineID | ifIndex (IF-MIB) |
+--------------------------------+------------------------------------+
| aLineType | ifType (IF-MIB) |
+--------------------------------+------------------------------------+
| aLineOperState | ifOperStatus (IF-MIB) |
+--------------------------------+------------------------------------+
| aLineStatus | *dsl*CurrStatus (*DSL-LINE-MIB) |
+--------------------------------+------------------------------------+
| aLineEnd | *dsl*Side (*DSL-LINE-MIB) |
+--------------------------------+------------------------------------+
| aLineAdminState | ifAdminStatus (IF-MIB) |
+--------------------------------+------------------------------------+
| aLineRemoteDiscoveryCode | gBondBceConfRemoteDiscoveryCode |
+--------------------------------+------------------------------------+
| aLineUpDownEnable | ifLinkUpDownTrapEnable (IF-MIB) |
+--------------------------------+------------------------------------+
| nLineUp | LinkUp (IF-MIB) |
+--------------------------------+------------------------------------+
| nLineDown | LinkDown (IF-MIB) |
+--------------------------------+------------------------------------+
| oChannel - Basic Package | |
| (Mandatory) | |
+--------------------------------+------------------------------------+
| aChannelID | ifIndex (IF-MIB) |
+--------------------------------+------------------------------------+
| aChannelGroupID | |
+--------------------------------+------------------------------------+
| aChannelType | ifType (IF-MIB) |
+--------------------------------+------------------------------------+
| aChannelOperState | ifOperStatus (IF-MIB) |
+--------------------------------+------------------------------------+
| aChannelStatus | *dsl*CurrStatus (*DSL-LINE-MIB), |
| | xdsl2ChStatus*Status |
| | (VDSL2-LINE-MIB) |
+--------------------------------+------------------------------------+
Table 2: Mapping of TR-159 Managed Objects
表2:TR-159托管对象的映射
The GBOND-MIB module IMPORTS objects from SNMPv2-SMI [RFC2578], SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], SNMP-FRAMEWORK-MIB [RFC3411], IF-MIB [RFC2863], and HC-PerfHist-TC-MIB [RFC3705]. The module has been structured as recommended by [RFC4181].
GBOND-MIB模块从SNMPv2 SMI[RFC2578]、SNMPv2 TC[RFC2579]、SNMPv2 CONF[RFC2580]、SNMP-FRAMEWORK-MIB[RFC3411]、IF-MIB[RFC2863]和HC PerfHist TC MIB[RFC3705]导入对象。该模块的结构符合[RFC4181]的建议。
GBOND-MIB DEFINITIONS ::= BEGIN
GBOND-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY,
OBJECT-TYPE,
NOTIFICATION-TYPE,
mib-2,
Unsigned32,
Gauge32
FROM SNMPv2-SMI -- RFC 2578
TEXTUAL-CONVENTION,
TruthValue,
RowStatus,
PhysAddress
FROM SNMPv2-TC -- RFC 2579
MODULE-COMPLIANCE,
OBJECT-GROUP,
NOTIFICATION-GROUP
FROM SNMPv2-CONF -- RFC 2580
SnmpAdminString
FROM SNMP-FRAMEWORK-MIB -- RFC 3411
ifIndex
FROM IF-MIB -- RFC 2863
HCPerfCurrentCount,
HCPerfIntervalCount,
HCPerfIntervalThreshold,
HCPerfValidIntervals,
HCPerfInvalidIntervals,
HCPerfTimeElapsed,
HCPerfTotalCount
FROM HC-PerfHist-TC-MIB -- RFC 3705
IANAgBondScheme,
IANAgBondSchemeList
FROM IANA-GBOND-TC-MIB
;
------------------------------------------------------------------------
IMPORTS
MODULE-IDENTITY,
OBJECT-TYPE,
NOTIFICATION-TYPE,
mib-2,
Unsigned32,
Gauge32
FROM SNMPv2-SMI -- RFC 2578
TEXTUAL-CONVENTION,
TruthValue,
RowStatus,
PhysAddress
FROM SNMPv2-TC -- RFC 2579
MODULE-COMPLIANCE,
OBJECT-GROUP,
NOTIFICATION-GROUP
FROM SNMPv2-CONF -- RFC 2580
SnmpAdminString
FROM SNMP-FRAMEWORK-MIB -- RFC 3411
ifIndex
FROM IF-MIB -- RFC 2863
HCPerfCurrentCount,
HCPerfIntervalCount,
HCPerfIntervalThreshold,
HCPerfValidIntervals,
HCPerfInvalidIntervals,
HCPerfTimeElapsed,
HCPerfTotalCount
FROM HC-PerfHist-TC-MIB -- RFC 3705
IANAgBondScheme,
IANAgBondSchemeList
FROM IANA-GBOND-TC-MIB
;
------------------------------------------------------------------------
gBondMIB MODULE-IDENTITY
LAST-UPDATED "201302200000Z" -- 20 February 2013
ORGANIZATION "IETF ADSL MIB Working Group"
CONTACT-INFO
"WG charter:
http://datatracker.ietf.org/wg/adslmib/charter/
gBondMIB MODULE-IDENTITY
LAST-UPDATED "201302200000Z" -- 20 February 2013
ORGANIZATION "IETF ADSL MIB Working Group"
CONTACT-INFO
"WG charter:
http://datatracker.ietf.org/wg/adslmib/charter/
Mailing Lists:
General Discussion: adslmib@ietf.org
To Subscribe: adslmib-request@ietf.org
In Body: subscribe your_email_address
Mailing Lists:
General Discussion: adslmib@ietf.org
To Subscribe: adslmib-request@ietf.org
In Body: subscribe your_email_address
Chair: Menachem Dodge Postal: ECI Telecom, Ltd. 30 Hasivim St. Petach-Tikva 4951169 Israel Phone: +972-3-926-8421 EMail: menachemdodge1@gmail.com
主席：梅纳赫姆·道奇邮政：ECI电信有限公司30 Hasivim St.Petach Tikva 4951169以色列电话：+972-3-926-8421电子邮件：menachemdodge1@gmail.com
Editor: Edward Beili Postal: Actelis Networks, Inc. 25 Bazel St., P.O.B. 10173 Petach-Tikva 49103 Israel Phone: +972-3-924-3491 EMail: edward.beili@actelis.com
编辑：Edward Beili Postal:Actelis Networks，Inc.巴泽尔街25号，邮编：10173 Petach Tikva 49103以色列电话：+972-3-924-3491电子邮件：Edward。beili@actelis.com
Editor: Moti Morgenstern Postal: ECI Telecom 30 Hasivim St. Petach-Tikva 4951169 Israel Phone: +972-3-926-6258 EMail: moti.morgenstern@ecitele.com"
编辑：Moti Morgenstern Postal:ECI Telecom 30 Hasivim St.Petach Tikva 4951169以色列电话：+972-3-926-6258电子邮件：Moti。morgenstern@ecitele.com"
DESCRIPTION "The objects in this MIB module are used to manage the multi-pair bonded xDSL interfaces, as defined in ITU-T Recommendations G.998.1, G.998.2, and G.998.3.
描述“此MIB模块中的对象用于管理ITU-T建议G.998.1、G.998.2和G.998.3中定义的多对绑定xDSL接口。
This MIB module MUST be used in conjunction with a bonding scheme-specific MIB module, that is, G9981-MIB, G9982-MIB, or G9983-MIB.
此MIB模块必须与特定于绑定方案的MIB模块（即G9981-MIB、G9982-MIB或G9983-MIB）结合使用。
The following references are used throughout this MIB module:
此MIB模块中使用了以下参考：
[G.998.1] refers to: ITU-T Recommendation G.998.1: 'ATM-based multi-pair bonding', January 2005.
[G.998.1]参考：ITU-T建议G.998.1:“基于ATM的多对连接”，2005年1月。
[G.998.2] refers to: ITU-T Recommendation G.998.2: 'Ethernet-based multi-pair bonding', January 2005.
[G.998.2]参考：ITU-T建议G.998.2:“基于以太网的多对连接”，2005年1月。
[G.998.3] refers to: ITU-T Recommendation G.998.3: 'Multi-pair bonding using time-division inverse multiplexing', January 2005.
[G.998.3]参考：ITU-T建议G.998.3:“使用时分反向多路复用的多对键合”，2005年1月。
[TR-159] refers to: Broadband Forum Technical Report: 'Management Framework for xDSL Bonding', December 2008.
[TR-159]参考：宽带论坛技术报告：“xDSL连接管理框架”，2008年12月。
Naming Conventions: BCE - Bonding Channel Entity BTU - Bonding Terminating Unit BTU-C - Bonding Terminating Unit, CO side BTU-R - Bonding Terminating Unit, Remote Terminal (CPE) side CO - Central Office CPE - Customer Premises Equipment GBS - Generic Bonding Sub-layer PM - Performance Monitoring SNR - Signal to Noise Ratio TCA - Threshold Crossing Alert
命名约定：BCE-键合通道实体BTU-键合终止单元BTU-C-键合终止单元，共侧BTU-R-键合终止单元，远程终端（CPE）side CO-中央办公室CPE-客户场所设备GBS-通用粘合子层PM-性能监测SNR-信噪比TCA-阈值交叉警报
Copyright (c) 2013 IETF Trust and the persons identified as authors of the code. All rights reserved.
版权所有（c）2013 IETF信托基金和被确定为代码作者的人员。版权所有。
Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info)."
根据IETF信托有关IETF文件的法律规定第4.c节规定的简化BSD许可证中包含的许可条款，允许以源代码和二进制格式重新分发和使用，无论是否修改(http://trustee.ietf.org/license-info)."
REVISION "201302200000Z" -- 20 February 2013 DESCRIPTION "Initial version, published as RFC 6765."
修订版“201302200000Z”-2013年2月20日描述“初始版本，发布为RFC 6765。”
::= { mib-2 211 }
::= { mib-2 211 }
-- Sections of the module
-- Structured as recommended by RFC 4181, Appendix D
-- Sections of the module
-- Structured as recommended by RFC 4181, Appendix D
gBondObjects OBJECT IDENTIFIER ::= { gBondMIB 1 }
gBondObjects OBJECT IDENTIFIER ::= { gBondMIB 1 }
gBondConformance OBJECT IDENTIFIER ::= { gBondMIB 2 }
gBondConformance OBJECT IDENTIFIER ::= { gBondMIB 2 }
-- Groups in the module
--模块中的组
gBondPort OBJECT IDENTIFIER ::= { gBondObjects 1 }
gBondPort OBJECT IDENTIFIER ::= { gBondObjects 1 }
gBondBce OBJECT IDENTIFIER ::= { gBondObjects 2 }
gBondBce OBJECT IDENTIFIER ::= { gBondObjects 2 }
-- Textual Conventions
--文本约定
GBondPm1DayIntervalThreshold ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"This textual convention defines a range of values that may be
set in a fault threshold alarm control for a 1-day Performance
Monitoring interval.
As the number of seconds in a 1-day interval numbers at most
86400, objects of this type may have a range of 0...86400,
where the value of 0 disables the alarm."
SYNTAX Unsigned32 (0..86400)
GBondPm1DayIntervalThreshold ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"This textual convention defines a range of values that may be
set in a fault threshold alarm control for a 1-day Performance
Monitoring interval.
As the number of seconds in a 1-day interval numbers at most
86400, objects of this type may have a range of 0...86400,
where the value of 0 disables the alarm."
SYNTAX Unsigned32 (0..86400)
-- Port Notifications group
--端口通知组
gBondPortNotifications OBJECT IDENTIFIER ::= { gBondPort 0 }
gBondPortNotifications OBJECT IDENTIFIER ::= { gBondPort 0 }
gBondLowUpRateCrossing NOTIFICATION-TYPE
OBJECTS {
-- ifIndex is not needed here, since we are under specific GBS
gBondPortStatUpDataRate,
gBondPortConfThreshLowUpRate
}
STATUS current
DESCRIPTION
"This notification indicates that the G.Bond port's upstream
data rate has reached/dropped below or exceeded the low
upstream rate threshold, specified by
gBondPortConfThreshLowUpRate.
gBondLowUpRateCrossing NOTIFICATION-TYPE
OBJECTS {
-- ifIndex is not needed here, since we are under specific GBS
gBondPortStatUpDataRate,
gBondPortConfThreshLowUpRate
}
STATUS current
DESCRIPTION
"This notification indicates that the G.Bond port's upstream
data rate has reached/dropped below or exceeded the low
upstream rate threshold, specified by
gBondPortConfThreshLowUpRate.
This notification MAY be sent for the -O subtype ports 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 is below it) and from low to normal. This notification is not applicable to the -R subtypes.
当端口“向上”时，可在交叉事件的两个方向上为-O子类型端口发送此通知：从正常（速率高于阈值）到低（速率等于阈值或低于阈值）以及从低到正常。此通知不适用于-R子类型。
It is RECOMMENDED that a small debouncing period of 2.5 sec, between the detection of the condition and notification, be implemented to prevent simultaneous LinkUp/LinkDown and gBondLowUpRateCrossing notifications from being sent.
建议在检测到状况和通知之间实施2.5秒的小去抖动周期，以防止同时发送LinkUp/LinkDown和gBondLowUpRateCrossing通知。
The adaptive nature of the G.Bond 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 BCEs in the aggregation group, causing a rate degradation of the aggregated G.Bond link. The dropped BCEs would then try to re-initialize, possibly at a lower rate than before, adjusting the rate to provide the required target SNR margin.
G.Bond技术的适应性使港口能够适应铜环境的变化；e、 例如，脉冲噪声、外来串扰或微中断可暂时降低聚合组中的一个或多个bce，导致聚合g键链路的速率降低。然后，丢弃的BCE将尝试重新初始化，可能以比以前更低的速率，调整速率以提供所需的目标SNR裕度。
Generation of this notification is controlled by the gBondPortConfLowRateCrossingEnable object.
此通知的生成由gBondPortConfLowRateCrossingEnable对象控制。
This object maps to the TR-159 notification
nGroupLowUpRateCrossing."
REFERENCE
"[TR-159], Section 5.5.1.24"
::= { gBondPortNotifications 1 }
This object maps to the TR-159 notification
nGroupLowUpRateCrossing."
REFERENCE
"[TR-159], Section 5.5.1.24"
::= { gBondPortNotifications 1 }
gBondLowDnRateCrossing NOTIFICATION-TYPE
OBJECTS {
-- ifIndex is not needed here, since we are under specific GBS
gBondPortStatDnDataRate,
gBondPortConfThreshLowDnRate
}
STATUS current
DESCRIPTION
"This notification indicates that the G.Bond port's downstream
data rate has reached/dropped below or exceeded the low
downstream rate threshold, specified by
gBondPortConfThreshLowDnRate.
gBondLowDnRateCrossing NOTIFICATION-TYPE
OBJECTS {
-- ifIndex is not needed here, since we are under specific GBS
gBondPortStatDnDataRate,
gBondPortConfThreshLowDnRate
}
STATUS current
DESCRIPTION
"This notification indicates that the G.Bond port's downstream
data rate has reached/dropped below or exceeded the low
downstream rate threshold, specified by
gBondPortConfThreshLowDnRate.
This notification MAY be sent for the -O subtype ports 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 is below it) and from low to normal. This notification is not applicable to the -R subtypes.
当端口“向上”时，可在交叉事件的两个方向上为-O子类型端口发送此通知：从正常（速率高于阈值）到低（速率等于阈值或低于阈值）以及从低到正常。此通知不适用于-R子类型。
It is RECOMMENDED that a small debouncing period of 2.5 sec, between the detection of the condition and notification, be implemented to prevent simultaneous LinkUp/LinkDown and gBondLowDnRateCrossing notifications from being sent.
建议在检测到状况和通知之间实施2.5秒的小去抖动周期，以防止同时发送链路上升/链路下降和GBondlowdRateCrossing通知。
The adaptive nature of the G.Bond 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 BCEs in the aggregation group, causing a rate degradation of the aggregated G.Bond link. The dropped BCEs would then try to re-initialize, possibly at a lower rate than before, adjusting the rate to provide the required target SNR margin.
G.Bond技术的适应性使港口能够适应铜环境的变化；e、 例如，脉冲噪声、外来串扰或微中断可暂时降低聚合组中的一个或多个bce，导致聚合g键链路的速率降低。然后，丢弃的BCE将尝试重新初始化，可能以比以前更低的速率，调整速率以提供所需的目标SNR裕度。
Generation of this notification is controlled by the gBondPortConfLowRateCrossingEnable object.
此通知的生成由gBondPortConfLowRateCrossingEnable对象控制。
This object maps to the TR-159 notification
nGroupLowDownRateCrossing."
REFERENCE
"[TR-159], Section 5.5.1.25"
::= { gBondPortNotifications 2}
This object maps to the TR-159 notification
nGroupLowDownRateCrossing."
REFERENCE
"[TR-159], Section 5.5.1.25"
::= { gBondPortNotifications 2}
gBondPmTca15MinESCrossing NOTIFICATION-TYPE
OBJECTS {
-- ifIndex is not needed here, since we are under specific GBS
gBondPortPmCur15MinES,
gBondPortPmTcaProfileThresh15MinES
}
STATUS current
DESCRIPTION
"This notification indicates that the Errored Seconds threshold,
specified by gBondPortPmTcaProfileThresh15MinES, has been
reached or exceeded for the GBS port.
gBondPmTca15MinESCrossing NOTIFICATION-TYPE
OBJECTS {
-- ifIndex is not needed here, since we are under specific GBS
gBondPortPmCur15MinES,
gBondPortPmTcaProfileThresh15MinES
}
STATUS current
DESCRIPTION
"This notification indicates that the Errored Seconds threshold,
specified by gBondPortPmTcaProfileThresh15MinES, has been
reached or exceeded for the GBS port.
Generation of this notification is controlled by the gBondPortConfPmTcaEnable and gBondPortPmTcaProfileThresh15MinES objects.
此通知的生成由gBondPortConfPmTcaEnable和GBondPortPmtCaProfileThreshMines对象控制。
This object maps to the TR-159 notification
nGroupPerfTca15MinES."
REFERENCE
"[TR-159], Section 5.5.1.42"
::= { gBondPortNotifications 3}
This object maps to the TR-159 notification
nGroupPerfTca15MinES."
REFERENCE
"[TR-159], Section 5.5.1.42"
::= { gBondPortNotifications 3}
gBondPmTca15MinSESCrossing NOTIFICATION-TYPE
OBJECTS {
-- ifIndex is not needed here, since we are under specific GBS
gBondPortPmCur15MinSES,
gBondPortPmTcaProfileThresh15MinSES
}
STATUS current
gBondPmTca15MinSESCrossing NOTIFICATION-TYPE
OBJECTS {
-- ifIndex is not needed here, since we are under specific GBS
gBondPortPmCur15MinSES,
gBondPortPmTcaProfileThresh15MinSES
}
STATUS current
DESCRIPTION "This notification indicates that the Severely Errored Seconds threshold, specified by gBondPortPmTcaProfileThresh15MinSES, has been reached or exceeded for the GBS port.
DESCRIPTION“此通知表示GBS端口已达到或超过gBondPortPmTcaProfileThresh15MinSES指定的严重错误秒数阈值。
Generation of this notification is controlled by the gBondPortConfPmTcaEnable and gBondPortPmTcaProfileThresh15MinSES objects.
此通知的生成由gBondPortConfPmTcaEnable和GBondPortPmtCaProfile对象控制。
This object maps to the TR-159 notification
nGroupPerfTca15MinSES."
REFERENCE
"[TR-159], Section 5.5.1.43"
::= { gBondPortNotifications 4}
This object maps to the TR-159 notification
nGroupPerfTca15MinSES."
REFERENCE
"[TR-159], Section 5.5.1.43"
::= { gBondPortNotifications 4}
gBondPmTca15MinUASCrossing NOTIFICATION-TYPE
OBJECTS {
-- ifIndex is not needed here, since we are under specific GBS
gBondPortPmCur15MinUAS,
gBondPortPmTcaProfileThresh15MinUAS
}
STATUS current
DESCRIPTION
"This notification indicates that the Unavailable Seconds
threshold, specified by gBondPortPmTcaProfileThresh15MinUAS,
has been reached or exceeded for the GBS port.
gBondPmTca15MinUASCrossing NOTIFICATION-TYPE
OBJECTS {
-- ifIndex is not needed here, since we are under specific GBS
gBondPortPmCur15MinUAS,
gBondPortPmTcaProfileThresh15MinUAS
}
STATUS current
DESCRIPTION
"This notification indicates that the Unavailable Seconds
threshold, specified by gBondPortPmTcaProfileThresh15MinUAS,
has been reached or exceeded for the GBS port.
Generation of this notification is controlled by the gBondPortConfPmTcaEnable and gBondPortPmTcaProfileThresh15MinUAS objects.
此通知的生成由gBondPortConfPmTcaEnable和gBondPortPmTcaProfileThresh15MinUAS对象控制。
This object maps to the TR-159 notification
nGroupPerfTca15MinUAS."
REFERENCE
"[TR-159], Section 5.5.1.44"
::= { gBondPortNotifications 5}
This object maps to the TR-159 notification
nGroupPerfTca15MinUAS."
REFERENCE
"[TR-159], Section 5.5.1.44"
::= { gBondPortNotifications 5}
gBondPmTca1DayESCrossing NOTIFICATION-TYPE
OBJECTS {
-- ifIndex is not needed here, since we are under specific GBS
gBondPortPmCur1DayES,
gBondPortPmTcaProfileThresh1DayES
}
STATUS current
DESCRIPTION
"This notification indicates that the Errored Seconds threshold,
specified by gBondPortPmTcaProfileThresh1DayES, has been
reached or exceeded for the GBS port.
gBondPmTca1DayESCrossing NOTIFICATION-TYPE
OBJECTS {
-- ifIndex is not needed here, since we are under specific GBS
gBondPortPmCur1DayES,
gBondPortPmTcaProfileThresh1DayES
}
STATUS current
DESCRIPTION
"This notification indicates that the Errored Seconds threshold,
specified by gBondPortPmTcaProfileThresh1DayES, has been
reached or exceeded for the GBS port.
Generation of this notification is controlled by the gBondPortConfPmTcaEnable and gBondPortPmTcaProfileThresh1DayES objects.
此通知的生成由gBondPortConfPmTcaEnable和gBondPortPmTcaProfileThresh1DayES对象控制。
This object maps to the TR-159 notification
nGroupPerfTca1DayES."
REFERENCE
"[TR-159], Section 5.5.1.54"
::= { gBondPortNotifications 6}
This object maps to the TR-159 notification
nGroupPerfTca1DayES."
REFERENCE
"[TR-159], Section 5.5.1.54"
::= { gBondPortNotifications 6}
gBondPmTca1DaySESCrossing NOTIFICATION-TYPE
OBJECTS {
-- ifIndex is not needed here, since we are under specific GBS
gBondPortPmCur1DaySES,
gBondPortPmTcaProfileThresh1DaySES
}
STATUS current
DESCRIPTION
"This notification indicates that the Severely Errored Seconds
threshold, specified by gBondPortPmTcaProfileThresh1DaySES,
has been reached or exceeded for the GBS port.
gBondPmTca1DaySESCrossing NOTIFICATION-TYPE
OBJECTS {
-- ifIndex is not needed here, since we are under specific GBS
gBondPortPmCur1DaySES,
gBondPortPmTcaProfileThresh1DaySES
}
STATUS current
DESCRIPTION
"This notification indicates that the Severely Errored Seconds
threshold, specified by gBondPortPmTcaProfileThresh1DaySES,
has been reached or exceeded for the GBS port.
Generation of this notification is controlled by the gBondPortConfPmTcaEnable and gBondPortPmTcaProfileThresh1DaySES objects.
此通知的生成由gBondPortConfPmTcaEnable和gBondPortPmTcaProfileThresh1DaySES对象控制。
This object maps to the TR-159 notification
nGroupPerfTca1DaySES."
REFERENCE
"[TR-159], Section 5.5.1.55"
::= { gBondPortNotifications 7}
This object maps to the TR-159 notification
nGroupPerfTca1DaySES."
REFERENCE
"[TR-159], Section 5.5.1.55"
::= { gBondPortNotifications 7}
gBondPmTca1DayUASCrossing NOTIFICATION-TYPE
OBJECTS {
-- ifIndex is not needed here, since we are under specific GBS
gBondPortPmCur1DayUAS,
gBondPortPmTcaProfileThresh1DayUAS
}
STATUS current
DESCRIPTION
"This notification indicates that the Unavailable Seconds
threshold, specified by gBondPortPmTcaProfileThresh1DayUAS,
has been reached or exceeded for the GBS port.
gBondPmTca1DayUASCrossing NOTIFICATION-TYPE
OBJECTS {
-- ifIndex is not needed here, since we are under specific GBS
gBondPortPmCur1DayUAS,
gBondPortPmTcaProfileThresh1DayUAS
}
STATUS current
DESCRIPTION
"This notification indicates that the Unavailable Seconds
threshold, specified by gBondPortPmTcaProfileThresh1DayUAS,
has been reached or exceeded for the GBS port.
Generation of this notification is controlled by the gBondPortConfPmTcaEnable and gBondPortPmTcaProfileThresh1DayUAS objects.
此通知的生成由gBondPortConfPmTcaEnable和gBondPortPmTcaProfileThresh1DayUAS对象控制。
This object maps to the TR-159 notification
nGroupPerfTca1DayUAS."
REFERENCE
"[TR-159], Section 5.5.1.56"
::= { gBondPortNotifications 8}
This object maps to the TR-159 notification
nGroupPerfTca1DayUAS."
REFERENCE
"[TR-159], Section 5.5.1.56"
::= { gBondPortNotifications 8}
-- G.Bond Port (GBS) group
--G.邦德端口（GBS）组
gBondPortConfTable OBJECT-TYPE
SYNTAX SEQUENCE OF GBondPortConfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Table for configuration of G.Bond GBS ports. Entries in this
table MUST be maintained in a persistent manner."
::= { gBondPort 1 }
gBondPortConfTable OBJECT-TYPE
SYNTAX SEQUENCE OF GBondPortConfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Table for configuration of G.Bond GBS ports. Entries in this
table MUST be maintained in a persistent manner."
::= { gBondPort 1 }
gBondPortConfEntry OBJECT-TYPE
SYNTAX GBondPortConfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the G.Bond Port Configuration table.
Each entry represents a G.Bond port indexed by the ifIndex.
Note that a G.Bond GBS port runs on top of a single
or multiple BCE port(s), which are also indexed by the ifIndex."
INDEX { ifIndex }
::= { gBondPortConfTable 1 }
gBondPortConfEntry OBJECT-TYPE
SYNTAX GBondPortConfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the G.Bond Port Configuration table.
Each entry represents a G.Bond port indexed by the ifIndex.
Note that a G.Bond GBS port runs on top of a single
or multiple BCE port(s), which are also indexed by the ifIndex."
INDEX { ifIndex }
::= { gBondPortConfTable 1 }
GBondPortConfEntry ::=
SEQUENCE {
gBondPortConfAdminScheme IANAgBondScheme,
gBondPortConfPeerAdminScheme IANAgBondScheme,
gBondPortConfDiscoveryCode PhysAddress,
gBondPortConfTargetUpDataRate Unsigned32,
gBondPortConfTargetDnDataRate Unsigned32,
gBondPortConfThreshLowUpRate Unsigned32,
gBondPortConfThreshLowDnRate Unsigned32,
gBondPortConfLowRateCrossingEnable TruthValue,
gBondPortConfPmTcaConfProfile SnmpAdminString,
gBondPortConfPmTcaEnable TruthValue
}
GBondPortConfEntry ::=
SEQUENCE {
gBondPortConfAdminScheme IANAgBondScheme,
gBondPortConfPeerAdminScheme IANAgBondScheme,
gBondPortConfDiscoveryCode PhysAddress,
gBondPortConfTargetUpDataRate Unsigned32,
gBondPortConfTargetDnDataRate Unsigned32,
gBondPortConfThreshLowUpRate Unsigned32,
gBondPortConfThreshLowDnRate Unsigned32,
gBondPortConfLowRateCrossingEnable TruthValue,
gBondPortConfPmTcaConfProfile SnmpAdminString,
gBondPortConfPmTcaEnable TruthValue
}
gBondPortConfAdminScheme OBJECT-TYPE SYNTAX IANAgBondScheme MAX-ACCESS read-write STATUS current
gBondPortConfAdminScheme对象类型语法IANANGBONDScheme最大访问读写状态当前
DESCRIPTION "A desired bonding scheme for a G.Bond GBS port. The following values instruct the port to use the corresponding bonding scheme if supported: none(0) - instructs the port not to use bonding (only on a single-BCE G.998.2 GBS) g9981(1) - instructs the port to use G.998.1 bonding g9982(2) - instructs the port to use G.998.2 bonding g9983(3) - instructs the port to use G.998.3 bonding
描述“G.Bond GBS端口所需的绑定方案。以下值指示端口使用相应的绑定方案（如果支持）：无（0）-指示端口不使用绑定（仅在单个BCE G.998.2 GBS上）g9981（1）-指示端口使用G.998.1绑定g9982（2）-指示端口使用G.998.2绑定g9983（3） -指示端口使用G.998.3键合
Changing of the gBondPortConfAdminScheme object MUST be performed when the link is administratively 'down', as indicated by the ifAdminStatus object in the IF-MIB. Attempts to change this object MUST be rejected (in the case of SNMP, with the error inconsistentValue), if the link is 'up' or initializing. Attempts to change this object to an unsupported bonding scheme (see gBondPortCapSchemesSupported) SHALL be rejected (in the case of SNMP, with the error wrongValue). Setting this object to the value of 'none' must be rejected for GBS ports with multiple BCEs (with the error inconsistentValue).
如IF-MIB中的ifAdminStatus对象所示，当链接处于管理“关闭”状态时，必须执行gBondPortConfAdminScheme对象的更改。如果链接处于“启动”或正在初始化状态，则必须拒绝更改此对象的尝试（对于SNMP，错误值不一致）。将此对象更改为不受支持的绑定方案的尝试（请参阅gBondPortCapSchemesSupported）将被拒绝（对于SNMP，错误值为error）。对于具有多个BCE的GBS端口，必须拒绝将此对象设置为值“none”（错误为“值不一致”）。
This object maps to the TR-159 attribute aGroupAdminBondScheme."
REFERENCE
"[TR-159], Section 5.5.1.6; RFC 2863, IF-MIB, ifAdminStatus"
::= { gBondPortConfEntry 1 }
This object maps to the TR-159 attribute aGroupAdminBondScheme."
REFERENCE
"[TR-159], Section 5.5.1.6; RFC 2863, IF-MIB, ifAdminStatus"
::= { gBondPortConfEntry 1 }
gBondPortConfPeerAdminScheme OBJECT-TYPE SYNTAX IANAgBondScheme MAX-ACCESS read-write STATUS current DESCRIPTION "A desired bonding scheme for a peer (link partner) G.Bond port (GBS). The following values instruct the peer port to use the corresponding bonding scheme if supported: none(0) - instructs the port not to use bonding (only on a single-BCE G.998.2 GBS) g9981(1) - instructs the port to use G.998.1 bonding g9982(2) - instructs the port to use G.998.2 bonding g9983(3) - instructs the port to use G.998.3 bonding
gBondPortConfPeerAdminScheme对象类型语法IANAgBondScheme MAX-ACCESS读写状态当前描述“对等（链接伙伴）的所需绑定方案G.绑定端口（GBS）。以下值指示对等端口使用相应的绑定方案（如果支持）：无（0）-指示端口不使用绑定（仅在单个BCE G.998.2 GBS上）g9981（1）-指示端口使用G.998.1键合g9982（2）-指示端口使用G.998.2键合g9983（3）-指示端口使用G.998.3键合
Changing of this object MUST be performed when the link is administratively 'down', as indicated by the ifAdminStatus object in the IF-MIB. Attempts to change this object MUST be rejected (in the case of SNMP, with the error inconsistentValue), if the link is 'up' or initializing. Attempts to change this object to an unsupported bonding scheme (see gBondPortCapPeerSchemesSupported) SHALL be
如IF-MIB中的ifAdminStatus对象所示，当链接处于管理“关闭”状态时，必须更改此对象。如果链接处于“启动”或正在初始化状态，则必须拒绝更改此对象的尝试（对于SNMP，错误值不一致）。尝试将此对象更改为不受支持的绑定方案（请参阅gBondPortCapPeerSchemesSupported）时，应停止
rejected (in the case of SNMP, with the error wrongValue). Setting this object to the value of 'none' must be rejected for GBS ports with multiple BCEs (with the error inconsistentValue).
拒绝（对于SNMP，错误值为）。对于具有多个BCE的GBS端口，必须拒绝将此对象设置为值“none”（错误为“值不一致”）。
This object maps to the TR-159 attribute
aGroupPeerAdminBondScheme."
REFERENCE
"[TR-159], Section 5.5.1.7; RFC 2863, IF-MIB, ifAdminStatus"
::= { gBondPortConfEntry 2 }
This object maps to the TR-159 attribute
aGroupPeerAdminBondScheme."
REFERENCE
"[TR-159], Section 5.5.1.7; RFC 2863, IF-MIB, ifAdminStatus"
::= { gBondPortConfEntry 2 }
gBondPortConfDiscoveryCode OBJECT-TYPE SYNTAX PhysAddress (SIZE (6)) MAX-ACCESS read-write STATUS current DESCRIPTION "A discovery code of the G.Bond port (GBS). A unique 6-octet-long code used by the Discovery function. This object MUST be instantiated for the -O subtype GBS before write operations on the gBondBceConfRemoteDiscoveryCode (Set_if_Clear and Clear_if_Same) are performed by BCEs associated with the GBS. 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 a write operation on the gBondBceConfRemoteDiscoveryCode object of a remote BCE of -O subtype, connected to one of the local BCEs associated with the GBS.
gBondPortConfDiscoveryCode对象类型语法physadress（大小（6））MAX-ACCESS读写状态当前描述“G.Bond端口（GBS）的发现代码。发现函数使用的唯一6个八位字节长的代码。在对gBondBceConfRemoteDiscoveryCode执行写入操作之前，必须为-O子类型GBS实例化此对象（设置“如果清除”和“如果清除”相同）由与GBS关联的BCE执行。重置后，-R子类型端口的此对象的初始值为全零。对于-R子类型端口，此对象的值不能直接更改。此值可能会由于对连接的-O子类型的远程BCE的gBondBceConfRemoteDiscoveryCode对象执行写操作而更改到与GBS关联的一个本地BCE。
Discovery MUST be performed when the link is administratively 'down', as indicated by the ifAdminStatus object in the IF-MIB. Attempts to change this object MUST be rejected (in the case of SNMP, with the error inconsistentValue), if the link is 'up' or initializing.
如IF-MIB中的ifAdminStatus对象所示，当链接处于管理“关闭”状态时，必须执行发现。如果链接处于“启动”或正在初始化状态，则必须拒绝更改此对象的尝试（对于SNMP，错误值不一致）。
This object maps to the TR-159 attribute
aGroupDiscoveryCode."
REFERENCE
"[TR-159], Section 5.5.1.20; [802.3], Sections 61.2.2.8.3,
61.2.2.8.4, 45.2.6.6.1, 45.2.6.8, 61A.2;
RFC 2863, IF-MIB, ifAdminStatus"
::= { gBondPortConfEntry 3 }
This object maps to the TR-159 attribute
aGroupDiscoveryCode."
REFERENCE
"[TR-159], Section 5.5.1.20; [802.3], Sections 61.2.2.8.3,
61.2.2.8.4, 45.2.6.6.1, 45.2.6.8, 61A.2;
RFC 2863, IF-MIB, ifAdminStatus"
::= { gBondPortConfEntry 3 }
gBondPortConfTargetUpDataRate OBJECT-TYPE SYNTAX Unsigned32 (0|1..10000000) UNITS "Kbps" MAX-ACCESS read-write STATUS current
GBONDPortConfTargetUpdateRate对象类型语法无符号32（0 | 1..10000000）单位“Kbps”最大访问读写状态当前
DESCRIPTION "A desired G.Bond port data rate in the upstream direction, in Kbps, to be achieved during initialization, under restrictions placed upon the member BCEs by their respective configuration settings. This object represents a sum of individual BCE upstream data rates, modified to compensate for fragmentation and encapsulation overhead (e.g., for an Ethernet service, the target data rate of 10 Mbps SHALL allow lossless transmission of full-duplex 10-Mbps Ethernet frame stream with minimal inter-frame gap). Note that the target upstream data rate may not be achieved during initialization (e.g., due to unavailability of required BCEs) or the initial bandwidth could deteriorate, so that the actual upstream data rate (gBondPortStatUpDataRate) could be less than gBondPortConfTargetUpDataRate.
DESCRIPTION“在初始化期间，在成员BCE各自的配置设置对其施加的限制下，上游方向上所需的G.Bond端口数据速率，以Kbps为单位。此对象表示单个BCE上游数据速率的总和，经过修改以补偿碎片和封装开销（例如，对于以太网服务，10 Mbps的目标数据速率应允许以最小帧间间隙无损传输全双工10 Mbps以太网帧流）。注意，在初始化期间可能无法达到目标上游数据速率（例如，由于所需BCE不可用）或者，初始带宽可能会恶化，因此实际上行数据速率（gBondPortStatUpDataRate）可能小于GBONDPortConfTargetUpdateRate。
The value is limited above by 10 Gbps, to accommodate very high speed bonded xDSL interfaces (e.g., 32 x 100 Mbps).
该值限制在10 Gbps以上，以适应非常高速的绑定xDSL接口（例如，32 x 100 Mbps）。
The value between 1 and 10000000 indicates that the total upstream data rate of the G.Bond port after initialization SHALL be equal to the target data rate or less, if the target upstream data rate cannot be achieved under the restrictions configured for BCEs. In cases where the copper environment allows a higher upstream data rate to be achieved than that specified by this object, the excess capability SHALL be either converted to an additional SNR margin or reclaimed by minimizing transmit power.
如果在为BCEs配置的限制下无法实现目标上游数据速率，则1到10000000之间的值表示初始化后G.Bond端口的总上游数据速率应等于或小于目标数据速率。如果铜缆环境允许实现比本目标规定更高的上行数据速率，则应将多余容量转换为额外的SNR裕度，或通过最小化发射功率回收。
The value of 0 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 a desired SNR margin per BCE.
值0表示目标数据速率不是固定的，应在指定的频谱限制下，在初始化期间（尽最大努力）将其设置为可达到的最大速率，且每BCE具有所需的SNR裕度。
This object is read-write for the -O subtype G.Bond ports. It is irrelevant for the -R subtypes -- attempts to read or change this object for such ports MUST be rejected (in the case of SNMP, with the error inconsistentValue).
此对象对于-O子类型G.Bond端口是读写的。它与-R子类型无关——必须拒绝尝试读取或更改此类端口的此对象（对于SNMP，错误为inconsistentValue）。
Changing of the target upstream data rate MUST be performed when the link is administratively 'down', as indicated by the ifAdminStatus object in the IF-MIB. Attempts to change this object MUST be rejected (in the case of SNMP, with the error inconsistentValue), if the link is 'up' or initializing.
如IF-MIB中的ifAdminStatus对象所示，当链路处于管理“关闭”状态时，必须更改目标上行数据速率。如果链接处于“启动”或正在初始化状态，则必须拒绝更改此对象的尝试（对于SNMP，错误值不一致）。
This object maps to the TR-159 attribute aGroupTargetUpRate."
此对象映射到TR-159属性aGroupTargetUpRate。”
REFERENCE
"[TR-159], Section 5.5.1.17; RFC 2863, IF-MIB, ifAdminStatus"
::= { gBondPortConfEntry 4 }
REFERENCE
"[TR-159], Section 5.5.1.17; RFC 2863, IF-MIB, ifAdminStatus"
::= { gBondPortConfEntry 4 }
gBondPortConfTargetDnDataRate OBJECT-TYPE SYNTAX Unsigned32 (0|1..10000000) UNITS "Kbps" MAX-ACCESS read-write STATUS current DESCRIPTION "A desired G.Bond port data rate in the downstream direction, in Kbps, to be achieved during initialization, under restrictions placed upon the member BCEs by their respective configuration settings. This object represents a sum of individual BCE downstream data rates, modified to compensate for fragmentation and encapsulation overhead (e.g., for an Ethernet service, the target data rate of 10 Mbps SHALL allow lossless transmission of full-duplex 10-Mbps Ethernet frame stream with minimal inter-frame gap). Note that the target downstream data rate may not be achieved during initialization (e.g., due to unavailability of required BCEs) or the initial bandwidth could deteriorate, so that the actual downstream data rate (gBondPortStatDnDataRate) could be less than gBondPortConfTargetDnDataRate.
gBondPortConfTargetDnDataRate对象类型语法无符号32（0 | 1..10000000）单位“Kbps”最大访问读写状态当前说明“在初始化过程中，在成员BCE各自的配置设置所施加的限制下，下游方向上所需的G.Bond端口数据速率，单位为Kbps。该对象表示单个BCE下游数据速率的总和，经过修改以补偿碎片和封装开销（例如，对于以太网服务，10 Mbps的目标数据速率应允许以最小帧间间隙无损传输全双工10 Mbps以太网帧流）。请注意，在初始化期间可能无法达到目标下游数据速率（例如，由于所需BCE不可用），或者初始带宽可能会恶化，因此实际下游数据速率（GBONDPORTSTATDNDARATE）可能小于GBONDPORTCONFTTARGETDNDATARATE。
The value is limited above by 10 Gbps, to accommodate very high speed bonded xDSL interfaces (e.g., 32 x 100 Mbps).
该值限制在10 Gbps以上，以适应非常高速的绑定xDSL接口（例如，32 x 100 Mbps）。
The value between 1 and 10000000 indicates that the total downstream data rate of the G.Bond port after initialization SHALL be equal to the target data rate or less, if the target downstream data rate cannot be achieved under the restrictions configured for BCEs. In cases where the copper environment allows a higher downstream data rate to be achieved than that specified by this object, the excess capability SHALL be either converted to an additional SNR margin or reclaimed by minimizing transmit power.
如果在为BCE配置的限制下无法实现目标下游数据速率，则1到10000000之间的值表示初始化后G.Bond端口的总下游数据速率应等于或小于目标数据速率。如果铜缆环境允许实现比本目标规定的更高的下游数据速率，则应将多余容量转换为额外的SNR裕度，或通过最小化发射功率回收。
The value of 0 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 a desired SNR margin per BCE.
值0表示目标数据速率不是固定的，应在指定的频谱限制下，在初始化期间（尽最大努力）将其设置为可达到的最大速率，且每BCE具有所需的SNR裕度。
This object is read-write for the -O subtype G.Bond ports. It is irrelevant for the -R subtypes -- attempts to read or change this object for such ports MUST be rejected (in the case of SNMP, with the error inconsistentValue).
此对象对于-O子类型G.Bond端口是读写的。它与-R子类型无关——必须拒绝尝试读取或更改此类端口的此对象（对于SNMP，错误为inconsistentValue）。
Changing of the target downstream data rate MUST be performed when the link is administratively 'down', as indicated by the ifAdminStatus object in the IF-MIB. Attempts to change this object MUST be rejected (in the case of SNMP, with the error inconsistentValue), if the link is 'up' or initializing.
如IF-MIB中的ifAdminStatus对象所示，当链路处于管理“关闭”状态时，必须更改目标下游数据速率。如果链接处于“启动”或正在初始化状态，则必须拒绝更改此对象的尝试（对于SNMP，错误值不一致）。
This object maps to the TR-159 attribute aGroupTargetDownRate."
REFERENCE
"[TR-159], Section 5.5.1.18; RFC 2863, IF-MIB, ifAdminStatus"
::= { gBondPortConfEntry 5 }
This object maps to the TR-159 attribute aGroupTargetDownRate."
REFERENCE
"[TR-159], Section 5.5.1.18; RFC 2863, IF-MIB, ifAdminStatus"
::= { gBondPortConfEntry 5 }
gBondPortConfThreshLowUpRate OBJECT-TYPE SYNTAX Unsigned32 (1..10000000) UNITS "Kbps" MAX-ACCESS read-write STATUS current DESCRIPTION "This object configures the G.Bond port low upstream rate crossing alarm threshold. When the current value of gBondPortStatUpDataRate for this port reaches/drops below or exceeds this threshold, a gBondLowUpRateCrossing notification MAY be generated if enabled by gBondPortConfLowRateCrossingEnable.
gBondPortConfThreshLowUpRate对象类型语法无符号32（1..10000000）单位“Kbps”最大访问读写状态当前说明“此对象配置G.Bond端口低上行速率穿越报警阈值。当此端口的gBondPortStatUpDataRate的当前值达到/低于或超过此阈值时，如果由gBondPortConfLowRateCrossingEnable启用，则可能会生成GBondLowUprateCrossingEnable通知。
This object is read-write for the -O subtype G.Bond ports. It is irrelevant for the -R subtypes -- attempts to read or change this object for such ports MUST be rejected (in the case of SNMP, with the error inconsistentValue).
此对象对于-O子类型G.Bond端口是读写的。它与-R子类型无关——必须拒绝尝试读取或更改此类端口的此对象（对于SNMP，错误为inconsistentValue）。
This object maps to the TR-159 attribute
aGroupthreshLowUpRate."
REFERENCE
"[TR-159], Section 5.5.1.21"
::= { gBondPortConfEntry 6 }
This object maps to the TR-159 attribute
aGroupthreshLowUpRate."
REFERENCE
"[TR-159], Section 5.5.1.21"
::= { gBondPortConfEntry 6 }
gBondPortConfThreshLowDnRate OBJECT-TYPE SYNTAX Unsigned32 (1..10000000) UNITS "Kbps" MAX-ACCESS read-write STATUS current DESCRIPTION "This object configures the G.Bond port low downstream rate crossing alarm threshold. When the current value of gBondPortStatDnDataRate for this port reaches/drops below or exceeds this threshold, a gBondLowDnRateCrossing notification MAY be generated if enabled by gBondPortConfLowRateCrossingEnable.
gBondPortConfThreshLowDnRate对象类型语法无符号32（1..10000000）单位“Kbps”最大访问读写状态当前说明“此对象配置G.Bond端口下游低速率穿越报警阈值。当此端口的GBondPortStatdData当前值达到/低于或超过此阈值时，如果gBondPortConfLowRateCrossingEnable启用，则可能会生成gBondLowDnRateCrossing通知。
This object is read-write for the -O subtype G.Bond ports. It is irrelevant for the -R subtypes -- attempts to read or change this object for such ports MUST be rejected (in the case of SNMP, with the error inconsistentValue).
此对象对于-O子类型G.Bond端口是读写的。它与-R子类型无关——必须拒绝尝试读取或更改此类端口的此对象（对于SNMP，错误为inconsistentValue）。
This object maps to the TR-159 attribute
aGroupThreshLowDownRate."
REFERENCE
"[TR-159], Section 5.5.1.22"
::= { gBondPortConfEntry 7 }
This object maps to the TR-159 attribute
aGroupThreshLowDownRate."
REFERENCE
"[TR-159], Section 5.5.1.22"
::= { gBondPortConfEntry 7 }
gBondPortConfLowRateCrossingEnable OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "Indicates whether gBondLowUpRateCrossing and gBondLowDnRateCrossing notifications should be generated for this interface.
gBondPortConfLowRateCrossingEnable对象类型语法TruthValue MAX-ACCESS读写状态当前描述”指示是否应为此接口生成GBondLowUprateCrosing和gBondLowDnRateCrossing通知。
A value of true(1) indicates that the notifications are enabled. A value of false(2) indicates that the notifications are disabled.
值为true（1）表示已启用通知。值false（2）表示已禁用通知。
This object is read-write for the -O subtype G.Bond ports. It is irrelevant for the -R subtypes -- attempts to read or change this object for such ports MUST be rejected (in the case of SNMP, with the error inconsistentValue).
此对象对于-O子类型G.Bond端口是读写的。它与-R子类型无关——必须拒绝尝试读取或更改此类端口的此对象（对于SNMP，错误为inconsistentValue）。
This object maps to the TR-159 attribute
aGroupLowRateCrossingEnable."
REFERENCE
"[TR-159], Section 5.5.1.23"
::= { gBondPortConfEntry 8 }
This object maps to the TR-159 attribute
aGroupLowRateCrossingEnable."
REFERENCE
"[TR-159], Section 5.5.1.23"
::= { gBondPortConfEntry 8 }
gBondPortConfPmTcaConfProfile OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (1..32))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The value of this object is the index of the row in the GBS
Port Alarm Configuration Profile table for Performance Monitoring
Threshold Crossing Alerts -- the gBondPortAlarmConfProfileTable,
which applies to this GBS port."
DEFVAL { "DEFVAL" }
::= { gBondPortConfEntry 9 }
gBondPortConfPmTcaConfProfile OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (1..32))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The value of this object is the index of the row in the GBS
Port Alarm Configuration Profile table for Performance Monitoring
Threshold Crossing Alerts -- the gBondPortAlarmConfProfileTable,
which applies to this GBS port."
DEFVAL { "DEFVAL" }
::= { gBondPortConfEntry 9 }
gBondPortConfPmTcaEnable OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "Indicates whether the gBondPerfTca*Crossing set of notifications should be generated for this interface.
gBondPortConfPmTcaEnable对象类型语法TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION”指示是否应为此接口生成gBondPerfTca*交叉通知集。
A value of true(1) indicates that the notifications are enabled. A value of false(2) indicates that the notifications are disabled.
值为true（1）表示已启用通知。值false（2）表示已禁用通知。
This object maps to the TR-159 attribute aGroupPerfTcaEnable."
REFERENCE
"[TR-159], Section 5.5.1.38"
::= { gBondPortConfEntry 10 }
This object maps to the TR-159 attribute aGroupPerfTcaEnable."
REFERENCE
"[TR-159], Section 5.5.1.38"
::= { gBondPortConfEntry 10 }
gBondPortCapTable OBJECT-TYPE
SYNTAX SEQUENCE OF GBondPortCapEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Table for capabilities of G.Bond ports. Entries in this table
MUST be maintained in a persistent manner."
::= { gBondPort 2 }
gBondPortCapTable OBJECT-TYPE
SYNTAX SEQUENCE OF GBondPortCapEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Table for capabilities of G.Bond ports. Entries in this table
MUST be maintained in a persistent manner."
::= { gBondPort 2 }
gBondPortCapEntry OBJECT-TYPE
SYNTAX GBondPortCapEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the G.Bond Port Capability table.
Each entry represents a G.Bond port indexed by the ifIndex.
Note that a G.Bond GBS port runs on top of a single
or multiple BCE port(s), which are also indexed by the ifIndex."
INDEX { ifIndex }
::= { gBondPortCapTable 1 }
gBondPortCapEntry OBJECT-TYPE
SYNTAX GBondPortCapEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the G.Bond Port Capability table.
Each entry represents a G.Bond port indexed by the ifIndex.
Note that a G.Bond GBS port runs on top of a single
or multiple BCE port(s), which are also indexed by the ifIndex."
INDEX { ifIndex }
::= { gBondPortCapTable 1 }
GBondPortCapEntry ::=
SEQUENCE {
gBondPortCapSchemesSupported IANAgBondSchemeList,
gBondPortCapPeerSchemesSupported IANAgBondSchemeList,
gBondPortCapCapacity Unsigned32,
gBondPortCapPeerCapacity Unsigned32
}
GBondPortCapEntry ::=
SEQUENCE {
gBondPortCapSchemesSupported IANAgBondSchemeList,
gBondPortCapPeerSchemesSupported IANAgBondSchemeList,
gBondPortCapCapacity Unsigned32,
gBondPortCapPeerCapacity Unsigned32
}
gBondPortCapSchemesSupported OBJECT-TYPE SYNTAX IANAgBondSchemeList MAX-ACCESS read-only STATUS current DESCRIPTION "Bonding capability of the G.Bond port (GBS). This is a read-only bitmap of the possible bonding schemes supported by the GBS. The various bit positions are: none(0) - GBS is capable of bonding bypass on a single-BCE G.998.2 GBS g9981(1) - GBS is capable of G.998.1 bonding g9982(2) - GBS is capable of G.998.2 bonding g9983(3) - GBS is capable of G.998.3 bonding
gBondPortCapSchemesSupported OBJECT-TYPE语法IANAgBondSchemeList MAX-ACCESS只读状态当前描述“G.绑定端口（GBS）的绑定能力”。这是GBS支持的可能绑定方案的只读位图。各种位位置为：无（0）-GBS能够在单个BCE上进行键合旁路G.998.2 GBS g9981（1）-GBS能够进行G.998.1键合g9982（2）-GBS能够进行G.998.2键合g9983（3）-GBS能够进行G.998.3键合
Note that for ports supporting multiple bonding schemes, the actual administrative scheme is set via gBondPortConfAdminScheme object. The current operating bonding scheme is reflected in the gBondPortStatOperScheme object.
请注意，对于支持多个绑定方案的端口，实际的管理方案是通过gBondPortConfAdminScheme对象设置的。当前的操作绑定方案反映在gBondPortStatOperScheme对象中。
This object maps to the TR-159 attribute
aGroupBondSchemesSupported."
REFERENCE
"[TR-159], Section 5.5.1.2"
::= { gBondPortCapEntry 1 }
This object maps to the TR-159 attribute
aGroupBondSchemesSupported."
REFERENCE
"[TR-159], Section 5.5.1.2"
::= { gBondPortCapEntry 1 }
gBondPortCapPeerSchemesSupported OBJECT-TYPE SYNTAX IANAgBondSchemeList MAX-ACCESS read-only STATUS current DESCRIPTION "Bonding capability of the peer G.Bond port (GBS). This is a read-only bitmap of the possible bonding schemes supported by the link partner GBS. The various bit positions are: none(0) - peer GBS does not support bonding, or the peer unit could not be reached, or peer GBS is capable of bonding bypass on a single-BCE G.998.2 GBS g9981(1) - peer GBS is capable of G.998.1 bonding g9982(2) - peer GBS is capable of G.998.2 bonding g9983(3) - peer GBS is capable of G.998.3 bonding
gBondPortCapPeerSchemesSupported对象类型语法IANAgBondSchemeList MAX-ACCESS只读状态当前描述“对等G.绑定端口（GBS）的绑定能力”。这是链接伙伴GBS支持的可能绑定方案的只读位图。各种位位置为：无（0）-对等GBS不支持绑定，或无法访问对等单元，或对等GBS能够在单个BCE G.998.2 GBS g9981（1）上进行绑定旁路-对等GBS能够进行G.998.1绑定g9982（2）-对等GBS能够进行G.998.2绑定g9983（3）-对等GBS能够进行G.998.3绑定
Note that for ports supporting multiple bonding schemes, the actual administrative scheme is set via the gBondPortConfPeerAdminScheme object. The current operating bonding scheme is reflected in the gBondPortStatPeerOperScheme object.
请注意，对于支持多个绑定方案的端口，实际的管理方案是通过gBondPortConfPeerAdminScheme对象设置的。当前操作绑定方案反映在GBondPortStatPeerOperatScheme对象中。
This object maps to the TR-159 attribute
aGroupPeerBondSchemesSupported."
REFERENCE
"[TR-159], Section 5.5.1.3"
::= { gBondPortCapEntry 2 }
This object maps to the TR-159 attribute
aGroupPeerBondSchemesSupported."
REFERENCE
"[TR-159], Section 5.5.1.3"
::= { gBondPortCapEntry 2 }
gBondPortCapCapacity OBJECT-TYPE SYNTAX Unsigned32 (1..32) MAX-ACCESS read-only STATUS current DESCRIPTION "Number of BCEs that can be aggregated by the local GBS. The number of BCEs currently assigned to a particular G.Bond port (gBondPortStatNumBCEs) is never greater than gBondPortCapCapacity.
gBondPortCapCapacity对象类型语法Unsigned32（1..32）MAX-ACCESS只读状态当前描述“可由本地GBS聚合的BCE数。当前分配给特定G.Bond端口（gBondPortStatNumBCEs）的BCE数永远不会大于GBONDPortCapacity。
This object maps to the TR-159 attribute aGroupCapacity."
REFERENCE
"[TR-159], Section 5.5.1.12"
::= { gBondPortCapEntry 3 }
This object maps to the TR-159 attribute aGroupCapacity."
REFERENCE
"[TR-159], Section 5.5.1.12"
::= { gBondPortCapEntry 3 }
gBondPortCapPeerCapacity OBJECT-TYPE SYNTAX Unsigned32 (0|1..32) MAX-ACCESS read-only STATUS current DESCRIPTION "Number of BCEs that can be aggregated by the peer GBS port. A value of 0 is returned when peer Bonding capacity is unknown (peer cannot be reached).
gBondPortCapPeerCapacity对象类型语法Unsigned32（0 | 1..32）MAX-ACCESS只读状态当前描述“可由对等GBS端口聚合的BCE数。当对等绑定容量未知（无法达到对等绑定容量）时，返回值0。
This object maps to the TR-159 attribute aGroupPeerCapacity."
REFERENCE
"[TR-159], Section 5.5.1.13"
::= { gBondPortCapEntry 4 }
This object maps to the TR-159 attribute aGroupPeerCapacity."
REFERENCE
"[TR-159], Section 5.5.1.13"
::= { gBondPortCapEntry 4 }
gBondPortStatTable OBJECT-TYPE SYNTAX SEQUENCE OF GBondPortStatEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table provides overall status information of G.Bond ports, complementing the generic status information from the ifTable of the IF-MIB. Additional status information about connected BCEs is available from the relevant line MIBs.
gBondPortStatTable GBondPortStatEntry MAX-ACCESS的对象类型语法序列不可访问状态当前描述“此表提供了G.Bond端口的总体状态信息，补充了IF-MIB ifTable中的通用状态信息。有关已连接BCE的其他状态信息可从相关线路MIB获得。
This table contains live data from the equipment. As such, it is NOT persistent."
此表包含设备的实时数据。因此，它不是持久性的。”
::= { gBondPort 3 }
::= { gBondPort 3 }
gBondPortStatEntry OBJECT-TYPE
SYNTAX GBondPortStatEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the G.Bond Port Status table.
Each entry represents a G.Bond port indexed by the ifIndex.
Note that a G.Bond GBS port runs on top of a single
or multiple BCE port(s), which are also indexed by the ifIndex."
INDEX { ifIndex }
::= { gBondPortStatTable 1 }
gBondPortStatEntry OBJECT-TYPE
SYNTAX GBondPortStatEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the G.Bond Port Status table.
Each entry represents a G.Bond port indexed by the ifIndex.
Note that a G.Bond GBS port runs on top of a single
or multiple BCE port(s), which are also indexed by the ifIndex."
INDEX { ifIndex }
::= { gBondPortStatTable 1 }
GBondPortStatEntry ::=
SEQUENCE {
gBondPortStatOperScheme IANAgBondScheme,
gBondPortStatPeerOperScheme IANAgBondScheme,
gBondPortStatUpDataRate Gauge32,
gBondPortStatDnDataRate Gauge32,
gBondPortStatFltStatus BITS,
gBondPortStatSide INTEGER,
gBondPortStatNumBCEs Unsigned32
}
GBondPortStatEntry ::=
SEQUENCE {
gBondPortStatOperScheme IANAgBondScheme,
gBondPortStatPeerOperScheme IANAgBondScheme,
gBondPortStatUpDataRate Gauge32,
gBondPortStatDnDataRate Gauge32,
gBondPortStatFltStatus BITS,
gBondPortStatSide INTEGER,
gBondPortStatNumBCEs Unsigned32
}
gBondPortStatOperScheme OBJECT-TYPE SYNTAX IANAgBondScheme MAX-ACCESS read-only STATUS current DESCRIPTION "Current operating bonding scheme of a G.Bond port. The possible values are: none(0) - bonding bypass on a single-BCE G.998.2 GBS g9981(1) - G.998.1 bonding g9982(2) - G.998.2 bonding g9983(3) - G.998.3 bonding
gBondPortStatOperScheme对象类型语法IANAGBONDSHEMA MAX-ACCESS只读状态当前描述“G.键合端口的当前操作键合方案。可能的值为：无（0）-单个BCE上的键合旁路G.998.2 GBS g9981（1）-G.998.1键合g9982（2）-G.998.2键合g9983（3）-G.998.3键合
This object maps to the TR-159 attribute
aGroupOperBondScheme."
REFERENCE
"[TR-159], Section 5.5.1.4"
::= { gBondPortStatEntry 1 }
This object maps to the TR-159 attribute
aGroupOperBondScheme."
REFERENCE
"[TR-159], Section 5.5.1.4"
::= { gBondPortStatEntry 1 }
gBondPortStatPeerOperScheme OBJECT-TYPE SYNTAX IANAgBondScheme MAX-ACCESS read-only STATUS current
gBondPortStatPeerOperScheme对象类型语法IANANGBONDScheme MAX-ACCESS只读状态当前
DESCRIPTION "Current operating bonding scheme of a G.Bond port link partner. The possible values are: unknown(0) - peer cannot be reached due to the link state or bonding bypass on a single-BCE G.998.2 GBS g9981(1) - G.998.1 bonding g9982(2) - G.998.2 bonding g9983(3) - G.998.3 bonding
DESCRIPTION“G.Bond端口链路伙伴的当前操作绑定方案。可能的值为：未知（0）-由于单个BCE G.998.2 GBS g9981（1）上的链路状态或绑定旁路而无法达到对等点-G.998.1绑定g9982（2）-G.998.2绑定g9983（3）-G.998.3绑定
This object maps to the TR-159 attribute
aGroupPeerOperBondScheme."
REFERENCE
"[TR-159], Section 5.5.1.5"
::= { gBondPortStatEntry 2 }
This object maps to the TR-159 attribute
aGroupPeerOperBondScheme."
REFERENCE
"[TR-159], Section 5.5.1.5"
::= { gBondPortStatEntry 2 }
gBondPortStatUpDataRate OBJECT-TYPE SYNTAX Gauge32 UNITS "bps" MAX-ACCESS read-only STATUS current DESCRIPTION "A current G.Bond port operational data rate in the upstream direction, in bps. This object represents an estimation of the sum of individual BCE upstream data rates, modified to compensate for fragmentation and encapsulation overhead (e.g., for an Ethernet service, the target data rate of 10 Mbps SHALL allow lossless transmission of full-duplex 10-Mbps Ethernet frame stream with minimal inter-frame gap).
gBondPortStatUpDataRate对象类型语法量表32单元“bps”MAX-ACCESS只读状态当前描述“上游方向的当前G.Bond端口操作数据速率，单位为bps。此对象表示单个BCE上游数据速率总和的估计值，经过修改以补偿碎片和封装开销（例如，对于以太网服务，10 Mbps的目标数据速率应允许以最小帧间间隙无损传输全双工10 Mbps以太网帧流）。
Note that for symmetrical interfaces, gBondPortStatUpDataRate == gBondPortStatDnDataRate == ifSpeed.
请注意，对于对称接口，GBONDPortStatePDataRate==gBondPortStatDnDataRate==ifSpeed。
This object maps to the TR-159 attribute aGroupUpRate."
REFERENCE
"[TR-159], Section 5.5.1.15"
::= { gBondPortStatEntry 3 }
This object maps to the TR-159 attribute aGroupUpRate."
REFERENCE
"[TR-159], Section 5.5.1.15"
::= { gBondPortStatEntry 3 }
gBondPortStatDnDataRate OBJECT-TYPE SYNTAX Gauge32 UNITS "bps" MAX-ACCESS read-only STATUS current DESCRIPTION "A current G.Bond port operational data rate in the downstream direction, in bps. This object represents an estimation of the sum of individual BCE downstream data rates, modified to compensate for
GBONDPORTSTATDNDARATE对象类型语法量表32单元“bps”MAX-ACCESS只读状态当前描述“下游方向的当前G.Bond端口操作数据速率，单位为bps。此对象表示单个BCE下游数据速率之和的估计值，经过修改以补偿
fragmentation and encapsulation overhead (e.g., for an Ethernet service, the target data rate of 10 Mbps SHALL allow lossless transmission of full-duplex 10-Mbps Ethernet frame stream with minimal inter-frame gap).
分段和封装开销（例如，对于以太网服务，10 Mbps的目标数据速率应允许以最小帧间间隙无损传输全双工10 Mbps以太网帧流）。
Note that for symmetrical interfaces, gBondPortStatUpDataRate == gBondPortStatDnDataRate == ifSpeed.
请注意，对于对称接口，GBONDPortStatePDataRate==gBondPortStatDnDataRate==ifSpeed。
This object maps to the TR-159 attribute aGroupDownRate."
REFERENCE
"[TR-159], Section 5.5.1.16"
::= { gBondPortStatEntry 4 }
This object maps to the TR-159 attribute aGroupDownRate."
REFERENCE
"[TR-159], Section 5.5.1.16"
::= { gBondPortStatEntry 4 }
gBondPortStatFltStatus OBJECT-TYPE
SYNTAX BITS {
noPeer(0),
peerPowerLoss(1),
peerBondSchemeMismatch(2),
bceSubTypeMismatch(3),
lowRate(4),
init(5),
ready(6)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"G.Bond (GBS) port fault status. This is a bitmap of possible
conditions. The various bit positions are:
noPeer - Peer GBS cannot be reached (e.g.,
no BCEs attached, all BCEs are
'down', etc.).
peerPowerLoss - Peer GBS has indicated impending unit
failure due to loss of local power
('Dying Gasp').
peerBondSchemeMismatch - Operating bonding scheme of a peer
GBS is different from the local one.
bceSubTypeMismatch - Local BCEs in the aggregation group
are not of the same sub-type, e.g.,
some BCEs in the local device are -O
while others are -R subtype.
lowRate - gBondUpRate/gBondDnRate of the port
has reached or dropped below
gBondPortConfThreshLowUpRate/
gBondPortConfThreshLowDnRate.
gBondPortStatFltStatus OBJECT-TYPE
SYNTAX BITS {
noPeer(0),
peerPowerLoss(1),
peerBondSchemeMismatch(2),
bceSubTypeMismatch(3),
lowRate(4),
init(5),
ready(6)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"G.Bond (GBS) port fault status. This is a bitmap of possible
conditions. The various bit positions are:
noPeer - Peer GBS cannot be reached (e.g.,
no BCEs attached, all BCEs are
'down', etc.).
peerPowerLoss - Peer GBS has indicated impending unit
failure due to loss of local power
('Dying Gasp').
peerBondSchemeMismatch - Operating bonding scheme of a peer
GBS is different from the local one.
bceSubTypeMismatch - Local BCEs in the aggregation group
are not of the same sub-type, e.g.,
some BCEs in the local device are -O
while others are -R subtype.
lowRate - gBondUpRate/gBondDnRate of the port
has reached or dropped below
gBondPortConfThreshLowUpRate/
gBondPortConfThreshLowDnRate.
init - The link is initializing, as a result of ifAdminStatus being set to 'up' for a particular BCE or a GBS to which the BCE is connected. ready - At least one BCE in the aggregation group is detecting handshake tones.
init—由于特定BCE或BCE连接的GBS的ifAdminStatus设置为“up”，链路正在初始化。就绪-聚合组中至少有一个BCE正在检测握手音。
This object is intended to supplement the ifOperStatus object in the IF-MIB.
此对象用于补充IF-MIB中的IFOperaStatus对象。
This object maps to the TR-159 attribute aGroupStatus."
REFERENCE
"[TR-159], Section 5.5.1.9; RFC 2863, IF-MIB, ifOperStatus"
::= { gBondPortStatEntry 5 }
This object maps to the TR-159 attribute aGroupStatus."
REFERENCE
"[TR-159], Section 5.5.1.9; RFC 2863, IF-MIB, ifOperStatus"
::= { gBondPortStatEntry 5 }
gBondPortStatSide OBJECT-TYPE
SYNTAX INTEGER {
subscriber(1),
office(2),
unknown(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"G.Bond port mode of operation (subtype).
The value of 'subscriber' indicates that the port is
designated as '-R' subtype (all BCEs assigned to this port are of
subtype '-R').
The value of 'office' indicates that the port is designated
as '-O' subtype (all BCEs assigned to this port are of
subtype '-O').
The value of 'unknown' indicates that the port has no assigned
BCEs yet or that the assigned BCEs are not of the same side
(subTypeBCEMismatch).
gBondPortStatSide OBJECT-TYPE
SYNTAX INTEGER {
subscriber(1),
office(2),
unknown(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"G.Bond port mode of operation (subtype).
The value of 'subscriber' indicates that the port is
designated as '-R' subtype (all BCEs assigned to this port are of
subtype '-R').
The value of 'office' indicates that the port is designated
as '-O' subtype (all BCEs assigned to this port are of
subtype '-O').
The value of 'unknown' indicates that the port has no assigned
BCEs yet or that the assigned BCEs are not of the same side
(subTypeBCEMismatch).
This object maps to the TR-159 attribute aGroupEnd."
REFERENCE
"[TR-159], Section 5.5.1.11"
::= { gBondPortStatEntry 6 }
This object maps to the TR-159 attribute aGroupEnd."
REFERENCE
"[TR-159], Section 5.5.1.11"
::= { gBondPortStatEntry 6 }
gBondPortStatNumBCEs OBJECT-TYPE SYNTAX Unsigned32 (0..32) MAX-ACCESS read-only STATUS current DESCRIPTION "Number of BCEs that are currently aggregated by the local GBS (assigned to the G.Bond port using the ifStackTable). This number is never greater than gBondPortCapCapacity.
gBondPortStatNumBCEs对象类型语法Unsigned32（0..32）MAX-ACCESS只读状态current DESCRIPTION“当前由本地GBS聚合的BCE数（使用ifStackTable分配给G.Bond端口）。此数永远不会大于GBONDPortCapCapCapCapacity。
This object SHALL be automatically incremented or decremented when a BCE is added or deleted to/from the G.Bond port using the ifStackTable.
当使用ifStackTable向G.Bond端口添加或删除BCE时，该对象应自动递增或递减。
This object maps to the TR-159 attribute aGroupNumChannels."
REFERENCE
"[TR-159], Section 5.5.1.14"
::= { gBondPortStatEntry 7 }
This object maps to the TR-159 attribute aGroupNumChannels."
REFERENCE
"[TR-159], Section 5.5.1.14"
::= { gBondPortStatEntry 7 }
-- Performance Monitoring group
--业绩监测组
gBondPortPM OBJECT IDENTIFIER ::= { gBondPort 4 }
gBondPortPM OBJECT IDENTIFIER ::= { gBondPort 4 }
gBondPortPmCurTable OBJECT-TYPE
SYNTAX SEQUENCE OF GBondPortPmCurEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains current Performance Monitoring (PM)
information for a GBS port. This table contains live data from
the equipment and as such is NOT persistent."
::= { gBondPortPM 1 }
gBondPortPmCurTable OBJECT-TYPE
SYNTAX SEQUENCE OF GBondPortPmCurEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains current Performance Monitoring (PM)
information for a GBS port. This table contains live data from
the equipment and as such is NOT persistent."
::= { gBondPortPM 1 }
gBondPortPmCurEntry OBJECT-TYPE
SYNTAX GBondPortPmCurEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the G.Bond Port PM table.
Each entry represents a G.Bond port indexed by the ifIndex.
Note that a G.Bond GBS port runs on top of a single
or multiple BCE port(s), which are also indexed by the ifIndex."
INDEX { ifIndex }
::= { gBondPortPmCurTable 1 }
gBondPortPmCurEntry OBJECT-TYPE
SYNTAX GBondPortPmCurEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the G.Bond Port PM table.
Each entry represents a G.Bond port indexed by the ifIndex.
Note that a G.Bond GBS port runs on top of a single
or multiple BCE port(s), which are also indexed by the ifIndex."
INDEX { ifIndex }
::= { gBondPortPmCurTable 1 }
GBondPortPmCurEntry ::=
SEQUENCE {
gBondPortPmCurES HCPerfTotalCount,
gBondPortPmCurSES HCPerfTotalCount,
gBondPortPmCurUAS HCPerfTotalCount,
gBondPortPmCur15MinValidIntervals HCPerfValidIntervals,
gBondPortPmCur15MinInvalidIntervals HCPerfInvalidIntervals,
gBondPortPmCur15MinTimeElapsed HCPerfTimeElapsed,
gBondPortPmCur15MinES HCPerfCurrentCount,
gBondPortPmCur15MinSES HCPerfCurrentCount,
gBondPortPmCur15MinUAS HCPerfCurrentCount,
gBondPortPmCur1DayValidIntervals Unsigned32,
GBondPortPmCurEntry ::=
SEQUENCE {
gBondPortPmCurES HCPerfTotalCount,
gBondPortPmCurSES HCPerfTotalCount,
gBondPortPmCurUAS HCPerfTotalCount,
gBondPortPmCur15MinValidIntervals HCPerfValidIntervals,
gBondPortPmCur15MinInvalidIntervals HCPerfInvalidIntervals,
gBondPortPmCur15MinTimeElapsed HCPerfTimeElapsed,
gBondPortPmCur15MinES HCPerfCurrentCount,
gBondPortPmCur15MinSES HCPerfCurrentCount,
gBondPortPmCur15MinUAS HCPerfCurrentCount,
gBondPortPmCur1DayValidIntervals Unsigned32,
gBondPortPmCur1DayInvalidIntervals Unsigned32, gBondPortPmCur1DayTimeElapsed HCPerfTimeElapsed, gBondPortPmCur1DayES HCPerfCurrentCount, gBondPortPmCur1DaySES HCPerfCurrentCount, gBondPortPmCur1DayUAS HCPerfCurrentCount }
gBondPortPmCur1DayInvalidIntervals Unsigned32，GBONDPORTPMCUR1DayTimeAppeased HcPerfTimeAppeased，GBONDPORTPMCUR1Days HCPerfCurrentCount，gBondPortPmCur1DayUAS HCPerfCurrentCount}
gBondPortPmCurES OBJECT-TYPE SYNTAX HCPerfTotalCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "A count of Errored Seconds (ES) on the GBS since the BTU was last restarted.
gBondPortPmCurES对象类型语法HCPerfTotalCount UNITS“seconds”MAX-ACCESS只读状态current DESCRIPTION“自上次重新启动BTU以来GBS上发生错误的秒数。
An Errored Second for a G.998.x interface is defined as a count of 1-second intervals during which one or more GBS errors are declared. The errors are specific for each bonding scheme, e.g., - lost cells for the ATM bonding - lost or discarded (due to an error or a buffer overflow) fragments for the Ethernet bonding - CRC-4, CRC-6, or CRC-8 errors for the TDIM bonding This object is inhibited during Unavailable Seconds (UAS).
G.998.x接口的出错秒定义为声明一个或多个GBS错误的1秒间隔计数。错误针对每个绑定方案是特定的，例如，ATM绑定的丢失信元-以太网绑定的丢失或丢弃（由于错误或缓冲区溢出）片段-TDIM绑定的CRC-4、CRC-6或CRC-8错误此对象在不可用秒（UAS）期间被禁止。
This object maps to the TR-159 attribute aGroupPerfES."
REFERENCE
"[TR-159], Section 5.5.1.29"
::= { gBondPortPmCurEntry 1 }
This object maps to the TR-159 attribute aGroupPerfES."
REFERENCE
"[TR-159], Section 5.5.1.29"
::= { gBondPortPmCurEntry 1 }
gBondPortPmCurSES OBJECT-TYPE SYNTAX HCPerfTotalCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "A count of Severely Errored Seconds (SES) on the GBS since the BTU was last restarted.
gBondPortPmCurSES对象类型语法HCPerfTotalCount UNITS“seconds”MAX-ACCESS只读状态current DESCRIPTION“自上次重新启动BTU以来GBS上严重错误秒数（SES）。
A Severely Errored Second for a G.998.x interface is defined as a count of 1-second intervals during which GBS errors cause at least 1% traffic loss of the nominal bonded link rate or at least 12 ms for the TDM traffic. The exact definition is specific for each bonding scheme, e.g., - 234 lost cells for the ATM bonding with 10-Mbps nominal link rate
G.998.x接口的严重错误秒被定义为1秒间隔计数，在此期间，GBS错误导致标称绑定链路速率至少1%的通信量损失，或TDM通信量至少12 ms。具体定义适用于每种连接方案，例如，对于标称链路速率为10 Mbps的ATM连接，-234个丢失信元
- 60 lost/discarded fragments for the Ethernet bonding with 10-Mbps nominal link rate and fixed 192-byte-long fragment size - 6 or more CRC-4 errors, one or more CRC-6 errors, or one or more CRC-8 errors for the TDM bonding This object is inhibited during Unavailable Seconds (UAS).
-60个丢失/丢弃的片段，用于10 Mbps标称链路速率和固定192字节长的片段大小的以太网绑定-6个或多个CRC-4错误，一个或多个CRC-6错误，或TDM绑定的一个或多个CRC-8错误此对象在不可用秒（UAS）期间被禁止。
This object maps to the TR-159 attribute aGroupPerfSES."
REFERENCE
"[TR-159], Section 5.5.1.30"
::= { gBondPortPmCurEntry 2 }
This object maps to the TR-159 attribute aGroupPerfSES."
REFERENCE
"[TR-159], Section 5.5.1.30"
::= { gBondPortPmCurEntry 2 }
gBondPortPmCurUAS OBJECT-TYPE SYNTAX HCPerfTotalCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "A count of Unavailable Seconds (UAS) on the GBS since the BTU was last restarted.
gBondPortPmCurUAS对象类型语法HCPerfTotalCount UNITS“seconds”MAX-ACCESS只读状态current DESCRIPTION“自上次重新启动BTU以来，GBS上不可用的秒数（UAS）。
An Unavailable Second for a G.998.x interface is defined as a count of 1-second intervals during which the bonded link is unavailable. The G.998.x link becomes unavailable at the onset of 10 contiguous SESs. The 10 SESs are included in the unavailable time. Once unavailable, the G.998.x line becomes available at the onset of 10 contiguous seconds with no SESs. The 10 seconds with no SESs are excluded from the unavailable time.
G.998.x接口的不可用秒定义为保税链路不可用的1秒间隔计数。在10次连续SES开始时，G.998.x链接变得不可用。10个SES包含在不可用时间内。一旦不可用，G.998.x行在连续10秒开始时变为可用，没有SES。无SES的10秒不在不可用时间内。
This object maps to the TR-159 attribute aGroupPerfUAS."
REFERENCE
"[TR-159], Section 5.5.1.31"
::= { gBondPortPmCurEntry 3 }
This object maps to the TR-159 attribute aGroupPerfUAS."
REFERENCE
"[TR-159], Section 5.5.1.31"
::= { gBondPortPmCurEntry 3 }
gBondPortPmCur15MinValidIntervals OBJECT-TYPE SYNTAX HCPerfValidIntervals MAX-ACCESS read-only STATUS current DESCRIPTION "A number of 15-minute intervals for which data was collected. The value of this object will be 96 or the maximum number of 15-minute history intervals collected by the implementation, unless the measurement was (re)started recently, in which case the value will be the number of complete 15-minute intervals for which there are at least some data.
gBondPortPmCur15MinValidIntervals对象类型语法HCPerfValidIntervals MAX-ACCESS只读状态当前描述“收集数据的15分钟间隔数。此对象的值将为96或实现收集的15分钟历史间隔的最大值，除非测量值为（re）最近开始，在这种情况下，该值将是至少有一些数据的完整15分钟间隔数。
In certain cases, it is possible that some intervals are unavailable. In this case, this object reports the maximum interval number for which data is available.
在某些情况下，某些间隔可能不可用。在这种情况下，此对象报告数据可用的最大间隔数。
This object maps to the TR-159 attribute
aGroupPerf15MinValidIntervals."
REFERENCE
"[TR-159], Section 5.5.1.32"
::= { gBondPortPmCurEntry 4 }
This object maps to the TR-159 attribute
aGroupPerf15MinValidIntervals."
REFERENCE
"[TR-159], Section 5.5.1.32"
::= { gBondPortPmCurEntry 4 }
gBondPortPmCur15MinInvalidIntervals OBJECT-TYPE SYNTAX HCPerfInvalidIntervals MAX-ACCESS read-only STATUS current DESCRIPTION "A number of 15-minute intervals for which data was not always available. The value will typically be zero, except in cases where the data for some intervals are not available.
gBondPortPmCur15MinInvalidIntervals对象类型语法HCPERFIVALIDIntervals MAX-ACCESS只读状态当前描述“数据不总是可用的15分钟间隔数。该值通常为零，除非某些间隔的数据不可用。
This object maps to the TR-159 attribute
aGroupPerf15MinInvalidIntervals."
REFERENCE
"[TR-159], Section 5.5.1.33"
::= { gBondPortPmCurEntry 5 }
This object maps to the TR-159 attribute
aGroupPerf15MinInvalidIntervals."
REFERENCE
"[TR-159], Section 5.5.1.33"
::= { gBondPortPmCurEntry 5 }
gBondPortPmCur15MinTimeElapsed OBJECT-TYPE SYNTAX HCPerfTimeElapsed UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "A count of seconds that have elapsed since the beginning of the current 15-minute performance interval.
GBONDPortPMCUR15MintimeeLassed对象类型语法HCPERFTIMEASED UNITS“秒”MAX-ACCESS只读状态当前描述“自当前15分钟性能间隔开始以来已过的秒数。
This object maps to the TR-159 attribute
aGroupPerfCurr15MinTimeElapsed."
REFERENCE
"[TR-159], Section 5.5.1.34"
::= { gBondPortPmCurEntry 6 }
This object maps to the TR-159 attribute
aGroupPerfCurr15MinTimeElapsed."
REFERENCE
"[TR-159], Section 5.5.1.34"
::= { gBondPortPmCurEntry 6 }
gBondPortPmCur15MinES OBJECT-TYPE SYNTAX HCPerfCurrentCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "A count of Errored Seconds (ES) on the GBS in the current 15-minute performance interval.
gBondPortPmCur15MinES对象类型语法HCPerfCurrentCount UNITS“seconds”MAX-ACCESS只读状态current DESCRIPTION“当前15分钟性能间隔内GBS上出错的秒数。
This object maps to the TR-159 attribute aGroupPerfCurr15MinES."
REFERENCE
"[TR-159], Section 5.5.1.35"
::= { gBondPortPmCurEntry 7 }
This object maps to the TR-159 attribute aGroupPerfCurr15MinES."
REFERENCE
"[TR-159], Section 5.5.1.35"
::= { gBondPortPmCurEntry 7 }
gBondPortPmCur15MinSES OBJECT-TYPE SYNTAX HCPerfCurrentCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "A count of Severely Errored Seconds (SES) on the GBS in the current 15-minute performance interval.
gBondPortPmCur15MinSES对象类型语法HCPerfCurrentCount UNITS“seconds”MAX-ACCESS只读状态current DESCRIPTION“当前15分钟性能间隔内GBS上严重错误秒数（SE）。
This object maps to the TR-159 attribute aGroupPerfCurr15MinSES."
REFERENCE
"[TR-159], Section 5.5.1.36"
::= { gBondPortPmCurEntry 8 }
This object maps to the TR-159 attribute aGroupPerfCurr15MinSES."
REFERENCE
"[TR-159], Section 5.5.1.36"
::= { gBondPortPmCurEntry 8 }
gBondPortPmCur15MinUAS OBJECT-TYPE SYNTAX HCPerfCurrentCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "A count of Unavailable Seconds (UAS) on the GBS in the current 15-minute performance interval.
GBONDPortPMCUR15minas对象类型语法HCPerfCurrentCount UNITS“seconds”MAX-ACCESS只读状态current DESCRIPTION“当前15分钟性能间隔内GBS上的不可用秒数（UAS）。
This object maps to the TR-159 attribute aGroupPerfCurr15MinUAS."
REFERENCE
"[TR-159], Section 5.5.1.37"
::= { gBondPortPmCurEntry 9 }
This object maps to the TR-159 attribute aGroupPerfCurr15MinUAS."
REFERENCE
"[TR-159], Section 5.5.1.37"
::= { gBondPortPmCurEntry 9 }
gBondPortPmCur1DayValidIntervals OBJECT-TYPE SYNTAX Unsigned32 (0..7) UNITS "days" MAX-ACCESS read-only STATUS current DESCRIPTION "A number of 1-day intervals for which data was collected. The value of this object will be 7 or the maximum number of 1-day history intervals collected by the implementation, unless the measurement was (re)started recently, in which case the value will be the number of complete 1-day intervals for which there are at least some data. In certain cases, it is possible that some intervals are unavailable. In this case, this object reports the maximum interval number for which data is available.
gBondPortPmCur1DayValidIntervals对象类型语法Unsigned32（0..7）个单位“天”最大访问只读状态当前描述“收集数据的1天间隔数。此对象的值将为7或实现收集的1天历史间隔的最大数，除非度量为（re）最近开始，在这种情况下，值将是至少有一些数据的完整1天间隔数。在某些情况下，可能有一些间隔不可用。在这种情况下，此对象报告数据可用的最大间隔数。
This object maps to the TR-159 attribute
aGroupPerf1DayValidIntervals."
REFERENCE
"[TR-159], Section 5.5.1.45"
::= { gBondPortPmCurEntry 10 }
This object maps to the TR-159 attribute
aGroupPerf1DayValidIntervals."
REFERENCE
"[TR-159], Section 5.5.1.45"
::= { gBondPortPmCurEntry 10 }
gBondPortPmCur1DayInvalidIntervals OBJECT-TYPE SYNTAX Unsigned32 (0..7) UNITS "days" MAX-ACCESS read-only STATUS current DESCRIPTION "A number of 1-day intervals for which data was not always available. The value will typically be zero, except in cases where the data for some intervals are not available.
gBondPortPmCur1DayInvalidIntervals对象类型语法Unsigned32（0..7）个单位“天”最大访问只读状态当前描述“数据并非始终可用的若干1天间隔。该值通常为零，除非某些间隔的数据不可用。
This object maps to the TR-159 attribute
aGroupPerf1DayInvalidIntervals."
REFERENCE
"[TR-159], Section 5.5.1.46"
::= { gBondPortPmCurEntry 11 }
This object maps to the TR-159 attribute
aGroupPerf1DayInvalidIntervals."
REFERENCE
"[TR-159], Section 5.5.1.46"
::= { gBondPortPmCurEntry 11 }
gBondPortPmCur1DayTimeElapsed OBJECT-TYPE SYNTAX HCPerfTimeElapsed UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "A count of seconds that have elapsed since the beginning of the current 1-day performance interval.
GBONDPORTPMCUR1DAYTIMEASED对象类型语法HCPERFTIMEASED UNITS“秒”MAX-ACCESS只读状态当前描述“自当前1天性能间隔开始以来已过的秒数。
This object maps to the TR-159 attribute
aGroupPerfCurr1DayTimeElapsed."
REFERENCE
"[TR-159], Section 5.5.1.47"
::= { gBondPortPmCurEntry 12 }
This object maps to the TR-159 attribute
aGroupPerfCurr1DayTimeElapsed."
REFERENCE
"[TR-159], Section 5.5.1.47"
::= { gBondPortPmCurEntry 12 }
gBondPortPmCur1DayES OBJECT-TYPE SYNTAX HCPerfCurrentCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "A count of Errored Seconds (ES) on the GBS in the current 1-day performance interval.
gBondPortPmCur1DayES对象类型语法HCPerfCurrentCount UNITS“seconds”MAX-ACCESS只读状态current DESCRIPTION“当前1天性能间隔内GBS上发生错误的秒数。
This object maps to the TR-159 attribute aGroupPerfCurr1DayES."
此对象映射到TR-159属性AgroperFCurr1Dayes。”
REFERENCE
"[TR-159], Section 5.5.1.48"
::= { gBondPortPmCurEntry 13 }
REFERENCE
"[TR-159], Section 5.5.1.48"
::= { gBondPortPmCurEntry 13 }
gBondPortPmCur1DaySES OBJECT-TYPE SYNTAX HCPerfCurrentCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "A count of Severely Errored Seconds (SES) on the GBS in the current 1-day performance interval.
gBondPortPmCur1DaySES对象类型语法HCPerfCurrentCount UNITS“seconds”MAX-ACCESS只读状态current DESCRIPTION“当前1天性能间隔内GBS上严重错误秒数（SE）。
This object maps to the TR-159 attribute aGroupPerfCurr1DaySES."
REFERENCE
"[TR-159], Section 5.5.1.49"
::= { gBondPortPmCurEntry 14 }
This object maps to the TR-159 attribute aGroupPerfCurr1DaySES."
REFERENCE
"[TR-159], Section 5.5.1.49"
::= { gBondPortPmCurEntry 14 }
gBondPortPmCur1DayUAS OBJECT-TYPE SYNTAX HCPerfCurrentCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "A count of Unavailable Seconds (UAS) on the GBS in the current 1-day performance interval.
gBondPortPmCur1DayUAS对象类型语法HCPerfCurrentCount UNITS“seconds”MAX-ACCESS只读状态current DESCRIPTION“当前1天性能间隔内GBS上的不可用秒（UAS）计数。
This object maps to the TR-159 attribute aGroupPerfCurr1DayUAS."
REFERENCE
"[TR-159], Section 5.5.1.50"
::= { gBondPortPmCurEntry 15 }
This object maps to the TR-159 attribute aGroupPerfCurr1DayUAS."
REFERENCE
"[TR-159], Section 5.5.1.50"
::= { gBondPortPmCurEntry 15 }
-- PM history: 15-min buckets
--PM历史记录：15分钟
gBondPortPm15MinTable OBJECT-TYPE
SYNTAX SEQUENCE OF GBondPortPm15MinEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains historical 15-minute buckets of Performance
Monitoring information for a GBS port (a row for each 15-minute
interval, up to 96 intervals).
Entries in this table MUST be maintained in a persistent manner."
::= { gBondPortPM 2 }
gBondPortPm15MinTable OBJECT-TYPE
SYNTAX SEQUENCE OF GBondPortPm15MinEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains historical 15-minute buckets of Performance
Monitoring information for a GBS port (a row for each 15-minute
interval, up to 96 intervals).
Entries in this table MUST be maintained in a persistent manner."
::= { gBondPortPM 2 }
gBondPortPm15MinEntry OBJECT-TYPE SYNTAX GBondPortPm15MinEntry MAX-ACCESS not-accessible
GBONDPortPM15Maintery对象类型语法GBONDPortPM15Maintery MAX-ACCESS不可访问
STATUS current
DESCRIPTION
"An entry in the G.Bond Port historical 15-minute PM table.
Each entry represents Performance Monitoring data for a GBS port,
indexed by the ifIndex, collected during a particular 15-minute
interval, indexed by the gBondPortPm15MinIntervalIndex."
INDEX { ifIndex, gBondPortPm15MinIntervalIndex }
::= { gBondPortPm15MinTable 1 }
STATUS current
DESCRIPTION
"An entry in the G.Bond Port historical 15-minute PM table.
Each entry represents Performance Monitoring data for a GBS port,
indexed by the ifIndex, collected during a particular 15-minute
interval, indexed by the gBondPortPm15MinIntervalIndex."
INDEX { ifIndex, gBondPortPm15MinIntervalIndex }
::= { gBondPortPm15MinTable 1 }
GBondPortPm15MinEntry ::=
SEQUENCE {
gBondPortPm15MinIntervalIndex Unsigned32,
gBondPortPm15MinIntervalMoniTime HCPerfTimeElapsed,
gBondPortPm15MinIntervalES HCPerfIntervalCount,
gBondPortPm15MinIntervalSES HCPerfIntervalCount,
gBondPortPm15MinIntervalUAS HCPerfIntervalCount,
gBondPortPm15MinIntervalValid TruthValue
}
GBondPortPm15MinEntry ::=
SEQUENCE {
gBondPortPm15MinIntervalIndex Unsigned32,
gBondPortPm15MinIntervalMoniTime HCPerfTimeElapsed,
gBondPortPm15MinIntervalES HCPerfIntervalCount,
gBondPortPm15MinIntervalSES HCPerfIntervalCount,
gBondPortPm15MinIntervalUAS HCPerfIntervalCount,
gBondPortPm15MinIntervalValid TruthValue
}
gBondPortPm15MinIntervalIndex OBJECT-TYPE SYNTAX Unsigned32 (1..96) MAX-ACCESS not-accessible STATUS current DESCRIPTION "Performance data interval number. 1 is the most recent previous interval; interval 96 is 24 hours ago. Intervals 2..96 are OPTIONAL.
GBONDPortPM15MiniIntervalIndex对象类型语法Unsigned32（1..96）MAX-ACCESS不可访问状态当前描述“性能数据间隔号。1是最近的上一个间隔；间隔96是24小时前。间隔2..96是可选的。
This object maps to the TR-159 attribute
aGroupPerf15MinIntervalNumber."
REFERENCE
"[TR-159], Section 5.5.1.57"
::= { gBondPortPm15MinEntry 1 }
This object maps to the TR-159 attribute
aGroupPerf15MinIntervalNumber."
REFERENCE
"[TR-159], Section 5.5.1.57"
::= { gBondPortPm15MinEntry 1 }
gBondPortPm15MinIntervalMoniTime OBJECT-TYPE
SYNTAX HCPerfTimeElapsed
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of seconds over which the performance data was actually
monitored. This value will be the same as the interval duration
(900 seconds), except in a situation where performance data
could not be collected for any reason."
::= { gBondPortPm15MinEntry 2 }
gBondPortPm15MinIntervalMoniTime OBJECT-TYPE
SYNTAX HCPerfTimeElapsed
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of seconds over which the performance data was actually
monitored. This value will be the same as the interval duration
(900 seconds), except in a situation where performance data
could not be collected for any reason."
::= { gBondPortPm15MinEntry 2 }
gBondPortPm15MinIntervalES OBJECT-TYPE SYNTAX HCPerfIntervalCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "A count of Errored Seconds (ES) on the GBS in the 15-minute performance history interval.
GBONDPortPM15MiniIntervales对象类型语法HCPerfIntervalCount UNITS“seconds”MAX-ACCESS只读状态current DESCRIPTION“在15分钟的性能历史记录间隔内，GBS上发生错误的秒数。
This object maps to the TR-159 attribute
aGroupPerf15MinIntervalES."
REFERENCE
"[TR-159], Section 5.5.1.59"
::= { gBondPortPm15MinEntry 3 }
This object maps to the TR-159 attribute
aGroupPerf15MinIntervalES."
REFERENCE
"[TR-159], Section 5.5.1.59"
::= { gBondPortPm15MinEntry 3 }
gBondPortPm15MinIntervalSES OBJECT-TYPE SYNTAX HCPerfIntervalCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "A count of Severely Errored Seconds (SES) on the GBS in the 15-minute performance history interval.
GBONDPortPM15MinIntervales对象类型语法HCPerfIntervalCount单位“秒”最大访问只读状态当前描述“15分钟性能历史记录间隔内GBS上严重错误秒数（SE）。
This object maps to the TR-159 attribute
aGroupPerf15MinIntervalSES."
REFERENCE
"[TR-159], Section 5.5.1.60"
::= { gBondPortPm15MinEntry 4 }
This object maps to the TR-159 attribute
aGroupPerf15MinIntervalSES."
REFERENCE
"[TR-159], Section 5.5.1.60"
::= { gBondPortPm15MinEntry 4 }
gBondPortPm15MinIntervalUAS OBJECT-TYPE SYNTAX HCPerfIntervalCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "A count of Unavailable Seconds (UAS) on the GBS in the current 15-minute performance interval.
GBONDPortPM15MiniIntervaluas对象类型语法HCPerfIntervalCount UNITS“秒”最大访问只读状态当前描述“当前15分钟性能间隔内GBS上不可用秒（UAS）的计数。
This object maps to the TR-159 attribute
aGroupPerf15MinIntervalUAS."
REFERENCE
"[TR-159], Section 5.5.1.61"
::= { gBondPortPm15MinEntry 5 }
This object maps to the TR-159 attribute
aGroupPerf15MinIntervalUAS."
REFERENCE
"[TR-159], Section 5.5.1.61"
::= { gBondPortPm15MinEntry 5 }
gBondPortPm15MinIntervalValid OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only
gBondPortPm15MinIntervalValid对象类型语法TruthValue MAX-ACCESS只读
STATUS current DESCRIPTION "A read-only object indicating whether or not this history bucket contains valid data. A valid bucket is reported as true(1) and an invalid bucket as false(2). If this history bucket is invalid, the BTU-C MUST NOT produce notifications based upon the value of the counters in this bucket. Note that an implementation may decide not to store invalid history buckets in its database. In such a case, this object is not required, as only valid history buckets are available while invalid history buckets are simply not in the database.
STATUS current DESCRIPTION“一个只读对象，指示此历史存储桶是否包含有效数据。有效存储桶报告为true（1），无效存储桶报告为false（2）。如果此历史存储桶无效，BTU-C不得基于此存储桶中计数器的值生成通知。请注意，实现可能决定不在其数据库中存储无效的历史存储桶。在这种情况下，不需要此对象，因为只有有效的历史存储桶可用，而无效的历史存储桶不可用mply不在数据库中。
This object maps to the TR-159 attribute
aGroupPerf15MinIntervalValid."
REFERENCE
"[TR-159], Section 5.5.1.58"
::= { gBondPortPm15MinEntry 6 }
This object maps to the TR-159 attribute
aGroupPerf15MinIntervalValid."
REFERENCE
"[TR-159], Section 5.5.1.58"
::= { gBondPortPm15MinEntry 6 }
-- PM history: 1-day buckets
--PM历史记录：1天
gBondPortPm1DayTable OBJECT-TYPE
SYNTAX SEQUENCE OF GBondPortPm1DayEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains historical 1-day buckets of Performance
Monitoring information for a GBS port (a row for each 1-day
interval, up to 7 intervals).
Entries in this table MUST be maintained in a persistent manner."
::= { gBondPortPM 3 }
gBondPortPm1DayTable OBJECT-TYPE
SYNTAX SEQUENCE OF GBondPortPm1DayEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains historical 1-day buckets of Performance
Monitoring information for a GBS port (a row for each 1-day
interval, up to 7 intervals).
Entries in this table MUST be maintained in a persistent manner."
::= { gBondPortPM 3 }
gBondPortPm1DayEntry OBJECT-TYPE
SYNTAX GBondPortPm1DayEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the G.Bond Port historical 1-day PM table.
Each entry represents Performance Monitoring data for a GBS port,
indexed by the ifIndex, collected during a particular 1-day
interval, indexed by the gBondPortPm1DayIntervalIndex."
INDEX { ifIndex, gBondPortPm1DayIntervalIndex }
::= { gBondPortPm1DayTable 1 }
gBondPortPm1DayEntry OBJECT-TYPE
SYNTAX GBondPortPm1DayEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the G.Bond Port historical 1-day PM table.
Each entry represents Performance Monitoring data for a GBS port,
indexed by the ifIndex, collected during a particular 1-day
interval, indexed by the gBondPortPm1DayIntervalIndex."
INDEX { ifIndex, gBondPortPm1DayIntervalIndex }
::= { gBondPortPm1DayTable 1 }
GBondPortPm1DayEntry ::=
SEQUENCE {
gBondPortPm1DayIntervalIndex Unsigned32,
gBondPortPm1DayIntervalMoniTime HCPerfTimeElapsed,
GBondPortPm1DayEntry ::=
SEQUENCE {
gBondPortPm1DayIntervalIndex Unsigned32,
gBondPortPm1DayIntervalMoniTime HCPerfTimeElapsed,
gBondPortPm1DayIntervalES HCPerfIntervalCount, gBondPortPm1DayIntervalSES HCPerfIntervalCount, gBondPortPm1DayIntervalUAS HCPerfIntervalCount, gBondPortPm1DayIntervalValid TruthValue }
gBondPortPm1DayIntervalES HCPerfIntervalCount，gBondPortPm1DayIntervalES HCPerfIntervalCount，gBondPortPm1DayIntervalUAS HCPerfIntervalCount，GBONDPortPM1DayIntervalValidalid TruthValue}
gBondPortPm1DayIntervalIndex OBJECT-TYPE SYNTAX Unsigned32 (1..7) MAX-ACCESS not-accessible STATUS current DESCRIPTION "Performance data interval number. 1 is the most recent previous interval; interval 7 is 7 days ago. Intervals 2..7 are OPTIONAL.
gBondPortPm1DayIntervalIndex对象类型语法Unsigned32（1..7）MAX-ACCESS不可访问状态当前描述“性能数据间隔号。1是最近的上一个间隔；间隔7是7天前。间隔2..7是可选的。
This object maps to the TR-159 attribute
aGroupPerf1DayIntervalNumber."
REFERENCE
"[TR-159], Section 5.5.1.62"
::= { gBondPortPm1DayEntry 1 }
This object maps to the TR-159 attribute
aGroupPerf1DayIntervalNumber."
REFERENCE
"[TR-159], Section 5.5.1.62"
::= { gBondPortPm1DayEntry 1 }
gBondPortPm1DayIntervalMoniTime OBJECT-TYPE SYNTAX HCPerfTimeElapsed UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "A count of seconds over which the performance data was actually monitored. This value will be the same as the interval duration (86400 seconds), except in a situation where performance data could not be collected for any reason.
gBondPortPm1DayIntervalMoniTime对象类型语法HCPERFTIMEASED UNITS“秒”MAX-ACCESS只读状态当前描述“实际监视性能数据的秒数。此值将与间隔持续时间（86400秒）相同，但因任何原因无法收集性能数据的情况除外。
This object maps to the TR-159 attribute
aGroupPerf1DayIntervalMoniSecs."
REFERENCE
"[TR-159], Section 5.5.1.64"
::= { gBondPortPm1DayEntry 2 }
This object maps to the TR-159 attribute
aGroupPerf1DayIntervalMoniSecs."
REFERENCE
"[TR-159], Section 5.5.1.64"
::= { gBondPortPm1DayEntry 2 }
gBondPortPm1DayIntervalES OBJECT-TYPE SYNTAX HCPerfIntervalCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "A count of Errored Seconds (ES) on the GBS in the 1-day performance history interval.
gBondPortPm1DayIntervalES对象类型语法HCPerfIntervalCount UNITS“seconds”MAX-ACCESS只读状态current DESCRIPTION“在1天的性能历史记录间隔内，GBS上发生错误的秒数。
This object maps to the TR-159 attribute
aGroupPerf1DayIntervalES."
REFERENCE
"[TR-159], Section 5.5.1.65"
::= { gBondPortPm1DayEntry 3 }
This object maps to the TR-159 attribute
aGroupPerf1DayIntervalES."
REFERENCE
"[TR-159], Section 5.5.1.65"
::= { gBondPortPm1DayEntry 3 }
gBondPortPm1DayIntervalSES OBJECT-TYPE SYNTAX HCPerfIntervalCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "A count of Severely Errored Seconds (SES) on the GBS in the 1-day performance history interval.
GBONDPortPM1DayIntervales对象类型语法HCPerfIntervalCount单位“秒”最大访问只读状态当前描述“1天性能历史记录间隔内GBS上严重错误秒数（SE）。
This object maps to the TR-159 attribute
aGroupPerf1DayIntervalSES."
REFERENCE
"[TR-159], Section 5.5.1.66"
::= { gBondPortPm1DayEntry 4 }
This object maps to the TR-159 attribute
aGroupPerf1DayIntervalSES."
REFERENCE
"[TR-159], Section 5.5.1.66"
::= { gBondPortPm1DayEntry 4 }
gBondPortPm1DayIntervalUAS OBJECT-TYPE SYNTAX HCPerfIntervalCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "A count of Unavailable Seconds (UAS) on the GBS in the current 1-day performance interval.
gBondPortPm1DayIntervalUAS对象类型语法HCPerfIntervalCount UNITS“秒”最大访问只读状态当前描述“当前1天性能间隔内GBS上不可用秒（UAS）的计数。
This object maps to the TR-159 attribute
aGroupPerf1DayIntervalUAS."
REFERENCE
"[TR-159], Section 5.5.1.67"
::= { gBondPortPm1DayEntry 5 }
This object maps to the TR-159 attribute
aGroupPerf1DayIntervalUAS."
REFERENCE
"[TR-159], Section 5.5.1.67"
::= { gBondPortPm1DayEntry 5 }
gBondPortPm1DayIntervalValid OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "A read-only object indicating whether or not this history bucket contains valid data. A valid bucket is reported as true(1) and an invalid bucket as false(2). If this history bucket is invalid, the BTU-C MUST NOT produce notifications based upon the value of the counters in this bucket.
GBONDPORTPM1DAYINTERVALID对象类型语法TruthValue MAX-ACCESS只读状态当前描述“一个只读对象，指示此历史存储桶是否包含有效数据。有效存储桶报告为true（1），无效存储桶报告为false（2）。如果此历史存储桶无效，BTU-C不得基于此存储桶中计数器的值生成通知。
Note that an implementation may decide not to store invalid history buckets in its database. In such a case, this object is not required, as only valid history buckets are available while invalid history buckets are simply not in the database.
请注意，实现可能决定不在其数据库中存储无效的历史存储桶。在这种情况下，不需要此对象，因为只有有效的历史存储桶可用，而无效的历史存储桶根本不在数据库中。
This object maps to the TR-159 attribute
aGroupPerf1DayIntervalValid."
REFERENCE
"[TR-159], Section 5.5.1.63"
::= { gBondPortPm1DayEntry 6 }
This object maps to the TR-159 attribute
aGroupPerf1DayIntervalValid."
REFERENCE
"[TR-159], Section 5.5.1.63"
::= { gBondPortPm1DayEntry 6 }
-- Performance Monitoring TCA Configuration profile
--性能监视TCA配置文件
gBondPortPmTcaProfileTable OBJECT-TYPE
SYNTAX SEQUENCE OF GBondPortPmTcaProfileEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table supports definitions of Performance Monitoring (PM)
Threshold Crossing Alert (TCA) configuration profiles for GBS
ports.
Entries in this table MUST be maintained in a persistent manner."
::= { gBondPortPM 4 }
gBondPortPmTcaProfileTable OBJECT-TYPE
SYNTAX SEQUENCE OF GBondPortPmTcaProfileEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table supports definitions of Performance Monitoring (PM)
Threshold Crossing Alert (TCA) configuration profiles for GBS
ports.
Entries in this table MUST be maintained in a persistent manner."
::= { gBondPortPM 4 }
gBondPortPmTcaProfileEntry OBJECT-TYPE
SYNTAX GBondPortPmTcaProfileEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the GBS PM TCA Configuration table.
Each entry corresponds to a single TCA configuration profile.
Each profile contains a set of parameters for setting alarm
thresholds for various performance attributes monitored at GBS
ports. Profiles may be created/deleted using the row
creation/deletion mechanism via
gBondPortPmTcaProfileRowStatus. If an active entry is
referenced via gBondPortConfPmTcaConfProfile, the entry MUST
remain active until all references are removed.
A default profile with an index of 'DEFVAL' will always exist,
and its parameters will be set to vendor-specific values
unless otherwise specified in this document."
INDEX { gBondPortPmTcaProfileName }
::= { gBondPortPmTcaProfileTable 1 }
gBondPortPmTcaProfileEntry OBJECT-TYPE
SYNTAX GBondPortPmTcaProfileEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the GBS PM TCA Configuration table.
Each entry corresponds to a single TCA configuration profile.
Each profile contains a set of parameters for setting alarm
thresholds for various performance attributes monitored at GBS
ports. Profiles may be created/deleted using the row
creation/deletion mechanism via
gBondPortPmTcaProfileRowStatus. If an active entry is
referenced via gBondPortConfPmTcaConfProfile, the entry MUST
remain active until all references are removed.
A default profile with an index of 'DEFVAL' will always exist,
and its parameters will be set to vendor-specific values
unless otherwise specified in this document."
INDEX { gBondPortPmTcaProfileName }
::= { gBondPortPmTcaProfileTable 1 }
GBondPortPmTcaProfileEntry ::=
SEQUENCE {
gBondPortPmTcaProfileName SnmpAdminString,
gBondPortPmTcaProfileThresh15MinES HCPerfIntervalThreshold,
gBondPortPmTcaProfileThresh15MinSES HCPerfIntervalThreshold,
gBondPortPmTcaProfileThresh15MinUAS HCPerfIntervalThreshold,
gBondPortPmTcaProfileThresh1DayES GBondPm1DayIntervalThreshold,
gBondPortPmTcaProfileThresh1DaySES GBondPm1DayIntervalThreshold,
gBondPortPmTcaProfileThresh1DayUAS GBondPm1DayIntervalThreshold,
gBondPortPmTcaProfileRowStatus RowStatus
}
GBondPortPmTcaProfileEntry ::=
SEQUENCE {
gBondPortPmTcaProfileName SnmpAdminString,
gBondPortPmTcaProfileThresh15MinES HCPerfIntervalThreshold,
gBondPortPmTcaProfileThresh15MinSES HCPerfIntervalThreshold,
gBondPortPmTcaProfileThresh15MinUAS HCPerfIntervalThreshold,
gBondPortPmTcaProfileThresh1DayES GBondPm1DayIntervalThreshold,
gBondPortPmTcaProfileThresh1DaySES GBondPm1DayIntervalThreshold,
gBondPortPmTcaProfileThresh1DayUAS GBondPm1DayIntervalThreshold,
gBondPortPmTcaProfileRowStatus RowStatus
}
gBondPortPmTcaProfileName OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (1..32))
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object is a unique index (name) associated with this
GBS PM TCA profile."
::= { gBondPortPmTcaProfileEntry 1 }
gBondPortPmTcaProfileName OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (1..32))
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object is a unique index (name) associated with this
GBS PM TCA profile."
::= { gBondPortPmTcaProfileEntry 1 }
gBondPortPmTcaProfileThresh15MinES OBJECT-TYPE SYNTAX HCPerfIntervalThreshold UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "A desired threshold for the number of Errored Seconds (ES) within any given 15-minute performance data collection interval. If the number of ESs in a particular 15-minute collection interval reaches or exceeds this value, a gBondPmTca15MinESCrossing notification MAY be generated if enabled by gBondPortConfPmTcaEnable. At most one notification can be sent per interval. Setting this attribute to zero (default) effectively disables the gBondPmTca15MinESCrossing notification.
gBondPortPmTcaProfileThresh15MinES对象类型语法HCPerfIntervalThreshold单位“秒”MAX-ACCESS read create STATUS current DESCRIPTION“出错秒数的所需阈值”在任何给定的15分钟性能数据采集间隔内。如果特定15分钟采集间隔内的ESs数量达到或超过此值，则如果由GBONDPortConfPMTCaable启用，则可能会生成GBONDPMTCA15minesscrossing通知。每个间隔最多可以发送一个通知。将此属性设置为零（默认）有效地禁用gBondPmTca15MinESCrossing通知。
This object maps to the TR-159 attribute
aGroupPerfThreshold15MinES."
REFERENCE
"[TR-159], Section 5.5.1.39"
::= { gBondPortPmTcaProfileEntry 2 }
This object maps to the TR-159 attribute
aGroupPerfThreshold15MinES."
REFERENCE
"[TR-159], Section 5.5.1.39"
::= { gBondPortPmTcaProfileEntry 2 }
gBondPortPmTcaProfileThresh15MinSES OBJECT-TYPE SYNTAX HCPerfIntervalThreshold UNITS "seconds" MAX-ACCESS read-create STATUS current
gBondPortPmTcaProfileThresh15MinSES对象类型语法HCPerfIntervalThreshold单位“秒”最大访问读取创建状态当前
DESCRIPTION "A desired threshold for the number of Severely Errored Seconds (SES) within any given 15-minute performance data collection interval. If the number of SESs in a particular 15-minute collection interval reaches or exceeds this value, a gBondPmTca15MinSESCrossing notification MAY be generated if enabled by gBondPortConfPmTcaEnable. At most one notification can be sent per interval. Setting this attribute to zero (default) effectively disables the gBondPmTca15MinSESCrossing notification.
描述“严重错误秒数（SES）的期望阈值”在任何给定的15分钟性能数据采集间隔内。如果特定15分钟采集间隔内的SES数量达到或超过此值，则如果GBONDPMCA15mInscrossing通知由GBONDPortConfPMTCEnable启用，则可能会生成GBONDPMCA15mInscrossing通知。每个间隔最多可以发送一个通知。将此属性设置为零（默认）有效禁用GBONDPMTCA15MINSCROSING通知。
This object maps to the TR-159 attribute
aGroupPerfThreshold15MinSES."
REFERENCE
"[TR-159], Section 5.5.1.40"
::= { gBondPortPmTcaProfileEntry 3 }
This object maps to the TR-159 attribute
aGroupPerfThreshold15MinSES."
REFERENCE
"[TR-159], Section 5.5.1.40"
::= { gBondPortPmTcaProfileEntry 3 }
gBondPortPmTcaProfileThresh15MinUAS OBJECT-TYPE SYNTAX HCPerfIntervalThreshold UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "A desired threshold for the number of Unavailable Seconds (UAS) within any given 15-minute performance data collection interval. If the number of UASs in a particular 15-minute collection interval reaches or exceeds this value, a gBondPmTca15MinUASCrossing notification MAY be generated if enabled by gBondPortConfPmTcaEnable. At most one notification can be sent per interval. Setting this attribute to zero (default) effectively disables the gBondPmTca15MinUASCrossing notification.
GBONDPortPMTCAProfileThresh15minas对象类型语法HCPerfIntervalThreshold单位“秒”MAX-ACCESS read create STATUS current DESCRIPTION“不可用秒数（UAS）的所需阈值”在任何给定的15分钟性能数据采集间隔内。如果特定15分钟采集间隔内的UAS数量达到或超过此值，则如果由GBONDPortConfPMTCaable启用，则可能会生成GBONDPMTCA15min交叉通知。每个间隔最多可以发送一个通知。将此属性设置为零（默认）有效地禁用GBONDPMTCA15min交叉通知。
This object maps to the TR-159 attribute
aGroupPerfThreshold15MinUAS."
REFERENCE
"[TR-159], Section 5.5.1.41"
::= { gBondPortPmTcaProfileEntry 4 }
This object maps to the TR-159 attribute
aGroupPerfThreshold15MinUAS."
REFERENCE
"[TR-159], Section 5.5.1.41"
::= { gBondPortPmTcaProfileEntry 4 }
gBondPortPmTcaProfileThresh1DayES OBJECT-TYPE SYNTAX GBondPm1DayIntervalThreshold UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "A desired threshold for the number of Errored Seconds (ES) within any given 1-day performance data collection interval.
GBONDPortPMTCAProfileThresh1Days对象类型语法GBondPm1DayIntervalThreshold单位“秒”MAX-ACCESS read create STATUS current DESCRIPTION“给定1天性能数据采集间隔内出错秒数的所需阈值。
If the number of ESs in a particular 1-day collection interval reaches or exceeds this value, a gBondPmTca1DayESCrossing notification MAY be generated if enabled by gBondPortConfPmTcaEnable. At most one notification can be sent per interval. Setting this attribute to zero (default) effectively disables the gBondPmTca1DayESCrossing notification.
如果特定1天采集间隔内的ESs数量达到或超过此值，则如果由gBondPortConfPmTcaEnable启用，则可能会生成GBONDPMTCA1DaysCrossing通知。每个间隔最多可以发送一个通知。将此属性设置为零（默认）将有效禁用GBONDPMTCA1DAYSCROSING通知。
This object maps to the TR-159 attribute
aGroupPerfThreshold1DayES."
REFERENCE
"[TR-159], Section 5.5.1.51"
::= { gBondPortPmTcaProfileEntry 5 }
This object maps to the TR-159 attribute
aGroupPerfThreshold1DayES."
REFERENCE
"[TR-159], Section 5.5.1.51"
::= { gBondPortPmTcaProfileEntry 5 }
gBondPortPmTcaProfileThresh1DaySES OBJECT-TYPE SYNTAX GBondPm1DayIntervalThreshold UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "A desired threshold for the number of Severely Errored Seconds (SES) within any given 1-day performance data collection interval. If the number of SESs in a particular 1-day collection interval reaches or exceeds this value, a gBondPmTca1DaySESCrossing notification MAY be generated if enabled by gBondPortConfPmTcaEnable. At most one notification can be sent per interval. Setting this attribute to zero (default) effectively disables the gBondPmTca1DaySESCrossing notification.
gBondPortPmTcaProfileThresh1DaySES对象类型语法GBondPm1DayIntervalThreshold单位“秒”MAX-ACCESS read create STATUS current DESCRIPTION“严重错误秒数（SES）的所需阈值”在任何给定的1天性能数据采集间隔内。如果特定1天采集间隔内的SES数量达到或超过此值，则如果GBONDPMCA1DayseScrossing由GBONDPortConfPMTCEnable启用，则可能会生成GBONDPMCA1DayseScrossing通知。每个间隔最多可以发送一个通知。将此属性设置为零（默认值）有效禁用gBondPmTca1DaySESCrossing通知。
This object maps to the TR-159 attribute
aGroupPerfThreshold1DaySES."
REFERENCE
"[TR-159], Section 5.5.1.52"
::= { gBondPortPmTcaProfileEntry 6 }
This object maps to the TR-159 attribute
aGroupPerfThreshold1DaySES."
REFERENCE
"[TR-159], Section 5.5.1.52"
::= { gBondPortPmTcaProfileEntry 6 }
gBondPortPmTcaProfileThresh1DayUAS OBJECT-TYPE SYNTAX GBondPm1DayIntervalThreshold UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "A desired threshold for the number of Unavailable Seconds (UAS) within any given 1-day performance data collection interval. If the number of UASs in a particular 1-day collection interval reaches or exceeds this value, a gBondPmTca1DayUASCrossing notification MAY be generated if enabled by
gBondPortPmTcaProfileThresh1DayUAS对象类型语法GBondPm1DayIntervalThreshold单位“秒”MAX-ACCESS read create STATUS current DESCRIPTION“不可用秒数（UAS）的所需阈值”在任何给定的1天性能数据采集间隔内。如果特定1天采集间隔内的UAS数量达到或超过此值，则如果由启用，则可能会生成gBondPmTca1DayUASCrossing通知
gBondPortConfPmTcaEnable. At most one notification can be sent per interval. Setting this attribute to zero (default) effectively disables the gBondPmTca1DayUASCrossing notification.
gbondportconfpmtcaable。每个间隔最多可以发送一个通知。将此属性设置为零（默认）将有效禁用gBondPmTca1DayUASCrossing通知。
This object maps to the TR-159 attribute
aGroupPerfThreshold1DayUAS."
REFERENCE
"[TR-159], Section 5.5.1.53"
::= { gBondPortPmTcaProfileEntry 7 }
This object maps to the TR-159 attribute
aGroupPerfThreshold1DayUAS."
REFERENCE
"[TR-159], Section 5.5.1.53"
::= { gBondPortPmTcaProfileEntry 7 }
gBondPortPmTcaProfileRowStatus 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 gBondPortPmTcaProfileTable per the semantics of RowStatus.
GBONDPortPMTCAProwStatus对象类型语法RowStatus MAX-ACCESS read create STATUS current DESCRIPTION“此对象根据RowStatus的语义控制gBondPortPmTcaProfileTable中关联项的创建、修改或删除。
If an 'active' entry is referenced via gBondPortConfPmTcaConfProfile instance(s), the entry MUST remain 'active'.
如果通过gBondPortConfPmTcaConfProfile实例引用了“活动”条目，则该条目必须保持“活动”。
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 to 'active'
again."
::= { gBondPortPmTcaProfileEntry 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 to 'active'
again."
::= { gBondPortPmTcaProfileEntry 8 }
-- The BCE group
--BCE集团
gBondBceConfTable OBJECT-TYPE SYNTAX SEQUENCE OF GBondBceConfEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Table for configuration of G.Bond common aspects for the Bonding Channel Entity (BCE) ports (modems/channels).
GBONDBECONFTABLE GBONDBECONFENTRY MAX-ACCESS的对象类型语法序列不可访问状态当前描述“用于键合通道实体（BCE）端口（调制解调器/通道）的G.键合公共特性配置的表”。
Entries in this table MUST be maintained in a persistent
manner."
::= { gBondBce 1 }
Entries in this table MUST be maintained in a persistent
manner."
::= { gBondBce 1 }
gBondBceConfEntry OBJECT-TYPE SYNTAX GBondBceConfEntry MAX-ACCESS not-accessible
gBondBceConfEntry对象类型语法gBondBceConfEntry MAX-ACCESS不可访问
STATUS current
DESCRIPTION
"An entry in the G.Bond BCE Configuration table.
Each entry represents common aspects of a G.Bond BCE port
indexed by the ifIndex. Note that a G.Bond BCE port can be
stacked below a single GBS port, also indexed by the ifIndex,
possibly together with other BCE ports if bonding is enabled."
INDEX { ifIndex }
::= { gBondBceConfTable 1 }
STATUS current
DESCRIPTION
"An entry in the G.Bond BCE Configuration table.
Each entry represents common aspects of a G.Bond BCE port
indexed by the ifIndex. Note that a G.Bond BCE port can be
stacked below a single GBS port, also indexed by the ifIndex,
possibly together with other BCE ports if bonding is enabled."
INDEX { ifIndex }
::= { gBondBceConfTable 1 }
GBondBceConfEntry ::=
SEQUENCE {
gBondBceConfRemoteDiscoveryCode PhysAddress
}
GBondBceConfEntry ::=
SEQUENCE {
gBondBceConfRemoteDiscoveryCode PhysAddress
}
gBondBceConfRemoteDiscoveryCode OBJECT-TYPE SYNTAX PhysAddress (SIZE (0|6)) MAX-ACCESS read-write STATUS current DESCRIPTION "A remote discovery code of the BCE port at the CO. A 6-octet-long discovery code of the peer GBS connected via the BCE. 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 gBondPortConfDiscoveryCode at the peer GBS SHALL be the same as gBondPortConfDiscoveryCode of the local GBS associated with the BCE 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 bonding is not enabled.
gBondBceConfRemoteDiscoveryCode对象类型语法physadress（大小（0 | 6））MAX-ACCESS读写状态当前说明“公司BCE端口的远程发现代码。通过BCE连接的对等GBS的6位字节长的发现代码。读取此对象将导致发现获取操作。如果相同操作，将此对象设置为全零将导致发现清除（对等GBS上的gBondPortConfDiscoveryCode值应与与BCE关联的本地GBS的gBondPortConfDiscoveryCode值相同，以便操作成功）。将非零值写入此对象将导致发现集\u if\u清除操作。未启用绑定时，尝试读取此对象时应返回零长度八位字节字符串。
This object is irrelevant in BCE-R port subtypes (CPE side): in this case, a zero-length octet string SHALL be returned on an attempt to read this object. An attempt to change this object MUST be rejected (in the case of SNMP, with the error inconsistentValue).
此对象在BCE-R端口子类型（CPE端）中不相关：在这种情况下，在尝试读取此对象时应返回零长度八位字节字符串。必须拒绝更改此对象的尝试（对于SNMP，错误值不一致）。
Discovery MUST be performed when the link is 'down'. Attempts to change this object MUST be rejected (in the case of SNMP, with the error inconsistentValue), If the link is 'up' or initializing.
必须在链接“关闭”时执行查找。如果链接处于“启动”或正在初始化状态，则必须拒绝更改此对象的尝试（对于SNMP，错误值不一致）。
This object maps to the TR-159 attribute aLineRemoteDiscoveryCode."
此对象映射到TR-159属性aLineRemoteDiscoveryCode。”
REFERENCE
"[TR-159], Section 5.5.6.7"
::= { gBondBceConfEntry 1 }
REFERENCE
"[TR-159], Section 5.5.6.7"
::= { gBondBceConfEntry 1 }
-- -- Conformance Statements --
----一致性声明--
gBondGroups OBJECT IDENTIFIER ::= { gBondConformance 1 }
gBondGroups OBJECT IDENTIFIER ::= { gBondConformance 1 }
gBondCompliances OBJECT IDENTIFIER ::= { gBondConformance 2 }
gBondCompliances OBJECT IDENTIFIER ::= { gBondConformance 2 }
-- Object Groups
--对象组
gBondBasicGroup OBJECT-GROUP
OBJECTS {
gBondPortStatOperScheme,
gBondPortStatUpDataRate,
gBondPortStatDnDataRate,
gBondPortConfTargetUpDataRate,
gBondPortConfTargetDnDataRate,
gBondPortCapSchemesSupported,
gBondPortCapCapacity,
gBondPortStatNumBCEs,
gBondPortStatSide,
gBondPortStatFltStatus
}
STATUS current
DESCRIPTION
"A collection of objects representing management information
common to all types of G.Bond ports."
::= { gBondGroups 1 }
gBondBasicGroup OBJECT-GROUP
OBJECTS {
gBondPortStatOperScheme,
gBondPortStatUpDataRate,
gBondPortStatDnDataRate,
gBondPortConfTargetUpDataRate,
gBondPortConfTargetDnDataRate,
gBondPortCapSchemesSupported,
gBondPortCapCapacity,
gBondPortStatNumBCEs,
gBondPortStatSide,
gBondPortStatFltStatus
}
STATUS current
DESCRIPTION
"A collection of objects representing management information
common to all types of G.Bond ports."
::= { gBondGroups 1 }
gBondDiscoveryGroup OBJECT-GROUP
OBJECTS {
gBondPortStatPeerOperScheme,
gBondPortCapPeerSchemesSupported,
gBondPortCapPeerCapacity,
gBondPortConfDiscoveryCode,
gBondBceConfRemoteDiscoveryCode
}
STATUS current
DESCRIPTION
"A collection of objects supporting OPTIONAL G.Bond discovery
in G.Bond ports."
::= { gBondGroups 2 }
gBondDiscoveryGroup OBJECT-GROUP
OBJECTS {
gBondPortStatPeerOperScheme,
gBondPortCapPeerSchemesSupported,
gBondPortCapPeerCapacity,
gBondPortConfDiscoveryCode,
gBondBceConfRemoteDiscoveryCode
}
STATUS current
DESCRIPTION
"A collection of objects supporting OPTIONAL G.Bond discovery
in G.Bond ports."
::= { gBondGroups 2 }
gBondMultiSchemeGroup OBJECT-GROUP
OBJECTS {
gBondPortConfAdminScheme,
gBondPortConfPeerAdminScheme
}
STATUS current
DESCRIPTION
"A collection of objects providing OPTIONAL management
information for G.Bond ports supporting multiple bonding
schemes."
::= { gBondGroups 3 }
gBondMultiSchemeGroup OBJECT-GROUP
OBJECTS {
gBondPortConfAdminScheme,
gBondPortConfPeerAdminScheme
}
STATUS current
DESCRIPTION
"A collection of objects providing OPTIONAL management
information for G.Bond ports supporting multiple bonding
schemes."
::= { gBondGroups 3 }
gBondTcaConfGroup OBJECT-GROUP
OBJECTS {
gBondPortConfThreshLowUpRate,
gBondPortConfThreshLowDnRate,
gBondPortConfLowRateCrossingEnable
}
STATUS current
DESCRIPTION
"A collection of objects required for configuration of alarm
thresholds and notifications in G.Bond ports."
::= { gBondGroups 4 }
gBondTcaConfGroup OBJECT-GROUP
OBJECTS {
gBondPortConfThreshLowUpRate,
gBondPortConfThreshLowDnRate,
gBondPortConfLowRateCrossingEnable
}
STATUS current
DESCRIPTION
"A collection of objects required for configuration of alarm
thresholds and notifications in G.Bond ports."
::= { gBondGroups 4 }
gBondTcaNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS {
gBondLowUpRateCrossing,
gBondLowDnRateCrossing
}
STATUS current
DESCRIPTION
"This group supports notifications of significant conditions
(non-PM threshold crossing alerts) associated with G.Bond ports."
::= { gBondGroups 5 }
gBondTcaNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS {
gBondLowUpRateCrossing,
gBondLowDnRateCrossing
}
STATUS current
DESCRIPTION
"This group supports notifications of significant conditions
(non-PM threshold crossing alerts) associated with G.Bond ports."
::= { gBondGroups 5 }
gBondPmCurGroup OBJECT-GROUP OBJECTS { gBondPortPmCurES, gBondPortPmCurSES, gBondPortPmCurUAS, gBondPortPmCur15MinValidIntervals, gBondPortPmCur15MinInvalidIntervals, gBondPortPmCur15MinTimeElapsed, gBondPortPmCur15MinES, gBondPortPmCur15MinSES, gBondPortPmCur15MinUAS, gBondPortPmCur1DayValidIntervals, gBondPortPmCur1DayInvalidIntervals,
gBondPmCurGroup对象组对象{gBondPortPmCurES，gBondPortPmCurUAS，GBONDPORTPMCUR15miniInvalidintervals，GBONDPORTPMCUR15miniInInvalidintervals，gBondPortPmCur15MinES，gBondPortPmCur15MinES，GBONDPORTPMCUR15minus，gBondPortPmCur1DayInvalidIntervals，
gBondPortPmCur1DayTimeElapsed,
gBondPortPmCur1DayES,
gBondPortPmCur1DaySES,
gBondPortPmCur1DayUAS
}
STATUS current
DESCRIPTION
"A collection of objects supporting OPTIONAL current Performance
Monitoring information for G.Bond ports."
::= { gBondGroups 6 }
gBondPortPmCur1DayTimeElapsed,
gBondPortPmCur1DayES,
gBondPortPmCur1DaySES,
gBondPortPmCur1DayUAS
}
STATUS current
DESCRIPTION
"A collection of objects supporting OPTIONAL current Performance
Monitoring information for G.Bond ports."
::= { gBondGroups 6 }
gBondPm15MinGroup OBJECT-GROUP
OBJECTS {
gBondPortPm15MinIntervalMoniTime,
gBondPortPm15MinIntervalES,
gBondPortPm15MinIntervalSES,
gBondPortPm15MinIntervalUAS,
gBondPortPm15MinIntervalValid
}
STATUS current
DESCRIPTION
"A collection of objects supporting OPTIONAL historical
Performance Monitoring information for G.Bond ports, during
previous 15-minute intervals."
::= { gBondGroups 7 }
gBondPm15MinGroup OBJECT-GROUP
OBJECTS {
gBondPortPm15MinIntervalMoniTime,
gBondPortPm15MinIntervalES,
gBondPortPm15MinIntervalSES,
gBondPortPm15MinIntervalUAS,
gBondPortPm15MinIntervalValid
}
STATUS current
DESCRIPTION
"A collection of objects supporting OPTIONAL historical
Performance Monitoring information for G.Bond ports, during
previous 15-minute intervals."
::= { gBondGroups 7 }
gBondPm1DayGroup OBJECT-GROUP
OBJECTS {
gBondPortPm1DayIntervalMoniTime,
gBondPortPm1DayIntervalES,
gBondPortPm1DayIntervalSES,
gBondPortPm1DayIntervalUAS,
gBondPortPm1DayIntervalValid
}
STATUS current
DESCRIPTION
"A collection of objects supporting OPTIONAL historical
Performance Monitoring information for G.Bond ports, during
previous 1-day intervals."
::= { gBondGroups 8 }
gBondPm1DayGroup OBJECT-GROUP
OBJECTS {
gBondPortPm1DayIntervalMoniTime,
gBondPortPm1DayIntervalES,
gBondPortPm1DayIntervalSES,
gBondPortPm1DayIntervalUAS,
gBondPortPm1DayIntervalValid
}
STATUS current
DESCRIPTION
"A collection of objects supporting OPTIONAL historical
Performance Monitoring information for G.Bond ports, during
previous 1-day intervals."
::= { gBondGroups 8 }
gBondPmTcaConfGroup OBJECT-GROUP OBJECTS { gBondPortConfPmTcaConfProfile, gBondPortConfPmTcaEnable, gBondPortPmTcaProfileThresh15MinES, gBondPortPmTcaProfileThresh15MinSES, gBondPortPmTcaProfileThresh15MinUAS,
gBondPmTcaConfGroup对象组对象{GBONDPortConfPMTCAConProfile，GBONDPortConfPMTCEnable，GBONDPortPMTCAProfileThresh15分钟，GBONDPortPMTCAProfileThresh15分钟，GBONDPortPMTCAProfileThresh15分钟，
gBondPortPmTcaProfileThresh1DayES,
gBondPortPmTcaProfileThresh1DaySES,
gBondPortPmTcaProfileThresh1DayUAS,
gBondPortPmTcaProfileRowStatus
}
STATUS current
DESCRIPTION
"A collection of objects required for configuration of
Performance Monitoring Threshold Crossing Alert notifications
in G.Bond ports."
::= { gBondGroups 9 }
gBondPortPmTcaProfileThresh1DayES,
gBondPortPmTcaProfileThresh1DaySES,
gBondPortPmTcaProfileThresh1DayUAS,
gBondPortPmTcaProfileRowStatus
}
STATUS current
DESCRIPTION
"A collection of objects required for configuration of
Performance Monitoring Threshold Crossing Alert notifications
in G.Bond ports."
::= { gBondGroups 9 }
gBondPmTcaNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS {
gBondPmTca15MinESCrossing,
gBondPmTca15MinSESCrossing,
gBondPmTca15MinUASCrossing,
gBondPmTca1DayESCrossing,
gBondPmTca1DaySESCrossing,
gBondPmTca1DayUASCrossing
}
STATUS current
DESCRIPTION
"This group supports notifications of Performance Monitoring
Threshold Crossing Alerts associated with G.Bond ports."
::= { gBondGroups 10 }
gBondPmTcaNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS {
gBondPmTca15MinESCrossing,
gBondPmTca15MinSESCrossing,
gBondPmTca15MinUASCrossing,
gBondPmTca1DayESCrossing,
gBondPmTca1DaySESCrossing,
gBondPmTca1DayUASCrossing
}
STATUS current
DESCRIPTION
"This group supports notifications of Performance Monitoring
Threshold Crossing Alerts associated with G.Bond ports."
::= { gBondGroups 10 }
-- Compliance Statements
--合规声明
gBondCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for G.Bond interfaces. Compliance with the following external compliance statements is REQUIRED:
GBOND合规模块-合规状态当前描述“G.Bond接口合规声明。需要符合以下外部合规声明：
MIB Module Compliance Statement
---------- --------------------
IF-MIB ifCompliance3
MIB Module Compliance Statement
---------- --------------------
IF-MIB ifCompliance3
Compliance with the following external compliance statements is OPTIONAL for implementations supporting bonding with flexible cross-connect between the GBS and BCE ports:
对于支持通过GBS和BCE端口之间的灵活交叉连接进行连接的实施，遵守以下外部符合性声明是可选的：
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 {
gBondBasicGroup,
gBondTcaConfGroup,
gBondTcaNotificationGroup
}
MODULE -- this module
MANDATORY-GROUPS {
gBondBasicGroup,
gBondTcaConfGroup,
gBondTcaNotificationGroup
}
GROUP gBondDiscoveryGroup DESCRIPTION "Support for this group is only required for implementations supporting the G.Bond Discovery function."
GROUP gBondDiscoveryGroup DESCRIPTION“只有支持G.Bond发现功能的实现才需要对该组的支持。”
GROUP gBondMultiSchemeGroup DESCRIPTION "Support for this group is only required for implementations supporting multiple bonding schemes."
GROUP gBondMultiSchemeGroup DESCRIPTION“仅支持多个绑定方案的实现需要对该组的支持。”
GROUP gBondPmCurGroup DESCRIPTION "Support for this group is only required for implementations supporting Performance Monitoring."
GROUP gBondPmCurGroup DESCRIPTION“只有支持性能监视的实现才需要对此组的支持。”
GROUP gBondPm15MinGroup DESCRIPTION "Support for this group is only required for implementations supporting 15-minute historical Performance Monitoring."
GROUP gBondPm15MinGroup DESCRIPTION“仅支持15分钟历史性能监控的实现需要对此组的支持。”
GROUP gBondPm1DayGroup DESCRIPTION "Support for this group is only required for implementations supporting 1-day historical Performance Monitoring."
组gBondPm1DayGroup DESCRIPTION“只有支持1天历史性能监控的实施才需要对该组的支持。”
GROUP gBondPmTcaConfGroup DESCRIPTION "Support for this group is only required for implementations supporting Performance Monitoring Threshold Crossing Alert notifications."
组gBondPmTcaConfGroup DESCRIPTION“只有支持性能监视阈值交叉警报通知的实现才需要对此组的支持。”
GROUP gBondPmTcaNotificationGroup DESCRIPTION "Support for this group is only required for implementations supporting Performance Monitoring Threshold Crossing Alert notifications."
组gBondPmTcaNotificationGroup DESCRIPTION“只有支持性能监视阈值交叉警报通知的实现才需要对此组的支持。”
OBJECT gBondPortCapSchemesSupported SYNTAX IANAgBondSchemeList DESCRIPTION "Support for all bonding scheme types is not required.
对象gBondPortCapSchemesSupported SYNTAX IANAgBondSchemeList DESCRIPTION“不需要支持所有绑定方案类型。
However, at least one value SHALL be supported."
但是，至少应支持一个值。”
OBJECT gBondPortCapPeerSchemesSupported SYNTAX IANAgBondSchemeList DESCRIPTION "Support for all bonding scheme types is not required. However, at least one value SHALL be supported."
对象gBondPortCapPeerSchemesSupported SYNTAX IANAgBondSchemeList DESCRIPTION“不需要支持所有绑定方案类型。但是，至少应支持一个值。”
::= { gBondCompliances 1 }
END
::= { gBondCompliances 1 }
END
The IANA-GBOND-TC-MIB module IMPORTS objects from SNMPv2-SMI [RFC2578] and SNMPv2-TC [RFC2579].
IANA-GBOND-TC-MIB模块从SNMPv2 SMI[RFC2578]和SNMPv2 TC[RFC2579]导入对象。
IANA-GBOND-TC-MIB DEFINITIONS ::= BEGIN
IANA-GBOND-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY,
mib-2
FROM SNMPv2-SMI
TEXTUAL-CONVENTION
FROM SNMPv2-TC
;
------------------------------------------------------------------------
ianaGBondTcMIB MODULE-IDENTITY
LAST-UPDATED "201302200000Z" -- 20 February 2013
ORGANIZATION "IANA"
CONTACT-INFO " Internet Assigned Numbers Authority
IMPORTS
MODULE-IDENTITY,
mib-2
FROM SNMPv2-SMI
TEXTUAL-CONVENTION
FROM SNMPv2-TC
;
------------------------------------------------------------------------
ianaGBondTcMIB MODULE-IDENTITY
LAST-UPDATED "201302200000Z" -- 20 February 2013
ORGANIZATION "IANA"
CONTACT-INFO " Internet Assigned Numbers Authority
Postal: ICANN 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536
邮寄地址：加利福尼亚州洛杉矶市滨水路12025号300室，邮编90094-2536
Tel: +1-310-301-5800
EMail: iana@iana.org"
Tel: +1-310-301-5800
EMail: iana@iana.org"
DESCRIPTION "This MIB module defines IANAgBondScheme and IANAgBondSchemeList TEXTUAL-CONVENTIONs, specifying enumerated values of the gBondPortConfAdminScheme, gBondPortConfPeerAdminScheme, gBondPortStatOperScheme, gBondPortStatPeerOperScheme, gBondPortCapSchemesSupported, and gBondPortCapPeerSchemesSupported objects, respectively, as defined in the GBOND-MIB.
描述“此MIB模块定义IANAgBondScheme和IANAgBondSchemeList文本约定，分别指定gBondPortConfAdminScheme、gBondPortConfPeerAdminScheme、gBondPortStatOperScheme、GBONDPortStatpeerOperatScheme、gBondPortCapSchemesSupported和gBondPortCapPeerSchemesSupported对象的枚举值，如GBOND-MIB中所定义。
It is intended that each new bonding scheme defined by the ITU-T Q4/SG15 working group and approved for publication in a revision of the ITU-T G.998 specification will be added to this MIB module, provided that it is suitable for being managed by the base objects in the GBOND-MIB. An Expert Review, as defined in RFC 5226, is REQUIRED for such additions.
计划将ITU-T Q4/SG15工作组定义并批准在ITU-T G.998规范修订版中发布的每个新的键合方案添加到此MIB模块中，前提是它适合由GBOND-MIB中的基本对象管理。如RFC 5226中所定义，此类增加需要专家审查。
The following references are used throughout this MIB module:
此MIB模块中使用了以下参考：
[G.998.1] refers to: ITU-T Recommendation G.998.1: 'ATM-based multi-pair bonding', January 2005.
[G.998.1]参考：ITU-T建议G.998.1:“基于ATM的多对连接”，2005年1月。
[G.998.2] refers to: ITU-T Recommendation G.998.2: 'Ethernet-based multi-pair bonding', January 2005.
[G.998.2]参考：ITU-T建议G.998.2:“基于以太网的多对连接”，2005年1月。
[G.998.3] refers to: ITU-T Recommendation G.998.3: 'Multi-pair bonding using time-division inverse multiplexing', January 2005.
[G.998.3]参考：ITU-T建议G.998.3:“使用时分反向多路复用的多对键合”，2005年1月。
Naming Conventions: BCE - Bonding Channel Entity GBS - Generic Bonding Sub-layer
命名约定：BCE-绑定通道实体GBS-通用绑定子层
These references should be updated as appropriate when a new bonding scheme is added to this MIB module.
当向该MIB模块添加新的绑定方案时，应酌情更新这些引用。
Copyright (c) 2013 IETF Trust and the persons identified as authors of the code. All rights reserved.
版权所有（c）2013 IETF信托基金和被确定为代码作者的人员。版权所有。
Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info)."
根据IETF信托有关IETF文件的法律规定第4.c节规定的简化BSD许可证中包含的许可条款，允许以源代码和二进制格式重新分发和使用，无论是否修改(http://trustee.ietf.org/license-info)."
REVISION "201302200000Z" -- 20 February 2013 DESCRIPTION "Initial version, published as RFC 6765."
修订版“201302200000Z”-2013年2月20日描述“初始版本，发布为RFC 6765。”
::= { mib-2 215 }
::= { mib-2 215 }
-- Textual Conventions
--文本约定
IANAgBondSchemeList ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual convention defines a bitmap of possible ITU-T
G.998 (G.Bond) bonding schemes. Currently, the following values
are defined for the corresponding bonding schemes:
g9981(1) - G.998.1 (G.Bond/ATM; see the G9981-MIB)
g9982(2) - G.998.2 (G.Bond/Ethernet; see the G9982-MIB)
g9983(3) - G.998.3 (G.Bond/TDIM; see the G9983-MIB)
An additional value of none(0) can be returned as a result
of a GET operation when a value of the object cannot be
determined (for example, a peer GBS cannot be reached), the port
does not support any kind of bonding, or when a single-BCE
G.998.2 GBS supports bonding (frame fragmentation/reassembly)
bypass."
IANAgBondSchemeList ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual convention defines a bitmap of possible ITU-T
G.998 (G.Bond) bonding schemes. Currently, the following values
are defined for the corresponding bonding schemes:
g9981(1) - G.998.1 (G.Bond/ATM; see the G9981-MIB)
g9982(2) - G.998.2 (G.Bond/Ethernet; see the G9982-MIB)
g9983(3) - G.998.3 (G.Bond/TDIM; see the G9983-MIB)
An additional value of none(0) can be returned as a result
of a GET operation when a value of the object cannot be
determined (for example, a peer GBS cannot be reached), the port
does not support any kind of bonding, or when a single-BCE
G.998.2 GBS supports bonding (frame fragmentation/reassembly)
bypass."
SYNTAX BITS {
none(0),
g9981(1),
g9982(2),
g9983(3)
}
SYNTAX BITS {
none(0),
g9981(1),
g9982(2),
g9983(3)
}
IANAgBondScheme ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual convention defines ITU-T G.998 bonding scheme
values. Possible values are:
none(0) - no bonding (e.g., on a single-BCE G.998.2 GBS)
or unknown
g9981(1) - G.998.1 (G.Bond/ATM)
g9982(2) - G.998.2 (G.Bond/Ethernet)
g9983(3) - G.998.3 (G.Bond/TDIM)"
SYNTAX INTEGER {
none(0),
g9981(1),
g9982(2),
g9983(3)
}
IANAgBondScheme ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual convention defines ITU-T G.998 bonding scheme
values. Possible values are:
none(0) - no bonding (e.g., on a single-BCE G.998.2 GBS)
or unknown
g9981(1) - G.998.1 (G.Bond/ATM)
g9982(2) - G.998.2 (G.Bond/Ethernet)
g9983(3) - G.998.3 (G.Bond/TDIM)"
SYNTAX INTEGER {
none(0),
g9981(1),
g9982(2),
g9983(3)
}
END
终止
There are a number of management objects defined in this MIB module with a MAX-ACCESS clause of read-write and/or read-create. Such objects may be considered sensitive or vulnerable in some network environments. The support for SET operations in a non-secure environment without proper protection can have a negative effect on network operations. These are the tables and objects and their sensitivity/vulnerability:
此MIB模块中定义了许多管理对象，其MAX-ACCESS子句为read-write和/或read-create。在某些网络环境中，此类对象可能被视为敏感或易受攻击。在没有适当保护的非安全环境中支持SET操作可能会对网络操作产生负面影响。以下是表和对象及其敏感度/漏洞：
o Changing of the gBondPortConfAdminScheme object may lead to a potential locking of the link, if the peer device does not support the desired bonding scheme.
o 如果对等设备不支持所需的绑定方案，则更改gBondPortConfAdminScheme对象可能会导致链路锁定。
o Changing of the gBondPortConfDiscoveryCode object, before the discovery operation, may lead to a wrongful discovery -- for example, when two CO ports are connected to the same multi-channel RT port, while both CO ports have the same discovery register value.
o 在发现操作之前更改gBondPortConfDiscoveryCode对象可能会导致错误的发现——例如，当两个CO端口连接到同一个多通道RT端口时，而两个CO端口具有相同的发现寄存器值。
o Changing of the target upstream/downstream data rate via gBondPortConfTargetUpDataRate/gBondPortConfTargetDnDataRate may lead to anything from degradation of link quality and data rate to a complete link initialization failure, as the ability of a G.Bond port to support a particular configuration depends on the copper environment.
o 通过GBONDPortConfTargetUpdateRate/gBondPortConfTargetDnDataRate更改目标上游/下游数据速率可能导致从链路质量和数据速率下降到完全链路初始化失败的任何情况，因为G.Bond端口支持特定配置的能力取决于铜缆环境。
o Activation of a specific line/channel may cause a severe degradation of service for another G.Bond port, whose channel(s) may be affected by the cross-talk from the newly activated channel.
o 特定线路/信道的激活可能会导致另一个G.Bond端口的服务严重退化，其信道可能会受到来自新激活信道的串扰的影响。
o Removal of a channel from an operationally 'up' G.Bond port, aggregating several channels, may cause degradation of the port's data rate.
o 从操作上“向上”的G.Bond端口移除一个通道，聚合多个通道，可能会导致端口数据速率降低。
Some of the readable objects in this MIB module (i.e., those with MAX-ACCESS other than not-accessible) may be considered sensitive or vulnerable in some network environments since, collectively, they provide information about the performance of network interfaces and can reveal some aspects of their configuration.
在某些网络环境中，此MIB模块中的一些可读对象（即具有MAX-ACCESS而非不可访问的对象）可能被视为敏感或易受攻击，因为它们共同提供了有关网络接口性能的信息，并且可以揭示其配置的某些方面。
In particular, since a bonded xDSL port can be comprised of multiple Unshielded Twisted Pair (UTP) voice-grade copper, located in the same bundle with other pairs belonging to another operator/customer, it is theoretically possible to eavesdrop on a G.Bond transmission, simply by "listening" to cross-talk from the bonded pairs, especially if the operating parameters of the G.Bond link in question are known.
特别是，由于绑定的xDSL端口可以由多个非屏蔽双绞线（UTP）语音级铜组成，与属于另一运营商/客户的其他线对位于同一束中，因此理论上可以通过简单地“监听”来自绑定线对的串扰来窃听G.Bond传输，特别是在已知G.Bond link的运行参数的情况下。
It is thus important to control even GET and/or NOTIFY access to these objects and possibly to even encrypt the values of these objects when sending them over the network via SNMP. These are the tables and objects and their sensitivity/vulnerability:
因此，在通过SNMP通过网络发送这些对象时，控制甚至获取和/或通知对这些对象的访问，甚至可能加密这些对象的值，这一点非常重要。以下是表和对象及其敏感度/漏洞：
o gBondPortStatTable - objects in this table provide status information for the G.Bond port, which may aid in identification of the pairs belonging to the bonded port and eavesdropping on the traffic over that port.
o gBondPortStatTable—此表中的对象提供G.Bond端口的状态信息，这可能有助于识别属于绑定端口的对，并窃听该端口上的流量。
SNMP versions prior to SNMPv3 did not include adequate security. Even if the network itself is secure (for example by using IPsec), there is no control as to who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in this MIB module.
SNMPv3之前的SNMP版本未包含足够的安全性。即使网络本身是安全的（例如通过使用IPsec），也无法控制安全网络上的谁可以访问和获取/设置（读取/更改/创建/删除）此MIB模块中的对象。
Implementations SHOULD provide the security features described by the SNMPv3 framework (see [RFC3410]), and implementations claiming compliance to the SNMPv3 standard MUST include full support for
实现应提供SNMPv3框架（参见[RFC3410]）所述的安全功能，并且声称符合SNMPv3标准的实现必须包括对
authentication and privacy via the User-based Security Model (USM)
[RFC3414] with the AES cipher algorithm [RFC3826]. Implementations
MAY also provide support for the Transport Security Model (TSM)
[RFC5591] in combination with a secure transport such as SSH
[RFC5592] or TLS/DTLS [RFC6353].
authentication and privacy via the User-based Security Model (USM)
[RFC3414] with the AES cipher algorithm [RFC3826]. Implementations
MAY also provide support for the Transport Security Model (TSM)
[RFC5591] in combination with a secure transport such as SSH
[RFC5592] or TLS/DTLS [RFC6353].
Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic security. It is then a customer/operator responsibility to ensure that the SNMP entity giving access to an instance of this MIB module is properly configured to give access to the objects only to those principals (users) that have legitimate rights to indeed GET or SET (change/create/delete) them.
此外，不建议部署SNMPv3之前的SNMP版本。相反，建议部署SNMPv3并启用加密安全性。然后，客户/运营商应负责确保授予访问此MIB模块实例权限的SNMP实体已正确配置为仅授予那些拥有确实获取或设置（更改/创建/删除）对象的合法权限的主体（用户）访问对象。
Three new values of IANAifType -- g9981(263), g9982(264), and g9983(265) -- have been allocated by IANA <http://www.iana.org/> in the IANAifType-MIB module [IANAifType-MIB].
IANA分配了IANAifType的三个新值——g9981（263）、g9982（264）和g9983（265）<http://www.iana.org/>在IANAifType MIB模块[IANAifType MIB]中。
An object identifier for gBondMIB MODULE-IDENTITY has been allocated by IANA in the MIB-2 transmission sub-tree (211).
IANA在MIB-2传输子树（211）中分配了gBondMIB模块标识的对象标识符。
This document defines the first version of the IANA-maintained IANA-GBOND-TC-MIB module. It is intended that each new G.998 bonding scheme defined by the ITU-T Q4/SG15 working group and approved for publication in a revision of ITU-T G.998.x will be added to the IANA-maintained MIB module, provided that it is suitable for being managed by the base objects in the GBOND-MIB module. An object identifier for ianaGBondTcMIB MODULE-IDENTITY has been allocated by IANA in the MIB-2 transmission sub-tree (215).
本文件定义了IANA维护的IANA-GBOND-TC-MIB模块的第一个版本。计划将ITU-T Q4/SG15工作组定义并批准在ITU-T G.998.x版本中发布的每个新G.998键合方案添加到IANA维护的MIB模块中，前提是它适合由GBOND-MIB模块中的基本对象管理。IANA已在MIB-2传输子树（215）中分配ianaGBondTcMIB模块标识的对象标识符。
For each new bonding scheme added, a short description of the bonding protocol and, wherever possible, a reference to a publicly available specification SHOULD be specified. An Expert Review, as defined in [RFC5226], is REQUIRED for each modification.
对于添加的每个新粘接方案，应指定粘接协议的简短说明，并在可能的情况下，参考公开可用的规范。根据[RFC5226]中的定义，每次修改都需要专家评审。
This document was produced by the [ADSLMIB] working group.
本文件由[ADSLMIB]工作组编制。
Special thanks to Dan Romascanu for his meticulous review of this text.
特别感谢Dan Romascanu对本文的仔细审阅。
[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月。
[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月。
[RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)", STD 62, RFC 3414, December 2002.
[RFC3414]Blumenthal，U.和B.Wijnen，“简单网络管理协议（SNMPv3）版本3的基于用户的安全模型（USM）”，STD 62，RFC 3414，2002年12月。
[RFC3705] Ray, B. and R. Abbi, "High Capacity Textual Conventions for MIB Modules Using Performance History Based on 15 Minute Intervals", RFC 3705, February 2004.
[RFC3705]Ray，B.和R.Abbi，“使用基于15分钟间隔的性能历史记录的MIB模块的高容量文本约定”，RFC 3705，2004年2月。
[RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The Advanced Encryption Standard (AES) Cipher Algorithm in the SNMP User-based Security Model", RFC 3826, June 2004.
[RFC3826]Blumenthal，U.，Maino，F.，和K.McCloghrie，“基于SNMP用户的安全模型中的高级加密标准（AES）密码算法”，RFC 3826，2004年6月。
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 2008.
[RFC5226]Narten，T.和H.Alvestrand，“在RFCs中编写IANA注意事项部分的指南”，BCP 26，RFC 5226，2008年5月。
[RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model for the Simple Network Management Protocol (SNMP)", RFC 5591, June 2009.
[RFC5591]Harrington，D.和W.Hardaker，“简单网络管理协议（SNMP）的传输安全模型”，RFC 55912009年6月。
[RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure Shell Transport Model for the Simple Network Management Protocol (SNMP)", RFC 5592, June 2009.
[RFC5592]Harrington，D.，Salowey，J.，和W.Hardaker，“简单网络管理协议（SNMP）的安全外壳传输模型”，RFC 55922009年6月。
[RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport Model for the Simple Network Management Protocol (SNMP)", RFC 6353, July 2011.
[RFC6353]Hardaker，W.“简单网络管理协议（SNMP）的传输层安全（TLS）传输模型”，RFC 63532011年7月。
[TR-159] Beili, E. and M. Morgenstern, "Management Framework for xDSL Bonding", Broadband Forum Technical Report TR-159, December 2008, <http://www.broadband-forum.org/technical/ download/TR-159.pdf>.
[TR-159]Beili，E.和M.Morgenstern，“xDSL连接的管理框架”，宽带论坛技术报告TR-159，2008年12月<http://www.broadband-forum.org/technical/ 下载/TR-159.pdf>。
[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月。
[ADSLMIB] IETF, "ADSL MIB (adslmib) Charter", <http://datatracker.ietf.org/wg/adslmib/charter/>.
[ADSLMIB]IETF，“ADSL MIB（ADSLMIB）章程”<http://datatracker.ietf.org/wg/adslmib/charter/>.
[AF-PHY-0086] ATM Forum, "Inverse Multiplexing for ATM (IMA) Specification Version 1.1", ATM Forum specification af-phy-0086.001, March 1999, <http://www.broadband-forum.org/ ftp/pub/approved-specs/af-phy-0086.001.pdf>.
[AF-PHY-0086]ATM论坛，“ATM（IMA）规范1.1版的反向多路复用”，ATM论坛规范AF-PHY-0086.001，1999年3月<http://www.broadband-forum.org/ ftp/pub/approved specs/af-phy-0086.001.pdf>。
[G.994.1] ITU-T, "Handshake procedures for digital subscriber line (DSL) transceivers", ITU-T Recommendation G.994.1, June 2012, <http://www.itu.int/rec/T-REC-G.994.1/en>.
[G.994.1]ITU-T，“数字用户线（DSL）收发器的握手程序”，ITU-T建议G.994.1，2012年6月<http://www.itu.int/rec/T-REC-G.994.1/en>.
[G.998.1] ITU-T, "ATM-based multi-pair bonding", ITU-T Recommendation G.998.1, January 2005, <http://www.itu.int/rec/T-REC-G.998.1/en>.
[G.998.1]ITU-T，“基于ATM的多对键合”，ITU-T建议G.998.1，2005年1月<http://www.itu.int/rec/T-REC-G.998.1/en>.
[G.998.2] ITU-T, "Ethernet-based multi-pair bonding", ITU-T Recommendation G.998.2, January 2005, <http://www.itu.int/rec/T-REC-G.998.2/en>.
[G.998.2]ITU-T，“基于以太网的多对连接”，ITU-T建议G.998.2，2005年1月<http://www.itu.int/rec/T-REC-G.998.2/en>.
[G.998.3] ITU-T, "Multi-pair bonding using time-division inverse multiplexing", ITU-T Recommendation G.998.3, January 2005, <http://www.itu.int/rec/T-REC-G.998.3/en>.
[G.998.3]ITU-T，“使用时分反向复用的多对键合”，ITU-T建议G.998.3，2005年1月<http://www.itu.int/rec/T-REC-G.998.3/en>.
[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>.
[RFC2790] Waldbusser, S. and P. Grillo, "Host Resources MIB", RFC 2790, March 2000.
[RFC2790]Waldbusser，S.和P.Grillo，“主机资源MIB”，RFC 27902000年3月。
[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月。
[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月。
[RFC3440] Ly, F. and G. Bathrick, "Definitions of Extension Managed Objects for Asymmetric Digital Subscriber Lines", RFC 3440, December 2002.
[RFC3440]Ly，F.和G.Bathrick，“非对称数字用户线路的扩展管理对象的定义”，RFC 3440，2002年12月。
[RFC3593] Tesink, K., "Textual Conventions for MIB Modules Using Performance History Based on 15 Minute Intervals", RFC 3593, September 2003.
[RFC3593]Tesink，K.“使用基于15分钟间隔的性能历史记录的MIB模块的文本约定”，RFC 3593，2003年9月。
[RFC3728] Ray, B. and R. Abbi, "Definitions of Managed Objects for Very High Speed Digital Subscriber Lines (VDSL)", RFC 3728, February 2004.
[RFC3728]Ray，B.和R.Abbi，“超高速数字用户线（VDSL）管理对象的定义”，RFC 3728，2004年2月。
[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月。
[RFC4706] Morgenstern, M., Dodge, M., Baillie, S., and U. Bonollo, "Definitions of Managed Objects for Asymmetric Digital Subscriber Line 2 (ADSL2)", RFC 4706, November 2006.
[RFC4706]Morgenstern，M.，Dodge，M.，Baillie，S.，和U.Bonollo，“非对称数字用户线路2（ADSL2）托管对象的定义”，RFC 4706，2006年11月。
[RFC5066] Beili, E., "Ethernet in the First Mile Copper (EFMCu) Interfaces MIB", RFC 5066, November 2007.
[RFC5066]Beili，E.“第一英里铜缆（EFMCu）接口MIB中的以太网”，RFC 5066，2007年11月。
[RFC5650] Morgenstern, M., Baillie, S., and U. Bonollo, "Definitions of Managed Objects for Very High Speed Digital Subscriber Line 2 (VDSL2)", RFC 5650, September 2009.
[RFC5650]Morgenstern，M.，Baillie，S.，和U.Bonollo，“超高速数字用户线路2（VDSL2）的托管对象定义”，RFC 56502009年9月。
[RFC5905] Mills, D., Martin, J., Burbank, J., and W. Kasch, "Network Time Protocol Version 4: Protocol and Algorithms Specification", RFC 5905, June 2010.
[RFC5905]Mills，D.，Martin，J.，Burbank，J.，和W.Kasch，“网络时间协议版本4：协议和算法规范”，RFC 59052010年6月。
[RFC6766] Beili, E., "xDSL Multi-Pair Bonding Using Time-Division Inverse Multiplexing (G.Bond/TDIM) MIB", RFC 6766, February 2013.
[RFC6766]Beili，E.“使用时分反向复用（G.Bond/TDIM）MIB的xDSL多对键合”，RFC 6766，2013年2月。
[RFC6767] Beili, E. and M. Morgenstern, "Ethernet-Based xDSL Multi-Pair Bonding (G.Bond/Ethernet) MIB", RFC 6767, February 2013.
[RFC6767]Beili，E.和M.Morgenstern，“基于以太网的xDSL多对键合（G.Bond/Ethernet）MIB”，RFC 67672013年2月。
[RFC6768] Beili, E., "ATM-Based xDSL Bonded Interfaces MIB", RFC 6768, February 2013.
[RFC6768]Beili，E.“基于ATM的xDSL绑定接口MIB”，RFC 6768，2013年2月。
Authors' Addresses
作者地址
Edward Beili Actelis Networks 25 Bazel St. Petach-Tikva 49103 Israel
Edward Beili Actelis Networks 25 Bazel St.Petach Tikva以色列49103
Phone: +972-3-924-3491
EMail: edward.beili@actelis.com
Phone: +972-3-924-3491
EMail: edward.beili@actelis.com
Moti Morgenstern ECI Telecom 30 Hasivim St. Petach-Tikva 4951169 Israel
Moti Morgenstern ECI Telecom 30 Hasivim St.Petach Tikva 4951169以色列
Phone: +972-3-926-6258
EMail: moti.morgenstern@ecitele.com
Phone: +972-3-926-6258
EMail: moti.morgenstern@ecitele.com