idnits 2.17.1 draft-ietf-adslmib-vdsl-03.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 (ITU9931], RFC2580], ETSI2701,, ETSI2702,, [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 (June 2002) is 7985 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'PAGE 10' is mentioned on line 495, but not defined == Missing Reference: 'PAGE 11' is mentioned on line 550, but not defined == Missing Reference: 'PAGE 12' is mentioned on line 605, but not defined == Missing Reference: 'PAGE 13' is mentioned on line 660, but not defined == Missing Reference: 'PAGE 14' is mentioned on line 715, but not defined == Missing Reference: 'PAGE 15' is mentioned on line 770, but not defined == Missing Reference: 'PAGE 16' is mentioned on line 825, but not defined == Missing Reference: 'PAGE 17' is mentioned on line 879, but not defined == Missing Reference: 'PAGE 18' is mentioned on line 934, but not defined == Missing Reference: 'PAGE 19' is mentioned on line 988, but not defined == Missing Reference: 'PAGE 20' is mentioned on line 1043, but not defined == Missing Reference: 'PAGE 21' is mentioned on line 1098, but not defined == Missing Reference: 'PAGE 22' is mentioned on line 1153, but not defined == Missing Reference: 'PAGE 23' is mentioned on line 1208, but not defined == Missing Reference: 'PAGE 24' is mentioned on line 1263, but not defined == Missing Reference: 'PAGE 25' is mentioned on line 1318, but not defined == Missing Reference: 'PAGE 26' is mentioned on line 1373, but not defined == Missing Reference: 'PAGE 27' is mentioned on line 1428, but not defined == Missing Reference: 'PAGE 28' is mentioned on line 1483, but not defined == Missing Reference: 'PAGE 29' is mentioned on line 1537, but not defined == Missing Reference: 'PAGE 30' is mentioned on line 1592, but not defined == Missing Reference: 'PAGE 31' is mentioned on line 1647, but not defined == Missing Reference: 'PAGE 32' is mentioned on line 1702, but not defined == Missing Reference: 'PAGE 33' is mentioned on line 1756, but not defined == Missing Reference: 'PAGE 34' is mentioned on line 1811, but not defined == Missing Reference: 'PAGE 35' is mentioned on line 1866, but not defined == Missing Reference: 'PAGE 36' is mentioned on line 1921, but not defined == Missing Reference: 'PAGE 37' is mentioned on line 1976, but not defined == Missing Reference: 'PAGE 38' is mentioned on line 2031, but not defined == Missing Reference: 'PAGE 39' is mentioned on line 2086, but not defined == Missing Reference: 'PAGE 40' is mentioned on line 2141, but not defined == Missing Reference: 'PAGE 41' is mentioned on line 2196, but not defined == Missing Reference: 'PAGE 42' is mentioned on line 2251, but not defined == Missing Reference: 'PAGE 43' is mentioned on line 2306, but not defined == Missing Reference: 'PAGE 44' is mentioned on line 2360, but not defined == Missing Reference: 'PAGE 45' is mentioned on line 2414, but not defined == Missing Reference: 'PAGE 46' is mentioned on line 2469, but not defined == Missing Reference: 'PAGE 47' is mentioned on line 2524, but not defined == Missing Reference: 'PAGE 48' is mentioned on line 2579, but not defined == Missing Reference: 'PAGE 49' is mentioned on line 2634, but not defined == Missing Reference: 'PAGE 50' is mentioned on line 2689, but not defined == Missing Reference: 'PAGE 51' is mentioned on line 2743, but not defined == Missing Reference: 'PAGE 52' is mentioned on line 2798, but not defined == Missing Reference: 'PAGE 53' is mentioned on line 2853, but not defined == Missing Reference: 'PAGE 54' is mentioned on line 2908, but not defined == Missing Reference: 'PAGE 55' is mentioned on line 2963, but not defined == Missing Reference: 'PAGE 56' is mentioned on line 3018, but not defined == Missing Reference: 'PAGE 57' is mentioned on line 3073, but not defined == Missing Reference: 'PAGE 58' is mentioned on line 3127, but not defined == Missing Reference: 'PAGE 59' is mentioned on line 3182, but not defined == Missing Reference: 'PAGE 60' is mentioned on line 3236, but not defined == Missing Reference: 'PAGE 61' is mentioned on line 3290, but not defined == Missing Reference: 'PAGE 62' is mentioned on line 3345, but not defined == Missing Reference: 'PAGE 63' is mentioned on line 3400, but not defined == Missing Reference: 'PAGE 64' is mentioned on line 3455, but not defined == Missing Reference: 'PAGE 65' is mentioned on line 3510, but not defined == Missing Reference: 'PAGE 66' is mentioned on line 3565, but not defined == Missing Reference: 'PAGE 67' is mentioned on line 3619, but not defined == Missing Reference: 'PAGE 68' is mentioned on line 3675, but not defined -- Looks like a reference, but probably isn't: '12' on line 3694 -- Looks like a reference, but probably isn't: '15' on line 3695 == Missing Reference: 'PAGE 69' is mentioned on line 3730, but not defined == Missing Reference: 'PAGE 70' is mentioned on line 3785, but not defined == Unused Reference: 'ETSI2701' is defined on line 3545, but no explicit reference was found in the text == Unused Reference: 'ETSI2702' is defined on line 3550, but no explicit reference was found in the text == Unused Reference: 'ITU9931' is defined on line 3555, but no explicit reference was found in the text == Unused Reference: 'RFC2662' is defined on line 3604, but no explicit reference was found in the text == Unused Reference: 'T1E1311' is defined on line 3610, but no explicit reference was found in the text == Unused Reference: 'T1E1011' is defined on line 3615, but no explicit reference was found in the text == Unused Reference: 'T1E1013' is defined on line 3621, 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' ** 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 (~~), 70 warnings (==), 13 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 June 2002 7 Definitions of Managed Objects for Very High 8 Speed Digital Subscriber Lines (VDSL) 9 draft-ietf-adslmib-vdsl-03.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]. 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 ............................................. 10 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]. 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 ... 148 SYNTAX INTEGER { 149 ... 150 vdsl(97), -- Very H-speed Digital Subscrib. Loop 151 ... 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 Expires December 17, 2002 [PAGE 10] 496 All objects defined in this MIB which may be set (read-write or 497 read-create), should be stored persistently. Following is an 498 exhaustive list of these persistent objects: 500 vdslLineConfProfile 501 vdslLineAlarmConfProfile 502 vdslLineConfProfileIndex 503 vdslLineConfProfileName 504 vdslLineConfTargetSnrMgn 505 vdslLineConfUpstreamTxSpeed 506 vdslLineConfDownstreamTxSpeed 507 vdslLineConfUpstreamPboControl 508 vdslLineConfDownstreamPboControl 509 vdslLineConfDeploymentScenario 510 vdslLineConfAdslOccupy 511 vdslLineConfApplicableStandard 512 vdslLineConfBandPlan 513 vdslLineConfBandPlanFx 514 vdslLineConfBandU0Usage 515 vdslLineConfUpstreamPsdTemplate 516 vdslLineConfDownstreamPsdTemplate 517 vdslLineConfProfileRowStatus 518 vdslMCMConfProfileTxWindowLength 519 vdslMCMConfProfileRowStatus 520 vdslMCMConfProfileTxBandNumber 521 vdslMCMConfProfileTxBandStart 522 vdslMCMConfProfileTxBandStop 523 vdslMCMConfProfileTxBandRowStatus 524 vdslMCMConfProfileRxBandNumber 525 vdslMCMConfProfileRxBandStart 526 vdslMCMConfProfileRxBandStop 527 vdslMCMConfProfileRxBandRowStatus 528 vdslMCMConfProfileTxPSDNumber 529 vdslMCMConfProfileTxPSDTone 530 vdslMCMConfProfileTxPSDPSD 531 vdslMCMConfProfileTxPSDRowStatus 532 vdslMCMConfProfileMaxTxPSDNumber 533 vdslMCMConfProfileMaxTxPSDTone 534 vdslMCMConfProfileMaxTxPSDPSD 535 vdslMCMConfProfileMaxTxPSDRowStatus 536 vdslMCMConfProfileMaxRxPSDNumber 537 vdslMCMConfProfileMaxRxPSDTone 538 vdslMCMConfProfileMaxRxPSDPSD 539 vdslMCMConfProfileMaxRxPSDRowStatus 540 vdslSCMConfProfileInterleaveDepth 541 vdslSCMConfProfileFastCodewordSize 542 vdslSCMConfProfileTransmitPSDMask 543 vdslSCMConfProfileBands 544 vdslSCMConfProfileFastFecSize 545 vdslSCMConfProfileRowStatus 546 vdslSCMConfProfileTxBandNumber 547 vdslSCMConfProfileTxBandTransmitPSDLevel 548 vdslSCMConfProfileTxBandSymbolRateProfile 550 Expires December 17, 2002 [PAGE 11] 551 vdslSCMConfProfileTxBandConstellationSize 552 vdslSCMConfProfileTxBandCenterFrequency 553 vdslSCMConfProfileTxBandRowStatus 554 vdslLineAlarmConfProfileIndex 555 vdslLineAlarmConfProfileName 556 vdslThresh15MinLofs 557 vdslThresh15MinLoss 558 vdslThresh15MinLprs 559 vdslThresh15MinESs 560 vdslThresh15MinSESs 561 vdslThresh15MinUASs 562 vdslInitFailureNotificationEnable 563 vdslLineAlarmConfProfileRowStatus 565 It should also be noted that interface indices in this MIB are 566 maintained persistently. VACM data relating to these should be 567 stored persistently as well. 569 3. Conformance and Compliance 571 For VDSL lines, the following group is mandatory: 573 - vdslGroup 575 For MCM VDSL lines, the following group is optional: 577 - vdslSCMGroup 579 For SCM VDSL lines, the following group is optional: 581 - vdslMCMGroup 583 4. Definitions 585 VDSL-LINE-MIB DEFINITIONS ::= BEGIN 587 IMPORTS 589 MODULE-IDENTITY, 590 OBJECT-TYPE, 591 Counter64, 592 Gauge32, 593 Integer32, 594 Unsigned32, 595 NOTIFICATION-TYPE, 596 transmission FROM SNMPv2-SMI 597 TEXTUAL-CONVENTION, 598 RowStatus, 599 TruthValue FROM SNMPv2-TC 600 HCPerfCurrentCount, 601 HCPerfIntervalCount FROM HC-PerfHist-TC-MIB 602 MODULE-COMPLIANCE, 603 OBJECT-GROUP, 605 Expires December 17, 2002 [PAGE 12] 606 NOTIFICATION-GROUP FROM SNMPv2-CONF 607 ifIndex FROM IF-MIB 608 SnmpAdminString FROM SNMP-FRAMEWORK-MIB; 610 vdslMIB MODULE-IDENTITY 611 LAST-UPDATED "200204090000Z" -- April 9, 2002 612 ORGANIZATION "ADSLMIB Working Group" 613 CONTACT-INFO "WG-email: adslmib@ietf.org 614 Info: https://www1.ietf.org/mailman/listinfo/adslmib 616 Chair: Mike Sneed 617 Postal: P.O. Box 37324 618 Raleigh NC 27627-7324 619 Email: sneedmike@hotmail.com 621 Co-editor: Bob Ray 622 PESA Switching Systems, Inc. 623 Postal: 330-A Wynn Drive 624 Huntsville, AL 35805 USA 625 Email: rray@pesa.com 626 Phone: +1 256 726 9200 ext. 142 628 Co-editor: Rajesh Abbi 629 Alcatel USA 630 Postal: 2912 Wake Forest Road 631 Raleigh, NC 27609-7860 USA 632 Email: Rajesh.Abbi@alcatel.com 633 Phone: +1 919 850 6194 634 " 636 DESCRIPTION 637 "The MIB module defining objects for the management of a pair of 638 VDSL modems at each end of the VDSL line. Each such line has 639 an entry in an ifTable which may include multiple modem lines. 640 An agent may reside at either end of the VDSL line however the 641 MIB is designed to require no management communication between 642 them beyond that inherent in the low-level VDSL line protocol. 643 The agent may monitor and control this protocol for its needs. 645 VDSL lines may support optional Fast or Interleaved channels. 646 If these are supported, additional entries corresponding to the 647 supported channels must be created in the ifTable. Thus a VDSL 648 line that supports both channels will have three entries in the 649 ifTable, one for each physical, fast, and interleaved, whose 650 ifType values are equal to vdsl(97), fast(125), and 651 interleaved(124), respectively. The ifStackTable is used to 652 represent the relationship between the entries. 654 Naming Conventions: 655 Vtuc -- (VTUC) modem at near (Central) end of line 656 Vtur -- (VTUR) modem at Remote end of line 657 Vtu -- One of either Vtuc or Vtur 658 Curr -- Current 660 Expires December 17, 2002 [PAGE 13] 661 Prev -- Previous 662 Atn -- Attenuation 663 ES -- Errored Second. 664 LCS -- Line Code Specific 665 Lof -- Loss of Frame 666 Lol -- Loss of Link 667 Los -- Loss of Signal 668 Lpr -- Loss of Power 669 xxxs -- interval of Seconds in which xxx occurs 670 (e.g., xxx=Lof, Los, Lpr) 671 Max -- Maximum 672 Mgn -- Margin 673 Min -- Minimum 674 Psd -- Power Spectral Density 675 Snr -- Signal to Noise Ratio 676 Tx -- Transmit 677 Blks -- Blocks 678 " 679 REVISION "200111010000Z" -- November 1, 2001 680 DESCRIPTION "Initial draft." 682 REVISION "200203310000Z" -- March 31, 2002 683 DESCRIPTION "Added R. Abbi as co-author." 685 REVISION "200204090000Z" -- April 9, 2002 686 DESCRIPTION "Removed use of IMPLIED profile indices." 688 REVISION "200206160000Z" -- June 16, 2002 689 DESCRIPTION "Revised per input from DSL Forum." 691 ::= { transmission xxxx } 693 vdslLineMib OBJECT IDENTIFIER ::= { vdslMIB 1 } 694 vdslMibObjects OBJECT IDENTIFIER ::= { vdslLineMib 1 } 696 -- 697 -- textual conventions used in this MIB 698 -- 700 VdslLineCodingType ::= TEXTUAL-CONVENTION 701 STATUS current 702 DESCRIPTION 703 "This data type is used as the syntax for the VDSL 704 Line Code." 705 SYNTAX INTEGER 706 { 707 other(1), -- none of the following 708 mcm(2), -- Multiple Carrier Modulation 709 scm(3) -- Single Carrier Modulation 710 } 712 VdslLineEntity ::= TEXTUAL-CONVENTION 713 STATUS current 715 Expires December 17, 2002 [PAGE 14] 716 DESCRIPTION 717 "Identifies a modem as being either Vtuc or Vtur. A 718 VDSL line consists of two modems, a Vtuc and a Vtur." 719 SYNTAX INTEGER 720 { 721 vtuc(1), -- central site modem 722 vtur(2) -- remote site modem 723 } 725 -- 726 -- objects 727 -- 729 vdslLineTable OBJECT-TYPE 730 SYNTAX SEQUENCE OF VdslLineEntry 731 MAX-ACCESS not-accessible 732 STATUS current 733 DESCRIPTION 734 "This table includes common attributes describing 735 both ends of the line. It is required for all VDSL 736 physical interfaces. VDSL physical interfaces are 737 those ifEntries where ifType is equal to vdsl(97)." 738 ::= { vdslMibObjects 1 } 740 vdslLineEntry OBJECT-TYPE 741 SYNTAX VdslLineEntry 742 MAX-ACCESS not-accessible 743 STATUS current 744 DESCRIPTION "An entry in the vdslLineTable." 745 INDEX { ifIndex } 746 ::= { vdslLineTable 1 } 748 VdslLineEntry ::= 749 SEQUENCE 750 { 751 vdslLineCoding VdslLineCodingType, 752 vdslLineType INTEGER, 753 vdslLineConfProfile Integer32, 754 vdslLineAlarmConfProfile Integer32 755 } 757 vdslLineCoding OBJECT-TYPE 758 SYNTAX VdslLineCodingType 759 MAX-ACCESS read-only 760 STATUS current 761 DESCRIPTION 762 "Specifies the VDSL coding type used on this line." 763 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 764 ::= { vdslLineEntry 1 } 766 vdslLineType OBJECT-TYPE 767 SYNTAX INTEGER 768 { 770 Expires December 17, 2002 [PAGE 15] 771 noChannel(1), -- no channels exist 772 fastOnly(2), -- fast channel only 773 slowOnly(3), -- slow channel only 774 either(4), -- either fast or slow channel exist 775 both(5) -- both fast and slow channels exist 776 } 777 MAX-ACCESS read-only 778 STATUS current 779 DESCRIPTION 780 "Defines the type of VDSL physical line 781 entity that exists, by defining whether and how 782 the line is channelized. If the line is channelized, 783 the value will be other than noChannel(1). This 784 object defines which channel type(s) are supported. 786 In the case that the line is channelized, the manager 787 can use the ifStackTable to determine the ifIndex for 788 the associated channel(s)." 789 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 790 ::= { vdslLineEntry 2 } 792 vdslLineConfProfile OBJECT-TYPE 793 SYNTAX Integer32 794 MAX-ACCESS read-write 795 STATUS current 796 DESCRIPTION 797 "The value of this object identifies the row 798 in the VDSL Line Configuration Profile Table, 799 ( vdslLineConfProfileTable ), which applies for this 800 VDSL line, and channels if applicable." 801 ::= { vdslLineEntry 3 } 803 vdslLineAlarmConfProfile OBJECT-TYPE 804 SYNTAX Integer32 805 MAX-ACCESS read-write 806 STATUS current 807 DESCRIPTION 808 "The value of this object identifies the row in the VDSL 809 Line Alarm Configuration Profile Table, 810 ( vdslLineAlarmConfProfileTable ), which applies to this 811 VDSL line, and channels if applicable." 812 ::= { vdslLineEntry 4 } 814 vdslPhysTable OBJECT-TYPE 815 SYNTAX SEQUENCE OF VdslPhysEntry 816 MAX-ACCESS not-accessible 817 STATUS current 818 DESCRIPTION 819 "This table provides one row for each Vtu. Each row 820 contains the Physical Layer Parameters table for that 821 Vtu. VDSL physical interfaces are those ifEntries where 822 ifType is equal to vdsl(97)." 823 ::= { vdslMibObjects 2 } 825 Expires December 17, 2002 [PAGE 16] 826 vdslPhysEntry OBJECT-TYPE 827 SYNTAX VdslPhysEntry 828 MAX-ACCESS not-accessible 829 STATUS current 830 DESCRIPTION "An entry in the vdslPhysTable." 831 INDEX { ifIndex, 832 vdslPhysSide } 833 ::= { vdslPhysTable 1 } 835 VdslPhysEntry ::= 836 SEQUENCE 837 { 838 vdslPhysSide VdslLineEntity, 839 vdslInvSerialNumber SnmpAdminString, 840 vdslInvVendorID SnmpAdminString, 841 vdslInvVersionNumber SnmpAdminString, 842 vdslCurrSnrMgn Integer32, 843 vdslCurrAtn Gauge32, 844 vdslCurrStatus BITS, 845 vdslCurrOutputPwr Integer32, 846 vdslCurrAttainableRate Gauge32 847 } 849 vdslPhysSide OBJECT-TYPE 850 SYNTAX VdslLineEntity 851 MAX-ACCESS read-only 852 STATUS current 853 DESCRIPTION 854 "Identifies whether the modem is the Vtuc or Vtur." 855 ::= { vdslPhysEntry 1 } 857 vdslInvSerialNumber OBJECT-TYPE 858 SYNTAX SnmpAdminString(SIZE (0..32)) 859 MAX-ACCESS read-only 860 STATUS current 861 DESCRIPTION 862 "The vendor specific string that identifies the 863 vendor equipment." 864 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 865 ::= { vdslPhysEntry 2 } 867 vdslInvVendorID OBJECT-TYPE 868 SYNTAX SnmpAdminString (SIZE (0..16)) 869 MAX-ACCESS read-only 870 STATUS current 871 DESCRIPTION 872 "The vendor ID code is a copy of the binary vendor 873 identification field expressed as readable characters." 874 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 875 ::= { vdslPhysEntry 3 } 877 vdslInvVersionNumber OBJECT-TYPE 879 Expires December 17, 2002 [PAGE 17] 880 SYNTAX SnmpAdminString (SIZE (0..16)) 881 MAX-ACCESS read-only 882 STATUS current 883 DESCRIPTION 884 "The vendor specific version number sent by this Vtu 885 as part of the initialization messages. It is a copy 886 of the binary version number field expressed as 887 readable characters." 888 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 889 ::= { vdslPhysEntry 4 } 891 vdslCurrSnrMgn OBJECT-TYPE 892 SYNTAX Integer32(-640..640) 893 UNITS "0.25dB" 894 MAX-ACCESS read-only 895 STATUS current 896 DESCRIPTION 897 "Noise Margin as seen by this Vtu with respect to its 898 received signal in 0.25dB." 899 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 900 ::= { vdslPhysEntry 5 } 902 vdslCurrAtn OBJECT-TYPE 903 SYNTAX Gauge32(0..630) 904 UNITS "0.25dB" 905 MAX-ACCESS read-only 906 STATUS current 907 DESCRIPTION 908 "Measured difference in the total power transmitted by 909 the peer Vtu and the total power received by this Vtu." 910 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 911 ::= { vdslPhysEntry 6 } 913 vdslCurrStatus OBJECT-TYPE 914 SYNTAX BITS 915 { 916 noDefect(0), 917 lossOfFraming(1), 918 lossOfSignal(2), 919 lossOfPower(3), 920 lossOfSignalQuality(4), 921 lossOfLink(5), 922 dataInitFailure(6), 923 configInitFailure(7), 924 protocolInitFailure(8), 925 noPeerVtuPresent(9) 926 } 927 MAX-ACCESS read-only 928 STATUS current 929 DESCRIPTION 930 "Indicates current state of the Vtu line. This is a 931 bit-map of possible conditions. The various bit 932 positions are: 934 Expires December 17, 2002 [PAGE 18] 935 0 noDefect There no defects on the line 937 1 lossOfFraming Vtu failure due to not receiving 938 valid frame. 940 2 lossOfSignal Vtu failure due to not receiving 941 signal. 943 3 lossOfPower Vtu failure due to loss of power. 945 4 lossOfSignalQuality Loss of Signal Quality is declared 946 when the Noise Margin falls below 947 the Minimum Noise Margin, or the 948 bit-error-rate exceeds 10^-7. 950 5 lossOfLink Vtu failure due to inability to 951 link with peer Vtu. 953 6 dataInitFailure Vtu failure during initialization 954 due to bit errors corrupting 955 startup exchange data. 957 7 configInitFailure Vtu failure during initialization 958 due to peer Vtu not able to support 959 requested configuration. 961 8 protocolInitFailure Vtu failure during initialization 962 due to incompatible protocol used 963 by the peer Vtu. 965 9 noPeerVtuPresent Vtu failure during initialization 966 due to no activation sequence 967 detected from peer Vtu. 969 This is intended to supplement ifOperStatus." 970 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 971 ::= { vdslPhysEntry 7 } 973 vdslCurrOutputPwr OBJECT-TYPE 974 SYNTAX Integer32(-310..310) 975 UNITS "0.25dBm" 976 MAX-ACCESS read-only 977 STATUS current 978 DESCRIPTION 979 "Measured total output power transmitted by this ATU. 980 This is the measurement that was reported during 981 the last activation sequence." 982 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 983 ::= { vdslPhysEntry 8 } 985 vdslCurrAttainableRate OBJECT-TYPE 986 SYNTAX Gauge32 988 Expires December 17, 2002 [PAGE 19] 989 UNITS "bps" 990 MAX-ACCESS read-only 991 STATUS current 992 DESCRIPTION 993 "Indicates the maximum currently attainable data rate 994 by the Vtu. This value will be equal or greater than 995 the current line rate. Note that for SCM, the minimum 996 and maximum data rates are equal." 997 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 998 ::= { vdslPhysEntry 9 } 1000 vdslChanTable OBJECT-TYPE 1001 SYNTAX SEQUENCE OF VdslChanEntry 1002 MAX-ACCESS not-accessible 1003 STATUS current 1004 DESCRIPTION 1005 "This table provides one row for each Vtu channel. 1006 VDSL channel interfaces are those ifEntries where 1007 ifType is equal to interleave(124) or fast(125)." 1008 ::= { vdslMibObjects 3 } 1010 vdslChanEntry OBJECT-TYPE 1011 SYNTAX VdslChanEntry 1012 MAX-ACCESS not-accessible 1013 STATUS current 1014 DESCRIPTION 1015 "An entry in the vdslChanTable." 1016 INDEX { ifIndex, 1017 vdslPhysSide } 1018 ::= { vdslChanTable 1 } 1020 VdslChanEntry ::= 1021 SEQUENCE 1022 { 1023 vdslChanInterleaveDelay Gauge32, 1024 vdslChanCrcBlockLength Gauge32 1025 } 1027 vdslChanInterleaveDelay OBJECT-TYPE 1028 SYNTAX Gauge32 1029 UNITS "milli-seconds" 1030 MAX-ACCESS read-only 1031 STATUS current 1032 DESCRIPTION 1033 "Interleave Delay for this channel. 1035 Interleave delay applies only to the interleave 1036 (slow) channel and defines the mapping (relative 1037 spacing) between subsequent input bytes at the 1038 interleaver input and their placement in the bit 1039 stream at the interleaver output. Larger numbers 1040 provide greater separation between consecutive 1041 input bytes in the output bit stream allowing for 1043 Expires December 17, 2002 [PAGE 20] 1044 improved impulse noise immunity at the expense of 1045 payload latency. 1047 In the case where the ifType is fast(125), use 1048 noSuchObject." 1049 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1050 ::= { vdslChanEntry 1 } 1052 vdslChanCrcBlockLength OBJECT-TYPE 1053 SYNTAX Gauge32 1054 UNITS "byte" 1055 MAX-ACCESS read-only 1056 STATUS current 1057 DESCRIPTION 1058 "Indicates the length of the channel data-block 1059 on which the CRC operates." 1060 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1061 ::= { vdslChanEntry 2 } 1063 vdslPerfDataTable OBJECT-TYPE 1064 SYNTAX SEQUENCE OF VdslPerfDataEntry 1065 MAX-ACCESS not-accessible 1066 STATUS current 1067 DESCRIPTION 1068 "This table provides one row for each VDSL physical 1069 interface. VDSL physical interfaces are those ifEntries 1070 where ifType is equal to vdsl(97)." 1071 ::= { vdslMibObjects 4 } 1073 vdslPerfDataEntry OBJECT-TYPE 1074 SYNTAX VdslPerfDataEntry 1075 MAX-ACCESS not-accessible 1076 STATUS current 1077 DESCRIPTION 1078 "An entry in the vdslPerfDataTable." 1079 INDEX { ifIndex, 1080 vdslPhysSide } 1081 ::= { vdslPerfDataTable 1 } 1083 VdslPerfDataEntry ::= 1084 SEQUENCE 1085 { 1086 vdslPerfValidIntervals Unsigned32, 1087 vdslPerfInvalidIntervals Unsigned32, 1088 vdslPerfLofs Counter64, 1089 vdslPerfLoss Counter64, 1090 vdslPerfLprs Counter64, 1091 vdslPerfESs Counter64, 1092 vdslPerfSESs Counter64, 1093 vdslPerfUASs Counter64, 1094 vdslPerfInits Counter64, 1095 vdslPerfCurr15MinTimeElapsed Unsigned32, 1096 vdslPerfCurr15MinLofs HCPerfCurrentCount, 1098 Expires December 17, 2002 [PAGE 21] 1099 vdslPerfCurr15MinLoss HCPerfCurrentCount, 1100 vdslPerfCurr15MinLprs HCPerfCurrentCount, 1101 vdslPerfCurr15MinESs HCPerfCurrentCount, 1102 vdslPerfCurr15MinSESs HCPerfCurrentCount, 1103 vdslPerfCurr15MinUASs HCPerfCurrentCount, 1104 vdslPerfCurr15MinInits HCPerfCurrentCount, 1105 vdslPerf1DayValidIntervals Unsigned32, 1106 vdslPerf1DayInvalidIntervals Unsigned32, 1107 vdslPerfCurr1DayTimeElapsed Unsigned32, 1108 vdslPerfCurr1DayLofs Counter64, 1109 vdslPerfCurr1DayLoss Counter64, 1110 vdslPerfCurr1DayLprs Counter64, 1111 vdslPerfCurr1DayESs Counter64, 1112 vdslPerfCurr1DaySESs Counter64, 1113 vdslPerfCurr1DayUASs Counter64, 1114 vdslPerfCurr1DayInits Counter64 1115 } 1117 vdslPerfValidIntervals OBJECT-TYPE 1118 SYNTAX Unsigned32(0..96) 1119 MAX-ACCESS read-only 1120 STATUS current 1121 DESCRIPTION 1122 "Valid Intervals per xxxValidInterval definition 1123 found in HC-PerfHist-TC-MIB." 1124 ::= { vdslPerfDataEntry 1 } 1126 vdslPerfInvalidIntervals OBJECT-TYPE 1127 SYNTAX Unsigned32(0..96) 1128 MAX-ACCESS read-only 1129 STATUS current 1130 DESCRIPTION 1131 "Invalid Intervals per xxxInvalidInterval definition 1132 found in HC-PerfHist-TC-MIB." 1133 ::= { vdslPerfDataEntry 2 } 1135 vdslPerfLofs OBJECT-TYPE 1136 SYNTAX Counter64 1137 UNITS "seconds" 1138 MAX-ACCESS read-only 1139 STATUS current 1140 DESCRIPTION 1141 "Count of seconds since the unit was last reset that there 1142 was Loss of Framing." 1143 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1144 ::= { vdslPerfDataEntry 3 } 1146 vdslPerfLoss OBJECT-TYPE 1147 SYNTAX Counter64 1148 UNITS "seconds" 1149 MAX-ACCESS read-only 1150 STATUS current 1151 DESCRIPTION 1153 Expires December 17, 2002 [PAGE 22] 1154 "Count of seconds since the unit was last reset that there 1155 was Loss of Signal." 1156 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1157 ::= { vdslPerfDataEntry 4 } 1159 vdslPerfLprs OBJECT-TYPE 1160 SYNTAX Counter64 1161 UNITS "seconds" 1162 MAX-ACCESS read-only 1163 STATUS current 1164 DESCRIPTION 1165 "Count of seconds since the unit was last reset that there 1166 was Loss of Power." 1167 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1168 ::= { vdslPerfDataEntry 5 } 1170 vdslPerfESs OBJECT-TYPE 1171 SYNTAX Counter64 1172 UNITS "seconds" 1173 MAX-ACCESS read-only 1174 STATUS current 1175 DESCRIPTION 1176 "Count of Errored Seconds since the unit was last reset. 1177 An Errored Second is a one-second interval containing one 1178 or more crc anomalies, or one or more los or lof defects." 1179 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1180 ::= { vdslPerfDataEntry 6 } 1182 vdslPerfSESs OBJECT-TYPE 1183 SYNTAX Counter64 1184 UNITS "seconds" 1185 MAX-ACCESS read-only 1186 STATUS current 1187 DESCRIPTION 1188 "Count of Severely Errored Seconds since the unit was last 1189 reset." 1190 ::= { vdslPerfDataEntry 7 } 1192 vdslPerfUASs OBJECT-TYPE 1193 SYNTAX Counter64 1194 UNITS "seconds" 1195 MAX-ACCESS read-only 1196 STATUS current 1197 DESCRIPTION 1198 "Count of Unavailable Seconds since the unit was last 1199 reset." 1200 ::= { vdslPerfDataEntry 8 } 1202 vdslPerfInits OBJECT-TYPE 1203 SYNTAX Counter64 1204 MAX-ACCESS read-only 1205 STATUS current 1206 DESCRIPTION 1208 Expires December 17, 2002 [PAGE 23] 1209 "Count of the line initialization attempts since the unit 1210 was last reset. This count includes both successful and 1211 failed attempts." 1212 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1213 ::= { vdslPerfDataEntry 9 } 1215 vdslPerfCurr15MinTimeElapsed OBJECT-TYPE 1216 SYNTAX Unsigned32(0..899) 1217 UNITS "seconds" 1218 MAX-ACCESS read-only 1219 STATUS current 1220 DESCRIPTION 1221 "Total elapsed seconds in this interval." 1222 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1223 ::= { vdslPerfDataEntry 10 } 1225 vdslPerfCurr15MinLofs OBJECT-TYPE 1226 SYNTAX HCPerfCurrentCount 1227 UNITS "seconds" 1228 MAX-ACCESS read-only 1229 STATUS current 1230 DESCRIPTION 1231 "Count of seconds during this interval that there 1232 was Loss of Framing." 1233 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1234 ::= { vdslPerfDataEntry 11 } 1236 vdslPerfCurr15MinLoss OBJECT-TYPE 1237 SYNTAX HCPerfCurrentCount 1238 UNITS "seconds" 1239 MAX-ACCESS read-only 1240 STATUS current 1241 DESCRIPTION 1242 "Count of seconds during this interval that there 1243 was Loss of Signal." 1244 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1245 ::= { vdslPerfDataEntry 12 } 1247 vdslPerfCurr15MinLprs OBJECT-TYPE 1248 SYNTAX HCPerfCurrentCount 1249 UNITS "seconds" 1250 MAX-ACCESS read-only 1251 STATUS current 1252 DESCRIPTION 1253 "Count of seconds during this interval that there 1254 was Loss of Power." 1255 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1256 ::= { vdslPerfDataEntry 13 } 1258 vdslPerfCurr15MinESs OBJECT-TYPE 1259 SYNTAX HCPerfCurrentCount 1260 UNITS "seconds" 1261 MAX-ACCESS read-only 1263 Expires December 17, 2002 [PAGE 24] 1264 STATUS current 1265 DESCRIPTION 1266 "Count of Errored Seconds during this interval. An Errored 1267 Second is a one-second interval containing one or more crc 1268 anomalies, or one or more los or lof defects." 1269 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1270 ::= { vdslPerfDataEntry 14 } 1272 vdslPerfCurr15MinSESs OBJECT-TYPE 1273 SYNTAX HCPerfCurrentCount 1274 UNITS "seconds" 1275 MAX-ACCESS read-only 1276 STATUS current 1277 DESCRIPTION 1278 "Count of Severely Errored Seconds during this interval." 1279 ::= { vdslPerfDataEntry 15 } 1281 vdslPerfCurr15MinUASs OBJECT-TYPE 1282 SYNTAX HCPerfCurrentCount 1283 UNITS "seconds" 1284 MAX-ACCESS read-only 1285 STATUS current 1286 DESCRIPTION 1287 "Count of Unavailable Seconds during this interval." 1288 ::= { vdslPerfDataEntry 16 } 1290 vdslPerfCurr15MinInits OBJECT-TYPE 1291 SYNTAX HCPerfCurrentCount 1292 MAX-ACCESS read-only 1293 STATUS current 1294 DESCRIPTION 1295 "Count of the line initialization attempts during this 1296 interval. This count includes both successful and 1297 failed attempts." 1298 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1299 ::= { vdslPerfDataEntry 17 } 1301 vdslPerf1DayValidIntervals OBJECT-TYPE 1302 SYNTAX Unsigned32(0..30) 1303 MAX-ACCESS read-only 1304 STATUS current 1305 DESCRIPTION 1306 "Valid Intervals per xxxValidInterval definition 1307 found in HC-PerfHist-TC-MIB." 1308 ::= { vdslPerfDataEntry 18 } 1310 vdslPerf1DayInvalidIntervals OBJECT-TYPE 1311 SYNTAX Unsigned32(0..30) 1312 MAX-ACCESS read-only 1313 STATUS current 1314 DESCRIPTION 1315 "Invalid Intervals per xxxInvalidInterval definition 1316 found in HC-PerfHist-TC-MIB." 1318 Expires December 17, 2002 [PAGE 25] 1319 ::= { vdslPerfDataEntry 19 } 1321 vdslPerfCurr1DayTimeElapsed OBJECT-TYPE 1322 SYNTAX Unsigned32(0..86399) 1323 UNITS "seconds" 1324 MAX-ACCESS read-only 1325 STATUS current 1326 DESCRIPTION 1327 "Number of seconds that have elapsed since the beginning 1328 of the current 1-day interval." 1329 ::= { vdslPerfDataEntry 20 } 1331 vdslPerfCurr1DayLofs OBJECT-TYPE 1332 SYNTAX Counter64 1333 UNITS "seconds" 1334 MAX-ACCESS read-only 1335 STATUS current 1336 DESCRIPTION 1337 "Count of Loss of Framing (LOF) Seconds since the 1338 beginning of the current 1-day interval." 1339 ::= { vdslPerfDataEntry 21 } 1341 vdslPerfCurr1DayLoss OBJECT-TYPE 1342 SYNTAX Counter64 1343 UNITS "seconds" 1344 MAX-ACCESS read-only 1345 STATUS current 1346 DESCRIPTION 1347 "Count of Loss of Signal (LOS) Seconds since the beginning 1348 of the current 1-day interval." 1349 ::= { vdslPerfDataEntry 22 } 1351 vdslPerfCurr1DayLprs OBJECT-TYPE 1352 SYNTAX Counter64 1353 UNITS "seconds" 1354 MAX-ACCESS read-only 1355 STATUS current 1356 DESCRIPTION 1357 "Count of Loss of Power (LPR) Seconds since the beginning 1358 of the current 1-day interval." 1359 ::= { vdslPerfDataEntry 23 } 1361 vdslPerfCurr1DayESs OBJECT-TYPE 1362 SYNTAX Counter64 1363 UNITS "seconds" 1364 MAX-ACCESS read-only 1365 STATUS current 1366 DESCRIPTION 1367 "Count of Errored Seconds (ES) since the beginning 1368 of the current 1-day interval." 1369 ::= { vdslPerfDataEntry 24 } 1371 vdslPerfCurr1DaySESs OBJECT-TYPE 1373 Expires December 17, 2002 [PAGE 26] 1374 SYNTAX Counter64 1375 UNITS "seconds" 1376 MAX-ACCESS read-only 1377 STATUS current 1378 DESCRIPTION 1379 "Count of Severely Errored Seconds (SES) since the 1380 beginning of the current 1-day interval." 1381 ::= { vdslPerfDataEntry 25 } 1383 vdslPerfCurr1DayUASs OBJECT-TYPE 1384 SYNTAX Counter64 1385 UNITS "seconds" 1386 MAX-ACCESS read-only 1387 STATUS current 1388 DESCRIPTION 1389 "Count of Unavailable Seconds (UAS) since the beginning 1390 of the current 1-day interval." 1391 ::= { vdslPerfDataEntry 26 } 1393 vdslPerfCurr1DayInits OBJECT-TYPE 1394 SYNTAX Counter64 1395 UNITS "seconds" 1396 MAX-ACCESS read-only 1397 STATUS current 1398 DESCRIPTION 1399 "Count of the line initialization attempts since the 1400 beginning of the current 1-day interval. This count 1401 includes both successful and failed attempts." 1402 ::= { vdslPerfDataEntry 27 } 1404 vdslPerfIntervalTable OBJECT-TYPE 1405 SYNTAX SEQUENCE OF VdslPerfIntervalEntry 1406 MAX-ACCESS not-accessible 1407 STATUS current 1408 DESCRIPTION 1409 "This table provides one row for each Vtu performance 1410 data collection interval. VDSL physical interfaces are 1411 those ifEntries where ifType is equal to vdsl(97)." 1412 ::= { vdslMibObjects 5 } 1414 vdslPerfIntervalEntry OBJECT-TYPE 1415 SYNTAX VdslPerfIntervalEntry 1416 MAX-ACCESS not-accessible 1417 STATUS current 1418 DESCRIPTION 1419 "An entry in the vdslPerfIntervalTable." 1420 INDEX { ifIndex, 1421 vdslPhysSide, 1422 vdslIntervalNumber } 1423 ::= { vdslPerfIntervalTable 1 } 1425 VdslPerfIntervalEntry ::= 1426 SEQUENCE 1428 Expires December 17, 2002 [PAGE 27] 1429 { 1430 vdslIntervalNumber Unsigned32, 1431 vdslIntervalLofs HCPerfIntervalCount, 1432 vdslIntervalLoss HCPerfIntervalCount, 1433 vdslIntervalLprs HCPerfIntervalCount, 1434 vdslIntervalESs HCPerfIntervalCount, 1435 vdslIntervalSESs HCPerfIntervalCount, 1436 vdslIntervalUASs HCPerfIntervalCount, 1437 vdslIntervalInits HCPerfIntervalCount 1438 } 1440 vdslIntervalNumber OBJECT-TYPE 1441 SYNTAX Unsigned32(1..96) 1442 MAX-ACCESS not-accessible 1443 STATUS current 1444 DESCRIPTION 1445 "Performance Data Interval number 1 is the the most 1446 recent previous interval; interval 96 is 24 hours ago. 1447 Intervals 2..96 are optional." 1448 ::= { vdslPerfIntervalEntry 1 } 1450 vdslIntervalLofs OBJECT-TYPE 1451 SYNTAX HCPerfIntervalCount 1452 UNITS "seconds" 1453 MAX-ACCESS read-only 1454 STATUS current 1455 DESCRIPTION 1456 "Count of seconds in the interval when there was Loss 1457 of Framing." 1458 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1459 ::= { vdslPerfIntervalEntry 2 } 1461 vdslIntervalLoss OBJECT-TYPE 1462 SYNTAX HCPerfIntervalCount 1463 UNITS "seconds" 1464 MAX-ACCESS read-only 1465 STATUS current 1466 DESCRIPTION 1467 "Count of seconds in the interval when there was Loss 1468 of Signal." 1469 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1470 ::= { vdslPerfIntervalEntry 3 } 1472 vdslIntervalLprs OBJECT-TYPE 1473 SYNTAX HCPerfIntervalCount 1474 UNITS "seconds" 1475 MAX-ACCESS read-only 1476 STATUS current 1477 DESCRIPTION 1478 "Count of seconds in the interval when there was Loss 1479 of Power." 1480 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1481 ::= { vdslPerfIntervalEntry 4 } 1483 Expires December 17, 2002 [PAGE 28] 1484 vdslIntervalESs OBJECT-TYPE 1485 SYNTAX HCPerfIntervalCount 1486 UNITS "seconds" 1487 MAX-ACCESS read-only 1488 STATUS current 1489 DESCRIPTION 1490 "Count of Errored Seconds (ES) in the interval. An Errored 1491 Second is a one-second interval containing one or more crc 1492 anomalies, one or more los or lof defects." 1493 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1494 ::= { vdslPerfIntervalEntry 5 } 1496 vdslIntervalSESs OBJECT-TYPE 1497 SYNTAX HCPerfIntervalCount 1498 UNITS "seconds" 1499 MAX-ACCESS read-only 1500 STATUS current 1501 DESCRIPTION 1502 "Count of Severely Errored Seconds in the interval." 1503 ::= { vdslPerfIntervalEntry 6 } 1505 vdslIntervalUASs OBJECT-TYPE 1506 SYNTAX HCPerfIntervalCount 1507 UNITS "seconds" 1508 MAX-ACCESS read-only 1509 STATUS current 1510 DESCRIPTION 1511 "Count of Unavailable Seconds in the interval." 1512 ::= { vdslPerfIntervalEntry 7 } 1514 vdslIntervalInits OBJECT-TYPE 1515 SYNTAX HCPerfIntervalCount 1516 MAX-ACCESS read-only 1517 STATUS current 1518 DESCRIPTION 1519 "Count of the line initialization attempts during this 1520 interval. This count includes both successful and 1521 failed attempts." 1522 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1523 ::= { vdslPerfIntervalEntry 8 } 1525 vdsl1DayIntervalTable OBJECT-TYPE 1526 SYNTAX SEQUENCE OF Vdsl1DayIntervalEntry 1527 MAX-ACCESS not-accessible 1528 STATUS current 1529 DESCRIPTION 1530 "This table provides one row for each VDSL performance 1531 data collection interval. This table contains live data 1532 from equipment. As such, it is NOT persistent." 1533 ::= { vdslMibObjects 6 } 1535 vdsl1DayIntervalEntry OBJECT-TYPE 1537 Expires December 17, 2002 [PAGE 29] 1538 SYNTAX Vdsl1DayIntervalEntry 1539 MAX-ACCESS not-accessible 1540 STATUS current 1541 DESCRIPTION 1542 "An entry in the vdsl1DayIntervalTable." 1543 INDEX { ifIndex, 1544 vdslPhysSide, 1545 vdsl1DayIntervalNumber } 1546 ::= { vdsl1DayIntervalTable 1 } 1548 Vdsl1DayIntervalEntry ::= 1549 SEQUENCE 1550 { 1551 vdsl1DayIntervalNumber Unsigned32, 1552 vdsl1DayIntervalMoniSecs Unsigned32, 1553 vdsl1DayIntervalLofs Counter64, 1554 vdsl1DayIntervalLoss Counter64, 1555 vdsl1DayIntervalLprs Counter64, 1556 vdsl1DayIntervalESs Counter64, 1557 vdsl1DayIntervalSESs Counter64, 1558 vdsl1DayIntervalUASs Counter64, 1559 vdsl1DayIntervalInits Counter64 1560 } 1562 vdsl1DayIntervalNumber OBJECT-TYPE 1563 SYNTAX Unsigned32(1..30) 1564 MAX-ACCESS not-accessible 1565 STATUS current 1566 DESCRIPTION 1567 "History Data Interval number. Interval 1 is the the most 1568 recent previous day; interval 30 is 30 days ago. Intervals 1569 2..30 are optional." 1570 ::= { vdsl1DayIntervalEntry 1 } 1572 vdsl1DayIntervalMoniSecs OBJECT-TYPE 1573 SYNTAX Unsigned32(0..86400) 1574 UNITS "seconds" 1575 MAX-ACCESS read-only 1576 STATUS current 1577 DESCRIPTION 1578 "The amount of time in the 1-day interval over which the 1579 performance monitoring information is actually counted. 1580 This value will be the same as the interval duration except 1581 in a situation where performance monitoring data could not 1582 be collected for any reason." 1583 ::= { vdsl1DayIntervalEntry 2 } 1585 vdsl1DayIntervalLofs OBJECT-TYPE 1586 SYNTAX Counter64 1587 UNITS "seconds" 1588 MAX-ACCESS read-only 1589 STATUS current 1590 DESCRIPTION 1592 Expires December 17, 2002 [PAGE 30] 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 1647 Expires December 17, 2002 [PAGE 31] 1648 DESCRIPTION 1649 "Count of Unavailable Seconds (UAS) during the 1-day 1650 interval as measured by vdsl1DayIntervalMoniSecs." 1651 ::= { vdsl1DayIntervalEntry 8 } 1653 vdsl1DayIntervalInits OBJECT-TYPE 1654 SYNTAX Counter64 1655 UNITS "seconds" 1656 MAX-ACCESS read-only 1657 STATUS current 1658 DESCRIPTION 1659 "Count of the line initialization attempts during the 1660 1-day interval as measured by vdsl1DayIntervalMoniSecs. 1661 This count includes both successful and failed attempts." 1662 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1663 ::= { vdsl1DayIntervalEntry 9 } 1665 vdslChanPerfDataTable OBJECT-TYPE 1666 SYNTAX SEQUENCE OF VdslChanPerfDataEntry 1667 MAX-ACCESS not-accessible 1668 STATUS current 1669 DESCRIPTION 1670 "This table provides one row for each Vtu channel. 1671 VDSL channel interfaces are those ifEntries where 1672 ifType is equal to interleave(124) or fast(125)." 1673 ::= { vdslMibObjects 7 } 1675 vdslChanPerfDataEntry OBJECT-TYPE 1676 SYNTAX VdslChanPerfDataEntry 1677 MAX-ACCESS not-accessible 1678 STATUS current 1679 DESCRIPTION 1680 "An entry in the vdslChanPerfDataTable." 1681 INDEX { ifIndex, 1682 vdslPhysSide } 1683 ::= { vdslChanPerfDataTable 1 } 1685 VdslChanPerfDataEntry ::= 1686 SEQUENCE 1687 { 1688 vdslChanPerfValidIntervals Unsigned32, 1689 vdslChanPerfInvalidIntervals Unsigned32, 1690 vdslChanCorrectedOctets Counter64, 1691 vdslChanUncorrectBlks Counter64, 1692 vdslChanPerfCurr15MinTimeElapsed Unsigned32, 1693 vdslChanPerfCurr15MinCorrectedOctets HCPerfCurrentCount, 1694 vdslChanPerfCurr15MinUncorrectBlks HCPerfCurrentCount, 1695 vdslChanPerf1DayValidIntervals Unsigned32, 1696 vdslChanPerf1DayInvalidIntervals Unsigned32, 1697 vdslChanPerfCurr1DayTimeElapsed Unsigned32, 1698 vdslChanPerfCurr1DayCorrectedOctets HCPerfCurrentCount, 1699 vdslChanPerfCurr1DayUncorrectBlks HCPerfCurrentCount 1700 } 1702 Expires December 17, 2002 [PAGE 32] 1703 vdslChanPerfValidIntervals OBJECT-TYPE 1704 SYNTAX Unsigned32(0..96) 1705 MAX-ACCESS read-only 1706 STATUS current 1707 DESCRIPTION 1708 "Valid Intervals per xxxValidInterval definition 1709 found in HC-PerfHist-TC-MIB." 1710 ::= { vdslChanPerfDataEntry 1 } 1712 vdslChanPerfInvalidIntervals OBJECT-TYPE 1713 SYNTAX Unsigned32(0..96) 1714 MAX-ACCESS read-only 1715 STATUS current 1716 DESCRIPTION 1717 "Invalid Intervals per xxxInvalidInterval definition 1718 found in HC-PerfHist-TC-MIB." 1719 ::= { vdslChanPerfDataEntry 2 } 1721 vdslChanCorrectedOctets OBJECT-TYPE 1722 SYNTAX Counter64 1723 MAX-ACCESS read-only 1724 STATUS current 1725 DESCRIPTION 1726 "Count of corrected octets since the unit was last reset." 1727 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1728 ::= { vdslChanPerfDataEntry 3 } 1730 vdslChanUncorrectBlks OBJECT-TYPE 1731 SYNTAX Counter64 1732 MAX-ACCESS read-only 1733 STATUS current 1734 DESCRIPTION 1735 "Count of uncorrected blocks since the unit was last reset." 1736 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1737 ::= { vdslChanPerfDataEntry 4 } 1739 vdslChanPerfCurr15MinTimeElapsed OBJECT-TYPE 1740 SYNTAX Unsigned32(0..899) 1741 UNITS "seconds" 1742 MAX-ACCESS read-only 1743 STATUS current 1744 DESCRIPTION 1745 "Total elapsed seconds in this interval." 1746 ::= { vdslChanPerfDataEntry 5 } 1748 vdslChanPerfCurr15MinCorrectedOctets OBJECT-TYPE 1749 SYNTAX HCPerfCurrentCount 1750 MAX-ACCESS read-only 1751 STATUS current 1752 DESCRIPTION 1753 "Count of corrected octets in this interval." 1754 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1756 Expires December 17, 2002 [PAGE 33] 1757 ::= { vdslChanPerfDataEntry 6 } 1759 vdslChanPerfCurr15MinUncorrectBlks OBJECT-TYPE 1760 SYNTAX HCPerfCurrentCount 1761 MAX-ACCESS read-only 1762 STATUS current 1763 DESCRIPTION 1764 "Count of uncorrected blocks in this interval." 1765 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1766 ::= { vdslChanPerfDataEntry 7 } 1768 vdslChanPerf1DayValidIntervals OBJECT-TYPE 1769 SYNTAX Unsigned32(0..30) 1770 MAX-ACCESS read-only 1771 STATUS current 1772 DESCRIPTION 1773 "Valid Intervals per xxxValidInterval definition 1774 found in HC-PerfHist-TC-MIB." 1775 ::= { vdslChanPerfDataEntry 8 } 1777 vdslChanPerf1DayInvalidIntervals OBJECT-TYPE 1778 SYNTAX Unsigned32(0..30) 1779 MAX-ACCESS read-only 1780 STATUS current 1781 DESCRIPTION 1782 "Invalid Intervals per xxxInvalidInterval definition 1783 found in HC-PerfHist-TC-MIB." 1784 ::= { vdslChanPerfDataEntry 9 } 1786 vdslChanPerfCurr1DayTimeElapsed OBJECT-TYPE 1787 SYNTAX Unsigned32(0..86399) 1788 UNITS "seconds" 1789 MAX-ACCESS read-only 1790 STATUS current 1791 DESCRIPTION 1792 "Number of seconds that have elapsed since the beginning 1793 of the current 1-day interval." 1794 ::= { vdslChanPerfDataEntry 10 } 1796 vdslChanPerfCurr1DayCorrectedOctets OBJECT-TYPE 1797 SYNTAX HCPerfCurrentCount 1798 MAX-ACCESS read-only 1799 STATUS current 1800 DESCRIPTION 1801 "Count of corrected octets since the beginning of the 1802 current 1-day interva." 1803 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1804 ::= { vdslChanPerfDataEntry 11 } 1806 vdslChanPerfCurr1DayUncorrectBlks OBJECT-TYPE 1807 SYNTAX HCPerfCurrentCount 1808 MAX-ACCESS read-only 1809 STATUS current 1811 Expires December 17, 2002 [PAGE 34] 1812 DESCRIPTION 1813 "Count of uncorrected blocks since the beginning of the 1814 current 1-day interva." 1815 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1816 ::= { vdslChanPerfDataEntry 12 } 1818 vdslChanIntervalTable OBJECT-TYPE 1819 SYNTAX SEQUENCE OF VdslChanIntervalEntry 1820 MAX-ACCESS not-accessible 1821 STATUS current 1822 DESCRIPTION 1823 "This table provides one row for each Vtu channel data 1824 collection interval. VDSL channel interfaces are those 1825 ifEntries where ifType is equal to interleave(124) or 1826 fast(125)." 1827 ::= { vdslMibObjects 8 } 1829 vdslChanIntervalEntry OBJECT-TYPE 1830 SYNTAX VdslChanIntervalEntry 1831 MAX-ACCESS not-accessible 1832 STATUS current 1833 DESCRIPTION 1834 "An entry in the vdslChanIntervalTable." 1835 INDEX { ifIndex, 1836 vdslPhysSide, 1837 vdslChanIntervalNumber } 1838 ::= { vdslChanIntervalTable 1 } 1840 VdslChanIntervalEntry ::= 1841 SEQUENCE 1842 { 1843 vdslChanIntervalNumber Unsigned32, 1844 vdslChanIntervalCorrectedOctets HCPerfIntervalCount, 1845 vdslChanIntervalUncorrectBlks HCPerfIntervalCount 1846 } 1848 vdslChanIntervalNumber OBJECT-TYPE 1849 SYNTAX Unsigned32(0..96) 1850 MAX-ACCESS not-accessible 1851 STATUS current 1852 DESCRIPTION 1853 "Performance Data Interval number 1 is the the most 1854 recent previous interval; interval 96 is 24 hours ago. 1855 Intervals 2..96 are optional." 1856 ::= { vdslChanIntervalEntry 1 } 1858 vdslChanIntervalCorrectedOctets OBJECT-TYPE 1859 SYNTAX HCPerfIntervalCount 1860 MAX-ACCESS read-only 1861 STATUS current 1862 DESCRIPTION 1863 "Count of corrected octets in this interval." 1864 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1866 Expires December 17, 2002 [PAGE 35] 1867 ::= { vdslChanIntervalEntry 2 } 1869 vdslChanIntervalUncorrectBlks OBJECT-TYPE 1870 SYNTAX HCPerfIntervalCount 1871 MAX-ACCESS read-only 1872 STATUS current 1873 DESCRIPTION 1874 "Count of uncorrected blocks in this interval." 1875 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1876 ::= { vdslChanIntervalEntry 3 } 1878 vdslChan1DayIntervalTable OBJECT-TYPE 1879 SYNTAX SEQUENCE OF VdslChan1DayIntervalEntry 1880 MAX-ACCESS not-accessible 1881 STATUS current 1882 DESCRIPTION 1883 "This table provides one row for each VDSL performance 1884 data collection interval. This table contains live data 1885 from equipment. As such, it is NOT persistent." 1886 ::= { vdslMibObjects 9 } 1888 vdslChan1DayIntervalEntry OBJECT-TYPE 1889 SYNTAX VdslChan1DayIntervalEntry 1890 MAX-ACCESS not-accessible 1891 STATUS current 1892 DESCRIPTION 1893 "An entry in the vdslChan1DayIntervalTable." 1894 INDEX { ifIndex, 1895 vdslPhysSide, 1896 vdslChan1DayIntervalNumber } 1897 ::= { vdslChan1DayIntervalTable 1 } 1899 VdslChan1DayIntervalEntry ::= 1900 SEQUENCE 1901 { 1902 vdslChan1DayIntervalNumber Unsigned32, 1903 vdslChan1DayIntervalMoniSecs Unsigned32, 1904 vdslChan1DayIntervalCorrectedOctets HCPerfCurrentCount, 1905 vdslChan1DayIntervalUncorrectBlks HCPerfCurrentCount 1906 } 1908 vdslChan1DayIntervalNumber OBJECT-TYPE 1909 SYNTAX Unsigned32(1..30) 1910 MAX-ACCESS not-accessible 1911 STATUS current 1912 DESCRIPTION 1913 "History Data Interval number. Interval 1 is the the most 1914 recent previous day; interval 30 is 30 days ago. Intervals 1915 2..30 are optional." 1916 ::= { vdslChan1DayIntervalEntry 1 } 1918 vdslChan1DayIntervalMoniSecs OBJECT-TYPE 1919 SYNTAX Unsigned32(0..86400) 1921 Expires December 17, 2002 [PAGE 36] 1922 UNITS "seconds" 1923 MAX-ACCESS read-only 1924 STATUS current 1925 DESCRIPTION 1926 "The amount of time in the 1-day interval over which the 1927 performance monitoring information is actually counted. 1928 This value will be the same as the interval duration except 1929 in a situation where performance monitoring data could not 1930 be collected for any reason." 1931 ::= { vdslChan1DayIntervalEntry 2 } 1933 vdslChan1DayIntervalCorrectedOctets OBJECT-TYPE 1934 SYNTAX HCPerfCurrentCount 1935 MAX-ACCESS read-only 1936 STATUS current 1937 DESCRIPTION 1938 "Count of corrected octets in this interval." 1939 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1940 ::= { vdslChan1DayIntervalEntry 3 } 1942 vdslChan1DayIntervalUncorrectBlks OBJECT-TYPE 1943 SYNTAX HCPerfCurrentCount 1944 MAX-ACCESS read-only 1945 STATUS current 1946 DESCRIPTION 1947 "Count of uncorrected blocks in this interval." 1948 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1949 ::= { vdslChan1DayIntervalEntry 4 } 1951 -- 1952 -- SCM physical band status 1953 -- 1955 vdslSCMPhysBandTable OBJECT-TYPE 1956 SYNTAX SEQUENCE OF VdslSCMPhysBandEntry 1957 MAX-ACCESS not-accessible 1958 STATUS current 1959 DESCRIPTION 1960 "This table provides one row for each SCM Vtu band." 1961 ::= { vdslMibObjects 10 } 1963 vdslSCMPhysBandEntry OBJECT-TYPE 1964 SYNTAX VdslSCMPhysBandEntry 1965 MAX-ACCESS not-accessible 1966 STATUS current 1967 DESCRIPTION 1968 "An entry in the vdslSCMPhysBandTable." 1969 INDEX { ifIndex, 1970 vdslPhysSide, 1971 vdslSCMPhysTxBandNumber } 1972 ::= { vdslSCMPhysBandTable 1 } 1974 VdslSCMPhysBandEntry ::= 1976 Expires December 17, 2002 [PAGE 37] 1977 SEQUENCE 1978 { 1979 vdslSCMPhysTxBandNumber INTEGER, 1980 vdslSCMPhysBandSnrMgn Integer32, 1981 vdslSCMPhysBandAtn Unsigned32 1982 } 1984 vdslSCMPhysTxBandNumber OBJECT-TYPE 1985 SYNTAX INTEGER 1986 { 1987 band1(1), 1988 band2(2), 1989 upstreamU0(3) 1990 } 1991 MAX-ACCESS not-accessible 1992 STATUS current 1993 DESCRIPTION 1994 "The SCM transmit band number for this entry." 1995 ::= { vdslSCMPhysBandEntry 1 } 1997 vdslSCMPhysBandSnrMgn OBJECT-TYPE 1998 SYNTAX Integer32(-127..127) 1999 UNITS "0.25 dB" 2000 MAX-ACCESS read-only 2001 STATUS current 2002 DESCRIPTION 2003 "Noise margin as seen by this Vtu and band with respect 2004 to its received signal in 0.25 dB." 2005 ::= { vdslSCMPhysBandEntry 2 } 2007 vdslSCMPhysBandAtn OBJECT-TYPE 2008 SYNTAX Unsigned32(0..255) 2009 UNITS "0.25 dB" 2010 MAX-ACCESS read-only 2011 STATUS current 2012 DESCRIPTION 2013 "Measured difference in the total power transmitted by 2014 the peer Vtu on this band and the total power received 2015 by this Vtu on this band in 0.25 dB." 2016 ::= { vdslSCMPhysBandEntry 3 } 2018 -- 2019 -- profile tables 2020 -- 2022 vdslLineConfProfileTable OBJECT-TYPE 2023 SYNTAX SEQUENCE OF VdslLineConfProfileEntry 2024 MAX-ACCESS not-accessible 2025 STATUS current 2026 DESCRIPTION 2027 "This table contains information on the VDSL line 2028 configuration. One entry in this table reflects a 2029 profile defined by a manager which can be used to 2031 Expires December 17, 2002 [PAGE 38] 2032 configure the VDSL line." 2033 ::= { vdslMibObjects 11 } 2035 vdslLineConfProfileEntry OBJECT-TYPE 2036 SYNTAX VdslLineConfProfileEntry 2037 MAX-ACCESS not-accessible 2038 STATUS current 2039 DESCRIPTION 2040 "Each entry consists of a list of parameters that 2041 represents the configuration of a VDSL line. A 2042 default profile with an index of 1 will always exist 2043 and its parameters will be set to vendor specific 2044 values, unless otherwise specified in this document." 2045 INDEX { vdslLineConfProfileIndex } 2046 ::= { vdslLineConfProfileTable 1 } 2048 VdslLineConfProfileEntry ::= 2049 SEQUENCE 2050 { 2051 vdslLineConfProfileIndex Unsigned32, 2052 vdslLineConfProfileName SnmpAdminString, 2053 vdslLineConfTargetSnrMgn Unsigned32, 2054 vdslLineConfUpstreamTxSpeed Unsigned32, 2055 vdslLineConfDownstreamTxSpeed Unsigned32, 2056 vdslLineConfUpstreamPboControl INTEGER, 2057 vdslLineConfDownstreamPboControl INTEGER, 2058 vdslLineConfDeploymentScenario INTEGER, 2059 vdslLineConfAdslOccupy TruthValue, 2060 vdslLineConfApplicableStandard INTEGER, 2061 vdslLineConfBandPlan INTEGER, 2062 vdslLineConfBandPlanFx Unsigned32, 2063 vdslLineConfBandU0Usage INTEGER, 2064 vdslLineConfUpstreamPsdTemplate INTEGER, 2065 vdslLineConfDownstreamPsdTemplate INTEGER, 2066 vdslLineConfProfileRowStatus RowStatus 2067 } 2069 vdslLineConfProfileIndex OBJECT-TYPE 2070 SYNTAX Unsigned32 2071 MAX-ACCESS read-create 2072 STATUS current 2073 DESCRIPTION 2074 "This object identifies a row in this table. A 2075 default profile with an index of 1 MUST always 2076 exist and its parameters will be set to vendor 2077 specific values, unless otherwise specified in 2078 this document." 2079 ::= { vdslLineConfProfileEntry 1 } 2081 vdslLineConfProfileName OBJECT-TYPE 2082 SYNTAX SnmpAdminString (SIZE (1..32)) 2083 MAX-ACCESS read-create 2084 STATUS current 2086 Expires December 17, 2002 [PAGE 39] 2087 DESCRIPTION 2088 "The name for this profile as specified by a user." 2089 ::= { vdslLineConfProfileEntry 2 } 2091 vdslLineConfTargetSnrMgn OBJECT-TYPE 2092 SYNTAX Unsigned32(0..310) 2093 UNITS "0.25dB" 2094 MAX-ACCESS read-create 2095 STATUS current 2096 DESCRIPTION 2097 "Configured Target Signal/Noise Margin. This is the 2098 Noise Margin the modems must achieve with a BER of 10-7 2099 or better to successfully complete initialization." 2100 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 2101 ::= { vdslLineConfProfileEntry 3 } 2103 vdslLineConfUpstreamTxSpeed OBJECT-TYPE 2104 SYNTAX Unsigned32 2105 UNITS "bits per second" 2106 MAX-ACCESS read-create 2107 STATUS current 2108 DESCRIPTION 2109 "Upstream transmit speed for this line." 2110 ::= { vdslLineConfProfileEntry 4 } 2112 vdslLineConfDownstreamTxSpeed OBJECT-TYPE 2113 SYNTAX Unsigned32 2114 UNITS "bits per second" 2115 MAX-ACCESS read-create 2116 STATUS current 2117 DESCRIPTION 2118 "Downstream transmit speed for this line." 2119 ::= { vdslLineConfProfileEntry 5 } 2121 vdslLineConfUpstreamPboControl OBJECT-TYPE 2122 SYNTAX INTEGER 2123 { 2124 disabled(1), 2125 enabled(2) 2126 } 2127 MAX-ACCESS read-create 2128 STATUS current 2129 DESCRIPTION 2130 "Upstream power backoff (PBO) control for this 2131 line. For modems which do not support upstream 2132 PBO control, this object MUST be fixed at disabled(1)." 2133 ::= { vdslLineConfProfileEntry 6 } 2135 vdslLineConfDownstreamPboControl OBJECT-TYPE 2136 SYNTAX INTEGER 2137 { 2138 disabled(1), 2139 enabled(2) 2141 Expires December 17, 2002 [PAGE 40] 2142 } 2143 MAX-ACCESS read-create 2144 STATUS current 2145 DESCRIPTION 2146 "Downstream power backoff (PBO) control for this 2147 line. For modems which do not support downstream 2148 PBO control, this object MUST be fixed at disabled(1)." 2149 ::= { vdslLineConfProfileEntry 7 } 2151 vdslLineConfDeploymentScenario OBJECT-TYPE 2152 SYNTAX INTEGER 2153 { 2154 fttCab(1), 2155 fttEx(2), 2156 other(3) 2157 } 2158 MAX-ACCESS read-create 2159 STATUS current 2160 DESCRIPTION 2161 "The VDSL line deployment scenario. When using 2162 fttCab(1), the VTU-C is located in a street cabinet. 2163 When using fttEx(2), the VTU-C is located at the 2164 central office." 2165 ::= { vdslLineConfProfileEntry 8 } 2167 vdslLineConfAdslOccupy OBJECT-TYPE 2168 SYNTAX TruthValue 2169 MAX-ACCESS read-create 2170 STATUS current 2171 DESCRIPTION 2172 "Indicates if the VDSL line can occupy the ADSL 2173 frequency range." 2174 ::= { vdslLineConfProfileEntry 9 } 2176 vdslLineConfApplicableStandard OBJECT-TYPE 2177 SYNTAX INTEGER 2178 { 2179 ansi(1), 2180 etsi(2), 2181 itu(3), 2182 other(4) 2183 } 2184 MAX-ACCESS read-create 2185 STATUS current 2186 DESCRIPTION 2187 "The VDSL standard to be used for the line." 2188 ::= { vdslLineConfProfileEntry 10 } 2190 vdslLineConfBandPlan OBJECT-TYPE 2191 SYNTAX INTEGER 2192 { 2193 bandPlan997(1), 2194 bandPlan998(2), 2196 Expires December 17, 2002 [PAGE 41] 2197 bandPlanFx(3), 2198 other(4) 2199 } 2200 MAX-ACCESS read-create 2201 STATUS current 2202 DESCRIPTION 2203 "The VDSL band plan to be used for the line." 2204 ::= { vdslLineConfProfileEntry 11 } 2206 vdslLineConfBandPlanFx OBJECT-TYPE 2207 SYNTAX Unsigned32 2208 UNITS "kHz" 2209 MAX-ACCESS read-create 2210 STATUS current 2211 DESCRIPTION 2212 "The frequency limit between bands D2 and U2 when 2213 vdslLineConfBandPlan is set to bandPlanFx(3)." 2214 ::= { vdslLineConfProfileEntry 12 } 2216 vdslLineConfBandU0Usage OBJECT-TYPE 2217 SYNTAX INTEGER 2218 { 2219 unused(1), 2220 upstream(2), 2221 downstream(3) 2222 } 2223 MAX-ACCESS read-create 2224 STATUS current 2225 DESCRIPTION 2226 "Defines the VDSL link use of the frequency range 2227 [25kHz - 138kHz] (U0)." 2228 ::= { vdslLineConfProfileEntry 13 } 2230 vdslLineConfUpstreamPsdTemplate OBJECT-TYPE 2231 SYNTAX INTEGER 2232 { 2233 templateMask1(1), 2234 templateMask2(2) 2235 } 2236 MAX-ACCESS read-create 2237 STATUS current 2238 DESCRIPTION 2239 "The upstream PSD template to be used for the line." 2240 ::= { vdslLineConfProfileEntry 14 } 2242 vdslLineConfDownstreamPsdTemplate OBJECT-TYPE 2243 SYNTAX INTEGER 2244 { 2245 templateMask1(1), 2246 templateMask2(2) 2247 } 2248 MAX-ACCESS read-create 2249 STATUS current 2251 Expires December 17, 2002 [PAGE 42] 2252 DESCRIPTION 2253 "The downstream PSD template to be used for the line." 2254 ::= { vdslLineConfProfileEntry 15 } 2256 vdslLineConfProfileRowStatus OBJECT-TYPE 2257 SYNTAX RowStatus 2258 MAX-ACCESS read-create 2259 STATUS current 2260 DESCRIPTION 2261 "This object is used to create a new row or modify or 2262 delete an existing row in this table. 2264 A profile activated by setting this object to `active'. 2265 When `active' is set, the system will validate the profile. 2267 Before a profile can be deleted or taken out of 2268 service, (by setting this object to `destroy' or 2269 `outOfService') it must be first unreferenced 2270 from all associated lines." 2271 ::= { vdslLineConfProfileEntry 16 } 2273 -- 2274 -- Multiple carrier modulation (MCM) configuration profile tables 2275 -- 2277 vdslLineMCMConfProfileTable OBJECT-TYPE 2278 SYNTAX SEQUENCE OF VdslLineMCMConfProfileEntry 2279 MAX-ACCESS not-accessible 2280 STATUS current 2281 DESCRIPTION 2282 "This table contains information on the VDSL line 2283 configuration. One entry in this table reflects a 2284 profile defined by a manager which can be used to 2285 configure the VDSL line. 2287 This table MUST be implemented for multiple carrier VDSL 2288 lines. This table MUST NOT be implemented for Single 2289 carrier VDSL lines." 2290 ::= { vdslMibObjects 12 } 2292 vdslLineMCMConfProfileEntry OBJECT-TYPE 2293 SYNTAX VdslLineMCMConfProfileEntry 2294 MAX-ACCESS not-accessible 2295 STATUS current 2296 DESCRIPTION 2297 "Each entry consists of a list of parameters that 2298 represents the configuration of a multiple carrier 2299 modulation VDSL modem. A default profile with an 2300 index of 1 will always exist and its parameters will 2301 be set to vendor specific values, unless otherwise 2302 specified in this document." 2303 INDEX { vdslLineConfProfileIndex } 2304 ::= { vdslLineMCMConfProfileTable 1 } 2306 Expires December 17, 2002 [PAGE 43] 2307 VdslLineMCMConfProfileEntry ::= 2308 SEQUENCE 2309 { 2310 vdslMCMConfProfileTxWindowLength Unsigned32, 2311 vdslMCMConfProfileRowStatus RowStatus 2312 } 2314 vdslMCMConfProfileTxWindowLength OBJECT-TYPE 2315 SYNTAX Unsigned32(1..255) 2316 UNITS "samples" 2317 MAX-ACCESS read-create 2318 STATUS current 2319 DESCRIPTION 2320 "Specifies the length of the transmit window, counted 2321 in samples at the sampling rate corresponding to the 2322 negotiated value of N." 2323 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 2324 ::= { vdslLineMCMConfProfileEntry 1 } 2326 vdslMCMConfProfileRowStatus OBJECT-TYPE 2327 SYNTAX RowStatus 2328 MAX-ACCESS read-create 2329 STATUS current 2330 DESCRIPTION 2331 "This object is used to create a new row or modify or 2332 delete an existing row in this table. 2334 A profile activated by setting this object to `active'. 2335 When `active' is set, the system will validate the profile. 2337 Before a profile can be deleted or taken out of 2338 service, (by setting this object to `destroy' or 2339 `outOfService') it must be first unreferenced 2340 from all associated lines." 2341 ::= { vdslLineMCMConfProfileEntry 2 } 2343 vdslLineMCMConfProfileTxBandTable OBJECT-TYPE 2344 SYNTAX SEQUENCE OF VdslLineMCMConfProfileTxBandEntry 2345 MAX-ACCESS not-accessible 2346 STATUS current 2347 DESCRIPTION 2348 "This table contains transmit band descriptor configuration 2349 information for a VDSL line. Each entry in this table 2350 reflects the configuration for one of possibly many bands 2351 with a multiple carrier modulation (MCM) VDSL line. 2352 These entries are defined by a manager and can be used to 2353 configure the VDSL line. 2355 This table MUST be implemented for multiple carrier 2356 modulation (MCM) VDSL lines. This table MUST NOT be 2357 implemented for single carrier modulation VDSL lines." 2358 ::= { vdslMibObjects 13 } 2360 Expires December 17, 2002 [PAGE 44] 2361 vdslLineMCMConfProfileTxBandEntry OBJECT-TYPE 2362 SYNTAX VdslLineMCMConfProfileTxBandEntry 2363 MAX-ACCESS not-accessible 2364 STATUS current 2365 DESCRIPTION 2366 "Each entry consists of a transmit band descriptor, which 2367 is defined by a start and a stop tone index. 2369 A default profile with an index of 1 will always exist and 2370 its parameters will be set to vendor specific values, 2371 unless otherwise specified in this document." 2372 INDEX { vdslLineConfProfileIndex, 2373 vdslMCMConfProfileTxBandNumber } 2374 ::= { vdslLineMCMConfProfileTxBandTable 1 } 2376 VdslLineMCMConfProfileTxBandEntry ::= 2377 SEQUENCE 2378 { 2379 vdslMCMConfProfileTxBandNumber Unsigned32, 2380 vdslMCMConfProfileTxBandStart Unsigned32, 2381 vdslMCMConfProfileTxBandStop Unsigned32, 2382 vdslMCMConfProfileTxBandRowStatus RowStatus 2383 } 2385 vdslMCMConfProfileTxBandNumber OBJECT-TYPE 2386 SYNTAX Unsigned32 2387 MAX-ACCESS read-create 2388 STATUS current 2389 DESCRIPTION 2390 "The index for this band descriptor entry." 2391 ::= { vdslLineMCMConfProfileTxBandEntry 1 } 2393 vdslMCMConfProfileTxBandStart OBJECT-TYPE 2394 SYNTAX Unsigned32 2395 MAX-ACCESS read-create 2396 STATUS current 2397 DESCRIPTION 2398 "Start tone index for this band." 2399 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 2400 ::= { vdslLineMCMConfProfileTxBandEntry 2 } 2402 vdslMCMConfProfileTxBandStop OBJECT-TYPE 2403 SYNTAX Unsigned32 2404 MAX-ACCESS read-create 2405 STATUS current 2406 DESCRIPTION 2407 "Stop tone index for this band." 2408 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 2409 ::= { vdslLineMCMConfProfileTxBandEntry 3 } 2411 vdslMCMConfProfileTxBandRowStatus OBJECT-TYPE 2412 SYNTAX RowStatus 2414 Expires December 17, 2002 [PAGE 45] 2415 MAX-ACCESS read-create 2416 STATUS current 2417 DESCRIPTION 2418 "This object is used to create a new row or modify or 2419 delete an existing row in this table. 2421 A profile activated by setting this object to `active'. 2422 When `active' is set, the system will validate the profile. 2424 Before a profile can be deleted or taken out of 2425 service, (by setting this object to `destroy' or 2426 `outOfService') it must be first unreferenced 2427 from all associated lines." 2428 ::= { vdslLineMCMConfProfileTxBandEntry 4 } 2430 vdslLineMCMConfProfileRxBandTable OBJECT-TYPE 2431 SYNTAX SEQUENCE OF VdslLineMCMConfProfileRxBandEntry 2432 MAX-ACCESS not-accessible 2433 STATUS current 2434 DESCRIPTION 2435 "This table contains receive band descriptor configuration 2436 information for a VDSL line. Each entry in this table 2437 reflects the configuration for one of possibly many bands 2438 with a multiple carrier modulation (MCM) VDSL line. 2439 These entries are defined by a manager and can be used to 2440 configure the VDSL line. 2442 This table MUST be implemented for multiple carrier 2443 modulation (MCM) VDSL lines. This table MUST NOT be 2444 implemented for single carrier modulation VDSL lines." 2445 ::= { vdslMibObjects 14 } 2447 vdslLineMCMConfProfileRxBandEntry OBJECT-TYPE 2448 SYNTAX VdslLineMCMConfProfileRxBandEntry 2449 MAX-ACCESS not-accessible 2450 STATUS current 2451 DESCRIPTION 2452 "Each entry consists of a transmit band descriptor, which 2453 is defined by a start and a stop tone index. 2455 A default profile with an index of 1 will always exist and 2456 its parameters will be set to vendor specific values, 2457 unless otherwise specified in this document." 2458 INDEX { vdslLineConfProfileIndex, 2459 vdslMCMConfProfileRxBandNumber } 2460 ::= { vdslLineMCMConfProfileRxBandTable 1 } 2462 VdslLineMCMConfProfileRxBandEntry ::= 2463 SEQUENCE 2464 { 2465 vdslMCMConfProfileRxBandNumber Unsigned32, 2466 vdslMCMConfProfileRxBandStart Unsigned32, 2467 vdslMCMConfProfileRxBandStop Unsigned32, 2469 Expires December 17, 2002 [PAGE 46] 2470 vdslMCMConfProfileRxBandRowStatus RowStatus 2471 } 2473 vdslMCMConfProfileRxBandNumber OBJECT-TYPE 2474 SYNTAX Unsigned32 2475 MAX-ACCESS read-create 2476 STATUS current 2477 DESCRIPTION 2478 "The index for this band descriptor entry." 2479 ::= { vdslLineMCMConfProfileRxBandEntry 1 } 2481 vdslMCMConfProfileRxBandStart OBJECT-TYPE 2482 SYNTAX Unsigned32 2483 MAX-ACCESS read-create 2484 STATUS current 2485 DESCRIPTION 2486 "Start tone index for this band." 2487 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 2488 ::= { vdslLineMCMConfProfileRxBandEntry 2 } 2490 vdslMCMConfProfileRxBandStop OBJECT-TYPE 2491 SYNTAX Unsigned32 2492 MAX-ACCESS read-create 2493 STATUS current 2494 DESCRIPTION 2495 "Stop tone index for this band." 2496 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 2497 ::= { vdslLineMCMConfProfileRxBandEntry 3 } 2499 vdslMCMConfProfileRxBandRowStatus OBJECT-TYPE 2500 SYNTAX RowStatus 2501 MAX-ACCESS read-create 2502 STATUS current 2503 DESCRIPTION 2504 "This object is used to create a new row or modify or 2505 delete an existing row in this table. 2507 A profile activated by setting this object to `active'. 2508 When `active' is set, the system will validate the profile. 2510 Before a profile can be deleted or taken out of 2511 service, (by setting this object to `destroy' or 2512 `outOfService') it must be first unreferenced 2513 from all associated lines." 2514 ::= { vdslLineMCMConfProfileRxBandEntry 4 } 2516 vdslLineMCMConfProfileTxPSDTable OBJECT-TYPE 2517 SYNTAX SEQUENCE OF VdslLineMCMConfProfileTxPSDEntry 2518 MAX-ACCESS not-accessible 2519 STATUS current 2520 DESCRIPTION 2521 "This table contains transmit PSD mask descriptor 2522 configuration information for a VDSL line. Each entry in 2524 Expires December 17, 2002 [PAGE 47] 2525 this table reflects the configuration for one tone within 2526 a multiple carrier modulation (MCM) VDSL line. These 2527 entries are defined by a manager and can be used to 2528 configure the VDSL line. 2530 This table MUST be implemented for multiple carrier 2531 modulation (MCM) VDSL lines. This table MUST NOT be 2532 implemented for single carrier modulation VDSL lines." 2533 ::= { vdslMibObjects 15 } 2535 vdslLineMCMConfProfileTxPSDEntry OBJECT-TYPE 2536 SYNTAX VdslLineMCMConfProfileTxPSDEntry 2537 MAX-ACCESS not-accessible 2538 STATUS current 2539 DESCRIPTION 2540 "Each entry consists of a transmit PSD mask descriptor, 2541 which defines the power spectral density (PSD) for a tone. 2543 A default profile with an index of 1 will always exist and 2544 its parameters will be set to vendor specific values, 2545 unless otherwise specified in this document." 2546 INDEX { vdslLineConfProfileIndex, 2547 vdslMCMConfProfileTxPSDNumber } 2548 ::= { vdslLineMCMConfProfileTxPSDTable 1 } 2550 VdslLineMCMConfProfileTxPSDEntry ::= 2551 SEQUENCE 2552 { 2553 vdslMCMConfProfileTxPSDNumber Unsigned32, 2554 vdslMCMConfProfileTxPSDTone Unsigned32, 2555 vdslMCMConfProfileTxPSDPSD Unsigned32, 2556 vdslMCMConfProfileTxPSDRowStatus RowStatus 2557 } 2559 vdslMCMConfProfileTxPSDNumber OBJECT-TYPE 2560 SYNTAX Unsigned32 2561 MAX-ACCESS read-create 2562 STATUS current 2563 DESCRIPTION 2564 "The index for this mask descriptor entry." 2565 ::= { vdslLineMCMConfProfileTxPSDEntry 1 } 2567 vdslMCMConfProfileTxPSDTone OBJECT-TYPE 2568 SYNTAX Unsigned32 2569 MAX-ACCESS read-create 2570 STATUS current 2571 DESCRIPTION 2572 "The tone index for which the PSD is being specified." 2573 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 2574 ::= { vdslLineMCMConfProfileTxPSDEntry 2 } 2576 vdslMCMConfProfileTxPSDPSD OBJECT-TYPE 2577 SYNTAX Unsigned32 2579 Expires December 17, 2002 [PAGE 48] 2580 UNITS "0.5dB" 2581 MAX-ACCESS read-create 2582 STATUS current 2583 DESCRIPTION 2584 "Power Spectral Density level in steps of 0.5dB with 2585 an offset of -140dbm/Hz." 2586 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 2587 ::= { vdslLineMCMConfProfileTxPSDEntry 3 } 2589 vdslMCMConfProfileTxPSDRowStatus OBJECT-TYPE 2590 SYNTAX RowStatus 2591 MAX-ACCESS read-create 2592 STATUS current 2593 DESCRIPTION 2594 "This object is used to create a new row or modify or 2595 delete an existing row in this table. 2597 A profile activated by setting this object to `active'. 2598 When `active' is set, the system will validate the profile. 2600 Before a profile can be deleted or taken out of 2601 service, (by setting this object to `destroy' or 2602 `outOfService') it must be first unreferenced 2603 from all associated lines." 2604 ::= { vdslLineMCMConfProfileTxPSDEntry 4 } 2606 vdslLineMCMConfProfileMaxTxPSDTable OBJECT-TYPE 2607 SYNTAX SEQUENCE OF VdslLineMCMConfProfileMaxTxPSDEntry 2608 MAX-ACCESS not-accessible 2609 STATUS current 2610 DESCRIPTION 2611 "This table contains transmit maximum PSD mask descriptor 2612 configuration information for a VDSL line. Each entry in 2613 this table reflects the configuration for one tone within 2614 a multiple carrier modulation (MCM) VDSL modem. These 2615 entries are defined by a manager and can be used to 2616 configure the VDSL line. 2618 This table MUST be implemented for multiple carrier 2619 modulation (MCM) VDSL lines. This table MUST NOT be 2620 implemented for single carrier modulation VDSL lines." 2621 ::= { vdslMibObjects 16 } 2623 vdslLineMCMConfProfileMaxTxPSDEntry OBJECT-TYPE 2624 SYNTAX VdslLineMCMConfProfileMaxTxPSDEntry 2625 MAX-ACCESS not-accessible 2626 STATUS current 2627 DESCRIPTION 2628 "Each entry consists of a transmit PSD mask descriptor, 2629 which defines the maximum power spectral density (PSD) 2630 for a tone. 2632 A default profile with an index of 1 MUST always exist and 2634 Expires December 17, 2002 [PAGE 49] 2635 its parameters will be set to vendor specific values, 2636 unless otherwise specified in this document." 2637 INDEX { vdslLineConfProfileIndex, 2638 vdslMCMConfProfileMaxTxPSDNumber } 2639 ::= { vdslLineMCMConfProfileMaxTxPSDTable 1 } 2641 VdslLineMCMConfProfileMaxTxPSDEntry ::= 2642 SEQUENCE 2643 { 2644 vdslMCMConfProfileMaxTxPSDNumber Unsigned32, 2645 vdslMCMConfProfileMaxTxPSDTone Unsigned32, 2646 vdslMCMConfProfileMaxTxPSDPSD Unsigned32, 2647 vdslMCMConfProfileMaxTxPSDRowStatus RowStatus 2648 } 2650 vdslMCMConfProfileMaxTxPSDNumber OBJECT-TYPE 2651 SYNTAX Unsigned32 2652 MAX-ACCESS read-create 2653 STATUS current 2654 DESCRIPTION 2655 "The index for this band descriptor entry." 2656 ::= { vdslLineMCMConfProfileMaxTxPSDEntry 1 } 2658 vdslMCMConfProfileMaxTxPSDTone OBJECT-TYPE 2659 SYNTAX Unsigned32 2660 MAX-ACCESS read-create 2661 STATUS current 2662 DESCRIPTION 2663 "The tone index for which the PSD is being specified." 2664 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 2665 ::= { vdslLineMCMConfProfileMaxTxPSDEntry 2 } 2667 vdslMCMConfProfileMaxTxPSDPSD OBJECT-TYPE 2668 SYNTAX Unsigned32 2669 UNITS "0.5dB" 2670 MAX-ACCESS read-create 2671 STATUS current 2672 DESCRIPTION 2673 "Power Spectral Density level in steps of 0.5dB with 2674 an offset of -140dbm/Hz." 2675 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 2676 ::= { vdslLineMCMConfProfileMaxTxPSDEntry 3 } 2678 vdslMCMConfProfileMaxTxPSDRowStatus OBJECT-TYPE 2679 SYNTAX RowStatus 2680 MAX-ACCESS read-create 2681 STATUS current 2682 DESCRIPTION 2683 "This object is used to create a new row or modify or 2684 delete an existing row in this table. 2686 A profile activated by setting this object to `active'. 2687 When `active' is set, the system will validate the profile. 2689 Expires December 17, 2002 [PAGE 50] 2690 Before a profile can be deleted or taken out of 2691 service, (by setting this object to `destroy' or 2692 `outOfService') it must be first unreferenced 2693 from all associated lines." 2694 ::= { vdslLineMCMConfProfileMaxTxPSDEntry 4 } 2696 vdslLineMCMConfProfileMaxRxPSDTable OBJECT-TYPE 2697 SYNTAX SEQUENCE OF VdslLineMCMConfProfileMaxRxPSDEntry 2698 MAX-ACCESS not-accessible 2699 STATUS current 2700 DESCRIPTION 2701 "This table contains maximum receive PSD mask descriptor 2702 configuration information for a VDSL line. Each entry in 2703 this table reflects the configuration for one tone within 2704 a multiple carrier modulation (MCM) VDSL modem. These 2705 entries are defined by a manager and can be used to 2706 configure the VDSL line. 2708 This table MUST be implemented for multiple carrier 2709 modulation (MCM) VDSL lines. This table MUST NOT be 2710 implemented for single carrier modulation VDSL lines." 2711 ::= { vdslMibObjects 17 } 2713 vdslLineMCMConfProfileMaxRxPSDEntry OBJECT-TYPE 2714 SYNTAX VdslLineMCMConfProfileMaxRxPSDEntry 2715 MAX-ACCESS not-accessible 2716 STATUS current 2717 DESCRIPTION 2718 "Each entry consists of a transmit PSD mask descriptor, 2719 which defines the power spectral density (PSD) for a 2720 tone. 2722 A default profile with an index of 1 will always exist and 2723 its parameters will be set to vendor specific values, 2724 unless otherwise specified in this document." 2725 INDEX { vdslLineConfProfileIndex, 2726 vdslMCMConfProfileMaxRxPSDNumber } 2727 ::= { vdslLineMCMConfProfileMaxRxPSDTable 1 } 2729 VdslLineMCMConfProfileMaxRxPSDEntry ::= 2730 SEQUENCE 2731 { 2732 vdslMCMConfProfileMaxRxPSDNumber Unsigned32, 2733 vdslMCMConfProfileMaxRxPSDTone Unsigned32, 2734 vdslMCMConfProfileMaxRxPSDPSD Unsigned32, 2735 vdslMCMConfProfileMaxRxPSDRowStatus RowStatus 2736 } 2738 vdslMCMConfProfileMaxRxPSDNumber OBJECT-TYPE 2739 SYNTAX Unsigned32 2740 MAX-ACCESS read-create 2741 STATUS current 2743 Expires December 17, 2002 [PAGE 51] 2744 DESCRIPTION 2745 "The index for this band descriptor entry." 2746 ::= { vdslLineMCMConfProfileMaxRxPSDEntry 1 } 2748 vdslMCMConfProfileMaxRxPSDTone OBJECT-TYPE 2749 SYNTAX Unsigned32 2750 MAX-ACCESS read-create 2751 STATUS current 2752 DESCRIPTION 2753 "The tone index for which the PSD is being specified." 2754 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 2755 ::= { vdslLineMCMConfProfileMaxRxPSDEntry 2 } 2757 vdslMCMConfProfileMaxRxPSDPSD OBJECT-TYPE 2758 SYNTAX Unsigned32 2759 UNITS "0.5dB" 2760 MAX-ACCESS read-create 2761 STATUS current 2762 DESCRIPTION 2763 "Power Spectral Density level in steps of 0.5dB with 2764 an offset of -140dbm/Hz." 2765 REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM 2766 ::= { vdslLineMCMConfProfileMaxRxPSDEntry 3 } 2768 vdslMCMConfProfileMaxRxPSDRowStatus OBJECT-TYPE 2769 SYNTAX RowStatus 2770 MAX-ACCESS read-create 2771 STATUS current 2772 DESCRIPTION 2773 "This object is used to create a new row or modify or 2774 delete an existing row in this table. 2776 A profile activated by setting this object to `active'. 2777 When `active' is set, the system will validate the profile. 2779 Before a profile can be deleted or taken out of 2780 service, (by setting this object to `destroy' or 2781 `outOfService') it must be first unreferenced 2782 from all associated lines." 2783 ::= { vdslLineMCMConfProfileMaxRxPSDEntry 4 } 2785 -- 2786 -- Single carrier modulation (SCM) configuration profile tables 2787 -- 2789 vdslLineSCMConfProfileTable OBJECT-TYPE 2790 SYNTAX SEQUENCE OF VdslLineSCMConfProfileEntry 2791 MAX-ACCESS not-accessible 2792 STATUS current 2793 DESCRIPTION 2794 "This table contains information on the VDSL line 2795 configuration. One entry in this table reflects a 2796 profile defined by a manager which can be used to 2798 Expires December 17, 2002 [PAGE 52] 2799 configure the VDSL line. 2801 This table MUST be implemented for single carrier 2802 modulation (SCM) VDSL lines. This table MUST NOT be 2803 implemented for multiple carrier modulation (MCM) VDSL 2804 lines." 2805 ::= { vdslMibObjects 18 } 2807 vdslLineSCMConfProfileEntry OBJECT-TYPE 2808 SYNTAX VdslLineSCMConfProfileEntry 2809 MAX-ACCESS not-accessible 2810 STATUS current 2811 DESCRIPTION 2812 "Each entry consists of a list of parameters that 2813 represents the configuration of a single carrier 2814 modulation VDSL modem. 2816 A default profile with an index of 1 MUST always exist and 2817 its parameters will be set to vendor specific values, 2818 unless otherwise specified in this document." 2819 INDEX { vdslLineConfProfileIndex } 2820 ::= { vdslLineSCMConfProfileTable 1 } 2822 VdslLineSCMConfProfileEntry ::= 2823 SEQUENCE 2824 { 2825 vdslSCMConfProfileInterleaveDepth Unsigned32, 2826 vdslSCMConfProfileFastCodewordSize Unsigned32, 2827 vdslSCMConfProfileTransmitPSDMask BITS, 2828 vdslSCMConfProfileBands INTEGER, 2829 vdslSCMConfProfileFastFecSize INTEGER, 2830 vdslSCMConfProfileRowStatus RowStatus 2831 } 2833 vdslSCMConfProfileInterleaveDepth OBJECT-TYPE 2834 SYNTAX Unsigned32 2835 UNITS "octets" 2836 MAX-ACCESS read-create 2837 STATUS current 2838 DESCRIPTION 2839 "Specifies the interleaving depth." 2840 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 2841 ::= { vdslLineSCMConfProfileEntry 1 } 2843 vdslSCMConfProfileFastCodewordSize OBJECT-TYPE 2844 SYNTAX Unsigned32(0..180) 2845 UNITS "octets" 2846 MAX-ACCESS read-create 2847 STATUS current 2848 DESCRIPTION 2849 "Specifies the length in octets of the fast codeword. 2850 A value of 0 indicates that the single latency transport 2851 class is to be utilized." 2853 Expires December 17, 2002 [PAGE 53] 2854 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 2855 ::= { vdslLineSCMConfProfileEntry 2 } 2857 vdslSCMConfProfileTransmitPSDMask OBJECT-TYPE 2858 SYNTAX BITS 2859 { 2860 vendorNotch1(0), -- vendor specific notch 2861 vendorNotch2(1), -- vendor specific notch 2862 amateurBand30m(2), -- amateur radio band notch 2863 amateurBand40m(3), -- amateur radio band notch 2864 amateurBand80m(4), -- amateur radio band notch 2865 amateurBand160m(5) -- amateur radio band notch 2866 } 2867 MAX-ACCESS read-create 2868 STATUS current 2869 DESCRIPTION 2870 "The transmit power spectral density mask code." 2871 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 2872 ::= { vdslLineSCMConfProfileEntry 3 } 2874 vdslSCMConfProfileBands OBJECT-TYPE 2875 SYNTAX INTEGER 2876 { 2877 oneBand(1), 2878 twoBands(2), 2879 upstreamU0(3) 2880 } 2881 MAX-ACCESS read-create 2882 STATUS current 2883 DESCRIPTION 2884 "Specifies the number of bands used to transmit." 2885 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 2886 ::= { vdslLineSCMConfProfileEntry 4 } 2888 vdslSCMConfProfileFastFecSize OBJECT-TYPE 2889 SYNTAX INTEGER 2890 { 2891 noFEC(1), 2892 fecSize2(2), 2893 fecSize4(3), 2894 fecSize16(4) 2895 } 2896 MAX-ACCESS read-create 2897 STATUS current 2898 DESCRIPTION 2899 "When fast channel is being used, this object specifies 2900 the size of the forward error correction (FEC) codeword." 2901 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 2902 ::= { vdslLineSCMConfProfileEntry 5 } 2904 vdslSCMConfProfileRowStatus OBJECT-TYPE 2905 SYNTAX RowStatus 2906 MAX-ACCESS read-create 2908 Expires December 17, 2002 [PAGE 54] 2909 STATUS current 2910 DESCRIPTION 2911 "This object is used to create a new row or modify or 2912 delete an existing row in this table. 2914 A profile activated by setting this object to `active'. 2915 When `active' is set, the system will validate the profile. 2917 Before a profile can be deleted or taken out of 2918 service, (by setting this object to `destroy' or 2919 `outOfService') it must be first unreferenced 2920 from all associated lines." 2921 ::= { vdslLineSCMConfProfileEntry 6 } 2923 vdslLineSCMConfProfileTxBandTable OBJECT-TYPE 2924 SYNTAX SEQUENCE OF VdslLineSCMConfProfileTxBandEntry 2925 MAX-ACCESS not-accessible 2926 STATUS current 2927 DESCRIPTION 2928 "This table contains transmit band descriptor configuration 2929 information for a VDSL line. Each entry in this table 2930 reflects the configuration for one of possibly three bands 2931 with a single carrier modulation (SCM) VDSL line. These 2932 entries are defined by a manager and can be used to configure 2933 the VDSL line. 2935 This table MUST be implemented for single carrier 2936 modulation (SCM) VDSL lines. This table MUST NOT be 2937 implemented for multiple carrier modulation (MCM) VDSL 2938 lines." 2939 ::= { vdslMibObjects 19 } 2941 vdslLineSCMConfProfileTxBandEntry OBJECT-TYPE 2942 SYNTAX VdslLineSCMConfProfileTxBandEntry 2943 MAX-ACCESS not-accessible 2944 STATUS current 2945 DESCRIPTION 2946 "Each entry consists of a list of parameters that 2947 represents the configuration of a single carrier 2948 modulation VDSL modem transmit band. 2950 A default profile with an index of 1 MUST always exist and 2951 its parameters will be set to vendor specific values, 2952 unless otherwise specified in this document." 2953 INDEX { vdslLineConfProfileIndex, 2954 vdslSCMConfProfileTxBandNumber } 2955 ::= { vdslLineSCMConfProfileTxBandTable 1 } 2957 VdslLineSCMConfProfileTxBandEntry ::= 2958 SEQUENCE 2959 { 2960 vdslSCMConfProfileTxBandNumber INTEGER, 2961 vdslSCMConfProfileTxBandTransmitPSDLevel Unsigned32, 2963 Expires December 17, 2002 [PAGE 55] 2964 vdslSCMConfProfileTxBandSymbolRateProfile Unsigned32, 2965 vdslSCMConfProfileTxBandConstellationSize Unsigned32, 2966 vdslSCMConfProfileTxBandCenterFrequency Unsigned32, 2967 vdslSCMConfProfileTxBandRowStatus RowStatus 2968 } 2970 vdslSCMConfProfileTxBandNumber OBJECT-TYPE 2971 SYNTAX INTEGER 2972 { 2973 band1(1), 2974 band2(2), 2975 upstreamU0(3) 2976 } 2977 MAX-ACCESS read-create 2978 STATUS current 2979 DESCRIPTION 2980 "The SCN transmit band number for this entry." 2981 ::= { vdslLineSCMConfProfileTxBandEntry 1 } 2983 vdslSCMConfProfileTxBandTransmitPSDLevel OBJECT-TYPE 2984 SYNTAX Unsigned32 2985 UNITS "-dBm/Hz" 2986 MAX-ACCESS read-create 2987 STATUS current 2988 DESCRIPTION 2989 "The transmit power spectral density for the VDSL modem." 2990 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 2991 ::= { vdslLineSCMConfProfileTxBandEntry 2 } 2993 vdslSCMConfProfileTxBandSymbolRateProfile OBJECT-TYPE 2994 SYNTAX Unsigned32 2995 UNITS "kbaud" 2996 MAX-ACCESS read-create 2997 STATUS current 2998 DESCRIPTION 2999 "The symbol rate profile calculated as S = SR/BSR, where 3000 SR is the required symbol rate in kbaud, BSR = 67.5." 3001 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 3002 ::= { vdslLineSCMConfProfileTxBandEntry 3 } 3004 vdslSCMConfProfileTxBandConstellationSize OBJECT-TYPE 3005 SYNTAX Unsigned32(0..8) 3006 UNITS "log2" 3007 MAX-ACCESS read-create 3008 STATUS current 3009 DESCRIPTION 3010 "Specifies the constellation size." 3011 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 3012 ::= { vdslLineSCMConfProfileTxBandEntry 4 } 3014 vdslSCMConfProfileTxBandCenterFrequency OBJECT-TYPE 3015 SYNTAX Unsigned32(0..511) 3016 UNITS "33.75kHz" 3018 Expires December 17, 2002 [PAGE 56] 3019 MAX-ACCESS read-create 3020 STATUS current 3021 DESCRIPTION 3022 "Specifies the center frequency profile K." 3023 REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM 3024 ::= { vdslLineSCMConfProfileTxBandEntry 5 } 3026 vdslSCMConfProfileTxBandRowStatus OBJECT-TYPE 3027 SYNTAX RowStatus 3028 MAX-ACCESS read-create 3029 STATUS current 3030 DESCRIPTION 3031 "This object is used to create a new row or modify or 3032 delete an existing row in this table. 3034 A profile activated by setting this object to `active'. 3035 When `active' is set, the system will validate the profile. 3037 Before a profile can be deleted or taken out of 3038 service, (by setting this object to `destroy' or 3039 `outOfService') it must be first unreferenced 3040 from all associated lines." 3041 ::= { vdslLineSCMConfProfileTxBandEntry 6 } 3043 -- 3044 -- Alarm configuration profile table 3045 -- 3047 vdslLineAlarmConfProfileTable OBJECT-TYPE 3048 SYNTAX SEQUENCE OF VdslLineAlarmConfProfileEntry 3049 MAX-ACCESS not-accessible 3050 STATUS current 3051 DESCRIPTION 3052 "This table contains information on the VDSL line alarm 3053 configuration. One entry in this table reflects a profile 3054 defined by a manager which can be used to configure the 3055 VDSL line alarm thresholds." 3056 ::= { vdslMibObjects 20 } 3058 vdslLineAlarmConfProfileEntry OBJECT-TYPE 3059 SYNTAX VdslLineAlarmConfProfileEntry 3060 MAX-ACCESS not-accessible 3061 STATUS current 3062 DESCRIPTION 3063 "Each entry consists of a list of parameters that 3064 represents the configuration of a VDSL line alarm 3065 profile. 3067 A default profile with an index of 1 MUST always exist and 3068 its parameters will be set to vendor specific values, 3069 unless otherwise specified in this document." 3070 INDEX { vdslLineAlarmConfProfileIndex } 3071 ::= { vdslLineAlarmConfProfileTable 1 } 3073 Expires December 17, 2002 [PAGE 57] 3074 VdslLineAlarmConfProfileEntry ::= 3075 SEQUENCE 3076 { 3077 vdslLineAlarmConfProfileIndex Unsigned32, 3078 vdslLineAlarmConfProfileName SnmpAdminString, 3079 vdslThresh15MinLofs Unsigned32, 3080 vdslThresh15MinLoss Unsigned32, 3081 vdslThresh15MinLprs Unsigned32, 3082 vdslThresh15MinESs Unsigned32, 3083 vdslThresh15MinSESs Unsigned32, 3084 vdslThresh15MinUASs Unsigned32, 3085 vdslInitFailureNotificationEnable TruthValue, 3086 vdslLineAlarmConfProfileRowStatus RowStatus 3087 } 3089 vdslLineAlarmConfProfileIndex OBJECT-TYPE 3090 SYNTAX Unsigned32 3091 MAX-ACCESS read-create 3092 STATUS current 3093 DESCRIPTION 3094 "This object is used by the line alarm configuration table 3095 in order to identify a row in that table. The system MUST 3096 provide a default profile whose index is 1." 3097 ::= { vdslLineAlarmConfProfileEntry 1 } 3099 vdslLineAlarmConfProfileName OBJECT-TYPE 3100 SYNTAX SnmpAdminString (SIZE (1..32)) 3101 MAX-ACCESS read-create 3102 STATUS current 3103 DESCRIPTION 3104 "The name for this profile as specified by a user." 3105 ::= { vdslLineAlarmConfProfileEntry 2 } 3107 vdslThresh15MinLofs OBJECT-TYPE 3108 SYNTAX Unsigned32(0..899) 3109 UNITS "seconds" 3110 MAX-ACCESS read-create 3111 STATUS current 3112 DESCRIPTION 3113 "This object configures the threshold for the number of 3114 loss of frame seconds (lofs) within any given 15-minute 3115 performance data collection interval. If the value of 3116 loss of frame seconds in a particular 15-minute collection 3117 interval reaches/exceeds this value, a 3118 vdslPerfLofsThreshNotification notification will be 3119 generated. No more than one notification will be sent 3120 per interval." 3121 ::= { vdslLineAlarmConfProfileEntry 3 } 3123 vdslThresh15MinLoss OBJECT-TYPE 3124 SYNTAX Unsigned32(0..899) 3125 UNITS "seconds" 3127 Expires December 17, 2002 [PAGE 58] 3128 MAX-ACCESS read-create 3129 STATUS current 3130 DESCRIPTION 3131 "This object configures the threshold for the number of 3132 loss of signal seconds (loss) within any given 15-minute 3133 performance data collection interval. If the value of 3134 loss of frame seconds in a particular 15-minute collection 3135 interval reaches/exceeds this value, a 3136 vdslPerfLossThreshNotification notification will be 3137 generated. One notification will be sent per interval 3138 per endpoint." 3139 ::= { vdslLineAlarmConfProfileEntry 4 } 3141 vdslThresh15MinLprs OBJECT-TYPE 3142 SYNTAX Unsigned32(0..899) 3143 UNITS "seconds" 3144 MAX-ACCESS read-create 3145 STATUS current 3146 DESCRIPTION 3147 "This object configures the threshold for the number of 3148 loss of power seconds (lprs) within any given 15-minute 3149 performance data collection interval. If the value of 3150 loss of frame seconds in a particular 15-minute collection 3151 interval reaches/exceeds this value, a 3152 vdslPerfLprsThreshNotification notification will be 3153 generated. No more than one notification will be sent 3154 per interval." 3155 ::= { vdslLineAlarmConfProfileEntry 5 } 3157 vdslThresh15MinESs OBJECT-TYPE 3158 SYNTAX Unsigned32(0..899) 3159 UNITS "seconds" 3160 MAX-ACCESS read-create 3161 STATUS current 3162 DESCRIPTION 3163 "This object configures the threshold for the number of 3164 errored seconds (ESs) within any given 15-minute 3165 performance data collection interval. If the value of 3166 errored seconds in a particular 15-minute collection 3167 interval reaches/exceeds this value, a 3168 vdslPerfESsThreshNotification notification will be 3169 generated. No more than one notification will be sent 3170 per interval." 3171 ::= { vdslLineAlarmConfProfileEntry 6 } 3173 vdslThresh15MinSESs OBJECT-TYPE 3174 SYNTAX Unsigned32(0..899) 3175 UNITS "seconds" 3176 MAX-ACCESS read-create 3177 STATUS current 3178 DESCRIPTION 3179 "This object configures the threshold for the number of 3180 severely errored seconds (SESs) within any given 15-minute 3182 Expires December 17, 2002 [PAGE 59] 3183 performance data collection interval. If the value of 3184 severely errored seconds in a particular 15-minute 3185 collection interval reaches/exceeds this value, a 3186 vdslPerfSESsThreshNotification notification will be 3187 generated. No more than one notification will be sent 3188 per interval." 3189 ::= { vdslLineAlarmConfProfileEntry 7 } 3191 vdslThresh15MinUASs OBJECT-TYPE 3192 SYNTAX Unsigned32(0..899) 3193 UNITS "seconds" 3194 MAX-ACCESS read-create 3195 STATUS current 3196 DESCRIPTION 3197 "This object configures the threshold for the number of 3198 unavailable seconds (UASs) within any given 15-minute 3199 performance data collection interval. If the value of 3200 unavailable seconds in a particular 15-minute collection 3201 interval reaches/exceeds this value, a 3202 vdslPerfUASsThreshNotification notification will be 3203 generated. No more than one notification will be sent 3204 per interval." 3205 ::= { vdslLineAlarmConfProfileEntry 8 } 3207 vdslInitFailureNotificationEnable OBJECT-TYPE 3208 SYNTAX TruthValue 3209 MAX-ACCESS read-create 3210 STATUS current 3211 DESCRIPTION 3212 "This object specifies if a vdslInitFailureNotification 3213 notification will be generated if an initialization 3214 failure occurs." 3215 ::= { vdslLineAlarmConfProfileEntry 9 } 3217 vdslLineAlarmConfProfileRowStatus OBJECT-TYPE 3218 SYNTAX RowStatus 3219 MAX-ACCESS read-create 3220 STATUS current 3221 DESCRIPTION 3222 "This object is used to create a new row or modify or 3223 delete an existing row in this table. 3225 A profile activated by setting this object to `active'. 3226 When `active' is set, the system will validate the profile. 3228 Before a profile can be deleted or taken out of 3229 service, (by setting this object to `destroy' or 3230 `outOfService') it must be first unreferenced 3231 from all associated lines." 3232 ::= { vdslLineAlarmConfProfileEntry 10 } 3234 -- Notification definitions 3236 Expires December 17, 2002 [PAGE 60] 3237 vdslNotifications OBJECT IDENTIFIER ::= { vdslLineMib 0 } 3239 vdslPerfLofsThreshNotification NOTIFICATION-TYPE 3240 OBJECTS { 3241 vdslPerfCurr15MinLofs, 3242 vdslThresh15MinLofs 3243 } 3244 STATUS current 3245 DESCRIPTION 3246 "Loss of Framing 15-minute interval threshold reached." 3247 ::= { vdslNotifications 1 } 3249 vdslPerfLossThreshNotification NOTIFICATION-TYPE 3250 OBJECTS { 3251 vdslPerfCurr15MinLoss, 3252 vdslThresh15MinLoss 3253 } 3254 STATUS current 3255 DESCRIPTION 3256 "Loss of Signal 15-minute interval threshold reached." 3257 ::= { vdslNotifications 2 } 3259 vdslPerfLprsThreshNotification NOTIFICATION-TYPE 3260 OBJECTS { 3261 vdslPerfCurr15MinLprs, 3262 vdslThresh15MinLprs 3263 } 3264 STATUS current 3265 DESCRIPTION 3266 "Loss of Power 15-minute interval threshold reached." 3267 ::= { vdslNotifications 3 } 3269 vdslPerfESsThreshNotification NOTIFICATION-TYPE 3270 OBJECTS { 3271 vdslPerfCurr15MinESs, 3272 vdslThresh15MinESs 3273 } 3274 STATUS current 3275 DESCRIPTION 3276 "Errored Seconds 15-minute interval threshold reached." 3277 ::= { vdslNotifications 4 } 3279 vdslPerfSESsThreshNotification NOTIFICATION-TYPE 3280 OBJECTS { 3281 vdslPerfCurr15MinSESs, 3282 vdslThresh15MinSESs 3283 } 3284 STATUS current 3285 DESCRIPTION 3286 "Severely Errored Seconds 15-minute interval threshold 3287 reached." 3288 ::= { vdslNotifications 5 } 3290 Expires December 17, 2002 [PAGE 61] 3291 vdslPerfUASsThreshNotification NOTIFICATION-TYPE 3292 OBJECTS { 3293 vdslPerfCurr15MinUASs, 3294 vdslThresh15MinUASs 3295 } 3296 STATUS current 3297 DESCRIPTION 3298 "Unavailable Seconds 15-minute interval threshold reached." 3299 ::= { vdslNotifications 6 } 3301 vdslInitFailureNotification NOTIFICATION-TYPE 3302 OBJECTS { 3303 vdslCurrStatus 3304 } 3305 STATUS current 3306 DESCRIPTION 3307 "Vtu initialization failed. See vdslCurrStatus for 3308 potential reasons." 3309 ::= { vdslNotifications 7 } 3311 -- conformance information 3313 vdslConformance OBJECT IDENTIFIER ::= { vdslLineMib 3 } 3314 vdslGroups OBJECT IDENTIFIER ::= { vdslConformance 1 } 3315 vdslCompliances OBJECT IDENTIFIER ::= { vdslConformance 2 } 3317 vdslLineMibCompliance MODULE-COMPLIANCE 3318 STATUS current 3319 DESCRIPTION 3320 "The compliance statement for SNMP entities which 3321 manage VDSL interfaces." 3323 MODULE -- this module 3324 MANDATORY-GROUPS 3325 { 3326 vdslGroup 3327 } 3329 GROUP vdslMCMGroup 3330 DESCRIPTION 3331 "This group is mandatory for VDSL Lines which 3332 utilize multiple carrier modulation. 3334 This group should not be implemented for VDSL lines 3335 which utilize single carrier modulation." 3337 GROUP vdslSCMGroup 3338 DESCRIPTION 3339 "This group is mandatory for VDSL lines which 3340 utilize single carrier modulation. 3342 This group should not be implemented for VDSL lines 3343 which utilize multiple carrier modulation" 3345 Expires December 17, 2002 [PAGE 62] 3346 ::= { vdslCompliances 1 } 3348 -- units of conformance 3350 vdslGroup OBJECT-GROUP 3351 OBJECTS 3352 { 3353 vdslLineCoding, 3354 vdslLineType, 3355 vdslLineConfProfile, 3356 vdslLineAlarmConfProfile, 3357 vdslPhysSide, 3358 vdslInvSerialNumber, 3359 vdslInvVendorID, 3360 vdslInvVersionNumber, 3361 vdslCurrSnrMgn, 3362 vdslCurrAtn, 3363 vdslCurrStatus, 3364 vdslCurrOutputPwr, 3365 vdslCurrAttainableRate, 3366 vdslChanInterleaveDelay, 3367 vdslChanCrcBlockLength, 3368 vdslPerfValidIntervals, 3369 vdslPerfInvalidIntervals, 3370 vdslPerfLofs, 3371 vdslPerfLoss, 3372 vdslPerfLprs, 3373 vdslPerfESs, 3374 vdslPerfSESs, 3375 vdslPerfUASs, 3376 vdslPerfInits, 3377 vdslPerfCurr15MinTimeElapsed, 3378 vdslPerfCurr15MinLofs, 3379 vdslPerfCurr15MinLoss, 3380 vdslPerfCurr15MinLprs, 3381 vdslPerfCurr15MinESs, 3382 vdslPerfCurr15MinSESs, 3383 vdslPerfCurr15MinUASs, 3384 vdslPerfCurr15MinInits, 3385 vdslPerf1DayValidIntervals, 3386 vdslPerf1DayInvalidIntervals, 3387 vdslPerfCurr1DayTimeElapsed, 3388 vdslPerfCurr1DayLofs, 3389 vdslPerfCurr1DayLoss, 3390 vdslPerfCurr1DayLprs, 3391 vdslPerfCurr1DayESs, 3392 vdslPerfCurr1DaySESs, 3393 vdslPerfCurr1DayUASs, 3394 vdslPerfCurr1DayInits, 3395 vdslIntervalLofs, 3396 vdslIntervalLoss, 3397 vdslIntervalLprs, 3398 vdslIntervalESs, 3400 Expires December 17, 2002 [PAGE 63] 3401 vdslIntervalSESs, 3402 vdslIntervalUASs, 3403 vdslIntervalInits, 3404 vdsl1DayIntervalMoniSecs, 3405 vdsl1DayIntervalLofs, 3406 vdsl1DayIntervalLoss, 3407 vdsl1DayIntervalLprs, 3408 vdsl1DayIntervalESs, 3409 vdsl1DayIntervalSESs, 3410 vdsl1DayIntervalUASs, 3411 vdsl1DayIntervalInits, 3412 vdslChanPerfValidIntervals, 3413 vdslChanPerfInvalidIntervals, 3414 vdslChanCorrectedOctets, 3415 vdslChanUncorrectBlks, 3416 vdslChanPerfCurr15MinTimeElapsed, 3417 vdslChanPerfCurr15MinCorrectedOctets, 3418 vdslChanPerfCurr15MinUncorrectBlks, 3419 vdslChanPerf1DayValidIntervals, 3420 vdslChanPerf1DayInvalidIntervals, 3421 vdslChanPerfCurr1DayTimeElapsed, 3422 vdslChanPerfCurr1DayCorrectedOctets, 3423 vdslChanPerfCurr1DayUncorrectBlks, 3424 vdslChanIntervalCorrectedOctets, 3425 vdslChanIntervalUncorrectBlks, 3426 vdslChan1DayIntervalMoniSecs, 3427 vdslChan1DayIntervalCorrectedOctets, 3428 vdslChan1DayIntervalUncorrectBlks, 3429 vdslLineConfProfileIndex, 3430 vdslLineConfProfileName, 3431 vdslLineConfTargetSnrMgn, 3432 vdslLineConfUpstreamTxSpeed, 3433 vdslLineConfDownstreamTxSpeed, 3434 vdslLineConfUpstreamPboControl, 3435 vdslLineConfDownstreamPboControl, 3436 vdslLineConfDeploymentScenario, 3437 vdslLineConfAdslOccupy, 3438 vdslLineConfApplicableStandard, 3439 vdslLineConfBandPlan, 3440 vdslLineConfBandPlanFx, 3441 vdslLineConfBandU0Usage, 3442 vdslLineConfUpstreamPsdTemplate, 3443 vdslLineConfDownstreamPsdTemplate, 3444 vdslLineConfProfileRowStatus, 3445 vdslLineAlarmConfProfileIndex, 3446 vdslLineAlarmConfProfileName, 3447 vdslThresh15MinLofs, 3448 vdslThresh15MinLoss, 3449 vdslThresh15MinLprs, 3450 vdslThresh15MinESs, 3451 vdslThresh15MinSESs, 3452 vdslThresh15MinUASs, 3453 vdslInitFailureNotificationEnable, 3455 Expires December 17, 2002 [PAGE 64] 3456 vdslLineAlarmConfProfileRowStatus 3457 } 3458 STATUS current 3459 DESCRIPTION 3460 "A collection of objects providing information about 3461 a VDSL Line." 3462 ::= { vdslGroups 1 } 3464 vdslMCMGroup OBJECT-GROUP 3465 OBJECTS 3466 { 3467 vdslMCMConfProfileTxWindowLength, 3468 vdslMCMConfProfileRowStatus, 3469 vdslMCMConfProfileTxBandNumber, 3470 vdslMCMConfProfileTxBandStart, 3471 vdslMCMConfProfileTxBandStop, 3472 vdslMCMConfProfileTxBandRowStatus, 3473 vdslMCMConfProfileRxBandNumber, 3474 vdslMCMConfProfileRxBandStart, 3475 vdslMCMConfProfileRxBandStop, 3476 vdslMCMConfProfileRxBandRowStatus, 3477 vdslMCMConfProfileTxPSDNumber, 3478 vdslMCMConfProfileTxPSDTone, 3479 vdslMCMConfProfileTxPSDPSD, 3480 vdslMCMConfProfileTxPSDRowStatus, 3481 vdslMCMConfProfileMaxTxPSDNumber, 3482 vdslMCMConfProfileMaxTxPSDTone, 3483 vdslMCMConfProfileMaxTxPSDPSD, 3484 vdslMCMConfProfileMaxTxPSDRowStatus, 3485 vdslMCMConfProfileMaxRxPSDNumber, 3486 vdslMCMConfProfileMaxRxPSDTone, 3487 vdslMCMConfProfileMaxRxPSDPSD, 3488 vdslMCMConfProfileMaxRxPSDRowStatus 3489 } 3490 STATUS current 3491 DESCRIPTION 3492 "A collection of objects providing configuration 3493 information for a VDSL line based upon multiple carrier 3494 modulation modem." 3495 ::= { vdslGroups 2 } 3497 vdslSCMGroup OBJECT-GROUP 3498 OBJECTS 3499 { 3500 vdslSCMPhysBandSnrMgn, 3501 vdslSCMPhysBandAtn, 3502 vdslSCMConfProfileInterleaveDepth, 3503 vdslSCMConfProfileFastCodewordSize, 3504 vdslSCMConfProfileTransmitPSDMask, 3505 vdslSCMConfProfileBands, 3506 vdslSCMConfProfileFastFecSize, 3507 vdslSCMConfProfileRowStatus, 3508 vdslSCMConfProfileTxBandNumber, 3510 Expires December 17, 2002 [PAGE 65] 3511 vdslSCMConfProfileTxBandTransmitPSDLevel, 3512 vdslSCMConfProfileTxBandSymbolRateProfile, 3513 vdslSCMConfProfileTxBandConstellationSize, 3514 vdslSCMConfProfileTxBandCenterFrequency, 3515 vdslSCMConfProfileTxBandRowStatus 3516 } 3517 STATUS current 3518 DESCRIPTION 3519 "A collection of objects providing configuration 3520 information for a VDSL line based upon single carrier 3521 modulation modem." 3522 ::= { vdslGroups 3 } 3524 vdslNotificationGroup NOTIFICATION-GROUP 3525 NOTIFICATIONS 3526 { 3527 vdslPerfLofsThreshNotification, 3528 vdslPerfLossThreshNotification, 3529 vdslPerfLprsThreshNotification, 3530 vdslPerfESsThreshNotification, 3531 vdslPerfSESsThreshNotification, 3532 vdslPerfUASsThreshNotification, 3533 vdslInitFailureNotification 3534 } 3535 STATUS current 3536 DESCRIPTION 3537 "This group supports notifications of significant 3538 conditions associated with VDSL Lines." 3539 ::= { vdslGroups 4 } 3541 END 3543 Normative References 3545 [ETSI2701] ETSI TS 101 270-1 V1.2.1 "Transmission and Multiplexing 3546 (TM); Access transmission systems on metallic access 3547 cables; Very high speed Digital Subscriber Line (VDSL); 3548 Part 1: Functional requirements", October 1999. 3550 [ETSI2702] ETSI TS 101 270-2 V1.1.1 "Transmission and Multiplexing 3551 (TM); Access transmission systems on metallic access 3552 cables; Very high speed Digital Subscriber Line (VDSL); 3553 Part 1: Transceiver specification", February 2001. 3555 [ITU9931] ITU-T G.993.1 "Very-high-speed digital subscriber line 3556 foundation", November 2001. 3558 [RFC1901] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 3559 "Introduction to Community-based SNMPv2", RFC 1901, 3560 January 1996. 3562 [RFC1905] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 3563 "Protocol Operations for Version 2 of the Simple Network 3565 Expires December 17, 2002 [PAGE 66] 3566 Management Protocol (SNMPv2)", RFC 1905, January 1996. 3568 [RFC1906] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 3569 "Transport Mappings for Version 2 of the Simple Network 3570 Management Protocol (SNMPv2)", RFC 1906, January 1996. 3572 [RFC2119] Bradner, S., "Key Words for use in RFCs to Indicate 3573 Requirement Levels", RFC 2119, March 1997. 3575 [RFC2493] Tesink, K., "Textual Conventions for MIB Modules Using 3576 Performance History Based on 15 Minute Intervals", RFC 3577 2493, January 1999. 3579 [RFC2571] Harrington, D., Presuhn, R. and B. Wijnen, "An 3580 Architecture for Describing SNMP Management Frameworks", 3581 RFC 2571, April 1999. 3583 [RFC2572] Case, J., Harrington D., Presuhn, R. and B. Wijnen, 3584 "Message Processing and Dispatching for the Simple Network 3585 Management Protocol (SNMP)", RFC 2572, April 1999. 3587 [RFC2574] Blumenthal, U. and B. Wijnen, "User-based Security Model 3588 (USM) for version 3 of the Simple Network Management 3589 Protocol (SNMPv3)", RFC 2574, April 1999. 3591 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 3592 Rose, M. and S. Waldbusser, "Structure of Management 3593 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 3594 1999. 3596 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 3597 Rose, M. and S. Waldbusser, "Textual Conventions for 3598 SMIv2", STD 58, RFC 2579, April 1999. 3600 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 3601 Rose, M. and S. Waldbusser, "Conformance Statements for 3602 SMIv2", STD 58, RFC 2580, April 1999. 3604 [RFC2662] Bathrick, G. and F. Ly, "Definitions of Managed Objects 3605 for the ADSL Lines", RFC 2662, August 1999. 3607 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 3608 MIB", RFC 2863, June 2000. 3610 [T1E1311] ANSI T1E1.4/2001-311, "Very-high-bit-rate Digital 3611 Subscriber Line (VDSL) Metallic Interface, Part 1: 3612 Functional Requirements and Common Specification", February 3613 2001. 3615 [T1E1011] ANSI T1E1.4/2001-011R3, "VDSL Metallic Interface, Part 2: 3616 Technical Specification for a Single-Carrier Modulation 3617 (SCM) Transceiver", November 2001. 3619 Expires December 17, 2002 [PAGE 67] 3621 [T1E1013] ANSI T1E1.4/2001-013R4, "VDSL Metallic Interface, Part 3: 3622 Technical Specification for a Multi-Carrier Modulation 3623 (MCM) Transceiver", November 2000. 3625 Informative References 3627 [RFC1155] Rose, M. and K. McCloghrie, "Structure and Identification 3628 of Management Information for TCP/IP-based Internets", STD 3629 16, RFC 1155, May 1990. 3631 [RFC1157] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple 3632 Network Management Protocol", STD 15, RFC 1157, May 1990. 3634 [RFC1212] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 3635 16, RFC 1212, March 1991. 3637 [RFC1215] Rose, M., "A Convention for Defining Traps for use with 3638 the SNMP", RFC 1215, March 1991. 3640 [RFC2570] Case, J., Mundy, R., Partain, D. and B. Stewart, 3641 "Introduction to Version 3 of the Internet-standard Network 3642 Management Framework", RFC 2570, April 1999. 3644 [RFC2573] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 Applications", 3645 RFC 2573, April 1999. 3647 [RFC2575] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based 3648 Access Control Model (VACM) for the Simple Network 3649 Management Protocol (SNMP)", RFC 2575, April 1999. 3651 Security Considerations 3653 There are a number of management objects defined in this MIB that 3654 have a MAX-ACCESS clause of read-write and/or read-create. Such 3655 objects may be considered sensitive or vulnerable in some network 3656 environments. The support for SET operations in a non-secure 3657 environment without proper protection can have a negative effect on 3658 network operations. 3660 VDSL layer connectivity from the Vtur will permit the subscriber 3661 to manipulate both the VDSL link directly and the VDSL embedded 3662 operations channel (EOC) for their own loop. For example, unchecked 3663 or unfiltered fluctuations initiated by the subscriber could generate 3664 sufficient notifications to potentially overwhelm either the 3665 management interface to the network or the element manager. 3667 For this reason, there are a number of managed objects in this MIB 3668 that may contain sensitive information. These are: 3670 vdslThresh15MinLofs 3671 vdslThresh15MinLoss 3672 vdslThresh15MinLprs 3673 vdslThresh15MinESs 3675 Expires December 17, 2002 [PAGE 68] 3676 vdslThresh15MinSESs 3677 vdslThresh15MinUASs 3679 It is thus important to control even GET access to these objects and 3680 possibly to even encrypt the values of these objects when sending 3681 them over the network via SNMP. Not all versions of SNMP provide 3682 features for such a secure environment. 3684 Further, notifications generated by agents implementing this MIB 3685 will contain the above threshold information. 3687 SNMPv1 by itself is not a secure environment. Even if the network 3688 itself is secure (for example by using IPSec), even then, there is no 3689 control as to who on the secure network is allowed to access and 3690 GET/SET (read/change/create/delete) the objects in this MIB. 3692 It is recommended that the implementers consider the security 3693 features as provided by the SNMPv3 framework. Specifically, the use 3694 of the User-based Security Model RFC 2574 [12] and the View- 3695 based Access Control Model RFC 2575 [15] is recommended. 3697 It is then a customer/user responsibility to ensure that the SNMP 3698 entity giving access to an instance of this MIB, is properly 3699 configured to give access to the objects only to those principals 3700 (users) that have legitimate rights to indeed GET or SET 3701 (change/create/delete) them. 3703 IANA Considerations 3705 The VDSL-LINE-MIB MIB module requires the allocation of a single 3706 object identifier for its MODULE-IDENTITY. IANA should allocate 3707 this object identifier in the transmission subtree. 3709 Acknowledgments 3711 David Horton (CiTR) 3713 Moti Morgenstern (Inovia) 3715 Intellectual Property Notice 3717 The IETF takes no position regarding the validity or scope of any 3718 intellectual property or other rights that might be claimed to 3719 pertain to the implementation or use of the technology described in 3720 this document or the extent to which any license under such rights 3721 might or might not be available; neither does it represent that it 3722 has made any effort to identify any such rights. Information on the 3723 IETF's procedures with respect to rights in standards-track and 3724 standards-related documentation can be found in BCP-11. Copies of 3725 claims of rights made available for publication and any assurances of 3726 licenses to be made available, or the result of an attempt made to 3727 obtain a general license or permission for the use of such 3728 proprietary rights by implementors or users of this specification can 3730 Expires December 17, 2002 [PAGE 69] 3731 be obtained from the IETF Secretariat. 3733 The IETF invites any interested party to bring to its attention any 3734 copyrights, patents or patent applications, or other proprietary 3735 rights which may cover technology that may be required to practice 3736 this standard. Please address the information to the IETF Executive 3737 Director. 3739 Authors' Addresses 3741 Bob Ray 3742 PESA Switching Systems, Inc. 3743 330-A Wynn Drive 3744 Huntsville, AL 35805 USA 3746 Phone: +1 256 726 9200 ext. 142 3747 Fax: +1 256 726 9271 3748 EMail: rray@pesa.com 3750 Rajesh Abbi 3751 Alcatel USA 3752 2912 Wake Forest Road 3753 Raleigh, NC 27609-7860 USA 3755 Phone: +1 919 850 6194 3756 EMail: Rajesh.Abbi@alcatel.com 3758 Full Copyright Statement 3760 Copyright (C) The Internet Society (2002). All Rights Reserved. 3762 This document and translations of it may be copied and furnished to 3763 others, and derivative works that comment on or otherwise explain it 3764 or assist in its implementation may be prepared, copied, published 3765 and distributed, in whole or in part, without restriction of any 3766 kind, provided that the above copyright notice and this paragraph are 3767 included on all such copies and derivative works. However, this 3768 document itself may not be modified in any way, such as by removing 3769 the copyright notice or references to the Internet Society or other 3770 Internet organizations, except as needed for the purpose of 3771 developing Internet standards in which case the procedures for 3772 copyrights defined in the Internet Standards process must be 3773 followed, or as required to translate it into languages other than 3774 English. 3776 The limited permissions granted above are perpetual and will not be 3777 revoked by the Internet Society or its successors or assigns. 3778 This document and the information contained herein is provided on an 3779 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 3780 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 3781 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 3782 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 3783 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 3785 Expires December 17, 2002 [PAGE 70]