draft-ietf-adslmib-adslext-10.txt   draft-ietf-adslmib-adslext-11.txt 
INTERNET-DRAFT ADSL Line Extension MIB Faye Ly INTERNET-DRAFT ADSL Line Extension MIB Faye Ly
Pedestal Networks Pedestal Networks
Gregory Bathrick Gregory Bathrick
Nokia Nokia
April 23, 2002 September 12, 2002
Definitions of Extension Managed Objects Definitions of Extension Managed Objects
for ADSL Lines for Asymmetric Digital Subscriber Lines
April 23, 2002 September 12, 2002
draft-ietf-adslmib-adslext-10.txt draft-ietf-adslmib-adslext-11.txt
1. Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that other Task Force (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet-Drafts. groups may also distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as ``work in progress.'' 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/1id-abstracts.html
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2002). All Rights Reserved. Copyright (C) The Internet Society (2002). All Rights Reserved.
2. Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes additional managed objects used for In particular, it describes additional managed objects used for
managing Asymmetric Digital Subscriber Line (ADSL) interfaces not managing Asymmetric Digital Subscriber Line (ADSL) interfaces not
covered by the ADSL Line MIB [RFC2662]. covered by the ADSL Line MIB [RFC2662].
3. The SNMP Network Management Framework 1. The SNMP Network Management Framework
The SNMP Management Framework presently consists of five major The SNMP Management Framework presently consists of five major
components: components:
o An overall architecture, described in RFC 2571 [RFC2571]. o An overall architecture, described in RFC 2571 [RFC2571].
o Mechanisms for describing and naming objects and events o Mechanisms for describing and naming objects and events
for the purpose of management. The first version of this for the purpose of management. The first version of this
Structure of Management Information (SMI) is called SMIv1 Structure of Management Information (SMI) is called SMIv1
and described in STD 16, RFC 1155 [RFC1155], STD 16, and described in STD 16, RFC 1155 [RFC1155], STD 16,
RFC 1212 [RFC1212] and RFC 1215 [RFC1215]. The second version, RFC 1212 [RFC1212] and RFC 1215 [RFC1215]. The second version,
skipping to change at page 3, line 5 skipping to change at page 3, line 5
This memo specifies a MIB module that is compliant to the SMIv2. A This memo specifies a MIB module that is compliant to the SMIv2. A
MIB conforming to the SMIv1 can be produced through the appropriate MIB conforming to the SMIv1 can be produced through the appropriate
translations. The resulting translated MIB must be semantically translations. The resulting translated MIB must be semantically
equivalent, except where objects or events are omitted because no equivalent, except where objects or events are omitted because no
translation is possible (use of Counter64). Some machine-readable translation is possible (use of Counter64). Some machine-readable
information in SMIv2 will be converted into textual descriptions in information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of machine SMIv1 during the translation process. However, this loss of machine
readable information is not considered to change the semantics of the readable information is not considered to change the semantics of the
MIB. MIB.
4. Introduction 2. Introduction
The purpose of this memo is to define a supplemental set of managed 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 [RFC2662]. objects that is not covered by ADSL Line MIB as defined in [RFC2662].
This memo addresses the additional objects defined in ITU G.997.1 This memo addresses the additional objects defined in ITU G.997.1
[ITU G.997.1]. [ITU G.997.1].
5. Relationship of ADSL Line Extension MIB with standard MIBs 3. Relationship of ADSL Line Extension MIB with standard MIBs
This section outlines the relationship of ADSL Line Extension MIB This section outlines the relationship of ADSL Line Extension MIB
with other MIBs described in RFCs and in their various degrees with other MIBs described in RFCs and in their various degrees
of standardization. In regards to these relationship, the ADSL Line of standardization. In regards to these relationship, the ADSL Line
Extension MIB follows conventions as used by the ADSL Line MIB with Extension MIB follows conventions as used by the ADSL Line MIB with
one exception. The value of the RFC2863 object, ifOperstatus, one exception. The value of the RFC2863 object, ifOperstatus,
SHALL be down(2) when the ADSL line interface is in power state L3 as SHALL be down(2) when the ADSL line interface is in power state L3 as
defined in ITU G.992.1 [ITU G.992.1], which means no power. Its value defined in ITU G.992.1 [ITU G.992.1], which means no power. Its value
shall be up(1) if the ADSL line interface is in power state L0 (power on) shall be up(1) if the ADSL line interface is in power state L0 (power on)
[ITU G.992.1] or L1 (reduced power). Power Status L2 [ITU G.992.1] is [ITU G.992.1] or L1 (reduced power). Power Status L2 [ITU G.992.1] is
not applicable. not applicable.
6. Conventions used in the MIB 4. Conventions used in the MIB
6.1 Structure 4.1 Structure
The MIB is organized to follow the same structure of the ADSL Line The MIB is organized to follow the same structure of the ADSL Line
MIB [RFC2662]. MIB [RFC2662].
6.2 Additional Managed Objects 4.2 Additional Managed Objects
Objects specific to the management of ADSL G.Lite as defined in Objects specific to the management of ADSL G.Lite as defined in
ITU G.992.2 [ITU G.992.2] are: ITU G.992.2 [ITU G.992.2] are:
- ADSL Transceiver Unit - Central Office End (ATU-C) - ADSL Transceiver Unit - Central Office End (ATU-C)
Transmission System and Line Mode Transmission System and Line Mode
- Power Management - Power Management
- Counters for Fast Retrains and Failed Fast Retrains - Counters for Fast Retrains and Failed Fast Retrains
- Counters for Severe Error Second-line and Unavailable Second - Counters for Severe Error Second-line and Unavailable Second
- Alternative profile configuration for the Dual line mode interface - Alternative profile configuration for the Dual line mode interface
Besides the management of G.Lite, another object has been added in Besides the management of G.Lite, another object has been added in
order to manage the ADSL line profile. The object is the line mode order to manage the ADSL line profile. The object is the line mode
configuration. configuration.
6.2.1 ATU-C ADSL Transmission System Parameters and Line Mode 4.2.1 ATU-C ADSL Transmission System Parameters and Line Mode
The adslLineConfigTable needs to be extended to cover control of the The adslLineConfigTable needs to be extended to cover control of the
ATU-C ADSL Transmission system. Three objects are defined to monitor ATU-C ADSL Transmission system. Three objects are defined to monitor
and configure the transmission mode as well as the actual line mode: and configure the transmission mode as well as the actual line mode:
- Capability - Capability
- Configuration - Configuration
- Actual Status - Actual Status
Transmission modes can further determine the line mode of the ADSL Transmission modes can further determine the line mode of the ADSL
skipping to change at page 4, line 46 skipping to change at page 4, line 46
G.992.1 TCM-ISDN symmetric Full G.992.1 TCM-ISDN symmetric Full
Table 1: Transmission Mode and Line Mode Table 1: Transmission Mode and Line Mode
In case more than one bit is configured for an ADSL interface and In case more than one bit is configured for an ADSL interface and
both Full and G.Lite modes are selected, the interface is said to both Full and G.Lite modes are selected, the interface is said to
be configured in the dual mode. Only one bit can be set in the Actual be configured in the dual mode. Only one bit can be set in the Actual
object that reflects the actual mode of transmission as well as the object that reflects the actual mode of transmission as well as the
line mode. line mode.
6.2.2 Power Management 4.2.2 Power Management
There are three possible power states for each managed ADSL interface There are three possible power states for each managed ADSL interface
operating in the G.Lite mode. L0 is power on, L1 is power on but operating in the G.Lite mode. L0 is power on, L1 is power on but
reduced and L3 is power off. Power state cannot be configured by an reduced and L3 is power off. Power state cannot be configured by an
operator but it can be viewed via the ifOperStatus object for the operator but it can be viewed via the ifOperStatus object for the
managed ADSL interface. The value of the object ifOperStatus is managed ADSL interface. The value of the object ifOperStatus is
set to down(2) if the ADSL interface is in power state L3 and is set set to down(2) if the ADSL interface is in power state L3 and is set
to up(1) if the ADSL line interface is in power state L0 or L1. to up(1) if the ADSL line interface is in power state L0 or L1.
An ADSL line power state, if the interface is operating in the An ADSL line power state, if the interface is operating in the
G.Lite mode, can also be monitored by the adslLineGlitePowerState G.Lite mode, can also be monitored by the adslLineGlitePowerState
object defined in the ADSL Line Extension table. The value of the object defined in the ADSL Line Extension table. The value of the
object enumerates the three power states attainable by the managed object enumerates the three power states attainable by the managed
interface. interface.
6.2.3 Fast Retrain Parameters 4.2.3 Fast Retrain Parameters
Section 7.4.15 [ITU G.997.1] specifies fast retrain parameters. Fast Section 7.4.15 [ITU G.997.1] specifies fast retrain parameters. Fast
retrain parameters include two counters: fast retrain count and failed retrain parameters include two counters: fast retrain count and failed
fast retrain count. These two counters have been added to all fast retrain count. These two counters have been added to all
performance tables. performance tables.
6.2.4 Counters for Severely Errored Second-line and Unavailable 4.2.4 Counters for Severely Errored Second-line and Unavailable
Seconds-line Seconds-line
ITU G.997.1 sections 6.2.1.1.7 and 6.2.1.1.9 specify two counters that ITU G.997.1 sections 6.2.1.1.7 and 6.2.1.1.9 specify two counters that
are not covered by the ADSL Line MIB [RFC2662]. These two counters are not covered by the ADSL Line MIB [RFC2662]. These two counters
(severely errored seconds-line and unavailable seconds-line) are added (severely errored seconds-line and unavailable seconds-line) are added
to all the performance tables. to all the performance tables.
Unavailable seconds counts cumulative number of seconds in which the Unavailable seconds counts cumulative number of seconds in which the
interface was unavailable during the measured period. This counter interface was unavailable during the measured period. This counter
does not include the seconds in which unavailability was caused solely does not include the seconds in which unavailability was caused solely
by fast retrains and failed fast retrains. Fast retrains and failed by fast retrains and failed fast retrains. Fast retrains and failed
fast retrains are considered to be part of the normal network operation fast retrains are considered to be part of the normal network operation
and thus are not counted as unavailable errors. and thus are not counted as unavailable errors.
6.2.5 Counters, Interval Buckets and Thresholds 4.2.5 Counters, Interval Buckets and Thresholds
For physical-level events, there are counters, current 15-minute and For physical-level events, there are counters, current 15-minute and
one (up to 96) 15-minute history bucket(s) of "interval-counters", as one (up to 96) 15-minute history bucket(s) of "interval-counters", as
well as current and previous 1-day interval-counters. Threshold well as current and previous 1-day interval-counters. Threshold
notification can be configured for each physical-layer current notification can be configured for each physical-layer current
15-minute bucket. 15-minute bucket.
There is no requirement for an agent to ensure fixed relationship There is no requirement for an agent to ensure fixed relationship
between the start of a fifteen minute and any wall clock; however between the start of a fifteen minute and any wall clock; however
some implementations may align the fifteen-minute intervals with some implementations may align the fifteen-minute intervals with
skipping to change at page 6, line 14 skipping to change at page 6, line 14
Counters are not reset when an ATU-C or ATU-R is reinitialized, only Counters are not reset when an ATU-C or ATU-R is reinitialized, only
when the agent is reset or reinitialized (or under specific request when the agent is reset or reinitialized (or under specific request
outside the scope of this MIB). outside the scope of this MIB).
The 15-minute event counters are of type PerfCurrentCount and The 15-minute event counters are of type PerfCurrentCount and
PerfIntervalCount. The 1-day event counters are of type PerfIntervalCount. The 1-day event counters are of type
AdslPerfCurrDayCount and AdslPerfPrevDayCount. Both 15-minute and 1- AdslPerfCurrDayCount and AdslPerfPrevDayCount. Both 15-minute and 1-
day time elapsed counters are of type AdslPerfTimeElapsed. day time elapsed counters are of type AdslPerfTimeElapsed.
6.2.6 Alternative profile configuration for the dual line mode 4.2.6 Alternative profile configuration for the dual line mode
interface interface
The object, adslLineConfProfileDualLite, is used only when the interface The object, adslLineConfProfileDualLite, is used only when the interface
(the ADSL line and, if applicable, channel) is configured as dual mode, (the ADSL line and, if applicable, channel) is configured as dual mode,
that is, the object adslLineTransAtucConfig is configured with one or that is, the object adslLineTransAtucConfig is configured with one or
more full-rate modes and one or more G.Lite modes. more full-rate modes and one or more G.Lite modes.
The object adslLineConfProfile defined in ADSL-MIB [RFC2662] is used as The object adslLineConfProfile defined in ADSL-MIB [RFC2662] is used as
the primary full-rate profile. The newly added object in this MIB the primary full-rate profile. The newly added object in this MIB
module, adslLineConfProfileDualLite, is used to describe and configure module, adslLineConfProfileDualLite, is used to describe and configure
skipping to change at page 6, line 42 skipping to change at page 6, line 42
When 'static' profiles are implemented, however, similar to the case When 'static' profiles are implemented, however, similar to the case
of the object, adslLineConfProfileName [RFC2662], this object's value of the object, adslLineConfProfileName [RFC2662], this object's value
will need to algorithmically represent the line. In this case, the will need to algorithmically represent the line. In this case, the
value of the line's ifIndex plus a value indicating the line mode type value of the line's ifIndex plus a value indicating the line mode type
(e.g., G.Lite, Full-rate) will be used. Therefore, the profile's name (e.g., G.Lite, Full-rate) will be used. Therefore, the profile's name
is a string of the concatenation of ifIndex and one of the follow is a string of the concatenation of ifIndex and one of the follow
values: Full or Lite. This string will be fixed-length (i.e., 14) with values: Full or Lite. This string will be fixed-length (i.e., 14) with
leading zero(s). For example, the profile name for ifIndex that leading zero(s). For example, the profile name for ifIndex that
equals '15' and is a full rate line, it will be '0000000015Full'. equals '15' and is a full rate line, it will be '0000000015Full'.
7. Conformance and Compliance 5. Conformance and Compliance
See the conformance and compliance statements within the information See the conformance and compliance statements within the information
module. module.
8. Definitions 6. Definitions
ADSL-LINE-EXT-MIB DEFINITIONS ::= BEGIN ADSL-LINE-EXT-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
Counter32, Counter32,
Integer32, Integer32,
NOTIFICATION-TYPE, NOTIFICATION-TYPE,
MODULE-IDENTITY, MODULE-IDENTITY,
OBJECT-TYPE FROM SNMPv2-SMI OBJECT-TYPE FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP, MODULE-COMPLIANCE, OBJECT-GROUP,
NOTIFICATION-GROUP FROM SNMPv2-CONF NOTIFICATION-GROUP FROM SNMPv2-CONF
skipping to change at page 30, line 51 skipping to change at page 30, line 51
adslAturSesLThreshTrap, adslAturSesLThreshTrap,
adslAturUasLThreshTrap adslAturUasLThreshTrap
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of ADSL extension notifications." "The collection of ADSL extension notifications."
::= { adslExtGroups 6 } ::= { adslExtGroups 6 }
END END
9. Acknowledgments 7. Acknowledgments
This document is a product of the ADSL MIB Working Group. This document is a product of the ADSL MIB Working Group.
10. Normative References 8. Normative References
[ANSI T1.413] American National Standards Institute, ANSI T1.413, [ANSI T1.413] American National Standards Institute, ANSI T1.413,
Issue 2, "Standards Project for Interfaces Relating Issue 2, "Standards Project for Interfaces Relating
to Carrier to Customer Connection of ADSL Equipment", to Carrier to Customer Connection of ADSL Equipment",
1998. 1998.
[ETSI DTS/TM06006] European Telecommunications Standards Institute [ETSI DTS/TM06006] European Telecommunications Standards Institute
"ADSL European Specific Requirements", November "ADSL European Specific Requirements", November
2000. 2000.
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/