draft-ietf-adslmib-adsllinemib-00.txt   draft-ietf-adslmib-adsllinemib-01.txt 
INTERNET-DRAFT ADSL Line MIB Gregory Bathrick INTERNET-DRAFT ADSL Line MIB Gregory Bathrick
AG Communication Systems AG Communication Systems
August 7, 1998 August 7, 1998
Definitions of Managed Objects Definitions of Managed Objects
for the ADSL Lines for the ADSL Lines
August 7, 1998 August 7, 1998
draft-ietf-adslmib-adsllinemib-00.txt draft-ietf-adslmib-adsllinemib-01.txt
1. Status of this Memo 1. Status of this Memo
This document is an Internet-Draft. Internet-Drafts are working This document is an Internet-Draft. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, documents of the Internet Engineering Task Force (IETF), its areas,
and its working groups. Note that other groups may also distribute and its working groups. Note that other groups may also distribute
working documents as Internet-Drafts. 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.''
To view the entire list of current Internet-Drafts, please check To view the entire list of current Internet-Drafts, please check the
the "1id-abstracts.txt" listing contained in the Internet-Drafts "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow
Shadow Directories on ftp.is.co.za (Africa), ftp.nordu.net Directories on ftp.is.co.za (Africa), ftp.nordu.net (Northern
(Northern Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au (Pacific
(Pacific Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu (US West Coast).
(US West Coast).
2. Abstract 2. Abstract
This document defines a standard SNMP MIB for ADSL lines based on the This document defines a standard SNMP MIB for ADSL lines based on the
ADSL Forum standard data model [9]. The model assumed by this MIB is ADSL Forum standard data model [9]. The model assumed by this MIB is
that the SNMP agent's perspective is from the ATU-C side which acts that the SNMP agent's perspective is from the ATU-C side which acts
as a proxy for the ATU-R. Each MIB instance includes information for as a proxy for the ATU-R. Each MIB instance includes information for
both ends of a single line, i.e., both the ATU-C and ATU-R. both ends of a single line, i.e., both the ATU-C and ATU-R.
It should be noted that the first version of this document was It should be noted that much of the content for the first version of
derived from work completed by the ADSL Forum's Network Management this document came from work completed by the ADSL Forum's Network
working group and documented in ADSL Forum TR-006 "SNMP-based ADSL Management working group and documented in ADSL Forum TR-006 "SNMP-
Line MIB"[9]. See Acknowledgement Section for a list individuals of based ADSL Line MIB"[9]. See Acknowledgement Section for a list
those involved with this effort. individuals of those involved with this effort.
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 2271 [13].
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
skipping to change at page 3, line 43 skipping to change at page 3, line 44
6. Relationship of the ADSL LINE MIB with standard MIBs 6. Relationship of the ADSL LINE MIB with standard MIBs
This section outlines the relationship of this MIB with other MIBs This section outlines the relationship of this MIB with other MIBs
described in RFCs and in various degrees of "standardization". MIB-2 described in RFCs and in various degrees of "standardization". MIB-2
(RFC 1213 [4] and 2233 [5]) and the Entity MIB (RFC 2037 [25]) are (RFC 1213 [4] and 2233 [5]) and the Entity MIB (RFC 2037 [25]) are
discussed below. discussed below.
6.1 General MIB-2 Integration (RFCs 1213 [4] and 2233 [5]) 6.1 General MIB-2 Integration (RFCs 1213 [4] and 2233 [5])
The ADSL LINE MIB specifies the detailed attributes of a data The ADSL LINE MIB specifies the detailed attributes of a data
interface. As such, it needs to integrate with MIB-2 (see [4] and interface. As such, it needs to integrate with MIB-2 ([4] and [5]).
[5]). The IANA has assigned the following ifTypes to ADSL: The IANA has assigned the following ifType(s) for XDSL:
IANAifType ::= TEXTUAL-CONVENTION IANAifType ::= TEXTUAL-CONVENTION
. . . . . .
SYNTAX INTEGER { SYNTAX INTEGER {
. . . . . .
adsl(94), -- Asymmetric Digital Subscriber Loop adsl(94), -- Asymmetric Digital Subscriber Loop
skipping to change at page 4, line 47 skipping to change at page 4, line 47
adslPhysIf ::= { transmission 94 } -- Physical tables adslPhysIf ::= { transmission 94 } -- Physical tables
adslInterIf ::= { transmission 124 } -- Interleaved Channel adslInterIf ::= { transmission 124 } -- Interleaved Channel
tables tables
adslFastIf ::= { transmission 125} -- Fast Channel tables adslFastIf ::= { transmission 125} -- Fast Channel tables
with each MIB branch containing the appropriate tables for that with each MIB branch containing the appropriate tables for that
interface type, as discussed below. Most such tables extends the interface type, as discussed below. Most such tables extends the
ifEntry table, and are indexed by ifIndex. In addition, there are ifEntry table, and are indexed by ifIndex. In addition, there are
two "profile" tables which may be accessed by ifIndex, or may be two "profile" tables which may be accessed by ifIndex, or
accessed with a profileIndex, as discussed in section 7.4 Profiles. profileIndex depending on the profile mode implemented. This is
explained in detail in section 7.4 Profiles.
6.1.1 ADSL Interface Types 6.1.1 ADSL Interface Types
As shown below, three ADSL interface types are defined in this As shown below, three ADSL interface types are defined in this
document, namely physical, interleaved channel, and fast channel. document, namely physical, interleaved channel, and fast channel.
The physical interface represents characteristics of the physical The physical interface represents characteristics of the physical
media associated with both the ATUC and ATUR. The interleaved and media associated with both the ATUC and ATUR. The interleaved and
fast channel interface represent the characteristics of the two types fast channel interface represent the characteristics of the two types
of ADSL channels. of ADSL channels.
For each ADSL Line, a physical interface always exists. Depending For each ADSL Line, a physical interface always exists. Depending
on which ADSL operational configuration is present (as listed in on which ADSL operational configuration is present (as listed in
Figure 5), the channel interfaces (fast or interleaved) may or may Figure 5), the channel interfaces (fast or interleaved) may or may
not be optional. not be exist.
______ ______ ______ ______
| |____________________| | | |____________________| |
| ATUC | | ATUR | | ATUC | | ATUR |
| |____________________| | | |____________________| |
|______| |______| |______| |______|
| <----- physical --------> | | <----- physical --------> |
| <--- fast channel ------> | | <--- fast channel ------> |
skipping to change at page 7, line 50 skipping to change at page 7, line 50
---------------------------------------------------------------------- ----------------------------------------------------------------------
Figure 2: Use of ifTable Objects Figure 2: Use of ifTable Objects
Use the ifTest table for Diagnostic tests, which extends ifEntry. Use the ifTest table for Diagnostic tests, which extends ifEntry.
The adslLineMib defines ADSL-specific values for ifTestTypes and The adslLineMib defines ADSL-specific values for ifTestTypes and
ifTestCodes. ifTestCodes.
Use the ifStackTable to associate the entries for physical, fast, Use the ifStackTable to associate the entries for physical, fast,
interleaved channels, and higher layers (e.g., ATM) is shown below in interleaved channels, and higher layers (e.g., ATM) is shown below in
figure 3. Use of ifStackTable is mandatory, because configuration figure 3. Use of ifStackTable is necessary, because configuration
information is stored in profile tables associated with the information is stored in profile tables associated with the
physical-layer ifEntry only. The channels ifEntrys need the physical-layer ifEntry only. The channels ifEntrys need the
ifStackTable to find their associated physical-layer entry and thus ifStackTable to find their associated physical-layer entry and thus
their configuration parameters. (See Profile section, 7.4). their configuration parameters. (See Profile section, 7.4).
______ (ifEntry=k) ______ ______ (ifEntry=k) ______
| | fast channel | | | | fast channel | |
| |________________________| | | |________________________| |
| | and/or | | | | and/or | |
| | | | | | | |
skipping to change at page 9, line 28 skipping to change at page 9, line 28
A. Atuc/Atur are used for the ATU-C and ATU-R. In other RFCs, these A. Atuc/Atur are used for the ATU-C and ATU-R. In other RFCs, these
are sometimes referred to as the Near End (Ne) and Far End (Fe) are sometimes referred to as the Near End (Ne) and Far End (Fe)
respectively, but not in this document. respectively, but not in this document.
B. The terms, "transmit" and "receive", are from the perspective of B. The terms, "transmit" and "receive", are from the perspective of
the corresponding table's end of the line. For example, the corresponding table's end of the line. For example,
adslAtucChanConfMaxTxRate defines the "downstream" rate, while adslAtucChanConfMaxTxRate defines the "downstream" rate, while
adslAturChanConfMaxTxRate defines the "upstream" rate for a adslAturChanConfMaxTxRate defines the "upstream" rate for a
particular channel. particular channel.
C. There are two possible channels: fast, and interleaved. Either C. There are two possible channels: fast, and interleaved. None, one
none, one or both may be implemented on a particular ADSL Line. or both may be implemented on a particular ADSL Line. Figure 5
Figure 5 illustrates all possible operational configurations. illustrates all possible operational configurations.
D. Lof, Lol, Los, Lpr mean Loss of Framing, Link, Signal, and Power, D. Lof, Lol, Los, Lpr mean Loss of Framing, Link, Signal, and Power,
respectively. Lpr is used by T1E1, so it is used for consistency respectively. Lpr is used by T1E1, so it is used for consistency
(rather than Lop). (rather than Lop).
A Loss of Link condition is declared at the ATU-C if a Loss of Signal A Loss of Link condition is declared at the ATU-C if a Loss of Signal
is not preceded by a 'dying-gasp' message from the ATU-R. Note that is not preceded by a 'dying-gasp' message from the ATU-R. Note that
Loss of Link is only supported by the ATU-C. Loss of Link is only supported by the ATU-C.
E. ES means errored second. An Errored Second is any second E. ES means errored second. An Errored Second is any second
containing one or more CRC anomaly, or one or more Los(s) or Severely containing one or more CRC anomaly, or one or more Los(s) or Severely
Errored Frame (Sef) defect(s). Errored Frame (Sef) defect(s).
F. A "block" is a physical-layer 'data buffer' over which CRCs are F. A "block" is a physical-layer 'data buffer' over which CRCs are
calculated. For example, in DMT, the block is defined as the ADSL calculated. For example, in DMT, the block is defined as the ADSL
superframe. The block duration is 250 micro-seconds so the block superframe. The block duration is 250 micro-seconds so the block
length in bytes, as defined in adslAtu*ChanCrcBlockLength, varies length in bytes, as defined in adslAtu*ChanCrcBlockLength, varies
with data rate. with data rate. See Line Code Specific MIBs [11] [12] for more line
code specific information.
G. Atn means Attenuation, Psd is Power Spectral Density and Snr is G. Atn means Attenuation, Psd is Power Spectral Density and Snr is
Signal to Noise Ratio. Signal to Noise Ratio.
H. LCS means line code specific, e.g., H. LCS means line code specific, e.g.,
o DMT = Discrete MultiTone o DMT = Discrete MultiTone
o CAP = Carrierless Amplitude and Phase modulation and o CAP = Carrierless Amplitude and Phase modulation and
skipping to change at page 10, line 33 skipping to change at page 10, line 33
The MIB has multiple parallel tables. There are tables for: The MIB has multiple parallel tables. There are tables for:
o line - common attributes o line - common attributes
o atuc and atur status o atuc and atur status
o atuc and atur performance o atuc and atur performance
- Current and up to 96 buckets of 15 min performance history - Current and up to 96 buckets of 15 min performance history
- Current and Previous 1 Day bucket performance history - Current and Previous 1-day bucket performance history
o profiles - configuration parameters and alarm parameters o profiles - configuration parameters and alarm parameters
Also, there are separate tables for Physical and Channel layers. Only There are separate tables for Physical and Channel layers. Since
one set of "channel" tables are defined, which are used for both fast their attributes are similar, only one set of "channel" tables are
and interleaved channels, since the attributes are the same. The defined to be used for both fast and interleaved channels. The
corresponding ifType gives the proper interpretation for that corresponding ifType gives the proper interpretation for that
ifEntry. ifEntry.
Finally, there are separate LCS tables, also for each end. These are
currently stubs. These will each be separate MIB Modules.
There could have been fewer tables by combining the ATU-C and ATU-R There could have been fewer tables by combining the ATU-C and ATU-R
information into shared tables. However, the tables are more easily information into shared tables. However, the tables are more easily
read when there are two identical sets of data. read when there are two identical sets of data.
The figure below lists the five possible ADSL operational The figure below lists the five possible ADSL operational
configurations. (indicated by the value of the adslLineType). In all configurations. (indicated by the value of the adslLineType). In all
configurations, the physical line interface entry will exist. configurations, the physical line interface entry will exist.
However, the existence of the ADSL channel varies in each case, as However, the existence of the ADSL channel varies in each case, as
shown below. shown below.
skipping to change at page 11, line 17 skipping to change at page 11, line 20
___________________________________________________________ ___________________________________________________________
No Channels (1) | Y | | | No Channels (1) | Y | | |
Fast Only (2) | Y | Y | | Fast Only (2) | Y | Y | |
Interleaved Only (3) | Y | | Y | Interleaved Only (3) | Y | | Y |
Fast or Interleaved (4) | Y | Y | Y | Fast or Interleaved (4) | Y | Y | Y |
Fast and Interleaved (5) | Y | Y | Y | Fast and Interleaved (5) | Y | Y | Y |
Figure 5: ADSL Operational configurations Figure 5: ADSL Operational configurations
NOTE: In (4), channel exists of either Fast or Interleaved type, but NOTE: In (4), channel exists of either Fast or Interleaved type, but
not both. the Manager may select the type of channel to be used. not both. The Manager may select the type of channel to be used.
Depending on which operation configuration exists, some or all ADSL Depending on which operation configuration exists, some or all ADSL
MIB tables are supported, as shown in below. MIB tables could be supported, as shown in below. See Conformance
Statements for more information on which objects are mandatory.
Table Phys Fast Interleaved Table Phys Fast Interleaved
___________________________________________________________ ___________________________________________________________
adslLineTable | Y | | | adslLineTable | Y | | |
adslAtucPhysTable | Y | | | adslAtucPhysTable | Y | | |
adslAturPhysTable | Y | | | adslAturPhysTable | Y | | |
adslAtucChanTable | | Y | Y | adslAtucChanTable | | Y | Y |
adslAturChanTable | | Y | Y | adslAturChanTable | | Y | Y |
adslAtucPerfDataTable | Y | | | adslAtucPerfDataTable | Y | | |
adslAturPerfDataTable | Y | | | adslAturPerfDataTable | Y | | |
adslAtucIntervalTable | Y | | | adslAtucIntervalTable | Y | | |
adslAturIntervalTable | Y | | | adslAturIntervalTable | Y | | |
adslAtucChanPerfDataTable | | Y | Y | adslAtucChanPerfDataTable | | Y | Y |
adslAturChanPerfDataTable | | Y | Y | adslAturChanPerfDataTable | | Y | Y |
adslAtucChanIntervalTable | | Y | Y | adslAtucChanIntervalTable | | Y | Y |
adslAturChanIntervalTable | | Y | Y | adslAturChanIntervalTable | | Y | Y |
Figure 6: Use of ADSL MIB Tables with various ifIndex values Figure 6: Use of ADSL MIB Tables with various ifIndex values
NOTE: For adslLineConfProfileTable and adslLineAlarmConfProfileTable, NOTE: For adslLineConfProfileTable and adslLineAlarmConfProfileTable
see Profile Section of this document for implementation details. will be present for all scenarios. See Profile Section of this
document for implementation details such as profile creation,
assignment, and indexing.
7.3 Counters, Interval Buckets and Thresholds 7.3 Counters, Interval Buckets and Thresholds
For physical-level ES, Los, Lof, Lol, Lpr and line initialization For physical-level ES, Los, Lof, Lol, Lpr and line initialization
attempts, there are event counters, current 15-minute and one (up to attempts, there are event counters, current 15-minute and one (up to
96) 15-minute history bucket(s) of "interval-counters", as well as 96) 15-minute history bucket(s) of "interval-counters", as well as
current and previous 1 Day interval-counters. current and previous 1-day interval-counters.
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
quarter hours. Likewise, an implementation may choose to align one quarter hours. Likewise, an implementation may choose to align one
day intervals with start of a day. day intervals with start of a day.
In all cases, the sum of the corresponding 15-minute interval timers In all cases, the sum of the corresponding 15-minute interval timers
for the current day should equal the current 1-day timers. However, for the current day should equal the current 1-day timers. However,
in most cases, this will not be the sum of all 96 intervals, as they in most cases, this will not be the sum of all 96 intervals, as they
skipping to change at page 13, line 13 skipping to change at page 13, line 19
always. always.
7.4.1 MODE-I : Dynamic Profiles 7.4.1 MODE-I : Dynamic Profiles
Implementations using this mode will enable the manager to Implementations using this mode will enable the manager to
dynamically create and delete profiles as needed. The index of the dynamically create and delete profiles as needed. The index of the
profile is an arbitrary integer in the range 1..N, where N is the profile is an arbitrary integer in the range 1..N, where N is the
maximum number of profiles supported by the equipment and is maximum number of profiles supported by the equipment and is
implementation specific. implementation specific.
One or more ADSL lines may be configured to share parameters in One or more ADSL lines may be configured to share parameters of a
Profile-n (adslLineConfProfileIndex = 'n') by setting their single profile (say adslLineConfProfileIndex = 'n') by setting their
adslLineConfProfile objects to the value of profile's index (n). If adslLineConfProfile objects to the value of profile's index (n). If
a change is made to Profile-n, all lines that refer to it will be a change is made to Profile-n, all lines that refer to it will be
re-configured to the changed parameters. re-configured to the changed parameters.
The next figure shows an example of how this mode can be implemented. The next figure shows an example of how this mode can be implemented.
In the example, ADSL lines '1' and 'x' share the configuration in In the example, ADSL lines '1' and 'x' share the configuration in
Profile-n, while line '2' uses Profile-1. Please note that three Profile-n, while line '2' uses Profile-1. Please note that all three
entries for each ADSL line, physical layer, the fast channel, and the entries for each ADSL line, physical layer, the fast channel, and the
interleaved channel, are represented by "i", "j", and "k" as before. interleaved channel, are represented by "i", "j", and "k" as before.
However, only the physical-layer entry "i" contains an adslLineTable However, only the physical-layer entry "i" contains an adslLineTable
entry, so only those entries contain pointers to the entry, so only those entries contain pointers to the
adslConfProfileEntry. The ifStackTable (see rfc2233 [5]) must be adslConfProfileEntry. The ifStackTable (see rfc2233 [5]) must be
used to link the channel entries to the corresponding physical layer used to link the channel entries to the corresponding physical layer
entry to get the channel's configuration parameters. entry to get the channel's configuration parameters.
ADSL ifIndex ifTable Configuration Line ADSL ifIndex ifTable Configuration Line
Profile Table Profile Table
skipping to change at page 14, line 25 skipping to change at page 14, line 33
adslLineAlarmConfProfileIndexNext, and adslLineAlarmConfProfileIndexNext, and
adslLineAlarmConfProfileRowStatus adslLineAlarmConfProfileRowStatus
are all used in conjunction with profiles. are all used in conjunction with profiles.
7.4.2 MODE-II : Static Profiles 7.4.2 MODE-II : Static Profiles
Implementations with this mode will automatically create a profile Implementations with this mode will automatically create a profile
one-for-one with each ADSL line physical entry with the profileIndex one-for-one with each ADSL line physical entry with the profileIndex
being the same as the ifIndex of the corresponding ADSL line entry being the same as the ifIndex of the corresponding ADSL line entry
("ix"). The Agent will not allow a Manager to create/delete ("ix"). In this mode, the Agent will not allow a Manager to
profiles in this mode. The adslLineConfProfile, create/delete profiles in this mode. Therefore, the
adslLineConfProfileIndexNext, adslLineConfProfileRowStatus, adslLineConfProfile, adslLineConfProfileIndexNext,
adlsLineAlarmProfile, adslLineAlarmConfProfileIndexNext, and adslLineConfProfileRowStatus, adlsLineAlarmProfile,
adslLineAlarmConfProfileIndexNext, and
adslLineAlarmConfProfileRowStatus objects are not used in this mode adslLineAlarmConfProfileRowStatus objects are not used in this mode
as each line has a unique, fixed profile that is not shared with as each line has a unique, fixed profile that is not shared with
other lines. other lines.
The figure below shows an example of this mode. In the example, ADSL The figure below shows an example of this mode. In the example, ADSL
lines '1', '2', and 'x' each have their own profiles. lines '1', '2', and 'x' each have their own profiles.
ADSL ifIndex ifTable Configuration Line ADSL ifIndex ifTable Configuration Line
Profile Table Profile Table
__________________________________________________________________ __________________________________________________________________
skipping to change at page 16, line 41 skipping to change at page 17, line 6
9. Definitions 9. Definitions
ADSL-LINE-MIB DEFINITIONS ::= BEGIN ADSL-LINE-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Counter32, MODULE-IDENTITY, OBJECT-TYPE, Counter32,
Gauge32, NOTIFICATION-TYPE, Integer32, Gauge32, NOTIFICATION-TYPE, Integer32,
OBJECT-IDENTITY, transmission FROM SNMPv2-SMI OBJECT-IDENTITY, transmission FROM SNMPv2-SMI
RowStatus, TruthValue FROM SNMPv2-TC RowStatus, TruthValue FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF
ifIndex FROM IF-MIB ifIndex FROM IF-MIB -- rfc2233
Utf8String FROM SYSAPPL-MIB Utf8String FROM SYSAPPL-MIB -- rfc2287
; ;
AdslLineProfileType ::= INTEGER AdslLineProfileType ::= INTEGER
adslMIB MODULE-IDENTITY adslMIB MODULE-IDENTITY
LAST-UPDATED "9808070000Z" LAST-UPDATED "9808070000Z"
ORGANIZATION "IETF ADSL-MIB WG" ORGANIZATION "IETF ADSL-MIB WG"
CONTACT-INFO CONTACT-INFO
" "
Gregory Bathrick Gregory Bathrick
AG Communication Systems AG Communication Systems
2500 W Utopia Rd. 2500 W Utopia Rd.
Phoenix, AZ 85027 USA Phoenix, AZ 85027 USA
skipping to change at page 17, line 22 skipping to change at page 17, line 32
2500 W Utopia Rd. 2500 W Utopia Rd.
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
John Burgess John Burgess
Predictive Systems, Inc. Predictive Systems, Inc.
25A Vreeland Rd. 25A Vreeland Rd.
Florham Park, NJ 07932 USA Florham Park, NJ 07932 USA
Tel: +1 201-301-5610 Tel: +1 973-301-5610
Fax: +1 201-301-5699 Fax: +1 973-301-5699
E-mail: jtburgess@predictive.com E-mail: jtburgess@predictive.com
" "
DESCRIPTION DESCRIPTION
"The MIB module defining objects for the management of a pair of "The MIB module defining objects for the management of a pair of
ADSL modems at each end of the ADSL line. Each such Line is ADSL modems at each end of the ADSL line. Each such Line is
indexed by ifIndex and appears as an interface on a central indexed by ifIndex and appears as an interface on a central
DSLAM (Digital Subscriber Line Access Mux.) Attributes on the DSLAM (Digital Subscriber Line Access Mux.) Attributes on the
ATUR are proxied by the DSLAM. ATUR are proxied by the DSLAM.
skipping to change at page 18, line 42 skipping to change at page 18, line 52
- clarified definition of channel block size, SNR - clarified definition of channel block size, SNR
Interleave Delay, Attenuation, and Output power. Interleave Delay, Attenuation, and Output power.
- corrected UNITS and SYNTAX of adsl rate objects, - corrected UNITS and SYNTAX of adsl rate objects,
Version#, VendorID. Version#, VendorID.
- added missing line activation objects. - added missing line activation objects.
General editorial cleanup. General editorial cleanup.
Added Security Statement (Dave Allan) Added Security Statement (Dave Allan)
" "
REVISION "9808071200Z"
DESCRIPTION
"General editorial cleanup.
"
::= { transmission 94 } ::= { transmission 94 }
adslLineMib OBJECT IDENTIFIER ::= { adslMIB 1 } adslLineMib OBJECT IDENTIFIER ::= { adslMIB 1 }
adslMibObjects OBJECT IDENTIFIER ::= { adslLineMib 1 } adslMibObjects OBJECT IDENTIFIER ::= { adslLineMib 1 }
adslLineTable OBJECT-TYPE adslLineTable OBJECT-TYPE
SYNTAX SEQUENCE OF AdslLineEntry SYNTAX SEQUENCE OF AdslLineEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
skipping to change at page 20, line 13 skipping to change at page 20, line 27
-- 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-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Defines the type of ADSL physical line "Defines the type of ADSL physical line
entity that exists, by defining whether and how entity that exists, by defining whether and how
the line is channelized. If the line is channelized, the line is channelized. If the line is channelized,
a value other than noChannel(1), this object the value will be other than noChannel(1). This
defines which channel type(s) are supported. object defines which channel type(s) are supported.
In the case that the line is channelized, the manager In the case that the line is channelized, the manager
can use the ifStackTable to determine the ifIndex for can use the ifStackTable to determine the ifIndex for
the associated channel(s)." the associated channel(s)."
::= { adslLineEntry 2 } ::= { adslLineEntry 2 }
adslLineSpecific OBJECT-TYPE adslLineSpecific OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 34, line 16 skipping to change at page 34, line 31
-- general 15 min interval information -- general 15 min interval information
-- --
adslAtucPerfValidIntervals OBJECT-TYPE adslAtucPerfValidIntervals OBJECT-TYPE
SYNTAX INTEGER(0..96) SYNTAX INTEGER(0..96)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of previous 15-minute intervals in the "Number of previous 15-minute intervals in the
adslAtucInterval Table for which valid data adslAtucInterval Table for which valid data
has been stored. This value will be equal to the has been stored. This value will be equal to the
maximum maximum # of intervals that are kept (n) unless the
number of intervals that are kept (n) unless the device device was brought online within the last (nx15)
was brought online within the last (nx15) minutes. In minutes. In the case where the agent is a proxy,
the case where the agent is a proxy, it is possible it is possible that some intervals are unavailable.
that some intervals are unavailable. In this case, In this case, this interval is the maximum interval
this interval is the maximum interval for which valid for which valid data is available."
data is available."
::= { adslAtucPerfDataEntry 7 } ::= { adslAtucPerfDataEntry 7 }
adslAtucPerfInvalidIntervals OBJECT-TYPE adslAtucPerfInvalidIntervals OBJECT-TYPE
SYNTAX INTEGER(0..96) SYNTAX INTEGER(0..96)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of 15 minute intervals which no valid data "The number of 15 minute intervals in which no valid
is available." data is available."
::= { adslAtucPerfDataEntry 8 } ::= { adslAtucPerfDataEntry 8 }
-- 15 min current performance group -- 15 min current performance group
-- --
adslAtucPerfCurr15MinTimeElapsed OBJECT-TYPE adslAtucPerfCurr15MinTimeElapsed OBJECT-TYPE
SYNTAX INTEGER(0..899) SYNTAX INTEGER(0..899)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 36, line 13 skipping to change at page 36, line 26
adslAtucPerfCurr15MinInits OBJECT-TYPE adslAtucPerfCurr15MinInits OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of the line initialization attempts in the "Count of the line initialization attempts in the
current 15 minute interval. Includes both successful current 15 minute interval. Includes both successful
and failed attempts." and failed attempts."
::= { adslAtucPerfDataEntry 15 } ::= { adslAtucPerfDataEntry 15 }
-- 1 Day current and previous performance group -- 1-day current and previous performance group
-- --
adslAtucPerfCurr1DayTimeElapsed OBJECT-TYPE adslAtucPerfCurr1DayTimeElapsed OBJECT-TYPE
SYNTAX INTEGER(0..86399) SYNTAX INTEGER(0..86399)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of seconds that have elapsed since the "Number of seconds that have elapsed since the
beginning of the current 1Day interval." beginning of the current 1-day interval."
::= { adslAtucPerfDataEntry 16 } ::= { adslAtucPerfDataEntry 16 }
adslAtucPerfCurr1DayLofs OBJECT-TYPE adslAtucPerfCurr1DayLofs OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
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 Loss of "Count of the number of seconds when there was Loss of
Framing during the current day as measured by Framing during the current day as measured by
skipping to change at page 38, line 8 skipping to change at page 38, line 21
SYNTAX INTEGER(0..899) SYNTAX INTEGER(0..899)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The time in the previous 1-day interval over which "The time in the previous 1-day interval over which
the performance monitoring information is actually the performance monitoring information is actually
counted. This value will normally be the same as the counted. This value will normally be the same as the
total interval duration except in a situation where total interval duration except in a situation where
performance monitoring data can not be collected performance monitoring data can not be collected
for any reason. Typically Elapsed 1-day Time will be for any reason. Typically Elapsed 1-day time will be
copied into Monitored Seconds when the 1-day roll-over copied into Monitored Seconds when the 1-day roll-over
occurs." occurs."
::= { adslAtucPerfDataEntry 23 } ::= { adslAtucPerfDataEntry 23 }
adslAtucPerfPrev1DayLofs OBJECT-TYPE adslAtucPerfPrev1DayLofs OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of seconds in the interval when there was "Count of seconds in the interval when there was
Loss of Framing within the most recent previous Loss of Framing within the most recent previous
1 day period." 1-day period."
::= { adslAtucPerfDataEntry 24 } ::= { adslAtucPerfDataEntry 24 }
adslAtucPerfPrev1DayLoss OBJECT-TYPE adslAtucPerfPrev1DayLoss OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of seconds in the interval when there was "Count of seconds in the interval when there was
Loss of Signal within the most recent previous Loss of Signal within the most recent previous
1 day period." 1-day period."
::= { adslAtucPerfDataEntry 25 } ::= { adslAtucPerfDataEntry 25 }
adslAtucPerfPrev1DayLols OBJECT-TYPE adslAtucPerfPrev1DayLols OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of seconds in the interval when there was "Count of seconds in the interval when there was
Loss of Link within the most recent previous Loss of Link within the most recent previous
1 day period." 1-day period."
::= { adslAtucPerfDataEntry 26 } ::= { adslAtucPerfDataEntry 26 }
adslAtucPerfPrev1DayLprs OBJECT-TYPE adslAtucPerfPrev1DayLprs OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of seconds in the interval when there was "Count of seconds in the interval when there was
Loss of Power within the most recent previous Loss of Power within the most recent previous
1 day period." 1-day period."
::= { adslAtucPerfDataEntry 27 } ::= { adslAtucPerfDataEntry 27 }
adslAtucPerfPrev1DayESs OBJECT-TYPE adslAtucPerfPrev1DayESs OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of Errored Seconds within the most recent "Count of Errored Seconds within the most recent
previous 1 day period. The errored second parameter is previous 1-day period. The errored second parameter is
a count of one-second intervals containing one or more a count of one-second intervals containing one or more
crc anomalies, or one or more los or sef defects." crc anomalies, or one or more los or sef defects."
::= { adslAtucPerfDataEntry 28 } ::= { adslAtucPerfDataEntry 28 }
adslAtucPerfPrev1DayInits OBJECT-TYPE adslAtucPerfPrev1DayInits OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of the line initialization attempts in the most "Count of the line initialization attempts in the most
recent previous 1 day period. Includes both successful recent previous 1-day period. Includes both successful
and failed attempts." and failed attempts."
::= { adslAtucPerfDataEntry 29 } ::= { adslAtucPerfDataEntry 29 }
adslAturPerfDataTable OBJECT-TYPE adslAturPerfDataTable OBJECT-TYPE
SYNTAX SEQUENCE OF AdslAturPerfDataEntry SYNTAX SEQUENCE OF AdslAturPerfDataEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table provides one row for each ATUR. "This table provides one row for each ATUR.
ADSL physical interfaces are ADSL physical interfaces are
skipping to change at page 41, line 49 skipping to change at page 42, line 14
that some intervals are unavailable. In this case, this that some intervals are unavailable. In this case, this
interval is the maximum interval for which valid data interval is the maximum interval for which valid data
is available." is available."
::= { adslAturPerfDataEntry 5 } ::= { adslAturPerfDataEntry 5 }
adslAturPerfInvalidIntervals OBJECT-TYPE adslAturPerfInvalidIntervals OBJECT-TYPE
SYNTAX INTEGER(0..96) SYNTAX INTEGER(0..96)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of 15 minute intervals which no valid data "The number of 15 minute intervals in which no valid
is available." data is available."
::= { adslAturPerfDataEntry 6 } ::= { adslAturPerfDataEntry 6 }
-- 15 min current performance group -- 15 min current performance group
-- --
adslAturPerfCurr15MinTimeElapsed OBJECT-TYPE adslAturPerfCurr15MinTimeElapsed OBJECT-TYPE
SYNTAX INTEGER(0..899) SYNTAX INTEGER(0..899)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Total elapsed seconds in this interval. "Total elapsed seconds in this interval.
A full interval is 900 seconds." A full interval is 900 seconds."
skipping to change at page 43, line 10 skipping to change at page 43, line 24
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of Errored Seconds in the current 15 minute "Count of Errored Seconds in the current 15 minute
interval. The errored second parameter is a count of interval. The errored second parameter is a count of
one-second intervals containing one or more crc one-second intervals containing one or more crc
anomalies, or one or more los or sef defects." anomalies, or one or more los or sef defects."
::= { adslAturPerfDataEntry 11 } ::= { adslAturPerfDataEntry 11 }
-- 1 Day current and previous performance group -- 1-day current and previous performance group
-- --
adslAturPerfCurr1DayTimeElapsed OBJECT-TYPE adslAturPerfCurr1DayTimeElapsed OBJECT-TYPE
SYNTAX INTEGER(0..86399) SYNTAX INTEGER(0..86399)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of seconds that have elapsed since the "Number of seconds that have elapsed since the
beginning of the current 1Day interval." beginning of the current 1-day interval."
::= { adslAturPerfDataEntry 12 } ::= { adslAturPerfDataEntry 12 }
adslAturPerfCurr1DayLofs OBJECT-TYPE adslAturPerfCurr1DayLofs OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
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 Loss "Count of the number of seconds when there was Loss
of Framing during the current day as measured by of Framing during the current day as measured by
skipping to change at page 44, line 32 skipping to change at page 44, line 46
SYNTAX INTEGER(0..899) SYNTAX INTEGER(0..899)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The time in the previous 1-day interval over which "The time in the previous 1-day interval over which
the performance monitoring information is actually the performance monitoring information is actually
counted. This value will normally be the same as the counted. This value will normally be the same as the
total interval duration except in a situation where total interval duration except in a situation where
performance monitoring data can not be collected performance monitoring data can not be collected
for any reason. Typically Elapsed 1-day Time will be for any reason. Typically Elapsed 1-day time will be
copied into Monitored Seconds when the 1-day roll-over copied into Monitored Seconds when the 1-day roll-over
occurs." occurs."
::= { adslAturPerfDataEntry 17 } ::= { adslAturPerfDataEntry 17 }
adslAturPerfPrev1DayLofs OBJECT-TYPE adslAturPerfPrev1DayLofs OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of seconds in the interval when there was "Count of seconds in the interval when there was
Loss of Framing within the most recent previous Loss of Framing within the most recent previous
1 day period." 1-day period."
::= { adslAturPerfDataEntry 18 } ::= { adslAturPerfDataEntry 18 }
adslAturPerfPrev1DayLoss OBJECT-TYPE adslAturPerfPrev1DayLoss OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of seconds in the interval when there was "Count of seconds in the interval when there was
Loss of Signal within the most recent previous Loss of Signal within the most recent previous
1 day period." 1-day period."
::= { adslAturPerfDataEntry 19 } ::= { adslAturPerfDataEntry 19 }
adslAturPerfPrev1DayLprs OBJECT-TYPE adslAturPerfPrev1DayLprs OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of seconds in the interval when there was "Count of seconds in the interval when there was
Loss of Power within the most recent previous Loss of Power within the most recent previous
1 day period." 1-day period."
::= { adslAturPerfDataEntry 20 } ::= { adslAturPerfDataEntry 20 }
adslAturPerfPrev1DayESs OBJECT-TYPE adslAturPerfPrev1DayESs OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of Errored Seconds within the most recent "Count of Errored Seconds within the most recent
previous 1 day period. The errored second parameter is previous 1-day period. The errored second parameter is
a count of one-second intervals containing one or more a count of one-second intervals containing one or more
crc anomalies, or one or more los or sef defects." crc anomalies, or one or more los or sef defects."
::= { adslAturPerfDataEntry 21 } ::= { adslAturPerfDataEntry 21 }
adslAtucIntervalTable OBJECT-TYPE adslAtucIntervalTable OBJECT-TYPE
SYNTAX SEQUENCE OF AdslAtucIntervalEntry SYNTAX SEQUENCE OF AdslAtucIntervalEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table provides one row for each ATUC "This table provides one row for each ATUC
skipping to change at page 52, line 4 skipping to change at page 52, line 18
"Number of previous 15-minute intervals in the "Number of previous 15-minute intervals in the
adslAtucChanIntervalTable Table for which valid data adslAtucChanIntervalTable Table for which valid data
has been stored. This value will be equal to the max has been stored. This value will be equal to the max
number of intervals that are kept (n) unless the device number of intervals that are kept (n) unless the device
was brought online within the last (nx15) minutes. In was brought online within the last (nx15) minutes. In
the case where the agent is a proxy, it is possible the case where the agent is a proxy, it is possible
that some intervals are unavailable. In this case, that some intervals are unavailable. In this case,
this interval is the maximum interval for which valid this interval is the maximum interval for which valid
data is available." data is available."
::= { adslAtucChanPerfDataEntry 5 } ::= { adslAtucChanPerfDataEntry 5 }
adslAtucChanPerfInvalidIntervals OBJECT-TYPE adslAtucChanPerfInvalidIntervals OBJECT-TYPE
SYNTAX INTEGER(0..96) SYNTAX INTEGER(0..96)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of 15 minute intervals which no valid data "The number of 15 minute intervals in which no valid
data
is available." is available."
::= { adslAtucChanPerfDataEntry 6 } ::= { adslAtucChanPerfDataEntry 6 }
-- 15 min current performance group -- 15 min current performance group
-- --
adslAtucChanPerfCurr15MinTimeElapsed OBJECT-TYPE adslAtucChanPerfCurr15MinTimeElapsed OBJECT-TYPE
SYNTAX INTEGER(0..899) SYNTAX INTEGER(0..899)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 53, line 14 skipping to change at page 53, line 31
adslAtucChanPerfCurr15MinUncorrectBlks OBJECT-TYPE adslAtucChanPerfCurr15MinUncorrectBlks OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of all blocks received with uncorrectable "Count of all blocks received with uncorrectable
errors on this channel within the current 15 minute errors on this channel within the current 15 minute
interval." interval."
::= { adslAtucChanPerfDataEntry 11 } ::= { adslAtucChanPerfDataEntry 11 }
-- 1 Day current and previous performance group -- 1-day current and previous performance group
-- --
adslAtucChanPerfCurr1DayTimeElapsed OBJECT-TYPE adslAtucChanPerfCurr1DayTimeElapsed OBJECT-TYPE
SYNTAX INTEGER(0..86399) SYNTAX INTEGER(0..86399)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of seconds that have elapsed since the "Number of seconds that have elapsed since the
beginning of the current 1Day interval." beginning of the current 1-day interval."
::= { adslAtucChanPerfDataEntry 12 } ::= { adslAtucChanPerfDataEntry 12 }
adslAtucChanPerfCurr1DayReceivedBlks OBJECT-TYPE adslAtucChanPerfCurr1DayReceivedBlks OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of all encoded blocks received on this "Count of all encoded blocks received on this
channel during the current day as measured by channel during the current day as measured by
adslAtucChanPerfCurr1DayTimeElapsed." adslAtucChanPerfCurr1DayTimeElapsed."
skipping to change at page 54, line 29 skipping to change at page 54, line 45
SYNTAX INTEGER(0..86399) SYNTAX INTEGER(0..86399)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The time in the previous 1-day interval over which "The time in the previous 1-day interval over which
the performance monitoring information is actually the performance monitoring information is actually
counted. This value will normally be the same as the counted. This value will normally be the same as the
total interval duration except in a situation where total interval duration except in a situation where
performance monitoring information can not be collected performance monitoring information can not be collected
for any reason. Typically Elapsed 1-day Time will be for any reason. Typically Elapsed 1-day time will be
copied into Monitored Seconds when the 1-day roll-over copied into Monitored Seconds when the 1-day roll-over
occurs." occurs."
::= { adslAtucChanPerfDataEntry 17 } ::= { adslAtucChanPerfDataEntry 17 }
adslAtucChanPerfPrev1DayReceivedBlks OBJECT-TYPE adslAtucChanPerfPrev1DayReceivedBlks OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of all encoded blocks received on this "Count of all encoded blocks received on this
channel within the most recent previous 1 day channel within the most recent previous 1-day
period." period."
::= { adslAtucChanPerfDataEntry 18 } ::= { adslAtucChanPerfDataEntry 18 }
adslAtucChanPerfPrev1DayTransmittedBlks OBJECT-TYPE adslAtucChanPerfPrev1DayTransmittedBlks OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of all encoded blocks transmitted on this "Count of all encoded blocks transmitted on this
channel within the most recent previous 1 day channel within the most recent previous 1-day
period." period."
::= { adslAtucChanPerfDataEntry 19 } ::= { adslAtucChanPerfDataEntry 19 }
adslAtucChanPerfPrev1DayCorrectedBlks OBJECT-TYPE adslAtucChanPerfPrev1DayCorrectedBlks OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of all blocks received with errors that were "Count of all blocks received with errors that were
corrected on this channel within the most recent corrected on this channel within the most recent
previous 1 day period." previous 1-day period."
::= { adslAtucChanPerfDataEntry 20 } ::= { adslAtucChanPerfDataEntry 20 }
adslAtucChanPerfPrev1DayUncorrectBlks OBJECT-TYPE adslAtucChanPerfPrev1DayUncorrectBlks OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of all blocks received with uncorrectable "Count of all blocks received with uncorrectable
errors on this channel within the most recent previous errors on this channel within the most recent previous
1 day period." 1-day period."
::= { adslAtucChanPerfDataEntry 21 } ::= { adslAtucChanPerfDataEntry 21 }
adslAturChanPerfDataTable OBJECT-TYPE adslAturChanPerfDataTable OBJECT-TYPE
SYNTAX SEQUENCE OF AdslAturChanPerfDataEntry SYNTAX SEQUENCE OF AdslAturChanPerfDataEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table provides one row for each ATUR channel. "This table provides one row for each ATUR channel.
ADSL channel interfaces are those ifEntries ADSL channel interfaces are those ifEntries
where ifType is equal to adslInterleave(124) where ifType is equal to adslInterleave(124)
skipping to change at page 57, line 39 skipping to change at page 58, line 6
that some intervals are unavailable. In this case, that some intervals are unavailable. In this case,
this interval is the maximum interval for which valid this interval is the maximum interval for which valid
data is available." data is available."
::= { adslAturChanPerfDataEntry 5 } ::= { adslAturChanPerfDataEntry 5 }
adslAturChanPerfInvalidIntervals OBJECT-TYPE adslAturChanPerfInvalidIntervals OBJECT-TYPE
SYNTAX INTEGER(0..96) SYNTAX INTEGER(0..96)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of 15 minute intervals which no valid data "The number of 15 minute intervals in which no valid
is available." data is available."
::= { adslAturChanPerfDataEntry 6 } ::= { adslAturChanPerfDataEntry 6 }
-- 15 min current performance group -- 15 min current performance group
-- --
adslAturChanPerfCurr15MinTimeElapsed OBJECT-TYPE adslAturChanPerfCurr15MinTimeElapsed OBJECT-TYPE
SYNTAX INTEGER(0..899) SYNTAX INTEGER(0..899)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 58, line 46 skipping to change at page 59, line 12
adslAturChanPerfCurr15MinUncorrectBlks OBJECT-TYPE adslAturChanPerfCurr15MinUncorrectBlks OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of all blocks received with uncorrectable "Count of all blocks received with uncorrectable
errors on this channel within the current 15 minute errors on this channel within the current 15 minute
interval." interval."
::= { adslAturChanPerfDataEntry 11 } ::= { adslAturChanPerfDataEntry 11 }
-- 1 Day current and previous performance group -- 1-day current and previous performance group
-- --
adslAturChanPerfCurr1DayTimeElapsed OBJECT-TYPE adslAturChanPerfCurr1DayTimeElapsed OBJECT-TYPE
SYNTAX INTEGER(0..86399) SYNTAX INTEGER(0..86399)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of seconds that have elapsed since the "Number of seconds that have elapsed since the
beginning of the current 1Day interval." beginning of the current 1-day interval."
::= { adslAturChanPerfDataEntry 12 } ::= { adslAturChanPerfDataEntry 12 }
adslAturChanPerfCurr1DayReceivedBlks OBJECT-TYPE adslAturChanPerfCurr1DayReceivedBlks OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of all encoded blocks received on this "Count of all encoded blocks received on this
channel during the current day as measured by channel during the current day as measured by
adslAturChanPerfCurr1DayTimeElapsed." adslAturChanPerfCurr1DayTimeElapsed."
skipping to change at page 60, line 13 skipping to change at page 60, line 28
SYNTAX INTEGER(0..86399) SYNTAX INTEGER(0..86399)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The time in the previous 1-day interval over which "The time in the previous 1-day interval over which
the performance monitoring information is actually the performance monitoring information is actually
counted. This value will normally be the same as the counted. This value will normally be the same as the
total interval duration except in a situation where total interval duration except in a situation where
performance monitoring information can not be collected performance monitoring information can not be collected
for any reason. Typically Elapsed 1-day Time will be for any reason. Typically Elapsed 1-day time will be
copied into Monitored Seconds when the 1-day roll-over copied into Monitored Seconds when the 1-day roll-over
occurs." occurs."
::= { adslAturChanPerfDataEntry 17 } ::= { adslAturChanPerfDataEntry 17 }
adslAturChanPerfPrev1DayReceivedBlks OBJECT-TYPE adslAturChanPerfPrev1DayReceivedBlks OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of all encoded blocks received on this "Count of all encoded blocks received on this
channel within the most recent previous 1 day channel within the most recent previous 1-day
period." period."
::= { adslAturChanPerfDataEntry 18 } ::= { adslAturChanPerfDataEntry 18 }
adslAturChanPerfPrev1DayTransmittedBlks OBJECT-TYPE adslAturChanPerfPrev1DayTransmittedBlks OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of all encoded blocks transmitted on this "Count of all encoded blocks transmitted on this
channel within the most recent previous 1 day channel within the most recent previous 1-day
period." period."
::= { adslAturChanPerfDataEntry 19 } ::= { adslAturChanPerfDataEntry 19 }
adslAturChanPerfPrev1DayCorrectedBlks OBJECT-TYPE adslAturChanPerfPrev1DayCorrectedBlks OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of all blocks received with errors that were "Count of all blocks received with errors that were
corrected on this channel within the most recent corrected on this channel within the most recent
previous 1 day period." previous 1-day period."
::= { adslAturChanPerfDataEntry 20 } ::= { adslAturChanPerfDataEntry 20 }
adslAturChanPerfPrev1DayUncorrectBlks OBJECT-TYPE adslAturChanPerfPrev1DayUncorrectBlks OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of all blocks received with uncorrectable "Count of all blocks received with uncorrectable
errors on this channel within the most recent previous errors on this channel within the most recent previous
1 day period." 1-day period."
::= { adslAturChanPerfDataEntry 21 } ::= { adslAturChanPerfDataEntry 21 }
adslAtucChanIntervalTable OBJECT-TYPE adslAtucChanIntervalTable OBJECT-TYPE
SYNTAX SEQUENCE OF AdslAtucChanIntervalEntry SYNTAX SEQUENCE OF AdslAtucChanIntervalEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table provides one row for each ATUC channel's "This table provides one row for each ATUC channel's
performance data collection interval. performance data collection interval.
ADSL channel interfaces are those ifEntries ADSL channel interfaces are those ifEntries
skipping to change at page 66, line 46 skipping to change at page 67, line 11
fixed (1), -- no rate adaptation fixed (1), -- no rate adaptation
adaptAtStartup (2), -- perform rate adaptation adaptAtStartup (2), -- perform rate adaptation
-- only at initialization -- only at initialization
adaptAtRuntime (3) -- perform rate adaptation at adaptAtRuntime (3) -- perform rate adaptation at
-- any time (i.e., RADSL) -- any time (i.e., RADSL)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Defines what form of transmit rate adaptation is "Defines what form of transmit rate adaptation is
configured on this modem. See WT008 for more configured on this modem. See ADSL Forum TR-005 [3]
information." for more information."
::= { adslLineConfProfileEntry 2 } ::= { adslLineConfProfileEntry 2 }
adslAtucConfRateChanRatio OBJECT-TYPE adslAtucConfRateChanRatio OBJECT-TYPE
SYNTAX INTEGER(0..100) SYNTAX INTEGER(0..100)
UNITS "%" UNITS "%"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Configured allocation ratio of excess transmit "Configured allocation ratio of excess transmit
bandwidth between fast and interleaved channels. Only bandwidth between fast and interleaved channels. Only
skipping to change at page 70, line 42 skipping to change at page 71, line 7
fixed (1), -- no rate adaptation fixed (1), -- no rate adaptation
adaptAtStartup (2), -- perform rate adaptation adaptAtStartup (2), -- perform rate adaptation
-- only at initialization -- only at initialization
adaptAtRuntime (3) -- perform rate adaptation at adaptAtRuntime (3) -- perform rate adaptation at
-- any time (i.e., RADSL) -- any time (i.e., RADSL)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Defines what form of transmit rate adaptation is "Defines what form of transmit rate adaptation is
configured on this modem. See ADSL Forum TR-005 configured on this modem. See ADSL Forum TR-005 [3]
for more information." for more information."
::= { adslLineConfProfileEntry 16 } ::= { adslLineConfProfileEntry 16 }
adslAturConfRateChanRatio OBJECT-TYPE adslAturConfRateChanRatio OBJECT-TYPE
SYNTAX INTEGER(0..100) SYNTAX INTEGER(0..100)
UNITS "%" UNITS "%"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Configured allocation ratio of excess transmit "Configured allocation ratio of excess transmit
skipping to change at page 76, line 32 skipping to change at page 76, line 43
"This object is used by the line alarm configuration "This object is used by the line alarm configuration
table in order to identify a row of this table" table in order to identify a row of this table"
::= { adslLineAlarmConfProfileEntry 1} ::= { adslLineAlarmConfProfileEntry 1}
adslAtucThresh15MinLofs OBJECT-TYPE adslAtucThresh15MinLofs OBJECT-TYPE
SYNTAX INTEGER(0..900) SYNTAX INTEGER(0..900)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of Loss of Frame Seconds, "The number of Loss of Frame Seconds
encountered by an ADSL interface within any given 15 encountered by an ADSL interface within any given 15
minutes performance data collection period, which minutes performance data collection period, which
causes the SNMP agent to send an causes the SNMP agent to send an
adslAtucPerfLofsThreshTrap. adslAtucPerfLofsThreshTrap.
Limit of one trap will be sent for any one interval. A Limit of one trap will be sent for any one interval. A
value of '0' will disable the trap." value of '0' will disable the trap."
::= { adslLineAlarmConfProfileEntry 2} ::= { adslLineAlarmConfProfileEntry 2}
adslAtucThresh15MinLoss OBJECT-TYPE adslAtucThresh15MinLoss OBJECT-TYPE
SYNTAX INTEGER(0..900) SYNTAX INTEGER(0..900)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of Loss of Signal Seconds, "The number of Loss of Signal Seconds
encountered by an ADSL interface within any given 15 encountered by an ADSL interface within any given 15
minutes performance data collection period, which minutes performance data collection period, which
causes the SNMP agent to send an causes the SNMP agent to send an
adslAtucPerfLossThreshTrap. adslAtucPerfLossThreshTrap.
Limit of one trap will be sent for any one interval. Limit of one trap will be sent for any one interval.
A value of '0' will disable the trap." A value of '0' will disable the trap."
::= { adslLineAlarmConfProfileEntry 3} ::= { adslLineAlarmConfProfileEntry 3}
adslAtucThresh15MinLols OBJECT-TYPE adslAtucThresh15MinLols OBJECT-TYPE
SYNTAX INTEGER(0..900) SYNTAX INTEGER(0..900)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of Loss of Link Seconds, "The number of Loss of Link Seconds
encountered by an ADSL interface within any given 15 encountered by an ADSL interface within any given 15
minutes performance data collection period, which minutes performance data collection period, which
causes the SNMP agent to send an causes the SNMP agent to send an
adslAtucPerfLolsThreshTrap. Limit of one trap will adslAtucPerfLolsThreshTrap. Limit of one trap will
be sent for any one interval. A value of '0' will be sent for any one interval. A value of '0' will
disable the trap." disable the trap."
::= { adslLineAlarmConfProfileEntry 4} ::= { adslLineAlarmConfProfileEntry 4}
adslAtucThresh15MinLprs OBJECT-TYPE adslAtucThresh15MinLprs OBJECT-TYPE
SYNTAX INTEGER(0..900) SYNTAX INTEGER(0..900)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of Loss of Power Seconds, "The number of Loss of Power Seconds
encountered by an ADSL interface within any given 15 encountered by an ADSL interface within any given 15
minutes performance data collection period, which minutes performance data collection period, which
causes the SNMP agent to send an causes the SNMP agent to send an
adslAtucPerfLprsThreshTrap. adslAtucPerfLprsThreshTrap.
Limit of one trap will be sent for any one interval. Limit of one trap will be sent for any one interval.
A value of '0' will disable the trap." A value of '0' will disable the trap."
::= { adslLineAlarmConfProfileEntry 5} ::= { adslLineAlarmConfProfileEntry 5}
adslAtucThresh15MinESs OBJECT-TYPE adslAtucThresh15MinESs OBJECT-TYPE
SYNTAX INTEGER(0..900) SYNTAX INTEGER(0..900)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of Errored Seconds, "The number of Errored Seconds
encountered by an ADSL interface within any given 15 encountered by an ADSL interface within any given 15
minutes performance data collection period, which minutes performance data collection period, which
causes the SNMP agent to send an causes the SNMP agent to send an
adslAtucPerfESsThreshTrap. adslAtucPerfESsThreshTrap.
Limit of one trap will be sent for any one interval. Limit of one trap will be sent for any one interval.
A value of '0' will disable the trap." A value of '0' will disable the trap."
::= { adslLineAlarmConfProfileEntry 6} ::= { adslLineAlarmConfProfileEntry 6}
adslAtucThreshFastRateUp OBJECT-TYPE adslAtucThreshFastRateUp OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "bps" UNITS "bps"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Applies to 'Fast' channels only. "Applies to 'Fast' channels only.
skipping to change at page 79, line 30 skipping to change at page 79, line 41
object is defaulted disable(2)." object is defaulted disable(2)."
DEFVAL { disable } DEFVAL { disable }
::= { adslLineAlarmConfProfileEntry 11 } ::= { adslLineAlarmConfProfileEntry 11 }
adslAturThresh15MinLofs OBJECT-TYPE adslAturThresh15MinLofs OBJECT-TYPE
SYNTAX INTEGER(0..900) SYNTAX INTEGER(0..900)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of Loss of Frame Seconds, "The number of Loss of Frame Seconds
encountered by an ADSL interface within any given 15 encountered by an ADSL interface within any given 15
minutes performance data collection period, which minutes performance data collection period, which
causes the SNMP agent to send an causes the SNMP agent to send an
adslAtucPerfLofsThreshTrap. adslAtucPerfLofsThreshTrap.
Limit of one trap will be sent for any one interval. Limit of one trap will be sent for any one interval.
A value of '0' will disable the trap." A value of '0' will disable the trap."
::= { adslLineAlarmConfProfileEntry 12 } ::= { adslLineAlarmConfProfileEntry 12 }
adslAturThresh15MinLoss OBJECT-TYPE adslAturThresh15MinLoss OBJECT-TYPE
SYNTAX INTEGER(0..900) SYNTAX INTEGER(0..900)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of Loss of Signal Seconds, "The number of Loss of Signal Seconds
encountered by an ADSL interface within any given 15 encountered by an ADSL interface within any given 15
minutes performance data collection period, which minutes performance data collection period, which
causes the SNMP agent to send an causes the SNMP agent to send an
adslAtucPerfLossThreshTrap. adslAtucPerfLossThreshTrap.
Limit of one trap will be sent for any one interval. Limit of one trap will be sent for any one interval.
A value of '0' will disable the trap." A value of '0' will disable the trap."
::= { adslLineAlarmConfProfileEntry 13 } ::= { adslLineAlarmConfProfileEntry 13 }
adslAturThresh15MinLprs OBJECT-TYPE adslAturThresh15MinLprs OBJECT-TYPE
SYNTAX INTEGER(0..900) SYNTAX INTEGER(0..900)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of Loss of Power Seconds, "The number of Loss of Power Seconds
encountered by an ADSL interface within any given 15 encountered by an ADSL interface within any given 15
minutes performance data collection period, which minutes performance data collection period, which
causes the SNMP agent to send an causes the SNMP agent to send an
adslAtucPerfLprsThreshTrap. adslAtucPerfLprsThreshTrap.
Limit of one trap will be sent for any one interval. Limit of one trap will be sent for any one interval.
A value of '0' will disable the trap." A value of '0' will disable the trap."
::= { adslLineAlarmConfProfileEntry 14 } ::= { adslLineAlarmConfProfileEntry 14 }
adslAturThresh15MinESs OBJECT-TYPE adslAturThresh15MinESs OBJECT-TYPE
SYNTAX INTEGER(0..900) SYNTAX INTEGER(0..900)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of Errored Seconds, "The number of Errored Seconds
encountered by an ADSL interface within any given 15 encountered by an ADSL interface within any given 15
minutes performance data collection period, which minutes performance data collection period, which
causes the SNMP agent to send an causes the SNMP agent to send an
adslAtucPerfESsThreshTrap. adslAtucPerfESsThreshTrap.
Limit of one trap will be sent for any one interval. Limit of one trap will be sent for any one interval.
A value of '0' will disable the trap." A value of '0' will disable the trap."
::= { adslLineAlarmConfProfileEntry 15 } ::= { adslLineAlarmConfProfileEntry 15 }
adslAturThreshFastRateUp OBJECT-TYPE adslAturThreshFastRateUp OBJECT-TYPE
skipping to change at page 82, line 7 skipping to change at page 82, line 17
DESCRIPTION DESCRIPTION
"This object is used to create a new row or modify or "This object is used to create a new row or modify or
delete an existing row in this table. delete an existing row in this table.
If the implementator of this MIB has chosen not If the implementator of this MIB has chosen not
to implement 'dynamic assignment' of profiles, this to implement 'dynamic assignment' of profiles, this
object is not useful and should return noSuchObject object is not useful and should return noSuchObject
upon SNMP request." upon SNMP request."
::= { adslLineAlarmConfProfileEntry 20 } ::= { adslLineAlarmConfProfileEntry 20 }
-- Line Code Specific Tables
-- These are place holders for the Line Code Specific MIBs
-- once they become available.
adslLCSTable OBJECT IDENTIFIER ::= { adslMibObjects 18 }
-- conformance information -- conformance information
adslConformance OBJECT IDENTIFIER ::= { adslLineMib 2 } adslConformance OBJECT IDENTIFIER ::= { adslLineMib 2 }
adslGroups OBJECT IDENTIFIER ::= { adslConformance 1 } adslGroups OBJECT IDENTIFIER ::= { adslConformance 1 }
adslCompliances OBJECT IDENTIFIER ::= { adslConformance 2 } adslCompliances OBJECT IDENTIFIER ::= { adslConformance 2 }
-- compliance statements -- compliance statements
adslLineMibCompliance MODULE-COMPLIANCE adslLineMibCompliance MODULE-COMPLIANCE
skipping to change at page 83, line 4 skipping to change at page 83, line 22
DESCRIPTION DESCRIPTION
"This group is optional." "This group is optional."
GROUP adslAtucChanPerformanceGroup GROUP adslAtucChanPerformanceGroup
DESCRIPTION DESCRIPTION
"This group is optional." "This group is optional."
GROUP adslAturChanPerformanceGroup GROUP adslAturChanPerformanceGroup
DESCRIPTION DESCRIPTION
"This group is optional." "This group is optional."
OBJECT adslAtucIntervalNumber OBJECT adslAtucIntervalNumber
SYNTAX INTEGER (1) SYNTAX INTEGER (1..1)
DESCRIPTION DESCRIPTION
"It is allowable to implement only one ATU-C 15min "It is allowable to implement only one ATU-C 15-minute
performance interval." performance interval."
OBJECT adslAturIntervalNumber OBJECT adslAturIntervalNumber
SYNTAX INTEGER (1) SYNTAX INTEGER (1..1)
DESCRIPTION DESCRIPTION
"It is allowable to implement only one ATU-R 15min "It is allowable to implement only one ATU-R 15-minute
performance interval." performance interval."
OBJECT adslAtucIntervalNumber OBJECT adslAtucIntervalNumber
SYNTAX INTEGER (1) SYNTAX INTEGER (1..1)
DESCRIPTION DESCRIPTION
"It is allowable to implement only one ATU-C "It is allowable to implement only one ATU-C
channel 15min performance interval." channel 15-minute performance interval."
OBJECT adslAtucIntervalNumber OBJECT adslAtucIntervalNumber
SYNTAX INTEGER (1) SYNTAX INTEGER (1..1)
DESCRIPTION DESCRIPTION
"It is allowable to implement only one ATU-R "It is allowable to implement only one ATU-R
channel 15min performance interval." channel 15-minute performance interval."
::= { adslCompliances 1 } ::= { adslCompliances 1 }
-- units of conformance -- units of conformance
adslLineGroup OBJECT-GROUP adslLineGroup OBJECT-GROUP
OBJECTS { OBJECTS {
adslLineCoding, adslLineType, adslLineSpecific adslLineCoding, adslLineType, adslLineSpecific
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 85, line 9 skipping to change at page 85, line 28
adslAtucPerfPrev1DayLofs, adslAtucPerfPrev1DayLoss, adslAtucPerfPrev1DayLofs, adslAtucPerfPrev1DayLoss,
adslAtucPerfPrev1DayLols, adslAtucPerfPrev1DayLprs, adslAtucPerfPrev1DayLols, adslAtucPerfPrev1DayLprs,
adslAtucPerfPrev1DayESs, adslAtucPerfPrev1DayInits, adslAtucPerfPrev1DayESs, adslAtucPerfPrev1DayInits,
adslAtucIntervalLofs, adslAtucIntervalLoss, adslAtucIntervalLofs, adslAtucIntervalLoss,
adslAtucIntervalLols, adslAtucIntervalLprs, adslAtucIntervalLols, adslAtucIntervalLprs,
adslAtucIntervalESs, adslAtucIntervalInits, adslAtucIntervalESs, adslAtucIntervalInits,
adslAtucIntervalValidData adslAtucIntervalValidData
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing current 15min, "A collection of objects providing current 15-minute,
1 day; and previous 1 day performance counts on 1-day; and previous 1-day performance counts on
ADSL Line (ATU-C end) ." ADSL Line (ATU-C end) ."
::= { adslGroups 5 } ::= { adslGroups 5 }
adslAturPhysPerfRawCounterGroup OBJECT-GROUP adslAturPhysPerfRawCounterGroup OBJECT-GROUP
OBJECTS { OBJECTS {
adslAturPerfLofs, adslAturPerfLoss, adslAturPerfLofs, adslAturPerfLoss,
adslAturPerfLprs, adslAturPerfESs adslAturPerfLprs, adslAturPerfESs
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 85, line 44 skipping to change at page 86, line 15
adslAturPerfCurr1DayLprs, adslAturPerfCurr1DayESs, adslAturPerfCurr1DayLprs, adslAturPerfCurr1DayESs,
adslAturPerfPrev1DayMoniSecs, adslAturPerfPrev1DayMoniSecs,
adslAturPerfPrev1DayLofs, adslAturPerfPrev1DayLoss, adslAturPerfPrev1DayLofs, adslAturPerfPrev1DayLoss,
adslAturPerfPrev1DayLprs, adslAturPerfPrev1DayESs, adslAturPerfPrev1DayLprs, adslAturPerfPrev1DayESs,
adslAturIntervalLofs, adslAturIntervalLofs,
adslAturIntervalLoss, adslAturIntervalLprs, adslAturIntervalLoss, adslAturIntervalLprs,
adslAturIntervalESs, adslAturIntervalValidData adslAturIntervalESs, adslAturIntervalValidData
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing current 15min, "A collection of objects providing current 15-minute,
1 day; and previous 1 day performance counts on 1-day; and previous 1-day performance counts on
ADSL Line (ATU-R end)." ADSL Line (ATU-R end)."
::= { adslGroups 7 } ::= { adslGroups 7 }
adslAtucChanPerformanceGroup OBJECT-GROUP adslAtucChanPerformanceGroup OBJECT-GROUP
OBJECTS { OBJECTS {
adslAtucChanReceivedBlks, adslAtucChanReceivedBlks,
adslAtucChanTransmittedBlks, adslAtucChanTransmittedBlks,
adslAtucChanCorrectedBlks, adslAtucChanCorrectedBlks,
adslAtucChanUncorrectBlks, adslAtucChanUncorrectBlks,
adslAtucChanPerfValidIntervals, adslAtucChanPerfValidIntervals,
skipping to change at page 91, line 20 skipping to change at page 91, line 39
aturSelfTest (2) aturSelfTest (2)
" "
::= { adslLineMib 4 } ::= { adslLineMib 4 }
adslTestCodes OBJECT IDENTIFIER ::= { adslLineMib 5 } adslTestCodes OBJECT IDENTIFIER ::= { adslLineMib 5 }
END END
10. Acknowledgments 10. Acknowledgments
Much technical information for this document was derived from ADSL ADSL Forum's TR006[9] editors:
Forum's TR006[9]. The original editors of this reference document
were:
Gregory Bathrick (AG Communication Systems) Gregory Bathrick (AG Communication Systems)
John Burgess (Predictive Systems) John Burgess (Predictive Systems)
The technical leader of the ADSL Forum network management working The technical leader of the ADSL Forum network management working
group was: group was:
Chi-Lin Tom (AFC) Chi-Lin Tom (AFC)
Contributions were received from the following contributors. Contributions were received from the following contributors.
Rajesh Abbi (Alcatel) Rajesh Abbi (Alcatel)
skipping to change at page 91, line 36 skipping to change at page 92, line 4
John Burgess (Predictive Systems) John Burgess (Predictive Systems)
The technical leader of the ADSL Forum network management working The technical leader of the ADSL Forum network management working
group was: group was:
Chi-Lin Tom (AFC) Chi-Lin Tom (AFC)
Contributions were received from the following contributors. Contributions were received from the following contributors.
Rajesh Abbi (Alcatel) Rajesh Abbi (Alcatel)
John Burgess (Predictive Systems)
Gregory Bathrick (AG Communication Systems)
Gail Cone (Amati)
Peter Duffy (Atlantech)
Kevin Godfrey (Motorola) Kevin Godfrey (Motorola)
Bill Hong (Diamond Lane)
Ron Knipper (Diamond Lane) Bob Jenness (Siemens)
Lars Johansson (Ericsson)
Tsu Kai Lu (DSC) Tsu Kai Lu (DSC)
Gigi Karmous-Edwards (Pulsecom) Gigi Karmous-Edwards (Pulsecom)
Ron Knipper (Diamond Lane)
Adil Masood (AG Communication Systems)
Padmore Peterson (BT)
Anna Salguero (SBC) Anna Salguero (SBC)
Lars Johansson (Ericsson)
Gail Cone (Amati)
Donald Simon (Motorola) Donald Simon (Motorola)
Frank Van der Putten (Alcatel)
Bob Jenness (Siemens)
John Stehman (Diamond Lane) John Stehman (Diamond Lane)
Chuck Storry (Newbridge) Chuck Storry (Newbridge)
Bill Hong (Diamond Lane)
John Burgess (Predictive Systems)
Gregory Bathrick (AG Communication Systems)
Chi-Lin Tom (AFC) Chi-Lin Tom (AFC)
Frank Van der Putten (Alcatel)
Marc Van Vlimmeren (Alcatel) Marc Van Vlimmeren (Alcatel)
Peter Duffy (Atlantech)
Padmore Peterson (BT)
11. References 11. References
[1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and [1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and
S. Waldbusser, "Structure of Management Information for Version S. Waldbusser, "Structure of Management Information for Version
2 of the Simple Network Management Protocol (SNMPv2)", 2 of the Simple Network Management Protocol (SNMPv2)",
RFC 1902, January 1996. RFC 1902, January 1996.
[2] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [2] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Textual Conventions for SNMPv2", RFC 1903, SNMP Research, "Textual Conventions for SNMPv2", RFC 1903, SNMP Research,
Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc.,
skipping to change at page 96, line 4 skipping to change at page 95, line 46
5. Introduction ........................................... 3 5. Introduction ........................................... 3
6. Relationship of the ADSL LINE MIB with standard MIBs ... 3 6. Relationship of the ADSL LINE MIB with standard MIBs ... 3
7. Conventions used in the MIB ............................ 9 7. Conventions used in the MIB ............................ 9
8. Conformance and Compliance ............................. 16 8. Conformance and Compliance ............................. 16
9. Definitions ............................................ 16 9. Definitions ............................................ 16
10. Acknowledgments ........................................ 90
11. References ............................................. 92 10. Acknowledgments ........................................ 91
11. References ............................................. 92
12. Security Considerations ................................ 94 12. Security Considerations ................................ 94
13. Authors' Addresses ..................................... 95 13. Authors' Addresses ..................................... 95
 End of changes. 

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