1ADSL ForumTechnical Report TR-024PreviouslyWorking TextWT-036v2DMT Line Code Specific MIBFor Network Management Working GroupJune 1999Abstract:This technical report defines a standard SNMP MIB for the DMT line code.Configuration, statistics, performance and history count elements are defined elements forDMT coded lines. These elements cover use during normal operation of ADSL lines aswell as detailed measurements for fault prediction and location.Notice:The ADSL Forum is a non-profit corporation organized to create guidelines for ADSL network systemdevelopment and deployment. This Technical Report has been approved by members of the Forum,however it is not binding on the ADSL Forum, any of its members, or any developer or service providerinvolved in ADSL. The document is subject to change, but only with approval of members of the Forum.
`
`

`
`DMT Line Code Specific MIB
`
`ADSL Forum TR—024
`
`Table of Contents
`
`1. INTRODUCTION .............................................................................................................................................3
`
`2. DMT LCS NIIB STRUCTURE .........................................................................................................................3
`
`3. DMT LCS NIIB TABLES..................................................................................................................................5
`
`4. DMT DEFINITIONS FOR ADSL LINE MIB ..................................................................................................6
`
`5. REFERENCES ..................................................................................................................................................7
`
`ASN-1 FORMAT DMT LINE CODE SPECIFIC NIIB. ......................................................................................8
`
`FIGURE 1. DMT LINE CODE SPECIFIC MIB .................................................................................................4
`
`List of Figt_1res
`
`3.1 DMT LINETABLE ........................................................................................................................................ ..5
`3.2 DMT PHYSICAL TABLES ............................................................................................................................... ..5
`3.3 DMT CHANNEL TABLES ............................................................................................................................... ..5
`3.4 DMT PHYSICAL PERFORMANCE TABLES ........................................................................................................ ..5
`3.5 DMT PHYSICAL INTERVAL TABLES ............................................................................................................... ..6
`3.6 DMT CHANNEL PERFORMANCE TABLES ........................................................................................................ ..6
`3.7 DMT CHANNEL INTERVAL TABLES ............................................................................................................... ..6
`3.8 PROFILE GROUP ............................................................................................................................................ ..6
`3.9 ALARM CONFIGURATION PROFILE TABLES ..................................................................................................... ..6
`
`DMT Line Code Specific MIBADSL Forum TR-0242Table of Contents1. INTRODUCTION.............................................................................................................................................32. DMT LCS MIB STRUCTURE.........................................................................................................................33. DMT LCS MIB TABLES..................................................................................................................................53.1 DMT LINE TABLE..........................................................................................................................................53.2 DMT PHYSICAL TABLES.................................................................................................................................53.3 DMT CHANNEL TABLES.................................................................................................................................53.4 DMT PHYSICAL PERFORMANCE TABLES..........................................................................................................53.5 DMT PHYSICAL INTERVAL TABLES.................................................................................................................63.6 DMT CHANNEL PERFORMANCE TABLES..........................................................................................................63.7 DMT CHANNEL INTERVAL TABLES.................................................................................................................63.8 PROFILE GROUP..............................................................................................................................................63.9 ALARM CONFIGURATION PROFILE TABLES.......................................................................................................64. DMT DEFINITIONS FOR ADSL LINE MIB..................................................................................................65. REFERENCES..................................................................................................................................................7ASN-1 FORMAT DMT LINE CODE SPECIFIC MIB.......................................................................................8List of FiguresFIGURE 1. DMT LINE CODE SPECIFIC MIB.................................................................................................4
`
`

