idnits 2.17.1 draft-ietf-adslmib-gbond-atm-mib-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 28 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 (May 26, 2011) is 4719 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) -- Possible downref: Non-RFC (?) normative reference: ref. 'G.998.1' == Outdated reference: A later version (-11) exists of draft-ietf-adslmib-gbond-mib-07 -- Possible downref: Non-RFC (?) normative reference: ref. 'TR-159' Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 4 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 May 26, 2011 5 Expires: November 27, 2011 7 ATM-Based xDSL Bonded Interfaces MIB 8 draft-ietf-adslmib-gbond-atm-mib-04.txt 10 Abstract 12 This document defines Management Information Base (MIB) module for 13 use with network management protocols in TCP/IP based networks. This 14 document proposes an extension to the GBOND-MIB module with a set of 15 objects for managing ATM-based multi-pair bonded xDSL interfaces, 16 defined in ITU-T recommendation G.998.1. 18 Status of This Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at http://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on November 27, 2011. 35 Copyright Notice 37 Copyright (c) 2011 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (http://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 53 2. The Internet-Standard Management Framework . . . . . . . . . . 3 54 3. The DSL Forum Management Framework for xDSL Bonding . . . . . 3 55 4. Relationship to other MIB modules . . . . . . . . . . . . . . 4 56 4.1. Relationship to Interfaces Group MIB module . . . . . . . 4 57 4.2. Relationship to G.Bond MIB module . . . . . . . . . . . . 4 58 4.3. Relationship to ATM MIB module . . . . . . . . . . . . . . 4 59 5. MIB Structure . . . . . . . . . . . . . . . . . . . . . . . . 4 60 5.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . 4 61 5.2. Performance Monitoring . . . . . . . . . . . . . . . . . . 5 62 5.3. Mapping of Broadband Forum TR-159 Managed Objects . . . . 5 63 6. G.Bond/ATM MIB Definitions . . . . . . . . . . . . . . . . . . 6 64 7. Security Considerations . . . . . . . . . . . . . . . . . . . 29 65 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30 66 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 30 67 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 30 68 10.1. Normative References . . . . . . . . . . . . . . . . . . . 30 69 10.2. Informative References . . . . . . . . . . . . . . . . . . 31 71 1. Introduction 73 The ATM-Based Multi-Pair Bonding, a.k.a. G.Bond/ATM, is specified in 74 ITU-T G.998.1 recommendation [G.998.1], which defines a method for 75 bonding (or aggregating) of multiple xDSL lines (or individual bearer 76 channels in multiple xDSL lines) into a single bi-directional logical 77 link carrying an ATM stream. 79 This specification can be viewed as an evolution of the legacy 80 Inverse Multiplexing over ATM (IMA) technology [af-phy-0086], applied 81 to xDSL with variable rates on each line/bearer channel. As with the 82 other bonding schemes, ATM bonding also allows bonding of up to 32 83 individual sub-layers with variable rates, providing common 84 functionality for the configuration, initialization, operation and 85 monitoring of the bonded link. 87 The MIB module, defined in this document, defines a set of managed 88 objects for the management of G.998.1 bonded interfaces, extending 89 the common objects specified in the GBOND-MIB 90 [I-D.ietf-adslmib-gbond-mib] module. 92 2. The Internet-Standard Management Framework 94 For a detailed overview of the documents that describe the current 95 Internet-Standard Management Framework, please refer to section 7 of 96 RFC 3410 [RFC3410]. 98 Managed objects are accessed via a virtual information store, termed 99 the Management Information Base or MIB. MIB objects are generally 100 accessed through the Simple Network Management Protocol (SNMP). 101 Objects in the MIB are defined using the mechanisms defined in the 102 Structure of Management Information (SMI). This memo specifies a MIB 103 module that is compliant to the SMIv2, which is described in STD 58, 104 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 105 [RFC2580]. 107 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 108 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 109 "OPTIONAL" in this document are to be interpreted as described in RFC 110 2119 [RFC2119]. 112 3. The DSL Forum Management Framework for xDSL Bonding 114 This document makes use of the DSL Forum technical report Management 115 Framework for xDSL Bonding [TR-159], defining a management model and 116 a hierarchy of management objects for the bonded xDSL interfaces. 118 4. Relationship to other MIB modules 120 This section outlines the relationship of the MIB modules defined in 121 this document with other MIB modules described in the relevant RFCs. 122 Specifically, the following MIB modules are discussed: Interfaces 123 Group MIB (IF-MIB) and G.Bond MIB (GBOND-MIB). 125 4.1. Relationship to Interfaces Group MIB module 127 A G.Bond/ATM port is a private case of a Bonded multi-pair xDSL 128 interface and as such is managed using generic interface management 129 objects defined in the IF-MIB [RFC2863]. In particular an interface 130 index (ifIndex) is used to index instances of G.Bond/ATM ports, as 131 well as xDSL lines/channels, in a managed system. 133 4.2. Relationship to G.Bond MIB module 135 GBOND-MIB [I-D.ietf-adslmib-gbond-mib] module defines management 136 objects common for all Bonded multi-pair xDSL interfaces. In 137 particular it describes the bonding management, bonded port and 138 channel configuration, initialization sequence etc. 140 Both GBOND-MIB and GBOND-ATM-MIB modules are REQUIRED to manage a 141 G.Bond/ATM port. 143 4.3. Relationship to ATM MIB module 145 ATM-MIB [RFC2515] module defines management objects for an ATM 146 interface. 148 ATM-MIB module can be used to manage the ATM aspects of a G.Bond/ATM 149 port. 151 5. MIB Structure 153 5.1. Overview 155 All management objects defined in the GBOND-ATM-MIB module are 156 contained in a single group gBondAtmPort. This group is further 157 split into 4 sub-groups, structured as recommended by RFC 4181 158 [RFC4181]: 160 o gBondTdimPortNotifications - containing notifications (Up/ 161 Downstream Diff. Delay Tolerance Exceeded). 163 o gBondAtmPortConfTable - containing objects for configuration of a 164 G.Bond/ATM port. 166 o gBondAtmPortStatusTable - containing objects providing overall 167 status information of a G.Bond/ATM port, complementing the generic 168 status information from the ifTable of IF-MIB and gBondFltStatus 169 of GBOND-MIB. 171 o gBondAtmPM - containing objects providing historical performance 172 monitoring (PM) information of a G.Bond/ATM port, complementing 173 the PM information from the gBondPortPM of GBOND-MIB. 175 Note that the rest of the objects for the Generic Bonded Sub-layer 176 (GBS) port configuration, capabilities, status, notifications and 177 performance monitoring is located in the GBOND-MIB module. 179 5.2. Performance Monitoring 181 The OPTIONAL performance monitoring counters, thresholds and history 182 buckets (interval-counters) are implemented using the textual 183 conventions defined in the HC-PerfHist-TC-MIB [RFC3705]. The HC- 184 PerfHist-TC-MIB defines 64-bit versions of the textual conventions 185 found in PerfHist-TC-MIB [RFC3593]. 187 The agent SHOULD align the beginning of each interval to a fifteen 188 minute boundary of a wall clock. Likewise, the beginning of each one 189 day intervals SHOULD be aligned with the start of a day. 191 Counters are not reset when a GBS is reinitialized, but rather only 192 when the agent is reset or reinitialized (or under specific request 193 outside the scope of this MIB module). 195 5.3. Mapping of Broadband Forum TR-159 Managed Objects 197 This section contains the mapping between relevant managed objects 198 (attributes) defined in [TR-159] and the managed objects defined in 199 this document. 201 +-------------------------------+-----------------------------------+ 202 | TR-159 Managed Object | Corresponding SNMP Object | 203 +-------------------------------+-----------------------------------+ 204 | oBondATM - Basic Package | | 205 | (Mandatory) | | 206 +-------------------------------+-----------------------------------+ 207 | aIMARxLostCells | gBondAtmRxLostCells | 208 +-------------------------------+-----------------------------------+ 209 | aIMAPeerRxLostCells | gBondAtmTxLostCells | 210 +-------------------------------+-----------------------------------+ 211 | aIMAMaxUpDiffDelay | gBondAtmMaxUpDiffDelay | 212 +-------------------------------+-----------------------------------+ 213 | aIMAMaxDownDiffDelay | gBondAtmMaxDnDiffDelay | 214 +-------------------------------+-----------------------------------+ 215 | aIMAUpDiffDelayTolerance | gBondAtmUpDiffDelayTolerance | 216 +-------------------------------+-----------------------------------+ 217 | aIMADownDiffDelayTolerance | gBondAtmDnDiffDelayTolerance | 218 +-------------------------------+-----------------------------------+ 219 | aIMADiffDelayToleranceExceede | gBondAtmDiffDelayToleranceExceede | 220 | dEnable | dEnable | 221 +-------------------------------+-----------------------------------+ 222 | nIMAUpDiffDelayToleranceExcee | gBondAtmUpDiffDelayToleranceExcee | 223 | ded | ded | 224 +-------------------------------+-----------------------------------+ 225 | nIMADownDiffDelayToleranceExc | gBondAtmDnDiffDelayToleranceExcee | 226 | eeded | ded | 227 +-------------------------------+-----------------------------------+ 229 Table 1: Mapping of TR-159 Managed Objects 231 6. G.Bond/ATM MIB Definitions 233 GBOND-ATM-MIB DEFINITIONS ::= BEGIN 235 IMPORTS 236 MODULE-IDENTITY, 237 OBJECT-TYPE, 238 NOTIFICATION-TYPE, 239 mib-2, 240 Unsigned32, 241 Counter32 242 FROM SNMPv2-SMI -- [RFC2578] 243 TEXTUAL-CONVENTION, 244 TruthValue 245 FROM SNMPv2-TC -- [RFC2579] 246 MODULE-COMPLIANCE, 247 OBJECT-GROUP, 248 NOTIFICATION-GROUP 249 FROM SNMPv2-CONF -- [RFC2580] 250 ifIndex 251 FROM IF-MIB -- [RFC2863] 252 HCPerfCurrentCount, 253 HCPerfIntervalCount, 254 HCPerfValidIntervals, 255 HCPerfInvalidIntervals, 256 HCPerfTimeElapsed 257 FROM HC-PerfHist-TC-MIB -- [RFC3705] 258 ; 259 ------------------------------------------------------------------------ 260 gBondAtmMIB MODULE-IDENTITY 261 LAST-UPDATED "201105260000Z" -- May 26, 2011 262 ORGANIZATION "IETF ADSL MIB Working Group" 263 CONTACT-INFO 264 "WG charter: 265 http://www.ietf.org/html.charters/adslmib-charter.html 267 Mailing Lists: 268 General Discussion: adslmib@ietf.org 269 To Subscribe: adslmib-request@ietf.org 270 In Body: subscribe your_email_address 272 Chair: Menachem Dodge 273 Postal: ECI Telecom, Ltd. 274 30 Hasivim St., 275 Petach-Tikva 4951169 276 Israel 277 Phone: +972-3-926-8421 278 EMail: menachem.dodge@ecitele.com 280 Editor: Edward Beili 281 Postal: Actelis Networks, Inc. 282 25 Bazel St., P.O.B. 10173 283 Petach-Tikva 49103 284 Israel 285 Phone: +972-3-924-3491 286 EMail: edward.beili@actelis.com" 288 DESCRIPTION 289 "The objects in this MIB module are used to manage the 290 multi-pair bonded xDSL Interfaces using ATM inverse 291 multiplexing, defined in ITU-T recommendation G.998.1 292 (G.Bond/ATM). 294 This MIB module MUST be used in conjunction with GBOND-MIB 295 module, common to all G.Bond technologies. 297 The following references are used throughout this MIB module: 299 [G.998.1] refers to: 300 ITU-T Recommendation G.998.1: 'ATM-based multi-pair bonding', 301 January 2005. 303 [TR-159] refers to: 304 Broadband Forum Technical Report: 'Management Framework for 305 xDSL Bonding', December 2008. 307 Naming Conventions: 308 ATM - Asynchronous Transfer Mode 309 BCE - Bonding Channel Entity 310 BTU - Bonding Terminating Unit 311 CO - Central Office 312 CPE - Customer Premises Equipment 313 GBS - Generic Bonding Sublayer 314 GBS-C - Generic Bonded Sub-layer, CO side 315 GBS-R - Generic Bonded Sub-layer, RT (or CPE) side 316 PM - Performance Monitoring 317 RT - Remote Terminal 318 SNR - Signal to Noise Ratio 319 SES - Severely Errored Seconds 320 US - Unavailable Seconds 322 Copyright (C) The IETF Trust (2011). 323 This version of this MIB module is part of RFC YYYY; 324 see the RFC itself for full legal notices." 326 REVISION "201105260000Z" -- May 26, 2011 327 DESCRIPTION "Initial version, published as RFC YYYY." 329 -- EdNote: Replace YYYY with the actual RFC number & 330 -- remove this note 332 ::= { mib-2 ZZZ } 334 -- EdNote: Replace ZZZ with a real OID once it is 335 -- allocated & remove this note. 337 -- Sections of the module 338 -- Structured as recommended by [RFC4181], Appendix D 340 gBondAtmObjects OBJECT IDENTIFIER ::= { gBondAtmMIB 1 } 342 gBondAtmConformance OBJECT IDENTIFIER ::= { gBondAtmMIB 2 } 344 -- Groups in the module 345 gBondAtmPort OBJECT IDENTIFIER ::= { gBondAtmObjects 1 } 347 -- Textual Conventions 349 MilliSeconds ::= TEXTUAL-CONVENTION 350 DISPLAY-HINT "d" 351 STATUS current 352 DESCRIPTION 353 "Represents time unit value in milliseconds." 354 SYNTAX Unsigned32 356 -- Port Notifications Group 358 gBondAtmPortNotifications OBJECT IDENTIFIER 359 ::= { gBondAtmPort 0 } 361 gBondAtmUpDiffDelayToleranceExceeded NOTIFICATION-TYPE 362 OBJECTS { 363 -- ifIndex is not needed here since we are under specific GBS 364 gBondAtmUpDiffDelayTolerance, 365 gBondAtmMaxUpDiffDelay 366 } 367 STATUS current 368 DESCRIPTION 369 "This notification indicates that the maximum upstream 370 differential delay has exceeded the max upstream differential 371 delay threshold, specified by gBondAtmUpDiffDelayTolerance. 373 This notification MAY be sent for the GBS-C ports while the 374 port is up, on the crossing event in both directions: from 375 normal (diff. delay is above the threshold) to low (diff. 376 delay equals the threshold or below it) and from low to 377 normal. This notification is not applicable to the GBS-R 378 ports. 380 Generation of this notification is controlled by the 381 gBondAtmDiffDelayToleranceExceededEnable attribute. 383 This object maps to the TR-159 notification 384 nIMAUpDiffDelayToleranceExceeded." 385 REFERENCE 386 "[TR-159] 5.5.2.8" 387 ::= { gBondAtmPortNotifications 1 } 389 gBondAtmDnDiffDelayToleranceExceeded NOTIFICATION-TYPE 390 OBJECTS { 391 -- ifIndex is not needed here since we are under specific GBS 392 gBondAtmDnDiffDelayTolerance, 393 gBondAtmMaxDnDiffDelay 394 } 395 STATUS current 396 DESCRIPTION 397 "This notification indicates that the maximum downstream 398 differential delay has exceeded the max downstream 399 differential delay threshold, specified by 400 gBondAtmDnDiffDelayTolerance. 402 This notification MAY be sent for the GBS-C ports while the 403 port is up, on the crossing event in both directions: from 404 normal (diff. delay is above the threshold) to low (diff. 405 delay equals the threshold or below it) and from low to 406 normal. This notification is not applicable to the GBS-R 407 ports. 409 Generation of this notification is controlled by the 410 gBondAtmDiffDelayToleranceExceededEnable attribute. 412 This object maps to the TR-159 notification 413 nIMADownDiffDelayToleranceExceeded." 414 REFERENCE 415 "[TR-159] 5.5.2.9" 416 ::= { gBondAtmPortNotifications 2 } 418 -- G.Bond/ATM Port group 420 gBondAtmPortConfTable OBJECT-TYPE 421 SYNTAX SEQUENCE OF GBondAtmPortConfEntry 422 MAX-ACCESS not-accessible 423 STATUS current 424 DESCRIPTION 425 "Table for Configuration of G.Bond/ATM ports. Entries in 426 this table MUST be maintained in a persistent manner" 427 ::= { gBondAtmPort 1 } 429 gBondAtmPortConfEntry OBJECT-TYPE 430 SYNTAX GBondAtmPortConfEntry 431 MAX-ACCESS not-accessible 432 STATUS current 433 DESCRIPTION 434 "An entry in the G.Bond/ATM Port Configuration table. 435 Each entry represents a G.Bond/ATM port indexed by the 436 ifIndex. Additional configuration parameters are available 437 via the gBondPortConfEntry of GBOND-MIB. 438 Note that a G.Bond/ATM port runs on top of a single or 439 multiple BCE port(s), which are also indexed by ifIndex." 440 INDEX { ifIndex } 441 ::= { gBondAtmPortConfTable 1 } 443 GBondAtmPortConfEntry ::= 444 SEQUENCE { 445 gBondAtmUpDiffDelayTolerance MilliSeconds, 446 gBondAtmDnDiffDelayTolerance MilliSeconds, 447 gBondAtmDiffDelayToleranceExceededEnable TruthValue 448 } 450 gBondAtmUpDiffDelayTolerance OBJECT-TYPE 451 SYNTAX MilliSeconds(0..2047) 452 UNITS "milliseconds" 453 MAX-ACCESS read-write 454 STATUS current 455 DESCRIPTION 456 "A maximum tolerated upstream differential delay (among 457 the member BCEs) of a G.Bond/ATM port, expressed in ms. 459 This object is read-write for the GBS-C and irrelevant for 460 the GBS-R ports. 462 This object maps to TR-159 attribute 463 aIMAUpDiffDelayTolerance" 464 REFERENCE 465 "[TR-159] 5.5.2.5; [G.998.1] 11.4.1 (6)" 466 ::= { gBondAtmPortConfEntry 1 } 468 gBondAtmDnDiffDelayTolerance OBJECT-TYPE 469 SYNTAX MilliSeconds(0..2047) 470 UNITS "milliseconds" 471 MAX-ACCESS read-write 472 STATUS current 473 DESCRIPTION 474 "A maximum tolerated downstream differential delay (among 475 the member BCEs) of a G.Bond/ATM port, expressed in ms. 477 This object is read-write for the GBS-C and irrelevant for 478 the GBS-R ports. 480 This object maps to TR-159 attribute 481 aIMADownDiffDelayTolerance" 482 REFERENCE 483 "[TR-159] 5.5.2.6; [G.998.1] 11.4.1 (6)" 484 ::= { gBondAtmPortConfEntry 2 } 486 gBondAtmDiffDelayToleranceExceededEnable OBJECT-TYPE 487 SYNTAX TruthValue 488 MAX-ACCESS read-write 489 STATUS current 490 DESCRIPTION 491 "Indicates whether gBondAtmUpDiffDelayToleranceExceeded and 492 gBondAtmDnDiffDelayToleranceExceeded notifications should 493 be generated for G.Bond/ATM port. 495 Value of true(1) indicates that the notifications are enabled. 496 Value of false(2) indicates that the notifications are 497 disabled. 499 This object is read-write for the GBS-C and irrelevant for 500 the GBS-R ports. 501 This object MUST be maintained in a persistent manner. 503 This object maps to the TR-159 attribute 504 aIMADiffDelayToleranceExceededEnable." 505 REFERENCE 506 "[TR-159] 5.5.5.7" 507 ::= { gBondAtmPortConfEntry 3 } 509 gBondAtmPortStatusTable OBJECT-TYPE 510 SYNTAX SEQUENCE OF GBondAtmPortStatusEntry 511 MAX-ACCESS not-accessible 512 STATUS current 513 DESCRIPTION 514 "This table provides overall status information of G.Bond/ATM 515 ports, complementing the generic status information from the 516 ifTable of IF-MIB and gBondFltStatus of GBOND-MIB. 517 Additional status information about connected BCEs is available 518 from the relevant line MIBs. 520 This table contains live data from the equipment. As such, it is 521 NOT persistent." 522 ::= { gBondAtmPort 2 } 524 gBondAtmPortStatusEntry OBJECT-TYPE 525 SYNTAX GBondAtmPortStatusEntry 526 MAX-ACCESS not-accessible 527 STATUS current 528 DESCRIPTION 529 "An entry in the G.Bond/ATM port Status table. 530 Each entry represents a G.Bond/ATM port indexed by the 531 ifIndex. 532 Note that a GBS port runs on top of a single or multiple BCE 533 port(s), which are also indexed by ifIndex." 534 INDEX { ifIndex } 535 ::= { gBondAtmPortStatusTable 1 } 537 GBondAtmPortStatusEntry ::= 538 SEQUENCE { 539 gBondAtmRxLostCells Counter32, 540 gBondAtmTxLostCells Counter32, 541 gBondAtmMaxUpDiffDelay Unsigned32, 542 gBondAtmMaxDnDiffDelay Unsigned32 543 } 545 gBondAtmRxLostCells OBJECT-TYPE 546 SYNTAX Counter32 547 MAX-ACCESS read-only 548 STATUS current 549 DESCRIPTION 550 "The number of lost ATM cells detected by the G.Bond/ATM port 551 in the receive direction, i.e. upstream direction for 552 a GBS-C port. 554 Discontinuities in the value of this counter can occur at 555 re-initialization of the management system, and at other times 556 as indicated by the value of ifCounterDiscontinuityTime, 557 defined in IF-MIB. 559 This object maps to TR-159 attribute aIMARxLostCells." 560 REFERENCE 561 "[TR-159] 5.5.2.1; [G.998.1] 11.4.2 (4)" 562 ::= { gBondAtmPortStatusEntry 1 } 564 gBondAtmTxLostCells OBJECT-TYPE 565 SYNTAX Counter32 566 MAX-ACCESS read-only 567 STATUS current 568 DESCRIPTION 569 "The number of lost ATM cells detected by the peer G.Bond/ATM 570 port in the receive direction, e.g. downstream direction for a 571 GBS-C port. 573 This object is read only for the GBS-C ports and irrelevant 574 for the GBS-R ports. 576 Discontinuities in the value of this counter can occur at 577 re-initialization of the management system, and at other times 578 as indicated by the value of ifCounterDiscontinuityTime, 579 defined in IF-MIB. 581 This object maps to TR-159 attribute aIMAPeerRxLostCells." 582 REFERENCE 583 "[TR-159] 5.5.2.1; [G.998.1] 11.4.2 (4)" 584 ::= { gBondAtmPortStatusEntry 2 } 586 gBondAtmMaxUpDiffDelay OBJECT-TYPE 587 SYNTAX Unsigned32 588 UNITS "0.1 ms" 589 MAX-ACCESS read-only 590 STATUS current 591 DESCRIPTION 592 "Current maximum upstream differential delay between all 593 operational BCEs in the G.Bond/ATM bonding group, measured in 594 units of 0.1ms. 596 This object is read-only for the GBS-C and irrelevant for 597 the GBS-R ports. 599 This object maps to TR-159 attribute aIMAMaxUpDiffDelay." 600 REFERENCE 601 "[TR-159] 5.5.2.3" 602 ::= { gBondAtmPortStatusEntry 3 } 604 gBondAtmMaxDnDiffDelay OBJECT-TYPE 605 SYNTAX Unsigned32 606 UNITS "0.1 ms" 607 MAX-ACCESS read-only 608 STATUS current 609 DESCRIPTION 610 "Current maximum downstream differential delay between all 611 operational BCEs in the G.Bond/ATM bonding group, measured in 612 units of 0.1ms. 614 This object is read-only for the GBS-C and irrelevant for 615 the GBS-R ports. 617 This object maps to TR-159 attribute aIMAMaxDownDiffDelay." 618 REFERENCE 619 "[TR-159] 5.5.2.4" 620 ::= { gBondAtmPortStatusEntry 4 } 622 ------------------------------- 623 -- Performance Monitoring group 624 ------------------------------- 626 gBondAtmPM OBJECT IDENTIFIER ::= { gBondAtmPort 3 } 628 gBondAtmPortPerfCurrTable OBJECT-TYPE 629 SYNTAX SEQUENCE OF GBondAtmPortPerfCurrEntry 630 MAX-ACCESS not-accessible 631 STATUS current 632 DESCRIPTION 633 "This table contains current Performance Monitoring information 634 for a G.Bond/ATM port. This table contains live data from the 635 equipment and as such is NOT persistent." 636 ::= { gBondAtmPM 1 } 638 gBondAtmPortPerfCurrEntry OBJECT-TYPE 639 SYNTAX GBondAtmPortPerfCurrEntry 640 MAX-ACCESS not-accessible 641 STATUS current 642 DESCRIPTION 643 "An entry in the G.Bond/ATM Port PM table. 644 Each entry represents a G.Bond/ATM port indexed by the 645 ifIndex." 646 INDEX { ifIndex } 647 ::= { gBondAtmPortPerfCurrTable 1 } 649 GBondAtmPortPerfCurrEntry ::= 650 SEQUENCE { 651 gBondAtmPortPerf15MinValidIntervals HCPerfValidIntervals, 652 gBondAtmPortPerf15MinInvalidIntervals HCPerfInvalidIntervals, 653 gBondAtmPortPerfCurr15MinTimeElapsed HCPerfTimeElapsed, 654 gBondAtmPortPerfCurr15MinRxLostCells HCPerfCurrentCount, 655 gBondAtmPortPerfCurr15MinTxLostCells HCPerfCurrentCount, 656 gBondAtmPortPerfCurr15MinUpDiffDelay HCPerfCurrentCount, 657 gBondAtmPortPerfCurr15MinDnDiffDelay HCPerfCurrentCount, 658 gBondAtmPortPerf1DayValidIntervals Unsigned32, 659 gBondAtmPortPerf1DayInvalidIntervals Unsigned32, 660 gBondAtmPortPerfCurr1DayTimeElapsed HCPerfTimeElapsed, 661 gBondAtmPortPerfCurr1DayRxLostCells HCPerfCurrentCount, 662 gBondAtmPortPerfCurr1DayTxLostCells HCPerfCurrentCount, 663 gBondAtmPortPerfCurr1DayUpDiffDelay HCPerfCurrentCount, 664 gBondAtmPortPerfCurr1DayDnDiffDelay HCPerfCurrentCount 665 } 667 gBondAtmPortPerf15MinValidIntervals OBJECT-TYPE 668 SYNTAX HCPerfValidIntervals 669 MAX-ACCESS read-only 670 STATUS current 671 DESCRIPTION 672 "A read-only number of 15-minute intervals for which the 673 performance data was collected. The value of this object will 674 be 96 or the maximum number of 15-minute history intervals 675 collected by the implementation unless the measurement was 676 (re-)started recently, in which case the value will be the 677 number of complete 15 minutes intervals for which there are at 678 least some data. 679 In certain cases it is possible that some intervals are 680 unavailable. In this case, this object reports the maximum 681 interval number for which data is available. 683 This object partially maps to the TR-159 attribute 684 aGroupPerf15MinValidIntervals." 685 REFERENCE 686 "[TR-159] 5.5.1.32" 687 ::= { gBondAtmPortPerfCurrEntry 1 } 689 gBondAtmPortPerf15MinInvalidIntervals OBJECT-TYPE 690 SYNTAX HCPerfInvalidIntervals 691 MAX-ACCESS read-only 692 STATUS current 693 DESCRIPTION 694 "A read-only number of 15-minute intervals for which the 695 performance data was not always available. The value will 696 typically be zero except in cases where the data for some 697 intervals are not available. 699 This object partially maps to the TR-159 attribute 700 aGroupPerf15MinInvalidIntervals." 701 REFERENCE 702 "[TR-159] 5.5.1.33" 703 ::= { gBondAtmPortPerfCurrEntry 2 } 705 gBondAtmPortPerfCurr15MinTimeElapsed OBJECT-TYPE 706 SYNTAX HCPerfTimeElapsed 707 MAX-ACCESS read-only 708 STATUS current 709 DESCRIPTION 710 "A read-only count of seconds that have elapsed since the 711 beginning of the current 15-minute performance interval. 713 This object partially maps to the TR-159 attribute 714 aGroupPerfCurr15MinTimeElapsed." 715 REFERENCE 716 "[TR-159] 5.5.1.34" 717 ::= { gBondAtmPortPerfCurrEntry 3 } 719 gBondAtmPortPerfCurr15MinRxLostCells OBJECT-TYPE 720 SYNTAX HCPerfCurrentCount 721 MAX-ACCESS read-only 722 STATUS current 723 DESCRIPTION 724 "A read-only count of lost ATM cells detected by a G.Bond/ATM 725 port (e.g. GBS-C) in the receive direction, during the current 726 15-minute performance history interval. 728 Note that the total number of lost ATM cells is indicated by the 729 gBondAtmRxLostCells object. 731 This object is inhibited during Severely Errored Seconds (SES) 732 or Unavailable Seconds (UAS)." 733 REFERENCE 734 "[TR-159] 5.5.2.1" 735 ::= { gBondAtmPortPerfCurrEntry 4} 737 gBondAtmPortPerfCurr15MinTxLostCells OBJECT-TYPE 738 SYNTAX HCPerfCurrentCount 739 MAX-ACCESS read-only 740 STATUS current 741 DESCRIPTION 742 "A read-only count of lost ATM cells detected by the peer 743 G.Bond/ATM port (e.g. by GBS-R for GBS-C), during the current 744 15-minute performance history interval. 746 Note that the total number of lost ATM cells is indicated by the 747 gBondAtmTxLostCells object. 749 This object is inhibited during Unavailable Seconds (UAS)." 750 REFERENCE 751 "[TR-159] 5.5.2.2" 752 ::= { gBondAtmPortPerfCurrEntry 5} 754 gBondAtmPortPerfCurr15MinUpDiffDelay OBJECT-TYPE 755 SYNTAX HCPerfCurrentCount 756 MAX-ACCESS read-only 757 STATUS current 758 DESCRIPTION 759 "A read-only value specifying maximum upstream differential 760 delay between all operational BCEs in the GBS-C, measured in 761 units of 0.1ms, during the current 15-minute performance 762 interval. 764 Note that the current max upstream differential delay is 765 indicated by the gBondAtmMaxUpDiffDelay object. 767 This object is inhibited during Unavailable Seconds (UAS)." 768 REFERENCE 769 "[TR-159] 5.5.2.3" 770 ::= { gBondAtmPortPerfCurrEntry 6} 772 gBondAtmPortPerfCurr15MinDnDiffDelay OBJECT-TYPE 773 SYNTAX HCPerfCurrentCount 774 MAX-ACCESS read-only 775 STATUS current 776 DESCRIPTION 777 "A read-only value specifying maximum downstream differential 778 delay between all operational BCEs in the GBS-C (as perceived 779 by GBS-R), measured in units of 0.1ms, during the current 780 15-minute performance history interval. 782 Note that the current max downstream differential delay is 783 indicated by the gBondAtmMaxDnDiffDelay object. 785 This object is inhibited during Unavailable Seconds (UAS)." 786 REFERENCE 787 "[TR-159] 5.5.2.4" 788 ::= { gBondAtmPortPerfCurrEntry 7} 790 gBondAtmPortPerf1DayValidIntervals OBJECT-TYPE 791 SYNTAX Unsigned32 (0..7) 792 MAX-ACCESS read-only 793 STATUS current 794 DESCRIPTION 795 "A read-only number of 1-day intervals for which data was 796 collected. The value of this object will be 7 or the maximum 797 number of 1-day history intervals collected by the 798 implementation unless the measurement was (re-)started recently, 799 in which case the value will be the number of complete 1-day 800 intervals for which there are at least some data. 801 In certain cases it is possible that some intervals are 802 unavailable. In this case, this object reports the maximum 803 interval number for which data is available." 804 REFERENCE 805 "[TR-159] 5.5.1.45" 806 ::= { gBondAtmPortPerfCurrEntry 8 } 808 gBondAtmPortPerf1DayInvalidIntervals OBJECT-TYPE 809 SYNTAX Unsigned32 (0..7) 810 MAX-ACCESS read-only 811 STATUS current 812 DESCRIPTION 813 "A read-only number of 1-day intervals for which data was 814 not always available. The value will typically be zero except in 815 cases where the data for some intervals are not available." 816 REFERENCE 817 "[TR-159] 5.5.1.46" 818 ::= { gBondAtmPortPerfCurrEntry 9 } 820 gBondAtmPortPerfCurr1DayTimeElapsed OBJECT-TYPE 821 SYNTAX HCPerfTimeElapsed 822 MAX-ACCESS read-only 823 STATUS current 824 DESCRIPTION 825 "A read-only count of seconds that have elapsed since the 826 beginning of the current 1-day performance interval." 828 REFERENCE 829 "[TR-159] 5.5.1.47" 830 ::= { gBondAtmPortPerfCurrEntry 10 } 832 gBondAtmPortPerfCurr1DayRxLostCells OBJECT-TYPE 833 SYNTAX HCPerfCurrentCount 834 MAX-ACCESS read-only 835 STATUS current 836 DESCRIPTION 837 "A read-only count of lost ATM cells detected by the G.Bond/ATM 838 port (e.g. GBS-C), during the current 1-day performance 839 interval. 841 This object is inhibited during Severely Errored Seconds (SES) 842 and Unavailable Seconds (UAS)." 843 ::= { gBondAtmPortPerfCurrEntry 11 } 845 gBondAtmPortPerfCurr1DayTxLostCells OBJECT-TYPE 846 SYNTAX HCPerfCurrentCount 847 MAX-ACCESS read-only 848 STATUS current 849 DESCRIPTION 850 "A read-only count of lost ATM cells detected by the peer 851 G.Bond/ATM port (e.g. by GBS-R for GBS-C), during the current 852 1-day performance history interval. 854 This object is inhibited during Unavailable Seconds (UAS)." 855 ::= { gBondAtmPortPerfCurrEntry 12 } 857 gBondAtmPortPerfCurr1DayUpDiffDelay OBJECT-TYPE 858 SYNTAX HCPerfCurrentCount 859 MAX-ACCESS read-only 860 STATUS current 861 DESCRIPTION 862 "A read-only value specifying maximum upstream differential 863 delay between all operational BCEs in the GBS-C, measured in 864 units of 0.1ms, during the current 1-day performance 865 interval. 867 This object is inhibited during Unavailable Seconds (UAS)." 868 ::= { gBondAtmPortPerfCurrEntry 13 } 870 gBondAtmPortPerfCurr1DayDnDiffDelay OBJECT-TYPE 871 SYNTAX HCPerfCurrentCount 872 MAX-ACCESS read-only 873 STATUS current 874 DESCRIPTION 875 "A read-only value specifying maximum downstream differential 876 delay between all operational BCEs in the GBS-C, measured in 877 units of 0.1ms, during the current 1-day performance 878 interval. 880 This object is inhibited during Unavailable Seconds (UAS)." 881 ::= { gBondAtmPortPerfCurrEntry 14 } 883 -- Port PM history: 15-min buckets 885 gBondAtmPortPerf15MinTable OBJECT-TYPE 886 SYNTAX SEQUENCE OF GBondAtmPortPerf15MinEntry 887 MAX-ACCESS not-accessible 888 STATUS current 889 DESCRIPTION 890 "This table contains historical 15-minute buckets of Performance 891 Monitoring information for a G.Bond/ATM port (a row for each 892 15-minute interval, up to 96 intervals). 893 Entries in this table MUST be maintained in a persistent manner." 894 ::= { gBondAtmPM 2 } 896 gBondAtmPortPerf15MinEntry OBJECT-TYPE 897 SYNTAX GBondAtmPortPerf15MinEntry 898 MAX-ACCESS not-accessible 899 STATUS current 900 DESCRIPTION 901 "An entry in the G.Bond/ATM Port historical 15-minute PM table. 902 Each entry represents performance monitoring data for a 903 G.Bond/ATM port, indexed by ifIndex, collected during a 904 particular 15-minute interval, indexed by 905 gBondAtmPortPerf15MinIntervalIndex." 906 INDEX { ifIndex, gBondAtmPortPerf15MinIntervalIndex } 907 ::= { gBondAtmPortPerf15MinTable 1 } 909 GBondAtmPortPerf15MinEntry ::= 910 SEQUENCE { 911 gBondAtmPortPerf15MinIntervalIndex Unsigned32, 912 gBondAtmPortPerf15MinIntervalMoniTime HCPerfTimeElapsed, 913 gBondAtmPortPerf15MinIntervalRxLostCells HCPerfIntervalCount, 914 gBondAtmPortPerf15MinIntervalTxLostCells HCPerfIntervalCount, 915 gBondAtmPortPerf15MinIntervalUpDiffDelay HCPerfIntervalCount, 916 gBondAtmPortPerf15MinIntervalDnDiffDelay HCPerfIntervalCount, 917 gBondAtmPortPerf15MinIntervalValid TruthValue 918 } 920 gBondAtmPortPerf15MinIntervalIndex OBJECT-TYPE 921 SYNTAX Unsigned32 (1..96) 922 MAX-ACCESS not-accessible 923 STATUS current 924 DESCRIPTION 925 "Performance Data Interval number. 1 is the most recent previous 926 interval; interval 96 is 24 hours ago. 927 Intervals 2..96 are OPTIONAL. 929 This object partially maps to the TR-159 attribute 930 aGroupPerf15MinIntervalNumber." 931 REFERENCE 932 "[TR-159] 5.5.1.57" 933 ::= { gBondAtmPortPerf15MinEntry 1 } 935 gBondAtmPortPerf15MinIntervalMoniTime OBJECT-TYPE 936 SYNTAX HCPerfTimeElapsed 937 MAX-ACCESS read-only 938 STATUS current 939 DESCRIPTION 940 "A read-only count of seconds over which the performance data 941 was actually monitored. This value will be the same as the 942 interval duration (900 seconds), except in a situation where 943 performance data could not be collected for any reason." 944 ::= { gBondAtmPortPerf15MinEntry 2 } 946 gBondAtmPortPerf15MinIntervalRxLostCells OBJECT-TYPE 947 SYNTAX HCPerfIntervalCount 948 MAX-ACCESS read-only 949 STATUS current 950 DESCRIPTION 951 "A read-only count of lost ATM cells detected by a G.Bond/ATM 952 port (e.g. GBS-C) in the receive direction, during the 953 15-minute performance history interval. 955 Note that the total number of lost ATM cells is indicated by the 956 gBondAtmRxLostCells object. 958 This object is inhibited during Severely Errored Seconds (SES) 959 or Unavailable Seconds (UAS)." 960 REFERENCE 961 "[TR-159] 5.5.2.1" 962 ::= { gBondAtmPortPerf15MinEntry 3 } 964 gBondAtmPortPerf15MinIntervalTxLostCells OBJECT-TYPE 965 SYNTAX HCPerfIntervalCount 966 MAX-ACCESS read-only 967 STATUS current 968 DESCRIPTION 969 "A read-only count of lost ATM cells detected by the peer 970 G.Bond/ATM port (e.g. by GBS-R for GBS-C), during the 15-minute 971 performance history interval. 973 Note that the total number of lost ATM cells is indicated by the 974 gBondAtmTxLostCells object. 976 This object is inhibited during Unavailable Seconds (UAS)." 977 REFERENCE 978 "[TR-159] 5.5.2.2" 979 ::= { gBondAtmPortPerf15MinEntry 4 } 981 gBondAtmPortPerf15MinIntervalUpDiffDelay OBJECT-TYPE 982 SYNTAX HCPerfIntervalCount 983 MAX-ACCESS read-only 984 STATUS current 985 DESCRIPTION 986 "A read-only value specifying maximum upstream differential 987 delay between all operational BCEs in the GBS, measured in 988 units of 0.1ms, during the 15-minute performance history 989 interval. 991 Note that the current max upstream differential delay is 992 indicated by the gBondAtmMaxUpDiffDelay object. 994 This object is inhibited during Unavailable Seconds (UAS)." 995 REFERENCE 996 "[TR-159] 5.5.2.3" 997 ::= { gBondAtmPortPerf15MinEntry 5 } 999 gBondAtmPortPerf15MinIntervalDnDiffDelay OBJECT-TYPE 1000 SYNTAX HCPerfIntervalCount 1001 MAX-ACCESS read-only 1002 STATUS current 1003 DESCRIPTION 1004 "A read-only value specifying maximum downstream differential 1005 delay between all operational BCEs in the GBS, as perceived by 1006 its peer port, measured in units of 0.1ms, during the 1007 15-minute performance history interval. 1009 Note that the current max upstream differential delay is 1010 indicated by the gBondAtmMaxDnDiffDelay object. 1012 This object is inhibited during Unavailable Seconds (UAS)." 1013 REFERENCE 1014 "[TR-159] 5.5.2.4" 1015 ::= { gBondAtmPortPerf15MinEntry 6 } 1017 gBondAtmPortPerf15MinIntervalValid OBJECT-TYPE 1018 SYNTAX TruthValue 1019 MAX-ACCESS read-only 1020 STATUS current 1021 DESCRIPTION 1022 "A read-only object indicating whether or not this history 1023 bucket contains valid data. Valid bucket is reported as true(1) 1024 and invalid bucket as false(2). 1025 If this history bucket is invalid the BTU MUST NOT produce 1026 notifications based upon the value of the counters in this 1027 bucket. 1028 Note that an implementation may decide not to store invalid 1029 history buckets in its data base. In such case this object is 1030 not required as only valid history buckets are available while 1031 invalid history buckets are simply not in the data base. 1033 This object partially maps to the TR-159 attribute 1034 aGroupPerf15MinIntervalValid." 1035 REFERENCE 1036 "[TR-159] 5.5.1.58" 1037 ::= { gBondAtmPortPerf15MinEntry 7 } 1039 -- Port PM history: 1-day buckets 1041 gBondAtmPortPerf1DayTable OBJECT-TYPE 1042 SYNTAX SEQUENCE OF GBondAtmPortPerf1DayEntry 1043 MAX-ACCESS not-accessible 1044 STATUS current 1045 DESCRIPTION 1046 "This table contains historical 1-day buckets of Performance 1047 Monitoring information for a G.Bond/ATM port (a row for each 1048 1-day interval, up to 7 intervals). 1049 Entries in this table MUST be maintained in a persistent manner." 1050 ::= { gBondAtmPM 3 } 1052 gBondAtmPortPerf1DayEntry OBJECT-TYPE 1053 SYNTAX GBondAtmPortPerf1DayEntry 1054 MAX-ACCESS not-accessible 1055 STATUS current 1056 DESCRIPTION 1057 "An entry in the G.Bond/ATM port historical 1-day PM table. 1058 Each entry represents performance monitoring data for such port, 1059 indexed by ifIndex, collected during a particular 1-day 1060 interval, indexed by gBondAtmPortPerf1DayIntervalIndex." 1061 INDEX { ifIndex, gBondAtmPortPerf1DayIntervalIndex } 1062 ::= { gBondAtmPortPerf1DayTable 1 } 1064 GBondAtmPortPerf1DayEntry ::= 1065 SEQUENCE { 1066 gBondAtmPortPerf1DayIntervalIndex Unsigned32, 1067 gBondAtmPortPerf1DayIntervalMoniTime HCPerfTimeElapsed, 1068 gBondAtmPortPerf1DayIntervalRxLostCells HCPerfIntervalCount, 1069 gBondAtmPortPerf1DayIntervalTxLostCells HCPerfIntervalCount, 1070 gBondAtmPortPerf1DayIntervalUpDiffDelay HCPerfIntervalCount, 1071 gBondAtmPortPerf1DayIntervalDnDiffDelay HCPerfIntervalCount, 1072 gBondAtmPortPerf1DayIntervalValid TruthValue 1073 } 1075 gBondAtmPortPerf1DayIntervalIndex OBJECT-TYPE 1076 SYNTAX Unsigned32 (1..7) 1077 MAX-ACCESS not-accessible 1078 STATUS current 1079 DESCRIPTION 1080 "Performance Data Interval number. 1 is the most recent previous 1081 interval; interval 7 is 24 hours ago. 1082 Intervals 2..7 are OPTIONAL. 1084 This object partially maps to the TR-159 attribute 1085 aGroupPerf1DayIntervalNumber." 1086 REFERENCE 1087 "[TR-159] 5.5.1.62" 1088 ::= { gBondAtmPortPerf1DayEntry 1 } 1090 gBondAtmPortPerf1DayIntervalMoniTime OBJECT-TYPE 1091 SYNTAX HCPerfTimeElapsed 1092 MAX-ACCESS read-only 1093 STATUS current 1094 DESCRIPTION 1095 "A read-only count of seconds over which the performance data 1096 was actually monitored. This value will be the same as the 1097 interval duration (86400 seconds), except in a situation where 1098 performance data could not be collected for any reason. 1100 This object partially maps to the TR-159 attribute 1101 aGroupPerf1DayIntervalMoniSecs." 1102 REFERENCE 1103 "[TR-159] 5.5.1.64" 1104 ::= { gBondAtmPortPerf1DayEntry 2 } 1106 gBondAtmPortPerf1DayIntervalRxLostCells OBJECT-TYPE 1107 SYNTAX HCPerfIntervalCount 1108 MAX-ACCESS read-only 1109 STATUS current 1110 DESCRIPTION 1111 "A read-only count of lost ATM cells detected by the G.Bond/ATM 1112 port (e.g. GBS-C), during the 1-day performance history interval. 1114 This object is inhibited during Severely Errored Seconds (SES) 1115 and Unavailable Seconds (UAS)." 1116 ::= { gBondAtmPortPerf1DayEntry 3 } 1118 gBondAtmPortPerf1DayIntervalTxLostCells OBJECT-TYPE 1119 SYNTAX HCPerfIntervalCount 1120 MAX-ACCESS read-only 1121 STATUS current 1122 DESCRIPTION 1123 "A read-only count of lost ATM cells detected by the peer 1124 G.Bond/ATM port (e.g. by GBS-R for GBS-C), during the 1-day 1125 performance history interval. 1127 This object is inhibited during Unavailable Seconds (UAS)." 1128 ::= { gBondAtmPortPerf1DayEntry 4 } 1130 gBondAtmPortPerf1DayIntervalUpDiffDelay OBJECT-TYPE 1131 SYNTAX HCPerfIntervalCount 1132 MAX-ACCESS read-only 1133 STATUS current 1134 DESCRIPTION 1135 "A read-only value specifying maximum upstream differential 1136 delay between all operational BCEs in the GBS-C, measured in 1137 units of 0.1ms, during the 1-day performance history interval. 1139 This object is inhibited during Unavailable Seconds (UAS)." 1140 ::= { gBondAtmPortPerf1DayEntry 5 } 1142 gBondAtmPortPerf1DayIntervalDnDiffDelay OBJECT-TYPE 1143 SYNTAX HCPerfIntervalCount 1144 MAX-ACCESS read-only 1145 STATUS current 1146 DESCRIPTION 1147 "A read-only value specifying maximum downstream differential 1148 delay between all operational BCEs in the GBS-C, measured in 1149 units of 0.1ms, during the 1-day performance history interval. 1151 This object is inhibited during Unavailable Seconds (UAS)." 1152 ::= { gBondAtmPortPerf1DayEntry 6 } 1154 gBondAtmPortPerf1DayIntervalValid OBJECT-TYPE 1155 SYNTAX TruthValue 1156 MAX-ACCESS read-only 1157 STATUS current 1158 DESCRIPTION 1159 "A read-only object indicating whether or not this history 1160 bucket contains valid data. Valid bucket is reported as true(1) 1161 and invalid bucket as false(2). 1162 If this history bucket is invalid the BTU MUST NOT produce 1163 notifications based upon the value of the counters in this 1164 bucket. 1165 Note that an implementation may decide not to store invalid 1166 history buckets in its data base. In such case this object is 1167 not required as only valid history buckets are available while 1168 invalid history buckets are simply not in the data base. 1170 This object partially maps to the TR-159 attribute 1171 aGroupPerf1DayIntervalValid." 1172 REFERENCE 1173 "[TR-159] 5.5.1.63" 1174 ::= { gBondAtmPortPerf1DayEntry 7 } 1176 -- 1177 -- Conformance Statements 1178 -- 1180 gBondAtmGroups OBJECT IDENTIFIER 1181 ::= { gBondAtmConformance 1 } 1183 gBondAtmCompliances OBJECT IDENTIFIER 1184 ::= { gBondAtmConformance 2 } 1186 -- Object Groups 1188 gBondAtmBasicGroup OBJECT-GROUP 1189 OBJECTS { 1190 gBondAtmRxLostCells, 1191 gBondAtmTxLostCells, 1192 gBondAtmMaxUpDiffDelay, 1193 gBondAtmMaxDnDiffDelay 1194 } 1195 STATUS current 1196 DESCRIPTION 1197 "A collection of objects representing management information 1198 for a G.Bond/ATM port." 1199 ::= { gBondAtmGroups 1 } 1201 gBondAtmAlarmConfGroup OBJECT-GROUP 1202 OBJECTS { 1203 gBondAtmUpDiffDelayTolerance, 1204 gBondAtmDnDiffDelayTolerance, 1205 gBondAtmDiffDelayToleranceExceededEnable 1206 } 1207 STATUS current 1208 DESCRIPTION 1209 "A collection of objects required for configuration of alarm 1210 thresholds and notifications in G.Bond/ATM ports." 1211 ::= { gBondAtmGroups 2 } 1213 gBondAtmNotificationGroup NOTIFICATION-GROUP 1214 NOTIFICATIONS { 1215 gBondAtmUpDiffDelayToleranceExceeded, 1216 gBondAtmDnDiffDelayToleranceExceeded 1217 } 1218 STATUS current 1219 DESCRIPTION 1220 "This group supports notifications of significant conditions 1221 associated with G.Bond/ATM ports." 1222 ::= { gBondAtmGroups 3 } 1224 gBondAtmPerfCurrGroup OBJECT-GROUP 1225 OBJECTS { 1226 gBondAtmPortPerf15MinValidIntervals, 1227 gBondAtmPortPerf15MinInvalidIntervals, 1228 gBondAtmPortPerfCurr15MinTimeElapsed, 1229 gBondAtmPortPerfCurr15MinRxLostCells, 1230 gBondAtmPortPerfCurr15MinTxLostCells, 1231 gBondAtmPortPerfCurr15MinUpDiffDelay, 1232 gBondAtmPortPerfCurr15MinDnDiffDelay, 1233 gBondAtmPortPerf1DayValidIntervals, 1234 gBondAtmPortPerf1DayInvalidIntervals, 1235 gBondAtmPortPerfCurr1DayTimeElapsed, 1236 gBondAtmPortPerfCurr1DayRxLostCells, 1237 gBondAtmPortPerfCurr1DayTxLostCells, 1238 gBondAtmPortPerfCurr1DayUpDiffDelay, 1239 gBondAtmPortPerfCurr1DayDnDiffDelay 1240 } 1241 STATUS current 1242 DESCRIPTION 1243 "A collection of objects supporting OPTIONAL current Performance 1244 Monitoring information for G.Bond/ATM ports." 1245 ::= { gBondAtmGroups 4 } 1247 gBondAtmPerf15MinGroup OBJECT-GROUP 1248 OBJECTS { 1249 gBondAtmPortPerf15MinIntervalMoniTime, 1250 gBondAtmPortPerf15MinIntervalRxLostCells, 1251 gBondAtmPortPerf15MinIntervalTxLostCells, 1252 gBondAtmPortPerf15MinIntervalUpDiffDelay, 1253 gBondAtmPortPerf15MinIntervalDnDiffDelay, 1254 gBondAtmPortPerf15MinIntervalValid 1255 } 1256 STATUS current 1257 DESCRIPTION 1258 "A collection of objects supporting OPTIONAL historical 1259 Performance Monitoring information for G.Bond/ATM ports, during 1260 previous 15-minute intervals ." 1261 ::= { gBondAtmGroups 5 } 1263 gBondAtmPerf1DayGroup OBJECT-GROUP 1264 OBJECTS { 1265 gBondAtmPortPerf1DayIntervalMoniTime, 1266 gBondAtmPortPerf1DayIntervalRxLostCells, 1267 gBondAtmPortPerf1DayIntervalTxLostCells, 1268 gBondAtmPortPerf1DayIntervalUpDiffDelay, 1269 gBondAtmPortPerf1DayIntervalDnDiffDelay, 1270 gBondAtmPortPerf1DayIntervalValid 1271 } 1272 STATUS current 1273 DESCRIPTION 1274 "A collection of objects supporting OPTIONAL historical 1275 Performance Monitoring information for G.Bond/ATM ports, during 1276 previous 1-day intervals ." 1277 ::= { gBondAtmGroups 6 } 1279 -- Compliance Statements 1281 gBondAtmCompliance MODULE-COMPLIANCE 1282 STATUS current 1283 DESCRIPTION 1284 "The compliance statement for G.Bond/ATM interfaces. 1285 Compliance with the following external compliance statements 1286 is REQUIRED: 1288 MIB Module Compliance Statement 1289 ---------- -------------------- 1290 IF-MIB ifCompliance3 1291 GBOND-MIB gBondCompliance" 1293 MODULE -- this module 1294 MANDATORY-GROUPS { 1295 gBondAtmBasicGroup, 1296 gBondAtmAlarmConfGroup, 1297 gBondAtmNotificationGroup 1298 } 1300 GROUP gBondAtmPerfCurrGroup 1301 DESCRIPTION 1302 "Support for this group is only required for implementations 1303 supporting Performance Monitoring." 1305 GROUP gBondAtmPerf15MinGroup 1306 DESCRIPTION 1307 "Support for this group is only required for implementations 1308 supporting historical Performance Monitoring." 1310 GROUP gBondAtmPerf1DayGroup 1311 DESCRIPTION 1312 "Support for this group is only required for implementations 1313 supporting 1-day historical Performance Monitoring." 1315 ::= { gBondAtmCompliances 1 } 1316 END 1318 7. Security Considerations 1320 There is a number of managed objects defined in the GBOND-ATM-MIB 1321 module that have a MAX-ACCESS clause of read-write. Writing to these 1322 objects can have potentially disruptive effects on network operation, 1323 for example: 1325 o Changing of gBondAtmPortConfTable configuration parameters MAY 1326 lead to a potential Service Level Agreement (SLA) breach, for 1327 example if a traffic delay is increased as a result of the higher 1328 delay tolerance (increased gBondAtmUpDiffDelayTolerance and/or 1329 gBondAtmDnDiffDelayTolerance), or the differential delay tolerance 1330 notifications are disabled by manipulating the 1331 gBondAtmDiffDelayToleranceExceededEnable parameter. 1333 The user of the GBOND-ATM-MIB module must therefore be aware that 1334 support for SET operations in a non-secure environment without proper 1335 protection can have a negative effect on network operations. 1337 The readable objects in the GBOND-ATM-MIB module (i.e., those with 1338 MAX-ACCESS other than not-accessible) may be considered sensitive in 1339 some environments since, collectively, they provide information about 1340 the performance of network interfaces and can reveal some aspects of 1341 their configuration. 1343 In such environments it is important to control also GET and NOTIFY 1344 access to these objects and possibly even to encrypt their values 1345 when sending them over the network via SNMP. 1347 SNMP versions prior to SNMPv3 did not include adequate security. 1348 Even if the network itself is secure (for example by using IPSec), 1349 even then, there is no control as to who on the secure network is 1350 allowed to access and GET/SET (read/change/create/delete) the objects 1351 in this MIB module. 1353 It is RECOMMENDED that implementers consider the security features as 1354 provided by the SNMPv3 framework (see [RFC3410], section 8), 1355 including full support for the SNMPv3 cryptographic mechanisms (for 1356 authentication and privacy). 1358 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1359 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1360 enable cryptographic security. It is then a customer/operator 1361 responsibility to ensure that the SNMP entity giving access to an 1362 instance of this MIB module is properly configured to give access to 1363 the objects only to those principals (users) that have legitimate 1364 rights to indeed GET or SET (change/create/delete) them. 1366 8. IANA Considerations 1368 An object identifier for gBondAtmMIB MODULE-IDENTITY SHALL be 1369 allocated by IANA [1] in the MIB-2 transmission sub-tree, before this 1370 document is published as an RFC. 1372 9. Acknowledgments 1374 This document was produced by the [ADSLMIB] working group. 1376 10. References 1378 10.1. Normative References 1380 [G.998.1] ITU-T, "ATM-based multi-pair bonding", 1381 ITU-T Recommendation G.998.3, 1382 January 2005. 1384 [I-D.ietf-adslmib-gbond-mib] Beili, E. and M. Morgenstern, "xDSL 1385 multi-pair bonding (G.Bond) MIB", 1386 draft-ietf-adslmib-gbond-mib-07 (work 1387 in progress), May 2011. 1389 [RFC2119] Bradner, S., "Key words for use in RFCs 1390 to Indicate Requirement Levels", 1391 BCP 14, RFC 2119, March 1997. 1393 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., 1394 and J. Schoenwaelder, Ed., "Structure 1395 of Management Information Version 2 1396 (SMIv2)", STD 58, RFC 2578, April 1999. 1398 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., 1399 and J. Schoenwaelder, Ed., "Textual 1400 Conventions for SMIv2", STD 58, 1401 RFC 2579, April 1999. 1403 [RFC2580] McCloghrie, K., Perkins, D., and J. 1404 Schoenwaelder, "Conformance Statements 1405 for SMIv2", STD 58, RFC 2580, 1406 April 1999. 1408 [RFC2863] McCloghrie, K. and F. Kastenholz, "The 1409 Interfaces Group MIB", RFC 2863, 1410 June 2000. 1412 [RFC3705] Ray, B. and R. Abbi, "High Capacity 1413 Textual Conventions for MIB Modules 1414 Using Performance History Based on 15 1415 Minute Intervals", RFC 3705, 1416 February 2004. 1418 [TR-159] Beili, E. and M. Morgenstern, 1419 "Management Framework for xDSL 1420 Bonding", Broadband Forum technical 1421 report TR-159, December 2008. 1423 10.2. Informative References 1425 [ADSLMIB] IETF, "ADSL MIB (adslmib) Charter", . 1429 [RFC2515] Tesink, K., "Definitions of Managed 1430 Objects for ATM Management", RFC 2515, 1431 February 1999. 1433 [RFC3410] Case, J., Mundy, R., Partain, D., and 1434 B. Stewart, "Introduction and 1435 Applicability Statements for Internet- 1436 Standard Management Framework", 1437 RFC 3410, December 2002. 1439 [RFC3593] Tesink, K., "Textual Conventions for 1440 MIB Modules Using Performance History 1441 Based on 15 Minute Intervals", 1442 RFC 3593, September 2003. 1444 [RFC4181] Heard, C., "Guidelines for Authors and 1445 Reviewers of MIB Documents", BCP 111, 1446 RFC 4181, September 2005. 1448 [af-phy-0086] ATM Forum, "Inverse Multiplexing for 1449 ATM (IMA) Specification Version 1.1", 1450 ATM Forum specification af-pfy- 1451 0086.001, March 1999. 1453 URIs 1455 [1] 1457 Author's Address 1459 Edward Beili 1460 Actelis Networks 1461 25 Bazel St. 1462 Petach-Tikva 49103 1463 Israel 1465 Phone: +972-3-924-3491 1466 EMail: edward.beili@actelis.com