idnits 2.17.1 draft-ietf-adslmib-hdsl2-02.txt: ** The Abstract section seems to be numbered Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 1) being 2704 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. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 813 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 (August 2000) is 8648 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 1340, but not defined == Missing Reference: '25' is mentioned on line 2350, but not defined == Missing Reference: '26' is mentioned on line 1453, but not defined == Missing Reference: '27' is mentioned on line 1508, but not defined == Missing Reference: '28' is mentioned on line 1565, but not defined == Missing Reference: '29' is mentioned on line 1622, but not defined == Missing Reference: '30' is mentioned on line 1679, but not defined == Missing Reference: '31' is mentioned on line 1736, but not defined == Missing Reference: '32' is mentioned on line 1793, but not defined == Missing Reference: '33' is mentioned on line 1850, but not defined == Missing Reference: '34' is mentioned on line 1907, but not defined == Missing Reference: '35' is mentioned on line 1964, but not defined == Missing Reference: '36' is mentioned on line 2019, but not defined == Missing Reference: '37' is mentioned on line 2076, but not defined == Missing Reference: '38' is mentioned on line 2133, but not defined == Missing Reference: '39' is mentioned on line 2190, but not defined == Missing Reference: '40' is mentioned on line 2247, but not defined == Missing Reference: '41' is mentioned on line 2304, but not defined == Missing Reference: '42' is mentioned on line 2361, but not defined == Missing Reference: '43' is mentioned on line 2418, but not defined == Missing Reference: '44' is mentioned on line 2475, but not defined == Missing Reference: '45' is mentioned on line 2526, 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 (~~), 26 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 August 2000 8 Definitions of Managed Objects for HDSL2 and SHDSL Lines 9 draft-ietf-adslmib-hdsl2-02.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 November 8, 2000 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 ................. 8 53 4.5 Profiles .................................................. 9 54 4.6 Traps ..................................................... 10 55 5. Conformance and Compliance ................................ 11 56 6. Definitions ............................................... 11 57 7. Security Considerations ................................... 42 58 8. Acknowledgments ........................................... 42 59 9. References ................................................ 43 60 10. Intellectual Property Notice .............................. 44 61 11. Authors' Addresses ........................................ 45 62 12. Full Copyright Statement .................................. 45 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 94 RFC 1906 [10]. The third version of the message protocol is 95 called SNMPv3 and described in RFC 1906 [10], RFC 2572 [11] and 96 RFC 2574 [12]. 98 Expires November 8, 2000 Page [2] 99 o Protocol operations for accessing management information. The 100 first set of protocol operations and associated PDU formats is 101 described in STD 15, RFC 1157 [8]. A second set of protocol 102 operations and associated PDU formats is described in RFC 1905 103 [13]. 105 o A set of fundamental applications described in RFC 2573 [14] 106 and the view-based access control mechanism described in RFC 107 2575 [15]. 109 A more detailed introduction to the current SNMP Management Framework 110 can be found in RFC 2570 [16]. 112 Managed objects are accessed via a virtual information store, termed 113 the Management Information Base or MIB. Objects in the MIB are 114 defined using the mechanisms defined in the SMI. 116 This memo specifies a MIB module that is compliant to the SMIv2. A 117 MIB conforming to the SMIv1 can be produced through the appropriate 118 translations. The resulting translated MIB must be semantically 119 equivalent, except where objects or events are omitted because no 120 translation is possible (use of Counter64). Some machine readable 121 information in SMIv2 will be converted into textual descriptions in 122 SMIv1 during the translation process. However, this loss of machine 123 readable information is not considered to change the semantics of the 124 MIB. 126 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 127 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 128 this document are to be interpreted as described in RFC 2119 [17]. 130 2.1. Object Definitions 132 Managed objects are accessed via a virtual information store, termed 133 the Management Information Base or MIB. Objects in the MIB are 134 defined using the subset of Abstract Syntax Notation One (ASN.1) 135 defined in the SMI. In particular, each object type is named by an 136 OBJECT IDENTIFIER, an administratively assigned name. The object 137 type together with an object instance serves to uniquely identify a 138 specific instantiation of the object. For human convenience, we 139 often use a textual string, termed the descriptor, to also refer to 140 the object type. 142 3. Introduction 144 This document describes an SNMP MIB for managing HDSL2/SHDSL Lines. 145 The MIB is intended to be compatible with both the SNMPv1 and SNMPv2. 146 These definitions are based upon the specifications for the HDSL2 and 147 SHDSL Embedded Operations Channel (EOC) as defined in ANSI 148 T1E1.4/2000-006 [18] and ITU G.991.2 (ex G.SHDSL) [19]. 150 The MIB will eventually be located in the MIB tree under MIB 2 151 transmission, as discussed in the MIB-2 Integration (RFC 1213 [20] and 152 RFC 2863 [21]) section of this document. Until approved by the IETF, 153 vendors may also choose to support it under the experimental tree. 155 Expires November 8, 2000 Page [3] 156 NOTE TO RFC EDITOR: please replace the above paragraph with the 157 following paragraph when appropriate: 159 The MIB is located in the MIB tree under MIB-2 transmission, as 160 discussing in the MIB-2 Integration (RFC 1213 [20] and RFC 2863 [21]) 161 section of this document. 163 3.1. Relationship of the HDSL2/SHDSL Line MIB with Standard MIBs 165 This section outlines the relationship of this MIB with other MIBs 166 described in RFCs and in various degrees of "standardization". 167 Specifically, MIB-2 as presented in RFC 1213 [20] and RFC 2863 [21] 168 is discussed. 170 3.1.1 General MIB-2 Integration (RFCs 1213 and 2863) 172 The HDSL2/SHDSL Line MIB specifies the detailed attributes of a data 173 interface. As such, it needs to integrate with RFC 2863 [21]. The 174 IANA has assigned the following ifTypes to HDSL2 and SHDSL: 176 IANAifType ::= TEXTUAL-CONVENTION 177 ... 178 SYNTAX INTEGER { 179 ... 180 hdsl2 (168), -- High Bit-Rate DSL, 2nd generation 181 shdsl (169), -- Multirate HDSL2 182 ... 183 } 185 This MIB will be accessed through the transmission subtree as shown: 187 hdsl2ShdslInterface ::= { transmission xxx } 188 NOTE TO RFC EDITOR: please replace the xxx with an assigned number 190 3.1.2 Usage of ifTable 192 The MIB branch identified by this ifType contains tables appropriate 193 for this interface type. Most such tables extend the ifEntry table, 194 and are indexed by ifIndex. 196 The following attributes are part of the mandatory ifGeneral group in 197 RFC 2863 [21], and are not duplicated in the HDSL2/SHDSL Line MIB. 199 =================================================================== 200 ifIndex Interface index. 202 ifDescr See interfaces MIB [21]. 204 ifType hdsl2(168) or shdsl(169). 206 ifSpeed Set as appropriate. 207 (This is fixed at 1552000 for HDSL2 lines) 209 ifPhysAddress This object should have an octet string 210 with zero length. 212 Expires November 8, 2000 Page [4] 213 ifAdminStatus See interfaces MIB [21]. 215 ifOperStatus See interfaces MIB [21]. 217 ifLastChange See interfaces MIB [21]. 219 ifName See interfaces MIB [21]. 221 ifLinkUpDownTrapEnable Default to enabled(1). 223 ifHighSpeed Set as appropriate. 224 (For HDSL2 lines, this is fixed at 2) 226 ifConnectorPresent Set as appropriate. 227 =================================================================== 228 Figure 1: Use of ifTable Objects 230 4. Conventions used in the MIB 232 4.1. Naming Conventions 234 A. xtuC refers to a central site terminal unit; 235 H2TU-C for HDSL2, or STU-C for SHDSL. 236 B. xtuR refers to a remote site terminal unit; 237 H2TU-R for HDSL2, or STU-R for SHDSL. 238 C. xtu refers to a terminal unit; either an xtuC or xtuR. 239 D. xru refer to a regenerator unit; 240 H2RU for HDSL2, or SRU for SHDSL. 241 E. xU refers to any HDSL2/SHDSL unit; either an xtu or xru. 242 F. CRC is cyclic redundancy check. 243 G. ES means errored second. 244 H. LOS means loss of signal. 245 I. LOSS means loss of signal second. 246 J. LOSW means loss of sync word, distinct from LOS. 247 K. LOSWS means LOSW second. 248 L. SES means severely errored second. 249 M. SNR means signal-to-noise ratio. 250 N. UAS means unavailable second. 252 4.2. Textual Conventions 254 The following textual conventions are defined to reflect the line 255 topology in the MIB (further discussed is the following section) 256 and to define the behaviour of the statistics to be maintained 257 by an agent. 259 o Hdsl2ShdslUnitId : 260 This attribute uniquely identifies each unit in a HDSL2/SHDSL span. 261 It mirrors the EOC addressing mechanism: 263 xtuC(1) - CO terminal unit 264 xtuR(2) - CPE terminal unit 265 xru1(3) .. xru8(10) - regenerators, numbered from 266 central office side 268 Expires November 8, 2000 Page [5] 269 o Hdsl2ShdslUnitSide: 270 This attribute references the two sides of a unit: 272 networkSide(1) - N in figure 2, below 273 customerSide(2) - C in figure 2, below 275 o Hdsl2ShdslWirePair: 276 This attribute references the wire-pairs connecting the units: 278 wirePair1(1) - First pair for HDSL2/SHDSL. 279 wirePair2(2) - Optional second pair for SHDSL only. 281 o Hdsl2ShdslPerfCurrDayCount: 283 This attribute defines the behaviour of the 1-day (24 hour) 284 gauges found in the MIB. 286 o Hdsl2Shdsl1DayIntervalCount: 288 This attribute defines the behaviour of the 1-day (24 hour) 289 interval counters found in the MIB. 291 o Hdsl2ShdslPerfTimeElapsed: 293 This attribute defines the behaviour of the elapsed time counters 294 found in the MIB. 296 o Hdsl2ShdslPerfIntervalThreshold: 298 This attribute defines the behaviour of the alarm thresholds found 299 in the MIB. 301 4.3. Structure 303 The MIB is structured into following MIB groups: 305 o Span Configuration Group: 307 This group supports MIB objects for configuring parameters for 308 the HDSL2/SHDSL span. It contains the following table(s): 310 - hdsl2ShdslSpanConfTable 312 o Unit Inventory Group: 314 This group supports MIB objects for retrieving unit inventory 315 information about units in HDSL2/SHDSL lines via the EOC. It 316 contains the following table(s): 318 - hdsl2ShdslInventoryTable 320 o Segment Endpoint Configuration Group: 322 This group supports MIB objects for configuring parameters for 323 the HDSL2/SHDSL segment endpoints. It contains the following 325 Expires November 8, 2000 Page [6] 326 table(s): 327 - hdsl2ShdslEndpointConfTable 329 o Segment Endpoint Current Status/Performance Group: 331 This group supports MIB objects that provide the current 332 status/performance information relating to segment endpoints. 333 It contains the following table(s): 335 - hdsl2ShdslEndpointCurrTable 337 o Segment Endpoint 15-Minute Interval Status/Performance Group: 339 This group supports MIB objects that provide historic 340 status/performance information relating to segment endpoints 341 in 15-minute intervals. It contains the following table(s): 343 - hdsl2Shdsl15MinIntervalTable 345 o Segment Endpoint 1-Day Interval Status/Performance Group: 347 This group supports MIB objects that provide historic 348 status/performance information relating to segment endpoints 349 in 1-day intervals. It contains the following table(s): 351 - hdsl2Shdsl1DayIntervalTable 353 o Maintenance Group: 355 This group supports MIB objects for performing maintenance 356 operations such as loopbacks for HDSL2/SHDSL lines. It contains 357 the following table(s): 359 - hdsl2ShdslEndpointMaintTable 360 - hdsl2ShdslUnitMaintTable 362 o Span Configuration Profile Group: 364 This group supports MIB objects for defining configuration profiles 365 for HDSL2/SHDSL Spans. It contains the following table(s): 367 - hdsl2ShdslSpanConfProfileTable 369 o Segment Endpoint Alarm Configuration Profile Group: 371 This group supports MIB objects for defining alarm configuration 372 profiles for HDSL2/SHDSL Segment Endpoints. It contains the 373 following table(s): 375 - hdsl2ShdslEndpointAlarmConfProfileTable 377 o Notifications Group: 379 This group defines Notiofication messages supported for HDSL2/ 380 SHDSL lines. It defines the following notifications: 382 Expires November 8, 2000 Page [7] 383 - hdsl2ShdslLoopAttenCrossingTrap 384 - hdsl2ShdslSNRMarginCrossingTrap 385 - hdsl2ShdslPerfESThreshTrap 386 - hdsl2ShdslPerfSESThreshTrap 387 - hdsl2ShdslPerfCRCanomaliesThreshTrap 388 - hdsl2ShdslPerfLOSWSThreshTrap 389 - hdsl2ShdslPerfUASThreshTrap 390 - hdsl2ShdslSpanInvalidNumRepeaters 392 4.3.1 Line Topology 394 An HDSL2/SHDSL Line consists of a minimum of two units - xtuC (the 395 central termination unit) and an xtuR (the remote termination unit). 396 The line may optionally support up to 8 repeater/regenerator units 397 (xru) as shown in the figure below. 399 <-- Network Side Customer Side --> 401 || 403 <~~~> <~~~> HDSL2/SHDSL Segments <~~~> 405 +-------+ +-------+ +-------+ +-------+ +-------+ 406 + C=1=N C=1=N C=..1..=N C=1=N + 407 | xtuC | | xru1 | | xru2 | | xru8 | | xtuR | 408 + C=2=N C=2=N C=..2..=N C=2=N + 409 +-------+ +-------+ +-------+ +-------+ +-------+ 411 Key: HDSL2/SHDSL Span 412 <~~~~> HDSL2/SHDSL Segment 413 1= HDSL2/SHDSL wire-pair-1 414 =2= SHDSL optional wire-pair-2 (Not applicable to HDSL2) 415 C Customer Side Segment Endpoint (modem) 416 N Network Side Segment Endpoint (modem) 418 Figure 2: General topology for an HDSL2/SHDSL Line 420 4.4. Counters, Interval Buckets and Thresholds 422 For SNR Margin, Loop Attenuation, ES, SES, CRC anomalies, LOSWS, and 423 UAS, there are event counters, current 15-minute and one (up to 96) 424 15-minute history bucket(s) of "interval-counters", as well as 425 current and one (up to 30) previous 1-day interval-counter(s). Each 426 current 15-minute event bucket has an associated threshold trap. 428 Unlike RFC 2493 [22] and RFC 2662 [23], there is no representation 429 in the MIB for invalid buckets. In those cases where the data for 430 an interval is suspect or known to be invalid, the agent should 431 not report the interval. 433 There is no requirement for an agent to ensure a fixed relationship 434 between the start of a fifteen minute and any wall clock; however 435 some implementations may align the fifteen minute intervals with 436 quarter hours. Likewise, an implementation may choose to align one 438 Expires November 8, 2000 Page [8] 439 day intervals with the start of a day. 441 Counters are not reset when an xU is reinitialized, only when the 442 agent is reset or reinitialized (or under specific request outside 443 the scope of this MIB). 445 4.5. Profiles 447 As a managed node can handle a large number of xUs, (e.g., hundreds 448 or perhaps thousands of lines), provisioning every parameter on every 449 xU may become burdensome. Moreover, most lines are provisioned 450 identically; with the same set of parameters. To simplify the 451 provisioning process, this MIB makes use of profiles. A profile is a 452 set of parameters that can be shared by multiple lines using the same 453 configuration. 455 The following profiles are used in this MIB: 457 o Span Configuration Profiles - Span configuration profiles contain 458 parameters for configuring HDSL2/SHDSL spans. They are defined in 459 the hdsl2ShdslSpanConfProfileTable. Since span configuration 460 parameters are only applicable for SHDSL, the support for span 461 configuration profiles is optional for HDSL2 interfaces. 463 o Segment Endpoint Alarm Configuration Profiles - These profiles 464 contain parameters for configuring alarm thresholds for HDSL2/ 465 SHDSL segment endpoints. These profiles are defined in the 466 hdsl2ShdslEndpointAlarmConfProfileTable. 468 Implementations will enable the manager to dynamically create and 469 delete profiles as needed. The index of each profile is a locally- 470 unique administratively assigned name for the profile having the 471 textual convention `SnmpAdminString' (RFC 2571 [1]). 473 One or more lines may be configured to share parameters of a single 474 profile (e.g., hdsl2ShdslEndpointAlarmConfProfile = `silver') by 475 setting its hdsl2ShdslEndpointAlarmConfProfile objects to the value of 476 this profile. If a change is made to the profile, all lines that refer 477 to it will be reconfigured to the changed parameters. Before a profile 478 can be deleted or taken out of service it must be first unreferenced 479 from all associated lines. 481 Implementations must provide a default profile whose name is `DEFVAL' 482 for each profile type. The values of the associated parameters will be 483 vendor specific unless otherwise indicated in this document. Before a 484 line's profiles have been set, these profiles will be automatically 485 used by setting hdsl2ShdslEndpointAlarmConfProfile and 486 hdsl2ShdslSpanConfProfile to `DEFVAL' where appropriate. 488 Profiles are created, assigned, and deleted dynamically using the 489 profile name and profile row status in each of the four profile tables. 491 Changes to alarm profiles MUST take effect immediately. Changes to 492 non-alarm profiles MAY be deferred until the next restart (hard reset 493 or soft restart) of the units on the line. Vendors MAY choose to have 495 Expires November 8, 2000 Page [9] 496 the non-alarm profile changes take effect immediately. Alarm profiles 497 are those profile settings found in the 498 hdsl2ShdslEndpointAlarmConfProfileTable. Non-alarm profiles are those 499 profile settings found in the hdsl2ShdslSpanConfTable and 500 hdsl2ShdslSpanConfProfileTable. 502 4.6. Traps 504 The ability to generate the SNMP traps coldStart/WarmStart (per [21]) 505 which are per agent (e.g., per DSLAM in such a device), and linkUp / 506 linkDown (per [21]) -- which are per interface (i.e., HDSL2/SHDSL line) 507 is required. 509 A linkDown trap may be generated whenever any of ES, SES, CRC Anomaly, 510 LOSWS, or UAS event occurs. At this operational point, a manager can 511 use hdsl2ShdslEndpointCurrStatus for additional detailed information. 512 The corresponding linkUp trap MAY be sent when all link failure 513 conditions are cleared. 515 The traps defined in this MIB are for initialization failure and for 516 the threshold crossings associated with the following events: ES, SES, 517 CRC Anomaly, LOSWS, and UAS. Each threshold has its own 518 enable/threshold value. When that value is 0, the trap is disabled. 520 The hdsl2ShdslEndpointCurrStatus is a bitmask representing all 521 outstanding error conditions associated with a particular Segment 522 Endpoint. Note that since status of remote endpoints is obtained via 523 the EOC, this information may be unavailable for units that are 524 unreachable via EOC during a line error condition. Therefore, not all 525 conditions may always be included in its current status. 527 Two alarm conditions, SNR Margin Alarm and Loop Attenuation Alarm, 528 are organized in a manner slightly different from that implied in 529 the EOC specifications. In the MIB, these alarm conditions are 530 tied to the two thresholds hdsl2ShdslEndpointThreshSNRMargin and 531 hdsl2ShdslEndpointThreshLoopAttenuation found in the 532 hdsl2ShdslEndpointAlarmConfProfileTable. In the EOC, the alarm 533 conditions associated with these thresholds are per-unit. In the 534 MIB, these alarm conditions are per-endpoint. For terminal units, 535 this has no impact. For repeaters, this implies an implementation 536 variance where the agent in the terminal unit is responsible for 537 detecting a threshold crossing. As the reporting of a repeater 538 detected alarm condition to the polling terminal unit occurs in 539 the same EOC message as the reporting of the current SNR Margin 540 and Loop Attenuation values, it is anticipated that this will have 541 very little impact on agent implementation. 543 A threshold trap occurs whenever the corresponding current 15-minute 544 interval error counter becomes equal to, or exceeds the threshold 545 value. One trap may be sent per interval per interface. Since the 546 current 15-minute counter are reset to 0 every 15 minutes, if the 547 condition persists, the trap may recur as often as every 15 minutes. 548 For example, to get a trap whenever a "loss of" event occurs (but at 549 most once every 15 minutes), set the corresponding threshold to 1. The 550 agent will generate a trap when the event originally occurs. 552 Expires November 8, 2000 Page [10] 553 Note that the NMS may receive a linkDown trap, as well, if enabled. At 554 the beginning of the next 15 minute interval, the counter is reset. 555 When the first second goes by and the event occurs, the current 556 interval bucket will be 1, which equals the threshold and the trap will 557 be sent again. 559 5. Conformance and Compliance 561 For both HDSL2 and SHDSL lines, the following group(s) are mandatory: 563 hdsl2ShdslSpanConfGroup 564 hdsl2ShdslInventoryGroup 565 hdsl2ShdslEndpointConfGroup 566 hdsl2Shdsl15MinIntervalGroup 567 hdsl2Shdsl1DayIntervalGroup 568 hdsl2ShdslMaintenanceGroup 569 hdsl2ShdslEndpointAlarmConfGroup 570 hdsl2ShdslNotificationGroup 572 For HDSL2 lines, the following group(s) are optional: 574 hdsl2ShdslSpanConfProfileGroup 576 6. Definitions 578 HDSL2-SHDSL-LINE-MIB DEFINITIONS ::= BEGIN 580 IMPORTS 581 MODULE-IDENTITY, 582 OBJECT-TYPE, 583 Counter32, 584 Gauge32, 585 NOTIFICATION-TYPE, 586 Integer32, 587 experimental FROM SNMPv2-SMI 588 DisplayString, 589 RowStatus, 590 TEXTUAL-CONVENTION FROM SNMPv2-TC 591 ifIndex FROM IF-MIB 592 PerfCurrentCount, 593 PerfIntervalCount FROM PerfHist-TC-MIB 594 SnmpAdminString FROM SNMP-FRAMEWORK-MIB 595 MODULE-COMPLIANCE, 596 OBJECT-GROUP, 597 NOTIFICATION-GROUP FROM SNMPv2-CONF; 599 hdsl2ShdslMIB MODULE-IDENTITY 601 LAST-UPDATED "0008210000Z" -- August 21, 2000 603 ORGANIZATION "ADSLMIB Working Group" 605 CONTACT-INFO 606 " 607 Bob Ray 609 Expires November 8, 2000 Page [11] 610 Verilink Corporation 611 127 Jetplex Circle 612 Madison, AL 35758 USA 613 Tel: +1 256-774-2380 614 Fax: +1 256-774-2277 615 E-mail: bray@verilink.com 617 Rajesh Abbi 618 Alcatel USA 619 2912 Wake Forest Road 620 Raleigh, NC 27609-7860 USA 621 Tel: +1 919-950-6194 622 Fax: +1 919-950-6670 623 E-mail: Rajesh.Abbi@usa.alcatel.com 624 " 626 DESCRIPTION 627 "This MIB module defines a collection of objects for 628 managing HDSL2/SHDSL lines. An agent may reside at 629 either end of the line, however the MIB is designed 630 to require no management communication between the 631 modems beyond that inherent in the low-level EOC line 632 protocol as defined in ANSI T1E1.4/2000-006 (for HDSL2 633 lines), or in ITU G.991.2 (for SHDSL lines)." 635 -- NOTE TO RFC EDITOR: Please replace the following with the 636 -- appropriate assigned 'transmission xxx' number 637 ::= { experimental 999999 } 639 hdsl2ShdslLineMib OBJECT IDENTIFIER ::= { hdsl2ShdslMIB 1 } 640 hdsl2ShdslMibObjects OBJECT IDENTIFIER ::= { hdsl2ShdslLineMib 1 } 642 -- Textual Conventions used in this MIB 643 -- 645 Hdsl2ShdslPerfCurrDayCount ::= TEXTUAL-CONVENTION 646 STATUS current 647 DESCRIPTION 648 "A counter associated with interface performance 649 measurements in a current 1-day (24 hour) measurement 650 interval. 652 The value of this counter starts at zero at the 653 beginning of an interval and is increased when 654 associated events occur, until the end of the 655 1-day interval. At that time the value of the 656 counter is stored in the previous 1-day history 657 interval, if available, and the current interval 658 counter is restarted at zero. 660 In the case where the agent has no valid data available 661 for this interval the corresponding object 662 instance is not available and upon a retrieval 663 request a corresponding error message shall be 664 returned to indicate that this instance does 666 Expires November 8, 2000 Page [12] 667 not exist (for example, a noSuchName error for 668 SNMPv1 and a noSuchInstance for SNMPv2 GET 669 operation)." 670 SYNTAX Gauge32 672 Hdsl2Shdsl1DayIntervalCount ::= TEXTUAL-CONVENTION 673 STATUS current 674 DESCRIPTION 675 "A counter associated with interface performance 676 measurements during the most previous 1-day (24 hour) 677 measurement interval. The value of this counter is 678 equal to the value of the current day counter at 679 the end of its most recent interval. 681 In the case where the agent has no valid data available 682 for this interval the corresponding object instance is 683 not available and upon a retrieval request a corresponding 684 error message shall be returned to indicate that this 685 instance does not exist (for example, a noSuchName error 686 for SNMPv1 and a noSuchInstance for SNMPv2 GET operation)." 687 SYNTAX Gauge32 689 Hdsl2ShdslPerfTimeElapsed ::= TEXTUAL-CONVENTION 690 STATUS current 691 DESCRIPTION 692 "The number of seconds that have elapsed since 693 the beginning of the current measurement period. 694 If, for some reason, such as an adjustment in the 695 system's time-of-day clock, the current interval 696 exceeds the maximum value, the agent will return 697 the maximum value." 698 SYNTAX Gauge32 700 Hdsl2ShdslPerfIntervalThreshold ::= TEXTUAL-CONVENTION 701 STATUS current 702 DESCRIPTION 703 "This convention defines a range of values 704 that may be set in a fault threshold alarm 705 control. As the number of seconds in a 706 15-minute interval numbers at most 900, objects 707 of this type may have a range of 0...900, where 708 the value of 0 disables the alarm." 709 SYNTAX INTEGER(0..900) 711 Hdsl2ShdslUnitId ::= TEXTUAL-CONVENTION 712 STATUS current 713 DESCRIPTION 714 "This is the unique identification for all units 715 in an HDSL2/SHDSL Span. It is based on the EOC 716 unit addressing scheme with reference to the xtuC." 717 SYNTAX INTEGER 718 { 719 xtuC(1), 720 xtuR(2), 721 xru1(3), 723 Expires November 8, 2000 Page [13] 724 xru2(4), 725 xru3(5), 726 xru4(6), 727 xru5(7), 728 xru6(8), 729 xru7(9), 730 xru8(10) 731 } 733 Hdsl2ShdslUnitSide ::= TEXTUAL-CONVENTION 734 STATUS current 735 DESCRIPTION 736 "This is the referenced side of an HDSL2/SHDSL 737 unit - Network or Customer side. The side 738 facing the Network is the Network side, while the 739 side facing the Customer is the Customer side." 740 SYNTAX INTEGER 741 { 742 networkSide(1), 743 customerSide(2) 744 } 746 Hdsl2ShdslWirePair ::= TEXTUAL-CONVENTION 747 STATUS current 748 DESCRIPTION 749 "This is the referenced pair of wires in an HDSL2/SHDSL 750 Segment. HDSL2 only supports a single pair (wirePair1), 751 while SHDSL supports an optional second pair (wirePair2)." 752 SYNTAX INTEGER 753 { 754 wirePair1(1), 755 wirePair2(2) 756 } 758 -- Span Configuration Group 759 -- 761 hdsl2ShdslSpanConfTable OBJECT-TYPE 762 SYNTAX SEQUENCE OF Hdsl2ShdslSpanConfEntry 763 MAX-ACCESS not-accessible 764 STATUS current 765 DESCRIPTION 766 "This table supports overall configuration of 767 HDSL2/SHDSL Spans." 768 ::= { hdsl2ShdslMibObjects 1 } 770 hdsl2ShdslSpanConfEntry OBJECT-TYPE 771 SYNTAX Hdsl2ShdslSpanConfEntry 772 MAX-ACCESS not-accessible 773 STATUS current 774 DESCRIPTION 775 "An entry in the hdsl2ShdslSpanConfTable. Each entry 776 represents the complete Span in a single HDSL2/SHDSL 777 line. It is indexed by the ifIndex of the associated 778 HDSL2/SHDSL line." 780 Expires November 8, 2000 Page [14] 781 INDEX { ifIndex } 782 ::= { hdsl2ShdslSpanConfTable 1 } 784 Hdsl2ShdslSpanConfEntry ::= 785 SEQUENCE 786 { 787 hdsl2ShdslConfNumRepeaters INTEGER, 788 hdsl2ShdslSpanConfProfile SnmpAdminString, 789 hdsl2ShdslSpanAlarmConfProfile SnmpAdminString 790 } 792 hdsl2ShdslConfNumRepeaters OBJECT-TYPE 793 SYNTAX INTEGER(0..8) 794 MAX-ACCESS read-write 795 STATUS current 797 DESCRIPTION 798 "This object provisions the number of repeaters/regenerators 799 in this HDSL2/SHDSL Span." 800 ::= { hdsl2ShdslSpanConfEntry 1 } 802 hdsl2ShdslSpanConfProfile OBJECT-TYPE 803 SYNTAX SnmpAdminString 804 MAX-ACCESS read-write 805 STATUS current 806 DESCRIPTION 807 "This object is a pointer to a span configuration profile in 808 the hdsl2ShdslSpanConfProfileTable, which applies to this span. 809 The value of this object is the index of the referenced profile 810 in the hdsl2ShdslSpanConfProfileTable. Note that span 811 configuration profiles are only applicable to SHDSL lines. 812 HDSL2 lines will not support this object. By default, this 813 object will have the value 'DEFVAL' (the index of the default 814 profile)." 815 ::= { hdsl2ShdslSpanConfEntry 2 } 817 hdsl2ShdslSpanAlarmConfProfile OBJECT-TYPE 818 SYNTAX SnmpAdminString 819 MAX-ACCESS read-write 820 STATUS current 821 DESCRIPTION 822 "This object is a pointer to an Alarm configuration profile in 823 the hdsl2ShdslEndpointAlarmConfProfileTable. The value of this 824 object is the index of the referenced profile in the 825 hdsl2ShdslEndpointAlarmConfProfileTable. The alarm threshold 826 configuration in the referenced profile will be used by default 827 for all segment endpoints in this span. Individual endpoints 828 may override this profile by explicitly specifying some other 829 profile in the hdsl2ShdslEndpointConfTable. By default, this 830 object will have the value 'DEFVAL' (the index of the default 831 profile)." 832 ::= { hdsl2ShdslSpanConfEntry 3 } 834 -- Unit Inventory Group 835 -- 837 Expires November 8, 2000 Page [15] 838 hdsl2ShdslInventoryTable OBJECT-TYPE 839 SYNTAX SEQUENCE OF Hdsl2ShdslInventoryEntry 840 MAX-ACCESS not-accessible 841 STATUS current 842 DESCRIPTION 843 "This table supports retrieval of unit inventory information 844 available via the EOC from units in a HDSL2/SHDSL line." 845 ::= { hdsl2ShdslMibObjects 2 } 847 hdsl2ShdslInventoryEntry OBJECT-TYPE 848 SYNTAX Hdsl2ShdslInventoryEntry 849 MAX-ACCESS not-accessible 850 STATUS current 851 DESCRIPTION 852 "An entry in the hdsl2ShdslInventoryTable. Each entry 853 represents inventory information for a single unit in a 854 HDSL2/SHDSL line. It is indexed by the ifIndex of the 855 HDSL2/SHDSL line and the Hdsl2ShdslUnitId of the 856 associated unit." 857 INDEX { ifIndex, hdsl2ShdslInvIndex } 858 ::= { hdsl2ShdslInventoryTable 1 } 860 Hdsl2ShdslInventoryEntry ::= 861 SEQUENCE 862 { 863 hdsl2ShdslInvIndex Hdsl2ShdslUnitId, 864 hdsl2ShdslInvVendorID Integer32, 865 hdsl2ShdslInvVendorModelNumber DisplayString, 866 hdsl2ShdslInvVendorSerialNumber DisplayString, 867 hdsl2ShdslInvVendorEOCSoftwareVersion Integer32, 868 hdsl2ShdslInvStandardVersion Integer32, 869 hdsl2ShdslInvVendorListNumber DisplayString, 870 hdsl2ShdslInvVendorIssueNumber DisplayString, 871 hdsl2ShdslInvVendorSoftwareVersion DisplayString, 872 hdsl2ShdslInvEquipmentCode DisplayString, 873 hdsl2ShdslInvVendorOther DisplayString 874 } 876 hdsl2ShdslInvIndex OBJECT-TYPE 877 SYNTAX Hdsl2ShdslUnitId 878 MAX-ACCESS read-only 879 STATUS current 880 DESCRIPTION 881 "The index into the hdsl2ShdslInventoryTable." 882 ::= { hdsl2ShdslInventoryEntry 1 } 884 hdsl2ShdslInvVendorID OBJECT-TYPE 885 SYNTAX Integer32 886 MAX-ACCESS read-only 887 STATUS current 888 DESCRIPTION 889 "Vendor ID as reported in an Inventory Response message." 890 ::= { hdsl2ShdslInventoryEntry 2 } 892 Expires November 8, 2000 Page [16] 893 hdsl2ShdslInvVendorModelNumber OBJECT-TYPE 894 SYNTAX DisplayString 895 MAX-ACCESS read-only 896 STATUS current 897 DESCRIPTION 898 "Vendor model number as reported in an Inventory Response 899 message." 900 ::= { hdsl2ShdslInventoryEntry 3 } 902 hdsl2ShdslInvVendorSerialNumber OBJECT-TYPE 903 SYNTAX DisplayString 904 MAX-ACCESS read-only 905 STATUS current 906 DESCRIPTION 907 "Vendor serial number as reported in an Inventory Response 908 message." 909 ::= { hdsl2ShdslInventoryEntry 4 } 911 hdsl2ShdslInvVendorEOCSoftwareVersion OBJECT-TYPE 912 SYNTAX Integer32 913 MAX-ACCESS read-only 914 STATUS current 915 DESCRIPTION 916 "Vendor EOC version as reported in an Inventory Response 917 message." 918 ::= { hdsl2ShdslInventoryEntry 5 } 920 hdsl2ShdslInvStandardVersion OBJECT-TYPE 921 SYNTAX Integer32 922 MAX-ACCESS read-only 923 STATUS current 924 DESCRIPTION 925 "Version of the HDSL2/SHDSL standard implemented, as reported 926 in an Inventory Response message." 927 ::= { hdsl2ShdslInventoryEntry 6 } 929 hdsl2ShdslInvVendorListNumber OBJECT-TYPE 930 SYNTAX DisplayString 931 MAX-ACCESS read-only 932 STATUS current 933 DESCRIPTION 934 "Vendor list number as reported in an Inventory Response 935 message." 936 ::= { hdsl2ShdslInventoryEntry 7 } 938 hdsl2ShdslInvVendorIssueNumber OBJECT-TYPE 939 SYNTAX DisplayString 940 MAX-ACCESS read-only 941 STATUS current 942 DESCRIPTION 943 "Vendor issue number as reported in an Inventory Response 944 message." 945 ::= { hdsl2ShdslInventoryEntry 8 } 947 Expires November 8, 2000 Page [17] 948 hdsl2ShdslInvVendorSoftwareVersion OBJECT-TYPE 949 SYNTAX DisplayString 950 MAX-ACCESS read-only 951 STATUS current 952 DESCRIPTION 953 "Vendor software version as reported in an Inventory 954 Response message." 955 ::= { hdsl2ShdslInventoryEntry 9 } 957 hdsl2ShdslInvEquipmentCode OBJECT-TYPE 958 SYNTAX DisplayString 959 MAX-ACCESS read-only 960 STATUS current 961 DESCRIPTION 962 "Equipment code conforming to ANSI T1.213, Coded Identification 963 of Equipment Entities." 964 ::= { hdsl2ShdslInventoryEntry 10 } 966 hdsl2ShdslInvVendorOther OBJECT-TYPE 967 SYNTAX DisplayString 968 MAX-ACCESS read-only 969 STATUS current 970 DESCRIPTION 971 "Other vendor information as reported in an Inventory 972 Response message." 973 ::= { hdsl2ShdslInventoryEntry 11 } 975 -- Segment Endpoint Configuration Group 976 -- 978 hdsl2ShdslEndpointConfTable OBJECT-TYPE 979 SYNTAX SEQUENCE OF Hdsl2ShdslEndpointConfEntry 980 MAX-ACCESS not-accessible 981 STATUS current 982 DESCRIPTION 983 "This table supports configuration parameters for segment 984 endpoints in a HDSL2/SHDSL line." 985 ::= { hdsl2ShdslMibObjects 4 } 987 hdsl2ShdslEndpointConfEntry OBJECT-TYPE 988 SYNTAX Hdsl2ShdslEndpointConfEntry 989 MAX-ACCESS not-accessible 990 STATUS current 991 DESCRIPTION 992 "An entry in the hdsl2ShdslEndpointConfTable. Each entry 993 represents a single segment endpoint in a HDSL2/SHDSL line. 994 It is indexed by the ifIndex of the HDSL2/SHDSL line, the 995 UnitId of the associated unit, the side of the unit, and the 996 wire-pair of the associated modem." 997 INDEX { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide, 998 hdsl2ShdslEndpointWirePair} 999 ::= { hdsl2ShdslEndpointConfTable 1 } 1001 Expires November 8, 2000 Page [18] 1002 Hdsl2ShdslEndpointConfEntry ::= 1003 SEQUENCE 1004 { 1005 hdsl2ShdslEndpointSide Hdsl2ShdslUnitSide, 1006 hdsl2ShdslEndpointWirePair Hdsl2ShdslWirePair, 1007 hdsl2ShdslEndpointAlarmConfProfile SnmpAdminString 1008 } 1010 hdsl2ShdslEndpointSide OBJECT-TYPE 1011 SYNTAX Hdsl2ShdslUnitSide 1012 MAX-ACCESS read-only 1013 STATUS current 1014 DESCRIPTION 1015 "The side of the unit associated with this segment endpoint - 1016 Network/Customer side - as per the Hdsl2ShdslUnitSide 1017 textual convention." 1018 ::= { hdsl2ShdslEndpointConfEntry 1 } 1020 hdsl2ShdslEndpointWirePair OBJECT-TYPE 1021 SYNTAX Hdsl2ShdslWirePair 1022 MAX-ACCESS read-only 1023 STATUS current 1024 DESCRIPTION 1025 "The wire-pair of the modem associated with this segment 1026 endpoint as per the Hdsl2ShdslWirePair textual convention." 1027 ::= { hdsl2ShdslEndpointConfEntry 2 } 1029 hdsl2ShdslEndpointAlarmConfProfile OBJECT-TYPE 1030 SYNTAX SnmpAdminString 1031 MAX-ACCESS read-write 1032 STATUS current 1033 DESCRIPTION 1034 "This object configures the alarm threshold values to be 1035 used for this segment endpoint. The values are obtained 1036 from the alarm configuration profile referenced by this 1037 object. The value of this object is the index of the 1038 referenced profile in the hdsl2ShdslLineAlarmConfProfileTable, 1039 or NULL. If the value is NULL, the endpoint uses the 1040 default Alarm Configuration Profile for the associated 1041 span as per the hdsl2ShdslSpanAlarmConfProfile object in 1042 the hdsl2ShdslSpanConfTable. The default value of this 1043 object is NULL." 1044 ::= { hdsl2ShdslEndpointConfEntry 3 } 1046 -- Segment Endpoint Current Status/Performance Group 1047 -- 1049 hdsl2ShdslEndpointCurrTable OBJECT-TYPE 1050 SYNTAX SEQUENCE OF Hdsl2ShdslEndpointCurrEntry 1051 MAX-ACCESS not-accessible 1052 STATUS current 1053 DESCRIPTION 1054 "This table contains current status and performance information 1055 for segment endpoints in HDSL2/SHDSL Lines." 1056 ::= { hdsl2ShdslMibObjects 5 } 1058 Expires November 8, 2000 Page [19] 1059 hdsl2ShdslEndpointCurrEntry OBJECT-TYPE 1060 SYNTAX Hdsl2ShdslEndpointCurrEntry 1061 MAX-ACCESS not-accessible 1062 STATUS current 1063 DESCRIPTION 1064 "An entry in the hdsl2ShdslEndpointCurrTable. Each entry 1065 contains status and performance information relating to a 1066 single segment endpoint. It is indexed by the ifIndex of 1067 the HDSL2/SHDSL line, the UnitId of the associated unit, 1068 the side of the unit, and the wire-pair of the associated 1069 modem." 1070 INDEX { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide, 1071 hdsl2ShdslEndpointWirePair} 1072 ::= { hdsl2ShdslEndpointCurrTable 1 } 1074 Hdsl2ShdslEndpointCurrEntry ::= 1075 SEQUENCE 1076 { 1077 hdsl2ShdslEndpointCurrAtn Integer32, 1078 hdsl2ShdslEndpointCurrSnrMgn Integer32, 1079 hdsl2ShdslEndpointCurrStatus Integer32, 1080 hdsl2ShdslEndpointES Counter32, 1081 hdsl2ShdslEndpointSES Counter32, 1082 hdsl2ShdslEndpointCRCanomalies Counter32, 1083 hdsl2ShdslEndpointLOSWS Counter32, 1084 hdsl2ShdslEndpointUAS Counter32, 1085 hdsl2ShdslEndpointCurr15MinTimeElapsed Hdsl2ShdslPerfTimeElapsed, 1086 hdsl2ShdslEndpointCurr15MinES PerfCurrentCount, 1087 hdsl2ShdslEndpointCurr15MinSES PerfCurrentCount, 1088 hdsl2ShdslEndpointCurr15MinCRCanomalies PerfCurrentCount, 1089 hdsl2ShdslEndpointCurr15MinLOSWS PerfCurrentCount, 1090 hdsl2ShdslEndpointCurr15MinUAS PerfCurrentCount, 1091 hdsl2ShdslEndpointCurr1DayTimeElapsed Hdsl2ShdslPerfTimeElapsed, 1092 hdsl2ShdslEndpointCurr1DayES Hdsl2ShdslPerfCurrDayCount, 1093 hdsl2ShdslEndpointCurr1DaySES Hdsl2ShdslPerfCurrDayCount, 1094 hdsl2ShdslEndpointCurr1DayCRCanomalies Hdsl2ShdslPerfCurrDayCount, 1095 hdsl2ShdslEndpointCurr1DayLOSWS Hdsl2ShdslPerfCurrDayCount, 1096 hdsl2ShdslEndpointCurr1DayUAS Hdsl2ShdslPerfCurrDayCount 1097 } 1099 hdsl2ShdslEndpointCurrAtn OBJECT-TYPE 1100 SYNTAX Integer32 1101 UNITS "dB" 1102 MAX-ACCESS read-only 1103 STATUS current 1104 DESCRIPTION 1105 "The current loop attenuation for this endpoint as 1106 reported in a Network or Customer Side Performance 1107 Status message." 1108 ::= { hdsl2ShdslEndpointCurrEntry 1 } 1110 hdsl2ShdslEndpointCurrSnrMgn OBJECT-TYPE 1111 SYNTAX Integer32 1112 UNITS "dB" 1113 MAX-ACCESS read-only 1115 Expires November 8, 2000 Page [20] 1116 STATUS current 1117 DESCRIPTION 1118 "The current SNR margin for this endpoint as reported 1119 in a Status Response/SNR message." 1120 ::= { hdsl2ShdslEndpointCurrEntry 2 } 1122 hdsl2ShdslEndpointCurrStatus OBJECT-TYPE 1123 SYNTAX Integer32 1124 MAX-ACCESS read-only 1125 STATUS current 1126 DESCRIPTION 1127 "Contains the current state of the endpoint. This is a 1128 bit-map of possible conditions. The various bit positions 1129 are: 1131 1 noDefect There no defects on the line 1133 2 powerBackoff Indicates enhanced Power Backoff 1135 4 deviceFault Indicates a vendor-dependent 1136 detection of diagnostics or 1137 self-test results 1139 8 dcContinuityFault Indicates vendor-dependent 1140 conditions that interfere with 1141 span powering such as short and 1142 open circuits 1144 16 snrMarginAlarm Indicates that the SNR margin 1145 has exceeded the alarm threshold 1147 32 loopAttenuationAlarm Indicates that the loop attentuation 1148 has exceeded the alarm threshold 1150 64 loswFailureAlarm Indicates a forward LOSW alarm 1152 128 configInitFailure Endpoint failure during initialization 1153 due to paired endpoint not able to 1154 support requested configuration 1156 256 protocolInitFailure Endpoint failure during initialization 1157 due to incompatible protocol used by 1158 the paired endpoint. 1160 512 noNeighborPresent Endpoint failure during initialization 1161 due to no activation sequence detected 1162 from paired endpoint. 1164 1024 loopbackActive A loopback is currently active at this 1165 Segment Endpoint. 1167 This is intended to supplement ifOperStatus." 1168 ::= { hdsl2ShdslEndpointCurrEntry 3 } 1170 Expires November 8, 2000 Page [21] 1171 hdsl2ShdslEndpointES OBJECT-TYPE 1172 SYNTAX Counter32 1173 UNITS "seconds" 1174 MAX-ACCESS read-only 1175 STATUS current 1176 DESCRIPTION 1177 "Count of Errored Seconds (ES) on this endpoint since the xU 1178 was last restarted." 1179 ::= { hdsl2ShdslEndpointCurrEntry 4 } 1181 hdsl2ShdslEndpointSES OBJECT-TYPE 1182 SYNTAX Counter32 1183 UNITS "seconds" 1184 MAX-ACCESS read-only 1185 STATUS current 1186 DESCRIPTION 1187 "Count of Severely Errored Seconds (SES) on this endpoint 1188 since the xU was last restarted." 1189 ::= { hdsl2ShdslEndpointCurrEntry 5 } 1191 hdsl2ShdslEndpointCRCanomalies OBJECT-TYPE 1192 SYNTAX Counter32 1193 MAX-ACCESS read-only 1194 STATUS current 1195 DESCRIPTION 1196 "Count of CRC anomalies on this endpoint since the xU was 1197 last restarted." 1198 ::= { hdsl2ShdslEndpointCurrEntry 6 } 1200 hdsl2ShdslEndpointLOSWS OBJECT-TYPE 1201 SYNTAX Counter32 1202 UNITS "seconds" 1203 MAX-ACCESS read-only 1204 STATUS current 1205 DESCRIPTION 1206 "Count of Loss of Sync Word (LOSW) Seconds on this endpoint 1207 since the xU was last restarted." 1208 ::= { hdsl2ShdslEndpointCurrEntry 7 } 1210 hdsl2ShdslEndpointUAS OBJECT-TYPE 1211 SYNTAX Counter32 1212 UNITS "seconds" 1213 MAX-ACCESS read-only 1214 STATUS current 1215 DESCRIPTION 1216 "Count of Unavailable Seconds (UAS) on this endpoint since 1217 the xU was last restarted." 1218 ::= { hdsl2ShdslEndpointCurrEntry 8 } 1220 hdsl2ShdslEndpointCurr15MinTimeElapsed OBJECT-TYPE 1221 SYNTAX Hdsl2ShdslPerfTimeElapsed 1222 UNITS "seconds" 1223 MAX-ACCESS read-only 1224 STATUS current 1225 DESCRIPTION 1227 Expires November 8, 2000 Page [22] 1228 "Total elapsed seconds in the current 15-minute interval." 1229 ::= { hdsl2ShdslEndpointCurrEntry 9 } 1231 hdsl2ShdslEndpointCurr15MinES OBJECT-TYPE 1232 SYNTAX PerfCurrentCount 1233 UNITS "seconds" 1234 MAX-ACCESS read-only 1235 STATUS current 1236 DESCRIPTION 1237 "Count of Errored Seconds (ES) in the current 15-minute 1238 interval." 1239 ::= { hdsl2ShdslEndpointCurrEntry 10 } 1241 hdsl2ShdslEndpointCurr15MinSES OBJECT-TYPE 1242 SYNTAX PerfCurrentCount 1243 UNITS "seconds" 1244 MAX-ACCESS read-only 1245 STATUS current 1246 DESCRIPTION 1247 "Count of Severely Errored Seconds (SES) in the current 1248 15-minute interval." 1249 ::= { hdsl2ShdslEndpointCurrEntry 11 } 1251 hdsl2ShdslEndpointCurr15MinCRCanomalies OBJECT-TYPE 1252 SYNTAX PerfCurrentCount 1253 MAX-ACCESS read-only 1254 STATUS current 1255 DESCRIPTION 1256 "Count of CRC anomalies in the current 15-minute interval." 1257 ::= { hdsl2ShdslEndpointCurrEntry 12 } 1259 hdsl2ShdslEndpointCurr15MinLOSWS OBJECT-TYPE 1260 SYNTAX PerfCurrentCount 1261 UNITS "seconds" 1262 MAX-ACCESS read-only 1263 STATUS current 1264 DESCRIPTION 1265 "Count of Loss of Sync Word (LOSW) Seconds in the current 1266 15-minute interval." 1267 ::= { hdsl2ShdslEndpointCurrEntry 13 } 1269 hdsl2ShdslEndpointCurr15MinUAS OBJECT-TYPE 1270 SYNTAX PerfCurrentCount 1271 UNITS "seconds" 1272 MAX-ACCESS read-only 1273 STATUS current 1274 DESCRIPTION 1275 "Count of Unavailable Seconds (UAS) in the current 15-minute 1276 interval." 1277 ::= { hdsl2ShdslEndpointCurrEntry 14 } 1279 hdsl2ShdslEndpointCurr1DayTimeElapsed OBJECT-TYPE 1280 SYNTAX Hdsl2ShdslPerfTimeElapsed 1281 UNITS "seconds" 1282 MAX-ACCESS read-only 1284 Expires November 8, 2000 Page [23] 1285 STATUS current 1286 DESCRIPTION 1287 "Number of seconds that have elapsed since the beginning of 1288 the current 1-day interval." 1289 ::= { hdsl2ShdslEndpointCurrEntry 15 } 1291 hdsl2ShdslEndpointCurr1DayES OBJECT-TYPE 1292 SYNTAX Hdsl2ShdslPerfCurrDayCount 1293 UNITS "seconds" 1294 MAX-ACCESS read-only 1295 STATUS current 1296 DESCRIPTION 1297 "Count of Errored Seconds (ES) during the current day as 1298 measured by hdslPerfCurr1DayTimeElapsed." 1299 ::= { hdsl2ShdslEndpointCurrEntry 16 } 1301 hdsl2ShdslEndpointCurr1DaySES OBJECT-TYPE 1302 SYNTAX Hdsl2ShdslPerfCurrDayCount 1303 UNITS "seconds" 1304 MAX-ACCESS read-only 1305 STATUS current 1306 DESCRIPTION 1307 "Count of Severely Errored Seconds (SES) during the current 1308 day as measured by hdslPerfCurr1DayTimeElapsed." 1309 ::= { hdsl2ShdslEndpointCurrEntry 17 } 1311 hdsl2ShdslEndpointCurr1DayCRCanomalies OBJECT-TYPE 1312 SYNTAX Hdsl2ShdslPerfCurrDayCount 1313 MAX-ACCESS read-only 1314 STATUS current 1315 DESCRIPTION 1316 "Count of CRC anomalies during the current day as measured 1317 by hdslPerfCurr1DayTimeElapsed." 1318 ::= { hdsl2ShdslEndpointCurrEntry 18 } 1320 hdsl2ShdslEndpointCurr1DayLOSWS OBJECT-TYPE 1321 SYNTAX Hdsl2ShdslPerfCurrDayCount 1322 UNITS "seconds" 1323 MAX-ACCESS read-only 1324 STATUS current 1325 DESCRIPTION 1326 "Count of Loss of Sync Word Seconds (LOSWS) during the 1327 current day as measured by hdslPerfCurr1DayTimeElapsed." 1328 ::= { hdsl2ShdslEndpointCurrEntry 19 } 1330 hdsl2ShdslEndpointCurr1DayUAS OBJECT-TYPE 1331 SYNTAX Hdsl2ShdslPerfCurrDayCount 1332 UNITS "seconds" 1333 MAX-ACCESS read-only 1334 STATUS current 1335 DESCRIPTION 1336 "Count of Unavailable Seconds (UAS) during the current 1337 day as measured by hdslPerfCurr1DayTimeElapsed." 1338 ::= { hdsl2ShdslEndpointCurrEntry 20 } 1340 Expires November 8, 2000 Page [24] 1341 -- Segment Endpoint 15-Minute Interval Status/Performance Group 1342 -- 1344 hdsl2Shdsl15MinIntervalTable OBJECT-TYPE 1345 SYNTAX SEQUENCE OF Hdsl2Shdsl15MinIntervalEntry 1346 MAX-ACCESS not-accessible 1347 STATUS current 1348 DESCRIPTION 1349 "This table provides one row for each HDSL2/SHDSL endpoint 1350 performance data collection interval." 1351 ::= { hdsl2ShdslMibObjects 6 } 1353 hdsl2Shdsl15MinIntervalEntry OBJECT-TYPE 1354 SYNTAX Hdsl2Shdsl15MinIntervalEntry 1355 MAX-ACCESS not-accessible 1356 STATUS current 1357 DESCRIPTION 1358 "An entry in the hdsl2Shdsl15MinIntervalTable." 1359 INDEX { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide, 1360 hdsl2ShdslEndpointWirePair, hdsl2Shdsl15MinIntervalNumber} 1361 ::= { hdsl2Shdsl15MinIntervalTable 1 } 1363 Hdsl2Shdsl15MinIntervalEntry ::= 1364 SEQUENCE 1365 { 1366 hdsl2Shdsl15MinIntervalNumber INTEGER, 1367 hdsl2Shdsl15MinIntervalES PerfIntervalCount, 1368 hdsl2Shdsl15MinIntervalSES PerfIntervalCount, 1369 hdsl2Shdsl15MinIntervalCRCanomalies PerfIntervalCount, 1370 hdsl2Shdsl15MinIntervalLOSWS PerfIntervalCount, 1371 hdsl2Shdsl15MinIntervalUAS PerfIntervalCount 1372 } 1374 hdsl2Shdsl15MinIntervalNumber OBJECT-TYPE 1375 SYNTAX INTEGER(1..96) 1376 MAX-ACCESS not-accessible 1377 STATUS current 1378 DESCRIPTION 1379 "Performance Data Interval number. 1 is the the most recent 1380 previous interval; interval 96 is 24 hours ago. Intervals 1381 2..96 are optional." 1382 ::= { hdsl2Shdsl15MinIntervalEntry 1 } 1384 hdsl2Shdsl15MinIntervalES OBJECT-TYPE 1385 SYNTAX PerfIntervalCount 1386 UNITS "seconds" 1387 MAX-ACCESS read-only 1388 STATUS current 1389 DESCRIPTION 1390 "Count of Errored Seconds (ES) during the interval." 1391 ::= { hdsl2Shdsl15MinIntervalEntry 2 } 1393 hdsl2Shdsl15MinIntervalSES OBJECT-TYPE 1394 SYNTAX PerfIntervalCount 1395 UNITS "seconds" 1397 Expires November 8, 2000 Page [25] 1398 MAX-ACCESS read-only 1399 STATUS current 1400 DESCRIPTION 1401 "Count of Severely Errored Seconds (SES) during the 1402 interval." 1403 ::= { hdsl2Shdsl15MinIntervalEntry 3 } 1405 hdsl2Shdsl15MinIntervalCRCanomalies OBJECT-TYPE 1406 SYNTAX PerfIntervalCount 1407 MAX-ACCESS read-only 1408 STATUS current 1409 DESCRIPTION 1410 "Count of CRC anomalies during the interval." 1411 ::= { hdsl2Shdsl15MinIntervalEntry 4 } 1413 hdsl2Shdsl15MinIntervalLOSWS OBJECT-TYPE 1414 SYNTAX PerfIntervalCount 1415 UNITS "seconds" 1416 MAX-ACCESS read-only 1417 STATUS current 1418 DESCRIPTION 1419 "Count of Loss of Sync Word (LOSW) Seconds during the interval." 1420 ::= { hdsl2Shdsl15MinIntervalEntry 5 } 1422 hdsl2Shdsl15MinIntervalUAS OBJECT-TYPE 1423 SYNTAX PerfIntervalCount 1424 UNITS "seconds" 1425 MAX-ACCESS read-only 1426 STATUS current 1427 DESCRIPTION 1428 "Count of Unavailable Seconds (UAS) during the interval." 1429 ::= { hdsl2Shdsl15MinIntervalEntry 6 } 1431 -- Segment Endpoint 1-Day Interval Status/Performance Group 1432 -- 1434 hdsl2Shdsl1DayIntervalTable OBJECT-TYPE 1435 SYNTAX SEQUENCE OF Hdsl2Shdsl1DayIntervalEntry 1436 MAX-ACCESS not-accessible 1437 STATUS current 1438 DESCRIPTION 1439 "This table provides one row for each HDSL2/SHDSL endpoint 1440 performance data collection interval." 1441 ::= { hdsl2ShdslMibObjects 7 } 1443 hdsl2Shdsl1DayIntervalEntry OBJECT-TYPE 1444 SYNTAX Hdsl2Shdsl1DayIntervalEntry 1445 MAX-ACCESS not-accessible 1446 STATUS current 1447 DESCRIPTION 1448 "An entry in the hdsl2Shdsl1DayIntervalTable." 1449 INDEX { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide, 1450 hdsl2ShdslEndpointWirePair, hdsl2Shdsl1DayIntervalInterval } 1451 ::= { hdsl2Shdsl1DayIntervalTable 1 } 1453 Expires November 8, 2000 Page [26] 1454 Hdsl2Shdsl1DayIntervalEntry ::= 1455 SEQUENCE 1456 { 1457 hdsl2Shdsl1DayIntervalInterval INTEGER, 1458 hdsl2Shdsl1DayIntervalMoniSecs Hdsl2ShdslPerfTimeElapsed, 1459 hdsl2Shdsl1DayIntervalES Hdsl2Shdsl1DayIntervalCount, 1460 hdsl2Shdsl1DayIntervalSES Hdsl2Shdsl1DayIntervalCount, 1461 hdsl2Shdsl1DayIntervalCRCanomalies Hdsl2Shdsl1DayIntervalCount, 1462 hdsl2Shdsl1DayIntervalLOSWS Hdsl2Shdsl1DayIntervalCount, 1463 hdsl2Shdsl1DayIntervalUAS Hdsl2Shdsl1DayIntervalCount 1464 } 1466 hdsl2Shdsl1DayIntervalInterval OBJECT-TYPE 1467 SYNTAX INTEGER(1..30) 1468 MAX-ACCESS not-accessible 1469 STATUS current 1470 DESCRIPTION 1471 "History Data Interval number. Interval 1 is the the most 1472 recent previous day; interval 30 is 30 days ago. Intervals 1473 2..30 are optional." 1474 ::= { hdsl2Shdsl1DayIntervalEntry 1 } 1476 hdsl2Shdsl1DayIntervalMoniSecs OBJECT-TYPE 1477 SYNTAX Hdsl2ShdslPerfTimeElapsed 1478 MAX-ACCESS read-only 1479 STATUS current 1480 DESCRIPTION 1481 "The amount of time in the 1-day interval over which the 1482 performance monitoring information is actually counted. 1483 This value will be the same as the interval duration except 1484 in a situation where performance monitoring data could not 1485 be collected for any reason." 1486 ::= { hdsl2Shdsl1DayIntervalEntry 2 } 1488 hdsl2Shdsl1DayIntervalES OBJECT-TYPE 1489 SYNTAX Hdsl2Shdsl1DayIntervalCount 1490 UNITS "seconds" 1491 MAX-ACCESS read-only 1492 STATUS current 1493 DESCRIPTION 1494 "Count of Errored Seconds (ES) during the 1-day interval as 1495 measured by hdsl2Shdsl1DayIntervalMoniSecs." 1496 ::= { hdsl2Shdsl1DayIntervalEntry 3 } 1498 hdsl2Shdsl1DayIntervalSES OBJECT-TYPE 1499 SYNTAX Hdsl2Shdsl1DayIntervalCount 1500 UNITS "seconds" 1501 MAX-ACCESS read-only 1502 STATUS current 1503 DESCRIPTION 1504 "Count of Severely Errored Seconds (SES) during the 1-day 1505 interval as measured by hdsl2Shdsl1DayIntervalMoniSecs." 1506 ::= { hdsl2Shdsl1DayIntervalEntry 4 } 1508 Expires November 8, 2000 Page [27] 1509 hdsl2Shdsl1DayIntervalCRCanomalies OBJECT-TYPE 1510 SYNTAX Hdsl2Shdsl1DayIntervalCount 1511 MAX-ACCESS read-only 1512 STATUS current 1513 DESCRIPTION 1514 "Count of CRC anomalies during the 1-day interval as 1515 measured by hdsl2Shdsl1DayIntervalMoniSecs." 1516 ::= { hdsl2Shdsl1DayIntervalEntry 5 } 1518 hdsl2Shdsl1DayIntervalLOSWS OBJECT-TYPE 1519 SYNTAX Hdsl2Shdsl1DayIntervalCount 1520 UNITS "seconds" 1521 MAX-ACCESS read-only 1522 STATUS current 1523 DESCRIPTION 1524 "Count of Loss of Sync Word (LOSW) Seconds during the 1-day 1525 interval as measured by hdsl2Shdsl1DayIntervalMoniSecs." 1526 ::= { hdsl2Shdsl1DayIntervalEntry 6 } 1528 hdsl2Shdsl1DayIntervalUAS OBJECT-TYPE 1529 SYNTAX Hdsl2Shdsl1DayIntervalCount 1530 MAX-ACCESS read-only 1531 STATUS current 1532 DESCRIPTION 1533 "Count of Unavailable Seconds (UAS) during the 1-day interval 1534 as measured by hdsl2Shdsl1DayIntervalMoniSecs." 1535 ::= { hdsl2Shdsl1DayIntervalEntry 7 } 1537 -- Maintenance Group 1538 -- 1540 hdsl2ShdslEndpointMaintTable OBJECT-TYPE 1541 SYNTAX SEQUENCE OF Hdsl2ShdslEndpointMaintEntry 1542 MAX-ACCESS not-accessible 1543 STATUS current 1544 DESCRIPTION 1545 "This table supports maintenance operations (eg. loopbacks) 1546 to be performed on HDSL2/SHDSL segment endpoints." 1547 ::= { hdsl2ShdslMibObjects 8 } 1549 hdsl2ShdslEndpointMaintEntry OBJECT-TYPE 1550 SYNTAX Hdsl2ShdslEndpointMaintEntry 1551 MAX-ACCESS not-accessible 1552 STATUS current 1553 DESCRIPTION 1554 "An entry in the hdsl2ShdslEndpointMaintTable. Each entry 1555 corresponds to a single segment endpoint, and is indexed by the 1556 ifIndex of the HDSL2/SHDSL line, the UnitId of the associated 1557 unit and the side of the unit." 1558 INDEX { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide } 1559 ::= { hdsl2ShdslEndpointMaintTable 1 } 1561 Hdsl2ShdslEndpointMaintEntry ::= 1562 SEQUENCE 1563 { 1565 Expires November 8, 2000 Page [28] 1566 hdsl2ShdslMaintLoopbackConfig INTEGER, 1567 hdsl2ShdslMaintTipRingReversal INTEGER, 1568 hdsl2ShdslMaintPowerBackOff INTEGER, 1569 hdsl2ShdslMaintSoftRestart INTEGER 1570 } 1572 hdsl2ShdslMaintLoopbackConfig OBJECT-TYPE 1573 SYNTAX INTEGER 1574 { 1575 noLoopback(1), 1576 normalLoopback(2), 1577 specialLoopback(3) 1578 } 1579 MAX-ACCESS read-write 1580 STATUS current 1581 DESCRIPTION 1582 "This object controls configuration of loopbacks for the 1583 associated segment endpoint. The status of the loopback 1584 is obtained via the hdsl2ShdslEndpointCurrStatus object." 1585 ::= { hdsl2ShdslEndpointMaintEntry 1 } 1587 hdsl2ShdslMaintTipRingReversal OBJECT-TYPE 1588 SYNTAX INTEGER 1589 { 1590 normal(1), 1591 reversed(2) 1592 } 1593 MAX-ACCESS read-only 1594 STATUS current 1595 DESCRIPTION 1596 "This object indicates the state of the tip/ring pair at 1597 the associated segment endpoint." 1598 ::= { hdsl2ShdslEndpointMaintEntry 2 } 1600 hdsl2ShdslMaintPowerBackOff OBJECT-TYPE 1601 SYNTAX INTEGER 1602 { 1603 default(1), 1604 enhanced(2) 1605 } 1606 MAX-ACCESS read-write 1607 STATUS current 1608 DESCRIPTION 1609 "This object configures the receiver at the associated 1610 segment endpoint to operate in default or enhanced power 1611 backoff mode." 1612 ::= { hdsl2ShdslEndpointMaintEntry 3 } 1614 hdsl2ShdslMaintSoftRestart OBJECT-TYPE 1615 SYNTAX INTEGER 1616 { 1617 ready(1), 1618 restart(2) 1619 } 1620 MAX-ACCESS read-write 1622 Expires November 8, 2000 Page [29] 1623 STATUS current 1624 DESCRIPTION 1625 "This object enables the manager to trigger a soft restart 1626 of the modem at the associated segment endpoint. The manager 1627 may only set this object to the 'restart(2)' value to initiate 1628 a restart. The agent will perform a restart after approximately 1629 5 seconds, and restore the object to the 'ready(1)' state." 1630 ::= { hdsl2ShdslEndpointMaintEntry 4 } 1632 hdsl2ShdslUnitMaintTable OBJECT-TYPE 1633 SYNTAX SEQUENCE OF Hdsl2ShdslUnitMaintEntry 1634 MAX-ACCESS not-accessible 1635 STATUS current 1636 DESCRIPTION 1637 "This table supports maintenance operations for units in a 1638 HDSL2/SHDSL line." 1639 ::= { hdsl2ShdslMibObjects 9 } 1641 hdsl2ShdslUnitMaintEntry OBJECT-TYPE 1642 SYNTAX Hdsl2ShdslUnitMaintEntry 1643 MAX-ACCESS not-accessible 1644 STATUS current 1645 DESCRIPTION 1646 "An entry in the hdsl2ShdslUnitMaintTable. Each entry 1647 corresponds to a single unit, and is indexed by the 1648 ifIndex of the HDSL2/SHDSL line and the UnitId of the 1649 associated unit." 1650 INDEX { ifIndex, hdsl2ShdslInvIndex } 1651 ::= { hdsl2ShdslUnitMaintTable 1 } 1653 Hdsl2ShdslUnitMaintEntry ::= 1654 SEQUENCE 1655 { 1656 hdsl2ShdslMaintLoopbackTimeout Integer32, 1657 hdsl2ShdslMaintUnitPowerSource INTEGER 1658 } 1660 hdsl2ShdslMaintLoopbackTimeout OBJECT-TYPE 1661 SYNTAX Integer32 1662 MAX-ACCESS read-write 1663 STATUS current 1664 DESCRIPTION 1665 "This object configures the timeout value for loopbacks 1666 initiated at segments endpoints contained in the associated 1667 unit. A value of 0 disables the timeout." 1668 ::= { hdsl2ShdslUnitMaintEntry 1 } 1670 hdsl2ShdslMaintUnitPowerSource OBJECT-TYPE 1671 SYNTAX INTEGER 1672 { 1673 local(1), 1674 span(2) 1675 } 1676 MAX-ACCESS read-only 1677 STATUS current 1679 Expires November 8, 2000 Page [30] 1680 DESCRIPTION 1681 "This object indicates the DC power source being used by the 1682 associated unit." 1683 ::= { hdsl2ShdslUnitMaintEntry 2 } 1685 -- Span Configuration Profile Group 1686 -- 1688 hdsl2ShdslSpanConfProfileTable OBJECT-TYPE 1689 SYNTAX SEQUENCE OF Hdsl2ShdslSpanConfProfileEntry 1690 MAX-ACCESS not-accessible 1691 STATUS current 1692 DESCRIPTION 1693 "This table supports definitions of span configuration 1694 profiles for SHDSL lines. HDSL2 does not support these 1695 configuration options." 1696 ::= { hdsl2ShdslMibObjects 10 } 1698 hdsl2ShdslSpanConfProfileEntry OBJECT-TYPE 1699 SYNTAX Hdsl2ShdslSpanConfProfileEntry 1700 MAX-ACCESS not-accessible 1701 STATUS current 1702 DESCRIPTION 1703 "Each entry corresponds to a single span configuration 1704 profile. Each profile contains a set of span configuration 1705 parameters. The configuration parameters in a profile are 1706 applied to those lines referencing that profile (see the 1707 hdsl2ShdslSpanConfProfile object). Profiles may be 1708 created/deleted using the row creation/deletion mechanism 1709 via hdsl2ShdslSpanConfProfileRowStatus. Profiles that are 1710 being referenced may not be deleted." 1711 INDEX { hdsl2ShdslSpanConfProfileName } 1712 ::= { hdsl2ShdslSpanConfProfileTable 1 } 1714 Hdsl2ShdslSpanConfProfileEntry ::= 1715 SEQUENCE 1716 { 1717 hdsl2ShdslSpanConfProfileName SnmpAdminString, 1718 hdsl2ShdslSpanWireInterface INTEGER, 1719 hdsl2ShdslSpanLineSpeed Integer32, 1720 hdsl2ShdslSpanConfPSD INTEGER, 1721 hdsl2ShdslSpanRemoteEnabled INTEGER, 1722 hdsl2ShdslSpanConfProfileRowStatus RowStatus 1723 } 1725 hdsl2ShdslSpanConfProfileName OBJECT-TYPE 1726 SYNTAX SnmpAdminString 1727 MAX-ACCESS read-create 1728 STATUS current 1729 DESCRIPTION 1730 "This object is the unique index associated with this profile." 1731 ::= { hdsl2ShdslSpanConfProfileEntry 1 } 1733 hdsl2ShdslSpanWireInterface OBJECT-TYPE 1734 SYNTAX INTEGER 1736 Expires November 8, 2000 Page [31] 1737 { 1738 twoWire(1), 1739 fourWire(2) 1740 } 1741 MAX-ACCESS read-create 1742 STATUS current 1743 DESCRIPTION 1744 "This object configures the two-wire or optional four-wire 1745 operation for SHDSL Lines." 1746 ::= { hdsl2ShdslSpanConfProfileEntry 2 } 1748 hdsl2ShdslSpanLineSpeed OBJECT-TYPE 1749 SYNTAX Integer32 1750 UNITS "bps" 1751 MAX-ACCESS read-create 1752 STATUS current 1753 DESCRIPTION 1754 "This object configures the transmission rate for the associated 1755 SHDSL Line in bits-per-second (bps)." 1756 ::= { hdsl2ShdslSpanConfProfileEntry 3 } 1758 hdsl2ShdslSpanConfPSD OBJECT-TYPE 1759 SYNTAX INTEGER 1760 { 1761 symmetric(1), 1762 asymmetric(2) 1763 } 1764 MAX-ACCESS read-create 1765 STATUS current 1766 DESCRIPTION 1767 "This object configures use of symmetric/asymmetric PSD (Power 1768 Spectral Density) Mask for the associated SHDSL Line. Support 1769 for symmetric PSD is mandatory for all supported data rates. 1770 Support for asymmetric PSD is optional." 1771 ::= { hdsl2ShdslSpanConfProfileEntry 4 } 1773 hdsl2ShdslSpanRemoteEnabled OBJECT-TYPE 1774 SYNTAX INTEGER 1775 { 1776 enabled(1), 1777 disabled(2) 1778 } 1779 MAX-ACCESS read-create 1780 STATUS current 1781 DESCRIPTION 1782 "This object enables/disables support for remote management 1783 of the units in a SHDSL line from the STU-R via the EOC." 1784 ::= { hdsl2ShdslSpanConfProfileEntry 5 } 1786 hdsl2ShdslSpanConfProfileRowStatus OBJECT-TYPE 1787 SYNTAX RowStatus 1788 MAX-ACCESS read-create 1789 STATUS current 1790 DESCRIPTION 1791 "This object controlls creation/deletion of the associated 1793 Expires November 8, 2000 Page [32] 1794 entry in this table per the semantics of RowStatus." 1795 ::= { hdsl2ShdslSpanConfProfileEntry 6 } 1797 -- Segment Endpoint Alarm Configuration Profile group 1798 -- 1800 hdsl2ShdslEndpointAlarmConfProfileTable OBJECT-TYPE 1801 SYNTAX SEQUENCE OF Hdsl2ShdslEndpointAlarmConfProfileEntry 1802 MAX-ACCESS not-accessible 1803 STATUS current 1804 DESCRIPTION 1805 "This table supports definitions of alarm configuration 1806 profiles for HDSL2/SHDSL segment endoints." 1807 ::= { hdsl2ShdslMibObjects 11 } 1809 hdsl2ShdslEndpointAlarmConfProfileEntry OBJECT-TYPE 1810 SYNTAX Hdsl2ShdslEndpointAlarmConfProfileEntry 1811 MAX-ACCESS not-accessible 1812 STATUS current 1813 DESCRIPTION 1814 "Each entry corresponds to a single alarm configuration 1815 profile. Each profile contains a set of parameters for setting 1816 alarm thresholds for various performance attributes monitored 1817 at HDSL2/SHDSL segment endpoints. Profiles may be 1818 created/deleted using the row creation/deletion mechanism via 1819 hdsl2ShdslEndpointAlarmConfProfileRowStatus. Profiles that 1820 are being referenced may not be deleted." 1821 INDEX { hdsl2ShdslEndpointAlarmConfProfileName } 1822 ::= { hdsl2ShdslEndpointAlarmConfProfileTable 1 } 1824 Hdsl2ShdslEndpointAlarmConfProfileEntry ::= 1825 SEQUENCE 1826 { 1827 hdsl2ShdslEndpointAlarmConfProfileName SnmpAdminString, 1828 hdsl2ShdslEndpointThreshLoopAttenuation Integer32, 1829 hdsl2ShdslEndpointThreshSNRMargin Integer32, 1830 hdsl2ShdslEndpointThreshES 1831 Hdsl2ShdslPerfIntervalThreshold, 1832 hdsl2ShdslEndpointThreshSES 1833 Hdsl2ShdslPerfIntervalThreshold, 1834 hdsl2ShdslEndpointThreshCRCanomalies Integer32, 1835 hdsl2ShdslEndpointThreshLOSWS 1836 Hdsl2ShdslPerfIntervalThreshold, 1837 hdsl2ShdslEndpointThreshUAS 1838 Hdsl2ShdslPerfIntervalThreshold, 1839 hdsl2ShdslEndpointAlarmConfProfileRowStatus RowStatus 1840 } 1842 hdsl2ShdslEndpointAlarmConfProfileName OBJECT-TYPE 1843 SYNTAX SnmpAdminString 1844 MAX-ACCESS read-create 1845 STATUS current 1846 DESCRIPTION 1847 "This object is the unique index associated with this profile." 1848 ::= { hdsl2ShdslEndpointAlarmConfProfileEntry 1 } 1850 Expires November 8, 2000 Page [33] 1851 hdsl2ShdslEndpointThreshLoopAttenuation OBJECT-TYPE 1852 SYNTAX Integer32 1853 UNITS "dB" 1854 MAX-ACCESS read-create 1855 STATUS current 1856 DESCRIPTION 1857 "This object configures the loop attentuation alarm threshold. 1858 When the current value reaches/exceeds this threshold, a 1859 hdsl2ShdslLoopAttenCrossingTrap will be generated." 1860 ::= { hdsl2ShdslEndpointAlarmConfProfileEntry 2 } 1862 hdsl2ShdslEndpointThreshSNRMargin OBJECT-TYPE 1863 SYNTAX Integer32 1864 UNITS "dB" 1865 MAX-ACCESS read-create 1866 STATUS current 1867 DESCRIPTION 1868 "This object configures the SNR margin alarm threshold. 1869 When the current value reaches/exceeds this threshold, a 1870 hdsl2ShdslSNRMarginCrossingTrap will be generated." 1871 ::= { hdsl2ShdslEndpointAlarmConfProfileEntry 3 } 1873 hdsl2ShdslEndpointThreshES OBJECT-TYPE 1874 SYNTAX Hdsl2ShdslPerfIntervalThreshold 1875 UNITS "seconds" 1876 MAX-ACCESS read-create 1877 STATUS current 1878 DESCRIPTION 1879 "This object configures the threshold for the number of 1880 errored seconds (ES) within any given 15-minute performance 1881 data collection interval. If the value of errored seconds 1882 in a particular 15-minute collection interval reaches/ 1883 exceeds this value, a hdsl2ShdslPerfESThreshTrap will be 1884 generated. One trap will be sent per interval per 1885 endpoint." 1886 ::= { hdsl2ShdslEndpointAlarmConfProfileEntry 4 } 1888 hdsl2ShdslEndpointThreshSES OBJECT-TYPE 1889 SYNTAX Hdsl2ShdslPerfIntervalThreshold 1890 UNITS "seconds" 1891 MAX-ACCESS read-create 1892 STATUS current 1893 DESCRIPTION 1894 "This object configures the threshold for the number of 1895 severely errored seconds (SES) within any given 15-minute 1896 performance data collection interval. If the value of severely 1897 errored seconds in a particular 15-minute collection interval 1898 reaches/exceeds this value, a hdsl2ShdslPerfSESThreshTrap will 1899 be generated. One trap will be sent per interval per endpoint." 1900 ::= { hdsl2ShdslEndpointAlarmConfProfileEntry 5 } 1902 hdsl2ShdslEndpointThreshCRCanomalies OBJECT-TYPE 1903 SYNTAX Integer32 1904 MAX-ACCESS read-create 1905 STATUS current 1907 Expires November 8, 2000 Page [34] 1908 DESCRIPTION 1909 "This object configures the threshold for the number of 1910 CRC anomalies within any given 15-minute performance data 1911 collection interval. If the value of CRC anomalies in a 1912 particular 15-minute collection interval reaches/exceeds 1913 this value, a hdsl2ShdslPerfCRCanomaliesThreshTrap will be 1914 generated. One trap will be sent per interval per endpoint." 1915 ::= { hdsl2ShdslEndpointAlarmConfProfileEntry 6 } 1917 hdsl2ShdslEndpointThreshLOSWS OBJECT-TYPE 1918 SYNTAX Hdsl2ShdslPerfIntervalThreshold 1919 UNITS "seconds" 1920 MAX-ACCESS read-create 1921 STATUS current 1922 DESCRIPTION 1923 "This object configures the threshold for the number of 1924 loss of sync word seconds (LOSWS) within any given 15-minute 1925 performance data collection interval. If the value of LOSWS 1926 in a particular 15-minute collection interval reaches/exceeds 1927 this value, a hdsl2ShdslPerfLOSWSThreshTrap will be generated. 1928 One trap will be sent per interval per endpoint." 1929 ::= { hdsl2ShdslEndpointAlarmConfProfileEntry 7 } 1931 hdsl2ShdslEndpointThreshUAS OBJECT-TYPE 1932 SYNTAX Hdsl2ShdslPerfIntervalThreshold 1933 UNITS "seconds" 1934 MAX-ACCESS read-create 1935 STATUS current 1936 DESCRIPTION 1937 "This object configures the threshold for the number of 1938 unavailable seconds (UAS) within any given 15-minute 1939 performance data collection interval. If the value of UAS 1940 in a particular 15-minute collection interval reaches/exceeds 1941 this value, a hdsl2ShdslPerfUASThreshTrap will be generated. 1942 One trap will be sent per interval per endpoint." 1943 ::= { hdsl2ShdslEndpointAlarmConfProfileEntry 8 } 1945 hdsl2ShdslEndpointAlarmConfProfileRowStatus OBJECT-TYPE 1946 SYNTAX RowStatus 1947 MAX-ACCESS read-create 1948 STATUS current 1949 DESCRIPTION 1950 "This object controls creation/deletion of the associated 1951 entry in this table as per the semantics of RowStatus." 1952 ::= { hdsl2ShdslEndpointAlarmConfProfileEntry 9 } 1954 -- Notifications Group 1955 -- 1957 hdsl2ShdslTraps OBJECT IDENTIFIER ::= { hdsl2ShdslLineMib 2 } 1958 hdsl2ShdslTrapsPrefix OBJECT IDENTIFIER ::= { hdsl2ShdslTraps 0 } 1960 hdsl2ShdslLoopAttenCrossingTrap NOTIFICATION-TYPE 1961 OBJECTS 1962 { 1964 Expires November 8, 2000 Page [35] 1965 ifIndex, 1966 hdsl2ShdslInvIndex, 1967 hdsl2ShdslEndpointSide, 1968 hdsl2ShdslEndpointWirePair, 1969 hdsl2ShdslEndpointCurrAtn, 1970 hdsl2ShdslEndpointThreshLoopAttenuation 1971 } 1972 STATUS current 1973 DESCRIPTION 1974 "This trap indicates that the loop attenuation threshold (as 1975 per the hdsl2ShdslEndpointThreshLoopAttenuation value) has been 1976 reached/exceeded for the HDSL2/SHDSL segment endpoint identified 1977 by the ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide, and 1978 hdsl2ShdslEndpointWirePair values." 1979 ::= { hdsl2ShdslTrapsPrefix 1 } 1981 hdsl2ShdslSNRMarginCrossingTrap NOTIFICATION-TYPE 1982 OBJECTS 1983 { 1984 ifIndex, 1985 hdsl2ShdslInvIndex, 1986 hdsl2ShdslEndpointSide, 1987 hdsl2ShdslEndpointWirePair, 1988 hdsl2ShdslEndpointCurrSnrMgn, 1989 hdsl2ShdslEndpointThreshSNRMargin 1990 } 1991 STATUS current 1992 DESCRIPTION 1993 "This trap indicates that the SNR margin threshold (as per the 1994 hdsl2ShdslEndpointThreshSNRMargin value) has been 1995 reached/exceeded for the HDSL2/SHDSL segment endpoint identified 1996 by the ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide, and 1997 hdsl2ShdslEndpointWirePair values." 1998 ::= { hdsl2ShdslTrapsPrefix 2 } 2000 hdsl2ShdslPerfESThreshTrap NOTIFICATION-TYPE 2001 OBJECTS 2002 { 2003 ifIndex, 2004 hdsl2ShdslInvIndex, 2005 hdsl2ShdslEndpointSide, 2006 hdsl2ShdslEndpointWirePair, 2007 hdsl2ShdslEndpointCurr15MinES, 2008 hdsl2ShdslEndpointThreshES 2009 } 2010 STATUS current 2011 DESCRIPTION 2012 "This trap indicates that the errored seconds threshold (as 2013 per the hdsl2ShdslEndpointThreshES value) has been reached/ 2014 exceeded for the HDSL2/SHDSL segment endpoint identified by the 2015 ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide, and 2016 hdsl2ShdslEndpointWirePair values." 2017 ::= { hdsl2ShdslTrapsPrefix 3 } 2019 Expires November 8, 2000 Page [36] 2020 hdsl2ShdslPerfSESThreshTrap NOTIFICATION-TYPE 2021 OBJECTS 2022 { 2023 ifIndex, 2024 hdsl2ShdslInvIndex, 2025 hdsl2ShdslEndpointSide, 2026 hdsl2ShdslEndpointWirePair, 2027 hdsl2ShdslEndpointCurr15MinSES, 2028 hdsl2ShdslEndpointThreshSES 2029 } 2030 STATUS current 2031 DESCRIPTION 2032 "This trap indicates that the severely errored seconds threshold 2033 (as per the hdsl2ShdslEndpointThreshSES value) has been reached/ 2034 exceeded for the HDSL2/SHDSL Segment Endpoint identified by the 2035 ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide, and 2036 hdsl2ShdslEndpointWirePair values." 2037 ::= { hdsl2ShdslTrapsPrefix 4 } 2039 hdsl2ShdslPerfCRCanomaliesThreshTrap NOTIFICATION-TYPE 2040 OBJECTS 2041 { 2042 ifIndex, 2043 hdsl2ShdslInvIndex, 2044 hdsl2ShdslEndpointSide, 2045 hdsl2ShdslEndpointWirePair, 2046 hdsl2ShdslEndpointCurr15MinCRCanomalies, 2047 hdsl2ShdslEndpointThreshCRCanomalies 2048 } 2049 STATUS current 2050 DESCRIPTION 2051 "This trap indicates that the CRC anomalies threshold (as 2052 per the hdsl2ShdslEndpointThreshCRCanomalies value) has been 2053 reached/exceeded for the HDSL2/SHDSL Segment Endpoint identified 2054 by the ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide, and 2055 hdsl2ShdslEndpointWirePair values." 2056 ::= { hdsl2ShdslTrapsPrefix 5 } 2058 hdsl2ShdslPerfLOSWSThreshTrap NOTIFICATION-TYPE 2059 OBJECTS 2060 { 2061 ifIndex, 2062 hdsl2ShdslInvIndex, 2063 hdsl2ShdslEndpointSide, 2064 hdsl2ShdslEndpointWirePair, 2065 hdsl2ShdslEndpointCurr15MinLOSWS, 2066 hdsl2ShdslEndpointThreshLOSWS 2067 } 2068 STATUS current 2069 DESCRIPTION 2070 "This trap indicates that the LOSW seconds threshold (as per the 2071 hdsl2ShdslEndpointThreshLOSWS value) has been reached/exceeded 2072 for the HDSL2/SHDSL segment endpoint identified by the ifIndex, 2073 hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide, and 2074 hdsl2ShdslEndpointWirePair values." 2076 Expires November 8, 2000 Page [37] 2077 ::= { hdsl2ShdslTrapsPrefix 6 } 2079 hdsl2ShdslPerfUASThreshTrap NOTIFICATION-TYPE 2080 OBJECTS 2081 { 2082 ifIndex, 2083 hdsl2ShdslInvIndex, 2084 hdsl2ShdslEndpointSide, 2085 hdsl2ShdslEndpointWirePair, 2086 hdsl2ShdslEndpointCurr15MinUAS, 2087 hdsl2ShdslEndpointThreshUAS 2088 } 2089 STATUS current 2090 DESCRIPTION 2091 "This trap indicates that the unavailable seconds threshold (as 2092 per the hdsl2ShdslEndpointThreshUAS value) has been reached/ 2093 exceeded for the HDSL2/SHDSL segment endpoint identified by the 2094 ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide, and 2095 hdsl2ShdslEndpointWirePair values." 2096 ::= { hdsl2ShdslTrapsPrefix 7 } 2098 hdsl2ShdslSpanInvalidNumRepeaters NOTIFICATION-TYPE 2099 OBJECTS 2100 { 2101 ifIndex, 2102 hdsl2ShdslConfNumRepeaters 2103 } 2104 STATUS current 2105 DESCRIPTION 2106 "This trap indicates that a mismatch has been detected between 2107 the number of repeater/regenerator units configured for a 2108 HDSL2/SHDSL line via the hdsl2ShdslConfNumRepeaters object and 2109 the actual number of repeater/regenerator units discovered via 2110 the EOC." 2111 ::= { hdsl2ShdslTrapsPrefix 8 } 2113 -- conformance information 2115 hdsl2ShdslConformance OBJECT IDENTIFIER ::= { hdsl2ShdslLineMib 3 } 2116 hdsl2ShdslGroups OBJECT IDENTIFIER ::= { hdsl2ShdslConformance 1 } 2117 hdsl2ShdslCompliances OBJECT IDENTIFIER ::= { hdsl2ShdslConformance 2 } 2119 -- agent compliance statements 2121 hdsl2ShdslLineMibCompliance MODULE-COMPLIANCE 2122 STATUS current 2123 DESCRIPTION 2124 "The section outlines compliance requirements for this MIB." 2125 MODULE 2126 MANDATORY-GROUPS 2127 { 2128 hdsl2ShdslSpanConfGroup, 2129 hdsl2ShdslInventoryGroup, 2130 hdsl2ShdslEndpointConfGroup, 2131 hdsl2ShdslEndpointCurrGroup, 2133 Expires November 8, 2000 Page [38] 2134 hdsl2Shdsl15MinIntervalGroup, 2135 hdsl2Shdsl1DayIntervalGroup, 2136 hdsl2ShdslMaintenanceGroup, 2137 hdsl2ShdslEndpointAlarmConfGroup, 2138 hdsl2ShdslNotificationGroup 2139 } 2141 GROUP hdsl2ShdslSpanConfProfileGroup 2142 DESCRIPTION 2143 "Support for this group is only required for implementations 2144 supporting SHDSL lines." 2146 ::= { hdsl2ShdslCompliances 1 } 2148 -- units of conformance 2150 hdsl2ShdslSpanConfGroup OBJECT-GROUP 2151 OBJECTS 2152 { 2153 hdsl2ShdslConfNumRepeaters, 2154 hdsl2ShdslSpanConfProfile, 2155 hdsl2ShdslSpanAlarmConfProfile 2156 } 2157 STATUS current 2158 DESCRIPTION 2159 "This group supports objects for configuring span related 2160 parameters for HDSL2/SHDSL lines." 2161 ::= { hdsl2ShdslGroups 1 } 2163 hdsl2ShdslInventoryGroup OBJECT-GROUP 2164 OBJECTS 2165 { 2166 hdsl2ShdslInvIndex, 2167 hdsl2ShdslInvVendorID, 2168 hdsl2ShdslInvVendorModelNumber, 2169 hdsl2ShdslInvVendorSerialNumber, 2170 hdsl2ShdslInvVendorEOCSoftwareVersion, 2171 hdsl2ShdslInvStandardVersion, 2172 hdsl2ShdslInvVendorListNumber, 2173 hdsl2ShdslInvVendorIssueNumber, 2174 hdsl2ShdslInvVendorSoftwareVersion, 2175 hdsl2ShdslInvEquipmentCode, 2176 hdsl2ShdslInvVendorOther 2177 } 2178 STATUS current 2179 DESCRIPTION 2180 "This group supports objects that provide unit inventory 2181 information about the units in HDSL2/SHDSL lines." 2182 ::= { hdsl2ShdslGroups 2 } 2184 hdsl2ShdslEndpointConfGroup OBJECT-GROUP 2185 OBJECTS 2186 { 2187 hdsl2ShdslEndpointSide, 2188 hdsl2ShdslEndpointWirePair, 2190 Expires November 8, 2000 Page [39] 2191 hdsl2ShdslEndpointAlarmConfProfile 2192 } 2193 STATUS current 2194 DESCRIPTION 2195 "This group supports objects for configuring parameters for 2196 segment endpoints in HDSL2/SHDSL lines." 2197 ::= { hdsl2ShdslGroups 3 } 2199 hdsl2ShdslEndpointCurrGroup OBJECT-GROUP 2200 OBJECTS 2201 { 2202 hdsl2ShdslEndpointSide, 2203 hdsl2ShdslEndpointWirePair, 2204 hdsl2ShdslEndpointCurrAtn, 2205 hdsl2ShdslEndpointCurrSnrMgn, 2206 hdsl2ShdslEndpointCurrStatus, 2207 hdsl2ShdslEndpointES, 2208 hdsl2ShdslEndpointSES, 2209 hdsl2ShdslEndpointCRCanomalies, 2210 hdsl2ShdslEndpointLOSWS, 2211 hdsl2ShdslEndpointUAS, 2212 hdsl2ShdslEndpointCurr15MinTimeElapsed, 2213 hdsl2ShdslEndpointCurr15MinES, 2214 hdsl2ShdslEndpointCurr15MinSES, 2215 hdsl2ShdslEndpointCurr15MinCRCanomalies, 2216 hdsl2ShdslEndpointCurr15MinLOSWS, 2217 hdsl2ShdslEndpointCurr15MinUAS, 2218 hdsl2ShdslEndpointCurr1DayTimeElapsed, 2219 hdsl2ShdslEndpointCurr1DayES, 2220 hdsl2ShdslEndpointCurr1DaySES, 2221 hdsl2ShdslEndpointCurr1DayCRCanomalies, 2222 hdsl2ShdslEndpointCurr1DayLOSWS, 2223 hdsl2ShdslEndpointCurr1DayUAS 2224 } 2225 STATUS current 2226 DESCRIPTION 2227 "This group supports objects which provide current status and 2228 performance measurements relating to segment endpoints in 2229 HDSL2/SHDSL lines." 2230 ::= { hdsl2ShdslGroups 4 } 2232 hdsl2Shdsl15MinIntervalGroup OBJECT-GROUP 2233 OBJECTS 2234 { 2235 hdsl2Shdsl15MinIntervalES, 2236 hdsl2Shdsl15MinIntervalSES, 2237 hdsl2Shdsl15MinIntervalCRCanomalies, 2238 hdsl2Shdsl15MinIntervalLOSWS, 2239 hdsl2Shdsl15MinIntervalUAS 2240 } 2241 STATUS current 2242 DESCRIPTION 2243 "This group supports objects which maintain historic performance 2244 measurements relating to segment endpoints in HDSL2/SHDSL lines 2245 in 15-minute intervals." 2247 Expires November 8, 2000 Page [40] 2248 ::= { hdsl2ShdslGroups 5 } 2250 hdsl2Shdsl1DayIntervalGroup OBJECT-GROUP 2251 OBJECTS 2252 { 2253 hdsl2Shdsl1DayIntervalMoniSecs, 2254 hdsl2Shdsl1DayIntervalES, 2255 hdsl2Shdsl1DayIntervalSES, 2256 hdsl2Shdsl1DayIntervalCRCanomalies, 2257 hdsl2Shdsl1DayIntervalLOSWS, 2258 hdsl2Shdsl1DayIntervalUAS 2259 } 2260 STATUS current 2261 DESCRIPTION 2262 "This group supports objects which maintain historic performance 2263 measurements relating to segment endpoints in HDSL2/SHDSL lines 2264 in 1-day intervals." 2265 ::= { hdsl2ShdslGroups 6 } 2267 hdsl2ShdslMaintenanceGroup OBJECT-GROUP 2268 OBJECTS 2269 { 2270 hdsl2ShdslMaintLoopbackConfig, 2271 hdsl2ShdslMaintTipRingReversal, 2272 hdsl2ShdslMaintPowerBackOff, 2273 hdsl2ShdslMaintSoftRestart, 2274 hdsl2ShdslMaintLoopbackTimeout, 2275 hdsl2ShdslMaintUnitPowerSource 2276 } 2277 STATUS current 2278 DESCRIPTION 2279 "This group supports objects that provide support for 2280 maintenance actions for HDSL2/SHDSL lines." 2281 ::= { hdsl2ShdslGroups 7 } 2283 hdsl2ShdslEndpointAlarmConfGroup OBJECT-GROUP 2284 OBJECTS 2285 { 2286 hdsl2ShdslEndpointAlarmConfProfileName, 2287 hdsl2ShdslEndpointThreshLoopAttenuation, 2288 hdsl2ShdslSpanWireInterface, 2289 hdsl2ShdslEndpointThreshSNRMargin, 2290 hdsl2ShdslEndpointThreshES, 2291 hdsl2ShdslEndpointThreshSES, 2292 hdsl2ShdslEndpointThreshCRCanomalies, 2293 hdsl2ShdslEndpointThreshLOSWS, 2294 hdsl2ShdslEndpointThreshUAS, 2295 hdsl2ShdslEndpointAlarmConfProfileRowStatus 2296 } 2297 STATUS current 2298 DESCRIPTION 2299 "This group supports objects that allow configuration of alarm 2300 thresholds for various performance parameters for HDSL2/SHDSL 2301 lines." 2302 ::= { hdsl2ShdslGroups 8 } 2304 Expires November 8, 2000 Page [41] 2305 hdsl2ShdslNotificationGroup NOTIFICATION-GROUP 2306 NOTIFICATIONS 2307 { 2308 hdsl2ShdslLoopAttenCrossingTrap, 2309 hdsl2ShdslSNRMarginCrossingTrap, 2310 hdsl2ShdslPerfESThreshTrap, 2311 hdsl2ShdslPerfSESThreshTrap, 2312 hdsl2ShdslPerfCRCanomaliesThreshTrap, 2313 hdsl2ShdslPerfLOSWSThreshTrap, 2314 hdsl2ShdslPerfUASThreshTrap, 2315 hdsl2ShdslSpanInvalidNumRepeaters 2316 } 2317 STATUS current 2318 DESCRIPTION 2319 "This group supports traps that enable notification of 2320 significant events/conditions associated with HDSL2/SHDSL 2321 lines." 2322 ::= { hdsl2ShdslGroups 9 } 2324 hdsl2ShdslSpanConfProfileGroup OBJECT-GROUP 2325 OBJECTS 2326 { 2327 hdsl2ShdslSpanConfProfileName, 2328 hdsl2ShdslSpanWireInterface, 2329 hdsl2ShdslSpanLineSpeed, 2330 hdsl2ShdslSpanRemoteEnabled, 2331 hdsl2ShdslSpanConfPSD, 2332 hdsl2ShdslSpanConfProfileRowStatus 2333 } 2334 STATUS current 2335 DESCRIPTION 2336 "This group supports objects that constitute configuration 2337 profiles for configuring span related parameters in SHDSL 2338 lines." 2339 ::= { hdsl2ShdslGroups 10 } 2341 END 2343 7. Security Considerations 2345 Security issues are not discussed in this memo. 2347 8. Acknowledgments 2349 The authors are deeply grateful to the authors of the ADSL LINE MIB 2350 (RFC 2662 [25]), Gregory Bathrick and Faye Ly, as much of the text 2351 and structure of this document originates in their documents. 2353 The authors also acknowledge the importance of contributions and 2354 suggestions regarding interface indexing structures received from 2355 David Horton of CITR. 2357 Other contributions were received from the following: 2359 Philip Bergstresser (Adtran) 2361 Expires November 8, 2000 Page [42] 2362 Steve Blackwell (Adtran) 2364 Mark Johnson (Red Point) 2366 Sharon Mantin (Orckit) 2368 Katy Sherman (Orckit) 2370 Mike Sneed (Pulse) 2372 9. References 2374 [1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 2375 Describing SNMP Management Frameworks", RFC 2571, April 1999. 2377 [2] Rose, M., and K. McCloghrie, "Structure and Identification of 2378 Management Information for TCP/IP-based Internets", STD 16, RFC 2379 1155, May 1990. 2381 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 16, 2382 RFC 1212, March 1991. 2384 [4] M. Rose, "A Convention for Defining Traps for use with the SNMP", 2385 RFC 1215, March 1991. 2387 [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 2388 M., and S. Waldbusser, "Structure of Management Information 2389 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 2391 [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 2392 M., and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, 2393 RFC 2579, April 1999. 2395 [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 2396 M., and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, 2397 RFC 2580, April 1999. 2399 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 2400 Network Management Protocol", STD 15, RFC 1157, May 1990. 2402 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2403 "Introduction to Community-based SNMPv2", RFC 1901, January 2404 1996. 2406 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport 2407 Mappings for Version 2 of the Simple Network Management Protocol 2408 (SNMPv2)", RFC 1906, January 1996. 2410 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 2411 Processing and Dispatching for the Simple Network Management 2412 Protocol (SNMP)", RFC 2572, April 1999. 2414 [12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) 2415 for version 3 of the Simple Network Management Protocol (SNMPv3)", 2416 RFC 2574, April 1999. 2418 Expires November 8, 2000 Page [43] 2419 [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 2420 Operations for Version 2 of the Simple Network Management Protocol 2421 (SNMPv2)", RFC 1905, January 1996. 2423 [14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 2424 2573, April 1999. 2426 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 2427 Control Model (VACM) for the Simple Network Management Protocol 2428 (SNMP)", RFC 2575, April 1999. 2430 [16] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction to 2431 Version 3 of the Internet-standard Network Management Framework", 2432 RFC 2570, April 1999. 2434 [17] Bradner, S., "Key Words for use in RFCs to Indicate Requirement 2435 Levels", RFC 2119, March 1997. 2437 [18] American National Standards Institute, ANSI T1E1.4/2000-006, 2438 February 2000. 2440 [19] Blackwell, S., Editor, "Single-Pair High-Speed Digital Subscriber 2441 Line (SHDSL) Transceivers", ITU-T Draft G.991.2, April 2000. 2443 [20] McCloghrie, K., and M. Rose, Editors, "Management Information Base 2444 for Network Management of TCP/IP-based internets: MIB-II", STD 17, 2445 RFC 1213, March 1991. 2447 [21] McCloghrie, K., and Kastenholz, F., "The Interfaces Group MIB", 2448 RFC 2863, June 2000. 2450 [22] Tesink, K., "Textual Conventions for MIB Modules Using Performance 2451 History Based on 15 Minute Intervals", RFC 2493, January 1999. 2453 [23] Bathrick, G., Ly, F., "Definitions of Managed Objects for the ADSL 2454 Lines", RFC 2662, August 1999. 2456 10. Intellectual Property Notice 2458 The IETF takes no position regarding the validity or scope of any 2459 intellectual property or other rights that might be claimed to 2460 pertain to the implementation or use of the technology described in 2461 this document or the extent to which any license under such rights 2462 might or might not be available; neither does it represent that it 2463 has made any effort to identify any such rights. Information on the 2464 IETF's procedures with respect to rights in standards-track and 2465 standards-related documentation can be found in BCP-11. Copies of 2466 claims of rights made available for publication and any assurances of 2467 licenses to be made available, or the result of an attempt made to 2468 obtain a general license or permission for the use of such 2469 proprietary rights by implementors or users of this specification can 2470 be obtained from the IETF Secretariat. 2472 The IETF invites any interested party to bring to its attention any 2473 copyrights, patents or patent applications, or other proprietary 2475 Expires November 8, 2000 Page [44] 2476 rights which may cover technology that may be required to practice 2477 this standard. Please address the information to the IETF Executive 2478 Director. 2480 11. Authors' Addresses 2482 Bob Ray 2483 Verilink Corporation 2484 127 Jetplex Circle 2485 Madison, AL 35758 USA 2486 Tel: +1 256-774-2380 2487 Fax: +1 256-774-2277 2488 E-mail: bray@verilink.com 2490 Rajesh Abbi 2491 Alcatel USA 2492 2912 Wake Forest Road 2493 Raleigh, NC 27609-7860 USA 2494 Tel: +1 919-950-6194 2495 Fax: +1 919-950-6670 2496 E-mail: Rajesh.Abbi@usa.alcatel.com 2498 12. Full Copyright Statement 2500 Copyright (C) The Internet Society (1999). All Rights Reserved. 2502 This document and translations of it may be copied and furnished to 2503 others, and derivative works that comment on or otherwise explain it 2504 or assist in its implementation may be prepared, copied, published 2505 and distributed, in whole or in part, without restriction of any 2506 kind, provided that the above copyright notice and this paragraph are 2507 included on all such copies and derivative works. However, this 2508 document itself may not be modified in any way, such as by removing 2509 the copyright notice or references to the Internet Society or other 2510 Internet organizations, except as needed for the purpose of 2511 developing Internet standards in which case the procedures for 2512 copyrights defined in the Internet Standards process must be 2513 followed, or as required to translate it into languages other than 2514 English. 2516 The limited permissions granted above are perpetual and will not be 2517 revoked by the Internet Society or its successors or assigns. 2519 This document and the information contained herein is provided on an 2520 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 2521 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 2522 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 2523 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 2524 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 2526 Expires November 8, 2000 Page [45]