`
`DMT Line Code Specific MIBADSL Forum TR-02431. IntroductionThis technical report details the elements of a Line Code Specific (LCS) MIB for ITU G.992.1 and G.992.2 (andreferenced regional standards) based Discrete Multi-Tone (DMT) ADSL lines including formal object definitionsin ASN-1. Configuration profiles and current performance statistics are defined. This LCS MIB text fills the spacein the ADSL line MIB defined by the ADSL Forum in TR-006 where line code specific details for ATU-C andATU-R are left for future definition. The DMT LCS MIB detail is presented in ASN-1 format at the end of thedocument.2. DMT LCS MIB StructureThe following additions are made to the generic ADSL Line MIB:•To facilitate a general purpose LCS architecture, the adslLCSMib element is added to the adslMibObjectsstructure. All LCS MIB tables are based off this element, including adslDMTMibObjects.•LCS tables are added under this new structure for each LCS type. These tables are organised identically to theelements under adslMibObjects. These tables perform the same functions as the tables under adslMibObjects;only their scope is limited to LCS parameters.•The LCS tables use the INDEX clause, allowing them to be indexed as logical extensions of the generic lineMIB tables.Figure 1 shows the DMT LCS MIB structure and how it extends the ADSL Line MIB. Although the MIB structureis in place to add LCS tables that correspond to all tables in adslMibObjects, not all are required for DMT. Asshown in Figure 1, the DMT LCS MIB only requires the following LCS tables:•DMT line table (i.e. actual configuration) for the line.•Physical tables (i.e. actuals) for both ATU-C and ATU-R.•Line configuration profile table.Following the precedent of ADSL Forum reports TR-005 and TR-006, this MIB definition assumes that the SNMPagent is located at the ATU-C and acts as a proxy for the ATU-R. The mechanisms by which the ATU-C controlsand monitors the ATU-R is mainly through standard DMT ADSL exchanges and the mechanism specific to eachobject in the DMT LCS MIB is identified in the attached ASN-1 code. Because the DMT LCS MIB resides at thecentral office and the SNMP agent proxies the ATU-R, some ATU-R elements may not be correctly reported whenthe link is not in steady state.
`
`

`
`DMT Line Code Specific MIBADSL Forum TR-0244adslMibObjects (1)adslLineDMTTable (1)adslAtucDMTPhysTable (2)adslAturDMTPhysTable (3)adslAtucDMTChanTable (4)adslAturDMTChanTable (5)adslAtucDMTPerfDataTable (6)adslAturDMTPerfDataTable (7)adslAtucDMTIntervalTable (8)adslAtucDMTIntervalTable (9)adslAtucDMTChanPerfDataTable (10)adslAturDMTChanPerfDataTable (11)adslAtucDMTChanIntervalTable (12)adslAturDMTChanIntervalTable (13)adslLineDMTConfProfileTable (14)adslLineDMTAlarmConfProfileTable (15)adslDMTMibObjects (1)4 items4 items3 itemsadslDMTMib(1)adslDMTConformance (3)1 itemadslLCSMib (16)adslLineTable (1)adslAtucPhysTable (2)adslAturPhysTable (3)adslAtucChanTable (4)adslAturChanTable (5)adslAtucPerfDataTable (6)adslAturPerfDataTable (7)adslAtucIntervalTable (8)adslAtucChanPerfDataTable (10)adslAturChanPerfDataTable (11)adslAtucChanIntervalTable (12)adslAturChanIntervalTable (13)adslLineConfProfileTable (14)adslLineAlarmConfProfileTable (15)adslAtucIntervalTable (9)adslDMTTraps (2)Figure 1. DMT Line Code Specific MIB
`
`

