draft-ietf-adslmib-adsllinemib-03.txt   draft-ietf-adslmib-adsllinemib-04.txt 
INTERNET-DRAFT ADSL Line MIB Gregory Bathrick INTERNET-DRAFT ADSL Line MIB Gregory Bathrick
AG Communication Systems AG Communication Systems
Faye Ly Faye Ly
Copper Mountain Networks Copper Mountain Networks
November 16, 1998 December 21, 1998
Definitions of Managed Objects Definitions of Managed Objects
for the ADSL Lines for the ADSL Lines
November 16, 1998 December 21, 1998
draft-ietf-adslmib-adsllinemib-03.txt draft-ietf-adslmib-adsllinemib-04.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
skipping to change at page 2, line 5 skipping to change at page 2, line 5
Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu (US West Coast). 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 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 ADSL standard describes ADSL Forum standard data model [9]. The ADSL standard describes
ATU-C and ATU-R as two sides of the ADSL line. This MIB covers both ATU-C and ATU-R as two sides of the ADSL line. This MIB covers both
ATU-C and ATU-R agent's perspectives. Each instance defined in the ATU-C and ATU-R agent's perspectives. Each instance defined in the
MIB represents a single ADSL line. MIB represents a single ADSL line.
It should be noted that much of the content for the first version It should be noted that the original version (v00) of this document
(v00) of this document came from work completed by the ADSL Forum's came from work completed by the ADSL Forum's Network Management
Network Management working group and documented in ADSL Forum TR-006 working group and documented in ADSL Forum TR-006 'SNMP-based ADSL
"SNMP-based ADSL Line MIB"[9]. See Acknowledgement Section for a Line MIB'[9]. See `REVISION' clauses of this document for changes
list of individuals involved with this effort. made to date. See Acknowledgement Section for a list of individuals
involved with these ADSL Forum and IETF efforts.
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 11, line 17 skipping to change at page 11, line 17
adslAtucInvVersionNumber adslAtucInvVersionNumber
adslAtucCurrStatus (Partial) adslAtucCurrStatus (Partial)
adslAtucCurrOutputPwr adslAtucCurrOutputPwr
adslAtucCurrAttainableRate adslAtucCurrAttainableRate
adslAturPhysTable all are supported adslAturPhysTable all are supported
adslAtucChanTable all except adslAtucChanTable all except
adslAtucChanCrcBlockLength adslAtucChanCrcBlockLength
are supported are supported
adslAtucPerfDataTable all except adslAtucPerfDataTable all except
adslAtucPerfLols, adslAtucPerfLprs adslAtucPerfLols, adslAtucPerfLprs
adslAtucPerfCurr15MinLols,
adslAtucPerfCurr15MinLprs,
adslAtucPerfCurr1DayLols, adslAtucPerfCurr1DayLols,
adslAtucPerfCurr1DayLprs, adslAtucPerfCurr1DayLprs,
adslAtucPerfPrev1DayLols and adslAtucPerfPrev1DayLols and
adslAtucPerfPrev1DayLprs adslAtucPerfPrev1DayLprs
are supported are supported
adslAturPerfDataTable all are supported adslAturPerfDataTable all are supported
adslAtucIntervalTable adslAtucIntervalLofs adslAtucIntervalTable adslAtucIntervalLofs
adslAtucIntervalLoss adslAtucIntervalLoss
adslAtucIntervalESs adslAtucIntervalESs
adslAtucIntervalInits adslAtucIntervalInits
skipping to change at page 11, line 47 skipping to change at page 11, line 49
-------------------------------------------------------------------- --------------------------------------------------------------------
Figure 7: MIB Tables and Objects Supported by the ATU-R Agent Figure 7: MIB Tables and Objects Supported by the ATU-R Agent
All traps supported by the ATU-R agent are also listed: All traps supported by the ATU-R agent are also listed:
adslAtucPerfLofsThreshTrap adslAtucPerfLofsThreshTrap
adslAtucPerfLossThreshTrap adslAtucPerfLossThreshTrap
adslAtucPerfESsThreshTrap adslAtucPerfESsThreshTrap
adslAtucRateChangeTrap adslAtucRateChangeTrap
adslAtucInitFailureTrap
adslAturPerfLofsThreshTrap adslAturPerfLofsThreshTrap
adslAturPerfLossThreshTrap adslAturPerfLossThreshTrap
adslAturPerfESsThreshTrap adslAturPerfESsThreshTrap
adslAturRateChangeTrap adslAturRateChangeTrap
adslAturInitFailureTrap
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
skipping to change at page 12, line 33 skipping to change at page 12, line 36
received-and-corrected blocks, received-but-uncorrectable blocks, and received-and-corrected blocks, received-but-uncorrectable blocks, and
transmitted blocks. There are the same set of 15-minute and 1-day transmitted blocks. There are the same set of 15-minute and 1-day
buckets as at the physical layer. buckets as at the physical layer.
Separate tables are provided for the 96 interval-counters. They are Separate tables are provided for the 96 interval-counters. They are
indexed by {ifIndex, AdslAtu*IntervalNumber}. indexed by {ifIndex, AdslAtu*IntervalNumber}.
Every physical layer object with a 15 minute current bucket also has Every physical layer object with a 15 minute current bucket also has
a 15-min threshold trap. a 15-min threshold trap.
Counters are not reset when an ATU-C is reinitialized, only when the Counters are not reset when an ATU-C or ATU-R is reinitialized, only
agent is reset or reinitialized (or under specific request outside when the agent is reset or reinitialized (or under specific request
the scope of this MIB). outside the scope of this MIB).
7.4 Profiles 7.4 Profiles
As a managed node can handle a large number of ATU-Cs (e.g., hundreds As a managed node can handle a large number of ATU-Cs (e.g., hundreds
or perhaps thousands of ADSL lines), provisioning every parameter on or perhaps thousands of ADSL lines), provisioning every parameter on
every ATU-C may become burdensome. In response, two MIB tables have every ATU-C may become burdensome. In response, two MIB tables have
been created to define ADSL equipment configuration data profiles, as been created to define ADSL equipment configuration data profiles, as
well as a mechanism to associate the equipment to these profiles. well as a mechanism to associate the equipment to these profiles.
Profile tables may be implemented in one of two ways, but not Profile tables may be implemented in one of two ways, but not
skipping to change at page 14, line 22 skipping to change at page 14, line 24
contains an adslLineTable entry, therefore only those entries contain contains an adslLineTable entry, therefore only those entries contain
pointers to the adslConfProfileTable. The ifStackTable (see rfc2233 pointers to the adslConfProfileTable. The ifStackTable (see rfc2233
[5]) can be used to link the channel entries to the corresponding [5]) can be used to link the channel entries to the corresponding
physical layer entry to get the channel's configuration parameters. physical layer entry to get the channel's configuration parameters.
See figure 4 for use of the ifStackTable. See figure 4 for use of the ifStackTable.
The same characteristics and mechanisms are present for the alarm The same characteristics and mechanisms are present for the alarm
profile type. There is no requirement that its index be the same as profile type. There is no requirement that its index be the same as
the configuration profile. the configuration profile.
Implementations of this mode, must provide a default profile whose
name is `DEFVAL' for each profile type: Configuration and Alarm. The
values of the associated parameters will be vendor specific unless
otherwise indicated in this document. Before a line's profiles have
been set, these profiles will be automatically used by setting
adslLineConfProfile and adslLineAlarmConfProfile to `DEFVAL'.
In this mode, profiles are created, assigned, and deleted dynamically In this mode, profiles are created, assigned, and deleted dynamically
using these four objects: adslLineConfProfile, using these four objects: adslLineConfProfile,
adslLineConfProfileRowStatus, adslLineAlarmProfile, and adslLineConfProfileRowStatus, adslLineAlarmProfile, and
adslLineAlarmConfProfileRowStatus. adslLineAlarmConfProfileRowStatus.
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. The name of this one-for-one with each ADSL line physical entry. The name of this
profile is a system generated read-only object whose value is profile is a system generated read-only object whose value is
skipping to change at page 15, line 34 skipping to change at page 15, line 43
occurs. At this operational point, a manager can use occurs. At this operational point, a manager can use
adslAtu*CurrStatus for additional detailed information. The adslAtu*CurrStatus for additional detailed information. The
corresponding linkUp trap is sent when all link failure conditions corresponding linkUp trap is sent when all link failure conditions
are cleared. are cleared.
The traps defined in this MIB are for initialization failure, rate The traps defined in this MIB are for initialization failure, rate
change, and for the threshold crossings associated with the following change, and for the threshold crossings associated with the following
events: Lofs, Lols, Loss, Lprs, and ESs. Each threshold has its own events: Lofs, Lols, Loss, Lprs, and ESs. Each threshold has its own
enable/threshold value. When that value is 0, the trap is disabled. enable/threshold value. When that value is 0, the trap is disabled.
The objects adslAtu*CurrStatus indicate, through a bitmask, all The current status objects (adslAtu*CurrStatus) indicate, through a
outstanding error conditions or that the line is operational. Note bitmask, all outstanding error conditions or that the line is
that each object claims to represent the status of the modem at that operational. Note that each object claims to represent the status of
end of the line. However, since the SNMP agent co-resides with the the modem at that end of the line. However, since the SNMP agent
ATU-C, adslAturCurrStatus may be incomplete. For example, when there likely co-resides with only one end of the line, the corresponding
are errors on the line, the ATU-R may not be able to correctly report far-end current status object may be incomplete. For example, when
this condition. Therefore, not all conditions are included in there are errors on the line, the far-end ATU may not be able to
adslAturCurrStatus. correctly report this condition. Therefore, not all conditions are
included in its current status.
A threshold trap occurs whenever the corresponding current 15-minute A threshold trap occurs whenever the corresponding current 15-minute
interval error counter becomes equal to the threshold value. Since interval error counter becomes equal to the threshold value. Since
the current 15-minute counter are reset to 0 every 15 minutes, if the the current 15-minute counter are reset to 0 every 15 minutes, if the
condition persists, the trap may recur as often as every 15 minutes. condition persists, the trap may recur as often as every 15 minutes.
For example, to get a trap whenever a "loss of" event occurs (but at For example, to get a trap whenever a "loss of" event occurs (but at
most once every 15 minutes), set the corresponding "Thresh15Min" to most once every 15 minutes), set the corresponding "Thresh15Min" to
1. The agent will generate a trap when the event originally occurs. 1. The agent will generate a trap when the event originally occurs.
Note that the NMS will get a linkDown trap, as well, if enabled. At Note that the NMS will get a linkDown trap, as well, if enabled. At
the beginning of the next 15 minute interval, the counter is reset. the beginning of the next 15 minute interval, the counter is reset.
When the first second goes by, the current interval bucket will be 1, When the first second goes by, the current interval bucket will be 1,
which equals the threshold and the trap will be sent again. which equals the threshold and the trap will be sent again.
The rate change trap is invoked when the transmit rate on a channel The rate change trap is invoked when the transmit rate on a channel
either increases by adsl(x)Thresh(y)RateUp or decreases by either increases by adsl(x)Thresh(y)RateUp or decreases by
adsl(x)Thresh(y)RateDown. The trap is per direction:(x) == Atuc or adsl(x)Thresh(y)RateDown. The trap is per direction:(x) == Atuc or
Atur, and per channel: (y) == Fast or Interleave. In other words, the Atur, and per channel: (y) == Fast or Interleave. In other words, the
trap is sent whenever the rate changes in either direction on either trap is sent whenever the rate changes in either direction on either
skipping to change at page 17, line 43 skipping to change at page 18, line 4
Fax: +1 650-858-8085 Fax: +1 650-858-8085
E-Mail: faye@norcal.coppermountain.com E-Mail: faye@norcal.coppermountain.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 973-301-5610 Tel: +1 973-301-5610
Fax: +1 973-301-5699 Fax: +1 973-301-5699
E-mail: jtburgess@predictive.com E-mail: jtburgess@predictive.com
IETF ADSL MIB Working Group (adsl@xlist.agcs.com) IETF ADSL MIB Working Group (adsl@xlist.agcs.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 has
indexed by ifIndex and appears as an interface on a central an entry in an ifTable which may include multiple modem lines.
DSLAM (Digital Subscriber Line Access Mux.) Attributes on the An agent may reside at either end of the ADSL line however the
ATUR are proxied by the DSLAM. MIB is designed to require no management communication between
them beyond that inherent in the low-level ADSL line protocol.
The agent may monitor and control this protocol for its needs.
ADSL lines may support optional Fast or Interleaved channels. ADSL lines may support optional Fast or Interleaved channels.
If these are supported, additional entries corresponding to the If these are supported, additional entries corresponding to the
supported channels must be created in the ifTable. Thus an ADSL supported channels must be created in the ifTable. Thus an ADSL
line that supports both channels will have three entries in the line that supports both channels will have three entries in the
ifTable, one for each physical, fast, and interleaved, whose ifTable, one for each physical, fast, and interleaved, whose
ifType values are equal to adsl(94), fast(125), and ifType values are equal to adsl(94), fast(125), and
interleaved(124), respectively. The ifStackTable is used to interleaved(124), respectively. The ifStackTable is used to
represent the relationship between the entries. represent the relationship between the entries.
skipping to change at page 20, line 13 skipping to change at page 20, line 23
REVISION "9811161200Z" REVISION "9811161200Z"
DESCRIPTION DESCRIPTION
" "
Changes: Changes:
- updated text and conformance statements to include - updated text and conformance statements to include
CPE equipment view. CPE equipment view.
- updated text and objects to change profile tables - updated text and objects to change profile tables
index to SnmpAdminString. index to SnmpAdminString.
- changed transmission xx to experimental 89. - changed transmission xx to experimental 89.
- resolved conflicting statements on when traps occur. - resolved conflicting statements on when traps occur.
- added Faye Ly as co-editor and Ted SooHoo and - added Faye Ly as co-editor and Ted Soo-Hoo and
Umberto Bonollo as contributors. Umberto Bonollo as contributors.
" "
::= { experimental 89 } -- to be assigned to `94' by IANA given IESG REVISION "9812211200Z"
DESCRIPTION
"
Group Last Call version:
Changes (as agreed to made at the Orlando meeting).
- editorial corrections related to past CPE view updates.
- technical clarifications related to the use of profiles.
" ::= { experimental 89 } -- to be assigned to `94' by IANA
given IESG
-- approval. -- approval.
adslLineMib OBJECT IDENTIFIER ::= { adslMIB 1 } adslLineMib OBJECT IDENTIFIER ::= { adslMIB 1 }
adslMibObjects OBJECT IDENTIFIER ::= { adslLineMib 1 } adslMibObjects OBJECT IDENTIFIER ::= { adslLineMib 1 }
-- textual convention -- textual convention
AdslLineProfileName ::= TEXTUAL-CONVENTION AdslLineProfileName ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This data type is used to identify a row in "This data type is used to uniquely identify a row in
an ADSL Line Profile Table." an ADSL Line Profile Table."
SYNTAX SnmpAdminString (SIZE (0..32)) SYNTAX SnmpAdminString (SIZE (1..32))
adslLineTable OBJECT-TYPE adslLineTable OBJECT-TYPE
SYNTAX SEQUENCE OF AdslLineEntry SYNTAX SEQUENCE OF AdslLineEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table includes common attributes describing "This table includes common attributes describing
both ends of the line. It is required for all ADSL both ends of the line. It is required for all ADSL
physical interfaces. ADSL physical interfaces are physical interfaces. ADSL physical interfaces are
those ifEntries where ifType is equal to adsl(94)." those ifEntries where ifType is equal to adsl(94)."
skipping to change at page 22, line 22 skipping to change at page 22, line 40
::= { adslLineEntry 3 } ::= { adslLineEntry 3 }
adslLineConfProfile OBJECT-TYPE adslLineConfProfile OBJECT-TYPE
SYNTAX AdslLineProfileName SYNTAX AdslLineProfileName
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of this object identifies the row "The value of this object identifies the row
in the ADSL Line Configuration Profile Table, in the ADSL Line Configuration Profile Table,
(adslLineConfProfileTable), which applies for this (adslLineConfProfileTable), which applies for this
ADSL line, and channels if applicable. In the case ADSL line, and channels if applicable.
which the configuration profile has not been set, the
value will be an SnmpAdminString of zero length. For `dynamic' mode, in the case which the
configuration profile has not been set, the
value will be set to `DEFVAL'.
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's MIN-ACCESS is read-only." object's MIN-ACCESS is read-only."
::= { adslLineEntry 4 } ::= { adslLineEntry 4 }
adslLineAlarmConfProfile OBJECT-TYPE adslLineAlarmConfProfile OBJECT-TYPE
SYNTAX AdslLineProfileName SYNTAX AdslLineProfileName
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of this object identifies the row "The value of this object identifies the row
in the ADSL Line Alarm Configuration Profile Table, in the ADSL Line Alarm Configuration Profile Table,
(adslLineAlarmConfProfileTable), which applies to this (adslLineAlarmConfProfileTable), which applies to this
ADSL line, and channels if applicable. In the case ADSL line, and channels if applicable.
which the configuration profile has not been set, the
value will be an SnmpAdminString of zero length. For `dynamic' mode, in the case which the
alarm profile has not been set, the
value will be set to `DEFVAL'.
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's MIN-ACCESS is read-only." object's MIN-ACCESS is read-only."
::= { adslLineEntry 5 } ::= { adslLineEntry 5 }
adslAtucPhysTable OBJECT-TYPE adslAtucPhysTable OBJECT-TYPE
SYNTAX SEQUENCE OF AdslAtucPhysEntry SYNTAX SEQUENCE OF AdslAtucPhysEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 25, line 8 skipping to change at page 25, line 29
lossOfSignalQuality(4), lossOfSignalQuality(4),
lossOfLink(5), lossOfLink(5),
dataInitFailure(6), dataInitFailure(6),
configInitFailure(7), configInitFailure(7),
protocolInitFailure(8), protocolInitFailure(8),
noPeerAtuPresent(9) noPeerAtuPresent(9)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Status indicates current state ATUC line. This is a "Indicates current state of the ATUC line. This is a
bit-map of possible conditions. The various bit bit-map of possible conditions. The various bit
positions are: positions are:
0 noDefect There no defects on the line 0 noDefect There no defects on the line
1 lossOfFraming ATUC failure due to not 1 lossOfFraming ATUC failure due to not
receiving valid frame. receiving valid frame.
2 lossOfSignal ATUC failure due to not 2 lossOfSignal ATUC failure due to not
receiving signal. receiving signal.
skipping to change at page 28, line 31 skipping to change at page 29, line 4
SYNTAX BITS { SYNTAX BITS {
noDefect(0), noDefect(0),
lossOfFraming(1), lossOfFraming(1),
lossOfSignal(2), lossOfSignal(2),
lossOfPower(3), lossOfPower(3),
lossOfSignalQuality(4) lossOfSignalQuality(4)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Status indicates current state ATUR line. This is a "Indicates current state of the ATUR line. This is a
bit-map of possible conditions. Due to the isolation bit-map of possible conditions. Due to the isolation
of the ATUR when line problems occur, many state of the ATUR when line problems occur, many state
conditions like loss of power, loss of quality signal, conditions like loss of power, loss of quality signal,
and initialization errors, can not be determined. and initialization errors, can not be determined.
While trouble shooting ATUR, also use object, While trouble shooting ATUR, also use object,
adslAtucCurrStatus. The various bit positions are: adslAtucCurrStatus. The various bit positions are:
0 noDefect There no defects on the line 0 noDefect There no defects on the line
1 lossOfFraming ATUR failure due to not 1 lossOfFraming ATUR failure due to not
skipping to change at page 66, line 42 skipping to change at page 67, line 14
configure the ADSL line." configure the ADSL line."
::= { adslMibObjects 14} ::= { adslMibObjects 14}
adslLineConfProfileEntry OBJECT-TYPE adslLineConfProfileEntry OBJECT-TYPE
SYNTAX AdslLineConfProfileEntry SYNTAX AdslLineConfProfileEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each entry consists of a list of parameters that "Each entry consists of a list of parameters that
represents the configuration of an ADSL modem. represents the configuration of an ADSL modem.
When `dynamic' profiles are implemented, a When `dynamic' profiles are implemented, a
profile is created in one step with all necessary profile is created in one step with all necessary
parameter values and adslLineProfileRowStatus set to parameter values and adslLineProfileRowStatus set to
createAndGo. This RowStatus object is also used createAndGo. This RowStatus object is also used
to destroy profiles. to destroy profiles.
Also when `dynamic' profiles are implemented, a default
profile will always exist. This profile's name will
be set to `DEFVAL' and its parameters will be set to
vendor specific values, unless otherwise specified
in this document.
When `static' profiles are implemented, profiles When `static' profiles are implemented, profiles
are automically created or destroyed as ADSL are automically created or destroyed as ADSL
physical lines are discovered and removed by physical lines are discovered and removed by
the system. The name of the profile will be the system. The name of the profile will be
equivalent to the decimal value of the line's equivalent to the decimal value of the line's
interface index. interface index.
" "
INDEX { adslLineConfProfileName} INDEX { IMPLIED adslLineConfProfileName}
::= { adslLineConfProfileTable 1} ::= { adslLineConfProfileTable 1}
AdslLineConfProfileEntry ::= AdslLineConfProfileEntry ::=
SEQUENCE { SEQUENCE {
adslLineConfProfileName adslLineConfProfileName AdslLineProfileName,
AdslLineProfileName,
adslAtucConfRateMode INTEGER, adslAtucConfRateMode INTEGER,
adslAtucConfRateChanRatio INTEGER, adslAtucConfRateChanRatio INTEGER,
adslAtucConfTargetSnrMgn INTEGER, adslAtucConfTargetSnrMgn INTEGER,
adslAtucConfMaxSnrMgn INTEGER, adslAtucConfMaxSnrMgn INTEGER,
adslAtucConfMinSnrMgn INTEGER, adslAtucConfMinSnrMgn INTEGER,
adslAtucConfDownshiftSnrMgn INTEGER, adslAtucConfDownshiftSnrMgn INTEGER,
adslAtucConfUpshiftSnrMgn INTEGER, adslAtucConfUpshiftSnrMgn INTEGER,
adslAtucConfMinUpshiftTime INTEGER, adslAtucConfMinUpshiftTime INTEGER,
adslAtucConfMinDownshiftTime INTEGER, adslAtucConfMinDownshiftTime INTEGER,
adslAtucChanConfFastMinTxRate INTEGER, adslAtucChanConfFastMinTxRate INTEGER,
skipping to change at page 67, line 51 skipping to change at page 68, line 29
adslAturChanConfMaxInterleaveDelay INTEGER, adslAturChanConfMaxInterleaveDelay INTEGER,
adslLineConfProfileRowStatus RowStatus adslLineConfProfileRowStatus RowStatus
} }
adslLineConfProfileName OBJECT-TYPE adslLineConfProfileName OBJECT-TYPE
SYNTAX AdslLineProfileName SYNTAX AdslLineProfileName
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is used by the line configuration table "This object is used by the line configuration table
in order to identify a row of this table" in order to identify a row of this table.
When `dynamic' profiles are implemented, the profile
name is user specified. Also, the system will always
provide a default profile whose name is `DEFVAL'.
When `static' profiles are implemented, there is an
one-to-one relationship between each line and its
profile. In which case, the profile name will
need to algorithmicly represent the Line's ifIndex.
Therefore, the profile's name is a decimalized string
of the ifIndex that is fixed-length (i.e., 10) with
leading zero(s). For example, the profile name for
ifIndex which equals '15' will be '0000000015'."
::= { adslLineConfProfileEntry 1 } ::= { adslLineConfProfileEntry 1 }
adslAtucConfRateMode OBJECT-TYPE adslAtucConfRateMode OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
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)
} }
skipping to change at page 76, line 5 skipping to change at page 76, line 45
::= { adslLineConfProfileEntry 29 } ::= { adslLineConfProfileEntry 29 }
adslLineConfProfileRowStatus OBJECT-TYPE adslLineConfProfileRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
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.
A profile activated by setting this object to
`active'. When `active' is set, the system
will validate the profile.
Before a profile can be deleted or taken out of Before a profile can be deleted or taken out of
service, (by setting this object to `destroy' or service, (by setting this object to `destroy' or
`outOfService') it must be first unreferenced `outOfService') it must be first unreferenced
from all associated lines. from all associated lines.
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's MIN-ACCESS is read-only and its value object's MIN-ACCESS is read-only and its value
is always to be `active'." is always to be `active'."
::= { adslLineConfProfileEntry 30 } ::= { adslLineConfProfileEntry 30 }
skipping to change at page 76, line 34 skipping to change at page 77, line 30
configure the modem for a physical line" configure the modem for a physical line"
::= { adslMibObjects 15} ::= { adslMibObjects 15}
adslLineAlarmConfProfileEntry OBJECT-TYPE adslLineAlarmConfProfileEntry OBJECT-TYPE
SYNTAX AdslLineAlarmConfProfileEntry SYNTAX AdslLineAlarmConfProfileEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each entry consists of a list of parameters that "Each entry consists of a list of parameters that
represents the configuration of an ADSL modem. represents the configuration of an ADSL modem.
When `dynamic' profiles are implemented, a When `dynamic' profiles are implemented, a
profile is created in one step with all necessary profile is created in one step with all necessary
parameter values and adslLineProfileRowStatus set to parameter values and adslLineProfileRowStatus set to
createAndGo. This RowStatus object is also used createAndGo. This RowStatus object is also used
to destroy profiles. to destroy profiles.
Also when `dynamic' profiles are implemented, a default
profile will always exist. This profile's name will
be set to `DEFVAL' and its parameters will be set to
vendor specific values, unless otherwise specified
in this document.
When `static' profiles are implemented, profiles When `static' profiles are implemented, profiles
are automically created or destroyed as ADSL are automically created or destroyed as ADSL
physical lines are discovered and removed by physical lines are discovered and removed by
the system. The name of the profile will be the system. The name of the profile will be
equivalent to the decimal value of the line's equivalent to the decimal value of the line's
interface index. interface index.
" "
INDEX { adslLineAlarmConfProfileName} INDEX { IMPLIED adslLineAlarmConfProfileName}
::= { adslLineAlarmConfProfileTable 1} ::= { adslLineAlarmConfProfileTable 1}
AdslLineAlarmConfProfileEntry ::= AdslLineAlarmConfProfileEntry ::=
SEQUENCE { SEQUENCE {
adslLineAlarmConfProfileName adslLineAlarmConfProfileName AdslLineProfileName,
AdslLineProfileName,
adslAtucThresh15MinLofs INTEGER, adslAtucThresh15MinLofs INTEGER,
adslAtucThresh15MinLoss INTEGER, adslAtucThresh15MinLoss INTEGER,
adslAtucThresh15MinLols INTEGER, adslAtucThresh15MinLols INTEGER,
adslAtucThresh15MinLprs INTEGER, adslAtucThresh15MinLprs INTEGER,
adslAtucThresh15MinESs INTEGER, adslAtucThresh15MinESs INTEGER,
adslAtucThreshFastRateUp Integer32, adslAtucThreshFastRateUp Integer32,
adslAtucThreshInterleaveRateUp Integer32, adslAtucThreshInterleaveRateUp Integer32,
adslAtucThreshFastRateDown Integer32, adslAtucThreshFastRateDown Integer32,
adslAtucThreshInterleaveRateDown Integer32, adslAtucThreshInterleaveRateDown Integer32,
adslAtucInitFailureTrapEnable INTEGER, adslAtucInitFailureTrapEnable INTEGER,
skipping to change at page 77, line 32 skipping to change at page 78, line 36
adslAturThreshInterleaveRateDown Integer32, adslAturThreshInterleaveRateDown Integer32,
adslLineAlarmConfProfileRowStatus RowStatus adslLineAlarmConfProfileRowStatus RowStatus
} }
adslLineAlarmConfProfileName OBJECT-TYPE adslLineAlarmConfProfileName OBJECT-TYPE
SYNTAX AdslLineProfileName SYNTAX AdslLineProfileName
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"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}
When `dynamic' profiles are implemented, the profile
name is user specified. Also, the system will always
provide a default profile whose name is `DEFVAL'.
When `static' profiles are implemented, there is an
one-to-one relationship between each line and its
profile. In which case, the profile name will
need to algorithmicly represent the Line's ifIndex.
Therefore, the profile's name is a decimalized string
of the ifIndex that is fixed-length (i.e., 10) with
leading zero(s). For example, the profile name for
ifIndex which equals '15' will be '0000000015'."
::= { 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
skipping to change at page 83, line 10 skipping to change at page 84, line 27
::= { adslLineAlarmConfProfileEntry 19 } ::= { adslLineAlarmConfProfileEntry 19 }
adslLineAlarmConfProfileRowStatus OBJECT-TYPE adslLineAlarmConfProfileRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
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.
A profile activated by setting this object to
`active'. When `active' is set, the system
will validate the profile.
Before a profile can be deleted or taken out of Before a profile can be deleted or taken out of
service, (by setting this object to `destroy' or service, (by setting this object to `destroy' or
`outOfService') it must be first unreferenced `outOfService') it must be first unreferenced
from all associated lines. from all associated lines.
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's MIN-ACCESS is read-only and its value object's MIN-ACCESS is read-only and its value
is always to be `active'." is always to be `active'."
::= { adslLineAlarmConfProfileEntry 20 } ::= { adslLineAlarmConfProfileEntry 20 }
-- Line Code Specific Tables -- Line Code Specific Tables
-- These are place holders for the Line Code Specific MIBs -- These are place holders for the Line Code Specific MIBs
-- once they become available. -- once they become available.
adslLCSTable OBJECT IDENTIFIER ::= { adslMibObjects 16 } adslLCSMib OBJECT IDENTIFIER ::= { adslMibObjects 16 }
-- trap definitions -- trap definitions
adslTraps OBJECT IDENTIFIER ::= { adslLineMib 2 } adslTraps OBJECT IDENTIFIER ::= { adslLineMib 2 }
adslAtucTraps OBJECT IDENTIFIER ::= { adslTraps 1 } adslAtucTraps OBJECT IDENTIFIER ::= { adslTraps 1 }
adslAtucPerfLofsThreshTrap NOTIFICATION-TYPE adslAtucPerfLofsThreshTrap NOTIFICATION-TYPE
OBJECTS { adslAtucThresh15MinLofs } OBJECTS { adslAtucThresh15MinLofs }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Loss of Framing 15-minute interval threshold reached." "Loss of Framing 15-minute interval threshold reached."
::= { adslAtucTraps 0 1 } ::= { adslAtucTraps 0 1 }
skipping to change at page 87, line 30 skipping to change at page 89, line 4
OBJECT adslLineAlarmConfProfileRowStatus OBJECT adslLineAlarmConfProfileRowStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Read-only access is applicable only when static "Read-only access is applicable only when static
profiles are implemented." profiles are implemented."
::= { adslCompliances 1 } ::= { adslCompliances 1 }
-- Atur compliance statements -- Atur compliance statements
adslLineMibAturCompliance MODULE-COMPLIANCE adslLineMibAturCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for SNMP entities "The compliance statement for SNMP entities
which manage ADSL ATU-R interfaces." which manage ADSL ATU-R interfaces."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS MANDATORY-GROUPS
{ {
adslAturLineGroup, adslAturAturPhysicalGroup, adslAturLineGroup, adslAturPhysicalGroup,
adslAturChannelGroup, adslAturChannelGroup,
adslAturAtucPhysPerfIntervalGroup, adslAturAtucPhysPerfIntervalGroup,
adslAturAturPhysPerfIntervalGroup, adslAturAturPhysPerfIntervalGroup,
adslAturLineProfileGroup, adslAturLineProfileGroup,
adslAturLineAlarmProfileGroup, adslAturLineAlarmProfileGroup,
adslAturLineProfileControlGroup adslAturLineProfileControlGroup
} }
GROUP adslAturAtucPhysPerfRawCounterGroup GROUP adslAturAtucPhysPerfRawCounterGroup
DESCRIPTION DESCRIPTION
skipping to change at page 96, line 10 skipping to change at page 97, line 32
ATU-R agent." ATU-R agent."
::= { adslGroups 17 } ::= { adslGroups 17 }
adslAturAtucPhysPerfIntervalGroup OBJECT-GROUP adslAturAtucPhysPerfIntervalGroup OBJECT-GROUP
OBJECTS { OBJECTS {
adslAtucPerfValidIntervals, adslAtucPerfValidIntervals,
adslAtucPerfInvalidIntervals, adslAtucPerfInvalidIntervals,
adslAtucPerfCurr15MinTimeElapsed, adslAtucPerfCurr15MinTimeElapsed,
adslAtucPerfCurr15MinLofs, adslAtucPerfCurr15MinLoss, adslAtucPerfCurr15MinLofs, adslAtucPerfCurr15MinLoss,
adslAtucPerfCurr15MinESs, adslAtucPerfCurr15MinInits, adslAtucPerfCurr15MinESs, adslAtucPerfCurr15MinInits,
adslAtucPerfCurr1DayTimeElapsed,
adslAtucPerfCurr1DayLofs, adslAtucPerfCurr1DayLoss, adslAtucPerfCurr1DayLofs, adslAtucPerfCurr1DayLoss,
adslAtucPerfCurr1DayESs, adslAtucPerfCurr1DayInits, adslAtucPerfCurr1DayESs, adslAtucPerfCurr1DayInits,
adslAtucPerfPrev1DayMoniSecs, adslAtucPerfPrev1DayMoniSecs,
adslAtucPerfPrev1DayLofs, adslAtucPerfPrev1DayLoss, adslAtucPerfPrev1DayLofs, adslAtucPerfPrev1DayLoss,
adslAtucPerfPrev1DayESs, adslAtucPerfPrev1DayInits, adslAtucPerfPrev1DayESs, adslAtucPerfPrev1DayInits,
adslAtucIntervalLofs, adslAtucIntervalLoss, adslAtucIntervalLofs, adslAtucIntervalLoss,
adslAtucIntervalESs, adslAtucIntervalInits, adslAtucIntervalESs, adslAtucIntervalInits,
adslAtucIntervalValidData adslAtucIntervalValidData
} }
STATUS current STATUS current
skipping to change at page 97, line 22 skipping to change at page 98, line 45
counts on ADSL Line (ATU-R end) provided by the counts on ADSL Line (ATU-R end) provided by the
ATU-R agent." ATU-R agent."
::= { adslGroups 20 } ::= { adslGroups 20 }
adslAturAtucChanPerformanceGroup OBJECT-GROUP adslAturAtucChanPerformanceGroup OBJECT-GROUP
OBJECTS { OBJECTS {
adslAtucChanReceivedBlks, adslAtucChanReceivedBlks,
adslAtucChanTransmittedBlks, adslAtucChanTransmittedBlks,
adslAtucChanCorrectedBlks, adslAtucChanCorrectedBlks,
adslAtucChanUncorrectBlks, adslAtucChanUncorrectBlks,
adslAtucChanPerfCurr15MinTimeElapsed,
adslAtucChanPerfCurr15MinReceivedBlks,
adslAtucChanPerfCurr15MinTransmittedBlks,
adslAtucChanPerfCurr15MinCorrectedBlks,
adslAtucChanPerfCurr15MinUncorrectBlks,
adslAtucChanPerfCurr1DayTimeElapsed,
adslAtucChanPerfCurr1DayReceivedBlks,
adslAtucChanPerfCurr1DayTransmittedBlks,
adslAtucChanPerfCurr1DayCorrectedBlks,
adslAtucChanPerfCurr1DayUncorrectBlks,
adslAtucChanPerfPrev1DayMoniSecs,
adslAtucChanPerfPrev1DayReceivedBlks,
adslAtucChanPerfPrev1DayTransmittedBlks,
adslAtucChanPerfPrev1DayCorrectedBlks,
adslAtucChanPerfPrev1DayUncorrectBlks,
adslAtucChanPerfValidIntervals, adslAtucChanPerfValidIntervals,
adslAtucChanPerfInvalidIntervals, adslAtucChanPerfInvalidIntervals,
adslAtucChanIntervalReceivedBlks, adslAtucChanIntervalReceivedBlks,
adslAtucChanIntervalTransmittedBlks, adslAtucChanIntervalTransmittedBlks,
adslAtucChanIntervalCorrectedBlks, adslAtucChanIntervalCorrectedBlks,
adslAtucChanIntervalUncorrectBlks, adslAtucChanIntervalUncorrectBlks,
adslAtucChanIntervalValidData adslAtucChanIntervalValidData
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 99, line 17 skipping to change at page 101, line 7
"A collection of objects providing profile "A collection of objects providing profile
control for the ADSL system by the ATU-R agent." control for the ADSL system by the ATU-R agent."
::= { adslGroups 24 } ::= { adslGroups 24 }
adslAturNotificationsGroup NOTIFICATION-GROUP adslAturNotificationsGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
adslAtucPerfLofsThreshTrap, adslAtucPerfLofsThreshTrap,
adslAtucPerfLossThreshTrap, adslAtucPerfLossThreshTrap,
adslAtucPerfESsThreshTrap, adslAtucPerfESsThreshTrap,
adslAtucRateChangeTrap, adslAtucRateChangeTrap,
adslAtucInitFailureTrap,
adslAturPerfLofsThreshTrap, adslAturPerfLofsThreshTrap,
adslAturPerfLossThreshTrap, adslAturPerfLossThreshTrap,
adslAturPerfLprsThreshTrap,
adslAturPerfESsThreshTrap, adslAturPerfESsThreshTrap,
adslAturRateChangeTrap adslAturRateChangeTrap
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of adsl notifications implemented by "The collection of ADSL notifications implemented by
the ATU-R agent." the ATU-R agent."
::= { adslGroups 25 } ::= { adslGroups 25 }
END END
10. Acknowledgments 10. Acknowledgments
Original ADSL Forum TR006[9] editors: Original ADSL Forum TR006[9] editors were:
Gregory Bathrick (AG Communication Systems) Gregory Bathrick (AG Communication Systems)
John Burgess (Predictive Systems) John Burgess (Predictive Systems)
Contributions have been received from the IETF-ADSLMIB and ADSLF-NM The current editors are:
working groups, including, but not limited to:
Gregory Bathrick (AG Communication Systems)
Faye Ly (Copper Mountain Networks)
Contributions have been received from, but not limited to following
contributors as well as the IETF ADSL MIB working group at large. (in
alphabetical order)
David Allen (Nortel) David Allen (Nortel)
Rajesh Abbi (Alcatel) Rajesh Abbi (Alcatel)
Gregory Bathrick (AG Communication Systems) Gregory Bathrick (AG Communication Systems)
Umberto Bonollo (NEC) Umberto Bonollo (NEC)
John Burgess (Predictive Systems) John Burgess (Predictive Systems)
Gail Cone (Amati) Gail Cone (Amati)
Peter Duffy (Atlantech) Peter Duffy (Atlantech)
Kevin Godfrey (Motorola) Kevin Godfrey (Motorola)
Bill Hong (Diamond Lane) Bill Hong (Diamond Lane)
skipping to change at page 100, line 13 skipping to change at page 102, line 10
Lars Johansson (Ericsson) Lars Johansson (Ericsson)
Jeff Johnson (RedBack Network) Jeff Johnson (RedBack Network)
Tsu Kai Lu (DSC) Tsu Kai Lu (DSC)
Faye Ly (Copper Mountain Networks) Faye Ly (Copper Mountain Networks)
Gigi Karmous-Edwards (Pulsecom) Gigi Karmous-Edwards (Pulsecom)
Ron Knipper (Diamond Lane) Ron Knipper (Diamond Lane)
Adil Masood (AG Communication Systems) Adil Masood (AG Communication Systems)
Padmore Peterson (BT) Padmore Peterson (BT)
Anna Salguero (SBC) Anna Salguero (SBC)
Donald Simon (Motorola) Donald Simon (Motorola)
Mike Sneed (Pulsecom)
Ted Soo-Hoo (Pulsecom) Ted Soo-Hoo (Pulsecom)
John Stehman (Diamond Lane) John Stehman (Diamond Lane)
Chuck Storry (Newbridge) Chuck Storry (Newbridge)
Chi-Lin Tom (AFC) Chi-Lin Tom (AFC)
Frank Van der Putten (Alcatel) Frank Van der Putten (Alcatel)
Marc Van Vlimmeren (Alcatel) Marc Van Vlimmeren (Alcatel)
Bert Wijnen (IBM) Bert Wijnen (IBM)
11. References 11. References
skipping to change at page 104, line 29 skipping to change at page 106, line 27
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 ............................ 7 7. Conventions used in the MIB ............................ 7
8. Conformance and Compliance ............................. 16 8. Conformance and Compliance ............................. 16
9. Definitions ............................................ 16 9. Definitions ............................................ 16
10. Acknowledgments ........................................ 98 10. Acknowledgments ........................................ 101
11. References ............................................. 99 11. References ............................................. 102
12. Security Considerations ................................ 102 12. Security Considerations ................................ 104
13. Authors' Addresses ..................................... 102 13. Authors' Addresses ..................................... 105
 End of changes. 

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