INTERNET-DRAFT Supplemental ADSL Line MIB Gregory Bathrick AG Communication Systems Faye Ly Copper Mountain Networks May 10, 1999 Definitions of Supplemental Managed Objects for ADSL Lines May 10, 1999 draft-ietf-adslmib-adsl2-00.txt 1. Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. 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). 2. Abstract This document defines a standard SNMP MIB for additional functions not covered by the ADSL Line MIB [1]. ADSL Line MIB defines management objects common for all ADSL lines regardless of line- codes, as defined by ANSI T1.413. This MIB defines a supplemental Expires August 1999 [Page 1] INTERNET-DRAFT ADSL Line MIB Febuary 26, 1999 set of managed objects defined by ITU G.997.1 [8]. In particular, it describes objects used to manage ADSL "Lite" interfaces as defined by ITU-T G.992.2 [9]. 3. The SNMP Network Management Framework The SNMP Management Framework presently consists of five major components: o An overall architecture, described in RFC 2271 [13]. 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 RFC 1155 [14], RFC 1212 [15] and RFC 1215 [16]. The second version, called SMIv2, is described in RFC 1902 [1], RFC 1903 [2] and RFC 1904 [17]. o Message protocols for transferring management information. The first version of the SNMP message protocol is called SNMPv1 and described in RFC 1157 [7]. A second version of the SNMP message protocol, which is not an Internet standards track protocol, is called SNMPv2c and described in RFC 1901 [18] and RFC 1906 [19]. The third version of the message protocol is called SNMPv3 and described in RFC 1906 [19], RFC 2272 [20] and RFC 2274 [21]. o Protocol operations for accessing management information. The first set of protocol operations and associated PDU formats is described in RFC 1157 [7]. A second set of protocol operations and associated PDU formats is described in RFC 1905 [8]. o A set of fundamental applications described in RFC 2273 [22] and the view-based access control mechanism described in RFC 2275 [23]. 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 document 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 (e.g., use of Counter64). Some machine readable information in SMIv2 will be converted into textual descriptions in SMIv1 during the translation process. However, this Expires August 1999 [Page 2] INTERNET-DRAFT ADSL Line MIB Febuary 26, 1999 loss of machine readable information is not considered to change the semantics of the MIB. 4. 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 extended 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. 5. Introduction The purpose of this memo is to define a supplemental set of managed objects that is not covered by ADSL Line MIB as defined in [10]. This memo addresses the additional objects defined in ITU G.997.1 [8]. These additional objects specifically address the management capabilities of ADSL "Lite" as defined by ITU-T G.992.2 [9]. 6. Relationship of the Supplemental ADSL LINE MIB with standard MIBs This section outlines the relationship of Supplemental ADSL Line MIB with other MIBs described in RFCs and in their various degrees of "standardization". Supplemental ADSL Line MIB obeys the same relationship between ADSL Line MIB to other standard MIBs. 7. Conventions used in the MIB 7.1 Naming Conventions In addition to the naming conventions defined in the ADSL Line MIB [1] section 7. This document defines the following naming conventions as well: A. Block Definition ADSL Line MIB defines a "block" as "a physical-layer `data buffer' over which CRCs are calculated". This document further clarifies Expires August 1999 [Page 3] INTERNET-DRAFT ADSL Line MIB Febuary 26, 1999 that a "block" referred in this MIB is defined as "a physical-layer 'data buffer' over which CRCs are calculated or a superframe. A "superframe" is defined as "???". . what is a R-S frame . 68 R-S frames compose a superframe? 7.2 Structure The MIB is organized to follow the same structure of the ADSL Line MIB [1]. 7.3 Additional Managed Objects A few objects are added to cover the ADSL "Lite" management and they are: - ATU-C Transmission System Capabilities - Power Management - Counters for Fast Retrains and Failed Fast Retrains - Counters for Severed Error Second-line and Unavailable Second - Correct Definition of Blocks Besides the management of ADSL "Lite", another object needs to be added to the ADSL Line MIB [10] in order to manage the ADSL line profile. The object is the line mode configuration. The MIB definitions are attached. The MIB will be branched from the ADSL Line MIB [10]. 7.3.1 ATU-C ADSL Transmission System Enabling The adslLineConfigTable needs to be extended to cover the ATU-C ADSL Transmission system enabling. Objects are defined to enable the configuration and monitoring of the ATU-C and ATU-R transmission system capabilities as well as the actual ADSL transmission system being used. 7.3.2 Power Management Specifically the ATU-C and ATU-R Total Output Power ?? 7.3.3 Fast Retrain Parameters Section 7.4.15 of ITU G.997.1 specifies fast retrain parameters. Fast retrain parameters include two counters: fast retrain count and failed fast retrain count. These two counters need to be added to all performance tables. Expires August 1999 [Page 4] INTERNET-DRAFT ADSL Line MIB Febuary 26, 1999 7.3.4 Counters for Severed Error Second-line and Unavailable Second Section 7.2.1.1.7 and section 7.2.1.1.9 specify two counters that are not covered by the ADSL Line MIB [10]. These two counters (severed error second-line and unavailable second) are added to all the performance tables. 7.3.5 Correct Definition of Blocks Correct block definition used by ADSL MIB is specified in section 7.1.A. 7.3.6 ADSL Line Mode configuration The adslLineConfProfileTable is extended to include a new object that allow operator to specify the line mode in a profile entry. 8. Conformance and Compliance See the conformance and compliance statements within the information module. 9. Definitions ADSL2-LINE-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, Gauge32, OBJECT-TYPE, mib-2 FROM SNMPv2-SMI TEXTUAL-CONVENTION FROM SNMPv2-TC adslMIB FROM ADSL-LINE-MIB ; adsl2MIB MODULE-IDENTITY LAST-UPDATED "9905141200Z" ORGANIZATION "IETF ADSL MIB Working Group" CONTACT-INFO " Gregory Bathrick AG Communication Systems A Subsidiary of Lucent Technologies 2500 W Utopia Rd. Phoenix, AZ 85027 USA Tel: +1 602-582-7679 Expires August 1999 [Page 5] INTERNET-DRAFT ADSL Line MIB Febuary 26, 1999 Fax: +1 602-582-7697 E-mail: bathricg@agcs.com Faye Ly Copper Mountain Networks Norcal Office 2470 Embarcadero Way Palo Alto, CA 94303 Tel: +1 650-858-8500 X240 E-Mail: faye@coppermountain.com DESCRIPTION "This MIB Module is a supplement to the ADSL-LINE-MIB [1]." ::= { adslMIB 2 } adsl2MIBObjects OBJECT IDENTIFIER ::= {atm2MIB 1} AdslTransmissionModeType ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "This data type is used as the syntax ADSL line transmission mode. The transmission mode is defined as: Bit 01 : Regional Std. (ANSI T1.413) Bit 02 : Regional Std. (ETSI DTS/TM06006) Bit 03 : G.992.1 POTS non-overlapped Bit 04 : G.992.1 POTS overlapped Bit 05 : G.992.1 ISDN non-overlapped Bit 06 : G.992.1 ISDN overlapped Bit 07 : G.992.1 TCM-ISDN non-overlapped Bit 08 : G.992.1 TCM-ISDN overlapped Bit 09 : G.992.2 POTS non-overlapped Bit 10 : G.992.2 POTS overlapped Bit 11 : G.992.2 with TCM-ISDN non-overlapped Bit 12 : G.992.2 with TCM-ISDN overlapped " SYNTAX BITS { ansit1413(1), etsi(2), 9921potsnon-overlapped(3), 9921potsoverlapped(4), 9921isdnnon-overlapped(5), 9921isdnoverlapped(6), 9921tcm-isdnnon-overlapped(7), 9921tcm-isdn-overlapped(8), 9922potsnon-overlapeed(9), 9922potsoverlapped(10), 9922tcm-isdnnon-overlapped(11), Expires August 1999 [Page 6] INTERNET-DRAFT ADSL Line MIB Febuary 26, 1999 9922tcm-isdn-overlapped(12) } adslLineExtTable OBJECT-TYPE SYNTAX SEQUENCE OF AdslExtLineEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains ADSL line configuration and monitoring information not defined in the adslLineTable from the ADSL-LINE-MIB [1]. This includes the capabilities and actual ADSL transmission system." ::= { adslMibObjects 17 } adslExtLineEntry OBJECT-TYPE SYNTAX AdslExtLineEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry extends the adslLineEntry defined in [1]. Each entry corresponds to an ADSL line." AUGMENTS { adslLineEntry } ::= { adslLineTable 1 } AdslExtLineEntry ::= SEQUENCE { adslLineTransAtucCap AdslTransmissionModeType, adslLineTransAturCap AdslTransmissionModeType, adslLineTransCapActual AdslTransmissionModeType } adslLineTransAtucCap OBJECT-TYPE SYNTAX AdslTransmissionModeType MAX-ACCESS read-only STATUS current DESCRIPTION "Specifies the ATU-C Transmission system capability." REFERENCE "Section 7.3.2 ITU G.997.1 [8]" ::= { adslExtLineEntry 1 } adslLineTransAturCap OBJECT-TYPE SYNTAX AdslTransmissionModeType MAX-ACCESS read-only Expires August 1999 [Page 7] INTERNET-DRAFT ADSL Line MIB Febuary 26, 1999 STATUS current DESCRIPTION "Specifies the ATU-R Transmission system capability." REFERENCE "Section 7.3.2 ITU G.997.1 [8]" ::= { adslExtLineEntry 2 } adslLineTransCapActual OBJECT-TYPE SYNTAX AdslTransmissionModeType MAX-ACCESS read-only STATUS current DESCRIPTION "Specifies the actual Transmission system capability for this ADSL line." REFERENCE "Section 7.3.2 ITU G.997.1 [8]" ::= { adslExtLineEntry 3 } adslAtucPerfDataExtTable OBJECT-TYPE SYNTAX SEQUENCE OF AdslAtucPerfDataExtEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains ADSL physical line counters information not defined in the adslAtucPerfDataTable from the ADSL- LINE-MIB [10]." ::= { adslMibObjects 18 } adslAtucPerfDataExtEntry OBJECT-TYPE SYNTAX AdslAtucPerfDataExtEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry extends the adslAtucPerfDataEntry defined in [10]. Each entry corresponds to an ADSL line." AUGMENTS { adslAtucPerfDataEntry } ::= { adslAtucPerfDataTable 1 } AdslAtucPerfDataEntry ::= SEQUENCE { adslAtucPerfStatFastR Counter32, adslAtucPerfStatFailedFastR Counter32, adslAtucPerfStatSesL Counter32, adslAtucPerfStatUasL Counter32, adslAtucPerfCurr15FastR PerfCurrentCount, adslAtucPerfCurr15FailedFastR PerfCurrentCount, adslAtucPerfCurr15MinSesL PerfCurrentCount, adslAtucPerfCurr15MinUasL PerfCurrentCount, Expires August 1999 [Page 8] INTERNET-DRAFT ADSL Line MIB Febuary 26, 1999 adslAtucPerfCurr1DayFastR AdslPerfCurrDayCount, adslAtucPerfCurr1DayFailedFastR AdslPerfCurrDayCount, adslAtucPerfCurr1DaySesL AdslPerfCurrDayCount, adslAtucPerfCurr1DayUasL AdslPerfCurrDayCount, adslAtucPerfPrev1DayFastR AdslPerfPrevDayCount, adslAtucPerfPrev1DayFailedFastR AdslPerfPrevDayCount adslAtucPerfPrev1DaySesL AdslPerfPrevDayCount, adslAtucPerfPrev1DayUasL AdslPerfPrevDayCount } adslAtucPerfStatFastR OBJECT-TYPE SYNTAX Counter MAX-ACCESS read-only STATUS current DESCRIPTION "The value of this object indicates the count of fast retrains." REFERENCE "ITU G.997.1 Section 7.4.15.1 [8]" ::= { adslAtucPerfDataEntry 1 } adslLineStatFailedFRetrains OBJECT-TYPE SYNTAX Counter MAX-ACCESS read-only STATUS current DESCRIPTION "The value of this object indicates the count of failed fast retrains." REFERENCE "ITU G.997.1 Section 7.4.15.2 [8]" ::= { adslAtucPerfDataEntry 2 } adslAtucPerfStatSesL OBJECT-TYPE SYNTAX Counter32 UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "The value of this object indicates the count of severely errored second-line." REFERENCE "ITU G.997.1 Section 7.2.1.1.7 [8]" ::= { adslAtucPerfDataEntry 3 } adslAtucPerfStatUasL OBJECT-TYPE SYNTAX Counter32 UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "The value of this object indicates the count of Expires August 1999 [Page 9] INTERNET-DRAFT ADSL Line MIB Febuary 26, 1999 unavailable second." REFERENCE "ITU G.997.1 Section 7.2.1.1.9 [8]" ::= { adslAtucPerfDataEntry 4 } adslAtucPerfCurr15MinFastR OBJECT-TYPE SYNTAX PerfCurrentCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of seconds in the current 15 minute interval when there was fast retrains." REFERENCE "ITU G.997.1 Section 7.4.15.1 [8]" ::= { adslAtucPerfDataEntry 5 } adslAtucPerfCurr15MinFailedFastR OBJECT-TYPE SYNTAX PerfCurrentCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of seconds in the current 15 minute interval when there was failed fast retrains." REFERENCE "ITU G.997.1 Section 7.4.15.2 [8]" ::= { adslAtucPerfDataEntry 6 } adslAtucPerfCurr15MinSesL OBJECT-TYPE SYNTAX PerfCurrentCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of seconds in the current 15 minute interval when there was fast retrains." REFERENCE "ITU G.997.1 Section 7.2.1.1.7 [8]" ::= { adslAtucPerfDataEntry 7 } adslAtucPerfCurr15MinUasL OBJECT-TYPE SYNTAX PerfCurrentCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of seconds in the current 15 minute interval when there was count for unavailable errored seconds." REFERENCE "ITU G.997.1 Section 7.2.1.1.9 [8]" ::= { adslAtucPerfDataEntry 8 } Expires August 1999 [Page 10] INTERNET-DRAFT ADSL Line MIB Febuary 26, 1999 adslAtucPerfCurr1DayFastR OBJECT-TYPE SYNTAX AdslPerfCurrDayCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of the number of seconds when there was fast retrains during the current day as measured by adslAtucPerfCurr1DayTimeElapsed." REFERENCE "ITU G.997.1 Section 7.4.15.1 [8]" ::= { adslAtucPerfDataEntry 9 } adslAtucPerfCurr1DayFailedFastR OBJECT-TYPE SYNTAX AdslPerfCurrDayCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of the number of seconds when there was failed fast retrains during the current day as measured by REFERENCE "ITU G.997.1 Section 7.4.15.2 [8]" ::= { adslAtucPerfDataEntry 10 } adslAtucPerfCurr1DaySesL OBJECT-TYPE SYNTAX AdslPerfCurrDayCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of the number of seconds when there was Severed Errored Seconds during the current day as measured by adslAtucPerfCurr1DayTimeElapsed." REFERENCE "ITU G.997.1 Section 7.2.1.1.7 [8]" ::= { adslAtucPerfDataEntry 11 } adslAtucPerfCurr1DayUasL OBJECT-TYPE SYNTAX AdslPerfCurrDayCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of the number of seconds when there was Unavailable Errored Seconds during the current day as measured by Expires August 1999 [Page 11] INTERNET-DRAFT ADSL Line MIB Febuary 26, 1999 adslAtucPerfCurr1DayTimeElapsed." REFERENCE "ITU G.997.1 Section 7.2.1.1.9 [8]" ::= { adslAtucPerfDataEntry 12 } adslAtucPerfPrev1DayFastR OBJECT-TYPE SYNTAX AdslPerfPrevDayCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of seconds in the interval when there was fast retrains within the most recent previous 1-day period." REFERENCE "ITU G.997.1 Section 7.4.15.1 [8]" ::= { adslAtucPerfDataEntry 13 } adslAtucPerfPrev1DayFailedFastR OBJECT-TYPE SYNTAX AdslPerfPrevDayCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of seconds in the interval when there was failed fast retrains within the most recent previous 1-day period." REFERENCE "ITU G.997.1 Section 7.4.15.2 [8]" ::= { adslAtucPerfDataEntry 14 } adslAtucPerfPrev1DaySesL OBJECT-TYPE SYNTAX AdslPerfPrevDayCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of seconds in the interval when there was severed errored seconds within the most recent previous 1-day period." REFERENCE "ITU G.997.1 Section 7.2.1.1.7 [8]" ::= { adslAtucPerfDataEntry 15 } adslAtucPerfPrev1DayFailedUasL OBJECT-TYPE SYNTAX AdslPerfPrevDayCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of seconds in the interval when there was Expires August 1999 [Page 12] INTERNET-DRAFT ADSL Line MIB Febuary 26, 1999 unavailable errored seconds within the most recent previous 1-day period." REFERENCE "ITU G.997.1 Section 7.2.1.1.9 [8]" ::= { adslAtucPerfDataEntry 16 } adslAturPerfDataExtTable OBJECT-TYPE SYNTAX SEQUENCE OF AdslAturPerfDataExtEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains ADSL physical line counters information not defined in the adslAturPerfDataTable from the ADSL- LINE-MIB [10]." ::= { adslMibObjects 19 } adslAturPerfDataExtEntry OBJECT-TYPE SYNTAX AdslAturPerfDataExtEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry extends the adslAturPerfDataEntry defined in [10]. Each entry corresponds to an ADSL line." AUGMENTS { adslAturPerfDataEntry } ::= { adslAturPerfDataTable 1 } AdslAturPerfDataEntry ::= SEQUENCE { adslAturPerfStatSesL Counter32, adslAturPerfStatUasL Counter32, adslAturPerfCurr15MinSesL PerfCurrentCount, adslAturPerfCurr15MinUasL PerfCurrentCount, adslAturPerfCurr1DaySesL AdslPerfCurrDayCount, adslAturPerfCurr1DayUasL AdslPerfCurrDayCount, adslAturPerfPrev1DaySesL AdslPerfPrevDayCount, adslAturPerfPrev1DayUasL AdslPerfPrevDayCount } adslAturPerfStatSesL OBJECT-TYPE SYNTAX Counter32 UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "The value of this object indicates the count of severely errored second-line." REFERENCE "ITU G.997.1 Section 7.2.1.1.7 [8]" ::= { adslAturPerfDataEntry 1 } Expires August 1999 [Page 13] INTERNET-DRAFT ADSL Line MIB Febuary 26, 1999 adslAturPerfStatUasL OBJECT-TYPE SYNTAX Counter32 UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "The value of this object indicates the count of unavailable second." REFERENCE "ITU G.997.1 Section 7.2.1.2.9 [8]" ::= { adslAturPerfDataEntry 2 } adslAturPerfCurr15MinSesL OBJECT-TYPE SYNTAX PerfCurrentCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of seconds in the current 15 minute interval when there was Severed Errored Seconds-Line." REFERENCE "ITU G.997.1 Section 7.2.1.2.7 [8]" ::= { adslAturPerfDataEntry 3 } adslAturPerfCurr15MinUasL OBJECT-TYPE SYNTAX PerfCurrentCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of seconds in the current 15 minute interval when there was Unavailable Errored Seconds." REFERENCE "ITU G.997.1 Section 7.2.1.2.9 [8]" ::= { adslAturPerfDataEntry 4 } adslAturPerfCurr1DaySesL OBJECT-TYPE SYNTAX AdslPerfCurrDayCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of the number of seconds when there was Severed Errored Seconds during the current day as measured by adslAturPerfCurr1DayTimeElapsed." REFERENCE "ITU G.997.1 Section 7.2.1.2.7 [8]" ::= { adslAturPerfDataEntry 5 } Expires August 1999 [Page 14] INTERNET-DRAFT ADSL Line MIB Febuary 26, 1999 adslAturPerfCurr1DayUasL OBJECT-TYPE SYNTAX AdslPerfCurrDayCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of the number of seconds when there was Unavailable Errored Seconds during the current day as measured by adslAturPerfCurr1DayTimeElapsed." REFERENCE "ITU G.997.1 Section 7.2.1.2.9 [8]" ::= { adslAturPerfDataEntry 6 } adslAturPerfPrev1DaySesL OBJECT-TYPE SYNTAX AdslPerfPrevDayCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of seconds in the interval when there was severed errored second within the most recent previous 1-day period." REFERENCE "ITU G.997.1 Section 7.2.1.2.7 [8]" ::= { adslAturPerfDataEntry 7 } adslAturPerfPrev1DayUasL OBJECT-TYPE SYNTAX AdslPerfPrevDayCount UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Count of seconds in the interval when there was unvailable errored second within the most recent previous 1-day period." REFERENCE "ITU G.997.1 Section 7.2.1.2.9 [8]" ::= { adslAturPerfDataEntry 8 } adslExtConfProfileTable OBJECT-TYPE SYNTAX SEQUENCE OF AdslExtConfProfileEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains ADSL line profile configuration information not defined in the adslLineConfProfileTable Expires August 1999 [Page 15] INTERNET-DRAFT ADSL Line MIB Febuary 26, 1999 from the ADSL-LINE-MIB [1]. This includes the line mode." ::= { adslMibObjects 19 } adslExtConfPrifleEntry OBJECT-TYPE SYNTAX AdslExtConfProfileEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry extends the adslLineConfPrifileEntry defined in [1]. Each entry corresponds to an ADSL line profile." AUGMENTS { adslLineConfProfileEntry } ::= { adslExtConfProfileTable 1 } AdslExtConfProfileEntry ::= SEQUENCE { adslExtConfPorifleLineMode INTEGER } adslExtConfProfileLineMode OBJECT-TYPE SYNTAX INTEGER { noChannel (1), -- no channels exist fastOnly (2), -- fast channel exists only interleavedOnly (3), -- interleaved channel exists -- only fastOrInterleaved (4),-- either fast or interleaved -- channels can exist, but -- only one at any time fastAndInterleaved (5)-- both fast or interleaved -- channels exist } MAX-ACCESS read-create STATUS current DESCRIPTION " This object is used to configure the ADSL physical line mode. " ::= { adslExtConfProfileEntry 1 } -- conformance information adsl2Conformance OBJECT IDENTIFIER ::= { adslLineMib 5 } adsl2Groups OBJECT IDENTIFIER ::= { adsl2Conformance 1 } adsl2Compliances OBJECT IDENTIFIER ::= { adsl2Conformance 2 } Expires August 1999 [Page 16] INTERNET-DRAFT ADSL Line MIB Febuary 26, 1999 -- ATU-C agent compliance statements adsl2LineMibAtucCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for SNMP entities which manage ADSL ATU-C interfaces." MODULE -- this module MANDATORY-GROUPS { adsl2LineGroup, adsl2AtucPhysPerfRawCounterGroup, adsl2AturPhysPerfRawCounterGroup, adsl2LineConfProfileControlGroup OBJECT-GROUP } GROUP adsl2AtucPhysPerfRawCounterGroup DESCRIPTION "This group is optional. Implementations which require continuous ATU-C physical event counters should implement this group." GROUP adsl2AturPhysPerfRawCounterGroup DESCRIPTION "This group is optional. Implementations which require continuous ATU-R physical event counters should implement this group." adsl2LineGroup OBJECT-GROUP OBJECTS { adslLineTransAtucCap, adslLineTransAturCap, adslLineTransCapActual } STATUS current DESCRIPTION "A collection of objects providing configuration information about an ADSL Line." ::= { adsl2Groups 1 } adsl2AtucPhysPerfRawCounterGroup OBJECT-GROUP OBJECTS { adslAtucPerfStatFastR, adslAtucPerfStatFailedFastR, adslAtucPerfCurr15FastR, adslAtucPerfCurr15FailedFastR, adslAtucPerfCurr1DayFastR, adslAtucPerfCurr1DayFailedFastR, adslAtucPerfPrev1DayFastR, Expires August 1999 [Page 17] INTERNET-DRAFT ADSL Line MIB Febuary 26, 1999 adslAtucPerfPrev1DayFailedFastR, adslAtucPerfStatSesL, adslAtucPerfStatUasL, adslAtucPerfCurr15MinSesL, adslAtucPerfCurr15MinUasL, adslAtucPerfCurr1DaySesL, adslAtucPerfCurr1DayUasL, adslAtucPerfPrev1DaySesL, adslAtucPerfPrev1DayUasL } STATUS current DESCRIPTION "A collection of objects providing raw performance counts on an ADSL Line (ATU-C end)." ::= { adsl2Groups 2 } adsl2AturPhysPerfRawCounterGroup OBJECT-GROUP OBJECTS { adslAturPerfStatSesL, adslAturPerfStatUasL, adslAturPerfCurr15MinSesL, adslAturPerfCurr15MinUasL, adslAturPerfCurr1DaySesL, adslAturPerfCurr1DayUasL, adslAturPerfPrev1DaySesL, adslAturPerfPrev1DayUasL } STATUS current DESCRIPTION "A collection of objects providing raw performance counts on an ADSL Line (ATU-C end)." ::= { adsl2Groups 3 } adsl2LineConfProfileControlGroup OBJECT-GROUP OBJECTS { adslExtConfPorifleLineMode } STATUS current DESCRIPTION "A collection of objects providing profile control for the ADSL system." ::= { adsl2Groups 4 } END 9. Acknowledgments This document is a product of the ADSL MIB Working Group. 10. References Expires August 1999 [Page 18] INTERNET-DRAFT ADSL Line MIB Febuary 26, 1999 [1] 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. [2] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual Conventions for SNMPv2", RFC 1903, SNMP Research, Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., International Network Services, January 1996. [3] McCloghrie, K., and M. Rose, Editors, "Management Information Base for Network Management of TCP/IP-based internets: MIB-II", STD 17, RFC 1213, Hughes LAN Systems, Performance Systems International, March 1991. [4] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB using SMIv2", RFC 2233, Cisco Systems, FTP Software, November 1997. [5] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Management Information Base for version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1907, January 1996. [6] Case, J., Fedor, M., Schoffstall, M., and J. Davin. " A Simple Network Management Protocol (SNMP)", STD 15, RFC 1157, SNMP Research, Performance Systems International, MIT Lab for Computer Science, May 1990. [7] SNMPv2 Working Group, 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. [8] ITU Draft Recommendation G.997.1 "Physical Layer Management for Digital Subscriber Line (DSL) Transceivers.", January 1999 [9] Chris Hansen, ITU "White Paper submission of Recommendation G.992.2" June/July 1999. [10] G. Bathrick, F. Ly "Definitions of Managed Objects for the ADSL Lines", May 14, 1999. Expires August 1999 [Page 19]