idnits 2.17.1 draft-ietf-adslmib-adslext-08.txt: ** The Abstract section seems to be numbered Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 1) being 1740 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Abstract section. (A line matching the expected section header was found, but with an unexpected indentation: ' 2. Abstract' ) ** The document seems to lack an Introduction section. ** The document seems to lack a Security Considerations section. (A line matching the expected section header was found, but with an unexpected indentation: ' 11. Security Considerations' ) ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack an Authors' Addresses Section. ** There are 114 instances of too long lines in the document, the longest one being 8 characters in excess of 72. ** The abstract seems to contain references ([RFC2573], [RFC1906], [RFC1155], [21], [RFC2574], [RFC2575], [RFC1157], [RFC2580], [23], [RFC2026], [RFC2863], [RFC2028], [ITUG992.1], [RFC2578], [RFC1212], [RFC1213], [RFC2579], [RFC1901], [RFC1215], [ITUG.992.1], [RFC2662], [ITUG.992.2], [ITUG.997.1], [RFC2570], [RFC2571], [RFC1905], [RFC2572]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 1115 has weird spacing: '...eshTrap notif...' -- 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 (August 1, 2001) is 8304 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 section? 'RFC2662' on line 1503 looks like a reference -- Missing reference section? 'RFC2571' on line 1471 looks like a reference -- Missing reference section? 'RFC1155' on line 1432 looks like a reference -- Missing reference section? 'RFC1212' on line 1439 looks like a reference -- Missing reference section? 'RFC1215' on line 1446 looks like a reference -- Missing reference section? 'RFC2578' on line 1490 looks like a reference -- Missing reference section? 'RFC2579' on line 1495 looks like a reference -- Missing reference section? 'RFC2580' on line 1499 looks like a reference -- Missing reference section? 'RFC1157' on line 1436 looks like a reference -- Missing reference section? 'RFC1901' on line 1449 looks like a reference -- Missing reference section? 'RFC1906' on line 1457 looks like a reference -- Missing reference section? 'RFC2572' on line 1475 looks like a reference -- Missing reference section? 'RFC2574' on line 1482 looks like a reference -- Missing reference section? 'RFC1905' on line 1453 looks like a reference -- Missing reference section? 'RFC2573' on line 1479 looks like a reference -- Missing reference section? 'RFC2575' on line 1486 looks like a reference -- Missing reference section? 'RFC2570' on line 1467 looks like a reference -- Missing reference section? 'ITU G.997.1' on line 1428 looks like a reference -- Missing reference section? 'ITU G.992.1' on line 1420 looks like a reference -- Missing reference section? 'ITU G.992.2' on line 1424 looks like a reference -- Missing reference section? 'ITU G992.1' on line 159 looks like a reference -- Missing reference section? 'RFC 2662' on line 934 looks like a reference -- Missing reference section? 'RFC1213' on line 1442 looks like a reference -- Missing reference section? 'RFC2026' on line 1461 looks like a reference -- Missing reference section? 'RFC2028' on line 1464 looks like a reference -- Missing reference section? 'RFC2863' on line 1506 looks like a reference -- Missing reference section? '21' on line 1538 looks like a reference -- Missing reference section? '23' on line 1539 looks like a reference Summary: 11 errors (**), 0 flaws (~~), 4 warnings (==), 30 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 INTERNET-DRAFT ADSL Line Extension MIB Faye Ly 2 Salira Optical Systems 3 Gregory Bathrick 4 Nokia 5 August 1, 2001 7 Definitions of Extension Managed Objects 8 for ADSL Lines 10 August 1, 2001 12 draft-ietf-adslmib-adslext-08.txt 14 1. Status of this Memo 16 This document is an Internet-Draft and is in full conformance with 17 all provisions of Section 10 of RFC2026. 19 Internet-Drafts are working documents of the Internet Engineering 20 Task Force (IETF), its areas, and its working groups. Note that other 21 groups may also distribute working documents as Internet-Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six months 24 and may be updated, replaced, or obsoleted by other documents at any 25 time. It is inappropriate to use Internet-Drafts as reference 26 material or to cite them other than as ``work in progress.'' 28 The list of current Internet-Drafts can be accessed at 29 http://www.ietf.org/1id-abstracts.html 31 The list of Internet-Draft Shadow Directories can be accessed at 32 http://www.ietf.org/shadow.html. 34 Copyright Notice 36 Copyright (C) The Internet Society (2000). All Rights Reserved. 38 2. Abstract 40 This memo defines a portion of the Management Information Base (MIB) 41 for use with network management protocols in the Internet community. 42 In particular, it describes additional managed objects used for 43 managing Asymmetric Digital Subscriber Line (ADSL) interfaces not 44 covered by the ADSL Line MIB [RFC2662]. 46 3. The SNMP Network Management Framework 48 The SNMP Management Framework presently consists of five major 49 components: An overall architecture, described in RFC 2571 50 [RFC2571]. Mechanisms for describing and naming objects and events 51 for the purpose of management. The first version of this Structure 52 of Management Information (SMI) is called SMIv1 and described in STD 53 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 1215 54 [RFC1215]. The second version, called SMIv2, is described in STD 58, 55 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 56 [RFC2580]. Message protocols for transferring management 57 information. The first version of the SNMP message protocol is 58 called SNMPv1 and described in STD 15, RFC 1157 [RFC1157]. A second 59 version of the SNMP message protocol, which is not an Internet 60 standards track protocol, is called SNMPv2c and described in RFC 1901 61 [RFC1901] and RFC 1906 [RFC1906]. The third version of the message 62 protocol is called SNMPv3 and described in RFC 1906 [RFC1906], RFC 63 2572 [RFC2572] and RFC 2574 [RFC2574]. Protocol operations for 64 accessing management information. The first set of protocol 65 operations and associated PDU formats is described in STD 15, RFC 66 1157 [RFC1157]. A second set of protocol operations and associated 67 PDU formats is described in RFC 1905 [RFC1905]. A set of fundamental 68 applications described in RFC 2573 [RFC2573] and the view-based 69 access control mechanism described in RFC 2575 [RFC2575]. 71 A more detailed introduction to the current SNMP Management Framework 72 can be found in RFC 2570 [RFC2570]. 74 Managed objects are accessed via a virtual information store, termed 75 the Management Information Base or MIB. Objects in the MIB are 76 defined using the mechanisms defined in the SMI. 78 This memo specifies a MIB module that is compliant to the SMIv2. A 79 MIB conforming to the SMIv1 can be produced through the appropriate 80 translations. The resulting translated MIB must be semantically 81 equivalent, except where objects or events are omitted because no 82 translation is possible (use of Counter64). Some machine-readable 83 information in SMIv2 will be converted into textual descriptions in 84 SMIv1 during the translation process. However, this loss of machine 85 readable information is not considered to change the semantics of the 86 MIB. 88 4. Introduction 90 The purpose of this memo is to define a supplemental set of managed 91 objects that is not covered by ADSL Line MIB as defined in [RFC2662]. 92 This memo addresses the additional objects defined in ITU G.997.1 93 [ITU G.997.1]. These additional objects specifically address the 94 management 96 5. Relationship of ADSL Line Extension MIB with standard MIBs 98 This section outlines the relationship of ADSL Line Extension MIB 99 with other MIBs described in RFCs and in their various degrees 100 of standardization. In regards to these relationship, the ADSL Line 101 Extension MIB follows conventions as used by the ADSL Line MIB with few 102 Exceptions as listed below. 104 5.1 ifOperStatus 106 The value of RFC 1213 object, ifOperstatus, shall be down(2) when the 107 ADSL line interface is in power state L3 as defined in ITU G.992.1 108 [ITU G.992.1], which means no power. Its value shall be up(1) if the 109 ADSL line interface is in power state L0 (power on) [ITU G.992.1] 110 or L1 (reduced power). Power Status L2 [ITU G.992.1] is not applicable. 112 6. Conventions used in the MIB 114 6.1 Structure 116 The MIB is organized to follow the same structure of the ADSL Line 117 MIB [RFC2662]. 119 6.2 Additional Managed Objects 121 Objects specific to the management of ADSL G.Lite as defined in 122 ITU G.992.2 [ITU G.992.2] are: 124 - ADSL Transceiver Unit - Central Office End (ATU-C) 125 Transmission System and Line Mode 126 - Power Management 127 - Counters for Fast Retrains and Failed Fast Retrains 128 - Counters for Severe Error Second-line and Unavailable Second 129 - Alternative profile configuration for the Dual line mode interface 131 Besides the management of G.Lite, another object has been added in order 132 to manage the ADSL line profile. The object is the line mode 133 configuration. 135 6.2.1 ATU-C ADSL Transmission System Parameters and Line Mode 137 The adslLineConfigTable needs to be extended to cover control of the 138 ATU-C ADSL Transmission system. Three objects are defined to monitor 139 and configure the transmission mode as well as the actual line mode: 141 - Capability 142 - Configuration 143 - Actual Status 145 Transmission modes can further determine the line mode of the ADSL 146 interface. For example, if g9921PotsNonOverlapped(2) is the actual 147 value of the ADSL interface, the interface is operating in Full rate 148 ADSL. If the interface is set to g9922PotsOverlapped(9), the 149 interface is operating in G.Lite mode. 151 The transmission mode and the corresponding line mode are defined as: 153 Transmission mode Line Mode 154 ---------------------------------------------------------- 155 Regional Std. (ANSI T1.413) Full 156 [ANSI T1.413] 157 Regional Std. (ETSI DTS/TM06006) Full 158 [ETSI DTS/TM06006] 159 G.992.1 [ITU G992.1] POTS non-overlapped Full 160 G.992.1 POTS overlapped Full 161 G.992.1 Integrated Services Digital 162 Network (ISDN) non-overlapped Full 163 G.992.1 ISDN overlapped Full 164 G.992.1 TCM-ISDN non-overlapped Full 165 G.992.1 TCM-ISDN overlapped Full 166 G.992.2 POTS non-overlapped G.Lite 167 G.992.2 POTS overlapped G.Lite 168 G.992.2 with TCM-ISDN G.Lite 169 non-overlapped 170 G.992.2 with TCM-ISDN overlapped G.Lite 171 G.992.1 TCM-ISDN symmetric Full 173 Table 1: Transmission Mode and Line Mode 175 In case more than one bit is configured for an ADSL interface and 176 both Full and G.Lite modes are selected, the interface is said to 177 be configured in the dual mode. Only one bit can be set in the Actual 178 object that reflects the actual mode of transmission as well as the 179 line mode. 181 6.2.2 Power Management 183 There are three possible power states for each managed ADSL interface 184 operating in the G.Lite mode. L0 is power on, L1 is power on but 185 reduced and L3 is power off. Power state cannot be configured by an 186 operator but it can be viewed via the ifOperStatus object for the 187 managed ADSL interface. The value of the object ifOperStatus is 188 set to down(2) if the ADSL interface is in power state L3 and is set 189 to up(1) if the ADSL line interface is in power state L0 or L1. 191 An ADSL line power state, if the interface is operating in the 192 G.Lite mode, can also be monitored by the adslLineGlitePowerState 193 object defined in the ADSL Line Extension table. The value of the 194 object enumerates the three power states attainable by the managed 195 interface. 197 6.2.3 Fast Retrain Parameters 199 Section 7.4.15 [ITU G.997.1] specifies fast retrain parameters. Fast 200 retrain parameters include two counters: fast retrain count and failed 201 fast retrain count. These two counters have been added to all 202 performance tables. 204 6.2.4 Counters for Severely Errored Second-line and Unavailable 205 Seconds-line 207 ITU G.997.1 sections 6.2.1.1.7 and 6.2.1.1.9 specify two counters that 208 are not covered by the ADSL Line MIB [RFC2662]. These two counters 209 (severely errored seconds-line and unavailable seconds-line) are added 210 to all the performance tables. 212 Unavailable seconds counts cumulative number of seconds in which the 213 interface was unavailable during the measured period. This counter 214 does not include the seconds in which unavailability was caused solely 215 by fast retrains and failed fast retrains. Fast retrains and failed 216 fast retrains are considered to be part of the normal network operation 217 and thus are not counted as unavailable errors. 219 6.2.5 Counters, Interval Buckets and Thresholds 221 For physical-level events, there are counters, current 15-minute and 222 one (up to 96) 15-minute history bucket(s) of "interval-counters", as 223 well as current and previous 1-day interval-counters. Each 224 physical-layer current 15-minute event bucket has threshold trap. 226 There is no requirement for an agent to ensure fixed relationship 227 between the start of a fifteen minute and any wall clock; however 228 some implementations may align the fifteen-minute intervals with 229 quarter hours. Likewise, an implementation may choose to align one 230 day intervals with start of a day. 232 Separate tables are provided for the 96 interval-counters. They are 233 indexed by {ifIndex, AdslAtu*IntervalNumber}. 235 Counters are not reset when an ATU-C or ATU-R is reinitialized, only 236 when the agent is reset or reinitialized (or under specific request 237 outside the scope of this MIB). 239 The 15-minute event counters are of type PerfCurrentCount and 240 PerfIntervalCount. The 1-day event counters are of type 241 AdslPerfCurrDayCount and AdslPerfPrevDayCount. Both 15-minute and 1- 242 day time elapsed counters are of type AdslPerfTimeElapsed. 244 6.2.6 Alternative profile configuration for the dual line mode 245 interface 247 The object, adslLineConfProfileDualLite, is used only when the interface 248 (the ADSL line and, if applicable, channel) is configured as dual mode, 249 that is, the object adslLineTransAtucConfig is configured with one or more 250 full-rate modes and one or more G.Lite modes. 252 The object adslLineConfProfile defined in ADSL-MIB [RFC2662] is used as 253 the primary full-rate profile. The newly added object in this MIB 254 module, adslLineConfProfileDualLite, is used to describe and configure 255 the G.Lite profile. Note that if one or more full-rate modes are 256 configured, or only G.Lite modes are configured, only the original 257 full-rate profile is needed. The dual-mode profile object is only 258 needed when both full-rate and G.Lite profiles are needed. In this case, 259 it will be set to the value of adslLineConfProfile. 261 When 'static' profiles are implemented, in much like the case of the 262 object, adslLineConfProfileName [RFC2662], this object's value will 263 need to algorithmically represent the line. In this case, the value 264 of the line's ifIndex plus a value indicating the line mode type 265 (e.g., G.Lite, Full-rate) will be used. Therefore, the profile's name 266 is a string of the concatenation 267 of ifIndex and one of the follow values: Full or Lite. This string will 268 be fixed-length (i.e., 14) with leading zero(s). For example, the 269 profile name for ifIndex that equals '15' and is a full rate line, 270 it will be '0000000015Full'. 272 7. Conformance and Compliance 274 See the conformance and compliance statements within the information 275 module. 277 8. Definitions 279 ADSL-LINE-EXT-MIB DEFINITIONS ::= BEGIN 281 IMPORTS 282 Counter32, 283 Unsigned32, 284 NOTIFICATION-TYPE, 285 MODULE-IDENTITY, Gauge32, 286 OBJECT-TYPE FROM SNMPv2-SMI 287 MODULE-COMPLIANCE, OBJECT-GROUP, 288 NOTIFICATION-GROUP FROM SNMPv2-CONF 289 TEXTUAL-CONVENTION FROM SNMPv2-TC 290 PerfCurrentCount, 291 PerfIntervalCount FROM PerfHist-TC-MIB 292 AdslPerfCurrDayCount, 293 AdslPerfPrevDayCount FROM ADSL-TC-MIB 294 SnmpAdminString FROM SNMP-FRAMEWORK-MIB 295 adslLineAlarmConfProfileEntry, 296 adslLineConfProfileEntry, 297 adslAturIntervalEntry, 298 adslAturPerfDataEntry, 299 adslAtucIntervalEntry, 300 adslAtucPerfDataEntry, 301 adslLineEntry, 302 adslMIB FROM ADSL-LINE-MIB 303 ; 305 adslExtMIB MODULE-IDENTITY 307 LAST-UPDATED "200104090000Z" 309 ORGANIZATION "IETF ADSL MIB Working Group" 311 CONTACT-INFO 312 " 313 Faye Ly 314 Salira Optical Systems 315 2698 Orchard Parkway 316 San Jose, CA 95134 317 Tel: +1 408-382-0088 318 Fax: +1 408-382-1688 319 E-Mail: faye@salira.com 321 Gregory Bathrick 322 NOKIA High Speed Access Nodes 323 1310 Redwood Way, 324 Petaluma, CA 94954 325 Tel: +1 707-793-7030 326 Fax: +1 707-792-0850 327 E-Mail: greg.bathrick@nokia.com 329 IETF ADSL MIB Working Group 330 331 " 332 DESCRIPTION 333 "This MIB Module is a supplement to the ADSL-LINE-MIB 334 [RFC2662]." 335 REVISION "0108011200Z" -- YY Month YYYY 336 DESCRIPTION "Initial Version, published as RFC xxxx. This MIB 337 module is supplement to the ADSL-LINE-MIB [RFC2662]." 338 ::= { adslMIB 3 } 340 adslExtMibObjects OBJECT IDENTIFIER ::= { adslExtMIB 1 } 342 AdslTransmissionModeType ::= TEXTUAL-CONVENTION 343 STATUS current 344 DESCRIPTION 345 "A set of ADSL line transmission modes, with one bit 346 per mode. The notes (F) and (L) denote Full-Rate 347 and G.Lite respectively: 348 Bit 00 : Regional Std. (ANSI T1.413) (F) 349 Bit 01 : Regional Std. (ETSI DTS/TM06006) (F) 350 Bit 02 : G.992.1 POTS non-overlapped (F) 351 Bit 03 : G.992.1 POTS overlapped (F) 352 Bit 04 : G.992.1 ISDN non-overlapped (F) 353 Bit 05 : G.992.1 ISDN overlapped (F) 354 Bit 06 : G.992.1 TCM-ISDN non-overlapped (F) 355 Bit 07 : G.992.1 TCM-ISDN overlapped (F) 356 Bit 08 : G.992.2 POTS non-overlapped (L) 357 Bit 09 : G.992.2 POTS overlapped (L) 358 Bit 10 : G.992.2 with TCM-ISDN non-overlapped (L) 359 Bit 11 : G.992.2 with TCM-ISDN overlapped (L) 360 Bit 12 : G.992.1 TCM-ISDN symmetric (F) 361 " 362 SYNTAX BITS { 363 ansit1413(0), 364 etsi(1), 365 q9921PotsNonOverlapped(2), 366 q9921PotsOverlapped(3), 367 q9921IsdnNonOverlapped(4), 368 q9921isdnOverlapped(5), 369 q9921tcmIsdnNonOverlapped(6), 370 q9921tcmIsdnOverlapped(7), 371 q9922potsNonOverlapeed(8), 372 q9922potsOverlapped(9), 373 q9922tcmIsdnNonOverlapped(10), 374 q9922tcmIsdnOverlapped(11), 375 q9921tcmIsdnSymmetric(12) 376 } 378 adslLineExtTable OBJECT-TYPE 379 SYNTAX SEQUENCE OF AdslLineExtEntry 380 MAX-ACCESS not-accessible 381 STATUS current 382 DESCRIPTION 383 "This table is an extension of RFC2662. It 384 contains ADSL line configuration and 385 monitoring information. This includes the ADSL 386 line's capabilities and actual ADSL transmission 387 bbbbbbsystem." 388 ::= { adslExtMibObjects 17 } 390 adslLineExtEntry OBJECT-TYPE 391 SYNTAX AdslLineExtEntry 392 MAX-ACCESS not-accessible 393 STATUS current 394 DESCRIPTION 395 "An entry extends the adslLineEntry defined in 396 [RFC2662]. Each entry corresponds to an ADSL 397 line." 398 AUGMENTS { adslLineEntry } 399 ::= { adslLineExtTable 1 } 401 AdslLineExtEntry ::= 402 SEQUENCE { 403 adslLineTransAtucCap AdslTransmissionModeType, 404 adslLineTransAtucConfig AdslTransmissionModeType, 405 adslLineTransAtucActual AdslTransmissionModeType, 406 adslLineGlitePowerState INTEGER, 407 adslLineConfProfileDualLite SnmpAdminString 408 } 410 adslLineTransAtucCap OBJECT-TYPE 411 SYNTAX AdslTransmissionModeType 412 MAX-ACCESS read-only 413 STATUS current 414 DESCRIPTION 415 "The transmission modes, represented by a 416 bitmask that the ATU-C is capable of 417 supporting. The modes available are limited 418 by the design of the equipment." 419 REFERENCE "Section 7.3.2 ITU G.997.1" 420 ::= { adslLineExtEntry 1 } 422 adslLineTransAtucConfig OBJECT-TYPE 423 SYNTAX AdslTransmissionModeType 424 MAX-ACCESS read-write 425 STATUS current 426 DESCRIPTION 427 "The transmission modes, represented by a bitmask, 428 currently enabled by the ATU-C. The manager can 429 only set those modes that are supported by the 430 ATU-C. An ATU-C's supported modes are provided by 431 AdslLineTransAtucCap." 432 REFERENCE "Section 7.3.2 ITU G.997.1" 433 ::= { adslLineExtEntry 2 } 435 adslLineTransAtucActual OBJECT-TYPE 436 SYNTAX AdslTransmissionModeType 437 MAX-ACCESS read-only 438 STATUS current 439 DESCRIPTION 440 "The actual transmission mode of the ATU-C. 441 During ADSL line initialization, the ADSL 442 Transceiver Unit - Remote terminal end (ATU-R) 443 will determine the mode used for the link. 444 This value will be limited a single transmission 445 mode that is a subset of those modes enabled 446 by the ATU-C and denoted by adslLineTransAtucConfig. 447 After an initialization has occurred, its mode is 448 saved as the 'Current' mode and is persistence 449 should the link go down. This object returns 0 450 (i.e. BITS with no mode bit set) if the mode is 451 not known." 452 REFERENCE "Section 7.3.2 ITU G.997.1 " 453 ::= { adslLineExtEntry 3 } 455 adslLineGlitePowerState OBJECT-TYPE 456 SYNTAX INTEGER { 457 none(1), 458 l0(2), -- L0 Power on 459 l1(3), -- L1 Power on but reduced 460 l3(4) -- L3 Power off 461 } 462 MAX-ACCESS read-only 463 STATUS current 464 DESCRIPTION 465 "The value of this object specifies the power 466 state of this interface. If the object 467 adslLineTransAtucActual is set to a G.992.2 468 (G.Lite)-type transmission mode, the value of 469 this object will be one of the valid power 470 states: L0(2), L1(3), or L3(4). Otherwise, its 471 value will be none(1)." 472 ::= { adslLineExtEntry 4 } 474 adslLineConfProfileDualLite OBJECT-TYPE 475 SYNTAX SnmpAdminString 476 MAX-ACCESS read-write 477 STATUS current 478 DESCRIPTION 479 "This object extends the definition an ADSL line and 480 associated channels (when applicable) for cases when 481 it is configured in dual mode, and operating in a 482 G.Lite-type mode as denoted by adslLineTransAtucActual. 483 Dual mode exists when the object, adslLineTransAtucConfig, 484 is configured with one or more full-rate modes and one or 485 more G.Lite modes simultaneously. 487 When 'dynamic' profiles are implemented, the value of 488 object is equal to the index of the applicable row in the 489 ADSL Line Configuration Profile Table, 490 AdslLineConfProfileTable defined in ADSL-MIB [RFC2662]. 492 In the case when dual-mode has not been enabled, the 493 value of the object will be equal to the value of the 494 object adslLineConfProfile [RFC2662]. 496 When `static' profiles are implemented, in much 497 like the case of the object, adslLineConfProfileName 498 [RFC2662], this object's value will need to 499 algorithmically represent the characteristics of the 500 line. In this case, the value of the line's ifIndex 501 plus a value indicating the line mode type 502 (e.g., G.Lite, Full-rate) will be used. Therefore, 503 the profile's name is a string concatenating the 504 ifIndex and one of the follow values: Full or Lite. This 505 string will be fixed-length (i.e., 14) with leading 506 zero(s). For example, the profile name for 507 ifIndex that equals '15' and is a full rate 508 line, it will be '0000000015Full'." 509 REFERENCE "Section 5.4 Profiles, RFC 2662" 510 ::= { adslLineExtEntry 5 } 512 adslAtucPerfDataExtTable OBJECT-TYPE 513 SYNTAX SEQUENCE OF AdslAtucPerfDataExtEntry 514 MAX-ACCESS not-accessible 515 STATUS current 516 DESCRIPTION 517 "This table extends adslAtucPerfDataTable [RFC2662] 518 with additional ADSL physical line counter 519 information such as unavailable seconds-line and 520 severely errored seconds-line." 521 ::= { adslExtMibObjects 18 } 523 adslAtucPerfDataExtEntry OBJECT-TYPE 524 SYNTAX AdslAtucPerfDataExtEntry 525 MAX-ACCESS not-accessible 526 STATUS current 527 DESCRIPTION 528 "An entry extends the adslAtucPerfDataEntry defined 529 in [RFC2662]. Each entry corresponds to an ADSL 530 line." 531 AUGMENTS { adslAtucPerfDataEntry } 532 ::= { adslAtucPerfDataExtTable 1 } 534 AdslAtucPerfDataExtEntry ::= 535 SEQUENCE { 536 adslAtucPerfStatFastR Counter32, 537 adslAtucPerfStatFailedFastR Counter32, 538 adslAtucPerfStatSesL Counter32, 539 adslAtucPerfStatUasL Counter32, 540 adslAtucPerfCurr15MinFastR PerfCurrentCount, 541 adslAtucPerfCurr15MinFailedFastR PerfCurrentCount, 542 adslAtucPerfCurr15MinSesL PerfCurrentCount, 543 adslAtucPerfCurr15MinUasL PerfCurrentCount, 544 adslAtucPerfCurr1DayFastR AdslPerfCurrDayCount, 545 adslAtucPerfCurr1DayFailedFastR AdslPerfCurrDayCount, 546 adslAtucPerfCurr1DaySesL AdslPerfCurrDayCount, 547 adslAtucPerfCurr1DayUasL AdslPerfCurrDayCount, 548 adslAtucPerfPrev1DayFastR AdslPerfPrevDayCount, 549 adslAtucPerfPrev1DayFailedFastR AdslPerfPrevDayCount, 550 adslAtucPerfPrev1DaySesL AdslPerfPrevDayCount, 551 adslAtucPerfPrev1DayUasL AdslPerfPrevDayCount 552 } 554 adslAtucPerfStatFastR OBJECT-TYPE 555 SYNTAX Counter32 556 UNITS "line retrains" 557 MAX-ACCESS read-only 558 STATUS current 559 DESCRIPTION 560 "The value of this object reports the count of 561 the number of fast line bs since last 562 agent reset." 563 REFERENCE "ITU G.997.1 Section 7.4.15.1 " 564 ::= { adslAtucPerfDataExtEntry 1 } 566 adslAtucPerfStatFailedFastR OBJECT-TYPE 567 SYNTAX Counter32 568 UNITS "line retrains" 569 MAX-ACCESS read-only 570 STATUS current 571 DESCRIPTION 572 "The value of this object reports the count of 573 the number of failed fast line retrains since 574 last agent reset." 575 REFERENCE "ITU G.997.1 Section 7.4.15.2 " 576 ::= { adslAtucPerfDataExtEntry 2 } 578 adslAtucPerfStatSesL OBJECT-TYPE 579 SYNTAX Counter32 580 UNITS "seconds" 581 MAX-ACCESS read-only 582 STATUS current 583 DESCRIPTION 584 "The value of this object reports the count of 585 the number of severely errored seconds-line since 586 last agent reset." 587 REFERENCE "ITU G.997.1 Section 7.2.1.1.7 " 588 ::= { adslAtucPerfDataExtEntry 3 } 590 adslAtucPerfStatUasL OBJECT-TYPE 591 SYNTAX Counter32 592 UNITS "seconds" 593 MAX-ACCESS read-only 594 STATUS current 595 DESCRIPTION 596 "The value of this object reports the count of 597 the number of unavailable seconds-line since 598 last agent reset." 599 REFERENCE "ITU G.997.1 Section 7.2.1.1.9 " 600 ::= { adslAtucPerfDataExtEntry 4 } 602 adslAtucPerfCurr15MinFastR OBJECT-TYPE 603 SYNTAX PerfCurrentCount 604 UNITS "seconds" 605 MAX-ACCESS read-only 606 STATUS current 607 DESCRIPTION 608 "For the current 15-minute interval, 609 adslAtucPerfCurr15MinFastR reports the current 610 number of seconds during which there have been 611 fast retrains." 612 REFERENCE "ITU G.997.1 Section 7.4.15.1 " 613 ::= { adslAtucPerfDataExtEntry 5 } 615 adslAtucPerfCurr15MinFailedFastR OBJECT-TYPE 616 SYNTAX PerfCurrentCount 617 UNITS "seconds" 618 MAX-ACCESS read-only 619 STATUS current 620 DESCRIPTION 621 "For the current 15-minute interval, 622 adslAtucPerfCurr15MinFailedFastR reports the current 623 number of seconds during which there have been 624 failed fast retrains." 625 REFERENCE "ITU G.997.1 Section 7.4.15.2 " 626 ::= { adslAtucPerfDataExtEntry 6 } 628 adslAtucPerfCurr15MinSesL OBJECT-TYPE 629 SYNTAX PerfCurrentCount 630 UNITS "seconds" 631 MAX-ACCESS read-only 632 STATUS current 633 DESCRIPTION 634 "For the current 15-minute interval, 635 adslAtucPerfCurr15MinSesL reports the current 636 number of seconds during which there have been 637 severely errored seconds-line." 638 REFERENCE "ITU G.997.1 Section 7.2.1.1.7 " 639 ::= { adslAtucPerfDataExtEntry 7 } 641 adslAtucPerfCurr15MinUasL OBJECT-TYPE 642 SYNTAX PerfCurrentCount 643 UNITS "seconds" 644 MAX-ACCESS read-only 645 STATUS current 646 DESCRIPTION 647 "For the current 15-minute interval, 648 adslAtucPerfCurr15MinUasL reports the current 649 number of seconds during which there have been 650 unavailable seconds-line." 651 REFERENCE "ITU G.997.1 Section 7.2.1.1.9 " 652 ::= { adslAtucPerfDataExtEntry 8 } 654 adslAtucPerfCurr1DayFastR OBJECT-TYPE 655 SYNTAX AdslPerfCurrDayCount 656 UNITS "seconds" 657 MAX-ACCESS read-only 658 STATUS current 659 DESCRIPTION 660 "For the current day as measured by 661 adslAtucPerfCurr1DayTimeElapsed [RFC 2662], 662 adslAtucPerfCurr1DayFastR reports the number 663 of seconds during which there have been 664 fast retrains." 665 REFERENCE "ITU G.997.1 Section 7.4.15.1 " 666 ::= { adslAtucPerfDataExtEntry 9 } 668 adslAtucPerfCurr1DayFailedFastR OBJECT-TYPE 669 SYNTAX AdslPerfCurrDayCount 670 UNITS "seconds" 671 MAX-ACCESS read-only 672 STATUS current 673 DESCRIPTION 674 "For the current day as measured by 675 adslAtucPerfCurr1DayTimeElapsed [RFC 2662], 676 adslAtucPerfCurr1DayFailedFastR reports the 677 number of seconds during which there have been 678 failed fast retrains." 679 REFERENCE "ITU G.997.1 Section 7.4.15.2 " 680 ::= { adslAtucPerfDataExtEntry 10 } 682 adslAtucPerfCurr1DaySesL OBJECT-TYPE 683 SYNTAX AdslPerfCurrDayCount 684 UNITS "seconds" 685 MAX-ACCESS read-only 686 STATUS current 687 DESCRIPTION 688 "For the current day as measured by 689 adslAtucPerfCurr1DayTimeElapsed [RFC 2662], 690 adslAtucPerfCurr1DaySesL reports the 691 number of seconds during which there have been 692 severely errored seconds-line." 693 REFERENCE "ITU G.997.1 Section 7.2.1.1.7 " 694 ::= { adslAtucPerfDataExtEntry 11 } 696 adslAtucPerfCurr1DayUasL OBJECT-TYPE 697 SYNTAX AdslPerfCurrDayCount 698 UNITS "seconds" 699 MAX-ACCESS read-only 700 STATUS current 701 DESCRIPTION 702 "For the current day as measured by 703 adslAtucPerfCurr1DayTimeElapsed [RFC 2662], 704 adslAtucPerfCurr1DayUasL reports the 705 number of seconds during which there have been 706 unavailable seconds-line." 707 REFERENCE "ITU G.997.1 Section 7.2.1.1.9 " 708 ::= { adslAtucPerfDataExtEntry 12 } 710 adslAtucPerfPrev1DayFastR OBJECT-TYPE 711 SYNTAX AdslPerfPrevDayCount 712 UNITS "seconds" 713 MAX-ACCESS read-only 714 STATUS current 715 DESCRIPTION 716 "For the previous day, adslAtucPerfPrev1DayFastR 717 reports the number of seconds during which there 718 were fast retrains." 719 REFERENCE "ITU G.997.1 Section 7.4.15.1 " 720 ::= { adslAtucPerfDataExtEntry 13 } 722 adslAtucPerfPrev1DayFailedFastR OBJECT-TYPE 723 SYNTAX AdslPerfPrevDayCount 724 UNITS "seconds" 725 MAX-ACCESS read-only 726 STATUS current 727 DESCRIPTION 728 "For the previous day, adslAtucPerfPrev1DayFailedFastR 729 reports the number of seconds during which there 730 were failed fast retrains." 731 REFERENCE "ITU G.997.1 Section 7.4.15.2 " 732 ::= { adslAtucPerfDataExtEntry 14 } 734 adslAtucPerfPrev1DaySesL OBJECT-TYPE 735 SYNTAX AdslPerfPrevDayCount 736 UNITS "seconds" 737 MAX-ACCESS read-only 738 STATUS current 739 DESCRIPTION 740 "For the previous day, adslAtucPerfPrev1DaySesL 741 reports the number of seconds during which there 742 were severely errored seconds-line." 743 REFERENCE "ITU G.997.1 Section 7.2.1.1.7 " 744 ::= { adslAtucPerfDataExtEntry 15 } 746 adslAtucPerfPrev1DayUasL OBJECT-TYPE 747 SYNTAX AdslPerfPrevDayCount 748 UNITS "seconds" 749 MAX-ACCESS read-only 750 STATUS current 751 DESCRIPTION 752 "For the previous day, adslAtucPerfPrev1DayUasL 753 reports the number of seconds during which there 754 were unavailable seconds-line." 755 REFERENCE "ITU G.997.1 Section 7.2.1.1.9 " 756 ::= { adslAtucPerfDataExtEntry 16 } 758 adslAtucIntervalExtTable OBJECT-TYPE 759 SYNTAX SEQUENCE OF AdslAtucIntervalExtEntry 760 MAX-ACCESS not-accessible 761 STATUS current 762 DESCRIPTION 763 "This table provides one row for each ATU-C 764 performance data collection interval for 765 ADSL physical interfaces whose 766 IfEntries' ifType is equal to adsl(94)." 767 ::= { adslExtMibObjects 19 } 769 adslAtucIntervalExtEntry OBJECT-TYPE 770 SYNTAX AdslAtucIntervalExtEntry 771 MAX-ACCESS not-accessible 772 STATUS current 773 DESCRIPTION "An entry in the 774 adslAtucIntervalExtTable." 775 AUGMENTS { adslAtucIntervalEntry } 776 ::= { adslAtucIntervalExtTable 1 } 778 AdslAtucIntervalExtEntry ::= 779 SEQUENCE { 780 adslAtucIntervalFastR PerfIntervalCount, 781 adslAtucIntervalFailedFastR PerfIntervalCount, 782 adslAtucIntervalSesL PerfIntervalCount, 783 adslAtucIntervalUasL PerfIntervalCount 784 } 786 adslAtucIntervalFastR OBJECT-TYPE 787 SYNTAX PerfIntervalCount 788 UNITS "seconds" 789 MAX-ACCESS read-only 790 STATUS current 791 DESCRIPTION 792 "For the current interval, adslAtucIntervalFastR 793 reports the current number of seconds during which 794 there have been fast retrains." 795 ::= { adslAtucIntervalExtEntry 1 } 797 adslAtucIntervalFailedFastR OBJECT-TYPE 798 SYNTAX PerfIntervalCount 799 UNITS "seconds" 800 MAX-ACCESS read-only 801 STATUS current 802 DESCRIPTION 803 "For the each interval, adslAtucIntervalFailedFastR 804 reports the number of seconds during which 805 there have been failed fast retrains." 806 ::= { adslAtucIntervalExtEntry 2 } 808 adslAtucIntervalSesL OBJECT-TYPE 809 SYNTAX PerfIntervalCount 810 UNITS "seconds" 811 MAX-ACCESS read-only 812 STATUS current 813 DESCRIPTION 814 "For the each interval, adslAtucIntervalSesL 815 reports the number of seconds during which 816 there have been severely errored seconds-line." 817 ::= { adslAtucIntervalExtEntry 3 } 819 adslAtucIntervalUasL OBJECT-TYPE 820 SYNTAX PerfIntervalCount 821 UNITS "seconds" 822 MAX-ACCESS read-only 823 STATUS current 824 DESCRIPTION 825 "For the each interval, adslAtucIntervalUasL 826 reports the number of seconds during which 827 there have been unavailable seconds-line." 828 ::= { adslAtucIntervalExtEntry 4 } 830 adslAturPerfDataExtTable OBJECT-TYPE 831 SYNTAX SEQUENCE OF AdslAturPerfDataExtEntry 832 MAX-ACCESS not-accessible 833 STATUS current 834 DESCRIPTION 835 "This table contains ADSL physical line counters 836 not defined in the adslAturPerfDataTable 837 from the ADSL-LINE-MIB [RFC2662]." 838 ::= { adslExtMibObjects 20 } 840 adslAturPerfDataExtEntry OBJECT-TYPE 841 SYNTAX AdslAturPerfDataExtEntry 842 MAX-ACCESS not-accessible 843 STATUS current 844 DESCRIPTION 845 "An entry extends the adslAturPerfDataEntry defined 846 in [RFC2662]. Each entry corresponds to an ADSL 847 line." 848 AUGMENTS { adslAturPerfDataEntry } 849 ::= { adslAturPerfDataExtTable 1 } 851 AdslAturPerfDataExtEntry ::= 852 SEQUENCE { 853 adslAturPerfStatSesL Counter32, 854 adslAturPerfStatUasL Counter32, 855 adslAturPerfCurr15MinSesL PerfCurrentCount, 856 adslAturPerfCurr15MinUasL PerfCurrentCount, 857 adslAturPerfCurr1DaySesL AdslPerfCurrDayCount, 858 adslAturPerfCurr1DayUasL AdslPerfCurrDayCount, 859 adslAturPerfPrev1DaySesL AdslPerfPrevDayCount, 860 adslAturPerfPrev1DayUasL AdslPerfPrevDayCount 861 } 863 adslAturPerfStatSesL OBJECT-TYPE 864 SYNTAX Counter32 865 UNITS "seconds" 866 MAX-ACCESS read-only 867 STATUS current 868 DESCRIPTION 869 "The value of this object reports the count of 870 severely errored second-line since the last agent 871 reset." 872 REFERENCE "ITU G.997.1 Section 7.2.1.1.7 " 873 ::= { adslAturPerfDataExtEntry 1 } 875 adslAturPerfStatUasL OBJECT-TYPE 876 SYNTAX Counter32 877 UNITS "seconds" 878 MAX-ACCESS read-only 879 STATUS current 880 DESCRIPTION 881 "The value of this object reports the count of 882 unavailable seconds-line since the last agent 883 reset." 884 REFERENCE "ITU G.997.1 Section 7.2.1.2.9 " 885 ::= { adslAturPerfDataExtEntry 2 } 887 adslAturPerfCurr15MinSesL OBJECT-TYPE 888 SYNTAX PerfCurrentCount 889 UNITS "seconds" 890 MAX-ACCESS read-only 891 STATUS current 892 DESCRIPTION 893 "For the current 15-minute interval, 894 adslAturPerfCurr15MinSesL reports the current 895 number of seconds during which there have been 896 severely errored seconds-line." 897 REFERENCE "ITU G.997.1 Section 7.2.1.2.7 " 898 ::= { adslAturPerfDataExtEntry 3 } 900 adslAturPerfCurr15MinUasL OBJECT-TYPE 901 SYNTAX PerfCurrentCount 902 UNITS "seconds" 903 MAX-ACCESS read-only 904 STATUS current 905 DESCRIPTION 906 "For the current 15-minute interval, 907 adslAturPerfCurr15MinUasL reports the current 908 number of seconds during which there have been 909 available seconds-line." 910 REFERENCE "ITU G.997.1 Section 7.2.1.2.9 " 911 ::= { adslAturPerfDataExtEntry 4 } 913 adslAturPerfCurr1DaySesL OBJECT-TYPE 914 SYNTAX AdslPerfCurrDayCount 915 UNITS "seconds" 916 MAX-ACCESS read-only 917 STATUS current 918 DESCRIPTION 919 "For the current day as measured by 920 adslAturPerfCurr1DayTimeElapsed [RFC 2662], 921 adslAturPerfCurr1DaySesL reports the 922 number of seconds during which there have been 923 severely errored seconds-line." 924 REFERENCE "ITU G.997.1 Section 7.2.1.2.7 " 925 ::= { adslAturPerfDataExtEntry 5 } 927 adslAturPerfCurr1DayUasL OBJECT-TYPE 928 SYNTAX AdslPerfCurrDayCount 929 UNITS "seconds" 930 MAX-ACCESS read-only 931 STATUS current 932 DESCRIPTION 933 "For the current day as measured by 934 adslAturPerfCurr1DayTimeElapsed [RFC 2662], 935 adslAturPerfCurr1DayUasL reports the 936 number of seconds during which there have been 937 unavailable seconds-line." 938 REFERENCE "ITU G.997.1 Section 7.2.1.2.9 " 939 ::= { adslAturPerfDataExtEntry 6 } 941 adslAturPerfPrev1DaySesL OBJECT-TYPE 942 SYNTAX AdslPerfPrevDayCount 943 UNITS "seconds" 944 MAX-ACCESS read-only 945 STATUS current 946 DESCRIPTION 947 "For the previous day, adslAturPerfPrev1DaySesL 948 reports the number of seconds during which there 949 were severely errored seconds-line." 950 REFERENCE "ITU G.997.1 Section 7.2.1.2.7 " 951 ::= { adslAturPerfDataExtEntry 7 } 953 adslAturPerfPrev1DayUasL OBJECT-TYPE 954 SYNTAX AdslPerfPrevDayCount 955 UNITS "seconds" 956 MAX-ACCESS read-only 957 STATUS current 958 DESCRIPTION 959 "For the previous day, adslAturPerfPrev1DayUasL 960 reports the number of seconds during which there 961 were severely errored seconds-line." 962 REFERENCE "ITU G.997.1 Section 7.2.1.2.9 " 963 ::= { adslAturPerfDataExtEntry 8 } 965 adslAturIntervalExtTable OBJECT-TYPE 966 SYNTAX SEQUENCE OF AdslAturIntervalExtEntry 967 MAX-ACCESS not-accessible 968 STATUS current 969 DESCRIPTION 970 "This table provides one row for each ATU-R 971 performance data collection interval for 972 ADSL physical interfaces whose 973 IfEntries' ifType is equal to adsl(94)." 974 ::= { adslExtMibObjects 21 } 976 adslAturIntervalExtEntry OBJECT-TYPE 977 SYNTAX AdslAturIntervalExtEntry 978 MAX-ACCESS not-accessible 979 STATUS current 980 DESCRIPTION "An entry in the 981 adslAturIntervalExtTable." 982 AUGMENTS { adslAturIntervalEntry } 983 ::= { adslAturIntervalExtTable 1 } 985 AdslAturIntervalExtEntry ::= 986 SEQUENCE { 987 adslAturIntervalSesL PerfIntervalCount, 988 adslAturIntervalUasL PerfIntervalCount 989 } 991 adslAturIntervalSesL OBJECT-TYPE 992 SYNTAX PerfIntervalCount 993 UNITS "seconds" 994 MAX-ACCESS read-only 995 STATUS current 996 DESCRIPTION 997 "For the each interval, adslAturIntervalSesL 998 reports the number of seconds during which 999 there have been severely errored seconds-line." 1000 ::= { adslAturIntervalExtEntry 1 } 1002 adslAturIntervalUasL OBJECT-TYPE 1003 SYNTAX PerfIntervalCount 1004 UNITS "seconds" 1005 MAX-ACCESS read-only 1006 STATUS current 1007 DESCRIPTION 1008 "For the each interval, adslAturIntervalUasL 1009 reports the number of seconds during which 1010 there have been unavailable seconds-line." 1011 ::= { adslAturIntervalExtEntry 2 } 1013 adslConfProfileExtTable OBJECT-TYPE 1014 SYNTAX SEQUENCE OF AdslConfProfileExtEntry 1015 MAX-ACCESS not-accessible 1016 STATUS current 1017 DESCRIPTION 1018 "The adslConfProfileExtTable extends the ADSL line 1019 profile configuration information in the 1020 adslLineConfProfileTable from the ADSL-LINE-MIB 1021 [RFC2662] by adding the ability to configure the 1022 ADSL physical line mode." 1023 ::= { adslExtMibObjects 22 } 1025 adslConfProfileExtEntry OBJECT-TYPE 1026 SYNTAX AdslConfProfileExtEntry 1027 MAX-ACCESS not-accessible 1028 STATUS current 1029 DESCRIPTION 1030 "An entry extends the adslLineConfProfileEntry defined 1031 in [RFC2662]. Each entry corresponds to an ADSL line 1032 profile." 1033 AUGMENTS { adslLineConfProfileEntry } 1034 ::= { adslConfProfileExtTable 1 } 1036 AdslConfProfileExtEntry ::= 1037 SEQUENCE { 1038 adslConfProfileLineType INTEGER 1039 } 1041 adslConfProfileLineType OBJECT-TYPE 1042 SYNTAX INTEGER { 1043 noChannel (1), -- no channels exist 1044 fastOnly (2), -- only fast channel exists 1045 interleavedOnly (3), -- only interleaved channel 1046 -- exist 1047 fastOrInterleaved (4),-- either fast or interleaved 1048 -- channels can exist, but 1049 -- only one at any time 1050 fastAndInterleaved (5)-- both the fast channel and 1051 -- the interleaved channel 1052 -- exist 1053 } 1054 MAX-ACCESS read-create 1055 STATUS current 1056 DESCRIPTION 1057 "This object is used to configure the ADSL physical 1058 line mode. It has following valid values: 1060 noChannel(1), when no channels exist. 1061 fastOnly(2), when only fast channel exists. 1062 interleavedOnly(3), when only interleaved channel 1063 exist. 1064 fastOrInterleaved(4), when either fast or 1065 interleaved channels can exist, but only one 1066 at any time. 1067 fastAndInterleaved(5), when both the fast channel 1068 and the interleaved channel exist. 1070 In the case when no value has been set, the default 1071 Value is noChannel(1). 1072 " 1073 ::= { adslConfProfileExtEntry 1 } 1075 adslAlarmConfProfileExtTable OBJECT-TYPE 1076 SYNTAX SEQUENCE OF AdslAlarmConfProfileExtEntry 1077 MAX-ACCESS not-accessible 1078 STATUS current 1079 DESCRIPTION 1080 "This table extends the adslLineAlarmConfProfileTable 1081 and provides threshold parameters for all the 1082 counters defined in this MIB module." 1083 ::= { adslExtMibObjects 23 } 1085 adslAlarmConfProfileExtEntry OBJECT-TYPE 1086 SYNTAX AdslAlarmConfProfileExtEntry 1087 MAX-ACCESS not-accessible 1088 STATUS current 1089 DESCRIPTION 1090 "An entry extends the adslLineAlarmConfProfileTable 1091 defined in [RFC2662]. Each entry corresponds to 1092 an ADSL alarm profile." 1093 AUGMENTS { adslLineAlarmConfProfileEntry } 1094 ::= { adslAlarmConfProfileExtTable 1 } 1096 AdslAlarmConfProfileExtEntry ::= 1097 SEQUENCE { 1098 adslAtucThreshold15MinFailedFastR INTEGER, 1099 adslAtucThreshold15MinSesL INTEGER, 1100 adslAtucThreshold15MinUasL INTEGER, 1101 adslAturThreshold15MinSesL INTEGER, 1102 adslAturThreshold15MinUasL INTEGER 1103 } 1105 adslAtucThreshold15MinFailedFastR OBJECT-TYPE 1106 SYNTAX INTEGER(0..900) 1107 UNITS "seconds" 1108 MAX-ACCESS read-create 1109 STATUS current 1110 DESCRIPTION 1111 "The first time the value of the corresponding 1112 instance of adslAtucPerfCurr15MinFailedFastR reaches 1113 or exceeds this value within a given 15-minute 1114 performance data collection period, an 1115 adslAtucFailedFastRThreshTrap notifications will 1116 be generated. The value '0' will disable the trap. 1117 The default value of this object is '0'." 1118 ::= { adslAlarmConfProfileExtEntry 1 } 1120 adslAtucThreshold15MinSesL OBJECT-TYPE 1121 SYNTAX INTEGER(0..900) 1122 UNITS "seconds" 1123 MAX-ACCESS read-create 1124 STATUS current 1125 DESCRIPTION 1126 "The first time the value of the corresponding instance 1127 of adslAtucPerf15MinSesL reaches or exceeds 1128 this value within a given 15-minute performance data 1129 collection period, an adslAtucSesLThreshTrap 1130 notifications will be generated. The value '0' will 1131 disable the trap. The default value of this object is 1132 '0'." 1133 ::= { adslAlarmConfProfileExtEntry 2 } 1135 adslAtucThreshold15MinUasL OBJECT-TYPE 1136 SYNTAX INTEGER(0..900) 1137 UNITS "seconds" 1138 MAX-ACCESS read-create 1139 STATUS current 1140 DESCRIPTION 1141 "The first time the value of the corresponding instance 1142 of adslAtucPerf15MinUasL reaches or exceeds 1143 this value within a given 15-minute performance data 1144 collection period, an adslAtucUasLThreshTrap 1145 notifications will be generated. The value '0' will 1146 disable the trap. The default value of this object is 1147 '0'." 1148 ::= { adslAlarmConfProfileExtEntry 3 } 1150 adslAturThreshold15MinSesL OBJECT-TYPE 1151 SYNTAX INTEGER(0..900) 1152 UNITS "seconds" 1153 MAX-ACCESS read-create 1154 STATUS current 1155 DESCRIPTION 1156 "The first time the value of the corresponding instance 1157 of adslAturPerf15MinSesL reaches or exceeds 1158 this value within a given 15-minute performance data 1159 collection period, an adslAturSesLThreshTrap 1160 notifications will be generated. The value '0' will 1161 disable the trap. The default value of this object is 1162 '0'." 1163 ::= { adslAlarmConfProfileExtEntry 4 } 1165 adslAturThreshold15MinUasL OBJECT-TYPE 1166 SYNTAX INTEGER(0..900) 1167 UNITS "seconds" 1168 MAX-ACCESS read-create 1169 STATUS current 1170 DESCRIPTION 1171 "The first time the value of the corresponding instance 1172 of adslAturPerf15MinUasL reaches or exceeds 1173 this value within a given 15-minute performance data 1174 collection period, an adslAturUasLThreshTrap 1175 notifications will be generated. The value '0' will 1176 disable the trap. The default value of this object is 1177 '0'." 1178 ::= { adslAlarmConfProfileExtEntry 5 } 1180 -- trap definitions 1182 adslExtTraps OBJECT IDENTIFIER ::= { adslExtMibObjects 24 } 1184 adslExtAtucTraps OBJECT IDENTIFIER ::= { adslExtTraps 1 } 1186 adslAtucFailedFastRThreshTrap NOTIFICATION-TYPE 1187 OBJECTS { adslAtucPerfCurr15MinFailedFastR } 1188 STATUS current 1189 DESCRIPTION 1190 "Failed Fast Retrains 15-minute threshold reached." 1191 ::= { adslExtAtucTraps 0 1 } 1193 adslAtucSesLThreshTrap NOTIFICATION-TYPE 1194 OBJECTS { adslAtucPerfCurr15MinSesL } 1195 STATUS current 1196 DESCRIPTION 1197 "Severely errored seconds-line 15-minute threshold 1198 reached." 1199 ::= { adslExtAtucTraps 0 2 } 1201 adslAtucUasLThreshTrap NOTIFICATION-TYPE 1202 OBJECTS { adslAtucPerfCurr15MinUasL } 1203 STATUS current 1204 DESCRIPTION 1205 "Unavailable seconds-line 15-minute threshold reached." 1206 ::= { adslExtAtucTraps 0 3 } 1208 adslExtAturTraps OBJECT IDENTIFIER ::= { adslExtTraps 2 } 1210 adslAturSesLThreshTrap NOTIFICATION-TYPE 1211 OBJECTS { adslAturPerfCurr15MinSesL } 1212 STATUS current 1213 DESCRIPTION 1214 "Severely errored seconds-line 15-minute threshold 1215 reached." 1216 ::= { adslExtAturTraps 0 1 } 1218 adslAturUasLThreshTrap NOTIFICATION-TYPE 1219 OBJECTS { adslAturPerfCurr15MinUasL } 1220 STATUS current 1221 DESCRIPTION 1222 "Unavailable seconds-line 15-minute threshold reached." 1223 ::= { adslExtAturTraps 0 2 } 1225 -- conformance information 1227 adslExtConformance OBJECT IDENTIFIER ::= { adslExtMIB 2 } 1229 adslExtGroups OBJECT IDENTIFIER ::= { adslExtConformance 1 } 1230 adslExtCompliances OBJECT IDENTIFIER ::= { adslExtConformance 2 } 1232 -- ATU-C agent compliance statements 1234 adslExtLineMibAtucCompliance MODULE-COMPLIANCE 1235 STATUS current 1236 DESCRIPTION 1237 "The compliance statement for SNMP entities which 1238 represent ADSL ATU-C interfaces." 1240 MODULE -- this module 1241 MANDATORY-GROUPS 1242 { 1243 adslExtLineGroup, 1244 adslExtLineConfProfileControlGroup, 1245 adslExtLineAlarmConfProfileGroup 1246 } 1248 GROUP adslExtAtucPhysPerfCounterGroup 1249 DESCRIPTION 1250 "This group is optional. Implementations which 1251 require continuous ATU-C physical event counters 1252 should implement this group." 1254 GROUP adslExtAturPhysPerfCounterGroup 1255 DESCRIPTION 1256 "This group is optional. Implementations which 1257 require continuous ATU-R physical event counters 1258 should implement this group." 1260 OBJECT adslAtucThreshold15MinFailedFastR 1261 MIN-ACCESS read-write 1262 DESCRIPTION 1263 "Read-write access is applicable only when 1264 static profiles as defined in ADSL Line MIB 1265 [RFC2662] are implemented." 1267 OBJECT adslAtucThreshold15MinSesL 1268 MIN-ACCESS read-write 1269 DESCRIPTION 1270 "Read-write access is applicable only when 1271 static profiles as defined in ADSL Line MIB 1272 [RFC2662] are implemented." 1274 OBJECT adslAtucThreshold15MinUasL 1275 MIN-ACCESS read-write 1276 DESCRIPTION 1277 "Read-write access is applicable only when 1278 static profiles as defined in ADSL Line MIB 1279 [RFC2662] are implemented." 1281 OBJECT adslAturThreshold15MinSesL 1282 MIN-ACCESS read-write 1283 DESCRIPTION 1284 "Read-write access is applicable only when 1285 static profiles as defined in ADSL Line MIB 1286 [RFC2662] are implemented." 1288 OBJECT adslAturThreshold15MinUasL 1289 MIN-ACCESS read-write 1290 DESCRIPTION 1291 "Read-write access is applicable only when 1292 static profiles as defined in ADSL Line MIB 1293 [RFC2662] are implemented." 1295 OBJECT adslLineConfProfileDualLite 1296 MIN-ACCESS read-only 1297 DESCRIPTION 1298 "Read-write access is applicable only when 1299 static profiles as defined in ADSL Line MIB 1300 [RFC2662] are implemented." 1302 ::= { adslExtCompliances 1 } 1304 -- units of conformance 1305 adslExtLineGroup OBJECT-GROUP 1306 OBJECTS { 1307 adslLineConfProfileDualLite, 1308 adslLineTransAtucCap, 1309 adslLineTransAtucConfig, 1310 adslLineTransAtucActual, 1311 adslLineGlitePowerState 1312 } 1313 STATUS current 1314 DESCRIPTION 1315 "A collection of objects providing extended 1316 configuration information about an ADSL Line." 1317 ::= { adslExtGroups 1 } 1319 adslExtAtucPhysPerfCounterGroup OBJECT-GROUP 1320 OBJECTS { 1321 adslAtucPerfStatFastR, 1322 adslAtucPerfStatFailedFastR, 1323 adslAtucPerfCurr15MinFastR, 1324 adslAtucPerfCurr15MinFailedFastR, 1325 adslAtucPerfCurr1DayFastR, 1326 adslAtucPerfCurr1DayFailedFastR, 1327 adslAtucPerfPrev1DayFastR, 1328 adslAtucPerfPrev1DayFailedFastR, 1329 adslAtucPerfStatSesL, 1330 adslAtucPerfStatUasL, 1331 adslAtucPerfCurr15MinSesL, 1332 adslAtucPerfCurr15MinUasL, 1333 adslAtucPerfCurr1DaySesL, 1334 adslAtucPerfCurr1DayUasL, 1335 adslAtucPerfPrev1DaySesL, 1336 adslAtucPerfPrev1DayUasL, 1337 adslAtucIntervalFastR, 1338 adslAtucIntervalFailedFastR, 1339 adslAtucIntervalSesL, 1340 adslAtucIntervalUasL 1341 } 1342 STATUS current 1343 DESCRIPTION 1344 "A collection of objects providing raw performance 1345 counts on an ADSL Line (ATU-C end)." 1346 ::= { adslExtGroups 2 } 1348 adslExtAturPhysPerfCounterGroup OBJECT-GROUP 1349 OBJECTS { 1350 adslAturPerfStatSesL, 1351 adslAturPerfStatUasL, 1352 adslAturPerfCurr15MinSesL, 1353 adslAturPerfCurr15MinUasL, 1354 adslAturPerfCurr1DaySesL, 1355 adslAturPerfCurr1DayUasL, 1356 adslAturPerfPrev1DaySesL, 1357 adslAturPerfPrev1DayUasL, 1358 adslAturIntervalSesL, adslAturIntervalUasL 1359 } 1360 STATUS current 1361 DESCRIPTION 1362 "A collection of objects providing raw performance 1363 counts on an ADSL Line (ATU-C end)." 1364 ::= { adslExtGroups 3 } 1366 adslExtLineConfProfileControlGroup OBJECT-GROUP 1367 OBJECTS { 1368 adslConfProfileLineType 1369 } 1370 STATUS current 1371 DESCRIPTION 1372 "A collection of objects providing profile 1373 control for the ADSL system." 1374 ::= { adslExtGroups 4 } 1376 adslExtLineAlarmConfProfileGroup OBJECT-GROUP 1377 OBJECTS { 1378 adslAtucThreshold15MinFailedFastR, 1379 adslAtucThreshold15MinSesL, 1380 adslAtucThreshold15MinUasL, 1381 adslAturThreshold15MinSesL, 1382 adslAturThreshold15MinUasL 1383 } 1384 STATUS current 1385 DESCRIPTION 1386 "A collection of objects providing alarm profile 1387 control for the ADSL system." 1388 ::= { adslExtGroups 5 } 1390 adslExtNotificationsGroup NOTIFICATION-GROUP 1391 NOTIFICATIONS { 1392 adslAtucFailedFastRThreshTrap, 1393 adslAtucSesLThreshTrap, 1394 adslAtucUasLThreshTrap, 1395 adslAturSesLThreshTrap, 1396 adslAturUasLThreshTrap 1397 } 1398 STATUS current 1399 DESCRIPTION 1400 "The collection of ADSL extension notifications." 1401 ::= { adslExtGroups 6 } 1403 END 1405 9. Acknowledgments 1407 This document is a product of the ADSL MIB Working Group. 1409 10. References 1411 [ANSI T1.413] American National Standards Institute, ANSI T1.413, 1412 Issue 2, "Standards Project for Interfaces Relating 1413 to Carrier to Customer Connection of ADSL Equipment", 1414 1998. 1416 [ETSI DTS/TM06006] European Telecommunications Standards Institute 1417 "ADSL European Specific Requirements", November 1418 2000. 1420 [ITU G.992.1] ITU-T Telecommunication Standardization Sector, 1421 "Asymmetric digital subscriber line (ADSL) 1422 transceivers", June 1999. 1424 [ITU G.992.2] ITU-T Telecommunication Standardization Sector, 1425 "Splitterless asymmetric digital subscriber line 1426 (ADSL) transceivers", June 1999. 1428 [ITU G.997.1] ITU-T Telecommunication Standardization Sector, 1429 "Physical Layer Management of Digital Subscriber 1430 Transceivers", June 1999. 1432 [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification 1433 of Management Information for TCP/IP-based Internets", STD 1434 16, RFC 1155, May 1990. 1436 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 1437 Network Management Protocol", STD 15, RFC 1157, May 1990. 1439 [RFC1212] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16, 1440 RFC 1212, March 1991. 1442 [RFC1213] McCloghrie, K. and M. Rose, "Management Information Base for 1443 Network Management of TCP/IP-based internets - MIB-II", 1444 STD 17, RFC 1213, March 1991. 1446 [RFC1215] M. Rose, "A Convention for Defining Traps for use with the 1447 SNMP", RFC 1215, March 1991. 1449 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1450 "Introduction to Community-based SNMPv2", RFC 1901, January 1451 1996. 1453 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1454 "Protocol Operations for Version 2 of the Simple Network 1455 Management Protocol (SNMPv2)", RFC 1905, January 1996. 1457 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1458 "Transport Mappings for Version 2 of the Simple Network 1459 Management Protocol (SNMPv2)", RFC 1906, January 1996. 1461 [RFC2026] Bradner S., "The Internet Standards Process - Revision 3", 1462 October 1996. 1464 [RFC2028] Hovey R., S. Bradner, "The Organizations Involved in the 1465 IETF Standards Process", October 1996. 1467 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 1468 "Introduction to Version 3 of the Internet-standard Network 1469 Management Framework", RFC 2570, April 1999. 1471 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture 1472 for Describing SNMP Management Frameworks", RFC 2571, April 1473 1999. 1475 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 1476 Processing and Dispatching for the Simple Network Management 1477 Protocol (SNMP)", RFC 2572, April 1999. 1479 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", 1480 RFC 2573, April 1999. 1482 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 1483 (USM) for version 3 of the Simple Network Management 1484 Protocol (SNMPv3)", RFC 2574, April 1999. 1486 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 1487 Access Control Model (VACM) for the Simple Network 1488 Management Protocol (SNMP)", RFC 2575, April 1999. 1490 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1491 Rose, M., and S. Waldbusser, "Structure of Management 1492 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1493 1999. 1495 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1496 Rose, M., and S. Waldbusser, "Textual Conventions for 1497 SMIv2", STD 58, RFC 2579, April 1999. 1499 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1500 Rose, M., and S. Waldbusser, "Conformance Statements for 1501 SMIv2", STD 58, RFC 2580, April 1999. 1503 [RFC2662] Bathrick G., F. Ly "Definitions of Managed Objects for the 1504 ADSL Lines", May 1999. 1506 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", 1507 RFC 2863, June 2000. 1509 11. Security Considerations 1511 1) Blocking unauthorized access to the ADSL MIB via the element 1512 management system is outside the scope of this document. It should be 1513 noted that access to the MIB permits the unauthorized entity to 1514 modify the profiles (section 6.4) such that both subscriber service and 1515 network operations can be interfered with. Subscriber service can be 1516 altered by modifying any of a number of service characteristics such 1517 as rate partitioning and maximum transmission rates. Network 1518 operations can be impacted by modification of trap thresholds such as 1519 Signal-to-Noise Ratio (SNR) margins. 1521 2) There are a number of managed objects in this MIB that may be 1522 considered to contain sensitive information. In particular, the 1523 certain objects may be considered sensitive in many environments, 1525 since it would allow an intruder to obtain information about which 1526 vendor's equipment is in use on the network. Therefore, it may be 1527 important in some environments to control read access to these 1528 objects and possibly to even encrypt the values of these object when 1529 sending them over the network via SNMP. Not all versions of SNMP 1530 provide features for such a secure environment. 1532 SNMPv1 by itself is such an insecure environment. Even if the 1533 network itself is secure (for example by using IPSec), even then, 1534 there is no control as to who on the secure network is allowed to 1535 access and GET (read) the objects in this MIB. It is recommended 1536 that the implementors consider the security features as provided by 1537 the SNMPv3 framework. Specifically, the use of the User-based 1538 Security Model RFC 2574 [21] and the View-based Access Control Model 1539 RFC 2575 [23] is recommended. 1541 It is then a customer/user responsibility to ensure that the SNMP 1542 entity giving access to an instance of this MIB, is properly 1543 configured to give access to those objects only to those principals 1544 (users) that have legitimate rights to access them. 1546 The profile mechanism presented in this document requires specific 1547 attention. The implementor of this MIB has a choice of implementing 1548 either 'static' or 'dynamic' profiles. In the case of 'static' 1549 profiles, the elements of the profile are read-write as opposed to 1550 read-create when 'dynamic' profiles are implemented: 1551 adslConfProfileLineType, adslAtucThreshold15MinFailedFastR, 1552 adslAtucThreshold15MinSesL, adslAtucThreshold15MinUasL, 1553 adslAturThreshold15MinSesL, and adslAturThreshold15MinUasL. 1555 This decision also impacts the mechanics of the index, 1556 adslLineconfProfileDualLite. When 'static' profiles are implemented, 1557 its value is algorithmically set by the system and its value is 1558 based on the ifIndex, hence not guaranteed across system reboots. In 1559 the case of dynamic profiles, this object is set by the SNMP manager. 1560 The implementor of this MIB may want to provide view of the profile on 1561 a customer-by-customer standpoint, but should be cautious of the 1562 dynamic nature of these objects. 1564 3) ADSL layer connectivity from the ATU-R will permit the subscriber 1565 to manipulate both the ADSL link directly and the ADSL overhead 1566 control channel(AOC)/embedded operations channel (EOC) 1567 for their own loop. For example, unchecked or unfiltered 1568 fluctuations initiated by the subscriber could generate sufficient 1569 traps to potentially overwhelm either the management interface to the 1570 network or the element manager. Other attacks affecting the ATU-R 1571 portions of the MIB may also be possible. 1573 12. Intellectual Property Notice 1575 The IETF takes no position regarding the validity or scope of any 1576 intellectual property or other rights that might be claimed to 1577 pertain to the implementation or use of the technology described in 1578 this document or the extent to which any license under such rights 1579 might or might not be available; neither does it represent that it 1580 has made any effort to identify any such rights. Information on the 1581 IETF's procedures with respect to rights in standards-track and 1582 standards-related documentation can be found in BCP-11 [RFC2028]. 1583 Copies of claims of rights made available for publication and any 1584 assurances of licenses to be made available, or the result of an 1585 attempt made to obtain a general license or permission for the use 1586 of such proprietary rights by implementors or users of this 1587 specification can be obtained from the IETF Secretariat." 1589 The IETF invites any interested party to bring to its attention any 1590 copyrights, patents or patent applications, or other proprietary 1591 rights that may cover technology that may be required to practice 1592 this standard. Please address the information to the IETF Executive 1593 Director. 1595 13. Authors' Addresses 1597 Faye Ly 1598 Salira Optical Systems 1599 2698 Orchard Parkway 1600 San Jose, CA 95134, USA 1602 Phone: +1 408-382-0088 1603 Fax: +1 408-382-1688 1604 EMail: faye@salira.com 1606 Gregory Bathrick 1607 NOKIA High Speed Access Nodes 1608 1310 Redwood Way, 1609 Petaluma, CA 94954, USA 1611 Phone: +1 707-793-7030 1612 Fax: +1 707-792-0850 1613 EMail: greg.bathrick@nokia.com 1615 14. Full Copyright Statement 1617 Copyright (C) The Internet Society (2001). All Rights Reserved. 1619 This document and translations of it may be copied and furnished to 1620 others, and derivative works that comment on or otherwise explain it 1621 or assist in its implementation may be prepared, copied, published 1622 and distributed, in whole or in part, without restriction of any 1623 kind, provided that the above copyright notice and this paragraph are 1624 included on all such copies and derivative works. However, this 1625 document itself may not be modified in any way, such as by removing 1626 the copyright notice or references to the Internet Society or other 1627 Internet organizations, except as needed for the purpose of 1628 developing Internet standards in which case the procedures for 1629 copyrights defined in the Internet Standards process must be 1630 followed, or as required to translate it into languages other than 1631 English. 1633 The limited permissions granted above are perpetual and will not be 1634 revoked by the Internet Society or its successors or assigns. 1636 This document and the information contained herein is provided on an 1637 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1638 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1639 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1640 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1641 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1643 Acknowledgement 1645 Funding for the RFC Editor function is currently provided by the 1646 Internet Society. 1648 Table of Contents 1650 1. Status of this Memo ..................................... 1 1651 2. Abstract ............................................... 1 1652 3. The SNMP Network Management Framework ................... 1 1653 4. Introduction ............................................ 2 1654 5. Relationship of ADSL LINE EXTENSION MIB with standard MIBs. 3 1655 6. Conventions used in the MIB ............................. 3 1656 7. Conformance and Compliance .............................. 5 1657 8. Definitions ............................................. 5 1658 9. Acknowledgments ......................................... 25 1659 10. References ......................................... ... 26 1660 11. Security Considerations ............................ ... 27 1661 12. Intellectual Property Notice ......................... ... 27 1662 13. Authors' Addresses .................................. ... 28 1663 14. Full Copyright Statement ................................ 29