idnits 2.17.1 draft-ietf-adslmib-hdsl2-10.txt: ** The Abstract section seems to be numbered Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == The page length should not exceed 58 lines per page, but there was 57 longer pages, the longest (page 2) being 59 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 58 pages 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. ** The abstract seems to contain references ([18], [19], 7], [5,6,, [2,3]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 2188 has weird spacing: '...aseDown wor...' -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (July 2001) is 8319 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) ** Obsolete normative reference: RFC 2571 (ref. '1') (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. '4') ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '8') ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. '9') ** Obsolete normative reference: RFC 1906 (ref. '10') (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2572 (ref. '11') (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (ref. '12') (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (ref. '13') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (ref. '14') (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (ref. '15') (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2570 (ref. '16') (Obsoleted by RFC 3410) -- Possible downref: Non-RFC (?) normative reference: ref. '18' -- Possible downref: Non-RFC (?) normative reference: ref. '19' ** Obsolete normative reference: RFC 2493 (ref. '22') (Obsoleted by RFC 3593) Summary: 24 errors (**), 0 flaws (~~), 4 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group B. Ray 2 Request for Comments: xxxx Verilink Corporation 3 Category: Standards Track R. Abbi 4 Alcatel 5 July 2001 7 Definitions of Managed Objects for HDSL2 and SHDSL Lines 8 draft-ietf-adslmib-hdsl2-10.txt 10 Status of this Memo 12 This document specifies an Internet standards track protocol for the 13 Internet community, and requests discussion and suggestions for 14 improvements. Please refer to the current edition of the "Internet 15 Official Protocol Standards" (STD 1) for the standardization state 16 and status of this protocol. Distribution of this memo is unlimited. 18 Copyright Notice 20 Copyright (C) The Internet Society (2001). All Rights Reserved. 22 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 24 Table of Contents 26 1. Abstract .................................................. 2 27 2. The SNMP Network Management Framework ..................... 2 28 3. Introduction .............................................. 3 29 3.1 Relationship of the HDSL2/SHDSL Line MIB to other MIBs .... 3 30 4. Conventions used in the MIB ............................... 5 31 4.1 Naming Conventions ........................................ 5 32 4.2 Textual Conventions ....................................... 5 33 4.3 Structure ................................................. 6 34 4.4 Counters, Interval Buckets and Thresholds ................. 9 35 4.5 Profiles .................................................. 9 36 4.6 Notifications ............................................. 10 37 5. Conformance and Compliance ................................ 12 38 6. Definitions ............................................... 12 39 7. Security Considerations ................................... 53 40 8. Acknowledgments ........................................... 54 41 9. References ................................................ 55 42 10. Intellectual Property Notice .............................. 56 43 11. Authors' Addresses ........................................ 57 44 12. Full Copyright Statement .................................. 57 46 1. Abstract 48 This document defines a portion of the Management Information Base 49 (MIB) module for use with network management protocols in the 50 Internet community. In particular, it describes objects used for 51 managing High Bit-Rate DSL - 2nd generation (HDSL2) [18] and 52 Single-Pair High-Speed Digital Subscriber Line (SHDSL) interfaces 53 [19]. 55 This document specifies a MIB module in a manner that is both 56 compliant to the SMIv2 (STD 58 [5, 6, 7]), and semantically 57 identical to the peer SMIv1 definitions (STD 16 [2, 3]). 59 2. The SNMP Management Framework 61 The SNMP Management Framework presently consists of five major 62 components: 64 o An overall architecture, described in RFC 2571 [1]. 66 o Mechanisms for describing and naming objects and events for the 67 purpose of management. The first version of this Structure of 68 Management Information (SMI) is called SMIv1 and described in 69 STD 16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4]. 70 The second version, called SMIv2, is described in STD 58, RFC 71 2578 [5], STD 58, RFC 2579 [6] and STD 58, RFC 2580 [7]. 73 o Message protocols for transferring management information. The 74 first version of the SNMP message protocol is called SNMPv1 and 75 described in STD 15, RFC 1157 [8]. A second version of the SNMP 76 message protocol, which is not an Internet standards track 78 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 80 protocol, is called SNMPv2c and described in RFC 1901 [9] and 81 RFC 1906 [10]. The third version of the message protocol is 82 called SNMPv3 and described in RFC 1906 [10], RFC 2572 [11] and 83 RFC 2574 [12]. 85 o Protocol operations for accessing management information. The 86 first set of protocol operations and associated PDU formats is 87 described in STD 15, RFC 1157 [8]. A second set of protocol 88 operations and associated PDU formats is described in RFC 1905 89 [13]. 91 o A set of fundamental applications described in RFC 2573 [14] 92 and the view-based access control mechanism described in RFC 93 2575 [15]. 95 A more detailed introduction to the current SNMP Management Framework 96 can be found in RFC 2570 [16]. 98 Managed objects are accessed via a virtual information store, termed 99 the Management Information Base or MIB. Objects in the MIB are 100 defined using the mechanisms defined in the SMI. 102 This memo specifies a MIB module that is compliant to the SMIv2. A 103 MIB conforming to the SMIv1 can be produced through the appropriate 104 translations. The resulting translated MIB must be semantically 105 equivalent, except where objects or events are omitted because no 106 translation is possible (use of Counter64). Some machine readable 107 information in SMIv2 will be converted into textual descriptions in 108 SMIv1 during the translation process. However, this loss of machine 109 readable information is not considered to change the semantics of the 110 MIB. 112 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 113 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 114 this document are to be interpreted as described in RFC 2119 [17]. 116 3. Introduction 118 This document describes an SNMP MIB for managing HDSL2/SHDSL Lines. 119 These definitions are based upon the specifications for the HDSL2 and 120 SHDSL Embedded Operations Channel (EOC) as defined in ANSI 121 T1E1.4/2000-006 [18] and ITU G.991.2 [19]. 123 The MIB is located in the MIB tree under MIB 2 transmission, as 124 discussed in the MIB-2 Integration (RFC 1213 [20] and RFC 2863 [21]) 125 section of this document. 127 3.1. Relationship of the HDSL2/SHDSL Line MIB to other MIBs 129 This section outlines the relationship of this MIB with other MIBs 130 described in RFCs. Specifically, IF-MIB as presented RFC 2863 [21] 131 is discussed. 133 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 135 3.1.1 General IF-MIB Integration (RFC 2863) 137 The HDSL2/SHDSL Line MIB specifies the detailed attributes of a data 138 interface. As such, it needs to integrate with RFC 2863 [21]. The 139 IANA has assigned the following ifTypes to HDSL2 and SHDSL: 141 IANAifType ::= TEXTUAL-CONVENTION 142 ... 143 SYNTAX INTEGER { 144 ... 145 hdsl2 (168), -- High Bit-Rate DSL, 2nd generation 146 shdsl (169), -- Multirate HDSL2 147 ... 148 } 150 3.1.2 Usage of ifTable 152 The MIB branch identified by this ifType contains tables appropriate 153 for this interface type. Most such tables extend the ifEntry table, 154 and are indexed by ifIndex. For interfaces in systems implementing 155 this MIB, those table entries indexed by ifIndex MUST be persistent. 157 The following attributes are part of the mandatory ifGeneral group in 158 RFC 2863 [21], and are not duplicated in the HDSL2/SHDSL Line MIB. 160 =================================================================== 161 ifIndex Interface index. 163 ifDescr See interfaces MIB [21]. 165 ifType hdsl2(168) or shdsl(169). 167 ifSpeed Set as appropriate. 168 (This is fixed at 1552000 for HDSL2 169 lines) 171 ifPhysAddress This object MUST have an octet string 172 with zero length. 174 ifAdminStatus See interfaces MIB [21]. 176 ifOperStatus See interfaces MIB [21]. 178 ifLastChange See interfaces MIB [21]. 180 ifName See interfaces MIB [21]. 182 ifLinkUpDownTrapEnable Default to enabled(1). 184 ifHighSpeed Set as appropriate. 185 (For HDSL2 lines, this is fixed at 2) 187 ifConnectorPresent Set as appropriate. 189 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 191 =================================================================== 192 Figure 1: Use of ifTable Objects 194 4. Conventions used in the MIB 196 4.1. Naming Conventions 198 A. xtuC refers to a central site terminal unit; 199 H2TU-C for HDSL2, or STU-C for SHDSL. 200 B. xtuR refers to a remote site terminal unit; 201 H2TU-R for HDSL2, or STU-R for SHDSL. 202 C. xtu refers to a terminal unit; either an xtuC or xtuR. 203 D. xru refer to a regenerator unit; 204 H2RU for HDSL2, or SRU for SHDSL. 205 E. xU refers to any HDSL2/SHDSL unit; either an xtu or xru. 206 F. CRC is cyclic redundancy check [19]. 207 G. ES means errored second [19]. 208 H. LOSW means loss of sync word [19]. 209 I. LOSWS means LOSW seconds [19]. 210 J. SES means severely errored second [19]. 211 K. SNR means signal-to-noise ratio [19]. 212 L. UAS means unavailable second [19]. 214 4.2. Textual Conventions 216 The following textual conventions are defined to reflect the line 217 topology in the MIB (further discussed in the following section) 218 and to define the behavior of the statistics to be maintained 219 by an agent. 221 o Hdsl2ShdslUnitId : 223 Attributes with this syntax uniquely identify each unit in a 224 HDSL2/SHDSL span. It mirrors the EOC addressing mechanism: 226 xtuC(1) - CO terminal unit 227 xtuR(2) - CPE terminal unit 228 xru1(3) .. xru8(10) - regenerators, numbered from 229 central office side 231 o Hdsl2ShdslUnitSide: 233 Attributes with this syntax reference the two sides of a unit: 235 networkSide(1) - N in figure 2, below 236 customerSide(2) - C in figure 2, below 238 o Hdsl2ShdslWirePair: 240 Attributes with this syntax reference the wire-pairs connecting 241 the units: 243 wirePair1(1) - First pair for HDSL2/SHDSL. 245 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 247 wirePair2(2) - Optional second pair for SHDSL only. 249 o Hdsl2ShdslTransmissionModeType: 251 Attributes with this syntax specify the regional setting for a 252 SHDSL line. Specified as a BITS construct, the two mode types are: 253 region1 - ITU-T G.991.2 Annex A 254 region2 - ITU-T G.991.2 Annex B 256 o Hdsl2ShdslPerfCurrDayCount: 258 Attributes with this syntax define the behavior of the 1-day (24 259 hour) gauges found in the MIB. 261 o Hdsl2Shdsl1DayIntervalCount: 263 Attributes with this syntax define the behavior of the 1-day (24 264 hour) interval counters found in the MIB. 266 o Hdsl2ShdslPerfTimeElapsed: 268 Attributes with this syntax define the behavior of the elapsed 269 time counters found in the MIB. 271 o Hdsl2ShdslPerfIntervalThreshold: 273 Attributes with this syntax define the behavior of the alarm 274 thresholds found in the MIB. 276 4.3. Structure 278 The MIB is structured into following MIB groups: 280 o Span Configuration Group: 282 This group supports MIB objects for configuring parameters for 283 the HDSL2/SHDSL span. It contains the following table: 285 - hdsl2ShdslSpanConfTable 287 o Span Status Group: 289 This group supports MIB objects for retrieving span status 290 information. It contains the following table: 292 - hdsl2ShdslSpanStatusTable 294 o Unit Inventory Group: 296 This group supports MIB objects for retrieving unit inventory 297 information about units in HDSL2/SHDSL lines via the EOC. It 298 contains the following table: 300 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 302 - hdsl2ShdslInventoryTable 304 o Segment Endpoint Configuration Group: 306 This group supports MIB objects for configuring parameters for 307 the HDSL2/SHDSL segment endpoints. It contains the following 308 table: 310 - hdsl2ShdslEndpointConfTable 312 o Segment Endpoint Current Status/Performance Group: 314 This group supports MIB objects that provide the current 315 status/performance information relating to segment endpoints. 316 It contains the following table: 318 - hdsl2ShdslEndpointCurrTable 320 o Segment Endpoint 15-Minute Interval Status/Performance Group: 322 This group supports MIB objects that provide historic 323 status/performance information relating to segment endpoints 324 in 15-minute intervals. It contains the following table: 326 - hdsl2Shdsl15MinIntervalTable 328 o Segment Endpoint 1-Day Interval Status/Performance Group: 330 This group supports MIB objects that provide historic 331 status/performance information relating to segment endpoints 332 in 1-day intervals. It contains the following table: 334 - hdsl2Shdsl1DayIntervalTable 336 o Maintenance Group: 338 This group supports MIB objects for performing maintenance 339 operations such as loopbacks for HDSL2/SHDSL lines. It contains 340 the following table(s): 342 - hdsl2ShdslEndpointMaintTable 343 - hdsl2ShdslUnitMaintTable 345 o Span Configuration Profile Group: 347 This group supports MIB objects for defining configuration profiles 348 for HDSL2/SHDSL Spans. It contains the following table: 350 - hdsl2ShdslSpanConfProfileTable 352 o Segment Endpoint Alarm Configuration Profile Group: 354 This group supports MIB objects for defining alarm configuration 356 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 358 profiles for HDSL2/SHDSL Segment Endpoints. It contains the 359 following table: 361 - hdsl2ShdslEndpointAlarmConfProfileTable 363 o Notifications Group: 365 This group defines the notifications supported for HDSL2/SHDSL 366 lines: 368 - hdsl2ShdslLoopAttenCrossing 369 - hdsl2ShdslSNRMarginCrossing 370 - hdsl2ShdslPerfESThresh 371 - hdsl2ShdslPerfSESThresh 372 - hdsl2ShdslPerfCRCanomaliesThresh 373 - hdsl2ShdslPerfLOSWSThresh 374 - hdsl2ShdslPerfUASThresh 375 - hdsl2ShdslSpanInvalidNumRepeaters 376 - hdsl2ShdslLoopbackFailure 377 - hdsl2ShdslpowerBackoff 378 - hdsl2ShdsldeviceFault 379 - hdsl2ShdsldcContinuityFault 380 - hdsl2ShdslconfigInitFailure 381 - hdsl2ShdslprotocolInitFailure 382 - hdsl2ShdslnoNeighborPresent 383 - hdsl2ShdslLocalPowerLoss 385 4.3.1 Line Topology 387 An HDSL2/SHDSL Line consists of a minimum of two units - xtuC (the 388 central termination unit) and an xtuR (the remote termination unit). 389 The line may optionally support up to 8 repeater/regenerator units 390 (xru) as shown in the figure below. 392 <-- Network Side Customer Side --> 394 || 396 <~~~> <~~~> HDSL2/SHDSL Segments <~~~> 398 +-------+ +-------+ +-------+ +-------+ +-------+ 399 + C=1=N C=1=N C=..1..=N C=1=N + 400 | xtuC | | xru1 | | xru2 | | xru8 | | xtuR | 401 + C=2=N C=2=N C=..2..=N C=2=N + 402 +-------+ +-------+ +-------+ +-------+ +-------+ 404 Key: HDSL2/SHDSL Span 405 <~~~~> HDSL2/SHDSL Segment 406 =1= HDSL2/SHDSL wire-pair-1 407 =2= SHDSL optional wire-pair-2 (Not applicable to HDSL2) 408 C Customer Side Segment Endpoint (modem) 409 N Network Side Segment Endpoint (modem) 411 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 413 Figure 2: General topology for an HDSL2/SHDSL Line 415 4.4. Counters, Interval Buckets and Thresholds 417 For SNR Margin, Loop Attenuation, ES, SES, CRC anomalies, LOSW, and 418 UAS, there are event counters, current 15-minute and 0 to 96 419 15-minute history bucket(s) of "interval-counters", as well as 420 current and 0 to 30 previous 1-day interval-counter(s). Each 421 current 15-minute event bucket has an associated threshold 422 notification. 424 Unlike RFC 2493 [22] and RFC 2662 [23], there is no representation 425 in the MIB for invalid buckets. In those cases where the data for 426 an interval is suspect or known to be invalid, the agent MUST NOT 427 report the interval. If the current 15-minute event bucket is 428 determined to be invalid, notifications based upon the value of the 429 event bucket MUST NOT be generated. 431 Not reporting an interval will result in holes in the associated 432 table. For example, the table, hdsl2Shdsl15MinIntervalTable, is 433 indexed by { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide, 434 hdsl2ShdslEndpointWirePair, hdsl2Shdsl15MinIntervalNumber}. If 435 interval 12 is determined to be invalid but intervals 11 and 13 436 are valid, a Get Next operation on the indices .1.1.1.1.11 would 437 return indices .1.1.1.1.13. 439 There is no requirement for an agent to ensure a fixed relationship 440 between the start of a fifteen minute and any wall clock; however 441 some implementations may align the fifteen minute intervals with 442 quarter hours. Likewise, an implementation may choose to align one 443 day intervals with the start of a day. 445 Counters are not reset when an xU is reinitialized, only when the 446 agent is reset or reinitialized (or under specific request outside 447 the scope of this MIB). 449 4.5. Profiles 451 As a managed node can handle a large number of xUs, (e.g., hundreds 452 or perhaps thousands of lines), provisioning every parameter on every 453 xU may become burdensome. Moreover, most lines are provisioned 454 identically with the same set of parameters. To simplify the 455 provisioning process, this MIB makes use of profiles. A profile is a 456 set of parameters that can be shared by multiple lines using the same 457 configuration. 459 The following profiles are used in this MIB: 461 o Span Configuration Profiles - Span configuration profiles contain 462 parameters for configuring HDSL2/SHDSL spans. They are defined 463 in the hdsl2ShdslSpanConfProfileTable. Since span configuration 464 parameters are only applicable for SHDSL, the support for span 466 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 468 configuration profiles is optional for HDSL2 interfaces. 470 Note that the configuration of the span dictates the behavior for 471 each individual segment end point in the span. If a different 472 configuration is provisioned for any given segment end point 473 within the span, however, the new configuration for this segment 474 end point will override the span configuration for this segment 475 end point only. 477 o Segment Endpoint Alarm Configuration Profiles - These profiles 478 contain parameters for configuring alarm thresholds for HDSL2/ 479 SHDSL segment endpoints. These profiles are defined in the 480 hdsl2ShdslEndpointAlarmConfProfileTable. 482 The index value for this profile is a locally-unique 483 administratively assigned name for the profile having the textual 484 convention `SnmpAdminString' (RFC 2571 [1]). 486 One or more lines may be configured to share parameters of a single 487 profile (e.g., hdsl2ShdslEndpointAlarmConfProfile = `silver') by 488 setting its hdsl2ShdslEndpointAlarmConfProfile objects to the value 489 of this profile. If a change is made to the profile, all lines that 490 refer to it will be reconfigured to the changed parameters. Before 491 a profile can be deleted or taken out of service it must be first 492 unreferenced from all associated lines. 494 Implementations MUST provide a default profile whose name is `DEFVAL' 495 for each profile type. The values of the associated parameters will 496 be vendor specific unless otherwise indicated in this document. 497 Before a line's profiles have been set, these profiles will be 498 automatically used by setting hdsl2ShdslEndpointAlarmConfProfile and 499 hdsl2ShdslSpanConfProfile to `DEFVAL' where appropriate. This 500 default profile name, 'DEFVAL', is considered reserved in the context 501 of profiles defined in this MIB. 503 Profiles are created, assigned, and deleted dynamically using the 504 profile name and profile row status in each of the four profile 505 tables. 507 Profile changes MUST take effect immediately. These changes MAY 508 result in a restart (hard reset or soft restart) of the units on the 509 line. 511 4.6. Notifications 513 The ability to generate the SNMP notifications coldStart/WarmStart 514 (per [21]) which are per agent (e.g., per Digital Subscriber Line 515 Access Multiplexer, or DSLAM, in such a device), and linkUp/linkDown 516 (per [21]) which are per interface (i.e., HDSL2/SHDSL line) is 517 required. 519 A linkDown notification MAY be generated whenever any of ES, SES, 520 CRC Anomaly, LOSW, or UAS event occurs. The corresponding linkUp 522 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 524 notification MAY be sent when all link failure conditions are 525 cleared. 527 The notifications defined in this MIB are for initialization failure 528 and for the threshold crossings associated with the following events: 529 ES, SES, CRC Anomaly, LOSW, and UAS. Each threshold has its own 530 enable/threshold value. When that value is 0, the notification is 531 disabled. 533 The hdsl2ShdslEndpointCurrStatus is a bitmask representing all 534 outstanding error conditions associated with a particular Segment 535 Endpoint. Note that since status of remote endpoints is obtained via 536 the EOC, this information may be unavailable for units that are 537 unreachable via EOC during a line error condition. Therefore, not 538 all conditions may always be included in its current status. 539 Notifications corresponding to the bit fields in this object are 540 defined. 542 Two alarm conditions, SNR Margin Alarm and Loop Attenuation Alarm, 543 are organized in a manner slightly different from that implied in 544 the EOC specifications. In the MIB, these alarm conditions are 545 tied to the two thresholds hdsl2ShdslEndpointThreshSNRMargin and 546 hdsl2ShdslEndpointThreshLoopAttenuation found in the 547 hdsl2ShdslEndpointAlarmConfProfileTable. In the EOC, the alarm 548 conditions associated with these thresholds are per-unit. In the 549 MIB, these alarm conditions are per-endpoint. For terminal units, 550 this has no impact. For repeaters, this implies an implementation 551 variance where the agent in the terminal unit is responsible for 552 detecting a threshold crossing. As the reporting of a repeater 553 detected alarm condition to the polling terminal unit occurs in 554 the same EOC message as the reporting of the current SNR Margin 555 and Loop Attenuation values, it is anticipated that this will have 556 very little impact on agent implementation. 558 A threshold notification occurs whenever the corresponding current 559 15-minute interval error counter becomes equal to, or exceeds the 560 threshold value. One notification may be sent per interval per 561 interface. Since the current 15-minute counter are reset to 0 every 562 15 minutes, if the condition persists, the notification may recur as 563 often as every 15 minutes. For example, to get a notification 564 whenever a "loss of" event occurs (but at most once every 15 565 minutes), set the corresponding threshold to 1. The agent will 566 generate a notification when the event originally occurs. 568 Note that the Network Management System, or NMS, may receive a 569 linkDown notification, as well, if enabled (via 570 ifLinkUpDownTrapEnable [21]). At the beginning of the next 15 minute 571 interval, the counter is reset. When the first second goes by and 572 the event occurs, the current interval bucket will be 1, which 573 equals the threshold and the notification will be sent again. 575 A hdsl2ShdslSpanInvalidNumRepeaters notification may be generated 576 following completion of the discovery phase if the number of 578 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 580 repeaters discovered on the line differs from the number of repeaters 581 specified in hdsl2ShdslSpanConfNumRepeaters. For those conditions 582 where the number of provisioned repeaters is greater than those 583 encountered during span discovery, all table entries associated with 584 the nonexistant repeaters are to be discarded. For those conditions 585 where the number of provisioned repeaters is less than those 586 encountered during span discovery, additional table entries are to 587 be created using the default span configuration profile. 589 5. Conformance and Compliance 591 For both HDSL2 and SHDSL lines, the following group(s) are mandatory: 593 hdsl2ShdslSpanConfGroup 594 hdsl2ShdslSpanStatusGroup 595 hdsl2ShdslInventoryGroup 596 hdsl2ShdslEndpointConfGroup 597 hdsl2Shdsl15MinIntervalGroup 598 hdsl2Shdsl1DayIntervalGroup 599 hdsl2ShdslMaintenanceGroup 600 hdsl2ShdslEndpointAlarmConfGroup 601 hdsl2ShdslNotificationGroup 603 For HDSL2 lines, the following group(s) are optional: 605 hdsl2ShdslSpanConfProfileGroup 606 hdsl2ShdslSpanShdslStatusGroup 608 6. Definitions 610 HDSL2-SHDSL-LINE-MIB DEFINITIONS ::= BEGIN 612 IMPORTS 613 MODULE-IDENTITY, 614 OBJECT-TYPE, 615 Counter32, 616 Gauge32, 617 NOTIFICATION-TYPE, 618 Integer32, 619 transmission FROM SNMPv2-SMI 620 RowStatus, 621 TEXTUAL-CONVENTION FROM SNMPv2-TC 622 ifIndex FROM IF-MIB 623 PerfCurrentCount, 624 PerfIntervalCount FROM PerfHist-TC-MIB 625 SnmpAdminString FROM SNMP-FRAMEWORK-MIB 626 MODULE-COMPLIANCE, 627 OBJECT-GROUP, 628 NOTIFICATION-GROUP FROM SNMPv2-CONF; 630 hdsl2ShdslMIB MODULE-IDENTITY 631 LAST-UPDATED "200107190000Z" -- July 19, 2001 632 ORGANIZATION "ADSLMIB Working Group" 634 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 636 CONTACT-INFO "WG-email: XDSLMIB@LISTSERV.ECIRALEIGH.COM 637 Subscribe: LISTSERV@LISTSERV.ECIRALEIGH.COM 638 In Body: subscribe/signoff XDSLMIB 639 Archive: index XDSLMIB/get 641 Chair: Mike Sneed 642 ECI Telecom 643 Postal: 1017 Main Campus Drive 644 Raleigh NC 27606 USA 645 Email: Mike.Sneed@go.ecitele.com 646 Phone: +1 919 513 1435 648 Co-editor: Bob Ray 649 Verilink Corporation 650 Postal: 950 Explorer Blvd 651 Huntsville, AL 35806 USA 652 Email: bray@verilink.com 653 Phone: +1 256 327 2380 655 Co-editor: Rajesh Abbi 656 Alcatel USA 657 Postal: 2912 Wake Forest Road 658 Raleigh, NC 27609-7860 USA 659 Email: Rajesh.Abbi@usa.alcatel.com 660 Phone: +1 919 850 6194 661 " 663 DESCRIPTION 664 "This MIB module defines a collection of objects for managing 665 HDSL2/SHDSL lines. An agent may reside at either end of the 666 line, however the MIB is designed to require no management 667 communication between the modems beyond that inherent in the 668 low-level EOC line protocol as defined in ANSI T1E1.4/2000-006 669 (for HDSL2 lines), or in ITU G.991.2 (for SHDSL lines)." 670 REVISION "200107190000Z" -- July 19, 2001 671 DESCRIPTION "Initial version, published as RFC xxxx." 673 ::= { transmission xxxx } -- to be assigned by IANA 675 hdsl2ShdslMibObjects OBJECT IDENTIFIER ::= { hdsl2ShdslMIB 1 } 677 -- Textual Conventions used in this MIB 678 -- 680 Hdsl2ShdslPerfCurrDayCount ::= TEXTUAL-CONVENTION 681 STATUS current 682 DESCRIPTION 683 "A gauge associated with interface performance measurements in 684 a current 1-day (24 hour) measurement interval. 686 The value of this gauge starts at zero at the beginning of an 687 interval and is increased when associated events occur, until 688 the end of the 1-day interval. At that time the value of the 690 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 692 gauge is stored in the previous 1-day history interval, as 693 defined in a companion object of type 694 Hdsl2Shdsl1DayIntevalCount, and the current interval counter 695 is restarted at zero. 697 In the case where the agent has no valid data available for 698 this interval the corresponding object instance is not 699 available and upon a retrieval request a corresponding error 700 message shall be returned to indicate that this instance does 701 not exist. Please note that zero is a valid value." 702 SYNTAX Gauge32 704 Hdsl2Shdsl1DayIntervalCount ::= TEXTUAL-CONVENTION 705 STATUS current 706 DESCRIPTION 707 "A counter associated with interface performance measurements 708 during the most previous 1-day (24 hour) measurement interval. 709 The value of this counter is equal to the value of the current 710 day counter, as defined in a companion object of type 711 Hdsl2ShdslPerfCurrDayCount, at the end of its most recent 712 interval. 714 In the case where the agent has no valid data available for 715 this interval the corresponding object instance is not 716 available and upon a retrieval request a corresponding error 717 message shall be returned to indicate that this instance does 718 not exist." 719 SYNTAX Gauge32 721 Hdsl2ShdslPerfTimeElapsed ::= TEXTUAL-CONVENTION 722 STATUS current 723 DESCRIPTION 724 "The number of seconds that have elapsed since the beginning of 725 the current measurement period. If, for some reason, such as 726 an adjustment in the system's time-of-day clock or the addition 727 of a leap second, the current interval exceeds the maximum 728 value, the agent will return the maximum value. 730 For 15 minute intervals, the range is limited to (0..899). 731 For 24 hour intervals, the range is limited to (0..86399)." 732 SYNTAX INTEGER(0..86399) 734 Hdsl2ShdslPerfIntervalThreshold ::= TEXTUAL-CONVENTION 735 STATUS current 736 DESCRIPTION 737 "This convention defines a range of values that may be set in 738 a fault threshold alarm control. As the number of seconds in 739 a 15-minute interval numbers at most 900, objects of this type 740 may have a range of 0...900, where the value of 0 disables the 741 alarm." 742 SYNTAX INTEGER(0..900) 744 Hdsl2ShdslUnitId ::= TEXTUAL-CONVENTION 746 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 748 STATUS current 749 DESCRIPTION 750 "This is the unique identification for all units in a 751 HDSL2/SHDSL Span. It is based on the EOC unit addressing 752 scheme with reference to the xtuC." 753 SYNTAX INTEGER 754 { 755 xtuC(1), 756 xtuR(2), 757 xru1(3), 758 xru2(4), 759 xru3(5), 760 xru4(6), 761 xru5(7), 762 xru6(8), 763 xru7(9), 764 xru8(10) 765 } 767 Hdsl2ShdslUnitSide ::= TEXTUAL-CONVENTION 768 STATUS current 769 DESCRIPTION 770 "This is the referenced side of a HDSL2/SHDSL unit - Network 771 or Customer side. The side facing the Network is the Network 772 side, while the side facing the Customer is the Customer side." 773 SYNTAX INTEGER 774 { 775 networkSide(1), 776 customerSide(2) 777 } 779 Hdsl2ShdslWirePair ::= TEXTUAL-CONVENTION 780 STATUS current 781 DESCRIPTION 782 "This is the referenced pair of wires in a HDSL2/SHDSL Segment. 783 HDSL2 only supports a single pair (wirePair1), while SHDSL 784 supports an optional second pair (wirePair2)." 785 SYNTAX INTEGER 786 { 787 wirePair1(1), 788 wirePair2(2) 789 } 791 Hdsl2ShdslTransmissionModeType ::= TEXTUAL-CONVENTION 792 STATUS current 793 DESCRIPTION 794 "Contains the regional setting of the HDSL2/SHDSL span, 795 represented as a bit-map of possible settings. The various 796 bit positions are: 798 Bit Meaning Description 799 1 region 1 Indicates ITU-T G.991.2 Annex A. 800 2 region 2 Indicates ITU-T G.991.2 Annex B." 802 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 804 SYNTAX BITS 805 { 806 region1(0), 807 region2(1) 808 } 810 -- Span Configuration Group 811 -- 813 hdsl2ShdslSpanConfTable OBJECT-TYPE 814 SYNTAX SEQUENCE OF Hdsl2ShdslSpanConfEntry 815 MAX-ACCESS not-accessible 816 STATUS current 817 DESCRIPTION 818 "This table supports overall configuration of HDSL2/SHDSL 819 Spans. Entries in this table MUST be maintained in a 820 persistent manner." 821 ::= { hdsl2ShdslMibObjects 1 } 823 hdsl2ShdslSpanConfEntry OBJECT-TYPE 824 SYNTAX Hdsl2ShdslSpanConfEntry 825 MAX-ACCESS not-accessible 826 STATUS current 827 DESCRIPTION 828 "An entry in the hdsl2ShdslSpanConfTable. Each entry 829 represents the complete Span in a single HDSL2/SHDSL line. 830 It is indexed by the ifIndex of the associated HDSL2/SHDSL 831 line." 832 INDEX { ifIndex } 833 ::= { hdsl2ShdslSpanConfTable 1 } 835 Hdsl2ShdslSpanConfEntry ::= 836 SEQUENCE 837 { 838 hdsl2ShdslSpanConfNumRepeaters INTEGER, 839 hdsl2ShdslSpanConfProfile SnmpAdminString, 840 hdsl2ShdslSpanConfAlarmProfile SnmpAdminString 841 } 843 hdsl2ShdslSpanConfNumRepeaters OBJECT-TYPE 844 SYNTAX INTEGER(0..8) 845 MAX-ACCESS read-write 846 STATUS current 847 DESCRIPTION 848 "This object provisions the number of repeaters/regenerators 849 in this HDSL2/SHDSL Span." 850 ::= { hdsl2ShdslSpanConfEntry 1 } 852 hdsl2ShdslSpanConfProfile OBJECT-TYPE 853 SYNTAX SnmpAdminString (SIZE(1..32)) 854 MAX-ACCESS read-write 855 STATUS current 856 DESCRIPTION 858 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 860 "This object is a pointer to a span configuration profile in 861 the hdsl2ShdslSpanConfProfileTable, which applies to this span. 862 The value of this object is the index of the referenced profile 863 in the hdsl2ShdslSpanConfProfileTable. Note that span 864 configuration profiles are only applicable to SHDSL lines. 865 HDSL2 lines MUST reference the default profile, 'DEFVAL'. 866 By default, this object will have the value 'DEFVAL' (the index 867 of the default profile). 869 Any attempt to set this object to a value that is not the value 870 of the index for an active entry in the profile table, 871 hdsl2ShdslSpanConfProfileTable, MUST be rejected." 872 ::= { hdsl2ShdslSpanConfEntry 2 } 874 hdsl2ShdslSpanConfAlarmProfile OBJECT-TYPE 875 SYNTAX SnmpAdminString (SIZE(1..32)) 876 MAX-ACCESS read-write 877 STATUS current 878 DESCRIPTION 879 "This object is a pointer to an Alarm configuration profile in 880 the hdsl2ShdslEndpointAlarmConfProfileTable. The value of this 881 object is the index of the referenced profile in the 882 hdsl2ShdslEndpointAlarmConfProfileTable. The alarm threshold 883 configuration in the referenced profile will be used by default 884 for all segment endpoints in this span. Individual endpoints 885 may override this profile by explicitly specifying some other 886 profile in the hdsl2ShdslEndpointConfTable. By default, this 887 object will have the value 'DEFVAL' (the index of the default 888 profile). 890 Any attempt to set this object to a value that is not the value 891 of the index for an active entry in the profile table, 892 hdsl2ShdslEndpointAlarmConfProfileTable, MUST be rejected." 893 ::= { hdsl2ShdslSpanConfEntry 3 } 895 -- Span Status Group 896 -- 898 hdsl2ShdslSpanStatusTable OBJECT-TYPE 899 SYNTAX SEQUENCE OF Hdsl2ShdslSpanStatusEntry 900 MAX-ACCESS not-accessible 901 STATUS current 902 DESCRIPTION 903 "This table provides overall status information of 904 HDSL2/SHDSL spans. This table contains live data from 905 equipment. As such, it is NOT persistent." 906 ::= { hdsl2ShdslMibObjects 2 } 908 hdsl2ShdslSpanStatusEntry OBJECT-TYPE 909 SYNTAX Hdsl2ShdslSpanStatusEntry 910 MAX-ACCESS not-accessible 911 STATUS current 912 DESCRIPTION 914 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 916 "An entry in the hdsl2ShdslSpanStatusTable. Each entry 917 represents the complete span in a single HDSL2/SHDSL line. 918 It is indexed by the ifIndex of the associated HDSL2/SHDSL 919 line." 920 INDEX { ifIndex } 921 ::= { hdsl2ShdslSpanStatusTable 1 } 923 Hdsl2ShdslSpanStatusEntry ::= 924 SEQUENCE 925 { 926 hdsl2ShdslStatusNumAvailRepeaters INTEGER, 927 hdsl2ShdslStatusMaxAttainableLineRate INTEGER, 928 hdsl2ShdslStatusActualLineRate INTEGER, 929 hdsl2ShdslStatusTransmissionModeCurrent 930 Hdsl2ShdslTransmissionModeType 931 } 933 hdsl2ShdslStatusNumAvailRepeaters OBJECT-TYPE 934 SYNTAX INTEGER(0..8) 935 MAX-ACCESS read-only 936 STATUS current 937 DESCRIPTION 938 "Contains the actual number of repeaters/regenerators 939 discovered in this HDSL2/SHDSL span." 940 ::= { hdsl2ShdslSpanStatusEntry 1 } 942 hdsl2ShdslStatusMaxAttainableLineRate OBJECT-TYPE 943 SYNTAX INTEGER(0..4112000) 944 UNITS "bps" 945 MAX-ACCESS read-only 946 STATUS current 947 DESCRIPTION 948 "Contains the maximum attainable line rate in this HDSL2/SHDSL 949 span." 950 ::= { hdsl2ShdslSpanStatusEntry 2 } 952 hdsl2ShdslStatusActualLineRate OBJECT-TYPE 953 SYNTAX INTEGER(0..4112000) 954 UNITS "bps" 955 MAX-ACCESS read-only 956 STATUS current 957 DESCRIPTION 958 "Contains the actual line rate in this HDSL2/SHDSL span. This 959 should equal ifSpeed." 960 ::= { hdsl2ShdslSpanStatusEntry 3 } 962 hdsl2ShdslStatusTransmissionModeCurrent OBJECT-TYPE 963 SYNTAX Hdsl2ShdslTransmissionModeType 964 MAX-ACCESS read-only 965 STATUS current 966 DESCRIPTION 967 "Contains the current Power Spectral Density (PSD) regional 968 setting of the HDSL2/SHDSL span." 970 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 972 ::= { hdsl2ShdslSpanStatusEntry 4 } 974 -- Unit Inventory Group 975 -- 977 hdsl2ShdslInventoryTable OBJECT-TYPE 978 SYNTAX SEQUENCE OF Hdsl2ShdslInventoryEntry 979 MAX-ACCESS not-accessible 980 STATUS current 981 DESCRIPTION 982 "This table supports retrieval of unit inventory information 983 available via the EOC from units in a HDSL2/SHDSL line. 985 Entries in this table are dynamically created during the 986 line discovery process. The life cycle for these entries 987 is as follows: 989 - xtu discovers a device, either a far-end xtu or an xru 990 - an inventory table entry is created for the device 991 - the line goes down for whatever reason 992 - inventory table entries for unreachable devices are 993 destroyed. 995 As these entries are created/destroyed dynamically, they 996 are NOT persistent." 997 ::= { hdsl2ShdslMibObjects 3 } 999 hdsl2ShdslInventoryEntry OBJECT-TYPE 1000 SYNTAX Hdsl2ShdslInventoryEntry 1001 MAX-ACCESS not-accessible 1002 STATUS current 1003 DESCRIPTION 1004 "An entry in the hdsl2ShdslInventoryTable. Each entry 1005 represents inventory information for a single unit in a 1006 HDSL2/SHDSL line. It is indexed by the ifIndex of the 1007 HDSL2/SHDSL line and the Hdsl2ShdslUnitId of the 1008 associated unit." 1009 INDEX { ifIndex, hdsl2ShdslInvIndex } 1010 ::= { hdsl2ShdslInventoryTable 1 } 1012 Hdsl2ShdslInventoryEntry ::= 1013 SEQUENCE 1014 { 1015 hdsl2ShdslInvIndex Hdsl2ShdslUnitId, 1016 hdsl2ShdslInvVendorID OCTET STRING, 1017 hdsl2ShdslInvVendorModelNumber OCTET STRING, 1018 hdsl2ShdslInvVendorSerialNumber OCTET STRING, 1019 hdsl2ShdslInvVendorEOCSoftwareVersion Integer32, 1020 hdsl2ShdslInvStandardVersion Integer32, 1021 hdsl2ShdslInvVendorListNumber OCTET STRING, 1022 hdsl2ShdslInvVendorIssueNumber OCTET STRING, 1023 hdsl2ShdslInvVendorSoftwareVersion OCTET STRING, 1024 hdsl2ShdslInvEquipmentCode OCTET STRING, 1026 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 1028 hdsl2ShdslInvVendorOther OCTET STRING, 1029 hdsl2ShdslInvTransmissionModeCapability 1030 Hdsl2ShdslTransmissionModeType 1031 } 1033 hdsl2ShdslInvIndex OBJECT-TYPE 1034 SYNTAX Hdsl2ShdslUnitId 1035 MAX-ACCESS read-only 1036 STATUS current 1037 DESCRIPTION 1038 "Each entry in this table corresponds to a physical element 1039 in a HDSL2/SHDSL Span. It is based on the EOC unit addressing 1040 scheme with reference to the xtuC." 1041 ::= { hdsl2ShdslInventoryEntry 1 } 1043 hdsl2ShdslInvVendorID OBJECT-TYPE 1044 SYNTAX OCTET STRING(SIZE(8)) 1045 MAX-ACCESS read-only 1046 STATUS current 1047 DESCRIPTION 1048 "Vendor ID as reported in an Inventory Response message." 1049 ::= { hdsl2ShdslInventoryEntry 2 } 1051 hdsl2ShdslInvVendorModelNumber OBJECT-TYPE 1052 SYNTAX OCTET STRING(SIZE(12)) 1053 MAX-ACCESS read-only 1054 STATUS current 1055 DESCRIPTION 1056 "Vendor model number as reported in an Inventory Response 1057 message." 1058 ::= { hdsl2ShdslInventoryEntry 3 } 1060 hdsl2ShdslInvVendorSerialNumber OBJECT-TYPE 1061 SYNTAX OCTET STRING(SIZE(12)) 1062 MAX-ACCESS read-only 1063 STATUS current 1064 DESCRIPTION 1065 "Vendor serial number as reported in an Inventory Response 1066 message." 1067 ::= { hdsl2ShdslInventoryEntry 4 } 1069 hdsl2ShdslInvVendorEOCSoftwareVersion OBJECT-TYPE 1070 SYNTAX Integer32 1071 MAX-ACCESS read-only 1072 STATUS current 1073 DESCRIPTION 1074 "Vendor EOC version as reported in a Discovery Response 1075 message." 1076 ::= { hdsl2ShdslInventoryEntry 5 } 1078 hdsl2ShdslInvStandardVersion OBJECT-TYPE 1079 SYNTAX Integer32 1080 MAX-ACCESS read-only 1082 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 1084 STATUS current 1085 DESCRIPTION 1086 "Version of the HDSL2/SHDSL standard implemented, as reported 1087 in an Inventory Response message." 1088 ::= { hdsl2ShdslInventoryEntry 6 } 1090 hdsl2ShdslInvVendorListNumber OBJECT-TYPE 1091 SYNTAX OCTET STRING(SIZE(3)) 1092 MAX-ACCESS read-only 1093 STATUS current 1094 DESCRIPTION 1095 "Vendor list number as reported in an Inventory Response 1096 message." 1097 ::= { hdsl2ShdslInventoryEntry 7 } 1099 hdsl2ShdslInvVendorIssueNumber OBJECT-TYPE 1100 SYNTAX OCTET STRING(SIZE(2)) 1101 MAX-ACCESS read-only 1102 STATUS current 1103 DESCRIPTION 1104 "Vendor issue number as reported in an Inventory Response 1105 message." 1106 ::= { hdsl2ShdslInventoryEntry 8 } 1108 hdsl2ShdslInvVendorSoftwareVersion OBJECT-TYPE 1109 SYNTAX OCTET STRING(SIZE(6)) 1110 MAX-ACCESS read-only 1111 STATUS current 1112 DESCRIPTION 1113 "Vendor software version as reported in an Inventory Response 1114 message." 1115 ::= { hdsl2ShdslInventoryEntry 9 } 1117 hdsl2ShdslInvEquipmentCode OBJECT-TYPE 1118 SYNTAX OCTET STRING(SIZE(10)) 1119 MAX-ACCESS read-only 1120 STATUS current 1121 DESCRIPTION 1122 "Equipment code conforming to ANSI T1.213, Coded Identification 1123 of Equipment Entities." 1124 ::= { hdsl2ShdslInventoryEntry 10 } 1126 hdsl2ShdslInvVendorOther OBJECT-TYPE 1127 SYNTAX OCTET STRING(SIZE(12)) 1128 MAX-ACCESS read-only 1129 STATUS current 1130 DESCRIPTION 1131 "Other vendor information as reported in an Inventory Response 1132 message." 1133 ::= { hdsl2ShdslInventoryEntry 11 } 1135 hdsl2ShdslInvTransmissionModeCapability OBJECT-TYPE 1136 SYNTAX Hdsl2ShdslTransmissionModeType 1138 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 1140 MAX-ACCESS read-only 1141 STATUS current 1142 DESCRIPTION 1143 "Contains the transmission mode capability of the SHDSL unit." 1144 ::= { hdsl2ShdslInventoryEntry 12 } 1146 -- Segment Endpoint Configuration Group 1147 -- 1149 hdsl2ShdslEndpointConfTable OBJECT-TYPE 1150 SYNTAX SEQUENCE OF Hdsl2ShdslEndpointConfEntry 1151 MAX-ACCESS not-accessible 1152 STATUS current 1153 DESCRIPTION 1154 "This table supports configuration parameters for segment 1155 endpoints in a HDSL2/SHDSL line. As this table is indexed 1156 by ifIndex, it MUST be maintained in a persistent manner." 1157 ::= { hdsl2ShdslMibObjects 4 } 1159 hdsl2ShdslEndpointConfEntry OBJECT-TYPE 1160 SYNTAX Hdsl2ShdslEndpointConfEntry 1161 MAX-ACCESS not-accessible 1162 STATUS current 1163 DESCRIPTION 1164 "An entry in the hdsl2ShdslEndpointConfTable. Each entry 1165 represents a single segment endpoint in a HDSL2/SHDSL line. 1166 It is indexed by the ifIndex of the HDSL2/SHDSL line, the 1167 UnitId of the associated unit, the side of the unit, and the 1168 wire-pair of the associated modem." 1169 INDEX { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide, 1170 hdsl2ShdslEndpointWirePair} 1171 ::= { hdsl2ShdslEndpointConfTable 1 } 1173 Hdsl2ShdslEndpointConfEntry ::= 1174 SEQUENCE 1175 { 1176 hdsl2ShdslEndpointSide Hdsl2ShdslUnitSide, 1177 hdsl2ShdslEndpointWirePair Hdsl2ShdslWirePair, 1178 hdsl2ShdslEndpointAlarmConfProfile SnmpAdminString 1179 } 1181 hdsl2ShdslEndpointSide OBJECT-TYPE 1182 SYNTAX Hdsl2ShdslUnitSide 1183 MAX-ACCESS read-only 1184 STATUS current 1185 DESCRIPTION 1186 "The side of the unit associated with this segment endpoint - 1187 Network/Customer side - as per the Hdsl2ShdslUnitSide textual 1188 convention." 1189 ::= { hdsl2ShdslEndpointConfEntry 1 } 1191 hdsl2ShdslEndpointWirePair OBJECT-TYPE 1192 SYNTAX Hdsl2ShdslWirePair 1194 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 1196 MAX-ACCESS read-only 1197 STATUS current 1198 DESCRIPTION 1199 "The wire-pair of the modem associated with this segment 1200 endpoint as per the Hdsl2ShdslWirePair textual convention." 1201 ::= { hdsl2ShdslEndpointConfEntry 2 } 1203 hdsl2ShdslEndpointAlarmConfProfile OBJECT-TYPE 1204 SYNTAX SnmpAdminString (SIZE(0..32)) 1205 MAX-ACCESS read-write 1206 STATUS current 1207 DESCRIPTION 1208 "This object configures the alarm threshold values to be used 1209 for this segment endpoint. The values are obtained from the 1210 alarm configuration profile referenced by this object. The 1211 value of this object is the index of the referenced profile in 1212 the hdsl2ShdslEndpointAlarmConfProfileTable, or NULL (a zero- 1213 length SnmpAdminString). If the value is a zero-length 1214 SnmpAdminString, the endpoint uses the default Alarm 1215 Configuration Profile for the associated span as per the 1216 hdsl2ShdslSpanConfAlarmProfile object in the 1217 hdsl2ShdslSpanConfTable. The default value of this object is 1218 a zero-length SnmpAdminString. 1220 Any attempt to set this object to a value that is not the value 1221 of the index for an active entry in the profile table, 1222 hdsl2ShdslEndpointAlarmConfProfileTable, MUST be rejected." 1223 ::= { hdsl2ShdslEndpointConfEntry 3 } 1225 -- Segment Endpoint Current Status/Performance Group 1226 -- 1228 hdsl2ShdslEndpointCurrTable OBJECT-TYPE 1229 SYNTAX SEQUENCE OF Hdsl2ShdslEndpointCurrEntry 1230 MAX-ACCESS not-accessible 1231 STATUS current 1232 DESCRIPTION 1233 "This table contains current status and performance information 1234 for segment endpoints in HDSL2/SHDSL Lines. As with other 1235 tables in this MIB indexed by ifIndex, entries in this table 1236 MUST be maintained in a persistent manner." 1237 ::= { hdsl2ShdslMibObjects 5 } 1239 hdsl2ShdslEndpointCurrEntry OBJECT-TYPE 1240 SYNTAX Hdsl2ShdslEndpointCurrEntry 1241 MAX-ACCESS not-accessible 1242 STATUS current 1243 DESCRIPTION 1244 "An entry in the hdsl2ShdslEndpointCurrTable. Each entry 1245 contains status and performance information relating to a 1246 single segment endpoint. It is indexed by the ifIndex of the 1247 HDSL2/SHDSL line, the UnitId of the associated unit, the side 1248 of the unit, and the wire-pair of the associated modem." 1250 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 1252 INDEX { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide, 1253 hdsl2ShdslEndpointWirePair } 1254 ::= { hdsl2ShdslEndpointCurrTable 1 } 1256 Hdsl2ShdslEndpointCurrEntry ::= 1257 SEQUENCE 1258 { 1259 hdsl2ShdslEndpointCurrAtn INTEGER, 1260 hdsl2ShdslEndpointCurrSnrMgn INTEGER, 1261 hdsl2ShdslEndpointCurrStatus BITS, 1262 hdsl2ShdslEndpointES Counter32, 1263 hdsl2ShdslEndpointSES Counter32, 1264 hdsl2ShdslEndpointCRCanomalies Counter32, 1265 hdsl2ShdslEndpointLOSWS Counter32, 1266 hdsl2ShdslEndpointUAS Counter32, 1267 hdsl2ShdslEndpointCurr15MinTimeElapsed 1268 Hdsl2ShdslPerfTimeElapsed, 1269 hdsl2ShdslEndpointCurr15MinES PerfCurrentCount, 1270 hdsl2ShdslEndpointCurr15MinSES PerfCurrentCount, 1271 hdsl2ShdslEndpointCurr15MinCRCanomalies PerfCurrentCount, 1272 hdsl2ShdslEndpointCurr15MinLOSWS PerfCurrentCount, 1273 hdsl2ShdslEndpointCurr15MinUAS PerfCurrentCount, 1274 hdsl2ShdslEndpointCurr1DayTimeElapsed 1275 Hdsl2ShdslPerfTimeElapsed, 1276 hdsl2ShdslEndpointCurr1DayES 1277 Hdsl2ShdslPerfCurrDayCount, 1278 hdsl2ShdslEndpointCurr1DaySES 1279 Hdsl2ShdslPerfCurrDayCount, 1280 hdsl2ShdslEndpointCurr1DayCRCanomalies 1281 Hdsl2ShdslPerfCurrDayCount, 1282 hdsl2ShdslEndpointCurr1DayLOSWS 1283 Hdsl2ShdslPerfCurrDayCount, 1284 hdsl2ShdslEndpointCurr1DayUAS 1285 Hdsl2ShdslPerfCurrDayCount 1286 } 1288 hdsl2ShdslEndpointCurrAtn OBJECT-TYPE 1289 SYNTAX INTEGER(-127..128) 1290 UNITS "dB" 1291 MAX-ACCESS read-only 1292 STATUS current 1293 DESCRIPTION 1294 "The current loop attenuation for this endpoint as reported in 1295 a Network or Customer Side Performance Status message." 1296 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1297 ::= { hdsl2ShdslEndpointCurrEntry 1 } 1299 hdsl2ShdslEndpointCurrSnrMgn OBJECT-TYPE 1300 SYNTAX INTEGER(-127..128) 1301 UNITS "dB" 1302 MAX-ACCESS read-only 1303 STATUS current 1304 DESCRIPTION 1306 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 1308 "The current SNR margin for this endpoint as reported in a 1309 Status Response/SNR message." 1310 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1311 ::= { hdsl2ShdslEndpointCurrEntry 2 } 1313 hdsl2ShdslEndpointCurrStatus OBJECT-TYPE 1314 SYNTAX BITS 1315 { 1316 noDefect(0), 1317 powerBackoff(1), 1318 deviceFault(2), 1319 dcContinuityFault(3), 1320 snrMarginAlarm(4), 1321 loopAttenuationAlarm(5), 1322 loswFailureAlarm(6), 1323 configInitFailure(7), 1324 protocolInitFailure(8), 1325 noNeighborPresent(9), 1326 loopbackActive(10) 1327 } 1328 MAX-ACCESS read-only 1329 STATUS current 1330 DESCRIPTION 1331 "Contains the current state of the endpoint. This is a 1332 bitmap of possible conditions. The various bit positions 1333 are: 1335 noDefect There no defects on the line. 1337 powerBackoff Indicates enhanced Power Backoff. 1339 deviceFault Indicates a vendor-dependent 1340 diagnostic or self-test fault 1341 has been detected. 1343 dcContinuityFault Indicates vendor-dependent 1344 conditions that interfere with 1345 span powering such as short and 1346 open circuits. 1348 snrMarginAlarm Indicates that the SNR margin 1349 has dropped below the alarm threshold. 1351 loopAttenuationAlarm Indicates that the loop attenuation 1352 has dropped below the alarm threshold. 1354 loswFailureAlarm Indicates a forward LOSW alarm. 1356 configInitFailure Endpoint failure during initialization 1357 due to paired endpoint not able to 1358 support requested configuration. 1360 protocolInitFailure Endpoint failure during initialization 1362 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 1364 due to incompatible protocol used by 1365 the paired endpoint. 1367 noNeighborPresent Endpoint failure during initialization 1368 due to no activation sequence detected 1369 from paired endpoint. 1371 loopbackActive A loopback is currently active at this 1372 Segment Endpoint. 1374 This is intended to supplement ifOperStatus. Note that there 1375 is a 1-1 relationship between the status bits defined in this 1376 object and the notification thresholds defined elsewhere in 1377 this MIB." 1378 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1379 ::= { hdsl2ShdslEndpointCurrEntry 3 } 1381 hdsl2ShdslEndpointES OBJECT-TYPE 1382 SYNTAX Counter32 1383 UNITS "seconds" 1384 MAX-ACCESS read-only 1385 STATUS current 1386 DESCRIPTION 1387 "Count of Errored Seconds (ES) on this endpoint since the xU 1388 was last restarted." 1389 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1390 ::= { hdsl2ShdslEndpointCurrEntry 4 } 1392 hdsl2ShdslEndpointSES OBJECT-TYPE 1393 SYNTAX Counter32 1394 UNITS "seconds" 1395 MAX-ACCESS read-only 1396 STATUS current 1397 DESCRIPTION 1398 "Count of Severely Errored Seconds (SES) on this endpoint 1399 since the xU was last restarted." 1400 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1401 ::= { hdsl2ShdslEndpointCurrEntry 5 } 1403 hdsl2ShdslEndpointCRCanomalies OBJECT-TYPE 1404 SYNTAX Counter32 1405 UNITS "detected CRC Anomalies" 1406 MAX-ACCESS read-only 1407 STATUS current 1408 DESCRIPTION 1409 "Count of CRC anomalies on this endpoint since the xU was 1410 last restarted." 1411 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1412 ::= { hdsl2ShdslEndpointCurrEntry 6 } 1414 hdsl2ShdslEndpointLOSWS OBJECT-TYPE 1415 SYNTAX Counter32 1416 UNITS "seconds" 1418 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 1420 MAX-ACCESS read-only 1421 STATUS current 1422 DESCRIPTION 1423 "Count of Loss of Sync Word (LOSW) Seconds on this endpoint 1424 since the xU was last restarted." 1425 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1426 ::= { hdsl2ShdslEndpointCurrEntry 7 } 1428 hdsl2ShdslEndpointUAS OBJECT-TYPE 1429 SYNTAX Counter32 1430 UNITS "seconds" 1431 MAX-ACCESS read-only 1432 STATUS current 1433 DESCRIPTION 1434 "Count of Unavailable Seconds (UAS) on this endpoint since 1435 the xU was last restarted." 1436 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1437 ::= { hdsl2ShdslEndpointCurrEntry 8 } 1439 hdsl2ShdslEndpointCurr15MinTimeElapsed OBJECT-TYPE 1440 SYNTAX Hdsl2ShdslPerfTimeElapsed 1441 UNITS "seconds" 1442 MAX-ACCESS read-only 1443 STATUS current 1444 DESCRIPTION 1445 "Total elapsed seconds in the current 15-minute interval." 1446 ::= { hdsl2ShdslEndpointCurrEntry 9 } 1448 hdsl2ShdslEndpointCurr15MinES OBJECT-TYPE 1449 SYNTAX PerfCurrentCount 1450 UNITS "seconds" 1451 MAX-ACCESS read-only 1452 STATUS current 1453 DESCRIPTION 1454 "Count of Errored Seconds (ES) in the current 15-minute 1455 interval." 1456 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1457 ::= { hdsl2ShdslEndpointCurrEntry 10 } 1459 hdsl2ShdslEndpointCurr15MinSES OBJECT-TYPE 1460 SYNTAX PerfCurrentCount 1461 UNITS "seconds" 1462 MAX-ACCESS read-only 1463 STATUS current 1464 DESCRIPTION 1465 "Count of Severely Errored Seconds (SES) in the current 1466 15-minute interval." 1467 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1468 ::= { hdsl2ShdslEndpointCurrEntry 11 } 1470 hdsl2ShdslEndpointCurr15MinCRCanomalies OBJECT-TYPE 1471 SYNTAX PerfCurrentCount 1472 UNITS "detected CRC Anomalies" 1474 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 1476 MAX-ACCESS read-only 1477 STATUS current 1478 DESCRIPTION 1479 "Count of CRC anomalies in the current 15-minute interval." 1480 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1481 ::= { hdsl2ShdslEndpointCurrEntry 12 } 1483 hdsl2ShdslEndpointCurr15MinLOSWS OBJECT-TYPE 1484 SYNTAX PerfCurrentCount 1485 UNITS "seconds" 1486 MAX-ACCESS read-only 1487 STATUS current 1488 DESCRIPTION 1489 "Count of Loss of Sync Word (LOSW) Seconds in the current 1490 15-minute interval." 1491 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1492 ::= { hdsl2ShdslEndpointCurrEntry 13 } 1494 hdsl2ShdslEndpointCurr15MinUAS OBJECT-TYPE 1495 SYNTAX PerfCurrentCount 1496 UNITS "seconds" 1497 MAX-ACCESS read-only 1498 STATUS current 1499 DESCRIPTION 1500 "Count of Unavailable Seconds (UAS) in the current 15-minute 1501 interval." 1502 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1503 ::= { hdsl2ShdslEndpointCurrEntry 14 } 1505 hdsl2ShdslEndpointCurr1DayTimeElapsed OBJECT-TYPE 1506 SYNTAX Hdsl2ShdslPerfTimeElapsed 1507 UNITS "seconds" 1508 MAX-ACCESS read-only 1509 STATUS current 1510 DESCRIPTION 1511 "Number of seconds that have elapsed since the beginning of 1512 the current 1-day interval." 1513 ::= { hdsl2ShdslEndpointCurrEntry 15 } 1515 hdsl2ShdslEndpointCurr1DayES OBJECT-TYPE 1516 SYNTAX Hdsl2ShdslPerfCurrDayCount 1517 UNITS "seconds" 1518 MAX-ACCESS read-only 1519 STATUS current 1520 DESCRIPTION 1521 "Count of Errored Seconds (ES) during the current day as 1522 measured by hdsl2ShdslEndpointCurr1DayTimeElapsed." 1523 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1524 ::= { hdsl2ShdslEndpointCurrEntry 16 } 1526 hdsl2ShdslEndpointCurr1DaySES OBJECT-TYPE 1527 SYNTAX Hdsl2ShdslPerfCurrDayCount 1528 UNITS "seconds" 1530 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 1532 MAX-ACCESS read-only 1533 STATUS current 1534 DESCRIPTION 1535 "Count of Severely Errored Seconds (SES) during the current 1536 day as measured by hdsl2ShdslEndpointCurr1DayTimeElapsed." 1537 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1538 ::= { hdsl2ShdslEndpointCurrEntry 17 } 1540 hdsl2ShdslEndpointCurr1DayCRCanomalies OBJECT-TYPE 1541 SYNTAX Hdsl2ShdslPerfCurrDayCount 1542 UNITS "detected CRC Anomalies" 1543 MAX-ACCESS read-only 1544 STATUS current 1545 DESCRIPTION 1546 "Count of CRC anomalies during the current day as measured 1547 by hdsl2ShdslEndpointCurr1DayTimeElapsed." 1548 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1549 ::= { hdsl2ShdslEndpointCurrEntry 18 } 1551 hdsl2ShdslEndpointCurr1DayLOSWS OBJECT-TYPE 1552 SYNTAX Hdsl2ShdslPerfCurrDayCount 1553 UNITS "seconds" 1554 MAX-ACCESS read-only 1555 STATUS current 1556 DESCRIPTION 1557 "Count of Loss of Sync Word (LOSW) Seconds during the current 1558 day as measured by hdsl2ShdslEndpointCurr1DayTimeElapsed." 1559 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1560 ::= { hdsl2ShdslEndpointCurrEntry 19 } 1562 hdsl2ShdslEndpointCurr1DayUAS OBJECT-TYPE 1563 SYNTAX Hdsl2ShdslPerfCurrDayCount 1564 UNITS "seconds" 1565 MAX-ACCESS read-only 1566 STATUS current 1567 DESCRIPTION 1568 "Count of Unavailable Seconds (UAS) during the current day as 1569 measured by hdsl2ShdslEndpointCurr1DayTimeElapsed." 1570 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1571 ::= { hdsl2ShdslEndpointCurrEntry 20 } 1573 -- Segment Endpoint 15-Minute Interval Status/Performance Group 1574 -- 1576 hdsl2Shdsl15MinIntervalTable OBJECT-TYPE 1577 SYNTAX SEQUENCE OF Hdsl2Shdsl15MinIntervalEntry 1578 MAX-ACCESS not-accessible 1579 STATUS current 1580 DESCRIPTION 1581 "This table provides one row for each HDSL2/SHDSL endpoint 1582 performance data collection interval. This table contains 1583 live data from equipment. As such, it is NOT persistent." 1584 ::= { hdsl2ShdslMibObjects 6 } 1586 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 1588 hdsl2Shdsl15MinIntervalEntry OBJECT-TYPE 1589 SYNTAX Hdsl2Shdsl15MinIntervalEntry 1590 MAX-ACCESS not-accessible 1591 STATUS current 1592 DESCRIPTION 1593 "An entry in the hdsl2Shdsl15MinIntervalTable." 1594 INDEX { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide, 1595 hdsl2ShdslEndpointWirePair, hdsl2Shdsl15MinIntervalNumber} 1596 ::= { hdsl2Shdsl15MinIntervalTable 1 } 1598 Hdsl2Shdsl15MinIntervalEntry ::= 1599 SEQUENCE 1600 { 1601 hdsl2Shdsl15MinIntervalNumber INTEGER, 1602 hdsl2Shdsl15MinIntervalES PerfIntervalCount, 1603 hdsl2Shdsl15MinIntervalSES PerfIntervalCount, 1604 hdsl2Shdsl15MinIntervalCRCanomalies PerfIntervalCount, 1605 hdsl2Shdsl15MinIntervalLOSWS PerfIntervalCount, 1606 hdsl2Shdsl15MinIntervalUAS PerfIntervalCount 1607 } 1609 hdsl2Shdsl15MinIntervalNumber OBJECT-TYPE 1610 SYNTAX INTEGER(1..96) 1611 MAX-ACCESS not-accessible 1612 STATUS current 1613 DESCRIPTION 1614 "Performance Data Interval number. 1 is the the most recent 1615 previous interval; interval 96 is 24 hours ago. Intervals 1616 2..96 are optional." 1617 ::= { hdsl2Shdsl15MinIntervalEntry 1 } 1619 hdsl2Shdsl15MinIntervalES OBJECT-TYPE 1620 SYNTAX PerfIntervalCount 1621 UNITS "seconds" 1622 MAX-ACCESS read-only 1623 STATUS current 1624 DESCRIPTION 1625 "Count of Errored Seconds (ES) during the interval." 1626 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1627 ::= { hdsl2Shdsl15MinIntervalEntry 2 } 1629 hdsl2Shdsl15MinIntervalSES OBJECT-TYPE 1630 SYNTAX PerfIntervalCount 1631 UNITS "seconds" 1632 MAX-ACCESS read-only 1633 STATUS current 1634 DESCRIPTION 1635 "Count of Severely Errored Seconds (SES) during the interval." 1636 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1637 ::= { hdsl2Shdsl15MinIntervalEntry 3 } 1639 hdsl2Shdsl15MinIntervalCRCanomalies OBJECT-TYPE 1641 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 1643 SYNTAX PerfIntervalCount 1644 UNITS "detected CRC Anomalies" 1645 MAX-ACCESS read-only 1646 STATUS current 1647 DESCRIPTION 1648 "Count of CRC anomalies during the interval." 1649 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1650 ::= { hdsl2Shdsl15MinIntervalEntry 4 } 1652 hdsl2Shdsl15MinIntervalLOSWS OBJECT-TYPE 1653 SYNTAX PerfIntervalCount 1654 UNITS "seconds" 1655 MAX-ACCESS read-only 1656 STATUS current 1657 DESCRIPTION 1658 "Count of Loss of Sync Word (LOSW) Seconds during the 1659 interval." 1660 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1661 ::= { hdsl2Shdsl15MinIntervalEntry 5 } 1663 hdsl2Shdsl15MinIntervalUAS OBJECT-TYPE 1664 SYNTAX PerfIntervalCount 1665 UNITS "seconds" 1666 MAX-ACCESS read-only 1667 STATUS current 1668 DESCRIPTION 1669 "Count of Unavailable Seconds (UAS) during the interval." 1670 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1671 ::= { hdsl2Shdsl15MinIntervalEntry 6 } 1673 -- Segment Endpoint 1-Day Interval Status/Performance Group 1674 -- 1676 hdsl2Shdsl1DayIntervalTable OBJECT-TYPE 1677 SYNTAX SEQUENCE OF Hdsl2Shdsl1DayIntervalEntry 1678 MAX-ACCESS not-accessible 1679 STATUS current 1680 DESCRIPTION 1681 "This table provides one row for each HDSL2/SHDSL endpoint 1682 performance data collection interval. This table contains 1683 live data from equipment. As such, it is NOT persistent." 1684 ::= { hdsl2ShdslMibObjects 7 } 1686 hdsl2Shdsl1DayIntervalEntry OBJECT-TYPE 1687 SYNTAX Hdsl2Shdsl1DayIntervalEntry 1688 MAX-ACCESS not-accessible 1689 STATUS current 1690 DESCRIPTION 1691 "An entry in the hdsl2Shdsl1DayIntervalTable." 1692 INDEX { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide, 1693 hdsl2ShdslEndpointWirePair, hdsl2Shdsl1DayIntervalNumber } 1694 ::= { hdsl2Shdsl1DayIntervalTable 1 } 1696 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 1698 Hdsl2Shdsl1DayIntervalEntry ::= 1699 SEQUENCE 1700 { 1701 hdsl2Shdsl1DayIntervalNumber INTEGER, 1702 hdsl2Shdsl1DayIntervalMoniSecs Hdsl2ShdslPerfTimeElapsed, 1703 hdsl2Shdsl1DayIntervalES Hdsl2Shdsl1DayIntervalCount, 1704 hdsl2Shdsl1DayIntervalSES Hdsl2Shdsl1DayIntervalCount, 1705 hdsl2Shdsl1DayIntervalCRCanomalies Hdsl2Shdsl1DayIntervalCount, 1706 hdsl2Shdsl1DayIntervalLOSWS Hdsl2Shdsl1DayIntervalCount, 1707 hdsl2Shdsl1DayIntervalUAS Hdsl2Shdsl1DayIntervalCount 1708 } 1710 hdsl2Shdsl1DayIntervalNumber OBJECT-TYPE 1711 SYNTAX INTEGER(1..30) 1712 MAX-ACCESS not-accessible 1713 STATUS current 1714 DESCRIPTION 1715 "History Data Interval number. Interval 1 is the the most 1716 recent previous day; interval 30 is 30 days ago. Intervals 1717 2..30 are optional." 1718 ::= { hdsl2Shdsl1DayIntervalEntry 1 } 1720 hdsl2Shdsl1DayIntervalMoniSecs OBJECT-TYPE 1721 SYNTAX Hdsl2ShdslPerfTimeElapsed 1722 UNITS "seconds" 1723 MAX-ACCESS read-only 1724 STATUS current 1725 DESCRIPTION 1726 "The amount of time in the 1-day interval over which the 1727 performance monitoring information is actually counted. 1728 This value will be the same as the interval duration except 1729 in a situation where performance monitoring data could not 1730 be collected for any reason." 1731 ::= { hdsl2Shdsl1DayIntervalEntry 2 } 1733 hdsl2Shdsl1DayIntervalES OBJECT-TYPE 1734 SYNTAX Hdsl2Shdsl1DayIntervalCount 1735 UNITS "seconds" 1736 MAX-ACCESS read-only 1737 STATUS current 1738 DESCRIPTION 1739 "Count of Errored Seconds (ES) during the 1-day interval as 1740 measured by hdsl2Shdsl1DayIntervalMoniSecs." 1741 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1742 ::= { hdsl2Shdsl1DayIntervalEntry 3 } 1744 hdsl2Shdsl1DayIntervalSES OBJECT-TYPE 1745 SYNTAX Hdsl2Shdsl1DayIntervalCount 1746 UNITS "seconds" 1747 MAX-ACCESS read-only 1748 STATUS current 1749 DESCRIPTION 1750 "Count of Severely Errored Seconds (SES) during the 1-day 1752 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 1754 interval as measured by hdsl2Shdsl1DayIntervalMoniSecs." 1755 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1756 ::= { hdsl2Shdsl1DayIntervalEntry 4 } 1758 hdsl2Shdsl1DayIntervalCRCanomalies OBJECT-TYPE 1759 SYNTAX Hdsl2Shdsl1DayIntervalCount 1760 UNITS "detected CRC Anomalies" 1761 MAX-ACCESS read-only 1762 STATUS current 1763 DESCRIPTION 1764 "Count of CRC anomalies during the 1-day interval as 1765 measured by hdsl2Shdsl1DayIntervalMoniSecs." 1766 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1767 ::= { hdsl2Shdsl1DayIntervalEntry 5 } 1769 hdsl2Shdsl1DayIntervalLOSWS OBJECT-TYPE 1770 SYNTAX Hdsl2Shdsl1DayIntervalCount 1771 UNITS "seconds" 1772 MAX-ACCESS read-only 1773 STATUS current 1774 DESCRIPTION 1775 "Count of Loss of Sync Word (LOSW) Seconds during the 1-day 1776 interval as measured by hdsl2Shdsl1DayIntervalMoniSecs." 1777 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1778 ::= { hdsl2Shdsl1DayIntervalEntry 6 } 1780 hdsl2Shdsl1DayIntervalUAS OBJECT-TYPE 1781 SYNTAX Hdsl2Shdsl1DayIntervalCount 1782 UNITS "seconds" 1783 MAX-ACCESS read-only 1784 STATUS current 1785 DESCRIPTION 1786 "Count of Unavailable Seconds (UAS) during the 1-day interval 1787 as measured by hdsl2Shdsl1DayIntervalMoniSecs." 1788 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1789 ::= { hdsl2Shdsl1DayIntervalEntry 7 } 1791 -- Maintenance Group 1792 -- 1794 hdsl2ShdslEndpointMaintTable OBJECT-TYPE 1795 SYNTAX SEQUENCE OF Hdsl2ShdslEndpointMaintEntry 1796 MAX-ACCESS not-accessible 1797 STATUS current 1798 DESCRIPTION 1799 "This table supports maintenance operations (eg. loopbacks) 1800 to be performed on HDSL2/SHDSL segment endpoints. This table 1801 contains live data from equipment. As such, it is NOT 1802 persistent." 1803 ::= { hdsl2ShdslMibObjects 8 } 1805 hdsl2ShdslEndpointMaintEntry OBJECT-TYPE 1806 SYNTAX Hdsl2ShdslEndpointMaintEntry 1808 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 1810 MAX-ACCESS not-accessible 1811 STATUS current 1812 DESCRIPTION 1813 "An entry in the hdsl2ShdslEndpointMaintTable. Each entry 1814 corresponds to a single segment endpoint, and is indexed by the 1815 ifIndex of the HDSL2/SHDSL line, the UnitId of the associated 1816 unit and the side of the unit." 1817 INDEX { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide } 1818 ::= { hdsl2ShdslEndpointMaintTable 1 } 1820 Hdsl2ShdslEndpointMaintEntry ::= 1821 SEQUENCE 1822 { 1823 hdsl2ShdslMaintLoopbackConfig INTEGER, 1824 hdsl2ShdslMaintTipRingReversal INTEGER, 1825 hdsl2ShdslMaintPowerBackOff INTEGER, 1826 hdsl2ShdslMaintSoftRestart INTEGER 1827 } 1829 hdsl2ShdslMaintLoopbackConfig OBJECT-TYPE 1830 SYNTAX INTEGER 1831 { 1832 noLoopback(1), 1833 normalLoopback(2), 1834 specialLoopback(3) 1835 } 1836 MAX-ACCESS read-write 1837 STATUS current 1838 DESCRIPTION 1839 "This object controls configuration of loopbacks for the 1840 associated segment endpoint. The status of the loopback 1841 is obtained via the hdsl2ShdslEndpointCurrStatus object." 1842 ::= { hdsl2ShdslEndpointMaintEntry 1 } 1844 hdsl2ShdslMaintTipRingReversal OBJECT-TYPE 1845 SYNTAX INTEGER 1846 { 1847 normal(1), 1848 reversed(2) 1849 } 1850 MAX-ACCESS read-only 1851 STATUS current 1852 DESCRIPTION 1853 "This object indicates the state of the tip/ring pair at the 1854 associated segment endpoint." 1855 ::= { hdsl2ShdslEndpointMaintEntry 2 } 1857 hdsl2ShdslMaintPowerBackOff OBJECT-TYPE 1858 SYNTAX INTEGER 1859 { 1860 default(1), 1861 enhanced(2) 1862 } 1864 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 1866 MAX-ACCESS read-write 1867 STATUS current 1868 DESCRIPTION 1869 "This object configures the receiver at the associated 1870 segment endpoint to operate in default or enhanced power 1871 backoff mode." 1872 ::= { hdsl2ShdslEndpointMaintEntry 3 } 1874 hdsl2ShdslMaintSoftRestart OBJECT-TYPE 1875 SYNTAX INTEGER 1876 { 1877 ready(1), 1878 restart(2) 1879 } 1880 MAX-ACCESS read-write 1881 STATUS current 1882 DESCRIPTION 1883 "This object enables the manager to trigger a soft restart 1884 of the modem at the associated segment endpoint. The manager 1885 may only set this object to the 'restart(2)' value, which 1886 initiates a restart. The agent will perform a restart after 1887 approximately 5 seconds. Following the 5 second period, the 1888 agent will restore the object to the 'ready(1)' state." 1889 ::= { hdsl2ShdslEndpointMaintEntry 4 } 1891 hdsl2ShdslUnitMaintTable OBJECT-TYPE 1892 SYNTAX SEQUENCE OF Hdsl2ShdslUnitMaintEntry 1893 MAX-ACCESS not-accessible 1894 STATUS current 1895 DESCRIPTION 1896 "This table supports maintenance operations for units in a 1897 HDSL2/SHDSL line. Entries in this table MUST be maintained 1898 in a persistent manner." 1899 ::= { hdsl2ShdslMibObjects 9 } 1901 hdsl2ShdslUnitMaintEntry OBJECT-TYPE 1902 SYNTAX Hdsl2ShdslUnitMaintEntry 1903 MAX-ACCESS not-accessible 1904 STATUS current 1905 DESCRIPTION 1906 "An entry in the hdsl2ShdslUnitMaintTable. Each entry 1907 corresponds to a single unit, and is indexed by the ifIndex 1908 of the HDSL2/SHDSL line and the UnitId of the associated 1909 unit." 1910 INDEX { ifIndex, hdsl2ShdslInvIndex } 1911 ::= { hdsl2ShdslUnitMaintTable 1 } 1913 Hdsl2ShdslUnitMaintEntry ::= 1914 SEQUENCE 1915 { 1916 hdsl2ShdslMaintLoopbackTimeout Integer32, 1917 hdsl2ShdslMaintUnitPowerSource INTEGER 1918 } 1920 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 1922 hdsl2ShdslMaintLoopbackTimeout OBJECT-TYPE 1923 SYNTAX Integer32(0..4095) 1924 UNITS "minutes" 1925 MAX-ACCESS read-write 1926 STATUS current 1927 DESCRIPTION 1928 "This object configures the timeout value for loopbacks 1929 initiated at segments endpoints contained in the associated 1930 unit. A value of 0 disables the timeout." 1931 ::= { hdsl2ShdslUnitMaintEntry 1 } 1933 hdsl2ShdslMaintUnitPowerSource OBJECT-TYPE 1934 SYNTAX INTEGER 1935 { 1936 local(1), 1937 span(2) 1938 } 1939 MAX-ACCESS read-only 1940 STATUS current 1941 DESCRIPTION 1942 "This object indicates the DC power source being used by the 1943 associated unit." 1944 ::= { hdsl2ShdslUnitMaintEntry 2 } 1946 -- Span Configuration Profile Group 1947 -- 1949 hdsl2ShdslSpanConfProfileTable OBJECT-TYPE 1950 SYNTAX SEQUENCE OF Hdsl2ShdslSpanConfProfileEntry 1951 MAX-ACCESS not-accessible 1952 STATUS current 1953 DESCRIPTION 1954 "This table supports definitions of span configuration 1955 profiles for SHDSL lines. HDSL2 does not support these 1956 configuration options. This table MUST be maintained 1957 in a persistent manner." 1958 ::= { hdsl2ShdslMibObjects 10 } 1960 hdsl2ShdslSpanConfProfileEntry OBJECT-TYPE 1961 SYNTAX Hdsl2ShdslSpanConfProfileEntry 1962 MAX-ACCESS not-accessible 1963 STATUS current 1964 DESCRIPTION 1965 "Each entry corresponds to a single span configuration 1966 profile. Each profile contains a set of span configuration 1967 parameters. The configuration parameters in a profile are 1968 applied to those lines referencing that profile (see the 1969 hdsl2ShdslSpanConfProfile object). Profiles may be 1970 created/deleted using the row creation/deletion mechanism 1971 via hdsl2ShdslSpanConfProfileRowStatus. If an active 1972 entry is referenced in hdsl2ShdslSpanConfProfile, the 1973 entry MUST remain active until all references are removed." 1975 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 1977 INDEX { IMPLIED hdsl2ShdslSpanConfProfileName } 1978 ::= { hdsl2ShdslSpanConfProfileTable 1 } 1980 Hdsl2ShdslSpanConfProfileEntry ::= 1981 SEQUENCE 1982 { 1983 hdsl2ShdslSpanConfProfileName SnmpAdminString, 1984 hdsl2ShdslSpanConfWireInterface INTEGER, 1985 hdsl2ShdslSpanConfMinLineRate INTEGER, 1986 hdsl2ShdslSpanConfMaxLineRate INTEGER, 1987 hdsl2ShdslSpanConfPSD INTEGER, 1988 hdsl2ShdslSpanConfTransmissionMode 1989 Hdsl2ShdslTransmissionModeType, 1990 hdsl2ShdslSpanConfRemoteEnabled INTEGER, 1991 hdsl2ShdslSpanConfPowerFeeding INTEGER, 1992 hdsl2ShdslSpanConfCurrCondTargetMarginDown INTEGER, 1993 hdsl2ShdslSpanConfWorstCaseTargetMarginDown INTEGER, 1994 hdsl2ShdslSpanConfCurrCondTargetMarginUp INTEGER, 1995 hdsl2ShdslSpanConfWorstCaseTargetMarginUp INTEGER, 1996 hdsl2ShdslSpanConfUsedTargetMargins BITS, 1997 hdsl2ShdslSpanConfProfileRowStatus RowStatus 1998 } 2000 hdsl2ShdslSpanConfProfileName OBJECT-TYPE 2001 SYNTAX SnmpAdminString (SIZE(1..32)) 2002 MAX-ACCESS not-accessible 2003 STATUS current 2004 DESCRIPTION 2005 "This object is the unique index associated with this profile. 2006 Entries in this table are referenced via the object 2007 hdsl2ShdslSpanConfProfile in Hdsl2ShdslSpanConfEntry." 2008 ::= { hdsl2ShdslSpanConfProfileEntry 1 } 2010 hdsl2ShdslSpanConfWireInterface OBJECT-TYPE 2011 SYNTAX INTEGER 2012 { 2013 twoWire(1), 2014 fourWire(2) 2015 } 2016 MAX-ACCESS read-create 2017 STATUS current 2018 DESCRIPTION 2019 "This object configures the two-wire or optional four-wire 2020 operation for SHDSL Lines." 2021 DEFVAL { twoWire } 2022 ::= { hdsl2ShdslSpanConfProfileEntry 2 } 2024 hdsl2ShdslSpanConfMinLineRate OBJECT-TYPE 2025 SYNTAX INTEGER(0..4112000) 2026 UNITS "bps" 2027 MAX-ACCESS read-create 2028 STATUS current 2029 DESCRIPTION 2031 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 2033 "This object configures the minimum transmission rate for 2034 the associated SHDSL Line in bits-per-second (bps). If 2035 the minimum line rate equals the maximum line rate 2036 (hdsl2ShdslSpanMaxLineRate), the line rate is considered 2037 'fixed'. If the minimum line rate is less than the maximum 2038 line rate, the line rate is considered 'rate-adaptive'." 2039 DEFVAL { 1552000 } 2040 ::= { hdsl2ShdslSpanConfProfileEntry 3 } 2042 hdsl2ShdslSpanConfMaxLineRate OBJECT-TYPE 2043 SYNTAX INTEGER(0..4112000) 2044 UNITS "bps" 2045 MAX-ACCESS read-create 2046 STATUS current 2047 DESCRIPTION 2048 "This object configures the maximum transmission rate for 2049 the associated SHDSL Line in bits-per-second (bps). If 2050 the minimum line rate equals the maximum line rate 2051 (hdsl2ShdslSpanMaxLineRate), the line rate is considered 2052 'fixed'. If the minimum line rate is less than the maximum 2053 line rate, the line rate is considered 'rate-adaptive'." 2054 DEFVAL { 1552000 } 2055 ::= { hdsl2ShdslSpanConfProfileEntry 4 } 2057 hdsl2ShdslSpanConfPSD OBJECT-TYPE 2058 SYNTAX INTEGER 2059 { 2060 symmetric(1), 2061 asymmetric(2) 2062 } 2063 MAX-ACCESS read-create 2064 STATUS current 2065 DESCRIPTION 2066 "This object configures use of symmetric/asymmetric PSD (Power 2067 Spectral Density) Mask for the associated SHDSL Line. Support 2068 for symmetric PSD is mandatory for all supported data rates. 2069 Support for asymmetric PSD is optional." 2070 DEFVAL { symmetric } 2071 ::= { hdsl2ShdslSpanConfProfileEntry 5 } 2073 hdsl2ShdslSpanConfTransmissionMode OBJECT-TYPE 2074 SYNTAX Hdsl2ShdslTransmissionModeType 2075 MAX-ACCESS read-create 2076 STATUS current 2077 DESCRIPTION 2078 "This object specifies the regional setting for the SHDSL 2079 line." 2080 DEFVAL { region1 } 2081 ::= { hdsl2ShdslSpanConfProfileEntry 6 } 2083 hdsl2ShdslSpanConfRemoteEnabled OBJECT-TYPE 2084 SYNTAX INTEGER 2085 { 2087 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 2089 enabled(1), 2090 disabled(2) 2091 } 2092 MAX-ACCESS read-create 2093 STATUS current 2094 DESCRIPTION 2095 "This object enables/disables support for remote management 2096 of the units in a SHDSL line from the STU-R via the EOC." 2097 DEFVAL { enabled } 2098 ::= { hdsl2ShdslSpanConfProfileEntry 7 } 2100 hdsl2ShdslSpanConfPowerFeeding OBJECT-TYPE 2101 SYNTAX INTEGER 2102 { 2103 noPower(1), 2104 powerFeed(2), 2105 wettingCurrent(3) 2106 } 2107 MAX-ACCESS read-create 2108 STATUS current 2109 DESCRIPTION 2110 "This object enables/disables support for optional power 2111 feeding in a SHDSL line." 2112 DEFVAL { noPower } 2113 ::= { hdsl2ShdslSpanConfProfileEntry 8 } 2115 hdsl2ShdslSpanConfCurrCondTargetMarginDown OBJECT-TYPE 2116 SYNTAX INTEGER(-10..21) 2117 UNITS "dB" 2118 MAX-ACCESS read-create 2119 STATUS current 2120 DESCRIPTION 2121 "This object specifies the downstream current condition target 2122 SNR margin for a SHDSL line. The SNR margin is the difference 2123 between the desired SNR and the actual SNR. Target SNR margin 2124 is the desired SNR margin for a unit." 2125 DEFVAL { 0 } 2126 ::= { hdsl2ShdslSpanConfProfileEntry 9 } 2128 hdsl2ShdslSpanConfWorstCaseTargetMarginDown OBJECT-TYPE 2129 SYNTAX INTEGER(-10..21) 2130 UNITS "dB" 2131 MAX-ACCESS read-create 2132 STATUS current 2133 DESCRIPTION 2134 "This object specifies the downstream worst case target SNR 2135 margin for a SHDSL line. The SNR margin is the difference 2136 between the desired SNR and the actual SNR. Target SNR 2137 margin is the desired SNR margin for a unit." 2138 DEFVAL { 0 } 2139 ::= { hdsl2ShdslSpanConfProfileEntry 10 } 2141 hdsl2ShdslSpanConfCurrCondTargetMarginUp OBJECT-TYPE 2143 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 2145 SYNTAX INTEGER(-10..21) 2146 UNITS "dB" 2147 MAX-ACCESS read-create 2148 STATUS current 2149 DESCRIPTION 2150 "This object specifies the upstream current condition target 2151 SNR margin for a SHDSL line. The SNR margin is the difference 2152 between the desired SNR and the actual SNR. Target SNR margin 2153 is the desired SNR margin for a unit." 2154 DEFVAL { 0 } 2155 ::= { hdsl2ShdslSpanConfProfileEntry 11 } 2157 hdsl2ShdslSpanConfWorstCaseTargetMarginUp OBJECT-TYPE 2158 SYNTAX INTEGER(-10..21) 2159 UNITS "dB" 2160 MAX-ACCESS read-create 2161 STATUS current 2162 DESCRIPTION 2163 "This object specifies the upstream worst case target SNR 2164 margin for a SHDSL line. The SNR margin is the difference 2165 between the desired SNR and the actual SNR. Target SNR margin 2166 is the desired SNR margin for a unit." 2167 DEFVAL { 0 } 2168 ::= { hdsl2ShdslSpanConfProfileEntry 12 } 2170 hdsl2ShdslSpanConfUsedTargetMargins OBJECT-TYPE 2171 SYNTAX BITS 2172 { 2173 currCondDown(0), 2174 worstCaseDown(1), 2175 currCondUp(2), 2176 worstCaseUp(3) 2177 } 2178 MAX-ACCESS read-create 2179 STATUS current 2180 DESCRIPTION 2181 "Contains indicates whether a target SNR margin is enabled or 2182 disabled. This is a bit-map of possible settings. The 2183 various bit positions are: 2185 currCondDown current condition downstream target SNR 2186 margin enabled 2188 worstCaseDown worst case downstream target SNR margin 2189 enabled 2191 currCondUp current condition upstream target SNR 2192 margin enabled 2194 worstCaseUp worst case upstream target SNR margin 2195 enabled." 2196 DEFVAL { 0 } 2197 ::= { hdsl2ShdslSpanConfProfileEntry 13 } 2199 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 2201 hdsl2ShdslSpanConfProfileRowStatus OBJECT-TYPE 2202 SYNTAX RowStatus 2203 MAX-ACCESS read-create 2204 STATUS current 2205 DESCRIPTION 2206 "This object controls creation/deletion of the associated 2207 entry in this table per the semantics of RowStatus. If an 2208 active entry is referenced in hdsl2ShdslSpanConfProfile, the 2209 entry MUST remain active until all references are removed." 2210 ::= { hdsl2ShdslSpanConfProfileEntry 14 } 2212 -- Segment Endpoint Alarm Configuration Profile group 2213 -- 2215 hdsl2ShdslEndpointAlarmConfProfileTable OBJECT-TYPE 2216 SYNTAX SEQUENCE OF Hdsl2ShdslEndpointAlarmConfProfileEntry 2217 MAX-ACCESS not-accessible 2218 STATUS current 2219 DESCRIPTION 2220 "This table supports definitions of alarm configuration 2221 profiles for HDSL2/SHDSL segment endpoints. This table 2222 MUST be maintained in a persistent manner." 2223 ::= { hdsl2ShdslMibObjects 11 } 2225 hdsl2ShdslEndpointAlarmConfProfileEntry OBJECT-TYPE 2226 SYNTAX Hdsl2ShdslEndpointAlarmConfProfileEntry 2227 MAX-ACCESS not-accessible 2228 STATUS current 2229 DESCRIPTION 2230 "Each entry corresponds to a single alarm configuration profile. 2231 Each profile contains a set of parameters for setting alarm 2232 thresholds for various performance attributes monitored at 2233 HDSL2/SHDSL segment endpoints. Profiles may be created/deleted 2234 using the row creation/deletion mechanism via 2235 hdsl2ShdslEndpointAlarmConfProfileRowStatus. If an active 2236 entry is referenced in either hdsl2ShdslSpanConfAlarmProfile 2237 or hdsl2ShdslEndpointAlarmConfProfile, the entry MUST remain 2238 active until all references are removed." 2239 INDEX { IMPLIED hdsl2ShdslEndpointAlarmConfProfileName } 2240 ::= { hdsl2ShdslEndpointAlarmConfProfileTable 1 } 2242 Hdsl2ShdslEndpointAlarmConfProfileEntry ::= 2243 SEQUENCE 2244 { 2245 hdsl2ShdslEndpointAlarmConfProfileName SnmpAdminString, 2246 hdsl2ShdslEndpointThreshLoopAttenuation INTEGER, 2247 hdsl2ShdslEndpointThreshSNRMargin INTEGER, 2248 hdsl2ShdslEndpointThreshES 2249 Hdsl2ShdslPerfIntervalThreshold, 2250 hdsl2ShdslEndpointThreshSES 2251 Hdsl2ShdslPerfIntervalThreshold, 2252 hdsl2ShdslEndpointThreshCRCanomalies Integer32, 2254 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 2256 hdsl2ShdslEndpointThreshLOSWS 2257 Hdsl2ShdslPerfIntervalThreshold, 2258 hdsl2ShdslEndpointThreshUAS 2259 Hdsl2ShdslPerfIntervalThreshold, 2260 hdsl2ShdslEndpointAlarmConfProfileRowStatus RowStatus 2261 } 2263 hdsl2ShdslEndpointAlarmConfProfileName OBJECT-TYPE 2264 SYNTAX SnmpAdminString (SIZE(1..32)) 2265 MAX-ACCESS not-accessible 2266 STATUS current 2267 DESCRIPTION 2268 "This object is the unique index associated with this profile." 2269 ::= { hdsl2ShdslEndpointAlarmConfProfileEntry 1 } 2271 hdsl2ShdslEndpointThreshLoopAttenuation OBJECT-TYPE 2272 SYNTAX INTEGER(-127..128) 2273 UNITS "dB" 2274 MAX-ACCESS read-create 2275 STATUS current 2276 DESCRIPTION 2277 "This object configures the loop attenuation alarm threshold. 2278 When the current value of hdsl2ShdslEndpointCurrAtn reaches 2279 or drops below this threshold, a hdsl2ShdslLoopAttenCrossing 2280 MAY be generated." 2281 DEFVAL { 0 } 2282 ::= { hdsl2ShdslEndpointAlarmConfProfileEntry 2 } 2284 hdsl2ShdslEndpointThreshSNRMargin OBJECT-TYPE 2285 SYNTAX INTEGER(-127..128) 2286 UNITS "dB" 2287 MAX-ACCESS read-create 2288 STATUS current 2289 DESCRIPTION 2290 "This object configures the SNR margin alarm threshold. 2291 When the current value of hdsl2ShdslEndpointCurrSnrMgn 2292 reaches or drops below this threshold, a 2293 hdsl2ShdslSNRMarginCrossing MAY be generated." 2294 DEFVAL { 0 } 2295 ::= { hdsl2ShdslEndpointAlarmConfProfileEntry 3 } 2297 hdsl2ShdslEndpointThreshES OBJECT-TYPE 2298 SYNTAX Hdsl2ShdslPerfIntervalThreshold 2299 UNITS "seconds" 2300 MAX-ACCESS read-create 2301 STATUS current 2302 DESCRIPTION 2303 "This object configures the threshold for the number of 2304 errored seconds (ES) within any given 15-minute performance 2305 data collection interval. If the value of errored seconds 2306 in a particular 15-minute collection interval reaches/ 2307 exceeds this value, a hdsl2ShdslPerfESThresh MAY be 2308 generated. At most one notification will be sent per 2310 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 2312 interval per endpoint." 2313 DEFVAL { 0 } 2314 ::= { hdsl2ShdslEndpointAlarmConfProfileEntry 4 } 2316 hdsl2ShdslEndpointThreshSES OBJECT-TYPE 2317 SYNTAX Hdsl2ShdslPerfIntervalThreshold 2318 UNITS "seconds" 2319 MAX-ACCESS read-create 2320 STATUS current 2321 DESCRIPTION 2322 "This object configures the threshold for the number of 2323 severely errored seconds (SES) within any given 15-minute 2324 performance data collection interval. If the value of 2325 severely errored seconds in a particular 15-minute collection 2326 interval reaches/exceeds this value, a hdsl2ShdslPerfSESThresh 2327 MAY be generated. At most one notification will be sent per 2328 interval per endpoint." 2329 DEFVAL { 0 } 2330 ::= { hdsl2ShdslEndpointAlarmConfProfileEntry 5 } 2332 hdsl2ShdslEndpointThreshCRCanomalies OBJECT-TYPE 2333 SYNTAX Integer32 2334 UNITS "detected CRC Anomalies" 2335 MAX-ACCESS read-create 2336 STATUS current 2337 DESCRIPTION 2338 "This object configures the threshold for the number of 2339 CRC anomalies within any given 15-minute performance data 2340 collection interval. If the value of CRC anomalies in a 2341 particular 15-minute collection interval reaches/exceeds 2342 this value, a hdsl2ShdslPerfCRCanomaliesThresh MAY be 2343 generated. At most one notification will be sent per 2344 interval per endpoint." 2345 DEFVAL { 0 } 2346 ::= { hdsl2ShdslEndpointAlarmConfProfileEntry 6 } 2348 hdsl2ShdslEndpointThreshLOSWS OBJECT-TYPE 2349 SYNTAX Hdsl2ShdslPerfIntervalThreshold 2350 UNITS "seconds" 2351 MAX-ACCESS read-create 2352 STATUS current 2353 DESCRIPTION 2354 "This object configures the threshold for the number of 2355 Loss of Sync Word (LOSW) Seconds within any given 15-minute 2356 performance data collection interval. If the value of LOSW 2357 in a particular 15-minute collection interval reaches/exceeds 2358 this value, a hdsl2ShdslPerfLOSWSThresh MAY be generated. 2359 At most one notification will be sent per interval per 2360 endpoint." 2361 DEFVAL { 0 } 2362 ::= { hdsl2ShdslEndpointAlarmConfProfileEntry 7 } 2364 hdsl2ShdslEndpointThreshUAS OBJECT-TYPE 2366 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 2368 SYNTAX Hdsl2ShdslPerfIntervalThreshold 2369 UNITS "seconds" 2370 MAX-ACCESS read-create 2371 STATUS current 2372 DESCRIPTION 2373 "This object configures the threshold for the number of 2374 unavailable seconds (UAS) within any given 15-minute 2375 performance data collection interval. If the value of UAS 2376 in a particular 15-minute collection interval reaches/exceeds 2377 this value, a hdsl2ShdslPerfUASThresh MAY be generated. 2378 At most one notification will be sent per interval per 2379 endpoint." 2380 DEFVAL { 0 } 2381 ::= { hdsl2ShdslEndpointAlarmConfProfileEntry 8 } 2383 hdsl2ShdslEndpointAlarmConfProfileRowStatus OBJECT-TYPE 2384 SYNTAX RowStatus 2385 MAX-ACCESS read-create 2386 STATUS current 2387 DESCRIPTION 2388 "This object controls creation/deletion of the associated 2389 entry in this table as per the semantics of RowStatus. 2390 If an active entry is referenced in either 2391 hdsl2ShdslSpanConfAlarmProfile or 2392 hdsl2ShdslEndpointAlarmConfProfile, the entry MUST remain 2393 active until all references are removed." 2394 ::= { hdsl2ShdslEndpointAlarmConfProfileEntry 9 } 2396 -- Notifications Group 2397 -- 2399 hdsl2ShdslNotifications OBJECT IDENTIFIER ::= { hdsl2ShdslMIB 0 } 2401 hdsl2ShdslLoopAttenCrossing NOTIFICATION-TYPE 2402 OBJECTS 2403 { 2404 hdsl2ShdslEndpointCurrAtn, 2405 hdsl2ShdslEndpointThreshLoopAttenuation 2406 } 2407 STATUS current 2408 DESCRIPTION 2409 "This notification indicates that the loop attenuation 2410 threshold (as per the hdsl2ShdslEndpointThreshLoopAttenuation 2411 value) has been reached/exceeded for the HDSL2/SHDSL segment 2412 endpoint." 2413 ::= { hdsl2ShdslNotifications 1 } 2415 hdsl2ShdslSNRMarginCrossing NOTIFICATION-TYPE 2416 OBJECTS 2417 { 2418 hdsl2ShdslEndpointCurrSnrMgn, 2419 hdsl2ShdslEndpointThreshSNRMargin 2420 } 2422 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 2424 STATUS current 2425 DESCRIPTION 2426 "This notification indicates that the SNR margin threshold (as 2427 per the hdsl2ShdslEndpointThreshSNRMargin value) has been 2428 reached/exceeded for the HDSL2/SHDSL segment endpoint." 2429 ::= { hdsl2ShdslNotifications 2 } 2431 hdsl2ShdslPerfESThresh NOTIFICATION-TYPE 2432 OBJECTS 2433 { 2434 hdsl2ShdslEndpointCurr15MinES, 2435 hdsl2ShdslEndpointThreshES 2436 } 2437 STATUS current 2438 DESCRIPTION 2439 "This notification indicates that the errored seconds threshold 2440 (as per the hdsl2ShdslEndpointThreshES value) has been reached/ 2441 exceeded for the HDSL2/SHDSL segment endpoint." 2442 ::= { hdsl2ShdslNotifications 3 } 2444 hdsl2ShdslPerfSESThresh NOTIFICATION-TYPE 2445 OBJECTS 2446 { 2447 hdsl2ShdslEndpointCurr15MinSES, 2448 hdsl2ShdslEndpointThreshSES 2449 } 2450 STATUS current 2451 DESCRIPTION 2452 "This notification indicates that the severely errored seconds 2453 threshold (as per the hdsl2ShdslEndpointThreshSES value) has 2454 been reached/exceeded for the HDSL2/SHDSL Segment Endpoint." 2455 ::= { hdsl2ShdslNotifications 4 } 2457 hdsl2ShdslPerfCRCanomaliesThresh NOTIFICATION-TYPE 2458 OBJECTS 2459 { 2460 hdsl2ShdslEndpointCurr15MinCRCanomalies, 2461 hdsl2ShdslEndpointThreshCRCanomalies 2462 } 2463 STATUS current 2464 DESCRIPTION 2465 "This notification indicates that the CRC anomalies threshold 2466 (as per the hdsl2ShdslEndpointThreshCRCanomalies value) has 2467 been reached/exceeded for the HDSL2/SHDSL Segment Endpoint." 2468 ::= { hdsl2ShdslNotifications 5 } 2470 hdsl2ShdslPerfLOSWSThresh NOTIFICATION-TYPE 2471 OBJECTS 2472 { 2473 hdsl2ShdslEndpointCurr15MinLOSWS, 2474 hdsl2ShdslEndpointThreshLOSWS 2475 } 2476 STATUS current 2478 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 2480 DESCRIPTION 2481 "This notification indicates that the LOSW seconds threshold 2482 (as per the hdsl2ShdslEndpointThreshLOSWS value) has been 2483 reached/exceeded for the HDSL2/SHDSL segment endpoint." 2484 ::= { hdsl2ShdslNotifications 6 } 2486 hdsl2ShdslPerfUASThresh NOTIFICATION-TYPE 2487 OBJECTS 2488 { 2489 hdsl2ShdslEndpointCurr15MinUAS, 2490 hdsl2ShdslEndpointThreshUAS 2491 } 2492 STATUS current 2493 DESCRIPTION 2494 "This notification indicates that the unavailable seconds 2495 threshold (as per the hdsl2ShdslEndpointThreshUAS value) has 2496 been reached/exceeded for the HDSL2/SHDSL segment endpoint." 2497 ::= { hdsl2ShdslNotifications 7 } 2499 hdsl2ShdslSpanInvalidNumRepeaters NOTIFICATION-TYPE 2500 OBJECTS 2501 { 2502 hdsl2ShdslSpanConfNumRepeaters 2503 } 2504 STATUS current 2505 DESCRIPTION 2506 "This notification indicates that a mismatch has been detected 2507 between the number of repeater/regenerator units configured 2508 for a HDSL2/SHDSL line via the hdsl2ShdslSpanConfNumRepeaters 2509 object and the actual number of repeater/regenerator units 2510 discovered via the EOC." 2511 ::= { hdsl2ShdslNotifications 8 } 2513 hdsl2ShdslLoopbackFailure NOTIFICATION-TYPE 2514 OBJECTS 2515 { 2516 hdsl2ShdslMaintLoopbackConfig 2517 } 2518 STATUS current 2519 DESCRIPTION 2520 "This notification indicates that an endpoint maintenance 2521 loopback command failed for an HDSL2/SHDSL segment." 2522 ::= { hdsl2ShdslNotifications 9 } 2524 hdsl2ShdslpowerBackoff NOTIFICATION-TYPE 2525 OBJECTS 2526 { 2527 hdsl2ShdslEndpointCurrStatus 2528 } 2529 STATUS current 2530 DESCRIPTION 2531 "This notification indicates that the bit setting for 2532 powerBackoff in the hdsl2ShdslEndpointCurrStatus object for 2534 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 2536 this endpoint has changed." 2537 ::= { hdsl2ShdslNotifications 10 } 2539 hdsl2ShdsldeviceFault NOTIFICATION-TYPE 2540 OBJECTS 2541 { 2542 hdsl2ShdslEndpointCurrStatus 2543 } 2544 STATUS current 2545 DESCRIPTION 2546 "This notification indicates that the bit setting for 2547 deviceFault in the hdsl2ShdslEndpointCurrStatus object for 2548 this endpoint has changed." 2549 ::= { hdsl2ShdslNotifications 11 } 2551 hdsl2ShdsldcContinuityFault NOTIFICATION-TYPE 2552 OBJECTS 2553 { 2554 hdsl2ShdslEndpointCurrStatus 2555 } 2556 STATUS current 2557 DESCRIPTION 2558 "This notification indicates that the bit setting for 2559 dcContinuityFault in the hdsl2ShdslEndpointCurrStatus object 2560 for this endpoint has changed." 2561 ::= { hdsl2ShdslNotifications 12 } 2563 hdsl2ShdslconfigInitFailure NOTIFICATION-TYPE 2564 OBJECTS 2565 { 2566 hdsl2ShdslEndpointCurrStatus 2567 } 2568 STATUS current 2569 DESCRIPTION 2570 "This notification indicates that the bit setting for 2571 configInitFailure in the hdsl2ShdslEndpointCurrStatus object 2572 for this endpoint has changed." 2573 ::= { hdsl2ShdslNotifications 13 } 2575 hdsl2ShdslprotocolInitFailure NOTIFICATION-TYPE 2576 OBJECTS 2577 { 2578 hdsl2ShdslEndpointCurrStatus 2579 } 2580 STATUS current 2581 DESCRIPTION 2582 "This notification indicates that the bit setting for 2583 protocolInitFailure in the hdsl2ShdslEndpointCurrStatus 2584 object for this endpoint has changed." 2585 ::= { hdsl2ShdslNotifications 14 } 2587 hdsl2ShdslnoNeighborPresent NOTIFICATION-TYPE 2588 OBJECTS 2590 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 2592 { 2593 hdsl2ShdslEndpointCurrStatus 2594 } 2595 STATUS current 2596 DESCRIPTION 2597 "This notification indicates that the bit setting for 2598 noNeighborPresent in the hdsl2ShdslEndpointCurrStatus object 2599 for this endpoint has changed." 2600 ::= { hdsl2ShdslNotifications 15 } 2602 hdsl2ShdslLocalPowerLoss NOTIFICATION-TYPE 2603 OBJECTS 2604 { 2605 ifIndex, 2606 hdsl2ShdslInvIndex 2607 } 2608 STATUS current 2609 DESCRIPTION 2610 "This notification indicates impending unit failure due to 2611 loss of local power (last gasp)." 2612 ::= { hdsl2ShdslNotifications 16 } 2614 -- conformance information 2615 -- 2617 hdsl2ShdslConformance OBJECT IDENTIFIER ::= { hdsl2ShdslMIB 3 } 2618 hdsl2ShdslGroups OBJECT IDENTIFIER ::= 2619 { hdsl2ShdslConformance 1 } 2620 hdsl2ShdslCompliances OBJECT IDENTIFIER ::= 2621 { hdsl2ShdslConformance 2 } 2623 -- agent compliance statements 2625 hdsl2ShdslLineMibCompliance MODULE-COMPLIANCE 2626 STATUS current 2627 DESCRIPTION 2628 "The section outlines compliance requirements for this MIB." 2629 MODULE 2630 MANDATORY-GROUPS 2631 { 2632 hdsl2ShdslSpanConfGroup, 2633 hdsl2ShdslSpanStatusGroup, 2634 hdsl2ShdslInventoryGroup, 2635 hdsl2ShdslEndpointConfGroup, 2636 hdsl2ShdslEndpointCurrGroup, 2637 hdsl2Shdsl15MinIntervalGroup, 2638 hdsl2Shdsl1DayIntervalGroup, 2639 hdsl2ShdslMaintenanceGroup, 2640 hdsl2ShdslEndpointAlarmConfGroup, 2641 hdsl2ShdslNotificationGroup 2642 } 2644 GROUP hdsl2ShdslInventoryShdslGroup 2646 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 2648 DESCRIPTION 2649 "Support for this group is only required for implementations 2650 supporting SHDSL lines." 2652 GROUP hdsl2ShdslSpanShdslStatusGroup 2653 DESCRIPTION 2654 "Support for this group is only required for implementations 2655 supporting SHDSL lines." 2657 GROUP hdsl2ShdslSpanConfProfileGroup 2658 DESCRIPTION 2659 "Support for this group is only required for implementations 2660 supporting SHDSL lines." 2662 ::= { hdsl2ShdslCompliances 1 } 2664 -- units of conformance 2665 -- 2667 hdsl2ShdslSpanConfGroup OBJECT-GROUP 2668 OBJECTS 2669 { 2670 hdsl2ShdslSpanConfNumRepeaters, 2671 hdsl2ShdslSpanConfProfile, 2672 hdsl2ShdslSpanConfAlarmProfile 2673 } 2674 STATUS current 2675 DESCRIPTION 2676 "This group supports objects for configuring span related 2677 parameters for HDSL2/SHDSL lines." 2678 ::= { hdsl2ShdslGroups 1 } 2680 hdsl2ShdslSpanStatusGroup OBJECT-GROUP 2681 OBJECTS 2682 { 2683 hdsl2ShdslStatusNumAvailRepeaters 2684 } 2685 STATUS current 2686 DESCRIPTION 2687 "This group supports objects for retrieving span related 2688 status for HDSL2/SHDSL lines." 2689 ::= { hdsl2ShdslGroups 2 } 2691 hdsl2ShdslInventoryShdslGroup OBJECT-GROUP 2692 OBJECTS 2693 { 2694 hdsl2ShdslInvTransmissionModeCapability 2695 } 2696 STATUS current 2697 DESCRIPTION 2698 "This group supports objects for retrieving SHDSL-specific 2699 inventory information." 2700 ::= { hdsl2ShdslGroups 3 } 2702 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 2704 hdsl2ShdslSpanShdslStatusGroup OBJECT-GROUP 2705 OBJECTS 2706 { 2707 hdsl2ShdslStatusMaxAttainableLineRate, 2708 hdsl2ShdslStatusActualLineRate, 2709 hdsl2ShdslStatusTransmissionModeCurrent 2710 } 2711 STATUS current 2712 DESCRIPTION 2713 "This group supports objects for retrieving SHDSL-specific 2714 span related status." 2715 ::= { hdsl2ShdslGroups 4 } 2717 hdsl2ShdslInventoryGroup OBJECT-GROUP 2718 OBJECTS 2719 { 2720 hdsl2ShdslInvIndex, 2721 hdsl2ShdslInvVendorID, 2722 hdsl2ShdslInvVendorModelNumber, 2723 hdsl2ShdslInvVendorSerialNumber, 2724 hdsl2ShdslInvVendorEOCSoftwareVersion, 2725 hdsl2ShdslInvStandardVersion, 2726 hdsl2ShdslInvVendorListNumber, 2727 hdsl2ShdslInvVendorIssueNumber, 2728 hdsl2ShdslInvVendorSoftwareVersion, 2729 hdsl2ShdslInvEquipmentCode, 2730 hdsl2ShdslInvVendorOther 2731 } 2732 STATUS current 2733 DESCRIPTION 2734 "This group supports objects that provide unit inventory 2735 information about the units in HDSL2/SHDSL lines." 2736 ::= { hdsl2ShdslGroups 5 } 2738 hdsl2ShdslEndpointConfGroup OBJECT-GROUP 2739 OBJECTS 2740 { 2741 hdsl2ShdslEndpointSide, 2742 hdsl2ShdslEndpointWirePair, 2743 hdsl2ShdslEndpointAlarmConfProfile 2744 } 2745 STATUS current 2746 DESCRIPTION 2747 "This group supports objects for configuring parameters for 2748 segment endpoints in HDSL2/SHDSL lines." 2749 ::= { hdsl2ShdslGroups 6 } 2751 hdsl2ShdslEndpointCurrGroup OBJECT-GROUP 2752 OBJECTS 2753 { 2754 hdsl2ShdslEndpointSide, 2755 hdsl2ShdslEndpointWirePair, 2757 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 2759 hdsl2ShdslEndpointCurrAtn, 2760 hdsl2ShdslEndpointCurrSnrMgn, 2761 hdsl2ShdslEndpointCurrStatus, 2762 hdsl2ShdslEndpointES, 2763 hdsl2ShdslEndpointSES, 2764 hdsl2ShdslEndpointCRCanomalies, 2765 hdsl2ShdslEndpointLOSWS, 2766 hdsl2ShdslEndpointUAS, 2767 hdsl2ShdslEndpointCurr15MinTimeElapsed, 2768 hdsl2ShdslEndpointCurr15MinES, 2769 hdsl2ShdslEndpointCurr15MinSES, 2770 hdsl2ShdslEndpointCurr15MinCRCanomalies, 2771 hdsl2ShdslEndpointCurr15MinLOSWS, 2772 hdsl2ShdslEndpointCurr15MinUAS, 2773 hdsl2ShdslEndpointCurr1DayTimeElapsed, 2774 hdsl2ShdslEndpointCurr1DayES, 2775 hdsl2ShdslEndpointCurr1DaySES, 2776 hdsl2ShdslEndpointCurr1DayCRCanomalies, 2777 hdsl2ShdslEndpointCurr1DayLOSWS, 2778 hdsl2ShdslEndpointCurr1DayUAS 2779 } 2780 STATUS current 2781 DESCRIPTION 2782 "This group supports objects which provide current status and 2783 performance measurements relating to segment endpoints in 2784 HDSL2/SHDSL lines." 2785 ::= { hdsl2ShdslGroups 7 } 2787 hdsl2Shdsl15MinIntervalGroup OBJECT-GROUP 2788 OBJECTS 2789 { 2790 hdsl2Shdsl15MinIntervalES, 2791 hdsl2Shdsl15MinIntervalSES, 2792 hdsl2Shdsl15MinIntervalCRCanomalies, 2793 hdsl2Shdsl15MinIntervalLOSWS, 2794 hdsl2Shdsl15MinIntervalUAS 2795 } 2796 STATUS current 2797 DESCRIPTION 2798 "This group supports objects which maintain historic 2799 performance measurements relating to segment endpoints in 2800 HDSL2/SHDSL lines in 15-minute intervals." 2801 ::= { hdsl2ShdslGroups 8 } 2803 hdsl2Shdsl1DayIntervalGroup OBJECT-GROUP 2804 OBJECTS 2805 { 2806 hdsl2Shdsl1DayIntervalMoniSecs, 2807 hdsl2Shdsl1DayIntervalES, 2808 hdsl2Shdsl1DayIntervalSES, 2809 hdsl2Shdsl1DayIntervalCRCanomalies, 2810 hdsl2Shdsl1DayIntervalLOSWS, 2811 hdsl2Shdsl1DayIntervalUAS 2813 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 2815 } 2816 STATUS current 2817 DESCRIPTION 2818 "This group supports objects which maintain historic 2819 performance measurements relating to segment endpoints in 2820 HDSL2/SHDSL lines in 1-day intervals." 2821 ::= { hdsl2ShdslGroups 9 } 2823 hdsl2ShdslMaintenanceGroup OBJECT-GROUP 2824 OBJECTS 2825 { 2826 hdsl2ShdslMaintLoopbackConfig, 2827 hdsl2ShdslMaintTipRingReversal, 2828 hdsl2ShdslMaintPowerBackOff, 2829 hdsl2ShdslMaintSoftRestart, 2830 hdsl2ShdslMaintLoopbackTimeout, 2831 hdsl2ShdslMaintUnitPowerSource 2832 } 2833 STATUS current 2834 DESCRIPTION 2835 "This group supports objects that provide support for 2836 maintenance actions for HDSL2/SHDSL lines." 2837 ::= { hdsl2ShdslGroups 10 } 2839 hdsl2ShdslEndpointAlarmConfGroup OBJECT-GROUP 2840 OBJECTS 2841 { 2842 hdsl2ShdslEndpointThreshLoopAttenuation, 2843 hdsl2ShdslEndpointThreshSNRMargin, 2844 hdsl2ShdslEndpointThreshES, 2845 hdsl2ShdslEndpointThreshSES, 2846 hdsl2ShdslEndpointThreshCRCanomalies, 2847 hdsl2ShdslEndpointThreshLOSWS, 2848 hdsl2ShdslEndpointThreshUAS, 2849 hdsl2ShdslEndpointAlarmConfProfileRowStatus 2850 } 2851 STATUS current 2852 DESCRIPTION 2853 "This group supports objects that allow configuration of alarm 2854 thresholds for various performance parameters for HDSL2/SHDSL 2855 lines." 2856 ::= { hdsl2ShdslGroups 11 } 2858 hdsl2ShdslNotificationGroup NOTIFICATION-GROUP 2859 NOTIFICATIONS 2860 { 2861 hdsl2ShdslLoopAttenCrossing, 2862 hdsl2ShdslSNRMarginCrossing, 2863 hdsl2ShdslPerfESThresh, 2864 hdsl2ShdslPerfSESThresh, 2865 hdsl2ShdslPerfCRCanomaliesThresh, 2866 hdsl2ShdslPerfLOSWSThresh, 2867 hdsl2ShdslPerfUASThresh, 2869 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 2871 hdsl2ShdslSpanInvalidNumRepeaters, 2872 hdsl2ShdslLoopbackFailure, 2873 hdsl2ShdslpowerBackoff, 2874 hdsl2ShdsldeviceFault, 2875 hdsl2ShdsldcContinuityFault, 2876 hdsl2ShdslconfigInitFailure, 2877 hdsl2ShdslprotocolInitFailure, 2878 hdsl2ShdslnoNeighborPresent, 2879 hdsl2ShdslLocalPowerLoss 2880 } 2881 STATUS current 2882 DESCRIPTION 2883 "This group supports notifications of significant conditions 2884 associated with HDSL2/SHDSL lines." 2885 ::= { hdsl2ShdslGroups 12 } 2887 hdsl2ShdslSpanConfProfileGroup OBJECT-GROUP 2888 OBJECTS 2889 { 2890 hdsl2ShdslSpanConfWireInterface, 2891 hdsl2ShdslSpanConfMinLineRate, 2892 hdsl2ShdslSpanConfMaxLineRate, 2893 hdsl2ShdslSpanConfPSD, 2894 hdsl2ShdslSpanConfTransmissionMode, 2895 hdsl2ShdslSpanConfRemoteEnabled, 2896 hdsl2ShdslSpanConfPowerFeeding, 2897 hdsl2ShdslSpanConfCurrCondTargetMarginDown, 2898 hdsl2ShdslSpanConfWorstCaseTargetMarginDown, 2899 hdsl2ShdslSpanConfCurrCondTargetMarginUp, 2900 hdsl2ShdslSpanConfWorstCaseTargetMarginUp, 2901 hdsl2ShdslSpanConfUsedTargetMargins, 2902 hdsl2ShdslSpanConfProfileRowStatus 2903 } 2904 STATUS current 2905 DESCRIPTION 2906 "This group supports objects that constitute configuration 2907 profiles for configuring span related parameters in SHDSL 2908 lines." 2909 ::= { hdsl2ShdslGroups 13 } 2911 END 2913 7. Security Considerations 2915 There are a number of management objects defined in this MIB that 2916 have a MAX-ACCESS clause of read-write and/or read-create. Such 2917 objects may be considered sensitive or vulnerable in some network 2918 environments. The support for SET operations in a non-secure 2919 environment without proper protection can have a negative effect on 2920 network operations. 2922 No managed objects in this MIB contain sensitive information. 2924 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 2926 SNMPv1 by itself is not a secure environment. Even if the network 2927 itself is secure (for example by using IPSec), even then, there is no 2928 control as to who on the secure network is allowed to access and 2929 GET/SET (read/change/create/delete) the objects in this MIB. 2931 It is recommended that the implementors consider the security 2932 features as provided by the SNMPv3 framework. Specifically, the use 2933 of the User-based Security Model RFC 2574 [12] and the View- 2934 based Access Control Model (VACM) RFC 2575 [15] is recommended. 2936 It is then a customer/user responsibility to ensure that the SNMP 2937 entity giving access to an instance of this MIB, is properly 2938 configured to give access to the objects only to those principals 2939 (users) that have legitimate rights to indeed GET or SET 2940 (change/create/delete) them. 2942 It should be noted that interface indices in this MIB are maintained 2943 persistently. VACM data relating to these should be stored 2944 persistently. 2946 8. Acknowledgments 2948 The authors are deeply grateful to the authors of the ADSL LINE MIB 2949 (RFC 2662 [23]), Gregory Bathrick and Faye Ly, as much of the text 2950 and structure of this document originates in their documents. 2952 The authors are also grateful to the authors of FR MFR MIB (RFC 3020 2953 [24]), Prayson Pate, Bob Lynch, and Kenneth Rehbehn, as the entirety 2954 of the Security Considerations section was lifted from their document. 2956 The authors also acknowledge the importance of contributions and 2957 suggestions regarding interface indexing structures received from 2958 David Horton of CITR. 2960 Other contributions were received from the following: 2962 Philip Bergstresser (Adtran) 2964 Steve Blackwell (Centillium) 2966 Umberto Bonollo (NEC Australia) 2968 Mark Johnson (Red Point) 2970 Sharon Mantin (Orckit) 2972 Moti Morgenstern (ECI) 2974 Raymond Murphy (Ericsson) 2976 Lee Nipper (Verilink) 2978 Katy Sherman (Orckit) 2980 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 2982 Mike Sneed (ECI) 2984 Jon Turney (DSL Solutions) 2986 Aron Wahl (Memotec) 2988 Michael Wrobel (Memotec) 2990 9. References 2992 [1] Harrington, D., Presuhn, R., and Wijnen, B., "An Architecture 2993 for Describing SNMP Management Frameworks", RFC 2571, April 1999. 2995 [2] Rose, M., and McCloghrie, K., "Structure and Identification of 2996 Management Information for TCP/IP-based Internets", STD 16, RFC 2997 1155, May 1990. 2999 [3] Rose, M., and McCloghrie, K., "Concise MIB Definitions", STD 16, 3000 RFC 1212, March 1991. 3002 [4] Rose, M., "A Convention for Defining Traps for use with the 3003 SNMP", RFC 1215, March 1991. 3005 [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 3006 M., and Waldbusser, S., "Structure of Management Information Version 3007 2 (SMIv2)", STD 58, RFC 2578, April 1999. 3009 [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 3010 M., and Waldbusser, S., "Textual Conventions for SMIv2", STD 58, 3011 RFC 2579, April 1999. 3013 [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 3014 M., and Waldbusser, S., "Conformance Statements for SMIv2", STD 58, 3015 RFC 2580, April 1999. 3017 [8] Case, J., Fedor, M., Schoffstall, M., and Davin, J., "Simple 3018 Network Management Protocol", STD 15, RFC 1157, May 1990. 3020 [9] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., 3021 "Introduction to Community-based SNMPv2", RFC 1901, January 1996. 3023 [10] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., 3024 "Transport Mappings for Version 2 of the Simple Network Management 3025 Protocol (SNMPv2)", RFC 1906, January 1996. 3027 [11] Case, J., Harrington D., Presuhn, R., and Wijnen, B., "Message 3028 Processing and Dispatching for the Simple Network Management 3029 Protocol (SNMP)", RFC 2572, April 1999. 3031 [12] Blumenthal, U., and Wijnen, B., "User-based Security Model (USM) 3032 for version 3 of the Simple Network Management Protocol (SNMPv3)", 3033 RFC 2574, April 1999. 3035 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 3037 [13] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., 3038 "Protocol Operations for Version 2 of the Simple Network Management 3039 Protocol (SNMPv2)", RFC 1905, January 1996. 3041 [14] Levi, D., Meyer, P., and Stewart, B., "SNMPv3 Applications", 3042 RFC 2573, April 1999. 3044 [15] Wijnen, B., Presuhn, R., and McCloghrie, K., "View-based Access 3045 Control Model (VACM) for the Simple Network Management Protocol 3046 (SNMP)", RFC 2575, April 1999. 3048 [16] Case, J., Mundy, R., Partain, D., and Stewart, B., "Introduction 3049 to Version 3 of the Internet-standard Network Management Framework", 3050 RFC 2570, April 1999. 3052 [17] Bradner, S., "Key Words for use in RFCs to Indicate Requirement 3053 Levels", RFC 2119, March 1997. 3055 [18] American National Standards Institute, ANSI T1E1.4/2000-006, 3056 February 2000. 3058 [19] Blackwell, S., Editor, "Single-Pair High-Speed Digital 3059 Subscriber Line (SHDSL) Transceivers", ITU-T Draft G.991.2, April 3060 2000. 3062 [20] McCloghrie, K., and Rose, M., Editors, "Management Information 3063 Base for Network Management of TCP/IP-based internets: MIB-II", STD 3064 17, RFC 1213, March 1991. 3066 [21] McCloghrie, K., and Kastenholz, F., "The Interfaces Group MIB", 3067 RFC 2863, June 2000. 3069 [22] Tesink, K., "Textual Conventions for MIB Modules Using 3070 Performance History Based on 15 Minute Intervals", RFC 2493, January 3071 1999. 3073 [23] Bathrick, G., Ly, F., "Definitions of Managed Objects for the 3074 ADSL Lines", RFC 2662, August 1999. 3076 [24] Pate, P., Lynch, B., Rehbehn, K., "Definitions of Managed 3077 Objects for Monitoring and Controlling the UNI/NNI Multilink Frame 3078 Relay Function", RFC 3020, December 2000. 3080 10. Intellectual Property Notice 3082 The IETF takes no position regarding the validity or scope of any 3083 intellectual property or other rights that might be claimed to 3084 pertain to the implementation or use of the technology described in 3085 this document or the extent to which any license under such rights 3086 might or might not be available; neither does it represent that it 3087 has made any effort to identify any such rights. Information on the 3088 IETF's procedures with respect to rights in standards-track and 3090 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 3092 standards-related documentation can be found in BCP-11. Copies of 3093 claims of rights made available for publication and any assurances of 3094 licenses to be made available, or the result of an attempt made to 3095 obtain a general license or permission for the use of such 3096 proprietary rights by implementors or users of this specification can 3097 be obtained from the IETF Secretariat. 3099 The IETF invites any interested party to bring to its attention any 3100 copyrights, patents or patent applications, or other proprietary 3101 rights which may cover technology that may be required to practice 3102 this standard. Please address the information to the IETF Executive 3103 Director. 3105 11. Authors' Addresses 3107 Rajesh Abbi 3108 Alcatel USA 3109 2912 Wake Forest Road 3110 Raleigh, NC 27609-7860 USA 3111 Tel: +1 919-850-6194 3112 Fax: +1 919-850-6670 3113 E-mail: Rajesh.Abbi@usa.alcatel.com 3115 Bob Ray 3116 Verilink Corporation 3117 950 Explorer Blvd 3118 Huntsville, AL 35806 USA 3119 Tel: +1 256-327-2380 3120 Fax: +1 256-327-2880 3121 E-mail: bray@verilink.com 3123 12. Full Copyright Statement 3125 Copyright (C) The Internet Society (2001). All Rights Reserved. 3127 This document and translations of it may be copied and furnished to 3128 others, and derivative works that comment on or otherwise explain it 3129 or assist in its implementation may be prepared, copied, published 3130 and distributed, in whole or in part, without restriction of any 3131 kind, provided that the above copyright notice and this paragraph are 3132 included on all such copies and derivative works. However, this 3133 document itself may not be modified in any way, such as by removing 3134 the copyright notice or references to the Internet Society or other 3135 Internet organizations, except as needed for the purpose of 3136 developing Internet standards in which case the procedures for 3137 copyrights defined in the Internet Standards process must be 3138 followed, or as required to translate it into languages other than 3139 English. 3141 The limited permissions granted above are perpetual and will not be 3142 revoked by the Internet Society or its successors or assigns. 3143 This document and the information contained herein is provided on an 3144 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 3146 RFC XXXX HDSL2-SHDSL-LINE MIB July 2001 3148 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 3149 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 3150 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 3151 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.