idnits 2.17.1 draft-ietf-adslmib-gshdslbis-11.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 19. -- Found old boilerplate from RFC 3978, Section 5.5 on line 3536. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 3508. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 3515. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 3521. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to 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 : ---------------------------------------------------------------------------- == There are 1 instance of lines with non-RFC2606-compliant FQDNs in the document. -- The abstract seems to indicate that this document obsoletes RFC3276, but the header doesn't have an 'Obsoletes:' line to match this. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- 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 (May 26, 2005) is 6872 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) -- Possible downref: Non-RFC (?) normative reference: ref. 'G.991.2' -- Obsolete informational reference (is this intentional?): RFC 3276 (Obsoleted by RFC 4319) Summary: 3 errors (**), 0 flaws (~~), 4 warnings (==), 10 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group C. Sikes 3 Internet-Draft Paradyne Networks, Inc. 4 Expires: November 27, 2005 B. Ray 5 PESA Switching Systems, Inc. 6 R. Abbi 7 Alcatel USA 8 May 26, 2005 10 Definitions of Managed Objects for High Bit-Rate DSL - 2nd generation 11 (HDSL2) and Single-Pair High-Speed Digital Subscriber Line (SHDSL) Lines 12 draft-ietf-adslmib-gshdslbis-11.txt 14 Status of this Memo 16 By submitting this Internet-Draft, each author represents that any 17 applicable patent or other IPR claims of which he or she is aware 18 have been or will be disclosed, and any of which he or she becomes 19 aware will be disclosed, in accordance with Section 6 of BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF), its areas, and its working groups. Note that 23 other groups may also distribute working documents as Internet- 24 Drafts. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 The list of current Internet-Drafts can be accessed at 32 http://www.ietf.org/ietf/1id-abstracts.txt. 34 The list of Internet-Draft Shadow Directories can be accessed at 35 http://www.ietf.org/shadow.html. 37 This Internet-Draft will expire on November 27, 2005. 39 Copyright Notice 41 Copyright (C) The Internet Society (2005). 43 Abstract 45 This document defines a Management Information Base (MIB) module for 46 use with network management protocols in the Internet community. In 47 particular, it describes objects used for managing High Bit-Rate 48 Digital Subscriber Line (DSL) - 2nd generation (HDSL2) and Single- 49 Pair High-Speed Digital Subscriber Line (SHDSL) interfaces. This 50 document introduces extensions to several objects and textual 51 conventions defined in HDSL2-SHDSL-Line MIB (RFC 3276). This 52 document obsoletes RFC 3276. 54 Table of Contents 56 1. The Internet-Standard Management Framework . . . . . . . . . . 3 57 2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 58 2.1 Relationship to other MIBs . . . . . . . . . . . . . . . . 3 59 2.2 IANA Considerations . . . . . . . . . . . . . . . . . . . 5 60 2.3 Conventions used in the MIB Module . . . . . . . . . . . . 6 61 2.4 Structure . . . . . . . . . . . . . . . . . . . . . . . . 7 62 2.5 Line Topology . . . . . . . . . . . . . . . . . . . . . . 10 63 2.6 Counters, Interval Buckets and Thresholds . . . . . . . . 11 64 2.7 Profiles . . . . . . . . . . . . . . . . . . . . . . . . . 11 65 2.8 Notifications . . . . . . . . . . . . . . . . . . . . . . 12 66 3. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 14 67 4. Implementation Analysis . . . . . . . . . . . . . . . . . . . 66 68 5. Security Considerations . . . . . . . . . . . . . . . . . . . 67 69 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 71 70 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 72 71 7.1 Normative References . . . . . . . . . . . . . . . . . . . 72 72 7.2 Informative References . . . . . . . . . . . . . . . . . . 73 73 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 74 74 Intellectual Property and Copyright Statements . . . . . . . . 75 76 1. The Internet-Standard Management Framework 78 For a detailed overview of the documents that describe the current 79 Internet-Standard Management Framework, please refer to Section 7 of 80 RFC 3410 [RFC3410]. 82 Managed objects are accessed via a virtual information store, termed 83 the Management Information Base or MIB. MIB objects are generally 84 accessed through the Simple Network Management Protocol (SNMP). 85 Objects in the MIB are defined using the mechanisms defined in the 86 Structure of Management Information (SMI). This memo specifies a MIB 87 module that is compliant to the SMIv2, which is described in STD 58, 88 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 89 [RFC2580]. 91 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 92 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 93 document are to be interpreted as described in RFC 2119 [RFC2119]. 95 2. Overview 97 This document defines a Management Information Base (MIB) module for 98 use with network management protocols in the Internet community for 99 the purpose of managing HDSL2/SHDSL Lines. 101 The MIB module described in RFC 3276 [RFC3276] describes objects used 102 for managing High Bit-Rate DSL - 2nd generation (HDSL2) [T1E1.4] and 103 Single-Pair High-Speed Digital Subscriber Line (SHDSL) interfaces 104 [G.991.2]. These object descriptions are based upon the 105 specifications for the HDSL2 and SHDSL Embedded Operations Channel 106 (EOC) as defined in American National Standards Institute (ANSI) 107 T1E1.4/2000-006 [T1E1.4] and International Telecommunication Union 108 (ITU) G.991.2 [G.991.2]. 110 This document obsoletes RFC 3276 [RFC3276] which supports G.shdsl in 111 that the MIB module described herein supports G.shdsl.bis as 112 described in the G.991.2 [G.991.2]. In addition, objects have been 113 added to improve the management of SHDSL lines. 115 The MIB module is located in the MIB tree under MIB 2 transmission, 116 as discussed in the MIB-2 Integration (RFC 2863 [RFC2863]) section of 117 this document. 119 2.1 Relationship to other MIBs 121 This section outlines the relationship of this MIB module with other 122 MIB modules described in RFCs. Specifically, IF-MIB as presented in 123 RFC 2863 [RFC2863] is discussed. 125 2.1.1 General IF-MIB Integration (RFC 2863) 127 The HDSL2/SHDSL Line MIB specifies the detailed attributes of a data 128 interface. As such, it needs to integrate with RFC 2863 [RFC2863]. 129 The IANA has assigned the following ifTypes to HDSL2 and SHDSL: 131 IANAifType ::= TEXTUAL-CONVENTION 132 ... 133 SYNTAX INTEGER { 134 ... 135 hdsl2 (168), -- High Bit-Rate DSL, 2nd generation 136 shdsl (169), -- Multirate HDSL2 137 ... 138 } 140 Note that the ifFixedLengthGroup from RFC 2863 [RFC2863] MUST be 141 supported and that the ifRcvAddressGroup does not apply to this MIB 142 module. 144 2.1.2 Usage of ifTable 146 The MIB branch identified by this ifType contains tables appropriate 147 for this interface type. Most such tables extend the ifEntry table, 148 and are indexed by ifIndex. For interfaces in systems implementing 149 this MIB module, those table entries indexed by ifIndex MUST be 150 persistent. 152 The following attributes are part of the mandatory 153 ifGeneralInformationGroup in RFC 2863 [RFC2863], and are not 154 duplicated in the HDSL2/SHDSL Line MIB. 156 =================================================================== 158 ifIndex Interface index. 160 ifDescr See interfaces MIB [RFC2863]. 162 ifType hdsl2(168) or shdsl(169). 164 ifSpeed Set as appropriate. 165 (This is fixed at 1552000 for HDSL2 166 lines) 168 ifPhysAddress This object MUST have an octet string 169 with zero length. 171 ifAdminStatus See interfaces MIB [RFC2863]. 173 ifOperStatus See interfaces MIB [RFC2863]. 175 ifLastChange See interfaces MIB [RFC2863]. 177 ifName See interfaces MIB [RFC2863]. 179 ifAlias See interfaces MIB [RFC2863]. 181 ifLinkUpDownTrapEnable Default to enabled(1). 183 ifHighSpeed Set as appropriate. 184 (For HDSL2 lines, this is fixed at 2) 186 ifConnectorPresent Set as appropriate. 188 =================================================================== 189 Figure 1: Use of ifTable Objects 191 2.2 IANA Considerations 193 The HDSL2-SHDSL-LINE-MIB module requires the allocation of a single 194 object identifier for its MODULE-IDENTITY. The IANA has allocated 195 this object identifier in the transmission subtree (48), defined in 196 the SNMPv2-SMI MIB module. 198 The assignment was in fact done when RFC 3276 was published, and this 199 revision of the RFC does not require any new action from IANA. 201 2.3 Conventions used in the MIB Module 203 2.3.1 Naming Conventions 205 A. xtuC refers to a central site terminal unit; 206 H2TU-C for HDSL2, or STU-C for SHDSL. 207 B. xtuR refers to a remote site terminal unit; 208 H2TU-R for HDSL2, or STU-R for SHDSL. 209 C. xtu refers to a terminal unit; either an xtuC or xtuR. 210 D. xru refer to a regenerator unit; 211 H2RU for HDSL2, or SRU for SHDSL. 212 E. xU refers to any HDSL2/SHDSL unit; either an xtu or xru. 213 F. CRC is cyclic redundancy check [G.991.2]. 214 G. ES means errored second [G.991.2]. 215 J. LOSW means loss of sync word [G.991.2]. 216 I. LOSWS means LOSW seconds [G.991.2]. 217 J. SES means severely errored second [G.991.2]. 218 K. SNR means signal-to-noise ratio [G.991.2]. 219 L. UAS means unavailable second [G.991.2]. 221 2.3.2 Textual Conventions 223 The following textual conventions are defined to reflect the line 224 topology in the MIB module (further discussed in the following 225 section) and to define the behavior of the statistics to be 226 maintained by an agent. 228 o Hdsl2ShdslUnitId: 230 Attributes with this syntax uniquely identify each unit in a 231 HDSL2/SHDSL span. It mirrors the EOC addressing mechanism: 233 xtuC(1) - central office (CO) terminal unit 234 xtuR(2) - customer premises equipment (CPE) 235 terminal unit 236 xru1(3) .. xru8(10) - regenerators, numbered from 237 central office side 239 o Hdsl2ShdslUnitSide: 241 Attributes with this syntax reference the two sides of a unit: 243 networkSide(1) - N in figure 2, below 244 customerSide(2) - C in figure 2, below 246 o Hdsl2ShdslWirePair: 248 Attributes with this syntax reference the wire pairs connecting 249 the units: 251 wirePair1(1) - First pair for HDSL2/SHDSL. 252 wirePair2(2) - Optional second pair for SHDSL only. 253 wirePair3(3) - Optional third pair for SHDSL.bis only. 254 wirePair4(4) - Optional fourth pair for SHDSL.bis only. 256 o Hdsl2ShdslTransmissionModeType: 258 Attributes with this syntax specify the regional setting for a 259 SHDSL line. Specified as a BITS construct, the two mode types 260 are: 262 region1 - ITU-T G.991.2 Annex A 263 region2 - ITU-T G.991.2 Annex B 265 o Hdsl2ShdslPerfCurrDayCount: 267 Attributes with this syntax define the behavior of the 1-day (24 268 hour) gauges found in the MIB module. 270 o Hdsl2Shdsl1DayIntervalCount: 272 Attributes with this syntax define the behavior of the 1-day (24 273 hour) interval counters found in the MIB module. 275 o Hdsl2ShdslPerfTimeElapsed: 277 Attributes with this syntax define the behavior of the elapsed 278 time counters found in the MIB module. 280 o Hdsl2ShdslPerfIntervalThreshold: 282 Attributes with this syntax define the behavior of the alarm 283 thresholds found in the MIB module. 285 o Hdsl2ShdslClockReferenceType: 287 Attributes with this syntax define the clock references for the 288 HDSL2/SHDSL span. 290 2.4 Structure 292 The MIB module is structured into following MIB groups: 294 o Span Configuration Group: 296 This group supports MIB objects for configuring parameters for the 297 HDSL2/SHDSL span. It contains the following table: 299 - hdsl2ShdslSpanConfTable 301 o Span Status Group: 303 This group supports MIB objects for retrieving span status 304 information. It contains the following table: 306 - hdsl2ShdslSpanStatusTable 308 o Unit Inventory Group: 310 This group supports MIB objects for retrieving unit inventory 311 information about units in HDSL2/SHDSL lines via the EOC. It 312 contains the following table: 314 - hdsl2ShdslInventoryTable 316 o Segment Endpoint Configuration Group: 318 This group supports MIB objects for configuring parameters for the 319 HDSL2/SHDSL segment endpoints. It contains the following table: 321 - hdsl2ShdslEndpointConfTable 323 o Segment Endpoint Current Status/Performance Group: 325 This group supports MIB objects that provide the current status/ 326 performance information relating to segment endpoints. It 327 contains the following table: 329 - hdsl2ShdslEndpointCurrTable 331 o Segment Endpoint 15-Minute Interval Status/Performance Group: 333 This group supports MIB objects that provide historic status/ 334 performance information relating to segment endpoints in 15-minute 335 intervals. It contains the following table: 337 - hdsl2Shdsl15MinIntervalTable 339 o Segment Endpoint 1-Day Interval Status/Performance Group: 341 This group supports MIB objects that provide historic status/ 342 performance information relating to segment endpoints in 1-day 343 intervals. It contains the following table: 345 - hdsl2Shdsl1DayIntervalTable 347 o Maintenance Group: 349 This group supports MIB objects for performing maintenance 350 operations such as loopbacks for HDSL2/SHDSL lines. It contains 351 the following table(s): 353 - hdsl2ShdslEndpointMaintTable 354 - hdsl2ShdslUnitMaintTable 356 o Span Configuration Profile Group: 358 This group supports MIB objects for defining configuration 359 profiles for HDSL2/SHDSL Spans. It contains the following table: 361 - hdsl2ShdslSpanConfProfileTable 363 o Segment Endpoint Alarm Configuration Profile Group: 365 This group supports MIB objects for defining alarm configuration 366 profiles for HDSL2/SHDSL Segment Endpoints. It contains the 367 following table: 369 - hdsl2ShdslEndpointAlarmConfProfileTable 371 o Notifications Group: 373 This group defines the notifications supported for HDSL2/SHDSL 374 lines: 376 - hdsl2ShdslLoopAttenCrossing 377 - hdsl2ShdslSNRMarginCrossing 378 - hdsl2ShdslPerfESThresh 379 - hdsl2ShdslPerfSESThresh 380 - hdsl2ShdslPerfCRCanomaliesThresh 381 - hdsl2ShdslPerfLOSWSThresh 382 - hdsl2ShdslPerfUASThresh 383 - hdsl2ShdslSpanInvalidNumRepeaters 384 - hdsl2ShdslLoopbackFailure 385 - hdsl2ShdslpowerBackoff 386 - hdsl2ShdsldeviceFault 387 - hdsl2ShdsldcContinuityFault 388 - hdsl2ShdslconfigInitFailure 389 - hdsl2ShdslprotocolInitFailure 390 - hdsl2ShdslnoNeighborPresent 391 - hdsl2ShdslLocalPowerLoss 393 o SHDSL Wire Pair Group: 395 This group supports MIB objects which provide status of the SHDSL- 396 specific wire pairs. 398 - hdsl2ShdslEndpointCurrTipRingReversal 399 - hdsl2ShdslEndpointCurrActivationState 401 o Payload Group: 403 This group supports MIB objects for retrieving payload rates which 404 excludes any framing overhead. 406 - hdsl2ShdslStatusMaxAttainablePayloadRate 407 - hdsl2ShdslStatusActualPayloadRate 409 2.5 Line Topology 411 An HDSL2/SHDSL Line consists of a minimum of two units - xtuC (the 412 central termination unit) and an xtuR (the remote termination unit). 413 The line may optionally support up to 8 repeater/regenerator units 414 (xru) as shown in the figure below. 416 <-- Network Side Customer Side --> 418 || 420 <~~~> <~~~> HDSL2/SHDSL Segments <~~~> 422 +-------+ +-------+ +-------+ +-------+ +-------+ 423 + C=1=N C=1=N C=..1..=N C=1=N + 424 | xtuC | | xru1 | | xru2 | | xru8 | | xtuR | 425 + C=2=N C=2=N C=..2..=N C=2=N + 426 +-------+ +-------+ +-------+ +-------+ +-------+ 428 Key: HDSL2/SHDSL Span 429 <~~~~> HDSL2/SHDSL Segment 430 =1= HDSL2/SHDSL wire-pair-1 431 =2= SHDSL optional wire-pair-2 (Not applicable to HDSL2) 432 C Customer Side Segment Endpoint (modem) 433 N Network Side Segment Endpoint (modem) 435 Figure 2: General topology for an HDSL2/SHDSL Line 437 2.6 Counters, Interval Buckets and Thresholds 439 For SNR Margin, Loop Attenuation, ES, SES, CRC anomalies, LOSW, and 440 UAS, there are event counters, current 15-minute and 0 to 96 15- 441 minute history bucket(s) of "interval-counters", as well as current 442 and 0 to 30 previous 1-day interval-counter(s). Each current 15- 443 minute event bucket has an associated threshold notification. 445 Unlike RFC 3593 [RFC3593] and RFC 2662 [RFC2662], there is no 446 representation in the MIB module for invalid buckets. In those cases 447 where the data for an interval is suspect or known to be invalid, the 448 agent MUST NOT report the interval. If the current 15-minute event 449 bucket is determined to be invalid, notifications based upon the 450 value of the event bucket MUST NOT be generated. 452 Not reporting an interval will result in holes in the associated 453 table. For example, the table, hdsl2Shdsl15MinIntervalTable, is 454 indexed by { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide, 455 hdsl2ShdslEndpointWirePair, hdsl2Shdsl15MinIntervalNumber}. If 456 interval 12 is determined to be invalid but intervals 11 and 13 are 457 valid, a Get Next operation on the indices .1.1.1.1.11 would return 458 indices .1.1.1.1.13. 460 There is no requirement for an agent to ensure a fixed relationship 461 between the start of a fifteen minute interval and any wall clock; 462 however some implementations may align the fifteen minute intervals 463 with quarter hours. Likewise, an implementation may choose to align 464 one day intervals with the start of a day. 466 Counters are not reset when an xU is reinitialized, only when the 467 agent is reset or reinitialized (or under specific request outside 468 the scope of this MIB module). 470 2.7 Profiles 472 As a managed node can handle a large number of xUs, (e.g., hundreds 473 or perhaps thousands of lines), provisioning every parameter on every 474 xU may become burdensome. Moreover, most lines are provisioned 475 identically with the same set of parameters. To simplify the 476 provisioning process, this MIB module makes use of profiles. A 477 profile is a set of parameters that can be shared by multiple lines 478 using the same configuration. 480 The following profiles are used in this MIB module: 482 o Span Configuration Profiles - Span configuration profiles contain 483 parameters for configuring HDSL2/SHDSL spans. They are defined in 484 the hdsl2ShdslSpanConfProfileTable. Since span configuration 485 parameters are only applicable for SHDSL, the support for span 486 configuration profiles are optional for HDSL2 interfaces. 488 Note that the configuration of the span dictates the behavior for 489 each individual segment endpoint in the span. If a different 490 configuration is provisioned for any given segment endpoint within 491 the span, the new configuration for this segment endpoint will 492 override the span configuration for this segment endpoint only. 494 o Segment Endpoint Alarm Configuration Profiles - These profiles 495 contain parameters for configuring alarm thresholds for HDSL2/ 496 SHDSL segment endpoints. These profiles are defined in the 497 hdsl2ShdslEndpointAlarmConfProfileTable. 499 The index value for this profile is a locally-unique 500 administratively assigned name for the profile having the textual 501 convention 'SnmpAdminString' (RFC 3411 [RFC3411]). 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 506 of this profile. If a change is made to the profile, all lines that 507 refer to it will be reconfigured to the changed parameters. Before a 508 profile can be deleted or taken out of service it must be first 509 unreferenced 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 513 be vendor specific unless otherwise indicated in this document. 514 Before a line's profiles have been set, these profiles will be 515 automatically used by setting hdsl2ShdslEndpointAlarmConfProfile and 516 hdsl2ShdslSpanConfProfile to 'DEFVAL' where appropriate. This 517 default profile name, 'DEFVAL', is considered reserved in the context 518 of profiles defined in this MIB module. 520 Profiles are created, assigned, and deleted dynamically using the 521 profile name and profile row status in each of the four profile 522 tables. 524 Profile changes MUST take effect immediately. These changes MAY 525 result in a restart (hard reset or soft restart) of the units on the 526 line. 528 2.8 Notifications 530 The ability to generate the SNMP notifications coldStart/WarmStart 531 (per [RFC3418]) which are per agent (e.g., per Digital Subscriber 532 Line Access Multiplexer, or DSLAM, in such a device), and linkUp/ 533 linkDown (per [RFC2863]) which are per interface (i.e., HDSL2/SHDSL 534 line) is required. 536 A linkDown notification MAY be generated whenever any of ES, SES, CRC 537 Anomaly, LOSW, or UAS event occurs. The corresponding linkUp 538 notification MAY be sent when all link failure conditions are 539 cleared. 541 The notifications defined in this MIB module are for initialization 542 failure and for the threshold crossings associated with the following 543 events: ES, SES, CRC Anomaly, LOSW, and UAS. Each threshold has its 544 own enable/threshold value. When that value is 0, the notification 545 is disabled. 547 The hdsl2ShdslEndpointCurrStatus is a bitmask representing all 548 outstanding error conditions associated with a particular Segment 549 Endpoint. Note that since status of remote endpoints is obtained via 550 the EOC, this information may be unavailable for units that are 551 unreachable via EOC during a line error condition. Therefore, not 552 all conditions may always be included in its current status. 553 Notifications corresponding to the bit fields in this object are 554 defined. 556 Two alarm conditions, SNR Margin Alarm and Loop Attenuation Alarm, 557 are organized in a manner slightly different from that implied in the 558 EOC specifications. In the MIB module, these alarm conditions are 559 tied to the two thresholds hdsl2ShdslEndpointThreshSNRMargin and 560 hdsl2ShdslEndpointThreshLoopAttenuation found in the 561 hdsl2ShdslEndpointAlarmConfProfileTable. In the EOC, the alarm 562 conditions associated with these thresholds are per-unit. In the MIB 563 module, these alarm conditions are per-endpoint. For terminal units, 564 this has no impact. For repeaters, this implies an implementation 565 variance where the agent in the terminal unit is responsible for 566 detecting a threshold crossing. As the reporting of a repeater 567 detected alarm condition to the polling terminal unit occurs in the 568 same EOC message as the reporting of the current SNR Margin and Loop 569 Attenuation values, it is anticipated that this will have very little 570 impact on agent implementation. 572 A threshold notification occurs whenever the corresponding current 573 15-minute interval error counter becomes equal to, or exceeds the 574 threshold value. Only one notification SHOULD be sent per interval 575 per interface. Since the current 15-minute counter is reset to 0 576 every 15 minutes, and if the condition persists, the notification may 577 recur as often as every 15 minutes. For example, to get a 578 notification whenever a "loss of" event occurs (but at most once 579 every 15 minutes), set the corresponding threshold to 1. The agent 580 will generate a notification when the event originally occurs. 582 Notifications, other than the threshold notifications listed above, 583 SHOULD be rate limited (throttled) such that there is at least a one- 584 minute gap between the generation of consecutive notification of the 585 same event. When notifications are rate limited, they are dropped 586 and not queued for sending at a future time. This is intended to be 587 a general rate-limiting statement for notifications that have no 588 explicit rate limiting assertions in this document otherwise. 590 Note that the Network Management System, or NMS, may receive a 591 linkDown notification, as well, if enabled (via 592 ifLinkUpDownTrapEnable [RFC2863]). At the beginning of the next 15 593 minute interval, the counter is reset. When the first second goes by 594 and the event occurs, the current interval bucket will be 1, which 595 equals the threshold, and the notification will be sent again. 597 A hdsl2ShdslSpanInvalidNumRepeaters notification may be generated 598 following completion of the discovery phase if the number of 599 repeaters discovered on the line differs from the number of repeaters 600 specified in hdsl2ShdslSpanConfNumRepeaters. For those conditions 601 where the number of provisioned repeaters is greater than those 602 encountered during span discovery, all table entries associated with 603 the nonexistent repeaters are to be discarded. For those conditions 604 where the number of provisioned repeaters is less than those 605 encountered during span discovery, additional table entries are to be 606 created using the default span configuration profile. 608 3. Definitions 610 HDSL2-SHDSL-LINE-MIB DEFINITIONS ::= BEGIN 612 IMPORTS 613 MODULE-IDENTITY, 614 OBJECT-TYPE, 615 Counter32, 616 Unsigned32, 617 Gauge32, 618 NOTIFICATION-TYPE, 619 Integer32, 620 transmission 621 FROM SNMPv2-SMI 622 RowStatus, 623 TEXTUAL-CONVENTION 624 FROM SNMPv2-TC 625 ifIndex 626 FROM IF-MIB 627 PerfCurrentCount, 628 PerfIntervalCount 629 FROM PerfHist-TC-MIB 631 SnmpAdminString 632 FROM SNMP-FRAMEWORK-MIB 633 MODULE-COMPLIANCE, 634 OBJECT-GROUP, 635 NOTIFICATION-GROUP 636 FROM SNMPv2-CONF; 638 hdsl2ShdslMIB MODULE-IDENTITY 639 LAST-UPDATED "200505260000Z" -- May 26, 2005 640 ORGANIZATION "ADSLMIB Working Group" 641 CONTACT-INFO "WG-email: adslmib@ietf.org 642 WG-URL: 643 http://www.ietf.org/html.charters/adslmib-charter.html 644 Info: https://www1.ietf.org/mailman/listinfo/adslmib 645 Chair: Mike Sneed 646 Postal: P.O. Box 37324 647 Raleigh NC 27627-7324 USA 648 Email: sneedmike@hotmail.com 650 Co-Chair Bob Ray 651 PESA Switching Systems, Inc. 652 Postal 330-A Wynn Drive 653 Huntsville, AL 35805 USA 654 Phone +1 256 726 9200 ext. 142 656 Co-editor: Clay Sikes 657 Paradyne Networks, Inc. 658 Postal: 8545 126th Ave. N. 659 Largo, FL 33772 USA 660 Email: csikes@paradyne.com 661 Phone: +1 727 530 8257 663 Co-editor: Bob Ray 664 PESA Switching Systems, Inc. 665 Postal: 330-A Wynn Drive 666 Huntsville, AL 35805 USA 667 Email: rray@pesa.com 668 Phone: +1 256 726 9200 ext. 142 670 Co-editor: Rajesh Abbi 671 Alcatel USA 672 Postal: 2912 Wake Forest Road 673 Raleigh, NC 27609-7860 USA 675 Email: Rajesh.Abbi@alcatel.com 676 Phone: +1 919 850 6194" 678 DESCRIPTION 679 "This MIB module defines a collection of objects for managing 680 HDSL2/SHDSL lines. An agent may reside at either end of the 681 line, however the MIB module is designed to require no 682 management communication between the modems beyond that 683 inherent in the low-level EOC line protocol as defined in 684 ANSI T1E1.4/2000-006 (for HDSL2 lines), or in ITU G.991.2 685 (for SHDSL lines). 687 Copyright (C) The Internet Society (2005). This version of 688 this MIB module is part of RFC xxxx; see the RFC itself for 689 full legal notices." 691 REVISION "200505260000Z" -- May 26, 2005 692 DESCRIPTION "This version, published as RFC xxxx. 693 The following changes have been made in this version: 694 1. Added a 3rd and 4th wire pair. 695 2. Modified all rates such that their rates are only 696 constrained by an unsigned 32-bit value and not by 697 what today's perceived technology limitations are. 698 3. Clarified that the rates from RFC 3276 include 699 payload and any applicable framing and added 700 objects for payload-only rates. 701 4. Added an object to indicate whether or not the 702 tip and ring are reversed on a wire pair. 703 5. Added an object to display the activation state 704 of a wire pair. 705 6. Added references as necessary for clarification. 706 7. Added display hints to textual conventions as 707 necessary. 708 8. Updated conformance statements as necessary. 709 9. Some changes were due to IETF requirements and 710 RFC generation tools." 712 REVISION "200205090000Z" -- May 9, 2002 713 DESCRIPTION "Initial version, published as RFC 3276." 715 ::= { transmission 48 } 717 hdsl2ShdslMibObjects OBJECT IDENTIFIER ::= { hdsl2ShdslMIB 1 } 719 -- Textual Conventions used in this MIB module 720 -- 722 Hdsl2ShdslPerfCurrDayCount ::= TEXTUAL-CONVENTION 723 DISPLAY-HINT "d" 724 STATUS current 725 DESCRIPTION 726 "A gauge associated with interface performance measurements in 727 a current 1-day (24 hour) measurement interval. 729 The value of this gauge starts at zero at the beginning of an 730 interval and is increased when associated events occur, until 731 the end of the 1-day interval. At that time the value of the 732 gauge is stored in the previous 1-day history interval, as 733 defined in a companion object of type 734 Hdsl2Shdsl1DayIntevalCount, and the current interval gauge 735 is restarted at zero. 737 In the case where the agent has no valid data available for 738 this interval the corresponding object instance is not 739 available and upon a retrieval request a corresponding error 740 message shall be returned to indicate that this instance does 741 not exist. Please note that zero is a valid value." 742 SYNTAX Gauge32 744 Hdsl2Shdsl1DayIntervalCount ::= TEXTUAL-CONVENTION 745 DISPLAY-HINT "d" 746 STATUS current 747 DESCRIPTION 748 "A counter associated with interface performance measurements 749 during the most previous 1-day (24 hour) measurement interval. 750 The value of this gauge is equal to the value of the current 751 day gauge, as defined in a companion object of type 752 Hdsl2ShdslPerfCurrDayCount, at the end of its most recent 753 interval. 755 In the case where the agent has no valid data available for 756 this interval the corresponding object instance is not 757 available and upon a retrieval request a corresponding error 758 message shall be returned to indicate that this instance does 759 not exist." 760 SYNTAX Gauge32 762 Hdsl2ShdslPerfTimeElapsed ::= TEXTUAL-CONVENTION 763 DISPLAY-HINT "d" 764 STATUS current 765 DESCRIPTION 766 "The number of seconds that have elapsed since the beginning of 767 the current measurement period. If, for some reason, such as 768 an adjustment in the system's time-of-day clock or the addition 769 of a leap second, the current interval exceeds the maximum 770 value, the agent will return the maximum value. 772 For 15 minute intervals, the range is limited to (0..899). 773 For 24 hour intervals, the range is limited to (0..86399)." 774 SYNTAX Unsigned32(0..86399) 776 Hdsl2ShdslPerfIntervalThreshold ::= TEXTUAL-CONVENTION 777 DISPLAY-HINT "d" 778 STATUS current 779 DESCRIPTION 780 "This convention defines a range of values that may be set in 781 a fault threshold alarm control. As the number of seconds in 782 a 15-minute interval numbers at most 900, objects of this type 783 may have a range of 0...900, where the value of 0 disables the 784 alarm." 785 SYNTAX Unsigned32(0..900) 787 Hdsl2ShdslUnitId ::= TEXTUAL-CONVENTION 788 STATUS current 789 DESCRIPTION 790 "This is the unique identification for all units in a 791 HDSL2/SHDSL Span. It is based on the EOC unit addressing 792 scheme with reference to the xtuC." 793 SYNTAX INTEGER 794 { 795 xtuC(1), 796 xtuR(2), 797 xru1(3), 798 xru2(4), 799 xru3(5), 800 xru4(6), 801 xru5(7), 802 xru6(8), 803 xru7(9), 804 xru8(10) 805 } 807 Hdsl2ShdslUnitSide ::= TEXTUAL-CONVENTION 808 STATUS current 809 DESCRIPTION 810 "This is the referenced side of a HDSL2/SHDSL unit - Network 811 or Customer side. The side facing the Network is the Network 812 side, while the side facing the Customer is the Customer side." 813 SYNTAX INTEGER 814 { 815 networkSide(1), 816 customerSide(2) 817 } 819 Hdsl2ShdslWirePair ::= TEXTUAL-CONVENTION 820 STATUS current 821 DESCRIPTION 822 "This is the referenced pair of wires in a HDSL2/SHDSL Segment. 823 HDSL2 only supports a single pair (wirePair1 or two wire), 824 SHDSL lines support an optional second pair (wirePair2 or four 825 wire), and G.shdsl.bis support an optional third pair 826 (wirePair3 or six wire) and an optional fourth pair 827 (wirePair4 or eight wire)." 828 SYNTAX INTEGER 829 { 830 wirePair1(1), -- two wire 831 wirePair2(2), -- four wire 832 wirePair3(3), -- six wire 833 wirePair4(4) -- eight wire 834 } 836 Hdsl2ShdslTransmissionModeType ::= TEXTUAL-CONVENTION 837 STATUS current 838 DESCRIPTION 839 "Contains the regional setting of the HDSL2/SHDSL span, 840 represented as a bit-map of possible settings. The various 841 bit positions are: 843 Bit Meaning Description 844 1 region 1 Indicates ITU-T G.991.2 Annex A. 845 2 region 2 Indicates ITU-T G.991.2 Annex B." 846 SYNTAX BITS 847 { 848 region1(0), 849 region2(1) 850 } 852 Hdsl2ShdslClockReferenceType ::= TEXTUAL-CONVENTION 853 STATUS current 854 DESCRIPTION 855 "The various STU-C symbol clock references for the 856 HDSL2/SHDSL span, represented as an enumeration." 857 SYNTAX INTEGER 858 { 859 localClk(1), -- Mode-1 per G991.2 860 networkClk(2), -- Mode-2 per G991.2 861 dataOrNetworkClk(3), -- Mode-3a per G991.2 862 dataClk(4) -- Mode-3b per G991.2 863 } 865 -- Span Configuration Group 866 -- 868 hdsl2ShdslSpanConfTable OBJECT-TYPE 869 SYNTAX SEQUENCE OF Hdsl2ShdslSpanConfEntry 870 MAX-ACCESS not-accessible 871 STATUS current 872 DESCRIPTION 873 "This table supports overall configuration of HDSL2/SHDSL 874 Spans. Entries in this table MUST be maintained in a 875 persistent manner." 876 ::= { hdsl2ShdslMibObjects 1 } 878 hdsl2ShdslSpanConfEntry OBJECT-TYPE 879 SYNTAX Hdsl2ShdslSpanConfEntry 880 MAX-ACCESS not-accessible 881 STATUS current 882 DESCRIPTION 883 "An entry in the hdsl2ShdslSpanConfTable. Each entry 884 represents the complete Span in a single HDSL2/SHDSL line. 885 It is indexed by the ifIndex of the associated HDSL2/SHDSL 886 line." 887 INDEX { ifIndex } 888 ::= { hdsl2ShdslSpanConfTable 1 } 890 Hdsl2ShdslSpanConfEntry ::= 891 SEQUENCE 892 { 893 hdsl2ShdslSpanConfNumRepeaters Unsigned32, 894 hdsl2ShdslSpanConfProfile SnmpAdminString, 895 hdsl2ShdslSpanConfAlarmProfile SnmpAdminString 896 } 898 hdsl2ShdslSpanConfNumRepeaters OBJECT-TYPE 899 SYNTAX Unsigned32(0..8) 900 UNITS "repeaters" 901 MAX-ACCESS read-write 902 STATUS current 903 DESCRIPTION 904 "This object provisions the number of repeaters/regenerators 905 in this HDSL2/SHDSL Span." 906 ::= { hdsl2ShdslSpanConfEntry 1 } 908 hdsl2ShdslSpanConfProfile OBJECT-TYPE 909 SYNTAX SnmpAdminString (SIZE(1..32)) 910 MAX-ACCESS read-write 911 STATUS current 912 DESCRIPTION 913 "This object is a pointer to a span configuration profile in 914 the hdsl2ShdslSpanConfProfileTable, which applies to this 915 span. The value of this object is the index of the referenced 916 profile in the hdsl2ShdslSpanConfProfileTable. Note that span 917 configuration profiles are only applicable to SHDSL lines. 919 HDSL2 lines MUST reference the default profile, 'DEFVAL'. 921 By default, this object will have the value 'DEFVAL' 922 (the index of the default profile). 924 Any attempt to set this object to a value that is not the value 925 of the index for an active entry in the profile table, 926 hdsl2ShdslSpanConfProfileTable, MUST be rejected." 927 ::= { hdsl2ShdslSpanConfEntry 2 } 929 hdsl2ShdslSpanConfAlarmProfile OBJECT-TYPE 930 SYNTAX SnmpAdminString (SIZE(1..32)) 931 MAX-ACCESS read-write 932 STATUS current 933 DESCRIPTION 934 "This object is a pointer to an Alarm configuration profile in 935 the hdsl2ShdslEndpointAlarmConfProfileTable. The value of 936 this object is the index of the referenced profile in the 937 hdsl2ShdslEndpointAlarmConfProfileTable. The alarm 938 threshold configuration in the referenced profile will be 939 used by default for all segment endpoints in this span. 940 Individual endpoints may override this profile by explicitly 941 specifying some other profile in the 942 hdsl2ShdslEndpointConfTable. By default, this object will 943 have the value 'DEFVAL' (the index of the default 944 profile). 946 Any attempt to set this object to a value that is not the value 947 of the index for an active entry in the profile table, 948 hdsl2ShdslEndpointAlarmConfProfileTable, MUST be rejected." 949 ::= { hdsl2ShdslSpanConfEntry 3 } 951 -- Span Status Group 952 -- 954 hdsl2ShdslSpanStatusTable OBJECT-TYPE 955 SYNTAX SEQUENCE OF Hdsl2ShdslSpanStatusEntry 956 MAX-ACCESS not-accessible 957 STATUS current 958 DESCRIPTION 959 "This table provides overall status information of 960 HDSL2/SHDSL spans. This table contains live data from 961 equipment. As such, it is NOT persistent." 962 ::= { hdsl2ShdslMibObjects 2 } 964 hdsl2ShdslSpanStatusEntry OBJECT-TYPE 965 SYNTAX Hdsl2ShdslSpanStatusEntry 966 MAX-ACCESS not-accessible 967 STATUS current 968 DESCRIPTION 969 "An entry in the hdsl2ShdslSpanStatusTable. Each entry 970 represents the complete span in a single HDSL2/SHDSL line. 971 It is indexed by the ifIndex of the associated HDSL2/SHDSL 972 line." 973 INDEX { ifIndex } 974 ::= { hdsl2ShdslSpanStatusTable 1 } 976 Hdsl2ShdslSpanStatusEntry ::= 977 SEQUENCE 978 { 979 hdsl2ShdslStatusNumAvailRepeaters Unsigned32, 980 hdsl2ShdslStatusMaxAttainableLineRate Unsigned32, 981 hdsl2ShdslStatusActualLineRate Unsigned32, 982 hdsl2ShdslStatusTransmissionModeCurrent 983 Hdsl2ShdslTransmissionModeType, 984 hdsl2ShdslStatusMaxAttainablePayloadRate Unsigned32, 985 hdsl2ShdslStatusActualPayloadRate Unsigned32 986 } 988 hdsl2ShdslStatusNumAvailRepeaters OBJECT-TYPE 989 SYNTAX Unsigned32(0..8) 990 MAX-ACCESS read-only 991 STATUS current 992 DESCRIPTION 993 "Contains the actual number of repeaters/regenerators 994 discovered in this HDSL2/SHDSL span." 995 ::= { hdsl2ShdslSpanStatusEntry 1 } 997 hdsl2ShdslStatusMaxAttainableLineRate OBJECT-TYPE 998 SYNTAX Unsigned32(0..4294967295) 999 UNITS "bps" 1000 MAX-ACCESS read-only 1001 STATUS current 1002 DESCRIPTION 1003 "Contains the maximum attainable line rate in this HDSL2/SHDSL 1004 span. This object provides the maximum rate the line is 1005 capable of achieving. This is based upon measurements made 1006 during line probing. This rate includes payload (user data) 1007 and any applicable framing overhead." 1008 ::= { hdsl2ShdslSpanStatusEntry 2 } 1010 hdsl2ShdslStatusActualLineRate OBJECT-TYPE 1011 SYNTAX Unsigned32(0..4294967295) 1012 UNITS "bps" 1013 MAX-ACCESS read-only 1014 STATUS current 1015 DESCRIPTION 1016 "Contains the actual line rate in this HDSL2/SHDSL span. This 1017 SHOULD equal ifSpeed. This rate includes payload (user data) 1018 and any applicable framing overhead" 1019 ::= { hdsl2ShdslSpanStatusEntry 3 } 1021 hdsl2ShdslStatusTransmissionModeCurrent OBJECT-TYPE 1022 SYNTAX Hdsl2ShdslTransmissionModeType 1023 MAX-ACCESS read-only 1024 STATUS current 1025 DESCRIPTION 1026 "Contains the current Power Spectral Density (PSD) regional 1027 setting of the HDSL2/SHDSL span." 1028 ::= { hdsl2ShdslSpanStatusEntry 4 } 1030 hdsl2ShdslStatusMaxAttainablePayloadRate OBJECT-TYPE 1031 SYNTAX Unsigned32(0..4294967295) 1032 UNITS "bps" 1033 MAX-ACCESS read-only 1034 STATUS current 1035 DESCRIPTION 1036 "Contains the maximum attainable payload (user data) 1037 line rate in this HDSL2/SHDSL span. This object provides 1038 the maximum rate the line is capable of achieving. This 1039 is based upon measurements made during line probing. Any 1040 framing overhead is not included." 1041 ::= { hdsl2ShdslSpanStatusEntry 5 } 1043 hdsl2ShdslStatusActualPayloadRate OBJECT-TYPE 1044 SYNTAX Unsigned32(0..4294967295) 1045 UNITS "bps" 1046 MAX-ACCESS read-only 1047 STATUS current 1048 DESCRIPTION 1049 "Contains the actual line rate in this HDSL2/SHDSL span. Any 1050 framing overhead is not included." 1051 ::= { hdsl2ShdslSpanStatusEntry 6 } 1053 -- Unit Inventory Group 1054 -- 1056 hdsl2ShdslInventoryTable OBJECT-TYPE 1057 SYNTAX SEQUENCE OF Hdsl2ShdslInventoryEntry 1058 MAX-ACCESS not-accessible 1059 STATUS current 1060 DESCRIPTION 1061 "This table supports retrieval of unit inventory information 1062 available via the EOC from units in a HDSL2/SHDSL line. 1064 Entries in this table are dynamically created during the 1065 line discovery process. The life cycle for these entries 1066 is as follows: 1068 - xtu discovers a device, either a far-end xtu or an xru 1069 - an inventory table entry is created for the device 1070 - the line goes down for whatever reason 1071 - inventory table entries for unreachable devices are 1072 destroyed. 1074 As these entries are created/destroyed dynamically, they 1075 are NOT persistent." 1076 ::= { hdsl2ShdslMibObjects 3 } 1078 hdsl2ShdslInventoryEntry OBJECT-TYPE 1079 SYNTAX Hdsl2ShdslInventoryEntry 1080 MAX-ACCESS not-accessible 1081 STATUS current 1082 DESCRIPTION 1083 "An entry in the hdsl2ShdslInventoryTable. Each entry 1084 represents inventory information for a single unit in a 1085 HDSL2/SHDSL line. It is indexed by the ifIndex of the 1086 HDSL2/SHDSL line and the Hdsl2ShdslUnitId of the 1087 associated unit." 1088 INDEX { ifIndex, hdsl2ShdslInvIndex } 1089 ::= { hdsl2ShdslInventoryTable 1 } 1091 Hdsl2ShdslInventoryEntry ::= 1092 SEQUENCE 1093 { 1094 hdsl2ShdslInvIndex Hdsl2ShdslUnitId, 1095 hdsl2ShdslInvVendorID OCTET STRING, 1096 hdsl2ShdslInvVendorModelNumber OCTET STRING, 1097 hdsl2ShdslInvVendorSerialNumber OCTET STRING, 1098 hdsl2ShdslInvVendorEOCSoftwareVersion Integer32, 1099 hdsl2ShdslInvStandardVersion Integer32, 1100 hdsl2ShdslInvVendorListNumber OCTET STRING, 1101 hdsl2ShdslInvVendorIssueNumber OCTET STRING, 1102 hdsl2ShdslInvVendorSoftwareVersion OCTET STRING, 1103 hdsl2ShdslInvEquipmentCode OCTET STRING, 1104 hdsl2ShdslInvVendorOther OCTET STRING, 1105 hdsl2ShdslInvTransmissionModeCapability 1106 Hdsl2ShdslTransmissionModeType 1107 } 1109 hdsl2ShdslInvIndex OBJECT-TYPE 1110 SYNTAX Hdsl2ShdslUnitId 1111 MAX-ACCESS not-accessible 1112 STATUS current 1113 DESCRIPTION 1114 "Each entry in this table corresponds to a physical element 1115 in a HDSL2/SHDSL Span. It is based on the EOC unit addressing 1116 scheme with reference to the xtuC." 1117 ::= { hdsl2ShdslInventoryEntry 1 } 1119 hdsl2ShdslInvVendorID OBJECT-TYPE 1120 SYNTAX OCTET STRING(SIZE(8)) 1121 MAX-ACCESS read-only 1122 STATUS current 1123 DESCRIPTION 1124 "Vendor ID as reported in an Inventory Response message." 1125 REFERENCE 1126 "G.991.2, Section 9.5.5.7.4, Inventory response - Message ID 1127 130, Octets 25-32." 1128 ::= { hdsl2ShdslInventoryEntry 2 } 1130 hdsl2ShdslInvVendorModelNumber OBJECT-TYPE 1131 SYNTAX OCTET STRING(SIZE(12)) 1132 MAX-ACCESS read-only 1133 STATUS current 1134 DESCRIPTION 1135 "Vendor model number as reported in an Inventory Response 1136 message." 1137 REFERENCE 1138 "G.991.2, Section 9.5.5.7.4, Inventory response - Message ID 1139 130, Octets 33-44." 1140 ::= { hdsl2ShdslInventoryEntry 3 } 1142 hdsl2ShdslInvVendorSerialNumber OBJECT-TYPE 1143 SYNTAX OCTET STRING(SIZE(12)) 1144 MAX-ACCESS read-only 1145 STATUS current 1146 DESCRIPTION 1147 "Vendor serial number as reported in an Inventory Response 1148 message." 1149 REFERENCE 1150 "G.991.2, Section 9.5.5.7.4, Inventory response - Message ID 1151 130, Octets 45-56." 1152 ::= { hdsl2ShdslInventoryEntry 4 } 1154 hdsl2ShdslInvVendorEOCSoftwareVersion OBJECT-TYPE 1155 SYNTAX Integer32 1156 MAX-ACCESS read-only 1157 STATUS current 1158 DESCRIPTION 1159 "Vendor EOC version as reported in a Discovery Response 1160 message." 1162 REFERENCE 1163 "G.991.2, Section 9.5.5.7.2, Discovery response - Message ID 1164 130, Octet 12." 1165 ::= { hdsl2ShdslInventoryEntry 5 } 1167 hdsl2ShdslInvStandardVersion OBJECT-TYPE 1168 SYNTAX Integer32 1169 MAX-ACCESS read-only 1170 STATUS current 1171 DESCRIPTION 1172 "Version of the HDSL2/SHDSL standard implemented, as reported 1173 in an Inventory Response message." 1174 REFERENCE 1175 "G.991.2, Section 9.5.5.7.4, Inventory response - Message ID 1176 130, Octet 2." 1177 ::= { hdsl2ShdslInventoryEntry 6 } 1179 hdsl2ShdslInvVendorListNumber OBJECT-TYPE 1180 SYNTAX OCTET STRING(SIZE(3)) 1181 MAX-ACCESS read-only 1182 STATUS current 1183 DESCRIPTION 1184 "Vendor list number as reported in an Inventory Response 1185 message." 1186 REFERENCE 1187 "G.991.2, Section 9.5.5.7.4, Inventory response - Message ID 1188 130, Octets 3-5." 1189 ::= { hdsl2ShdslInventoryEntry 7 } 1191 hdsl2ShdslInvVendorIssueNumber OBJECT-TYPE 1192 SYNTAX OCTET STRING(SIZE(2)) 1193 MAX-ACCESS read-only 1194 STATUS current 1195 DESCRIPTION 1196 "Vendor issue number as reported in an Inventory Response 1197 message." 1198 REFERENCE 1199 "G.991.2, Section 9.5.5.7.4, Inventory response - Message ID 1200 130, Octets 6-7." 1201 ::= { hdsl2ShdslInventoryEntry 8 } 1203 hdsl2ShdslInvVendorSoftwareVersion OBJECT-TYPE 1204 SYNTAX OCTET STRING(SIZE(6)) 1205 MAX-ACCESS read-only 1206 STATUS current 1207 DESCRIPTION 1208 "Vendor software version as reported in an Inventory Response 1209 message." 1211 REFERENCE 1212 "G.991.2, Section 9.5.5.7.4, Inventory response - Message ID 1213 130, Octets 8-13." 1214 ::= { hdsl2ShdslInventoryEntry 9 } 1216 hdsl2ShdslInvEquipmentCode OBJECT-TYPE 1217 SYNTAX OCTET STRING(SIZE(10)) 1218 MAX-ACCESS read-only 1219 STATUS current 1220 DESCRIPTION 1221 "Equipment code conforming to ANSI T1.213, Coded Identification 1222 of Equipment Entities." 1223 REFERENCE 1224 "G.991.2, Section 9.5.5.7.4, Inventory response - Message ID 1225 130, Octets 14-23." 1226 ::= { hdsl2ShdslInventoryEntry 10 } 1228 hdsl2ShdslInvVendorOther OBJECT-TYPE 1229 SYNTAX OCTET STRING(SIZE(12)) 1230 MAX-ACCESS read-only 1231 STATUS current 1232 DESCRIPTION 1233 "Other vendor information as reported in an Inventory Response 1234 message." 1235 REFERENCE 1236 "G.991.2, Section 9.5.5.7.4, Inventory response - Message ID 1237 130, Octets 57-68." 1238 ::= { hdsl2ShdslInventoryEntry 11 } 1240 hdsl2ShdslInvTransmissionModeCapability OBJECT-TYPE 1241 SYNTAX Hdsl2ShdslTransmissionModeType 1242 MAX-ACCESS read-only 1243 STATUS current 1244 DESCRIPTION 1245 "Contains the transmission mode capability of the SHDSL unit." 1246 ::= { hdsl2ShdslInventoryEntry 12 } 1248 -- Segment Endpoint Configuration Group 1249 -- 1251 hdsl2ShdslEndpointConfTable OBJECT-TYPE 1252 SYNTAX SEQUENCE OF Hdsl2ShdslEndpointConfEntry 1253 MAX-ACCESS not-accessible 1254 STATUS current 1255 DESCRIPTION 1256 "This table supports configuration parameters for segment 1257 endpoints in a HDSL2/SHDSL line. As this table is indexed 1258 by ifIndex, it MUST be maintained in a persistent manner." 1260 ::= { hdsl2ShdslMibObjects 4 } 1262 hdsl2ShdslEndpointConfEntry OBJECT-TYPE 1263 SYNTAX Hdsl2ShdslEndpointConfEntry 1264 MAX-ACCESS not-accessible 1265 STATUS current 1266 DESCRIPTION 1267 "An entry in the hdsl2ShdslEndpointConfTable. Each entry 1268 represents a single segment endpoint in a HDSL2/SHDSL line. 1269 It is indexed by the ifIndex of the HDSL2/SHDSL line, the 1270 UnitId of the associated unit, the side of the unit, and the 1271 wire pair of the associated modem." 1272 INDEX { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide, 1273 hdsl2ShdslEndpointWirePair} 1274 ::= { hdsl2ShdslEndpointConfTable 1 } 1276 Hdsl2ShdslEndpointConfEntry ::= 1277 SEQUENCE 1278 { 1279 hdsl2ShdslEndpointSide Hdsl2ShdslUnitSide, 1280 hdsl2ShdslEndpointWirePair Hdsl2ShdslWirePair, 1281 hdsl2ShdslEndpointAlarmConfProfile SnmpAdminString 1282 } 1284 hdsl2ShdslEndpointSide OBJECT-TYPE 1285 SYNTAX Hdsl2ShdslUnitSide 1286 MAX-ACCESS not-accessible 1287 STATUS current 1288 DESCRIPTION 1289 "The side of the unit associated with this segment endpoint - 1290 Network/Customer side - as per the Hdsl2ShdslUnitSide textual 1291 convention." 1292 ::= { hdsl2ShdslEndpointConfEntry 1 } 1294 hdsl2ShdslEndpointWirePair OBJECT-TYPE 1295 SYNTAX Hdsl2ShdslWirePair 1296 MAX-ACCESS not-accessible 1297 STATUS current 1298 DESCRIPTION 1299 "The wire pair of the modem associated with this segment 1300 endpoint as per the Hdsl2ShdslWirePair textual convention." 1301 ::= { hdsl2ShdslEndpointConfEntry 2 } 1303 hdsl2ShdslEndpointAlarmConfProfile OBJECT-TYPE 1304 SYNTAX SnmpAdminString (SIZE(0..32)) 1305 MAX-ACCESS read-write 1306 STATUS current 1307 DESCRIPTION 1308 "This object configures the alarm threshold values to be used 1309 for this segment endpoint. The values are obtained from the 1310 alarm configuration profile referenced by this object. The 1311 value of this object is the index of the referenced profile in 1312 the hdsl2ShdslEndpointAlarmConfProfileTable, or NULL (a 1313 zero-length SnmpAdminString). If the value is a zero-length 1314 SnmpAdminString, the endpoint uses the default Alarm 1315 Configuration Profile for the associated span as per the 1316 hdsl2ShdslSpanConfAlarmProfile object in the 1317 hdsl2ShdslSpanConfTable. The default value of this object is 1318 a zero-length SnmpAdminString. 1320 Any attempt to set this object to a value that is not the value 1321 of the index for an active entry in the profile table, 1322 hdsl2ShdslEndpointAlarmConfProfileTable, MUST be rejected." 1323 ::= { hdsl2ShdslEndpointConfEntry 3 } 1325 -- Segment Endpoint Current Status/Performance Group 1326 -- 1328 hdsl2ShdslEndpointCurrTable OBJECT-TYPE 1329 SYNTAX SEQUENCE OF Hdsl2ShdslEndpointCurrEntry 1330 MAX-ACCESS not-accessible 1331 STATUS current 1332 DESCRIPTION 1333 "This table contains current status and performance information 1334 for segment endpoints in HDSL2/SHDSL Lines. As with other 1335 tables in this MIB module indexed by ifIndex, entries in this 1336 table MUST be maintained in a persistent manner." 1337 ::= { hdsl2ShdslMibObjects 5 } 1339 hdsl2ShdslEndpointCurrEntry OBJECT-TYPE 1340 SYNTAX Hdsl2ShdslEndpointCurrEntry 1341 MAX-ACCESS not-accessible 1342 STATUS current 1343 DESCRIPTION 1344 "An entry in the hdsl2ShdslEndpointCurrTable. Each entry 1345 contains status and performance information relating to a 1346 single segment endpoint. It is indexed by the ifIndex of the 1347 HDSL2/SHDSL line, the UnitId of the associated unit, the side 1348 of the unit, and the wire pair of the associated modem." 1349 INDEX { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide, 1350 hdsl2ShdslEndpointWirePair } 1351 ::= { hdsl2ShdslEndpointCurrTable 1 } 1353 Hdsl2ShdslEndpointCurrEntry ::= 1354 SEQUENCE 1355 { 1356 hdsl2ShdslEndpointCurrAtn Integer32, 1357 hdsl2ShdslEndpointCurrSnrMgn Integer32, 1358 hdsl2ShdslEndpointCurrStatus BITS, 1359 hdsl2ShdslEndpointES Counter32, 1360 hdsl2ShdslEndpointSES Counter32, 1361 hdsl2ShdslEndpointCRCanomalies Counter32, 1362 hdsl2ShdslEndpointLOSWS Counter32, 1363 hdsl2ShdslEndpointUAS Counter32, 1364 hdsl2ShdslEndpointCurr15MinTimeElapsed 1365 Hdsl2ShdslPerfTimeElapsed, 1366 hdsl2ShdslEndpointCurr15MinES PerfCurrentCount, 1367 hdsl2ShdslEndpointCurr15MinSES PerfCurrentCount, 1368 hdsl2ShdslEndpointCurr15MinCRCanomalies PerfCurrentCount, 1369 hdsl2ShdslEndpointCurr15MinLOSWS PerfCurrentCount, 1370 hdsl2ShdslEndpointCurr15MinUAS PerfCurrentCount, 1371 hdsl2ShdslEndpointCurr1DayTimeElapsed 1372 Hdsl2ShdslPerfTimeElapsed, 1373 hdsl2ShdslEndpointCurr1DayES 1374 Hdsl2ShdslPerfCurrDayCount, 1375 hdsl2ShdslEndpointCurr1DaySES 1376 Hdsl2ShdslPerfCurrDayCount, 1377 hdsl2ShdslEndpointCurr1DayCRCanomalies 1378 Hdsl2ShdslPerfCurrDayCount, 1379 hdsl2ShdslEndpointCurr1DayLOSWS 1380 Hdsl2ShdslPerfCurrDayCount, 1381 hdsl2ShdslEndpointCurr1DayUAS 1382 Hdsl2ShdslPerfCurrDayCount, 1383 hdsl2ShdslEndpointCurrTipRingReversal INTEGER, 1384 hdsl2ShdslEndpointCurrActivationState INTEGER 1385 } 1387 hdsl2ShdslEndpointCurrAtn OBJECT-TYPE 1388 SYNTAX Integer32(-127..128) 1389 UNITS "dB" 1390 MAX-ACCESS read-only 1391 STATUS current 1392 DESCRIPTION 1393 "The current loop attenuation for this endpoint as reported in 1394 a Network or Customer Side Performance Status message." 1395 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1396 ::= { hdsl2ShdslEndpointCurrEntry 1 } 1398 hdsl2ShdslEndpointCurrSnrMgn OBJECT-TYPE 1399 SYNTAX Integer32(-127..128) 1400 UNITS "dB" 1401 MAX-ACCESS read-only 1402 STATUS current 1403 DESCRIPTION 1404 "The current SNR margin for this endpoint as reported in a 1405 Status Response/SNR message." 1406 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1407 ::= { hdsl2ShdslEndpointCurrEntry 2 } 1409 hdsl2ShdslEndpointCurrStatus OBJECT-TYPE 1410 SYNTAX BITS 1411 { 1412 noDefect(0), 1413 powerBackoff(1), 1414 deviceFault(2), 1415 dcContinuityFault(3), 1416 snrMarginAlarm(4), 1417 loopAttenuationAlarm(5), 1418 loswFailureAlarm(6), 1419 configInitFailure(7), 1420 protocolInitFailure(8), 1421 noNeighborPresent(9), 1422 loopbackActive(10) 1423 } 1424 MAX-ACCESS read-only 1425 STATUS current 1426 DESCRIPTION 1427 "Contains the current state of the endpoint. This is a 1428 bit-map of possible conditions. The various bit positions 1429 are: 1431 noDefect There are no defects on the line. 1433 powerBackoff Indicates enhanced Power Backoff. 1435 deviceFault Indicates a vendor-dependent 1436 diagnostic or self-test fault 1437 has been detected. 1439 dcContinuityFault Indicates vendor-dependent 1440 conditions that interfere with 1441 span powering such as short and 1442 open circuits. 1444 snrMarginAlarm Indicates that the SNR margin 1445 has dropped below the alarm threshold. 1447 loopAttenuationAlarm Indicates that the loop attenuation 1448 exceeds the alarm threshold. 1450 loswFailureAlarm Indicates a forward LOSW alarm. 1452 configInitFailure Endpoint failure during initialization 1453 due to paired endpoint not able to 1454 support requested configuration. 1456 protocolInitFailure Endpoint failure during initialization 1457 due to incompatible protocol used by 1458 the paired endpoint. 1460 noNeighborPresent Endpoint failure during initialization 1461 due to no activation sequence detected 1462 from paired endpoint. 1464 loopbackActive A loopback is currently active at this 1465 Segment Endpoint. 1467 This is intended to supplement ifOperStatus. Note that there 1468 is a 1:1 relationship between the status bits defined in this 1469 object and the notification thresholds defined elsewhere in 1470 this MIB module." 1471 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1472 ::= { hdsl2ShdslEndpointCurrEntry 3 } 1474 hdsl2ShdslEndpointES OBJECT-TYPE 1475 SYNTAX Counter32 1476 UNITS "seconds" 1477 MAX-ACCESS read-only 1478 STATUS current 1479 DESCRIPTION 1480 "Count of Errored Seconds (ES) on this endpoint since the xU 1481 was last restarted." 1482 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1483 ::= { hdsl2ShdslEndpointCurrEntry 4 } 1485 hdsl2ShdslEndpointSES OBJECT-TYPE 1486 SYNTAX Counter32 1487 UNITS "seconds" 1488 MAX-ACCESS read-only 1489 STATUS current 1490 DESCRIPTION 1491 "Count of Severely Errored Seconds (SES) on this endpoint 1492 since the xU was last restarted." 1493 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1494 ::= { hdsl2ShdslEndpointCurrEntry 5 } 1496 hdsl2ShdslEndpointCRCanomalies OBJECT-TYPE 1497 SYNTAX Counter32 1498 UNITS "detected CRC Anomalies" 1499 MAX-ACCESS read-only 1500 STATUS current 1501 DESCRIPTION 1502 "Count of CRC anomalies on this endpoint since the xU was 1503 last restarted." 1504 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1505 ::= { hdsl2ShdslEndpointCurrEntry 6 } 1507 hdsl2ShdslEndpointLOSWS OBJECT-TYPE 1508 SYNTAX Counter32 1509 UNITS "seconds" 1510 MAX-ACCESS read-only 1511 STATUS current 1512 DESCRIPTION 1513 "Count of Loss of Sync Word (LOSW) Seconds on this endpoint 1514 since the xU was last restarted." 1515 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1516 ::= { hdsl2ShdslEndpointCurrEntry 7 } 1518 hdsl2ShdslEndpointUAS OBJECT-TYPE 1519 SYNTAX Counter32 1520 UNITS "seconds" 1521 MAX-ACCESS read-only 1522 STATUS current 1523 DESCRIPTION 1524 "Count of Unavailable Seconds (UAS) on this endpoint since 1525 the xU was last restarted." 1526 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1527 ::= { hdsl2ShdslEndpointCurrEntry 8 } 1529 hdsl2ShdslEndpointCurr15MinTimeElapsed OBJECT-TYPE 1530 SYNTAX Hdsl2ShdslPerfTimeElapsed 1531 UNITS "seconds" 1532 MAX-ACCESS read-only 1533 STATUS current 1534 DESCRIPTION 1535 "Total elapsed seconds in the current 15-minute interval." 1536 ::= { hdsl2ShdslEndpointCurrEntry 9 } 1538 hdsl2ShdslEndpointCurr15MinES OBJECT-TYPE 1539 SYNTAX PerfCurrentCount 1540 UNITS "seconds" 1541 MAX-ACCESS read-only 1542 STATUS current 1543 DESCRIPTION 1544 "Count of Errored Seconds (ES) in the current 15-minute 1545 interval." 1546 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1547 ::= { hdsl2ShdslEndpointCurrEntry 10 } 1549 hdsl2ShdslEndpointCurr15MinSES OBJECT-TYPE 1550 SYNTAX PerfCurrentCount 1551 UNITS "seconds" 1552 MAX-ACCESS read-only 1553 STATUS current 1554 DESCRIPTION 1555 "Count of Severely Errored Seconds (SES) in the current 1556 15-minute interval." 1557 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1558 ::= { hdsl2ShdslEndpointCurrEntry 11 } 1560 hdsl2ShdslEndpointCurr15MinCRCanomalies OBJECT-TYPE 1561 SYNTAX PerfCurrentCount 1562 UNITS "detected CRC Anomalies" 1563 MAX-ACCESS read-only 1564 STATUS current 1565 DESCRIPTION 1566 "Count of CRC anomalies in the current 15-minute interval." 1567 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1568 ::= { hdsl2ShdslEndpointCurrEntry 12 } 1570 hdsl2ShdslEndpointCurr15MinLOSWS OBJECT-TYPE 1571 SYNTAX PerfCurrentCount 1572 UNITS "seconds" 1573 MAX-ACCESS read-only 1574 STATUS current 1575 DESCRIPTION 1576 "Count of Loss of Sync Word (LOSW) Seconds in the current 1577 15-minute interval." 1578 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1579 ::= { hdsl2ShdslEndpointCurrEntry 13 } 1581 hdsl2ShdslEndpointCurr15MinUAS OBJECT-TYPE 1582 SYNTAX PerfCurrentCount 1583 UNITS "seconds" 1584 MAX-ACCESS read-only 1585 STATUS current 1586 DESCRIPTION 1587 "Count of Unavailable Seconds (UAS) in the current 15-minute 1588 interval." 1589 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1590 ::= { hdsl2ShdslEndpointCurrEntry 14 } 1592 hdsl2ShdslEndpointCurr1DayTimeElapsed OBJECT-TYPE 1593 SYNTAX Hdsl2ShdslPerfTimeElapsed 1594 UNITS "seconds" 1595 MAX-ACCESS read-only 1596 STATUS current 1597 DESCRIPTION 1598 "Number of seconds that have elapsed since the beginning of 1599 the current 1-day interval." 1600 ::= { hdsl2ShdslEndpointCurrEntry 15 } 1602 hdsl2ShdslEndpointCurr1DayES OBJECT-TYPE 1603 SYNTAX Hdsl2ShdslPerfCurrDayCount 1604 UNITS "seconds" 1605 MAX-ACCESS read-only 1606 STATUS current 1607 DESCRIPTION 1608 "Count of Errored Seconds (ES) during the current day as 1609 measured by hdsl2ShdslEndpointCurr1DayTimeElapsed." 1610 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1611 ::= { hdsl2ShdslEndpointCurrEntry 16 } 1613 hdsl2ShdslEndpointCurr1DaySES OBJECT-TYPE 1614 SYNTAX Hdsl2ShdslPerfCurrDayCount 1615 UNITS "seconds" 1616 MAX-ACCESS read-only 1617 STATUS current 1618 DESCRIPTION 1619 "Count of Severely Errored Seconds (SES) during the current 1620 day as measured by hdsl2ShdslEndpointCurr1DayTimeElapsed." 1621 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1622 ::= { hdsl2ShdslEndpointCurrEntry 17 } 1624 hdsl2ShdslEndpointCurr1DayCRCanomalies OBJECT-TYPE 1625 SYNTAX Hdsl2ShdslPerfCurrDayCount 1626 UNITS "detected CRC Anomalies" 1627 MAX-ACCESS read-only 1628 STATUS current 1629 DESCRIPTION 1630 "Count of CRC anomalies during the current day as measured 1631 by hdsl2ShdslEndpointCurr1DayTimeElapsed." 1632 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1633 ::= { hdsl2ShdslEndpointCurrEntry 18 } 1635 hdsl2ShdslEndpointCurr1DayLOSWS OBJECT-TYPE 1636 SYNTAX Hdsl2ShdslPerfCurrDayCount 1637 UNITS "seconds" 1638 MAX-ACCESS read-only 1639 STATUS current 1640 DESCRIPTION 1641 "Count of Loss of Sync Word (LOSW) Seconds during the current 1642 day as measured by hdsl2ShdslEndpointCurr1DayTimeElapsed." 1643 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1644 ::= { hdsl2ShdslEndpointCurrEntry 19 } 1646 hdsl2ShdslEndpointCurr1DayUAS OBJECT-TYPE 1647 SYNTAX Hdsl2ShdslPerfCurrDayCount 1648 UNITS "seconds" 1649 MAX-ACCESS read-only 1650 STATUS current 1651 DESCRIPTION 1652 "Count of Unavailable Seconds (UAS) during the current day as 1653 measured by hdsl2ShdslEndpointCurr1DayTimeElapsed." 1654 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1655 ::= { hdsl2ShdslEndpointCurrEntry 20 } 1657 hdsl2ShdslEndpointCurrTipRingReversal OBJECT-TYPE 1658 SYNTAX INTEGER 1659 { 1660 normal(1), 1661 reversed(2) 1662 } 1663 MAX-ACCESS read-only 1664 STATUS current 1665 DESCRIPTION 1666 "This object indicates the state of the tip/ring for the 1667 wire pair." 1668 ::= { hdsl2ShdslEndpointCurrEntry 21 } 1670 hdsl2ShdslEndpointCurrActivationState OBJECT-TYPE 1671 SYNTAX INTEGER 1672 { 1673 preActivation(1), -- PreTrain 1674 activation(2), -- Training 1675 data(3) -- Trained 1676 } 1677 MAX-ACCESS read-only 1678 STATUS current 1679 DESCRIPTION 1680 "This object indicates the activation or training state of 1681 the wire pair." 1682 REFERENCE "ITU-T G.991.2, Section 6.2 PMD Activation Sequence" 1683 ::= { hdsl2ShdslEndpointCurrEntry 22 } 1685 -- Segment Endpoint 15-Minute Interval Status/Performance Group 1686 -- 1688 hdsl2Shdsl15MinIntervalTable OBJECT-TYPE 1689 SYNTAX SEQUENCE OF Hdsl2Shdsl15MinIntervalEntry 1690 MAX-ACCESS not-accessible 1691 STATUS current 1692 DESCRIPTION 1693 "This table provides one row for each HDSL2/SHDSL endpoint 1694 performance data collection interval. This table contains 1695 live data from equipment. As such, it is NOT persistent." 1696 ::= { hdsl2ShdslMibObjects 6 } 1698 hdsl2Shdsl15MinIntervalEntry OBJECT-TYPE 1699 SYNTAX Hdsl2Shdsl15MinIntervalEntry 1700 MAX-ACCESS not-accessible 1701 STATUS current 1702 DESCRIPTION 1703 "An entry in the hdsl2Shdsl15MinIntervalTable." 1704 INDEX { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide, 1705 hdsl2ShdslEndpointWirePair, hdsl2Shdsl15MinIntervalNumber} 1706 ::= { hdsl2Shdsl15MinIntervalTable 1 } 1708 Hdsl2Shdsl15MinIntervalEntry ::= 1709 SEQUENCE 1710 { 1711 hdsl2Shdsl15MinIntervalNumber Unsigned32, 1712 hdsl2Shdsl15MinIntervalES PerfIntervalCount, 1713 hdsl2Shdsl15MinIntervalSES PerfIntervalCount, 1714 hdsl2Shdsl15MinIntervalCRCanomalies PerfIntervalCount, 1715 hdsl2Shdsl15MinIntervalLOSWS PerfIntervalCount, 1716 hdsl2Shdsl15MinIntervalUAS PerfIntervalCount 1717 } 1719 hdsl2Shdsl15MinIntervalNumber OBJECT-TYPE 1720 SYNTAX Unsigned32(1..96) 1721 MAX-ACCESS not-accessible 1722 STATUS current 1723 DESCRIPTION 1724 "Performance Data Interval number. Interval 1 is the most 1725 recent previous interval; interval 96 is 24 hours ago. 1726 Intervals 2..96 are optional." 1727 ::= { hdsl2Shdsl15MinIntervalEntry 1 } 1729 hdsl2Shdsl15MinIntervalES OBJECT-TYPE 1730 SYNTAX PerfIntervalCount 1731 UNITS "seconds" 1732 MAX-ACCESS read-only 1733 STATUS current 1734 DESCRIPTION 1735 "Count of Errored Seconds (ES) during the interval." 1736 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1737 ::= { hdsl2Shdsl15MinIntervalEntry 2 } 1739 hdsl2Shdsl15MinIntervalSES OBJECT-TYPE 1740 SYNTAX PerfIntervalCount 1741 UNITS "seconds" 1742 MAX-ACCESS read-only 1743 STATUS current 1744 DESCRIPTION 1745 "Count of Severely Errored Seconds (SES) during the interval." 1746 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1747 ::= { hdsl2Shdsl15MinIntervalEntry 3 } 1749 hdsl2Shdsl15MinIntervalCRCanomalies OBJECT-TYPE 1750 SYNTAX PerfIntervalCount 1751 UNITS "detected CRC Anomalies" 1752 MAX-ACCESS read-only 1753 STATUS current 1754 DESCRIPTION 1755 "Count of CRC anomalies during the interval." 1756 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1757 ::= { hdsl2Shdsl15MinIntervalEntry 4 } 1759 hdsl2Shdsl15MinIntervalLOSWS OBJECT-TYPE 1760 SYNTAX PerfIntervalCount 1761 UNITS "seconds" 1762 MAX-ACCESS read-only 1763 STATUS current 1764 DESCRIPTION 1765 "Count of Loss of Sync Word (LOSW) Seconds during the 1766 interval." 1767 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1768 ::= { hdsl2Shdsl15MinIntervalEntry 5 } 1770 hdsl2Shdsl15MinIntervalUAS OBJECT-TYPE 1771 SYNTAX PerfIntervalCount 1772 UNITS "seconds" 1773 MAX-ACCESS read-only 1774 STATUS current 1775 DESCRIPTION 1776 "Count of Unavailable Seconds (UAS) during the interval." 1777 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1778 ::= { hdsl2Shdsl15MinIntervalEntry 6 } 1780 -- Segment Endpoint 1-Day Interval Status/Performance Group 1781 -- 1783 hdsl2Shdsl1DayIntervalTable OBJECT-TYPE 1784 SYNTAX SEQUENCE OF Hdsl2Shdsl1DayIntervalEntry 1785 MAX-ACCESS not-accessible 1786 STATUS current 1787 DESCRIPTION 1788 "This table provides one row for each HDSL2/SHDSL endpoint 1789 performance data collection interval. This table contains 1790 live data from equipment. As such, it is NOT persistent." 1791 ::= { hdsl2ShdslMibObjects 7 } 1793 hdsl2Shdsl1DayIntervalEntry OBJECT-TYPE 1794 SYNTAX Hdsl2Shdsl1DayIntervalEntry 1795 MAX-ACCESS not-accessible 1796 STATUS current 1797 DESCRIPTION 1798 "An entry in the hdsl2Shdsl1DayIntervalTable." 1799 INDEX { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide, 1800 hdsl2ShdslEndpointWirePair, hdsl2Shdsl1DayIntervalNumber } 1801 ::= { hdsl2Shdsl1DayIntervalTable 1 } 1803 Hdsl2Shdsl1DayIntervalEntry ::= 1804 SEQUENCE 1805 { 1806 hdsl2Shdsl1DayIntervalNumber Unsigned32, 1807 hdsl2Shdsl1DayIntervalMoniSecs Hdsl2ShdslPerfTimeElapsed, 1808 hdsl2Shdsl1DayIntervalES Hdsl2Shdsl1DayIntervalCount, 1809 hdsl2Shdsl1DayIntervalSES Hdsl2Shdsl1DayIntervalCount, 1810 hdsl2Shdsl1DayIntervalCRCanomalies Hdsl2Shdsl1DayIntervalCount, 1811 hdsl2Shdsl1DayIntervalLOSWS Hdsl2Shdsl1DayIntervalCount, 1812 hdsl2Shdsl1DayIntervalUAS Hdsl2Shdsl1DayIntervalCount 1813 } 1815 hdsl2Shdsl1DayIntervalNumber OBJECT-TYPE 1816 SYNTAX Unsigned32(1..30) 1817 MAX-ACCESS not-accessible 1818 STATUS current 1819 DESCRIPTION 1820 "History Data Interval number. Interval 1 is the most 1821 recent previous day; interval 30 is 30 days ago. Intervals 1822 2..30 are optional." 1823 ::= { hdsl2Shdsl1DayIntervalEntry 1 } 1825 hdsl2Shdsl1DayIntervalMoniSecs OBJECT-TYPE 1826 SYNTAX Hdsl2ShdslPerfTimeElapsed 1827 UNITS "seconds" 1828 MAX-ACCESS read-only 1829 STATUS current 1830 DESCRIPTION 1831 "The amount of time in the 1-day interval over which the 1832 performance monitoring information is actually counted. 1833 This value will be the same as the interval duration except 1834 in a situation where performance monitoring data could not 1835 be collected for any reason." 1836 ::= { hdsl2Shdsl1DayIntervalEntry 2 } 1838 hdsl2Shdsl1DayIntervalES OBJECT-TYPE 1839 SYNTAX Hdsl2Shdsl1DayIntervalCount 1840 UNITS "seconds" 1841 MAX-ACCESS read-only 1842 STATUS current 1843 DESCRIPTION 1844 "Count of Errored Seconds (ES) during the 1-day interval as 1845 measured by hdsl2Shdsl1DayIntervalMoniSecs." 1846 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1847 ::= { hdsl2Shdsl1DayIntervalEntry 3 } 1849 hdsl2Shdsl1DayIntervalSES OBJECT-TYPE 1850 SYNTAX Hdsl2Shdsl1DayIntervalCount 1851 UNITS "seconds" 1852 MAX-ACCESS read-only 1853 STATUS current 1854 DESCRIPTION 1855 "Count of Severely Errored Seconds (SES) during the 1-day 1856 interval as measured by hdsl2Shdsl1DayIntervalMoniSecs." 1857 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1858 ::= { hdsl2Shdsl1DayIntervalEntry 4 } 1860 hdsl2Shdsl1DayIntervalCRCanomalies OBJECT-TYPE 1861 SYNTAX Hdsl2Shdsl1DayIntervalCount 1862 UNITS "detected CRC Anomalies" 1863 MAX-ACCESS read-only 1864 STATUS current 1865 DESCRIPTION 1866 "Count of CRC anomalies during the 1-day interval as 1867 measured by hdsl2Shdsl1DayIntervalMoniSecs." 1868 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1869 ::= { hdsl2Shdsl1DayIntervalEntry 5 } 1871 hdsl2Shdsl1DayIntervalLOSWS OBJECT-TYPE 1872 SYNTAX Hdsl2Shdsl1DayIntervalCount 1873 UNITS "seconds" 1874 MAX-ACCESS read-only 1875 STATUS current 1876 DESCRIPTION 1877 "Count of Loss of Sync Word (LOSW) Seconds during the 1-day 1878 interval as measured by hdsl2Shdsl1DayIntervalMoniSecs." 1879 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1880 ::= { hdsl2Shdsl1DayIntervalEntry 6 } 1882 hdsl2Shdsl1DayIntervalUAS OBJECT-TYPE 1883 SYNTAX Hdsl2Shdsl1DayIntervalCount 1884 UNITS "seconds" 1885 MAX-ACCESS read-only 1886 STATUS current 1887 DESCRIPTION 1888 "Count of Unavailable Seconds (UAS) during the 1-day interval 1889 as measured by hdsl2Shdsl1DayIntervalMoniSecs." 1890 REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" 1891 ::= { hdsl2Shdsl1DayIntervalEntry 7 } 1893 -- Maintenance Group 1894 -- 1896 hdsl2ShdslEndpointMaintTable OBJECT-TYPE 1897 SYNTAX SEQUENCE OF Hdsl2ShdslEndpointMaintEntry 1898 MAX-ACCESS not-accessible 1899 STATUS current 1900 DESCRIPTION 1901 "This table supports maintenance operations (e.g. loopbacks) 1902 to be performed on HDSL2/SHDSL segment endpoints. This table 1903 contains live data from equipment. As such, it is NOT 1904 persistent." 1905 ::= { hdsl2ShdslMibObjects 8 } 1907 hdsl2ShdslEndpointMaintEntry OBJECT-TYPE 1908 SYNTAX Hdsl2ShdslEndpointMaintEntry 1909 MAX-ACCESS not-accessible 1910 STATUS current 1911 DESCRIPTION 1912 "An entry in the hdsl2ShdslEndpointMaintTable. Each entry 1913 corresponds to a single segment endpoint, and is indexed by the 1914 ifIndex of the HDSL2/SHDSL line, the UnitId of the associated 1915 unit and the side of the unit." 1916 INDEX { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide } 1917 ::= { hdsl2ShdslEndpointMaintTable 1 } 1919 Hdsl2ShdslEndpointMaintEntry ::= 1920 SEQUENCE 1921 { 1922 hdsl2ShdslMaintLoopbackConfig INTEGER, 1923 hdsl2ShdslMaintTipRingReversal INTEGER, 1924 hdsl2ShdslMaintPowerBackOff INTEGER, 1925 hdsl2ShdslMaintSoftRestart INTEGER 1926 } 1928 hdsl2ShdslMaintLoopbackConfig OBJECT-TYPE 1929 SYNTAX INTEGER 1930 { 1931 noLoopback(1), 1932 normalLoopback(2), 1933 specialLoopback(3) 1934 } 1935 MAX-ACCESS read-write 1936 STATUS current 1937 DESCRIPTION 1938 "This object controls configuration of loopbacks for the 1939 associated segment endpoint. The status of the loopback 1940 is obtained via the hdsl2ShdslEndpointCurrStatus object." 1941 ::= { hdsl2ShdslEndpointMaintEntry 1 } 1943 hdsl2ShdslMaintTipRingReversal OBJECT-TYPE 1944 SYNTAX INTEGER 1945 { 1946 normal(1), 1947 reversed(2) 1948 } 1949 MAX-ACCESS read-only 1950 STATUS current 1951 DESCRIPTION 1952 "This object indicates the state of the tip/ring pair at the 1953 associated segment endpoint." 1954 ::= { hdsl2ShdslEndpointMaintEntry 2 } 1956 hdsl2ShdslMaintPowerBackOff OBJECT-TYPE 1957 SYNTAX INTEGER 1958 { 1959 default(1), 1960 enhanced(2) 1961 } 1962 MAX-ACCESS read-write 1963 STATUS current 1964 DESCRIPTION 1965 "This object configures the receiver at the associated 1966 segment endpoint to operate in default or enhanced power 1967 backoff mode." 1968 ::= { hdsl2ShdslEndpointMaintEntry 3 } 1970 hdsl2ShdslMaintSoftRestart OBJECT-TYPE 1971 SYNTAX INTEGER 1972 { 1973 ready(1), 1974 restart(2) 1975 } 1976 MAX-ACCESS read-write 1977 STATUS current 1978 DESCRIPTION 1979 "This object enables the manager to trigger a soft restart 1980 of the modem at the associated segment endpoint. The 1981 manager may only set this object to the 'restart(2)' 1982 value, which initiates a restart. The agent will perform a 1983 restart after approximately 5 seconds. Following the 5 second 1984 period, the agent will restore the object to the 'ready(1)' 1985 state." 1986 ::= { hdsl2ShdslEndpointMaintEntry 4 } 1988 hdsl2ShdslUnitMaintTable OBJECT-TYPE 1989 SYNTAX SEQUENCE OF Hdsl2ShdslUnitMaintEntry 1990 MAX-ACCESS not-accessible 1991 STATUS current 1992 DESCRIPTION 1993 "This table supports maintenance operations for units in a 1994 HDSL2/SHDSL line. Entries in this table MUST be maintained 1995 in a persistent manner." 1996 ::= { hdsl2ShdslMibObjects 9 } 1998 hdsl2ShdslUnitMaintEntry OBJECT-TYPE 1999 SYNTAX Hdsl2ShdslUnitMaintEntry 2000 MAX-ACCESS not-accessible 2001 STATUS current 2002 DESCRIPTION 2003 "An entry in the hdsl2ShdslUnitMaintTable. Each entry 2004 corresponds to a single unit, and is indexed by the 2005 ifIndex of the HDSL2/SHDSL line and the UnitId of the 2006 associated unit." 2007 INDEX { ifIndex, hdsl2ShdslInvIndex } 2008 ::= { hdsl2ShdslUnitMaintTable 1 } 2010 Hdsl2ShdslUnitMaintEntry ::= 2011 SEQUENCE 2012 { 2013 hdsl2ShdslMaintLoopbackTimeout Integer32, 2014 hdsl2ShdslMaintUnitPowerSource INTEGER 2015 } 2017 hdsl2ShdslMaintLoopbackTimeout OBJECT-TYPE 2018 SYNTAX Integer32(0..4095) 2019 UNITS "minutes" 2020 MAX-ACCESS read-write 2021 STATUS current 2022 DESCRIPTION 2023 "This object configures the timeout value for loopbacks 2024 initiated at segments endpoints contained in the associated 2025 unit. A value of 0 disables the timeout." 2026 ::= { hdsl2ShdslUnitMaintEntry 1 } 2028 hdsl2ShdslMaintUnitPowerSource OBJECT-TYPE 2029 SYNTAX INTEGER 2030 { 2031 local(1), 2032 span(2) 2033 } 2034 MAX-ACCESS read-only 2035 STATUS current 2036 DESCRIPTION 2037 "This object indicates the DC power source being used by the 2038 associated unit." 2039 ::= { hdsl2ShdslUnitMaintEntry 2 } 2041 -- Span Configuration Profile Group 2042 -- 2044 hdsl2ShdslSpanConfProfileTable OBJECT-TYPE 2045 SYNTAX SEQUENCE OF Hdsl2ShdslSpanConfProfileEntry 2046 MAX-ACCESS not-accessible 2047 STATUS current 2048 DESCRIPTION 2049 "This table supports definitions of span configuration 2050 profiles for SHDSL lines. HDSL2 does not support these 2051 configuration options. This table MUST be maintained 2052 in a persistent manner." 2053 ::= { hdsl2ShdslMibObjects 10 } 2055 hdsl2ShdslSpanConfProfileEntry OBJECT-TYPE 2056 SYNTAX Hdsl2ShdslSpanConfProfileEntry 2057 MAX-ACCESS not-accessible 2058 STATUS current 2059 DESCRIPTION 2060 "Each entry corresponds to a single span configuration 2061 profile. Each profile contains a set of span configuration 2062 parameters. The configuration parameters in a profile are 2063 applied to those lines referencing that profile (see the 2064 hdsl2ShdslSpanConfProfile object). Profiles may be 2065 created/deleted using the row creation/deletion mechanism 2066 via hdsl2ShdslSpanConfProfileRowStatus. If an active 2067 entry is referenced in hdsl2ShdslSpanConfProfile, the 2068 entry MUST remain active until all references are removed." 2069 INDEX { IMPLIED hdsl2ShdslSpanConfProfileName } 2070 ::= { hdsl2ShdslSpanConfProfileTable 1 } 2072 Hdsl2ShdslSpanConfProfileEntry ::= 2073 SEQUENCE 2074 { 2075 hdsl2ShdslSpanConfProfileName SnmpAdminString, 2076 hdsl2ShdslSpanConfWireInterface INTEGER, 2077 hdsl2ShdslSpanConfMinLineRate Unsigned32, 2078 hdsl2ShdslSpanConfMaxLineRate Unsigned32, 2079 hdsl2ShdslSpanConfPSD INTEGER, 2080 hdsl2ShdslSpanConfTransmissionMode 2081 Hdsl2ShdslTransmissionModeType, 2082 hdsl2ShdslSpanConfRemoteEnabled INTEGER, 2083 hdsl2ShdslSpanConfPowerFeeding INTEGER, 2084 hdsl2ShdslSpanConfCurrCondTargetMarginDown Integer32, 2085 hdsl2ShdslSpanConfWorstCaseTargetMarginDown Integer32, 2086 hdsl2ShdslSpanConfCurrCondTargetMarginUp Integer32, 2087 hdsl2ShdslSpanConfWorstCaseTargetMarginUp Integer32, 2088 hdsl2ShdslSpanConfUsedTargetMargins BITS, 2089 hdsl2ShdslSpanConfReferenceClock 2090 Hdsl2ShdslClockReferenceType, 2091 hdsl2ShdslSpanConfLineProbeEnable INTEGER, 2092 hdsl2ShdslSpanConfProfileRowStatus RowStatus 2093 } 2095 hdsl2ShdslSpanConfProfileName OBJECT-TYPE 2096 SYNTAX SnmpAdminString (SIZE(1..32)) 2097 MAX-ACCESS not-accessible 2098 STATUS current 2099 DESCRIPTION 2100 "This object is the unique index associated with this profile. 2101 Entries in this table are referenced via the object 2102 hdsl2ShdslSpanConfProfile in Hdsl2ShdslSpanConfEntry." 2103 ::= { hdsl2ShdslSpanConfProfileEntry 1 } 2105 hdsl2ShdslSpanConfWireInterface OBJECT-TYPE 2106 SYNTAX INTEGER 2107 { 2108 twoWire(1), 2109 fourWire(2), 2110 sixWire(3), 2111 eightWire(4) 2112 } 2113 MAX-ACCESS read-create 2114 STATUS current 2115 DESCRIPTION 2116 "This object configures the two-wire or optional four-wire, 2117 six-wire, or eight-wire operation for SHDSL Lines." 2118 DEFVAL { twoWire } 2119 ::= { hdsl2ShdslSpanConfProfileEntry 2 } 2121 hdsl2ShdslSpanConfMinLineRate OBJECT-TYPE 2122 SYNTAX Unsigned32(0..4294967295) 2123 UNITS "bps" 2124 MAX-ACCESS read-create 2125 STATUS current 2126 DESCRIPTION 2127 "This object configures the minimum transmission rate for 2128 the associated SHDSL Line in bits-per-second (bps) and includes 2129 both payload (user data) and any applicable framing overhead. 2130 If the minimum line rate equals the maximum line rate 2131 (hdsl2ShdslSpanMaxLineRate), the line rate is considered 2132 'fixed'. If the minimum line rate is less than the 2133 maximum line rate, the line rate is considered 2134 'rate-adaptive'." 2135 DEFVAL { 1552000 } 2136 ::= { hdsl2ShdslSpanConfProfileEntry 3 } 2138 hdsl2ShdslSpanConfMaxLineRate OBJECT-TYPE 2139 SYNTAX Unsigned32(0..4294967295) 2140 UNITS "bps" 2141 MAX-ACCESS read-create 2142 STATUS current 2143 DESCRIPTION 2144 "This object configures the maximum transmission rate for 2145 the associated SHDSL Line in bits-per-second (bps) and includes 2146 both payload (user data) and any applicable framing overhead. 2147 If the minimum line rate equals the maximum line rate 2148 (hdsl2ShdslSpanMaxLineRate), the line rate is considered 2149 'fixed'. If the minimum line rate is less than the 2150 maximum line rate, the line rate is considered 2151 'rate-adaptive'." 2152 DEFVAL { 1552000 } 2153 ::= { hdsl2ShdslSpanConfProfileEntry 4 } 2155 hdsl2ShdslSpanConfPSD OBJECT-TYPE 2156 SYNTAX INTEGER 2157 { 2158 symmetric(1), 2159 asymmetric(2) 2160 } 2161 MAX-ACCESS read-create 2162 STATUS current 2163 DESCRIPTION 2164 "This object configures use of symmetric/asymmetric PSD (Power 2165 Spectral Density) Mask for the associated SHDSL Line. Support 2166 for symmetric PSD is mandatory for all supported data rates. 2167 Support for asymmetric PSD is optional." 2168 DEFVAL { symmetric } 2169 ::= { hdsl2ShdslSpanConfProfileEntry 5 } 2171 hdsl2ShdslSpanConfTransmissionMode OBJECT-TYPE 2172 SYNTAX Hdsl2ShdslTransmissionModeType 2173 MAX-ACCESS read-create 2174 STATUS current 2175 DESCRIPTION 2176 "This object specifies the regional setting for the SHDSL 2177 line." 2178 DEFVAL { { region1 } } 2179 ::= { hdsl2ShdslSpanConfProfileEntry 6 } 2181 hdsl2ShdslSpanConfRemoteEnabled OBJECT-TYPE 2182 SYNTAX INTEGER 2183 { 2184 enabled(1), 2185 disabled(2) 2186 } 2187 MAX-ACCESS read-create 2188 STATUS current 2189 DESCRIPTION 2190 "This object enables/disables support for remote management 2191 of the units in a SHDSL line from the STU-R via the EOC." 2192 DEFVAL { enabled } 2193 ::= { hdsl2ShdslSpanConfProfileEntry 7 } 2195 hdsl2ShdslSpanConfPowerFeeding OBJECT-TYPE 2196 SYNTAX INTEGER 2197 { 2198 noPower(1), 2199 powerFeed(2), 2200 wettingCurrent(3) 2201 } 2202 MAX-ACCESS read-create 2203 STATUS current 2204 DESCRIPTION 2205 "This object enables/disables support for optional power 2206 feeding in a SHDSL line." 2207 DEFVAL { noPower } 2208 ::= { hdsl2ShdslSpanConfProfileEntry 8 } 2210 hdsl2ShdslSpanConfCurrCondTargetMarginDown OBJECT-TYPE 2211 SYNTAX Integer32(-10..21) 2212 UNITS "dB" 2213 MAX-ACCESS read-create 2214 STATUS current 2215 DESCRIPTION 2216 "This object specifies the downstream current condition target 2217 SNR margin for a SHDSL line. The SNR margin is the difference 2218 between the desired SNR and the actual SNR. Target SNR margin 2219 is the desired SNR margin for a unit." 2220 DEFVAL { 0 } 2221 ::= { hdsl2ShdslSpanConfProfileEntry 9 } 2223 hdsl2ShdslSpanConfWorstCaseTargetMarginDown OBJECT-TYPE 2224 SYNTAX Integer32(-10..21) 2225 UNITS "dB" 2226 MAX-ACCESS read-create 2227 STATUS current 2228 DESCRIPTION 2229 "This object specifies the downstream worst case target SNR 2230 margin for a SHDSL line. The SNR margin is the difference 2231 between the desired SNR and the actual SNR. Target SNR 2232 margin is the desired SNR margin for a unit." 2233 DEFVAL { 0 } 2234 ::= { hdsl2ShdslSpanConfProfileEntry 10 } 2236 hdsl2ShdslSpanConfCurrCondTargetMarginUp OBJECT-TYPE 2237 SYNTAX Integer32(-10..21) 2238 UNITS "dB" 2239 MAX-ACCESS read-create 2240 STATUS current 2241 DESCRIPTION 2242 "This object specifies the upstream current condition target 2243 SNR margin for a SHDSL line. The SNR margin is the difference 2244 between the desired SNR and the actual SNR. Target SNR margin 2245 is the desired SNR margin for a unit." 2246 DEFVAL { 0 } 2247 ::= { hdsl2ShdslSpanConfProfileEntry 11 } 2249 hdsl2ShdslSpanConfWorstCaseTargetMarginUp OBJECT-TYPE 2250 SYNTAX Integer32(-10..21) 2251 UNITS "dB" 2252 MAX-ACCESS read-create 2253 STATUS current 2254 DESCRIPTION 2255 "This object specifies the upstream worst case target SNR 2256 margin for a SHDSL line. The SNR margin is the difference 2257 between the desired SNR and the actual SNR. Target SNR margin 2258 is the desired SNR margin for a unit." 2259 DEFVAL { 0 } 2260 ::= { hdsl2ShdslSpanConfProfileEntry 12 } 2262 hdsl2ShdslSpanConfUsedTargetMargins OBJECT-TYPE 2263 SYNTAX BITS 2264 { 2265 currCondDown(0), 2266 worstCaseDown(1), 2267 currCondUp(2), 2268 worstCaseUp(3) 2269 } 2270 MAX-ACCESS read-create 2271 STATUS current 2272 DESCRIPTION 2273 "Indicates whether a target SNR margin is enabled or 2274 disabled. This is a bit-map of possible settings. The 2275 various bit positions are: 2277 currCondDown - current condition downstream target SNR 2278 margin enabled 2280 worstCaseDown - worst case downstream target SNR margin 2281 enabled 2283 currCondUp - current condition upstream target SNR 2284 margin enabled 2286 worstCaseUp - worst case upstream target SNR margin 2287 enabled." 2288 DEFVAL { { currCondDown } } 2289 ::= { hdsl2ShdslSpanConfProfileEntry 13 } 2291 hdsl2ShdslSpanConfReferenceClock OBJECT-TYPE 2292 SYNTAX Hdsl2ShdslClockReferenceType 2293 MAX-ACCESS read-create 2294 STATUS current 2295 DESCRIPTION 2296 "This object configures the clock reference for the STU-C 2297 in a SHDSL Line." 2298 DEFVAL { localClk } 2299 ::= { hdsl2ShdslSpanConfProfileEntry 14 } 2301 hdsl2ShdslSpanConfLineProbeEnable OBJECT-TYPE 2302 SYNTAX INTEGER 2303 { 2304 disable(1), 2305 enable(2) 2306 } 2307 MAX-ACCESS read-create 2308 STATUS current 2309 DESCRIPTION 2310 "This object enables/disables support for Line Probe of 2311 the units in a SHDSL line. When Line Probe is enabled, the 2312 system performs Line Probing to find the best possible 2313 rate. If Line probe is disabled, the rate adaptation phase 2314 is skipped to shorten set up time." 2315 DEFVAL { disable } 2316 ::= { hdsl2ShdslSpanConfProfileEntry 15 } 2318 hdsl2ShdslSpanConfProfileRowStatus OBJECT-TYPE 2319 SYNTAX RowStatus 2320 MAX-ACCESS read-create 2321 STATUS current 2322 DESCRIPTION 2323 "This object controls creation/deletion of the associated 2324 entry in this table per the semantics of RowStatus. If an 2325 active entry is referenced in hdsl2ShdslSpanConfProfile, the 2326 entry MUST remain active until all references are removed." 2327 ::= { hdsl2ShdslSpanConfProfileEntry 16 } 2329 -- Segment Endpoint Alarm Configuration Profile group 2330 -- 2332 hdsl2ShdslEndpointAlarmConfProfileTable OBJECT-TYPE 2333 SYNTAX SEQUENCE OF Hdsl2ShdslEndpointAlarmConfProfileEntry 2334 MAX-ACCESS not-accessible 2335 STATUS current 2336 DESCRIPTION 2337 "This table supports definitions of alarm configuration 2338 profiles for HDSL2/SHDSL segment endpoints. This table 2339 MUST be maintained in a persistent manner." 2340 ::= { hdsl2ShdslMibObjects 11 } 2342 hdsl2ShdslEndpointAlarmConfProfileEntry OBJECT-TYPE 2343 SYNTAX Hdsl2ShdslEndpointAlarmConfProfileEntry 2344 MAX-ACCESS not-accessible 2345 STATUS current 2346 DESCRIPTION 2347 "Each entry corresponds to a single alarm configuration profile. 2348 Each profile contains a set of parameters for setting alarm 2349 thresholds for various performance attributes monitored at 2350 HDSL2/SHDSL segment endpoints. Profiles may be created/deleted 2351 using the row creation/deletion mechanism via 2352 hdsl2ShdslEndpointAlarmConfProfileRowStatus. If an active 2353 entry is referenced in either hdsl2ShdslSpanConfAlarmProfile 2354 or hdsl2ShdslEndpointAlarmConfProfile, the entry MUST remain 2355 active until all references are removed." 2356 INDEX { IMPLIED hdsl2ShdslEndpointAlarmConfProfileName } 2357 ::= { hdsl2ShdslEndpointAlarmConfProfileTable 1 } 2359 Hdsl2ShdslEndpointAlarmConfProfileEntry ::= 2360 SEQUENCE 2361 { 2362 hdsl2ShdslEndpointAlarmConfProfileName SnmpAdminString, 2363 hdsl2ShdslEndpointThreshLoopAttenuation Integer32, 2364 hdsl2ShdslEndpointThreshSNRMargin Integer32, 2365 hdsl2ShdslEndpointThreshES 2366 Hdsl2ShdslPerfIntervalThreshold, 2368 hdsl2ShdslEndpointThreshSES 2369 Hdsl2ShdslPerfIntervalThreshold, 2370 hdsl2ShdslEndpointThreshCRCanomalies Integer32, 2371 hdsl2ShdslEndpointThreshLOSWS 2372 Hdsl2ShdslPerfIntervalThreshold, 2373 hdsl2ShdslEndpointThreshUAS 2374 Hdsl2ShdslPerfIntervalThreshold, 2375 hdsl2ShdslEndpointAlarmConfProfileRowStatus RowStatus 2376 } 2378 hdsl2ShdslEndpointAlarmConfProfileName OBJECT-TYPE 2379 SYNTAX SnmpAdminString (SIZE(1..32)) 2380 MAX-ACCESS not-accessible 2381 STATUS current 2382 DESCRIPTION 2383 "This object is the unique index associated with this profile." 2384 ::= { hdsl2ShdslEndpointAlarmConfProfileEntry 1 } 2386 hdsl2ShdslEndpointThreshLoopAttenuation OBJECT-TYPE 2387 SYNTAX Integer32(-127..128) 2388 UNITS "dB" 2389 MAX-ACCESS read-create 2390 STATUS current 2391 DESCRIPTION 2392 "This object configures the loop attenuation alarm threshold. 2393 When the current value of hdsl2ShdslEndpointCurrAtn reaches 2394 or exceeds this threshold, a hdsl2ShdslLoopAttenCrossing 2395 MAY be generated." 2396 DEFVAL { 0 } 2397 ::= { hdsl2ShdslEndpointAlarmConfProfileEntry 2 } 2399 hdsl2ShdslEndpointThreshSNRMargin OBJECT-TYPE 2400 SYNTAX Integer32(-127..128) 2401 UNITS "dB" 2402 MAX-ACCESS read-create 2403 STATUS current 2404 DESCRIPTION 2405 "This object configures the SNR margin alarm threshold. 2406 When the current value of hdsl2ShdslEndpointCurrSnrMgn 2407 reaches or drops below this threshold, a 2408 hdsl2ShdslSNRMarginCrossing MAY be generated." 2409 DEFVAL { 0 } 2410 ::= { hdsl2ShdslEndpointAlarmConfProfileEntry 3 } 2412 hdsl2ShdslEndpointThreshES OBJECT-TYPE 2413 SYNTAX Hdsl2ShdslPerfIntervalThreshold 2414 UNITS "seconds" 2415 MAX-ACCESS read-create 2416 STATUS current 2417 DESCRIPTION 2418 "This object configures the threshold for the number of 2419 errored seconds (ES) within any given 15-minute performance 2420 data collection interval. If the value of errored seconds 2421 in a particular 15-minute collection interval reaches/ 2422 exceeds this value, a hdsl2ShdslPerfESThresh MAY be 2423 generated. At most one notification will be sent per 2424 interval per endpoint." 2425 DEFVAL { 0 } 2426 ::= { hdsl2ShdslEndpointAlarmConfProfileEntry 4 } 2428 hdsl2ShdslEndpointThreshSES OBJECT-TYPE 2429 SYNTAX Hdsl2ShdslPerfIntervalThreshold 2430 UNITS "seconds" 2431 MAX-ACCESS read-create 2432 STATUS current 2433 DESCRIPTION 2434 "This object configures the threshold for the number of 2435 severely errored seconds (SES) within any given 15-minute 2436 performance data collection interval. If the value of 2437 severely errored seconds in a particular 15-minute collection 2438 interval reaches/exceeds this value, a hdsl2ShdslPerfSESThresh 2439 MAY be generated. At most one notification will be sent per 2440 interval per endpoint." 2441 DEFVAL { 0 } 2442 ::= { hdsl2ShdslEndpointAlarmConfProfileEntry 5 } 2444 hdsl2ShdslEndpointThreshCRCanomalies OBJECT-TYPE 2445 SYNTAX Integer32 2446 UNITS "detected CRC Anomalies" 2447 MAX-ACCESS read-create 2448 STATUS current 2449 DESCRIPTION 2450 "This object configures the threshold for the number of 2451 CRC anomalies within any given 15-minute performance data 2452 collection interval. If the value of CRC anomalies in a 2453 particular 15-minute collection interval reaches/exceeds 2454 this value, a hdsl2ShdslPerfCRCanomaliesThresh MAY be 2455 generated. At most one notification will be sent per 2456 interval per endpoint." 2457 DEFVAL { 0 } 2458 ::= { hdsl2ShdslEndpointAlarmConfProfileEntry 6 } 2460 hdsl2ShdslEndpointThreshLOSWS OBJECT-TYPE 2461 SYNTAX Hdsl2ShdslPerfIntervalThreshold 2462 UNITS "seconds" 2463 MAX-ACCESS read-create 2464 STATUS current 2465 DESCRIPTION 2466 "This object configures the threshold for the number of 2467 Loss of Sync Word (LOSW) Seconds within any given 15-minute 2468 performance data collection interval. If the value of LOSW 2469 in a particular 15-minute collection interval reaches/exceeds 2470 this value, a hdsl2ShdslPerfLOSWSThresh MAY be generated. 2471 At most one notification will be sent per interval per 2472 endpoint." 2473 DEFVAL { 0 } 2474 ::= { hdsl2ShdslEndpointAlarmConfProfileEntry 7 } 2476 hdsl2ShdslEndpointThreshUAS OBJECT-TYPE 2477 SYNTAX Hdsl2ShdslPerfIntervalThreshold 2478 UNITS "seconds" 2479 MAX-ACCESS read-create 2480 STATUS current 2481 DESCRIPTION 2482 "This object configures the threshold for the number of 2483 unavailable seconds (UAS) within any given 15-minute 2484 performance data collection interval. If the value of UAS 2485 in a particular 15-minute collection interval reaches/exceeds 2486 this value, a hdsl2ShdslPerfUASThresh MAY be generated. 2487 At most one notification will be sent per interval per 2488 endpoint." 2489 DEFVAL { 0 } 2490 ::= { hdsl2ShdslEndpointAlarmConfProfileEntry 8 } 2492 hdsl2ShdslEndpointAlarmConfProfileRowStatus OBJECT-TYPE 2493 SYNTAX RowStatus 2494 MAX-ACCESS read-create 2495 STATUS current 2496 DESCRIPTION 2497 "This object controls creation/deletion of the associated 2498 entry in this table as per the semantics of RowStatus. 2499 If an active entry is referenced in either 2500 hdsl2ShdslSpanConfAlarmProfile or 2501 hdsl2ShdslEndpointAlarmConfProfile, the entry MUST remain 2502 active until all references are removed." 2503 ::= { hdsl2ShdslEndpointAlarmConfProfileEntry 9 } 2505 -- Notifications Group 2506 -- 2508 hdsl2ShdslNotifications OBJECT IDENTIFIER ::= { hdsl2ShdslMIB 0 } 2510 hdsl2ShdslLoopAttenCrossing NOTIFICATION-TYPE 2511 OBJECTS 2512 { 2513 hdsl2ShdslEndpointCurrAtn, 2514 hdsl2ShdslEndpointThreshLoopAttenuation 2515 } 2516 STATUS current 2517 DESCRIPTION 2518 "This notification indicates that the loop attenuation 2519 threshold (as per the hdsl2ShdslEndpointThreshLoopAttenuation 2520 value) has been reached/exceeded for the HDSL2/SHDSL segment 2521 endpoint." 2522 ::= { hdsl2ShdslNotifications 1 } 2524 hdsl2ShdslSNRMarginCrossing NOTIFICATION-TYPE 2525 OBJECTS 2526 { 2527 hdsl2ShdslEndpointCurrSnrMgn, 2528 hdsl2ShdslEndpointThreshSNRMargin 2529 } 2530 STATUS current 2531 DESCRIPTION 2532 "This notification indicates that the SNR margin threshold (as 2533 per the hdsl2ShdslEndpointThreshSNRMargin value) has been 2534 reached/exceeded for the HDSL2/SHDSL segment endpoint." 2535 ::= { hdsl2ShdslNotifications 2 } 2537 hdsl2ShdslPerfESThresh NOTIFICATION-TYPE 2538 OBJECTS 2539 { 2540 hdsl2ShdslEndpointCurr15MinES, 2541 hdsl2ShdslEndpointThreshES 2542 } 2543 STATUS current 2544 DESCRIPTION 2545 "This notification indicates that the errored seconds 2546 threshold (as per the hdsl2ShdslEndpointThreshES value) 2547 has been reached/exceeded for the HDSL2/SHDSL segment 2548 endpoint." 2549 ::= { hdsl2ShdslNotifications 3 } 2551 hdsl2ShdslPerfSESThresh NOTIFICATION-TYPE 2552 OBJECTS 2553 { 2554 hdsl2ShdslEndpointCurr15MinSES, 2555 hdsl2ShdslEndpointThreshSES 2556 } 2557 STATUS current 2558 DESCRIPTION 2559 "This notification indicates that the severely errored seconds 2560 threshold (as per the hdsl2ShdslEndpointThreshSES value) has 2561 been reached/exceeded for the HDSL2/SHDSL Segment Endpoint." 2562 ::= { hdsl2ShdslNotifications 4 } 2564 hdsl2ShdslPerfCRCanomaliesThresh NOTIFICATION-TYPE 2565 OBJECTS 2566 { 2567 hdsl2ShdslEndpointCurr15MinCRCanomalies, 2568 hdsl2ShdslEndpointThreshCRCanomalies 2569 } 2570 STATUS current 2571 DESCRIPTION 2572 "This notification indicates that the CRC anomalies threshold 2573 (as per the hdsl2ShdslEndpointThreshCRCanomalies value) has 2574 been reached/exceeded for the HDSL2/SHDSL Segment Endpoint." 2575 ::= { hdsl2ShdslNotifications 5 } 2577 hdsl2ShdslPerfLOSWSThresh NOTIFICATION-TYPE 2578 OBJECTS 2579 { 2580 hdsl2ShdslEndpointCurr15MinLOSWS, 2581 hdsl2ShdslEndpointThreshLOSWS 2582 } 2583 STATUS current 2584 DESCRIPTION 2585 "This notification indicates that the LOSW seconds threshold 2586 (as per the hdsl2ShdslEndpointThreshLOSWS value) has been 2587 reached/exceeded for the HDSL2/SHDSL segment endpoint." 2588 ::= { hdsl2ShdslNotifications 6 } 2590 hdsl2ShdslPerfUASThresh NOTIFICATION-TYPE 2591 OBJECTS 2592 { 2593 hdsl2ShdslEndpointCurr15MinUAS, 2594 hdsl2ShdslEndpointThreshUAS 2595 } 2596 STATUS current 2597 DESCRIPTION 2598 "This notification indicates that the unavailable seconds 2599 threshold (as per the hdsl2ShdslEndpointThreshUAS value) has 2600 been reached/exceeded for the HDSL2/SHDSL segment endpoint." 2601 ::= { hdsl2ShdslNotifications 7 } 2603 hdsl2ShdslSpanInvalidNumRepeaters NOTIFICATION-TYPE 2604 OBJECTS 2605 { 2606 hdsl2ShdslSpanConfNumRepeaters 2607 } 2608 STATUS current 2609 DESCRIPTION 2610 "This notification indicates that a mismatch has been detected 2611 between the number of repeater/regenerator units configured 2612 for a HDSL2/SHDSL line via the hdsl2ShdslSpanConfNumRepeaters 2613 object and the actual number of repeater/regenerator units 2614 discovered via the EOC." 2615 ::= { hdsl2ShdslNotifications 8 } 2617 hdsl2ShdslLoopbackFailure NOTIFICATION-TYPE 2618 OBJECTS 2619 { 2620 hdsl2ShdslMaintLoopbackConfig 2621 } 2622 STATUS current 2623 DESCRIPTION 2624 "This notification indicates that an endpoint maintenance 2625 loopback command failed for an HDSL2/SHDSL segment." 2626 ::= { hdsl2ShdslNotifications 9 } 2628 hdsl2ShdslpowerBackoff NOTIFICATION-TYPE 2629 OBJECTS 2630 { 2631 hdsl2ShdslEndpointCurrStatus 2632 } 2633 STATUS current 2634 DESCRIPTION 2635 "This notification indicates that the bit setting for 2636 powerBackoff in the hdsl2ShdslEndpointCurrStatus object for 2637 this endpoint has changed." 2638 ::= { hdsl2ShdslNotifications 10 } 2640 hdsl2ShdsldeviceFault NOTIFICATION-TYPE 2641 OBJECTS 2642 { 2643 hdsl2ShdslEndpointCurrStatus 2644 } 2645 STATUS current 2646 DESCRIPTION 2647 "This notification indicates that the bit setting for 2648 deviceFault in the hdsl2ShdslEndpointCurrStatus object for 2649 this endpoint has changed." 2650 ::= { hdsl2ShdslNotifications 11 } 2652 hdsl2ShdsldcContinuityFault NOTIFICATION-TYPE 2653 OBJECTS 2654 { 2655 hdsl2ShdslEndpointCurrStatus 2656 } 2657 STATUS current 2658 DESCRIPTION 2659 "This notification indicates that the bit setting for 2660 dcContinuityFault in the hdsl2ShdslEndpointCurrStatus object 2661 for this endpoint has changed." 2662 ::= { hdsl2ShdslNotifications 12 } 2664 hdsl2ShdslconfigInitFailure NOTIFICATION-TYPE 2665 OBJECTS 2666 { 2667 hdsl2ShdslEndpointCurrStatus 2668 } 2669 STATUS current 2670 DESCRIPTION 2671 "This notification indicates that the bit setting for 2672 configInitFailure in the hdsl2ShdslEndpointCurrStatus object 2673 for this endpoint has changed." 2674 ::= { hdsl2ShdslNotifications 13 } 2676 hdsl2ShdslprotocolInitFailure NOTIFICATION-TYPE 2677 OBJECTS 2678 { 2679 hdsl2ShdslEndpointCurrStatus 2680 } 2681 STATUS current 2682 DESCRIPTION 2683 "This notification indicates that the bit setting for 2684 protocolInitFailure in the hdsl2ShdslEndpointCurrStatus 2685 object for this endpoint has changed." 2686 ::= { hdsl2ShdslNotifications 14 } 2688 hdsl2ShdslnoNeighborPresent NOTIFICATION-TYPE 2689 OBJECTS 2690 { 2691 hdsl2ShdslEndpointCurrStatus 2692 } 2693 STATUS current 2694 DESCRIPTION 2695 "This notification indicates that the bit setting for 2696 noNeighborPresent in the hdsl2ShdslEndpointCurrStatus object 2697 for this endpoint has changed." 2698 ::= { hdsl2ShdslNotifications 15 } 2700 hdsl2ShdslLocalPowerLoss NOTIFICATION-TYPE 2701 OBJECTS 2702 { 2703 hdsl2ShdslInvVendorID 2704 } 2705 STATUS current 2706 DESCRIPTION 2707 "This notification indicates impending unit failure due to 2708 loss of local power (last gasp)." 2709 ::= { hdsl2ShdslNotifications 16 } 2711 -- conformance information 2712 -- 2714 hdsl2ShdslConformance OBJECT IDENTIFIER ::= { hdsl2ShdslMIB 3 } 2715 hdsl2ShdslGroups OBJECT IDENTIFIER ::= 2716 { hdsl2ShdslConformance 1 } 2717 hdsl2ShdslCompliances OBJECT IDENTIFIER ::= 2718 { hdsl2ShdslConformance 2 } 2720 -- agent compliance statements 2722 hdsl2ShdslLineMibCompliance MODULE-COMPLIANCE 2723 STATUS deprecated 2724 DESCRIPTION 2725 "The compliance statement for SNMP entities which implement 2726 HDSL2 and SHDSL. The version of SHDSL supported in this 2727 compliance statement is g.shdsl. 2729 **** This compliance statement is deprecated. ****" 2730 MODULE 2731 MANDATORY-GROUPS 2732 { 2733 hdsl2ShdslSpanConfGroup, 2734 hdsl2ShdslSpanStatusGroup, 2735 hdsl2ShdslInventoryGroup, 2736 hdsl2ShdslEndpointConfGroup, 2737 hdsl2ShdslEndpointCurrGroup, 2738 hdsl2Shdsl15MinIntervalGroup, 2739 hdsl2Shdsl1DayIntervalGroup, 2740 hdsl2ShdslMaintenanceGroup, 2741 hdsl2ShdslEndpointAlarmConfGroup, 2742 hdsl2ShdslNotificationGroup 2743 } 2745 GROUP hdsl2ShdslInventoryShdslGroup 2746 DESCRIPTION 2747 "Support for this group is only required for implementations 2748 supporting SHDSL lines." 2750 GROUP hdsl2ShdslSpanShdslStatusGroup 2751 DESCRIPTION 2752 "Support for this group is only required for implementations 2753 supporting SHDSL lines." 2755 GROUP hdsl2ShdslSpanConfProfileGroup 2756 DESCRIPTION 2757 "Support for this group is only required for implementations 2758 supporting SHDSL lines." 2760 OBJECT hdsl2ShdslSpanConfWireInterface 2761 SYNTAX INTEGER 2762 { 2763 twoWire(1), 2764 fourWire(2) 2765 } 2766 DESCRIPTION 2767 "An implementation only has to support the range as 2768 applicable for the original g.shdsl specification defined 2769 in RFC 3276." 2771 OBJECT hdsl2ShdslStatusMaxAttainableLineRate 2772 SYNTAX Unsigned32(0..4112000) 2773 DESCRIPTION 2774 "An implementation only has to support the range as 2775 applicable for the original g.shdsl specification defined 2776 in RFC 3276." 2778 OBJECT hdsl2ShdslStatusActualLineRate 2779 SYNTAX Unsigned32(0..4112000) 2780 DESCRIPTION 2781 "An implementation only has to support the range as 2782 applicable for the original g.shdsl specification defined 2783 in RFC 3276." 2785 OBJECT hdsl2ShdslSpanConfMinLineRate 2786 SYNTAX Unsigned32(0..4112000) 2787 DESCRIPTION 2788 "An implementation only has to support the range as 2789 applicable for the original g.shdsl specification defined 2790 in RFC 3276." 2792 OBJECT hdsl2ShdslSpanConfMaxLineRate 2793 SYNTAX Unsigned32(0..4112000) 2794 DESCRIPTION 2795 "An implementation only has to support the range as 2796 applicable for the original g.shdsl specification defined 2797 in RFC 3276." 2799 ::= { hdsl2ShdslCompliances 1 } 2801 hdsl2GshdslbisLineMibCompliance MODULE-COMPLIANCE 2802 STATUS current 2803 DESCRIPTION 2804 "The compliance statement for SNMP entities which implement 2805 HDSL2 and SHDSL. The version of SHDSL supported in this 2806 compliance statement is g.shdsl.bis." 2807 MODULE 2808 MANDATORY-GROUPS 2809 { 2810 hdsl2ShdslSpanConfGroup, 2811 hdsl2ShdslSpanStatusGroup, 2812 hdsl2ShdslInventoryGroup, 2813 hdsl2ShdslEndpointConfGroup, 2814 hdsl2ShdslEndpointCurrGroup, 2815 hdsl2Shdsl15MinIntervalGroup, 2816 hdsl2Shdsl1DayIntervalGroup, 2817 hdsl2ShdslMaintenanceGroup, 2818 hdsl2ShdslEndpointAlarmConfGroup, 2819 hdsl2ShdslNotificationGroup 2820 } 2822 GROUP hdsl2ShdslInventoryShdslGroup 2823 DESCRIPTION 2824 "Support for this group is only required for implementations 2825 supporting SHDSL lines." 2827 GROUP hdsl2ShdslSpanShdslStatusGroup 2828 DESCRIPTION 2829 "Support for this group is only required for implementations 2830 supporting SHDSL lines." 2832 GROUP hdsl2ShdslSpanConfProfileGroup 2833 DESCRIPTION 2834 "Support for this group is only required for implementations 2835 supporting SHDSL lines." 2837 GROUP hdsl2ShdslWirePairGroup 2838 DESCRIPTION 2839 "Support for this group is only required for implementations 2840 supporting SHDSL lines." 2842 GROUP hdsl2ShdslPayloadRateGroup 2843 DESCRIPTION 2844 "Support for this group is only required for implementations 2845 supporting SHDSL lines." 2847 ::= { hdsl2ShdslCompliances 2 } 2849 -- units of conformance 2850 -- 2852 hdsl2ShdslSpanConfGroup OBJECT-GROUP 2853 OBJECTS 2854 { 2855 hdsl2ShdslSpanConfNumRepeaters, 2856 hdsl2ShdslSpanConfProfile, 2857 hdsl2ShdslSpanConfAlarmProfile 2858 } 2859 STATUS current 2860 DESCRIPTION 2861 "This group supports objects for configuring span related 2862 parameters for HDSL2/SHDSL lines." 2863 ::= { hdsl2ShdslGroups 1 } 2865 hdsl2ShdslSpanStatusGroup OBJECT-GROUP 2866 OBJECTS 2867 { 2868 hdsl2ShdslStatusNumAvailRepeaters 2869 } 2870 STATUS current 2871 DESCRIPTION 2872 "This group supports objects for retrieving span related 2873 status for HDSL2/SHDSL lines." 2874 ::= { hdsl2ShdslGroups 2 } 2876 hdsl2ShdslInventoryShdslGroup OBJECT-GROUP 2877 OBJECTS 2878 { 2879 hdsl2ShdslInvTransmissionModeCapability 2880 } 2881 STATUS current 2882 DESCRIPTION 2883 "This group supports objects for retrieving SHDSL-specific 2884 inventory information." 2885 ::= { hdsl2ShdslGroups 3 } 2887 hdsl2ShdslSpanShdslStatusGroup OBJECT-GROUP 2888 OBJECTS 2889 { 2890 hdsl2ShdslStatusMaxAttainableLineRate, 2891 hdsl2ShdslStatusActualLineRate, 2892 hdsl2ShdslStatusTransmissionModeCurrent 2893 } 2894 STATUS current 2895 DESCRIPTION 2896 "This group supports objects for retrieving SHDSL-specific 2897 span related status." 2898 ::= { hdsl2ShdslGroups 4 } 2900 hdsl2ShdslInventoryGroup OBJECT-GROUP 2901 OBJECTS 2902 { 2903 hdsl2ShdslInvVendorID, 2904 hdsl2ShdslInvVendorModelNumber, 2905 hdsl2ShdslInvVendorSerialNumber, 2906 hdsl2ShdslInvVendorEOCSoftwareVersion, 2907 hdsl2ShdslInvStandardVersion, 2908 hdsl2ShdslInvVendorListNumber, 2909 hdsl2ShdslInvVendorIssueNumber, 2910 hdsl2ShdslInvVendorSoftwareVersion, 2911 hdsl2ShdslInvEquipmentCode, 2912 hdsl2ShdslInvVendorOther 2913 } 2914 STATUS current 2915 DESCRIPTION 2916 "This group supports objects that provide unit inventory 2917 information about the units in HDSL2/SHDSL lines." 2918 ::= { hdsl2ShdslGroups 5 } 2920 hdsl2ShdslEndpointConfGroup OBJECT-GROUP 2921 OBJECTS 2922 { 2923 hdsl2ShdslEndpointCurrAtn 2924 } 2925 STATUS current 2926 DESCRIPTION 2927 "This group supports objects for configuring parameters for 2928 segment endpoints in HDSL2/SHDSL lines." 2929 ::= { hdsl2ShdslGroups 6 } 2931 hdsl2ShdslEndpointCurrGroup OBJECT-GROUP 2932 OBJECTS 2933 { 2934 hdsl2ShdslEndpointCurrAtn, 2935 hdsl2ShdslEndpointCurrSnrMgn, 2936 hdsl2ShdslEndpointCurrStatus, 2937 hdsl2ShdslEndpointES, 2938 hdsl2ShdslEndpointSES, 2939 hdsl2ShdslEndpointCRCanomalies, 2940 hdsl2ShdslEndpointLOSWS, 2941 hdsl2ShdslEndpointUAS, 2942 hdsl2ShdslEndpointCurr15MinTimeElapsed, 2943 hdsl2ShdslEndpointCurr15MinES, 2944 hdsl2ShdslEndpointCurr15MinSES, 2945 hdsl2ShdslEndpointCurr15MinCRCanomalies, 2946 hdsl2ShdslEndpointCurr15MinLOSWS, 2947 hdsl2ShdslEndpointCurr15MinUAS, 2948 hdsl2ShdslEndpointCurr1DayTimeElapsed, 2949 hdsl2ShdslEndpointCurr1DayES, 2950 hdsl2ShdslEndpointCurr1DaySES, 2951 hdsl2ShdslEndpointCurr1DayCRCanomalies, 2952 hdsl2ShdslEndpointCurr1DayLOSWS, 2953 hdsl2ShdslEndpointCurr1DayUAS 2954 } 2955 STATUS current 2956 DESCRIPTION 2957 "This group supports objects which provide current status and 2958 performance measurements relating to segment endpoints in 2959 HDSL2/SHDSL lines." 2960 ::= { hdsl2ShdslGroups 7 } 2962 hdsl2Shdsl15MinIntervalGroup OBJECT-GROUP 2963 OBJECTS 2964 { 2965 hdsl2Shdsl15MinIntervalES, 2966 hdsl2Shdsl15MinIntervalSES, 2967 hdsl2Shdsl15MinIntervalCRCanomalies, 2968 hdsl2Shdsl15MinIntervalLOSWS, 2969 hdsl2Shdsl15MinIntervalUAS 2970 } 2971 STATUS current 2972 DESCRIPTION 2973 "This group supports objects which maintain historic 2974 performance measurements relating to segment endpoints in 2975 HDSL2/SHDSL lines in 15-minute intervals." 2976 ::= { hdsl2ShdslGroups 8 } 2978 hdsl2Shdsl1DayIntervalGroup OBJECT-GROUP 2979 OBJECTS 2980 { 2981 hdsl2Shdsl1DayIntervalMoniSecs, 2982 hdsl2Shdsl1DayIntervalES, 2983 hdsl2Shdsl1DayIntervalSES, 2984 hdsl2Shdsl1DayIntervalCRCanomalies, 2985 hdsl2Shdsl1DayIntervalLOSWS, 2986 hdsl2Shdsl1DayIntervalUAS 2987 } 2988 STATUS current 2989 DESCRIPTION 2990 "This group supports objects which maintain historic 2991 performance measurements relating to segment endpoints in 2992 HDSL2/SHDSL lines in 1-day intervals." 2994 ::= { hdsl2ShdslGroups 9 } 2996 hdsl2ShdslMaintenanceGroup OBJECT-GROUP 2997 OBJECTS 2998 { 2999 hdsl2ShdslMaintLoopbackConfig, 3000 hdsl2ShdslMaintTipRingReversal, 3001 hdsl2ShdslMaintPowerBackOff, 3002 hdsl2ShdslMaintSoftRestart, 3003 hdsl2ShdslMaintLoopbackTimeout, 3004 hdsl2ShdslMaintUnitPowerSource 3005 } 3006 STATUS current 3007 DESCRIPTION 3008 "This group supports objects that provide support for 3009 maintenance actions for HDSL2/SHDSL lines." 3010 ::= { hdsl2ShdslGroups 10 } 3012 hdsl2ShdslEndpointAlarmConfGroup OBJECT-GROUP 3013 OBJECTS 3014 { 3015 hdsl2ShdslEndpointAlarmConfProfile, 3016 hdsl2ShdslEndpointThreshLoopAttenuation, 3017 hdsl2ShdslEndpointThreshSNRMargin, 3018 hdsl2ShdslEndpointThreshES, 3019 hdsl2ShdslEndpointThreshSES, 3020 hdsl2ShdslEndpointThreshCRCanomalies, 3021 hdsl2ShdslEndpointThreshLOSWS, 3022 hdsl2ShdslEndpointThreshUAS, 3023 hdsl2ShdslEndpointAlarmConfProfileRowStatus 3024 } 3025 STATUS current 3026 DESCRIPTION 3027 "This group supports objects that allow configuration of alarm 3028 thresholds for various performance parameters for HDSL2/SHDSL 3029 lines." 3030 ::= { hdsl2ShdslGroups 11 } 3032 hdsl2ShdslNotificationGroup NOTIFICATION-GROUP 3033 NOTIFICATIONS 3034 { 3035 hdsl2ShdslLoopAttenCrossing, 3036 hdsl2ShdslSNRMarginCrossing, 3037 hdsl2ShdslPerfESThresh, 3038 hdsl2ShdslPerfSESThresh, 3039 hdsl2ShdslPerfCRCanomaliesThresh, 3040 hdsl2ShdslPerfLOSWSThresh, 3041 hdsl2ShdslPerfUASThresh, 3042 hdsl2ShdslSpanInvalidNumRepeaters, 3043 hdsl2ShdslLoopbackFailure, 3044 hdsl2ShdslpowerBackoff, 3045 hdsl2ShdsldeviceFault, 3046 hdsl2ShdsldcContinuityFault, 3047 hdsl2ShdslconfigInitFailure, 3048 hdsl2ShdslprotocolInitFailure, 3049 hdsl2ShdslnoNeighborPresent, 3050 hdsl2ShdslLocalPowerLoss 3051 } 3052 STATUS current 3053 DESCRIPTION 3054 "This group supports notifications of significant conditions 3055 associated with HDSL2/SHDSL lines." 3056 ::= { hdsl2ShdslGroups 12 } 3058 hdsl2ShdslSpanConfProfileGroup OBJECT-GROUP 3059 OBJECTS 3060 { 3061 hdsl2ShdslSpanConfWireInterface, 3062 hdsl2ShdslSpanConfMinLineRate, 3063 hdsl2ShdslSpanConfMaxLineRate, 3064 hdsl2ShdslSpanConfPSD, 3065 hdsl2ShdslSpanConfTransmissionMode, 3066 hdsl2ShdslSpanConfRemoteEnabled, 3067 hdsl2ShdslSpanConfPowerFeeding, 3068 hdsl2ShdslSpanConfCurrCondTargetMarginDown, 3069 hdsl2ShdslSpanConfWorstCaseTargetMarginDown, 3070 hdsl2ShdslSpanConfCurrCondTargetMarginUp, 3071 hdsl2ShdslSpanConfWorstCaseTargetMarginUp, 3072 hdsl2ShdslSpanConfUsedTargetMargins, 3073 hdsl2ShdslSpanConfReferenceClock, 3074 hdsl2ShdslSpanConfLineProbeEnable, 3075 hdsl2ShdslSpanConfProfileRowStatus 3076 } 3077 STATUS current 3078 DESCRIPTION 3079 "This group supports objects that constitute configuration 3080 profiles for configuring span related parameters in SHDSL 3081 lines." 3082 ::= { hdsl2ShdslGroups 13 } 3084 hdsl2ShdslWirePairGroup OBJECT-GROUP 3085 OBJECTS 3086 { 3087 hdsl2ShdslEndpointCurrTipRingReversal, 3088 hdsl2ShdslEndpointCurrActivationState 3089 } 3090 STATUS current 3091 DESCRIPTION 3092 "This group supports objects which provide the status 3093 of SHDSL-specific wire pairs." 3094 ::= { hdsl2ShdslGroups 14 } 3096 hdsl2ShdslPayloadRateGroup OBJECT-GROUP 3097 OBJECTS 3098 { 3099 hdsl2ShdslStatusMaxAttainablePayloadRate, 3100 hdsl2ShdslStatusActualPayloadRate 3101 } 3102 STATUS current 3103 DESCRIPTION 3104 "This group supports object for retrieving payload rates 3105 which excludes any framing overhead." 3106 ::= { hdsl2ShdslGroups 15 } 3108 END 3110 4. Implementation Analysis 3112 A management application which supports RFC 3276 could mistakenly 3113 flag a unit which responds with a rate or wire pair which exceeds the 3114 ranges and/or enumerations specified in RFC 3276. For example, a 3115 G.shdsl.bis line with four wire pairs would report statistics for 3116 wire pairs that do not exist in RFC 3276. That is, a GET-NEXT 3117 request issues with the object identifier: 3119 hdsl2ShdslEndpointCurrAtn.1.1.1.2 3121 might return 3123 hdsl2ShdslEndpointCurrAtn.1.1.1.3 = 0 3125 with a G.shdsl.bis unit and 3127 hdsl2ShdslEndpointCurrSnrMgn.1.1.1.1 = 0 3129 with an HDSL2 unit as these objects are indexed by 3131 INDEX { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslendpointSide, 3132 hdsl2ShdslEndpointWirePair } 3134 A management application intended to manage G.shdsl.bis agents SHOULD 3135 be modified to accept this sequence. 3137 One should note that this same unmodified management application is 3138 still capable of managing G.shdsl.bis agents albeit to the degree of 3139 G.SHDSL (non-bis) limitations. That is, it can create and monitor 3140 configurations limited to two wire pairs with an upper rate limit of 3141 4112000 bits/second. 3143 5. Security Considerations 3145 There are a number of management objects defined in this MIB module 3146 with a MAX-ACCESS clause of read-write and/or read-create. Such 3147 objects may be considered sensitive or vulnerable in some network 3148 environments. The support for SET operations in a non-secure 3149 environment without proper protection can have a negative effect on 3150 network operations. These are the tables and objects and their 3151 sensitivity/vulnerability: 3153 o hdsl2ShdslSpanConfTable 3155 The table consists of the following objects that support SET 3156 operations: 3158 * hdsl2ShdslSpanConfNumRepeaters 3159 * hdsl2ShdslSpanConfProfile 3160 * hdsl2ShdslSpanConfAlarmProfile 3162 Unauthorized changes to hdsl2ShdslSpanConfNumRepeaters could 3163 result in a hdsl2ShdslSpanInvalidNumRepeaters notification. Note 3164 the discussion on hdsl2ShdslSpanInvalidNumRepeaters in the 3165 Notifications Section above. 3167 Unauthorized changes to hdsl2ShdslSpanConfProfile could have an 3168 adverse operational effect on a span. Reference the 3169 hdsl2ShdslSpanConfProfileTable discussion below. 3171 Unauthorized changes to hdsl2ShdslSpanConfAlarmProfile could have 3172 a contrary effect on notifications. Reference the 3173 hdsl2ShdslEndpointAlarmConfProfileTable discussion below. 3175 o hdsl2ShdslEndpointConfTable 3177 This table contains one object, 3178 hdsl2ShdslEndpointAlarmConfProfile, that supports SET operations. 3179 Unauthorized changes could have an undesirable notifications. 3180 Reference the hdsl2ShdslEndpointAlarmConfProfileTable discussion 3181 below. 3183 o hdsl2ShdslEndpointMaintTable 3185 The table consists of the following objects that support SET 3186 operations: 3188 * hdsl2ShdslMaintLoopbackConfig 3189 * hdsl2ShdslMaintPowerBackoff 3190 * hdsl2ShdslMaintSoftRestart 3192 Unauthorized changes to hdsl2ShdslMaintLoopbackConfig could 3193 prevent end-to-end data transfer due to an activation of a 3194 loopback. 3196 Unauthorized changes to hdsl2ShdslMaintPowerBackoff could result 3197 in an increased in bundle interference. 3199 Unauthorized changes to hdsl2ShdslMaintSoftRestart could result in 3200 a temporary interruption of end-to-end data transfer as the result 3201 of the triggering of a soft restart. 3203 o hdsl2ShdslUnitMaintTable 3205 This table contains one object, hdsl2ShdslMaintLoopbackTimeout, 3206 that supports SET operations. An unauthorized change to this 3207 object could result in the timeout value for loopbacks being 3208 increased, decreased, or disabled. 3210 o hdsl2ShdslSpanConfProfileTable 3212 The table consists of the following objects that support SET 3213 operations: 3215 * hdsl2ShdslSpanConfWireInterface 3216 * hdsl2ShdslSpanConfMinLineRate 3217 * hdsl2ShdslSpanConfMaxLineRate 3218 * hdsl2ShdslSpanConfPSD 3219 * hdsl2ShdslSpanConfTransmissionMode 3220 * hdsl2ShdslSpanConfRemoteEnabled 3221 * hdsl2ShdslSpanConfPowerFeeding 3222 * hdsl2ShdslSpanConfCurrCondTargetMarginDown 3223 * hdsl2ShdslSpanConfWorstCaseTargetMarginDown 3224 * hdsl2ShdslSpanConfCurrCondTargetMarginUp 3225 * hdsl2ShdslSpanConfWorstCaseTargetMarginUp 3226 * hdsl2ShdslSpanConfUsedTargetMargins 3227 * hdsl2ShdslSpanConfReferenceClock 3228 * hdsl2ShdslSpanConfLineProbeEnable 3229 * hdsl2ShdslSpanConfProfileRowStatus 3231 Setting any of the objects to an incorrect value could have an 3232 adverse operational effect on a span. 3234 Unauthorized changes to the hdsl2ShdslSpanConfWireInterface could 3235 result in the failure of a span to achieve activation to a state 3236 that would permit data flow. For example, setting this object to 3237 six-wire or eight-wire operation when one of the units in the span 3238 only supports two-wire or four-wire operation would likely prevent 3239 an expected end-to-end data transfer capability. 3241 Unauthorized changes to hdsl2ShdslSpanConfMinLineRate or 3242 hdsl2ShdslSpanConfMaxLineRate could have an adverse effect on 3243 performance. The range of allowable line rates could be altered 3244 such that the span may not be able to train to an line rate that 3245 would permit any end-user data to traverse the span or the span 3246 could train to a line rate that is either greater than or less 3247 than the line rate that the provider has pledged. 3249 Unauthorized changes to hdsl2ShdslSpanConfPSD or 3250 hdsl2ShdslSpanConfTransmissionMode could have a detrimental effect 3251 loop reach, performance, or spectral compatibility. 3253 Unauthorized changes to hdsl2ShdslSpanConfRemoteEnable could alter 3254 the remote management ability of units. 3256 Unauthorized changes to hdsl2ShdslSpanConfPowerFeeding could 3257 shutdown units that are expected to be feed power remotely. 3258 Changing the configuration such that wetting current is not 3259 supplied may result in corrosion of electrical contacts. 3261 Unauthorized changes to 3262 hdsl2ShdslSpanConfCurrCondTargetMarginDown, 3263 hdsl2ShdslSpanConfWorstCaseTargetMarginDown, 3264 hdsl2ShdslSpanConfCurrCondTargetMarginUp, 3265 hdsl2ShdslSpanConfWorstCaseTargetMarginUp, or 3266 hdsl2ShdslSpanConfUsedTargetMargins could result in invalid 3267 parameters used to determine if a data rate can be supported under 3268 current and worst-case noise. 3270 Unauthorized changes to hdsl2ShdslSpanConfReferenceClock could 3271 result in the selection of a clock source which might either 3272 prevent any data from being transferred or impair data transfer. 3273 In addition, an increase in CRC anomalies may be experienced. 3275 Unauthorized changes to hdsl2ShdslSpanConfLineProbeEnable could 3276 have a negative effect on selecting the optimum rate or power 3277 level based on current line conditions. 3279 Unauthorized changes to row status could result in unwanted 3280 profiles being created or brought into service. Also, changes to 3281 the row status could result in profiles being inadvertently 3282 deleted or taken out of service. 3284 o hdsl2ShdslEndpointAlarmConfProfileTable 3286 The table consists of the following objects that support SET 3287 operations: 3289 * hdsl2ShdslEndpointThreshLoopAttenuation 3290 * hdsl2ShdslEndpointThreshSNRMargin 3291 * hdsl2ShdslEndpointThreshES 3292 * hdsl2ShdslEndpointThreshSES 3293 * hdsl2ShdslEndpointThreshCRCanomalies 3294 * hdsl2ShdslEndpointThreshLOSWS 3295 * hdsl2ShdslEndpointThreshUAS 3296 * hdsl2ShdslEndpointAlarmConfProfileRowStatus 3298 Increasing any of the threshold values could result a notification 3299 being suppressed or deferred. Setting a threshold to 0 could 3300 result in a notification being suppressed. Suppressing or 3301 deferring a notification could prevent the timely delivery of 3302 important diagnostic information. Decreasing any of the threshold 3303 values could result in a notification being sent from the network 3304 falsely reporting a threshold crossing. 3306 Changing a threshold value could also have an impact on the amount 3307 of notifications the agent sends. This document adds a paragraph, 3308 which was not in RFC 3276 [RFC3276], to the Notifications Section 3309 which provides general guidance to the rate limiting of 3310 notifications. Agent implementations not adhering to the rate- 3311 limiting desires could result in notifications being generated at 3312 an uncontrolled rate. Unauthorized changes to a threshold value 3313 could result in an undesired notification rate. 3315 Unauthorized changes to row status could result in unwanted 3316 profiles being created or brought into service. Also, changes to 3317 the row status could result in profiles being inadvertently 3318 deleted or taken out of service. 3320 Some of the readable objects in this MIB module (i.e., objects with a 3321 MAX-ACCESS other than not-accessible) may be considered sensitive or 3322 vulnerable in some network environments. It is thus important to 3323 control even GET and/or NOTIFY access to these objects and possibly 3324 to even encrypt the values of these objects when sending them over 3325 the network via SNMP. These are the tables and objects and their 3326 sensitivity/vulnerability: 3328 o hdsl2ShdslInventoryTable 3330 Access to these objects would allow an intruder to obtain 3331 information about which vendor's equipment is in use on the 3332 network. Further, such information is considered sensitive in 3333 many environments for competitive reasons. 3335 * hdsl2ShdslInvVendorID 3336 * hdsl2ShdslInvVendorModelNumber 3337 * hdsl2ShdslInvVendorSerialNumber 3338 * hdsl2ShdslInvVendorEOCSoftwareVersion 3339 * hdsl2ShdslInvStandardVersion 3340 * hdsl2ShdslInvVendorListNumber 3341 * hdsl2ShdslInvVendorIssueNumber 3342 * hdsl2ShdslInvVendorSoftwareVersion 3343 * hdsl2ShdslInvEquipmentCode 3344 * hdsl2ShdslInvVendorOther 3345 * hdsl2ShdslInvTransmissionModeCapability 3347 SNMP versions prior to SNMPv3 did not include adequate security. 3348 Even if the network itself is secure (for example by using IPSec), 3349 even then, there is no control as to who on the secure network is 3350 allowed to access and GET/SET (read/change/create/delete) the objects 3351 in this MIB module. 3353 It is RECOMMENDED that implementers consider the security features as 3354 provided by the SNMPv3 framework (see [RFC3410], Section 8), 3355 including full support for the SNMPv3 cryptographic mechanisms (for 3356 authentication and privacy). 3358 Further, deployment of SNMP versions prior to SNMPv3 is NOT 3359 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 3360 enable cryptographic security. It is then a customer/operator 3361 responsibility to ensure that the SNMP entity giving access to an 3362 instance of this MIB module is properly configured to give access to 3363 the objects only to those principals (users) that have legitimate 3364 rights to indeed GET or SET (change/create/delete) them. 3366 6. Acknowledgments 3368 The authors are deeply grateful to the authors of the ADSL LINE MIB 3369 (RFC 2662 [RFC2662]), Gregory Bathrick and Faye Ly, as much of the 3370 text and structure of this document originates in their documents. 3372 The authors are also grateful to the authors of FR MFR MIB (RFC 3020 3374 [RFC3020]), Prayson Pate, Bob Lynch, and Kenneth Rehbehn, as the 3375 majority of the Security Considerations section was lifted from their 3376 document. 3378 The authors also acknowledge the importance of the contributions and 3379 suggestions regarding interface indexing structures received from 3380 David Horton of CITR. 3382 The authors are extremely thankful to Bert Wijnen, Randy Presuhn, and 3383 C. M. Heard for their extensive review and the many suggestions they 3384 provided. 3386 Other contributions were received from the following: 3388 Matt Beanland (Extel Communications) 3389 Philip Bergstresser (Adtran) 3390 Steve Blackwell (Centillium) 3391 Umberto Bonollo (NEC Australia) 3392 John Egan (Metalink BroadBand) 3393 Yagal Hachmon (RAD) 3394 Mark Johnson (Red Point) 3395 Sharon Mantin (Orckit) 3396 Moti Morgenstern (ECI) 3397 Raymond Murphy (Ericsson) 3398 Lee Nipper (Verilink) 3399 Randy Presuhn (BMC Software) 3400 Katy Sherman (Orckit) 3401 Mike Sneed (ECI) 3402 Jon Turney (DSL Solutions) 3403 Aron Wahl (Memotec) 3404 Jim Wilson (for Mindspeed) 3405 Bert Wijnen (Lucent) 3406 Michael Wrobel (Memotec) 3408 7. References 3410 7.1 Normative References 3412 [G.991.2] Blackwell, S., "Single-Pair High-Speed Digital Subscriber 3413 Line (SHDSL) Transceivers", ITU-T G.991.2, December 2003. 3415 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 3416 Requirement Levels", BCP 14, RFC 2119, March 1997. 3418 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 3419 Schoenwaelder, Ed., "Structure of Management Information 3420 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 3422 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 3423 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 3424 STD 58, RFC 2579, April 1999. 3426 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 3427 "Conformance Statements for SMIv2", STD 58, RFC 2580, 3428 April 1999. 3430 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 3431 MIB", RFC 2863, June 2000. 3433 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 3434 Architecture for Describing Simple Network Management 3435 Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, 3436 December 2002. 3438 [RFC3593] Tesink, K., "Textual Conventions for MIB Modules Using 3439 Performance History Based on 15 Minute Intervals", 3440 RFC 3593, September 2003. 3442 [T1E1.4] American National Standards Institute, "ANSI T1E1.4/ 3443 2000-006", February 2000. 3445 7.2 Informative References 3447 [RFC2662] Bathrick, G. and F. Ly, "Definitions of Managed Objects 3448 for the ADSL Lines", RFC 2662, August 1999. 3450 [RFC3020] Pate, P., Lynch, B., and K. Rehbehn, "Definitions of 3451 Managed Objects for Monitoring and Controlling the UNI/NNI 3452 Multilink Frame Relay Function", RFC 3020, December 2000. 3454 [RFC3276] Ray, B. and R. Abbi, "Definitions of Managed Objects for 3455 High Bit-Rate DSL - 2nd generation (HDSL2) and Single-Pair 3456 High-Speed Digital Subscriber Line (SHDSL) Lines 3457 Processing", RFC 3276, May 2002. 3459 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 3460 "Introduction and Applicability Statements for Internet- 3461 Standard Management Framework", RFC 3410, December 2002. 3463 [RFC3418] Presuhn, R., "Management Information Base (MIB) for the 3464 Simple Network Management Protocol (SNMP)", STD 62, 3465 RFC 3418, December 2002. 3467 Authors' Addresses 3469 Clay Sikes 3470 Paradyne Networks, Inc. 3471 8454 126th Ave. N. 3472 Largo, FL 33773 3473 US 3475 Phone: +1 727 530 8257 3476 Fax: +1 727 532 5698 3477 Email: csikes@paradyne.com 3479 Bob Ray 3480 PESA Switching Systems, Inc. 3481 330-A Wynn Drive 3482 Huntsville, AL 35805 3483 US 3485 Phone: +1 256 726 9200 ext. 142 3486 Fax: +1 256 726 9271 3487 Email: rray@pesa.com 3489 Rajesh Abbi 3490 Alcatel USA 3491 2912 Wake Forest Road 3492 Raleigh, NC 27609-7860 3493 US 3495 Phone: +1 919-850-6194 3496 Fax: +1 919-850-6670 3497 Email: Rajesh.Abbi@alcatel.com 3499 Intellectual Property Statement 3501 The IETF takes no position regarding the validity or scope of any 3502 Intellectual Property Rights or other rights that might be claimed to 3503 pertain to the implementation or use of the technology described in 3504 this document or the extent to which any license under such rights 3505 might or might not be available; nor does it represent that it has 3506 made any independent effort to identify any such rights. Information 3507 on the procedures with respect to rights in RFC documents can be 3508 found in BCP 78 and BCP 79. 3510 Copies of IPR disclosures made to the IETF Secretariat and any 3511 assurances of licenses to be made available, or the result of an 3512 attempt made to obtain a general license or permission for the use of 3513 such proprietary rights by implementers or users of this 3514 specification can be obtained from the IETF on-line IPR repository at 3515 http://www.ietf.org/ipr. 3517 The IETF invites any interested party to bring to its attention any 3518 copyrights, patents or patent applications, or other proprietary 3519 rights that may cover technology that may be required to implement 3520 this standard. Please address the information to the IETF at 3521 ietf-ipr@ietf.org. 3523 The IETF has been notified of intellectual property rights claimed in 3524 regard to some or all of the specification contained in this 3525 document. For more information consult the online list of claimed 3526 rights. 3528 Disclaimer of Validity 3530 This document and the information contained herein are provided on an 3531 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 3532 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 3533 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 3534 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 3535 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 3536 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 3538 Copyright Statement 3540 Copyright (C) The Internet Society (2005). This document is subject 3541 to the rights, licenses and restrictions contained in BCP 78, and 3542 except as set forth therein, the authors retain all their rights. 3544 Acknowledgment 3546 Funding for the RFC Editor function is currently provided by the 3547 Internet Society. 3549 -- Paradyne Mail --