idnits 2.17.1 draft-ietf-adslmib-gbond-mib-06.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 (March 14, 2011) is 4784 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 2979, but no explicit reference was found in the text == Unused Reference: 'G.993.1' is defined on line 2986, 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-03 == Outdated reference: A later version (-08) exists of draft-ietf-adslmib-gbond-eth-mib-03 == Outdated reference: A later version (-08) exists of draft-ietf-adslmib-gbond-tdim-mib-05 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: September 15, 2011 ECI Telecom 6 March 14, 2011 8 xDSL multi-pair bonding (G.Bond) MIB 9 draft-ietf-adslmib-gbond-mib-06.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 September 15, 2011. 39 Copyright Notice 41 Copyright (c) 2011 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 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 [G.994.1] handshake 299 protocol. This information can then be used to detect copper 300 misconnections or for an automatic assignment of the local BCEs into 301 aggregation groups 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 // potentially 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 "201103140000Z" -- Mar 14, 2011 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 4951169 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 49103 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 4951169 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 (2011). 846 This version of this MIB module is part of RFC XXXX; 847 see the RFC itself for full legal notices." 849 REVISION "201103140000Z" -- Mar 14, 2011 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 a G.Bond port indexed by the ifIndex. 1153 Note that a 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 accommodate 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 accommodate 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, a 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, a 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 a 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 a G.Bond port indexed by the ifIndex. 1600 Note that a 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 "Current operating bonding scheme of a G.Bond port link partner. 1639 The possible values are: 1640 unknown(0) - peer cannot be reached due to the link state 1641 g9981(1) - G.998.1 bonding 1642 g9982(2) - G.998.2 bonding 1643 g9983(3) - G.998.3 bonding 1645 This object maps to the TR-159 attribute 1646 aGroupPeerOperBondScheme." 1647 REFERENCE 1648 "[TR-159] 5.5.1.5" 1649 ::= { gBondPortStatusEntry 2 } 1651 gBondUpDataRate OBJECT-TYPE 1652 SYNTAX Gauge32 1653 UNITS "bps" 1654 MAX-ACCESS read-only 1655 STATUS current 1656 DESCRIPTION 1657 "A current G.Bond port operational Data Rate in the upstream 1658 direction, in bps. 1659 This object represents an estimation of the sum of individual 1660 BCE upstream data rates, modified to compensate for 1661 fragmentation and encapsulation overhead (e.g., for an 1662 Ethernet service, the target data rate of 10Mbps SHALL allow 1663 lossless transmission of full-duplex 10Mbps Ethernet frame 1664 stream with minimal inter-frame gap). 1666 Note that for symmetrical interfaces gBondUpDataRate == 1667 gBondDnDataRate == ifSpeed. 1669 This object maps to the TR-159 attribute aGroupUpRate." 1670 REFERENCE 1671 "[TR-159] 5.5.1.15" 1672 ::= { gBondPortStatusEntry 3 } 1674 gBondDnDataRate OBJECT-TYPE 1675 SYNTAX Gauge32 1676 UNITS "bps" 1677 MAX-ACCESS read-only 1678 STATUS current 1679 DESCRIPTION 1680 "A current G.Bond port operational Data Rate in the downstream 1681 direction, in bps. 1682 This object represents an estimation of the sum of individual 1683 BCE downstream data rates, modified to compensate for 1684 fragmentation and encapsulation overhead (e.g., for an 1685 Ethernet service, the target data rate of 10Mbps SHALL allow 1686 lossless transmission of full-duplex 10Mbps Ethernet frame 1687 stream with minimal inter-frame gap). 1689 Note that for symmetrical interfaces gBondUpDataRate == 1690 gBondDnDataRate == ifSpeed. 1692 This object maps to the TR-159 attribute aGroupDownRate." 1693 REFERENCE 1694 "[TR-159] 5.5.1.16" 1695 ::= { gBondPortStatusEntry 4 } 1697 gBondFltStatus OBJECT-TYPE 1698 SYNTAX BITS { 1699 noPeer(0), 1700 peerPowerLoss(1), 1701 peerBondSchemeMismatch(2), 1702 bceSubTypeMismatch(3), 1703 lowRate(4) 1704 } 1705 MAX-ACCESS read-only 1706 STATUS current 1707 DESCRIPTION 1708 "G.Bond (GBS) port Fault Status. This is a bitmap of possible 1709 conditions. The various bit positions are: 1710 noPeer - peer GBS cannot be reached (e.g., 1711 no BCEs attached, all BCEs are Down 1712 etc.). 1713 peerPowerLoss - peer GBS has indicated impending unit 1714 failure due to loss of local power 1715 ('Dying Gasp'). 1716 peerBondSchemeMismatch - operating bonding scheme of a peer 1717 GBS is different from the local one. 1718 bceSubTypeMismatch - local BCEs in the aggregation group 1719 are not of the same sub-type, e.g., 1720 some BCEs in the local device are -O 1721 while others are -R subtype. 1722 lowRate - gBondUpRate/gBondDnRate of the port 1723 has reached or dropped below 1724 gBondThreshLowUpRate/ 1725 gBondThreshLowUpRate. 1727 This object is intended to supplement ifOperStatus object 1728 in IF-MIB and ifMauMediaAvailable in MAU-MIB. 1730 This object maps to the TR-159 attribute aGroupStatus." 1731 REFERENCE 1732 "[TR-159] 5.5.1.9; IF-MIB, ifOperStatus; MAU-MIB, 1733 ifMauMediaAvailable" 1734 ::= { gBondPortStatusEntry 5 } 1736 gBondPortSide OBJECT-TYPE 1737 SYNTAX INTEGER { 1738 subscriber(1), 1739 office(2), 1740 unknown(3) 1742 } 1743 MAX-ACCESS read-only 1744 STATUS current 1745 DESCRIPTION 1746 "G.Bond port mode of operation (subtype). 1747 The value of 'subscriber' indicates the port is designated as 1748 '-R' subtype (all BCEs assigned to this port are of subtype 1749 '-R'). 1750 The value of the 'office' indicates that the port is 1751 designated as '-O' subtype (all BCEs assigned to this port are 1752 of subtype '-O'). 1753 The value of 'unknown' indicates that the port has no assigned 1754 BCEs yet or that the assigned BCEs are not of the same side 1755 (subTypeBCEMismatch). 1757 This object maps to the TR-159 attribute aGroupEnd." 1758 REFERENCE 1759 "[TR-159] 5.5.1.11" 1760 ::= { gBondPortStatusEntry 6 } 1762 gBondNumBCEs OBJECT-TYPE 1763 SYNTAX Unsigned32 (0..32) 1764 MAX-ACCESS read-only 1765 STATUS current 1766 DESCRIPTION 1767 "Number of BCEs that is currently aggregated by the local GBS 1768 (assigned to the G.Bond port using ifStackTable). 1769 This number is never greater than gBondCapacity. 1771 This object SHALL be automatically incremented or decremented 1772 when a BCE is added or deleted to/from the G.Bond port using 1773 ifStackTable. 1775 This object maps to the TR-159 attribute aGroupNumChannels" 1776 REFERENCE 1777 "[TR-159] 5.5.1.14" 1778 ::= { gBondPortStatusEntry 7 } 1780 -- Performance Monitoring group 1782 gBondPortPM OBJECT IDENTIFIER ::= { gBondPort 4 } 1784 gBondPortPerfCurrTable OBJECT-TYPE 1785 SYNTAX SEQUENCE OF GBondPortPerfCurrEntry 1786 MAX-ACCESS not-accessible 1787 STATUS current 1788 DESCRIPTION 1789 "This table contains current Performance Monitoring (PM) 1790 information for a GBS port. This table contains live data from 1791 the equipment and as such is NOT persistent." 1792 ::= { gBondPortPM 1 } 1794 gBondPortPerfCurrEntry OBJECT-TYPE 1795 SYNTAX GBondPortPerfCurrEntry 1796 MAX-ACCESS not-accessible 1797 STATUS current 1798 DESCRIPTION 1799 "An entry in the G.Bond Port PM table. 1800 Each entry represents a G.Bond port indexed by the ifIndex. 1801 Note that a G.Bond GBS port runs on top of a single 1802 or multiple BCE port(s), which are also indexed by ifIndex." 1803 INDEX { ifIndex } 1804 ::= { gBondPortPerfCurrTable 1 } 1806 GBondPortPerfCurrEntry ::= 1807 SEQUENCE { 1808 gBondPerfES HCPerfTotalCount, 1809 gBondPerfSES HCPerfTotalCount, 1810 gBondPerfUAS HCPerfTotalCount, 1811 gBondPerf15MinValidIntervals HCPerfValidIntervals, 1812 gBondPerf15MinInvalidIntervals HCPerfInvalidIntervals, 1813 gBondPerfCurr15MinTimeElapsed HCPerfTimeElapsed, 1814 gBondPerfCurr15MinES HCPerfCurrentCount, 1815 gBondPerfCurr15MinSES HCPerfCurrentCount, 1816 gBondPerfCurr15MinUAS HCPerfCurrentCount, 1817 gBondPerf1DayValidIntervals Unsigned32, 1818 gBondPerf1DayInvalidIntervals Unsigned32, 1819 gBondPerfCurr1DayTimeElapsed HCPerfTimeElapsed, 1820 gBondPerfCurr1DayES HCPerfCurrentCount, 1821 gBondPerfCurr1DaySES HCPerfCurrentCount, 1822 gBondPerfCurr1DayUAS HCPerfCurrentCount 1823 } 1825 gBondPerfES OBJECT-TYPE 1826 SYNTAX HCPerfTotalCount 1827 MAX-ACCESS read-only 1828 STATUS current 1829 DESCRIPTION 1830 "A read-only count of Errored Seconds (ES) on the GBS since the 1831 BTU was last restarted. 1833 An Errored Second for a G.998.x interface is defined as a count 1834 of 1-second intervals during which one or more GBS errors are 1835 declared. The errors are specific for each bonding scheme, e.g. 1836 - lost cells for the ATM bonding; 1837 - lost or discarded (due to an error or a buffer overflow) 1838 fragments for the Ethernet bonding; 1839 - CRC4, CRC6 or CRC8 errors for the TDIM bonding 1840 This object is inhibited during Unavailable Seconds (UAS). 1842 This object maps to the TR-159 attribute aGroupPerfES." 1843 REFERENCE 1844 "[TR-159] 5.5.1.29" 1845 ::= { gBondPortPerfCurrEntry 1 } 1847 gBondPerfSES OBJECT-TYPE 1848 SYNTAX HCPerfTotalCount 1849 MAX-ACCESS read-only 1850 STATUS current 1851 DESCRIPTION 1852 "A read-only count of Severely Errored Seconds (SES) on the GBS 1853 since the BTU was last restarted. 1855 A Severely Errored Second for a G.998.x interface is defined as 1856 a count of 1-second intervals during which GBS errors cause at 1857 least 1% traffic loss of the nominal bonded link rate or at 1858 least 12ms for the TDM traffic. The exact definition is specific 1859 for each bonding scheme, e.g. 1860 - 234 lost cells for the ATM bonding with 10Mbps nominal link 1861 rate 1862 - 60 lost/discarded fragments for the Ethernet bonding with 1863 10Mbps nominal link rate and fixed 192 Byte-long fragment 1864 size. 1865 - 6 or more CRC4, one or more CRC6 or one or more CRC8 errors 1866 for the TDM bonding 1867 This object is inhibited during Unavailable Seconds (UAS). 1869 This object maps to the TR-159 attribute aGroupPerfSES." 1870 REFERENCE 1871 "[TR-159] 5.5.1.30" 1872 ::= { gBondPortPerfCurrEntry 2 } 1874 gBondPerfUAS OBJECT-TYPE 1875 SYNTAX HCPerfTotalCount 1876 MAX-ACCESS read-only 1877 STATUS current 1878 DESCRIPTION 1879 "A read-only count of Unavailable Seconds (UAS) on the GBS since 1880 the BTU was last restarted. 1882 An Unavailable Second for a G.998.x interface is defined as a 1883 count of 1-second intervals during which the bonded link is 1884 unavailable. The G.998.x link becomes unavailable at the onset 1885 of 10 contiguous SESs. The 10 SESs are included in the 1886 unavailable time. Once unavailable, the G.998.x line becomes 1887 available at the onset of 10 contiguous seconds with no SESs. 1888 The 10 seconds with no SESs are excluded from unavailable time. 1890 This object maps to the TR-159 attribute aGroupPerfUAS." 1891 REFERENCE 1892 "[TR-159] 5.5.1.31" 1893 ::= { gBondPortPerfCurrEntry 3 } 1895 gBondPerf15MinValidIntervals OBJECT-TYPE 1896 SYNTAX HCPerfValidIntervals 1897 MAX-ACCESS read-only 1898 STATUS current 1899 DESCRIPTION 1900 "A read-only number of 15-minute intervals for which data was 1901 collected. The value of this object will be 96 or the maximum 1902 number of 15-minute history intervals collected by the 1903 implementation unless the measurement was (re-)started recently, 1904 in which case the value will be the number of complete 15 1905 minutes intervals for which there are at least some data. 1906 In certain cases it is possible that some intervals are 1907 unavailable. In this case, this object reports the maximum 1908 interval number for which data is available. 1910 This object maps to the TR-159 attribute 1911 aGroupPerf15MinValidIntervals." 1912 REFERENCE 1913 "[TR-159] 5.5.1.32" 1914 ::= { gBondPortPerfCurrEntry 4 } 1916 gBondPerf15MinInvalidIntervals OBJECT-TYPE 1917 SYNTAX HCPerfInvalidIntervals 1918 MAX-ACCESS read-only 1919 STATUS current 1920 DESCRIPTION 1921 "A read-only number of 15-minute intervals for which data was 1922 not always available. The value will typically be zero except in 1923 cases where the data for some intervals are not available. 1925 This object maps to the TR-159 attribute 1926 aGroupPerf15MinInvalidIntervals." 1927 REFERENCE 1928 "[TR-159] 5.5.1.33" 1929 ::= { gBondPortPerfCurrEntry 5 } 1931 gBondPerfCurr15MinTimeElapsed OBJECT-TYPE 1932 SYNTAX HCPerfTimeElapsed 1933 MAX-ACCESS read-only 1934 STATUS current 1935 DESCRIPTION 1936 "A read-only count of seconds that have elapsed since the 1937 beginning of the current 15-minute performance interval. 1939 This object maps to the TR-159 attribute 1940 aGroupPerfCurr15MinTimeElapsed." 1941 REFERENCE 1942 "[TR-159] 5.5.1.34" 1943 ::= { gBondPortPerfCurrEntry 6 } 1945 gBondPerfCurr15MinES OBJECT-TYPE 1946 SYNTAX HCPerfCurrentCount 1947 MAX-ACCESS read-only 1948 STATUS current 1949 DESCRIPTION 1950 "A read-only count of Errored Seconds (ES) on the GBS in the 1951 current 15-minute performance interval. 1953 This object maps to the TR-159 attribute aGroupPerfCurr15MinES." 1954 REFERENCE 1955 "[TR-159] 5.5.1.35" 1956 ::= { gBondPortPerfCurrEntry 7 } 1958 gBondPerfCurr15MinSES OBJECT-TYPE 1959 SYNTAX HCPerfCurrentCount 1960 MAX-ACCESS read-only 1961 STATUS current 1962 DESCRIPTION 1963 "A read-only count of Severely Errored Seconds (ES) on the GBS 1964 in the current 15-minute performance interval. 1966 This object maps to the TR-159 attribute aGroupPerfCurr15MinSES." 1967 REFERENCE 1968 "[TR-159] 5.5.1.36" 1969 ::= { gBondPortPerfCurrEntry 8 } 1971 gBondPerfCurr15MinUAS OBJECT-TYPE 1972 SYNTAX HCPerfCurrentCount 1973 MAX-ACCESS read-only 1974 STATUS current 1975 DESCRIPTION 1976 "A read-only count of Unavailable Seconds (UAS) on the GBS in 1977 the current 15-minute performance interval. 1979 This object maps to the TR-159 attribute aGroupPerfCurr15MinUAS." 1980 REFERENCE 1981 "[TR-159] 5.5.1.37" 1982 ::= { gBondPortPerfCurrEntry 9 } 1984 gBondPerf1DayValidIntervals OBJECT-TYPE 1985 SYNTAX Unsigned32 (0..7) 1986 MAX-ACCESS read-only 1987 STATUS current 1988 DESCRIPTION 1989 "A read-only number of 1-day intervals for which data was 1990 collected. The value of this object will be 7 or the maximum 1991 number of 1-day history intervals collected by the 1992 implementation unless the measurement was (re-)started recently, 1993 in which case the value will be the number of complete 1-day 1994 intervals for which there are at least some data. 1995 In certain cases it is possible that some intervals are 1996 unavailable. In this case, this object reports the maximum 1997 interval number for which data is available. 1999 This object maps to the TR-159 attribute 2000 aGroupPerf1DayValidIntervals." 2001 REFERENCE 2002 "[TR-159] 5.5.1.45" 2003 ::= { gBondPortPerfCurrEntry 10 } 2005 gBondPerf1DayInvalidIntervals OBJECT-TYPE 2006 SYNTAX Unsigned32 (0..7) 2007 MAX-ACCESS read-only 2008 STATUS current 2009 DESCRIPTION 2010 "A read-only number of 1-day intervals for which data was 2011 not always available. The value will typically be zero except in 2012 cases where the data for some intervals are not available. 2014 This object maps to the TR-159 attribute 2015 aGroupPerf1DayInvalidIntervals." 2016 REFERENCE 2017 "[TR-159] 5.5.1.46" 2018 ::= { gBondPortPerfCurrEntry 11 } 2020 gBondPerfCurr1DayTimeElapsed OBJECT-TYPE 2021 SYNTAX HCPerfTimeElapsed 2022 MAX-ACCESS read-only 2023 STATUS current 2024 DESCRIPTION 2025 "A read-only count of seconds that have elapsed since the 2026 beginning of the current 1-day performance interval. 2028 This object maps to the TR-159 attribute 2029 aGroupPerfCurr1DayTimeElapsed." 2030 REFERENCE 2031 "[TR-159] 5.5.1.47" 2032 ::= { gBondPortPerfCurrEntry 12 } 2034 gBondPerfCurr1DayES OBJECT-TYPE 2035 SYNTAX HCPerfCurrentCount 2036 MAX-ACCESS read-only 2037 STATUS current 2038 DESCRIPTION 2039 "A read-only count of Errored Seconds (ES) on the GBS in the 2040 current 1-day performance interval. 2042 This object maps to the TR-159 attribute aGroupPerfCurr1DayES." 2043 REFERENCE 2044 "[TR-159] 5.5.1.48" 2045 ::= { gBondPortPerfCurrEntry 13 } 2047 gBondPerfCurr1DaySES OBJECT-TYPE 2048 SYNTAX HCPerfCurrentCount 2049 MAX-ACCESS read-only 2050 STATUS current 2051 DESCRIPTION 2052 "A read-only count of Severely Errored Seconds (ES) on the GBS 2053 in the current 1-day performance interval. 2055 This object maps to the TR-159 attribute aGroupPerfCurr1DaySES." 2056 REFERENCE 2057 "[TR-159] 5.5.1.49" 2058 ::= { gBondPortPerfCurrEntry 14 } 2060 gBondPerfCurr1DayUAS OBJECT-TYPE 2061 SYNTAX HCPerfCurrentCount 2062 MAX-ACCESS read-only 2063 STATUS current 2064 DESCRIPTION 2065 "A read-only count of Unavailable Seconds (UAS) on the GBS in 2066 the current 1-day performance interval. 2068 This object maps to the TR-159 attribute aGroupPerfCurr1DayUAS." 2069 REFERENCE 2070 "[TR-159] 5.5.1.50" 2071 ::= { gBondPortPerfCurrEntry 15 } 2073 -- PM history: 15-min buckets 2075 gBondPortPerf15MinTable OBJECT-TYPE 2076 SYNTAX SEQUENCE OF GBondPortPerf15MinEntry 2077 MAX-ACCESS not-accessible 2078 STATUS current 2079 DESCRIPTION 2080 "This table contains historical 15-minute buckets of Performance 2081 Monitoring information for a GBS port (a row for each 15-minute 2082 interval, up to 96 intervals). 2083 Entries in this table MUST be maintained in a persistent manner." 2084 ::= { gBondPortPM 2 } 2086 gBondPortPerf15MinEntry OBJECT-TYPE 2087 SYNTAX GBondPortPerf15MinEntry 2088 MAX-ACCESS not-accessible 2089 STATUS current 2090 DESCRIPTION 2091 "An entry in the G.Bond Port historical 15-minute PM table. 2092 Each entry represents performance monitoring data for a GBS port, 2093 indexed by ifIndex, collected during a particular 15-minute 2094 interval, indexed by gBondPerf15MinIntervalIndex." 2095 INDEX { ifIndex, gBondPerf15MinIntervalIndex } 2096 ::= { gBondPortPerf15MinTable 1 } 2098 GBondPortPerf15MinEntry ::= 2099 SEQUENCE { 2100 gBondPerf15MinIntervalIndex Unsigned32, 2101 gBondPerf15MinIntervalMoniTime HCPerfTimeElapsed, 2102 gBondPerf15MinIntervalES HCPerfIntervalCount, 2103 gBondPerf15MinIntervalSES HCPerfIntervalCount, 2104 gBondPerf15MinIntervalUAS HCPerfIntervalCount, 2105 gBondPerf15MinIntervalValid TruthValue 2106 } 2108 gBondPerf15MinIntervalIndex OBJECT-TYPE 2109 SYNTAX Unsigned32 (1..96) 2110 MAX-ACCESS not-accessible 2111 STATUS current 2112 DESCRIPTION 2113 "Performance Data Interval number. 1 is the most recent previous 2114 interval; interval 96 is 24 hours ago. 2115 Intervals 2..96 are OPTIONAL. 2117 This object maps to the TR-159 attribute 2118 aGroupPerf15MinIntervalNumber." 2119 REFERENCE 2120 "[TR-159] 5.5.1.57" 2121 ::= { gBondPortPerf15MinEntry 1 } 2123 gBondPerf15MinIntervalMoniTime OBJECT-TYPE 2124 SYNTAX HCPerfTimeElapsed 2125 MAX-ACCESS read-only 2126 STATUS current 2127 DESCRIPTION 2128 "A read-only count of seconds over which the performance data 2129 was actually monitored. This value will be the same as the 2130 interval duration (900 seconds), except in a situation where 2131 performance data could not be collected for any reason." 2132 ::= { gBondPortPerf15MinEntry 2 } 2134 gBondPerf15MinIntervalES OBJECT-TYPE 2135 SYNTAX HCPerfIntervalCount 2136 MAX-ACCESS read-only 2137 STATUS current 2138 DESCRIPTION 2139 "A read-only count of Errored Seconds (ES) on the GBS in the 2140 15-minute performance history interval. 2142 This object maps to the TR-159 attribute 2143 aGroupPerf15MinIntervalES." 2144 REFERENCE 2145 "[TR-159] 5.5.1.59" 2146 ::= { gBondPortPerf15MinEntry 3 } 2148 gBondPerf15MinIntervalSES OBJECT-TYPE 2149 SYNTAX HCPerfIntervalCount 2150 MAX-ACCESS read-only 2151 STATUS current 2152 DESCRIPTION 2153 "A read-only count of Severely Errored Seconds (ES) on the GBS 2154 in the 15-minute performance history interval. 2156 This object maps to the TR-159 attribute 2157 aGroupPerf15MinIntervalSES." 2158 REFERENCE 2159 "[TR-159] 5.5.1.60" 2160 ::= { gBondPortPerf15MinEntry 4 } 2162 gBondPerf15MinIntervalUAS OBJECT-TYPE 2163 SYNTAX HCPerfIntervalCount 2164 MAX-ACCESS read-only 2165 STATUS current 2166 DESCRIPTION 2167 "A read-only count of Unavailable Seconds (UAS) on the GBS in 2168 the current 15-minute performance interval. 2170 This object maps to the TR-159 attribute aGroupPerfCurr15MinUAS." 2171 REFERENCE 2172 "[TR-159] 5.5.1.61" 2174 ::= { gBondPortPerf15MinEntry 5 } 2176 gBondPerf15MinIntervalValid OBJECT-TYPE 2177 SYNTAX TruthValue 2178 MAX-ACCESS read-only 2179 STATUS current 2180 DESCRIPTION 2181 "A read-only object indicating whether or not this history 2182 bucket contains valid data. Valid bucket is reported as true(1) 2183 and invalid bucket as false(2). 2184 If this history bucket is invalid the BTU-C MUST NOT produce 2185 notifications based upon the value of the counters in this 2186 bucket. 2187 Note that an implementation may decide not to store invalid 2188 history buckets in its data base. In such case this object is 2189 not required as only valid history buckets are available while 2190 invalid history buckets are simply not in the data base. 2192 This object maps to the TR-159 attribute 2193 aGroupPerf15MinIntervalValid." 2194 REFERENCE 2195 "[TR-159] 5.5.1.58" 2196 ::= { gBondPortPerf15MinEntry 6 } 2198 -- PM history: 1-day buckets 2200 gBondPortPerf1DayTable OBJECT-TYPE 2201 SYNTAX SEQUENCE OF GBondPortPerf1DayEntry 2202 MAX-ACCESS not-accessible 2203 STATUS current 2204 DESCRIPTION 2205 "This table contains historical 1-day buckets of Performance 2206 Monitoring information for a GBS port (a row for each 1-day 2207 interval, up to 7 intervals). 2208 Entries in this table MUST be maintained in a persistent manner." 2209 ::= { gBondPortPM 3 } 2211 gBondPortPerf1DayEntry OBJECT-TYPE 2212 SYNTAX GBondPortPerf1DayEntry 2213 MAX-ACCESS not-accessible 2214 STATUS current 2215 DESCRIPTION 2216 "An entry in the G.Bond Port historical 1-day PM table. 2217 Each entry represents performance monitoring data for a GBS port, 2218 indexed by ifIndex, collected during a particular 1-day 2219 interval, indexed by gBondPerf1DayIntervalIndex." 2220 INDEX { ifIndex, gBondPerf1DayIntervalIndex } 2221 ::= { gBondPortPerf1DayTable 1 } 2223 GBondPortPerf1DayEntry ::= 2224 SEQUENCE { 2225 gBondPerf1DayIntervalIndex Unsigned32, 2226 gBondPerf1DayIntervalMoniTime HCPerfTimeElapsed, 2227 gBondPerf1DayIntervalES HCPerfIntervalCount, 2228 gBondPerf1DayIntervalSES HCPerfIntervalCount, 2229 gBondPerf1DayIntervalUAS HCPerfIntervalCount, 2230 gBondPerf1DayIntervalValid TruthValue 2231 } 2233 gBondPerf1DayIntervalIndex OBJECT-TYPE 2234 SYNTAX Unsigned32 (1..7) 2235 MAX-ACCESS not-accessible 2236 STATUS current 2237 DESCRIPTION 2238 "Performance Data Interval number. 1 is the most recent previous 2239 interval; interval 7 is 7 days ago. 2240 Intervals 2..7 are OPTIONAL. 2242 This object maps to the TR-159 attribute 2243 aGroupPerf1DayIntervalNumber." 2244 REFERENCE 2245 "[TR-159] 5.5.1.62" 2246 ::= { gBondPortPerf1DayEntry 1 } 2248 gBondPerf1DayIntervalMoniTime OBJECT-TYPE 2249 SYNTAX HCPerfTimeElapsed 2250 MAX-ACCESS read-only 2251 STATUS current 2252 DESCRIPTION 2253 "A read-only count of seconds over which the performance data 2254 was actually monitored. This value will be the same as the 2255 interval duration (86400 seconds), except in a situation where 2256 performance data could not be collected for any reason. 2258 This object maps to the TR-159 attribute 2259 aGroupPerf1DayIntervalMoniSecs." 2260 REFERENCE 2261 "[TR-159] 5.5.1.64" 2262 ::= { gBondPortPerf1DayEntry 2 } 2264 gBondPerf1DayIntervalES OBJECT-TYPE 2265 SYNTAX HCPerfIntervalCount 2266 MAX-ACCESS read-only 2267 STATUS current 2268 DESCRIPTION 2269 "A read-only count of Errored Seconds (ES) on the GBS in the 2270 1-day performance history interval. 2272 This object maps to the TR-159 attribute 2273 aGroupPerf1DayIntervalES." 2274 REFERENCE 2275 "[TR-159] 5.5.1.65" 2276 ::= { gBondPortPerf1DayEntry 3 } 2278 gBondPerf1DayIntervalSES OBJECT-TYPE 2279 SYNTAX HCPerfIntervalCount 2280 MAX-ACCESS read-only 2281 STATUS current 2282 DESCRIPTION 2283 "A read-only count of Severely Errored Seconds (ES) on the GBS 2284 in the 1-day performance history interval. 2286 This object maps to the TR-159 attribute 2287 aGroupPerf1DayIntervalSES." 2288 REFERENCE 2289 "[TR-159] 5.5.1.66" 2290 ::= { gBondPortPerf1DayEntry 4 } 2292 gBondPerf1DayIntervalUAS OBJECT-TYPE 2293 SYNTAX HCPerfIntervalCount 2294 MAX-ACCESS read-only 2295 STATUS current 2296 DESCRIPTION 2297 "A read-only count of Unavailable Seconds (UAS) on the GBS in 2298 the current 1-day performance interval. 2300 This object maps to the TR-159 attribute aGroupPerfCurr1DayUAS." 2301 REFERENCE 2302 "[TR-159] 5.5.1.67" 2303 ::= { gBondPortPerf1DayEntry 5 } 2305 gBondPerf1DayIntervalValid OBJECT-TYPE 2306 SYNTAX TruthValue 2307 MAX-ACCESS read-only 2308 STATUS current 2309 DESCRIPTION 2310 "A read-only object indicating whether or not this history 2311 bucket contains valid data. Valid bucket is reported as true(1) 2312 and invalid bucket as false(2). 2313 If this history bucket is invalid the BTU-C MUST NOT produce 2314 notifications based upon the value of the counters in this 2315 bucket. 2316 Note that an implementation may decide not to store invalid 2317 history buckets in its data base. In such case this object is 2318 not required as only valid history buckets are available while 2319 invalid history buckets are simply not in the data base. 2321 This object maps to the TR-159 attribute 2322 aGroupPerf1DayIntervalValid." 2323 REFERENCE 2324 "[TR-159] 5.5.1.63" 2325 ::= { gBondPortPerf1DayEntry 6 } 2327 -- Performance Monitoring TCA Configuration profile 2329 gBondPortPerfTcaConfProfileTable OBJECT-TYPE 2330 SYNTAX SEQUENCE OF GBondPortPerfTcaConfProfileEntry 2331 MAX-ACCESS not-accessible 2332 STATUS current 2333 DESCRIPTION 2334 "This table supports definitions of Performance Monitoring (PM) 2335 Threshold Crossing Alerts (TCA) configuration profiles for GBS 2336 ports. 2337 Entries in this table MUST be maintained in a persistent manner." 2338 ::= { gBondPortPM 4 } 2340 gBondPortPerfTcaConfProfileEntry OBJECT-TYPE 2341 SYNTAX GBondPortPerfTcaConfProfileEntry 2342 MAX-ACCESS not-accessible 2343 STATUS current 2344 DESCRIPTION 2345 "An entry in the GBS PM TCA Configuration table. 2346 Each entry corresponds to a single TCA configuration profile. 2347 Each profile contains a set of parameters for setting alarm 2348 thresholds for various performance attributes monitored at GBS 2349 ports. Profiles may be created/deleted using the row 2350 creation/deletion mechanism via 2351 gBondPerfTcaConfProfileRowStatus. If an active entry is 2352 referenced via gBondPerfTcaConfProfile, the entry MUST 2353 remain active until all references are removed. 2354 A default profile with an index of 'DEFVAL', will always exist 2355 and its parameters will be set to vendor specific values, 2356 unless otherwise specified in this document." 2357 INDEX { gBondPerfTcaConfProfileName } 2358 ::= { gBondPortPerfTcaConfProfileTable 1 } 2360 GBondPortPerfTcaConfProfileEntry ::= 2361 SEQUENCE { 2362 gBondPerfTcaConfProfileName SnmpAdminString, 2363 gBondPerfThreshold15MinES HCPerfIntervalThreshold, 2364 gBondPerfThreshold15MinSES HCPerfIntervalThreshold, 2365 gBondPerfThreshold15MinUAS HCPerfIntervalThreshold, 2366 gBondPerfThreshold1DayES GBondPerf1DayIntervalThreshold, 2367 gBondPerfThreshold1DaySES GBondPerf1DayIntervalThreshold, 2368 gBondPerfThreshold1DayUAS GBondPerf1DayIntervalThreshold, 2369 gBondPerfTcaConfProfileRowStatus RowStatus 2370 } 2372 gBondPerfTcaConfProfileName OBJECT-TYPE 2373 SYNTAX SnmpAdminString (SIZE(1..32)) 2374 MAX-ACCESS not-accessible 2375 STATUS current 2376 DESCRIPTION 2377 "This object is a unique index (name) associated with this 2378 GBS PM TCA profile." 2379 ::= { gBondPortPerfTcaConfProfileEntry 1 } 2381 gBondPerfThreshold15MinES OBJECT-TYPE 2382 SYNTAX HCPerfIntervalThreshold 2383 MAX-ACCESS read-create 2384 STATUS current 2385 DESCRIPTION 2386 "A desired threshold for the number of Errored Seconds (ES) 2387 within any given 15-minute performance data collection interval. 2388 If the number of ESs in a particular 15-minute collection 2389 interval reaches or exceeds this value, a 2390 gBondPerfTca15MinESCrossing notification MAY be generated if 2391 enabled by gBondPerfTcaEnable. 2392 At most one notification can be sent per interval. 2393 Setting this attribute to zero (default) effectively disables 2394 gBondPerfTca15MinESCrossing notification. 2396 This object maps to the TR-159 attribute 2397 aGroupPerfThreshold15MinES." 2398 REFERENCE 2399 "[TR-159] 5.5.1.39" 2400 ::= { gBondPortPerfTcaConfProfileEntry 2 } 2402 gBondPerfThreshold15MinSES OBJECT-TYPE 2403 SYNTAX HCPerfIntervalThreshold 2404 MAX-ACCESS read-create 2405 STATUS current 2406 DESCRIPTION 2407 "A desired threshold for the number of Severely Errored Seconds 2408 (SES) within any given 15-minute performance data collection 2409 interval. 2410 If the number of SESs in a particular 15-minute collection 2411 interval reaches or exceeds this value, a 2412 gBondPerfTca15MinSESCrossing notification MAY be generated if 2413 enabled by gBondPerfTcaEnable. 2414 At most one notification can be sent per interval. 2415 Setting this attribute to zero (default) effectively disables 2416 gBondPerfTca15MinSESCrossing notification. 2418 This object maps to the TR-159 attribute 2419 aGroupPerfThreshold15MinSES." 2420 REFERENCE 2421 "[TR-159] 5.5.1.40" 2422 ::= { gBondPortPerfTcaConfProfileEntry 3 } 2424 gBondPerfThreshold15MinUAS OBJECT-TYPE 2425 SYNTAX HCPerfIntervalThreshold 2426 MAX-ACCESS read-create 2427 STATUS current 2428 DESCRIPTION 2429 "A desired threshold for the number of Unavailable Seconds (UAS) 2430 within any given 15-minute performance data collection interval. 2431 If the number of UASs in a particular 15-minute collection 2432 interval reaches or exceeds this value, a 2433 gBondPerfTca15MinUASCrossing notification MAY be generated if 2434 enabled by gBondPerfTcaEnable. 2435 At most one notification can be sent per interval. 2436 Setting this attribute to zero (default) effectively disables 2437 gBondPerfTca15MinUASCrossing notification. 2439 This object maps to the TR-159 attribute 2440 aGroupPerfThreshold15MinUAS." 2441 REFERENCE 2442 "[TR-159] 5.5.1.41" 2443 ::= { gBondPortPerfTcaConfProfileEntry 4 } 2445 gBondPerfThreshold1DayES OBJECT-TYPE 2446 SYNTAX GBondPerf1DayIntervalThreshold 2447 MAX-ACCESS read-create 2448 STATUS current 2449 DESCRIPTION 2450 "A desired threshold for the number of Errored Seconds (ES) 2451 within any given 1-day performance data collection interval. 2452 If the number of ESs in a particular 1-day collection interval 2453 reaches or exceeds this value, a gBondPerfTca1DayESCrossing 2454 notification MAY be generated if enabled by gBondPerfTcaEnable. 2455 At most one notification can be sent per interval. 2456 Setting this attribute to zero (default) effectively disables 2457 gBondPerfTca1DayESCrossing notification. 2459 This object maps to the TR-159 attribute 2460 aGroupPerfThreshold1DayES." 2461 REFERENCE 2462 "[TR-159] 5.5.1.51" 2463 ::= { gBondPortPerfTcaConfProfileEntry 5 } 2465 gBondPerfThreshold1DaySES OBJECT-TYPE 2466 SYNTAX GBondPerf1DayIntervalThreshold 2467 MAX-ACCESS read-create 2468 STATUS current 2469 DESCRIPTION 2470 "A desired threshold for the number of Severely Errored Seconds 2471 (SES) within any given 1-day performance data collection 2472 interval. 2473 If the number of SESs in a particular 1-day collection interval 2474 reaches or exceeds this value, a gBondPerfTca1DaySESCrossing 2475 notification MAY be generated if enabled by gBondPerfTcaEnable. 2476 At most one notification can be sent per interval. 2477 Setting this attribute to zero (default) effectively disables 2478 gBondPerfTca1DaySESCrossing notification. 2480 This object maps to the TR-159 attribute 2481 aGroupPerfThreshold1DaySES." 2482 REFERENCE 2483 "[TR-159] 5.5.1.52" 2484 ::= { gBondPortPerfTcaConfProfileEntry 6 } 2486 gBondPerfThreshold1DayUAS OBJECT-TYPE 2487 SYNTAX GBondPerf1DayIntervalThreshold 2488 MAX-ACCESS read-create 2489 STATUS current 2490 DESCRIPTION 2491 "A desired threshold for the number of Unavailable Seconds (UAS) 2492 within any given 1-day performance data collection interval. 2493 If the number of UASs in a particular 1-day collection interval 2494 reaches or exceeds this value, a gBondPerfTca1DayUASCrossing 2495 notification MAY be generated if enabled by gBondPerfTcaEnable. 2496 At most one notification can be sent per interval. 2497 Setting this attribute to zero (default) effectively disables 2498 gBondPerfTca1DayUASCrossing notification. 2500 This object maps to the TR-159 attribute 2501 aGroupPerfThreshold1DayUAS." 2502 REFERENCE 2503 "[TR-159] 5.5.1.53" 2504 ::= { gBondPortPerfTcaConfProfileEntry 7 } 2506 gBondPerfTcaConfProfileRowStatus OBJECT-TYPE 2507 SYNTAX RowStatus 2508 MAX-ACCESS read-create 2509 STATUS current 2510 DESCRIPTION 2511 "This object controls the creation, modification, or deletion 2512 of the associated entry in the gBondPortPerfTcaConfProfileTable 2513 per the semantics of RowStatus. 2515 If an 'active' entry is referenced via gBondPerfTcaConfProfile 2516 instance(s), the entry MUST remain 'active'. 2518 An 'active' entry SHALL NOT be modified. In order to modify an 2519 existing entry, it MUST be taken out of service (by setting 2520 this object to 'notInService'), modified, and set 'active' 2521 again." 2522 ::= { gBondPortPerfTcaConfProfileEntry 8 } 2524 -- The BCE group 2526 gBondBceConfTable OBJECT-TYPE 2527 SYNTAX SEQUENCE OF GBondBceConfEntry 2528 MAX-ACCESS not-accessible 2529 STATUS current 2530 DESCRIPTION 2531 "Table for Configuration of G.Bond common aspects for the 2532 Bonding Channel Entity (BCE) ports (modems/channels). 2534 Entries in this table MUST be maintained in a persistent 2535 manner." 2536 ::= { gBondBce 1 } 2538 gBondBceConfEntry OBJECT-TYPE 2539 SYNTAX GBondBceConfEntry 2540 MAX-ACCESS not-accessible 2541 STATUS current 2542 DESCRIPTION 2543 "An entry in the G.Bond BCE Configuration table. 2544 Each entry represents common aspects of a G.Bond BCE port 2545 indexed by the ifIndex. Note that a G.Bond BCE port can be 2546 stacked below a single GBS port, also indexed by ifIndex, 2547 possibly together with other BCE ports if GAF is enabled." 2548 INDEX { ifIndex } 2549 ::= { gBondBceConfTable 1 } 2551 GBondBceConfEntry ::= 2552 SEQUENCE { 2553 gBondBceRemoteDiscoveryCode PhysAddress 2554 } 2556 gBondBceRemoteDiscoveryCode OBJECT-TYPE 2557 SYNTAX PhysAddress (SIZE(0|6)) 2558 MAX-ACCESS read-write 2559 STATUS current 2560 DESCRIPTION 2561 "A Remote Discovery Code of the BCE port at CO. 2562 A 6 octet long Discovery Code of the peer GBS connected via 2563 the BCE. 2564 Reading this object results in a Discovery Get operation. 2565 Setting this object to all zeroes results in a Discovery 2566 Clear_if_Same operation (the value of gBondDiscoveryCode 2567 at the peer GBS SHALL be the same as gBondDiscoveryCode of 2568 the local GBS associated with the BCE for the operation to 2569 succeed). 2570 Writing a non-zero value to this object results in a 2571 Discovery Set_if_Clear operation. 2572 A zero-length octet string SHALL be returned on an attempt to 2573 read this object when GAF aggregation is not enabled. 2575 This object is irrelevant in BCE-R port subtypes (CPE side): 2576 in this case a zero length octet string SHALL be returned on 2577 an attempt to read this object, writing to this object SHALL 2578 be rejected. 2580 Discovery MUST be performed when the link is Down. 2581 Attempts to change this object MUST be rejected (in case of 2582 SNMP with the error inconsistentValue), if the link is Up or 2583 Initializing. 2585 This object maps to the TR-159 attribute 2586 aLineRemoteDiscoveryCode." 2587 REFERENCE 2588 "[TR-159] 5.5.6.7" 2589 ::= { gBondBceConfEntry 1 } 2591 -- 2592 -- Conformance Statements 2593 -- 2595 gBondGroups OBJECT IDENTIFIER ::= { gBondConformance 1 } 2597 gBondCompliances OBJECT IDENTIFIER ::= { gBondConformance 2 } 2599 -- Object Groups 2601 gBondBasicGroup OBJECT-GROUP 2602 OBJECTS { 2603 gBondOperScheme, 2604 gBondUpDataRate, 2605 gBondDnDataRate, 2606 gBondTargetUpDataRate, 2607 gBondTargetDnDataRate, 2608 gBondOperScheme, 2609 gBondCapacity, 2610 gBondNumBCEs, 2611 gBondPortSide, 2612 gBondFltStatus 2613 } 2614 STATUS current 2615 DESCRIPTION 2616 "A collection of objects representing management information 2617 common to all types of G.Bond ports." 2618 ::= { gBondGroups 1 } 2620 gBondDiscoveryGroup OBJECT-GROUP 2621 OBJECTS { 2622 gBondPeerOperScheme, 2623 gBondPeerCapacity, 2624 gBondDiscoveryCode, 2625 gBondBceRemoteDiscoveryCode 2626 } 2627 STATUS current 2628 DESCRIPTION 2629 "A collection of objects supporting OPTIONAL G.Bond discovery 2630 in G.Bond ports." 2631 ::= { gBondGroups 2 } 2633 gBondMultiSchemeGroup OBJECT-GROUP 2634 OBJECTS { 2635 gBondSchemesSupported, 2636 gBondPeerSchemesSupported, 2637 gBondAdminScheme, 2638 gBondPeerAdminScheme 2639 } 2640 STATUS current 2641 DESCRIPTION 2642 "A collection of objects providing OPTIONAL management 2643 information for G.Bond ports supporting multiple bonding 2644 schemes." 2645 ::= { gBondGroups 3 } 2647 gBondTcaConfGroup OBJECT-GROUP 2648 OBJECTS { 2649 gBondThreshLowUpRate, 2650 gBondThreshLowDnRate, 2651 gBondLowRateCrossingEnable 2652 } 2653 STATUS current 2654 DESCRIPTION 2655 "A collection of objects required for configuration of alarm 2656 thresholds and notifications in G.Bond ports." 2657 ::= { gBondGroups 4 } 2659 gBondTcaNotificationGroup NOTIFICATION-GROUP 2660 NOTIFICATIONS { 2661 gBondLowUpRateCrossing, 2662 gBondLowDnRateCrossing 2663 } 2664 STATUS current 2665 DESCRIPTION 2666 "This group supports notifications of significant conditions 2667 (non-PM threshold crossing alerts) associated with G.Bond ports." 2668 ::= { gBondGroups 5 } 2670 gBondPerfCurrGroup OBJECT-GROUP 2671 OBJECTS { 2672 gBondPerfES, 2673 gBondPerfSES, 2674 gBondPerfUAS, 2675 gBondPerf15MinValidIntervals, 2676 gBondPerf15MinInvalidIntervals, 2677 gBondPerfCurr15MinTimeElapsed, 2678 gBondPerfCurr15MinES, 2679 gBondPerfCurr15MinSES, 2680 gBondPerfCurr15MinUAS, 2681 gBondPerf1DayValidIntervals, 2682 gBondPerf1DayInvalidIntervals, 2683 gBondPerfCurr1DayTimeElapsed, 2684 gBondPerfCurr1DayES, 2685 gBondPerfCurr1DaySES, 2686 gBondPerfCurr1DayUAS 2687 } 2688 STATUS current 2689 DESCRIPTION 2690 "A collection of objects supporting OPTIONAL current Performance 2691 Monitoring information for G.Bond ports." 2692 ::= { gBondGroups 6 } 2694 gBondPerf15MinGroup OBJECT-GROUP 2695 OBJECTS { 2696 gBondPerf15MinIntervalMoniTime, 2697 gBondPerf15MinIntervalES, 2698 gBondPerf15MinIntervalSES, 2699 gBondPerf15MinIntervalUAS, 2700 gBondPerf15MinIntervalValid 2701 } 2702 STATUS current 2703 DESCRIPTION 2704 "A collection of objects supporting OPTIONAL historical 2705 Performance Monitoring information for G.Bond ports, during 2706 previous 15-minute intervals ." 2707 ::= { gBondGroups 7 } 2709 gBondPerf1DayGroup OBJECT-GROUP 2710 OBJECTS { 2711 gBondPerf1DayIntervalMoniTime, 2712 gBondPerf1DayIntervalES, 2713 gBondPerf1DayIntervalSES, 2714 gBondPerf1DayIntervalUAS, 2715 gBondPerf1DayIntervalValid 2716 } 2717 STATUS current 2718 DESCRIPTION 2719 "A collection of objects supporting OPTIONAL historical 2720 Performance Monitoring information for G.Bond ports, during 2721 previous 1-day intervals ." 2722 ::= { gBondGroups 8 } 2724 gBondPerfTcaConfGroup OBJECT-GROUP 2725 OBJECTS { 2726 gBondPerfTcaConfProfile, 2727 gBondPerfTcaEnable, 2728 gBondPerfThreshold15MinES, 2729 gBondPerfThreshold15MinSES, 2730 gBondPerfThreshold15MinUAS, 2731 gBondPerfThreshold1DayES, 2732 gBondPerfThreshold1DaySES, 2733 gBondPerfThreshold1DayUAS, 2734 gBondPerfTcaConfProfileRowStatus 2735 } 2736 STATUS current 2737 DESCRIPTION 2738 "A collection of objects required for configuration of 2739 Performance Monitoring Threshold Crossing Alert notifications 2740 in G.Bond ports." 2741 ::= { gBondGroups 9 } 2743 gBondPerfTcaNotificationGroup NOTIFICATION-GROUP 2744 NOTIFICATIONS { 2745 gBondPerfTca15MinESCrossing, 2746 gBondPerfTca15MinSESCrossing, 2747 gBondPerfTca15MinUASCrossing, 2748 gBondPerfTca1DayESCrossing, 2749 gBondPerfTca1DaySESCrossing, 2750 gBondPerfTca1DayUASCrossing 2751 } 2752 STATUS current 2753 DESCRIPTION 2754 "This group supports notifications of performance monitoring 2755 thresholds crossing alerts associated with G.Bond ports." 2756 ::= { gBondGroups 10 } 2758 -- Compliance Statements 2760 gBondCompliance MODULE-COMPLIANCE 2761 STATUS current 2762 DESCRIPTION 2763 "The compliance statement for G.Bond interfaces. 2764 Compliance with the following external compliance statements 2765 is REQUIRED: 2767 MIB Module Compliance Statement 2768 ---------- -------------------- 2769 IF-MIB ifCompliance3 2771 Compliance with the following external compliance statements 2772 is OPTIONAL for implementations supporting bonding with 2773 flexible cross-connect between the GBS and BCE ports: 2775 MIB Module Compliance Statement 2776 ---------- -------------------- 2777 IF-INVERTED-STACK-MIB ifInvCompliance 2778 IF-CAP-STACK-MIB ifCapStackCompliance" 2780 MODULE -- this module 2781 MANDATORY-GROUPS { 2782 gBondBasicGroup, 2783 gBondTcaConfGroup, 2784 gBondTcaNotificationGroup 2785 } 2787 GROUP gBondDiscoveryGroup 2788 DESCRIPTION 2789 "Support for this group is only required for implementations 2790 supporting G.Bond Discovery function." 2792 GROUP gBondMultiSchemeGroup 2793 DESCRIPTION 2794 "Support for this group is only required for implementations 2795 supporting multiple bonding schemes." 2797 GROUP gBondPerfCurrGroup 2798 DESCRIPTION 2799 "Support for this group is only required for implementations 2800 supporting Performance Monitoring." 2802 GROUP gBondPerf15MinGroup 2803 DESCRIPTION 2804 "Support for this group is only required for implementations 2805 supporting 15-min historical Performance Monitoring." 2807 GROUP gBondPerf1DayGroup 2808 DESCRIPTION 2809 "Support for this group is only required for implementations 2810 supporting 1-day historical Performance Monitoring." 2812 GROUP gBondPerfTcaConfGroup 2813 DESCRIPTION 2814 "Support for this group is only required for implementations 2815 supporting Performance Monitoring Threshold Crossing Alert 2816 notifications." 2818 GROUP gBondPerfTcaNotificationGroup 2819 DESCRIPTION 2820 "Support for this group is only required for implementations 2821 supporting Performance Monitoring Threshold Crossing Alert 2822 notifications." 2824 ::= { gBondCompliances 1 } 2825 END 2827 7. Security Considerations 2829 There is a number of managed objects defined in the GBOND-MIB module 2830 that have a MAX-ACCESS clause of read-write or read-create. Most 2831 objects are writable only when the link is Down. Writing to these 2832 objects can have potentially disruptive effects on network operation, 2833 for example: 2835 o Changing of gBondAdminScheme MAY lead to a potential locking of 2836 the link, if the peer device does not support desired bonding 2837 scheme. 2839 o Changing of gBondDiscoveryCode, before the discovery operation, 2840 MAY lead to a wrongful discovery, for example when two CO ports 2841 are connected to the same multi-channel RT port, while both CO 2842 ports have the same discovery register value. 2844 o Changing GBS configuration parameters (e.g., profile of a GBS via 2845 gBondAdminProfile) MAY lead to anything from link quality and rate 2846 degradation to a complete link initialization failure, as ability 2847 of a G.Bond port to support a particular configuration depends on 2848 the copper environment. 2850 o Activation of a specific line/channel MAY cause a severe 2851 degradation of service for another G.Bond port, whose channel(s) 2852 MAY be affected by the cross-talk from the newly activated 2853 channel. 2855 o Removal of a channel from an operationally 'up' G.Bond port, 2856 aggregating several channels, MAY cause port's rate degradation 2858 The user of the GBOND-MIB module must therefore be aware that support 2859 for SET operations in a non-secure environment without proper 2860 protection can have a negative effect on network operations. 2862 The readable objects in the GBOND-MIB module (i.e., those with MAX- 2863 ACCESS other than not-accessible) may be considered sensitive in some 2864 environments since, collectively, they provide information about the 2865 performance of network interfaces and can reveal some aspects of 2866 their configuration. In particular, since a bonded xDSL port can be 2867 comprised of multiple Unshielded Twisted Pair (UTP) voice grade 2868 copper, located in the same bundle with other pairs belonging to 2869 another operator/customer, it is theoretically possible to eavesdrop 2870 to a G.Bond transmission, simply by "listening" to a cross-talk from 2871 the bonded pairs, especially if the parameters of the G.Bond link in 2872 question are known. 2874 In such environments it is important to control also GET and NOTIFY 2875 access to these objects and possibly even to encrypt their values 2876 when sending them over the network via SNMP. 2878 SNMP versions prior to SNMPv3 did not include adequate security. 2879 Even if the network itself is secure (for example by using IPSec), 2880 even then, there is no control as to who on the secure network is 2881 allowed to access and GET/SET (read/change/create/delete) the objects 2882 in this MIB module. 2884 It is RECOMMENDED that implementers consider the security features as 2885 provided by the SNMPv3 framework (see [RFC3410], section 8), 2886 including full support for the SNMPv3 cryptographic mechanisms (for 2887 authentication and privacy). 2889 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2890 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2891 enable cryptographic security. It is then a customer/operator 2892 responsibility to ensure that the SNMP entity giving access to an 2893 instance of this MIB module is properly configured to give access to 2894 the objects only to those principals (users) that have legitimate 2895 rights to indeed GET or SET (change/create/delete) them. 2897 8. IANA Considerations 2899 Three new values of IANAifType: g9981, g9982 and g9982 SHALL be 2900 defined by the IANA [1] in the IANAifType-MIB module 2901 [IANAifType-MIB], before this document is published as an RFC. 2903 Additionally, an object identifier for gBondMIB MODULE-IDENTITY SHALL 2904 be allocated by IANA in the MIB-2 transmission sub-tree, before this 2905 document is published. 2907 9. Acknowledgments 2909 This document was produced by the [ADSLMIB] working group. 2911 10. References 2913 10.1. Normative References 2915 [RFC2119] Bradner, S., "Key words for use in 2916 RFCs to Indicate Requirement 2917 Levels", BCP 14, RFC 2119, 2918 March 1997. 2920 [RFC2578] McCloghrie, K., Ed., Perkins, D., 2921 Ed., and J. Schoenwaelder, Ed., 2922 "Structure of Management 2923 Information Version 2 (SMIv2)", 2924 STD 58, RFC 2578, April 1999. 2926 [RFC2579] McCloghrie, K., Ed., Perkins, D., 2927 Ed., and J. Schoenwaelder, Ed., 2928 "Textual Conventions for SMIv2", 2929 STD 58, RFC 2579, April 1999. 2931 [RFC2580] McCloghrie, K., Perkins, D., and 2932 J. Schoenwaelder, "Conformance 2933 Statements for SMIv2", STD 58, 2934 RFC 2580, April 1999. 2936 [RFC2863] McCloghrie, K. and F. Kastenholz, 2937 "The Interfaces Group MIB", 2938 RFC 2863, June 2000. 2940 [RFC3411] Harrington, D., Presuhn, R., and 2941 B. Wijnen, "An Architecture for 2942 Describing Simple Network 2943 Management Protocol (SNMP) 2944 Management Frameworks", STD 62, 2945 RFC 3411, December 2002. 2947 [RFC3705] Ray, B. and R. Abbi, "High 2948 Capacity Textual Conventions for 2949 MIB Modules Using Performance 2950 History Based on 15 Minute 2951 Intervals", RFC 3705, 2952 February 2004. 2954 [TR-159] Beili, E. and M. Morgenstern, 2955 "Management Framework for xDSL 2956 Bonding", Broadband Forum 2957 technical report TR-159, 2958 December 2008. 2960 10.2. Informative References 2962 [802.3] IEEE, "IEEE Standard for 2963 Information technology - 2964 Telecommunications and information 2965 exchange between systems - Local 2966 and metropolitan area networks - 2967 Specific requirements - Part 3: 2968 Carrier Sense Multiple Access with 2969 Collision Detection (CSMA/CD) 2970 Access Method and Physical Layer 2971 Specifications", IEEE Std 802.3- 2972 2005, December 2005. 2974 [ADSLMIB] IETF, "ADSL MIB (adslmib) 2975 Charter", . 2979 [G.991.2] ITU-T, "Single-pair High-speed 2980 Digital Subscriber Line (SHDSL) 2981 transceivers", ITU-T 2982 Recommendation G.991.2, 2983 December 2003, . 2986 [G.993.1] ITU-T, "Very High speed Digital 2987 Subscriber Line transceivers", 2988 ITU-T Recommendation G.993.1, 2989 June 2004, . 2992 [G.994.1] ITU-T, "Handshake procedures for 2993 digital subscriber line (DSL) 2994 transceivers", ITU-T 2995 Recommendation G.994.1, 2996 February 2007, . 2999 [G.998.1] ITU-T, "ATM-based multi-pair 3000 bonding", ITU-T 3001 Recommendation G.998.1, 3002 January 2005, . 3005 [G.998.2] ITU-T, "Ethernet-based multi-pair 3006 bonding", ITU-T 3007 Recommendation G.998.2, 3008 January 2005, . 3011 [G.998.3] ITU-T, "Multi-pair bonding using 3012 time-division inverse 3013 multiplexing", ITU-T 3014 Recommendation G.998.3, 3015 January 2005, . 3018 [I-D.ietf-adslmib-gbond-atm-mib] Beili, E., "ATM-based xDSL Bonded 3019 Interfaces MIB", draft-ietf- 3020 adslmib-gbond-atm-mib-03 (work in 3021 progress), March 2011. 3023 [I-D.ietf-adslmib-gbond-eth-mib] Beili, E. and M. Morgenstern, 3024 "Ethernet-based xDSL Bonded 3025 Interfaces MIB", draft-ietf- 3026 adslmib-gbond-eth-mib-03 (work in 3027 progress), March 2011. 3029 [I-D.ietf-adslmib-gbond-tdim-mib] Beili, E., "TDIM-based xDSL Bonded 3030 Interfaces MIB", draft-ietf- 3031 adslmib-gbond-tdim-mib-05 (work in 3032 progress), March 2011. 3034 [IANAifType-MIB] Internet Assigned Numbers 3035 Authority (IANA), "IANAifType 3036 Textual Convention definition", . 3040 [RFC2864] McCloghrie, K. and G. Hanson, "The 3041 Inverted Stack Table Extension to 3042 the Interfaces Group MIB", 3043 RFC 2864, June 2000. 3045 [RFC3410] Case, J., Mundy, R., Partain, D., 3046 and B. Stewart, "Introduction and 3047 Applicability Statements for 3048 Internet-Standard Management 3049 Framework", RFC 3410, 3050 December 2002. 3052 [RFC3440] Ly, F. and G. Bathrick, 3053 "Definitions of Extension Managed 3054 Objects for Asymmetric Digital 3055 Subscriber Lines", RFC 3440, 3056 December 2002. 3058 [RFC3593] Tesink, K., "Textual Conventions 3059 for MIB Modules Using Performance 3060 History Based on 15 Minute 3061 Intervals", RFC 3593, 3062 September 2003. 3064 [RFC3728] Ray, B. and R. Abbi, "Definitions 3065 of Managed Objects for Very High 3066 Speed Digital Subscriber Lines 3067 (VDSL)", RFC 3728, February 2004. 3069 [RFC4181] Heard, C., "Guidelines for Authors 3070 and Reviewers of MIB Documents", 3071 BCP 111, RFC 4181, September 2005. 3073 [RFC4319] Sikes, C., Ray, B., and R. Abbi, 3074 "Definitions of Managed Objects 3075 for High Bit-Rate DSL - 2nd 3076 generation (HDSL2) and Single-Pair 3077 High-Speed Digital Subscriber Line 3078 (SHDSL) Lines", RFC 4319, 3079 December 2005. 3081 [RFC4706] Morgenstern, M., Dodge, M., 3082 Baillie, S., and U. Bonollo, 3083 "Definitions of Managed Objects 3084 for Asymmetric Digital Subscriber 3085 Line 2 (ADSL2)", RFC 4706, 3086 November 2006. 3088 [RFC4836] Beili, E., "Definitions of Managed 3089 Objects for IEEE 802.3 Medium 3090 Attachment Units (MAUs)", 3091 RFC 4836, April 2007. 3093 [RFC5066] Beili, E., "Ethernet in the First 3094 Mile Copper (EFMCu) Interfaces 3095 MIB", RFC 5066, November 2007. 3097 [RFC5650] Morgenstern, M., Baillie, S., and 3098 U. Bonollo, "Definitions of 3099 Managed Objects for Very High 3100 Speed Digital Subscriber Line 2 3101 (VDSL2)", RFC 5650, 3102 September 2009. 3104 [af-phy-0086] ATM Forum, "Inverse Multiplexing 3105 for ATM (IMA) Specification 3106 Version 1.1", ATM Forum 3107 specification af-pfy-0086.001, 3108 March 1999. 3110 URIs 3112 [1] 3114 Authors' Addresses 3116 Edward Beili 3117 Actelis Networks 3118 25 Bazel St. 3119 Petach-Tikva 49103 3120 Israel 3122 Phone: +972-3-924-3491 3123 EMail: edward.beili@actelis.com 3125 Moti Morgenstern 3126 ECI Telecom 3127 30 Hasivim St. 3128 Petach-Tikva 4951169 3129 Israel 3131 Phone: +972-3-926-6258 3132 EMail: moti.morgenstern@ecitele.com