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