idnits 2.17.1 draft-ietf-adslmib-hdsl2-09.txt: ** The Abstract section seems to be numbered 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 expiration date. The document expiration date should appear on the first and last page. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 52 longer pages, the longest (page 1) being 60 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There is 1 instance of too long lines in the document, the longest one being 1 character in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 841 has weird spacing: '... object will ...' == Line 2014 has weird spacing: '...aseDown wor...' -- 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 2001) is 8411 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: '25' is mentioned on line 1415, but not defined == Missing Reference: '26' is mentioned on line 1472, but not defined == Missing Reference: '27' is mentioned on line 1529, but not defined == Missing Reference: '28' is mentioned on line 1586, but not defined == Missing Reference: '29' is mentioned on line 1642, but not defined == Missing Reference: '30' is mentioned on line 1699, but not defined == Missing Reference: '31' is mentioned on line 1755, but not defined == Missing Reference: '32' is mentioned on line 1811, but not defined == Missing Reference: '33' is mentioned on line 1868, but not defined == Missing Reference: '34' is mentioned on line 1925, but not defined == Missing Reference: '35' is mentioned on line 1982, but not defined == Missing Reference: '36' is mentioned on line 2039, but not defined == Missing Reference: '37' is mentioned on line 2096, but not defined == Missing Reference: '38' is mentioned on line 2153, but not defined == Missing Reference: '39' is mentioned on line 2210, but not defined == Missing Reference: '40' is mentioned on line 2267, but not defined == Missing Reference: '41' is mentioned on line 2324, but not defined == Missing Reference: '42' is mentioned on line 2381, but not defined == Missing Reference: '43' is mentioned on line 2437, but not defined == Missing Reference: '44' is mentioned on line 2493, but not defined == Missing Reference: '45' is mentioned on line 2550, but not defined == Missing Reference: '46' is mentioned on line 2607, but not defined == Missing Reference: '47' is mentioned on line 2664, but not defined == Missing Reference: '48' is mentioned on line 2721, but not defined == Missing Reference: '49' is mentioned on line 2777, but not defined == Missing Reference: '50' is mentioned on line 2833, but not defined == Missing Reference: '51' is mentioned on line 2890, but not defined == Missing Reference: '52' is mentioned on line 2929, but not defined ** Obsolete normative reference: RFC 2571 (ref. '1') (Obsoleted by RFC 3411) -- Possible downref: Non-RFC (?) normative reference: ref. '2' ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. '4') ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '8') ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. '9') ** Obsolete normative reference: RFC 1906 (ref. '10') (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2572 (ref. '11') (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (ref. '12') (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (ref. '13') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (ref. '14') (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (ref. '15') (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2570 (ref. '16') (Obsoleted by RFC 3410) -- Possible downref: Non-RFC (?) normative reference: ref. '18' -- Possible downref: Non-RFC (?) normative reference: ref. '19' ** Obsolete normative reference: RFC 2493 (ref. '22') (Obsoleted by RFC 3593) Summary: 18 errors (**), 0 flaws (~~), 33 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 INTERNET-DRAFT B. Ray 2 Verilink Corporation 4 R. Abbi 5 Alcatel 6 April 2001 8 Definitions of Managed Objects for HDSL2 and SHDSL Lines 9 draft-ietf-adslmib-hdsl2-09.txt 11 Status of this Memo 13 This document is an Internet-Draft and is in full conformance with 14 all provisions of Section 10 of RFC 2026. 16 Internet-Drafts are working documents of the Internet Engineering 17 Task Force (IETF), its areas, and its working groups. Note that other 18 groups may also distribute working documents as Internet-Drafts. 20 Internet-Drafts are draft documents valid for a maximum of six months 21 and may be updated, replaced, or obsoleted by other documents at any 22 time. It is inappropriate to use Internet-Drafts as reference 23 material or to cite them other than as "work in progress." 25 The list of current Internet-Drafts can be accessed at 26 http://www.ietf.org/ietf/1id-abstracts.txt 28 The list of Internet-Draft Shadow Directories can be accessed at 29 http://www.ietf.org/shadow.html. 31 To view the entire list of current Internet-Drafts, please check the 32 "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow 33 Directories on ftp.is.co.za (Africa), ftp.nordu.net (Northern 34 Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au (Pacific 35 Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu (US West Coast). 37 Copyright Notice 39 Copyright (C) The Internet Society (2001). All Rights Reserved. 41 Table of Contents 43 1. Abstract .................................................. 2 44 2. The SNMP Network Management Framework ..................... 2 45 3. Introduction .............................................. 3 46 3.1 Relationship of the MIB with Standard MIBs ................ 3 47 4. Conventions used in the MIB ............................... 4 48 4.1 Naming Conventions ........................................ 4 49 4.2 Textual Conventions ....................................... 4 50 4.3 Structure ................................................. 5 51 4.4 Counters, Interval Buckets and Thresholds ................. 8 52 4.5 Profiles .................................................. 8 53 4.6 Notifications ............................................. 9 54 5. Conformance and Compliance ................................ 11 55 6. Definitions ............................................... 11 56 7. Security Considerations ................................... 48 57 8. Acknowledgments ........................................... 49 59 Expires October 2, 2001 Page [1] 60 9. References ................................................ 49 61 10. Intellectual Property Notice .............................. 51 62 11. Authors' Addresses ........................................ 51 63 12. Full Copyright Statement .................................. 52 65 1. Abstract 67 This document defines an experimental portion of the Management 68 Information Base (MIB) module for use with network management protocols 69 in the Internet community. In particular, it describes objects used for 70 managing HDSL2 and SHDSL interfaces. 72 This document specifies a MIB module in a manner that is both compliant 73 to the SNMPv2 SMI, and semantically identical to the peer SNMPv1 74 definitions. 76 2. The SNMP Management Framework 78 The SNMP Management Framework presently consists of five major 79 components: 81 o An overall architecture, described in RFC 2571 [1]. 83 o Mechanisms for describing and naming objects and events for the 84 purpose of management. The first version of this Structure of 85 Management Information (SMI) is called SMIv1 and described in 86 STD 16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4]. 87 The second version, called SMIv2, is described in STD 58, RFC 88 2578 [5], STD 58, RFC 2579 [6] and STD 58, RFC 2580 [7]. 90 o Message protocols for transferring management information. The 91 first version of the SNMP message protocol is called SNMPv1 and 92 described in STD 15, RFC 1157 [8]. A second version of the SNMP 93 message protocol, which is not an Internet standards track 94 protocol, is called SNMPv2c and described in RFC 1901 [9] and 95 RFC 1906 [10]. The third version of the message protocol is 96 called SNMPv3 and described in RFC 1906 [10], RFC 2572 [11] and 97 RFC 2574 [12]. 99 o Protocol operations for accessing management information. The 100 first set of protocol operations and associated PDU formats is 101 described in STD 15, RFC 1157 [8]. A second set of protocol 102 operations and associated PDU formats is described in RFC 1905 103 [13]. 105 o A set of fundamental applications described in RFC 2573 [14] 106 and the view-based access control mechanism described in RFC 107 2575 [15]. 109 A more detailed introduction to the current SNMP Management Framework 110 can be found in RFC 2570 [16]. 112 Managed objects are accessed via a virtual information store, termed 113 the Management Information Base or MIB. Objects in the MIB are 114 defined using the mechanisms defined in the SMI. 116 Expires October 2, 2001 Page [2] 117 This memo specifies a MIB module that is compliant to the SMIv2. A 118 MIB conforming to the SMIv1 can be produced through the appropriate 119 translations. The resulting translated MIB must be semantically 120 equivalent, except where objects or events are omitted because no 121 translation is possible (use of Counter64). Some machine readable 122 information in SMIv2 will be converted into textual descriptions in 123 SMIv1 during the translation process. However, this loss of machine 124 readable information is not considered to change the semantics of the 125 MIB. 127 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 128 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 129 this document are to be interpreted as described in RFC 2119 [17]. 131 3. Introduction 133 This document describes an SNMP MIB for managing HDSL2/SHDSL Lines. 134 These definitions are based upon the specifications for the HDSL2 and 135 SHDSL Embedded Operations Channel (EOC) as defined in ANSI 136 T1E1.4/2000-006 [18] and ITU G.991.2 (ex G.SHDSL) [19]. 138 The MIB will eventually be located in the MIB tree under MIB 2 139 transmission, as discussed in the MIB-2 Integration (RFC 1213 [20] and 140 RFC 2863 [21]) section of this document. Until approved by the IETF, 141 vendors may also choose to support it under the experimental tree. 143 3.1. Relationship of the HDSL2/SHDSL Line MIB with Standard MIBs 145 This section outlines the relationship of this MIB with other MIBs 146 described in RFCs and in various degrees of "standardization". 147 Specifically, MIB-2 as presented in RFC 1213 [20] and RFC 2863 [21] 148 is discussed. 150 3.1.1 General MIB-2 Integration (RFCs 1213 and 2863) 152 The HDSL2/SHDSL Line MIB specifies the detailed attributes of a data 153 interface. As such, it needs to integrate with RFC 2863 [21]. The 154 IANA has assigned the following ifTypes to HDSL2 and SHDSL: 156 IANAifType ::= TEXTUAL-CONVENTION 157 ... 158 SYNTAX INTEGER { 159 ... 160 hdsl2 (168), -- High Bit-Rate DSL, 2nd generation 161 shdsl (169), -- Multirate HDSL2 162 ... 163 } 165 3.1.2 Usage of ifTable 167 The MIB branch identified by this ifType contains tables appropriate 168 for this interface type. Most such tables extend the ifEntry table, 169 and are indexed by ifIndex. 171 Expires October 2, 2001 Page [3] 172 The following attributes are part of the mandatory ifGeneral group in 173 RFC 2863 [21], and are not duplicated in the HDSL2/SHDSL Line MIB. 175 =================================================================== 176 ifIndex Interface index. 178 ifDescr See interfaces MIB [21]. 180 ifType hdsl2(168) or shdsl(169). 182 ifSpeed Set as appropriate. 183 (This is fixed at 1552000 for HDSL2 lines) 185 ifPhysAddress This object should have an octet string 186 with zero length. 188 ifAdminStatus See interfaces MIB [21]. 190 ifOperStatus See interfaces MIB [21]. 192 ifLastChange See interfaces MIB [21]. 194 ifName See interfaces MIB [21]. 196 ifLinkUpDownTrapEnable Default to enabled(1). 198 ifHighSpeed Set as appropriate. 199 (For HDSL2 lines, this is fixed at 2) 201 ifConnectorPresent Set as appropriate. 202 =================================================================== 203 Figure 1: Use of ifTable Objects 205 4. Conventions used in the MIB 207 4.1. Naming Conventions 209 A. xtuC refers to a central site terminal unit; 210 H2TU-C for HDSL2, or STU-C for SHDSL. 211 B. xtuR refers to a remote site terminal unit; 212 H2TU-R for HDSL2, or STU-R for SHDSL. 213 C. xtu refers to a terminal unit; either an xtuC or xtuR. 214 D. xru refer to a regenerator unit; 215 H2RU for HDSL2, or SRU for SHDSL. 216 E. xU refers to any HDSL2/SHDSL unit; either an xtu or xru. 217 F. CRC is cyclic redundancy check. 218 G. ES means errored second. 219 H. LOSW means loss of sync word. 220 I. LOSWS means LOSW seconds. 221 J. SES means severely errored second. 222 K. SNR means signal-to-noise ratio. 223 L. UAS means unavailable second. 225 4.2. Textual Conventions 227 Expires October 2, 2001 Page [4] 228 The following textual conventions are defined to reflect the line 229 topology in the MIB (further discussed is the following section) 230 and to define the behaviour of the statistics to be maintained 231 by an agent. 233 o Hdsl2ShdslUnitId : 235 This attribute uniquely identifies each unit in a HDSL2/SHDSL span. 236 It mirrors the EOC addressing mechanism: 238 xtuC(1) - CO terminal unit 239 xtuR(2) - CPE terminal unit 240 xru1(3) .. xru8(10) - regenerators, numbered from 241 central office side 243 o Hdsl2ShdslUnitSide: 244 This attribute references the two sides of a unit: 246 networkSide(1) - N in figure 2, below 247 customerSide(2) - C in figure 2, below 249 o Hdsl2ShdslWirePair: 250 This attribute references the wire-pairs connecting the units: 252 wirePair1(1) - First pair for HDSL2/SHDSL. 253 wirePair2(2) - Optional second pair for SHDSL only. 255 o Hdsl2ShdslTransmissionModeType: 256 This attribute specifies the regional setting for a SHDSL line. 257 Specified as a BITS construct, the two mode types are: 259 region1 - ITU-T G.991.2 Annex A 260 region2 - ITU-T G.991.2 Annex B 262 o Hdsl2ShdslPerfCurrDayCount: 264 This attribute defines the behaviour of the 1-day (24 hour) 265 gauges found in the MIB. 267 o Hdsl2Shdsl1DayIntervalCount: 269 This attribute defines the behaviour of the 1-day (24 hour) 270 interval counters found in the MIB. 272 o Hdsl2ShdslPerfTimeElapsed: 274 This attribute defines the behaviour of the elapsed time counters 275 found in the MIB. 277 o Hdsl2ShdslPerfIntervalThreshold: 279 This attribute defines the behaviour of the alarm thresholds found 280 in the MIB. 282 4.3. Structure 284 Expires October 2, 2001 Page [5] 285 The MIB is structured into following MIB groups: 287 o Span Configuration Group: 289 This group supports MIB objects for configuring parameters for 290 the HDSL2/SHDSL span. It contains the following table(s): 292 - hdsl2ShdslSpanConfTable 294 o Span Status Group: 296 This group supports MIB objects for retrieving span status 297 information. It contains the following table(s): 299 - hdsl2ShdslSpanStatusTable 301 o Unit Inventory Group: 303 This group supports MIB objects for retrieving unit inventory 304 information about units in HDSL2/SHDSL lines via the EOC. It 305 contains the following table(s): 307 - hdsl2ShdslInventoryTable 309 o Segment Endpoint Configuration Group: 311 This group supports MIB objects for configuring parameters for 312 the HDSL2/SHDSL segment endpoints. It contains the following 313 table(s): 315 - hdsl2ShdslEndpointConfTable 317 o Segment Endpoint Current Status/Performance Group: 319 This group supports MIB objects that provide the current 320 status/performance information relating to segment endpoints. 321 It contains the following table(s): 323 - hdsl2ShdslEndpointCurrTable 325 o Segment Endpoint 15-Minute Interval Status/Performance Group: 327 This group supports MIB objects that provide historic 328 status/performance information relating to segment endpoints 329 in 15-minute intervals. It contains the following table(s): 331 - hdsl2Shdsl15MinIntervalTable 333 o Segment Endpoint 1-Day Interval Status/Performance Group: 335 This group supports MIB objects that provide historic 336 status/performance information relating to segment endpoints 337 in 1-day intervals. It contains the following table(s): 339 Expires October 2, 2001 Page [6] 340 - hdsl2Shdsl1DayIntervalTable 342 o Maintenance Group: 344 This group supports MIB objects for performing maintenance 345 operations such as loopbacks for HDSL2/SHDSL lines. It contains 346 the following table(s): 348 - hdsl2ShdslEndpointMaintTable 349 - hdsl2ShdslUnitMaintTable 351 o Span Configuration Profile Group: 353 This group supports MIB objects for defining configuration profiles 354 for HDSL2/SHDSL Spans. It contains the following table(s): 356 - hdsl2ShdslSpanConfProfileTable 358 o Segment Endpoint Alarm Configuration Profile Group: 360 This group supports MIB objects for defining alarm configuration 361 profiles for HDSL2/SHDSL Segment Endpoints. It contains the 362 following table(s): 364 - hdsl2ShdslEndpointAlarmConfProfileTable 366 o Notifications Group: 368 This group defines Notification messages supported for HDSL2/ 369 SHDSL lines. It defines the following notifications: 371 - hdsl2ShdslLoopAttenCrossing 372 - hdsl2ShdslSNRMarginCrossing 373 - hdsl2ShdslPerfESThresh 374 - hdsl2ShdslPerfSESThresh 375 - hdsl2ShdslPerfCRCanomaliesThresh 376 - hdsl2ShdslPerfLOSWSThresh 377 - hdsl2ShdslPerfUASThresh 378 - hdsl2ShdslSpanInvalidNumRepeaters 379 - hdsl2ShdslLoopbackFailure 380 - hdsl2ShdslpowerBackoff 381 - hdsl2ShdsldeviceFault 382 - hdsl2ShdsldcContinuityFault 383 - hdsl2ShdslconfigInitFailure 384 - hdsl2ShdslprotocolInitFailure 385 - hdsl2ShdslnoNeighborPresent 386 - hdsl2ShdsllocalPowerLoss 388 4.3.1 Line Topology 390 An HDSL2/SHDSL Line consists of a minimum of two units - xtuC (the 391 central termination unit) and an xtuR (the remote termination unit). 392 The line may optionally support up to 8 repeater/regenerator units 393 (xru) as shown in the figure below. 395 Expires October 2, 2001 Page [7] 396 <-- Network Side Customer Side --> 398 || 400 <~~~> <~~~> HDSL2/SHDSL Segments <~~~> 402 +-------+ +-------+ +-------+ +-------+ +-------+ 403 + C=1=N C=1=N C=..1..=N C=1=N + 404 | xtuC | | xru1 | | xru2 | | xru8 | | xtuR | 405 + C=2=N C=2=N C=..2..=N C=2=N + 406 +-------+ +-------+ +-------+ +-------+ +-------+ 408 Key: HDSL2/SHDSL Span 409 <~~~~> HDSL2/SHDSL Segment 410 =1= HDSL2/SHDSL wire-pair-1 411 =2= SHDSL optional wire-pair-2 (Not applicable to HDSL2) 412 C Customer Side Segment Endpoint (modem) 413 N Network Side Segment Endpoint (modem) 415 Figure 2: General topology for an HDSL2/SHDSL Line 417 4.4. Counters, Interval Buckets and Thresholds 419 For SNR Margin, Loop Attenuation, ES, SES, CRC anomalies, LOSW, and 420 UAS, there are event counters, current 15-minute and one (up to 96) 421 15-minute history bucket(s) of "interval-counters", as well as 422 current and one (up to 30) previous 1-day interval-counter(s). Each 423 current 15-minute event bucket has an associated threshold 424 notification. 426 Unlike RFC 2493 [22] and RFC 2662 [23], there is no representation 427 in the MIB for invalid buckets. In those cases where the data for 428 an interval is suspect or known to be invalid, the agent should 429 not report the interval. 431 There is no requirement for an agent to ensure a fixed relationship 432 between the start of a fifteen minute and any wall clock; however 433 some implementations may align the fifteen minute intervals with 434 quarter hours. Likewise, an implementation may choose to align one 435 day intervals with the start of a day. 437 Counters are not reset when an xU is reinitialized, only when the 438 agent is reset or reinitialized (or under specific request outside 439 the scope of this MIB). 441 4.5. Profiles 443 As a managed node can handle a large number of xUs, (e.g., hundreds 444 or perhaps thousands of lines), provisioning every parameter on every 445 xU may become burdensome. Moreover, most lines are provisioned 446 identically; with the same set of parameters. To simplify the 447 provisioning process, this MIB makes use of profiles. A profile is a 448 set of parameters that can be shared by multiple lines using the same 449 configuration. 451 Expires October 2, 2001 Page [8] 452 The following profiles are used in this MIB: 454 o Span Configuration Profiles - Span configuration profiles contain 455 parameters for configuring HDSL2/SHDSL spans. They are defined in 456 the hdsl2ShdslSpanConfProfileTable. Since span configuration 457 parameters are only applicable for SHDSL, the support for span 458 configuration profiles is optional for HDSL2 interfaces. 460 Note that the configuration of the span dictates the behavior for 461 each individual segment end point in the span. If a different 462 configuration is provisioned for any given segment end point within 463 the span, however, the new configuraiton for this segment end point 464 will override the span configuration for this segment end point only. 466 o Segment Endpoint Alarm Configuration Profiles - These profiles 467 contain parameters for configuring alarm thresholds for HDSL2/ 468 SHDSL segment endpoints. These profiles are defined in the 469 hdsl2ShdslEndpointAlarmConfProfileTable. 471 Implementations will enable the manager to dynamically create and 472 delete profiles as needed. The index of each profile is a locally- 473 unique administratively assigned name for the profile having the 474 textual convention `SnmpAdminString' (RFC 2571 [1]). 476 One or more lines may be configured to share parameters of a single 477 profile (e.g., hdsl2ShdslEndpointAlarmConfProfile = `silver') by 478 setting its hdsl2ShdslEndpointAlarmConfProfile objects to the value of 479 this profile. If a change is made to the profile, all lines that refer 480 to it will be reconfigured to the changed parameters. Before a profile 481 can be deleted or taken out of service it must be first unreferenced 482 from all associated lines. 484 Implementations must provide a default profile whose name is `DEFVAL' 485 for each profile type. The values of the associated parameters will be 486 vendor specific unless otherwise indicated in this document. Before a 487 line's profiles have been set, these profiles will be automatically 488 used by setting hdsl2ShdslEndpointAlarmConfProfile and 489 hdsl2ShdslSpanConfProfile to `DEFVAL' where appropriate. 491 Profiles are created, assigned, and deleted dynamically using the 492 profile name and profile row status in each of the four profile tables. 494 Profile changes MUST take effect immediately. These changes MAY result 495 in a restart (hard reset or soft restart) of the units on the line. 497 4.6. Notifications 499 The ability to generate the SNMP notifications coldStart/WarmStart (per 500 [21]) which are per agent (e.g., per DSLAM in such a device), and 501 linkUp/linkDown (per [21]) -- which are per interface (i.e., HDSL2/SHDSL 502 line) is required. 504 A linkDown notification may be generated whenever any of ES, SES, CRC 505 Anomaly, LOSW, or UAS event occurs. The corresponding linkUp 507 Expires October 2, 2001 Page [9] 508 notification MAY be sent when all link failure conditions are cleared. 510 The notifications defined in this MIB are for initialization failure and 511 for the threshold crossings associated with the following events: ES, 512 SES, CRC Anomaly, LOSW, and UAS. Each threshold has its own 513 enable/threshold value. When that value is 0, the notification is 514 disabled. 516 The hdsl2ShdslEndpointCurrStatus is a bitmask representing all 517 outstanding error conditions associated with a particular Segment 518 Endpoint. Note that since status of remote endpoints is obtained via 519 the EOC, this information may be unavailable for units that are 520 unreachable via EOC during a line error condition. Therefore, not all 521 conditions may always be included in its current status. Notifications 522 corresponding to the bit fields in this object are defined. 524 Two alarm conditions, SNR Margin Alarm and Loop Attenuation Alarm, 525 are organized in a manner slightly different from that implied in 526 the EOC specifications. In the MIB, these alarm conditions are 527 tied to the two thresholds hdsl2ShdslEndpointThreshSNRMargin and 528 hdsl2ShdslEndpointThreshLoopAttenuation found in the 529 hdsl2ShdslEndpointAlarmConfProfileTable. In the EOC, the alarm 530 conditions associated with these thresholds are per-unit. In the 531 MIB, these alarm conditions are per-endpoint. For terminal units, 532 this has no impact. For repeaters, this implies an implementation 533 variance where the agent in the terminal unit is responsible for 534 detecting a threshold crossing. As the reporting of a repeater 535 detected alarm condition to the polling terminal unit occurs in 536 the same EOC message as the reporting of the current SNR Margin 537 and Loop Attenuation values, it is anticipated that this will have 538 very little impact on agent implementation. 540 A threshold notification occurs whenever the corresponding current 541 15-minute interval error counter becomes equal to, or exceeds the 542 threshold value. One notification may be sent per interval per 543 interface. Since the current 15-minute counter are reset to 0 every 15 544 minutes, if the condition persists, the notification may recur as 545 often as every 15 minutes. For example, to get a notification 546 whenever a "loss of" event occurs (but at most once every 15 minutes), 547 set the corresponding threshold to 1. The agent will generate a 548 notification when the event originally occurs. 550 Note that the NMS may receive a linkDown notification, as well, if 551 enabled. At the beginning of the next 15 minute interval, the counter is 552 reset. When the first second goes by and the event occurs, the current 553 interval bucket will be 1, which equals the threshold and the 554 notification will be sent again. 556 A hdsl2ShdslSpanInvalidNumRepeaters notification may be generated 557 following completion of the discovery phase if the number of repeaters 558 discovered on the line differs from the number of repeaters specified in 559 hdsl2ShdslSpanConfNumRepeaters. For those conditions where the number 560 of provisioned repeaters is greater than those encountered during span 561 discovery, all table entries associated with the nonexistant repeaters 562 are to be discarded. For those conditions where the number of 564 Expires October 2, 2001 Page [10] 565 provisioned repeaters is less than those encountered during span 566 discovery, additional table entries are to be created using the default 567 span configuration profile. 569 5. Conformance and Compliance 571 For both HDSL2 and SHDSL lines, the following group(s) are mandatory: 573 hdsl2ShdslSpanConfGroup 574 hdsl2ShdslSpanStatusGroup 575 hdsl2ShdslInventoryGroup 576 hdsl2ShdslEndpointConfGroup 577 hdsl2Shdsl15MinIntervalGroup 578 hdsl2Shdsl1DayIntervalGroup 579 hdsl2ShdslMaintenanceGroup 580 hdsl2ShdslEndpointAlarmConfGroup 581 hdsl2ShdslNotificationGroup 583 For HDSL2 lines, the following group(s) are optional: 585 hdsl2ShdslSpanConfProfileGroup 586 hdsl2ShdslSpanShdslStatusGroup 588 6. Definitions 590 HDSL2-SHDSL-LINE-MIB DEFINITIONS ::= BEGIN 592 IMPORTS 593 MODULE-IDENTITY, 594 OBJECT-TYPE, 595 Counter32, 596 Gauge32, 597 NOTIFICATION-TYPE, 598 Integer32, 599 experimental FROM SNMPv2-SMI 600 RowStatus, 601 TEXTUAL-CONVENTION FROM SNMPv2-TC 602 ifIndex FROM IF-MIB 603 PerfCurrentCount, 604 PerfIntervalCount FROM PerfHist-TC-MIB 605 SnmpAdminString FROM SNMP-FRAMEWORK-MIB 606 MODULE-COMPLIANCE, 607 OBJECT-GROUP, 608 NOTIFICATION-GROUP FROM SNMPv2-CONF; 610 hdsl2ShdslMIB MODULE-IDENTITY 611 LAST-UPDATED "200104020000Z" -- April 2, 2001 612 ORGANIZATION "ADSLMIB Working Group" 613 CONTACT-INFO "WG-email: XDSLMIB@LISTSERV.ECIRALEIGH.COM 614 Subscribe: LISTSERV@LISTSERV.ECIRALEIGH.COM 615 In Body: subscribe/signoff XDSLMIB 616 Archive: index XDSLMIB/get 618 Co-chair: Dave Allan 619 Nortel Networks 621 Expires October 2, 2001 Page [11] 622 Postal: 3500 Carling Avenue 623 Nepean ON K2H 8E9 Canada 624 Email: dallan@nortelnetworks.com 625 Phone: +1 613 763 6362 (ESN 393) 627 Co-chair: Mike Sneed 628 ECI Telecom 629 Postal: 1017 Main Campus Drive 630 Raleigh NC 37606 631 Email: Mike.Sneed@go.ecitele.com 632 Phone: +1 919 513 1435 634 Co-editor: Bob Ray 635 Verilink Corporation 636 Postal: 950 Explorer Blvd 637 Huntsville, AL 35806 USA 638 Email: bray@verilink.com 639 Phone: +1 256 327 2380 641 Co-editor: Rajesh Abbi 642 Alcatel USA 643 Postal: 2912 Wake Forest Road 644 Raleigh, NC 27609-7860 USA 645 Email: Rajesh.Abbi@usa.alcatel.com 646 Phone: +1 919 950 6194 647 " 649 DESCRIPTION 650 "This MIB module defines a collection of objects for managing 651 HDSL2/SHDSL lines. An agent may reside at either end of the 652 line, however the MIB is designed to require no management 653 communication between the modems beyond that inherent in the 654 low-level EOC line protocol as defined in ANSI T1E1.4/2000-006 655 (for HDSL2 lines), or in ITU G.991.2 (for SHDSL lines)." 656 REVISION "200104020000Z" -- April 2, 2001 657 DESCRIPTION "Initial version, published as RFC xxxx." 659 ::= { experimental 109 } -- to be assigned by IANA 661 hdsl2ShdslMibObjects OBJECT IDENTIFIER ::= { hdsl2ShdslMIB 1 } 663 -- Textual Conventions used in this MIB 664 -- 666 Hdsl2ShdslPerfCurrDayCount ::= TEXTUAL-CONVENTION 667 STATUS current 668 DESCRIPTION 669 "A gauge associated with interface performance measurements in 670 a current 1-day (24 hour) measurement interval. 672 The value of this gauge starts at zero at the beginning of an 673 interval and is increased when associated events occur, until 674 the end of the 1-day interval. At that time the value of the 675 gauge is stored in the previous 1-day history interval, if 676 available, and the current interval counter is restarted at 678 Expires October 2, 2001 Page [12] 679 zero. 681 In the case where the agent has no valid data available for 682 this interval the corresponding object instance is not 683 available and upon a retrieval request a corresponding error 684 message shall be returned to indicate that this instance does 685 not exist (for example, a noSuchName error for SNMPv1 and a 686 noSuchInstance for SNMPv2 GET operation)." 687 SYNTAX Gauge32 689 Hdsl2Shdsl1DayIntervalCount ::= TEXTUAL-CONVENTION 690 STATUS current 691 DESCRIPTION 692 "A counter associated with interface performance measurements 693 during the most previous 1-day (24 hour) measurement interval. 694 The value of this counter is equal to the value of the current 695 day counter at the end of its most recent interval. 697 In the case where the agent has no valid data available for 698 this interval the corresponding object instance is not 699 available and upon a retrieval request a corresponding error 700 message shall be returned to indicate that this instance does 701 not exist (for example, a noSuchName error for SNMPv1 and a 702 noSuchInstance for SNMPv2 GET operation)." 703 SYNTAX Gauge32 705 Hdsl2ShdslPerfTimeElapsed ::= TEXTUAL-CONVENTION 706 STATUS current 707 DESCRIPTION 708 "The number of seconds that have elapsed since the beginning of 709 the current measurement period. If, for some reason, such as 710 an adjustment in the system's time-of-day clock, the current 711 interval exceeds the maximum value, the agent will return the 712 maximum value." 713 SYNTAX Gauge32 715 Hdsl2ShdslPerfIntervalThreshold ::= TEXTUAL-CONVENTION 716 STATUS current 717 DESCRIPTION 718 "This convention defines a range of values that may be set in 719 a fault threshold alarm control. As the number of seconds in 720 a 15-minute interval numbers at most 900, objects of this type 721 may have a range of 0...900, where the value of 0 disables the 722 alarm." 723 SYNTAX INTEGER(0..900) 725 Hdsl2ShdslUnitId ::= TEXTUAL-CONVENTION 726 STATUS current 727 DESCRIPTION 728 "This is the unique identification for all units in a 729 HDSL2/SHDSL Span. It is based on the EOC unit addressing 730 scheme with reference to the xtuC." 731 SYNTAX INTEGER 732 { 733 xtuC(1), 735 Expires October 2, 2001 Page [13] 736 xtuR(2), 737 xru1(3), 738 xru2(4), 739 xru3(5), 740 xru4(6), 741 xru5(7), 742 xru6(8), 743 xru7(9), 744 xru8(10) 745 } 747 Hdsl2ShdslUnitSide ::= TEXTUAL-CONVENTION 748 STATUS current 749 DESCRIPTION 750 "This is the referenced side of a HDSL2/SHDSL unit - Network 751 or Customer side. The side facing the Network is the Network 752 side, while the side facing the Customer is the Customer side." 753 SYNTAX INTEGER 754 { 755 networkSide(1), 756 customerSide(2) 757 } 759 Hdsl2ShdslWirePair ::= TEXTUAL-CONVENTION 760 STATUS current 761 DESCRIPTION 762 "This is the referenced pair of wires in a HDSL2/SHDSL Segment. 763 HDSL2 only supports a single pair (wirePair1), while SHDSL 764 supports an optional second pair (wirePair2)." 765 SYNTAX INTEGER 766 { 767 wirePair1(1), 768 wirePair2(2) 769 } 771 Hdsl2ShdslTransmissionModeType ::= TEXTUAL-CONVENTION 772 STATUS current 773 DESCRIPTION 774 "Contains the regional setting of the HDSL2/SHDSL span, 775 represented as a bit-map of possible settings. The various 776 bit positions are: 778 Bit Meaning Description 779 1 region 1 Indicates ITU-T G.991.2 Annex A. 780 2 region 2 Indicates ITU-T G.991.2 Annex B." 781 SYNTAX BITS 782 { 783 region1(0), 784 region2(1) 785 } 787 -- Span Configuration Group 788 -- 790 hdsl2ShdslSpanConfTable OBJECT-TYPE 792 Expires October 2, 2001 Page [14] 793 SYNTAX SEQUENCE OF Hdsl2ShdslSpanConfEntry 794 MAX-ACCESS not-accessible 795 STATUS current 796 DESCRIPTION 797 "This table supports overall configuration of HDSL2/SHDSL 798 Spans." 799 ::= { hdsl2ShdslMibObjects 1 } 801 hdsl2ShdslSpanConfEntry OBJECT-TYPE 802 SYNTAX Hdsl2ShdslSpanConfEntry 803 MAX-ACCESS not-accessible 804 STATUS current 805 DESCRIPTION 806 "An entry in the hdsl2ShdslSpanConfTable. Each entry 807 represents the complete Span in a single HDSL2/SHDSL line. 808 It is indexed by the ifIndex of the associated HDSL2/SHDSL 809 line." 810 INDEX { ifIndex } 811 ::= { hdsl2ShdslSpanConfTable 1 } 813 Hdsl2ShdslSpanConfEntry ::= 814 SEQUENCE 815 { 816 hdsl2ShdslSpanConfNumRepeaters INTEGER, 817 hdsl2ShdslSpanConfProfile SnmpAdminString, 818 hdsl2ShdslSpanConfAlarmProfile SnmpAdminString 819 } 821 hdsl2ShdslSpanConfNumRepeaters OBJECT-TYPE 822 SYNTAX INTEGER(0..8) 823 MAX-ACCESS read-write 824 STATUS current 825 DESCRIPTION 826 "This object provisions the number of repeaters/regenerators 827 in this HDSL2/SHDSL Span." 828 ::= { hdsl2ShdslSpanConfEntry 1 } 830 hdsl2ShdslSpanConfProfile OBJECT-TYPE 831 SYNTAX SnmpAdminString (SIZE(1..32)) 832 MAX-ACCESS read-write 833 STATUS current 834 DESCRIPTION 835 "This object is a pointer to a span configuration profile in 836 the hdsl2ShdslSpanConfProfileTable, which applies to this span. 837 The value of this object is the index of the referenced profile 838 in the hdsl2ShdslSpanConfProfileTable. Note that span 839 configuration profiles are only applicable to SHDSL lines. 840 HDSL2 lines will not support this object. By default, this 841 object will have the value 'DEFVAL' (the index of the default 842 profile)." 843 ::= { hdsl2ShdslSpanConfEntry 2 } 845 hdsl2ShdslSpanConfAlarmProfile OBJECT-TYPE 846 SYNTAX SnmpAdminString (SIZE(1..32)) 847 MAX-ACCESS read-write 849 Expires October 2, 2001 Page [15] 850 STATUS current 851 DESCRIPTION 852 "This object is a pointer to an Alarm configuration profile in 853 the hdsl2ShdslEndpointAlarmConfProfileTable. The value of this 854 object is the index of the referenced profile in the 855 hdsl2ShdslEndpointAlarmConfProfileTable. The alarm threshold 856 configuration in the referenced profile will be used by default 857 for all segment endpoints in this span. Individual endpoints 858 may override this profile by explicitly specifying some other 859 profile in the hdsl2ShdslEndpointConfTable. By default, this 860 object will have the value 'DEFVAL' (the index of the default 861 profile)." 862 ::= { hdsl2ShdslSpanConfEntry 3 } 864 -- Span Status Group 865 -- 867 hdsl2ShdslSpanStatusTable OBJECT-TYPE 868 SYNTAX SEQUENCE OF Hdsl2ShdslSpanStatusEntry 869 MAX-ACCESS not-accessible 870 STATUS current 871 DESCRIPTION 872 "This table provides overall status information of 873 HDSL2/SHDSL spans." 874 ::= { hdsl2ShdslMibObjects 2 } 876 hdsl2ShdslSpanStatusEntry OBJECT-TYPE 877 SYNTAX Hdsl2ShdslSpanStatusEntry 878 MAX-ACCESS not-accessible 879 STATUS current 880 DESCRIPTION 881 "An entry in the hdsl2ShdslSpanStatusTable. Each entry 882 represents the complete span in a single HDSL2/SHDSL line. It 883 is indexed by the ifIndex of the associated HDSL2/SHDSL line." 884 INDEX { ifIndex } 885 ::= { hdsl2ShdslSpanStatusTable 1 } 887 Hdsl2ShdslSpanStatusEntry ::= 888 SEQUENCE 889 { 890 hdsl2ShdslStatusNumAvailRepeaters INTEGER, 891 hdsl2ShdslStatusMaxAttainableLineRate Integer32, 892 hdsl2ShdslStatusActualLineRate Integer32, 893 hdsl2ShdslStatusTransmissionModeCurrent 894 Hdsl2ShdslTransmissionModeType 895 } 897 hdsl2ShdslStatusNumAvailRepeaters OBJECT-TYPE 898 SYNTAX INTEGER(0..8) 899 MAX-ACCESS read-only 900 STATUS current 901 DESCRIPTION 902 "Contains the actual number of repeaters/regenerators 903 discovered in this HDSL2/SHDSL span." 904 ::= { hdsl2ShdslSpanStatusEntry 1 } 906 Expires October 2, 2001 Page [16] 907 hdsl2ShdslStatusMaxAttainableLineRate OBJECT-TYPE 908 SYNTAX Integer32 909 UNITS "bps" 910 MAX-ACCESS read-only 911 STATUS current 912 DESCRIPTION 913 "Contains the maximum attainable line rate in this HDSL2/SHDSL 914 span." 915 ::= { hdsl2ShdslSpanStatusEntry 2 } 917 hdsl2ShdslStatusActualLineRate OBJECT-TYPE 918 SYNTAX Integer32 919 UNITS "bps" 920 MAX-ACCESS read-only 921 STATUS current 922 DESCRIPTION 923 "Contains the actual line rate in this HDSL2/SHDSL span." 924 ::= { hdsl2ShdslSpanStatusEntry 3 } 926 hdsl2ShdslStatusTransmissionModeCurrent OBJECT-TYPE 927 SYNTAX Hdsl2ShdslTransmissionModeType 928 MAX-ACCESS read-only 929 STATUS current 930 DESCRIPTION 931 "Contains the current PSD regional setting of the 932 HDSL2/SHDSL span." 933 ::= { hdsl2ShdslSpanStatusEntry 4 } 935 -- Unit Inventory Group 936 -- 938 hdsl2ShdslInventoryTable OBJECT-TYPE 939 SYNTAX SEQUENCE OF Hdsl2ShdslInventoryEntry 940 MAX-ACCESS not-accessible 941 STATUS current 942 DESCRIPTION 943 "This table supports retrieval of unit inventory information 944 available via the EOC from units in a HDSL2/SHDSL line." 945 ::= { hdsl2ShdslMibObjects 3 } 947 hdsl2ShdslInventoryEntry OBJECT-TYPE 948 SYNTAX Hdsl2ShdslInventoryEntry 949 MAX-ACCESS not-accessible 950 STATUS current 951 DESCRIPTION 952 "An entry in the hdsl2ShdslInventoryTable. Each entry 953 represents inventory information for a single unit in a 954 HDSL2/SHDSL line. It is indexed by the ifIndex of the 955 HDSL2/SHDSL line and the Hdsl2ShdslUnitId of the 956 associated unit." 957 INDEX { ifIndex, hdsl2ShdslInvIndex } 958 ::= { hdsl2ShdslInventoryTable 1 } 960 Hdsl2ShdslInventoryEntry ::= 962 Expires October 2, 2001 Page [17] 963 SEQUENCE 964 { 965 hdsl2ShdslInvIndex Hdsl2ShdslUnitId, 966 hdsl2ShdslInvVendorID OCTET STRING, 967 hdsl2ShdslInvVendorModelNumber OCTET STRING, 968 hdsl2ShdslInvVendorSerialNumber OCTET STRING, 969 hdsl2ShdslInvVendorEOCSoftwareVersion Integer32, 970 hdsl2ShdslInvStandardVersion Integer32, 971 hdsl2ShdslInvVendorListNumber OCTET STRING, 972 hdsl2ShdslInvVendorIssueNumber OCTET STRING, 973 hdsl2ShdslInvVendorSoftwareVersion OCTET STRING, 974 hdsl2ShdslInvEquipmentCode OCTET STRING, 975 hdsl2ShdslInvVendorOther OCTET STRING, 976 hdsl2ShdslInvTransmissionModeCapability 977 Hdsl2ShdslTransmissionModeType 978 } 980 hdsl2ShdslInvIndex OBJECT-TYPE 981 SYNTAX Hdsl2ShdslUnitId 982 MAX-ACCESS read-only 983 STATUS current 984 DESCRIPTION 985 "The index into the hdsl2ShdslInventoryTable." 986 ::= { hdsl2ShdslInventoryEntry 1 } 988 hdsl2ShdslInvVendorID OBJECT-TYPE 989 SYNTAX OCTET STRING(SIZE(8)) 990 MAX-ACCESS read-only 991 STATUS current 992 DESCRIPTION 993 "Vendor ID as reported in an Inventory Response message." 994 ::= { hdsl2ShdslInventoryEntry 2 } 996 hdsl2ShdslInvVendorModelNumber OBJECT-TYPE 997 SYNTAX OCTET STRING(SIZE(12)) 998 MAX-ACCESS read-only 999 STATUS current 1000 DESCRIPTION 1001 "Vendor model number as reported in an Inventory Response 1002 message." 1003 ::= { hdsl2ShdslInventoryEntry 3 } 1005 hdsl2ShdslInvVendorSerialNumber OBJECT-TYPE 1006 SYNTAX OCTET STRING(SIZE(12)) 1007 MAX-ACCESS read-only 1008 STATUS current 1009 DESCRIPTION 1010 "Vendor serial number as reported in an Inventory Response 1011 message." 1012 ::= { hdsl2ShdslInventoryEntry 4 } 1014 hdsl2ShdslInvVendorEOCSoftwareVersion OBJECT-TYPE 1015 SYNTAX Integer32 1016 MAX-ACCESS read-only 1017 STATUS current 1019 Expires October 2, 2001 Page [18] 1020 DESCRIPTION 1021 "Vendor EOC version as reported in a Discovery Response 1022 message." 1023 ::= { hdsl2ShdslInventoryEntry 5 } 1025 hdsl2ShdslInvStandardVersion OBJECT-TYPE 1026 SYNTAX Integer32 1027 MAX-ACCESS read-only 1028 STATUS current 1029 DESCRIPTION 1030 "Version of the HDSL2/SHDSL standard implemented, as reported 1031 in an Inventory Response message." 1032 ::= { hdsl2ShdslInventoryEntry 6 } 1034 hdsl2ShdslInvVendorListNumber OBJECT-TYPE 1035 SYNTAX OCTET STRING(SIZE(3)) 1036 MAX-ACCESS read-only 1037 STATUS current 1038 DESCRIPTION 1039 "Vendor list number as reported in an Inventory Response 1040 message." 1041 ::= { hdsl2ShdslInventoryEntry 7 } 1043 hdsl2ShdslInvVendorIssueNumber OBJECT-TYPE 1044 SYNTAX OCTET STRING(SIZE(2)) 1045 MAX-ACCESS read-only 1046 STATUS current 1047 DESCRIPTION 1048 "Vendor issue number as reported in an Inventory Response 1049 message." 1050 ::= { hdsl2ShdslInventoryEntry 8 } 1052 hdsl2ShdslInvVendorSoftwareVersion OBJECT-TYPE 1053 SYNTAX OCTET STRING(SIZE(6)) 1054 MAX-ACCESS read-only 1055 STATUS current 1056 DESCRIPTION 1057 "Vendor software version as reported in an Inventory 1058 Response message." 1059 ::= { hdsl2ShdslInventoryEntry 9 } 1061 hdsl2ShdslInvEquipmentCode OBJECT-TYPE 1062 SYNTAX OCTET STRING(SIZE(10)) 1063 MAX-ACCESS read-only 1064 STATUS current 1065 DESCRIPTION 1066 "Equipment code conforming to ANSI T1.213, Coded Identification 1067 of Equipment Entities." 1068 ::= { hdsl2ShdslInventoryEntry 10 } 1070 hdsl2ShdslInvVendorOther OBJECT-TYPE 1071 SYNTAX OCTET STRING(SIZE(12)) 1072 MAX-ACCESS read-only 1073 STATUS current 1074 DESCRIPTION 1076 Expires October 2, 2001 Page [19] 1077 "Other vendor information as reported in an Inventory 1078 Response message." 1079 ::= { hdsl2ShdslInventoryEntry 11 } 1081 hdsl2ShdslInvTransmissionModeCapability OBJECT-TYPE 1082 SYNTAX Hdsl2ShdslTransmissionModeType 1083 MAX-ACCESS read-only 1084 STATUS current 1085 DESCRIPTION 1086 "Contains the transmission mode capability of the SHDSL unit." 1087 ::= { hdsl2ShdslInventoryEntry 12 } 1089 -- Segment Endpoint Configuration Group 1090 -- 1092 hdsl2ShdslEndpointConfTable OBJECT-TYPE 1093 SYNTAX SEQUENCE OF Hdsl2ShdslEndpointConfEntry 1094 MAX-ACCESS not-accessible 1095 STATUS current 1096 DESCRIPTION 1097 "This table supports configuration parameters for segment 1098 endpoints in a HDSL2/SHDSL line." 1099 ::= { hdsl2ShdslMibObjects 4 } 1101 hdsl2ShdslEndpointConfEntry OBJECT-TYPE 1102 SYNTAX Hdsl2ShdslEndpointConfEntry 1103 MAX-ACCESS not-accessible 1104 STATUS current 1105 DESCRIPTION 1106 "An entry in the hdsl2ShdslEndpointConfTable. Each entry 1107 represents a single segment endpoint in a HDSL2/SHDSL line. 1108 It is indexed by the ifIndex of the HDSL2/SHDSL line, the 1109 UnitId of the associated unit, the side of the unit, and the 1110 wire-pair of the associated modem." 1111 INDEX { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide, 1112 hdsl2ShdslEndpointWirePair} 1113 ::= { hdsl2ShdslEndpointConfTable 1 } 1115 Hdsl2ShdslEndpointConfEntry ::= 1116 SEQUENCE 1117 { 1118 hdsl2ShdslEndpointSide Hdsl2ShdslUnitSide, 1119 hdsl2ShdslEndpointWirePair Hdsl2ShdslWirePair, 1120 hdsl2ShdslEndpointAlarmConfProfile SnmpAdminString 1121 } 1123 hdsl2ShdslEndpointSide OBJECT-TYPE 1124 SYNTAX Hdsl2ShdslUnitSide 1125 MAX-ACCESS read-only 1126 STATUS current 1127 DESCRIPTION 1128 "The side of the unit associated with this segment endpoint - 1129 Network/Customer side - as per the Hdsl2ShdslUnitSide textual 1130 convention." 1131 ::= { hdsl2ShdslEndpointConfEntry 1 } 1133 Expires October 2, 2001 Page [20] 1134 hdsl2ShdslEndpointWirePair OBJECT-TYPE 1135 SYNTAX Hdsl2ShdslWirePair 1136 MAX-ACCESS read-only 1137 STATUS current 1138 DESCRIPTION 1139 "The wire-pair of the modem associated with this segment 1140 endpoint as per the Hdsl2ShdslWirePair textual convention." 1141 ::= { hdsl2ShdslEndpointConfEntry 2 } 1143 hdsl2ShdslEndpointAlarmConfProfile OBJECT-TYPE 1144 SYNTAX SnmpAdminString (SIZE(0..32)) 1145 MAX-ACCESS read-write 1146 STATUS current 1147 DESCRIPTION 1148 "This object configures the alarm threshold values to be used 1149 for this segment endpoint. The values are obtained from the 1150 alarm configuration profile referenced by this object. The 1151 value of this object is the index of the referenced profile in 1152 the hdsl2ShdslEndpointAlarmConf ProfileTable, or NULL (a zero- 1153 length SnmpAdminString). If the value is NULL, the endpoint 1154 uses the default Alarm Configuration Profile for the associated 1155 span as per the hdsl2ShdslSpanConfAlarmProfile object in the 1156 hdsl2ShdslSpanConfTable. The default value of this object is 1157 NULL." 1158 ::= { hdsl2ShdslEndpointConfEntry 3 } 1160 -- Segment Endpoint Current Status/Performance Group 1161 -- 1163 hdsl2ShdslEndpointCurrTable OBJECT-TYPE 1164 SYNTAX SEQUENCE OF Hdsl2ShdslEndpointCurrEntry 1165 MAX-ACCESS not-accessible 1166 STATUS current 1167 DESCRIPTION 1168 "This table contains current status and performance information 1169 for segment endpoints in HDSL2/SHDSL Lines." 1170 ::= { hdsl2ShdslMibObjects 5 } 1172 hdsl2ShdslEndpointCurrEntry OBJECT-TYPE 1173 SYNTAX Hdsl2ShdslEndpointCurrEntry 1174 MAX-ACCESS not-accessible 1175 STATUS current 1176 DESCRIPTION 1177 "An entry in the hdsl2ShdslEndpointCurrTable. Each entry 1178 contains status and performance information relating to a 1179 single segment endpoint. It is indexed by the ifIndex of the 1180 HDSL2/SHDSL line, the UnitId of the associated unit, the side 1181 of the unit, and the wire-pair of the associated modem." 1182 INDEX { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide, 1183 hdsl2ShdslEndpointWirePair } 1184 ::= { hdsl2ShdslEndpointCurrTable 1 } 1186 Hdsl2ShdslEndpointCurrEntry ::= 1187 SEQUENCE 1189 Expires October 2, 2001 Page [21] 1190 { 1191 hdsl2ShdslEndpointCurrAtn Integer32, 1192 hdsl2ShdslEndpointCurrSnrMgn Integer32, 1193 hdsl2ShdslEndpointCurrStatus Integer32, 1194 hdsl2ShdslEndpointES Counter32, 1195 hdsl2ShdslEndpointSES Counter32, 1196 hdsl2ShdslEndpointCRCanomalies Counter32, 1197 hdsl2ShdslEndpointLOSWS Counter32, 1198 hdsl2ShdslEndpointUAS Counter32, 1199 hdsl2ShdslEndpointCurr15MinTimeElapsed Hdsl2ShdslPerfTimeElapsed, 1200 hdsl2ShdslEndpointCurr15MinES PerfCurrentCount, 1201 hdsl2ShdslEndpointCurr15MinSES PerfCurrentCount, 1202 hdsl2ShdslEndpointCurr15MinCRCanomalies PerfCurrentCount, 1203 hdsl2ShdslEndpointCurr15MinLOSWS PerfCurrentCount, 1204 hdsl2ShdslEndpointCurr15MinUAS PerfCurrentCount, 1205 hdsl2ShdslEndpointCurr1DayTimeElapsed Hdsl2ShdslPerfTimeElapsed, 1206 hdsl2ShdslEndpointCurr1DayES Hdsl2ShdslPerfCurrDayCount, 1207 hdsl2ShdslEndpointCurr1DaySES Hdsl2ShdslPerfCurrDayCount, 1208 hdsl2ShdslEndpointCurr1DayCRCanomalies Hdsl2ShdslPerfCurrDayCount, 1209 hdsl2ShdslEndpointCurr1DayLOSWS Hdsl2ShdslPerfCurrDayCount, 1210 hdsl2ShdslEndpointCurr1DayUAS Hdsl2ShdslPerfCurrDayCount 1211 } 1213 hdsl2ShdslEndpointCurrAtn OBJECT-TYPE 1214 SYNTAX Integer32 1215 UNITS "dB" 1216 MAX-ACCESS read-only 1217 STATUS current 1218 DESCRIPTION 1219 "The current loop attenuation for this endpoint as reported in 1220 a Network or Customer Side Performance Status message." 1221 ::= { hdsl2ShdslEndpointCurrEntry 1 } 1223 hdsl2ShdslEndpointCurrSnrMgn OBJECT-TYPE 1224 SYNTAX Integer32 1225 UNITS "dB" 1226 MAX-ACCESS read-only 1227 STATUS current 1228 DESCRIPTION 1229 "The current SNR margin for this endpoint as reported in a 1230 Status Response/SNR message." 1231 ::= { hdsl2ShdslEndpointCurrEntry 2 } 1233 hdsl2ShdslEndpointCurrStatus OBJECT-TYPE 1234 SYNTAX Integer32 1235 MAX-ACCESS read-only 1236 STATUS current 1237 DESCRIPTION 1238 "Contains the current state of the endpoint. This is a 1239 bit-map of possible conditions. The various bit positions 1240 are: 1242 1 noDefect There no defects on the line 1244 2 powerBackoff Indicates enhanced Power Backoff 1246 Expires October 2, 2001 Page [22] 1247 4 deviceFault Indicates a vendor-dependent 1248 detection of diagnostics or 1249 self-test results 1251 8 dcContinuityFault Indicates vendor-dependent 1252 conditions that interfere with 1253 span powering such as short and 1254 open circuits 1256 16 snrMarginAlarm Indicates that the SNR margin 1257 has dropped below the alarm threshold 1259 32 loopAttenuationAlarm Indicates that the loop attentuation 1260 has dropped below the alarm threshold 1262 64 loswFailureAlarm Indicates a forward LOSW alarm 1264 128 configInitFailure Endpoint failure during initialization 1265 due to paired endpoint not able to 1266 support requested configuration 1268 256 protocolInitFailure Endpoint failure during initialization 1269 due to incompatible protocol used by 1270 the paired endpoint. 1272 512 noNeighborPresent Endpoint failure during initialization 1273 due to no activation sequence detected 1274 from paired endpoint. 1276 1024 loopbackActive A loopback is currently active at this 1277 Segment Endpoint. 1279 This is intended to supplement ifOperStatus." 1280 ::= { hdsl2ShdslEndpointCurrEntry 3 } 1282 hdsl2ShdslEndpointES OBJECT-TYPE 1283 SYNTAX Counter32 1284 UNITS "seconds" 1285 MAX-ACCESS read-only 1286 STATUS current 1287 DESCRIPTION 1288 "Count of Errored Seconds (ES) on this endpoint since the xU 1289 was last restarted." 1290 ::= { hdsl2ShdslEndpointCurrEntry 4 } 1292 hdsl2ShdslEndpointSES OBJECT-TYPE 1293 SYNTAX Counter32 1294 UNITS "seconds" 1295 MAX-ACCESS read-only 1296 STATUS current 1297 DESCRIPTION 1298 "Count of Severely Errored Seconds (SES) on this endpoint 1299 since the xU was last restarted." 1300 ::= { hdsl2ShdslEndpointCurrEntry 5 } 1302 Expires October 2, 2001 Page [23] 1303 hdsl2ShdslEndpointCRCanomalies OBJECT-TYPE 1304 SYNTAX Counter32 1305 MAX-ACCESS read-only 1306 STATUS current 1307 DESCRIPTION 1308 "Count of CRC anomalies on this endpoint since the xU was 1309 last restarted." 1310 ::= { hdsl2ShdslEndpointCurrEntry 6 } 1312 hdsl2ShdslEndpointLOSWS OBJECT-TYPE 1313 SYNTAX Counter32 1314 UNITS "seconds" 1315 MAX-ACCESS read-only 1316 STATUS current 1317 DESCRIPTION 1318 "Count of Loss of Sync Word (LOSW) Seconds on this endpoint 1319 since the xU was last restarted." 1320 ::= { hdsl2ShdslEndpointCurrEntry 7 } 1322 hdsl2ShdslEndpointUAS OBJECT-TYPE 1323 SYNTAX Counter32 1324 UNITS "seconds" 1325 MAX-ACCESS read-only 1326 STATUS current 1327 DESCRIPTION 1328 "Count of Unavailable Seconds (UAS) on this endpoint since 1329 the xU was last restarted." 1330 ::= { hdsl2ShdslEndpointCurrEntry 8 } 1332 hdsl2ShdslEndpointCurr15MinTimeElapsed OBJECT-TYPE 1333 SYNTAX Hdsl2ShdslPerfTimeElapsed 1334 UNITS "seconds" 1335 MAX-ACCESS read-only 1336 STATUS current 1337 DESCRIPTION 1338 "Total elapsed seconds in the current 15-minute interval." 1339 ::= { hdsl2ShdslEndpointCurrEntry 9 } 1341 hdsl2ShdslEndpointCurr15MinES OBJECT-TYPE 1342 SYNTAX PerfCurrentCount 1343 UNITS "seconds" 1344 MAX-ACCESS read-only 1345 STATUS current 1346 DESCRIPTION 1347 "Count of Errored Seconds (ES) in the current 15-minute 1348 interval." 1349 ::= { hdsl2ShdslEndpointCurrEntry 10 } 1351 hdsl2ShdslEndpointCurr15MinSES OBJECT-TYPE 1352 SYNTAX PerfCurrentCount 1353 UNITS "seconds" 1354 MAX-ACCESS read-only 1355 STATUS current 1356 DESCRIPTION 1358 Expires October 2, 2001 Page [24] 1359 "Count of Severely Errored Seconds (SES) in the current 1360 15-minute interval." 1361 ::= { hdsl2ShdslEndpointCurrEntry 11 } 1363 hdsl2ShdslEndpointCurr15MinCRCanomalies OBJECT-TYPE 1364 SYNTAX PerfCurrentCount 1365 MAX-ACCESS read-only 1366 STATUS current 1367 DESCRIPTION 1368 "Count of CRC anomalies in the current 15-minute interval." 1369 ::= { hdsl2ShdslEndpointCurrEntry 12 } 1371 hdsl2ShdslEndpointCurr15MinLOSWS OBJECT-TYPE 1372 SYNTAX PerfCurrentCount 1373 UNITS "seconds" 1374 MAX-ACCESS read-only 1375 STATUS current 1376 DESCRIPTION 1377 "Count of Loss of Sync Word (LOSW) Seconds in the current 1378 15-minute interval." 1379 ::= { hdsl2ShdslEndpointCurrEntry 13 } 1381 hdsl2ShdslEndpointCurr15MinUAS OBJECT-TYPE 1382 SYNTAX PerfCurrentCount 1383 UNITS "seconds" 1384 MAX-ACCESS read-only 1385 STATUS current 1386 DESCRIPTION 1387 "Count of Unavailable Seconds (UAS) in the current 15-minute 1388 interval." 1389 ::= { hdsl2ShdslEndpointCurrEntry 14 } 1391 hdsl2ShdslEndpointCurr1DayTimeElapsed OBJECT-TYPE 1392 SYNTAX Hdsl2ShdslPerfTimeElapsed 1393 UNITS "seconds" 1394 MAX-ACCESS read-only 1395 STATUS current 1396 DESCRIPTION 1397 "Number of seconds that have elapsed since the beginning of 1398 the current 1-day interval." 1399 ::= { hdsl2ShdslEndpointCurrEntry 15 } 1401 hdsl2ShdslEndpointCurr1DayES OBJECT-TYPE 1402 SYNTAX Hdsl2ShdslPerfCurrDayCount 1403 UNITS "seconds" 1404 MAX-ACCESS read-only 1405 STATUS current 1406 DESCRIPTION 1407 "Count of Errored Seconds (ES) during the current day as 1408 measured by hdsl2ShdslEndpointCurr1DayTimeElapsed." 1409 ::= { hdsl2ShdslEndpointCurrEntry 16 } 1411 hdsl2ShdslEndpointCurr1DaySES OBJECT-TYPE 1412 SYNTAX Hdsl2ShdslPerfCurrDayCount 1413 UNITS "seconds" 1415 Expires October 2, 2001 Page [25] 1416 MAX-ACCESS read-only 1417 STATUS current 1418 DESCRIPTION 1419 "Count of Severely Errored Seconds (SES) during the current 1420 day as measured by hdsl2ShdslEndpointCurr1DayTimeElapsed." 1421 ::= { hdsl2ShdslEndpointCurrEntry 17 } 1423 hdsl2ShdslEndpointCurr1DayCRCanomalies OBJECT-TYPE 1424 SYNTAX Hdsl2ShdslPerfCurrDayCount 1425 MAX-ACCESS read-only 1426 STATUS current 1427 DESCRIPTION 1428 "Count of CRC anomalies during the current day as measured 1429 by hdsl2ShdslEndpointCurr1DayTimeElapsed." 1430 ::= { hdsl2ShdslEndpointCurrEntry 18 } 1432 hdsl2ShdslEndpointCurr1DayLOSWS OBJECT-TYPE 1433 SYNTAX Hdsl2ShdslPerfCurrDayCount 1434 UNITS "seconds" 1435 MAX-ACCESS read-only 1436 STATUS current 1437 DESCRIPTION 1438 "Count of Loss of Sync Word (LOSW) Seconds during the current 1439 day as measured by hdsl2ShdslEndpointCurr1DayTimeElapsed." 1440 ::= { hdsl2ShdslEndpointCurrEntry 19 } 1442 hdsl2ShdslEndpointCurr1DayUAS OBJECT-TYPE 1443 SYNTAX Hdsl2ShdslPerfCurrDayCount 1444 UNITS "seconds" 1445 MAX-ACCESS read-only 1446 STATUS current 1447 DESCRIPTION 1448 "Count of Unavailable Seconds (UAS) during the current day as 1449 measured by hdsl2ShdslEndpointCurr1DayTimeElapsed." 1450 ::= { hdsl2ShdslEndpointCurrEntry 20 } 1452 -- Segment Endpoint 15-Minute Interval Status/Performance Group 1453 -- 1455 hdsl2Shdsl15MinIntervalTable OBJECT-TYPE 1456 SYNTAX SEQUENCE OF Hdsl2Shdsl15MinIntervalEntry 1457 MAX-ACCESS not-accessible 1458 STATUS current 1459 DESCRIPTION 1460 "This table provides one row for each HDSL2/SHDSL endpoint 1461 performance data collection interval." 1462 ::= { hdsl2ShdslMibObjects 6 } 1464 hdsl2Shdsl15MinIntervalEntry OBJECT-TYPE 1465 SYNTAX Hdsl2Shdsl15MinIntervalEntry 1466 MAX-ACCESS not-accessible 1467 STATUS current 1468 DESCRIPTION 1469 "An entry in the hdsl2Shdsl15MinIntervalTable." 1470 INDEX { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide, 1472 Expires October 2, 2001 Page [26] 1473 hdsl2ShdslEndpointWirePair, hdsl2Shdsl15MinIntervalNumber} 1474 ::= { hdsl2Shdsl15MinIntervalTable 1 } 1476 Hdsl2Shdsl15MinIntervalEntry ::= 1477 SEQUENCE 1478 { 1479 hdsl2Shdsl15MinIntervalNumber INTEGER, 1480 hdsl2Shdsl15MinIntervalES PerfIntervalCount, 1481 hdsl2Shdsl15MinIntervalSES PerfIntervalCount, 1482 hdsl2Shdsl15MinIntervalCRCanomalies PerfIntervalCount, 1483 hdsl2Shdsl15MinIntervalLOSWS PerfIntervalCount, 1484 hdsl2Shdsl15MinIntervalUAS PerfIntervalCount 1485 } 1487 hdsl2Shdsl15MinIntervalNumber OBJECT-TYPE 1488 SYNTAX INTEGER(1..96) 1489 MAX-ACCESS not-accessible 1490 STATUS current 1491 DESCRIPTION 1492 "Performance Data Interval number. 1 is the the most recent 1493 previous interval; interval 96 is 24 hours ago. Intervals 1494 2..96 are optional." 1495 ::= { hdsl2Shdsl15MinIntervalEntry 1 } 1497 hdsl2Shdsl15MinIntervalES OBJECT-TYPE 1498 SYNTAX PerfIntervalCount 1499 UNITS "seconds" 1500 MAX-ACCESS read-only 1501 STATUS current 1502 DESCRIPTION 1503 "Count of Errored Seconds (ES) during the interval." 1504 ::= { hdsl2Shdsl15MinIntervalEntry 2 } 1506 hdsl2Shdsl15MinIntervalSES OBJECT-TYPE 1507 SYNTAX PerfIntervalCount 1508 UNITS "seconds" 1509 MAX-ACCESS read-only 1510 STATUS current 1511 DESCRIPTION 1512 "Count of Severely Errored Seconds (SES) during the 1513 interval." 1514 ::= { hdsl2Shdsl15MinIntervalEntry 3 } 1516 hdsl2Shdsl15MinIntervalCRCanomalies OBJECT-TYPE 1517 SYNTAX PerfIntervalCount 1518 MAX-ACCESS read-only 1519 STATUS current 1520 DESCRIPTION 1521 "Count of CRC anomalies during the interval." 1522 ::= { hdsl2Shdsl15MinIntervalEntry 4 } 1524 hdsl2Shdsl15MinIntervalLOSWS OBJECT-TYPE 1525 SYNTAX PerfIntervalCount 1526 UNITS "seconds" 1527 MAX-ACCESS read-only 1529 Expires October 2, 2001 Page [27] 1530 STATUS current 1531 DESCRIPTION 1532 "Count of Loss of Sync Word (LOSW) Seconds during the 1533 interval." 1534 ::= { hdsl2Shdsl15MinIntervalEntry 5 } 1536 hdsl2Shdsl15MinIntervalUAS OBJECT-TYPE 1537 SYNTAX PerfIntervalCount 1538 UNITS "seconds" 1539 MAX-ACCESS read-only 1540 STATUS current 1541 DESCRIPTION 1542 "Count of Unavailable Seconds (UAS) during the interval." 1543 ::= { hdsl2Shdsl15MinIntervalEntry 6 } 1545 -- Segment Endpoint 1-Day Interval Status/Performance Group 1546 -- 1548 hdsl2Shdsl1DayIntervalTable OBJECT-TYPE 1549 SYNTAX SEQUENCE OF Hdsl2Shdsl1DayIntervalEntry 1550 MAX-ACCESS not-accessible 1551 STATUS current 1552 DESCRIPTION 1553 "This table provides one row for each HDSL2/SHDSL endpoint 1554 performance data collection interval." 1555 ::= { hdsl2ShdslMibObjects 7 } 1557 hdsl2Shdsl1DayIntervalEntry OBJECT-TYPE 1558 SYNTAX Hdsl2Shdsl1DayIntervalEntry 1559 MAX-ACCESS not-accessible 1560 STATUS current 1561 DESCRIPTION 1562 "An entry in the hdsl2Shdsl1DayIntervalTable." 1563 INDEX { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide, 1564 hdsl2ShdslEndpointWirePair, hdsl2Shdsl1DayIntervalNumber } 1565 ::= { hdsl2Shdsl1DayIntervalTable 1 } 1567 Hdsl2Shdsl1DayIntervalEntry ::= 1568 SEQUENCE 1569 { 1570 hdsl2Shdsl1DayIntervalNumber INTEGER, 1571 hdsl2Shdsl1DayIntervalMoniSecs Hdsl2ShdslPerfTimeElapsed, 1572 hdsl2Shdsl1DayIntervalES Hdsl2Shdsl1DayIntervalCount, 1573 hdsl2Shdsl1DayIntervalSES Hdsl2Shdsl1DayIntervalCount, 1574 hdsl2Shdsl1DayIntervalCRCanomalies Hdsl2Shdsl1DayIntervalCount, 1575 hdsl2Shdsl1DayIntervalLOSWS Hdsl2Shdsl1DayIntervalCount, 1576 hdsl2Shdsl1DayIntervalUAS Hdsl2Shdsl1DayIntervalCount 1577 } 1579 hdsl2Shdsl1DayIntervalNumber OBJECT-TYPE 1580 SYNTAX INTEGER(1..30) 1581 MAX-ACCESS not-accessible 1582 STATUS current 1583 DESCRIPTION 1584 "History Data Interval number. Interval 1 is the the most 1586 Expires October 2, 2001 Page [28] 1587 recent previous day; interval 30 is 30 days ago. Intervals 1588 2..30 are optional." 1589 ::= { hdsl2Shdsl1DayIntervalEntry 1 } 1591 hdsl2Shdsl1DayIntervalMoniSecs OBJECT-TYPE 1592 SYNTAX Hdsl2ShdslPerfTimeElapsed 1593 MAX-ACCESS read-only 1594 STATUS current 1595 DESCRIPTION 1596 "The amount of time in the 1-day interval over which the 1597 performance monitoring information is actually counted. 1598 This value will be the same as the interval duration except 1599 in a situation where performance monitoring data could not 1600 be collected for any reason." 1601 ::= { hdsl2Shdsl1DayIntervalEntry 2 } 1603 hdsl2Shdsl1DayIntervalES OBJECT-TYPE 1604 SYNTAX Hdsl2Shdsl1DayIntervalCount 1605 UNITS "seconds" 1606 MAX-ACCESS read-only 1607 STATUS current 1608 DESCRIPTION 1609 "Count of Errored Seconds (ES) during the 1-day interval as 1610 measured by hdsl2Shdsl1DayIntervalMoniSecs." 1611 ::= { hdsl2Shdsl1DayIntervalEntry 3 } 1613 hdsl2Shdsl1DayIntervalSES OBJECT-TYPE 1614 SYNTAX Hdsl2Shdsl1DayIntervalCount 1615 UNITS "seconds" 1616 MAX-ACCESS read-only 1617 STATUS current 1618 DESCRIPTION 1619 "Count of Severely Errored Seconds (SES) during the 1-day 1620 interval as measured by hdsl2Shdsl1DayIntervalMoniSecs." 1621 ::= { hdsl2Shdsl1DayIntervalEntry 4 } 1623 hdsl2Shdsl1DayIntervalCRCanomalies OBJECT-TYPE 1624 SYNTAX Hdsl2Shdsl1DayIntervalCount 1625 MAX-ACCESS read-only 1626 STATUS current 1627 DESCRIPTION 1628 "Count of CRC anomalies during the 1-day interval as 1629 measured by hdsl2Shdsl1DayIntervalMoniSecs." 1630 ::= { hdsl2Shdsl1DayIntervalEntry 5 } 1632 hdsl2Shdsl1DayIntervalLOSWS OBJECT-TYPE 1633 SYNTAX Hdsl2Shdsl1DayIntervalCount 1634 UNITS "seconds" 1635 MAX-ACCESS read-only 1636 STATUS current 1637 DESCRIPTION 1638 "Count of Loss of Sync Word (LOSW) Seconds during the 1-day 1639 interval as measured by hdsl2Shdsl1DayIntervalMoniSecs." 1640 ::= { hdsl2Shdsl1DayIntervalEntry 6 } 1642 Expires October 2, 2001 Page [29] 1643 hdsl2Shdsl1DayIntervalUAS OBJECT-TYPE 1644 SYNTAX Hdsl2Shdsl1DayIntervalCount 1645 MAX-ACCESS read-only 1646 STATUS current 1647 DESCRIPTION 1648 "Count of Unavailable Seconds (UAS) during the 1-day interval 1649 as measured by hdsl2Shdsl1DayIntervalMoniSecs." 1650 ::= { hdsl2Shdsl1DayIntervalEntry 7 } 1652 -- Maintenance Group 1653 -- 1655 hdsl2ShdslEndpointMaintTable OBJECT-TYPE 1656 SYNTAX SEQUENCE OF Hdsl2ShdslEndpointMaintEntry 1657 MAX-ACCESS not-accessible 1658 STATUS current 1659 DESCRIPTION 1660 "This table supports maintenance operations (eg. loopbacks) 1661 to be performed on HDSL2/SHDSL segment endpoints." 1662 ::= { hdsl2ShdslMibObjects 8 } 1664 hdsl2ShdslEndpointMaintEntry OBJECT-TYPE 1665 SYNTAX Hdsl2ShdslEndpointMaintEntry 1666 MAX-ACCESS not-accessible 1667 STATUS current 1668 DESCRIPTION 1669 "An entry in the hdsl2ShdslEndpointMaintTable. Each entry 1670 corresponds to a single segment endpoint, and is indexed by the 1671 ifIndex of the HDSL2/SHDSL line, the UnitId of the associated 1672 unit and the side of the unit." 1673 INDEX { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide } 1674 ::= { hdsl2ShdslEndpointMaintTable 1 } 1676 Hdsl2ShdslEndpointMaintEntry ::= 1677 SEQUENCE 1678 { 1679 hdsl2ShdslMaintLoopbackConfig INTEGER, 1680 hdsl2ShdslMaintTipRingReversal INTEGER, 1681 hdsl2ShdslMaintPowerBackOff INTEGER, 1682 hdsl2ShdslMaintSoftRestart INTEGER 1683 } 1685 hdsl2ShdslMaintLoopbackConfig OBJECT-TYPE 1686 SYNTAX INTEGER 1687 { 1688 noLoopback(1), 1689 normalLoopback(2), 1690 specialLoopback(3) 1691 } 1692 MAX-ACCESS read-write 1693 STATUS current 1694 DESCRIPTION 1695 "This object controls configuration of loopbacks for the 1696 associated segment endpoint. The status of the loopback 1697 is obtained via the hdsl2ShdslEndpointCurrStatus object." 1699 Expires October 2, 2001 Page [30] 1700 ::= { hdsl2ShdslEndpointMaintEntry 1 } 1702 hdsl2ShdslMaintTipRingReversal OBJECT-TYPE 1703 SYNTAX INTEGER 1704 { 1705 normal(1), 1706 reversed(2) 1707 } 1708 MAX-ACCESS read-only 1709 STATUS current 1710 DESCRIPTION 1711 "This object indicates the state of the tip/ring pair at 1712 the associated segment endpoint." 1713 ::= { hdsl2ShdslEndpointMaintEntry 2 } 1715 hdsl2ShdslMaintPowerBackOff OBJECT-TYPE 1716 SYNTAX INTEGER 1717 { 1718 default(1), 1719 enhanced(2) 1720 } 1721 MAX-ACCESS read-write 1722 STATUS current 1723 DESCRIPTION 1724 "This object configures the receiver at the associated 1725 segment endpoint to operate in default or enhanced power 1726 backoff mode." 1727 ::= { hdsl2ShdslEndpointMaintEntry 3 } 1729 hdsl2ShdslMaintSoftRestart OBJECT-TYPE 1730 SYNTAX INTEGER 1731 { 1732 ready(1), 1733 restart(2) 1734 } 1735 MAX-ACCESS read-write 1736 STATUS current 1737 DESCRIPTION 1738 "This object enables the manager to trigger a soft restart 1739 of the modem at the associated segment endpoint. The manager 1740 may only set this object to the 'restart(2)' value to initiate 1741 a restart. The agent will perform a restart after 1742 approximately 5 seconds, and restore the object to the 1743 'ready(1)' state." 1744 ::= { hdsl2ShdslEndpointMaintEntry 4 } 1746 hdsl2ShdslUnitMaintTable OBJECT-TYPE 1747 SYNTAX SEQUENCE OF Hdsl2ShdslUnitMaintEntry 1748 MAX-ACCESS not-accessible 1749 STATUS current 1750 DESCRIPTION 1751 "This table supports maintenance operations for units in a 1752 HDSL2/SHDSL line." 1753 ::= { hdsl2ShdslMibObjects 9 } 1755 Expires October 2, 2001 Page [31] 1756 hdsl2ShdslUnitMaintEntry OBJECT-TYPE 1757 SYNTAX Hdsl2ShdslUnitMaintEntry 1758 MAX-ACCESS not-accessible 1759 STATUS current 1760 DESCRIPTION 1761 "An entry in the hdsl2ShdslUnitMaintTable. Each entry 1762 corresponds to a single unit, and is indexed by the ifIndex 1763 of the HDSL2/SHDSL line and the UnitId of the associated 1764 unit." 1765 INDEX { ifIndex, hdsl2ShdslInvIndex } 1766 ::= { hdsl2ShdslUnitMaintTable 1 } 1768 Hdsl2ShdslUnitMaintEntry ::= 1769 SEQUENCE 1770 { 1771 hdsl2ShdslMaintLoopbackTimeout Integer32, 1772 hdsl2ShdslMaintUnitPowerSource INTEGER 1773 } 1775 hdsl2ShdslMaintLoopbackTimeout OBJECT-TYPE 1776 SYNTAX Integer32 1777 MAX-ACCESS read-write 1778 STATUS current 1779 DESCRIPTION 1780 "This object configures the timeout value for loopbacks 1781 initiated at segments endpoints contained in the associated 1782 unit. A value of 0 disables the timeout." 1783 ::= { hdsl2ShdslUnitMaintEntry 1 } 1785 hdsl2ShdslMaintUnitPowerSource OBJECT-TYPE 1786 SYNTAX INTEGER 1787 { 1788 local(1), 1789 span(2) 1790 } 1791 MAX-ACCESS read-only 1792 STATUS current 1793 DESCRIPTION 1794 "This object indicates the DC power source being used by the 1795 associated unit." 1796 ::= { hdsl2ShdslUnitMaintEntry 2 } 1798 -- Span Configuration Profile Group 1799 -- 1801 hdsl2ShdslSpanConfProfileTable OBJECT-TYPE 1802 SYNTAX SEQUENCE OF Hdsl2ShdslSpanConfProfileEntry 1803 MAX-ACCESS not-accessible 1804 STATUS current 1805 DESCRIPTION 1806 "This table supports definitions of span configuration 1807 profiles for SHDSL lines. HDSL2 does not support these 1808 configuration options." 1809 ::= { hdsl2ShdslMibObjects 10 } 1811 Expires October 2, 2001 Page [32] 1812 hdsl2ShdslSpanConfProfileEntry OBJECT-TYPE 1813 SYNTAX Hdsl2ShdslSpanConfProfileEntry 1814 MAX-ACCESS not-accessible 1815 STATUS current 1816 DESCRIPTION 1817 "Each entry corresponds to a single span configuration 1818 profile. Each profile contains a set of span configuration 1819 parameters. The configuration parameters in a profile are 1820 applied to those lines referencing that profile (see the 1821 hdsl2ShdslSpanConfProfile object). Profiles may be 1822 created/deleted using the row creation/deletion mechanism 1823 via hdsl2ShdslSpanConfProfileRowStatus. Profiles that are 1824 being referenced may not be deleted." 1825 INDEX { IMPLIED hdsl2ShdslSpanConfProfileName } 1826 ::= { hdsl2ShdslSpanConfProfileTable 1 } 1828 Hdsl2ShdslSpanConfProfileEntry ::= 1829 SEQUENCE 1830 { 1831 hdsl2ShdslSpanConfProfileName SnmpAdminString, 1832 hdsl2ShdslSpanConfWireInterface INTEGER, 1833 hdsl2ShdslSpanConfMinLineRate Integer32, 1834 hdsl2ShdslSpanConfMaxLineRate Integer32, 1835 hdsl2ShdslSpanConfPSD INTEGER, 1836 hdsl2ShdslSpanConfTransmissionMode 1837 Hdsl2ShdslTransmissionModeType, 1838 hdsl2ShdslSpanConfRemoteEnabled INTEGER, 1839 hdsl2ShdslSpanConfPowerFeeding INTEGER, 1840 hdsl2ShdslSpanConfCurrCondTargetMarginDown INTEGER, 1841 hdsl2ShdslSpanConfWorstCaseTargetMarginDown INTEGER, 1842 hdsl2ShdslSpanConfCurrCondTargetMarginUp INTEGER, 1843 hdsl2ShdslSpanConfWorstCaseTargetMarginUp INTEGER, 1844 hdsl2ShdslSpanConfUsedTargetMargins Integer32, 1845 hdsl2ShdslSpanConfProfileRowStatus RowStatus 1846 } 1848 hdsl2ShdslSpanConfProfileName OBJECT-TYPE 1849 SYNTAX SnmpAdminString (SIZE(1..32)) 1850 MAX-ACCESS not-accessible 1851 STATUS current 1852 DESCRIPTION 1853 "This object is the unique index associated with this profile." 1854 ::= { hdsl2ShdslSpanConfProfileEntry 1 } 1856 hdsl2ShdslSpanConfWireInterface OBJECT-TYPE 1857 SYNTAX INTEGER 1858 { 1859 twoWire(1), 1860 fourWire(2) 1861 } 1862 MAX-ACCESS read-create 1863 STATUS current 1864 DESCRIPTION 1865 "This object configures the two-wire or optional four-wire 1866 operation for SHDSL Lines." 1868 Expires October 2, 2001 Page [33] 1869 ::= { hdsl2ShdslSpanConfProfileEntry 2 } 1871 hdsl2ShdslSpanConfMinLineRate OBJECT-TYPE 1872 SYNTAX Integer32 1873 UNITS "bps" 1874 MAX-ACCESS read-create 1875 STATUS current 1876 DESCRIPTION 1877 "This object configures the minimum transmission rate for 1878 the associated SHDSL Line in bits-per-second (bps). If 1879 the minimum line rate equals the maximum line rate 1880 (hdsl2ShdslSpanMaxLineRate), the line rate is considered 1881 'fixed'. If the minimum line rate is less than the maximum 1882 line rate, the line rate is considered 'rate-adaptive'." 1883 ::= { hdsl2ShdslSpanConfProfileEntry 3 } 1885 hdsl2ShdslSpanConfMaxLineRate OBJECT-TYPE 1886 SYNTAX Integer32 1887 UNITS "bps" 1888 MAX-ACCESS read-create 1889 STATUS current 1890 DESCRIPTION 1891 "This object configures the maximum transmission rate for 1892 the associated SHDSL Line in bits-per-second (bps). If 1893 the minimum line rate equals the maximum line rate 1894 (hdsl2ShdslSpanMaxLineRate), the line rate is considered 1895 'fixed'. If the minimum line rate is less than the maximum 1896 line rate, the line rate is considered 'rate-adaptive'." 1897 ::= { hdsl2ShdslSpanConfProfileEntry 4 } 1899 hdsl2ShdslSpanConfPSD OBJECT-TYPE 1900 SYNTAX INTEGER 1901 { 1902 symmetric(1), 1903 asymmetric(2) 1904 } 1905 MAX-ACCESS read-create 1906 STATUS current 1907 DESCRIPTION 1908 "This object configures use of symmetric/asymmetric PSD (Power 1909 Spectral Density) Mask for the associated SHDSL Line. Support 1910 for symmetric PSD is mandatory for all supported data rates. 1911 Support for asymmetric PSD is optional." 1912 ::= { hdsl2ShdslSpanConfProfileEntry 5 } 1914 hdsl2ShdslSpanConfTransmissionMode OBJECT-TYPE 1915 SYNTAX Hdsl2ShdslTransmissionModeType 1916 MAX-ACCESS read-create 1917 STATUS current 1918 DESCRIPTION 1919 "This object specifies the regional setting for the SHDSL 1920 line." 1921 ::= { hdsl2ShdslSpanConfProfileEntry 6 } 1923 hdsl2ShdslSpanConfRemoteEnabled OBJECT-TYPE 1925 Expires October 2, 2001 Page [34] 1926 SYNTAX INTEGER 1927 { 1928 enabled(1), 1929 disabled(2) 1930 } 1931 MAX-ACCESS read-create 1932 STATUS current 1933 DESCRIPTION 1934 "This object enables/disables support for remote management 1935 of the units in a SHDSL line from the STU-R via the EOC." 1936 ::= { hdsl2ShdslSpanConfProfileEntry 7 } 1938 hdsl2ShdslSpanConfPowerFeeding OBJECT-TYPE 1939 SYNTAX INTEGER 1940 { 1941 noPower(1), 1942 powerFeed(2), 1943 wettingCurrent(3) 1944 } 1945 MAX-ACCESS read-create 1946 STATUS current 1947 DESCRIPTION 1948 "This object enables/disables support for optional power 1949 feeding in a SHDSL line." 1950 ::= { hdsl2ShdslSpanConfProfileEntry 8 } 1952 hdsl2ShdslSpanConfCurrCondTargetMarginDown OBJECT-TYPE 1953 SYNTAX INTEGER(-10..21) 1954 UNITS "dB" 1955 MAX-ACCESS read-create 1956 STATUS current 1957 DESCRIPTION 1958 "This object specifies the downstream current condition target 1959 SNR margin for a SHDSL line. The SNR margin is the difference 1960 between the desired SNR and the actual SNR. Target SNR margin 1961 is the desired SNR margin for a unit." 1962 ::= { hdsl2ShdslSpanConfProfileEntry 9 } 1964 hdsl2ShdslSpanConfWorstCaseTargetMarginDown OBJECT-TYPE 1965 SYNTAX INTEGER(-10..21) 1966 UNITS "dB" 1967 MAX-ACCESS read-create 1968 STATUS current 1969 DESCRIPTION 1970 "This object specifies the downstream worst case target SNR 1971 margin for a SHDSL line. The SNR margin is the difference 1972 between the desired SNR and the actual SNR. Target SNR 1973 margin is the desired SNR margin for a unit." 1974 ::= { hdsl2ShdslSpanConfProfileEntry 10 } 1976 hdsl2ShdslSpanConfCurrCondTargetMarginUp OBJECT-TYPE 1977 SYNTAX INTEGER(-10..21) 1978 UNITS "dB" 1979 MAX-ACCESS read-create 1980 STATUS current 1982 Expires October 2, 2001 Page [35] 1983 DESCRIPTION 1984 "This object specifies the upstream current condition target 1985 SNR margin for a SHDSL line. The SNR margin is the difference 1986 between the desired SNR and the actual SNR. Target SNR margin 1987 is the desired SNR margin for a unit." 1988 ::= { hdsl2ShdslSpanConfProfileEntry 11 } 1990 hdsl2ShdslSpanConfWorstCaseTargetMarginUp OBJECT-TYPE 1991 SYNTAX INTEGER(-10..21) 1992 UNITS "dB" 1993 MAX-ACCESS read-create 1994 STATUS current 1995 DESCRIPTION 1996 "This object specifies the upstream worst case target SNR 1997 margin for a SHDSL line. The SNR margin is the difference 1998 between the desired SNR and the actual SNR. Target SNR margin 1999 is the desired SNR margin for a unit." 2000 ::= { hdsl2ShdslSpanConfProfileEntry 12 } 2002 hdsl2ShdslSpanConfUsedTargetMargins OBJECT-TYPE 2003 SYNTAX Integer32 2004 MAX-ACCESS read-create 2005 STATUS current 2006 DESCRIPTION 2007 "Contains indicates whether a target SNR margin is enabled or 2008 disabled. This is a bit-map of possible settings. The 2009 various bit positions are: 2011 1 currCondDown current condition downstream target SNR 2012 margin enabled 2014 2 worstCaseDown worst case downstream target SNR margin 2015 enabled 2017 4 currCondUp current condition upstream target SNR 2018 margin enabled 2020 8 worstCaseUp worst case upstream target SNR margin 2021 enabled." 2022 ::= { hdsl2ShdslSpanConfProfileEntry 13 } 2024 hdsl2ShdslSpanConfProfileRowStatus OBJECT-TYPE 2025 SYNTAX RowStatus 2026 MAX-ACCESS read-create 2027 STATUS current 2028 DESCRIPTION 2029 "This object controlls creation/deletion of the associated 2030 entry in this table per the semantics of RowStatus." 2031 ::= { hdsl2ShdslSpanConfProfileEntry 14 } 2033 -- Segment Endpoint Alarm Configuration Profile group 2034 -- 2036 hdsl2ShdslEndpointAlarmConfProfileTable OBJECT-TYPE 2037 SYNTAX SEQUENCE OF Hdsl2ShdslEndpointAlarmConfProfileEntry 2039 Expires October 2, 2001 Page [36] 2040 MAX-ACCESS not-accessible 2041 STATUS current 2042 DESCRIPTION 2043 "This table supports definitions of alarm configuration 2044 profiles for HDSL2/SHDSL segment endoints." 2045 ::= { hdsl2ShdslMibObjects 11 } 2047 hdsl2ShdslEndpointAlarmConfProfileEntry OBJECT-TYPE 2048 SYNTAX Hdsl2ShdslEndpointAlarmConfProfileEntry 2049 MAX-ACCESS not-accessible 2050 STATUS current 2051 DESCRIPTION 2052 "Each entry corresponds to a single alarm configuration profile. 2053 Each profile contains a set of parameters for setting alarm 2054 thresholds for various performance attributes monitored at 2055 HDSL2/SHDSL segment endpoints. Profiles may be created/deleted 2056 using the row creation/deletion mechanism via 2057 hdsl2ShdslEndpointAlarmConfProfileRowStatus. Profiles that 2058 are being referenced may not be deleted." 2059 INDEX { IMPLIED hdsl2ShdslEndpointAlarmConfProfileName } 2060 ::= { hdsl2ShdslEndpointAlarmConfProfileTable 1 } 2062 Hdsl2ShdslEndpointAlarmConfProfileEntry ::= 2063 SEQUENCE 2064 { 2065 hdsl2ShdslEndpointAlarmConfProfileName SnmpAdminString, 2066 hdsl2ShdslEndpointThreshLoopAttenuation Integer32, 2067 hdsl2ShdslEndpointThreshSNRMargin Integer32, 2068 hdsl2ShdslEndpointThreshES 2069 Hdsl2ShdslPerfIntervalThreshold, 2070 hdsl2ShdslEndpointThreshSES 2071 Hdsl2ShdslPerfIntervalThreshold, 2072 hdsl2ShdslEndpointThreshCRCanomalies Integer32, 2073 hdsl2ShdslEndpointThreshLOSWS 2074 Hdsl2ShdslPerfIntervalThreshold, 2075 hdsl2ShdslEndpointThreshUAS 2076 Hdsl2ShdslPerfIntervalThreshold, 2077 hdsl2ShdslEndpointAlarmConfProfileRowStatus RowStatus 2078 } 2080 hdsl2ShdslEndpointAlarmConfProfileName OBJECT-TYPE 2081 SYNTAX SnmpAdminString (SIZE(1..32)) 2082 MAX-ACCESS not-accessible 2083 STATUS current 2084 DESCRIPTION 2085 "This object is the unique index associated with this profile." 2086 ::= { hdsl2ShdslEndpointAlarmConfProfileEntry 1 } 2088 hdsl2ShdslEndpointThreshLoopAttenuation OBJECT-TYPE 2089 SYNTAX Integer32 2090 UNITS "dB" 2091 MAX-ACCESS read-create 2092 STATUS current 2093 DESCRIPTION 2094 "This object configures the loop attentuation alarm threshold. 2096 Expires October 2, 2001 Page [37] 2097 When the current value reaches or drops below this threshold, 2098 a hdsl2ShdslLoopAttenCrossing will be generated." 2099 ::= { hdsl2ShdslEndpointAlarmConfProfileEntry 2 } 2101 hdsl2ShdslEndpointThreshSNRMargin OBJECT-TYPE 2102 SYNTAX Integer32 2103 UNITS "dB" 2104 MAX-ACCESS read-create 2105 STATUS current 2106 DESCRIPTION 2107 "This object configures the SNR margin alarm threshold. 2108 When the current value reaches or drops below this threshold, 2109 a hdsl2ShdslSNRMarginCrossing will be generated." 2110 ::= { hdsl2ShdslEndpointAlarmConfProfileEntry 3 } 2112 hdsl2ShdslEndpointThreshES OBJECT-TYPE 2113 SYNTAX Hdsl2ShdslPerfIntervalThreshold 2114 UNITS "seconds" 2115 MAX-ACCESS read-create 2116 STATUS current 2117 DESCRIPTION 2118 "This object configures the threshold for the number of 2119 errored seconds (ES) within any given 15-minute performance 2120 data collection interval. If the value of errored seconds 2121 in a particular 15-minute collection interval reaches/ 2122 exceeds this value, a hdsl2ShdslPerfESThresh will be 2123 generated. One notification will be sent per interval per 2124 endpoint." 2125 ::= { hdsl2ShdslEndpointAlarmConfProfileEntry 4 } 2127 hdsl2ShdslEndpointThreshSES OBJECT-TYPE 2128 SYNTAX Hdsl2ShdslPerfIntervalThreshold 2129 UNITS "seconds" 2130 MAX-ACCESS read-create 2131 STATUS current 2132 DESCRIPTION 2133 "This object configures the threshold for the number of 2134 severely errored seconds (SES) within any given 15-minute 2135 performance data collection interval. If the value of 2136 severely errored seconds in a particular 15-minute collection 2137 interval reaches/exceeds this value, a hdsl2ShdslPerfSESThresh 2138 will be generated. One notification will be sent per interval 2139 per endpoint." 2140 ::= { hdsl2ShdslEndpointAlarmConfProfileEntry 5 } 2142 hdsl2ShdslEndpointThreshCRCanomalies OBJECT-TYPE 2143 SYNTAX Integer32 2144 MAX-ACCESS read-create 2145 STATUS current 2146 DESCRIPTION 2147 "This object configures the threshold for the number of 2148 CRC anomalies within any given 15-minute performance data 2149 collection interval. If the value of CRC anomalies in a 2150 particular 15-minute collection interval reaches/exceeds 2151 this value, a hdsl2ShdslPerfCRCanomaliesThresh will be 2153 Expires October 2, 2001 Page [38] 2154 generated. One notification will be sent per interval per 2155 endpoint." 2156 ::= { hdsl2ShdslEndpointAlarmConfProfileEntry 6 } 2158 hdsl2ShdslEndpointThreshLOSWS OBJECT-TYPE 2159 SYNTAX Hdsl2ShdslPerfIntervalThreshold 2160 UNITS "seconds" 2161 MAX-ACCESS read-create 2162 STATUS current 2163 DESCRIPTION 2164 "This object configures the threshold for the number of 2165 Loss of Sync Word (LOSW) Seconds within any given 15-minute 2166 performance data collection interval. If the value of LOSW 2167 in a particular 15-minute collection interval reaches/exceeds 2168 this value, a hdsl2ShdslPerfLOSWSThresh will be generated. 2169 One notification will be sent per interval per endpoint." 2170 ::= { hdsl2ShdslEndpointAlarmConfProfileEntry 7 } 2172 hdsl2ShdslEndpointThreshUAS OBJECT-TYPE 2173 SYNTAX Hdsl2ShdslPerfIntervalThreshold 2174 UNITS "seconds" 2175 MAX-ACCESS read-create 2176 STATUS current 2177 DESCRIPTION 2178 "This object configures the threshold for the number of 2179 unavailable seconds (UAS) within any given 15-minute 2180 performance data collection interval. If the value of UAS 2181 in a particular 15-minute collection interval reaches/exceeds 2182 this value, a hdsl2ShdslPerfUASThresh will be generated. 2183 One notification will be sent per interval per endpoint." 2184 ::= { hdsl2ShdslEndpointAlarmConfProfileEntry 8 } 2186 hdsl2ShdslEndpointAlarmConfProfileRowStatus OBJECT-TYPE 2187 SYNTAX RowStatus 2188 MAX-ACCESS read-create 2189 STATUS current 2190 DESCRIPTION 2191 "This object controls creation/deletion of the associated 2192 entry in this table as per the semantics of RowStatus." 2193 ::= { hdsl2ShdslEndpointAlarmConfProfileEntry 9 } 2195 -- Notifications Group 2196 -- 2198 hdsl2ShdslNotifications OBJECT IDENTIFIER ::= { hdsl2ShdslMIB 0 } 2200 hdsl2ShdslLoopAttenCrossing NOTIFICATION-TYPE 2201 OBJECTS 2202 { 2203 hdsl2ShdslEndpointCurrAtn, 2204 hdsl2ShdslEndpointThreshLoopAttenuation 2205 } 2206 STATUS current 2207 DESCRIPTION 2208 "This notification indicates that the loop attenuation 2210 Expires October 2, 2001 Page [39] 2211 threshold (as per the hdsl2ShdslEndpointThreshLoopAttenuation 2212 value) has been reached/exceeded for the HDSL2/SHDSL segment 2213 endpoint." 2214 ::= { hdsl2ShdslNotifications 1 } 2216 hdsl2ShdslSNRMarginCrossing NOTIFICATION-TYPE 2217 OBJECTS 2218 { 2219 hdsl2ShdslEndpointCurrSnrMgn, 2220 hdsl2ShdslEndpointThreshSNRMargin 2221 } 2222 STATUS current 2223 DESCRIPTION 2224 "This notification indicates that the SNR margin threshold (as 2225 per the hdsl2ShdslEndpointThreshSNRMargin value) has been 2226 reached/exceeded for the HDSL2/SHDSL segment endpoint." 2227 ::= { hdsl2ShdslNotifications 2 } 2229 hdsl2ShdslPerfESThresh NOTIFICATION-TYPE 2230 OBJECTS 2231 { 2232 hdsl2ShdslEndpointCurr15MinES, 2233 hdsl2ShdslEndpointThreshES 2234 } 2235 STATUS current 2236 DESCRIPTION 2237 "This notification indicates that the errored seconds threshold 2238 (as per the hdsl2ShdslEndpointThreshES value) has been reached/ 2239 exceeded for the HDSL2/SHDSL segment endpoint." 2240 ::= { hdsl2ShdslNotifications 3 } 2242 hdsl2ShdslPerfSESThresh NOTIFICATION-TYPE 2243 OBJECTS 2244 { 2245 hdsl2ShdslEndpointCurr15MinSES, 2246 hdsl2ShdslEndpointThreshSES 2247 } 2248 STATUS current 2249 DESCRIPTION 2250 "This notification indicates that the severely errored seconds 2251 threshold (as per the hdsl2ShdslEndpointThreshSES value) has 2252 been reached/exceeded for the HDSL2/SHDSL Segment Endpoint." 2253 ::= { hdsl2ShdslNotifications 4 } 2255 hdsl2ShdslPerfCRCanomaliesThresh NOTIFICATION-TYPE 2256 OBJECTS 2257 { 2258 hdsl2ShdslEndpointCurr15MinCRCanomalies, 2259 hdsl2ShdslEndpointThreshCRCanomalies 2260 } 2261 STATUS current 2262 DESCRIPTION 2263 "This notification indicates that the CRC anomalies threshold 2264 (as per the hdsl2ShdslEndpointThreshCRCanomalies value) has 2265 been reached/exceeded for the HDSL2/SHDSL Segment Endpoint." 2267 Expires October 2, 2001 Page [40] 2268 ::= { hdsl2ShdslNotifications 5 } 2270 hdsl2ShdslPerfLOSWSThresh NOTIFICATION-TYPE 2271 OBJECTS 2272 { 2273 hdsl2ShdslEndpointCurr15MinLOSWS, 2274 hdsl2ShdslEndpointThreshLOSWS 2275 } 2276 STATUS current 2277 DESCRIPTION 2278 "This notification indicates that the LOSW seconds threshold 2279 (as per the hdsl2ShdslEndpointThreshLOSWS value) has been 2280 reached/exceeded for the HDSL2/SHDSL segment endpoint." 2281 ::= { hdsl2ShdslNotifications 6 } 2283 hdsl2ShdslPerfUASThresh NOTIFICATION-TYPE 2284 OBJECTS 2285 { 2286 hdsl2ShdslEndpointCurr15MinUAS, 2287 hdsl2ShdslEndpointThreshUAS 2288 } 2289 STATUS current 2290 DESCRIPTION 2291 "This notification indicates that the unavailable seconds 2292 threshold (as per the hdsl2ShdslEndpointThreshUAS value) has 2293 been reached/exceeded for the HDSL2/SHDSL segment endpoint." 2294 ::= { hdsl2ShdslNotifications 7 } 2296 hdsl2ShdslSpanInvalidNumRepeaters NOTIFICATION-TYPE 2297 OBJECTS 2298 { 2299 hdsl2ShdslSpanConfNumRepeaters 2300 } 2301 STATUS current 2302 DESCRIPTION 2303 "This notification indicates that a mismatch has been detected 2304 between the number of repeater/regenerator units configured 2305 for a HDSL2/SHDSL line via the hdsl2ShdslSpanConfNumRepeaters 2306 object and the actual number of repeater/regenerator units 2307 discovered via the EOC." 2308 ::= { hdsl2ShdslNotifications 8 } 2310 hdsl2ShdslLoopbackFailure NOTIFICATION-TYPE 2311 OBJECTS 2312 { 2313 hdsl2ShdslMaintLoopbackConfig 2314 } 2315 STATUS current 2316 DESCRIPTION 2317 "This notification indicates that an endpoint maintenance 2318 loopback command failed for an HDSL2/SHDSL segment." 2319 ::= { hdsl2ShdslNotifications 9 } 2321 hdsl2ShdslpowerBackoff NOTIFICATION-TYPE 2322 OBJECTS 2324 Expires October 2, 2001 Page [41] 2325 { 2326 hdsl2ShdslEndpointCurrStatus 2327 } 2328 STATUS current 2329 DESCRIPTION 2330 "This notification indicates that the bit setting for 2331 powerBackoff in the hdsl2ShdslEndpointCurrStatus object for 2332 this endpoint has changed." 2333 ::= { hdsl2ShdslNotifications 10 } 2335 hdsl2ShdsldeviceFault NOTIFICATION-TYPE 2336 OBJECTS 2337 { 2338 hdsl2ShdslEndpointCurrStatus 2339 } 2340 STATUS current 2341 DESCRIPTION 2342 "This notification indicates that the bit setting for 2343 deviceFault in the hdsl2ShdslEndpointCurrStatus object for 2344 this endpoint has changed." 2345 ::= { hdsl2ShdslNotifications 11 } 2347 hdsl2ShdsldcContinuityFault NOTIFICATION-TYPE 2348 OBJECTS 2349 { 2350 hdsl2ShdslEndpointCurrStatus 2351 } 2352 STATUS current 2353 DESCRIPTION 2354 "This notification indicates that the bit setting for 2355 dcContinuityFault in the hdsl2ShdslEndpointCurrStatus object 2356 for this endpoint has changed." 2357 ::= { hdsl2ShdslNotifications 12 } 2359 hdsl2ShdslconfigInitFailure NOTIFICATION-TYPE 2360 OBJECTS 2361 { 2362 hdsl2ShdslEndpointCurrStatus 2363 } 2364 STATUS current 2365 DESCRIPTION 2366 "This notification indicates that the bit setting for 2367 configInitFailure in the hdsl2ShdslEndpointCurrStatus object 2368 for this endpoint has changed." 2369 ::= { hdsl2ShdslNotifications 13 } 2371 hdsl2ShdslprotocolInitFailure NOTIFICATION-TYPE 2372 OBJECTS 2373 { 2374 hdsl2ShdslEndpointCurrStatus 2375 } 2376 STATUS current 2377 DESCRIPTION 2378 "This notification indicates that the bit setting for 2379 protocolInitFailure in the hdsl2ShdslEndpointCurrStatus 2381 Expires October 2, 2001 Page [42] 2382 object for this endpoint has changed." 2383 ::= { hdsl2ShdslNotifications 14 } 2385 hdsl2ShdslnoNeighborPresent NOTIFICATION-TYPE 2386 OBJECTS 2387 { 2388 hdsl2ShdslEndpointCurrStatus 2389 } 2390 STATUS current 2391 DESCRIPTION 2392 "This notification indicates that the bit setting for 2393 noNeighborPresent in the hdsl2ShdslEndpointCurrStatus object 2394 for this endpoint has changed." 2395 ::= { hdsl2ShdslNotifications 15 } 2397 hdsl2ShdsllocalPowerLoss NOTIFICATION-TYPE 2398 OBJECTS 2399 { 2400 ifIndex, 2401 hdsl2ShdslInvIndex 2402 } 2403 STATUS current 2404 DESCRIPTION 2405 "This notification indicates impending unit failure due to 2406 loss of local power (last gasp)." 2407 ::= { hdsl2ShdslNotifications 16 } 2409 -- conformance information 2410 -- 2412 hdsl2ShdslConformance OBJECT IDENTIFIER ::= { hdsl2ShdslMIB 3 } 2413 hdsl2ShdslGroups OBJECT IDENTIFIER ::= { hdsl2ShdslConformance 1 } 2414 hdsl2ShdslCompliances OBJECT IDENTIFIER ::= { hdsl2ShdslConformance 2 } 2416 -- agent compliance statements 2418 hdsl2ShdslLineMibCompliance MODULE-COMPLIANCE 2419 STATUS current 2420 DESCRIPTION 2421 "The section outlines compliance requirements for this MIB." 2422 MODULE 2423 MANDATORY-GROUPS 2424 { 2425 hdsl2ShdslSpanConfGroup, 2426 hdsl2ShdslSpanStatusGroup, 2427 hdsl2ShdslInventoryGroup, 2428 hdsl2ShdslEndpointConfGroup, 2429 hdsl2ShdslEndpointCurrGroup, 2430 hdsl2Shdsl15MinIntervalGroup, 2431 hdsl2Shdsl1DayIntervalGroup, 2432 hdsl2ShdslMaintenanceGroup, 2433 hdsl2ShdslEndpointAlarmConfGroup, 2434 hdsl2ShdslNotificationGroup 2435 } 2437 Expires October 2, 2001 Page [43] 2438 GROUP hdsl2ShdslInventoryShdslGroup 2439 DESCRIPTION 2440 "Support for this group is only required for implementations 2441 supporting SHDSL lines." 2443 GROUP hdsl2ShdslSpanShdslStatusGroup 2444 DESCRIPTION 2445 "Support for this group is only required for implementations 2446 supporting SHDSL lines." 2448 GROUP hdsl2ShdslSpanConfProfileGroup 2449 DESCRIPTION 2450 "Support for this group is only required for implementations 2451 supporting SHDSL lines." 2453 ::= { hdsl2ShdslCompliances 1 } 2455 -- units of conformance 2456 -- 2458 hdsl2ShdslSpanConfGroup OBJECT-GROUP 2459 OBJECTS 2460 { 2461 hdsl2ShdslSpanConfNumRepeaters, 2462 hdsl2ShdslSpanConfProfile, 2463 hdsl2ShdslSpanConfAlarmProfile 2464 } 2465 STATUS current 2466 DESCRIPTION 2467 "This group supports objects for configuring span related 2468 parameters for HDSL2/SHDSL lines." 2469 ::= { hdsl2ShdslGroups 1 } 2471 hdsl2ShdslSpanStatusGroup OBJECT-GROUP 2472 OBJECTS 2473 { 2474 hdsl2ShdslStatusNumAvailRepeaters 2475 } 2476 STATUS current 2477 DESCRIPTION 2478 "This group supports objects for retrieving span related 2479 status for HDSL2/SHDSL lines." 2480 ::= { hdsl2ShdslGroups 2 } 2482 hdsl2ShdslInventoryShdslGroup OBJECT-GROUP 2483 OBJECTS 2484 { 2485 hdsl2ShdslInvTransmissionModeCapability 2486 } 2487 STATUS current 2488 DESCRIPTION 2489 "This group supports objects for retrieving SHDSL-specific 2490 inventory information." 2491 ::= { hdsl2ShdslGroups 3 } 2493 Expires October 2, 2001 Page [44] 2494 hdsl2ShdslSpanShdslStatusGroup OBJECT-GROUP 2495 OBJECTS 2496 { 2497 hdsl2ShdslStatusMaxAttainableLineRate, 2498 hdsl2ShdslStatusActualLineRate, 2499 hdsl2ShdslStatusTransmissionModeCurrent 2500 } 2501 STATUS current 2502 DESCRIPTION 2503 "This group supports objects for retrieving SHDSL-specific 2504 span related status." 2505 ::= { hdsl2ShdslGroups 4 } 2507 hdsl2ShdslInventoryGroup OBJECT-GROUP 2508 OBJECTS 2509 { 2510 hdsl2ShdslInvIndex, 2511 hdsl2ShdslInvVendorID, 2512 hdsl2ShdslInvVendorModelNumber, 2513 hdsl2ShdslInvVendorSerialNumber, 2514 hdsl2ShdslInvVendorEOCSoftwareVersion, 2515 hdsl2ShdslInvStandardVersion, 2516 hdsl2ShdslInvVendorListNumber, 2517 hdsl2ShdslInvVendorIssueNumber, 2518 hdsl2ShdslInvVendorSoftwareVersion, 2519 hdsl2ShdslInvEquipmentCode, 2520 hdsl2ShdslInvVendorOther 2521 } 2522 STATUS current 2523 DESCRIPTION 2524 "This group supports objects that provide unit inventory 2525 information about the units in HDSL2/SHDSL lines." 2526 ::= { hdsl2ShdslGroups 5 } 2528 hdsl2ShdslEndpointConfGroup OBJECT-GROUP 2529 OBJECTS 2530 { 2531 hdsl2ShdslEndpointSide, 2532 hdsl2ShdslEndpointWirePair, 2533 hdsl2ShdslEndpointAlarmConfProfile 2534 } 2535 STATUS current 2536 DESCRIPTION 2537 "This group supports objects for configuring parameters for 2538 segment endpoints in HDSL2/SHDSL lines." 2539 ::= { hdsl2ShdslGroups 6 } 2541 hdsl2ShdslEndpointCurrGroup OBJECT-GROUP 2542 OBJECTS 2543 { 2544 hdsl2ShdslEndpointSide, 2545 hdsl2ShdslEndpointWirePair, 2546 hdsl2ShdslEndpointCurrAtn, 2547 hdsl2ShdslEndpointCurrSnrMgn, 2548 hdsl2ShdslEndpointCurrStatus, 2550 Expires October 2, 2001 Page [45] 2551 hdsl2ShdslEndpointES, 2552 hdsl2ShdslEndpointSES, 2553 hdsl2ShdslEndpointCRCanomalies, 2554 hdsl2ShdslEndpointLOSWS, 2555 hdsl2ShdslEndpointUAS, 2556 hdsl2ShdslEndpointCurr15MinTimeElapsed, 2557 hdsl2ShdslEndpointCurr15MinES, 2558 hdsl2ShdslEndpointCurr15MinSES, 2559 hdsl2ShdslEndpointCurr15MinCRCanomalies, 2560 hdsl2ShdslEndpointCurr15MinLOSWS, 2561 hdsl2ShdslEndpointCurr15MinUAS, 2562 hdsl2ShdslEndpointCurr1DayTimeElapsed, 2563 hdsl2ShdslEndpointCurr1DayES, 2564 hdsl2ShdslEndpointCurr1DaySES, 2565 hdsl2ShdslEndpointCurr1DayCRCanomalies, 2566 hdsl2ShdslEndpointCurr1DayLOSWS, 2567 hdsl2ShdslEndpointCurr1DayUAS 2568 } 2569 STATUS current 2570 DESCRIPTION 2571 "This group supports objects which provide current status and 2572 performance measurements relating to segment endpoints in 2573 HDSL2/SHDSL lines." 2574 ::= { hdsl2ShdslGroups 7 } 2576 hdsl2Shdsl15MinIntervalGroup OBJECT-GROUP 2577 OBJECTS 2578 { 2579 hdsl2Shdsl15MinIntervalES, 2580 hdsl2Shdsl15MinIntervalSES, 2581 hdsl2Shdsl15MinIntervalCRCanomalies, 2582 hdsl2Shdsl15MinIntervalLOSWS, 2583 hdsl2Shdsl15MinIntervalUAS 2584 } 2585 STATUS current 2586 DESCRIPTION 2587 "This group supports objects which maintain historic 2588 performance measurements relating to segment endpoints in 2589 HDSL2/SHDSL lines in 15-minute intervals." 2590 ::= { hdsl2ShdslGroups 8 } 2592 hdsl2Shdsl1DayIntervalGroup OBJECT-GROUP 2593 OBJECTS 2594 { 2595 hdsl2Shdsl1DayIntervalMoniSecs, 2596 hdsl2Shdsl1DayIntervalES, 2597 hdsl2Shdsl1DayIntervalSES, 2598 hdsl2Shdsl1DayIntervalCRCanomalies, 2599 hdsl2Shdsl1DayIntervalLOSWS, 2600 hdsl2Shdsl1DayIntervalUAS 2601 } 2602 STATUS current 2603 DESCRIPTION 2604 "This group supports objects which maintain historic 2605 performance measurements relating to segment endpoints in 2607 Expires October 2, 2001 Page [46] 2608 HDSL2/SHDSL lines in 1-day intervals." 2609 ::= { hdsl2ShdslGroups 9 } 2611 hdsl2ShdslMaintenanceGroup OBJECT-GROUP 2612 OBJECTS 2613 { 2614 hdsl2ShdslMaintLoopbackConfig, 2615 hdsl2ShdslMaintTipRingReversal, 2616 hdsl2ShdslMaintPowerBackOff, 2617 hdsl2ShdslMaintSoftRestart, 2618 hdsl2ShdslMaintLoopbackTimeout, 2619 hdsl2ShdslMaintUnitPowerSource 2620 } 2621 STATUS current 2622 DESCRIPTION 2623 "This group supports objects that provide support for 2624 maintenance actions for HDSL2/SHDSL lines." 2625 ::= { hdsl2ShdslGroups 10 } 2627 hdsl2ShdslEndpointAlarmConfGroup OBJECT-GROUP 2628 OBJECTS 2629 { 2630 hdsl2ShdslEndpointThreshLoopAttenuation, 2631 hdsl2ShdslEndpointThreshSNRMargin, 2632 hdsl2ShdslEndpointThreshES, 2633 hdsl2ShdslEndpointThreshSES, 2634 hdsl2ShdslEndpointThreshCRCanomalies, 2635 hdsl2ShdslEndpointThreshLOSWS, 2636 hdsl2ShdslEndpointThreshUAS, 2637 hdsl2ShdslEndpointAlarmConfProfileRowStatus 2638 } 2639 STATUS current 2640 DESCRIPTION 2641 "This group supports objects that allow configuration of alarm 2642 thresholds for various performance parameters for HDSL2/SHDSL 2643 lines." 2644 ::= { hdsl2ShdslGroups 11 } 2646 hdsl2ShdslNotificationGroup NOTIFICATION-GROUP 2647 NOTIFICATIONS 2648 { 2649 hdsl2ShdslLoopAttenCrossing, 2650 hdsl2ShdslSNRMarginCrossing, 2651 hdsl2ShdslPerfESThresh, 2652 hdsl2ShdslPerfSESThresh, 2653 hdsl2ShdslPerfCRCanomaliesThresh, 2654 hdsl2ShdslPerfLOSWSThresh, 2655 hdsl2ShdslPerfUASThresh, 2656 hdsl2ShdslSpanInvalidNumRepeaters, 2657 hdsl2ShdslLoopbackFailure, 2658 hdsl2ShdslpowerBackoff, 2659 hdsl2ShdsldeviceFault, 2660 hdsl2ShdsldcContinuityFault, 2661 hdsl2ShdslconfigInitFailure, 2662 hdsl2ShdslprotocolInitFailure, 2664 Expires October 2, 2001 Page [47] 2665 hdsl2ShdslnoNeighborPresent, 2666 hdsl2ShdsllocalPowerLoss 2667 } 2668 STATUS current 2669 DESCRIPTION 2670 "This group supports notifications of significant events/ 2671 conditions associated with HDSL2/SHDSL lines." 2672 ::= { hdsl2ShdslGroups 12 } 2674 hdsl2ShdslSpanConfProfileGroup OBJECT-GROUP 2675 OBJECTS 2676 { 2677 hdsl2ShdslSpanConfWireInterface, 2678 hdsl2ShdslSpanConfMinLineRate, 2679 hdsl2ShdslSpanConfMaxLineRate, 2680 hdsl2ShdslSpanConfPSD, 2681 hdsl2ShdslSpanConfTransmissionMode, 2682 hdsl2ShdslSpanConfRemoteEnabled, 2683 hdsl2ShdslSpanConfPowerFeeding, 2684 hdsl2ShdslSpanConfCurrCondTargetMarginDown, 2685 hdsl2ShdslSpanConfWorstCaseTargetMarginDown, 2686 hdsl2ShdslSpanConfCurrCondTargetMarginUp, 2687 hdsl2ShdslSpanConfWorstCaseTargetMarginUp, 2688 hdsl2ShdslSpanConfUsedTargetMargins, 2689 hdsl2ShdslSpanConfProfileRowStatus 2690 } 2691 STATUS current 2692 DESCRIPTION 2693 "This group supports objects that constitute configuration 2694 profiles for configuring span related parameters in SHDSL 2695 lines." 2696 ::= { hdsl2ShdslGroups 13 } 2698 END 2700 7. Security Considerations 2702 There are a number of management objects defined in this MIB that 2703 have a MAX-ACCESS clause of read-write and/or read-create. Such 2704 objects may be considered sensitive or vulnerable in some network 2705 environments. The support for SET operations in a non-secure 2706 environment without proper protection can have a negative effect on 2707 network operations. 2709 No managed objects in this MIB contain sensitive information. 2711 SNMPv1 by itself is not a secure environment. Even if the network 2712 itself is secure (for example by using IPSec), even then, there is no 2713 control as to who on the secure network is allowed to access and 2714 GET/SET (read/change/create/delete) the objects in this MIB. 2716 It is recommended that the implementers consider the security 2717 features as provided by the SNMPv3 framework. Specifically, the use 2718 of the User-based Security Model RFC 2574 [12] and the View- 2719 based Access Control Model RFC 2575 [15] is recommended. 2721 Expires October 2, 2001 Page [48] 2722 It is then a customer/user responsibility to ensure that the SNMP 2723 entity giving access to an instance of this MIB, is properly 2724 configured to give access to the objects only to those principals 2725 (users) that have legitimate rights to indeed GET or SET 2726 (change/create/delete) them. 2728 8. Acknowledgments 2730 The authors are deeply grateful to the authors of the ADSL LINE MIB 2731 (RFC 2662 [23]), Gregory Bathrick and Faye Ly, as much of the text 2732 and structure of this document originates in their documents. 2734 The authors are also grateful to the authors of FR MFR MIB (RFC 3020 2735 [24]), Prayson Pate, Bob Lynch, and Kenneth Rehbehn, as the entirety 2736 of the Security Considerations section was lifted from their document. 2738 The authors also acknowledge the importance of contributions and 2739 suggestions regarding interface indexing structures received from 2740 David Horton of CITR. 2742 Other contributions were received from the following: 2744 Philip Bergstresser (Adtran) 2746 Steve Blackwell (Centillium) 2748 Umberto Bonollo (NEC Australia) 2750 Mark Johnson (Red Point) 2752 Sharon Mantin (Orckit) 2754 Moti Morgenstern (ECI) 2756 Raymond Murphy (Ericsson) 2758 Lee Nipper (Verilink) 2760 Katy Sherman (Orckit) 2762 Mike Sneed (ECI) 2764 Jon Turney (DSL Solutions) 2766 Aron Wahl (Memotec) 2768 Michael Wrobel (Memotec) 2770 9. References 2772 [1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 2773 Describing SNMP Management Frameworks", RFC 2571, April 1999. 2775 [2] Rose, M., and K. McCloghrie, "Structure and Identification of 2777 Expires October 2, 2001 Page [49] 2778 Management Information for TCP/IP-based Internets", STD 16, RFC 2779 1155, May 1990. 2781 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 16, 2782 RFC 1212, March 1991. 2784 [4] M. Rose, "A Convention for Defining Traps for use with the SNMP", 2785 RFC 1215, March 1991. 2787 [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 2788 M., and S. Waldbusser, "Structure of Management Information 2789 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 2791 [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 2792 M., and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, 2793 RFC 2579, April 1999. 2795 [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 2796 M., and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, 2797 RFC 2580, April 1999. 2799 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 2800 Network Management Protocol", STD 15, RFC 1157, May 1990. 2802 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2803 "Introduction to Community-based SNMPv2", RFC 1901, January 2804 1996. 2806 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport 2807 Mappings for Version 2 of the Simple Network Management Protocol 2808 (SNMPv2)", RFC 1906, January 1996. 2810 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 2811 Processing and Dispatching for the Simple Network Management 2812 Protocol (SNMP)", RFC 2572, April 1999. 2814 [12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) 2815 for version 3 of the Simple Network Management Protocol (SNMPv3)", 2816 RFC 2574, April 1999. 2818 [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 2819 Operations for Version 2 of the Simple Network Management Protocol 2820 (SNMPv2)", RFC 1905, January 1996. 2822 [14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 2823 2573, April 1999. 2825 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 2826 Control Model (VACM) for the Simple Network Management Protocol 2827 (SNMP)", RFC 2575, April 1999. 2829 [16] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction to 2830 Version 3 of the Internet-standard Network Management Framework", 2831 RFC 2570, April 1999. 2833 Expires October 2, 2001 Page [50] 2834 [17] Bradner, S., "Key Words for use in RFCs to Indicate Requirement 2835 Levels", RFC 2119, March 1997. 2837 [18] American National Standards Institute, ANSI T1E1.4/2000-006, 2838 February 2000. 2840 [19] Blackwell, S., Editor, "Single-Pair High-Speed Digital Subscriber 2841 Line (SHDSL) Transceivers", ITU-T Draft G.991.2, April 2000. 2843 [20] McCloghrie, K., and M. Rose, Editors, "Management Information Base 2844 for Network Management of TCP/IP-based internets: MIB-II", STD 17, 2845 RFC 1213, March 1991. 2847 [21] McCloghrie, K., and Kastenholz, F., "The Interfaces Group MIB", 2848 RFC 2863, June 2000. 2850 [22] Tesink, K., "Textual Conventions for MIB Modules Using Performance 2851 History Based on 15 Minute Intervals", RFC 2493, January 1999. 2853 [23] Bathrick, G., Ly, F., "Definitions of Managed Objects for the ADSL 2854 Lines", RFC 2662, August 1999. 2856 [24] Pate, P., Lynch, B., Rehbehn, K., "Definitions of Managed Objects 2857 for Monitoring and Controlling the UNI/NNI Multilink Frame Relay 2858 Function", RFC 3020, December 2000. 2860 10. Intellectual Property Notice 2862 The IETF takes no position regarding the validity or scope of any 2863 intellectual property or other rights that might be claimed to 2864 pertain to the implementation or use of the technology described in 2865 this document or the extent to which any license under such rights 2866 might or might not be available; neither does it represent that it 2867 has made any effort to identify any such rights. Information on the 2868 IETF's procedures with respect to rights in standards-track and 2869 standards-related documentation can be found in BCP-11. Copies of 2870 claims of rights made available for publication and any assurances of 2871 licenses to be made available, or the result of an attempt made to 2872 obtain a general license or permission for the use of such 2873 proprietary rights by implementors or users of this specification can 2874 be obtained from the IETF Secretariat. 2876 The IETF invites any interested party to bring to its attention any 2877 copyrights, patents or patent applications, or other proprietary 2878 rights which may cover technology that may be required to practice 2879 this standard. Please address the information to the IETF Executive 2880 Director. 2882 11. Authors' Addresses 2884 Rajesh Abbi 2885 Alcatel USA 2886 2912 Wake Forest Road 2887 Raleigh, NC 27609-7860 USA 2888 Tel: +1 919-950-6194 2890 Expires October 2, 2001 Page [51] 2891 Fax: +1 919-950-6670 2892 E-mail: Rajesh.Abbi@usa.alcatel.com 2894 Bob Ray 2895 Verilink Corporation 2896 950 Explorer Blvd 2897 Huntsville, AL 35806 USA 2898 Tel: +1 256-327-2380 2899 Fax: +1 256-327-2880 2900 E-mail: bray@verilink.com 2902 12. Full Copyright Statement 2904 Copyright (C) The Internet Society (1999). All Rights Reserved. 2906 This document and translations of it may be copied and furnished to 2907 others, and derivative works that comment on or otherwise explain it 2908 or assist in its implementation may be prepared, copied, published 2909 and distributed, in whole or in part, without restriction of any 2910 kind, provided that the above copyright notice and this paragraph are 2911 included on all such copies and derivative works. However, this 2912 document itself may not be modified in any way, such as by removing 2913 the copyright notice or references to the Internet Society or other 2914 Internet organizations, except as needed for the purpose of 2915 developing Internet standards in which case the procedures for 2916 copyrights defined in the Internet Standards process must be 2917 followed, or as required to translate it into languages other than 2918 English. 2920 The limited permissions granted above are perpetual and will not be 2921 revoked by the Internet Society or its successors or assigns. 2922 This document and the information contained herein is provided on an 2923 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 2924 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 2925 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 2926 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 2927 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 2929 Expires October 2, 2001 Page [52]