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