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