idnits 2.17.1 draft-ietf-adslmib-vdsl-05.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 8 instances of too long lines in the document, the longest one being 4 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 7857 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 4037 -- Looks like a reference, but probably isn't: '15' on line 4038 == Unused Reference: 'ETSI2701' is defined on line 3891, but no explicit reference was found in the text == Unused Reference: 'ETSI2702' is defined on line 3896, but no explicit reference was found in the text == Unused Reference: 'ITU9931' is defined on line 3901, but no explicit reference was found in the text == Unused Reference: 'ITU9971' is defined on line 3904, but no explicit reference was found in the text == Unused Reference: 'RFC2662' is defined on line 3951, but no explicit reference was found in the text == Unused Reference: 'T1E1311' is defined on line 3957, but no explicit reference was found in the text == Unused Reference: 'T1E1011' is defined on line 3962, but no explicit reference was found in the text == Unused Reference: 'T1E1013' is defined on line 3966, 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-05.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 ............................................... 12 60 References ................................................ 66 61 Security Considerations ................................... 68 62 IANA Considerations ....................................... 69 63 Acknowledgments ........................................... 69 64 Intellectual Property Notice .............................. 69 65 Authors' Addresses ........................................ 70 66 Full Copyright Statement .................................. 70 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 minute 489 interval, the counter is reset. When the first second goes by and 490 the event occurs, the current interval bucket will be 1, which 491 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 496 read-create), should be stored persistently. Following is an 497 exhaustive list of these persistent objects: 499 vdslLineConfProfile 500 vdslLineAlarmConfProfile 501 vdslLineConfProfileIndex 502 vdslLineConfProfileName 503 vdslLineConfDownstreamMaxPwr 504 vdslLineConfUpstreamMaxPwr 505 vdslLineConfDownstreamMaxSnrMgn 506 vdslLineConfDownstreamMinSnrMgn 507 vdslLineConfDownstreamTargetSnrMgn 508 vdslLineConfUpstreamMaxSnrMgn 509 vdslLineConfUpstreamMinSnrMgn 510 vdslLineConfUpstreamTargetSnrMgn 511 vdslLineConfDownstreamFastMaxDataRate 512 vdslLineConfDownstreamFastMinDataRate 513 vdslLineConfDownstreamSlowMaxDataRate 514 vdslLineConfDownstreamSlowMinDataRate 515 vdslLineConfUpstreamFastMaxDataRate 516 vdslLineConfUpstreamFastMinDataRate 517 vdslLineConfUpstreamSlowMaxDataRate 518 vdslLineConfUpstreamSlowMinDataRate 519 vdslLineConfRateAdaptationRatio 520 vdslLineConfUpstreamDataRate 521 vdslLineConfDownstreamDataRate 522 vdslLineConfDownstreamMaxInterDelay 523 vdslLineConfUpstreamMaxInterDelay 524 vdslLineConfUpstreamPboControl 525 vdslLineConfDownstreamPboControl 526 vdslLineConfDeploymentScenario 527 vdslLineConfAdslOccupy 528 vdslLineConfApplicableStandard 529 vdslLineConfBandPlan 530 vdslLineConfBandPlanFx 531 vdslLineConfBandU0Usage 532 vdslLineConfUpstreamPsdTemplate 533 vdslLineConfDownstreamPsdTemplate 534 vdslLineConfProfileRowStatus 535 vdslMCMConfProfileTxWindowLength 536 vdslMCMConfProfileRowStatus 537 vdslMCMConfProfileTxBandNumber 538 vdslMCMConfProfileTxBandStart 539 vdslMCMConfProfileTxBandStop 540 vdslMCMConfProfileTxBandRowStatus 541 vdslMCMConfProfileRxBandNumber 542 vdslMCMConfProfileRxBandStart 543 vdslMCMConfProfileRxBandStop 544 vdslMCMConfProfileRxBandRowStatus 545 vdslMCMConfProfileTxPSDNumber 546 vdslMCMConfProfileTxPSDTone 547 vdslMCMConfProfileTxPSDPSD 548 vdslMCMConfProfileTxPSDRowStatus 549 vdslMCMConfProfileMaxTxPSDNumber 550 vdslMCMConfProfileMaxTxPSDTone 551 vdslMCMConfProfileMaxTxPSDPSD 552 vdslMCMConfProfileMaxTxPSDRowStatus 553 vdslMCMConfProfileMaxRxPSDNumber 554 vdslMCMConfProfileMaxRxPSDTone 555 vdslMCMConfProfileMaxRxPSDPSD 556 vdslMCMConfProfileMaxRxPSDRowStatus 557 vdslSCMConfProfileSide 558 vdslSCMConfProfileInterleaveDepth 559 vdslSCMConfProfileNumCarriers 560 vdslSCMConfProfileFastCodewordSize 561 vdslSCMConfProfileTransmitPSDMask 562 vdslSCMConfProfileVendorNotch1Start 563 vdslSCMConfProfileVendorNotch1Stop 564 vdslSCMConfProfileVendorNotch2Start 565 vdslSCMConfProfileVendorNotch2Stop 566 vdslSCMConfProfileFastFecSize 567 vdslSCMConfProfileSlowBlockSize 568 vdslSCMConfProfileRowStatus 569 vdslSCMConfProfileTxBandNumber 570 vdslSCMConfProfileTxBandTransmitPSDLevel 571 vdslSCMConfProfileTxBandSymbolRateProfile 572 vdslSCMConfProfileTxBandConstellationSize 573 vdslSCMConfProfileTxBandCenterFrequency 574 vdslSCMConfProfileTxBandRowStatus 575 vdslLineAlarmConfProfileIndex 576 vdslLineAlarmConfProfileName 577 vdslThresh15MinLofs 578 vdslThresh15MinLoss 579 vdslThresh15MinLprs 580 vdslThresh15MinESs 581 vdslThresh15MinSESs 582 vdslThresh15MinUASs 583 vdslInitFailureNotificationEnable 584 vdslLineAlarmConfProfileRowStatus 586 It should also be noted that interface indices in this MIB are 587 maintained persistently. VACM data relating to these should be 588 stored persistently as well. 590 3. Conformance and Compliance 592 For VDSL lines, the following group is mandatory: 594 - vdslGroup 596 For MCM VDSL lines, the following group is optional: 598 - vdslSCMGroup 600 For SCM VDSL lines, the following group is optional: 602 - vdslMCMGroup 604 4. Definitions 605 VDSL-LINE-MIB DEFINITIONS ::= BEGIN 607 IMPORTS 609 MODULE-IDENTITY, 610 OBJECT-TYPE, 611 Counter64, 612 Gauge32, 613 Integer32, 614 Unsigned32, 615 NOTIFICATION-TYPE, 616 transmission FROM SNMPv2-SMI 617 TEXTUAL-CONVENTION, 618 RowStatus, 619 TruthValue FROM SNMPv2-TC 620 HCPerfValidIntervals, 621 HCPerfInvalidIntervals, 622 HCPerfTimeElapsed, 623 HCPerfIntervalThreshold, 624 HCPerfCurrentCount, 625 HCPerfIntervalCount FROM HC-PerfHist-TC-MIB 626 MODULE-COMPLIANCE, 627 OBJECT-GROUP, 628 NOTIFICATION-GROUP FROM SNMPv2-CONF 629 ifIndex FROM IF-MIB 630 SnmpAdminString FROM SNMP-FRAMEWORK-MIB; 632 vdslMIB MODULE-IDENTITY 633 LAST-UPDATED "200210150000Z" -- October 15, 2002 634 ORGANIZATION "ADSLMIB Working Group" 635 CONTACT-INFO "WG-email: adslmib@ietf.org 636 Info: https://www1.ietf.org/mailman/listinfo/adslmib 638 Chair: Mike Sneed 639 Postal: P.O. Box 37324 640 Raleigh NC 27627-7324 641 Email: sneedmike@hotmail.com 643 Co-editor: Bob Ray 644 PESA Switching Systems, Inc. 645 Postal: 330-A Wynn Drive 646 Huntsville, AL 35805 USA 647 Email: rray@pesa.com 648 Phone: +1 256 726 9200 ext. 142 650 Co-editor: Rajesh Abbi 651 Alcatel USA 652 Postal: 2912 Wake Forest Road 653 Raleigh, NC 27609-7860 USA 654 Email: Rajesh.Abbi@alcatel.com 655 Phone: +1 919 850 6194 657 " 658 DESCRIPTION 659 "The MIB module defining objects for the management of a pair of 660 VDSL modems at each end of the VDSL line. Each such line has 661 an entry in an ifTable which may include multiple modem lines. 662 An agent may reside at either end of the VDSL line however the 663 MIB is designed to require no management communication between 664 them beyond that inherent in the low-level VDSL line protocol. 665 The agent may monitor and control this protocol for its needs. 667 VDSL lines may support optional Fast or Interleaved channels. 668 If these are supported, additional entries corresponding to the 669 supported channels must be created in the ifTable. Thus a VDSL 670 line that supports both channels will have three entries in the 671 ifTable, one for each physical, fast, and interleaved, whose 672 ifType values are equal to vdsl(97), fast(125), and 673 interleaved(124), respectively. The ifStackTable is used to 674 represent the relationship between the entries. 676 Naming Conventions: 677 Vtuc -- (VTUC) modem at near (Central) end of line 678 Vtur -- (VTUR) modem at Remote end of line 679 Vtu -- One of either Vtuc or Vtur 680 Curr -- Current 681 Prev -- Previous 682 Atn -- Attenuation 683 ES -- Errored Second. 684 LCS -- Line Code Specific 685 Lof -- Loss of Frame 686 Lol -- Loss of Link 687 Los -- Loss of Signal 688 Lpr -- Loss of Power 689 xxxs -- interval of Seconds in which xxx occurs 690 (e.g., xxx=Lof, Los, Lpr) 691 Max -- Maximum 692 Mgn -- Margin 693 Min -- Minimum 694 Psd -- Power Spectral Density 695 Snr -- Signal to Noise Ratio 696 Tx -- Transmit 697 Blks -- Blocks 698 " 699 REVISION "200111010000Z" -- November 1, 2001 700 DESCRIPTION "Initial draft." 702 REVISION "200203310000Z" -- March 31, 2002 703 DESCRIPTION "Added R. Abbi as co-author." 705 REVISION "200204090000Z" -- April 9, 2002 706 DESCRIPTION "Removed use of IMPLIED profile indices." 707 REVISION "200206160000Z" -- June 16, 2002 708 DESCRIPTION "Revised per input from DSL Forum." 710 REVISION "200209230000Z" -- September 23, 2002 711 DESCRIPTION "Revised per more input from DSL Forum." 713 REVISION "200210150000Z" -- October 15, 2002 714 DESCRIPTION "Modified per input from Randy Presuhn and 715 Moti Morgenstern." 717 ::= { transmission xxxx } 719 vdslLineMib OBJECT IDENTIFIER ::= { vdslMIB 1 } 720 vdslMibObjects OBJECT IDENTIFIER ::= { vdslLineMib 1 } 722 -- 723 -- textual conventions used in this MIB 724 -- 726 VdslLineCodingType ::= TEXTUAL-CONVENTION 727 STATUS current 728 DESCRIPTION 729 "This data type is used as the syntax for the VDSL 730 Line Code." 731 SYNTAX INTEGER 732 { 733 other(1), -- none of the following 734 mcm(2), -- Multiple Carrier Modulation 735 scm(3) -- Single Carrier Modulation 736 } 738 VdslLineEntity ::= TEXTUAL-CONVENTION 739 STATUS current 740 DESCRIPTION 741 "Identifies a modem as being either Vtuc or Vtur. A 742 VDSL line consists of two modems, a Vtuc and a Vtur." 743 SYNTAX INTEGER 744 { 745 vtuc(1), -- central site modem 746 vtur(2) -- remote site modem 747 } 749 -- 750 -- objects 751 -- 753 vdslLineTable OBJECT-TYPE 754 SYNTAX SEQUENCE OF VdslLineEntry 755 MAX-ACCESS not-accessible 756 STATUS current 757 DESCRIPTION 758 "This table includes common attributes describing 759 both ends of the line. It is required for all VDSL 760 physical interfaces. VDSL physical interfaces are 761 those ifEntries where ifType is equal to vdsl(97)." 762 ::= { vdslMibObjects 1 } 764 vdslLineEntry OBJECT-TYPE 765 SYNTAX VdslLineEntry 766 MAX-ACCESS not-accessible 767 STATUS current 768 DESCRIPTION "An entry in the vdslLineTable." 769 INDEX { ifIndex } 770 ::= { vdslLineTable 1 } 772 VdslLineEntry ::= 773 SEQUENCE 774 { 775 vdslLineCoding VdslLineCodingType, 776 vdslLineType INTEGER, 777 vdslLineConfProfile Integer32, 778 vdslLineAlarmConfProfile Integer32 779 } 781 vdslLineCoding OBJECT-TYPE 782 SYNTAX VdslLineCodingType 783 MAX-ACCESS read-only 784 STATUS current 785 DESCRIPTION 786 "Specifies the VDSL coding type used on this line." 787 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 788 ::= { vdslLineEntry 1 } 790 vdslLineType OBJECT-TYPE 791 SYNTAX INTEGER 792 { 793 noChannel(1), -- no channels exist 794 fastOnly(2), -- fast channel only 795 slowOnly(3), -- slow channel only 796 either(4), -- either fast or slow channel exist 797 both(5) -- both fast and slow channels exist 798 } 799 MAX-ACCESS read-only 800 STATUS current 801 DESCRIPTION 802 "Defines the type of VDSL physical line 803 entity that exists, by defining whether and how 804 the line is channelized. If the line is channelized, 805 the value will be other than noChannel(1). This 806 object defines which channel type(s) are supported. 808 In the case that the line is channelized, the manager 809 can use the ifStackTable to determine the ifIndex for 810 the associated channel(s). 812 Note that slow and interleaved refer to the same 813 channel." 814 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 815 ::= { vdslLineEntry 2 } 817 vdslLineConfProfile OBJECT-TYPE 818 SYNTAX Integer32 819 MAX-ACCESS read-write 820 STATUS current 821 DESCRIPTION 822 "The value of this object identifies the row 823 in the VDSL Line Configuration Profile Table, 824 ( vdslLineConfProfileTable ), which applies for this 825 VDSL line, and channels if applicable." 826 ::= { vdslLineEntry 3 } 828 vdslLineAlarmConfProfile OBJECT-TYPE 829 SYNTAX Integer32 830 MAX-ACCESS read-write 831 STATUS current 832 DESCRIPTION 833 "The value of this object identifies the row in the VDSL 834 Line Alarm Configuration Profile Table, 835 ( vdslLineAlarmConfProfileTable ), which applies to this 836 VDSL line, and channels if applicable." 837 ::= { vdslLineEntry 4 } 839 vdslPhysTable OBJECT-TYPE 840 SYNTAX SEQUENCE OF VdslPhysEntry 841 MAX-ACCESS not-accessible 842 STATUS current 843 DESCRIPTION 844 "This table provides one row for each Vtu. Each row 845 contains the Physical Layer Parameters table for that 846 Vtu. VDSL physical interfaces are those ifEntries where 847 ifType is equal to vdsl(97)." 848 ::= { vdslMibObjects 2 } 850 vdslPhysEntry OBJECT-TYPE 851 SYNTAX VdslPhysEntry 852 MAX-ACCESS not-accessible 853 STATUS current 854 DESCRIPTION "An entry in the vdslPhysTable." 855 INDEX { ifIndex, 856 vdslPhysSide } 857 ::= { vdslPhysTable 1 } 859 VdslPhysEntry ::= 860 SEQUENCE 861 { 862 vdslPhysSide VdslLineEntity, 863 vdslInvSerialNumber SnmpAdminString, 864 vdslInvVendorID SnmpAdminString, 865 vdslInvVersionNumber SnmpAdminString, 866 vdslCurrSnrMgn Integer32, 867 vdslCurrAtn Gauge32, 868 vdslCurrStatus BITS, 869 vdslCurrOutputPwr Integer32, 870 vdslCurrAttainableRate Gauge32 871 } 873 vdslPhysSide OBJECT-TYPE 874 SYNTAX VdslLineEntity 875 MAX-ACCESS read-only 876 STATUS current 877 DESCRIPTION 878 "Identifies whether the modem is the Vtuc or Vtur." 879 ::= { vdslPhysEntry 1 } 881 vdslInvSerialNumber OBJECT-TYPE 882 SYNTAX SnmpAdminString(SIZE (0..32)) 883 MAX-ACCESS read-only 884 STATUS current 885 DESCRIPTION 886 "The vendor specific string that identifies the 887 vendor equipment." 888 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 889 ::= { vdslPhysEntry 2 } 891 vdslInvVendorID OBJECT-TYPE 892 SYNTAX SnmpAdminString (SIZE (0..16)) 893 MAX-ACCESS read-only 894 STATUS current 895 DESCRIPTION 896 "The vendor ID code is a copy of the binary vendor 897 identification field expressed as readable characters." 898 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 899 ::= { vdslPhysEntry 3 } 901 vdslInvVersionNumber OBJECT-TYPE 902 SYNTAX SnmpAdminString (SIZE (0..16)) 903 MAX-ACCESS read-only 904 STATUS current 905 DESCRIPTION 906 "The vendor specific version number sent by this Vtu 907 as part of the initialization messages. It is a copy 908 of the binary version number field expressed as 909 readable characters." 910 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 911 ::= { vdslPhysEntry 4 } 913 vdslCurrSnrMgn OBJECT-TYPE 914 SYNTAX Integer32 (-127..127) 915 UNITS "0.25dBm" 916 MAX-ACCESS read-only 917 STATUS current 918 DESCRIPTION 919 "Noise Margin as seen by this Vtu with respect to its 920 received signal in 0.25dB. The effective range is 921 -31.75 to +31.75dB." 922 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 923 ::= { vdslPhysEntry 5 } 925 vdslCurrAtn OBJECT-TYPE 926 SYNTAX Gauge32 (0..255) 927 UNITS "0.25dBm" 928 MAX-ACCESS read-only 929 STATUS current 930 DESCRIPTION 931 "Measured difference in the total power transmitted by 932 the peer Vtu and the total power received by this Vtu. 933 The effective range is 0 to +63.75dB." 934 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 935 ::= { vdslPhysEntry 6 } 937 vdslCurrStatus OBJECT-TYPE 938 SYNTAX BITS 939 { 940 noDefect(0), 941 lossOfFraming(1), 942 lossOfSignal(2), 943 lossOfPower(3), 944 lossOfSignalQuality(4), 945 lossOfLink(5), 946 dataInitFailure(6), 947 configInitFailure(7), 948 protocolInitFailure(8), 949 noPeerVtuPresent(9) 950 } 951 MAX-ACCESS read-only 952 STATUS current 953 DESCRIPTION 954 "Indicates current state of the Vtu line. This is a 955 bit-map of possible conditions. The various bit 956 positions are: 958 0 noDefect There no defects on the line 960 1 lossOfFraming Vtu failure due to not receiving 961 valid frame. 963 2 lossOfSignal Vtu failure due to not receiving 964 signal. 966 3 lossOfPower Vtu failure due to loss of power. 968 4 lossOfSignalQuality Loss of Signal Quality is declared 969 when the Noise Margin falls below 970 the Minimum Noise Margin, or the 971 bit-error-rate exceeds 10^-7. 973 5 lossOfLink Vtu failure due to inability to 974 link with peer Vtu. 976 6 dataInitFailure Vtu failure during initialization 977 due to bit errors corrupting 978 startup exchange data. 980 7 configInitFailure Vtu failure during initialization 981 due to peer Vtu not able to support 982 requested configuration. 984 8 protocolInitFailure Vtu failure during initialization 985 due to incompatible protocol used 986 by the peer Vtu. 988 9 noPeerVtuPresent Vtu failure during initialization 989 due to no activation sequence 990 detected from peer Vtu. 992 This is intended to supplement ifOperStatus." 993 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 994 ::= { vdslPhysEntry 7 } 996 vdslCurrOutputPwr OBJECT-TYPE 997 SYNTAX Integer32 (0..160) 998 UNITS "0.1dBm" 999 MAX-ACCESS read-only 1000 STATUS current 1001 DESCRIPTION 1002 "Measured total output power transmitted by this VTU. 1003 This is the measurement that was reported during 1004 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 } 1049 vdslChanInterleaveDelay OBJECT-TYPE 1050 SYNTAX Gauge32 1051 UNITS "ms" 1052 MAX-ACCESS read-only 1053 STATUS current 1054 DESCRIPTION 1055 "Interleave Delay for this channel. 1057 Interleave delay applies only to the interleave 1058 (slow) channel and defines the mapping (relative 1059 spacing) between subsequent input bytes at the 1060 interleaver input and their placement in the bit 1061 stream at the interleaver output. Larger numbers 1062 provide greater separation between consecutive 1063 input bytes in the output bit stream allowing for 1064 improved impulse noise immunity at the expense of 1065 payload latency. 1067 In the case where the ifType is fast(125), use 1068 noSuchObject." 1069 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1070 ::= { vdslChanEntry 1 } 1072 vdslChanCrcBlockLength OBJECT-TYPE 1073 SYNTAX Gauge32 1074 UNITS "byte" 1075 MAX-ACCESS read-only 1076 STATUS current 1077 DESCRIPTION 1078 "Indicates the length of the channel data-block 1079 on which the CRC operates." 1080 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1081 ::= { vdslChanEntry 2 } 1083 vdslPerfDataTable OBJECT-TYPE 1084 SYNTAX SEQUENCE OF VdslPerfDataEntry 1085 MAX-ACCESS not-accessible 1086 STATUS current 1087 DESCRIPTION 1088 "This table provides one row for each VDSL physical 1089 interface. VDSL physical interfaces are those ifEntries 1090 where ifType is equal to vdsl(97)." 1091 ::= { vdslMibObjects 4 } 1093 vdslPerfDataEntry OBJECT-TYPE 1094 SYNTAX VdslPerfDataEntry 1095 MAX-ACCESS not-accessible 1096 STATUS current 1097 DESCRIPTION 1098 "An entry in the vdslPerfDataTable." 1099 INDEX { ifIndex, 1100 vdslPhysSide } 1101 ::= { vdslPerfDataTable 1 } 1103 VdslPerfDataEntry ::= 1104 SEQUENCE 1105 { 1106 vdslPerfValidIntervals HCPerfValidIntervals, 1107 vdslPerfInvalidIntervals HCPerfInvalidIntervals, 1108 vdslPerfLofs Counter64, 1109 vdslPerfLoss Counter64, 1110 vdslPerfLprs Counter64, 1111 vdslPerfESs Counter64, 1112 vdslPerfSESs Counter64, 1113 vdslPerfUASs Counter64, 1114 vdslPerfInits Counter64, 1115 vdslPerfCurr15MinTimeElapsed HCPerfTimeElapsed, 1116 vdslPerfCurr15MinLofs HCPerfCurrentCount, 1117 vdslPerfCurr15MinLoss HCPerfCurrentCount, 1118 vdslPerfCurr15MinLprs HCPerfCurrentCount, 1119 vdslPerfCurr15MinESs HCPerfCurrentCount, 1120 vdslPerfCurr15MinSESs HCPerfCurrentCount, 1121 vdslPerfCurr15MinUASs HCPerfCurrentCount, 1122 vdslPerfCurr15MinInits HCPerfCurrentCount, 1123 vdslPerf1DayValidIntervals HCPerfValidIntervals, 1124 vdslPerf1DayInvalidIntervals HCPerfInvalidIntervals, 1125 vdslPerfCurr1DayTimeElapsed HCPerfTimeElapsed, 1126 vdslPerfCurr1DayLofs Counter64, 1127 vdslPerfCurr1DayLoss Counter64, 1128 vdslPerfCurr1DayLprs Counter64, 1129 vdslPerfCurr1DayESs Counter64, 1130 vdslPerfCurr1DaySESs Counter64, 1131 vdslPerfCurr1DayUASs Counter64, 1132 vdslPerfCurr1DayInits Counter64 1133 } 1135 vdslPerfValidIntervals OBJECT-TYPE 1136 SYNTAX HCPerfValidIntervals 1137 MAX-ACCESS read-only 1138 STATUS current 1139 DESCRIPTION 1140 "Valid Intervals per definition found in 1141 HC-PerfHist-TC-MIB." 1142 ::= { vdslPerfDataEntry 1 } 1144 vdslPerfInvalidIntervals OBJECT-TYPE 1145 SYNTAX HCPerfInvalidIntervals 1146 MAX-ACCESS read-only 1147 STATUS current 1148 DESCRIPTION 1149 "Invalid Intervals per definition found in 1150 HC-PerfHist-TC-MIB." 1151 ::= { vdslPerfDataEntry 2 } 1153 vdslPerfLofs OBJECT-TYPE 1154 SYNTAX Counter64 1155 UNITS "seconds" 1156 MAX-ACCESS read-only 1157 STATUS current 1158 DESCRIPTION 1159 "Count of seconds since the unit was last reset that there 1160 was Loss of Framing." 1161 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1162 ::= { vdslPerfDataEntry 3 } 1164 vdslPerfLoss OBJECT-TYPE 1165 SYNTAX Counter64 1166 UNITS "seconds" 1167 MAX-ACCESS read-only 1168 STATUS current 1169 DESCRIPTION 1170 "Count of seconds since the unit was last reset that there 1171 was Loss of Signal." 1172 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1173 ::= { vdslPerfDataEntry 4 } 1175 vdslPerfLprs OBJECT-TYPE 1176 SYNTAX Counter64 1177 UNITS "seconds" 1178 MAX-ACCESS read-only 1179 STATUS current 1180 DESCRIPTION 1181 "Count of seconds since the unit was last reset that there 1182 was Loss of Power." 1183 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1184 ::= { vdslPerfDataEntry 5 } 1186 vdslPerfESs OBJECT-TYPE 1187 SYNTAX Counter64 1188 UNITS "seconds" 1189 MAX-ACCESS read-only 1190 STATUS current 1191 DESCRIPTION 1192 "Count of Errored Seconds since the unit was last reset. 1193 An Errored Second is a one-second interval containing one 1194 or more crc anomalies, or one or more los or lof defects." 1195 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1196 ::= { vdslPerfDataEntry 6 } 1198 vdslPerfSESs OBJECT-TYPE 1199 SYNTAX Counter64 1200 UNITS "seconds" 1201 MAX-ACCESS read-only 1202 STATUS current 1203 DESCRIPTION 1204 "Count of Severely Errored Seconds since the unit was last 1205 reset." 1206 ::= { vdslPerfDataEntry 7 } 1208 vdslPerfUASs OBJECT-TYPE 1209 SYNTAX Counter64 1210 UNITS "seconds" 1211 MAX-ACCESS read-only 1212 STATUS current 1213 DESCRIPTION 1214 "Count of Unavailable Seconds since the unit was last 1215 reset." 1216 ::= { vdslPerfDataEntry 8 } 1218 vdslPerfInits OBJECT-TYPE 1219 SYNTAX Counter64 1220 MAX-ACCESS read-only 1221 STATUS current 1222 DESCRIPTION 1223 "Count of the line initialization attempts since the unit 1224 was last reset. This count includes both successful and 1225 failed attempts." 1226 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1227 ::= { vdslPerfDataEntry 9 } 1229 vdslPerfCurr15MinTimeElapsed OBJECT-TYPE 1230 SYNTAX HCPerfTimeElapsed 1231 UNITS "seconds" 1232 MAX-ACCESS read-only 1233 STATUS current 1234 DESCRIPTION 1235 "Total elapsed seconds in this interval." 1236 ::= { vdslPerfDataEntry 10 } 1238 vdslPerfCurr15MinLofs OBJECT-TYPE 1239 SYNTAX HCPerfCurrentCount 1240 UNITS "seconds" 1241 MAX-ACCESS read-only 1242 STATUS current 1243 DESCRIPTION 1244 "Count of seconds during this interval that there 1245 was Loss of Framing." 1246 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1247 ::= { vdslPerfDataEntry 11 } 1249 vdslPerfCurr15MinLoss OBJECT-TYPE 1250 SYNTAX HCPerfCurrentCount 1251 UNITS "seconds" 1252 MAX-ACCESS read-only 1253 STATUS current 1254 DESCRIPTION 1255 "Count of seconds during this interval that there 1256 was Loss of Signal." 1257 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1258 ::= { vdslPerfDataEntry 12 } 1260 vdslPerfCurr15MinLprs OBJECT-TYPE 1261 SYNTAX HCPerfCurrentCount 1262 UNITS "seconds" 1263 MAX-ACCESS read-only 1264 STATUS current 1265 DESCRIPTION 1266 "Count of seconds during this interval that there 1267 was Loss of Power." 1268 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1269 ::= { vdslPerfDataEntry 13 } 1271 vdslPerfCurr15MinESs OBJECT-TYPE 1272 SYNTAX HCPerfCurrentCount 1273 UNITS "seconds" 1274 MAX-ACCESS read-only 1275 STATUS current 1276 DESCRIPTION 1277 "Count of Errored Seconds during this interval. An Errored 1278 Second is a one-second interval containing one or more crc 1279 anomalies, or one or more los or lof defects." 1280 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1281 ::= { vdslPerfDataEntry 14 } 1283 vdslPerfCurr15MinSESs OBJECT-TYPE 1284 SYNTAX HCPerfCurrentCount 1285 UNITS "seconds" 1286 MAX-ACCESS read-only 1287 STATUS current 1288 DESCRIPTION 1289 "Count of Severely Errored Seconds during this interval." 1290 ::= { vdslPerfDataEntry 15 } 1292 vdslPerfCurr15MinUASs OBJECT-TYPE 1293 SYNTAX HCPerfCurrentCount 1294 UNITS "seconds" 1295 MAX-ACCESS read-only 1296 STATUS current 1297 DESCRIPTION 1298 "Count of Unavailable Seconds during this interval." 1299 ::= { vdslPerfDataEntry 16 } 1301 vdslPerfCurr15MinInits OBJECT-TYPE 1302 SYNTAX HCPerfCurrentCount 1303 MAX-ACCESS read-only 1304 STATUS current 1305 DESCRIPTION 1306 "Count of the line initialization attempts during this 1307 interval. This count includes both successful and 1308 failed attempts." 1309 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1310 ::= { vdslPerfDataEntry 17 } 1312 vdslPerf1DayValidIntervals OBJECT-TYPE 1313 SYNTAX HCPerfValidIntervals 1314 MAX-ACCESS read-only 1315 STATUS current 1316 DESCRIPTION 1317 "Valid Intervals per definition found in 1318 HC-PerfHist-TC-MIB." 1319 ::= { vdslPerfDataEntry 18 } 1321 vdslPerf1DayInvalidIntervals OBJECT-TYPE 1322 SYNTAX HCPerfInvalidIntervals 1323 MAX-ACCESS read-only 1324 STATUS current 1325 DESCRIPTION 1326 "Invalid Intervals per definition found in 1327 HC-PerfHist-TC-MIB." 1328 ::= { vdslPerfDataEntry 19 } 1330 vdslPerfCurr1DayTimeElapsed OBJECT-TYPE 1331 SYNTAX HCPerfTimeElapsed 1332 UNITS "seconds" 1333 MAX-ACCESS read-only 1334 STATUS current 1335 DESCRIPTION 1336 "Number of seconds that have elapsed since the beginning 1337 of the current 1-day interval." 1338 ::= { vdslPerfDataEntry 20 } 1340 vdslPerfCurr1DayLofs OBJECT-TYPE 1341 SYNTAX Counter64 1342 UNITS "seconds" 1343 MAX-ACCESS read-only 1344 STATUS current 1345 DESCRIPTION 1346 "Count of Loss of Framing (LOF) Seconds since the 1347 beginning of the current 1-day interval." 1348 ::= { vdslPerfDataEntry 21 } 1350 vdslPerfCurr1DayLoss OBJECT-TYPE 1351 SYNTAX Counter64 1352 UNITS "seconds" 1353 MAX-ACCESS read-only 1354 STATUS current 1355 DESCRIPTION 1356 "Count of Loss of Signal (LOS) Seconds since the beginning 1357 of the current 1-day interval." 1358 ::= { vdslPerfDataEntry 22 } 1360 vdslPerfCurr1DayLprs OBJECT-TYPE 1361 SYNTAX Counter64 1362 UNITS "seconds" 1363 MAX-ACCESS read-only 1364 STATUS current 1365 DESCRIPTION 1366 "Count of Loss of Power (LPR) Seconds since the beginning 1367 of the current 1-day interval." 1368 ::= { vdslPerfDataEntry 23 } 1370 vdslPerfCurr1DayESs OBJECT-TYPE 1371 SYNTAX Counter64 1372 UNITS "seconds" 1373 MAX-ACCESS read-only 1374 STATUS current 1375 DESCRIPTION 1376 "Count of Errored Seconds (ES) since the beginning 1377 of the current 1-day interval." 1378 ::= { vdslPerfDataEntry 24 } 1380 vdslPerfCurr1DaySESs OBJECT-TYPE 1381 SYNTAX Counter64 1382 UNITS "seconds" 1383 MAX-ACCESS read-only 1384 STATUS current 1385 DESCRIPTION 1386 "Count of Severely Errored Seconds (SES) since the 1387 beginning of the current 1-day interval." 1388 ::= { vdslPerfDataEntry 25 } 1390 vdslPerfCurr1DayUASs OBJECT-TYPE 1391 SYNTAX Counter64 1392 UNITS "seconds" 1393 MAX-ACCESS read-only 1394 STATUS current 1395 DESCRIPTION 1396 "Count of Unavailable Seconds (UAS) since the beginning 1397 of the current 1-day interval." 1398 ::= { vdslPerfDataEntry 26 } 1400 vdslPerfCurr1DayInits OBJECT-TYPE 1401 SYNTAX Counter64 1402 UNITS "seconds" 1403 MAX-ACCESS read-only 1404 STATUS current 1405 DESCRIPTION 1406 "Count of the line initialization attempts since the 1407 beginning of the current 1-day interval. This count 1408 includes both successful and failed attempts." 1409 ::= { vdslPerfDataEntry 27 } 1411 vdslPerfIntervalTable OBJECT-TYPE 1412 SYNTAX SEQUENCE OF VdslPerfIntervalEntry 1413 MAX-ACCESS not-accessible 1414 STATUS current 1415 DESCRIPTION 1416 "This table provides one row for each Vtu performance 1417 data collection interval. VDSL physical interfaces are 1418 those ifEntries where ifType is equal to vdsl(97)." 1419 ::= { vdslMibObjects 5 } 1421 vdslPerfIntervalEntry OBJECT-TYPE 1422 SYNTAX VdslPerfIntervalEntry 1423 MAX-ACCESS not-accessible 1424 STATUS current 1425 DESCRIPTION 1426 "An entry in the vdslPerfIntervalTable." 1427 INDEX { ifIndex, 1428 vdslPhysSide, 1429 vdslIntervalNumber } 1430 ::= { vdslPerfIntervalTable 1 } 1432 VdslPerfIntervalEntry ::= 1433 SEQUENCE 1434 { 1435 vdslIntervalNumber Unsigned32, 1436 vdslIntervalLofs HCPerfIntervalCount, 1437 vdslIntervalLoss HCPerfIntervalCount, 1438 vdslIntervalLprs HCPerfIntervalCount, 1439 vdslIntervalESs HCPerfIntervalCount, 1440 vdslIntervalSESs HCPerfIntervalCount, 1441 vdslIntervalUASs HCPerfIntervalCount, 1442 vdslIntervalInits HCPerfIntervalCount 1443 } 1445 vdslIntervalNumber OBJECT-TYPE 1446 SYNTAX Unsigned32 (1..96) 1447 MAX-ACCESS not-accessible 1448 STATUS current 1449 DESCRIPTION 1450 "Performance Data Interval number 1 is the the most 1451 recent previous interval; interval 96 is 24 hours ago. 1452 Intervals 2..96 are optional." 1453 ::= { vdslPerfIntervalEntry 1 } 1455 vdslIntervalLofs OBJECT-TYPE 1456 SYNTAX HCPerfIntervalCount 1457 UNITS "seconds" 1458 MAX-ACCESS read-only 1459 STATUS current 1460 DESCRIPTION 1461 "Count of seconds in the interval when there was Loss 1462 of Framing." 1463 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1464 ::= { vdslPerfIntervalEntry 2 } 1466 vdslIntervalLoss OBJECT-TYPE 1467 SYNTAX HCPerfIntervalCount 1468 UNITS "seconds" 1469 MAX-ACCESS read-only 1470 STATUS current 1471 DESCRIPTION 1472 "Count of seconds in the interval when there was Loss 1473 of Signal." 1474 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1475 ::= { vdslPerfIntervalEntry 3 } 1477 vdslIntervalLprs OBJECT-TYPE 1478 SYNTAX HCPerfIntervalCount 1479 UNITS "seconds" 1480 MAX-ACCESS read-only 1481 STATUS current 1482 DESCRIPTION 1483 "Count of seconds in the interval when there was Loss 1484 of Power." 1485 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1486 ::= { vdslPerfIntervalEntry 4 } 1488 vdslIntervalESs OBJECT-TYPE 1489 SYNTAX HCPerfIntervalCount 1490 UNITS "seconds" 1491 MAX-ACCESS read-only 1492 STATUS current 1493 DESCRIPTION 1494 "Count of Errored Seconds (ES) in the interval. An Errored 1495 Second is a one-second interval containing one or more crc 1496 anomalies, one or more los or lof defects." 1497 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1498 ::= { vdslPerfIntervalEntry 5 } 1500 vdslIntervalSESs OBJECT-TYPE 1501 SYNTAX HCPerfIntervalCount 1502 UNITS "seconds" 1503 MAX-ACCESS read-only 1504 STATUS current 1505 DESCRIPTION 1506 "Count of Severely Errored Seconds in the interval." 1507 ::= { vdslPerfIntervalEntry 6 } 1509 vdslIntervalUASs OBJECT-TYPE 1510 SYNTAX HCPerfIntervalCount 1511 UNITS "seconds" 1512 MAX-ACCESS read-only 1513 STATUS current 1514 DESCRIPTION 1515 "Count of Unavailable Seconds in the interval." 1516 ::= { vdslPerfIntervalEntry 7 } 1518 vdslIntervalInits OBJECT-TYPE 1519 SYNTAX HCPerfIntervalCount 1520 MAX-ACCESS read-only 1521 STATUS current 1522 DESCRIPTION 1523 "Count of the line initialization attempts during this 1524 interval. This count includes both successful and 1525 failed attempts." 1526 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1527 ::= { vdslPerfIntervalEntry 8 } 1529 vdsl1DayIntervalTable OBJECT-TYPE 1530 SYNTAX SEQUENCE OF Vdsl1DayIntervalEntry 1531 MAX-ACCESS not-accessible 1532 STATUS current 1533 DESCRIPTION 1534 "This table provides one row for each VDSL performance 1535 data collection interval. This table contains live data 1536 from equipment. As such, it is NOT persistent." 1537 ::= { vdslMibObjects 6 } 1539 vdsl1DayIntervalEntry OBJECT-TYPE 1540 SYNTAX Vdsl1DayIntervalEntry 1541 MAX-ACCESS not-accessible 1542 STATUS current 1543 DESCRIPTION 1544 "An entry in the vdsl1DayIntervalTable." 1545 INDEX { ifIndex, 1546 vdslPhysSide, 1547 vdsl1DayIntervalNumber } 1548 ::= { vdsl1DayIntervalTable 1 } 1550 Vdsl1DayIntervalEntry ::= 1551 SEQUENCE 1552 { 1553 vdsl1DayIntervalNumber Unsigned32, 1554 vdsl1DayIntervalMoniSecs HCPerfTimeElapsed, 1555 vdsl1DayIntervalLofs Counter64, 1556 vdsl1DayIntervalLoss Counter64, 1557 vdsl1DayIntervalLprs Counter64, 1558 vdsl1DayIntervalESs Counter64, 1559 vdsl1DayIntervalSESs Counter64, 1560 vdsl1DayIntervalUASs Counter64, 1561 vdsl1DayIntervalInits Counter64 1562 } 1564 vdsl1DayIntervalNumber OBJECT-TYPE 1565 SYNTAX Unsigned32 (1..30) 1566 MAX-ACCESS not-accessible 1567 STATUS current 1568 DESCRIPTION 1569 "History Data Interval number. Interval 1 is the the most 1570 recent previous day; interval 30 is 30 days ago. Intervals 1571 2..30 are optional." 1572 ::= { vdsl1DayIntervalEntry 1 } 1574 vdsl1DayIntervalMoniSecs OBJECT-TYPE 1575 SYNTAX HCPerfTimeElapsed 1576 UNITS "seconds" 1577 MAX-ACCESS read-only 1578 STATUS current 1579 DESCRIPTION 1580 "The amount of time in the 1-day interval over which the 1581 performance monitoring information is actually counted. 1582 This value will be the same as the interval duration except 1583 in a situation where performance monitoring data could not 1584 be collected for any reason." 1585 ::= { vdsl1DayIntervalEntry 2 } 1587 vdsl1DayIntervalLofs OBJECT-TYPE 1588 SYNTAX Counter64 1589 UNITS "seconds" 1590 MAX-ACCESS read-only 1591 STATUS current 1592 DESCRIPTION 1593 "Count of Loss of Frame (LOF) Seconds during the 1-day 1594 interval as measured by vdsl1DayIntervalMoniSecs." 1595 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1596 ::= { vdsl1DayIntervalEntry 3 } 1598 vdsl1DayIntervalLoss OBJECT-TYPE 1599 SYNTAX Counter64 1600 UNITS "seconds" 1601 MAX-ACCESS read-only 1602 STATUS current 1603 DESCRIPTION 1604 "Count of Loss of Signal (LOS) Seconds during the 1-day 1605 interval as measured by vdsl1DayIntervalMoniSecs." 1606 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1607 ::= { vdsl1DayIntervalEntry 4 } 1609 vdsl1DayIntervalLprs OBJECT-TYPE 1610 SYNTAX Counter64 1611 UNITS "seconds" 1612 MAX-ACCESS read-only 1613 STATUS current 1614 DESCRIPTION 1615 "Count of Loss of Power (LPR) Seconds during the 1-day 1616 interval as measured by vdsl1DayIntervalMoniSecs." 1617 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1618 ::= { vdsl1DayIntervalEntry 5 } 1620 vdsl1DayIntervalESs OBJECT-TYPE 1621 SYNTAX Counter64 1622 UNITS "seconds" 1623 MAX-ACCESS read-only 1624 STATUS current 1625 DESCRIPTION 1626 "Count of Errored Seconds (ES) during the 1-day 1627 interval as measured by vdsl1DayIntervalMoniSecs." 1628 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1629 ::= { vdsl1DayIntervalEntry 6 } 1631 vdsl1DayIntervalSESs OBJECT-TYPE 1632 SYNTAX Counter64 1633 UNITS "seconds" 1634 MAX-ACCESS read-only 1635 STATUS current 1636 DESCRIPTION 1637 "Count of Severely Errored Seconds (SES) during the 1-day 1638 interval as measured by vdsl1DayIntervalMoniSecs." 1639 ::= { vdsl1DayIntervalEntry 7 } 1641 vdsl1DayIntervalUASs OBJECT-TYPE 1642 SYNTAX Counter64 1643 UNITS "seconds" 1644 MAX-ACCESS read-only 1645 STATUS current 1646 DESCRIPTION 1647 "Count of Unavailable Seconds (UAS) during the 1-day 1648 interval as measured by vdsl1DayIntervalMoniSecs." 1649 ::= { vdsl1DayIntervalEntry 8 } 1651 vdsl1DayIntervalInits OBJECT-TYPE 1652 SYNTAX Counter64 1653 UNITS "seconds" 1654 MAX-ACCESS read-only 1655 STATUS current 1656 DESCRIPTION 1657 "Count of the line initialization attempts during the 1658 1-day interval as measured by vdsl1DayIntervalMoniSecs. 1659 This count includes both successful and failed attempts." 1660 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1661 ::= { vdsl1DayIntervalEntry 9 } 1663 vdslChanPerfDataTable OBJECT-TYPE 1664 SYNTAX SEQUENCE OF VdslChanPerfDataEntry 1665 MAX-ACCESS not-accessible 1666 STATUS current 1667 DESCRIPTION 1668 "This table provides one row for each Vtu channel. 1669 VDSL channel interfaces are those ifEntries where 1670 ifType is equal to interleave(124) or fast(125)." 1671 ::= { vdslMibObjects 7 } 1673 vdslChanPerfDataEntry OBJECT-TYPE 1674 SYNTAX VdslChanPerfDataEntry 1675 MAX-ACCESS not-accessible 1676 STATUS current 1677 DESCRIPTION 1678 "An entry in the vdslChanPerfDataTable." 1679 INDEX { ifIndex, 1680 vdslPhysSide } 1681 ::= { vdslChanPerfDataTable 1 } 1683 VdslChanPerfDataEntry ::= 1684 SEQUENCE 1685 { 1686 vdslChanPerfValidIntervals HCPerfValidIntervals, 1687 vdslChanPerfInvalidIntervals HCPerfInvalidIntervals, 1688 vdslChanCorrectedOctets Counter64, 1689 vdslChanUncorrectBlks Counter64, 1690 vdslChanPerfCurr15MinTimeElapsed HCPerfTimeElapsed, 1691 vdslChanPerfCurr15MinCorrectedOctets HCPerfCurrentCount, 1692 vdslChanPerfCurr15MinUncorrectBlks HCPerfCurrentCount, 1693 vdslChanPerf1DayValidIntervals HCPerfValidIntervals, 1694 vdslChanPerf1DayInvalidIntervals HCPerfInvalidIntervals, 1695 vdslChanPerfCurr1DayTimeElapsed HCPerfTimeElapsed, 1696 vdslChanPerfCurr1DayCorrectedOctets HCPerfCurrentCount, 1697 vdslChanPerfCurr1DayUncorrectBlks HCPerfCurrentCount 1698 } 1700 vdslChanPerfValidIntervals OBJECT-TYPE 1701 SYNTAX HCPerfValidIntervals 1702 MAX-ACCESS read-only 1703 STATUS current 1704 DESCRIPTION 1705 "Valid Intervals per definition found in 1706 HC-PerfHist-TC-MIB." 1707 ::= { vdslChanPerfDataEntry 1 } 1709 vdslChanPerfInvalidIntervals OBJECT-TYPE 1710 SYNTAX HCPerfInvalidIntervals 1711 MAX-ACCESS read-only 1712 STATUS current 1713 DESCRIPTION 1714 "Invalid Intervals per definition found in 1715 HC-PerfHist-TC-MIB." 1716 ::= { vdslChanPerfDataEntry 2 } 1718 vdslChanCorrectedOctets OBJECT-TYPE 1719 SYNTAX Counter64 1720 MAX-ACCESS read-only 1721 STATUS current 1722 DESCRIPTION 1723 "Count of corrected octets since the unit was last reset." 1724 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1725 ::= { vdslChanPerfDataEntry 3 } 1727 vdslChanUncorrectBlks OBJECT-TYPE 1728 SYNTAX Counter64 1729 MAX-ACCESS read-only 1730 STATUS current 1731 DESCRIPTION 1732 "Count of uncorrected blocks since the unit was last reset." 1733 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1734 ::= { vdslChanPerfDataEntry 4 } 1736 vdslChanPerfCurr15MinTimeElapsed OBJECT-TYPE 1737 SYNTAX HCPerfTimeElapsed 1738 UNITS "seconds" 1739 MAX-ACCESS read-only 1740 STATUS current 1741 DESCRIPTION 1742 "Total elapsed seconds in this interval." 1743 ::= { vdslChanPerfDataEntry 5 } 1745 vdslChanPerfCurr15MinCorrectedOctets OBJECT-TYPE 1746 SYNTAX HCPerfCurrentCount 1747 MAX-ACCESS read-only 1748 STATUS current 1749 DESCRIPTION 1750 "Count of corrected octets in this interval." 1751 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1752 ::= { vdslChanPerfDataEntry 6 } 1754 vdslChanPerfCurr15MinUncorrectBlks OBJECT-TYPE 1755 SYNTAX HCPerfCurrentCount 1756 MAX-ACCESS read-only 1757 STATUS current 1758 DESCRIPTION 1759 "Count of uncorrected blocks in this interval." 1760 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1761 ::= { vdslChanPerfDataEntry 7 } 1763 vdslChanPerf1DayValidIntervals OBJECT-TYPE 1764 SYNTAX HCPerfValidIntervals 1765 MAX-ACCESS read-only 1766 STATUS current 1767 DESCRIPTION 1768 "Valid Intervals per definition found in 1769 HC-PerfHist-TC-MIB." 1770 ::= { vdslChanPerfDataEntry 8 } 1772 vdslChanPerf1DayInvalidIntervals OBJECT-TYPE 1773 SYNTAX HCPerfInvalidIntervals 1774 MAX-ACCESS read-only 1775 STATUS current 1776 DESCRIPTION 1777 "Invalid Intervals per definition found in 1778 HC-PerfHist-TC-MIB." 1779 ::= { vdslChanPerfDataEntry 9 } 1781 vdslChanPerfCurr1DayTimeElapsed OBJECT-TYPE 1782 SYNTAX HCPerfTimeElapsed 1783 UNITS "seconds" 1784 MAX-ACCESS read-only 1785 STATUS current 1786 DESCRIPTION 1787 "Number of seconds that have elapsed since the beginning 1788 of the current 1-day interval." 1789 ::= { vdslChanPerfDataEntry 10 } 1791 vdslChanPerfCurr1DayCorrectedOctets OBJECT-TYPE 1792 SYNTAX HCPerfCurrentCount 1793 MAX-ACCESS read-only 1794 STATUS current 1795 DESCRIPTION 1796 "Count of corrected octets since the beginning of the 1797 current 1-day interva." 1798 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1799 ::= { vdslChanPerfDataEntry 11 } 1801 vdslChanPerfCurr1DayUncorrectBlks OBJECT-TYPE 1802 SYNTAX HCPerfCurrentCount 1803 MAX-ACCESS read-only 1804 STATUS current 1805 DESCRIPTION 1806 "Count of uncorrected blocks since the beginning of the 1807 current 1-day interva." 1808 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1809 ::= { vdslChanPerfDataEntry 12 } 1811 vdslChanIntervalTable OBJECT-TYPE 1812 SYNTAX SEQUENCE OF VdslChanIntervalEntry 1813 MAX-ACCESS not-accessible 1814 STATUS current 1815 DESCRIPTION 1816 "This table provides one row for each Vtu channel data 1817 collection interval. VDSL channel interfaces are those 1818 ifEntries where ifType is equal to interleave(124) or 1819 fast(125)." 1820 ::= { vdslMibObjects 8 } 1822 vdslChanIntervalEntry OBJECT-TYPE 1823 SYNTAX VdslChanIntervalEntry 1824 MAX-ACCESS not-accessible 1825 STATUS current 1826 DESCRIPTION 1827 "An entry in the vdslChanIntervalTable." 1828 INDEX { ifIndex, 1829 vdslPhysSide, 1830 vdslChanIntervalNumber } 1831 ::= { vdslChanIntervalTable 1 } 1833 VdslChanIntervalEntry ::= 1834 SEQUENCE 1835 { 1836 vdslChanIntervalNumber Unsigned32, 1837 vdslChanIntervalCorrectedOctets HCPerfIntervalCount, 1838 vdslChanIntervalUncorrectBlks HCPerfIntervalCount 1839 } 1841 vdslChanIntervalNumber OBJECT-TYPE 1842 SYNTAX Unsigned32 (0..96) 1843 MAX-ACCESS not-accessible 1844 STATUS current 1845 DESCRIPTION 1846 "Performance Data Interval number 1 is the the most 1847 recent previous interval; interval 96 is 24 hours ago. 1848 Intervals 2..96 are optional." 1849 ::= { vdslChanIntervalEntry 1 } 1851 vdslChanIntervalCorrectedOctets OBJECT-TYPE 1852 SYNTAX HCPerfIntervalCount 1853 MAX-ACCESS read-only 1854 STATUS current 1855 DESCRIPTION 1856 "Count of corrected octets in this interval." 1857 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1858 ::= { vdslChanIntervalEntry 2 } 1860 vdslChanIntervalUncorrectBlks OBJECT-TYPE 1861 SYNTAX HCPerfIntervalCount 1862 MAX-ACCESS read-only 1863 STATUS current 1864 DESCRIPTION 1865 "Count of uncorrected blocks in this interval." 1866 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1867 ::= { vdslChanIntervalEntry 3 } 1869 vdslChan1DayIntervalTable OBJECT-TYPE 1870 SYNTAX SEQUENCE OF VdslChan1DayIntervalEntry 1871 MAX-ACCESS not-accessible 1872 STATUS current 1873 DESCRIPTION 1874 "This table provides one row for each VDSL performance 1875 data collection interval. This table contains live data 1876 from equipment. As such, it is NOT persistent." 1877 ::= { vdslMibObjects 9 } 1879 vdslChan1DayIntervalEntry OBJECT-TYPE 1880 SYNTAX VdslChan1DayIntervalEntry 1881 MAX-ACCESS not-accessible 1882 STATUS current 1883 DESCRIPTION 1884 "An entry in the vdslChan1DayIntervalTable." 1885 INDEX { ifIndex, 1886 vdslPhysSide, 1887 vdslChan1DayIntervalNumber } 1888 ::= { vdslChan1DayIntervalTable 1 } 1890 VdslChan1DayIntervalEntry ::= 1891 SEQUENCE 1892 { 1893 vdslChan1DayIntervalNumber Unsigned32, 1894 vdslChan1DayIntervalMoniSecs HCPerfTimeElapsed, 1895 vdslChan1DayIntervalCorrectedOctets HCPerfCurrentCount, 1896 vdslChan1DayIntervalUncorrectBlks HCPerfCurrentCount 1897 } 1899 vdslChan1DayIntervalNumber OBJECT-TYPE 1900 SYNTAX Unsigned32 (1..30) 1901 MAX-ACCESS not-accessible 1902 STATUS current 1903 DESCRIPTION 1904 "History Data Interval number. Interval 1 is the the most 1905 recent previous day; interval 30 is 30 days ago. Intervals 1906 2..30 are optional." 1907 ::= { vdslChan1DayIntervalEntry 1 } 1909 vdslChan1DayIntervalMoniSecs OBJECT-TYPE 1910 SYNTAX HCPerfTimeElapsed 1911 UNITS "seconds" 1912 MAX-ACCESS read-only 1913 STATUS current 1914 DESCRIPTION 1915 "The amount of time in the 1-day interval over which the 1916 performance monitoring information is actually counted. 1917 This value will be the same as the interval duration except 1918 in a situation where performance monitoring data could not 1919 be collected for any reason." 1920 ::= { vdslChan1DayIntervalEntry 2 } 1922 vdslChan1DayIntervalCorrectedOctets OBJECT-TYPE 1923 SYNTAX HCPerfCurrentCount 1924 MAX-ACCESS read-only 1925 STATUS current 1926 DESCRIPTION 1927 "Count of corrected octets in this interval." 1928 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1929 ::= { vdslChan1DayIntervalEntry 3 } 1931 vdslChan1DayIntervalUncorrectBlks OBJECT-TYPE 1932 SYNTAX HCPerfCurrentCount 1933 MAX-ACCESS read-only 1934 STATUS current 1935 DESCRIPTION 1936 "Count of uncorrected blocks in this interval." 1937 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1938 ::= { vdslChan1DayIntervalEntry 4 } 1940 -- 1941 -- SCM physical band status 1942 -- 1944 vdslSCMPhysBandTable OBJECT-TYPE 1945 SYNTAX SEQUENCE OF VdslSCMPhysBandEntry 1946 MAX-ACCESS not-accessible 1947 STATUS current 1948 DESCRIPTION 1949 "This table provides one row for each SCM Vtu band." 1950 ::= { vdslMibObjects 10 } 1952 vdslSCMPhysBandEntry OBJECT-TYPE 1953 SYNTAX VdslSCMPhysBandEntry 1954 MAX-ACCESS not-accessible 1955 STATUS current 1956 DESCRIPTION 1957 "An entry in the vdslSCMPhysBandTable." 1958 INDEX { ifIndex, 1959 vdslPhysSide, 1960 vdslSCMPhysTxBandNumber } 1961 ::= { vdslSCMPhysBandTable 1 } 1963 VdslSCMPhysBandEntry ::= 1964 SEQUENCE 1965 { 1966 vdslSCMPhysTxBandNumber INTEGER, 1967 vdslSCMPhysBandSnrMgn Integer32, 1968 vdslSCMPhysBandAtn Unsigned32 1969 } 1971 vdslSCMPhysTxBandNumber OBJECT-TYPE 1972 SYNTAX INTEGER 1973 { 1974 band1(1), 1975 band2(2), 1976 upstreamU0(3) 1977 } 1978 MAX-ACCESS not-accessible 1979 STATUS current 1980 DESCRIPTION 1981 "The SCM transmit band number for this entry." 1982 ::= { vdslSCMPhysBandEntry 1 } 1984 vdslSCMPhysBandSnrMgn OBJECT-TYPE 1985 SYNTAX Integer32 (-127..127) 1986 UNITS "0.25 dBm" 1987 MAX-ACCESS read-only 1988 STATUS current 1989 DESCRIPTION 1990 "Noise margin as seen by this Vtu and band with respect 1991 to its received signal in 0.25 dB." 1992 ::= { vdslSCMPhysBandEntry 2 } 1994 vdslSCMPhysBandAtn OBJECT-TYPE 1995 SYNTAX Unsigned32 (0..255) 1996 UNITS "0.25 dBm" 1997 MAX-ACCESS read-only 1998 STATUS current 1999 DESCRIPTION 2000 "Measured difference in the total power transmitted by 2001 the peer Vtu on this band and the total power received 2002 by this Vtu on this band in 0.25 dB." 2003 ::= { vdslSCMPhysBandEntry 3 } 2005 -- 2006 -- profile tables 2007 -- 2009 vdslLineConfProfileTable OBJECT-TYPE 2010 SYNTAX SEQUENCE OF VdslLineConfProfileEntry 2011 MAX-ACCESS not-accessible 2012 STATUS current 2013 DESCRIPTION 2014 "This table contains information on the VDSL line 2015 configuration. One entry in this table reflects a 2016 profile defined by a manager which can be used to 2017 configure the VDSL line." 2018 ::= { vdslMibObjects 11 } 2020 vdslLineConfProfileEntry OBJECT-TYPE 2021 SYNTAX VdslLineConfProfileEntry 2022 MAX-ACCESS not-accessible 2023 STATUS current 2024 DESCRIPTION 2025 "Each entry consists of a list of parameters that 2026 represents the configuration of a VDSL line. A 2027 default profile with an index of 1 will always exist 2028 and its parameters will be set to vendor specific 2029 values, unless otherwise specified in this document." 2030 INDEX { vdslLineConfProfileIndex } 2031 ::= { vdslLineConfProfileTable 1 } 2033 VdslLineConfProfileEntry ::= 2034 SEQUENCE 2035 { 2036 vdslLineConfProfileIndex Unsigned32, 2037 vdslLineConfProfileName SnmpAdminString, 2038 vdslLineConfDownstreamMaxPwr Unsigned32, 2039 vdslLineConfUpstreamMaxPwr Unsigned32, 2040 vdslLineConfDownstreamMaxSnrMgn Unsigned32, 2041 vdslLineConfDownstreamMinSnrMgn Unsigned32, 2042 vdslLineConfDownstreamTargetSnrMgn Unsigned32, 2043 vdslLineConfUpstreamMaxSnrMgn Unsigned32, 2044 vdslLineConfUpstreamMinSnrMgn Unsigned32, 2045 vdslLineConfUpstreamTargetSnrMgn Unsigned32, 2046 vdslLineConfDownstreamFastMaxDataRate Unsigned32, 2047 vdslLineConfDownstreamFastMinDataRate Unsigned32, 2048 vdslLineConfDownstreamSlowMaxDataRate Unsigned32, 2049 vdslLineConfDownstreamSlowMinDataRate Unsigned32, 2050 vdslLineConfUpstreamFastMaxDataRate Unsigned32, 2051 vdslLineConfUpstreamFastMinDataRate Unsigned32, 2052 vdslLineConfUpstreamSlowMaxDataRate Unsigned32, 2053 vdslLineConfUpstreamSlowMinDataRate Unsigned32, 2054 vdslLineConfRateAdaptationRatio Unsigned32, 2055 vdslLineConfUpstreamDataRate Unsigned32, 2056 vdslLineConfDownstreamDataRate Unsigned32, 2057 vdslLineConfDownstreamMaxInterDelay Unsigned32, 2058 vdslLineConfUpstreamMaxInterDelay Unsigned32, 2059 vdslLineConfUpstreamPboControl INTEGER, 2060 vdslLineConfDownstreamPboControl INTEGER, 2061 vdslLineConfDeploymentScenario INTEGER, 2062 vdslLineConfAdslOccupy TruthValue, 2063 vdslLineConfApplicableStandard INTEGER, 2064 vdslLineConfBandPlan INTEGER, 2065 vdslLineConfBandPlanFx Unsigned32, 2066 vdslLineConfBandU0Usage INTEGER, 2067 vdslLineConfUpstreamPsdTemplate INTEGER, 2068 vdslLineConfDownstreamPsdTemplate INTEGER, 2069 vdslLineConfProfileRowStatus RowStatus 2070 } 2072 vdslLineConfProfileIndex OBJECT-TYPE 2073 SYNTAX Unsigned32 2074 MAX-ACCESS read-create 2075 STATUS current 2076 DESCRIPTION 2077 "This object identifies a row in this table. A 2078 default profile with an index of 1 MUST always 2079 exist and its parameters will be set to vendor 2080 specific values, unless otherwise specified in 2081 this document." 2082 ::= { vdslLineConfProfileEntry 1 } 2084 vdslLineConfProfileName OBJECT-TYPE 2085 SYNTAX SnmpAdminString (SIZE (1..32)) 2086 MAX-ACCESS read-create 2087 STATUS current 2088 DESCRIPTION 2089 "The name for this profile as specified by a user." 2090 ::= { vdslLineConfProfileEntry 2 } 2092 vdslLineConfDownstreamMaxPwr OBJECT-TYPE 2093 SYNTAX Unsigned32 (0..58) 2094 UNITS "0.25dBm" 2095 MAX-ACCESS read-create 2096 STATUS current 2097 DESCRIPTION 2098 "Specifies the maximum aggregate downstream power 2099 level in the range 0..14.5dBm." 2100 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 2101 ::= { vdslLineConfProfileEntry 3 } 2103 vdslLineConfUpstreamMaxPwr 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 upstream power 2110 level in the range 0..14.5dBm." 2111 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 2112 ::= { vdslLineConfProfileEntry 4 } 2114 vdslLineConfDownstreamMaxSnrMgn OBJECT-TYPE 2115 SYNTAX Unsigned32 (0..127) 2116 UNITS "0.25dBm" 2117 MAX-ACCESS read-create 2118 STATUS current 2119 DESCRIPTION 2120 "Specifies the maximum downstream Signal/Noise Margin 2121 in units of 0.25 dB, for a range of 0..31.75 dB." 2122 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 2123 ::= { vdslLineConfProfileEntry 5 } 2125 vdslLineConfDownstreamMinSnrMgn OBJECT-TYPE 2126 SYNTAX Unsigned32 (0..127) 2127 UNITS "0.25dBm" 2128 MAX-ACCESS read-create 2129 STATUS current 2130 DESCRIPTION 2131 "Specifies the minimum 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 6 } 2136 vdslLineConfDownstreamTargetSnrMgn OBJECT-TYPE 2137 SYNTAX Unsigned32 (0..127) 2138 UNITS "0.25dBm" 2139 MAX-ACCESS read-create 2140 STATUS current 2141 DESCRIPTION 2142 "Specifies the target downstream Signal/Noise Margin 2143 in units of 0.25 dB, for a range of 0..31.75 dB. 2144 This is the Noise Margin the modems must achieve with a 2145 BER of 10-7 or better to successfully complete 2146 initialization." 2147 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 2148 ::= { vdslLineConfProfileEntry 7 } 2150 vdslLineConfUpstreamMaxSnrMgn OBJECT-TYPE 2151 SYNTAX Unsigned32 (0..127) 2152 UNITS "0.25dBm" 2153 MAX-ACCESS read-create 2154 STATUS current 2155 DESCRIPTION 2156 "Specifies the maximum upstream Signal/Noise Margin 2157 in units of 0.25 dB, for a range of 0..31.75 dB." 2158 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 2159 ::= { vdslLineConfProfileEntry 8 } 2161 vdslLineConfUpstreamMinSnrMgn OBJECT-TYPE 2162 SYNTAX Unsigned32 (0..127) 2163 UNITS "0.25dBm" 2164 MAX-ACCESS read-create 2165 STATUS current 2166 DESCRIPTION 2167 "Specifies the minimum 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 9 } 2172 vdslLineConfUpstreamTargetSnrMgn OBJECT-TYPE 2173 SYNTAX Unsigned32 (0..127) 2174 UNITS "0.25dBm" 2175 MAX-ACCESS read-create 2176 STATUS current 2177 DESCRIPTION 2178 "Specifies the target upstream Signal/Noise Margin in 2179 units of 0.25 dB, for a range of 0..31.75 dB. This 2180 is the Noise Margin the modems must achieve with a BER of 2181 10-7 or better to successfully complete initialization." 2182 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 2183 ::= { vdslLineConfProfileEntry 10 } 2185 vdslLineConfDownstreamFastMaxDataRate OBJECT-TYPE 2186 SYNTAX Unsigned32 2187 UNITS "kbps" 2188 MAX-ACCESS read-create 2189 STATUS current 2190 DESCRIPTION 2191 "Specifies the maximum downstream fast channel 2192 data rate in steps of 1024 bits/second." 2193 ::= { vdslLineConfProfileEntry 11 } 2195 vdslLineConfDownstreamFastMinDataRate OBJECT-TYPE 2196 SYNTAX Unsigned32 2197 UNITS "kbps" 2198 MAX-ACCESS read-create 2199 STATUS current 2200 DESCRIPTION 2201 "Specifies the minimum downstream fast channel 2202 data rate in steps of 1024 bits/second." 2203 ::= { vdslLineConfProfileEntry 12 } 2205 vdslLineConfDownstreamSlowMaxDataRate OBJECT-TYPE 2206 SYNTAX Unsigned32 2207 UNITS "kbps" 2208 MAX-ACCESS read-create 2209 STATUS current 2210 DESCRIPTION 2211 "Specifies the maximum downstream slow channel 2212 data rate in steps of 1024 bits/second." 2213 ::= { vdslLineConfProfileEntry 13 } 2215 vdslLineConfDownstreamSlowMinDataRate OBJECT-TYPE 2216 SYNTAX Unsigned32 2217 UNITS "kbps" 2218 MAX-ACCESS read-create 2219 STATUS current 2220 DESCRIPTION 2221 "Specifies the minimum downstream slow channel 2222 data rate in steps of 1024 bits/second." 2223 ::= { vdslLineConfProfileEntry 14 } 2225 vdslLineConfUpstreamFastMaxDataRate OBJECT-TYPE 2226 SYNTAX Unsigned32 2227 UNITS "kbps" 2228 MAX-ACCESS read-create 2229 STATUS current 2230 DESCRIPTION 2231 "Specifies the maximum upstream fast channel 2232 data rate in steps of 1024 bits/second." 2233 ::= { vdslLineConfProfileEntry 15 } 2235 vdslLineConfUpstreamFastMinDataRate OBJECT-TYPE 2236 SYNTAX Unsigned32 2237 UNITS "kbps" 2238 MAX-ACCESS read-create 2239 STATUS current 2240 DESCRIPTION 2241 "Specifies the minimum upstream fast channel 2242 data rate in steps of 1024 bits/second." 2243 ::= { vdslLineConfProfileEntry 16 } 2245 vdslLineConfUpstreamSlowMaxDataRate OBJECT-TYPE 2246 SYNTAX Unsigned32 2247 UNITS "kbps" 2248 MAX-ACCESS read-create 2249 STATUS current 2250 DESCRIPTION 2251 "Specifies the maximum upstream slow channel 2252 data rate in steps of 1024 bits/second." 2253 ::= { vdslLineConfProfileEntry 17 } 2255 vdslLineConfUpstreamSlowMinDataRate OBJECT-TYPE 2256 SYNTAX Unsigned32 2257 UNITS "kbps" 2258 MAX-ACCESS read-create 2259 STATUS current 2260 DESCRIPTION 2261 "Specifies the minimum upstream slow channel 2262 data rate in steps of 1024 bits/second." 2263 ::= { vdslLineConfProfileEntry 18 } 2265 vdslLineConfRateAdaptationRatio OBJECT-TYPE 2266 SYNTAX Unsigned32 (0..100) 2267 UNITS "percent" 2268 MAX-ACCESS read-create 2269 STATUS current 2270 DESCRIPTION 2271 "For dynamic rate adaptation at startup, the allocation 2272 of data rate in excess of the minimum data rate for each 2273 channel is controlled by the object. This object specifies 2274 the ratio of the allocation of the excess data rate between 2275 the fast and the slow channels. This allocation represents 2276 Fast Channel Allocation / Slow Channel Allocation." 2277 ::= { vdslLineConfProfileEntry 19 } 2279 vdslLineConfUpstreamDataRate OBJECT-TYPE 2280 SYNTAX Unsigned32 2281 UNITS "kbps" 2282 MAX-ACCESS read-create 2283 STATUS current 2284 DESCRIPTION 2285 "Aggregate upstream transmit speed for this line 2286 in steps of 1024 bits/second." 2287 ::= { vdslLineConfProfileEntry 20 } 2289 vdslLineConfDownstreamDataRate OBJECT-TYPE 2290 SYNTAX Unsigned32 2291 UNITS "kbps" 2292 MAX-ACCESS read-create 2293 STATUS current 2294 DESCRIPTION 2295 "Aggregate downstream transmit speed for this line 2296 in steps of 1024 bits/second." 2297 ::= { vdslLineConfProfileEntry 21 } 2299 vdslLineConfDownstreamMaxInterDelay OBJECT-TYPE 2300 SYNTAX Unsigned32 (0..255) 2301 UNITS "ms" 2302 MAX-ACCESS read-create 2303 STATUS current 2304 DESCRIPTION 2305 "Specifies the maximum interleave delay for the 2306 downstream slow channel." 2307 ::= { vdslLineConfProfileEntry 22 } 2309 vdslLineConfUpstreamMaxInterDelay OBJECT-TYPE 2310 SYNTAX Unsigned32 (0..255) 2311 UNITS "ms" 2312 MAX-ACCESS read-create 2313 STATUS current 2314 DESCRIPTION 2315 "Specifies the maximum interleave delay for the 2316 upstream slow channel." 2317 ::= { vdslLineConfProfileEntry 23 } 2319 vdslLineConfUpstreamPboControl OBJECT-TYPE 2320 SYNTAX INTEGER 2321 { 2322 disabled(1), 2323 enabled(2) 2324 } 2325 MAX-ACCESS read-create 2326 STATUS current 2327 DESCRIPTION 2328 "Upstream power backoff (PBO) control for this 2329 line. For modems which do not support upstream 2330 PBO control, this object MUST be fixed at disabled(1)." 2331 ::= { vdslLineConfProfileEntry 24 } 2333 vdslLineConfDownstreamPboControl OBJECT-TYPE 2334 SYNTAX INTEGER 2335 { 2336 disabled(1), 2337 enabled(2) 2338 } 2339 MAX-ACCESS read-create 2340 STATUS current 2341 DESCRIPTION 2342 "Downstream power backoff (PBO) control for this 2343 line. For modems which do not support downstream 2344 PBO control, this object MUST be fixed at disabled(1)." 2345 ::= { vdslLineConfProfileEntry 25 } 2347 vdslLineConfDeploymentScenario OBJECT-TYPE 2348 SYNTAX INTEGER 2349 { 2350 fttCab(1), 2351 fttEx(2), 2352 other(3) 2353 } 2354 MAX-ACCESS read-create 2355 STATUS current 2356 DESCRIPTION 2357 "The VDSL line deployment scenario. When using 2358 fttCab(1), the VTU-C is located in a street cabinet. 2359 When using fttEx(2), the VTU-C is located at the 2360 central office." 2361 ::= { vdslLineConfProfileEntry 26 } 2363 vdslLineConfAdslOccupy OBJECT-TYPE 2364 SYNTAX TruthValue 2365 MAX-ACCESS read-create 2366 STATUS current 2367 DESCRIPTION 2368 "Indicates if the VDSL line can occupy the ADSL 2369 frequency range." 2370 ::= { vdslLineConfProfileEntry 27 } 2372 vdslLineConfApplicableStandard OBJECT-TYPE 2373 SYNTAX INTEGER 2374 { 2375 ansi(1), 2376 etsi(2), 2377 itu(3), 2378 other(4) 2379 } 2380 MAX-ACCESS read-create 2381 STATUS current 2382 DESCRIPTION 2383 "The VDSL standard to be used for the line." 2384 ::= { vdslLineConfProfileEntry 28 } 2386 vdslLineConfBandPlan OBJECT-TYPE 2387 SYNTAX INTEGER 2388 { 2389 bandPlan997(1), 2390 bandPlan998(2), 2391 bandPlanFx(3), 2392 other(4) 2393 } 2394 MAX-ACCESS read-create 2395 STATUS current 2396 DESCRIPTION 2397 "The VDSL band plan to be used for the line. 2399 bandPlan997(1) is to be used for 2400 ITU-T G.993.1 Bandplan-B 2401 ETSI Bandplan 2402 ANSI Plan 997 2404 bandPlan998(2) is to be used for 2405 ITU-T G.993.1 Bandplan-A 2406 ANSI Plan 998 2408 bandPlanFx(3) is to be used for 2409 ITU-T G.993.1 Bandplan-C. 2411 other(4) is to be used for 2412 non-standard bandplans. 2414 If this object is set to bandPlanFx(3), then 2415 the object vdslLineConfBandPlanFx MUST also be 2416 set." 2417 ::= { vdslLineConfProfileEntry 29 } 2419 vdslLineConfBandPlanFx OBJECT-TYPE 2420 SYNTAX Unsigned32 (3750..12000) 2421 UNITS "kHz" 2422 MAX-ACCESS read-create 2423 STATUS current 2424 DESCRIPTION 2425 "The frequency limit between bands D2 and U2 when 2426 vdslLineConfBandPlan is set to bandPlanFx(3)." 2427 ::= { vdslLineConfProfileEntry 30 } 2429 vdslLineConfBandU0Usage OBJECT-TYPE 2430 SYNTAX INTEGER 2431 { 2432 unused(1), 2433 upstream(2), 2434 downstream(3) 2435 } 2436 MAX-ACCESS read-create 2437 STATUS current 2438 DESCRIPTION 2439 "Defines the VDSL link use of the frequency range 2440 [25kHz - 138kHz] (U0)." 2441 ::= { vdslLineConfProfileEntry 31 } 2443 vdslLineConfUpstreamPsdTemplate OBJECT-TYPE 2444 SYNTAX INTEGER 2445 { 2446 templateMask1(1), 2447 templateMask2(2) 2448 } 2449 MAX-ACCESS read-create 2450 STATUS current 2451 DESCRIPTION 2452 "The upstream PSD template to be used for the line." 2453 ::= { vdslLineConfProfileEntry 32 } 2455 vdslLineConfDownstreamPsdTemplate OBJECT-TYPE 2456 SYNTAX INTEGER 2457 { 2458 templateMask1(1), 2459 templateMask2(2) 2460 } 2461 MAX-ACCESS read-create 2462 STATUS current 2463 DESCRIPTION 2464 "The downstream PSD template to be used for the line." 2465 ::= { vdslLineConfProfileEntry 33 } 2467 vdslLineConfProfileRowStatus OBJECT-TYPE 2468 SYNTAX RowStatus 2469 MAX-ACCESS read-create 2470 STATUS current 2471 DESCRIPTION 2472 "This object is used to create a new row or modify or 2473 delete an existing row in this table. 2475 A profile activated by setting this object to `active'. 2476 When `active' is set, the system will validate the profile. 2478 Before a profile can be deleted or taken out of 2479 service, (by setting this object to `destroy' or 2480 `outOfService') it must be first unreferenced 2481 from all associated lines." 2482 ::= { vdslLineConfProfileEntry 34 } 2484 -- 2485 -- Multiple carrier modulation (MCM) configuration profile tables 2486 -- 2488 vdslLineMCMConfProfileTable OBJECT-TYPE 2489 SYNTAX SEQUENCE OF VdslLineMCMConfProfileEntry 2490 MAX-ACCESS not-accessible 2491 STATUS current 2492 DESCRIPTION 2493 "This table contains additional information on 2494 multiple carrier VDSL lines. One entry in this table 2495 reflects a profile defined by a manager which can be used 2496 to configure the VDSL line. 2498 The entries in this table MUST NOT be used for single 2499 carrier (SCM) VDSL lines." 2500 ::= { vdslMibObjects 12 } 2502 vdslLineMCMConfProfileEntry OBJECT-TYPE 2503 SYNTAX VdslLineMCMConfProfileEntry 2504 MAX-ACCESS not-accessible 2505 STATUS current 2506 DESCRIPTION 2507 "Each entry consists of a list of parameters that 2508 represents the configuration of a multiple carrier 2509 modulation VDSL modem. A default profile with an 2510 index of 1 will always exist and its parameters will 2511 be set to vendor specific values, unless otherwise 2512 specified in this document." 2513 INDEX { vdslLineConfProfileIndex } 2514 ::= { vdslLineMCMConfProfileTable 1 } 2516 VdslLineMCMConfProfileEntry ::= 2517 SEQUENCE 2518 { 2519 vdslMCMConfProfileTxWindowLength Unsigned32, 2520 vdslMCMConfProfileRowStatus RowStatus 2521 } 2523 vdslMCMConfProfileTxWindowLength OBJECT-TYPE 2524 SYNTAX Unsigned32 (1..255) 2525 UNITS "samples" 2526 MAX-ACCESS read-create 2527 STATUS current 2528 DESCRIPTION 2529 "Specifies the length of the transmit window, counted 2530 in samples at the sampling rate corresponding to the 2531 negotiated value of N." 2532 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 2533 ::= { vdslLineMCMConfProfileEntry 1 } 2535 vdslMCMConfProfileRowStatus OBJECT-TYPE 2536 SYNTAX RowStatus 2537 MAX-ACCESS read-create 2538 STATUS current 2539 DESCRIPTION 2540 "This object is used to create a new row or modify or 2541 delete an existing row in this table. 2543 A profile activated by setting this object to `active'. 2544 When `active' is set, the system will validate the profile. 2546 Before a profile can be deleted or taken out of 2547 service, (by setting this object to `destroy' or 2548 `outOfService') it must be first unreferenced 2549 from all associated lines." 2550 ::= { vdslLineMCMConfProfileEntry 2 } 2552 vdslLineMCMConfProfileTxBandTable OBJECT-TYPE 2553 SYNTAX SEQUENCE OF VdslLineMCMConfProfileTxBandEntry 2554 MAX-ACCESS not-accessible 2555 STATUS current 2556 DESCRIPTION 2557 "This table contains transmit band descriptor configuration 2558 information for a VDSL line. Each entry in this table 2559 reflects the configuration for one of possibly many bands 2560 with a multiple carrier modulation (MCM) VDSL line. 2561 These entries are defined by a manager and can be used to 2562 configure the VDSL line. 2564 The entries in this table MUST NOT be used for single 2565 carrier (SCM) VDSL lines." 2566 ::= { vdslMibObjects 13 } 2568 vdslLineMCMConfProfileTxBandEntry OBJECT-TYPE 2569 SYNTAX VdslLineMCMConfProfileTxBandEntry 2570 MAX-ACCESS not-accessible 2571 STATUS current 2572 DESCRIPTION 2573 "Each entry consists of a transmit band descriptor, which 2574 is defined by a start and a stop tone index. 2576 A default profile with an index of 1 will always exist and 2577 its parameters will be set to vendor specific values, 2578 unless otherwise specified in this document." 2579 INDEX { vdslLineConfProfileIndex, 2580 vdslMCMConfProfileTxBandNumber } 2581 ::= { vdslLineMCMConfProfileTxBandTable 1 } 2583 VdslLineMCMConfProfileTxBandEntry ::= 2584 SEQUENCE 2585 { 2586 vdslMCMConfProfileTxBandNumber Unsigned32, 2587 vdslMCMConfProfileTxBandStart Unsigned32, 2588 vdslMCMConfProfileTxBandStop Unsigned32, 2589 vdslMCMConfProfileTxBandRowStatus RowStatus 2590 } 2592 vdslMCMConfProfileTxBandNumber OBJECT-TYPE 2593 SYNTAX Unsigned32 2594 MAX-ACCESS read-create 2595 STATUS current 2596 DESCRIPTION 2597 "The index for this band descriptor entry." 2598 ::= { vdslLineMCMConfProfileTxBandEntry 1 } 2600 vdslMCMConfProfileTxBandStart OBJECT-TYPE 2601 SYNTAX Unsigned32 2602 MAX-ACCESS read-create 2603 STATUS current 2604 DESCRIPTION 2605 "Start tone index for this band." 2606 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 2607 ::= { vdslLineMCMConfProfileTxBandEntry 2 } 2609 vdslMCMConfProfileTxBandStop OBJECT-TYPE 2610 SYNTAX Unsigned32 2611 MAX-ACCESS read-create 2612 STATUS current 2613 DESCRIPTION 2614 "Stop tone index for this band." 2615 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 2616 ::= { vdslLineMCMConfProfileTxBandEntry 3 } 2618 vdslMCMConfProfileTxBandRowStatus OBJECT-TYPE 2619 SYNTAX RowStatus 2620 MAX-ACCESS read-create 2621 STATUS current 2622 DESCRIPTION 2623 "This object is used to create a new row or modify or 2624 delete an existing row in this table. 2626 A profile activated by setting this object to `active'. 2627 When `active' is set, the system will validate the profile. 2629 Before a profile can be deleted or taken out of 2630 service, (by setting this object to `destroy' or 2631 `outOfService') it must be first unreferenced 2632 from all associated lines." 2633 ::= { vdslLineMCMConfProfileTxBandEntry 4 } 2635 vdslLineMCMConfProfileRxBandTable OBJECT-TYPE 2636 SYNTAX SEQUENCE OF VdslLineMCMConfProfileRxBandEntry 2637 MAX-ACCESS not-accessible 2638 STATUS current 2639 DESCRIPTION 2640 "This table contains receive band descriptor configuration 2641 information for a VDSL line. Each entry in this table 2642 reflects the configuration for one of possibly many bands 2643 with a multiple carrier modulation (MCM) VDSL line. 2644 These entries are defined by a manager and can be used to 2645 configure the VDSL line. 2647 The entries in this table MUST NOT be used for single 2648 carrier (SCM) VDSL lines." 2649 ::= { vdslMibObjects 14 } 2651 vdslLineMCMConfProfileRxBandEntry OBJECT-TYPE 2652 SYNTAX VdslLineMCMConfProfileRxBandEntry 2653 MAX-ACCESS not-accessible 2654 STATUS current 2655 DESCRIPTION 2656 "Each entry consists of a transmit band descriptor, which 2657 is defined by a start and a stop tone index. 2659 A default profile with an index of 1 will always exist and 2660 its parameters will be set to vendor specific values, 2661 unless otherwise specified in this document." 2662 INDEX { vdslLineConfProfileIndex, 2663 vdslMCMConfProfileRxBandNumber } 2664 ::= { vdslLineMCMConfProfileRxBandTable 1 } 2666 VdslLineMCMConfProfileRxBandEntry ::= 2667 SEQUENCE 2668 { 2669 vdslMCMConfProfileRxBandNumber Unsigned32, 2670 vdslMCMConfProfileRxBandStart Unsigned32, 2671 vdslMCMConfProfileRxBandStop Unsigned32, 2672 vdslMCMConfProfileRxBandRowStatus RowStatus 2673 } 2675 vdslMCMConfProfileRxBandNumber OBJECT-TYPE 2676 SYNTAX Unsigned32 2677 MAX-ACCESS read-create 2678 STATUS current 2679 DESCRIPTION 2680 "The index for this band descriptor entry." 2681 ::= { vdslLineMCMConfProfileRxBandEntry 1 } 2683 vdslMCMConfProfileRxBandStart OBJECT-TYPE 2684 SYNTAX Unsigned32 2685 MAX-ACCESS read-create 2686 STATUS current 2687 DESCRIPTION 2688 "Start tone index for this band." 2689 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 2690 ::= { vdslLineMCMConfProfileRxBandEntry 2 } 2692 vdslMCMConfProfileRxBandStop OBJECT-TYPE 2693 SYNTAX Unsigned32 2694 MAX-ACCESS read-create 2695 STATUS current 2696 DESCRIPTION 2697 "Stop tone index for this band." 2698 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 2699 ::= { vdslLineMCMConfProfileRxBandEntry 3 } 2701 vdslMCMConfProfileRxBandRowStatus OBJECT-TYPE 2702 SYNTAX RowStatus 2703 MAX-ACCESS read-create 2704 STATUS current 2705 DESCRIPTION 2706 "This object is used to create a new row or modify or 2707 delete an existing row in this table. 2709 A profile activated by setting this object to `active'. 2710 When `active' is set, the system will validate the profile. 2712 Before a profile can be deleted or taken out of 2713 service, (by setting this object to `destroy' or 2714 `outOfService') it must be first unreferenced 2715 from all associated lines." 2716 ::= { vdslLineMCMConfProfileRxBandEntry 4 } 2718 vdslLineMCMConfProfileTxPSDTable OBJECT-TYPE 2719 SYNTAX SEQUENCE OF VdslLineMCMConfProfileTxPSDEntry 2720 MAX-ACCESS not-accessible 2721 STATUS current 2722 DESCRIPTION 2723 "This table contains transmit PSD mask descriptor 2724 configuration information for a VDSL line. Each entry in 2725 this table reflects the configuration for one tone within 2726 a multiple carrier modulation (MCM) VDSL line. These 2727 entries are defined by a manager and can be used to 2728 configure the VDSL line. 2730 The entries in this table MUST NOT be used for single 2731 carrier (SCM) VDSL lines." 2732 ::= { vdslMibObjects 15 } 2734 vdslLineMCMConfProfileTxPSDEntry OBJECT-TYPE 2735 SYNTAX VdslLineMCMConfProfileTxPSDEntry 2736 MAX-ACCESS not-accessible 2737 STATUS current 2738 DESCRIPTION 2739 "Each entry consists of a transmit PSD mask descriptor, 2740 which defines the power spectral density (PSD) for a tone. 2741 A default profile with an index of 1 will always exist and 2742 its parameters will be set to vendor specific values, 2743 unless otherwise specified in this document." 2744 INDEX { vdslLineConfProfileIndex, 2745 vdslMCMConfProfileTxPSDNumber } 2746 ::= { vdslLineMCMConfProfileTxPSDTable 1 } 2748 VdslLineMCMConfProfileTxPSDEntry ::= 2749 SEQUENCE 2750 { 2751 vdslMCMConfProfileTxPSDNumber Unsigned32, 2752 vdslMCMConfProfileTxPSDTone Unsigned32, 2753 vdslMCMConfProfileTxPSDPSD Unsigned32, 2754 vdslMCMConfProfileTxPSDRowStatus RowStatus 2755 } 2757 vdslMCMConfProfileTxPSDNumber OBJECT-TYPE 2758 SYNTAX Unsigned32 2759 MAX-ACCESS read-create 2760 STATUS current 2761 DESCRIPTION 2762 "The index for this mask descriptor entry." 2763 ::= { vdslLineMCMConfProfileTxPSDEntry 1 } 2765 vdslMCMConfProfileTxPSDTone OBJECT-TYPE 2766 SYNTAX Unsigned32 2767 MAX-ACCESS read-create 2768 STATUS current 2769 DESCRIPTION 2770 "The tone index for which the PSD is being specified." 2771 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 2772 ::= { vdslLineMCMConfProfileTxPSDEntry 2 } 2774 vdslMCMConfProfileTxPSDPSD OBJECT-TYPE 2775 SYNTAX Unsigned32 2776 UNITS "0.5dBm" 2777 MAX-ACCESS read-create 2778 STATUS current 2779 DESCRIPTION 2780 "Power Spectral Density level in steps of 0.5dB with 2781 an offset of -140dbm/Hz." 2782 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 2783 ::= { vdslLineMCMConfProfileTxPSDEntry 3 } 2785 vdslMCMConfProfileTxPSDRowStatus OBJECT-TYPE 2786 SYNTAX RowStatus 2787 MAX-ACCESS read-create 2788 STATUS current 2789 DESCRIPTION 2790 "This object is used to create a new row or modify or 2791 delete an existing row in this table. 2793 A profile activated by setting this object to `active'. 2794 When `active' is set, the system will validate the profile. 2796 Before a profile can be deleted or taken out of 2797 service, (by setting this object to `destroy' or 2798 `outOfService') it must be first unreferenced 2799 from all associated lines." 2800 ::= { vdslLineMCMConfProfileTxPSDEntry 4 } 2802 vdslLineMCMConfProfileMaxTxPSDTable OBJECT-TYPE 2803 SYNTAX SEQUENCE OF VdslLineMCMConfProfileMaxTxPSDEntry 2804 MAX-ACCESS not-accessible 2805 STATUS current 2806 DESCRIPTION 2807 "This table contains transmit maximum PSD mask descriptor 2808 configuration information for a VDSL line. Each entry in 2809 this table reflects the configuration for one tone within 2810 a multiple carrier modulation (MCM) VDSL modem. These 2811 entries are defined by a manager and can be used to 2812 configure the VDSL line. 2814 The entries in this table MUST NOT be used for single 2815 carrier (SCM) VDSL lines." 2816 ::= { vdslMibObjects 16 } 2818 vdslLineMCMConfProfileMaxTxPSDEntry OBJECT-TYPE 2819 SYNTAX VdslLineMCMConfProfileMaxTxPSDEntry 2820 MAX-ACCESS not-accessible 2821 STATUS current 2822 DESCRIPTION 2823 "Each entry consists of a transmit PSD mask descriptor, 2824 which defines the maximum power spectral density (PSD) 2825 for a tone. 2827 A default profile with an index of 1 MUST always exist and 2828 its parameters will be set to vendor specific values, 2829 unless otherwise specified in this document." 2830 INDEX { vdslLineConfProfileIndex, 2831 vdslMCMConfProfileMaxTxPSDNumber } 2833 ::= { vdslLineMCMConfProfileMaxTxPSDTable 1 } 2835 VdslLineMCMConfProfileMaxTxPSDEntry ::= 2836 SEQUENCE 2837 { 2838 vdslMCMConfProfileMaxTxPSDNumber Unsigned32, 2839 vdslMCMConfProfileMaxTxPSDTone Unsigned32, 2840 vdslMCMConfProfileMaxTxPSDPSD Unsigned32, 2841 vdslMCMConfProfileMaxTxPSDRowStatus RowStatus 2842 } 2844 vdslMCMConfProfileMaxTxPSDNumber OBJECT-TYPE 2845 SYNTAX Unsigned32 2846 MAX-ACCESS read-create 2847 STATUS current 2848 DESCRIPTION 2849 "The index for this band descriptor entry." 2850 ::= { vdslLineMCMConfProfileMaxTxPSDEntry 1 } 2852 vdslMCMConfProfileMaxTxPSDTone OBJECT-TYPE 2853 SYNTAX Unsigned32 2854 MAX-ACCESS read-create 2855 STATUS current 2856 DESCRIPTION 2857 "The tone index for which the PSD is being specified." 2858 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 2859 ::= { vdslLineMCMConfProfileMaxTxPSDEntry 2 } 2861 vdslMCMConfProfileMaxTxPSDPSD OBJECT-TYPE 2862 SYNTAX Unsigned32 2863 UNITS "0.5dBm" 2864 MAX-ACCESS read-create 2865 STATUS current 2866 DESCRIPTION 2867 "Power Spectral Density level in steps of 0.5dB with 2868 an offset of -140dbm/Hz." 2869 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 2870 ::= { vdslLineMCMConfProfileMaxTxPSDEntry 3 } 2872 vdslMCMConfProfileMaxTxPSDRowStatus OBJECT-TYPE 2873 SYNTAX RowStatus 2874 MAX-ACCESS read-create 2875 STATUS current 2876 DESCRIPTION 2877 "This object is used to create a new row or modify or 2878 delete an existing row in this table. 2880 A profile activated by setting this object to `active'. 2881 When `active' is set, the system will validate the profile. 2883 Before a profile can be deleted or taken out of 2884 service, (by setting this object to `destroy' or 2885 `outOfService') it must be first unreferenced 2886 from all associated lines." 2887 ::= { vdslLineMCMConfProfileMaxTxPSDEntry 4 } 2889 vdslLineMCMConfProfileMaxRxPSDTable OBJECT-TYPE 2890 SYNTAX SEQUENCE OF VdslLineMCMConfProfileMaxRxPSDEntry 2891 MAX-ACCESS not-accessible 2892 STATUS current 2893 DESCRIPTION 2894 "This table contains maximum receive PSD mask descriptor 2895 configuration information for a VDSL line. Each entry in 2896 this table reflects the configuration for one tone within 2897 a multiple carrier modulation (MCM) VDSL modem. These 2898 entries are defined by a manager and can be used to 2899 configure the VDSL line. 2901 The entries in this table MUST NOT be used for single 2902 carrier (SCM) VDSL lines." 2903 ::= { vdslMibObjects 17 } 2905 vdslLineMCMConfProfileMaxRxPSDEntry OBJECT-TYPE 2906 SYNTAX VdslLineMCMConfProfileMaxRxPSDEntry 2907 MAX-ACCESS not-accessible 2908 STATUS current 2909 DESCRIPTION 2910 "Each entry consists of a transmit PSD mask descriptor, 2911 which defines the power spectral density (PSD) for a 2912 tone. 2914 A default profile with an index of 1 will always exist and 2915 its parameters will be set to vendor specific values, 2916 unless otherwise specified in this document." 2917 INDEX { vdslLineConfProfileIndex, 2918 vdslMCMConfProfileMaxRxPSDNumber } 2919 ::= { vdslLineMCMConfProfileMaxRxPSDTable 1 } 2921 VdslLineMCMConfProfileMaxRxPSDEntry ::= 2922 SEQUENCE 2923 { 2924 vdslMCMConfProfileMaxRxPSDNumber Unsigned32, 2925 vdslMCMConfProfileMaxRxPSDTone Unsigned32, 2926 vdslMCMConfProfileMaxRxPSDPSD Unsigned32, 2927 vdslMCMConfProfileMaxRxPSDRowStatus RowStatus 2928 } 2930 vdslMCMConfProfileMaxRxPSDNumber OBJECT-TYPE 2931 SYNTAX Unsigned32 2932 MAX-ACCESS read-create 2933 STATUS current 2934 DESCRIPTION 2935 "The index for this band descriptor entry." 2936 ::= { vdslLineMCMConfProfileMaxRxPSDEntry 1 } 2938 vdslMCMConfProfileMaxRxPSDTone OBJECT-TYPE 2939 SYNTAX Unsigned32 2940 MAX-ACCESS read-create 2941 STATUS current 2942 DESCRIPTION 2943 "The tone index for which the PSD is being specified." 2944 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 2945 ::= { vdslLineMCMConfProfileMaxRxPSDEntry 2 } 2947 vdslMCMConfProfileMaxRxPSDPSD OBJECT-TYPE 2948 SYNTAX Unsigned32 2949 UNITS "0.5dBm" 2950 MAX-ACCESS read-create 2951 STATUS current 2952 DESCRIPTION 2953 "Power Spectral Density level in steps of 0.5dB with 2954 an offset of -140dbm/Hz." 2955 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 2956 ::= { vdslLineMCMConfProfileMaxRxPSDEntry 3 } 2958 vdslMCMConfProfileMaxRxPSDRowStatus OBJECT-TYPE 2959 SYNTAX RowStatus 2960 MAX-ACCESS read-create 2961 STATUS current 2962 DESCRIPTION 2963 "This object is used to create a new row or modify or 2964 delete an existing row in this table. 2966 A profile activated by setting this object to `active'. 2967 When `active' is set, the system will validate the profile. 2969 Before a profile can be deleted or taken out of 2970 service, (by setting this object to `destroy' or 2971 `outOfService') it must be first unreferenced 2972 from all associated lines." 2973 ::= { vdslLineMCMConfProfileMaxRxPSDEntry 4 } 2975 -- 2976 -- Single carrier modulation (SCM) configuration profile tables 2977 -- 2979 vdslLineSCMConfProfileTable OBJECT-TYPE 2980 SYNTAX SEQUENCE OF VdslLineSCMConfProfileEntry 2981 MAX-ACCESS not-accessible 2982 STATUS current 2983 DESCRIPTION 2984 "This table contains information on the VDSL line 2985 configuration. One entry in this table reflects a 2986 profile defined by a manager which can be used to 2987 configure the VDSL line. 2989 The entries in this table MUST NOT be used for 2990 multiple carrier (MCM) VDSL lines." 2991 ::= { vdslMibObjects 18 } 2993 vdslLineSCMConfProfileEntry OBJECT-TYPE 2994 SYNTAX VdslLineSCMConfProfileEntry 2995 MAX-ACCESS not-accessible 2996 STATUS current 2997 DESCRIPTION 2998 "Each entry consists of a list of parameters that 2999 represents the configuration of a single carrier 3000 modulation VDSL modem. 3002 A default profile with an index of 1 MUST always exist and 3003 its parameters will be set to vendor specific values, 3004 unless otherwise specified in this document." 3005 INDEX { vdslLineConfProfileIndex, vdslSCMConfProfileSide } 3006 ::= { vdslLineSCMConfProfileTable 1 } 3008 VdslLineSCMConfProfileEntry ::= 3009 SEQUENCE 3010 { 3011 vdslSCMConfProfileSide VdslLineEntity, 3012 vdslSCMConfProfileInterleaveDepth Unsigned32, 3013 vdslSCMConfProfileNumCarriers INTEGER, 3014 vdslSCMConfProfileFastCodewordSize Unsigned32, 3015 vdslSCMConfProfileTransmitPSDMask BITS, 3016 vdslSCMConfProfileVendorNotch1Start Unsigned32, 3017 vdslSCMConfProfileVendorNotch1Stop Unsigned32, 3018 vdslSCMConfProfileVendorNotch2Start Unsigned32, 3019 vdslSCMConfProfileVendorNotch2Stop Unsigned32, 3020 vdslSCMConfProfileFastFecSize INTEGER, 3021 vdslSCMConfProfileSlowBlockSize INTEGER, 3022 vdslSCMConfProfileRowStatus RowStatus 3023 } 3025 vdslSCMConfProfileSide OBJECT-TYPE 3026 SYNTAX VdslLineEntity 3027 MAX-ACCESS read-create 3028 STATUS current 3029 DESCRIPTION 3030 "Identifies whether this entry describes downstream 3031 or upstream transmission." 3032 ::= { vdslLineSCMConfProfileEntry 1 } 3034 vdslSCMConfProfileInterleaveDepth OBJECT-TYPE 3035 SYNTAX Unsigned32 (0..64) 3036 MAX-ACCESS read-create 3037 STATUS current 3038 DESCRIPTION 3039 "Specifies the interleaving depth." 3040 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 3041 ::= { vdslLineSCMConfProfileEntry 2 } 3043 vdslSCMConfProfileNumCarriers OBJECT-TYPE 3044 SYNTAX INTEGER 3045 { 3046 oneCarrier(1), 3047 twoCarriers(2) 3048 } 3049 MAX-ACCESS read-create 3050 STATUS current 3051 DESCRIPTION 3052 "Specifies the number of carriers." 3053 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 3054 ::= { vdslLineSCMConfProfileEntry 3 } 3056 vdslSCMConfProfileFastCodewordSize OBJECT-TYPE 3057 SYNTAX Unsigned32 (0..180) 3058 UNITS "octets" 3059 MAX-ACCESS read-create 3060 STATUS current 3061 DESCRIPTION 3062 "Specifies the length in octets of the fast codeword. 3063 A value of 0 indicates that the single latency transport 3064 class is to be utilized." 3065 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 3066 ::= { vdslLineSCMConfProfileEntry 4 } 3068 vdslSCMConfProfileTransmitPSDMask OBJECT-TYPE 3069 SYNTAX BITS 3070 { 3071 vendorNotch1(0), -- vendor specific notch 3072 vendorNotch2(1), -- vendor specific notch 3073 amateurBand30m(2), -- amateur radio band notch 3074 amateurBand40m(3), -- amateur radio band notch 3075 amateurBand80m(4), -- amateur radio band notch 3076 amateurBand160m(5) -- amateur radio band notch 3077 } 3078 MAX-ACCESS read-create 3079 STATUS current 3080 DESCRIPTION 3081 "The transmit power spectral density mask code. 3083 Amateur radio band notching is defined in the VDSL 3084 spectrum as follows: 3086 Band Start Frequency Stop Frequecy 3087 ---- ------------------ -------------------------------- 3088 30m 1810 kHz 2000 kHz 3089 40m 3500 kHz 3800 kHz (ETSI); 4000 kHz (ANSI) 3090 80m 7000 kHz 7100 kHz (ETSI); 7300 kHz (ANSI) 3091 160m 10100 kHz 10150 kHz 3092 Notching for each standard band can be enabled or disabled 3093 via the bit mask. 3095 Two custom, or vendor specific, notches may be specified. 3096 If either of these are enabled via the bit mask, then the 3097 following objects MUST be specified: 3099 If vendorNotch1 is enabled, then both 3100 vdslSCMConfProfileVendorNotch1Start 3101 vdslSCMConfProfileVendorNotch1Stop 3102 MUST be specified. 3104 If vendorNotch2 is enabled, then both 3105 vdslSCMConfProfileVendorNotch2Start 3106 vdslSCMConfProfileVendorNotch2Stop 3107 MUST be specified." 3108 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 3109 ::= { vdslLineSCMConfProfileEntry 5 } 3111 vdslSCMConfProfileVendorNotch1Start OBJECT-TYPE 3112 SYNTAX Unsigned32 3113 UNITS "kHz" 3114 MAX-ACCESS read-create 3115 STATUS current 3116 DESCRIPTION 3117 "Specifies the start frequency of the vendor-specific 3118 amateur radio notch 1." 3119 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 3120 ::= { vdslLineSCMConfProfileEntry 6 } 3122 vdslSCMConfProfileVendorNotch1Stop OBJECT-TYPE 3123 SYNTAX Unsigned32 3124 UNITS "kHz" 3125 MAX-ACCESS read-create 3126 STATUS current 3127 DESCRIPTION 3128 "Specifies the stop frequency of the vendor-specific 3129 amateur radio notch 1." 3130 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 3131 ::= { vdslLineSCMConfProfileEntry 7 } 3133 vdslSCMConfProfileVendorNotch2Start OBJECT-TYPE 3134 SYNTAX Unsigned32 3135 UNITS "kHz" 3136 MAX-ACCESS read-create 3137 STATUS current 3138 DESCRIPTION 3139 "Specifies the start frequency of the vendor-specific 3140 amateur radio notch 2." 3141 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 3142 ::= { vdslLineSCMConfProfileEntry 8 } 3144 vdslSCMConfProfileVendorNotch2Stop OBJECT-TYPE 3145 SYNTAX Unsigned32 3146 UNITS "kHz" 3147 MAX-ACCESS read-create 3148 STATUS current 3149 DESCRIPTION 3150 "Specifies the stop frequency of the vendor-specific 3151 amateur radio notch 2." 3152 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 3153 ::= { vdslLineSCMConfProfileEntry 9 } 3155 vdslSCMConfProfileFastFecSize OBJECT-TYPE 3156 SYNTAX INTEGER 3157 { 3158 noFEC(1), 3159 fecSize2(2), 3160 fecSize4(3), 3161 fecSize16(4) 3162 } 3163 MAX-ACCESS read-create 3164 STATUS current 3165 DESCRIPTION 3166 "When fast channel is being used, this object specifies 3167 the size of the forward error correction (FEC) codeword." 3168 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 3169 ::= { vdslLineSCMConfProfileEntry 10 } 3171 vdslSCMConfProfileSlowBlockSize OBJECT-TYPE 3172 SYNTAX INTEGER 3173 { 3174 s8(1), 3175 s4(2), 3176 s2(3) 3177 } 3178 MAX-ACCESS read-create 3179 STATUS current 3180 DESCRIPTION 3181 "Specifies the slow channel interleaved block size. 3182 Options are s/8, s/4, or s/2." 3183 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 3184 ::= { vdslLineSCMConfProfileEntry 11 } 3186 vdslSCMConfProfileRowStatus OBJECT-TYPE 3187 SYNTAX RowStatus 3188 MAX-ACCESS read-create 3189 STATUS current 3190 DESCRIPTION 3191 "This object is used to create a new row or modify or 3192 delete an existing row in this table. 3194 A profile activated by setting this object to `active'. 3195 When `active' is set, the system will validate the profile. 3197 Before a profile can be deleted or taken out of 3198 service, (by setting this object to `destroy' or 3199 `outOfService') it must be first unreferenced 3200 from all associated lines." 3201 ::= { vdslLineSCMConfProfileEntry 12 } 3203 vdslLineSCMConfProfileTxBandTable OBJECT-TYPE 3204 SYNTAX SEQUENCE OF VdslLineSCMConfProfileTxBandEntry 3205 MAX-ACCESS not-accessible 3206 STATUS current 3207 DESCRIPTION 3208 "This table contains transmit band descriptor configuration 3209 information for a VDSL line. Each entry in this table 3210 reflects the configuration for one of possibly three bands 3211 with a single carrier modulation (SCM) VDSL line. These 3212 entries are defined by a manager and can be used to configure 3213 the VDSL line. 3215 The entries in this table MUST NOT be used for 3216 multiple carrier (MCM) VDSL lines." 3217 ::= { vdslMibObjects 19 } 3219 vdslLineSCMConfProfileTxBandEntry OBJECT-TYPE 3220 SYNTAX VdslLineSCMConfProfileTxBandEntry 3221 MAX-ACCESS not-accessible 3222 STATUS current 3223 DESCRIPTION 3224 "Each entry consists of a list of parameters that 3225 represents the configuration of a single carrier 3226 modulation VDSL modem transmit band. 3228 A default profile with an index of 1 MUST always exist and 3229 its parameters will be set to vendor specific values, 3230 unless otherwise specified in this document." 3231 INDEX { vdslLineConfProfileIndex, 3232 vdslSCMConfProfileTxBandSide, 3233 vdslSCMConfProfileTxBandNumber } 3234 ::= { vdslLineSCMConfProfileTxBandTable 1 } 3236 VdslLineSCMConfProfileTxBandEntry ::= 3237 SEQUENCE 3238 { 3239 vdslSCMConfProfileTxBandSide VdslLineEntity, 3240 vdslSCMConfProfileTxBandNumber INTEGER, 3241 vdslSCMConfProfileTxBandTransmitPSDLevel Unsigned32, 3242 vdslSCMConfProfileTxBandSymbolRateProfile Unsigned32, 3243 vdslSCMConfProfileTxBandConstellationSize Unsigned32, 3244 vdslSCMConfProfileTxBandCenterFrequency Unsigned32, 3245 vdslSCMConfProfileTxBandRowStatus RowStatus 3246 } 3248 vdslSCMConfProfileTxBandSide OBJECT-TYPE 3249 SYNTAX VdslLineEntity 3250 MAX-ACCESS read-create 3251 STATUS current 3252 DESCRIPTION 3253 "Identifies whether this band entry describes 3254 downstream or upstream transmission." 3255 ::= { vdslLineSCMConfProfileTxBandEntry 1 } 3257 vdslSCMConfProfileTxBandNumber OBJECT-TYPE 3258 SYNTAX INTEGER 3259 { 3260 band1(1), 3261 band2(2), 3262 upstreamU0(3) 3263 } 3264 MAX-ACCESS read-create 3265 STATUS current 3266 DESCRIPTION 3267 "The SCN transmit band number for this entry." 3268 ::= { vdslLineSCMConfProfileTxBandEntry 2 } 3270 vdslSCMConfProfileTxBandTransmitPSDLevel OBJECT-TYPE 3271 SYNTAX Unsigned32 3272 UNITS "-dBm/Hz" 3273 MAX-ACCESS read-create 3274 STATUS current 3275 DESCRIPTION 3276 "The transmit power spectral density for the VDSL modem." 3277 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 3278 ::= { vdslLineSCMConfProfileTxBandEntry 3 } 3280 vdslSCMConfProfileTxBandSymbolRateProfile OBJECT-TYPE 3281 SYNTAX Unsigned32 3282 UNITS "kbaud" 3283 MAX-ACCESS read-create 3284 STATUS current 3285 DESCRIPTION 3286 "The symbol rate profile calculated as S = SR/BSR, where 3287 SR is the required symbol rate in kbaud, BSR = 67.5." 3288 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 3289 ::= { vdslLineSCMConfProfileTxBandEntry 4 } 3291 vdslSCMConfProfileTxBandConstellationSize OBJECT-TYPE 3292 SYNTAX Unsigned32 (0..8) 3293 UNITS "log2" 3294 MAX-ACCESS read-create 3295 STATUS current 3296 DESCRIPTION 3297 "Specifies the constellation size." 3298 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 3299 ::= { vdslLineSCMConfProfileTxBandEntry 5 } 3301 vdslSCMConfProfileTxBandCenterFrequency OBJECT-TYPE 3302 SYNTAX Unsigned32 (0..511) 3303 UNITS "33.75kHz" 3304 MAX-ACCESS read-create 3305 STATUS current 3306 DESCRIPTION 3307 "Specifies the center frequency profile K." 3308 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 3309 ::= { vdslLineSCMConfProfileTxBandEntry 6 } 3311 vdslSCMConfProfileTxBandRowStatus OBJECT-TYPE 3312 SYNTAX RowStatus 3313 MAX-ACCESS read-create 3314 STATUS current 3315 DESCRIPTION 3316 "This object is used to create a new row or modify or 3317 delete an existing row in this table. 3319 A profile activated by setting this object to `active'. 3320 When `active' is set, the system will validate the profile. 3322 Before a profile can be deleted or taken out of 3323 service, (by setting this object to `destroy' or 3324 `outOfService') it must be first unreferenced 3325 from all associated lines." 3326 ::= { vdslLineSCMConfProfileTxBandEntry 7 } 3328 -- 3329 -- Alarm configuration profile table 3330 -- 3332 vdslLineAlarmConfProfileTable OBJECT-TYPE 3333 SYNTAX SEQUENCE OF VdslLineAlarmConfProfileEntry 3334 MAX-ACCESS not-accessible 3335 STATUS current 3336 DESCRIPTION 3337 "This table contains information on the VDSL line alarm 3338 configuration. One entry in this table reflects a profile 3339 defined by a manager which can be used to configure the 3340 VDSL line alarm thresholds." 3341 ::= { vdslMibObjects 20 } 3343 vdslLineAlarmConfProfileEntry OBJECT-TYPE 3344 SYNTAX VdslLineAlarmConfProfileEntry 3345 MAX-ACCESS not-accessible 3346 STATUS current 3347 DESCRIPTION 3348 "Each entry consists of a list of parameters that 3349 represents the configuration of a VDSL line alarm 3350 profile. 3352 A default profile with an index of 1 MUST always exist and 3353 its parameters will be set to vendor specific values, 3354 unless otherwise specified in this document." 3355 INDEX { vdslLineAlarmConfProfileIndex } 3356 ::= { vdslLineAlarmConfProfileTable 1 } 3358 VdslLineAlarmConfProfileEntry ::= 3359 SEQUENCE 3360 { 3361 vdslLineAlarmConfProfileIndex Unsigned32, 3362 vdslLineAlarmConfProfileName SnmpAdminString, 3363 vdslThresh15MinLofs HCPerfIntervalThreshold, 3364 vdslThresh15MinLoss HCPerfIntervalThreshold, 3365 vdslThresh15MinLprs HCPerfIntervalThreshold, 3366 vdslThresh15MinESs HCPerfIntervalThreshold, 3367 vdslThresh15MinSESs HCPerfIntervalThreshold, 3368 vdslThresh15MinUASs HCPerfIntervalThreshold, 3369 vdslInitFailureNotificationEnable TruthValue, 3370 vdslLineAlarmConfProfileRowStatus RowStatus 3371 } 3373 vdslLineAlarmConfProfileIndex OBJECT-TYPE 3374 SYNTAX Unsigned32 3375 MAX-ACCESS read-create 3376 STATUS current 3377 DESCRIPTION 3378 "This object is used by the line alarm configuration table 3379 in order to identify a row in that table. The system MUST 3380 provide a default profile whose index is 1." 3381 ::= { vdslLineAlarmConfProfileEntry 1 } 3383 vdslLineAlarmConfProfileName OBJECT-TYPE 3384 SYNTAX SnmpAdminString (SIZE (1..32)) 3385 MAX-ACCESS read-create 3386 STATUS current 3387 DESCRIPTION 3388 "The name for this profile as specified by a user." 3389 ::= { vdslLineAlarmConfProfileEntry 2 } 3391 vdslThresh15MinLofs OBJECT-TYPE 3392 SYNTAX HCPerfIntervalThreshold 3393 UNITS "seconds" 3394 MAX-ACCESS read-create 3395 STATUS current 3396 DESCRIPTION 3397 "This object configures the threshold for the number of 3398 loss of frame seconds (lofs) within any given 15-minute 3399 performance data collection interval. If the value of 3400 loss of frame seconds in a particular 15-minute collection 3401 interval reaches/exceeds this value, a 3402 vdslPerfLofsThreshNotification notification will be 3403 generated. No more than one notification will be sent 3404 per interval." 3405 ::= { vdslLineAlarmConfProfileEntry 3 } 3407 vdslThresh15MinLoss OBJECT-TYPE 3408 SYNTAX HCPerfIntervalThreshold 3409 UNITS "seconds" 3410 MAX-ACCESS read-create 3411 STATUS current 3412 DESCRIPTION 3413 "This object configures the threshold for the number of 3414 loss of signal seconds (loss) within any given 15-minute 3415 performance data collection interval. If the value of 3416 loss of frame seconds in a particular 15-minute collection 3417 interval reaches/exceeds this value, a 3418 vdslPerfLossThreshNotification notification will be 3419 generated. One notification will be sent per interval 3420 per endpoint." 3421 ::= { vdslLineAlarmConfProfileEntry 4 } 3423 vdslThresh15MinLprs OBJECT-TYPE 3424 SYNTAX HCPerfIntervalThreshold 3425 UNITS "seconds" 3426 MAX-ACCESS read-create 3427 STATUS current 3428 DESCRIPTION 3429 "This object configures the threshold for the number of 3430 loss of power seconds (lprs) within any given 15-minute 3431 performance data collection interval. If the value of 3432 loss of frame seconds in a particular 15-minute collection 3433 interval reaches/exceeds this value, a 3434 vdslPerfLprsThreshNotification notification will be 3435 generated. No more than one notification will be sent 3436 per interval." 3437 ::= { vdslLineAlarmConfProfileEntry 5 } 3439 vdslThresh15MinESs OBJECT-TYPE 3440 SYNTAX HCPerfIntervalThreshold 3441 UNITS "seconds" 3442 MAX-ACCESS read-create 3443 STATUS current 3444 DESCRIPTION 3445 "This object configures the threshold for the number of 3446 errored seconds (ESs) within any given 15-minute 3447 performance data collection interval. If the value of 3448 errored seconds in a particular 15-minute collection 3449 interval reaches/exceeds this value, a 3450 vdslPerfESsThreshNotification notification will be 3451 generated. No more than one notification will be sent 3452 per interval." 3453 ::= { vdslLineAlarmConfProfileEntry 6 } 3455 vdslThresh15MinSESs OBJECT-TYPE 3456 SYNTAX HCPerfIntervalThreshold 3457 UNITS "seconds" 3458 MAX-ACCESS read-create 3459 STATUS current 3460 DESCRIPTION 3461 "This object configures the threshold for the number of 3462 severely errored seconds (SESs) within any given 15-minute 3463 performance data collection interval. If the value of 3464 severely errored seconds in a particular 15-minute 3465 collection interval reaches/exceeds this value, a 3466 vdslPerfSESsThreshNotification notification will be 3467 generated. No more than one notification will be sent 3468 per interval." 3469 ::= { vdslLineAlarmConfProfileEntry 7 } 3471 vdslThresh15MinUASs OBJECT-TYPE 3472 SYNTAX HCPerfIntervalThreshold 3473 UNITS "seconds" 3474 MAX-ACCESS read-create 3475 STATUS current 3476 DESCRIPTION 3477 "This object configures the threshold for the number of 3478 unavailable seconds (UASs) within any given 15-minute 3479 performance data collection interval. If the value of 3480 unavailable seconds in a particular 15-minute collection 3481 interval reaches/exceeds this value, a 3482 vdslPerfUASsThreshNotification notification will be 3483 generated. No more than one notification will be sent 3484 per interval." 3485 ::= { vdslLineAlarmConfProfileEntry 8 } 3487 vdslInitFailureNotificationEnable OBJECT-TYPE 3488 SYNTAX TruthValue 3489 MAX-ACCESS read-create 3490 STATUS current 3491 DESCRIPTION 3492 "This object specifies if a vdslInitFailureNotification 3493 notification will be generated if an initialization 3494 failure occurs." 3495 ::= { vdslLineAlarmConfProfileEntry 9 } 3497 vdslLineAlarmConfProfileRowStatus OBJECT-TYPE 3498 SYNTAX RowStatus 3499 MAX-ACCESS read-create 3500 STATUS current 3501 DESCRIPTION 3502 "This object is used to create a new row or modify or 3503 delete an existing row in this table. 3505 A profile activated by setting this object to `active'. 3506 When `active' is set, the system will validate the profile. 3508 Before a profile can be deleted or taken out of 3509 service, (by setting this object to `destroy' or 3510 `outOfService') it must be first unreferenced 3511 from all associated lines." 3512 ::= { vdslLineAlarmConfProfileEntry 10 } 3514 -- Notification definitions 3516 vdslNotifications OBJECT IDENTIFIER ::= { vdslLineMib 0 } 3518 vdslPerfLofsThreshNotification NOTIFICATION-TYPE 3519 OBJECTS { 3520 vdslPerfCurr15MinLofs, 3521 vdslThresh15MinLofs 3522 } 3523 STATUS current 3524 DESCRIPTION 3525 "Loss of Framing 15-minute interval threshold reached." 3526 ::= { vdslNotifications 1 } 3528 vdslPerfLossThreshNotification NOTIFICATION-TYPE 3529 OBJECTS { 3530 vdslPerfCurr15MinLoss, 3531 vdslThresh15MinLoss 3532 } 3533 STATUS current 3534 DESCRIPTION 3535 "Loss of Signal 15-minute interval threshold reached." 3536 ::= { vdslNotifications 2 } 3538 vdslPerfLprsThreshNotification NOTIFICATION-TYPE 3539 OBJECTS { 3540 vdslPerfCurr15MinLprs, 3541 vdslThresh15MinLprs 3542 } 3543 STATUS current 3544 DESCRIPTION 3545 "Loss of Power 15-minute interval threshold reached." 3546 ::= { vdslNotifications 3 } 3548 vdslPerfESsThreshNotification NOTIFICATION-TYPE 3549 OBJECTS { 3550 vdslPerfCurr15MinESs, 3551 vdslThresh15MinESs 3552 } 3553 STATUS current 3554 DESCRIPTION 3555 "Errored Seconds 15-minute interval threshold reached." 3556 ::= { vdslNotifications 4 } 3558 vdslPerfSESsThreshNotification NOTIFICATION-TYPE 3559 OBJECTS { 3560 vdslPerfCurr15MinSESs, 3561 vdslThresh15MinSESs 3562 } 3563 STATUS current 3564 DESCRIPTION 3565 "Severely Errored Seconds 15-minute interval threshold 3566 reached." 3567 ::= { vdslNotifications 5 } 3569 vdslPerfUASsThreshNotification NOTIFICATION-TYPE 3570 OBJECTS { 3571 vdslPerfCurr15MinUASs, 3572 vdslThresh15MinUASs 3573 } 3574 STATUS current 3575 DESCRIPTION 3576 "Unavailable Seconds 15-minute interval threshold reached." 3577 ::= { vdslNotifications 6 } 3579 vdslDownMaxSnrMgnExceededNotification NOTIFICATION-TYPE 3580 OBJECTS { 3581 vdslCurrSnrMgn, 3582 vdslLineConfDownstreamMaxSnrMgn 3583 } 3584 STATUS current 3585 DESCRIPTION 3586 "The downstream Signal to Noise Margin exceeded 3587 vdslLineConfDownstreamMaxSnrMgn. The object 3588 vdslCurrSnrMgn will contain the Signal to Noise 3589 margin as measured by the VTU-R." 3590 ::= { vdslNotifications 7 } 3592 vdslDownMinSnrMgnExceededNotification NOTIFICATION-TYPE 3593 OBJECTS { 3594 vdslCurrSnrMgn, 3595 vdslLineConfDownstreamMinSnrMgn 3596 } 3597 STATUS current 3598 DESCRIPTION 3599 "The downstream Signal to Noise Margin fell below 3600 vdslLineConfDownstreamMinSnrMgn. The object 3601 vdslCurrSnrMgn will contain the Signal to Noise 3602 margin as measured by the VTU-R." 3603 ::= { vdslNotifications 8 } 3605 vdslUpMaxSnrMgnExceededNotification NOTIFICATION-TYPE 3606 OBJECTS { 3607 vdslCurrSnrMgn, 3608 vdslLineConfUpstreamMaxSnrMgn 3609 } 3610 STATUS current 3611 DESCRIPTION 3612 "The upstream Signal to Noise Margin exceeded 3613 vdslLineConfDownstreamMaxSnrMgn. The object 3614 vdslCurrSnrMgn will contain the Signal to Noise 3615 margin as measured by the VTU-C." 3616 ::= { vdslNotifications 9 } 3618 vdslUpMinSnrMgnExceededNotification NOTIFICATION-TYPE 3619 OBJECTS { 3620 vdslCurrSnrMgn, 3621 vdslLineConfUpstreamMinSnrMgn 3622 } 3623 STATUS current 3624 DESCRIPTION 3625 "The upstream Signal to Noise Margin fell below 3626 vdslLineConfDownstreamMinSnrMgn. The object 3627 vdslCurrSnrMgn will contain the Signal to Noise 3628 margin as measured by the VTU-C." 3629 ::= { vdslNotifications 10 } 3631 vdslInitFailureNotification NOTIFICATION-TYPE 3632 OBJECTS { 3633 vdslCurrStatus 3634 } 3635 STATUS current 3636 DESCRIPTION 3637 "Vtu initialization failed. See vdslCurrStatus for 3638 potential reasons." 3639 ::= { vdslNotifications 11 } 3641 -- conformance information 3643 vdslConformance OBJECT IDENTIFIER ::= { vdslLineMib 3 } 3644 vdslGroups OBJECT IDENTIFIER ::= { vdslConformance 1 } 3645 vdslCompliances OBJECT IDENTIFIER ::= { vdslConformance 2 } 3647 vdslLineMibCompliance MODULE-COMPLIANCE 3648 STATUS current 3649 DESCRIPTION 3650 "The compliance statement for SNMP entities which 3651 manage VDSL interfaces." 3653 MODULE -- this module 3654 MANDATORY-GROUPS 3655 { 3656 vdslGroup 3657 } 3659 GROUP vdslMCMGroup 3660 DESCRIPTION 3661 "This group is mandatory for VDSL Lines which 3662 utilize multiple carrier modulation (MCM)." 3664 GROUP vdslSCMGroup 3665 DESCRIPTION 3666 "This group is mandatory for VDSL lines which 3667 utilize single carrier modulation (SCM)." 3669 ::= { vdslCompliances 1 } 3671 -- units of conformance 3673 vdslGroup OBJECT-GROUP 3674 OBJECTS 3675 { 3676 vdslLineCoding, 3677 vdslLineType, 3678 vdslLineConfProfile, 3679 vdslLineAlarmConfProfile, 3680 vdslPhysSide, 3681 vdslInvSerialNumber, 3682 vdslInvVendorID, 3683 vdslInvVersionNumber, 3684 vdslCurrSnrMgn, 3685 vdslCurrAtn, 3686 vdslCurrStatus, 3687 vdslCurrOutputPwr, 3688 vdslCurrAttainableRate, 3689 vdslChanInterleaveDelay, 3690 vdslChanCrcBlockLength, 3691 vdslPerfValidIntervals, 3692 vdslPerfInvalidIntervals, 3693 vdslPerfLofs, 3694 vdslPerfLoss, 3695 vdslPerfLprs, 3696 vdslPerfESs, 3697 vdslPerfSESs, 3698 vdslPerfUASs, 3699 vdslPerfInits, 3700 vdslPerfCurr15MinTimeElapsed, 3701 vdslPerfCurr15MinLofs, 3702 vdslPerfCurr15MinLoss, 3703 vdslPerfCurr15MinLprs, 3704 vdslPerfCurr15MinESs, 3705 vdslPerfCurr15MinSESs, 3706 vdslPerfCurr15MinUASs, 3707 vdslPerfCurr15MinInits, 3708 vdslPerf1DayValidIntervals, 3709 vdslPerf1DayInvalidIntervals, 3710 vdslPerfCurr1DayTimeElapsed, 3711 vdslPerfCurr1DayLofs, 3712 vdslPerfCurr1DayLoss, 3713 vdslPerfCurr1DayLprs, 3714 vdslPerfCurr1DayESs, 3715 vdslPerfCurr1DaySESs, 3716 vdslPerfCurr1DayUASs, 3717 vdslPerfCurr1DayInits, 3718 vdslIntervalLofs, 3719 vdslIntervalLoss, 3720 vdslIntervalLprs, 3721 vdslIntervalESs, 3722 vdslIntervalSESs, 3723 vdslIntervalUASs, 3724 vdslIntervalInits, 3725 vdsl1DayIntervalMoniSecs, 3726 vdsl1DayIntervalLofs, 3727 vdsl1DayIntervalLoss, 3728 vdsl1DayIntervalLprs, 3729 vdsl1DayIntervalESs, 3730 vdsl1DayIntervalSESs, 3731 vdsl1DayIntervalUASs, 3732 vdsl1DayIntervalInits, 3733 vdslChanPerfValidIntervals, 3734 vdslChanPerfInvalidIntervals, 3735 vdslChanCorrectedOctets, 3736 vdslChanUncorrectBlks, 3737 vdslChanPerfCurr15MinTimeElapsed, 3738 vdslChanPerfCurr15MinCorrectedOctets, 3739 vdslChanPerfCurr15MinUncorrectBlks, 3740 vdslChanPerf1DayValidIntervals, 3741 vdslChanPerf1DayInvalidIntervals, 3742 vdslChanPerfCurr1DayTimeElapsed, 3743 vdslChanPerfCurr1DayCorrectedOctets, 3744 vdslChanPerfCurr1DayUncorrectBlks, 3745 vdslChanIntervalCorrectedOctets, 3746 vdslChanIntervalUncorrectBlks, 3747 vdslChan1DayIntervalMoniSecs, 3748 vdslChan1DayIntervalCorrectedOctets, 3749 vdslChan1DayIntervalUncorrectBlks, 3750 vdslLineConfProfileIndex, 3751 vdslLineConfProfileName, 3752 vdslLineConfDownstreamMaxPwr, 3753 vdslLineConfUpstreamMaxPwr, 3754 vdslLineConfDownstreamMaxSnrMgn, 3755 vdslLineConfDownstreamMinSnrMgn, 3756 vdslLineConfDownstreamTargetSnrMgn, 3757 vdslLineConfUpstreamMaxSnrMgn, 3758 vdslLineConfUpstreamMinSnrMgn, 3759 vdslLineConfUpstreamTargetSnrMgn, 3760 vdslLineConfDownstreamFastMaxDataRate, 3761 vdslLineConfDownstreamFastMinDataRate, 3762 vdslLineConfDownstreamSlowMaxDataRate, 3763 vdslLineConfDownstreamSlowMinDataRate, 3764 vdslLineConfUpstreamFastMaxDataRate, 3765 vdslLineConfUpstreamFastMinDataRate, 3766 vdslLineConfUpstreamSlowMaxDataRate, 3767 vdslLineConfUpstreamSlowMinDataRate, 3768 vdslLineConfRateAdaptationRatio, 3769 vdslLineConfUpstreamDataRate, 3770 vdslLineConfDownstreamDataRate, 3771 vdslLineConfDownstreamMaxInterDelay, 3772 vdslLineConfUpstreamMaxInterDelay, 3773 vdslLineConfUpstreamPboControl, 3774 vdslLineConfDownstreamPboControl, 3775 vdslLineConfDeploymentScenario, 3776 vdslLineConfAdslOccupy, 3777 vdslLineConfApplicableStandard, 3778 vdslLineConfBandPlan, 3779 vdslLineConfBandPlanFx, 3780 vdslLineConfBandU0Usage, 3781 vdslLineConfUpstreamPsdTemplate, 3782 vdslLineConfDownstreamPsdTemplate, 3783 vdslLineConfProfileRowStatus, 3784 vdslLineAlarmConfProfileIndex, 3785 vdslLineAlarmConfProfileName, 3786 vdslThresh15MinLofs, 3787 vdslThresh15MinLoss, 3788 vdslThresh15MinLprs, 3789 vdslThresh15MinESs, 3790 vdslThresh15MinSESs, 3791 vdslThresh15MinUASs, 3792 vdslInitFailureNotificationEnable, 3793 vdslLineAlarmConfProfileRowStatus 3794 } 3795 STATUS current 3796 DESCRIPTION 3797 "A collection of objects providing information about 3798 a VDSL Line." 3799 ::= { vdslGroups 1 } 3801 vdslMCMGroup OBJECT-GROUP 3802 OBJECTS 3803 { 3804 vdslMCMConfProfileTxWindowLength, 3805 vdslMCMConfProfileRowStatus, 3806 vdslMCMConfProfileTxBandNumber, 3807 vdslMCMConfProfileTxBandStart, 3808 vdslMCMConfProfileTxBandStop, 3809 vdslMCMConfProfileTxBandRowStatus, 3810 vdslMCMConfProfileRxBandNumber, 3811 vdslMCMConfProfileRxBandStart, 3812 vdslMCMConfProfileRxBandStop, 3813 vdslMCMConfProfileRxBandRowStatus, 3814 vdslMCMConfProfileTxPSDNumber, 3815 vdslMCMConfProfileTxPSDTone, 3816 vdslMCMConfProfileTxPSDPSD, 3817 vdslMCMConfProfileTxPSDRowStatus, 3818 vdslMCMConfProfileMaxTxPSDNumber, 3819 vdslMCMConfProfileMaxTxPSDTone, 3820 vdslMCMConfProfileMaxTxPSDPSD, 3821 vdslMCMConfProfileMaxTxPSDRowStatus, 3822 vdslMCMConfProfileMaxRxPSDNumber, 3823 vdslMCMConfProfileMaxRxPSDTone, 3824 vdslMCMConfProfileMaxRxPSDPSD, 3825 vdslMCMConfProfileMaxRxPSDRowStatus 3826 } 3827 STATUS current 3828 DESCRIPTION 3829 "A collection of objects providing configuration 3830 information for a VDSL line based upon multiple carrier 3831 modulation modem." 3832 ::= { vdslGroups 2 } 3834 vdslSCMGroup OBJECT-GROUP 3835 OBJECTS 3836 { 3837 vdslSCMPhysBandSnrMgn, 3838 vdslSCMPhysBandAtn, 3839 vdslSCMConfProfileSide, 3840 vdslSCMConfProfileInterleaveDepth, 3841 vdslSCMConfProfileNumCarriers, 3842 vdslSCMConfProfileFastCodewordSize, 3843 vdslSCMConfProfileTransmitPSDMask, 3844 vdslSCMConfProfileVendorNotch1Start, 3845 vdslSCMConfProfileVendorNotch1Stop, 3846 vdslSCMConfProfileVendorNotch2Start, 3847 vdslSCMConfProfileVendorNotch2Stop, 3848 vdslSCMConfProfileFastFecSize, 3849 vdslSCMConfProfileSlowBlockSize, 3850 vdslSCMConfProfileRowStatus, 3851 vdslSCMConfProfileTxBandSide, 3852 vdslSCMConfProfileTxBandNumber, 3853 vdslSCMConfProfileTxBandTransmitPSDLevel, 3854 vdslSCMConfProfileTxBandSymbolRateProfile, 3855 vdslSCMConfProfileTxBandConstellationSize, 3856 vdslSCMConfProfileTxBandCenterFrequency, 3857 vdslSCMConfProfileTxBandRowStatus 3858 } 3859 STATUS current 3860 DESCRIPTION 3861 "A collection of objects providing configuration 3862 information for a VDSL line based upon single carrier 3863 modulation modem." 3864 ::= { vdslGroups 3 } 3866 vdslNotificationGroup NOTIFICATION-GROUP 3867 NOTIFICATIONS 3868 { 3869 vdslPerfLofsThreshNotification, 3870 vdslPerfLossThreshNotification, 3871 vdslPerfLprsThreshNotification, 3872 vdslPerfESsThreshNotification, 3873 vdslPerfSESsThreshNotification, 3874 vdslPerfUASsThreshNotification, 3875 vdslDownMaxSnrMgnExceededNotification, 3876 vdslDownMinSnrMgnExceededNotification, 3877 vdslUpMaxSnrMgnExceededNotification, 3878 vdslUpMinSnrMgnExceededNotification, 3879 vdslInitFailureNotification 3880 } 3881 STATUS current 3882 DESCRIPTION 3883 "This group supports notifications of significant 3884 conditions associated with VDSL Lines." 3885 ::= { vdslGroups 4 } 3887 END 3889 Normative References 3891 [ETSI2701] ETSI TS 101 270-1 V1.2.1 "Transmission and Multiplexing 3892 (TM); Access transmission systems on metallic access 3893 cables; Very high speed Digital Subscriber Line (VDSL); 3894 Part 1: Functional requirements", October 1999. 3896 [ETSI2702] ETSI TS 101 270-2 V1.1.1 "Transmission and Multiplexing 3897 (TM); Access transmission systems on metallic access 3898 cables; Very high speed Digital Subscriber Line (VDSL); 3899 Part 1: Transceiver specification", February 2001. 3901 [ITU9931] ITU-T G.993.1 "Very-high-speed digital subscriber line 3902 foundation", November 2001. 3904 [ITU9971] ITU-T G.997.1 "Physical layer management for Digital 3905 Subscriber Line (DSL) Transcievers", July 1999. 3907 [RFC1901] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 3908 "Introduction to Community-based SNMPv2", RFC 1901, 3909 January 1996. 3911 [RFC1905] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 3912 "Protocol Operations for Version 2 of the Simple Network 3913 Management Protocol (SNMPv2)", RFC 1905, January 1996. 3915 [RFC1906] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 3916 "Transport Mappings for Version 2 of the Simple Network 3917 Management Protocol (SNMPv2)", RFC 1906, January 1996. 3919 [RFC2119] Bradner, S., "Key Words for use in RFCs to Indicate 3920 Requirement Levels", RFC 2119, March 1997. 3922 [RFC2493] Tesink, K., "Textual Conventions for MIB Modules Using 3923 Performance History Based on 15 Minute Intervals", RFC 3924 2493, January 1999. 3926 [RFC2571] Harrington, D., Presuhn, R. and B. Wijnen, "An 3927 Architecture for Describing SNMP Management Frameworks", 3928 RFC 2571, April 1999. 3930 [RFC2572] Case, J., Harrington D., Presuhn, R. and B. Wijnen, 3931 "Message Processing and Dispatching for the Simple Network 3932 Management Protocol (SNMP)", RFC 2572, April 1999. 3934 [RFC2574] Blumenthal, U. and B. Wijnen, "User-based Security Model 3935 (USM) for version 3 of the Simple Network Management 3936 Protocol (SNMPv3)", RFC 2574, April 1999. 3938 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 3939 Rose, M. and S. Waldbusser, "Structure of Management 3940 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 3941 1999. 3943 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 3944 Rose, M. and S. Waldbusser, "Textual Conventions for 3945 SMIv2", STD 58, RFC 2579, April 1999. 3947 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 3948 Rose, M. and S. Waldbusser, "Conformance Statements for 3949 SMIv2", STD 58, RFC 2580, April 1999. 3951 [RFC2662] Bathrick, G. and F. Ly, "Definitions of Managed Objects 3952 for the ADSL Lines", RFC 2662, August 1999. 3954 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 3955 MIB", RFC 2863, June 2000. 3957 [T1E1311] ANSI T1E1.4/2001-311, "Very-high-bit-rate Digital 3958 Subscriber Line (VDSL) Metallic Interface, Part 1: 3959 Functional Requirements and Common Specification", February 3960 2001. 3962 [T1E1011] ANSI T1E1.4/2001-011R3, "VDSL Metallic Interface, Part 2: 3963 Technical Specification for a Single-Carrier Modulation 3964 (SCM) Transceiver", November 2001. 3966 [T1E1013] ANSI T1E1.4/2001-013R4, "VDSL Metallic Interface, Part 3: 3967 Technical Specification for a Multi-Carrier Modulation 3968 (MCM) Transceiver", November 2000. 3970 Informative References 3972 [RFC1155] Rose, M. and K. McCloghrie, "Structure and Identification 3973 of Management Information for TCP/IP-based Internets", STD 3974 16, RFC 1155, May 1990. 3976 [RFC1157] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple 3977 Network Management Protocol", STD 15, RFC 1157, May 1990. 3979 [RFC1212] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 3980 16, RFC 1212, March 1991. 3982 [RFC1215] Rose, M., "A Convention for Defining Traps for use with 3983 the SNMP", RFC 1215, March 1991. 3985 [RFC2570] Case, J., Mundy, R., Partain, D. and B. Stewart, 3986 "Introduction to Version 3 of the Internet-standard Network 3987 Management Framework", RFC 2570, April 1999. 3989 [RFC2573] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 Applications", 3990 RFC 2573, April 1999. 3992 [RFC2575] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based 3993 Access Control Model (VACM) for the Simple Network 3994 Management Protocol (SNMP)", RFC 2575, April 1999. 3996 Security Considerations 3998 There are a number of management objects defined in this MIB that 3999 have a MAX-ACCESS clause of read-write and/or read-create. Such 4000 objects may be considered sensitive or vulnerable in some network 4001 environments. The support for SET operations in a non-secure 4002 environment without proper protection can have a negative effect on 4003 network operations. 4005 VDSL layer connectivity from the Vtur will permit the subscriber 4006 to manipulate both the VDSL link directly and the VDSL embedded 4007 operations channel (EOC) for their own loop. For example, unchecked 4008 or unfiltered fluctuations initiated by the subscriber could generate 4009 sufficient notifications to potentially overwhelm either the 4010 management interface to the network or the element manager. 4012 For this reason, there are a number of managed objects in this MIB 4013 that may contain sensitive information. These are: 4015 vdslThresh15MinLofs 4016 vdslThresh15MinLoss 4017 vdslThresh15MinLprs 4018 vdslThresh15MinESs 4019 vdslThresh15MinSESs 4020 vdslThresh15MinUASs 4022 It is thus important to control even GET access to these objects and 4023 possibly to even encrypt the values of these objects when sending 4024 them over the network via SNMP. Not all versions of SNMP provide 4025 features for such a secure environment. 4027 Further, notifications generated by agents implementing this MIB 4028 will contain the above threshold information. 4030 SNMPv1 by itself is not a secure environment. Even if the network 4031 itself is secure (for example by using IPSec), even then, there is no 4032 control as to who on the secure network is allowed to access and 4033 GET/SET (read/change/create/delete) the objects in this MIB. 4035 It is recommended that the implementers consider the security 4036 features as provided by the SNMPv3 framework. Specifically, the use 4037 of the User-based Security Model RFC 2574 [12] and the View- 4038 based Access Control Model RFC 2575 [15] is recommended. 4040 It is then a customer/user responsibility to ensure that the SNMP 4041 entity giving access to an instance of this MIB, is properly 4042 configured to give access to the objects only to those principals 4043 (users) that have legitimate rights to indeed GET or SET 4044 (change/create/delete) them. 4046 IANA Considerations 4048 The VDSL-LINE-MIB MIB module requires the allocation of a single 4049 object identifier for its MODULE-IDENTITY. IANA should allocate 4050 this object identifier in the transmission subtree. 4052 Acknowledgments 4054 David Horton (CiTR) 4056 Moti Morgenstern (Inovia) 4058 Intellectual Property Notice 4060 The IETF takes no position regarding the validity or scope of any 4061 intellectual property or other rights that might be claimed to 4062 pertain to the implementation or use of the technology described in 4063 this document or the extent to which any license under such rights 4064 might or might not be available; neither does it represent that it 4065 has made any effort to identify any such rights. Information on the 4066 IETF's procedures with respect to rights in standards-track and 4067 standards-related documentation can be found in BCP-11. Copies of 4068 claims of rights made available for publication and any assurances of 4069 licenses to be made available, or the result of an attempt made to 4070 obtain a general license or permission for the use of such 4071 proprietary rights by implementors or users of this specification can 4072 be obtained from the IETF Secretariat. 4074 The IETF invites any interested party to bring to its attention any 4075 copyrights, patents or patent applications, or other proprietary 4076 rights which may cover technology that may be required to practice 4077 this standard. Please address the information to the IETF Executive 4078 Director. 4080 Authors' Addresses 4082 Bob Ray 4083 PESA Switching Systems, Inc. 4084 330-A Wynn Drive 4085 Huntsville, AL 35805 USA 4087 Phone: +1 256 726 9200 ext. 142 4088 Fax: +1 256 726 9271 4089 EMail: rray@pesa.com 4091 Rajesh Abbi 4092 Alcatel USA 4093 2912 Wake Forest Road 4094 Raleigh, NC 27609-7860 USA 4096 Phone: +1 919 850 6194 4097 EMail: Rajesh.Abbi@alcatel.com 4099 Full Copyright Statement 4101 Copyright (C) The Internet Society (2002). All Rights Reserved. 4103 This document and translations of it may be copied and furnished to 4104 others, and derivative works that comment on or otherwise explain it 4105 or assist in its implementation may be prepared, copied, published 4106 and distributed, in whole or in part, without restriction of any 4107 kind, provided that the above copyright notice and this paragraph are 4108 included on all such copies and derivative works. However, this 4109 document itself may not be modified in any way, such as by removing 4110 the copyright notice or references to the Internet Society or other 4111 Internet organizations, except as needed for the purpose of 4112 developing Internet standards in which case the procedures for 4113 copyrights defined in the Internet Standards process must be 4114 followed, or as required to translate it into languages other than 4115 English. 4117 The limited permissions granted above are perpetual and will not be 4118 revoked by the Internet Society or its successors or assigns. 4119 This document and the information contained herein is provided on an 4120 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 4121 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 4122 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 4123 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 4124 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.