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