idnits 2.17.1 draft-ietf-adslmib-adslext-07.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 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: ' 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 124 instances of too long lines in the document, the longest one being 7 characters in excess of 72. ** The abstract seems to contain references ([RFC2573], [RFC1906], [RFC1155], [21], [RFC2574], [RFC2575], [RFC1157], [RFC2580], [23], [RFC2863], [RFC2578], [RFC1212], [RFC1213], [RFC2579], [RFC1901], [RFC1215], [RFC2662], [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 -- 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 (April 9, 2001) is 8418 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 1283 looks like a reference -- Missing reference section? 'RFC2571' on line 1214 looks like a reference -- Missing reference section? 'RFC1155' on line 1222 looks like a reference -- Missing reference section? 'RFC1212' on line 55 looks like a reference -- Missing reference section? 'RFC1215' on line 1226 looks like a reference -- Missing reference section? 'RFC2578' on line 1229 looks like a reference -- Missing reference section? 'RFC2579' on line 1234 looks like a reference -- Missing reference section? 'RFC2580' on line 1238 looks like a reference -- Missing reference section? 'RFC1157' on line 1242 looks like a reference -- Missing reference section? 'RFC1901' on line 1245 looks like a reference -- Missing reference section? 'RFC1906' on line 1249 looks like a reference -- Missing reference section? 'RFC2572' on line 1253 looks like a reference -- Missing reference section? 'RFC2574' on line 1257 looks like a reference -- Missing reference section? 'RFC1905' on line 1261 looks like a reference -- Missing reference section? 'RFC2573' on line 1265 looks like a reference -- Missing reference section? 'RFC2575' on line 1268 looks like a reference -- Missing reference section? 'RFC2570' on line 1272 looks like a reference -- Missing reference section? 'RFC1213' on line 1276 looks like a reference -- Missing reference section? 'RFC2863' on line 1280 looks like a reference -- Missing reference section? '21' on line 1314 looks like a reference -- Missing reference section? '23' on line 1315 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 Salira Optical Systems 4 Gregory Bathrick 5 Nokia 6 April 9, 2001 8 Definitions of Extension Managed Objects 9 for ADSL Lines 11 April 9, 2001 13 draft-ietf-adslmib-adslext-07.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/1id-abstracts.html 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 memo defines a portion of the Management Information Base (MIB) 44 for use with network management protocols in the Internet community. 45 In particular, it describes additional managed objects used for 46 managing ADSL interfaces not covered by the ADSL Line MIB [RFC2662]. 48 3. The SNMP Network Management Framework 50 The SNMP Management Framework presently consists of five major 51 components: An overall architecture, described in RFC 2571 52 [RFC2571]. Mechanisms for describing and naming objects and events 53 for the purpose of management. The first version of this Structure 54 of Management Information (SMI) is called SMIv1 and described in STD 55 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 1215 56 [RFC1215]. The second version, called SMIv2, is described in STD 58, 57 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 58 [RFC2580]. Message protocols for transferring management 59 information. The first version of the SNMP message protocol is 60 called SNMPv1 and described in STD 15, RFC 1157 [RFC1157]. A second 61 version of the SNMP message protocol, which is not an Internet 62 standards track protocol, is called SNMPv2c and described in RFC 1901 63 [RFC1901] and RFC 1906 [RFC1906]. The third version of the message 64 protocol is called SNMPv3 and described in RFC 1906 [RFC1906], RFC 65 2572 [RFC2572] and RFC 2574 [RFC2574]. Protocol operations for 66 accessing management information. The first set of protocol 67 operations and associated PDU formats is described in STD 15, RFC 68 1157 [RFC1157]. A second set of protocol operations and associated 69 PDU formats is described in RFC 1905 [RFC1905]. A set of fundamental 70 applications described in RFC 2573 [RFC2573] and the view-based 71 access control mechanism described in RFC 2575 [RFC2575]. 73 A more detailed introduction to the current SNMP Management Framework 74 can be found in RFC 2570 [RFC2570]. 76 Managed objects are accessed via a virtual information store, termed 77 the Management Information Base or MIB. Objects in the MIB are 78 defined using the mechanisms defined in the SMI. 80 This memo specifies a MIB module that is compliant to the SMIv2. A 81 MIB conforming to the SMIv1 can be produced through the appropriate 82 translations. The resulting translated MIB must be semantically 83 equivalent, except where objects or events are omitted because no 84 translation is possible (use of Counter64). Some machine readable 85 information in SMIv2 will be converted into textual descriptions in 86 SMIv1 during the translation process. However, this loss of machine 87 readable information is not considered to change the semantics of the 88 MIB. 90 4. Introduction 92 The purpose of this memo is to define a supplemental set of managed 93 objects that is not covered by ADSL Line MIB as defined in [RFC2662]. 94 This memo addresses the additional objects defined in ITU G.997.1. 95 These additional objects specifically address the management 97 5. Relationship of the ADSL LINE EXTENSION MIB with standard MIBs 99 This section outlines the relationship of ADSL Line Extension MIB 100 with other MIBs described in RFCs and in their various degrees 101 of "standardization". ADSL Line Extension MIB obeys the same 102 relationship between ADSL Line MIB to other standard MIBs with 103 one exception for the ifOperStatus as defined in RFC 1213. 105 5.1 ifOperStatus 107 ifOperStatus is set to down(2) when the ADSL line interface is in 108 power state L3, which means no power. ifOperStatus is set to up(1) 109 if the ADSL line interface is in power state L0 (power on) 110 or L1 (reduced power). 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 A few objects are added to cover the ADSL "Lite" management and they are: 123 - ATU-C Transmission System and Line Mode 124 - Power Management 125 - Counters for Fast Retrains and Failed Fast Retrains 126 - Counters for Severe Error Second-line and Unavailable Second 127 - Alternative profile configuration for the Dual line mode interface 129 Besides the management of ADSL "Lite", another object has been added 130 to the ADSL Line MIB [RFC2662] in order to manage the ADSL line profile. 131 The object is the line mode configuration. 133 The MIB definitions are attached. The MIB will be branched from the 134 ADSL Line MIB [RFC2662]. 136 6.2.1 ATU-C ADSL Transmission System Parameters and Line Mode 138 The adslLineConfigTable needs to be extended to cover control of the 139 ATU-C ADSL Transmission system. Three objects are defined to monitor 140 and configure the transmission mode as well as the actual line mode: 142 - Capability 143 - Configuration 144 - Actual Status 146 Transmission modes can further determine the line mode of the ADSL 147 interface. For example, if g9921PotsNonOverlapped(2) is the actual 148 value of the ADSL interface, the interface is operating in Full rate 149 ADSL. If the interface is set to g9922PotsOverlapped(9), the interface 150 is operating in G.lite mode. 152 The transmssion mode and the corresponding line mode are defined as: 154 Transmission mode Line Mode 155 ---------------------------------------------------------- 156 Regional Std. (ANSI T1.413) Full 157 Regional Std. (ETSI DTS/TM06006) Full 158 G.992.1 POTS non-overlapped Full 159 G.992.1 POTS overlapped Full 160 G.992.1 ISDN non-overlapped Full 161 G.992.1 ISDN overlapped Full 162 G.992.1 TCM-ISDN non-overlapped Full 163 G.992.1 TCM-ISDN overlapped Full 164 G.992.2 POTS non-overlapped Lite 165 G.992.2 POTS overlapped Lite 166 G.992.2 with TCM-ISDN non-overlapped Lite 167 G.992.2 with TCM-ISDN overlapped Lite 168 G.992.1 TCM-ISDN symmetric Full 170 Table 1: Transmission Mode and Line Mode 172 In case more than one bit is configured for an ADSL interface and 173 both Full and Lite modes are selected, the interface is said to 174 configure in the dual mode. Only one bit can be set in the Actual 175 object that reflects the actual mode of transmission as well as the 176 line mode. 178 6.2.2 Power Management 180 There are three power states for each managed ADSL interface operating 181 in the G.lite mode. L0 is power on, L1 is power on but reduced and L3 182 is power off. Power state cannot be configured by an operator but it 183 can be viewed via the ifOperStatus object for the managed ADSL interface. 184 The value of the object ifOperStatus is set to down(2) if the ADSL 185 interface is in power state L3 and is set to up(1) if the ADSL line 186 interface is in power state L0 or L1. 188 An ADSL line power state, if the interface is operating in the G.lite 189 mode, can also be monitored by the adslLineGlitePowerState object 190 defined in the ADSL Line Extension table. The value of the object 191 enumerates the three power states attainable by the managed interface. 193 6.2.3 Fast Retrain Parameters 194 Section 7.4.15 of ITU G.997.1 specifies fast retrain parameters. Fast 195 retrain parameters include two counters: fast retrain count and failed 196 fast retrain count. These two counters have been added to all 197 performance tables. 199 6.2.4 Counters for Severe Error Second-line and Unavailable Second 201 Section 6.2.1.1.7 and section 6.2.1.1.9 specify two counters that are 202 not covered by the ADSL Line MIB [RFC2662]. These two counters 203 (severe error seconds-line and unavailable seconds) are added 204 to all the performance tables. 206 Unavailable seconds counts cumulative number of seconds in which the 207 interface was unavailable during the measured period. This counter 208 does not include the seconds in which unavailability was caused solely 209 by fast retrains and failed fast retrins. Fast retrains and failed 210 fast retrains are considered to be part of the normal network operation 211 and thus are not counted as unavailable errors. 213 6.2.5 Alternative profile configuration for the Dual line mode interface 215 This object is used only when the interface (for the ADSL line or 216 channel) is configured as dual mode, that is, the object 217 adslLineTransAtucConfig is configued with one or more full-rate 218 modes and one or more Lite modes. 220 The object adslLineConfProfile defined in ADSL-MIB [RFC2662] is used as 221 the primary full-rate profile. The newly added object in this MIB 222 module, adslLineConfProfileDualLite is used to describe or configure 223 the Lite profile. Note that if one or more full-rate modes are 224 configured, or only lite modes are configured, only the original 225 full-rate profile is needed. The dual-mode profile object is only 226 needed when both full-rate and lite profiles are needed. 228 If the static profile is used, the profile name is the ifIndex ASCII 229 string plus the differentiator string appended to the end of the 230 static profile name. For example, for interface 100, the object 231 adslLineConfProfile is set by the agent to be "100Full" and the 232 object adslLineConfProfileDualLite is set to be "100Lite". 234 7. Conformance and Compliance 236 See the conformance and compliance statements within the information 237 module. 239 8. Definitions 240 ADSL-LINE-EXT-MIB DEFINITIONS ::= BEGIN 242 IMPORTS 243 Counter32, 244 Unsigned32, 245 NOTIFICATION-TYPE, 246 MODULE-IDENTITY, Gauge32, 247 OBJECT-TYPE, mib-2 FROM SNMPv2-SMI 248 MODULE-COMPLIANCE, OBJECT-GROUP, 249 NOTIFICATION-GROUP FROM SNMPv2-CONF 250 TEXTUAL-CONVENTION FROM SNMPv2-TC 251 PerfCurrentCount, 252 PerfIntervalCount FROM PerfHist-TC-MIB 253 AdslPerfCurrDayCount, 254 AdslPerfPrevDayCount, 255 AdslPerfTimeElapsed, 256 AdslLineCodingType FROM ADSL-TC-MIB 257 ifIndex FROM IF-MIB 258 SnmpAdminString FROM SNMP-FRAMEWORK-MIB 259 adslLineAlarmConfProfileEntry, 260 adslLineConfProfileEntry, 261 adslAturIntervalEntry, 262 adslAturPerfDataEntry, 263 adslAtucIntervalEntry, 264 adslAtucPerfDataEntry, 265 adslLineEntry, 266 adslMIB FROM ADSL-LINE-MIB 267 ; 269 adslExtMIB MODULE-IDENTITY 271 LAST-UPDATED "200104090000Z" 273 ORGANIZATION "IETF ADSL MIB Working Group" 275 CONTACT-INFO 276 " 277 Faye Ly 278 Salira Optical Systems 279 2698 Orchard Parkway 280 San Jose, CA 95134 281 Tel: +1 408-382-0088 282 Fax: +1 408-382-1688 283 E-Mail: faye@salira.com 285 Gregory Bathrick 286 NOKIA High Speed Access Nodes 287 1310 Redwood Way, 288 Petaluma, CA 94954, USA 289 Tel: +1 707-793-7030 290 Fax: +1 707-792-0850 291 E-Mail: greg.bathrick@nokia.com 293 IETF ADSL MIB Working Group (XDSLMIB@LISTSERV.ECIRALEIGH.COM> 294 " 295 DESCRIPTION 296 "This MIB Module is a supplement to the ADSL-LINE-MIB 297 [RFC2662]." 298 ::= { adslMIB 3 } 300 adslExtMibObjects OBJECT IDENTIFIER ::= { adslExtMIB 1 } 302 AdslTransmissionModeType ::= TEXTUAL-CONVENTION 303 STATUS current 304 DESCRIPTION 305 "A set of ADSL line transmission modes, with one bit 306 per mode. The notes (F) and (L) denote Full-Rate 307 and Lite respectively: 308 Bit 00 : Regional Std. (ANSI T1.413) (F) 309 Bit 01 : Regional Std. (ETSI DTS/TM06006) (F) 310 Bit 02 : G.992.1 POTS non-overlapped (F) 311 Bit 03 : G.992.1 POTS overlapped (F) 312 Bit 04 : G.992.1 ISDN non-overlapped (F) 313 Bit 05 : G.992.1 ISDN overlapped (F) 314 Bit 06 : G.992.1 TCM-ISDN non-overlapped (F) 315 Bit 07 : G.992.1 TCM-ISDN overlapped (F) 316 Bit 08 : G.992.2 POTS non-overlapped (L) 317 Bit 09 : G.992.2 POTS overlapped (L) 318 Bit 10 : G.992.2 with TCM-ISDN non-overlapped (L) 319 Bit 11 : G.992.2 with TCM-ISDN overlapped (L) 320 Bit 12 : G.992.1 TCM-ISDN symmetric (F) 321 " 322 SYNTAX BITS { 323 ansit1413(0), 324 etsi(1), 325 q9921PotsNonOverlapped(2), 326 q9921PotsOverlapped(3), 327 q9921IsdnNonOverlapped(4), 328 q9921isdnOverlapped(5), 329 q9921tcmIsdnNonOverlapped(6), 330 q9921tcmIsdnOverlapped(7), 331 q9922potsNonOverlapeed(8), 332 q9922potsOverlapped(9), 333 q9922tcmIsdnNonOverlapped(10), 334 q9922tcmIsdnOverlapped(11), 335 q9921tcmIsdnSymmetric(12) 337 } 339 adslLineExtTable OBJECT-TYPE 340 SYNTAX SEQUENCE OF AdslLineExtEntry 341 MAX-ACCESS not-accessible 342 STATUS current 343 DESCRIPTION 344 "This table contains ADSL line configuration and 345 monitoring information not defined in the 346 adslLineTable from the ADSL-LINE-MIB [RFC2662]. 347 This includes the capabilities and actual ADSL 348 transmission system." 349 ::= { adslExtMibObjects 17 } 351 adslLineExtEntry OBJECT-TYPE 352 SYNTAX AdslLineExtEntry 353 MAX-ACCESS not-accessible 354 STATUS current 355 DESCRIPTION 356 "An entry extends the adslLineEntry defined in 357 [RFC2662]. Each entry corresponds to an ADSL 358 line." 359 AUGMENTS { adslLineEntry } 360 ::= { adslLineExtTable 1 } 362 AdslLineExtEntry ::= 363 SEQUENCE { 364 adslLineTransAtucCap AdslTransmissionModeType, 365 adslLineTransAtucConfig AdslTransmissionModeType, 366 adslLineTransAtucActual AdslTransmissionModeType, 367 adslLineGlitePowerState INTEGER, 368 adslLineConfProfileDualLite SnmpAdminString 369 } 371 adslLineTransAtucCap OBJECT-TYPE 372 SYNTAX AdslTransmissionModeType 373 MAX-ACCESS read-only 374 STATUS current 375 DESCRIPTION 376 "The transmission modes that the ATU-C is capable 377 of supporting. The modes available are limited 378 by the design of the equipment." 379 REFERENCE "Section 7.3.2 ITU G.997.1" 380 ::= { adslLineExtEntry 1 } 382 adslLineTransAtucConfig OBJECT-TYPE 383 SYNTAX AdslTransmissionModeType 384 MAX-ACCESS read-write 385 STATUS current 386 DESCRIPTION 387 "The transmission modes that the ATU-C must enable 388 for the line. The ATU-C's enable modes must be 389 a subset of its capable modes." 390 REFERENCE "Section 7.3.2 ITU G.997.1" 391 ::= { adslLineExtEntry 2 } 393 adslLineTransAtucActual OBJECT-TYPE 394 SYNTAX AdslTransmissionModeType 395 MAX-ACCESS read-only 396 STATUS current 397 DESCRIPTION 398 "The transmission mode of the ATU-C. This object 399 returns 0 (i.e BITS with no mode bit set) if there 400 is no mode currently known. The initialization 401 with the ATU-R will determine the mode used 402 and the result must be a one-mode subset of the 403 'Enable' modes. After an initialization has 404 occurred, its mode is saved as the 'Current' mode 405 and it should persist even if the link goes down 406 subsequently. This leaves a hint on what may be 407 used next time." 408 REFERENCE "Section 7.3.2 ITU G.997.1 " 409 ::= { adslLineExtEntry 3 } 411 adslLineGlitePowerState OBJECT-TYPE 412 SYNTAX INTEGER { 413 none(1), 414 l0(2), -- L0 Power on 415 l1(3), -- L1 Power on but reduced 416 l3(4) -- L3 Power off 417 } 418 MAX-ACCESS read-only 419 STATUS current 420 DESCRIPTION 421 "The value of this object specifies the power state 422 this interface is in. If the object adslLineModeActual 423 is set to glite, the value of this object can be either 424 one of the power state from L0 to L3. If the object 425 adslLineTransAtucActual is set to other than G.lite, 426 the value of this object is always set to none(1)." 427 ::= { adslLineExtEntry 4 } 429 adslLineConfProfileDualLite OBJECT-TYPE 430 SYNTAX SnmpAdminString 431 MAX-ACCESS read-write 432 STATUS current 433 DESCRIPTION 434 "The value of this object identifies the row 435 in the ADSL Line Configuration Profile Table, 436 (adslLineConfProfileTable), which applies for this 437 ADSL line, and channels if applicable, when the 438 mode after initialization is any G.992.2 (G.lite) 439 mode AND adslLineTransAtucConfig has enabled 440 dual-mode. Dual-mode in this case means one or more 441 Full-Rate modes AND one or more Lite modes enabled. 443 If dual-mode has not been enabled by this MIB or if 444 the ATU-C does not support this extension MIB, then 445 the previously existing adslLineConfProfile is used 446 even if the ATU-C mode is one of the G.992.2 modes." 447 ::= { adslLineExtEntry 5 } 449 adslAtucPerfDataExtTable OBJECT-TYPE 450 SYNTAX SEQUENCE OF AdslAtucPerfDataExtEntry 451 MAX-ACCESS not-accessible 452 STATUS current 453 DESCRIPTION 454 "This table contains ADSL physical line counters 455 information not defined in the adslAtucPerfDataTable 456 from the ADSL-LINE-MIB [RFC2662]." 457 ::= { adslExtMibObjects 18 } 459 adslAtucPerfDataExtEntry OBJECT-TYPE 460 SYNTAX AdslAtucPerfDataExtEntry 461 MAX-ACCESS not-accessible 462 STATUS current 463 DESCRIPTION 464 "An entry extends the adslAtucPerfDataEntry defined 465 in [RFC2662]. Each entry corresponds to an ADSL line." 466 AUGMENTS { adslAtucPerfDataEntry } 467 ::= { adslAtucPerfDataExtTable 1 } 469 AdslAtucPerfDataExtEntry ::= 470 SEQUENCE { 471 adslAtucPerfStatFastR Counter32, 472 adslAtucPerfStatFailedFastR Counter32, 473 adslAtucPerfStatSesL Counter32, 474 adslAtucPerfStatUasL Counter32, 475 adslAtucPerfCurr15MinFastR PerfCurrentCount, 476 adslAtucPerfCurr15MinFailedFastR PerfCurrentCount, 477 adslAtucPerfCurr15MinSesL PerfCurrentCount, 478 adslAtucPerfCurr15MinUasL PerfCurrentCount, 479 adslAtucPerfCurr1DayFastR AdslPerfCurrDayCount, 480 adslAtucPerfCurr1DayFailedFastR AdslPerfCurrDayCount, 481 adslAtucPerfCurr1DaySesL AdslPerfCurrDayCount, 482 adslAtucPerfCurr1DayUasL AdslPerfCurrDayCount, 483 adslAtucPerfPrev1DayFastR AdslPerfPrevDayCount, 484 adslAtucPerfPrev1DayFailedFastR AdslPerfPrevDayCount, 485 adslAtucPerfPrev1DaySesL AdslPerfPrevDayCount, 486 adslAtucPerfPrev1DayUasL AdslPerfPrevDayCount 487 } 489 adslAtucPerfStatFastR OBJECT-TYPE 490 SYNTAX Counter32 491 MAX-ACCESS read-only 492 STATUS current 493 DESCRIPTION 494 "The value of this object indicates the count of 495 fast retrains." 496 REFERENCE "ITU G.997.1 Section 7.4.15.1 " 497 ::= { adslAtucPerfDataExtEntry 1 } 499 adslAtucPerfStatFailedFastR OBJECT-TYPE 500 SYNTAX Counter32 501 MAX-ACCESS read-only 502 STATUS current 503 DESCRIPTION 504 "The value of this object indicates the count of 505 failed fast retrains." 506 REFERENCE "ITU G.997.1 Section 7.4.15.2 " 507 ::= { adslAtucPerfDataExtEntry 2 } 509 adslAtucPerfStatSesL OBJECT-TYPE 510 SYNTAX Counter32 511 UNITS "seconds" 512 MAX-ACCESS read-only 513 STATUS current 514 DESCRIPTION 515 "The value of this object indicates the count of 516 severely errored second-line." 517 REFERENCE "ITU G.997.1 Section 7.2.1.1.7 " 518 ::= { adslAtucPerfDataExtEntry 3 } 520 adslAtucPerfStatUasL OBJECT-TYPE 521 SYNTAX Counter32 522 UNITS "seconds" 523 MAX-ACCESS read-only 524 STATUS current 525 DESCRIPTION 526 "The value of this object indicates the count of 527 unavailable second." 528 REFERENCE "ITU G.997.1 Section 7.2.1.1.9 " 530 ::= { adslAtucPerfDataExtEntry 4 } 532 adslAtucPerfCurr15MinFastR OBJECT-TYPE 533 SYNTAX PerfCurrentCount 534 UNITS "seconds" 535 MAX-ACCESS read-only 536 STATUS current 537 DESCRIPTION 538 "Count of seconds in the current 15 minute interval 539 when there was fast retrains." 540 REFERENCE "ITU G.997.1 Section 7.4.15.1 " 541 ::= { adslAtucPerfDataExtEntry 5 } 543 adslAtucPerfCurr15MinFailedFastR OBJECT-TYPE 544 SYNTAX PerfCurrentCount 545 UNITS "seconds" 546 MAX-ACCESS read-only 547 STATUS current 548 DESCRIPTION 549 "Count of seconds in the current 15 minute interval 550 when there was failed fast retrains." 551 REFERENCE "ITU G.997.1 Section 7.4.15.2 " 552 ::= { adslAtucPerfDataExtEntry 6 } 554 adslAtucPerfCurr15MinSesL OBJECT-TYPE 555 SYNTAX PerfCurrentCount 556 UNITS "seconds" 557 MAX-ACCESS read-only 558 STATUS current 559 DESCRIPTION 560 "Count of seconds in the current 15 minute interval 561 when there was fast retrains." 562 REFERENCE "ITU G.997.1 Section 7.2.1.1.7 " 563 ::= { adslAtucPerfDataExtEntry 7 } 565 adslAtucPerfCurr15MinUasL OBJECT-TYPE 566 SYNTAX PerfCurrentCount 567 UNITS "seconds" 568 MAX-ACCESS read-only 569 STATUS current 570 DESCRIPTION 571 "Count of seconds in the current 15 minute interval 572 when there was count for unavailable errored seconds." 573 REFERENCE "ITU G.997.1 Section 7.2.1.1.9 " 574 ::= { adslAtucPerfDataExtEntry 8 } 576 adslAtucPerfCurr1DayFastR OBJECT-TYPE 577 SYNTAX AdslPerfCurrDayCount 578 UNITS "seconds" 579 MAX-ACCESS read-only 580 STATUS current 581 DESCRIPTION 582 "Count of the number of seconds when there was fast 583 retrains during the current day as measured by 584 adslAtucPerfCurr1DayTimeElapsed." 585 REFERENCE "ITU G.997.1 Section 7.4.15.1 " 586 ::= { adslAtucPerfDataExtEntry 9 } 588 adslAtucPerfCurr1DayFailedFastR OBJECT-TYPE 589 SYNTAX AdslPerfCurrDayCount 590 UNITS "seconds" 591 MAX-ACCESS read-only 592 STATUS current 593 DESCRIPTION 594 "Count of the number of seconds when there was failed 595 fast retrains during the current day as measured by 596 adslAtucPerfCurr1DayTimeElapsed." 597 REFERENCE "ITU G.997.1 Section 7.4.15.2 " 598 ::= { adslAtucPerfDataExtEntry 10 } 600 adslAtucPerfCurr1DaySesL OBJECT-TYPE 601 SYNTAX AdslPerfCurrDayCount 602 UNITS "seconds" 603 MAX-ACCESS read-only 604 STATUS current 605 DESCRIPTION 606 "Count of the number of seconds when there was Severe 607 Errored Seconds during the current day as measured by 608 adslAtucPerfCurr1DayTimeElapsed." 609 REFERENCE "ITU G.997.1 Section 7.2.1.1.7 " 610 ::= { adslAtucPerfDataExtEntry 11 } 612 adslAtucPerfCurr1DayUasL OBJECT-TYPE 613 SYNTAX AdslPerfCurrDayCount 614 UNITS "seconds" 615 MAX-ACCESS read-only 616 STATUS current 617 DESCRIPTION 618 "Count of the number of seconds when there was 619 Unavailable Errored Seconds during the current 620 day as measured by adslAtucPerfCurr1DayTimeElapsed." 621 REFERENCE "ITU G.997.1 Section 7.2.1.1.9 " 622 ::= { adslAtucPerfDataExtEntry 12 } 624 adslAtucPerfPrev1DayFastR OBJECT-TYPE 625 SYNTAX AdslPerfPrevDayCount 626 UNITS "seconds" 627 MAX-ACCESS read-only 628 STATUS current 629 DESCRIPTION 630 "Count of seconds in the interval when there was 631 fast retrains within the most recent previous 632 1-day period." 633 REFERENCE "ITU G.997.1 Section 7.4.15.1 " 634 ::= { adslAtucPerfDataExtEntry 13 } 636 adslAtucPerfPrev1DayFailedFastR OBJECT-TYPE 637 SYNTAX AdslPerfPrevDayCount 638 UNITS "seconds" 639 MAX-ACCESS read-only 640 STATUS current 641 DESCRIPTION 642 "Count of seconds in the interval when there was 643 failed fast retrains within the most recent previous 644 1-day period." 645 REFERENCE "ITU G.997.1 Section 7.4.15.2 " 646 ::= { adslAtucPerfDataExtEntry 14 } 648 adslAtucPerfPrev1DaySesL OBJECT-TYPE 649 SYNTAX AdslPerfPrevDayCount 650 UNITS "seconds" 651 MAX-ACCESS read-only 652 STATUS current 653 DESCRIPTION 654 "Count of seconds in the interval when there was 655 severed errored seconds within the most recent previous 656 1-day period." 657 REFERENCE "ITU G.997.1 Section 7.2.1.1.7 " 658 ::= { adslAtucPerfDataExtEntry 15 } 660 adslAtucPerfPrev1DayUasL OBJECT-TYPE 661 SYNTAX AdslPerfPrevDayCount 662 UNITS "seconds" 663 MAX-ACCESS read-only 664 STATUS current 665 DESCRIPTION 666 "Count of seconds in the interval when there was 667 unavailable errored seconds within the most recent 668 previous 1-day period." 669 REFERENCE "ITU G.997.1 Section 7.2.1.1.9 " 670 ::= { adslAtucPerfDataExtEntry 16 } 672 adslAtucIntervalExtTable OBJECT-TYPE 673 SYNTAX SEQUENCE OF AdslAtucIntervalExtEntry 674 MAX-ACCESS not-accessible 675 STATUS current 676 DESCRIPTION 677 "This table provides one row for each ATUC 678 performance data collection interval. 679 ADSL physical interfaces are 680 those ifEntries where ifType is equal to adsl(94)." 681 ::= { adslExtMibObjects 19 } 683 adslAtucIntervalExtEntry OBJECT-TYPE 684 SYNTAX AdslAtucIntervalExtEntry 685 MAX-ACCESS not-accessible 686 STATUS current 687 DESCRIPTION "An entry in the adslAtucIntervalExtTable." 688 AUGMENTS { adslAtucIntervalEntry } 689 ::= { adslAtucIntervalExtTable 1 } 691 AdslAtucIntervalExtEntry ::= 692 SEQUENCE { 693 adslAtucIntervalFastR PerfIntervalCount, 694 adslAtucIntervalFailedFastR PerfIntervalCount, 695 adslAtucIntervalSesL PerfIntervalCount, 696 adslAtucIntervalUasL PerfIntervalCount 697 } 699 adslAtucIntervalFastR OBJECT-TYPE 700 SYNTAX PerfIntervalCount 701 UNITS "seconds" 702 MAX-ACCESS read-only 703 STATUS current 704 DESCRIPTION 705 "Count of seconds in the interval when there was Fast 706 Retrains." 707 ::= { adslAtucIntervalExtEntry 1 } 709 adslAtucIntervalFailedFastR OBJECT-TYPE 710 SYNTAX PerfIntervalCount 711 UNITS "seconds" 712 MAX-ACCESS read-only 713 STATUS current 714 DESCRIPTION 715 "Count of seconds in the interval when there was Failed 716 Fast Retrains." 717 ::= { adslAtucIntervalExtEntry 2 } 719 adslAtucIntervalSesL OBJECT-TYPE 720 SYNTAX PerfIntervalCount 721 UNITS "seconds" 722 MAX-ACCESS read-only 723 STATUS current 724 DESCRIPTION 725 "Count of seconds in the interval when there was 726 severed errors." 727 ::= { adslAtucIntervalExtEntry 3 } 729 adslAtucIntervalUasL OBJECT-TYPE 730 SYNTAX PerfIntervalCount 731 UNITS "seconds" 732 MAX-ACCESS read-only 733 STATUS current 734 DESCRIPTION 735 "Count of seconds in the interval when there was 736 unavailable errors." 737 ::= { adslAtucIntervalExtEntry 4 } 739 adslAturPerfDataExtTable OBJECT-TYPE 740 SYNTAX SEQUENCE OF AdslAturPerfDataExtEntry 741 MAX-ACCESS not-accessible 742 STATUS current 743 DESCRIPTION 744 "This table contains ADSL physical line counters 745 information not defined in the adslAturPerfDataTable 746 from the ADSL-LINE-MIB [RFC2662]." 747 ::= { adslExtMibObjects 20 } 749 adslAturPerfDataExtEntry OBJECT-TYPE 750 SYNTAX AdslAturPerfDataExtEntry 751 MAX-ACCESS not-accessible 752 STATUS current 753 DESCRIPTION 754 "An entry extends the adslAturPerfDataEntry defined 755 in [RFC2662]. Each entry corresponds to an ADSL line." 756 AUGMENTS { adslAturPerfDataEntry } 757 ::= { adslAturPerfDataExtTable 1 } 759 AdslAturPerfDataExtEntry ::= 760 SEQUENCE { 761 adslAturPerfStatSesL Counter32, 762 adslAturPerfStatUasL Counter32, 763 adslAturPerfCurr15MinSesL PerfCurrentCount, 764 adslAturPerfCurr15MinUasL PerfCurrentCount, 765 adslAturPerfCurr1DaySesL AdslPerfCurrDayCount, 766 adslAturPerfCurr1DayUasL AdslPerfCurrDayCount, 767 adslAturPerfPrev1DaySesL AdslPerfPrevDayCount, 768 adslAturPerfPrev1DayUasL AdslPerfPrevDayCount 769 } 770 adslAturPerfStatSesL OBJECT-TYPE 771 SYNTAX Counter32 772 UNITS "seconds" 773 MAX-ACCESS read-only 774 STATUS current 775 DESCRIPTION 776 "The value of this object indicates the count of 777 severely errored second-line." 778 REFERENCE "ITU G.997.1 Section 7.2.1.1.7 " 779 ::= { adslAturPerfDataExtEntry 1 } 781 adslAturPerfStatUasL OBJECT-TYPE 782 SYNTAX Counter32 783 UNITS "seconds" 784 MAX-ACCESS read-only 785 STATUS current 786 DESCRIPTION 787 "The value of this object indicates the count of 788 unavailable second." 789 REFERENCE "ITU G.997.1 Section 7.2.1.2.9 " 790 ::= { adslAturPerfDataExtEntry 2 } 792 adslAturPerfCurr15MinSesL OBJECT-TYPE 793 SYNTAX PerfCurrentCount 794 UNITS "seconds" 795 MAX-ACCESS read-only 796 STATUS current 797 DESCRIPTION 798 "Count of seconds in the current 15 minute interval 799 when there was Severe Errored Seconds-Line." 800 REFERENCE "ITU G.997.1 Section 7.2.1.2.7 " 801 ::= { adslAturPerfDataExtEntry 3 } 803 adslAturPerfCurr15MinUasL OBJECT-TYPE 804 SYNTAX PerfCurrentCount 805 UNITS "seconds" 806 MAX-ACCESS read-only 807 STATUS current 808 DESCRIPTION 809 "Count of seconds in the current 15 minute interval 810 when there was Unavailable Errored Seconds." 811 REFERENCE "ITU G.997.1 Section 7.2.1.2.9 " 812 ::= { adslAturPerfDataExtEntry 4 } 814 adslAturPerfCurr1DaySesL OBJECT-TYPE 815 SYNTAX AdslPerfCurrDayCount 816 UNITS "seconds" 817 MAX-ACCESS read-only 818 STATUS current 819 DESCRIPTION 820 "Count of the number of seconds when there was Severe 821 Errored Seconds during the current day as measured by 822 adslAturPerfCurr1DayTimeElapsed." 823 REFERENCE "ITU G.997.1 Section 7.2.1.2.7 " 824 ::= { adslAturPerfDataExtEntry 5 } 826 adslAturPerfCurr1DayUasL OBJECT-TYPE 827 SYNTAX AdslPerfCurrDayCount 828 UNITS "seconds" 829 MAX-ACCESS read-only 830 STATUS current 831 DESCRIPTION 832 "Count of the number of seconds when there was 833 Unavailable Errored Seconds during the current 834 day as measured by adslAturPerfCurr1DayTimeElapsed." 835 REFERENCE "ITU G.997.1 Section 7.2.1.2.9 " 836 ::= { adslAturPerfDataExtEntry 6 } 838 adslAturPerfPrev1DaySesL OBJECT-TYPE 839 SYNTAX AdslPerfPrevDayCount 840 UNITS "seconds" 841 MAX-ACCESS read-only 842 STATUS current 843 DESCRIPTION 844 "Count of seconds in the interval when there was 845 severed errored second within the most recent previous 846 1-day period." 847 REFERENCE "ITU G.997.1 Section 7.2.1.2.7 " 848 ::= { adslAturPerfDataExtEntry 7 } 850 adslAturPerfPrev1DayUasL OBJECT-TYPE 851 SYNTAX AdslPerfPrevDayCount 852 UNITS "seconds" 853 MAX-ACCESS read-only 854 STATUS current 855 DESCRIPTION 856 "Count of seconds in the interval when there was 857 unavailable errored second within the most recent 858 previous 1-day period." 859 REFERENCE "ITU G.997.1 Section 7.2.1.2.9 " 860 ::= { adslAturPerfDataExtEntry 8 } 862 adslAturIntervalExtTable OBJECT-TYPE 863 SYNTAX SEQUENCE OF AdslAturIntervalExtEntry 864 MAX-ACCESS not-accessible 865 STATUS current 866 DESCRIPTION 867 "This table provides one row for each ATUC 868 performance data collection interval. 869 ADSL physical interfaces are 870 those ifEntries where ifType is equal to adsl(94)." 871 ::= { adslExtMibObjects 21 } 873 adslAturIntervalExtEntry OBJECT-TYPE 874 SYNTAX AdslAturIntervalExtEntry 875 MAX-ACCESS not-accessible 876 STATUS current 877 DESCRIPTION "An entry in the adslAturIntervalExtTable." 878 AUGMENTS { adslAturIntervalEntry } 879 ::= { adslAturIntervalExtTable 1 } 881 AdslAturIntervalExtEntry ::= 882 SEQUENCE { 883 adslAturIntervalSesL PerfIntervalCount, 884 adslAturIntervalUasL PerfIntervalCount 885 } 887 adslAturIntervalSesL OBJECT-TYPE 888 SYNTAX PerfIntervalCount 889 UNITS "seconds" 890 MAX-ACCESS read-only 891 STATUS current 892 DESCRIPTION 893 "Count of seconds in the interval when there was 894 severed errors." 895 ::= { adslAturIntervalExtEntry 1 } 897 adslAturIntervalUasL OBJECT-TYPE 898 SYNTAX PerfIntervalCount 899 UNITS "seconds" 900 MAX-ACCESS read-only 901 STATUS current 902 DESCRIPTION 903 "Count of seconds in the interval when there was 904 unavailable errors." 905 ::= { adslAturIntervalExtEntry 2 } 907 adslConfProfileExtTable OBJECT-TYPE 908 SYNTAX SEQUENCE OF AdslConfProfileExtEntry 909 MAX-ACCESS not-accessible 910 STATUS current 911 DESCRIPTION 912 "This table contains ADSL line profile configuration 913 information not defined in the adslLineConfProfileTable 914 from the ADSL-LINE-MIB [RFC2662]. This includes the line 915 mode." 916 ::= { adslExtMibObjects 22 } 918 adslConfProfileExtEntry OBJECT-TYPE 919 SYNTAX AdslConfProfileExtEntry 920 MAX-ACCESS not-accessible 921 STATUS current 922 DESCRIPTION 923 "An entry extends the adslLineConfProfileEntry defined 924 in [RFC2662]. Each entry corresponds to an ADSL line 925 profile." 926 AUGMENTS { adslLineConfProfileEntry } 927 ::= { adslConfProfileExtTable 1 } 929 AdslConfProfileExtEntry ::= 930 SEQUENCE { 931 adslConfProfileLineType INTEGER 932 } 934 adslConfProfileLineType OBJECT-TYPE 935 SYNTAX INTEGER { 936 noChannel (1), -- no channels exist 937 fastOnly (2), -- fast channel exists only 938 interleavedOnly (3), -- interleaved channel exists 939 -- only 940 fastOrInterleaved (4),-- either fast or interleaved 941 -- channels can exist, but 942 -- only one at any time 943 fastAndInterleaved (5)-- both fast or interleaved 944 -- channels exist 945 } 946 MAX-ACCESS read-create 947 STATUS current 948 DESCRIPTION 949 " 950 This object is used to configure the ADSL physical line 951 mode. " 952 ::= { adslConfProfileExtEntry 1 } 954 adslAlarmConfProfileExtTable OBJECT-TYPE 955 SYNTAX SEQUENCE OF AdslAlarmConfProfileExtEntry 956 MAX-ACCESS not-accessible 957 STATUS current 958 DESCRIPTION 959 "This table extends the adslLineAlarmConfProfileTable 960 and provides threshold parameters for all the counters 961 defined in this MIB module." 962 ::= { adslExtMibObjects 23 } 964 adslAlarmConfProfileExtEntry OBJECT-TYPE 965 SYNTAX AdslAlarmConfProfileExtEntry 966 MAX-ACCESS not-accessible 967 STATUS current 968 DESCRIPTION 969 "An entry extends the adslLineAlarmConfProfileTable 970 defined in [RFC2662]. Each entry corresponds to 971 an ADSL alarm profile." 972 AUGMENTS { adslLineAlarmConfProfileEntry } 973 ::= { adslAlarmConfProfileExtTable 1 } 975 AdslAlarmConfProfileExtEntry ::= 976 SEQUENCE { 977 adslAtucThreshold15MinFailedFastR Unsigned32, 978 adslAtucThreshold15MinSesL Unsigned32, 979 adslAtucThreshold15MinUasL Unsigned32 980 } 982 adslAtucThreshold15MinFailedFastR OBJECT-TYPE 983 SYNTAX Unsigned32 984 UNITS "seconds" 985 MAX-ACCESS read-create 986 STATUS current 987 DESCRIPTION 988 "The number of failed retrains encountered by an 989 ADSL interface within any giving 15 minutes performance 990 data collection period, which cause the SNMP agent 991 to send an adslAtucFailedFastRTrap. One trap will be 992 sent per interval per interface. A value '0' will 993 disable the trap." 994 ::= { adslAlarmConfProfileExtEntry 1 } 996 adslAtucThreshold15MinSesL OBJECT-TYPE 997 SYNTAX Unsigned32 998 UNITS "seconds" 999 MAX-ACCESS read-create 1000 STATUS current 1001 DESCRIPTION 1002 "The number of Severe errored seconds encountered by an 1003 ADSL interface withing any giving 15 minutes performance 1004 data collection period, which cause the SNMP agent 1005 to send an adslAtucSesLTrap. One trap will be 1006 sent per interval per interface. A value '0' will 1007 disable the trap." 1008 ::= { adslAlarmConfProfileExtEntry 2 } 1009 adslAtucThreshold15MinUasL OBJECT-TYPE 1010 SYNTAX Unsigned32 1011 UNITS "seconds" 1012 MAX-ACCESS read-create 1013 STATUS current 1014 DESCRIPTION 1015 "The number of unavailable errored seconds encountered 1016 by an ADSL interface withing any giving 15 minutes 1017 performance data collection period, which cause the 1018 SNMP agent to send an adslAtucUasLThreshTrap. 1019 One trap will be sent per interval per interface. 1020 A value '0' will disable the trap." 1021 ::= { adslAlarmConfProfileExtEntry 3 } 1023 -- trap definitions 1025 adslExtTraps OBJECT IDENTIFIER ::= { adslExtMibObjects 24 } 1027 adslExtAtucTraps OBJECT IDENTIFIER ::= { adslExtTraps 1 } 1029 adslAtucFailedFastRThreshTrap NOTIFICATION-TYPE 1030 OBJECTS { adslAtucPerfCurr15MinFailedFastR } 1031 STATUS current 1032 DESCRIPTION 1033 "Failed Fast Retrains 15 minutes threshold reached." 1034 ::= { adslExtAtucTraps 0 1 } 1036 adslAtucSesLThreshTrap NOTIFICATION-TYPE 1037 OBJECTS { adslAtucPerfCurr15MinSesL } 1038 STATUS current 1039 DESCRIPTION 1040 "Severe errored seconds 15 minutes threshold reached." 1041 ::= { adslExtAtucTraps 0 2 } 1043 adslAtucUasLThreshTrap NOTIFICATION-TYPE 1044 OBJECTS { adslAtucPerfCurr15MinUasL } 1045 STATUS current 1046 DESCRIPTION 1047 "Unavailable seconds 15 minutes threshold reached." 1048 ::= { adslExtAtucTraps 0 3 } 1050 -- conformance information 1052 adslExtConformance OBJECT IDENTIFIER ::= { adslExtMIB 2 } 1054 adslExtGroups OBJECT IDENTIFIER ::= { adslExtConformance 1 } 1055 adslExtCompliances OBJECT IDENTIFIER ::= { adslExtConformance 2 } 1056 -- ATU-C agent compliance statements 1058 adslExtLineMibAtucCompliance MODULE-COMPLIANCE 1059 STATUS current 1060 DESCRIPTION 1061 "The compliance statement for SNMP entities which 1062 manage ADSL ATU-C interfaces." 1064 MODULE -- this module 1065 MANDATORY-GROUPS 1066 { 1067 adslExtLineGroup, 1068 adslExtLineConfProfileControlGroup, 1069 adslExtLineAlarmConfProfileGroup 1070 } 1072 GROUP adslExtAtucPhysPerfRawCounterGroup 1073 DESCRIPTION 1074 "This group is optional. Implementations which 1075 require continuous ATU-C physical event counters 1076 should implement this group." 1078 GROUP adslExtAturPhysPerfRawCounterGroup 1079 DESCRIPTION 1080 "This group is optional. Implementations which 1081 require continuous ATU-R physical event counters 1082 should implement this group." 1084 OBJECT adslAtucThreshold15MinFailedFastR 1085 MIN-ACCESS read-write 1086 DESCRIPTION 1087 "Read-write access is applicable when 1088 static profiles are implemented." 1090 OBJECT adslAtucThreshold15MinSesL 1091 MIN-ACCESS read-write 1092 DESCRIPTION 1093 "Read-write access is applicable when 1094 static profiles are implemented." 1096 OBJECT adslAtucThreshold15MinUasL 1097 MIN-ACCESS read-write 1098 DESCRIPTION 1099 "Read-write access is applicable when 1100 static profiles are implemented." 1102 OBJECT adslLineConfProfileDualLite 1103 MIN-ACCESS read-only 1104 DESCRIPTION 1105 "Read-only access is applicable when static 1106 profiles are implemented." 1108 ::= { adslExtCompliances 1 } 1110 -- units of conformance 1111 adslExtLineGroup OBJECT-GROUP 1112 OBJECTS { 1113 adslLineConfProfileDualLite, 1114 adslLineTransAtucCap, 1115 adslLineTransAtucConfig, 1116 adslLineTransAtucActual, 1117 adslLineGlitePowerState 1118 } 1119 STATUS current 1120 DESCRIPTION 1121 "A collection of objects providing configuration 1122 information about an ADSL Line." 1123 ::= { adslExtGroups 1 } 1125 adslExtAtucPhysPerfRawCounterGroup OBJECT-GROUP 1126 OBJECTS { 1127 adslAtucPerfStatFastR, 1128 adslAtucPerfStatFailedFastR, 1129 adslAtucPerfCurr15MinFastR, 1130 adslAtucPerfCurr15MinFailedFastR, 1131 adslAtucPerfCurr1DayFastR, 1132 adslAtucPerfCurr1DayFailedFastR, 1133 adslAtucPerfPrev1DayFastR, 1134 adslAtucPerfPrev1DayFailedFastR, 1135 adslAtucPerfStatSesL, 1136 adslAtucPerfStatUasL, 1137 adslAtucPerfCurr15MinSesL, 1138 adslAtucPerfCurr15MinUasL, 1139 adslAtucPerfCurr1DaySesL, 1140 adslAtucPerfCurr1DayUasL, 1141 adslAtucPerfPrev1DaySesL, 1142 adslAtucPerfPrev1DayUasL, 1143 adslAtucIntervalFastR, 1144 adslAtucIntervalFailedFastR, 1145 adslAtucIntervalSesL, 1146 adslAtucIntervalUasL 1147 } 1148 STATUS current 1149 DESCRIPTION 1150 "A collection of objects providing raw performance 1151 counts on an ADSL Line (ATU-C end)." 1153 ::= { adslExtGroups 2 } 1155 adslExtAturPhysPerfRawCounterGroup OBJECT-GROUP 1156 OBJECTS { 1157 adslAturPerfStatSesL, 1158 adslAturPerfStatUasL, 1159 adslAturPerfCurr15MinSesL, 1160 adslAturPerfCurr15MinUasL, 1161 adslAturPerfCurr1DaySesL, 1162 adslAturPerfCurr1DayUasL, 1163 adslAturPerfPrev1DaySesL, 1164 adslAturPerfPrev1DayUasL, 1165 adslAturIntervalSesL, adslAturIntervalUasL 1166 } 1167 STATUS current 1168 DESCRIPTION 1169 "A collection of objects providing raw performance 1170 counts on an ADSL Line (ATU-C end)." 1171 ::= { adslExtGroups 3 } 1173 adslExtLineConfProfileControlGroup OBJECT-GROUP 1174 OBJECTS { 1175 adslConfProfileLineType 1176 } 1177 STATUS current 1178 DESCRIPTION 1179 "A collection of objects providing profile 1180 control for the ADSL system." 1181 ::= { adslExtGroups 4 } 1183 adslExtLineAlarmConfProfileGroup OBJECT-GROUP 1184 OBJECTS { 1185 adslAtucThreshold15MinFailedFastR, 1186 adslAtucThreshold15MinSesL, 1187 adslAtucThreshold15MinUasL 1188 } 1189 STATUS current 1190 DESCRIPTION 1191 "A collection of objects providing alarm profile 1192 control for the ADSL system." 1193 ::= { adslExtGroups 5 } 1195 adslExtNotificationsGroup NOTIFICATION-GROUP 1196 NOTIFICATIONS { 1197 adslAtucFailedFastRThreshTrap, 1198 adslAtucSesLThreshTrap, 1199 adslAtucUasLThreshTrap 1200 } 1201 STATUS current 1202 DESCRIPTION 1203 "The collection of ADSL 2 notifications." 1204 ::= { adslExtGroups 6 } 1206 END 1208 9. Acknowledgments 1210 This document is a product of the ADSL MIB Working Group. 1212 10. References 1214 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture 1215 for Describing SNMP Management Frameworks", RFC 2571, April 1216 1999. 1218 [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification 1219 of Management Information for TCP/IP-based Internets", STD 1220 16, RFC 1155, May 1990. 1222 [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification 1223 of Management Information for TCP/IP-based Internets", STD 1224 16, RFC 1155, May 1990. 1226 [RFC1215] M. Rose, "A Convention for Defining Traps for use with the 1227 SNMP", RFC 1215, March 1991. 1229 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1230 Rose, M., and S. Waldbusser, "Structure of Management 1231 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1232 1999. 1234 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1235 Rose, M., and S. Waldbusser, "Textual Conventions for 1236 SMIv2", STD 58, RFC 2579, April 1999. 1238 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1239 Rose, M., and S. Waldbusser, "Conformance Statements for 1240 SMIv2", STD 58, RFC 2580, April 1999. 1242 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 1243 Network Management Protocol", STD 15, RFC 1157, May 1990. 1245 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1246 "Introduction to Community-based SNMPv2", RFC 1901, January 1247 1996. 1249 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1250 "Transport Mappings for Version 2 of the Simple Network 1251 Management Protocol (SNMPv2)", RFC 1906, January 1996. 1253 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 1254 Processing and Dispatching for the Simple Network Management 1255 Protocol (SNMP)", RFC 2572, April 1999. 1257 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 1258 (USM) for version 3 of the Simple Network Management 1259 Protocol (SNMPv3)", RFC 2574, April 1999. 1261 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1262 "Protocol Operations for Version 2 of the Simple Network 1263 Management Protocol (SNMPv2)", RFC 1905, January 1996. 1265 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", 1266 RFC 2573, April 1999. 1268 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 1269 Access Control Model (VACM) for the Simple Network 1270 Management Protocol (SNMP)", RFC 2575, April 1999. 1272 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 1273 "Introduction to Version 3 of the Internet-standard Network 1274 Management Framework", RFC 2570, April 1999. 1276 [RFC1213] McCloghrie, K. and M. Rose, "Management Information Base for 1277 Network Management of TCP/IP-based internets - MIB-II", 1278 STD 17, RFC 1213, March 1991. 1280 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", 1281 RFC 2863, June 2000. 1283 [RFC2662] G. Bathrick, F. Ly "Definitions of Managed Objects for the 1284 ADSL Lines", May 14, 1999. 1286 11. Security Considerations 1288 1) Blocking unauthorized access to the ADSL MIB via the element 1289 management system is outside the scope of this document. It should be 1290 noted that access to the MIB permits the unauthorized entity to 1291 modify the profiles (sect 6.4) such that both subscriber service and 1292 network operations can be interfered with. Subscriber service can be 1293 altered by modifying any of a number of service characteristics such 1294 as rate partitioning and maximum transmission rates. Network 1295 operations can be impacted by modification of trap thresholds such as 1296 SNR margins. 1298 2) There are a number of managed objects in this MIB that may be 1299 considered to contain sensitive information. In particular, the 1300 certain objects may be considered sensitive in many environments, 1301 since it would allow an intruder to obtain information about which 1302 vendor's equipment is in use on the network. Therefore, it may be 1303 important in some environments to control read access to these 1304 objects and possibly to even encrypt the values of these object when 1305 sending them over the network via SNMP. Not all versions of SNMP 1306 provide features for such a secure environment. 1308 SNMPv1 by itself is such an insecure environment. Even if the 1309 network itself is secure (for example by using IPSec), even then, 1310 there is no control as to who on the secure network is allowed to 1311 access and GET (read) the objects in this MIB. It is recommended 1312 that the implementors consider the security features as provided by 1313 the SNMPv3 framework. Specifically, the use of the User-based 1314 Security Model RFC 2574 [21] and the View-based Access Control Model 1315 RFC 2575 [23] is recommended. 1317 It is then a customer/user responsibility to ensure that the SNMP 1318 entity giving access to an instance of this MIB, is properly 1319 configured to give access to those objects only to those principals 1320 (users) that have legitimate rights to access them. 1322 3) ADSL layer connectivity from the ATU-R will permit the subscriber 1323 to manipulate both the ADSL link directly and the AOC/EOC channels 1324 for their own loop. For example, unchecked or unfiltered 1325 fluctuations initiated by the subscriber could generate sufficient 1326 traps to potentially overwhelm either the management interface to the 1327 network or the element manager. Other attacks affecting the ATU-R 1328 portions of the MIB may also be possible. 1330 11. Intellectual Property Notice 1332 The IETF takes no position regarding the validity or scope of any 1333 intellectual property or other rights that might be claimed to 1334 pertain to the implementation or use of the technology described in 1335 this document or the extent to which any license under such rights 1336 might or might not be available; neither does it represent that it 1337 has made any effort to identify any such rights. Information on the 1338 IETF's procedures with respect to rights in standards-track and 1339 standards-related documentation can be found in BCP-11. Copies of 1340 claims of rights made available for publication and any assurances of 1341 licenses to be made available, or the result of an attempt made to 1342 obtain a general license or permission for the use of such 1343 proprietary rights by implementers or users of this specification can 1344 be obtained from the IETF Secretariat." 1346 The IETF invites any interested party to bring to its attention any 1347 copyrights, patents or patent applications, or other proprietary 1348 rights which may cover technology that may be required to practice 1349 this standard. Please address the information to the IETF Executive 1350 Director. 1352 12. Authors' Addresses 1354 Faye Ly 1355 Salira Optical Systems 1356 2698 Orchard Parkway 1357 San Jose, CA 95134 1359 Phone: +1 408-382-0088 1360 Fax: +1 408-382-1688 1361 EMail: faye@salira.com 1363 Gregory Bathrick 1364 NOKIA High Speed Access Nodes 1365 1310 Redwood Way, 1366 Petaluma, CA 94954, USA 1368 Phone: +1 707-793-7030 1369 Fax: +1 707-792-0850 1370 EMail: greg.bathrick@nokia.com 1372 13. Full Copyright Statement 1374 Copyright (C) The Internet Society (2001). All Rights Reserved. 1376 This document and translations of it may be copied and furnished to 1377 others, and derivative works that comment on or otherwise explain it 1378 or assist in its implementation may be prepared, copied, published 1379 and distributed, in whole or in part, without restriction of any 1380 kind, provided that the above copyright notice and this paragraph are 1381 included on all such copies and derivative works. However, this 1382 document itself may not be modified in any way, such as by removing 1383 the copyright notice or references to the Internet Society or other 1384 Internet organizations, except as needed for the purpose of 1385 developing Internet standards in which case the procedures for 1386 copyrights defined in the Internet Standards process must be 1387 followed, or as required to translate it into languages other than 1388 English. 1390 The limited permissions granted above are perpetual and will not be 1391 revoked by the Internet Society or its successors or assigns. 1393 This document and the information contained herein is provided on an 1394 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1395 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1396 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1397 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1398 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1400 Acknowledgement 1402 Funding for the RFC Editor function is currently provided by the 1403 Internet Society. 1405 Table of Contents 1407 1. Status of this Memo ..................................... 1 1408 2. Abstract ............................................... 1 1409 3. The SNMP Network Management Framework ................... 1 1410 4. Introduction ............................................ 2 1411 5. Relationship of the ADSL LINE EXTENSION MIB with standard MIBs 1412 ............................................ 3 1413 6. Conventions used in the MIB ............................. 3 1414 7. Conformance and Compliance .............................. 5 1415 8. Definitions ............................................. 5 1416 9. Acknowledgments ......................................... 25 1417 10. References ............................................. 26 1418 11. Security Considerations ................................ 27 1419 12. Authors' Addresses ..................................... 28 1420 13. Full Copyright Satement ................................ 29