draft-ietf-adslmib-gshdslbis-09.txt   draft-ietf-adslmib-gshdslbis-10.txt 
Network Working Group C. Sikes Network Working Group C. Sikes
Internet-Draft Paradyne Corporation Internet-Draft Paradyne Corporation
Expires: September 15, 2005 B. Ray Expires: October 15, 2005 B. Ray
PESA Switching Systems, Inc. PESA Switching Systems, Inc.
R. Abbi R. Abbi
Alcatel USA Alcatel USA
March 14, 2005 April 13, 2005
Definitions of Managed Objects for G.shdsl.bis Lines Definitions of Managed Objects for High Bit-Rate DSL - 2nd generation
draft-ietf-adslmib-gshdslbis-09.txt (HDSL2) and Single-Pair High-Speed Digital Subscriber Line (SHDSL) Lines
draft-ietf-adslmib-gshdslbis-10.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is subject to all provisions By submitting this Internet-Draft, each author represents that any
of Section 3 of RFC 3667. By submitting this Internet-Draft, each applicable patent or other IPR claims of which he or she is aware
author represents that any applicable patent or other IPR claims of have been or will be disclosed, and any of which he or she becomes
which he or she is aware have been or will be disclosed, and any of aware will be disclosed, in accordance with Section 6 of BCP 79.
which he or she become aware will be disclosed, in accordance with
RFC 3668.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as other groups may also distribute working documents as Internet-
Internet-Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on September 15, 2005. This Internet-Draft will expire on October 15, 2005.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). Copyright (C) The Internet Society (2005).
Abstract Abstract
This document defines a Management Information Base (MIB) module for This document defines a Management Information Base (MIB) module for
use with network management protocols in the Internet community. In use with network management protocols in the Internet community. In
particular, it describes objects used for managing High Bit-Rate particular, it describes objects used for managing High Bit-Rate
Digital Subscriber Line (DSL) - 2nd generation (HDSL2) and Digital Subscriber Line (DSL) - 2nd generation (HDSL2) and Single-
Single-Pair High-Speed Digital Subscriber Line (SHDSL) interfaces. Pair High-Speed Digital Subscriber Line (SHDSL) interfaces. This
This document introduces extensions to several objects and textual document introduces extensions to several objects and textual
conventions defined in HDSL2-SHDSL-Line MIB (RFC 3276). This conventions defined in HDSL2-SHDSL-Line MIB (RFC 3276). This
document obsoletes RFC 3276. document obsoletes RFC 3276.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. The Internet-Standard Management Framework . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . . 3 2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2.1 Relationship to other MIBs . . . . . . . . . . . . . . . . 3
3.1 Relationship of the HDSL2/SHDSL Line MIB to other MIBs . . 3 2.2 IANA Considerations . . . . . . . . . . . . . . . . . . . 5
3.1.1 General IF-MIB Integration (RFC 2863) . . . . . . . . 4 2.3 Conventions used in the MIB Module . . . . . . . . . . . . 6
3.1.2 Usage of ifTable . . . . . . . . . . . . . . . . . . . 4 2.4 Structure . . . . . . . . . . . . . . . . . . . . . . . . 7
3.2 IANA Considerations . . . . . . . . . . . . . . . . . . . 5 2.5 Line Topology . . . . . . . . . . . . . . . . . . . . . . 10
4. Conventions used in the MIB . . . . . . . . . . . . . . . . . 6 2.6 Counters, Interval Buckets and Thresholds . . . . . . . . 11
4.1 Naming Conventions . . . . . . . . . . . . . . . . . . . . 6 2.7 Profiles . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.2 Textual Conventions . . . . . . . . . . . . . . . . . . . 6 2.8 Notifications . . . . . . . . . . . . . . . . . . . . . . 12
4.3 Structure . . . . . . . . . . . . . . . . . . . . . . . . 7 3. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.3.1 Line Topology . . . . . . . . . . . . . . . . . . . . 10 4. Implementation Analysis . . . . . . . . . . . . . . . . . . . 66
4.4 Counters, Interval Buckets and Thresholds . . . . . . . . 11 5. Security Considerations . . . . . . . . . . . . . . . . . . . 67
4.5 Profiles . . . . . . . . . . . . . . . . . . . . . . . . . 11 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 71
4.6 Notifications . . . . . . . . . . . . . . . . . . . . . . 12 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 72
5. Conformance and Compliance . . . . . . . . . . . . . . . . . . 14 7.1 Normative References . . . . . . . . . . . . . . . . . . . 72
6. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 15 7.2 Informative References . . . . . . . . . . . . . . . . . . 73
7. Implementation Analysis . . . . . . . . . . . . . . . . . . . 66 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 74
8. Security Considerations . . . . . . . . . . . . . . . . . . . 66
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 71
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 72
10.1 Normative References . . . . . . . . . . . . . . . . . . . 72
10.2 Informative References . . . . . . . . . . . . . . . . . . 73
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 73
Intellectual Property and Copyright Statements . . . . . . . . 75 Intellectual Property and Copyright Statements . . . . . . . . 75
1. Introduction 1. The Internet-Standard Management Framework
This document defines a Management Information Base (MIB) module for
use with network management protocols in the Internet community. The
MIB module described in RFC 3276 [RFC3276] describes objects used for
managing High Bit-Rate DSL - 2nd generation (HDSL2) [T1E1.4] and
Single-Pair High-Speed Digital Subscriber Line (SHDSL) interfaces
[G.991.2]. This document obsoletes RFC 3276 [RFC3276] which supports
G.shdsl in that the MIB module described herein supports G.shdsl.bis
as described in the G.991.2 [G.991.2]. In addition, objects have
been added to improve the management of SHDSL lines.
2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to Section 7 of Internet-Standard Management Framework, please refer to Section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580]. [RFC2580].
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
3. Introduction 2. Overview
This document describes an SNMP MIB for managing HDSL2/SHDSL Lines. This document defines a Management Information Base (MIB) module for
These definitions are based upon the specifications for the HDSL2 and use with network management protocols in the Internet community for
SHDSL Embedded Operations Channel (EOC) as defined in American the purpose of managing HDSL2/SHDSL Lines.
National Standards Institute (ANSI) T1E1.4/2000-006 [T1E1.4] and
International Telecommunication Union (ITU) G.991.2 [G.991.2].
The MIB is located in the MIB tree under MIB 2 transmission, as The MIB module described in RFC 3276 [RFC3276] describes objects used
discussed in the MIB-2 Integration (RFC 3418 [RFC3418] and RFC 2863 for managing High Bit-Rate DSL - 2nd generation (HDSL2) [T1E1.4] and
[RFC2863]) section of this document. Single-Pair High-Speed Digital Subscriber Line (SHDSL) interfaces
[G.991.2]. These object descriptions are based upon the
specifications for the HDSL2 and SHDSL Embedded Operations Channel
(EOC) as defined in American National Standards Institute (ANSI)
T1E1.4/2000-006 [T1E1.4] and International Telecommunication Union
(ITU) G.991.2 [G.991.2].
3.1 Relationship of the HDSL2/SHDSL Line MIB to other MIBs This document obsoletes RFC 3276 [RFC3276] which supports G.shdsl in
that the MIB module described herein supports G.shdsl.bis as
described in the G.991.2 [G.991.2]. In addition, objects have been
added to improve the management of SHDSL lines.
This section outlines the relationship of this MIB with other MIBs The MIB module is located in the MIB tree under MIB 2 transmission,
described in RFCs. Specifically, IF-MIB as presented in RFC 2863 as discussed in the MIB-2 Integration (RFC 2863 [RFC2863]) section of
[RFC2863] is discussed. this document.
3.1.1 General IF-MIB Integration (RFC 2863) 2.1 Relationship to other MIBs
This section outlines the relationship of this MIB module with other
MIB modules described in RFCs. Specifically, IF-MIB as presented in
RFC 2863 [RFC2863] is discussed.
2.1.1 General IF-MIB Integration (RFC 2863)
The HDSL2/SHDSL Line MIB specifies the detailed attributes of a data The HDSL2/SHDSL Line MIB specifies the detailed attributes of a data
interface. As such, it needs to integrate with RFC 2863 [RFC2863]. interface. As such, it needs to integrate with RFC 2863 [RFC2863].
The IANA has assigned the following ifTypes to HDSL2 and SHDSL: The IANA has assigned the following ifTypes to HDSL2 and SHDSL:
IANAifType ::= TEXTUAL-CONVENTION IANAifType ::= TEXTUAL-CONVENTION
... ...
SYNTAX INTEGER { SYNTAX INTEGER {
... ...
hdsl2 (168), -- High Bit-Rate DSL, 2nd generation hdsl2 (168), -- High Bit-Rate DSL, 2nd generation
shdsl (169), -- Multirate HDSL2 shdsl (169), -- Multirate HDSL2
... ...
} }
Note that the ifFixedLengthGroup from RFC 2863 [RFC2863] MUST be Note that the ifFixedLengthGroup from RFC 2863 [RFC2863] MUST be
supported and that the ifRcvAddressGroup does not apply to this MIB. supported and that the ifRcvAddressGroup does not apply to this MIB
module.
3.1.2 Usage of ifTable 2.1.2 Usage of ifTable
The MIB branch identified by this ifType contains tables appropriate The MIB branch identified by this ifType contains tables appropriate
for this interface type. Most such tables extend the ifEntry table, for this interface type. Most such tables extend the ifEntry table,
and are indexed by ifIndex. For interfaces in systems implementing and are indexed by ifIndex. For interfaces in systems implementing
this MIB, those table entries indexed by ifIndex MUST be persistent. this MIB module, those table entries indexed by ifIndex MUST be
persistent.
The following attributes are part of the mandatory The following attributes are part of the mandatory
ifGeneralInformationGroup in RFC 2863 [RFC2863], and are not ifGeneralInformationGroup in RFC 2863 [RFC2863], and are not
duplicated in the HDSL2/SHDSL Line MIB. duplicated in the HDSL2/SHDSL Line MIB.
=================================================================== ===================================================================
ifIndex Interface index. ifIndex Interface index.
ifDescr See interfaces MIB [RFC2863]. ifDescr See interfaces MIB [RFC2863].
skipping to change at page 5, line 40 skipping to change at page 5, line 40
ifLinkUpDownTrapEnable Default to enabled(1). ifLinkUpDownTrapEnable Default to enabled(1).
ifHighSpeed Set as appropriate. ifHighSpeed Set as appropriate.
(For HDSL2 lines, this is fixed at 2) (For HDSL2 lines, this is fixed at 2)
ifConnectorPresent Set as appropriate. ifConnectorPresent Set as appropriate.
=================================================================== ===================================================================
Figure 1: Use of ifTable Objects Figure 1: Use of ifTable Objects
3.2 IANA Considerations 2.2 IANA Considerations
The HDSL2-SHDSL-LINE-MIB module requires the allocation of a single The HDSL2-SHDSL-LINE-MIB module requires the allocation of a single
object identifier for its MODULE-IDENTITY. The IANA has allocated object identifier for its MODULE-IDENTITY. The IANA has allocated
this object identifier in the transmission subtree (48), defined in this object identifier in the transmission subtree (48), defined in
the SNMPv2-SMI MIB module. the SNMPv2-SMI MIB module.
The assignment was in fact done when RFC 3276 was published, and this The assignment was in fact done when RFC 3276 was published, and this
revision of the RFC does not require any new action from IANA. revision of the RFC does not require any new action from IANA.
4. Conventions used in the MIB 2.3 Conventions used in the MIB Module
4.1 Naming Conventions 2.3.1 Naming Conventions
A. xtuC refers to a central site terminal unit; A. xtuC refers to a central site terminal unit;
H2TU-C for HDSL2, or STU-C for SHDSL. H2TU-C for HDSL2, or STU-C for SHDSL.
B. xtuR refers to a remote site terminal unit; B. xtuR refers to a remote site terminal unit;
H2TU-R for HDSL2, or STU-R for SHDSL. H2TU-R for HDSL2, or STU-R for SHDSL.
C. xtu refers to a terminal unit; either an xtuC or xtuR. C. xtu refers to a terminal unit; either an xtuC or xtuR.
D. xru refer to a regenerator unit; D. xru refer to a regenerator unit;
H2RU for HDSL2, or SRU for SHDSL. H2RU for HDSL2, or SRU for SHDSL.
E. xU refers to any HDSL2/SHDSL unit; either an xtu or xru. E. xU refers to any HDSL2/SHDSL unit; either an xtu or xru.
F. CRC is cyclic redundancy check [G.991.2]. F. CRC is cyclic redundancy check [G.991.2].
G. ES means errored second [G.991.2]. G. ES means errored second [G.991.2].
J. LOSW means loss of sync word [G.991.2]. J. LOSW means loss of sync word [G.991.2].
I. LOSWS means LOSW seconds [G.991.2]. I. LOSWS means LOSW seconds [G.991.2].
J. SES means severely errored second [G.991.2]. J. SES means severely errored second [G.991.2].
K. SNR means signal-to-noise ratio [G.991.2]. K. SNR means signal-to-noise ratio [G.991.2].
L. UAS means unavailable second [G.991.2]. L. UAS means unavailable second [G.991.2].
4.2 Textual Conventions 2.3.2 Textual Conventions
The following textual conventions are defined to reflect the line The following textual conventions are defined to reflect the line
topology in the MIB (further discussed in the following section) and topology in the MIB module (further discussed in the following
to define the behavior of the statistics to be maintained by an section) and to define the behavior of the statistics to be
agent. maintained by an agent.
o Hdsl2ShdslUnitId: o Hdsl2ShdslUnitId:
Attributes with this syntax uniquely identify each unit in a Attributes with this syntax uniquely identify each unit in a
HDSL2/SHDSL span. It mirrors the EOC addressing mechanism: HDSL2/SHDSL span. It mirrors the EOC addressing mechanism:
xtuC(1) - central office (CO) terminal unit xtuC(1) - central office (CO) terminal unit
xtuR(2) - customer premises equipment (CPE) xtuR(2) - customer premises equipment (CPE)
terminal unit terminal unit
xru1(3) .. xru8(10) - regenerators, numbered from xru1(3) .. xru8(10) - regenerators, numbered from
skipping to change at page 7, line 23 skipping to change at page 7, line 23
Attributes with this syntax specify the regional setting for a Attributes with this syntax specify the regional setting for a
SHDSL line. Specified as a BITS construct, the two mode types SHDSL line. Specified as a BITS construct, the two mode types
are: are:
region1 - ITU-T G.991.2 Annex A region1 - ITU-T G.991.2 Annex A
region2 - ITU-T G.991.2 Annex B region2 - ITU-T G.991.2 Annex B
o Hdsl2ShdslPerfCurrDayCount: o Hdsl2ShdslPerfCurrDayCount:
Attributes with this syntax define the behavior of the 1-day (24 Attributes with this syntax define the behavior of the 1-day (24
hour) gauges found in the MIB. hour) gauges found in the MIB module.
o Hdsl2Shdsl1DayIntervalCount: o Hdsl2Shdsl1DayIntervalCount:
Attributes with this syntax define the behavior of the 1-day (24 Attributes with this syntax define the behavior of the 1-day (24
hour) interval counters found in the MIB. hour) interval counters found in the MIB module.
o Hdsl2ShdslPerfTimeElapsed: o Hdsl2ShdslPerfTimeElapsed:
Attributes with this syntax define the behavior of the elapsed Attributes with this syntax define the behavior of the elapsed
time counters found in the MIB. time counters found in the MIB module.
o Hdsl2ShdslPerfIntervalThreshold: o Hdsl2ShdslPerfIntervalThreshold:
Attributes with this syntax define the behavior of the alarm Attributes with this syntax define the behavior of the alarm
thresholds found in the MIB. thresholds found in the MIB module.
o Hdsl2ShdslClockReferenceType: o Hdsl2ShdslClockReferenceType:
Attributes with this syntax define the clock references for the Attributes with this syntax define the clock references for the
HDSL2/SHDSL span. HDSL2/SHDSL span.
4.3 Structure 2.4 Structure
The MIB is structured into following MIB groups: The MIB module is structured into following MIB groups:
o Span Configuration Group: o Span Configuration Group:
This group supports MIB objects for configuring parameters for the This group supports MIB objects for configuring parameters for the
HDSL2/SHDSL span. It contains the following table: HDSL2/SHDSL span. It contains the following table:
- hdsl2ShdslSpanConfTable - hdsl2ShdslSpanConfTable
o Span Status Group: o Span Status Group:
skipping to change at page 8, line 32 skipping to change at page 8, line 32
o Segment Endpoint Configuration Group: o Segment Endpoint Configuration Group:
This group supports MIB objects for configuring parameters for the This group supports MIB objects for configuring parameters for the
HDSL2/SHDSL segment endpoints. It contains the following table: HDSL2/SHDSL segment endpoints. It contains the following table:
- hdsl2ShdslEndpointConfTable - hdsl2ShdslEndpointConfTable
o Segment Endpoint Current Status/Performance Group: o Segment Endpoint Current Status/Performance Group:
This group supports MIB objects that provide the current This group supports MIB objects that provide the current status/
status/performance information relating to segment endpoints. It performance information relating to segment endpoints. It
contains the following table: contains the following table:
- hdsl2ShdslEndpointCurrTable - hdsl2ShdslEndpointCurrTable
o Segment Endpoint 15-Minute Interval Status/Performance Group: o Segment Endpoint 15-Minute Interval Status/Performance Group:
This group supports MIB objects that provide historic This group supports MIB objects that provide historic status/
status/performance information relating to segment endpoints in performance information relating to segment endpoints in 15-minute
15-minute intervals. It contains the following table: intervals. It contains the following table:
- hdsl2Shdsl15MinIntervalTable - hdsl2Shdsl15MinIntervalTable
o Segment Endpoint 1-Day Interval Status/Performance Group: o Segment Endpoint 1-Day Interval Status/Performance Group:
This group supports MIB objects that provide historic This group supports MIB objects that provide historic status/
status/performance information relating to segment endpoints in performance information relating to segment endpoints in 1-day
1-day intervals. It contains the following table: intervals. It contains the following table:
- hdsl2Shdsl1DayIntervalTable - hdsl2Shdsl1DayIntervalTable
o Maintenance Group: o Maintenance Group:
This group supports MIB objects for performing maintenance This group supports MIB objects for performing maintenance
operations such as loopbacks for HDSL2/SHDSL lines. It contains operations such as loopbacks for HDSL2/SHDSL lines. It contains
the following table(s): the following table(s):
- hdsl2ShdslEndpointMaintTable - hdsl2ShdslEndpointMaintTable
skipping to change at page 10, line 6 skipping to change at page 10, line 6
- hdsl2ShdslLoopbackFailure - hdsl2ShdslLoopbackFailure
- hdsl2ShdslpowerBackoff - hdsl2ShdslpowerBackoff
- hdsl2ShdsldeviceFault - hdsl2ShdsldeviceFault
- hdsl2ShdsldcContinuityFault - hdsl2ShdsldcContinuityFault
- hdsl2ShdslconfigInitFailure - hdsl2ShdslconfigInitFailure
- hdsl2ShdslprotocolInitFailure - hdsl2ShdslprotocolInitFailure
- hdsl2ShdslnoNeighborPresent - hdsl2ShdslnoNeighborPresent
- hdsl2ShdslLocalPowerLoss - hdsl2ShdslLocalPowerLoss
o SHDSL Wire Pair Group: o SHDSL Wire Pair Group:
This group supports MIB objects which provide status of the This group supports MIB objects which provide status of the SHDSL-
SHDSL-specific wire pairs. specific wire pairs.
- hdsl2ShdslEndpointCurrTipRingReversal - hdsl2ShdslEndpointCurrTipRingReversal
- hdsl2ShdslEndpointCurrActivationState - hdsl2ShdslEndpointCurrActivationState
o Payload Group: o Payload Group:
This group supports MIB objects for retrieving payload rates which This group supports MIB objects for retrieving payload rates which
excludes any framing overhead. excludes any framing overhead.
- hdsl2ShdslStatusMaxAttainablePayloadRate - hdsl2ShdslStatusMaxAttainablePayloadRate
- hdsl2ShdslStatusActualPayloadRate - hdsl2ShdslStatusActualPayloadRate
4.3.1 Line Topology 2.5 Line Topology
An HDSL2/SHDSL Line consists of a minimum of two units - xtuC (the An HDSL2/SHDSL Line consists of a minimum of two units - xtuC (the
central termination unit) and an xtuR (the remote termination unit). central termination unit) and an xtuR (the remote termination unit).
The line may optionally support up to 8 repeater/regenerator units The line may optionally support up to 8 repeater/regenerator units
(xru) as shown in the figure below. (xru) as shown in the figure below.
<-- Network Side Customer Side --> <-- Network Side Customer Side -->
|</////////////////// HDSL2/SHDSL Span ////////////////////>| |</////////////////// HDSL2/SHDSL Span ////////////////////>|
skipping to change at page 11, line 5 skipping to change at page 11, line 5
Key: <////> HDSL2/SHDSL Span Key: <////> HDSL2/SHDSL Span
<~~~~> HDSL2/SHDSL Segment <~~~~> HDSL2/SHDSL Segment
=1= HDSL2/SHDSL wire-pair-1 =1= HDSL2/SHDSL wire-pair-1
=2= SHDSL optional wire-pair-2 (Not applicable to HDSL2) =2= SHDSL optional wire-pair-2 (Not applicable to HDSL2)
C Customer Side Segment Endpoint (modem) C Customer Side Segment Endpoint (modem)
N Network Side Segment Endpoint (modem) N Network Side Segment Endpoint (modem)
Figure 2: General topology for an HDSL2/SHDSL Line Figure 2: General topology for an HDSL2/SHDSL Line
4.4 Counters, Interval Buckets and Thresholds 2.6 Counters, Interval Buckets and Thresholds
For SNR Margin, Loop Attenuation, ES, SES, CRC anomalies, LOSW, and For SNR Margin, Loop Attenuation, ES, SES, CRC anomalies, LOSW, and
UAS, there are event counters, current 15-minute and 0 to 96 UAS, there are event counters, current 15-minute and 0 to 96 15-
15-minute history bucket(s) of "interval-counters", as well as minute history bucket(s) of "interval-counters", as well as current
current and 0 to 30 previous 1-day interval-counter(s). Each current and 0 to 30 previous 1-day interval-counter(s). Each current 15-
15-minute event bucket has an associated threshold notification. minute event bucket has an associated threshold notification.
Unlike RFC 3593 [RFC3593] and RFC 2662 [RFC2662], there is no Unlike RFC 3593 [RFC3593] and RFC 2662 [RFC2662], there is no
representation in the MIB for invalid buckets. In those cases where representation in the MIB module for invalid buckets. In those cases
the data for an interval is suspect or known to be invalid, the agent where the data for an interval is suspect or known to be invalid, the
MUST NOT report the interval. If the current 15-minute event bucket agent MUST NOT report the interval. If the current 15-minute event
is determined to be invalid, notifications based upon the value of bucket is determined to be invalid, notifications based upon the
the event bucket MUST NOT be generated. value of the event bucket MUST NOT be generated.
Not reporting an interval will result in holes in the associated Not reporting an interval will result in holes in the associated
table. For example, the table, hdsl2Shdsl15MinIntervalTable, is table. For example, the table, hdsl2Shdsl15MinIntervalTable, is
indexed by { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide, indexed by { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide,
hdsl2ShdslEndpointWirePair, hdsl2Shdsl15MinIntervalNumber}. If hdsl2ShdslEndpointWirePair, hdsl2Shdsl15MinIntervalNumber}. If
interval 12 is determined to be invalid but intervals 11 and 13 are interval 12 is determined to be invalid but intervals 11 and 13 are
valid, a Get Next operation on the indices .1.1.1.1.11 would return valid, a Get Next operation on the indices .1.1.1.1.11 would return
indices .1.1.1.1.13. indices .1.1.1.1.13.
There is no requirement for an agent to ensure a fixed relationship There is no requirement for an agent to ensure a fixed relationship
between the start of a fifteen minute interval and any wall clock; between the start of a fifteen minute interval and any wall clock;
however some implementations may align the fifteen minute intervals however some implementations may align the fifteen minute intervals
with quarter hours. Likewise, an implementation may choose to align with quarter hours. Likewise, an implementation may choose to align
one day intervals with the start of a day. one day intervals with the start of a day.
Counters are not reset when an xU is reinitialized, only when the Counters are not reset when an xU is reinitialized, only when the
agent is reset or reinitialized (or under specific request outside agent is reset or reinitialized (or under specific request outside
the scope of this MIB). the scope of this MIB module).
4.5 Profiles 2.7 Profiles
As a managed node can handle a large number of xUs, (e.g., hundreds As a managed node can handle a large number of xUs, (e.g., hundreds
or perhaps thousands of lines), provisioning every parameter on every or perhaps thousands of lines), provisioning every parameter on every
xU may become burdensome. Moreover, most lines are provisioned xU may become burdensome. Moreover, most lines are provisioned
identically with the same set of parameters. To simplify the identically with the same set of parameters. To simplify the
provisioning process, this MIB makes use of profiles. A profile is a provisioning process, this MIB module makes use of profiles. A
set of parameters that can be shared by multiple lines using the same profile is a set of parameters that can be shared by multiple lines
configuration. using the same configuration.
The following profiles are used in this MIB: The following profiles are used in this MIB module:
o Span Configuration Profiles - Span configuration profiles contain o Span Configuration Profiles - Span configuration profiles contain
parameters for configuring HDSL2/SHDSL spans. They are defined in parameters for configuring HDSL2/SHDSL spans. They are defined in
the hdsl2ShdslSpanConfProfileTable. Since span configuration the hdsl2ShdslSpanConfProfileTable. Since span configuration
parameters are only applicable for SHDSL, the support for span parameters are only applicable for SHDSL, the support for span
configuration profiles are optional for HDSL2 interfaces. configuration profiles are optional for HDSL2 interfaces.
Note that the configuration of the span dictates the behavior for Note that the configuration of the span dictates the behavior for
each individual segment endpoint in the span. If a different each individual segment endpoint in the span. If a different
configuration is provisioned for any given segment endpoint within configuration is provisioned for any given segment endpoint within
the span, the new configuration for this segment endpoint will the span, the new configuration for this segment endpoint will
override the span configuration for this segment endpoint only. override the span configuration for this segment endpoint only.
o Segment Endpoint Alarm Configuration Profiles - These profiles o Segment Endpoint Alarm Configuration Profiles - These profiles
contain parameters for configuring alarm thresholds for contain parameters for configuring alarm thresholds for HDSL2/
HDSL2/SHDSL segment endpoints. These profiles are defined in the SHDSL segment endpoints. These profiles are defined in the
hdsl2ShdslEndpointAlarmConfProfileTable. hdsl2ShdslEndpointAlarmConfProfileTable.
The index value for this profile is a locally-unique The index value for this profile is a locally-unique
administratively assigned name for the profile having the textual administratively assigned name for the profile having the textual
convention 'SnmpAdminString' (RFC 3411 [RFC3411]). convention 'SnmpAdminString' (RFC 3411 [RFC3411]).
One or more lines may be configured to share parameters of a single One or more lines may be configured to share parameters of a single
profile (e.g., hdsl2ShdslEndpointAlarmConfProfile = 'silver') by profile (e.g., hdsl2ShdslEndpointAlarmConfProfile = 'silver') by
setting its hdsl2ShdslEndpointAlarmConfProfile objects to the value setting its hdsl2ShdslEndpointAlarmConfProfile objects to the value
of this profile. If a change is made to the profile, all lines that of this profile. If a change is made to the profile, all lines that
skipping to change at page 12, line 37 skipping to change at page 12, line 37
profile can be deleted or taken out of service it must be first profile can be deleted or taken out of service it must be first
unreferenced from all associated lines. unreferenced from all associated lines.
Implementations MUST provide a default profile whose name is 'DEFVAL' Implementations MUST provide a default profile whose name is 'DEFVAL'
for each profile type. The values of the associated parameters will for each profile type. The values of the associated parameters will
be vendor specific unless otherwise indicated in this document. be vendor specific unless otherwise indicated in this document.
Before a line's profiles have been set, these profiles will be Before a line's profiles have been set, these profiles will be
automatically used by setting hdsl2ShdslEndpointAlarmConfProfile and automatically used by setting hdsl2ShdslEndpointAlarmConfProfile and
hdsl2ShdslSpanConfProfile to 'DEFVAL' where appropriate. This hdsl2ShdslSpanConfProfile to 'DEFVAL' where appropriate. This
default profile name, 'DEFVAL', is considered reserved in the context default profile name, 'DEFVAL', is considered reserved in the context
of profiles defined in this MIB. of profiles defined in this MIB module.
Profiles are created, assigned, and deleted dynamically using the Profiles are created, assigned, and deleted dynamically using the
profile name and profile row status in each of the four profile profile name and profile row status in each of the four profile
tables. tables.
Profile changes MUST take effect immediately. These changes MAY Profile changes MUST take effect immediately. These changes MAY
result in a restart (hard reset or soft restart) of the units on the result in a restart (hard reset or soft restart) of the units on the
line. line.
4.6 Notifications 2.8 Notifications
The ability to generate the SNMP notifications coldStart/WarmStart The ability to generate the SNMP notifications coldStart/WarmStart
(per [RFC3418]) which are per agent (e.g., per Digital Subscriber (per [RFC3418]) which are per agent (e.g., per Digital Subscriber
Line Access Multiplexer, or DSLAM, in such a device), and Line Access Multiplexer, or DSLAM, in such a device), and linkUp/
linkUp/linkDown (per [RFC2863]) which are per interface (i.e., linkDown (per [RFC2863]) which are per interface (i.e., HDSL2/SHDSL
HDSL2/SHDSL line) is required. line) is required.
A linkDown notification MAY be generated whenever any of ES, SES, CRC A linkDown notification MAY be generated whenever any of ES, SES, CRC
Anomaly, LOSW, or UAS event occurs. The corresponding linkUp Anomaly, LOSW, or UAS event occurs. The corresponding linkUp
notification MAY be sent when all link failure conditions are notification MAY be sent when all link failure conditions are
cleared. cleared.
The notifications defined in this MIB are for initialization failure The notifications defined in this MIB module are for initialization
and for the threshold crossings associated with the following events: failure and for the threshold crossings associated with the following
ES, SES, CRC Anomaly, LOSW, and UAS. Each threshold has its own events: ES, SES, CRC Anomaly, LOSW, and UAS. Each threshold has its
enable/threshold value. When that value is 0, the notification is own enable/threshold value. When that value is 0, the notification
disabled. is disabled.
The hdsl2ShdslEndpointCurrStatus is a bitmask representing all The hdsl2ShdslEndpointCurrStatus is a bitmask representing all
outstanding error conditions associated with a particular Segment outstanding error conditions associated with a particular Segment
Endpoint. Note that since status of remote endpoints is obtained via Endpoint. Note that since status of remote endpoints is obtained via
the EOC, this information may be unavailable for units that are the EOC, this information may be unavailable for units that are
unreachable via EOC during a line error condition. Therefore, not unreachable via EOC during a line error condition. Therefore, not
all conditions may always be included in its current status. all conditions may always be included in its current status.
Notifications corresponding to the bit fields in this object are Notifications corresponding to the bit fields in this object are
defined. defined.
Two alarm conditions, SNR Margin Alarm and Loop Attenuation Alarm, Two alarm conditions, SNR Margin Alarm and Loop Attenuation Alarm,
are organized in a manner slightly different from that implied in the are organized in a manner slightly different from that implied in the
EOC specifications. In the MIB, these alarm conditions are tied to EOC specifications. In the MIB module, these alarm conditions are
the two thresholds hdsl2ShdslEndpointThreshSNRMargin and tied to the two thresholds hdsl2ShdslEndpointThreshSNRMargin and
hdsl2ShdslEndpointThreshLoopAttenuation found in the hdsl2ShdslEndpointThreshLoopAttenuation found in the
hdsl2ShdslEndpointAlarmConfProfileTable. In the EOC, the alarm hdsl2ShdslEndpointAlarmConfProfileTable. In the EOC, the alarm
conditions associated with these thresholds are per-unit. In the conditions associated with these thresholds are per-unit. In the MIB
MIB, these alarm conditions are per-endpoint. For terminal units, module, these alarm conditions are per-endpoint. For terminal units,
this has no impact. For repeaters, this implies an implementation this has no impact. For repeaters, this implies an implementation
variance where the agent in the terminal unit is responsible for variance where the agent in the terminal unit is responsible for
detecting a threshold crossing. As the reporting of a repeater detecting a threshold crossing. As the reporting of a repeater
detected alarm condition to the polling terminal unit occurs in the detected alarm condition to the polling terminal unit occurs in the
same EOC message as the reporting of the current SNR Margin and Loop same EOC message as the reporting of the current SNR Margin and Loop
Attenuation values, it is anticipated that this will have very little Attenuation values, it is anticipated that this will have very little
impact on agent implementation. impact on agent implementation.
A threshold notification occurs whenever the corresponding current A threshold notification occurs whenever the corresponding current
15-minute interval error counter becomes equal to, or exceeds the 15-minute interval error counter becomes equal to, or exceeds the
threshold value. Only one notification SHOULD be sent per interval threshold value. Only one notification SHOULD be sent per interval
per interface. Since the current 15-minute counter is reset to 0 per interface. Since the current 15-minute counter is reset to 0
every 15 minutes, and if the condition persists, the notification may every 15 minutes, and if the condition persists, the notification may
recur as often as every 15 minutes. For example, to get a recur as often as every 15 minutes. For example, to get a
notification whenever a "loss of" event occurs (but at most once notification whenever a "loss of" event occurs (but at most once
every 15 minutes), set the corresponding threshold to 1. The agent every 15 minutes), set the corresponding threshold to 1. The agent
will generate a notification when the event originally occurs. will generate a notification when the event originally occurs.
Notifications, other than the threshold notifications listed above, Notifications, other than the threshold notifications listed above,
SHOULD be rate limited (throttled) such that there is at least a SHOULD be rate limited (throttled) such that there is at least a one-
one-minute gap between the generation of consecutive notification of minute gap between the generation of consecutive notification of the
the same event. When notifications are rate limited, they are same event. When notifications are rate limited, they are dropped
dropped and not queued for sending at a future time. This is and not queued for sending at a future time. This is intended to be
intended to be a general rate-limiting statement for notifications a general rate-limiting statement for notifications that have no
that have no explicit rate limiting assertions in this document explicit rate limiting assertions in this document otherwise.
otherwise.
Note that the Network Management System, or NMS, may receive a Note that the Network Management System, or NMS, may receive a
linkDown notification, as well, if enabled (via linkDown notification, as well, if enabled (via
ifLinkUpDownTrapEnable [RFC2863]). At the beginning of the next 15 ifLinkUpDownTrapEnable [RFC2863]). At the beginning of the next 15
minute interval, the counter is reset. When the first second goes by minute interval, the counter is reset. When the first second goes by
and the event occurs, the current interval bucket will be 1, which and the event occurs, the current interval bucket will be 1, which
equals the threshold, and the notification will be sent again. equals the threshold, and the notification will be sent again.
A hdsl2ShdslSpanInvalidNumRepeaters notification may be generated A hdsl2ShdslSpanInvalidNumRepeaters notification may be generated
following completion of the discovery phase if the number of following completion of the discovery phase if the number of
repeaters discovered on the line differs from the number of repeaters repeaters discovered on the line differs from the number of repeaters
specified in hdsl2ShdslSpanConfNumRepeaters. For those conditions specified in hdsl2ShdslSpanConfNumRepeaters. For those conditions
where the number of provisioned repeaters is greater than those where the number of provisioned repeaters is greater than those
encountered during span discovery, all table entries associated with encountered during span discovery, all table entries associated with
the nonexistent repeaters are to be discarded. For those conditions the nonexistent repeaters are to be discarded. For those conditions
where the number of provisioned repeaters is less than those where the number of provisioned repeaters is less than those
encountered during span discovery, additional table entries are to be encountered during span discovery, additional table entries are to be
created using the default span configuration profile. created using the default span configuration profile.
5. Conformance and Compliance 3. Definitions
For both HDSL2 and SHDSL lines, the following group(s) are mandatory:
hdsl2ShdslSpanConfGroup
hdsl2ShdslSpanStatusGroup
hdsl2ShdslInventoryGroup
hdsl2ShdslEndpointConfGroup
hdsl2Shdsl15MinIntervalGroup
hdsl2Shdsl1DayIntervalGroup
hdsl2ShdslMaintenanceGroup
hdsl2ShdslEndpointAlarmConfGroup
hdsl2ShdslNotificationGroup
hdsl2ShdslWirePairGroup
hdsl2ShdslPayloadRateGroup
For HDSL2 lines, the following group(s) are optional:
hdsl2ShdslSpanConfProfileGroup
hdsl2ShdslSpanShdslStatusGroup
hdsl2ShdslWirePairGroup
hdsl2ShdslPayloadRateGroup
6. Definitions
HDSL2-SHDSL-LINE-MIB DEFINITIONS ::= BEGIN HDSL2-SHDSL-LINE-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
OBJECT-TYPE, OBJECT-TYPE,
Counter32, Counter32,
Unsigned32, Unsigned32,
Gauge32, Gauge32,
NOTIFICATION-TYPE, NOTIFICATION-TYPE,
skipping to change at page 15, line 36 skipping to change at page 15, line 12
PerfIntervalCount PerfIntervalCount
FROM PerfHist-TC-MIB FROM PerfHist-TC-MIB
SnmpAdminString SnmpAdminString
FROM SNMP-FRAMEWORK-MIB FROM SNMP-FRAMEWORK-MIB
MODULE-COMPLIANCE, MODULE-COMPLIANCE,
OBJECT-GROUP, OBJECT-GROUP,
NOTIFICATION-GROUP NOTIFICATION-GROUP
FROM SNMPv2-CONF; FROM SNMPv2-CONF;
hdsl2ShdslMIB MODULE-IDENTITY hdsl2ShdslMIB MODULE-IDENTITY
LAST-UPDATED "200503140000Z" -- March 14, 2005 LAST-UPDATED "200504130000Z" -- April 13, 2005
ORGANIZATION "ADSLMIB Working Group" ORGANIZATION "ADSLMIB Working Group"
CONTACT-INFO "WG-email: adslmib@ietf.org CONTACT-INFO "WG-email: adslmib@ietf.org
WG-URL: WG-URL:
http://www.ietf.org/html.charters/adslmib-charter.html http://www.ietf.org/html.charters/adslmib-charter.html
Info: https://www1.ietf.org/mailman/listinfo/adslmib Info: https://www1.ietf.org/mailman/listinfo/adslmib
Chair: Mike Sneed Chair: Mike Sneed
Postal: P.O. Box 37324 Postal: P.O. Box 37324
Raleigh NC 27627-7324 USA Raleigh NC 27627-7324 USA
Email: sneedmike@hotmail.com Email: sneedmike@hotmail.com
skipping to change at page 16, line 31 skipping to change at page 16, line 6
Alcatel USA Alcatel USA
Postal: 2912 Wake Forest Road Postal: 2912 Wake Forest Road
Raleigh, NC 27609-7860 USA Raleigh, NC 27609-7860 USA
Email: Rajesh.Abbi@alcatel.com Email: Rajesh.Abbi@alcatel.com
Phone: +1 919 850 6194" Phone: +1 919 850 6194"
DESCRIPTION DESCRIPTION
"This MIB module defines a collection of objects for managing "This MIB module defines a collection of objects for managing
HDSL2/SHDSL lines. An agent may reside at either end of the HDSL2/SHDSL lines. An agent may reside at either end of the
line, however the MIB is designed to require no management line, however the MIB module is designed to require no
communication between the modems beyond that inherent in the management communication between the modems beyond that
low-level EOC line protocol as defined in ANSI T1E1.4/2000-006 inherent in the low-level EOC line protocol as defined in
(for HDSL2 lines), or in ITU G.991.2 (for SHDSL lines). ANSI T1E1.4/2000-006 (for HDSL2 lines), or in ITU G.991.2
(for SHDSL lines).
Copyright (C) The Internet Society (2005). This version of Copyright (C) The Internet Society (2005). This version of
this MIB module is part of RFC xxxx; see the RFC itself for this MIB module is part of RFC xxxx; see the RFC itself for
full legal notices." full legal notices."
REVISION "200503140000Z" -- March 14, 2005 REVISION "200504130000Z" -- April 13, 2005
DESCRIPTION "This version, published as RFC xxxx. DESCRIPTION "This version, published as RFC xxxx.
The following changes have been made in this version: The following changes have been made in this version:
1. Added a 3rd and 4th wire pair. 1. Added a 3rd and 4th wire pair.
2. Modified all rates such that their rates are only 2. Modified all rates such that their rates are only
constrained by an unsigned 32-bit value and not by constrained by an unsigned 32-bit value and not by
what today's perceived technology limitations are. what today's perceived technology limitations are.
3. Clarified that the rates from RFC 3276 include 3. Clarified that the rates from RFC 3276 include
payload and any applicable framing and added payload and any applicable framing and added
objects for payload-only rates. objects for payload-only rates.
4. Added an object to indicate whether or not the 4. Added an object to indicate whether or not the
skipping to change at page 17, line 21 skipping to change at page 16, line 44
9. Some changes were due to IETF requirements and 9. Some changes were due to IETF requirements and
RFC generation tools." RFC generation tools."
REVISION "200205090000Z" -- May 9, 2002 REVISION "200205090000Z" -- May 9, 2002
DESCRIPTION "Initial version, published as RFC 3276." DESCRIPTION "Initial version, published as RFC 3276."
::= { transmission 48 } ::= { transmission 48 }
hdsl2ShdslMibObjects OBJECT IDENTIFIER ::= { hdsl2ShdslMIB 1 } hdsl2ShdslMibObjects OBJECT IDENTIFIER ::= { hdsl2ShdslMIB 1 }
-- Textual Conventions used in this MIB -- Textual Conventions used in this MIB module
-- --
Hdsl2ShdslPerfCurrDayCount ::= TEXTUAL-CONVENTION Hdsl2ShdslPerfCurrDayCount ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A gauge associated with interface performance measurements in "A gauge associated with interface performance measurements in
a current 1-day (24 hour) measurement interval. a current 1-day (24 hour) measurement interval.
The value of this gauge starts at zero at the beginning of an The value of this gauge starts at zero at the beginning of an
skipping to change at page 30, line 7 skipping to change at page 29, line 31
-- Segment Endpoint Current Status/Performance Group -- Segment Endpoint Current Status/Performance Group
-- --
hdsl2ShdslEndpointCurrTable OBJECT-TYPE hdsl2ShdslEndpointCurrTable OBJECT-TYPE
SYNTAX SEQUENCE OF Hdsl2ShdslEndpointCurrEntry SYNTAX SEQUENCE OF Hdsl2ShdslEndpointCurrEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains current status and performance information "This table contains current status and performance information
for segment endpoints in HDSL2/SHDSL Lines. As with other for segment endpoints in HDSL2/SHDSL Lines. As with other
tables in this MIB indexed by ifIndex, entries in this table tables in this MIB module indexed by ifIndex, entries in this
MUST be maintained in a persistent manner." table MUST be maintained in a persistent manner."
::= { hdsl2ShdslMibObjects 5 } ::= { hdsl2ShdslMibObjects 5 }
hdsl2ShdslEndpointCurrEntry OBJECT-TYPE hdsl2ShdslEndpointCurrEntry OBJECT-TYPE
SYNTAX Hdsl2ShdslEndpointCurrEntry SYNTAX Hdsl2ShdslEndpointCurrEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the hdsl2ShdslEndpointCurrTable. Each entry "An entry in the hdsl2ShdslEndpointCurrTable. Each entry
contains status and performance information relating to a contains status and performance information relating to a
single segment endpoint. It is indexed by the ifIndex of the single segment endpoint. It is indexed by the ifIndex of the
skipping to change at page 32, line 46 skipping to change at page 32, line 23
noNeighborPresent Endpoint failure during initialization noNeighborPresent Endpoint failure during initialization
due to no activation sequence detected due to no activation sequence detected
from paired endpoint. from paired endpoint.
loopbackActive A loopback is currently active at this loopbackActive A loopback is currently active at this
Segment Endpoint. Segment Endpoint.
This is intended to supplement ifOperStatus. Note that there This is intended to supplement ifOperStatus. Note that there
is a 1:1 relationship between the status bits defined in this is a 1:1 relationship between the status bits defined in this
object and the notification thresholds defined elsewhere in object and the notification thresholds defined elsewhere in
this MIB." this MIB module."
REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7" REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7"
::= { hdsl2ShdslEndpointCurrEntry 3 } ::= { hdsl2ShdslEndpointCurrEntry 3 }
hdsl2ShdslEndpointES OBJECT-TYPE hdsl2ShdslEndpointES OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of Errored Seconds (ES) on this endpoint since the xU "Count of Errored Seconds (ES) on this endpoint since the xU
skipping to change at page 58, line 50 skipping to change at page 58, line 23
hdsl2ShdslConformance OBJECT IDENTIFIER ::= { hdsl2ShdslMIB 3 } hdsl2ShdslConformance OBJECT IDENTIFIER ::= { hdsl2ShdslMIB 3 }
hdsl2ShdslGroups OBJECT IDENTIFIER ::= hdsl2ShdslGroups OBJECT IDENTIFIER ::=
{ hdsl2ShdslConformance 1 } { hdsl2ShdslConformance 1 }
hdsl2ShdslCompliances OBJECT IDENTIFIER ::= hdsl2ShdslCompliances OBJECT IDENTIFIER ::=
{ hdsl2ShdslConformance 2 } { hdsl2ShdslConformance 2 }
-- agent compliance statements -- agent compliance statements
hdsl2ShdslLineMibCompliance MODULE-COMPLIANCE hdsl2ShdslLineMibCompliance MODULE-COMPLIANCE
STATUS current STATUS deprecated
DESCRIPTION DESCRIPTION
"The section outlines compliance requirements for this MIB." "The compliance statement for SNMP entities which implement
HDSL2 and SHDSL. The version of SHDSL supported in this
compliance statement is g.shdsl.
**** This compliance statement is deprecated. ****"
MODULE MODULE
MANDATORY-GROUPS MANDATORY-GROUPS
{ {
hdsl2ShdslSpanConfGroup, hdsl2ShdslSpanConfGroup,
hdsl2ShdslSpanStatusGroup, hdsl2ShdslSpanStatusGroup,
hdsl2ShdslInventoryGroup, hdsl2ShdslInventoryGroup,
hdsl2ShdslEndpointConfGroup, hdsl2ShdslEndpointConfGroup,
hdsl2ShdslEndpointCurrGroup, hdsl2ShdslEndpointCurrGroup,
hdsl2Shdsl15MinIntervalGroup, hdsl2Shdsl15MinIntervalGroup,
hdsl2Shdsl1DayIntervalGroup, hdsl2Shdsl1DayIntervalGroup,
skipping to change at page 59, line 35 skipping to change at page 59, line 12
GROUP hdsl2ShdslSpanShdslStatusGroup GROUP hdsl2ShdslSpanShdslStatusGroup
DESCRIPTION DESCRIPTION
"Support for this group is only required for implementations "Support for this group is only required for implementations
supporting SHDSL lines." supporting SHDSL lines."
GROUP hdsl2ShdslSpanConfProfileGroup GROUP hdsl2ShdslSpanConfProfileGroup
DESCRIPTION DESCRIPTION
"Support for this group is only required for implementations "Support for this group is only required for implementations
supporting SHDSL lines." supporting SHDSL lines."
GROUP hdsl2ShdslWirePairGroup
DESCRIPTION
"Support for this group is only required for implementations
supporting SHDSL lines."
GROUP hdsl2ShdslPayloadRateGroup
DESCRIPTION
"Support for this group is only required for implementations
supporting SHDSL lines."
OBJECT hdsl2ShdslSpanConfWireInterface OBJECT hdsl2ShdslSpanConfWireInterface
SYNTAX INTEGER SYNTAX INTEGER
{ {
twoWire(1), twoWire(1),
fourWire(2) fourWire(2)
} }
DESCRIPTION DESCRIPTION
"An implementation only has to support the range as "An implementation only has to support the range as
applicable for the original g.shdsl specification defined applicable for the original g.shdsl specification defined
in RFC 3276." in RFC 3276."
skipping to change at page 60, line 37 skipping to change at page 60, line 4
in RFC 3276." in RFC 3276."
OBJECT hdsl2ShdslSpanConfMaxLineRate OBJECT hdsl2ShdslSpanConfMaxLineRate
SYNTAX Unsigned32(0..4112000) SYNTAX Unsigned32(0..4112000)
DESCRIPTION DESCRIPTION
"An implementation only has to support the range as "An implementation only has to support the range as
applicable for the original g.shdsl specification defined applicable for the original g.shdsl specification defined
in RFC 3276." in RFC 3276."
::= { hdsl2ShdslCompliances 1 } ::= { hdsl2ShdslCompliances 1 }
hdsl2GshdslbisLineMibCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities which implement
HDSL2 and SHDSL. The version of SHDSL supported in this
compliance statement is g.shdsl.bis."
MODULE
MANDATORY-GROUPS
{
hdsl2ShdslSpanConfGroup,
hdsl2ShdslSpanStatusGroup,
hdsl2ShdslInventoryGroup,
hdsl2ShdslEndpointConfGroup,
hdsl2ShdslEndpointCurrGroup,
hdsl2Shdsl15MinIntervalGroup,
hdsl2Shdsl1DayIntervalGroup,
hdsl2ShdslMaintenanceGroup,
hdsl2ShdslEndpointAlarmConfGroup,
hdsl2ShdslNotificationGroup
}
GROUP hdsl2ShdslInventoryShdslGroup
DESCRIPTION
"Support for this group is only required for implementations
supporting SHDSL lines."
GROUP hdsl2ShdslSpanShdslStatusGroup
DESCRIPTION
"Support for this group is only required for implementations
supporting SHDSL lines."
GROUP hdsl2ShdslSpanConfProfileGroup
DESCRIPTION
"Support for this group is only required for implementations
supporting SHDSL lines."
GROUP hdsl2ShdslWirePairGroup
DESCRIPTION
"Support for this group is only required for implementations
supporting SHDSL lines."
GROUP hdsl2ShdslPayloadRateGroup
DESCRIPTION
"Support for this group is only required for implementations
supporting SHDSL lines."
::= { hdsl2ShdslCompliances 2 }
-- units of conformance -- units of conformance
-- --
hdsl2ShdslSpanConfGroup OBJECT-GROUP hdsl2ShdslSpanConfGroup OBJECT-GROUP
OBJECTS OBJECTS
{ {
hdsl2ShdslSpanConfNumRepeaters, hdsl2ShdslSpanConfNumRepeaters,
hdsl2ShdslSpanConfProfile, hdsl2ShdslSpanConfProfile,
hdsl2ShdslSpanConfAlarmProfile hdsl2ShdslSpanConfAlarmProfile
} }
skipping to change at page 66, line 10 skipping to change at page 66, line 24
hdsl2ShdslStatusActualPayloadRate hdsl2ShdslStatusActualPayloadRate
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group supports object for retrieving payload rates "This group supports object for retrieving payload rates
which excludes any framing overhead." which excludes any framing overhead."
::= { hdsl2ShdslGroups 15 } ::= { hdsl2ShdslGroups 15 }
END END
7. Implementation Analysis 4. Implementation Analysis
A management application which supports RFC 3276 could mistakenly A management application which supports RFC 3276 could mistakenly
flag a unit which responds with a rate or wire pair which exceeds the flag a unit which responds with a rate or wire pair which exceeds the
ranges and/or enumerations specified in RFC 3276. For example, a ranges and/or enumerations specified in RFC 3276. For example, a
G.shdsl.bis line with four wire pairs would report statistics for G.shdsl.bis line with four wire pairs would report statistics for
wire pairs that do not exist in RFC 3276. That is, a GET-NEXT wire pairs that do not exist in RFC 3276. That is, a GET-NEXT
request issues with the object identifier: request issues with the object identifier:
hdsl2ShdslEndpointCurrAtn.1.1.1.2 hdsl2ShdslEndpointCurrAtn.1.1.1.2
skipping to change at page 66, line 43 skipping to change at page 67, line 11
A management application intended to manage G.shdsl.bis agents SHOULD A management application intended to manage G.shdsl.bis agents SHOULD
be modified to accept this sequence. be modified to accept this sequence.
One should note that this same unmodified management application is One should note that this same unmodified management application is
still capable of managing G.shdsl.bis agents albeit to the degree of still capable of managing G.shdsl.bis agents albeit to the degree of
G.SHDSL (non-bis) limitations. That is, it can create and monitor G.SHDSL (non-bis) limitations. That is, it can create and monitor
configurations limited to two wire pairs with an upper rate limit of configurations limited to two wire pairs with an upper rate limit of
4112000 bits/second. 4112000 bits/second.
8. Security Considerations 5. Security Considerations
There are a number of management objects defined in this MIB module There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-write and/or read-create. Such with a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. These are the tables and objects and their network operations. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
o hdsl2ShdslSpanConfTable o hdsl2ShdslSpanConfTable
skipping to change at page 70, line 16 skipping to change at page 70, line 36
result in a notification being suppressed. Suppressing or result in a notification being suppressed. Suppressing or
deferring a notification could prevent the timely delivery of deferring a notification could prevent the timely delivery of
important diagnostic information. Decreasing any of the threshold important diagnostic information. Decreasing any of the threshold
values could result in a notification being sent from the network values could result in a notification being sent from the network
falsely reporting a threshold crossing. falsely reporting a threshold crossing.
Changing a threshold value could also have an impact on the amount Changing a threshold value could also have an impact on the amount
of notifications the agent sends. This document adds a paragraph, of notifications the agent sends. This document adds a paragraph,
which was not in RFC 3276 [RFC3276], to the Notifications Section which was not in RFC 3276 [RFC3276], to the Notifications Section
which provides general guidance to the rate limiting of which provides general guidance to the rate limiting of
notifications. Agent implementations not adhering to the notifications. Agent implementations not adhering to the rate-
rate-limiting desires could result in notifications being limiting desires could result in notifications being generated at
generated at an uncontrolled rate. Illegitimate changes to a an uncontrolled rate. Illegitimate changes to a threshold value
threshold value could result in an undesired notification rate. could result in an undesired notification rate.
Unauthorized changes to row status could result in unwanted Unauthorized changes to row status could result in unwanted
profiles being created or brought into service. Also, changes to profiles being created or brought into service. Also, changes to
the row status could result in profiles being inadvertently the row status could result in profiles being inadvertently
deleted or taken out of service. deleted or taken out of service.
Some of the readable objects in this MIB module (i.e., objects with a Some of the readable objects in this MIB module (i.e., objects with a
MAX-ACCESS other than not-accessible) may be considered sensitive or MAX-ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments. It is thus important to vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly control even GET and/or NOTIFY access to these objects and possibly
skipping to change at page 71, line 25 skipping to change at page 71, line 43
authentication and privacy). authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
9. Acknowledgments 6. Acknowledgments
The authors are deeply grateful to the authors of the ADSL LINE MIB The authors are deeply grateful to the authors of the ADSL LINE MIB
(RFC 2662 [RFC2662]), Gregory Bathrick and Faye Ly, as much of the (RFC 2662 [RFC2662]), Gregory Bathrick and Faye Ly, as much of the
text and structure of this document originates in their documents. text and structure of this document originates in their documents.
The authors are also grateful to the authors of FR MFR MIB (RFC 3020 The authors are also grateful to the authors of FR MFR MIB (RFC 3020
[RFC3020]), Prayson Pate, Bob Lynch, and Kenneth Rehbehn, as the [RFC3020]), Prayson Pate, Bob Lynch, and Kenneth Rehbehn, as the
majority of the Security Considerations section was lifted from their majority of the Security Considerations section was lifted from their
document. document.
The authors also acknowledge the importance of the contributions and The authors also acknowledge the importance of the contributions and
suggestions regarding interface indexing structures received from suggestions regarding interface indexing structures received from
David Horton of CITR. David Horton of CITR.
The authors are extremely thankful to Bert Wijnen, Randy Presuhn, and The authors are extremely thankful to Bert Wijnen, Randy Presuhn, and
C. M. Heard for their extensive review and the many suggestions C. M. Heard for their extensive review and the many suggestions they
they provided. provided.
Other contributions were received from the following: Other contributions were received from the following:
Matt Beanland (Extel Communications) Matt Beanland (Extel Communications)
Philip Bergstresser (Adtran) Philip Bergstresser (Adtran)
Steve Blackwell (Centillium) Steve Blackwell (Centillium)
Umberto Bonollo (NEC Australia) Umberto Bonollo (NEC Australia)
John Egan (Metalink BroadBand) John Egan (Metalink BroadBand)
Yagal Hachmon (RAD) Yagal Hachmon (RAD)
Mark Johnson (Red Point) Mark Johnson (Red Point)
skipping to change at page 72, line 25 skipping to change at page 72, line 35
Lee Nipper (Verilink) Lee Nipper (Verilink)
Randy Presuhn (BMC Software) Randy Presuhn (BMC Software)
Katy Sherman (Orckit) Katy Sherman (Orckit)
Mike Sneed (ECI) Mike Sneed (ECI)
Jon Turney (DSL Solutions) Jon Turney (DSL Solutions)
Aron Wahl (Memotec) Aron Wahl (Memotec)
Jim Wilson (for Mindspeed) Jim Wilson (for Mindspeed)
Bert Wijnen (Lucent) Bert Wijnen (Lucent)
Michael Wrobel (Memotec) Michael Wrobel (Memotec)
10. References 7. References
10.1 Normative References 7.1 Normative References
[G.991.2] Blackwell, S., "Single-Pair High-Speed Digital Subscriber [G.991.2] Blackwell, S., "Single-Pair High-Speed Digital Subscriber
Line (SHDSL) Transceivers", ITU-T G.991.2, December 2003. Line (SHDSL) Transceivers", ITU-T G.991.2, December 2003.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Rose, M. and S. Waldbusser, "Structure of Management Schoenwaelder, Ed., "Structure of Management Information
Information Version 2 (SMIv2)", STD 58, RFC 2578, April Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Rose, M. and S. Waldbusser, "Textual Conventions for Schoenwaelder, Ed., "Textual Conventions for SMIv2",
SMIv2", STD 58, RFC 2579, April 1999. STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D. and J. Schoenwaelder, [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580, "Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999. April 1999.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, June 2000. MIB", RFC 2863, June 2000.
[RFC3411] Harrington, D., Presuhn, R. and B. Wijnen, "An [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An
Architecture for Describing Simple Network Management Architecture for Describing Simple Network Management
Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, Protocol (SNMP) Management Frameworks", STD 62, RFC 3411,
December 2002. December 2002.
[RFC3593] Tesink, K., "Textual Conventions for MIB Modules Using [RFC3593] Tesink, K., "Textual Conventions for MIB Modules Using
Performance History Based on 15 Minute Intervals", Performance History Based on 15 Minute Intervals",
RFC 3593, September 2003. RFC 3593, September 2003.
[T1E1.4] American National Standards Institute, "ANSI [T1E1.4] American National Standards Institute, "ANSI T1E1.4/
T1E1.4/2000-006", February 2000. 2000-006", February 2000.
10.2 Informative References 7.2 Informative References
[RFC2662] Bathrick, G. and F. Ly, "Definitions of Managed Objects [RFC2662] Bathrick, G. and F. Ly, "Definitions of Managed Objects
for the ADSL Lines", RFC 2662, August 1999. for the ADSL Lines", RFC 2662, August 1999.
[RFC3020] Pate, P., Lynch, B. and K. Rehbehn, "Definitions of [RFC3020] Pate, P., Lynch, B., and K. Rehbehn, "Definitions of
Managed Objects for Monitoring and Controlling the UNI/NNI Managed Objects for Monitoring and Controlling the UNI/NNI
Multilink Frame Relay Function", RFC 3020, December 2000. Multilink Frame Relay Function", RFC 3020, December 2000.
[RFC3276] Ray, B. and R. Abbi, "Definitions of Managed Objects for [RFC3276] Ray, B. and R. Abbi, "Definitions of Managed Objects for
High Bit-Rate DSL - 2nd generation (HDSL2) and Single-Pair High Bit-Rate DSL - 2nd generation (HDSL2) and Single-Pair
High-Speed Digital Subscriber Line (SHDSL) Lines High-Speed Digital Subscriber Line (SHDSL) Lines
Processing", RFC 3276, May 2002. Processing", RFC 3276, May 2002.
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for "Introduction and Applicability Statements for Internet-
Internet-Standard Management Framework", RFC 3410, Standard Management Framework", RFC 3410, December 2002.
December 2002.
[RFC3418] Presuhn, R., "Management Information Base (MIB) for the [RFC3418] Presuhn, R., "Management Information Base (MIB) for the
Simple Network Management Protocol (SNMP)", STD 62, Simple Network Management Protocol (SNMP)", STD 62,
RFC 3418, December 2002. RFC 3418, December 2002.
Authors' Addresses Authors' Addresses
Clay Sikes Clay Sikes
Paradyne Corporation Paradyne Corporation
8454 126th Ave. N. 8454 126th Ave. N.
 End of changes. 

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