draft-ietf-adslmib-adslext-04.txt   draft-ietf-adslmib-adslext-05.txt 
INTERNET-DRAFT ADSL Line Extention MIB Faye Ly INTERNET-DRAFT ADSL Line Extension MIB Faye Ly
Copper Mountain Networks Copper Mountain Networks
Gregory Bathrick Gregory Bathrick
AG Communication Systems Nokia
March 10, 2000 June 5, 2000
Definitions of Extention Managed Objects Definitions of Extension Managed Objects
for ADSL Lines for ADSL Lines
March 10, 2000 June 5, 2000
draft-ietf-adslmib-adslext-04.txt draft-ietf-adslmib-adslext-05.txt
1. Status of this Memo 1. 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.
skipping to change at page 2, line 9 skipping to change at page 2, line 9
This document defines a standard SNMP MIB for additional functions This document defines a standard SNMP MIB for additional functions
not covered by the ADSL Line MIB [1]. not covered by the ADSL Line MIB [1].
3. The SNMP Network Management Framework 3. 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 [11]. o An overall architecture, described in RFC 2571 [11].
o Mechanisms for describing and naming objects and events for o Mechanisms for describing and naming objects and events for the
the purpose of management. The first version of this purpose of management. The first version of this Structure of
Structure of Management Information (SMI) is called SMIv1 and Management Information (SMI) is called SMIv1 and described in
described in RFC 1155 [14], RFC 1212 [15] and RFC 1215 [16]. STD
The second version, called SMIv2, is described in RFC 2579 16, RFC 1155 [14], STD 16, RFC 1212 [15] and RFC 1215 [16]. The
[1], RFC 1903 [2] and RFC 1904 [17]. second version, called SMIv2, is described in STD 58, RFC 2578
[1], STD 58, RFC 2579 [2] and STD 58, RFC 2580 [17].
o Message protocols for transferring management information. o Message protocols for transferring management information.
The first version of the SNMP message protocol is called The first version of the SNMP message protocol is called
SNMPv1 and described in RFC 1157 [7]. A second version of SNMPv1 and described in RFC 1157 [7]. A second version of
the SNMP message protocol, which is not an Internet standards the SNMP message protocol, which is not an Internet standards
track protocol, is called SNMPv2c and described in RFC 1901 track protocol, is called SNMPv2c and described in RFC 1901
[18] and RFC 1906 [19]. The third version of the message [18] and RFC 1906 [19]. The third version of the message
protocol is called SNMPv3 and described in RFC 1906 [19], RFC protocol is called SNMPv3 and described in RFC 1906 [19], RFC
2272 [20] and RFC 2274 [21]. 2272 [20] and RFC 2274 [21].
skipping to change at page 2, line 50 skipping to change at page 3, line 4
A MIB conforming to the SMIv1 can be produced through the appropriate A 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 (e.g., use of Counter64). Some machine translation is possible (e.g., use of Counter64). Some machine
readable information in SMIv2 will be converted into textual readable information in SMIv2 will be converted into textual
descriptions in SMIv1 during the translation process. However, this descriptions in SMIv1 during the translation process. However, this
loss of machine readable information is not considered to change the loss of machine readable information is not considered to change the
semantics of the MIB. semantics of the MIB.
4. Change Log 4. Change Log
This section tracks changes made to the revisions of the Internet This section tracks changes made to the revisions of the Internet
Drafts of this document. It will be deleted when the document is Drafts of this document. It will be deleted when the document is
published as an RFC. published as an RFC.
The following changes were made for the version of the document dated The following changes were made for the version of the document dated
May 10, 2000.
- Fixed the syntax AUGMENT for all tables.
- Corrected typos and added section 10, 11 and 12.
The following changes were made for the version of the document dated
May 10, 2000.
- Renamed adslLineTransAtucCapActual to adslLineTransAtucActual
The following changes were made for the version of the document dated
March 10, 2000. March 10, 2000.
- Added a new object in the adslLineExtTable describing the - Added a new object in the adslLineExtTable describing the
G.lite power state. G.lite power state.
The following changes were made for the version of the document dated The following changes were made for the version of the document dated
October 20, 1999. October 20, 1999.
- Changed adslLineExtTable to include config ATU-C, ATU-C and - Changed adslLineExtTable to include config ATU-C, ATU-C and
ATU-R actual transmission capabilities. ATU-R actual transmission capabilities.
- renamed adslProfileLineMode to adslProfileLineType to match - renamed adslProfileLineMode to adslProfileLineType to match
skipping to change at page 3, line 33 skipping to change at page 3, line 43
5. Introduction 5. Introduction
The purpose of this memo is to define a supplemental set of 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 managed objects that is not covered by ADSL Line MIB as defined in
[10]. This memo addresses the additional objects defined in ITU [10]. This memo addresses the additional objects defined in ITU
G.997.1 [8]. These additional objects specifically address the G.997.1 [8]. These additional objects specifically address the
management capabilities of ADSL "Lite" as defined by ITU-T G.992.2 management capabilities of ADSL "Lite" as defined by ITU-T G.992.2
[9]. [9].
6. Relationship of the ADSL LINE EXTENTION MIB with standard MIBs 6. Relationship of the ADSL LINE EXTENSION MIB with standard MIBs
This section outlines the relationship of ADSL Line Extention MIB This section outlines the relationship of ADSL Line Extension MIB
with other MIBs described in RFCs and in their various degrees of with other MIBs described in RFCs and in their various degrees of
"standardization". ADSL Line Extention MIB obeys the same "standardization". ADSL Line Extension MIB obeys the same
relationship between ADSL Line MIB to other standard MIBs with one relationship between ADSL Line MIB to other standard MIBs with one
exception for the ifOperStatus as defined in RFC 1213 [3]. exception for the ifOperStatus as defined in RFC 1213 [3].
6.1 ifOperStatus 6.1 ifOperStatus
ifOperStatus is set to down(2) when the ADSL line interface is in ifOperStatus is set to down(2) when the ADSL line interface is in
power state L2 which means no power. ifOperStatus is set to up(1) if power state L2, which means no power. ifOperStatus is set to up(1)
the ADSL line interface is in power state L0 (power on) or L1 if the ADSL line interface is in power state L0 (power on) or L1
(reduced power). (reduced power).
7. Conventions used in the MIB 7. Conventions used in the MIB
7.1 Structure 7.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 [1]. MIB [1].
7.2 Additional Managed Objects 7.2 Additional Managed Objects
A few objects are added to cover the ADSL "Lite" management and they A few objects are added to cover the ADSL "Lite" management and they
are: are:
- ATU-C Transmission System and Line Mode - ATU-C Transmission System and Line Mode
- Power Management - Power Management
skipping to change at page 4, line 15 skipping to change at page 4, line 24
MIB [1]. MIB [1].
7.2 Additional Managed Objects 7.2 Additional Managed Objects
A few objects are added to cover the ADSL "Lite" management and they A few objects are added to cover the ADSL "Lite" management and they
are: are:
- ATU-C Transmission System and Line Mode - ATU-C 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 Severed Error Second-line and Unavailable Second - Counters for Severe Error Second-line and Unavailable Second
- Alternative profile configuration for the Dual line mode - Alternative profile configuration for the Dual line mode
interface interface
Besides the management of ADSL "Lite", another object needs to be Besides the management of ADSL "Lite", another object has been
added to the ADSL Line MIB [10] in order to manage the ADSL line added to the ADSL Line MIB [10] in order to manage the ADSL line
profile. The object is the line mode configuration. profile. The object is the line mode configuration.
The MIB definitions are attached. The MIB will be branched from The MIB definitions are attached. The MIB will be branched from
the ADSL Line MIB [10]. the ADSL Line MIB [10].
7.2.1 ATU-C ADSL Transmission System Parameters and Line Mode 7.2.1 ATU-C ADSL Transmission System Parameters and Line Mode
The adslLineConfigTable needs to be extended to cover the ATU-C The adslLineConfigTable needs to be extended to cover control of
ADSL Transmission system enabling. Three objects are defined to the ATU-C ADSL Transmission system. Three objects are defined to
monitor and configure the transmission mode as well as the actual monitor and configure the transmission mode as well as the actual
line mode: line mode:
- Capability - Capability
- Configuration - Configuration
- Actual Status - Actual Status
Transmission modes can further determine the line mode of the Transmission modes can further determine the line mode of the
ADSL interface. For example, if g9921PotsNonOverlapped(2) is the ADSL interface. For example, if g9921PotsNonOverlapped(2) is the
actual value of the ADSL interface, the interface is operating in actual value of the ADSL interface, the interface is operating in
skipping to change at page 5, line 31 skipping to change at page 5, line 41
7.2.2 Power Management 7.2.2 Power Management
There are three power states for each managed ADSL interface There are three 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 L2 is power off. Power state cannot be configured by an reduced and L2 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 set managed ADSL interface. The value of the object ifOperStatus is set
to down(2) if the ADSL interface is in power state L2 and is set to to down(2) if the ADSL interface is in power state L2 and is set to
up(1) if the ADSL line interface is in power state L0 or L1. up(1) if the ADSL line interface is in power state L0 or L1.
An ADSL line power state, if is operating in the G.lite mode, An ADSL line power state, if the interface is operating in the
can also be monitored by the adslLineGlitePowerState object defined G.lite mode, can also be monitored by the adslLineGlitePowerState
in the ADSL Line Extention table. The value of the object enumerates object defined in the ADSL Line Extension table. The value of the
the three power states the managed interface can be in. object enumerates the three power states attainable by the managed
interface.
7.2.3 Fast Retrain Parameters 7.2.3 Fast Retrain Parameters
Section 7.4.15 of ITU G.997.1 specifies 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 Fast retrain parameters include two counters: fast retrain count and
failed fast retrain count. These two counters need to be added to failed fast retrain count. These two counters have been added to all
all performance tables. performance tables.
7.2.4 Counters for Severed Error Second-line and Unavailable Second 7.2.4 Counters for Severe Error Second-line and Unavailable Second
Section 7.2.1.1.7 and section 7.2.1.1.9 specify two counters 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 that are not covered by the ADSL Line MIB [10]. These two counters
(severed error second-line and unavailable second) are added to all (severe error seconds-line and unavailable seconds) are added to all
the performance tables. the performance tables.
Unavailable second counts number of seconds when there was Unavailable seconds counts cumulative number of seconds in which
Unavailable Errored seconds during the measured period. This counter the interface was unavailable during the measured period. This
does not include the seconds incurred by Fast Retrain and Failed Fast counter does not include the seconds in which unavailability was
Retrain. Fast Retrain and Failed Fast Retrain are considered to be caused solely by fast retrains and failed fast retrins. Fast
part of normal network operation and thus are not counted as retrains and failed fast retrains are considered to be part of the
unavailable errors. normal network operation and thus are not counted as unavailable
errors.
7.2.5 Alternative profile configuration for the Dual line mode 7.2.5 Alternative profile configuration for the Dual line mode
interface interface
This object is used only when the interface (for the ADSL line This object is used only when the interface (for the ADSL line
or channel) is configured as dual mode, that is, the object or channel) is configured as dual mode, that is, the object
adslLineTransAtucModeConfig is configued with one or more Full-Rate adslLineTransAtucConfig is configued with one or more full-rate modes
modes and one or more Lite modes. and one or more Lite modes.
The object adslLineConfProfile defined in ADSL-MIB [10] is used The object adslLineConfProfile defined in ADSL-MIB [10] is used
as the primary Rull-Rate profile. The newly added object in this MIB as the primary full-rate profile. The newly added object in this MIB
module, adslLineConfProfileDualLite is used to describe or configure module, adslLineConfProfileDualLite is used to describe or configure
the Lite profile. Note that if one or more Full-Rate modes are the Lite profile. Note that if one or more full-rate modes are
configured, only one Full-Rate profile is needed. This object is configured, or only lite modes are configured, only the original
only needed when both Full-Rate and Lite profiles are needed. full-rate profile is needed. The dual-mode profile object is only
needed when both full-rate and lite profiles are needed.
If the static profile is used, the profile name is the ifIndex If the static profile is used, the profile name is the ifIndex
ASCII string plus the differentiator string appended to the end of ASCII string plus the differentiator string appended to the end of
the static profile name. For example, for interface 100, the object the static profile name. For example, for interface 100, the object
adslLineConfProfile is set by the agent to be "100Full" and the adslLineConfProfile is set by the agent to be "100Full" and the
object adslLineConfProfileDualLite is set to be "100Lite". object adslLineConfProfileDualLite is set to be "100Lite".
8. Conformance and Compliance 8. Conformance and Compliance
See the conformance and compliance statements within the information See the conformance and compliance statements within the information
skipping to change at page 7, line 9 skipping to change at page 7, line 20
NOTIFICATION-GROUP FROM SNMPv2-CONF NOTIFICATION-GROUP FROM SNMPv2-CONF
TEXTUAL-CONVENTION FROM SNMPv2-TC TEXTUAL-CONVENTION FROM SNMPv2-TC
PerfCurrentCount, PerfCurrentCount,
PerfIntervalCount FROM PerfHist-TC-MIB PerfIntervalCount FROM PerfHist-TC-MIB
AdslPerfCurrDayCount, AdslPerfCurrDayCount,
AdslPerfPrevDayCount, AdslPerfPrevDayCount,
AdslPerfTimeElapsed, AdslPerfTimeElapsed,
AdslLineCodingType FROM ADSL-TC-MIB AdslLineCodingType FROM ADSL-TC-MIB
ifIndex FROM IF-MIB ifIndex FROM IF-MIB
SnmpAdminString FROM SNMP-FRAMEWORK-MIB SnmpAdminString FROM SNMP-FRAMEWORK-MIB
adslLineEntry, adslLineConfProfileName,
adslAtucPerfDataEntry,
adslLineConfProfileEntry,
adslAtucIntervalNumber, adslAtucIntervalNumber,
adslAturIntervalNumber, adslAturIntervalNumber,
adslLineAlarmConfProfileEntry, adslLineAlarmConfProfileName,
adslAturPerfDataEntry,
adslMIB FROM ADSL-LINE-MIB adslMIB FROM ADSL-LINE-MIB
; ;
adslExtMIB MODULE-IDENTITY adslExtMIB MODULE-IDENTITY
LAST-UPDATED "9905141200Z" LAST-UPDATED "9905141200Z"
ORGANIZATION "IETF ADSL MIB Working Group" ORGANIZATION "IETF ADSL MIB Working Group"
CONTACT-INFO CONTACT-INFO
" "
Faye Ly Faye Ly
Copper Mountain Networks Copper Mountain Networks
Norcal Office Norcal Office
2470 Embarcadero Way 2470 Embarcadero Way
Palo Alto, CA 94303 Palo Alto, CA 94303
Tel: +1 650-687-3323 Tel: +1 650-687-3323
Fax: +1 650-687-3372
E-Mail: faye@coppermountain.com E-Mail: faye@coppermountain.com
Gregory Bathrick Gregory Bathrick
AG Communication Systems NOKIA High Speed Access Nodes
A Subsidiary of Lucent Technologies 1310 Redwood Way,
2500 W Utopia Rd. Petaluma, CA 94954, USA
Phoenix, AZ 85027 USA Tel: +1 707-793-7030
Tel: +1 602-582-7679 Fax: +1 707-792-0850
Fax: +1 602-582-7697 E-Mail: greg.bathrick@nokia.com"
E-mail: bathricg@agcs.com"
DESCRIPTION DESCRIPTION
"This MIB Module is a supplement to the ADSL-LINE-MIB [1]." "This MIB Module is a supplement to the ADSL-LINE-MIB [1]."
::= { adslMIB 3 } ::= { adslMIB 3 }
adslExtMibObjects OBJECT IDENTIFIER ::= { adslExtMIB 1 } adslExtMibObjects OBJECT IDENTIFIER ::= { adslExtMIB 1 }
AdslTransmissionModeType ::= TEXTUAL-CONVENTION AdslTransmissionModeType ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A set of ADSL line transmission modes, with one bit "A set of ADSL line transmission modes, with one bit
per mode. The notes (F) and (L) denote Full-Rate per mode. The notes (F) and (L) denote Full-Rate
and Lite respectively: and Lite respectively:
Bit 01 : Regional Std. (ANSI T1.413) (F) Bit 00 : Regional Std. (ANSI T1.413) (F)
Bit 02 : Regional Std. (ETSI DTS/TM06006) (F) Bit 01 : Regional Std. (ETSI DTS/TM06006) (F)
Bit 03 : G.992.1 POTS non-overlapped (F) Bit 02 : G.992.1 POTS non-overlapped (F)
Bit 04 : G.992.1 POTS overlapped (F) Bit 03 : G.992.1 POTS overlapped (F)
Bit 05 : G.992.1 ISDN non-overlapped (F) Bit 04 : G.992.1 ISDN non-overlapped (F)
Bit 06 : G.992.1 ISDN overlapped (F) Bit 05 : G.992.1 ISDN overlapped (F)
Bit 07 : G.992.1 TCM-ISDN non-overlapped (F) Bit 06 : G.992.1 TCM-ISDN non-overlapped (F)
Bit 08 : G.992.1 TCM-ISDN overlapped (F) Bit 07 : G.992.1 TCM-ISDN overlapped (F)
Bit 09 : G.992.2 POTS non-overlapped (L) Bit 08 : G.992.2 POTS non-overlapped (L)
Bit 10 : G.992.2 POTS overlapped (L) Bit 09 : G.992.2 POTS overlapped (L)
Bit 11 : G.992.2 with TCM-ISDN non-overlapped (L) Bit 10 : G.992.2 with TCM-ISDN non-overlapped (L)
Bit 12 : G.992.2 with TCM-ISDN overlapped (L) Bit 11 : G.992.2 with TCM-ISDN overlapped (L)
" "
SYNTAX BITS { SYNTAX BITS {
ansit1413(0), ansit1413(0),
etsi(1), etsi(1),
a9921potsNonoverlapped(2), q9921PotsNonOverlapped(2),
a9921potsoverlapped(3), q9921PotsOverlapped(3),
a9921isdnnonoverlapped(4), q9921IsdnNonOverlapped(4),
a9921isdnoverlapped(5), q9921isdnOverlapped(5),
a9921tcmIsdnNonoverlapped(6), q9921tcmIsdnNonOverlapped(6),
a9921tcmIsdnOverlapped(7), q9921tcmIsdnOverlapped(7),
a9922potsnonOverlapeed(8), q9922potsNonOverlapeed(8),
a9922potsOverlapped(9), q9922potsOverlapped(9),
a9922tcmIsdnNonOverlapped(10), q9922tcmIsdnNonOverlapped(10),
a9922tcmIsdnOverlapped(11) q9922tcmIsdnOverlapped(11)
} }
adslLineExtTable OBJECT-TYPE adslLineExtTable OBJECT-TYPE
SYNTAX SEQUENCE OF AdslLineExtEntry SYNTAX SEQUENCE OF AdslLineExtEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains ADSL line configuration and "This table contains ADSL line configuration and
monitoring monitoring
information not defined in the adslLineTable from information not defined in the adslLineTable from
skipping to change at page 9, line 17 skipping to change at page 9, line 25
"An entry extends the adslLineEntry defined in [1]. "An entry extends the adslLineEntry defined in [1].
Each Each
entry corresponds to an ADSL line." entry corresponds to an ADSL line."
INDEX { ifIndex } INDEX { ifIndex }
::= { adslLineExtTable 1 } ::= { adslLineExtTable 1 }
AdslLineExtEntry ::= AdslLineExtEntry ::=
SEQUENCE { SEQUENCE {
adslLineTransAtucCap AdslTransmissionModeType, adslLineTransAtucCap AdslTransmissionModeType,
adslLineTransAtucConfig AdslTransmissionModeType, adslLineTransAtucConfig AdslTransmissionModeType,
adslLineTransAtucCapActual AdslTransmissionModeType, adslLineTransAtucActual AdslTransmissionModeType,
adslLineGlitePowerState INTEGER, adslLineGlitePowerState INTEGER,
adslLineConfProfileDualLite SnmpAdminString adslLineConfProfileDualLite SnmpAdminString
} }
adslLineTransAtucCap OBJECT-TYPE adslLineTransAtucCap OBJECT-TYPE
SYNTAX AdslTransmissionModeType SYNTAX AdslTransmissionModeType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The transmission modes that the ATU-C is capable "The transmission modes that the ATU-C is capable
skipping to change at page 9, line 43 skipping to change at page 10, line 4
adslLineTransAtucConfig OBJECT-TYPE adslLineTransAtucConfig OBJECT-TYPE
SYNTAX AdslTransmissionModeType SYNTAX AdslTransmissionModeType
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The transmission modes that the ATU-C must enable "The transmission modes that the ATU-C must enable
for the line. The ATU-C's enable modes must be for the line. The ATU-C's enable modes must be
a subset of its capable modes." a subset of its capable modes."
REFERENCE "Section 7.3.2 ITU G.997.1 [8]" REFERENCE "Section 7.3.2 ITU G.997.1 [8]"
::= { adslLineExtEntry 2 } ::= { adslLineExtEntry 2 }
adslLineTransAtucActual OBJECT-TYPE
adslLineTransAtucCapActual OBJECT-TYPE
SYNTAX AdslTransmissionModeType SYNTAX AdslTransmissionModeType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The transmission mode of the ATU-C. This object "The transmission mode of the ATU-C. This object
returns 0 (i.e BITS with no mode bit set) if there returns 0 (i.e BITS with no mode bit set) if there
is no mode currently known. The initialization is no mode currently known. The initialization
with the ATU-R will determine the mode used with the ATU-R will determine the mode used
and the result must be a one-mode subset of the and the result must be a one-mode subset of the
'Enable' modes. After an initialization has 'Enable' modes. After an initialization has
skipping to change at page 10, line 32 skipping to change at page 10, line 40
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of this object specifies the power state "The value of this object specifies the power state
this interface is in. If the object this interface is in. If the object
adslLineModeActual adslLineModeActual
is set to glite, the value of this object can be is set to glite, the value of this object can be
either either
one of the power state from L0 to L2. If the one of the power state from L0 to L2. If the
object object
adslLineTransAtucCapActual is set to other than adslLineTransAtucActual is set to other than
G.lite, G.lite,
the value of this object is always set to none(1)." the value of this object is always set to none(1)."
::= { adslLineExtEntry 4 } ::= { adslLineExtEntry 4 }
adslLineConfProfileDualLite OBJECT-TYPE adslLineConfProfileDualLite OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of this object identifies the row "The value of this object identifies the row
in the ADSL Line Configuration Profile Table, in the ADSL Line Configuration Profile Table,
(adslLineConfProfileTable), which applies for this (adslLineConfProfileTable), which applies for this
ADSL line, and channels if applicable, when the mode ADSL line, and channels if applicable, when the mode
after initialization is any G.992.2 (G.lite) mode after initialization is any G.992.2 (G.lite) mode
AND adslLineTransAtucModeConfig has enabled dual- AND adslLineTransAtucConfig has enabled dual-mode.
mode. Dual-mode in this case means one or more Dual-mode in this case means one or more Full-Rate
Full-Rate modes AND one or more Lite modes enabled. modes AND one or more Lite modes enabled.
If dual-mode has not been enabled by this MIB or if If dual-mode has not been enabled by this MIB or if
the ATU-C does not support this extension MIB, then the ATU-C does not support this extension MIB, then
the previously existing adslLineConfProfile is used the previously existing adslLineConfProfile is used
even if the ATU-C mode is one of the G.992.2 modes." even if the ATU-C mode is one of the G.992.2 modes."
::= { adslLineExtEntry 5 } ::= { adslLineExtEntry 5 }
adslAtucPerfDataExtTable OBJECT-TYPE adslAtucPerfDataExtTable OBJECT-TYPE
SYNTAX SEQUENCE OF AdslAtucPerfDataExtEntry SYNTAX SEQUENCE OF AdslAtucPerfDataExtEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
skipping to change at page 14, line 24 skipping to change at page 14, line 32
REFERENCE "ITU G.997.1 Section 7.4.15.2 [8]" REFERENCE "ITU G.997.1 Section 7.4.15.2 [8]"
::= { adslAtucPerfDataExtEntry 10 } ::= { adslAtucPerfDataExtEntry 10 }
adslAtucPerfCurr1DaySesL OBJECT-TYPE adslAtucPerfCurr1DaySesL OBJECT-TYPE
SYNTAX AdslPerfCurrDayCount SYNTAX AdslPerfCurrDayCount
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of the number of seconds when there was "Count of the number of seconds when there was
Severed Severe
Errored Seconds during the current day as measured Errored Seconds during the current day as measured
by by
adslAtucPerfCurr1DayTimeElapsed." adslAtucPerfCurr1DayTimeElapsed."
REFERENCE "ITU G.997.1 Section 7.2.1.1.7 [8]" REFERENCE "ITU G.997.1 Section 7.2.1.1.7 [8]"
::= { adslAtucPerfDataExtEntry 11 } ::= { adslAtucPerfDataExtEntry 11 }
adslAtucPerfCurr1DayUasL OBJECT-TYPE adslAtucPerfCurr1DayUasL OBJECT-TYPE
SYNTAX AdslPerfCurrDayCount SYNTAX AdslPerfCurrDayCount
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 18, line 33 skipping to change at page 18, line 41
REFERENCE "ITU G.997.1 Section 7.2.1.2.9 [8]" REFERENCE "ITU G.997.1 Section 7.2.1.2.9 [8]"
::= { adslAturPerfDataExtEntry 2 } ::= { adslAturPerfDataExtEntry 2 }
adslAturPerfCurr15MinSesL OBJECT-TYPE adslAturPerfCurr15MinSesL OBJECT-TYPE
SYNTAX PerfCurrentCount SYNTAX PerfCurrentCount
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of seconds in the current 15 minute interval "Count of seconds in the current 15 minute interval
when there was Severed Errored Seconds-Line." when there was Severe Errored Seconds-Line."
REFERENCE "ITU G.997.1 Section 7.2.1.2.7 [8]" REFERENCE "ITU G.997.1 Section 7.2.1.2.7 [8]"
::= { adslAturPerfDataExtEntry 3 } ::= { adslAturPerfDataExtEntry 3 }
adslAturPerfCurr15MinUasL OBJECT-TYPE adslAturPerfCurr15MinUasL OBJECT-TYPE
SYNTAX PerfCurrentCount SYNTAX PerfCurrentCount
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of seconds in the current 15 minute interval "Count of seconds in the current 15 minute interval
skipping to change at page 19, line 8 skipping to change at page 19, line 16
REFERENCE "ITU G.997.1 Section 7.2.1.2.9 [8]" REFERENCE "ITU G.997.1 Section 7.2.1.2.9 [8]"
::= { adslAturPerfDataExtEntry 4 } ::= { adslAturPerfDataExtEntry 4 }
adslAturPerfCurr1DaySesL OBJECT-TYPE adslAturPerfCurr1DaySesL OBJECT-TYPE
SYNTAX AdslPerfCurrDayCount SYNTAX AdslPerfCurrDayCount
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of the number of seconds when there was "Count of the number of seconds when there was
Severed Severe
Errored Seconds during the current day as measured Errored Seconds during the current day as measured
by by
adslAturPerfCurr1DayTimeElapsed." adslAturPerfCurr1DayTimeElapsed."
REFERENCE "ITU G.997.1 Section 7.2.1.2.7 [8]" REFERENCE "ITU G.997.1 Section 7.2.1.2.7 [8]"
::= { adslAturPerfDataExtEntry 5 } ::= { adslAturPerfDataExtEntry 5 }
adslAturPerfCurr1DayUasL OBJECT-TYPE adslAturPerfCurr1DayUasL OBJECT-TYPE
SYNTAX AdslPerfCurrDayCount SYNTAX AdslPerfCurrDayCount
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 21, line 24 skipping to change at page 21, line 33
::= { adslExtMibObjects 22 } ::= { adslExtMibObjects 22 }
adslConfProfileExtEntry OBJECT-TYPE adslConfProfileExtEntry OBJECT-TYPE
SYNTAX AdslConfProfileExtEntry SYNTAX AdslConfProfileExtEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry extends the adslLineConfProfileEntry "An entry extends the adslLineConfProfileEntry
defined in [1]. defined in [1].
Each entry corresponds to an ADSL line profile." Each entry corresponds to an ADSL line profile."
AUGMENTS { adslLineConfProfileEntry } INDEX { IMPLIED adslLineConfProfileName}
::= { adslConfProfileExtTable 1 } ::= { adslConfProfileExtTable 1 }
AdslConfProfileExtEntry ::= AdslConfProfileExtEntry ::=
SEQUENCE { SEQUENCE {
adslConfProfileLineType INTEGER adslConfProfileLineType INTEGER
} }
adslConfProfileLineType OBJECT-TYPE adslConfProfileLineType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
noChannel (1), -- no channels exist noChannel (1), -- no channels exist
skipping to change at page 22, line 23 skipping to change at page 22, line 33
in this MIB module." in this MIB module."
::= { adslExtMibObjects 23 } ::= { adslExtMibObjects 23 }
adslAlarmConfProfileExtEntry OBJECT-TYPE adslAlarmConfProfileExtEntry OBJECT-TYPE
SYNTAX AdslAlarmConfProfileExtEntry SYNTAX AdslAlarmConfProfileExtEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry extends the adslLineAlarmConfProfileTable "An entry extends the adslLineAlarmConfProfileTable
defined in [10]. Each entry corresponds to an ADSL alarm profile." defined in [10]. Each entry corresponds to an ADSL alarm profile."
AUGMENTS { adslLineAlarmConfProfileEntry } INDEX { IMPLIED adslLineAlarmConfProfileName}
::= { adslAlarmConfProfileExtTable 1 } ::= { adslAlarmConfProfileExtTable 1 }
AdslAlarmConfProfileExtEntry ::= AdslAlarmConfProfileExtEntry ::=
SEQUENCE { SEQUENCE {
adslAtucThreshold15MinFailedFastR Unsigned32, adslAtucThreshold15MinFailedFastR Unsigned32,
adslAtucThreshold15MinSesL Unsigned32, adslAtucThreshold15MinSesL Unsigned32,
adslAtucThreshold15MinUasL Unsigned32 adslAtucThreshold15MinUasL Unsigned32
} }
adslAtucThreshold15MinFailedFastR OBJECT-TYPE adslAtucThreshold15MinFailedFastR OBJECT-TYPE
skipping to change at page 23, line 7 skipping to change at page 23, line 17
sent per interval per interface. A value '0' will sent per interval per interface. A value '0' will
disable the trap." disable the trap."
::= { adslAlarmConfProfileExtEntry 1 } ::= { adslAlarmConfProfileExtEntry 1 }
adslAtucThreshold15MinSesL OBJECT-TYPE adslAtucThreshold15MinSesL OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of Severed errored seconds encountered "The number of Severe errored seconds encountered by
by an an
ADSL interface withing any giving 15 minutes ADSL interface withing any giving 15 minutes
performance performance
data collection period, which cause the SNMP agent data collection period, which cause the SNMP agent
to send an adslAtucSesLTrap. One trap will be to send an adslAtucSesLTrap. One trap will be
sent per interval per interface. A value '0' will sent per interval per interface. A value '0' will
disable the trap." disable the trap."
::= { adslAlarmConfProfileExtEntry 2 } ::= { adslAlarmConfProfileExtEntry 2 }
adslAtucThreshold15MinUasL OBJECT-TYPE adslAtucThreshold15MinUasL OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
skipping to change at page 23, line 51 skipping to change at page 24, line 13
OBJECTS { adslAtucPerfCurr15MinFailedFastR } OBJECTS { adslAtucPerfCurr15MinFailedFastR }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Failed Fast Retrains 15 minutes threshold reached." "Failed Fast Retrains 15 minutes threshold reached."
::= { adslExtAtucTraps 0 1 } ::= { adslExtAtucTraps 0 1 }
adslAtucSesLThreshTrap NOTIFICATION-TYPE adslAtucSesLThreshTrap NOTIFICATION-TYPE
OBJECTS { adslAtucPerfCurr15MinSesL } OBJECTS { adslAtucPerfCurr15MinSesL }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Severed errored seconds 15 minutes threshold "Severe errored seconds 15 minutes threshold
reached." reached."
::= { adslExtAtucTraps 0 2 } ::= { adslExtAtucTraps 0 2 }
adslAtucUasLThreshTrap NOTIFICATION-TYPE adslAtucUasLThreshTrap NOTIFICATION-TYPE
OBJECTS { adslAtucPerfCurr15MinUasL } OBJECTS { adslAtucPerfCurr15MinUasL }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Unavailable seconds 15 minutes threshold reached." "Unavailable seconds 15 minutes threshold reached."
::= { adslExtAtucTraps 0 3 } ::= { adslExtAtucTraps 0 3 }
skipping to change at page 25, line 33 skipping to change at page 25, line 42
profiles are implemented." profiles are implemented."
::= { adslExtCompliances 1 } ::= { adslExtCompliances 1 }
-- units of conformance -- units of conformance
adslExtLineGroup OBJECT-GROUP adslExtLineGroup OBJECT-GROUP
OBJECTS { OBJECTS {
adslLineConfProfileDualLite, adslLineConfProfileDualLite,
adslLineTransAtucCap, adslLineTransAtucCap,
adslLineTransAtucConfig, adslLineTransAtucConfig,
adslLineTransAtucCapActual, adslLineTransAtucActual,
adslLineGlitePowerState adslLineGlitePowerState
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing configuration "A collection of objects providing configuration
information about an ADSL Line." information about an ADSL Line."
::= { adslExtGroups 1 } ::= { adslExtGroups 1 }
adslExtAtucPhysPerfRawCounterGroup OBJECT-GROUP adslExtAtucPhysPerfRawCounterGroup OBJECT-GROUP
OBJECTS { OBJECTS {
skipping to change at line 1313 skipping to change at page 28, line 36
[9] Chris Hansen, ITU "White Paper submission of Recommendation [9] Chris Hansen, ITU "White Paper submission of Recommendation
G.992.2" G.992.2"
June/July 1999. June/July 1999.
[10] G. Bathrick, F. Ly "Definitions of Managed Objects for the [10] G. Bathrick, F. Ly "Definitions of Managed Objects for the
ADSL ADSL
Lines", May 14, 1999. Lines", May 14, 1999.
[11] D. Harrington, R. Presuhn, B. Wijnen, "An architecture for [11] D. Harrington, R. Presuhn, B. Wijnen, "An architecture for
Describing SNMP Management Frameworks", RFC 2571, April 1999. Describing SNMP Management Frameworks", RFC 2571, April 1999.
[14] Rose, M. and K. McCloghrie, "Structure and Identification of
Management Information for TCP/IP-based Internets", STD 16,
RFC
1155, May 1990.
[15] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD
16,
RFC 1212, March 1991.
[16] Rose, M., "A Convention for Defining Traps for use with the
SNMP", RFC 1215, March 1991.
[17] McCloghrie K., Perkins D. and J. Schoenwaelder, "Conformance
Statements for SMIv2", RFC 2580, April 1999.
[18] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
"Introduction to Community-based SNMPv2", RFC 1901, January
1996.
[19] 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.
[20] Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message
Processing and Dispatching for the Simple Network Management
Protocol (SNMP)", RFC 2572, April 1999.
[21] Blumenthal, U. and B. Wijnen, "User-based Security Model
(USM)
for version 3 of the Simple Network Management Protocol
(SNMPv3)", RFC 2574, April 1999.
[22] Levi, D., Meyer, P. and B. Stewart, "SNMP Applications", RFC
2573, April 1999.
[23] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based
Access
Control Model (VACM) for the Simple Network Management
Protocol
(SNMP)", RFC 2575, April 1999.
10. Security Considerations
1) Blocking unauthorized access to the ADSL MIB via the element
management system is outside the scope of this document. It should
be
noted that access to the MIB permits the unauthorized entity to
modify the profiles (sect 6.4) such that both subscriber service
and
network operations can be interfered with. Subscriber service can
be
altered by modifying any of a number of service characteristics
such
as rate partitioning and maximum transmission rates. Network
operations can be impacted by modification of trap thresholds such
as
SNR margins.
2) There are a number of managed objects in this MIB that may be
considered to contain sensitive information. In particular, the
certain objects may be considered sensitive in many environments,
since it would allow an intruder to obtain information about which
vendor's equipment is in use on the network. Therefore, it may be
important in some environments to control read access to these
objects and possibly to even encrypt the values of these object
when
sending them over the network via SNMP. Not all versions of SNMP
provide features for such a secure environment.
SNMPv1 by itself is such an insecure environment. Even if the
network itself is secure (for example by using IPSec), even then,
there is no control as to who on the secure network is allowed to
access and GET (read) the objects in this MIB. It is recommended
that the implementors consider the security features as provided
by
the SNMPv3 framework. Specifically, the use of the User-based
Security Model RFC 2574 [21] and the View-based Access Control
Model
RFC 2575 [23] is recommended.
It is then a customer/user responsibility to ensure that the SNMP
entity giving access to an instance of this MIB, is properly
configured to give access to those objects only to those
principals
(users) that have legitimate rights to access them.
3) ADSL layer connectivity from the ATU-R will permit the
subscriber
to manipulate both the ADSL link directly and the AOC/EOC channels
for their own loop. For example, unchecked or unfiltered
fluctuations initiated by the subscriber could generate sufficient
traps to potentially overwhelm either the management interface to
the
network or the element manager. Other attacks affecting the ATU-R
portions of the MIB may also be possible.
11. 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
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 implementers 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.
12. Authors' Addresses
Faye Ly
Copper Mountain Networks
Norcal Office
2470 Embarcadero Way
Palo Alto, CA 94303
Phone: +1 650-687-3323
Fax: +1 650-687-3372
EMail: faye@coppermountain.com
Gregory Bathrick
NOKIA High Speed Access Nodes
1310 Redwood Way,
Petaluma, CA 94954, USA
Phone: +1 707-793-7030
Fax: +1 707-792-0850
EMail: greg.bathrick@nokia.com
13. 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.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
 End of changes. 

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