idnits 2.17.1 draft-ietf-adslmib-vdsl-06.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 7 instances of too long lines in the document, the longest one being 3 characters in excess of 72. ** The abstract seems to contain references (RFC2580], ETSI2701,, ETSI2702,, ITU9931,, ITU9971], [T1E1311,T1E1011,, [RFC2578,RFC2579,, T1E1013,), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Unrecognized Status in 'Category: Internet Draft', assuming Proposed Standard (Expected one of 'Standards Track', 'Full Standard', 'Draft Standard', 'Proposed Standard', 'Best Current Practice', 'Informational', 'Experimental', 'Informational', 'Historic'.) -- 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 (October 2002) is 7864 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) -- Looks like a reference, but probably isn't: '12' on line 4039 -- Looks like a reference, but probably isn't: '15' on line 4040 == Unused Reference: 'ETSI2701' is defined on line 3892, but no explicit reference was found in the text == Unused Reference: 'ETSI2702' is defined on line 3897, but no explicit reference was found in the text == Unused Reference: 'ITU9931' is defined on line 3902, but no explicit reference was found in the text == Unused Reference: 'ITU9971' is defined on line 3905, but no explicit reference was found in the text == Unused Reference: 'RFC2662' is defined on line 3952, but no explicit reference was found in the text == Unused Reference: 'T1E1311' is defined on line 3958, but no explicit reference was found in the text == Unused Reference: 'T1E1011' is defined on line 3963, but no explicit reference was found in the text == Unused Reference: 'T1E1013' is defined on line 3968, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'ETSI2701' -- Possible downref: Non-RFC (?) normative reference: ref. 'ETSI2702' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU9931' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU9971' ** Downref: Normative reference to an Historic RFC: RFC 1901 ** Obsolete normative reference: RFC 1905 (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 1906 (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2493 (Obsoleted by RFC 3593) ** Obsolete normative reference: RFC 2571 (Obsoleted by RFC 3411) ** Obsolete normative reference: RFC 2572 (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (Obsoleted by RFC 3414) -- Possible downref: Non-RFC (?) normative reference: ref. 'T1E1311' -- Possible downref: Non-RFC (?) normative reference: ref. 'T1E1011' -- Possible downref: Non-RFC (?) normative reference: ref. 'T1E1013' -- Obsolete informational reference (is this intentional?): RFC 2570 (Obsoleted by RFC 3410) -- Obsolete informational reference (is this intentional?): RFC 2573 (Obsoleted by RFC 3413) -- Obsolete informational reference (is this intentional?): RFC 2575 (Obsoleted by RFC 3415) Summary: 11 errors (**), 0 flaws (~~), 10 warnings (==), 14 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group B. Ray 2 Category: Internet Draft PESA Switching Systems 3 R. Abbi 4 Alcatel 5 October 2002 7 Definitions of Managed Objects for Very High 8 Speed Digital Subscriber Lines (VDSL) 9 draft-ietf-adslmib-vdsl-06.txt 11 Status of this Memo 13 This document is an Internet-Draft and is subject to all provisions 14 of Section 10 of RFC2026. 16 Internet-Drafts are working documents of the Internet Engineering 17 Task Force (IETF), its areas, and its working groups. Note that 18 other groups may also distribute working documents as Internet- 19 Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six months 22 and may be updated, replaced, or obsoleted by other documents at any 23 time. It is inappropriate to use Internet-Drafts as reference 24 material or to cite them other than as "work in progress." 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/1id-abstracts.txt 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html 32 Copyright Notice 34 Copyright (C) The Internet Society (2002). All Rights Reserved. 36 Abstract 38 This document defines a Management Information Base (MIB) module for 39 use with network management protocols in the Internet community. In 40 particular, it describes objects used for managing Very high speed 41 Digital Subscriber Line (VDSL) interfaces [T1E1311, T1E1011, T1E1013, 42 ETSI2701, ETSI2702, ITU9931, ITU9971]. 44 This document specifies a MIB module in a manner that is compliant 45 to the SMIv2 (STD 58 [RFC2578, RFC2579, RFC2580]). 47 Table of Contents 49 1. The SNMP Management Framework ............................. 2 50 2. Overview .................................................. 3 51 2.1 Relationship of the VDSL Line MIB to other MIBs ........... 3 52 2.2 Conventions used in the MIB ............................... 5 53 2.3 Structure ................................................. 6 54 2.4 Counters, Interval Buckets and Thresholds ................. 8 55 2.5 Profiles .................................................. 8 56 2.6 Notifications ............................................. 9 57 2.7 Persistence ............................................... 10 58 3. Conformance and Compliance ................................ 12 59 4. Definitions ............................................... 13 60 References ................................................ 77 61 Security Considerations ................................... 79 62 IANA Considerations ....................................... 80 63 Acknowledgments ........................................... 80 64 Intellectual Property Notice .............................. 81 65 Authors' Addresses ........................................ 81 66 Full Copyright Statement .................................. 81 68 1. The SNMP Management Framework 70 The SNMP Management Framework presently consists of five major 71 components: 73 o An overall architecture, described in RFC 2571 [RFC2571]. 75 o Mechanisms for describing and naming objects and events for the 76 purpose of management. The first version of this Structure of 77 Management Information (SMI) is called SMIv1 and described in 78 STD 16 [RFC1155, RFC1212] and RFC 1215 [RFC1215]. The second 79 version, called SMIv2, is described in STD 58 [RFC2578, RFC2579, 80 RFC2580]. 82 o Message protocols for transferring management information. The 83 first version of the SNMP message protocol is called SNMPv1 and 84 described in STD 15 [RFC1157]. A second version of the SNMP 85 message protocol, which is not an Internet standards track 86 protocol, is called SNMPv2c and described in RFC 1901 [RFC1901] 87 and RFC 1906 [RFC1906]. The third version of the message 88 protocol is called SNMPv3 and described in RFC 1906 [RFC1906], 89 RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. 91 o Protocol operations for accessing management information. The 92 first set of protocol operations and associated PDU formats is 93 described in STD 15 [RFC1157]. A second set of protocol 94 operations and associated PDU formats is described in RFC 1905 95 [RFC1905]. 97 o A set of fundamental applications described in RFC 2573 [RFC2573] 98 and the view-based access control mechanism described in RFC 99 2575 [RFC2575]. 101 A more detailed introduction to the current SNMP Management Framework 102 can be found in RFC 2570 [RFC2570]. 104 Managed objects are accessed via a virtual information store, termed 105 the Management Information Base or MIB. Objects in the MIB are 106 defined using the mechanisms defined in the SMI. 108 This memo specifies a MIB module that is compliant to the SMIv2. A 109 MIB conforming to the SMIv1 can be produced through the appropriate 110 translations. The resulting translated MIB must be semantically 111 equivalent, except where objects or events are omitted because no 112 translation is possible (use of Counter64). Some machine readable 113 information in SMIv2 will be converted into textual descriptions in 114 SMIv1 during the translation process. However, this loss of machine 115 readable information is not considered to change the semantics of the 116 MIB. 118 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 119 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 120 this document are to be interpreted as described in RFC 2119 121 [RFC2119]. 123 2. Overview 125 This document describes an SNMP MIB for managing VDSL Lines. These 126 definitions are based upon the specifications for VDSL as defined 127 in T1E1, ETSI, and ITU documentation [T1E1311, T1E1011, T1E1013, 128 ETSI2701, ETSI2702, ITU9931, ITU9971]. 130 The MIB is located in the MIB tree under MIB 2 transmission, as 131 discussed in the MIB-2 Integration (RFC 2863 [RFC2863]) section of 132 this document. 134 2.1 Relationship of the VDSL Line MIB to other MIBs 136 This section outlines the relationship of this MIB with other MIBs 137 described in RFCs. Specifically, IF-MIB as presented RFC 2863 138 [RFC2863] is discussed. 140 2.1.1 General IF-MIB Integration (RFC 2863) 142 The VDSL Line MIB specifies the detailed attributes of a data 143 interface. As such, it needs to integrate with RFC 2863 [RFC2863]. 144 The IANA has assigned the following ifType to VDSL: 146 IANAifType ::= TEXTUAL-CONVENTION 147 ... 149 SYNTAX INTEGER { 150 ... 151 vdsl(97), -- Very H-speed Digital Subscrib. Loop 152 ... 153 } 155 Additionally, a VDSL line may contain an optional fast channel 156 and an optional interleaved channel which also integrate into RFC 157 2863 [RFC2863]. The IANA has assigned the following ifTypes to these 158 channels: 160 IANAifType ::= TEXTUAL-CONVENTION 161 ... 162 SYNTAX INTEGER { 163 ... 164 interleave (124), -- Interleave channel 165 fast (125), -- Fast channel 166 ... 167 } 169 2.1.2 Usage of ifTable 171 The MIB branch identified by this ifType contains tables appropriate 172 for this interface type. Most such tables extend the ifEntry table, 173 and are indexed by ifIndex. For interfaces in systems implementing 174 this MIB, those table entries indexed by ifIndex MUST be persistent. 176 The following attributes are part of the mandatory ifGeneral group in 177 RFC 2863 [RFC2863], and are not duplicated in the VDSL Line MIB. 179 =================================================================== 180 ifIndex Interface index. 182 ifDescr See interfaces MIB [RFC2863]. 184 ifType vdsl(97), 185 interleaved(124), or 186 fast(125) 188 ifSpeed Set as appropriate. 190 ifPhysAddress This object MUST have an octet string 191 with zero length. 193 ifAdminStatus See interfaces MIB [RFC2863]. 195 ifOperStatus See interfaces MIB [RFC2863]. 197 ifLastChange See interfaces MIB [RFC2863]. 199 ifName See interfaces MIB [RFC2863]. 201 ifLinkUpDownTrapEnable Default to enabled(1). 203 ifHighSpeed Set as appropriate. 205 ifConnectorPresent Set as appropriate. 207 =================================================================== 208 Figure 1: Use of ifTable Objects 210 Section 2.3, below, describes the structure of this MIB in relation 211 to ifEntry in greater detail. 213 2.2 Conventions used in the MIB 215 2.2.1 Naming Conventions 217 A. Vtuc -- (VTUC) modem at near (Central) end of line 218 B. Vtur -- (VTUR) modem at Remote end of line 219 C. Vtu -- One of either Vtuc or Vtur 220 D. Curr -- Current 221 E. Prev -- Previous 222 F. Atn -- Attenuation 223 G. ES -- Errored Second 224 H. SES -- Severely Errored Second 225 I. UAS -- Unavailable Second 226 J. LCS -- Line Code Specific 227 K. Lof -- Loss of Frame 228 L. Lol -- Loss of Link 229 M. Los -- Loss of Signal 230 N. Lpr -- Loss of Power 231 O. xxxs -- interval of Seconds in which xxx occurs 232 (e.g., xxx=Lof, Los, Lpr) 233 P. Max -- Maximum 234 Q. Mgn -- Margin 235 R. Min -- Minimum 236 S. Psd -- Power Spectral Density 237 T. Snr -- Signal to Noise Ratio 238 U. Tx -- Transmit 239 V. Blks -- Blocks 241 2.2.2 Textual Conventions 243 The following textual conventions are defined to reflect the line 244 topology in the MIB (further discussed in the following section) 245 and to define the behavior of the statistics to be maintained 246 by an agent. 248 o VdslLineCodingType : 250 Attributes with this syntax identify the line coding used. 251 Specified as an INTEGER, the three values are: 253 other(1) -- none of the following 254 mcm(2) -- Multiple Carrier Modulation 255 scm(3) -- Single Carrier Modulation 257 o VdslLineEntity : 259 Attributes with this syntax reference the two sides of a line. 260 Specified as an INTEGER, the two values are: 262 vtuc(1) -- central site modem 263 vtur(2) -- remote site modem 265 2.3 Structure 267 The MIB is structured into following MIB groups: 269 o vdslGroup : 271 This group supports all line code independent MIB objects found 272 in this MIB. The following tables contain objects permitted for 273 ifType vdsl(97): 275 - vdslLineTable 276 - vdslPhysTable 277 - vdslPerfDataTable 278 - vdslPerfIntervalTable 279 - vdslPerf1DayIntervalTable 280 - vdslLineConfProfileTable 281 - vdslLineAlarmConfProfileTable 283 The following tables contain objects permitted for ifTypes 284 interleaved(124) and (fast): 286 - vdslChanTable 287 - vdslChanPerfDataTable 288 - vdslChanPerfIntervalTable 289 - vdslChanPerf1DayIntervalTable 291 o vdslMCMGroup : 293 This group supports MIB objects for defining configuration profiles 294 for Multiple Carrier Modulation (MCM) VDSL modems. It contains the 295 following tables: 297 - vdslLineMCMConfProfileTable 298 - vdslLineMCMConfProfileTxBandTable 299 - vdslLineMCMConfProfileRxBandTable 300 - vdslLineMCMConfProfileTxPSDTable 301 - vdslLineMCMConfProfileMaxTxPSDTable 302 - vdslLineMCMConfProfileMaxRxPSDTable 304 Objects in this group MUST be implemented for MCM VDSL lines. 306 o vdslSCMGroup : 308 This group supports MIB objects for defining configuration profiles 309 for Single Carrier Modulation (SCM) VDSL modems. It contains the 310 following tables: 312 - vdslLineSCMConfProfileTable 313 - vdslLineSCMConfProfileTxBandTable 315 This group also supports the following line code dependent tables: 317 - vdslSCMPhysBandTable 319 Objects in this group MUST be implemented for SCM VDSL lines. 321 Figure 2, below, displays the relationship of the tables in the 322 vdslGroup to ifEntry (and each other): 324 ifEntry(ifType=97) ----> vdslLineTableEntry 1:(0..1) 326 vdslLineTableEntry ----> vdslPhysTableEntry 1:(0..2) 327 ----> vdslPerfDataEntry 1:(0..2) 328 ----> vdslLineConfProfileEntry 1:(0..1) 329 ----> vdslLineAlarmConfProfileEntry 1:(0..1) 331 vdslPhysTableEntry ----> vdslPerfIntervalEntry 1:(0..96) 332 ----> vdslPerf1DayIntervalEntry 1:(0..30) 334 ifEntry(ifType=124) ----> vdslChanEntry 1:(0..2) 335 ----> vdslChanPerfDataEntry 1:(0..2) 337 ifEntry(ifType=125) ----> vdslChanEntry 1:(0..2) 338 ----> vdslChanPerfDataEntry 1:(0..2) 340 vdslChanEntry ----> vdslchanPerfIntervalEntry 1:(0..96) 341 ----> vdslchan1DayPerfIntervalEntry 1:(0..30) 343 Figure 2: Table Relationships 345 2.3.1 Line Topology 347 A VDSL Line consists of a two units - Vtuc (the central termination 348 unit) and a Vtur (the remote termination unit). 350 <-- Network Side Customer Side --> 352 || 354 +-------+ +-------+ 355 | | | | 356 | Vtuc +------------------+ Vtur | 357 | | | | 358 +-------+ +-------+ 360 Figure 3: General topology for a VDSL Line 362 2.4 Counters, Interval Buckets and Thresholds 364 For Loss of Frame (lof), Loss of Link (lol), Loss of Signal (los), 365 and Loss of Power (lpr), Errored Seconds (ES), Severely Errored 366 Seconds (SES), and Unavailable Seconds (UAS) there are event counters, 367 current 15-minute, 0 to 96 15-minute history bucket(s), and 0 to 30 368 1-day history bucket(s) of "interval-counters". Each current 369 15-minute event bucket has an associated threshold notification. 371 Each of these counters uses the textual conventions defined in the 372 HC-PerfHist-TC-MIB. The HC-PerfHist-TC-MIB is a work-in-progress, 373 but simply defines 64-bit versions of the textual conventions 374 found in RFC 2493 [RFC2493]. 376 There is no requirement for an agent to ensure a fixed relationship 377 between the start of a fifteen minute and any wall clock; however 378 some implementations may align the fifteen minute intervals with 379 quarter hours. Likewise, an implementation may choose to align one 380 day intervals with the start of a day. 382 Counters are not reset when an Vtu is reinitialized, only when the 383 agent is reset or reinitialized (or under specific request outside 384 the scope of this MIB). 386 2.5 Profiles 388 As a managed node can handle a large number of Vtus, (e.g., hundreds 389 or perhaps thousands of lines), provisioning every parameter on every 390 Vtu may become burdensome. Moreover, most lines are provisioned 391 identically with the same set of parameters. To simplify the 392 provisioning process, this MIB makes use of profiles. A profile is a 393 set of parameters that can be shared by multiple lines using the same 394 configuration. 396 The following profiles are used in this MIB: 398 o Line Configuration Profiles - Line configuration profiles contain 399 parameters for configuring VDSL lines. They are defined in nine 400 tables: 402 - vdslLineConfProfileTable 403 - vdslLineMCMConfProfileTable 404 - vdslLineMCMConfProfileTxBandTable 405 - vdslLineMCMConfProfileRxBandTable 406 - vdslLineMCMConfProfileTxPSDTable 407 - vdslLineMCMConfProfileMaxTxPSDTable 408 - vdslLineMCMConfProfileMaxRxPSDTable 409 - vdslLineSCMConfProfileTable 410 - vdslLineSCMConfProfileTxBandTable 412 As noted above, the latter eight tables in the above list are 413 line code specific. 415 The object, vdslLineConfProfileIndex, is used as a common 416 index for all of the above tables. A profile, then, consists 417 of the combination of a line code independent configuration 418 (i.e. an entry in vdslLineConfProfileTable) and a set of line 419 code dependent configurations (i.e. entries in either 420 vdslLineMCMConfProfilexxx or vdslLineSCMConfProfilexxx). 422 o Alarm Configuration Profiles - These profiles contain parameters 423 for configuring alarm thresholds for VDSL modems. These profiles 424 are defined in the vdslLineAlarmConfProfileTable. 426 One or more lines may be configured to share parameters of a single 427 profile by setting its vdslLineConfProfile objects to the value of 428 this profile. If a change is made to the profile, all lines that 429 refer to it will be reconfigured to the changed parameters. Before 430 a profile can be deleted or taken out of service it must be first 431 unreferenced from all associated lines. 433 Implementations MUST provide a default profile with an index value 434 of 1 for each profile type. The values of the associated parameters 435 will be vendor specific unless otherwise indicated in this document. 436 Before a line's profiles have been set, these profiles will be 437 automatically used by setting vdslLineConfProfile and 438 vdslLineAlarmConfProfile to 1 where appropriate. This default 439 profile entry is considered reserved in the context of profiles 440 defined in this MIB. 442 Profiles are created, assigned, and deleted dynamically using the 443 profile name and profile row status in each of the four profile 444 tables. 446 Profile changes MUST take effect immediately. These changes MAY 447 result in a restart (hard reset or soft restart) of the units on the 448 line. 450 2.6 Notifications 452 The ability to generate the SNMP notifications coldStart/WarmStart 453 (per [RFC2863]) which are per agent (e.g., per Digital Subscriber Line 454 Access Multiplexer, or DSLAM, in such a device), and linkUp/linkDown 455 (per [RFC2863]) which are per interface (i.e., VDSL line) is required. 457 The notifications defined in this MIB are for initialization failure 458 and for the threshold crossings associated with the following events: 459 lof, lol, los, lpr, ES, SES, and UAS. Each threshold has its own 460 enable/threshold value. When that value is 0, the notification is 461 disabled. 463 A linkDown notification MAY be generated whenever any of lof, lol, 464 los, lpr, ES, SES, or UAS threshold crossing event (as defined 465 in this MIB) occurs. The corresponding linkUp notification MAY be 466 sent when all link failure conditions are cleared. 468 The vdslCurrStatus is a bitmask representing all outstanding error 469 conditions associated with a particular VDSL modem. Note that since 470 status of remote modems is obtained via the EOC, this information 471 may be unavailable for units that are unreachable via EOC during a 472 line error condition. Therefore, not all conditions may always be 473 included in its current status. Notifications corresponding to the 474 bit fields in this object are defined. 476 A threshold notification occurs whenever the corresponding current 477 15-minute interval error counter becomes equal to, or exceeds the 478 threshold value. One notification may be sent per interval per 479 interface. Since the current 15-minute counter are reset to 0 every 480 15 minutes, if the condition persists, the notification may recur as 481 often as every 15 minutes. For example, to get a notification 482 whenever a "loss of" event occurs (but at most once every 15 483 minutes), set the corresponding threshold to 1. The agent will 484 generate a notification when the event originally occurs. 486 Note that the Network Management System, or NMS, may receive a 487 linkDown notification, as well, if enabled (via 488 ifLinkUpDownTrapEnable [RFC2863]). At the beginning of the next 15 489 minute interval, the counter is reset. When the first second goes 490 by and the event occurs, the current interval bucket will be 1, 491 which equals the threshold and the notification will be sent again. 493 2.7 Persistence 495 All objects defined in this MIB which may be set (read-write or 497 read-create), should be stored persistently. Following is an 498 exhaustive list of these persistent objects: 500 vdslLineConfProfile 501 vdslLineAlarmConfProfile 502 vdslLineConfProfileIndex 503 vdslLineConfProfileName 504 vdslLineConfDownstreamMaxPwr 505 vdslLineConfUpstreamMaxPwr 506 vdslLineConfDownstreamMaxSnrMgn 507 vdslLineConfDownstreamMinSnrMgn 508 vdslLineConfDownstreamTargetSnrMgn 509 vdslLineConfUpstreamMaxSnrMgn 510 vdslLineConfUpstreamMinSnrMgn 511 vdslLineConfUpstreamTargetSnrMgn 512 vdslLineConfDownstreamFastMaxDataRate 513 vdslLineConfDownstreamFastMinDataRate 514 vdslLineConfDownstreamSlowMaxDataRate 515 vdslLineConfDownstreamSlowMinDataRate 516 vdslLineConfUpstreamFastMaxDataRate 517 vdslLineConfUpstreamFastMinDataRate 518 vdslLineConfUpstreamSlowMaxDataRate 519 vdslLineConfUpstreamSlowMinDataRate 520 vdslLineConfRateAdaptationRatio 521 vdslLineConfUpstreamDataRate 522 vdslLineConfDownstreamDataRate 523 vdslLineConfDownstreamMaxInterDelay 524 vdslLineConfUpstreamMaxInterDelay 525 vdslLineConfUpstreamPboControl 526 vdslLineConfDownstreamPboControl 527 vdslLineConfDeploymentScenario 528 vdslLineConfAdslOccupy 529 vdslLineConfApplicableStandard 530 vdslLineConfBandPlan 531 vdslLineConfBandPlanFx 532 vdslLineConfBandU0Usage 533 vdslLineConfUpstreamPsdTemplate 534 vdslLineConfDownstreamPsdTemplate 535 vdslLineConfProfileRowStatus 536 vdslMCMConfProfileTxWindowLength 537 vdslMCMConfProfileRowStatus 538 vdslMCMConfProfileTxBandNumber 539 vdslMCMConfProfileTxBandStart 540 vdslMCMConfProfileTxBandStop 541 vdslMCMConfProfileTxBandRowStatus 542 vdslMCMConfProfileRxBandStart 543 vdslMCMConfProfileRxBandStop 544 vdslMCMConfProfileRxBandRowStatus 545 vdslMCMConfProfileTxPSDTone 546 vdslMCMConfProfileTxPSDPSD 547 vdslMCMConfProfileTxPSDRowStatus 548 vdslMCMConfProfileMaxTxPSDTone 549 vdslMCMConfProfileMaxTxPSDPSD 550 vdslMCMConfProfileMaxTxPSDRowStatus 551 vdslMCMConfProfileMaxRxPSDTone 552 vdslMCMConfProfileMaxRxPSDPSD 553 vdslMCMConfProfileMaxRxPSDRowStatus 554 vdslSCMConfProfileInterleaveDepth 555 vdslSCMConfProfileNumCarriers 556 vdslSCMConfProfileFastCodewordSize 557 vdslSCMConfProfileTransmitPSDMask 558 vdslSCMConfProfileVendorNotch1Start 559 vdslSCMConfProfileVendorNotch1Stop 560 vdslSCMConfProfileVendorNotch2Start 561 vdslSCMConfProfileVendorNotch2Stop 562 vdslSCMConfProfileFastFecSize 563 vdslSCMConfProfileSlowBlockSize 564 vdslSCMConfProfileRowStatus 565 vdslSCMConfProfileTxBandTransmitPSDLevel 566 vdslSCMConfProfileTxBandSymbolRateProfile 567 vdslSCMConfProfileTxBandConstellationSize 568 vdslSCMConfProfileTxBandCenterFrequency 569 vdslSCMConfProfileTxBandRowStatus 570 vdslLineAlarmConfProfileName 571 vdslThresh15MinLofs 572 vdslThresh15MinLoss 573 vdslThresh15MinLprs 574 vdslThresh15MinESs 575 vdslThresh15MinSESs 576 vdslThresh15MinUASs 577 vdslInitFailureNotificationEnable 578 vdslLineAlarmConfProfileRowStatus 580 It should also be noted that interface indices in this MIB are 581 maintained persistently. VACM data relating to these should be 582 stored persistently as well. 584 3. Conformance and Compliance 586 For VDSL lines, the following group is mandatory: 588 - vdslGroup 590 For MCM VDSL lines, the following group is optional: 592 - vdslSCMGroup 594 For SCM VDSL lines, the following group is optional: 596 - vdslMCMGroup 598 4. Definitions 600 VDSL-LINE-MIB DEFINITIONS ::= BEGIN 602 IMPORTS 604 MODULE-IDENTITY, 605 OBJECT-TYPE, 606 Counter64, 607 Gauge32, 608 Integer32, 609 Unsigned32, 610 NOTIFICATION-TYPE, 611 transmission FROM SNMPv2-SMI 612 TEXTUAL-CONVENTION, 613 RowStatus, 614 TruthValue FROM SNMPv2-TC 615 HCPerfValidIntervals, 616 HCPerfInvalidIntervals, 617 HCPerfTimeElapsed, 618 HCPerfIntervalThreshold, 619 HCPerfCurrentCount, 620 HCPerfIntervalCount FROM HC-PerfHist-TC-MIB 621 MODULE-COMPLIANCE, 622 OBJECT-GROUP, 623 NOTIFICATION-GROUP FROM SNMPv2-CONF 624 ifIndex FROM IF-MIB 625 SnmpAdminString FROM SNMP-FRAMEWORK-MIB; 627 vdslMIB MODULE-IDENTITY 628 LAST-UPDATED "200210300000Z" -- October 30, 2002 629 ORGANIZATION "ADSLMIB Working Group" 630 CONTACT-INFO "WG-email: adslmib@ietf.org 631 Info: https://www1.ietf.org/mailman/listinfo/adslmib 633 Chair: Mike Sneed 634 Postal: P.O. Box 37324 635 Raleigh NC 27627-7324 636 Email: sneedmike@hotmail.com 638 Co-editor: Bob Ray 639 PESA Switching Systems, Inc. 640 Postal: 330-A Wynn Drive 641 Huntsville, AL 35805 USA 642 Email: rray@pesa.com 643 Phone: +1 256 726 9200 ext. 142 645 Co-editor: Rajesh Abbi 646 Alcatel USA 647 Postal: 2912 Wake Forest Road 648 Raleigh, NC 27609-7860 USA 649 Email: Rajesh.Abbi@alcatel.com 650 Phone: +1 919 850 6194 652 " 653 DESCRIPTION 654 "The MIB module defining objects for the management of a pair of 655 VDSL modems at each end of the VDSL line. Each such line has 656 an entry in an ifTable which may include multiple modem lines. 657 An agent may reside at either end of the VDSL line however the 658 MIB is designed to require no management communication between 659 them beyond that inherent in the low-level VDSL line protocol. 660 The agent may monitor and control this protocol for its needs. 662 VDSL lines may support optional Fast or Interleaved channels. 663 If these are supported, additional entries corresponding to the 664 supported channels must be created in the ifTable. Thus a VDSL 665 line that supports both channels will have three entries in the 666 ifTable, one for each physical, fast, and interleaved, whose 667 ifType values are equal to vdsl(97), fast(125), and 668 interleaved(124), respectively. The ifStackTable is used to 669 represent the relationship between the entries. 671 Naming Conventions: 672 Vtuc -- (VTUC) modem at near (Central) end of line 673 Vtur -- (VTUR) modem at Remote end of line 674 Vtu -- One of either Vtuc or Vtur 675 Curr -- Current 676 Prev -- Previous 677 Atn -- Attenuation 678 ES -- Errored Second. 679 LCS -- Line Code Specific 680 Lof -- Loss of Frame 681 Lol -- Loss of Link 682 Los -- Loss of Signal 683 Lpr -- Loss of Power 684 xxxs -- interval of Seconds in which xxx occurs 685 (e.g., xxx=Lof, Los, Lpr) 686 Max -- Maximum 687 Mgn -- Margin 688 Min -- Minimum 689 Psd -- Power Spectral Density 690 Snr -- Signal to Noise Ratio 691 Tx -- Transmit 692 Blks -- Blocks 693 " 694 REVISION "200111010000Z" -- November 1, 2001 695 DESCRIPTION "Initial draft." 697 REVISION "200203310000Z" -- March 31, 2002 698 DESCRIPTION "Added R. Abbi as co-author." 699 REVISION "200204090000Z" -- April 9, 2002 700 DESCRIPTION "Removed use of IMPLIED profile indices." 702 REVISION "200206160000Z" -- June 16, 2002 703 DESCRIPTION "Revised per input from DSL Forum." 705 REVISION "200209230000Z" -- September 23, 2002 706 DESCRIPTION "Revised per more input from DSL Forum." 708 REVISION "200210150000Z" -- October 15, 2002 709 DESCRIPTION "Modified per input from Randy Presuhn and 710 Moti Morgenstern." 712 REVISION "200210300000Z" -- October 30, 2002 713 DESCRIPTION "Modified per input from Umberto Bonollo 714 and Travis Levin." 716 ::= { transmission xxxx } 718 vdslLineMib OBJECT IDENTIFIER ::= { vdslMIB 1 } 719 vdslMibObjects OBJECT IDENTIFIER ::= { vdslLineMib 1 } 721 -- 722 -- textual conventions used in this MIB 723 -- 725 VdslLineCodingType ::= TEXTUAL-CONVENTION 726 STATUS current 727 DESCRIPTION 728 "This data type is used as the syntax for the VDSL 729 Line Code." 730 SYNTAX INTEGER 731 { 732 other(1), -- none of the following 733 mcm(2), -- Multiple Carrier Modulation 734 scm(3) -- Single Carrier Modulation 735 } 737 VdslLineEntity ::= TEXTUAL-CONVENTION 738 STATUS current 739 DESCRIPTION 740 "Identifies a modem as being either Vtuc or Vtur. A 741 VDSL line consists of two modems, a Vtuc and a Vtur." 742 SYNTAX INTEGER 743 { 744 vtuc(1), -- central site modem 745 vtur(2) -- remote site modem 746 } 748 -- 749 -- objects 750 -- 752 vdslLineTable OBJECT-TYPE 753 SYNTAX SEQUENCE OF VdslLineEntry 754 MAX-ACCESS not-accessible 755 STATUS current 756 DESCRIPTION 757 "This table includes common attributes describing 758 both ends of the line. It is required for all VDSL 759 physical interfaces. VDSL physical interfaces are 760 those ifEntries where ifType is equal to vdsl(97)." 761 ::= { vdslMibObjects 1 } 763 vdslLineEntry OBJECT-TYPE 764 SYNTAX VdslLineEntry 765 MAX-ACCESS not-accessible 766 STATUS current 767 DESCRIPTION "An entry in the vdslLineTable." 768 INDEX { ifIndex } 769 ::= { vdslLineTable 1 } 771 VdslLineEntry ::= 772 SEQUENCE 773 { 774 vdslLineCoding VdslLineCodingType, 775 vdslLineType INTEGER, 776 vdslLineConfProfile Unsigned32, 777 vdslLineAlarmConfProfile Unsigned32 778 } 780 vdslLineCoding OBJECT-TYPE 781 SYNTAX VdslLineCodingType 782 MAX-ACCESS read-only 783 STATUS current 784 DESCRIPTION 785 "Specifies the VDSL coding type used on this line." 786 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 787 ::= { vdslLineEntry 1 } 789 vdslLineType OBJECT-TYPE 790 SYNTAX INTEGER 791 { 792 noChannel(1), -- no channels exist 793 fastOnly(2), -- fast channel only 794 slowOnly(3), -- slow channel only 795 either(4), -- either fast or slow channel exist 796 both(5) -- both fast and slow channels exist 797 } 798 MAX-ACCESS read-only 799 STATUS current 800 DESCRIPTION 801 "Defines the type of VDSL physical line 802 entity that exists, by defining whether and how 803 the line is channelized. If the line is channelized, 804 the value will be other than noChannel(1). This 805 object defines which channel type(s) are supported. 807 In the case that the line is channelized, the manager 808 can use the ifStackTable to determine the ifIndex for 809 the associated channel(s). 811 Note that slow and interleaved refer to the same 812 channel." 813 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 814 ::= { vdslLineEntry 2 } 816 vdslLineConfProfile OBJECT-TYPE 817 SYNTAX Unsigned32 818 MAX-ACCESS read-write 819 STATUS current 820 DESCRIPTION 821 "The value of this object identifies the row 822 in the VDSL Line Configuration Profile Table, 823 ( vdslLineConfProfileTable ), which applies for this 824 VDSL line, and channels if applicable." 825 ::= { vdslLineEntry 3 } 827 vdslLineAlarmConfProfile OBJECT-TYPE 828 SYNTAX Unsigned32 829 MAX-ACCESS read-write 830 STATUS current 831 DESCRIPTION 832 "The value of this object identifies the row in the VDSL 833 Line Alarm Configuration Profile Table, 834 ( vdslLineAlarmConfProfileTable ), which applies to this 835 VDSL line, and channels if applicable." 836 ::= { vdslLineEntry 4 } 838 vdslPhysTable OBJECT-TYPE 839 SYNTAX SEQUENCE OF VdslPhysEntry 840 MAX-ACCESS not-accessible 841 STATUS current 842 DESCRIPTION 843 "This table provides one row for each Vtu. Each row 844 contains the Physical Layer Parameters table for that 845 Vtu. VDSL physical interfaces are those ifEntries where 846 ifType is equal to vdsl(97)." 847 ::= { vdslMibObjects 2 } 849 vdslPhysEntry OBJECT-TYPE 850 SYNTAX VdslPhysEntry 851 MAX-ACCESS not-accessible 852 STATUS current 853 DESCRIPTION "An entry in the vdslPhysTable." 854 INDEX { ifIndex, 855 vdslPhysSide } 856 ::= { vdslPhysTable 1 } 858 VdslPhysEntry ::= 859 SEQUENCE 860 { 861 vdslPhysSide VdslLineEntity, 862 vdslInvSerialNumber SnmpAdminString, 863 vdslInvVendorID SnmpAdminString, 864 vdslInvVersionNumber SnmpAdminString, 865 vdslCurrSnrMgn Integer32, 866 vdslCurrAtn Gauge32, 867 vdslCurrStatus BITS, 868 vdslCurrOutputPwr Integer32, 869 vdslCurrAttainableRate Gauge32 870 } 872 vdslPhysSide OBJECT-TYPE 873 SYNTAX VdslLineEntity 874 MAX-ACCESS not-accessible 875 STATUS current 876 DESCRIPTION 877 "Identifies whether the modem is the Vtuc or Vtur." 878 ::= { vdslPhysEntry 1 } 880 vdslInvSerialNumber OBJECT-TYPE 881 SYNTAX SnmpAdminString(SIZE (0..32)) 882 MAX-ACCESS read-only 883 STATUS current 884 DESCRIPTION 885 "The vendor specific string that identifies the 886 vendor equipment." 887 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 888 ::= { vdslPhysEntry 2 } 890 vdslInvVendorID OBJECT-TYPE 891 SYNTAX SnmpAdminString (SIZE (0..16)) 892 MAX-ACCESS read-only 893 STATUS current 894 DESCRIPTION 895 "The vendor ID code is a copy of the binary vendor 896 identification field expressed as readable characters." 897 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 898 ::= { vdslPhysEntry 3 } 900 vdslInvVersionNumber OBJECT-TYPE 901 SYNTAX SnmpAdminString (SIZE (0..16)) 902 MAX-ACCESS read-only 903 STATUS current 904 DESCRIPTION 905 "The vendor specific version number sent by this Vtu 906 as part of the initialization messages. It is a copy 907 of the binary version number field expressed as 908 readable characters." 909 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 910 ::= { vdslPhysEntry 4 } 912 vdslCurrSnrMgn OBJECT-TYPE 913 SYNTAX Integer32 (-127..127) 914 UNITS "0.25dBm" 915 MAX-ACCESS read-only 916 STATUS current 917 DESCRIPTION 918 "Noise Margin as seen by this Vtu with respect to its 919 received signal in 0.25dB. The effective range is 920 -31.75 to +31.75dB." 921 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 922 ::= { vdslPhysEntry 5 } 924 vdslCurrAtn OBJECT-TYPE 925 SYNTAX Gauge32 (0..255) 926 UNITS "0.25dBm" 927 MAX-ACCESS read-only 928 STATUS current 929 DESCRIPTION 930 "Measured difference in the total power transmitted by 931 the peer Vtu and the total power received by this Vtu. 932 The effective range is 0 to +63.75dB." 933 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 934 ::= { vdslPhysEntry 6 } 936 vdslCurrStatus OBJECT-TYPE 937 SYNTAX BITS 938 { 939 noDefect(0), 940 lossOfFraming(1), 941 lossOfSignal(2), 942 lossOfPower(3), 943 lossOfSignalQuality(4), 944 lossOfLink(5), 945 dataInitFailure(6), 946 configInitFailure(7), 947 protocolInitFailure(8), 948 noPeerVtuPresent(9) 949 } 950 MAX-ACCESS read-only 951 STATUS current 952 DESCRIPTION 953 "Indicates current state of the Vtu line. This is a 954 bit-map of possible conditions. The various bit 955 positions are: 957 0 noDefect There no defects on the line 959 1 lossOfFraming Vtu failure due to not receiving 960 a valid frame. 962 2 lossOfSignal Vtu failure due to not receiving 963 signal. 965 3 lossOfPower Vtu failure due to loss of power. 967 4 lossOfSignalQuality Loss of Signal Quality is declared 968 when the Noise Margin falls below 969 the Minimum Noise Margin, or the 970 bit-error-rate exceeds 10^-7. 972 5 lossOfLink Vtu failure due to inability to 973 link with peer Vtu. 975 6 dataInitFailure Vtu failure during initialization 976 due to bit errors corrupting 977 startup exchange data. 979 7 configInitFailure Vtu failure during initialization 980 due to peer Vtu not able to support 981 requested configuration. 983 8 protocolInitFailure Vtu failure during initialization 984 due to incompatible protocol used 985 by the peer Vtu. 987 9 noPeerVtuPresent Vtu failure during initialization 988 due to no activation sequence 989 detected from peer Vtu. 991 This is intended to supplement ifOperStatus." 992 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 993 ::= { vdslPhysEntry 7 } 995 vdslCurrOutputPwr OBJECT-TYPE 996 SYNTAX Integer32 (0..160) 997 UNITS "0.1dBm" 998 MAX-ACCESS read-only 999 STATUS current 1000 DESCRIPTION 1001 "Measured total output power transmitted by this VTU. 1002 This is the measurement that was reported during 1003 the last activation sequence." 1005 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1006 ::= { vdslPhysEntry 8 } 1008 vdslCurrAttainableRate OBJECT-TYPE 1009 SYNTAX Gauge32 1010 UNITS "kbps" 1011 MAX-ACCESS read-only 1012 STATUS current 1013 DESCRIPTION 1014 "Indicates the maximum currently attainable data rate 1015 in steps of 1024 bits/second by the Vtu. This value 1016 will be equal or greater than the current line rate. 1017 Note that for SCM, the minimum and maximum data rates 1018 are equal." 1019 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1020 ::= { vdslPhysEntry 9 } 1022 vdslChanTable OBJECT-TYPE 1023 SYNTAX SEQUENCE OF VdslChanEntry 1024 MAX-ACCESS not-accessible 1025 STATUS current 1026 DESCRIPTION 1027 "This table provides one row for each Vtu channel. 1028 VDSL channel interfaces are those ifEntries where 1029 ifType is equal to interleave(124) or fast(125)." 1030 ::= { vdslMibObjects 3 } 1032 vdslChanEntry OBJECT-TYPE 1033 SYNTAX VdslChanEntry 1034 MAX-ACCESS not-accessible 1035 STATUS current 1036 DESCRIPTION 1037 "An entry in the vdslChanTable." 1038 INDEX { ifIndex, 1039 vdslPhysSide } 1040 ::= { vdslChanTable 1 } 1042 VdslChanEntry ::= 1043 SEQUENCE 1044 { 1045 vdslChanInterleaveDelay Gauge32, 1046 vdslChanCrcBlockLength Gauge32, 1047 vdslChanCurrTxRate Gauge32 1048 } 1050 vdslChanInterleaveDelay OBJECT-TYPE 1051 SYNTAX Gauge32 1052 UNITS "ms" 1053 MAX-ACCESS read-only 1054 STATUS current 1055 DESCRIPTION 1056 "Interleave Delay for this channel. 1058 Interleave delay applies only to the interleave 1059 (slow) channel and defines the mapping (relative 1060 spacing) between subsequent input bytes at the 1061 interleaver input and their placement in the bit 1062 stream at the interleaver output. Larger numbers 1063 provide greater separation between consecutive 1064 input bytes in the output bit stream allowing for 1065 improved impulse noise immunity at the expense of 1066 payload latency. 1068 In the case where the ifType is fast(125), use 1069 noSuchObject." 1070 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1071 ::= { vdslChanEntry 1 } 1073 vdslChanCrcBlockLength OBJECT-TYPE 1074 SYNTAX Gauge32 1075 UNITS "byte" 1076 MAX-ACCESS read-only 1077 STATUS current 1078 DESCRIPTION 1079 "Indicates the length of the channel data-block 1080 on which the CRC operates." 1081 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1082 ::= { vdslChanEntry 2 } 1084 vdslChanCurrTxRate OBJECT-TYPE 1085 SYNTAX Gauge32 1086 UNITS "kbps" 1087 MAX-ACCESS read-only 1088 STATUS current 1089 DESCRIPTION 1090 "Actual transmit data rate on this channel." 1091 ::= { vdslChanEntry 3 } 1093 vdslPerfDataTable OBJECT-TYPE 1094 SYNTAX SEQUENCE OF VdslPerfDataEntry 1095 MAX-ACCESS not-accessible 1096 STATUS current 1097 DESCRIPTION 1098 "This table provides one row for each VDSL physical 1099 interface. VDSL physical interfaces are those ifEntries 1100 where ifType is equal to vdsl(97)." 1101 ::= { vdslMibObjects 4 } 1103 vdslPerfDataEntry OBJECT-TYPE 1104 SYNTAX VdslPerfDataEntry 1105 MAX-ACCESS not-accessible 1106 STATUS current 1107 DESCRIPTION 1108 "An entry in the vdslPerfDataTable." 1109 INDEX { ifIndex, 1110 vdslPhysSide } 1111 ::= { vdslPerfDataTable 1 } 1113 VdslPerfDataEntry ::= 1114 SEQUENCE 1115 { 1116 vdslPerfValidIntervals HCPerfValidIntervals, 1117 vdslPerfInvalidIntervals HCPerfInvalidIntervals, 1118 vdslPerfLofs Counter64, 1119 vdslPerfLoss Counter64, 1120 vdslPerfLprs Counter64, 1121 vdslPerfESs Counter64, 1122 vdslPerfSESs Counter64, 1123 vdslPerfUASs Counter64, 1124 vdslPerfInits Counter64, 1125 vdslPerfCurr15MinTimeElapsed HCPerfTimeElapsed, 1126 vdslPerfCurr15MinLofs HCPerfCurrentCount, 1127 vdslPerfCurr15MinLoss HCPerfCurrentCount, 1128 vdslPerfCurr15MinLprs HCPerfCurrentCount, 1129 vdslPerfCurr15MinESs HCPerfCurrentCount, 1130 vdslPerfCurr15MinSESs HCPerfCurrentCount, 1131 vdslPerfCurr15MinUASs HCPerfCurrentCount, 1132 vdslPerfCurr15MinInits HCPerfCurrentCount, 1133 vdslPerf1DayValidIntervals HCPerfValidIntervals, 1134 vdslPerf1DayInvalidIntervals HCPerfInvalidIntervals, 1135 vdslPerfCurr1DayTimeElapsed HCPerfTimeElapsed, 1136 vdslPerfCurr1DayLofs Counter64, 1137 vdslPerfCurr1DayLoss Counter64, 1138 vdslPerfCurr1DayLprs Counter64, 1139 vdslPerfCurr1DayESs Counter64, 1140 vdslPerfCurr1DaySESs Counter64, 1141 vdslPerfCurr1DayUASs Counter64, 1142 vdslPerfCurr1DayInits Counter64 1143 } 1145 vdslPerfValidIntervals OBJECT-TYPE 1146 SYNTAX HCPerfValidIntervals 1147 MAX-ACCESS read-only 1148 STATUS current 1149 DESCRIPTION 1150 "Valid Intervals per definition found in 1151 HC-PerfHist-TC-MIB." 1152 ::= { vdslPerfDataEntry 1 } 1154 vdslPerfInvalidIntervals OBJECT-TYPE 1155 SYNTAX HCPerfInvalidIntervals 1156 MAX-ACCESS read-only 1157 STATUS current 1158 DESCRIPTION 1159 "Invalid Intervals per definition found in 1160 HC-PerfHist-TC-MIB." 1161 ::= { vdslPerfDataEntry 2 } 1163 vdslPerfLofs OBJECT-TYPE 1164 SYNTAX Counter64 1165 UNITS "seconds" 1166 MAX-ACCESS read-only 1167 STATUS current 1168 DESCRIPTION 1169 "Count of seconds since the unit was last reset that there 1170 was Loss of Framing." 1171 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1172 ::= { vdslPerfDataEntry 3 } 1174 vdslPerfLoss OBJECT-TYPE 1175 SYNTAX Counter64 1176 UNITS "seconds" 1177 MAX-ACCESS read-only 1178 STATUS current 1179 DESCRIPTION 1180 "Count of seconds since the unit was last reset that there 1181 was Loss of Signal." 1182 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1183 ::= { vdslPerfDataEntry 4 } 1185 vdslPerfLprs OBJECT-TYPE 1186 SYNTAX Counter64 1187 UNITS "seconds" 1188 MAX-ACCESS read-only 1189 STATUS current 1190 DESCRIPTION 1191 "Count of seconds since the unit was last reset that there 1192 was Loss of Power." 1193 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1194 ::= { vdslPerfDataEntry 5 } 1196 vdslPerfESs OBJECT-TYPE 1197 SYNTAX Counter64 1198 UNITS "seconds" 1199 MAX-ACCESS read-only 1200 STATUS current 1201 DESCRIPTION 1202 "Count of Errored Seconds since the unit was last reset. 1203 An Errored Second is a one-second interval containing one 1204 or more crc anomalies, or one or more los or lof defects." 1205 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1206 ::= { vdslPerfDataEntry 6 } 1208 vdslPerfSESs OBJECT-TYPE 1209 SYNTAX Counter64 1210 UNITS "seconds" 1211 MAX-ACCESS read-only 1212 STATUS current 1213 DESCRIPTION 1214 "Count of Severely Errored Seconds since the unit was last 1215 reset." 1216 ::= { vdslPerfDataEntry 7 } 1218 vdslPerfUASs OBJECT-TYPE 1219 SYNTAX Counter64 1220 UNITS "seconds" 1221 MAX-ACCESS read-only 1222 STATUS current 1223 DESCRIPTION 1224 "Count of Unavailable Seconds since the unit was last 1225 reset." 1226 ::= { vdslPerfDataEntry 8 } 1228 vdslPerfInits OBJECT-TYPE 1229 SYNTAX Counter64 1230 MAX-ACCESS read-only 1231 STATUS current 1232 DESCRIPTION 1233 "Count of the line initialization attempts since the unit 1234 was last reset. This count includes both successful and 1235 failed attempts." 1236 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1237 ::= { vdslPerfDataEntry 9 } 1239 vdslPerfCurr15MinTimeElapsed OBJECT-TYPE 1240 SYNTAX HCPerfTimeElapsed 1241 UNITS "seconds" 1242 MAX-ACCESS read-only 1243 STATUS current 1244 DESCRIPTION 1245 "Total elapsed seconds in this interval." 1246 ::= { vdslPerfDataEntry 10 } 1248 vdslPerfCurr15MinLofs OBJECT-TYPE 1249 SYNTAX HCPerfCurrentCount 1250 UNITS "seconds" 1251 MAX-ACCESS read-only 1252 STATUS current 1253 DESCRIPTION 1254 "Count of seconds during this interval that there 1255 was Loss of Framing." 1256 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1257 ::= { vdslPerfDataEntry 11 } 1259 vdslPerfCurr15MinLoss OBJECT-TYPE 1260 SYNTAX HCPerfCurrentCount 1261 UNITS "seconds" 1262 MAX-ACCESS read-only 1263 STATUS current 1264 DESCRIPTION 1265 "Count of seconds during this interval that there 1266 was Loss of Signal." 1267 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1268 ::= { vdslPerfDataEntry 12 } 1270 vdslPerfCurr15MinLprs OBJECT-TYPE 1271 SYNTAX HCPerfCurrentCount 1272 UNITS "seconds" 1273 MAX-ACCESS read-only 1274 STATUS current 1275 DESCRIPTION 1276 "Count of seconds during this interval that there 1277 was Loss of Power." 1278 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1279 ::= { vdslPerfDataEntry 13 } 1281 vdslPerfCurr15MinESs OBJECT-TYPE 1282 SYNTAX HCPerfCurrentCount 1283 UNITS "seconds" 1284 MAX-ACCESS read-only 1285 STATUS current 1286 DESCRIPTION 1287 "Count of Errored Seconds during this interval. An Errored 1288 Second is a one-second interval containing one or more crc 1289 anomalies, or one or more los or lof defects." 1290 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1291 ::= { vdslPerfDataEntry 14 } 1293 vdslPerfCurr15MinSESs OBJECT-TYPE 1294 SYNTAX HCPerfCurrentCount 1295 UNITS "seconds" 1296 MAX-ACCESS read-only 1297 STATUS current 1298 DESCRIPTION 1299 "Count of Severely Errored Seconds during this interval." 1300 ::= { vdslPerfDataEntry 15 } 1302 vdslPerfCurr15MinUASs OBJECT-TYPE 1303 SYNTAX HCPerfCurrentCount 1304 UNITS "seconds" 1305 MAX-ACCESS read-only 1306 STATUS current 1307 DESCRIPTION 1308 "Count of Unavailable Seconds during this interval." 1309 ::= { vdslPerfDataEntry 16 } 1311 vdslPerfCurr15MinInits OBJECT-TYPE 1312 SYNTAX HCPerfCurrentCount 1313 MAX-ACCESS read-only 1314 STATUS current 1315 DESCRIPTION 1316 "Count of the line initialization attempts during this 1317 interval. This count includes both successful and 1318 failed attempts." 1319 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1320 ::= { vdslPerfDataEntry 17 } 1322 vdslPerf1DayValidIntervals OBJECT-TYPE 1323 SYNTAX HCPerfValidIntervals 1324 MAX-ACCESS read-only 1325 STATUS current 1326 DESCRIPTION 1327 "Valid Intervals per definition found in 1328 HC-PerfHist-TC-MIB." 1329 ::= { vdslPerfDataEntry 18 } 1331 vdslPerf1DayInvalidIntervals OBJECT-TYPE 1332 SYNTAX HCPerfInvalidIntervals 1333 MAX-ACCESS read-only 1334 STATUS current 1335 DESCRIPTION 1336 "Invalid Intervals per definition found in 1337 HC-PerfHist-TC-MIB." 1338 ::= { vdslPerfDataEntry 19 } 1340 vdslPerfCurr1DayTimeElapsed OBJECT-TYPE 1341 SYNTAX HCPerfTimeElapsed 1342 UNITS "seconds" 1343 MAX-ACCESS read-only 1344 STATUS current 1345 DESCRIPTION 1346 "Number of seconds that have elapsed since the beginning 1347 of the current 1-day interval." 1348 ::= { vdslPerfDataEntry 20 } 1350 vdslPerfCurr1DayLofs OBJECT-TYPE 1351 SYNTAX Counter64 1352 UNITS "seconds" 1353 MAX-ACCESS read-only 1354 STATUS current 1355 DESCRIPTION 1356 "Count of Loss of Framing (LOF) Seconds since the 1357 beginning of the current 1-day interval." 1358 ::= { vdslPerfDataEntry 21 } 1360 vdslPerfCurr1DayLoss OBJECT-TYPE 1361 SYNTAX Counter64 1362 UNITS "seconds" 1363 MAX-ACCESS read-only 1364 STATUS current 1365 DESCRIPTION 1366 "Count of Loss of Signal (LOS) Seconds since the beginning 1367 of the current 1-day interval." 1368 ::= { vdslPerfDataEntry 22 } 1370 vdslPerfCurr1DayLprs OBJECT-TYPE 1371 SYNTAX Counter64 1372 UNITS "seconds" 1373 MAX-ACCESS read-only 1374 STATUS current 1375 DESCRIPTION 1376 "Count of Loss of Power (LPR) Seconds since the beginning 1377 of the current 1-day interval." 1378 ::= { vdslPerfDataEntry 23 } 1380 vdslPerfCurr1DayESs OBJECT-TYPE 1381 SYNTAX Counter64 1382 UNITS "seconds" 1383 MAX-ACCESS read-only 1384 STATUS current 1385 DESCRIPTION 1386 "Count of Errored Seconds (ES) since the beginning 1387 of the current 1-day interval." 1388 ::= { vdslPerfDataEntry 24 } 1390 vdslPerfCurr1DaySESs OBJECT-TYPE 1391 SYNTAX Counter64 1392 UNITS "seconds" 1393 MAX-ACCESS read-only 1394 STATUS current 1395 DESCRIPTION 1396 "Count of Severely Errored Seconds (SES) since the 1397 beginning of the current 1-day interval." 1398 ::= { vdslPerfDataEntry 25 } 1400 vdslPerfCurr1DayUASs OBJECT-TYPE 1401 SYNTAX Counter64 1402 UNITS "seconds" 1403 MAX-ACCESS read-only 1404 STATUS current 1405 DESCRIPTION 1406 "Count of Unavailable Seconds (UAS) since the beginning 1407 of the current 1-day interval." 1408 ::= { vdslPerfDataEntry 26 } 1410 vdslPerfCurr1DayInits OBJECT-TYPE 1411 SYNTAX Counter64 1412 UNITS "seconds" 1413 MAX-ACCESS read-only 1414 STATUS current 1415 DESCRIPTION 1416 "Count of the line initialization attempts since the 1417 beginning of the current 1-day interval. This count 1418 includes both successful and failed attempts." 1419 ::= { vdslPerfDataEntry 27 } 1421 vdslPerfIntervalTable OBJECT-TYPE 1422 SYNTAX SEQUENCE OF VdslPerfIntervalEntry 1423 MAX-ACCESS not-accessible 1424 STATUS current 1425 DESCRIPTION 1426 "This table provides one row for each Vtu performance 1427 data collection interval. VDSL physical interfaces are 1428 those ifEntries where ifType is equal to vdsl(97)." 1429 ::= { vdslMibObjects 5 } 1431 vdslPerfIntervalEntry OBJECT-TYPE 1432 SYNTAX VdslPerfIntervalEntry 1433 MAX-ACCESS not-accessible 1434 STATUS current 1435 DESCRIPTION 1436 "An entry in the vdslPerfIntervalTable." 1437 INDEX { ifIndex, 1438 vdslPhysSide, 1439 vdslIntervalNumber } 1440 ::= { vdslPerfIntervalTable 1 } 1442 VdslPerfIntervalEntry ::= 1443 SEQUENCE 1444 { 1445 vdslIntervalNumber Unsigned32, 1446 vdslIntervalLofs HCPerfIntervalCount, 1447 vdslIntervalLoss HCPerfIntervalCount, 1448 vdslIntervalLprs HCPerfIntervalCount, 1449 vdslIntervalESs HCPerfIntervalCount, 1450 vdslIntervalSESs HCPerfIntervalCount, 1451 vdslIntervalUASs HCPerfIntervalCount, 1452 vdslIntervalInits HCPerfIntervalCount 1453 } 1455 vdslIntervalNumber OBJECT-TYPE 1456 SYNTAX Unsigned32 (1..96) 1457 MAX-ACCESS not-accessible 1458 STATUS current 1459 DESCRIPTION 1460 "Performance Data Interval number 1 is the the most 1461 recent previous interval; interval 96 is 24 hours ago. 1462 Intervals 2..96 are optional." 1463 ::= { vdslPerfIntervalEntry 1 } 1465 vdslIntervalLofs OBJECT-TYPE 1466 SYNTAX HCPerfIntervalCount 1467 UNITS "seconds" 1468 MAX-ACCESS read-only 1469 STATUS current 1470 DESCRIPTION 1471 "Count of seconds in the interval when there was Loss 1472 of Framing." 1473 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1474 ::= { vdslPerfIntervalEntry 2 } 1476 vdslIntervalLoss OBJECT-TYPE 1477 SYNTAX HCPerfIntervalCount 1478 UNITS "seconds" 1479 MAX-ACCESS read-only 1480 STATUS current 1481 DESCRIPTION 1482 "Count of seconds in the interval when there was Loss 1483 of Signal." 1484 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1485 ::= { vdslPerfIntervalEntry 3 } 1487 vdslIntervalLprs OBJECT-TYPE 1488 SYNTAX HCPerfIntervalCount 1489 UNITS "seconds" 1490 MAX-ACCESS read-only 1491 STATUS current 1492 DESCRIPTION 1493 "Count of seconds in the interval when there was Loss 1494 of Power." 1495 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1496 ::= { vdslPerfIntervalEntry 4 } 1498 vdslIntervalESs OBJECT-TYPE 1499 SYNTAX HCPerfIntervalCount 1500 UNITS "seconds" 1501 MAX-ACCESS read-only 1502 STATUS current 1503 DESCRIPTION 1504 "Count of Errored Seconds (ES) in the interval. An Errored 1505 Second is a one-second interval containing one or more crc 1506 anomalies, one or more los or lof defects." 1507 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1508 ::= { vdslPerfIntervalEntry 5 } 1510 vdslIntervalSESs OBJECT-TYPE 1511 SYNTAX HCPerfIntervalCount 1512 UNITS "seconds" 1513 MAX-ACCESS read-only 1514 STATUS current 1515 DESCRIPTION 1516 "Count of Severely Errored Seconds in the interval." 1517 ::= { vdslPerfIntervalEntry 6 } 1519 vdslIntervalUASs OBJECT-TYPE 1520 SYNTAX HCPerfIntervalCount 1521 UNITS "seconds" 1522 MAX-ACCESS read-only 1523 STATUS current 1524 DESCRIPTION 1525 "Count of Unavailable Seconds in the interval." 1526 ::= { vdslPerfIntervalEntry 7 } 1528 vdslIntervalInits OBJECT-TYPE 1529 SYNTAX HCPerfIntervalCount 1530 MAX-ACCESS read-only 1531 STATUS current 1532 DESCRIPTION 1533 "Count of the line initialization attempts during this 1534 interval. This count includes both successful and 1535 failed attempts." 1536 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1537 ::= { vdslPerfIntervalEntry 8 } 1539 vdsl1DayIntervalTable OBJECT-TYPE 1540 SYNTAX SEQUENCE OF Vdsl1DayIntervalEntry 1541 MAX-ACCESS not-accessible 1542 STATUS current 1543 DESCRIPTION 1544 "This table provides one row for each VDSL performance 1545 data collection interval. This table contains live data 1546 from equipment. As such, it is NOT persistent." 1547 ::= { vdslMibObjects 6 } 1549 vdsl1DayIntervalEntry OBJECT-TYPE 1550 SYNTAX Vdsl1DayIntervalEntry 1551 MAX-ACCESS not-accessible 1552 STATUS current 1553 DESCRIPTION 1554 "An entry in the vdsl1DayIntervalTable." 1555 INDEX { ifIndex, 1556 vdslPhysSide, 1557 vdsl1DayIntervalNumber } 1558 ::= { vdsl1DayIntervalTable 1 } 1560 Vdsl1DayIntervalEntry ::= 1561 SEQUENCE 1562 { 1563 vdsl1DayIntervalNumber Unsigned32, 1564 vdsl1DayIntervalMoniSecs HCPerfTimeElapsed, 1565 vdsl1DayIntervalLofs Counter64, 1566 vdsl1DayIntervalLoss Counter64, 1567 vdsl1DayIntervalLprs Counter64, 1568 vdsl1DayIntervalESs Counter64, 1569 vdsl1DayIntervalSESs Counter64, 1570 vdsl1DayIntervalUASs Counter64, 1571 vdsl1DayIntervalInits Counter64 1572 } 1574 vdsl1DayIntervalNumber OBJECT-TYPE 1575 SYNTAX Unsigned32 (1..30) 1576 MAX-ACCESS not-accessible 1577 STATUS current 1578 DESCRIPTION 1579 "History Data Interval number. Interval 1 is the the most 1580 recent previous day; interval 30 is 30 days ago. Intervals 1581 2..30 are optional." 1582 ::= { vdsl1DayIntervalEntry 1 } 1584 vdsl1DayIntervalMoniSecs OBJECT-TYPE 1585 SYNTAX HCPerfTimeElapsed 1586 UNITS "seconds" 1587 MAX-ACCESS read-only 1588 STATUS current 1589 DESCRIPTION 1590 "The amount of time in the 1-day interval over which the 1591 performance monitoring information is actually counted. 1592 This value will be the same as the interval duration except 1593 in a situation where performance monitoring data could not 1594 be collected for any reason." 1595 ::= { vdsl1DayIntervalEntry 2 } 1597 vdsl1DayIntervalLofs OBJECT-TYPE 1598 SYNTAX Counter64 1599 UNITS "seconds" 1600 MAX-ACCESS read-only 1601 STATUS current 1602 DESCRIPTION 1603 "Count of Loss of Frame (LOF) Seconds during the 1-day 1604 interval as measured by vdsl1DayIntervalMoniSecs." 1605 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1606 ::= { vdsl1DayIntervalEntry 3 } 1608 vdsl1DayIntervalLoss OBJECT-TYPE 1609 SYNTAX Counter64 1610 UNITS "seconds" 1611 MAX-ACCESS read-only 1612 STATUS current 1613 DESCRIPTION 1614 "Count of Loss of Signal (LOS) Seconds during the 1-day 1615 interval as measured by vdsl1DayIntervalMoniSecs." 1616 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1617 ::= { vdsl1DayIntervalEntry 4 } 1619 vdsl1DayIntervalLprs OBJECT-TYPE 1620 SYNTAX Counter64 1621 UNITS "seconds" 1622 MAX-ACCESS read-only 1623 STATUS current 1624 DESCRIPTION 1625 "Count of Loss of Power (LPR) Seconds during the 1-day 1626 interval as measured by vdsl1DayIntervalMoniSecs." 1627 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1628 ::= { vdsl1DayIntervalEntry 5 } 1630 vdsl1DayIntervalESs OBJECT-TYPE 1631 SYNTAX Counter64 1632 UNITS "seconds" 1633 MAX-ACCESS read-only 1634 STATUS current 1635 DESCRIPTION 1636 "Count of Errored Seconds (ES) during the 1-day 1637 interval as measured by vdsl1DayIntervalMoniSecs." 1638 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1639 ::= { vdsl1DayIntervalEntry 6 } 1641 vdsl1DayIntervalSESs OBJECT-TYPE 1642 SYNTAX Counter64 1643 UNITS "seconds" 1644 MAX-ACCESS read-only 1645 STATUS current 1646 DESCRIPTION 1647 "Count of Severely Errored Seconds (SES) during the 1-day 1648 interval as measured by vdsl1DayIntervalMoniSecs." 1649 ::= { vdsl1DayIntervalEntry 7 } 1651 vdsl1DayIntervalUASs OBJECT-TYPE 1652 SYNTAX Counter64 1653 UNITS "seconds" 1654 MAX-ACCESS read-only 1655 STATUS current 1656 DESCRIPTION 1657 "Count of Unavailable Seconds (UAS) during the 1-day 1658 interval as measured by vdsl1DayIntervalMoniSecs." 1659 ::= { vdsl1DayIntervalEntry 8 } 1661 vdsl1DayIntervalInits OBJECT-TYPE 1662 SYNTAX Counter64 1663 UNITS "seconds" 1664 MAX-ACCESS read-only 1665 STATUS current 1666 DESCRIPTION 1667 "Count of the line initialization attempts during the 1668 1-day interval as measured by vdsl1DayIntervalMoniSecs. 1669 This count includes both successful and failed attempts." 1670 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1671 ::= { vdsl1DayIntervalEntry 9 } 1673 vdslChanPerfDataTable OBJECT-TYPE 1674 SYNTAX SEQUENCE OF VdslChanPerfDataEntry 1675 MAX-ACCESS not-accessible 1676 STATUS current 1677 DESCRIPTION 1678 "This table provides one row for each Vtu channel. 1679 VDSL channel interfaces are those ifEntries where 1680 ifType is equal to interleave(124) or fast(125)." 1681 ::= { vdslMibObjects 7 } 1683 vdslChanPerfDataEntry OBJECT-TYPE 1684 SYNTAX VdslChanPerfDataEntry 1685 MAX-ACCESS not-accessible 1686 STATUS current 1687 DESCRIPTION 1688 "An entry in the vdslChanPerfDataTable." 1689 INDEX { ifIndex, 1690 vdslPhysSide } 1691 ::= { vdslChanPerfDataTable 1 } 1693 VdslChanPerfDataEntry ::= 1694 SEQUENCE 1695 { 1696 vdslChanPerfValidIntervals HCPerfValidIntervals, 1697 vdslChanPerfInvalidIntervals HCPerfInvalidIntervals, 1698 vdslChanCorrectedOctets Counter64, 1699 vdslChanUncorrectBlks Counter64, 1700 vdslChanPerfCurr15MinTimeElapsed HCPerfTimeElapsed, 1701 vdslChanPerfCurr15MinCorrectedOctets HCPerfCurrentCount, 1702 vdslChanPerfCurr15MinUncorrectBlks HCPerfCurrentCount, 1703 vdslChanPerf1DayValidIntervals HCPerfValidIntervals, 1704 vdslChanPerf1DayInvalidIntervals HCPerfInvalidIntervals, 1705 vdslChanPerfCurr1DayTimeElapsed HCPerfTimeElapsed, 1706 vdslChanPerfCurr1DayCorrectedOctets HCPerfCurrentCount, 1707 vdslChanPerfCurr1DayUncorrectBlks HCPerfCurrentCount 1708 } 1710 vdslChanPerfValidIntervals OBJECT-TYPE 1711 SYNTAX HCPerfValidIntervals 1712 MAX-ACCESS read-only 1713 STATUS current 1714 DESCRIPTION 1715 "Valid Intervals per definition found in 1716 HC-PerfHist-TC-MIB." 1717 ::= { vdslChanPerfDataEntry 1 } 1719 vdslChanPerfInvalidIntervals OBJECT-TYPE 1720 SYNTAX HCPerfInvalidIntervals 1721 MAX-ACCESS read-only 1722 STATUS current 1723 DESCRIPTION 1724 "Invalid Intervals per definition found in 1725 HC-PerfHist-TC-MIB." 1726 ::= { vdslChanPerfDataEntry 2 } 1728 vdslChanCorrectedOctets OBJECT-TYPE 1729 SYNTAX Counter64 1730 MAX-ACCESS read-only 1731 STATUS current 1732 DESCRIPTION 1733 "Count of corrected octets since the unit was last reset." 1734 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1735 ::= { vdslChanPerfDataEntry 3 } 1737 vdslChanUncorrectBlks OBJECT-TYPE 1738 SYNTAX Counter64 1739 MAX-ACCESS read-only 1740 STATUS current 1741 DESCRIPTION 1742 "Count of uncorrected blocks since the unit was last reset." 1743 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1744 ::= { vdslChanPerfDataEntry 4 } 1746 vdslChanPerfCurr15MinTimeElapsed OBJECT-TYPE 1747 SYNTAX HCPerfTimeElapsed 1748 UNITS "seconds" 1749 MAX-ACCESS read-only 1750 STATUS current 1751 DESCRIPTION 1752 "Total elapsed seconds in this interval." 1753 ::= { vdslChanPerfDataEntry 5 } 1755 vdslChanPerfCurr15MinCorrectedOctets OBJECT-TYPE 1756 SYNTAX HCPerfCurrentCount 1757 MAX-ACCESS read-only 1758 STATUS current 1759 DESCRIPTION 1760 "Count of corrected octets in this interval." 1761 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1762 ::= { vdslChanPerfDataEntry 6 } 1764 vdslChanPerfCurr15MinUncorrectBlks OBJECT-TYPE 1765 SYNTAX HCPerfCurrentCount 1766 MAX-ACCESS read-only 1767 STATUS current 1768 DESCRIPTION 1769 "Count of uncorrected blocks in this interval." 1771 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1772 ::= { vdslChanPerfDataEntry 7 } 1774 vdslChanPerf1DayValidIntervals OBJECT-TYPE 1775 SYNTAX HCPerfValidIntervals 1776 MAX-ACCESS read-only 1777 STATUS current 1778 DESCRIPTION 1779 "Valid Intervals per definition found in 1780 HC-PerfHist-TC-MIB." 1781 ::= { vdslChanPerfDataEntry 8 } 1783 vdslChanPerf1DayInvalidIntervals OBJECT-TYPE 1784 SYNTAX HCPerfInvalidIntervals 1785 MAX-ACCESS read-only 1786 STATUS current 1787 DESCRIPTION 1788 "Invalid Intervals per definition found in 1789 HC-PerfHist-TC-MIB." 1790 ::= { vdslChanPerfDataEntry 9 } 1792 vdslChanPerfCurr1DayTimeElapsed OBJECT-TYPE 1793 SYNTAX HCPerfTimeElapsed 1794 UNITS "seconds" 1795 MAX-ACCESS read-only 1796 STATUS current 1797 DESCRIPTION 1798 "Number of seconds that have elapsed since the beginning 1799 of the current 1-day interval." 1800 ::= { vdslChanPerfDataEntry 10 } 1802 vdslChanPerfCurr1DayCorrectedOctets OBJECT-TYPE 1803 SYNTAX HCPerfCurrentCount 1804 MAX-ACCESS read-only 1805 STATUS current 1806 DESCRIPTION 1807 "Count of corrected octets since the beginning of the 1808 current 1-day interva." 1809 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1810 ::= { vdslChanPerfDataEntry 11 } 1812 vdslChanPerfCurr1DayUncorrectBlks OBJECT-TYPE 1813 SYNTAX HCPerfCurrentCount 1814 MAX-ACCESS read-only 1815 STATUS current 1816 DESCRIPTION 1817 "Count of uncorrected blocks since the beginning of the 1818 current 1-day interva." 1819 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1820 ::= { vdslChanPerfDataEntry 12 } 1822 vdslChanIntervalTable OBJECT-TYPE 1823 SYNTAX SEQUENCE OF VdslChanIntervalEntry 1824 MAX-ACCESS not-accessible 1825 STATUS current 1826 DESCRIPTION 1827 "This table provides one row for each Vtu channel data 1828 collection interval. VDSL channel interfaces are those 1829 ifEntries where ifType is equal to interleave(124) or 1830 fast(125)." 1831 ::= { vdslMibObjects 8 } 1833 vdslChanIntervalEntry OBJECT-TYPE 1834 SYNTAX VdslChanIntervalEntry 1835 MAX-ACCESS not-accessible 1836 STATUS current 1837 DESCRIPTION 1838 "An entry in the vdslChanIntervalTable." 1839 INDEX { ifIndex, 1840 vdslPhysSide, 1841 vdslChanIntervalNumber } 1842 ::= { vdslChanIntervalTable 1 } 1844 VdslChanIntervalEntry ::= 1845 SEQUENCE 1846 { 1847 vdslChanIntervalNumber Unsigned32, 1848 vdslChanIntervalCorrectedOctets HCPerfIntervalCount, 1849 vdslChanIntervalUncorrectBlks HCPerfIntervalCount 1850 } 1852 vdslChanIntervalNumber OBJECT-TYPE 1853 SYNTAX Unsigned32 (0..96) 1854 MAX-ACCESS not-accessible 1855 STATUS current 1856 DESCRIPTION 1857 "Performance Data Interval number 1 is the the most 1858 recent previous interval; interval 96 is 24 hours ago. 1859 Intervals 2..96 are optional." 1860 ::= { vdslChanIntervalEntry 1 } 1862 vdslChanIntervalCorrectedOctets OBJECT-TYPE 1863 SYNTAX HCPerfIntervalCount 1864 MAX-ACCESS read-only 1865 STATUS current 1866 DESCRIPTION 1867 "Count of corrected octets in this interval." 1868 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1869 ::= { vdslChanIntervalEntry 2 } 1871 vdslChanIntervalUncorrectBlks OBJECT-TYPE 1872 SYNTAX HCPerfIntervalCount 1873 MAX-ACCESS read-only 1874 STATUS current 1875 DESCRIPTION 1876 "Count of uncorrected blocks in this interval." 1877 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1878 ::= { vdslChanIntervalEntry 3 } 1880 vdslChan1DayIntervalTable OBJECT-TYPE 1881 SYNTAX SEQUENCE OF VdslChan1DayIntervalEntry 1882 MAX-ACCESS not-accessible 1883 STATUS current 1884 DESCRIPTION 1885 "This table provides one row for each VDSL performance 1886 data collection interval. This table contains live data 1887 from equipment. As such, it is NOT persistent." 1888 ::= { vdslMibObjects 9 } 1890 vdslChan1DayIntervalEntry OBJECT-TYPE 1891 SYNTAX VdslChan1DayIntervalEntry 1892 MAX-ACCESS not-accessible 1893 STATUS current 1894 DESCRIPTION 1895 "An entry in the vdslChan1DayIntervalTable." 1896 INDEX { ifIndex, 1897 vdslPhysSide, 1898 vdslChan1DayIntervalNumber } 1899 ::= { vdslChan1DayIntervalTable 1 } 1901 VdslChan1DayIntervalEntry ::= 1902 SEQUENCE 1903 { 1904 vdslChan1DayIntervalNumber Unsigned32, 1905 vdslChan1DayIntervalMoniSecs HCPerfTimeElapsed, 1906 vdslChan1DayIntervalCorrectedOctets HCPerfCurrentCount, 1907 vdslChan1DayIntervalUncorrectBlks HCPerfCurrentCount 1908 } 1910 vdslChan1DayIntervalNumber OBJECT-TYPE 1911 SYNTAX Unsigned32 (1..30) 1912 MAX-ACCESS not-accessible 1913 STATUS current 1914 DESCRIPTION 1915 "History Data Interval number. Interval 1 is the the most 1916 recent previous day; interval 30 is 30 days ago. Intervals 1917 2..30 are optional." 1918 ::= { vdslChan1DayIntervalEntry 1 } 1920 vdslChan1DayIntervalMoniSecs OBJECT-TYPE 1921 SYNTAX HCPerfTimeElapsed 1922 UNITS "seconds" 1923 MAX-ACCESS read-only 1924 STATUS current 1925 DESCRIPTION 1926 "The amount of time in the 1-day interval over which the 1927 performance monitoring information is actually counted. 1928 This value will be the same as the interval duration except 1929 in a situation where performance monitoring data could not 1930 be collected for any reason." 1931 ::= { vdslChan1DayIntervalEntry 2 } 1933 vdslChan1DayIntervalCorrectedOctets OBJECT-TYPE 1934 SYNTAX HCPerfCurrentCount 1935 MAX-ACCESS read-only 1936 STATUS current 1937 DESCRIPTION 1938 "Count of corrected octets in this interval." 1939 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1940 ::= { vdslChan1DayIntervalEntry 3 } 1942 vdslChan1DayIntervalUncorrectBlks OBJECT-TYPE 1943 SYNTAX HCPerfCurrentCount 1944 MAX-ACCESS read-only 1945 STATUS current 1946 DESCRIPTION 1947 "Count of uncorrected blocks in this interval." 1948 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1949 ::= { vdslChan1DayIntervalEntry 4 } 1951 -- 1952 -- SCM physical band status 1953 -- 1955 vdslSCMPhysBandTable OBJECT-TYPE 1956 SYNTAX SEQUENCE OF VdslSCMPhysBandEntry 1957 MAX-ACCESS not-accessible 1958 STATUS current 1959 DESCRIPTION 1960 "This table provides one row for each SCM Vtu band." 1961 ::= { vdslMibObjects 10 } 1963 vdslSCMPhysBandEntry OBJECT-TYPE 1964 SYNTAX VdslSCMPhysBandEntry 1965 MAX-ACCESS not-accessible 1966 STATUS current 1967 DESCRIPTION 1968 "An entry in the vdslSCMPhysBandTable." 1969 INDEX { ifIndex, 1970 vdslPhysSide, 1971 vdslSCMPhysTxBandNumber } 1972 ::= { vdslSCMPhysBandTable 1 } 1974 VdslSCMPhysBandEntry ::= 1975 SEQUENCE 1976 { 1977 vdslSCMPhysTxBandNumber INTEGER, 1978 vdslSCMPhysBandSnrMgn Integer32, 1979 vdslSCMPhysBandAtn Unsigned32 1980 } 1982 vdslSCMPhysTxBandNumber OBJECT-TYPE 1983 SYNTAX INTEGER 1984 { 1985 band1(1), 1986 band2(2), 1987 upstreamU0(3) 1988 } 1989 MAX-ACCESS not-accessible 1990 STATUS current 1991 DESCRIPTION 1992 "The SCM transmit band number for this entry." 1993 ::= { vdslSCMPhysBandEntry 1 } 1995 vdslSCMPhysBandSnrMgn OBJECT-TYPE 1996 SYNTAX Integer32 (-127..127) 1997 UNITS "0.25 dBm" 1998 MAX-ACCESS read-only 1999 STATUS current 2000 DESCRIPTION 2001 "Noise margin as seen by this Vtu and band with respect 2002 to its received signal in 0.25 dB." 2003 ::= { vdslSCMPhysBandEntry 2 } 2005 vdslSCMPhysBandAtn OBJECT-TYPE 2006 SYNTAX Unsigned32 (0..255) 2007 UNITS "0.25 dBm" 2008 MAX-ACCESS read-only 2009 STATUS current 2010 DESCRIPTION 2011 "Measured difference in the total power transmitted by 2012 the peer Vtu on this band and the total power received 2013 by this Vtu on this band in 0.25 dB." 2014 ::= { vdslSCMPhysBandEntry 3 } 2016 -- 2017 -- profile tables 2018 -- 2020 vdslLineConfProfileTable OBJECT-TYPE 2021 SYNTAX SEQUENCE OF VdslLineConfProfileEntry 2022 MAX-ACCESS not-accessible 2023 STATUS current 2024 DESCRIPTION 2025 "This table contains information on the VDSL line 2026 configuration. One entry in this table reflects a 2027 profile defined by a manager which can be used to 2028 configure the VDSL line." 2029 ::= { vdslMibObjects 11 } 2031 vdslLineConfProfileEntry OBJECT-TYPE 2032 SYNTAX VdslLineConfProfileEntry 2033 MAX-ACCESS not-accessible 2034 STATUS current 2035 DESCRIPTION 2036 "Each entry consists of a list of parameters that 2037 represents the configuration of a VDSL line. A 2038 default profile with an index of 1 will always exist 2039 and its parameters will be set to vendor specific 2040 values, unless otherwise specified in this document." 2041 INDEX { vdslLineConfProfileIndex } 2042 ::= { vdslLineConfProfileTable 1 } 2044 VdslLineConfProfileEntry ::= 2045 SEQUENCE 2046 { 2047 vdslLineConfProfileIndex Unsigned32, 2048 vdslLineConfProfileName SnmpAdminString, 2049 vdslLineConfDownstreamMaxPwr Unsigned32, 2050 vdslLineConfUpstreamMaxPwr Unsigned32, 2051 vdslLineConfDownstreamMaxSnrMgn Unsigned32, 2052 vdslLineConfDownstreamMinSnrMgn Unsigned32, 2053 vdslLineConfDownstreamTargetSnrMgn Unsigned32, 2054 vdslLineConfUpstreamMaxSnrMgn Unsigned32, 2055 vdslLineConfUpstreamMinSnrMgn Unsigned32, 2056 vdslLineConfUpstreamTargetSnrMgn Unsigned32, 2057 vdslLineConfDownstreamFastMaxDataRate Unsigned32, 2058 vdslLineConfDownstreamFastMinDataRate Unsigned32, 2059 vdslLineConfDownstreamSlowMaxDataRate Unsigned32, 2060 vdslLineConfDownstreamSlowMinDataRate Unsigned32, 2061 vdslLineConfUpstreamFastMaxDataRate Unsigned32, 2062 vdslLineConfUpstreamFastMinDataRate Unsigned32, 2063 vdslLineConfUpstreamSlowMaxDataRate Unsigned32, 2064 vdslLineConfUpstreamSlowMinDataRate Unsigned32, 2065 vdslLineConfRateAdaptationRatio Unsigned32, 2066 vdslLineConfUpstreamDataRate Unsigned32, 2067 vdslLineConfDownstreamDataRate Unsigned32, 2068 vdslLineConfDownstreamMaxInterDelay Unsigned32, 2069 vdslLineConfUpstreamMaxInterDelay Unsigned32, 2070 vdslLineConfUpstreamPboControl INTEGER, 2071 vdslLineConfDownstreamPboControl INTEGER, 2072 vdslLineConfDeploymentScenario INTEGER, 2073 vdslLineConfAdslOccupy TruthValue, 2074 vdslLineConfApplicableStandard INTEGER, 2075 vdslLineConfBandPlan INTEGER, 2076 vdslLineConfBandPlanFx Unsigned32, 2077 vdslLineConfBandU0Usage INTEGER, 2078 vdslLineConfUpstreamPsdTemplate INTEGER, 2079 vdslLineConfDownstreamPsdTemplate INTEGER, 2080 vdslLineConfProfileRowStatus RowStatus 2081 } 2083 vdslLineConfProfileIndex OBJECT-TYPE 2084 SYNTAX Unsigned32 2085 MAX-ACCESS read-only 2086 STATUS current 2087 DESCRIPTION 2088 "This object identifies a row in this table. A 2089 default profile with an index of 1 MUST always 2090 exist and its parameters will be set to vendor 2091 specific values, unless otherwise specified in 2092 this document." 2093 ::= { vdslLineConfProfileEntry 1 } 2095 vdslLineConfProfileName OBJECT-TYPE 2096 SYNTAX SnmpAdminString (SIZE (1..32)) 2097 MAX-ACCESS read-create 2098 STATUS current 2099 DESCRIPTION 2100 "The name for this profile as specified by a user." 2101 ::= { vdslLineConfProfileEntry 2 } 2103 vdslLineConfDownstreamMaxPwr OBJECT-TYPE 2104 SYNTAX Unsigned32 (0..58) 2105 UNITS "0.25dBm" 2106 MAX-ACCESS read-create 2107 STATUS current 2108 DESCRIPTION 2109 "Specifies the maximum aggregate downstream power 2110 level in the range 0..14.5dBm." 2111 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 2112 ::= { vdslLineConfProfileEntry 3 } 2114 vdslLineConfUpstreamMaxPwr OBJECT-TYPE 2115 SYNTAX Unsigned32 (0..58) 2116 UNITS "0.25dBm" 2117 MAX-ACCESS read-create 2118 STATUS current 2119 DESCRIPTION 2120 "Specifies the maximum aggregate upstream power 2121 level in the range 0..14.5dBm." 2122 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 2123 ::= { vdslLineConfProfileEntry 4 } 2125 vdslLineConfDownstreamMaxSnrMgn OBJECT-TYPE 2126 SYNTAX Unsigned32 (0..127) 2127 UNITS "0.25dBm" 2128 MAX-ACCESS read-create 2129 STATUS current 2130 DESCRIPTION 2131 "Specifies the maximum downstream Signal/Noise Margin 2132 in units of 0.25 dB, for a range of 0..31.75 dB." 2133 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 2134 ::= { vdslLineConfProfileEntry 5 } 2136 vdslLineConfDownstreamMinSnrMgn OBJECT-TYPE 2137 SYNTAX Unsigned32 (0..127) 2138 UNITS "0.25dBm" 2139 MAX-ACCESS read-create 2140 STATUS current 2141 DESCRIPTION 2142 "Specifies the minimum downstream Signal/Noise Margin 2143 in units of 0.25 dB, for a range of 0..31.75 dB." 2144 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 2145 ::= { vdslLineConfProfileEntry 6 } 2147 vdslLineConfDownstreamTargetSnrMgn OBJECT-TYPE 2148 SYNTAX Unsigned32 (0..127) 2149 UNITS "0.25dBm" 2150 MAX-ACCESS read-create 2151 STATUS current 2152 DESCRIPTION 2153 "Specifies the target downstream Signal/Noise Margin 2154 in units of 0.25 dB, for a range of 0..31.75 dB. 2155 This is the Noise Margin the modems must achieve with a 2156 BER of 10-7 or better to successfully complete 2157 initialization." 2158 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 2159 ::= { vdslLineConfProfileEntry 7 } 2161 vdslLineConfUpstreamMaxSnrMgn OBJECT-TYPE 2162 SYNTAX Unsigned32 (0..127) 2163 UNITS "0.25dBm" 2164 MAX-ACCESS read-create 2165 STATUS current 2166 DESCRIPTION 2167 "Specifies the maximum upstream Signal/Noise Margin 2168 in units of 0.25 dB, for a range of 0..31.75 dB." 2169 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 2170 ::= { vdslLineConfProfileEntry 8 } 2172 vdslLineConfUpstreamMinSnrMgn OBJECT-TYPE 2173 SYNTAX Unsigned32 (0..127) 2174 UNITS "0.25dBm" 2175 MAX-ACCESS read-create 2176 STATUS current 2177 DESCRIPTION 2178 "Specifies the minimum upstream Signal/Noise Margin 2179 in units of 0.25 dB, for a range of 0..31.75 dB." 2180 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 2181 ::= { vdslLineConfProfileEntry 9 } 2183 vdslLineConfUpstreamTargetSnrMgn OBJECT-TYPE 2184 SYNTAX Unsigned32 (0..127) 2185 UNITS "0.25dBm" 2186 MAX-ACCESS read-create 2187 STATUS current 2188 DESCRIPTION 2189 "Specifies the target upstream Signal/Noise Margin in 2190 units of 0.25 dB, for a range of 0..31.75 dB. This 2191 is the Noise Margin the modems must achieve with a BER of 2192 10-7 or better to successfully complete initialization." 2193 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 2194 ::= { vdslLineConfProfileEntry 10 } 2196 vdslLineConfDownstreamFastMaxDataRate OBJECT-TYPE 2197 SYNTAX Unsigned32 2198 UNITS "kbps" 2199 MAX-ACCESS read-create 2200 STATUS current 2201 DESCRIPTION 2202 "Specifies the maximum downstream fast channel 2203 data rate in steps of 1024 bits/second." 2204 ::= { vdslLineConfProfileEntry 11 } 2206 vdslLineConfDownstreamFastMinDataRate OBJECT-TYPE 2207 SYNTAX Unsigned32 2208 UNITS "kbps" 2209 MAX-ACCESS read-create 2210 STATUS current 2211 DESCRIPTION 2212 "Specifies the minimum downstream fast channel 2213 data rate in steps of 1024 bits/second." 2214 ::= { vdslLineConfProfileEntry 12 } 2216 vdslLineConfDownstreamSlowMaxDataRate OBJECT-TYPE 2217 SYNTAX Unsigned32 2218 UNITS "kbps" 2219 MAX-ACCESS read-create 2220 STATUS current 2221 DESCRIPTION 2222 "Specifies the maximum downstream slow channel 2223 data rate in steps of 1024 bits/second." 2224 ::= { vdslLineConfProfileEntry 13 } 2226 vdslLineConfDownstreamSlowMinDataRate OBJECT-TYPE 2227 SYNTAX Unsigned32 2228 UNITS "kbps" 2229 MAX-ACCESS read-create 2230 STATUS current 2231 DESCRIPTION 2232 "Specifies the minimum downstream slow channel 2233 data rate in steps of 1024 bits/second." 2234 ::= { vdslLineConfProfileEntry 14 } 2236 vdslLineConfUpstreamFastMaxDataRate OBJECT-TYPE 2237 SYNTAX Unsigned32 2238 UNITS "kbps" 2239 MAX-ACCESS read-create 2240 STATUS current 2241 DESCRIPTION 2242 "Specifies the maximum upstream fast channel 2243 data rate in steps of 1024 bits/second." 2244 ::= { vdslLineConfProfileEntry 15 } 2246 vdslLineConfUpstreamFastMinDataRate OBJECT-TYPE 2247 SYNTAX Unsigned32 2248 UNITS "kbps" 2249 MAX-ACCESS read-create 2250 STATUS current 2251 DESCRIPTION 2252 "Specifies the minimum upstream fast channel 2253 data rate in steps of 1024 bits/second." 2254 ::= { vdslLineConfProfileEntry 16 } 2256 vdslLineConfUpstreamSlowMaxDataRate OBJECT-TYPE 2257 SYNTAX Unsigned32 2258 UNITS "kbps" 2259 MAX-ACCESS read-create 2260 STATUS current 2261 DESCRIPTION 2262 "Specifies the maximum upstream slow channel 2263 data rate in steps of 1024 bits/second." 2264 ::= { vdslLineConfProfileEntry 17 } 2266 vdslLineConfUpstreamSlowMinDataRate OBJECT-TYPE 2267 SYNTAX Unsigned32 2268 UNITS "kbps" 2269 MAX-ACCESS read-create 2270 STATUS current 2271 DESCRIPTION 2272 "Specifies the minimum upstream slow channel 2273 data rate in steps of 1024 bits/second." 2274 ::= { vdslLineConfProfileEntry 18 } 2276 vdslLineConfRateAdaptationRatio OBJECT-TYPE 2277 SYNTAX Unsigned32 (0..100) 2278 UNITS "percent" 2279 MAX-ACCESS read-create 2280 STATUS current 2281 DESCRIPTION 2282 "For dynamic rate adaptation at startup, the allocation 2283 of data rate in excess of the minimum data rate for each 2284 channel is controlled by the object. This object specifies 2285 the ratio of the allocation of the excess data rate between 2286 the fast and the slow channels. This allocation represents 2287 Fast Channel Allocation / Slow Channel Allocation." 2288 ::= { vdslLineConfProfileEntry 19 } 2290 vdslLineConfUpstreamDataRate OBJECT-TYPE 2291 SYNTAX Unsigned32 2292 UNITS "kbps" 2293 MAX-ACCESS read-create 2294 STATUS current 2295 DESCRIPTION 2296 "Aggregate upstream transmit speed for this line 2297 in steps of 1024 bits/second." 2298 ::= { vdslLineConfProfileEntry 20 } 2300 vdslLineConfDownstreamDataRate OBJECT-TYPE 2301 SYNTAX Unsigned32 2302 UNITS "kbps" 2303 MAX-ACCESS read-create 2304 STATUS current 2305 DESCRIPTION 2306 "Aggregate downstream transmit speed for this line 2307 in steps of 1024 bits/second." 2308 ::= { vdslLineConfProfileEntry 21 } 2310 vdslLineConfDownstreamMaxInterDelay OBJECT-TYPE 2311 SYNTAX Unsigned32 (0..255) 2312 UNITS "ms" 2313 MAX-ACCESS read-create 2314 STATUS current 2315 DESCRIPTION 2316 "Specifies the maximum interleave delay for the 2317 downstream slow channel." 2318 ::= { vdslLineConfProfileEntry 22 } 2320 vdslLineConfUpstreamMaxInterDelay OBJECT-TYPE 2321 SYNTAX Unsigned32 (0..255) 2322 UNITS "ms" 2323 MAX-ACCESS read-create 2324 STATUS current 2325 DESCRIPTION 2326 "Specifies the maximum interleave delay for the 2327 upstream slow channel." 2328 ::= { vdslLineConfProfileEntry 23 } 2330 vdslLineConfUpstreamPboControl OBJECT-TYPE 2331 SYNTAX INTEGER 2332 { 2333 disabled(1), 2334 enabled(2) 2335 } 2336 MAX-ACCESS read-create 2337 STATUS current 2338 DESCRIPTION 2339 "Upstream power backoff (PBO) control for this 2340 line. For modems which do not support upstream 2341 PBO control, this object MUST be fixed at disabled(1)." 2342 ::= { vdslLineConfProfileEntry 24 } 2344 vdslLineConfDownstreamPboControl OBJECT-TYPE 2345 SYNTAX INTEGER 2346 { 2347 disabled(1), 2348 enabled(2) 2349 } 2350 MAX-ACCESS read-create 2351 STATUS current 2352 DESCRIPTION 2353 "Downstream power backoff (PBO) control for this 2354 line. For modems which do not support downstream 2355 PBO control, this object MUST be fixed at disabled(1)." 2356 ::= { vdslLineConfProfileEntry 25 } 2358 vdslLineConfDeploymentScenario OBJECT-TYPE 2359 SYNTAX INTEGER 2360 { 2361 fttCab(1), 2362 fttEx(2), 2363 other(3) 2364 } 2365 MAX-ACCESS read-create 2366 STATUS current 2367 DESCRIPTION 2368 "The VDSL line deployment scenario. When using 2369 fttCab(1), the VTU-C is located in a street cabinet. 2370 When using fttEx(2), the VTU-C is located at the 2371 central office." 2372 ::= { vdslLineConfProfileEntry 26 } 2374 vdslLineConfAdslOccupy OBJECT-TYPE 2375 SYNTAX TruthValue 2376 MAX-ACCESS read-create 2377 STATUS current 2378 DESCRIPTION 2379 "Indicates if the VDSL line can occupy the ADSL 2380 frequency range." 2381 ::= { vdslLineConfProfileEntry 27 } 2383 vdslLineConfApplicableStandard OBJECT-TYPE 2384 SYNTAX INTEGER 2385 { 2386 ansi(1), 2387 etsi(2), 2388 itu(3), 2389 other(4) 2390 } 2391 MAX-ACCESS read-create 2392 STATUS current 2393 DESCRIPTION 2394 "The VDSL standard to be used for the line." 2395 ::= { vdslLineConfProfileEntry 28 } 2397 vdslLineConfBandPlan OBJECT-TYPE 2398 SYNTAX INTEGER 2399 { 2400 bandPlan997(1), 2401 bandPlan998(2), 2402 bandPlanFx(3), 2403 other(4) 2404 } 2405 MAX-ACCESS read-create 2406 STATUS current 2407 DESCRIPTION 2408 "The VDSL band plan to be used for the line. 2410 bandPlan997(1) is to be used for 2411 ITU-T G.993.1 Bandplan-B 2412 ETSI Bandplan 2413 ANSI Plan 997 2415 bandPlan998(2) is to be used for 2416 ITU-T G.993.1 Bandplan-A 2417 ANSI Plan 998 2419 bandPlanFx(3) is to be used for 2420 ITU-T G.993.1 Bandplan-C. 2422 other(4) is to be used for 2423 non-standard bandplans. 2425 If this object is set to bandPlanFx(3), then 2426 the object vdslLineConfBandPlanFx MUST also be 2427 set." 2428 ::= { vdslLineConfProfileEntry 29 } 2430 vdslLineConfBandPlanFx OBJECT-TYPE 2431 SYNTAX Unsigned32 (3750..12000) 2432 UNITS "kHz" 2433 MAX-ACCESS read-create 2434 STATUS current 2435 DESCRIPTION 2436 "The frequency limit between bands D2 and U2 when 2437 vdslLineConfBandPlan is set to bandPlanFx(3)." 2438 ::= { vdslLineConfProfileEntry 30 } 2440 vdslLineConfBandU0Usage OBJECT-TYPE 2441 SYNTAX INTEGER 2442 { 2443 unused(1), 2444 upstream(2), 2445 downstream(3) 2446 } 2447 MAX-ACCESS read-create 2448 STATUS current 2449 DESCRIPTION 2450 "Defines the VDSL link use of the frequency range 2451 [25kHz - 138kHz] (U0)." 2452 ::= { vdslLineConfProfileEntry 31 } 2454 vdslLineConfUpstreamPsdTemplate OBJECT-TYPE 2455 SYNTAX INTEGER 2456 { 2457 templateMask1(1), 2458 templateMask2(2) 2459 } 2460 MAX-ACCESS read-create 2461 STATUS current 2462 DESCRIPTION 2463 "The upstream PSD template to be used for the line." 2464 ::= { vdslLineConfProfileEntry 32 } 2466 vdslLineConfDownstreamPsdTemplate OBJECT-TYPE 2467 SYNTAX INTEGER 2468 { 2469 templateMask1(1), 2470 templateMask2(2) 2471 } 2472 MAX-ACCESS read-create 2473 STATUS current 2474 DESCRIPTION 2475 "The downstream PSD template to be used for the line." 2476 ::= { vdslLineConfProfileEntry 33 } 2478 vdslLineConfProfileRowStatus OBJECT-TYPE 2479 SYNTAX RowStatus 2480 MAX-ACCESS read-create 2481 STATUS current 2482 DESCRIPTION 2483 "This object is used to create a new row or modify or 2484 delete an existing row in this table. 2486 A profile activated by setting this object to `active'. 2487 When `active' is set, the system will validate the profile. 2489 Before a profile can be deleted or taken out of 2490 service, (by setting this object to `destroy' or 2491 `outOfService') it must be first unreferenced 2492 from all associated lines." 2493 ::= { vdslLineConfProfileEntry 34 } 2495 -- 2496 -- Multiple carrier modulation (MCM) configuration profile tables 2497 -- 2499 vdslLineMCMConfProfileTable OBJECT-TYPE 2500 SYNTAX SEQUENCE OF VdslLineMCMConfProfileEntry 2501 MAX-ACCESS not-accessible 2502 STATUS current 2503 DESCRIPTION 2504 "This table contains additional information on 2505 multiple carrier VDSL lines. One entry in this table 2506 reflects a profile defined by a manager which can be used 2507 to configure the VDSL line. 2509 The entries in this table MUST NOT be used for single 2510 carrier (SCM) VDSL lines." 2511 ::= { vdslMibObjects 12 } 2513 vdslLineMCMConfProfileEntry OBJECT-TYPE 2514 SYNTAX VdslLineMCMConfProfileEntry 2515 MAX-ACCESS not-accessible 2516 STATUS current 2517 DESCRIPTION 2518 "Each entry consists of a list of parameters that 2519 represents the configuration of a multiple carrier 2520 modulation VDSL modem. A default profile with an 2521 index of 1 will always exist and its parameters will 2522 be set to vendor specific values, unless otherwise 2523 specified in this document." 2524 INDEX { vdslLineConfProfileIndex } 2525 ::= { vdslLineMCMConfProfileTable 1 } 2527 VdslLineMCMConfProfileEntry ::= 2528 SEQUENCE 2529 { 2530 vdslMCMConfProfileTxWindowLength Unsigned32, 2531 vdslMCMConfProfileRowStatus RowStatus 2532 } 2534 vdslMCMConfProfileTxWindowLength OBJECT-TYPE 2535 SYNTAX Unsigned32 (1..255) 2536 UNITS "samples" 2537 MAX-ACCESS read-create 2538 STATUS current 2539 DESCRIPTION 2540 "Specifies the length of the transmit window, counted 2541 in samples at the sampling rate corresponding to the 2542 negotiated value of N." 2543 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 2544 ::= { vdslLineMCMConfProfileEntry 1 } 2546 vdslMCMConfProfileRowStatus OBJECT-TYPE 2547 SYNTAX RowStatus 2548 MAX-ACCESS read-create 2549 STATUS current 2550 DESCRIPTION 2551 "This object is used to create a new row or modify or 2552 delete an existing row in this table. 2554 A profile activated by setting this object to `active'. 2555 When `active' is set, the system will validate the profile. 2557 Before a profile can be deleted or taken out of 2558 service, (by setting this object to `destroy' or 2559 `outOfService') it must be first unreferenced 2560 from all associated lines." 2561 ::= { vdslLineMCMConfProfileEntry 2 } 2563 vdslLineMCMConfProfileTxBandTable OBJECT-TYPE 2564 SYNTAX SEQUENCE OF VdslLineMCMConfProfileTxBandEntry 2565 MAX-ACCESS not-accessible 2566 STATUS current 2567 DESCRIPTION 2568 "This table contains transmit band descriptor configuration 2569 information for a VDSL line. Each entry in this table 2570 reflects the configuration for one of possibly many bands 2571 with a multiple carrier modulation (MCM) VDSL line. 2572 These entries are defined by a manager and can be used to 2573 configure the VDSL line. 2575 The entries in this table MUST NOT be used for single 2576 carrier (SCM) VDSL lines." 2577 ::= { vdslMibObjects 13 } 2579 vdslLineMCMConfProfileTxBandEntry OBJECT-TYPE 2580 SYNTAX VdslLineMCMConfProfileTxBandEntry 2581 MAX-ACCESS not-accessible 2582 STATUS current 2583 DESCRIPTION 2584 "Each entry consists of a transmit band descriptor, which 2585 is defined by a start and a stop tone index. 2587 A default profile with an index of 1 will always exist and 2588 its parameters will be set to vendor specific values, 2589 unless otherwise specified in this document." 2590 INDEX { vdslLineConfProfileIndex, 2591 vdslMCMConfProfileTxBandNumber } 2592 ::= { vdslLineMCMConfProfileTxBandTable 1 } 2594 VdslLineMCMConfProfileTxBandEntry ::= 2595 SEQUENCE 2596 { 2597 vdslMCMConfProfileTxBandNumber Unsigned32, 2598 vdslMCMConfProfileTxBandStart Unsigned32, 2599 vdslMCMConfProfileTxBandStop Unsigned32, 2600 vdslMCMConfProfileTxBandRowStatus RowStatus 2601 } 2603 vdslMCMConfProfileTxBandNumber OBJECT-TYPE 2604 SYNTAX Unsigned32 2605 MAX-ACCESS not-accessible 2606 STATUS current 2607 DESCRIPTION 2608 "The index for this band descriptor entry." 2609 ::= { vdslLineMCMConfProfileTxBandEntry 1 } 2611 vdslMCMConfProfileTxBandStart OBJECT-TYPE 2612 SYNTAX Unsigned32 2613 MAX-ACCESS read-create 2614 STATUS current 2615 DESCRIPTION 2616 "Start tone index for this band." 2617 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 2618 ::= { vdslLineMCMConfProfileTxBandEntry 2 } 2620 vdslMCMConfProfileTxBandStop OBJECT-TYPE 2621 SYNTAX Unsigned32 2622 MAX-ACCESS read-create 2623 STATUS current 2624 DESCRIPTION 2625 "Stop tone index for this band." 2626 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 2627 ::= { vdslLineMCMConfProfileTxBandEntry 3 } 2629 vdslMCMConfProfileTxBandRowStatus OBJECT-TYPE 2630 SYNTAX RowStatus 2631 MAX-ACCESS read-create 2632 STATUS current 2633 DESCRIPTION 2634 "This object is used to create a new row or modify or 2635 delete an existing row in this table. 2637 A profile activated by setting this object to `active'. 2639 When `active' is set, the system will validate the profile. 2641 Before a profile can be deleted or taken out of 2642 service, (by setting this object to `destroy' or 2643 `outOfService') it must be first unreferenced 2644 from all associated lines." 2645 ::= { vdslLineMCMConfProfileTxBandEntry 4 } 2647 vdslLineMCMConfProfileRxBandTable OBJECT-TYPE 2648 SYNTAX SEQUENCE OF VdslLineMCMConfProfileRxBandEntry 2649 MAX-ACCESS not-accessible 2650 STATUS current 2651 DESCRIPTION 2652 "This table contains receive band descriptor configuration 2653 information for a VDSL line. Each entry in this table 2654 reflects the configuration for one of possibly many bands 2655 with a multiple carrier modulation (MCM) VDSL line. 2656 These entries are defined by a manager and can be used to 2657 configure the VDSL line. 2659 The entries in this table MUST NOT be used for single 2660 carrier (SCM) VDSL lines." 2661 ::= { vdslMibObjects 14 } 2663 vdslLineMCMConfProfileRxBandEntry OBJECT-TYPE 2664 SYNTAX VdslLineMCMConfProfileRxBandEntry 2665 MAX-ACCESS not-accessible 2666 STATUS current 2667 DESCRIPTION 2668 "Each entry consists of a transmit band descriptor, which 2669 is defined by a start and a stop tone index. 2671 A default profile with an index of 1 will always exist and 2672 its parameters will be set to vendor specific values, 2673 unless otherwise specified in this document." 2674 INDEX { vdslLineConfProfileIndex, 2675 vdslMCMConfProfileRxBandNumber } 2676 ::= { vdslLineMCMConfProfileRxBandTable 1 } 2678 VdslLineMCMConfProfileRxBandEntry ::= 2679 SEQUENCE 2680 { 2681 vdslMCMConfProfileRxBandNumber Unsigned32, 2682 vdslMCMConfProfileRxBandStart Unsigned32, 2683 vdslMCMConfProfileRxBandStop Unsigned32, 2684 vdslMCMConfProfileRxBandRowStatus RowStatus 2685 } 2687 vdslMCMConfProfileRxBandNumber OBJECT-TYPE 2688 SYNTAX Unsigned32 2689 MAX-ACCESS not-accessible 2690 STATUS current 2691 DESCRIPTION 2692 "The index for this band descriptor entry." 2693 ::= { vdslLineMCMConfProfileRxBandEntry 1 } 2695 vdslMCMConfProfileRxBandStart OBJECT-TYPE 2696 SYNTAX Unsigned32 2697 MAX-ACCESS read-create 2698 STATUS current 2699 DESCRIPTION 2700 "Start tone index for this band." 2701 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 2702 ::= { vdslLineMCMConfProfileRxBandEntry 2 } 2704 vdslMCMConfProfileRxBandStop OBJECT-TYPE 2705 SYNTAX Unsigned32 2706 MAX-ACCESS read-create 2707 STATUS current 2708 DESCRIPTION 2709 "Stop tone index for this band." 2710 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 2711 ::= { vdslLineMCMConfProfileRxBandEntry 3 } 2713 vdslMCMConfProfileRxBandRowStatus OBJECT-TYPE 2714 SYNTAX RowStatus 2715 MAX-ACCESS read-create 2716 STATUS current 2717 DESCRIPTION 2718 "This object is used to create a new row or modify or 2719 delete an existing row in this table. 2721 A profile activated by setting this object to `active'. 2722 When `active' is set, the system will validate the profile. 2724 Before a profile can be deleted or taken out of 2725 service, (by setting this object to `destroy' or 2726 `outOfService') it must be first unreferenced 2727 from all associated lines." 2728 ::= { vdslLineMCMConfProfileRxBandEntry 4 } 2730 vdslLineMCMConfProfileTxPSDTable OBJECT-TYPE 2731 SYNTAX SEQUENCE OF VdslLineMCMConfProfileTxPSDEntry 2732 MAX-ACCESS not-accessible 2733 STATUS current 2734 DESCRIPTION 2735 "This table contains transmit PSD mask descriptor 2736 configuration information for a VDSL line. Each entry in 2737 this table reflects the configuration for one tone within 2738 a multiple carrier modulation (MCM) VDSL line. These 2739 entries are defined by a manager and can be used to 2740 configure the VDSL line. 2742 The entries in this table MUST NOT be used for single 2743 carrier (SCM) VDSL lines." 2744 ::= { vdslMibObjects 15 } 2746 vdslLineMCMConfProfileTxPSDEntry OBJECT-TYPE 2747 SYNTAX VdslLineMCMConfProfileTxPSDEntry 2748 MAX-ACCESS not-accessible 2749 STATUS current 2750 DESCRIPTION 2751 "Each entry consists of a transmit PSD mask descriptor, 2752 which defines the power spectral density (PSD) for a tone. 2753 A default profile with an index of 1 will always exist and 2754 its parameters will be set to vendor specific values, 2755 unless otherwise specified in this document." 2756 INDEX { vdslLineConfProfileIndex, 2757 vdslMCMConfProfileTxPSDNumber } 2758 ::= { vdslLineMCMConfProfileTxPSDTable 1 } 2760 VdslLineMCMConfProfileTxPSDEntry ::= 2761 SEQUENCE 2762 { 2763 vdslMCMConfProfileTxPSDNumber Unsigned32, 2764 vdslMCMConfProfileTxPSDTone Unsigned32, 2765 vdslMCMConfProfileTxPSDPSD Unsigned32, 2766 vdslMCMConfProfileTxPSDRowStatus RowStatus 2767 } 2769 vdslMCMConfProfileTxPSDNumber OBJECT-TYPE 2770 SYNTAX Unsigned32 2771 MAX-ACCESS not-accessible 2772 STATUS current 2773 DESCRIPTION 2774 "The index for this mask descriptor entry." 2775 ::= { vdslLineMCMConfProfileTxPSDEntry 1 } 2777 vdslMCMConfProfileTxPSDTone OBJECT-TYPE 2778 SYNTAX Unsigned32 2779 MAX-ACCESS read-create 2780 STATUS current 2781 DESCRIPTION 2782 "The tone index for which the PSD is being specified." 2783 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 2784 ::= { vdslLineMCMConfProfileTxPSDEntry 2 } 2786 vdslMCMConfProfileTxPSDPSD OBJECT-TYPE 2787 SYNTAX Unsigned32 2788 UNITS "0.5dBm" 2789 MAX-ACCESS read-create 2790 STATUS current 2791 DESCRIPTION 2792 "Power Spectral Density level in steps of 0.5dB with 2793 an offset of -140dbm/Hz." 2794 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 2795 ::= { vdslLineMCMConfProfileTxPSDEntry 3 } 2797 vdslMCMConfProfileTxPSDRowStatus OBJECT-TYPE 2798 SYNTAX RowStatus 2799 MAX-ACCESS read-create 2800 STATUS current 2801 DESCRIPTION 2802 "This object is used to create a new row or modify or 2803 delete an existing row in this table. 2805 A profile activated by setting this object to `active'. 2806 When `active' is set, the system will validate the profile. 2808 Before a profile can be deleted or taken out of 2809 service, (by setting this object to `destroy' or 2810 `outOfService') it must be first unreferenced 2811 from all associated lines." 2812 ::= { vdslLineMCMConfProfileTxPSDEntry 4 } 2814 vdslLineMCMConfProfileMaxTxPSDTable OBJECT-TYPE 2815 SYNTAX SEQUENCE OF VdslLineMCMConfProfileMaxTxPSDEntry 2816 MAX-ACCESS not-accessible 2817 STATUS current 2818 DESCRIPTION 2819 "This table contains transmit maximum PSD mask descriptor 2820 configuration information for a VDSL line. Each entry in 2821 this table reflects the configuration for one tone within 2822 a multiple carrier modulation (MCM) VDSL modem. These 2823 entries are defined by a manager and can be used to 2824 configure the VDSL line. 2826 The entries in this table MUST NOT be used for single 2827 carrier (SCM) VDSL lines." 2828 ::= { vdslMibObjects 16 } 2830 vdslLineMCMConfProfileMaxTxPSDEntry OBJECT-TYPE 2831 SYNTAX VdslLineMCMConfProfileMaxTxPSDEntry 2832 MAX-ACCESS not-accessible 2833 STATUS current 2834 DESCRIPTION 2835 "Each entry consists of a transmit PSD mask descriptor, 2836 which defines the maximum power spectral density (PSD) 2837 for a tone. 2839 A default profile with an index of 1 MUST always exist and 2840 its parameters will be set to vendor specific values, 2841 unless otherwise specified in this document." 2842 INDEX { vdslLineConfProfileIndex, 2843 vdslMCMConfProfileMaxTxPSDNumber } 2844 ::= { vdslLineMCMConfProfileMaxTxPSDTable 1 } 2846 VdslLineMCMConfProfileMaxTxPSDEntry ::= 2847 SEQUENCE 2848 { 2849 vdslMCMConfProfileMaxTxPSDNumber Unsigned32, 2850 vdslMCMConfProfileMaxTxPSDTone Unsigned32, 2851 vdslMCMConfProfileMaxTxPSDPSD Unsigned32, 2852 vdslMCMConfProfileMaxTxPSDRowStatus RowStatus 2853 } 2855 vdslMCMConfProfileMaxTxPSDNumber OBJECT-TYPE 2856 SYNTAX Unsigned32 2857 MAX-ACCESS not-accessible 2858 STATUS current 2859 DESCRIPTION 2860 "The index for this band descriptor entry." 2861 ::= { vdslLineMCMConfProfileMaxTxPSDEntry 1 } 2863 vdslMCMConfProfileMaxTxPSDTone OBJECT-TYPE 2864 SYNTAX Unsigned32 2865 MAX-ACCESS read-create 2866 STATUS current 2867 DESCRIPTION 2868 "The tone index for which the PSD is being specified." 2869 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 2870 ::= { vdslLineMCMConfProfileMaxTxPSDEntry 2 } 2872 vdslMCMConfProfileMaxTxPSDPSD OBJECT-TYPE 2873 SYNTAX Unsigned32 2874 UNITS "0.5dBm" 2875 MAX-ACCESS read-create 2876 STATUS current 2877 DESCRIPTION 2878 "Power Spectral Density level in steps of 0.5dB with 2879 an offset of -140dbm/Hz." 2880 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 2881 ::= { vdslLineMCMConfProfileMaxTxPSDEntry 3 } 2883 vdslMCMConfProfileMaxTxPSDRowStatus OBJECT-TYPE 2884 SYNTAX RowStatus 2885 MAX-ACCESS read-create 2886 STATUS current 2887 DESCRIPTION 2888 "This object is used to create a new row or modify or 2889 delete an existing row in this table. 2891 A profile activated by setting this object to `active'. 2892 When `active' is set, the system will validate the profile. 2894 Before a profile can be deleted or taken out of 2895 service, (by setting this object to `destroy' or 2896 `outOfService') it must be first unreferenced 2897 from all associated lines." 2898 ::= { vdslLineMCMConfProfileMaxTxPSDEntry 4 } 2900 vdslLineMCMConfProfileMaxRxPSDTable OBJECT-TYPE 2901 SYNTAX SEQUENCE OF VdslLineMCMConfProfileMaxRxPSDEntry 2902 MAX-ACCESS not-accessible 2903 STATUS current 2904 DESCRIPTION 2905 "This table contains maximum receive PSD mask descriptor 2906 configuration information for a VDSL line. Each entry in 2907 this table reflects the configuration for one tone within 2908 a multiple carrier modulation (MCM) VDSL modem. These 2909 entries are defined by a manager and can be used to 2910 configure the VDSL line. 2912 The entries in this table MUST NOT be used for single 2913 carrier (SCM) VDSL lines." 2914 ::= { vdslMibObjects 17 } 2916 vdslLineMCMConfProfileMaxRxPSDEntry OBJECT-TYPE 2917 SYNTAX VdslLineMCMConfProfileMaxRxPSDEntry 2918 MAX-ACCESS not-accessible 2919 STATUS current 2920 DESCRIPTION 2921 "Each entry consists of a transmit PSD mask descriptor, 2922 which defines the power spectral density (PSD) for a 2923 tone. 2925 A default profile with an index of 1 will always exist and 2926 its parameters will be set to vendor specific values, 2927 unless otherwise specified in this document." 2928 INDEX { vdslLineConfProfileIndex, 2929 vdslMCMConfProfileMaxRxPSDNumber } 2930 ::= { vdslLineMCMConfProfileMaxRxPSDTable 1 } 2932 VdslLineMCMConfProfileMaxRxPSDEntry ::= 2933 SEQUENCE 2934 { 2935 vdslMCMConfProfileMaxRxPSDNumber Unsigned32, 2936 vdslMCMConfProfileMaxRxPSDTone Unsigned32, 2937 vdslMCMConfProfileMaxRxPSDPSD Unsigned32, 2938 vdslMCMConfProfileMaxRxPSDRowStatus RowStatus 2939 } 2941 vdslMCMConfProfileMaxRxPSDNumber OBJECT-TYPE 2942 SYNTAX Unsigned32 2943 MAX-ACCESS not-accessible 2944 STATUS current 2945 DESCRIPTION 2946 "The index for this band descriptor entry." 2947 ::= { vdslLineMCMConfProfileMaxRxPSDEntry 1 } 2949 vdslMCMConfProfileMaxRxPSDTone OBJECT-TYPE 2950 SYNTAX Unsigned32 2951 MAX-ACCESS read-create 2952 STATUS current 2953 DESCRIPTION 2954 "The tone index for which the PSD is being specified." 2955 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 2956 ::= { vdslLineMCMConfProfileMaxRxPSDEntry 2 } 2958 vdslMCMConfProfileMaxRxPSDPSD OBJECT-TYPE 2959 SYNTAX Unsigned32 2960 UNITS "0.5dBm" 2961 MAX-ACCESS read-create 2962 STATUS current 2963 DESCRIPTION 2964 "Power Spectral Density level in steps of 0.5dB with 2965 an offset of -140dbm/Hz." 2966 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 2967 ::= { vdslLineMCMConfProfileMaxRxPSDEntry 3 } 2969 vdslMCMConfProfileMaxRxPSDRowStatus OBJECT-TYPE 2970 SYNTAX RowStatus 2971 MAX-ACCESS read-create 2972 STATUS current 2973 DESCRIPTION 2974 "This object is used to create a new row or modify or 2975 delete an existing row in this table. 2977 A profile activated by setting this object to `active'. 2978 When `active' is set, the system will validate the profile. 2980 Before a profile can be deleted or taken out of 2981 service, (by setting this object to `destroy' or 2982 `outOfService') it must be first unreferenced 2983 from all associated lines." 2984 ::= { vdslLineMCMConfProfileMaxRxPSDEntry 4 } 2986 -- 2987 -- Single carrier modulation (SCM) configuration profile tables 2988 -- 2990 vdslLineSCMConfProfileTable OBJECT-TYPE 2991 SYNTAX SEQUENCE OF VdslLineSCMConfProfileEntry 2992 MAX-ACCESS not-accessible 2993 STATUS current 2994 DESCRIPTION 2995 "This table contains information on the VDSL line 2996 configuration. One entry in this table reflects a 2997 profile defined by a manager which can be used to 2998 configure the VDSL line. 3000 The entries in this table MUST NOT be used for 3001 multiple carrier (MCM) VDSL lines." 3002 ::= { vdslMibObjects 18 } 3004 vdslLineSCMConfProfileEntry OBJECT-TYPE 3005 SYNTAX VdslLineSCMConfProfileEntry 3006 MAX-ACCESS not-accessible 3007 STATUS current 3008 DESCRIPTION 3009 "Each entry consists of a list of parameters that 3010 represents the configuration of a single carrier 3011 modulation VDSL modem. 3013 A default profile with an index of 1 MUST always exist and 3014 its parameters will be set to vendor specific values, 3015 unless otherwise specified in this document." 3016 INDEX { vdslLineConfProfileIndex, 3017 vdslSCMConfProfileSide } 3018 ::= { vdslLineSCMConfProfileTable 1 } 3020 VdslLineSCMConfProfileEntry ::= 3021 SEQUENCE 3022 { 3023 vdslSCMConfProfileSide VdslLineEntity, 3024 vdslSCMConfProfileInterleaveDepth Unsigned32, 3025 vdslSCMConfProfileNumCarriers INTEGER, 3026 vdslSCMConfProfileFastCodewordSize Unsigned32, 3027 vdslSCMConfProfileTransmitPSDMask BITS, 3028 vdslSCMConfProfileVendorNotch1Start Unsigned32, 3029 vdslSCMConfProfileVendorNotch1Stop Unsigned32, 3030 vdslSCMConfProfileVendorNotch2Start Unsigned32, 3031 vdslSCMConfProfileVendorNotch2Stop Unsigned32, 3032 vdslSCMConfProfileFastFecSize INTEGER, 3033 vdslSCMConfProfileSlowBlockSize INTEGER, 3034 vdslSCMConfProfileRowStatus RowStatus 3035 } 3037 vdslSCMConfProfileSide OBJECT-TYPE 3038 SYNTAX VdslLineEntity 3039 MAX-ACCESS not-accessible 3040 STATUS current 3041 DESCRIPTION 3042 "Identifies whether this entry describes downstream 3043 or upstream transmission." 3044 ::= { vdslLineSCMConfProfileEntry 1 } 3046 vdslSCMConfProfileInterleaveDepth OBJECT-TYPE 3047 SYNTAX Unsigned32 (0..64) 3048 MAX-ACCESS read-create 3049 STATUS current 3050 DESCRIPTION 3051 "Specifies the interleaving depth." 3052 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 3053 ::= { vdslLineSCMConfProfileEntry 2 } 3055 vdslSCMConfProfileNumCarriers OBJECT-TYPE 3056 SYNTAX INTEGER 3057 { 3058 oneCarrier(1), 3059 twoCarriers(2) 3060 } 3061 MAX-ACCESS read-create 3062 STATUS current 3063 DESCRIPTION 3064 "Specifies the number of carriers." 3065 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 3066 ::= { vdslLineSCMConfProfileEntry 3 } 3068 vdslSCMConfProfileFastCodewordSize OBJECT-TYPE 3069 SYNTAX Unsigned32 (0..180) 3070 UNITS "octets" 3071 MAX-ACCESS read-create 3072 STATUS current 3073 DESCRIPTION 3074 "Specifies the length in octets of the fast codeword. 3075 A value of 0 indicates that the single latency transport 3076 class is to be utilized." 3077 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 3078 ::= { vdslLineSCMConfProfileEntry 4 } 3080 vdslSCMConfProfileTransmitPSDMask OBJECT-TYPE 3081 SYNTAX BITS 3082 { 3083 vendorNotch1(0), -- vendor specific notch 3084 vendorNotch2(1), -- vendor specific notch 3085 amateurBand30m(2), -- amateur radio band notch 3086 amateurBand40m(3), -- amateur radio band notch 3087 amateurBand80m(4), -- amateur radio band notch 3088 amateurBand160m(5) -- amateur radio band notch 3089 } 3090 MAX-ACCESS read-create 3091 STATUS current 3092 DESCRIPTION 3093 "The transmit power spectral density mask code. 3095 Amateur radio band notching is defined in the VDSL 3096 spectrum as follows: 3098 Band Start Frequency Stop Frequecy 3099 ---- ------------------ -------------------------------- 3100 30m 1810 kHz 2000 kHz 3101 40m 3500 kHz 3800 kHz (ETSI); 4000 kHz (ANSI) 3102 80m 7000 kHz 7100 kHz (ETSI); 7300 kHz (ANSI) 3103 160m 10100 kHz 10150 kHz 3105 Notching for each standard band can be enabled or disabled 3106 via the bit mask. 3108 Two custom, or vendor specific, notches may be specified. 3109 If either of these are enabled via the bit mask, then the 3110 following objects MUST be specified: 3112 If vendorNotch1 is enabled, then both 3113 vdslSCMConfProfileVendorNotch1Start 3114 vdslSCMConfProfileVendorNotch1Stop 3115 MUST be specified. 3117 If vendorNotch2 is enabled, then both 3118 vdslSCMConfProfileVendorNotch2Start 3119 vdslSCMConfProfileVendorNotch2Stop 3120 MUST be specified." 3121 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 3122 ::= { vdslLineSCMConfProfileEntry 5 } 3124 vdslSCMConfProfileVendorNotch1Start OBJECT-TYPE 3125 SYNTAX Unsigned32 3126 UNITS "kHz" 3127 MAX-ACCESS read-create 3128 STATUS current 3129 DESCRIPTION 3130 "Specifies the start frequency of the vendor-specific 3131 amateur radio notch 1." 3132 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 3133 ::= { vdslLineSCMConfProfileEntry 6 } 3135 vdslSCMConfProfileVendorNotch1Stop OBJECT-TYPE 3136 SYNTAX Unsigned32 3137 UNITS "kHz" 3138 MAX-ACCESS read-create 3139 STATUS current 3140 DESCRIPTION 3141 "Specifies the stop frequency of the vendor-specific 3142 amateur radio notch 1." 3143 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 3144 ::= { vdslLineSCMConfProfileEntry 7 } 3146 vdslSCMConfProfileVendorNotch2Start OBJECT-TYPE 3147 SYNTAX Unsigned32 3148 UNITS "kHz" 3149 MAX-ACCESS read-create 3150 STATUS current 3151 DESCRIPTION 3152 "Specifies the start frequency of the vendor-specific 3153 amateur radio notch 2." 3154 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 3155 ::= { vdslLineSCMConfProfileEntry 8 } 3157 vdslSCMConfProfileVendorNotch2Stop OBJECT-TYPE 3158 SYNTAX Unsigned32 3159 UNITS "kHz" 3160 MAX-ACCESS read-create 3161 STATUS current 3162 DESCRIPTION 3163 "Specifies the stop frequency of the vendor-specific 3164 amateur radio notch 2." 3165 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 3166 ::= { vdslLineSCMConfProfileEntry 9 } 3168 vdslSCMConfProfileFastFecSize OBJECT-TYPE 3169 SYNTAX INTEGER 3170 { 3171 noFEC(1), 3172 fecSize2(2), 3173 fecSize4(3), 3174 fecSize16(4) 3175 } 3176 MAX-ACCESS read-create 3177 STATUS current 3178 DESCRIPTION 3179 "When fast channel is being used, this object specifies 3180 the size of the forward error correction (FEC) codeword." 3181 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 3182 ::= { vdslLineSCMConfProfileEntry 10 } 3184 vdslSCMConfProfileSlowBlockSize OBJECT-TYPE 3185 SYNTAX INTEGER 3186 { 3187 s8(1), 3188 s4(2), 3189 s2(3) 3190 } 3191 MAX-ACCESS read-create 3192 STATUS current 3193 DESCRIPTION 3194 "Specifies the slow channel interleaved block size. 3195 Options are s/8, s/4, or s/2." 3196 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 3197 ::= { vdslLineSCMConfProfileEntry 11 } 3199 vdslSCMConfProfileRowStatus OBJECT-TYPE 3200 SYNTAX RowStatus 3201 MAX-ACCESS read-create 3202 STATUS current 3203 DESCRIPTION 3204 "This object is used to create a new row or modify or 3205 delete an existing row in this table. 3207 A profile activated by setting this object to `active'. 3208 When `active' is set, the system will validate the profile. 3210 Before a profile can be deleted or taken out of 3211 service, (by setting this object to `destroy' or 3212 `outOfService') it must be first unreferenced 3213 from all associated lines." 3214 ::= { vdslLineSCMConfProfileEntry 12 } 3216 vdslLineSCMConfProfileTxBandTable OBJECT-TYPE 3217 SYNTAX SEQUENCE OF VdslLineSCMConfProfileTxBandEntry 3218 MAX-ACCESS not-accessible 3219 STATUS current 3220 DESCRIPTION 3221 "This table contains transmit band descriptor configuration 3222 information for a VDSL line. Each entry in this table 3223 reflects the configuration for one of possibly three bands 3224 with a single carrier modulation (SCM) VDSL line. These 3225 entries are defined by a manager and can be used to configure 3226 the VDSL line. 3228 The entries in this table MUST NOT be used for 3229 multiple carrier (MCM) VDSL lines." 3230 ::= { vdslMibObjects 19 } 3232 vdslLineSCMConfProfileTxBandEntry OBJECT-TYPE 3233 SYNTAX VdslLineSCMConfProfileTxBandEntry 3234 MAX-ACCESS not-accessible 3235 STATUS current 3236 DESCRIPTION 3237 "Each entry consists of a list of parameters that 3238 represents the configuration of a single carrier 3239 modulation VDSL modem transmit band. 3241 A default profile with an index of 1 MUST always exist and 3242 its parameters will be set to vendor specific values, 3243 unless otherwise specified in this document." 3244 INDEX { vdslLineConfProfileIndex, 3245 vdslSCMConfProfileTxBandSide, 3246 vdslSCMConfProfileTxBandNumber } 3247 ::= { vdslLineSCMConfProfileTxBandTable 1 } 3249 VdslLineSCMConfProfileTxBandEntry ::= 3250 SEQUENCE 3251 { 3252 vdslSCMConfProfileTxBandSide VdslLineEntity, 3253 vdslSCMConfProfileTxBandNumber INTEGER, 3254 vdslSCMConfProfileTxBandTransmitPSDLevel Unsigned32, 3255 vdslSCMConfProfileTxBandSymbolRateProfile Unsigned32, 3256 vdslSCMConfProfileTxBandConstellationSize Unsigned32, 3257 vdslSCMConfProfileTxBandCenterFrequency Unsigned32, 3258 vdslSCMConfProfileTxBandRowStatus RowStatus 3259 } 3261 vdslSCMConfProfileTxBandSide OBJECT-TYPE 3262 SYNTAX VdslLineEntity 3263 MAX-ACCESS not-accessible 3264 STATUS current 3265 DESCRIPTION 3266 "Identifies whether this band entry describes 3267 downstream or upstream transmission." 3268 ::= { vdslLineSCMConfProfileTxBandEntry 1 } 3270 vdslSCMConfProfileTxBandNumber OBJECT-TYPE 3271 SYNTAX INTEGER 3272 { 3273 band1(1), 3274 band2(2), 3275 upstreamU0(3) 3276 } 3277 MAX-ACCESS not-accessible 3278 STATUS current 3279 DESCRIPTION 3280 "The SCN transmit band number for this entry." 3281 ::= { vdslLineSCMConfProfileTxBandEntry 2 } 3283 vdslSCMConfProfileTxBandTransmitPSDLevel OBJECT-TYPE 3284 SYNTAX Unsigned32 3285 UNITS "-dBm/Hz" 3286 MAX-ACCESS read-create 3287 STATUS current 3288 DESCRIPTION 3289 "The transmit power spectral density for the VDSL modem." 3290 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 3291 ::= { vdslLineSCMConfProfileTxBandEntry 3 } 3293 vdslSCMConfProfileTxBandSymbolRateProfile OBJECT-TYPE 3294 SYNTAX Unsigned32 3295 UNITS "kbaud" 3296 MAX-ACCESS read-create 3297 STATUS current 3298 DESCRIPTION 3299 "The symbol rate profile calculated as S = SR/BSR, where 3300 SR is the required symbol rate in kbaud, BSR = 67.5." 3301 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 3302 ::= { vdslLineSCMConfProfileTxBandEntry 4 } 3304 vdslSCMConfProfileTxBandConstellationSize OBJECT-TYPE 3305 SYNTAX Unsigned32 (0..8) 3306 UNITS "log2" 3307 MAX-ACCESS read-create 3308 STATUS current 3309 DESCRIPTION 3310 "Specifies the constellation size." 3311 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 3312 ::= { vdslLineSCMConfProfileTxBandEntry 5 } 3314 vdslSCMConfProfileTxBandCenterFrequency OBJECT-TYPE 3315 SYNTAX Unsigned32 (0..511) 3316 UNITS "33.75kHz" 3317 MAX-ACCESS read-create 3318 STATUS current 3319 DESCRIPTION 3320 "Specifies the center frequency profile K." 3321 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 3322 ::= { vdslLineSCMConfProfileTxBandEntry 6 } 3324 vdslSCMConfProfileTxBandRowStatus OBJECT-TYPE 3325 SYNTAX RowStatus 3326 MAX-ACCESS read-create 3327 STATUS current 3328 DESCRIPTION 3329 "This object is used to create a new row or modify or 3330 delete an existing row in this table. 3332 A profile activated by setting this object to `active'. 3333 When `active' is set, the system will validate the profile. 3335 Before a profile can be deleted or taken out of 3336 service, (by setting this object to `destroy' or 3337 `outOfService') it must be first unreferenced 3338 from all associated lines." 3339 ::= { vdslLineSCMConfProfileTxBandEntry 7 } 3341 -- 3342 -- Alarm configuration profile table 3343 -- 3345 vdslLineAlarmConfProfileTable OBJECT-TYPE 3346 SYNTAX SEQUENCE OF VdslLineAlarmConfProfileEntry 3347 MAX-ACCESS not-accessible 3348 STATUS current 3349 DESCRIPTION 3350 "This table contains information on the VDSL line alarm 3351 configuration. One entry in this table reflects a profile 3352 defined by a manager which can be used to configure the 3353 VDSL line alarm thresholds." 3354 ::= { vdslMibObjects 20 } 3356 vdslLineAlarmConfProfileEntry OBJECT-TYPE 3357 SYNTAX VdslLineAlarmConfProfileEntry 3358 MAX-ACCESS not-accessible 3359 STATUS current 3360 DESCRIPTION 3361 "Each entry consists of a list of parameters that 3362 represents the configuration of a VDSL line alarm 3363 profile. 3365 A default profile with an index of 1 MUST always exist and 3366 its parameters will be set to vendor specific values, 3367 unless otherwise specified in this document." 3368 INDEX { vdslLineAlarmConfProfileIndex } 3369 ::= { vdslLineAlarmConfProfileTable 1 } 3371 VdslLineAlarmConfProfileEntry ::= 3372 SEQUENCE 3373 { 3374 vdslLineAlarmConfProfileIndex Unsigned32, 3375 vdslLineAlarmConfProfileName SnmpAdminString, 3376 vdslThresh15MinLofs HCPerfIntervalThreshold, 3377 vdslThresh15MinLoss HCPerfIntervalThreshold, 3378 vdslThresh15MinLprs HCPerfIntervalThreshold, 3379 vdslThresh15MinESs HCPerfIntervalThreshold, 3380 vdslThresh15MinSESs HCPerfIntervalThreshold, 3381 vdslThresh15MinUASs HCPerfIntervalThreshold, 3382 vdslInitFailureNotificationEnable TruthValue, 3383 vdslLineAlarmConfProfileRowStatus RowStatus 3384 } 3386 vdslLineAlarmConfProfileIndex OBJECT-TYPE 3387 SYNTAX Unsigned32 3388 MAX-ACCESS not-accessible 3389 STATUS current 3390 DESCRIPTION 3391 "This object is used by the line alarm configuration table 3392 in order to identify a row in that table. The system MUST 3393 provide a default profile whose index is 1." 3394 ::= { vdslLineAlarmConfProfileEntry 1 } 3396 vdslLineAlarmConfProfileName OBJECT-TYPE 3397 SYNTAX SnmpAdminString (SIZE (1..32)) 3398 MAX-ACCESS read-create 3399 STATUS current 3400 DESCRIPTION 3401 "The name for this profile as specified by a user." 3402 ::= { vdslLineAlarmConfProfileEntry 2 } 3404 vdslThresh15MinLofs OBJECT-TYPE 3405 SYNTAX HCPerfIntervalThreshold 3406 UNITS "seconds" 3407 MAX-ACCESS read-create 3408 STATUS current 3409 DESCRIPTION 3410 "This object configures the threshold for the number of 3411 loss of frame seconds (lofs) within any given 15-minute 3412 performance data collection interval. If the value of 3413 loss of frame seconds in a particular 15-minute collection 3414 interval reaches/exceeds this value, a 3415 vdslPerfLofsThreshNotification notification will be 3416 generated. No more than one notification will be sent 3417 per interval." 3418 ::= { vdslLineAlarmConfProfileEntry 3 } 3420 vdslThresh15MinLoss OBJECT-TYPE 3421 SYNTAX HCPerfIntervalThreshold 3422 UNITS "seconds" 3423 MAX-ACCESS read-create 3424 STATUS current 3425 DESCRIPTION 3426 "This object configures the threshold for the number of 3427 loss of signal seconds (loss) within any given 15-minute 3428 performance data collection interval. If the value of 3429 loss of frame seconds in a particular 15-minute collection 3430 interval reaches/exceeds this value, a 3431 vdslPerfLossThreshNotification notification will be 3432 generated. One notification will be sent per interval 3433 per endpoint." 3434 ::= { vdslLineAlarmConfProfileEntry 4 } 3436 vdslThresh15MinLprs OBJECT-TYPE 3437 SYNTAX HCPerfIntervalThreshold 3438 UNITS "seconds" 3439 MAX-ACCESS read-create 3440 STATUS current 3441 DESCRIPTION 3442 "This object configures the threshold for the number of 3443 loss of power seconds (lprs) within any given 15-minute 3444 performance data collection interval. If the value of 3445 loss of frame seconds in a particular 15-minute collection 3446 interval reaches/exceeds this value, a 3447 vdslPerfLprsThreshNotification notification will be 3448 generated. No more than one notification will be sent 3449 per interval." 3450 ::= { vdslLineAlarmConfProfileEntry 5 } 3452 vdslThresh15MinESs OBJECT-TYPE 3453 SYNTAX HCPerfIntervalThreshold 3454 UNITS "seconds" 3455 MAX-ACCESS read-create 3456 STATUS current 3457 DESCRIPTION 3458 "This object configures the threshold for the number of 3459 errored seconds (ESs) within any given 15-minute 3460 performance data collection interval. If the value of 3461 errored seconds in a particular 15-minute collection 3462 interval reaches/exceeds this value, a 3463 vdslPerfESsThreshNotification notification will be 3464 generated. No more than one notification will be sent 3465 per interval." 3466 ::= { vdslLineAlarmConfProfileEntry 6 } 3468 vdslThresh15MinSESs OBJECT-TYPE 3469 SYNTAX HCPerfIntervalThreshold 3470 UNITS "seconds" 3471 MAX-ACCESS read-create 3472 STATUS current 3473 DESCRIPTION 3474 "This object configures the threshold for the number of 3475 severely errored seconds (SESs) within any given 15-minute 3476 performance data collection interval. If the value of 3477 severely errored seconds in a particular 15-minute 3478 collection interval reaches/exceeds this value, a 3479 vdslPerfSESsThreshNotification notification will be 3480 generated. No more than one notification will be sent 3481 per interval." 3482 ::= { vdslLineAlarmConfProfileEntry 7 } 3484 vdslThresh15MinUASs OBJECT-TYPE 3485 SYNTAX HCPerfIntervalThreshold 3486 UNITS "seconds" 3487 MAX-ACCESS read-create 3488 STATUS current 3489 DESCRIPTION 3490 "This object configures the threshold for the number of 3491 unavailable seconds (UASs) within any given 15-minute 3492 performance data collection interval. If the value of 3493 unavailable seconds in a particular 15-minute collection 3494 interval reaches/exceeds this value, a 3495 vdslPerfUASsThreshNotification notification will be 3496 generated. No more than one notification will be sent 3497 per interval." 3498 ::= { vdslLineAlarmConfProfileEntry 8 } 3500 vdslInitFailureNotificationEnable OBJECT-TYPE 3501 SYNTAX TruthValue 3502 MAX-ACCESS read-create 3503 STATUS current 3504 DESCRIPTION 3505 "This object specifies if a vdslInitFailureNotification 3506 notification will be generated if an initialization 3507 failure occurs." 3508 ::= { vdslLineAlarmConfProfileEntry 9 } 3510 vdslLineAlarmConfProfileRowStatus OBJECT-TYPE 3511 SYNTAX RowStatus 3512 MAX-ACCESS read-create 3513 STATUS current 3514 DESCRIPTION 3515 "This object is used to create a new row or modify or 3516 delete an existing row in this table. 3518 A profile activated by setting this object to `active'. 3519 When `active' is set, the system will validate the profile. 3521 Before a profile can be deleted or taken out of service, 3522 (by setting this object to `destroy' or `outOfService') it 3523 must be first unreferenced from all associated lines." 3524 ::= { vdslLineAlarmConfProfileEntry 10 } 3526 -- Notification definitions 3528 vdslNotifications OBJECT IDENTIFIER ::= { vdslLineMib 0 } 3530 vdslPerfLofsThreshNotification NOTIFICATION-TYPE 3531 OBJECTS { 3532 vdslPerfCurr15MinLofs, 3533 vdslThresh15MinLofs 3534 } 3535 STATUS current 3536 DESCRIPTION 3537 "Loss of Framing 15-minute interval threshold reached." 3538 ::= { vdslNotifications 1 } 3540 vdslPerfLossThreshNotification NOTIFICATION-TYPE 3541 OBJECTS { 3542 vdslPerfCurr15MinLoss, 3543 vdslThresh15MinLoss 3544 } 3545 STATUS current 3546 DESCRIPTION 3547 "Loss of Signal 15-minute interval threshold reached." 3548 ::= { vdslNotifications 2 } 3550 vdslPerfLprsThreshNotification NOTIFICATION-TYPE 3551 OBJECTS { 3552 vdslPerfCurr15MinLprs, 3553 vdslThresh15MinLprs 3554 } 3555 STATUS current 3556 DESCRIPTION 3557 "Loss of Power 15-minute interval threshold reached." 3558 ::= { vdslNotifications 3 } 3560 vdslPerfESsThreshNotification NOTIFICATION-TYPE 3561 OBJECTS { 3562 vdslPerfCurr15MinESs, 3563 vdslThresh15MinESs 3564 } 3565 STATUS current 3566 DESCRIPTION 3567 "Errored Seconds 15-minute interval threshold reached." 3568 ::= { vdslNotifications 4 } 3570 vdslPerfSESsThreshNotification NOTIFICATION-TYPE 3571 OBJECTS { 3572 vdslPerfCurr15MinSESs, 3573 vdslThresh15MinSESs 3574 } 3575 STATUS current 3576 DESCRIPTION 3577 "Severely Errored Seconds 15-minute interval threshold 3578 reached." 3579 ::= { vdslNotifications 5 } 3581 vdslPerfUASsThreshNotification NOTIFICATION-TYPE 3582 OBJECTS { 3583 vdslPerfCurr15MinUASs, 3584 vdslThresh15MinUASs 3585 } 3586 STATUS current 3587 DESCRIPTION 3588 "Unavailable Seconds 15-minute interval threshold reached." 3589 ::= { vdslNotifications 6 } 3591 vdslDownMaxSnrMgnExceededNotification NOTIFICATION-TYPE 3592 OBJECTS { 3593 vdslCurrSnrMgn, 3594 vdslLineConfDownstreamMaxSnrMgn 3595 } 3596 STATUS current 3597 DESCRIPTION 3598 "The downstream Signal to Noise Margin exceeded 3599 vdslLineConfDownstreamMaxSnrMgn. The object 3600 vdslCurrSnrMgn will contain the Signal to Noise 3601 margin as measured by the VTU-R." 3602 ::= { vdslNotifications 7 } 3604 vdslDownMinSnrMgnExceededNotification NOTIFICATION-TYPE 3605 OBJECTS { 3606 vdslCurrSnrMgn, 3607 vdslLineConfDownstreamMinSnrMgn 3608 } 3609 STATUS current 3610 DESCRIPTION 3611 "The downstream Signal to Noise Margin fell below 3612 vdslLineConfDownstreamMinSnrMgn. The object 3613 vdslCurrSnrMgn will contain the Signal to Noise 3614 margin as measured by the VTU-R." 3615 ::= { vdslNotifications 8 } 3617 vdslUpMaxSnrMgnExceededNotification NOTIFICATION-TYPE 3618 OBJECTS { 3619 vdslCurrSnrMgn, 3620 vdslLineConfUpstreamMaxSnrMgn 3621 } 3622 STATUS current 3623 DESCRIPTION 3624 "The upstream Signal to Noise Margin exceeded 3625 vdslLineConfDownstreamMaxSnrMgn. The object 3626 vdslCurrSnrMgn will contain the Signal to Noise 3627 margin as measured by the VTU-C." 3628 ::= { vdslNotifications 9 } 3630 vdslUpMinSnrMgnExceededNotification NOTIFICATION-TYPE 3631 OBJECTS { 3632 vdslCurrSnrMgn, 3633 vdslLineConfUpstreamMinSnrMgn 3634 } 3635 STATUS current 3636 DESCRIPTION 3637 "The upstream Signal to Noise Margin fell below 3638 vdslLineConfDownstreamMinSnrMgn. The object 3639 vdslCurrSnrMgn will contain the Signal to Noise 3640 margin as measured by the VTU-C." 3641 ::= { vdslNotifications 10 } 3643 vdslInitFailureNotification NOTIFICATION-TYPE 3644 OBJECTS { 3645 vdslCurrStatus 3646 } 3647 STATUS current 3648 DESCRIPTION 3649 "Vtu initialization failed. See vdslCurrStatus for 3650 potential reasons." 3651 ::= { vdslNotifications 11 } 3653 -- conformance information 3655 vdslConformance OBJECT IDENTIFIER ::= { vdslLineMib 3 } 3656 vdslGroups OBJECT IDENTIFIER ::= { vdslConformance 1 } 3657 vdslCompliances OBJECT IDENTIFIER ::= { vdslConformance 2 } 3658 vdslLineMibCompliance MODULE-COMPLIANCE 3659 STATUS current 3660 DESCRIPTION 3661 "The compliance statement for SNMP entities which 3662 manage VDSL interfaces." 3664 MODULE -- this module 3665 MANDATORY-GROUPS 3666 { 3667 vdslGroup 3668 } 3670 GROUP vdslMCMGroup 3671 DESCRIPTION 3672 "This group is mandatory for VDSL Lines which 3673 utilize multiple carrier modulation (MCM)." 3674 GROUP vdslSCMGroup 3675 DESCRIPTION 3676 "This group is mandatory for VDSL lines which 3677 utilize single carrier modulation (SCM)." 3679 ::= { vdslCompliances 1 } 3681 -- units of conformance 3683 vdslGroup OBJECT-GROUP 3684 OBJECTS 3685 { 3686 vdslLineCoding, 3687 vdslLineType, 3688 vdslLineConfProfile, 3689 vdslLineAlarmConfProfile, 3690 vdslInvSerialNumber, 3691 vdslInvVendorID, 3692 vdslInvVersionNumber, 3693 vdslCurrSnrMgn, 3694 vdslCurrAtn, 3695 vdslCurrStatus, 3696 vdslCurrOutputPwr, 3697 vdslCurrAttainableRate, 3698 vdslChanInterleaveDelay, 3699 vdslChanCrcBlockLength, 3700 vdslChanCurrTxRate, 3701 vdslPerfValidIntervals, 3702 vdslPerfInvalidIntervals, 3703 vdslPerfLofs, 3704 vdslPerfLoss, 3705 vdslPerfLprs, 3706 vdslPerfESs, 3707 vdslPerfSESs, 3708 vdslPerfUASs, 3709 vdslPerfInits, 3710 vdslPerfCurr15MinTimeElapsed, 3711 vdslPerfCurr15MinLofs, 3712 vdslPerfCurr15MinLoss, 3713 vdslPerfCurr15MinLprs, 3714 vdslPerfCurr15MinESs, 3715 vdslPerfCurr15MinSESs, 3716 vdslPerfCurr15MinUASs, 3717 vdslPerfCurr15MinInits, 3718 vdslPerf1DayValidIntervals, 3719 vdslPerf1DayInvalidIntervals, 3720 vdslPerfCurr1DayTimeElapsed, 3721 vdslPerfCurr1DayLofs, 3722 vdslPerfCurr1DayLoss, 3723 vdslPerfCurr1DayLprs, 3724 vdslPerfCurr1DayESs, 3725 vdslPerfCurr1DaySESs, 3726 vdslPerfCurr1DayUASs, 3727 vdslPerfCurr1DayInits, 3728 vdslIntervalLofs, 3729 vdslIntervalLoss, 3730 vdslIntervalLprs, 3731 vdslIntervalESs, 3732 vdslIntervalSESs, 3733 vdslIntervalUASs, 3734 vdslIntervalInits, 3735 vdsl1DayIntervalMoniSecs, 3736 vdsl1DayIntervalLofs, 3737 vdsl1DayIntervalLoss, 3738 vdsl1DayIntervalLprs, 3739 vdsl1DayIntervalESs, 3740 vdsl1DayIntervalSESs, 3741 vdsl1DayIntervalUASs, 3742 vdsl1DayIntervalInits, 3743 vdslChanPerfValidIntervals, 3744 vdslChanPerfInvalidIntervals, 3745 vdslChanCorrectedOctets, 3746 vdslChanUncorrectBlks, 3747 vdslChanPerfCurr15MinTimeElapsed, 3748 vdslChanPerfCurr15MinCorrectedOctets, 3749 vdslChanPerfCurr15MinUncorrectBlks, 3750 vdslChanPerf1DayValidIntervals, 3751 vdslChanPerf1DayInvalidIntervals, 3752 vdslChanPerfCurr1DayTimeElapsed, 3753 vdslChanPerfCurr1DayCorrectedOctets, 3754 vdslChanPerfCurr1DayUncorrectBlks, 3755 vdslChanIntervalCorrectedOctets, 3756 vdslChanIntervalUncorrectBlks, 3757 vdslChan1DayIntervalMoniSecs, 3758 vdslChan1DayIntervalCorrectedOctets, 3759 vdslChan1DayIntervalUncorrectBlks, 3760 vdslLineConfProfileIndex, 3761 vdslLineConfProfileName, 3762 vdslLineConfDownstreamMaxPwr, 3763 vdslLineConfUpstreamMaxPwr, 3764 vdslLineConfDownstreamMaxSnrMgn, 3765 vdslLineConfDownstreamMinSnrMgn, 3766 vdslLineConfDownstreamTargetSnrMgn, 3767 vdslLineConfUpstreamMaxSnrMgn, 3768 vdslLineConfUpstreamMinSnrMgn, 3769 vdslLineConfUpstreamTargetSnrMgn, 3770 vdslLineConfDownstreamFastMaxDataRate, 3771 vdslLineConfDownstreamFastMinDataRate, 3772 vdslLineConfDownstreamSlowMaxDataRate, 3773 vdslLineConfDownstreamSlowMinDataRate, 3774 vdslLineConfUpstreamFastMaxDataRate, 3775 vdslLineConfUpstreamFastMinDataRate, 3776 vdslLineConfUpstreamSlowMaxDataRate, 3777 vdslLineConfUpstreamSlowMinDataRate, 3778 vdslLineConfRateAdaptationRatio, 3779 vdslLineConfUpstreamDataRate, 3780 vdslLineConfDownstreamDataRate, 3781 vdslLineConfDownstreamMaxInterDelay, 3782 vdslLineConfUpstreamMaxInterDelay, 3783 vdslLineConfUpstreamPboControl, 3784 vdslLineConfDownstreamPboControl, 3785 vdslLineConfDeploymentScenario, 3786 vdslLineConfAdslOccupy, 3787 vdslLineConfApplicableStandard, 3788 vdslLineConfBandPlan, 3789 vdslLineConfBandPlanFx, 3790 vdslLineConfBandU0Usage, 3791 vdslLineConfUpstreamPsdTemplate, 3792 vdslLineConfDownstreamPsdTemplate, 3793 vdslLineConfProfileRowStatus, 3794 vdslLineAlarmConfProfileName, 3795 vdslThresh15MinLofs, 3796 vdslThresh15MinLoss, 3797 vdslThresh15MinLprs, 3798 vdslThresh15MinESs, 3799 vdslThresh15MinSESs, 3800 vdslThresh15MinUASs, 3801 vdslInitFailureNotificationEnable, 3802 vdslLineAlarmConfProfileRowStatus 3803 } 3804 STATUS current 3805 DESCRIPTION 3806 "A collection of objects providing information about 3807 a VDSL Line." 3808 ::= { vdslGroups 1 } 3810 vdslMCMGroup OBJECT-GROUP 3811 OBJECTS 3812 { 3813 vdslMCMConfProfileTxWindowLength, 3814 vdslMCMConfProfileRowStatus, 3815 vdslMCMConfProfileTxBandStart, 3816 vdslMCMConfProfileTxBandStop, 3817 vdslMCMConfProfileTxBandRowStatus, 3818 vdslMCMConfProfileRxBandStart, 3819 vdslMCMConfProfileRxBandStop, 3820 vdslMCMConfProfileRxBandRowStatus, 3821 vdslMCMConfProfileTxPSDTone, 3822 vdslMCMConfProfileTxPSDPSD, 3823 vdslMCMConfProfileTxPSDRowStatus, 3824 vdslMCMConfProfileMaxTxPSDTone, 3825 vdslMCMConfProfileMaxTxPSDPSD, 3826 vdslMCMConfProfileMaxTxPSDRowStatus, 3827 vdslMCMConfProfileMaxRxPSDTone, 3828 vdslMCMConfProfileMaxRxPSDPSD, 3829 vdslMCMConfProfileMaxRxPSDRowStatus 3830 } 3831 STATUS current 3832 DESCRIPTION 3833 "A collection of objects providing configuration 3834 information for a VDSL line based upon multiple carrier 3835 modulation modem." 3836 ::= { vdslGroups 2 } 3838 vdslSCMGroup OBJECT-GROUP 3839 OBJECTS 3840 { 3841 vdslSCMPhysBandSnrMgn, 3842 vdslSCMPhysBandAtn, 3843 vdslSCMConfProfileInterleaveDepth, 3844 vdslSCMConfProfileNumCarriers, 3845 vdslSCMConfProfileFastCodewordSize, 3846 vdslSCMConfProfileTransmitPSDMask, 3847 vdslSCMConfProfileVendorNotch1Start, 3848 vdslSCMConfProfileVendorNotch1Stop, 3849 vdslSCMConfProfileVendorNotch2Start, 3850 vdslSCMConfProfileVendorNotch2Stop, 3851 vdslSCMConfProfileFastFecSize, 3852 vdslSCMConfProfileSlowBlockSize, 3853 vdslSCMConfProfileRowStatus, 3854 vdslSCMConfProfileTxBandTransmitPSDLevel, 3855 vdslSCMConfProfileTxBandSymbolRateProfile, 3856 vdslSCMConfProfileTxBandConstellationSize, 3857 vdslSCMConfProfileTxBandCenterFrequency, 3858 vdslSCMConfProfileTxBandRowStatus 3859 } 3860 STATUS current 3861 DESCRIPTION 3862 "A collection of objects providing configuration 3863 information for a VDSL line based upon single carrier 3864 modulation modem." 3865 ::= { vdslGroups 3 } 3867 vdslNotificationGroup NOTIFICATION-GROUP 3868 NOTIFICATIONS 3869 { 3870 vdslPerfLofsThreshNotification, 3871 vdslPerfLossThreshNotification, 3872 vdslPerfLprsThreshNotification, 3873 vdslPerfESsThreshNotification, 3874 vdslPerfSESsThreshNotification, 3875 vdslPerfUASsThreshNotification, 3876 vdslDownMaxSnrMgnExceededNotification, 3877 vdslDownMinSnrMgnExceededNotification, 3878 vdslUpMaxSnrMgnExceededNotification, 3879 vdslUpMinSnrMgnExceededNotification, 3880 vdslInitFailureNotification 3881 } 3882 STATUS current 3883 DESCRIPTION 3884 "This group supports notifications of significant 3885 conditions associated with VDSL Lines." 3886 ::= { vdslGroups 4 } 3888 END 3890 Normative References 3892 [ETSI2701] ETSI TS 101 270-1 V1.2.1 "Transmission and Multiplexing 3893 (TM); Access transmission systems on metallic access 3894 cables; Very high speed Digital Subscriber Line (VDSL); 3895 Part 1: Functional requirements", October 1999. 3897 [ETSI2702] ETSI TS 101 270-2 V1.1.1 "Transmission and Multiplexing 3898 (TM); Access transmission systems on metallic access 3899 cables; Very high speed Digital Subscriber Line (VDSL); 3900 Part 1: Transceiver specification", February 2001. 3902 [ITU9931] ITU-T G.993.1 "Very-high-speed digital subscriber line 3903 foundation", November 2001. 3905 [ITU9971] ITU-T G.997.1 "Physical layer management for Digital 3906 Subscriber Line (DSL) Transcievers", July 1999. 3908 [RFC1901] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 3909 "Introduction to Community-based SNMPv2", RFC 1901, 3910 January 1996. 3912 [RFC1905] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 3913 "Protocol Operations for Version 2 of the Simple Network 3914 Management Protocol (SNMPv2)", RFC 1905, January 1996. 3916 [RFC1906] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 3917 "Transport Mappings for Version 2 of the Simple Network 3918 Management Protocol (SNMPv2)", RFC 1906, January 1996. 3920 [RFC2119] Bradner, S., "Key Words for use in RFCs to Indicate 3921 Requirement Levels", RFC 2119, March 1997. 3923 [RFC2493] Tesink, K., "Textual Conventions for MIB Modules Using 3924 Performance History Based on 15 Minute Intervals", RFC 3925 2493, January 1999. 3927 [RFC2571] Harrington, D., Presuhn, R. and B. Wijnen, "An 3928 Architecture for Describing SNMP Management Frameworks", 3929 RFC 2571, April 1999. 3931 [RFC2572] Case, J., Harrington D., Presuhn, R. and B. Wijnen, 3932 "Message Processing and Dispatching for the Simple Network 3933 Management Protocol (SNMP)", RFC 2572, April 1999. 3935 [RFC2574] Blumenthal, U. and B. Wijnen, "User-based Security Model 3936 (USM) for version 3 of the Simple Network Management 3937 Protocol (SNMPv3)", RFC 2574, April 1999. 3939 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 3940 Rose, M. and S. Waldbusser, "Structure of Management 3941 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 3942 1999. 3944 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 3945 Rose, M. and S. Waldbusser, "Textual Conventions for 3946 SMIv2", STD 58, RFC 2579, April 1999. 3948 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 3949 Rose, M. and S. Waldbusser, "Conformance Statements for 3950 SMIv2", STD 58, RFC 2580, April 1999. 3952 [RFC2662] Bathrick, G. and F. Ly, "Definitions of Managed Objects 3953 for the ADSL Lines", RFC 2662, August 1999. 3955 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 3956 MIB", RFC 2863, June 2000. 3958 [T1E1311] ANSI T1E1.4/2001-311, "Very-high-bit-rate Digital 3959 Subscriber Line (VDSL) Metallic Interface, Part 1: 3960 Functional Requirements and Common Specification", February 3961 2001. 3963 [T1E1011] ANSI T1E1.4/2001-011R3, "VDSL Metallic Interface, Part 2: 3965 Technical Specification for a Single-Carrier Modulation 3966 (SCM) Transceiver", November 2001. 3968 [T1E1013] ANSI T1E1.4/2001-013R4, "VDSL Metallic Interface, Part 3: 3969 Technical Specification for a Multi-Carrier Modulation 3970 (MCM) Transceiver", November 2000. 3972 Informative References 3974 [RFC1155] Rose, M. and K. McCloghrie, "Structure and Identification 3975 of Management Information for TCP/IP-based Internets", STD 3976 16, RFC 1155, May 1990. 3978 [RFC1157] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple 3979 Network Management Protocol", STD 15, RFC 1157, May 1990. 3981 [RFC1212] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 3982 16, RFC 1212, March 1991. 3984 [RFC1215] Rose, M., "A Convention for Defining Traps for use with 3985 the SNMP", RFC 1215, March 1991. 3987 [RFC2570] Case, J., Mundy, R., Partain, D. and B. Stewart, 3988 "Introduction to Version 3 of the Internet-standard Network 3989 Management Framework", RFC 2570, April 1999. 3991 [RFC2573] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 Applications", 3992 RFC 2573, April 1999. 3994 [RFC2575] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based 3995 Access Control Model (VACM) for the Simple Network 3996 Management Protocol (SNMP)", RFC 2575, April 1999. 3998 Security Considerations 4000 There are a number of management objects defined in this MIB that 4001 have a MAX-ACCESS clause of read-write and/or read-create. Such 4002 objects may be considered sensitive or vulnerable in some network 4003 environments. The support for SET operations in a non-secure 4004 environment without proper protection can have a negative effect on 4005 network operations. 4007 VDSL layer connectivity from the Vtur will permit the subscriber 4008 to manipulate both the VDSL link directly and the VDSL embedded 4009 operations channel (EOC) for their own loop. For example, unchecked 4010 or unfiltered fluctuations initiated by the subscriber could generate 4011 sufficient notifications to potentially overwhelm either the 4012 management interface to the network or the element manager. 4014 For this reason, there are a number of managed objects in this MIB 4015 that may contain sensitive information. These are: 4017 vdslThresh15MinLofs 4018 vdslThresh15MinLoss 4019 vdslThresh15MinLprs 4020 vdslThresh15MinESs 4021 vdslThresh15MinSESs 4022 vdslThresh15MinUASs 4024 It is thus important to control even GET access to these objects and 4025 possibly to even encrypt the values of these objects when sending 4026 them over the network via SNMP. Not all versions of SNMP provide 4027 features for such a secure environment. 4029 Further, notifications generated by agents implementing this MIB 4030 will contain the above threshold information. 4032 SNMPv1 by itself is not a secure environment. Even if the network 4033 itself is secure (for example by using IPSec), even then, there is no 4034 control as to who on the secure network is allowed to access and 4035 GET/SET (read/change/create/delete) the objects in this MIB. 4037 It is recommended that the implementers consider the security 4038 features as provided by the SNMPv3 framework. Specifically, the use 4039 of the User-based Security Model RFC 2574 [12] and the View- 4040 based Access Control Model RFC 2575 [15] is recommended. 4042 It is then a customer/user responsibility to ensure that the SNMP 4043 entity giving access to an instance of this MIB, is properly 4044 configured to give access to the objects only to those principals 4045 (users) that have legitimate rights to indeed GET or SET 4046 (change/create/delete) them. 4048 IANA Considerations 4050 The VDSL-LINE-MIB MIB module requires the allocation of a single 4051 object identifier for its MODULE-IDENTITY. IANA should allocate 4052 this object identifier in the transmission subtree. 4054 Acknowledgments 4056 Umberto Bonollo (NEC) 4058 Andrew Cheers (NEC) 4060 David Horton (CiTR) 4062 Travis Levin (Paradyne) 4064 Moti Morgenstern (Inovia) 4066 Randy Presuhn (BMC) 4068 Intellectual Property Notice 4070 The IETF takes no position regarding the validity or scope of any 4071 intellectual property or other rights that might be claimed to 4072 pertain to the implementation or use of the technology described in 4073 this document or the extent to which any license under such rights 4074 might or might not be available; neither does it represent that it 4075 has made any effort to identify any such rights. Information on the 4076 IETF's procedures with respect to rights in standards-track and 4077 standards-related documentation can be found in BCP-11. Copies of 4078 claims of rights made available for publication and any assurances of 4079 licenses to be made available, or the result of an attempt made to 4080 obtain a general license or permission for the use of such 4081 proprietary rights by implementors or users of this specification can 4082 be obtained from the IETF Secretariat. 4084 The IETF invites any interested party to bring to its attention any 4085 copyrights, patents or patent applications, or other proprietary 4086 rights which may cover technology that may be required to practice 4087 this standard. Please address the information to the IETF Executive 4088 Director. 4090 Authors' Addresses 4092 Bob Ray 4093 PESA Switching Systems, Inc. 4094 330-A Wynn Drive 4095 Huntsville, AL 35805 USA 4097 Phone: +1 256 726 9200 ext. 142 4098 Fax: +1 256 726 9271 4099 EMail: rray@pesa.com 4101 Rajesh Abbi 4102 Alcatel USA 4103 2912 Wake Forest Road 4104 Raleigh, NC 27609-7860 USA 4106 Phone: +1 919 850 6194 4107 EMail: Rajesh.Abbi@alcatel.com 4109 Full Copyright Statement 4111 Copyright (C) The Internet Society (2002). All Rights Reserved. 4113 This document and translations of it may be copied and furnished to 4114 others, and derivative works that comment on or otherwise explain it 4115 or assist in its implementation may be prepared, copied, published 4116 and distributed, in whole or in part, without restriction of any 4117 kind, provided that the above copyright notice and this paragraph are 4118 included on all such copies and derivative works. However, this 4119 document itself may not be modified in any way, such as by removing 4120 the copyright notice or references to the Internet Society or other 4121 Internet organizations, except as needed for the purpose of 4122 developing Internet standards in which case the procedures for 4123 copyrights defined in the Internet Standards process must be 4124 followed, or as required to translate it into languages other than 4125 English. 4127 The limited permissions granted above are perpetual and will not be 4128 revoked by the Internet Society or its successors or assigns. 4129 This document and the information contained herein is provided on an 4130 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 4131 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 4132 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 4133 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 4134 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.