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