idnits 2.17.1 draft-ietf-adslmib-vdsl-12.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 : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. == 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 2003) is 7522 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) == Unused Reference: 'DSLFTR057' is defined on line 3364, but no explicit reference was found in the text == Unused Reference: 'ETSI2701' is defined on line 3367, but no explicit reference was found in the text == Unused Reference: 'ETSI2702' is defined on line 3372, but no explicit reference was found in the text == Unused Reference: 'ITU9931' is defined on line 3377, but no explicit reference was found in the text == Unused Reference: 'ITU9971' is defined on line 3380, but no explicit reference was found in the text == Unused Reference: 'T1E1311' is defined on line 3416, but no explicit reference was found in the text == Unused Reference: 'T1E1011' is defined on line 3421, but no explicit reference was found in the text == Unused Reference: 'T1E1013' is defined on line 3425, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'DSLFTR057' -- 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' -- Possible downref: Non-RFC (?) normative reference: ref. 'RFCXXXX' -- Possible downref: Non-RFC (?) normative reference: ref. 'T1E1311' -- Possible downref: Non-RFC (?) normative reference: ref. 'T1E1011' -- Possible downref: Non-RFC (?) normative reference: ref. 'T1E1013' Summary: 3 errors (**), 0 flaws (~~), 11 warnings (==), 11 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 2003 7 Definitions of Managed Objects for Very High 8 Speed Digital Subscriber Lines (VDSL) 9 draft-ietf-adslmib-vdsl-12.txt 11 Status of this Memo 13 This document is an Internet-Draft and is in full conformance with 14 all provisions 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 19 Internet-Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six 22 months and may be updated, replaced, or obsoleted by other documents 23 at any time. It is inappropriate to use Internet-Drafts as 24 reference 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/ietf/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 (2003). 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. 43 Table of Contents 45 1. The Internet-Standard Management Framework .................... 2 46 2. Overview ...................................................... 2 47 2.1 Relationship of the VDSL Line MIB Module to other MIB Modules . 3 48 2.2 Conventions used in the MIB Module ............................ 4 49 2.3 Structure ..................................................... 5 50 2.4 Counters, Interval Buckets and Thresholds ..................... 6 51 2.5 Profiles ...................................................... 7 52 2.6 Notifications ................................................. 8 53 2.7 Persistence ................................................... 9 54 3. Conformance and Compliance .................................... 10 55 4. Definitions ................................................... 10 56 5. Intellectual Property ......................................... 64 57 6. Normative References .......................................... 64 58 7. Informative References ........................................ 65 59 8. Security Considerations ....................................... 66 60 9. Acknowledgements .............................................. 67 61 10. Authors' Addresses ............................................ 67 62 11. Full Copyright Statement ...................................... 68 64 1. The Internet-Standard Management Framework 66 For a detailed overview of the documents that describe the current 67 Internet-Standard Management Framework, please refer to section 7 of 68 RFC 3410 [RFC3410]. 70 Managed objects are accessed via a virtual information store, termed 71 the Management Information Base or MIB. MIB objects are generally 72 accessed through the Simple Network Management Protocol (SNMP). 73 Objects in the MIB are defined using the mechanisms defined in the 74 Structure of Management Information (SMI). This memo specifies a 75 MIB module that is compliant to the SMIv2, which is described in STD 76 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 77 2580 [RFC2580]. 79 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 80 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 81 document are to be interpreted as described in [RFC2119]. 83 2. Overview 85 This document describes an SNMP MIB module for managing VDSL Lines. 86 These definitions are based upon the specifications for VDSL as 87 defined in T1E1, ETSI, and ITU documentation [T1E1311, T1E1011, 88 T1E1013, ETSI2701, ETSI2702, ITU9931, ITU9971]. 90 The MIB module is located in the MIB tree under MIB 2 transmission, 91 as discussed in the MIB-2 Integration (RFC 2863 [RFC2863]) section 92 of this document. 94 2.1 Relationship of the VDSL Line MIB Module to other MIB Modules 96 This section outlines the relationship of this MIB with other MIBs 97 described in RFCs. Specifically, IF-MIB as presented in RFC 2863 98 [RFC2863] is discussed. 100 2.1.1 General IF-MIB Integration (RFC 2863) 102 The VDSL Line MIB specifies the detailed attributes of a data 103 interface. As such, it needs to integrate with RFC 2863 [RFC2863]. 104 The IANA has assigned the following ifType to VDSL: 106 IANAifType ::= TEXTUAL-CONVENTION 107 ... 109 SYNTAX INTEGER { 110 ... 111 vdsl(97), -- Very H-speed Digital Subscrib. Loop 112 ... 113 } 115 Additionally, a VDSL line may contain an optional fast channel 116 and an optional interleaved channel which also integrate into RFC 117 2863 [RFC2863]. The IANA has assigned the following ifTypes to 118 these channels: 120 IANAifType ::= TEXTUAL-CONVENTION 121 ... 122 SYNTAX INTEGER { 123 ... 124 interleave (124), -- Interleave channel 125 fast (125), -- Fast channel 126 ... 127 } 129 2.1.2 Usage of ifTable 131 The MIB branch identified by this ifType contains tables appropriate 132 for this interface type. Most such tables extend the ifEntry table, 133 and are indexed by ifIndex. For interfaces in systems implementing 134 this MIB, those table entries indexed by ifIndex MUST be persistent. 136 The following attributes are part of the mandatory ifGeneral group 137 in RFC 2863 [RFC2863], and are not duplicated in the VDSL Line MIB. 139 =================================================================== 140 ifIndex Interface index. 142 ifDescr See interfaces MIB [RFC2863]. 144 ifType vdsl(97), 145 interleave(124), or 146 fast(125) 148 ifSpeed Set as appropriate. 150 ifPhysAddress This object MUST have an octet string 151 with zero length. 153 ifAdminStatus See interfaces MIB [RFC2863]. 155 ifOperStatus See interfaces MIB [RFC2863]. 157 ifLastChange See interfaces MIB [RFC2863]. 159 ifName See interfaces MIB [RFC2863]. 161 ifHighSpeed Set as appropriate. 163 ifConnectorPresent Set as appropriate. 165 ifLinkUpDownTrapEnable Default to enabled(1). 167 =================================================================== 168 Figure 1: Use of ifTable Objects 170 Section 2.3, below, describes the structure of this MIB in relation 171 to ifEntry in greater detail. 173 2.2 Conventions used in the MIB Module 175 2.2.1 Naming Conventions 177 A. Vtuc -- (VTUC) transceiver at near (Central) end of line 178 B. Vtur -- (VTUR) transceiver at Remote end of line 179 C. Vtu -- One of either Vtuc or Vtur 180 D. Curr -- Current 181 E. Prev -- Previous 182 F. Atn -- Attenuation 183 G. ES -- Errored Second 184 H. SES -- Severely Errored Second 185 I. UAS -- Unavailable Second 186 J. LCS -- Line Code Specific 187 K. Lof -- Loss of Frame 188 L. Lol -- Loss of Link 189 M. Los -- Loss of Signal 190 N. Lpr -- Loss of Power 191 O. xxxs -- Sum of Seconds in which xxx has occured 192 (e.g., xxx = Lof, Los, Lpr, Lol) 193 P. Max -- Maximum 194 Q. Mgn -- Margin 195 R. Min -- Minimum 196 S. Psd -- Power Spectral Density 197 T. Snr -- Signal to Noise Ratio 198 U. Tx -- Transmit 199 V. Blks -- Blocks 201 2.2.2 Textual Conventions 203 The following textual conventions are defined to reflect the line 204 topology in the MIB (further discussed in the following section) 205 and to define the behavior of the statistics to be maintained 206 by an agent. 208 o VdslLineCodingType : 210 Attributes with this syntax identify the line coding used. 211 Specified as an INTEGER, the three values are: 213 other(1) -- none of the following 214 mcm(2) -- Multiple Carrier Modulation 215 scm(3) -- Single Carrier Modulation 217 o VdslLineEntity : 219 Attributes with this syntax reference the two sides of a line. 220 Specified as an INTEGER, the two values are: 222 vtuc(1) -- central site transceiver 223 vtur(2) -- remote site transceiver 225 2.3 Structure 227 The MIB is structured into the following MIB groups: 229 o vdslGroup : 231 This group supports all line code independent MIB objects found 232 in this MIB. The following tables contain objects permitted for 233 ifType vdsl(97): 235 - vdslLineTable 236 - vdslPhysTable 237 - vdslPerfDataTable 238 - vdslPerfIntervalTable 239 - vdslPerf1DayIntervalTable 240 - vdslLineConfProfileTable 241 - vdslLineAlarmConfProfileTable 243 The following tables contain objects permitted for ifTypes 244 interleave(124) and (fast): 246 - vdslChanTable 247 - vdslChanPerfDataTable 248 - vdslChanPerfIntervalTable 249 - vdslChanPerf1DayIntervalTable 251 Figure 2, below, displays the relationship of the tables in the 252 vdslGroup to ifEntry (and each other): 254 ifEntry(ifType=97) ---> vdslLineTableEntry 1:(0 to 1) 256 vdslLineTableEntry ---> vdslPhysTableEntry 1:(0 to 2) 257 ---> vdslPerfDataEntry 1:(0 to 2) 258 ---> vdslLineConfProfileEntry 1:(0 to 1) 259 ---> vdslLineAlarmConfProfileEntry 1:(0 to 1) 261 vdslPhysTableEntry ---> vdslPerfIntervalEntry 1:(0 to 96) 262 ---> vdslPerf1DayIntervalEntry 1:(0 to 30) 264 ifEntry(ifType=124) ---> vdslChanEntry 1:(0 to 2) 265 ---> vdslChanPerfDataEntry 1:(0 to 2) 267 ifEntry(ifType=125) ---> vdslChanEntry 1:(0 to 2) 268 ---> vdslChanPerfDataEntry 1:(0 to 2) 270 vdslChanEntry ---> vdslchanPerfIntervalEntry 1:(0 to 96) 271 ---> vdslchan1DayPerfIntervalEntry 1:(0 to 30) 273 Figure 2: Table Relationships 275 o vdslNotificationGroup : 277 This group contains definitions of VDSL line notifications. Section 278 2.6, below, presents greater detail on the notifications defined 279 within the MIB module. 281 2.3.1 Line Topology 283 A VDSL Line consists of two units - a Vtuc (the central tranceiver 284 unit) and a Vtur (the remote transceiver unit). 286 <-- Network Side Customer Side --> 288 || 290 +-------+ +-------+ 291 | | | | 292 | Vtuc +------------------+ Vtur | 293 | | | | 294 +-------+ +-------+ 296 Figure 3: General topology for a VDSL Line 298 2.4 Counters, Interval Buckets and Thresholds 300 For Loss of Frame (lof), Loss of Link (lol), Loss of Signal (los), 301 and Loss of Power (lpr), Errored Seconds (ES), Severely Errored 302 Seconds (SES), and Unavailable Seconds (UAS) there are event 303 counters, current 15-minute, 0 to 96 15-minute history bucket(s), 304 and 0 to 30 1-day history bucket(s) of "interval-counters". Each 305 current 15-minute event bucket has an associated threshold 306 notification. 308 Each of these counters uses the textual conventions defined in the 309 HC-PerfHist-TC-MIB [RFCXXXX]. The HC-PerfHist-TC-MIB defines 64- 310 --- RFC Ed: please replace XXXX with the RFC number assigned to the 311 --- accompanying HC-TC MIB 312 bit versions of the textual conventions found in RFC 3593 [RFC3593]. 314 There is no requirement for an agent to ensure a fixed relationship 315 between the start of a fifteen minute interval and any wall clock; 316 however, some implementations may align the fifteen minute intervals 317 with quarter hours. Likewise, an implementation may choose to align 318 one day intervals with the start of a day. 320 Counters are not reset when a Vtu is reinitialized, only when the 321 agent is reset or reinitialized (or under specific request outside 322 the scope of this MIB module). 324 2.5 Profiles 326 As a managed node can handle a large number of Vtus, (e.g., hundreds 327 or perhaps thousands of lines), provisioning every parameter on 328 every Vtu may become burdensome. Moreover, most lines are 329 provisioned identically with the same set of parameters. To 330 simplify the provisioning process, this MIB makes use of profiles. 331 A profile is a set of parameters that can be shared by multiple 332 lines using the same configuration. 334 The following profiles are used in this MIB module: 336 o Line Configuration Profiles - Line configuration profiles 337 contain parameters for configuring VDSL lines. They are defined 338 in the vdslLineConfProfileTable. 340 o Alarm Configuration Profiles - These profiles contain parameters 341 for configuring alarm thresholds for VDSL transceivers. These 342 profiles are defined in the vdslLineAlarmConfProfileTable. 344 One or more lines may be configured to share parameters of a single 345 profile by setting their vdslLineConfProfile objects to the value of 346 this profile. If a change is made to the profile, all lines that 347 refer to it will be reconfigured to the changed parameters. Before 348 a profile can be deleted or taken out of service it must be first 349 unreferenced from all associated lines. 351 Implementations MUST provide a default profile with an index value 352 of 'DEFVAL' for each profile type. The values of the associated 353 parameters will be vendor specific unless otherwise indicated in 354 this document. Before a line's profiles have been set, these 355 profiles will be automatically used by setting vdslLineConfProfile 356 and vdslLineAlarmConfProfile to 'DEFVAL' where appropriate. This 357 default profile name, 'DEFVAL', is considered reserved in the 358 context of profiles defined in this MIB module. 360 Profiles are created, assigned, and deleted dynamically using the 361 profile name and profile row status in each of the ten profile 362 tables (nine line configuration tables and one alarm configuration 363 table). 365 Profile changes MUST take effect immediately. These changes MAY 366 result in a restart (hard reset or soft restart) of the units on the 367 line. 369 2.6 Notifications 371 The ability to generate the SNMP notifications coldStart/WarmStart 372 (per [RFC3418]) which are per agent (e.g., per Digital Subscriber 373 Line Access Multiplexer, or DSLAM, in such a device), and 374 linkUp/linkDown (per [RFC2863]) which are per interface (i.e., VDSL 375 line) is required. 377 The notifications defined in this MIB are for initialization failure 378 and for the threshold crossings associated with the following 379 events: lof, lol, los, lpr, ES, SES, and UAS. Each threshold has 380 its own enable/threshold value. When that value is 0, the 381 notification is disabled. 383 A linkDown notification MAY be generated whenever any of lof, lol, 384 los, lpr, ES, SES, or UAS threshold crossing event (as defined 385 in this MIB module) occurs. The corresponding linkUp notification 386 MAY be sent when all link failure conditions are cleared. 388 The vdslPhysCurrStatus is a bitmask representing all outstanding 389 error conditions associated with a particular VDSL transceiver. 390 Note that since status of remote transceivers is obtained via the 391 EOC, this information may be unavailable for units that are 392 unreachable via the EOC during a line error condition. Therefore, 393 not all conditions may always be included in its current status. 394 Notifications corresponding to the bit fields in this object are 395 defined. 397 A threshold notification occurs whenever the corresponding current 398 15-minute interval error counter becomes equal to, or exceeds the 399 threshold value. One notification may be sent per interval per 400 interface. Since the current 15-minute counters are reset to 0 401 every 15 minutes, if the condition persists, the notification may 402 recur as often as every 15 minutes. For example, to get a 403 notification whenever a "loss of" event occurs (but at most once 404 every 15 minutes), set the corresponding threshold to 1. The agent 405 will generate a notification when the event originally occurs. 407 Note that the Network Management System, or NMS, may receive a 408 linkDown notification, as well, if enabled (via 409 ifLinkUpDownTrapEnable [RFC2863]). At the beginning of the next 15 410 minute interval, the counter is reset. When the first second goes 411 by and the event occurs, the current interval bucket will be 1, 412 which equals the threshold and the notification will be sent again. 414 2.7 Persistence 416 All read-write and read-create objects defined in this MIB module 417 SHOULD be stored persistently. Following is an exhaustive list of 418 these persistent objects: 420 vdslLineConfProfile 421 vdslLineAlarmConfProfile 422 vdslLineConfProfileName 423 vdslLineConfDownRateMode 424 vdslLineConfUpRateMode 425 vdslLineConfDownMaxPwr 426 vdslLineConfUpMaxPwr 427 vdslLineConfDownMaxSnrMgn 428 vdslLineConfDownMinSnrMgn 429 vdslLineConfDownTargetSnrMgn 430 vdslLineConfUpMaxSnrMgn 431 vdslLineConfUpMinSnrMgn 432 vdslLineConfUpTargetSnrMgn 433 vdslLineConfDownFastMaxDataRate 434 vdslLineConfDownFastMinDataRate 435 vdslLineConfDownSlowMaxDataRate 436 vdslLineConfDownSlowMinDataRate 437 vdslLineConfUpFastMaxDataRate 438 vdslLineConfUpFastMinDataRate 439 vdslLineConfUpSlowMaxDataRate 440 vdslLineConfUpSlowMinDataRate 441 vdslLineConfDownRateRatio 442 vdslLineConfUpRateRatio 443 vdslLineConfDownMaxInterDelay 444 vdslLineConfUpMaxInterDelay 445 vdslLineConfDownPboControl 446 vdslLineConfUpPboControl 447 vdslLineConfDownPboLevel 448 vdslLineConfUpPboLevel 449 vdslLineConfDeploymentScenario 450 vdslLineConfAdslPresence 451 vdslLineConfApplicableStandard 452 vdslLineConfBandPlan 453 vdslLineConfBandPlanFx 454 vdslLineConfBandOptUsage 455 vdslLineConfUpPsdTemplate 456 vdslLineConfDownPsdTemplate 457 vdslLineConfHamBandMask 458 vdslLineConfCustomNotch1Start 459 vdslLineConfCustomNotch1Stop 460 vdslLineConfCustomNotch2Start 461 vdslLineConfCustomNotch2Stop 462 vdslLineConfDownTargetSlowBurst 463 vdslLineConfUpTargetSlowBurst 464 vdslLineConfDownMaxFastFec 465 vdslLineConfUpMaxFastFec 466 vdslLineConfLineType 467 vdslLineConfProfRowStatus 468 vdslLineAlarmConfProfileName 469 vdslLineAlarmConfThresh15MinLofs 470 vdslLineAlarmConfThresh15MinLoss 471 vdslLineAlarmConfThresh15MinLprs 472 vdslLineAlarmConfThresh15MinLols 473 vdslLineAlarmConfThresh15MinESs 474 vdslLineAlarmConfThresh15MinSESs 475 vdslLineAlarmConfThresh15MinUASs 476 vdslLineAlarmConfInitFailure 477 vdslLineAlarmConfProfRowStatus 479 It should also be noted that interface indices in this MIB are 480 maintained persistently. VACM data relating to these SHOULD be 481 stored persistently as well [RFC3415]. 483 3. Conformance and Compliance 485 For VDSL lines, the following groups are mandatory: 487 - vdslGroup 488 - vdslNotificationGroup 490 4. Definitions 492 VDSL-LINE-MIB DEFINITIONS ::= BEGIN 494 IMPORTS 496 MODULE-IDENTITY, 497 OBJECT-TYPE, 498 Gauge32, 499 Integer32, 500 Unsigned32, 501 NOTIFICATION-TYPE, 502 transmission FROM SNMPv2-SMI 503 ZeroBasedCounter64 FROM HCNUM-TC 504 TEXTUAL-CONVENTION, 505 RowStatus, 506 TruthValue FROM SNMPv2-TC 507 HCPerfValidIntervals, 508 HCPerfInvalidIntervals, 509 HCPerfTimeElapsed, 510 HCPerfIntervalThreshold, 511 HCPerfCurrentCount, 512 HCPerfIntervalCount FROM HC-PerfHist-TC-MIB 513 MODULE-COMPLIANCE, 514 OBJECT-GROUP, 515 NOTIFICATION-GROUP FROM SNMPv2-CONF 516 ifIndex FROM IF-MIB 517 SnmpAdminString FROM SNMP-FRAMEWORK-MIB; 518 vdslMIB MODULE-IDENTITY 519 LAST-UPDATED "200309240000Z" -- September 24, 2003 520 ORGANIZATION "ADSLMIB Working Group" 521 CONTACT-INFO "WG-email: adslmib@ietf.org 522 Info: https://www1.ietf.org/mailman/listinfo/adslmib 524 Chair: Mike Sneed 525 Sand Channel Systems 526 Postal: P.O. Box 37324 527 Raleigh, NC 27627-7324 528 USA 529 Email: sneedmike@hotmail.com 530 Phone: +1 206 600 7022 532 Co-editor: Bob Ray 533 PESA Switching Systems, Inc. 534 Postal: 330-A Wynn Drive 535 Huntsville, AL 35805 536 USA 537 Email: rray@pesa.com 538 Phone: +1 256 726 9200 ext. 142 540 Co-editor: Rajesh Abbi 541 Alcatel USA 542 Postal: 2912 Wake Forest Road 543 Raleigh, NC 27609-7860 544 USA 545 Email: Rajesh.Abbi@alcatel.com 546 Phone: +1 919 850 6194 547 " 548 DESCRIPTION 549 "The MIB module defining objects for the management of a pair 550 of VDSL transceivers at each end of the VDSL line. Each such 551 line has an entry in an ifTable which may include multiple 552 transceiver lines. An agent may reside at either end of the 553 VDSL line. However, the MIB is designed to require no 554 management communication between them beyond that inherent in 555 the low-level VDSL line protocol. The agent may monitor and 556 control this protocol for its needs. 558 VDSL lines may support optional Fast or Interleaved channels. 559 If these are supported, additional entries corresponding to the 560 supported channels must be created in the ifTable. Thus a VDSL 561 line that supports both channels will have three entries in the 562 ifTable, one for each physical, fast, and interleaved, whose 563 ifType values are equal to vdsl(97), fast(125), and 564 interleaved(124), respectively. The ifStackTable is used to 565 represent the relationship between the entries. 567 Naming Conventions: 568 Vtuc -- (VTUC) transceiver at near (Central) end of line 569 Vtur -- (VTUR) transceiver at Remote end of line 570 Vtu -- One of either Vtuc or Vtur 571 Curr -- Current 572 Prev -- Previous 573 Atn -- Attenuation 574 ES -- Errored Second. 575 SES -- Severely Errored Second 576 UAS -- Unavailable Second 577 LCS -- Line Code Specific 578 Lof -- Loss of Frame 579 Lol -- Loss of Link 580 Los -- Loss of Signal 581 Lpr -- Loss of Power 582 xxxs -- Sum of Seconds in which xxx has occured 583 (e.g., xxx = Lof, Los, Lpr, Lol) 584 Max -- Maximum 585 Mgn -- Margin 586 Min -- Minimum 587 Psd -- Power Spectral Density 588 Snr -- Signal to Noise Ratio 589 Tx -- Transmit 590 Blks -- Blocks 592 Copyright (C) The Internet Society (2003). This version 593 of this MIB module is part of RFC XXXX: see the RFC 594 itself for full legal notices." 595 -- RFC Ed.: replace XXXX with assigned number & remove this note 596 REVISION "200309240000Z" -- September 24, 2003 597 DESCRIPTION "Initial version, published as RFC XXXX." 598 -- RFC Ed.: replace XXXX with assigned number & remove this note 599 ::= { transmission YYYY } -- To be assigned by IANA 600 -- RFC Ed.: we suggest to put it under { transmission 97 } because 601 -- 97 is the value of the main ifType for the MIB objects 602 -- defined in this MIB module. 604 vdslLineMib OBJECT IDENTIFIER ::= { vdslMIB 1 } 605 vdslMibObjects OBJECT IDENTIFIER ::= { vdslLineMib 1 } 607 -- 608 -- textual conventions used in this MIB 609 -- 611 VdslLineCodingType ::= TEXTUAL-CONVENTION 612 STATUS current 613 DESCRIPTION 614 "This data type is used as the syntax for the VDSL Line 615 Code. Attributes with this syntax identify the line coding 616 used. Specified as an INTEGER, the three values are: 618 other(1) -- none of the following 619 mcm(2) -- Multiple Carrier Modulation 620 scm(3) -- Single Carrier Modulation" 621 SYNTAX INTEGER 622 { 623 other(1), 624 mcm(2), 625 scm(3) 626 } 628 VdslLineEntity ::= TEXTUAL-CONVENTION 629 STATUS current 630 DESCRIPTION 631 "Identifies a transceiver as being either Vtuc or Vtur. 632 A VDSL line consists of two transcievers, a Vtuc and a 633 Vtur. Attributes with this syntax reference the two sides 634 of a line. Specified as an INTEGER, the two values are: 636 vtuc(1) -- central site transceiver 637 vtur(2) -- remote site transceiver" 638 SYNTAX INTEGER 639 { 640 vtuc(1), 641 vtur(2) 642 } 644 -- 645 -- objects 646 -- 648 vdslLineTable OBJECT-TYPE 649 SYNTAX SEQUENCE OF VdslLineEntry 650 MAX-ACCESS not-accessible 651 STATUS current 652 DESCRIPTION 653 "This table includes common attributes describing 654 both ends of the line. It is required for all VDSL 655 physical interfaces. VDSL physical interfaces are 656 those ifEntries where ifType is equal to vdsl(97)." 657 ::= { vdslMibObjects 1 } 659 vdslLineEntry OBJECT-TYPE 660 SYNTAX VdslLineEntry 661 MAX-ACCESS not-accessible 662 STATUS current 663 DESCRIPTION "An entry in the vdslLineTable." 664 INDEX { ifIndex } 665 ::= { vdslLineTable 1 } 667 VdslLineEntry ::= 668 SEQUENCE 669 { 670 vdslLineCoding VdslLineCodingType, 671 vdslLineType INTEGER, 672 vdslLineConfProfile SnmpAdminString, 673 vdslLineAlarmConfProfile SnmpAdminString 674 } 676 vdslLineCoding OBJECT-TYPE 677 SYNTAX VdslLineCodingType 678 MAX-ACCESS read-only 679 STATUS current 680 DESCRIPTION 681 "Specifies the VDSL coding type used on this line." 682 REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" 683 ::= { vdslLineEntry 1 } 685 vdslLineType OBJECT-TYPE 686 SYNTAX INTEGER 687 { 688 noChannel(1), -- no channels exist 689 fastOnly(2), -- only fast channel exists 690 interleavedOnly(3), -- only interleaved channel exists 691 fastOrInterleaved(4), -- either fast or interleaved channel 692 -- exist, but only one at a time 693 fastAndInterleaved(5) -- both fast and interleaved channels 694 -- exist 695 } 696 MAX-ACCESS read-only 697 STATUS current 698 DESCRIPTION 699 "Defines the type of VDSL physical line entity that exists, 700 by defining whether and how the line is channelized. If 701 the line is channelized, the value will be other than 702 noChannel(1). This object defines which channel type(s) 703 are supported. Defined values are: 705 noChannel(1) -- no channels exist 706 fastOnly(2) -- only fast channel exists 707 interleavedOnly(3) -- only interleaved channel exists 708 fastOrInterleaved(4) -- either fast or interleaved channel 709 -- exist, but only one at a time 710 fastAndInterleaved(5) -- both fast and interleaved channels 711 -- exist 713 Note that 'slow' and 'interleaved' refer to the same 714 channel. In the case that the line is channelized, the 715 manager can use the ifStackTable to determine the ifIndex 716 for the associated channel(s)." 717 REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" 718 ::= { vdslLineEntry 2 } 720 vdslLineConfProfile OBJECT-TYPE 721 SYNTAX SnmpAdminString (SIZE(1..32)) 722 MAX-ACCESS read-write 723 STATUS current 724 DESCRIPTION 725 "The value of this object identifies the row in the VDSL 726 Line Configuration Profile Table, vdslLineConfProfileTable, 727 which applies for this VDSL line, and channels if 728 applicable. 730 This object MUST be maintained in a persistent manner." 731 DEFVAL { "DEFVAL" } 732 ::= { vdslLineEntry 3 } 734 vdslLineAlarmConfProfile OBJECT-TYPE 735 SYNTAX SnmpAdminString (SIZE(1..32)) 736 MAX-ACCESS read-write 737 STATUS current 738 DESCRIPTION 739 "The value of this object identifies the row in the VDSL 740 Line Alarm Configuration Profile Table, 741 vdslLineAlarmConfProfileTable, which applies to this 742 VDSL line, and channels if applicable. 744 This object MUST be maintained in a persistent manner." 745 DEFVAL { "DEFVAL" } 746 ::= { vdslLineEntry 4 } 748 vdslPhysTable OBJECT-TYPE 749 SYNTAX SEQUENCE OF VdslPhysEntry 750 MAX-ACCESS not-accessible 751 STATUS current 752 DESCRIPTION 753 "This table provides one row for each Vtu. Each row 754 contains the Physical Layer Parameters table for that 755 Vtu. VDSL physical interfaces are those ifEntries where 756 ifType is equal to vdsl(97)." 757 ::= { vdslMibObjects 2 } 759 vdslPhysEntry OBJECT-TYPE 760 SYNTAX VdslPhysEntry 761 MAX-ACCESS not-accessible 762 STATUS current 763 DESCRIPTION "An entry in the vdslPhysTable." 764 INDEX { ifIndex, 765 vdslPhysSide } 766 ::= { vdslPhysTable 1 } 768 VdslPhysEntry ::= 769 SEQUENCE 770 { 771 vdslPhysSide VdslLineEntity, 772 vdslPhysInvSerialNumber SnmpAdminString, 773 vdslPhysInvVendorID SnmpAdminString, 774 vdslPhysInvVersionNumber SnmpAdminString, 775 vdslPhysCurrSnrMgn Integer32, 776 vdslPhysCurrAtn Gauge32, 777 vdslPhysCurrStatus BITS, 778 vdslPhysCurrOutputPwr Integer32, 779 vdslPhysCurrAttainableRate Gauge32, 780 vdslPhysCurrLineRate Gauge32 781 } 783 vdslPhysSide OBJECT-TYPE 784 SYNTAX VdslLineEntity 785 MAX-ACCESS not-accessible 786 STATUS current 787 DESCRIPTION 788 "Identifies whether the transceiver is the Vtuc or Vtur." 789 ::= { vdslPhysEntry 1 } 791 vdslPhysInvSerialNumber OBJECT-TYPE 792 SYNTAX SnmpAdminString(SIZE (0..32)) 793 MAX-ACCESS read-only 794 STATUS current 795 DESCRIPTION 796 "The vendor specific string that identifies the 797 vendor equipment." 798 REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" 799 ::= { vdslPhysEntry 2 } 801 vdslPhysInvVendorID OBJECT-TYPE 802 SYNTAX SnmpAdminString (SIZE (0..16)) 803 MAX-ACCESS read-only 804 STATUS current 805 DESCRIPTION 806 "The vendor ID code is a copy of the binary vendor 807 identification field expressed as readable characters 808 in hexadecimal notation." 809 REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" 810 ::= { vdslPhysEntry 3 } 812 vdslPhysInvVersionNumber OBJECT-TYPE 813 SYNTAX SnmpAdminString (SIZE (0..16)) 814 MAX-ACCESS read-only 815 STATUS current 816 DESCRIPTION 817 "The vendor specific version number sent by this Vtu 818 as part of the initialization messages. It is a copy 819 of the binary version number field expressed as 820 readable characters in hexadecimal notation." 821 REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" 822 ::= { vdslPhysEntry 4 } 824 vdslPhysCurrSnrMgn OBJECT-TYPE 825 SYNTAX Integer32 (-127..127) 826 UNITS "0.25dBm" 827 MAX-ACCESS read-only 828 STATUS current 829 DESCRIPTION 830 "Noise Margin as seen by this Vtu with respect to its 831 received signal in 0.25dB. The effective range is 832 -31.75 to +31.75 dB." 833 REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" 834 ::= { vdslPhysEntry 5 } 836 vdslPhysCurrAtn OBJECT-TYPE 837 SYNTAX Gauge32 (0..255) 838 UNITS "0.25dBm" 839 MAX-ACCESS read-only 840 STATUS current 841 DESCRIPTION 842 "Measured difference in the total power transmitted by 843 the peer Vtu and the total power received by this Vtu. 844 The effective range is 0 to +63.75 dB." 845 REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" 846 ::= { vdslPhysEntry 6 } 848 vdslPhysCurrStatus OBJECT-TYPE 849 SYNTAX BITS 850 { 851 noDefect(0), 852 lossOfFraming(1), 853 lossOfSignal(2), 854 lossOfPower(3), 855 lossOfSignalQuality(4), 856 lossOfLink(5), 857 dataInitFailure(6), 858 configInitFailure(7), 859 protocolInitFailure(8), 860 noPeerVtuPresent(9) 861 } 862 MAX-ACCESS read-only 863 STATUS current 864 DESCRIPTION 865 "Indicates current state of the Vtu line. This is a 866 bit-map of possible conditions. The various bit 867 positions are: 869 0 noDefect There are no defects on the line. 871 1 lossOfFraming Vtu failure due to not receiving 872 a valid frame. 874 2 lossOfSignal Vtu failure due to not receiving 875 signal. 877 3 lossOfPower Vtu failure due to loss of power. 879 4 lossOfSignalQuality Loss of Signal Quality is declared 880 when the Noise Margin falls below 881 the Minimum Noise Margin, or the 882 bit-error-rate exceeds 10^-7. 884 5 lossOfLink Vtu failure due to inability to 885 link with peer Vtu. Set whenever 886 the transceiver is in the 'Warm 887 Start' state. 889 6 dataInitFailure Vtu failure during initialization 890 due to bit errors corrupting 891 startup exchange data. 893 7 configInitFailure Vtu failure during initialization 894 due to peer Vtu not able to 895 support requested configuration. 897 8 protocolInitFailure Vtu failure during initialization 898 due to incompatible protocol used 899 by the peer Vtu. 901 9 noPeerVtuPresent Vtu failure during initialization 902 due to no activation sequence 903 detected from peer Vtu. 905 This is intended to supplement ifOperStatus." 906 REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" 907 ::= { vdslPhysEntry 7 } 909 vdslPhysCurrOutputPwr OBJECT-TYPE 910 SYNTAX Integer32 (0..160) 911 UNITS "0.1dBm" 912 MAX-ACCESS read-only 913 STATUS current 914 DESCRIPTION 915 "Measured total output power transmitted by this VTU. 916 This is the measurement that was reported during 917 the last activation sequence." 918 REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" 919 ::= { vdslPhysEntry 8 } 921 vdslPhysCurrAttainableRate OBJECT-TYPE 922 SYNTAX Gauge32 923 UNITS "kbps" 924 MAX-ACCESS read-only 925 STATUS current 926 DESCRIPTION 927 "Indicates the maximum currently attainable data rate 928 in steps of 1000 bits/second by the Vtu. This value 929 will be equal to or greater than vdslPhysCurrLineRate. 930 Note that for SCM, the minimum and maximum data rates 931 are equal. Note: 1 kbps = 1000 bps." 932 REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" 933 ::= { vdslPhysEntry 9 } 935 vdslPhysCurrLineRate OBJECT-TYPE 936 SYNTAX Gauge32 937 UNITS "kbps" 938 MAX-ACCESS read-only 939 STATUS current 940 DESCRIPTION 941 "Indicates the current data rate in steps of 1000 942 bits/second by the Vtu. This value will be less than 943 or equal to vdslPhysCurrAttainableRate. Note: 1 kbps = 944 1000 bps." 945 REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" 946 ::= { vdslPhysEntry 10 } 948 vdslChanTable OBJECT-TYPE 949 SYNTAX SEQUENCE OF VdslChanEntry 950 MAX-ACCESS not-accessible 951 STATUS current 952 DESCRIPTION 953 "This table provides one row for each Vtu channel. 954 VDSL channel interfaces are those ifEntries where 955 ifType is equal to interleave(124) or fast(125)." 956 ::= { vdslMibObjects 3 } 958 vdslChanEntry OBJECT-TYPE 959 SYNTAX VdslChanEntry 960 MAX-ACCESS not-accessible 961 STATUS current 962 DESCRIPTION 963 "An entry in the vdslChanTable." 964 INDEX { ifIndex, 965 vdslPhysSide } 966 ::= { vdslChanTable 1 } 968 VdslChanEntry ::= 969 SEQUENCE 970 { 971 vdslChanInterleaveDelay Gauge32, 972 vdslChanCrcBlockLength Gauge32, 973 vdslChanCurrTxRate Gauge32, 974 vdslChanCurrTxSlowBurstProtect Gauge32, 975 vdslChanCurrTxFastFec Gauge32 976 } 978 vdslChanInterleaveDelay OBJECT-TYPE 979 SYNTAX Gauge32 980 UNITS "milliseconds" 981 MAX-ACCESS read-only 982 STATUS current 983 DESCRIPTION 984 "Interleave Delay for this channel. 986 Interleave delay applies only to the interleave 987 (slow) channel and defines the mapping (relative 988 spacing) between subsequent input bytes at the 989 interleaver input and their placement in the bit 990 stream at the interleaver output. Larger numbers 991 provide greater separation between consecutive 992 input bytes in the output bit stream allowing for 993 improved impulse noise immunity at the expense of 994 payload latency. 996 In the case where the ifType is fast(125), return 997 a value of zero." 998 REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" 999 ::= { vdslChanEntry 1 } 1001 vdslChanCrcBlockLength OBJECT-TYPE 1002 SYNTAX Gauge32 1003 UNITS "bytes" 1004 MAX-ACCESS read-only 1005 STATUS current 1006 DESCRIPTION 1007 "Indicates the length of the channel data-block 1008 on which the CRC operates." 1009 REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" 1010 ::= { vdslChanEntry 2 } 1012 vdslChanCurrTxRate OBJECT-TYPE 1013 SYNTAX Gauge32 1014 UNITS "kbps" 1015 MAX-ACCESS read-only 1016 STATUS current 1017 DESCRIPTION 1018 "Actual transmit data rate on this channel. Note: 1 1019 kbps = 1000 bps." 1020 ::= { vdslChanEntry 3 } 1022 vdslChanCurrTxSlowBurstProtect OBJECT-TYPE 1023 SYNTAX Gauge32 (0..1275) 1024 UNITS "microseconds" 1025 MAX-ACCESS read-only 1026 STATUS current 1027 DESCRIPTION 1028 "Actual level of impulse noise (burst) protection 1029 for an interleaved (slow) channel. This parameter is 1030 not applicable to fast channels. For fast channels, 1031 a value of zero shall be returned." 1032 REFERENCE "ITU-T G.997.1, section 7.3.2.3" 1033 ::= { vdslChanEntry 4 } 1035 vdslChanCurrTxFastFec OBJECT-TYPE 1036 SYNTAX Gauge32 (0..50) 1037 UNITS "%" 1038 MAX-ACCESS read-only 1039 STATUS current 1040 DESCRIPTION 1041 "Actual Forward Error Correction (FEC) redundancy 1042 related overhead for a fast channel. This parameter 1043 is not applicable to an interleaved (slow) channel. 1044 For interleaved channels, a value of zero shall be 1045 returned." 1046 ::= { vdslChanEntry 5 } 1048 vdslPerfDataTable OBJECT-TYPE 1049 SYNTAX SEQUENCE OF VdslPerfDataEntry 1050 MAX-ACCESS not-accessible 1051 STATUS current 1052 DESCRIPTION 1053 "This table provides one row for each VDSL physical 1054 interface. VDSL physical interfaces are those ifEntries 1055 where ifType is equal to vdsl(97)." 1056 ::= { vdslMibObjects 4 } 1058 vdslPerfDataEntry OBJECT-TYPE 1059 SYNTAX VdslPerfDataEntry 1060 MAX-ACCESS not-accessible 1061 STATUS current 1062 DESCRIPTION 1063 "An entry in the vdslPerfDataTable." 1064 INDEX { ifIndex, 1065 vdslPhysSide } 1066 ::= { vdslPerfDataTable 1 } 1068 VdslPerfDataEntry ::= 1069 SEQUENCE 1070 { 1071 vdslPerfDataValidIntervals HCPerfValidIntervals, 1072 vdslPerfDataInvalidIntervals HCPerfInvalidIntervals, 1073 vdslPerfDataLofs Unsigned32, 1074 vdslPerfDataLoss Unsigned32, 1075 vdslPerfDataLprs Unsigned32, 1076 vdslPerfDataLols Unsigned32, 1077 vdslPerfDataESs Unsigned32, 1078 vdslPerfDataSESs Unsigned32, 1079 vdslPerfDataUASs Unsigned32, 1080 vdslPerfDataInits Unsigned32, 1081 vdslPerfDataCurr15MinTimeElapsed HCPerfTimeElapsed, 1082 vdslPerfDataCurr15MinLofs HCPerfCurrentCount, 1083 vdslPerfDataCurr15MinLoss HCPerfCurrentCount, 1084 vdslPerfDataCurr15MinLprs HCPerfCurrentCount, 1085 vdslPerfDataCurr15MinLols HCPerfCurrentCount, 1086 vdslPerfDataCurr15MinESs HCPerfCurrentCount, 1087 vdslPerfDataCurr15MinSESs HCPerfCurrentCount, 1088 vdslPerfDataCurr15MinUASs HCPerfCurrentCount, 1089 vdslPerfDataCurr15MinInits HCPerfCurrentCount, 1090 vdslPerfData1DayValidIntervals HCPerfValidIntervals, 1091 vdslPerfData1DayInvalidIntervals HCPerfInvalidIntervals, 1092 vdslPerfDataCurr1DayTimeElapsed HCPerfTimeElapsed, 1093 vdslPerfDataCurr1DayLofs Unsigned32, 1094 vdslPerfDataCurr1DayLoss Unsigned32, 1095 vdslPerfDataCurr1DayLprs Unsigned32, 1096 vdslPerfDataCurr1DayLols Unsigned32, 1097 vdslPerfDataCurr1DayESs Unsigned32, 1098 vdslPerfDataCurr1DaySESs Unsigned32, 1099 vdslPerfDataCurr1DayUASs Unsigned32, 1100 vdslPerfDataCurr1DayInits Unsigned32 1101 } 1103 vdslPerfDataValidIntervals OBJECT-TYPE 1104 SYNTAX HCPerfValidIntervals 1105 UNITS "intervals" 1106 MAX-ACCESS read-only 1107 STATUS current 1108 DESCRIPTION 1109 "Valid Intervals per definition found in 1110 HC-PerfHist-TC-MIB." 1111 ::= { vdslPerfDataEntry 1 } 1113 vdslPerfDataInvalidIntervals OBJECT-TYPE 1114 SYNTAX HCPerfInvalidIntervals 1115 UNITS "intervals" 1116 MAX-ACCESS read-only 1117 STATUS current 1118 DESCRIPTION 1119 "Invalid Intervals per definition found in 1120 HC-PerfHist-TC-MIB." 1121 ::= { vdslPerfDataEntry 2 } 1123 vdslPerfDataLofs OBJECT-TYPE 1124 SYNTAX Unsigned32 1125 UNITS "seconds" 1126 MAX-ACCESS read-only 1127 STATUS current 1128 DESCRIPTION 1129 "Count of seconds since the unit was last reset that there 1130 was Loss of Framing." 1131 REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" 1132 ::= { vdslPerfDataEntry 3 } 1134 vdslPerfDataLoss OBJECT-TYPE 1135 SYNTAX Unsigned32 1136 UNITS "seconds" 1137 MAX-ACCESS read-only 1138 STATUS current 1139 DESCRIPTION 1140 "Count of seconds since the unit was last reset that there 1141 was Loss of Signal." 1142 REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" 1143 ::= { vdslPerfDataEntry 4 } 1145 vdslPerfDataLprs OBJECT-TYPE 1146 SYNTAX Unsigned32 1147 UNITS "seconds" 1148 MAX-ACCESS read-only 1149 STATUS current 1150 DESCRIPTION 1151 "Count of seconds since the unit was last reset that there 1152 was Loss of Power." 1154 REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" 1155 ::= { vdslPerfDataEntry 5 } 1157 vdslPerfDataLols OBJECT-TYPE 1158 SYNTAX Unsigned32 1159 UNITS "seconds" 1160 MAX-ACCESS read-only 1161 STATUS current 1162 DESCRIPTION 1163 "Count of seconds since the unit was last reset that there 1164 was Loss of Link." 1165 ::= { vdslPerfDataEntry 6 } 1167 vdslPerfDataESs OBJECT-TYPE 1168 SYNTAX Unsigned32 1169 UNITS "seconds" 1170 MAX-ACCESS read-only 1171 STATUS current 1172 DESCRIPTION 1173 "Count of Errored Seconds since the unit was last reset. 1174 An Errored Second is a one-second interval containing one 1175 or more CRC anomalies, or one or more LOS or LOF defects." 1176 REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" 1177 ::= { vdslPerfDataEntry 7 } 1179 vdslPerfDataSESs OBJECT-TYPE 1180 SYNTAX Unsigned32 1181 UNITS "seconds" 1182 MAX-ACCESS read-only 1183 STATUS current 1184 DESCRIPTION 1185 "Count of Severely Errored Seconds since the unit was last 1186 reset." 1187 ::= { vdslPerfDataEntry 8 } 1189 vdslPerfDataUASs OBJECT-TYPE 1190 SYNTAX Unsigned32 1191 UNITS "seconds" 1192 MAX-ACCESS read-only 1193 STATUS current 1194 DESCRIPTION 1195 "Count of Unavailable Seconds since the unit was last 1196 reset." 1197 ::= { vdslPerfDataEntry 9 } 1199 vdslPerfDataInits OBJECT-TYPE 1200 SYNTAX Unsigned32 1201 UNITS "occurences" 1202 MAX-ACCESS read-only 1203 STATUS current 1204 DESCRIPTION 1205 "Count of the line initialization attempts since the unit 1206 was last reset. This count includes both successful and 1207 failed attempts." 1208 REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" 1209 ::= { vdslPerfDataEntry 10 } 1211 vdslPerfDataCurr15MinTimeElapsed OBJECT-TYPE 1212 SYNTAX HCPerfTimeElapsed 1213 UNITS "seconds" 1214 MAX-ACCESS read-only 1215 STATUS current 1216 DESCRIPTION 1217 "Total elapsed seconds in this interval." 1218 ::= { vdslPerfDataEntry 11 } 1220 vdslPerfDataCurr15MinLofs OBJECT-TYPE 1221 SYNTAX HCPerfCurrentCount 1222 UNITS "seconds" 1223 MAX-ACCESS read-only 1224 STATUS current 1225 DESCRIPTION 1226 "Count of seconds during this interval that there 1227 was Loss of Framing." 1228 REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" 1229 ::= { vdslPerfDataEntry 12 } 1231 vdslPerfDataCurr15MinLoss OBJECT-TYPE 1232 SYNTAX HCPerfCurrentCount 1233 UNITS "seconds" 1234 MAX-ACCESS read-only 1235 STATUS current 1236 DESCRIPTION 1237 "Count of seconds during this interval that there 1238 was Loss of Signal." 1239 REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" 1240 ::= { vdslPerfDataEntry 13 } 1242 vdslPerfDataCurr15MinLprs OBJECT-TYPE 1243 SYNTAX HCPerfCurrentCount 1244 UNITS "seconds" 1245 MAX-ACCESS read-only 1246 STATUS current 1247 DESCRIPTION 1248 "Count of seconds during this interval that there 1249 was Loss of Power." 1250 REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" 1251 ::= { vdslPerfDataEntry 14 } 1253 vdslPerfDataCurr15MinLols OBJECT-TYPE 1254 SYNTAX HCPerfCurrentCount 1255 UNITS "seconds" 1256 MAX-ACCESS read-only 1257 STATUS current 1258 DESCRIPTION 1259 "Count of seconds during this interval that there 1260 was Loss of Link." 1261 ::= { vdslPerfDataEntry 15 } 1263 vdslPerfDataCurr15MinESs OBJECT-TYPE 1264 SYNTAX HCPerfCurrentCount 1265 UNITS "seconds" 1266 MAX-ACCESS read-only 1267 STATUS current 1268 DESCRIPTION 1269 "Count of Errored Seconds during this interval. An Errored 1270 Second is a one-second interval containing one or more CRC 1271 anomalies, or one or more LOS or LOF defects." 1272 REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" 1273 ::= { vdslPerfDataEntry 16 } 1275 vdslPerfDataCurr15MinSESs OBJECT-TYPE 1276 SYNTAX HCPerfCurrentCount 1277 UNITS "seconds" 1278 MAX-ACCESS read-only 1279 STATUS current 1280 DESCRIPTION 1281 "Count of Severely Errored Seconds during this interval." 1282 ::= { vdslPerfDataEntry 17 } 1284 vdslPerfDataCurr15MinUASs OBJECT-TYPE 1285 SYNTAX HCPerfCurrentCount 1286 UNITS "seconds" 1287 MAX-ACCESS read-only 1288 STATUS current 1289 DESCRIPTION 1290 "Count of Unavailable Seconds during this interval." 1291 ::= { vdslPerfDataEntry 18 } 1293 vdslPerfDataCurr15MinInits OBJECT-TYPE 1294 SYNTAX HCPerfCurrentCount 1295 UNITS "occurences" 1296 MAX-ACCESS read-only 1297 STATUS current 1298 DESCRIPTION 1299 "Count of the line initialization attempts during this 1300 interval. This count includes both successful and 1301 failed attempts." 1302 REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" 1303 ::= { vdslPerfDataEntry 19 } 1305 vdslPerfData1DayValidIntervals OBJECT-TYPE 1306 SYNTAX HCPerfValidIntervals 1307 UNITS "intervals" 1308 MAX-ACCESS read-only 1309 STATUS current 1310 DESCRIPTION 1311 "Valid Intervals per definition found in 1312 HC-PerfHist-TC-MIB." 1314 ::= { vdslPerfDataEntry 20 } 1316 vdslPerfData1DayInvalidIntervals OBJECT-TYPE 1317 SYNTAX HCPerfInvalidIntervals 1318 UNITS "intervals" 1319 MAX-ACCESS read-only 1320 STATUS current 1321 DESCRIPTION 1322 "Invalid Intervals per definition found in 1323 HC-PerfHist-TC-MIB." 1324 ::= { vdslPerfDataEntry 21 } 1326 vdslPerfDataCurr1DayTimeElapsed OBJECT-TYPE 1327 SYNTAX HCPerfTimeElapsed 1328 UNITS "seconds" 1329 MAX-ACCESS read-only 1330 STATUS current 1331 DESCRIPTION 1332 "Number of seconds that have elapsed since the beginning 1333 of the current 1-day interval." 1334 ::= { vdslPerfDataEntry 22 } 1336 vdslPerfDataCurr1DayLofs OBJECT-TYPE 1337 SYNTAX Unsigned32 1338 UNITS "seconds" 1339 MAX-ACCESS read-only 1340 STATUS current 1341 DESCRIPTION 1342 "Count of Loss of Framing (LOF) Seconds since the 1343 beginning of the current 1-day interval." 1344 ::= { vdslPerfDataEntry 23 } 1346 vdslPerfDataCurr1DayLoss OBJECT-TYPE 1347 SYNTAX Unsigned32 1348 UNITS "seconds" 1349 MAX-ACCESS read-only 1350 STATUS current 1351 DESCRIPTION 1352 "Count of Loss of Signal (LOS) Seconds since the beginning 1353 of the current 1-day interval." 1354 ::= { vdslPerfDataEntry 24 } 1356 vdslPerfDataCurr1DayLprs OBJECT-TYPE 1357 SYNTAX Unsigned32 1358 UNITS "seconds" 1359 MAX-ACCESS read-only 1360 STATUS current 1361 DESCRIPTION 1362 "Count of Loss of Power (LPR) Seconds since the beginning 1363 of the current 1-day interval." 1364 ::= { vdslPerfDataEntry 25 } 1366 vdslPerfDataCurr1DayLols OBJECT-TYPE 1367 SYNTAX Unsigned32 1368 UNITS "seconds" 1369 MAX-ACCESS read-only 1370 STATUS current 1371 DESCRIPTION 1372 "Count of Loss of Link (LOL) Seconds since the beginning 1373 of the current 1-day interval." 1374 ::= { vdslPerfDataEntry 26 } 1376 vdslPerfDataCurr1DayESs OBJECT-TYPE 1377 SYNTAX Unsigned32 1378 UNITS "seconds" 1379 MAX-ACCESS read-only 1380 STATUS current 1381 DESCRIPTION 1382 "Count of Errored Seconds (ES) since the beginning 1383 of the current 1-day interval." 1384 ::= { vdslPerfDataEntry 27 } 1386 vdslPerfDataCurr1DaySESs OBJECT-TYPE 1387 SYNTAX Unsigned32 1388 UNITS "seconds" 1389 MAX-ACCESS read-only 1390 STATUS current 1391 DESCRIPTION 1392 "Count of Severely Errored Seconds (SES) since the 1393 beginning of the current 1-day interval." 1394 ::= { vdslPerfDataEntry 28 } 1396 vdslPerfDataCurr1DayUASs OBJECT-TYPE 1397 SYNTAX Unsigned32 1398 UNITS "seconds" 1399 MAX-ACCESS read-only 1400 STATUS current 1401 DESCRIPTION 1402 "Count of Unavailable Seconds (UAS) since the beginning 1403 of the current 1-day interval." 1404 ::= { vdslPerfDataEntry 29 } 1406 vdslPerfDataCurr1DayInits OBJECT-TYPE 1407 SYNTAX Unsigned32 1408 UNITS "seconds" 1409 MAX-ACCESS read-only 1410 STATUS current 1411 DESCRIPTION 1412 "Count of the line initialization attempts since the 1413 beginning of the current 1-day interval. This count 1414 includes both successful and failed attempts." 1415 ::= { vdslPerfDataEntry 30 } 1417 vdslPerfIntervalTable OBJECT-TYPE 1418 SYNTAX SEQUENCE OF VdslPerfIntervalEntry 1419 MAX-ACCESS not-accessible 1420 STATUS current 1421 DESCRIPTION 1422 "This table provides one row for each Vtu performance 1423 data collection interval. VDSL physical interfaces are 1424 those ifEntries where ifType is equal to vdsl(97)." 1425 ::= { vdslMibObjects 5 } 1427 vdslPerfIntervalEntry OBJECT-TYPE 1428 SYNTAX VdslPerfIntervalEntry 1429 MAX-ACCESS not-accessible 1430 STATUS current 1431 DESCRIPTION 1432 "An entry in the vdslPerfIntervalTable." 1433 INDEX { ifIndex, 1434 vdslPhysSide, 1435 vdslPerfIntervalNumber } 1436 ::= { vdslPerfIntervalTable 1 } 1438 VdslPerfIntervalEntry ::= 1439 SEQUENCE 1440 { 1441 vdslPerfIntervalNumber Unsigned32, 1442 vdslPerfIntervalLofs HCPerfIntervalCount, 1443 vdslPerfIntervalLoss HCPerfIntervalCount, 1444 vdslPerfIntervalLprs HCPerfIntervalCount, 1445 vdslPerfIntervalLols HCPerfIntervalCount, 1446 vdslPerfIntervalESs HCPerfIntervalCount, 1447 vdslPerfIntervalSESs HCPerfIntervalCount, 1448 vdslPerfIntervalUASs HCPerfIntervalCount, 1449 vdslPerfIntervalInits HCPerfIntervalCount 1450 } 1452 vdslPerfIntervalNumber OBJECT-TYPE 1453 SYNTAX Unsigned32 (1..96) 1454 MAX-ACCESS not-accessible 1455 STATUS current 1456 DESCRIPTION 1457 "Performance Data Interval number 1 is the most recent 1458 previous interval; interval 96 is 24 hours ago. 1459 Intervals 2 to 96 are optional." 1460 ::= { vdslPerfIntervalEntry 1 } 1462 vdslPerfIntervalLofs OBJECT-TYPE 1463 SYNTAX HCPerfIntervalCount 1464 UNITS "seconds" 1465 MAX-ACCESS read-only 1466 STATUS current 1467 DESCRIPTION 1468 "Count of seconds in the interval when there was Loss 1469 of Framing." 1470 REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" 1471 ::= { vdslPerfIntervalEntry 2 } 1473 vdslPerfIntervalLoss OBJECT-TYPE 1474 SYNTAX HCPerfIntervalCount 1475 UNITS "seconds" 1476 MAX-ACCESS read-only 1477 STATUS current 1478 DESCRIPTION 1479 "Count of seconds in the interval when there was Loss 1480 of Signal." 1481 REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" 1482 ::= { vdslPerfIntervalEntry 3 } 1484 vdslPerfIntervalLprs OBJECT-TYPE 1485 SYNTAX HCPerfIntervalCount 1486 UNITS "seconds" 1487 MAX-ACCESS read-only 1488 STATUS current 1489 DESCRIPTION 1490 "Count of seconds in the interval when there was Loss 1491 of Power." 1492 REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" 1493 ::= { vdslPerfIntervalEntry 4 } 1495 vdslPerfIntervalLols OBJECT-TYPE 1496 SYNTAX HCPerfIntervalCount 1497 UNITS "seconds" 1498 MAX-ACCESS read-only 1499 STATUS current 1500 DESCRIPTION 1501 "Count of seconds in the interval when there was Loss 1502 of Link." 1503 ::= { vdslPerfIntervalEntry 5 } 1505 vdslPerfIntervalESs OBJECT-TYPE 1506 SYNTAX HCPerfIntervalCount 1507 UNITS "seconds" 1508 MAX-ACCESS read-only 1509 STATUS current 1510 DESCRIPTION 1511 "Count of Errored Seconds (ES) in the interval. An Errored 1512 Second is a one-second interval containing one or more CRC 1513 anomalies, one or more LOS or LOF defects." 1514 REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" 1515 ::= { vdslPerfIntervalEntry 6 } 1517 vdslPerfIntervalSESs OBJECT-TYPE 1518 SYNTAX HCPerfIntervalCount 1519 UNITS "seconds" 1520 MAX-ACCESS read-only 1521 STATUS current 1522 DESCRIPTION 1523 "Count of Severely Errored Seconds in the interval." 1524 ::= { vdslPerfIntervalEntry 7 } 1526 vdslPerfIntervalUASs OBJECT-TYPE 1527 SYNTAX HCPerfIntervalCount 1528 UNITS "seconds" 1529 MAX-ACCESS read-only 1530 STATUS current 1531 DESCRIPTION 1532 "Count of Unavailable Seconds in the interval." 1533 ::= { vdslPerfIntervalEntry 8 } 1535 vdslPerfIntervalInits OBJECT-TYPE 1536 SYNTAX HCPerfIntervalCount 1537 MAX-ACCESS read-only 1538 STATUS current 1539 DESCRIPTION 1540 "Count of the line initialization attempts during this 1541 interval. This count includes both successful and 1542 failed attempts." 1543 REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" 1544 ::= { vdslPerfIntervalEntry 9 } 1546 vdslPerf1DayIntervalTable OBJECT-TYPE 1547 SYNTAX SEQUENCE OF VdslPerf1DayIntervalEntry 1548 MAX-ACCESS not-accessible 1549 STATUS current 1550 DESCRIPTION 1551 "This table provides one row for each VDSL performance 1552 data collection interval. This table contains live data 1553 from equipment. As such, it is NOT persistent." 1554 ::= { vdslMibObjects 6 } 1556 vdslPerf1DayIntervalEntry OBJECT-TYPE 1557 SYNTAX VdslPerf1DayIntervalEntry 1558 MAX-ACCESS not-accessible 1559 STATUS current 1560 DESCRIPTION 1561 "An entry in the vdslPerf1DayIntervalTable." 1562 INDEX { ifIndex, 1563 vdslPhysSide, 1564 vdslPerf1DayIntervalNumber } 1565 ::= { vdslPerf1DayIntervalTable 1 } 1567 VdslPerf1DayIntervalEntry ::= 1568 SEQUENCE 1569 { 1570 vdslPerf1DayIntervalNumber Unsigned32, 1571 vdslPerf1DayIntervalMoniSecs HCPerfTimeElapsed, 1572 vdslPerf1DayIntervalLofs Unsigned32, 1573 vdslPerf1DayIntervalLoss Unsigned32, 1574 vdslPerf1DayIntervalLprs Unsigned32, 1575 vdslPerf1DayIntervalLols Unsigned32, 1576 vdslPerf1DayIntervalESs Unsigned32, 1577 vdslPerf1DayIntervalSESs Unsigned32, 1578 vdslPerf1DayIntervalUASs Unsigned32, 1579 vdslPerf1DayIntervalInits Unsigned32 1580 } 1582 vdslPerf1DayIntervalNumber OBJECT-TYPE 1583 SYNTAX Unsigned32 (1..30) 1584 MAX-ACCESS not-accessible 1585 STATUS current 1586 DESCRIPTION 1587 "History Data Interval number. Interval 1 is the most 1588 recent previous day; interval 30 is 30 days ago. Intervals 1589 2 to 30 are optional." 1590 ::= { vdslPerf1DayIntervalEntry 1 } 1592 vdslPerf1DayIntervalMoniSecs OBJECT-TYPE 1593 SYNTAX HCPerfTimeElapsed 1594 UNITS "seconds" 1595 MAX-ACCESS read-only 1596 STATUS current 1597 DESCRIPTION 1598 "The amount of time in the 1-day interval over which the 1599 performance monitoring information is actually counted. 1600 This value will be the same as the interval duration except 1601 in a situation where performance monitoring data could not 1602 be collected for any reason." 1603 ::= { vdslPerf1DayIntervalEntry 2 } 1605 vdslPerf1DayIntervalLofs OBJECT-TYPE 1606 SYNTAX Unsigned32 1607 UNITS "seconds" 1608 MAX-ACCESS read-only 1609 STATUS current 1610 DESCRIPTION 1611 "Count of Loss of Frame (LOF) Seconds during the 1-day 1612 interval as measured by vdslPerf1DayIntervalMoniSecs." 1613 REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" 1614 ::= { vdslPerf1DayIntervalEntry 3 } 1616 vdslPerf1DayIntervalLoss OBJECT-TYPE 1617 SYNTAX Unsigned32 1618 UNITS "seconds" 1619 MAX-ACCESS read-only 1620 STATUS current 1621 DESCRIPTION 1622 "Count of Loss of Signal (LOS) Seconds during the 1-day 1623 interval as measured by vdslPerf1DayIntervalMoniSecs." 1624 REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" 1625 ::= { vdslPerf1DayIntervalEntry 4 } 1627 vdslPerf1DayIntervalLprs OBJECT-TYPE 1628 SYNTAX Unsigned32 1629 UNITS "seconds" 1630 MAX-ACCESS read-only 1631 STATUS current 1632 DESCRIPTION 1633 "Count of Loss of Power (LPR) Seconds during the 1-day 1634 interval as measured by vdslPerf1DayIntervalMoniSecs." 1635 REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" 1636 ::= { vdslPerf1DayIntervalEntry 5 } 1638 vdslPerf1DayIntervalLols OBJECT-TYPE 1639 SYNTAX Unsigned32 1640 UNITS "seconds" 1641 MAX-ACCESS read-only 1642 STATUS current 1643 DESCRIPTION 1644 "Count of Loss of Link (LOL) Seconds during the 1-day 1645 interval as measured by vdslPerf1DayIntervalMoniSecs." 1646 ::= { vdslPerf1DayIntervalEntry 6 } 1648 vdslPerf1DayIntervalESs OBJECT-TYPE 1649 SYNTAX Unsigned32 1650 UNITS "seconds" 1651 MAX-ACCESS read-only 1652 STATUS current 1653 DESCRIPTION 1654 "Count of Errored Seconds (ES) during the 1-day 1655 interval as measured by vdslPerf1DayIntervalMoniSecs." 1656 REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" 1657 ::= { vdslPerf1DayIntervalEntry 7 } 1659 vdslPerf1DayIntervalSESs OBJECT-TYPE 1660 SYNTAX Unsigned32 1661 UNITS "seconds" 1662 MAX-ACCESS read-only 1663 STATUS current 1664 DESCRIPTION 1665 "Count of Severely Errored Seconds (SES) during the 1-day 1666 interval as measured by vdslPerf1DayIntervalMoniSecs." 1667 ::= { vdslPerf1DayIntervalEntry 8 } 1669 vdslPerf1DayIntervalUASs OBJECT-TYPE 1670 SYNTAX Unsigned32 1671 UNITS "seconds" 1672 MAX-ACCESS read-only 1673 STATUS current 1674 DESCRIPTION 1675 "Count of Unavailable Seconds (UAS) during the 1-day 1676 interval as measured by vdslPerf1DayIntervalMoniSecs." 1677 ::= { vdslPerf1DayIntervalEntry 9 } 1679 vdslPerf1DayIntervalInits OBJECT-TYPE 1680 SYNTAX Unsigned32 1681 UNITS "seconds" 1682 MAX-ACCESS read-only 1683 STATUS current 1684 DESCRIPTION 1685 "Count of the line initialization attempts during the 1686 1-day interval as measured by vdslPerf1DayIntervalMoniSecs. 1687 This count includes both successful and failed attempts." 1688 REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" 1689 ::= { vdslPerf1DayIntervalEntry 10 } 1691 vdslChanPerfDataTable OBJECT-TYPE 1692 SYNTAX SEQUENCE OF VdslChanPerfDataEntry 1693 MAX-ACCESS not-accessible 1694 STATUS current 1695 DESCRIPTION 1696 "This table provides one row for each Vtu channel. 1697 VDSL channel interfaces are those ifEntries where 1698 ifType is equal to interleave(124) or fast(125)." 1699 ::= { vdslMibObjects 7 } 1701 vdslChanPerfDataEntry OBJECT-TYPE 1702 SYNTAX VdslChanPerfDataEntry 1703 MAX-ACCESS not-accessible 1704 STATUS current 1705 DESCRIPTION 1706 "An entry in the vdslChanPerfDataTable." 1707 INDEX { ifIndex, 1708 vdslPhysSide } 1709 ::= { vdslChanPerfDataTable 1 } 1711 VdslChanPerfDataEntry ::= 1712 SEQUENCE 1713 { 1714 vdslChanValidIntervals HCPerfValidIntervals, 1715 vdslChanInvalidIntervals HCPerfInvalidIntervals, 1716 vdslChanFixedOctets ZeroBasedCounter64, 1717 vdslChanBadBlks ZeroBasedCounter64, 1718 vdslChanCurr15MinTimeElapsed HCPerfTimeElapsed, 1719 vdslChanCurr15MinFixedOctets HCPerfCurrentCount, 1720 vdslChanCurr15MinBadBlks HCPerfCurrentCount, 1721 vdslChan1DayValidIntervals HCPerfValidIntervals, 1722 vdslChan1DayInvalidIntervals HCPerfInvalidIntervals, 1723 vdslChanCurr1DayTimeElapsed HCPerfTimeElapsed, 1724 vdslChanCurr1DayFixedOctets HCPerfCurrentCount, 1725 vdslChanCurr1DayBadBlks HCPerfCurrentCount 1726 } 1728 vdslChanValidIntervals OBJECT-TYPE 1729 SYNTAX HCPerfValidIntervals 1730 UNITS "intervals" 1731 MAX-ACCESS read-only 1732 STATUS current 1733 DESCRIPTION 1734 "Valid Intervals per definition found in 1735 HC-PerfHist-TC-MIB." 1736 ::= { vdslChanPerfDataEntry 1 } 1738 vdslChanInvalidIntervals OBJECT-TYPE 1739 SYNTAX HCPerfInvalidIntervals 1740 UNITS "intervals" 1741 MAX-ACCESS read-only 1742 STATUS current 1743 DESCRIPTION 1744 "Invalid Intervals per definition found in 1745 HC-PerfHist-TC-MIB." 1746 ::= { vdslChanPerfDataEntry 2 } 1748 vdslChanFixedOctets OBJECT-TYPE 1749 SYNTAX ZeroBasedCounter64 1750 UNITS "octets" 1751 MAX-ACCESS read-only 1752 STATUS current 1753 DESCRIPTION 1754 "Count of corrected octets since the unit was last reset." 1755 REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" 1756 ::= { vdslChanPerfDataEntry 3 } 1758 vdslChanBadBlks OBJECT-TYPE 1759 SYNTAX ZeroBasedCounter64 1760 UNITS "blocks" 1761 MAX-ACCESS read-only 1762 STATUS current 1763 DESCRIPTION 1764 "Count of uncorrectable blocks since the unit was last 1765 reset." 1766 REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" 1767 ::= { vdslChanPerfDataEntry 4 } 1769 vdslChanCurr15MinTimeElapsed OBJECT-TYPE 1770 SYNTAX HCPerfTimeElapsed 1771 UNITS "seconds" 1772 MAX-ACCESS read-only 1773 STATUS current 1774 DESCRIPTION 1775 "Total elapsed seconds in this interval." 1776 ::= { vdslChanPerfDataEntry 5 } 1778 vdslChanCurr15MinFixedOctets OBJECT-TYPE 1779 SYNTAX HCPerfCurrentCount 1780 UNITS "octets" 1781 MAX-ACCESS read-only 1782 STATUS current 1783 DESCRIPTION 1784 "Count of corrected octets in this interval." 1785 REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" 1786 ::= { vdslChanPerfDataEntry 6 } 1788 vdslChanCurr15MinBadBlks OBJECT-TYPE 1789 SYNTAX HCPerfCurrentCount 1790 UNITS "blocks" 1791 MAX-ACCESS read-only 1792 STATUS current 1793 DESCRIPTION 1794 "Count of uncorrectable blocks in this interval." 1795 REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" 1796 ::= { vdslChanPerfDataEntry 7 } 1798 vdslChan1DayValidIntervals OBJECT-TYPE 1799 SYNTAX HCPerfValidIntervals 1800 MAX-ACCESS read-only 1801 STATUS current 1802 DESCRIPTION 1803 "Valid Intervals per definition found in 1804 HC-PerfHist-TC-MIB." 1805 ::= { vdslChanPerfDataEntry 8 } 1807 vdslChan1DayInvalidIntervals OBJECT-TYPE 1808 SYNTAX HCPerfInvalidIntervals 1809 MAX-ACCESS read-only 1810 STATUS current 1811 DESCRIPTION 1812 "Invalid Intervals per definition found in 1813 HC-PerfHist-TC-MIB." 1814 ::= { vdslChanPerfDataEntry 9 } 1816 vdslChanCurr1DayTimeElapsed OBJECT-TYPE 1817 SYNTAX HCPerfTimeElapsed 1818 UNITS "seconds" 1819 MAX-ACCESS read-only 1820 STATUS current 1821 DESCRIPTION 1822 "Number of seconds that have elapsed since the beginning 1823 of the current 1-day interval." 1824 ::= { vdslChanPerfDataEntry 10 } 1826 vdslChanCurr1DayFixedOctets OBJECT-TYPE 1827 SYNTAX HCPerfCurrentCount 1828 UNITS "octets" 1829 MAX-ACCESS read-only 1830 STATUS current 1831 DESCRIPTION 1832 "Count of corrected octets since the beginning of the 1833 current 1-day interval." 1834 REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" 1835 ::= { vdslChanPerfDataEntry 11 } 1837 vdslChanCurr1DayBadBlks OBJECT-TYPE 1838 SYNTAX HCPerfCurrentCount 1839 UNITS "blocks" 1840 MAX-ACCESS read-only 1841 STATUS current 1842 DESCRIPTION 1843 "Count of uncorrectable blocks since the beginning of the 1844 current 1-day interval." 1845 REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" 1846 ::= { vdslChanPerfDataEntry 12 } 1848 vdslChanIntervalTable OBJECT-TYPE 1849 SYNTAX SEQUENCE OF VdslChanIntervalEntry 1850 MAX-ACCESS not-accessible 1851 STATUS current 1852 DESCRIPTION 1853 "This table provides one row for each Vtu channel data 1854 collection interval. VDSL channel interfaces are those 1855 ifEntries where ifType is equal to interleave(124) or 1856 fast(125)." 1857 ::= { vdslMibObjects 8 } 1859 vdslChanIntervalEntry OBJECT-TYPE 1860 SYNTAX VdslChanIntervalEntry 1861 MAX-ACCESS not-accessible 1862 STATUS current 1863 DESCRIPTION 1864 "An entry in the vdslChanIntervalTable." 1865 INDEX { ifIndex, 1866 vdslPhysSide, 1867 vdslChanIntervalNumber } 1868 ::= { vdslChanIntervalTable 1 } 1870 VdslChanIntervalEntry ::= 1871 SEQUENCE 1872 { 1873 vdslChanIntervalNumber Unsigned32, 1874 vdslChanIntervalFixedOctets HCPerfIntervalCount, 1875 vdslChanIntervalBadBlks HCPerfIntervalCount 1876 } 1878 vdslChanIntervalNumber OBJECT-TYPE 1879 SYNTAX Unsigned32 (1..96) 1880 MAX-ACCESS not-accessible 1881 STATUS current 1882 DESCRIPTION 1883 "Performance Data Interval number 1 is the most recent 1884 previous interval; interval 96 is 24 hours ago. 1885 Intervals 2 to 96 are optional." 1886 ::= { vdslChanIntervalEntry 1 } 1888 vdslChanIntervalFixedOctets OBJECT-TYPE 1889 SYNTAX HCPerfIntervalCount 1890 UNITS "octets" 1891 MAX-ACCESS read-only 1892 STATUS current 1893 DESCRIPTION 1894 "Count of corrected octets in this interval." 1895 REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" 1896 ::= { vdslChanIntervalEntry 2 } 1898 vdslChanIntervalBadBlks OBJECT-TYPE 1899 SYNTAX HCPerfIntervalCount 1900 UNITS "blocks" 1901 MAX-ACCESS read-only 1902 STATUS current 1903 DESCRIPTION 1904 "Count of uncorrectable blocks in this interval." 1905 REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" 1906 ::= { vdslChanIntervalEntry 3 } 1908 vdslChan1DayIntervalTable OBJECT-TYPE 1909 SYNTAX SEQUENCE OF VdslChan1DayIntervalEntry 1910 MAX-ACCESS not-accessible 1911 STATUS current 1912 DESCRIPTION 1913 "This table provides one row for each VDSL performance 1914 data collection interval. This table contains live data 1915 from equipment. As such, it is NOT persistent." 1916 ::= { vdslMibObjects 9 } 1918 vdslChan1DayIntervalEntry OBJECT-TYPE 1919 SYNTAX VdslChan1DayIntervalEntry 1920 MAX-ACCESS not-accessible 1921 STATUS current 1922 DESCRIPTION 1923 "An entry in the vdslChan1DayIntervalTable." 1924 INDEX { ifIndex, 1925 vdslPhysSide, 1926 vdslChan1DayIntervalNumber } 1927 ::= { vdslChan1DayIntervalTable 1 } 1929 VdslChan1DayIntervalEntry ::= 1930 SEQUENCE 1931 { 1932 vdslChan1DayIntervalNumber Unsigned32, 1933 vdslChan1DayIntervalMoniSecs HCPerfTimeElapsed, 1934 vdslChan1DayIntervalFixedOctets HCPerfCurrentCount, 1935 vdslChan1DayIntervalBadBlks HCPerfCurrentCount 1936 } 1938 vdslChan1DayIntervalNumber OBJECT-TYPE 1939 SYNTAX Unsigned32 (1..30) 1940 MAX-ACCESS not-accessible 1941 STATUS current 1942 DESCRIPTION 1943 "History Data Interval number. Interval 1 is the most 1944 recent previous day; interval 30 is 30 days ago. Intervals 1945 2 to 30 are optional." 1946 ::= { vdslChan1DayIntervalEntry 1 } 1948 vdslChan1DayIntervalMoniSecs OBJECT-TYPE 1949 SYNTAX HCPerfTimeElapsed 1950 UNITS "seconds" 1951 MAX-ACCESS read-only 1952 STATUS current 1953 DESCRIPTION 1954 "The amount of time in the 1-day interval over which the 1955 performance monitoring information is actually counted. 1956 This value will be the same as the interval duration except 1957 in a situation where performance monitoring data could not 1958 be collected for any reason." 1959 ::= { vdslChan1DayIntervalEntry 2 } 1961 vdslChan1DayIntervalFixedOctets OBJECT-TYPE 1962 SYNTAX HCPerfCurrentCount 1963 UNITS "octets" 1964 MAX-ACCESS read-only 1965 STATUS current 1966 DESCRIPTION 1967 "Count of corrected octets in this interval." 1968 REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" 1969 ::= { vdslChan1DayIntervalEntry 3 } 1971 vdslChan1DayIntervalBadBlks OBJECT-TYPE 1972 SYNTAX HCPerfCurrentCount 1973 UNITS "blocks" 1974 MAX-ACCESS read-only 1975 STATUS current 1976 DESCRIPTION 1977 "Count of uncorrectable blocks in this interval." 1978 REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" 1979 ::= { vdslChan1DayIntervalEntry 4 } 1981 -- 1982 -- profile tables 1983 -- 1985 vdslLineConfProfileTable OBJECT-TYPE 1986 SYNTAX SEQUENCE OF VdslLineConfProfileEntry 1987 MAX-ACCESS not-accessible 1988 STATUS current 1989 DESCRIPTION 1990 "This table contains information on the VDSL line 1991 configuration. One entry in this table reflects a 1992 profile defined by a manager which can be used to 1993 configure the VDSL line. 1995 Entries in this table MUST be maintained in a 1996 persistent manner." 1997 ::= { vdslMibObjects 11 } 1999 vdslLineConfProfileEntry OBJECT-TYPE 2000 SYNTAX VdslLineConfProfileEntry 2001 MAX-ACCESS not-accessible 2002 STATUS current 2003 DESCRIPTION 2004 "Each entry consists of a list of parameters that 2005 represents the configuration of a VDSL line. 2007 A default profile with an index of 'DEFVAL', will 2008 always exist and its parameters will be set to vendor 2009 specific values, unless otherwise specified in this 2010 document." 2011 INDEX { vdslLineConfProfileName } 2012 ::= { vdslLineConfProfileTable 1 } 2014 VdslLineConfProfileEntry ::= 2015 SEQUENCE 2016 { 2017 vdslLineConfProfileName SnmpAdminString, 2018 vdslLineConfDownRateMode INTEGER, 2019 vdslLineConfUpRateMode INTEGER, 2020 vdslLineConfDownMaxPwr Unsigned32, 2021 vdslLineConfUpMaxPwr Unsigned32, 2022 vdslLineConfDownMaxSnrMgn Unsigned32, 2023 vdslLineConfDownMinSnrMgn Unsigned32, 2024 vdslLineConfDownTargetSnrMgn Unsigned32, 2025 vdslLineConfUpMaxSnrMgn Unsigned32, 2026 vdslLineConfUpMinSnrMgn Unsigned32, 2027 vdslLineConfUpTargetSnrMgn Unsigned32, 2028 vdslLineConfDownFastMaxDataRate Unsigned32, 2029 vdslLineConfDownFastMinDataRate Unsigned32, 2030 vdslLineConfDownSlowMaxDataRate Unsigned32, 2031 vdslLineConfDownSlowMinDataRate Unsigned32, 2032 vdslLineConfUpFastMaxDataRate Unsigned32, 2033 vdslLineConfUpFastMinDataRate Unsigned32, 2034 vdslLineConfUpSlowMaxDataRate Unsigned32, 2035 vdslLineConfUpSlowMinDataRate Unsigned32, 2036 vdslLineConfDownRateRatio Unsigned32, 2037 vdslLineConfUpRateRatio Unsigned32, 2038 vdslLineConfDownMaxInterDelay Unsigned32, 2039 vdslLineConfUpMaxInterDelay Unsigned32, 2040 vdslLineConfDownPboControl INTEGER, 2041 vdslLineConfUpPboControl INTEGER, 2042 vdslLineConfDownPboLevel Unsigned32, 2043 vdslLineConfUpPboLevel Unsigned32, 2044 vdslLineConfDeploymentScenario INTEGER, 2045 vdslLineConfAdslPresence INTEGER, 2046 vdslLineConfApplicableStandard INTEGER, 2047 vdslLineConfBandPlan INTEGER, 2048 vdslLineConfBandPlanFx Unsigned32, 2049 vdslLineConfBandOptUsage INTEGER, 2050 vdslLineConfUpPsdTemplate INTEGER, 2051 vdslLineConfDownPsdTemplate INTEGER, 2052 vdslLineConfHamBandMask BITS, 2053 vdslLineConfCustomNotch1Start Unsigned32, 2054 vdslLineConfCustomNotch1Stop Unsigned32, 2055 vdslLineConfCustomNotch2Start Unsigned32, 2056 vdslLineConfCustomNotch2Stop Unsigned32, 2057 vdslLineConfDownTargetSlowBurst Unsigned32, 2058 vdslLineConfUpTargetSlowBurst Unsigned32, 2059 vdslLineConfDownMaxFastFec Unsigned32, 2060 vdslLineConfUpMaxFastFec Unsigned32, 2061 vdslLineConfLineType INTEGER, 2062 vdslLineConfProfRowStatus RowStatus 2063 } 2065 vdslLineConfProfileName OBJECT-TYPE 2066 SYNTAX SnmpAdminString (SIZE (1..32)) 2067 MAX-ACCESS not-accessible 2068 STATUS current 2069 DESCRIPTION 2070 "This object identifies a row in this table. 2072 A default profile with an index of 'DEFVAL', will 2073 always exist and its parameters will be set to vendor 2074 specific values, unless otherwise specified in this 2075 document." 2076 ::= { vdslLineConfProfileEntry 1 } 2078 vdslLineConfDownRateMode OBJECT-TYPE 2079 SYNTAX INTEGER 2080 { 2081 manual(1), 2082 adaptAtInit(2) 2083 } 2084 MAX-ACCESS read-create 2085 STATUS current 2086 DESCRIPTION 2087 "Specifies the rate selection behavior for the line 2088 in the downstream direction. 2090 manual(1) forces the rate to the configured rate 2091 adaptAtInit(2) adapts the line based upon line quality." 2092 DEFVAL { adaptAtInit } 2093 ::= { vdslLineConfProfileEntry 2 } 2095 vdslLineConfUpRateMode OBJECT-TYPE 2096 SYNTAX INTEGER 2097 { 2098 manual(1), 2099 adaptAtInit(2) 2100 } 2101 MAX-ACCESS read-create 2102 STATUS current 2103 DESCRIPTION 2104 "Specifies the rate selection behavior for the line 2105 in the upstream direction. 2107 manual(1) forces the rate to the configured rate 2108 adaptAtInit(2) adapts the line based upon line quality." 2110 DEFVAL { adaptAtInit } 2111 ::= { vdslLineConfProfileEntry 3 } 2113 vdslLineConfDownMaxPwr OBJECT-TYPE 2114 SYNTAX Unsigned32 (0..58) 2115 UNITS "0.25dBm" 2116 MAX-ACCESS read-create 2117 STATUS current 2118 DESCRIPTION 2119 "Specifies the maximum aggregate downstream power 2120 level in the range 0 to 14.5 dBm." 2121 REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" 2122 DEFVAL { 0 } 2123 ::= { vdslLineConfProfileEntry 4 } 2125 vdslLineConfUpMaxPwr OBJECT-TYPE 2126 SYNTAX Unsigned32 (0..58) 2127 UNITS "0.25dBm" 2128 MAX-ACCESS read-create 2129 STATUS current 2130 DESCRIPTION 2131 "Specifies the maximum aggregate upstream power 2132 level in the range 0 to 14.5 dBm." 2133 REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" 2134 DEFVAL { 0 } 2135 ::= { vdslLineConfProfileEntry 5 } 2137 vdslLineConfDownMaxSnrMgn OBJECT-TYPE 2138 SYNTAX Unsigned32 (0..127) 2139 UNITS "0.25dBm" 2140 MAX-ACCESS read-create 2141 STATUS current 2142 DESCRIPTION 2143 "Specifies the maximum downstream Signal/Noise Margin 2144 in units of 0.25 dB, for a range of 0 to 31.75 dB." 2145 REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" 2146 DEFVAL { 0 } 2147 ::= { vdslLineConfProfileEntry 6 } 2149 vdslLineConfDownMinSnrMgn OBJECT-TYPE 2150 SYNTAX Unsigned32 (0..127) 2151 UNITS "0.25dBm" 2152 MAX-ACCESS read-create 2153 STATUS current 2154 DESCRIPTION 2155 "Specifies the minimum downstream Signal/Noise Margin 2156 in units of 0.25 dB, for a range of 0 to 31.75 dB." 2157 REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" 2158 DEFVAL { 0 } 2159 ::= { vdslLineConfProfileEntry 7 } 2161 vdslLineConfDownTargetSnrMgn OBJECT-TYPE 2162 SYNTAX Unsigned32 (0..127) 2163 UNITS "0.25dBm" 2164 MAX-ACCESS read-create 2165 STATUS current 2166 DESCRIPTION 2167 "Specifies the target downstream Signal/Noise Margin 2168 in units of 0.25 dB, for a range of 0 to 31.75 dB. 2169 This is the Noise Margin the transceivers must achieve 2170 with a BER of 10^-7 or better to successfully complete 2171 initialization." 2172 REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" 2173 DEFVAL { 0 } 2174 ::= { vdslLineConfProfileEntry 8 } 2176 vdslLineConfUpMaxSnrMgn OBJECT-TYPE 2177 SYNTAX Unsigned32 (0..127) 2178 UNITS "0.25dBm" 2179 MAX-ACCESS read-create 2180 STATUS current 2181 DESCRIPTION 2182 "Specifies the maximum upstream Signal/Noise Margin 2183 in units of 0.25 dB, for a range of 0 to 31.75 dB." 2184 REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" 2185 DEFVAL { 0 } 2186 ::= { vdslLineConfProfileEntry 9 } 2188 vdslLineConfUpMinSnrMgn OBJECT-TYPE 2189 SYNTAX Unsigned32 (0..127) 2190 UNITS "0.25dBm" 2191 MAX-ACCESS read-create 2192 STATUS current 2193 DESCRIPTION 2194 "Specifies the minimum upstream Signal/Noise Margin 2195 in units of 0.25 dB, for a range of 0 to 31.75 dB." 2196 REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" 2197 DEFVAL { 0 } 2198 ::= { vdslLineConfProfileEntry 10 } 2200 vdslLineConfUpTargetSnrMgn OBJECT-TYPE 2201 SYNTAX Unsigned32 (0..127) 2202 UNITS "0.25dBm" 2203 MAX-ACCESS read-create 2204 STATUS current 2205 DESCRIPTION 2206 "Specifies the target upstream Signal/Noise Margin in 2207 units of 0.25 dB, for a range of 0 to 31.75 dB. This 2208 is the Noise Margin the transceivers must achieve with 2209 a BER of 10^-7 or better to successfully complete 2210 initialization." 2211 REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" 2212 DEFVAL { 0 } 2213 ::= { vdslLineConfProfileEntry 11 } 2215 vdslLineConfDownFastMaxDataRate OBJECT-TYPE 2216 SYNTAX Unsigned32 2217 UNITS "kbps" 2218 MAX-ACCESS read-create 2219 STATUS current 2220 DESCRIPTION 2221 "Specifies the maximum downstream fast channel 2222 data rate in steps of 1000 bits/second." 2223 DEFVAL { 0 } 2224 ::= { vdslLineConfProfileEntry 12 } 2226 vdslLineConfDownFastMinDataRate OBJECT-TYPE 2227 SYNTAX Unsigned32 2228 UNITS "kbps" 2229 MAX-ACCESS read-create 2230 STATUS current 2231 DESCRIPTION 2232 "Specifies the minimum downstream fast channel 2233 data rate in steps of 1000 bits/second." 2234 DEFVAL { 0 } 2235 ::= { vdslLineConfProfileEntry 13 } 2237 vdslLineConfDownSlowMaxDataRate OBJECT-TYPE 2238 SYNTAX Unsigned32 2239 UNITS "kbps" 2240 MAX-ACCESS read-create 2241 STATUS current 2242 DESCRIPTION 2243 "Specifies the maximum downstream slow channel 2244 data rate in steps of 1000 bits/second. 2246 The maximum aggregate downstream transmit speed 2247 of the line can be derived from the sum of maximum 2248 downstream fast and slow channel data rates." 2249 DEFVAL { 0 } 2250 ::= { vdslLineConfProfileEntry 14 } 2252 vdslLineConfDownSlowMinDataRate OBJECT-TYPE 2253 SYNTAX Unsigned32 2254 UNITS "kbps" 2255 MAX-ACCESS read-create 2256 STATUS current 2257 DESCRIPTION 2258 "Specifies the minimum downstream slow channel 2259 data rate in steps of 1000 bits/second. 2261 The minimum aggregate downstream transmit speed 2262 of the line can be derived from the sum of minimum 2263 downstream fast and slow channel data rates." 2264 DEFVAL { 0 } 2265 ::= { vdslLineConfProfileEntry 15 } 2267 vdslLineConfUpFastMaxDataRate OBJECT-TYPE 2268 SYNTAX Unsigned32 2269 UNITS "kbps" 2270 MAX-ACCESS read-create 2271 STATUS current 2272 DESCRIPTION 2273 "Specifies the maximum upstream fast channel 2274 data rate in steps of 1000 bits/second. 2276 The maximum aggregate upstream transmit speed 2277 of the line can be derived from the sum of maximum 2278 upstream fast and slow channel data rates." 2279 DEFVAL { 0 } 2280 ::= { vdslLineConfProfileEntry 16 } 2282 vdslLineConfUpFastMinDataRate OBJECT-TYPE 2283 SYNTAX Unsigned32 2284 UNITS "kbps" 2285 MAX-ACCESS read-create 2286 STATUS current 2287 DESCRIPTION 2288 "Specifies the minimum upstream fast channel 2289 data rate in steps of 1000 bits/second. 2291 The minimum aggregate upstream transmit speed 2292 of the line can be derived from the sum of minimum 2293 upstream fast and slow channel data rates." 2294 DEFVAL { 0 } 2295 ::= { vdslLineConfProfileEntry 17 } 2297 vdslLineConfUpSlowMaxDataRate OBJECT-TYPE 2298 SYNTAX Unsigned32 2299 UNITS "kbps" 2300 MAX-ACCESS read-create 2301 STATUS current 2302 DESCRIPTION 2303 "Specifies the maximum upstream slow channel 2304 data rate in steps of 1000 bits/second." 2305 DEFVAL { 0 } 2306 ::= { vdslLineConfProfileEntry 18 } 2308 vdslLineConfUpSlowMinDataRate OBJECT-TYPE 2309 SYNTAX Unsigned32 2310 UNITS "kbps" 2311 MAX-ACCESS read-create 2312 STATUS current 2313 DESCRIPTION 2314 "Specifies the minimum upstream slow channel 2315 data rate in steps of 1000 bits/second." 2316 DEFVAL { 0 } 2317 ::= { vdslLineConfProfileEntry 19 } 2319 vdslLineConfDownRateRatio OBJECT-TYPE 2320 SYNTAX Unsigned32 (0..100) 2321 UNITS "percent" 2322 MAX-ACCESS read-create 2323 STATUS current 2324 DESCRIPTION 2325 "For dynamic rate adaptation at startup, the allocation 2326 of data rate in excess of the minimum data rate for each 2327 channel is controlled by the object. This object specifies 2328 the ratio of the allocation of the excess data rate between 2329 the fast and the slow channels. This allocation represents 2330 downstream Fast Channel Allocation / Slow Channel 2331 Allocation." 2332 DEFVAL { 0 } 2333 ::= { vdslLineConfProfileEntry 20 } 2335 vdslLineConfUpRateRatio OBJECT-TYPE 2336 SYNTAX Unsigned32 (0..100) 2337 UNITS "percent" 2338 MAX-ACCESS read-create 2339 STATUS current 2340 DESCRIPTION 2341 "For dynamic rate adaptation at startup, the allocation 2342 of data rate in excess of the minimum data rate for each 2343 channel is controlled by the object. This object specifies 2344 the ratio of the allocation of the excess data rate between 2345 the fast and the slow channels. This allocation represents 2346 upstream Fast Channel Allocation/Slow Channel Allocation." 2347 DEFVAL { 0 } 2348 ::= { vdslLineConfProfileEntry 21 } 2350 vdslLineConfDownMaxInterDelay OBJECT-TYPE 2351 SYNTAX Unsigned32 (0..255) 2352 UNITS "milliseconds" 2353 MAX-ACCESS read-create 2354 STATUS current 2355 DESCRIPTION 2356 "Specifies the maximum interleave delay for the 2357 downstream slow channel." 2358 DEFVAL { 0 } 2359 ::= { vdslLineConfProfileEntry 22 } 2361 vdslLineConfUpMaxInterDelay OBJECT-TYPE 2362 SYNTAX Unsigned32 (0..255) 2363 UNITS "milliseconds" 2364 MAX-ACCESS read-create 2365 STATUS current 2366 DESCRIPTION 2367 "Specifies the maximum interleave delay for the 2368 upstream slow channel." 2369 DEFVAL { 0 } 2370 ::= { vdslLineConfProfileEntry 23 } 2372 vdslLineConfDownPboControl OBJECT-TYPE 2373 SYNTAX INTEGER 2374 { 2375 disabled(1), 2376 auto(2), 2377 manual(3) 2378 } 2379 MAX-ACCESS read-create 2380 STATUS current 2381 DESCRIPTION 2382 "Downstream power backoff (PBO) control for this 2383 line. For transceivers which do not support downstream 2384 PBO control, this object MUST be fixed at disabled(1). 2385 If auto(2) is selected, the transceiver will automatically 2386 adjust the power backoff. If manual(3) is selected, 2387 then the transceiver will use the value from 2388 vdslLineConfDownPboLevel." 2389 DEFVAL { disabled } 2390 ::= { vdslLineConfProfileEntry 24 } 2392 vdslLineConfUpPboControl OBJECT-TYPE 2393 SYNTAX INTEGER 2394 { 2395 disabled(1), 2396 auto(2), 2397 manual(3) 2398 } 2399 MAX-ACCESS read-create 2400 STATUS current 2401 DESCRIPTION 2402 "Upstream power backoff (PBO) control for this 2403 line. For transceivers which do not support upstream 2404 PBO control, this object MUST be fixed at disabled(1). 2405 If auto(2) is selected, the transceiver will automatically 2406 adjust the power backoff. If manual(3) is selected, 2407 then the transceiver will use the value from 2408 vdslLineConfUpPboLevel." 2409 DEFVAL { disabled } 2410 ::= { vdslLineConfProfileEntry 25 } 2412 vdslLineConfDownPboLevel OBJECT-TYPE 2413 SYNTAX Unsigned32 (0..160) 2414 UNITS "0.25dB" 2415 MAX-ACCESS read-create 2416 STATUS current 2417 DESCRIPTION 2418 "Specifies the downstream backoff level to be used 2419 when vdslLineConfDownPboControl = manual(3)." 2420 DEFVAL { 0 } 2421 ::= { vdslLineConfProfileEntry 26 } 2423 vdslLineConfUpPboLevel OBJECT-TYPE 2424 SYNTAX Unsigned32 (0..160) 2425 UNITS "0.25dB" 2426 MAX-ACCESS read-create 2427 STATUS current 2428 DESCRIPTION 2429 "Specifies the upstream backoff level to be used 2430 when vdslLineConfUpPboControl = manual(3)." 2431 DEFVAL { 0 } 2432 ::= { vdslLineConfProfileEntry 27 } 2434 vdslLineConfDeploymentScenario OBJECT-TYPE 2435 SYNTAX INTEGER 2436 { 2437 fttCab(1), 2438 fttEx(2), 2439 other(3) 2440 } 2441 MAX-ACCESS read-create 2442 STATUS current 2443 DESCRIPTION 2444 "The VDSL line deployment scenario. When using 2445 fttCab(1), the VTU-C is located in a street cabinet. 2446 When using fttEx(2), the VTU-C is located at the 2447 central office. Changes to this value will have 2448 no effect on the transceiver." 2449 REFERENCE "DSL Forum TR-057" 2450 DEFVAL { fttCab } 2451 ::= { vdslLineConfProfileEntry 28 } 2453 vdslLineConfAdslPresence OBJECT-TYPE 2454 SYNTAX INTEGER 2455 { 2456 none(1), 2457 adslOverPots(2), 2458 adslOverISDN(3) 2459 } 2460 MAX-ACCESS read-create 2461 STATUS current 2462 DESCRIPTION 2463 "Indicates presence of ADSL service in the associated 2464 cable bundle/binder. 2466 none(1) indicates no ADSL service in the bundle 2467 adslOverPots(2) indicates ADSL service over POTS is 2468 present in the bundle 2469 adslOverISDN(3) indicates ADSL service over ISDN is 2470 present in the bundle" 2471 DEFVAL { none } 2472 ::= { vdslLineConfProfileEntry 29 } 2474 vdslLineConfApplicableStandard OBJECT-TYPE 2475 SYNTAX INTEGER 2476 { 2477 ansi(1), 2478 etsi(2), 2479 itu(3), 2480 other(4) 2481 } 2482 MAX-ACCESS read-create 2483 STATUS current 2484 DESCRIPTION 2485 "The VDSL standard to be used for the line. 2487 ansi(1) indicates ANSI standard 2488 etsi(2) indicates ETSI standard 2489 itu(3) indicates ITU standard 2490 other(4) indicates a standard other than the above." 2491 DEFVAL { ansi } 2492 ::= { vdslLineConfProfileEntry 30 } 2494 vdslLineConfBandPlan OBJECT-TYPE 2495 SYNTAX INTEGER 2496 { 2497 bandPlan997(1), 2498 bandPlan998(2), 2499 bandPlanFx(3), 2500 other(4) 2501 } 2502 MAX-ACCESS read-create 2503 STATUS current 2504 DESCRIPTION 2505 "The VDSL band plan to be used for the line. 2507 bandPlan997(1) is to be used for 2508 ITU-T G.993.1 Bandplan-B 2509 ETSI Bandplan 2510 ANSI Plan 997 2512 bandPlan998(2) is to be used for 2513 ITU-T G.993.1 Bandplan-A 2514 ANSI Plan 998 2516 bandPlanFx(3) is to be used for 2517 ITU-T G.993.1 Bandplan-C. 2519 other(4) is to be used for 2520 non-standard bandplans. 2522 If this object is set to bandPlanFx(3), then the 2523 object vdslLineConfBandPlanFx MUST also be set." 2524 DEFVAL { bandPlan997 } 2525 ::= { vdslLineConfProfileEntry 31 } 2527 vdslLineConfBandPlanFx OBJECT-TYPE 2528 SYNTAX Unsigned32 (3750..12000) 2529 UNITS "kHz" 2530 MAX-ACCESS read-create 2531 STATUS current 2532 DESCRIPTION 2533 "The frequency limit between bands D2 and U2 when 2534 vdslLineConfBandPlan is set to bandPlanFx(3)." 2535 DEFVAL { 3750 } 2536 ::= { vdslLineConfProfileEntry 32 } 2538 vdslLineConfBandOptUsage OBJECT-TYPE 2539 SYNTAX INTEGER 2540 { 2541 unused(1), 2542 upstream(2), 2543 downstream(3) 2544 } 2545 MAX-ACCESS read-create 2546 STATUS current 2547 DESCRIPTION 2548 "Defines the VDSL link use of the optional frequency 2549 range [25kHz - 138kHz] (Opt). 2551 unused(1) indicates Opt is unused 2552 upstream(2) indicates Opt usage is for upstream 2553 downstream(3) indicates Opt usage is for downstream." 2554 REFERENCE "ITU-T G.993.1, section 6.1" 2555 DEFVAL { unused } 2556 ::= { vdslLineConfProfileEntry 33 } 2558 vdslLineConfUpPsdTemplate OBJECT-TYPE 2559 SYNTAX INTEGER 2560 { 2561 templateMask1(1), 2562 templateMask2(2) 2563 } 2564 MAX-ACCESS read-create 2565 STATUS current 2566 DESCRIPTION 2567 "The upstream PSD template to be used for the line. 2568 Here, templateMask1(1) refers to a notched mask that 2569 limits the transmitted PSD within the internationally 2570 standardized HAM (Handheld Amateur Radio) radio bands, 2571 while templateMask2(2) refers to an unnotched mask. 2573 The masks themselves depend upon the applicable 2574 standard being used (vdslLineConfApplicableStandard)." 2575 REFERENCE "DSL TR-057" 2576 DEFVAL { templateMask1 } 2577 ::= { vdslLineConfProfileEntry 34 } 2579 vdslLineConfDownPsdTemplate OBJECT-TYPE 2580 SYNTAX INTEGER 2581 { 2582 templateMask1(1), 2583 templateMask2(2) 2584 } 2585 MAX-ACCESS read-create 2586 STATUS current 2587 DESCRIPTION 2588 "The downstream PSD template to be used for the line. 2589 Here, templateMask1(1) refers to a notched mask that 2590 limits the transmitted PSD within the internationally 2591 standardized HAM (Handheld Amateur Radio) radio bands, 2592 while templateMask2(2) refers to an unnotched mask. 2594 The masks themselves depend upon the applicable 2595 standard being used (vdslLineConfApplicableStandard)." 2596 REFERENCE "DSL TR-057" 2597 DEFVAL { templateMask1 } 2598 ::= { vdslLineConfProfileEntry 35 } 2600 vdslLineConfHamBandMask OBJECT-TYPE 2601 SYNTAX BITS 2602 { 2603 customNotch1(0), -- custom (region-specific) notch 2604 customNotch2(1), -- custom (region-specific) notch 2605 amateurBand30m(2), -- amateur radio band notch 2606 amateurBand40m(3), -- amateur radio band notch 2607 amateurBand80m(4), -- amateur radio band notch 2608 amateurBand160m(5) -- amateur radio band notch 2609 } 2610 MAX-ACCESS read-create 2611 STATUS current 2612 DESCRIPTION 2613 "The transmit power spectral density mask code, used 2614 to avoid interference with HAM (Handheld Amateur Radio) 2615 radio bands by introducing power control (notching) in one 2616 or more of these bands. 2618 Amateur radio band notching is defined in the VDSL 2619 spectrum as follows: 2621 Band Start Frequency Stop Frequency 2622 ---- ------------------ -------------------------------- 2623 30m 1810 kHz 2000 kHz 2624 40m 3500 kHz 3800 kHz (ETSI); 4000 kHz (ANSI) 2625 80m 7000 kHz 7100 kHz (ETSI); 7300 kHz (ANSI) 2626 160m 10100 kHz 10150 kHz 2628 Notching for each standard band can be enabled or disabled 2629 via the bit mask. 2631 Two custom notches may be specified. If either of these 2632 are enabled via the bit mask, then the following objects 2633 MUST be specified: 2635 If customNotch1 is enabled, then both 2636 vdslLineConfCustomNotch1Start 2637 vdslLineConfCustomNotch1Stop 2638 MUST be specified. 2640 If customNotch2 is enabled, then both 2641 vdslLineConfCustomNotch2Start 2642 vdslLineConfCustomNotch2Stop 2643 MUST be specified." 2644 REFERENCE "DSLF TR-057, section 2.6" 2645 DEFVAL { { } } 2646 ::= { vdslLineConfProfileEntry 36 } 2648 vdslLineConfCustomNotch1Start OBJECT-TYPE 2649 SYNTAX Unsigned32 2650 UNITS "kHz" 2651 MAX-ACCESS read-create 2652 STATUS current 2653 DESCRIPTION 2654 "Specifies the start frequency of custom HAM (Handheld 2655 Amateur Radio) notch 1. vdslLineConfCustomNotch1Start MUST 2656 be less than or equal to vdslLineConfCustomNotch1Stop." 2657 DEFVAL { 0 } 2658 ::= { vdslLineConfProfileEntry 37 } 2660 vdslLineConfCustomNotch1Stop OBJECT-TYPE 2661 SYNTAX Unsigned32 2662 UNITS "kHz" 2663 MAX-ACCESS read-create 2664 STATUS current 2665 DESCRIPTION 2666 "Specifies the stop frequency of custom HAM (Handheld 2667 Amateur Radio) notch 1. vdslLineConfCustomNotch1Stop MUST 2668 be greater than or equal to vdslLineConfCustomNotch1Start." 2669 DEFVAL { 0 } 2670 ::= { vdslLineConfProfileEntry 38 } 2672 vdslLineConfCustomNotch2Start OBJECT-TYPE 2673 SYNTAX Unsigned32 2674 UNITS "kHz" 2675 MAX-ACCESS read-create 2676 STATUS current 2677 DESCRIPTION 2678 "Specifies the start frequency of custom HAM (Handheld 2679 Amateur Radio) notch 2. vdslLineConfCustomNotch2Start MUST 2680 be less than or equal to vdslLineConfCustomNotch2Stop." 2681 DEFVAL { 0 } 2682 ::= { vdslLineConfProfileEntry 39 } 2684 vdslLineConfCustomNotch2Stop OBJECT-TYPE 2685 SYNTAX Unsigned32 2686 UNITS "kHz" 2687 MAX-ACCESS read-create 2688 STATUS current 2689 DESCRIPTION 2690 "Specifies the stop frequency of custom HAM (Handheld 2691 Amateur Radio) notch 2. vdslLineConfCustomNotch2Stop MUST 2692 be greater than or equal to vdslLineConfCustomNotch2Start." 2694 DEFVAL { 0 } 2695 ::= { vdslLineConfProfileEntry 40 } 2697 vdslLineConfDownTargetSlowBurst OBJECT-TYPE 2698 SYNTAX Unsigned32 (0..1275) 2699 UNITS "microseconds" 2700 MAX-ACCESS read-create 2701 STATUS current 2702 DESCRIPTION 2703 "Specifies the target level of impulse noise (burst) 2704 protection for an interleaved (slow) channel." 2705 REFERENCE "ITU-T G.997.1, section 7.3.2.3" 2706 DEFVAL { 0 } 2707 ::= { vdslLineConfProfileEntry 41 } 2709 vdslLineConfUpTargetSlowBurst OBJECT-TYPE 2710 SYNTAX Unsigned32 (0..1275) 2711 UNITS "microseconds" 2712 MAX-ACCESS read-create 2713 STATUS current 2714 DESCRIPTION 2715 "Specifies the target level of impulse noise (burst) 2716 protection for an interleaved (slow) channel." 2717 REFERENCE "ITU-T G.997.1, section 7.3.2.3" 2718 DEFVAL { 0 } 2719 ::= { vdslLineConfProfileEntry 42 } 2721 vdslLineConfDownMaxFastFec OBJECT-TYPE 2722 SYNTAX Unsigned32 (0..50) 2723 UNITS "%" 2724 MAX-ACCESS read-create 2725 STATUS current 2726 DESCRIPTION 2727 "This parameter provisions the maximum level of Forward 2728 Error Correction (FEC) redundancy related overhead to 2729 be maintained for a fast channel." 2730 DEFVAL { 0 } 2731 ::= { vdslLineConfProfileEntry 43 } 2733 vdslLineConfUpMaxFastFec OBJECT-TYPE 2734 SYNTAX Unsigned32 (0..50) 2735 UNITS "%" 2736 MAX-ACCESS read-create 2737 STATUS current 2738 DESCRIPTION 2739 "This parameter provisions the maximum level of Forward 2740 Error Correction (FEC) redundancy related overhead to 2741 be maintained for a fast channel." 2742 DEFVAL { 0 } 2743 ::= { vdslLineConfProfileEntry 44 } 2745 vdslLineConfLineType OBJECT-TYPE 2746 SYNTAX INTEGER 2747 { 2748 noChannel(1), -- no channels exist 2749 fastOnly(2), -- only fast channel exists 2750 interleavedOnly(3), -- only interleaved channel exists 2751 fastOrInterleaved(4), -- either fast or interleaved channel 2752 -- exist, but only one at a time 2753 fastAndInterleaved(5) -- both fast and interleaved channels 2754 -- exist 2755 } 2756 MAX-ACCESS read-create 2757 STATUS current 2758 DESCRIPTION 2759 "This parameter provisions the VDSL physical entity at 2760 start-up by defining whether and how the line will be 2761 channelized, i.e. which channel type(s) are supported. 2762 If the line is to be channelized, the value will be other 2763 than noChannel(1). 2765 This configuration can be activated only during start-up. 2766 Afterwards, the value of vdslLineType coincides with the 2767 value of vdslLineConfLineType. Depending on this value, 2768 the corresponding entries in the ifTable for the 2769 interleaved and the fast channels are enabled or disabled 2770 according to the value of their ifOperStatus. 2772 Defined values are: 2774 noChannel(1) -- no channels exist 2775 fastOnly(2) -- only fast channel exists 2776 interleavedOnly(3) -- only interleaved channel exists 2777 fastOrInterleaved(4) -- either fast or interleaved channel 2778 -- exists, but only one at a time 2779 fastAndInterleaved(5) -- both fast and interleaved channels 2780 -- exist 2782 Note that 'slow' and 'interleaved' refer to the same 2783 channel." 2784 REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" 2785 DEFVAL { noChannel } 2786 ::= { vdslLineConfProfileEntry 45 } 2788 vdslLineConfProfRowStatus OBJECT-TYPE 2789 SYNTAX RowStatus 2790 MAX-ACCESS read-create 2791 STATUS current 2792 DESCRIPTION 2793 "This object is used to create a new row or modify or 2794 delete an existing row in this table. 2796 A profile activated by setting this object to 'active'. 2797 When 'active' is set, the system will validate the profile. 2799 Before a profile can be deleted or taken out of service 2800 (by setting this object to 'destroy' or 'outOfService'), 2801 it must be first unreferenced from all associated lines. 2803 An 'active' profile may be modified at any time. Note 2804 that some changes may require that any referenced lines be 2805 restarted (e.g. vdslLineConfLineType)." 2806 ::= { vdslLineConfProfileEntry 46 } 2808 -- 2809 -- Alarm configuration profile table 2810 -- 2812 vdslLineAlarmConfProfileTable OBJECT-TYPE 2813 SYNTAX SEQUENCE OF VdslLineAlarmConfProfileEntry 2814 MAX-ACCESS not-accessible 2815 STATUS current 2816 DESCRIPTION 2817 "This table contains information on the VDSL line alarm 2818 configuration. One entry in this table reflects a profile 2819 defined by a manager which can be used to configure the 2820 VDSL line alarm thresholds. 2822 Entries in this table MUST be maintained in a 2823 persistent manner." 2824 ::= { vdslMibObjects 20 } 2826 vdslLineAlarmConfProfileEntry OBJECT-TYPE 2827 SYNTAX VdslLineAlarmConfProfileEntry 2828 MAX-ACCESS not-accessible 2829 STATUS current 2830 DESCRIPTION 2831 "Each entry consists of a list of parameters that 2832 represents the configuration of a VDSL line alarm 2833 profile. 2835 A default profile with an index of 'DEFVAL', will 2836 always exist and its parameters will be set to vendor 2837 specific values, unless otherwise specified in this 2838 document." 2839 INDEX { vdslLineAlarmConfProfileName } 2840 ::= { vdslLineAlarmConfProfileTable 1 } 2842 VdslLineAlarmConfProfileEntry ::= 2843 SEQUENCE 2844 { 2845 vdslLineAlarmConfProfileName SnmpAdminString, 2846 vdslLineAlarmConfThresh15MinLofs HCPerfIntervalThreshold, 2847 vdslLineAlarmConfThresh15MinLoss HCPerfIntervalThreshold, 2848 vdslLineAlarmConfThresh15MinLprs HCPerfIntervalThreshold, 2849 vdslLineAlarmConfThresh15MinLols HCPerfIntervalThreshold, 2850 vdslLineAlarmConfThresh15MinESs HCPerfIntervalThreshold, 2851 vdslLineAlarmConfThresh15MinSESs HCPerfIntervalThreshold, 2852 vdslLineAlarmConfThresh15MinUASs HCPerfIntervalThreshold, 2853 vdslLineAlarmConfInitFailure TruthValue, 2854 vdslLineAlarmConfProfRowStatus RowStatus 2855 } 2857 vdslLineAlarmConfProfileName OBJECT-TYPE 2858 SYNTAX SnmpAdminString (SIZE (1..32)) 2859 MAX-ACCESS not-accessible 2860 STATUS current 2861 DESCRIPTION 2862 "The name for this profile as specified by an 2863 adminstrator." 2864 ::= { vdslLineAlarmConfProfileEntry 1 } 2866 vdslLineAlarmConfThresh15MinLofs OBJECT-TYPE 2867 SYNTAX HCPerfIntervalThreshold 2868 UNITS "seconds" 2869 MAX-ACCESS read-create 2870 STATUS current 2871 DESCRIPTION 2872 "This object configures the threshold for the number of 2873 loss of frame seconds (lofs) within any given 15-minute 2874 performance data collection interval. If the value of 2875 loss of frame seconds in a particular 15-minute collection 2876 interval reaches/exceeds this value, a 2877 vdslPerfLofsThreshNotification notification will be 2878 generated. No more than one notification will be sent 2879 per interval." 2880 DEFVAL { 0 } 2881 ::= { vdslLineAlarmConfProfileEntry 2 } 2883 vdslLineAlarmConfThresh15MinLoss OBJECT-TYPE 2884 SYNTAX HCPerfIntervalThreshold 2885 UNITS "seconds" 2886 MAX-ACCESS read-create 2887 STATUS current 2888 DESCRIPTION 2889 "This object configures the threshold for the number of 2890 loss of signal seconds (loss) within any given 15-minute 2891 performance data collection interval. If the value of 2892 loss of signal seconds in a particular 15-minute 2893 collection interval reaches/exceeds this value, a 2894 vdslPerfLossThreshNotification notification will be 2895 generated. One notification will be sent per interval 2896 per endpoint." 2897 DEFVAL { 0 } 2898 ::= { vdslLineAlarmConfProfileEntry 3 } 2900 vdslLineAlarmConfThresh15MinLprs OBJECT-TYPE 2901 SYNTAX HCPerfIntervalThreshold 2902 UNITS "seconds" 2903 MAX-ACCESS read-create 2904 STATUS current 2905 DESCRIPTION 2906 "This object configures the threshold for the number of 2907 loss of power seconds (lprs) within any given 15-minute 2908 performance data collection interval. If the value of 2909 loss of power seconds in a particular 15-minute collection 2910 interval reaches/exceeds this value, a 2911 vdslPerfLprsThreshNotification notification will be 2912 generated. No more than one notification will be sent 2913 per interval." 2914 DEFVAL { 0 } 2915 ::= { vdslLineAlarmConfProfileEntry 4 } 2917 vdslLineAlarmConfThresh15MinLols OBJECT-TYPE 2918 SYNTAX HCPerfIntervalThreshold 2919 UNITS "seconds" 2920 MAX-ACCESS read-create 2921 STATUS current 2922 DESCRIPTION 2923 "This object configures the threshold for the number of 2924 loss of link seconds (lols) within any given 15-minute 2925 performance data collection interval. If the value of 2926 loss of power seconds in a particular 15-minute collection 2927 interval reaches/exceeds this value, a 2928 vdslPerfLolsThreshNotification notification will be 2929 generated. No more than one notification will be sent 2930 per interval." 2931 DEFVAL { 0 } 2932 ::= { vdslLineAlarmConfProfileEntry 5 } 2934 vdslLineAlarmConfThresh15MinESs OBJECT-TYPE 2935 SYNTAX HCPerfIntervalThreshold 2936 UNITS "seconds" 2937 MAX-ACCESS read-create 2938 STATUS current 2939 DESCRIPTION 2940 "This object configures the threshold for the number of 2941 errored seconds (ESs) within any given 15-minute 2942 performance data collection interval. If the value of 2943 errored seconds in a particular 15-minute collection 2944 interval reaches/exceeds this value, a 2945 vdslPerfESsThreshNotification notification will be 2946 generated. No more than one notification will be sent 2947 per interval." 2948 DEFVAL { 0 } 2949 ::= { vdslLineAlarmConfProfileEntry 6 } 2951 vdslLineAlarmConfThresh15MinSESs OBJECT-TYPE 2952 SYNTAX HCPerfIntervalThreshold 2953 UNITS "seconds" 2954 MAX-ACCESS read-create 2955 STATUS current 2956 DESCRIPTION 2957 "This object configures the threshold for the number of 2958 severely errored seconds (SESs) within any given 15-minute 2959 performance data collection interval. If the value of 2960 severely errored seconds in a particular 15-minute 2961 collection interval reaches/exceeds this value, a 2962 vdslPerfSESsThreshNotification notification will be 2963 generated. No more than one notification will be sent 2964 per interval." 2965 DEFVAL { 0 } 2966 ::= { vdslLineAlarmConfProfileEntry 7 } 2968 vdslLineAlarmConfThresh15MinUASs OBJECT-TYPE 2969 SYNTAX HCPerfIntervalThreshold 2970 UNITS "seconds" 2971 MAX-ACCESS read-create 2972 STATUS current 2973 DESCRIPTION 2974 "This object configures the threshold for the number of 2975 unavailable seconds (UASs) within any given 15-minute 2976 performance data collection interval. If the value of 2977 unavailable seconds in a particular 15-minute collection 2978 interval reaches/exceeds this value, a 2979 vdslPerfUASsThreshNotification notification will be 2980 generated. No more than one notification will be sent 2981 per interval." 2982 DEFVAL { 0 } 2983 ::= { vdslLineAlarmConfProfileEntry 8 } 2985 vdslLineAlarmConfInitFailure OBJECT-TYPE 2986 SYNTAX TruthValue 2987 MAX-ACCESS read-create 2988 STATUS current 2989 DESCRIPTION 2990 "This object specifies if a vdslInitFailureNotification 2991 notification will be generated if an initialization 2992 failure occurs." 2993 DEFVAL { false } 2994 ::= { vdslLineAlarmConfProfileEntry 9 } 2996 vdslLineAlarmConfProfRowStatus OBJECT-TYPE 2997 SYNTAX RowStatus 2998 MAX-ACCESS read-create 2999 STATUS current 3000 DESCRIPTION 3001 "This object is used to create a new row or modify or 3002 delete an existing row in this table. 3004 A profile activated by setting this object to 'active'. 3005 When 'active' is set, the system will validate the profile. 3007 Before a profile can be deleted or taken out of service, 3008 (by setting this object to 'destroy' or 'outOfService') it 3009 must be first unreferenced from all associated lines. 3011 An 'active' profile may be modified at any time." 3013 ::= { vdslLineAlarmConfProfileEntry 10 } 3015 -- Notification definitions 3017 vdslNotifications OBJECT IDENTIFIER ::= { vdslLineMib 0 } 3019 vdslPerfLofsThreshNotification NOTIFICATION-TYPE 3020 OBJECTS { 3021 vdslPerfDataCurr15MinLofs 3022 } 3023 STATUS current 3024 DESCRIPTION 3025 "Loss of Framing 15-minute interval threshold 3026 (vdslLineAlarmConfThresh15MinLofs) reached." 3027 ::= { vdslNotifications 1 } 3029 vdslPerfLossThreshNotification NOTIFICATION-TYPE 3030 OBJECTS { 3031 vdslPerfDataCurr15MinLoss 3032 } 3033 STATUS current 3034 DESCRIPTION 3035 "Loss of Signal 15-minute interval threshold 3036 (vdslLineAlarmConfThresh15MinLoss) reached." 3037 ::= { vdslNotifications 2 } 3039 vdslPerfLprsThreshNotification NOTIFICATION-TYPE 3040 OBJECTS { 3041 vdslPerfDataCurr15MinLprs 3042 } 3043 STATUS current 3044 DESCRIPTION 3045 "Loss of Power 15-minute interval threshold 3046 (vdslLineAlarmConfThresh15MinLprs) reached." 3047 ::= { vdslNotifications 3 } 3049 vdslPerfLolsThreshNotification NOTIFICATION-TYPE 3050 OBJECTS { 3051 vdslPerfDataCurr15MinLols 3052 } 3053 STATUS current 3054 DESCRIPTION 3055 "Loss of Link 15-minute interval threshold 3056 (vdslLineAlarmConfThresh15MinLols) reached." 3057 ::= { vdslNotifications 4 } 3059 vdslPerfESsThreshNotification NOTIFICATION-TYPE 3060 OBJECTS { 3061 vdslPerfDataCurr15MinESs 3062 } 3063 STATUS current 3064 DESCRIPTION 3065 "Errored Seconds 15-minute interval threshold 3066 (vdslLineAlarmConfThresh15MinESs) reached." 3067 ::= { vdslNotifications 5 } 3069 vdslPerfSESsThreshNotification NOTIFICATION-TYPE 3070 OBJECTS { 3071 vdslPerfDataCurr15MinSESs 3072 } 3073 STATUS current 3074 DESCRIPTION 3075 "Severely Errored Seconds 15-minute interval threshold 3076 (vdslLineAlarmConfThresh15MinSESs) reached." 3077 ::= { vdslNotifications 6 } 3079 vdslPerfUASsThreshNotification NOTIFICATION-TYPE 3080 OBJECTS { 3081 vdslPerfDataCurr15MinUASs 3082 } 3083 STATUS current 3084 DESCRIPTION 3085 "Unavailable Seconds 15-minute interval threshold 3086 (vdslLineAlarmConfThresh15MinUASs) reached." 3087 ::= { vdslNotifications 7 } 3089 vdslDownMaxSnrMgnNotification NOTIFICATION-TYPE 3090 OBJECTS { 3091 vdslPhysCurrSnrMgn 3092 } 3093 STATUS current 3094 DESCRIPTION 3095 "The downstream Signal to Noise Margin exceeded 3096 vdslLineConfDownMaxSnrMgn. The object 3097 vdslPhysCurrSnrMgn will contain the Signal to Noise 3098 margin as measured by the VTU-R." 3099 ::= { vdslNotifications 8 } 3101 vdslDownMinSnrMgnNotification NOTIFICATION-TYPE 3102 OBJECTS { 3103 vdslPhysCurrSnrMgn 3104 } 3105 STATUS current 3106 DESCRIPTION 3107 "The downstream Signal to Noise Margin fell below 3108 vdslLineConfDownMinSnrMgn. The object vdslPhysCurrSnrMgn 3109 will contain the Signal to Noise margin as measured by 3110 the VTU-R." 3111 ::= { vdslNotifications 9 } 3113 vdslUpMaxSnrMgnNotification NOTIFICATION-TYPE 3114 OBJECTS { 3115 vdslPhysCurrSnrMgn 3116 } 3117 STATUS current 3118 DESCRIPTION 3119 "The upstream Signal to Noise Margin exceeded 3120 vdslLineConfUpMaxSnrMgn. The object vdslPhysCurrSnrMgn 3121 will contain the Signal to Noise margin as measured 3122 by the VTU-C." 3123 ::= { vdslNotifications 10 } 3125 vdslUpMinSnrMgnNotification NOTIFICATION-TYPE 3126 OBJECTS { 3127 vdslPhysCurrSnrMgn 3128 } 3129 STATUS current 3130 DESCRIPTION 3131 "The upstream Signal to Noise Margin fell below 3132 vdslLineConfUpMinSnrMgn. The object vdslPhysCurrSnrMgn 3133 will contain the Signal to Noise margin as measured 3134 by the VTU-C." 3135 ::= { vdslNotifications 11 } 3137 vdslInitFailureNotification NOTIFICATION-TYPE 3138 OBJECTS { 3139 vdslPhysCurrStatus 3140 } 3141 STATUS current 3142 DESCRIPTION 3143 "Vtu initialization failed. See vdslPhysCurrStatus for 3144 potential reasons." 3145 ::= { vdslNotifications 12 } 3147 -- conformance information 3149 vdslConformance OBJECT IDENTIFIER ::= { vdslLineMib 3 } 3150 vdslGroups OBJECT IDENTIFIER ::= { vdslConformance 1 } 3151 vdslCompliances OBJECT IDENTIFIER ::= { vdslConformance 2 } 3153 vdslLineMibCompliance MODULE-COMPLIANCE 3154 STATUS current 3155 DESCRIPTION 3156 "The compliance statement for SNMP entities which 3157 manage VDSL interfaces." 3159 MODULE -- this module 3160 MANDATORY-GROUPS 3161 { 3162 vdslGroup, 3163 vdslNotificationGroup 3164 } 3165 ::= { vdslCompliances 1 } 3167 -- units of conformance 3169 vdslGroup OBJECT-GROUP 3170 OBJECTS 3171 { 3172 vdslLineCoding, 3173 vdslLineType, 3174 vdslLineConfProfile, 3175 vdslLineAlarmConfProfile, 3176 vdslPhysInvSerialNumber, 3177 vdslPhysInvVendorID, 3178 vdslPhysInvVersionNumber, 3179 vdslPhysCurrSnrMgn, 3180 vdslPhysCurrAtn, 3181 vdslPhysCurrStatus, 3182 vdslPhysCurrOutputPwr, 3183 vdslPhysCurrAttainableRate, 3184 vdslPhysCurrLineRate, 3185 vdslChanInterleaveDelay, 3186 vdslChanCrcBlockLength, 3187 vdslChanCurrTxRate, 3188 vdslChanCurrTxSlowBurstProtect, 3189 vdslChanCurrTxFastFec, 3190 vdslPerfDataValidIntervals, 3191 vdslPerfDataInvalidIntervals, 3192 vdslPerfDataLofs, 3193 vdslPerfDataLoss, 3194 vdslPerfDataLprs, 3195 vdslPerfDataLols, 3196 vdslPerfDataESs, 3197 vdslPerfDataSESs, 3198 vdslPerfDataUASs, 3199 vdslPerfDataInits, 3200 vdslPerfDataCurr15MinTimeElapsed, 3201 vdslPerfDataCurr15MinLofs, 3202 vdslPerfDataCurr15MinLoss, 3203 vdslPerfDataCurr15MinLprs, 3204 vdslPerfDataCurr15MinLols, 3205 vdslPerfDataCurr15MinESs, 3206 vdslPerfDataCurr15MinSESs, 3207 vdslPerfDataCurr15MinUASs, 3208 vdslPerfDataCurr15MinInits, 3209 vdslPerfData1DayValidIntervals, 3210 vdslPerfData1DayInvalidIntervals, 3211 vdslPerfDataCurr1DayTimeElapsed, 3212 vdslPerfDataCurr1DayLofs, 3213 vdslPerfDataCurr1DayLoss, 3214 vdslPerfDataCurr1DayLprs, 3215 vdslPerfDataCurr1DayLols, 3216 vdslPerfDataCurr1DayESs, 3217 vdslPerfDataCurr1DaySESs, 3218 vdslPerfDataCurr1DayUASs, 3219 vdslPerfDataCurr1DayInits, 3220 vdslPerfIntervalLofs, 3221 vdslPerfIntervalLoss, 3222 vdslPerfIntervalLprs, 3223 vdslPerfIntervalLols, 3224 vdslPerfIntervalESs, 3225 vdslPerfIntervalSESs, 3226 vdslPerfIntervalUASs, 3227 vdslPerfIntervalInits, 3228 vdslPerf1DayIntervalMoniSecs, 3229 vdslPerf1DayIntervalLofs, 3230 vdslPerf1DayIntervalLoss, 3231 vdslPerf1DayIntervalLprs, 3232 vdslPerf1DayIntervalLols, 3233 vdslPerf1DayIntervalESs, 3234 vdslPerf1DayIntervalSESs, 3235 vdslPerf1DayIntervalUASs, 3236 vdslPerf1DayIntervalInits, 3237 vdslChanValidIntervals, 3238 vdslChanInvalidIntervals, 3239 vdslChanFixedOctets, 3240 vdslChanBadBlks, 3241 vdslChanCurr15MinTimeElapsed, 3242 vdslChanCurr15MinFixedOctets, 3243 vdslChanCurr15MinBadBlks, 3244 vdslChan1DayValidIntervals, 3245 vdslChan1DayInvalidIntervals, 3246 vdslChanCurr1DayTimeElapsed, 3247 vdslChanCurr1DayFixedOctets, 3248 vdslChanCurr1DayBadBlks, 3249 vdslChanIntervalFixedOctets, 3250 vdslChanIntervalBadBlks, 3251 vdslChan1DayIntervalMoniSecs, 3252 vdslChan1DayIntervalFixedOctets, 3253 vdslChan1DayIntervalBadBlks, 3254 vdslLineConfDownRateMode, 3255 vdslLineConfUpRateMode, 3256 vdslLineConfDownMaxPwr, 3257 vdslLineConfUpMaxPwr, 3258 vdslLineConfDownMaxSnrMgn, 3259 vdslLineConfDownMinSnrMgn, 3260 vdslLineConfDownTargetSnrMgn, 3261 vdslLineConfUpMaxSnrMgn, 3262 vdslLineConfUpMinSnrMgn, 3263 vdslLineConfUpTargetSnrMgn, 3264 vdslLineConfDownFastMaxDataRate, 3265 vdslLineConfDownFastMinDataRate, 3266 vdslLineConfDownSlowMaxDataRate, 3267 vdslLineConfDownSlowMinDataRate, 3268 vdslLineConfUpFastMaxDataRate, 3269 vdslLineConfUpFastMinDataRate, 3270 vdslLineConfUpSlowMaxDataRate, 3271 vdslLineConfUpSlowMinDataRate, 3272 vdslLineConfDownRateRatio, 3273 vdslLineConfUpRateRatio, 3274 vdslLineConfDownMaxInterDelay, 3275 vdslLineConfUpMaxInterDelay, 3276 vdslLineConfDownPboControl, 3277 vdslLineConfUpPboControl, 3278 vdslLineConfDownPboLevel, 3279 vdslLineConfUpPboLevel, 3280 vdslLineConfDeploymentScenario, 3281 vdslLineConfAdslPresence, 3282 vdslLineConfApplicableStandard, 3283 vdslLineConfBandPlan, 3284 vdslLineConfBandPlanFx, 3285 vdslLineConfBandOptUsage, 3286 vdslLineConfUpPsdTemplate, 3287 vdslLineConfDownPsdTemplate, 3288 vdslLineConfHamBandMask, 3289 vdslLineConfCustomNotch1Start, 3290 vdslLineConfCustomNotch1Stop, 3291 vdslLineConfCustomNotch2Start, 3292 vdslLineConfCustomNotch2Stop, 3293 vdslLineConfDownTargetSlowBurst, 3294 vdslLineConfUpTargetSlowBurst, 3295 vdslLineConfDownMaxFastFec, 3296 vdslLineConfUpMaxFastFec, 3297 vdslLineConfLineType, 3298 vdslLineConfProfRowStatus, 3299 vdslLineAlarmConfThresh15MinLofs, 3300 vdslLineAlarmConfThresh15MinLoss, 3301 vdslLineAlarmConfThresh15MinLprs, 3302 vdslLineAlarmConfThresh15MinLols, 3303 vdslLineAlarmConfThresh15MinESs, 3304 vdslLineAlarmConfThresh15MinSESs, 3305 vdslLineAlarmConfThresh15MinUASs, 3306 vdslLineAlarmConfInitFailure, 3307 vdslLineAlarmConfProfRowStatus 3308 } 3309 STATUS current 3310 DESCRIPTION 3311 "A collection of objects providing information about 3312 a VDSL Line." 3313 ::= { vdslGroups 1 } 3315 vdslNotificationGroup NOTIFICATION-GROUP 3316 NOTIFICATIONS 3317 { 3318 vdslPerfLofsThreshNotification, 3319 vdslPerfLossThreshNotification, 3320 vdslPerfLprsThreshNotification, 3321 vdslPerfLolsThreshNotification, 3322 vdslPerfESsThreshNotification, 3323 vdslPerfSESsThreshNotification, 3324 vdslPerfUASsThreshNotification, 3325 vdslDownMaxSnrMgnNotification, 3326 vdslDownMinSnrMgnNotification, 3327 vdslUpMaxSnrMgnNotification, 3328 vdslUpMinSnrMgnNotification, 3329 vdslInitFailureNotification 3330 } 3332 STATUS current 3333 DESCRIPTION 3334 "This group supports notifications of significant 3335 conditions associated with VDSL Lines." 3336 ::= { vdslGroups 2 } 3338 END 3340 5. Intellectual Property Notice 3342 The IETF takes no position regarding the validity or scope of any 3343 intellectual property or other rights that might be claimed to 3344 pertain to the implementation or use of the technology described in 3345 this document or the extent to which any license under such rights 3346 might or might not be available; neither does it represent that it 3347 has made any effort to identify any such rights. Information on the 3348 IETF's procedures with respect to rights in standards-track and 3349 standards-related documentation can be found in BCP-11. Copies of 3350 claims of rights made available for publication and any assurances 3351 of licenses to be made available, or the result of an attempt made 3352 to obtain a general license or permission for the use of such 3353 proprietary rights by implementors or users of this specification 3354 can be obtained from the IETF Secretariat. 3356 The IETF invites any interested party to bring to its attention any 3357 copyrights, patents or patent applications, or other proprietary 3358 rights which may cover technology that may be required to practice 3359 this standard. Please address the information to the IETF Executive 3360 Director. 3362 6. Normative References 3364 [DSLFTR057] DSL Forum TR-057, "VDSL Network Element Management", 3365 February 2003. 3367 [ETSI2701] ETSI TS 101 270-1 V1.2.1 "Transmission and Multiplexing 3368 (TM); Access transmission systems on metallic access 3369 cables; Very high speed Digital Subscriber Line (VDSL); 3370 Part 1: Functional requirements", October 1999. 3372 [ETSI2702] ETSI TS 101 270-2 V1.1.1 "Transmission and Multiplexing 3373 (TM); Access transmission systems on metallic access 3374 cables; Very high speed Digital Subscriber Line (VDSL); 3375 Part 1: Transceiver specification", February 2001. 3377 [ITU9931] ITU-T G.993.1 "Very-high-speed digital subscriber line 3378 foundation", November 2001. 3380 [ITU9971] ITU-T G.997.1 "Physical layer management for Digital 3381 Subscriber Line (DSL) Transceivers", July 1999. 3383 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 3384 Requirement Levels", BCP 14, RFC 2119, March 1997. 3386 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 3387 J., Rose, M. and S. Waldbusser, "Structure of 3388 Management Information Version 2 (SMIv2)", STD 58, RFC 3389 2578, April 1999. 3391 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 3392 J., Rose, M. and S. Waldbusser, "Textual Conventions 3393 for SMIv2", STD 58, RFC 2579, April 1999. 3395 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 3396 J., Rose, M. and S. Waldbusser, "Conformance 3397 Statements for SMIv2", STD 58, RFC 2580, April 1999. 3399 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces 3400 Group MIB", RFC 2863, June 2000. 3402 [RFC3418] Presuhn, R., "Management Information Base (MIB) for the 3403 Simple Network Management Protocol (SNMP)", STD 62, RFC 3404 3418, December 2002. 3406 [RFC3593] Tesink, K., "Textual Conventions for MIB Modules Using 3407 Performance History Based on 15 Minute Intervals", RFC 3408 3593, September 2003. 3410 [RFCXXXX] Ray, B. and R. Abbi, "High Capacity Textual Conventions 3411 for MIB Modules Using Performance History Based on 3412 15 Minute Intervals", RFC XXXX, YYYY 2003. 3413 --- RFC Ed: please replace XXXX with the RFC number assigned to the 3414 --- accompanying HC-TC MIB and YYYY with the appropriate month. 3416 [T1E1311] ANSI T1E1.4/2001-311, "Very-high-bit-rate Digital 3417 Subscriber Line (VDSL) Metallic Interface, Part 1: 3418 Functional Requirements and Common Specification", 3419 February 2001. 3421 [T1E1011] ANSI T1E1.4/2001-011R3, "VDSL Metallic Interface, Part 3422 2: Technical Specification for a Single-Carrier 3423 Modulation (SCM) Transceiver", November 2001. 3425 [T1E1013] ANSI T1E1.4/2001-013R4, "VDSL Metallic Interface, Part 3426 3: Technical Specification for a Multi-Carrier 3427 Modulation (MCM) Transceiver", November 2000. 3429 7. Informative References 3431 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 3432 "Introduction and Applicability Statements for Internet- 3433 Standard Management Framework", RFC 3410, December 2002. 3435 [RFC3415] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based 3436 Access Control Model (VACM) for the Simple Network 3437 Management Protocol (SNMP)", RFC 3415, December 2002. 3439 8. Security Considerations 3441 There are a number of management objects defined in this MIB module 3442 with a MAX-ACCESS clause of read-write and/or read-create. Such 3443 objects may be considered sensitive or vulnerable in some network 3444 environments. The support for SET operations in a non-secure 3445 environment without proper protection can have a negative effect on 3446 network operations. These are the tables and objects and their 3447 sensitivity/vulnerability: 3449 Some of the readable objects in this MIB module (i.e., objects with 3450 a MAX-ACCESS other than not-accessible) may be considered sensitive 3451 or vulnerable in some network environments. It is thus important to 3452 control even GET and/or NOTIFY access to these objects and possibly 3453 to even encrypt the values of these objects when sending them over 3454 the network via SNMP. 3456 VDSL layer connectivity from the Vtur will permit the subscriber 3457 to manipulate both the VDSL link directly and the VDSL embedded 3458 operations channel (EOC) for their own loop. For example, unchecked 3459 or unfiltered fluctuations initiated by the subscriber could 3460 generate sufficient notifications to potentially overwhelm either 3461 the management interface to the network or the element manager. 3463 Additionally, allowing write access to configuration data may allow 3464 an end-user to increase their service levels or affect other 3465 end-users in either a positive or negative manner. For this reason, 3466 the following tables should be considered to contain sensitive 3467 information: 3469 vdslLineTable 3470 vdslLineConfProfileTable 3471 vdslLineAlarmConfProfileTable 3473 Individual line utilization information, available via the 3474 performance tables, may be considered sensitive. For example, 3475 if an end-user has a far lower line utilization during certain 3476 periods of the day, it may indicate an empty office or residence. 3477 For these reasons, the following tables should be considered to 3478 contain sensitive information: 3480 - vdslPerfDataTable 3481 - vdslPerfIntervalTable 3482 - vdslPerf1DayIntervalTable 3484 Further, notifications generated by agents implementing this MIB 3485 will contain threshold and performance information. 3487 It is thus important to control even GET access to the objects 3488 within these tables and possibly to even encrypt the values of 3489 these objects when sending them over the network via SNMP. Not 3490 all versions of SNMP provide features for such a secure 3491 environment. 3493 SNMP versions prior to SNMPv3 did not include adequate security. 3494 Even if the network itself is secure (for example by using IPSec), 3495 even then, there is no control as to who on the secure network is 3496 allowed to access and GET/SET (read/change/create/delete) the 3497 objects in this MIB module. 3499 It is RECOMMENDED that implementers consider the security features 3500 as provided by the SNMPv3 framework (see [RFC3410], section 8), 3501 including full support for the SNMPv3 cryptographic mechanisms (for 3502 authentication and privacy). 3504 Further, deployment of SNMP versions prior to SNMPv3 is NOT 3505 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 3506 enable cryptographic security. It is then a customer/operator 3507 responsibility to ensure that the SNMP entity giving access to an 3508 instance of this MIB module is properly configured to give access to 3509 the objects only to those principals (users) that have legitimate 3510 rights to indeed GET or SET (change/create/delete) them. 3512 9. Acknowledgements 3514 Greg Bathrick (Nokia) 3516 Umberto Bonollo (NEC) 3518 Andrew Cheers (NEC) 3520 Felix Flemisch (Siemens) 3522 David Horton (CiTR) 3524 Travis Levin (Paradyne) 3526 Moti Morgenstern (Inovia) 3528 Randy Presuhn (BMC) 3530 Say Sabit (NLC) 3532 Bert Wijnen (Lucent) 3534 10. Authors' Addresses 3536 Bob Ray 3537 PESA Switching Systems, Inc. 3538 330-A Wynn Drive 3539 Huntsville, AL 35805 3540 USA 3542 Phone: +1 256 726 9200 ext. 142 3543 Fax: +1 256 726 9271 3544 Email: rray@pesa.com 3546 Rajesh Abbi 3547 Alcatel USA 3548 2912 Wake Forest Road 3549 Raleigh, NC 27609-7860 3550 USA 3552 Phone: +1 919 850 6194 3553 Email: Rajesh.Abbi@alcatel.com 3555 11. Full Copyright Statement 3557 Copyright (C) The Internet Society (2003). All Rights Reserved. 3558 This document and translations of it may be copied and furnished to 3559 others, and derivative works that comment on or otherwise explain it 3560 or assist in its implementation may be prepared, copied, published 3561 and distributed, in whole or in part, without restriction of any 3562 kind, provided that the above copyright notice and this paragraph 3563 are included on all such copies and derivative works. However, this 3564 document itself may not be modified in any way, such as by removing 3565 the copyright notice or references to the Internet Society or other 3566 Internet organizations, except as needed for the purpose of 3567 developing Internet standards in which case the procedures for 3568 copyrights defined in the Internet Standards process must be 3569 followed, or as required to translate it into languages other than 3570 English. 3572 The limited permissions granted above are perpetual and will not be 3573 revoked by the Internet Society or its successors or assigns. 3575 This document and the information contained herein is provided on an 3576 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 3577 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 3578 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 3579 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 3580 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.