idnits 2.17.1 draft-ietf-adslmib-gbond-atm-mib-06.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 28 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (March 12, 2012) is 4421 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-10 -- Possible downref: Non-RFC (?) normative reference: ref. 'TR-159' Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group E. Beili 3 Internet-Draft Actelis Networks 4 Intended status: Standards Track March 12, 2012 5 Expires: September 13, 2012 7 ATM-Based xDSL Bonded Interfaces MIB 8 draft-ietf-adslmib-gbond-atm-mib-06.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 13, 2012. 35 Copyright Notice 37 Copyright (c) 2012 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 . . . . . . . . . . . . . . . . . . . 30 65 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 31 66 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 31 67 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 31 68 10.1. Normative References . . . . . . . . . . . . . . . . . . . 31 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", "NOT RECOMMENDED", "MAY", and 109 "OPTIONAL" in this document are to be interpreted as described in RFC 110 2119 [RFC2119]. 112 3. The DSL Forum Management Framework for xDSL Bonding 114 This document makes use of the DSL Forum technical report Management 115 Framework for xDSL Bonding [TR-159], defining a management model and 116 a hierarchy of management objects for the bonded xDSL interfaces. 118 4. Relationship to other MIB modules 120 This section outlines the relationship of the MIB modules defined in 121 this document with other MIB modules described in the relevant RFCs. 122 Specifically, the following MIB modules are discussed: Interfaces 123 Group MIB (IF-MIB) and G.Bond MIB (GBOND-MIB). 125 4.1. Relationship to Interfaces Group MIB module 127 A G.Bond/ATM port is a private case of a Bonded multi-pair xDSL 128 interface and as such is managed using generic interface management 129 objects defined in the IF-MIB [RFC2863]. In particular an interface 130 index (ifIndex) is used to index instances of G.Bond/ATM ports, as 131 well as xDSL lines/channels, in a managed system. 133 4.2. Relationship to G.Bond MIB module 135 GBOND-MIB [I-D.ietf-adslmib-gbond-mib] module defines management 136 objects common for all Bonded multi-pair xDSL interfaces. In 137 particular it describes the bonding management, bonded port and 138 channel configuration, initialization sequence etc. 140 Both GBOND-MIB and G9981-MIB modules are REQUIRED to manage a G.Bond/ 141 ATM port. 143 4.3. Relationship to ATM MIB module 145 ATM-MIB [RFC2515] module defines management objects for an ATM 146 interface. 148 ATM-MIB module can be used to manage the ATM aspects of a G.Bond/ATM 149 port. 151 5. MIB Structure 153 5.1. Overview 155 All management objects defined in the G9981-MIB module are contained 156 in a single group g9981Port. This group is further split into 4 sub- 157 groups, structured as recommended by RFC 4181 [RFC4181]: 159 o g9981PortNotifications - containing notifications (Up/Downstream 160 Differential Delay Tolerance Exceeded). 162 o g9981PortConfTable - containing objects for configuration of a 163 G.Bond/ATM port. 165 o g9981PortStatusTable - containing objects providing overall status 166 information of a G.Bond/ATM port, complementing the generic status 167 information from the ifTable of IF-MIB and gBondFltStatus of 168 GBOND-MIB. 170 o g9981PM - 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. 193 Note that the accumulation of certain performance events for a 194 monitored entity is inhibited (counting stops) during periods of 195 service unavailability on that entity. The DESCRIPTION clause of 196 performance monitoring counters in this MIB module specifies which of 197 the counters are inhibited during periods of service unavailability. 199 5.3. Mapping of Broadband Forum TR-159 Managed Objects 201 This section contains the mapping between relevant managed objects 202 (attributes) defined in [TR-159] and the managed objects defined in 203 this document. 205 +-----------------------------+-------------------------------------+ 206 | TR-159 Managed Object | Corresponding SNMP Object | 207 +-----------------------------+-------------------------------------+ 208 | oBondATM - Basic Package | | 209 | (Mandatory) | | 210 +-----------------------------+-------------------------------------+ 211 | aIMARxLostCells | g9981PortStatRxLostCells | 212 +-----------------------------+-------------------------------------+ 213 | aIMAPeerRxLostCells | g9981PortStatTxLostCells | 214 +-----------------------------+-------------------------------------+ 215 | aIMAMaxUpDiffDelay | g9981PortStatMaxUpDiffDelay | 216 +-----------------------------+-------------------------------------+ 217 | aIMAMaxDownDiffDelay | g9981PortStatMaxDnDiffDelay | 218 +-----------------------------+-------------------------------------+ 219 | aIMAUpDiffDelayTolerance | g9981PortConfUpDiffDelayTolerance | 220 +-----------------------------+-------------------------------------+ 221 | aIMADownDiffDelayTolerance | g9981PortConfDnDiffDelayTolerance | 222 +-----------------------------+-------------------------------------+ 223 | aIMADiffDelayToleranceExcee | g9981PortConfDiffDelayToleranceExce | 224 | dedEnable | ededEnable | 225 +-----------------------------+-------------------------------------+ 226 | nIMAUpDiffDelayToleranceExc | g9981UpDiffDelayToleranceExceeded | 227 | eeded | | 228 +-----------------------------+-------------------------------------+ 229 | nIMADownDiffDelayToleranceE | g9981DnDiffDelayToleranceExceeded | 230 | xceeded | | 231 +-----------------------------+-------------------------------------+ 233 Table 1: Mapping of TR-159 Managed Objects 235 6. G.Bond/ATM MIB Definitions 237 G9981-MIB DEFINITIONS ::= BEGIN 239 IMPORTS 240 MODULE-IDENTITY, 241 OBJECT-TYPE, 242 NOTIFICATION-TYPE, 243 mib-2, 244 Unsigned32, 245 Counter32 246 FROM SNMPv2-SMI -- [RFC2578] 247 TEXTUAL-CONVENTION, 248 TruthValue 249 FROM SNMPv2-TC -- [RFC2579] 250 MODULE-COMPLIANCE, 251 OBJECT-GROUP, 252 NOTIFICATION-GROUP 253 FROM SNMPv2-CONF -- [RFC2580] 254 ifIndex 255 FROM IF-MIB -- [RFC2863] 256 HCPerfCurrentCount, 257 HCPerfIntervalCount, 258 HCPerfValidIntervals, 259 HCPerfInvalidIntervals, 260 HCPerfTimeElapsed 261 FROM HC-PerfHist-TC-MIB -- [RFC3705] 262 ; 263 ------------------------------------------------------------------------ 264 g9981MIB MODULE-IDENTITY 265 LAST-UPDATED "201203120000Z" -- Mar 12, 2012 266 ORGANIZATION "IETF ADSL MIB Working Group" 267 CONTACT-INFO 268 "WG charter: 269 http://www.ietf.org/html.charters/adslmib-charter.html 271 Mailing Lists: 272 General Discussion: adslmib@ietf.org 273 To Subscribe: adslmib-request@ietf.org 274 In Body: subscribe your_email_address 276 Chair: Menachem Dodge 277 Postal: ECI Telecom, Ltd. 278 30 Hasivim St., 279 Petach-Tikva 4951169 280 Israel 281 Phone: +972-3-926-8421 282 EMail: menachem.dodge@ecitele.com 284 Editor: Edward Beili 285 Postal: Actelis Networks, Inc. 286 25 Bazel St., P.O.B. 10173 287 Petach-Tikva 49103 288 Israel 289 Phone: +972-3-924-3491 290 EMail: edward.beili@actelis.com" 292 DESCRIPTION 293 "The objects in this MIB module are used to manage the 294 multi-pair bonded xDSL Interfaces using ATM inverse 295 multiplexing, defined in ITU-T recommendation G.998.1 296 (G.Bond/ATM). 298 This MIB module MUST be used in conjunction with GBOND-MIB 299 module, common to all G.Bond technologies. 301 The following references are used throughout this MIB module: 303 [G.998.1] refers to: 304 ITU-T Recommendation G.998.1: 'ATM-based multi-pair bonding', 305 January 2005. 307 [TR-159] refers to: 308 Broadband Forum Technical Report: 'Management Framework for 309 xDSL Bonding', December 2008. 311 Naming Conventions: 312 ATM - Asynchronous Transfer Mode 313 BCE - Bonding Channel Entity 314 BTU - Bonding Terminating Unit 315 CO - Central Office 316 CPE - Customer Premises Equipment 317 GBS - Generic Bonding Sublayer 318 GBS-C - Generic Bonded Sub-layer, CO side 319 GBS-R - Generic Bonded Sub-layer, RT (or CPE) side 320 PM - Performance Monitoring 321 RT - Remote Terminal 322 SNR - Signal to Noise Ratio 323 SES - Severely Errored Seconds 324 US - Unavailable Seconds 326 Copyright (C) The IETF Trust (2012). 327 This version of this MIB module is part of RFC YYYY; 328 see the RFC itself for full legal notices." 330 REVISION "201203120000Z" -- Mar 12, 2012 331 DESCRIPTION "Initial version, published as RFC YYYY." 333 -- EdNote: Replace YYYY with the actual RFC number & 334 -- remove this note 336 ::= { mib-2 ZZZ } 338 -- EdNote: Replace ZZZ with a real OID once it is 339 -- allocated & remove this note. 341 -- Sections of the module 342 -- Structured as recommended by [RFC4181], Appendix D 344 g9981Objects OBJECT IDENTIFIER ::= { g9981MIB 1 } 346 g9981Conformance OBJECT IDENTIFIER ::= { g9981MIB 2 } 348 -- Groups in the module 349 g9981Port OBJECT IDENTIFIER ::= { g9981Objects 1 } 351 -- Textual Conventions 353 MilliSeconds ::= TEXTUAL-CONVENTION 354 DISPLAY-HINT "d" 355 STATUS current 356 DESCRIPTION 357 "Represents time unit value in milliseconds." 358 SYNTAX Unsigned32 360 -- Port Notifications Group 362 g9981PortNotifications OBJECT IDENTIFIER 363 ::= { g9981Port 0 } 365 g9981UpDiffDelayToleranceExceeded NOTIFICATION-TYPE 366 OBJECTS { 367 -- ifIndex is not needed here since we are under specific GBS 368 g9981PortConfUpDiffDelayTolerance, 369 g9981PortStatMaxUpDiffDelay 370 } 371 STATUS current 372 DESCRIPTION 373 "This notification indicates that the maximum upstream 374 differential delay has exceeded the max upstream differential 375 delay threshold, specified by 376 g9981PortConfUpDiffDelayTolerance. 378 This notification MAY be sent for the GBS-C ports while the 379 port is up, on the crossing event in both directions: from 380 normal (diff. delay is above the threshold) to low (diff. 381 delay equals the threshold or below it) and from low to 382 normal. This notification is not applicable to the GBS-R 383 ports. 385 Generation of this notification is controlled by the 386 g9981PortConfDiffDelayToleranceExceededEnable attribute. 388 This object maps to the TR-159 notification 389 nIMAUpDiffDelayToleranceExceeded." 390 REFERENCE 391 "[TR-159] 5.5.2.8" 392 ::= { g9981PortNotifications 1 } 394 g9981DnDiffDelayToleranceExceeded NOTIFICATION-TYPE 395 OBJECTS { 396 -- ifIndex is not needed here since we are under specific GBS 397 g9981PortConfDnDiffDelayTolerance, 398 g9981PortStatMaxDnDiffDelay 399 } 400 STATUS current 401 DESCRIPTION 402 "This notification indicates that the maximum downstream 403 differential delay has exceeded the max downstream 404 differential delay threshold, specified by 405 g9981PortConfDnDiffDelayTolerance. 407 This notification MAY be sent for the GBS-C ports while the 408 port is up, on the crossing event in both directions: from 409 normal (diff. delay is above the threshold) to low (diff. 410 delay equals the threshold or below it) and from low to 411 normal. This notification is not applicable to the GBS-R 412 ports. 414 Generation of this notification is controlled by the 415 g9981PortConfDiffDelayToleranceExceededEnable attribute. 417 This object maps to the TR-159 notification 418 nIMADownDiffDelayToleranceExceeded." 419 REFERENCE 420 "[TR-159] 5.5.2.9" 421 ::= { g9981PortNotifications 2 } 423 -- G.Bond/ATM Port group 425 g9981PortConfTable OBJECT-TYPE 426 SYNTAX SEQUENCE OF G9981PortConfEntry 427 MAX-ACCESS not-accessible 428 STATUS current 429 DESCRIPTION 430 "Table for Configuration of G.Bond/ATM ports. Entries in 431 this table MUST be maintained in a persistent manner" 432 ::= { g9981Port 1 } 434 g9981PortConfEntry OBJECT-TYPE 435 SYNTAX G9981PortConfEntry 436 MAX-ACCESS not-accessible 437 STATUS current 438 DESCRIPTION 439 "An entry in the G.Bond/ATM Port Configuration table. 440 Each entry represents a G.Bond/ATM port indexed by the 441 ifIndex. Additional configuration parameters are available 442 via the gBondPortConfEntry of GBOND-MIB. 443 Note that a G.Bond/ATM port runs on top of a single or 444 multiple BCE port(s), which are also indexed by ifIndex." 446 INDEX { ifIndex } 447 ::= { g9981PortConfTable 1 } 449 G9981PortConfEntry ::= 450 SEQUENCE { 451 g9981PortConfUpDiffDelayTolerance MilliSeconds, 452 g9981PortConfDnDiffDelayTolerance MilliSeconds, 453 g9981PortConfDiffDelayToleranceExceededEnable TruthValue 454 } 456 g9981PortConfUpDiffDelayTolerance OBJECT-TYPE 457 SYNTAX MilliSeconds(0..2047) 458 UNITS "milliseconds" 459 MAX-ACCESS read-write 460 STATUS current 461 DESCRIPTION 462 "A maximum tolerated upstream differential delay (among 463 the member BCEs) of a G.Bond/ATM port, expressed in ms. 465 This object is read-write for the GBS-C ports. 466 It is irrelevant for the GBS-R ports - an attempt to read or 467 change this object MUST be rejected (in case of SNMP with the 468 error inconsistentValue). 470 This object maps to TR-159 attribute 471 aIMAUpDiffDelayTolerance" 472 REFERENCE 473 "[TR-159] 5.5.2.5; [G.998.1] 11.4.1 (6)" 474 ::= { g9981PortConfEntry 1 } 476 g9981PortConfDnDiffDelayTolerance OBJECT-TYPE 477 SYNTAX MilliSeconds(0..2047) 478 UNITS "milliseconds" 479 MAX-ACCESS read-write 480 STATUS current 481 DESCRIPTION 482 "A maximum tolerated downstream differential delay (among 483 the member BCEs) of a G.Bond/ATM port, expressed in ms. 485 This object is read-write for the GBS-C ports. 486 It is irrelevant for the GBS-R ports - an attempt to read or 487 change this object MUST be rejected (in case of SNMP with the 488 error inconsistentValue). 490 This object maps to TR-159 attribute 491 aIMADownDiffDelayTolerance" 492 REFERENCE 493 "[TR-159] 5.5.2.6; [G.998.1] 11.4.1 (6)" 495 ::= { g9981PortConfEntry 2 } 497 g9981PortConfDiffDelayToleranceExceededEnable OBJECT-TYPE 498 SYNTAX TruthValue 499 MAX-ACCESS read-write 500 STATUS current 501 DESCRIPTION 502 "Indicates whether g9981UpDiffDelayToleranceExceeded and 503 g9981DnDiffDelayToleranceExceeded notifications should 504 be generated for G.Bond/ATM port. 506 Value of true(1) indicates that the notifications are enabled. 507 Value of false(2) indicates that the notifications are 508 disabled. 510 This object is read-write for the GBS-C. 511 It is irrelevant for the GBS-R ports - an attempt to read or 512 change this object MUST be rejected (in case of SNMP with the 513 error inconsistentValue). 515 This object maps to the TR-159 attribute 516 aIMADiffDelayToleranceExceededEnable." 517 REFERENCE 518 "[TR-159] 5.5.5.7" 519 ::= { g9981PortConfEntry 3 } 521 g9981PortStatTable OBJECT-TYPE 522 SYNTAX SEQUENCE OF G9981PortStatEntry 523 MAX-ACCESS not-accessible 524 STATUS current 525 DESCRIPTION 526 "This table provides overall status information of G.Bond/ATM 527 ports, complementing the generic status information from the 528 ifTable of IF-MIB and gBondFltStatus of GBOND-MIB. 529 Additional status information about connected BCEs is available 530 from the relevant line MIBs. 532 This table contains live data from the equipment. As such, it is 533 NOT persistent." 534 ::= { g9981Port 2 } 536 g9981PortStatEntry OBJECT-TYPE 537 SYNTAX G9981PortStatEntry 538 MAX-ACCESS not-accessible 539 STATUS current 540 DESCRIPTION 541 "An entry in the G.Bond/ATM port Status table. 543 Each entry represents a G.Bond/ATM port indexed by the 544 ifIndex. 545 Note that a GBS port runs on top of a single or multiple BCE 546 port(s), which are also indexed by ifIndex." 547 INDEX { ifIndex } 548 ::= { g9981PortStatTable 1 } 550 G9981PortStatEntry ::= 551 SEQUENCE { 552 g9981PortStatRxLostCells Counter32, 553 g9981PortStatTxLostCells Counter32, 554 g9981PortStatMaxUpDiffDelay Unsigned32, 555 g9981PortStatMaxDnDiffDelay Unsigned32 556 } 558 g9981PortStatRxLostCells OBJECT-TYPE 559 SYNTAX Counter32 560 UNITS "cells" 561 MAX-ACCESS read-only 562 STATUS current 563 DESCRIPTION 564 "The number of lost ATM cells detected by the G.Bond/ATM port 565 in the receive direction, i.e. upstream direction for 566 a GBS-C port. 568 Discontinuities in the value of this counter can occur at 569 re-initialization of the management system, and at other times 570 as indicated by the value of ifCounterDiscontinuityTime, 571 defined in IF-MIB. 573 This object maps to TR-159 attribute aIMARxLostCells." 574 REFERENCE 575 "[TR-159] 5.5.2.1; [G.998.1] 11.4.2 (4)" 576 ::= { g9981PortStatEntry 1 } 578 g9981PortStatTxLostCells OBJECT-TYPE 579 SYNTAX Counter32 580 UNITS "cells" 581 MAX-ACCESS read-only 582 STATUS current 583 DESCRIPTION 584 "The number of lost ATM cells detected by the peer G.Bond/ATM 585 port in the receive direction, e.g. downstream direction for a 586 GBS-C port. 588 This object is irrelevant for the GBS-R ports - an attempt to 589 read it MUST be rejected (in case of SNMP with the error 590 inconsistentValue). 592 Discontinuities in the value of this counter can occur at 593 re-initialization of the management system, and at other times 594 as indicated by the value of ifCounterDiscontinuityTime, 595 defined in IF-MIB. 597 This object maps to TR-159 attribute aIMAPeerRxLostCells." 598 REFERENCE 599 "[TR-159] 5.5.2.1; [G.998.1] 11.4.2 (4)" 600 ::= { g9981PortStatEntry 2 } 602 g9981PortStatMaxUpDiffDelay OBJECT-TYPE 603 SYNTAX Unsigned32 604 UNITS "0.1 ms" 605 MAX-ACCESS read-only 606 STATUS current 607 DESCRIPTION 608 "Current maximum upstream differential delay between all 609 operational BCEs in the G.Bond/ATM bonding group, measured in 610 units of 0.1 ms. 612 This object is read-only for the GBS-C ports. 613 It is irrelevant for the GBS-R ports - an attempt to read this 614 object MUST be rejected (in case of SNMP with the error 615 inconsistentValue). 617 This object maps to TR-159 attribute aIMAMaxUpDiffDelay." 618 REFERENCE 619 "[TR-159] 5.5.2.3" 620 ::= { g9981PortStatEntry 3 } 622 g9981PortStatMaxDnDiffDelay OBJECT-TYPE 623 SYNTAX Unsigned32 624 UNITS "0.1 ms" 625 MAX-ACCESS read-only 626 STATUS current 627 DESCRIPTION 628 "Current maximum downstream differential delay between all 629 operational BCEs in the G.Bond/ATM bonding group, measured in 630 units of 0.1 ms. 632 This object is read-only for the GBS-C ports. 633 It is irrelevant for the GBS-R ports - an attempt to read this 634 object MUST be rejected (in case of SNMP with the error 635 inconsistentValue). 637 This object maps to TR-159 attribute aIMAMaxDownDiffDelay." 638 REFERENCE 639 "[TR-159] 5.5.2.4" 641 ::= { g9981PortStatEntry 4 } 643 ------------------------------- 644 -- Performance Monitoring group 645 ------------------------------- 647 g9981PM OBJECT IDENTIFIER ::= { g9981Port 3 } 649 g9981PortPmCurTable OBJECT-TYPE 650 SYNTAX SEQUENCE OF G9981PortPmCurEntry 651 MAX-ACCESS not-accessible 652 STATUS current 653 DESCRIPTION 654 "This table contains current Performance Monitoring information 655 for a G.Bond/ATM port. This table contains live data from the 656 equipment and as such is NOT persistent." 657 ::= { g9981PM 1 } 659 g9981PortPmCurEntry OBJECT-TYPE 660 SYNTAX G9981PortPmCurEntry 661 MAX-ACCESS not-accessible 662 STATUS current 663 DESCRIPTION 664 "An entry in the G.Bond/ATM Port PM table. 665 Each entry represents a G.Bond/ATM port indexed by the 666 ifIndex." 667 INDEX { ifIndex } 668 ::= { g9981PortPmCurTable 1 } 670 G9981PortPmCurEntry ::= 671 SEQUENCE { 672 g9981PortPmCur15MinValidIntervals HCPerfValidIntervals, 673 g9981PortPmCur15MinInvalidIntervals HCPerfInvalidIntervals, 674 g9981PortPmCur15MinTimeElapsed HCPerfTimeElapsed, 675 g9981PortPmCur15MinRxLostCells HCPerfCurrentCount, 676 g9981PortPmCur15MinTxLostCells HCPerfCurrentCount, 677 g9981PortPmCur15MinUpDiffDelay HCPerfCurrentCount, 678 g9981PortPmCur15MinDnDiffDelay HCPerfCurrentCount, 679 g9981PortPmCur1DayValidIntervals Unsigned32, 680 g9981PortPmCur1DayInvalidIntervals Unsigned32, 681 g9981PortPmCur1DayTimeElapsed HCPerfTimeElapsed, 682 g9981PortPmCur1DayRxLostCells HCPerfCurrentCount, 683 g9981PortPmCur1DayTxLostCells HCPerfCurrentCount, 684 g9981PortPmCur1DayUpDiffDelay HCPerfCurrentCount, 685 g9981PortPmCur1DayDnDiffDelay HCPerfCurrentCount 686 } 688 g9981PortPmCur15MinValidIntervals OBJECT-TYPE 689 SYNTAX HCPerfValidIntervals 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 collected. The value of this object will 695 be 96 or the maximum number of 15-minute history intervals 696 collected by the implementation unless the measurement was 697 (re-)started recently, in which case the value will be the 698 number of complete 15 minutes intervals for which there are at 699 least some data. 700 In certain cases it is possible that some intervals are 701 unavailable. In this case, this object reports the maximum 702 interval number for which data is available. 704 This object partially maps to the TR-159 attribute 705 aGroupPerf15MinValidIntervals." 706 REFERENCE 707 "[TR-159] 5.5.1.32" 708 ::= { g9981PortPmCurEntry 1 } 710 g9981PortPmCur15MinInvalidIntervals OBJECT-TYPE 711 SYNTAX HCPerfInvalidIntervals 712 MAX-ACCESS read-only 713 STATUS current 714 DESCRIPTION 715 "A read-only number of 15-minute intervals for which the 716 performance data was not always available. The value will 717 typically be zero except in cases where the data for some 718 intervals are not available. 720 This object partially maps to the TR-159 attribute 721 aGroupPerf15MinInvalidIntervals." 722 REFERENCE 723 "[TR-159] 5.5.1.33" 724 ::= { g9981PortPmCurEntry 2 } 726 g9981PortPmCur15MinTimeElapsed OBJECT-TYPE 727 SYNTAX HCPerfTimeElapsed 728 UNITS "seconds" 729 MAX-ACCESS read-only 730 STATUS current 731 DESCRIPTION 732 "A read-only count of seconds that have elapsed since the 733 beginning of the current 15-minute performance interval. 735 This object partially maps to the TR-159 attribute 736 aGroupPerfCurr15MinTimeElapsed." 738 REFERENCE 739 "[TR-159] 5.5.1.34" 740 ::= { g9981PortPmCurEntry 3 } 742 g9981PortPmCur15MinRxLostCells OBJECT-TYPE 743 SYNTAX HCPerfCurrentCount 744 UNITS "cells" 745 MAX-ACCESS read-only 746 STATUS current 747 DESCRIPTION 748 "A read-only count of lost ATM cells detected by a G.Bond/ATM 749 port (e.g. GBS-C) in the receive direction, during the current 750 15-minute performance history interval. 752 Note that the total number of lost ATM cells is indicated by the 753 g9981PortStatRxLostCells object. 755 This object is inhibited during Severely Errored Seconds (SES) 756 or Unavailable Seconds (UAS)." 757 REFERENCE 758 "[TR-159] 5.5.2.1" 759 ::= { g9981PortPmCurEntry 4} 761 g9981PortPmCur15MinTxLostCells OBJECT-TYPE 762 SYNTAX HCPerfCurrentCount 763 UNITS "cells" 764 MAX-ACCESS read-only 765 STATUS current 766 DESCRIPTION 767 "A read-only count of lost ATM cells detected by the peer 768 G.Bond/ATM port (e.g. by GBS-R for GBS-C), during the current 769 15-minute performance history interval. 771 Note that the total number of lost ATM cells is indicated by the 772 g9981PortStatTxLostCells object. 774 This object is inhibited during Unavailable Seconds (UAS)." 775 REFERENCE 776 "[TR-159] 5.5.2.2" 777 ::= { g9981PortPmCurEntry 5} 779 g9981PortPmCur15MinUpDiffDelay OBJECT-TYPE 780 SYNTAX HCPerfCurrentCount 781 UNITS "0.1 ms" 782 MAX-ACCESS read-only 783 STATUS current 784 DESCRIPTION 785 "A read-only value specifying maximum upstream differential 786 delay between all operational BCEs in the GBS-C, measured in 787 units of 0.1 ms, during the current 15-minute performance 788 interval. 790 Note that the current max upstream differential delay is 791 indicated by the g9981PortStatMaxUpDiffDelay object. 793 This object is inhibited during Unavailable Seconds (UAS)." 794 REFERENCE 795 "[TR-159] 5.5.2.3" 796 ::= { g9981PortPmCurEntry 6} 798 g9981PortPmCur15MinDnDiffDelay OBJECT-TYPE 799 SYNTAX HCPerfCurrentCount 800 UNITS "0.1 ms" 801 MAX-ACCESS read-only 802 STATUS current 803 DESCRIPTION 804 "A read-only value specifying maximum downstream differential 805 delay between all operational BCEs in the GBS-C (as perceived 806 by GBS-R), measured in units of 0.1 ms, during the current 807 15-minute performance history interval. 809 Note that the current max downstream differential delay is 810 indicated by the g9981PortStatMaxDnDiffDelay object. 812 This object is inhibited during Unavailable Seconds (UAS)." 813 REFERENCE 814 "[TR-159] 5.5.2.4" 815 ::= { g9981PortPmCurEntry 7} 817 g9981PortPmCur1DayValidIntervals OBJECT-TYPE 818 SYNTAX Unsigned32 (0..7) 819 UNITS "days" 820 MAX-ACCESS read-only 821 STATUS current 822 DESCRIPTION 823 "A read-only number of 1-day intervals for which data was 824 collected. The value of this object will be 7 or the maximum 825 number of 1-day history intervals collected by the 826 implementation unless the measurement was (re-)started recently, 827 in which case the value will be the number of complete 1-day 828 intervals for which there are at least some data. 829 In certain cases it is possible that some intervals are 830 unavailable. In this case, this object reports the maximum 831 interval number for which data is available." 832 REFERENCE 833 "[TR-159] 5.5.1.45" 835 ::= { g9981PortPmCurEntry 8 } 837 g9981PortPmCur1DayInvalidIntervals OBJECT-TYPE 838 SYNTAX Unsigned32 (0..7) 839 UNITS "days" 840 MAX-ACCESS read-only 841 STATUS current 842 DESCRIPTION 843 "A read-only number of 1-day intervals for which data was 844 not always available. The value will typically be zero except in 845 cases where the data for some intervals are not available." 846 REFERENCE 847 "[TR-159] 5.5.1.46" 848 ::= { g9981PortPmCurEntry 9 } 850 g9981PortPmCur1DayTimeElapsed OBJECT-TYPE 851 SYNTAX HCPerfTimeElapsed 852 UNITS "seconds" 853 MAX-ACCESS read-only 854 STATUS current 855 DESCRIPTION 856 "A read-only count of seconds that have elapsed since the 857 beginning of the current 1-day performance interval." 858 REFERENCE 859 "[TR-159] 5.5.1.47" 860 ::= { g9981PortPmCurEntry 10 } 862 g9981PortPmCur1DayRxLostCells OBJECT-TYPE 863 SYNTAX HCPerfCurrentCount 864 UNITS "cells" 865 MAX-ACCESS read-only 866 STATUS current 867 DESCRIPTION 868 "A read-only count of lost ATM cells detected by the G.Bond/ATM 869 port (e.g. GBS-C), during the current 1-day performance 870 interval. 872 This object is inhibited during Severely Errored Seconds (SES) 873 and Unavailable Seconds (UAS)." 874 ::= { g9981PortPmCurEntry 11 } 876 g9981PortPmCur1DayTxLostCells OBJECT-TYPE 877 SYNTAX HCPerfCurrentCount 878 UNITS "cells" 879 MAX-ACCESS read-only 880 STATUS current 881 DESCRIPTION 882 "A read-only count of lost ATM cells detected by the peer 883 G.Bond/ATM port (e.g. by GBS-R for GBS-C), during the current 884 1-day performance history interval. 886 This object is inhibited during Unavailable Seconds (UAS)." 887 ::= { g9981PortPmCurEntry 12 } 889 g9981PortPmCur1DayUpDiffDelay OBJECT-TYPE 890 SYNTAX HCPerfCurrentCount 891 UNITS "0.1 ms" 892 MAX-ACCESS read-only 893 STATUS current 894 DESCRIPTION 895 "A read-only value specifying maximum upstream differential 896 delay between all operational BCEs in the GBS-C, measured in 897 units of 0.1 ms, during the current 1-day performance 898 interval. 900 This object is inhibited during Unavailable Seconds (UAS)." 901 ::= { g9981PortPmCurEntry 13 } 903 g9981PortPmCur1DayDnDiffDelay OBJECT-TYPE 904 SYNTAX HCPerfCurrentCount 905 UNITS "0.1 ms" 906 MAX-ACCESS read-only 907 STATUS current 908 DESCRIPTION 909 "A read-only value specifying maximum downstream differential 910 delay between all operational BCEs in the GBS-C, measured in 911 units of 0.1 ms, during the current 1-day performance 912 interval. 914 This object is inhibited during Unavailable Seconds (UAS)." 915 ::= { g9981PortPmCurEntry 14 } 917 -- Port PM history: 15-min buckets 919 g9981PortPm15MinTable OBJECT-TYPE 920 SYNTAX SEQUENCE OF G9981PortPm15MinEntry 921 MAX-ACCESS not-accessible 922 STATUS current 923 DESCRIPTION 924 "This table contains historical 15-minute buckets of Performance 925 Monitoring information for a G.Bond/ATM port (a row for each 926 15-minute interval, up to 96 intervals). 927 Entries in this table MUST be maintained in a persistent manner." 928 ::= { g9981PM 2 } 930 g9981PortPm15MinEntry OBJECT-TYPE 931 SYNTAX G9981PortPm15MinEntry 932 MAX-ACCESS not-accessible 933 STATUS current 934 DESCRIPTION 935 "An entry in the G.Bond/ATM Port historical 15-minute PM table. 936 Each entry represents performance monitoring data for a 937 G.Bond/ATM port, indexed by ifIndex, collected during a 938 particular 15-minute interval, indexed by 939 g9981PortPm15MinIntervalIndex." 940 INDEX { ifIndex, g9981PortPm15MinIntervalIndex } 941 ::= { g9981PortPm15MinTable 1 } 943 G9981PortPm15MinEntry ::= 944 SEQUENCE { 945 g9981PortPm15MinIntervalIndex Unsigned32, 946 g9981PortPm15MinIntervalMoniTime HCPerfTimeElapsed, 947 g9981PortPm15MinIntervalRxLostCells HCPerfIntervalCount, 948 g9981PortPm15MinIntervalTxLostCells HCPerfIntervalCount, 949 g9981PortPm15MinIntervalUpDiffDelay HCPerfIntervalCount, 950 g9981PortPm15MinIntervalDnDiffDelay HCPerfIntervalCount, 951 g9981PortPm15MinIntervalValid TruthValue 952 } 954 g9981PortPm15MinIntervalIndex OBJECT-TYPE 955 SYNTAX Unsigned32 (1..96) 956 MAX-ACCESS not-accessible 957 STATUS current 958 DESCRIPTION 959 "Performance Data Interval number. 1 is the most recent previous 960 interval; interval 96 is 24 hours ago. 961 Intervals 2..96 are OPTIONAL. 963 This object partially maps to the TR-159 attribute 964 aGroupPerf15MinIntervalNumber." 965 REFERENCE 966 "[TR-159] 5.5.1.57" 967 ::= { g9981PortPm15MinEntry 1 } 969 g9981PortPm15MinIntervalMoniTime OBJECT-TYPE 970 SYNTAX HCPerfTimeElapsed 971 UNITS "seconds" 972 MAX-ACCESS read-only 973 STATUS current 974 DESCRIPTION 975 "A read-only count of seconds over which the performance data 976 was actually monitored. This value will be the same as the 977 interval duration (900 seconds), except in a situation where 978 performance data could not be collected for any reason." 980 ::= { g9981PortPm15MinEntry 2 } 982 g9981PortPm15MinIntervalRxLostCells OBJECT-TYPE 983 SYNTAX HCPerfIntervalCount 984 UNITS "cells" 985 MAX-ACCESS read-only 986 STATUS current 987 DESCRIPTION 988 "A read-only count of lost ATM cells detected by a G.Bond/ATM 989 port (e.g. GBS-C) in the receive direction, during the 990 15-minute performance history interval. 992 Note that the total number of lost ATM cells is indicated by the 993 g9981PortStatRxLostCells object. 995 This object is inhibited during Severely Errored Seconds (SES) 996 or Unavailable Seconds (UAS)." 997 REFERENCE 998 "[TR-159] 5.5.2.1" 999 ::= { g9981PortPm15MinEntry 3 } 1001 g9981PortPm15MinIntervalTxLostCells OBJECT-TYPE 1002 SYNTAX HCPerfIntervalCount 1003 UNITS "cells" 1004 MAX-ACCESS read-only 1005 STATUS current 1006 DESCRIPTION 1007 "A read-only count of lost ATM cells detected by the peer 1008 G.Bond/ATM port (e.g. by GBS-R for GBS-C), during the 15-minute 1009 performance history interval. 1011 Note that the total number of lost ATM cells is indicated by the 1012 g9981PortStatTxLostCells object. 1014 This object is inhibited during Unavailable Seconds (UAS)." 1015 REFERENCE 1016 "[TR-159] 5.5.2.2" 1017 ::= { g9981PortPm15MinEntry 4 } 1019 g9981PortPm15MinIntervalUpDiffDelay OBJECT-TYPE 1020 SYNTAX HCPerfIntervalCount 1021 UNITS "0.1 ms" 1022 MAX-ACCESS read-only 1023 STATUS current 1024 DESCRIPTION 1025 "A read-only value specifying maximum upstream differential 1026 delay between all operational BCEs in the GBS, measured in 1027 units of 0.1 ms, during the 15-minute performance history 1028 interval. 1030 Note that the current max upstream differential delay is 1031 indicated by the g9981PortStatMaxUpDiffDelay object. 1033 This object is inhibited during Unavailable Seconds (UAS)." 1034 REFERENCE 1035 "[TR-159] 5.5.2.3" 1036 ::= { g9981PortPm15MinEntry 5 } 1038 g9981PortPm15MinIntervalDnDiffDelay OBJECT-TYPE 1039 SYNTAX HCPerfIntervalCount 1040 UNITS "0.1 ms" 1041 MAX-ACCESS read-only 1042 STATUS current 1043 DESCRIPTION 1044 "A read-only value specifying maximum downstream differential 1045 delay between all operational BCEs in the GBS, as perceived by 1046 its peer port, measured in units of 0.1 ms, during the 1047 15-minute performance history interval. 1049 Note that the current max upstream differential delay is 1050 indicated by the g9981PortStatMaxDnDiffDelay object. 1052 This object is inhibited during Unavailable Seconds (UAS)." 1053 REFERENCE 1054 "[TR-159] 5.5.2.4" 1055 ::= { g9981PortPm15MinEntry 6 } 1057 g9981PortPm15MinIntervalValid OBJECT-TYPE 1058 SYNTAX TruthValue 1059 MAX-ACCESS read-only 1060 STATUS current 1061 DESCRIPTION 1062 "A read-only object indicating whether or not this history 1063 bucket contains valid data. Valid bucket is reported as true(1) 1064 and invalid bucket as false(2). 1065 If this history bucket is invalid the BTU MUST NOT produce 1066 notifications based upon the value of the counters in this 1067 bucket. 1068 Note that an implementation may decide not to store invalid 1069 history buckets in its data base. In such case this object is 1070 not required as only valid history buckets are available while 1071 invalid history buckets are simply not in the data base. 1073 This object partially maps to the TR-159 attribute 1074 aGroupPerf15MinIntervalValid." 1075 REFERENCE 1076 "[TR-159] 5.5.1.58" 1077 ::= { g9981PortPm15MinEntry 7 } 1079 -- Port PM history: 1-day buckets 1081 g9981PortPm1DayTable OBJECT-TYPE 1082 SYNTAX SEQUENCE OF G9981PortPm1DayEntry 1083 MAX-ACCESS not-accessible 1084 STATUS current 1085 DESCRIPTION 1086 "This table contains historical 1-day buckets of Performance 1087 Monitoring information for a G.Bond/ATM port (a row for each 1088 1-day interval, up to 7 intervals). 1089 Entries in this table MUST be maintained in a persistent manner." 1090 ::= { g9981PM 3 } 1092 g9981PortPm1DayEntry OBJECT-TYPE 1093 SYNTAX G9981PortPm1DayEntry 1094 MAX-ACCESS not-accessible 1095 STATUS current 1096 DESCRIPTION 1097 "An entry in the G.Bond/ATM port historical 1-day PM table. 1098 Each entry represents performance monitoring data for such port, 1099 indexed by ifIndex, collected during a particular 1-day 1100 interval, indexed by g9981PortPm1DayIntervalIndex." 1101 INDEX { ifIndex, g9981PortPm1DayIntervalIndex } 1102 ::= { g9981PortPm1DayTable 1 } 1104 G9981PortPm1DayEntry ::= 1105 SEQUENCE { 1106 g9981PortPm1DayIntervalIndex Unsigned32, 1107 g9981PortPm1DayIntervalMoniTime HCPerfTimeElapsed, 1108 g9981PortPm1DayIntervalRxLostCells HCPerfIntervalCount, 1109 g9981PortPm1DayIntervalTxLostCells HCPerfIntervalCount, 1110 g9981PortPm1DayIntervalUpDiffDelay HCPerfIntervalCount, 1111 g9981PortPm1DayIntervalDnDiffDelay HCPerfIntervalCount, 1112 g9981PortPm1DayIntervalValid TruthValue 1113 } 1115 g9981PortPm1DayIntervalIndex OBJECT-TYPE 1116 SYNTAX Unsigned32 (1..7) 1117 MAX-ACCESS not-accessible 1118 STATUS current 1119 DESCRIPTION 1120 "Performance Data Interval number. 1 is the most recent previous 1121 interval; interval 7 is 24 hours ago. 1122 Intervals 2..7 are OPTIONAL. 1124 This object partially maps to the TR-159 attribute 1125 aGroupPerf1DayIntervalNumber." 1126 REFERENCE 1127 "[TR-159] 5.5.1.62" 1128 ::= { g9981PortPm1DayEntry 1 } 1130 g9981PortPm1DayIntervalMoniTime OBJECT-TYPE 1131 SYNTAX HCPerfTimeElapsed 1132 UNITS "seconds" 1133 MAX-ACCESS read-only 1134 STATUS current 1135 DESCRIPTION 1136 "A count of seconds over which the performance data was actually 1137 monitored. This value will be the same as the interval duration 1138 (86400 seconds), except in a situation where performance data 1139 could not be collected for any reason. 1141 This object partially maps to the TR-159 attribute 1142 aGroupPerf1DayIntervalMoniSecs." 1143 REFERENCE 1144 "[TR-159] 5.5.1.64" 1145 ::= { g9981PortPm1DayEntry 2 } 1147 g9981PortPm1DayIntervalRxLostCells OBJECT-TYPE 1148 SYNTAX HCPerfIntervalCount 1149 UNITS "cells" 1150 MAX-ACCESS read-only 1151 STATUS current 1152 DESCRIPTION 1153 "A count of lost ATM cells detected by the G.Bond/ATM port 1154 (e.g. GBS-C), during the 1-day performance history interval. 1156 This object is inhibited during Severely Errored Seconds (SES) 1157 and Unavailable Seconds (UAS)." 1158 ::= { g9981PortPm1DayEntry 3 } 1160 g9981PortPm1DayIntervalTxLostCells OBJECT-TYPE 1161 SYNTAX HCPerfIntervalCount 1162 UNITS "cells" 1163 MAX-ACCESS read-only 1164 STATUS current 1165 DESCRIPTION 1166 "A count of lost ATM cells detected by the peer G.Bond/ATM port 1167 (e.g. by GBS-R for GBS-C), during the 1-day performance history 1168 interval. 1170 This object is inhibited during Unavailable Seconds (UAS)." 1171 ::= { g9981PortPm1DayEntry 4 } 1173 g9981PortPm1DayIntervalUpDiffDelay OBJECT-TYPE 1174 SYNTAX HCPerfIntervalCount 1175 UNITS "0.1 ms" 1176 MAX-ACCESS read-only 1177 STATUS current 1178 DESCRIPTION 1179 "A read-only value specifying maximum upstream differential 1180 delay between all operational BCEs in the GBS-C, measured in 1181 units of 0.1 ms, during the 1-day performance history interval. 1183 This object is inhibited during Unavailable Seconds (UAS)." 1184 ::= { g9981PortPm1DayEntry 5 } 1186 g9981PortPm1DayIntervalDnDiffDelay OBJECT-TYPE 1187 SYNTAX HCPerfIntervalCount 1188 UNITS "0.1 ms" 1189 MAX-ACCESS read-only 1190 STATUS current 1191 DESCRIPTION 1192 "A read-only value specifying maximum downstream differential 1193 delay between all operational BCEs in the GBS-C, measured in 1194 units of 0.1 ms, during the 1-day performance history interval. 1196 This object is inhibited during Unavailable Seconds (UAS)." 1197 ::= { g9981PortPm1DayEntry 6 } 1199 g9981PortPm1DayIntervalValid OBJECT-TYPE 1200 SYNTAX TruthValue 1201 MAX-ACCESS read-only 1202 STATUS current 1203 DESCRIPTION 1204 "A read-only object indicating whether or not this history 1205 bucket contains valid data. Valid bucket is reported as true(1) 1206 and invalid bucket as false(2). 1207 If this history bucket is invalid the BTU MUST NOT produce 1208 notifications based upon the value of the counters in this 1209 bucket. 1210 Note that an implementation may decide not to store invalid 1211 history buckets in its data base. In such case this object is 1212 not required as only valid history buckets are available while 1213 invalid history buckets are simply not in the data base. 1215 This object partially maps to the TR-159 attribute 1216 aGroupPerf1DayIntervalValid." 1217 REFERENCE 1218 "[TR-159] 5.5.1.63" 1219 ::= { g9981PortPm1DayEntry 7 } 1221 -- 1222 -- Conformance Statements 1223 -- 1225 g9981Groups OBJECT IDENTIFIER 1226 ::= { g9981Conformance 1 } 1228 g9981Compliances OBJECT IDENTIFIER 1229 ::= { g9981Conformance 2 } 1231 -- Object Groups 1233 g9981BasicGroup OBJECT-GROUP 1234 OBJECTS { 1235 g9981PortStatRxLostCells, 1236 g9981PortStatTxLostCells, 1237 g9981PortStatMaxUpDiffDelay, 1238 g9981PortStatMaxDnDiffDelay 1239 } 1240 STATUS current 1241 DESCRIPTION 1242 "A collection of objects representing management information 1243 for a G.Bond/ATM port." 1244 ::= { g9981Groups 1 } 1246 g9981AlarmConfGroup OBJECT-GROUP 1247 OBJECTS { 1248 g9981PortConfUpDiffDelayTolerance, 1249 g9981PortConfDnDiffDelayTolerance, 1250 g9981PortConfDiffDelayToleranceExceededEnable 1251 } 1252 STATUS current 1253 DESCRIPTION 1254 "A collection of objects required for configuration of alarm 1255 thresholds and notifications in G.Bond/ATM ports." 1256 ::= { g9981Groups 2 } 1258 g9981NotificationGroup NOTIFICATION-GROUP 1259 NOTIFICATIONS { 1260 g9981UpDiffDelayToleranceExceeded, 1261 g9981DnDiffDelayToleranceExceeded 1262 } 1263 STATUS current 1264 DESCRIPTION 1265 "This group supports notifications of significant conditions 1266 associated with G.Bond/ATM ports." 1267 ::= { g9981Groups 3 } 1269 g9981PerfCurrGroup OBJECT-GROUP 1270 OBJECTS { 1271 g9981PortPmCur15MinValidIntervals, 1272 g9981PortPmCur15MinInvalidIntervals, 1273 g9981PortPmCur15MinTimeElapsed, 1274 g9981PortPmCur15MinRxLostCells, 1275 g9981PortPmCur15MinTxLostCells, 1276 g9981PortPmCur15MinUpDiffDelay, 1277 g9981PortPmCur15MinDnDiffDelay, 1278 g9981PortPmCur1DayValidIntervals, 1279 g9981PortPmCur1DayInvalidIntervals, 1280 g9981PortPmCur1DayTimeElapsed, 1281 g9981PortPmCur1DayRxLostCells, 1282 g9981PortPmCur1DayTxLostCells, 1283 g9981PortPmCur1DayUpDiffDelay, 1284 g9981PortPmCur1DayDnDiffDelay 1285 } 1286 STATUS current 1287 DESCRIPTION 1288 "A collection of objects supporting OPTIONAL current Performance 1289 Monitoring information for G.Bond/ATM ports." 1290 ::= { g9981Groups 4 } 1292 g9981Perf15MinGroup OBJECT-GROUP 1293 OBJECTS { 1294 g9981PortPm15MinIntervalMoniTime, 1295 g9981PortPm15MinIntervalRxLostCells, 1296 g9981PortPm15MinIntervalTxLostCells, 1297 g9981PortPm15MinIntervalUpDiffDelay, 1298 g9981PortPm15MinIntervalDnDiffDelay, 1299 g9981PortPm15MinIntervalValid 1300 } 1301 STATUS current 1302 DESCRIPTION 1303 "A collection of objects supporting OPTIONAL historical 1304 Performance Monitoring information for G.Bond/ATM ports, during 1305 previous 15-minute intervals ." 1306 ::= { g9981Groups 5 } 1308 g9981Perf1DayGroup OBJECT-GROUP 1309 OBJECTS { 1310 g9981PortPm1DayIntervalMoniTime, 1311 g9981PortPm1DayIntervalRxLostCells, 1312 g9981PortPm1DayIntervalTxLostCells, 1313 g9981PortPm1DayIntervalUpDiffDelay, 1314 g9981PortPm1DayIntervalDnDiffDelay, 1315 g9981PortPm1DayIntervalValid 1316 } 1317 STATUS current 1318 DESCRIPTION 1319 "A collection of objects supporting OPTIONAL historical 1320 Performance Monitoring information for G.Bond/ATM ports, during 1321 previous 1-day intervals ." 1322 ::= { g9981Groups 6 } 1324 -- Compliance Statements 1326 g9981Compliance MODULE-COMPLIANCE 1327 STATUS current 1328 DESCRIPTION 1329 "The compliance statement for G.Bond/ATM interfaces. 1330 Compliance with the following external compliance statements 1331 is REQUIRED: 1333 MIB Module Compliance Statement 1334 ---------- -------------------- 1335 IF-MIB ifCompliance3 1336 GBOND-MIB gBondCompliance" 1338 MODULE -- this module 1339 MANDATORY-GROUPS { 1340 g9981BasicGroup, 1341 g9981AlarmConfGroup, 1342 g9981NotificationGroup 1343 } 1345 GROUP g9981PerfCurrGroup 1346 DESCRIPTION 1347 "Support for this group is only required for implementations 1348 supporting Performance Monitoring." 1350 GROUP g9981Perf15MinGroup 1351 DESCRIPTION 1352 "Support for this group is only required for implementations 1353 supporting historical Performance Monitoring." 1355 GROUP g9981Perf1DayGroup 1356 DESCRIPTION 1357 "Support for this group is only required for implementations 1358 supporting 1-day historical Performance Monitoring." 1360 ::= { g9981Compliances 1 } 1361 END 1362 7. Security Considerations 1364 There is a number of managed objects defined in this MIB module with 1365 a MAX-ACCESS clause of read-write. Such objects may be considered 1366 sensitive or vulnerable in some network environments. The support 1367 for SET operations in a non-secure environment without proper 1368 protection can have a negative effect on network operations. These 1369 are the tables and objects and their sensitivity/vulnerability: 1371 o Changing of g9981PortConfTable configuration parameters MAY lead 1372 to a potential Service Level Agreement (SLA) breach, for example 1373 if a traffic delay is increased as a result of the higher delay 1374 tolerance (increased g9981PortConfUpDiffDelayTolerance and/or 1375 g9981PortConfDnDiffDelayTolerance), or the differential delay 1376 tolerance notifications are disabled by manipulating the 1377 g9981PortConfDiffDelayToleranceExceededEnable parameter. 1379 Some of the readable objects in this MIB module (i.e., those with 1380 MAX-ACCESS other than not-accessible) may be considered sensitive or 1381 vulnerable in some network environments since, collectively, they 1382 provide information about the performance of network interfaces and 1383 can reveal some aspects of their configuration. 1385 It is thus important to control even GET and/or NOTIFY access to 1386 these objects and possibly even encrypt the values of these objects 1387 when sending them over the network via SNMP. 1389 SNMP versions prior to SNMPv3 did not include adequate security. 1390 Even if the network itself is secure (for example by using IPSec), 1391 there is no control as to who on the secure network is allowed to 1392 access and GET/SET (read/change/create/delete) the objects in this 1393 MIB module. 1395 Implementations MUST provide the security features described by the 1396 SNMPv3 framework (see [RFC3410]), including full support for 1397 authentication and privacy via the User-based Security Model (USM) 1398 [RFC3414] with the AES cipher algorithm [RFC3826]. Implementations 1399 MAY also provide support for the Transport Security Model (TSM) 1400 [RFC5591] in combination with a secure transport such as SSH 1401 [RFC5592] or TLS/DTLS [RFC6353]. 1403 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1404 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1405 enable cryptographic security. It is then a customer/operator 1406 responsibility to ensure that the SNMP entity giving access to an 1407 instance of this MIB module is properly configured to give access to 1408 the objects only to those principals (users) that have legitimate 1409 rights to indeed GET or SET (change/create/delete) them. 1411 8. IANA Considerations 1413 An object identifier for g9981MIB MODULE-IDENTITY SHALL be allocated 1414 by IANA [1] in the MIB-2 transmission sub-tree, before this document 1415 is published as an RFC. 1417 9. Acknowledgments 1419 This document was produced by the [ADSLMIB] working group. 1421 Special thanks to Dan Romascanu for his meticulous review of this 1422 text. 1424 10. References 1426 10.1. Normative References 1428 [G.998.1] ITU-T, "ATM-based multi-pair bonding", 1429 ITU-T Recommendation G.998.3, 1430 January 2005. 1432 [I-D.ietf-adslmib-gbond-mib] Beili, E. and M. Morgenstern, "xDSL 1433 multi-pair bonding (G.Bond) MIB", 1434 draft-ietf-adslmib-gbond-mib-10 (work 1435 in progress), March 2012. 1437 [RFC2119] Bradner, S., "Key words for use in RFCs 1438 to Indicate Requirement Levels", 1439 BCP 14, RFC 2119, March 1997. 1441 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., 1442 and J. Schoenwaelder, Ed., "Structure 1443 of Management Information Version 2 1444 (SMIv2)", STD 58, RFC 2578, April 1999. 1446 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., 1447 and J. Schoenwaelder, Ed., "Textual 1448 Conventions for SMIv2", STD 58, 1449 RFC 2579, April 1999. 1451 [RFC2580] McCloghrie, K., Perkins, D., and J. 1452 Schoenwaelder, "Conformance Statements 1453 for SMIv2", STD 58, RFC 2580, 1454 April 1999. 1456 [RFC2863] McCloghrie, K. and F. Kastenholz, "The 1457 Interfaces Group MIB", RFC 2863, 1458 June 2000. 1460 [RFC3414] Blumenthal, U. and B. Wijnen, "User- 1461 based Security Model (USM) for version 1462 3 of the Simple Network Management 1463 Protocol (SNMPv3)", STD 62, RFC 3414, 1464 December 2002. 1466 [RFC3705] Ray, B. and R. Abbi, "High Capacity 1467 Textual Conventions for MIB Modules 1468 Using Performance History Based on 15 1469 Minute Intervals", RFC 3705, 1470 February 2004. 1472 [RFC3826] Blumenthal, U., Maino, F., and K. 1473 McCloghrie, "The Advanced Encryption 1474 Standard (AES) Cipher Algorithm in the 1475 SNMP User-based Security Model", 1476 RFC 3826, June 2004. 1478 [TR-159] Beili, E. and M. Morgenstern, 1479 "Management Framework for xDSL 1480 Bonding", Broadband Forum technical 1481 report TR-159, December 2008. 1483 10.2. Informative References 1485 [ADSLMIB] IETF, "ADSL MIB (adslmib) Charter", . 1489 [RFC2515] Tesink, K., "Definitions of Managed 1490 Objects for ATM Management", RFC 2515, 1491 February 1999. 1493 [RFC3410] Case, J., Mundy, R., Partain, D., and 1494 B. Stewart, "Introduction and 1495 Applicability Statements for Internet- 1496 Standard Management Framework", 1497 RFC 3410, December 2002. 1499 [RFC3593] Tesink, K., "Textual Conventions for 1500 MIB Modules Using Performance History 1501 Based on 15 Minute Intervals", 1502 RFC 3593, September 2003. 1504 [RFC4181] Heard, C., "Guidelines for Authors and 1505 Reviewers of MIB Documents", BCP 111, 1506 RFC 4181, September 2005. 1508 [RFC5591] Harrington, D. and W. Hardaker, 1509 "Transport Security Model for the 1510 Simple Network Management Protocol 1511 (SNMP)", RFC 5591, June 2009. 1513 [RFC5592] Harrington, D., Salowey, J., and W. 1514 Hardaker, "Secure Shell Transport Model 1515 for the Simple Network Management 1516 Protocol (SNMP)", RFC 5592, June 2009. 1518 [RFC6353] Hardaker, W., "Transport Layer Security 1519 (TLS) Transport Model for the Simple 1520 Network Management Protocol (SNMP)", 1521 RFC 6353, July 2011. 1523 [af-phy-0086] ATM Forum, "Inverse Multiplexing for 1524 ATM (IMA) Specification Version 1.1", 1525 ATM Forum specification af-pfy- 1526 0086.001, March 1999. 1528 URIs 1530 [1] 1532 Author's Address 1534 Edward Beili 1535 Actelis Networks 1536 25 Bazel St. 1537 Petach-Tikva 49103 1538 Israel 1540 Phone: +972-3-924-3491 1541 EMail: edward.beili@actelis.com