draft-ietf-adslmib-adsl2-00.txt   draft-ietf-adslmib-adsl2-01.txt 
INTERNET-DRAFT Supplemental ADSL Line MIB Gregory Bathrick INTERNET-DRAFT Supplemental ADSL Line MIB Faye Ly
AG Communication Systems
Faye Ly
Copper Mountain Networks Copper Mountain Networks
May 10, 1999 Gregory Bathrick
AG Communication Systems
June 24,
1999
Definitions of Supplemental Managed Objects Definitions of Supplemental Managed Objects
for ADSL Lines for ADSL Lines
May 10, 1999 June 24, 1999
draft-ietf-adslmib-adsl2-00.txt draft-ietf-adslmib-adsl2-01.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 1, line 35 skipping to change at page 1, line 36
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 The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
To view the entire list of current Internet-Drafts, please check the
"1id-abstracts.txt" listing contained in the Internet-Drafts Shadow
Directories on ftp.is.co.za (Africa), ftp.nordu.net (Northern
Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au (Pacific
Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu (US West Coast).
2. Abstract 2. Abstract
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]. ADSL Line MIB defines not covered by the ADSL Line MIB [1].
management objects common for all ADSL lines regardless of line-
codes, as defined by ANSI T1.413. This MIB defines a supplemental
set of managed objects defined by ITU G.997.1 [8]. In particular, it
describes objects used to manage ADSL "Lite" interfaces as defined by
ITU-T G.992.2 [9].
3. The SNMP Network Management Framework 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 2271 [13]. 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 purpose of management. The first version of this the purpose of management. The first version of this
Structure of Management Information (SMI) is called SMIv1 and Structure of Management Information (SMI) is called SMIv1 and
described in RFC 1155 [14], RFC 1212 [15] and RFC 1215 [16]. described in RFC 1155 [14], RFC 1212 [15] and RFC 1215 [16].
The second version, called SMIv2, is described in RFC 1902 The second version, called SMIv2, is described in RFC 2579
[1], RFC 1903 [2] and RFC 1904 [17]. [1], RFC 1903 [2] and RFC 1904 [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 3, line 7 skipping to change at page 2, line 52
This document specifies a MIB module that is compliant to the SMIv2. This document specifies a MIB module that is compliant to the SMIv2.
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. Object Definitions 4. Change Log
This section tracks changes made to the revisions of the Internet
Drafts of this document. It will be deleted when the document is
published as an RFC.
Managed objects are accessed via a virtual information store, The following changes were made for the version of the document dated
termed June 24, 1999.
the Management Information Base or MIB. Objects in the MIB are
defined using the extended subset of Abstract Syntax Notation One - Deleted orginal section 4 and replace it with the change log.
(ASN.1) defined in the SMI. In particular, each object type is - Corrected Reference section to include the right RFCs.
named - Deleted portions of the Abstract section so there is no
by an OBJECT IDENTIFIER, an administratively assigned name. The overlapping
object type together with an object instance serves to uniquely between this section and the Introduction section.
identify a specific instantiation of the object. For human - Rename adslExtConfProfileLineMode to adslConfProfileLineMode
convenience, we often use a textual string, termed the descriptor, - Added the adslAtucAlarmConfExtTable which contains the
to following
also refer to the object type. objects:
adslAtucThreshold15MinFailedFastR
adslAtucThreshold15MinSesL
adslAtucThreshold15MinUasL
- Added 3 traps:
adslAtucFailedFastRThresholdTrap
adslAtucSesLThresholdTrap
adslAtucUasLThresholdTrap
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 Supplemental ADSL LINE MIB with standard MIBs 6. Relationship of the Supplemental ADSL LINE MIB with standard MIBs
This section outlines the relationship of Supplemental ADSL Line MIB This section outlines the relationship of Supplemental ADSL Line 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". Supplemental ADSL Line MIB obeys the same "standardization". Supplemental ADSL Line MIB obeys the same
relationship between ADSL Line MIB to other standard MIBs. relationship between ADSL Line MIB to other standard MIBs with one
exception for the ifOperStatus as defined in RFC 1213 [3].
7. Conventions used in the MIB 6.1 ifOperStatus
ifOperStatus is set to down(2) when the ADSL line interface has gone
into the no-power state (L3).
7. Conventions used in the MIB
7.1 Naming Conventions 7.1 Naming Conventions
In addition to the naming conventions defined in the ADSL Line MIB In addition to the naming conventions defined in the ADSL Line MIB
[1] section 7. This document defines the following naming [10] section 6. This document defines the following naming
conventions as well: conventions as well:
A. Block Definition A. Block Definition
ADSL Line MIB defines a "block" as "a physical-layer `data buffer' ADSL Line MIB defines a "block" as "a physical-layer `data buffer'
over which CRCs are calculated". This document further clarifies over which CRCs are calculated".
that a "block" referred in this MIB is defined as "a physical-layer
'data buffer' over which CRCs are calculated or a superframe. A ??
"superframe" is defined as "???". . what is a R-S frame
. 68 R-S frames compose a superframe?
7.2 Structure 7.2 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.3 Additional Managed Objects 7.3 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 Capabilities - ATU-C Transmission System Capabilities
- 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 Severed Error Second-line and Unavailable Second
- Correct Definition of Blocks - Clarify Definition of Blocks
Besides the management of ADSL "Lite", another object needs to be Besides the management of ADSL "Lite", another object needs to be
added to the ADSL Line MIB [10] in order to manage the ADSL line 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.3.1 ATU-C ADSL Transmission System Enabling 7.3.1 ATU-C ADSL Transmission System Parameters
The adslLineConfigTable needs to be extended to cover the ATU-C The adslLineConfigTable needs to be extended to cover the ATU-C
ADSL Transmission system enabling. Objects are defined to enable the ADSL Transmission system enabling. Objects are defined to enable the
configuration and monitoring of the ATU-C and ATU-R transmission configuration and monitoring of the ATU-C and ATU-R transmission
system capabilities as well as the actual ADSL transmission system system capabilities as well as the actual ADSL transmission system
being used. being used.
7.3.2 Power Management 7.3.2 Power Management
Specifically the ATU-C and ATU-R Total Output Power ?? Specifically the ATU-C and ATU-R Total Output Power ??
skipping to change at page 5, line 12 skipping to change at page 5, line 18
failed fast retrain count. These two counters need to be added to failed fast retrain count. These two counters need to be added to
all performance tables. all performance tables.
7.3.4 Counters for Severed Error Second-line and Unavailable Second 7.3.4 Counters for Severed Error Second-line and Unavailable Second
Section 7.2.1.1.7 and section 7.2.1.1.9 specify two counters 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 (severed error second-line and unavailable second) are added to all
the performance tables. the performance tables.
7.3.5 Correct Definition of Blocks 7.3.5 Clarify Definition of Blocks
Correct block definition used by ADSL MIB is specified in section Clarify block definition used by ADSL MIB is specified in section
7.1.A. 7.1.A.
7.3.6 ADSL Line Mode configuration 7.3.6 ADSL Line Mode configuration
The adslLineConfProfileTable is extended to include a new object that The adslLineConfProfileTable is extended to include a new object that
allow operator to specify the line mode in a profile entry. allow operator to specify the line mode in a profile entry.
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 6, line 12 skipping to change at page 6, line 19
Phoenix, AZ 85027 USA Phoenix, AZ 85027 USA
Tel: +1 602-582-7679 Tel: +1 602-582-7679
Fax: +1 602-582-7697 Fax: +1 602-582-7697
E-mail: bathricg@agcs.com E-mail: bathricg@agcs.com
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-858-8500 X240 Tel: +1 650-687-3323
E-Mail: faye@coppermountain.com E-Mail: faye@coppermountain.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 2 } ::= { adslMIB 2 }
adsl2MIBObjects OBJECT IDENTIFIER ::= {atm2MIB 1} adsl2MIBObjects OBJECT IDENTIFIER ::= {atm2MIB 1}
AdslTransmissionModeType ::= TEXTUAL-CONVENTION AdslTransmissionModeType ::= TEXTUAL-CONVENTION
STATUS current STATUS current
skipping to change at page 7, line 30 skipping to change at page 7, line 37
adslExtLineEntry OBJECT-TYPE adslExtLineEntry OBJECT-TYPE
SYNTAX AdslExtLineEntry SYNTAX AdslExtLineEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"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."
AUGMENTS { adslLineEntry } AUGMENTS { adslLineEntry }
::= { adslLineTable 1 } ::= { adslLineExtTable 1 }
AdslExtLineEntry ::= AdslExtLineEntry ::=
SEQUENCE { SEQUENCE {
adslLineTransEnabled INTEGER,
adslLineTransAtucCap AdslTransmissionModeType, adslLineTransAtucCap AdslTransmissionModeType,
adslLineTransAturCap AdslTransmissionModeType, adslLineTransAturCap AdslTransmissionModeType,
adslLineTransCapActual AdslTransmissionModeType adslLineTransCapActual AdslTransmissionModeType
} }
adslLineTransEnabled OBJECT-TYPE
SYNTAX INTEGER {
yes(1),
no(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object is used to enable or disable the ADSL
Line
Transmission."
::= { adslExtLineEntry 1 }
adslLineTransAtucCap OBJECT-TYPE adslLineTransAtucCap OBJECT-TYPE
SYNTAX AdslTransmissionModeType SYNTAX AdslTransmissionModeType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the ATU-C Transmission system "Specifies the ATU-C Transmission system
capability." capability."
REFERENCE "Section 7.3.2 ITU G.997.1 [8]" REFERENCE "Section 7.3.2 ITU G.997.1 [8]"
::= { adslExtLineEntry 1 } ::= { adslExtLineEntry 2 }
adslLineTransAturCap OBJECT-TYPE adslLineTransAturCap OBJECT-TYPE
SYNTAX AdslTransmissionModeType SYNTAX AdslTransmissionModeType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the ATU-R Transmission system "Specifies the ATU-R Transmission system
capability." capability."
REFERENCE "Section 7.3.2 ITU G.997.1 [8]" REFERENCE "Section 7.3.2 ITU G.997.1 [8]"
::= { adslExtLineEntry 2 } ::= { adslExtLineEntry 3 }
adslLineTransCapActual OBJECT-TYPE adslLineTransCapActual OBJECT-TYPE
SYNTAX AdslTransmissionModeType SYNTAX AdslTransmissionModeType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the actual Transmission system capability "Specifies the actual Transmission system capability
for this for this
ADSL line." ADSL line."
REFERENCE "Section 7.3.2 ITU G.997.1 [8]" REFERENCE "Section 7.3.2 ITU G.997.1 [8]"
::= { adslExtLineEntry 3 } ::= { adslExtLineEntry 4 }
adslAtucPerfDataExtTable OBJECT-TYPE adslAtucPerfDataExtTable OBJECT-TYPE
SYNTAX SEQUENCE OF AdslAtucPerfDataExtEntry SYNTAX SEQUENCE OF AdslAtucPerfDataExtEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains ADSL physical line counters "This table contains ADSL physical line counters
information not defined in the adslAtucPerfDataTable from the ADSL- information not defined in the adslAtucPerfDataTable from the ADSL-
LINE-MIB [10]." LINE-MIB [10]."
::= { adslMibObjects 18 } ::= { adslMibObjects 18 }
skipping to change at page 16, line 6 skipping to change at page 16, line 27
adslExtConfProfileTable OBJECT-TYPE adslExtConfProfileTable OBJECT-TYPE
SYNTAX SEQUENCE OF AdslExtConfProfileEntry SYNTAX SEQUENCE OF AdslExtConfProfileEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains ADSL line profile configuration "This table contains ADSL line profile configuration
information not defined in the information not defined in the
adslLineConfProfileTable adslLineConfProfileTable
from the ADSL-LINE-MIB [1]. This includes the line from the ADSL-LINE-MIB [1]. This includes the line
mode." mode."
::= { adslMibObjects 19 } ::= { adslMibObjects 20 }
adslExtConfPrifleEntry OBJECT-TYPE adslExtConfPrifleEntry OBJECT-TYPE
SYNTAX AdslExtConfProfileEntry SYNTAX AdslExtConfProfileEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry extends the adslLineConfPrifileEntry "An entry extends the adslLineConfPrifileEntry
defined in [1]. defined in [1].
Each entry corresponds to an ADSL line profile." Each entry corresponds to an ADSL line profile."
AUGMENTS { adslLineConfProfileEntry } AUGMENTS { adslLineConfProfileEntry }
::= { adslExtConfProfileTable 1 } ::= { adslExtConfProfileTable 1 }
AdslExtConfProfileEntry ::= AdslExtConfProfileEntry ::=
SEQUENCE { SEQUENCE {
adslExtConfPorifleLineMode INTEGER adslConfPorifileLineMode INTEGER
} }
adslExtConfProfileLineMode OBJECT-TYPE adslConfProfileLineMode OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
noChannel (1), -- no channels exist noChannel (1), -- no channels exist
fastOnly (2), -- fast channel exists only fastOnly (2), -- fast channel exists only
interleavedOnly (3), -- interleaved channel exists interleavedOnly (3), -- interleaved channel exists
-- only -- only
fastOrInterleaved (4),-- either fast or interleaved fastOrInterleaved (4),-- either fast or interleaved
-- channels can exist, but -- channels can exist, but
-- only one at any time -- only one at any time
fastAndInterleaved (5)-- both fast or interleaved fastAndInterleaved (5)-- both fast or interleaved
-- channels exist -- channels exist
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" "
This object is used to configure the ADSL physical This object is used to configure the ADSL physical
line line
mode. " mode. "
::= { adslExtConfProfileEntry 1 } ::= { adslExtConfProfileEntry 1 }
adslLineAlarmConfProExtTable OBJECT-TYPE
SYNTAX SEQUENCE OF AdslLineAlarmConfProExtEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table extends the
adslLineAlarmConfProfileTable and
provides threshold parameters for all the counters
defined
in this MIB module."
::= { adslMibObjects 21 }
adslLineAlarmConfProfExtEntry OBJECT-TYPE
SYNTAX AdslLineAlarmConfProfExtEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry extends the adslLineAlarmConfProfileTable
defined in [10]. Each entry corresponds to an ADSL alarm profile."
AUGMENTS { adslLineAlarmConfProfileEntry }
::= { adslLineAlarmConfProfTable 1 }
AdslLineAlarmConfProfExtEntry ::=
SEQUENCE {
adslAtucThreshold15MinFailedFastR Unsigned32,
adslAtucThreshold15MinSesL Unsigned32,
adslAtucThreshold15MinUasL Unsigned32
}
adslAtucThreshold15MinFailedFastR OBJECT-TYPE
SYNTAX Unsigned32
UNITS "seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The number of failed retrains encountered by an
ADSL interface withing any givin 15 minutes
performance
data collection period, which cause the SNMP agent
to send an adslAtucFailedFastRTrap. One trap will
be
sent per interval per interface. A value '0' will
disable the trap."
::= { adslLineAlarmConfProfExtEntry 1 }
adslAtucThreshold15MinSesL OBJECT-TYPE
SYNTAX Unsigned32
UNITS "seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The number of Severed errored seconds encountered
by an
ADSL interface withing any givin 15 minutes
performance
data collection period, which cause the SNMP agent
to send an adslAtucSesLTrap. One trap will be
sent per interval per interface. A value '0' will
disable the trap."
::= { adslLineAlarmConfProfExtEntry 2 }
adslAtucThreshold15MinUasL OBJECT-TYPE
SYNTAX Unsigned32
UNITS "seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The number of unavailable errored seconds
encountered by an
ADSL interface withing any givin 15 minutes
performance
data collection period, which cause the SNMP agent
to send an adslAtucFailedFastRTrap. One trap will
be
sent per interval per interface. A value '0' will
disable the trap."
::= { adslLineAlarmConfProfExtEntry 3 }
-- trap definitions
adsl2Traps OBJECT IDENTIFIER ::= { adslMibObjects 22 }
adsl2AtucTraps OBJECT IDENTIFIER ::= { adsl2Traps 1 }
adslAtucFailedFastRThreshTrap NOTIFICATION-TYPE
OBJECTS { adslAtucPerfCurr15FailedFastR }
STATUS current
DESCRIPTION
"Failed Fast Retrains 15 minutes threshold reached."
::= { adslAtucTraps 0 1 }
adslAtucSesLThreshTrap NOTIFICATION-TYPE
OBJECTS { adslAtucPerfCurr15MinSesL }
STATUS current
DESCRIPTION
"Severed errored seconds 15 minutes threshold
reached."
::= { adslAtucTraps 0 2 }
adslAtucUasLThreshTrap NOTIFICATION-TYPE
OBJECTS { adslAtucPerfCurr15MinUasL }
STATUS current
DESCRIPTION
"Unavailable seconds 15 minutes threshold reached."
::= { adslAtucTraps 0 3 }
-- conformance information -- conformance information
adsl2Conformance OBJECT IDENTIFIER ::= { adslLineMib 5 } adsl2Conformance OBJECT IDENTIFIER ::= { adslLineMib 5 }
adsl2Groups OBJECT IDENTIFIER ::= { adsl2Conformance 1 } adsl2Groups OBJECT IDENTIFIER ::= { adsl2Conformance 1 }
adsl2Compliances OBJECT IDENTIFIER ::= { adsl2Conformance 2 } adsl2Compliances OBJECT IDENTIFIER ::= { adsl2Conformance 2 }
-- ATU-C agent compliance statements -- ATU-C agent compliance statements
adsl2LineMibAtucCompliance MODULE-COMPLIANCE adsl2LineMibAtucCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for SNMP entities which "The compliance statement for SNMP entities which
manage ADSL ATU-C interfaces." manage ADSL ATU-C interfaces."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS MANDATORY-GROUPS
skipping to change at page 17, line 18 skipping to change at page 19, line 49
DESCRIPTION DESCRIPTION
"The compliance statement for SNMP entities which "The compliance statement for SNMP entities which
manage ADSL ATU-C interfaces." manage ADSL ATU-C interfaces."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS MANDATORY-GROUPS
{ {
adsl2LineGroup, adsl2LineGroup,
adsl2AtucPhysPerfRawCounterGroup, adsl2AtucPhysPerfRawCounterGroup,
adsl2AturPhysPerfRawCounterGroup, adsl2AturPhysPerfRawCounterGroup,
adsl2LineConfProfileControlGroup OBJECT-GROUP adsl2LineConfProfileControlGroup,
adsl2LineAlarmConfProfileGroup
} }
GROUP adsl2AtucPhysPerfRawCounterGroup GROUP adsl2AtucPhysPerfRawCounterGroup
DESCRIPTION DESCRIPTION
"This group is optional. Implementations which "This group is optional. Implementations which
require continuous ATU-C physical event counters require continuous ATU-C physical event counters
should implement this group." should implement this group."
GROUP adsl2AturPhysPerfRawCounterGroup GROUP adsl2AturPhysPerfRawCounterGroup
DESCRIPTION DESCRIPTION
"This group is optional. Implementations which "This group is optional. Implementations which
require continuous ATU-R physical event counters require continuous ATU-R physical event counters
skipping to change at page 17, line 33 skipping to change at page 20, line 16
"This group is optional. Implementations which "This group is optional. Implementations which
require continuous ATU-C physical event counters require continuous ATU-C physical event counters
should implement this group." should implement this group."
GROUP adsl2AturPhysPerfRawCounterGroup GROUP adsl2AturPhysPerfRawCounterGroup
DESCRIPTION DESCRIPTION
"This group is optional. Implementations which "This group is optional. Implementations which
require continuous ATU-R physical event counters require continuous ATU-R physical event counters
should implement this group." should implement this group."
OBJECT adslAtucThreshold15MinFailedFastR
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslAtucThreshold15MinSesL
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslAtucThreshold15MinUasL
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
adsl2LineGroup OBJECT-GROUP adsl2LineGroup OBJECT-GROUP
OBJECTS { OBJECTS {
adslLineTransEnabled,
adslLineTransAtucCap, adslLineTransAturCap, adslLineTransAtucCap, adslLineTransAturCap,
adslLineTransCapActual adslLineTransCapActual
} }
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."
::= { adsl2Groups 1 } ::= { adsl2Groups 1 }
adsl2AtucPhysPerfRawCounterGroup OBJECT-GROUP adsl2AtucPhysPerfRawCounterGroup OBJECT-GROUP
skipping to change at page 18, line 36 skipping to change at page 21, line 38
adslAturPerfPrev1DayUasL adslAturPerfPrev1DayUasL
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing raw performance "A collection of objects providing raw performance
counts on an ADSL Line (ATU-C end)." counts on an ADSL Line (ATU-C end)."
::= { adsl2Groups 3 } ::= { adsl2Groups 3 }
adsl2LineConfProfileControlGroup OBJECT-GROUP adsl2LineConfProfileControlGroup OBJECT-GROUP
OBJECTS { OBJECTS {
adslExtConfPorifleLineMode adslConfPorifleLineMode
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing profile "A collection of objects providing profile
control for the ADSL system." control for the ADSL system."
::= { adsl2Groups 4 } ::= { adsl2Groups 4 }
END adsl2LineAlarmConfProfileGroup OBJECT-GROUP
OBJECTS {
adslAtucThreshold15MinFailedFastR,
adslAtucThreshold15MinSesL,
adslAtucThreshold15MinUasL
}
STATUS current
DESCRIPTION
"A collection of objects providing alarm profile
control for the ADSL system."
::= { adsl2Groups 4 } END
9. Acknowledgments 9. Acknowledgments
This document is a product of the ADSL MIB Working Group. This document is a product of the ADSL MIB Working Group.
10. References 10. References
[1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and
S. Waldbusser, "Structure of Management Information for
Version
2 of the Simple Network Management Protocol (SNMPv2)",
RFC 1902, January 1996.
[2] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [1] B. Wijnen, D. Harrington, R. Presuhn, "Structure of
"Textual Conventions for SNMPv2", RFC 1903, SNMP Research, Management Information Version 2 (SMIv2)" RFC 2578,
Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., April 1999.
International Network Services, January 1996.
[2] K. McCloghrie, D. Perkins, J. Schoenwaelder,
"Textual Conventions for SMIv2", RFC 2579, April 1999.
[3] McCloghrie, K., and M. Rose, Editors, "Management [3] McCloghrie, K., and M. Rose, Editors, "Management
Information Base for Network Management of TCP/IP-based Information Base for Network Management of TCP/IP-based
internets: MIB-II", STD 17, RFC 1213, Hughes LAN Systems, internets: MIB-II", STD 17, RFC 1213, Hughes LAN Systems,
Performance Systems International, March 1991. Performance Systems International, March 1991.
[4] McCloghrie, K. and F. Kastenholz, "The Interfaces Group [4] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB using SMIv2", RFC 2233, Cisco Systems, FTP Software, MIB using SMIv2", RFC 2233, Cisco Systems, FTP Software,
November 1997. November 1997.
skipping to change at page 19, line 44 skipping to change at page 23, line 4
[7] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and [7] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and
S. Waldbusser, "Protocol Operations for Version 2 of the S. Waldbusser, "Protocol Operations for Version 2 of the
Simple Simple
Network Management Protocol (SNMPv2)", RFC 1905, January Network Management Protocol (SNMPv2)", RFC 1905, January
1996. 1996.
[8] ITU Draft Recommendation G.997.1 "Physical Layer Management [8] ITU Draft Recommendation G.997.1 "Physical Layer Management
for for
Digital Subscriber Line (DSL) Transceivers.", January 1999 Digital Subscriber Line (DSL) Transceivers.", January 1999
[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
Describing SNMP Management Frameworks", RFC 2571, April 1999.
 End of changes. 

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