`
`DMT Line Code Specific MIBADSL Forum TR-02453. DMT LCS MIB TablesTo facilitate a general purpose LCS architecture, the adslLCSMib object is added to the adslMibObjects structure inTR006. All LCS MIB tables are based off this element, including adslDMTMibObjects.3.1 DMT Line TableThe DMT physical line table, adslLineDMTTable, reports the following elements common to the line that resultfrom a successful line initialisation and training process:•Report whether autonomous data streaming1 is allowed on the eoc or only transaction based data exchangesusing the adslLineDMTEOC object. See ITU recommendation G.997.1 and 994.1 for further details.3.2 DMT Physical TablesThe adslAtucDMTPhysTable and adslAturDMTPhysTable tables contain DMT specific operating statusinformation. This includes ATU state as well as per bin information for bit loading, SNR and attenuation.Both ATU-C state and ATU-R state are reported by the relevant physical tables (objects adslAtucDMTState andadslAturDMTState) and will change dynamically. The ATU-R status may not be current and depends on having anoperating link to be reported because the SNMP agent proxies the ATU-R.During start-up each ATU determines the SNR in each bin. In addition an approximation of the signal attenuationat that frequency is calculated. This information is used to calculate the bit loading (bits and gain) to achieve theconfigured rate. Once in SHOWTIME each ATU continues to monitor the SNR and uses this information tosuggest bit swaps (or dynamic rate changes if this optional procedure is implemented) which causes the bit loading(bits or gain per bin) to change. Up to 32 bins may be used in the upstream direction and up to 256 bins in thedownstream direction. Only instantaneous (or raw) versions of these objects are available in this MIB. The ATU-RSNR and Attenuation status may not be current and depends on having an operating link to be reported because theSNMP agent proxies the ATU-R. Note that all per bin objects are optional.3.3 DMT Channel TablesThe DMT LCS MIB includes placeholders for the adslAtucDMTChanTable and adslAturDMTChanTabletables, which are not currently used.3.4 DMT Physical Performance TablesThe DMT LCS MIB includes placeholders for the adslAtucDMTPerfDataTable andadslAturDMTPerfDataTable tables, which are not currently used. 1 The autonomous data streaming mode is sometimes known as eoc clear channel mode. Autonomous datastreaming is a mandatory function defined in ITU G.992.1 and G.992.2. The transport of SNMP messages overthe clear eoc channel has been identified by G.997.1 as optional and is indicated during initialization bymessages defined in Recommendation G.994.1.
`
`

`
`DMT Line Code Specific MIBADSL Forum TR-02463.5 DMT Physical Interval TablesThe DMT LCS MIB includes placeholders for the adslAtucDMTIntervalTable and adslAturDMTIntervalTabletables, which are not currently used.3.6 DMT Channel Performance TablesThe DMT LCS MIB includes placeholders for the adslAtucDMTChanPerfDataTable andadslAturDMTChanPerfDataTable tables, which are not currently used.3.7 DMT Channel Interval TablesThe DMT LCS MIB includes placeholders for the adslAtucDMTChanIntervalTable andadslAturDMTChanIntervalTable tables, which are not currently used.3.8 Profile GroupWhen dynamic profiles are used, the mechanism prescribed in TR-006 should be used to manage profile elementsfor both the generic adslLineConfProfileTable and the LCS specific table.When a DMT ADSL line is initialising and training, the configuration is controlled by the ATU-C thus allowingoperators to define various line profiles. The DMT configuration profile table (adslLineDMTConfProfileTable)allows the following aspects of the line to be configured before initialisation is attempted. The ATU-R or linecondition may restrict the final configuration to be different from that requested in the target configuration. Thetarget configuration elements are:•Enable/disable each upstream DMT frequency bin using the adslAtucDMTConfFreqBins element and eachdownstream frequency bin using adslAturDMTConfFreqBins. The default and initial value is to enable allfrequency bins. The adslAturDMTConfFreqBins element is passed to the ATU-R, using a vendor specificmechanism, for use during subsequent initialisations. Note that user control of certain bins may be ignoredwhen transceiver operation may be compromised (eg. pilot tone may not be disabled, certain bins may not beused for operation as per G.992.2 (lite) and G.992.1 Annex B (ISDN under), etc).•Configure the eoc processor to support transaction based eoc only or support additional autonomous datastreaming operation. Although ITU Recommendations G.992.1 and G.992.2 require support for autonomousdata transfers, the use of SNMP protocol over this clear channel eoc is optional as per G.997.1. It is thisoptional support of SNMP that is enabled when autonomous data streaming operation is enabled using theadslLineDMTConfEOC element. The default value is to disable autonomous data streaming operation (andthereby SNMP transfers) in the profile.3.9 Alarm Configuration Profile TablesThe DMT LCS MIB includes placeholders for the adslLineDMTAlarmConfProfileTable which are not currentlyused.4. DMT Definitions for ADSL Line MIBThe following definitions are made for use in ADSL Forum document TR-006, which defines the ADSL Line MIB:
`
`

