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