idnits 2.17.1 draft-ietf-adslmib-gbond-atm-mib-03.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 use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (March 14, 2011) is 4792 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-06 -- Possible downref: Non-RFC (?) normative reference: ref. 'TR-159' Summary: 0 errors (**), 0 flaws (~~), 4 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 March 14, 2011 5 Expires: September 15, 2011 7 ATM-Based xDSL Bonded Interfaces MIB 8 draft-ietf-adslmib-gbond-atm-mib-03.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 September 15, 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", "MAY", and "OPTIONAL" in this 109 document are to be interpreted as described in RFC 2119 [RFC2119]. 111 3. The DSL Forum Management Framework for xDSL Bonding 113 This document makes use of the DSL Forum technical report Management 114 Framework for xDSL Bonding [TR-159], defining a management model and 115 a hierarchy of management objects for the bonded xDSL interfaces. 117 4. Relationship to other MIB modules 119 This section outlines the relationship of the MIB modules defined in 120 this document with other MIB modules described in the relevant RFCs. 121 Specifically, the following MIB modules are discussed: Interfaces 122 Group MIB (IF-MIB) and G.Bond MIB (GBOND-MIB). 124 4.1. Relationship to Interfaces Group MIB module 126 A G.Bond/ATM port is a private case of a Bonded multi-pair xDSL 127 interface and as such is managed using generic interface management 128 objects defined in the IF-MIB [RFC2863]. In particular an interface 129 index (ifIndex) is used to index instances of G.Bond/ATM ports, as 130 well as xDSL lines/channels, in a managed system. 132 4.2. Relationship to G.Bond MIB module 134 GBOND-MIB [I-D.ietf-adslmib-gbond-mib] module defines management 135 objects common for all Bonded multi-pair xDSL interfaces. In 136 particular it describes the bonding management, bonded port and 137 channel configuration, initialization sequence etc. 139 Both GBOND-MIB and GBOND-ATM-MIB modules are REQUIRED to manage a 140 G.Bond/ATM port. 142 4.3. Relationship to ATM MIB module 144 ATM-MIB [RFC2515] module defines management objects for an ATM 145 interface. 147 ATM-MIB module can be used to manage the ATM aspects of a G.Bond/ATM 148 port. 150 5. MIB Structure 152 5.1. Overview 154 All management objects defined in the GBOND-ATM-MIB module are 155 contained in a single group gBondAtmPort. This group is further 156 split into 4 sub-groups, structured as recommended by RFC 4181 157 [RFC4181]: 159 o gBondTdimPortNotifications - containing notifications (Up/ 160 Downstream Diff. Delay Tolerance Exceeded). 162 o gBondAtmPortConfTable - containing objects for configuration of a 163 G.Bond/ATM port. 165 o gBondAtmPortStatusTable - containing objects providing overall 166 status information of a G.Bond/ATM port, complementing the generic 167 status information from the ifTable of IF-MIB and gBondFltStatus 168 of GBOND-MIB. 170 o gBondAtmPM - containing objects providing historical performance 171 monitoring (PM) information of a G.Bond/ATM port, complementing 172 the PM information from the gBondPortPM of GBOND-MIB. 174 Note that the rest of the objects for the Generic Bonded Sub-layer 175 (GBS) port configuration, capabilities, status, notifications and 176 performance monitoring is located in the GBOND-MIB module. 178 5.2. Performance Monitoring 180 The OPTIONAL performance monitoring counters, thresholds and history 181 buckets (interval-counters) are implemented using the textual 182 conventions defined in the HC-PerfHist-TC-MIB [RFC3705]. The HC- 183 PerfHist-TC-MIB defines 64-bit versions of the textual conventions 184 found in PerfHist-TC-MIB [RFC3593]. 186 The agent SHOULD align the beginning of each interval to a fifteen 187 minute boundary of a wall clock. Likewise, the beginning of each one 188 day intervals SHOULD be aligned with the start of a day. 190 Counters are not reset when a GBS is reinitialized, but rather only 191 when the agent is reset or reinitialized (or under specific request 192 outside the scope of this MIB module). 194 5.3. Mapping of Broadband Forum TR-159 Managed Objects 196 This section contains the mapping between relevant managed objects 197 (attributes) defined in [TR-159] and the managed objects defined in 198 this document. 200 +-------------------------------+-----------------------------------+ 201 | TR-159 Managed Object | Corresponding SNMP Object | 202 +-------------------------------+-----------------------------------+ 203 | oBondATM - Basic Package | | 204 | (Mandatory) | | 205 +-------------------------------+-----------------------------------+ 206 | aIMARxLostCells | gBondAtmRxLostCells | 207 +-------------------------------+-----------------------------------+ 208 | aIMAPeerRxLostCells | gBondAtmTxLostCells | 209 +-------------------------------+-----------------------------------+ 210 | aIMAMaxUpDiffDelay | gBondAtmMaxUpDiffDelay | 211 +-------------------------------+-----------------------------------+ 212 | aIMAMaxDownDiffDelay | gBondAtmMaxDnDiffDelay | 213 +-------------------------------+-----------------------------------+ 214 | aIMAUpDiffDelayTolerance | gBondAtmUpDiffDelayTolerance | 215 +-------------------------------+-----------------------------------+ 216 | aIMADownDiffDelayTolerance | gBondAtmDnDiffDelayTolerance | 217 +-------------------------------+-----------------------------------+ 218 | aIMADiffDelayToleranceExceede | gBondAtmDiffDelayToleranceExceede | 219 | dEnable | dEnable | 220 +-------------------------------+-----------------------------------+ 221 | nIMAUpDiffDelayToleranceExcee | gBondAtmUpDiffDelayToleranceExcee | 222 | ded | ded | 223 +-------------------------------+-----------------------------------+ 224 | nIMADownDiffDelayToleranceExc | gBondAtmDnDiffDelayToleranceExcee | 225 | eeded | ded | 226 +-------------------------------+-----------------------------------+ 228 Table 1: Mapping of TR-159 Managed Objects 230 6. G.Bond/ATM MIB Definitions 232 GBOND-ATM-MIB DEFINITIONS ::= BEGIN 234 IMPORTS 235 MODULE-IDENTITY, 236 OBJECT-TYPE, 237 NOTIFICATION-TYPE, 238 mib-2, 239 Unsigned32, 240 Counter32 241 FROM SNMPv2-SMI -- [RFC2578] 242 TEXTUAL-CONVENTION, 243 TruthValue 244 FROM SNMPv2-TC -- [RFC2579] 245 MODULE-COMPLIANCE, 246 OBJECT-GROUP, 247 NOTIFICATION-GROUP 248 FROM SNMPv2-CONF -- [RFC2580] 249 ifIndex 250 FROM IF-MIB -- [RFC2863] 251 HCPerfCurrentCount, 252 HCPerfIntervalCount, 253 HCPerfValidIntervals, 254 HCPerfInvalidIntervals, 255 HCPerfTimeElapsed 256 FROM HC-PerfHist-TC-MIB -- [RFC3705] 257 ; 258 ------------------------------------------------------------------------ 259 gBondAtmMIB MODULE-IDENTITY 260 LAST-UPDATED "201103140000Z" -- Mar 14, 2011 261 ORGANIZATION "IETF ADSL MIB Working Group" 262 CONTACT-INFO 263 "WG charter: 264 http://www.ietf.org/html.charters/adslmib-charter.html 266 Mailing Lists: 267 General Discussion: adslmib@ietf.org 268 To Subscribe: adslmib-request@ietf.org 269 In Body: subscribe your_email_address 271 Chair: Menachem Dodge 272 Postal: ECI Telecom, Ltd. 273 30 Hasivim St., 274 Petach-Tikva 4951169 275 Israel 276 Phone: +972-3-926-8421 277 EMail: menachem.dodge@ecitele.com 279 Editor: Edward Beili 280 Postal: Actelis Networks, Inc. 281 25 Bazel St., P.O.B. 10173 282 Petach-Tikva 49103 283 Israel 284 Phone: +972-3-924-3491 285 EMail: edward.beili@actelis.com" 287 DESCRIPTION 288 "The objects in this MIB module are used to manage the 289 multi-pair bonded xDSL Interfaces using ATM inverse 290 multiplexing, defined in ITU-T recommendation G.998.1 291 (G.Bond/ATM). 293 This MIB module MUST be used in conjunction with GBOND-MIB 294 module, common to all G.Bond technologies. 296 The following references are used throughout this MIB module: 298 [G.998.1] refers to: 299 ITU-T Recommendation G.998.1: 'ATM-based multi-pair bonding', 300 January 2005. 302 [TR-159] refers to: 303 Broadband Forum Technical Report: 'Management Framework for 304 xDSL Bonding', December 2008. 306 Naming Conventions: 307 ATM - Asynchronous Transfer Mode 308 BCE - Bonding Channel Entity 309 BTU - Bonding Terminating Unit 310 CO - Central Office 311 CPE - Customer Premises Equipment 312 GBS - Generic Bonding Sublayer 313 GBS-C - Generic Bonded Sub-layer, CO side 314 GBS-R - Generic Bonded Sub-layer, RT (or CPE) side 315 PM - Performance Monitoring 316 RT - Remote Terminal 317 SNR - Signal to Noise Ratio 318 SES - Severely Errored Seconds 319 US - Unavailable Seconds 321 Copyright (C) The IETF Trust (2011). 322 This version of this MIB module is part of RFC YYYY; 323 see the RFC itself for full legal notices." 325 REVISION "201103140000Z" -- Mar 14, 2011 326 DESCRIPTION "Initial version, published as RFC YYYY." 328 -- EdNote: Replace YYYY with the actual RFC number & 329 -- remove this note 331 ::= { mib-2 ZZZ } 333 -- EdNote: Replace ZZZ with a real OID once it is 334 -- allocated & remove this note. 336 -- Sections of the module 337 -- Structured as recommended by [RFC4181], Appendix D 339 gBondAtmObjects OBJECT IDENTIFIER ::= { gBondAtmMIB 1 } 341 gBondAtmConformance OBJECT IDENTIFIER ::= { gBondAtmMIB 2 } 343 -- Groups in the module 344 gBondAtmPort OBJECT IDENTIFIER ::= { gBondAtmObjects 1 } 346 -- Textual Conventions 348 MilliSeconds ::= TEXTUAL-CONVENTION 349 DISPLAY-HINT "d" 350 STATUS current 351 DESCRIPTION 352 "Represents time unit value in milliseconds." 353 SYNTAX Unsigned32 355 -- Port Notifications Group 357 gBondAtmPortNotifications OBJECT IDENTIFIER 358 ::= { gBondAtmPort 0 } 360 gBondAtmUpDiffDelayToleranceExceeded NOTIFICATION-TYPE 361 OBJECTS { 362 -- ifIndex is not needed here since we are under specific GBS 363 gBondAtmUpDiffDelayTolerance, 364 gBondAtmMaxUpDiffDelay 365 } 366 STATUS current 367 DESCRIPTION 368 "This notification indicates that the maximum upstream 369 differential delay has exceeded the max upstream differential 370 delay threshold, specified by gBondAtmUpDiffDelayTolerance. 372 This notification MAY be sent for the GBS-C ports while the 373 port is up, on the crossing event in both directions: from 374 normal (diff. delay is above the threshold) to low (diff. 375 delay equals the threshold or below it) and from low to 376 normal. This notification is not applicable to the GBS-R 377 ports. 379 Generation of this notification is controlled by the 380 gBondAtmDiffDelayToleranceExceededEnable attribute. 382 This object maps to the TR-159 notification 383 nIMAUpDiffDelayToleranceExceeded." 384 REFERENCE 385 "[TR-159] 5.5.2.8" 386 ::= { gBondAtmPortNotifications 1 } 388 gBondAtmDnDiffDelayToleranceExceeded NOTIFICATION-TYPE 389 OBJECTS { 390 -- ifIndex is not needed here since we are under specific GBS 391 gBondAtmDnDiffDelayTolerance, 392 gBondAtmMaxDnDiffDelay 393 } 394 STATUS current 395 DESCRIPTION 396 "This notification indicates that the maximum downstream 397 differential delay has exceeded the max downstream 398 differential delay threshold, specified by 399 gBondAtmDnDiffDelayTolerance. 401 This notification MAY be sent for the GBS-C ports while the 402 port is up, on the crossing event in both directions: from 403 normal (diff. delay is above the threshold) to low (diff. 404 delay equals the threshold or below it) and from low to 405 normal. This notification is not applicable to the GBS-R 406 ports. 408 Generation of this notification is controlled by the 409 gBondAtmDiffDelayToleranceExceededEnable attribute. 411 This object maps to the TR-159 notification 412 nIMADownDiffDelayToleranceExceeded." 413 REFERENCE 414 "[TR-159] 5.5.2.9" 415 ::= { gBondAtmPortNotifications 2 } 417 -- G.Bond/ATM Port group 419 gBondAtmPortConfTable OBJECT-TYPE 420 SYNTAX SEQUENCE OF GBondAtmPortConfEntry 421 MAX-ACCESS not-accessible 422 STATUS current 423 DESCRIPTION 424 "Table for Configuration of G.Bond/ATM ports. Entries in 425 this table MUST be maintained in a persistent manner" 426 ::= { gBondAtmPort 1 } 428 gBondAtmPortConfEntry OBJECT-TYPE 429 SYNTAX GBondAtmPortConfEntry 430 MAX-ACCESS not-accessible 431 STATUS current 432 DESCRIPTION 433 "An entry in the G.Bond/ATM Port Configuration table. 434 Each entry represents a G.Bond/ATM port indexed by the 435 ifIndex. Additional configuration parameters are available 436 via the gBondPortConfEntry of GBOND-MIB. 437 Note that a G.Bond/ATM port runs on top of a single or 438 multiple BCE port(s), which are also indexed by ifIndex." 439 INDEX { ifIndex } 440 ::= { gBondAtmPortConfTable 1 } 442 GBondAtmPortConfEntry ::= 443 SEQUENCE { 444 gBondAtmUpDiffDelayTolerance MilliSeconds, 445 gBondAtmDnDiffDelayTolerance MilliSeconds, 446 gBondAtmDiffDelayToleranceExceededEnable TruthValue 447 } 449 gBondAtmUpDiffDelayTolerance OBJECT-TYPE 450 SYNTAX MilliSeconds(0..2047) 451 UNITS "milliseconds" 452 MAX-ACCESS read-write 453 STATUS current 454 DESCRIPTION 455 "A maximum tolerated upstream differential delay (among 456 the member BCEs) of a G.Bond/ATM port, expressed in ms. 458 This object is read-write for the GBS-C and irrelevant for 459 the GBS-R ports. 461 This object maps to TR-159 attribute 462 aIMAUpDiffDelayTolerance" 463 REFERENCE 464 "[TR-159] 5.5.2.5; [G.998.1] 11.4.1 (6)" 465 ::= { gBondAtmPortConfEntry 1 } 467 gBondAtmDnDiffDelayTolerance OBJECT-TYPE 468 SYNTAX MilliSeconds(0..2047) 469 UNITS "milliseconds" 470 MAX-ACCESS read-write 471 STATUS current 472 DESCRIPTION 473 "A maximum tolerated downstream differential delay (among 474 the member BCEs) of a G.Bond/ATM port, expressed in ms. 476 This object is read-write for the GBS-C and irrelevant for 477 the GBS-R ports. 479 This object maps to TR-159 attribute 480 aIMADownDiffDelayTolerance" 481 REFERENCE 482 "[TR-159] 5.5.2.6; [G.998.1] 11.4.1 (6)" 483 ::= { gBondAtmPortConfEntry 2 } 485 gBondAtmDiffDelayToleranceExceededEnable OBJECT-TYPE 486 SYNTAX TruthValue 487 MAX-ACCESS read-write 488 STATUS current 489 DESCRIPTION 490 "Indicates whether gBondAtmUpDiffDelayToleranceExceeded and 491 gBondAtmDnDiffDelayToleranceExceeded notifications should 492 be generated for G.Bond/ATM port. 494 Value of true(1) indicates that the notifications are enabled. 495 Value of false(2) indicates that the notifications are 496 disabled. 498 This object is read-write for the GBS-C and irrelevant for 499 the GBS-R ports. 500 This object MUST be maintained in a persistent manner. 502 This object maps to the TR-159 attribute 503 aIMADiffDelayToleranceExceededEnable." 504 REFERENCE 505 "[TR-159] 5.5.5.7" 506 ::= { gBondAtmPortConfEntry 3 } 508 gBondAtmPortStatusTable OBJECT-TYPE 509 SYNTAX SEQUENCE OF GBondAtmPortStatusEntry 510 MAX-ACCESS not-accessible 511 STATUS current 512 DESCRIPTION 513 "This table provides overall status information of G.Bond/ATM 514 ports, complementing the generic status information from the 515 ifTable of IF-MIB and gBondFltStatus of GBOND-MIB. 516 Additional status information about connected BCEs is available 517 from the relevant line MIBs. 519 This table contains live data from the equipment. As such, it is 520 NOT persistent." 521 ::= { gBondAtmPort 2 } 523 gBondAtmPortStatusEntry OBJECT-TYPE 524 SYNTAX GBondAtmPortStatusEntry 525 MAX-ACCESS not-accessible 526 STATUS current 527 DESCRIPTION 528 "An entry in the G.Bond/ATM port Status table. 529 Each entry represents a G.Bond/ATM port indexed by the 530 ifIndex. 531 Note that a GBS port runs on top of a single or multiple BCE 532 port(s), which are also indexed by ifIndex." 533 INDEX { ifIndex } 534 ::= { gBondAtmPortStatusTable 1 } 536 GBondAtmPortStatusEntry ::= 537 SEQUENCE { 538 gBondAtmRxLostCells Counter32, 539 gBondAtmTxLostCells Counter32, 540 gBondAtmMaxUpDiffDelay Unsigned32, 541 gBondAtmMaxDnDiffDelay Unsigned32 542 } 544 gBondAtmRxLostCells OBJECT-TYPE 545 SYNTAX Counter32 546 MAX-ACCESS read-only 547 STATUS current 548 DESCRIPTION 549 "The number of lost ATM cells detected by the G.Bond/ATM port 550 in the receive direction, i.e. upstream direction for 551 a GBS-C port. 553 Discontinuities in the value of this counter can occur at 554 re-initialization of the management system, and at other times 555 as indicated by the value of ifCounterDiscontinuityTime, 556 defined in IF-MIB. 558 This object maps to TR-159 attribute aIMARxLostCells." 559 REFERENCE 560 "[TR-159] 5.5.2.1; [G.998.1] 11.4.2 (4)" 561 ::= { gBondAtmPortStatusEntry 1 } 563 gBondAtmTxLostCells OBJECT-TYPE 564 SYNTAX Counter32 565 MAX-ACCESS read-only 566 STATUS current 567 DESCRIPTION 568 "The number of lost ATM cells detected by the peer G.Bond/ATM 569 port in the receive direction, e.g. downstream direction for a 570 GBS-C port. 572 This object is read only for the GBS-C ports and irrelevant 573 for the GBS-R ports. 575 Discontinuities in the value of this counter can occur at 576 re-initialization of the management system, and at other times 577 as indicated by the value of ifCounterDiscontinuityTime, 578 defined in IF-MIB. 580 This object maps to TR-159 attribute aIMAPeerRxLostCells." 581 REFERENCE 582 "[TR-159] 5.5.2.1; [G.998.1] 11.4.2 (4)" 583 ::= { gBondAtmPortStatusEntry 2 } 585 gBondAtmMaxUpDiffDelay OBJECT-TYPE 586 SYNTAX Unsigned32 587 UNITS "0.1 ms" 588 MAX-ACCESS read-only 589 STATUS current 590 DESCRIPTION 591 "Current maximum upstream differential delay between all 592 operational BCEs in the G.Bond/ATM bonding group, measured in 593 units of 0.1ms. 595 This object is read-only for the GBS-C and irrelevant for 596 the GBS-R ports. 598 This object maps to TR-159 attribute aIMAMaxUpDiffDelay." 599 REFERENCE 600 "[TR-159] 5.5.2.3" 601 ::= { gBondAtmPortStatusEntry 3 } 603 gBondAtmMaxDnDiffDelay OBJECT-TYPE 604 SYNTAX Unsigned32 605 UNITS "0.1 ms" 606 MAX-ACCESS read-only 607 STATUS current 608 DESCRIPTION 609 "Current maximum downstream differential delay between all 610 operational BCEs in the G.Bond/ATM bonding group, measured in 611 units of 0.1ms. 613 This object is read-only for the GBS-C and irrelevant for 614 the GBS-R ports. 616 This object maps to TR-159 attribute aIMAMaxDownDiffDelay." 617 REFERENCE 618 "[TR-159] 5.5.2.4" 619 ::= { gBondAtmPortStatusEntry 4 } 621 ------------------------------- 622 -- Performance Monitoring group 623 ------------------------------- 625 gBondAtmPM OBJECT IDENTIFIER ::= { gBondAtmPort 3 } 627 gBondAtmPortPerfCurrTable OBJECT-TYPE 628 SYNTAX SEQUENCE OF GBondAtmPortPerfCurrEntry 629 MAX-ACCESS not-accessible 630 STATUS current 631 DESCRIPTION 632 "This table contains current Performance Monitoring information 633 for a G.Bond/ATM port. This table contains live data from the 634 equipment and as such is NOT persistent." 635 ::= { gBondAtmPM 1 } 637 gBondAtmPortPerfCurrEntry OBJECT-TYPE 638 SYNTAX GBondAtmPortPerfCurrEntry 639 MAX-ACCESS not-accessible 640 STATUS current 641 DESCRIPTION 642 "An entry in the G.Bond/ATM Port PM table. 643 Each entry represents a G.Bond/ATM port indexed by the 644 ifIndex." 645 INDEX { ifIndex } 646 ::= { gBondAtmPortPerfCurrTable 1 } 648 GBondAtmPortPerfCurrEntry ::= 649 SEQUENCE { 650 gBondAtmPortPerf15MinValidIntervals HCPerfValidIntervals, 651 gBondAtmPortPerf15MinInvalidIntervals HCPerfInvalidIntervals, 652 gBondAtmPortPerfCurr15MinTimeElapsed HCPerfTimeElapsed, 653 gBondAtmPortPerfCurr15MinRxLostCells HCPerfCurrentCount, 654 gBondAtmPortPerfCurr15MinTxLostCells HCPerfCurrentCount, 655 gBondAtmPortPerfCurr15MinUpDiffDelay HCPerfCurrentCount, 656 gBondAtmPortPerfCurr15MinDnDiffDelay HCPerfCurrentCount, 657 gBondAtmPortPerf1DayValidIntervals Unsigned32, 658 gBondAtmPortPerf1DayInvalidIntervals Unsigned32, 659 gBondAtmPortPerfCurr1DayTimeElapsed HCPerfTimeElapsed, 660 gBondAtmPortPerfCurr1DayRxLostCells HCPerfCurrentCount, 661 gBondAtmPortPerfCurr1DayTxLostCells HCPerfCurrentCount, 662 gBondAtmPortPerfCurr1DayUpDiffDelay HCPerfCurrentCount, 663 gBondAtmPortPerfCurr1DayDnDiffDelay HCPerfCurrentCount 664 } 666 gBondAtmPortPerf15MinValidIntervals OBJECT-TYPE 667 SYNTAX HCPerfValidIntervals 668 MAX-ACCESS read-only 669 STATUS current 670 DESCRIPTION 671 "A read-only number of 15-minute intervals for which the 672 performance data was collected. The value of this object will 673 be 96 or the maximum number of 15-minute history intervals 674 collected by the implementation unless the measurement was 675 (re-)started recently, in which case the value will be the 676 number of complete 15 minutes intervals for which there are at 677 least some data. 678 In certain cases it is possible that some intervals are 679 unavailable. In this case, this object reports the maximum 680 interval number for which data is available. 682 This object partially maps to the TR-159 attribute 683 aGroupPerf15MinValidIntervals." 684 REFERENCE 685 "[TR-159] 5.5.1.32" 686 ::= { gBondAtmPortPerfCurrEntry 1 } 688 gBondAtmPortPerf15MinInvalidIntervals OBJECT-TYPE 689 SYNTAX HCPerfInvalidIntervals 690 MAX-ACCESS read-only 691 STATUS current 692 DESCRIPTION 693 "A read-only number of 15-minute intervals for which the 694 performance data was not always available. The value will 695 typically be zero except in cases where the data for some 696 intervals are not available. 698 This object partially maps to the TR-159 attribute 699 aGroupPerf15MinInvalidIntervals." 700 REFERENCE 701 "[TR-159] 5.5.1.33" 702 ::= { gBondAtmPortPerfCurrEntry 2 } 704 gBondAtmPortPerfCurr15MinTimeElapsed OBJECT-TYPE 705 SYNTAX HCPerfTimeElapsed 706 MAX-ACCESS read-only 707 STATUS current 708 DESCRIPTION 709 "A read-only count of seconds that have elapsed since the 710 beginning of the current 15-minute performance interval. 712 This object partially maps to the TR-159 attribute 713 aGroupPerfCurr15MinTimeElapsed." 714 REFERENCE 715 "[TR-159] 5.5.1.34" 716 ::= { gBondAtmPortPerfCurrEntry 3 } 718 gBondAtmPortPerfCurr15MinRxLostCells OBJECT-TYPE 719 SYNTAX HCPerfCurrentCount 720 MAX-ACCESS read-only 721 STATUS current 722 DESCRIPTION 723 "A read-only count of lost ATM cells detected by a G.Bond/ATM 724 port (e.g. GBS-C) in the receive direction, during the current 725 15-minute performance history interval. 727 Note that the total number of lost ATM cells is indicated by the 728 gBondAtmRxLostCells object. 730 This object is inhibited during Severely Errored Seconds (SES) 731 or Unavailable Seconds (UAS)." 732 REFERENCE 733 "[TR-159] 5.5.2.1" 734 ::= { gBondAtmPortPerfCurrEntry 4} 736 gBondAtmPortPerfCurr15MinTxLostCells OBJECT-TYPE 737 SYNTAX HCPerfCurrentCount 738 MAX-ACCESS read-only 739 STATUS current 740 DESCRIPTION 741 "A read-only count of lost ATM cells detected by the peer 742 G.Bond/ATM port (e.g. by GBS-R for GBS-C), during the current 743 15-minute performance history interval. 745 Note that the total number of lost ATM cells is indicated by the 746 gBondAtmTxLostCells object. 748 This object is inhibited during Unavailable Seconds (UAS)." 749 REFERENCE 750 "[TR-159] 5.5.2.2" 751 ::= { gBondAtmPortPerfCurrEntry 5} 753 gBondAtmPortPerfCurr15MinUpDiffDelay OBJECT-TYPE 754 SYNTAX HCPerfCurrentCount 755 MAX-ACCESS read-only 756 STATUS current 757 DESCRIPTION 758 "A read-only value specifying maximum upstream differential 759 delay between all operational BCEs in the GBS-C, measured in 760 units of 0.1ms, during the current 15-minute performance 761 interval. 763 Note that the current max upstream differential delay is 764 indicated by the gBondAtmMaxUpDiffDelay object. 766 This object is inhibited during Unavailable Seconds (UAS)." 767 REFERENCE 768 "[TR-159] 5.5.2.3" 769 ::= { gBondAtmPortPerfCurrEntry 6} 771 gBondAtmPortPerfCurr15MinDnDiffDelay OBJECT-TYPE 772 SYNTAX HCPerfCurrentCount 773 MAX-ACCESS read-only 774 STATUS current 775 DESCRIPTION 776 "A read-only value specifying maximum downstream differential 777 delay between all operational BCEs in the GBS-C (as perceived 778 by GBS-R), measured in units of 0.1ms, during the current 779 15-minute performance history interval. 781 Note that the current max downstream differential delay is 782 indicated by the gBondAtmMaxDnDiffDelay object. 784 This object is inhibited during Unavailable Seconds (UAS)." 785 REFERENCE 786 "[TR-159] 5.5.2.4" 787 ::= { gBondAtmPortPerfCurrEntry 7} 789 gBondAtmPortPerf1DayValidIntervals OBJECT-TYPE 790 SYNTAX Unsigned32 (0..7) 791 MAX-ACCESS read-only 792 STATUS current 793 DESCRIPTION 794 "A read-only number of 1-day intervals for which data was 795 collected. The value of this object will be 7 or the maximum 796 number of 1-day history intervals collected by the 797 implementation unless the measurement was (re-)started recently, 798 in which case the value will be the number of complete 1-day 799 intervals for which there are at least some data. 800 In certain cases it is possible that some intervals are 801 unavailable. In this case, this object reports the maximum 802 interval number for which data is available." 803 REFERENCE 804 "[TR-159] 5.5.1.45" 805 ::= { gBondAtmPortPerfCurrEntry 8 } 807 gBondAtmPortPerf1DayInvalidIntervals OBJECT-TYPE 808 SYNTAX Unsigned32 (0..7) 809 MAX-ACCESS read-only 810 STATUS current 811 DESCRIPTION 812 "A read-only number of 1-day intervals for which data was 813 not always available. The value will typically be zero except in 814 cases where the data for some intervals are not available." 815 REFERENCE 816 "[TR-159] 5.5.1.46" 817 ::= { gBondAtmPortPerfCurrEntry 9 } 819 gBondAtmPortPerfCurr1DayTimeElapsed OBJECT-TYPE 820 SYNTAX HCPerfTimeElapsed 821 MAX-ACCESS read-only 822 STATUS current 823 DESCRIPTION 824 "A read-only count of seconds that have elapsed since the 825 beginning of the current 1-day performance interval." 827 REFERENCE 828 "[TR-159] 5.5.1.47" 829 ::= { gBondAtmPortPerfCurrEntry 10 } 831 gBondAtmPortPerfCurr1DayRxLostCells OBJECT-TYPE 832 SYNTAX HCPerfCurrentCount 833 MAX-ACCESS read-only 834 STATUS current 835 DESCRIPTION 836 "A read-only count of lost ATM cells detected by the G.Bond/ATM 837 port (e.g. GBS-C), during the current 1-day performance 838 interval. 840 This object is inhibited during Severely Errored Seconds (SES) 841 and Unavailable Seconds (UAS)." 842 ::= { gBondAtmPortPerfCurrEntry 11 } 844 gBondAtmPortPerfCurr1DayTxLostCells OBJECT-TYPE 845 SYNTAX HCPerfCurrentCount 846 MAX-ACCESS read-only 847 STATUS current 848 DESCRIPTION 849 "A read-only count of lost ATM cells detected by the peer 850 G.Bond/ATM port (e.g. by GBS-R for GBS-C), during the current 851 1-day performance history interval. 853 This object is inhibited during Unavailable Seconds (UAS)." 854 ::= { gBondAtmPortPerfCurrEntry 12 } 856 gBondAtmPortPerfCurr1DayUpDiffDelay OBJECT-TYPE 857 SYNTAX HCPerfCurrentCount 858 MAX-ACCESS read-only 859 STATUS current 860 DESCRIPTION 861 "A read-only value specifying maximum upstream differential 862 delay between all operational BCEs in the GBS-C, measured in 863 units of 0.1ms, during the current 1-day performance 864 interval. 866 This object is inhibited during Unavailable Seconds (UAS)." 867 ::= { gBondAtmPortPerfCurrEntry 13 } 869 gBondAtmPortPerfCurr1DayDnDiffDelay OBJECT-TYPE 870 SYNTAX HCPerfCurrentCount 871 MAX-ACCESS read-only 872 STATUS current 873 DESCRIPTION 874 "A read-only value specifying maximum downstream differential 875 delay between all operational BCEs in the GBS-C, measured in 876 units of 0.1ms, during the current 1-day performance 877 interval. 879 This object is inhibited during Unavailable Seconds (UAS)." 880 ::= { gBondAtmPortPerfCurrEntry 14 } 882 -- Port PM history: 15-min buckets 884 gBondAtmPortPerf15MinTable OBJECT-TYPE 885 SYNTAX SEQUENCE OF GBondAtmPortPerf15MinEntry 886 MAX-ACCESS not-accessible 887 STATUS current 888 DESCRIPTION 889 "This table contains historical 15-minute buckets of Performance 890 Monitoring information for a G.Bond/ATM port (a row for each 891 15-minute interval, up to 96 intervals). 892 Entries in this table MUST be maintained in a persistent manner." 893 ::= { gBondAtmPM 2 } 895 gBondAtmPortPerf15MinEntry OBJECT-TYPE 896 SYNTAX GBondAtmPortPerf15MinEntry 897 MAX-ACCESS not-accessible 898 STATUS current 899 DESCRIPTION 900 "An entry in the G.Bond/ATM Port historical 15-minute PM table. 901 Each entry represents performance monitoring data for a 902 G.Bond/ATM port, indexed by ifIndex, collected during a 903 particular 15-minute interval, indexed by 904 gBondAtmPortPerf15MinIntervalIndex." 905 INDEX { ifIndex, gBondAtmPortPerf15MinIntervalIndex } 906 ::= { gBondAtmPortPerf15MinTable 1 } 908 GBondAtmPortPerf15MinEntry ::= 909 SEQUENCE { 910 gBondAtmPortPerf15MinIntervalIndex Unsigned32, 911 gBondAtmPortPerf15MinIntervalMoniTime HCPerfTimeElapsed, 912 gBondAtmPortPerf15MinIntervalRxLostCells HCPerfIntervalCount, 913 gBondAtmPortPerf15MinIntervalTxLostCells HCPerfIntervalCount, 914 gBondAtmPortPerf15MinIntervalUpDiffDelay HCPerfIntervalCount, 915 gBondAtmPortPerf15MinIntervalDnDiffDelay HCPerfIntervalCount, 916 gBondAtmPortPerf15MinIntervalValid TruthValue 917 } 919 gBondAtmPortPerf15MinIntervalIndex OBJECT-TYPE 920 SYNTAX Unsigned32 (1..96) 921 MAX-ACCESS not-accessible 922 STATUS current 923 DESCRIPTION 924 "Performance Data Interval number. 1 is the most recent previous 925 interval; interval 96 is 24 hours ago. 926 Intervals 2..96 are OPTIONAL. 928 This object partially maps to the TR-159 attribute 929 aGroupPerf15MinIntervalNumber." 930 REFERENCE 931 "[TR-159] 5.5.1.57" 932 ::= { gBondAtmPortPerf15MinEntry 1 } 934 gBondAtmPortPerf15MinIntervalMoniTime OBJECT-TYPE 935 SYNTAX HCPerfTimeElapsed 936 MAX-ACCESS read-only 937 STATUS current 938 DESCRIPTION 939 "A read-only count of seconds over which the performance data 940 was actually monitored. This value will be the same as the 941 interval duration (900 seconds), except in a situation where 942 performance data could not be collected for any reason." 943 ::= { gBondAtmPortPerf15MinEntry 2 } 945 gBondAtmPortPerf15MinIntervalRxLostCells OBJECT-TYPE 946 SYNTAX HCPerfIntervalCount 947 MAX-ACCESS read-only 948 STATUS current 949 DESCRIPTION 950 "A read-only count of lost ATM cells detected by a G.Bond/ATM 951 port (e.g. GBS-C) in the receive direction, during the 952 15-minute performance history interval. 954 Note that the total number of lost ATM cells is indicated by the 955 gBondAtmRxLostCells object. 957 This object is inhibited during Severely Errored Seconds (SES) 958 or Unavailable Seconds (UAS)." 959 REFERENCE 960 "[TR-159] 5.5.2.1" 961 ::= { gBondAtmPortPerf15MinEntry 3 } 963 gBondAtmPortPerf15MinIntervalTxLostCells OBJECT-TYPE 964 SYNTAX HCPerfIntervalCount 965 MAX-ACCESS read-only 966 STATUS current 967 DESCRIPTION 968 "A read-only count of lost ATM cells detected by the peer 969 G.Bond/ATM port (e.g. by GBS-R for GBS-C), during the 15-minute 970 performance history interval. 972 Note that the total number of lost ATM cells is indicated by the 973 gBondAtmTxLostCells object. 975 This object is inhibited during Unavailable Seconds (UAS)." 976 REFERENCE 977 "[TR-159] 5.5.2.2" 978 ::= { gBondAtmPortPerf15MinEntry 4 } 980 gBondAtmPortPerf15MinIntervalUpDiffDelay OBJECT-TYPE 981 SYNTAX HCPerfIntervalCount 982 MAX-ACCESS read-only 983 STATUS current 984 DESCRIPTION 985 "A read-only value specifying maximum upstream differential 986 delay between all operational BCEs in the GBS, measured in 987 units of 0.1ms, during the 15-minute performance history 988 interval. 990 Note that the current max upstream differential delay is 991 indicated by the gBondAtmMaxUpDiffDelay object. 993 This object is inhibited during Unavailable Seconds (UAS)." 994 REFERENCE 995 "[TR-159] 5.5.2.3" 996 ::= { gBondAtmPortPerf15MinEntry 5 } 998 gBondAtmPortPerf15MinIntervalDnDiffDelay OBJECT-TYPE 999 SYNTAX HCPerfIntervalCount 1000 MAX-ACCESS read-only 1001 STATUS current 1002 DESCRIPTION 1003 "A read-only value specifying maximum downstream differential 1004 delay between all operational BCEs in the GBS, as perceived by 1005 its peer port, measured in units of 0.1ms, during the 1006 15-minute performance history interval. 1008 Note that the current max upstream differential delay is 1009 indicated by the gBondAtmMaxDnDiffDelay object. 1011 This object is inhibited during Unavailable Seconds (UAS)." 1012 REFERENCE 1013 "[TR-159] 5.5.2.4" 1014 ::= { gBondAtmPortPerf15MinEntry 6 } 1016 gBondAtmPortPerf15MinIntervalValid OBJECT-TYPE 1017 SYNTAX TruthValue 1018 MAX-ACCESS read-only 1019 STATUS current 1020 DESCRIPTION 1021 "A read-only object indicating whether or not this history 1022 bucket contains valid data. Valid bucket is reported as true(1) 1023 and invalid bucket as false(2). 1024 If this history bucket is invalid the BTU MUST NOT produce 1025 notifications based upon the value of the counters in this 1026 bucket. 1027 Note that an implementation may decide not to store invalid 1028 history buckets in its data base. In such case this object is 1029 not required as only valid history buckets are available while 1030 invalid history buckets are simply not in the data base. 1032 This object partially maps to the TR-159 attribute 1033 aGroupPerf15MinIntervalValid." 1034 REFERENCE 1035 "[TR-159] 5.5.1.58" 1036 ::= { gBondAtmPortPerf15MinEntry 7 } 1038 -- Port PM history: 1-day buckets 1040 gBondAtmPortPerf1DayTable OBJECT-TYPE 1041 SYNTAX SEQUENCE OF GBondAtmPortPerf1DayEntry 1042 MAX-ACCESS not-accessible 1043 STATUS current 1044 DESCRIPTION 1045 "This table contains historical 1-day buckets of Performance 1046 Monitoring information for a G.Bond/ATM port (a row for each 1047 1-day interval, up to 7 intervals). 1048 Entries in this table MUST be maintained in a persistent manner." 1049 ::= { gBondAtmPM 3 } 1051 gBondAtmPortPerf1DayEntry OBJECT-TYPE 1052 SYNTAX GBondAtmPortPerf1DayEntry 1053 MAX-ACCESS not-accessible 1054 STATUS current 1055 DESCRIPTION 1056 "An entry in the G.Bond/ATM port historical 1-day PM table. 1057 Each entry represents performance monitoring data for such port, 1058 indexed by ifIndex, collected during a particular 1-day 1059 interval, indexed by gBondAtmPortPerf1DayIntervalIndex." 1060 INDEX { ifIndex, gBondAtmPortPerf1DayIntervalIndex } 1061 ::= { gBondAtmPortPerf1DayTable 1 } 1063 GBondAtmPortPerf1DayEntry ::= 1064 SEQUENCE { 1065 gBondAtmPortPerf1DayIntervalIndex Unsigned32, 1066 gBondAtmPortPerf1DayIntervalMoniTime HCPerfTimeElapsed, 1067 gBondAtmPortPerf1DayIntervalRxLostCells HCPerfIntervalCount, 1068 gBondAtmPortPerf1DayIntervalTxLostCells HCPerfIntervalCount, 1069 gBondAtmPortPerf1DayIntervalUpDiffDelay HCPerfIntervalCount, 1070 gBondAtmPortPerf1DayIntervalDnDiffDelay HCPerfIntervalCount, 1071 gBondAtmPortPerf1DayIntervalValid TruthValue 1072 } 1074 gBondAtmPortPerf1DayIntervalIndex OBJECT-TYPE 1075 SYNTAX Unsigned32 (1..7) 1076 MAX-ACCESS not-accessible 1077 STATUS current 1078 DESCRIPTION 1079 "Performance Data Interval number. 1 is the most recent previous 1080 interval; interval 7 is 24 hours ago. 1081 Intervals 2..7 are OPTIONAL. 1083 This object partially maps to the TR-159 attribute 1084 aGroupPerf1DayIntervalNumber." 1085 REFERENCE 1086 "[TR-159] 5.5.1.62" 1087 ::= { gBondAtmPortPerf1DayEntry 1 } 1089 gBondAtmPortPerf1DayIntervalMoniTime OBJECT-TYPE 1090 SYNTAX HCPerfTimeElapsed 1091 MAX-ACCESS read-only 1092 STATUS current 1093 DESCRIPTION 1094 "A read-only count of seconds over which the performance data 1095 was actually monitored. This value will be the same as the 1096 interval duration (86400 seconds), except in a situation where 1097 performance data could not be collected for any reason. 1099 This object partially maps to the TR-159 attribute 1100 aGroupPerf1DayIntervalMoniSecs." 1101 REFERENCE 1102 "[TR-159] 5.5.1.64" 1103 ::= { gBondAtmPortPerf1DayEntry 2 } 1105 gBondAtmPortPerf1DayIntervalRxLostCells OBJECT-TYPE 1106 SYNTAX HCPerfIntervalCount 1107 MAX-ACCESS read-only 1108 STATUS current 1109 DESCRIPTION 1110 "A read-only count of lost ATM cells detected by the G.Bond/ATM 1111 port (e.g. GBS-C), during the 1-day performance history interval. 1113 This object is inhibited during Severely Errored Seconds (SES) 1114 and Unavailable Seconds (UAS)." 1115 ::= { gBondAtmPortPerf1DayEntry 3 } 1117 gBondAtmPortPerf1DayIntervalTxLostCells OBJECT-TYPE 1118 SYNTAX HCPerfIntervalCount 1119 MAX-ACCESS read-only 1120 STATUS current 1121 DESCRIPTION 1122 "A read-only count of lost ATM cells detected by the peer 1123 G.Bond/ATM port (e.g. by GBS-R for GBS-C), during the 1-day 1124 performance history interval. 1126 This object is inhibited during Unavailable Seconds (UAS)." 1127 ::= { gBondAtmPortPerf1DayEntry 4 } 1129 gBondAtmPortPerf1DayIntervalUpDiffDelay OBJECT-TYPE 1130 SYNTAX HCPerfIntervalCount 1131 MAX-ACCESS read-only 1132 STATUS current 1133 DESCRIPTION 1134 "A read-only value specifying maximum upstream differential 1135 delay between all operational BCEs in the GBS-C, measured in 1136 units of 0.1ms, during the 1-day performance history interval. 1138 This object is inhibited during Unavailable Seconds (UAS)." 1139 ::= { gBondAtmPortPerf1DayEntry 5 } 1141 gBondAtmPortPerf1DayIntervalDnDiffDelay OBJECT-TYPE 1142 SYNTAX HCPerfIntervalCount 1143 MAX-ACCESS read-only 1144 STATUS current 1145 DESCRIPTION 1146 "A read-only value specifying maximum downstream differential 1147 delay between all operational BCEs in the GBS-C, measured in 1148 units of 0.1ms, during the 1-day performance history interval. 1150 This object is inhibited during Unavailable Seconds (UAS)." 1151 ::= { gBondAtmPortPerf1DayEntry 6 } 1153 gBondAtmPortPerf1DayIntervalValid OBJECT-TYPE 1154 SYNTAX TruthValue 1155 MAX-ACCESS read-only 1156 STATUS current 1157 DESCRIPTION 1158 "A read-only object indicating whether or not this history 1159 bucket contains valid data. Valid bucket is reported as true(1) 1160 and invalid bucket as false(2). 1161 If this history bucket is invalid the BTU MUST NOT produce 1162 notifications based upon the value of the counters in this 1163 bucket. 1164 Note that an implementation may decide not to store invalid 1165 history buckets in its data base. In such case this object is 1166 not required as only valid history buckets are available while 1167 invalid history buckets are simply not in the data base. 1169 This object partially maps to the TR-159 attribute 1170 aGroupPerf1DayIntervalValid." 1171 REFERENCE 1172 "[TR-159] 5.5.1.63" 1173 ::= { gBondAtmPortPerf1DayEntry 7 } 1175 -- 1176 -- Conformance Statements 1177 -- 1179 gBondAtmGroups OBJECT IDENTIFIER 1180 ::= { gBondAtmConformance 1 } 1182 gBondAtmCompliances OBJECT IDENTIFIER 1183 ::= { gBondAtmConformance 2 } 1185 -- Object Groups 1187 gBondAtmBasicGroup OBJECT-GROUP 1188 OBJECTS { 1189 gBondAtmRxLostCells, 1190 gBondAtmTxLostCells, 1191 gBondAtmMaxUpDiffDelay, 1192 gBondAtmMaxDnDiffDelay 1193 } 1194 STATUS current 1195 DESCRIPTION 1196 "A collection of objects representing management information 1197 for a G.Bond/ATM port." 1198 ::= { gBondAtmGroups 1 } 1200 gBondAtmAlarmConfGroup OBJECT-GROUP 1201 OBJECTS { 1202 gBondAtmUpDiffDelayTolerance, 1203 gBondAtmDnDiffDelayTolerance, 1204 gBondAtmDiffDelayToleranceExceededEnable 1205 } 1206 STATUS current 1207 DESCRIPTION 1208 "A collection of objects required for configuration of alarm 1209 thresholds and notifications in G.Bond/ATM ports." 1210 ::= { gBondAtmGroups 2 } 1212 gBondAtmNotificationGroup NOTIFICATION-GROUP 1213 NOTIFICATIONS { 1214 gBondAtmUpDiffDelayToleranceExceeded, 1215 gBondAtmDnDiffDelayToleranceExceeded 1216 } 1217 STATUS current 1218 DESCRIPTION 1219 "This group supports notifications of significant conditions 1220 associated with G.Bond/ATM ports." 1221 ::= { gBondAtmGroups 3 } 1223 gBondAtmPerfCurrGroup OBJECT-GROUP 1224 OBJECTS { 1225 gBondAtmPortPerf15MinValidIntervals, 1226 gBondAtmPortPerf15MinInvalidIntervals, 1227 gBondAtmPortPerfCurr15MinTimeElapsed, 1228 gBondAtmPortPerfCurr15MinRxLostCells, 1229 gBondAtmPortPerfCurr15MinTxLostCells, 1230 gBondAtmPortPerfCurr15MinUpDiffDelay, 1231 gBondAtmPortPerfCurr15MinDnDiffDelay, 1232 gBondAtmPortPerf1DayValidIntervals, 1233 gBondAtmPortPerf1DayInvalidIntervals, 1234 gBondAtmPortPerfCurr1DayTimeElapsed, 1235 gBondAtmPortPerfCurr1DayRxLostCells, 1236 gBondAtmPortPerfCurr1DayTxLostCells, 1237 gBondAtmPortPerfCurr1DayUpDiffDelay, 1238 gBondAtmPortPerfCurr1DayDnDiffDelay 1239 } 1240 STATUS current 1241 DESCRIPTION 1242 "A collection of objects supporting OPTIONAL current Performance 1243 Monitoring information for G.Bond/ATM ports." 1244 ::= { gBondAtmGroups 4 } 1246 gBondAtmPerf15MinGroup OBJECT-GROUP 1247 OBJECTS { 1248 gBondAtmPortPerf15MinIntervalMoniTime, 1249 gBondAtmPortPerf15MinIntervalRxLostCells, 1250 gBondAtmPortPerf15MinIntervalTxLostCells, 1251 gBondAtmPortPerf15MinIntervalUpDiffDelay, 1252 gBondAtmPortPerf15MinIntervalDnDiffDelay, 1253 gBondAtmPortPerf15MinIntervalValid 1254 } 1255 STATUS current 1256 DESCRIPTION 1257 "A collection of objects supporting OPTIONAL historical 1258 Performance Monitoring information for G.Bond/ATM ports, during 1259 previous 15-minute intervals ." 1260 ::= { gBondAtmGroups 5 } 1262 gBondAtmPerf1DayGroup OBJECT-GROUP 1263 OBJECTS { 1264 gBondAtmPortPerf1DayIntervalMoniTime, 1265 gBondAtmPortPerf1DayIntervalRxLostCells, 1266 gBondAtmPortPerf1DayIntervalTxLostCells, 1267 gBondAtmPortPerf1DayIntervalUpDiffDelay, 1268 gBondAtmPortPerf1DayIntervalDnDiffDelay, 1269 gBondAtmPortPerf1DayIntervalValid 1270 } 1271 STATUS current 1272 DESCRIPTION 1273 "A collection of objects supporting OPTIONAL historical 1274 Performance Monitoring information for G.Bond/ATM ports, during 1275 previous 1-day intervals ." 1276 ::= { gBondAtmGroups 6 } 1278 -- Compliance Statements 1280 gBondAtmCompliance MODULE-COMPLIANCE 1281 STATUS current 1282 DESCRIPTION 1283 "The compliance statement for G.Bond/ATM interfaces. 1284 Compliance with the following external compliance statements 1285 is REQUIRED: 1287 MIB Module Compliance Statement 1288 ---------- -------------------- 1289 IF-MIB ifCompliance3 1290 GBOND-MIB gBondCompliance" 1292 MODULE -- this module 1293 MANDATORY-GROUPS { 1294 gBondAtmBasicGroup, 1295 gBondAtmAlarmConfGroup, 1296 gBondAtmNotificationGroup 1297 } 1299 GROUP gBondAtmPerfCurrGroup 1300 DESCRIPTION 1301 "Support for this group is only required for implementations 1302 supporting Performance Monitoring." 1304 GROUP gBondAtmPerf15MinGroup 1305 DESCRIPTION 1306 "Support for this group is only required for implementations 1307 supporting historical Performance Monitoring." 1309 GROUP gBondAtmPerf1DayGroup 1310 DESCRIPTION 1311 "Support for this group is only required for implementations 1312 supporting 1-day historical Performance Monitoring." 1314 ::= { gBondAtmCompliances 1 } 1315 END 1317 7. Security Considerations 1319 There is a number of managed objects defined in the GBOND-ATM-MIB 1320 module that have a MAX-ACCESS clause of read-write. Writing to these 1321 objects can have potentially disruptive effects on network operation, 1322 for example: 1324 o Changing of gBondAtmPortConfTable configuration parameters MAY 1325 lead to a potential Service Level Agreement (SLA) breach, for 1326 example if a traffic delay is increased as a result of the higher 1327 delay tolerance (increased gBondAtmUpDiffDelayTolerance and/or 1328 gBondAtmDnDiffDelayTolerance), or the differential delay tolerance 1329 notifications are disabled by manipulating the 1330 gBondAtmDiffDelayToleranceExceededEnable parameter. 1332 The user of the GBOND-ATM-MIB module must therefore be aware that 1333 support for SET operations in a non-secure environment without proper 1334 protection can have a negative effect on network operations. 1336 The readable objects in the GBOND-ATM-MIB module (i.e., those with 1337 MAX-ACCESS other than not-accessible) may be considered sensitive in 1338 some environments since, collectively, they provide information about 1339 the performance of network interfaces and can reveal some aspects of 1340 their configuration. 1342 In such environments it is important to control also GET and NOTIFY 1343 access to these objects and possibly even to encrypt their values 1344 when sending them over the network via SNMP. 1346 SNMP versions prior to SNMPv3 did not include adequate security. 1347 Even if the network itself is secure (for example by using IPSec), 1348 even then, there is no control as to who on the secure network is 1349 allowed to access and GET/SET (read/change/create/delete) the objects 1350 in this MIB module. 1352 It is RECOMMENDED that implementers consider the security features as 1353 provided by the SNMPv3 framework (see [RFC3410], section 8), 1354 including full support for the SNMPv3 cryptographic mechanisms (for 1355 authentication and privacy). 1357 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1358 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1359 enable cryptographic security. It is then a customer/operator 1360 responsibility to ensure that the SNMP entity giving access to an 1361 instance of this MIB module is properly configured to give access to 1362 the objects only to those principals (users) that have legitimate 1363 rights to indeed GET or SET (change/create/delete) them. 1365 8. IANA Considerations 1367 An object identifier for gBondAtmMIB MODULE-IDENTITY SHALL be 1368 allocated by IANA [1] in the MIB-2 transmission sub-tree, before this 1369 document is published as an RFC. 1371 9. Acknowledgments 1373 This document was produced by the [ADSLMIB] working group. 1375 10. References 1377 10.1. Normative References 1379 [G.998.1] ITU-T, "ATM-based multi-pair bonding", 1380 ITU-T Recommendation G.998.3, 1381 January 2005. 1383 [I-D.ietf-adslmib-gbond-mib] Beili, E. and M. Morgenstern, "xDSL 1384 multi-pair bonding (G.Bond) MIB", 1385 draft-ietf-adslmib-gbond-mib-06 (work 1386 in progress), March 2011. 1388 [RFC2119] Bradner, S., "Key words for use in RFCs 1389 to Indicate Requirement Levels", 1390 BCP 14, RFC 2119, March 1997. 1392 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., 1393 and J. Schoenwaelder, Ed., "Structure 1394 of Management Information Version 2 1395 (SMIv2)", STD 58, RFC 2578, April 1999. 1397 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., 1398 and J. Schoenwaelder, Ed., "Textual 1399 Conventions for SMIv2", STD 58, 1400 RFC 2579, April 1999. 1402 [RFC2580] McCloghrie, K., Perkins, D., and J. 1403 Schoenwaelder, "Conformance Statements 1404 for SMIv2", STD 58, RFC 2580, 1405 April 1999. 1407 [RFC2863] McCloghrie, K. and F. Kastenholz, "The 1408 Interfaces Group MIB", RFC 2863, 1409 June 2000. 1411 [RFC3705] Ray, B. and R. Abbi, "High Capacity 1412 Textual Conventions for MIB Modules 1413 Using Performance History Based on 15 1414 Minute Intervals", RFC 3705, 1415 February 2004. 1417 [TR-159] Beili, E. and M. Morgenstern, 1418 "Management Framework for xDSL 1419 Bonding", Broadband Forum technical 1420 report TR-159, December 2008. 1422 10.2. Informative References 1424 [ADSLMIB] IETF, "ADSL MIB (adslmib) Charter", . 1428 [RFC2515] Tesink, K., "Definitions of Managed 1429 Objects for ATM Management", RFC 2515, 1430 February 1999. 1432 [RFC3410] Case, J., Mundy, R., Partain, D., and 1433 B. Stewart, "Introduction and 1434 Applicability Statements for Internet- 1435 Standard Management Framework", 1436 RFC 3410, December 2002. 1438 [RFC3593] Tesink, K., "Textual Conventions for 1439 MIB Modules Using Performance History 1440 Based on 15 Minute Intervals", 1441 RFC 3593, September 2003. 1443 [RFC4181] Heard, C., "Guidelines for Authors and 1444 Reviewers of MIB Documents", BCP 111, 1445 RFC 4181, September 2005. 1447 [af-phy-0086] ATM Forum, "Inverse Multiplexing for 1448 ATM (IMA) Specification Version 1.1", 1449 ATM Forum specification af-pfy- 1450 0086.001, March 1999. 1452 URIs 1454 [1] 1456 Author's Address 1458 Edward Beili 1459 Actelis Networks 1460 25 Bazel St. 1461 Petach-Tikva 49103 1462 Israel 1464 Phone: +972-3-924-3491 1465 EMail: edward.beili@actelis.com