idnits 2.17.1 draft-ietf-adslmib-adslext-06.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? ** The document is more than 15 pages and seems to lack a Table of Contents. == 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 64 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: ' 10. 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. ** The abstract seems to contain references ([20], [2], [15], [3], [21], [16], [4], [22], [17], [5], [23], [18], [6], [19], [7], [8], [9], [10], [11], [14], [1]), 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 -- 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 (January 14, 2001) is 8504 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? '1' on line 1282 looks like a reference -- Missing reference section? '11' on line 1327 looks like a reference -- Missing reference section? '14' on line 1330 looks like a reference -- Missing reference section? '15' on line 1335 looks like a reference -- Missing reference section? '16' on line 1339 looks like a reference -- Missing reference section? '2' on line 1286 looks like a reference -- Missing reference section? '17' on line 1342 looks like a reference -- Missing reference section? '7' on line 1309 looks like a reference -- Missing reference section? '18' on line 1345 looks like a reference -- Missing reference section? '19' on line 1349 looks like a reference -- Missing reference section? '20' on line 1353 looks like a reference -- Missing reference section? '21' on line 1406 looks like a reference -- Missing reference section? '8' on line 1315 looks like a reference -- Missing reference section? '22' on line 1362 looks like a reference -- Missing reference section? '23' on line 1408 looks like a reference -- Missing reference section? '10' on line 1323 looks like a reference -- Missing reference section? '9' on line 1319 looks like a reference -- Missing reference section? '3' on line 1289 looks like a reference -- Missing reference section? '4' on line 1294 looks like a reference -- Missing reference section? '5' on line 1298 looks like a reference -- Missing reference section? '6' on line 1303 looks like a reference Summary: 11 errors (**), 0 flaws (~~), 3 warnings (==), 23 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET-DRAFT ADSL Line Extension MIB Faye Ly 3 Copper Mountain Networks 4 Gregory Bathrick 5 Nokia 6 January 14, 2001 8 Definitions of Extension Managed Objects 9 for ADSL Lines 11 January 14, 2001 13 draft-ietf-adslmib-adslext-06.txt 15 1. Status of this Memo 17 This document is an Internet-Draft and is in full conformance with 18 all provisions of Section 10 of RFC2026. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF), its areas, and its working groups. Note that other 22 groups may also distribute working documents as Internet-Drafts. 24 Internet-Drafts are draft documents valid for a maximum of six months 25 and may be updated, replaced, or obsoleted by other documents at any 26 time. It is inappropriate to use Internet-Drafts as reference 27 material or to cite them other than as ``work in progress.'' 29 The list of current Internet-Drafts can be accessed at 30 http://www.ietf.org/ietf/1id-abstracts.txt 32 The list of Internet-Draft Shadow Directories can be accessed at 33 http://www.ietf.org/shadow.html. 35 To view the entire list of current Internet-Drafts, please check the 36 "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow 37 Directories on ftp.is.co.za (Africa), ftp.nordu.net (Northern 38 Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au (Pacific 39 Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu (US West Coast). 41 2. Abstract 43 This document defines a standard SNMP MIB for additional functions 44 not covered by the ADSL Line MIB [1]. 46 3. The SNMP Network Management Framework 47 The SNMP Management Framework presently consists of five major 48 components: 50 o An overall architecture, described in RFC 2571 [11]. 52 o Mechanisms for describing and naming objects and events for the 53 purpose of management. The first version of this Structure of 54 Management Information (SMI) is called SMIv1 and described in 55 STD 56 16, RFC 1155 [14], STD 16, RFC 1212 [15] and RFC 1215 [16]. The 57 second version, called SMIv2, is described in STD 58, RFC 2578 58 [1], STD 58, RFC 2579 [2] and STD 58, RFC 2580 [17]. 60 o Message protocols for transferring management information. 61 The first version of the SNMP message protocol is called 62 SNMPv1 and described in RFC 1157 [7]. A second version of 63 the SNMP message protocol, which is not an Internet standards 64 track protocol, is called SNMPv2c and described in RFC 1901 65 [18] and RFC 1906 [19]. The third version of the message 66 protocol is called SNMPv3 and described in RFC 1906 [19], RFC 67 2272 [20] and RFC 2274 [21]. 69 o Protocol operations for accessing management information. 70 The first set of protocol operations and associated PDU 71 formats is described in RFC 1157 [7]. A second set of 72 protocol operations and associated PDU formats is described 73 in RFC 1905 [8]. 75 o A set of fundamental applications described in RFC 2273 [22] 76 and the view-based access control mechanism described in RFC 77 2275 [23]. 79 Managed objects are accessed via a virtual information store, termed 80 the Management Information Base or MIB. Objects in the MIB are 81 defined using the mechanisms defined in the SMI. 83 This document specifies a MIB module that is compliant to the SMIv2. 84 A MIB conforming to the SMIv1 can be produced through the appropriate 85 translations. The resulting translated MIB must be semantically 86 equivalent, except where objects or events are omitted because no 87 translation is possible (e.g., use of Counter64). Some machine 88 readable information in SMIv2 will be converted into textual 89 descriptions in SMIv1 during the translation process. However, this 90 loss of machine readable information is not considered to change the 91 semantics of the MIB. 93 4. Change Log 94 This section tracks changes made to the revisions of the Internet 95 Drafts of this document. It will be deleted when the document is 96 published as an RFC. 98 The following changes were made for the version of the document dated 99 May 10, 2000. 100 - Fixed the syntax AUGMENT for all tables. 101 - Corrected typos and added section 10, 11 and 12. 103 The following changes were made for the version of the document dated 104 May 10, 2000. 105 - Renamed adslLineTransAtucCapActual to adslLineTransAtucActual 107 The following changes were made for the version of the document dated 108 March 10, 2000. 109 - Added a new object in the adslLineExtTable describing the 110 G.lite power state. 112 The following changes were made for the version of the document dated 113 October 20, 1999. 115 - Changed adslLineExtTable to include config ATU-C, ATU-C and 116 ATU-R actual transmission capabilities. 117 - renamed adslProfileLineMode to adslProfileLineType to match 118 rfc2662 adslLineType object. 119 - Added two objects in the adslLineExtTable: one for 120 adslLineModeConfig and adslLineModeActual. 121 - Added a new textual convention for ADSL line mode. 122 - Corrected the MIB compiled errors and typos. 124 5. Introduction 126 The purpose of this memo is to define a supplemental set of 127 managed objects that is not covered by ADSL Line MIB as defined in 128 [10]. This memo addresses the additional objects defined in ITU 129 G.997.1 [8]. These additional objects specifically address the 130 management capabilities of ADSL "Lite" as defined by ITU-T G.992.2 131 [9]. 133 6. Relationship of the ADSL LINE EXTENSION MIB with standard MIBs 135 This section outlines the relationship of ADSL Line Extension MIB 136 with other MIBs described in RFCs and in their various degrees of 137 "standardization". ADSL Line Extension MIB obeys the same 138 relationship between ADSL Line MIB to other standard MIBs with one 139 exception for the ifOperStatus as defined in RFC 1213 [3]. 141 6.1 ifOperStatus 142 ifOperStatus is set to down(2) when the ADSL line interface is in 143 power state L2, which means no power. ifOperStatus is set to up(1) 144 if the ADSL line interface is in power state L0 (power on) or L1 145 (reduced power). 147 7. Conventions used in the MIB 149 7.1 Structure 151 The MIB is organized to follow the same structure of the ADSL Line 152 MIB [1]. 154 7.2 Additional Managed Objects 156 A few objects are added to cover the ADSL "Lite" management and they 157 are: 159 - ATU-C Transmission System and Line Mode 160 - Power Management 161 - Counters for Fast Retrains and Failed Fast Retrains 162 - Counters for Severe Error Second-line and Unavailable Second 163 - Alternative profile configuration for the Dual line mode 164 interface 166 Besides the management of ADSL "Lite", another object has been 167 added to the ADSL Line MIB [10] in order to manage the ADSL line 168 profile. The object is the line mode configuration. 170 The MIB definitions are attached. The MIB will be branched from 171 the ADSL Line MIB [10]. 173 7.2.1 ATU-C ADSL Transmission System Parameters and Line Mode 175 The adslLineConfigTable needs to be extended to cover control of 176 the ATU-C ADSL Transmission system. Three objects are defined to 177 monitor and configure the transmission mode as well as the actual 178 line mode: 180 - Capability 181 - Configuration 182 - Actual Status 184 Transmission modes can further determine the line mode of the 185 ADSL interface. For example, if g9921PotsNonOverlapped(2) is the 186 actual value of the ADSL interface, the interface is operating in 187 Full rate ADSL. If the interface is set to g9922PotsOverlapped(9), 188 the interface is operating in G.lite mode. 190 The transmssion mode and the corresponding line mode are defined 191 as: 193 Transmission mode Line Mode 194 ---------------------------------------------------------- 195 Regional Std. (ANSI T1.413) Full 196 Regional Std. (ETSI DTS/TM06006) Full 197 G.992.1 POTS non-overlapped Full 198 G.992.1 POTS overlapped Full 199 G.992.1 ISDN non-overlapped Full 200 G.992.1 ISDN overlapped Full 201 G.992.1 TCM-ISDN non-overlapped Full 202 G.992.1 TCM-ISDN overlapped Full 203 G.992.2 POTS non-overlapped Lite 204 G.992.2 POTS overlapped Lite 205 G.992.2 with TCM-ISDN non-overlapped Lite 206 G.992.2 with TCM-ISDN overlapped Lite 207 G.992.1 TCM-ISDN symmetric Full 209 Table 1: Transmission Mode and Line Mode 211 In case more than one bit is configured for an ADSL interface 212 and both Full and Lite modes are selected, the interface is said to 213 configure in the dual mode. Only one bit can be set in the Actual 214 object that reflects the actual mode of transmission as well as the 215 line mode. 217 7.2.2 Power Management 219 There are three power states for each managed ADSL interface 220 operating in the G.lite mode. L0 is power on, L1 is power on but 221 reduced and L2 is power off. Power state cannot be configured by an 222 operator but it can be viewed via the ifOperStatus object for the 223 managed ADSL interface. The value of the object ifOperStatus is set 224 to down(2) if the ADSL interface is in power state L2 and is set to 225 up(1) if the ADSL line interface is in power state L0 or L1. 227 An ADSL line power state, if the interface is operating in the 228 G.lite mode, can also be monitored by the adslLineGlitePowerState 229 object defined in the ADSL Line Extension table. The value of the 230 object enumerates the three power states attainable by the managed 231 interface. 233 7.2.3 Fast Retrain Parameters 235 Section 7.4.15 of ITU G.997.1 specifies fast retrain parameters. 236 Fast retrain parameters include two counters: fast retrain count and 237 failed fast retrain count. These two counters have been added to all 238 performance tables. 240 7.2.4 Counters for Severe Error Second-line and Unavailable Second 242 Section 7.2.1.1.7 and section 7.2.1.1.9 specify two counters 243 that are not covered by the ADSL Line MIB [10]. These two counters 244 (severe error seconds-line and unavailable seconds) are added to all 245 the performance tables. 247 Unavailable seconds counts cumulative number of seconds in which 248 the interface was unavailable during the measured period. This 249 counter does not include the seconds in which unavailability was 250 caused solely by fast retrains and failed fast retrins. Fast 251 retrains and failed fast retrains are considered to be part of the 252 normal network operation and thus are not counted as unavailable 253 errors. 255 7.2.5 Alternative profile configuration for the Dual line mode 256 interface 258 This object is used only when the interface (for the ADSL line 259 or channel) is configured as dual mode, that is, the object 260 adslLineTransAtucConfig is configued with one or more full-rate modes 261 and one or more Lite modes. 263 The object adslLineConfProfile defined in ADSL-MIB [10] is used 264 as the primary full-rate profile. The newly added object in this MIB 265 module, adslLineConfProfileDualLite is used to describe or configure 266 the Lite profile. Note that if one or more full-rate modes are 267 configured, or only lite modes are configured, only the original 268 full-rate profile is needed. The dual-mode profile object is only 269 needed when both full-rate and lite profiles are needed. 271 If the static profile is used, the profile name is the ifIndex 272 ASCII string plus the differentiator string appended to the end of 273 the static profile name. For example, for interface 100, the object 274 adslLineConfProfile is set by the agent to be "100Full" and the 275 object adslLineConfProfileDualLite is set to be "100Lite". 277 8. Conformance and Compliance 279 See the conformance and compliance statements within the information 280 module. 282 9. Definitions 284 ADSL-LINE-EXT-MIB DEFINITIONS ::= BEGIN 285 IMPORTS 286 Counter32, 287 Unsigned32, 288 NOTIFICATION-TYPE, 289 MODULE-IDENTITY, Gauge32, 290 OBJECT-TYPE, mib-2 FROM SNMPv2-SMI 291 MODULE-COMPLIANCE, OBJECT-GROUP, 292 NOTIFICATION-GROUP FROM SNMPv2-CONF 293 TEXTUAL-CONVENTION FROM SNMPv2-TC 294 PerfCurrentCount, 295 PerfIntervalCount FROM PerfHist-TC-MIB 296 AdslPerfCurrDayCount, 297 AdslPerfPrevDayCount, 298 AdslPerfTimeElapsed, 299 AdslLineCodingType FROM ADSL-TC-MIB 300 ifIndex FROM IF-MIB 301 SnmpAdminString FROM SNMP-FRAMEWORK-MIB 302 adslLineConfProfileName, 303 adslAtucIntervalNumber, 304 adslAturIntervalNumber, 305 adslLineAlarmConfProfileName, 306 adslMIB FROM ADSL-LINE-MIB 307 ; 309 adslExtMIB MODULE-IDENTITY 311 LAST-UPDATED "0101141200Z" 313 ORGANIZATION "IETF ADSL MIB Working Group" 315 CONTACT-INFO 316 " 317 Faye Ly 318 Copper Mountain Networks 319 Norcal Office 320 2470 Embarcadero Way 321 Palo Alto, CA 94303 322 Tel: +1 650-687-3323 323 Fax: +1 650-687-3372 324 E-Mail: faye@coppermountain.com 326 Gregory Bathrick 327 NOKIA High Speed Access Nodes 328 1310 Redwood Way, 329 Petaluma, CA 94954, USA 330 Tel: +1 707-793-7030 331 Fax: +1 707-792-0850 332 E-Mail: greg.bathrick@nokia.com" 334 DESCRIPTION 335 "This MIB Module is a supplement to the ADSL-LINE-MIB [1]." 336 ::= { adslMIB 3 } 338 adslExtMibObjects OBJECT IDENTIFIER ::= { adslExtMIB 1 } 340 AdslTransmissionModeType ::= TEXTUAL-CONVENTION 341 STATUS current 342 DESCRIPTION 343 "A set of ADSL line transmission modes, with one bit 344 per mode. The notes (F) and (L) denote Full-Rate 345 and Lite respectively: 346 Bit 00 : Regional Std. (ANSI T1.413) (F) 347 Bit 01 : Regional Std. (ETSI DTS/TM06006) (F) 348 Bit 02 : G.992.1 POTS non-overlapped (F) 349 Bit 03 : G.992.1 POTS overlapped (F) 350 Bit 04 : G.992.1 ISDN non-overlapped (F) 351 Bit 05 : G.992.1 ISDN overlapped (F) 352 Bit 06 : G.992.1 TCM-ISDN non-overlapped (F) 353 Bit 07 : G.992.1 TCM-ISDN overlapped (F) 354 Bit 08 : G.992.2 POTS non-overlapped (L) 355 Bit 09 : G.992.2 POTS overlapped (L) 356 Bit 10 : G.992.2 with TCM-ISDN non-overlapped (L) 357 Bit 11 : G.992.2 with TCM-ISDN overlapped (L) 358 Bit 12 : G.992.1 TCM-ISDN symmetric (F) 359 " 360 SYNTAX BITS { 361 ansit1413(0), 362 etsi(1), 363 q9921PotsNonOverlapped(2), 364 q9921PotsOverlapped(3), 365 q9921IsdnNonOverlapped(4), 366 q9921isdnOverlapped(5), 367 q9921tcmIsdnNonOverlapped(6), 368 q9921tcmIsdnOverlapped(7), 369 q9922potsNonOverlapeed(8), 370 q9922potsOverlapped(9), 371 q9922tcmIsdnNonOverlapped(10), 372 q9922tcmIsdnOverlapped(11), 373 q9921tcmIsdnSymmetric(12) 374 } 376 adslLineExtTable OBJECT-TYPE 377 SYNTAX SEQUENCE OF AdslLineExtEntry 378 MAX-ACCESS not-accessible 379 STATUS current 380 DESCRIPTION 381 "This table contains ADSL line configuration and 383 monitoring 384 information not defined in the adslLineTable from 385 the 386 ADSL-LINE-MIB [1]. This includes the capabilities 387 and 388 actual ADSL transmission system." 389 ::= { adslExtMibObjects 17 } 391 adslLineExtEntry OBJECT-TYPE 392 SYNTAX AdslLineExtEntry 393 MAX-ACCESS not-accessible 394 STATUS current 395 DESCRIPTION 396 "An entry extends the adslLineEntry defined in [1]. 397 Each 398 entry corresponds to an ADSL line." 399 INDEX { ifIndex } 400 ::= { adslLineExtTable 1 } 402 AdslLineExtEntry ::= 403 SEQUENCE { 404 adslLineTransAtucCap AdslTransmissionModeType, 405 adslLineTransAtucConfig AdslTransmissionModeType, 406 adslLineTransAtucActual AdslTransmissionModeType, 407 adslLineGlitePowerState INTEGER, 408 adslLineConfProfileDualLite SnmpAdminString 409 } 411 adslLineTransAtucCap OBJECT-TYPE 412 SYNTAX AdslTransmissionModeType 413 MAX-ACCESS read-only 414 STATUS current 415 DESCRIPTION 416 "The transmission modes that the ATU-C is capable 417 of supporting. The modes available are limited 418 by the design of the equipment." 419 REFERENCE "Section 7.3.2 ITU G.997.1 [8]" 420 ::= { adslLineExtEntry 1 } 422 adslLineTransAtucConfig OBJECT-TYPE 423 SYNTAX AdslTransmissionModeType 424 MAX-ACCESS read-write 425 STATUS current 426 DESCRIPTION 427 "The transmission modes that the ATU-C must enable 428 for the line. The ATU-C's enable modes must be 429 a subset of its capable modes." 430 REFERENCE "Section 7.3.2 ITU G.997.1 [8]" 432 ::= { adslLineExtEntry 2 } 434 adslLineTransAtucActual OBJECT-TYPE 435 SYNTAX AdslTransmissionModeType 436 MAX-ACCESS read-only 437 STATUS current 438 DESCRIPTION 439 "The transmission mode of the ATU-C. This object 440 returns 0 (i.e BITS with no mode bit set) if there 441 is no mode currently known. The initialization 442 with the ATU-R will determine the mode used 443 and the result must be a one-mode subset of the 444 'Enable' modes. After an initialization has 445 occurred, 446 its mode is saved as the 'Current' mode and it 447 should persist even if the link goes down 448 subsequently. This leaves a hint on what may be 449 used next time." 450 REFERENCE "Section 7.3.2 ITU G.997.1 [8]" 451 ::= { adslLineExtEntry 3 } 453 adslLineGlitePowerState OBJECT-TYPE 454 SYNTAX INTEGER { 455 none(1), 456 l0(2), -- L0 Power on 457 l1(3), -- L1 Power on but reduced 458 l2(4) -- L2 Power off 459 } 460 MAX-ACCESS read-only 461 STATUS current 462 DESCRIPTION 463 "The value of this object specifies the power state 464 this interface is in. If the object 465 adslLineModeActual 466 is set to glite, the value of this object can be 467 either 468 one of the power state from L0 to L2. If the 469 object 470 adslLineTransAtucActual is set to other than 471 G.lite, 472 the value of this object is always set to none(1)." 473 ::= { adslLineExtEntry 4 } 475 adslLineConfProfileDualLite OBJECT-TYPE 476 SYNTAX SnmpAdminString 477 MAX-ACCESS read-write 478 STATUS current 479 DESCRIPTION 480 "The value of this object identifies the row 481 in the ADSL Line Configuration Profile Table, 482 (adslLineConfProfileTable), which applies for this 483 ADSL line, and channels if applicable, when the mode 484 after initialization is any G.992.2 (G.lite) mode 485 AND adslLineTransAtucConfig has enabled dual-mode. 486 Dual-mode in this case means one or more Full-Rate 487 modes AND one or more Lite modes enabled. 489 If dual-mode has not been enabled by this MIB or if 490 the ATU-C does not support this extension MIB, then 491 the previously existing adslLineConfProfile is used 492 even if the ATU-C mode is one of the G.992.2 modes." 493 ::= { adslLineExtEntry 5 } 495 adslAtucPerfDataExtTable OBJECT-TYPE 496 SYNTAX SEQUENCE OF AdslAtucPerfDataExtEntry 497 MAX-ACCESS not-accessible 498 STATUS current 499 DESCRIPTION 500 "This table contains ADSL physical line counters 501 information not defined in the adslAtucPerfDataTable from the ADSL- 502 LINE-MIB [10]." 503 ::= { adslExtMibObjects 18 } 505 adslAtucPerfDataExtEntry OBJECT-TYPE 506 SYNTAX AdslAtucPerfDataExtEntry 507 MAX-ACCESS not-accessible 508 STATUS current 509 DESCRIPTION 510 "An entry extends the adslAtucPerfDataEntry defined 511 in [10]. Each entry corresponds to an ADSL line." 512 INDEX { ifIndex } 513 ::= { adslAtucPerfDataExtTable 1 } 515 AdslAtucPerfDataExtEntry ::= 516 SEQUENCE { 517 adslAtucPerfStatFastR Counter32, 518 adslAtucPerfStatFailedFastR Counter32, 519 adslAtucPerfStatSesL Counter32, 520 adslAtucPerfStatUasL Counter32, 521 adslAtucPerfCurr15MinFastR PerfCurrentCount, 522 adslAtucPerfCurr15MinFailedFastR PerfCurrentCount, 523 adslAtucPerfCurr15MinSesL PerfCurrentCount, 524 adslAtucPerfCurr15MinUasL PerfCurrentCount, 525 adslAtucPerfCurr1DayFastR AdslPerfCurrDayCount, 526 adslAtucPerfCurr1DayFailedFastR AdslPerfCurrDayCount, 527 adslAtucPerfCurr1DaySesL AdslPerfCurrDayCount, 528 adslAtucPerfCurr1DayUasL AdslPerfCurrDayCount, 529 adslAtucPerfPrev1DayFastR AdslPerfPrevDayCount, 530 adslAtucPerfPrev1DayFailedFastR AdslPerfPrevDayCount, 531 adslAtucPerfPrev1DaySesL AdslPerfPrevDayCount, 532 adslAtucPerfPrev1DayUasL AdslPerfPrevDayCount 533 } 535 adslAtucPerfStatFastR OBJECT-TYPE 536 SYNTAX Counter32 537 MAX-ACCESS read-only 538 STATUS current 539 DESCRIPTION 540 "The value of this object indicates the count of 541 fast retrains." 542 REFERENCE "ITU G.997.1 Section 7.4.15.1 [8]" 543 ::= { adslAtucPerfDataExtEntry 1 } 545 adslAtucPerfStatFailedFastR OBJECT-TYPE 546 SYNTAX Counter32 547 MAX-ACCESS read-only 548 STATUS current 549 DESCRIPTION 550 "The value of this object indicates the count of 551 failed fast retrains." 552 REFERENCE "ITU G.997.1 Section 7.4.15.2 [8]" 553 ::= { adslAtucPerfDataExtEntry 2 } 555 adslAtucPerfStatSesL OBJECT-TYPE 556 SYNTAX Counter32 557 UNITS "seconds" 558 MAX-ACCESS read-only 559 STATUS current 560 DESCRIPTION 561 "The value of this object indicates the count of 562 severely errored second-line." 563 REFERENCE "ITU G.997.1 Section 7.2.1.1.7 [8]" 564 ::= { adslAtucPerfDataExtEntry 3 } 566 adslAtucPerfStatUasL OBJECT-TYPE 567 SYNTAX Counter32 568 UNITS "seconds" 569 MAX-ACCESS read-only 570 STATUS current 571 DESCRIPTION 572 "The value of this object indicates the count of 573 unavailable second." 574 REFERENCE "ITU G.997.1 Section 7.2.1.1.9 [8]" 575 ::= { adslAtucPerfDataExtEntry 4 } 576 adslAtucPerfCurr15MinFastR OBJECT-TYPE 577 SYNTAX PerfCurrentCount 578 UNITS "seconds" 579 MAX-ACCESS read-only 580 STATUS current 581 DESCRIPTION 582 "Count of seconds in the current 15 minute interval 583 when there was fast retrains." 584 REFERENCE "ITU G.997.1 Section 7.4.15.1 [8]" 585 ::= { adslAtucPerfDataExtEntry 5 } 587 adslAtucPerfCurr15MinFailedFastR OBJECT-TYPE 588 SYNTAX PerfCurrentCount 589 UNITS "seconds" 590 MAX-ACCESS read-only 591 STATUS current 592 DESCRIPTION 593 "Count of seconds in the current 15 minute interval 594 when there was failed fast retrains." 595 REFERENCE "ITU G.997.1 Section 7.4.15.2 [8]" 596 ::= { adslAtucPerfDataExtEntry 6 } 598 adslAtucPerfCurr15MinSesL OBJECT-TYPE 599 SYNTAX PerfCurrentCount 600 UNITS "seconds" 601 MAX-ACCESS read-only 602 STATUS current 603 DESCRIPTION 604 "Count of seconds in the current 15 minute interval 605 when there was fast retrains." 606 REFERENCE "ITU G.997.1 Section 7.2.1.1.7 [8]" 607 ::= { adslAtucPerfDataExtEntry 7 } 609 adslAtucPerfCurr15MinUasL OBJECT-TYPE 610 SYNTAX PerfCurrentCount 611 UNITS "seconds" 612 MAX-ACCESS read-only 613 STATUS current 614 DESCRIPTION 615 "Count of seconds in the current 15 minute interval 616 when there was count for unavailable errored 617 seconds." 618 REFERENCE "ITU G.997.1 Section 7.2.1.1.9 [8]" 619 ::= { adslAtucPerfDataExtEntry 8 } 621 adslAtucPerfCurr1DayFastR OBJECT-TYPE 622 SYNTAX AdslPerfCurrDayCount 623 UNITS "seconds" 624 MAX-ACCESS read-only 625 STATUS current 626 DESCRIPTION 627 "Count of the number of seconds when there was fast 628 retrains during the current day as measured by 629 adslAtucPerfCurr1DayTimeElapsed." 630 REFERENCE "ITU G.997.1 Section 7.4.15.1 [8]" 631 ::= { adslAtucPerfDataExtEntry 9 } 633 adslAtucPerfCurr1DayFailedFastR OBJECT-TYPE 634 SYNTAX AdslPerfCurrDayCount 635 UNITS "seconds" 636 MAX-ACCESS read-only 637 STATUS current 638 DESCRIPTION 639 "Count of the number of seconds when there was 640 failed 641 fast retrains during the current day as measured by 642 adslAtucPerfCurr1DayTimeElapsed." 643 REFERENCE "ITU G.997.1 Section 7.4.15.2 [8]" 644 ::= { adslAtucPerfDataExtEntry 10 } 646 adslAtucPerfCurr1DaySesL OBJECT-TYPE 647 SYNTAX AdslPerfCurrDayCount 648 UNITS "seconds" 649 MAX-ACCESS read-only 650 STATUS current 651 DESCRIPTION 652 "Count of the number of seconds when there was 653 Severe 654 Errored Seconds during the current day as measured 655 by 656 adslAtucPerfCurr1DayTimeElapsed." 657 REFERENCE "ITU G.997.1 Section 7.2.1.1.7 [8]" 658 ::= { adslAtucPerfDataExtEntry 11 } 660 adslAtucPerfCurr1DayUasL OBJECT-TYPE 661 SYNTAX AdslPerfCurrDayCount 662 UNITS "seconds" 663 MAX-ACCESS read-only 664 STATUS current 665 DESCRIPTION 666 "Count of the number of seconds when there was 667 Unavailable 668 Errored Seconds during the current day as measured 669 by 670 adslAtucPerfCurr1DayTimeElapsed." 671 REFERENCE "ITU G.997.1 Section 7.2.1.1.9 [8]" 673 ::= { adslAtucPerfDataExtEntry 12 } 675 adslAtucPerfPrev1DayFastR OBJECT-TYPE 676 SYNTAX AdslPerfPrevDayCount 677 UNITS "seconds" 678 MAX-ACCESS read-only 679 STATUS current 680 DESCRIPTION 681 "Count of seconds in the interval when there was 682 fast retrains within the most recent previous 683 1-day period." 684 REFERENCE "ITU G.997.1 Section 7.4.15.1 [8]" 685 ::= { adslAtucPerfDataExtEntry 13 } 687 adslAtucPerfPrev1DayFailedFastR OBJECT-TYPE 688 SYNTAX AdslPerfPrevDayCount 689 UNITS "seconds" 690 MAX-ACCESS read-only 691 STATUS current 692 DESCRIPTION 693 "Count of seconds in the interval when there was 694 failed fast retrains within the most recent previous 695 1-day period." 696 REFERENCE "ITU G.997.1 Section 7.4.15.2 [8]" 697 ::= { adslAtucPerfDataExtEntry 14 } 699 adslAtucPerfPrev1DaySesL OBJECT-TYPE 700 SYNTAX AdslPerfPrevDayCount 701 UNITS "seconds" 702 MAX-ACCESS read-only 703 STATUS current 704 DESCRIPTION 705 "Count of seconds in the interval when there was 706 severed errored seconds within the most recent 707 previous 708 1-day period." 709 REFERENCE "ITU G.997.1 Section 7.2.1.1.7 [8]" 710 ::= { adslAtucPerfDataExtEntry 15 } 712 adslAtucPerfPrev1DayUasL OBJECT-TYPE 713 SYNTAX AdslPerfPrevDayCount 714 UNITS "seconds" 715 MAX-ACCESS read-only 716 STATUS current 717 DESCRIPTION 718 "Count of seconds in the interval when there was 719 unavailable errored seconds within the most recent 720 previous 721 1-day period." 722 REFERENCE "ITU G.997.1 Section 7.2.1.1.9 [8]" 723 ::= { adslAtucPerfDataExtEntry 16 } 725 adslAtucIntervalExtTable OBJECT-TYPE 726 SYNTAX SEQUENCE OF AdslAtucIntervalExtEntry 727 MAX-ACCESS not-accessible 728 STATUS current 729 DESCRIPTION 730 "This table provides one row for each ATUC 731 performance data collection interval. 732 ADSL physical interfaces are 733 those ifEntries where ifType is equal to adsl(94)." 734 ::= { adslExtMibObjects 19 } 736 adslAtucIntervalExtEntry OBJECT-TYPE 737 SYNTAX AdslAtucIntervalExtEntry 738 MAX-ACCESS not-accessible 739 STATUS current 740 DESCRIPTION "An entry in the 741 adslAtucIntervalExtTable." 742 INDEX { ifIndex, adslAtucIntervalNumber } 743 ::= { adslAtucIntervalExtTable 1 } 745 AdslAtucIntervalExtEntry ::= 746 SEQUENCE { 747 adslAtucIntervalFastR PerfIntervalCount, 748 adslAtucIntervalFailedFastR PerfIntervalCount, 749 adslAtucIntervalSesL PerfIntervalCount, 750 adslAtucIntervalUasL PerfIntervalCount 751 } 753 adslAtucIntervalFastR OBJECT-TYPE 754 SYNTAX PerfIntervalCount 755 UNITS "seconds" 756 MAX-ACCESS read-only 757 STATUS current 758 DESCRIPTION 759 "Count of seconds in the interval when there was 760 Fast 761 Retrains." 762 ::= { adslAtucIntervalExtEntry 1 } 764 adslAtucIntervalFailedFastR OBJECT-TYPE 765 SYNTAX PerfIntervalCount 766 UNITS "seconds" 767 MAX-ACCESS read-only 768 STATUS current 769 DESCRIPTION 770 "Count of seconds in the interval when there was 771 Failed 772 Fast Retrains." 773 ::= { adslAtucIntervalExtEntry 2 } 775 adslAtucIntervalSesL OBJECT-TYPE 776 SYNTAX PerfIntervalCount 777 UNITS "seconds" 778 MAX-ACCESS read-only 779 STATUS current 780 DESCRIPTION 781 "Count of seconds in the interval when there was 782 severed errors." 783 ::= { adslAtucIntervalExtEntry 3 } 785 adslAtucIntervalUasL OBJECT-TYPE 786 SYNTAX PerfIntervalCount 787 UNITS "seconds" 788 MAX-ACCESS read-only 789 STATUS current 790 DESCRIPTION 791 "Count of seconds in the interval when there was 792 unavailable errors." 793 ::= { adslAtucIntervalExtEntry 4 } 795 adslAturPerfDataExtTable OBJECT-TYPE 796 SYNTAX SEQUENCE OF AdslAturPerfDataExtEntry 797 MAX-ACCESS not-accessible 798 STATUS current 799 DESCRIPTION 800 "This table contains ADSL physical line counters 801 information not defined in the adslAturPerfDataTable from the ADSL- 802 LINE-MIB [10]." 803 ::= { adslExtMibObjects 20 } 805 adslAturPerfDataExtEntry OBJECT-TYPE 806 SYNTAX AdslAturPerfDataExtEntry 807 MAX-ACCESS not-accessible 808 STATUS current 809 DESCRIPTION 810 "An entry extends the adslAturPerfDataEntry defined 811 in [10]. Each entry corresponds to an ADSL line." 812 INDEX { ifIndex } 813 ::= { adslAturPerfDataExtTable 1 } 815 AdslAturPerfDataExtEntry ::= 816 SEQUENCE { 817 adslAturPerfStatSesL Counter32, 818 adslAturPerfStatUasL Counter32, 819 adslAturPerfCurr15MinSesL PerfCurrentCount, 820 adslAturPerfCurr15MinUasL PerfCurrentCount, 821 adslAturPerfCurr1DaySesL AdslPerfCurrDayCount, 822 adslAturPerfCurr1DayUasL AdslPerfCurrDayCount, 823 adslAturPerfPrev1DaySesL AdslPerfPrevDayCount, 824 adslAturPerfPrev1DayUasL AdslPerfPrevDayCount 825 } 827 adslAturPerfStatSesL OBJECT-TYPE 828 SYNTAX Counter32 829 UNITS "seconds" 830 MAX-ACCESS read-only 831 STATUS current 832 DESCRIPTION 833 "The value of this object indicates the count of 834 severely errored second-line." 835 REFERENCE "ITU G.997.1 Section 7.2.1.1.7 [8]" 836 ::= { adslAturPerfDataExtEntry 1 } 838 adslAturPerfStatUasL OBJECT-TYPE 839 SYNTAX Counter32 840 UNITS "seconds" 841 MAX-ACCESS read-only 842 STATUS current 843 DESCRIPTION 844 "The value of this object indicates the count of 845 unavailable second." 846 REFERENCE "ITU G.997.1 Section 7.2.1.2.9 [8]" 847 ::= { adslAturPerfDataExtEntry 2 } 849 adslAturPerfCurr15MinSesL OBJECT-TYPE 850 SYNTAX PerfCurrentCount 851 UNITS "seconds" 852 MAX-ACCESS read-only 853 STATUS current 854 DESCRIPTION 855 "Count of seconds in the current 15 minute interval 856 when there was Severe Errored Seconds-Line." 857 REFERENCE "ITU G.997.1 Section 7.2.1.2.7 [8]" 858 ::= { adslAturPerfDataExtEntry 3 } 860 adslAturPerfCurr15MinUasL OBJECT-TYPE 861 SYNTAX PerfCurrentCount 862 UNITS "seconds" 863 MAX-ACCESS read-only 864 STATUS current 865 DESCRIPTION 866 "Count of seconds in the current 15 minute interval 867 when there was Unavailable Errored Seconds." 868 REFERENCE "ITU G.997.1 Section 7.2.1.2.9 [8]" 869 ::= { adslAturPerfDataExtEntry 4 } 871 adslAturPerfCurr1DaySesL OBJECT-TYPE 872 SYNTAX AdslPerfCurrDayCount 873 UNITS "seconds" 874 MAX-ACCESS read-only 875 STATUS current 876 DESCRIPTION 877 "Count of the number of seconds when there was 878 Severe 879 Errored Seconds during the current day as measured 880 by 881 adslAturPerfCurr1DayTimeElapsed." 882 REFERENCE "ITU G.997.1 Section 7.2.1.2.7 [8]" 883 ::= { adslAturPerfDataExtEntry 5 } 885 adslAturPerfCurr1DayUasL OBJECT-TYPE 886 SYNTAX AdslPerfCurrDayCount 887 UNITS "seconds" 888 MAX-ACCESS read-only 889 STATUS current 890 DESCRIPTION 891 "Count of the number of seconds when there was 892 Unavailable 893 Errored Seconds during the current day as measured 894 by 895 adslAturPerfCurr1DayTimeElapsed." 896 REFERENCE "ITU G.997.1 Section 7.2.1.2.9 [8]" 897 ::= { adslAturPerfDataExtEntry 6 } 899 adslAturPerfPrev1DaySesL OBJECT-TYPE 900 SYNTAX AdslPerfPrevDayCount 901 UNITS "seconds" 902 MAX-ACCESS read-only 903 STATUS current 904 DESCRIPTION 905 "Count of seconds in the interval when there was 906 severed errored second within the most recent 907 previous 908 1-day period." 909 REFERENCE "ITU G.997.1 Section 7.2.1.2.7 [8]" 910 ::= { adslAturPerfDataExtEntry 7 } 911 adslAturPerfPrev1DayUasL OBJECT-TYPE 912 SYNTAX AdslPerfPrevDayCount 913 UNITS "seconds" 914 MAX-ACCESS read-only 915 STATUS current 916 DESCRIPTION 917 "Count of seconds in the interval when there was 918 unavailable errored second within the most recent 919 previous 920 1-day period." 921 REFERENCE "ITU G.997.1 Section 7.2.1.2.9 [8]" 922 ::= { adslAturPerfDataExtEntry 8 } 924 adslAturIntervalExtTable OBJECT-TYPE 925 SYNTAX SEQUENCE OF AdslAturIntervalExtEntry 926 MAX-ACCESS not-accessible 927 STATUS current 928 DESCRIPTION 929 "This table provides one row for each ATUC 930 performance data collection interval. 931 ADSL physical interfaces are 932 those ifEntries where ifType is equal to adsl(94)." 933 ::= { adslExtMibObjects 21 } 935 adslAturIntervalExtEntry OBJECT-TYPE 936 SYNTAX AdslAturIntervalExtEntry 937 MAX-ACCESS not-accessible 938 STATUS current 939 DESCRIPTION "An entry in the 940 adslAturIntervalExtTable." 941 INDEX { ifIndex, adslAturIntervalNumber } 942 ::= { adslAturIntervalExtTable 1 } 944 AdslAturIntervalExtEntry ::= 945 SEQUENCE { 946 adslAturIntervalSesL PerfIntervalCount, 947 adslAturIntervalUasL PerfIntervalCount 948 } 950 adslAturIntervalSesL OBJECT-TYPE 951 SYNTAX PerfIntervalCount 952 UNITS "seconds" 953 MAX-ACCESS read-only 954 STATUS current 955 DESCRIPTION 956 "Count of seconds in the interval when there was 957 severed errors." 958 ::= { adslAturIntervalExtEntry 1 } 959 adslAturIntervalUasL OBJECT-TYPE 960 SYNTAX PerfIntervalCount 961 UNITS "seconds" 962 MAX-ACCESS read-only 963 STATUS current 964 DESCRIPTION 965 "Count of seconds in the interval when there was 966 unavailable errors." 967 ::= { adslAturIntervalExtEntry 2 } 969 adslConfProfileExtTable OBJECT-TYPE 970 SYNTAX SEQUENCE OF AdslConfProfileExtEntry 971 MAX-ACCESS not-accessible 972 STATUS current 973 DESCRIPTION 974 "This table contains ADSL line profile configuration 975 information not defined in the 976 adslLineConfProfileTable 977 from the ADSL-LINE-MIB [1]. This includes the line 978 mode." 979 ::= { adslExtMibObjects 22 } 981 adslConfProfileExtEntry OBJECT-TYPE 982 SYNTAX AdslConfProfileExtEntry 983 MAX-ACCESS not-accessible 984 STATUS current 985 DESCRIPTION 986 "An entry extends the adslLineConfProfileEntry 987 defined in [1]. 988 Each entry corresponds to an ADSL line profile." 989 INDEX { IMPLIED adslLineConfProfileName} 990 ::= { adslConfProfileExtTable 1 } 992 AdslConfProfileExtEntry ::= 993 SEQUENCE { 994 adslConfProfileLineType INTEGER 995 } 997 adslConfProfileLineType OBJECT-TYPE 998 SYNTAX INTEGER { 999 noChannel (1), -- no channels exist 1000 fastOnly (2), -- fast channel exists only 1001 interleavedOnly (3), -- interleaved channel exists 1002 -- only 1003 fastOrInterleaved (4),-- either fast or interleaved 1004 -- channels can exist, but 1005 -- only one at any time 1006 fastAndInterleaved (5)-- both fast or interleaved 1007 -- channels exist 1008 } 1009 MAX-ACCESS read-create 1010 STATUS current 1011 DESCRIPTION 1012 " 1013 This object is used to configure the ADSL physical 1014 line 1015 mode. " 1016 ::= { adslConfProfileExtEntry 1 } 1018 adslAlarmConfProfileExtTable OBJECT-TYPE 1019 SYNTAX SEQUENCE OF AdslAlarmConfProfileExtEntry 1020 MAX-ACCESS not-accessible 1021 STATUS current 1022 DESCRIPTION 1023 "This table extends the 1024 adslLineAlarmConfProfileTable and 1025 provides threshold parameters for all the counters 1026 defined 1027 in this MIB module." 1028 ::= { adslExtMibObjects 23 } 1030 adslAlarmConfProfileExtEntry OBJECT-TYPE 1031 SYNTAX AdslAlarmConfProfileExtEntry 1032 MAX-ACCESS not-accessible 1033 STATUS current 1034 DESCRIPTION 1035 "An entry extends the adslLineAlarmConfProfileTable 1036 defined in [10]. Each entry corresponds to an ADSL alarm profile." 1037 INDEX { IMPLIED adslLineAlarmConfProfileName} 1038 ::= { adslAlarmConfProfileExtTable 1 } 1040 AdslAlarmConfProfileExtEntry ::= 1041 SEQUENCE { 1042 adslAtucThreshold15MinFailedFastR Unsigned32, 1043 adslAtucThreshold15MinSesL Unsigned32, 1044 adslAtucThreshold15MinUasL Unsigned32 1045 } 1047 adslAtucThreshold15MinFailedFastR OBJECT-TYPE 1048 SYNTAX Unsigned32 1049 UNITS "seconds" 1050 MAX-ACCESS read-create 1051 STATUS current 1052 DESCRIPTION 1053 "The number of failed retrains encountered by an 1054 ADSL interface within any giving 15 minutes 1056 performance 1057 data collection period, which cause the SNMP agent 1058 to send an adslAtucFailedFastRTrap. One trap will 1059 be 1060 sent per interval per interface. A value '0' will 1061 disable the trap." 1062 ::= { adslAlarmConfProfileExtEntry 1 } 1064 adslAtucThreshold15MinSesL OBJECT-TYPE 1065 SYNTAX Unsigned32 1066 UNITS "seconds" 1067 MAX-ACCESS read-create 1068 STATUS current 1069 DESCRIPTION 1070 "The number of Severe errored seconds encountered by 1071 an 1072 ADSL interface withing any giving 15 minutes 1073 performance 1074 data collection period, which cause the SNMP agent 1075 to send an adslAtucSesLTrap. One trap will be 1076 sent per interval per interface. A value '0' will 1077 disable the trap." 1078 ::= { adslAlarmConfProfileExtEntry 2 } 1080 adslAtucThreshold15MinUasL OBJECT-TYPE 1081 SYNTAX Unsigned32 1082 UNITS "seconds" 1083 MAX-ACCESS read-create 1084 STATUS current 1085 DESCRIPTION 1086 "The number of unavailable errored seconds 1087 encountered by an 1088 ADSL interface withing any giving 15 minutes 1089 performance 1090 data collection period, which cause the SNMP agent 1091 to send an adslAtucUasLThreshTrap. One trap will 1092 be 1093 sent per interval per interface. A value '0' will 1094 disable the trap." 1095 ::= { adslAlarmConfProfileExtEntry 3 } 1097 -- trap definitions 1099 adslExtTraps OBJECT IDENTIFIER ::= { adslExtMibObjects 24 } 1101 adslExtAtucTraps OBJECT IDENTIFIER ::= { adslExtTraps 1 } 1103 adslAtucFailedFastRThreshTrap NOTIFICATION-TYPE 1104 OBJECTS { adslAtucPerfCurr15MinFailedFastR } 1105 STATUS current 1106 DESCRIPTION 1107 "Failed Fast Retrains 15 minutes threshold reached." 1108 ::= { adslExtAtucTraps 0 1 } 1110 adslAtucSesLThreshTrap NOTIFICATION-TYPE 1111 OBJECTS { adslAtucPerfCurr15MinSesL } 1112 STATUS current 1113 DESCRIPTION 1114 "Severe errored seconds 15 minutes threshold 1115 reached." 1116 ::= { adslExtAtucTraps 0 2 } 1118 adslAtucUasLThreshTrap NOTIFICATION-TYPE 1119 OBJECTS { adslAtucPerfCurr15MinUasL } 1120 STATUS current 1121 DESCRIPTION 1122 "Unavailable seconds 15 minutes threshold reached." 1123 ::= { adslExtAtucTraps 0 3 } 1125 -- conformance information 1127 adslExtConformance OBJECT IDENTIFIER ::= { adslExtMIB 2 } 1129 adslExtGroups OBJECT IDENTIFIER ::= { adslExtConformance 1 } 1130 adslExtCompliances OBJECT IDENTIFIER ::= { adslExtConformance 2 } 1132 -- ATU-C agent compliance statements 1134 adslExtLineMibAtucCompliance MODULE-COMPLIANCE 1135 STATUS current 1136 DESCRIPTION 1137 "The compliance statement for SNMP entities which 1138 manage ADSL ATU-C interfaces." 1140 MODULE -- this module 1141 MANDATORY-GROUPS 1142 { 1143 adslExtLineGroup, 1144 adslExtLineConfProfileControlGroup, 1145 adslExtLineAlarmConfProfileGroup 1146 } 1148 GROUP adslExtAtucPhysPerfRawCounterGroup 1149 DESCRIPTION 1150 "This group is optional. Implementations which 1151 require continuous ATU-C physical event counters 1152 should implement this group." 1154 GROUP adslExtAturPhysPerfRawCounterGroup 1155 DESCRIPTION 1156 "This group is optional. Implementations which 1157 require continuous ATU-R physical event counters 1158 should implement this group." 1160 OBJECT adslAtucThreshold15MinFailedFastR 1161 MIN-ACCESS read-write 1162 DESCRIPTION 1163 "Read-write access is applicable when 1164 static profiles are implemented." 1166 OBJECT adslAtucThreshold15MinSesL 1167 MIN-ACCESS read-write 1168 DESCRIPTION 1169 "Read-write access is applicable when 1170 static profiles are implemented." 1172 OBJECT adslAtucThreshold15MinUasL 1173 MIN-ACCESS read-write 1174 DESCRIPTION 1175 "Read-write access is applicable when 1176 static profiles are implemented." 1178 OBJECT adslLineConfProfileDualLite 1179 MIN-ACCESS read-only 1180 DESCRIPTION 1181 "Read-only access is applicable when static 1182 profiles are implemented." 1184 ::= { adslExtCompliances 1 } 1186 -- units of conformance 1187 adslExtLineGroup OBJECT-GROUP 1188 OBJECTS { 1189 adslLineConfProfileDualLite, 1190 adslLineTransAtucCap, 1191 adslLineTransAtucConfig, 1192 adslLineTransAtucActual, 1193 adslLineGlitePowerState 1194 } 1195 STATUS current 1196 DESCRIPTION 1197 "A collection of objects providing configuration 1198 information about an ADSL Line." 1199 ::= { adslExtGroups 1 } 1200 adslExtAtucPhysPerfRawCounterGroup OBJECT-GROUP 1201 OBJECTS { 1202 adslAtucPerfStatFastR, adslAtucPerfStatFailedFastR, 1203 adslAtucPerfCurr15MinFastR, 1204 adslAtucPerfCurr15MinFailedFastR, 1205 adslAtucPerfCurr1DayFastR, 1206 adslAtucPerfCurr1DayFailedFastR, 1207 adslAtucPerfPrev1DayFastR, 1208 adslAtucPerfPrev1DayFailedFastR, 1209 adslAtucPerfStatSesL, adslAtucPerfStatUasL, 1210 adslAtucPerfCurr15MinSesL, 1211 adslAtucPerfCurr15MinUasL, 1212 adslAtucPerfCurr1DaySesL, adslAtucPerfCurr1DayUasL, 1213 adslAtucPerfPrev1DaySesL, adslAtucPerfPrev1DayUasL, 1214 adslAtucIntervalFastR, adslAtucIntervalFailedFastR, 1215 adslAtucIntervalSesL, adslAtucIntervalUasL 1216 } 1217 STATUS current 1218 DESCRIPTION 1219 "A collection of objects providing raw performance 1220 counts on an ADSL Line (ATU-C end)." 1221 ::= { adslExtGroups 2 } 1223 adslExtAturPhysPerfRawCounterGroup OBJECT-GROUP 1224 OBJECTS { 1225 adslAturPerfStatSesL, 1226 adslAturPerfStatUasL, 1227 adslAturPerfCurr15MinSesL, 1228 adslAturPerfCurr15MinUasL, 1229 adslAturPerfCurr1DaySesL, 1230 adslAturPerfCurr1DayUasL, 1231 adslAturPerfPrev1DaySesL, 1232 adslAturPerfPrev1DayUasL, 1233 adslAturIntervalSesL, adslAturIntervalUasL 1234 } 1235 STATUS current 1236 DESCRIPTION 1237 "A collection of objects providing raw performance 1238 counts on an ADSL Line (ATU-C end)." 1239 ::= { adslExtGroups 3 } 1241 adslExtLineConfProfileControlGroup OBJECT-GROUP 1242 OBJECTS { 1243 adslConfProfileLineType 1244 } 1245 STATUS current 1246 DESCRIPTION 1247 "A collection of objects providing profile 1248 control for the ADSL system." 1249 ::= { adslExtGroups 4 } 1251 adslExtLineAlarmConfProfileGroup OBJECT-GROUP 1252 OBJECTS { 1253 adslAtucThreshold15MinFailedFastR, 1254 adslAtucThreshold15MinSesL, 1255 adslAtucThreshold15MinUasL 1256 } 1257 STATUS current 1258 DESCRIPTION 1259 "A collection of objects providing alarm profile 1260 control for the ADSL system." 1261 ::= { adslExtGroups 5 } 1263 adslExtNotificationsGroup NOTIFICATION-GROUP 1264 NOTIFICATIONS { 1265 adslAtucFailedFastRThreshTrap, 1266 adslAtucSesLThreshTrap, 1267 adslAtucUasLThreshTrap 1268 } 1269 STATUS current 1270 DESCRIPTION 1271 "The collection of ADSL 2 notifications." 1272 ::= { adslExtGroups 6 } 1274 END 1276 9. Acknowledgments 1278 This document is a product of the ADSL MIB Working Group. 1280 10. References 1282 [1] B. Wijnen, D. Harrington, R. Presuhn, "Structure of 1283 Management Information Version 2 (SMIv2)" RFC 2578, 1284 April 1999. 1286 [2] K. McCloghrie, D. Perkins, J. Schoenwaelder, 1287 "Textual Conventions for SMIv2", RFC 2579, April 1999. 1289 [3] McCloghrie, K., and M. Rose, Editors, "Management 1290 Information Base for Network Management of TCP/IP-based 1291 internets: MIB-II", STD 17, RFC 1213, Hughes LAN Systems, 1292 Performance Systems International, March 1991. 1294 [4] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 1295 MIB using SMIv2", RFC 2233, Cisco Systems, FTP Software, 1296 November 1997. 1298 [5] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., 1299 and S. Waldbusser, "Management Information Base for 1300 version 2 of the Simple Network Management Protocol 1301 (SNMPv2)", RFC 1907, January 1996. 1303 [6] Case, J., Fedor, M., Schoffstall, M., and J. Davin. " A 1304 Simple 1305 Network Management Protocol (SNMP)", STD 15, RFC 1157, SNMP 1306 Research, Performance Systems International, MIT Lab for 1307 Computer Science, May 1990. 1309 [7] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 1310 S. Waldbusser, "Protocol Operations for Version 2 of the 1311 Simple 1312 Network Management Protocol (SNMPv2)", RFC 1905, January 1313 1996. 1315 [8] ITU Draft Recommendation G.997.1 "Physical Layer Management 1316 for 1317 Digital Subscriber Line (DSL) Transceivers.", January 1999 1319 [9] Chris Hansen, ITU "White Paper submission of Recommendation 1320 G.992.2" 1321 June/July 1999. 1323 [10] G. Bathrick, F. Ly "Definitions of Managed Objects for the 1324 ADSL 1325 Lines", May 14, 1999. 1327 [11] D. Harrington, R. Presuhn, B. Wijnen, "An architecture for 1328 Describing SNMP Management Frameworks", RFC 2571, April 1999. 1330 [14] Rose, M. and K. McCloghrie, "Structure and Identification of 1331 Management Information for TCP/IP-based Internets", STD 16, 1332 RFC 1333 1155, May 1990. 1335 [15] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 1336 16, 1337 RFC 1212, March 1991. 1339 [16] Rose, M., "A Convention for Defining Traps for use with the 1340 SNMP", RFC 1215, March 1991. 1342 [17] McCloghrie K., Perkins D. and J. Schoenwaelder, "Conformance 1343 Statements for SMIv2", RFC 2580, April 1999. 1345 [18] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 1346 "Introduction to Community-based SNMPv2", RFC 1901, January 1347 1996. 1349 [19] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 1350 "Transport Mappings for Version 2 of the Simple Network 1351 Management Protocol (SNMPv2)", RFC 1906, January 1996. 1353 [20] Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message 1354 Processing and Dispatching for the Simple Network Management 1355 Protocol (SNMP)", RFC 2572, April 1999. 1357 [21] Blumenthal, U. and B. Wijnen, "User-based Security Model 1358 (USM) 1359 for version 3 of the Simple Network Management Protocol 1360 (SNMPv3)", RFC 2574, April 1999. 1362 [22] Levi, D., Meyer, P. and B. Stewart, "SNMP Applications", RFC 1363 2573, April 1999. 1365 [23] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based 1366 Access 1367 Control Model (VACM) for the Simple Network Management 1368 Protocol 1369 (SNMP)", RFC 2575, April 1999. 1371 10. Security Considerations 1373 1) Blocking unauthorized access to the ADSL MIB via the element 1374 management system is outside the scope of this document. It should 1375 be 1376 noted that access to the MIB permits the unauthorized entity to 1377 modify the profiles (sect 6.4) such that both subscriber service 1378 and 1379 network operations can be interfered with. Subscriber service can 1380 be 1381 altered by modifying any of a number of service characteristics 1382 such 1383 as rate partitioning and maximum transmission rates. Network 1384 operations can be impacted by modification of trap thresholds such 1385 as 1386 SNR margins. 1388 2) There are a number of managed objects in this MIB that may be 1389 considered to contain sensitive information. In particular, the 1390 certain objects may be considered sensitive in many environments, 1391 since it would allow an intruder to obtain information about which 1392 vendor's equipment is in use on the network. Therefore, it may be 1393 important in some environments to control read access to these 1394 objects and possibly to even encrypt the values of these object 1395 when 1396 sending them over the network via SNMP. Not all versions of SNMP 1397 provide features for such a secure environment. 1399 SNMPv1 by itself is such an insecure environment. Even if the 1400 network itself is secure (for example by using IPSec), even then, 1401 there is no control as to who on the secure network is allowed to 1402 access and GET (read) the objects in this MIB. It is recommended 1403 that the implementors consider the security features as provided 1404 by 1405 the SNMPv3 framework. Specifically, the use of the User-based 1406 Security Model RFC 2574 [21] and the View-based Access Control 1407 Model 1408 RFC 2575 [23] is recommended. 1410 It is then a customer/user responsibility to ensure that the SNMP 1411 entity giving access to an instance of this MIB, is properly 1412 configured to give access to those objects only to those 1413 principals 1414 (users) that have legitimate rights to access them. 1416 3) ADSL layer connectivity from the ATU-R will permit the 1417 subscriber 1418 to manipulate both the ADSL link directly and the AOC/EOC channels 1419 for their own loop. For example, unchecked or unfiltered 1420 fluctuations initiated by the subscriber could generate sufficient 1421 traps to potentially overwhelm either the management interface to 1422 the 1423 network or the element manager. Other attacks affecting the ATU-R 1424 portions of the MIB may also be possible. 1426 11. Intellectual Property Notice 1428 The IETF takes no position regarding the validity or scope of any 1429 intellectual property or other rights that might be claimed to 1430 pertain to the implementation or use of the technology described 1431 in 1432 this document or the extent to which any license under such rights 1433 might or might not be available; neither does it represent that it 1434 has made any effort to identify any such rights. Information on 1435 the 1436 IETF's procedures with respect to rights in standards-track and 1437 standards-related documentation can be found in BCP-11. Copies of 1438 claims of rights made available for publication and any assurances 1439 of 1440 licenses to be made available, or the result of an attempt made to 1441 obtain a general license or permission for the use of such 1442 proprietary rights by implementers or users of this specification 1443 can 1444 be obtained from the IETF Secretariat." 1446 The IETF invites any interested party to bring to its attention 1447 any 1448 copyrights, patents or patent applications, or other proprietary 1449 rights which may cover technology that may be required to practice 1450 this standard. Please address the information to the IETF 1451 Executive 1452 Director. 1454 12. Authors' Addresses 1456 Faye Ly 1457 Copper Mountain Networks 1458 Norcal Office 1459 2470 Embarcadero Way 1460 Palo Alto, CA 94303 1462 Phone: +1 650-687-3323 1463 Fax: +1 650-687-3372 1464 EMail: faye@coppermountain.com 1466 Gregory Bathrick 1467 NOKIA High Speed Access Nodes 1468 1310 Redwood Way, 1469 Petaluma, CA 94954, USA 1471 Phone: +1 707-793-7030 1472 Fax: +1 707-792-0850 1473 EMail: greg.bathrick@nokia.com 1475 13. Full Copyright Statement 1477 Copyright (C) The Internet Society (1999). All Rights Reserved. 1479 This document and translations of it may be copied and furnished 1480 to 1481 others, and derivative works that comment on or otherwise explain 1482 it 1483 or assist in its implementation may be prepared, copied, published 1484 and distributed, in whole or in part, without restriction of any 1485 kind, provided that the above copyright notice and this paragraph 1486 are 1487 included on all such copies and derivative works. However, this 1488 document itself may not be modified in any way, such as by 1490 removing 1491 the copyright notice or references to the Internet Society or 1492 other 1493 Internet organizations, except as needed for the purpose of 1494 developing Internet standards in which case the procedures for 1495 copyrights defined in the Internet Standards process must be 1496 followed, or as required to translate it into languages other than 1497 English. 1499 The limited permissions granted above are perpetual and will not 1500 be 1501 revoked by the Internet Society or its successors or assigns. 1503 This document and the information contained herein is provided on 1504 an 1505 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET 1506 ENGINEERING 1507 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1508 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1509 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1510 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1512 Acknowledgement 1514 Funding for the RFC Editor function is currently provided by the 1515 Internet Society.