idnits 2.17.1 draft-ietf-adslmib-hdsl2-06.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: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 1) being 59 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 858 has weird spacing: '... object will ...' -- 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 (November 2000) is 8556 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: '24' is mentioned on line 1329, but not defined == Missing Reference: '25' is mentioned on line 2603, but not defined == Missing Reference: '26' is mentioned on line 1437, but not defined == Missing Reference: '27' is mentioned on line 1491, but not defined == Missing Reference: '28' is mentioned on line 1545, but not defined == Missing Reference: '29' is mentioned on line 1599, but not defined == Missing Reference: '30' is mentioned on line 1653, but not defined == Missing Reference: '31' is mentioned on line 1707, but not defined == Missing Reference: '32' is mentioned on line 1761, but not defined == Missing Reference: '33' is mentioned on line 1815, but not defined == Missing Reference: '34' is mentioned on line 1869, but not defined == Missing Reference: '35' is mentioned on line 1923, but not defined == Missing Reference: '36' is mentioned on line 1976, but not defined == Missing Reference: '37' is mentioned on line 2030, but not defined == Missing Reference: '38' is mentioned on line 2084, but not defined == Missing Reference: '39' is mentioned on line 2138, but not defined == Missing Reference: '40' is mentioned on line 2192, but not defined == Missing Reference: '41' is mentioned on line 2246, but not defined == Missing Reference: '42' is mentioned on line 2300, but not defined == Missing Reference: '43' is mentioned on line 2353, but not defined == Missing Reference: '44' is mentioned on line 2407, but not defined == Missing Reference: '45' is mentioned on line 2461, but not defined == Missing Reference: '46' is mentioned on line 2516, but not defined == Missing Reference: '47' is mentioned on line 2570, but not defined == Missing Reference: '48' is mentioned on line 2624, but not defined == Missing Reference: '49' is mentioned on line 2679, but not defined == Missing Reference: '50' is mentioned on line 2733, but not defined == Missing Reference: '51' is mentioned on line 2786, but not defined ** Obsolete normative reference: RFC 2571 (ref. '1') (Obsoleted by RFC 3411) ** 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: 17 errors (**), 0 flaws (~~), 32 warnings (==), 4 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 November 2000 8 Definitions of Managed Objects for HDSL2 and SHDSL Lines 9 draft-ietf-adslmib-hdsl2-06.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 (2000). All Rights Reserved. 41 Expires May 21, 2001 Page [1] 42 Table of Contents 44 1. Abstract .................................................. 2 45 2. The SNMPv2 Network Management Framework ................... 2 46 3. Introduction .............................................. 3 47 3.1 Relationship of the MIB with Standard MIBs ................ 4 48 4. Conventions used in the MIB ............................... 5 49 4.1 Naming Conventions ........................................ 5 50 4.2 Textual Conventions ....................................... 5 51 4.3 Structure ................................................. 6 52 4.4 Counters, Interval Buckets and Thresholds ................. 9 53 4.5 Profiles .................................................. 9 54 4.6 Traps ..................................................... 11 55 5. Conformance and Compliance ................................ 12 56 6. Definitions ............................................... 12 57 7. Security Considerations ................................... 48 58 8. Acknowledgments ........................................... 48 59 9. References ................................................ 49 60 10. Intellectual Property Notice .............................. 50 61 11. Authors' Addresses ........................................ 51 62 12. Full Copyright Statement .................................. 51 64 1. Abstract 66 This document defines an experimental portion of the Management 67 Information Base (MIB) MIB module for use with network management 68 protocols in the Internet community. In particular, it describes 69 objects used for managing HDSL2 and SHDSL interfaces. 71 This document specifies a MIB module in a manner that is both compliant 72 to the SNMPv2 SMI, and semantically identical to the peer SNMPv1 73 definitions. 75 2. The SNMP Management Framework 77 The SNMP Management Framework presently consists of five major 78 components: 80 o An overall architecture, described in RFC 2571 [1]. 82 o Mechanisms for describing and naming objects and events for the 83 purpose of management. The first version of this Structure of 84 Management Information (SMI) is called SMIv1 and described in 85 STD 16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4]. 86 The second version, called SMIv2, is described in STD 58, RFC 87 2578 [5], STD 58, RFC 2579 [6] and STD 58, RFC 2580 [7]. 89 o Message protocols for transferring management information. The 90 first version of the SNMP message protocol is called SNMPv1 and 91 described in STD 15, RFC 1157 [8]. A second version of the SNMP 92 message protocol, which is not an Internet standards track 93 protocol, is called SNMPv2c and described in RFC 1901 [9] and 95 Expires May 21, 2001 Page [2] 96 RFC 1906 [10]. The third version of the message protocol is 97 called SNMPv3 and described in RFC 1906 [10], RFC 2572 [11] and 98 RFC 2574 [12]. 100 o Protocol operations for accessing management information. The 101 first set of protocol operations and associated PDU formats is 102 described in STD 15, RFC 1157 [8]. A second set of protocol 103 operations and associated PDU formats is described in RFC 1905 104 [13]. 106 o A set of fundamental applications described in RFC 2573 [14] 107 and the view-based access control mechanism described in RFC 108 2575 [15]. 110 A more detailed introduction to the current SNMP Management Framework 111 can be found in RFC 2570 [16]. 113 Managed objects are accessed via a virtual information store, termed 114 the Management Information Base or MIB. Objects in the MIB are 115 defined using the mechanisms defined in the SMI. 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 2.1. Object Definitions 133 Managed objects are accessed via a virtual information store, termed 134 the Management Information Base or MIB. Objects in the MIB are 135 defined using the subset of Abstract Syntax Notation One (ASN.1) 136 defined in the SMI. In particular, each object type is named by an 137 OBJECT IDENTIFIER, an administratively assigned name. The object 138 type together with an object instance serves to uniquely identify a 139 specific instantiation of the object. For human convenience, we 140 often use a textual string, termed the descriptor, to also refer to 141 the object type. 143 3. Introduction 145 This document describes an SNMP MIB for managing HDSL2/SHDSL Lines. 146 The MIB is intended to be compatible with both the SNMPv1 and SNMPv2. 147 These definitions are based upon the specifications for the HDSL2 and 149 Expires May 21, 2001 Page [2] 150 SHDSL Embedded Operations Channel (EOC) as defined in ANSI 151 T1E1.4/2000-006 [18] and ITU G.991.2 (ex G.SHDSL) [19]. 153 The MIB will eventually be located in the MIB tree under MIB 2 154 transmission, as discussed in the MIB-2 Integration (RFC 1213 [20] and 155 RFC 2863 [21]) section of this document. Until approved by the IETF, 156 vendors may also choose to support it under the experimental tree. 158 NOTE TO RFC EDITOR: please replace the above paragraph with the 159 following paragraph when appropriate: 161 The MIB is located in the MIB tree under MIB-2 transmission, as 162 discussing in the MIB-2 Integration (RFC 1213 [20] and RFC 2863 [21]) 163 section of this document. 165 3.1. Relationship of the HDSL2/SHDSL Line MIB with Standard MIBs 167 This section outlines the relationship of this MIB with other MIBs 168 described in RFCs and in various degrees of "standardization". 169 Specifically, MIB-2 as presented in RFC 1213 [20] and RFC 2863 [21] 170 is discussed. 172 3.1.1 General MIB-2 Integration (RFCs 1213 and 2863) 174 The HDSL2/SHDSL Line MIB specifies the detailed attributes of a data 175 interface. As such, it needs to integrate with RFC 2863 [21]. The 176 IANA has assigned the following ifTypes to HDSL2 and SHDSL: 178 IANAifType ::= TEXTUAL-CONVENTION 179 ... 180 SYNTAX INTEGER { 181 ... 182 hdsl2 (168), -- High Bit-Rate DSL, 2nd generation 183 shdsl (169), -- Multirate HDSL2 184 ... 185 } 187 This MIB will be accessed through the transmission subtree as shown: 189 hdsl2ShdslInterface ::= { transmission xxx } 190 NOTE TO RFC EDITOR: please replace the xxx with an assigned number 192 3.1.2 Usage of ifTable 194 The MIB branch identified by this ifType contains tables appropriate 195 for this interface type. Most such tables extend the ifEntry table, 196 and are indexed by ifIndex. 198 The following attributes are part of the mandatory ifGeneral group in 199 RFC 2863 [21], and are not duplicated in the HDSL2/SHDSL Line MIB. 201 Expires May 21, 2001 Page [3] 202 =================================================================== 203 ifIndex Interface index. 205 ifDescr See interfaces MIB [21]. 207 ifType hdsl2(168) or shdsl(169). 209 ifSpeed Set as appropriate. 210 (This is fixed at 1552000 for HDSL2 lines) 212 ifPhysAddress This object should have an octet string 213 with zero length. 215 ifAdminStatus See interfaces MIB [21]. 217 ifOperStatus See interfaces MIB [21]. 219 ifLastChange See interfaces MIB [21]. 221 ifName See interfaces MIB [21]. 223 ifLinkUpDownTrapEnable Default to enabled(1). 225 ifHighSpeed Set as appropriate. 226 (For HDSL2 lines, this is fixed at 2) 228 ifConnectorPresent Set as appropriate. 229 =================================================================== 230 Figure 1: Use of ifTable Objects 232 4. Conventions used in the MIB 234 4.1. Naming Conventions 236 A. xtuC refers to a central site terminal unit; 237 H2TU-C for HDSL2, or STU-C for SHDSL. 238 B. xtuR refers to a remote site terminal unit; 239 H2TU-R for HDSL2, or STU-R for SHDSL. 240 C. xtu refers to a terminal unit; either an xtuC or xtuR. 241 D. xru refer to a regenerator unit; 242 H2RU for HDSL2, or SRU for SHDSL. 243 E. xU refers to any HDSL2/SHDSL unit; either an xtu or xru. 244 F. CRC is cyclic redundancy check. 245 G. ES means errored second. 246 H. LOS means loss of signal. 247 I. LOSS means loss of signal second. 248 J. LOSW means loss of sync word, distinct from LOS. 249 K. LOSWS means LOSW second. 250 L. SES means severely errored second. 251 M. SNR means signal-to-noise ratio. 252 N. UAS means unavailable second. 254 Expires May 21, 2001 Page [4] 255 4.2. Textual Conventions 257 The following textual conventions are defined to reflect the line 258 topology in the MIB (further discussed is the following section) 259 and to define the behaviour of the statistics to be maintained 260 by an agent. 262 o Hdsl2ShdslUnitId : 263 This attribute uniquely identifies each unit in a HDSL2/SHDSL span. 264 It mirrors the EOC addressing mechanism: 266 xtuC(1) - CO terminal unit 267 xtuR(2) - CPE terminal unit 268 xru1(3) .. xru8(10) - regenerators, numbered from 269 central office side 271 o Hdsl2ShdslUnitSide: 272 This attribute references the two sides of a unit: 274 networkSide(1) - N in figure 2, below 275 customerSide(2) - C in figure 2, below 277 o Hdsl2ShdslWirePair: 278 This attribute references the wire-pairs connecting the units: 280 wirePair1(1) - First pair for HDSL2/SHDSL. 281 wirePair2(2) - Optional second pair for SHDSL only. 283 o Hdsl2ShdslTransmissionModeType: 284 This attribute specifies the regional setting for a SHDSL line. 285 Specified as a bit-map, the three mode type are: 287 region1 - ITU-T G.991.2 Annex A 288 region2 - ITU-T G.991.2 Annex B 289 region3 - ITU-T G.991.2 Annex C 291 o Hdsl2ShdslPerfCurrDayCount: 293 This attribute defines the behaviour of the 1-day (24 hour) 294 gauges found in the MIB. 296 o Hdsl2Shdsl1DayIntervalCount: 298 This attribute defines the behaviour of the 1-day (24 hour) 299 interval counters found in the MIB. 301 o Hdsl2ShdslPerfTimeElapsed: 303 This attribute defines the behaviour of the elapsed time counters 304 found in the MIB. 306 o Hdsl2ShdslPerfIntervalThreshold: 308 Expires May 21, 2001 Page [5] 309 This attribute defines the behaviour of the alarm thresholds found 310 in the MIB. 312 4.3. Structure 314 The MIB is structured into following MIB groups: 316 o Span Configuration Group: 318 This group supports MIB objects for configuring parameters for 319 the HDSL2/SHDSL span. It contains the following table(s): 321 - hdsl2ShdslSpanConfTable 323 o Span Status Group: 325 This group supports MIB objects for retrieving span status 326 information. It contains the following table(s): 328 - hdsl2ShdslSpanStatusTable 330 o Unit Inventory Group: 332 This group supports MIB objects for retrieving unit inventory 333 information about units in HDSL2/SHDSL lines via the EOC. It 334 contains the following table(s): 336 - hdsl2ShdslInventoryTable 338 o Segment Endpoint Configuration Group: 340 This group supports MIB objects for configuring parameters for 341 the HDSL2/SHDSL segment endpoints. It contains the following 342 table(s): 344 - hdsl2ShdslEndpointConfTable 346 o Segment Endpoint Current Status/Performance Group: 348 This group supports MIB objects that provide the current 349 status/performance information relating to segment endpoints. 350 It contains the following table(s): 352 - hdsl2ShdslEndpointCurrTable 354 o Segment Endpoint 15-Minute Interval Status/Performance Group: 356 This group supports MIB objects that provide historic 357 status/performance information relating to segment endpoints 358 in 15-minute intervals. It contains the following table(s): 360 - hdsl2Shdsl15MinIntervalTable 362 Expires May 21, 2001 Page [6] 363 o Segment Endpoint 1-Day Interval Status/Performance Group: 365 This group supports MIB objects that provide historic 366 status/performance information relating to segment endpoints 367 in 1-day intervals. It contains the following table(s): 369 - hdsl2Shdsl1DayIntervalTable 371 o Maintenance Group: 373 This group supports MIB objects for performing maintenance 374 operations such as loopbacks for HDSL2/SHDSL lines. It contains 375 the following table(s): 377 - hdsl2ShdslEndpointMaintTable 378 - hdsl2ShdslUnitMaintTable 380 o Span Configuration Profile Group: 382 This group supports MIB objects for defining configuration profiles 383 for HDSL2/SHDSL Spans. It contains the following table(s): 385 - hdsl2ShdslSpanConfProfileTable 387 o Segment Endpoint Alarm Configuration Profile Group: 389 This group supports MIB objects for defining alarm configuration 390 profiles for HDSL2/SHDSL Segment Endpoints. It contains the 391 following table(s): 393 - hdsl2ShdslEndpointAlarmConfProfileTable 395 o Notifications Group: 397 This group defines Notiofication messages supported for HDSL2/ 398 SHDSL lines. It defines the following notifications: 400 - hdsl2ShdslLoopAttenCrossingTrap 401 - hdsl2ShdslSNRMarginCrossingTrap 402 - hdsl2ShdslPerfESThreshTrap 403 - hdsl2ShdslPerfSESThreshTrap 404 - hdsl2ShdslPerfCRCanomaliesThreshTrap 405 - hdsl2ShdslPerfLOSWSThreshTrap 406 - hdsl2ShdslPerfUASThreshTrap 407 - hdsl2ShdslSpanInvalidNumRepeaters 408 - hdsl2ShdslLoopbackFailure 410 4.3.1 Line Topology 412 An HDSL2/SHDSL Line consists of a minimum of two units - xtuC (the 413 central termination unit) and an xtuR (the remote termination unit). 414 The line may optionally support up to 8 repeater/regenerator units 415 (xru) as shown in the figure below. 417 Expires May 21, 2001 Page [7] 418 <-- Network Side Customer Side --> 420 || 422 <~~~> <~~~> HDSL2/SHDSL Segments <~~~> 424 +-------+ +-------+ +-------+ +-------+ +-------+ 425 + C=1=N C=1=N C=..1..=N C=1=N + 426 | xtuC | | xru1 | | xru2 | | xru8 | | xtuR | 427 + C=2=N C=2=N C=..2..=N C=2=N + 428 +-------+ +-------+ +-------+ +-------+ +-------+ 430 Key: HDSL2/SHDSL Span 431 <~~~~> HDSL2/SHDSL Segment 432 1= HDSL2/SHDSL wire-pair-1 433 =2= SHDSL optional wire-pair-2 (Not applicable to HDSL2) 434 C Customer Side Segment Endpoint (modem) 435 N Network Side Segment Endpoint (modem) 437 Figure 2: General topology for an HDSL2/SHDSL Line 439 4.4. Counters, Interval Buckets and Thresholds 441 For SNR Margin, Loop Attenuation, ES, SES, CRC anomalies, LOSWS, and 442 UAS, there are event counters, current 15-minute and one (up to 96) 443 15-minute history bucket(s) of "interval-counters", as well as 444 current and one (up to 30) previous 1-day interval-counter(s). Each 445 current 15-minute event bucket has an associated threshold trap. 447 Unlike RFC 2493 [22] and RFC 2662 [23], there is no representation 448 in the MIB for invalid buckets. In those cases where the data for 449 an interval is suspect or known to be invalid, the agent should 450 not report the interval. 452 There is no requirement for an agent to ensure a fixed relationship 453 between the start of a fifteen minute and any wall clock; however 454 some implementations may align the fifteen minute intervals with 455 quarter hours. Likewise, an implementation may choose to align one 456 day intervals with the start of a day. 458 Counters are not reset when an xU is reinitialized, only when the 459 agent is reset or reinitialized (or under specific request outside 460 the scope of this MIB). 462 4.5. Profiles 464 As a managed node can handle a large number of xUs, (e.g., hundreds 465 or perhaps thousands of lines), provisioning every parameter on every 466 xU may become burdensome. Moreover, most lines are provisioned 467 identically; with the same set of parameters. To simplify the 468 provisioning process, this MIB makes use of profiles. A profile is a 470 Expires May 21, 2001 Page [8] 471 set of parameters that can be shared by multiple lines using the same 472 configuration. 474 The following profiles are used in this MIB: 476 o Span Configuration Profiles - Span configuration profiles contain 477 parameters for configuring HDSL2/SHDSL spans. They are defined in 478 the hdsl2ShdslSpanConfProfileTable. Since span configuration 479 parameters are only applicable for SHDSL, the support for span 480 configuration profiles is optional for HDSL2 interfaces. 482 Note that the configuration of the span dictates the behavior for 483 each individual segment end point in the span. If a different 484 configuration is provisioned for any given segment end point within 485 the span, however, the new configuraiton for this segment end point 486 will override the span configuration for this segment end point only. 488 o Segment Endpoint Alarm Configuration Profiles - These profiles 489 contain parameters for configuring alarm thresholds for HDSL2/ 490 SHDSL segment endpoints. These profiles are defined in the 491 hdsl2ShdslEndpointAlarmConfProfileTable. 493 Implementations will enable the manager to dynamically create and 494 delete profiles as needed. The index of each profile is a locally- 495 unique administratively assigned name for the profile having the 496 textual convention `SnmpAdminString' (RFC 2571 [1]). 498 One or more lines may be configured to share parameters of a single 499 profile (e.g., hdsl2ShdslEndpointAlarmConfProfile = `silver') by 500 setting its hdsl2ShdslEndpointAlarmConfProfile objects to the value of 501 this profile. If a change is made to the profile, all lines that refer 502 to it will be reconfigured to the changed parameters. Before a profile 503 can be deleted or taken out of service it must be first unreferenced 504 from all associated lines. 506 Implementations must provide a default profile whose name is `DEFVAL' 507 for each profile type. The values of the associated parameters will be 508 vendor specific unless otherwise indicated in this document. Before a 509 line's profiles have been set, these profiles will be automatically 510 used by setting hdsl2ShdslEndpointAlarmConfProfile and 511 hdsl2ShdslSpanConfProfile to `DEFVAL' where appropriate. 513 Profiles are created, assigned, and deleted dynamically using the 514 profile name and profile row status in each of the four profile tables. 516 Profile changes MUST take effect immediately. These changes MAY result 517 in a restart (hard reset or soft restart) of the units on the line. 519 4.6. Traps 521 The ability to generate the SNMP traps coldStart/WarmStart (per [21]) 522 which are per agent (e.g., per DSLAM in such a device), and linkUp / 524 Expires May 21, 2001 Page [9] 525 linkDown (per [21]) -- which are per interface (i.e., HDSL2/SHDSL line) 526 is required. 528 A linkDown trap may be generated whenever any of ES, SES, CRC Anomaly, 529 LOSWS, or UAS event occurs. At this operational point, a manager can 530 use hdsl2ShdslEndpointCurrStatus for additional detailed information. 531 The corresponding linkUp trap MAY be sent when all link failure 532 conditions are cleared. 534 The traps defined in this MIB are for initialization failure and for 535 the threshold crossings associated with the following events: ES, SES, 536 CRC Anomaly, LOSWS, and UAS. Each threshold has its own 537 enable/threshold value. When that value is 0, the trap is disabled. 539 The hdsl2ShdslEndpointCurrStatus is a bitmask representing all 540 outstanding error conditions associated with a particular Segment 541 Endpoint. Note that since status of remote endpoints is obtained via 542 the EOC, this information may be unavailable for units that are 543 unreachable via EOC during a line error condition. Therefore, not all 544 conditions may always be included in its current status. 546 Two alarm conditions, SNR Margin Alarm and Loop Attenuation Alarm, 547 are organized in a manner slightly different from that implied in 548 the EOC specifications. In the MIB, these alarm conditions are 549 tied to the two thresholds hdsl2ShdslEndpointThreshSNRMargin and 550 hdsl2ShdslEndpointThreshLoopAttenuation found in the 551 hdsl2ShdslEndpointAlarmConfProfileTable. In the EOC, the alarm 552 conditions associated with these thresholds are per-unit. In the 553 MIB, these alarm conditions are per-endpoint. For terminal units, 554 this has no impact. For repeaters, this implies an implementation 555 variance where the agent in the terminal unit is responsible for 556 detecting a threshold crossing. As the reporting of a repeater 557 detected alarm condition to the polling terminal unit occurs in 558 the same EOC message as the reporting of the current SNR Margin 559 and Loop Attenuation values, it is anticipated that this will have 560 very little impact on agent implementation. 562 A threshold trap occurs whenever the corresponding current 15-minute 563 interval error counter becomes equal to, or exceeds the threshold 564 value. One trap may be sent per interval per interface. Since the 565 current 15-minute counter are reset to 0 every 15 minutes, if the 566 condition persists, the trap may recur as often as every 15 minutes. 567 For example, to get a trap whenever a "loss of" event occurs (but at 568 most once every 15 minutes), set the corresponding threshold to 1. The 569 agent will generate a trap when the event originally occurs. 571 Note that the NMS may receive a linkDown trap, as well, if enabled. At 572 the beginning of the next 15 minute interval, the counter is reset. 573 When the first second goes by and the event occurs, the current 574 interval bucket will be 1, which equals the threshold and the trap will 575 be sent again. 577 Expires May 21, 2001 Page [10] 578 A hdsl2ShdslSpanInvalidNumRepeaters trap may be generated following 579 completion of the discovery phase if the number of repeaters discovered 580 on the line differs from the number of repeaters specified in 581 hdsl2ShdslConfNumRepeaters. For those conditions where the number of 582 provisioned repeaters is greater than those encountered during span 583 discovery, all table entries associated with the nonexistant repeaters 584 are to be discarded. For those conditions where the number of 585 provisioned repeaters is less than those encountered during span 586 discovery, additional table entries are to be created using the default 587 span configuration profile. 589 5. Conformance and Compliance 591 For both HDSL2 and SHDSL lines, the following group(s) are mandatory: 593 hdsl2ShdslSpanConfGroup 594 hdsl2ShdslSpanStatusGroup 595 hdsl2ShdslInventoryGroup 596 hdsl2ShdslEndpointConfGroup 597 hdsl2Shdsl15MinIntervalGroup 598 hdsl2Shdsl1DayIntervalGroup 599 hdsl2ShdslMaintenanceGroup 600 hdsl2ShdslEndpointAlarmConfGroup 601 hdsl2ShdslNotificationGroup 603 For HDSL2 lines, the following group(s) are optional: 605 hdsl2ShdslSpanConfProfileGroup 606 hdsl2ShdslSpanShdslStatusGroup 608 6. Definitions 610 HDSL2-SHDSL-LINE-MIB DEFINITIONS ::= BEGIN 612 IMPORTS 613 MODULE-IDENTITY, 614 OBJECT-TYPE, 615 Counter32, 616 Gauge32, 617 NOTIFICATION-TYPE, 618 Integer32, 619 experimental FROM SNMPv2-SMI 620 DisplayString, 621 RowStatus, 622 TEXTUAL-CONVENTION FROM SNMPv2-TC 623 ifIndex FROM IF-MIB 624 PerfCurrentCount, 625 PerfIntervalCount FROM PerfHist-TC-MIB 626 SnmpAdminString FROM SNMP-FRAMEWORK-MIB 627 MODULE-COMPLIANCE, 628 OBJECT-GROUP, 629 NOTIFICATION-GROUP FROM SNMPv2-CONF; 631 Expires May 21, 2001 Page [11] 632 hdsl2ShdslMIB MODULE-IDENTITY 634 LAST-UPDATED "000011210000Z" -- November 21, 2000 636 ORGANIZATION "ADSLMIB Working Group" 638 CONTACT-INFO 640 " 641 Bob Ray 642 Verilink Corporation 643 127 Jetplex Circle 644 Madison, AL 35758 USA 645 Tel: +1 256-774-2380 646 Fax: +1 256-774-2277 647 E-mail: bray@verilink.com 649 Rajesh Abbi 650 Alcatel USA 651 2912 Wake Forest Road 652 Raleigh, NC 27609-7860 USA 653 Tel: +1 919-950-6194 654 Fax: +1 919-950-6670 655 E-mail: Rajesh.Abbi@usa.alcatel.com 656 " 658 DESCRIPTION 659 "This MIB module defines a collection of objects for 660 managing HDSL2/SHDSL lines. An agent may reside at 661 either end of the line, however the MIB is designed 662 to require no management communication between the 663 modems beyond that inherent in the low-level EOC line 664 protocol as defined in ANSI T1E1.4/2000-006 (for HDSL2 665 lines), or in ITU G.991.2 (for SHDSL lines)." 667 -- NOTE TO RFC EDITOR: Please replace the following with the 668 -- appropriate assigned 'transmission xxx' number 669 ::= { experimental 999999 } 671 hdsl2ShdslLineMib OBJECT IDENTIFIER ::= { hdsl2ShdslMIB 1 } 672 hdsl2ShdslMibObjects OBJECT IDENTIFIER ::= { hdsl2ShdslLineMib 1 } 674 -- Textual Conventions used in this MIB 675 -- 677 Hdsl2ShdslPerfCurrDayCount ::= TEXTUAL-CONVENTION 678 STATUS current 679 DESCRIPTION 680 "A counter associated with interface performance 681 measurements in a current 1-day (24 hour) measurement 682 interval. 684 Expires May 21, 2001 Page [12] 685 The value of this counter starts at zero at the 686 beginning of an interval and is increased when 687 associated events occur, until the end of the 688 1-day interval. At that time the value of the 689 counter is stored in the previous 1-day history 690 interval, if available, and the current interval 691 counter is restarted at zero. 693 In the case where the agent has no valid data available 694 for this interval the corresponding object 695 instance is not available and upon a retrieval 696 request a corresponding error message shall be 697 returned to indicate that this instance does 698 not exist (for example, a noSuchName error for 699 SNMPv1 and a noSuchInstance for SNMPv2 GET 700 operation)." 701 SYNTAX Gauge32 703 Hdsl2Shdsl1DayIntervalCount ::= TEXTUAL-CONVENTION 704 STATUS current 705 DESCRIPTION 706 "A counter associated with interface performance 707 measurements during the most previous 1-day (24 hour) 708 measurement interval. The value of this counter is 709 equal to the value of the current day counter at 710 the end of its most recent interval. 712 In the case where the agent has no valid data available 713 for this interval the corresponding object instance is 714 not available and upon a retrieval request a corresponding 715 error message shall be returned to indicate that this 716 instance does not exist (for example, a noSuchName error 717 for SNMPv1 and a noSuchInstance for SNMPv2 GET operation)." 718 SYNTAX Gauge32 720 Hdsl2ShdslPerfTimeElapsed ::= TEXTUAL-CONVENTION 721 STATUS current 722 DESCRIPTION 723 "The number of seconds that have elapsed since 724 the beginning of the current measurement period. 725 If, for some reason, such as an adjustment in the 726 system's time-of-day clock, the current interval 727 exceeds the maximum value, the agent will return 728 the maximum value." 729 SYNTAX Gauge32 731 Hdsl2ShdslPerfIntervalThreshold ::= TEXTUAL-CONVENTION 732 STATUS current 733 DESCRIPTION 734 "This convention defines a range of values 735 that may be set in a fault threshold alarm 736 control. As the number of seconds in a 738 Expires May 21, 2001 Page [13] 739 15-minute interval numbers at most 900, objects 740 of this type may have a range of 0...900, where 741 the value of 0 disables the alarm." 742 SYNTAX INTEGER(0..900) 744 Hdsl2ShdslUnitId ::= TEXTUAL-CONVENTION 745 STATUS current 746 DESCRIPTION 747 "This is the unique identification for all units 748 in an HDSL2/SHDSL Span. It is based on the EOC 749 unit addressing scheme with reference to the xtuC." 750 SYNTAX INTEGER 751 { 752 xtuC(1), 753 xtuR(2), 754 xru1(3), 755 xru2(4), 756 xru3(5), 757 xru4(6), 758 xru5(7), 759 xru6(8), 760 xru7(9), 761 xru8(10) 762 } 764 Hdsl2ShdslUnitSide ::= TEXTUAL-CONVENTION 765 STATUS current 766 DESCRIPTION 767 "This is the referenced side of an HDSL2/SHDSL 768 unit - Network or Customer side. The side 769 facing the Network is the Network side, while the 770 side facing the Customer is the Customer side." 771 SYNTAX INTEGER 772 { 773 networkSide(1), 774 customerSide(2) 775 } 777 Hdsl2ShdslWirePair ::= TEXTUAL-CONVENTION 778 STATUS current 779 DESCRIPTION 780 "This is the referenced pair of wires in an HDSL2/SHDSL 781 Segment. HDSL2 only supports a single pair (wirePair1), 782 while SHDSL supports an optional second pair (wirePair2)." 783 SYNTAX INTEGER 784 { 785 wirePair1(1), 786 wirePair2(2) 787 } 789 Hdsl2ShdslTransmissionModeType ::= TEXTUAL-CONVENTION 790 STATUS current 792 Expires May 21, 2001 Page [14] 793 DESCRIPTION 794 "Contains the regional setting of the HDSL2/SHDSL span, 795 represented as a bit-map of possible settings. The various 796 bit positions are: 798 1 region 1 Indicates ITU-T G.991.2 Annex A. 800 2 region 2 Indicates ITU-T G.991.2 Annex B. 802 4 region 3 Indicates ITU-T G.991.2 Annex C." 803 SYNTAX Integer32 805 -- Span Configuration Group 806 -- 808 hdsl2ShdslSpanConfTable OBJECT-TYPE 809 SYNTAX SEQUENCE OF Hdsl2ShdslSpanConfEntry 810 MAX-ACCESS not-accessible 811 STATUS current 812 DESCRIPTION 813 "This table supports overall configuration of 814 HDSL2/SHDSL Spans." 815 ::= { hdsl2ShdslMibObjects 1 } 817 hdsl2ShdslSpanConfEntry OBJECT-TYPE 818 SYNTAX Hdsl2ShdslSpanConfEntry 819 MAX-ACCESS not-accessible 820 STATUS current 821 DESCRIPTION 822 "An entry in the hdsl2ShdslSpanConfTable. Each entry 823 represents the complete Span in a single HDSL2/SHDSL 824 line. It is indexed by the ifIndex of the associated 825 HDSL2/SHDSL line." 826 INDEX { ifIndex } 827 ::= { hdsl2ShdslSpanConfTable 1 } 829 Hdsl2ShdslSpanConfEntry ::= 830 SEQUENCE 831 { 832 hdsl2ShdslConfNumRepeaters INTEGER, 833 hdsl2ShdslSpanConfProfile SnmpAdminString, 834 hdsl2ShdslSpanAlarmConfProfile SnmpAdminString 835 } 837 hdsl2ShdslConfNumRepeaters OBJECT-TYPE 838 SYNTAX INTEGER(0..8) 839 MAX-ACCESS read-write 840 STATUS current 841 DESCRIPTION 842 "This object provisions the number of repeaters/regenerators 843 in this HDSL2/SHDSL Span." 844 ::= { hdsl2ShdslSpanConfEntry 1 } 846 Expires May 21, 2001 Page [15] 847 hdsl2ShdslSpanConfProfile OBJECT-TYPE 848 SYNTAX SnmpAdminString (SIZE(1..32)) 849 MAX-ACCESS read-write 850 STATUS current 851 DESCRIPTION 852 "This object is a pointer to a span configuration profile in 853 the hdsl2ShdslSpanConfProfileTable, which applies to this span. 854 The value of this object is the index of the referenced profile 855 in the hdsl2ShdslSpanConfProfileTable. Note that span 856 configuration profiles are only applicable to SHDSL lines. 857 HDSL2 lines will not support this object. By default, this 858 object will have the value 'DEFVAL' (the index of the default 859 profile)." 860 ::= { hdsl2ShdslSpanConfEntry 2 } 862 hdsl2ShdslSpanAlarmConfProfile OBJECT-TYPE 863 SYNTAX SnmpAdminString (SIZE(1..32)) 864 MAX-ACCESS read-write 865 STATUS current 866 DESCRIPTION 867 "This object is a pointer to an Alarm configuration profile in 868 the hdsl2ShdslEndpointAlarmConfProfileTable. The value of this 869 object is the index of the referenced profile in the 870 hdsl2ShdslEndpointAlarmConfProfileTable. The alarm threshold 871 configuration in the referenced profile will be used by default 872 for all segment endpoints in this span. Individual endpoints 873 may override this profile by explicitly specifying some other 874 profile in the hdsl2ShdslEndpointConfTable. By default, this 875 object will have the value 'DEFVAL' (the index of the default 876 profile)." 877 ::= { hdsl2ShdslSpanConfEntry 3 } 879 -- Span Status Group 880 -- 882 hdsl2ShdslSpanStatusTable OBJECT-TYPE 883 SYNTAX SEQUENCE OF Hdsl2ShdslSpanStatusEntry 884 MAX-ACCESS not-accessible 885 STATUS current 886 DESCRIPTION 887 "This table provides overall status information of 888 HDSL2/SHDSL spans." 889 ::= { hdsl2ShdslMibObjects 2 } 891 hdsl2ShdslSpanStatusEntry OBJECT-TYPE 892 SYNTAX Hdsl2ShdslSpanStatusEntry 893 MAX-ACCESS not-accessible 894 STATUS current 895 DESCRIPTION 896 "An entry in the hdsl2ShdslSpanStatusTable. Each entry 897 represents the complete span in a single HDSL2/SHDSL 898 line. It is indexed by the ifIndex of the associated 900 Expires May 21, 2001 Page [16] 901 HDSL2/SHDSL line." 902 INDEX { ifIndex } 903 ::= { hdsl2ShdslSpanStatusTable 1 } 905 Hdsl2ShdslSpanStatusEntry ::= 906 SEQUENCE 907 { 908 hdsl2ShdslStatusNumAvailRepeaters INTEGER, 909 hdsl2ShdslStatusMaxAttainableLineRate Integer32, 910 hdsl2ShdslStatusActualLineRate Integer32, 911 hdsl2ShdslStatusTransmissionModeCurrent 912 Hdsl2ShdslTransmissionModeType 913 } 915 hdsl2ShdslStatusNumAvailRepeaters OBJECT-TYPE 916 SYNTAX INTEGER(0..8) 917 MAX-ACCESS read-only 918 STATUS current 919 DESCRIPTION 920 "Contains the actual number of repeaters/regenerators 921 discovered in this HDSL2/SHDSL span." 922 ::= { hdsl2ShdslSpanStatusEntry 1 } 924 hdsl2ShdslStatusMaxAttainableLineRate OBJECT-TYPE 925 SYNTAX Integer32 926 MAX-ACCESS read-only 927 STATUS current 928 DESCRIPTION 929 "Contains the maximum attainable line rate in this HDSL2/SHDSL 930 span." 931 ::= { hdsl2ShdslSpanStatusEntry 2 } 933 hdsl2ShdslStatusActualLineRate OBJECT-TYPE 934 SYNTAX Integer32 935 MAX-ACCESS read-only 936 STATUS current 937 DESCRIPTION 938 "Contains the actual line rate in this HDSL2/SHDSL span." 939 ::= { hdsl2ShdslSpanStatusEntry 3 } 941 hdsl2ShdslStatusTransmissionModeCurrent OBJECT-TYPE 942 SYNTAX Hdsl2ShdslTransmissionModeType 943 MAX-ACCESS read-only 944 STATUS current 945 DESCRIPTION 946 "Contains the current PSD regional setting of the 947 HDSL2/SHDSL span." 948 ::= { hdsl2ShdslSpanStatusEntry 4 } 950 -- Unit Inventory Group 951 -- 953 Expires May 21, 2001 Page [17] 954 hdsl2ShdslInventoryTable OBJECT-TYPE 955 SYNTAX SEQUENCE OF Hdsl2ShdslInventoryEntry 956 MAX-ACCESS not-accessible 957 STATUS current 958 DESCRIPTION 959 "This table supports retrieval of unit inventory information 960 available via the EOC from units in a HDSL2/SHDSL line." 961 ::= { hdsl2ShdslMibObjects 3 } 963 hdsl2ShdslInventoryEntry OBJECT-TYPE 964 SYNTAX Hdsl2ShdslInventoryEntry 965 MAX-ACCESS not-accessible 966 STATUS current 967 DESCRIPTION 968 "An entry in the hdsl2ShdslInventoryTable. Each entry 969 represents inventory information for a single unit in a 970 HDSL2/SHDSL line. It is indexed by the ifIndex of the 971 HDSL2/SHDSL line and the Hdsl2ShdslUnitId of the 972 associated unit." 973 INDEX { ifIndex, hdsl2ShdslInvIndex } 974 ::= { hdsl2ShdslInventoryTable 1 } 976 Hdsl2ShdslInventoryEntry ::= 977 SEQUENCE 978 { 979 hdsl2ShdslInvIndex Hdsl2ShdslUnitId, 980 hdsl2ShdslInvVendorID OCTET STRING, 981 hdsl2ShdslInvVendorModelNumber DisplayString, 982 hdsl2ShdslInvVendorSerialNumber DisplayString, 983 hdsl2ShdslInvVendorEOCSoftwareVersion Integer32, 984 hdsl2ShdslInvStandardVersion Integer32, 985 hdsl2ShdslInvVendorListNumber DisplayString, 986 hdsl2ShdslInvVendorIssueNumber DisplayString, 987 hdsl2ShdslInvVendorSoftwareVersion DisplayString, 988 hdsl2ShdslInvEquipmentCode DisplayString, 989 hdsl2ShdslInvVendorOther DisplayString, 990 hdsl2ShdslInvTransmissionModeCapability 991 Hdsl2ShdslTransmissionModeType 992 } 994 hdsl2ShdslInvIndex OBJECT-TYPE 995 SYNTAX Hdsl2ShdslUnitId 996 MAX-ACCESS read-only 997 STATUS current 998 DESCRIPTION 999 "The index into the hdsl2ShdslInventoryTable." 1000 ::= { hdsl2ShdslInventoryEntry 1 } 1002 hdsl2ShdslInvVendorID OBJECT-TYPE 1003 SYNTAX OCTET STRING(SIZE(9)) 1004 MAX-ACCESS read-only 1005 STATUS current 1007 Expires May 21, 2001 Page [18] 1008 DESCRIPTION 1009 "Vendor ID as reported in an Inventory Response message. 1010 Note that there is a variance between G.994.1 and G.991.2 1011 as to the contents of this field (8 octets vs. 8.5 octets 1012 respectively). In all cases, this object should report 1013 the Vendor ID as reported by the inventoried unit. The 1014 Vendor ID MUST be right-aligned with respect to the 1015 entirety of the octet string, resulting in the high order 1016 nibble of the first octet being zero. 1017 " 1018 ::= { hdsl2ShdslInventoryEntry 2 } 1020 hdsl2ShdslInvVendorModelNumber OBJECT-TYPE 1021 SYNTAX DisplayString 1022 MAX-ACCESS read-only 1023 STATUS current 1024 DESCRIPTION 1025 "Vendor model number as reported in an Inventory Response 1026 message." 1027 ::= { hdsl2ShdslInventoryEntry 3 } 1029 hdsl2ShdslInvVendorSerialNumber OBJECT-TYPE 1030 SYNTAX DisplayString 1031 MAX-ACCESS read-only 1032 STATUS current 1033 DESCRIPTION 1034 "Vendor serial number as reported in an Inventory Response 1035 message." 1036 ::= { hdsl2ShdslInventoryEntry 4 } 1038 hdsl2ShdslInvVendorEOCSoftwareVersion OBJECT-TYPE 1039 SYNTAX Integer32 1040 MAX-ACCESS read-only 1041 STATUS current 1042 DESCRIPTION 1043 "Vendor EOC version as reported in a Discovery Response 1044 message." 1045 ::= { hdsl2ShdslInventoryEntry 5 } 1047 hdsl2ShdslInvStandardVersion OBJECT-TYPE 1048 SYNTAX Integer32 1049 MAX-ACCESS read-only 1050 STATUS current 1051 DESCRIPTION 1052 "Version of the HDSL2/SHDSL standard implemented, as reported 1053 in an Inventory Response message." 1054 ::= { hdsl2ShdslInventoryEntry 6 } 1056 hdsl2ShdslInvVendorListNumber OBJECT-TYPE 1057 SYNTAX DisplayString 1058 MAX-ACCESS read-only 1059 STATUS current 1061 Expires May 21, 2001 Page [19] 1062 DESCRIPTION 1063 "Vendor list number as reported in an Inventory Response 1064 message." 1065 ::= { hdsl2ShdslInventoryEntry 7 } 1067 hdsl2ShdslInvVendorIssueNumber OBJECT-TYPE 1068 SYNTAX DisplayString 1069 MAX-ACCESS read-only 1070 STATUS current 1071 DESCRIPTION 1072 "Vendor issue number as reported in an Inventory Response 1073 message." 1074 ::= { hdsl2ShdslInventoryEntry 8 } 1076 hdsl2ShdslInvVendorSoftwareVersion OBJECT-TYPE 1077 SYNTAX DisplayString 1078 MAX-ACCESS read-only 1079 STATUS current 1080 DESCRIPTION 1081 "Vendor software version as reported in an Inventory 1082 Response message." 1083 ::= { hdsl2ShdslInventoryEntry 9 } 1085 hdsl2ShdslInvEquipmentCode OBJECT-TYPE 1086 SYNTAX DisplayString 1087 MAX-ACCESS read-only 1088 STATUS current 1089 DESCRIPTION 1090 "Equipment code conforming to ANSI T1.213, Coded Identification 1091 of Equipment Entities." 1092 ::= { hdsl2ShdslInventoryEntry 10 } 1094 hdsl2ShdslInvVendorOther OBJECT-TYPE 1095 SYNTAX DisplayString 1096 MAX-ACCESS read-only 1097 STATUS current 1098 DESCRIPTION 1099 "Other vendor information as reported in an Inventory 1100 Response message." 1101 ::= { hdsl2ShdslInventoryEntry 11 } 1103 hdsl2ShdslInvTransmissionModeCapability OBJECT-TYPE 1104 SYNTAX Hdsl2ShdslTransmissionModeType 1105 MAX-ACCESS read-only 1106 STATUS current 1107 DESCRIPTION 1108 "Contains the transmission mode capability of the SHDSL unit." 1109 ::= { hdsl2ShdslInventoryEntry 12 } 1111 -- Segment Endpoint Configuration Group 1112 -- 1114 Expires May 21, 2001 Page [20] 1115 hdsl2ShdslEndpointConfTable OBJECT-TYPE 1116 SYNTAX SEQUENCE OF Hdsl2ShdslEndpointConfEntry 1117 MAX-ACCESS not-accessible 1118 STATUS current 1119 DESCRIPTION 1120 "This table supports configuration parameters for segment 1121 endpoints in a HDSL2/SHDSL line." 1122 ::= { hdsl2ShdslMibObjects 4 } 1124 hdsl2ShdslEndpointConfEntry OBJECT-TYPE 1125 SYNTAX Hdsl2ShdslEndpointConfEntry 1126 MAX-ACCESS not-accessible 1127 STATUS current 1128 DESCRIPTION 1129 "An entry in the hdsl2ShdslEndpointConfTable. Each entry 1130 represents a single segment endpoint in a HDSL2/SHDSL line. 1131 It is indexed by the ifIndex of the HDSL2/SHDSL line, the 1132 UnitId of the associated unit, the side of the unit, and the 1133 wire-pair of the associated modem." 1134 INDEX { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide, 1135 hdsl2ShdslEndpointWirePair} 1136 ::= { hdsl2ShdslEndpointConfTable 1 } 1138 Hdsl2ShdslEndpointConfEntry ::= 1139 SEQUENCE 1140 { 1141 hdsl2ShdslEndpointSide Hdsl2ShdslUnitSide, 1142 hdsl2ShdslEndpointWirePair Hdsl2ShdslWirePair, 1143 hdsl2ShdslEndpointAlarmConfProfile SnmpAdminString 1144 } 1146 hdsl2ShdslEndpointSide OBJECT-TYPE 1147 SYNTAX Hdsl2ShdslUnitSide 1148 MAX-ACCESS read-only 1149 STATUS current 1150 DESCRIPTION 1151 "The side of the unit associated with this segment endpoint - 1152 Network/Customer side - as per the Hdsl2ShdslUnitSide 1153 textual convention." 1154 ::= { hdsl2ShdslEndpointConfEntry 1 } 1156 hdsl2ShdslEndpointWirePair OBJECT-TYPE 1157 SYNTAX Hdsl2ShdslWirePair 1158 MAX-ACCESS read-only 1159 STATUS current 1160 DESCRIPTION 1161 "The wire-pair of the modem associated with this segment 1162 endpoint as per the Hdsl2ShdslWirePair textual convention." 1163 ::= { hdsl2ShdslEndpointConfEntry 2 } 1165 hdsl2ShdslEndpointAlarmConfProfile OBJECT-TYPE 1166 SYNTAX SnmpAdminString (SIZE(0..32)) 1168 Expires May 21, 2001 Page [21] 1169 MAX-ACCESS read-write 1170 STATUS current 1171 DESCRIPTION 1172 "This object configures the alarm threshold values to be 1173 used for this segment endpoint. The values are obtained 1174 from the alarm configuration profile referenced by this 1175 object. The value of this object is the index of the 1176 referenced profile in the hdsl2ShdslLineAlarmConfProfileTable, 1177 or NULL (a string of length 0). If the value is NULL, the 1178 endpoint uses the default Alarm Configuration Profile for the 1179 associated span as per the hdsl2ShdslSpanAlarmConfProfile 1180 object in the hdsl2ShdslSpanConfTable. The default value of 1181 this object is NULL. 1182 ::= { hdsl2ShdslEndpointConfEntry 3 } 1184 -- Segment Endpoint Current Status/Performance Group 1185 -- 1187 hdsl2ShdslEndpointCurrTable OBJECT-TYPE 1188 SYNTAX SEQUENCE OF Hdsl2ShdslEndpointCurrEntry 1189 MAX-ACCESS not-accessible 1190 STATUS current 1191 DESCRIPTION 1192 "This table contains current status and performance information 1193 for segment endpoints in HDSL2/SHDSL Lines." 1194 ::= { hdsl2ShdslMibObjects 5 } 1196 hdsl2ShdslEndpointCurrEntry OBJECT-TYPE 1197 SYNTAX Hdsl2ShdslEndpointCurrEntry 1198 MAX-ACCESS not-accessible 1199 STATUS current 1200 DESCRIPTION 1201 "An entry in the hdsl2ShdslEndpointCurrTable. Each entry 1202 contains status and performance information relating to a 1203 single segment endpoint. It is indexed by the ifIndex of 1204 the HDSL2/SHDSL line, the UnitId of the associated unit, 1205 the side of the unit, and the wire-pair of the associated 1206 modem." 1207 INDEX { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide, 1208 hdsl2ShdslEndpointWirePair} 1209 ::= { hdsl2ShdslEndpointCurrTable 1 } 1211 Hdsl2ShdslEndpointCurrEntry ::= 1212 SEQUENCE 1213 { 1214 hdsl2ShdslEndpointCurrAtn Integer32, 1215 hdsl2ShdslEndpointCurrSnrMgn Integer32, 1216 hdsl2ShdslEndpointCurrStatus Integer32, 1217 hdsl2ShdslEndpointES Counter32, 1218 hdsl2ShdslEndpointSES Counter32, 1219 hdsl2ShdslEndpointCRCanomalies Counter32, 1221 Expires May 21, 2001 Page [22] 1222 hdsl2ShdslEndpointLOSWS Counter32, 1223 hdsl2ShdslEndpointUAS Counter32, 1224 hdsl2ShdslEndpointCurr15MinTimeElapsed Hdsl2ShdslPerfTimeElapsed, 1225 hdsl2ShdslEndpointCurr15MinES PerfCurrentCount, 1226 hdsl2ShdslEndpointCurr15MinSES PerfCurrentCount, 1227 hdsl2ShdslEndpointCurr15MinCRCanomalies PerfCurrentCount, 1228 hdsl2ShdslEndpointCurr15MinLOSWS PerfCurrentCount, 1229 hdsl2ShdslEndpointCurr15MinUAS PerfCurrentCount, 1230 hdsl2ShdslEndpointCurr1DayTimeElapsed Hdsl2ShdslPerfTimeElapsed, 1231 hdsl2ShdslEndpointCurr1DayES Hdsl2ShdslPerfCurrDayCount, 1232 hdsl2ShdslEndpointCurr1DaySES Hdsl2ShdslPerfCurrDayCount, 1233 hdsl2ShdslEndpointCurr1DayCRCanomalies Hdsl2ShdslPerfCurrDayCount, 1234 hdsl2ShdslEndpointCurr1DayLOSWS Hdsl2ShdslPerfCurrDayCount, 1235 hdsl2ShdslEndpointCurr1DayUAS Hdsl2ShdslPerfCurrDayCount 1236 } 1238 hdsl2ShdslEndpointCurrAtn OBJECT-TYPE 1239 SYNTAX Integer32 1240 UNITS "dB" 1241 MAX-ACCESS read-only 1242 STATUS current 1243 DESCRIPTION 1244 "The current loop attenuation for this endpoint as 1245 reported in a Network or Customer Side Performance 1246 Status message." 1247 ::= { hdsl2ShdslEndpointCurrEntry 1 } 1249 hdsl2ShdslEndpointCurrSnrMgn OBJECT-TYPE 1250 SYNTAX Integer32 1251 UNITS "dB" 1252 MAX-ACCESS read-only 1253 STATUS current 1254 DESCRIPTION 1255 "The current SNR margin for this endpoint as reported 1256 in a Status Response/SNR message." 1257 ::= { hdsl2ShdslEndpointCurrEntry 2 } 1259 hdsl2ShdslEndpointCurrStatus OBJECT-TYPE 1260 SYNTAX Integer32 1261 MAX-ACCESS read-only 1262 STATUS current 1263 DESCRIPTION 1264 "Contains the current state of the endpoint. This is a 1265 bit-map of possible conditions. The various bit positions 1266 are: 1268 1 noDefect There no defects on the line 1270 2 powerBackoff Indicates enhanced Power Backoff 1272 4 deviceFault Indicates a vendor-dependent 1273 detection of diagnostics or 1275 Expires May 21, 2001 Page [23] 1276 self-test results 1278 8 dcContinuityFault Indicates vendor-dependent 1279 conditions that interfere with 1280 span powering such as short and 1281 open circuits 1283 16 snrMarginAlarm Indicates that the SNR margin 1284 has exceeded the alarm threshold 1286 32 loopAttenuationAlarm Indicates that the loop attentuation 1287 has exceeded the alarm threshold 1289 64 loswFailureAlarm Indicates a forward LOSW alarm 1291 128 configInitFailure Endpoint failure during initialization 1292 due to paired endpoint not able to 1293 support requested configuration 1295 256 protocolInitFailure Endpoint failure during initialization 1296 due to incompatible protocol used by 1297 the paired endpoint. 1299 512 noNeighborPresent Endpoint failure during initialization 1300 due to no activation sequence detected 1301 from paired endpoint. 1303 1024 loopbackActive A loopback is currently active at this 1304 Segment Endpoint. 1306 This is intended to supplement ifOperStatus." 1307 ::= { hdsl2ShdslEndpointCurrEntry 3 } 1309 hdsl2ShdslEndpointES OBJECT-TYPE 1310 SYNTAX Counter32 1311 UNITS "seconds" 1312 MAX-ACCESS read-only 1313 STATUS current 1314 DESCRIPTION 1315 "Count of Errored Seconds (ES) on this endpoint since the xU 1316 was last restarted." 1317 ::= { hdsl2ShdslEndpointCurrEntry 4 } 1319 hdsl2ShdslEndpointSES OBJECT-TYPE 1320 SYNTAX Counter32 1321 UNITS "seconds" 1322 MAX-ACCESS read-only 1323 STATUS current 1324 DESCRIPTION 1325 "Count of Severely Errored Seconds (SES) on this endpoint 1326 since the xU was last restarted." 1327 ::= { hdsl2ShdslEndpointCurrEntry 5 } 1329 Expires May 21, 2001 Page [24] 1330 hdsl2ShdslEndpointCRCanomalies OBJECT-TYPE 1331 SYNTAX Counter32 1332 MAX-ACCESS read-only 1333 STATUS current 1334 DESCRIPTION 1335 "Count of CRC anomalies on this endpoint since the xU was 1336 last restarted." 1337 ::= { hdsl2ShdslEndpointCurrEntry 6 } 1339 hdsl2ShdslEndpointLOSWS OBJECT-TYPE 1340 SYNTAX Counter32 1341 UNITS "seconds" 1342 MAX-ACCESS read-only 1343 STATUS current 1344 DESCRIPTION 1345 "Count of Loss of Sync Word (LOSW) Seconds on this endpoint 1346 since the xU was last restarted." 1347 ::= { hdsl2ShdslEndpointCurrEntry 7 } 1349 hdsl2ShdslEndpointUAS OBJECT-TYPE 1350 SYNTAX Counter32 1351 UNITS "seconds" 1352 MAX-ACCESS read-only 1353 STATUS current 1354 DESCRIPTION 1355 "Count of Unavailable Seconds (UAS) on this endpoint since 1356 the xU was last restarted." 1357 ::= { hdsl2ShdslEndpointCurrEntry 8 } 1359 hdsl2ShdslEndpointCurr15MinTimeElapsed OBJECT-TYPE 1360 SYNTAX Hdsl2ShdslPerfTimeElapsed 1361 UNITS "seconds" 1362 MAX-ACCESS read-only 1363 STATUS current 1364 DESCRIPTION 1365 "Total elapsed seconds in the current 15-minute interval." 1366 ::= { hdsl2ShdslEndpointCurrEntry 9 } 1368 hdsl2ShdslEndpointCurr15MinES OBJECT-TYPE 1369 SYNTAX PerfCurrentCount 1370 UNITS "seconds" 1371 MAX-ACCESS read-only 1372 STATUS current 1373 DESCRIPTION 1374 "Count of Errored Seconds (ES) in the current 15-minute 1375 interval." 1376 ::= { hdsl2ShdslEndpointCurrEntry 10 } 1378 hdsl2ShdslEndpointCurr15MinSES OBJECT-TYPE 1379 SYNTAX PerfCurrentCount 1380 UNITS "seconds" 1381 MAX-ACCESS read-only 1383 Expires May 21, 2001 Page [25] 1384 STATUS current 1385 DESCRIPTION 1386 "Count of Severely Errored Seconds (SES) in the current 1387 15-minute interval." 1388 ::= { hdsl2ShdslEndpointCurrEntry 11 } 1390 hdsl2ShdslEndpointCurr15MinCRCanomalies OBJECT-TYPE 1391 SYNTAX PerfCurrentCount 1392 MAX-ACCESS read-only 1393 STATUS current 1394 DESCRIPTION 1395 "Count of CRC anomalies in the current 15-minute interval." 1396 ::= { hdsl2ShdslEndpointCurrEntry 12 } 1398 hdsl2ShdslEndpointCurr15MinLOSWS OBJECT-TYPE 1399 SYNTAX PerfCurrentCount 1400 UNITS "seconds" 1401 MAX-ACCESS read-only 1402 STATUS current 1403 DESCRIPTION 1404 "Count of Loss of Sync Word (LOSW) Seconds in the current 1405 15-minute interval." 1406 ::= { hdsl2ShdslEndpointCurrEntry 13 } 1408 hdsl2ShdslEndpointCurr15MinUAS OBJECT-TYPE 1409 SYNTAX PerfCurrentCount 1410 UNITS "seconds" 1411 MAX-ACCESS read-only 1412 STATUS current 1413 DESCRIPTION 1414 "Count of Unavailable Seconds (UAS) in the current 15-minute 1415 interval." 1416 ::= { hdsl2ShdslEndpointCurrEntry 14 } 1418 hdsl2ShdslEndpointCurr1DayTimeElapsed OBJECT-TYPE 1419 SYNTAX Hdsl2ShdslPerfTimeElapsed 1420 UNITS "seconds" 1421 MAX-ACCESS read-only 1422 STATUS current 1423 DESCRIPTION 1424 "Number of seconds that have elapsed since the beginning of 1425 the current 1-day interval." 1426 ::= { hdsl2ShdslEndpointCurrEntry 15 } 1428 hdsl2ShdslEndpointCurr1DayES OBJECT-TYPE 1429 SYNTAX Hdsl2ShdslPerfCurrDayCount 1430 UNITS "seconds" 1431 MAX-ACCESS read-only 1432 STATUS current 1433 DESCRIPTION 1434 "Count of Errored Seconds (ES) during the current day as 1435 measured by hdsl2ShdslEndpointCurr1DayTimeElapsed." 1437 Expires May 21, 2001 Page [26] 1438 ::= { hdsl2ShdslEndpointCurrEntry 16 } 1440 hdsl2ShdslEndpointCurr1DaySES OBJECT-TYPE 1441 SYNTAX Hdsl2ShdslPerfCurrDayCount 1442 UNITS "seconds" 1443 MAX-ACCESS read-only 1444 STATUS current 1445 DESCRIPTION 1446 "Count of Severely Errored Seconds (SES) during the current 1447 day as measured by hdsl2ShdslEndpointCurr1DayTimeElapsed." 1448 ::= { hdsl2ShdslEndpointCurrEntry 17 } 1450 hdsl2ShdslEndpointCurr1DayCRCanomalies OBJECT-TYPE 1451 SYNTAX Hdsl2ShdslPerfCurrDayCount 1452 MAX-ACCESS read-only 1453 STATUS current 1454 DESCRIPTION 1455 "Count of CRC anomalies during the current day as measured 1456 by hdsl2ShdslEndpointCurr1DayTimeElapsed." 1457 ::= { hdsl2ShdslEndpointCurrEntry 18 } 1459 hdsl2ShdslEndpointCurr1DayLOSWS OBJECT-TYPE 1460 SYNTAX Hdsl2ShdslPerfCurrDayCount 1461 UNITS "seconds" 1462 MAX-ACCESS read-only 1463 STATUS current 1464 DESCRIPTION 1465 "Count of Loss of Sync Word Seconds (LOSWS) during the current 1466 day as measured by hdsl2ShdslEndpointCurr1DayTimeElapsed." 1467 ::= { hdsl2ShdslEndpointCurrEntry 19 } 1469 hdsl2ShdslEndpointCurr1DayUAS OBJECT-TYPE 1470 SYNTAX Hdsl2ShdslPerfCurrDayCount 1471 UNITS "seconds" 1472 MAX-ACCESS read-only 1473 STATUS current 1474 DESCRIPTION 1475 "Count of Unavailable Seconds (UAS) during the current 1476 day as measured by hdsl2ShdslEndpointCurr1DayTimeElapsed." 1477 ::= { hdsl2ShdslEndpointCurrEntry 20 } 1479 -- Segment Endpoint 15-Minute Interval Status/Performance Group 1480 -- 1482 hdsl2Shdsl15MinIntervalTable OBJECT-TYPE 1483 SYNTAX SEQUENCE OF Hdsl2Shdsl15MinIntervalEntry 1484 MAX-ACCESS not-accessible 1485 STATUS current 1486 DESCRIPTION 1487 "This table provides one row for each HDSL2/SHDSL endpoint 1488 performance data collection interval." 1489 ::= { hdsl2ShdslMibObjects 6 } 1491 Expires May 21, 2001 Page [27] 1492 hdsl2Shdsl15MinIntervalEntry OBJECT-TYPE 1493 SYNTAX Hdsl2Shdsl15MinIntervalEntry 1494 MAX-ACCESS not-accessible 1495 STATUS current 1496 DESCRIPTION 1497 "An entry in the hdsl2Shdsl15MinIntervalTable." 1498 INDEX { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide, 1499 hdsl2ShdslEndpointWirePair, hdsl2Shdsl15MinIntervalNumber} 1500 ::= { hdsl2Shdsl15MinIntervalTable 1 } 1502 Hdsl2Shdsl15MinIntervalEntry ::= 1503 SEQUENCE 1504 { 1505 hdsl2Shdsl15MinIntervalNumber INTEGER, 1506 hdsl2Shdsl15MinIntervalES PerfIntervalCount, 1507 hdsl2Shdsl15MinIntervalSES PerfIntervalCount, 1508 hdsl2Shdsl15MinIntervalCRCanomalies PerfIntervalCount, 1509 hdsl2Shdsl15MinIntervalLOSWS PerfIntervalCount, 1510 hdsl2Shdsl15MinIntervalUAS PerfIntervalCount 1511 } 1513 hdsl2Shdsl15MinIntervalNumber OBJECT-TYPE 1514 SYNTAX INTEGER(1..96) 1515 MAX-ACCESS not-accessible 1516 STATUS current 1517 DESCRIPTION 1518 "Performance Data Interval number. 1 is the the most recent 1519 previous interval; interval 96 is 24 hours ago. Intervals 1520 2..96 are optional." 1521 ::= { hdsl2Shdsl15MinIntervalEntry 1 } 1523 hdsl2Shdsl15MinIntervalES OBJECT-TYPE 1524 SYNTAX PerfIntervalCount 1525 UNITS "seconds" 1526 MAX-ACCESS read-only 1527 STATUS current 1528 DESCRIPTION 1529 "Count of Errored Seconds (ES) during the interval." 1530 ::= { hdsl2Shdsl15MinIntervalEntry 2 } 1532 hdsl2Shdsl15MinIntervalSES OBJECT-TYPE 1533 SYNTAX PerfIntervalCount 1534 UNITS "seconds" 1535 MAX-ACCESS read-only 1536 STATUS current 1537 DESCRIPTION 1538 "Count of Severely Errored Seconds (SES) during the 1539 interval." 1540 ::= { hdsl2Shdsl15MinIntervalEntry 3 } 1542 hdsl2Shdsl15MinIntervalCRCanomalies OBJECT-TYPE 1543 SYNTAX PerfIntervalCount 1545 Expires May 21, 2001 Page [28] 1546 MAX-ACCESS read-only 1547 STATUS current 1548 DESCRIPTION 1549 "Count of CRC anomalies during the interval." 1550 ::= { hdsl2Shdsl15MinIntervalEntry 4 } 1552 hdsl2Shdsl15MinIntervalLOSWS OBJECT-TYPE 1553 SYNTAX PerfIntervalCount 1554 UNITS "seconds" 1555 MAX-ACCESS read-only 1556 STATUS current 1557 DESCRIPTION 1558 "Count of Loss of Sync Word (LOSW) Seconds during the interval." 1559 ::= { hdsl2Shdsl15MinIntervalEntry 5 } 1561 hdsl2Shdsl15MinIntervalUAS OBJECT-TYPE 1562 SYNTAX PerfIntervalCount 1563 UNITS "seconds" 1564 MAX-ACCESS read-only 1565 STATUS current 1566 DESCRIPTION 1567 "Count of Unavailable Seconds (UAS) during the interval." 1568 ::= { hdsl2Shdsl15MinIntervalEntry 6 } 1570 -- Segment Endpoint 1-Day Interval Status/Performance Group 1571 -- 1573 hdsl2Shdsl1DayIntervalTable OBJECT-TYPE 1574 SYNTAX SEQUENCE OF Hdsl2Shdsl1DayIntervalEntry 1575 MAX-ACCESS not-accessible 1576 STATUS current 1577 DESCRIPTION 1578 "This table provides one row for each HDSL2/SHDSL endpoint 1579 performance data collection interval." 1580 ::= { hdsl2ShdslMibObjects 7 } 1582 hdsl2Shdsl1DayIntervalEntry OBJECT-TYPE 1583 SYNTAX Hdsl2Shdsl1DayIntervalEntry 1584 MAX-ACCESS not-accessible 1585 STATUS current 1586 DESCRIPTION 1587 "An entry in the hdsl2Shdsl1DayIntervalTable." 1588 INDEX { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide, 1589 hdsl2ShdslEndpointWirePair, hdsl2Shdsl1DayIntervalInterval } 1590 ::= { hdsl2Shdsl1DayIntervalTable 1 } 1592 Hdsl2Shdsl1DayIntervalEntry ::= 1593 SEQUENCE 1594 { 1595 hdsl2Shdsl1DayIntervalInterval INTEGER, 1596 hdsl2Shdsl1DayIntervalMoniSecs Hdsl2ShdslPerfTimeElapsed, 1597 hdsl2Shdsl1DayIntervalES Hdsl2Shdsl1DayIntervalCount, 1599 Expires May 21, 2001 Page [29] 1600 hdsl2Shdsl1DayIntervalSES Hdsl2Shdsl1DayIntervalCount, 1601 hdsl2Shdsl1DayIntervalCRCanomalies Hdsl2Shdsl1DayIntervalCount, 1602 hdsl2Shdsl1DayIntervalLOSWS Hdsl2Shdsl1DayIntervalCount, 1603 hdsl2Shdsl1DayIntervalUAS Hdsl2Shdsl1DayIntervalCount 1604 } 1606 hdsl2Shdsl1DayIntervalInterval OBJECT-TYPE 1607 SYNTAX INTEGER(1..30) 1608 MAX-ACCESS not-accessible 1609 STATUS current 1610 DESCRIPTION 1611 "History Data Interval number. Interval 1 is the the most 1612 recent previous day; interval 30 is 30 days ago. Intervals 1613 2..30 are optional." 1614 ::= { hdsl2Shdsl1DayIntervalEntry 1 } 1616 hdsl2Shdsl1DayIntervalMoniSecs OBJECT-TYPE 1617 SYNTAX Hdsl2ShdslPerfTimeElapsed 1618 MAX-ACCESS read-only 1619 STATUS current 1620 DESCRIPTION 1621 "The amount of time in the 1-day interval over which the 1622 performance monitoring information is actually counted. 1623 This value will be the same as the interval duration except 1624 in a situation where performance monitoring data could not 1625 be collected for any reason." 1626 ::= { hdsl2Shdsl1DayIntervalEntry 2 } 1628 hdsl2Shdsl1DayIntervalES OBJECT-TYPE 1629 SYNTAX Hdsl2Shdsl1DayIntervalCount 1630 UNITS "seconds" 1631 MAX-ACCESS read-only 1632 STATUS current 1633 DESCRIPTION 1634 "Count of Errored Seconds (ES) during the 1-day interval as 1635 measured by hdsl2Shdsl1DayIntervalMoniSecs." 1636 ::= { hdsl2Shdsl1DayIntervalEntry 3 } 1638 hdsl2Shdsl1DayIntervalSES OBJECT-TYPE 1639 SYNTAX Hdsl2Shdsl1DayIntervalCount 1640 UNITS "seconds" 1641 MAX-ACCESS read-only 1642 STATUS current 1643 DESCRIPTION 1644 "Count of Severely Errored Seconds (SES) during the 1-day 1645 interval as measured by hdsl2Shdsl1DayIntervalMoniSecs." 1646 ::= { hdsl2Shdsl1DayIntervalEntry 4 } 1648 hdsl2Shdsl1DayIntervalCRCanomalies OBJECT-TYPE 1649 SYNTAX Hdsl2Shdsl1DayIntervalCount 1650 MAX-ACCESS read-only 1651 STATUS current 1653 Expires May 21, 2001 Page [30] 1654 DESCRIPTION 1655 "Count of CRC anomalies during the 1-day interval as 1656 measured by hdsl2Shdsl1DayIntervalMoniSecs." 1657 ::= { hdsl2Shdsl1DayIntervalEntry 5 } 1659 hdsl2Shdsl1DayIntervalLOSWS OBJECT-TYPE 1660 SYNTAX Hdsl2Shdsl1DayIntervalCount 1661 UNITS "seconds" 1662 MAX-ACCESS read-only 1663 STATUS current 1664 DESCRIPTION 1665 "Count of Loss of Sync Word (LOSW) Seconds during the 1-day 1666 interval as measured by hdsl2Shdsl1DayIntervalMoniSecs." 1667 ::= { hdsl2Shdsl1DayIntervalEntry 6 } 1669 hdsl2Shdsl1DayIntervalUAS OBJECT-TYPE 1670 SYNTAX Hdsl2Shdsl1DayIntervalCount 1671 MAX-ACCESS read-only 1672 STATUS current 1673 DESCRIPTION 1674 "Count of Unavailable Seconds (UAS) during the 1-day interval 1675 as measured by hdsl2Shdsl1DayIntervalMoniSecs." 1676 ::= { hdsl2Shdsl1DayIntervalEntry 7 } 1678 -- Maintenance Group 1679 -- 1681 hdsl2ShdslEndpointMaintTable OBJECT-TYPE 1682 SYNTAX SEQUENCE OF Hdsl2ShdslEndpointMaintEntry 1683 MAX-ACCESS not-accessible 1684 STATUS current 1685 DESCRIPTION 1686 "This table supports maintenance operations (eg. loopbacks) 1687 to be performed on HDSL2/SHDSL segment endpoints." 1688 ::= { hdsl2ShdslMibObjects 8 } 1690 hdsl2ShdslEndpointMaintEntry OBJECT-TYPE 1691 SYNTAX Hdsl2ShdslEndpointMaintEntry 1692 MAX-ACCESS not-accessible 1693 STATUS current 1694 DESCRIPTION 1695 "An entry in the hdsl2ShdslEndpointMaintTable. Each entry 1696 corresponds to a single segment endpoint, and is indexed by the 1697 ifIndex of the HDSL2/SHDSL line, the UnitId of the associated 1698 unit and the side of the unit." 1699 INDEX { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide } 1700 ::= { hdsl2ShdslEndpointMaintTable 1 } 1702 Hdsl2ShdslEndpointMaintEntry ::= 1703 SEQUENCE 1704 { 1705 hdsl2ShdslMaintLoopbackConfig INTEGER, 1707 Expires May 21, 2001 Page [31] 1708 hdsl2ShdslMaintTipRingReversal INTEGER, 1709 hdsl2ShdslMaintPowerBackOff INTEGER, 1710 hdsl2ShdslMaintSoftRestart INTEGER 1711 } 1713 hdsl2ShdslMaintLoopbackConfig OBJECT-TYPE 1714 SYNTAX INTEGER 1715 { 1716 noLoopback(1), 1717 normalLoopback(2), 1718 specialLoopback(3) 1719 } 1720 MAX-ACCESS read-write 1721 STATUS current 1722 DESCRIPTION 1723 "This object controls configuration of loopbacks for the 1724 associated segment endpoint. The status of the loopback 1725 is obtained via the hdsl2ShdslEndpointCurrStatus object." 1726 ::= { hdsl2ShdslEndpointMaintEntry 1 } 1728 hdsl2ShdslMaintTipRingReversal OBJECT-TYPE 1729 SYNTAX INTEGER 1730 { 1731 normal(1), 1732 reversed(2) 1733 } 1734 MAX-ACCESS read-only 1735 STATUS current 1736 DESCRIPTION 1737 "This object indicates the state of the tip/ring pair at 1738 the associated segment endpoint." 1739 ::= { hdsl2ShdslEndpointMaintEntry 2 } 1741 hdsl2ShdslMaintPowerBackOff OBJECT-TYPE 1742 SYNTAX INTEGER 1743 { 1744 default(1), 1745 enhanced(2) 1746 } 1747 MAX-ACCESS read-write 1748 STATUS current 1749 DESCRIPTION 1750 "This object configures the receiver at the associated 1751 segment endpoint to operate in default or enhanced power 1752 backoff mode." 1753 ::= { hdsl2ShdslEndpointMaintEntry 3 } 1755 hdsl2ShdslMaintSoftRestart OBJECT-TYPE 1756 SYNTAX INTEGER 1757 { 1758 ready(1), 1759 restart(2) 1761 Expires May 21, 2001 Page [32] 1762 } 1763 MAX-ACCESS read-write 1764 STATUS current 1765 DESCRIPTION 1766 "This object enables the manager to trigger a soft restart 1767 of the modem at the associated segment endpoint. The manager 1768 may only set this object to the 'restart(2)' value to initiate 1769 a restart. The agent will perform a restart after approximately 1770 5 seconds, and restore the object to the 'ready(1)' state." 1771 ::= { hdsl2ShdslEndpointMaintEntry 4 } 1773 hdsl2ShdslUnitMaintTable OBJECT-TYPE 1774 SYNTAX SEQUENCE OF Hdsl2ShdslUnitMaintEntry 1775 MAX-ACCESS not-accessible 1776 STATUS current 1777 DESCRIPTION 1778 "This table supports maintenance operations for units in a 1779 HDSL2/SHDSL line." 1780 ::= { hdsl2ShdslMibObjects 9 } 1782 hdsl2ShdslUnitMaintEntry OBJECT-TYPE 1783 SYNTAX Hdsl2ShdslUnitMaintEntry 1784 MAX-ACCESS not-accessible 1785 STATUS current 1786 DESCRIPTION 1787 "An entry in the hdsl2ShdslUnitMaintTable. Each entry 1788 corresponds to a single unit, and is indexed by the 1789 ifIndex of the HDSL2/SHDSL line and the UnitId of the 1790 associated unit." 1791 INDEX { ifIndex, hdsl2ShdslInvIndex } 1792 ::= { hdsl2ShdslUnitMaintTable 1 } 1794 Hdsl2ShdslUnitMaintEntry ::= 1795 SEQUENCE 1796 { 1797 hdsl2ShdslMaintLoopbackTimeout Integer32, 1798 hdsl2ShdslMaintUnitPowerSource INTEGER 1799 } 1801 hdsl2ShdslMaintLoopbackTimeout OBJECT-TYPE 1802 SYNTAX Integer32 1803 MAX-ACCESS read-write 1804 STATUS current 1805 DESCRIPTION 1806 "This object configures the timeout value for loopbacks 1807 initiated at segments endpoints contained in the associated 1808 unit. A value of 0 disables the timeout." 1809 ::= { hdsl2ShdslUnitMaintEntry 1 } 1811 hdsl2ShdslMaintUnitPowerSource OBJECT-TYPE 1812 SYNTAX INTEGER 1813 { 1815 Expires May 21, 2001 Page [33] 1816 local(1), 1817 span(2) 1818 } 1819 MAX-ACCESS read-only 1820 STATUS current 1821 DESCRIPTION 1822 "This object indicates the DC power source being used by the 1823 associated unit." 1824 ::= { hdsl2ShdslUnitMaintEntry 2 } 1826 -- Span Configuration Profile Group 1827 -- 1829 hdsl2ShdslSpanConfProfileTable OBJECT-TYPE 1830 SYNTAX SEQUENCE OF Hdsl2ShdslSpanConfProfileEntry 1831 MAX-ACCESS not-accessible 1832 STATUS current 1833 DESCRIPTION 1834 "This table supports definitions of span configuration 1835 profiles for SHDSL lines. HDSL2 does not support these 1836 configuration options." 1837 ::= { hdsl2ShdslMibObjects 10 } 1839 hdsl2ShdslSpanConfProfileEntry OBJECT-TYPE 1840 SYNTAX Hdsl2ShdslSpanConfProfileEntry 1841 MAX-ACCESS not-accessible 1842 STATUS current 1843 DESCRIPTION 1844 "Each entry corresponds to a single span configuration 1845 profile. Each profile contains a set of span configuration 1846 parameters. The configuration parameters in a profile are 1847 applied to those lines referencing that profile (see the 1848 hdsl2ShdslSpanConfProfile object). Profiles may be 1849 created/deleted using the row creation/deletion mechanism 1850 via hdsl2ShdslSpanConfProfileRowStatus. Profiles that are 1851 being referenced may not be deleted." 1852 INDEX { IMPLIED hdsl2ShdslSpanConfProfileName } 1853 ::= { hdsl2ShdslSpanConfProfileTable 1 } 1855 Hdsl2ShdslSpanConfProfileEntry ::= 1856 SEQUENCE 1857 { 1858 hdsl2ShdslSpanConfProfileName SnmpAdminString, 1859 hdsl2ShdslSpanWireInterface INTEGER, 1860 hdsl2ShdslSpanMinLineRate Integer32, 1861 hdsl2ShdslSpanMaxLineRate Integer32, 1862 hdsl2ShdslSpanConfPSD INTEGER, 1863 hdsl2ShdslSpanConfTransmissionMode Hdsl2ShdslTransmissionModeType, 1864 hdsl2ShdslSpanRemoteEnabled INTEGER, 1865 hdsl2ShdslSpanPowerFeeding INTEGER, 1866 hdsl2ShdslSpanConfProfileRowStatus RowStatus 1867 } 1869 Expires May 21, 2001 Page [34] 1870 hdsl2ShdslSpanConfProfileName OBJECT-TYPE 1871 SYNTAX SnmpAdminString (SIZE(1..32)) 1872 MAX-ACCESS not-accessible 1873 STATUS current 1874 DESCRIPTION 1875 "This object is the unique index associated with this profile." 1876 ::= { hdsl2ShdslSpanConfProfileEntry 1 } 1878 hdsl2ShdslSpanWireInterface OBJECT-TYPE 1879 SYNTAX INTEGER 1880 { 1881 twoWire(1), 1882 fourWire(2) 1883 } 1884 MAX-ACCESS read-create 1885 STATUS current 1886 DESCRIPTION 1887 "This object configures the two-wire or optional four-wire 1888 operation for SHDSL Lines." 1889 ::= { hdsl2ShdslSpanConfProfileEntry 2 } 1891 hdsl2ShdslSpanMinLineRate OBJECT-TYPE 1892 SYNTAX Integer32 1893 UNITS "bps" 1894 MAX-ACCESS read-create 1895 STATUS current 1896 DESCRIPTION 1897 "This object configures the minimum transmission rate for 1898 the associated SHDSL Line in bits-per-second (bps). If 1899 the minimum line rate equals the maximum line rate 1900 (hdsl2ShdslSpanMaxLineRate), the line rate is considered 1901 'fixed'. If the minimum line rate is less than the maximum 1902 line rate, the line rate is considered 'rate-adaptive'." 1903 ::= { hdsl2ShdslSpanConfProfileEntry 3 } 1905 hdsl2ShdslSpanMaxLineRate OBJECT-TYPE 1906 SYNTAX Integer32 1907 UNITS "bps" 1908 MAX-ACCESS read-create 1909 STATUS current 1910 DESCRIPTION 1911 "This object configures the maximum transmission rate for 1912 the associated SHDSL Line in bits-per-second (bps). If 1913 the minimum line rate equals the maximum line rate 1914 (hdsl2ShdslSpanMaxLineRate), the line rate is considered 1915 'fixed'. If the minimum line rate is less than the maximum 1916 line rate, the line rate is considered 'rate-adaptive'." 1917 ::= { hdsl2ShdslSpanConfProfileEntry 4 } 1919 hdsl2ShdslSpanConfPSD OBJECT-TYPE 1920 SYNTAX INTEGER 1921 { 1923 Expires May 21, 2001 Page [35] 1924 symmetric(1), 1925 asymmetric(2) 1926 } 1927 MAX-ACCESS read-create 1928 STATUS current 1929 DESCRIPTION 1930 "This object configures use of symmetric/asymmetric PSD (Power 1931 Spectral Density) Mask for the associated SHDSL Line. Support 1932 for symmetric PSD is mandatory for all supported data rates. 1933 Support for asymmetric PSD is optional." 1934 ::= { hdsl2ShdslSpanConfProfileEntry 5 } 1936 hdsl2ShdslSpanConfTransmissionMode OBJECT-TYPE 1937 SYNTAX Hdsl2ShdslTransmissionModeType 1938 MAX-ACCESS read-create 1939 STATUS current 1940 DESCRIPTION 1941 "This object specifies the regional setting for the SHDSL 1942 line." 1943 ::= { hdsl2ShdslSpanConfProfileEntry 6 } 1945 hdsl2ShdslSpanRemoteEnabled OBJECT-TYPE 1946 SYNTAX INTEGER 1947 { 1948 enabled(1), 1949 disabled(2) 1950 } 1951 MAX-ACCESS read-create 1952 STATUS current 1953 DESCRIPTION 1954 "This object enables/disables support for remote management 1955 of the units in a SHDSL line from the STU-R via the EOC." 1956 ::= { hdsl2ShdslSpanConfProfileEntry 7 } 1958 hdsl2ShdslSpanPowerFeeding OBJECT-TYPE 1959 SYNTAX INTEGER 1960 { 1961 noPower(1), 1962 powerFeed(2), 1963 wettingCurrent(3) 1964 } 1965 MAX-ACCESS read-create 1966 STATUS current 1967 DESCRIPTION 1968 "This object enables/disables support for optional power 1969 feeding in a SHDSL line." 1970 ::= { hdsl2ShdslSpanConfProfileEntry 8 } 1972 hdsl2ShdslSpanConfProfileRowStatus OBJECT-TYPE 1973 SYNTAX RowStatus 1974 MAX-ACCESS read-create 1976 Expires May 21, 2001 Page [36] 1977 STATUS current 1978 DESCRIPTION 1979 "This object controlls creation/deletion of the associated 1980 entry in this table per the semantics of RowStatus." 1981 ::= { hdsl2ShdslSpanConfProfileEntry 9 } 1983 -- Segment Endpoint Alarm Configuration Profile group 1984 -- 1986 hdsl2ShdslEndpointAlarmConfProfileTable OBJECT-TYPE 1987 SYNTAX SEQUENCE OF Hdsl2ShdslEndpointAlarmConfProfileEntry 1988 MAX-ACCESS not-accessible 1989 STATUS current 1990 DESCRIPTION 1991 "This table supports definitions of alarm configuration 1992 profiles for HDSL2/SHDSL segment endoints." 1993 ::= { hdsl2ShdslMibObjects 11 } 1995 hdsl2ShdslEndpointAlarmConfProfileEntry OBJECT-TYPE 1996 SYNTAX Hdsl2ShdslEndpointAlarmConfProfileEntry 1997 MAX-ACCESS not-accessible 1998 STATUS current 1999 DESCRIPTION 2000 "Each entry corresponds to a single alarm configuration 2001 profile. Each profile contains a set of parameters for setting 2002 alarm thresholds for various performance attributes monitored 2003 at HDSL2/SHDSL segment endpoints. Profiles may be 2004 created/deleted using the row creation/deletion mechanism via 2005 hdsl2ShdslEndpointAlarmConfProfileRowStatus. Profiles that 2006 are being referenced may not be deleted." 2007 INDEX { IMPLIED hdsl2ShdslEndpointAlarmConfProfileName } 2008 ::= { hdsl2ShdslEndpointAlarmConfProfileTable 1 } 2010 Hdsl2ShdslEndpointAlarmConfProfileEntry ::= 2011 SEQUENCE 2012 { 2013 hdsl2ShdslEndpointAlarmConfProfileName SnmpAdminString, 2014 hdsl2ShdslEndpointThreshLoopAttenuation Integer32, 2015 hdsl2ShdslEndpointThreshSNRMargin Integer32, 2016 hdsl2ShdslEndpointThreshES 2017 Hdsl2ShdslPerfIntervalThreshold, 2018 hdsl2ShdslEndpointThreshSES 2019 Hdsl2ShdslPerfIntervalThreshold, 2020 hdsl2ShdslEndpointThreshCRCanomalies Integer32, 2021 hdsl2ShdslEndpointThreshLOSWS 2022 Hdsl2ShdslPerfIntervalThreshold, 2023 hdsl2ShdslEndpointThreshUAS 2024 Hdsl2ShdslPerfIntervalThreshold, 2025 hdsl2ShdslEndpointAlarmConfProfileRowStatus RowStatus 2026 } 2028 hdsl2ShdslEndpointAlarmConfProfileName OBJECT-TYPE 2030 Expires May 21, 2001 Page [37] 2031 SYNTAX SnmpAdminString (SIZE(1..32)) 2032 MAX-ACCESS not-accessible 2033 STATUS current 2034 DESCRIPTION 2035 "This object is the unique index associated with this profile." 2036 ::= { hdsl2ShdslEndpointAlarmConfProfileEntry 1 } 2038 hdsl2ShdslEndpointThreshLoopAttenuation OBJECT-TYPE 2039 SYNTAX Integer32 2040 UNITS "dB" 2041 MAX-ACCESS read-create 2042 STATUS current 2043 DESCRIPTION 2044 "This object configures the loop attentuation alarm threshold. 2045 When the current value reaches/exceeds this threshold, a 2046 hdsl2ShdslLoopAttenCrossingTrap will be generated." 2047 ::= { hdsl2ShdslEndpointAlarmConfProfileEntry 2 } 2049 hdsl2ShdslEndpointThreshSNRMargin OBJECT-TYPE 2050 SYNTAX Integer32 2051 UNITS "dB" 2052 MAX-ACCESS read-create 2053 STATUS current 2054 DESCRIPTION 2055 "This object configures the SNR margin alarm threshold. 2056 When the current value reaches/exceeds this threshold, a 2057 hdsl2ShdslSNRMarginCrossingTrap will be generated." 2058 ::= { hdsl2ShdslEndpointAlarmConfProfileEntry 3 } 2060 hdsl2ShdslEndpointThreshES OBJECT-TYPE 2061 SYNTAX Hdsl2ShdslPerfIntervalThreshold 2062 UNITS "seconds" 2063 MAX-ACCESS read-create 2064 STATUS current 2065 DESCRIPTION 2066 "This object configures the threshold for the number of 2067 errored seconds (ES) within any given 15-minute performance 2068 data collection interval. If the value of errored seconds 2069 in a particular 15-minute collection interval reaches/ 2070 exceeds this value, a hdsl2ShdslPerfESThreshTrap will be 2071 generated. One trap will be sent per interval per 2072 endpoint." 2073 ::= { hdsl2ShdslEndpointAlarmConfProfileEntry 4 } 2075 hdsl2ShdslEndpointThreshSES OBJECT-TYPE 2076 SYNTAX Hdsl2ShdslPerfIntervalThreshold 2077 UNITS "seconds" 2078 MAX-ACCESS read-create 2079 STATUS current 2080 DESCRIPTION 2081 "This object configures the threshold for the number of 2082 severely errored seconds (SES) within any given 15-minute 2084 Expires May 21, 2001 Page [38] 2085 performance data collection interval. If the value of severely 2086 errored seconds in a particular 15-minute collection interval 2087 reaches/exceeds this value, a hdsl2ShdslPerfSESThreshTrap will 2088 be generated. One trap will be sent per interval per endpoint." 2089 ::= { hdsl2ShdslEndpointAlarmConfProfileEntry 5 } 2091 hdsl2ShdslEndpointThreshCRCanomalies OBJECT-TYPE 2092 SYNTAX Integer32 2093 MAX-ACCESS read-create 2094 STATUS current 2095 DESCRIPTION 2096 "This object configures the threshold for the number of 2097 CRC anomalies within any given 15-minute performance data 2098 collection interval. If the value of CRC anomalies in a 2099 particular 15-minute collection interval reaches/exceeds 2100 this value, a hdsl2ShdslPerfCRCanomaliesThreshTrap will be 2101 generated. One trap will be sent per interval per endpoint." 2102 ::= { hdsl2ShdslEndpointAlarmConfProfileEntry 6 } 2104 hdsl2ShdslEndpointThreshLOSWS OBJECT-TYPE 2105 SYNTAX Hdsl2ShdslPerfIntervalThreshold 2106 UNITS "seconds" 2107 MAX-ACCESS read-create 2108 STATUS current 2109 DESCRIPTION 2110 "This object configures the threshold for the number of 2111 loss of sync word seconds (LOSWS) within any given 15-minute 2112 performance data collection interval. If the value of LOSWS 2113 in a particular 15-minute collection interval reaches/exceeds 2114 this value, a hdsl2ShdslPerfLOSWSThreshTrap will be generated. 2115 One trap will be sent per interval per endpoint." 2116 ::= { hdsl2ShdslEndpointAlarmConfProfileEntry 7 } 2118 hdsl2ShdslEndpointThreshUAS OBJECT-TYPE 2119 SYNTAX Hdsl2ShdslPerfIntervalThreshold 2120 UNITS "seconds" 2121 MAX-ACCESS read-create 2122 STATUS current 2123 DESCRIPTION 2124 "This object configures the threshold for the number of 2125 unavailable seconds (UAS) within any given 15-minute 2126 performance data collection interval. If the value of UAS 2127 in a particular 15-minute collection interval reaches/exceeds 2128 this value, a hdsl2ShdslPerfUASThreshTrap will be generated. 2129 One trap will be sent per interval per endpoint." 2130 ::= { hdsl2ShdslEndpointAlarmConfProfileEntry 8 } 2132 hdsl2ShdslEndpointAlarmConfProfileRowStatus OBJECT-TYPE 2133 SYNTAX RowStatus 2134 MAX-ACCESS read-create 2135 STATUS current 2136 DESCRIPTION 2138 Expires May 21, 2001 Page [39] 2139 "This object controls creation/deletion of the associated 2140 entry in this table as per the semantics of RowStatus." 2141 ::= { hdsl2ShdslEndpointAlarmConfProfileEntry 9 } 2143 -- Notifications Group 2144 -- 2146 hdsl2ShdslTraps OBJECT IDENTIFIER ::= { hdsl2ShdslLineMib 2 } 2147 hdsl2ShdslTrapsPrefix OBJECT IDENTIFIER ::= { hdsl2ShdslTraps 0 } 2149 hdsl2ShdslLoopAttenCrossingTrap NOTIFICATION-TYPE 2150 OBJECTS 2151 { 2152 ifIndex, 2153 hdsl2ShdslInvIndex, 2154 hdsl2ShdslEndpointSide, 2155 hdsl2ShdslEndpointWirePair, 2156 hdsl2ShdslEndpointCurrAtn, 2157 hdsl2ShdslEndpointThreshLoopAttenuation 2158 } 2159 STATUS current 2160 DESCRIPTION 2161 "This trap indicates that the loop attenuation threshold (as 2162 per the hdsl2ShdslEndpointThreshLoopAttenuation value) has been 2163 reached/exceeded for the HDSL2/SHDSL segment endpoint identified 2164 by the ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide, and 2165 hdsl2ShdslEndpointWirePair values." 2166 ::= { hdsl2ShdslTrapsPrefix 1 } 2168 hdsl2ShdslSNRMarginCrossingTrap NOTIFICATION-TYPE 2169 OBJECTS 2170 { 2171 ifIndex, 2172 hdsl2ShdslInvIndex, 2173 hdsl2ShdslEndpointSide, 2174 hdsl2ShdslEndpointWirePair, 2175 hdsl2ShdslEndpointCurrSnrMgn, 2176 hdsl2ShdslEndpointThreshSNRMargin 2177 } 2178 STATUS current 2179 DESCRIPTION 2180 "This trap indicates that the SNR margin threshold (as per the 2181 hdsl2ShdslEndpointThreshSNRMargin value) has been 2182 reached/exceeded for the HDSL2/SHDSL segment endpoint identified 2183 by the ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide, and 2184 hdsl2ShdslEndpointWirePair values." 2185 ::= { hdsl2ShdslTrapsPrefix 2 } 2187 hdsl2ShdslPerfESThreshTrap NOTIFICATION-TYPE 2188 OBJECTS 2189 { 2190 ifIndex, 2192 Expires May 21, 2001 Page [40] 2193 hdsl2ShdslInvIndex, 2194 hdsl2ShdslEndpointSide, 2195 hdsl2ShdslEndpointWirePair, 2196 hdsl2ShdslEndpointCurr15MinES, 2197 hdsl2ShdslEndpointThreshES 2198 } 2199 STATUS current 2200 DESCRIPTION 2201 "This trap indicates that the errored seconds threshold (as 2202 per the hdsl2ShdslEndpointThreshES value) has been reached/ 2203 exceeded for the HDSL2/SHDSL segment endpoint identified by the 2204 ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide, and 2205 hdsl2ShdslEndpointWirePair values." 2206 ::= { hdsl2ShdslTrapsPrefix 3 } 2208 hdsl2ShdslPerfSESThreshTrap NOTIFICATION-TYPE 2209 OBJECTS 2210 { 2211 ifIndex, 2212 hdsl2ShdslInvIndex, 2213 hdsl2ShdslEndpointSide, 2214 hdsl2ShdslEndpointWirePair, 2215 hdsl2ShdslEndpointCurr15MinSES, 2216 hdsl2ShdslEndpointThreshSES 2217 } 2218 STATUS current 2219 DESCRIPTION 2220 "This trap indicates that the severely errored seconds threshold 2221 (as per the hdsl2ShdslEndpointThreshSES value) has been reached/ 2222 exceeded for the HDSL2/SHDSL Segment Endpoint identified by the 2223 ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide, and 2224 hdsl2ShdslEndpointWirePair values." 2225 ::= { hdsl2ShdslTrapsPrefix 4 } 2227 hdsl2ShdslPerfCRCanomaliesThreshTrap NOTIFICATION-TYPE 2228 OBJECTS 2229 { 2230 ifIndex, 2231 hdsl2ShdslInvIndex, 2232 hdsl2ShdslEndpointSide, 2233 hdsl2ShdslEndpointWirePair, 2234 hdsl2ShdslEndpointCurr15MinCRCanomalies, 2235 hdsl2ShdslEndpointThreshCRCanomalies 2236 } 2237 STATUS current 2238 DESCRIPTION 2239 "This trap indicates that the CRC anomalies threshold (as 2240 per the hdsl2ShdslEndpointThreshCRCanomalies value) has been 2241 reached/exceeded for the HDSL2/SHDSL Segment Endpoint identified 2242 by the ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide, and 2243 hdsl2ShdslEndpointWirePair values." 2244 ::= { hdsl2ShdslTrapsPrefix 5 } 2246 Expires May 21, 2001 Page [41] 2247 hdsl2ShdslPerfLOSWSThreshTrap NOTIFICATION-TYPE 2248 OBJECTS 2249 { 2250 ifIndex, 2251 hdsl2ShdslInvIndex, 2252 hdsl2ShdslEndpointSide, 2253 hdsl2ShdslEndpointWirePair, 2254 hdsl2ShdslEndpointCurr15MinLOSWS, 2255 hdsl2ShdslEndpointThreshLOSWS 2256 } 2257 STATUS current 2258 DESCRIPTION 2259 "This trap indicates that the LOSW seconds threshold (as per the 2260 hdsl2ShdslEndpointThreshLOSWS value) has been reached/exceeded 2261 for the HDSL2/SHDSL segment endpoint identified by the ifIndex, 2262 hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide, and 2263 hdsl2ShdslEndpointWirePair values." 2264 ::= { hdsl2ShdslTrapsPrefix 6 } 2266 hdsl2ShdslPerfUASThreshTrap NOTIFICATION-TYPE 2267 OBJECTS 2268 { 2269 ifIndex, 2270 hdsl2ShdslInvIndex, 2271 hdsl2ShdslEndpointSide, 2272 hdsl2ShdslEndpointWirePair, 2273 hdsl2ShdslEndpointCurr15MinUAS, 2274 hdsl2ShdslEndpointThreshUAS 2275 } 2276 STATUS current 2277 DESCRIPTION 2278 "This trap indicates that the unavailable seconds threshold (as 2279 per the hdsl2ShdslEndpointThreshUAS value) has been reached/ 2280 exceeded for the HDSL2/SHDSL segment endpoint identified by the 2281 ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide, and 2282 hdsl2ShdslEndpointWirePair values." 2283 ::= { hdsl2ShdslTrapsPrefix 7 } 2285 hdsl2ShdslSpanInvalidNumRepeaters NOTIFICATION-TYPE 2286 OBJECTS 2287 { 2288 ifIndex, 2289 hdsl2ShdslConfNumRepeaters 2290 } 2291 STATUS current 2292 DESCRIPTION 2293 "This trap indicates that a mismatch has been detected between 2294 the number of repeater/regenerator units configured for a 2295 HDSL2/SHDSL line via the hdsl2ShdslConfNumRepeaters object and 2296 the actual number of repeater/regenerator units discovered via 2297 the EOC." 2298 ::= { hdsl2ShdslTrapsPrefix 8 } 2300 Expires May 21, 2001 Page [42] 2301 hdsl2ShdslLoopbackFailure NOTIFICATION-TYPE 2302 OBJECTS 2303 { 2304 ifIndex, 2305 hdsl2ShdslInvIndex, 2306 hdsl2ShdslEndpointSide, 2307 hdsl2ShdslMaintLoopbackConfig 2308 } 2309 STATUS current 2310 DESCRIPTION 2311 "This trap indicates that an endpoint maintenance loopback 2312 command failed for an HDSL2/SHDSL segment." 2313 ::= { hdsl2ShdslTrapsPrefix 9 } 2315 -- conformance information 2316 -- 2318 hdsl2ShdslConformance OBJECT IDENTIFIER ::= { hdsl2ShdslLineMib 3 } 2319 hdsl2ShdslGroups OBJECT IDENTIFIER ::= { hdsl2ShdslConformance 1 } 2320 hdsl2ShdslCompliances OBJECT IDENTIFIER ::= { hdsl2ShdslConformance 2 } 2322 -- agent compliance statements 2324 hdsl2ShdslLineMibCompliance MODULE-COMPLIANCE 2325 STATUS current 2326 DESCRIPTION 2327 "The section outlines compliance requirements for this MIB." 2328 MODULE 2329 MANDATORY-GROUPS 2330 { 2331 hdsl2ShdslSpanConfGroup, 2332 hdsl2ShdslSpanStatusGroup, 2333 hdsl2ShdslInventoryGroup, 2334 hdsl2ShdslEndpointConfGroup, 2335 hdsl2ShdslEndpointCurrGroup, 2336 hdsl2Shdsl15MinIntervalGroup, 2337 hdsl2Shdsl1DayIntervalGroup, 2338 hdsl2ShdslMaintenanceGroup, 2339 hdsl2ShdslEndpointAlarmConfGroup, 2340 hdsl2ShdslNotificationGroup 2341 } 2343 GROUP hdsl2ShdslInventoryShdslGroup 2344 DESCRIPTION 2345 "Support for this group is only required for implementations 2346 supporting SHDSL lines." 2348 GROUP hdsl2ShdslSpanShdslStatusGroup 2349 DESCRIPTION 2350 "Support for this group is only required for implementations 2351 supporting SHDSL lines." 2353 Expires May 21, 2001 Page [43] 2354 GROUP hdsl2ShdslSpanConfProfileGroup 2355 DESCRIPTION 2356 "Support for this group is only required for implementations 2357 supporting SHDSL lines." 2359 ::= { hdsl2ShdslCompliances 1 } 2361 -- units of conformance 2362 -- 2364 hdsl2ShdslSpanConfGroup OBJECT-GROUP 2365 OBJECTS 2366 { 2367 hdsl2ShdslConfNumRepeaters, 2368 hdsl2ShdslSpanConfProfile, 2369 hdsl2ShdslSpanAlarmConfProfile 2370 } 2371 STATUS current 2372 DESCRIPTION 2373 "This group supports objects for configuring span related 2374 parameters for HDSL2/SHDSL lines." 2375 ::= { hdsl2ShdslGroups 1 } 2377 hdsl2ShdslSpanStatusGroup OBJECT-GROUP 2378 OBJECTS 2379 { 2380 hdsl2ShdslStatusNumAvailRepeaters 2381 } 2382 STATUS current 2383 DESCRIPTION 2384 "This group supports objects for retrieving span related 2385 status for HDSL2/SHDSL lines." 2386 ::= { hdsl2ShdslGroups 2 } 2388 hdsl2ShdslInventoryShdslGroup OBJECT-GROUP 2389 OBJECTS 2390 { 2391 hdsl2ShdslInvTransmissionModeCapability 2392 } 2393 STATUS current 2394 DESCRIPTION 2395 "This group supports objects for retrieving SHDSL-specific 2396 inventory information." 2397 ::= { hdsl2ShdslGroups 3 } 2399 hdsl2ShdslSpanShdslStatusGroup OBJECT-GROUP 2400 OBJECTS 2401 { 2402 hdsl2ShdslStatusMaxAttainableLineRate, 2403 hdsl2ShdslStatusActualLineRate, 2404 hdsl2ShdslStatusTransmissionModeCurrent 2405 } 2407 Expires May 21, 2001 Page [44] 2408 STATUS current 2409 DESCRIPTION 2410 "This group supports objects for retrieving SHDSL-specific 2411 span related status." 2412 ::= { hdsl2ShdslGroups 4 } 2414 hdsl2ShdslInventoryGroup OBJECT-GROUP 2415 OBJECTS 2416 { 2417 hdsl2ShdslInvIndex, 2418 hdsl2ShdslInvVendorID, 2419 hdsl2ShdslInvVendorModelNumber, 2420 hdsl2ShdslInvVendorSerialNumber, 2421 hdsl2ShdslInvVendorEOCSoftwareVersion, 2422 hdsl2ShdslInvStandardVersion, 2423 hdsl2ShdslInvVendorListNumber, 2424 hdsl2ShdslInvVendorIssueNumber, 2425 hdsl2ShdslInvVendorSoftwareVersion, 2426 hdsl2ShdslInvEquipmentCode, 2427 hdsl2ShdslInvVendorOther 2428 } 2429 STATUS current 2430 DESCRIPTION 2431 "This group supports objects that provide unit inventory 2432 information about the units in HDSL2/SHDSL lines." 2433 ::= { hdsl2ShdslGroups 5 } 2435 hdsl2ShdslEndpointConfGroup OBJECT-GROUP 2436 OBJECTS 2437 { 2438 hdsl2ShdslEndpointSide, 2439 hdsl2ShdslEndpointWirePair, 2440 hdsl2ShdslEndpointAlarmConfProfile 2441 } 2442 STATUS current 2443 DESCRIPTION 2444 "This group supports objects for configuring parameters for 2445 segment endpoints in HDSL2/SHDSL lines." 2446 ::= { hdsl2ShdslGroups 6 } 2448 hdsl2ShdslEndpointCurrGroup OBJECT-GROUP 2449 OBJECTS 2450 { 2451 hdsl2ShdslEndpointSide, 2452 hdsl2ShdslEndpointWirePair, 2453 hdsl2ShdslEndpointCurrAtn, 2454 hdsl2ShdslEndpointCurrSnrMgn, 2455 hdsl2ShdslEndpointCurrStatus, 2456 hdsl2ShdslEndpointES, 2457 hdsl2ShdslEndpointSES, 2458 hdsl2ShdslEndpointCRCanomalies, 2459 hdsl2ShdslEndpointLOSWS, 2461 Expires May 21, 2001 Page [45] 2462 hdsl2ShdslEndpointUAS, 2463 hdsl2ShdslEndpointCurr15MinTimeElapsed, 2464 hdsl2ShdslEndpointCurr15MinES, 2465 hdsl2ShdslEndpointCurr15MinSES, 2466 hdsl2ShdslEndpointCurr15MinCRCanomalies, 2467 hdsl2ShdslEndpointCurr15MinLOSWS, 2468 hdsl2ShdslEndpointCurr15MinUAS, 2469 hdsl2ShdslEndpointCurr1DayTimeElapsed, 2470 hdsl2ShdslEndpointCurr1DayES, 2471 hdsl2ShdslEndpointCurr1DaySES, 2472 hdsl2ShdslEndpointCurr1DayCRCanomalies, 2473 hdsl2ShdslEndpointCurr1DayLOSWS, 2474 hdsl2ShdslEndpointCurr1DayUAS 2475 } 2476 STATUS current 2477 DESCRIPTION 2478 "This group supports objects which provide current status and 2479 performance measurements relating to segment endpoints in 2480 HDSL2/SHDSL lines." 2481 ::= { hdsl2ShdslGroups 7 } 2483 hdsl2Shdsl15MinIntervalGroup OBJECT-GROUP 2484 OBJECTS 2485 { 2486 hdsl2Shdsl15MinIntervalES, 2487 hdsl2Shdsl15MinIntervalSES, 2488 hdsl2Shdsl15MinIntervalCRCanomalies, 2489 hdsl2Shdsl15MinIntervalLOSWS, 2490 hdsl2Shdsl15MinIntervalUAS 2491 } 2492 STATUS current 2493 DESCRIPTION 2494 "This group supports objects which maintain historic performance 2495 measurements relating to segment endpoints in HDSL2/SHDSL lines 2496 in 15-minute intervals." 2497 ::= { hdsl2ShdslGroups 8 } 2499 hdsl2Shdsl1DayIntervalGroup OBJECT-GROUP 2500 OBJECTS 2501 { 2502 hdsl2Shdsl1DayIntervalMoniSecs, 2503 hdsl2Shdsl1DayIntervalES, 2504 hdsl2Shdsl1DayIntervalSES, 2505 hdsl2Shdsl1DayIntervalCRCanomalies, 2506 hdsl2Shdsl1DayIntervalLOSWS, 2507 hdsl2Shdsl1DayIntervalUAS 2508 } 2509 STATUS current 2510 DESCRIPTION 2511 "This group supports objects which maintain historic performance 2512 measurements relating to segment endpoints in HDSL2/SHDSL lines 2513 in 1-day intervals." 2514 ::= { hdsl2ShdslGroups 9 } 2516 Expires May 21, 2001 Page [46] 2517 hdsl2ShdslMaintenanceGroup OBJECT-GROUP 2518 OBJECTS 2519 { 2520 hdsl2ShdslMaintLoopbackConfig, 2521 hdsl2ShdslMaintTipRingReversal, 2522 hdsl2ShdslMaintPowerBackOff, 2523 hdsl2ShdslMaintSoftRestart, 2524 hdsl2ShdslMaintLoopbackTimeout, 2525 hdsl2ShdslMaintUnitPowerSource 2526 } 2527 STATUS current 2528 DESCRIPTION 2529 "This group supports objects that provide support for 2530 maintenance actions for HDSL2/SHDSL lines." 2531 ::= { hdsl2ShdslGroups 10 } 2533 hdsl2ShdslEndpointAlarmConfGroup OBJECT-GROUP 2534 OBJECTS 2535 { 2536 hdsl2ShdslEndpointThreshLoopAttenuation, 2537 hdsl2ShdslSpanWireInterface, 2538 hdsl2ShdslEndpointThreshSNRMargin, 2539 hdsl2ShdslEndpointThreshES, 2540 hdsl2ShdslEndpointThreshSES, 2541 hdsl2ShdslEndpointThreshCRCanomalies, 2542 hdsl2ShdslEndpointThreshLOSWS, 2543 hdsl2ShdslEndpointThreshUAS, 2544 hdsl2ShdslEndpointAlarmConfProfileRowStatus 2545 } 2546 STATUS current 2547 DESCRIPTION 2548 "This group supports objects that allow configuration of alarm 2549 thresholds for various performance parameters for HDSL2/SHDSL 2550 lines." 2551 ::= { hdsl2ShdslGroups 11 } 2553 hdsl2ShdslNotificationGroup NOTIFICATION-GROUP 2554 NOTIFICATIONS 2555 { 2556 hdsl2ShdslLoopAttenCrossingTrap, 2557 hdsl2ShdslSNRMarginCrossingTrap, 2558 hdsl2ShdslPerfESThreshTrap, 2559 hdsl2ShdslPerfSESThreshTrap, 2560 hdsl2ShdslPerfCRCanomaliesThreshTrap, 2561 hdsl2ShdslPerfLOSWSThreshTrap, 2562 hdsl2ShdslPerfUASThreshTrap, 2563 hdsl2ShdslSpanInvalidNumRepeaters, 2564 hdsl2ShdslLoopbackFailure 2565 } 2566 STATUS current 2567 DESCRIPTION 2568 "This group supports traps that enable notification of 2570 Expires May 21, 2001 Page [47] 2571 significant events/conditions associated with HDSL2/SHDSL 2572 lines." 2573 ::= { hdsl2ShdslGroups 12 } 2575 hdsl2ShdslSpanConfProfileGroup OBJECT-GROUP 2576 OBJECTS 2577 { 2578 hdsl2ShdslSpanWireInterface, 2579 hdsl2ShdslSpanMinLineRate, 2580 hdsl2ShdslSpanMaxLineRate, 2581 hdsl2ShdslSpanConfPSD, 2582 hdsl2ShdslSpanConfTransmissionMode, 2583 hdsl2ShdslSpanRemoteEnabled, 2584 hdsl2ShdslSpanPowerFeeding, 2585 hdsl2ShdslSpanConfProfileRowStatus 2586 } 2587 STATUS current 2588 DESCRIPTION 2589 "This group supports objects that constitute configuration 2590 profiles for configuring span related parameters in SHDSL 2591 lines." 2592 ::= { hdsl2ShdslGroups 13 } 2594 END 2596 7. Security Considerations 2598 Security issues are not discussed in this memo. 2600 8. Acknowledgments 2602 The authors are deeply grateful to the authors of the ADSL LINE MIB 2603 (RFC 2662 [25]), Gregory Bathrick and Faye Ly, as much of the text 2604 and structure of this document originates in their documents. 2606 The authors also acknowledge the importance of contributions and 2607 suggestions regarding interface indexing structures received from 2608 David Horton of CITR. 2610 Other contributions were received from the following: 2612 Philip Bergstresser (Adtran) 2614 Steve Blackwell (Adtran) 2616 Mark Johnson (Red Point) 2618 Sharon Mantin (Orckit) 2620 Moti Morgenstern (ECI) 2622 Raymond Murphy (Ericsson) 2624 Expires May 21, 2001 Page [48] 2625 Katy Sherman (Orckit) 2627 Mike Sneed (ECI) 2629 Aron Wahl (Memotec) 2631 Michael Wrobel (Memotec) 2633 9. References 2635 [1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 2636 Describing SNMP Management Frameworks", RFC 2571, April 1999. 2638 [2] Rose, M., and K. McCloghrie, "Structure and Identification of 2639 Management Information for TCP/IP-based Internets", STD 16, RFC 2640 1155, May 1990. 2642 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 16, 2643 RFC 1212, March 1991. 2645 [4] M. Rose, "A Convention for Defining Traps for use with the SNMP", 2646 RFC 1215, March 1991. 2648 [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 2649 M., and S. Waldbusser, "Structure of Management Information 2650 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 2652 [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 2653 M., and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, 2654 RFC 2579, April 1999. 2656 [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 2657 M., and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, 2658 RFC 2580, April 1999. 2660 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 2661 Network Management Protocol", STD 15, RFC 1157, May 1990. 2663 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2664 "Introduction to Community-based SNMPv2", RFC 1901, January 2665 1996. 2667 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport 2668 Mappings for Version 2 of the Simple Network Management Protocol 2669 (SNMPv2)", RFC 1906, January 1996. 2671 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 2672 Processing and Dispatching for the Simple Network Management 2673 Protocol (SNMP)", RFC 2572, April 1999. 2675 [12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) 2676 for version 3 of the Simple Network Management Protocol (SNMPv3)", 2677 RFC 2574, April 1999. 2679 Expires May 21, 2001 Page [49] 2680 [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 2681 Operations for Version 2 of the Simple Network Management Protocol 2682 (SNMPv2)", RFC 1905, January 1996. 2684 [14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 2685 2573, April 1999. 2687 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 2688 Control Model (VACM) for the Simple Network Management Protocol 2689 (SNMP)", RFC 2575, April 1999. 2691 [16] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction to 2692 Version 3 of the Internet-standard Network Management Framework", 2693 RFC 2570, April 1999. 2695 [17] Bradner, S., "Key Words for use in RFCs to Indicate Requirement 2696 Levels", RFC 2119, March 1997. 2698 [18] American National Standards Institute, ANSI T1E1.4/2000-006, 2699 February 2000. 2701 [19] Blackwell, S., Editor, "Single-Pair High-Speed Digital Subscriber 2702 Line (SHDSL) Transceivers", ITU-T Draft G.991.2, April 2000. 2704 [20] McCloghrie, K., and M. Rose, Editors, "Management Information Base 2705 for Network Management of TCP/IP-based internets: MIB-II", STD 17, 2706 RFC 1213, March 1991. 2708 [21] McCloghrie, K., and Kastenholz, F., "The Interfaces Group MIB", 2709 RFC 2863, June 2000. 2711 [22] Tesink, K., "Textual Conventions for MIB Modules Using Performance 2712 History Based on 15 Minute Intervals", RFC 2493, January 1999. 2714 [23] Bathrick, G., Ly, F., "Definitions of Managed Objects for the ADSL 2715 Lines", RFC 2662, August 1999. 2717 10. Intellectual Property Notice 2719 The IETF takes no position regarding the validity or scope of any 2720 intellectual property or other rights that might be claimed to 2721 pertain to the implementation or use of the technology described in 2722 this document or the extent to which any license under such rights 2723 might or might not be available; neither does it represent that it 2724 has made any effort to identify any such rights. Information on the 2725 IETF's procedures with respect to rights in standards-track and 2726 standards-related documentation can be found in BCP-11. Copies of 2727 claims of rights made available for publication and any assurances of 2728 licenses to be made available, or the result of an attempt made to 2729 obtain a general license or permission for the use of such 2730 proprietary rights by implementors or users of this specification can 2731 be obtained from the IETF Secretariat. 2733 Expires May 21, 2001 Page [50] 2734 The IETF invites any interested party to bring to its attention any 2735 copyrights, patents or patent applications, or other proprietary 2736 rights which may cover technology that may be required to practice 2737 this standard. Please address the information to the IETF Executive 2738 Director. 2740 11. Authors' Addresses 2742 Bob Ray 2743 Verilink Corporation 2744 127 Jetplex Circle 2745 Madison, AL 35758 USA 2746 Tel: +1 256-774-2380 2747 Fax: +1 256-774-2277 2748 E-mail: bray@verilink.com 2750 Rajesh Abbi 2751 Alcatel USA 2752 2912 Wake Forest Road 2753 Raleigh, NC 27609-7860 USA 2754 Tel: +1 919-950-6194 2755 Fax: +1 919-950-6670 2756 E-mail: Rajesh.Abbi@usa.alcatel.com 2758 12. Full Copyright Statement 2760 Copyright (C) The Internet Society (1999). All Rights Reserved. 2762 This document and translations of it may be copied and furnished to 2763 others, and derivative works that comment on or otherwise explain it 2764 or assist in its implementation may be prepared, copied, published 2765 and distributed, in whole or in part, without restriction of any 2766 kind, provided that the above copyright notice and this paragraph are 2767 included on all such copies and derivative works. However, this 2768 document itself may not be modified in any way, such as by removing 2769 the copyright notice or references to the Internet Society or other 2770 Internet organizations, except as needed for the purpose of 2771 developing Internet standards in which case the procedures for 2772 copyrights defined in the Internet Standards process must be 2773 followed, or as required to translate it into languages other than 2774 English. 2776 The limited permissions granted above are perpetual and will not be 2777 revoked by the Internet Society or its successors or assigns. 2779 This document and the information contained herein is provided on an 2780 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 2781 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 2782 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 2783 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 2784 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 2786 Expires May 21, 2001 Page [51]