idnits 2.17.1 draft-ietf-adslmib-vdsl-08.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There is 1 instance of too long lines in the document, the longest one being 3 characters in excess of 72. ** The abstract seems to contain references (RFC2580], ETSI2701,, ETSI2702,, ITU9931,, ITU9971], [T1E1311,T1E1011,, [RFC2578,RFC2579,, T1E1013,), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Unrecognized Status in 'Category: Internet Draft', assuming Proposed Standard (Expected one of 'Standards Track', 'Full Standard', 'Draft Standard', 'Proposed Standard', 'Best Current Practice', 'Informational', 'Experimental', 'Informational', 'Historic'.) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (April 2003) is 7675 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Looks like a reference, but probably isn't: '12' on line 3237 -- Looks like a reference, but probably isn't: '15' on line 3238 == Unused Reference: 'ETSI2701' is defined on line 3089, but no explicit reference was found in the text == Unused Reference: 'ETSI2702' is defined on line 3094, but no explicit reference was found in the text == Unused Reference: 'ITU9931' is defined on line 3099, but no explicit reference was found in the text == Unused Reference: 'ITU9971' is defined on line 3102, but no explicit reference was found in the text == Unused Reference: 'RFC2662' is defined on line 3149, but no explicit reference was found in the text == Unused Reference: 'T1E1311' is defined on line 3155, but no explicit reference was found in the text == Unused Reference: 'T1E1011' is defined on line 3160, but no explicit reference was found in the text == Unused Reference: 'T1E1013' is defined on line 3164, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'ETSI2701' -- Possible downref: Non-RFC (?) normative reference: ref. 'ETSI2702' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU9931' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU9971' ** Downref: Normative reference to an Historic RFC: RFC 1901 ** Obsolete normative reference: RFC 1905 (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 1906 (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2493 (Obsoleted by RFC 3593) ** Obsolete normative reference: RFC 2571 (Obsoleted by RFC 3411) ** Obsolete normative reference: RFC 2572 (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (Obsoleted by RFC 3414) -- Possible downref: Non-RFC (?) normative reference: ref. 'T1E1311' -- Possible downref: Non-RFC (?) normative reference: ref. 'T1E1011' -- Possible downref: Non-RFC (?) normative reference: ref. 'T1E1013' -- Obsolete informational reference (is this intentional?): RFC 2570 (Obsoleted by RFC 3410) -- Obsolete informational reference (is this intentional?): RFC 2573 (Obsoleted by RFC 3413) -- Obsolete informational reference (is this intentional?): RFC 2575 (Obsoleted by RFC 3415) Summary: 11 errors (**), 0 flaws (~~), 10 warnings (==), 14 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group B. Ray 2 Category: Internet Draft PESA Switching Systems 3 R. Abbi 4 Alcatel 5 April 2003 7 Definitions of Managed Objects for Very High 8 Speed Digital Subscriber Lines (VDSL) 9 draft-ietf-adslmib-vdsl-08.txt 11 Status of this Memo 13 This document is an Internet-Draft and is subject to all provisions 14 of Section 10 of RFC2026. 16 Internet-Drafts are working documents of the Internet Engineering 17 Task Force (IETF), its areas, and its working groups. Note that 18 other groups may also distribute working documents as Internet- 19 Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six months 22 and may be updated, replaced, or obsoleted by other documents at any 23 time. It is inappropriate to use Internet-Drafts as reference 24 material or to cite them other than as "work in progress." 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/1id-abstracts.txt 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html 32 Copyright Notice 34 Copyright (C) The Internet Society (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 [T1E1311, T1E1011, T1E1013, 42 ETSI2701, ETSI2702, ITU9931, ITU9971]. 44 This document specifies a MIB module in a manner that is compliant 45 to the SMIv2 (STD 58 [RFC2578, RFC2579, RFC2580]). 47 Table of Contents 49 1. The SNMP Management Framework ............................. 2 50 2. Overview .................................................. 3 51 2.1 Relationship of the VDSL Line MIB to other MIBs ........... 3 52 2.2 Conventions used in the MIB ............................... 5 53 2.3 Structure ................................................. 6 54 2.4 Counters, Interval Buckets and Thresholds ................. 7 55 2.5 Profiles .................................................. 7 56 2.6 Notifications ............................................. 8 57 2.7 Persistence ............................................... 9 58 3. Conformance and Compliance ................................ 10 59 4. Definitions ............................................... 10 60 References ................................................ 60 61 Security Considerations ................................... 62 62 IANA Considerations ....................................... 63 63 Acknowledgments ........................................... 63 64 Intellectual Property Notice .............................. 64 65 Authors' Addresses ........................................ 64 66 Full Copyright Statement .................................. 64 68 1. The SNMP Management Framework 70 The SNMP Management Framework presently consists of five major 71 components: 73 o An overall architecture, described in RFC 2571 [RFC2571]. 75 o Mechanisms for describing and naming objects and events for the 76 purpose of management. The first version of this Structure of 77 Management Information (SMI) is called SMIv1 and described in 78 STD 16 [RFC1155, RFC1212] and RFC 1215 [RFC1215]. The second 79 version, called SMIv2, is described in STD 58 [RFC2578, RFC2579, 80 RFC2580]. 82 o Message protocols for transferring management information. The 83 first version of the SNMP message protocol is called SNMPv1 and 84 described in STD 15 [RFC1157]. A second version of the SNMP 85 message protocol, which is not an Internet standards track 86 protocol, is called SNMPv2c and described in RFC 1901 [RFC1901] 87 and RFC 1906 [RFC1906]. The third version of the message 88 protocol is called SNMPv3 and described in RFC 1906 [RFC1906], 89 RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. 91 o Protocol operations for accessing management information. The 92 first set of protocol operations and associated PDU formats is 93 described in STD 15 [RFC1157]. A second set of protocol 94 operations and associated PDU formats is described in RFC 1905 95 [RFC1905]. 97 o A set of fundamental applications described in RFC 2573 [RFC2573] 98 and the view-based access control mechanism described in RFC 99 2575 [RFC2575]. 101 A more detailed introduction to the current SNMP Management Framework 102 can be found in RFC 2570 [RFC2570]. 104 Managed objects are accessed via a virtual information store, termed 105 the Management Information Base or MIB. Objects in the MIB are 106 defined using the mechanisms defined in the SMI. 108 This memo specifies a MIB module that is compliant to the SMIv2. The 109 textual conventions used in this MIB module cannot be translated 110 to SMIv1 since the Counter64 type does not exist in SMIv1. 112 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 113 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 114 this document are to be interpreted as described in RFC 2119 115 [RFC2119]. 117 2. Overview 119 This document describes an SNMP MIB for managing VDSL Lines. These 120 definitions are based upon the specifications for VDSL as defined 121 in T1E1, ETSI, and ITU documentation [T1E1311, T1E1011, T1E1013, 122 ETSI2701, ETSI2702, ITU9931, ITU9971]. 124 The MIB is located in the MIB tree under MIB 2 transmission, as 125 discussed in the MIB-2 Integration (RFC 2863 [RFC2863]) section of 126 this document. 128 2.1 Relationship of the VDSL Line MIB to other MIBs 130 This section outlines the relationship of this MIB with other MIBs 131 described in RFCs. Specifically, IF-MIB as presented RFC 2863 132 [RFC2863] is discussed. 134 2.1.1 General IF-MIB Integration (RFC 2863) 136 The VDSL Line MIB specifies the detailed attributes of a data 137 interface. As such, it needs to integrate with RFC 2863 [RFC2863]. 138 The IANA has assigned the following ifType to VDSL: 140 IANAifType ::= TEXTUAL-CONVENTION 141 ... 143 SYNTAX INTEGER { 144 ... 145 vdsl(97), -- Very H-speed Digital Subscrib. Loop 146 ... 147 } 149 Additionally, a VDSL line may contain an optional fast channel 150 and an optional interleaved channel which also integrate into RFC 151 2863 [RFC2863]. The IANA has assigned the following ifTypes to these 152 channels: 154 IANAifType ::= TEXTUAL-CONVENTION 155 ... 156 SYNTAX INTEGER { 157 ... 158 interleave (124), -- Interleave channel 159 fast (125), -- Fast channel 160 ... 161 } 163 2.1.2 Usage of ifTable 165 The MIB branch identified by this ifType contains tables appropriate 166 for this interface type. Most such tables extend the ifEntry table, 167 and are indexed by ifIndex. For interfaces in systems implementing 168 this MIB, those table entries indexed by ifIndex MUST be persistent. 170 The following attributes are part of the mandatory ifGeneral group in 171 RFC 2863 [RFC2863], and are not duplicated in the VDSL Line MIB. 173 =================================================================== 174 ifIndex Interface index. 176 ifDescr See interfaces MIB [RFC2863]. 178 ifType vdsl(97), 179 interleaved(124), or 180 fast(125) 182 ifSpeed Set as appropriate. 184 ifPhysAddress This object MUST have an octet string 185 with zero length. 187 ifAdminStatus See interfaces MIB [RFC2863]. 189 ifOperStatus See interfaces MIB [RFC2863]. 191 ifLastChange See interfaces MIB [RFC2863]. 193 ifName See interfaces MIB [RFC2863]. 195 ifHighSpeed Set as appropriate. 197 ifConnectorPresent Set as appropriate. 199 ifLinkUpDownTrapEnable Default to enabled(1). 201 =================================================================== 202 Figure 1: Use of ifTable Objects 204 Section 2.3, below, describes the structure of this MIB in relation 205 to ifEntry in greater detail. 207 2.2 Conventions used in the MIB 209 2.2.1 Naming Conventions 211 A. Vtuc -- (VTUC) modem at near (Central) end of line 212 B. Vtur -- (VTUR) modem at Remote end of line 213 C. Vtu -- One of either Vtuc or Vtur 214 D. Curr -- Current 215 E. Prev -- Previous 216 F. Atn -- Attenuation 217 G. ES -- Errored Second 218 H. SES -- Severely Errored Second 219 I. UAS -- Unavailable Second 220 J. LCS -- Line Code Specific 221 K. Lof -- Loss of Frame 222 L. Lol -- Loss of Link 223 M. Los -- Loss of Signal 224 N. Lpr -- Loss of Power 225 O. xxxs -- interval of Seconds in which xxx occurs 226 (e.g., xxx=Lof, Los, Lpr, Lol) 227 P. Max -- Maximum 228 Q. Mgn -- Margin 229 R. Min -- Minimum 230 S. Psd -- Power Spectral Density 231 T. Snr -- Signal to Noise Ratio 232 U. Tx -- Transmit 233 V. Blks -- Blocks 235 2.2.2 Textual Conventions 237 The following textual conventions are defined to reflect the line 238 topology in the MIB (further discussed in the following section) 239 and to define the behavior of the statistics to be maintained 240 by an agent. 242 o VdslLineCodingType : 244 Attributes with this syntax identify the line coding used. 245 Specified as an INTEGER, the three values are: 247 other(1) -- none of the following 248 mcm(2) -- Multiple Carrier Modulation 249 scm(3) -- Single Carrier Modulation 251 o VdslLineEntity : 253 Attributes with this syntax reference the two sides of a line. 254 Specified as an INTEGER, the two values are: 256 vtuc(1) -- central site modem 257 vtur(2) -- remote site modem 259 2.3 Structure 261 The MIB is structured into following MIB groups: 263 o vdslGroup : 265 This group supports all line code independent MIB objects found 266 in this MIB. The following tables contain objects permitted for 267 ifType vdsl(97): 269 - vdslLineTable 270 - vdslPhysTable 271 - vdslPerfDataTable 272 - vdslPerfIntervalTable 273 - vdslPerf1DayIntervalTable 274 - vdslLineConfProfileTable 275 - vdslLineAlarmConfProfileTable 277 The following tables contain objects permitted for ifTypes 278 interleaved(124) and (fast): 280 - vdslChanTable 281 - vdslChanPerfDataTable 282 - vdslChanPerfIntervalTable 283 - vdslChanPerf1DayIntervalTable 285 Figure 2, below, displays the relationship of the tables in the 286 vdslGroup to ifEntry (and each other): 288 ifEntry(ifType=97) ----> vdslLineTableEntry 1:(0..1) 290 vdslLineTableEntry ----> vdslPhysTableEntry 1:(0..2) 291 ----> vdslPerfDataEntry 1:(0..2) 292 ----> vdslLineConfProfileEntry 1:(0..1) 293 ----> vdslLineAlarmConfProfileEntry 1:(0..1) 295 vdslPhysTableEntry ----> vdslPerfIntervalEntry 1:(0..96) 296 ----> vdslPerf1DayIntervalEntry 1:(0..30) 298 ifEntry(ifType=124) ----> vdslChanEntry 1:(0..2) 299 ----> vdslChanPerfDataEntry 1:(0..2) 301 ifEntry(ifType=125) ----> vdslChanEntry 1:(0..2) 302 ----> vdslChanPerfDataEntry 1:(0..2) 304 vdslChanEntry ----> vdslchanPerfIntervalEntry 1:(0..96) 305 ----> vdslchan1DayPerfIntervalEntry 1:(0..30) 307 Figure 2: Table Relationships 309 2.3.1 Line Topology 311 A VDSL Line consists of a two units - Vtuc (the central termination 312 unit) and a Vtur (the remote termination unit). 314 <-- Network Side Customer Side --> 316 || 318 +-------+ +-------+ 319 | | | | 320 | Vtuc +------------------+ Vtur | 321 | | | | 322 +-------+ +-------+ 324 Figure 3: General topology for a VDSL Line 326 2.4 Counters, Interval Buckets and Thresholds 328 For Loss of Frame (lof), Loss of Link (lol), Loss of Signal (los), 329 and Loss of Power (lpr), Errored Seconds (ES), Severely Errored 330 Seconds (SES), and Unavailable Seconds (UAS) there are event 331 counters, current 15-minute, 0 to 96 15-minute history bucket(s), 332 and 0 to 30 1-day history bucket(s) of "interval-counters". Each 333 current 15-minute event bucket has an associated threshold 334 notification. 336 Each of these counters uses the textual conventions defined in the 337 HC-PerfHist-TC-MIB. The HC-PerfHist-TC-MIB is a work-in-progress, 338 but simply defines 64-bit versions of the textual conventions 339 found in RFC 2493 [RFC2493]. 341 There is no requirement for an agent to ensure a fixed relationship 342 between the start of a fifteen minute and any wall clock; however 343 some implementations may align the fifteen minute intervals with 344 quarter hours. Likewise, an implementation may choose to align one 345 day intervals with the start of a day. 347 Counters are not reset when an Vtu is reinitialized, only when the 348 agent is reset or reinitialized (or under specific request outside 349 the scope of this MIB). 351 2.5 Profiles 353 As a managed node can handle a large number of Vtus, (e.g., hundreds 354 or perhaps thousands of lines), provisioning every parameter on every 355 Vtu may become burdensome. Moreover, most lines are provisioned 356 identically with the same set of parameters. To simplify the 357 provisioning process, this MIB makes use of profiles. A profile is a 358 set of parameters that can be shared by multiple lines using the same 359 configuration. 361 The following profiles are used in this MIB: 363 o Line Configuration Profiles - Line configuration profiles contain 364 parameters for configuring VDSL lines. They are defined in the 365 vdslLineConfProfileTable. 367 o Alarm Configuration Profiles - These profiles contain parameters 368 for configuring alarm thresholds for VDSL modems. These profiles 369 are defined in the vdslLineAlarmConfProfileTable. 371 One or more lines may be configured to share parameters of a single 372 profile by setting its vdslLineConfProfile objects to the value of 373 this profile. If a change is made to the profile, all lines that 374 refer to it will be reconfigured to the changed parameters. Before 375 a profile can be deleted or taken out of service it must be first 376 unreferenced from all associated lines. 378 Implementations MUST provide a default profile with an index value of 379 `DEFVAL' for each profile type. The values of the associated 380 parameters will be vendor specific unless otherwise indicated in this 381 document. Before a line's profiles have been set, these profiles 382 will be automatically used by setting vdslLineConfProfile and 383 vdslLineAlarmConfProfile to `DEFVAL' where appropriate. This 384 default profile name, 'DEFVAL', is considered reserved in the context 385 of profiles defined in this MIB. 387 Profiles are created, assigned, and deleted dynamically using the 388 profile name and profile row status in each of the ten profile 389 tables (nine line configuration tables and one alarm configuration 390 table). 392 Profile changes MUST take effect immediately. These changes MAY 393 result in a restart (hard reset or soft restart) of the units on the 394 line. 396 2.6 Notifications 398 The ability to generate the SNMP notifications coldStart/WarmStart 399 (per [RFC2863]) which are per agent (e.g., per Digital Subscriber 400 Line Access Multiplexer, or DSLAM, in such a device), and 401 linkUp/linkDown (per [RFC2863]) which are per interface (i.e., VDSL 402 line) is required. 404 The notifications defined in this MIB are for initialization failure 405 and for the threshold crossings associated with the following events: 406 lof, lol, los, lpr, ES, SES, and UAS. Each threshold has its own 407 enable/threshold value. When that value is 0, the notification is 408 disabled. 410 A linkDown notification MAY be generated whenever any of lof, lol, 411 los, lpr, ES, SES, or UAS threshold crossing event (as defined 412 in this MIB) occurs. The corresponding linkUp notification MAY be 413 sent when all link failure conditions are cleared. 415 The vdslCurrStatus is a bitmask representing all outstanding error 416 conditions associated with a particular VDSL modem. Note that since 417 status of remote modems is obtained via the EOC, this information 418 may be unavailable for units that are unreachable via EOC during a 419 line error condition. Therefore, not all conditions may always be 420 included in its current status. Notifications corresponding to the 421 bit fields in this object are defined. 423 A threshold notification occurs whenever the corresponding current 424 15-minute interval error counter becomes equal to, or exceeds the 425 threshold value. One notification may be sent per interval per 426 interface. Since the current 15-minute counter are reset to 0 every 427 15 minutes, if the condition persists, the notification may recur as 428 often as every 15 minutes. For example, to get a notification 429 whenever a "loss of" event occurs (but at most once every 15 430 minutes), set the corresponding threshold to 1. The agent will 431 generate a notification when the event originally occurs. 433 Note that the Network Management System, or NMS, may receive a 434 linkDown notification, as well, if enabled (via 435 ifLinkUpDownTrapEnable [RFC2863]). At the beginning of the next 15 436 minute interval, the counter is reset. When the first second goes 437 by and the event occurs, the current interval bucket will be 1, 438 which equals the threshold and the notification will be sent again. 440 2.7 Persistence 442 All objects defined in this MIB which may be set (read-write or 443 read-create), should be stored persistently. Following is an 444 exhaustive list of these persistent objects: 446 vdslLineConfProfile 447 vdslLineAlarmConfProfile 448 vdslLineConfProfileName 449 vdslLineConfDownstreamRateMode 450 vdslLineConfUpstreamRateMode 451 vdslLineConfDownstreamMaxPwr 452 vdslLineConfUpstreamMaxPwr 453 vdslLineConfDownstreamMaxSnrMgn 454 vdslLineConfDownstreamMinSnrMgn 455 vdslLineConfDownstreamTargetSnrMgn 456 vdslLineConfUpstreamMaxSnrMgn 457 vdslLineConfUpstreamMinSnrMgn 458 vdslLineConfUpstreamTargetSnrMgn 459 vdslLineConfDownstreamFastMaxDataRate 460 vdslLineConfDownstreamFastMinDataRate 461 vdslLineConfDownstreamSlowMaxDataRate 462 vdslLineConfDownstreamSlowMinDataRate 463 vdslLineConfUpstreamFastMaxDataRate 464 vdslLineConfUpstreamFastMinDataRate 465 vdslLineConfUpstreamSlowMaxDataRate 466 vdslLineConfUpstreamSlowMinDataRate 467 vdslLineConfDownstreamRateRatio 468 vdslLineConfUpstreamRateRatio 469 vdslLineConfDownstreamMaxInterDelay 470 vdslLineConfUpstreamMaxInterDelay 471 vdslLineConfDownstreamPboControl 472 vdslLineConfUpstreamPboControl 473 vdslLineConfDownstreamPboLevel 474 vdslLineConfUpstreamPboLevel 475 vdslLineConfDeploymentScenario 476 vdslLineConfAdslPresence 477 vdslLineConfApplicableStandard 478 vdslLineConfBandPlan 479 vdslLineConfBandPlanFx 480 vdslLineConfBandU0Usage 481 vdslLineConfUpstreamPsdTemplate 482 vdslLineConfDownstreamPsdTemplate 483 vdslLineConfHamBandMask 484 vdslLineConfCustomNotch1Start 485 vdslLineConfCustomNotch1Stop 486 vdslLineConfCustomNotch2Start 487 vdslLineConfCustomNotch2Stop 488 vdslLineConfProfileRowStatus 489 vdslLineAlarmConfProfileName 490 vdslThresh15MinLofs 491 vdslThresh15MinLoss 492 vdslThresh15MinLprs 493 vdslThresh15MinLols 494 vdslThresh15MinESs 495 vdslThresh15MinSESs 496 vdslThresh15MinUASs 497 vdslInitFailureNotificationEnable 498 vdslLineAlarmConfProfileRowStatus 500 It should also be noted that interface indices in this MIB are 501 maintained persistently. VACM data relating to these should be 502 stored persistently as well. 504 3. Conformance and Compliance 506 For VDSL lines, the following group is mandatory: 508 - vdslGroup 510 4. Definitions 511 VDSL-LINE-MIB DEFINITIONS ::= BEGIN 513 IMPORTS 515 MODULE-IDENTITY, 516 OBJECT-TYPE, 517 Counter64, 518 Gauge32, 519 Integer32, 520 Unsigned32, 521 NOTIFICATION-TYPE, 522 transmission FROM SNMPv2-SMI 523 TEXTUAL-CONVENTION, 524 RowStatus, 525 TruthValue FROM SNMPv2-TC 526 HCPerfValidIntervals, 527 HCPerfInvalidIntervals, 528 HCPerfTimeElapsed, 529 HCPerfIntervalThreshold, 530 HCPerfCurrentCount, 531 HCPerfIntervalCount FROM HC-PerfHist-TC-MIB 532 MODULE-COMPLIANCE, 533 OBJECT-GROUP, 534 NOTIFICATION-GROUP FROM SNMPv2-CONF 535 ifIndex FROM IF-MIB 536 SnmpAdminString FROM SNMP-FRAMEWORK-MIB; 538 vdslMIB MODULE-IDENTITY 539 LAST-UPDATED "200304180000Z" -- April 18, 2003 540 ORGANIZATION "ADSLMIB Working Group" 541 CONTACT-INFO "WG-email: adslmib@ietf.org 542 Info: https://www1.ietf.org/mailman/listinfo/adslmib 544 Chair: Mike Sneed 545 Sand Channel Systems 546 Postal: P.O. Box 37324 547 Raleigh NC 27627-7324 548 Email: sneedmike@hotmail.com 549 Phone: +1 206 600 7022 551 Co-editor: Bob Ray 552 PESA Switching Systems, Inc. 553 Postal: 330-A Wynn Drive 554 Huntsville, AL 35805 USA 555 Email: rray@pesa.com 556 Phone: +1 256 726 9200 ext. 142 558 Co-editor: Rajesh Abbi 559 Alcatel USA 560 Postal: 2912 Wake Forest Road 561 Raleigh, NC 27609-7860 USA 563 Email: Rajesh.Abbi@alcatel.com 564 Phone: +1 919 850 6194 566 " 567 DESCRIPTION 568 "The MIB module defining objects for the management of a pair of 569 VDSL modems at each end of the VDSL line. Each such line has 570 an entry in an ifTable which may include multiple modem lines. 571 An agent may reside at either end of the VDSL line however the 572 MIB is designed to require no management communication between 573 them beyond that inherent in the low-level VDSL line protocol. 574 The agent may monitor and control this protocol for its needs. 576 VDSL lines may support optional Fast or Interleaved channels. 577 If these are supported, additional entries corresponding to the 578 supported channels must be created in the ifTable. Thus a VDSL 579 line that supports both channels will have three entries in the 580 ifTable, one for each physical, fast, and interleaved, whose 581 ifType values are equal to vdsl(97), fast(125), and 582 interleaved(124), respectively. The ifStackTable is used to 583 represent the relationship between the entries. 585 Naming Conventions: 586 Vtuc -- (VTUC) modem at near (Central) end of line 587 Vtur -- (VTUR) modem at Remote end of line 588 Vtu -- One of either Vtuc or Vtur 589 Curr -- Current 590 Prev -- Previous 591 Atn -- Attenuation 592 ES -- Errored Second. 593 LCS -- Line Code Specific 594 Lof -- Loss of Frame 595 Lol -- Loss of Link 596 Los -- Loss of Signal 597 Lpr -- Loss of Power 598 xxxs -- interval of Seconds in which xxx occurs 599 (e.g., xxx=Lof, Los, Lpr) 600 Max -- Maximum 601 Mgn -- Margin 602 Min -- Minimum 603 Psd -- Power Spectral Density 604 Snr -- Signal to Noise Ratio 605 Tx -- Transmit 606 Blks -- Blocks 607 " 608 REVISION "200111010000Z" -- November 1, 2001 609 DESCRIPTION "Initial draft." 611 REVISION "200203310000Z" -- March 31, 2002 612 DESCRIPTION "Added R. Abbi as co-author." 614 REVISION "200204090000Z" -- April 9, 2002 615 DESCRIPTION "Removed use of IMPLIED profile indices." 617 REVISION "200206160000Z" -- June 16, 2002 618 DESCRIPTION "Revised per input from DSL Forum." 620 REVISION "200209230000Z" -- September 23, 2002 621 DESCRIPTION "Revised per more input from DSL Forum." 623 REVISION "200210150000Z" -- October 15, 2002 624 DESCRIPTION "Modified per input from Randy Presuhn and 625 Moti Morgenstern." 627 REVISION "200210300000Z" -- October 30, 2002 628 DESCRIPTION "Modified per input from Umberto Bonollo 629 and Travis Levin." 631 REVISION "200212300000Z" -- December 30, 2002 632 DESCRIPTION "Changed profile indices to strings." 634 REVISION "200304180000Z" -- April 18, 2003 635 DESCRIPTION "Brought into conformance with DSLF TR-057." 637 ::= { transmission xxxx } 639 vdslLineMib OBJECT IDENTIFIER ::= { vdslMIB 1 } 640 vdslMibObjects OBJECT IDENTIFIER ::= { vdslLineMib 1 } 642 -- 643 -- textual conventions used in this MIB 644 -- 646 VdslLineCodingType ::= TEXTUAL-CONVENTION 647 STATUS current 648 DESCRIPTION 649 "This data type is used as the syntax for the VDSL 650 Line Code." 651 SYNTAX INTEGER 652 { 653 other(1), -- none of the following 654 mcm(2), -- Multiple Carrier Modulation 655 scm(3) -- Single Carrier Modulation 656 } 658 VdslLineEntity ::= TEXTUAL-CONVENTION 659 STATUS current 660 DESCRIPTION 661 "Identifies a modem as being either Vtuc or Vtur. A 662 VDSL line consists of two modems, a Vtuc and a Vtur." 663 SYNTAX INTEGER 664 { 665 vtuc(1), -- central site modem 666 vtur(2) -- remote site modem 667 } 669 -- 670 -- objects 671 -- 673 vdslLineTable OBJECT-TYPE 674 SYNTAX SEQUENCE OF VdslLineEntry 675 MAX-ACCESS not-accessible 676 STATUS current 677 DESCRIPTION 678 "This table includes common attributes describing 679 both ends of the line. It is required for all VDSL 680 physical interfaces. VDSL physical interfaces are 681 those ifEntries where ifType is equal to vdsl(97)." 682 ::= { vdslMibObjects 1 } 684 vdslLineEntry OBJECT-TYPE 685 SYNTAX VdslLineEntry 686 MAX-ACCESS not-accessible 687 STATUS current 688 DESCRIPTION "An entry in the vdslLineTable." 689 INDEX { ifIndex } 690 ::= { vdslLineTable 1 } 692 VdslLineEntry ::= 693 SEQUENCE 694 { 695 vdslLineCoding VdslLineCodingType, 696 vdslLineType INTEGER, 697 vdslLineConfProfile SnmpAdminString, 698 vdslLineAlarmConfProfile SnmpAdminString 699 } 701 vdslLineCoding OBJECT-TYPE 702 SYNTAX VdslLineCodingType 703 MAX-ACCESS read-only 704 STATUS current 705 DESCRIPTION 706 "Specifies the VDSL coding type used on this line." 707 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 708 ::= { vdslLineEntry 1 } 710 vdslLineType OBJECT-TYPE 711 SYNTAX INTEGER 712 { 713 noChannel(1), -- no channels exist 714 fastOnly(2), -- fast channel only 715 slowOnly(3), -- slow channel only 716 either(4), -- either fast or slow channel exist 717 both(5) -- both fast and slow channels exist 718 } 720 MAX-ACCESS read-only 721 STATUS current 722 DESCRIPTION 723 "Defines the type of VDSL physical line 724 entity that exists, by defining whether and how 725 the line is channelized. If the line is channelized, 726 the value will be other than noChannel(1). This 727 object defines which channel type(s) are supported. 729 In the case that the line is channelized, the manager 730 can use the ifStackTable to determine the ifIndex for 731 the associated channel(s). 733 Note that slow and interleaved refer to the same 734 channel." 735 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 736 ::= { vdslLineEntry 2 } 738 vdslLineConfProfile OBJECT-TYPE 739 SYNTAX SnmpAdminString (SIZE(1..32)) 740 MAX-ACCESS read-write 741 STATUS current 742 DESCRIPTION 743 "The value of this object identifies the row 744 in the VDSL Line Configuration Profile Table, 745 ( vdslLineConfProfileTable ), which applies for this 746 VDSL line, and channels if applicable." 747 ::= { vdslLineEntry 3 } 749 vdslLineAlarmConfProfile OBJECT-TYPE 750 SYNTAX SnmpAdminString (SIZE(1..32)) 751 MAX-ACCESS read-write 752 STATUS current 753 DESCRIPTION 754 "The value of this object identifies the row in the VDSL 755 Line Alarm Configuration Profile Table, 756 ( vdslLineAlarmConfProfileTable ), which applies to this 757 VDSL line, and channels if applicable." 758 ::= { vdslLineEntry 4 } 760 vdslPhysTable OBJECT-TYPE 761 SYNTAX SEQUENCE OF VdslPhysEntry 762 MAX-ACCESS not-accessible 763 STATUS current 764 DESCRIPTION 765 "This table provides one row for each Vtu. Each row 766 contains the Physical Layer Parameters table for that 767 Vtu. VDSL physical interfaces are those ifEntries where 768 ifType is equal to vdsl(97)." 769 ::= { vdslMibObjects 2 } 771 vdslPhysEntry OBJECT-TYPE 772 SYNTAX VdslPhysEntry 773 MAX-ACCESS not-accessible 774 STATUS current 775 DESCRIPTION "An entry in the vdslPhysTable." 776 INDEX { ifIndex, 777 vdslPhysSide } 778 ::= { vdslPhysTable 1 } 780 VdslPhysEntry ::= 781 SEQUENCE 782 { 783 vdslPhysSide VdslLineEntity, 784 vdslInvSerialNumber SnmpAdminString, 785 vdslInvVendorID SnmpAdminString, 786 vdslInvVersionNumber SnmpAdminString, 787 vdslCurrSnrMgn Integer32, 788 vdslCurrAtn Gauge32, 789 vdslCurrStatus BITS, 790 vdslCurrOutputPwr Integer32, 791 vdslCurrAttainableRate Gauge32, 792 vdslCurrLineRate Gauge32 793 } 795 vdslPhysSide OBJECT-TYPE 796 SYNTAX VdslLineEntity 797 MAX-ACCESS not-accessible 798 STATUS current 799 DESCRIPTION 800 "Identifies whether the modem is the Vtuc or Vtur." 801 ::= { vdslPhysEntry 1 } 803 vdslInvSerialNumber OBJECT-TYPE 804 SYNTAX SnmpAdminString(SIZE (0..32)) 805 MAX-ACCESS read-only 806 STATUS current 807 DESCRIPTION 808 "The vendor specific string that identifies the 809 vendor equipment." 810 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 811 ::= { vdslPhysEntry 2 } 813 vdslInvVendorID OBJECT-TYPE 814 SYNTAX SnmpAdminString (SIZE (0..16)) 815 MAX-ACCESS read-only 816 STATUS current 817 DESCRIPTION 818 "The vendor ID code is a copy of the binary vendor 819 identification field expressed as readable characters." 820 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 821 ::= { vdslPhysEntry 3 } 823 vdslInvVersionNumber OBJECT-TYPE 824 SYNTAX SnmpAdminString (SIZE (0..16)) 825 MAX-ACCESS read-only 826 STATUS current 827 DESCRIPTION 828 "The vendor specific version number sent by this Vtu 829 as part of the initialization messages. It is a copy 830 of the binary version number field expressed as 831 readable characters." 832 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 833 ::= { vdslPhysEntry 4 } 835 vdslCurrSnrMgn OBJECT-TYPE 836 SYNTAX Integer32 (-127..127) 837 UNITS "0.25dBm" 838 MAX-ACCESS read-only 839 STATUS current 840 DESCRIPTION 841 "Noise Margin as seen by this Vtu with respect to its 842 received signal in 0.25dB. The effective range is 843 -31.75 to +31.75dB." 844 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 845 ::= { vdslPhysEntry 5 } 847 vdslCurrAtn OBJECT-TYPE 848 SYNTAX Gauge32 (0..255) 849 UNITS "0.25dBm" 850 MAX-ACCESS read-only 851 STATUS current 852 DESCRIPTION 853 "Measured difference in the total power transmitted by 854 the peer Vtu and the total power received by this Vtu. 855 The effective range is 0 to +63.75dB." 856 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 857 ::= { vdslPhysEntry 6 } 859 vdslCurrStatus OBJECT-TYPE 860 SYNTAX BITS 861 { 862 noDefect(0), 863 lossOfFraming(1), 864 lossOfSignal(2), 865 lossOfPower(3), 866 lossOfSignalQuality(4), 867 lossOfLink(5), 868 dataInitFailure(6), 869 configInitFailure(7), 870 protocolInitFailure(8), 871 noPeerVtuPresent(9) 872 } 873 MAX-ACCESS read-only 874 STATUS current 875 DESCRIPTION 876 "Indicates current state of the Vtu line. This is a 877 bit-map of possible conditions. The various bit 878 positions are: 880 0 noDefect There no defects on the line 882 1 lossOfFraming Vtu failure due to not receiving 883 a valid frame. 885 2 lossOfSignal Vtu failure due to not receiving 886 signal. 888 3 lossOfPower Vtu failure due to loss of power. 890 4 lossOfSignalQuality Loss of Signal Quality is declared 891 when the Noise Margin falls below 892 the Minimum Noise Margin, or the 893 bit-error-rate exceeds 10^-7. 895 5 lossOfLink Vtu failure due to inability to 896 link with peer Vtu. Set whenever 897 the transceiver is in the 'Warm 898 Start' state. 900 6 dataInitFailure Vtu failure during initialization 901 due to bit errors corrupting 902 startup exchange data. 904 7 configInitFailure Vtu failure during initialization 905 due to peer Vtu not able to support 906 requested configuration. 908 8 protocolInitFailure Vtu failure during initialization 909 due to incompatible protocol used 910 by the peer Vtu. 912 9 noPeerVtuPresent Vtu failure during initialization 913 due to no activation sequence 914 detected from peer Vtu. 916 This is intended to supplement ifOperStatus." 917 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 918 ::= { vdslPhysEntry 7 } 920 vdslCurrOutputPwr OBJECT-TYPE 921 SYNTAX Integer32 (0..160) 922 UNITS "0.1dBm" 923 MAX-ACCESS read-only 924 STATUS current 925 DESCRIPTION 926 "Measured total output power transmitted by this VTU. 927 This is the measurement that was reported during 928 the last activation sequence." 929 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 930 ::= { vdslPhysEntry 8 } 932 vdslCurrAttainableRate OBJECT-TYPE 933 SYNTAX Gauge32 934 UNITS "kbps" 935 MAX-ACCESS read-only 936 STATUS current 937 DESCRIPTION 938 "Indicates the maximum currently attainable data rate 939 in steps of 1024 bits/second by the Vtu. This value 940 will be equal to or greater than vdslCurrLineRate. 941 Note that for SCM, the minimum and maximum data rates 942 are equal." 943 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 944 ::= { vdslPhysEntry 9 } 946 vdslCurrLineRate OBJECT-TYPE 947 SYNTAX Gauge32 948 UNITS "kbps" 949 MAX-ACCESS read-only 950 STATUS current 951 DESCRIPTION 952 "Indicates the current data rate in steps of 1024 953 bits/second by the Vtu. This value will be less than 954 or equal to vdslCurrAttainableRate." 955 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 956 ::= { vdslPhysEntry 10 } 958 vdslChanTable OBJECT-TYPE 959 SYNTAX SEQUENCE OF VdslChanEntry 960 MAX-ACCESS not-accessible 961 STATUS current 962 DESCRIPTION 963 "This table provides one row for each Vtu channel. 964 VDSL channel interfaces are those ifEntries where 965 ifType is equal to interleave(124) or fast(125)." 966 ::= { vdslMibObjects 3 } 968 vdslChanEntry OBJECT-TYPE 969 SYNTAX VdslChanEntry 970 MAX-ACCESS not-accessible 971 STATUS current 972 DESCRIPTION 973 "An entry in the vdslChanTable." 974 INDEX { ifIndex, 975 vdslPhysSide } 976 ::= { vdslChanTable 1 } 978 VdslChanEntry ::= 979 SEQUENCE 980 { 981 vdslChanInterleaveDelay Gauge32, 982 vdslChanCrcBlockLength Gauge32, 983 vdslChanCurrTxRate Gauge32, 984 vdslChanOverhead Gauge32, 985 vdslChanBurstProtection Gauge32 986 } 988 vdslChanInterleaveDelay OBJECT-TYPE 989 SYNTAX Gauge32 990 UNITS "ms" 991 MAX-ACCESS read-only 992 STATUS current 993 DESCRIPTION 994 "Interleave Delay for this channel. 996 Interleave delay applies only to the interleave 997 (slow) channel and defines the mapping (relative 998 spacing) between subsequent input bytes at the 999 interleaver input and their placement in the bit 1000 stream at the interleaver output. Larger numbers 1001 provide greater separation between consecutive 1002 input bytes in the output bit stream allowing for 1003 improved impulse noise immunity at the expense of 1004 payload latency. 1006 In the case where the ifType is fast(125), use 1007 noSuchObject." 1008 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1009 ::= { vdslChanEntry 1 } 1011 vdslChanCrcBlockLength OBJECT-TYPE 1012 SYNTAX Gauge32 1013 UNITS "byte" 1014 MAX-ACCESS read-only 1015 STATUS current 1016 DESCRIPTION 1017 "Indicates the length of the channel data-block 1018 on which the CRC operates." 1019 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1020 ::= { vdslChanEntry 2 } 1022 vdslChanCurrTxRate OBJECT-TYPE 1023 SYNTAX Gauge32 1024 UNITS "kbps" 1025 MAX-ACCESS read-only 1026 STATUS current 1027 DESCRIPTION 1028 "Actual transmit data rate on this channel." 1029 ::= { vdslChanEntry 3 } 1031 vdslChanOverhead OBJECT-TYPE 1032 SYNTAX Gauge32 1033 UNITS "%" 1034 MAX-ACCESS read-only 1035 STATUS current 1036 DESCRIPTION 1037 "TBD" 1038 ::= { vdslChanEntry 4 } 1040 vdslChanBurstProtection OBJECT-TYPE 1041 SYNTAX Gauge32 1042 UNITS "ms" 1043 MAX-ACCESS read-only 1044 STATUS current 1045 DESCRIPTION 1046 "TBD" 1047 ::= { vdslChanEntry 5 } 1049 vdslPerfDataTable OBJECT-TYPE 1050 SYNTAX SEQUENCE OF VdslPerfDataEntry 1051 MAX-ACCESS not-accessible 1052 STATUS current 1053 DESCRIPTION 1054 "This table provides one row for each VDSL physical 1055 interface. VDSL physical interfaces are those ifEntries 1056 where ifType is equal to vdsl(97)." 1057 ::= { vdslMibObjects 4 } 1059 vdslPerfDataEntry OBJECT-TYPE 1060 SYNTAX VdslPerfDataEntry 1061 MAX-ACCESS not-accessible 1062 STATUS current 1063 DESCRIPTION 1064 "An entry in the vdslPerfDataTable." 1065 INDEX { ifIndex, 1066 vdslPhysSide } 1067 ::= { vdslPerfDataTable 1 } 1069 VdslPerfDataEntry ::= 1070 SEQUENCE 1071 { 1072 vdslPerfValidIntervals HCPerfValidIntervals, 1073 vdslPerfInvalidIntervals HCPerfInvalidIntervals, 1074 vdslPerfLofs Counter64, 1075 vdslPerfLoss Counter64, 1076 vdslPerfLprs Counter64, 1077 vdslPerfLols Counter64, 1078 vdslPerfESs Counter64, 1079 vdslPerfSESs Counter64, 1080 vdslPerfUASs Counter64, 1081 vdslPerfInits Counter64, 1082 vdslPerfCurr15MinTimeElapsed HCPerfTimeElapsed, 1083 vdslPerfCurr15MinLofs HCPerfCurrentCount, 1084 vdslPerfCurr15MinLoss HCPerfCurrentCount, 1085 vdslPerfCurr15MinLprs HCPerfCurrentCount, 1086 vdslPerfCurr15MinLols HCPerfCurrentCount, 1087 vdslPerfCurr15MinESs HCPerfCurrentCount, 1088 vdslPerfCurr15MinSESs HCPerfCurrentCount, 1089 vdslPerfCurr15MinUASs HCPerfCurrentCount, 1090 vdslPerfCurr15MinInits HCPerfCurrentCount, 1091 vdslPerf1DayValidIntervals HCPerfValidIntervals, 1092 vdslPerf1DayInvalidIntervals HCPerfInvalidIntervals, 1093 vdslPerfCurr1DayTimeElapsed HCPerfTimeElapsed, 1094 vdslPerfCurr1DayLofs Counter64, 1095 vdslPerfCurr1DayLoss Counter64, 1096 vdslPerfCurr1DayLprs Counter64, 1097 vdslPerfCurr1DayLols Counter64, 1098 vdslPerfCurr1DayESs Counter64, 1099 vdslPerfCurr1DaySESs Counter64, 1100 vdslPerfCurr1DayUASs Counter64, 1101 vdslPerfCurr1DayInits Counter64 1102 } 1104 vdslPerfValidIntervals OBJECT-TYPE 1105 SYNTAX HCPerfValidIntervals 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 vdslPerfInvalidIntervals OBJECT-TYPE 1114 SYNTAX HCPerfInvalidIntervals 1115 MAX-ACCESS read-only 1116 STATUS current 1117 DESCRIPTION 1118 "Invalid Intervals per definition found in 1119 HC-PerfHist-TC-MIB." 1120 ::= { vdslPerfDataEntry 2 } 1122 vdslPerfLofs OBJECT-TYPE 1123 SYNTAX Counter64 1124 UNITS "seconds" 1125 MAX-ACCESS read-only 1126 STATUS current 1127 DESCRIPTION 1128 "Count of seconds since the unit was last reset that there 1129 was Loss of Framing." 1130 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1131 ::= { vdslPerfDataEntry 3 } 1133 vdslPerfLoss OBJECT-TYPE 1134 SYNTAX Counter64 1135 UNITS "seconds" 1136 MAX-ACCESS read-only 1137 STATUS current 1138 DESCRIPTION 1139 "Count of seconds since the unit was last reset that there 1140 was Loss of Signal." 1141 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1142 ::= { vdslPerfDataEntry 4 } 1144 vdslPerfLprs OBJECT-TYPE 1145 SYNTAX Counter64 1146 UNITS "seconds" 1147 MAX-ACCESS read-only 1148 STATUS current 1149 DESCRIPTION 1150 "Count of seconds since the unit was last reset that there 1151 was Loss of Power." 1152 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1153 ::= { vdslPerfDataEntry 5 } 1155 vdslPerfLols OBJECT-TYPE 1156 SYNTAX Counter64 1157 UNITS "seconds" 1158 MAX-ACCESS read-only 1159 STATUS current 1160 DESCRIPTION 1161 "Count of seconds since the unit was last reset that there 1162 was Loss of Link." 1163 ::= { vdslPerfDataEntry 6 } 1165 vdslPerfESs OBJECT-TYPE 1166 SYNTAX Counter64 1167 UNITS "seconds" 1168 MAX-ACCESS read-only 1169 STATUS current 1170 DESCRIPTION 1171 "Count of Errored Seconds since the unit was last reset. 1172 An Errored Second is a one-second interval containing one 1173 or more crc anomalies, or one or more los or lof defects." 1174 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1175 ::= { vdslPerfDataEntry 7 } 1177 vdslPerfSESs OBJECT-TYPE 1178 SYNTAX Counter64 1179 UNITS "seconds" 1180 MAX-ACCESS read-only 1181 STATUS current 1182 DESCRIPTION 1183 "Count of Severely Errored Seconds since the unit was last 1184 reset." 1185 ::= { vdslPerfDataEntry 8 } 1187 vdslPerfUASs OBJECT-TYPE 1188 SYNTAX Counter64 1189 UNITS "seconds" 1190 MAX-ACCESS read-only 1191 STATUS current 1192 DESCRIPTION 1193 "Count of Unavailable Seconds since the unit was last 1194 reset." 1195 ::= { vdslPerfDataEntry 9 } 1197 vdslPerfInits OBJECT-TYPE 1198 SYNTAX Counter64 1199 MAX-ACCESS read-only 1200 STATUS current 1201 DESCRIPTION 1202 "Count of the line initialization attempts since the unit 1203 was last reset. This count includes both successful and 1204 failed attempts." 1205 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1206 ::= { vdslPerfDataEntry 10 } 1208 vdslPerfCurr15MinTimeElapsed OBJECT-TYPE 1209 SYNTAX HCPerfTimeElapsed 1210 UNITS "seconds" 1211 MAX-ACCESS read-only 1212 STATUS current 1213 DESCRIPTION 1214 "Total elapsed seconds in this interval." 1215 ::= { vdslPerfDataEntry 11 } 1217 vdslPerfCurr15MinLofs OBJECT-TYPE 1218 SYNTAX HCPerfCurrentCount 1219 UNITS "seconds" 1220 MAX-ACCESS read-only 1221 STATUS current 1222 DESCRIPTION 1223 "Count of seconds during this interval that there 1224 was Loss of Framing." 1225 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1226 ::= { vdslPerfDataEntry 12 } 1228 vdslPerfCurr15MinLoss OBJECT-TYPE 1229 SYNTAX HCPerfCurrentCount 1230 UNITS "seconds" 1231 MAX-ACCESS read-only 1232 STATUS current 1233 DESCRIPTION 1234 "Count of seconds during this interval that there 1235 was Loss of Signal." 1236 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1237 ::= { vdslPerfDataEntry 13 } 1239 vdslPerfCurr15MinLprs OBJECT-TYPE 1240 SYNTAX HCPerfCurrentCount 1241 UNITS "seconds" 1242 MAX-ACCESS read-only 1243 STATUS current 1244 DESCRIPTION 1245 "Count of seconds during this interval that there 1246 was Loss of Power." 1247 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1248 ::= { vdslPerfDataEntry 14 } 1250 vdslPerfCurr15MinLols OBJECT-TYPE 1251 SYNTAX HCPerfCurrentCount 1252 UNITS "seconds" 1253 MAX-ACCESS read-only 1254 STATUS current 1255 DESCRIPTION 1256 "Count of seconds during this interval that there 1257 was Loss of Link." 1258 ::= { vdslPerfDataEntry 15 } 1260 vdslPerfCurr15MinESs OBJECT-TYPE 1261 SYNTAX HCPerfCurrentCount 1262 UNITS "seconds" 1263 MAX-ACCESS read-only 1264 STATUS current 1265 DESCRIPTION 1266 "Count of Errored Seconds during this interval. An Errored 1267 Second is a one-second interval containing one or more crc 1268 anomalies, or one or more los or lof defects." 1269 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1270 ::= { vdslPerfDataEntry 16 } 1272 vdslPerfCurr15MinSESs OBJECT-TYPE 1273 SYNTAX HCPerfCurrentCount 1274 UNITS "seconds" 1275 MAX-ACCESS read-only 1276 STATUS current 1277 DESCRIPTION 1278 "Count of Severely Errored Seconds during this interval." 1279 ::= { vdslPerfDataEntry 17 } 1281 vdslPerfCurr15MinUASs OBJECT-TYPE 1282 SYNTAX HCPerfCurrentCount 1283 UNITS "seconds" 1284 MAX-ACCESS read-only 1285 STATUS current 1286 DESCRIPTION 1287 "Count of Unavailable Seconds during this interval." 1288 ::= { vdslPerfDataEntry 18 } 1290 vdslPerfCurr15MinInits OBJECT-TYPE 1291 SYNTAX HCPerfCurrentCount 1292 MAX-ACCESS read-only 1293 STATUS current 1294 DESCRIPTION 1295 "Count of the line initialization attempts during this 1296 interval. This count includes both successful and 1297 failed attempts." 1298 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1299 ::= { vdslPerfDataEntry 19 } 1301 vdslPerf1DayValidIntervals OBJECT-TYPE 1302 SYNTAX HCPerfValidIntervals 1303 MAX-ACCESS read-only 1304 STATUS current 1305 DESCRIPTION 1306 "Valid Intervals per definition found in 1307 HC-PerfHist-TC-MIB." 1308 ::= { vdslPerfDataEntry 20 } 1310 vdslPerf1DayInvalidIntervals OBJECT-TYPE 1311 SYNTAX HCPerfInvalidIntervals 1312 MAX-ACCESS read-only 1313 STATUS current 1314 DESCRIPTION 1315 "Invalid Intervals per definition found in 1316 HC-PerfHist-TC-MIB." 1317 ::= { vdslPerfDataEntry 21 } 1319 vdslPerfCurr1DayTimeElapsed OBJECT-TYPE 1320 SYNTAX HCPerfTimeElapsed 1321 UNITS "seconds" 1322 MAX-ACCESS read-only 1323 STATUS current 1324 DESCRIPTION 1325 "Number of seconds that have elapsed since the beginning 1326 of the current 1-day interval." 1327 ::= { vdslPerfDataEntry 22 } 1329 vdslPerfCurr1DayLofs OBJECT-TYPE 1330 SYNTAX Counter64 1331 UNITS "seconds" 1332 MAX-ACCESS read-only 1333 STATUS current 1334 DESCRIPTION 1335 "Count of Loss of Framing (LOF) Seconds since the 1336 beginning of the current 1-day interval." 1337 ::= { vdslPerfDataEntry 23 } 1339 vdslPerfCurr1DayLoss OBJECT-TYPE 1340 SYNTAX Counter64 1341 UNITS "seconds" 1342 MAX-ACCESS read-only 1343 STATUS current 1344 DESCRIPTION 1345 "Count of Loss of Signal (LOS) Seconds since the beginning 1346 of the current 1-day interval." 1347 ::= { vdslPerfDataEntry 24 } 1349 vdslPerfCurr1DayLprs OBJECT-TYPE 1350 SYNTAX Counter64 1351 UNITS "seconds" 1352 MAX-ACCESS read-only 1353 STATUS current 1354 DESCRIPTION 1355 "Count of Loss of Power (LPR) Seconds since the beginning 1356 of the current 1-day interval." 1357 ::= { vdslPerfDataEntry 25 } 1359 vdslPerfCurr1DayLols OBJECT-TYPE 1360 SYNTAX Counter64 1361 UNITS "seconds" 1362 MAX-ACCESS read-only 1363 STATUS current 1364 DESCRIPTION 1365 "Count of Loss of Link (LOL) Seconds since the beginning 1366 of the current 1-day interval." 1367 ::= { vdslPerfDataEntry 26 } 1369 vdslPerfCurr1DayESs OBJECT-TYPE 1370 SYNTAX Counter64 1371 UNITS "seconds" 1372 MAX-ACCESS read-only 1373 STATUS current 1374 DESCRIPTION 1375 "Count of Errored Seconds (ES) since the beginning 1376 of the current 1-day interval." 1377 ::= { vdslPerfDataEntry 27 } 1379 vdslPerfCurr1DaySESs OBJECT-TYPE 1380 SYNTAX Counter64 1381 UNITS "seconds" 1382 MAX-ACCESS read-only 1383 STATUS current 1384 DESCRIPTION 1385 "Count of Severely Errored Seconds (SES) since the 1386 beginning of the current 1-day interval." 1387 ::= { vdslPerfDataEntry 28 } 1389 vdslPerfCurr1DayUASs OBJECT-TYPE 1390 SYNTAX Counter64 1391 UNITS "seconds" 1392 MAX-ACCESS read-only 1393 STATUS current 1394 DESCRIPTION 1395 "Count of Unavailable Seconds (UAS) since the beginning 1396 of the current 1-day interval." 1397 ::= { vdslPerfDataEntry 29 } 1399 vdslPerfCurr1DayInits OBJECT-TYPE 1400 SYNTAX Counter64 1401 UNITS "seconds" 1402 MAX-ACCESS read-only 1403 STATUS current 1404 DESCRIPTION 1405 "Count of the line initialization attempts since the 1406 beginning of the current 1-day interval. This count 1407 includes both successful and failed attempts." 1408 ::= { vdslPerfDataEntry 30 } 1410 vdslPerfIntervalTable OBJECT-TYPE 1411 SYNTAX SEQUENCE OF VdslPerfIntervalEntry 1412 MAX-ACCESS not-accessible 1413 STATUS current 1414 DESCRIPTION 1415 "This table provides one row for each Vtu performance 1416 data collection interval. VDSL physical interfaces are 1417 those ifEntries where ifType is equal to vdsl(97)." 1418 ::= { vdslMibObjects 5 } 1420 vdslPerfIntervalEntry OBJECT-TYPE 1421 SYNTAX VdslPerfIntervalEntry 1422 MAX-ACCESS not-accessible 1423 STATUS current 1424 DESCRIPTION 1425 "An entry in the vdslPerfIntervalTable." 1426 INDEX { ifIndex, 1427 vdslPhysSide, 1428 vdslIntervalNumber } 1429 ::= { vdslPerfIntervalTable 1 } 1431 VdslPerfIntervalEntry ::= 1432 SEQUENCE 1433 { 1434 vdslIntervalNumber Unsigned32, 1435 vdslIntervalLofs HCPerfIntervalCount, 1436 vdslIntervalLoss HCPerfIntervalCount, 1437 vdslIntervalLprs HCPerfIntervalCount, 1438 vdslIntervalLols HCPerfIntervalCount, 1439 vdslIntervalESs HCPerfIntervalCount, 1440 vdslIntervalSESs HCPerfIntervalCount, 1441 vdslIntervalUASs HCPerfIntervalCount, 1442 vdslIntervalInits HCPerfIntervalCount 1443 } 1445 vdslIntervalNumber OBJECT-TYPE 1446 SYNTAX Unsigned32 (1..96) 1447 MAX-ACCESS not-accessible 1448 STATUS current 1449 DESCRIPTION 1450 "Performance Data Interval number 1 is the the most 1451 recent previous interval; interval 96 is 24 hours ago. 1452 Intervals 2..96 are optional." 1453 ::= { vdslPerfIntervalEntry 1 } 1455 vdslIntervalLofs OBJECT-TYPE 1456 SYNTAX HCPerfIntervalCount 1457 UNITS "seconds" 1458 MAX-ACCESS read-only 1459 STATUS current 1460 DESCRIPTION 1461 "Count of seconds in the interval when there was Loss 1462 of Framing." 1463 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1464 ::= { vdslPerfIntervalEntry 2 } 1466 vdslIntervalLoss OBJECT-TYPE 1467 SYNTAX HCPerfIntervalCount 1468 UNITS "seconds" 1469 MAX-ACCESS read-only 1470 STATUS current 1471 DESCRIPTION 1472 "Count of seconds in the interval when there was Loss 1473 of Signal." 1474 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1475 ::= { vdslPerfIntervalEntry 3 } 1477 vdslIntervalLprs OBJECT-TYPE 1478 SYNTAX HCPerfIntervalCount 1479 UNITS "seconds" 1480 MAX-ACCESS read-only 1481 STATUS current 1482 DESCRIPTION 1483 "Count of seconds in the interval when there was Loss 1484 of Power." 1485 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1486 ::= { vdslPerfIntervalEntry 4 } 1488 vdslIntervalLols OBJECT-TYPE 1489 SYNTAX HCPerfIntervalCount 1490 UNITS "seconds" 1491 MAX-ACCESS read-only 1492 STATUS current 1493 DESCRIPTION 1494 "Count of seconds in the interval when there was Loss 1495 of Link." 1496 ::= { vdslPerfIntervalEntry 5 } 1498 vdslIntervalESs OBJECT-TYPE 1499 SYNTAX HCPerfIntervalCount 1500 UNITS "seconds" 1501 MAX-ACCESS read-only 1502 STATUS current 1503 DESCRIPTION 1504 "Count of Errored Seconds (ES) in the interval. An Errored 1505 Second is a one-second interval containing one or more crc 1506 anomalies, one or more los or lof defects." 1507 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1508 ::= { vdslPerfIntervalEntry 6 } 1510 vdslIntervalSESs OBJECT-TYPE 1511 SYNTAX HCPerfIntervalCount 1512 UNITS "seconds" 1513 MAX-ACCESS read-only 1514 STATUS current 1515 DESCRIPTION 1516 "Count of Severely Errored Seconds in the interval." 1517 ::= { vdslPerfIntervalEntry 7 } 1519 vdslIntervalUASs OBJECT-TYPE 1520 SYNTAX HCPerfIntervalCount 1521 UNITS "seconds" 1522 MAX-ACCESS read-only 1523 STATUS current 1524 DESCRIPTION 1525 "Count of Unavailable Seconds in the interval." 1526 ::= { vdslPerfIntervalEntry 8 } 1528 vdslIntervalInits OBJECT-TYPE 1529 SYNTAX HCPerfIntervalCount 1530 MAX-ACCESS read-only 1531 STATUS current 1532 DESCRIPTION 1533 "Count of the line initialization attempts during this 1534 interval. This count includes both successful and 1535 failed attempts." 1536 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1537 ::= { vdslPerfIntervalEntry 9 } 1539 vdsl1DayIntervalTable OBJECT-TYPE 1540 SYNTAX SEQUENCE OF Vdsl1DayIntervalEntry 1541 MAX-ACCESS not-accessible 1542 STATUS current 1543 DESCRIPTION 1544 "This table provides one row for each VDSL performance 1545 data collection interval. This table contains live data 1546 from equipment. As such, it is NOT persistent." 1547 ::= { vdslMibObjects 6 } 1549 vdsl1DayIntervalEntry OBJECT-TYPE 1550 SYNTAX Vdsl1DayIntervalEntry 1551 MAX-ACCESS not-accessible 1552 STATUS current 1553 DESCRIPTION 1554 "An entry in the vdsl1DayIntervalTable." 1555 INDEX { ifIndex, 1556 vdslPhysSide, 1557 vdsl1DayIntervalNumber } 1558 ::= { vdsl1DayIntervalTable 1 } 1560 Vdsl1DayIntervalEntry ::= 1561 SEQUENCE 1562 { 1563 vdsl1DayIntervalNumber Unsigned32, 1564 vdsl1DayIntervalMoniSecs HCPerfTimeElapsed, 1565 vdsl1DayIntervalLofs Counter64, 1566 vdsl1DayIntervalLoss Counter64, 1567 vdsl1DayIntervalLprs Counter64, 1568 vdsl1DayIntervalLols Counter64, 1569 vdsl1DayIntervalESs Counter64, 1570 vdsl1DayIntervalSESs Counter64, 1571 vdsl1DayIntervalUASs Counter64, 1572 vdsl1DayIntervalInits Counter64 1573 } 1575 vdsl1DayIntervalNumber OBJECT-TYPE 1576 SYNTAX Unsigned32 (1..30) 1577 MAX-ACCESS not-accessible 1578 STATUS current 1579 DESCRIPTION 1580 "History Data Interval number. Interval 1 is the the most 1581 recent previous day; interval 30 is 30 days ago. Intervals 1582 2..30 are optional." 1583 ::= { vdsl1DayIntervalEntry 1 } 1585 vdsl1DayIntervalMoniSecs OBJECT-TYPE 1586 SYNTAX HCPerfTimeElapsed 1587 UNITS "seconds" 1588 MAX-ACCESS read-only 1589 STATUS current 1590 DESCRIPTION 1591 "The amount of time in the 1-day interval over which the 1592 performance monitoring information is actually counted. 1593 This value will be the same as the interval duration except 1594 in a situation where performance monitoring data could not 1595 be collected for any reason." 1596 ::= { vdsl1DayIntervalEntry 2 } 1598 vdsl1DayIntervalLofs OBJECT-TYPE 1599 SYNTAX Counter64 1600 UNITS "seconds" 1601 MAX-ACCESS read-only 1602 STATUS current 1603 DESCRIPTION 1604 "Count of Loss of Frame (LOF) Seconds during the 1-day 1605 interval as measured by vdsl1DayIntervalMoniSecs." 1606 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1607 ::= { vdsl1DayIntervalEntry 3 } 1609 vdsl1DayIntervalLoss OBJECT-TYPE 1610 SYNTAX Counter64 1611 UNITS "seconds" 1612 MAX-ACCESS read-only 1613 STATUS current 1614 DESCRIPTION 1615 "Count of Loss of Signal (LOS) Seconds during the 1-day 1616 interval as measured by vdsl1DayIntervalMoniSecs." 1617 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1618 ::= { vdsl1DayIntervalEntry 4 } 1620 vdsl1DayIntervalLprs OBJECT-TYPE 1621 SYNTAX Counter64 1622 UNITS "seconds" 1623 MAX-ACCESS read-only 1624 STATUS current 1625 DESCRIPTION 1626 "Count of Loss of Power (LPR) Seconds during the 1-day 1627 interval as measured by vdsl1DayIntervalMoniSecs." 1628 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1629 ::= { vdsl1DayIntervalEntry 5 } 1631 vdsl1DayIntervalLols OBJECT-TYPE 1632 SYNTAX Counter64 1633 UNITS "seconds" 1634 MAX-ACCESS read-only 1635 STATUS current 1636 DESCRIPTION 1637 "Count of Loss of Link (LOL) Seconds during the 1-day 1638 interval as measured by vdsl1DayIntervalMoniSecs." 1639 ::= { vdsl1DayIntervalEntry 6 } 1641 vdsl1DayIntervalESs OBJECT-TYPE 1642 SYNTAX Counter64 1643 UNITS "seconds" 1644 MAX-ACCESS read-only 1645 STATUS current 1646 DESCRIPTION 1647 "Count of Errored Seconds (ES) during the 1-day 1648 interval as measured by vdsl1DayIntervalMoniSecs." 1649 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1650 ::= { vdsl1DayIntervalEntry 7 } 1652 vdsl1DayIntervalSESs OBJECT-TYPE 1653 SYNTAX Counter64 1654 UNITS "seconds" 1655 MAX-ACCESS read-only 1656 STATUS current 1657 DESCRIPTION 1658 "Count of Severely Errored Seconds (SES) during the 1-day 1659 interval as measured by vdsl1DayIntervalMoniSecs." 1660 ::= { vdsl1DayIntervalEntry 8 } 1662 vdsl1DayIntervalUASs OBJECT-TYPE 1663 SYNTAX Counter64 1664 UNITS "seconds" 1665 MAX-ACCESS read-only 1666 STATUS current 1667 DESCRIPTION 1668 "Count of Unavailable Seconds (UAS) during the 1-day 1669 interval as measured by vdsl1DayIntervalMoniSecs." 1670 ::= { vdsl1DayIntervalEntry 9 } 1672 vdsl1DayIntervalInits OBJECT-TYPE 1673 SYNTAX Counter64 1674 UNITS "seconds" 1675 MAX-ACCESS read-only 1676 STATUS current 1677 DESCRIPTION 1678 "Count of the line initialization attempts during the 1679 1-day interval as measured by vdsl1DayIntervalMoniSecs. 1680 This count includes both successful and failed attempts." 1681 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1682 ::= { vdsl1DayIntervalEntry 10 } 1684 vdslChanPerfDataTable OBJECT-TYPE 1685 SYNTAX SEQUENCE OF VdslChanPerfDataEntry 1686 MAX-ACCESS not-accessible 1687 STATUS current 1688 DESCRIPTION 1689 "This table provides one row for each Vtu channel. 1690 VDSL channel interfaces are those ifEntries where 1691 ifType is equal to interleave(124) or fast(125)." 1692 ::= { vdslMibObjects 7 } 1694 vdslChanPerfDataEntry OBJECT-TYPE 1695 SYNTAX VdslChanPerfDataEntry 1696 MAX-ACCESS not-accessible 1697 STATUS current 1698 DESCRIPTION 1699 "An entry in the vdslChanPerfDataTable." 1700 INDEX { ifIndex, 1701 vdslPhysSide } 1702 ::= { vdslChanPerfDataTable 1 } 1704 VdslChanPerfDataEntry ::= 1705 SEQUENCE 1706 { 1707 vdslChanPerfValidIntervals HCPerfValidIntervals, 1708 vdslChanPerfInvalidIntervals HCPerfInvalidIntervals, 1709 vdslChanCorrectedOctets Counter64, 1710 vdslChanUncorrectableBlks Counter64, 1711 vdslChanPerfCurr15MinTimeElapsed HCPerfTimeElapsed, 1712 vdslChanPerfCurr15MinCorrectedOctets HCPerfCurrentCount, 1713 vdslChanPerfCurr15MinUncorrectableBlks HCPerfCurrentCount, 1714 vdslChanPerf1DayValidIntervals HCPerfValidIntervals, 1715 vdslChanPerf1DayInvalidIntervals HCPerfInvalidIntervals, 1716 vdslChanPerfCurr1DayTimeElapsed HCPerfTimeElapsed, 1717 vdslChanPerfCurr1DayCorrectedOctets HCPerfCurrentCount, 1718 vdslChanPerfCurr1DayUncorrectableBlks HCPerfCurrentCount 1719 } 1721 vdslChanPerfValidIntervals OBJECT-TYPE 1722 SYNTAX HCPerfValidIntervals 1723 MAX-ACCESS read-only 1724 STATUS current 1725 DESCRIPTION 1726 "Valid Intervals per definition found in 1727 HC-PerfHist-TC-MIB." 1728 ::= { vdslChanPerfDataEntry 1 } 1730 vdslChanPerfInvalidIntervals OBJECT-TYPE 1731 SYNTAX HCPerfInvalidIntervals 1732 MAX-ACCESS read-only 1733 STATUS current 1734 DESCRIPTION 1735 "Invalid Intervals per definition found in 1736 HC-PerfHist-TC-MIB." 1737 ::= { vdslChanPerfDataEntry 2 } 1739 vdslChanCorrectedOctets OBJECT-TYPE 1740 SYNTAX Counter64 1741 MAX-ACCESS read-only 1742 STATUS current 1743 DESCRIPTION 1744 "Count of corrected octets since the unit was last reset." 1745 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1746 ::= { vdslChanPerfDataEntry 3 } 1748 vdslChanUncorrectableBlks OBJECT-TYPE 1749 SYNTAX Counter64 1750 MAX-ACCESS read-only 1751 STATUS current 1752 DESCRIPTION 1753 "Count of uncorrectable blocks since the unit was last 1754 reset." 1755 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1756 ::= { vdslChanPerfDataEntry 4 } 1758 vdslChanPerfCurr15MinTimeElapsed OBJECT-TYPE 1759 SYNTAX HCPerfTimeElapsed 1760 UNITS "seconds" 1761 MAX-ACCESS read-only 1762 STATUS current 1763 DESCRIPTION 1764 "Total elapsed seconds in this interval." 1765 ::= { vdslChanPerfDataEntry 5 } 1767 vdslChanPerfCurr15MinCorrectedOctets OBJECT-TYPE 1768 SYNTAX HCPerfCurrentCount 1769 MAX-ACCESS read-only 1770 STATUS current 1771 DESCRIPTION 1772 "Count of corrected octets in this interval." 1773 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1774 ::= { vdslChanPerfDataEntry 6 } 1776 vdslChanPerfCurr15MinUncorrectableBlks OBJECT-TYPE 1777 SYNTAX HCPerfCurrentCount 1778 MAX-ACCESS read-only 1779 STATUS current 1780 DESCRIPTION 1781 "Count of uncorrectable blocks in this interval." 1782 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1783 ::= { vdslChanPerfDataEntry 7 } 1785 vdslChanPerf1DayValidIntervals OBJECT-TYPE 1786 SYNTAX HCPerfValidIntervals 1787 MAX-ACCESS read-only 1788 STATUS current 1789 DESCRIPTION 1790 "Valid Intervals per definition found in 1791 HC-PerfHist-TC-MIB." 1792 ::= { vdslChanPerfDataEntry 8 } 1794 vdslChanPerf1DayInvalidIntervals OBJECT-TYPE 1795 SYNTAX HCPerfInvalidIntervals 1796 MAX-ACCESS read-only 1797 STATUS current 1798 DESCRIPTION 1799 "Invalid Intervals per definition found in 1800 HC-PerfHist-TC-MIB." 1801 ::= { vdslChanPerfDataEntry 9 } 1803 vdslChanPerfCurr1DayTimeElapsed OBJECT-TYPE 1804 SYNTAX HCPerfTimeElapsed 1805 UNITS "seconds" 1806 MAX-ACCESS read-only 1807 STATUS current 1808 DESCRIPTION 1809 "Number of seconds that have elapsed since the beginning 1810 of the current 1-day interval." 1811 ::= { vdslChanPerfDataEntry 10 } 1813 vdslChanPerfCurr1DayCorrectedOctets OBJECT-TYPE 1814 SYNTAX HCPerfCurrentCount 1815 MAX-ACCESS read-only 1816 STATUS current 1817 DESCRIPTION 1818 "Count of corrected octets since the beginning of the 1819 current 1-day interval." 1820 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1821 ::= { vdslChanPerfDataEntry 11 } 1823 vdslChanPerfCurr1DayUncorrectableBlks OBJECT-TYPE 1824 SYNTAX HCPerfCurrentCount 1825 MAX-ACCESS read-only 1826 STATUS current 1827 DESCRIPTION 1828 "Count of uncorrectable blocks since the beginning of the 1829 current 1-day interval." 1830 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1831 ::= { vdslChanPerfDataEntry 12 } 1833 vdslChanIntervalTable OBJECT-TYPE 1834 SYNTAX SEQUENCE OF VdslChanIntervalEntry 1835 MAX-ACCESS not-accessible 1836 STATUS current 1837 DESCRIPTION 1838 "This table provides one row for each Vtu channel data 1839 collection interval. VDSL channel interfaces are those 1840 ifEntries where ifType is equal to interleave(124) or 1841 fast(125)." 1842 ::= { vdslMibObjects 8 } 1844 vdslChanIntervalEntry OBJECT-TYPE 1845 SYNTAX VdslChanIntervalEntry 1846 MAX-ACCESS not-accessible 1847 STATUS current 1848 DESCRIPTION 1849 "An entry in the vdslChanIntervalTable." 1850 INDEX { ifIndex, 1851 vdslPhysSide, 1852 vdslChanIntervalNumber } 1853 ::= { vdslChanIntervalTable 1 } 1855 VdslChanIntervalEntry ::= 1856 SEQUENCE 1857 { 1858 vdslChanIntervalNumber Unsigned32, 1859 vdslChanIntervalCorrectedOctets HCPerfIntervalCount, 1860 vdslChanIntervalUncorrectableBlks HCPerfIntervalCount 1861 } 1863 vdslChanIntervalNumber OBJECT-TYPE 1864 SYNTAX Unsigned32 (0..96) 1865 MAX-ACCESS not-accessible 1866 STATUS current 1867 DESCRIPTION 1868 "Performance Data Interval number 1 is the the most 1869 recent previous interval; interval 96 is 24 hours ago. 1870 Intervals 2..96 are optional." 1871 ::= { vdslChanIntervalEntry 1 } 1873 vdslChanIntervalCorrectedOctets OBJECT-TYPE 1874 SYNTAX HCPerfIntervalCount 1875 MAX-ACCESS read-only 1876 STATUS current 1877 DESCRIPTION 1878 "Count of corrected octets in this interval." 1879 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1880 ::= { vdslChanIntervalEntry 2 } 1882 vdslChanIntervalUncorrectableBlks OBJECT-TYPE 1883 SYNTAX HCPerfIntervalCount 1884 MAX-ACCESS read-only 1885 STATUS current 1886 DESCRIPTION 1887 "Count of uncorrectable blocks in this interval." 1888 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1889 ::= { vdslChanIntervalEntry 3 } 1891 vdslChan1DayIntervalTable OBJECT-TYPE 1892 SYNTAX SEQUENCE OF VdslChan1DayIntervalEntry 1893 MAX-ACCESS not-accessible 1894 STATUS current 1895 DESCRIPTION 1896 "This table provides one row for each VDSL performance 1897 data collection interval. This table contains live data 1898 from equipment. As such, it is NOT persistent." 1899 ::= { vdslMibObjects 9 } 1901 vdslChan1DayIntervalEntry OBJECT-TYPE 1902 SYNTAX VdslChan1DayIntervalEntry 1903 MAX-ACCESS not-accessible 1904 STATUS current 1905 DESCRIPTION 1906 "An entry in the vdslChan1DayIntervalTable." 1907 INDEX { ifIndex, 1908 vdslPhysSide, 1909 vdslChan1DayIntervalNumber } 1910 ::= { vdslChan1DayIntervalTable 1 } 1912 VdslChan1DayIntervalEntry ::= 1913 SEQUENCE 1914 { 1915 vdslChan1DayIntervalNumber Unsigned32, 1916 vdslChan1DayIntervalMoniSecs HCPerfTimeElapsed, 1917 vdslChan1DayIntervalCorrectedOctets HCPerfCurrentCount, 1918 vdslChan1DayIntervalUncorrectableBlks HCPerfCurrentCount 1919 } 1921 vdslChan1DayIntervalNumber OBJECT-TYPE 1922 SYNTAX Unsigned32 (1..30) 1923 MAX-ACCESS not-accessible 1924 STATUS current 1925 DESCRIPTION 1926 "History Data Interval number. Interval 1 is the the most 1927 recent previous day; interval 30 is 30 days ago. Intervals 1928 2..30 are optional." 1929 ::= { vdslChan1DayIntervalEntry 1 } 1931 vdslChan1DayIntervalMoniSecs OBJECT-TYPE 1932 SYNTAX HCPerfTimeElapsed 1933 UNITS "seconds" 1934 MAX-ACCESS read-only 1935 STATUS current 1936 DESCRIPTION 1937 "The amount of time in the 1-day interval over which the 1938 performance monitoring information is actually counted. 1939 This value will be the same as the interval duration except 1940 in a situation where performance monitoring data could not 1941 be collected for any reason." 1942 ::= { vdslChan1DayIntervalEntry 2 } 1944 vdslChan1DayIntervalCorrectedOctets OBJECT-TYPE 1945 SYNTAX HCPerfCurrentCount 1946 MAX-ACCESS read-only 1947 STATUS current 1948 DESCRIPTION 1949 "Count of corrected octets in this interval." 1950 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1951 ::= { vdslChan1DayIntervalEntry 3 } 1953 vdslChan1DayIntervalUncorrectableBlks OBJECT-TYPE 1954 SYNTAX HCPerfCurrentCount 1955 MAX-ACCESS read-only 1956 STATUS current 1957 DESCRIPTION 1958 "Count of uncorrectable blocks in this interval." 1959 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 1960 ::= { vdslChan1DayIntervalEntry 4 } 1962 -- 1963 -- profile tables 1964 -- 1966 vdslLineConfProfileTable OBJECT-TYPE 1967 SYNTAX SEQUENCE OF VdslLineConfProfileEntry 1968 MAX-ACCESS not-accessible 1969 STATUS current 1970 DESCRIPTION 1971 "This table contains information on the VDSL line 1972 configuration. One entry in this table reflects a 1973 profile defined by a manager which can be used to 1974 configure the VDSL line." 1975 ::= { vdslMibObjects 11 } 1977 vdslLineConfProfileEntry OBJECT-TYPE 1978 SYNTAX VdslLineConfProfileEntry 1979 MAX-ACCESS not-accessible 1980 STATUS current 1981 DESCRIPTION 1982 "Each entry consists of a list of parameters that 1983 represents the configuration of a VDSL line. 1985 A default profile with an index of 'DEFVAL', will 1986 always exist and its parameters will be set to vendor 1987 specific values, unless otherwise specified in this 1988 document." 1989 INDEX { vdslLineConfProfileName } 1990 ::= { vdslLineConfProfileTable 1 } 1992 VdslLineConfProfileEntry ::= 1993 SEQUENCE 1994 { 1995 vdslLineConfProfileName SnmpAdminString, 1996 vdslLineConfDownstreamRateMode INTEGER, 1997 vdslLineConfUpstreamRateMode INTEGER, 1998 vdslLineConfDownstreamMaxPwr Unsigned32, 1999 vdslLineConfUpstreamMaxPwr Unsigned32, 2000 vdslLineConfDownstreamMaxSnrMgn Unsigned32, 2001 vdslLineConfDownstreamMinSnrMgn Unsigned32, 2002 vdslLineConfDownstreamTargetSnrMgn Unsigned32, 2003 vdslLineConfUpstreamMaxSnrMgn Unsigned32, 2004 vdslLineConfUpstreamMinSnrMgn Unsigned32, 2005 vdslLineConfUpstreamTargetSnrMgn Unsigned32, 2006 vdslLineConfDownstreamFastMaxDataRate Unsigned32, 2007 vdslLineConfDownstreamFastMinDataRate Unsigned32, 2008 vdslLineConfDownstreamSlowMaxDataRate Unsigned32, 2009 vdslLineConfDownstreamSlowMinDataRate Unsigned32, 2010 vdslLineConfUpstreamFastMaxDataRate Unsigned32, 2011 vdslLineConfUpstreamFastMinDataRate Unsigned32, 2012 vdslLineConfUpstreamSlowMaxDataRate Unsigned32, 2013 vdslLineConfUpstreamSlowMinDataRate Unsigned32, 2014 vdslLineConfDownstreamRateRatio Unsigned32, 2015 vdslLineConfUpstreamRateRatio Unsigned32, 2016 vdslLineConfDownstreamMaxInterDelay Unsigned32, 2017 vdslLineConfUpstreamMaxInterDelay Unsigned32, 2018 vdslLineConfDownstreamPboControl INTEGER, 2019 vdslLineConfUpstreamPboControl INTEGER, 2020 vdslLineConfDownstreamPboLevel Unsigned32, 2021 vdslLineConfUpstreamPboLevel Unsigned32, 2022 vdslLineConfDeploymentScenario INTEGER, 2023 vdslLineConfAdslPresence INTEGER, 2024 vdslLineConfApplicableStandard INTEGER, 2025 vdslLineConfBandPlan INTEGER, 2026 vdslLineConfBandPlanFx Unsigned32, 2027 vdslLineConfBandU0Usage INTEGER, 2028 vdslLineConfUpstreamPsdTemplate INTEGER, 2029 vdslLineConfDownstreamPsdTemplate INTEGER, 2030 vdslLineConfHamBandMask BITS, 2031 vdslLineConfCustomNotch1Start Unsigned32, 2032 vdslLineConfCustomNotch1Stop Unsigned32, 2033 vdslLineConfCustomNotch2Start Unsigned32, 2034 vdslLineConfCustomNotch2Stop Unsigned32, 2035 vdslLineConfProfileRowStatus RowStatus 2036 } 2038 vdslLineConfProfileName OBJECT-TYPE 2039 SYNTAX SnmpAdminString (SIZE (1..32)) 2040 MAX-ACCESS not-accessible 2041 STATUS current 2042 DESCRIPTION 2043 "This object identifies a row in this table. 2045 A default profile with an index of 'DEFVAL', will 2046 always exist and its parameters will be set to vendor 2047 specific values, unless otherwise specified in this 2048 document." 2049 ::= { vdslLineConfProfileEntry 1 } 2051 vdslLineConfDownstreamRateMode OBJECT-TYPE 2052 SYNTAX INTEGER 2053 { 2054 manual(1), 2055 adaptAtInit(2) 2056 } 2057 MAX-ACCESS read-create 2058 STATUS current 2059 DESCRIPTION 2060 "Specifies the rate selection behaviour for the line 2061 in the downstream direction." 2062 ::= { vdslLineConfProfileEntry 2 } 2064 vdslLineConfUpstreamRateMode OBJECT-TYPE 2065 SYNTAX INTEGER 2066 { 2067 manual(1), 2068 adaptAtInit(2) 2069 } 2070 MAX-ACCESS read-create 2071 STATUS current 2072 DESCRIPTION 2073 "Specifies the rate selection behaviour for the line 2074 in the upstream direction." 2075 ::= { vdslLineConfProfileEntry 3 } 2077 vdslLineConfDownstreamMaxPwr OBJECT-TYPE 2078 SYNTAX Unsigned32 (0..58) 2079 UNITS "0.25dBm" 2080 MAX-ACCESS read-create 2081 STATUS current 2082 DESCRIPTION 2083 "Specifies the maximum aggregate downstream power 2084 level in the range 0..14.5dBm." 2085 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 2086 ::= { vdslLineConfProfileEntry 4 } 2088 vdslLineConfUpstreamMaxPwr OBJECT-TYPE 2089 SYNTAX Unsigned32 (0..58) 2090 UNITS "0.25dBm" 2091 MAX-ACCESS read-create 2092 STATUS current 2093 DESCRIPTION 2094 "Specifies the maximum aggregate upstream power 2095 level in the range 0..14.5dBm." 2096 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 2097 ::= { vdslLineConfProfileEntry 5 } 2099 vdslLineConfDownstreamMaxSnrMgn OBJECT-TYPE 2100 SYNTAX Unsigned32 (0..127) 2101 UNITS "0.25dBm" 2102 MAX-ACCESS read-create 2103 STATUS current 2104 DESCRIPTION 2105 "Specifies the maximum downstream Signal/Noise Margin 2106 in units of 0.25 dB, for a range of 0..31.75 dB." 2107 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 2108 ::= { vdslLineConfProfileEntry 6 } 2110 vdslLineConfDownstreamMinSnrMgn OBJECT-TYPE 2111 SYNTAX Unsigned32 (0..127) 2112 UNITS "0.25dBm" 2113 MAX-ACCESS read-create 2114 STATUS current 2115 DESCRIPTION 2116 "Specifies the minimum downstream Signal/Noise Margin 2117 in units of 0.25 dB, for a range of 0..31.75 dB." 2118 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 2119 ::= { vdslLineConfProfileEntry 7 } 2121 vdslLineConfDownstreamTargetSnrMgn OBJECT-TYPE 2122 SYNTAX Unsigned32 (0..127) 2123 UNITS "0.25dBm" 2124 MAX-ACCESS read-create 2125 STATUS current 2126 DESCRIPTION 2127 "Specifies the target downstream Signal/Noise Margin 2128 in units of 0.25 dB, for a range of 0..31.75 dB. 2129 This is the Noise Margin the modems must achieve with a 2130 BER of 10-7 or better to successfully complete 2131 initialization." 2132 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 2133 ::= { vdslLineConfProfileEntry 8 } 2135 vdslLineConfUpstreamMaxSnrMgn OBJECT-TYPE 2136 SYNTAX Unsigned32 (0..127) 2137 UNITS "0.25dBm" 2138 MAX-ACCESS read-create 2139 STATUS current 2140 DESCRIPTION 2141 "Specifies the maximum upstream Signal/Noise Margin 2142 in units of 0.25 dB, for a range of 0..31.75 dB." 2143 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 2144 ::= { vdslLineConfProfileEntry 9 } 2146 vdslLineConfUpstreamMinSnrMgn OBJECT-TYPE 2147 SYNTAX Unsigned32 (0..127) 2148 UNITS "0.25dBm" 2149 MAX-ACCESS read-create 2150 STATUS current 2151 DESCRIPTION 2152 "Specifies the minimum upstream Signal/Noise Margin 2153 in units of 0.25 dB, for a range of 0..31.75 dB." 2154 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 2155 ::= { vdslLineConfProfileEntry 10 } 2157 vdslLineConfUpstreamTargetSnrMgn OBJECT-TYPE 2158 SYNTAX Unsigned32 (0..127) 2159 UNITS "0.25dBm" 2160 MAX-ACCESS read-create 2161 STATUS current 2162 DESCRIPTION 2163 "Specifies the target upstream Signal/Noise Margin in 2164 units of 0.25 dB, for a range of 0..31.75 dB. This 2165 is the Noise Margin the modems must achieve with a BER of 2166 10-7 or better to successfully complete initialization." 2167 REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec 2168 ::= { vdslLineConfProfileEntry 11 } 2170 vdslLineConfDownstreamFastMaxDataRate OBJECT-TYPE 2171 SYNTAX Unsigned32 2172 UNITS "kbps" 2173 MAX-ACCESS read-create 2174 STATUS current 2175 DESCRIPTION 2176 "Specifies the maximum downstream fast channel 2177 data rate in steps of 1024 bits/second." 2178 ::= { vdslLineConfProfileEntry 12 } 2180 vdslLineConfDownstreamFastMinDataRate OBJECT-TYPE 2181 SYNTAX Unsigned32 2182 UNITS "kbps" 2183 MAX-ACCESS read-create 2184 STATUS current 2185 DESCRIPTION 2186 "Specifies the minimum downstream fast channel 2187 data rate in steps of 1024 bits/second." 2188 ::= { vdslLineConfProfileEntry 13 } 2190 vdslLineConfDownstreamSlowMaxDataRate OBJECT-TYPE 2191 SYNTAX Unsigned32 2192 UNITS "kbps" 2193 MAX-ACCESS read-create 2194 STATUS current 2195 DESCRIPTION 2196 "Specifies the maximum downstream slow channel 2197 data rate in steps of 1024 bits/second." 2198 ::= { vdslLineConfProfileEntry 14 } 2200 vdslLineConfDownstreamSlowMinDataRate OBJECT-TYPE 2201 SYNTAX Unsigned32 2202 UNITS "kbps" 2203 MAX-ACCESS read-create 2204 STATUS current 2205 DESCRIPTION 2206 "Specifies the minimum downstream slow channel 2207 data rate in steps of 1024 bits/second." 2208 ::= { vdslLineConfProfileEntry 15 } 2210 vdslLineConfUpstreamFastMaxDataRate OBJECT-TYPE 2211 SYNTAX Unsigned32 2212 UNITS "kbps" 2213 MAX-ACCESS read-create 2214 STATUS current 2215 DESCRIPTION 2216 "Specifies the maximum upstream fast channel 2217 data rate in steps of 1024 bits/second." 2218 ::= { vdslLineConfProfileEntry 16 } 2220 vdslLineConfUpstreamFastMinDataRate OBJECT-TYPE 2221 SYNTAX Unsigned32 2222 UNITS "kbps" 2223 MAX-ACCESS read-create 2224 STATUS current 2225 DESCRIPTION 2226 "Specifies the minimum upstream fast channel 2227 data rate in steps of 1024 bits/second." 2229 ::= { vdslLineConfProfileEntry 17 } 2231 vdslLineConfUpstreamSlowMaxDataRate OBJECT-TYPE 2232 SYNTAX Unsigned32 2233 UNITS "kbps" 2234 MAX-ACCESS read-create 2235 STATUS current 2236 DESCRIPTION 2237 "Specifies the maximum upstream slow channel 2238 data rate in steps of 1024 bits/second." 2239 ::= { vdslLineConfProfileEntry 18 } 2241 vdslLineConfUpstreamSlowMinDataRate OBJECT-TYPE 2242 SYNTAX Unsigned32 2243 UNITS "kbps" 2244 MAX-ACCESS read-create 2245 STATUS current 2246 DESCRIPTION 2247 "Specifies the minimum upstream slow channel 2248 data rate in steps of 1024 bits/second." 2249 ::= { vdslLineConfProfileEntry 19 } 2251 vdslLineConfDownstreamRateRatio OBJECT-TYPE 2252 SYNTAX Unsigned32 (0..100) 2253 UNITS "percent" 2254 MAX-ACCESS read-create 2255 STATUS current 2256 DESCRIPTION 2257 "For dynamic rate adaptation at startup, the allocation 2258 of data rate in excess of the minimum data rate for each 2259 channel is controlled by the object. This object specifies 2260 the ratio of the allocation of the excess data rate between 2261 the fast and the slow channels. This allocation represents 2262 downstream Fast Channel Allocation / Slow Channel 2263 Allocation." 2264 ::= { vdslLineConfProfileEntry 20 } 2266 vdslLineConfUpstreamRateRatio OBJECT-TYPE 2267 SYNTAX Unsigned32 (0..100) 2268 UNITS "percent" 2269 MAX-ACCESS read-create 2270 STATUS current 2271 DESCRIPTION 2272 "For dynamic rate adaptation at startup, the allocation 2273 of data rate in excess of the minimum data rate for each 2274 channel is controlled by the object. This object specifies 2275 the ratio of the allocation of the excess data rate between 2276 the fast and the slow channels. This allocation represents 2277 upstream Fast Channel Allocation / Slow Channel Allocation." 2278 ::= { vdslLineConfProfileEntry 21 } 2280 vdslLineConfDownstreamMaxInterDelay OBJECT-TYPE 2281 SYNTAX Unsigned32 (0..255) 2282 UNITS "ms" 2283 MAX-ACCESS read-create 2284 STATUS current 2285 DESCRIPTION 2286 "Specifies the maximum interleave delay for the 2287 downstream slow channel." 2288 ::= { vdslLineConfProfileEntry 22 } 2290 vdslLineConfUpstreamMaxInterDelay OBJECT-TYPE 2291 SYNTAX Unsigned32 (0..255) 2292 UNITS "ms" 2293 MAX-ACCESS read-create 2294 STATUS current 2295 DESCRIPTION 2296 "Specifies the maximum interleave delay for the 2297 upstream slow channel." 2298 ::= { vdslLineConfProfileEntry 23 } 2300 vdslLineConfDownstreamPboControl OBJECT-TYPE 2301 SYNTAX INTEGER 2302 { 2303 disabled(1), 2304 auto(2), 2305 manual(3) 2306 } 2307 MAX-ACCESS read-create 2308 STATUS current 2309 DESCRIPTION 2310 "Downstream power backoff (PBO) control for this 2311 line. For modems which do not support downstream 2312 PBO control, this object MUST be fixed at disabled(1)." 2313 ::= { vdslLineConfProfileEntry 24 } 2315 vdslLineConfUpstreamPboControl OBJECT-TYPE 2316 SYNTAX INTEGER 2317 { 2318 disabled(1), 2319 auto(2), 2320 manual(3) 2321 } 2322 MAX-ACCESS read-create 2323 STATUS current 2324 DESCRIPTION 2325 "Upstream power backoff (PBO) control for this 2326 line. For modems which do not support upstream 2327 PBO control, this object MUST be fixed at disabled(1)." 2328 ::= { vdslLineConfProfileEntry 25 } 2330 vdslLineConfDownstreamPboLevel OBJECT-TYPE 2331 SYNTAX Unsigned32 (0..160) 2332 UNITS "0.25dB" 2333 MAX-ACCESS read-create 2334 STATUS current 2335 DESCRIPTION 2336 "Specifies the downstream backoff level to be used 2337 when vdslLineConfDownstreamPboControl = manual(3)." 2338 ::= { vdslLineConfProfileEntry 26 } 2340 vdslLineConfUpstreamPboLevel OBJECT-TYPE 2341 SYNTAX Unsigned32 (0..160) 2342 UNITS "0.25dB" 2343 MAX-ACCESS read-create 2344 STATUS current 2345 DESCRIPTION 2346 "Specifies the upstream backoff level to be used 2347 when vdslLineConfUpstreamPboControl = manual(3)." 2348 ::= { vdslLineConfProfileEntry 27 } 2350 vdslLineConfDeploymentScenario OBJECT-TYPE 2351 SYNTAX INTEGER 2352 { 2353 fttCab(1), 2354 fttEx(2), 2355 other(3) 2356 } 2357 MAX-ACCESS read-create 2358 STATUS current 2359 DESCRIPTION 2360 "The VDSL line deployment scenario. When using 2361 fttCab(1), the VTU-C is located in a street cabinet. 2362 When using fttEx(2), the VTU-C is located at the 2363 central office." 2364 ::= { vdslLineConfProfileEntry 28 } 2366 vdslLineConfAdslPresence OBJECT-TYPE 2367 SYNTAX INTEGER 2368 { 2369 none(1), 2370 adslOverPots(2), 2371 adslOverISDN(3) 2372 } 2373 MAX-ACCESS read-create 2374 STATUS current 2375 DESCRIPTION 2376 "Indicates presence of ADSL service in the associated 2377 cable bundle/binder." 2378 ::= { vdslLineConfProfileEntry 29 } 2380 vdslLineConfApplicableStandard OBJECT-TYPE 2381 SYNTAX INTEGER 2382 { 2383 ansi(1), 2384 etsi(2), 2385 itu(3), 2386 other(4) 2387 } 2388 MAX-ACCESS read-create 2389 STATUS current 2390 DESCRIPTION 2391 "The VDSL standard to be used for the line." 2392 ::= { vdslLineConfProfileEntry 30 } 2394 vdslLineConfBandPlan OBJECT-TYPE 2395 SYNTAX INTEGER 2396 { 2397 bandPlan997(1), 2398 bandPlan998(2), 2399 bandPlanFx(3), 2400 other(4) 2401 } 2402 MAX-ACCESS read-create 2403 STATUS current 2404 DESCRIPTION 2405 "The VDSL band plan to be used for the line. 2407 bandPlan997(1) is to be used for 2408 ITU-T G.993.1 Bandplan-B 2409 ETSI Bandplan 2410 ANSI Plan 997 2412 bandPlan998(2) is to be used for 2413 ITU-T G.993.1 Bandplan-A 2414 ANSI Plan 998 2416 bandPlanFx(3) is to be used for 2417 ITU-T G.993.1 Bandplan-C. 2419 other(4) is to be used for 2420 non-standard bandplans. 2422 If this object is set to bandPlanFx(3), then 2423 the object vdslLineConfBandPlanFx MUST also be 2424 set." 2425 ::= { vdslLineConfProfileEntry 31 } 2427 vdslLineConfBandPlanFx OBJECT-TYPE 2428 SYNTAX Unsigned32 (3750..12000) 2429 UNITS "kHz" 2430 MAX-ACCESS read-create 2431 STATUS current 2432 DESCRIPTION 2433 "The frequency limit between bands D2 and U2 when 2434 vdslLineConfBandPlan is set to bandPlanFx(3)." 2435 ::= { vdslLineConfProfileEntry 32 } 2437 vdslLineConfBandU0Usage OBJECT-TYPE 2438 SYNTAX INTEGER 2439 { 2440 unused(1), 2441 upstream(2), 2442 downstream(3) 2443 } 2444 MAX-ACCESS read-create 2445 STATUS current 2446 DESCRIPTION 2447 "Defines the VDSL link use of the frequency range 2448 [25kHz - 138kHz] (U0)." 2449 ::= { vdslLineConfProfileEntry 33 } 2451 vdslLineConfUpstreamPsdTemplate OBJECT-TYPE 2452 SYNTAX INTEGER 2453 { 2454 templateMask1(1), 2455 templateMask2(2) 2456 } 2457 MAX-ACCESS read-create 2458 STATUS current 2459 DESCRIPTION 2460 "The upstream PSD template to be used for the line." 2461 ::= { vdslLineConfProfileEntry 34 } 2463 vdslLineConfDownstreamPsdTemplate OBJECT-TYPE 2464 SYNTAX INTEGER 2465 { 2466 templateMask1(1), 2467 templateMask2(2) 2468 } 2469 MAX-ACCESS read-create 2470 STATUS current 2471 DESCRIPTION 2472 "The downstream PSD template to be used for the line." 2473 ::= { vdslLineConfProfileEntry 35 } 2475 vdslLineConfHamBandMask OBJECT-TYPE 2476 SYNTAX BITS 2477 { 2478 customNotch1(0), -- custom (region-specific) notch 2479 customNotch2(1), -- custom (region-specific) notch 2480 amateurBand30m(2), -- amateur radio band notch 2481 amateurBand40m(3), -- amateur radio band notch 2482 amateurBand80m(4), -- amateur radio band notch 2483 amateurBand160m(5) -- amateur radio band notch 2484 } 2485 MAX-ACCESS read-create 2486 STATUS current 2487 DESCRIPTION 2488 "The transmit power spectral density mask code. 2490 Amateur radio band notching is defined in the VDSL 2491 spectrum as follows: 2493 Band Start Frequency Stop Frequecy 2494 ---- ------------------ -------------------------------- 2495 30m 1810 kHz 2000 kHz 2496 40m 3500 kHz 3800 kHz (ETSI); 4000 kHz (ANSI) 2497 80m 7000 kHz 7100 kHz (ETSI); 7300 kHz (ANSI) 2498 160m 10100 kHz 10150 kHz 2500 Notching for each standard band can be enabled or disabled 2501 via the bit mask. 2503 Two custom notches may be specified. If either of these 2504 are enabled via the bit mask, then the following objects 2505 MUST be specified: 2507 If customNotch1 is enabled, then both 2508 vdslLineConfCustomNotch1Start 2509 vdslLineConfCustomNotch1Stop 2510 MUST be specified. 2512 If customNotch2 is enabled, then both 2513 vdslLineConfCustomNotch2Start 2514 vdslLineConfCustomNotch2Stop 2515 MUST be specified." 2516 ::= { vdslLineConfProfileEntry 36 } 2518 vdslLineConfCustomNotch1Start OBJECT-TYPE 2519 SYNTAX Unsigned32 2520 UNITS "kHz" 2521 MAX-ACCESS read-create 2522 STATUS current 2523 DESCRIPTION 2524 "Specifies the start frequency of amateur radio notch 1." 2525 ::= { vdslLineConfProfileEntry 37 } 2527 vdslLineConfCustomNotch1Stop OBJECT-TYPE 2528 SYNTAX Unsigned32 2529 UNITS "kHz" 2530 MAX-ACCESS read-create 2531 STATUS current 2532 DESCRIPTION 2533 "Specifies the stop frequency of amateur radio notch 1." 2534 ::= { vdslLineConfProfileEntry 38 } 2536 vdslLineConfCustomNotch2Start OBJECT-TYPE 2537 SYNTAX Unsigned32 2538 UNITS "kHz" 2539 MAX-ACCESS read-create 2540 STATUS current 2541 DESCRIPTION 2542 "Specifies the start frequency of amateur radio notch 2." 2543 ::= { vdslLineConfProfileEntry 39 } 2545 vdslLineConfCustomNotch2Stop OBJECT-TYPE 2546 SYNTAX Unsigned32 2547 UNITS "kHz" 2548 MAX-ACCESS read-create 2549 STATUS current 2550 DESCRIPTION 2551 "Specifies the stop frequency of amateur radio notch 2." 2552 ::= { vdslLineConfProfileEntry 40 } 2554 vdslLineConfProfileRowStatus OBJECT-TYPE 2555 SYNTAX RowStatus 2556 MAX-ACCESS read-create 2557 STATUS current 2558 DESCRIPTION 2559 "This object is used to create a new row or modify or 2560 delete an existing row in this table. 2562 A profile activated by setting this object to `active'. 2563 When `active' is set, the system will validate the profile. 2565 Before a profile can be deleted or taken out of 2566 service, (by setting this object to `destroy' or 2567 `outOfService') it must be first unreferenced 2568 from all associated lines." 2569 ::= { vdslLineConfProfileEntry 41 } 2571 -- 2572 -- Alarm configuration profile table 2573 -- 2575 vdslLineAlarmConfProfileTable OBJECT-TYPE 2576 SYNTAX SEQUENCE OF VdslLineAlarmConfProfileEntry 2577 MAX-ACCESS not-accessible 2578 STATUS current 2579 DESCRIPTION 2580 "This table contains information on the VDSL line alarm 2581 configuration. One entry in this table reflects a profile 2582 defined by a manager which can be used to configure the 2583 VDSL line alarm thresholds." 2584 ::= { vdslMibObjects 20 } 2586 vdslLineAlarmConfProfileEntry OBJECT-TYPE 2587 SYNTAX VdslLineAlarmConfProfileEntry 2588 MAX-ACCESS not-accessible 2589 STATUS current 2590 DESCRIPTION 2591 "Each entry consists of a list of parameters that 2592 represents the configuration of a VDSL line alarm 2593 profile. 2595 A default profile with an index of 'DEFVAL', will 2596 always exist and its parameters will be set to vendor 2597 specific values, unless otherwise specified in this 2598 document." 2599 INDEX { vdslLineAlarmConfProfileName } 2600 ::= { vdslLineAlarmConfProfileTable 1 } 2602 VdslLineAlarmConfProfileEntry ::= 2603 SEQUENCE 2604 { 2605 vdslLineAlarmConfProfileName SnmpAdminString, 2606 vdslThresh15MinLofs HCPerfIntervalThreshold, 2607 vdslThresh15MinLoss HCPerfIntervalThreshold, 2608 vdslThresh15MinLprs HCPerfIntervalThreshold, 2609 vdslThresh15MinLols HCPerfIntervalThreshold, 2610 vdslThresh15MinESs HCPerfIntervalThreshold, 2611 vdslThresh15MinSESs HCPerfIntervalThreshold, 2612 vdslThresh15MinUASs HCPerfIntervalThreshold, 2613 vdslInitFailureNotificationEnable TruthValue, 2614 vdslLineAlarmConfProfileRowStatus RowStatus 2615 } 2617 vdslLineAlarmConfProfileName OBJECT-TYPE 2618 SYNTAX SnmpAdminString (SIZE (1..32)) 2619 MAX-ACCESS not-accessible 2620 STATUS current 2621 DESCRIPTION 2622 "The name for this profile as specified by a user." 2623 ::= { vdslLineAlarmConfProfileEntry 1 } 2625 vdslThresh15MinLofs OBJECT-TYPE 2626 SYNTAX HCPerfIntervalThreshold 2627 UNITS "seconds" 2628 MAX-ACCESS read-create 2629 STATUS current 2630 DESCRIPTION 2631 "This object configures the threshold for the number of 2632 loss of frame seconds (lofs) within any given 15-minute 2633 performance data collection interval. If the value of 2634 loss of frame seconds in a particular 15-minute collection 2635 interval reaches/exceeds this value, a 2636 vdslPerfLofsThreshNotification notification will be 2637 generated. No more than one notification will be sent 2638 per interval." 2639 ::= { vdslLineAlarmConfProfileEntry 2 } 2641 vdslThresh15MinLoss OBJECT-TYPE 2642 SYNTAX HCPerfIntervalThreshold 2643 UNITS "seconds" 2644 MAX-ACCESS read-create 2645 STATUS current 2646 DESCRIPTION 2647 "This object configures the threshold for the number of 2648 loss of signal seconds (loss) within any given 15-minute 2649 performance data collection interval. If the value of 2650 loss of signal seconds in a particular 15-minute collection 2651 interval reaches/exceeds this value, a 2652 vdslPerfLossThreshNotification notification will be 2653 generated. One notification will be sent per interval 2654 per endpoint." 2655 ::= { vdslLineAlarmConfProfileEntry 3 } 2657 vdslThresh15MinLprs OBJECT-TYPE 2658 SYNTAX HCPerfIntervalThreshold 2659 UNITS "seconds" 2660 MAX-ACCESS read-create 2661 STATUS current 2662 DESCRIPTION 2663 "This object configures the threshold for the number of 2664 loss of power seconds (lprs) within any given 15-minute 2665 performance data collection interval. If the value of 2666 loss of power seconds in a particular 15-minute collection 2667 interval reaches/exceeds this value, a 2668 vdslPerfLprsThreshNotification notification will be 2669 generated. No more than one notification will be sent 2670 per interval." 2671 ::= { vdslLineAlarmConfProfileEntry 4 } 2673 vdslThresh15MinLols OBJECT-TYPE 2674 SYNTAX HCPerfIntervalThreshold 2675 UNITS "seconds" 2676 MAX-ACCESS read-create 2677 STATUS current 2678 DESCRIPTION 2679 "This object configures the threshold for the number of 2680 loss of link seconds (lols) within any given 15-minute 2681 performance data collection interval. If the value of 2682 loss of power seconds in a particular 15-minute collection 2683 interval reaches/exceeds this value, a 2684 vdslPerfLolsThreshNotification notification will be 2685 generated. No more than one notification will be sent 2686 per interval." 2687 ::= { vdslLineAlarmConfProfileEntry 5 } 2689 vdslThresh15MinESs OBJECT-TYPE 2690 SYNTAX HCPerfIntervalThreshold 2691 UNITS "seconds" 2692 MAX-ACCESS read-create 2693 STATUS current 2694 DESCRIPTION 2695 "This object configures the threshold for the number of 2696 errored seconds (ESs) within any given 15-minute 2697 performance data collection interval. If the value of 2698 errored seconds in a particular 15-minute collection 2699 interval reaches/exceeds this value, a 2700 vdslPerfESsThreshNotification notification will be 2701 generated. No more than one notification will be sent 2702 per interval." 2703 ::= { vdslLineAlarmConfProfileEntry 6 } 2705 vdslThresh15MinSESs OBJECT-TYPE 2706 SYNTAX HCPerfIntervalThreshold 2707 UNITS "seconds" 2708 MAX-ACCESS read-create 2709 STATUS current 2710 DESCRIPTION 2711 "This object configures the threshold for the number of 2712 severely errored seconds (SESs) within any given 15-minute 2713 performance data collection interval. If the value of 2714 severely errored seconds in a particular 15-minute 2715 collection interval reaches/exceeds this value, a 2716 vdslPerfSESsThreshNotification notification will be 2717 generated. No more than one notification will be sent 2718 per interval." 2719 ::= { vdslLineAlarmConfProfileEntry 7 } 2721 vdslThresh15MinUASs OBJECT-TYPE 2722 SYNTAX HCPerfIntervalThreshold 2723 UNITS "seconds" 2724 MAX-ACCESS read-create 2725 STATUS current 2726 DESCRIPTION 2727 "This object configures the threshold for the number of 2728 unavailable seconds (UASs) within any given 15-minute 2729 performance data collection interval. If the value of 2730 unavailable seconds in a particular 15-minute collection 2731 interval reaches/exceeds this value, a 2732 vdslPerfUASsThreshNotification notification will be 2733 generated. No more than one notification will be sent 2734 per interval." 2735 ::= { vdslLineAlarmConfProfileEntry 8 } 2737 vdslInitFailureNotificationEnable OBJECT-TYPE 2738 SYNTAX TruthValue 2739 MAX-ACCESS read-create 2740 STATUS current 2741 DESCRIPTION 2742 "This object specifies if a vdslInitFailureNotification 2743 notification will be generated if an initialization 2744 failure occurs." 2745 ::= { vdslLineAlarmConfProfileEntry 9 } 2747 vdslLineAlarmConfProfileRowStatus OBJECT-TYPE 2748 SYNTAX RowStatus 2749 MAX-ACCESS read-create 2750 STATUS current 2751 DESCRIPTION 2752 "This object is used to create a new row or modify or 2753 delete an existing row in this table. 2755 A profile activated by setting this object to `active'. 2756 When `active' is set, the system will validate the profile. 2758 Before a profile can be deleted or taken out of service, 2759 (by setting this object to `destroy' or `outOfService') it 2760 must be first unreferenced from all associated lines." 2761 ::= { vdslLineAlarmConfProfileEntry 10 } 2763 -- Notification definitions 2765 vdslNotifications OBJECT IDENTIFIER ::= { vdslLineMib 0 } 2767 vdslPerfLofsThreshNotification NOTIFICATION-TYPE 2768 OBJECTS { 2769 vdslPerfCurr15MinLofs, 2770 vdslThresh15MinLofs 2771 } 2772 STATUS current 2773 DESCRIPTION 2774 "Loss of Framing 15-minute interval threshold reached." 2775 ::= { vdslNotifications 1 } 2777 vdslPerfLossThreshNotification NOTIFICATION-TYPE 2778 OBJECTS { 2779 vdslPerfCurr15MinLoss, 2780 vdslThresh15MinLoss 2781 } 2782 STATUS current 2783 DESCRIPTION 2784 "Loss of Signal 15-minute interval threshold reached." 2785 ::= { vdslNotifications 2 } 2787 vdslPerfLprsThreshNotification NOTIFICATION-TYPE 2788 OBJECTS { 2789 vdslPerfCurr15MinLprs, 2790 vdslThresh15MinLprs 2791 } 2792 STATUS current 2793 DESCRIPTION 2794 "Loss of Power 15-minute interval threshold reached." 2795 ::= { vdslNotifications 3 } 2797 vdslPerfLolsThreshNotification NOTIFICATION-TYPE 2798 OBJECTS { 2799 vdslPerfCurr15MinLols, 2800 vdslThresh15MinLols 2801 } 2802 STATUS current 2803 DESCRIPTION 2804 "Loss of Link 15-minute interval threshold reached." 2805 ::= { vdslNotifications 4 } 2807 vdslPerfESsThreshNotification NOTIFICATION-TYPE 2808 OBJECTS { 2809 vdslPerfCurr15MinESs, 2810 vdslThresh15MinESs 2811 } 2812 STATUS current 2813 DESCRIPTION 2814 "Errored Seconds 15-minute interval threshold reached." 2815 ::= { vdslNotifications 5 } 2817 vdslPerfSESsThreshNotification NOTIFICATION-TYPE 2818 OBJECTS { 2819 vdslPerfCurr15MinSESs, 2820 vdslThresh15MinSESs 2821 } 2822 STATUS current 2823 DESCRIPTION 2824 "Severely Errored Seconds 15-minute interval threshold 2825 reached." 2826 ::= { vdslNotifications 6 } 2828 vdslPerfUASsThreshNotification NOTIFICATION-TYPE 2829 OBJECTS { 2830 vdslPerfCurr15MinUASs, 2831 vdslThresh15MinUASs 2832 } 2833 STATUS current 2834 DESCRIPTION 2835 "Unavailable Seconds 15-minute interval threshold reached." 2836 ::= { vdslNotifications 7 } 2838 vdslDownMaxSnrMgnExceededNotification NOTIFICATION-TYPE 2839 OBJECTS { 2840 vdslCurrSnrMgn, 2841 vdslLineConfDownstreamMaxSnrMgn 2842 } 2843 STATUS current 2844 DESCRIPTION 2845 "The downstream Signal to Noise Margin exceeded 2846 vdslLineConfDownstreamMaxSnrMgn. The object 2847 vdslCurrSnrMgn will contain the Signal to Noise 2848 margin as measured by the VTU-R." 2849 ::= { vdslNotifications 8 } 2851 vdslDownMinSnrMgnExceededNotification NOTIFICATION-TYPE 2852 OBJECTS { 2853 vdslCurrSnrMgn, 2854 vdslLineConfDownstreamMinSnrMgn 2855 } 2856 STATUS current 2857 DESCRIPTION 2858 "The downstream Signal to Noise Margin fell below 2859 vdslLineConfDownstreamMinSnrMgn. The object 2860 vdslCurrSnrMgn will contain the Signal to Noise 2861 margin as measured by the VTU-R." 2862 ::= { vdslNotifications 9 } 2864 vdslUpMaxSnrMgnExceededNotification NOTIFICATION-TYPE 2865 OBJECTS { 2866 vdslCurrSnrMgn, 2867 vdslLineConfUpstreamMaxSnrMgn 2868 } 2869 STATUS current 2870 DESCRIPTION 2871 "The upstream Signal to Noise Margin exceeded 2872 vdslLineConfDownstreamMaxSnrMgn. The object 2873 vdslCurrSnrMgn will contain the Signal to Noise 2874 margin as measured by the VTU-C." 2875 ::= { vdslNotifications 10 } 2877 vdslUpMinSnrMgnExceededNotification NOTIFICATION-TYPE 2878 OBJECTS { 2879 vdslCurrSnrMgn, 2880 vdslLineConfUpstreamMinSnrMgn 2881 } 2882 STATUS current 2883 DESCRIPTION 2884 "The upstream Signal to Noise Margin fell below 2885 vdslLineConfDownstreamMinSnrMgn. The object 2886 vdslCurrSnrMgn will contain the Signal to Noise 2887 margin as measured by the VTU-C." 2888 ::= { vdslNotifications 11 } 2890 vdslInitFailureNotification NOTIFICATION-TYPE 2891 OBJECTS { 2892 vdslCurrStatus 2893 } 2894 STATUS current 2895 DESCRIPTION 2896 "Vtu initialization failed. See vdslCurrStatus for 2897 potential reasons." 2898 ::= { vdslNotifications 12 } 2900 -- conformance information 2902 vdslConformance OBJECT IDENTIFIER ::= { vdslLineMib 3 } 2903 vdslGroups OBJECT IDENTIFIER ::= { vdslConformance 1 } 2904 vdslCompliances OBJECT IDENTIFIER ::= { vdslConformance 2 } 2905 vdslLineMibCompliance MODULE-COMPLIANCE 2906 STATUS current 2907 DESCRIPTION 2908 "The compliance statement for SNMP entities which 2909 manage VDSL interfaces." 2911 MODULE -- this module 2912 MANDATORY-GROUPS 2913 { 2914 vdslGroup 2915 } 2917 ::= { vdslCompliances 1 } 2919 -- units of conformance 2921 vdslGroup OBJECT-GROUP 2922 OBJECTS 2923 { 2924 vdslLineCoding, 2925 vdslLineType, 2926 vdslLineConfProfile, 2927 vdslLineAlarmConfProfile, 2928 vdslInvSerialNumber, 2929 vdslInvVendorID, 2930 vdslInvVersionNumber, 2931 vdslCurrSnrMgn, 2932 vdslCurrAtn, 2933 vdslCurrStatus, 2934 vdslCurrOutputPwr, 2935 vdslCurrAttainableRate, 2936 vdslCurrLineRate, 2937 vdslChanInterleaveDelay, 2938 vdslChanCrcBlockLength, 2939 vdslChanCurrTxRate, 2940 vdslChanOverhead, 2941 vdslChanBurstProtection, 2942 vdslPerfValidIntervals, 2943 vdslPerfInvalidIntervals, 2944 vdslPerfLofs, 2945 vdslPerfLoss, 2946 vdslPerfLprs, 2947 vdslPerfLols, 2948 vdslPerfESs, 2949 vdslPerfSESs, 2950 vdslPerfUASs, 2951 vdslPerfInits, 2952 vdslPerfCurr15MinTimeElapsed, 2953 vdslPerfCurr15MinLofs, 2954 vdslPerfCurr15MinLoss, 2955 vdslPerfCurr15MinLprs, 2956 vdslPerfCurr15MinLols, 2957 vdslPerfCurr15MinESs, 2958 vdslPerfCurr15MinSESs, 2959 vdslPerfCurr15MinUASs, 2960 vdslPerfCurr15MinInits, 2961 vdslPerf1DayValidIntervals, 2962 vdslPerf1DayInvalidIntervals, 2963 vdslPerfCurr1DayTimeElapsed, 2964 vdslPerfCurr1DayLofs, 2965 vdslPerfCurr1DayLoss, 2966 vdslPerfCurr1DayLprs, 2967 vdslPerfCurr1DayLols, 2968 vdslPerfCurr1DayESs, 2969 vdslPerfCurr1DaySESs, 2970 vdslPerfCurr1DayUASs, 2971 vdslPerfCurr1DayInits, 2972 vdslIntervalLofs, 2973 vdslIntervalLoss, 2974 vdslIntervalLprs, 2975 vdslIntervalLols, 2976 vdslIntervalESs, 2977 vdslIntervalSESs, 2978 vdslIntervalUASs, 2979 vdslIntervalInits, 2980 vdsl1DayIntervalMoniSecs, 2981 vdsl1DayIntervalLofs, 2982 vdsl1DayIntervalLoss, 2983 vdsl1DayIntervalLprs, 2984 vdsl1DayIntervalLols, 2985 vdsl1DayIntervalESs, 2986 vdsl1DayIntervalSESs, 2987 vdsl1DayIntervalUASs, 2988 vdsl1DayIntervalInits, 2989 vdslChanPerfValidIntervals, 2990 vdslChanPerfInvalidIntervals, 2991 vdslChanCorrectedOctets, 2992 vdslChanUncorrectableBlks, 2993 vdslChanPerfCurr15MinTimeElapsed, 2994 vdslChanPerfCurr15MinCorrectedOctets, 2995 vdslChanPerfCurr15MinUncorrectableBlks, 2996 vdslChanPerf1DayValidIntervals, 2997 vdslChanPerf1DayInvalidIntervals, 2998 vdslChanPerfCurr1DayTimeElapsed, 2999 vdslChanPerfCurr1DayCorrectedOctets, 3000 vdslChanPerfCurr1DayUncorrectableBlks, 3001 vdslChanIntervalCorrectedOctets, 3002 vdslChanIntervalUncorrectableBlks, 3003 vdslChan1DayIntervalMoniSecs, 3004 vdslChan1DayIntervalCorrectedOctets, 3005 vdslChan1DayIntervalUncorrectableBlks, 3006 vdslLineConfDownstreamRateMode, 3007 vdslLineConfUpstreamRateMode, 3008 vdslLineConfDownstreamMaxPwr, 3009 vdslLineConfUpstreamMaxPwr, 3010 vdslLineConfDownstreamMaxSnrMgn, 3011 vdslLineConfDownstreamMinSnrMgn, 3012 vdslLineConfDownstreamTargetSnrMgn, 3013 vdslLineConfUpstreamMaxSnrMgn, 3014 vdslLineConfUpstreamMinSnrMgn, 3015 vdslLineConfUpstreamTargetSnrMgn, 3016 vdslLineConfDownstreamFastMaxDataRate, 3017 vdslLineConfDownstreamFastMinDataRate, 3018 vdslLineConfDownstreamSlowMaxDataRate, 3019 vdslLineConfDownstreamSlowMinDataRate, 3020 vdslLineConfUpstreamFastMaxDataRate, 3021 vdslLineConfUpstreamFastMinDataRate, 3022 vdslLineConfUpstreamSlowMaxDataRate, 3023 vdslLineConfUpstreamSlowMinDataRate, 3024 vdslLineConfDownstreamRateRatio, 3025 vdslLineConfUpstreamRateRatio, 3026 vdslLineConfDownstreamMaxInterDelay, 3027 vdslLineConfUpstreamMaxInterDelay, 3028 vdslLineConfDownstreamPboControl, 3029 vdslLineConfUpstreamPboControl, 3030 vdslLineConfDownstreamPboLevel, 3031 vdslLineConfUpstreamPboLevel, 3032 vdslLineConfDeploymentScenario, 3033 vdslLineConfAdslPresence, 3034 vdslLineConfApplicableStandard, 3035 vdslLineConfBandPlan, 3036 vdslLineConfBandPlanFx, 3037 vdslLineConfBandU0Usage, 3038 vdslLineConfUpstreamPsdTemplate, 3039 vdslLineConfDownstreamPsdTemplate, 3040 vdslLineConfHamBandMask, 3041 vdslLineConfCustomNotch1Start, 3042 vdslLineConfCustomNotch1Stop, 3043 vdslLineConfCustomNotch2Start, 3044 vdslLineConfCustomNotch2Stop, 3045 vdslLineConfProfileRowStatus, 3046 vdslThresh15MinLofs, 3047 vdslThresh15MinLoss, 3048 vdslThresh15MinLprs, 3049 vdslThresh15MinLols, 3050 vdslThresh15MinESs, 3051 vdslThresh15MinSESs, 3052 vdslThresh15MinUASs, 3053 vdslInitFailureNotificationEnable, 3054 vdslLineAlarmConfProfileRowStatus 3055 } 3056 STATUS current 3057 DESCRIPTION 3058 "A collection of objects providing information about 3059 a VDSL Line." 3061 ::= { vdslGroups 1 } 3063 vdslNotificationGroup NOTIFICATION-GROUP 3064 NOTIFICATIONS 3065 { 3066 vdslPerfLofsThreshNotification, 3067 vdslPerfLossThreshNotification, 3068 vdslPerfLprsThreshNotification, 3069 vdslPerfLolsThreshNotification, 3070 vdslPerfESsThreshNotification, 3071 vdslPerfSESsThreshNotification, 3072 vdslPerfUASsThreshNotification, 3073 vdslDownMaxSnrMgnExceededNotification, 3074 vdslDownMinSnrMgnExceededNotification, 3075 vdslUpMaxSnrMgnExceededNotification, 3076 vdslUpMinSnrMgnExceededNotification, 3077 vdslInitFailureNotification 3078 } 3079 STATUS current 3080 DESCRIPTION 3081 "This group supports notifications of significant 3082 conditions associated with VDSL Lines." 3083 ::= { vdslGroups 2 } 3085 END 3087 Normative References 3089 [ETSI2701] ETSI TS 101 270-1 V1.2.1 "Transmission and Multiplexing 3090 (TM); Access transmission systems on metallic access 3091 cables; Very high speed Digital Subscriber Line (VDSL); 3092 Part 1: Functional requirements", October 1999. 3094 [ETSI2702] ETSI TS 101 270-2 V1.1.1 "Transmission and Multiplexing 3095 (TM); Access transmission systems on metallic access 3096 cables; Very high speed Digital Subscriber Line (VDSL); 3097 Part 1: Transceiver specification", February 2001. 3099 [ITU9931] ITU-T G.993.1 "Very-high-speed digital subscriber line 3100 foundation", November 2001. 3102 [ITU9971] ITU-T G.997.1 "Physical layer management for Digital 3103 Subscriber Line (DSL) Transcievers", July 1999. 3105 [RFC1901] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 3106 "Introduction to Community-based SNMPv2", RFC 1901, 3107 January 1996. 3109 [RFC1905] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 3110 "Protocol Operations for Version 2 of the Simple Network 3111 Management Protocol (SNMPv2)", RFC 1905, January 1996. 3113 [RFC1906] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 3114 "Transport Mappings for Version 2 of the Simple Network 3115 Management Protocol (SNMPv2)", RFC 1906, January 1996. 3117 [RFC2119] Bradner, S., "Key Words for use in RFCs to Indicate 3118 Requirement Levels", RFC 2119, March 1997. 3120 [RFC2493] Tesink, K., "Textual Conventions for MIB Modules Using 3121 Performance History Based on 15 Minute Intervals", RFC 3122 2493, January 1999. 3124 [RFC2571] Harrington, D., Presuhn, R. and B. Wijnen, "An 3125 Architecture for Describing SNMP Management Frameworks", 3126 RFC 2571, April 1999. 3128 [RFC2572] Case, J., Harrington D., Presuhn, R. and B. Wijnen, 3129 "Message Processing and Dispatching for the Simple Network 3130 Management Protocol (SNMP)", RFC 2572, April 1999. 3132 [RFC2574] Blumenthal, U. and B. Wijnen, "User-based Security Model 3133 (USM) for version 3 of the Simple Network Management 3134 Protocol (SNMPv3)", RFC 2574, April 1999. 3136 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 3137 Rose, M. and S. Waldbusser, "Structure of Management 3138 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 3139 1999. 3141 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 3142 Rose, M. and S. Waldbusser, "Textual Conventions for 3143 SMIv2", STD 58, RFC 2579, April 1999. 3145 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 3146 Rose, M. and S. Waldbusser, "Conformance Statements for 3147 SMIv2", STD 58, RFC 2580, April 1999. 3149 [RFC2662] Bathrick, G. and F. Ly, "Definitions of Managed Objects 3150 for the ADSL Lines", RFC 2662, August 1999. 3152 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 3153 MIB", RFC 2863, June 2000. 3155 [T1E1311] ANSI T1E1.4/2001-311, "Very-high-bit-rate Digital 3156 Subscriber Line (VDSL) Metallic Interface, Part 1: 3157 Functional Requirements and Common Specification", 3158 February 2001. 3160 [T1E1011] ANSI T1E1.4/2001-011R3, "VDSL Metallic Interface, Part 2: 3161 Technical Specification for a Single-Carrier Modulation 3162 (SCM) Transceiver", November 2001. 3164 [T1E1013] ANSI T1E1.4/2001-013R4, "VDSL Metallic Interface, Part 3: 3166 Technical Specification for a Multi-Carrier Modulation 3167 (MCM) Transceiver", November 2000. 3169 Informative References 3171 [RFC1155] Rose, M. and K. McCloghrie, "Structure and Identification 3172 of Management Information for TCP/IP-based Internets", STD 3173 16, RFC 1155, May 1990. 3175 [RFC1157] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple 3176 Network Management Protocol", STD 15, RFC 1157, May 1990. 3178 [RFC1212] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 3179 16, RFC 1212, March 1991. 3181 [RFC1215] Rose, M., "A Convention for Defining Traps for use with 3182 the SNMP", RFC 1215, March 1991. 3184 [RFC2570] Case, J., Mundy, R., Partain, D. and B. Stewart, 3185 "Introduction to Version 3 of the Internet-standard 3186 Network Management Framework", RFC 2570, April 1999. 3188 [RFC2573] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 Applications", 3189 RFC 2573, April 1999. 3191 [RFC2575] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based 3192 Access Control Model (VACM) for the Simple Network 3193 Management Protocol (SNMP)", RFC 2575, April 1999. 3195 Security Considerations 3197 There are a number of management objects defined in this MIB that 3198 have a MAX-ACCESS clause of read-write and/or read-create. Such 3199 objects may be considered sensitive or vulnerable in some network 3200 environments. The support for SET operations in a non-secure 3201 environment without proper protection can have a negative effect on 3202 network operations. 3204 VDSL layer connectivity from the Vtur will permit the subscriber 3205 to manipulate both the VDSL link directly and the VDSL embedded 3206 operations channel (EOC) for their own loop. For example, unchecked 3207 or unfiltered fluctuations initiated by the subscriber could generate 3208 sufficient notifications to potentially overwhelm either the 3209 management interface to the network or the element manager. 3211 For this reason, there are a number of managed objects in this MIB 3212 that may contain sensitive information. These are: 3214 vdslThresh15MinLofs 3215 vdslThresh15MinLoss 3216 vdslThresh15MinLprs 3217 vdslThresh15MinLols 3218 vdslThresh15MinESs 3219 vdslThresh15MinSESs 3220 vdslThresh15MinUASs 3222 It is thus important to control even GET access to these objects and 3223 possibly to even encrypt the values of these objects when sending 3224 them over the network via SNMP. Not all versions of SNMP provide 3225 features for such a secure environment. 3227 Further, notifications generated by agents implementing this MIB 3228 will contain the above threshold information. 3230 SNMPv1 by itself is not a secure environment. Even if the network 3231 itself is secure (for example by using IPSec), even then, there is no 3232 control as to who on the secure network is allowed to access and 3233 GET/SET (read/change/create/delete) the objects in this MIB. 3235 It is recommended that the implementers consider the security 3236 features as provided by the SNMPv3 framework. Specifically, the use 3237 of the User-based Security Model RFC 2574 [12] and the View- 3238 based Access Control Model RFC 2575 [15] is recommended. 3240 It is then a customer/user responsibility to ensure that the SNMP 3241 entity giving access to an instance of this MIB, is properly 3242 configured to give access to the objects only to those principals 3243 (users) that have legitimate rights to indeed GET or SET 3244 (change/create/delete) them. 3246 IANA Considerations 3248 The VDSL-LINE-MIB MIB module requires the allocation of a single 3249 object identifier for its MODULE-IDENTITY. IANA should allocate 3250 this object identifier in the transmission subtree. 3252 Acknowledgments 3254 Greg Bathrick (Nokia) 3256 Umberto Bonollo (NEC) 3258 Andrew Cheers (NEC) 3260 David Horton (CiTR) 3262 Travis Levin (Paradyne) 3264 Moti Morgenstern (Inovia) 3266 Randy Presuhn (BMC) 3268 Bert Wijnen (Lucent) 3270 Intellectual Property Notice 3272 The IETF takes no position regarding the validity or scope of any 3273 intellectual property or other rights that might be claimed to 3274 pertain to the implementation or use of the technology described in 3275 this document or the extent to which any license under such rights 3276 might or might not be available; neither does it represent that it 3277 has made any effort to identify any such rights. Information on the 3278 IETF's procedures with respect to rights in standards-track and 3279 standards-related documentation can be found in BCP-11. Copies of 3280 claims of rights made available for publication and any assurances of 3281 licenses to be made available, or the result of an attempt made to 3282 obtain a general license or permission for the use of such 3283 proprietary rights by implementors or users of this specification can 3284 be obtained from the IETF Secretariat. 3286 The IETF invites any interested party to bring to its attention any 3287 copyrights, patents or patent applications, or other proprietary 3288 rights which may cover technology that may be required to practice 3289 this standard. Please address the information to the IETF Executive 3290 Director. 3292 Authors' Addresses 3294 Bob Ray 3295 PESA Switching Systems, Inc. 3296 330-A Wynn Drive 3297 Huntsville, AL 35805 USA 3299 Phone: +1 256 726 9200 ext. 142 3300 Fax: +1 256 726 9271 3301 EMail: rray@pesa.com 3303 Rajesh Abbi 3304 Alcatel USA 3305 2912 Wake Forest Road 3306 Raleigh, NC 27609-7860 USA 3308 Phone: +1 919 850 6194 3309 EMail: Rajesh.Abbi@alcatel.com 3311 Full Copyright Statement 3313 Copyright (C) The Internet Society (2003). All Rights Reserved. 3315 This document and translations of it may be copied and furnished to 3316 others, and derivative works that comment on or otherwise explain it 3317 or assist in its implementation may be prepared, copied, published 3318 and distributed, in whole or in part, without restriction of any 3319 kind, provided that the above copyright notice and this paragraph are 3320 included on all such copies and derivative works. However, this 3321 document itself may not be modified in any way, such as by removing 3322 the copyright notice or references to the Internet Society or other 3323 Internet organizations, except as needed for the purpose of 3324 developing Internet standards in which case the procedures for 3325 copyrights defined in the Internet Standards process must be 3326 followed, or as required to translate it into languages other than 3327 English. 3329 The limited permissions granted above are perpetual and will not be 3330 revoked by the Internet Society or its successors or assigns. 3331 This document and the information contained herein is provided on an 3332 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 3333 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 3334 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 3335 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 3336 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.