idnits 2.17.1 draft-ietf-adslmib-gbond-mib-09.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 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 (Feb 13, 2012) is 4456 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 3069, but no explicit reference was found in the text == Unused Reference: 'G.993.1' is defined on line 3076, 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-05 == Outdated reference: A later version (-08) exists of draft-ietf-adslmib-gbond-eth-mib-05 == Outdated reference: A later version (-08) exists of draft-ietf-adslmib-gbond-tdim-mib-07 Summary: 0 errors (**), 0 flaws (~~), 7 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: August 16, 2012 ECI Telecom 6 Feb 13, 2012 8 xDSL multi-pair bonding (G.Bond) MIB 9 draft-ietf-adslmib-gbond-mib-09.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 August 16, 2012. 39 Copyright Notice 41 Copyright (c) 2012 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents 46 (http://trustee.ietf.org/license-info) in effect on the date of 47 publication of this document. Please review these documents 48 carefully, as they describe your rights and restrictions with respect 49 to this document. Code Components extracted from this document must 50 include Simplified BSD License text as described in Section 4.e of 51 the Trust Legal Provisions and are provided without warranty as 52 described in the Simplified BSD License. 54 Table of Contents 56 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 57 2. The Internet-Standard Management Framework . . . . . . . . . . 4 58 3. The DSL Forum Management Framework for xDSL Bonding . . . . . 4 59 4. Relationship to Other MIB modules . . . . . . . . . . . . . . 4 60 4.1. Relationship to Interfaces Group MIB module . . . . . . . 5 61 4.1.1. Layering Model . . . . . . . . . . . . . . . . . . . . 5 62 4.1.2. xDSL Bonding . . . . . . . . . . . . . . . . . . . . . 7 63 4.1.3. Discovery Operation . . . . . . . . . . . . . . . . . 7 64 4.1.4. G.Bond ports initialization . . . . . . . . . . . . . 9 65 4.1.5. Usage of ifTable . . . . . . . . . . . . . . . . . . . 10 66 4.2. Relationship to G.Bond ATM, ETH and TDIM MIB modules . . . 11 67 4.3. Relationship to xDSL MIB modules . . . . . . . . . . . . . 12 68 5. MIB Structure . . . . . . . . . . . . . . . . . . . . . . . . 12 69 5.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . 12 70 5.2. Performance Monitoring . . . . . . . . . . . . . . . . . . 12 71 5.3. Mapping of DSL Forum TR-159 Managed Objects . . . . . . . 13 72 6. xDSL Multi-pair Bonding MIB Definitions . . . . . . . . . . . 17 73 7. Security Considerations . . . . . . . . . . . . . . . . . . . 62 74 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 63 75 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 63 76 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 64 77 10.1. Normative References . . . . . . . . . . . . . . . . . . . 64 78 10.2. Informative References . . . . . . . . . . . . . . . . . . 65 80 1. Introduction 82 The xDSL Multi-Pair Bonding, allows a service provider to provide 83 high bandwidth services to business and residential customers over 84 multiple xDSL lines, with greater speed and resiliency, than the 85 service over a single xDSL line, bridging the gap between xDSL and 86 fiber-based transport. 88 There are three xDSL Multi-Pair Bonding schemes, also known under 89 collective name G.Bond: 91 o The ATM-Based Multi-Pair Bonding, specified in ITU-T G.998.1 92 recommendation [G.998.1], which defines a method for bonding (or 93 aggregating) of multiple xDSL lines (or individual bearer channels 94 in multiple xDSL lines) into a single bi-directional logical link 95 carrying an ATM stream. This specification can be viewed as an 96 evolution of the legacy Inverse Multiplexing over ATM (IMA) 97 technology [af-phy-0086], applied to xDSL with variable rates on 98 each line/bearer channel. 100 o The Ethernet-Based Multi-Pair Bonding, specified in ITU-T G.998.2 101 recommendation [G.998.2], which defines a method for bonding (or 102 aggregating) of multiple xDSL lines (or individual bearer channels 103 in multiple xDSL lines) into a single bi-directional logical link 104 carrying an Ethernet stream. This specification can be viewed as 105 IEEE 802.3-2005 [802.3] Clause 61 Physical Medium Entity (PME) 106 Aggregation, generalized to work over any xDSL technology 107 (2Base-TL and 10Pass-TS interfaces defined by IEEE use G.SHDSL and 108 VDSL technology respectively). 110 o The Multi-pair bonding using time-division inverse multiplexing 111 (TDIM), specified in ITU-T G.998.3 recommendation [G.998.3], which 112 defines a method for bonding (or aggregating) of multiple xDSL 113 lines into a single bi-directional logical link carrying a mix of 114 various traffic streams (e.g., Ethernet, ATM, TDM). 116 Architecturally all three bonding schemes define a new "bonded" 117 Transport Protocol Specific - Transmission Convergence (TPS-TC) sub- 118 layer, stacked above multiple ATM-TC, Ethernet/PTM-TC or STM-TC 119 (clear channel) sub-layers for the ATM, Ethernet or TDIM bonding 120 respectively. Each underlying TPS-TC sub-layer represents a protocol 121 specific interface to an xDSL line or an individual bearer channel of 122 an xDSL line. Bonding of multiple bearer channels in the same xDSL 123 line is not allowed. 125 All schemes allow bonding of up to 32 individual line/channel sub- 126 layers with variable rates, providing common functionality for the 127 configuration, initialization, operation and monitoring of the bonded 128 link. 130 This document defines a MIB module common to all 3 schemes. 131 Additional managed objects, specific to each bonding technology, are 132 defined in GBOND-ATM-MIB [I-D.ietf-adslmib-gbond-atm-mib], GBOND-ETH- 133 MIB [I-D.ietf-adslmib-gbond-eth-mib] and GBOND-TDIM-MIB 134 [I-D.ietf-adslmib-gbond-tdim-mib] modules. 136 2. The Internet-Standard Management Framework 138 For a detailed overview of the documents that describe the current 139 Internet-Standard Management Framework, please refer to section 7 of 140 RFC 3410 [RFC3410]. 142 Managed objects are accessed via a virtual information store, termed 143 the Management Information Base or MIB. MIB objects are generally 144 accessed through the Simple Network Management Protocol (SNMP). 145 Objects in the MIB are defined using the mechanisms defined in the 146 Structure of Management Information (SMI). This document specifies a 147 MIB module that is compliant to the SMIv2, which is described in STD 148 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 149 2580 [RFC2580]. 151 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 152 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 153 "OPTIONAL" in this document are to be interpreted as described in RFC 154 2119 [RFC2119]. 156 3. The DSL Forum Management Framework for xDSL Bonding 158 This document makes use of the DSL Forum technical report Management 159 Framework for xDSL Bonding [TR-159], defining a management model and 160 a hierarchy of management objects for the bonded xDSL interfaces. 162 4. Relationship to Other MIB modules 164 This section outlines the relationship of the MIB modules defined in 165 this document with other MIB modules described in the relevant RFCs. 166 Specifically, the following MIB modules are discussed: Interfaces 167 Group MIB (IF-MIB), Inverse Stack Table MIB (IF-INVERTED-STACK-MIB) 168 Interface Stack Capability MIB (IF-CAP-STACK-MIB), G.Bond scheme 169 specific modules: G.Bond/ATM (GBOND-ATM-MIB), G.Bond/Ethernet (GBOND- 170 ETH-MIB) and G.Bond/TDIM (GBOND-TDIM-MIB), and DSL specific MIB 171 modules: ADSL (ADSL-LINE-EXT-MIB), ADSL2 (ADSL2-LINE-MIB), SHDSL 172 (HDSL2-SHDSL-LINE-MIB), VDSL (VDSL-LINE-MIB) and VDSL2 (VDSL2-LINE- 173 MIB). 175 4.1. Relationship to Interfaces Group MIB module 177 A bonded xDSL port is a stacked (a.k.a. aggregated or bonded) 178 interface and as such is managed using generic interface management 179 objects defined in the IF-MIB [RFC2863]. 181 The stack management, i.e., actual connection of the sub-layers to 182 the top layer interface, is done via the ifStackTable, as defined in 183 the IF-MIB [RFC2863] and its inverse ifInvStackTable, as defined in 184 the IF-INVERTED-STACK-MIB [RFC2864]. 186 The ifCapStackTable and its inverse ifInvCapStackTable defined in the 187 IF-CAP-STACK-MIB [RFC5066], extend the stack management with an 188 ability to describe possible connections or cross-connect capability, 189 when a flexible cross-connect matrix is present between the interface 190 layers. 192 4.1.1. Layering Model 194 A G.Bond interface can aggregate up to 32 channel sub-layers, with 195 each channel representing an xDSL line or an xDSL bearer channel. 196 For the purpose of brevity we will refer to the bonded interface as 197 Generic Bonded Sub-layer (GBS) and to the channel sub-layer as 198 Bonding Channel Entity (BCE). 200 A generic G.Bond device can have a number of GBS ports, each 201 connected to a particular upper layer (e.g., Media Access Control 202 (MAC) interface for G.998.2 scheme), while simultaneously cross- 203 connected to a number of underlying BCEs, with a single GBS per BCE 204 relationship. 206 A GBS port is represented in the Interface table (ifTable) as a 207 separate interface with an ifType of g9981(263), g9982(264) or 208 g9983(265) for a particular bonding scheme. 210 Each BCE in the aggregated GBS port is represented in the ifTable as 211 a separate interface with an ifType relevant to a particular xDSL 212 technology, e.g., shdsl(169) or vdsl(97). The ifType values are 213 defined in [IANAifType-MIB]. 215 The following figure shows the layering diagram and corresponding use 216 of ifTable for the bonded xDSL interfaces: 218 .-----------------------------. - 219 | GBS | ^ 1 ifEntry 220 | (TPS-TC) | v ifType: g9981(263), g9982(264) 221 +-----------------+---+-------+ - or g9983(265) 222 | TPS-TC \ | | | ^ 223 +---------\ | | | | N ifEntry (N=1..32) 224 | PMS-TC )BCE 1 |...| BCE N | ) ifType: adsl(94), shdsl(169), 225 +---------/ | | | | vdsl(97), vdsl2(251), 226 | PMD / | | | v etc. 227 '-----------------+---+-------' - 229 BCE - Bonding Channel Entity 230 GBS - Generic Bonded Sub-layer 231 PMD - Physical Medium Dependent 232 TPS-TC - Transport Protocol Specific - Transmission Convergence 233 PMS-TC - Physical Media Specific - Transmission Convergence 235 Figure 1: Use of ifTable for bonded xDSL interfaces 237 The ifStackTable is indexed by the ifIndex values of the aggregated 238 G.Bond port (GBS) and the BCEs connected to it. ifStackTable allows a 239 Network Management application to determine which BCEs are connected 240 to a particular GBS and change connections (if supported by the 241 application). The ifInvStackTable, being an inverted version of the 242 ifStackTable, provides an efficient means for a Network Management 243 application to read a subset of the ifStackTable and thereby 244 determine which GBS runs on top of a particular BCE. 246 The ifCapStackTable defined in the IF-CAP-STACK-MIB module, specifies 247 for each higher-layer interface (e.g., GBS port) a list of lower- 248 layer interfaces (e.g., BCEs), which can possibly be cross-connected 249 to that higher-layer interface, determined by the cross-connect 250 capability of the device. This table, modeled after ifStackTable, is 251 read only, reflecting current cross-connect capability of a stacked 252 interface, which can be dynamic in some implementations (e.g., if 253 xDSL lines are located on a pluggable module and the module is pulled 254 out). Note that BCE availability per GBS, described by 255 ifCapStackTable, can be constrained by other parameters, for example 256 by aggregation capacity of a GBS or by the BCE in question being 257 already connected to another GBS. So, in order to ensure that a 258 particular BCE can be connected to the GBS, all respective parameters 259 (e.g., ifCapStackTable, ifStackTable and gBondPortCapCapacity) SHALL 260 be inspected. 262 The ifInvCapStackTable, also defined in the IF-CAP-STACK-MIB module, 263 describes which higher-layer interfaces (e.g., GBS ports) can 264 possibly be connected to a particular lower-layer interface (e.g., 265 BCE), providing inverted mapping of ifCapStackTable. While it 266 contains no additional information beyond that already contained in 267 the ifCapStackTable, the ifInvCapStackTable has the ifIndex values in 268 its INDEX clause in the reverse order, i.e., the lower-layer 269 interface first, and the higher-layer interface second, providing 270 efficient means for a Network Management application to read a subset 271 of the ifCapStackTable and thereby determine which interfaces can be 272 connected to run on top of a particular interface. 274 4.1.2. xDSL Bonding 276 The G.998.x Bonding allows a number of BCEs to be aggregated onto a 277 single logical GBS port, by splitting the incoming traffic into 278 multiple streams, transmitting each stream over a specific BCE and 279 combining the streams at the remote GBS port, preserving the original 280 traffic order. 282 The Ethernet frames MAY be fragmented before the transmission and 283 reassembled at the remote end to minimize transportation delay. 285 The Bonding is OPTIONAL, meaning that a device with a single BCE MAY 286 perform fragmentation and re-assembly if this function is supported 287 by the device. The agent is REQUIRED to indicate the Bonding 288 capability for all types of G.Bond ports (ATM, Ethernet and TDIM). 290 The GBOND-MIB module allows a Network Management application to query 291 Bonding capability and enable/disable it if supported. Note that 292 enabling Bonding effectively turns on fragmentation and re-assembly 293 function, even on a single-BCE port. 295 4.1.3. Discovery Operation 297 The G.Bond ports may optionally support discovery operation, whereby 298 BCEs, during initialization, exchange information about their 299 respective aggregation groups (GBS), via [G.994.1] handshake (G.hs) 300 protocol. This information can then be used to detect copper 301 misconnections or for an automatic assignment of the local BCEs into 302 aggregation groups instead of a fixed pre-configuration. 304 The MIB module defined in this document allow a Network Management 305 application to control G.Bond discovery mechanism and query its 306 results. 308 Two tables are used by the G.Bond discovery mechanism: ifStackTable 309 and ifCapStackTable. The following pseudo-code gives an example of 310 the discovery and automatic BCE assignment for a generic multi-GBS 311 G.Bond device, located at Central Office (CO), using objects defined 312 in this MIB module, IF-CAP-STACK-MIB and IF-MIB modules [Note that 313 automatic BCE assignment is only shown here for the purposes of the 314 example. Fixed BCE pre-assignment, manual assignment or auto- 315 assignment using an alternative internal algorithm may be chosen by a 316 particular implementation]: 318 // Go over all GBS ports in the CO device 319 FOREACH gbs[i] IN CO_device 320 { // Perform discovery and auto-assignment on GBS ports 321 // with room for more Channels 322 IF ( gbs[i].NumBCEs < gbs[i].BondCapacity ) 323 { // Assign a unique 6-octets local discovery code to the GBS 324 // e.g., MAC address of the associated port or some other 325 // unique number specifically allocated for this purpose. 326 dc = gbs[i].DiscoveryCode = MAC[i]; 327 // Go over all disconnected Channels, which can 328 // potentially be connected to the GBS 329 FOREACH bce[j] IN ifCapStackTable[gbs[i]] AND 330 NOT IN ifStackTable[gbs[i]] // not connected 331 { // Try to grab the remote RT_device, by writing the value 332 // of the local 6 Byte discovery code to the remote 333 // discovery code register (via handshake mechanism). 334 // This operation is atomic Set-if-Clear action, i.e., it 335 // would succeed only if the remote discovery register was 336 // zero. Read the remote discovery code register via Get 337 // operation to see if the RT_device, attached via the BCE 338 // is indeed marked as being the CO_device peer. 339 bce[j].RemoteDiscoveryCode = dc; // Set-if-Clear 340 r = bce[j].RemoteDiscoveryCode; // Get 341 IF ( r == dc AND gbs[i].NumBCEs < gbs[i].BondCapacity) 342 { // Remote RT_device connected via BCE[j] is/was a peer 343 // for GBS[i] and there room for another BCE in the 344 // GBS[i] aggregation group (max. Bonding capacity is 345 // not reached yet). 346 // Connect this BCE to the GBS (via ifStackTable, 347 // ifInvStackTable being inverse of ifStackTable is 348 // updated automatically, i.e., gbs[i] is auto-added 349 // to ifInvStackTable[bce[j]]) 350 ADD bce[j] TO ifStackTable[gbs[i]]; 351 gbs[i].NumBCEs = gbs[i].NumBCEs + 1; 352 // Discover all other disconnected BCEs, 353 // attached to the same RT_device and connect them to 354 // the GBS provided there is enough room for more BCEs. 355 FOREACH bce[k] IN ifCapStackTable[gbs[i]] and 356 NOT IN ifStackTable[gbs[i]] 357 { // Get Remote Discovery Code from the BCE to see if 358 // it belongs to a connected RT_device "grabbed" by 359 // the CO_device. 360 r = bce[k].RemoteDiscoveryCode; 361 IF ( r == dc AND gbs[i].NumBCEs < gbs[i].BondCapacity) 362 { // Physically connect the BCE to the GBS 363 // (gbs[i] is auto-added TO ifInvStackTable[bce[k]]) 364 ADD bce[k] TO ifStackTable[gbs[i]]; 365 gbs[i].NumBCEs = gbs[i].NumBCEs + 1; 366 } 367 } 368 } 369 // At this point we have discovered all local BCEs which 370 // are physically connected to the same remote RT_device 371 // and connected them to GBS[i]. Go to the next GBS. 372 BREAK; 373 } 374 } 375 } 377 An SNMP Agent for a G.Bond device builds ifCapStackTable and its 378 inverse ifInvCapStackTable on device initialization, according to the 379 cross-connect capabilities of the device. 381 Adding a BCE to the ifStackTable row for a specific GBS, involves 382 actual connection of the BCE to the GBS. 384 Note that GBS port does not have to be operationally 'down' for the 385 connection to succeed. In fact, a dynamic BCE addition (and removal) 386 MAY be implemented with an available BCE being initialized first (by 387 setting its ifAdminStatus to 'up') and then added to an operationally 388 'up' GBS port, by modifying a respective ifStackTable (and respective 389 ifInvStackTable) entry. 391 It is RECOMMENDED that a removal of the last operationally 'up' BCE 392 from an operationally 'up' GBS, i.e. modification of a respective 393 entry in ifStackTable and a corresponding entry in ifInvStackTable, 394 would be rejected by the implementation (in case of SNMP with the 395 error inconsistentValue), as this action would completely drop the 396 link. 398 In addition to the standard handshake-based discovery described 399 above, [G.998.2] defines an optional frame-based discovery and pair 400 management. These frame-based methods are discussed in 401 [I-D.ietf-adslmib-gbond-eth-mib]. 403 4.1.4. G.Bond ports initialization 405 G.Bond ports being built on top of xDSL technology, require a lengthy 406 initialization or 'training' process, before any data can pass. 408 During this initialization both ends of a link (peers) work 409 cooperatively to achieve required data rate on a particular copper 410 pair. Sometimes, when the copper line is too long or the noise on 411 the line is too high, that 'training' process may fail to achieve a 412 specific target rate with required characteristics. 414 The ifAdminStatus object from the IF-MIB, controls the desired state 415 of a GBS with all the BCEs connected to it or of an individual BCE 416 port. Setting this object to 'up' instructs a particular GBS or a 417 BCE to start initialization process, which may take tens of seconds 418 for G.Bond ports. The ifOperStatus object from the IF-MIB shows the 419 operational state of an interface for GBS, extended by 420 gBondPortStatFltStatus object defined in this document, and 421 corresponding *Status object from a relevant xDSL line MIB for BCE 422 interfaces. 424 A disconnected BCE may be initialized by changing the ifAdminState 425 from 'down' to 'up'. Changing the ifAdminState to 'up' on the GBS 426 initializes all BCEs connected to that particular GBS. Note that in 427 case of bonding some interfaces may fail to initialize while others 428 succeed. The GBS is considered operationally 'up' if at least one 429 bonded BCE is operationally 'up'. When all BCEs connected to the GBS 430 are 'down' the GBS SHALL be considered operationally 431 'lowerLayerDown'. The GBS SHALL be considered operationally 432 'notPresent' if it is not connected to any BCE. The GBS/BCE 433 interface SHALL remain operationally 'down' during initialization, 434 indicated by 'init' value of the gBondPortStatFltStatus object. 436 4.1.5. Usage of ifTable 438 Both BCE and GBS interfaces are managed using interface specific 439 management objects defined in the GBOND-MIB module and generic 440 interface objects from the ifTable of IF-MIB, with all management 441 table entries referenced by the interface index ifIndex. 443 The following table summarizes G.Bond specific interpretations for 444 some of the ifTable objects specified by the mandatory 445 ifGeneralInformationGroup: 447 +---------------+---------------------------------------------------+ 448 | IF-MIB object | G.Bond interpretation | 449 +---------------+---------------------------------------------------+ 450 | ifIndex | Interface index. Note that each BCE and each GBS | 451 | | in the G.Bond PHY MUST have a unique index, as | 452 | | there are some GBS and BCE specific attributes | 453 | | accessible only on the GBS or BCE level. | 454 +---------------+---------------------------------------------------+ 455 | ifType | g9981(263), g9982(264) or g9983(265) for the ATM, | 456 | | Ethernet or TDIM GBS respectively, shdsl(169) for | 457 | | G.SHDSL BCE, vdsl(97) for VDSL BCE, etc. | 458 +---------------+---------------------------------------------------+ 459 | ifSpeed | Operating data rate for the BCE. For the GBS it | 460 | | is the sum of the current operating data rates of | 461 | | all BCEs in the aggregation group, without the | 462 | | encapsulation overhead and G.Bond overhead, but | 463 | | accounting for the Inter-Frame Gaps (IFG). When a | 464 | | GBS or a BCE is operating in an asymetrical | 465 | | fashion (upstream data rate differs from the | 466 | | downstream one) the lowest of the values is | 467 | | shown. | 468 +---------------+---------------------------------------------------+ 469 | ifAdminStatus | Setting this object to 'up' instructs a | 470 | | particular GBS (with all BCEs connected to it) or | 471 | | a BCE to start initialization process | 472 +---------------+---------------------------------------------------+ 473 | ifOperStatus | A relevant *Status object from a particular line | 474 | | MIB supplements the value of ifOperStatus for | 475 | | BCEs. gBondPortStatFltStatus supplements the | 476 | | value of ifOperStatus for GBS. Note that both | 477 | | relevant objects shall be inspected to determine | 478 | | the real operational status of a BCE/GBS port, | 479 | | e.g. a GBS port may be operationally 'up' with | 480 | | gBondPortStatFltStatus indicating lowRate(4) | 481 | | fault condition, or 'down' with no gBond faults. | 482 +---------------+---------------------------------------------------+ 484 Table 1: G.Bond interpretation of IF-MIB objects 486 4.2. Relationship to G.Bond ATM, ETH and TDIM MIB modules 488 The MIB module defined in this document is common to all three G.998 489 bonding schemes. It MUST be used in conjunction with a bonding 490 scheme-specific MIB module: 492 o GBOND-ATM-MIB [I-D.ietf-adslmib-gbond-atm-mib] for a G.998.1 493 bonded interface. 495 o GBOND-ETH-MIB [I-D.ietf-adslmib-gbond-eth-mib] for a G.998.2 496 bonded interface. 498 o GBOND-TDIM-MIB [I-D.ietf-adslmib-gbond-tdim-mib] for a G.998.3 499 bonded interface. 501 4.3. Relationship to xDSL MIB modules 503 Each xDSL technology is described in a relevant xDSL line MIB module: 504 e.g., HDSL2-SHDSL-LINE-MIB [RFC4319] for G.SHDSL, ADSL-LINE-EXT-MIB 505 [RFC3440] for ADSL, ADSL2-LINE-MIB [RFC4706] for ADSL2, VDSL-LINE-MIB 506 [RFC3728] for VDSL or VDSL2-LINE-MIB [RFC5650] for VDSL2. 508 These MIB moduless are used to manage individual xDSL lines/channels 509 (BCEs). 511 5. MIB Structure 513 5.1. Overview 515 The main management objects defined in the GBOND-MIB module are split 516 into 2 groups, structured as recommended by RFC 4181 [RFC4181]: 518 o gBondPort - containing objects for configuration, capabilities, 519 status, historical performance monitoring and notifications, 520 common to all G.Bond ports (GBS). 522 o gBondBce - containing a single common object for configuration of 523 the remote discovery code per BCE. Note that the rest of the 524 objects for BCE configuration, capabilities, status and 525 notifications, is located in relevant xDSL line MIB modules as 526 well as in the bonding scheme specific MIB modules. 528 5.2. Performance Monitoring 530 The OPTIONAL performance monitoring counters, thresholds and history 531 buckets (interval-counters) defined in [TR-159] are implemented using 532 the textual conventions defined in the HC-PerfHist-TC-MIB [RFC3705]. 533 The HC-PerfHist-TC-MIB defines 64-bit versions of the textual 534 conventions found in PerfHist-TC-MIB [RFC3593]. 536 The agent SHOULD align the beginning of each interval to a fifteen 537 minute boundary of a wall clock. Likewise, the beginning of each one 538 day intervals SHOULD be aligned with the start of a day. 540 The rationale behind it is to simplify collection and analysis of the 541 PM from multiple agents by a network management system (NMS) - each 542 PM interval can be "time-stamped" using the gBond*IntervalIndex 543 object, the fact that 1-day interval starts at 00:00 and 15-min 544 intervals are aligned with 1/4 hour and the network-wide "wall 545 clock", typically distributed via NTP or SNTP. If the agent does not 546 have an access to the wall clock, a local clock can be used. In this 547 case, as well as when coping with multiple time zones, the NMS would 548 have to correlate for the difference between the agent's local clock 549 (available for example via hrSystemDate object from HOST-RESOURCES- 550 MIB [RFC2790]) and the wall clock. 552 Counters are not reset when a GBS is reinitialized, but rather only 553 when the agent is reset or reinitialized. 555 Note that the accumulation of certain performance events for a 556 monitored entity is inhibited (counting stops) during periods of 557 service unavailability on that monitored entity. The DESCRIPTION 558 clause of performance monitoring counters in this MIB module 559 specifies which of the counters are inhibited during periods of 560 service unavailability. 562 5.3. Mapping of DSL Forum TR-159 Managed Objects 564 This section contains the mapping between relevant managed objects 565 (attributes) defined in [TR-159] and managed objects defined in this 566 document and in associated MIB modules, i.e., the IF-MIB [RFC2863]. 568 +-------------------------------+-----------------------------------+ 569 | G.Bond Managed Object | Corresponding SNMP Object | 570 +-------------------------------+-----------------------------------+ 571 | oBondingGroup - Basic Package | | 572 | (Mandatory) | | 573 +-------------------------------+-----------------------------------+ 574 | aGroupID | ifIndex (IF-MIB) | 575 +-------------------------------+-----------------------------------+ 576 | aGroupBondSchemesSupported | gBondPortCapSchemesSupported | 577 +-------------------------------+-----------------------------------+ 578 | aGroupPeerBondSchemesSupporte | gBondPortCapPeerSchemesSupported | 579 | d | | 580 +-------------------------------+-----------------------------------+ 581 | aGroupAdminBondScheme | gBondPortConfAdminScheme | 582 +-------------------------------+-----------------------------------+ 583 | aGroupPeerAdminBondScheme | gBondPortConfPeerAdminScheme | 584 +-------------------------------+-----------------------------------+ 585 | aGroupOperBondScheme | gBondPortStatOperScheme | 586 +-------------------------------+-----------------------------------+ 587 | aGroupPeerOperBondScheme | gBondPortStatPeerOperScheme | 588 +-------------------------------+-----------------------------------+ 589 | aGroupEnd | gBondPortStatSide | 590 +-------------------------------+-----------------------------------+ 591 +-------------------------------+-----------------------------------+ 592 | aGroupOperState | ifOperStatus (IF-MIB) | 593 +-------------------------------+-----------------------------------+ 594 | aGroupAdminState | ifAdminStatus (IF-MIB) | 595 +-------------------------------+-----------------------------------+ 596 | aGroupStatus | gBondPortStatFltStatus | 597 +-------------------------------+-----------------------------------+ 598 | aGroupCapacity | gBondPortCapCapacity | 599 +-------------------------------+-----------------------------------+ 600 | aGroupPeerCapacity | gBondPortCapPeerCapacity | 601 +-------------------------------+-----------------------------------+ 602 | aGroupNumChannels | gBondPortStatNumBCEs | 603 +-------------------------------+-----------------------------------+ 604 | aGroupName | ifName (IF-MIB) | 605 +-------------------------------+-----------------------------------+ 606 | aGroupDiscoveryCode | gBondPortConfDiscoveryCode | 607 +-------------------------------+-----------------------------------+ 608 | aGroupUpRate | gBondPortStatUpDataRate | 609 +-------------------------------+-----------------------------------+ 610 | aGroupDownRate | gBondPortStatDnDataRate | 611 +-------------------------------+-----------------------------------+ 612 | aGroupTargetUpRate | gBondPortConfTargetUpDataRate | 613 +-------------------------------+-----------------------------------+ 614 | aGroupTargetDownRate | gBondPortConfTargetDnDataRate | 615 +-------------------------------+-----------------------------------+ 616 | aGroupThreshLowUpRate | gBondPortConfThreshLowUpRate | 617 +-------------------------------+-----------------------------------+ 618 | aGroupThreshLowDownRate | gBondPortConfThreshLowDnRate | 619 +-------------------------------+-----------------------------------+ 620 | aGroupLowRateCrossingEnable | gBondPortConfLowRateCrossingEnabl | 621 | | e | 622 +-------------------------------+-----------------------------------+ 623 | nGroupLowUpRateCrossing | gBondLowUpRateCrossing | 624 +-------------------------------+-----------------------------------+ 625 | nGroupLowDownRateCrossing | gBondLowDnRateCrossing | 626 +-------------------------------+-----------------------------------+ 627 | aGroupLinkUpDownEnable | ifLinkUpDownTrapEnable (IF-MIB) | 628 +-------------------------------+-----------------------------------+ 629 | nGroupLinkUp | linkDown (IF-MIB) | 630 +-------------------------------+-----------------------------------+ 631 | nGroupLinkDown | linkUp (IF-MIB) | 632 +-------------------------------+-----------------------------------+ 633 | oBondingGroup - PM Package | | 634 | (Optional) | | 635 +-------------------------------+-----------------------------------+ 636 | aGroupPerfES | gBondPortPmCurES | 637 +-------------------------------+-----------------------------------+ 638 | aGroupPerfSES | gBondPortPmCurSES | 639 | aGroupPerfUAS | gBondPortPmCurUAS | 640 +-------------------------------+-----------------------------------+ 641 | aGroupPerf15MinValidIntervals | gBondPortPmCur15MinValidIntervals | 642 +-------------------------------+-----------------------------------+ 643 | aGroupPerf15MinInvalidInterva | gBondPortPmCur15MinInvalidInterva | 644 | ls | ls | 645 +-------------------------------+-----------------------------------+ 646 | aGroupPerfCurr15MinTimeElapse | gBondPortPmCur15MinTimeElapsed | 647 | d | | 648 +-------------------------------+-----------------------------------+ 649 | aGroupPerfCurr15MinES | gBondPortPmCur15MinES | 650 +-------------------------------+-----------------------------------+ 651 | aGroupPerfCurr15MinSES | gBondPortPmCur15MinSES | 652 +-------------------------------+-----------------------------------+ 653 | aGroupPerfCurr15MinUAS | gBondPortPmCur15MinUAS | 654 +-------------------------------+-----------------------------------+ 655 | aGroupPerfTcaEnable | gBondPortConfPmTcaEnable | 656 +-------------------------------+-----------------------------------+ 657 | aGroupPerfThreshold15MinES | gBondPortPmTcaProfileThresh15MinE | 658 | | S | 659 +-------------------------------+-----------------------------------+ 660 | aGroupPerfThreshold15MinSES | gBondPortPmTcaProfileThresh15MinS | 661 | | ES | 662 +-------------------------------+-----------------------------------+ 663 | aGroupPerfThreshold15MinUAS | gBondPortPmTcaProfileThresh15MinU | 664 | | AS | 665 +-------------------------------+-----------------------------------+ 666 | nGroupPerfTca15MinES | gBondPmTca15MinESCrossing | 667 +-------------------------------+-----------------------------------+ 668 | nGroupPerfTca15MinSES | gBondPmTca15MinSESCrossing | 669 +-------------------------------+-----------------------------------+ 670 | nGroupPerfTca15MinUAS | gBondPmTca15MinUASCrossing | 671 +-------------------------------+-----------------------------------+ 672 | aGroupPerf1DayValidIntervals | gBondPortPmCur1DayValidIntervals | 673 +-------------------------------+-----------------------------------+ 674 | aGroupPerf1DayInvalidInterval | gBondPortPmCur1DayInvalidInterval | 675 | s | s | 676 +-------------------------------+-----------------------------------+ 677 | aGroupPerfCurr1DayTimeElapsed | gBondPortPmCur1DayTimeElapsed | 678 +-------------------------------+-----------------------------------+ 679 | aGroupPerfCurr1DayES | gBondPortPmCur1DayIntervalES | 680 +-------------------------------+-----------------------------------+ 681 | aGroupPerfCurr1DaySES | gBondPortPmCur1DayIntervalSES | 682 +-------------------------------+-----------------------------------+ 683 | aGroupPerfCurr1DayUAS | gBondPortPmCur1DayIntervalUAS | 684 +-------------------------------+-----------------------------------+ 685 | aGroupPerfThreshold1DayES | gBondPortPmTcaProfileThresh1DayES | 686 +-------------------------------+-----------------------------------+ 687 +-------------------------------+-----------------------------------+ 688 | aGroupPerfThreshold1DaySES | gBondPortPmTcaProfileThresh1DaySE | 689 | | S | 690 +-------------------------------+-----------------------------------+ 691 | aGroupPerfThreshold1DayUAS | gBondPortPmTcaProfileThresh1DayUA | 692 | | S | 693 +-------------------------------+-----------------------------------+ 694 | nGroupPerfTca1DayES | gBondPmTca1DayESCrossing | 695 +-------------------------------+-----------------------------------+ 696 | nGroupPerfTca1DaySES | gBondPmTca1DaySESCrossing | 697 +-------------------------------+-----------------------------------+ 698 | nGroupPerfTca1DayUAS | gBondPmTca1DayUASCrossing | 699 +-------------------------------+-----------------------------------+ 700 | aGroupPerf15MinIntervalNumber | gBondPortPm15MinIntervalIndex | 701 +-------------------------------+-----------------------------------+ 702 | aGroupPerf15MinIntervalValid | gBondPortPm15MinIntervalValid | 703 +-------------------------------+-----------------------------------+ 704 | aGroupPerf15MinIntervalES | gBondPortPm15MinIntervalES | 705 +-------------------------------+-----------------------------------+ 706 | aGroupPerf15MinIntervalSES | gBondPortPm15MinIntervalSES | 707 +-------------------------------+-----------------------------------+ 708 | aGroupPerf15MinIntervalUAS | gBondPortPm15MinIntervalUAS | 709 +-------------------------------+-----------------------------------+ 710 | aGroupPerf1DayIntervalNumber | gBondPortPm1DayIntervalIndex | 711 +-------------------------------+-----------------------------------+ 712 | aGroupPerf1DayIntervalValid | gBondPortPm1DayIntervalValid | 713 +-------------------------------+-----------------------------------+ 714 | aGroupPerf1DayIntervalMoniSec | gBondPortPm1DayIntervalMoniTime | 715 | s | | 716 +-------------------------------+-----------------------------------+ 717 | aGroupPerf1DayIntervalES | gBondPortPm1DayIntervalES | 718 +-------------------------------+-----------------------------------+ 719 | aGroupPerf1DayIntervalSES | gBondPortPm1DayIntervalSES | 720 +-------------------------------+-----------------------------------+ 721 | aGroupPerf1DayIntervalUAS | gBondPortPm1DayIntervalUAS | 722 +-------------------------------+-----------------------------------+ 723 | oLine - Basic Package | | 724 | (Mandatory) | | 725 +-------------------------------+-----------------------------------+ 726 | aLineID | ifIndex (IF-MIB) | 727 +-------------------------------+-----------------------------------+ 728 | aLineType | ifType (IF-MIB) | 729 +-------------------------------+-----------------------------------+ 730 | aLineOperState | ifOperStatus (IF-MIB) | 731 +-------------------------------+-----------------------------------+ 732 | aLineStatus | *dsl*CurrStatus (*DSL-LINE-MIB) | 733 +-------------------------------+-----------------------------------+ 734 | aLineEnd | *dsl*Side (*DSL-LINE-MIB) | 735 | aLineAdminState | ifAdminStatus (IF-MIB) | 736 +-------------------------------+-----------------------------------+ 737 | aLineRemoteDiscoveryCode | gBondBceConfRemoteDiscoveryCode | 738 +-------------------------------+-----------------------------------+ 739 | aLineUpDownEnable | ifLinkUpDownTrapEnable (IF-MIB) | 740 +-------------------------------+-----------------------------------+ 741 | nLineUp | linkUp (IF-MIB) | 742 +-------------------------------+-----------------------------------+ 743 | nLineDown | linkDown (IF-MIB) | 744 +-------------------------------+-----------------------------------+ 745 | oChannel - Basic Package | | 746 | (Mandatory) | | 747 +-------------------------------+-----------------------------------+ 748 | aChannelID | ifIndex (IF-MIB) | 749 +-------------------------------+-----------------------------------+ 750 | aChannelGroupID | | 751 +-------------------------------+-----------------------------------+ 752 | aChannelType | ifType (IF-MIB) | 753 +-------------------------------+-----------------------------------+ 754 | aChannelOperState | ifOperStatus (IF-MIB) | 755 +-------------------------------+-----------------------------------+ 756 | aChannelStatus | *dsl*CurrStatus (*DSL-LINE-MIB), | 757 | | xdsl2ChStatus*Status | 758 | | (VDSL2-LINE-MIB) | 759 +-------------------------------+-----------------------------------+ 761 Table 2: Mapping of TR-159 Managed Objects 763 6. xDSL Multi-pair Bonding MIB Definitions 765 GBOND-MIB DEFINITIONS ::= BEGIN 767 IMPORTS 768 MODULE-IDENTITY, 769 OBJECT-TYPE, 770 NOTIFICATION-TYPE, 771 mib-2, 772 Unsigned32, 773 Gauge32 774 FROM SNMPv2-SMI -- [RFC2578] 775 TEXTUAL-CONVENTION, 776 TruthValue, 777 RowStatus, 778 PhysAddress 779 FROM SNMPv2-TC -- [RFC2579] 780 MODULE-COMPLIANCE, 781 OBJECT-GROUP, 782 NOTIFICATION-GROUP 783 FROM SNMPv2-CONF -- [RFC2580] 784 SnmpAdminString 785 FROM SNMP-FRAMEWORK-MIB -- [RFC3411] 786 ifIndex 787 FROM IF-MIB -- [RFC2863] 788 HCPerfCurrentCount, 789 HCPerfIntervalCount, 790 HCPerfIntervalThreshold, 791 HCPerfValidIntervals, 792 HCPerfInvalidIntervals, 793 HCPerfTimeElapsed, 794 HCPerfTotalCount 795 FROM HC-PerfHist-TC-MIB -- [RFC3705] 796 ; 797 ------------------------------------------------------------------------ 798 gBondMIB MODULE-IDENTITY 799 LAST-UPDATED "201202130000Z" -- Feb 13, 2012 800 ORGANIZATION "IETF ADSL MIB Working Group" 801 CONTACT-INFO 802 "WG charter: 803 http://www.ietf.org/html.charters/adslmib-charter.html 805 Mailing Lists: 806 General Discussion: adslmib@ietf.org 807 To Subscribe: adslmib-request@ietf.org 808 In Body: subscribe your_email_address 810 Chair: Menachem Dodge 811 Postal: ECI Telecom, Ltd. 812 30 Hasivim St., 813 Petach-Tikva 4951169 814 Israel 815 Phone: +972-3-926-8421 816 EMail: menachem.dodge@ecitele.com 818 Editor: Edward Beili 819 Postal: Actelis Networks, Inc. 820 25 Bazel St., P.O.B. 10173 821 Petach-Tikva 49103 822 Israel 823 Phone: +972-3-924-3491 824 EMail: edward.beili@actelis.com 826 Editor: Moti Morgenstern 827 Postal: ECI Telecom 828 30 Hasivim St. 829 Petach-Tikva 4951169 830 Israel 832 Phone: +972-3-926-6258 833 EMail: moti.morgenstern@ecitele.com" 835 DESCRIPTION 836 "The objects in this MIB module are used to manage the 837 multi-pair bonded xDSL Interfaces, defined in ITU-T 838 recommendations G.998.1, G.998.2 and G.998.3. 840 This MIB module MUST be used in conjunction with a bonding 841 scheme specific MIB module, that is, GBOND-ATM-MIB, 842 GBOND-ETH-MIB or GBOND-TDIM-MIB. 844 The following references are used throughout this MIB module: 846 [G.998.1] refers to: 847 ITU-T Recommendation G.998.1: 'ATM-based multi-pair bonding', 848 January 2005. 850 [G.998.2] refers to: 851 ITU-T Recommendation G.998.2: 'Ethernet-based multi-pair 852 bonding', January 2005. 854 [G.998.3] refers to: 855 ITU-T Recommendation G.998.3: 'Multi-pair bonding using 856 time-division inverse multiplexing', January 2005. 858 [TR-159] refers to: 859 Broadband Forum Technical Report: 'Management Framework for 860 xDSL Bonding', December 2008. 862 Naming Conventions: 863 BCE - Bonding Channel Entity 864 BTU - Bonding Transmission Unit 865 BTU-C - Bonding Transmission Unit, CO side 866 BTU-R - Bonding Transmission Unit, Remote Terminal (CPE) side 867 CO - Central Office 868 CPE - Customer Premises Equipment 869 GBS - Generic Bonding Sublayer 870 PM - Performance Monitoring 871 SNR - Signal to Noise Ratio 872 TCA - Threshold Crossing Alert 874 Copyright (C) The IETF Trust (2012). 875 This version of this MIB module is part of RFC XXXX; 876 see the RFC itself for full legal notices." 878 REVISION "201202130000Z" -- Feb 13, 2012 879 DESCRIPTION "Initial version, published as RFC XXXX." 880 -- EdNote: Replace XXXX with the actual RFC number & 881 -- remove this note 883 ::= { mib-2 ZZZ } 885 -- EdNote: Replace ZZZ with a real OID once it is 886 -- allocated & remove this note. 888 -- Sections of the module 889 -- Structured as recommended by [RFC4181], Appendix D 891 gBondObjects OBJECT IDENTIFIER ::= { gBondMIB 1 } 893 gBondConformance OBJECT IDENTIFIER ::= { gBondMIB 2 } 895 -- Groups in the module 897 gBondPort OBJECT IDENTIFIER ::= { gBondObjects 1 } 899 gBondBce OBJECT IDENTIFIER ::= { gBondObjects 2 } 901 -- Textual Conventions 903 GBondSchemeList ::= TEXTUAL-CONVENTION 904 STATUS current 905 DESCRIPTION 906 "This textual convention defines a bitmap of possible ITU-T 907 G.998 (G.Bond) bonding schemes. Currently there are 3 bonding 908 schemes defined: G.998.1, G.998.2 and G.998.3, identified by 909 bit values g9981(1), g9982(2) and g9983(3), respectively. 910 An additional value of unknown(0), can be returned as a result 911 of GET operation, when an value of the object cannot be 912 determined, for example a peer GBS cannot be reached or it 913 does not support any kind of bonding." 914 SYNTAX BITS { 915 unknown(0), 916 g9981(1), 917 g9982(2), 918 g9983(3) 919 } 921 GBondScheme ::= TEXTUAL-CONVENTION 922 STATUS current 923 DESCRIPTION 924 "This textual convention defines ITU-T G.998 bonding scheme 925 values. Possible values are: 926 unknown(0) - undefined or unknown 927 g9981(1) - G.998.1 (G.Bond/ATM) 928 g9982(2) - G.998.2 (G.Bond/Ethernet) 929 g9983(3) - G.998.3 (G.Bond/TDIM)." 930 SYNTAX INTEGER { 931 unknown(0), 932 g9981(1), 933 g9982(2), 934 g9983(3) 935 } 937 GBondPm1DayIntervalThreshold ::= TEXTUAL-CONVENTION 938 DISPLAY-HINT "d" 939 STATUS current 940 DESCRIPTION 941 "This textual convention defines a range of values that may be 942 set in a fault threshold alarm control for a 1-day performance 943 monitoring interval. 944 As the number of seconds in a 1-day interval numbers at most 945 86400, objects of this type may have a range of 0...86400, 946 where the value of 0 disables the alarm." 947 SYNTAX Unsigned32 (0..86400) 949 -- Port Notifications Group 951 gBondPortNotifications OBJECT IDENTIFIER ::= { gBondPort 0 } 953 gBondLowUpRateCrossing NOTIFICATION-TYPE 954 OBJECTS { 955 -- ifIndex is not needed here since we are under specific GBS 956 gBondPortStatUpDataRate, 957 gBondPortConfThreshLowUpRate 958 } 959 STATUS current 960 DESCRIPTION 961 "This notification indicates that the G.Bond port' upstream 962 data rate has reached/dropped below or exceeded the low 963 upstream rate threshold, specified by 964 gBondPortConfThreshLowUpRate. 966 This notification MAY be sent for the -O subtype ports 967 while the port is up, on the crossing event in both 968 directions: from normal (rate is above the threshold) to low 969 (rate equals the threshold or below it) and from low to 970 normal. This notification is not applicable to the -R 971 subtypes. 973 It is RECOMMENDED that a small debouncing period of 2.5 sec, 974 between the detection of the condition and notification, 975 is implemented to prevent simultaneous LinkUp/LinkDown and 976 gBondLowUpRateCrossing notifications to be sent. 978 The adaptive nature of the G.Bond technology allows the port 979 to adapt itself to the changes in the copper environment, 980 e.g., an impulse noise, alien crosstalk, or a 981 micro-interruption may temporarily drop one or more BCEs in 982 the aggregation group, causing a rate degradation of the 983 aggregated G.Bond link. The dropped BCEs would then try to 984 re-initialize, possibly at a lower rate than before, adjusting 985 the rate to provide required target SNR margin. 987 Generation of this notification is controlled by the 988 gBondPortConfLowRateCrossingEnable object. 990 This object maps to the TR-159 notification 991 nGroupLowUpRateCrossing." 992 REFERENCE 993 "[TR-159] 5.5.1.24" 994 ::= { gBondPortNotifications 1 } 996 gBondLowDnRateCrossing NOTIFICATION-TYPE 997 OBJECTS { 998 -- ifIndex is not needed here since we are under specific GBS 999 gBondPortStatDnDataRate, 1000 gBondPortConfThreshLowDnRate 1001 } 1002 STATUS current 1003 DESCRIPTION 1004 "This notification indicates that the G.Bond port' downstream 1005 data rate has reached/dropped below or exceeded the low 1006 downstream rate threshold, specified by 1007 gBondPortConfThreshLowDnRate. 1009 This notification MAY be sent for the -O subtype ports 1010 while the port is up, on the crossing event in both 1011 directions: from normal (rate is above the threshold) to low 1012 (rate equals the threshold or below it) and from low to 1013 normal. This notification is not applicable to the -R 1014 subtypes. 1016 It is RECOMMENDED that a small debouncing period of 2.5 sec, 1017 between the detection of the condition and notification, 1018 is implemented to prevent simultaneous LinkUp/LinkDown and 1019 gBondLowDnRateCrossing notifications to be sent. 1021 The adaptive nature of the G.Bond technology allows the port 1022 to adapt itself to the changes in the copper environment, 1023 e.g., an impulse noise, alien crosstalk, or a 1024 micro-interruption may temporarily drop one or more BCEs in 1025 the aggregation group, causing a rate degradation of the 1026 aggregated G.Bond link. The dropped BCEs would then try to 1027 re-initialize, possibly at a lower rate than before, 1028 adjusting the rate to provide required target SNR margin. 1030 Generation of this notification is controlled by the 1031 gBondPortConfLowRateCrossingEnable object. 1033 This object maps to the TR-159 notification 1034 nGroupLowDownRateCrossing." 1035 REFERENCE 1036 "[TR-159] 5.5.1.25" 1037 ::= { gBondPortNotifications 2} 1039 gBondPmTca15MinESCrossing NOTIFICATION-TYPE 1040 OBJECTS { 1041 -- ifIndex is not needed here since we are under specific GBS 1042 gBondPortPmCur15MinES, 1043 gBondPortPmTcaProfileThresh15MinES 1044 } 1045 STATUS current 1046 DESCRIPTION 1047 "This notification indicates that the Errored Seconds threshold, 1048 specified by gBondPortPmTcaProfileThresh15MinES, has been 1049 reached or exceeded for the GPS port. 1051 Generation of this notification is controlled by 1052 gBondPortConfPmTcaEnable and 1053 gBondPortPmTcaProfileThresh15MinES objects. 1055 This object maps to the TR-159 notification 1056 nGroupPerfTca15MinES." 1057 REFERENCE 1058 "[TR-159] 5.5.1.42" 1059 ::= { gBondPortNotifications 3} 1061 gBondPmTca15MinSESCrossing NOTIFICATION-TYPE 1062 OBJECTS { 1063 -- ifIndex is not needed here since we are under specific GBS 1064 gBondPortPmCur15MinSES, 1065 gBondPortPmTcaProfileThresh15MinSES 1066 } 1067 STATUS current 1068 DESCRIPTION 1069 "This notification indicates that the Severely Errored Seconds 1070 threshold, specified by gBondPortPmTcaProfileThresh15MinSES, 1071 has been reached or exceeded for the GPS port. 1073 Generation of this notification is controlled by 1074 gBondPortConfPmTcaEnable and 1075 gBondPortPmTcaProfileThresh15MinSES objects. 1077 This object maps to the TR-159 notification 1078 nGroupPerfTca15MinSES." 1079 REFERENCE 1080 "[TR-159] 5.5.1.43" 1081 ::= { gBondPortNotifications 4} 1083 gBondPmTca15MinUASCrossing NOTIFICATION-TYPE 1084 OBJECTS { 1085 -- ifIndex is not needed here since we are under specific GBS 1086 gBondPortPmCur15MinUAS, 1087 gBondPortPmTcaProfileThresh15MinUAS 1088 } 1089 STATUS current 1090 DESCRIPTION 1091 "This notification indicates that the Unavailable Seconds 1092 threshold, specified by gBondPortPmTcaProfileThresh15MinES, 1093 has been reached or exceeded for the GPS port. 1095 Generation of this notification is controlled by 1096 gBondPortConfPmTcaEnable and 1097 gBondPortPmTcaProfileThresh15MinUAS objects. 1099 This object maps to the TR-159 notification 1100 nGroupPerfTca15MinUAS." 1101 REFERENCE 1102 "[TR-159] 5.5.1.44" 1103 ::= { gBondPortNotifications 5} 1105 gBondPmTca1DayESCrossing NOTIFICATION-TYPE 1106 OBJECTS { 1107 -- ifIndex is not needed here since we are under specific GBS 1108 gBondPortPmCur1DayES, 1109 gBondPortPmTcaProfileThresh1DayES 1110 } 1111 STATUS current 1112 DESCRIPTION 1113 "This notification indicates that the Errored Seconds threshold, 1114 specified by gBondPortPmTcaProfileThresh1DayES, has been 1115 reached or exceeded for the GPS port. 1117 Generation of this notification is controlled by 1118 gBondPortConfPmTcaEnable and 1119 gBondPortPmTcaProfileThresh1DayES objects. 1121 This object maps to the TR-159 notification 1122 nGroupPerfTca1DayES." 1123 REFERENCE 1124 "[TR-159] 5.5.1.54" 1125 ::= { gBondPortNotifications 6} 1127 gBondPmTca1DaySESCrossing NOTIFICATION-TYPE 1128 OBJECTS { 1129 -- ifIndex is not needed here since we are under specific GBS 1130 gBondPortPmCur1DaySES, 1131 gBondPortPmTcaProfileThresh1DaySES 1132 } 1133 STATUS current 1134 DESCRIPTION 1135 "This notification indicates that the Severely Errored Seconds 1136 threshold, specified by gBondPortPmTcaProfileThresh1DaySES, 1137 has been reached or exceeded for the GPS port. 1139 Generation of this notification is controlled by 1140 gBondPortConfPmTcaEnable and 1141 gBondPortPmTcaProfileThresh1DaySES objects. 1143 This object maps to the TR-159 notification 1144 nGroupPerfTca1DaySES." 1145 REFERENCE 1146 "[TR-159] 5.5.1.55" 1147 ::= { gBondPortNotifications 7} 1149 gBondPmTca1DayUASCrossing NOTIFICATION-TYPE 1150 OBJECTS { 1151 -- ifIndex is not needed here since we are under specific GBS 1152 gBondPortPmCur1DayUAS, 1153 gBondPortPmTcaProfileThresh1DayUAS 1154 } 1155 STATUS current 1156 DESCRIPTION 1157 "This notification indicates that the Unavailable Seconds 1158 threshold, specified by gBondPortPmTcaProfileThresh1DayUAS, 1159 has been reached or exceeded for the GPS port. 1161 Generation of this notification is controlled by 1162 gBondPortConfPmTcaEnable and 1163 gBondPortPmTcaProfileThresh1DayUAS objects. 1165 This object maps to the TR-159 notification 1166 nGroupPerfTca1DayUAS." 1168 REFERENCE 1169 "[TR-159] 5.5.1.56" 1170 ::= { gBondPortNotifications 8} 1172 -- G.Bond Port (GBS) group 1174 gBondPortConfTable OBJECT-TYPE 1175 SYNTAX SEQUENCE OF GBondPortConfEntry 1176 MAX-ACCESS not-accessible 1177 STATUS current 1178 DESCRIPTION 1179 "Table for configuration of G.Bond GBS ports. Entries in this 1180 table MUST be maintained in a persistent manner" 1181 ::= { gBondPort 1 } 1183 gBondPortConfEntry OBJECT-TYPE 1184 SYNTAX GBondPortConfEntry 1185 MAX-ACCESS not-accessible 1186 STATUS current 1187 DESCRIPTION 1188 "An entry in the G.Bond Port Configuration table. 1189 Each entry represents a G.Bond port indexed by the ifIndex. 1190 Note that a G.Bond GBS port runs on top of a single 1191 or multiple BCE port(s), which are also indexed by ifIndex." 1192 INDEX { ifIndex } 1193 ::= { gBondPortConfTable 1 } 1195 GBondPortConfEntry ::= 1196 SEQUENCE { 1197 gBondPortConfAdminScheme GBondScheme, 1198 gBondPortConfPeerAdminScheme GBondScheme, 1199 gBondPortConfDiscoveryCode PhysAddress, 1200 gBondPortConfTargetUpDataRate Unsigned32, 1201 gBondPortConfTargetDnDataRate Unsigned32, 1202 gBondPortConfThreshLowUpRate Unsigned32, 1203 gBondPortConfThreshLowDnRate Unsigned32, 1204 gBondPortConfLowRateCrossingEnable TruthValue, 1205 gBondPortConfPmTcaConfProfile SnmpAdminString, 1206 gBondPortConfPmTcaEnable TruthValue 1207 } 1209 gBondPortConfAdminScheme OBJECT-TYPE 1210 SYNTAX GBondScheme 1211 MAX-ACCESS read-write 1212 STATUS current 1213 DESCRIPTION 1214 "A desired bonding scheme for a G.Bond GBS port. 1215 The following values instruct the port to use corresponding 1216 bonding scheme if supported: 1217 g9981(1) - instructs the port to use G.998.1 bonding 1218 g9982(2) - instructs the port to use G.998.2 bonding 1219 g9983(3) - instructs the port to use G.998.3 bonding 1221 Changing of gBondPortConfAdminScheme MUST be performed when the 1222 link is administratively 'down', as indicated by the 1223 ifAdminStatus object in IF-MIB. 1224 Attempts to change this object MUST be rejected (in case of SNMP 1225 with the error inconsistentValue), if the link is Up or 1226 Initializing. Attempts to change this object to an unsupported 1227 bonding scheme (see gBondPortCapSchemesSupported) SHALL be 1228 rejected (in case of SNMP with the error wrongValue). 1230 This object maps to the TR-159 attribute aGroupAdminBondScheme." 1231 REFERENCE 1232 "[TR-159] 5.5.1.6; IF-MIB, ifAdminStatus" 1233 ::= { gBondPortConfEntry 1 } 1235 gBondPortConfPeerAdminScheme OBJECT-TYPE 1236 SYNTAX GBondScheme 1237 MAX-ACCESS read-write 1238 STATUS current 1239 DESCRIPTION 1240 "A desired bonding scheme for a peer (link partner) G.Bond 1241 port (GBS). 1242 The following values instruct the peer port to use 1243 corresponding bonding scheme if supported: 1244 g9981(1) - instructs the port to use G.998.1 bonding 1245 g9982(2) - instructs the port to use G.998.2 bonding 1246 g9983(3) - instructs the port to use G.998.3 bonding 1248 Changing of this object MUST be performed when the link is 1249 administratively 'down', as indicated by the ifAdminStatus 1250 object in IF-MIB. 1251 Attempts to change this object MUST be rejected (in case of SNMP 1252 with the error inconsistentValue), if the link is Up or 1253 Initializing. Attempts to change this object to an unsupported 1254 bonding scheme (see gBondPortCapPeerSchemesSupported) SHALL be 1255 rejected (in case of SNMP with the error wrongValue). 1257 This object maps to the TR-159 attribute 1258 aGroupPeerAdminBondScheme." 1259 REFERENCE 1260 "[TR-159] 5.5.1.7; IF-MIB, ifAdminStatus" 1261 ::= { gBondPortConfEntry 2 } 1263 gBondPortConfDiscoveryCode OBJECT-TYPE 1264 SYNTAX PhysAddress (SIZE(6)) 1265 MAX-ACCESS read-write 1266 STATUS current 1267 DESCRIPTION 1268 "A Discovery Code of the G.Bond port (GBS). 1269 A unique 6 octet long code used by the Discovery function. 1270 This object MUST be instantiated for the -O subtype GBS before 1271 writing operations on the gBondBceConfRemoteDiscoveryCode 1272 (Set_if_Clear and Clear_if_Same) are performed by BCEs 1273 associated with the GBS. 1274 The initial value of this object for -R subtype ports after 1275 reset is all zeroes. For -R subtype ports, the value of this 1276 object cannot be changed directly. This value may be changed 1277 as a result of writing operation on the 1278 gBondBceConfRemoteDiscoveryCode object of remote BCE of -O 1279 subtype, connected to one of the local BCEs associated with 1280 the GBS. 1282 Discovery MUST be performed when the link is administratively 1283 'down', as indicated by the ifAdminStatus object in IF-MIB. 1284 Attempts to change this object MUST be rejected (in case of 1285 SNMP with the error inconsistentValue), if the link is Up or 1286 Initializing. 1288 This object maps to the TR-159 attribute 1289 aGroupDiscoveryCode." 1290 REFERENCE 1291 "[TR-159] 5.5.1.20; [802.3] 61.2.2.8.3, 61.2.2.8.4, 1292 45.2.6.6.1, 45.2.6.8, 61A.2; IF-MIB, ifAdminStatus" 1293 ::= { gBondPortConfEntry 3 } 1295 gBondPortConfTargetUpDataRate OBJECT-TYPE 1296 SYNTAX Unsigned32(0|1..10000000) 1297 UNITS "Kbps" 1298 MAX-ACCESS read-write 1299 STATUS current 1300 DESCRIPTION 1301 "A desired G.Bond port Data Rate in the upstream direction, 1302 in Kbps, to be achieved during initialization, under 1303 restrictions placed upon the member BCEs by their respective 1304 configuration settings. 1305 This object represents a sum of individual BCE upstream data 1306 rates, modified to compensate for fragmentation and 1307 encapsulation overhead (e.g., for an Ethernet service, the 1308 target data rate of 10Mbps SHALL allow lossless transmission 1309 of full-duplex 10Mbps Ethernet frame stream with minimal 1310 inter-frame gap). 1311 Note that the target upstream data rate may not be achieved 1312 during initialization (e.g., due to unavailability of required 1313 BCEs) or the initial bandwidth could deteriorate, so that the 1314 actual upstream data rate (gBondPortStatUpDataRate) could be less 1315 than gBondPortConfTargetUpDataRate. 1317 The value is limited above by 10 Gbps, to accommodate very 1318 high speed bonded xDSL interfaces (e.g. 32 x 100Mbps). 1320 The value between 1 and 10000000 indicates that the total 1321 upstream data rate of the G.Bond port after initialization 1322 SHALL be equal to the target data rate or less, if the target 1323 upstream data rate cannot be achieved under the restrictions 1324 configured for BCEs. In case the copper environment allows to 1325 achieve higher upstream data rate than that specified by this 1326 object, the excess capability SHALL be either converted to 1327 additional SNR margin or reclaimed by minimizing transmit 1328 power. 1330 The value of 0 means that the target data rate is not 1331 fixed and SHALL be set to the maximum attainable rate during 1332 initialization (Best Effort), under specified spectral 1333 restrictions and with desired SNR Margin per BCE. 1335 This object is read-write for the -O subtype G.Bond ports. 1336 It is irrelevant for the -R subtypes - attempts to read or 1337 change this object for such ports MUST be rejected (in case of 1338 SNMP with the error inconsistentValue). 1340 Changing of the Target Upstream Data Rate MUST be performed 1341 when the link is administratively 'down', as indicated by the 1342 ifAdminStatus object in IF-MIB. 1343 Attempts to change this object MUST be rejected (in case of SNMP 1344 with the error inconsistentValue), if the link is Up or 1345 Initializing. 1347 This object maps to the TR-159 attribute aGroupTargetUpRate." 1348 REFERENCE 1349 "[TR-159] 5.5.1.17; IF-MIB, ifAdminStatus" 1350 ::= { gBondPortConfEntry 4 } 1352 gBondPortConfTargetDnDataRate OBJECT-TYPE 1353 SYNTAX Unsigned32(0|1..10000000) 1354 UNITS "Kbps" 1355 MAX-ACCESS read-write 1356 STATUS current 1357 DESCRIPTION 1358 "A desired G.Bond port Data Rate in the downstream direction, 1359 in Kbps, to be achieved during initialization, under 1360 restrictions placed upon the member BCEs by their respective 1361 configuration settings. 1362 This object represents a sum of individual BCE downstream data 1363 rates, modified to compensate for fragmentation and 1364 encapsulation overhead (e.g., for an Ethernet service, the 1365 target data rate of 10Mbps SHALL allow lossless transmission 1366 of full-duplex 10Mbps Ethernet frame stream with minimal 1367 inter-frame gap). 1368 Note that the target downstream data rate may not be achieved 1369 during initialization (e.g., due to unavailability of required 1370 BCEs) or the initial bandwidth could deteriorate, so that the 1371 actual downstream data rate (gBondPortStatDnDataRate) could be 1372 less than gBondPortConfTargetDnDataRate. 1374 The value is limited above by 10 Gbps, to accommodate very 1375 high speed bonded xDSL interfaces (e.g. 32 x 100Mbps). 1377 The value between 1 and 10000000 indicates that the total 1378 downstream data rate of the G.Bond port after initialization 1379 SHALL be equal to the target data rate or less, if the target 1380 downstream data rate cannot be achieved under the restrictions 1381 configured for BCEs. In case the copper environment allows to 1382 achieve higher downstream data rate than that specified by 1383 this object, the excess capability SHALL be either converted 1384 to additional SNR margin or reclaimed by minimizing transmit 1385 power. 1387 The value of 0 means that the target data rate is not 1388 fixed and SHALL be set to the maximum attainable rate during 1389 initialization (Best Effort), under specified spectral 1390 restrictions and with desired SNR Margin per BCE. 1392 This object is read-write for the -O subtype G.Bond ports. 1393 It is irrelevant for the -R subtypes - attempts to read or 1394 change this object for such ports MUST be rejected (in case of 1395 SNMP with the error inconsistentValue). 1397 Changing of the Target Downstream Data Rate MUST be performed 1398 when the link is administratively 'down', as indicated by the 1399 ifAdminStatus object in IF-MIB. 1400 Attempts to change this object MUST be rejected (in case of SNMP 1401 with the error inconsistentValue), if the link is Up or 1402 Initializing. 1404 This object maps to the TR-159 attribute aGroupTargetDownRate." 1405 REFERENCE 1406 "[TR-159] 5.5.1.18; IF-MIB, ifAdminStatus" 1407 ::= { gBondPortConfEntry 5 } 1409 gBondPortConfThreshLowUpRate OBJECT-TYPE 1410 SYNTAX Unsigned32(1..10000000) 1411 UNITS "Kbps" 1412 MAX-ACCESS read-write 1413 STATUS current 1414 DESCRIPTION 1415 "This object configures the G.Bond port low upstream rate 1416 crossing alarm threshold. When the current value of 1417 gBondPortStatUpDataRate for this port reaches/drops below or 1418 exceeds this threshold, a gBondLowUpRateCrossing notification 1419 MAY be generated if enabled by 1420 gBondPortConfLowRateCrossingEnable. 1422 This object is read-write for the -O subtype G.Bond ports. 1423 It is irrelevant for the -R subtypes - attempts to read or 1424 change this object for such ports MUST be rejected (in case of 1425 SNMP with the error inconsistentValue). 1427 This object maps to the TR-159 attribute 1428 aGroupthreshLowUpRate." 1429 REFERENCE 1430 "[TR-159] 5.5.1.21" 1431 ::= { gBondPortConfEntry 6 } 1433 gBondPortConfThreshLowDnRate OBJECT-TYPE 1434 SYNTAX Unsigned32(1..10000000) 1435 UNITS "Kbps" 1436 MAX-ACCESS read-write 1437 STATUS current 1438 DESCRIPTION 1439 "This object configures the G.Bond port low downstream rate 1440 crossing alarm threshold. When the current value of 1441 gBondPortStatDnDataRate for this port reaches/drops below or 1442 exceeds this threshold, a gBondLowDnRateCrossing notification 1443 MAY be generated if enabled by 1444 gBondPortConfLowRateCrossingEnable. 1446 This object is read-write for the -O subtype G.Bond ports. 1447 It is irrelevant for the -R subtypes - attempts to read or 1448 change this object for such ports MUST be rejected (in case of 1449 SNMP with the error inconsistentValue). 1451 This object maps to the TR-159 attribute 1452 aGroupThreshDownUpRate." 1453 REFERENCE 1454 "[TR-159] 5.5.1.22" 1455 ::= { gBondPortConfEntry 7 } 1457 gBondPortConfLowRateCrossingEnable OBJECT-TYPE 1458 SYNTAX TruthValue 1459 MAX-ACCESS read-write 1460 STATUS current 1461 DESCRIPTION 1462 "Indicates whether gBondLowUpRateCrossing and 1463 gBondLowDnRateCrossing notifications should be generated 1464 for this interface. 1466 Value of true(1) indicates that the notifications are enabled. 1467 Value of false(2) indicates that the notifications are 1468 disabled. 1470 This object is read-write for the -O subtype G.Bond ports. 1471 It is irrelevant for the -R subtypes - attempts to read or 1472 change this object for such ports MUST be rejected (in case of 1473 SNMP with the error inconsistentValue). 1475 This object maps to the TR-159 attribute 1476 aGroupLowRateCrossingEnable." 1477 REFERENCE 1478 "[TR-159] 5.5.1.23" 1479 ::= { gBondPortConfEntry 8 } 1481 gBondPortConfPmTcaConfProfile OBJECT-TYPE 1482 SYNTAX SnmpAdminString (SIZE(1..32)) 1483 MAX-ACCESS read-write 1484 STATUS current 1485 DESCRIPTION 1486 "The value of this object is the index of the row in the GBS 1487 port Alarm Configuration Profile Table for Performance Monitoring 1488 Threshold Crossing Alerts - gBondPortAlarmConfProfileTable, 1489 which applies to this GBS port." 1490 DEFVAL { "DEFVAL" } 1491 ::= { gBondPortConfEntry 9 } 1493 gBondPortConfPmTcaEnable OBJECT-TYPE 1494 SYNTAX TruthValue 1495 MAX-ACCESS read-write 1496 STATUS current 1497 DESCRIPTION 1498 "Indicates whether gBondPerfTca*Crossing set of notifications 1499 should be generated for this interface. 1501 Value of true(1) indicates that the notifications are enabled. 1502 Value of false(2) indicates that the notifications are disabled. 1504 This object maps to the TR-159 attribute aGroupPerfTcaEnable." 1506 REFERENCE 1507 "[TR-159] 5.5.1.38" 1508 ::= { gBondPortConfEntry 10 } 1510 gBondPortCapTable OBJECT-TYPE 1511 SYNTAX SEQUENCE OF GBondPortCapEntry 1512 MAX-ACCESS not-accessible 1513 STATUS current 1514 DESCRIPTION 1515 "Table for capabilities of G.Bond Ports. Entries in this table 1516 MUST be maintained in a persistent manner" 1517 ::= { gBondPort 2 } 1519 gBondPortCapEntry OBJECT-TYPE 1520 SYNTAX GBondPortCapEntry 1521 MAX-ACCESS not-accessible 1522 STATUS current 1523 DESCRIPTION 1524 "An entry in the G.Bond Port Capability table. 1525 Each entry represents a G.Bond port indexed by the ifIndex. 1526 Note that a G.Bond GBS port runs on top of a single 1527 or multiple BCE port(s), which are also indexed by ifIndex." 1528 INDEX { ifIndex } 1529 ::= { gBondPortCapTable 1 } 1531 GBondPortCapEntry ::= 1532 SEQUENCE { 1533 gBondPortCapSchemesSupported GBondSchemeList, 1534 gBondPortCapPeerSchemesSupported GBondSchemeList, 1535 gBondPortCapCapacity Unsigned32, 1536 gBondPortCapPeerCapacity Unsigned32 1537 } 1539 gBondPortCapSchemesSupported OBJECT-TYPE 1540 SYNTAX GBondSchemeList 1541 MAX-ACCESS read-only 1542 STATUS current 1543 DESCRIPTION 1544 "Bonding Capability of the G.Bond port (GBS). This is a 1545 read-only bitmap of the possible bonding schemes supported by 1546 the GBS. The various bit-positions are: 1547 g9981(1) - GBS is capable of G.998.1 bonding 1548 g9982(2) - GBS is capable of G.998.2 bonding 1549 g9983(3) - GBS is capable of G.998.3 bonding 1551 Note that for ports supporting multiple bonding schemes the 1552 actual administrative scheme is set via gBondPortConfAdminScheme 1553 object. The current operating bonding scheme is reflected in 1554 the gBondPortStatOperScheme. 1556 This object maps to the TR-159 attribute 1557 aGroupBondSchemesSupported." 1558 REFERENCE 1559 "[TR-159] 5.5.1.2" 1560 ::= { gBondPortCapEntry 1 } 1562 gBondPortCapPeerSchemesSupported OBJECT-TYPE 1563 SYNTAX GBondSchemeList 1564 MAX-ACCESS read-only 1565 STATUS current 1566 DESCRIPTION 1567 "Bonding Capability of the peer G.Bond port (GBS). This is a 1568 read-only bitmap of the possible bonding schemes supported by 1569 the link partner GBS. The various bit-positions are: 1570 unknown(0) - GBS does not support bonding or 1571 the peer unit could not be reached. 1572 g9981(1) - GBS is capable of G.998.1 bonding 1573 g9982(2) - GBS is capable of G.998.2 bonding 1574 g9983(3) - GBS is capable of G.998.3 bonding 1576 Note that for ports supporting multiple bonding schemes the 1577 actual administrative scheme is set via 1578 gBondPortConfPeerAdminScheme object. The current operating 1579 bonding scheme is reflected in the gBondPortStatPeerOperScheme. 1581 This object maps to the TR-159 attribute 1582 aGroupBondPeerSchemesSupported." 1583 REFERENCE 1584 "[TR-159] 5.5.1.3" 1585 ::= { gBondPortCapEntry 2 } 1587 gBondPortCapCapacity OBJECT-TYPE 1588 SYNTAX Unsigned32 (1..32) 1589 MAX-ACCESS read-only 1590 STATUS current 1591 DESCRIPTION 1592 "Number of BCEs that can be aggregated by the local GBS. 1593 The number of BCEs currently assigned to a particular G.Bond 1594 port (gBondPortStatNumBCEs) is never greater than 1595 gBondPortCapCapacity. 1597 This object maps to the TR-159 attribute aGroupCapacity." 1598 REFERENCE 1599 "[TR-159] 5.5.1.12" 1600 ::= { gBondPortCapEntry 3 } 1602 gBondPortCapPeerCapacity OBJECT-TYPE 1603 SYNTAX Unsigned32 (0|1..32) 1604 MAX-ACCESS read-only 1605 STATUS current 1606 DESCRIPTION 1607 "Number of BCEs that can be aggregated by the peer GBS port. 1608 Value of 0 is returned when peer Bonding Capacity is unknown 1609 (peer cannot be reached). 1611 This object maps to the TR-159 attribute aGroupPeerCapacity." 1612 REFERENCE 1613 "[TR-159] 5.5.1.13" 1614 ::= { gBondPortCapEntry 4 } 1616 gBondPortStatTable OBJECT-TYPE 1617 SYNTAX SEQUENCE OF GBondPortStatEntry 1618 MAX-ACCESS not-accessible 1619 STATUS current 1620 DESCRIPTION 1621 "This table provides overall status information of G.Bond 1622 ports, complementing the generic status information from the 1623 ifTable of IF-MIB. Additional status information about 1624 connected BCEs is available from the relevant line MIBs 1626 This table contains live data from the equipment. As such, 1627 it is NOT persistent." 1628 ::= { gBondPort 3 } 1630 gBondPortStatEntry OBJECT-TYPE 1631 SYNTAX GBondPortStatEntry 1632 MAX-ACCESS not-accessible 1633 STATUS current 1634 DESCRIPTION 1635 "An entry in the G.Bond Port Status table. 1636 Each entry represents a G.Bond port indexed by the ifIndex. 1637 Note that a G.Bond GBS port runs on top of a single 1638 or multiple BCE port(s), which are also indexed by ifIndex." 1639 INDEX { ifIndex } 1640 ::= { gBondPortStatTable 1 } 1642 GBondPortStatEntry ::= 1643 SEQUENCE { 1644 gBondPortStatOperScheme GBondScheme, 1645 gBondPortStatPeerOperScheme GBondScheme, 1646 gBondPortStatUpDataRate Gauge32, 1647 gBondPortStatDnDataRate Gauge32, 1648 gBondPortStatFltStatus BITS, 1649 gBondPortStatSide INTEGER, 1650 gBondPortStatNumBCEs Unsigned32 1651 } 1653 gBondPortStatOperScheme OBJECT-TYPE 1654 SYNTAX GBondScheme 1655 MAX-ACCESS read-only 1656 STATUS current 1657 DESCRIPTION 1658 "Current operating bonding scheme of a G.Bond port. 1659 The possible values are: 1660 g9981(1) - G.998.1 bonding 1661 g9982(2) - G.998.2 bonding 1662 g9983(3) - G.998.3 bonding 1664 This object maps to the TR-159 attribute 1665 aGroupOperBondScheme." 1666 REFERENCE 1667 "[TR-159] 5.5.1.4" 1668 ::= { gBondPortStatEntry 1 } 1670 gBondPortStatPeerOperScheme OBJECT-TYPE 1671 SYNTAX GBondScheme 1672 MAX-ACCESS read-only 1673 STATUS current 1674 DESCRIPTION 1675 "Current operating bonding scheme of a G.Bond port link partner. 1676 The possible values are: 1677 unknown(0) - peer cannot be reached due to the link state 1678 g9981(1) - G.998.1 bonding 1679 g9982(2) - G.998.2 bonding 1680 g9983(3) - G.998.3 bonding 1682 This object maps to the TR-159 attribute 1683 aGroupPeerOperBondScheme." 1684 REFERENCE 1685 "[TR-159] 5.5.1.5" 1686 ::= { gBondPortStatEntry 2 } 1688 gBondPortStatUpDataRate OBJECT-TYPE 1689 SYNTAX Gauge32 1690 UNITS "bps" 1691 MAX-ACCESS read-only 1692 STATUS current 1693 DESCRIPTION 1694 "A current G.Bond port operational Data Rate in the upstream 1695 direction, in bps. 1696 This object represents an estimation of the sum of individual 1697 BCE upstream data rates, modified to compensate for 1698 fragmentation and encapsulation overhead (e.g., for an 1699 Ethernet service, the target data rate of 10Mbps SHALL allow 1700 lossless transmission of full-duplex 10Mbps Ethernet frame 1701 stream with minimal inter-frame gap). 1703 Note that for symmetrical interfaces gBondPortStatUpDataRate == 1704 gBondPortStatDnDataRate == ifSpeed. 1706 This object maps to the TR-159 attribute aGroupUpRate." 1707 REFERENCE 1708 "[TR-159] 5.5.1.15" 1709 ::= { gBondPortStatEntry 3 } 1711 gBondPortStatDnDataRate OBJECT-TYPE 1712 SYNTAX Gauge32 1713 UNITS "bps" 1714 MAX-ACCESS read-only 1715 STATUS current 1716 DESCRIPTION 1717 "A current G.Bond port operational Data Rate in the downstream 1718 direction, in bps. 1719 This object represents an estimation of the sum of individual 1720 BCE downstream data rates, modified to compensate for 1721 fragmentation and encapsulation overhead (e.g., for an 1722 Ethernet service, the target data rate of 10Mbps SHALL allow 1723 lossless transmission of full-duplex 10Mbps Ethernet frame 1724 stream with minimal inter-frame gap). 1726 Note that for symmetrical interfaces gBondPortStatUpDataRate == 1727 gBondPortStatDnDataRate == ifSpeed. 1729 This object maps to the TR-159 attribute aGroupDownRate." 1730 REFERENCE 1731 "[TR-159] 5.5.1.16" 1732 ::= { gBondPortStatEntry 4 } 1734 gBondPortStatFltStatus OBJECT-TYPE 1735 SYNTAX BITS { 1736 noPeer(0), 1737 peerPowerLoss(1), 1738 peerBondSchemeMismatch(2), 1739 bceSubTypeMismatch(3), 1740 lowRate(4), 1741 init(5), 1742 ready(6) 1743 } 1744 MAX-ACCESS read-only 1745 STATUS current 1746 DESCRIPTION 1747 "G.Bond (GBS) port Fault Status. This is a bitmap of possible 1748 conditions. The various bit positions are: 1749 noPeer - peer GBS cannot be reached (e.g., 1750 no BCEs attached, all BCEs are Down 1751 etc.). 1752 peerPowerLoss - peer GBS has indicated impending unit 1753 failure due to loss of local power 1754 ('Dying Gasp'). 1755 peerBondSchemeMismatch - operating bonding scheme of a peer 1756 GBS is different from the local one. 1757 bceSubTypeMismatch - local BCEs in the aggregation group 1758 are not of the same sub-type, e.g., 1759 some BCEs in the local device are -O 1760 while others are -R subtype. 1761 lowRate - gBondUpRate/gBondDnRate of the port 1762 has reached or dropped below 1763 gBondPortConfThreshLowUpRate/ 1764 gBondPortConfThreshLowDnRate. 1765 init - The link is Initializing, as a result of 1766 ifAdminStatus being set to 'up' for a 1767 particular BCE or a GBS to which the BCE 1768 is connected. 1769 ready - at least one BCE in the aggregation 1770 group is detecting handshake tones. 1772 This object is intended to supplement ifOperStatus object 1773 in IF-MIB. 1775 This object maps to the TR-159 attribute aGroupStatus." 1776 REFERENCE 1777 "[TR-159] 5.5.1.9; IF-MIB, ifOperStatus" 1778 ::= { gBondPortStatEntry 5 } 1780 gBondPortStatSide OBJECT-TYPE 1781 SYNTAX INTEGER { 1782 subscriber(1), 1783 office(2), 1784 unknown(3) 1785 } 1786 MAX-ACCESS read-only 1787 STATUS current 1788 DESCRIPTION 1789 "G.Bond port mode of operation (subtype). 1790 The value of 'subscriber' indicates the port is designated as 1791 '-R' subtype (all BCEs assigned to this port are of subtype 1792 '-R'). 1793 The value of the 'office' indicates that the port is 1794 designated as '-O' subtype (all BCEs assigned to this port are 1795 of subtype '-O'). 1796 The value of 'unknown' indicates that the port has no assigned 1797 BCEs yet or that the assigned BCEs are not of the same side 1798 (subTypeBCEMismatch). 1800 This object maps to the TR-159 attribute aGroupEnd." 1801 REFERENCE 1802 "[TR-159] 5.5.1.11" 1803 ::= { gBondPortStatEntry 6 } 1805 gBondPortStatNumBCEs OBJECT-TYPE 1806 SYNTAX Unsigned32 (0..32) 1807 MAX-ACCESS read-only 1808 STATUS current 1809 DESCRIPTION 1810 "Number of BCEs that is currently aggregated by the local GBS 1811 (assigned to the G.Bond port using ifStackTable). 1812 This number is never greater than gBondPortCapCapacity. 1814 This object SHALL be automatically incremented or decremented 1815 when a BCE is added or deleted to/from the G.Bond port using 1816 ifStackTable. 1818 This object maps to the TR-159 attribute aGroupNumChannels" 1819 REFERENCE 1820 "[TR-159] 5.5.1.14" 1821 ::= { gBondPortStatEntry 7 } 1823 -- Performance Monitoring group 1825 gBondPortPM OBJECT IDENTIFIER ::= { gBondPort 4 } 1827 gBondPortPmCurTable OBJECT-TYPE 1828 SYNTAX SEQUENCE OF GBondPortPmCurEntry 1829 MAX-ACCESS not-accessible 1830 STATUS current 1831 DESCRIPTION 1832 "This table contains current Performance Monitoring (PM) 1833 information for a GBS port. This table contains live data from 1834 the equipment and as such is NOT persistent." 1835 ::= { gBondPortPM 1 } 1837 gBondPortPmCurEntry OBJECT-TYPE 1838 SYNTAX GBondPortPmCurEntry 1839 MAX-ACCESS not-accessible 1840 STATUS current 1841 DESCRIPTION 1842 "An entry in the G.Bond Port PM table. 1843 Each entry represents a G.Bond port indexed by the ifIndex. 1844 Note that a G.Bond GBS port runs on top of a single 1845 or multiple BCE port(s), which are also indexed by ifIndex." 1846 INDEX { ifIndex } 1847 ::= { gBondPortPmCurTable 1 } 1849 GBondPortPmCurEntry ::= 1850 SEQUENCE { 1851 gBondPortPmCurES HCPerfTotalCount, 1852 gBondPortPmCurSES HCPerfTotalCount, 1853 gBondPortPmCurUAS HCPerfTotalCount, 1854 gBondPortPmCur15MinValidIntervals HCPerfValidIntervals, 1855 gBondPortPmCur15MinInvalidIntervals HCPerfInvalidIntervals, 1856 gBondPortPmCur15MinTimeElapsed HCPerfTimeElapsed, 1857 gBondPortPmCur15MinES HCPerfCurrentCount, 1858 gBondPortPmCur15MinSES HCPerfCurrentCount, 1859 gBondPortPmCur15MinUAS HCPerfCurrentCount, 1860 gBondPortPmCur1DayValidIntervals Unsigned32, 1861 gBondPortPmCur1DayInvalidIntervals Unsigned32, 1862 gBondPortPmCur1DayTimeElapsed HCPerfTimeElapsed, 1863 gBondPortPmCur1DayES HCPerfCurrentCount, 1864 gBondPortPmCur1DaySES HCPerfCurrentCount, 1865 gBondPortPmCur1DayUAS HCPerfCurrentCount 1866 } 1868 gBondPortPmCurES OBJECT-TYPE 1869 SYNTAX HCPerfTotalCount 1870 UNITS "seconds" 1871 MAX-ACCESS read-only 1872 STATUS current 1873 DESCRIPTION 1874 "A count of Errored Seconds (ES) on the GBS since the BTU was 1875 last restarted. 1877 An Errored Second for a G.998.x interface is defined as a count 1878 of 1-second intervals during which one or more GBS errors are 1879 declared. The errors are specific for each bonding scheme, e.g. 1880 - lost cells for the ATM bonding; 1881 - lost or discarded (due to an error or a buffer overflow) 1882 fragments for the Ethernet bonding; 1883 - CRC4, CRC6 or CRC8 errors for the TDIM bonding 1884 This object is inhibited during Unavailable Seconds (UAS). 1886 This object maps to the TR-159 attribute aGroupPerfES." 1888 REFERENCE 1889 "[TR-159] 5.5.1.29" 1890 ::= { gBondPortPmCurEntry 1 } 1892 gBondPortPmCurSES OBJECT-TYPE 1893 SYNTAX HCPerfTotalCount 1894 UNITS "seconds" 1895 MAX-ACCESS read-only 1896 STATUS current 1897 DESCRIPTION 1898 "A count of Severely Errored Seconds (SES) on the GBS since the 1899 BTU was last restarted. 1901 A Severely Errored Second for a G.998.x interface is defined as 1902 a count of 1-second intervals during which GBS errors cause at 1903 least 1% traffic loss of the nominal bonded link rate or at 1904 least 12ms for the TDM traffic. The exact definition is specific 1905 for each bonding scheme, e.g. 1906 - 234 lost cells for the ATM bonding with 10Mbps nominal link 1907 rate 1908 - 60 lost/discarded fragments for the Ethernet bonding with 1909 10Mbps nominal link rate and fixed 192 Byte-long fragment 1910 size. 1911 - 6 or more CRC4, one or more CRC6 or one or more CRC8 errors 1912 for the TDM bonding 1913 This object is inhibited during Unavailable Seconds (UAS). 1915 This object maps to the TR-159 attribute aGroupPerfSES." 1916 REFERENCE 1917 "[TR-159] 5.5.1.30" 1918 ::= { gBondPortPmCurEntry 2 } 1920 gBondPortPmCurUAS OBJECT-TYPE 1921 SYNTAX HCPerfTotalCount 1922 UNITS "seconds" 1923 MAX-ACCESS read-only 1924 STATUS current 1925 DESCRIPTION 1926 "A count of Unavailable Seconds (UAS) on the GBS since the BTU 1927 was last restarted. 1929 An Unavailable Second for a G.998.x interface is defined as a 1930 count of 1-second intervals during which the bonded link is 1931 unavailable. The G.998.x link becomes unavailable at the onset 1932 of 10 contiguous SESs. The 10 SESs are included in the 1933 unavailable time. Once unavailable, the G.998.x line becomes 1934 available at the onset of 10 contiguous seconds with no SESs. 1935 The 10 seconds with no SESs are excluded from unavailable time. 1937 This object maps to the TR-159 attribute aGroupPerfUAS." 1938 REFERENCE 1939 "[TR-159] 5.5.1.31" 1940 ::= { gBondPortPmCurEntry 3 } 1942 gBondPortPmCur15MinValidIntervals OBJECT-TYPE 1943 SYNTAX HCPerfValidIntervals 1944 MAX-ACCESS read-only 1945 STATUS current 1946 DESCRIPTION 1947 "A number of 15-minute intervals for which data was collected. 1948 The value of this object will be 96 or the maximum number of 1949 15-minute history intervals collected by the implementation 1950 unless the measurement was (re-)started recently, in which case 1951 the value will be the number of complete 15 minutes intervals 1952 for which there are at least some data. 1953 In certain cases it is possible that some intervals are 1954 unavailable. In this case, this object reports the maximum 1955 interval number for which data is available. 1957 This object maps to the TR-159 attribute 1958 aGroupPerf15MinValidIntervals." 1959 REFERENCE 1960 "[TR-159] 5.5.1.32" 1961 ::= { gBondPortPmCurEntry 4 } 1963 gBondPortPmCur15MinInvalidIntervals OBJECT-TYPE 1964 SYNTAX HCPerfInvalidIntervals 1965 MAX-ACCESS read-only 1966 STATUS current 1967 DESCRIPTION 1968 "A number of 15-minute intervals for which data was not always 1969 available. The value will typically be zero except in cases 1970 where the data for some intervals are not available. 1972 This object maps to the TR-159 attribute 1973 aGroupPerf15MinInvalidIntervals." 1974 REFERENCE 1975 "[TR-159] 5.5.1.33" 1976 ::= { gBondPortPmCurEntry 5 } 1978 gBondPortPmCur15MinTimeElapsed OBJECT-TYPE 1979 SYNTAX HCPerfTimeElapsed 1980 UNITS "seconds" 1981 MAX-ACCESS read-only 1982 STATUS current 1983 DESCRIPTION 1984 "A count of seconds that have elapsed since the beginning of the 1985 current 15-minute performance interval. 1987 This object maps to the TR-159 attribute 1988 aGroupPerfCurr15MinTimeElapsed." 1989 REFERENCE 1990 "[TR-159] 5.5.1.34" 1991 ::= { gBondPortPmCurEntry 6 } 1993 gBondPortPmCur15MinES OBJECT-TYPE 1994 SYNTAX HCPerfCurrentCount 1995 UNITS "seconds" 1996 MAX-ACCESS read-only 1997 STATUS current 1998 DESCRIPTION 1999 "A count of Errored Seconds (ES) on the GBS in the current 2000 15-minute performance interval. 2002 This object maps to the TR-159 attribute aGroupPerfCurr15MinES." 2003 REFERENCE 2004 "[TR-159] 5.5.1.35" 2005 ::= { gBondPortPmCurEntry 7 } 2007 gBondPortPmCur15MinSES OBJECT-TYPE 2008 SYNTAX HCPerfCurrentCount 2009 UNITS "seconds" 2010 MAX-ACCESS read-only 2011 STATUS current 2012 DESCRIPTION 2013 "A count of Severely Errored Seconds (ES) on the GBS in the 2014 current 15-minute performance interval. 2016 This object maps to the TR-159 attribute aGroupPerfCurr15MinSES." 2017 REFERENCE 2018 "[TR-159] 5.5.1.36" 2019 ::= { gBondPortPmCurEntry 8 } 2021 gBondPortPmCur15MinUAS OBJECT-TYPE 2022 SYNTAX HCPerfCurrentCount 2023 UNITS "seconds" 2024 MAX-ACCESS read-only 2025 STATUS current 2026 DESCRIPTION 2027 "A count of Unavailable Seconds (UAS) on the GBS in the current 2028 15-minute performance interval. 2030 This object maps to the TR-159 attribute aGroupPerfCurr15MinUAS." 2031 REFERENCE 2032 "[TR-159] 5.5.1.37" 2034 ::= { gBondPortPmCurEntry 9 } 2036 gBondPortPmCur1DayValidIntervals OBJECT-TYPE 2037 SYNTAX Unsigned32 (0..7) 2038 UNITS "days" 2039 MAX-ACCESS read-only 2040 STATUS current 2041 DESCRIPTION 2042 "A number of 1-day intervals for which data was collected. 2043 The value of this object will be 7 or the maximum number of 2044 1-day history intervals collected by the implementation unless 2045 the measurement was (re-)started recently, in which case the 2046 value will be the number of complete 1-day intervals for which 2047 there are at least some data. 2048 In certain cases it is possible that some intervals are 2049 unavailable. In this case, this object reports the maximum 2050 interval number for which data is available. 2052 This object maps to the TR-159 attribute 2053 aGroupPerf1DayValidIntervals." 2054 REFERENCE 2055 "[TR-159] 5.5.1.45" 2056 ::= { gBondPortPmCurEntry 10 } 2058 gBondPortPmCur1DayInvalidIntervals OBJECT-TYPE 2059 SYNTAX Unsigned32 (0..7) 2060 UNITS "days" 2061 MAX-ACCESS read-only 2062 STATUS current 2063 DESCRIPTION 2064 "A number of 1-day intervals for which data was not always 2065 available. The value will typically be zero except in cases 2066 where the data for some intervals are not available. 2068 This object maps to the TR-159 attribute 2069 aGroupPerf1DayInvalidIntervals." 2070 REFERENCE 2071 "[TR-159] 5.5.1.46" 2072 ::= { gBondPortPmCurEntry 11 } 2074 gBondPortPmCur1DayTimeElapsed OBJECT-TYPE 2075 SYNTAX HCPerfTimeElapsed 2076 UNITS "seconds" 2077 MAX-ACCESS read-only 2078 STATUS current 2079 DESCRIPTION 2080 "A count of seconds that have elapsed since the beginning of 2081 the current 1-day performance interval. 2083 This object maps to the TR-159 attribute 2084 aGroupPerfCurr1DayTimeElapsed." 2085 REFERENCE 2086 "[TR-159] 5.5.1.47" 2087 ::= { gBondPortPmCurEntry 12 } 2089 gBondPortPmCur1DayES OBJECT-TYPE 2090 SYNTAX HCPerfCurrentCount 2091 UNITS "seconds" 2092 MAX-ACCESS read-only 2093 STATUS current 2094 DESCRIPTION 2095 "A count of Errored Seconds (ES) on the GBS in the current 1-day 2096 performance interval. 2098 This object maps to the TR-159 attribute aGroupPerfCurr1DayES." 2099 REFERENCE 2100 "[TR-159] 5.5.1.48" 2101 ::= { gBondPortPmCurEntry 13 } 2103 gBondPortPmCur1DaySES OBJECT-TYPE 2104 SYNTAX HCPerfCurrentCount 2105 UNITS "seconds" 2106 MAX-ACCESS read-only 2107 STATUS current 2108 DESCRIPTION 2109 "A count of Severely Errored Seconds (ES) on the GBS in the 2110 current 1-day performance interval. 2112 This object maps to the TR-159 attribute aGroupPerfCurr1DaySES." 2113 REFERENCE 2114 "[TR-159] 5.5.1.49" 2115 ::= { gBondPortPmCurEntry 14 } 2117 gBondPortPmCur1DayUAS OBJECT-TYPE 2118 SYNTAX HCPerfCurrentCount 2119 UNITS "seconds" 2120 MAX-ACCESS read-only 2121 STATUS current 2122 DESCRIPTION 2123 "A count of Unavailable Seconds (UAS) on the GBS in the current 2124 1-day performance interval. 2126 This object maps to the TR-159 attribute aGroupPerfCurr1DayUAS." 2127 REFERENCE 2128 "[TR-159] 5.5.1.50" 2129 ::= { gBondPortPmCurEntry 15 } 2131 -- PM history: 15-min buckets 2133 gBondPortPm15MinTable OBJECT-TYPE 2134 SYNTAX SEQUENCE OF GBondPortPm15MinEntry 2135 MAX-ACCESS not-accessible 2136 STATUS current 2137 DESCRIPTION 2138 "This table contains historical 15-minute buckets of Performance 2139 Monitoring information for a GBS port (a row for each 15-minute 2140 interval, up to 96 intervals). 2141 Entries in this table MUST be maintained in a persistent manner." 2142 ::= { gBondPortPM 2 } 2144 gBondPortPm15MinEntry OBJECT-TYPE 2145 SYNTAX GBondPortPm15MinEntry 2146 MAX-ACCESS not-accessible 2147 STATUS current 2148 DESCRIPTION 2149 "An entry in the G.Bond Port historical 15-minute PM table. 2150 Each entry represents performance monitoring data for a GBS port, 2151 indexed by ifIndex, collected during a particular 15-minute 2152 interval, indexed by gBondPortPm15MinIntervalIndex." 2153 INDEX { ifIndex, gBondPortPm15MinIntervalIndex } 2154 ::= { gBondPortPm15MinTable 1 } 2156 GBondPortPm15MinEntry ::= 2157 SEQUENCE { 2158 gBondPortPm15MinIntervalIndex Unsigned32, 2159 gBondPortPm15MinIntervalMoniTime HCPerfTimeElapsed, 2160 gBondPortPm15MinIntervalES HCPerfIntervalCount, 2161 gBondPortPm15MinIntervalSES HCPerfIntervalCount, 2162 gBondPortPm15MinIntervalUAS HCPerfIntervalCount, 2163 gBondPortPm15MinIntervalValid TruthValue 2164 } 2166 gBondPortPm15MinIntervalIndex OBJECT-TYPE 2167 SYNTAX Unsigned32 (1..96) 2168 MAX-ACCESS not-accessible 2169 STATUS current 2170 DESCRIPTION 2171 "Performance Data Interval number. 1 is the most recent previous 2172 interval; interval 96 is 24 hours ago. 2173 Intervals 2..96 are OPTIONAL. 2175 This object maps to the TR-159 attribute 2176 aGroupPerf15MinIntervalNumber." 2177 REFERENCE 2178 "[TR-159] 5.5.1.57" 2180 ::= { gBondPortPm15MinEntry 1 } 2182 gBondPortPm15MinIntervalMoniTime OBJECT-TYPE 2183 SYNTAX HCPerfTimeElapsed 2184 UNITS "seconds" 2185 MAX-ACCESS read-only 2186 STATUS current 2187 DESCRIPTION 2188 "A count of seconds over which the performance data was actually 2189 monitored. This value will be the same as the interval duration 2190 (900 seconds), except in a situation where performance data 2191 could not be collected for any reason." 2192 ::= { gBondPortPm15MinEntry 2 } 2194 gBondPortPm15MinIntervalES OBJECT-TYPE 2195 SYNTAX HCPerfIntervalCount 2196 UNITS "seconds" 2197 MAX-ACCESS read-only 2198 STATUS current 2199 DESCRIPTION 2200 "A count of Errored Seconds (ES) on the GBS in the 15-minute 2201 performance history interval. 2203 This object maps to the TR-159 attribute 2204 aGroupPerf15MinIntervalES." 2205 REFERENCE 2206 "[TR-159] 5.5.1.59" 2207 ::= { gBondPortPm15MinEntry 3 } 2209 gBondPortPm15MinIntervalSES OBJECT-TYPE 2210 SYNTAX HCPerfIntervalCount 2211 UNITS "seconds" 2212 MAX-ACCESS read-only 2213 STATUS current 2214 DESCRIPTION 2215 "A count of Severely Errored Seconds (ES) on the GBS in the 2216 15-minute performance history interval. 2218 This object maps to the TR-159 attribute 2219 aGroupPerf15MinIntervalSES." 2220 REFERENCE 2221 "[TR-159] 5.5.1.60" 2222 ::= { gBondPortPm15MinEntry 4 } 2224 gBondPortPm15MinIntervalUAS OBJECT-TYPE 2225 SYNTAX HCPerfIntervalCount 2226 UNITS "seconds" 2227 MAX-ACCESS read-only 2228 STATUS current 2229 DESCRIPTION 2230 "A count of Unavailable Seconds (UAS) on the GBS in the current 2231 15-minute performance interval. 2233 This object maps to the TR-159 attribute aGroupPerfCurr15MinUAS." 2234 REFERENCE 2235 "[TR-159] 5.5.1.61" 2236 ::= { gBondPortPm15MinEntry 5 } 2238 gBondPortPm15MinIntervalValid OBJECT-TYPE 2239 SYNTAX TruthValue 2240 MAX-ACCESS read-only 2241 STATUS current 2242 DESCRIPTION 2243 "A read-only object indicating whether or not this history 2244 bucket contains valid data. Valid bucket is reported as true(1) 2245 and invalid bucket as false(2). 2246 If this history bucket is invalid the BTU-C MUST NOT produce 2247 notifications based upon the value of the counters in this 2248 bucket. 2249 Note that an implementation may decide not to store invalid 2250 history buckets in its data base. In such case this object is 2251 not required as only valid history buckets are available while 2252 invalid history buckets are simply not in the data base. 2254 This object maps to the TR-159 attribute 2255 aGroupPerf15MinIntervalValid." 2256 REFERENCE 2257 "[TR-159] 5.5.1.58" 2258 ::= { gBondPortPm15MinEntry 6 } 2260 -- PM history: 1-day buckets 2262 gBondPortPm1DayTable OBJECT-TYPE 2263 SYNTAX SEQUENCE OF GBondPortPm1DayEntry 2264 MAX-ACCESS not-accessible 2265 STATUS current 2266 DESCRIPTION 2267 "This table contains historical 1-day buckets of Performance 2268 Monitoring information for a GBS port (a row for each 1-day 2269 interval, up to 7 intervals). 2270 Entries in this table MUST be maintained in a persistent manner." 2271 ::= { gBondPortPM 3 } 2273 gBondPortPm1DayEntry OBJECT-TYPE 2274 SYNTAX GBondPortPm1DayEntry 2275 MAX-ACCESS not-accessible 2276 STATUS current 2277 DESCRIPTION 2278 "An entry in the G.Bond Port historical 1-day PM table. 2279 Each entry represents performance monitoring data for a GBS port, 2280 indexed by ifIndex, collected during a particular 1-day 2281 interval, indexed by gBondPortPm1DayIntervalIndex." 2282 INDEX { ifIndex, gBondPortPm1DayIntervalIndex } 2283 ::= { gBondPortPm1DayTable 1 } 2285 GBondPortPm1DayEntry ::= 2286 SEQUENCE { 2287 gBondPortPm1DayIntervalIndex Unsigned32, 2288 gBondPortPm1DayIntervalMoniTime HCPerfTimeElapsed, 2289 gBondPortPm1DayIntervalES HCPerfIntervalCount, 2290 gBondPortPm1DayIntervalSES HCPerfIntervalCount, 2291 gBondPortPm1DayIntervalUAS HCPerfIntervalCount, 2292 gBondPortPm1DayIntervalValid TruthValue 2293 } 2295 gBondPortPm1DayIntervalIndex OBJECT-TYPE 2296 SYNTAX Unsigned32 (1..7) 2297 MAX-ACCESS not-accessible 2298 STATUS current 2299 DESCRIPTION 2300 "Performance Data Interval number. 1 is the most recent previous 2301 interval; interval 7 is 7 days ago. 2302 Intervals 2..7 are OPTIONAL. 2304 This object maps to the TR-159 attribute 2305 aGroupPerf1DayIntervalNumber." 2306 REFERENCE 2307 "[TR-159] 5.5.1.62" 2308 ::= { gBondPortPm1DayEntry 1 } 2310 gBondPortPm1DayIntervalMoniTime OBJECT-TYPE 2311 SYNTAX HCPerfTimeElapsed 2312 UNITS "seconds" 2313 MAX-ACCESS read-only 2314 STATUS current 2315 DESCRIPTION 2316 "A count of seconds over which the performance data was actually 2317 monitored. This value will be the same as the interval duration 2318 (86400 seconds), except in a situation where performance data 2319 could not be collected for any reason. 2321 This object maps to the TR-159 attribute 2322 aGroupPerf1DayIntervalMoniSecs." 2323 REFERENCE 2324 "[TR-159] 5.5.1.64" 2325 ::= { gBondPortPm1DayEntry 2 } 2327 gBondPortPm1DayIntervalES OBJECT-TYPE 2328 SYNTAX HCPerfIntervalCount 2329 UNITS "seconds" 2330 MAX-ACCESS read-only 2331 STATUS current 2332 DESCRIPTION 2333 "A count of Errored Seconds (ES) on the GBS in the 1-day 2334 performance history interval. 2336 This object maps to the TR-159 attribute 2337 aGroupPerf1DayIntervalES." 2338 REFERENCE 2339 "[TR-159] 5.5.1.65" 2340 ::= { gBondPortPm1DayEntry 3 } 2342 gBondPortPm1DayIntervalSES OBJECT-TYPE 2343 SYNTAX HCPerfIntervalCount 2344 UNITS "seconds" 2345 MAX-ACCESS read-only 2346 STATUS current 2347 DESCRIPTION 2348 "A count of Severely Errored Seconds (ES) on the GBS in the 2349 1-day performance history interval. 2351 This object maps to the TR-159 attribute 2352 aGroupPerf1DayIntervalSES." 2353 REFERENCE 2354 "[TR-159] 5.5.1.66" 2355 ::= { gBondPortPm1DayEntry 4 } 2357 gBondPortPm1DayIntervalUAS OBJECT-TYPE 2358 SYNTAX HCPerfIntervalCount 2359 UNITS "seconds" 2360 MAX-ACCESS read-only 2361 STATUS current 2362 DESCRIPTION 2363 "A count of Unavailable Seconds (UAS) on the GBS in the current 2364 1-day performance interval. 2366 This object maps to the TR-159 attribute aGroupPerfCurr1DayUAS." 2367 REFERENCE 2368 "[TR-159] 5.5.1.67" 2369 ::= { gBondPortPm1DayEntry 5 } 2371 gBondPortPm1DayIntervalValid OBJECT-TYPE 2372 SYNTAX TruthValue 2373 MAX-ACCESS read-only 2374 STATUS current 2375 DESCRIPTION 2376 "A read-only object indicating whether or not this history 2377 bucket contains valid data. Valid bucket is reported as true(1) 2378 and invalid bucket as false(2). 2379 If this history bucket is invalid the BTU-C MUST NOT produce 2380 notifications based upon the value of the counters in this 2381 bucket. 2382 Note that an implementation may decide not to store invalid 2383 history buckets in its data base. In such case this object is 2384 not required as only valid history buckets are available while 2385 invalid history buckets are simply not in the data base. 2387 This object maps to the TR-159 attribute 2388 aGroupPerf1DayIntervalValid." 2389 REFERENCE 2390 "[TR-159] 5.5.1.63" 2391 ::= { gBondPortPm1DayEntry 6 } 2393 -- Performance Monitoring TCA Configuration profile 2395 gBondPortPmTcaProfileTable OBJECT-TYPE 2396 SYNTAX SEQUENCE OF GBondPortPmTcaProfileEntry 2397 MAX-ACCESS not-accessible 2398 STATUS current 2399 DESCRIPTION 2400 "This table supports definitions of Performance Monitoring (PM) 2401 Threshold Crossing Alerts (TCA) configuration profiles for GBS 2402 ports. 2403 Entries in this table MUST be maintained in a persistent manner." 2404 ::= { gBondPortPM 4 } 2406 gBondPortPmTcaProfileEntry OBJECT-TYPE 2407 SYNTAX GBondPortPmTcaProfileEntry 2408 MAX-ACCESS not-accessible 2409 STATUS current 2410 DESCRIPTION 2411 "An entry in the GBS PM TCA Configuration table. 2412 Each entry corresponds to a single TCA configuration profile. 2413 Each profile contains a set of parameters for setting alarm 2414 thresholds for various performance attributes monitored at GBS 2415 ports. Profiles may be created/deleted using the row 2416 creation/deletion mechanism via 2417 gBondPortPmTcaProfileRowStatus. If an active entry is 2418 referenced via gBondPortConfPmTcaConfProfile, the entry MUST 2419 remain active until all references are removed. 2420 A default profile with an index of 'DEFVAL', will always exist 2421 and its parameters will be set to vendor specific values, 2422 unless otherwise specified in this document." 2423 INDEX { gBondPortPmTcaProfileName } 2424 ::= { gBondPortPmTcaProfileTable 1 } 2426 GBondPortPmTcaProfileEntry ::= 2427 SEQUENCE { 2428 gBondPortPmTcaProfileName SnmpAdminString, 2429 gBondPortPmTcaProfileThresh15MinES HCPerfIntervalThreshold, 2430 gBondPortPmTcaProfileThresh15MinSES HCPerfIntervalThreshold, 2431 gBondPortPmTcaProfileThresh15MinUAS HCPerfIntervalThreshold, 2432 gBondPortPmTcaProfileThresh1DayES GBondPm1DayIntervalThreshold, 2433 gBondPortPmTcaProfileThresh1DaySES GBondPm1DayIntervalThreshold, 2434 gBondPortPmTcaProfileThresh1DayUAS GBondPm1DayIntervalThreshold, 2435 gBondPortPmTcaProfileRowStatus RowStatus 2436 } 2438 gBondPortPmTcaProfileName OBJECT-TYPE 2439 SYNTAX SnmpAdminString (SIZE(1..32)) 2440 MAX-ACCESS not-accessible 2441 STATUS current 2442 DESCRIPTION 2443 "This object is a unique index (name) associated with this 2444 GBS PM TCA profile." 2445 ::= { gBondPortPmTcaProfileEntry 1 } 2447 gBondPortPmTcaProfileThresh15MinES OBJECT-TYPE 2448 SYNTAX HCPerfIntervalThreshold 2449 UNITS "seconds" 2450 MAX-ACCESS read-create 2451 STATUS current 2452 DESCRIPTION 2453 "A desired threshold for the number of Errored Seconds (ES) 2454 within any given 15-minute performance data collection interval. 2455 If the number of ESs in a particular 15-minute collection 2456 interval reaches or exceeds this value, a 2457 gBondPmTca15MinESCrossing notification MAY be generated if 2458 enabled by gBondPortConfPmTcaEnable. 2459 At most one notification can be sent per interval. 2460 Setting this attribute to zero (default) effectively disables 2461 gBondPmTca15MinESCrossing notification. 2463 This object maps to the TR-159 attribute 2464 aGroupPerfThreshold15MinES." 2465 REFERENCE 2466 "[TR-159] 5.5.1.39" 2468 ::= { gBondPortPmTcaProfileEntry 2 } 2470 gBondPortPmTcaProfileThresh15MinSES OBJECT-TYPE 2471 SYNTAX HCPerfIntervalThreshold 2472 UNITS "seconds" 2473 MAX-ACCESS read-create 2474 STATUS current 2475 DESCRIPTION 2476 "A desired threshold for the number of Severely Errored Seconds 2477 (SES) within any given 15-minute performance data collection 2478 interval. 2479 If the number of SESs in a particular 15-minute collection 2480 interval reaches or exceeds this value, a 2481 gBondPmTca15MinSESCrossing notification MAY be generated if 2482 enabled by gBondPortConfPmTcaEnable. 2483 At most one notification can be sent per interval. 2484 Setting this attribute to zero (default) effectively disables 2485 gBondPmTca15MinSESCrossing notification. 2487 This object maps to the TR-159 attribute 2488 aGroupPerfThreshold15MinSES." 2489 REFERENCE 2490 "[TR-159] 5.5.1.40" 2491 ::= { gBondPortPmTcaProfileEntry 3 } 2493 gBondPortPmTcaProfileThresh15MinUAS OBJECT-TYPE 2494 SYNTAX HCPerfIntervalThreshold 2495 UNITS "seconds" 2496 MAX-ACCESS read-create 2497 STATUS current 2498 DESCRIPTION 2499 "A desired threshold for the number of Unavailable Seconds (UAS) 2500 within any given 15-minute performance data collection interval. 2501 If the number of UASs in a particular 15-minute collection 2502 interval reaches or exceeds this value, a 2503 gBondPmTca15MinUASCrossing notification MAY be generated if 2504 enabled by gBondPortConfPmTcaEnable. 2505 At most one notification can be sent per interval. 2506 Setting this attribute to zero (default) effectively disables 2507 gBondPmTca15MinUASCrossing notification. 2509 This object maps to the TR-159 attribute 2510 aGroupPerfThreshold15MinUAS." 2511 REFERENCE 2512 "[TR-159] 5.5.1.41" 2513 ::= { gBondPortPmTcaProfileEntry 4 } 2515 gBondPortPmTcaProfileThresh1DayES OBJECT-TYPE 2516 SYNTAX GBondPm1DayIntervalThreshold 2517 UNITS "seconds" 2518 MAX-ACCESS read-create 2519 STATUS current 2520 DESCRIPTION 2521 "A desired threshold for the number of Errored Seconds (ES) 2522 within any given 1-day performance data collection interval. 2523 If the number of ESs in a particular 1-day collection interval 2524 reaches or exceeds this value, a gBondPmTca1DayESCrossing 2525 notification MAY be generated if enabled by 2526 gBondPortConfPmTcaEnable. 2527 At most one notification can be sent per interval. 2528 Setting this attribute to zero (default) effectively disables 2529 gBondPmTca1DayESCrossing notification. 2531 This object maps to the TR-159 attribute 2532 aGroupPerfThreshold1DayES." 2533 REFERENCE 2534 "[TR-159] 5.5.1.51" 2535 ::= { gBondPortPmTcaProfileEntry 5 } 2537 gBondPortPmTcaProfileThresh1DaySES OBJECT-TYPE 2538 SYNTAX GBondPm1DayIntervalThreshold 2539 UNITS "seconds" 2540 MAX-ACCESS read-create 2541 STATUS current 2542 DESCRIPTION 2543 "A desired threshold for the number of Severely Errored Seconds 2544 (SES) within any given 1-day performance data collection 2545 interval. 2546 If the number of SESs in a particular 1-day collection interval 2547 reaches or exceeds this value, a gBondPmTca1DaySESCrossing 2548 notification MAY be generated if enabled by 2549 gBondPortConfPmTcaEnable. 2550 At most one notification can be sent per interval. 2551 Setting this attribute to zero (default) effectively disables 2552 gBondPmTca1DaySESCrossing notification. 2554 This object maps to the TR-159 attribute 2555 aGroupPerfThreshold1DaySES." 2556 REFERENCE 2557 "[TR-159] 5.5.1.52" 2558 ::= { gBondPortPmTcaProfileEntry 6 } 2560 gBondPortPmTcaProfileThresh1DayUAS OBJECT-TYPE 2561 SYNTAX GBondPm1DayIntervalThreshold 2562 UNITS "seconds" 2563 MAX-ACCESS read-create 2564 STATUS current 2565 DESCRIPTION 2566 "A desired threshold for the number of Unavailable Seconds (UAS) 2567 within any given 1-day performance data collection interval. 2568 If the number of UASs in a particular 1-day collection interval 2569 reaches or exceeds this value, a gBondPmTca1DayUASCrossing 2570 notification MAY be generated if enabled by 2571 gBondPortConfPmTcaEnable. 2572 At most one notification can be sent per interval. 2573 Setting this attribute to zero (default) effectively disables 2574 gBondPmTca1DayUASCrossing notification. 2576 This object maps to the TR-159 attribute 2577 aGroupPerfThreshold1DayUAS." 2578 REFERENCE 2579 "[TR-159] 5.5.1.53" 2580 ::= { gBondPortPmTcaProfileEntry 7 } 2582 gBondPortPmTcaProfileRowStatus OBJECT-TYPE 2583 SYNTAX RowStatus 2584 MAX-ACCESS read-create 2585 STATUS current 2586 DESCRIPTION 2587 "This object controls the creation, modification, or deletion 2588 of the associated entry in the gBondPortPmTcaProfileTable 2589 per the semantics of RowStatus. 2591 If an 'active' entry is referenced via 2592 gBondPortConfPmTcaConfProfile instance(s), the entry MUST 2593 remain 'active'. 2595 An 'active' entry SHALL NOT be modified. In order to modify an 2596 existing entry, it MUST be taken out of service (by setting 2597 this object to 'notInService'), modified, and set 'active' 2598 again." 2599 ::= { gBondPortPmTcaProfileEntry 8 } 2601 -- The BCE group 2603 gBondBceConfTable OBJECT-TYPE 2604 SYNTAX SEQUENCE OF GBondBceConfEntry 2605 MAX-ACCESS not-accessible 2606 STATUS current 2607 DESCRIPTION 2608 "Table for Configuration of G.Bond common aspects for the 2609 Bonding Channel Entity (BCE) ports (modems/channels). 2611 Entries in this table MUST be maintained in a persistent 2612 manner." 2613 ::= { gBondBce 1 } 2615 gBondBceConfEntry OBJECT-TYPE 2616 SYNTAX GBondBceConfEntry 2617 MAX-ACCESS not-accessible 2618 STATUS current 2619 DESCRIPTION 2620 "An entry in the G.Bond BCE Configuration table. 2621 Each entry represents common aspects of a G.Bond BCE port 2622 indexed by the ifIndex. Note that a G.Bond BCE port can be 2623 stacked below a single GBS port, also indexed by ifIndex, 2624 possibly together with other BCE ports if GAF is enabled." 2625 INDEX { ifIndex } 2626 ::= { gBondBceConfTable 1 } 2628 GBondBceConfEntry ::= 2629 SEQUENCE { 2630 gBondBceConfRemoteDiscoveryCode PhysAddress 2631 } 2633 gBondBceConfRemoteDiscoveryCode OBJECT-TYPE 2634 SYNTAX PhysAddress (SIZE(0|6)) 2635 MAX-ACCESS read-write 2636 STATUS current 2637 DESCRIPTION 2638 "A Remote Discovery Code of the BCE port at CO. 2639 A 6 octet long Discovery Code of the peer GBS connected via 2640 the BCE. 2641 Reading this object results in a Discovery Get operation. 2642 Setting this object to all zeroes results in a Discovery 2643 Clear_if_Same operation (the value of gBondPortConfDiscoveryCode 2644 at the peer GBS SHALL be the same as gBondPortConfDiscoveryCode 2645 of the local GBS associated with the BCE for the operation to 2646 succeed). 2647 Writing a non-zero value to this object results in a 2648 Discovery Set_if_Clear operation. 2649 A zero-length octet string SHALL be returned on an attempt to 2650 read this object when GAF aggregation is not enabled. 2652 This object is irrelevant in BCE-R port subtypes (CPE side): 2653 in this case a zero length octet string SHALL be returned on 2654 an attempt to read this object, an attempt to change this object 2655 MUST be rejected (in case of SNMP with the error 2656 inconsistentValue). 2658 Discovery MUST be performed when the link is Down. 2660 Attempts to change this object MUST be rejected (in case of 2661 SNMP with the error inconsistentValue), If the link is Up or 2662 Initializing. 2664 This object maps to the TR-159 attribute 2665 aLineRemoteDiscoveryCode." 2666 REFERENCE 2667 "[TR-159] 5.5.6.7" 2668 ::= { gBondBceConfEntry 1 } 2670 -- 2671 -- Conformance Statements 2672 -- 2674 gBondGroups OBJECT IDENTIFIER ::= { gBondConformance 1 } 2676 gBondCompliances OBJECT IDENTIFIER ::= { gBondConformance 2 } 2678 -- Object Groups 2680 gBondBasicGroup OBJECT-GROUP 2681 OBJECTS { 2682 gBondPortStatOperScheme, 2683 gBondPortStatUpDataRate, 2684 gBondPortStatDnDataRate, 2685 gBondPortConfTargetUpDataRate, 2686 gBondPortConfTargetDnDataRate, 2687 gBondPortCapCapacity, 2688 gBondPortStatNumBCEs, 2689 gBondPortStatSide, 2690 gBondPortStatFltStatus 2691 } 2692 STATUS current 2693 DESCRIPTION 2694 "A collection of objects representing management information 2695 common to all types of G.Bond ports." 2696 ::= { gBondGroups 1 } 2698 gBondDiscoveryGroup OBJECT-GROUP 2699 OBJECTS { 2700 gBondPortStatPeerOperScheme, 2701 gBondPortCapPeerCapacity, 2702 gBondPortConfDiscoveryCode, 2703 gBondBceConfRemoteDiscoveryCode 2704 } 2705 STATUS current 2706 DESCRIPTION 2707 "A collection of objects supporting OPTIONAL G.Bond discovery 2708 in G.Bond ports." 2709 ::= { gBondGroups 2 } 2711 gBondMultiSchemeGroup OBJECT-GROUP 2712 OBJECTS { 2713 gBondPortCapSchemesSupported, 2714 gBondPortCapPeerSchemesSupported, 2715 gBondPortConfAdminScheme, 2716 gBondPortConfPeerAdminScheme 2717 } 2718 STATUS current 2719 DESCRIPTION 2720 "A collection of objects providing OPTIONAL management 2721 information for G.Bond ports supporting multiple bonding 2722 schemes." 2723 ::= { gBondGroups 3 } 2725 gBondTcaConfGroup OBJECT-GROUP 2726 OBJECTS { 2727 gBondPortConfThreshLowUpRate, 2728 gBondPortConfThreshLowDnRate, 2729 gBondPortConfLowRateCrossingEnable 2730 } 2731 STATUS current 2732 DESCRIPTION 2733 "A collection of objects required for configuration of alarm 2734 thresholds and notifications in G.Bond ports." 2735 ::= { gBondGroups 4 } 2737 gBondTcaNotificationGroup NOTIFICATION-GROUP 2738 NOTIFICATIONS { 2739 gBondLowUpRateCrossing, 2740 gBondLowDnRateCrossing 2741 } 2742 STATUS current 2743 DESCRIPTION 2744 "This group supports notifications of significant conditions 2745 (non-PM threshold crossing alerts) associated with G.Bond ports." 2746 ::= { gBondGroups 5 } 2748 gBondPmCurGroup OBJECT-GROUP 2749 OBJECTS { 2750 gBondPortPmCurES, 2751 gBondPortPmCurSES, 2752 gBondPortPmCurUAS, 2753 gBondPortPmCur15MinValidIntervals, 2754 gBondPortPmCur15MinInvalidIntervals, 2755 gBondPortPmCur15MinTimeElapsed, 2756 gBondPortPmCur15MinES, 2757 gBondPortPmCur15MinSES, 2758 gBondPortPmCur15MinUAS, 2759 gBondPortPmCur1DayValidIntervals, 2760 gBondPortPmCur1DayInvalidIntervals, 2761 gBondPortPmCur1DayTimeElapsed, 2762 gBondPortPmCur1DayES, 2763 gBondPortPmCur1DaySES, 2764 gBondPortPmCur1DayUAS 2765 } 2766 STATUS current 2767 DESCRIPTION 2768 "A collection of objects supporting OPTIONAL current Performance 2769 Monitoring information for G.Bond ports." 2770 ::= { gBondGroups 6 } 2772 gBondPm15MinGroup OBJECT-GROUP 2773 OBJECTS { 2774 gBondPortPm15MinIntervalMoniTime, 2775 gBondPortPm15MinIntervalES, 2776 gBondPortPm15MinIntervalSES, 2777 gBondPortPm15MinIntervalUAS, 2778 gBondPortPm15MinIntervalValid 2779 } 2780 STATUS current 2781 DESCRIPTION 2782 "A collection of objects supporting OPTIONAL historical 2783 Performance Monitoring information for G.Bond ports, during 2784 previous 15-minute intervals ." 2785 ::= { gBondGroups 7 } 2787 gBondPm1DayGroup OBJECT-GROUP 2788 OBJECTS { 2789 gBondPortPm1DayIntervalMoniTime, 2790 gBondPortPm1DayIntervalES, 2791 gBondPortPm1DayIntervalSES, 2792 gBondPortPm1DayIntervalUAS, 2793 gBondPortPm1DayIntervalValid 2794 } 2795 STATUS current 2796 DESCRIPTION 2797 "A collection of objects supporting OPTIONAL historical 2798 Performance Monitoring information for G.Bond ports, during 2799 previous 1-day intervals ." 2800 ::= { gBondGroups 8 } 2802 gBondPmTcaConfGroup OBJECT-GROUP 2803 OBJECTS { 2804 gBondPortConfPmTcaConfProfile, 2805 gBondPortConfPmTcaEnable, 2806 gBondPortPmTcaProfileThresh15MinES, 2807 gBondPortPmTcaProfileThresh15MinSES, 2808 gBondPortPmTcaProfileThresh15MinUAS, 2809 gBondPortPmTcaProfileThresh1DayES, 2810 gBondPortPmTcaProfileThresh1DaySES, 2811 gBondPortPmTcaProfileThresh1DayUAS, 2812 gBondPortPmTcaProfileRowStatus 2813 } 2814 STATUS current 2815 DESCRIPTION 2816 "A collection of objects required for configuration of 2817 Performance Monitoring Threshold Crossing Alert notifications 2818 in G.Bond ports." 2819 ::= { gBondGroups 9 } 2821 gBondPmTcaNotificationGroup NOTIFICATION-GROUP 2822 NOTIFICATIONS { 2823 gBondPmTca15MinESCrossing, 2824 gBondPmTca15MinSESCrossing, 2825 gBondPmTca15MinUASCrossing, 2826 gBondPmTca1DayESCrossing, 2827 gBondPmTca1DaySESCrossing, 2828 gBondPmTca1DayUASCrossing 2829 } 2830 STATUS current 2831 DESCRIPTION 2832 "This group supports notifications of performance monitoring 2833 thresholds crossing alerts associated with G.Bond ports." 2834 ::= { gBondGroups 10 } 2836 -- Compliance Statements 2838 gBondCompliance MODULE-COMPLIANCE 2839 STATUS current 2840 DESCRIPTION 2841 "The compliance statement for G.Bond interfaces. 2842 Compliance with the following external compliance statements 2843 is REQUIRED: 2845 MIB Module Compliance Statement 2846 ---------- -------------------- 2847 IF-MIB ifCompliance3 2849 Compliance with the following external compliance statements 2850 is OPTIONAL for implementations supporting bonding with 2851 flexible cross-connect between the GBS and BCE ports: 2853 MIB Module Compliance Statement 2854 ---------- -------------------- 2855 IF-INVERTED-STACK-MIB ifInvCompliance 2856 IF-CAP-STACK-MIB ifCapStackCompliance" 2858 MODULE -- this module 2859 MANDATORY-GROUPS { 2860 gBondBasicGroup, 2861 gBondTcaConfGroup, 2862 gBondTcaNotificationGroup 2863 } 2865 GROUP gBondDiscoveryGroup 2866 DESCRIPTION 2867 "Support for this group is only required for implementations 2868 supporting G.Bond Discovery function." 2870 GROUP gBondMultiSchemeGroup 2871 DESCRIPTION 2872 "Support for this group is only required for implementations 2873 supporting multiple bonding schemes." 2875 GROUP gBondPmCurGroup 2876 DESCRIPTION 2877 "Support for this group is only required for implementations 2878 supporting Performance Monitoring." 2880 GROUP gBondPm15MinGroup 2881 DESCRIPTION 2882 "Support for this group is only required for implementations 2883 supporting 15-min historical Performance Monitoring." 2885 GROUP gBondPm1DayGroup 2886 DESCRIPTION 2887 "Support for this group is only required for implementations 2888 supporting 1-day historical Performance Monitoring." 2890 GROUP gBondPmTcaConfGroup 2891 DESCRIPTION 2892 "Support for this group is only required for implementations 2893 supporting Performance Monitoring Threshold Crossing Alert 2894 notifications." 2896 GROUP gBondPmTcaNotificationGroup 2897 DESCRIPTION 2898 "Support for this group is only required for implementations 2899 supporting Performance Monitoring Threshold Crossing Alert 2900 notifications." 2902 ::= { gBondCompliances 1 } 2903 END 2905 7. Security Considerations 2907 There is a number of managed objects defined in this MIB module with 2908 a MAX-ACCESS clause of read-write and/or read-create. Such objects 2909 may be considered sensitive or vulnerable in some network 2910 environments. The support for SET operations in a non-secure 2911 environment without proper protection can have a negative effect on 2912 network operations. These are the tables and objects and their 2913 sensitivity/vulnerability: 2915 o Changing of gBondPortConfAdminScheme may lead to a potential 2916 locking of the link, if the peer device does not support desired 2917 bonding scheme. 2919 o Changing of gBondPortConfDiscoveryCode, before the discovery 2920 operation, may lead to a wrongful discovery, for example when two 2921 CO ports are connected to the same multi-channel RT port, while 2922 both CO ports have the same discovery register value. 2924 o Changing of target upstream/downstream data rate via 2925 gBondPortConfTargetUpDataRate/gBondPortConfTargetDnDataRate may 2926 lead to anything from link quality and rate degradation to a 2927 complete link initialization failure, as ability of a G.Bond port 2928 to support a particular configuration depends on the copper 2929 environment. 2931 o Activation of a specific line/channel may cause a severe 2932 degradation of service for another G.Bond port, whose channel(s) 2933 may be affected by the cross-talk from the newly activated 2934 channel. 2936 o Removal of a channel from an operationally 'up' G.Bond port, 2937 aggregating several channels, may cause port's rate degradation 2939 Some of the readable objects in this MIB module (i.e., those with 2940 MAX-ACCESS other than not-accessible) may be considered sensitive or 2941 vulnerable in some network environments since, collectively, they 2942 provide information about the performance of network interfaces and 2943 can reveal some aspects of their configuration. 2945 In particular, since a bonded xDSL port can be comprised of multiple 2946 Unshielded Twisted Pair (UTP) voice grade copper, located in the same 2947 bundle with other pairs belonging to another operator/customer, it is 2948 theoretically possible to eavesdrop to a G.Bond transmission, simply 2949 by "listening" to a cross-talk from the bonded pairs, especially if 2950 the operating parameters of the G.Bond link in question are known. 2952 It is thus important to control even GET and/or NOTIFY access to 2953 these objects and possibly even encrypt the values of these objects 2954 when sending them over the network via SNMP. These are the tables 2955 and objects and their sensitivity/vulnerability: 2957 o gBondPortStatTable - objects in this table provide status 2958 information for the G.Bond port, which may aid in identification 2959 of the pairs belonging to the bonded port and eavesdroping to the 2960 traffic over that port. 2962 SNMP versions prior to SNMPv3 did not include adequate security. 2963 Even if the network itself is secure (for example by using IPSec), 2964 there is no control as to who on the secure network is allowed to 2965 access and GET/SET (read/change/create/delete) the objects in this 2966 MIB module. 2968 Implementations MUST provide the security features described by the 2969 SNMPv3 framework (see [RFC3410]), including full support for 2970 authentication and privacy via the User-based Security Model (USM) 2971 [RFC3414] with the AES cipher algorithm [RFC3826]. Implementations 2972 MAY also provide support for the Transport Security Model (TSM) 2973 [RFC5591] in combination with a secure transport such as SSH 2974 [RFC5592] or TLS/DTLS [RFC6353]. 2976 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2977 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2978 enable cryptographic security. It is then a customer/operator 2979 responsibility to ensure that the SNMP entity giving access to an 2980 instance of this MIB module is properly configured to give access to 2981 the objects only to those principals (users) that have legitimate 2982 rights to indeed GET or SET (change/create/delete) them. 2984 8. IANA Considerations 2986 Three new values of IANAifType: g9981(263), g9982(264) and g9983(265) 2987 have been allocated by IANA [1] in the IANAifType-MIB module 2988 [IANAifType-MIB]. 2990 An object identifier for gBondMIB MODULE-IDENTITY SHALL be allocated 2991 by IANA in the MIB-2 transmission sub-tree, before this document is 2992 published. 2994 9. Acknowledgments 2996 This document was produced by the [ADSLMIB] working group. 2998 Special thanks to Dan Romascanu for his meticulous review of this 2999 text. 3001 10. References 3003 10.1. Normative References 3005 [RFC2119] Bradner, S., "Key words for use in 3006 RFCs to Indicate Requirement 3007 Levels", BCP 14, RFC 2119, 3008 March 1997. 3010 [RFC2578] McCloghrie, K., Ed., Perkins, D., 3011 Ed., and J. Schoenwaelder, Ed., 3012 "Structure of Management 3013 Information Version 2 (SMIv2)", 3014 STD 58, RFC 2578, April 1999. 3016 [RFC2579] McCloghrie, K., Ed., Perkins, D., 3017 Ed., and J. Schoenwaelder, Ed., 3018 "Textual Conventions for SMIv2", 3019 STD 58, RFC 2579, April 1999. 3021 [RFC2580] McCloghrie, K., Perkins, D., and 3022 J. Schoenwaelder, "Conformance 3023 Statements for SMIv2", STD 58, 3024 RFC 2580, April 1999. 3026 [RFC2863] McCloghrie, K. and F. Kastenholz, 3027 "The Interfaces Group MIB", 3028 RFC 2863, June 2000. 3030 [RFC3411] Harrington, D., Presuhn, R., and 3031 B. Wijnen, "An Architecture for 3032 Describing Simple Network 3033 Management Protocol (SNMP) 3034 Management Frameworks", STD 62, 3035 RFC 3411, December 2002. 3037 [RFC3705] Ray, B. and R. Abbi, "High 3038 Capacity Textual Conventions for 3039 MIB Modules Using Performance 3040 History Based on 15 Minute 3041 Intervals", RFC 3705, 3042 February 2004. 3044 [TR-159] Beili, E. and M. Morgenstern, 3045 "Management Framework for xDSL 3046 Bonding", Broadband Forum 3047 technical report TR-159, 3048 December 2008. 3050 10.2. Informative References 3052 [802.3] IEEE, "IEEE Standard for 3053 Information technology - 3054 Telecommunications and information 3055 exchange between systems - Local 3056 and metropolitan area networks - 3057 Specific requirements - Part 3: 3058 Carrier Sense Multiple Access with 3059 Collision Detection (CSMA/CD) 3060 Access Method and Physical Layer 3061 Specifications", IEEE Std 802.3- 3062 2005, December 2005. 3064 [ADSLMIB] IETF, "ADSL MIB (adslmib) 3065 Charter", . 3069 [G.991.2] ITU-T, "Single-pair High-speed 3070 Digital Subscriber Line (SHDSL) 3071 transceivers", ITU-T 3072 Recommendation G.991.2, 3073 December 2003, . 3076 [G.993.1] ITU-T, "Very High speed Digital 3077 Subscriber Line transceivers", 3078 ITU-T Recommendation G.993.1, 3079 June 2004, . 3082 [G.994.1] ITU-T, "Handshake procedures for 3083 digital subscriber line (DSL) 3084 transceivers", ITU-T 3085 Recommendation G.994.1, 3086 February 2007, . 3089 [G.998.1] ITU-T, "ATM-based multi-pair 3090 bonding", ITU-T 3091 Recommendation G.998.1, 3092 January 2005, . 3095 [G.998.2] ITU-T, "Ethernet-based multi-pair 3096 bonding", ITU-T 3097 Recommendation G.998.2, 3098 January 2005, . 3101 [G.998.3] ITU-T, "Multi-pair bonding using 3102 time-division inverse 3103 multiplexing", ITU-T 3104 Recommendation G.998.3, 3105 January 2005, . 3108 [I-D.ietf-adslmib-gbond-atm-mib] Beili, E., "ATM-based xDSL Bonded 3109 Interfaces MIB", draft-ietf- 3110 adslmib-gbond-atm-mib-05 (work in 3111 progress), Feb 2012. 3113 [I-D.ietf-adslmib-gbond-eth-mib] Beili, E. and M. Morgenstern, 3114 "Ethernet-based xDSL Bonded 3115 Interfaces MIB", draft-ietf- 3116 adslmib-gbond-eth-mib-05 (work in 3117 progress), February 2012. 3119 [I-D.ietf-adslmib-gbond-tdim-mib] Beili, E., "TDIM-based xDSL Bonded 3120 Interfaces MIB", draft-ietf- 3121 adslmib-gbond-tdim-mib-07 (work in 3122 progress), Feb 2012. 3124 [IANAifType-MIB] Internet Assigned Numbers 3125 Authority (IANA), "IANAifType 3126 Textual Convention definition", . 3130 [RFC2790] Waldbusser, S. and P. Grillo, 3131 "Host Resources MIB", RFC 2790, 3132 March 2000. 3134 [RFC2864] McCloghrie, K. and G. Hanson, "The 3135 Inverted Stack Table Extension to 3136 the Interfaces Group MIB", 3137 RFC 2864, June 2000. 3139 [RFC3410] Case, J., Mundy, R., Partain, D., 3140 and B. Stewart, "Introduction and 3141 Applicability Statements for 3142 Internet-Standard Management 3143 Framework", RFC 3410, 3144 December 2002. 3146 [RFC3414] Blumenthal, U. and B. Wijnen, 3147 "User-based Security Model (USM) 3148 for version 3 of the Simple 3149 Network Management Protocol 3150 (SNMPv3)", STD 62, RFC 3414, 3151 December 2002. 3153 [RFC3440] Ly, F. and G. Bathrick, 3154 "Definitions of Extension Managed 3155 Objects for Asymmetric Digital 3156 Subscriber Lines", RFC 3440, 3157 December 2002. 3159 [RFC3593] Tesink, K., "Textual Conventions 3160 for MIB Modules Using Performance 3161 History Based on 15 Minute 3162 Intervals", RFC 3593, 3163 September 2003. 3165 [RFC3728] Ray, B. and R. Abbi, "Definitions 3166 of Managed Objects for Very High 3167 Speed Digital Subscriber Lines 3168 (VDSL)", RFC 3728, February 2004. 3170 [RFC3826] Blumenthal, U., Maino, F., and K. 3171 McCloghrie, "The Advanced 3172 Encryption Standard (AES) Cipher 3173 Algorithm in the SNMP User-based 3174 Security Model", RFC 3826, 3175 June 2004. 3177 [RFC4181] Heard, C., "Guidelines for Authors 3178 and Reviewers of MIB Documents", 3179 BCP 111, RFC 4181, September 2005. 3181 [RFC4319] Sikes, C., Ray, B., and R. Abbi, 3182 "Definitions of Managed Objects 3183 for High Bit-Rate DSL - 2nd 3184 generation (HDSL2) and Single-Pair 3185 High-Speed Digital Subscriber Line 3186 (SHDSL) Lines", RFC 4319, 3187 December 2005. 3189 [RFC4706] Morgenstern, M., Dodge, M., 3190 Baillie, S., and U. Bonollo, 3191 "Definitions of Managed Objects 3192 for Asymmetric Digital Subscriber 3193 Line 2 (ADSL2)", RFC 4706, 3194 November 2006. 3196 [RFC5066] Beili, E., "Ethernet in the First 3197 Mile Copper (EFMCu) Interfaces 3198 MIB", RFC 5066, November 2007. 3200 [RFC5591] Harrington, D. and W. Hardaker, 3201 "Transport Security Model for the 3202 Simple Network Management Protocol 3203 (SNMP)", RFC 5591, June 2009. 3205 [RFC5592] Harrington, D., Salowey, J., and 3206 W. Hardaker, "Secure Shell 3207 Transport Model for the Simple 3208 Network Management Protocol 3209 (SNMP)", RFC 5592, June 2009. 3211 [RFC5650] Morgenstern, M., Baillie, S., and 3212 U. Bonollo, "Definitions of 3213 Managed Objects for Very High 3214 Speed Digital Subscriber Line 2 3215 (VDSL2)", RFC 5650, 3216 September 2009. 3218 [RFC6353] Hardaker, W., "Transport Layer 3219 Security (TLS) Transport Model for 3220 the Simple Network Management 3221 Protocol (SNMP)", RFC 6353, 3222 July 2011. 3224 [af-phy-0086] ATM Forum, "Inverse Multiplexing 3225 for ATM (IMA) Specification 3226 Version 1.1", ATM Forum 3227 specification af-pfy-0086.001, 3228 March 1999. 3230 URIs 3232 [1] 3234 Authors' Addresses 3236 Edward Beili 3237 Actelis Networks 3238 25 Bazel St. 3239 Petach-Tikva 49103 3240 Israel 3242 Phone: +972-3-924-3491 3243 EMail: edward.beili@actelis.com 3245 Moti Morgenstern 3246 ECI Telecom 3247 30 Hasivim St. 3248 Petach-Tikva 4951169 3249 Israel 3251 Phone: +972-3-926-6258 3252 EMail: moti.morgenstern@ecitele.com