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