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