idnits 2.17.1 draft-ietf-adslmib-gbond-mib-05.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 61 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (November 27, 2010) is 4889 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'G.991.2' is defined on line 2983, but no explicit reference was found in the text == Unused Reference: 'G.993.1' is defined on line 2990, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'TR-159' == Outdated reference: A later version (-06) exists of draft-ietf-adslmib-gbond-atm-mib-02 == Outdated reference: A later version (-08) exists of draft-ietf-adslmib-gbond-eth-mib-02 == Outdated reference: A later version (-08) exists of draft-ietf-adslmib-gbond-tdim-mib-04 Summary: 0 errors (**), 0 flaws (~~), 8 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group E. Beili 3 Internet-Draft Actelis Networks 4 Intended status: Standards Track M. Morgenstern 5 Expires: May 31, 2011 ECI Telecom 6 November 27, 2010 8 xDSL multi-pair bonding (G.Bond) MIB 9 draft-ietf-adslmib-gbond-mib-05.txt 11 Abstract 13 This document defines Management Information Base (MIB) module for 14 use with network management protocols in TCP/IP-based internets. 15 This document proposes an extension to the Interfaces Group MIB with 16 a set of common objects for managing multi-pair bonded Digital 17 Subscriber Line (xDSL) interfaces, defined in ITU-T recommendations 18 G.998.1, G.998.2 and G.998.3. The MIB modules specific to each 19 bonding technology are defined in GBOND-ATM-MIB, GBOND-ETH-MIB and 20 GBOND-TDIM-MIB respectively. 22 Status of This Memo 24 This Internet-Draft is submitted in full conformance with the 25 provisions of BCP 78 and BCP 79. 27 Internet-Drafts are working documents of the Internet Engineering 28 Task Force (IETF). Note that other groups may also distribute 29 working documents as Internet-Drafts. The list of current Internet- 30 Drafts is at http://datatracker.ietf.org/drafts/current/. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet-Drafts as reference 35 material or to cite them other than as "work in progress." 37 This Internet-Draft will expire on May 31, 2011. 39 Copyright Notice 41 Copyright (c) 2010 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents 46 (http://trustee.ietf.org/license-info) in effect on the date of 47 publication of this document. Please review these documents 48 carefully, as they describe your rights and restrictions with respect 49 to this document. Code Components extracted from this document must 50 include Simplified BSD License text as described in Section 4.e of 51 the Trust Legal Provisions and are provided without warranty as 52 described in the Simplified BSD License. 54 Table of Contents 56 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 57 2. The Internet-Standard Management Framework . . . . . . . . . . 4 58 3. The DSL Forum Management Framework for xDSL Bonding . . . . . 4 59 4. Relationship to Other MIB modules . . . . . . . . . . . . . . 4 60 4.1. Relationship to Interfaces Group MIB module . . . . . . . 5 61 4.1.1. Layering Model . . . . . . . . . . . . . . . . . . . . 5 62 4.1.2. xDSL Bonding . . . . . . . . . . . . . . . . . . . . . 7 63 4.1.3. Discovery Operation . . . . . . . . . . . . . . . . . 7 64 4.1.4. G.Bond ports initialization . . . . . . . . . . . . . 9 65 4.1.5. Usage of ifTable . . . . . . . . . . . . . . . . . . . 10 66 4.2. Relationship to G.Bond ATM, ETH and TDIM MIB modules . . . 11 67 4.3. Relationship to xDSL MIB modules . . . . . . . . . . . . . 11 68 5. MIB Structure . . . . . . . . . . . . . . . . . . . . . . . . 12 69 5.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . 12 70 5.2. Performance Monitoring . . . . . . . . . . . . . . . . . . 12 71 5.3. Mapping of DSL Forum TR-159 Managed Objects . . . . . . . 12 72 6. xDSL Multi-pair Bonding MIB Definitions . . . . . . . . . . . 17 73 7. Security Considerations . . . . . . . . . . . . . . . . . . . 60 74 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 62 75 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 62 76 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 62 77 10.1. Normative References . . . . . . . . . . . . . . . . . . . 62 78 10.2. Informative References . . . . . . . . . . . . . . . . . . 63 80 1. Introduction 82 The xDSL Multi-Pair Bonding, allows a service provider to provide 83 high bandwidth services to business and residential customers over 84 multiple xDSL lines, with greater speed and resiliency, than the 85 service over a single xDSL line, bridging the gap between xDSL and 86 fiber-based transport. 88 There are three xDSL Multi-Pair Bonding schemes, also known under 89 collective name G.Bond: 91 o The ATM-Based Multi-Pair Bonding, specified in ITU-T G.998.1 92 recommendation [G.998.1], which defines a method for bonding (or 93 aggregating) of multiple xDSL lines (or individual bearer channels 94 in multiple xDSL lines) into a single bi-directional logical link 95 carrying an ATM stream. This specification can be viewed as an 96 evolution of the legacy Inverse Multiplexing over ATM (IMA) 97 technology [af-phy-0086], applied to xDSL with variable rates on 98 each line/bearer channel. 100 o The Ethernet-Based Multi-Pair Bonding, specified in ITU-T G.998.2 101 recommendation [G.998.2], which defines a method for bonding (or 102 aggregating) of multiple xDSL lines (or individual bearer channels 103 in multiple xDSL lines) into a single bi-directional logical link 104 carrying an Ethernet stream. This specification can be viewed as 105 IEEE 802.3-2005 [802.3] Clause 61 Physical Medium Entity (PME) 106 Aggregation, generalized to work over any xDSL technology. 107 (2Base-TL and 10Pass-TS interfaces defined by IEEE use G.SHDSL and 108 VDSL technology respectively). 110 o The Multi-pair bonding using time-division inverse multiplexing 111 (TDIM), specified in ITU-T G.998.3 recommendation [G.998.3], which 112 defines a method for bonding (or aggregating) of multiple xDSL 113 lines into a single bi-directional logical link carrying a mix of 114 various traffic streams (e.g., Ethernet, ATM, TDM). 116 Architecturally all three bonding schemes define a new "bonded" 117 Transport Protocol Specific - Transmission Convergence (TPS-TC) sub- 118 layer, stacked above multiple ATM-TC, Ethernet/PTM-TC or STM-TC 119 (clear channel) sub-layers for the ATM, Ethernet or TDIM bonding 120 respectively. Each underlying TPS-TC sub-layer represents a protocol 121 specific gamma-interface to an xDSL line or an individual bearer 122 channel of an xDSL line. Bonding of multiple bearer channels in the 123 same xDSL line is not allowed. 125 All schemes allow bonding of up to 32 individual line/channel sub- 126 layers with variable rates, providing common functionality for the 127 configuration, initialization, operation and monitoring of the bonded 128 link. 130 This document defines a MIB module common to all 3 schemes. 131 Additional managed objects, specific to each bonding technology, are 132 defined in GBOND-ATM-MIB [I-D.ietf-adslmib-gbond-atm-mib], GBOND-ETH- 133 MIB [I-D.ietf-adslmib-gbond-eth-mib] and GBOND-TDIM-MIB 134 [I-D.ietf-adslmib-gbond-tdim-mib] modules. 136 2. The Internet-Standard Management Framework 138 For a detailed overview of the documents that describe the current 139 Internet-Standard Management Framework, please refer to section 7 of 140 RFC 3410 [RFC3410]. 142 Managed objects are accessed via a virtual information store, termed 143 the Management Information Base or MIB. MIB objects are generally 144 accessed through the Simple Network Management Protocol (SNMP). 145 Objects in the MIB are defined using the mechanisms defined in the 146 Structure of Management Information (SMI). This document specifies a 147 MIB module that is compliant to the SMIv2, which is described in STD 148 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 149 2580 [RFC2580]. 151 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 152 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 153 document are to be interpreted as described in RFC 2119 [RFC2119]. 155 3. The DSL Forum Management Framework for xDSL Bonding 157 This document makes use of the DSL Forum technical report Management 158 Framework for xDSL Bonding [TR-159], defining a management model and 159 a hierarchy of management objects for the bonded xDSL interfaces. 161 4. Relationship to Other MIB modules 163 This section outlines the relationship of the MIB modules defined in 164 this document with other MIB modules described in the relevant RFCs. 165 Specifically, the following MIB modules are discussed: Interfaces 166 Group MIB (IF-MIB), Inverse Stack Table MIB (IF-INVERTED-STACK-MIB) 167 Interface Stack Capability MIB (IF-CAP-STACK-MIB), G.Bond scheme 168 specific modules: G.Bond/ATM (GBOND-ATM-MIB), G.Bond/Ethernet (GBOND- 169 ETH-MIB) and G.Bond/TDIM (GBOND-TDIM-MIB), and DSL specific MIB 170 modules: ADSL (ADSL-LINE-EXT-MIB), ADSL2 (ADSL2-LINE-MIB), SHDSL 171 (HDSL2-SHDSL-LINE-MIB), VDSL (VDSL-LINE-MIB) and VDSL2 (VDSL2-LINE- 172 MIB). 174 4.1. Relationship to Interfaces Group MIB module 176 A bonded xDSL port is a stacked (a.k.a. aggregated or bonded) 177 interface and as such is managed using generic interface management 178 objects defined in the IF-MIB [RFC2863]. 180 The stack management, i.e., actual connection of the sub-layers to 181 the top layer interface, is done via the ifStackTable, as defined in 182 the IF-MIB [RFC2863] and its inverse ifInvStackTable, as defined in 183 the IF-INVERTED-STACK-MIB [RFC2864]. 185 The ifCapStackTable and its inverse ifInvCapStackTable defined in the 186 IF-CAP-STACK-MIB [RFC5066], extend the stack management with an 187 ability to describe possible connections or cross-connect capability, 188 when a flexible cross-connect matrix is present between the interface 189 layers. 191 4.1.1. Layering Model 193 A G.Bond interface can aggregate up to 32 channel sub-layers, with 194 each channel representing an xDSL line or an xDSL bearer channel. 195 For the purpose of brevity we will refer to the bonded interface as 196 Generic Bonded Sub-layer (GBS) and to the channel sub-layer as 197 Bonding Channel Entity (BCE). 199 A generic G.Bond device can have a number of GBS ports, each 200 connected to a particular upper layer (e.g., Media Access Control 201 (MAC) interface for G.998.2 scheme), while simultaneously cross- 202 connected to a number of underlying BCEs, with a single GBS per BCE 203 relationship. 205 A GBS port is represented in the Interface table (ifTable) as a 206 separate interface with an ifType of g9981, g9982 or g9983 for a 207 particular bonding scheme. 209 Each BCE in the aggregated GBS port is represented in the ifTable as 210 a separate interface with an ifType relevant to a particular xDSL 211 technology, e.g., shdsl(169) or vdsl(97). The ifType values are 212 defined in [IANAifType-MIB]. 214 The following figure shows the layering diagram and corresponding use 215 of ifTable for the bonded xDSL interfaces: 217 .-----------------------------. - 218 | GBS | ^ 1 ifEntry 219 | (TPS-TC) | v ifType: g9981, g9982 or g9983 220 +-----------------+---+-------+ - 221 | TPS-TC \ | | | ^ 222 +---------\ | | | | N ifEntry (N=1..32) 223 | PMS-TC )BCE 1 |...| BCE N | ) ifType: adsl(94), shdsl(169), 224 +---------/ | | | | vdsl(97), vdsl2(251), 225 | PMD / | | | v etc. 226 '-----------------+---+-------' - 228 BCE - Bonding Channel Entity 229 GBS - Generic Bonded Sub-layer 230 PMD - Physical Medium Dependent 231 TPS-TC - Transport Protocol Specific - Transmission Convergence 232 PMS-TC - Physical Media Specific - Transmission Convergence 234 Figure 1: Use of ifTable for bonded xDSL interfaces 236 The ifStackTable is indexed by the ifIndex values of the aggregated 237 G.Bond port (GBS) and the BCEs connected to it. ifStackTable allows a 238 Network Management application to determine which BCEs are connected 239 to a particular GBS and change connections (if supported by the 240 application). The ifInvStackTable, being an inverted version of the 241 ifStackTable, provides an efficient means for a Network Management 242 application to read a subset of the ifStackTable and thereby 243 determine which GBS runs on top of a particular BCE. 245 The ifCapStackTable defined in the IF-CAP-STACK-MIB module, specifies 246 for each higher-layer interface (e.g., GBS port) a list of lower- 247 layer interfaces (e.g., BCEs), which can possibly be cross-connected 248 to that higher-layer interface, determined by the cross-connect 249 capability of the device. This table, modeled after ifStackTable, is 250 read only, reflecting current cross-connect capability of a stacked 251 interface, which can be dynamic in some implementations (e.g., if 252 xDSL lines are located on a pluggable module and the module is pulled 253 out). Note that BCE availability per GBS, described by 254 ifCapStackTable, can be constrained by other parameters, for example 255 by aggregation capacity of a GBS or by the BCE in question being 256 already connected to another GBS. So, in order to ensure that a 257 particular BCE can be connected to the GBS, all respective parameters 258 (e.g., ifCapStackTable, ifStackTable and gBondCapacity) SHALL be 259 inspected. 261 The ifInvCapStackTable, also defined in the IF-CAP-STACK-MIB module, 262 describes which higher-layer interfaces (e.g., GBS ports) can 263 possibly be connected to a particular lower-layer interface (e.g., 264 BCE), providing inverted mapping of ifCapStackTable. While it 265 contains no additional information beyond that already contained in 266 the ifCapStackTable, the ifInvCapStackTable has the ifIndex values in 267 its INDEX clause in the reverse order, i.e., the lower-layer 268 interface first, and the higher-layer interface second, providing an 269 efficient means for a Network Management application to read a subset 270 of the ifCapStackTable and thereby determine which interfaces can be 271 connected to run on top of a particular interface. 273 4.1.2. xDSL Bonding 275 The G.998.x Bonding allows a number of BCEs to be aggregated onto a 276 single logical GBS port, by splitting the incoming traffic into 277 multiple streams, transmitting each stream over a specific BCE and 278 combining the streams at the remote GBS port, preserving the original 279 traffic order. 281 Big Ethernet frames MAY be fragmented before the transmission and 282 reassembled at the remote end to minimize transportation delay. 284 The Bonding is OPTIONAL, meaning that a device with a single BCE MAY 285 perform fragmentation and re-assembly if this function is supported 286 by the device. The agent is REQUIRED to report on the Bonding 287 capability for all types of G.Bond ports (ATM, Ethernet and TDIM). 289 The GBOND-MIB module allows a Network Management application to query 290 Bonding capability and enable/disable it if supported. Note that 291 enabling Bonding effectively turns on fragmentation and re-assembly, 292 even on a single-BCE port. 294 4.1.3. Discovery Operation 296 The G.Bond ports may optionally support discovery operation, whereby 297 BCEs, during initialization, exchange information about their 298 respective aggregation groups (GBS), via xDSL handshake protocol. 299 This information can then be used to detect copper misconnections or 300 for an automatic assignment of the local BCEs into aggregation groups 301 instead of a fixed pre-configuration. 303 The MIB module defined in this document allow a Network Management 304 application to control G.Bond Discovery mechanism and query its 305 results. 307 Two tables are used by the G.Bond Discovery mechanism: ifStackTable 308 and ifCapStackTable. The following pseudo-code gives an example of 309 the Discovery and automatic BCE assignment for a generic multi-GBS 310 G.Bond device, located at Central Office (CO), using objects defined 311 in this MIB module, IF-CAP-STACK-MIB and IF-MIB modules [Note that 312 automatic BCE assignment is only shown here for the purposes of the 313 example. Fixed BCE pre-assignment, manual assignment or auto- 314 assignment using an alternative internal algorithm may be chosen by a 315 particular implementation]: 317 // Go over all GBS ports in the CO device 318 FOREACH gbs[i] IN CO_device 319 { // Perform discovery and auto-assignment on GBS ports 320 // with room for more Channels 321 IF ( gbs[i].NumBCEs < gbs[i].BondCapacity ) 322 { // Assign a unique 6-octets local discovery code to the GBS 323 // e.g., MAC address 324 dc = gbs[i].DiscoveryCode = MAC[i]; 325 // Go over all disconnected Channels, which can 326 // pottentially be connected to the GBS 327 FOREACH bce[j] IN ifCapStackTable[gbs[i]] AND 328 NOT IN ifStackTable[gbs[i]] // not connected 329 { // Try to grab the remote RT_device, by writing the value 330 // of the local 6 Byte discovery code to the remote 331 // discovery code register (via handshake mechanism). 332 // This operation is atomic Set-if-Clear action, i.e., it 333 // would succeed only if the remote discovery register was 334 // zero. Read the remote discovery code register via Get 335 // operation to see if the RT_device, attached via the BCE 336 // is indeed marked as being the CO_device peer. 337 bce[j].RemoteDiscoveryCode = dc; // Set-if-Clear 338 r = bce[j].RemoteDiscoveryCode; // Get 339 IF ( r == dc AND gbs[i].NumBCEs < gbs[i].BondCapacity) 340 { // Remote RT_device connected via BCE[j] is/was a peer 341 // for GBS[i] and there room for another BCE in the 342 // GBS[i] aggregation group (max. Bonding capacity is 343 // not reached yet). 344 // Connect this BCE to the GBS (via ifStackTable, 345 // ifInvStackTable being inverse of ifStackTable is 346 // updated automatically, i.e., gbs[i] is auto-added 347 // to ifInvStackTable[bce[j]]) 348 ADD bce[j] TO ifStackTable[gbs[i]]; 349 gbs[i].NumBCEs = gbs[i].NumBCEs + 1; 350 // Discover all other disconnected BCEs, 351 // attached to the same RT_device and connect them to 352 // the GBS provided there is enough room for more BCEs. 353 FOREACH bce[k] IN ifCapStackTable[gbs[i]] and 354 NOT IN ifStackTable[gbs[i]] 355 { // Get Remote Discovery Code from the BCE to see if 356 // it belongs to a connected RT_device "grabbed" by 357 // the CO_device. 359 r = bce[k].RemoteDiscoveryCode; 360 IF ( r == dc AND gbs[i].NumBCEs < gbs[i].BondCapacity) 361 { // Physically connect the BCE to the GBS 362 // (gbs[i] is auto-added TO ifInvStackTable[bce[k]]) 363 ADD bce[k] TO ifStackTable[gbs[i]]; 364 gbs[i].NumBCEs = gbs[i].NumBCEs + 1; 365 } 366 } 367 } 368 // At this point we have discovered all local BCEs which 369 // are physically connected to the same remote RT_device 370 // and connected them to GBS[i]. Go to the next GBS. 371 BREAK; 372 } 373 } 374 } 376 An SNMP Agent for a G.Bond device builds ifCapStackTable and its 377 inverse ifInvCapStackTable on device initialiation, according to the 378 cross-connect capabilities of the device. 380 Adding a BCE to the ifStackTable row for a specific GBS, involves 381 actual connection of the BCE to the GBS. 383 Note that GBS port does not have to be operationally 'down' for the 384 connection to succeed. In fact, a dynamic BCE addition (and removal) 385 MAY be implemented with an available BCE being initialized first (by 386 setting its ifAdminStatus to 'up') and then added to an operationally 387 'up' GBS port, by modifying a respective ifStackTable (and respective 388 ifInvStackTable) entry. 390 It is RECOMMENDED that a removal of the last operationally 'up' BCE 391 from an operationally 'up' GBS would be rejected by the 392 implementation, as this action would completely drop the link. 394 In addition to the standard handshake-based discovery described 395 above, [G.998.2] defines an optional frame-based discovery and pair 396 management. These frame-based methods are discussed in 397 [I-D.ietf-adslmib-gbond-eth-mib]. 399 4.1.4. G.Bond ports initialization 401 G.Bond ports being built on top of xDSL technology, require a lengthy 402 initialization or 'training' process, before any data can pass. 403 During this initialization both ends of a link (peers) work 404 cooperatively to achieve required data rate on a particular copper 405 pair. Sometimes, when the copper line is too long or the noise on 406 the line is too high, that 'training' process may fail to achieve a 407 specific target rate with required characteristics. 409 The ifAdminStatus object from the IF-MIB, controls the desired state 410 of a GBS with all the BCEs connected to it or of an individual BCE 411 port. Setting this object to 'up' instructs a particular GBS or a 412 BCE to start initialization process, which may take tens of seconds 413 for G.Bond ports. The ifOperStatus object shows the operational 414 state of an interface (extended by ifMauMediaAvailable object from 415 MAU-MIB [RFC4836] for GBS and *Status object from a relevant line MIB 416 for BCE interfaces). 418 A disconnected BCE may be initialized by changing the ifAdminState 419 from 'down' to 'up'. Changing the ifAdminState to 'up' on the GBS 420 initializes all BCEs connected to that particular GBS. Note that in 421 case of bonding some interfaces may fail to initialize while others 422 succeed. The GBS is considered operationally 'up' if at least one 423 bonded BCE is operationally 'up'. When all BCEs connected to the GBS 424 are 'down' the GBS SHALL be considered operationally 425 'lowerLayerDown'. The GBS SHALL be considered operationally 426 'notPresent' if it is not connected to any BCE. The GBS/BCE 427 interface SHALL remain operationally 'down' during initialization. 429 4.1.5. Usage of ifTable 431 Both BCE and GBS interfaces are managed using interface specific 432 management objects defined in the GBOND-MIB module and generic 433 interface objects from the ifTable of IF-MIB, with all management 434 table entries referenced by the interface index ifIndex. 436 The following table summarizes G.Bond specific interpretations for 437 some of the ifTable objects specified by the mandatory 438 ifGeneralInformationGroup: 440 +---------------+---------------------------------------------------+ 441 | IF-MIB object | G.Bond interpretation | 442 +---------------+---------------------------------------------------+ 443 | ifIndex | Interface index. Note that each BCE and each GBS | 444 | | in the G.Bond PHY MUST have a unique index, as | 445 | | there some GBS and BCE specific attributes | 446 | | accessible only on the GBS or BCE level. | 447 +---------------+---------------------------------------------------+ 448 | ifType | g9981, g9982 or g9982 for the ATM, Ethernet or | 449 | | TDIM GBS respectively, shdsl(169) for G.SHDSL | 450 | | BCE, vdsl(97) for VDSL BCE, etc. | 451 +---------------+---------------------------------------------------+ 452 +---------------+---------------------------------------------------+ 453 | ifSpeed | Operating data rate for the BCE. For the GBS it | 454 | | is the sum of the current operating data rates of | 455 | | all BCEs in the aggregation group, without the | 456 | | encapsulation overhead and G.Bond overhead, but | 457 | | accounting for the Inter-Frame Gaps (IFG). When a | 458 | | GBS or a BCE is operating in an assymetrical | 459 | | fashion (upstream data rate differs from the | 460 | | downstream one) the lowest of the values is | 461 | | shown. | 462 +---------------+---------------------------------------------------+ 463 | ifAdminStatus | Setting this object to 'up' instructs a | 464 | | particular GBS (with all BCEs connected to it) or | 465 | | a BCE to start initialization process | 466 +---------------+---------------------------------------------------+ 467 | ifOperStatus | a relevant *Status object from a particular line | 468 | | MIB supplements the 'down' value of ifOperStatus | 469 | | for BCEs. | 470 +---------------+---------------------------------------------------+ 472 Table 1: G.Bond interpretation of IF-MIB objects 474 4.2. Relationship to G.Bond ATM, ETH and TDIM MIB modules 476 This MIB module defined in this document is common to all three G.998 477 bonding schemes. It MUST be used in conjunction with a bonding 478 scheme-specific MIB module: 480 o GBOND-ATM-MIB [I-D.ietf-adslmib-gbond-atm-mib] for a G.998.1 481 bonded interface. 483 o GBOND-ETH-MIB [I-D.ietf-adslmib-gbond-eth-mib] for a G.998.2 484 bonded interface. 486 o GBOND-TDIM-MIB [I-D.ietf-adslmib-gbond-tdim-mib] for a G.998.3 487 bonded interface. 489 4.3. Relationship to xDSL MIB modules 491 Each xDSL technology is described in a relevant xDSL line MIB module: 492 e.g., HDSL2-SHDSL-LINE-MIB [RFC4319] for G.SHDSL, ADSL-LINE-EXT-MIB 493 [RFC3440] for ADSL, ADSL2-LINE-MIB [RFC4706] for ADSL2, VDSL-LINE-MIB 494 [RFC3728] for VDSL or VDSL2-LINE-MIB [RFC5650] for VDSL2. 496 These MIBs are used to manage individual xDSL lines/channels (BCEs). 498 5. MIB Structure 500 5.1. Overview 502 The main management objects defined in the GBOND-MIB module are split 503 into 2 groups, structured as recommended by RFC 4181 [RFC4181]: 505 o gBondPort - containing objects for configuration, capabilities, 506 status, historical performance monitoring and notifications, 507 common to all G.Bond ports (GBS). 509 o gBondBce - containing a single common object for configuration of 510 the remote discovery code per BCE. Note that the rest of the 511 objects for BCE configuration, capabilities, status and 512 notifications, is located in relevant xDSL line MIB modules as 513 well as in the bonding scheme specific MIB modules. 515 5.2. Performance Monitoring 517 The OPTIONAL performance monitoring counters, thresholds and history 518 buckets (interval-counters) defined in [TR-159] are implemented using 519 the textual conventions defined in the HC-PerfHist-TC-MIB [RFC3705]. 520 The HC-PerfHist-TC-MIB defines 64-bit versions of the textual 521 conventions found in PerfHist-TC-MIB [RFC3593]. 523 The agent SHOULD align the beginning of each interval to a fifteen 524 minute boundary of a wall clock. Likewise, the beginning of each one 525 day intervals SHOULD be aligned with the start of a day. 527 Counters are not reset when a GBS is reinitialized, but rather only 528 when the agent is reset or reinitialized (or under specific request 529 outside the scope of this MIB module). 531 5.3. Mapping of DSL Forum TR-159 Managed Objects 533 This section contains the mapping between relevant managed objects 534 (attributes) defined in [TR-159] and managed objects defined in this 535 document and in associated MIB modules, i.e., the IF-MIB [RFC2863]. 537 +---------------------------------+---------------------------------+ 538 | G.Bond Managed Object | Corresponding SNMP Object | 539 +---------------------------------+---------------------------------+ 540 | oBondingGroup - Basic Package | | 541 | (Mandatory) | | 542 +---------------------------------+---------------------------------+ 543 | aGroupID | ifIndex (IF-MIB) | 544 +---------------------------------+---------------------------------+ 545 | aGroupBondSchemesSupported | gBondSchemesSupported | 546 | aGroupPeerBondSchemesSupported | gBondPeerSchemesSupported | 547 +---------------------------------+---------------------------------+ 548 | aGroupAdminBondScheme | gBondAdminScheme | 549 +---------------------------------+---------------------------------+ 550 | aGroupPeerAdminBondScheme | gBondPeerAdminScheme | 551 +---------------------------------+---------------------------------+ 552 | aGroupOperBondScheme | gBondOperScheme | 553 +---------------------------------+---------------------------------+ 554 | aGroupPeerOperBondScheme | gBondPeerOperScheme | 555 +---------------------------------+---------------------------------+ 556 | aGroupEnd | gBondPortSide | 557 +---------------------------------+---------------------------------+ 558 | aGroupOperState | ifOperStatus (IF-MIB) | 559 +---------------------------------+---------------------------------+ 560 | aGroupAdminState | ifAdminStatus (IF-MIB) | 561 +---------------------------------+---------------------------------+ 562 | aGroupStatus | gBondFltStatus | 563 +---------------------------------+---------------------------------+ 564 | aGroupCapacity | gBondCapacity | 565 +---------------------------------+---------------------------------+ 566 | aGroupPeerCapacity | gBondPeerCapacity | 567 +---------------------------------+---------------------------------+ 568 | aGroupNumChannels | gBondNumBCEs | 569 +---------------------------------+---------------------------------+ 570 | aGroupName | ifName (IF-MIB) | 571 +---------------------------------+---------------------------------+ 572 | aGroupDiscoveryCode | gBondDiscoveryCode | 573 +---------------------------------+---------------------------------+ 574 | aGroupUpRate | gBondUpDataRate | 575 +---------------------------------+---------------------------------+ 576 | aGroupDownRate | gBondDnDataRate | 577 +---------------------------------+---------------------------------+ 578 | aGroupTargetUpRate | gBondTargetUpDataRate | 579 +---------------------------------+---------------------------------+ 580 | aGroupTargetDownRate | gBondTargetDnDataRate | 581 +---------------------------------+---------------------------------+ 582 | aGroupThreshLowUpRate | gBondThreshLowUpRate | 583 +---------------------------------+---------------------------------+ 584 | aGroupThreshLowDownRate | gBondThreshLowDnRate | 585 +---------------------------------+---------------------------------+ 586 | aGroupLowRateCrossingEnable | gBondLowRateCrossingEnable | 587 +---------------------------------+---------------------------------+ 588 | nGroupLowUpRateCrossing | gBondLowUpRateCrossing | 589 +---------------------------------+---------------------------------+ 590 | nGroupLowDownRateCrossing | gBondLowDnRateCrossing | 591 +---------------------------------+---------------------------------+ 592 +---------------------------------+---------------------------------+ 593 | aGroupLinkUpDownEnable | _EdNote: Currently IF-MIB | 594 | | doesn't provide a control for | 595 | | the linkUp/linkDown | 596 | | notifications. Can we define a | 597 | | control in one MIB module while | 598 | | the notifications are in | 599 | | another?_ | 600 +---------------------------------+---------------------------------+ 601 | nGroupLinkUp | linkDown (IF-MIB) | 602 +---------------------------------+---------------------------------+ 603 | nGroupLinkDown | linkUp (IF-MIB) | 604 +---------------------------------+---------------------------------+ 605 | oBondingGroup - PM Package | | 606 | (Optional) | | 607 +---------------------------------+---------------------------------+ 608 | aGroupPerfES | gBondPerfES | 609 +---------------------------------+---------------------------------+ 610 | aGroupPerfSES | gBondPerfSES | 611 +---------------------------------+---------------------------------+ 612 | aGroupPerfUAS | gBondPerfUAS | 613 +---------------------------------+---------------------------------+ 614 | aGroupPerf15MinValidIntervals | gBondPerf15MinValidIntervals | 615 +---------------------------------+---------------------------------+ 616 | aGroupPerf15MinInvalidIntervals | gBondPerf15MinInvalidIntervals | 617 +---------------------------------+---------------------------------+ 618 | aGroupPerfCurr15MinTimeElapsed | gBondPerfCurr15MinTimeElapsed | 619 +---------------------------------+---------------------------------+ 620 | aGroupPerfCurr15MinES | gBondPerfCurr15MinES | 621 +---------------------------------+---------------------------------+ 622 | aGroupPerfCurr15MinSES | gBondPerfCurr15MinSES | 623 +---------------------------------+---------------------------------+ 624 | aGroupPerfCurr15MinUAS | gBondPerfCurr15MinUAS | 625 +---------------------------------+---------------------------------+ 626 | aGroupPerfTcaEnable | gBondPerfTcaEnable | 627 +---------------------------------+---------------------------------+ 628 | aGroupPerfThreshold15MinES | gBondPerfThereshold15MinES | 629 +---------------------------------+---------------------------------+ 630 | aGroupPerfThreshold15MinSES | gBondPerfThereshold15MinSES | 631 +---------------------------------+---------------------------------+ 632 | aGroupPerfThreshold15MinUAS | gBondPerfThereshold15MinUAS | 633 +---------------------------------+---------------------------------+ 634 | nGroupPerfTca15MinES | gBondPerfTca15MinESCrossing | 635 +---------------------------------+---------------------------------+ 636 | nGroupPerfTca15MinSES | gBondPerfTca15MinSESCrossing | 637 +---------------------------------+---------------------------------+ 638 | nGroupPerfTca15MinUAS | gBondPerfTca15MinUASCrossing | 639 +---------------------------------+---------------------------------+ 640 +---------------------------------+---------------------------------+ 641 | aGroupPerf1DayValidIntervals | gBondPerf1DayValidIntervals | 642 +---------------------------------+---------------------------------+ 643 | aGroupPerf1DayInvalidIntervals | gBondPerf1DayInvalidIntervals | 644 +---------------------------------+---------------------------------+ 645 | aGroupPerfCurr1DayTimeElapsed | gBondPerfCurr1DayTimeElapsed | 646 +---------------------------------+---------------------------------+ 647 | aGroupPerfCurr1DayES | gBondPerf1DayIntervalES | 648 +---------------------------------+---------------------------------+ 649 | aGroupPerfCurr1DaySES | gBondPerf1DayIntervalSES | 650 +---------------------------------+---------------------------------+ 651 | aGroupPerfCurr1DayUAS | gBondPerf1DayIntervalUAS | 652 +---------------------------------+---------------------------------+ 653 | aGroupPerfThreshold1DayES | gBondPerfThreshold1DayES | 654 +---------------------------------+---------------------------------+ 655 | aGroupPerfThreshold1DaySES | gBondPerfThreshold1DaySES | 656 +---------------------------------+---------------------------------+ 657 | aGroupPerfThreshold1DayUAS | gBondPerfThreshold1DayUAS | 658 +---------------------------------+---------------------------------+ 659 | nGroupPerfTca1DayES | gBondPerfTca1DayESCrossing | 660 +---------------------------------+---------------------------------+ 661 | nGroupPerfTca1DaySES | gBondPerfTca1DaySESCrossing | 662 +---------------------------------+---------------------------------+ 663 | nGroupPerfTca1DayUAS | gBondPerfTca1DayUASCrossing | 664 +---------------------------------+---------------------------------+ 665 | aGroupPerf15MinIntervalNumber | gBondPerf15MinIntervalIndex | 666 +---------------------------------+---------------------------------+ 667 | aGroupPerf15MinIntervalValid | gBondPerf15MinIntervalValid | 668 +---------------------------------+---------------------------------+ 669 | aGroupPerf15MinIntervalES | gBondPerf15MinIntervalES | 670 +---------------------------------+---------------------------------+ 671 | aGroupPerf15MinIntervalSES | gBondPerf15MinIntervalSES | 672 +---------------------------------+---------------------------------+ 673 | aGroupPerf15MinIntervalUAS | gBondPerf15MinIntervalUAS | 674 +---------------------------------+---------------------------------+ 675 | aGroupPerf1DayIntervalNumber | gBondPerf1DayIntervalIndex | 676 +---------------------------------+---------------------------------+ 677 | aGroupPerf1DayIntervalValid | gBondPerf1DayIntervalValid | 678 +---------------------------------+---------------------------------+ 679 | aGroupPerf1DayIntervalMoniSecs | gBondPerf1DayIntervalMoniTime | 680 +---------------------------------+---------------------------------+ 681 | aGroupPerf1DayIntervalES | gBondPerf1DayIntervalES | 682 +---------------------------------+---------------------------------+ 683 | aGroupPerf1DayIntervalSES | gBondPerf1DayIntervalSES | 684 +---------------------------------+---------------------------------+ 685 | aGroupPerf1DayIntervalUAS | gBondPerf1DayIntervalUAS | 686 +---------------------------------+---------------------------------+ 687 +---------------------------------+---------------------------------+ 688 | oLine - Basic Package | | 689 | (Mandatory) | | 690 +---------------------------------+---------------------------------+ 691 | aLineID | ifIndex (IF-MIB) | 692 +---------------------------------+---------------------------------+ 693 | aLineType | ifType (IF-MIB) | 694 +---------------------------------+---------------------------------+ 695 | aLineOperState | ifOperStatus (IF-MIB) | 696 +---------------------------------+---------------------------------+ 697 | aLineStatus | *dsl*CurrStatus (*DSL-LINE-MIB) | 698 +---------------------------------+---------------------------------+ 699 | aLineEnd | *dsl*Side (*DSL-LINE-MIB) | 700 +---------------------------------+---------------------------------+ 701 | aLineAdminState | ifAdminStatus (IF-MIB) | 702 +---------------------------------+---------------------------------+ 703 | aLineRemoteDiscoveryCode | gBondBceRemoteDiscoveryCode | 704 +---------------------------------+---------------------------------+ 705 | aLineUpDownEnable | _EdNote: Currently IF-MIB | 706 | | doesn't provide a control for | 707 | | the linkUp/linkDown | 708 | | notifications. Can we define a | 709 | | control in one MIB module while | 710 | | the notifications are in | 711 | | another?_ | 712 +---------------------------------+---------------------------------+ 713 | nLineUp | linkUp (IF-MIB) | 714 +---------------------------------+---------------------------------+ 715 | nLineDown | linkDown (IF-MIB) | 716 +---------------------------------+---------------------------------+ 717 | oChannel - Basic Package | | 718 | (Mandatory) | | 719 +---------------------------------+---------------------------------+ 720 | aChannelID | ifIndex (IF-MIB) | 721 +---------------------------------+---------------------------------+ 722 | aChannelGroupID | | 723 +---------------------------------+---------------------------------+ 724 | aChannelType | ifType (IF-MIB) | 725 +---------------------------------+---------------------------------+ 726 | aChannelOperState | ifOperStatus (IF-MIB) | 727 +---------------------------------+---------------------------------+ 728 | aChannelStatus | *dsl*CurrStatus | 729 | | (*DSL-LINE-MIB), | 730 | | xdsl2ChStatus*Status | 731 | | (VDSL2-LINE-MIB) | 732 +---------------------------------+---------------------------------+ 734 Table 2: Mapping of TR-159 Managed Objects 736 6. xDSL Multi-pair Bonding MIB Definitions 738 GBOND-MIB DEFINITIONS ::= BEGIN 740 IMPORTS 741 MODULE-IDENTITY, 742 OBJECT-TYPE, 743 NOTIFICATION-TYPE, 744 mib-2, 745 Unsigned32, 746 Gauge32 747 FROM SNMPv2-SMI -- [RFC2578] 748 TEXTUAL-CONVENTION, 749 TruthValue, 750 RowStatus, 751 PhysAddress 752 FROM SNMPv2-TC -- [RFC2579] 753 MODULE-COMPLIANCE, 754 OBJECT-GROUP, 755 NOTIFICATION-GROUP 756 FROM SNMPv2-CONF -- [RFC2580] 757 SnmpAdminString 758 FROM SNMP-FRAMEWORK-MIB -- [RFC3411] 759 ifIndex 760 FROM IF-MIB -- [RFC2863] 761 HCPerfCurrentCount, 762 HCPerfIntervalCount, 763 HCPerfIntervalThreshold, 764 HCPerfValidIntervals, 765 HCPerfInvalidIntervals, 766 HCPerfTimeElapsed, 767 HCPerfTotalCount 768 FROM HC-PerfHist-TC-MIB -- [RFC3705] 769 ; 770 ------------------------------------------------------------------------ 771 gBondMIB MODULE-IDENTITY 772 LAST-UPDATED "201011270000Z" -- Nov 27, 2010 773 ORGANIZATION "IETF ADSL MIB Working Group" 774 CONTACT-INFO 775 "WG charter: 776 http://www.ietf.org/html.charters/adslmib-charter.html 778 Mailing Lists: 779 General Discussion: adslmib@ietf.org 780 To Subscribe: adslmib-request@ietf.org 781 In Body: subscribe your_email_address 783 Chair: Menachem Dodge 785 Postal: ECI Telecom, Ltd. 786 30 Hasivim St., 787 Petach-Tikva 49517 788 Israel 789 Phone: +972-3-926-8421 790 EMail: menachem.dodge@ecitele.com 792 Editor: Edward Beili 793 Postal: Actelis Networks, Inc. 794 25 Bazel St., P.O.B. 10173 795 Petach-Tikva 10173 796 Israel 797 Phone: +972-3-924-3491 798 EMail: edward.beili@actelis.com 800 Editor: Moti Morgenstern 801 Postal: ECI Telecom 802 30 Hasivim St. 803 Petach-Tikva 49517 804 Israel 805 Phone: +972-3-926-6258 806 EMail: moti.morgenstern@ecitele.com" 808 DESCRIPTION 809 "The objects in this MIB module are used to manage the 810 multi-pair bonded xDSL Interfaces, defined in ITU-T 811 recommendations G.998.1, G.998.2 and G.998.3. 813 This MIB module MUST be used in conjunction with a bonding 814 scheme specific MIB module, that is, GBOND-ATM-MIB, 815 GBOND-ETH-MIB or GBOND-TDIM-MIB. 817 The following references are used throughout this MIB module: 819 [G.998.1] refers to: 820 ITU-T Recommendation G.998.1: 'ATM-based multi-pair bonding', 821 January 2005. 823 [G.998.2] refers to: 824 ITU-T Recommendation G.998.2: 'Ethernet-based multi-pair 825 bonding', January 2005. 827 [G.998.3] refers to: 828 ITU-T Recommendation G.998.3: 'Multi-pair bonding using 829 time-division inverse multiplexing', January 2005. 831 [TR-159] refers to: 832 Broadband Forum Technical Report: 'Management Framework for 833 xDSL Bonding', December 2008. 835 Naming Conventions: 836 BCE - Bonding Channel Entity 837 BTU - Bonding Transmission Unit 838 CO - Central Office 839 CPE - Customer Premises Equipment 840 GBS - Generic Bonding Sublayer 841 PM - Performance Monitoring 842 SNR - Signal to Noise Ratio 843 TCA - Threshold Crossing Alert 845 Copyright (C) The IETF Trust (2010). 846 This version of this MIB module is part of RFC XXXX; 847 see the RFC itself for full legal notices." 849 REVISION "201011270000Z" -- Nov 27, 2010 850 DESCRIPTION "Initial version, published as RFC XXXX." 852 -- EdNote: Replace XXXX with the actual RFC number & 853 -- remove this note 855 ::= { mib-2 ZZZ } 857 -- EdNote: Replace ZZZ with a real OID once it is 858 -- allocated & remove this note. 860 -- Sections of the module 861 -- Structured as recommended by [RFC4181], Appendix D 863 gBondObjects OBJECT IDENTIFIER ::= { gBondMIB 1 } 865 gBondConformance OBJECT IDENTIFIER ::= { gBondMIB 2 } 867 -- Groups in the module 869 gBondPort OBJECT IDENTIFIER ::= { gBondObjects 1 } 871 gBondBce OBJECT IDENTIFIER ::= { gBondObjects 2 } 873 -- Textual Conventions 875 GBondSchemeList ::= TEXTUAL-CONVENTION 876 STATUS current 877 DESCRIPTION 878 "This textual convention defines a bitmap of possible ITU-T 879 G.998 (G.Bond) bonding schemes. Currently there are 3 bonding 880 schemes defined: G.998.1, G.998.2 and G.998.3, identified by 881 bit values g9981(1), g9982(2) and g9983(3), respectively. 882 An additional value of unknown(0), can be returned as a result 883 of GET operation, when an value of the object cannot be 884 determined, for example a peer GBS cannot be reached or it 885 does not support any kind of bonding." 886 SYNTAX BITS { 887 unknown(0), 888 g9981(1), 889 g9982(2), 890 g9983(3) 891 } 893 GBondScheme ::= TEXTUAL-CONVENTION 894 STATUS current 895 DESCRIPTION 896 "This textual convention defines ITU-T G.998 bonding scheme 897 values. Possible values are: 898 unknown(0) - undefined or unknown 899 g9981(1) - G.998.1 (G.Bond/ATM) 900 g9982(2) - G.998.2 (G.Bond/Ethernt) 901 g9983(3) - G.998.3 (G.Bond/TDIM)." 902 SYNTAX INTEGER { 903 unknown(0), 904 g9981(1), 905 g9982(2), 906 g9983(3) 907 } 909 GBondPerf1DayIntervalThreshold ::= TEXTUAL-CONVENTION 910 DISPLAY-HINT "d" 911 STATUS current 912 DESCRIPTION 913 "This textual convention defines a range of values that may be 914 set in a fault threshold alarm control for a 1-day interval. 915 As the number of seconds in a 1-day interval numbers at most 916 86400, objects of this type may have a range of 0...86400, 917 where the value of 0 disables the alarm." 918 SYNTAX Unsigned32 (0..86400) 920 -- Port Notifications Group 922 gBondPortNotifications OBJECT IDENTIFIER ::= { gBondPort 0 } 924 gBondLowUpRateCrossing NOTIFICATION-TYPE 925 OBJECTS { 926 -- ifIndex is not needed here since we are under specific GBS 927 gBondUpDataRate, 928 gBondThreshLowUpRate 929 } 930 STATUS current 931 DESCRIPTION 932 "This notification indicates that the G.Bond port' upstream 933 data rate has reached/dropped below or exceeded the low 934 upstream rate threshold, specified by gBondThreshLowUpRate. 936 This notification MAY be sent for the -O subtype ports 937 while the port is up, on the crossing event in both 938 directions: from normal (rate is above the threshold) to low 939 (rate equals the threshold or below it) and from low to 940 normal. This notification is not applicable to the -R 941 subtypes. 943 It is RECOMMENDED that a small debouncing period of 2.5 sec, 944 between the detection of the condition and notification, 945 is implemented to prevent simultaneous LinkUp/LinkDown and 946 gBondLowUpRateCrossing notifications to be sent. 948 The adaptive nature of the G.Bond technology allows the port 949 to adapt itself to the changes in the copper environment, 950 e.g., an impulse noise, alien crosstalk, or a 951 micro-interruption may temporarily drop one or more BCEs in 952 the aggregation group, causing a rate degradation of the 953 aggregated G.Bond link. The dropped BCEs would then try to 954 re-initialize, possibly at a lower rate than before, adjusting 955 the rate to provide required target SNR margin. 957 Generation of this notification is controlled by the 958 gBondLowRateCrossingEnable object. 960 This object maps to the TR-159 notification 961 nGroupLowUpRateCrossing." 962 REFERENCE 963 "[TR-159] 5.5.1.24" 964 ::= { gBondPortNotifications 1 } 966 gBondLowDnRateCrossing NOTIFICATION-TYPE 967 OBJECTS { 968 -- ifIndex is not needed here since we are under specific GBS 969 gBondDnDataRate, 970 gBondThreshLowDnRate 971 } 972 STATUS current 973 DESCRIPTION 974 "This notification indicates that the G.Bond port' downstream 975 data rate has reached/dropped below or exceeded the low 976 downstream rate threshold, specified by 977 gBondThreshLowDnRate. 979 This notification MAY be sent for the -O subtype ports 980 while the port is up, on the crossing event in both 981 directions: from normal (rate is above the threshold) to low 982 (rate equals the threshold or below it) and from low to 983 normal. This notification is not applicable to the -R 984 subtypes. 986 It is RECOMMENDED that a small debouncing period of 2.5 sec, 987 between the detection of the condition and notification, 988 is implemented to prevent simultaneous LinkUp/LinkDown and 989 gBondLowDnRateCrossing notifications to be sent. 991 The adaptive nature of the G.Bond technology allows the port 992 to adapt itself to the changes in the copper environment, 993 e.g., an impulse noise, alien crosstalk, or a 994 micro-interruption may temporarily drop one or more BCEs in 995 the aggregation group, causing a rate degradation of the 996 aggregated G.Bond link. The dropped BCEs would then try to 997 re-initialize, possibly at a lower rate than before, 998 adjusting the rate to provide required target SNR margin. 1000 Generation of this notification is controlled by the 1001 gBondLowRateCrossingEnable object. 1003 This object maps to the TR-159 notification 1004 nGroupLowDownRateCrossing." 1005 REFERENCE 1006 "[TR-159] 5.5.1.25" 1007 ::= { gBondPortNotifications 2} 1009 gBondPerfTca15MinESCrossing NOTIFICATION-TYPE 1010 OBJECTS { 1011 -- ifIndex is not needed here since we are under specific GBS 1012 gBondPerfCurr15MinES, 1013 gBondPerfThreshold15MinES 1014 } 1015 STATUS current 1016 DESCRIPTION 1017 "This notification indicates that the Errored Seconds threshold, 1018 specified by gBondPerfThreshold15MinES, has been reached or 1019 exceeded for the GPS port. 1021 Generation of this notification is controlled by 1022 gBondPerfTcaEnable and gBondPerfThreshold15MinES objects. 1024 This object maps to the TR-159 notification 1025 nGroupPerfTca15MinES." 1026 REFERENCE 1027 "[TR-159] 5.5.1.42" 1028 ::= { gBondPortNotifications 3} 1030 gBondPerfTca15MinSESCrossing NOTIFICATION-TYPE 1031 OBJECTS { 1032 -- ifIndex is not needed here since we are under specific GBS 1033 gBondPerfCurr15MinSES, 1034 gBondPerfThreshold15MinSES 1035 } 1036 STATUS current 1037 DESCRIPTION 1038 "This notification indicates that the Severely Errored Seconds 1039 threshold, specified by gBondPerfThreshold15MinSES, has been 1040 reached or exceeded for the GPS port. 1042 Generation of this notification is controlled by 1043 gBondPerfTcaEnable and gBondPerfThreshold15MinSES objects. 1045 This object maps to the TR-159 notification 1046 nGroupPerfTca15MinSES." 1047 REFERENCE 1048 "[TR-159] 5.5.1.43" 1049 ::= { gBondPortNotifications 4} 1051 gBondPerfTca15MinUASCrossing NOTIFICATION-TYPE 1052 OBJECTS { 1053 -- ifIndex is not needed here since we are under specific GBS 1054 gBondPerfCurr15MinUAS, 1055 gBondPerfThreshold15MinUAS 1056 } 1057 STATUS current 1058 DESCRIPTION 1059 "This notification indicates that the Unavailable Seconds 1060 threshold, specified by gBondPerfThreshold15MinES, has been 1061 reached or exceeded for the GPS port. 1063 Generation of this notification is controlled by 1064 gBondPerfTcaEnable and gBondPerfThreshold15MinUAS objects. 1066 This object maps to the TR-159 notification 1067 nGroupPerfTca15MinUAS." 1068 REFERENCE 1069 "[TR-159] 5.5.1.44" 1070 ::= { gBondPortNotifications 5} 1072 gBondPerfTca1DayESCrossing NOTIFICATION-TYPE 1073 OBJECTS { 1074 -- ifIndex is not needed here since we are under specific GBS 1075 gBondPerfCurr1DayES, 1076 gBondPerfThreshold1DayES 1077 } 1078 STATUS current 1079 DESCRIPTION 1080 "This notification indicates that the Errored Seconds threshold, 1081 specified by gBondPerfThreshold1DayES, has been reached or 1082 exceeded for the GPS port. 1084 Generation of this notification is controlled by 1085 gBondPerfTcaEnable and gBondPerfThreshold1DayES objects. 1087 This object maps to the TR-159 notification 1088 nGroupPerfTca1DayES." 1089 REFERENCE 1090 "[TR-159] 5.5.1.54" 1091 ::= { gBondPortNotifications 6} 1093 gBondPerfTca1DaySESCrossing NOTIFICATION-TYPE 1094 OBJECTS { 1095 -- ifIndex is not needed here since we are under specific GBS 1096 gBondPerfCurr1DaySES, 1097 gBondPerfThreshold1DaySES 1098 } 1099 STATUS current 1100 DESCRIPTION 1101 "This notification indicates that the Severely Errored Seconds 1102 threshold, specified by gBondPerfThreshold1DaySES, has been 1103 reached or exceeded for the GPS port. 1105 Generation of this notification is controlled by 1106 gBondPerfTcaEnable and gBondPerfThreshold1DaySES objects. 1108 This object maps to the TR-159 notification 1109 nGroupPerfTca1DaySES." 1110 REFERENCE 1111 "[TR-159] 5.5.1.55" 1112 ::= { gBondPortNotifications 7} 1114 gBondPerfTca1DayUASCrossing NOTIFICATION-TYPE 1115 OBJECTS { 1116 -- ifIndex is not needed here since we are under specific GBS 1117 gBondPerfCurr1DayUAS, 1118 gBondPerfThreshold1DayUAS 1119 } 1120 STATUS current 1121 DESCRIPTION 1122 "This notification indicates that the Unavailable Seconds 1123 threshold, specified by gBondPerfThreshold1DayUAS, has been 1124 reached or exceeded for the GPS port. 1126 Generation of this notification is controlled by 1127 gBondPerfTcaEnable and gBondPerfThreshold1DayUAS objects. 1129 This object maps to the TR-159 notification 1130 nGroupPerfTca1DayUAS." 1131 REFERENCE 1132 "[TR-159] 5.5.1.56" 1133 ::= { gBondPortNotifications 8} 1135 -- G.Bond Port (GBS) group 1137 gBondPortConfTable OBJECT-TYPE 1138 SYNTAX SEQUENCE OF GBondPortConfEntry 1139 MAX-ACCESS not-accessible 1140 STATUS current 1141 DESCRIPTION 1142 "Table for Configuration of G.Bond GBS ports. Entries in this 1143 table MUST be maintained in a persistent manner" 1144 ::= { gBondPort 1 } 1146 gBondPortConfEntry OBJECT-TYPE 1147 SYNTAX GBondPortConfEntry 1148 MAX-ACCESS not-accessible 1149 STATUS current 1150 DESCRIPTION 1151 "An entry in the G.Bond Port Configuration table. 1152 Each entry represents an G.Bond port indexed by the ifIndex. 1153 Note that an G.Bond GBS port runs on top of a single 1154 or multiple BCE port(s), which are also indexed by ifIndex." 1155 INDEX { ifIndex } 1156 ::= { gBondPortConfTable 1 } 1158 GBondPortConfEntry ::= 1159 SEQUENCE { 1160 gBondAdminScheme GBondScheme, 1161 gBondPeerAdminScheme GBondScheme, 1162 gBondDiscoveryCode PhysAddress, 1163 gBondTargetUpDataRate Unsigned32, 1164 gBondTargetDnDataRate Unsigned32, 1165 gBondThreshLowUpRate Unsigned32, 1166 gBondThreshLowDnRate Unsigned32, 1167 gBondLowRateCrossingEnable TruthValue, 1168 gBondPerfTcaConfProfile SnmpAdminString, 1169 gBondPerfTcaEnable TruthValue 1170 } 1172 gBondAdminScheme OBJECT-TYPE 1173 SYNTAX GBondScheme 1174 MAX-ACCESS read-write 1175 STATUS current 1176 DESCRIPTION 1177 "A desired bonding scheme for a G.Bond GBS port. 1178 The following values instruct the port to use corresponding 1179 bonding scheme if supported: 1180 g9981(1) - instructs the port to use G.998.1 bonding 1181 g9982(2) - instructs the port to use G.998.2 bonding 1182 g9983(3) - instructs the port to use G.998.3 bonding 1184 Changing of the gBondAdminScheme MUST be performed when the 1185 link is Down. Attempts to change this object MUST be rejected 1186 (in case of SNMP with the error inconsistentValue), if the 1187 link is Up or Initializing. Attempts to change this object to 1188 an unsupported bonding scheme (see gBondSchemesSupported) 1189 SHALL be rejected (in case of SNMP with the error wrongValue). 1191 This object MUST be maintained in a persistent manner. 1193 This object maps to the TR-159 attribute 1194 aGroupAdminBondScheme." 1195 REFERENCE 1196 "[TR-159] 5.5.1.6" 1197 ::= { gBondPortConfEntry 1 } 1199 gBondPeerAdminScheme OBJECT-TYPE 1200 SYNTAX GBondScheme 1201 MAX-ACCESS read-write 1202 STATUS current 1203 DESCRIPTION 1204 "A desired bonding scheme for a peer (link partner) G.Bond 1205 port (GBS). 1206 The following values instruct the peer port to use 1207 corresponding bonding scheme if supported: 1208 g9981(1) - instructs the port to use G.998.1 bonding 1209 g9982(2) - instructs the port to use G.998.2 bonding 1210 g9983(3) - instructs the port to use G.998.3 bonding 1212 Changing of the gBondAdminScheme MUST be performed when the 1213 link is Down. Attempts to change this object MUST be rejected 1214 (in case of SNMP with the error inconsistentValue), if the 1215 link is Up or Initializing. Attempts to change this object to 1216 an unsupported bonding scheme (see gBondPeerSchemesSupported) 1217 SHALL be rejected (in case of SNMP with the error wrongValue). 1219 This object MUST be maintained in a persistent manner. 1221 This object maps to the TR-159 attribute 1222 aGroupPeerAdminBondScheme." 1223 REFERENCE 1224 "[TR-159] 5.5.1.7" 1225 ::= { gBondPortConfEntry 2 } 1227 gBondDiscoveryCode OBJECT-TYPE 1228 SYNTAX PhysAddress (SIZE(6)) 1229 MAX-ACCESS read-write 1230 STATUS current 1231 DESCRIPTION 1232 "A Discovery Code of the G.Bond port (GBS). 1233 A unique 6 octet long code used by the Discovery function. 1234 This object MUST be instantiated for the -O subtype GBS before 1235 writing operations on the gBondBceRemoteDiscoveryCode 1236 (Set_if_Clear and Clear_if_Same) are performed by BCEs 1237 associated with the GBS. 1238 The initial value of this object for -R subtype ports after 1239 reset is all zeroes. For -R subtype ports, the value of this 1240 object cannot be changed directly. This value may be changed 1241 as a result of writing operation on the 1242 gBondBceRemoteDiscoveryCode object of remote BCE of -O 1243 subtype, connected to one of the local BCEs associated with 1244 the GBS. 1246 Discovery MUST be performed when the link is Down. 1247 Attempts to change this object MUST be rejected (in case of 1248 SNMP with the error inconsistentValue), if the link is Up or 1249 Initializing. 1251 This object maps to the TR-159 attribute 1252 aGroupDiscoveryCode." 1253 REFERENCE 1254 "[TR-159] 5.5.1.20; [802.3] 61.2.2.8.3, 61.2.2.8.4, 1255 45.2.6.6.1, 45.2.6.8, 61A.2" 1256 ::= { gBondPortConfEntry 3 } 1258 gBondTargetUpDataRate OBJECT-TYPE 1259 SYNTAX Unsigned32(0|1..10000000) 1260 UNITS "Kbps" 1261 MAX-ACCESS read-write 1262 STATUS current 1263 DESCRIPTION 1264 "A desired G.Bond port Data Rate in the upstream direction, 1265 in Kbps, to be achieved during initialization, under 1266 restrictions placed upon the member BCEs by their respective 1267 configuration settings. 1268 This object represents a sum of individual BCE upstream data 1269 rates, modified to compensate for fragmentation and 1270 encapsulation overhead (e.g., for an Ethernet service, the 1271 target data rate of 10Mbps SHALL allow lossless transmission 1272 of full-duplex 10Mbps Ethernet frame stream with minimal 1273 inter-frame gap). 1274 Note that the target upstream data rate may not be achieved 1275 during initialization (e.g., due to unavailability of required 1276 BCEs) or the initial bandwidth could deteriorate, so that the 1277 actual upstream data rate (gBondUpDataRate) could be less 1278 than gBondTargetUpDataRate. 1280 The value is limited above by 10 Gbps, to accomodate very 1281 high speed bonded xDSL interfaces (e.g. 32 x 100Mbps). 1283 The value between 1 and 10000000 indicates that the total 1284 upstream data rate of the G.Bond port after initialization 1285 SHALL be equal to the target data rate or less, if the target 1286 upstream data rate cannot be achieved under the restrictions 1287 configured for BCEs. In case the copper environment allows to 1288 achieve higher upstream data rate than that specified by this 1289 object, the excess capability SHALL be either converted to 1290 additional SNR margin or reclaimed by minimizing transmit 1291 power. 1293 The value of 0 means that the target data rate is not 1294 fixed and SHALL be set to the maximum attainable rate during 1295 initialization (Best Effort), under specified spectral 1296 restrictions and with desired SNR Margin per BCE. 1298 This object is read-write for the -O subtype G.Bond ports 1299 and irrelevant for the -R subtypes. 1301 Changing of the Target Upstream Data Rate MUST be performed 1302 when the link is Down. Attempts to change this object MUST be 1303 rejected (In case of SNMP with the error inconsistentValue), 1304 if the link is Up or Initializing. 1306 This object MUST be maintained in a persistent manner. 1308 This object maps to the TR-159 attribute 1309 aGroupTargetUpRate." 1310 REFERENCE 1311 "[TR-159] 5.5.1.17" 1313 ::= { gBondPortConfEntry 4 } 1315 gBondTargetDnDataRate OBJECT-TYPE 1316 SYNTAX Unsigned32(0|1..10000000) 1317 UNITS "Kbps" 1318 MAX-ACCESS read-write 1319 STATUS current 1320 DESCRIPTION 1321 "A desired G.Bond port Data Rate in the downstream direction, 1322 in Kbps, to be achieved during initialization, under 1323 restrictions placed upon the member BCEs by their respective 1324 configuration settings. 1325 This object represents a sum of individual BCE downstream data 1326 rates, modified to compensate for fragmentation and 1327 encapsulation overhead (e.g., for an Ethernet service, the 1328 target data rate of 10Mbps SHALL allow lossless transmission 1329 of full-duplex 10Mbps Ethernet frame stream with minimal 1330 inter-frame gap). 1331 Note that the target downstream data rate may not be achieved 1332 during initialization (e.g., due to unavailability of required 1333 BCEs) or the initial bandwidth could deteriorate, so that the 1334 actual downstream data rate (gBondDnDataRate) could be less 1335 than gBondTargetDnDataRate. 1337 The value is limited above by 10 Gbps, to accomodate very 1338 high speed bonded xDSL interfaces (e.g. 32 x 100Mbps). 1340 The value between 1 and 10000000 indicates that the total 1341 downstream data rate of the G.Bond port after initialization 1342 SHALL be equal to the target data rate or less, if the target 1343 downstream data rate cannot be achieved under the restrictions 1344 configured for BCEs. In case the copper environment allows to 1345 achieve higher downstream data rate than that specified by 1346 this object, the excess capability SHALL be either converted 1347 to additional SNR margin or reclaimed by minimizing transmit 1348 power. 1350 The value of 0 means that the target data rate is not 1351 fixed and SHALL be set to the maximum attainable rate during 1352 initialization (Best Effort), under specified spectral 1353 restrictions and with desired SNR Margin per BCE. 1355 This object is read-write for the -O subtype G.Bond ports 1356 and irrelevant for the -R subtypes. 1358 Changing of the Target Downstream Data Rate MUST be performed 1359 when the link is Down. Attempts to change this object MUST be 1360 rejected (In case of SNMP with the error inconsistentValue), 1361 if the link is Up or Initializing. 1363 This object MUST be maintained in a persistent manner. 1365 This object maps to the TR-159 attribute 1366 aGroupTargetDownRate." 1367 REFERENCE 1368 "[TR-159] 5.5.1.18" 1369 ::= { gBondPortConfEntry 5 } 1371 gBondThreshLowUpRate OBJECT-TYPE 1372 SYNTAX Unsigned32(1..10000000) 1373 UNITS "Kbps" 1374 MAX-ACCESS read-write 1375 STATUS current 1376 DESCRIPTION 1377 "This object configures the G.Bond port low upstream rate 1378 crossing alarm threshold. When the current value of 1379 gBondUpDataRate for this port reaches/drops below or exceeds 1380 this threshold, an gBondLowUpRateCrossing notification MAY be 1381 generated if enabled by gBondLowRateCrossingEnable. 1383 This object is read-write for the -O subtype G.Bond ports 1384 and irrelevant for the -R subtypes. 1386 This object MUST be maintained in a persistent manner. 1388 This object maps to the TR-159 attribute 1389 aGroupthreshLowUpRate." 1390 REFERENCE 1391 "[TR-159] 5.5.1.21" 1392 ::= { gBondPortConfEntry 6 } 1394 gBondThreshLowDnRate OBJECT-TYPE 1395 SYNTAX Unsigned32(1..10000000) 1396 UNITS "Kbps" 1397 MAX-ACCESS read-write 1398 STATUS current 1399 DESCRIPTION 1400 "This object configures the G.Bond port low downstream rate 1401 crossing alarm threshold. When the current value of 1402 gBondDnDataRate for this port reaches/drops below or exceeds 1403 this threshold, an gBondLowDnRateCrossing notification MAY 1404 be generated if enabled by gBondLowRateCrossingEnable. 1406 This object is read-write for the -O subtype G.Bond ports 1407 and irrelevant for the -R subtypes. 1409 This object MUST be maintained in a persistent manner. 1411 This object maps to the TR-159 attribute 1412 aGroupThreshDownUpRate." 1413 REFERENCE 1414 "[TR-159] 5.5.1.22" 1415 ::= { gBondPortConfEntry 7 } 1417 gBondLowRateCrossingEnable OBJECT-TYPE 1418 SYNTAX TruthValue 1419 MAX-ACCESS read-write 1420 STATUS current 1421 DESCRIPTION 1422 "Indicates whether gBondLowUpRateCrossing and 1423 gBondLowDnRateCrossing notifications should be generated 1424 for this interface. 1426 Value of true(1) indicates that the notifications are enabled. 1427 Value of false(2) indicates that the notifications are 1428 disabled. 1430 This object is read-write for the -O subtype G.Bond ports 1431 and irrelevant for the -R subtypes. 1433 This object MUST be maintained in a persistent manner. 1435 This object maps to the TR-159 attribute 1436 aGroupLowRateCrossingEnable." 1437 REFERENCE 1438 "[TR-159] 5.5.1.23" 1439 ::= { gBondPortConfEntry 8 } 1441 gBondPerfTcaConfProfile OBJECT-TYPE 1442 SYNTAX SnmpAdminString (SIZE(1..32)) 1443 MAX-ACCESS read-write 1444 STATUS current 1445 DESCRIPTION 1446 "The value of this object is the index of the row in the GBS 1447 port Alarm Configuration Profile Table for Performance Monitoring 1448 Threshold Crossing Alerts - gBondPortAlarmConfProfileTable, 1449 which applies to this GBS port. 1451 This object MUST be maintained in a persistent manner." 1452 DEFVAL { "DEFVAL" } 1453 ::= { gBondPortConfEntry 9 } 1455 gBondPerfTcaEnable OBJECT-TYPE 1456 SYNTAX TruthValue 1457 MAX-ACCESS read-write 1458 STATUS current 1459 DESCRIPTION 1460 "Indicates whether gBondPerfTca*Crossing set of notifications 1461 should be generated for this interface. 1463 Value of true(1) indicates that the notifications are enabled. 1464 Value of false(2) indicates that the notifications are 1465 disabled. 1467 This object MUST be maintained in a persistent manner. 1469 This object maps to the TR-159 attribute aGroupPerfTcaEnable." 1470 REFERENCE 1471 "[TR-159] 5.5.1.38" 1472 ::= { gBondPortConfEntry 10 } 1474 gBondPortCapabilityTable OBJECT-TYPE 1475 SYNTAX SEQUENCE OF GBondPortCapabilityEntry 1476 MAX-ACCESS not-accessible 1477 STATUS current 1478 DESCRIPTION 1479 "Table for Capabilities of G.Bond Ports. Entries in this table 1480 MUST be maintained in a persistent manner" 1481 ::= { gBondPort 2 } 1483 gBondPortCapabilityEntry OBJECT-TYPE 1484 SYNTAX GBondPortCapabilityEntry 1485 MAX-ACCESS not-accessible 1486 STATUS current 1487 DESCRIPTION 1488 "An entry in the G.Bond Port Capability table. 1489 Each entry represents an G.Bond port indexed by the ifIndex. 1490 Note that a G.Bond GBS port runs on top of a single 1491 or multiple BCE port(s), which are also indexed by ifIndex." 1492 INDEX { ifIndex } 1493 ::= { gBondPortCapabilityTable 1 } 1495 GBondPortCapabilityEntry ::= 1496 SEQUENCE { 1497 gBondSchemesSupported GBondSchemeList, 1498 gBondPeerSchemesSupported GBondSchemeList, 1499 gBondCapacity Unsigned32, 1500 gBondPeerCapacity Unsigned32 1501 } 1503 gBondSchemesSupported OBJECT-TYPE 1504 SYNTAX GBondSchemeList 1505 MAX-ACCESS read-only 1506 STATUS current 1507 DESCRIPTION 1508 "Bonding Capability of the G.Bond port (GBS). This is a 1509 read-only bitmap of the possible bonding schemes supported by 1510 the GBS. The various bit-positions are: 1511 g9981(1) - GBS is capable of G.998.1 bonding 1512 g9982(2) - GBS is capable of G.998.2 bonding 1513 g9983(3) - GBS is capable of G.998.3 bonding 1515 Note that for ports supporting multiple bonding schemes the 1516 actual administrative scheme is set via gBondAdminScheme 1517 object. The current operating bonding scheme is reflected in 1518 the gBondOperScheme. 1520 This object maps to the TR-159 attribute 1521 aGroupBondSchemesSupported." 1522 REFERENCE 1523 "[TR-159] 5.5.1.2" 1524 ::= { gBondPortCapabilityEntry 1 } 1526 gBondPeerSchemesSupported OBJECT-TYPE 1527 SYNTAX GBondSchemeList 1528 MAX-ACCESS read-only 1529 STATUS current 1530 DESCRIPTION 1531 "Bonding Capability of the peer G.Bond port (GBS). This is a 1532 read-only bitmap of the possible bonding schemes supported by 1533 the link partner GBS. The various bit-positions are: 1534 unknown(0) - GBS does not support bonding or 1535 the peer unit could not be reached. 1536 g9981(1) - GBS is capable of G.998.1 bonding 1537 g9982(2) - GBS is capable of G.998.2 bonding 1538 g9983(3) - GBS is capable of G.998.3 bonding 1540 Note that for ports supporting multiple bonding schemes the 1541 actual administrative scheme is set via gBondPeerAdminScheme 1542 object. The current operating bonding scheme is reflected in 1543 the gBondPeerOperScheme. 1545 This object maps to the TR-159 attribute 1546 aGroupBondPeerSchemesSupported." 1547 REFERENCE 1548 "[TR-159] 5.5.1.3" 1549 ::= { gBondPortCapabilityEntry 2 } 1551 gBondCapacity OBJECT-TYPE 1552 SYNTAX Unsigned32 (1..32) 1553 MAX-ACCESS read-only 1554 STATUS current 1555 DESCRIPTION 1556 "Number of BCEs that can be aggregated by the local GBS. 1557 The number of BCEs currently assigned to a particular G.Bond 1558 port (gBondNumBCEs) is never greater than gBondCapacity. 1560 This object maps to the TR-159 attribute aGroupCapacity." 1561 REFERENCE 1562 "[TR-159] 5.5.1.12" 1563 ::= { gBondPortCapabilityEntry 3 } 1565 gBondPeerCapacity OBJECT-TYPE 1566 SYNTAX Unsigned32 (0|1..32) 1567 MAX-ACCESS read-only 1568 STATUS current 1569 DESCRIPTION 1570 "Number of BCEs that can be aggregated by the peer GBS port. 1571 Value of 0 is returned when peer Bonding Capacity is unknown 1572 (peer cannot be reached). 1574 This object maps to the TR-159 attribute aGroupPeerCapacity." 1575 REFERENCE 1576 "[TR-159] 5.5.1.13" 1577 ::= { gBondPortCapabilityEntry 4 } 1579 gBondPortStatusTable OBJECT-TYPE 1580 SYNTAX SEQUENCE OF GBondPortStatusEntry 1581 MAX-ACCESS not-accessible 1582 STATUS current 1583 DESCRIPTION 1584 "This table provides overall status information of G.Bond 1585 ports, complementing the generic status information from the 1586 ifTable of IF-MIB. Additional status information about 1587 connected BCEs is available from the relevant line MIBs 1589 This table contains live data from the equipment. As such, 1590 it is NOT persistent." 1591 ::= { gBondPort 3 } 1593 gBondPortStatusEntry OBJECT-TYPE 1594 SYNTAX GBondPortStatusEntry 1595 MAX-ACCESS not-accessible 1596 STATUS current 1597 DESCRIPTION 1598 "An entry in the G.Bond Port Status table. 1599 Each entry represents an G.Bond port indexed by the ifIndex. 1600 Note that an G.Bond GBS port runs on top of a single 1601 or multiple BCE port(s), which are also indexed by ifIndex." 1602 INDEX { ifIndex } 1603 ::= { gBondPortStatusTable 1 } 1605 GBondPortStatusEntry ::= 1606 SEQUENCE { 1607 gBondOperScheme GBondScheme, 1608 gBondPeerOperScheme GBondScheme, 1609 gBondUpDataRate Gauge32, 1610 gBondDnDataRate Gauge32, 1611 gBondFltStatus BITS, 1612 gBondPortSide INTEGER, 1613 gBondNumBCEs Unsigned32 1614 } 1616 gBondOperScheme OBJECT-TYPE 1617 SYNTAX GBondScheme 1618 MAX-ACCESS read-only 1619 STATUS current 1620 DESCRIPTION 1621 "Current operating bonding scheme of a G.Bond port. 1622 The possible values are: 1623 g9981(1) - G.998.1 bonding 1624 g9982(2) - G.998.2 bonding 1625 g9983(3) - G.998.3 bonding 1627 This object maps to the TR-159 attribute 1628 aGroupOperBondScheme." 1629 REFERENCE 1630 "[TR-159] 5.5.1.4" 1631 ::= { gBondPortStatusEntry 1 } 1633 gBondPeerOperScheme OBJECT-TYPE 1634 SYNTAX GBondScheme 1635 MAX-ACCESS read-only 1636 STATUS current 1637 DESCRIPTION 1638 "Curent operating bonding scheme of a G.Bond port link 1639 partner. 1640 The possible values are: 1641 unknown(0) - peer cannot be reached due to the link 1642 state 1643 g9981(1) - G.998.1 bonding 1644 g9982(2) - G.998.2 bonding 1645 g9983(3) - G.998.3 bonding 1647 This object maps to the TR-159 attribute 1648 aGroupPeerOperBondScheme." 1649 REFERENCE 1650 "[TR-159] 5.5.1.5" 1651 ::= { gBondPortStatusEntry 2 } 1653 gBondUpDataRate OBJECT-TYPE 1654 SYNTAX Gauge32 1655 UNITS "bps" 1656 MAX-ACCESS read-only 1657 STATUS current 1658 DESCRIPTION 1659 "A current G.Bond port operational Data Rate in the upstream 1660 direction, in bps. 1661 This object represents an estimation of the sum of individual 1662 BCE upstream data rates, modified to compensate for 1663 fragmentation and encapsulation overhead (e.g., for an 1664 Ethernet service, the target data rate of 10Mbps SHALL allow 1665 lossless transmission of full-duplex 10Mbps Ethernet frame 1666 stream with minimal inter-frame gap). 1668 Note that for symmetrical interfaces gBondUpDataRate == 1669 gBondDnDataRate == ifSpeed. 1671 This object maps to the TR-159 attribute aGroupUpRate." 1672 REFERENCE 1673 "[TR-159] 5.5.1.15" 1674 ::= { gBondPortStatusEntry 3 } 1676 gBondDnDataRate OBJECT-TYPE 1677 SYNTAX Gauge32 1678 UNITS "bps" 1679 MAX-ACCESS read-only 1680 STATUS current 1681 DESCRIPTION 1682 "A current G.Bond port operational Data Rate in the downstream 1683 direction, in bps. 1684 This object represents an estimation of the sum of individual 1685 BCE downstream data rates, modified to compensate for 1686 fragmentation and encapsulation overhead (e.g., for an 1687 Ethernet service, the target data rate of 10Mbps SHALL allow 1688 lossless transmission of full-duplex 10Mbps Ethernet frame 1689 stream with minimal inter-frame gap). 1691 Note that for symmetrical interfaces gBondUpDataRate == 1692 gBondDnDataRate == ifSpeed. 1694 This object maps to the TR-159 attribute aGroupDownRate." 1696 REFERENCE 1697 "[TR-159] 5.5.1.16" 1698 ::= { gBondPortStatusEntry 4 } 1700 gBondFltStatus OBJECT-TYPE 1701 SYNTAX BITS { 1702 noPeer(0), 1703 peerPowerLoss(1), 1704 peerBondSchemeMismatch(2), 1705 bceSubTypeMismatch(3), 1706 lowRate(4) 1707 } 1708 MAX-ACCESS read-only 1709 STATUS current 1710 DESCRIPTION 1711 "G.Bond (GBS) port Fault Status. This is a bitmap of possible 1712 conditions. The various bit positions are: 1713 noPeer - peer GBS cannot be reached (e.g., 1714 no BCEs attached, all BCEs are Down 1715 etc.). 1716 peerPowerLoss - peer GBS has indicated impending unit 1717 failure due to loss of local power 1718 ('Dying Gasp'). 1719 peerBondSchemeMismatch - operating bonding scheme of a peer 1720 GBS is different from the local one. 1721 bceSubTypeMismatch - local BCEs in the aggregation group 1722 are not of the same sub-type, e.g., 1723 some BCEs in the local device are -O 1724 while others are -R subtype. 1725 lowRate - gBondUpRate/gBondDnRate of the port 1726 has reached or dropped below 1727 gBondThreshLowUpRate/ 1728 gBondThreshLowUpRate. 1730 This object is intended to supplement ifOperStatus object 1731 in IF-MIB and ifMauMediaAvailable in MAU-MIB. 1733 This object maps to the TR-159 attribute aGroupStatus." 1734 REFERENCE 1735 "[TR-159] 5.5.1.9; IF-MIB, ifOperStatus; MAU-MIB, 1736 ifMauMediaAvailable" 1737 ::= { gBondPortStatusEntry 5 } 1739 gBondPortSide OBJECT-TYPE 1740 SYNTAX INTEGER { 1741 subscriber(1), 1742 office(2), 1743 unknown(3) 1744 } 1745 MAX-ACCESS read-only 1746 STATUS current 1747 DESCRIPTION 1748 "G.Bond port mode of operation (subtype). 1749 The value of 'subscriber' indicates the port is designated as 1750 '-R' subtype (all BCEs assigned to this port are of subtype 1751 '-R'). 1752 The value of the 'office' indicates that the port is 1753 designated as '-O' subtype (all BCEs assigned to this port are 1754 of subtype '-O'). 1755 The value of 'unknown' indicates that the port has no assigned 1756 BCEs yet or that the assigned BCEs are not of the same side 1757 (subTypeBCEMismatch). 1759 This object maps to the TR-159 attribute aGroupEnd." 1760 REFERENCE 1761 "[TR-159] 5.5.1.11" 1762 ::= { gBondPortStatusEntry 6 } 1764 gBondNumBCEs OBJECT-TYPE 1765 SYNTAX Unsigned32 (0..32) 1766 MAX-ACCESS read-only 1767 STATUS current 1768 DESCRIPTION 1769 "Number of BCEs that is currently aggregated by the local GBS 1770 (assigned to the G.Bond port using ifStackTable). 1771 This number is never greater than gBondCapacity. 1773 This object SHALL be automatically incremented or decremented 1774 when a BCE is added or deleted to/from the G.Bond port using 1775 ifStackTable. 1777 This object maps to the TR-159 attribute aGroupNumChannels" 1778 REFERENCE 1779 "[TR-159] 5.5.1.14" 1780 ::= { gBondPortStatusEntry 7 } 1782 -- Performance Monitoring group 1784 gBondPortPM OBJECT IDENTIFIER ::= { gBondPort 4 } 1786 gBondPortPerfCurrTable OBJECT-TYPE 1787 SYNTAX SEQUENCE OF GBondPortPerfCurrEntry 1788 MAX-ACCESS not-accessible 1789 STATUS current 1790 DESCRIPTION 1791 "This table contains current Performance Monitoring (PM) 1792 information for a GBS port. This table contains live data from 1793 the equipment and as such is NOT persistent." 1794 ::= { gBondPortPM 1 } 1796 gBondPortPerfCurrEntry OBJECT-TYPE 1797 SYNTAX GBondPortPerfCurrEntry 1798 MAX-ACCESS not-accessible 1799 STATUS current 1800 DESCRIPTION 1801 "An entry in the G.Bond Port PM table. 1802 Each entry represents an G.Bond port indexed by the ifIndex. 1803 Note that a G.Bond GBS port runs on top of a single 1804 or multiple BCE port(s), which are also indexed by ifIndex." 1805 INDEX { ifIndex } 1806 ::= { gBondPortPerfCurrTable 1 } 1808 GBondPortPerfCurrEntry ::= 1809 SEQUENCE { 1810 gBondPerfES HCPerfTotalCount, 1811 gBondPerfSES HCPerfTotalCount, 1812 gBondPerfUAS HCPerfTotalCount, 1813 gBondPerf15MinValidIntervals HCPerfValidIntervals, 1814 gBondPerf15MinInvalidIntervals HCPerfInvalidIntervals, 1815 gBondPerfCurr15MinTimeElapsed HCPerfTimeElapsed, 1816 gBondPerfCurr15MinES HCPerfCurrentCount, 1817 gBondPerfCurr15MinSES HCPerfCurrentCount, 1818 gBondPerfCurr15MinUAS HCPerfCurrentCount, 1819 gBondPerf1DayValidIntervals Unsigned32, 1820 gBondPerf1DayInvalidIntervals Unsigned32, 1821 gBondPerfCurr1DayTimeElapsed HCPerfTimeElapsed, 1822 gBondPerfCurr1DayES HCPerfCurrentCount, 1823 gBondPerfCurr1DaySES HCPerfCurrentCount, 1824 gBondPerfCurr1DayUAS HCPerfCurrentCount 1825 } 1827 gBondPerfES OBJECT-TYPE 1828 SYNTAX HCPerfTotalCount 1829 MAX-ACCESS read-only 1830 STATUS current 1831 DESCRIPTION 1832 "A read-only count of Errored Seconds (ES) on the GBS since the 1833 BTU was last restarted. 1835 An Errored Second for a G.998.x interface is defined as a count 1836 of 1-second intervals during which one or more GBS errors are 1837 declared. The errors are specific for each bonding scheme, e.g. 1839 - lost cells for the ATM bonding; 1840 - lost or discarded (due to an error or a buffer overflow) 1841 fragments for the Ethernet bonding; 1842 - CRC4, CRC6 or CRC8 errors for the TDIM bonding 1843 This object is inhibited during Unavailable Seconds (UAS). 1845 This object maps to the TR-159 attribute aGroupPerfES." 1846 REFERENCE 1847 "[TR-159] 5.5.1.29" 1848 ::= { gBondPortPerfCurrEntry 1 } 1850 gBondPerfSES OBJECT-TYPE 1851 SYNTAX HCPerfTotalCount 1852 MAX-ACCESS read-only 1853 STATUS current 1854 DESCRIPTION 1855 "A read-only count of Severely Errored Seconds (SES) on the GBS 1856 since the BTU was last restarted. 1858 A Severely Errored Second for a G.998.x interface is defined as 1859 a count of 1-second intervals during which GBS errors cause at 1860 least 1% traffic loss of the nominal bonded link rate or at 1861 least 12ms for the TDM traffic. The exact definition is specific 1862 for each bonding scheme, e.g. 1863 - 234 lost cells for the ATM bonding with 10Mbps nominal link 1864 rate 1865 - 60 lost/discarded fragments for the Ethernet bonding with 1866 10Mbps nominal link rate and fixed 192 Byte-long fragment 1867 size. 1868 - 6 or more CRC4, one or more CRC6 or one or more CRC8 errors 1869 for the TDM bonding 1870 This object is inhibited during Unavailable Seconds (UAS). 1872 This object maps to the TR-159 attribute aGroupPerfSES." 1873 REFERENCE 1874 "[TR-159] 5.5.1.30" 1875 ::= { gBondPortPerfCurrEntry 2 } 1877 gBondPerfUAS OBJECT-TYPE 1878 SYNTAX HCPerfTotalCount 1879 MAX-ACCESS read-only 1880 STATUS current 1881 DESCRIPTION 1882 "A read-only count of Unavailable Seconds (UAS) on the GBS since 1883 the BTU was last restarted. 1885 An Unavailable Second for a G.998.x interface is defined as a 1886 count of 1-second intervals during which the bonded link is 1887 unavailable. The G.998.x link becomes unavailable at the onset 1888 of 10 contiguous SESs. The 10 SESs are included in the 1889 unavailable time. Once unavailable, the G.998.x line becomes 1890 available at the onset of 10 contiguous seconds with no SESs. 1891 The 10 seconds with no SESs are excluded from unavailable time. 1893 This object maps to the TR-159 attribute aGroupPerfUAS." 1894 REFERENCE 1895 "[TR-159] 5.5.1.31" 1896 ::= { gBondPortPerfCurrEntry 3 } 1898 gBondPerf15MinValidIntervals OBJECT-TYPE 1899 SYNTAX HCPerfValidIntervals 1900 MAX-ACCESS read-only 1901 STATUS current 1902 DESCRIPTION 1903 "A read-only number of 15-minute intervals for which data was 1904 collected. The value of this object will be 96 or the maximum 1905 number of 15-minute history intervals collected by the 1906 implementation unless the measurement was (re-)started recently, 1907 in which case the value will be the number of complete 15 1908 minutes intervals for which there are at least some data. 1909 In certain cases it is possible that some intervals are 1910 unavailable. In this case, this object reports the maximum 1911 interval number for which data is available. 1913 This object maps to the TR-159 attribute 1914 aGroupPerf15MinValidIntervals." 1915 REFERENCE 1916 "[TR-159] 5.5.1.32" 1917 ::= { gBondPortPerfCurrEntry 4 } 1919 gBondPerf15MinInvalidIntervals OBJECT-TYPE 1920 SYNTAX HCPerfInvalidIntervals 1921 MAX-ACCESS read-only 1922 STATUS current 1923 DESCRIPTION 1924 "A read-only number of 15-minute intervals for which data was 1925 not always available. The value will typically be zero except in 1926 cases where the data for some intervals are not available. 1928 This object maps to the TR-159 attribute 1929 aGroupPerf15MinInvalidIntervals." 1930 REFERENCE 1931 "[TR-159] 5.5.1.33" 1932 ::= { gBondPortPerfCurrEntry 5 } 1934 gBondPerfCurr15MinTimeElapsed OBJECT-TYPE 1935 SYNTAX HCPerfTimeElapsed 1936 MAX-ACCESS read-only 1937 STATUS current 1938 DESCRIPTION 1939 "A read-only count of seconds that have elapsed since the 1940 beginning of the current 15-minute performance history interval. 1942 This object maps to the TR-159 attribute 1943 aGroupPerfCurr15MinTimeElapsed." 1944 REFERENCE 1945 "[TR-159] 5.5.1.34" 1946 ::= { gBondPortPerfCurrEntry 6 } 1948 gBondPerfCurr15MinES OBJECT-TYPE 1949 SYNTAX HCPerfCurrentCount 1950 MAX-ACCESS read-only 1951 STATUS current 1952 DESCRIPTION 1953 "A read-only count of Errored Seconds (ES) on the GBS in the 1954 current 15-minute performance history interval. 1956 This object maps to the TR-159 attribute aGroupPerfCurr15MinES." 1957 REFERENCE 1958 "[TR-159] 5.5.1.35" 1959 ::= { gBondPortPerfCurrEntry 7 } 1961 gBondPerfCurr15MinSES OBJECT-TYPE 1962 SYNTAX HCPerfCurrentCount 1963 MAX-ACCESS read-only 1964 STATUS current 1965 DESCRIPTION 1966 "A read-only count of Severely Errored Seconds (ES) on the GBS 1967 in the current 15-minute performance history interval. 1969 This object maps to the TR-159 attribute aGroupPerfCurr15MinSES." 1970 REFERENCE 1971 "[TR-159] 5.5.1.36" 1972 ::= { gBondPortPerfCurrEntry 8 } 1974 gBondPerfCurr15MinUAS OBJECT-TYPE 1975 SYNTAX HCPerfCurrentCount 1976 MAX-ACCESS read-only 1977 STATUS current 1978 DESCRIPTION 1979 "A read-only count of Unavailable Seconds (UAS) on the GBS in 1980 the current 15-minute performance history interval. 1982 This object maps to the TR-159 attribute aGroupPerfCurr15MinUAS." 1984 REFERENCE 1985 "[TR-159] 5.5.1.37" 1986 ::= { gBondPortPerfCurrEntry 9 } 1988 gBondPerf1DayValidIntervals OBJECT-TYPE 1989 SYNTAX Unsigned32 (0..7) 1990 MAX-ACCESS read-only 1991 STATUS current 1992 DESCRIPTION 1993 "A read-only number of 1-day intervals for which data was 1994 collected. The value of this object will be 7 or the maximum 1995 number of 1-day history intervals collected by the 1996 implementation unless the measurement was (re-)started recently, 1997 in which case the value will be the number of complete 1-day 1998 intervals for which there are at least some data. 1999 In certain cases it is possible that some intervals are 2000 unavailable. In this case, this object reports the maximum 2001 interval number for which data is available. 2003 This object maps to the TR-159 attribute 2004 aGroupPerf1DayValidIntervals." 2005 REFERENCE 2006 "[TR-159] 5.5.1.45" 2007 ::= { gBondPortPerfCurrEntry 10 } 2009 gBondPerf1DayInvalidIntervals OBJECT-TYPE 2010 SYNTAX Unsigned32 (0..7) 2011 MAX-ACCESS read-only 2012 STATUS current 2013 DESCRIPTION 2014 "A read-only number of 1-day intervals for which data was 2015 not always available. The value will typically be zero except in 2016 cases where the data for some intervals are not available. 2018 This object maps to the TR-159 attribute 2019 aGroupPerf1DayInvalidIntervals." 2020 REFERENCE 2021 "[TR-159] 5.5.1.46" 2022 ::= { gBondPortPerfCurrEntry 11 } 2024 gBondPerfCurr1DayTimeElapsed OBJECT-TYPE 2025 SYNTAX HCPerfTimeElapsed 2026 MAX-ACCESS read-only 2027 STATUS current 2028 DESCRIPTION 2029 "A read-only count of seconds that have elapsed since the 2030 beginning of the current 1-day performance history interval. 2032 This object maps to the TR-159 attribute 2033 aGroupPerfCurr1DayTimeElapsed." 2034 REFERENCE 2035 "[TR-159] 5.5.1.47" 2036 ::= { gBondPortPerfCurrEntry 12 } 2038 gBondPerfCurr1DayES OBJECT-TYPE 2039 SYNTAX HCPerfCurrentCount 2040 MAX-ACCESS read-only 2041 STATUS current 2042 DESCRIPTION 2043 "A read-only count of Errored Seconds (ES) on the GBS in the 2044 current 1-day performance history interval. 2046 This object maps to the TR-159 attribute aGroupPerfCurr1DayES." 2047 REFERENCE 2048 "[TR-159] 5.5.1.48" 2049 ::= { gBondPortPerfCurrEntry 13 } 2051 gBondPerfCurr1DaySES OBJECT-TYPE 2052 SYNTAX HCPerfCurrentCount 2053 MAX-ACCESS read-only 2054 STATUS current 2055 DESCRIPTION 2056 "A read-only count of Severely Errored Seconds (ES) on the GBS 2057 in the current 1-day performance history interval. 2059 This object maps to the TR-159 attribute aGroupPerfCurr1DaySES." 2060 REFERENCE 2061 "[TR-159] 5.5.1.49" 2062 ::= { gBondPortPerfCurrEntry 14 } 2064 gBondPerfCurr1DayUAS OBJECT-TYPE 2065 SYNTAX HCPerfCurrentCount 2066 MAX-ACCESS read-only 2067 STATUS current 2068 DESCRIPTION 2069 "A read-only count of Unavailable Seconds (UAS) on the GBS in 2070 the current 1-day performance history interval. 2072 This object maps to the TR-159 attribute aGroupPerfCurr1DayUAS." 2073 REFERENCE 2074 "[TR-159] 5.5.1.50" 2075 ::= { gBondPortPerfCurrEntry 15 } 2077 -- PM history: 15-min buckets 2079 gBondPortPerf15MinTable OBJECT-TYPE 2080 SYNTAX SEQUENCE OF GBondPortPerf15MinEntry 2081 MAX-ACCESS not-accessible 2082 STATUS current 2083 DESCRIPTION 2084 "This table contains historical 15-minute buckets of Performance 2085 Monitoring information for a GBS port (a row for each 15-minute 2086 interval, up to 96 intervals). 2087 Entries in this table MUST be maintained in a persistent manner." 2088 ::= { gBondPortPM 2 } 2090 gBondPortPerf15MinEntry OBJECT-TYPE 2091 SYNTAX GBondPortPerf15MinEntry 2092 MAX-ACCESS not-accessible 2093 STATUS current 2094 DESCRIPTION 2095 "An entry in the G.Bond Port historical 15-minute PM table. 2096 Each entry represents performance monitoring data for a GBS port, 2097 indexed by ifIndex, collected during a particular 15-minute 2098 interval, indexed by gBondPerf15MinIntervalIndex." 2099 INDEX { ifIndex, gBondPerf15MinIntervalIndex } 2100 ::= { gBondPortPerf15MinTable 1 } 2102 GBondPortPerf15MinEntry ::= 2103 SEQUENCE { 2104 gBondPerf15MinIntervalIndex Unsigned32, 2105 gBondPerf15MinIntervalMoniTime HCPerfTimeElapsed, 2106 gBondPerf15MinIntervalES HCPerfIntervalCount, 2107 gBondPerf15MinIntervalSES HCPerfIntervalCount, 2108 gBondPerf15MinIntervalUAS HCPerfIntervalCount, 2109 gBondPerf15MinIntervalValid TruthValue 2110 } 2112 gBondPerf15MinIntervalIndex OBJECT-TYPE 2113 SYNTAX Unsigned32 (1..96) 2114 MAX-ACCESS not-accessible 2115 STATUS current 2116 DESCRIPTION 2117 "Performance Data Interval number. 1 is the most recent previous 2118 interval; interval 96 is 24 hours ago. 2119 Intervals 2..96 are OPTIONAL. 2121 This object maps to the TR-159 attribute 2122 aGroupPerf15MinIntervalNumber." 2123 REFERENCE 2124 "[TR-159] 5.5.1.57" 2125 ::= { gBondPortPerf15MinEntry 1 } 2127 gBondPerf15MinIntervalMoniTime OBJECT-TYPE 2128 SYNTAX HCPerfTimeElapsed 2129 MAX-ACCESS read-only 2130 STATUS current 2131 DESCRIPTION 2132 "A read-only count of seconds over which the performance data 2133 was actually monitored. This value will be the same as the 2134 interval duration (900 seconds), except in a situation where 2135 performance data could not be collected for any reason." 2136 ::= { gBondPortPerf15MinEntry 2 } 2138 gBondPerf15MinIntervalES OBJECT-TYPE 2139 SYNTAX HCPerfIntervalCount 2140 MAX-ACCESS read-only 2141 STATUS current 2142 DESCRIPTION 2143 "A read-only count of Errored Seconds (ES) on the GBS in the 2144 15-minute performance history interval. 2146 This object maps to the TR-159 attribute 2147 aGroupPerf15MinIntervalES." 2148 REFERENCE 2149 "[TR-159] 5.5.1.59" 2150 ::= { gBondPortPerf15MinEntry 3 } 2152 gBondPerf15MinIntervalSES OBJECT-TYPE 2153 SYNTAX HCPerfIntervalCount 2154 MAX-ACCESS read-only 2155 STATUS current 2156 DESCRIPTION 2157 "A read-only count of Severely Errored Seconds (ES) on the GBS 2158 in the 15-minute performance history interval. 2160 This object maps to the TR-159 attribute 2161 aGroupPerf15MinIntervalSES." 2162 REFERENCE 2163 "[TR-159] 5.5.1.60" 2164 ::= { gBondPortPerf15MinEntry 4 } 2166 gBondPerf15MinIntervalUAS OBJECT-TYPE 2167 SYNTAX HCPerfIntervalCount 2168 MAX-ACCESS read-only 2169 STATUS current 2170 DESCRIPTION 2171 "A read-only count of Unavailable Seconds (UAS) on the GBS in 2172 the current 15-minute performance history interval. 2174 This object maps to the TR-159 attribute aGroupPerfCurr15MinUAS." 2175 REFERENCE 2176 "[TR-159] 5.5.1.61" 2177 ::= { gBondPortPerf15MinEntry 5 } 2179 gBondPerf15MinIntervalValid OBJECT-TYPE 2180 SYNTAX TruthValue 2181 MAX-ACCESS read-only 2182 STATUS current 2183 DESCRIPTION 2184 "A read-only object indicating whether or not this history 2185 bucket contains valid data. Valid bucket is reported as true(1) 2186 and invalid bucket as false(2). 2187 If this history bucket is invalid the BTU-C MUST NOT produce 2188 notifications based upon the value of the counters in this 2189 bucket. 2190 Note that an implementation may decide not to store invalid 2191 history buckets in its data base. In such case this object is 2192 not required as only valid history buckets are available while 2193 invalid history buckets are simply not in the data base. 2195 This object maps to the TR-159 attribute 2196 aGroupPerf15MinIntervalValid." 2197 REFERENCE 2198 "[TR-159] 5.5.1.58" 2199 ::= { gBondPortPerf15MinEntry 6 } 2201 -- PM history: 1-day buckets 2203 gBondPortPerf1DayTable OBJECT-TYPE 2204 SYNTAX SEQUENCE OF GBondPortPerf1DayEntry 2205 MAX-ACCESS not-accessible 2206 STATUS current 2207 DESCRIPTION 2208 "This table contains historical 1-day buckets of Performance 2209 Monitoring information for a GBS port (a row for each 1-day 2210 interval, up to 7 intervals). 2211 Entries in this table MUST be maintained in a persistent manner." 2212 ::= { gBondPortPM 3 } 2214 gBondPortPerf1DayEntry OBJECT-TYPE 2215 SYNTAX GBondPortPerf1DayEntry 2216 MAX-ACCESS not-accessible 2217 STATUS current 2218 DESCRIPTION 2219 "An entry in the G.Bond Port historical 1-day PM table. 2220 Each entry represents performance monitoring data for a GBS port, 2221 indexed by ifIndex, collected during a particular 1-day 2222 interval, indexed by gBondPerf1DayIntervalIndex." 2223 INDEX { ifIndex, gBondPerf1DayIntervalIndex } 2224 ::= { gBondPortPerf1DayTable 1 } 2226 GBondPortPerf1DayEntry ::= 2227 SEQUENCE { 2228 gBondPerf1DayIntervalIndex Unsigned32, 2229 gBondPerf1DayIntervalMoniTime HCPerfTimeElapsed, 2230 gBondPerf1DayIntervalES HCPerfIntervalCount, 2231 gBondPerf1DayIntervalSES HCPerfIntervalCount, 2232 gBondPerf1DayIntervalUAS HCPerfIntervalCount, 2233 gBondPerf1DayIntervalValid TruthValue 2234 } 2236 gBondPerf1DayIntervalIndex OBJECT-TYPE 2237 SYNTAX Unsigned32 (1..7) 2238 MAX-ACCESS not-accessible 2239 STATUS current 2240 DESCRIPTION 2241 "Performance Data Interval number. 1 is the most recent previous 2242 interval; interval 7 is 24 hours ago. 2243 Intervals 2..7 are OPTIONAL. 2245 This object maps to the TR-159 attribute 2246 aGroupPerf1DayIntervalNumber." 2247 REFERENCE 2248 "[TR-159] 5.5.1.62" 2249 ::= { gBondPortPerf1DayEntry 1 } 2251 gBondPerf1DayIntervalMoniTime OBJECT-TYPE 2252 SYNTAX HCPerfTimeElapsed 2253 MAX-ACCESS read-only 2254 STATUS current 2255 DESCRIPTION 2256 "A read-only count of seconds over which the performance data 2257 was actually monitored. This value will be the same as the 2258 interval duration (86400 seconds), except in a situation where 2259 performance data could not be collected for any reason. 2261 This object maps to the TR-159 attribute 2262 aGroupPerf1DayIntervalMoniSecs." 2263 REFERENCE 2264 "[TR-159] 5.5.1.64" 2265 ::= { gBondPortPerf1DayEntry 2 } 2267 gBondPerf1DayIntervalES OBJECT-TYPE 2268 SYNTAX HCPerfIntervalCount 2269 MAX-ACCESS read-only 2270 STATUS current 2271 DESCRIPTION 2272 "A read-only count of Errored Seconds (ES) on the GBS in the 2273 1-day performance history interval. 2275 This object maps to the TR-159 attribute 2276 aGroupPerf1DayIntervalES." 2277 REFERENCE 2278 "[TR-159] 5.5.1.65" 2279 ::= { gBondPortPerf1DayEntry 3 } 2281 gBondPerf1DayIntervalSES OBJECT-TYPE 2282 SYNTAX HCPerfIntervalCount 2283 MAX-ACCESS read-only 2284 STATUS current 2285 DESCRIPTION 2286 "A read-only count of Severely Errored Seconds (ES) on the GBS 2287 in the 1-day performance history interval. 2289 This object maps to the TR-159 attribute 2290 aGroupPerf1DayIntervalSES." 2291 REFERENCE 2292 "[TR-159] 5.5.1.66" 2293 ::= { gBondPortPerf1DayEntry 4 } 2295 gBondPerf1DayIntervalUAS OBJECT-TYPE 2296 SYNTAX HCPerfIntervalCount 2297 MAX-ACCESS read-only 2298 STATUS current 2299 DESCRIPTION 2300 "A read-only count of Unavailable Seconds (UAS) on the GBS in 2301 the current 1-day performance history interval. 2303 This object maps to the TR-159 attribute aGroupPerfCurr1DayUAS." 2304 REFERENCE 2305 "[TR-159] 5.5.1.67" 2306 ::= { gBondPortPerf1DayEntry 5 } 2308 gBondPerf1DayIntervalValid OBJECT-TYPE 2309 SYNTAX TruthValue 2310 MAX-ACCESS read-only 2311 STATUS current 2312 DESCRIPTION 2313 "A read-only object indicating whether or not this history 2314 bucket contains valid data. Valid bucket is reported as true(1) 2315 and invalid bucket as false(2). 2316 If this history bucket is invalid the BTU-C MUST NOT produce 2317 notifications based upon the value of the counters in this 2318 bucket. 2319 Note that an implementation may decide not to store invalid 2320 history buckets in its data base. In such case this object is 2321 not required as only valid history buckets are available while 2322 invalid history buckets are simply not in the data base. 2324 This object maps to the TR-159 attribute 2325 aGroupPerf1DayIntervalValid." 2326 REFERENCE 2327 "[TR-159] 5.5.1.63" 2328 ::= { gBondPortPerf1DayEntry 6 } 2330 -- Performance Monitoring TCA Configuration profile 2332 gBondPortPerfTcaConfProfileTable OBJECT-TYPE 2333 SYNTAX SEQUENCE OF GBondPortPerfTcaConfProfileEntry 2334 MAX-ACCESS not-accessible 2335 STATUS current 2336 DESCRIPTION 2337 "This table supports definitions of Performance Monitoring (PM) 2338 Threshold Crossing Alerts (TCA) configuration profiles for GBS 2339 ports. 2340 Entries in this table MUST be maintained in a persistent manner." 2341 ::= { gBondPortPM 4 } 2343 gBondPortPerfTcaConfProfileEntry OBJECT-TYPE 2344 SYNTAX GBondPortPerfTcaConfProfileEntry 2345 MAX-ACCESS not-accessible 2346 STATUS current 2347 DESCRIPTION 2348 "An entry in the GBS PM TCA Configuration table. 2349 Each entry corresponds to a single TCA configuration profile. 2350 Each profile contains a set of parameters for setting alarm 2351 thresholds for various performance attributes monitored at GBS 2352 ports. Profiles may be created/deleted using the row 2353 creation/deletion mechanism via 2354 gBondPerfTcaConfProfileRowStatus. If an active entry is 2355 referenced via gBondPerfTcaConfProfile, the entry MUST 2356 remain active until all references are removed. 2357 A default profile with an index of 'DEFVAL', will always exist 2358 and its parameters will be set to vendor specific values, 2359 unless otherwise specified in this document." 2360 INDEX { gBondPerfTcaConfProfileName } 2361 ::= { gBondPortPerfTcaConfProfileTable 1 } 2363 GBondPortPerfTcaConfProfileEntry ::= 2364 SEQUENCE { 2365 gBondPerfTcaConfProfileName SnmpAdminString, 2366 gBondPerfThreshold15MinES HCPerfIntervalThreshold, 2367 gBondPerfThreshold15MinSES HCPerfIntervalThreshold, 2368 gBondPerfThreshold15MinUAS HCPerfIntervalThreshold, 2369 gBondPerfThreshold1DayES GBondPerf1DayIntervalThreshold, 2370 gBondPerfThreshold1DaySES GBondPerf1DayIntervalThreshold, 2371 gBondPerfThreshold1DayUAS GBondPerf1DayIntervalThreshold, 2372 gBondPerfTcaConfProfileRowStatus RowStatus 2373 } 2375 gBondPerfTcaConfProfileName OBJECT-TYPE 2376 SYNTAX SnmpAdminString (SIZE(1..32)) 2377 MAX-ACCESS not-accessible 2378 STATUS current 2379 DESCRIPTION 2380 "This object is a unique index (name) associated with this 2381 GBS PM TCA profile." 2382 ::= { gBondPortPerfTcaConfProfileEntry 1 } 2384 gBondPerfThreshold15MinES OBJECT-TYPE 2385 SYNTAX HCPerfIntervalThreshold 2386 MAX-ACCESS read-create 2387 STATUS current 2388 DESCRIPTION 2389 "A desired threshold for the number of Errored Seconds (ES) 2390 within any given 15-minute performance data collection interval. 2391 If the number of ESs in a particular 15-minute collection 2392 interval reaches or exceeds this value, a 2393 gBondPerfTca15MinESCrossing notification MAY be generated if 2394 enabled by gBondPerfTcaEnable. 2395 At most one notification can be sent per interval. 2396 Setting this attribute to zero (default) effectively disables 2397 gBondPerfTca15MinESCrossing notification. 2399 This object maps to the TR-159 attribute 2400 aGroupPerfThreshold15MinES." 2401 REFERENCE 2402 "[TR-159] 5.5.1.39" 2403 ::= { gBondPortPerfTcaConfProfileEntry 2 } 2405 gBondPerfThreshold15MinSES OBJECT-TYPE 2406 SYNTAX HCPerfIntervalThreshold 2407 MAX-ACCESS read-create 2408 STATUS current 2409 DESCRIPTION 2410 "A desired threshold for the number of Severely Errored Seconds 2411 (SES) within any given 15-minute performance data collection 2412 interval. 2413 If the number of SESs in a particular 15-minute collection 2414 interval reaches or exceeds this value, a 2415 gBondPerfTca15MinSESCrossing notification MAY be generated if 2416 enabled by gBondPerfTcaEnable. 2417 At most one notification can be sent per interval. 2418 Setting this attribute to zero (default) effectively disables 2419 gBondPerfTca15MinSESCrossing notification. 2421 This object maps to the TR-159 attribute 2422 aGroupPerfThreshold15MinSES." 2423 REFERENCE 2424 "[TR-159] 5.5.1.40" 2425 ::= { gBondPortPerfTcaConfProfileEntry 3 } 2427 gBondPerfThreshold15MinUAS OBJECT-TYPE 2428 SYNTAX HCPerfIntervalThreshold 2429 MAX-ACCESS read-create 2430 STATUS current 2431 DESCRIPTION 2432 "A desired threshold for the number of Unavailable Seconds (UAS) 2433 within any given 15-minute performance data collection interval. 2434 If the number of UASs in a particular 15-minute collection 2435 interval reaches or exceeds this value, a 2436 gBondPerfTca15MinUASCrossing notification MAY be generated if 2437 enabled by gBondPerfTcaEnable. 2438 At most one notification can be sent per interval. 2439 Setting this attribute to zero (default) effectively disables 2440 gBondPerfTca15MinUASCrossing notification. 2442 This object maps to the TR-159 attribute 2443 aGroupPerfThreshold15MinUAS." 2444 REFERENCE 2445 "[TR-159] 5.5.1.41" 2446 ::= { gBondPortPerfTcaConfProfileEntry 4 } 2448 gBondPerfThreshold1DayES OBJECT-TYPE 2449 SYNTAX GBondPerf1DayIntervalThreshold 2450 MAX-ACCESS read-create 2451 STATUS current 2452 DESCRIPTION 2453 "A desired threshold for the number of Errored Seconds (ES) 2454 within any given 1-day performance data collection interval. 2455 If the number of ESs in a particular 1-day collection interval 2456 reaches or exceeds this value, a gBondPerfTca1DayESCrossing 2457 notification MAY be generated if enabled by gBondPerfTcaEnable. 2458 At most one notification can be sent per interval. 2459 Setting this attribute to zero (default) effectively disables 2460 gBondPerfTca1DayESCrossing notification. 2462 This object maps to the TR-159 attribute 2463 aGroupPerfThreshold1DayES." 2464 REFERENCE 2465 "[TR-159] 5.5.1.51" 2466 ::= { gBondPortPerfTcaConfProfileEntry 5 } 2468 gBondPerfThreshold1DaySES OBJECT-TYPE 2469 SYNTAX GBondPerf1DayIntervalThreshold 2470 MAX-ACCESS read-create 2471 STATUS current 2472 DESCRIPTION 2473 "A desired threshold for the number of Severely Errored Seconds 2474 (SES) within any given 1-day performance data collection 2475 interval. 2476 If the number of SESs in a particular 1-day collection interval 2477 reaches or exceeds this value, a gBondPerfTca1DaySESCrossing 2478 notification MAY be generated if enabled by gBondPerfTcaEnable. 2479 At most one notification can be sent per interval. 2480 Setting this attribute to zero (default) effectively disables 2481 gBondPerfTca1DaySESCrossing notification. 2483 This object maps to the TR-159 attribute 2484 aGroupPerfThreshold1DaySES." 2485 REFERENCE 2486 "[TR-159] 5.5.1.52" 2487 ::= { gBondPortPerfTcaConfProfileEntry 6 } 2489 gBondPerfThreshold1DayUAS OBJECT-TYPE 2490 SYNTAX GBondPerf1DayIntervalThreshold 2491 MAX-ACCESS read-create 2492 STATUS current 2493 DESCRIPTION 2494 "A desired threshold for the number of Unavailable Seconds (UAS) 2495 within any given 1-day performance data collection interval. 2496 If the number of UASs in a particular 1-day collection interval 2497 reaches or exceeds this value, a gBondPerfTca1DayUASCrossing 2498 notification MAY be generated if enabled by gBondPerfTcaEnable. 2499 At most one notification can be sent per interval. 2500 Setting this attribute to zero (default) effectively disables 2501 gBondPerfTca1DayUASCrossing notification. 2503 This object maps to the TR-159 attribute 2504 aGroupPerfThreshold1DayUAS." 2505 REFERENCE 2506 "[TR-159] 5.5.1.53" 2507 ::= { gBondPortPerfTcaConfProfileEntry 7 } 2509 gBondPerfTcaConfProfileRowStatus OBJECT-TYPE 2510 SYNTAX RowStatus 2511 MAX-ACCESS read-create 2512 STATUS current 2513 DESCRIPTION 2514 "This object controls the creation, modification, or deletion 2515 of the associated entry in the gBondPortPerfTcaConfProfileTable 2516 per the semantics of RowStatus. 2518 If an 'active' entry is referenced via gBondPerfTcaConfProfile 2519 instance(s), the entry MUST remain 'active'. 2521 An 'active' entry SHALL NOT be modified. In order to modify an 2522 existing entry, it MUST be taken out of service (by setting 2523 this object to 'notInService'), modified, and set 'active' 2524 again." 2525 ::= { gBondPortPerfTcaConfProfileEntry 8 } 2527 -- The BCE group 2529 gBondBceConfTable OBJECT-TYPE 2530 SYNTAX SEQUENCE OF GBondBceConfEntry 2531 MAX-ACCESS not-accessible 2532 STATUS current 2533 DESCRIPTION 2534 "Table for Configuration of G.Bond common aspects for the 2535 Bonding Channel Entity (BCE) ports (modems/channels). 2537 Entries in this table MUST be maintained in a persistent 2538 manner." 2539 ::= { gBondBce 1 } 2541 gBondBceConfEntry OBJECT-TYPE 2542 SYNTAX GBondBceConfEntry 2543 MAX-ACCESS not-accessible 2544 STATUS current 2545 DESCRIPTION 2546 "An entry in the G.Bond BCE Configuration table. 2547 Each entry represents common aspects of a G.Bond BCE port 2548 indexed by the ifIndex. Note that an G.Bond BCE port can be 2549 stacked below a single GBS port, also indexed by ifIndex, 2550 possibly together with other BCE ports if GAF is enabled." 2551 INDEX { ifIndex } 2552 ::= { gBondBceConfTable 1 } 2554 GBondBceConfEntry ::= 2555 SEQUENCE { 2556 gBondBceRemoteDiscoveryCode PhysAddress 2557 } 2559 gBondBceRemoteDiscoveryCode OBJECT-TYPE 2560 SYNTAX PhysAddress (SIZE(0|6)) 2561 MAX-ACCESS read-write 2562 STATUS current 2563 DESCRIPTION 2564 "A Remote Discovery Code of the BCE port at CO. 2565 A 6 octet long Discovery Code of the peer GBS connected via 2566 the BCE. 2567 Reading this object results in a Discovery Get operation. 2568 Setting this object to all zeroes results in a Discovery 2569 Clear_if_Same operation (the value of gBondDiscoveryCode 2570 at the peer GBS SHALL be the same as gBondDiscoveryCode of 2571 the local GBS associated with the BCE for the operation to 2572 succeed). 2573 Writing a non-zero value to this object results in a 2574 Discovery Set_if_Clear operation. 2575 A zero-length octet string SHALL be returned on an attempt to 2576 read this object when GAF aggregation is not enabled. 2578 This object is irrelevant in BCE-R port subtypes (CPE side): 2579 in this case a zero length octet string SHALL be returned on 2580 an attempt to read this object, writing to this object SHALL 2581 be rejected. 2583 Discovery MUST be performed when the link is Down. 2584 Attempts to change this object MUST be rejected (in case of 2585 SNMP with the error inconsistentValue), if the link is Up or 2586 Initializing. 2588 This object maps to the TR-159 attribute 2589 aLineRemoteDiscoveryCode." 2590 REFERENCE 2591 "[TR-159] 5.5.6.7" 2592 ::= { gBondBceConfEntry 1 } 2594 -- 2595 -- Conformance Statements 2596 -- 2598 gBondGroups OBJECT IDENTIFIER ::= { gBondConformance 1 } 2600 gBondCompliances OBJECT IDENTIFIER ::= { gBondConformance 2 } 2602 -- Object Groups 2604 gBondBasicGroup OBJECT-GROUP 2605 OBJECTS { 2606 gBondOperScheme, 2607 gBondUpDataRate, 2608 gBondDnDataRate, 2609 gBondTargetUpDataRate, 2610 gBondTargetDnDataRate, 2611 gBondOperScheme, 2612 gBondCapacity, 2613 gBondNumBCEs, 2614 gBondPortSide, 2615 gBondFltStatus 2616 } 2617 STATUS current 2618 DESCRIPTION 2619 "A collection of objects representing management information 2620 common to all types of G.Bond ports." 2621 ::= { gBondGroups 1 } 2623 gBondDiscoveryGroup OBJECT-GROUP 2624 OBJECTS { 2625 gBondPeerOperScheme, 2626 gBondPeerCapacity, 2627 gBondDiscoveryCode, 2628 gBondBceRemoteDiscoveryCode 2629 } 2630 STATUS current 2631 DESCRIPTION 2632 "A collection of objects supporting OPTIONAL G.Bond discovery 2633 in G.Bond ports." 2634 ::= { gBondGroups 2 } 2636 gBondMultiSchemeGroup OBJECT-GROUP 2637 OBJECTS { 2638 gBondSchemesSupported, 2639 gBondPeerSchemesSupported, 2640 gBondAdminScheme, 2641 gBondPeerAdminScheme 2642 } 2643 STATUS current 2644 DESCRIPTION 2645 "A collection of objects providing OPTIONAL management 2646 information for G.Bond ports supporting multiple bonding 2647 schemes." 2648 ::= { gBondGroups 3 } 2650 gBondTcaConfGroup OBJECT-GROUP 2651 OBJECTS { 2652 gBondThreshLowUpRate, 2653 gBondThreshLowDnRate, 2654 gBondLowRateCrossingEnable 2656 } 2657 STATUS current 2658 DESCRIPTION 2659 "A collection of objects required for configuration of alarm 2660 thresholds and notifications in G.Bond ports." 2661 ::= { gBondGroups 4 } 2663 gBondTcaNotificationGroup NOTIFICATION-GROUP 2664 NOTIFICATIONS { 2665 gBondLowUpRateCrossing, 2666 gBondLowDnRateCrossing 2667 } 2668 STATUS current 2669 DESCRIPTION 2670 "This group supports notifications of significant conditions 2671 (non-PM threshold crossing alerts) associated with G.Bond ports." 2672 ::= { gBondGroups 5 } 2674 gBondPerfCurrGroup OBJECT-GROUP 2675 OBJECTS { 2676 gBondPerfES, 2677 gBondPerfSES, 2678 gBondPerfUAS, 2679 gBondPerf15MinValidIntervals, 2680 gBondPerf15MinInvalidIntervals, 2681 gBondPerfCurr15MinTimeElapsed, 2682 gBondPerfCurr15MinES, 2683 gBondPerfCurr15MinSES, 2684 gBondPerfCurr15MinUAS, 2685 gBondPerf1DayValidIntervals, 2686 gBondPerf1DayInvalidIntervals, 2687 gBondPerfCurr1DayTimeElapsed, 2688 gBondPerfCurr1DayES, 2689 gBondPerfCurr1DaySES, 2690 gBondPerfCurr1DayUAS 2691 } 2692 STATUS current 2693 DESCRIPTION 2694 "A collection of objects supporting OPTIONAL current Performance 2695 Monitoring information for G.Bond ports." 2696 ::= { gBondGroups 6 } 2698 gBondPerf15MinGroup OBJECT-GROUP 2699 OBJECTS { 2700 gBondPerf15MinIntervalMoniTime, 2701 gBondPerf15MinIntervalES, 2702 gBondPerf15MinIntervalSES, 2703 gBondPerf15MinIntervalUAS, 2704 gBondPerf15MinIntervalValid 2705 } 2706 STATUS current 2707 DESCRIPTION 2708 "A collection of objects supporting OPTIONAL historical 2709 Performance Monitoring information for G.Bond ports, during 2710 previous 15-minute intervals ." 2711 ::= { gBondGroups 7 } 2713 gBondPerf1DayGroup OBJECT-GROUP 2714 OBJECTS { 2715 gBondPerf1DayIntervalMoniTime, 2716 gBondPerf1DayIntervalES, 2717 gBondPerf1DayIntervalSES, 2718 gBondPerf1DayIntervalUAS, 2719 gBondPerf1DayIntervalValid 2720 } 2721 STATUS current 2722 DESCRIPTION 2723 "A collection of objects supporting OPTIONAL historical 2724 Performance Monitoring information for G.Bond ports, during 2725 previous 1-day intervals ." 2726 ::= { gBondGroups 8 } 2728 gBondPerfTcaConfGroup OBJECT-GROUP 2729 OBJECTS { 2730 gBondPerfTcaConfProfile, 2731 gBondPerfTcaEnable, 2732 gBondPerfThreshold15MinES, 2733 gBondPerfThreshold15MinSES, 2734 gBondPerfThreshold15MinUAS, 2735 gBondPerfThreshold1DayES, 2736 gBondPerfThreshold1DaySES, 2737 gBondPerfThreshold1DayUAS, 2738 gBondPerfTcaConfProfileRowStatus 2739 } 2740 STATUS current 2741 DESCRIPTION 2742 "A collection of objects required for configuration of 2743 Performance Monitoring Threshold Crossing Alert notifications 2744 in G.Bond ports." 2745 ::= { gBondGroups 9 } 2747 gBondPerfTcaNotificationGroup NOTIFICATION-GROUP 2748 NOTIFICATIONS { 2749 gBondPerfTca15MinESCrossing, 2750 gBondPerfTca15MinSESCrossing, 2751 gBondPerfTca15MinUASCrossing, 2752 gBondPerfTca1DayESCrossing, 2753 gBondPerfTca1DaySESCrossing, 2754 gBondPerfTca1DayUASCrossing 2755 } 2756 STATUS current 2757 DESCRIPTION 2758 "This group supports notifications of performance monitoring 2759 thresholds crossing alerts associated with G.Bond ports." 2760 ::= { gBondGroups 10 } 2762 -- Compliance Statements 2764 gBondCompliance MODULE-COMPLIANCE 2765 STATUS current 2766 DESCRIPTION 2767 "The compliance statement for G.Bond interfaces. 2768 Compliance with the following external compliance statements 2769 is REQUIRED: 2771 MIB Module Compliance Statement 2772 ---------- -------------------- 2773 IF-MIB ifCompliance3 2775 Compliance with the following external compliance statements 2776 is OPTIONAL for implementations supporting bonding with 2777 flexible cross-connect between the GBS and BCE ports: 2779 MIB Module Compliance Statement 2780 ---------- -------------------- 2781 IF-INVERTED-STACK-MIB ifInvCompliance 2782 IF-CAP-STACK-MIB ifCapStackCompliance" 2784 MODULE -- this module 2785 MANDATORY-GROUPS { 2786 gBondBasicGroup, 2787 gBondTcaConfGroup, 2788 gBondTcaNotificationGroup 2789 } 2791 GROUP gBondDiscoveryGroup 2792 DESCRIPTION 2793 "Support for this group is only required for implementations 2794 supporting G.Bond Discovery function." 2796 GROUP gBondMultiSchemeGroup 2797 DESCRIPTION 2798 "Support for this group is only required for implementations 2799 supporting multiple bonding schemes." 2801 GROUP gBondPerfCurrGroup 2802 DESCRIPTION 2803 "Support for this group is only required for implementations 2804 supporting Performance Monitoring." 2806 GROUP gBondPerf15MinGroup 2807 DESCRIPTION 2808 "Support for this group is only required for implementations 2809 supporting historical Performance Monitoring." 2811 GROUP gBondPerf1DayGroup 2812 DESCRIPTION 2813 "Support for this group is only required for implementations 2814 supporting historical Performance Monitoring." 2816 GROUP gBondPerfTcaConfGroup 2817 DESCRIPTION 2818 "Support for this group is only required for implementations 2819 supporting Performance Monitoring Threshold Crossing Alert 2820 notifications." 2822 GROUP gBondPerfTcaNotificationGroup 2823 DESCRIPTION 2824 "Support for this group is only required for implementations 2825 supporting Performance Monitoring Threshold Crossing Alert 2826 notifications." 2828 ::= { gBondCompliances 1 } 2829 END 2831 7. Security Considerations 2833 There is a number of managed objects defined in the GBOND-MIB module 2834 that have a MAX-ACCESS clause of read-write or read-create. Most 2835 objects are writeable only when the link is Down. Writing to these 2836 objects can have potentially disruptive effects on network operation, 2837 for example: 2839 o Changing of gBondAdminScheme MAY lead to a potential locking of 2840 the link, if the peer device does not support desired bonding 2841 scheme. 2843 o Changing of gBondDiscoveryCode, before the discovery operation, 2844 MAY lead to a wrongful discovery, for example when two CO ports 2845 are connected to the same multi-channel RT port, while both CO 2846 ports have the same Discovery register value. 2848 o Changing GBS configuration parameters (e.g., profile of a GBS via 2849 gBondAdminProfile) MAY lead to anything from link quality and rate 2850 degradation to a complete link initialization failure, as ability 2851 of an G.Bond port to support a particular configuration depends on 2852 the copper environment. 2854 o Activation of a specific line/channel MAY cause a severe 2855 degradation of service for another G.Bond port, whose channel(s) 2856 MAY be affected by the cross-talk from the newly activated 2857 channel. 2859 o Removal of a channel from an operationally 'up' G.Bond port, 2860 aggregating several channels, MAY cause port's rate degradation 2862 The user of the GBOND-MIB module must therefore be aware that support 2863 for SET operations in a non-secure environment without proper 2864 protection can have a negative effect on network operations. 2866 The readable objects in the GBOND-MIB module (i.e., those with MAX- 2867 ACCESS other than not-accessible) may be considered sensitive in some 2868 environments since, collectively, they provide information about the 2869 performance of network interfaces and can reveal some aspects of 2870 their configuration. In particular, since a bonded xDSL port can be 2871 comprised of multiple Unshielded Twisted Pair (UTP) voice grade 2872 copper, located in the same bundle with other pairs belonging to 2873 another operator/customer, it is theoretically possible to evasdrop 2874 to a G.Bond transmission, simply by "listening" to a cross-talk from 2875 the bonded pairs, especially if the parameters of the G.Bond link in 2876 question are known. 2878 In such environments it is important to control also GET and NOTIFY 2879 access to these objects and possibly even to encrypt their values 2880 when sending them over the network via SNMP. 2882 SNMP versions prior to SNMPv3 did not include adequate security. 2883 Even if the network itself is secure (for example by using IPSec), 2884 even then, there is no control as to who on the secure network is 2885 allowed to access and GET/SET (read/change/create/delete) the objects 2886 in this MIB module. 2888 It is RECOMMENDED that implementers consider the security features as 2889 provided by the SNMPv3 framework (see [RFC3410], section 8), 2890 including full support for the SNMPv3 cryptographic mechanisms (for 2891 authentication and privacy). 2893 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2894 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2895 enable cryptographic security. It is then a customer/operator 2896 responsibility to ensure that the SNMP entity giving access to an 2897 instance of this MIB module is properly configured to give access to 2898 the objects only to those principals (users) that have legitimate 2899 rights to indeed GET or SET (change/create/delete) them. 2901 8. IANA Considerations 2903 Three new values of IANAifType: g9981, g9982 and g9982 SHALL be 2904 defined by the IANA [1] in the IANAifType-MIB module 2905 [IANAifType-MIB], before this document is published as an RFC. 2907 Additionally, an object identifier for gBondMIB MODULE-IDENTITY SHALL 2908 be allocated by IANA in the MIB-2 transmission sub-tree, before this 2909 document is published. 2911 9. Acknowledgments 2913 This document was produced by the [ADSLMIB] working group. 2915 10. References 2917 10.1. Normative References 2919 [RFC2119] Bradner, S., "Key words for use in 2920 RFCs to Indicate Requirement 2921 Levels", BCP 14, RFC 2119, 2922 March 1997. 2924 [RFC2578] McCloghrie, K., Ed., Perkins, D., 2925 Ed., and J. Schoenwaelder, Ed., 2926 "Structure of Management 2927 Information Version 2 (SMIv2)", 2928 STD 58, RFC 2578, April 1999. 2930 [RFC2579] McCloghrie, K., Ed., Perkins, D., 2931 Ed., and J. Schoenwaelder, Ed., 2932 "Textual Conventions for SMIv2", 2933 STD 58, RFC 2579, April 1999. 2935 [RFC2580] McCloghrie, K., Perkins, D., and 2936 J. Schoenwaelder, "Conformance 2937 Statements for SMIv2", STD 58, 2938 RFC 2580, April 1999. 2940 [RFC2863] McCloghrie, K. and F. Kastenholz, 2941 "The Interfaces Group MIB", 2942 RFC 2863, June 2000. 2944 [RFC3411] Harrington, D., Presuhn, R., and 2945 B. Wijnen, "An Architecture for 2946 Describing Simple Network 2947 Management Protocol (SNMP) 2948 Management Frameworks", STD 62, 2949 RFC 3411, December 2002. 2951 [RFC3705] Ray, B. and R. Abbi, "High 2952 Capacity Textual Conventions for 2953 MIB Modules Using Performance 2954 History Based on 15 Minute 2955 Intervals", RFC 3705, 2956 February 2004. 2958 [TR-159] Beili, E. and M. Morgenstern, 2959 "Management Framework for xDSL 2960 Bonding", Broadband Forum 2961 technical report TR-159, 2962 December 2008. 2964 10.2. Informative References 2966 [802.3] IEEE, "IEEE Standard for 2967 Information technology - 2968 Telecommunications and information 2969 exchange between systems - Local 2970 and metropolitan area networks - 2971 Specific requirements - Part 3: 2972 Carrier Sense Multiple Access with 2973 Collision Detection (CSMA/CD) 2974 Access Method and Physical Layer 2975 Specifications", IEEE Std 802.3- 2976 2005, December 2005. 2978 [ADSLMIB] IETF, "ADSL MIB (adslmib) 2979 Charter", . 2983 [G.991.2] ITU-T, "Single-pair High-speed 2984 Digital Subscriber Line (SHDSL) 2985 transceivers", ITU-T 2986 Recommendation G.991.2, 2987 December 2003, . 2990 [G.993.1] ITU-T, "Very High speed Digital 2991 Subscriber Line transceivers", 2992 ITU-T Recommendation G.993.1, 2993 June 2004, . 2996 [G.998.1] ITU-T, "ATM-based multi-pair 2997 bonding", ITU-T 2998 Recommendation G.998.1, 2999 January 2005, . 3002 [G.998.2] ITU-T, "Ethernet-based multi-pair 3003 bonding", ITU-T 3004 Recommendation G.998.2, 3005 January 2005, . 3008 [G.998.3] ITU-T, "Multi-pair bonding using 3009 time-division inverse 3010 multiplexing", ITU-T 3011 Recommendation G.998.3, 3012 January 2005, . 3015 [I-D.ietf-adslmib-gbond-atm-mib] Beili, E., "ATM-based xDSL Bonded 3016 Interfaces MIB", draft-ietf- 3017 adslmib-gbond-atm-mib-02 (work in 3018 progress), November 2010. 3020 [I-D.ietf-adslmib-gbond-eth-mib] Beili, E. and M. Morgenstern, 3021 "Ethernet-based xDSL Bonded 3022 Interfaces MIB", draft-ietf- 3023 adslmib-gbond-eth-mib-02 (work in 3024 progress), November 2010. 3026 [I-D.ietf-adslmib-gbond-tdim-mib] Beili, E., "TDIM-based xDSL Bonded 3027 Interfaces MIB", draft-ietf- 3028 adslmib-gbond-tdim-mib-04 (work in 3029 progress), November 2010. 3031 [IANAifType-MIB] Internet Assigned Numbers 3032 Authority (IANA), "IANAifType 3033 Textual Convention definition", . 3037 [RFC2864] McCloghrie, K. and G. Hanson, "The 3038 Inverted Stack Table Extension to 3039 the Interfaces Group MIB", 3040 RFC 2864, June 2000. 3042 [RFC3410] Case, J., Mundy, R., Partain, D., 3043 and B. Stewart, "Introduction and 3044 Applicability Statements for 3045 Internet-Standard Management 3046 Framework", RFC 3410, 3047 December 2002. 3049 [RFC3440] Ly, F. and G. Bathrick, 3050 "Definitions of Extension Managed 3051 Objects for Asymmetric Digital 3052 Subscriber Lines", RFC 3440, 3053 December 2002. 3055 [RFC3593] Tesink, K., "Textual Conventions 3056 for MIB Modules Using Performance 3057 History Based on 15 Minute 3058 Intervals", RFC 3593, 3059 September 2003. 3061 [RFC3728] Ray, B. and R. Abbi, "Definitions 3062 of Managed Objects for Very High 3063 Speed Digital Subscriber Lines 3064 (VDSL)", RFC 3728, February 2004. 3066 [RFC4181] Heard, C., "Guidelines for Authors 3067 and Reviewers of MIB Documents", 3068 BCP 111, RFC 4181, September 2005. 3070 [RFC4319] Sikes, C., Ray, B., and R. Abbi, 3071 "Definitions of Managed Objects 3072 for High Bit-Rate DSL - 2nd 3073 generation (HDSL2) and Single-Pair 3074 High-Speed Digital Subscriber Line 3075 (SHDSL) Lines", RFC 4319, 3076 December 2005. 3078 [RFC4706] Morgenstern, M., Dodge, M., 3079 Baillie, S., and U. Bonollo, 3080 "Definitions of Managed Objects 3081 for Asymmetric Digital Subscriber 3082 Line 2 (ADSL2)", RFC 4706, 3083 November 2006. 3085 [RFC4836] Beili, E., "Definitions of Managed 3086 Objects for IEEE 802.3 Medium 3087 Attachment Units (MAUs)", 3088 RFC 4836, April 2007. 3090 [RFC5066] Beili, E., "Ethernet in the First 3091 Mile Copper (EFMCu) Interfaces 3092 MIB", RFC 5066, November 2007. 3094 [RFC5650] Morgenstern, M., Baillie, S., and 3095 U. Bonollo, "Definitions of 3096 Managed Objects for Very High 3097 Speed Digital Subscriber Line 2 3098 (VDSL2)", RFC 5650, 3099 September 2009. 3101 [af-phy-0086] ATM Forum, "Inverse Multiplexing 3102 for ATM (IMA) Specification 3103 Version 1.1", ATM Forum 3104 specification af-pfy-0086.001, 3105 March 1999. 3107 URIs 3109 [1] 3111 Authors' Addresses 3113 Edward Beili 3114 Actelis Networks 3115 25 Bazel St. 3116 Petach-Tikva 49103 3117 Israel 3119 Phone: +972-3-924-3491 3120 EMail: edward.beili@actelis.com 3122 Moti Morgenstern 3123 ECI Telecom 3124 30 Hasivim St. 3125 Petach-Tikva 49517 3126 Israel 3128 Phone: +972-3-926-6258 3129 EMail: moti.morgenstern@ecitele.com