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