idnits 2.17.1 draft-ietf-adslmib-gbond-atm-mib-01.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 (May 27, 2010) is 5076 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) == Missing Reference: 'T-159' is mentioned on line 485, but not defined -- Possible downref: Non-RFC (?) normative reference: ref. 'G.998.1' == Outdated reference: A later version (-11) exists of draft-ietf-adslmib-gbond-mib-04 ** Downref: Normative reference to an Informational RFC: RFC 3410 -- Possible downref: Non-RFC (?) normative reference: ref. 'TR-159' Summary: 1 error (**), 0 flaws (~~), 5 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 27, 2010 5 Expires: November 28, 2010 7 ATM-Based xDSL Bonded Interfaces MIB 8 draft-ietf-adslmib-gbond-atm-mib-01.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 28, 2010. 35 Copyright Notice 37 Copyright (c) 2010 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 . . . . . . . . . . . . . . . . . . 32 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 Unsigned32, 239 Counter32, 240 TimeTicks 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 InterfaceIndex 251 FROM IF-MIB -- [RFC2863] 252 HCPerfCurrentCount, 253 HCPerfIntervalCount, 254 HCPerfIntervalThreshold, 255 HCPerfValidIntervals, 256 HCPerfInvalidIntervals, 257 HCPerfTimeElapsed, 258 HCPerfTotalCount 259 FROM HC-PerfHist-TC-MIB -- [RFC3705] 260 ; 262 gBondAtmMIB MODULE-IDENTITY 263 LAST-UPDATED "201005270000Z" -- May 27, 2010 264 ORGANIZATION "IETF ADSL MIB Working Group" 265 CONTACT-INFO 266 "WG charter: 267 http://www.ietf.org/html.charters/adslmib-charter.html 269 Mailing Lists: 270 General Discussion: adslmib@ietf.org 271 To Subscribe: adslmib-request@ietf.org 272 In Body: subscribe your_email_address 274 Chair: Menachem Dodge 275 Postal: ECI Telecom, Ltd. 276 30 Hasivim St., 277 Petach-Tikva 49517 278 Israel 279 Phone: +972-3-926-8421 280 EMail: menachem.dodge@ecitele.com 282 Editor: Edward Beili 283 Postal: Actelis Networks, Inc. 284 25 Bazel St., P.O.B. 10173 285 Petach-Tikva 10173 286 Israel 287 Phone: +972-3-924-3491 288 EMail: edward.beili@actelis.com" 290 DESCRIPTION 291 "The objects in this MIB module are used to manage the 292 multi-pair bonded xDSL Interfaces using ATM inverse 293 multiplexing, defined in ITU-T recommendation G.998.1 294 (G.Bond/ATM). 296 This MIB module MUST be used in conjunction with GBOND-MIB 297 module, common to all G.Bond technologies. 299 The following references are used throughout this MIB module: 301 [G.998.1] refers to: 302 ITU-T Recommendation G.998.1: 'ATM-based multi-pair bonding', 303 January 2005. 305 [TR-159] refers to: 306 Broadband Forum Technical Report: 'Management Framework for 307 xDSL Bonding', December 2008. 309 Naming Conventions: 310 ATM - Asynchronous Transfer Mode 311 BCE - Bonding Channel Entity 312 BTU - Bonding Terminating Unit 313 CO - Central Office 314 CPE - Customer Premises Equipment 315 GBS - Generic Bonding Sublayer 316 GBS-C - Generic Bonded Sub-layer, CO side 317 GBS-R - Generic Bonded Sub-layer, RT (or CPE) side 318 PM - Performance Monitoring 319 RT - Remote Terminal 320 SNR - Signal to Noise Ratio 321 SES - Severely Errored Seconds 322 US - Unavailable Seconds 324 Copyright (C) The IETF Trust (2010). 325 This version of this MIB module is part of RFC YYYY; 326 see the RFC itself for full legal notices." 328 REVISION "201005270000Z" -- May 27, 2010 329 DESCRIPTION "Initial version, published as RFC YYYY." 331 -- EdNote: Replace YYYY with the actual RFC number & 332 -- remove this note 334 ::= { mib-2 ZZZ } 336 -- EdNote: Replace ZZZ with a real OID once it is 337 -- allocated & remove this note. 339 -- Sections of the module 340 -- Structured as recommended by [RFC4181], Appendix D 342 gBondAtmObjects OBJECT IDENTIFIER ::= { gBondAtmMIB 1 } 343 gBondAtmConformance OBJECT IDENTIFIER ::= { gBondAtmMIB 2 } 345 -- Groups in the module 347 gBondAtmPort OBJECT IDENTIFIER ::= { gBondAtmObjects 1 } 349 -- Textual Conventions 351 MilliSeconds ::= TEXTUAL-CONVENTION 352 DISPLAY-HINT "d" 353 STATUS current 354 DESCRIPTION 355 "Represents time unit value in milliseconds." 356 SYNTAX Unsigned32 358 -- Port Notifications Group 360 gBondAtmPortNotifications OBJECT IDENTIFIER 361 ::= { gBondAtmPort 0 } 363 gBondAtmUpDiffDelayToleranceExceeded NOTIFICATION-TYPE 364 OBJECTS { 365 -- ifIndex is not needed here since we are under specific GBS 366 gBondAtmUpDiffDelayTolerance, 367 gBondAtmMaxUpDiffDelay 368 } 369 STATUS current 370 DESCRIPTION 371 "This notification indicates that the maximum upstream 372 differential delay has exceeded the max upstream differential 373 delay threshold, specified by gBondAtmUpDiffDelayTolerance. 375 This notification MAY be sent for the GBS-C ports while the 376 port is up, on the crossing event in both directions: from 377 normal (diff. delay is above the threshold) to low (diff. 378 delay equals the threshold or below it) and from low to 379 normal. This notification is not applicable to the GBS-R 380 ports. 382 Generation of this notification is controlled by the 383 gBondAtmDiffDelayToleranceExceededEnable attribute. 385 This object maps to the TR-159 notification 386 nIMAUpDiffDelayToleranceExceeded." 387 REFERENCE 388 "[TR-159] 5.5.2.8" 389 ::= { gBondAtmPortNotifications 1 } 391 gBondAtmDnDiffDelayToleranceExceeded NOTIFICATION-TYPE 392 OBJECTS { 393 -- ifIndex is not needed here since we are under specific GBS 394 gBondAtmDnDiffDelayTolerance, 395 gBondAtmMaxDnDiffDelay 396 } 397 STATUS current 398 DESCRIPTION 399 "This notification indicates that the maximum downstream 400 differential delay has exceeded the max downstream 401 differential delay threshold, specified by 402 gBondAtmDnDiffDelayTolerance. 404 This notification MAY be sent for the GBS-C ports while the 405 port is up, on the crossing event in both directions: from 406 normal (diff. delay is above the threshold) to low (diff. 407 delay equals the threshold or below it) and from low to 408 normal. This notification is not applicable to the GBS-R 409 ports. 411 Generation of this notification is controlled by the 412 gBondAtmDiffDelayToleranceExceededEnable attribute. 414 This object maps to the TR-159 notification 415 nIMADownDiffDelayToleranceExceeded." 416 REFERENCE 417 "[TR-159] 5.5.2.9" 418 ::= { gBondAtmPortNotifications 2 } 420 -- G.Bond/ATM Port group 422 gBondAtmPortConfTable OBJECT-TYPE 423 SYNTAX SEQUENCE OF GBondAtmPortConfEntry 424 MAX-ACCESS not-accessible 425 STATUS current 426 DESCRIPTION 427 "Table for Configuration of G.Bond/ATM ports. Entries in 428 this table MUST be maintained in a persistent manner" 429 ::= { gBondAtmPort 1 } 431 gBondAtmPortConfEntry OBJECT-TYPE 432 SYNTAX GBondAtmPortConfEntry 433 MAX-ACCESS not-accessible 434 STATUS current 435 DESCRIPTION 436 "An entry in the G.Bond/ATM Port Configuration table. 437 Each entry represents an G.Bond/ATM port indexed by the 438 ifIndex. Additional configuration parameters are available 439 via the gBondPortConfEntry of GBOND-MIB. 440 Note that an G.Bond/ATM port runs on top of a single or 441 multiple BCE port(s), which are also indexed by ifIndex." 442 INDEX { ifIndex } 443 ::= { gBondAtmPortConfTable 1 } 445 GBondAtmPortConfEntry ::= 446 SEQUENCE { 447 gBondAtmUpDiffDelayTolerance MilliSeconds, 448 gBondAtmDnDiffDelayTolerance MilliSeconds, 449 gBondAtmDiffDelayToleranceExceededEnable TruthValue 450 } 452 gBondAtmUpDiffDelayTolerance OBJECT-TYPE 453 SYNTAX MilliSeconds(0..2047) 454 UNITS "milliseconds" 455 MAX-ACCESS read-write 456 STATUS current 457 DESCRIPTION 458 "A maximum tolerated upstream differential delay (among 459 the member BCEs) of a G.Bond/ATM port, expressed in ms. 461 This object is read-write for the GBS-C and irrelevant for 462 the GBS-R ports. 464 This object maps to TR-159 attribute 465 aIMAUpDiffDelayTolerance" 466 REFERENCE 467 "[T-159] 5.5.2.5; [G.998.1] 11.4.1 (6)" 468 ::= { gBondAtmPortConfEntry 1 } 470 gBondAtmDnDiffDelayTolerance OBJECT-TYPE 471 SYNTAX MilliSeconds(0..2047) 472 UNITS "milliseconds" 473 MAX-ACCESS read-write 474 STATUS current 475 DESCRIPTION 476 "A maximum tolerated downstream differential delay (among 477 the member BCEs) of a G.Bond/ATM port, expressed in ms. 479 This object is read-write for the GBS-C and irrelevant for 480 the GBS-R ports. 482 This object maps to TR-159 attribute 483 aIMADownDiffDelayTolerance" 484 REFERENCE 485 "[T-159] 5.5.2.6; [G.998.1] 11.4.1 (6)" 486 ::= { gBondAtmPortConfEntry 2 } 488 gBondAtmDiffDelayToleranceExceededEnable OBJECT-TYPE 489 SYNTAX TruthValue 490 MAX-ACCESS read-write 491 STATUS current 492 DESCRIPTION 493 "Indicates whether gBondAtmUpDiffDelayToleranceExceeded and 494 gBondAtmDnDiffDelayToleranceExceeded notifications should 495 be generated for G.Bond/ATM port. 497 Value of true(1) indicates that the notifications are enabled. 498 Value of false(2) indicates that the notifications are 499 disabled. 501 This object is read-write for the GBS-C and irrelevant for 502 the GBS-R ports. 503 This object MUST be maintained in a persistent manner. 505 This object maps to the TR-159 attribute 506 aIMADiffDelayToleranceExceededEnable." 507 REFERENCE 508 "[TR-159] 5.5.5.7" 509 ::= { gBondAtmPortConfEntry 3 } 511 gBondAtmPortStatusTable OBJECT-TYPE 512 SYNTAX SEQUENCE OF GBondAtmPortStatusEntry 513 MAX-ACCESS not-accessible 514 STATUS current 515 DESCRIPTION 516 "This table provides overall status information of G.Bond/ATM 517 ports, complementing the generic status information from the 518 ifTable of IF-MIB and gBondFltStatus of GBOND-MIB. 519 Additional status information about connected BCEs is available 520 from the relevant line MIBs. 522 This table contains live data from the equipment. As such, it is 523 NOT persistent." 524 ::= { gBondAtmPort 2 } 526 gBondAtmPortStatusEntry OBJECT-TYPE 527 SYNTAX GBondAtmPortStatusEntry 528 MAX-ACCESS not-accessible 529 STATUS current 530 DESCRIPTION 531 "An entry in the G.Bond/ATM port Status table. 532 Each entry represents a G.Bond/ATM port indexed by the 533 ifIndex. 534 Note that a GBS port runs on top of a single or multiple BCE 535 port(s), which are also indexed by ifIndex." 536 INDEX { ifIndex } 537 ::= { gBondAtmPortStatusTable 1 } 539 GBondAtmPortStatusEntry ::= 540 SEQUENCE { 541 gBondAtmRxLostCells Counter32, 542 gBondAtmTxLostCells Counter32, 543 gBondAtmMaxUpDiffDelay Unsigned32, 544 gBondAtmMaxDnDiffDelay Unsigned32 545 } 547 gBondAtmRxLostCells OBJECT-TYPE 548 SYNTAX Counter32 549 MAX-ACCESS read-only 550 STATUS current 551 DESCRIPTION 552 "The number of lost ATM cells detected by the G.Bond/ATM port 553 in the receive direction, i.e. upstream direction for 554 a GBS-C port. 556 Discontinuities in the value of this counter can occur at 557 re-initialization of the management system, and at other times 558 as indicated by the value of ifCounterDiscontinuityTime, 559 defined in IF-MIB. 561 This object maps to TR-159 attribute aIMARxLostCells." 562 REFERENCE 563 "[TR-159] 5.5.2.1; [G.998.1] 11.4.2 (4)" 564 ::= { gBondAtmPortStatusEntry 1 } 566 gBondAtmTxLostCells OBJECT-TYPE 567 SYNTAX Counter32 568 MAX-ACCESS read-only 569 STATUS current 570 DESCRIPTION 571 "The number of lost ATM cells detected by the peer G.Bond/ATM 572 port in the receive direction, e.g. downstream direction for a 573 GBS-C port. 575 This object is read only for the GBS-C ports and irrelevant 576 for the GBS-R ports. 578 Discontinuities in the value of this counter can occur at 579 re-initialization of the management system, and at other times 580 as indicated by the value of ifCounterDiscontinuityTime, 581 defined in IF-MIB. 583 This object maps to TR-159 attribute aIMAPeerRxLostCells." 584 REFERENCE 585 "[TR-159] 5.5.2.1; [G.998.1] 11.4.2 (4)" 586 ::= { gBondAtmPortStatusEntry 2 } 588 gBondAtmMaxUpDiffDelay OBJECT-TYPE 589 SYNTAX Unsigned32 590 UNITS "0.1 ms" 591 MAX-ACCESS read-only 592 STATUS current 593 DESCRIPTION 594 "Current maximum upstream differential delay between all 595 operational BCEs in the G.Bond/ATM bonding group, measured in 596 units of 0.1ms. 598 This object is read-only for the GBS-C and irrelevant for 599 the GBS-R ports. 601 This object maps to TR-159 attribute aIMAMaxUpDiffDelay." 602 REFERENCE 603 "[TR-159] 5.5.2.3" 604 ::= { gBondAtmPortStatusEntry 3 } 606 gBondAtmMaxDnDiffDelay OBJECT-TYPE 607 SYNTAX Unsigned32 608 UNITS "0.1 ms" 609 MAX-ACCESS read-only 610 STATUS current 611 DESCRIPTION 612 "Current maximum downstream differential delay between all 613 operational BCEs in the G.Bond/ATM bonding group, measured in 614 units of 0.1ms. 616 This object is read-only for the GBS-C and irrelevant for 617 the GBS-R ports. 619 This object maps to TR-159 attribute aIMAMaxDownDiffDelay." 620 REFERENCE 621 "[TR-159] 5.5.2.4" 622 ::= { gBondAtmPortStatusEntry 4 } 624 ------------------------------- 625 -- Performance Monitoring group 626 ------------------------------- 628 gBondAtmPM OBJECT IDENTIFIER ::= { gBondAtmPort 3 } 630 gBondAtmPortPerfCurrTable OBJECT-TYPE 631 SYNTAX SEQUENCE OF GBondAtmPortPerfCurrEntry 632 MAX-ACCESS not-accessible 633 STATUS current 634 DESCRIPTION 635 "This table contains current Performance Monitoring information 636 for a G.Bond/ATM port. This table contains live data from the 637 equipment and as such is NOT persistent." 638 ::= { gBondAtmPM 1 } 640 gBondAtmPortPerfCurrEntry OBJECT-TYPE 641 SYNTAX GBondAtmPortPerfCurrEntry 642 MAX-ACCESS not-accessible 643 STATUS current 644 DESCRIPTION 645 "An entry in the G.Bond/ATM Port PM table. 646 Each entry represents an G.Bond/ATM port indexed by the 647 ifIndex." 648 INDEX { ifIndex } 649 ::= { gBondAtmPortPerfCurrTable 1 } 651 GBondAtmPortPerfCurrEntry ::= 652 SEQUENCE { 653 gBondAtmPortPerf15MinValidIntervals HCPerfValidIntervals, 654 gBondAtmPortPerf15MinInvalidIntervals HCPerfInvalidIntervals, 655 gBondAtmPortPerfCurr15MinTimeElapsed HCPerfTimeElapsed, 656 gBondAtmPortPerfCurr15MinRxLostCells HCPerfCurrentCount, 657 gBondAtmPortPerfCurr15MinTxLostCells HCPerfCurrentCount, 658 gBondAtmPortPerfCurr15MinUpDiffDelay HCPerfCurrentCount, 659 gBondAtmPortPerfCurr15MinDnDiffDelay HCPerfCurrentCount, 660 gBondAtmPortPerf1DayValidIntervals Unsigned32, 661 gBondAtmPortPerf1DayInvalidIntervals Unsigned32, 662 gBondAtmPortPerfCurr1DayTimeElapsed HCPerfTimeElapsed, 663 gBondAtmPortPerfCurr1DayRxLostCells HCPerfCurrentCount, 664 gBondAtmPortPerfCurr1DayTxLostCells HCPerfCurrentCount, 665 gBondAtmPortPerfCurr1DayUpDiffDelay HCPerfCurrentCount, 666 gBondAtmPortPerfCurr1DayDnDiffDelay HCPerfCurrentCount 667 } 669 gBondAtmPortPerf15MinValidIntervals OBJECT-TYPE 670 SYNTAX HCPerfValidIntervals 671 MAX-ACCESS read-only 672 STATUS current 673 DESCRIPTION 674 "A read-only number of 15-minute intervals for which the 675 performance data was collected. The value of this object will 676 be 96 or the maximum number of 15-minute history intervals 677 collected by the implementation unless the measurement was 678 (re-)started recently, in which case the value will be the 679 number of complete 15 minutes intervals for which there are at 680 least some data. 681 In certain cases it is possible that some intervals are 682 unavailable. In this case, this object reports the maximum 683 interval number for which data is available. 685 This object partially maps to the TR-159 attribute 686 aGroupPerf15MinValidIntervals." 687 REFERENCE 688 "[TR-159] 5.5.1.32" 689 ::= { gBondAtmPortPerfCurrEntry 1 } 691 gBondAtmPortPerf15MinInvalidIntervals OBJECT-TYPE 692 SYNTAX HCPerfInvalidIntervals 693 MAX-ACCESS read-only 694 STATUS current 695 DESCRIPTION 696 "A read-only number of 15-minute intervals for which the 697 performance data was not always available. The value will 698 typically be zero except in cases where the data for some 699 intervals are not available. 701 This object partially maps to the TR-159 attribute 702 aGroupPerf15MinInvalidIntervals." 703 REFERENCE 704 "[TR-159] 5.5.1.33" 705 ::= { gBondAtmPortPerfCurrEntry 2 } 707 gBondAtmPortPerfCurr15MinTimeElapsed OBJECT-TYPE 708 SYNTAX HCPerfTimeElapsed 709 MAX-ACCESS read-only 710 STATUS current 711 DESCRIPTION 712 "A read-only count of seconds that have elapsed since the 713 beginning of the current 15-minute performance history interval. 715 This object partially maps to the TR-159 attribute 716 aGroupPerfCurr15MinTimeElapsed." 717 REFERENCE 718 "[TR-159] 5.5.1.34" 719 ::= { gBondAtmPortPerfCurrEntry 3 } 721 gBondAtmPortPerfCurr15MinRxLostCells OBJECT-TYPE 722 SYNTAX HCPerfCurrentCount 723 MAX-ACCESS read-only 724 STATUS current 725 DESCRIPTION 726 "A read-only count of lost ATM cells detected by a G.Bond/ATM 727 port (e.g. GBS-C) in the receive direction, during the current 728 15-minute performance history interval. 730 Note that the total number of lost ATM cells is indicated by the 731 gBondAtmRxLostCells object. 733 This object is inhibited during Severely Errored Seconds (SES) 734 or Unavailable Seconds (UAS)." 735 REFERENCE 736 "[TR-159] 5.5.2.1" 737 ::= { gBondAtmPortPerfCurrEntry 4} 739 gBondAtmPortPerfCurr15MinTxLostCells OBJECT-TYPE 740 SYNTAX HCPerfCurrentCount 741 MAX-ACCESS read-only 742 STATUS current 743 DESCRIPTION 744 "A read-only count of lost ATM cells detected by the peer 745 G.Bond/ATM port (e.g. by GBS-R for GBS-C), during the current 746 15-minute performance history interval. 748 Note that the total number of lost ATM cells is indicated by the 749 gBondAtmTxLostCells object. 751 This object is inhibited during Unavailable Seconds (UAS)." 752 REFERENCE 753 "[TR-159] 5.5.2.2" 754 ::= { gBondAtmPortPerfCurrEntry 5} 756 gBondAtmPortPerfCurr15MinUpDiffDelay OBJECT-TYPE 757 SYNTAX HCPerfCurrentCount 758 MAX-ACCESS read-only 759 STATUS current 760 DESCRIPTION 761 "A read-only value specifying maximum upstream differential 762 delay between all operational BCEs in the GBS-C, measured in 763 units of 0.1ms, during the current 15-minute performance history 764 interval. 766 Note that the current max upstream differential delay is 767 indicated by the gBondAtmMaxUpDiffDelay object. 769 This object is inhibited during Unavailable Seconds (UAS)." 770 REFERENCE 771 "[TR-159] 5.5.2.3" 772 ::= { gBondAtmPortPerfCurrEntry 6} 774 gBondAtmPortPerfCurr15MinDnDiffDelay OBJECT-TYPE 775 SYNTAX HCPerfCurrentCount 776 MAX-ACCESS read-only 777 STATUS current 778 DESCRIPTION 779 "A read-only value specifying maximum downstream differential 780 delay between all operational BCEs in the GBS-C (as percieved 781 by GBS-R), measured in units of 0.1ms, during the current 782 15-minute performance history interval. 784 Note that the current max downstream differential delay is 785 indicated by the gBondAtmMaxDnDiffDelay object. 787 This object is inhibited during Unavailable Seconds (UAS)." 788 REFERENCE 789 "[TR-159] 5.5.2.4" 790 ::= { gBondAtmPortPerfCurrEntry 7} 792 gBondAtmPortPerf1DayValidIntervals OBJECT-TYPE 793 SYNTAX Unsigned32 (0..7) 794 MAX-ACCESS read-only 795 STATUS current 796 DESCRIPTION 797 "A read-only number of 1-day intervals for which data was 798 collected. The value of this object will be 7 or the maximum 799 number of 1-day history intervals collected by the 800 implementation unless the measurement was (re-)started recently, 801 in which case the value will be the number of complete 1-day 802 intervals for which there are at least some data. 803 In certain cases it is possible that some intervals are 804 unavailable. In this case, this object reports the maximum 805 interval number for which data is available." 806 REFERENCE 807 "[TR-159] 5.5.1.45" 808 ::= { gBondAtmPortPerfCurrEntry 8 } 810 gBondAtmPortPerf1DayInvalidIntervals OBJECT-TYPE 811 SYNTAX Unsigned32 (0..7) 812 MAX-ACCESS read-only 813 STATUS current 814 DESCRIPTION 815 "A read-only number of 1-day intervals for which data was 816 not always available. The value will typically be zero except in 817 cases where the data for some intervals are not available." 818 REFERENCE 819 "[TR-159] 5.5.1.46" 820 ::= { gBondAtmPortPerfCurrEntry 9 } 822 gBondAtmPortPerfCurr1DayTimeElapsed OBJECT-TYPE 823 SYNTAX HCPerfTimeElapsed 824 MAX-ACCESS read-only 825 STATUS current 826 DESCRIPTION 827 "A read-only count of seconds that have elapsed since the 828 beginning of the current 1-day performance history interval." 829 REFERENCE 830 "[TR-159] 5.5.1.47" 831 ::= { gBondAtmPortPerfCurrEntry 10 } 833 gBondAtmPortPerfCurr1DayRxLostCells OBJECT-TYPE 834 SYNTAX HCPerfCurrentCount 835 MAX-ACCESS read-only 836 STATUS current 837 DESCRIPTION 838 "A read-only count of lost ATM cells detected by the G.Bond/ATM 839 port (e.g. GBS-C), during the current 1-day performance history 840 interval. 842 This object is inhibited during Severely Errored Seconds (SES) 843 and Unavailable Seconds (UAS)." 844 REFERENCE 845 "" 846 ::= { gBondAtmPortPerfCurrEntry 11 } 848 gBondAtmPortPerfCurr1DayTxLostCells OBJECT-TYPE 849 SYNTAX HCPerfCurrentCount 850 MAX-ACCESS read-only 851 STATUS current 852 DESCRIPTION 853 "A read-only count of lost ATM cells detected by the peer 854 G.Bond/ATM port (e.g. by GBS-R for GBS-C), during the current 855 1-day performance history interval. 857 This object is inhibited during Unavailable Seconds (UAS)." 858 REFERENCE 859 "" 860 ::= { gBondAtmPortPerfCurrEntry 12 } 862 gBondAtmPortPerfCurr1DayUpDiffDelay OBJECT-TYPE 863 SYNTAX HCPerfCurrentCount 864 MAX-ACCESS read-only 865 STATUS current 866 DESCRIPTION 867 "A read-only value specifying maximum upstream differential 868 delay between all operational BCEs in the GBS-C, measured in 869 units of 0.1ms, during the current 1-day performance history 870 interval. 872 This object is inhibited during Unavailable Seconds (UAS)." 873 REFERENCE 874 "" 875 ::= { gBondAtmPortPerfCurrEntry 13 } 877 gBondAtmPortPerfCurr1DayDnDiffDelay OBJECT-TYPE 878 SYNTAX HCPerfCurrentCount 879 MAX-ACCESS read-only 880 STATUS current 881 DESCRIPTION 882 "A read-only value specifying maximum downstream differential 883 delay between all operational BCEs in the GBS-C, measured in 884 units of 0.1ms, during the current 1-day performance history 885 interval. 887 This object is inhibited during Unavailable Seconds (UAS)." 888 REFERENCE 889 "" 890 ::= { gBondAtmPortPerfCurrEntry 14 } 892 -- Port PM history: 15-min buckets 894 gBondAtmPortPerf15MinTable OBJECT-TYPE 895 SYNTAX SEQUENCE OF GBondAtmPortPerf15MinEntry 896 MAX-ACCESS not-accessible 897 STATUS current 898 DESCRIPTION 899 "This table contains historical 15-minute buckets of Performance 900 Monitoring information for a G.Bond/ATM port (a row for each 901 15-minute interval, up to 96 intervals). 902 Entries in this table MUST be maintained in a persistent manner." 903 ::= { gBondAtmPM 2 } 905 gBondAtmPortPerf15MinEntry OBJECT-TYPE 906 SYNTAX GBondAtmPortPerf15MinEntry 907 MAX-ACCESS not-accessible 908 STATUS current 909 DESCRIPTION 910 "An entry in the G.Bond/ATM Port historical 15-minute PM table. 911 Each entry represents performance monitoring data for a 912 G.Bond/ATM port, indexed by ifIndex, collected during a 913 particular 15-minute interval, indexed by 914 gBondAtmPortPerf15MinIntervalIndex." 915 INDEX { ifIndex, gBondAtmPortPerf15MinIntervalIndex } 916 ::= { gBondAtmPortPerf15MinTable 1 } 918 GBondAtmPortPerf15MinEntry ::= 919 SEQUENCE { 920 gBondAtmPortPerf15MinIntervalIndex Unsigned32, 921 gBondAtmPortPerf15MinIntervalMoniTime HCPerfTimeElapsed, 922 gBondAtmPortPerf15MinIntervalRxLostCells HCPerfIntervalCount, 923 gBondAtmPortPerf15MinIntervalTxLostCells HCPerfIntervalCount, 924 gBondAtmPortPerf15MinIntervalUpDiffDelay HCPerfIntervalCount, 925 gBondAtmPortPerf15MinIntervalDnDiffDelay HCPerfIntervalCount, 926 gBondAtmPortPerf15MinIntervalValid TruthValue 927 } 929 gBondAtmPortPerf15MinIntervalIndex OBJECT-TYPE 930 SYNTAX Unsigned32 (1..96) 931 MAX-ACCESS not-accessible 932 STATUS current 933 DESCRIPTION 934 "Performance Data Interval number. 1 is the most recent previous 935 interval; interval 96 is 24 hours ago. 936 Intervals 2..96 are OPTIONAL. 938 This object partially maps to the TR-159 attribute 939 aGroupPerf15MinIntervalNumber." 940 REFERENCE 941 "[TR-159] 5.5.1.57" 942 ::= { gBondAtmPortPerf15MinEntry 1 } 944 gBondAtmPortPerf15MinIntervalMoniTime OBJECT-TYPE 945 SYNTAX HCPerfTimeElapsed 946 MAX-ACCESS read-only 947 STATUS current 948 DESCRIPTION 949 "A read-only count of seconds over which the performance data 950 was actually monitored. This value will be the same as the 951 interval duration (900 seconds), except in a situation where 952 performance data could not be collected for any reason." 953 ::= { gBondAtmPortPerf15MinEntry 2 } 955 gBondAtmPortPerf15MinIntervalRxLostCells OBJECT-TYPE 956 SYNTAX HCPerfIntervalCount 957 MAX-ACCESS read-only 958 STATUS current 959 DESCRIPTION 960 "A read-only count of lost ATM cells detected by a G.Bond/ATM 961 port (e.g. GBS-C) in the receive direction, during the 962 15-minute performance history interval. 964 Note that the total number of lost ATM cells is indicated by the 965 gBondAtmRxLostCells object. 967 This object is inhibited during Severely Errored Seconds (SES) 968 or Unavailable Seconds (UAS)." 969 REFERENCE 970 "[TR-159] 5.5.2.1" 971 ::= { gBondAtmPortPerf15MinEntry 3 } 973 gBondAtmPortPerf15MinIntervalTxLostCells OBJECT-TYPE 974 SYNTAX HCPerfIntervalCount 975 MAX-ACCESS read-only 976 STATUS current 977 DESCRIPTION 978 "A read-only count of lost ATM cells detected by the peer 979 G.Bond/ATM port (e.g. by GBS-R for GBS-C), during the 15-minute 980 performance history interval. 982 Note that the total number of lost ATM cells is indicated by the 983 gBondAtmTxLostCells object. 985 This object is inhibited during Unavailable Seconds (UAS)." 986 REFERENCE 987 "[TR-159] 5.5.2.2" 988 ::= { gBondAtmPortPerf15MinEntry 4 } 990 gBondAtmPortPerf15MinIntervalUpDiffDelay OBJECT-TYPE 991 SYNTAX HCPerfIntervalCount 992 MAX-ACCESS read-only 993 STATUS current 994 DESCRIPTION 995 "A read-only value specifying maximum upstream differential 996 delay between all operational BCEs in the GBS, measured in 997 units of 0.1ms, during the 15-minute performance history 998 interval. 1000 Note that the current max upstream differential delay is 1001 indicated by the gBondAtmMaxUpDiffDelay object. 1003 This object is inhibited during Unavailable Seconds (UAS)." 1004 REFERENCE 1005 "[TR-159] 5.5.2.3" 1006 ::= { gBondAtmPortPerf15MinEntry 5 } 1008 gBondAtmPortPerf15MinIntervalDnDiffDelay OBJECT-TYPE 1009 SYNTAX HCPerfIntervalCount 1010 MAX-ACCESS read-only 1011 STATUS current 1012 DESCRIPTION 1013 "A read-only value specifying maximum downstream differential 1014 delay between all operational BCEs in the GBS, as perceived by 1015 its peer port, measured in units of 0.1ms, during the 1016 15-minute performance history interval. 1018 Note that the current max upstream differential delay is 1019 indicated by the gBondAtmMaxDnDiffDelay object. 1021 This object is inhibited during Unavailable Seconds (UAS)." 1022 REFERENCE 1023 "[TR-159] 5.5.2.4" 1024 ::= { gBondAtmPortPerf15MinEntry 6 } 1026 gBondAtmPortPerf15MinIntervalValid OBJECT-TYPE 1027 SYNTAX TruthValue 1028 MAX-ACCESS read-only 1029 STATUS current 1030 DESCRIPTION 1031 "A read-only object indicating whether or not this history 1032 bucket contains valid data. Valid bucket is reported as true(1) 1033 and invalid bucket as false(2). 1034 If this history bucket is invalid the BTU MUST NOT produce 1035 notifications based upon the value of the counters in this 1036 bucket. 1037 Note that an implementation may decide not to store invalid 1038 history buckets in its data base. In such case this object is 1039 not required as only valid history buckets are available while 1040 invalid history buckets are simply not in the data base. 1042 This object partially maps to the TR-159 attribute 1043 aGroupPerf15MinIntervalValid." 1044 REFERENCE 1045 "[TR-159] 5.5.1.58" 1046 ::= { gBondAtmPortPerf15MinEntry 7 } 1048 -- Port PM history: 1-day buckets 1050 gBondAtmPortPerf1DayTable OBJECT-TYPE 1051 SYNTAX SEQUENCE OF GBondAtmPortPerf1DayEntry 1052 MAX-ACCESS not-accessible 1053 STATUS current 1054 DESCRIPTION 1055 "This table contains historical 1-day buckets of Performance 1056 Monitoring information for a G.Bond/ATM port (a row for each 1057 1-day interval, up to 7 intervals). 1058 Entries in this table MUST be maintained in a persistent manner." 1059 ::= { gBondAtmPM 3 } 1061 gBondAtmPortPerf1DayEntry OBJECT-TYPE 1062 SYNTAX GBondAtmPortPerf1DayEntry 1063 MAX-ACCESS not-accessible 1064 STATUS current 1065 DESCRIPTION 1066 "An entry in the G.Bond/ATM port historical 1-day PM table. 1067 Each entry represents performance monitoring data for such port, 1068 indexed by ifIndex, collected during a particular 1-day 1069 interval, indexed by gBondAtmPortPerf1DayIntervalIndex." 1070 INDEX { ifIndex, gBondAtmPortPerf1DayIntervalIndex } 1071 ::= { gBondAtmPortPerf1DayTable 1 } 1073 GBondAtmPortPerf1DayEntry ::= 1074 SEQUENCE { 1075 gBondAtmPortPerf1DayIntervalIndex Unsigned32, 1076 gBondAtmPortPerf1DayIntervalMoniTime HCPerfTimeElapsed, 1077 gBondAtmPortPerf1DayIntervalRxLostCells HCPerfIntervalCount, 1078 gBondAtmPortPerf1DayIntervalTxLostCells HCPerfIntervalCount, 1079 gBondAtmPortPerf1DayIntervalUpDiffDelay HCPerfIntervalCount, 1080 gBondAtmPortPerf1DayIntervalDnDiffDelay HCPerfIntervalCount, 1081 gBondAtmPortPerf1DayIntervalValid TruthValue 1082 } 1084 gBondAtmPortPerf1DayIntervalIndex OBJECT-TYPE 1085 SYNTAX Unsigned32 (1..7) 1086 MAX-ACCESS not-accessible 1087 STATUS current 1088 DESCRIPTION 1089 "Performance Data Interval number. 1 is the most recent previous 1090 interval; interval 7 is 24 hours ago. 1091 Intervals 2..7 are OPTIONAL. 1093 This object partially maps to the TR-159 attribute 1094 aGroupPerf1DayIntervalNumber." 1095 REFERENCE 1096 "[TR-159] 5.5.1.62" 1097 ::= { gBondAtmPortPerf1DayEntry 1 } 1099 gBondAtmPortPerf1DayIntervalMoniTime OBJECT-TYPE 1100 SYNTAX HCPerfTimeElapsed 1101 MAX-ACCESS read-only 1102 STATUS current 1103 DESCRIPTION 1104 "A read-only count of seconds over which the performance data 1105 was actually monitored. This value will be the same as the 1106 interval duration (86400 seconds), except in a situation where 1107 performance data could not be collected for any reason. 1109 This object partially maps to the TR-159 attribute 1110 aGroupPerf1DayIntervalMoniSecs." 1111 REFERENCE 1112 "[TR-159] 5.5.1.64" 1113 ::= { gBondAtmPortPerf1DayEntry 2 } 1115 gBondAtmPortPerf1DayIntervalRxLostCells OBJECT-TYPE 1116 SYNTAX HCPerfIntervalCount 1117 MAX-ACCESS read-only 1118 STATUS current 1119 DESCRIPTION 1120 "A read-only count of lost ATM cells detected by the G.Bond/ATM 1121 port (e.g. GBS-C), during the 1-day performance history interval. 1123 This object is inhibited during Severely Errored Seconds (SES) 1124 and Unavailable Seconds (UAS)." 1125 REFERENCE 1126 "" 1127 ::= { gBondAtmPortPerf1DayEntry 3 } 1129 gBondAtmPortPerf1DayIntervalTxLostCells OBJECT-TYPE 1130 SYNTAX HCPerfIntervalCount 1131 MAX-ACCESS read-only 1132 STATUS current 1133 DESCRIPTION 1134 "A read-only count of lost ATM cells detected by the peer 1135 G.Bond/ATM port (e.g. by GBS-R for GBS-C), during the 1-day 1136 performance history interval. 1138 This object is inhibited during Unavailable Seconds (UAS)." 1139 REFERENCE 1140 "" 1141 ::= { gBondAtmPortPerf1DayEntry 4 } 1143 gBondAtmPortPerf1DayIntervalUpDiffDelay OBJECT-TYPE 1144 SYNTAX HCPerfIntervalCount 1145 MAX-ACCESS read-only 1146 STATUS current 1147 DESCRIPTION 1148 "A read-only value specifying maximum upstream differential 1149 delay between all operational BCEs in the GBS-C, measured in 1150 units of 0.1ms, during the 1-day performance history interval. 1152 This object is inhibited during Unavailable Seconds (UAS)." 1153 REFERENCE 1154 "" 1155 ::= { gBondAtmPortPerf1DayEntry 5 } 1157 gBondAtmPortPerf1DayIntervalDnDiffDelay OBJECT-TYPE 1158 SYNTAX HCPerfIntervalCount 1159 MAX-ACCESS read-only 1160 STATUS current 1161 DESCRIPTION 1162 "A read-only value specifying maximum downstream differential 1163 delay between all operational BCEs in the GBS-C, measured in 1164 units of 0.1ms, during the 1-day performance history interval. 1166 This object is inhibited during Unavailable Seconds (UAS)." 1167 REFERENCE 1168 "" 1169 ::= { gBondAtmPortPerf1DayEntry 6 } 1171 gBondAtmPortPerf1DayIntervalValid OBJECT-TYPE 1172 SYNTAX TruthValue 1173 MAX-ACCESS read-only 1174 STATUS current 1175 DESCRIPTION 1176 "A read-only object indicating whether or not this history 1177 bucket contains valid data. Valid bucket is reported as true(1) 1178 and invalid bucket as false(2). 1179 If this history bucket is invalid the BTU MUST NOT produce 1180 notifications based upon the value of the counters in this 1181 bucket. 1182 Note that an implementation may decide not to store invalid 1183 history buckets in its data base. In such case this object is 1184 not required as only valid history buckets are available while 1185 invalid history buckets are simply not in the data base. 1187 This object partially maps to the TR-159 attribute 1188 aGroupPerf1DayIntervalValid." 1189 REFERENCE 1190 "[TR-159] 5.5.1.63" 1191 ::= { gBondAtmPortPerf1DayEntry 7 } 1193 -- 1194 -- Conformance Statements 1195 -- 1197 gBondAtmGroups OBJECT IDENTIFIER 1198 ::= { gBondAtmConformance 1 } 1200 gBondAtmCompliances OBJECT IDENTIFIER 1201 ::= { gBondAtmConformance 2 } 1203 -- Object Groups 1205 gBondAtmBasicGroup OBJECT-GROUP 1206 OBJECTS { 1207 gBondAtmRxLostCells, 1208 gBondAtmTxLostCells, 1209 gBondAtmMaxUpDiffDelay, 1210 gBondAtmMaxDnDiffDelay 1211 } 1212 STATUS current 1213 DESCRIPTION 1214 "A collection of objects representing management information 1215 for an G.Bond/ATM port." 1216 ::= { gBondAtmGroups 1 } 1218 gBondAtmAlarmConfGroup OBJECT-GROUP 1219 OBJECTS { 1220 gBondAtmUpDiffDelayTolerance, 1221 gBondAtmDnDiffDelayTolerance, 1222 gBondAtmDiffDelayToleranceExceededEnable 1223 } 1224 STATUS current 1225 DESCRIPTION 1226 "A collection of objects required for configuration of alarm 1227 thresholds and notifications in G.Bond/ATM ports." 1228 ::= { gBondAtmGroups 2 } 1230 gBondAtmNotificationGroup NOTIFICATION-GROUP 1231 NOTIFICATIONS { 1232 gBondAtmUpDiffDelayToleranceExceeded, 1233 gBondAtmDnDiffDelayToleranceExceeded 1234 } 1235 STATUS current 1236 DESCRIPTION 1237 "This group supports notifications of significant conditions 1238 associated with G.Bond/ATM ports." 1239 ::= { gBondAtmGroups 3 } 1241 gBondAtmPerfCurrGroup OBJECT-GROUP 1242 OBJECTS { 1243 gBondAtmPortPerf15MinValidIntervals, 1244 gBondAtmPortPerf15MinInvalidIntervals, 1245 gBondAtmPortPerfCurr15MinTimeElapsed, 1246 gBondAtmPortPerfCurr15MinRxLostCells, 1247 gBondAtmPortPerfCurr15MinTxLostCells, 1248 gBondAtmPortPerfCurr15MinUpDiffDelay, 1249 gBondAtmPortPerfCurr15MinDnDiffDelay, 1250 gBondAtmPortPerf1DayValidIntervals, 1251 gBondAtmPortPerf1DayInvalidIntervals, 1252 gBondAtmPortPerfCurr1DayTimeElapsed, 1253 gBondAtmPortPerfCurr1DayRxLostCells, 1254 gBondAtmPortPerfCurr1DayTxLostCells, 1255 gBondAtmPortPerfCurr1DayUpDiffDelay, 1256 gBondAtmPortPerfCurr1DayDnDiffDelay, 1257 } 1258 STATUS current 1259 DESCRIPTION 1260 "A collection of objects supporting OPTIONAL current Performance 1261 Monitoring information for G.Bond/ATM ports." 1262 ::= { gBondAtmGroups 4 } 1264 gBondAtmPerf15MinGroup OBJECT-GROUP 1265 OBJECTS { 1266 gBondAtmPortPerf15MinIntervalMoniTime, 1267 gBondAtmPortPerf15MinIntervalRxLostCells, 1268 gBondAtmPortPerf15MinIntervalTxLostCells, 1269 gBondAtmPortPerf15MinIntervalUpDiffDelay, 1270 gBondAtmPortPerf15MinIntervalDnDiffDelay, 1271 gBondAtmPortPerf15MinIntervalValid, 1272 } 1273 STATUS current 1274 DESCRIPTION 1275 "A collection of objects supporting OPTIONAL historical 1276 Performance Monitoring information for G.Bond/ATM ports, during 1277 previous 15-minute intervals ." 1278 ::= { gBondAtmGroups 5 } 1280 gBondAtmPerf1DayGroup OBJECT-GROUP 1281 OBJECTS { 1282 gBondAtmPortPerf1DayIntervalMoniTime, 1283 gBondAtmPortPerf1DayIntervalRxLostCells, 1284 gBondAtmPortPerf1DayIntervalTxLostCells, 1285 gBondAtmPortPerf1DayIntervalUpDiffDelay, 1286 gBondAtmPortPerf1DayIntervalDnDiffDelay, 1287 gBondAtmPortPerf1DayIntervalValid, 1288 } 1289 STATUS current 1290 DESCRIPTION 1291 "A collection of objects supporting OPTIONAL historical 1292 Performance Monitoring information for G.Bond/ATM ports, during 1293 previous 1-day intervals ." 1294 ::= { gBondAtmGroups 6 } 1296 -- Compliance Statements 1298 gBondAtmCompliance MODULE-COMPLIANCE 1299 STATUS current 1300 DESCRIPTION 1301 "The compliance statement for G.Bond/ATM interfaces. 1302 Compliance with the following external compliance statements 1303 is REQUIRED: 1305 MIB Module Compliance Statement 1306 ---------- -------------------- 1307 IF-MIB ifCompliance3 1308 GBOND-MIB gBondCompliance" 1310 MODULE -- this module 1311 MANDATORY-GROUPS { 1312 gBondAtmBasicGroup, 1313 gBondAtmAlarmConfGroup, 1314 gBondAtmNotificationGroup 1315 } 1317 GROUP gBondAtmPerfCurrGroup 1318 DESCRIPTION 1319 "Support for this group is only required for implementations 1320 supporting Performance Monitoring." 1322 GROUP gBondAtmPerf15MinGroup 1323 DESCRIPTION 1324 "Support for this group is only required for implementations 1325 supporting historical Performance Monitoring." 1327 GROUP gBondAtmPerf1DayGroup 1328 DESCRIPTION 1329 "Support for this group is only required for implementations 1330 supporting 1-day historical Performance Monitoring." 1332 ::= { gBondAtmCompliances 1 } 1333 END 1335 7. Security Considerations 1337 There is a number of managed objects defined in the GBOND-ATM-MIB 1338 module that have a MAX-ACCESS clause of read-write. Writing to these 1339 objects can have potentially disruptive effects on network operation, 1340 for example: 1342 o Changing of gBondAtmPortConfTable configuration paratemers MAY 1343 lead to a potential Service Level Agreement (SLA) breach, for 1344 example if a traffic delay is increased as a result of the higher 1345 delay tolerance (increased gBondAtmUpDiffDelayTolerance and/or 1346 gBondAtmDnDiffDelayTolerance), or the differential delay tolerance 1347 notifications are disabled by manipulating the 1348 gBondAtmDiffDelayToleranceExceededEnable parameter. 1350 The user of the GBOND-ATM-MIB module must therefore be aware that 1351 support for SET operations in a non-secure environment without proper 1352 protection can have a negative effect on network operations. 1354 The readable objects in the GBOND-ATM-MIB module (i.e., those with 1355 MAX-ACCESS other than not-accessible) may be considered sensitive in 1356 some environments since, collectively, they provide information about 1357 the performance of network interfaces and can reveal some aspects of 1358 their configuration. 1360 In such environments it is important to control also GET and NOTIFY 1361 access to these objects and possibly even to encrypt their values 1362 when sending them over the network via SNMP. 1364 SNMP versions prior to SNMPv3 did not include adequate security. 1365 Even if the network itself is secure (for example by using IPSec), 1366 even then, there is no control as to who on the secure network is 1367 allowed to access and GET/SET (read/change/create/delete) the objects 1368 in this MIB module. 1370 It is RECOMMENDED that implementers consider the security features as 1371 provided by the SNMPv3 framework (see [RFC3410], section 8), 1372 including full support for the SNMPv3 cryptographic mechanisms (for 1373 authentication and privacy). 1375 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1376 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1377 enable cryptographic security. It is then a customer/operator 1378 responsibility to ensure that the SNMP entity giving access to an 1379 instance of this MIB module is properly configured to give access to 1380 the objects only to those principals (users) that have legitimate 1381 rights to indeed GET or SET (change/create/delete) them. 1383 8. IANA Considerations 1385 An object identifier for gBondAtmMIB MODULE-IDENTITY SHALL be 1386 allocated by IANA [1] in the MIB-2 transmission sub-tree, before this 1387 document is published as an RFC. 1389 9. Acknowledgments 1391 This document was produced by the [ADSLMIB] working group. 1393 10. References 1395 10.1. Normative References 1397 [G.998.1] ITU-T, "ATM-based multi-pair bonding", 1398 ITU-T Recommendation G.998.3, 1399 January 2005. 1401 [I-D.ietf-adslmib-gbond-mib] Beili, E. and M. Morgenstern, "xDSL 1402 multi-pair bonding (G.Bond) MIB", 1403 draft-ietf-adslmib-gbond-mib-04 (work 1404 in progress), May 2010. 1406 [RFC2119] Bradner, S., "Key words for use in RFCs 1407 to Indicate Requirement Levels", 1408 BCP 14, RFC 2119, March 1997. 1410 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., 1411 and J. Schoenwaelder, Ed., "Structure 1412 of Management Information Version 2 1413 (SMIv2)", STD 58, RFC 2578, April 1999. 1415 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., 1416 and J. Schoenwaelder, Ed., "Textual 1417 Conventions for SMIv2", STD 58, 1418 RFC 2579, April 1999. 1420 [RFC2580] McCloghrie, K., Perkins, D., and J. 1421 Schoenwaelder, "Conformance Statements 1422 for SMIv2", STD 58, RFC 2580, 1423 April 1999. 1425 [RFC2863] McCloghrie, K. and F. Kastenholz, "The 1426 Interfaces Group MIB", RFC 2863, 1427 June 2000. 1429 [RFC3410] Case, J., Mundy, R., Partain, D., and 1430 B. Stewart, "Introduction and 1431 Applicability Statements for Internet- 1432 Standard Management Framework", 1433 RFC 3410, December 2002. 1435 [RFC3705] Ray, B. and R. Abbi, "High Capacity 1436 Textual Conventions for MIB Modules 1437 Using Performance History Based on 15 1438 Minute Intervals", RFC 3705, 1439 February 2004. 1441 [TR-159] Beili, E. and M. Morgenstern, 1442 "Management Framework for xDSL 1443 Bonding", Broadband Forum technical 1444 report TR-159, December 2008. 1446 10.2. Informative References 1448 [ADSLMIB] IETF, "ADSL MIB (adslmib) Charter", . 1452 [RFC2515] Tesink, K., "Definitions of Managed 1453 Objects for ATM Management", RFC 2515, 1454 February 1999. 1456 [RFC3593] Tesink, K., "Textual Conventions for 1457 MIB Modules Using Performance History 1458 Based on 15 Minute Intervals", 1459 RFC 3593, September 2003. 1461 [RFC4181] Heard, C., "Guidelines for Authors and 1462 Reviewers of MIB Documents", BCP 111, 1463 RFC 4181, September 2005. 1465 [af-phy-0086] ATM Forum, "Inverse Multiplexing for 1466 ATM (IMA) Specification Version 1.1", 1467 ATM Forum specification af-pfy- 1468 0086.001, March 1999. 1470 URIs 1472 [1] 1474 Author's Address 1476 Edward Beili 1477 Actelis Networks 1478 25 Bazel St. 1479 Petach-Tikva 49103 1480 Israel 1482 Phone: +972-3-924-3491 1483 EMail: edward.beili@actelis.com