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