Ethernet-Based xDSL Multi-Pair Bonding (G.Bond/Ethernet) MIB
Extracted elements (25)
BACP (Bonding Aggregation Control Protocol) is an optional alternative to the mandatory G.hs-based discovery protocol. G.hs cannot be used in-service while the link is 'up', whereas BACP is a frame-based in-service protocol for discovery, aggregation, and pair management, making it suitable for dynamic reconfiguration without taking the link down.
Performance monitoring counters are not reset when a GBS is re-initialized, but only when the agent itself is reset or re-initialized. This preserves historical PM data across link bounces, which is essential for trend analysis and troubleshooting.
The G.Bond/Ethernet management is split across two MIB modules: GBOND-MIB for objects common to all G.Bond technologies (bonding management, port/channel configuration, G.hs discovery, initialization) and G9982-MIB for Ethernet-specific objects. This separation avoids duplicating common bonding objects across technology-specific MIBs.
An IEEE 802.3 2BASE-TL/10PASS-TS interface can be managed by either (a) IF-MIB + IF-CAP-STACK-MIB + EtherLike-MIB + MAU-MIB + EFM-CU-MIB, or (b) IF-MIB + IF-CAP-STACK-MIB + GBOND-MIB + G9982-MIB + HDSL2-SHDSL-LINE-MIB/VDSL-LINE-MIB. The EFM-CU-MIB path lacks historical PM while the GBOND-MIB/G9982-MIB path provides full PM functionality.
While EFM-CU-MIB uses ifMauMediaAvailable from MAU-MIB for bonded xDSL-specific operational states, GBOND-MIB provides these indications via gBondPortStatFltStatus complementing ifOperStatus. Implementations should be aware of this difference when transitioning between management frameworks.
Any modification of g9982BceConfEligibleGroupID MUST be reflected in the ifCapStackTable and its inverse ifInvCapStackTable. Attempts to change this object MUST be rejected if the BCE is already aggregated with other BCEs (more than one BCE connected to the same GBS).
Attempts to change g9982PortConfAdminCp (the bonding control protocol) SHALL be rejected with inconsistentValue if the link is 'up' or initializing. Attempts to set a non-supported protocol (e.g., BACP when g9982PortCapBacpSupported is false) SHALL also be rejected.
Attempts to set g9982PortConfTcAdminType to a non-supported PTM-TC encapsulation type SHALL be rejected with the error inconsistentValue. Changing this object is traffic-disruptive and SHALL be rejected if the link is 'up' or initializing.
BCEs with different g9982BceConfEligibleGroupID values MUST NOT be connected to the same GBS. BCEs with the same EligibleGroupID MAY be connected to different GBS ports.
BCEs with different g9982BceConfPeerEligibleGroupID values MUST NOT be connected to the same GBS. A zero-length octet string SHALL be returned for this object on systems not supporting BACP or when no BACPDUs have been received.
Entries in g9982PortConfTable, g9982PortCapTable, g9982PortPm15MinTable, g9982PortPm1DayTable, and g9982BceConfTable MUST be maintained in a persistent manner across agent restarts.
If a 15-minute or 1-day history bucket is invalid (g9982PortPm15MinIntervalValid or g9982PortPm1DayIntervalValid is false), the BTU MUST NOT produce notifications based upon the value of the counters in that bucket.
The agent SHOULD align the beginning of each 15-minute performance monitoring interval to a fifteen-minute boundary of a wall clock, and each one-day interval SHOULD be aligned with the start of a day.
The G9982-MIB module MUST be used in conjunction with the GBOND-MIB module, which is common to all G.Bond technologies. Both modules are REQUIRED to manage a G.Bond/Ethernet port.
The g9982BceConfEligibleGroupID object MUST be automatically updated whenever the ifCapStackTable/ifInvCapStackTable are changed during BACP initialization.
g9982BceConfTable provides persistent per-BCE BACP configuration: g9982BceConfEligibleGroupID (read-write, 6-octet PhysAddress identifying bonding eligibility group) and g9982BceConfPeerEligibleGroupID (read-only, 6-octet remote group ID received via BACPDU Local info TLV). Returns zero-length string on non-BACP systems.
g9982BceStatTable provides non-persistent per-BCE PTM-TC error counters: g9982BceStatTcInCodingErrors (PTM-TC encapsulation errors) and g9982BceStatTcInCrcErrors (PTM-TC CRC errors), both Counter32 types mapping to TR-159 attributes aChannelPtmTcRxCodingViolations and aChannelPtmTcRxCrcErrors.
G9982CpType is a textual convention enumerating bonding control protocol types: unknown(0), cpHS(1) for G.hs-based discovery and aggregation, and cpBACP(2) for the frame-based Bonding Aggregation Control Protocol specified in G.998.2-Amd2 Annex C.
g9982PortCapTable provides read-only, persistent per-GBS-port capability information: g9982PortCapTcTypesSupported (BITS indicating supported PTM-TC encapsulation types: tc6465 and/or tcHDLC) and g9982PortCapBacpSupported (TruthValue indicating BACP support). Indexed by ifIndex.
g9982PortConfTable provides persistent per-GBS-port configuration: g9982PortConfTcAdminType (desired PTM-TC encapsulation, read-write) and g9982PortConfAdminCp (desired bonding control protocol, read-write, default cpHS). Indexed by ifIndex.
g9982PortStatTable provides non-persistent live status per GBS port: operational TC type (g9982PortStatTcOperType), operational control protocol (g9982PortStatOperCp), and eight Counter32 receive-error counters covering RxErrors, RxSmallFragments (<64 bytes), RxLargeFragments (>512 bytes), RxBadFragments, RxLostFragments, RxLostStarts, RxLostEnds, and RxOverflows.
G9982PtmTcType is a textual convention enumerating PTM-TC encapsulation types: tc6465(1) for 64/65-octet encapsulation per IEEE 802.3 Clause 61.3.3, and tcHDLC(2) for HDLC encapsulation per G.998.2 Annex B.
Performance monitoring tables provide current and historical interval data at two granularities: g9982PortPmCurTable (current 15-min and 1-day intervals), g9982PortPm15MinTable (up to 96 historical 15-minute intervals), and g9982PortPm1DayTable (up to 7 historical 1-day intervals). All PM counters are inhibited during Unavailable Seconds (UAS).
The G9982-MIB module is assigned the OID mib-2 264 (i.e., { mib-2 264 }), registered under the standard MIB-2 subtree. This is the root OID for all objects defined in this module.
The G9982-MIB contains read-write objects (g9982PortConfTcAdminType, g9982PortConfAdminCp) and read-write BACP configuration (g9982BceConfEligibleGroupID) that can disrupt traffic if modified by unauthorized users. SNMPv3 with authentication and privacy MUST be used to protect access to these sensitive objects, as unauthorized modification could cause service disruption on bonded xDSL interfaces.