idnits 2.17.1 draft-ietf-adslmib-vdsl2-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 18. -- Found old boilerplate from RFC 3978, Section 5.5 on line 7750. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 7727. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 7734. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 7740. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 66 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the 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 2006) is 6669 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: 'RFCxxx' is mentioned on line 1939, but not defined == Missing Reference: 'RFCxxxx' is mentioned on line 1947, but not defined -- Possible downref: Non-RFC (?) normative reference: ref. 'G.992.1' -- Possible downref: Non-RFC (?) normative reference: ref. 'G.992.2' -- Possible downref: Non-RFC (?) normative reference: ref. 'G.992.3' -- Possible downref: Non-RFC (?) normative reference: ref. 'G.992.4' -- Possible downref: Non-RFC (?) normative reference: ref. 'G.992.5' -- Possible downref: Non-RFC (?) normative reference: ref. 'G.993.1' -- Possible downref: Non-RFC (?) normative reference: ref. 'G.993.2' -- Possible downref: Non-RFC (?) normative reference: ref. 'G.997.1' -- Possible downref: Non-RFC (?) normative reference: ref. 'TR-129' Summary: 3 errors (**), 0 flaws (~~), 5 warnings (==), 16 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group M. Morgenstern 3 Internet-Draft ECI Telecom Ltd. 4 Expires: July 5, 2006 S. Baillie 5 U. Bonollo 6 NEC Australia 7 January 2006 9 Definitions of Managed Objects for Very High Speed Digital Subscriber 10 Line 2 (VDSL2) 11 draft-ietf-adslmib-vdsl2-00.txt 13 Status of this Memo 15 By submitting this Internet-Draft, each author represents that any 16 applicable patent or other IPR claims of which he or she is aware 17 have been or will be disclosed, and any of which he or she becomes 18 aware will be disclosed, in accordance with Section 6 of BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF), its areas, and its working groups. Note that 22 other groups may also distribute working documents as Internet- 23 Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 The list of current Internet-Drafts can be accessed at 31 http://www.ietf.org/ietf/1id-abstracts.txt. 33 The list of Internet-Draft Shadow Directories can be accessed at 34 http://www.ietf.org/shadow.html. 36 This Internet-Draft will expire on July 5, 2006. 38 Copyright Notice 40 Copyright (C) The Internet Society (2006). 42 Abstract 44 This document defines a Management Information Base (MIB) module for 45 use with network management protocols in the Internet community. In 46 particular, it describes objects used for managing parameters of the 47 "Very High Speed Digital Subscriber Line 2 (VDSL2)" interface type, 48 which are also applicable for managing ADSL, ADSL2, and ADSL2+ 49 interfaces. 51 Table of Contents 53 1. The Internet-Standard Management Framework . . . . . . . . . 3 54 2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 3 55 2.1. Relationship to other MIBs . . . . . . . . . . . . . . . 4 56 2.2. IANA Considerations . . . . . . . . . . . . . . . . . . . 6 57 2.3. Conventions Used in the MIB Module . . . . . . . . . . . 7 58 2.4. Structure . . . . . . . . . . . . . . . . . . . . . . . . 13 59 2.5. Persistence . . . . . . . . . . . . . . . . . . . . . . . 16 60 2.6. Line Topology . . . . . . . . . . . . . . . . . . . . . . 18 61 2.7. Counters, Interval Buckets, and Thresholds . . . . . . . 19 62 2.8. Profiles . . . . . . . . . . . . . . . . . . . . . . . . 21 63 2.9. Notifications . . . . . . . . . . . . . . . . . . . . . . 25 64 3. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 26 65 4. Implementation Analysis . . . . . . . . . . . . . . . . . . . 153 66 5. Security Considerations . . . . . . . . . . . . . . . . . . . 153 67 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 160 68 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 161 69 7.1. Normative References . . . . . . . . . . . . . . . . . . 161 70 7.2. Informative References . . . . . . . . . . . . . . . . . 162 71 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 163 72 Intellectual Property and Copyright Statements . . . . . . . . . 164 74 1. The Internet-Standard Management Framework 76 For a detailed overview of the documents that describe the current 77 Internet-Standard Management Framework, please refer to Section 7 of 78 RFC 3410 [RFC3410]. 80 Managed objects are accessed via a virtual information store, termed 81 the Management Information Base or MIB. MIB objects are generally 82 accessed through the Simple Network Management Protocol (SNMP). 83 Objects in the MIB are defined using the mechanisms defined in the 84 Structure of Management Information (SMI). This memo specifies a MIB 85 module that is compliant to the SMIv2, which is described in STD 58, 86 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 87 [RFC2580]. 89 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 90 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 91 document are to be interpreted as described in RFC 2119 [RFC2119]. 93 2. Overview 95 This document defines a Management Information Base (MIB) module for 96 use with network management protocols in the Internet community for 97 the purpose of managing VDSL2, ADSL, ADSL2, and ADSL2+ lines. 99 The MIB module described in RFC 2662 [RFC2662] describes objects used 100 for managing Asymmetric Bit-Rate DSL (ADSL) interfaces per 101 [T1E1.413], [G.992.1], and [G.992.2]. These object descriptions are 102 based upon the specifications for the ADSL Embedded Operations 103 Channel (EOC) as defined in American National Standards Institute 104 (ANSI) T1E1.413/1995 [T1E1.413] and International Telecommunication 105 Union (ITU-T) G.992.1 [G.992.1] and G.992.2 [G.992.2]. 107 The MIB module described in RFC xxxx 108 (draft-ietf-adslmib-adsl2-05.txt) is a wider management model that 109 includes, in addition to ADSL technology, the ADSL2 and ADSL2+ 110 technologies per G.992.3, G.992.4, and G.992.5 ([G.992.3], [G.992.4], 111 and [G.992.5] respectively). 113 This document does not obsolete RFC 2662 [RFC2662], or RFC xxxx 114 (draft-ietf-adslmib-adsl2-05.txt) but rather provides a more 115 comprehensive management model that addresses the VDSL2 technology 116 per G.993.2 ([G.993.2]) as well as ADSL, ADSL2 and ADSL2+ 117 technologies. 119 Additionally, the management framework for VDSL2 lines [TR-129] 120 specified by the Digital Subscriber Line Forum (DSLF) has been taken 121 into consideration. That framework is based on ITU-T G.997.1 122 standard [G.997.1]. 124 Note that the management model according to this document does not 125 allow managing VDSL technology per G.993.1 ([G.993.1]). VDSL lines 126 MUST be managed by RFC 3728 [RFC3728]. 128 The MIB module is located in the MIB tree under MIB 2 transmission, 129 as discussed in the MIB-2 Integration (RFC 2863 [RFC2863]) section of 130 this document. 132 2.1. Relationship to other MIBs 134 This section outlines the relationship of this MIB module with other 135 MIB modules described in RFCs. Specifically, IF-MIB as presented in 136 RFC 2863 [RFC2863] is discussed. 138 2.1.1. General IF-MIB Integration (RFC 2863) 140 The VDSL2 Line MIB specifies the detailed attributes of a data 141 interface. As such, it needs to integrate with RFC 2863 [RFC2863]. 142 The IANA has assigned the following ifTypes, which may be applicable 143 for VDSL2 lines as well as for ADSL, ADSL2 and ADSL2+ lines: 145 IANAifType ::= TEXTUAL-CONVENTION 146 ... 147 SYNTAX INTEGER { 148 ... 149 channel(70), -- channel 150 ADSL (94), -- Asymmetric Digital Subscriber Loop 151 ... 152 Interleave(124), -- Interleaved Channel 153 Fast(125), -- Fast Channel 154 ... 155 ADSL2 (230), -- Asymmetric Digital Subscriber Loop 2 156 VDSL2 (xxx), -- Very High Speed Digital Subscriber Loop 2 157 ... 158 } 160 ADSL lines that are identified with ifType=ADSL (94) MUST be managed 161 with the MIB specified by RFC2662. ADSL, ADSL2, and ADSL2+ lines 162 identified with ifType=ADSL2 (230) MUST be managed with the MIB 163 specified by RFC xxxx (draft-ietf-adslmib-adsl2-05.txt). VDSL2, 164 ADSL, ADSL2, and ADSL2+ lines identified with ifType=VDSL2 (xxx) MUST 165 be managed with the MIB specified by this document. 167 In any case, the SNMP agent may use either ifType=Interleave (124) or 168 Fast (125) for each channel, e.g., depending on whether or not it is 169 capable of using an interleaver on that channel. It may use the 170 ifType=channel (70) when all channels are capable of using an 171 interleaver (e.g., for ADSL2 xtus). 173 Note that the ifFixedLengthGroup from RFC 2863 [RFC2863] MUST be 174 supported and that the ifRcvAddressGroup does not apply to this MIB 175 module. 177 2.1.2. Usage of ifTable 179 The MIB branch identified by ifType contains tables appropriate for 180 the interface types described above. Most such tables extend the 181 ifEntry table, and are indexed by ifIndex. For interfaces in systems 182 implementing this MIB module, those table entries indexed by ifIndex 183 MUST be persistent. 185 The following attributes are part of the mandatory 186 ifGeneralInformationGroup in the Interfaces MIB [RFC2863], and are 187 not duplicated in the VDSL2 Line MIB. 189 =================================================================== 190 ifIndex Interface index. 192 ifDescr See interfaces MIB. 194 ifType VDSL2 (230) or 195 Channel (70) or 196 Interleave (124) or 197 Fast (125) 199 ifSpeed Set as appropriate. 201 ifPhysAddress This object MUST have an octet string 202 with zero length. 204 ifAdminStatus See interfaces MIB. 206 ifOperStatus See interfaces MIB. 208 ifLastChange See interfaces MIB. 210 ifName See interfaces MIB. 212 ifAlias See interfaces MIB. 214 ifLinkUpDownTrapEnable Default to enabled(1). 216 ifHighSpeed Set as appropriate. 218 ifConnectorPresent Set as appropriate. 220 =================================================================== 221 Figure 1: Use of ifTable Objects 223 2.2. IANA Considerations 225 The VDSL2-LINE-MIB module requires the allocation of a new ifType 226 value for Very High Speed Digital Subscriber Loop Version 2, to 227 distinguish between ADSL lines that are managed with the RFC2662 228 management model, ADSL/ADSL2 and ADSL2+ lines that are managed with 229 the RFC xxxx (draft-ietf-adslmib-adsl2-05.txt) management model, and 230 VDSL2/ADSL/ADSL2 and ADSL2+ lines that are managed with the model 231 defined in this document. 233 Also the VDSL2-LINE-MIB module requires the allocation of a single 234 object identifier for its MODULE-IDENTITY. The IANA should allocate 235 this object identifier in the transmission subtree. 237 2.3. Conventions Used in the MIB Module 239 2.3.1. Naming Conventions 241 atuc ADSL/ADSL2 or ADSL2+ line termination unit - 242 Central office 243 atur ADSL/ADSL2 or ADSL2+ line termination unit - 244 Remote site 245 CRC Cyclical redundancy check 246 DELT Dual Ended Loop Test 247 ES Errored second 248 FEC Forward Error Correction 249 LOF Loss of framing 250 LOS Loss of signal 251 LOSS LOS Second 252 SES Severely-errored second 253 SNR Signal-to-noise ratio 254 UAS Unavailable second 255 vtuc VDSL2 line termination unit - Central office 256 vtur VDSL2 line termination unit - Remote site 257 Xtuc ADSL/ADSL2/ADSL2+ or VDSL2 line termination unit - 258 Central office 259 Xtur ADSL/ADSL2/ADSL2+ or VDSL2 line termination unit - 260 Remote site 261 xtu A terminal unit; either an Xtuc or Xtur 263 2.3.2. Textual Conventions 265 The following textual conventions are defined to reflect the line 266 topology in the MIB module (further discussed in the following 267 section), the various transmission modes, power states, 268 synchronization states, possible values for various configuration 269 parameters, status parameters, and other parameter types. 271 o Xdsl2Unit: 273 Attributes with this syntax uniquely identify each unit in the 274 VDSL2/ADSL/ADSL2/ADSL2+ link. It mirrors the EOC addressing 275 mechanism: 277 xtuc(1) - central office (CO) terminal unit 278 xtur(2) - customer premises equipment (CPE) 279 terminal unit 281 o Xdsl2Direction: 283 Attributes with this syntax uniquely identify a transmission 284 direction in a VDSL2/ADSL/ADSL2/ADSL2+ link. Upstream direction 285 is a transmission from the customer premises equipment (CPE) 286 towards the central office (CO), while downstream direction is a 287 transmission from the CO towards the CPE. 289 upstream(1) - Transmission from the CPE to the CO 290 downstream(2) - Transmission from the CO to the CPE 292 o Xdsl2TransmissionModeType: 294 Attributes with this syntax reference the list of possible 295 transmission modes for VDSL2/ADSL/ADSL2 or ADSL2+. 297 Specified as a BITS construct, there are currently a few dozen 298 transmission modes in the list. 300 o Xdsl2RaMode: 302 Attributes with this syntax reference if and how Rate-Adaptive 303 synchronization is being used on the respective VDSL2/ADSL/ADSL2 304 or ADSL2+ link: 306 manual (1) - No Rate-Adaptation. The initialization process 307 attempts to synchronize to a specified rate. 308 rainit (2) - Rate-Adaptation during initialization process 309 only, which attempts to synchronize to a rate 310 between minimum and maximum specified values. 311 dynamicRa (3) - Dynamic Rate-Adaptation during initialization 312 process as well as during SHOWTIME. 314 o Xdsl2InitResult: 316 Attributes with this syntax reference the recent result of a full 317 initialization attempt: 319 noFail (0) - Successful initialization 320 configError (1) - Configuration failure 321 configNotFeasible (2) - Configuration details not supported 322 commFail (3) - Communication failure 323 noPeerAtu (4) - Peer ATU not detected 324 otherCause (5) - Other initialization failure reason 326 o Xdsl2OperationModes: 328 Attributes with this syntax uniquely identify an XDSL mode, which 329 is a category associated with each transmission mode defined for 330 the VDSL2/ADSL/ADSL2 or ADSL2+ link. Part of the line 331 configuration profile depends on the XDSL Mode: 333 ------***************************************************** 334 ----- The following list will be changed. Instead of the 335 ----- the current list we'll add a list that follows the xTSE 336 ------***************************************************** 338 defMode (1), - The default/generic PSD configuration. 339 The default configuration will be used 340 when no other matching mode specific 341 configuration can be found. 342 adsl (2), - ADSL (POTS or ISDN) 343 adsl2Pots (3), - ADSL2 (ISDN) 344 adsl2Isdn (4), - ADSL2 (ISDN) 345 adsl2PlusPots (5), - ADSL2+ (POTS) 346 adsl2PlusIsdn (6), - ADSL2+ (ISDN) 347 adsl2ReachExtended (7)- Reach Extended ADSL2 349 o Xdsl2PowerMngState: 351 Attributes with this syntax uniquely identify each power 352 management state defined for the VDSL2/ADSL/ADSL2 or ADSL2+ link. 353 For VDSL2 links only L0 and L3 states are supported: 355 l0(1) - L0 - Full power management state 356 l1(2) - L1 - Low power management state (for G.992.2) 357 l2(3) - L2 - Low power management state (for G.992.3, 358 G.992.4, and G.992.5) 359 l3(4) - L3 - Idle power management state 361 o Xdsl2ConfPmsForce: 363 Attributes with this syntax are configuration parameters that 364 reference the desired power management state for the VDSL2/ADSL/ 365 ADSL2 or ADSL2+ link. For VDSL2 links only L0 and L3 states are 366 supported: 368 l3toL0 (0) - Perform a transition from L3 to L0 (Full 369 power management state) 370 l0toL2 (2) - Perform a transition from L0 to L2 (Low 371 power management state) 372 l0orL2toL3 (3) - Perform a transition into L3 (Idle power 373 management state) 375 o Xdsl2LConfProfPmMode: 377 Attributes with this syntax are configuration parameters that 378 reference the power modes/states into which the xTU-C or xTU-R may 379 autonomously transit. 381 This is a BITS structure that allows control of the following 382 transit options: 384 allowTransitionsToIdle (0) - xTU may autonomously transit 385 to idle (L3) state. 386 allowTransitionsToLowPower (1)- xTU may autonomously transit 387 to low-power (L2) state. 389 o Xdsl2LineLdsf: 391 Attributes with this syntax are configuration parameters that 392 control the Loop Diagnostic mode for the VDSL2/ADSL/ADSL2 or 393 ADSL2+ link: 395 inhibit (0) - Inhibit Loop Diagnostic mode 396 force (1) - Force/Initiate Loop Diagnostic mode 398 o Xdsl2LdsfResult: 400 Attributes with this syntax are status parameters that report the 401 result of the recent Loop Diagnostic mode issued for the VDSL2/ 402 ADSL/ADSL2 or ADSL2+ link: 404 none (1) - The default value, in case LDSF was never 405 requested for the associated line. 406 success (2) - The recent command completed 407 successfully. 408 inProgress (3) - The Loop Diagnostics process is in 409 progress. 410 unsupported (4) - The NE or the line card doesn't support 411 LDSF. 412 cannotRun (5) - The NE cannot initiate the command, due 413 to a non specific reason. 414 aborted (6) - The Loop Diagnostics process aborted. 415 failed (7) - The Loop Diagnostics process failed. 416 illegalMode (8) - The NE cannot initiate the command, due 417 to the specific mode of the relevant 418 line. 419 adminUp (9) - The NE cannot initiate the command because 420 the relevant line is administratively 421 'Up'. 422 tableFull (10) - The NE cannot initiate the command, due 423 to reaching the maximum number of rows 424 in the results table. 425 noResources (11) - The NE cannot initiate the command, due 426 to lack of internal memory resources. 428 o Xdsl2SymbolProtection: 430 Attributes with this syntax are configuration parameters that 431 reference the minimum length impulse noise protection (INP) in 432 terms of number of symbols: 434 noProtection (1) - INP not required 435 halfSymbol (2) - INP length = 1/2 symbol 436 singleSymbol (3) - INP length = 1 symbol 437 twoSymbols (4) - INP length = 2 symbols 438 threeSymbols (5) - INP length = 3 symbols 439 fourSymbols (6) - INP length = 4 symbols 440 fiveSymbols (7) - INP length = 5 symbols 441 sixSymbols (8) - INP length = 6 symbols 442 sevenSymbols (9) - INP length = 7 symbols 443 eightSymbols (10) - INP length = 8 symbols 444 nineSymbols (11) - INP length = 9 symbols 445 tenSymbols (12) - INP length = 10 symbols 446 elevenSymbols (13) - INP length = 11 symbols 447 twelveSymbols (14) - INP length = 12 symbols 448 thirteeSymbols (15)- INP length = 13 symbols 449 fourteenSymbols (16)-INP length = 14 symbols 450 fifteenSymbols (17)- INP length = 15 symbols 451 sixteenSymbols (18)- INP length = 16 symbols 453 o Xdsl2MaxBer: 455 Attributes with this syntax are configuration parameters that 456 reference the maximum Bit Error Rate (BER): 458 eminus3 (1) - Maximum BER=E^-3 459 eminus5 (2) - Maximum BER=E^-5 460 eminus7 (3) - Maximum BER=E^-7 462 o Xdsl2ScMaskDs: 464 Attributes with this syntax are configuration parameters that 465 reference the downstream sub-carrier mask. It is a bitmap of up 466 to 4096 bits. 468 o Xdsl2ScMaskUs: 470 Attributes with this syntax are configuration parameters that 471 reference the upstream sub-carrier mask. It is a bitmap of up to 472 4096 bits. 474 o Xdsl2RfiDs: 476 Attributes with this syntax are configuration parameters that 477 reference the downstream notch filters. It is a bitmap of up to 478 4096 bits. 480 o Xdsl2PsdMaskDs: 482 Attributes with this syntax are configuration parameters that 483 reference the downstream power spectrum density (PSD) mask. It is 484 a structure of up to 32 breakpoints, where each breakpoint 485 occupies 3 octets. 487 o Xdsl2PsdMaskUs: 489 Attributes with this syntax are configuration parameters that 490 reference the upstream power spectrum density (PSD) mask. It is a 491 structure of up to 16 breakpoints, where each breakpoint occupies 492 3 octets. 494 o Xdsl2Tssi: 496 Attributes with this syntax are status parameters that reference 497 the transmit spectrum shaping (TSSi). It is a structure of up to 498 32 breakpoints, where each breakpoint occupies 3 octets. 500 o Xdsl2LastTransmittedState: 502 Attributes with this syntax reference the list of initialization 503 states for VDSL2/ADSL/ADSL2 or ADSL2+ modems. The list of states 504 for CO side modems is different from the list of states for the 505 CPE side modems. 507 Specified as an enumeration type, there are currently a few dozen 508 states in the list per each unit side (i.e., CO and CPE). 510 o Xdsl2LineStatus: 512 Attributes with this syntax are status parameters that reflect the 513 failure status for a given endpoint of VDSL2/ADSL/ADSL2 or ADSL2+ 514 link. 516 This is a BITS structure that can report the following failures: 518 noDefect (0) - This bit position positively reports that 519 no defect or failure exist. 520 lossOfFraming (1) - Loss of frame synchronization 521 lossOfSignal (2) - Loss of signal 522 lossOfPower (3) - Loss of power. Usually this failure may 523 be reported for CPE units only 524 initFailure (4) - Recent initialization process failed. 525 Never active on xTU-R. 527 o Xdsl2ChAtmStatus: 529 Attributes with this syntax are status parameters that reflect the 530 failure status for Transmission Convergence (TC) layer of a given 531 ATM interface (data path over a VDSL2/ADSL/ADSL2 or ADSL2+ link). 533 This is a BITS structure that can report the following failures: 535 noDefect (0) - This bit position positively reports 536 that no defect or failure exist. 537 noCellDelineation (1) - The link was successfully 539 initialized but cell delineation 541 was never acquired on the 543 associated ATM data path. 544 lossOfCellDelineation (2)- Loss of cell delineation on the 545 associated ATM data path 547 o Xdsl2ChPtmStatus: 549 Attributes with this syntax are status parameters that reflect the 550 failure status for a given PTM interface (packet data path over a 551 VDSL2/ADSL/ADSL2 or ADSL2+ link). 553 This is a BITS structure that can report the following failures: 555 noDefect (0) - This bit position positively reports that no 556 defect or failure exist. 557 outOfSync (1) - Out of synchronization. 559 2.4. Structure 561 The MIB module is structured into following MIB groups: 563 o Line Configuration, Maintenance, and Status Group: 565 This group supports MIB objects for configuring parameters for the 566 VDSL2/ADSL/ADSL2 or ADSL2+ line and retrieving line status 567 information. It also supports MIB objects for configuring a 568 requested power state or initiating a Dual Ended Line Test (DELT) 569 process in the VDSL2/ADSL/ADSL2 or ADSL2+ line. It contains the 570 following table: 572 - xdsl2LineTable 574 o Channel Status Group: 576 This group supports MIB objects for retrieving channel layer 577 status information. It contains the following table: 579 - xdsl2ChannelStatusTable 581 o Subcarrier Status Group: 583 This group supports MIB objects for retrieving the sub-carrier 584 layer status information, mostly collected by a Dual Ended Line 585 Test (DELT) process. It contains the following table: 587 - xdsl2SCStatusTable 589 o Unit Inventory Group: 591 This group supports MIB objects for retrieving Unit inventory 592 information about units in VDSL2/ADSL/ADSL2 or ADSL2+ lines via 593 the EOC. It contains the following table: 595 - xdsl2LineInventoryTable 597 o Current Performance Group: 599 This group supports MIB objects that provide the current 600 performance information relating to VDSL2/ADSL/ADSL2 and ADSL2+ 601 line, units and channels level. It contains the following tables: 603 - xdsl2PMLineCurrTable 604 - xdsl2PMLineCurrInitTable 605 - xdsl2PMChCurrTable 607 o 15-Minute Interval Performance Group: 609 This group supports MIB objects that provide historic performance 610 information relating to VDSL2/ADSL/ADSL2 and ADSL2+ line, units 611 and channels level in 15-minute intervals. It contains the 612 following tables: 614 - xdsl2PMLineHist15MinTable 615 - xdsl2PMLineInitHist15MinTable 616 - xdsl2PMChHist15MinTable 618 o 1-Day Interval Performance Group: 620 This group supports MIB objects that provide historic performance 621 information relating to VDSL2/ADSL/ADSL2 and ADSL2+ line, units 622 and channels level in 1-day intervals. It contains the following 623 tables: 625 - xdsl2PMLineHist1DayTable 626 - xdsl2PMLineInitHist1DayTable 627 - xdsl2PMChHist1DTable 629 o Configuration Template and Profile Group: 631 This group supports MIB objects for defining configuration 632 profiles for VDSL2/ADSL/ADSL2 and ADSL2+ lines and channels, as 633 well as configuration templates. Each configuration template is 634 comprised of one line configuration profile and one or more 635 channel configuration profiles. This group contains the following 636 tables: 638 - xdsl2LineConfTemplateTable 639 - xdsl2LineConfProfTable 640 - xdsl2LineConfProfModeSpecTable 641 - xdsl2ChConfProfileTable 643 o Alarm Configuration Template and Profile Group: 645 This group supports MIB objects for defining alarm profiles for 646 VDSL2/ADSL/ADSL2 and ADSL2+ lines and channels, as well as alarm 647 templates. Each alarm template is comprised of one line alarm 648 profile and one or more channel alarm profiles. This group 649 contains the following tables: 651 - xdsl2LineAlarmConfTemplateTable 652 - xdsl2LineAlarmConfProfileTable 653 - xdsl2ChAlarmConfProfileTable 655 o Notifications Group: 657 This group defines the notifications supported for VDLS2/ADSL/ 658 ADSL2 and ADSL2+ lines: 660 - xdsl2LinePerfFECSThreshXtuc 661 - xdsl2LinePerfFECSThreshXtur 662 - xdsl2LinePerfESThreshXtuc 663 - xdsl2LinePerfESThreshXtur 664 - xdsl2LinePerfSESThreshXtuc 665 - xdsl2LinePerfSESThreshXtur 666 - xdsl2LinePerfLOSSThreshXtuc 667 - xdsl2LinePerfLOSSThreshXtur 668 - xdsl2LinePerfUASThreshXtuc 669 - xdsl2LinePerfUASThreshXtur 670 - xdsl2LinePerfCodingViolationsThreshXtuc 671 - xdsl2LinePerfCodingViolationsThreshXtur 672 - xdsl2LinePerfCorrectedThreshXtuc 673 - xdsl2LinePerfCorrectedThreshXtur 674 - xdsl2LinePerfFailedFullInitThresh 675 - xdsl2LinePerfFailedShortInitThresh 676 - xdsl2LineStatusChangeXtuc 677 - xdsl2LineStatusChangeXtur 679 2.5. Persistence 681 All read-create objects and most read-write objects defined in this 682 MIB module SHOULD be stored persistently. Following is an exhaustive 683 list of these persistent objects: 684 ------***************************************************** ----- The 685 following list will probably be partially changed 686 ------***************************************************** 688 xdsl2LineCnfgTemplate 689 xdsl2LineAlarmCnfgTemplate 690 xdsl2LineCmndConfPmsf 691 xdsl2LineCmndConfLdsf 692 xdsl2LineCmndAutomodeColdStart 693 xdsl2LConfTempTemplateName 694 xdsl2LConfTempLineProfile 695 xdsl2LConfTempChan1ConfProfile 696 xdsl2LConfTempChan1RaRatioDs 697 xdsl2LConfTempChan1RaRatioUs 698 xdsl2LConfTempChan2ConfProfile 699 xdsl2LConfTempChan2RaRatioDs 700 xdsl2LConfTempChan2RaRatioUs 701 xdsl2LConfTempChan3ConfProfile 702 xdsl2LConfTempChan3RaRatioDs 703 xdsl2LConfTempChan3RaRatioUs 704 xdsl2LConfTempChan4ConfProfile 705 xdsl2LConfTempChan4RaRatioDs 706 xdsl2LConfTempChan4RaRatioUs 707 xdsl2LConfTempRowStatus 708 xdsl2LConfProfProfileName 709 xdsl2LConfProfScMaskDs 710 xdsl2LConfProfScMaskUs 711 xdsl2LConfProfRfiBandsDs 712 xdsl2LConfProfRaModeDs 713 xdsl2LConfProfRaModeUs 714 xdsl2LConfProfRaUsNrmDs 715 xdsl2LConfProfRaUsNrmUs 716 xdsl2LConfProfRaUsTimeDs 717 xdsl2LConfProfRaUsTimeUs 718 xdsl2LConfProfRaDsNrmsDs 719 xdsl2LConfProfRaDsNrmsUs 720 xdsl2LConfProfRaDsTimeDs 721 xdsl2LConfProfRaDsTimeUs 722 xdsl2LConfProfTargetSnrmDs 723 xdsl2LConfProfTargetSnrmUs 724 xdsl2LConfProfMaxSnrmDs 725 xdsl2LConfProfMaxSnrmUs 726 xdsl2LConfProfMinSnrmDs 727 xdsl2LConfProfMinSnrmUs 728 xdsl2LConfProfMsgMinUs 729 xdsl2LConfProfMsgMinDs 730 xdsl2LConfProfXtuTransSysEna 731 xdsl2LConfProfPmMode 732 xdsl2LConfProfL0Time 733 xdsl2LConfProfL2Time 734 xdsl2LConfProfL2Atpr 735 xdsl2LConfProfL2Atprt 736 xdsl2LconfProfRowStatus 737 xdsl2LconfProfAdslMode 738 xdsl2LConfProfMaxNomPsdDs 739 xdsl2LConfProfMaxNomPsdUs 740 xdsl2LConfProfMaxNomAtpDs 741 xdsl2LConfProfMaxNomAtpUs 742 xdsl2LConfProfMaxAggRxPwrUs 743 xdsl2LConfProfPsdMaskDs 744 xdsl2LConfProfPsdMaskUs 745 xdsl2LConfProfPsdMaskSelectUs 746 xdsl2LConfProfModeSpecRowStatus 747 xdsl2ChConfProfProfileName 748 xdsl2ChConfProfMinDataRateDs 749 xdsl2ChConfProfMinDataRateUs 750 xdsl2ChConfProfMinResDataRateDs 751 xdsl2ChConfProfMinResDataRateUs 752 xdsl2ChConfProfMaxDataRateDs 753 xdsl2ChConfProfMaxDataRateUs 754 xdsl2ChConfProfMinDataRateLowPwrDs 755 xdsl2ChConfProfMaxDelayDs 756 xdsl2ChConfProfMaxDelayUs 757 xdsl2ChConfProfMinProtectionDs 758 xdsl2ChConfProfMinProtectionUs 759 xdsl2ChConfProfMaxBerDs 760 xdsl2ChConfProfMaxBerUs 761 xdsl2ChConfProfUsDataRateDs 762 xdsl2ChConfProfDsDataRateDs 763 xdsl2ChConfProfUsDataRateUs 764 xdsl2ChConfProfDsDataRateUs 765 xdsl2ChConfProfImaEnabled 766 xdsl2ChConfProfRowStatus 767 xdsl2LAlarmConfTempTemplateName 768 xdsl2LAlarmConfTempLineProfile 769 xdsl2LAlarmConfTempChan1ConfProfile 770 xdsl2LAlarmConfTempChan2ConfProfile 771 xdsl2LAlarmConfTempChan3ConfProfile 772 xdsl2LAlarmConfTempChan4ConfProfile 773 xdsl2LAlarmConfTempRowStatus 774 xdsl2LineAlarmConfProfileName 775 xdsl2LineAlarmConfProfileXtucThresh15MinFecs 776 xdsl2LineAlarmConfProfileXtucThresh15MinEs 777 xdsl2LineAlarmConfProfileXtucThresh15MinSes 778 xdsl2LineAlarmConfProfileXtucThresh15MinLoss 779 xdsl2LineAlarmConfProfileXtucThresh15MinUas 780 xdsl2LineAlarmConfProfileXturThresh15MinFecs 781 xdsl2LineAlarmConfProfileXturThresh15MinEs 782 xdsl2LineAlarmConfProfileXturThresh15MinSes 783 xdsl2LineAlarmConfProfileXturThresh15MinLoss 784 xdsl2LineAlarmConfProfileXturThresh15MinUas 785 xdsl2LineAlarmConfProfileThresh15MinFailedFullInt 786 xdsl2LineAlarmConfProfileThresh15MinFailedShrtInt 787 xdsl2LineAlarmConfProfileRowStatus 788 xdsl2ChAlarmConfProfileName 789 xdsl2ChAlarmConfProfileXtucThresh15MinCodingViolations 790 xdsl2ChAlarmConfProfileXtucThresh15MinCorrected 791 xdsl2ChAlarmConfProfileXturThresh15MinCodingViolations 792 xdsl2ChAlarmConfProfileXturThresh15MinCorrected 793 xdsl2ChAlarmConfProfileRowStatus 795 Note also that the interface indices in this MIB are maintained 796 persistently. View-based Access Control Model (VACM) data relating 797 to these SHOULD be stored persistently as well [RFC3410]. 799 2.6. Line Topology 801 A VDSL2/ADSL/ADSL2 and ADSL2+ Line consists of two units: atuc or 802 vtuc (a central office termination unit) and atur or vtur (a remote 803 termination unit). There are up to 4 channels (maximum number of 804 channels depends on the specific DSL technology), each carrying an 805 independent information flow, as shown in the figure below. 807 <-- Network Side Customer Side --> 809 || 811 +-------+ +-------+ 812 + |<---------------------1------------------->| + 813 + atuc |<---------------------2------------------->| atur + 814 | or <~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~>| or | 815 + vtuc |<---------------------3------------------->| vtuc + 816 + |<---------------------4------------------->| + 817 +-------+ +-------+ 819 Key: VDSL2/ADSL/ADSL2/ADSL2+ Span 820 <~~~~> VDSL2/ADSL/ADSL2/ADSL2+ twisted-pair 821 -1- Channel #1 carried over the line 822 -2- Optional channel #2 carried over the line 823 -3- Optional channel #3 carried over the line 824 -4- Optional channel #4 carried over the line 826 Figure 2: General topology for a VDSL2/ADSL/ADSL2/ADSL2+ Line 828 2.7. Counters, Interval Buckets, and Thresholds 830 2.7.1. Counters Managed 832 There are various types of counters specified in this MIB. Each 833 counter refers either to the whole VDSL2/ADSL/ADSL2/ADSL2+ line, to 834 one of the xtu entities, or to one of the bearer channels. 836 o On the whole line level 838 For full initializations, failed full initializations, short 839 initializations, and for failed short initializations there are event 840 counters, current 15-minute and 0 to 96 15-minute history bucket(s) 841 of "interval-counters", as well as current and 0 to 30 previous 1-day 842 interval-counter(s). Each current 15-minute "failed" event bucket 843 has an associated threshold notification. 845 o On the xtu level 847 For the LOS Seconds, ES, SES, FEC seconds, and UAS, there are event 848 counters, current 15-minute and 0 to 96 15-minute history bucket(s) 849 of "interval-counters", as well as current and 0 to 30 previous 1-day 850 interval-counter(s). Each current 15-minute event bucket has an 851 associated threshold notification. 853 o On the bearer channel level 855 For the coding violations (CRC anomalies) and corrected blocks (i.e., 856 FEC events) there are event counters, current 15-minute and 0 to 96 857 15-minute history bucket(s) of "interval-counters", as well as 858 current and 0 to 30 previous 1-day interval-counter(s). Each current 859 15-minute event bucket has an associated threshold notification. 861 2.7.2. Minimum Number Of Buckets 863 Although it is possible to support up to 96 15-minute history buckets 864 of "interval-counters", systems implementing this MIB module SHOULD 865 practically support at least 16 buckets, as specified in ITU-T 866 G.997.1, paragraph 7.2.7.2. 868 Similarly, it is possible to support up to 30 previous 1-day 869 "interval-counters", but systems implementing this MIB module SHOULD 870 support at least 1 previous day buckets. 872 2.7.3. Interval Buckets Initialization 874 There is no requirement for an agent to ensure a fixed relationship 875 between the start of a 15-minute interval and any wall clock; 876 however, some implementations may align the 15-minute intervals with 877 quarter hours. Likewise, an implementation may choose to align one 878 day intervals with the start of a day. 880 Counters are not reset when an xtU is reinitialized, only when the 881 agent is reset or reinitialized (or under specific request outside 882 the scope of this MIB module). 884 2.7.4. Interval Buckets Validity 886 As in RFC 3593 [RFC3593] and RFC 2662 [RFC2662], in case the data for 887 an interval is suspect or known to be invalid, the agent MUST report 888 the interval as invalid. If the current 15-minute event bucket is 889 determined to be invalid, the element management system SHOULD ignore 890 its content and the agent MUST NOT generate notifications based upon 891 the value of the event bucket. 893 A valid 15-minute event bucket SHOULD usually count the events for 894 exactly 15 minutes. Similarly, a valid 1-day event bucket SHOULD 895 usually count the events for exactly 24 hours. However, the 896 following scenarios are exceptional: 898 1) For implementations that align the 15-minute intervals with 899 quarter hours, and the 1-day intervals with start of a day, the 900 management system may still start the PM process not aligned with 901 the wall clock. Such a management system may wish to retrieve 902 even partial information for the first event buckets, rather than 903 declaring them all as invalid. 904 2) For an event bucket that suffered relatively short outages, the 905 management system may wish to retrieve the available PM outcomes, 906 rather than declaring the whole event bucket as invalid. This is 907 more important for 1-day event buckets. 908 3) An event bucket may be shorter or longer than the formal duration 909 if a clock adjustment was performed during the interval. 911 This MIB allows supporting the exceptional scenarios described above 912 by reporting the actual Monitoring Time of a monitoring interval. 913 This parameter is relevant only for Valid intervals, but is useful 914 for these exceptional scenarios: 915 a) The management system MAY still declare a partial PM interval as 916 Valid and report the actual number of seconds the interval lasted. 917 b) If the interval was shortened or extended due to clock 918 corrections, the management system SHOULD report the actual number 919 of seconds the interval lasted, beside reporting that the interval 920 is Valid. 922 2.8. Profiles 924 As a managed node can handle a large number of xtUs, (e.g., hundreds 925 or perhaps thousands of lines), provisioning every parameter on every 926 xtU may become burdensome. Moreover, most lines are provisioned 927 identically with the same set of parameters. To simplify the 928 provisioning process, this MIB module makes use of profiles and 929 templates. 931 A configuration profile is a set of parameters that can be shared by 932 multiple entities. There are configuration profiles to address the 933 line level provisioning and another type of profile that addresses 934 the channel level provisioning parameters. 936 A configuration template is actually a profile-of-profiles. That is, 937 a template is comprised of one line configuration profile and one or 938 more channel configuration profiles. A template provides the 939 complete configuration of a line. The same configuration can be 940 shared by multiple lines. 942 Similarly to the configuration profiles and templates, this MIB 943 module makes use of templates and profiles for specifying the alarm 944 thresholds associated with performance parameters. This allows 945 provisioning multiple lines with the same criteria for generating 946 threshold crossing notifications. 948 The following paragraphs describe templates and profiles used in this 949 MIB module 951 2.8.1. Configuration Profiles And Templates 953 o Line Configuration Profiles - Line configuration profiles contain 954 parameters for configuring the low layer of VDLS2/ADSL/ADSL2 and 955 ADSL2+ lines. They are defined in the xdsl2LineConfProfTable. 957 The line configuration includes issues such as the specific VDSL2/ 958 ADSL/ADSL2 or ADSL2+ modes to enable on the respective line, power 959 spectrum parameters, rate adaptation criteria, and SNR margin 960 related parameters. A subset of the line configuration parameters 961 depends upon the specific ADSL Mode allowed (i.e., Does the 962 profile allow VDSL2, ADSL, ADSL2 and/or ADSL2+?) as well as what 963 annex/annexes of the standard are allowed. This is the reason a 964 line profile MUST include one or more mode-specific extensions. 966 o Channel Configuration Profiles - Channel configuration profiles 967 contain parameters for configuring bearer channels over the VDSL2/ 968 ADSL/ADSL2 and ADSL2+ lines. They are sometimes considered as the 969 service layer configuration of the VDSL2/ADSL/ADSL2 and ADSL2+ 970 lines. They are defined in the xdsl2ChConfProfTable. 972 The channel configuration includes issues such as the desired 973 minimum and maximum rate on each traffic flow direction and 974 impulse noise protection parameters. 976 o Line Configuration Templates - Line configuration templates allow 977 combining line configuration profiles and channel configuration 978 profiles to a comprehensive configuration of the VDSL2/ADSL/ADSL2 979 and ADSL2+ line. They are defined in the 980 xdsl2LineConfTemplateTable. 982 The line configuration template includes one index (OID) of a line 983 configuration profile and one to four indexes of channel 984 configuration profiles. The template also addresses the issue of 985 distributing the excess available data rate on each traffic flow 986 direction (i.e., the data rate left after each channel is 987 allocated a data rate to satisfy its minimum requested data rate) 988 among the various channels. 990 2.8.2. Alarm Configuration Profiles And Templates 991 o Line Alarm Configuration Profiles - Line level Alarm configuration 992 profiles contain the threshold values for Performance Monitoring 993 (PM) parameters, counted either on the whole line level or on an 994 xtu level. Thresholds are required only for failures and 995 anomalies. E.g., there are thresholds for failed initializations 996 and LOS seconds, but not for the aggregate number of full 997 initializations. These profiles are defined in the 998 adsl2LineAlarmConfProfTable. 1000 o Channel Alarm Configuration Profiles - Channel level Alarm 1001 configuration profiles contain the threshold values for PM 1002 parameters counted on a bearer channel level. Thresholds are 1003 defined for two types of anomalies: corrected blocks and coding 1004 violations. These profiles are defined in the 1005 xdsl2ChAlarmConfProfTable. 1007 o Line Alarm Configuration Templates - Line Alarm configuration 1008 templates allow combining line level alarm configuration profiles 1009 and channel level alarm configuration profiles to a comprehensive 1010 configuration of the PM thresholds for VDSL2/ADSL/ADSL2 and ADSL2+ 1011 line. They are defined in the xdsl2LineAlarmConfTemplateTable. 1013 The line alarm configuration template includes one index (OID) of 1014 a line level alarm configuration profile and one to four indexes 1015 of channel level alarm configuration profiles. 1017 2.8.3. Managing Profiles And Templates 1019 The index value for each profile and template is a locally-unique, 1020 administratively assigned name having the textual convention 1021 'SnmpAdminString' (RFC 3411 [RFC3411]). 1023 One or more lines may be configured to share parameters of a single 1024 configuration template (e.g., xdsl2LConfTempTemplateName = 'silver') 1025 by setting its xdsl2LCnfgLineTemplate objects to the value of this 1026 template. 1028 One or more lines may be configured to share parameters of a single 1029 Alarm configuration template (e.g., xdsl2LAlarmConfTempTemplateName = 1030 'silver') by setting its xdsl2LCnfgAlarmTemplate objects to the value 1031 of this template. 1033 Before a template can be deleted or taken out of service it MUST be 1034 first unreferenced from all associated lines. Implementations MAY 1035 also reject template modification while it is associated with any 1036 line. Implementations MUST reject template modification while its 1037 row status is set to 'active'. 1039 Before a profile can be deleted or taken out of service it MUST be 1040 first unreferenced from all associated templates. Implementations 1041 MAY also reject profile modification while it is referenced by any 1042 template. Implementations MUST reject profile modification while its 1043 row status is set to 'active'. 1045 Implementations MUST provide a default profile whose name is 'DEFVAL' 1046 for each profile and template type. The values of the associated 1047 parameters will be vendor-specific unless otherwise indicated in this 1048 document. Before a line's templates have been set, these templates 1049 will be automatically used by setting xdsl2LCnfgLineTemplate and 1050 xdsl2LCnfgAlarmTemplate to 'DEFVAL' where appropriate. This default 1051 profile name, 'DEFVAL', is considered reserved in the context of 1052 profiles and templates defined in this MIB module. 1054 Profiles and templates are created, assigned, and deleted dynamically 1055 using the profile name and profile row status in each of the profile 1056 tables. 1058 If the implementation allows modifying a profile or template while it 1059 is associated with a line, then such changes MUST take effect 1060 immediately. These changes MAY result in a restart (hard reset or 1061 soft restart) of the units on the line. 1063 2.8.4. Managing Multiple Bearer Channels 1065 The number of bearer channels is configured by setting the template 1066 attributes xdsl2LConfTempChan1ConfProfile, 1067 xdsl2LConfTempChan2ConfProfile, xdsl2LConfTempChan3ConfProfile, and 1068 xdsl2LConfTempChan4ConfProfile and then assigning that template to a 1069 DSL line using the xdsl2LineCnfgTemplate attribute. When the number 1070 of bearer channels for a DSL line changes, the SNMP agent will 1071 automatically create or destroy rows in channel-related tables 1072 associated with that line. For example, when a DSL line is operating 1073 with one bearer channel, there will be zero rows in channel-related 1074 tables for channels two, three, and four. The SNMP agent MUST create 1075 and destroy channel related rows as follows : 1077 o When the number of bearer channels for a DSL line changes to a 1078 higher number, the SNMP agent will automatically create rows in 1079 the xdsl2ChannelStatusTable, and xdsl2PMChCurrTable tables for 1080 that line. 1081 o When the number of bearer channels for a DSL line changes to a 1082 lower number, the SNMP agent will automatically destroy rows in 1083 the xdsl2ChannelStatusTable, 1084 xdsl2PMChCurrTable,xdsl2PMChHist15MinTable and 1085 xdsl2PMChHist1DTable tables for that line. 1087 2.9. Notifications 1089 The ability to generate the SNMP notifications coldStart/WarmStart 1090 (per [RFC3418]), which are per agent (e.g., per Digital Subscriber 1091 Line Access Multiplexer, or DSLAM, in such a device), and linkUp/ 1092 linkDown (per [RFC2863]), which are per interface (i.e., VDSL2/ADSL/ 1093 ADSL2 or ADSL2+ line) is required. 1095 A linkDown notification MAY be generated whenever any of ES, SES, CRC 1096 Anomaly, LOS, LOF, or UAS event occurs. The corresponding linkUp 1097 notification MAY be sent when all link failure conditions are 1098 cleared. 1100 The notifications defined in this MIB module are for status change 1101 (e.g., initialization failure) and for the threshold crossings 1102 associated with the following events: Full initialization failures, 1103 short initialization failures, ES, SES, FEC Seconds, LOS Seconds, 1104 UAS, FEC Seconds, FEC events, and CRC anomalies. Each threshold has 1105 its own enable/threshold value. When that value is 0, the 1106 notification is disabled. 1108 The xdsl2LStatusStatusAtur and adsl2LStatusStatusAtuc are bitmasks 1109 representing all outstanding error conditions associated with the 1110 AtuR and xtuc (respectively). Note that since the xtur status is 1111 obtained via the EOC, this information may be unavailable in case the 1112 xtur is unreachable via EOC during a line error condition. 1113 Therefore, not all conditions may always be included in its current 1114 status. Notifications corresponding to the bit fields in those two 1115 status objects are defined. 1117 Note that there are other status parameters that refer to the AtuR 1118 (e.g., downstream line attenuation). Those parameters also depend on 1119 the availability of EOC between the central office xtu and the remote 1120 xtu. 1122 A threshold notification occurs whenever the corresponding current 1123 15-minute interval error counter becomes equal to, or exceeds the 1124 threshold value. Only one notification SHOULD be sent per interval 1125 per interface. Since the current 15-minute counter is reset to 0 1126 every 15 minutes, and if the condition persists, the notification may 1127 recur as often as every 15 minutes. For example, to get a 1128 notification whenever a "loss of" event occurs (but at most once 1129 every 15 minutes), set the corresponding threshold to 1. The agent 1130 will generate a notification when the event originally occurs. 1132 Notifications, other than the threshold notifications listed above, 1133 SHOULD be rate limited (throttled) such that there is an 1134 implementation-specific gap between the generation of consecutive 1135 notifications of the same event. When notifications are rate 1136 limited, they are dropped and not queued for sending at a future 1137 time. This is intended to be a general rate-limiting statement for 1138 notifications that otherwise have no explicit rate limiting 1139 assertions in this document. 1141 Note that the Network Management System, or NMS, may receive a 1142 linkDown notification, as well, if enabled (via 1143 ifLinkUpDownTrapEnable [RFC2863]). At the beginning of the next 15 1144 minute interval, the counter is reset. When the first second goes by 1145 and the event occurs, the current interval bucket will be 1, which 1146 equals the threshold, and the notification will be sent again. 1148 3. Definitions 1150 VDSL2-LINE-TC-MIB DEFINITIONS ::= BEGIN 1152 IMPORTS 1153 MODULE-IDENTITY, 1154 transmission 1155 FROM SNMPv2-SMI 1157 TEXTUAL-CONVENTION 1158 FROM SNMPv2-TC; 1160 vdsl2TCMIB MODULE-IDENTITY 1161 LAST-UPDATED "200601220000Z" -- January 22, 2006 1162 ORGANIZATION "ADSLMIB Working Group" 1163 CONTACT-INFO "WG-email: adslmib@ietf.org 1164 Info: https://www1.ietf.org/mailman/listinfo/adslmib 1166 Chair: Mike Sneed 1167 Sand Channel Systems 1168 Postal: P.O. Box 37324 1169 Raleigh NC 27627-732 1170 Email: sneedmike@hotmail.com 1171 Phone: +1 206 600 7022 1173 Co-Chair: Menachem Dodge 1174 ECI Telecom Ltd. 1175 Postal: 30 Hasivim St. 1176 Petach Tikva 49517, 1177 Israel. 1179 Email: mbdodge@ieee.org 1180 Phone: +972 3 926 8421 1182 Co-editor: Moti Morgenstern 1183 ECI Telecom Ltd. 1184 Postal: 30 Hasivim St. 1185 Petach Tikva 49517, 1186 Israel. 1187 Email: moti.morgenstern@ecitele.com 1188 Phone: +972 3 926 6258 1190 Co-editor: Scott Baillie 1191 NEC Australia 1192 Postal: 649-655 Springvale Road, 1193 Mulgrave, Victoria 3170, 1194 Australia. 1195 Email: scott.baillie@nec.com.au 1196 Phone: +61 3 9264 3986 1198 Co-editor: Umberto Bonollo 1199 NEC Australia 1200 Postal: 649-655 Springvale Road, 1201 Mulgrave, Victoria 3170, 1202 Australia. 1203 Email: umberto.bonollo@nec.com.au 1204 Phone: +61 3 9264 3385 1205 " 1206 DESCRIPTION 1207 "This MIB Module provides Textual Conventions to be 1208 used by the VDSL2-LINE-MIB module for the purpose of 1209 managing VDSL2, ADSL, ADSL2 and ADSL2+ lines. 1211 Copyright (C) The Internet Society (2006). This version of 1212 this MIB module is part of RFC XXXX: see the RFC itself for 1213 full legal notices." 1215 -- RFC Ed.: replace XXXX with assigned number & remove this note 1216 REVISION "200601220000Z" -- January 22, 2006 1217 DESCRIPTION "Initial version, published as RFC XXXX." 1218 -- RFC Ed.: replace XX with assigned number & remove this note 1219 ::= { transmission xxx 2} -- vdsl2MIB 2 1220 -- IANA, the xxx here must be the same as the one assigned 1221 -- to the vdsl2MIB below. 1222 -- RFC Ed.: Please fill in xxx once assigned by IANA. 1224 ------------------------------------------------ 1225 -- Textual Conventions -- 1226 ------------------------------------------------ 1227 Xdsl2Unit ::= TEXTUAL-CONVENTION 1228 STATUS current 1229 DESCRIPTION 1230 "Identifies a transceiver as being either xtuc or 1231 xtur. 1232 A VDSL2/ADSL/ADSL2 or ADSL2+ line consists of two 1233 transceivers, an xtuc and an xtur. 1234 In the case of ADSL/ADSL2 and ADSL2+ those two 1235 transceivers are also called atuc and atur. 1236 In the case of VDSL2 those two transceivers are 1237 also called vtuc and vtur. 1238 Attributes with this syntax reference the two 1239 sides of a line. Specified as an INTEGER, the two values 1240 are: 1241 xtuc(1) -- central office transceiver 1242 xtur(2) -- remote site transceiver" 1243 SYNTAX INTEGER { 1244 xtuc(1), 1245 xtur(2) 1246 } 1248 Xdsl2Direction ::= TEXTUAL-CONVENTION 1249 STATUS current 1250 DESCRIPTION 1251 "Identifies the direction of a band as being 1252 either upstream or downstream. Specified as an INTEGER, 1253 the two values are: 1254 upstream(1) 1255 downstream(2)" 1256 SYNTAX INTEGER { 1257 upstream(1), 1258 downstream(2) 1259 } 1261 ------***************************************************** 1262 ----- The following TC doesn't include yet the VDSL2 bits 1263 ------***************************************************** 1264 Xdsl2TransmissionModeType ::= TEXTUAL-CONVENTION 1265 STATUS current 1266 DESCRIPTION 1267 "A set of ADSL2 line transmission modes, with one bit 1268 per mode. The notes (F) and (L) denote Full-Rate 1269 and Lite/splitterless respectively: 1270 Bit 00 : Regional Std. (ANSI T1.413) (F) 1271 Bit 01 : Regional Std. (ETSI DTS/TM06006) (F) 1272 Bit 02 : G.992.1 POTS non-overlapped (F) 1273 Bit 03 : G.992.1 POTS overlapped (F) 1274 Bit 04 : G.992.1 ISDN non-overlapped (F) 1275 Bit 05 : G.992.1 ISDN overlapped (F) 1276 Bit 06 : G.992.1 TCM-ISDN non-overlapped (F) 1277 Bit 07 : G.992.1 TCM-ISDN overlapped (F) 1278 Bit 08 : G.992.2 POTS non-overlapped (L) 1279 Bit 09 : G.992.2 POTS overlapped (L) 1280 Bit 10 : G.992.2 with TCM-ISDN non-overlapped (L) 1281 Bit 11 : G.992.2 with TCM-ISDN overlapped (L) 1282 Bit 12 : G.992.1 TCM-ISDN symmetric (F) --- not in G.997.1 1283 Bit 13-17: Reserved 1284 Bit 18 : G.992.3 POTS non-overlapped (F) 1285 Bit 19 : G.992.3 POTS overlapped (F) 1286 Bit 20 : G.992.3 ISDN non-overlapped (F) 1287 Bit 21 : G.992.3 ISDN overlapped (F) 1288 Bit 22-23: Reserved 1289 Bit 24 : G.992.4 POTS non-overlapped (L) 1290 Bit 25 : G.992.4 POTS overlapped (L) 1291 Bit 26-27: Reserved 1292 Bit 28 : G.992.3 Annex I All-Digital non-overlapped (F) 1293 Bit 29 : G.992.3 Annex I All-Digital overlapped (F) 1294 Bit 30 : G.992.3 Annex J All-Digital non-overlapped (F) 1295 Bit 31 : G.992.3 Annex J All-Digital overlapped (F) 1296 Bit 32 : G.992.4 Annex I All-Digital non-overlapped (L) 1297 Bit 33 : G.992.4 Annex I All-Digital overlapped (L) 1298 Bit 34 : G.992.3 Annex L POTS non-overlapped, mode 1, 1299 wide U/S (F) 1300 Bit 35 : G.992.3 Annex L POTS non-overlapped, mode 2, 1301 narrow U/S(F) 1302 Bit 36 : G.992.3 Annex L POTS overlapped, mode 3, 1303 wide U/S (F) 1304 Bit 37 : G.992.3 Annex L POTS overlapped, mode 4, 1305 narrow U/S (F) 1306 Bit 38 : G.992.3 Annex M POTS non-overlapped (F) 1307 Bit 39 : G.992.3 Annex M POTS overlapped (F) 1308 Bit 40 : G.992.5 POTS non-overlapped (F) 1309 Bit 41 : G.992.5 POTS overlapped (F) 1310 Bit 42 : G.992.5 ISDN non-overlapped (F) 1311 Bit 43 : G.992.5 ISDN overlapped (F) 1312 Bit 44-45: Reserved 1313 Bit 46 : G.992.5 Annex I All-Digital non-overlapped (F) 1314 Bit 47 : G.992.5 Annex I All-Digital overlapped (F) 1315 Bit 48 : G.992.5 Annex J All-Digital non-overlapped (F) 1316 Bit 49 : G.992.5 Annex J All-Digital overlapped (F) 1317 Bit 50 : G.992.5 Annex M POTS non-overlapped (F) 1318 Bit 51 : G.992.5 Annex M POTS overlapped (F) 1319 Bit 52-55: Reserved" 1320 SYNTAX BITS { 1321 ansit1413(0), 1322 etsi(1), 1323 q9921PotsNonOverlapped(2), 1324 q9921PotsOverlapped(3), 1325 q9921IsdnNonOverlapped(4), 1326 q9921isdnOverlapped(5), 1327 q9921tcmIsdnNonOverlapped(6), 1328 q9921tcmIsdnOverlapped(7), 1329 q9922potsNonOverlapeed(8), 1330 q9922potsOverlapped(9), 1331 q9922tcmIsdnNonOverlapped(10), 1332 q9922tcmIsdnOverlapped(11), 1333 q9921tcmIsdnSymmetric(12), 1334 reserved1(13), 1335 reserved2(14), 1336 reserved3(15), 1337 reserved4(16), 1338 reserved5(17), 1339 q9923PotsNonOverlapped(18), 1340 q9923PotsOverlapped(19), 1341 q9923IsdnNonOverlapped(20), 1342 q9923isdnOverlapped(21), 1343 reserved6(22), 1344 reserved7(23), 1345 q9924potsNonOverlapeed(24), 1346 q9924potsOverlapped(25), 1347 reserved8(26), 1348 reserved9(27), 1349 q9923AnnexIAllDigNonOverlapped(28), 1350 q9923AnnexIAllDigOverlapped(29), 1351 q9923AnnexJAllDigNonOverlapped(30), 1352 q9923AnnexJAllDigOverlapped(31), 1353 q9924AnnexIAllDigNonOverlapped(32), 1354 q9924AnnexIAllDigOverlapped(33), 1355 q9923AnnexLMode1NonOverlapped(34), 1356 q9923AnnexLMode2NonOverlapped(35), 1357 q9923AnnexLMode3Overlapped(36), 1358 q9923AnnexLMode4Overlapped(37), 1359 q9923AnnexMPotsNonOverlapped(38), 1360 q9923AnnexMPotsOverlapped(39), 1361 q9925PotsNonOverlapped(40), 1362 q9925PotsOverlapped(41), 1363 q9925IsdnNonOverlapped(42), 1364 q9925isdnOverlapped(43), 1365 reserved10(44), 1366 reserved11(45), 1367 q9925AnnexIAllDigNonOverlapped(46), 1368 q9925AnnexIAllDigOverlapped(47), 1369 q9925AnnexJAllDigNonOverlapped(48), 1370 q9925AnnexJAllDigOverlapped(49), 1371 q9925AnnexMPotsNonOverlapped(50), 1372 q9925AnnexMPotsOverlapped(51), 1373 reserved12(52), 1374 reserved13(53), 1375 reserved14(54), 1376 reserved15(55) 1377 } 1379 Xdsl2RaMode ::= TEXTUAL-CONVENTION 1380 STATUS current 1381 DESCRIPTION 1382 "Specifies the rate adaptation behavior for the line. 1383 The three possible behaviors are: 1384 manual (1) - No Rate-Adaptation. The initialization 1385 process attempts to synchronize to a 1386 specified rate. 1387 rainit (2) - Rate-Adaptation during initialization process 1388 only, which attempts to synchronize to a rate 1389 between minimum and maximum specified values. 1390 dynamicRa (3)- Dynamic Rate-Adaptation during initialization 1391 process as well as during SHOWTIME" 1392 SYNTAX INTEGER { 1393 manual(1), 1394 raInit(2), 1395 dynamicRa(3) 1396 } 1398 Xdsl2InitResult ::= TEXTUAL-CONVENTION 1399 STATUS current 1400 DESCRIPTION 1401 "Specifies the result of full initialization attempt; the 1402 six possible result values are: 1403 noFail (0) - Successful initialization 1404 configError (1) - Configuration failure 1405 configNotFeasible (2) - Configuration details not supported 1406 commFail (3) - Communication failure 1407 noPeerAtu (4) - Peer ATU not detected 1408 otherCause (5) - Other initialization failure reason" 1409 SYNTAX INTEGER { 1410 noFail(0), 1411 configError(1), 1412 configNotFeasible(2), 1413 commFail(3), 1414 noPeerAtu(4), 1415 otherCause(5) 1416 } 1418 ------***************************************************** 1419 ----- The following TC is subject to thorough changes 1420 ------***************************************************** 1421 Xdsl2OperationModes ::= TEXTUAL-CONVENTION 1422 STATUS current 1423 DESCRIPTION 1424 "The VDSL2 management model specified includes an xDSL Mode 1425 attribute which identifies an instance of xDSL Mode-Specific 1426 PSD Configuration object in the xDSL Line Profile. The 1427 following classes of xDSL operating mode are defined. " 1428 SYNTAX INTEGER { 1429 defMode (1), 1430 adsl (2), 1431 adsl2Pots (3), 1432 adsl2Isdn (4), 1433 adsl2PlusPots (5), 1434 adsl2PlusIsdn (6), 1435 adsl2ReachExtended (7) 1436 } 1438 Xdsl2PowerMngState ::= TEXTUAL-CONVENTION 1439 STATUS current 1440 DESCRIPTION 1441 "Attributes with this syntax uniquely identify each power 1442 management state defined for the VDSL2/ADSL/ADSL2 or ADSL2+ 1443 link. 1444 In VDSL2 only L0 and L3 states are defined. 1445 The possible values are: 1446 l0(1) - L0 - Full power management state 1447 l1(2) - L1 - Low power management state (for G.992.2) 1448 l2(3) - L2 - Low power management state (for G.992.3, 1449 G.992.4, and G.992.5) 1450 l3(4) - L3 - Idle power management state" 1452 SYNTAX INTEGER { 1453 l0(1), 1454 l1(2), 1455 l2(3), 1456 l3(4) 1457 } 1459 Xdsl2ConfPmsForce ::= TEXTUAL-CONVENTION 1460 STATUS current 1461 DESCRIPTION 1462 "Attributes with this syntax are configuration parameters 1463 that reference the desired power management state for the 1464 VDSL2/ADSL/ADSL2 or ADSL2+ link 1465 In VDSL2 only L0 and L3 states are defined: 1467 l3toL0 (0) - Perform a transition from L3 to L0 1468 (Full power management state) 1469 l0toL2 (2) - Perform a transition from L0 to L2 1470 (Low power management state) 1471 l0orL2toL3 (3) - Perform a transition into L3 (Idle 1472 power management state)" 1474 SYNTAX INTEGER { 1475 l3toL0 (0), 1476 l0toL2 (2), 1477 l0orL2toL3 (3) 1478 } 1480 Xdsl2LConfProfPmMode ::= TEXTUAL-CONVENTION 1481 STATUS current 1482 DESCRIPTION 1483 "Attributes with this syntax are configuration parameters 1484 that reference the power modes/states into which the xTU-C or 1485 xTU-R may autonomously transit. 1487 It is a BITS structure that allows control of the following 1488 transit options: 1489 allowTransitionsToIdle (0) - xTU may autonomously transit 1490 to idle (L3) state. 1491 allowTransitionsToLowPower (1)- xTU may autonomously transit 1492 to low-power (L2) state." 1494 SYNTAX BITS { 1495 allowTransitionsToIdle(0), 1496 allowTransitionsToLowPower(1) 1497 } 1499 Xdsl2LineLdsf ::= TEXTUAL-CONVENTION 1500 STATUS current 1501 DESCRIPTION 1502 "Attributes with this syntax are configuration parameters 1503 that control the Loop Diagnostic mode for a VDSL2/ADSL/ADSL2 1504 or ADSL2+ link. The possible values are: 1505 inhibit (0) - Inhibit Loop Diagnostic mode 1506 force (1) - Force/Initiate Loop Diagnostic mode" 1508 SYNTAX INTEGER { 1509 inhibit(0), 1510 force(1) 1511 } 1513 Xdsl2LdsfResult ::= TEXTUAL-CONVENTION 1514 STATUS current 1515 DESCRIPTION 1516 "Possible failure reasons associated with performing 1517 Dual Ended Loop Test (DELT) on a DSL line. 1518 Possible values are: 1519 none (1) - The default value in case LDSF was never 1520 requested for the associated line. 1521 success (2) - The recent command completed 1522 successfully. 1523 inProgress (3) - The Loop Diagnostics process is in 1524 progress. 1525 unsupported (4) - The NE or the line card doesn't support 1526 LDSF. 1527 cannotRun (5) - The NE cannot initiate the command, due 1528 to a non specific reason. 1529 aborted (6) - The Loop Diagnostics process aborted. 1530 failed (7) - The Loop Diagnostics process failed. 1531 illegalMode (8) - The NE cannot initiate the command, due 1532 to the specific mode of the relevant 1533 line. 1534 adminUp (9) - The NE cannot initiate the command, as 1535 the relevant line is administratively 1536 'Up'. 1537 tableFull (10)- The NE cannot initiate the command, due 1538 to reaching the maximum number of rows 1539 in the results table. 1540 noResources (11)- The NE cannot initiate the command, due 1541 to lack of internal memory resources." 1542 SYNTAX INTEGER { 1543 none (1), 1544 success (2), 1545 inProgress (3), 1546 unsupported (4), 1547 cannotRun (5), 1548 aborted (6), 1549 failed (7), 1550 illegalMode (8), 1551 adminUp (9), 1552 tableFull (10), 1553 noResources (11) 1554 } 1556 Xdsl2SymbolProtection ::= TEXTUAL-CONVENTION 1557 STATUS current 1558 DESCRIPTION 1559 "Attributes with this syntax are configuration parameters 1560 that reference the minimum length impulse noise protection 1561 (INP) in terms of number of symbols. The possible values are: 1562 noProtection (i.e., INP not required), halfSymbol (i.e., INP 1563 length is 1/2 symbol), and 1-16 symbols in steps of 1 symbol" 1565 SYNTAX INTEGER { 1566 noProtection (1), 1567 halfSymbol (2), 1568 singleSymbol (3), 1569 twoSymbols (4), 1570 threeSymbols (5), 1571 fourSymbols (6), 1572 fiveSymbols (7), 1573 sixSymbols (8), 1574 sevenSymbols (9), 1575 eightSymbols (10), 1576 nineSymbols (11), 1577 tenSymbols (12), 1578 elevenSymbols (13), 1579 twelveSymbols (14), 1580 thirteeSymbols (15), 1581 fourteenSymbols (16), 1582 fifteenSymbols (17), 1583 sixteenSymbols (18) 1584 } 1585 Xdsl2MaxBer ::= TEXTUAL-CONVENTION 1586 STATUS current 1587 DESCRIPTION 1588 "Attributes with this syntax are configuration parameters 1589 that reference the maximum Bit Error Rate (BER). 1590 The possible values are: 1592 eminus3 (1) - Maximum BER=E^-3 1593 eminus5 (2) - Maximum BER=E^-5 1594 eminus7 (3) - Maximum BER=E^-7" 1595 SYNTAX INTEGER { 1596 eminus3(1), 1597 eminus5(2), 1598 eminus7(3) 1599 } 1601 Xdsl2ScMaskDs ::= TEXTUAL-CONVENTION 1602 STATUS current 1603 DESCRIPTION 1604 "Each one of the 4096 bits in this OCTET 1605 STRING array represents the corresponding bin 1606 in the downstream direction. A value of one 1607 indicates that the bin is not in use." 1608 SYNTAX OCTET STRING (SIZE(0..512)) 1610 Xdsl2ScMaskUs ::= TEXTUAL-CONVENTION 1611 STATUS current 1612 DESCRIPTION 1613 "Each one of the 4096 bits in this OCTET 1614 STRING array represents the corresponding bin 1615 in the upstream direction. A value of one 1616 indicates that the bin is not in use." 1617 SYNTAX OCTET STRING (SIZE(0..512)) 1619 Xdsl2RfiDs ::= TEXTUAL-CONVENTION 1620 STATUS current 1621 DESCRIPTION 1622 "Each one of the 4096 bits in this OCTET 1623 STRING array represents the corresponding bin 1624 in the downstream direction. A value of one 1625 indicates that the bin is part of a notch 1626 filter." 1627 SYNTAX OCTET STRING (SIZE(0..512)) 1629 Xdsl2PsdMaskDs ::= TEXTUAL-CONVENTION 1630 STATUS current 1631 DESCRIPTION 1632 "This is a structure that represents up to 1633 32 PSD Mask breakpoints. 1634 Each breakpoint occupies 3 octets: The first 1635 two octets hold the index of the sub-carrier 1636 associated with the breakpoint. The third octet 1637 holds the PSD reduction at the breakpoint from 0 1638 (0dBm/Hz) to 255 (-127.5 dBm/Hz) using units of 1639 0.5dBm/Hz." 1640 SYNTAX OCTET STRING (SIZE(0..96)) 1642 Xdsl2PsdMaskUs ::= TEXTUAL-CONVENTION 1643 STATUS current 1644 DESCRIPTION 1645 "This is a structure that represents up to 1646 16 PSD Mask breakpoints. 1647 Each breakpoint occupies 3 octets: The first 1648 two octets hold the index of the sub-carrier 1649 associated with the breakpoint. The third octet 1650 holds the PSD reduction at the breakpoint from 0 1651 (0dBm/Hz) to 255 (-127.5 dBm/Hz) using units of 1652 0.5dBm/Hz." 1653 SYNTAX OCTET STRING (SIZE(0..48)) 1655 Xdsl2Tssi ::= TEXTUAL-CONVENTION 1656 STATUS current 1657 DESCRIPTION 1658 "This is a structure that represents up to 1659 32 transmit spectrum shaping (TSSi) breakpoints. 1660 Each breakpoint occupies 3 octets: The first 1661 two octets hold the index of the sub-carrier 1662 associated with the breakpoint. The third octet 1663 holds the shaping parameter at the breakpoint. It 1664 is a value from 0 to 127 (units of -0.5dB). The 1665 special value 127 indicates that the sub-carrier 1666 is not transmitted." 1667 SYNTAX OCTET STRING (SIZE(0..96)) 1669 ------***************************************************** 1670 ----- The following TC we should add VDSL2 related states 1671 ------***************************************************** 1672 Xdsl2LastTransmittedState ::= TEXTUAL-CONVENTION 1673 STATUS current 1674 DESCRIPTION 1675 "This parameter represents the last successful 1676 transmitted initialization state in the last full 1677 initialization performed on the line States are 1678 per the specific xDSL technology and are numbered 1679 from 0 (if G.994.1 is used) or 1 (if G.994.1 is 1680 not used) up to Showtime." 1681 SYNTAX INTEGER { 1682 atucG9941(0), 1683 atucQuiet1(1), 1684 atucComb1(2), 1685 atucQuiet2(3), 1686 atucComb2(4), 1687 atucIcomb1(5), 1688 atucLineprob(6), 1689 atucQuiet3(7), 1690 atucComb3(8), 1691 atucIComb2(9), 1692 atucMsgfmt(10), 1693 atucMsgpcb(11), 1694 atucQuiet4(12), 1695 atucReverb1(13), 1696 atucTref1(14), 1697 atucReverb2(15), 1698 atucEct(16), 1699 atucReverb3(17), 1700 atucTref2(18), 1701 atucReverb4(19), 1702 atucSegue1(20), 1703 atucMsg1(21), 1704 atucReverb5(22), 1705 atucSegue2(23), 1706 atucMedley(24), 1707 atucExchmarker(25), 1708 atucMsg2(26), 1709 atucReverb6(27), 1710 atucSegue3(28), 1711 atucParams(29), 1712 atucReverb7(30), 1713 atucSegue4(31), 1714 atucShowtime(32), 1715 -- 1716 aturG9941(100), 1717 aturQuiet1(101), 1718 aturComb1(102), 1719 aturQuiet2(103), 1720 aturComb2(104), 1721 aturIcomb1(105), 1722 aturLineprob(106), 1723 aturQuiet3(107), 1724 aturComb3(108), 1725 aturIcomb2(109), 1726 aturMsgfmt(110), 1727 aturMsgpcb(111), 1728 aturReverb1(112), 1729 aturQuiet4(113), 1730 aturReverb2(114), 1731 aturQuiet5(115), 1732 aturReverb3(116), 1733 aturEct(117), 1734 aturReverb4(118), 1735 aturSegue1(119), 1736 aturReverb5(120), 1737 aturSegue2(121), 1738 aturMsg1(122), 1739 aturMedley(123), 1740 aturExchmarker(124), 1741 aturMsg2(125), 1742 aturReverb6(126), 1743 aturSegue3(127), 1744 aturParams(128), 1745 aturReverb7(129), 1746 aturSegue4(130), 1747 aturShowtime(131) 1748 } 1750 Xdsl2LineStatus ::= TEXTUAL-CONVENTION 1751 STATUS current 1752 DESCRIPTION 1753 "Attributes with this syntax are status parameters 1754 that reflect the failure status for a given endpoint of 1755 VDSL2/ADSL/ADSL2 or ADSL2+ link. 1757 This BITS structure can report the following failures: 1759 noDefect (0) - This bit position positively reports 1760 that no defect or failure exist. 1761 lossOfFraming (1) - Loss of frame synchronization 1762 lossOfSignal (2) - Loss of signal 1763 lossOfPower (3) - Loss of power. Usually this failure may 1764 be reported for CPE units only 1765 initFailure (4) - Recent initialization process failed. 1766 Never active on xTU-R." 1767 SYNTAX BITS { 1768 noDefect(0), 1769 lossOfFraming(1), 1770 lossOfSignal(2), 1771 lossOfPower(3), 1772 initFailure(4) 1773 } 1775 Xdsl2ChAtmStatus ::= TEXTUAL-CONVENTION 1776 STATUS current 1777 DESCRIPTION 1778 "Attributes with this syntax are status parameters that 1779 reflect the failure status for Transmission Convergence (TC) 1780 layer of a given ATM interface (data path over a VDSL2/ADSL/ 1781 ADSL2 or ADSL2+ link). 1783 This BITS structure can report the following failures: 1784 noDefect (0) - This bit position positively 1785 reports that no defect or failure 1786 exist. 1787 noCellDelineation (1) - The link was successfully 1789 initialized but cell delineation 1791 was never acquired on the 1793 associated ATM data path. 1794 lossOfCellDelineation (2)- Loss of cell delineation on the 1795 associated ATM data path" 1797 SYNTAX BITS { 1798 noDefect(0), 1799 noCellDelineation(1), 1800 lossOfCellDelineation(2) 1801 } 1803 Xsl2ChPtmStatus ::= TEXTUAL-CONVENTION 1804 STATUS current 1805 DESCRIPTION 1806 "Attributes with this syntax are status parameters that 1807 reflect the failure status for a given PTM interface (packet 1808 data path over a VDSL2/ADSL/ADSL2 or ADSL2+ link). 1810 This BITS structure can report the following failures: 1811 noDefect (0) - This bit position positively 1812 reports that no defect or failure exist. 1813 outOfSync (1) - Out of synchronization. " 1815 SYNTAX BITS { 1816 noDefect(0), 1817 outOfSync(1) 1818 } 1820 END 1822 VSL2-LINE-MIB DEFINITIONS ::= BEGIN 1824 IMPORTS 1825 MODULE-IDENTITY, 1826 OBJECT-TYPE, 1827 transmission, 1828 Unsigned32, 1829 NOTIFICATION-TYPE, 1830 Integer32, 1831 Counter32 1832 FROM SNMPv2-SMI 1834 ifIndex 1835 FROM IF-MIB 1837 TruthValue, 1838 RowStatus 1839 FROM SNMPv2-TC 1841 SnmpAdminString 1842 FROM SNMP-FRAMEWORK-MIB 1844 HCPerfIntervalThreshold, 1845 HCPerfTimeElapsed 1846 FROM HC-PerfHist-TC-MIB -- [RFC3705] 1848 Xdsl2Unit, 1849 Xdsl2Direction, 1850 Xdsl2TransmissionModeType, 1851 Xdsl2RaMode, 1852 Xdsl2InitResult, 1853 Xdsl2OperationModes, 1854 Xdsl2PowerMngState, 1855 Xdsl2ConfPmsForce, 1856 Xdsl2LConfProfPmMode, 1857 Xdsl2LineLdsf, 1858 Xdsl2LdsfResult, 1859 Xdsl2SymbolProtection, 1860 Xdsl2MaxBer, 1861 Xdsl2ScMaskDs, 1862 Xdsl2ScMaskUs, 1863 Xdsl2RfiDs, 1864 Xdsl2PsdMaskDs, 1865 Xdsl2PsdMaskUs, 1866 Xdsl2Tssi, 1867 Xdsl2LastTransmittedState, 1868 Xdsl2LineStatus, 1869 Xdsl2ChAtmStatus, 1870 Xdsl2ChPtmStatus 1871 FROM VSL2-LINE-TC-MIB -- [This document] 1873 MODULE-COMPLIANCE, 1874 OBJECT-GROUP, 1875 NOTIFICATION-GROUP 1876 FROM SNMPv2-CONF; 1878 vsl2MIB MODULE-IDENTITY 1879 LAST-UPDATED "200601220000Z" -- January 22, 2006 1880 ORGANIZATION "ADSLMIB Working Group" 1881 CONTACT-INFO "WG-email: adslmib@ietf.org 1882 Info: https://www1.ietf.org/mailman/listinfo/adslmib 1884 Chair: Mike Sneed 1885 Sand Channel Systems 1886 Postal: P.O. Box 37324 1887 Raleigh NC 27627-732 1888 Email: sneedmike@hotmail.com 1889 Phone: +1 206 600 7022 1891 Co-Chair: Menachem Dodge 1892 ECI Telecom Ltd. 1893 Postal: 30 Hasivim St. 1894 Petach Tikva 49517, 1895 Israel. 1896 Email: mbdodge@ieee.org 1897 Phone: +972 3 926 8421 1899 Co-editor: Moti Morgenstern 1900 ECI Telecom Ltd. 1901 Postal: 30 Hasivim St. 1902 Petach Tikva 49517, 1903 Israel. 1904 Email: moti.morgenstern@ecitele.com 1905 Phone: +972 3 926 6258 1907 Co-editor: Scott Baillie 1908 NEC Australia 1909 Postal: 649-655 Springvale Road, 1910 Mulgrave, Victoria 3170, 1911 Australia. 1912 Email: scott.baillie@nec.com.au 1913 Phone: +61 3 9264 3986 1915 Co-editor: Umberto Bonollo 1916 NEC Australia 1917 Postal: 649-655 Springvale Road, 1918 Mulgrave, Victoria 3170, 1919 Australia. 1920 Email: umberto.bonollo@nec.com.au 1921 Phone: +61 3 9264 3385 1922 " 1923 DESCRIPTION 1924 " 1925 This document defines a Management Information Base (MIB) 1926 module for use with network management protocols in the 1927 Internet community for the purpose of managing VDSL2, ADSL, 1928 ADSL2, and ADSL2+ lines. 1930 The MIB module described in RFC 2662 [RFC2662] defines 1931 objects used for managing Asymmetric Bit-Rate DSL (ADSL) 1932 interfaces per [T1E1.413], [G.992.1], and [G.992.2]. 1933 These object descriptions are based upon the specifications 1934 for the ADSL Embedded Operations Channel (EOC) as defined 1935 in American National Standards Institute (ANSI) T1E1.413 1936 [T1E1.413] and International Telecommunication Union (ITU-T) 1937 G.992.1 [G.992.1] and G.992.2 [G.992.2]. 1939 The MIB module described in RFC xxxx [RFCxxx] defines 1940 objects used for managing ADSL2 interfaces per [G.992.3] 1941 and [G.992.4], and ADSL2+ interfaces per [g.992.5]. That MIB 1942 is also capable of managing ADSL interfaces per [T1E1.413], 1944 [G.992.1], and [G.992.2]. 1946 This document does not obsolete RFC 2662 [RFC2662] and 1947 RFCxxxx [RFCxxxx], but rather provides a more comprehensive 1948 management model that manages VDSL2 interfaces per G.993.2 1949 [G.993.2] as well as ADSL, ADSL2 and ADSL2+ technologies 1950 per T1E1.413, G.992.1, G.992.2, G.992.3, G.992.4, and 1951 G.992.5 1952 ([T1E1.413], [G.992.1], [G.992.2], [G.992.3], [G.992.4], and 1953 [G.992.5] respectively). 1955 Additionally, the management framework for VDSL2 lines 1956 specified by the Digital Subscriber Line Forum 1957 (DSLF) has been taken into consideration [TR-129]. That 1958 framework is based on ITU-T G.997.1 standard [G.997.1]. 1960 The MIB module is located in the MIB tree under MIB 2 1961 transmission, as discussed in the MIB-2 Integration (RFC 2863 1962 [RFC2863]) section of this document. 1964 Copyright (C) The Internet Society (2006). This version of 1965 this MIB module is part of RFC XXXX: see the RFC itself for 1966 full legal notices." 1968 -- RFC Ed.: replace XXXX with assigned number & remove this note 1969 REVISION "200601220000Z" -- January 22, 2006 1970 DESCRIPTION "Initial version, published as RFC XXXX." 1971 -- RFC Ed.: replace XXXX with assigned number & remove this note 1972 ::= { transmission xxx } 1973 -- IANA, we suggest to put it under { transmission xxx } because 1974 -- this is the first available number. 1975 -- RFC Ed.: Please fill in xxx once assigned by IANA. 1977 vdsl2 OBJECT IDENTIFIER ::= { vdsl2MIB 1 } 1978 ------------------------------------------------ 1979 xdsl2Line OBJECT IDENTIFIER ::= { vdsl2 1 } 1980 xdsl2Status OBJECT IDENTIFIER ::= { vdsl2 2 } 1981 xdsl2Inventory OBJECT IDENTIFIER ::= { vdsl2 3 } 1982 xdsl2PM OBJECT IDENTIFIER ::= { vdsl2 4 } 1983 xdsl2Profile OBJECT IDENTIFIER ::= { vdsl2 5 } 1984 xdsl2Scalar OBJECT IDENTIFIER ::= { vdsl2 6 } 1985 xdsl2Notifications OBJECT IDENTIFIER ::= { vdsl2 0 } 1986 xdsl2Conformance OBJECT IDENTIFIER ::= { vdsl2 8 } 1987 ------------------------------------------------ 1988 xdsl2PMLine OBJECT IDENTIFIER ::= { xdsl2PM 1 } 1989 xdsl2PMChannel OBJECT IDENTIFIER ::= { xdsl2PM 2 } 1990 ------------------------------------------------ 1991 xdsl2ProfileLine OBJECT IDENTIFIER ::= { xdsl2Profile 1 } 1992 xdsl2ProfileChannel OBJECT IDENTIFIER ::= { xdsl2Profile 2 } 1993 xdsl2ProfileAlarmConf OBJECT IDENTIFIER ::= { xdsl2Profile 3 } 1994 ------------------------------------------------ 1995 xdsl2ScalarSC OBJECT IDENTIFIER ::= { xdsl2Scalar 1 } 1996 ------------------------------------------------ 1998 ------***************************************************** 1999 ----- Should revise all references in this MIB 2000 ------***************************************************** 2002 ------------------------------------------------ 2003 -- xdsl2LineTable -- 2004 ------------------------------------------------ 2005 xdsl2LineTable OBJECT-TYPE 2006 SYNTAX SEQUENCE OF Xdsl2LineEntry 2007 MAX-ACCESS not-accessible 2008 STATUS current 2009 DESCRIPTION 2010 "The table adsl2LineTable contains configuration, 2011 command and status parameters of the VDSL2/ADSL/ADSL2 2012 or ADSL2+ line. 2013 The index of this table is an interface index where the 2014 interface has an ifType of vdsl2(xxx). 2016 Several objects in this table MUST be maintained in a 2017 persistent manner. " 2018 ::= { xdsl2Line 1 } 2020 xdsl2LineEntry OBJECT-TYPE 2021 SYNTAX Adsl2LineEntry 2022 MAX-ACCESS not-accessible 2023 STATUS current 2024 DESCRIPTION 2025 "The table xdsl2LineTable contains configuration, 2026 commands and status parameters of the VDSL2/ADSL/ADSL2 2027 or ADSL2+ line." 2028 INDEX { ifIndex } 2029 ::= { xdsl2LineTable 1 } 2031 Xdsl2LineEntry ::= 2032 SEQUENCE { 2033 xdsl2LineCnfgTemplate SnmpAdminString, 2034 xdsl2LineAlarmCnfgTemplate SnmpAdminString, 2035 xdsl2LineCmndConfPmsf Xdsl2ConfPmsForce, 2036 xdsl2LineCmndConfLdsf Xdsl2LineLdsf, 2037 xdsl2LineCmndConfLdsfFailReason Xdsl2LdsfResult, 2038 xdsl2LineCmndAutomodeColdStart TruthValue, 2039 xdsl2LineStatusXtuTransSys Xdsl2TransmissionModeType, 2040 xdsl2LineStatusPwrMngState Xdsl2PowerMngState, 2041 xdsl2LineStatusInitResult Xdsl2InitResult, 2042 xdsl2LineStatusLastStateDs Xdsl2LastTransmittedState, 2043 xdsl2LineStatusLastStateUs Xdsl2LastTransmittedState, 2044 xdsl2LineStatusXtur Xdsl2LineStatus, 2045 xdsl2LineStatusXtuc Xdsl2LineStatus, 2046 xdsl2LineStatusLnAttenDs Unsigned32, 2047 xdsl2LineStatusLnAttenUs Unsigned32, 2048 xdsl2LineStatusSigAttenDs Unsigned32, 2049 xdsl2LineStatusSigAttenUs Unsigned32, 2050 xdsl2LineStatusSnrMarginDs Integer32, 2051 xdsl2LineStatusSnrMarginUs Integer32, 2052 xdsl2LineStatusAttainableRateDs Unsigned32, 2053 xdsl2LineStatusAttainableRateUs Unsigned32, 2054 xdsl2LineStatusActPsdDs Integer32, 2055 xdsl2LineStatusActPsdUs Integer32, 2056 xdsl2LineStatusActAtpDs Integer32, 2057 xdsl2LineStatusActAtpUs Integer32 2058 } 2060 xdsl2LineCnfgTemplate OBJECT-TYPE 2061 SYNTAX SnmpAdminString (SIZE(1..32)) 2062 MAX-ACCESS read-write 2063 STATUS current 2064 DESCRIPTION 2065 "The value of this object identifies the row in the xDSL2 Line 2066 Configuration Templates Table, (xdsl2LineConfTemplateTable), 2067 which applies for this line. 2069 This object MUST be maintained in a persistent manner." 2070 REFERENCE "DSL Forum TR-129, paragraph 5.1.1" 2071 DEFVAL { "DEFVAL" } 2072 ::= { xdsl2LineEntry 1 } 2074 xdsl2LineAlarmCnfgTemplate OBJECT-TYPE 2075 SYNTAX SnmpAdminString (SIZE(1..32)) 2076 MAX-ACCESS read-write 2077 STATUS current 2078 DESCRIPTION 2079 "The value of this object identifies the row in the xDSL2 Line 2080 Alarm Configuration Template Table, 2081 (xdsl2LineAlarmConfTemplateTable), which applies to this line. 2083 This object MUST be maintained in a persistent manner." 2084 REFERENCE "DSL Forum TR-129, paragraph 5.1.1" 2085 DEFVAL { "DEFVAL" } 2086 ::= { xdsl2LineEntry 2 } 2088 xdsl2LineCmndConfPmsf OBJECT-TYPE 2089 SYNTAX Xdsl2ConfPmsForce 2090 MAX-ACCESS read-write 2091 STATUS current 2092 DESCRIPTION 2093 "Power management state forced. Defines the line states to be 2094 forced by the near-end xTU on this line. The various possible 2095 values are: 2096 l3toL0 (0), 2097 l0toL2 (2), 2098 l0orL2toL3 (3). 2100 This object MUST be maintained in a persistent manner." 2101 REFERENCE "ITU-T G.997.1, paragraph 7.3.1.1.3" 2102 DEFVAL { l3toL0 } 2103 ::= { xdsl2LineEntry 3 } 2105 xdsl2LineCmndConfLdsf OBJECT-TYPE 2106 SYNTAX Xdsl2LineLdsf 2107 MAX-ACCESS read-write 2108 STATUS current 2109 DESCRIPTION 2110 "Loop diagnostics mode forced (LDSF). Defines whether the line 2111 should be forced into the loop diagnostics mode by the 2112 near-end xTU on this line or only be responsive to loop 2113 diagnostics initiated by the far-end xTU. 2115 This object MUST be maintained in a persistent manner. 2116 However, in case the operator forces loop diagnostics mode 2117 then the access node should reset the object (inhibit) when 2118 loop diagnostics mode procedures are completed." 2119 REFERENCE "ITU-T G.997.1, paragraph 7.3.1.1.8" 2120 DEFVAL { inhibit } 2121 ::= { xdsl2LineEntry 4 } 2123 xdsl2LineCmndConfLdsfFailReason OBJECT-TYPE 2124 SYNTAX Xdsl2LdsfResult 2125 MAX-ACCESS read-only 2126 STATUS current 2127 DESCRIPTION 2128 "The status of the recent occasion the Loop diagnostics mode 2129 forced (LDSF) was issued for the associated line. Possible 2130 values are: 2131 none (1) - The default value in case LDSF was never 2132 requested for the associated line. 2133 success (2) - The recent command completed 2134 successfully. 2135 inProgress (3) - The Loop Diagnostics process is in 2136 progress. 2137 unsupported (4) - The NE or the line card doesn't support 2138 LDSF. 2139 cannotRun (5) - The NE cannot initiate the command, due 2140 to a non specific reason. 2141 aborted (6) - The Loop Diagnostics process aborted. 2142 failed (7) - The Loop Diagnostics process failed. 2143 illegalMode (8) - The NE cannot initiate the command, due 2144 to the specific mode of the relevant 2145 line. 2146 adminUp (9) - The NE cannot initiate the command, as 2147 the relevant line is administratively 2148 'Up'. 2149 tableFull (10)- The NE cannot initiate the command, due 2150 to reaching the maximum number of rows 2151 in the results table. 2152 noResources (11)- The NE cannot initiate the command, due 2153 to lack of internal memory resources." 2154 DEFVAL { none } 2155 ::= { xdsl2LineEntry 5 } 2157 xdsl2LineCmndAutomodeColdStart OBJECT-TYPE 2158 SYNTAX TruthValue 2159 MAX-ACCESS read-write 2160 STATUS current 2161 DESCRIPTION 2162 "Automode cold start forced. This parameter is defined 2163 in order to improve testing of the performance of xTUs 2164 supporting automode when it is enabled in the MIB. 2165 Change the value of this parameter to 'true' indicates 2166 a change in loop conditions applied to the devices under 2167 test. The xTUs shall reset any historical information 2168 used for automode and for shortening G.994.1 handshake 2169 and initialization. 2171 Automode is the case where multiple operation-modes are 2172 enabled through the xdsl2LConfProfAtuTransSysEna object 2173 in the line configuration profile being used for the 2174 line, and where the selection of the actual 2175 operation-mode depends not only on the common 2176 capabilities of both xTUs (as exchanged in G.994.1), but 2177 also on achievable data rates under given loop 2178 conditions. 2180 This object MUST be maintained in a persistent manner." 2182 REFERENCE "ITU-T G.997.1, paragraph 7.3.1.1.10" 2183 DEFVAL { false } 2184 ::= { xdsl2LineEntry 6 } 2186 xdsl2LineStatusAtuTransSys OBJECT-TYPE 2187 SYNTAX Xdsl2TransmissionModeType 2188 MAX-ACCESS read-only 2189 STATUS current 2190 DESCRIPTION 2191 "The xTU Transmission System (xTS) in use. 2192 It is coded in a bit-map representation with one bit set to 2193 '1' (the selected coding for the DSL line). This parameter 2194 may be derived from the handshaking procedures defined in 2195 Recommendation G.994.1. A set of xDSL line transmission 2196 modes, with one bit per mode. " 2197 REFERENCE "ITU-T G.997.1, paragraph 7.3.1.1.1" 2198 ::= { xdsl2LineEntry 7 } 2200 xdsl2LineStatusPwrMngState OBJECT-TYPE 2201 SYNTAX Xdsl2PowerMngState 2202 MAX-ACCESS read-only 2203 STATUS current 2204 DESCRIPTION 2205 "The current power management state. One of four possible 2206 power management states: 2207 L0 - Synchronized and full transmission (i.e., Showtime), 2208 L1 - Low Power with reduced net data rate (G.992.2 only), 2209 L2 - Low Power with reduced net data rate (G.992.3 and 2210 G.992.4 only), 2211 L3 - No power 2212 The various possible values are:l0(1), l1(2), l2(3), l3(4)." 2213 REFERENCE "ITU-T G.997.1, paragraph 7.5.1.2" 2214 ::= { xdsl2LineEntry 8 } 2216 xdsl2LineStatusInitResult OBJECT-TYPE 2217 SYNTAX Xdsl2InitResult 2218 MAX-ACCESS read-only 2219 STATUS current 2220 DESCRIPTION 2221 "Indicates the result of the last full initialization performed 2222 on the line. It is an enumeration type with the following 2223 values: noFailure(0), configError(1), configNotFeasible(2), 2224 commFail(3), noPeerAtu(4), otherCause(5)." 2225 REFERENCE "ITU-T G.997.1, paragraph 7.5.1.3" 2226 ::= { xdsl2LineEntry 9 } 2228 xdsl2LineStatusLastStateDs OBJECT-TYPE 2229 SYNTAX Xdsl2LastTransmittedState 2230 MAX-ACCESS read-only 2231 STATUS current 2232 DESCRIPTION 2233 "The last successful transmitted initialization state in 2234 the downstream direction in the last full initialization 2235 performed on the line." 2236 REFERENCE "ITU-T G.997.1, paragraph 7.5.1.4" 2237 ::= { xdsl2LineEntry 10 } 2239 xdsl2LineStatusLastStateUs OBJECT-TYPE 2240 SYNTAX Xdsl2LastTransmittedState 2241 MAX-ACCESS read-only 2242 STATUS current 2243 DESCRIPTION 2244 "The last successful transmitted initialization state in the 2245 upstream direction in the last full initialization performed 2246 on the line." 2247 REFERENCE "ITU-T G.997.1, paragraph 7.5.1.5" 2248 ::= { xdsl2LineEntry 11 } 2250 xdsl2LineStatusXtur OBJECT-TYPE 2251 SYNTAX Xdsl2LineStatus 2252 MAX-ACCESS read-only 2253 STATUS current 2254 DESCRIPTION 2255 "Indicates current state (existing failures) of the xTU-R. 2256 This is a bit-map of possible conditions. " 2257 REFERENCE "ITU-T G.997.1, paragraph 7.1.1.2" 2258 ::= { xdsl2LineEntry 12 } 2260 xdsl2LineStatusXtuc OBJECT-TYPE 2261 SYNTAX Xdsl2LineStatus 2262 MAX-ACCESS read-only 2263 STATUS current 2264 DESCRIPTION 2265 "Indicates current state (existing failures) of the xTU-C. 2266 This is a bit-map of possible conditions. " 2267 REFERENCE "ITU-T G.997.1, paragraph 7.1.1.1" 2268 ::= { xdsl2LineEntry 13 } 2270 xdsl2LineStatusLnAttenDs OBJECT-TYPE 2271 SYNTAX Unsigned32 2272 UNITS "0.1 dB" 2273 MAX-ACCESS read-only 2274 STATUS current 2275 DESCRIPTION 2276 "The measured difference in the total power transmitted by the 2277 xTU-C and the total power received by the xTU-R over all sub- 2278 carriers during diagnostics mode and initialization. It 2279 ranges from 0 to 1270 units of 0.1 dB (Physical values 2280 are 0 to 127 dB). A value of all 1's indicates the line 2281 attenuation is out of range to be represented." 2282 REFERENCE "ITU-T G.997.1, paragraph 7.5.1.6" 2283 ::= { xdsl2LineEntry 14 } 2285 xdsl2LineStatusLnAttenUs OBJECT-TYPE 2286 SYNTAX Unsigned32 2287 UNITS "0.1 dB" 2288 MAX-ACCESS read-only 2289 STATUS current 2290 DESCRIPTION 2291 "The measured difference in the total power transmitted by the 2292 xTU-R and the total power received by the xTU-C over all sub- 2293 carriers during diagnostics mode and initialization. 2294 It ranges from 0 to 1270 units of 0.1 dB (Physical values are 2295 0 to 127 dB). A value of all 1's indicates the line 2296 attenuation is out of range to be represented." 2297 REFERENCE "ITU-T G.997.1, paragraph 7.5.1.7" 2298 ::= { xdsl2LineEntry 15 } 2300 xdsl2LineStatusSigAttenDs OBJECT-TYPE 2301 SYNTAX Unsigned32 2302 UNITS "0.1 dB" 2303 MAX-ACCESS read-only 2304 STATUS current 2305 DESCRIPTION 2306 "The measured difference in the total power transmitted by the 2307 xTU-C and the total power received by the xTU-R over all sub- 2308 carriers during Showtime. It ranges from 0 to 1270 units of 2309 0.1 dB (Physical values are 0 to 127 dB). A value of all 2310 1's indicates the line attenuation is out of range to be 2311 represented." 2312 REFERENCE "ITU-T G.997.1, paragraph 7.5.1.8" 2313 ::= { xdsl2LineEntry 16 } 2315 xdsl2LineStatusSigAttenUs OBJECT-TYPE 2316 SYNTAX Unsigned32 2317 UNITS "0.1 dB" 2318 MAX-ACCESS read-only 2319 STATUS current 2320 DESCRIPTION 2321 "The measured difference in the total power transmitted by the 2322 xTU-R and the total power received by the xTU-C over all sub- 2323 carriers during Showtime. It ranges from 0 to 1270 units of 2324 0.1 dB (Physical values are 0 to 127 dB). A value of all 2325 1's indicates the line attenuation is out of range to be 2326 represented." 2328 REFERENCE "ITU-T G.997.1, paragraph 7.5.1.9" 2329 ::= { xdsl2LineEntry 17 } 2331 xdsl2LineStatusSnrMarginDs OBJECT-TYPE 2332 SYNTAX Integer32 2333 UNITS "0.1 dB" 2334 MAX-ACCESS read-only 2335 STATUS current 2336 DESCRIPTION 2337 "Downstream SNR Margin is the maximum increase in dB of the 2338 noise power received at the xTU-R, such that the BER 2339 requirements are met for all downstream bearer channels. It 2340 ranges from -640 to 630 units of 0.1 dB (Physical values are 2341 -64 to 63 dB). A value of all 1's indicates the line 2342 attenuation is out of range to be represented." 2343 REFERENCE "ITU-T G.997.1, paragraph 7.5.1.10" 2344 ::= { xdsl2LineEntry 18 } 2346 xdsl2LineStatusSnrMarginUs OBJECT-TYPE 2347 SYNTAX Integer32 2348 UNITS "0.1 dB" 2349 MAX-ACCESS read-only 2350 STATUS current 2351 DESCRIPTION 2352 "Upstream SNR Margin is the maximum increase in dB of the noise 2353 power received at the xTU-C, such that the BER requirements 2354 are met for all downstream bearer channels. It ranges from 2355 -640 to 630 units of 0.1 dB (Physical values are -64 to 2356 63 dB). A value of all 1's indicates the line attenuation 2357 is out of range to be represented." 2358 REFERENCE "ITU-T G.997.1, paragraph 7.5.1.11" 2359 ::= { xdsl2LineEntry 19 } 2361 xdsl2LineStatusAttainableRateDs OBJECT-TYPE 2362 SYNTAX Unsigned32 2363 UNITS "bits/second" 2364 MAX-ACCESS read-only 2365 STATUS current 2366 DESCRIPTION 2367 "Maximum Attainable Data Rate Downstream. 2368 The maximum downstream net data rate currently attainable by 2369 the xTU-C transmitter and the xTU-R receiver, coded in bit/s." 2370 REFERENCE "ITU-T G.997.1, paragraph 7.5.1.12" 2371 ::= { xdsl2LineEntry 20 } 2373 xdsl2LineStatusAttainableRateUs OBJECT-TYPE 2374 SYNTAX Unsigned32 2375 UNITS "bits/second" 2376 MAX-ACCESS read-only 2377 STATUS current 2378 DESCRIPTION 2379 "Maximum Attainable Data Rate Upstream. 2380 The maximum upstream net data rate currently attainable by the 2381 xTU-R transmitter and the xTU-C receiver, coded in bit/s." 2382 REFERENCE "ITU-T G.997.1, paragraph 7.5.1.13" 2383 ::= { xdsl2LineEntry 21 } 2385 xdsl2LineStatusActPsdDs OBJECT-TYPE 2386 SYNTAX Integer32 2387 UNITS "0.1 dB" 2388 MAX-ACCESS read-only 2389 STATUS current 2390 DESCRIPTION 2391 "Actual Power Spectrum Density (PSD) Downstream. The average 2392 downstream transmit PSD over the sub-carriers used for 2393 downstream. It ranges from -900 to 0 units of 0.1 dB 2394 (Physical values are -90 to 0 dBm/Hz). A value of all 1's 2395 indicates the measurement is out of range to be represented." 2396 REFERENCE "ITU-T G.997.1, paragraph 7.5.1.14" 2397 ::= { xdsl2LineEntry 22 } 2399 xdsl2LineStatusActPsdUs OBJECT-TYPE 2400 SYNTAX Integer32 2401 UNITS "0.1 dB" 2402 MAX-ACCESS read-only 2403 STATUS current 2404 DESCRIPTION 2405 "Actual Power Spectrum Density (PSD) Upstream. The average 2406 upstream transmit PSD over the sub-carriers used for upstream. 2407 It ranges from -900 to 0 units of 0.1 dB (Physical values 2408 are -90 to 0 dBm/Hz). A value of all 1's indicates the 2409 measurement is out of range to be represented." 2410 REFERENCE "ITU-T G.997.1, paragraph 7.5.1.15" 2411 ::= { xdsl2LineEntry 23 } 2413 xdsl2LineStatusActAtpDs OBJECT-TYPE 2414 SYNTAX Integer32 2415 UNITS "0.1 dB" 2416 MAX-ACCESS read-only 2417 STATUS current 2418 DESCRIPTION 2419 "Actual Aggregate Transmit Power Downstream. The total amount 2420 of transmit power delivered by the xTU-C at the U-C reference 2421 point, at the instant of measurement. It ranges from -310 to 2422 310 units of 0.1 dB (Physical values are -31 to 31 dBm). A 2423 value of all 1's indicates the measurement is out of range to 2424 be represented." 2425 REFERENCE "ITU-T G.997.1, paragraph 7.5.1.16" 2426 ::= { xdsl2LineEntry 24 } 2428 xdsl2LineStatusActAtpUs OBJECT-TYPE 2429 SYNTAX Integer32 2430 UNITS "0.1 dB" 2431 MAX-ACCESS read-only 2432 STATUS current 2433 DESCRIPTION 2434 "Actual Aggregate Transmit Power Upstream. The total amount of 2435 transmit power delivered by the xTU-R at the U-R 2436 reference point, at the instant of measurement. It ranges 2437 from -310 to 310 units of 0.1 dB (Physical values are -31 2438 to 31 dBm). A value of all 1's indicates the measurement 2439 is out of range to be represented." 2440 REFERENCE "ITU-T G.997.1, paragraph 7.5.1.17" 2441 ::= { xdsl2LineEntry 25 } 2443 ------------------------------------------------ 2444 -- xdsl2ChannelStatusTable -- 2445 ------------------------------------------------ 2446 xdsl2ChannelStatusTable OBJECT-TYPE 2447 SYNTAX SEQUENCE OF Xdsl2ChannelStatusEntry 2448 MAX-ACCESS not-accessible 2449 STATUS current 2450 DESCRIPTION 2451 "The table xdsl2ChannelStatusTable contains status 2452 parameters of VDSL2/ADSL/ADSL2 or ADSL2+ channel. 2453 This table contains live data from equipment. As such, 2454 it is NOT persistent." 2455 ::= { xdsl2Status 1 } 2457 xdsl2ChannelStatusEntry OBJECT-TYPE 2458 SYNTAX Xdsl2ChannelStatusEntry 2459 MAX-ACCESS not-accessible 2460 STATUS current 2461 DESCRIPTION 2462 "The table xdsl2ChannelStatusTable contains status 2463 parameters of VDSL2/ADSL/ADSL2 or ADSL2+ channel. 2464 The index of this table is an interface index where 2465 the interface has an ifType value that is applicable 2466 for a DSL channel and the termination unit." 2467 INDEX { ifIndex, xdsl2ChStatusUnit } 2468 ::= { adsl2ChannelStatusTable 1 } 2470 Adsl2ChannelStatusEntry ::= 2471 SEQUENCE { 2472 adsl2ChStatusUnit Xdsl2Unit, 2473 xdsl2ChStatusChannelNum Unsigned32, 2474 xdsl2ChStatusActDataRate Unsigned32, 2475 xdsl2ChStatusPrevDataRate Unsigned32, 2476 xdsl2ChStatusActDelay Unsigned32, 2477 xdsl2ChStatusAtmStatus Xdsl2ChAtmStatus, 2478 xdsl2ChStatusPtmStatus Xdsl2ChPtmStatus 2479 } 2481 xdsl2ChStatusUnit OBJECT-TYPE 2482 SYNTAX Xdsl2Unit 2483 MAX-ACCESS not-accessible 2484 STATUS current 2485 DESCRIPTION 2486 "The termination unit xtuc(1) or xtur(2)." 2487 ::= { xdsl2ChannelStatusEntry 1 } 2489 xdsl2ChStatusChannelNum OBJECT-TYPE 2490 SYNTAX Unsigned32 2491 MAX-ACCESS read-only 2492 STATUS current 2493 DESCRIPTION 2494 "Provides the bearer channel number associated with this 2495 row (i.e., the channel ifIndex). 2496 This enables determining the channel configuration profile 2497 and the channel thresholds profile applicable for this 2498 bearer channel." 2499 ::= { xdsl2ChannelStatusEntry 2 } 2501 xdsl2ChStatusActDataRate OBJECT-TYPE 2502 SYNTAX Unsigned32(0..200000000) 2503 UNITS "bits/second" 2504 MAX-ACCESS read-only 2505 STATUS current 2506 DESCRIPTION 2507 "The actual net data rate that the bearer channel is operating 2508 at, if in L0 power management state. In L1 or L2 states, it 2509 relates to the previous L0 state. The data rate is coded in 2510 bit/s." 2511 REFERENCE "ITU-T G.997.1, paragraph 7.5.2.1" 2512 ::= { xdsl2ChannelStatusEntry 3 } 2514 xdsl2ChStatusPrevDataRate OBJECT-TYPE 2515 SYNTAX Unsigned32(0..200000000) 2516 UNITS "bits/second" 2517 MAX-ACCESS read-only 2518 STATUS current 2519 DESCRIPTION 2520 "The previous net data rate that the bearer channel was 2521 operating at just before the latest rate change event. This 2522 could be a full or short initialization, fast retrain, DRA or 2523 power management transitions, excluding transitions between L0 2524 state and L1 or L2 states. The data rate is coded in bit/s." 2525 REFERENCE "ITU-T G.997.1, paragraph 7.5.2.2" 2526 ::= { xdsl2ChannelStatusEntry 4 } 2528 xdsl2ChStatusActDelay OBJECT-TYPE 2529 SYNTAX Unsigned32(0..8176) 2530 UNITS "milliseconds" 2531 MAX-ACCESS read-only 2532 STATUS current 2533 DESCRIPTION 2534 "The actual one-way interleaving delay introduced by the 2535 PMS-TC in the direction of the bearer channel, if in L0 2536 power management state. In L1 or L2 states, it relates to 2537 the previous L0 state. It is coded in ms (rounded to the 2538 nearest ms)." 2539 REFERENCE "ITU-T G.997.1, paragraph 7.5.2.3" 2540 ::= { xdsl2ChannelStatusEntry 5 } 2542 xdsl2ChStatusAtmStatus OBJECT-TYPE 2543 SYNTAX Xdsl2ChAtmStatus 2544 MAX-ACCESS read-only 2545 STATUS current 2546 DESCRIPTION 2547 "Indicates current state (existing failures) of the DSL 2548 channel in case its Data Path is ATM. This is a bit-map of 2549 possible conditions. The various bit positions are: 2550 noFailure(0), 2551 noCellDelineation(1), 2552 lossOfCellDelineation (2). 2553 In case the channel is not of ATM Data Path the object is set 2554 to '0'." 2555 REFERENCE "ITU-T G.997.1, paragraph 7.1.4" 2556 ::= { xdsl2ChannelStatusEntry 6 } 2558 xdsl2ChStatusPtmStatus OBJECT-TYPE 2559 SYNTAX Xdsl2ChPtmStatus 2560 MAX-ACCESS read-only 2561 STATUS current 2562 DESCRIPTION 2563 "Indicates current state (existing failures) of the DSL 2564 channel in case its Data Path is PTM. This is a bit-map of 2565 possible conditions. The various bit positions are: 2566 noFailure(0), 2567 outOfSync (1). 2568 In case the channel is not of PTM Data Path the object is set 2569 to '0'." 2570 REFERENCE "ITU-T G.997.1, paragraph 7.1.5" 2571 ::= { xdsl2ChannelStatusEntry 7 } 2573 ------------------------------------------------ 2574 -- Scalars that relate to the xdsl2SCStatusTable. 2575 ------------------------------------------------ 2577 xdsl2ScalarSCMaxInterfaces OBJECT-TYPE 2578 SYNTAX Unsigned32 2579 MAX-ACCESS read-only 2580 STATUS current 2581 DESCRIPTION 2582 "This value determines the upper size of xdsl2SCStatusTable. 2583 The maximum number of entries in xdsl2SCStatusTable is equal 2584 to two times the value of this attribute." 2585 ::= { xdsl2ScalarSC 1 } 2587 xdsl2ScalarSCAvailInterfaces OBJECT-TYPE 2588 SYNTAX Unsigned32 2589 MAX-ACCESS read-only 2590 STATUS current 2591 DESCRIPTION 2592 "This value determines the amount of space that is 2593 currently available in xdsl2SCStatusTable. 2594 The number of entries available in xdsl2SCStatusTable is equal 2595 to two times the value of this attribute." 2596 ::= { xdsl2ScalarSC 2 } 2598 ------***************************************************** 2599 ----- Should revise The following table. 2600 ----- 1. There should be a reference to the SC groups 2601 ----- 2. We should solve the issue of too long data structures 2602 ----- caused by supporting 4096 sub-carriers. 2603 ------***************************************************** 2605 ------------------------------------------------ 2606 -- xdsl2SCStatusTable -- 2607 ------------------------------------------------ 2609 xdsl2SCStatusTable OBJECT-TYPE 2610 SYNTAX SEQUENCE OF Xdsl2SCStatusEntry 2611 MAX-ACCESS not-accessible 2612 STATUS current 2613 DESCRIPTION 2614 "The table xdsl2SCStatusTable contains status parameters 2615 of VDSL2/ADSL/ADSL2 and ADSL2+ sub-carriers. This table 2616 contains live data from equipment. As such, it is NOT 2617 persistent." 2618 ::= { xdsl2Status 2 } 2620 xdsl2SCStatusEntry OBJECT-TYPE 2621 SYNTAX Xdsl2SCStatusEntry 2622 MAX-ACCESS not-accessible 2623 STATUS current 2624 DESCRIPTION 2625 "The table Hfxdsl2SCStatusEntry contains status parameters 2626 of VDSL2/ADSL/ADSL2 and ADSL2+ sub-carriers. 2627 The index of this table is an interface index where the 2628 interface has an ifType of vdsl2(xxx)." 2629 INDEX { ifIndex, xdsl2SCStatusDirection } 2630 ::= { xdsl2SCStatusTable 1 } 2632 Xdsl2SCStatusEntry ::= 2633 SEQUENCE { 2634 xdsl2SCStatusDirection Xdsl2Direction, 2635 xdsl2SCStatusMtime Unsigned32, 2636 xdsl2SCStatusSnr OCTET STRING, 2637 xdsl2SCStatusBitsAlloc OCTET STRING, 2638 xdsl2SCStatusGainAlloc OCTET STRING, 2639 xdsl2SCStatusTssi Xdsl2Tssi, 2640 xdsl2SCStatusLinScale Unsigned32, 2641 xdsl2SCStatusLinReal OCTET STRING, 2642 xdsl2SCStatusLinImg OCTET STRING, 2643 xdsl2SCStatusLogMt Unsigned32, 2644 xdsl2SCStatusLog OCTET STRING, 2645 xdsl2SCStatusQlnMt Unsigned32, 2646 xdsl2SCStatusQln OCTET STRING, 2647 xdsl2SCStatusLnAtten Unsigned32, 2648 xdsl2SCStatusSigAtten Unsigned32, 2649 xdsl2SCStatusSnrMargin Integer32, 2650 xdsl2SCStatusAttainableRate Unsigned32, 2651 xdsl2SCStatusActAtp Integer32, 2652 xdsl2SCStatusRowStatus RowStatus 2653 } 2655 xdsl2SCStatusDirection OBJECT-TYPE 2656 SYNTAX Xdsl2Direction 2657 MAX-ACCESS not-accessible 2658 STATUS current 2659 DESCRIPTION 2660 "The direction of the sub-carrier either 2661 upstream or downstream" 2662 ::= { xdsl2SCStatusEntry 1 } 2664 xdsl2SCStatusMtime OBJECT-TYPE 2665 SYNTAX Unsigned32 2666 UNITS "symbols" 2667 MAX-ACCESS read-only 2668 STATUS current 2669 DESCRIPTION 2670 "SNR Measurement Time. The number of symbols used to 2671 measure the SNR values on the respective transmission 2672 direction. It should correspond to the value specified in the 2673 recommendation (e.g., the number of symbols in 1 second 2674 time interval for G.992.3). This parameter corresponds to 2675 1 second in loop diagnostic procedure and should be updated 2676 otherwise" 2677 REFERENCE "ITU-T G.997.1, paragraph 7.5.1.20.1 (SNRMTds) 2678 and paragraph 7.5.1.20.3 (SNRMTus)" 2679 ::= { xdsl2SCStatusEntry 2 } 2681 xdsl2SCStatusSnr OBJECT-TYPE 2682 SYNTAX OCTET STRING (SIZE(0..512)) 2683 MAX-ACCESS read-only 2684 STATUS current 2685 DESCRIPTION 2686 "The SNR Margin per sub-carrier, expressing the ratio between 2687 the received signal power and received noise power per 2688 subscriber. It is an array of 512 bytes, designed for 2689 supporting up to 512 (downstream) sub-carriers. 2690 The number of utilized octets on downstream direction depends 2691 on NSCds, and on upstream direction it depends on NSCus. This 2692 value is referred here as NSC. 2693 Byte i (0 <= i < NSC) is set to a value in the range 0 to 2694 254 to indicate that the respective downstream or upstream sub- 2695 carrier i has SNR of: (-32 + Xdsl2SubcarrierSnr(i)/2) in dB 2696 (i.e., -32 to 95dB). 2697 The special value 255 means that no measurement could be done 2698 for the subcarrier because it is out of the PSD mask passband 2699 or that the noise PSD is out of range to be represented. 2700 Each value in this array is 8 bits wide." 2701 REFERENCE "ITU-T G.997.1, paragraph 7.5.1.20.2 (SNRpsds) 2702 and paragraph 7.5.1.20.4 (SNRpsus)" 2703 ::= { xdsl2SCStatusEntry 3 } 2705 xdsl2SCStatusBitsAlloc OBJECT-TYPE 2706 SYNTAX OCTET STRING (SIZE(0..256)) 2707 UNITS "bits" 2708 MAX-ACCESS read-only 2709 STATUS current 2710 DESCRIPTION 2711 "The bits allocation per sub-carrier. An array of 256 bytes 2712 (512 nibbles), designed for supporting up to 512 (downstream) 2713 sub-carriers. 2714 The number of utilized nibbles on downstream direction depends 2715 on NSCds, and on upstream direction it depends on NSCus. This 2716 value is referred here as NSC. 2717 Nibble i (0 <= i < NSC) is set to a value in the range 0 2718 to 15 to indicate that the respective downstream or upstream 2719 sub-carrier i has the same amount of bits allocation." 2720 REFERENCE "ITU-T G.997.1, paragraph 7.5.1.21.1 (BITSpsds) 2721 and paragraph 7.5.1.21.2 (BITSpsus)" 2722 ::= { xdsl2SCStatusEntry 4 } 2724 xdsl2SCStatusGainAlloc OBJECT-TYPE 2725 SYNTAX OCTET STRING (SIZE(0..1024)) 2726 MAX-ACCESS read-only 2727 STATUS current 2728 DESCRIPTION 2729 "The gain allocation per sub-carrier. An array of 512 16-bits 2730 values, designed for supporting up to 512 (downstream) sub- 2731 carriers. 2732 The number of utilized octets on downstream direction depends 2733 on NSCds, and on upstream direction it depends on NSCus. This 2734 value is referred here as NSC. 2735 Value i (0 <= i < NSC) is in the range 0 to 4093 to indicate 2736 that the respective downstream or upstream sub-carrier i has the 2737 same amount of gain value. 2738 The gain value is represented as a multiple of 1/512 on 2739 linear scale. Each value in this array is 16 bits wide and is 2740 stored in big endian format." 2741 REFERENCE "ITU-T G.997.1, paragraph 7.5.1.21.3 (GAINSpsds) 2742 and paragraph 7.5.1.21.4 (GAINSpsus)" 2743 ::= { xdsl2SCStatusEntry 5 } 2745 xdsl2SCStatusTssi OBJECT-TYPE 2746 SYNTAX Xdsl2Tssi 2747 MAX-ACCESS read-only 2748 STATUS current 2749 DESCRIPTION 2750 "The transmit spectrum shaping (TSSi) breakpoints expressed 2751 as the set of breakpoints exchanged during G.994.1. 2752 Each breakpoint is a pair of values occupying 3 octets with the 2753 following structure: 2754 First 2 octets - Index of the subcarrier used in the context of 2755 the breakpoint. 2756 Third octet - The shaping parameter at the breakpoint. 2758 Subcarrier index is an unsigned number in the range 1 to either 2759 NSCds (downstream direction) or NSCus (upstream direction). 2760 The shaping parameter value is in the range 0 to 127 (units of 2761 -0.5dB). The special value 127 indicates that the subcarrier 2762 is not transmitted." 2763 REFERENCE "ITU-T G.997.1, paragraph 7.5.1.21.5 (TSSpsds) 2764 and paragraph 7.5.1.21.6 (TSSpsus)" 2765 ::= { xdsl2SCStatusEntry 6 } 2767 xdsl2SCStatusLinScale OBJECT-TYPE 2768 SYNTAX Unsigned32 2769 MAX-ACCESS read-only 2770 STATUS current 2771 DESCRIPTION 2772 "The scale factor to be applied to the H(f) linear 2773 representation values for the respective transmission direction. 2774 This parameter is only available after a loop diagnostic 2775 procedure." 2776 REFERENCE "ITU-T G.997.1, paragraph 7.5.1.18.1 (HLINSCds) 2777 and paragraph 7.5.1.18.5 (HLINSCus)" 2778 ::= { xdsl2SCStatusEntry 7 } 2780 xdsl2SCStatusLinReal OBJECT-TYPE 2781 SYNTAX OCTET STRING (SIZE(0..1024)) 2782 MAX-ACCESS read-only 2783 STATUS current 2784 DESCRIPTION 2785 "An array of up to 512 complex H(f) linear representation 2786 values in linear scale for the respective transmission 2787 direction. It is designed to support up to 512 (downstream) 2788 sub-carriers. 2789 The number of utilized values on downstream direction depends 2790 on NSCds, and on upstream direction it depends on NSCus. This 2791 value is referred here as NSC. 2792 Each array entry represents the real component [referred here as 2793 a(i)] of Hlin(f = i*Df) value for a particular sub-carrier index 2794 i (0 <= i < NSC). 2795 Hlin(f) is represented as ((scale/2^15)*((a(i)+j*b(i))/2^15)), 2796 where scale is Xdsl2SubcarrierLinScale and a(i) and b(i) 2797 [provided by the Xdsl2SubcarrierLinImg object] are in the range 2798 (-2^15+1) to (+2^15-1). 2799 A special value a(i)=b(i)= -2^15 indicates that no measurement 2800 could be done for the subcarrier because it is out of the 2801 passband or that the attenuation is out of range to be 2802 represented. This parameter is only available after a loop 2803 diagnostic procedure. 2804 Each value in this array is 16 bits wide and is stored in big 2805 endian format." 2807 REFERENCE "ITU-T G.997.1, paragraph 7.5.1.18.2 (HLINpsds) 2808 and paragraph 7.5.1.18.6 (HLINpsds)" 2809 ::= { xdsl2SCStatusEntry 8 } 2811 xdsl2SCStatusLinImg OBJECT-TYPE 2812 SYNTAX OCTET STRING (SIZE(0..1024)) 2813 MAX-ACCESS read-only 2814 STATUS current 2815 DESCRIPTION 2816 "An array of up to 512 complex H(f) linear representation 2817 values in linear scale for the respective transmission 2818 direction. It is designed to support up to 512 (downstream) 2819 sub-carriers. 2820 The number of utilized values on downstream direction depends 2821 on NSCds, and on upstream direction it depends on NSCus. This 2822 value is referred here as NSC. 2823 Each array entry represents the imaginary component [referred 2824 here as b(i)] of Hlin(f = i*Df) value for a particular sub- 2825 carrier index i (0 <= i < NSC). 2826 Hlin(f) is represented as ((scale/2^15)*((a(i)+j*b(i))/2^15)), 2827 where scale is Xdsl2SubcarrierLinScale and a(i) [provided by 2828 the Xdsl2SubcarrierLinReal object] and b(i) are in the range 2829 (-2^15+1) to (+2^15-1). 2830 A special value a(i)=b(i)= -2^15 indicates that no measurement 2831 could be done for the subcarrier because it is out of the 2832 passband or that the attenuation is out of range to be 2833 represented. This parameter is only available after a loop 2834 diagnostic procedure. 2835 Each value in this array is 16 bits wide and is stored in big 2836 endian format." 2837 REFERENCE "ITU-T G.997.1, paragraph 7.5.1.18.2 (HLINpsds) 2838 and paragraph 7.5.1.18.6 (HLINpsds)" 2839 ::= { xdsl2SCStatusEntry 9 } 2841 xdsl2SCStatusLogMt OBJECT-TYPE 2842 SYNTAX Unsigned32 2843 MAX-ACCESS read-only 2844 STATUS current 2845 DESCRIPTION 2846 "The number of symbols used to measure the H(f) logarithmic 2847 measurement values for the respective transmission direction. 2848 This parameter should correspond to the value specified in the 2849 recommendation (e.g., the number of symbols in 1 second 2850 time interval for G.992.3). This parameter corresponds to 1 2851 second in loop diagnostic procedure and should be updated in 2852 initialization" 2853 REFERENCE "ITU-T G.997.1, paragraph 7.5.1.18.3 (HLOGMTds) 2854 and paragraph 7.5.1.18.7 (HLOGMTus)" 2856 ::= { xdsl2SCStatusEntry 10 } 2858 xdsl2SCStatusLog OBJECT-TYPE 2859 SYNTAX OCTET STRING (SIZE(0..1024)) 2860 MAX-ACCESS read-only 2861 STATUS current 2862 DESCRIPTION 2863 "An array of up to 512 real H(f) logarithmic representation 2864 values in dB for the respective transmission direction. It is 2865 designed to support up to 512 (downstream) sub-carriers 2866 The number of utilized values on downstream direction depends 2867 on NSCds, and on upstream direction it depends on NSCus. This 2868 value is referred here as NSC. 2869 Each array entry represents the real Hlog(f = i*Df) value for a 2870 particular sub-carrier index i, (0 <= i < NSC). 2871 The real Hlog(f) value is represented as (6-m(i)/10), with m(i) 2872 in the range 0 to 1022. A special value m=1023 indicates that 2873 no measurement could be done for the subcarrier because it is 2874 out of the passband or that the attenuation is out of range to 2875 be represented. This parameter is applicable in loop 2876 diagnostic procedure and initialization. 2877 Each value in this array is 16 bits wide and is stored 2878 in big endian format." 2879 REFERENCE "ITU-T G.997.1, paragraph 7.5.1.18.4 (HLOGpsds) 2880 and paragraph 7.5.1.18.8 (HLOGpsus)" 2881 ::= { xdsl2SCStatusEntry 11 } 2883 xdsl2SCStatusQlnMt OBJECT-TYPE 2884 SYNTAX Unsigned32 2885 MAX-ACCESS read-only 2886 STATUS current 2887 DESCRIPTION 2888 "The number of symbols used to measure the Quiet Line Noise 2889 values on the respective transmission direction. This 2890 parameter should correspond to the value specified in the 2891 recommendation (e.g., the number of symbols in 1 second time 2892 interval for G.992.3). This parameter corresponds to 1 second 2893 in loop diagnostic procedure and should be updated in 2894 initialization " 2895 REFERENCE "ITU-T G.997.1, paragraph 7.5.1.19.1 (QLNMTds) 2896 and paragraph 7.5.1.19.3 (QLNMTus)" 2897 ::= { xdsl2SCStatusEntry 12 } 2899 xdsl2SCStatusQln OBJECT-TYPE 2900 SYNTAX OCTET STRING (SIZE(0..512)) 2901 UNITS "dBm/Hz" 2902 MAX-ACCESS read-only 2903 STATUS current 2904 DESCRIPTION 2905 "An array of up to 512 real Quiet Line Noise values in dBm/Hz 2906 for the respective transmission direction. It is designed for 2907 up to 512 (downstream) sub-carriers 2908 The number of utilized values on downstream direction depends 2909 on NSCds, and on upstream direction it depends on NSCus. This 2910 value is referred here as NSC. 2911 Each array entry represents the QLN(f = i*Df) value for a 2912 particular sub-carrier index i, (0 <= i < NSC). 2913 The QLN(f) is represented as ( -23-n(i)/2), with n(i) in the 2914 range 0 to 254. A special value n(i)=255 indicates that no 2915 measurement could be done for the subcarrier because it is out 2916 of the passband or that the noise PSD is out of range to be 2917 represented. 2918 This parameter is applicable in loop diagnostic procedure and 2919 initialization. Each value in this array is 8 bits wide." 2920 REFERENCE "ITU-T G.997.1, paragraph 7.5.1.19.2 (QLNpsds) 2921 and paragraph 7.5.1.19.4 (QLNpsus)" 2922 ::= { xdsl2SCStatusEntry 13 } 2924 xdsl2SCStatusLnAtten OBJECT-TYPE 2925 SYNTAX Unsigned32 2926 UNITS "0.1 dB" 2927 MAX-ACCESS read-only 2928 STATUS current 2929 DESCRIPTION 2930 "When referring to the downstream direction, it is the measured 2931 difference in the total power transmitted by the XTU-C and the 2932 total power received by the XTU-R over all sub-carriers during 2933 diagnostics mode. 2934 When referring to the upstream direction, it is the measured 2935 difference in the total power transmitted by the XTU-R and the 2936 total power received by the XTU-C over all sub-carriers during 2937 diagnostics mode. 2938 It ranges from 0 to 1270 units of 0.1 dB (Physical values are 2939 0 to 127 dB). A value of all 1's indicates the line 2940 attenuation is out of range to be represented. 2941 This object reflects the value of the parameter following the 2942 most recent DELT performed on the associated line. Once 2943 the DELT process is over, the parameter no longer changes 2944 until the row is deleted or a new DELT process is initiated. " 2945 REFERENCE "ITU-T G.997.1, paragraph 7.5.1.6 (LATNds) 2946 and paragraph 7.5.1.7 (LATNus)" 2947 ::= { xdsl2SCStatusEntry 14 } 2949 xdsl2SCStatusSigAtten OBJECT-TYPE 2950 SYNTAX Unsigned32 2951 UNITS "0.1 dB" 2952 MAX-ACCESS read-only 2953 STATUS current 2954 DESCRIPTION 2955 "When referring to the downstream direction, it is the measured 2956 difference in the total power transmitted by the 2957 XTU-C and the total power received by the XTU-R over all sub 2958 carriers during Showtime after the diagnostics mode. 2959 When referring to the upstream direction, it is the measured 2960 difference in the total power transmitted by the 2961 XTU-R and the total power received by the XTU-C over all sub 2962 carriers during Showtime after the diagnostics mode. 2963 It ranges from 0 to 1270 units of 0.1 dB (Physical values 2964 are 0 to 127 dB). A value of all 1's indicates the line 2965 attenuation is out of range to be represented. 2966 This object reflects the value of the parameter following the 2967 most recent DELT performed on the associated line. Once 2968 the DELT process is over, the parameter no longer changes 2969 until the row is deleted or a new DELT process is initiated. " 2970 REFERENCE "ITU-T G.997.1, paragraph 7.5.1.8 (SATNds) 2971 and paragraph 7.5.1.9 (SATNus)" 2972 ::= { xdsl2SCStatusEntry 15 } 2974 xdsl2SCStatusSnrMargin OBJECT-TYPE 2975 SYNTAX Integer32 2976 UNITS "0.1 dB" 2977 MAX-ACCESS read-only 2978 STATUS current 2979 DESCRIPTION 2980 "SNR Margin is the maximum increase in dB of the noise power 2981 received at the XTU (XTU-R on downstream direction and XATU-C 2982 on upstream direction), such that the BER requirements are met 2983 for all bearer channels received at the XTU. It ranges from 2984 -640 to 630 units of 0.1 dB (Physical values are -64 to 2985 63 dB). A value of all 1's indicates the SNR margin is 2986 out of range to be represented. 2987 This object reflects the value of the parameter following the 2988 most recent DELT performed on the associated line. Once 2989 the DELT process is over, the parameter no longer changes 2990 until the row is deleted or a new DELT process is initiated. " 2991 REFERENCE "ITU-T G.997.1, paragraph 7.5.1.10 (SNRMds) 2992 and paragraph 7.5.1.11 (SNRMus)" 2993 ::= { xdsl2SCStatusEntry 16 } 2995 xdsl2SCStatusAttainableRate OBJECT-TYPE 2996 SYNTAX Unsigned32 2997 UNITS "bits/second" 2998 MAX-ACCESS read-only 2999 STATUS current 3000 DESCRIPTION 3001 "Maximum Attainable Data Rate. The maximum net data rate 3002 currently attainable by the XTU-C transmitter and XTU-R 3003 receiver (when referring to downstream direction) or by the 3004 XTU-R transmitter and XTU-C receiver (when referring to 3005 upstream direction). Value is coded in bits/s. 3006 This object reflects the value of the parameter following the 3007 most recent DELT performed on the associated line. Once 3008 the DELT process is over, the parameter no longer changes 3009 until the row is deleted or a new DELT process is initiated. " 3010 REFERENCE "ITU-T G.997.1, paragraph 7.5.1.12 (ATTNDRds) 3011 and paragraph 7.5.1.13 (ATTNDRus)" 3012 ::= { xdsl2SCStatusEntry 17 } 3014 xdsl2SCStatusActAtp OBJECT-TYPE 3015 SYNTAX Integer32 3016 UNITS "0.1 dB" 3017 MAX-ACCESS read-only 3018 STATUS current 3019 DESCRIPTION 3020 "Actual Aggregate Transmit Power from the XTU (XTU-R on 3021 downstream direction and XTU-C on upstream direction), at the 3022 instant of measurement. It ranges from -310 to 310 units of 3023 0.1 dB (Physical values are -31 to 31 dBm). A value of all 3024 1's indicates the measurement is out of range to be 3025 represented. 3026 This object reflects the value of the parameter following the 3027 most recent DELT performed on the associated line. Once 3028 the DELT process is over, the parameter no longer changes 3029 until the row is deleted or a new DELT process is initiated. " 3030 REFERENCE "ITU-T G.997.1, paragraph 7.5.1.14 (ACTPSDds) 3031 and paragraph 7.5.1.15 (ACTPSDus)" 3032 ::= { xdsl2SCStatusEntry 18 } 3034 xdsl2SCStatusRowStatus OBJECT-TYPE 3035 SYNTAX RowStatus 3036 MAX-ACCESS read-write 3037 STATUS current 3038 DESCRIPTION 3039 "Row Status. The SNMP agent should create a row in this 3040 table for storing the results of a DELT performed on the 3041 associated line, if such a row does not already exist. 3042 The SNMP agent may have limited resources; therefore, if 3043 multiple rows co-exist in the table, it may fail to add 3044 new rows to the table or allocate memory resources for a new 3045 DELT process. If that occurs, the SNMP agent responds with 3046 either the value 'tableFull' or the value 3047 'noResources' (for xdsl2LineCmndConfLdsfFailReason 3048 object in xdsl2LineTable) 3049 The management system (the operator) may delete rows according 3050 to any scheme. E.g., after retrieving the results." 3051 ::= { xdsl2SCStatusEntry 19 } 3053 ------------------------------------------------ 3054 -- xdsl2LineInventoryTable -- 3055 ------------------------------------------------ 3056 xdsl2LineInventoryTable OBJECT-TYPE 3057 SYNTAX SEQUENCE OF Xdsl2LineInventoryEntry 3058 MAX-ACCESS not-accessible 3059 STATUS current 3060 DESCRIPTION 3061 "The table xdsl2LineInventoryTable contains inventory of DSL 3062 termination unit. 3063 The objects in this table are NOT persistent." 3064 ::= { xdsl2Inventory 1 } 3066 xdsl2LineInventoryEntry OBJECT-TYPE 3067 SYNTAX Xdsl2LineInventoryEntry 3068 MAX-ACCESS not-accessible 3069 STATUS current 3070 DESCRIPTION 3071 "The table xdsl2LineInventoryTable contains inventory of DSL 3072 termination unit. 3073 The index of this table is an interface index where the 3074 interface has an ifType of vdsl2(xxx)." 3075 INDEX { ifIndex, xdsl2LInvUnit } 3076 ::= { xdsl2LineInventoryTable 1 } 3078 Xdsl2LineInventoryEntry ::= 3079 SEQUENCE { 3080 xdsl2LInvUnit Xdsl2Unit, 3081 xdsl2LInvG994VendorId OCTET STRING, 3082 xdsl2LInvSystemVendorId OCTET STRING, 3083 xdsl2LInvVersionNumber OCTET STRING, 3084 xdsl2LInvSerialNumber OCTET STRING, 3085 xdsl2LInvSelfTestResult OCTET STRING, 3086 xdsl2LInvTransmissionCapabilities Xdsl2TransmissionModeType 3087 } 3089 xdsl2LInvUnit OBJECT-TYPE 3090 SYNTAX Xdsl2Unit 3091 MAX-ACCESS not-accessible 3092 STATUS current 3093 DESCRIPTION 3094 "The termination unit xtuc{1} or xtur{2}." 3095 ::= { xdsl2LineInventoryEntry 1 } 3097 xdsl2LInvG994VendorId OBJECT-TYPE 3098 SYNTAX OCTET STRING (SIZE(0..8)) 3099 MAX-ACCESS read-only 3100 STATUS current 3101 DESCRIPTION 3102 "The ATU G.994.1 Vendor ID as inserted in the G.994.1 CL/CLR 3103 message. It consists of 8 binary octets, including a country 3104 code followed by a (regionally allocated) provider code, as 3105 defined in Recommendation T.35." 3106 REFERENCE "ITU-T G.997.1, paragraph 7.4" 3107 ::= { xdsl2LineInventoryEntry 2 } 3109 xdsl2LInvSystemVendorId OBJECT-TYPE 3110 SYNTAX OCTET STRING (SIZE(0..8)) 3111 MAX-ACCESS read-only 3112 STATUS current 3113 DESCRIPTION 3114 "The ATU System Vendor ID (identifies the XTU system 3115 integrator) as inserted in the Overhead Messages (both XTUs 3116 for G.992.3 and G.992.4) or in the Embedded Operations 3117 Channel (only XTU-R in G.992.1 and G.992.2). It consists of 3118 8 binary octets, with same format as used for 3119 Xdsl2InvG994VendorId." 3120 REFERENCE "ITU-T G.997.1, paragraph 7.4" 3121 ::= { xdsl2LineInventoryEntry 3 } 3123 xdsl2LInvVersionNumber OBJECT-TYPE 3124 SYNTAX OCTET STRING (SIZE(0..16)) 3125 MAX-ACCESS read-only 3126 STATUS current 3127 DESCRIPTION 3128 "The XTU version number (vendor specific information) as 3129 inserted in the Overhead Messages (both XTUs for G.992.3 and 3130 G.992.4) or in the Embedded Operations Channel (only XTU-R in 3131 G.992.1 and G.992.2). It consists of up to 16 binary octets." 3132 REFERENCE "ITU-T G.997.1, paragraph 7.4" 3133 ::= { xdsl2LineInventoryEntry 4 } 3135 xdsl2LInvSerialNumber OBJECT-TYPE 3136 SYNTAX OCTET STRING (SIZE(0..32)) 3137 MAX-ACCESS read-only 3138 STATUS current 3139 DESCRIPTION 3140 "The XTU serial number (vendor specific information) as 3141 inserted in the Overhead Messages (both XTUs for G.992.3 and 3142 G.992.4) or in the Embedded Operations Channel (only XTU-R in 3143 G.992.1 and G.992.2). It is vendor specific information. It 3144 consists of up to 32 ASCII characters." 3146 REFERENCE "ITU-T G.997.1, paragraph 7.4" 3147 ::= { xdsl2LineInventoryEntry 5 } 3149 xdsl2LInvSelfTestResult OBJECT-TYPE 3150 SYNTAX OCTET STRING (SIZE(0..4)) 3151 MAX-ACCESS read-only 3152 STATUS current 3153 DESCRIPTION 3154 "The XTU self-test result, coded as a 32-bit integer. The 3155 most significant octet of this object is '0' if the self-test 3156 passed, and '1' if the self-test failed. The interpretation 3157 of the other octets is vendor discretionary." 3158 REFERENCE "ITU-T G.997.1, paragraph 7.4" 3159 ::= { xdsl2LineInventoryEntry 6 } 3161 xdsl2LInvTransmissionCapabilities OBJECT-TYPE 3162 SYNTAX Xdsl2TransmissionModeType 3163 MAX-ACCESS read-only 3164 STATUS current 3165 DESCRIPTION 3166 "The XTU transmission system capability list of the different 3167 coding types. It is coded in a bit-map representation with 1 3168 or more bits set. A bit set to '1' means that the XTU 3169 supports the respective coding. The value may be derived 3170 from the handshaking procedures defined in G.994.1. A set 3171 of xDSL line transmission modes, with one bit per mode." 3172 REFERENCE "ITU-T G.997.1, paragraph 7.4" 3173 ::= { xdsl2LineInventoryEntry 7 } 3175 ------------------------------------------------ 3176 -- xdsl2LineConfTemplateTable -- 3177 ------------------------------------------------ 3178 xdsl2LineConfTemplateTable OBJECT-TYPE 3179 SYNTAX SEQUENCE OF Xdsl2LineConfTemplateEntry 3180 MAX-ACCESS not-accessible 3181 STATUS current 3182 DESCRIPTION 3183 "The table xdsl2LineConfTemplateTable contains VDSL2/ADSL/ 3184 ADSL2 and ADSL2+ line configuration template. 3186 Entries in this table MUST be maintained in a 3187 persistent manner." 3188 ::= { xdsl2ProfileLine 1 } 3190 xdsl2LineConfTemplateEntry OBJECT-TYPE 3191 SYNTAX Xdsl2LineConfTemplateEntry 3192 MAX-ACCESS not-accessible 3193 STATUS current 3194 DESCRIPTION 3195 "The table xdsl2LineConfTemplateTable contains VDSL2/ADSL/ 3196 ADSL2 and ADSL2+ line configuration template. 3198 A default template with an index of 'DEFVAL' will 3199 always exist and its parameters will be set to vendor-specific 3200 values, unless otherwise specified in this document" 3201 INDEX { xdsl2LConfTempTemplateName } 3202 ::= { xdsl2LineConfTemplateTable 1 } 3204 Xdsl2LineConfTemplateEntry ::= 3205 SEQUENCE { 3206 xdsl2LConfTempTemplateName SnmpAdminString, 3207 xdsl2LConfTempLineProfile SnmpAdminString, 3208 xdsl2LConfTempChan1ConfProfile SnmpAdminString, 3209 xdsl2LConfTempChan1RaRatioDs Unsigned32, 3210 xdsl2LConfTempChan1RaRatioUs Unsigned32, 3211 xdsl2LConfTempChan2ConfProfile SnmpAdminString, 3212 xdsl2LConfTempChan2RaRatioDs Unsigned32, 3213 xdsl2LConfTempChan2RaRatioUs Unsigned32, 3214 xdsl2LConfTempChan3ConfProfile SnmpAdminString, 3215 xdsl2LConfTempChan3RaRatioDs Unsigned32, 3216 xdsl2LConfTempChan3RaRatioUs Unsigned32, 3217 xdsl2LConfTempChan4ConfProfile SnmpAdminString, 3218 xdsl2LConfTempChan4RaRatioDs Unsigned32, 3219 xdsl2LConfTempChan4RaRatioUs Unsigned32, 3220 xdsl2LConfTempRowStatus RowStatus 3221 } 3223 xdsl2LConfTempTemplateName OBJECT-TYPE 3224 SYNTAX SnmpAdminString (SIZE(1..32)) 3225 MAX-ACCESS not-accessible 3226 STATUS current 3227 DESCRIPTION 3228 "This object identifies a row in this table." 3229 REFERENCE "DSL Forum TR-90, paragraph 5.1.4" 3230 ::= { xdsl2LineConfTemplateEntry 1 } 3232 xdsl2LConfTempLineProfile OBJECT-TYPE 3233 SYNTAX SnmpAdminString (SIZE(1..32)) 3234 MAX-ACCESS read-create 3235 STATUS current 3236 DESCRIPTION 3237 "The value of this object identifies the row in the VDSL2/ADSL/ 3238 ADSL2 and ADSL2+ line configuration Profile Table, 3239 (Xdsl2LineConfProfileTable), 3240 which applies for this DSL line." 3242 REFERENCE "DSL Forum TR-90, paragraph 5.1.4" 3243 DEFVAL { "DEFVAL" } 3244 ::= { xdsl2LineConfTemplateEntry 2 } 3246 xdsl2LConfTempChan1ConfProfile OBJECT-TYPE 3247 SYNTAX SnmpAdminString (SIZE(1..32)) 3248 MAX-ACCESS read-create 3249 STATUS current 3250 DESCRIPTION 3251 "The value of this object identifies the row in the VDSL2/ADSL/ 3252 ADSL2 and ADSL2+ channel configuration Profile Table, 3253 (Xdsl2ChanConfProfileTable) that applies to DSL bearer 3254 channel #1. The channel profile name specified here must 3255 match the name of an existing row in the 3256 xdsl2ChConfProfileTable table." 3257 DEFVAL { "DEFVAL" } 3258 ::= { xdsl2LineConfTemplateEntry 3 } 3260 xdsl2LConfTempChan1RaRatioDs OBJECT-TYPE 3261 SYNTAX Unsigned32(0..100) 3262 UNITS "percents" 3263 MAX-ACCESS read-create 3264 STATUS current 3265 DESCRIPTION 3266 "Rate Adaptation Ratio. The ratio (in %) that should be taken 3267 into account for the bearer channel #1 when performing rate 3268 adaptation on Downstream. The ratio refers to the available 3269 data rate in excess of the Minimum Data Rate, summed over all 3270 bearer channels. Also, the 100 - 3271 Xdsl2ConfTemplateChan1RaRatioDs is the ratio of excess data 3272 rate to be assigned to all other bearer channels on Downstream 3273 direction. The sum of rate adaptation ratios over all bearers 3274 on the same direction shall be equal to 100%." 3275 REFERENCE "ITU-T G.997.1, paragraph 7.3.2.1" 3276 DEFVAL { 100 } 3277 ::= { xdsl2LineConfTemplateEntry 4 } 3279 xdsl2LConfTempChan1RaRatioUs OBJECT-TYPE 3280 SYNTAX Unsigned32(0..100) 3281 UNITS "percents" 3282 MAX-ACCESS read-create 3283 STATUS current 3284 DESCRIPTION 3285 "Rate Adaptation Ratio. The ratio (in %) that should be taken 3286 into account for the bearer channel #1 when performing rate 3287 adaptation on Upstream. The ratio refers to the available 3288 data rate in excess of the Minimum Data Rate, summed over all 3289 bearer channels. Also, the 3290 100 - Xdsl2ConfTemplateChan1RaRatioUs is the ratio of excess 3291 data rate to be assigned to all other bearer channels on 3292 Upstream direction. The sum of rate adaptation ratios over 3293 all bearers on the same direction shall be equal to 100 %." 3294 REFERENCE "ITU-T G.997.1, paragraph 7.3.2.1" 3295 DEFVAL { 100 } 3296 ::= { xdsl2LineConfTemplateEntry 5 } 3298 xdsl2LConfTempChan2ConfProfile OBJECT-TYPE 3299 SYNTAX SnmpAdminString (SIZE(0..32)) 3300 MAX-ACCESS read-create 3301 STATUS current 3302 DESCRIPTION 3303 "The value of this object identifies the row in the VDSL2/ADSL/ 3304 ADSL2 and ADSL2+ channel configuration Profile Table, 3305 (Xdsl2ChanConfProfileTable) that applies to DSL bearer 3306 channel #2. If the channel is unused, then the object is set 3307 to a zero length string. 3308 This object may be set to a zero length string only if 3309 xdsl2LConfTempChan3ConfProfile contains a zero length 3310 string." 3312 DEFVAL { "" } 3313 ::= { xdsl2LineConfTemplateEntry 6 } 3315 xdsl2LConfTempChan2RaRatioDs OBJECT-TYPE 3316 SYNTAX Unsigned32(0..100) 3317 UNITS "percents" 3318 MAX-ACCESS read-create 3319 STATUS current 3320 DESCRIPTION 3321 "Rate Adaptation Ratio. The ratio (in %) that should be taken 3322 into account for the bearer channel #2 when performing rate 3323 adaptation on Downstream. The ratio refers to the available 3324 data rate in excess of the Minimum Data Rate, summed over all 3325 bearer channels. Also, the 3326 100 - Xdsl2ConfTemplateChan2RaRatioDs is the ratio of excess 3327 data rate to be assigned to all other bearer channels on 3328 Downstream direction. The sum of rate adaptation ratios 3329 over all bearers on the same direction shall be equal to 3330 100%." 3331 REFERENCE "ITU-T G.997.1, paragraph 7.3.2.1" 3332 DEFVAL { 0 } 3333 ::= { xdsl2LineConfTemplateEntry 7 } 3335 xdsl2LConfTempChan2RaRatioUs OBJECT-TYPE 3336 SYNTAX Unsigned32(0..100) 3337 UNITS "percents" 3338 MAX-ACCESS read-create 3339 STATUS current 3340 DESCRIPTION 3341 "Rate Adaptation Ratio. The ratio (in %) that should be taken 3342 into account for the bearer channel #2 when performing rate 3343 adaptation on Upstream. The ratio refers to the available 3344 data rate in excess of the Minimum Data Rate, summed over all 3345 bearer channels. Also, the 3346 100 - Xdsl2ConfTemplateChan2RaRatioUs is the ratio of excess 3347 data rate to be assigned to all other bearer channels on 3348 Upstream direction. The sum of rate adaptation ratios over 3349 all bearers on the same direction shall be equal to 100 %." 3350 REFERENCE "ITU-T G.997.1, paragraph 7.3.2.1" 3351 DEFVAL { 0 } 3352 ::= { xdsl2LineConfTemplateEntry 8 } 3354 xdsl2LConfTempChan3ConfProfile OBJECT-TYPE 3355 SYNTAX SnmpAdminString (SIZE(0..32)) 3356 MAX-ACCESS read-create 3357 STATUS current 3358 DESCRIPTION 3359 "The value of this object identifies the row in the VDSL2/ADSL/ 3360 ADSL2 and ADSL2+ channel configuration Profile Table, 3361 (Xdsl2ChanConfProfileTable) that applies to DSL bearer 3362 channel #3. If the channel is unused, then the object is set 3363 to a zero length string. 3364 This object may be set to a zero length string only if 3365 xdsl2LConfTempChan4ConfProfile contains a zero length 3366 string. 3367 This object may be set to a non-zero length string only if 3368 xdsl2LConfTempChan2ConfProfile contains a non-zero length 3369 string." 3370 DEFVAL { "" } 3371 ::= { xdsl2LineConfTemplateEntry 9 } 3373 xdsl2LConfTempChan3RaRatioDs OBJECT-TYPE 3374 SYNTAX Unsigned32(0..100) 3375 UNITS "percents" 3376 MAX-ACCESS read-create 3377 STATUS current 3378 DESCRIPTION 3379 "Rate Adaptation Ratio. The ratio (in %) that should be taken 3380 into account for the bearer channel #3 when performing rate 3381 adaptation on Downstream. The ratio refers to the available 3382 data rate in excess of the Minimum Data Rate, summed over all 3383 bearer channels. Also, the 100 - 3384 Xdsl2ConfTemplateChan3RaRatioDs is the ratio of excess data 3385 rate to be assigned to all other bearer channels on Downstream 3386 direction. The sum of rate adaptation ratios over all bearers 3387 on the same direction shall be equal to 100%." 3388 REFERENCE "ITU-T G.997.1, paragraph 7.3.2.1" 3389 DEFVAL { 0 } 3390 ::= { xdsl2LineConfTemplateEntry 10 } 3392 xdsl2LConfTempChan3RaRatioUs OBJECT-TYPE 3393 SYNTAX Unsigned32(0..100) 3394 UNITS "percents" 3395 MAX-ACCESS read-create 3396 STATUS current 3397 DESCRIPTION 3398 "Rate Adaptation Ratio. The ratio (in %) that should be taken 3399 into account for the bearer channel #3 when performing rate 3400 adaptation on Upstream. The ratio refers to the available 3401 data rate in excess of the Minimum Data Rate, summed over all 3402 bearer channels. Also, the 3403 100 - Xdsl2ConfTemplateChan3RaRatioUs is the ratio of excess 3404 data rate to be assigned to all other bearer channels on 3405 Upstream direction. The sum of rate adaptation ratios over 3406 all bearers on the same direction shall be equal to 100%." 3407 REFERENCE "ITU-T G.997.1, paragraph 7.3.2.1" 3408 DEFVAL { 0 } 3409 ::= { xdsl2LineConfTemplateEntry 11 } 3411 xdsl2LConfTempChan4ConfProfile OBJECT-TYPE 3412 SYNTAX SnmpAdminString (SIZE(0..32)) 3413 MAX-ACCESS read-create 3414 STATUS current 3415 DESCRIPTION 3416 "The value of this object identifies the row in the VDSL2/ADSL/ 3417 ADSL2 and ADSL2+ channel configuration Profile Table, 3418 (Xdsl2ChanConfProfileTable) that applies to DSL bearer 3419 channel #4. If the channel is unused, then the object is set 3420 to a zero length string. 3421 This object may be set to a non-zero length string only if 3422 xdsl2LConfTempChan3ConfProfile contains a non-zero length 3423 string." 3424 DEFVAL { "" } 3425 ::= { xdsl2LineConfTemplateEntry 12 } 3427 xdsl2LConfTempChan4RaRatioDs OBJECT-TYPE 3428 SYNTAX Unsigned32(0..100) 3429 UNITS "percents" 3430 MAX-ACCESS read-create 3431 STATUS current 3432 DESCRIPTION 3433 "Rate Adaptation Ratio. The ratio (in %) that should be taken 3434 into account for the bearer channel #4 when performing rate 3435 adaptation on Downstream. The ratio refers to the available 3436 data rate in excess of the Minimum Data Rate, summed over all 3437 bearer channels. Also, the 100 - 3439 xdsl2LConfTempChan4RaRatioDs is the ratio of 3440 excess data rate to be assigned to all other bearer channels. 3441 The sum of rate adaptation ratios over all bearers on the same 3442 direction shall sum to 100%." 3443 REFERENCE "ITU-T G.997.1, paragraph 7.3.2.1" 3444 DEFVAL { 0 } 3445 ::= { xdsl2LineConfTemplateEntry 13 } 3447 xdsl2LConfTempChan4RaRatioUs OBJECT-TYPE 3448 SYNTAX Unsigned32(0..100) 3449 UNITS "percents" 3450 MAX-ACCESS read-create 3451 STATUS current 3452 DESCRIPTION 3453 "Rate Adaptation Ratio. The ratio (in %) that should be taken 3454 into account for the bearer channel #4 when performing rate 3455 adaptation on Upstream. The ratio refers to the available 3456 data rate in excess of the Minimum Data Rate, summed over 3457 all bearer channels. Also, the 100 - 3459 xdsl2LConfTempChan4RaRatioUs is the 3460 ratio of excess data rate to be assigned to all other bearer 3461 channels. The sum of rate adaptation ratios over all bearers 3462 on the same direction shall sum to 100%." 3463 REFERENCE "ITU-T G.997.1, paragraph 7.3.2.1" 3464 DEFVAL { 0 } 3465 ::= { xdsl2LineConfTemplateEntry 14 } 3467 xdsl2LConfTempRowStatus OBJECT-TYPE 3468 SYNTAX RowStatus 3469 MAX-ACCESS read-create 3470 STATUS current 3471 DESCRIPTION 3472 "This object is used to create a new row or to modify or 3473 delete an existing row in this table. 3475 A template is activated by setting this object to 'active'. 3476 When 'active' is set, the system will validate the template. 3477 Template modification is prohibited while this object is set 3478 to 'active'. 3480 Before a template can be deleted or taken out of service 3481 (by setting this object to 'destroy' or 'notInService'), 3482 it must be first unreferenced from all associated 3483 lines." 3484 ::= { xdsl2LineConfTemplateEntry 15 } 3486 ------------------------------------------ 3487 -- xdsl2LineConfProfTable -- 3488 ------------------------------------------ 3489 xdsl2LineConfProfTable OBJECT-TYPE 3490 SYNTAX SEQUENCE OF Xdsl2LineConfProfEntry 3491 MAX-ACCESS not-accessible 3492 STATUS current 3493 DESCRIPTION 3494 "The table xdsl2LineConfProfTable contains VDSL2/ADSL/ 3495 ADSL2 and ADSL2+ line configuration profile. 3497 Entries in this table MUST be maintained in a 3498 persistent manner." 3499 ::= { xdsl2ProfileLine 2 } 3501 xdsl2LineConfProfEntry OBJECT-TYPE 3502 SYNTAX Xdsl2LineConfProfEntry 3503 MAX-ACCESS not-accessible 3504 STATUS current 3505 DESCRIPTION 3506 "The table xdsl2LineConfProfTable contains VDSL2/ADSL/ 3507 ADSL2 and ADSL2+ line configuration profile. 3509 A default profile with an index of 'DEFVAL' will 3510 always exist and its parameters will be set to vendor-specific 3511 values, unless otherwise specified in this document" 3512 INDEX { xdsl2LConfProfProfileName } 3513 ::= { xdsl2LineConfProfTable 1 } 3515 Xdsl2LineConfProfEntry ::= 3516 SEQUENCE { 3517 xdsl2LConfProfProfileName SnmpAdminString, 3518 xdsl2LConfProfScMaskDs Xdsl2ScMaskDs, 3519 xdsl2LConfProfScMaskUs Xdsl2ScMaskUs, 3520 xdsl2LConfProfRfiBandsDs Xdsl2RfiDs, 3521 xdsl2LConfProfRaModeDs Xdsl2RaMode, 3522 xdsl2LConfProfRaModeUs Xdsl2RaMode, 3523 xdsl2LConfProfRaUsNrmDs Unsigned32, 3524 xdsl2LConfProfRaUsNrmUs Unsigned32, 3525 xdsl2LConfProfRaUsTimeDs Unsigned32, 3526 xdsl2LConfProfRaUsTimeUs Unsigned32, 3527 xdsl2LConfProfRaDsNrmsDs Unsigned32, 3528 xdsl2LConfProfRaDsNrmsUs Unsigned32, 3529 xdsl2LConfProfRaDsTimeDs Unsigned32, 3530 xdsl2LConfProfRaDsTimeUs Unsigned32, 3531 xdsl2LConfProfTargetSnrmDs Unsigned32, 3532 xdsl2LConfProfTargetSnrmUs Unsigned32, 3533 xdsl2LConfProfMaxSnrmDs Unsigned32, 3534 xdsl2LConfProfMaxSnrmUs Unsigned32, 3535 xdsl2LConfProfMinSnrmDs Unsigned32, 3536 xdsl2LConfProfMinSnrmUs Unsigned32, 3537 xdsl2LConfProfMsgMinUs Unsigned32, 3538 xdsl2LConfProfMsgMinDs Unsigned32, 3539 xdsl2LConfProfXtuTransSysEna Xdsl2TransmissionModeType, 3540 xdsl2LConfProfPmMode Xdsl2LConfProfPmMode, 3541 xdsl2LConfProfL0Time Unsigned32, 3542 xdsl2LConfProfL2Time Unsigned32, 3543 xdsl2LConfProfL2Atpr Unsigned32, 3544 xdsl2LConfProfL2Atprt Unsigned32, 3545 xdsl2LConfProfRowStatus RowStatus 3546 } 3548 xdsl2LConfProfProfileName OBJECT-TYPE 3549 SYNTAX SnmpAdminString (SIZE(1..32)) 3550 MAX-ACCESS not-accessible 3551 STATUS current 3552 DESCRIPTION 3553 "This object identifies a row in this table." 3554 ::= { xdsl2LineConfProfEntry 1 } 3556 xdsl2LConfProfScMaskDs OBJECT-TYPE 3557 SYNTAX Xdsl2ScMaskDs 3558 MAX-ACCESS read-create 3559 STATUS current 3560 DESCRIPTION 3561 "Sub-carriers mask. A bitmap of 4096 bits that allows masking 3562 up to 4096 downstream sub-carriers, depending on NSCds. If 3563 bit i (0 <= i < NSCds) is set to '1', the respective 3564 downstream sub-carrier i is masked, and if set to '0', the 3565 respective sub-carrier is unmasked. Note that there should 3566 always be unmasked sub-carriers (i.e., the object cannot be 3567 all 1's). Also note that if NSCds < 4096, all bits 3568 i (NSCds i <= 4096) should be set to '1'." 3569 REFERENCE "ITU-T G.997.1, paragraph 7.3.1.2.6" 3570 ::= { xdsl2LineConfProfEntry 2 } 3572 xdsl2LConfProfScMaskUs OBJECT-TYPE 3573 SYNTAX Xdsl2ScMaskUs 3574 MAX-ACCESS read-create 3575 STATUS current 3576 DESCRIPTION 3577 "Sub-carriers mask. A bitmap of 4096 bits that allows masking 3578 up to 4096 downstream sub-carriers, depending on NSCds. If 3579 bit i (0 <= i < NSCus) is set to '1', the respective 3580 upstream sub-carrier i is masked, and if set to '0', the 3581 respective sub-carrier is unmasked. Note that there 3582 should always be unmasked sub-carriers (i.e., the object 3583 cannot be all 1's). Also note that if NSCus < 3584 4096, all bits i (NSCus < i <= 4096) should be set to '1'." 3585 REFERENCE "ITU-T G.997.1, paragraph 7.3.1.2.7" 3586 ::= { xdsl2LineConfProfEntry 3 } 3588 xdsl2LConfProfRfiBandsDs OBJECT-TYPE 3589 SYNTAX Xdsl2RfiDs 3590 MAX-ACCESS read-create 3591 STATUS current 3592 DESCRIPTION 3593 "The subset of downstream PSD mask breakpoints that shall be 3594 used to notch an RFI band. 3595 The specific interpolation around these points is defined in 3596 G.992.5. It is a bitmap of 4096 bits that allows referring to 3597 up to 4096 downstream sub-carriers, depending on NSCds. If 3598 bit i (0 <= i < NSCds) is set to '1', the respective 3599 downstream sub-carrier i is part of a notch filter, and if 3600 set to '0', the respective sub-carrier is not 3601 part of a notch filter. 3602 This information complements the specification provided by 3603 xdsl2LconfProfPsdMaskDs. 3604 Note that if NSCds < 4096, all bits i (NSCds= 1 for one or more bearer channels OR 5218 LOS >= 1 OR SEF >=1 OR LPR >= 1 5219 xtu-r: FEBE >= 1 for one or more bearer channels OR 5220 LOS-FE >=1 OR RDI >=1 OR LPR-FE >=1 . 5221 This parameter is inhibited during UAS." 5222 REFERENCE "ITU-T G.997.1, paragraph 7.2.1" 5223 ::= { xdsl2PMLineCurrEntry 6 } 5225 xdsl2PMLCurr15MSes OBJECT-TYPE 5226 SYNTAX Counter32 5227 UNITS "seconds" 5228 MAX-ACCESS read-only 5229 STATUS current 5230 DESCRIPTION 5231 "Count of seconds during this interval that there was: 5232 xtu-c: (CRC-8 summed over all bearer channels) >= 18 OR 5233 LOS >= 1 OR SEF >= 1 OR LPR >= 1 5234 xtu-r: (FEBE summed over all bearer channels) >= 18 OR 5235 LOS-FE >= 1 OR RDI >= 1 OR LPR-FE >= 1 . 5236 This parameter is inhibited during UAS." 5237 REFERENCE "ITU-T G.997.1, paragraph 7.2.1" 5238 ::= { xdsl2PMLineCurrEntry 7 } 5240 xdsl2PMLCurr15MLoss OBJECT-TYPE 5241 SYNTAX Counter32 5242 UNITS "seconds" 5243 MAX-ACCESS read-only 5244 STATUS current 5245 DESCRIPTION 5246 "Count of seconds during this interval that there was LOS (or 5247 LOS-FE for xtu-r)." 5248 REFERENCE "ITU-T G.997.1, paragraph 7.2.1" 5249 ::= { xdsl2PMLineCurrEntry 8 } 5251 xdsl2PMLCurr15MUas OBJECT-TYPE 5252 SYNTAX Counter32 5253 UNITS "seconds" 5254 MAX-ACCESS read-only 5255 STATUS current 5256 DESCRIPTION 5257 "Count of seconds in Unavailability State during this 5258 interval. Unavailability begins at the onset of 10 5259 contiguous severely-errored seconds, and ends at the 5260 onset of 10 contiguous seconds with no severely-errored 5261 seconds." 5262 REFERENCE "ITU-T G.997.1, paragraph 7.2.1" 5263 ::= { xdsl2PMLineCurrEntry 9 } 5265 xdsl2PMLCurr1DayValidIntervals OBJECT-TYPE 5266 SYNTAX Unsigned32 5267 MAX-ACCESS read-only 5268 STATUS current 5269 DESCRIPTION 5270 "Valid intervals." 5271 ::= { xdsl2PMLineCurrEntry 10 } 5273 xdsl2PMLCurr1DayInvalidIntervals OBJECT-TYPE 5274 SYNTAX Unsigned32 5275 MAX-ACCESS read-only 5276 STATUS current 5277 DESCRIPTION 5278 "Invalid intervals." 5279 ::= { xdsl2PMLineCurrEntry 11 } 5281 xdsl2PMLCurr1DayTimeElapsed OBJECT-TYPE 5282 SYNTAX HCPerfTimeElapsed 5283 UNITS "seconds" 5284 MAX-ACCESS read-only 5285 STATUS current 5286 DESCRIPTION 5287 "Total elapsed seconds in this interval." 5288 ::= { xdsl2PMLineCurrEntry 12 } 5290 xdsl2PMLCurr1DayFecs OBJECT-TYPE 5291 SYNTAX Counter32 5292 UNITS "seconds" 5293 MAX-ACCESS read-only 5294 STATUS current 5295 DESCRIPTION 5296 "Count of seconds during this interval that there was at least 5297 one FEC correction event for one or more bearer channels in 5298 this line. This parameter is inhibited during UAS or SES." 5299 REFERENCE "ITU-T G.997.1, paragraph 7.2.1" 5300 ::= { xdsl2PMLineCurrEntry 13 } 5302 xdsl2PMLCurr1DayEs OBJECT-TYPE 5303 SYNTAX Counter32 5304 UNITS "seconds" 5305 MAX-ACCESS read-only 5306 STATUS current 5307 DESCRIPTION 5308 "Count of seconds during this interval that there was: 5309 xtu-c: CRC-8 >= 1 for one or more bearer channels OR 5310 LOS >= 1 OR SEF >= 1 OR LPR >= 1 5311 xtu-r: FEBE >= 1 for one or more bearer channels OR 5312 LOS-FE >= 1 OR RDI >= 1 OR LPR-FE >= 1. 5313 This parameter is inhibited during UAS." 5315 REFERENCE "ITU-T G.997.1, paragraph 7.2.1" 5316 ::= { xdsl2PMLineCurrEntry 14 } 5318 xdsl2PMLCurr1DaySes OBJECT-TYPE 5319 SYNTAX Counter32 5320 UNITS "seconds" 5321 MAX-ACCESS read-only 5322 STATUS current 5323 DESCRIPTION 5324 "Count of seconds during this interval that there was: 5325 xtu-c: (CRC-8 summed over all bearer channels) >= 18 OR 5326 LOS >= 1 OR SEF >= 1 OR LPR >= 1 5327 xtu-r: (FEBE summed over all bearer channels) >= 18 OR 5328 LOS-FE >= 1 OR RDI >= 1 OR LPR-FE >= 1 5329 This parameter is inhibited during UAS." 5330 REFERENCE "ITU-T G.997.1, paragraph 7.2.1" 5331 ::= { xdsl2PMLineCurrEntry 15 } 5333 xdsl2PMLCurr1DayLoss OBJECT-TYPE 5334 SYNTAX Counter32 5335 UNITS "seconds" 5336 MAX-ACCESS read-only 5337 STATUS current 5338 DESCRIPTION 5339 "Count of seconds during this interval that there was LOS (or 5340 LOS-FE for xtu-r)." 5341 REFERENCE "ITU-T G.997.1, paragraph 7.2.1" 5342 ::= { xdsl2PMLineCurrEntry 16 } 5344 xdsl2PMLCurr1DayUas OBJECT-TYPE 5345 SYNTAX Counter32 5346 UNITS "seconds" 5347 MAX-ACCESS read-only 5348 STATUS current 5349 DESCRIPTION 5350 "Count of seconds in Unavailability State during this interval. 5351 Unavailability begins at the onset of 10 contiguous severely 5352 -errored seconds, and ends at the onset of 10 contiguous 5353 seconds with no severely-errored seconds." 5354 REFERENCE "ITU-T G.997.1, paragraph 7.2.1" 5355 ::= { xdsl2PMLineCurrEntry 17 } 5357 ------------------------------------------------ 5358 -- PM line init current counters -- 5359 ------------------------------------------------ 5361 xdsl2PMLineCurrInitTable OBJECT-TYPE 5362 SYNTAX SEQUENCE OF Xdsl2PMLineCurrInitEntry 5363 MAX-ACCESS not-accessible 5364 STATUS current 5365 DESCRIPTION 5366 "The table xdsl2PMLineCurrInitTable contains current 5367 initialization counters of DSL line. The objects in 5368 this table are NOT persistent." 5369 ::= { xdsl2PMLine 2 } 5371 xdsl2PMLineCurrInitEntry OBJECT-TYPE 5372 SYNTAX Xdsl2PMLineCurrInitEntry 5373 MAX-ACCESS not-accessible 5374 STATUS current 5375 DESCRIPTION 5376 "The table xdsl2PMLineCurrInitTable contains current 5377 initialization counters of DSL line. 5378 The index of this table is an interface index where the 5379 interface has an ifType of vdsl2(xxx) and the termination 5380 unit." 5381 INDEX { ifIndex } 5382 ::= { xdsl2PMLineCurrInitTable 1 } 5384 Xdsl2PMLineCurrInitEntry ::= 5385 SEQUENCE { 5386 xdsl2PMLCurrInit15MTimeElapsed Unsigned32, 5387 xdsl2PMLCurrInit15MFullInits Unsigned32, 5388 xdsl2PMLCurrInit15MFailedFullInits Unsigned32, 5389 xdsl2PMLCurrInit15MShortInits Unsigned32, 5390 xdsl2PMLCurrInit15MFailedShortInits Unsigned32, 5391 xdsl2PMLCurrInit1DayTimeElapsed Unsigned32, 5392 xdsl2PMLCurrInit1DayFullInits Unsigned32, 5393 xdsl2PMLCurrInit1DayFailedFullInits Unsigned32, 5394 xdsl2PMLCurrInit1DayShortInits Unsigned32, 5395 xdsl2PMLCurrInit1DayFailedShortInits Unsigned32 5396 } 5398 xdsl2PMLCurrInit15MTimeElapsed OBJECT-TYPE 5399 SYNTAX Unsigned32 5400 UNITS "seconds" 5401 MAX-ACCESS read-only 5402 STATUS current 5403 DESCRIPTION 5404 "Total elapsed seconds in this interval." 5405 ::= { xdsl2PMLineCurrInitEntry 1 } 5407 xdsl2PMLCurrInit15MFullInits OBJECT-TYPE 5408 SYNTAX Unsigned32 5409 MAX-ACCESS read-only 5410 STATUS current 5411 DESCRIPTION 5412 "Count of full initializations attempted on the line 5413 (successful and failed) during this interval." 5414 REFERENCE "ITU-T G.997.1, paragraph 7.2.1" 5415 ::= { xdsl2PMLineCurrInitEntry 2 } 5417 xdsl2PMLCurrInit15MFailedFullInits OBJECT-TYPE 5418 SYNTAX Unsigned32 5419 MAX-ACCESS read-only 5420 STATUS current 5421 DESCRIPTION 5422 "Count of failed full initializations on the line during this 5423 interval." 5424 REFERENCE "ITU-T G.997.1, paragraph 7.2.1" 5425 ::= { xdsl2PMLineCurrInitEntry 3 } 5427 xdsl2PMLCurrInit15MShortInits OBJECT-TYPE 5428 SYNTAX Unsigned32 5429 MAX-ACCESS read-only 5430 STATUS current 5431 DESCRIPTION 5432 "Count of short initializations attempted on the line 5433 (successful and failed) during this interval." 5434 REFERENCE "ITU-T G.997.1, paragraph 7.2.1" 5435 ::= { xdsl2PMLineCurrInitEntry 4 } 5437 xdsl2PMLCurrInit15MFailedShortInits OBJECT-TYPE 5438 SYNTAX Unsigned32 5439 MAX-ACCESS read-only 5440 STATUS current 5441 DESCRIPTION 5442 "Count of failed short initializations on the line during this 5443 interval." 5444 REFERENCE "ITU-T G.997.1, paragraph 7.2.1" 5445 ::= { xdsl2PMLineCurrInitEntry 5 } 5447 xdsl2PMLCurrInit1DayTimeElapsed OBJECT-TYPE 5448 SYNTAX Unsigned32 5449 UNITS "seconds" 5450 MAX-ACCESS read-only 5451 STATUS current 5452 DESCRIPTION 5453 "Total elapsed seconds in this interval." 5454 ::= { xdsl2PMLineCurrInitEntry 6 } 5456 xdsl2PMLCurrInit1DayFullInits OBJECT-TYPE 5457 SYNTAX Unsigned32 5458 MAX-ACCESS read-only 5459 STATUS current 5460 DESCRIPTION 5461 "Count of full initializations attempted on the line 5462 (successful and failed) during this interval." 5463 REFERENCE "ITU-T G.997.1, paragraph 7.2.1" 5464 ::= { xdsl2PMLineCurrInitEntry 7 } 5466 xdsl2PMLCurrInit1DayFailedFullInits OBJECT-TYPE 5467 SYNTAX Unsigned32 5468 MAX-ACCESS read-only 5469 STATUS current 5470 DESCRIPTION 5471 "Count of failed full initializations on the line during this 5472 interval." 5473 REFERENCE "ITU-T G.997.1, paragraph 7.2.1" 5474 ::= { xdsl2PMLineCurrInitEntry 8 } 5476 xdsl2PMLCurrInit1DayShortInits OBJECT-TYPE 5477 SYNTAX Unsigned32 5478 MAX-ACCESS read-only 5479 STATUS current 5480 DESCRIPTION 5481 "Count of short initializations attempted on the line 5482 (successful and failed) during this interval." 5483 REFERENCE "ITU-T G.997.1, paragraph 7.2.1" 5484 ::= { xdsl2PMLineCurrInitEntry 9 } 5486 xdsl2PMLCurrInit1DayFailedShortInits OBJECT-TYPE 5487 SYNTAX Unsigned32 5488 MAX-ACCESS read-only 5489 STATUS current 5490 DESCRIPTION 5491 "Count of failed short initializations on the line during this 5492 interval." 5493 REFERENCE "ITU-T G.997.1, paragraph 7.2.1" 5494 ::= { xdsl2PMLineCurrInitEntry 10 } 5496 ------------------------------------------- 5497 -- PM line history 15 Minutes -- 5498 ------------------------------------------- 5499 xdsl2PMLineHist15MinTable OBJECT-TYPE 5500 SYNTAX SEQUENCE OF Xdsl2PMLineHist15MinEntry 5501 MAX-ACCESS not-accessible 5502 STATUS current 5503 DESCRIPTION 5504 "The table xdsl2PMLineHist15MinTable contains PM line history 5505 for 15min intervals of DSL line. The objects in this table 5506 are NOT persistent." 5507 ::= { xdsl2PMLine 3 } 5509 xdsl2PMLineHist15MinEntry OBJECT-TYPE 5510 SYNTAX Xdsl2PMLineHist15MinEntry 5511 MAX-ACCESS not-accessible 5512 STATUS current 5513 DESCRIPTION 5514 "The table xdsl2PMLineHist15MinTable contains PM line history 5515 for 15min intervals of DSL line. 5516 The index of this table is an interface index where the 5517 interface has an ifType of vdsl2(xxx), the termination unit, 5518 and an interval number." 5519 INDEX { ifIndex, 5520 xdsl2PMLHist15MUnit, 5521 xdsl2PMLHist15MInterval } 5522 ::= { xdsl2PMLineHist15MinTable 1 } 5524 Xdsl2PMLineHist15MinEntry ::= 5525 SEQUENCE { 5526 xdsl2PMLHist15MUnit Xdsl2Unit, 5527 xdsl2PMLHist15MInterval Unsigned32, 5528 xdsl2PMLHist15MMonitoredTime Unsigned32, 5529 xdsl2PMLHist15MFecs Counter32, 5530 xdsl2PMLHist15MEs Counter32, 5531 xdsl2PMLHist15MSes Counter32, 5532 xdsl2PMLHist15MLoss Counter32, 5533 xdsl2PMLHist15MUas Counter32, 5534 xdsl2PMLHist15MValidInterval TruthValue 5535 } 5537 xdsl2PMLHist15MUnit OBJECT-TYPE 5538 SYNTAX Xdsl2Unit 5539 MAX-ACCESS not-accessible 5540 STATUS current 5541 DESCRIPTION 5542 "The termination unit xtuc{1} or xtur{2}." 5543 ::= { xdsl2PMLineHist15MinEntry 1 } 5545 xdsl2PMLHist15MInterval OBJECT-TYPE 5546 SYNTAX Unsigned32 (1..96) 5547 MAX-ACCESS not-accessible 5548 STATUS current 5549 DESCRIPTION 5550 "The interval number." 5551 ::= { xdsl2PMLineHist15MinEntry 2 } 5553 xdsl2PMLHist15MMonitoredTime OBJECT-TYPE 5554 SYNTAX Unsigned32 5555 UNITS "seconds" 5556 MAX-ACCESS read-only 5557 STATUS current 5558 DESCRIPTION 5559 "Total seconds monitored in this interval." 5560 ::= { xdsl2PMLineHist15MinEntry 3 } 5562 xdsl2PMLHist15MFecs OBJECT-TYPE 5563 SYNTAX Counter32 5564 UNITS "seconds" 5565 MAX-ACCESS read-only 5566 STATUS current 5567 DESCRIPTION 5568 "Count of seconds during this interval that there was at least 5569 one FEC correction event for one or more bearer channels in 5570 this line. This parameter is inhibited during UAS or SES." 5571 REFERENCE "ITU-T G.997.1, paragraph 7.2.1" 5572 ::= { xdsl2PMLineHist15MinEntry 4 } 5574 xdsl2PMLHist15MEs OBJECT-TYPE 5575 SYNTAX Counter32 5576 UNITS "seconds" 5577 MAX-ACCESS read-only 5578 STATUS current 5579 DESCRIPTION 5580 "Count of seconds during this interval that there was: 5581 xtu-c: CRC-8 >= 1 for one or more bearer channels OR 5582 LOS >= 1 OR SEF >= 1 OR LPR >= 1 5583 xtu-r: FEBE >= 1 for one or more bearer channels OR 5584 LOS-FE >= 1 OR RDI >= 1 OR LPR-FE >= 1. 5585 This parameter is inhibited during UAS." 5586 REFERENCE "ITU-T G.997.1, paragraph 7.2.1" 5587 ::= { xdsl2PMLineHist15MinEntry 5 } 5589 xdsl2PMLHist15MSes OBJECT-TYPE 5590 SYNTAX Counter32 5591 UNITS "seconds" 5592 MAX-ACCESS read-only 5593 STATUS current 5594 DESCRIPTION 5595 "Count of seconds during this interval that there was: 5596 xtu-c: (CRC-8 summed over all bearer channels) >= 18 OR 5597 LOS >= 1 OR SEF >= 1 OR LPR >= 1 5598 xtu-r: (FEBE summed over all bearer channels) >= 18 OR 5599 LOS-FE >= 1 OR RDI >= 1 OR LPR-FE >= 1. 5600 This parameter is inhibited during UAS." 5602 REFERENCE "ITU-T G.997.1, paragraph 7.2.1" 5603 ::= { xdsl2PMLineHist15MinEntry 6 } 5605 xdsl2PMLHist15MLoss OBJECT-TYPE 5606 SYNTAX Counter32 5607 UNITS "seconds" 5608 MAX-ACCESS read-only 5609 STATUS current 5610 DESCRIPTION 5611 "Count of seconds during this interval that there was LOS (or 5612 LOS-FE for xtu-r)." 5613 REFERENCE "ITU-T G.997.1, paragraph 7.2.1" 5614 ::= { xdsl2PMLineHist15MinEntry 7 } 5616 xdsl2PMLHist15MUas OBJECT-TYPE 5617 SYNTAX Counter32 5618 UNITS "seconds" 5619 MAX-ACCESS read-only 5620 STATUS current 5621 DESCRIPTION 5622 "Count of seconds in Unavailability State during this interval. 5623 Unavailability begins at the onset of 10 contiguous severely 5624 -errored seconds, and ends at the onset of 10 contiguous 5625 seconds with no severely-errored seconds." 5626 REFERENCE "ITU-T G.997.1, paragraph 7.2.1" 5627 ::= { xdsl2PMLineHist15MinEntry 8 } 5629 xdsl2PMLHist15MValidInterval OBJECT-TYPE 5630 SYNTAX TruthValue 5631 MAX-ACCESS read-only 5632 STATUS current 5633 DESCRIPTION 5634 "This variable indicates if the data for this interval is 5635 valid." 5636 ::= { xdsl2PMLineHist15MinEntry 9 } 5638 --------------------------------------- 5639 -- PM line history 1 Day -- 5640 --------------------------------------- 5641 xdsl2PMLineHist1DayTable OBJECT-TYPE 5642 SYNTAX SEQUENCE OF Xdsl2PMLineHist1DayEntry 5643 MAX-ACCESS not-accessible 5644 STATUS current 5645 DESCRIPTION 5646 "The table xdsl2PMLineHist1DayTable contains PM line history 5647 for 24 hours intervals of DSL line. The objects in this 5648 table are NOT persistent." 5649 ::= { xdsl2PMLine 4 } 5651 xdsl2PMLineHist1DayEntry OBJECT-TYPE 5652 SYNTAX Xdsl2PMLineHist1DayEntry 5653 MAX-ACCESS not-accessible 5654 STATUS current 5655 DESCRIPTION 5656 "The table xdsl2PMLineHist1DayTable contains PM line history 5657 for 24 hours intervals of DSL line. 5658 The indexes of this table is an interface index where the 5659 interface has an ifType of vdsl2(xxx), the termination unit 5660 and an interval number." 5662 INDEX { ifIndex, 5663 xdsl2PMLHist1DUnit, 5664 xdsl2PMLHist1DInterval } 5665 ::= { xdsl2PMLineHist1DayTable 1 } 5667 Xdsl2PMLineHist1DayEntry ::= 5668 SEQUENCE { 5669 xdsl2PMLHist1DUnit Xdsl2Unit, 5670 xdsl2PMLHist1DInterval Unsigned32, 5671 xdsl2PMLHist1DMonitoredTime Unsigned32, 5672 xdsl2PMLHist1DFecs Counter32, 5673 xdsl2PMLHist1DEs Counter32, 5674 xdsl2PMLHist1DSes Counter32, 5675 xdsl2PMLHist1DLoss Counter32, 5676 xdsl2PMLHist1DUas Counter32, 5677 xdsl2PMLHist1DValidInterval TruthValue 5678 } 5680 xdsl2PMLHist1DUnit OBJECT-TYPE 5681 SYNTAX Xdsl2Unit 5682 MAX-ACCESS not-accessible 5683 STATUS current 5684 DESCRIPTION 5685 "The termination unit." 5686 ::= { xdsl2PMLineHist1DayEntry 1 } 5688 xdsl2PMLHist1DInterval OBJECT-TYPE 5689 SYNTAX Unsigned32 (1..30) 5690 MAX-ACCESS not-accessible 5691 STATUS current 5692 DESCRIPTION 5693 "The interval number." 5694 ::= { xdsl2PMLineHist1DayEntry 2 } 5696 xdsl2PMLHist1DMonitoredTime OBJECT-TYPE 5697 SYNTAX Unsigned32 5698 UNITS "seconds" 5699 MAX-ACCESS read-only 5700 STATUS current 5701 DESCRIPTION 5702 "Total seconds monitored in this interval." 5703 ::= { xdsl2PMLineHist1DayEntry 3 } 5705 xdsl2PMLHist1DFecs OBJECT-TYPE 5706 SYNTAX Counter32 5707 UNITS "seconds" 5708 MAX-ACCESS read-only 5709 STATUS current 5710 DESCRIPTION 5711 "Count of seconds during this interval that there was at least 5712 one FEC correction event for one or more bearer channels in 5713 this line. This parameter is inhibited during UAS or SES." 5714 REFERENCE "ITU-T G.997.1, paragraph 7.2.1" 5715 ::= { xdsl2PMLineHist1DayEntry 4 } 5717 xdsl2PMLHist1DEs OBJECT-TYPE 5718 SYNTAX Counter32 5719 UNITS "seconds" 5720 MAX-ACCESS read-only 5721 STATUS current 5722 DESCRIPTION 5723 "Count of seconds during this interval that there was: 5724 xtu-c: CRC-8 >= 1 for one or more bearer channels OR 5725 LOS >= 1 OR SEF >= 1 OR LPR >= 1 5726 xtu-r: FEBE >= 1 for one or more bearer channels OR 5727 LOS-FE >= 1 OR RDI >= 1 OR LPR-FE >= 1. 5728 This parameter is inhibited during UAS." 5729 REFERENCE "ITU-T G.997.1, paragraph 7.2.1" 5730 ::= { xdsl2PMLineHist1DayEntry 5 } 5732 xdsl2PMLHist1DSes OBJECT-TYPE 5733 SYNTAX Counter32 5734 UNITS "seconds" 5735 MAX-ACCESS read-only 5736 STATUS current 5737 DESCRIPTION 5738 "Count of seconds during this interval that there was: 5739 xtu-c: (CRC-8 summed over all bearer channels) >= 18 OR 5740 LOS >= 1 OR SEF >> 1 OR LPR >= 1 5741 xtu-r: (FEBE summed over all bearer channels) >= 18 OR 5742 LOS-FE >= 1 OR RDI >= 1 OR LPR-FE >= 1. 5743 This parameter is inhibited during UAS." 5745 REFERENCE "ITU-T G.997.1, paragraph 7.2.1" 5746 ::= { xdsl2PMLineHist1DayEntry 6 } 5748 xdsl2PMLHist1DLoss OBJECT-TYPE 5749 SYNTAX Counter32 5750 UNITS "seconds" 5751 MAX-ACCESS read-only 5752 STATUS current 5753 DESCRIPTION 5754 "Count of seconds during this interval that there was LOS (or 5755 LOS-FE for xtu-r)." 5756 REFERENCE "ITU-T G.997.1, paragraph 7.2.1" 5757 ::= { xdsl2PMLineHist1DayEntry 7 } 5759 xdsl2PMLHist1DUas OBJECT-TYPE 5760 SYNTAX Counter32 5761 UNITS "seconds" 5762 MAX-ACCESS read-only 5763 STATUS current 5764 DESCRIPTION 5765 "Count of seconds in Unavailability State during this interval. 5766 Unavailability begins at the onset of 10 contiguous severely 5767 -errored seconds, and ends at the onset of 10 contiguous 5768 seconds with no severely-errored seconds." 5769 REFERENCE "ITU-T G.997.1, paragraph 7.2.1" 5770 ::= { xdsl2PMLineHist1DayEntry 8 } 5772 xdsl2PMLHist1DValidInterval OBJECT-TYPE 5773 SYNTAX TruthValue 5774 MAX-ACCESS read-only 5775 STATUS current 5776 DESCRIPTION 5777 "This variable indicates if the data for this interval is 5778 valid." 5779 ::= { xdsl2PMLineHist1DayEntry 9 } 5781 ------------------------------------------- 5782 -- PM line init history 15 Minutes -- 5783 ------------------------------------------- 5785 xdsl2PMLineInitHist15MinTable OBJECT-TYPE 5786 SYNTAX SEQUENCE OF Xdsl2PMLineInitHist15MinEntry 5787 MAX-ACCESS not-accessible 5788 STATUS current 5789 DESCRIPTION 5790 "The table xdsl2PMLineInitHist15MinTable contains PM line 5791 initialization history for 15 minutes intervals of DSL 5792 line. The objects in this table are NOT persistent." 5793 ::= { xdsl2PMLine 5 } 5795 xdsl2PMLineInitHist15MinEntry OBJECT-TYPE 5796 SYNTAX Xdsl2PMLineInitHist15MinEntry 5797 MAX-ACCESS not-accessible 5798 STATUS current 5799 DESCRIPTION 5800 "The table xdsl2PMLineInitHist15MinTable contains PM line 5801 initialization history for 15 minutes intervals of DSL 5802 line. 5803 The index of this table is an interface index where the 5804 interface has an ifType of vdsl2(xxx) and an interval number." 5806 INDEX { ifIndex, 5807 xdsl2PMLHistInit15MInterval } 5808 ::= { xdsl2PMLineInitHist15MinTable 1 } 5810 Xdsl2PMLineInitHist15MinEntry ::= 5811 SEQUENCE { 5812 xdsl2PMLHistInit15MInterval Unsigned32, 5813 xdsl2PMLHistInit15MMonitoredTime Unsigned32, 5814 xdsl2PMLHistInit15MFullInits Unsigned32, 5815 xdsl2PMLHistInit15MFailedFullInits Unsigned32, 5816 xdsl2PMLHistInit15MShortInits Unsigned32, 5817 xdsl2PMLHistInit15MFailedShortInits Unsigned32, 5818 xdsl2PMLHistInit15MValidInterval TruthValue 5819 } 5821 xdsl2PMLHistInit15MInterval OBJECT-TYPE 5822 SYNTAX Unsigned32 (1..96) 5823 MAX-ACCESS not-accessible 5824 STATUS current 5825 DESCRIPTION 5826 "The interval number." 5827 ::= { xdsl2PMLineInitHist15MinEntry 1 } 5829 xdsl2PMLHistInit15MMonitoredTime OBJECT-TYPE 5830 SYNTAX Unsigned32 5831 UNITS "seconds" 5832 MAX-ACCESS read-only 5833 STATUS current 5834 DESCRIPTION 5835 "Total seconds monitored in this interval." 5836 ::= { xdsl2PMLineInitHist15MinEntry 2 } 5838 xdsl2PMLHistInit15MFullInits OBJECT-TYPE 5839 SYNTAX Unsigned32 5840 MAX-ACCESS read-only 5841 STATUS current 5842 DESCRIPTION 5843 "Count of full initializations attempted on the line 5844 (successful and failed) during this interval." 5845 REFERENCE "ITU-T G.997.1, paragraph 7.2.1" 5846 ::= { xdsl2PMLineInitHist15MinEntry 3 } 5848 xdsl2PMLHistInit15MFailedFullInits OBJECT-TYPE 5849 SYNTAX Unsigned32 5850 MAX-ACCESS read-only 5851 STATUS current 5852 DESCRIPTION 5853 "Count of failed full initializations on the line during this 5854 interval." 5855 REFERENCE "ITU-T G.997.1, paragraph 7.2.1" 5856 ::= { xdsl2PMLineInitHist15MinEntry 4 } 5858 xdsl2PMLHistInit15MShortInits OBJECT-TYPE 5859 SYNTAX Unsigned32 5860 MAX-ACCESS read-only 5861 STATUS current 5862 DESCRIPTION 5863 "Count of short initializations attempted on the line 5864 (successful and failed) during this interval." 5865 REFERENCE "ITU-T G.997.1, paragraph 7.2.1" 5866 ::= { xdsl2PMLineInitHist15MinEntry 5 } 5868 xdsl2PMLHistInit15MFailedShortInits OBJECT-TYPE 5869 SYNTAX Unsigned32 5870 MAX-ACCESS read-only 5871 STATUS current 5872 DESCRIPTION 5873 "Count of failed short initializations on the line during this 5874 interval." 5875 REFERENCE "ITU-T G.997.1, paragraph 7.2.1" 5876 ::= { xdsl2PMLineInitHist15MinEntry 6 } 5878 xdsl2PMLHistInit15MValidInterval OBJECT-TYPE 5879 SYNTAX TruthValue 5880 MAX-ACCESS read-only 5881 STATUS current 5882 DESCRIPTION 5883 "This variable indicates if the data for this interval is 5884 valid." 5885 ::= { xdsl2PMLineInitHist15MinEntry 7 } 5887 ------------------------------------------- 5888 -- PM line init history 1 Day -- 5889 ------------------------------------------- 5890 xdsl2PMLineInitHist1DayTable OBJECT-TYPE 5891 SYNTAX SEQUENCE OF Xdsl2PMLineInitHist1DayEntry 5892 MAX-ACCESS not-accessible 5893 STATUS current 5894 DESCRIPTION 5895 "The table xdsl2PMLineInitHist1DayTable contains PM line 5896 initialization history for 24 hours intervals of DSL 5897 line. The objects in this table are NOT persistent." 5898 ::= { xdsl2PMLine 6 } 5900 xdsl2PMLineInitHist1DayEntry OBJECT-TYPE 5901 SYNTAX Xdsl2PMLineInitHist1DayEntry 5902 MAX-ACCESS not-accessible 5903 STATUS current 5904 DESCRIPTION 5905 "The table xdsl2PMLineInitHist1DayTable contains PM line 5906 initialization history for 24 hours intervals of DSL 5907 line. 5908 The indexes of this table is an interface index where the 5909 interface has an ifType of vdsl2(xxx) and an interval number." 5910 INDEX { ifIndex, 5911 xdsl2PMLHistinit1DInterval } 5912 ::= { xdsl2PMLineInitHist1DayTable 1 } 5914 Xdsl2PMLineInitHist1DayEntry ::= 5915 SEQUENCE { 5916 xdsl2PMLHistinit1DInterval Unsigned32, 5917 xdsl2PMLHistinit1DMonitoredTime Unsigned32, 5918 xdsl2PMLHistinit1DFullInits Unsigned32, 5919 xdsl2PMLHistinit1DFailedFullInits Unsigned32, 5920 xdsl2PMLHistinit1DShortInits Unsigned32, 5921 xdsl2PMLHistinit1DFailedShortInits Unsigned32, 5922 xdsl2PMLHistinit1DValidInterval TruthValue 5923 } 5925 xdsl2PMLHistinit1DInterval OBJECT-TYPE 5926 SYNTAX Unsigned32 (1..30) 5927 MAX-ACCESS not-accessible 5928 STATUS current 5929 DESCRIPTION 5930 "The interval number." 5931 ::= { xdsl2PMLineInitHist1DayEntry 1 } 5933 xdsl2PMLHistinit1DMonitoredTime OBJECT-TYPE 5934 SYNTAX Unsigned32 5935 UNITS "seconds" 5936 MAX-ACCESS read-only 5937 STATUS current 5938 DESCRIPTION 5939 "Total seconds monitored in this interval." 5940 ::= { xdsl2PMLineInitHist1DayEntry 2 } 5942 xdsl2PMLHistinit1DFullInits OBJECT-TYPE 5943 SYNTAX Unsigned32 5944 MAX-ACCESS read-only 5945 STATUS current 5946 DESCRIPTION 5947 "Count of full initializations attempted on the line 5948 (successful and failed) during this interval." 5949 REFERENCE "ITU-T G.997.1, paragraph 7.2.1" 5950 ::= { xdsl2PMLineInitHist1DayEntry 3 } 5952 xdsl2PMLHistinit1DFailedFullInits OBJECT-TYPE 5953 SYNTAX Unsigned32 5954 MAX-ACCESS read-only 5955 STATUS current 5956 DESCRIPTION 5957 "Count of failed full initializations on the line during this 5958 interval." 5959 REFERENCE "ITU-T G.997.1, paragraph 7.2.1" 5960 ::= { xdsl2PMLineInitHist1DayEntry 4 } 5962 xdsl2PMLHistinit1DShortInits OBJECT-TYPE 5963 SYNTAX Unsigned32 5964 MAX-ACCESS read-only 5965 STATUS current 5966 DESCRIPTION 5967 "Count of short initializations attempted on the line 5968 (successful and failed) during this interval." 5969 REFERENCE "ITU-T G.997.1, paragraph 7.2.1" 5970 ::= { xdsl2PMLineInitHist1DayEntry 5 } 5972 xdsl2PMLHistinit1DFailedShortInits OBJECT-TYPE 5973 SYNTAX Unsigned32 5974 MAX-ACCESS read-only 5975 STATUS current 5976 DESCRIPTION 5977 "Count of failed short initializations on the line during this 5978 interval." 5979 REFERENCE "ITU-T G.997.1, paragraph 7.2.1" 5980 ::= { xdsl2PMLineInitHist1DayEntry 6 } 5982 xdsl2PMLHistinit1DValidInterval OBJECT-TYPE 5983 SYNTAX TruthValue 5984 MAX-ACCESS read-only 5985 STATUS current 5986 DESCRIPTION 5987 "This variable indicates if the data for this interval is 5988 valid." 5989 ::= { xdsl2PMLineInitHist1DayEntry 7 } 5991 --------------------------------------------------- 5992 -- PM channel current counters -- 5993 --------------------------------------------------- 5994 xdsl2PMChCurrTable OBJECT-TYPE 5995 SYNTAX SEQUENCE OF Xdsl2PMChCurrEntry 5996 MAX-ACCESS not-accessible 5997 STATUS current 5998 DESCRIPTION 5999 "The table xdsl2PMChCurrTable contains current Performance 6000 Monitoring results of DSL channel. The objects in this 6001 table are NOT persistent." 6002 ::= { xdsl2PMChannel 1 } 6004 xdsl2PMChCurrEntry OBJECT-TYPE 6005 SYNTAX Xdsl2PMChCurrEntry 6006 MAX-ACCESS not-accessible 6007 STATUS current 6008 DESCRIPTION 6009 "The table xdsl2PMChCurrTable contains current Performance 6010 Monitoring results of DSL channel. 6011 The indexes of this table is an interface index where 6012 the interface has an ifType value which is applicable 6013 for a DSL channel and the termination unit." 6014 INDEX { ifIndex, xdsl2PMChCurrUnit } 6015 ::= { xdsl2PMChCurrTable 1 } 6017 Xdsl2PMChCurrEntry ::= 6018 SEQUENCE { 6019 xdsl2PMChCurrUnit Xdsl2Unit, 6020 xdsl2PMChCurrValidIntervals Unsigned32, 6021 xdsl2PMChCurrInvalidIntervals Unsigned32, 6022 xdsl2PMChCurr15MTimeElapsed HCPerfTimeElapsed, 6023 xdsl2PMChCurr15MCodingViolations Unsigned32, 6024 xdsl2PMChCurr15MCorrectedBlocks Unsigned32, 6025 xdsl2PMChCurr1DayValidIntervals Unsigned32, 6026 xdsl2PMChCurr1DayInvalidIntervals Unsigned32, 6027 xdsl2PMChCurr1DayTimeElapsed HCPerfTimeElapsed, 6028 xdsl2PMChCurr1DayCodingViolations Unsigned32, 6029 xdsl2PMChCurr1DayCorrectedBlocks Unsigned32 6030 } 6032 xdsl2PMChCurrUnit OBJECT-TYPE 6033 SYNTAX Xdsl2Unit 6034 MAX-ACCESS not-accessible 6035 STATUS current 6036 DESCRIPTION 6037 "The termination unit." 6038 ::= { xdsl2PMChCurrEntry 1 } 6040 xdsl2PMChCurrValidIntervals OBJECT-TYPE 6041 SYNTAX Unsigned32 6042 MAX-ACCESS read-only 6043 STATUS current 6044 DESCRIPTION 6045 "Valid intervals." 6046 ::= { xdsl2PMChCurrEntry 2 } 6048 xdsl2PMChCurrInvalidIntervals OBJECT-TYPE 6049 SYNTAX Unsigned32 6050 MAX-ACCESS read-only 6051 STATUS current 6052 DESCRIPTION 6053 "Invalid intervals." 6054 ::= { xdsl2PMChCurrEntry 3 } 6056 xdsl2PMChCurr15MTimeElapsed OBJECT-TYPE 6057 SYNTAX HCPerfTimeElapsed 6058 UNITS "seconds" 6059 MAX-ACCESS read-only 6060 STATUS current 6061 DESCRIPTION 6062 "Total elapsed seconds in this interval." 6063 ::= { xdsl2PMChCurrEntry 4 } 6065 xdsl2PMChCurr15MCodingViolations OBJECT-TYPE 6066 SYNTAX Unsigned32 6067 MAX-ACCESS read-only 6068 STATUS current 6069 DESCRIPTION 6070 "Count of CRC-8 (FEBE for xtu-r) anomalies occurring in the 6071 channel during the interval. This parameter is inhibited 6072 during UAS or SES. If the CRC is applied over multiple 6073 channels, then each related CRC-8 (or FEBE) anomaly should 6074 increment each of the counters related to the individual 6075 channels." 6076 REFERENCE "ITU-T G.997.1, paragraph 7.2.2" 6078 ::= { xdsl2PMChCurrEntry 5 } 6080 xdsl2PMChCurr15MCorrectedBlocks OBJECT-TYPE 6081 SYNTAX Unsigned32 6082 MAX-ACCESS read-only 6083 STATUS current 6084 DESCRIPTION 6085 "Count of FEC (FFEC for xtu-r) anomalies (corrected code words) 6086 occurring in the channel during the interval. This parameter 6087 is inhibited during UAS or SES. If the FEC is applied over 6088 multiple channels, then each related FEC (or FFEC) anomaly 6089 should increment each of the counters related to the 6090 individual channels." 6091 REFERENCE "ITU-T G.997.1, paragraph 7.2.2" 6092 ::= { xdsl2PMChCurrEntry 6 } 6094 xdsl2PMChCurr1DayValidIntervals OBJECT-TYPE 6095 SYNTAX Unsigned32 6096 MAX-ACCESS read-only 6097 STATUS current 6098 DESCRIPTION 6099 "Valid intervals." 6100 ::= { xdsl2PMChCurrEntry 7 } 6102 xdsl2PMChCurr1DayInvalidIntervals OBJECT-TYPE 6103 SYNTAX Unsigned32 6104 MAX-ACCESS read-only 6105 STATUS current 6106 DESCRIPTION 6107 "Invalid intervals." 6108 ::= { xdsl2PMChCurrEntry 8 } 6110 xdsl2PMChCurr1DayTimeElapsed OBJECT-TYPE 6111 SYNTAX HCPerfTimeElapsed 6112 UNITS "seconds" 6113 MAX-ACCESS read-only 6114 STATUS current 6115 DESCRIPTION 6116 "Total elapsed seconds in this interval." 6117 ::= { xdsl2PMChCurrEntry 9 } 6119 xdsl2PMChCurr1DayCodingViolations OBJECT-TYPE 6120 SYNTAX Unsigned32 6121 MAX-ACCESS read-only 6122 STATUS current 6123 DESCRIPTION 6124 "Count of CRC-8 (FEBE for xtu-r) anomalies occurring in the 6125 channel during the interval. This parameter is inhibited 6126 during UAS or SES. If the CRC is applied over multiple 6127 channels, then each related CRC-8 (or FEBE) anomaly should 6128 increment each of the counters related to the individual 6129 channels." 6130 REFERENCE "ITU-T G.997.1, paragraph 7.2.2" 6131 ::= { xdsl2PMChCurrEntry 10 } 6133 xdsl2PMChCurr1DayCorrectedBlocks OBJECT-TYPE 6134 SYNTAX Unsigned32 6135 MAX-ACCESS read-only 6136 STATUS current 6137 DESCRIPTION 6138 "Count of FEC (FFEC for xtu-r) anomalies (corrected code words) 6139 occurring in the channel during the interval. This parameter 6140 is inhibited during UAS or SES. If the FEC is applied over 6141 multiple channels, then each related FEC (or FFEC) anomaly 6142 should increment each of the counters related to the 6143 individual channels." 6144 REFERENCE "ITU-T G.997.1, paragraph 7.2.2" 6145 ::= { xdsl2PMChCurrEntry 11 } 6147 ------------------------------------------- 6148 -- PM channel history 15 Minutes -- 6149 ------------------------------------------- 6150 xdsl2PMChHist15MinTable OBJECT-TYPE 6151 SYNTAX SEQUENCE OF Xdsl2PMChHist15MinEntry 6152 MAX-ACCESS not-accessible 6153 STATUS current 6154 DESCRIPTION 6155 "The table xdsl2PMChCurrTable contains current Performance 6156 Monitoring results of DSL channel. The objects in this 6157 table are NOT persistent." 6158 ::= { xdsl2PMChannel 2 } 6160 xdsl2PMChHist15MinEntry OBJECT-TYPE 6161 SYNTAX Xdsl2PMChHist15MinEntry 6162 MAX-ACCESS not-accessible 6163 STATUS current 6164 DESCRIPTION 6165 "The table xdsl2PMChCurrTable contains current Performance 6166 Monitoring results of DSL channel. 6167 The indexes of this table is an interface index where 6168 the interface has an ifType value which is applicable 6169 for a DSL channel, the termination unit and the 6170 interval number." 6171 INDEX { ifIndex, 6172 xdsl2PMChHist15MUnit, 6173 xdsl2PMChHist15MInterval } 6174 ::= { xdsl2PMChHist15MinTable 1 } 6176 Xdsl2PMChHist15MinEntry ::= 6177 SEQUENCE { 6178 xdsl2PMChHist15MUnit Xdsl2Unit, 6179 xdsl2PMChHist15MInterval Unsigned32, 6180 xdsl2PMChHist15MMonitoredTime Unsigned32, 6181 xdsl2PMChHist15MCodingViolations Unsigned32, 6182 xdsl2PMChHist15MCorrectedBlocks Unsigned32, 6183 xdsl2PMChHist15MValidInterval TruthValue 6184 } 6186 xdsl2PMChHist15MUnit OBJECT-TYPE 6187 SYNTAX Xdsl2Unit 6188 MAX-ACCESS not-accessible 6189 STATUS current 6190 DESCRIPTION 6191 "The termination unit." 6192 ::= { xdsl2PMChHist15MinEntry 1 } 6194 xdsl2PMChHist15MInterval OBJECT-TYPE 6195 SYNTAX Unsigned32 (1..96) 6196 MAX-ACCESS not-accessible 6197 STATUS current 6198 DESCRIPTION 6199 "The interval number." 6200 ::= { xdsl2PMChHist15MinEntry 2 } 6202 xdsl2PMChHist15MMonitoredTime OBJECT-TYPE 6203 SYNTAX Unsigned32 6204 UNITS "seconds" 6205 MAX-ACCESS read-only 6206 STATUS current 6207 DESCRIPTION 6208 "Total seconds monitored in this interval." 6209 ::= { xdsl2PMChHist15MinEntry 3 } 6211 xdsl2PMChHist15MCodingViolations OBJECT-TYPE 6212 SYNTAX Unsigned32 6213 MAX-ACCESS read-only 6214 STATUS current 6215 DESCRIPTION 6216 "Count of CRC-8 (FEBE for xtu-r) anomalies occurring in the 6217 channel during the interval. This parameter is inhibited 6218 during UAS or SES. If the CRC is applied over multiple 6219 channels, then each related CRC-8 (or FEBE) anomaly should 6220 increment each of the counters related to the individual 6221 channels." 6222 REFERENCE "ITU-T G.997.1, paragraph 7.2.2" 6223 ::= { xdsl2PMChHist15MinEntry 4 } 6225 xdsl2PMChHist15MCorrectedBlocks OBJECT-TYPE 6226 SYNTAX Unsigned32 6227 MAX-ACCESS read-only 6228 STATUS current 6229 DESCRIPTION 6230 "Count of FEC (FFEC for xtu-r) anomalies (corrected code words) 6231 occurring in the channel during the interval. This parameter 6232 is inhibited during UAS or SES. If the FEC is applied over 6233 multiple channels, then each related FEC (or FFEC) anomaly 6234 should increment each of the counters related to the 6235 individual channels." 6236 REFERENCE "ITU-T G.997.1, paragraph 7.2.2" 6237 ::= { xdsl2PMChHist15MinEntry 5 } 6239 xdsl2PMChHist15MValidInterval OBJECT-TYPE 6240 SYNTAX TruthValue 6241 MAX-ACCESS read-only 6242 STATUS current 6243 DESCRIPTION 6244 "This variable indicates if the data for this interval is 6245 valid." 6246 ::= { xdsl2PMChHist15MinEntry 6 } 6248 ------------------------------------------ 6249 -- PM channel history 1 Day -- 6250 ------------------------------------------ 6251 xdsl2PMChHist1DTable OBJECT-TYPE 6252 SYNTAX SEQUENCE OF Xdsl2PMChHist1DEntry 6253 MAX-ACCESS not-accessible 6254 STATUS current 6255 DESCRIPTION 6256 "The table xdsl2PMChHist1DayTable contains PM channel history 6257 for 1 day intervals of DSL. The objects in this table are 6258 NOT persistent." 6259 ::= { xdsl2PMChannel 3 } 6261 xdsl2PMChHist1DEntry OBJECT-TYPE 6262 SYNTAX Xdsl2PMChHist1DEntry 6263 MAX-ACCESS not-accessible 6264 STATUS current 6265 DESCRIPTION 6266 "The table xdsl2PMChHist1DayTable contains PM channel history 6267 for 1 day intervals of DSL. 6268 The indexes of this table is an interface index where 6269 the interface has an ifType value which is applicable 6270 for a DSL channel, the termination unit and the 6271 interval number." 6273 INDEX { ifIndex, 6274 xdsl2PMChHist1DUnit, 6275 xdsl2PMChHist1DInterval } 6276 ::= { xdsl2PMChHist1DTable 1 } 6278 Xdsl2PMChHist1DEntry ::= 6279 SEQUENCE { 6280 xdsl2PMChHist1DUnit Xdsl2Unit, 6281 xdsl2PMChHist1DInterval Unsigned32, 6282 xdsl2PMChHist1DMonitoredTime Unsigned32, 6283 xdsl2PMChHist1DCodingViolations Unsigned32, 6284 xdsl2PMChHist1DCorrectedBlocks Unsigned32, 6285 xdsl2PMChHist1DValidInterval TruthValue 6286 } 6288 xdsl2PMChHist1DUnit OBJECT-TYPE 6289 SYNTAX Xdsl2Unit 6290 MAX-ACCESS not-accessible 6291 STATUS current 6292 DESCRIPTION 6293 "The termination unit." 6294 ::= { xdsl2PMChHist1DEntry 1 } 6296 xdsl2PMChHist1DInterval OBJECT-TYPE 6297 SYNTAX Unsigned32 (1..30) 6298 MAX-ACCESS not-accessible 6299 STATUS current 6300 DESCRIPTION 6301 "The interval number." 6302 ::= { xdsl2PMChHist1DEntry 2 } 6304 xdsl2PMChHist1DMonitoredTime OBJECT-TYPE 6305 SYNTAX Unsigned32 6306 UNITS "seconds" 6307 MAX-ACCESS read-only 6308 STATUS current 6309 DESCRIPTION 6310 "Total seconds monitored in this interval." 6311 ::= { xdsl2PMChHist1DEntry 3 } 6313 xdsl2PMChHist1DCodingViolations OBJECT-TYPE 6314 SYNTAX Unsigned32 6315 MAX-ACCESS read-only 6316 STATUS current 6317 DESCRIPTION 6318 "Count of CRC-8 (FEBE for xtu-r) anomalies occurring in the 6319 channel during the interval. This parameter is inhibited 6320 during UAS or SES. If the CRC is applied over multiple 6321 channels, then each related CRC-8 (or FEBE) anomaly should 6322 increment each of the counters related to the individual 6323 channels." 6324 REFERENCE "ITU-T G.997.1, paragraph 7.2.2" 6325 ::= { xdsl2PMChHist1DEntry 4 } 6327 xdsl2PMChHist1DCorrectedBlocks OBJECT-TYPE 6328 SYNTAX Unsigned32 6329 MAX-ACCESS read-only 6330 STATUS current 6331 DESCRIPTION 6332 "Count of FEC (FFEC for xtu-r) anomalies (corrected code words) 6333 occurring in the channel during the interval. This parameter 6334 is inhibited during UAS or SES. If the FEC is applied over 6335 multiple channels, then each related FEC (or FFEC) anomaly 6336 should increment each of the counters related to the 6337 individual channels." 6338 REFERENCE "ITU-T G.997.1, paragraph 7.2.2" 6339 ::= { xdsl2PMChHist1DEntry 5 } 6341 xdsl2PMChHist1DValidInterval OBJECT-TYPE 6342 SYNTAX TruthValue 6343 MAX-ACCESS read-only 6344 STATUS current 6345 DESCRIPTION 6346 "This variable indicates if the data for this interval is 6347 valid." 6348 ::= { xdsl2PMChHist1DEntry 6 } 6350 ------------------------------------------- 6351 -- Notifications Group -- 6352 ------------------------------------------- 6354 xdsl2LinePerfFECSThreshXtuc NOTIFICATION-TYPE 6355 OBJECTS 6356 { 6357 xdsl2PMLCurr15MFecs, 6358 xdsl2LineAlarmConfProfileXtucThresh15MinFecs 6359 } 6360 STATUS current 6361 DESCRIPTION 6362 "This notification indicates that the FEC seconds threshold 6363 has been reached/exceeded for the referred XTU-C." 6364 ::= { xdsl2Notifications 1 } 6366 xdsl2LinePerfFECSThreshXtur NOTIFICATION-TYPE 6367 OBJECTS 6368 { 6369 xdsl2PMLCurr15MFecs, 6370 xdsl2LineAlarmConfProfileXturThresh15MinFecs 6371 } 6372 STATUS current 6373 DESCRIPTION 6374 "This notification indicates that the FEC seconds threshold 6375 has been reached/exceeded for the referred XTU-R." 6376 ::= { xdsl2Notifications 2 } 6378 xdsl2LinePerfESThreshXtuc NOTIFICATION-TYPE 6379 OBJECTS 6380 { 6381 xdsl2PMLCurr15MEs, 6382 xdsl2LineAlarmConfProfileXtucThresh15MinEs 6383 } 6384 STATUS current 6385 DESCRIPTION 6386 "This notification indicates that the errored seconds threshold 6387 has been reached/exceeded for the referred XTU-C." 6388 ::= { xdsl2Notifications 3 } 6390 xdsl2LinePerfESThreshXtur NOTIFICATION-TYPE 6391 OBJECTS 6392 { 6393 xdsl2PMLCurr15MEs, 6394 xdsl2LineAlarmConfProfileXturThresh15MinEs 6395 } 6396 STATUS current 6397 DESCRIPTION 6398 "This notification indicates that the errored seconds threshold 6399 has been reached/exceeded for the referred XTU-R." 6400 ::= { xdsl2Notifications 4 } 6402 xdsl2LinePerfSESThreshXtuc NOTIFICATION-TYPE 6403 OBJECTS 6404 { 6405 xdsl2PMLCurr15MSes, 6406 xdsl2LineAlarmConfProfileXtucThresh15MinSes 6407 } 6408 STATUS current 6409 DESCRIPTION 6410 "This notification indicates that the severely-errored seconds 6411 threshold has been reached/exceeded for the referred XTU-C." 6412 ::= { xdsl2Notifications 5 } 6414 xdsl2LinePerfSESThreshXtur NOTIFICATION-TYPE 6415 OBJECTS 6416 { 6417 xdsl2PMLCurr15MSes, 6418 xdsl2LineAlarmConfProfileXturThresh15MinSes 6419 } 6420 STATUS current 6421 DESCRIPTION 6422 "This notification indicates that the severely-errored seconds 6423 threshold has been reached/exceeded for the referred XTU-R." 6424 ::= { xdsl2Notifications 6 } 6426 xdsl2LinePerfLOSSThreshXtuc NOTIFICATION-TYPE 6427 OBJECTS 6428 { 6429 xdsl2PMLCurr15MLoss, 6430 xdsl2LineAlarmConfProfileXtucThresh15MinLoss 6431 } 6432 STATUS current 6433 DESCRIPTION 6434 "This notification indicates that the LOS seconds 6435 threshold has been reached/exceeded for the referred XTU-C." 6436 ::= { xdsl2Notifications 7 } 6438 xdsl2LinePerfLOSSThreshXtur NOTIFICATION-TYPE 6439 OBJECTS 6440 { 6441 xdsl2PMLCurr15MLoss, 6442 xdsl2LineAlarmConfProfileXturThresh15MinLoss 6443 } 6444 STATUS current 6445 DESCRIPTION 6446 "This notification indicates that the LOS seconds 6447 threshold has been reached/exceeded for the referred XTU-R." 6448 ::= { xdsl2Notifications 8 } 6450 xdsl2LinePerfUASThreshXtuc NOTIFICATION-TYPE 6451 OBJECTS 6452 { 6453 xdsl2PMLCurr15MUas, 6454 xdsl2LineAlarmConfProfileXtucThresh15MinUas 6455 } 6456 STATUS current 6457 DESCRIPTION 6458 "This notification indicates that the unavailable seconds 6459 threshold has been reached/exceeded for the referred XTU-C." 6460 ::= { xdsl2Notifications 9 } 6462 xdsl2LinePerfUASThreshXtur NOTIFICATION-TYPE 6463 OBJECTS 6464 { 6465 xdsl2PMLCurr15MUas, 6466 xdsl2LineAlarmConfProfileXturThresh15MinUas 6467 } 6468 STATUS current 6469 DESCRIPTION 6470 "This notification indicates that the unavailable seconds 6471 threshold has been reached/exceeded for the referred XTU-R." 6472 ::= { xdsl2Notifications 10 } 6474 xdsl2LinePerfCodingViolationsThreshXtuc NOTIFICATION-TYPE 6475 OBJECTS 6476 { 6477 xdsl2PMChCurr15MCodingViolations, 6478 xdsl2ChAlarmConfProfileXtucThresh15MinCodingViolations 6479 } 6480 STATUS current 6481 DESCRIPTION 6482 "This notification indicates that the coding violations 6483 threshold has been reached/exceeded for the referred XTU-C." 6484 ::= { xdsl2Notifications 11 } 6486 xdsl2LinePerfCodingViolationsThreshXtur NOTIFICATION-TYPE 6487 OBJECTS 6488 { 6489 xdsl2PMChCurr15MCodingViolations, 6490 xdsl2ChAlarmConfProfileXturThresh15MinCodingViolations 6491 } 6492 STATUS current 6493 DESCRIPTION 6494 "This notification indicates that the coding violations 6495 threshold has been reached/exceeded for the referred XTU-R." 6496 ::= { xdsl2Notifications 12 } 6498 xdsl2LinePerfCorrectedThreshXtuc NOTIFICATION-TYPE 6499 OBJECTS 6500 { 6501 xdsl2PMChCurr15MCorrectedBlocks, 6502 xdsl2ChAlarmConfProfileXtucThresh15MinCorrected 6503 } 6504 STATUS current 6505 DESCRIPTION 6506 "This notification indicates that the corrected blocks 6507 (FEC events) threshold has been reached/exceeded for the 6508 referred XTU-C." 6509 ::= { xdsl2Notifications 13 } 6511 xdsl2LinePerfCorrectedThreshXtur NOTIFICATION-TYPE 6512 OBJECTS 6513 { 6514 xdsl2PMChCurr15MCorrectedBlocks, 6515 xdsl2ChAlarmConfProfileXturThresh15MinCorrected 6516 } 6517 STATUS current 6518 DESCRIPTION 6519 "This notification indicates that the corrected blocks 6520 (FEC events) threshold has been reached/exceeded for the 6521 referred XTU-R." 6522 ::= { xdsl2Notifications 14 } 6524 xdsl2LinePerfFailedFullInitThresh NOTIFICATION-TYPE 6525 OBJECTS 6526 { 6527 xdsl2PMLCurrInit15MFailedFullInits, 6528 xdsl2LineAlarmConfProfileThresh15MinFailedFullInt 6529 } 6530 STATUS current 6531 DESCRIPTION 6532 "This notification indicates that the failed full 6533 initializations threshold has been reached/exceeded for the 6534 referred ADSL/ADSL2 or ADSL2 line." 6535 ::= { xdsl2Notifications 15 } 6537 xdsl2LinePerfFailedShortInitThresh NOTIFICATION-TYPE 6538 OBJECTS 6539 { 6540 xdsl2PMLCurrInit15MFailedShortInits, 6541 xdsl2LineAlarmConfProfileThresh15MinFailedShrtInt 6542 } 6543 STATUS current 6544 DESCRIPTION 6545 "This notification indicates that the failed short 6546 initializations threshold has been reached/exceeded for the 6547 referred VDSL2/ADSL/ADSL2 or ADSL2+ line." 6548 ::= { xdsl2Notifications 16 } 6550 xdsl2LineStatusChangeXtuc NOTIFICATION-TYPE 6551 OBJECTS 6552 { 6553 xdsl2LineStatusXtuc 6554 } 6555 STATUS current 6556 DESCRIPTION 6557 "This notification indicates that a status change is 6558 detected for the referred XTU-C." 6559 ::= { xdsl2Notifications 17 } 6561 xdsl2LineStatusChangeXtur NOTIFICATION-TYPE 6562 OBJECTS 6563 { 6564 xdsl2LineStatusXtur 6565 } 6566 STATUS current 6567 DESCRIPTION 6568 "This notification indicates that a status change is 6569 detected for the referred XTU-R." 6570 ::= { xdsl2Notifications 18 } 6572 -- conformance information 6574 vdsl2Groups OBJECT IDENTIFIER ::= { vdsl2Conformance 1 } 6575 vdsl2Compliances OBJECT IDENTIFIER ::= { vdsl2Conformance 2 } 6577 vdsl2LineMibCompliance MODULE-COMPLIANCE 6578 STATUS current 6579 DESCRIPTION 6580 "The compliance statement for SNMP entities which 6581 manage VDSL2/ADSL/ADSL2 and ADSL2+ interfaces." 6582 MODULE -- this module 6583 MANDATORY-GROUPS 6584 { 6585 vdsl2LineGroup, 6586 vdsl2ChannelStatusGroup, 6587 vdsl2SCStatusGroup, 6588 vdsl2LineInventoryGroup, 6589 vdsl2LineConfTemplateGroup, 6590 vdsl2LineConfProfGroup, 6591 vdsl2LineConfProfModeSpecGroup, 6592 vdsl2ChConfProfileGroup, 6593 vdsl2LineAlarmConfTemplateGroup, 6594 vdsl2PMLineCurrGroup, 6595 vdsl2PMLineCurrInitGroup, 6596 vdsl2PMLineHist15MinGroup, 6597 vdsl2PMLineHist1DayGroup, 6598 vdsl2PMLineInitHist15MinGroup, 6599 vdsl2PMLineInitHist1DayGroup, 6600 vdsl2PMChCurrGroup, 6601 vdsl2PMChHist15MinGroup, 6602 vdsl2PMChHist1DGroup 6603 } 6605 GROUP vdsl2ChannelStatusAtmGroup 6606 DESCRIPTION 6607 "The group of status objects required when the data path 6608 is ATM." 6610 GROUP vdsl2ChannelStatusPtmGroup 6611 DESCRIPTION 6612 "The group of status objects required when the data path 6613 is PTM." 6615 GROUP vdsl2LineConfProfRaGroup 6616 DESCRIPTION 6617 "The group of objects required for controlling the rate 6618 adaptive behavior of the line." 6620 GROUP vdsl2LineConfProfMsgMinGroup 6621 DESCRIPTION 6622 "The group of objects required for controlling the rate 6623 reserved for Overhead traffic." 6625 GROUP vdsl2LineAlarmConfProfileGroup 6626 DESCRIPTION 6627 "The group of objects that define the alarm thresholds 6628 on line level PM counters." 6630 GROUP vdsl2ChAlarmConfProfileGroup 6631 DESCRIPTION 6632 "The group of objects that define the alarm thresholds 6633 on channel level PM counters." 6635 GROUP vdsl2ChConfProfileAtmGroup 6636 DESCRIPTION 6637 "The group of configuration objects required when the data 6638 path is ATM." 6640 GROUP vdsl2ChConfProfileMinResGroup 6641 DESCRIPTION 6642 "The group of configuration objects required for the 6643 reserved data rate." 6645 GROUP vdsl2PMLineCurrInitShortGroup 6646 DESCRIPTION 6647 "The group of PM counters for the current intervals 6648 short initializations." 6650 GROUP vdsl2PMLineInitHist15MinShortGroup 6651 DESCRIPTION 6652 "The group of PM counters for the previous 15 minutes 6653 intervals short initializations." 6655 GROUP vdsl2PMLineInitHist1DayShortGroup 6656 DESCRIPTION 6657 "The group of PM counters for the previous 24 hours 6658 intervals short initializations." 6660 GROUP vdsl2ScalarSCGroup 6661 DESCRIPTION 6662 "The group of objects that report the available memory 6663 resources for DELT processes." 6665 GROUP vdsl2ThreshNotificationGroup 6666 DESCRIPTION 6667 "The group of thresholds crossing notifications." 6669 GROUP vdsl2StatusChangeNotificationGroup 6670 DESCRIPTION 6671 "The group of status change notifications." 6673 ::= { vdsl2Compliances 1 } 6675 -- units of conformance 6677 vdsl2LineGroup OBJECT-GROUP 6678 OBJECTS 6679 { 6680 xdsl2LineCnfgTemplate, 6681 xdsl2LineAlarmCnfgTemplate, 6682 xdsl2LineCmndConfPmsf, 6683 xdsl2LineCmndConfLdsf, 6684 xdsl2LineCmndConfLdsfFailReason, 6685 xdsl2LineCmndAutomodeColdStart, 6686 xdsl2LineStatusXtuTransSys, 6687 xdsl2LineStatusPwrMngState, 6688 xdsl2LineStatusInitResult, 6689 xdsl2LineStatusLastStateDs, 6690 xdsl2LineStatusLastStateUs, 6691 xdsl2LineStatusXtur, 6692 xdsl2LineStatusXtuc, 6693 xdsl2LineStatusLnAttenDs, 6694 xdsl2LineStatusLnAttenUs, 6695 xdsl2LineStatusSigAttenDs, 6696 xdsl2LineStatusSigAttenUs, 6697 xdsl2LineStatusSnrMarginDs, 6698 xdsl2LineStatusSnrMarginUs, 6699 xdsl2LineStatusAttainableRateDs, 6700 xdsl2LineStatusAttainableRateUs, 6701 xdsl2LineStatusActPsdDs, 6702 xdsl2LineStatusActPsdUs, 6703 xdsl2LineStatusActAtpDs, 6704 xdsl2LineStatusActAtpUs 6705 } 6706 STATUS current 6707 DESCRIPTION 6708 "The group of configuration, status, and commands objects 6709 on the line level." 6710 ::= { vdsl2Groups 1 } 6712 vdsl2ChannelStatusGroup OBJECT-GROUP 6713 OBJECTS 6714 { 6715 xdsl2ChStatusChannelNum, 6716 xdsl2ChStatusActDataRate, 6717 xdsl2ChStatusPrevDataRate, 6718 xdsl2ChStatusActDelay 6719 } 6720 STATUS current 6721 DESCRIPTION 6722 "The group of status objects on the channel level." 6723 ::= { vdsl2Groups 2 } 6725 vdsl2ChannelStatusAtmGroup OBJECT-GROUP 6726 OBJECTS 6727 { 6728 xdsl2ChStatusAtmStatus 6729 } 6730 STATUS current 6731 DESCRIPTION 6732 "The group of status objects on the data path level 6733 when it is ATM." 6734 ::= { vdsl2Groups 3 } 6736 vdsl2ChannelStatusPtmGroup OBJECT-GROUP 6737 OBJECTS 6738 { 6739 xdsl2ChStatusPtmStatus 6740 } 6741 STATUS current 6742 DESCRIPTION 6743 "The group of status objects on the data path level 6744 when it is PTM." 6745 ::= { vdsl2Groups 4 } 6747 vdsl2SCStatusGroup OBJECT-GROUP 6748 OBJECTS 6749 { 6750 xdsl2SCStatusMtime, 6751 xdsl2SCStatusSnr, 6752 xdsl2SCStatusBitsAlloc, 6753 xdsl2SCStatusGainAlloc, 6754 xdsl2SCStatusTssi, 6755 xdsl2SCStatusLinScale, 6756 xdsl2SCStatusLinReal, 6757 xdsl2SCStatusLinImg, 6758 xdsl2SCStatusLogMt, 6759 xdsl2SCStatusLog, 6760 xdsl2SCStatusQlnMt, 6761 xdsl2SCStatusQln, 6762 xdsl2SCStatusLnAtten, 6763 xdsl2SCStatusSigAtten, 6764 xdsl2SCStatusSnrMargin, 6765 xdsl2SCStatusAttainableRate, 6766 xdsl2SCStatusActAtp, 6767 xdsl2SCStatusRowStatus 6768 } 6769 STATUS current 6770 DESCRIPTION 6771 "The group of status objects on the sub-carrier level. 6772 They are updated as a result of a DELT process." 6773 ::= { vdsl2Groups 5 } 6775 vdsl2LineInventoryGroup OBJECT-GROUP 6776 OBJECTS 6777 { 6778 xdsl2LInvG994VendorId, 6779 xdsl2LInvSystemVendorId, 6780 xdsl2LInvVersionNumber, 6781 xdsl2LInvSerialNumber, 6782 xdsl2LInvSelfTestResult, 6783 xdsl2LInvTransmissionCapabilities 6784 } 6785 STATUS current 6786 DESCRIPTION 6787 "The group of inventory objects per xTU." 6788 ::= { vdsl2Groups 6 } 6790 vdsl2LineConfTemplateGroup OBJECT-GROUP 6791 OBJECTS 6792 { 6793 xdsl2LConfTempLineProfile, 6794 xdsl2LConfTempChan1ConfProfile, 6795 xdsl2LConfTempChan1RaRatioDs, 6796 xdsl2LConfTempChan1RaRatioUs, 6797 xdsl2LConfTempChan2ConfProfile, 6798 xdsl2LConfTempChan2RaRatioDs, 6799 xdsl2LConfTempChan2RaRatioUs, 6800 xdsl2LConfTempChan3ConfProfile, 6801 xdsl2LConfTempChan3RaRatioDs, 6802 xdsl2LConfTempChan3RaRatioUs, 6803 xdsl2LConfTempChan4ConfProfile, 6804 xdsl2LConfTempChan4RaRatioDs, 6805 xdsl2LConfTempChan4RaRatioUs, 6806 xdsl2LConfTempRowStatus 6807 } 6808 STATUS current 6809 DESCRIPTION 6810 "The group of objects in a line configuration template." 6811 ::= { vdsl2Groups 7 } 6813 vdsl2LineConfProfGroup OBJECT-GROUP 6814 OBJECTS 6815 { 6816 xdsl2LConfProfScMaskDs, 6817 xdsl2LConfProfScMaskUs, 6818 xdsl2LConfProfRfiBandsDs, 6819 xdsl2LConfProfRaModeDs, 6820 xdsl2LConfProfRaModeUs, 6821 xdsl2LConfProfTargetSnrmDs, 6822 xdsl2LConfProfTargetSnrmUs, 6823 xdsl2LConfProfMaxSnrmDs, 6824 xdsl2LConfProfMaxSnrmUs, 6825 xdsl2LConfProfMinSnrmDs, 6826 xdsl2LConfProfMinSnrmUs, 6827 xdsl2LConfProfAtuTransSysEna, 6828 xdsl2LConfProfPmMode, 6829 xdsl2LConfProfL0Time, 6830 xdsl2LConfProfL2Time, 6831 xdsl2LConfProfL2Atpr, 6832 xdsl2LConfProfL2Atprt, 6833 xdsl2LConfProfRowStatus 6834 } 6835 STATUS current 6836 DESCRIPTION 6837 "The group of objects in a line configuration profile." 6838 ::= { vdsl2Groups 8 } 6840 vdsl2LineConfProfRaGroup OBJECT-GROUP 6841 OBJECTS 6842 { 6843 xdsl2LConfProfRaUsNrmDs, 6844 xdsl2LConfProfRaUsNrmUs, 6845 xdsl2LConfProfRaUsTimeDs, 6846 xdsl2LConfProfRaUsTimeUs, 6847 xdsl2LConfProfRaDsNrmsDs, 6848 xdsl2LConfProfRaDsNrmsUs, 6849 xdsl2LConfProfRaDsTimeDs, 6850 xdsl2LConfProfRaDsTimeUs 6851 } 6852 STATUS current 6853 DESCRIPTION 6854 "The group of objects required for controlling the rate 6855 adaptive behavior of the line." 6856 ::= { vdsl2Groups 9 } 6858 vdsl2LineConfProfMsgMinGroup OBJECT-GROUP 6859 OBJECTS 6860 { 6861 xdsl2LConfProfMsgMinUs, 6862 xdsl2LConfProfMsgMinDs 6863 } 6864 STATUS current 6865 DESCRIPTION 6866 "The group of objects required for controlling the rate 6867 reserved for Overhead traffic." 6868 ::= { vdsl2Groups 10 } 6870 vdsl2LineConfProfModeSpecGroup OBJECT-GROUP 6871 OBJECTS 6872 { 6873 xdsl2LConfProfMaxNomPsdDs, 6874 xdsl2LConfProfMaxNomPsdUs, 6875 xdsl2LConfProfMaxNomAtpDs, 6876 xdsl2LConfProfMaxNomAtpUs, 6877 xdsl2LConfProfMaxAggRxPwrUs, 6878 xdsl2LConfProfPsdMaskDs, 6879 xdsl2LConfProfPsdMaskUs, 6880 xdsl2LConfProfPsdMaskSelectUs, 6881 xdsl2LConfProfModeSpecRowStatus 6882 } 6883 STATUS current 6884 DESCRIPTION 6885 "The group of objects in a line configuration profile 6886 that have an instance for each operation mode allowed." 6887 ::= { vdsl2Groups 11 } 6889 vdsl2ChConfProfileGroup OBJECT-GROUP 6890 OBJECTS 6891 { 6892 xdsl2ChConfProfMinDataRateDs, 6893 xdsl2ChConfProfMinDataRateUs, 6894 xdsl2ChConfProfMaxDataRateDs, 6895 xdsl2ChConfProfMaxDataRateUs, 6896 xdsl2ChConfProfMinDataRateLowPwrDs, 6897 xdsl2ChConfProfMaxDelayDs, 6898 xdsl2ChConfProfMaxDelayUs, 6899 xdsl2ChConfProfMinProtectionDs, 6900 xdsl2ChConfProfMinProtectionUs, 6901 xdsl2ChConfProfMaxBerDs, 6902 xdsl2ChConfProfMaxBerUs, 6903 xdsl2ChConfProfUsDataRateDs, 6904 xdsl2ChConfProfDsDataRateDs, 6905 xdsl2ChConfProfUsDataRateUs, 6906 xdsl2ChConfProfDsDataRateUs, 6907 xdsl2ChConfProfRowStatus 6908 } 6909 STATUS current 6910 DESCRIPTION 6911 "The group of objects in a channel configuration profile." 6912 ::= { vdsl2Groups 12 } 6914 vdsl2ChConfProfileAtmGroup OBJECT-GROUP 6915 OBJECTS 6916 { 6917 xdsl2ChConfProfImaEnabled, 6918 xdsl2ChStatusAtmStatus 6919 } 6920 STATUS current 6921 DESCRIPTION 6922 "The group of configuration objects required when the data 6923 path is ATM." 6924 ::= { vdsl2Groups 13 } 6926 vdsl2ChConfProfileMinResGroup OBJECT-GROUP 6927 OBJECTS 6928 { 6929 xdsl2ChConfProfMinResDataRateDs, 6930 xdsl2ChConfProfMinResDataRateUs 6931 } 6932 STATUS current 6933 DESCRIPTION 6934 "The group of configuration objects required for the 6935 reserved data rate." 6936 ::= { vdsl2Groups 14 } 6938 vdsl2LineAlarmConfTemplateGroup OBJECT-GROUP 6939 OBJECTS 6940 { 6941 xdsl2LAlarmConfTempLineProfile, 6942 xdsl2LAlarmConfTempChan1ConfProfile, 6943 xdsl2LAlarmConfTempChan2ConfProfile, 6944 xdsl2LAlarmConfTempChan3ConfProfile, 6945 xdsl2LAlarmConfTempChan4ConfProfile, 6946 xdsl2LAlarmConfTempRowStatus 6947 } 6948 STATUS current 6949 DESCRIPTION 6950 "The group of objects in a line alarm 6951 template." 6952 ::= { vdsl2Groups 15 } 6954 vdsl2LineAlarmConfProfileGroup OBJECT-GROUP 6955 OBJECTS 6956 { 6957 xdsl2LineAlarmConfProfileXtucThresh15MinFecs, 6958 xdsl2LineAlarmConfProfileXtucThresh15MinEs, 6959 xdsl2LineAlarmConfProfileXtucThresh15MinSes, 6960 xdsl2LineAlarmConfProfileXtucThresh15MinLoss, 6961 xdsl2LineAlarmConfProfileXtucThresh15MinUas, 6962 xdsl2LineAlarmConfProfileXturThresh15MinFecs, 6963 xdsl2LineAlarmConfProfileXturThresh15MinEs, 6964 xdsl2LineAlarmConfProfileXturThresh15MinSes, 6965 xdsl2LineAlarmConfProfileXturThresh15MinLoss, 6966 xdsl2LineAlarmConfProfileXturThresh15MinUas, 6967 xdsl2LineAlarmConfProfileThresh15MinFailedFullInt, 6968 xdsl2LineAlarmConfProfileThresh15MinFailedShrtInt, 6969 xdsl2LineAlarmConfProfileRowStatus 6970 } 6971 STATUS current 6972 DESCRIPTION 6973 "The group of objects in a line alarm profile." 6974 ::= { vdsl2Groups 16 } 6976 vdsl2ChAlarmConfProfileGroup OBJECT-GROUP 6977 OBJECTS 6978 { 6979 xdsl2ChAlarmConfProfileAtucThresh15MinCodingViolations, 6980 xdsl2ChAlarmConfProfileAtucThresh15MinCorrected, 6981 xdsl2ChAlarmConfProfileAturThresh15MinCodingViolations, 6982 xdsl2ChAlarmConfProfileAturThresh15MinCorrected, 6983 xdsl2ChAlarmConfProfileRowStatus 6984 } 6985 STATUS current 6986 DESCRIPTION 6987 "The group of objects in a channel alarm profile." 6988 ::= { vdsl2Groups 17 } 6990 vdsl2PMLineCurrGroup OBJECT-GROUP 6991 OBJECTS 6992 { 6993 xdsl2PMLCurrValidIntervals, 6994 xdsl2PMLCurrInvalidIntervals, 6995 xdsl2PMLCurr15MTimeElapsed, 6996 xdsl2PMLCurr15MFecs, 6997 xdsl2PMLCurr15MEs, 6998 xdsl2PMLCurr15MSes, 6999 xdsl2PMLCurr15MLoss, 7000 xdsl2PMLCurr15MUas, 7001 xdsl2PMLCurr1DayValidIntervals, 7002 xdsl2PMLCurr1DayInvalidIntervals, 7003 xdsl2PMLCurr1DayTimeElapsed, 7004 xdsl2PMLCurr1DayFecs, 7005 xdsl2PMLCurr1DayEs, 7006 xdsl2PMLCurr1DaySes, 7007 xdsl2PMLCurr1DayLoss, 7008 xdsl2PMLCurr1DayUas 7009 } 7010 STATUS current 7011 DESCRIPTION 7012 "The group of objects that report the line level 7013 counters for current PM intervals." 7014 ::= { vdsl2Groups 18 } 7016 vdsl2PMLineCurrInitGroup OBJECT-GROUP 7017 OBJECTS 7018 { 7019 xdsl2PMLCurrInit15MTimeElapsed, 7020 xdsl2PMLCurrInit15MFullInits, 7021 xdsl2PMLCurrInit15MFailedFullInits, 7022 xdsl2PMLCurrInit1DayTimeElapsed, 7023 xdsl2PMLCurrInit1DayFullInits, 7024 xdsl2PMLCurrInit1DayFailedFullInits 7025 } 7026 STATUS current 7027 DESCRIPTION 7028 "The group of objects that report the full 7029 initializations counters for current PM intervals." 7030 ::= { vdsl2Groups 19 } 7032 vdsl2PMLineCurrInitShortGroup OBJECT-GROUP 7033 OBJECTS 7034 { 7035 xdsl2PMLCurrInit15MShortInits, 7036 xdsl2PMLCurrInit15MFailedShortInits, 7037 xdsl2PMLCurrInit1DayShortInits, 7038 xdsl2PMLCurrInit1DayFailedShortInits 7039 } 7040 STATUS current 7041 DESCRIPTION 7042 "The group of objects that report the short 7043 initializations counters for current PM intervals." 7044 ::= { vdsl2Groups 20 } 7046 vdsl2PMLineHist15MinGroup OBJECT-GROUP 7047 OBJECTS 7048 { 7049 xdsl2PMLHist15MMonitoredTime, 7050 xdsl2PMLHist15MFecs, 7051 xdsl2PMLHist15MEs, 7052 xdsl2PMLHist15MSes, 7053 xdsl2PMLHist15MLoss, 7054 xdsl2PMLHist15MUas, 7055 xdsl2PMLHist15MValidInterval 7056 } 7057 STATUS current 7058 DESCRIPTION 7059 "The group of line level PM counters for the previous 7060 15 minutes intervals." 7061 ::= { vdsl2Groups 21 } 7063 vdsl2PMLineHist1DayGroup OBJECT-GROUP 7064 OBJECTS 7065 { 7066 xdsl2PMLHist1DMonitoredTime, 7067 xdsl2PMLHist1DFecs, 7068 xdsl2PMLHist1DEs, 7069 xdsl2PMLHist1DSes, 7070 xdsl2PMLHist1DLoss, 7071 xdsl2PMLHist1DUas, 7072 xdsl2PMLHist1DValidInterval 7073 } 7074 STATUS current 7075 DESCRIPTION 7076 "The group of line level PM counters for the previous 7077 24 hours intervals." 7078 ::= { vdsl2Groups 22 } 7080 vdsl2PMLineInitHist15MinGroup OBJECT-GROUP 7081 OBJECTS 7082 { 7083 xdsl2PMLHistInit15MMonitoredTime, 7084 xdsl2PMLHistInit15MFullInits, 7085 xdsl2PMLHistInit15MFailedFullInits, 7086 xdsl2PMLHistInit15MValidInterval 7087 } 7088 STATUS current 7089 DESCRIPTION 7090 "The group of PM counters for the previous 15 minutes 7091 intervals full initializations." 7092 ::= { vdsl2Groups 23 } 7094 vdsl2PMLineInitHist15MinShortGroup OBJECT-GROUP 7095 OBJECTS 7096 { 7097 xdsl2PMLHistInit15MShortInits, 7098 xdsl2PMLHistInit15MFailedShortInits 7099 } 7100 STATUS current 7101 DESCRIPTION 7102 "The group of PM counters for the previous 15 minutes 7103 intervals short initializations." 7104 ::= { vdsl2Groups 24 } 7106 vdsl2PMLineInitHist1DayGroup OBJECT-GROUP 7107 OBJECTS 7108 { 7109 xdsl2PMLHistinit1DMonitoredTime, 7110 xdsl2PMLHistinit1DFullInits, 7111 xdsl2PMLHistinit1DFailedFullInits, 7112 xdsl2PMLHistinit1DValidInterval 7113 } 7114 STATUS current 7115 DESCRIPTION 7116 "The group of PM counters for the previous 24 hours 7117 intervals full initializations." 7118 ::= { vdsl2Groups 25 } 7120 vdsl2PMLineInitHist1DayShortGroup OBJECT-GROUP 7121 OBJECTS 7122 { 7123 xdsl2PMLHistinit1DShortInits, 7124 xdsl2PMLHistinit1DFailedShortInits 7125 } 7126 STATUS current 7127 DESCRIPTION 7128 "The group of PM counters for the previous 24 hours 7129 intervals short initializations." 7130 ::= { vdsl2Groups 26 } 7132 vdsl2PMChCurrGroup OBJECT-GROUP 7133 OBJECTS 7134 { 7135 xdsl2PMChCurrValidIntervals, 7136 xdsl2PMChCurrInvalidIntervals, 7137 xdsl2PMChCurr15MTimeElapsed, 7138 xdsl2PMChCurr15MCodingViolations, 7139 xdsl2PMChCurr15MCorrectedBlocks, 7140 xdsl2PMChCurr1DayValidIntervals, 7141 xdsl2PMChCurr1DayInvalidIntervals, 7142 xdsl2PMChCurr1DayTimeElapsed, 7143 xdsl2PMChCurr1DayCodingViolations, 7144 xdsl2PMChCurr1DayCorrectedBlocks 7145 } 7146 STATUS current 7147 DESCRIPTION 7148 "The group of objects that report the channel level 7149 counters for current PM intervals." 7150 ::= { vdsl2Groups 27 } 7152 vdsl2PMChHist15MinGroup OBJECT-GROUP 7153 OBJECTS 7154 { 7155 xdsl2PMChHist15MMonitoredTime, 7156 xdsl2PMChHist15MCodingViolations, 7157 xdsl2PMChHist15MCorrectedBlocks, 7158 xdsl2PMChHist15MValidInterval 7159 } 7160 STATUS current 7161 DESCRIPTION 7162 "The group of objects that report the channel level 7163 counters for previous 15 minutes PM intervals." 7164 ::= { vdsl2Groups 28 } 7166 vdsl2PMChHist1DGroup OBJECT-GROUP 7167 OBJECTS 7168 { 7169 xdsl2PMChHist1DMonitoredTime, 7170 xdsl2PMChHist1DCodingViolations, 7171 xdsl2PMChHist1DCorrectedBlocks, 7172 xdsl2PMChHist1DValidInterval 7173 } 7174 STATUS current 7175 DESCRIPTION 7176 "The group of objects that report the channel level 7177 counters for previous 24 hours PM intervals." 7178 ::= { vdsl2Groups 29 } 7180 vdsl2ScalarSCGroup OBJECT-GROUP 7181 OBJECTS 7182 { 7183 xdsl2ScalarSCMaxInterfaces, 7184 xdsl2ScalarSCAvailInterfaces 7185 } 7186 STATUS current 7187 DESCRIPTION 7188 "The group of objects that report the available memory 7189 resources for DELT processes." 7190 ::= { vdsl2Groups 30 } 7192 vdsl2ThreshNotificationGroup NOTIFICATION-GROUP 7193 NOTIFICATIONS 7194 { 7195 xdsl2LinePerfFECSThreshAtuc, 7196 xdsl2LinePerfFECSThreshAtur, 7197 xdsl2LinePerfESThreshAtuc, 7198 xdsl2LinePerfESThreshAtur, 7199 xdsl2LinePerfSESThreshAtuc, 7200 xdsl2LinePerfSESThreshAtur, 7201 xdsl2LinePerfLOSSThreshAtuc, 7202 xdsl2LinePerfLOSSThreshAtur, 7203 xdsl2LinePerfUASThreshAtuc, 7204 xdsl2LinePerfUASThreshAtur, 7205 xdsl2LinePerfCodingViolationsThreshAtuc, 7206 xdsl2LinePerfCodingViolationsThreshAtur, 7207 xdsl2LinePerfCorrectedThreshAtuc, 7208 xdsl2LinePerfCorrectedThreshAtur, 7209 xdsl2LinePerfFailedFullInitThresh, 7210 xdsl2LinePerfFailedShortInitThresh 7211 } 7212 STATUS current 7213 DESCRIPTION 7214 "This group supports notifications of significant conditions 7215 associated with DSL lines." 7216 ::= { vdsl2Groups 31 } 7218 vdsl2StatusChangeNotificationGroup NOTIFICATION-GROUP 7219 NOTIFICATIONS 7220 { 7221 xdsl2LineStatusChangeAtuc, 7222 xdsl2LineStatusChangeAtur 7223 } 7224 STATUS current 7225 DESCRIPTION 7226 "This group supports notifications of thresholds crossing 7227 associated with DSL lines." 7229 ::= { vdsl2Groups 32 } 7231 END 7233 4. Implementation Analysis 7235 A management application intended to manage ADSL links (e.g., 7236 G.992.1) with this MIB module MUST be modified to adapt itself to 7237 certain differences between RFC 2662 [RFC2662] and this MIB module, 7238 including the following aspects: 7240 o Though the configuration templates/profiles allow referring to 1-4 7241 bearer channels, ADSL links are limited to 2 channels at most 7242 o Though the channel configuration profile allows higher data rates, 7243 ADSL links are limited to downstream/upstream data rate as assumed 7244 in RFC 2662 [RFC2662] 7245 o The Impulse Noise Protection (INP) configuration parameters are 7246 given by minimum protection and maximum delay parameters. 7247 o The line configuration profile includes a sub-table that addresses 7248 mode-specific parameters. For ADSL links, the management 7249 application SHOULD create a row in that table for the 'adsl' mode. 7250 o The line configuration profile includes parameters that are 7251 irrelevant for ADSL links. Similarly, many status parameters in 7252 the MIB are irrelevant for certain ADSL modes. Therefore, it is 7253 advised to consult with ITU G.997.1 standard [G.997.1] regarding 7254 the scope and relevance of each parameter in this MIB. 7256 5. Security Considerations 7258 There are a number of management objects defined in this MIB module 7259 with a MAX-ACCESS clause of read-write and/or read-create. Such 7260 objects may be considered sensitive or vulnerable in some network 7261 environments. The support for SET operations in a non-secure 7262 environment without proper protection can have a negative effect on 7263 network operations. These are the tables and objects and their 7264 sensitivity/vulnerability: 7266 o adsl2LineTable 7268 The table consists of the following objects that support SET 7269 operations: 7271 * xdsl2LineCnfgTemplate 7272 * xdsl2LineAlarmCnfgTemplate 7273 * xdsl2LineCmndConfPmsf 7274 * xdsl2LineCmndConfLdsf 7275 * xdsl2LineCmndAutomodeColdStart 7277 Unauthorized changes to xdsl2LineCnfgTemplate could have a major 7278 adverse operational effect on many lines simultaneously. 7280 Unauthorized changes to xdsl2LineAlarmCnfgTemplate could have a 7281 contrary effect on notifications. 7283 Unauthorized changes to xdsl2LineCmndConfPmsf could have an 7284 adverse affect on the power consumption of a line and may disrupt 7285 an operational service. 7287 Unauthorized changes to xdsl2LineCmndConfLdsf could cause an 7288 unscheduled line test to be carried out on the line. 7290 Unauthorized changes to xdsl2LineCmndAutomodeColdStart could cause 7291 an unscheduled cold reset to the line. 7293 o adsl2SCStatusTable 7295 This table contains one object, xdsl2SCStatusRowStatus, that 7296 supports SET operations. Unauthorized changes could result in 7297 line test results being deleted prematurely. 7299 o xdsl2LineConfTemplateTable 7301 The table consists of the following objects that support SET 7302 operations: 7304 * xdsl2LConfTempLineProfile 7305 * xdsl2LConfTempChan1ConfProfile 7306 * xdsl2LConfTempChan1RaRatioDs 7307 * xdsl2LConfTempChan1RaRatioUs 7308 * xdsl2LConfTempChan2ConfProfile 7309 * xdsl2LConfTempChan2RaRatioDs 7310 * xdsl2LConfTempChan2RaRatioUs 7311 * xdsl2LConfTempChan3ConfProfile 7312 * xdsl2LConfTempChan3RaRatioDs 7313 * xdsl2LConfTempChan3RaRatioUs 7314 * xdsl2LConfTempChan4ConfProfile 7315 * xdsl2LConfTempChan4RaRatioDs 7316 * xdsl2LConfTempChan4RaRatioUs 7317 * xdsl2LConfTempRowStatus 7319 Unauthorized changes to xdsl2LConfTempLineProfile, 7320 xdsl2LConfTempChan1ConfProfile, xdsl2LConfTempChan2ConfProfile, 7321 xdsl2LConfTempChan3ConfProfile, or xdsl2LConfTempChan4ConfProfile 7322 could have an adverse operational effect on several lines; could 7323 change several lines over to running in unwanted levels of 7324 operation; or could result in several services undergoing changes 7325 in the number of channels that carry the service. 7327 Unauthorized changes to xdsl2LConfTempChan1RaRatioDs, 7328 xdsl2LConfTempChan2RaRatioDs, xdsl2LConfTempChan3RaRatioDs, or 7329 xdsl2LConfTempChan4RaRatioDs, would alter the relative rate 7330 allocations among all channels belonging to a line. This could 7331 have an adverse operational effect on several lines. 7333 Unauthorized changes to xdsl2LConfTempRowStatus could result in 7334 templates being created or brought into service prematurely; or 7335 could result in templates being inadvertently deleted or taken out 7336 of service. 7338 o xdsl2LineConfProfTable 7340 The table consists of the following objects that support SET 7341 operations: 7343 * xdsl2LConfProfScMaskDs 7344 * xdsl2LConfProfScMaskUs 7345 * xdsl2LConfProfRfiBandsDs 7346 * xdsl2LConfProfRaModeDs 7347 * xdsl2LConfProfRaModeUs 7348 * xdsl2LConfProfRaUsNrmDs 7349 * xdsl2LConfProfRaUsNrmUs 7350 * xdsl2LConfProfRaUsTimeDs 7351 * xdsl2LConfProfRaUsTimeUs 7352 * xdsl2LConfProfRaDsNrmsDs 7353 * xdsl2LConfProfRaDsNrmsUs 7354 * xdsl2LConfProfRaDsTimeDs 7355 * xdsl2LConfProfRaDsTimeUs 7356 * xdsl2LConfProfTargetSnrmDs 7357 * xdsl2LConfProfTargetSnrmUs 7358 * xdsl2LConfProfMaxSnrmDs 7359 * xdsl2LConfProfMaxSnrmUs 7360 * xdsl2LConfProfMinSnrmDs 7361 * xdsl2LConfProfMinSnrmUs 7362 * xdsl2LConfProfMsgMinUs 7363 * xdsl2LConfProfMsgMinDs 7364 * xdsl2LConfProfAtuTransSysEna 7365 * xdsl2LConfProfPmMode 7366 * xdsl2LConfProfL0Time 7367 * xdsl2LConfProfL2Time 7368 * xdsl2LConfProfL2Atpr 7369 * xdsl2LConfProfL2Atprt 7370 * xdsl2LConfProfRowStatus 7372 Unauthorized changes resulting in the setting of any of the above 7373 objects to an incorrect value could have an adverse operational 7374 effect on several lines. 7376 Also, unauthorized changes to xdsl2LConfProfRowStatus could result 7377 in unwanted line profiles being created or brought into service 7378 prematurely; or could result in line profiles being inadvertently 7379 deleted or taken out of service. 7381 o xdsl2LineConfProfModeSpecTable 7383 The table consists of the following objects that support SET 7384 operations: 7386 * xdsl2LConfProfMaxNomPsdDs 7387 * xdsl2LConfProfMaxNomPsdUs 7388 * xdsl2LConfProfMaxNomAtpDs 7389 * xdsl2LConfProfMaxNomAtpUs 7390 * xdsl2LConfProfMaxAggRxPwrUs 7391 * xdsl2LConfProfPsdMaskDs 7392 * xdsl2LConfProfPsdMaskUs 7393 * xdsl2LConfProfPsdMaskSelectUs 7394 * xdsl2LConfProfModeSpecRowStatus 7396 Unauthorized changes resulting in the setting of any of the above 7397 objects to an incorrect value could have an adverse operational 7398 effect on several lines. 7400 Also, unauthorized changes to xdsl2LConfProfModeSpecRowStatus 7401 could result in unwanted PSD configurations being created or 7402 brought into service prematurely; or could result in PSD 7403 configurations being inadvertently deleted or taken out of 7404 service. 7406 o xdsl2ChConfProfileTable 7408 The table consists of the following objects that support SET 7409 operations: 7411 * xdsl2ChConfProfMinDataRateDs 7412 * xdsl2ChConfProfMinDataRateUs 7413 * xdsl2ChConfProfMinResDataRateDs 7414 * xdsl2ChConfProfMinResDataRateUs 7415 * xdsl2ChConfProfMaxDataRateDs 7416 * xdsl2ChConfProfMaxDataRateUs 7417 * xdsl2ChConfProfMinDataRateLowPwrDs 7418 * xdsl2ChConfProfMaxDelayDs 7419 * xdsl2ChConfProfMaxDelayUs 7420 * xdsl2ChConfProfMinProtectionDs 7421 * xdsl2ChConfProfMinProtectionUs 7422 * xdsl2ChConfProfMaxBerDs 7423 * xdsl2ChConfProfMaxBerUs 7424 * xdsl2ChConfProfUsDataRateDs 7425 * xdsl2ChConfProfDsDataRateDs 7426 * xdsl2ChConfProfUsDataRateUs 7427 * xdsl2ChConfProfDsDataRateUs 7428 * xdsl2ChConfProfImaEnabled 7429 * xdsl2ChConfProfRowStatus 7431 Unauthorized changes resulting in the setting of any of the above 7432 objects to an incorrect value could have an adverse operational 7433 effect on several lines. 7435 Also, unauthorized changes to xdsl2ChConfProfRowStatus could 7436 result in unwanted channel profiles being created or brought into 7437 service prematurely; or could result in channel profiles being 7438 inadvertently deleted or taken out of service. 7440 o xdsl2LineAlarmConfTemplateTable 7442 The table consists of the following objects that support SET 7443 operations: 7445 * xdsl2LAlarmConfTempLineProfile 7446 * xdsl2LAlarmConfTempChan1ConfProfile 7447 * xdsl2LalarmConfTempChan2ConfProfile 7448 * xdsl2LalarmConfTempChan3ConfProfile 7449 * xdsl2LalarmConfTempChan4ConfProfile 7450 * xdsl2LAlarmConfTempRowStatus 7452 Unauthorized changes to xdsl2LAlarmConfTempLineProfile, 7453 xdsl2LAlarmConfTempChan1ConfProfile, 7454 xdsl2LAlarmConfTempChan2ConfProfile, 7455 xdsl2LAlarmConfTempChan3ConfProfile, or 7456 xdsl2LAlarmConfTempChan4ConfProfile could have an adverse effect 7457 on the management of notifications generated at the scope of 7458 several to many lines; or could change several to many lines over 7459 to running with unwanted management rates for generated 7460 notifications. 7462 Unauthorized changes to xdsl2LAlarmConfTempRowStatus could result 7463 in alarm templates being created or brought into service 7464 prematurely; or could result in alarm templates being 7465 inadvertently deleted or taken out of service. 7467 o xdsl2LineAlarmConfProfileTable 7469 The table consists of the following objects that support SET 7470 operations: 7472 * xdsl2LineAlarmConfProfileXtucThresh15MinFecs 7473 * xdsl2LineAlarmConfProfileXtucThresh15MinEs 7474 * xdsl2LineAlarmConfProfileXtucThresh15MinSes 7475 * xdsl2LineAlarmConfProfileXtucThresh15MinLoss 7476 * xdsl2LineAlarmConfProfileXtucThresh15MinUas 7477 * xdsl2LineAlarmConfProfileXturThresh15MinFecs 7478 * xdsl2LineAlarmConfProfileXturThresh15MinEs 7479 * xdsl2LineAlarmConfProfileXturThresh15MinSes 7480 * xdsl2LineAlarmConfProfileXturThresh15MinLoss 7481 * xdsl2LineAlarmConfProfileXturThresh15MinUas 7482 * xdsl2LineAlarmConfProfileThresh15MinFailedFullInt 7483 * xdsl2LineAlarmConfProfileThresh15MinFailedShrtInt 7484 * xdsl2LineAlarmConfProfileRowStatus 7486 Increasing any of the threshold values could result in a 7487 notification being suppressed or deferred. Setting a threshold to 7488 0 could result in a notification being suppressed. Suppressing or 7489 deferring a notification could prevent the timely delivery of 7490 important diagnostic information. Decreasing any of the threshold 7491 values could result in a notification being sent from the network 7492 falsely reporting a threshold crossing. 7494 Changing a threshold value could also have an impact on the amount 7495 of notifications the agent sends. The Notifications Section of 7496 this document has a paragraph which provides general guidance on 7497 the rate limiting of notifications. Agent implementations not 7498 providing rate limiting could result in notifications being 7499 generated at an uncontrolled rate. Unauthorized changes to a 7500 threshold value could result in an undesired notification rate. 7502 Unauthorized changes to row status could result in unwanted line 7503 alarm profiles being created or brought into service. Also, 7504 changes to the row status could result in line alarm profiles 7505 being inadvertently deleted or taken out of service. 7507 o xdsl2ChAlarmConfProfileTable 7509 The table consists of the following objects that support SET 7510 operations: 7512 * xdsl2ChAlarmConfProfileXtucThresh15MinCodingViolations 7513 * xdsl2ChAlarmConfProfileXtucThresh15MinCorrected 7514 * xdsl2ChAlarmConfProfileXturThresh15MinCodingViolations 7515 * xdsl2ChAlarmConfProfileXturThresh15MinCorrected 7516 * xdsl2ChAlarmConfProfileRowStatus 7517 * xdsl2LineAlarmConfProfileXturThresh15MinFecs 7518 * xdsl2LineAlarmConfProfileXturThresh15MinEs 7519 * xdsl2LineAlarmConfProfileXturThresh15MinSes 7520 * xdsl2LineAlarmConfProfileXturThresh15MinLoss 7521 * xdsl2LineAlarmConfProfileXturThresh15MinUas 7522 * xdsl2LineAlarmConfProfileThresh15MinFailedFullInt 7523 * xdsl2LineAlarmConfProfileThresh15MinFailedShrtInt 7524 * xdsl2LineAlarmConfProfileRowStatus 7526 Increasing any of the threshold values could result in a 7527 notification being suppressed or deferred. Setting a threshold to 7528 0 could result in a notification being suppressed. Suppressing or 7529 deferring a notification could prevent the timely delivery of 7530 important diagnostic information. Decreasing any of the threshold 7531 values could result in a notification being sent from the network 7532 falsely reporting a threshold crossing. 7534 Changing a threshold value could also have an impact on the amount 7535 of notifications the agent sends. The Notifications Section of 7536 this document has a paragraph which provides general guidance on 7537 the rate limiting of notifications. Agent implementations not 7538 providing rate limiting could result in notifications being 7539 generated at an uncontrolled rate. Unauthorized changes to a 7540 threshold value could result in an undesired notification rate. 7542 Unauthorized changes to row status could result in unwanted 7543 channel alarm profiles being created or brought into service. 7544 Also, changes to the row status could result in channel alarm 7545 profiles being inadvertently deleted or taken out of service. 7547 Some of the readable objects in this MIB module (i.e., objects with a 7548 MAX-ACCESS other than not-accessible) may be considered sensitive or 7549 vulnerable in some network environments. It is thus important to 7550 control even GET and/or NOTIFY access to these objects and possibly 7551 to even encrypt the values of these objects when sending them over 7552 the network via SNMP. These are the tables and objects and their 7553 sensitivity/vulnerability: 7555 o xdsl2LineInventoryTable 7557 Access to these objects would allow an intruder to obtain 7558 information about which vendor's equipment is in use on the 7559 network. Further, such information is considered sensitive in 7560 many environments for competitive reasons. 7562 * xdsl2LInvG994VendorId 7563 * xdsl2LInvSystemVendorId 7564 * xdsl2LInvVersionNumber 7565 * xdsl2LInvSerialNumber 7566 * xdsl2LInvSelfTestResult 7567 * xdsl2LInvTransmissionCapabilities 7569 SNMP versions prior to SNMPv3 did not include adequate security. 7570 Even if the network itself is secure (for example by using IPSec), 7571 even then, there is no control as to who on the secure network is 7572 allowed to access and GET/SET (read/change/create/delete) the objects 7573 in this MIB module. 7575 It is RECOMMENDED that implementers consider the security features as 7576 provided by the SNMPv3 framework (see [RFC3410], Section 8), 7577 including full support for the SNMPv3 cryptographic mechanisms (for 7578 authentication and privacy). 7580 It is RECOMMENDED to deploy SNMPv3 and to enable cryptographic 7581 security. It is then a customer/operator responsibility to ensure 7582 that the SNMP entity giving access to an instance of this MIB module 7583 is properly configured to give access only to those objects whose 7584 principals (users) have legitimate rights to indeed GET or SET 7585 (change/create/delete) them. 7587 6. Acknowledgments 7589 The authors are deeply grateful to the authors of the HDSL2 LINE MIB 7590 (RFC 4319), Clay Sikes and Bob Ray, for contributing to accelerating 7591 the work on this document. The structure of this document as well as 7592 several paragraphs originate in their document. 7594 Other contributions and advice were received from the following: 7596 Randy Presuhn (Mindspring) 7597 Chen Jian (Huawei) 7598 Bert Wijnen (Lucent) 7599 Clay Sikes (Zhone) 7601 7. References 7603 7.1. Normative References 7605 [G.992.1] "Asymmetric digital subscriber line (ADSL) transceivers", 7606 ITU-T G.992.1, 1999. 7608 [G.992.2] "Splitterless asymmetric digital subscriber line (ADSL) 7609 transceivers", ITU-T G.992.2, 1999. 7611 [G.992.3] "Asymmetric digital subscriber line transceivers 2 7612 (ADSL2)", ITU-T G.992.3, 2002. 7614 [G.992.4] "Splitterless asymmetric digital subscriber line 7615 transceivers 2 (Splitterless ADSL2)", ITU-T G.992.4, 2002. 7617 [G.992.5] "Asymmetric digital subscriber line (ADSL) transceivers - 7618 Extended bandwidth ADSL2 (ADSL2+)", ITU-T G.992.5, 2003. 7620 [G.993.1] "Very-high speed Digital Subscriber Line Transceivers", 7621 ITU-T G.993.1, June 2004. 7623 [G.993.2] "Very-high speed Digital Subscriber Line Transceivers 2 7624 (VDSL2 draft)", ITU-T G.993.2, February 2006. 7626 [G.997.1] "Physical layer management for digital subscriber line 7627 (DSL) transceivers", ITU-T G.997.1, May 2003. 7629 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 7630 Requirement Levels", BCP 14, RFC 2119, March 1997. 7632 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 7633 Schoenwaelder, Ed., "Structure of Management Information 7634 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 7636 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 7637 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 7638 STD 58, RFC 2579, April 1999. 7640 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 7641 "Conformance Statements for SMIv2", STD 58, RFC 2580, 7642 April 1999. 7644 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 7645 MIB", RFC 2863, June 2000. 7647 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 7648 Architecture for Describing Simple Network Management 7649 Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, 7650 December 2002. 7652 [RFC3593] Tesink, K., "Textual Conventions for MIB Modules Using 7653 Performance History Based on 15 Minute Intervals", 7654 RFC 3593, September 2003. 7656 [RFC3705] Ray, B. and R. Abbi, "High Capacity Textual Conventions 7657 for MIB Modules Using Performance History Based on 15 7658 Minute Intervals", RFC 3705, February 2004. 7660 [T1E1.413] 7661 J. Bingham & F. Van der Putten, "Network and Customer 7662 Installation Interfaces - Asymmetric Digital Subscriber 7663 Line (ADSL) Metallic Interface. (T1.413 Issue 2)", 7664 ANSI T1E1.413-1998, June 1998. 7666 [TR-129] Adams, P., "Protocol Independent Object Model for Managing 7667 VDSL2", DSL Forum TR-129, March 2005. 7669 7.2. Informative References 7671 [RFC2662] Bathrick, G. and F. Ly, "Definitions of Managed Objects 7672 for the ADSL Lines", RFC 2662, August 1999. 7674 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 7675 "Introduction and Applicability Statements for Internet- 7676 Standard Management Framework", RFC 3410, December 2002. 7678 [RFC3418] Presuhn, R., "Management Information Base (MIB) for the 7679 Simple Network Management Protocol (SNMP)", STD 62, 7680 RFC 3418, December 2002. 7682 [RFC3728] Ray, B. and R. Abbi, "Definitions of Managed Objects for 7683 Very High Speed Digital Subscriber Lines (VDSL)", 7684 RFC 3728, February 2004. 7686 Authors' Addresses 7688 Moti Morgenstern 7689 ECI Telecom Ltd. 7690 30 Hasivim St. 7691 Petach Tikva 49517 7692 Israel 7694 Phone: +972 3 926 6258 7695 Fax: +972 3 928 7342 7696 Email: moti.Morgenstern@ecitele.com 7698 Scott Baillie 7699 NEC Australia 7700 649-655 Springvale Road 7701 Mulgrave, Victoria 3170 7702 Australia 7704 Phone: +61 3 9264 3986 7705 Fax: +61 3 9264 3892 7706 Email: scott.baillie@nec.com.au 7708 Umberto Bonollo 7709 NEC Australia 7710 649-655 Springvale Road 7711 Mulgrave, Victoria 3170 7712 Australia 7714 Phone: +61 3 9264 3385 7715 Fax: +61 3 9264 3892 7716 Email: umberto.bonollo@nec.com.au 7718 Intellectual Property Statement 7720 The IETF takes no position regarding the validity or scope of any 7721 Intellectual Property Rights or other rights that might be claimed to 7722 pertain to the implementation or use of the technology described in 7723 this document or the extent to which any license under such rights 7724 might or might not be available; nor does it represent that it has 7725 made any independent effort to identify any such rights. Information 7726 on the procedures with respect to rights in RFC documents can be 7727 found in BCP 78 and BCP 79. 7729 Copies of IPR disclosures made to the IETF Secretariat and any 7730 assurances of licenses to be made available, or the result of an 7731 attempt made to obtain a general license or permission for the use of 7732 such proprietary rights by implementers or users of this 7733 specification can be obtained from the IETF on-line IPR repository at 7734 http://www.ietf.org/ipr. 7736 The IETF invites any interested party to bring to its attention any 7737 copyrights, patents or patent applications, or other proprietary 7738 rights that may cover technology that may be required to implement 7739 this standard. Please address the information to the IETF at 7740 ietf-ipr@ietf.org. 7742 Disclaimer of Validity 7744 This document and the information contained herein are provided on an 7745 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 7746 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 7747 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 7748 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 7749 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 7750 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 7752 Copyright Statement 7754 Copyright (C) The Internet Society (2006). This document is subject 7755 to the rights, licenses and restrictions contained in BCP 78, and 7756 except as set forth therein, the authors retain all their rights. 7758 Acknowledgment 7760 Funding for the RFC Editor function is currently provided by the 7761 Internet Society.