`
`DMT Line Code Specific MIBADSL Forum TR-0247•SNR values quoted in the ADSL Line MIB are single numbers, not separate values for each frequency bin.SNR values in the ADSL Line MIB should be calculated in the same manner as ITU G.992.1. InitialisationSNR values are exchanged in the C-MSGS1, C-MSGS-RA, R-MSGS2 and R-MSGS-RA and may be reporteddirectly in the ADSL Line MIB. The current SNR measurement at the ATU-R may be obtained using an eocread register exchange.•Line attenuation values quoted in the ADSL Line MIB are single numbers, not separate values for eachfrequency bin. Attenuation values in the ADSL Line MIB should be calculated in the same manner as ITUG.992.1. Line attenuation values are reported by the ATU-R during initialisation in R-MSGS2 and R-MSGS-RA and may be reported directly in the ADSL Line MIB. The current line attenuation measurement at theATU-R may be obtained using an eoc read register exchange.These definitions customise certain generic elements in the ADSL Line MIB for application to a DMT line.5. References1.ANSI T1.413-1995; Telecommunications - Network and Customer Installation Interfaces - Asymmetric DigitalSubscriber Line (ADSL) Metallic Interface.2.ANSI T1E1.4/98-007R1, Draft version of ADSL T1.413 Issue 2, May 1998.3.ADSL Forum TR-006; Network Management Technical Report, SNMP-Based ADSL Line MIB.4. ADSL Forum contributions 97-144 and 97-145 describing eoc autonomous data streaming proposals. 5. IETF, draft-ietf-adslmib-adsllinemib-04.txt, Definitions of Managed Objects for the ADSL Lines 6. ITU, Draft G.997.1, Physical Layer Management for Digital Subscriber Line (DSL) Transceivers 7. ITU, Draft G.992.1, Asymmetrical Digital Subscriber Line (ADSL) Transceivers 8. ITU, Draft G.992.2, Splitterless Asymmetrical Digital Subscriber Line (ADSL) Transceivers 9. ITU, Draft G.994.1, Handshake Procedures for Digital Subscriber Line (DSL) Transceivers 10. ADSL Forum contribution 99-079, Suggested Changes to DMT Line Code Specific MIB. 11. ADSL Forum contribution 99-135, Proposal for In-Service Line Analysis and Test MIB
`
`

