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