INTERNET-DRAFT B. Ray Verilink Corporation June 2000 Definitions of Managed Objects for HDSL2 and SHDSL Lines draft-ietf-adslmib-hdsl2-01.txt Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC 2026. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. To view the entire list of current Internet-Drafts, please check the "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow Directories on ftp.is.co.za (Africa), ftp.nordu.net (Northern Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au (Pacific Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu (US West Coast). Copyright Notice Copyright (C) The Internet Society (2000). All Rights Reserved. Expires November 8, 2000 Page [1] INTERNET-DRAFT HDSL2-LINE MIB May 2000 Table of Contents 1. Abstract .................................................. 2 2. The SNMPv2 Network Management Framework ................... 2 3. Introduction .............................................. 3 3.1 Relationship of the HDSL2 Line MIB with Standard MIBs ...... 4 4. Conventions used in the MIB ............................... 5 4.1 Naming Conventions ........................................ 5 4.2 Structure ................................................. 5 4.3 Counters, Interval Buckets and Thresholds ................. 7 4.4 Profiles .................................................. 8 4.5 Traps ..................................................... 9 5. Conformance and Compliance ................................ 10 6. Definitions ............................................... 10 7. Security Considerations ................................... 58 8. Acknowledgments ........................................... 58 9. References ................................................ 59 10. Intellectual Property Notice .............................. 60 11. Authors' Addresses ........................................ 61 12. Full Copyright Statement .................................. 61 1. Abstract This document defines an experimental portion of the Management Information Base (MIB) MIB module for use with network management protocols in the Internet community. In particular, it describes objects used for managing HDSL2 and SHDSL interfaces. This document specifies a MIB module in a manner that is both compliant to the SNMPv2 SMI, and semantically identical to the peer SNMPv1 definitions. 2. The SNMP Management Framework The SNMP Management Framework presently consists of five major components: o An overall architecture, described in RFC 2571 [1]. o Mechanisms for describing and naming objects and events for the purpose of management. The first version of this Structure of Management Information (SMI) is called SMIv1 and described in STD 16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4]. The second version, called SMIv2, is described in STD 58, RFC 2578 [5], STD 58, RFC 2579 [6] and STD 58, RFC 2580 [7]. o Message protocols for transferring management information. The first version of the SNMP message protocol is called SNMPv1 and described in STD 15, RFC 1157 [8]. A second version of the SNMP message protocol, which is not an Internet standards track protocol, is called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. The third version of the message protocol is called SNMPv3 and described in RFC 1906 [10], RFC 2572 [11] and Expires November 8, 2000 Page [2] INTERNET-DRAFT HDSL2-LINE MIB May 2000 RFC 2574 [12]. o Protocol operations for accessing management information. The first set of protocol operations and associated PDU formats is described in STD 15, RFC 1157 [8]. A second set of protocol operations and associated PDU formats is described in RFC 1905 [13]. o A set of fundamental applications described in RFC 2573 [14] and the view-based access control mechanism described in RFC 2575 [15]. A more detailed introduction to the current SNMP Management Framework can be found in RFC 2570 [16]. Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the mechanisms defined in the SMI. This memo specifies a MIB module that is compliant to the SMIv2. A MIB conforming to the SMIv1 can be produced through the appropriate translations. The resulting translated MIB must be semantically equivalent, except where objects or events are omitted because no translation is possible (use of Counter64). Some machine readable information in SMIv2 will be converted into textual descriptions in SMIv1 during the translation process. However, this loss of machine readable information is not considered to change the semantics of the MIB. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [17]. 2.1. Object Definitions Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the subset of Abstract Syntax Notation One (ASN.1) defined in the SMI. In particular, each object type is named by an OBJECT IDENTIFIER, an administratively assigned name. The object type together with an object instance serves to uniquely identify a specific instantiation of the object. For human convenience, we often use a textual string, termed the descriptor, to also refer to the object type. 3. Introduction This document describes an SNMP HDSL2 Line MIB which is intended to work with both the SNMPv1 and the SNMPv2. The MIB, however, is based on SNMPv2 Structure of Management Information [18] and SNMPv2 Textual Conventions [19]. This does not, however, mean that either the Agent or Manager must be SNMPv2 protocol compliant. All MIB definitions are backward compatible for SNMPv1 implementation. Expires November 8, 2000 Page [3] INTERNET-DRAFT HDSL2-LINE MIB May 2000 The MIB definitions are attached. These definitions are based upon the specification for the HDSL2 and SHDSL Embedded Operations Channel (EOC) as defined in ANSI T1E1.4/2000-006 [20] and ITU G.991.2 (ex G.SHDSL) [21]. The MIB will eventually be located in the MIB tree under MIB 2 transmission, as discussed in the MIB-2 Integration (RFC 1213 [22] and RFC 2233 [23]) section of this document. Until approved by the IETF, vendors may also choose to support it under their own enterprise IDs. hdsl2LineMIB MODULE-IDENTITY ::= { VendorEnterpriseID nnn } 3.1. Relationship of the HDSL2 Line MIB with Standard MIBs This section outlines the relationship of this MIB with other MIBs described in RFCs and in various degrees of "standardization". Specifically, MIB-2 as presented in RFC 1213 [22] and RFC 2233 [23] is discussed. 3.1.1 General MIB-2 Integration (RFCs 1213 and 2233) The HDSL2 Line MIB specifies the detailed attributes of a data interface. As such, it needs to integrate with RFC 2233 [23]. The IANA has assigned the following ifTypes to HDSL2 and SHDSL: IANAifType ::= TEXTUAL-CONVENTION ... SYNTAX INTEGER { ... hdsl2 (168), -- High Bit-Rate DSL, 2nd generation shdsl (169), -- Multirate HDSL2 ... } Therefore, pending approval of the IETF, RFC 2233 [23] mandates that this MIB will be accessed through one of the two following mib-2.transmission.ifTypes as shown: hdsl2Interface ::= { transmission 168 } shdslInterface ::= { transmission 169 } 3.1.2 Usage of ifTable The MIB branch identified by this ifType contains tables appropriate for this interface type. Most such tables extend the ifEntry table, and are indexed by ifIndex. The following attributes are part of the mandatory ifGeneral group in RFC 2233 [23], and are not duplicated in the HDSL2 Line MIB. =================================================================== ifIndex Interface index. ifDescr See interfaces MIB [23]. Expires November 8, 2000 Page [4] INTERNET-DRAFT HDSL2-LINE MIB May 2000 ifType hdsl2(168) or shdsl(169). ifSpeed Set as appropriate. For HDSL2 lines, this is fixed at 1552000. ifPhysAddress This object should have an octet string with zero length. ifAdminStatus See interfaces MIB [23]. ifOperStatus See interfaces MIB [23]. ifLastChange See interfaces MIB [23]. ifName See interfaces MIB [23]. ifLinkUpDownTrapEnable Default to enabled(1). ifHighSpeed Set as appropriate. For HDSL2 lines, this is fixed at 2. ifConnectorPresent Set as appropriate. =================================================================== Figure 1: Use of ifTable Objects 4. Conventions used in the MIB 4.1. Naming Conventions A. htuC refers to a central site terminal unit; a HDSL2 H2TU-C or a SHDSL STU-C. B. htuR refers to a remote site terminal unit; either a HDSL2 H2TU-R or a SHDSL STU-R. C. htu refers to a terminal unit; either an htuC or htuR. D. hru refer to a regenerator unit; either a HDSL2 H2RU or a SHDSL SRU. E. hu refers to any HDSL2 unit; either an htu or hru. F. CRC is cyclic redundancy check. G. CVL means Code Violation - Line. H. ES means errored second. I. LOS means loss of signal. J. LOSS means loss of signal second. K. LOSW means loss of sync word, distinct from LOS. L. LOSWS means LOSW second. M. SES means severely errored second. N. SNR means signal-to-noise ratio. O. UAS means unavailable second. 4.2. Structure The MIB has tables for: o HU inventory Expires November 8, 2000 Page [5] INTERNET-DRAFT HDSL2-LINE MIB May 2000 o line topology o HU performance - Current and up to 96 buckets of 15 minute performance history - Current and up to 30 buckets of 24 hour performance history o HTU DS1 performance - Current and up to 96 buckets of 15 min performance history - Current and up to 30 buckets of 24 hour performance history o profiles - configuration and alarm parameters o maintenance - test configuration and control parameters 4.2.1 Line Topology An HDSL2 Line consists of a minimum of two HDSL2 modems. These modems are the HTU-C, for central site terminal unit, and HTU-R, for remote site terminal unit. Further, between these two units are from one to eight optional regenerators, called HRUs. Each HRU contains two HDSL2 modems, one on the network side which communicates "upstream" towards the HTU-C, and one on the customer side which communicates "downstream" towards the HTU-R. For the purposes of this MIB, each HDSL2 modem, whether resident in an HTU or HRU, is considered an "endpoint". The relationship between physical equipment inventory and the endpoints is accomplished through the use of three tables: o hdsl2LineTable, which defines the number of repeaters on a HDSL2 line for the purpose of pre-provisioning o hdsl2InventoryTable, which contains equipment inventory information o hdsl2EndpointConfTable, which identifies each endpoint Two textual conventions are introduced to assist in the topological configuration: o Hdsl2UnitId, which mirrors the EOC addressing mechanism: htuC(1) - CO terminal unit htuR(2) - CPE terminal unit hru1(3) .. hru8(10) - regenerators, numbered from central office side o Hdsl2ModemId, which enumerates the four possible modems on an inventory unit: Expires November 8, 2000 Page [6] INTERNET-DRAFT HDSL2-LINE MIB May 2000 networkSide1(1) - HDSL2 and SHDSL pair 1 networkSide2(2) - SHDSL 4-wire implementation, pair 2 customerSide1(3) - HDSL2 and SHDSL pair 1 customerSide2(4) - SHDSL 4-wire implementation, pair 2 For example, consider the following HDSL2 line: +-------+ +-----+ +-------+ | HTU-C +---+ HRU +---+ HTU-R | +-------+ +-----+ +-------+ Figure 2: Sample HDSL2 line The following table entries would represent this line: Inventory Endpoint Hdsl2ModemId --------- -------- ---------------- htuC(1) 1 customerSide1(3) htuR(2) 2 networkSide1(1) hru1(3) 3 networkSide1(1) 4 customerSide1(3) Figure 3: Sample HDSL2 line topology For a 4-wire SHDSL Line, the following table entries would represent the line: Inventory Endpoint Hdsl2ModemId --------- -------- ---------------- htuC(1) 1 customerSide1(3) 2 customerSide2(4) htuR(2) 3 networkSide1(1) 4 networkSide2(2) hru1(3) 5 networkSide1(1) 6 networkSide2(2) 7 customerSide1(3) 8 customerSide2(4) Figure 4: Sample 4-wire SHDSL line topology 4.3. Counters, Interval Buckets and Thresholds For SNR Margin, Loop Attenuation, ES, SES, CRC anomalies, LOSWS, and UAS, there are event counters, current 15-minute and one (up to 96) 15-minute history bucket(s) of "interval-counters", as well as current and one (up to 30) previous 1-day interval-counter(s). Each current 15-minute event bucket has an associated threshold trap. The buckets are defined using the textual conventions of RFC 2493 [24]. For HDSL2 implementations which support DS1 interfaces on the HTUs, there are similar counters, buckets, and thresholds for DS1 ES, DS1 SES, DS1 CV-L, and DS1 LOSS. Expires November 8, 2000 Page [7] INTERNET-DRAFT HDSL2-LINE MIB May 2000 Unlike RFC 2493 [24] and RFC 2662 [25], there is no representation in the MIB for invalid buckets. In those cases where the data for an interval is suspect or known to be invalid, the agent should not report the interval. There is no requirement for an agent to ensure a fixed relationship between the start of a fifteen minute and any wall clock; however some implementations may align the fifteen minute intervals with quarter hours. Likewise, an implementation may choose to align one day intervals with the start of a day. Counters are not reset when an HU is reinitialized, only when the agent is reset or reinitialized (or under specific request outside the scope of this MIB). 4.4. Profiles As a managed node can handle a large number of HUs, (e.g., hundreds or perhaps thousands of HDSL2 lines), provisioning every parameter on every HU may become burdensome. In response, five MIB tables have been created to define HDSL2 equipment configuration data profiles, as well as a mechanism to associate the equipment to these profiles. The five tables are: o hdsl2LineTable, used to specify the number of regenerators (repeaters) in a line. While this information is available following the EOC discovery process, it is not otherwise available for pre-provisioning of a line. For this reason, this table allows a user to specify the number of regenerators on a line prior to the discovery process. o hdsl2EndpointAlarmConfProfileTable, used for configuring alarm thresholds for each endpoint. o hdsl2DS1ProfileTable, used for configuring DS1-specific interfaces. This group is optional for SDHSL interfaces. o hdsl2DS1AlarmConfProfileTable, used for configuring DS1-specific alarm thresholds. This group is optional for SHDSL interfaces. o hdsl2ShdslProfileTable, used for configuring SHDSL lines. This group is optional for HDSL2 interfaces. Implementations will enable the manager to dynamically create and delete profiles as needed. The index of each profile is a locally- unique administratively assigned name for the profile having the textual convention `SnmpAdminString' (RFC 2571 [26]). One or more HDSL2 lines may be configured to share parameters of a single profile (e.g., hdsl2EndpointAlarmConfProfile = `silver') by setting its hdsl2EndpointAlarmConfProfile objects to the value of this profile. If a change is made to the profile, all lines that refer Expires November 8, 2000 Page [8] INTERNET-DRAFT HDSL2-LINE MIB May 2000 to it will be reconfigured to the changed parameters. Before a profile can be deleted or taken out of service it must be first unreferenced from all associated lines. Implementations must provide a default profile whose name is `DEFVAL' for each profile type. The values of the associated parameters will be vendor specific unless otherwise indicated in this document. Before a line's profiles have been set, these profiles will be automatically used by setting hdsl2EndpointAlarmConfProfile, hdsl2ShdslProfile, hdsl2DS1ConfProfile, and hdsl2DS1AlarmConfProfile to `DEFVAL' where appropriate. Profiles are created, assigned, and deleted dynamically using the profile name and profile row status in each of the four profile tables. Changes to alarm profiles MUST take effect immediately. Changes to non-alarm profiles MAY be deferred until the next restart (hard reset or soft restart) of the units on the line. Vendors MAY choose to have the non-alarm profile changes take effect immediately. Alarm profiles are those profile settings found in the hdsl2EndpointAlarmConfProfileTable and the (optional) hdsl2DS1AlarmConfProfileTable. Non-alarm profiles are those profile settings found in the hdsl2LineTable and the (optional) hdsl2DS1ProfileTable and hdsl2ShdslProfileTable. 4.5. Traps The ability to generate the SNMP traps coldStart/WarmStart (per [23]) which are per agent (e.g., per DSLAM in such a device), and linkUp / linkDown (per [23]) -- which are per interface (i.e., HDSL2 line) is required. A linkDown trap may be generated whenever any of ES, SES, CRC Anomaly, LOSWS, or UAS event occurs. At this operational point, a manager can use hdsl2EndpointCurrStatus for additional detailed information. The corresponding linkUp trap may be sent when all link failure conditions are cleared. The traps defined in this MIB are for initialization failure and for the threshold crossings associated with the following events: ES, SES, CRC Anomaly, LOSWS, UAS, DS1 ES, DS1 SES, DS1 CVL, and DS1 LOSS. Each threshold has its own enable/threshold value. When that value is 0, the trap is disabled. The current status object, hdsl2EndpointCurrStatus, indicates, through a bitmask, all outstanding error conditions or that the line is operational. Note that this object claims to represent the status of a particular HDSL2 interface. However, since the SNMP agent likely co-resides with only one end of the line such as a HTU-C, the status object for interfaces 'down the line' (such as HRUs and the HTU-R) may be incomplete. For example, when there are errors on the line, the far-end HTU may not be able to correctly report this condition. Therefore, not all conditions are included in its current Expires November 8, 2000 Page [9] INTERNET-DRAFT HDSL2-LINE MIB May 2000 status. A threshold trap occurs whenever the corresponding current 15-minute interval error counter becomes equal and/or exceeds to the threshold value. One trap may be sent per interval per interface. Since the current 15-minute counter are reset to 0 every 15 minutes, if the condition persists, the trap may recur as often as every 15 minutes. For example, to get a trap whenever a "loss of" event occurs (but at most once every 15 minutes), set the corresponding threshold to 1. The agent will generate a trap when the event originally occurs. Note that the NMS may receive a linkDown trap, as well, if enabled. At the beginning of the next 15 minute interval, the counter is reset. When the first second goes by and the event occurs, the current interval bucket will be 1, which equals the threshold and the trap will be sent again. 5. Conformance and Compliance The MIB is organized to cover all elements of an HDSL2 line. In addition, objects have been added to provide support for SHDSL lines. For both HDSL2 and SHDSL lines, the following groups are mandatory: hdsl2LineGroup hdsl2InventoryGroup hdsl2EndpointGroup hdsl2IntervalGroup hdsl2HistoryGroup hdsl2MaintenanceGroup hdsl2EndpointAlarmConfGroup hdsl2NotificationGroup For HDSL2 lines, the following groups are optional: hdsl2ShdslGroup hdsl2ShdslProfileGroup For SHDSL lines, the following groups are optional: hdsl2DS1ConfigGroup hdsl2DS1PerfGroup hdsl2DS1IntervalGroup hdsl2DS1HistoryGroup hdsl2DS1ProfileGroup hdsl2DS1NotificationGroup 6. Definitions HDSL2-LINE-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, Expires November 8, 2000 Page [10] INTERNET-DRAFT HDSL2-LINE MIB May 2000 OBJECT-TYPE, Counter32, Gauge32, NOTIFICATION-TYPE, Integer32, enterprises FROM SNMPv2-SMI DisplayString, RowStatus, TEXTUAL-CONVENTION FROM SNMPv2-TC ifIndex FROM RFC1213-MIB PerfCurrentCount, PerfIntervalCount FROM PerfHist-TC-MIB SnmpAdminString FROM SNMP-FRAMEWORK-MIB MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP FROM SNMPv2-CONF; hdsl2MIB MODULE-IDENTITY LAST-UPDATED "0006290000Z" -- June 29, 2000 ORGANIZATION "ADSLMIB Working Group" CONTACT-INFO " Bob Ray Verilink Corporation 127 Jetplex Circle Madison, AL 35758 USA Tel: +1 256-774-2380 Fax: +1 256-774-2277 E-mail: bray@verilink.com " DESCRIPTION "The MIB module defining objects for the management of a series of HDSL2/SHDSL modems on a HDSL2/SHDSL line. An agent may reside at either end of the line, however the MIB is designed to require no management communication between the modems beyond that inherent in the low-level EOC line protocol as defined in ANSI T1E1.4/2000-006 (for HDSL2 lines), or in ITU G.991.2 (for SHDSL lines). The agent may monitor and control this protocol for its needs." ::= { enterprises 999999 } hdsl2LineMib OBJECT IDENTIFIER ::= { hdsl2MIB 1 } hdsl2MibObjects OBJECT IDENTIFIER ::= { hdsl2LineMib 1 } -- temporary assignment clause used for compilation -- reasons only. Upon assignment by the IETF, this -- value will be changed. During this interim Expires November 8, 2000 Page [11] INTERNET-DRAFT HDSL2-LINE MIB May 2000 -- period, it is recommended that implementors of -- this MIB assign this to a point under their -- private enterprise assignment tree. -- Textual conventions used in MIB -- Hdsl2PerfCurrDayCount ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "A counter associated with interface performance measurements in a current 1-day (24 hour) measurement interval. The value of this counter starts at zero at the beginning of an interval and is increased when associated events occur, until the end of the 1-day interval. At that time the value of the counter is stored in the previous 1-day history interval, if available, and the current interval counter is restarted at zero. In the case where the agent has no valid data available for this interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation)." SYNTAX Gauge32 Hdsl2HistoryCount ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "A counter associated with interface performance measurements during the most previous 1-day (24 hour) measurement interval. The value of this counter is equal to the value of the current day counter at the end of its most recent interval. In the case where the agent has no valid data available for this interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation)." SYNTAX Gauge32 Hdsl2PerfTimeElapsed ::= TEXTUAL-CONVENTION STATUS current Expires November 8, 2000 Page [12] INTERNET-DRAFT HDSL2-LINE MIB May 2000 DESCRIPTION "The number of seconds that have elapsed since the beginning of the current measurement period. If, for some reason, such as an adjustment in the system's time-of-day clock, the current interval exceeds the maximum value, the agent will return the maximum value." SYNTAX Gauge32 Hdsl2UnitId ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The EOC unit addressing scheme. The optional regenerators/repeaters are numbered sequentially 1..8 from the HTU-C." SYNTAX INTEGER { htuC(1), htuR(2), hru1(3), hru2(4), hru3(5), hru4(6), hru5(7), hru6(8), hru7(9), hru8(10) } Hdsl2ModemId ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "An enumeration which represents the four possible modems (endpoints) in a HDSL2 unit. The following list identifies the modems which populate a given inventory unit. Unit ModemId ----------------- ------------------ HDSL2 HTU-C customerSide1 HDSL2 HTU-R networkSide1 HDSL2 HRU networkSide1 customerSide1 SHDSL HTU-C 2-wire customerSide1 SHDSL HTU-R 2-wire networkSide1 SHDSL HRU 2-wire networkSide1 customerSide1 SHDSL HTU-C 4-wire customerSide1 customerSide2 SHDSL HTU-R 4-wire networkSide1 networkSide2 Expires November 8, 2000 Page [13] INTERNET-DRAFT HDSL2-LINE MIB May 2000 SHDSL HRU 4-wire networkSide1 networkSide2 customerSide1 customerSide2" SYNTAX INTEGER { networkSide1(1), networkSide2(2), customerSide1(3), customerSide2(4) } -- Inventory group -- hdsl2LineTable OBJECT-TYPE SYNTAX SEQUENCE OF Hdsl2LineTableEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Defines the number of repeaters in each HDSL2 line." ::= { hdsl2MibObjects 1 } hdsl2LineTableEntry OBJECT-TYPE SYNTAX Hdsl2LineTableEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the hdsl2LineTable." INDEX { ifIndex } ::= { hdsl2LineTable 1 } Hdsl2LineTableEntry ::= SEQUENCE { hdsl2LineNumRepeaters INTEGER } hdsl2LineNumRepeaters OBJECT-TYPE SYNTAX INTEGER(0..8) MAX-ACCESS read-write STATUS current DESCRIPTION "Specifies the number of repeaters on the HDSL2 line." ::= { hdsl2LineTableEntry 1 } hdsl2InventoryTable OBJECT-TYPE SYNTAX SEQUENCE OF Hdsl2InventoryEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table includes common attributes describing elements of an HDSL2 line. It is required for all Expires November 8, 2000 Page [14] INTERNET-DRAFT HDSL2-LINE MIB May 2000 HDSL2 physical interfaces. HDSL2 physical interfaces are those ifEntries where ifType is equal to hdsl2(168) or shdsl(169)." ::= { hdsl2MibObjects 2 } hdsl2InventoryEntry OBJECT-TYPE SYNTAX Hdsl2InventoryEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the hdsl2InventoryTable." INDEX { ifIndex, hdsl2InvIndex } ::= { hdsl2InventoryTable 1 } Hdsl2InventoryEntry ::= SEQUENCE { hdsl2InvIndex Hdsl2UnitId, hdsl2InvVendorID Integer32, hdsl2InvVendorModelNumber DisplayString, hdsl2InvVendorSerialNumber DisplayString, hdsl2InvVendorEOCSoftwareVersion Integer32, hdsl2Invhdsl2StandardVersion Integer32, hdsl2InvVendorListNumber DisplayString, hdsl2InvVendorIssueNumber DisplayString, hdsl2InvVendorSoftwareVersion DisplayString, hdsl2InvEquipmentCode DisplayString, hdsl2InvVendorOther DisplayString } hdsl2InvIndex OBJECT-TYPE SYNTAX Hdsl2UnitId MAX-ACCESS read-only STATUS current DESCRIPTION "The index into the hdsl2InventoryTable." ::= { hdsl2InventoryEntry 1 } hdsl2InvVendorID OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "Vendor ID as reported in an Inventory Response message." ::= { hdsl2InventoryEntry 2 } hdsl2InvVendorModelNumber OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS current DESCRIPTION "Vendor model number as reported in an Inventory Expires November 8, 2000 Page [15] INTERNET-DRAFT HDSL2-LINE MIB May 2000 Response message." ::= { hdsl2InventoryEntry 3 } hdsl2InvVendorSerialNumber OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS current DESCRIPTION "Vendor serial number as reported in an Inventory Response message." ::= { hdsl2InventoryEntry 4 } hdsl2InvVendorEOCSoftwareVersion OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "Vendor EOC version as reported in an Inventory Response message." ::= { hdsl2InventoryEntry 5 } hdsl2Invhdsl2StandardVersion OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "Vendor HDSL2 standard version number as reported in an Inventory Response message." ::= { hdsl2InventoryEntry 6 } hdsl2InvVendorListNumber OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS current DESCRIPTION "Vendor list number as reported in an Inventory Response message." ::= { hdsl2InventoryEntry 7 } hdsl2InvVendorIssueNumber OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS current DESCRIPTION "Vendor issue number as reported in an Inventory Response message." ::= { hdsl2InventoryEntry 8 } hdsl2InvVendorSoftwareVersion OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS current DESCRIPTION Expires November 8, 2000 Page [16] INTERNET-DRAFT HDSL2-LINE MIB May 2000 "Vendor software version as reported in an Inventory Response message." ::= { hdsl2InventoryEntry 9 } hdsl2InvEquipmentCode OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS current DESCRIPTION "Equipment code conforming to ANSI T1.213, Coded Identification of Equipment Entities." ::= { hdsl2InventoryEntry 10 } hdsl2InvVendorOther OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS current DESCRIPTION "Other vendor information as reported in an Inventory response message." ::= { hdsl2InventoryEntry 11 } -- SHDSL support group -- hdsl2ShdslTable OBJECT-TYPE SYNTAX SEQUENCE OF Hdsl2ShdslEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table provides for a SHDSL configuration record. It is required for all SHDSL physical interfaces. SHDSL physical interfaces are those ifEntries where ifType is equal to shdsl(169)." ::= { hdsl2MibObjects 3 } hdsl2ShdslEntry OBJECT-TYPE SYNTAX Hdsl2ShdslEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the hdsl2ShdslTable." INDEX { ifIndex } ::= { hdsl2ShdslTable 1 } Hdsl2ShdslEntry ::= SEQUENCE { hdsl2ShdslWireInterface INTEGER, hdsl2ShdslProfile SnmpAdminString } hdsl2ShdslWireInterface OBJECT-TYPE Expires November 8, 2000 Page [17] INTERNET-DRAFT HDSL2-LINE MIB May 2000 SYNTAX INTEGER { twoWire(1), fourWire(2) } MAX-ACCESS read-only STATUS current DESCRIPTION "Specifies if the unit has a 2 or 4 wire interface." ::= { hdsl2ShdslEntry 1 } hdsl2ShdslProfile OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-write STATUS current DESCRIPTION "The value of this object identifies the row in the SHDSL Configuration Profile Table, hdsl2ShdslProfileTable, which applies to this SHDSL line. In the case which the configuration profile has not been set, the value will be set to 'DEFVAL'." ::= { hdsl2ShdslEntry 2 } -- Endpoint group -- hdsl2EndpointConfTable OBJECT-TYPE SYNTAX SEQUENCE OF Hdsl2EndpointConfEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains configuration information for an HDSL2 endpoint. Each row in this table represents an endpoint in a HDSL2 line. An endpoint is considered an end of a HDSL2 segment; the modem on each end of a HDSL2 segment." ::= { hdsl2MibObjects 4 } hdsl2EndpointConfEntry OBJECT-TYPE SYNTAX Hdsl2EndpointConfEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the hdsl2EndpointConfTable." INDEX { ifIndex, hdsl2EndpointIndex } ::= { hdsl2EndpointConfTable 1 } Hdsl2EndpointConfEntry ::= SEQUENCE { hdsl2EndpointIndex Integer32, hdsl2EndpointUnit Hdsl2UnitId, Expires November 8, 2000 Page [18] INTERNET-DRAFT HDSL2-LINE MIB May 2000 hdsl2EndpointModem Hdsl2ModemId, hdsl2EndpointAlarmConfProfile SnmpAdminString } hdsl2EndpointIndex OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The index into the hdsl2EndpointConfTable." ::= { hdsl2EndpointConfEntry 1 } hdsl2EndpointUnit OBJECT-TYPE SYNTAX Hdsl2UnitId MAX-ACCESS read-only STATUS current DESCRIPTION "The HU associated with the endpoint; an entry in the hdsl2InventoryTable." ::= { hdsl2EndpointConfEntry 2 } hdsl2EndpointModem OBJECT-TYPE SYNTAX Hdsl2ModemId MAX-ACCESS read-only STATUS current DESCRIPTION "The modem on the unit." ::= { hdsl2EndpointConfEntry 3 } hdsl2EndpointAlarmConfProfile OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-write STATUS current DESCRIPTION "The value of this object identifies the row in the HDSL2 Line Alarm Configuration Profile Table, hdsl2LineAlarmConfProfileTable, which applies to this HDSL2 endpoint. In the case which the configuration profile has not been set, the value will be set to 'DEFVAL'." ::= { hdsl2EndpointConfEntry 4 } hdsl2EndpointTable OBJECT-TYPE SYNTAX SEQUENCE OF Hdsl2EndpointEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains a row for each endpoint in a HDSL2 line. An endpoint is considered an end of a HDSL2 segment; the modem on each end of a HDSL2 segment." ::= { hdsl2MibObjects 5 } Expires November 8, 2000 Page [19] INTERNET-DRAFT HDSL2-LINE MIB May 2000 hdsl2EndpointEntry OBJECT-TYPE SYNTAX Hdsl2EndpointEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the hdsl2Endpoint Table." INDEX { ifIndex, hdsl2EndpointIndex } ::= { hdsl2EndpointTable 1 } Hdsl2EndpointEntry ::= SEQUENCE { hdsl2EndpointCurrAtn Integer32, hdsl2EndpointCurrSnrMgn Integer32, hdsl2EndpointCurrStatus Integer32, hdsl2EndpointES Counter32, hdsl2EndpointSES Counter32, hdsl2EndpointCRCanomaly Counter32, hdsl2EndpointLOSWS Counter32, hdsl2EndpointUAS Counter32, hdsl2EndpointCurr15MinTimeElapsed Hdsl2PerfTimeElapsed, hdsl2EndpointCurr15MinES PerfCurrentCount, hdsl2EndpointCurr15MinSES PerfCurrentCount, hdsl2EndpointCurr15MinCRCanomaly PerfCurrentCount, hdsl2EndpointCurr15MinLOSWS PerfCurrentCount, hdsl2EndpointCurr15MinUAS PerfCurrentCount, hdsl2EndpointCurr1DayTimeElapsed Hdsl2PerfTimeElapsed, hdsl2EndpointCurr1DayES Hdsl2PerfCurrDayCount, hdsl2EndpointCurr1DaySES Hdsl2PerfCurrDayCount, hdsl2EndpointCurr1DayCRCanomaly Hdsl2PerfCurrDayCount, hdsl2EndpointCurr1DayLOSWS Hdsl2PerfCurrDayCount, hdsl2EndpointCurr1DayUAS Hdsl2PerfCurrDayCount } hdsl2EndpointCurrAtn OBJECT-TYPE SYNTAX Integer32 UNITS "dB" MAX-ACCESS read-only STATUS current DESCRIPTION "The current loop attenuation for this endpoint as reported in a Network or Customer Side Performance Status message." ::= { hdsl2EndpointEntry 1 } hdsl2EndpointCurrSnrMgn OBJECT-TYPE SYNTAX Integer32 UNITS "dB" MAX-ACCESS read-only STATUS current Expires November 8, 2000 Page [20] INTERNET-DRAFT HDSL2-LINE MIB May 2000 DESCRIPTION "The current SNR margin for this endpoint as reported in a Status Response/SNR message." ::= { hdsl2EndpointEntry 2 } hdsl2EndpointCurrStatus OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "Contains the current state of the endpoint. This is a bit-map of possible conditions. The various bit positions are: 1 noDefect There no defects on the line 2 powerBackoff Indicates enhanced Power Backoff 4 deviceFault Indicates a vendor-dependent detection of diagnostics or self-test results 8 dcContinuityFault Indicates vendor-dependent conditions that interfere with span powering such as short and open circuits 16 snrMarginAlarm Indicates that the SNR margin has exceeded the alarm threshold 32 loopAttenuationAlarm Indicates that the loop attentuation has exceeded the alarm threshold 64 loswFailureAlarm Indicates a forward LOSW alarm 128 configInitFailure Endpoint failure during initialization due to paired endpoint not able to support requested configuration 256 protocolInitFailure Endpoint failure during initialization due to incompatible protocol used by the paired endpoint. 512 noNeighborPresent Endpoint failure during initialization due to no activation sequence detected from paired endpoint. This is intended to supplement ifOperStatus." ::= { hdsl2EndpointEntry 3 } hdsl2EndpointES OBJECT-TYPE SYNTAX Counter32 UNITS "seconds" Expires November 8, 2000 Page [21] INTERNET-DRAFT HDSL2-LINE MIB May 2000 MAX-ACCESS read-only STATUS current DESCRIPTION "Count of Errored Seconds (ES) on this endpoint since the HU was last restarted." ::= { hdsl2EndpointEntry 4 } hdsl2EndpointSES OBJECT-TYPE SYNTAX Counter32 UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of Severely Errored Seconds (SES) on this endpoint since the HU was last restarted." ::= { hdsl2EndpointEntry 5 } hdsl2EndpointCRCanomaly OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Count of CRC anomalies on this endpoint since the HU was last restarted." ::= { hdsl2EndpointEntry 6 } hdsl2EndpointLOSWS OBJECT-TYPE SYNTAX Counter32 UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of Loss of Sync Word (LOSW) Seconds on this endpoint since the HU was last restarted." ::= { hdsl2EndpointEntry 7 } hdsl2EndpointUAS OBJECT-TYPE SYNTAX Counter32 UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of Unavailable Seconds (UAS) on this endpoint since the HU was last restarted." ::= { hdsl2EndpointEntry 8 } hdsl2EndpointCurr15MinTimeElapsed OBJECT-TYPE SYNTAX Hdsl2PerfTimeElapsed UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Total elapsed seconds in this interval." Expires November 8, 2000 Page [22] INTERNET-DRAFT HDSL2-LINE MIB May 2000 ::= { hdsl2EndpointEntry 9 } hdsl2EndpointCurr15MinES OBJECT-TYPE SYNTAX PerfCurrentCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of Errored Seconds (ES) in the current 15 minute interval." ::= { hdsl2EndpointEntry 10 } hdsl2EndpointCurr15MinSES OBJECT-TYPE SYNTAX PerfCurrentCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of Severely Errored Seconds (SES) in the current 15 minute interval." ::= { hdsl2EndpointEntry 11 } hdsl2EndpointCurr15MinCRCanomaly OBJECT-TYPE SYNTAX PerfCurrentCount MAX-ACCESS read-only STATUS current DESCRIPTION "Count of CRC anomalies in the current 15 minute interval." ::= { hdsl2EndpointEntry 12 } hdsl2EndpointCurr15MinLOSWS OBJECT-TYPE SYNTAX PerfCurrentCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of Loss of Sync Word (LOSW) Seconds in the current 15 minute interval." ::= { hdsl2EndpointEntry 13 } hdsl2EndpointCurr15MinUAS OBJECT-TYPE SYNTAX PerfCurrentCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of Unavailable Seconds (UAS) in the current 15 minute interval." ::= { hdsl2EndpointEntry 14 } hdsl2EndpointCurr1DayTimeElapsed OBJECT-TYPE SYNTAX Hdsl2PerfTimeElapsed Expires November 8, 2000 Page [23] INTERNET-DRAFT HDSL2-LINE MIB May 2000 UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Number of seconds that have elapsed since the beginning of the current 1-day interval." ::= { hdsl2EndpointEntry 15 } hdsl2EndpointCurr1DayES OBJECT-TYPE SYNTAX Hdsl2PerfCurrDayCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of Errored Seconds (ES) during the current day as measured by hdslPerfCurr1DayTimeElapsed." ::= { hdsl2EndpointEntry 16 } hdsl2EndpointCurr1DaySES OBJECT-TYPE SYNTAX Hdsl2PerfCurrDayCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of Severely Errored Seconds (SES) during the current day as measured by hdslPerfCurr1DayTimeElapsed." ::= { hdsl2EndpointEntry 17 } hdsl2EndpointCurr1DayCRCanomaly OBJECT-TYPE SYNTAX Hdsl2PerfCurrDayCount MAX-ACCESS read-only STATUS current DESCRIPTION "Count of CRC anomalies during the current day as measured by hdslPerfCurr1DayTimeElapsed." ::= { hdsl2EndpointEntry 18 } hdsl2EndpointCurr1DayLOSWS OBJECT-TYPE SYNTAX Hdsl2PerfCurrDayCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of Loss of Sync Word (LOSW) Seconds during the current day as measured by hdslPerfCurr1DayTimeElapsed." ::= { hdsl2EndpointEntry 19 } hdsl2EndpointCurr1DayUAS OBJECT-TYPE SYNTAX Hdsl2PerfCurrDayCount UNITS "seconds" MAX-ACCESS read-only Expires November 8, 2000 Page [24] INTERNET-DRAFT HDSL2-LINE MIB May 2000 STATUS current DESCRIPTION "Count of Unavailable Seconds (UAS) during the current day as measured by hdslPerfCurr1DayTimeElapsed." ::= { hdsl2EndpointEntry 20 } -- interval group -- hdsl2IntervalTable OBJECT-TYPE SYNTAX SEQUENCE OF Hdsl2IntervalEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table provides one row for each HDSL2 endpoint performance data collection interval." ::= { hdsl2MibObjects 6 } hdsl2IntervalEntry OBJECT-TYPE SYNTAX Hdsl2IntervalEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the hdsl2IntervalTable." INDEX { ifIndex, hdsl2EndpointIndex, hdsl2IntervalNumber } ::= { hdsl2IntervalTable 1 } Hdsl2IntervalEntry ::= SEQUENCE { hdsl2IntervalNumber INTEGER, hdsl2IntervalES PerfIntervalCount, hdsl2IntervalSES PerfIntervalCount, hdsl2IntervalCRCanomaly PerfIntervalCount, hdsl2IntervalLOSWseconds PerfIntervalCount, hdsl2IntervalUAS PerfIntervalCount } hdsl2IntervalNumber OBJECT-TYPE SYNTAX INTEGER(1..96) MAX-ACCESS not-accessible STATUS current DESCRIPTION "Performance Data Interval number. 1 is the the most recent previous interval; interval 96 is 24 hours ago. Intervals 2..96 are optional." ::= { hdsl2IntervalEntry 1 } hdsl2IntervalES OBJECT-TYPE SYNTAX PerfIntervalCount UNITS "seconds" MAX-ACCESS read-only Expires November 8, 2000 Page [25] INTERNET-DRAFT HDSL2-LINE MIB May 2000 STATUS current DESCRIPTION "Count of Errored Seconds (ES) during the interval." ::= { hdsl2IntervalEntry 2 } hdsl2IntervalSES OBJECT-TYPE SYNTAX PerfIntervalCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of Severely Errored Seconds (SES) during the interval." ::= { hdsl2IntervalEntry 3 } hdsl2IntervalCRCanomaly OBJECT-TYPE SYNTAX PerfIntervalCount MAX-ACCESS read-only STATUS current DESCRIPTION "Count of CRC anomalies during the interval." ::= { hdsl2IntervalEntry 4 } hdsl2IntervalLOSWseconds OBJECT-TYPE SYNTAX PerfIntervalCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of Loss of Sync Word (LOSW) Seconds during the interval." ::= { hdsl2IntervalEntry 5 } hdsl2IntervalUAS OBJECT-TYPE SYNTAX PerfIntervalCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of Unavailable Seconds (UAS) during the interval." ::= { hdsl2IntervalEntry 6 } -- history group -- hdsl2HistoryTable OBJECT-TYPE SYNTAX SEQUENCE OF Hdsl2HistoryEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table provides one row for each HDSL2 endpoint performance data collection interval." Expires November 8, 2000 Page [26] INTERNET-DRAFT HDSL2-LINE MIB May 2000 ::= { hdsl2MibObjects 7 } hdsl2HistoryEntry OBJECT-TYPE SYNTAX Hdsl2HistoryEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the hdsl2HistoryTable." INDEX { ifIndex, hdsl2EndpointIndex, hdsl2HistoryInterval } ::= { hdsl2HistoryTable 1 } Hdsl2HistoryEntry ::= SEQUENCE { hdsl2HistoryInterval INTEGER, hdsl2HistoryMoniSecs Hdsl2PerfTimeElapsed, hdsl2HistoryES Hdsl2HistoryCount, hdsl2HistorySES Hdsl2HistoryCount, hdsl2HistoryCRCanomaly Hdsl2HistoryCount, hdsl2HistoryLOSWS Hdsl2HistoryCount, hdsl2HistoryUAS Hdsl2HistoryCount } hdsl2HistoryInterval OBJECT-TYPE SYNTAX INTEGER(1..30) MAX-ACCESS not-accessible STATUS current DESCRIPTION "History Data Interval number. Interval 1 is the the most recent previous day; interval 30 is 30 days ago. Intervals 2..30 are optional." ::= { hdsl2HistoryEntry 1 } hdsl2HistoryMoniSecs OBJECT-TYPE SYNTAX Hdsl2PerfTimeElapsed MAX-ACCESS read-only STATUS current DESCRIPTION "The amount of time in the 1-day interval over which the performance monitoring information is actually counted. This value will be the same as the interval duration except in a situation where performance monitoring data could not be collected for any reason." ::= { hdsl2HistoryEntry 2 } hdsl2HistoryES OBJECT-TYPE SYNTAX Hdsl2HistoryCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of Errored Seconds (ES) during the 1-day interval as measured by hdsl2HistoryMoniSecs." Expires November 8, 2000 Page [27] INTERNET-DRAFT HDSL2-LINE MIB May 2000 ::= { hdsl2HistoryEntry 3 } hdsl2HistorySES OBJECT-TYPE SYNTAX Hdsl2HistoryCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of Severely Errored Seconds (SES) during the 1-day interval as measured by hdsl2HistoryMoniSecs." ::= { hdsl2HistoryEntry 4 } hdsl2HistoryCRCanomaly OBJECT-TYPE SYNTAX Hdsl2HistoryCount MAX-ACCESS read-only STATUS current DESCRIPTION "Count of CRC anomalies during the 1-day interval as measured by hdsl2HistoryMoniSecs." ::= { hdsl2HistoryEntry 5 } hdsl2HistoryLOSWS OBJECT-TYPE SYNTAX Hdsl2HistoryCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of Loss of Sync Word (LOSW) Seconds during the 1-day interval as measured by hdsl2HistoryMoniSecs." ::= { hdsl2HistoryEntry 6 } hdsl2HistoryUAS OBJECT-TYPE SYNTAX Hdsl2HistoryCount MAX-ACCESS read-only STATUS current DESCRIPTION "Count of Unavailable Seconds (UAS) during the 1-day interval as measured by hdsl2HistoryMoniSecs." ::= { hdsl2HistoryEntry 7 } -- DS1 group -- hdsl2DS1ConfTable OBJECT-TYPE SYNTAX SEQUENCE OF Hdsl2DS1ConfEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table provides one row for each HDSL2 DS1 interface." ::= { hdsl2MibObjects 8 } hdsl2DS1ConfEntry OBJECT-TYPE Expires November 8, 2000 Page [28] INTERNET-DRAFT HDSL2-LINE MIB May 2000 SYNTAX Hdsl2DS1ConfEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in hdsl2DS1ConfTable." INDEX { ifIndex, hdsl2DS1htuIndex } ::= { hdsl2DS1ConfTable 1 } Hdsl2DS1ConfEntry ::= SEQUENCE { hdsl2DS1htuIndex INTEGER, hdsl2DS1ConfProfile SnmpAdminString, hdsl2DS1AlarmConfProfile SnmpAdminString } hdsl2DS1htuIndex OBJECT-TYPE SYNTAX INTEGER { htuC(1), htuR(2) } MAX-ACCESS read-only STATUS current DESCRIPTION "Selects the DS1 interface." ::= { hdsl2DS1ConfEntry 1 } hdsl2DS1ConfProfile OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-write STATUS current DESCRIPTION "The value of this object identifies the row in the HDSL2 DS1 Configuration Profile Table, hdsl2DS1ProfileTable, which applies to this HDSL2 HTU. In the case which the configuration profile has not been set, the value will be set to 'DEFVAL'." ::= { hdsl2DS1ConfEntry 2 } hdsl2DS1AlarmConfProfile OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-write STATUS current DESCRIPTION "The value of this object identifies the row in the HDSL2 DS1 Alarm Configuration Profile Table, hdsl2DS1AlarmConfProfileTable, which applies to this HDSL2 HTU. In the case which the configuration profile has not been set, the value will be set to 'DEFVAL'." ::= { hdsl2DS1ConfEntry 3 } Expires November 8, 2000 Page [29] INTERNET-DRAFT HDSL2-LINE MIB May 2000 hdsl2DS1PerfDataTable OBJECT-TYPE SYNTAX SEQUENCE OF Hdsl2DS1PerfDataEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table provides one row for each HDSL2 DS1 interface." ::= { hdsl2MibObjects 9 } hdsl2DS1PerfDataEntry OBJECT-TYPE SYNTAX Hdsl2DS1PerfDataEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in hdsl2DS1PerfDataTable." INDEX { ifIndex, hdsl2DS1htuIndex } ::= { hdsl2DS1PerfDataTable 1 } Hdsl2DS1PerfDataEntry ::= SEQUENCE { hdsl2DS1PerfCVL Counter32, hdsl2DS1PerfES Counter32, hdsl2DS1PerfSES Counter32, hdsl2DS1PerfLOSS Counter32, hdsl2DS1PerfCurr15MinTimeElapsed Hdsl2PerfTimeElapsed, hdsl2DS1PerfCurr15MinCVL PerfCurrentCount, hdsl2DS1PerfCurr15MinES PerfCurrentCount, hdsl2DS1PerfCurr15MinSES PerfCurrentCount, hdsl2DS1PerfCurr15MinLOSS PerfCurrentCount, hdsl2DS1PerfCurr1DayTimeElapsed Hdsl2PerfTimeElapsed, hdsl2DS1PerfCurr1DayCVL Hdsl2PerfCurrDayCount, hdsl2DS1PerfCurr1DayES Hdsl2PerfCurrDayCount, hdsl2DS1PerfCurr1DaySES Hdsl2PerfCurrDayCount, hdsl2DS1PerfCurr1DayLOSS Hdsl2PerfCurrDayCount } hdsl2DS1PerfCVL OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Count of Code Violations - Line (CVL) as defined in ANSI T1.231 on this interface since the HTU was last restarted." ::= { hdsl2DS1PerfDataEntry 1 } hdsl2DS1PerfES OBJECT-TYPE SYNTAX Counter32 UNITS "seconds" MAX-ACCESS read-only Expires November 8, 2000 Page [30] INTERNET-DRAFT HDSL2-LINE MIB May 2000 STATUS current DESCRIPTION "Count of Errored Seconds (ES) as defined in ANSI T1.231 on this interface since the HTU was last restarted." ::= { hdsl2DS1PerfDataEntry 2 } hdsl2DS1PerfSES OBJECT-TYPE SYNTAX Counter32 UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of Severely Errored Seconds (SES) as defined in ANSI T1.231 on this interface since the HTU was last restarted." ::= { hdsl2DS1PerfDataEntry 3 } hdsl2DS1PerfLOSS OBJECT-TYPE SYNTAX Counter32 UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of Loss of Signal (LOS) Seconds as defined in ANSI T1.231 on this interface since the HTU was last restarted." ::= { hdsl2DS1PerfDataEntry 4 } hdsl2DS1PerfCurr15MinTimeElapsed OBJECT-TYPE SYNTAX Hdsl2PerfTimeElapsed UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Total elapsed seconds in this interval." ::= { hdsl2DS1PerfDataEntry 5 } hdsl2DS1PerfCurr15MinCVL OBJECT-TYPE SYNTAX PerfCurrentCount MAX-ACCESS read-only STATUS current DESCRIPTION "Count of Code Violations - Line (CVL) as defined in ANSI T1.231 on this interface in the current 15-minute interval." ::= { hdsl2DS1PerfDataEntry 6 } hdsl2DS1PerfCurr15MinES OBJECT-TYPE SYNTAX PerfCurrentCount UNITS "seconds" MAX-ACCESS read-only STATUS current Expires November 8, 2000 Page [31] INTERNET-DRAFT HDSL2-LINE MIB May 2000 DESCRIPTION "Count of Errored Seconds (ES) as defined in ANSI T1.231 on this interface in the current 15-minute interval." ::= { hdsl2DS1PerfDataEntry 7 } hdsl2DS1PerfCurr15MinSES OBJECT-TYPE SYNTAX PerfCurrentCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of Severely Errored Seconds (SES) as defined in ANSI T1.231 on this interface in the current 15-minute interval." ::= { hdsl2DS1PerfDataEntry 8 } hdsl2DS1PerfCurr15MinLOSS OBJECT-TYPE SYNTAX PerfCurrentCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of Loss of Signal (LOS) Seconds as defined in ANSI T1.231 on this interface in the current 15-minute interval." ::= { hdsl2DS1PerfDataEntry 9 } hdsl2DS1PerfCurr1DayTimeElapsed OBJECT-TYPE SYNTAX Hdsl2PerfTimeElapsed UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Number of seconds that have elapsed since the beginning of the current 1-day interval." ::= { hdsl2DS1PerfDataEntry 10 } hdsl2DS1PerfCurr1DayCVL OBJECT-TYPE SYNTAX Hdsl2PerfCurrDayCount MAX-ACCESS read-only STATUS current DESCRIPTION "Count of Code Violations - Line (CVL) as defined in ANSI T1.231 on this interface during the current day as measured by hdsl2DS1PerfCurr1DayTimeElapsed." ::= { hdsl2DS1PerfDataEntry 11 } hdsl2DS1PerfCurr1DayES OBJECT-TYPE SYNTAX Hdsl2PerfCurrDayCount UNITS "seconds" MAX-ACCESS read-only STATUS current Expires November 8, 2000 Page [32] INTERNET-DRAFT HDSL2-LINE MIB May 2000 DESCRIPTION "Count of Errored Seconds (ES) as defined in ANSI T1.231 on this interface during the current day as measured by hdsl2DS1PerfCurr1DayTimeElapsed." ::= { hdsl2DS1PerfDataEntry 12 } hdsl2DS1PerfCurr1DaySES OBJECT-TYPE SYNTAX Hdsl2PerfCurrDayCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of Severely Errored Seconds (SES) as defined in ANSI T1.231 on this interface during the current day as measured by hdsl2DS1PerfCurr1DayTimeElapsed." ::= { hdsl2DS1PerfDataEntry 13 } hdsl2DS1PerfCurr1DayLOSS OBJECT-TYPE SYNTAX Hdsl2PerfCurrDayCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of Loss of Signal (LOS) Seconds as defined in ANSI T1.231 on this interface during the current day as measured by hdsl2DS1PerfCurr1DayTimeElapsed." ::= { hdsl2DS1PerfDataEntry 14 } -- DS1 interval group -- hdsl2DS1IntervalTable OBJECT-TYPE SYNTAX SEQUENCE OF Hdsl2DS1IntervalEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table provides one row for each HTU DS1 interface performance data collection interval." ::= { hdsl2MibObjects 10 } hdsl2DS1IntervalEntry OBJECT-TYPE SYNTAX Hdsl2DS1IntervalEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the hdsl2DS1IntervalTable." INDEX { ifIndex, hdsl2DS1htuIndex, hdsl2DS1IntervalNumber } ::= { hdsl2DS1IntervalTable 1 } Hdsl2DS1IntervalEntry ::= SEQUENCE { hdsl2DS1IntervalNumber INTEGER, Expires November 8, 2000 Page [33] INTERNET-DRAFT HDSL2-LINE MIB May 2000 hdsl2DS1IntervalCVL PerfIntervalCount, hdsl2DS1IntervalES PerfIntervalCount, hdsl2DS1IntervalSES PerfIntervalCount, hdsl2DS1IntervalLOSS PerfIntervalCount } hdsl2DS1IntervalNumber OBJECT-TYPE SYNTAX INTEGER(1..96) MAX-ACCESS not-accessible STATUS current DESCRIPTION "Performance Data Interval number. 1 is the the most recent previous interval; interval 96 is 24 hours ago. Intervals 2..96 are optional." ::= { hdsl2DS1IntervalEntry 1 } hdsl2DS1IntervalCVL OBJECT-TYPE SYNTAX PerfIntervalCount MAX-ACCESS read-only STATUS current DESCRIPTION "Count of Code Violations - Line (CVL) as defined in ANSI T1.231 on this interface during the interval." ::= { hdsl2DS1IntervalEntry 2 } hdsl2DS1IntervalES OBJECT-TYPE SYNTAX PerfIntervalCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of Errored Seconds (ES) as defined in ANSI T1.231 on this interface during the interval." ::= { hdsl2DS1IntervalEntry 3 } hdsl2DS1IntervalSES OBJECT-TYPE SYNTAX PerfIntervalCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of Severely Errored Seconds (SES) as defined in ANSI T1.231 on this interface during the interval." ::= { hdsl2DS1IntervalEntry 4 } hdsl2DS1IntervalLOSS OBJECT-TYPE SYNTAX PerfIntervalCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of Loss of Signal (LOS) Seconds as defined in ANSI T1.231 on this interface during the interval." Expires November 8, 2000 Page [34] INTERNET-DRAFT HDSL2-LINE MIB May 2000 ::= { hdsl2DS1IntervalEntry 5 } -- DS1 history group -- hdsl2DS1HistoryTable OBJECT-TYPE SYNTAX SEQUENCE OF Hdsl2DS1HistoryEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table provides one row for each HTU DS1 interface performance data collection interval." ::= { hdsl2MibObjects 11 } hdsl2DS1HistoryEntry OBJECT-TYPE SYNTAX Hdsl2DS1HistoryEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the hdsl2DS1HistoryTable." INDEX { ifIndex, hdsl2DS1htuIndex, hdsl2DS1HistoryInterval } ::= { hdsl2DS1HistoryTable 1 } Hdsl2DS1HistoryEntry ::= SEQUENCE { hdsl2DS1HistoryInterval INTEGER, hdsl2DS1HistoryMoniSecs Hdsl2PerfTimeElapsed, hdsl2DS1HistoryCVL Hdsl2HistoryCount, hdsl2DS1HistoryES Hdsl2HistoryCount, hdsl2DS1HistorySES Hdsl2HistoryCount, hdsl2DS1HistoryLOSS Hdsl2HistoryCount } hdsl2DS1HistoryInterval OBJECT-TYPE SYNTAX INTEGER(1..30) MAX-ACCESS not-accessible STATUS current DESCRIPTION "DS1 History Data Interval number. Interval 1 is the the most recent previous day; interval 30 is 30 days ago. Intervals 2..30 are optional." ::= { hdsl2DS1HistoryEntry 1 } hdsl2DS1HistoryMoniSecs OBJECT-TYPE SYNTAX Hdsl2PerfTimeElapsed UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "The amount of time in the previous 1-day interval over which the performance monitoring information is actually counted. This value will be the same Expires November 8, 2000 Page [35] INTERNET-DRAFT HDSL2-LINE MIB May 2000 as the interval duration except in a situation where performance monitoring data could not be collected for any reason." ::= { hdsl2DS1HistoryEntry 2 } hdsl2DS1HistoryCVL OBJECT-TYPE SYNTAX Hdsl2HistoryCount MAX-ACCESS read-only STATUS current DESCRIPTION "Count of Code Violations - Line (CVL) as defined in ANSI T1.231 on this interface during the previous day as measured by hdsl2DS1HistoryMoniSecs." ::= { hdsl2DS1HistoryEntry 3 } hdsl2DS1HistoryES OBJECT-TYPE SYNTAX Hdsl2HistoryCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of Errored Seconds (ES) as defined in ANSI T1.231 on this interface during the previous day as measured by hdsl2DS1HistoryMoniSecs." ::= { hdsl2DS1HistoryEntry 4 } hdsl2DS1HistorySES OBJECT-TYPE SYNTAX Hdsl2HistoryCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of Severely Errored Seconds (SES) as defined in ANSI T1.231 on this interface during the previous day as measured by hdsl2DS1HistoryMoniSecs." ::= { hdsl2DS1HistoryEntry 5 } hdsl2DS1HistoryLOSS OBJECT-TYPE SYNTAX Hdsl2HistoryCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of Loss of Signal (LOS) Seconds as defined in ANSI T1.231 on this interface during the previous day as measured by hdsl2DS1HistoryMoniSecs." ::= { hdsl2DS1HistoryEntry 6 } -- Maintenance Group -- hdsl2MaintenanceTable OBJECT-TYPE SYNTAX SEQUENCE OF Hdsl2MaintenanceEntry Expires November 8, 2000 Page [36] INTERNET-DRAFT HDSL2-LINE MIB May 2000 MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table provides one row for each HDSL2 modem. This table is used for controlling test loops on the HDSL2 line segments." ::= { hdsl2MibObjects 12 } hdsl2MaintenanceEntry OBJECT-TYPE SYNTAX Hdsl2MaintenanceEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the hdsl2MaintenanceTable." INDEX { ifIndex, hdsl2InvIndex } ::= { hdsl2MaintenanceTable 1 } Hdsl2MaintenanceEntry ::= SEQUENCE { hdsl2MaintLoopbackCommand INTEGER, hdsl2MaintLoopbackStatus Integer32, hdsl2MaintLoopbackTimeout Integer32, hdsl2MaintLocalSpanPower INTEGER, hdsl2MaintCustomerTipRingReversal INTEGER, hdsl2MaintNetworkTipRingReversal INTEGER, hdsl2MaintNetworkPowerBackOff INTEGER, hdsl2MaintNetworkSoftRestart INTEGER, hdsl2MaintCustomerPowerBackOff INTEGER, hdsl2MaintCustomerSoftRestart INTEGER } hdsl2MaintLoopbackCommand OBJECT-TYPE SYNTAX INTEGER { noCommand(0), clearMaintenanceStates(1), initiateSpecialLoopback(2), terminateSpecialLoopback(3), initiateLoopback(4), terminateLoopback(5) } MAX-ACCESS read-write STATUS current DESCRIPTION "Setting this object to a non-zero value causes the specified operation to be attempted on the HDSL2 interface." ::= { hdsl2MaintenanceEntry 1 } hdsl2MaintLoopbackStatus OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only Expires November 8, 2000 Page [37] INTERNET-DRAFT HDSL2-LINE MIB May 2000 STATUS current DESCRIPTION "Bitmapped loopback status 1 Proprietary maintenance state active 2 Special loopback active 4 Loopback active" ::= { hdsl2MaintenanceEntry 2 } hdsl2MaintLoopbackTimeout OBJECT-TYPE SYNTAX Integer32 UNITS "minutes" MAX-ACCESS read-write STATUS current DESCRIPTION "Specifies the loopback timeout. If a loopback is not cleared before the expiration of the timeout, then the element shall revert to normal operation." ::= { hdsl2MaintenanceEntry 3 } hdsl2MaintLocalSpanPower OBJECT-TYPE SYNTAX INTEGER { spanPowered(0), localPowered(1) } MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates whether the unit is span or locally powered." ::= { hdsl2MaintenanceEntry 4 } hdsl2MaintCustomerTipRingReversal OBJECT-TYPE SYNTAX INTEGER { normal(0), reversed(1) } MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates the state of tip/ring." ::= { hdsl2MaintenanceEntry 5 } hdsl2MaintNetworkTipRingReversal OBJECT-TYPE SYNTAX INTEGER { normal(0), reversed(1) } MAX-ACCESS read-only STATUS current Expires November 8, 2000 Page [38] INTERNET-DRAFT HDSL2-LINE MIB May 2000 DESCRIPTION "Indicates the state of tip/ring." ::= { hdsl2MaintenanceEntry 6 } hdsl2MaintNetworkPowerBackOff OBJECT-TYPE SYNTAX INTEGER { default(0), enhanced(1) } MAX-ACCESS read-write STATUS current DESCRIPTION "Specifies if a receiver is set to the default or enhanced modes of power backoff." ::= { hdsl2MaintenanceEntry 7 } hdsl2MaintNetworkSoftRestart OBJECT-TYPE SYNTAX INTEGER { noRestart(0), restart(1) } MAX-ACCESS read-write STATUS current DESCRIPTION "Specifies if the receiver is to be soft-restarted (after 5 seconds)." ::= { hdsl2MaintenanceEntry 8 } hdsl2MaintCustomerPowerBackOff OBJECT-TYPE SYNTAX INTEGER { default(0), enhanced(1) } MAX-ACCESS read-write STATUS current DESCRIPTION "Specifies if a receiver is set to the default or enhanced modes of power backoff." ::= { hdsl2MaintenanceEntry 9 } hdsl2MaintCustomerSoftRestart OBJECT-TYPE SYNTAX INTEGER { noRestart(0), restart(1) } MAX-ACCESS read-write STATUS current DESCRIPTION "Specifies if the receiver is to be soft-restarted Expires November 8, 2000 Page [39] INTERNET-DRAFT HDSL2-LINE MIB May 2000 (after 5 seconds)." ::= { hdsl2MaintenanceEntry 10 } -- DS1 profile group -- hdsl2DS1ProfileTable OBJECT-TYPE SYNTAX SEQUENCE OF Hdsl2DS1ProfileEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains information on the HDSL2 DS1 configuration. One entry in this table reflects a profile defined by a manager which can be used to configure a HDSL2 DS1 interface." ::= { hdsl2MibObjects 13 } hdsl2DS1ProfileEntry OBJECT-TYPE SYNTAX Hdsl2DS1ProfileEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Each entry consists of a list of parameters that represents the DS1 configuration of a HDSL2 HTU. A profile is created in one step with all necessary parameter values and hdsl2DS1ProfileRowStatus set to createAndGo. This RowStatus object is also used to delete destroy profiles." INDEX { hdsl2DS1ProfileName } ::= { hdsl2DS1ProfileTable 1 } Hdsl2DS1ProfileEntry ::= SEQUENCE { hdsl2DS1ProfileName SnmpAdminString, hdsl2DS1FrameFormat INTEGER, hdsl2DS1LineCode INTEGER, hdsl2DS1PulseEqualization INTEGER, hdsl2DS1NetworkLoopback INTEGER, hdsl2DS1DownstreamLOSD INTEGER, hdsl2DS1UpstreamLOSD INTEGER, hdsl2DS1ProfileRowStatus RowStatus } hdsl2DS1ProfileName OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-create STATUS current DESCRIPTION "The index into the HDSL2 DS1 Profile Table." ::= { hdsl2DS1ProfileEntry 1 } hdsl2DS1FrameFormat OBJECT-TYPE Expires November 8, 2000 Page [40] INTERNET-DRAFT HDSL2-LINE MIB May 2000 SYNTAX INTEGER { auto(0), unframed(1), sf(2), esf(3), terminalFraming(4), slc96(5) } MAX-ACCESS read-create STATUS current DESCRIPTION "Specifies the DS1 Frame Format." ::= { hdsl2DS1ProfileEntry 2 } hdsl2DS1LineCode OBJECT-TYPE SYNTAX INTEGER { auto(0), ami(1), b8zs(2), reserved(3) } MAX-ACCESS read-create STATUS current DESCRIPTION "Specifies the DS1 Line Code." ::= { hdsl2DS1ProfileEntry 3 } hdsl2DS1PulseEqualization OBJECT-TYPE SYNTAX INTEGER { external(0), switched(1), automatic(2), feet000to133(3), feet133to266(4), feet266to399(5), feet399to533(6), feet533to655(7), db0dot0(8), db7dot5(9), db15dot0(10), db22dot5(11) } MAX-ACCESS read-create STATUS current DESCRIPTION "Specifies the DS1 Pulse Equalization and Line Buildout." ::= { hdsl2DS1ProfileEntry 4 } hdsl2DS1NetworkLoopback OBJECT-TYPE Expires November 8, 2000 Page [41] INTERNET-DRAFT HDSL2-LINE MIB May 2000 SYNTAX INTEGER { ais(0), los(1) } MAX-ACCESS read-create STATUS current DESCRIPTION "On network loopback, the HTU sends AIS or LOS towards the DS1 interface." ::= { hdsl2DS1ProfileEntry 5 } hdsl2DS1DownstreamLOSD OBJECT-TYPE SYNTAX INTEGER { ais(0), los(1) } MAX-ACCESS read-create STATUS current DESCRIPTION "On LOS defect indication on the HDSL2 line, the HTU sends AIS or LOS towards the DS1 interface." ::= { hdsl2DS1ProfileEntry 6 } hdsl2DS1UpstreamLOSD OBJECT-TYPE SYNTAX INTEGER { ais(0), loopback(1) } MAX-ACCESS read-create STATUS current DESCRIPTION "On LOS at the DS1 input, the HTU sends AIS or Loopback on the HDSL2 line." ::= { hdsl2DS1ProfileEntry 7 } hdsl2DS1ProfileRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This object is used to create a new row or modify or delete an existing row in this table." ::= { hdsl2DS1ProfileEntry 8 } -- SHDSL profile group -- hdsl2ShdslProfileTable OBJECT-TYPE SYNTAX SEQUENCE OF Hdsl2ShdslProfileEntry MAX-ACCESS not-accessible Expires November 8, 2000 Page [42] INTERNET-DRAFT HDSL2-LINE MIB May 2000 STATUS current DESCRIPTION "This table contains information on a SHDSL configuration. One entry in this table reflects a profile defined by a manager which can be used to configure a SHDSL interface." ::= { hdsl2MibObjects 14 } hdsl2ShdslProfileEntry OBJECT-TYPE SYNTAX Hdsl2ShdslProfileEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Each entry consists of a list of parameters that represents the configuration of a SHDSL line. A profile is created in one step with all necessary parameter values and hdsl2ShdslProfileRowStatus set to createAndGo. This RowStatus object is also used to delete destroy profiles." INDEX { hdsl2ShdslProfileName } ::= { hdsl2ShdslProfileTable 1 } Hdsl2ShdslProfileEntry ::= SEQUENCE { hdsl2ShdslProfileName SnmpAdminString, hdsl2ShdslLineSpeed Integer32, hdsl2ShdslRemoteEnabled INTEGER, hdsl2ShdslProfileRowStatus RowStatus } hdsl2ShdslProfileName OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-create STATUS current DESCRIPTION "The index into the SHDSL Profile Table." ::= { hdsl2ShdslProfileEntry 1 } hdsl2ShdslLineSpeed OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-create STATUS current DESCRIPTION "The speed of the SHDSL line." ::= { hdsl2ShdslProfileEntry 2 } hdsl2ShdslRemoteEnabled OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } Expires November 8, 2000 Page [43] INTERNET-DRAFT HDSL2-LINE MIB May 2000 MAX-ACCESS read-create STATUS current DESCRIPTION "Defines if STU-R commands are enabled." ::= { hdsl2ShdslProfileEntry 3 } hdsl2ShdslProfileRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This object is used to create a new row or modify or delete an existing row in this table." ::= { hdsl2ShdslProfileEntry 4 } -- Alarm Profile group -- hdsl2EndpointAlarmConfProfileTable OBJECT-TYPE SYNTAX SEQUENCE OF Hdsl2EndpointAlarmConfProfileEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains information on the HDSL2 alarm configuration. One entry in this table reflects a profile defined by a manager which can be used to configure a HDSL2 endpoint." ::= { hdsl2MibObjects 15 } hdsl2EndpointAlarmConfProfileEntry OBJECT-TYPE SYNTAX Hdsl2EndpointAlarmConfProfileEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Each entry consists of a list of parameters that represents the configuration of a HDSL2 endpoint. A profile is created in one step with all necessary parameter values and hdsl2EndpointAlarmConfProfileRowStatus set to createAndGo. This RowStatus object is also used to delete destroy profiles." INDEX { hdsl2EndpointAlarmConfProfileName } ::= { hdsl2EndpointAlarmConfProfileTable 1 } Hdsl2EndpointAlarmConfProfileEntry ::= SEQUENCE { hdsl2EndpointAlarmConfProfileName SnmpAdminString, hdsl2EndpointThreshLoopAttenuation Integer32, hdsl2EndpointThreshSNRMargin Integer32, hdsl2EndpointThreshES INTEGER, hdsl2EndpointThreshSES INTEGER, hdsl2EndpointThreshCRCanomaly Integer32, hdsl2EndpointThreshLOSWS INTEGER, Expires November 8, 2000 Page [44] INTERNET-DRAFT HDSL2-LINE MIB May 2000 hdsl2EndpointThreshUAS INTEGER, hdsl2EndpointAlarmConfProfileRowStatus RowStatus } hdsl2EndpointAlarmConfProfileName OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-create STATUS current DESCRIPTION "The index into the HDSL2 Endpoint Alarm Profile Table." ::= { hdsl2EndpointAlarmConfProfileEntry 1 } hdsl2EndpointThreshLoopAttenuation OBJECT-TYPE SYNTAX Integer32 UNITS "dB" MAX-ACCESS read-create STATUS current DESCRIPTION "Specifies the Loop Attentuation alarm threshold. When the current value crosses this threshold, a hdsl2LoopAttenCrossingTrap will be generated." ::= { hdsl2EndpointAlarmConfProfileEntry 2 } hdsl2EndpointThreshSNRMargin OBJECT-TYPE SYNTAX Integer32 UNITS "dB" MAX-ACCESS read-create STATUS current DESCRIPTION "Specifies the SNR Margin alarm threshold. When the current value crosses this threshold, a hdsl2SNRMarginCrossingTrap will be generated." ::= { hdsl2EndpointAlarmConfProfileEntry 3 } hdsl2EndpointThreshES OBJECT-TYPE SYNTAX INTEGER(0..900) UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "The number of Errored Seconds (ES) encountered by a HDSL2 endpoint within any given 15 minutes performance data collection period, which causes the SNMP agent to send a hdsl2PerfESThreshTrap. One trap will be sent per interval per endpoint. A value of '0' will disable the trap." ::= { hdsl2EndpointAlarmConfProfileEntry 5 } hdsl2EndpointThreshSES OBJECT-TYPE SYNTAX INTEGER(0..900) UNITS "seconds" MAX-ACCESS read-create STATUS current Expires November 8, 2000 Page [45] INTERNET-DRAFT HDSL2-LINE MIB May 2000 DESCRIPTION "The number of Severely Errored Seconds (SES) encountered by a HDSL2 endpoint within any given 15 minutes performance data collection period, which causes the SNMP agent to send a hdsl2PerfESThreshTrap. One trap will be sent per interval per endpoint. A value of '0' will disable the trap." ::= { hdsl2EndpointAlarmConfProfileEntry 6 } hdsl2EndpointThreshCRCanomaly OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-create STATUS current DESCRIPTION "The number of CRC anomalies encountered by a HDSL2 endpoint within any given 15 minutes performance data collection period, which causes the SNMP agent to send a hdsl2PerfCRCanomalyThreshTrap. One trap will be sent per interval per endpoint. A value of '0' will disable the trap." ::= { hdsl2EndpointAlarmConfProfileEntry 4 } hdsl2EndpointThreshLOSWS OBJECT-TYPE SYNTAX INTEGER(0..900) UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "The number of Loss of Sync Word (LOSW) Seconds encountered by a HDSL2 endpoint within any given 15 minutes performance data collection period, which causes the SNMP agent to send a hdsl2PerfLOSWThreshTrap. One trap will be sent per interval per endpoint. A value of '0' will disable the trap." ::= { hdsl2EndpointAlarmConfProfileEntry 7 } hdsl2EndpointThreshUAS OBJECT-TYPE SYNTAX INTEGER(0..900) UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "The number of Unavailable Seconds (UAS) encountered by a HDSL2 endpoint within any given 15 minutes performance data collection period, which causes the SNMP agent to send a hdsl2PerfUASThreshTrap. One trap will be sent per interval per endpoint. A value of '0' will disable the trap." ::= { hdsl2EndpointAlarmConfProfileEntry 8 } hdsl2EndpointAlarmConfProfileRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create Expires November 8, 2000 Page [46] INTERNET-DRAFT HDSL2-LINE MIB May 2000 STATUS current DESCRIPTION "This object is used to create a new row or modify or delete an existing row in this table." ::= { hdsl2EndpointAlarmConfProfileEntry 9 } -- DS1 Alarm Profile -- hdsl2DS1AlarmConfProfileTable OBJECT-TYPE SYNTAX SEQUENCE OF Hdsl2DS1AlarmConfProfileEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains information on the HDSL2 alarm configuration. One entry in this table reflects a profile defined by a manager which can be used to configure a HDSL2 HTU." ::= { hdsl2MibObjects 16 } hdsl2DS1AlarmConfProfileEntry OBJECT-TYPE SYNTAX Hdsl2DS1AlarmConfProfileEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Each entry consists of a list of parameters that represents the alarm configuration of a HDSL2 HTU DS1 interface. A profile is created in one step with all necessary parameter values and hdsl2DS1AlarmConfProfileRowStatus set to createAndGo. This RowStatus object is also used to delete destroy profiles." INDEX { hdsl2DS1AlarmConfProfileName } ::= { hdsl2DS1AlarmConfProfileTable 1 } Hdsl2DS1AlarmConfProfileEntry ::= SEQUENCE { hdsl2DS1AlarmConfProfileName SnmpAdminString, hdsl2DS1ThreshCVL Integer32, hdsl2DS1ThreshES INTEGER, hdsl2DS1ThreshSES INTEGER, hdsl2DS1ThreshLOSS INTEGER, hdsl2DS1AlarmConfProfileRowStatus RowStatus } hdsl2DS1AlarmConfProfileName OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-create STATUS current DESCRIPTION "The index into the HDSL2 DS1 Alarm Profile Table." ::= { hdsl2DS1AlarmConfProfileEntry 1 } Expires November 8, 2000 Page [47] INTERNET-DRAFT HDSL2-LINE MIB May 2000 hdsl2DS1ThreshCVL OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-create STATUS current DESCRIPTION "The number of Code Violations - Line (CVL) encountered by a HDSL2 HTU DS1 interface within any given 15 minutes performance data collection period, which causes the SNMP agent to send a hdsl2DS1CVLThreshTrap. One trap will be sent per interval per interface. A value of '0' will disable the trap." ::= { hdsl2DS1AlarmConfProfileEntry 2} hdsl2DS1ThreshES OBJECT-TYPE SYNTAX INTEGER(0..900) UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "The count of Errored Seconds (ES) encountered by a HDSL2 HTU DS1 interface within any given 15 minutes performance data collection period, which causes the SNMP agent to send a hdsl2DS1ESThreshTrap. One trap will be sent per interval per interface. A value of '0' will disable the trap." ::= { hdsl2DS1AlarmConfProfileEntry 3 } hdsl2DS1ThreshSES OBJECT-TYPE SYNTAX INTEGER(0..900) UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "The count of Severely Errored Seconds (SES) encountered by a HDSL2 HTU DS1 interface within any given 15 minutes performance data collection period, which causes the SNMP agent to send a hdsl2DS1SESThreshTrap. One trap will be sent per interval per interface. A value of '0' will disable the trap." ::= { hdsl2DS1AlarmConfProfileEntry 4 } hdsl2DS1ThreshLOSS OBJECT-TYPE SYNTAX INTEGER(0..900) UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "The count of Loss of Signal Seconds (LOSS) encountered by a HDSL2 HTU DS1 interface within any given 15 minutes performance data collection period, which causes the SNMP agent to send a hdsl2DS1LOSSThreshTrap. One trap will be sent per interval per interface. A value of '0' will disable the trap." ::= { hdsl2DS1AlarmConfProfileEntry 5 } Expires November 8, 2000 Page [48] INTERNET-DRAFT HDSL2-LINE MIB May 2000 hdsl2DS1AlarmConfProfileRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This object is used to create a new row or modify or delete an existing row in this table." ::= { hdsl2DS1AlarmConfProfileEntry 6 } -- trap definitions -- hdsl2Traps OBJECT IDENTIFIER ::= { hdsl2LineMib 2 } hdsl2TrapsPrefix OBJECT IDENTIFIER ::= { hdsl2Traps 0 } hdsl2LoopAttenCrossingTrap NOTIFICATION-TYPE OBJECTS { ifIndex, hdsl2EndpointIndex, hdsl2EndpointCurrAtn, hdsl2EndpointThreshLoopAttenuation } STATUS current DESCRIPTION "Loop Attenuation threshold crossed." ::= { hdsl2TrapsPrefix 1 } hdsl2SNRMarginCrossingTrap NOTIFICATION-TYPE OBJECTS { ifIndex, hdsl2EndpointIndex, hdsl2EndpointCurrSnrMgn, hdsl2EndpointThreshSNRMargin } STATUS current DESCRIPTION "SNR Margin threshold crossed." ::= { hdsl2TrapsPrefix 2 } hdsl2PerfESThreshTrap NOTIFICATION-TYPE OBJECTS { ifIndex, hdsl2EndpointIndex, hdsl2EndpointCurr15MinES, hdsl2EndpointThreshES } STATUS current DESCRIPTION "Errored Seconds (ES) threshold reached." ::= { hdsl2TrapsPrefix 3 } Expires November 8, 2000 Page [49] INTERNET-DRAFT HDSL2-LINE MIB May 2000 hdsl2PerfSESThreshTrap NOTIFICATION-TYPE OBJECTS { ifIndex, hdsl2EndpointIndex, hdsl2EndpointCurr15MinSES, hdsl2EndpointThreshSES } STATUS current DESCRIPTION "Severely Errored Seconds (SES) threshold reached." ::= { hdsl2TrapsPrefix 4 } hdsl2PerfCRCanomalyThreshTrap NOTIFICATION-TYPE OBJECTS { ifIndex, hdsl2EndpointIndex, hdsl2EndpointCurr15MinCRCanomaly, hdsl2EndpointThreshCRCanomaly } STATUS current DESCRIPTION "CRC Anomaly threshold reached." ::= { hdsl2TrapsPrefix 5 } hdsl2PerfLOSWThreshTrap NOTIFICATION-TYPE OBJECTS { ifIndex, hdsl2EndpointIndex, hdsl2EndpointCurr15MinLOSWS, hdsl2EndpointThreshLOSWS } STATUS current DESCRIPTION "Loss of Sync Word (LOSW) Seconds threshold reached." ::= { hdsl2TrapsPrefix 6 } hdsl2PerfUASThreshTrap NOTIFICATION-TYPE OBJECTS { ifIndex, hdsl2EndpointIndex, hdsl2EndpointCurr15MinUAS, hdsl2EndpointThreshUAS } STATUS current DESCRIPTION "Unavailable Seconds (UAS) threshold reached." ::= { hdsl2TrapsPrefix 7 } hdsl2DS1CVLThreshTrap NOTIFICATION-TYPE Expires November 8, 2000 Page [50] INTERNET-DRAFT HDSL2-LINE MIB May 2000 OBJECTS { ifIndex, hdsl2DS1htuIndex, hdsl2DS1PerfCurr15MinCVL, hdsl2DS1ThreshCVL } STATUS current DESCRIPTION "DS1 Code Violation - Line (CVL) threshold reached." ::= { hdsl2TrapsPrefix 8 } hdsl2DS1ESThreshTrap NOTIFICATION-TYPE OBJECTS { ifIndex, hdsl2DS1htuIndex, hdsl2DS1PerfCurr15MinES, hdsl2DS1ThreshES } STATUS current DESCRIPTION "DS1 Errored Seconds (ES) threshold reached." ::= { hdsl2TrapsPrefix 9 } hdsl2DS1SESThreshTrap NOTIFICATION-TYPE OBJECTS { ifIndex, hdsl2DS1htuIndex, hdsl2DS1PerfCurr15MinSES, hdsl2DS1ThreshSES } STATUS current DESCRIPTION "DS1 Severely Errored Seconds (SES) threshold reached." ::= { hdsl2TrapsPrefix 10 } hdsl2DS1LOSSThreshTrap NOTIFICATION-TYPE OBJECTS { ifIndex, hdsl2DS1htuIndex, hdsl2DS1PerfCurr15MinLOSS, hdsl2DS1ThreshLOSS } STATUS current DESCRIPTION "DS1 Loss of Signal (LOS) Seconds threshold reached." ::= { hdsl2TrapsPrefix 11 } -- conformance information Expires November 8, 2000 Page [51] INTERNET-DRAFT HDSL2-LINE MIB May 2000 hdsl2Conformance OBJECT IDENTIFIER ::= { hdsl2LineMib 3 } hdsl2Groups OBJECT IDENTIFIER ::= { hdsl2Conformance 1 } hdsl2Compliances OBJECT IDENTIFIER ::= { hdsl2Conformance 2 } -- HDSL2 agent compliance statements hdsl2LineMibCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for SNMP entities which manage HDSL2 interfaces." MODULE MANDATORY-GROUPS { hdsl2LineGroup, hdsl2InventoryGroup, hdsl2EndpointGroup, hdsl2IntervalGroup, hdsl2HistoryGroup, hdsl2MaintenanceGroup, hdsl2EndpointAlarmConfGroup, hdsl2NotificationGroup } GROUP hdsl2ShdslGroup DESCRIPTION "This group is optional. Implementations which support SHDSL must implement this group." GROUP hdsl2ShdslProfileGroup DESCRIPTION "This group is optional. Implementations which support SHDSL must implement this group." GROUP hdsl2DS1ConfigGroup DESCRIPTION "This group is optional. Implementations which support HTU DS1 interfaces must implement this group." GROUP hdsl2DS1PerfGroup DESCRIPTION "This group is optional. Implementations which support HTU DS1 interfaces must implement this group." GROUP hdsl2DS1IntervalGroup DESCRIPTION "This group is optional. Implementations which support HTU DS1 interfaces must implement this group." GROUP hdsl2DS1HistoryGroup DESCRIPTION "This group is optional. Implementations which support HTU DS1 interfaces must implement this group." Expires November 8, 2000 Page [52] INTERNET-DRAFT HDSL2-LINE MIB May 2000 GROUP hdsl2DS1ProfileGroup DESCRIPTION "This group is optional. Implementations which support HTU DS1 interfaces must implement this group." GROUP hdsl2DS1NotificationGroup DESCRIPTION "This group is optional. Implementations which support HTU DS1 interfaces must implement this group." ::= { hdsl2Compliances 1 } -- units of conformance hdsl2LineGroup OBJECT-GROUP OBJECTS { hdsl2LineNumRepeaters } STATUS current DESCRIPTION "A collection of objects providing pre-provisioning capability for a HDSL2 line." ::= { hdsl2Groups 1 } hdsl2InventoryGroup OBJECT-GROUP OBJECTS { hdsl2InvIndex, hdsl2InvVendorID, hdsl2InvVendorModelNumber, hdsl2InvVendorSerialNumber, hdsl2InvVendorEOCSoftwareVersion, hdsl2Invhdsl2StandardVersion, hdsl2InvVendorListNumber, hdsl2InvVendorIssueNumber, hdsl2InvVendorSoftwareVersion, hdsl2InvEquipmentCode, hdsl2InvVendorOther } STATUS current DESCRIPTION "A collection of objects providing inventory information about a HDSL2 line." ::= { hdsl2Groups 2 } hdsl2EndpointGroup OBJECT-GROUP OBJECTS { hdsl2EndpointIndex, hdsl2EndpointUnit, hdsl2EndpointModem, hdsl2EndpointAlarmConfProfile, Expires November 8, 2000 Page [53] INTERNET-DRAFT HDSL2-LINE MIB May 2000 hdsl2EndpointCurrAtn, hdsl2EndpointCurrSnrMgn, hdsl2EndpointCurrStatus, hdsl2EndpointES, hdsl2EndpointSES, hdsl2EndpointCRCanomaly, hdsl2EndpointLOSWS, hdsl2EndpointUAS, hdsl2EndpointCurr15MinTimeElapsed, hdsl2EndpointCurr15MinES, hdsl2EndpointCurr15MinSES, hdsl2EndpointCurr15MinCRCanomaly, hdsl2EndpointCurr15MinLOSWS, hdsl2EndpointCurr15MinUAS, hdsl2EndpointCurr1DayTimeElapsed, hdsl2EndpointCurr1DayES, hdsl2EndpointCurr1DaySES, hdsl2EndpointCurr1DayCRCanomaly, hdsl2EndpointCurr1DayLOSWS, hdsl2EndpointCurr1DayUAS } STATUS current DESCRIPTION "A collection of objects providing endpoint information about a HDSL2 line." ::= { hdsl2Groups 3 } hdsl2IntervalGroup OBJECT-GROUP OBJECTS { hdsl2IntervalES, hdsl2IntervalSES, hdsl2IntervalCRCanomaly, hdsl2IntervalLOSWseconds, hdsl2IntervalUAS } STATUS current DESCRIPTION "A collection of objects providing performance information about a HDSL2 line." ::= { hdsl2Groups 4 } hdsl2HistoryGroup OBJECT-GROUP OBJECTS { hdsl2HistoryMoniSecs, hdsl2HistoryES, hdsl2HistorySES, hdsl2HistoryCRCanomaly, hdsl2HistoryLOSWS, hdsl2HistoryUAS } STATUS current Expires November 8, 2000 Page [54] INTERNET-DRAFT HDSL2-LINE MIB May 2000 DESCRIPTION "A collection of objects providing historical performance information about a HDSL2 line." ::= { hdsl2Groups 5 } hdsl2MaintenanceGroup OBJECT-GROUP OBJECTS { hdsl2MaintLoopbackCommand, hdsl2MaintLoopbackStatus, hdsl2MaintLoopbackTimeout, hdsl2MaintLocalSpanPower, hdsl2MaintCustomerTipRingReversal, hdsl2MaintNetworkTipRingReversal, hdsl2MaintNetworkPowerBackOff, hdsl2MaintNetworkSoftRestart, hdsl2MaintCustomerPowerBackOff, hdsl2MaintCustomerSoftRestart } STATUS current DESCRIPTION "A collection of objects providing test configuration and control for a HDSL2 line." ::= { hdsl2Groups 6 } hdsl2EndpointAlarmConfGroup OBJECT-GROUP OBJECTS { hdsl2EndpointAlarmConfProfileName, hdsl2EndpointThreshLoopAttenuation, hdsl2EndpointThreshSNRMargin, hdsl2EndpointThreshES, hdsl2EndpointThreshSES, hdsl2EndpointThreshCRCanomaly, hdsl2EndpointThreshLOSWS, hdsl2EndpointThreshUAS, hdsl2EndpointAlarmConfProfileRowStatus } STATUS current DESCRIPTION "A collection of objects providing alarm configuration for a HDSL2 line." ::= { hdsl2Groups 7 } hdsl2NotificationGroup NOTIFICATION-GROUP NOTIFICATIONS { hdsl2LoopAttenCrossingTrap, hdsl2SNRMarginCrossingTrap, hdsl2PerfESThreshTrap, hdsl2PerfSESThreshTrap, hdsl2PerfCRCanomalyThreshTrap, hdsl2PerfLOSWThreshTrap, Expires November 8, 2000 Page [55] INTERNET-DRAFT HDSL2-LINE MIB May 2000 hdsl2PerfUASThreshTrap } STATUS current DESCRIPTION "A collection of trap objects for a HDSL2 line." ::= { hdsl2Groups 8 } hdsl2ShdslGroup OBJECT-GROUP OBJECTS { hdsl2ShdslWireInterface, hdsl2ShdslProfile } STATUS current DESCRIPTION "A collection of objects providing configuration support for a SHDSL line." ::= { hdsl2Groups 9 } hdsl2ShdslProfileGroup OBJECT-GROUP OBJECTS { hdsl2ShdslProfileName, hdsl2ShdslLineSpeed, hdsl2ShdslRemoteEnabled, hdsl2ShdslProfileRowStatus } STATUS current DESCRIPTION "A collection of objects providing dynamic profile support for a SHDSL line." ::= { hdsl2Groups 10 } hdsl2DS1ConfigGroup OBJECT-GROUP OBJECTS { hdsl2DS1htuIndex, hdsl2DS1ConfProfile, hdsl2DS1AlarmConfProfile } STATUS current DESCRIPTION "A collection of objects providing HTU DS1 configuration information for a HDSL2 line." ::= { hdsl2Groups 11 } hdsl2DS1PerfGroup OBJECT-GROUP OBJECTS { hdsl2DS1PerfCVL, hdsl2DS1PerfES, hdsl2DS1PerfSES, hdsl2DS1PerfLOSS, Expires November 8, 2000 Page [56] INTERNET-DRAFT HDSL2-LINE MIB May 2000 hdsl2DS1PerfCurr15MinTimeElapsed, hdsl2DS1PerfCurr15MinCVL, hdsl2DS1PerfCurr15MinES, hdsl2DS1PerfCurr15MinSES, hdsl2DS1PerfCurr15MinLOSS, hdsl2DS1PerfCurr1DayTimeElapsed, hdsl2DS1PerfCurr1DayCVL, hdsl2DS1PerfCurr1DayES, hdsl2DS1PerfCurr1DaySES, hdsl2DS1PerfCurr1DayLOSS } STATUS current DESCRIPTION "A collection of objects providing HTU DS1 performance information for a HDSL2 line." ::= { hdsl2Groups 12 } hdsl2DS1IntervalGroup OBJECT-GROUP OBJECTS { hdsl2DS1IntervalCVL, hdsl2DS1IntervalES, hdsl2DS1IntervalSES, hdsl2DS1IntervalLOSS } STATUS current DESCRIPTION "A collection of objects providing HTU DS1 performance information." ::= { hdsl2Groups 13 } hdsl2DS1HistoryGroup OBJECT-GROUP OBJECTS { hdsl2DS1HistoryMoniSecs, hdsl2DS1HistoryCVL, hdsl2DS1HistoryES, hdsl2DS1HistorySES, hdsl2DS1HistoryLOSS } STATUS current DESCRIPTION "A collection of objects providing historical HTU DS1 performance information." ::= { hdsl2Groups 14 } hdsl2DS1ProfileGroup OBJECT-GROUP OBJECTS { hdsl2DS1ProfileName, hdsl2DS1FrameFormat, hdsl2DS1LineCode, hdsl2DS1PulseEqualization, Expires November 8, 2000 Page [57] INTERNET-DRAFT HDSL2-LINE MIB May 2000 hdsl2DS1NetworkLoopback, hdsl2DS1DownstreamLOSD, hdsl2DS1UpstreamLOSD, hdsl2DS1ProfileRowStatus } STATUS current DESCRIPTION "A collection of objects providing HTU DS1 configuration support for a HDSL2 line." ::= { hdsl2Groups 15 } hdsl2DS1NotificationGroup NOTIFICATION-GROUP NOTIFICATIONS { hdsl2DS1CVLThreshTrap, hdsl2DS1ESThreshTrap, hdsl2DS1SESThreshTrap, hdsl2DS1LOSSThreshTrap } STATUS current DESCRIPTION "A collection of trap objects for a HTU DS1 interface." ::= { hdsl2Groups 16 } END 7. Security Considerations Security issues are not discussed in this memo. 8. Acknowledgments The author is deeply grateful to the authors of the ADSL LINE MIB (RFC 2662 [25]), Gregory Bathrick and Faye Ly, as much of the text and structure of this document originates in their documents. The author acknowledges the suggestions and contributions of Rajesh Abbi of Alcatel regarding the textual convention Hdsl2UnitId. The author also acknowledges the importance of contributions and suggestions regarding interface indexing structures received from David Horton of CITR. Other contributions were received from the following: Philip Bergstresser (Adtran) Steve Blackwell (Adtran) Mark Johnson (Red Point) Mike Sneed (Pulse) Expires November 8, 2000 Page [58] INTERNET-DRAFT HDSL2-LINE MIB May 2000 9. References [1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for Describing SNMP Management Frameworks", RFC 2571, April 1999. [2] Rose, M., and K. McCloghrie, "Structure and Identification of Management Information for TCP/IP-based Internets", STD 16, RFC 1155, May 1990. [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 16, RFC 1212, March 1991. [4] M. Rose, "A Convention for Defining Traps for use with the SNMP", RFC 1215, March 1991. [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999. [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999. [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network Management Protocol", STD 15, RFC 1157, May 1990. [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Introduction to Community-based SNMPv2", RFC 1901, January 1996. [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1906, January 1996. [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)", RFC 2572, April 1999. [12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 2574, April 1999. [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1905, January 1996. [14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 2573, April 1999. Expires November 8, 2000 Page [59] INTERNET-DRAFT HDSL2-LINE MIB May 2000 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)", RFC 2575, April 1999. [16] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction to Version 3 of the Internet-standard Network Management Framework", RFC 2570, April 1999. [17] Bradner, S., "Key Words for use in RFCs to Indicate Requirement Levels", RFC 2119, March 1997. [18] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure of Management Information for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, January 1996. [19] Case, J., McCloghrie, K., Rose, M. and Waldbusser, S., "Textual Conventions for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1903, January 1996. [20] American National Standards Institute, ANSI T1E1.4/2000-006, February 2000. [21] Blackwell, S., Editor, "Single-Pair High-Speed Digital Subscriber Line (SHDSL) Transceivers", ITU-T Draft G.991.2, April 2000. [22] McCloghrie, K., and M. Rose, Editors, "Management Information Base for Network Management of TCP/IP-based internets: MIB-II", STD 17, RFC 1213, March 1991. [23] McCloghrie, K., and Kastenholz, F., "The Interfaces Group MIB using SMIv2", RFC 2233, November 1997. [24] Tesink, K., "Textual Conventions for MIB Modules Using Performance History Based on 15 Minute Intervals", RFC 2493, January 1999. [25] Bathrick, G., Ly, F., "Definitions of Managed Objects for the ADSL Lines", RFC 2662, August 1999. [26] D. Harrington, R. Presuhn, B. Wijnen, "An architecture for Describing SNMP Management Frameworks", RFC 2571, April 1999. 10. Intellectual Property Notice The IETF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be found in BCP-11. Copies of claims of rights made available for publication and any assurances of Expires November 8, 2000 Page [60] INTERNET-DRAFT HDSL2-LINE MIB May 2000 licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementors or users of this specification can be obtained from the IETF Secretariat. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director. 11. Authors' Addresses Bob Ray Verilink Corporation 127 Jetplex Circle Madison, AL 35758 USA Tel: +1 256-774-2380 Fax: +1 256-774-2277 E-mail: bray@verilink.com 12. Full Copyright Statement Copyright (C) The Internet Society (1999). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Expires November 8, 2000 Page [61]