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