`
`8
`
` INDEX
` "DMT physical layer actuals information entry"
` DESCRIPTION
` MAX-ACCESS not-accessible
`adslAtucDMTPhysEntry OBJECT-TYPE
`
`AdslAtucDMTPhysEntry
`
`STATUS current
`SYNTAX
`
`::= {adslAtucDMTPhysTable 1}
`
`{ifIndex }
`
` "DMT interface physical layer actuals information
` DESCRIPTION
` MAX-ACCESS not-accessible
`adslAtucDMTPhysTable OBJECT-TYPE
`-- ATU-C PHYSICAL TABLE
`
`STATUS current
`SYNTAX SEQUENCE OF AdslAtucDMTPhysEntry
`
`table for the central office."
`
`::= {adslDMTMibObjects 2}
`
`ATU’s support this capability."
`determined. Streaming support is only reported if both
`the capability of both ATUs has been
`initialization, unknown is reported until
`streaming mode or only transaction mode. After
`
`::= { adslLineDMTEntry 1 }
`
`STATUS current
`
` "Reports whether the eoc can support autonomous data
` DESCRIPTION
` MAX-ACCESS read-only
` }
` -- original transaction mode
` -- eoc supports autonomous data streaming mode and
` -- eoc only operates in original transaction mode
` -- eoc mode is unknown yet
`
`streaming (3)
`transaction (2),
`unknown (1),
`
`dslLineDMTEOC OBJECT-TYPE
`
`SYNTAX INTEGER {
`
`adslLineDMTEOC INTEGER
`
`
` SEQUENCE {
`AdslLineDMTEntry ::=
`
`} a
`
` "DMT interface physical layer actuals information
` DESCRIPTION
` MAX-ACCESS not-accessible
`adslLineDMTTable OBJECT-TYPE
`--DMT LINE TABLE
`adslDMTMibObjects OBJECT IDENTIFIER ::= { adslDMTMib 1 }
`
`STATUS current
`SYNTAX SEQUENCE OF AdslLineDMTEntry
`
`Atur -- (ATUR) modem at Remote end of line
`Atuc -- (ATUC) modem at near (Central) end of line
`
`::= {adslLCSMib 1}
` LCS -- Line Code Specific"
`
`Kanata, On, Canada K2K 2E6
`
` "Naming Conventions:
` DESCRIPTION
` "
` E-mail: cstorry@newbridge.com
` Fax: +1 613-599-3634
` Tel: +1 613-591-3600
` 600 March Rd.
` Newbridge Networks
` Chuck Storry
` E-mail: bathricg@agcs.com
` Fax: +1 602-582-7697
` Tel: +1 602-582-7679
` Phoenix, AZ 85027 USA
`2500 W Utopia Rd.
` AG Communication Systems
` Gregory Bathrick
` E-mail: ttz864@email.sps.mot.com
` Fax: +44 1355 261790
` Tel: +44 1355 565597
`
`Glasgow, United Kingdom.
`Colvilles Road, East Kilbride,
`Motorola Inc.
` Kevin Godfrey
` "
` CONTACT-INFO
` ORGANIZATION "ADSL Forum"
` LAST-UPDATED "9906221200Z"
`adslDMTMib MODULE-IDENTITY
`-- DMT LCS MIB OBJECTS
`
` INDEX
` "DMT physical layer line actuals information entry"
` DESCRIPTION
` MAX-ACCESS not-accessible
`adslLineDMTEntry OBJECT-TYPE
`
`AdslLineDMTEntry
`
`STATUS current
`SYNTAX
`
`::= {adslLineDMTTable 1}
`
`{ifIndex }
`
`::= {adslDMTMibObjects 1}
`
`table."
`
`adslLCSMib,adslLineConfProfileName FROM ADSL-LINE-MIB ;
`ifIndex FROM IF-MIB
`
` MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF
` MODULE-IDENTITY, OBJECT-TYPE FROM SNMPv2-SMI
` IMPORTS
`ADSL-DMT-LINE-MIBDEFINITIONS ::= BEGIN
`
`ASN-1 Format DMT Line Code Specific MIB.
`
`ADSL Forum TR-024
`
`DMT Line Code Specific MIB
`
`

`
`9
`
`state depending on the ATU-C state. When the inference
`reported by the SNMP agent at the ATU-C which infers the
` The current state can change dynamically. ATU-R state is
` "Reports current state of the ATU-R DMT transceiver.
` DESCRIPTION
` MAX-ACCESS read-only
` }
`
`STATUS current
`
`steadystate (6) -- normal operating mode
`exchange (5), -- exchanging final operating parameters
`analyzing (4), -- channel analysis in progress
`training (3), -- transceiver training in progress
`activating (2), -- activation in progress
`other (1), -- Unknown or other state
`
`SYNTAX INTEGER {
`adslAturDMTState OBJECT-TYPE
`
`adslAturDMTBinAtn OCTET STRING
`adslAturDMTBinSNR OCTET STRING,
`adslAturDMTBinBits OCTET STRING,
`adslAturDMTState INTEGER,
`
` }
`
` SEQUENCE {
`AdslAturDMTPhysEntry ::=
`
` INDEX
` "DMT physical layer actuals information entry"
` DESCRIPTION
` MAX-ACCESS not-accessible
`adslAturDMTPhysEntry OBJECT-TYPE
`
`AdslAturDMTPhysEntry
`
`STATUS current
`SYNTAX
`
`::= {adslAturDMTPhysTable 1}
`
`{ifIndex }
`
` "DMT interface physical layer actuals information
` DESCRIPTION
` MAX-ACCESS not-accessible
`adslAturDMTPhysTable OBJECT-TYPE
`-- ATU-R PHYSICAL TABLE
`
`STATUS current
`SYNTAX SEQUENCE OF AdslAturDMTPhysEntry
`
`table for the remote unit."
`
`::= {adslDMTMibObjects 3}
`
`steps)."
`to a 0 to 127.5 dB Attenuation (0.5 dB
`integer, ranging from 0 to 255, corresponding
`string. Each octet is coded as an unsigned
`for the bin indexed by this element of the
` "Each octet contains the attenuation per bin
` DESCRIPTION
` MAX-ACCESS read-only
`adslAtucDMTBinAtn OBJECT-TYPE
`
`STATUS current
`SYNTAX OCTET STRING (SIZE (32))
`
`::= { adslAtucDMTPhysEntry 4 }
`
`notresponding (12) -- DMT transceiver not responding
`steadystate (11), -- normal operating mode
`exchange (10), -- exchanging final operating parameters
`analyzing (9), -- channel analysis in progress
`training (8), -- transceiver training in progress
`activating (7), -- activation in progress
`tone (6), -- requesting ATU-R to be silent
`quiet (5), -- awaiting activation request from ATU-R
`idle (4), -- transceiver is initialized but idle
`configure (3), -- DMT transceiver being configured
`powerup (2), -- DMT transceiver not yet configured
`other (1), -- Unknown or other state
`
`SYNTAX INTEGER {
`adslAtucDMTState OBJECT-TYPE
`
`adslAtucDMTBinAtn OCTET STRING
`adslAtucDMTBinSNR OCTET STRING,
`adslAtucDMTBinBits OCTET STRING,
`adslAtucDMTState INTEGER,
`
` }
`
` SEQUENCE {
`AdslAtucDMTPhysEntry ::=
`
` The current state can change dynamically. The SNMP
` "Reports current state of the ATU-C DMT transceiver.
` DESCRIPTION
` MAX-ACCESS read-only
` }
`
`to a 0 to 63.5 dB SNR (0.5 dB steps)."
`integer, ranging from 0 to 127, corresponding
`string. Each octet is coded as an unsigned
`for the bin indexed by this element of the
`
`::= { adslAtucDMTPhysEntry 3 }
`
` "Each octet contains the SNR per bin
` DESCRIPTION
` MAX-ACCESS read-only
`adslAtucDMTBinSNR OBJECT-TYPE
`
`STATUS current
`SYNTAX OCTET STRING (SIZE (32))
`
`bits per bin."
` The range of expected values is from 0 to 15
`which contains the number of bits for bin 31.
`bits for bin 0 through to the 31st element
`string. The 0th element contains the number of
`for the bin indexed by this element of the
` "Each octet contains the number of bits per bin
` DESCRIPTION
` MAX-ACCESS read-only
`adslAtucDMTBinBits OBJECT-TYPE
`
`STATUS current
`SYNTAX OCTET STRING (SIZE (32))
`
`::= { adslAtucDMTPhysEntry 2 }
`
`state machine."
`agent reports the state after querying the ATU-C
`
`::= { adslAtucDMTPhysEntry 1 }
`
`STATUS current
`
`ADSL Forum TR-024
`
`DMT Line Code Specific MIB
`
`

`
`--adslLineDMTTable for the final settings.
`--options process. Check the adslAtucDMTPhysTable and
`--parameters may have changed due to the negotiation and rate
`--initialization. After initialization is complete, the
`-- Configuration profiles define the starting point for line
` }
`
`adslLineDMTConfEOC INTEGER
`adslAturDMTConfFreqBins OCTET STRING,
`adslAtucDMTConfFreqBins OCTET STRING,
`
` SEQUENCE {
`AdslDMTConfProfileEntry ::=
`
` INDEX
` "DMT interface config information entry"
` DESCRIPTION
` MAX-ACCESS not-accessible
`adslDMTConfProfileEntry OBJECT-TYPE
`
`AdslDMTConfProfileEntry
`
`STATUS current
`SYNTAX
`
`::= {adslLineDMTConfProfileTable 1}
`{adslLineConfProfileName }
`
`parameters for the physical layer before initialization."
` "This table contains the target DMT specific configuration
` DESCRIPTION
` MAX-ACCESS not-accessible
`adslLineDMTConfProfileTable OBJECT-TYPE
`-- CONFIGURATION FOR ATU-C/ATU-R DMT INTERFACES
`
`STATUS current
`SYNTAX SEQUENCE OF AdslDMTConfProfileEntry
`
`::= {adslDMTMibObjects 14}
`
`adslAturDMTChanIntervalTable OBJECT IDENTIFIER ::= {adslDMTMibObjects 13}
`adslAtucDMTChanIntervalTable OBJECT IDENTIFIER ::= {adslDMTMibObjects 12}
`-- CHANNEL INTERVAL TABLES
`
`adslAturDMTChanPerfDataTable OBJECT IDENTIFIER ::= {adslDMTMibObjects 11}
`
` 15 bits per bin "
` 255. The range of expected values is from 0 to
`
`which contains the number of bits for bin
`bits for bin 0 through to the 255th element
`string. The 0th element contains the number of
`for the bin indexed by this element of the
` "Each octet contains the number of bits per bin
` DESCRIPTION
` MAX-ACCESS read-only
`adslAturDMTBinBits OBJECT-TYPE
`
`STATUS current
`SYNTAX OCTET STRING (SIZE (256))
`
`::= { adslAturDMTPhysEntry 2 }
`
`cannot be made, unknown state is returned."
`
`::= { adslAturDMTPhysEntry 1 }
`
`ADSL Forum TR-024
`
`DMT Line Code Specific MIB
`
`adslAtucDMTChanPerfDataTable OBJECT IDENTIFIER ::= {adslDMTMibObjects 10}
`-- CHANNEL PERFORMANCE DATA TABLES
`
`adslAturDMTIntervalTable OBJECT IDENTIFIER ::= {adslDMTMibObjects 9}
`adslAtucDMTIntervalTable OBJECT IDENTIFIER ::= {adslDMTMibObjects 8}
`-- INTERVAL TABLES
`
`adslAturDMTPerfDataTable OBJECT IDENTIFIER ::= {adslDMTMibObjects 7}
`adslAtucDMTPerfDataTable OBJECT IDENTIFIER ::= {adslDMTMibObjects 6}
`-- PERFORMANCE DATA TABLES
`
`adslAturDMTChanTable OBJECT IDENTIFIER ::= {adslDMTMibObjects 5}
`adslAtucDMTChanTable OBJECT IDENTIFIER ::= {adslDMTMibObjects 4}
`-- CHANNEL TABLES
`
`steps)."
`to a 0 to 127.5 dB Attenuation (0.5 dB
`integer, ranging from 0 to 255, corresponding
`string. Each octet is coded as an unsigned
`for the bin indexed by this element of the
` "Each octet contains the attenuation per bin
` DESCRIPTION
` MAX-ACCESS read-only
`adslAturDMTBinAtn OBJECT-TYPE
`
`STATUS current
`SYNTAX OCTET STRING (SIZE (256))
`
`::= { adslAturDMTPhysEntry 4 }
`
`to a 0 to 63.5 dB SNR (0.5 dB steps)."
`integer, ranging from 0 to 127, corresponding
`string. Each octet is coded as an unsigned
`for the bin indexed by this element of the
`
`::= { adslAturDMTPhysEntry 3 }
`
` "Each octet contains the SNR per bin
` DESCRIPTION
` MAX-ACCESS read-only
`adslAturDMTBinSNR OBJECT-TYPE
`
`STATUS current
`SYNTAX OCTET STRING (SIZE (256))
`
`sub-carrier frequency bin and a 0 enables reception."
`bin). A bit set to 1 disables reception of the specified
`octet controlling sub-carrier zero (lowest frequency
`bit controls one bin with the first bit of the first
`frequency bins that the ATU-C receiver monitors. Each
` "A string of 32 bits to enable/disable the incoming DMT
` DESCRIPTION
` MAX-ACCESS read-create
`
`STATUS current
`SYNTAX OCTET STRING (SIZE(4))
`adslAtucDMTConfFreqBins OBJECT-TYPE
`
`{ ’00000000’H }
`
` DEFVAL
`
`10
`
`SYNTAX OCTET STRING (SIZE(32))
`
`adslAturDMTConfFreqBins OBJECT-TYPE
`
` MAX-ACCESS read-create
`
`::= { adslDMTConfProfileEntry 1 }
`
`

`
` OBJECTS {
`
` "A collection of objects providing management
` DESCRIPTION
` }
`
`STATUS current
`
`adslLineDMTConfEOC
`adslAturDMTConfFreqBins,
`adslAtucDMTConfFreqBins,
`adslAturDMTState,
`adslAtucDMTState,
`adslLineDMTEOC,
`
`adslDMTGroup OBJECT-GROUP
`
` OBJECTS {
`
` -- units of conformance
`
`::= { adslDMTCompliances 1 }
`
`information about an DMT ADSL Line."
`
`adslAturDMTBinAtn
`adslAturDMTBinSNR,
`adslAturDMTBinBits,
`adslAtucDMTBinAtn,
`adslAtucDMTBinSNR,
`adslAtucDMTBinBits,
`adslDMTBinGroup OBJECT-GROUP
`::= { adslDMTGroups 1 }
`
` “A collection of objects providing per bin
` DESCRIPTION
` }
`
`information about a DMT ADSL Line.”
`
`::= { adslDMTGroups 2 }
`
`STATUS current
`
`11
`
` "This group is optional. It is implemented when
` DESCRIPTION
`
`adslDMTBinGroup
`
`GROUP
`
`per bin status information is available."
`
` MANDATORY-GROUPS {adslDMTGroup }
` MODULE -- this module
`
` "The compliance statement for SNMP entities
` DESCRIPTION
`
`which have ADSL DMT interfaces."
`
`STATUS current
`adslLineMibCompliance MODULE-COMPLIANCE
`
`END
`
` -- compliance statements
`adslDMTCompliances OBJECT IDENTIFIER ::= { adslDMTConformance 2 }
`adslDMTGroups OBJECT IDENTIFIER ::= { adslDMTConformance 1 }
`adslDMTConformance OBJECT IDENTIFIER ::= { adslDMTMib 3 }
`--place holder
`adslDMTTraps OBJECT IDENTIFIER ::= { adslDMTMib 2 }
`15}
`adslLineDMTAlarmConfProfileTable OBJECT IDENTIFIER ::= {adslDMTMibObjects
`-- ALARM CONFIGURATION FOR BOTH ATU-C/ATU-R DMT INTERFACES
`
`reception."
`specified sub-carrier frequency bin and a 0 enables
`frequency bin). A bit set to 1 disables reception of the
`first octet controlling sub-carrier zero (lowest
`adslAturDMTConfFreqBins to the ATU-R is vendor specific.
`after the next activation. The mechanism to pass
`frequency bins that the ATU-R receiver should monitor
`
` Each bit controls one bin with the first bit of the
`
` "A string of 256 bits to enable/disable the incoming DMT
` DESCRIPTION
`
`STATUS current
`
`{
`
`’0000000000000000000000000000000000000000000000000000000000000000’H }
` DEFVAL
`
` DEFVAL
` ADSL line."
` "Defines the embedded operations channel mode for the DMT
` DESCRIPTION
` MAX-ACCESS read-create
` }
` -- addition to byte transaction mode
` -- eoc allows autonomous data streaming mode in
` -- eoc operates in byte transaction mode
`
`STATUS current
`
`adslLineDMTConfEOC OBJECT-TYPE
`
`SYNTAX INTEGER {
`
`streaming (2)
`byte (1),
`
`{ byte } -- default to byte transaction mode
`
`::= { adslDMTConfProfileEntry 3 }
`
`::= { adslDMTConfProfileEntry 2 }
`
`ADSL Forum TR-024
`
`DMT Line Code Specific MIB
`
`

`
`12Editors Note: this page will not form part of the final technical report.Contributory Material to this Technical ReportThe following ADSL Forum contributions have been made on this technical report and their commentsincorporated:1. 99-079, Suggested Changes to DMT Line Code Specific MIB. Chuck Storry, Newbridge, Washington meeting,March 1999.2. 99-113, Straw Ballot vote on WT-036 DMT LCS MIB. Chuck Storry, Newbridge, Vienna meeting, May 1999.WT-036 Revision HistoryRevisionDate IssuedEditorComments1March 22, 1999Chuck StorryInitial release of WT-036 incorporating comments from 99-0792June, 1999Chuck StorryVersion for Letter Ballot incorporating straw ballotcomments