draft-ietf-adslmib-gshdslbis-11.txt   rfc4319.txt 
Network Working Group C. Sikes Network Working Group C. Sikes
Internet-Draft Paradyne Networks, Inc. Request for Comments: 4319 Zhone Technologies, Inc.
Expires: November 27, 2005 B. Ray Obsoletes: 3276 B. Ray
PESA Switching Systems, Inc. Category: Standards Track PESA Switching Systems, Inc.
R. Abbi R. Abbi
Alcatel USA Alcatel USA
May 26, 2005 December 2005
Definitions of Managed Objects for High Bit-Rate DSL - 2nd generation
(HDSL2) and Single-Pair High-Speed Digital Subscriber Line (SHDSL) Lines
draft-ietf-adslmib-gshdslbis-11.txt
Status of this Memo
By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at Definitions of Managed Objects for
http://www.ietf.org/ietf/1id-abstracts.txt. High Bit-Rate DSL - 2nd generation (HDSL2) and
Single-Pair High-Speed Digital Subscriber Line (SHDSL) Lines
The list of Internet-Draft Shadow Directories can be accessed at Status of This Memo
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on November 27, 2005. This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
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 Single- Digital Subscriber Line (DSL) - 2nd generation (HDSL2) and
Pair High-Speed Digital Subscriber Line (SHDSL) interfaces. This Single-Pair High-Speed Digital Subscriber Line (SHDSL) interfaces.
document introduces extensions to several objects and textual This 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. The Internet-Standard Management Framework . . . . . . . . . . 3 1. The Internet-Standard Management Framework ......................2
2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Overview ........................................................2
2.1 Relationship to other MIBs . . . . . . . . . . . . . . . . 3 2.1. Relationship to Other MIBs .................................3
2.2 IANA Considerations . . . . . . . . . . . . . . . . . . . 5 2.1.1. General IF-MIB Integration (RFC 2863) ...............3
2.3 Conventions used in the MIB Module . . . . . . . . . . . . 6 2.1.2. Usage of ifTable ....................................3
2.4 Structure . . . . . . . . . . . . . . . . . . . . . . . . 7 2.2. IANA Considerations ........................................4
2.5 Line Topology . . . . . . . . . . . . . . . . . . . . . . 10 2.3. Conventions Used in the MIB Module .........................5
2.6 Counters, Interval Buckets and Thresholds . . . . . . . . 11 2.3.1. Naming Conventions ..................................5
2.7 Profiles . . . . . . . . . . . . . . . . . . . . . . . . . 11 2.3.2. Textual Conventions .................................5
2.8 Notifications . . . . . . . . . . . . . . . . . . . . . . 12 2.4. Structure ..................................................7
3. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 14 2.5. Line Topology ..............................................9
4. Implementation Analysis . . . . . . . . . . . . . . . . . . . 66 2.6. Counters, Interval Buckets, and Thresholds ................10
5. Security Considerations . . . . . . . . . . . . . . . . . . . 67 2.7. Profiles ..................................................11
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 71 2.8. Notifications .............................................12
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 72 3. Definitions ....................................................14
7.1 Normative References . . . . . . . . . . . . . . . . . . . 72 4. Implementation Analysis ........................................66
7.2 Informative References . . . . . . . . . . . . . . . . . . 73 5. Security Considerations ........................................66
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 74 6. Acknowledgements ...............................................71
Intellectual Property and Copyright Statements . . . . . . . . 75 7. References .....................................................72
7.1. Normative References ......................................72
7.2. Informative References ....................................73
1. The Internet-Standard Management Framework 1. 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).
skipping to change at page 3, line 28 skipping to change at page 2, line 52
[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].
2. Overview 2. Overview
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 for use with network management protocols in the Internet community for
the purpose of managing HDSL2/SHDSL Lines. the purpose of managing HDSL2/SHDSL lines.
The MIB module described in RFC 3276 [RFC3276] describes objects used The MIB module described in RFC 3276 [RFC3276] describes objects used
for managing High Bit-Rate DSL - 2nd generation (HDSL2) [T1E1.4] and for managing High Bit-Rate DSL - 2nd generation (HDSL2) [T1E1.4] and
Single-Pair High-Speed Digital Subscriber Line (SHDSL) interfaces Single-Pair High-Speed Digital Subscriber Line (SHDSL) interfaces
[G.991.2]. These object descriptions are based upon the [G.991.2]. These object descriptions are based upon the
specifications for the HDSL2 and SHDSL Embedded Operations Channel specifications for the HDSL2 and SHDSL Embedded Operations Channel
(EOC) as defined in American National Standards Institute (ANSI) (EOC), as defined in the American National Standards Institute (ANSI)
T1E1.4/2000-006 [T1E1.4] and International Telecommunication Union T1E1.4/2000-006 [T1E1.4] and International Telecommunication Union
(ITU) G.991.2 [G.991.2]. (ITU) G.991.2 [G.991.2].
This document obsoletes RFC 3276 [RFC3276] which supports G.shdsl in This document obsoletes RFC 3276 [RFC3276], which supports G.shdsl in
that the MIB module described herein supports G.shdsl.bis as 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 described in the G.991.2 [G.991.2]. In addition, objects have been
added to improve the management of SHDSL lines. added to improve the management of SHDSL lines.
The MIB module is located in the MIB tree under MIB 2 transmission, The MIB module is located in the MIB tree under MIB 2 transmission,
as discussed in the MIB-2 Integration (RFC 2863 [RFC2863]) section of as discussed in the MIB-2 Integration (RFC 2863 [RFC2863]) section of
this document. this document.
2.1 Relationship to other MIBs 2.1. Relationship to Other MIBs
This section outlines the relationship of this MIB module with other This section outlines the relationship of this MIB module with other
MIB modules described in RFCs. Specifically, IF-MIB as presented in MIB modules described in RFCs. Specifically, the IF-MIB, as
RFC 2863 [RFC2863] is discussed. presented in RFC 2863 [RFC2863], is discussed.
2.1.1 General IF-MIB Integration (RFC 2863) 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. module.
2.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 module, those table entries indexed by ifIndex MUST be this MIB module, those table entries indexed by ifIndex MUST be
persistent. 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].
ifType hdsl2(168) or shdsl(169). ifType hdsl2(168) or shdsl(169).
ifSpeed Set as appropriate. ifSpeed Set as appropriate.
skipping to change at page 5, line 40 skipping to change at page 4, line 46
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
2.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.
2.3 Conventions used in the MIB Module 2.3. Conventions Used in the MIB Module
2.3.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].
2.3.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 module (further discussed in the following topology in the MIB module (further discussed in the following
section) and to define the behavior of the statistics to be section) and to define the behavior of the statistics to be
maintained by an 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 an
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
central office side central office side
o Hdsl2ShdslUnitSide: o Hdsl2ShdslUnitSide:
skipping to change at page 7, line 13 skipping to change at page 6, line 16
Attributes with this syntax reference the wire pairs connecting Attributes with this syntax reference the wire pairs connecting
the units: the units:
wirePair1(1) - First pair for HDSL2/SHDSL. wirePair1(1) - First pair for HDSL2/SHDSL.
wirePair2(2) - Optional second pair for SHDSL only. wirePair2(2) - Optional second pair for SHDSL only.
wirePair3(3) - Optional third pair for SHDSL.bis only. wirePair3(3) - Optional third pair for SHDSL.bis only.
wirePair4(4) - Optional fourth pair for SHDSL.bis only. wirePair4(4) - Optional fourth pair for SHDSL.bis only.
o Hdsl2ShdslTransmissionModeType: o Hdsl2ShdslTransmissionModeType:
Attributes with this syntax specify the regional setting for a Attributes with this syntax specify the regional setting for an
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 module. hour) gauges found in the MIB module.
skipping to change at page 7, line 45 skipping to change at page 7, line 5
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 module. 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.
2.4 Structure 2.4. Structure
The MIB module is structured into following MIB groups: The MIB module is structured into the 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 9, line 19 skipping to change at page 8, line 24
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
- hdsl2ShdslUnitMaintTable - hdsl2ShdslUnitMaintTable
o Span Configuration Profile Group: o Span Configuration Profile Group:
This group supports MIB objects for defining configuration This group supports MIB objects for defining configuration
profiles for HDSL2/SHDSL Spans. It contains the following table: profiles for HDSL2/SHDSL spans. It contains the following table:
- hdsl2ShdslSpanConfProfileTable - hdsl2ShdslSpanConfProfileTable
o Segment Endpoint Alarm Configuration Profile Group: o Segment Endpoint Alarm Configuration Profile Group:
This group supports MIB objects for defining alarm configuration This group supports MIB objects for defining alarm configuration
profiles for HDSL2/SHDSL Segment Endpoints. It contains the profiles for HDSL2/SHDSL segment endpoints. It contains the
following table: following table:
- hdsl2ShdslEndpointAlarmConfProfileTable - hdsl2ShdslEndpointAlarmConfProfileTable
o Notifications Group: o Notifications Group:
This group defines the notifications supported for HDSL2/SHDSL This group defines the notifications supported for HDSL2/SHDSL
lines: lines:
- hdsl2ShdslLoopAttenCrossing - hdsl2ShdslLoopAttenCrossing
skipping to change at page 10, line 4 skipping to change at page 9, line 9
- hdsl2ShdslPerfUASThresh - hdsl2ShdslPerfUASThresh
- hdsl2ShdslSpanInvalidNumRepeaters - hdsl2ShdslSpanInvalidNumRepeaters
- 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 SHDSL- This group supports MIB objects that provide status of the 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 that
excludes any framing overhead. exclude any framing overhead.
- hdsl2ShdslStatusMaxAttainablePayloadRate - hdsl2ShdslStatusMaxAttainablePayloadRate
- hdsl2ShdslStatusActualPayloadRate - hdsl2ShdslStatusActualPayloadRate
2.5 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 ////////////////////>|
<~~~> <~~~> HDSL2/SHDSL Segments <~~~> <~~~> <~~~> HDSL2/SHDSL Segments <~~~>
+-------+ +-------+ +-------+ +-------+ +-------+ +-------+ +-------+ +-------+ +-------+ +-------+
+ C=1=N C=1=N C=..1..=N C=1=N + + C=1=N C=1=N C=..1..=N C=1=N +
| xtuC | | xru1 | | xru2 | | xru8 | | xtuR | | xtuC | | xru1 | | xru2 | | xru8 | | xtuR |
+ C=2=N C=2=N C=..2..=N C=2=N + + C=2=N C=2=N C=..2..=N C=2=N +
+-------+ +-------+ +-------+ +-------+ +-------+ +-------+ +-------+ +-------+ +-------+ +-------+
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
2.6 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 15- UAS, there are event counters, current 15-minute and 0 to 96 15-
minute history bucket(s) of "interval-counters", as well as current minute history bucket(s) of "interval-counters", as well as current
and 0 to 30 previous 1-day interval-counter(s). Each current 15- and 0 to 30 previous 1-day interval-counter(s). Each current 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 module for invalid buckets. In those cases representation in the MIB module for invalid buckets. In those cases
where the data for an interval is suspect or known to be invalid, the where the data for an interval is suspect or known to be invalid, the
agent MUST NOT report the interval. If the current 15-minute event agent MUST NOT report the interval. If the current 15-minute event
bucket is determined to be invalid, notifications based upon the bucket is determined to be invalid, notifications based upon the
value of 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 15-minute interval and any wall clock;
however some implementations may align the fifteen minute intervals however, some implementations may align the 15-minute intervals with
with quarter hours. Likewise, an implementation may choose to align quarter hours. Likewise, an implementation may choose to align 1-day
one day intervals with the start of a 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 module). the scope of this MIB module).
2.7 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
or perhaps thousands of lines), provisioning every parameter on every perhaps thousands of lines), provisioning every parameter on every xU
xU may become burdensome. Moreover, most lines are provisioned 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 module makes use of profiles. A provisioning process, this MIB module makes use of profiles. A
profile is a set of parameters that can be shared by multiple lines profile is a set of parameters that can be shared by multiple lines
using the same configuration. using the same configuration.
The following profiles are used in this MIB module: 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 is 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 HDSL2/ contain parameters for configuring alarm thresholds for 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
refer to it will be reconfigured to the changed parameters. Before a refer to it will be reconfigured to the changed parameters. Before a
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 module. 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.
2.8 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 linkUp/ Line Access Multiplexer, or DSLAM, in such a device), and linkUp/
linkDown (per [RFC2863]) which are per interface (i.e., HDSL2/SHDSL linkDown (per [RFC2863]), which are per interface (i.e., 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 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 module are for initialization The notifications defined in this MIB module are for initialization
failure and for the threshold crossings associated with the following failure and for the threshold crossings associated with the following
events: ES, SES, CRC Anomaly, LOSW, and UAS. Each threshold has its events: ES, SES, CRC anomaly, LOSW, and UAS. Each threshold has its
own enable/threshold value. When that value is 0, the notification own enable/threshold value. When that value is 0, the notification
is 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 the status of remote endpoints is obtained
the EOC, this information may be unavailable for units that are via 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 module, these alarm conditions are EOC specifications. In the MIB module, these alarm conditions are
tied to 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 MIB conditions associated with these thresholds are per unit. In the MIB
module, 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 one- SHOULD be rate limited (throttled) such that there is at least a
minute gap between the generation of consecutive notification of the 1-minute gap between the generation of consecutive notifications of
same event. When notifications are rate limited, they are dropped the same event. When notifications are rate limited, they are
and not queued for sending at a future time. This is intended to be dropped and not queued for sending at a future time. This is
a general rate-limiting statement for notifications that have no intended to be a general rate-limiting statement for notifications
explicit rate limiting assertions in this document otherwise. that have no explicit rate-limiting assertions in this document
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
ifLinkUpDownTrapEnable [RFC2863]). At the beginning of the next 15 [RFC2863]). At the beginning of the next 15-minute interval, the
minute interval, the counter is reset. When the first second goes by counter is reset. When the first second goes by and the event
and the event occurs, the current interval bucket will be 1, which occurs, the current interval bucket will be 1, which equals the
equals the threshold, and the notification will be sent again. threshold, and the notification will be sent again.
A hdsl2ShdslSpanInvalidNumRepeaters notification may be generated An 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.
skipping to change at page 15, line 12 skipping to change at page 14, line 37
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 "200505260000Z" -- May 26, 2005 LAST-UPDATED "200512070000Z" -- December 7, 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 Sand Channel Systems
Raleigh NC 27627-7324 USA Postal: 1210-203 Westview Ln
Raleigh NC 27605 USA
Email: sneedmike@hotmail.com Email: sneedmike@hotmail.com
Phone: +1 206 600 7022
Co-Chair Bob Ray Co-Chair Bob Ray
PESA Switching Systems, Inc. PESA Switching Systems, Inc.
Postal 330-A Wynn Drive Postal 330-A Wynn Drive
Huntsville, AL 35805 USA Huntsville, AL 35805 USA
Phone +1 256 726 9200 ext. 142 Phone +1 256 726 9200 ext. 142
Co-editor: Clay Sikes Co-editor: Clay Sikes
Paradyne Networks, Inc. Zhone Technologies, Inc.
Postal: 8545 126th Ave. N. Postal: 8545 126th Ave. N.
Largo, FL 33772 USA Largo, FL 33772 USA
Email: csikes@paradyne.com Email: csikes@zhone.com
Phone: +1 727 530 8257 Phone: +1 727 530 8257
Co-editor: Bob Ray Co-editor: Bob Ray
PESA Switching Systems, Inc. PESA Switching Systems, Inc.
Postal: 330-A Wynn Drive Postal: 330-A Wynn Drive
Huntsville, AL 35805 USA Huntsville, AL 35805 USA
Email: rray@pesa.com Email: rray@pesa.com
Phone: +1 256 726 9200 ext. 142 Phone: +1 256 726 9200 ext. 142
Co-editor: Rajesh Abbi Co-editor: Rajesh Abbi
Alcatel USA Alcatel USA
Postal: 2912 Wake Forest Road Postal: 2301 Sugar Bush Road
Raleigh, NC 27609-7860 USA Raleigh, NC 27612-3339 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 module is designed to require no line; however, the MIB module is designed to require no
management communication between the modems beyond that management communication between the modems beyond that
inherent in the low-level EOC line protocol as defined in inherent in the low-level EOC line protocol as defined in
ANSI T1E1.4/2000-006 (for HDSL2 lines), or in ITU G.991.2 ANSI T1E1.4/2000-006 (for HDSL2 lines) or in ITU G.991.2
(for SHDSL lines). (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 4319; see the RFC itself for
full legal notices." full legal notices."
REVISION "200505260000Z" -- May 26, 2005 REVISION "200512070000Z" -- December 7, 2005
DESCRIPTION "This version, published as RFC xxxx. DESCRIPTION "This version, published as RFC 4319.
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 the
tip and ring are reversed on a wire pair. tip and ring are reversed on a wire pair.
5. Added an object to display the activation state 5. Added an object to display the activation state
of a wire pair. of a wire pair.
6. Added references as necessary for clarification. 6. Added references as necessary for clarification.
7. Added display hints to textual conventions as 7. Added display hints to textual conventions as
necessary. necessary.
8. Updated conformance statements as necessary. 8. Updated conformance statements as necessary.
9. Some changes were due to IETF requirements and 9. Some changes were due to IETF requirements and
RFC generation tools." RFC generation tools."
skipping to change at page 17, line 8 skipping to change at page 16, line 38
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
interval and is increased when associated events occur, until interval and is increased when associated events occur, until
the end of the 1-day interval. At that time the value of the the end of the 1-day interval. At that time, the value of the
gauge is stored in the previous 1-day history interval, as gauge is stored in the previous 1-day history interval, as
defined in a companion object of type defined in a companion object of type
Hdsl2Shdsl1DayIntevalCount, and the current interval gauge Hdsl2Shdsl1DayIntevalCount, and the current interval gauge
is restarted at zero. is restarted at zero.
In the case where the agent has no valid data available for In the case where the agent has no valid data available for
this interval the corresponding object instance is not this interval, the corresponding object instance is not
available and upon a retrieval request a corresponding error available, and upon a retrieval request, a corresponding error
message shall be returned to indicate that this instance does message shall be returned to indicate that this instance does
not exist. Please note that zero is a valid value." not exist. Please note that zero is a valid value."
SYNTAX Gauge32 SYNTAX Gauge32
Hdsl2Shdsl1DayIntervalCount ::= TEXTUAL-CONVENTION Hdsl2Shdsl1DayIntervalCount ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A counter associated with interface performance measurements "A counter associated with interface performance measurements
during the most previous 1-day (24 hour) measurement interval. during the most previous 1-day (24 hour) measurement interval.
The value of this gauge is equal to the value of the current The value of this gauge is equal to the value of the current
day gauge, as defined in a companion object of type day gauge, as defined in a companion object of type
Hdsl2ShdslPerfCurrDayCount, at the end of its most recent Hdsl2ShdslPerfCurrDayCount, at the end of its most recent
interval. interval.
In the case where the agent has no valid data available for In the case where the agent has no valid data available for
this interval the corresponding object instance is not this interval, the corresponding object instance is not
available and upon a retrieval request a corresponding error available, and upon a retrieval request, a corresponding error
message shall be returned to indicate that this instance does message shall be returned to indicate that this instance does
not exist." not exist."
SYNTAX Gauge32 SYNTAX Gauge32
Hdsl2ShdslPerfTimeElapsed ::= TEXTUAL-CONVENTION Hdsl2ShdslPerfTimeElapsed ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of seconds that have elapsed since the beginning of "The number of seconds that have elapsed since the beginning of
the current measurement period. If, for some reason, such as the current measurement period. If, for some reason, such as
an adjustment in the system's time-of-day clock or the addition an adjustment in the system's time-of-day clock or the addition
of a leap second, the current interval exceeds the maximum of a leap second, the current interval exceeds the maximum
value, the agent will return the maximum value. value, the agent will return the maximum value.
For 15 minute intervals, the range is limited to (0..899). For 15-minute intervals, the range is limited to (0..899).
For 24 hour intervals, the range is limited to (0..86399)." For 24-hour intervals, the range is limited to (0..86399)."
SYNTAX Unsigned32(0..86399) SYNTAX Unsigned32(0..86399)
Hdsl2ShdslPerfIntervalThreshold ::= TEXTUAL-CONVENTION Hdsl2ShdslPerfIntervalThreshold ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This convention defines a range of values that may be set in "This convention defines a range of values that may be set in
a fault threshold alarm control. As the number of seconds in a fault threshold alarm control. As the number of seconds in
a 15-minute interval numbers at most 900, objects of this type a 15-minute interval numbers at most 900, objects of this type
may have a range of 0...900, where the value of 0 disables the may have a range of 0...900, where the value of 0 disables the
alarm." alarm."
SYNTAX Unsigned32(0..900) SYNTAX Unsigned32(0..900)
skipping to change at page 18, line 18 skipping to change at page 17, line 48
"This convention defines a range of values that may be set in "This convention defines a range of values that may be set in
a fault threshold alarm control. As the number of seconds in a fault threshold alarm control. As the number of seconds in
a 15-minute interval numbers at most 900, objects of this type a 15-minute interval numbers at most 900, objects of this type
may have a range of 0...900, where the value of 0 disables the may have a range of 0...900, where the value of 0 disables the
alarm." alarm."
SYNTAX Unsigned32(0..900) SYNTAX Unsigned32(0..900)
Hdsl2ShdslUnitId ::= TEXTUAL-CONVENTION Hdsl2ShdslUnitId ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the unique identification for all units in a "This is the unique identification for all units in an
HDSL2/SHDSL Span. It is based on the EOC unit addressing HDSL2/SHDSL span. It is based on the EOC unit addressing
scheme with reference to the xtuC." scheme with reference to the xtuC."
SYNTAX INTEGER SYNTAX INTEGER
{ {
xtuC(1), xtuC(1),
xtuR(2), xtuR(2),
xru1(3), xru1(3),
xru2(4), xru2(4),
xru3(5), xru3(5),
xru4(6), xru4(6),
xru5(7), xru5(7),
xru6(8), xru6(8),
xru7(9), xru7(9),
xru8(10) xru8(10)
} }
Hdsl2ShdslUnitSide ::= TEXTUAL-CONVENTION Hdsl2ShdslUnitSide ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the referenced side of a HDSL2/SHDSL unit - Network "This is the referenced side of an HDSL2/SHDSL unit - Network
or Customer side. The side facing the Network is the Network or Customer side. The side facing the Network is the Network
side, while the side facing the Customer is the Customer side." side, while the side facing the Customer is the Customer side."
SYNTAX INTEGER SYNTAX INTEGER
{ {
networkSide(1), networkSide(1),
customerSide(2) customerSide(2)
} }
Hdsl2ShdslWirePair ::= TEXTUAL-CONVENTION Hdsl2ShdslWirePair ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the referenced pair of wires in a HDSL2/SHDSL Segment. "This is the referenced pair of wires in an HDSL2/SHDSL segment.
HDSL2 only supports a single pair (wirePair1 or two wire), HDSL2 only supports a single pair (wirePair1 or two wire),
SHDSL lines support an optional second pair (wirePair2 or four SHDSL lines support an optional second pair (wirePair2 or four
wire), and G.shdsl.bis support an optional third pair wire), and G.shdsl.bis support an optional third pair
(wirePair3 or six wire) and an optional fourth pair (wirePair3 or six wire) and an optional fourth pair
(wirePair4 or eight wire)." (wirePair4 or eight wire)."
SYNTAX INTEGER SYNTAX INTEGER
{ {
wirePair1(1), -- two wire wirePair1(1), -- two wire
wirePair2(2), -- four wire wirePair2(2), -- four wire
wirePair3(3), -- six wire wirePair3(3), -- six wire
wirePair4(4) -- eight wire wirePair4(4) -- eight wire
} }
Hdsl2ShdslTransmissionModeType ::= TEXTUAL-CONVENTION Hdsl2ShdslTransmissionModeType ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Contains the regional setting of the HDSL2/SHDSL span, "Contains the regional setting of the HDSL2/SHDSL span,
represented as a bit-map of possible settings. The various represented as a bit-map of possible settings. The various
bit positions are: bit positions are as follows:
Bit Meaning Description Bit Meaning Description
1 region 1 Indicates ITU-T G.991.2 Annex A. 1 region 1 Indicates ITU-T G.991.2 Annex A.
2 region 2 Indicates ITU-T G.991.2 Annex B." 2 region 2 Indicates ITU-T G.991.2 Annex B."
SYNTAX BITS SYNTAX BITS
{ {
region1(0), region1(0),
region2(1) region2(1)
} }
skipping to change at page 20, line 4 skipping to change at page 19, line 34
dataClk(4) -- Mode-3b per G991.2 dataClk(4) -- Mode-3b per G991.2
} }
-- Span Configuration Group -- Span Configuration Group
-- --
hdsl2ShdslSpanConfTable OBJECT-TYPE hdsl2ShdslSpanConfTable OBJECT-TYPE
SYNTAX SEQUENCE OF Hdsl2ShdslSpanConfEntry SYNTAX SEQUENCE OF Hdsl2ShdslSpanConfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table supports overall configuration of HDSL2/SHDSL "This table supports overall configuration of HDSL2/SHDSL
Spans. Entries in this table MUST be maintained in a spans. Entries in this table MUST be maintained in a
persistent manner." persistent manner."
::= { hdsl2ShdslMibObjects 1 } ::= { hdsl2ShdslMibObjects 1 }
hdsl2ShdslSpanConfEntry OBJECT-TYPE hdsl2ShdslSpanConfEntry OBJECT-TYPE
SYNTAX Hdsl2ShdslSpanConfEntry SYNTAX Hdsl2ShdslSpanConfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the hdsl2ShdslSpanConfTable. Each entry "An entry in the hdsl2ShdslSpanConfTable. Each entry
represents the complete Span in a single HDSL2/SHDSL line. represents the complete span in a single HDSL2/SHDSL line.
It is indexed by the ifIndex of the associated HDSL2/SHDSL It is indexed by the ifIndex of the associated HDSL2/SHDSL
line." line."
INDEX { ifIndex } INDEX { ifIndex }
::= { hdsl2ShdslSpanConfTable 1 } ::= { hdsl2ShdslSpanConfTable 1 }
Hdsl2ShdslSpanConfEntry ::= Hdsl2ShdslSpanConfEntry ::=
SEQUENCE SEQUENCE
{ {
hdsl2ShdslSpanConfNumRepeaters Unsigned32, hdsl2ShdslSpanConfNumRepeaters Unsigned32,
hdsl2ShdslSpanConfProfile SnmpAdminString, hdsl2ShdslSpanConfProfile SnmpAdminString,
hdsl2ShdslSpanConfAlarmProfile SnmpAdminString hdsl2ShdslSpanConfAlarmProfile SnmpAdminString
} }
hdsl2ShdslSpanConfNumRepeaters OBJECT-TYPE hdsl2ShdslSpanConfNumRepeaters OBJECT-TYPE
SYNTAX Unsigned32(0..8) SYNTAX Unsigned32(0..8)
skipping to change at page 20, line 37 skipping to change at page 20, line 19
hdsl2ShdslSpanConfAlarmProfile SnmpAdminString hdsl2ShdslSpanConfAlarmProfile SnmpAdminString
} }
hdsl2ShdslSpanConfNumRepeaters OBJECT-TYPE hdsl2ShdslSpanConfNumRepeaters OBJECT-TYPE
SYNTAX Unsigned32(0..8) SYNTAX Unsigned32(0..8)
UNITS "repeaters" UNITS "repeaters"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object provisions the number of repeaters/regenerators "This object provisions the number of repeaters/regenerators
in this HDSL2/SHDSL Span." in this HDSL2/SHDSL span."
::= { hdsl2ShdslSpanConfEntry 1 } ::= { hdsl2ShdslSpanConfEntry 1 }
hdsl2ShdslSpanConfProfile OBJECT-TYPE hdsl2ShdslSpanConfProfile OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE(1..32)) SYNTAX SnmpAdminString (SIZE(1..32))
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is a pointer to a span configuration profile in "This object is a pointer to a span configuration profile in
the hdsl2ShdslSpanConfProfileTable, which applies to this the hdsl2ShdslSpanConfProfileTable, which applies to this
span. The value of this object is the index of the referenced span. The value of this object is the index of the referenced
skipping to change at page 21, line 18 skipping to change at page 20, line 47
Any attempt to set this object to a value that is not the value Any attempt to set this object to a value that is not the value
of the index for an active entry in the profile table, of the index for an active entry in the profile table,
hdsl2ShdslSpanConfProfileTable, MUST be rejected." hdsl2ShdslSpanConfProfileTable, MUST be rejected."
::= { hdsl2ShdslSpanConfEntry 2 } ::= { hdsl2ShdslSpanConfEntry 2 }
hdsl2ShdslSpanConfAlarmProfile OBJECT-TYPE hdsl2ShdslSpanConfAlarmProfile OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE(1..32)) SYNTAX SnmpAdminString (SIZE(1..32))
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is a pointer to an Alarm configuration profile in "This object is a pointer to an alarm configuration profile in
the hdsl2ShdslEndpointAlarmConfProfileTable. The value of the hdsl2ShdslEndpointAlarmConfProfileTable. The value of
this object is the index of the referenced profile in the this object is the index of the referenced profile in the
hdsl2ShdslEndpointAlarmConfProfileTable. The alarm hdsl2ShdslEndpointAlarmConfProfileTable. The alarm
threshold configuration in the referenced profile will be threshold configuration in the referenced profile will be
used by default for all segment endpoints in this span. used by default for all segment endpoints in this span.
Individual endpoints may override this profile by explicitly Individual endpoints may override this profile by explicitly
specifying some other profile in the specifying some other profile in the
hdsl2ShdslEndpointConfTable. By default, this object will hdsl2ShdslEndpointConfTable. By default, this object will
have the value 'DEFVAL' (the index of the default have the value 'DEFVAL' (the index of the default
profile). profile).
skipping to change at page 23, line 49 skipping to change at page 23, line 30
-- Unit Inventory Group -- Unit Inventory Group
-- --
hdsl2ShdslInventoryTable OBJECT-TYPE hdsl2ShdslInventoryTable OBJECT-TYPE
SYNTAX SEQUENCE OF Hdsl2ShdslInventoryEntry SYNTAX SEQUENCE OF Hdsl2ShdslInventoryEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table supports retrieval of unit inventory information "This table supports retrieval of unit inventory information
available via the EOC from units in a HDSL2/SHDSL line. available via the EOC from units in an HDSL2/SHDSL line.
Entries in this table are dynamically created during the Entries in this table are dynamically created during the
line discovery process. The life cycle for these entries line discovery process. The life cycle for these entries
is as follows: is as follows:
- xtu discovers a device, either a far-end xtu or an xru - xtu discovers a device, either a far-end xtu or an xru
- an inventory table entry is created for the device - an inventory table entry is created for the device
- the line goes down for whatever reason - the line goes down for whatever reason
- inventory table entries for unreachable devices are - inventory table entries for unreachable devices are
destroyed. destroyed
As these entries are created/destroyed dynamically, they As these entries are created/destroyed dynamically, they
are NOT persistent." are NOT persistent."
::= { hdsl2ShdslMibObjects 3 } ::= { hdsl2ShdslMibObjects 3 }
hdsl2ShdslInventoryEntry OBJECT-TYPE hdsl2ShdslInventoryEntry OBJECT-TYPE
SYNTAX Hdsl2ShdslInventoryEntry SYNTAX Hdsl2ShdslInventoryEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the hdsl2ShdslInventoryTable. Each entry "An entry in the hdsl2ShdslInventoryTable. Each entry
represents inventory information for a single unit in a represents inventory information for a single unit in an
HDSL2/SHDSL line. It is indexed by the ifIndex of the HDSL2/SHDSL line. It is indexed by the ifIndex of the
HDSL2/SHDSL line and the Hdsl2ShdslUnitId of the HDSL2/SHDSL line and the Hdsl2ShdslUnitId of the
associated unit." associated unit."
INDEX { ifIndex, hdsl2ShdslInvIndex } INDEX { ifIndex, hdsl2ShdslInvIndex }
::= { hdsl2ShdslInventoryTable 1 } ::= { hdsl2ShdslInventoryTable 1 }
Hdsl2ShdslInventoryEntry ::= Hdsl2ShdslInventoryEntry ::=
SEQUENCE SEQUENCE
{ {
hdsl2ShdslInvIndex Hdsl2ShdslUnitId, hdsl2ShdslInvIndex Hdsl2ShdslUnitId,
skipping to change at page 25, line 6 skipping to change at page 24, line 35
hdsl2ShdslInvTransmissionModeCapability hdsl2ShdslInvTransmissionModeCapability
Hdsl2ShdslTransmissionModeType Hdsl2ShdslTransmissionModeType
} }
hdsl2ShdslInvIndex OBJECT-TYPE hdsl2ShdslInvIndex OBJECT-TYPE
SYNTAX Hdsl2ShdslUnitId SYNTAX Hdsl2ShdslUnitId
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each entry in this table corresponds to a physical element "Each entry in this table corresponds to a physical element
in a HDSL2/SHDSL Span. It is based on the EOC unit addressing in an HDSL2/SHDSL span. It is based on the EOC unit addressing
scheme with reference to the xtuC." scheme with reference to the xtuC."
::= { hdsl2ShdslInventoryEntry 1 } ::= { hdsl2ShdslInventoryEntry 1 }
hdsl2ShdslInvVendorID OBJECT-TYPE hdsl2ShdslInvVendorID OBJECT-TYPE
SYNTAX OCTET STRING(SIZE(8)) SYNTAX OCTET STRING(SIZE(8))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Vendor ID as reported in an Inventory Response message." "Vendor ID as reported in an Inventory Response message."
REFERENCE REFERENCE
skipping to change at page 26, line 6 skipping to change at page 25, line 35
hdsl2ShdslInvVendorEOCSoftwareVersion OBJECT-TYPE hdsl2ShdslInvVendorEOCSoftwareVersion OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Vendor EOC version as reported in a Discovery Response "Vendor EOC version as reported in a Discovery Response
message." message."
REFERENCE REFERENCE
"G.991.2, Section 9.5.5.7.2, Discovery response - Message ID "G.991.2, Section 9.5.5.7.2, Discovery response - Message ID
130, Octet 12." 129, Octet 12."
::= { hdsl2ShdslInventoryEntry 5 } ::= { hdsl2ShdslInventoryEntry 5 }
hdsl2ShdslInvStandardVersion OBJECT-TYPE hdsl2ShdslInvStandardVersion OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Version of the HDSL2/SHDSL standard implemented, as reported "Version of the HDSL2/SHDSL standard implemented, as reported
in an Inventory Response message." in an Inventory Response message."
REFERENCE REFERENCE
skipping to change at page 27, line 50 skipping to change at page 27, line 31
-- Segment Endpoint Configuration Group -- Segment Endpoint Configuration Group
-- --
hdsl2ShdslEndpointConfTable OBJECT-TYPE hdsl2ShdslEndpointConfTable OBJECT-TYPE
SYNTAX SEQUENCE OF Hdsl2ShdslEndpointConfEntry SYNTAX SEQUENCE OF Hdsl2ShdslEndpointConfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table supports configuration parameters for segment "This table supports configuration parameters for segment
endpoints in a HDSL2/SHDSL line. As this table is indexed endpoints in an HDSL2/SHDSL line. As this table is indexed
by ifIndex, it MUST be maintained in a persistent manner." by ifIndex, it MUST be maintained in a persistent manner."
::= { hdsl2ShdslMibObjects 4 } ::= { hdsl2ShdslMibObjects 4 }
hdsl2ShdslEndpointConfEntry OBJECT-TYPE hdsl2ShdslEndpointConfEntry OBJECT-TYPE
SYNTAX Hdsl2ShdslEndpointConfEntry SYNTAX Hdsl2ShdslEndpointConfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the hdsl2ShdslEndpointConfTable. Each entry "An entry in the hdsl2ShdslEndpointConfTable. Each entry
represents a single segment endpoint in a HDSL2/SHDSL line. represents a single segment endpoint in an HDSL2/SHDSL line.
It is indexed by the ifIndex of the HDSL2/SHDSL line, the It is indexed by the ifIndex of the HDSL2/SHDSL line, the
UnitId of the associated unit, the side of the unit, and the UnitId of the associated unit, the side of the unit, and the
wire pair of the associated modem." wire pair of the associated modem."
INDEX { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide, INDEX { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide,
hdsl2ShdslEndpointWirePair} hdsl2ShdslEndpointWirePair}
::= { hdsl2ShdslEndpointConfTable 1 } ::= { hdsl2ShdslEndpointConfTable 1 }
Hdsl2ShdslEndpointConfEntry ::= Hdsl2ShdslEndpointConfEntry ::=
SEQUENCE SEQUENCE
{ {
hdsl2ShdslEndpointSide Hdsl2ShdslUnitSide, hdsl2ShdslEndpointSide Hdsl2ShdslUnitSide,
hdsl2ShdslEndpointWirePair Hdsl2ShdslWirePair, hdsl2ShdslEndpointWirePair Hdsl2ShdslWirePair,
hdsl2ShdslEndpointAlarmConfProfile SnmpAdminString hdsl2ShdslEndpointAlarmConfProfile SnmpAdminString
} }
hdsl2ShdslEndpointSide OBJECT-TYPE hdsl2ShdslEndpointSide OBJECT-TYPE
SYNTAX Hdsl2ShdslUnitSide SYNTAX Hdsl2ShdslUnitSide
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The side of the unit associated with this segment endpoint - "The side of the unit associated with this segment endpoint --
Network/Customer side - as per the Hdsl2ShdslUnitSide textual Network/Customer side -- as per the Hdsl2ShdslUnitSide textual
convention." convention."
::= { hdsl2ShdslEndpointConfEntry 1 } ::= { hdsl2ShdslEndpointConfEntry 1 }
hdsl2ShdslEndpointWirePair OBJECT-TYPE hdsl2ShdslEndpointWirePair OBJECT-TYPE
SYNTAX Hdsl2ShdslWirePair SYNTAX Hdsl2ShdslWirePair
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The wire pair of the modem associated with this segment "The wire pair of the modem associated with this segment
endpoint as per the Hdsl2ShdslWirePair textual convention." endpoint as per the Hdsl2ShdslWirePair textual convention."
skipping to change at page 29, line 23 skipping to change at page 29, line 4
hdsl2ShdslSpanConfTable. The default value of this object is hdsl2ShdslSpanConfTable. The default value of this object is
a zero-length SnmpAdminString. a zero-length SnmpAdminString.
Any attempt to set this object to a value that is not the value Any attempt to set this object to a value that is not the value
of the index for an active entry in the profile table, of the index for an active entry in the profile table,
hdsl2ShdslEndpointAlarmConfProfileTable, MUST be rejected." hdsl2ShdslEndpointAlarmConfProfileTable, MUST be rejected."
::= { hdsl2ShdslEndpointConfEntry 3 } ::= { hdsl2ShdslEndpointConfEntry 3 }
-- 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 module indexed by ifIndex, entries in this tables in this MIB module indexed by ifIndex, entries in this
table 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
skipping to change at page 31, line 29 skipping to change at page 31, line 9
configInitFailure(7), configInitFailure(7),
protocolInitFailure(8), protocolInitFailure(8),
noNeighborPresent(9), noNeighborPresent(9),
loopbackActive(10) loopbackActive(10)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Contains the current state of the endpoint. This is a "Contains the current state of the endpoint. This is a
bit-map of possible conditions. The various bit positions bit-map of possible conditions. The various bit positions
are: are as follows:
noDefect There are no defects on the line. noDefect There are no defects on the line.
powerBackoff Indicates enhanced Power Backoff. powerBackoff Indicates enhanced Power Backoff.
deviceFault Indicates a vendor-dependent deviceFault Indicates that a vendor-dependent
diagnostic or self-test fault diagnostic or self-test fault
has been detected. has been detected.
dcContinuityFault Indicates vendor-dependent dcContinuityFault Indicates vendor-dependent
conditions that interfere with conditions that interfere with
span powering such as short and span powering such as short and
open circuits. open circuits.
snrMarginAlarm Indicates that the SNR margin snrMarginAlarm Indicates that the SNR margin
has dropped below the alarm threshold. has dropped below the alarm threshold.
skipping to change at page 32, line 18 skipping to change at page 31, line 45
protocolInitFailure Endpoint failure during initialization protocolInitFailure Endpoint failure during initialization
due to incompatible protocol used by due to incompatible protocol used by
the paired endpoint. the paired endpoint.
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 module." 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
skipping to change at page 41, line 19 skipping to change at page 40, line 49
::= { hdsl2Shdsl1DayIntervalEntry 7 } ::= { hdsl2Shdsl1DayIntervalEntry 7 }
-- Maintenance Group -- Maintenance Group
-- --
hdsl2ShdslEndpointMaintTable OBJECT-TYPE hdsl2ShdslEndpointMaintTable OBJECT-TYPE
SYNTAX SEQUENCE OF Hdsl2ShdslEndpointMaintEntry SYNTAX SEQUENCE OF Hdsl2ShdslEndpointMaintEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table supports maintenance operations (e.g. loopbacks) "This table supports maintenance operations (e.g., loopbacks)
to be performed on HDSL2/SHDSL segment endpoints. This table to be performed on HDSL2/SHDSL segment endpoints. This table
contains live data from equipment. As such, it is NOT contains live data from equipment. As such, it is NOT
persistent." persistent."
::= { hdsl2ShdslMibObjects 8 } ::= { hdsl2ShdslMibObjects 8 }
hdsl2ShdslEndpointMaintEntry OBJECT-TYPE hdsl2ShdslEndpointMaintEntry OBJECT-TYPE
SYNTAX Hdsl2ShdslEndpointMaintEntry SYNTAX Hdsl2ShdslEndpointMaintEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the hdsl2ShdslEndpointMaintTable. Each entry "An entry in the hdsl2ShdslEndpointMaintTable. Each entry
corresponds to a single segment endpoint, and is indexed by the corresponds to a single segment endpoint and is indexed by the
ifIndex of the HDSL2/SHDSL line, the UnitId of the associated ifIndex of the HDSL2/SHDSL line, the UnitId of the associated
unit and the side of the unit." unit, and the side of the unit."
INDEX { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide } INDEX { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide }
::= { hdsl2ShdslEndpointMaintTable 1 } ::= { hdsl2ShdslEndpointMaintTable 1 }
Hdsl2ShdslEndpointMaintEntry ::= Hdsl2ShdslEndpointMaintEntry ::=
SEQUENCE SEQUENCE
{ {
hdsl2ShdslMaintLoopbackConfig INTEGER, hdsl2ShdslMaintLoopbackConfig INTEGER,
hdsl2ShdslMaintTipRingReversal INTEGER, hdsl2ShdslMaintTipRingReversal INTEGER,
hdsl2ShdslMaintPowerBackOff INTEGER, hdsl2ShdslMaintPowerBackOff INTEGER,
hdsl2ShdslMaintSoftRestart INTEGER hdsl2ShdslMaintSoftRestart INTEGER
skipping to change at page 43, line 26 skipping to change at page 43, line 8
HDSL2/SHDSL line. Entries in this table MUST be maintained HDSL2/SHDSL line. Entries in this table MUST be maintained
in a persistent manner." in a persistent manner."
::= { hdsl2ShdslMibObjects 9 } ::= { hdsl2ShdslMibObjects 9 }
hdsl2ShdslUnitMaintEntry OBJECT-TYPE hdsl2ShdslUnitMaintEntry OBJECT-TYPE
SYNTAX Hdsl2ShdslUnitMaintEntry SYNTAX Hdsl2ShdslUnitMaintEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the hdsl2ShdslUnitMaintTable. Each entry "An entry in the hdsl2ShdslUnitMaintTable. Each entry
corresponds to a single unit, and is indexed by the corresponds to a single unit and is indexed by the
ifIndex of the HDSL2/SHDSL line and the UnitId of the ifIndex of the HDSL2/SHDSL line and the UnitId of the
associated unit." associated unit."
INDEX { ifIndex, hdsl2ShdslInvIndex } INDEX { ifIndex, hdsl2ShdslInvIndex }
::= { hdsl2ShdslUnitMaintTable 1 } ::= { hdsl2ShdslUnitMaintTable 1 }
Hdsl2ShdslUnitMaintEntry ::= Hdsl2ShdslUnitMaintEntry ::=
SEQUENCE SEQUENCE
{ {
hdsl2ShdslMaintLoopbackTimeout Integer32, hdsl2ShdslMaintLoopbackTimeout Integer32,
hdsl2ShdslMaintUnitPowerSource INTEGER hdsl2ShdslMaintUnitPowerSource INTEGER
skipping to change at page 45, line 43 skipping to change at page 45, line 25
{ {
twoWire(1), twoWire(1),
fourWire(2), fourWire(2),
sixWire(3), sixWire(3),
eightWire(4) eightWire(4)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object configures the two-wire or optional four-wire, "This object configures the two-wire or optional four-wire,
six-wire, or eight-wire operation for SHDSL Lines." six-wire, or eight-wire operation for SHDSL lines."
DEFVAL { twoWire } DEFVAL { twoWire }
::= { hdsl2ShdslSpanConfProfileEntry 2 } ::= { hdsl2ShdslSpanConfProfileEntry 2 }
hdsl2ShdslSpanConfMinLineRate OBJECT-TYPE hdsl2ShdslSpanConfMinLineRate OBJECT-TYPE
SYNTAX Unsigned32(0..4294967295) SYNTAX Unsigned32(0..4294967295)
UNITS "bps" UNITS "bps"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object configures the minimum transmission rate for "This object configures the minimum transmission rate for
skipping to change at page 47, line 21 skipping to change at page 46, line 51
hdsl2ShdslSpanConfRemoteEnabled OBJECT-TYPE hdsl2ShdslSpanConfRemoteEnabled OBJECT-TYPE
SYNTAX INTEGER SYNTAX INTEGER
{ {
enabled(1), enabled(1),
disabled(2) disabled(2)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object enables/disables support for remote management "This object enables/disables support for remote management
of the units in a SHDSL line from the STU-R via the EOC." of the units in an SHDSL line from the STU-R via the EOC."
DEFVAL { enabled } DEFVAL { enabled }
::= { hdsl2ShdslSpanConfProfileEntry 7 } ::= { hdsl2ShdslSpanConfProfileEntry 7 }
hdsl2ShdslSpanConfPowerFeeding OBJECT-TYPE hdsl2ShdslSpanConfPowerFeeding OBJECT-TYPE
SYNTAX INTEGER SYNTAX INTEGER
{ {
noPower(1), noPower(1),
powerFeed(2), powerFeed(2),
wettingCurrent(3) wettingCurrent(3)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object enables/disables support for optional power "This object enables/disables support for optional power
feeding in a SHDSL line." feeding in an SHDSL line."
DEFVAL { noPower } DEFVAL { noPower }
::= { hdsl2ShdslSpanConfProfileEntry 8 } ::= { hdsl2ShdslSpanConfProfileEntry 8 }
hdsl2ShdslSpanConfCurrCondTargetMarginDown OBJECT-TYPE hdsl2ShdslSpanConfCurrCondTargetMarginDown OBJECT-TYPE
SYNTAX Integer32(-10..21) SYNTAX Integer32(-10..21)
UNITS "dB" UNITS "dB"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the downstream current condition target "This object specifies the downstream current condition target
SNR margin for a SHDSL line. The SNR margin is the difference SNR margin for an SHDSL line. The SNR margin is the difference
between the desired SNR and the actual SNR. Target SNR margin between the desired SNR and the actual SNR. Target SNR margin
is the desired SNR margin for a unit." is the desired SNR margin for a unit."
DEFVAL { 0 } DEFVAL { 0 }
::= { hdsl2ShdslSpanConfProfileEntry 9 } ::= { hdsl2ShdslSpanConfProfileEntry 9 }
hdsl2ShdslSpanConfWorstCaseTargetMarginDown OBJECT-TYPE hdsl2ShdslSpanConfWorstCaseTargetMarginDown OBJECT-TYPE
SYNTAX Integer32(-10..21) SYNTAX Integer32(-10..21)
UNITS "dB" UNITS "dB"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the downstream worst case target SNR "This object specifies the downstream worst-case target SNR
margin for a SHDSL line. The SNR margin is the difference margin for an SHDSL line. The SNR margin is the difference
between the desired SNR and the actual SNR. Target SNR between the desired SNR and the actual SNR. Target SNR
margin is the desired SNR margin for a unit." margin is the desired SNR margin for a unit."
DEFVAL { 0 } DEFVAL { 0 }
::= { hdsl2ShdslSpanConfProfileEntry 10 } ::= { hdsl2ShdslSpanConfProfileEntry 10 }
hdsl2ShdslSpanConfCurrCondTargetMarginUp OBJECT-TYPE hdsl2ShdslSpanConfCurrCondTargetMarginUp OBJECT-TYPE
SYNTAX Integer32(-10..21) SYNTAX Integer32(-10..21)
UNITS "dB" UNITS "dB"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the upstream current condition target "This object specifies the upstream current-condition target
SNR margin for a SHDSL line. The SNR margin is the difference SNR margin for an SHDSL line. The SNR margin is the difference
between the desired SNR and the actual SNR. Target SNR margin between the desired SNR and the actual SNR. Target SNR margin
is the desired SNR margin for a unit." is the desired SNR margin for a unit."
DEFVAL { 0 } DEFVAL { 0 }
::= { hdsl2ShdslSpanConfProfileEntry 11 } ::= { hdsl2ShdslSpanConfProfileEntry 11 }
hdsl2ShdslSpanConfWorstCaseTargetMarginUp OBJECT-TYPE hdsl2ShdslSpanConfWorstCaseTargetMarginUp OBJECT-TYPE
SYNTAX Integer32(-10..21) SYNTAX Integer32(-10..21)
UNITS "dB" UNITS "dB"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the upstream worst case target SNR "This object specifies the upstream worst-case target SNR
margin for a SHDSL line. The SNR margin is the difference margin for an SHDSL line. The SNR margin is the difference
between the desired SNR and the actual SNR. Target SNR margin between the desired SNR and the actual SNR. Target SNR margin
is the desired SNR margin for a unit." is the desired SNR margin for a unit."
DEFVAL { 0 } DEFVAL { 0 }
::= { hdsl2ShdslSpanConfProfileEntry 12 } ::= { hdsl2ShdslSpanConfProfileEntry 12 }
hdsl2ShdslSpanConfUsedTargetMargins OBJECT-TYPE hdsl2ShdslSpanConfUsedTargetMargins OBJECT-TYPE
SYNTAX BITS SYNTAX BITS
{ {
currCondDown(0), currCondDown(0),
worstCaseDown(1), worstCaseDown(1),
currCondUp(2), currCondUp(2),
worstCaseUp(3) worstCaseUp(3)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates whether a target SNR margin is enabled or "Indicates whether a target SNR margin is enabled or
disabled. This is a bit-map of possible settings. The disabled. This is a bit-map of possible settings. The
various bit positions are: various bit positions are as follows:
currCondDown - current condition downstream target SNR currCondDown - current-condition downstream target SNR
margin enabled margin enabled
worstCaseDown - worst case downstream target SNR margin worstCaseDown - worst-case downstream target SNR margin
enabled enabled
currCondUp - current condition upstream target SNR currCondUp - current-condition upstream target SNR
margin enabled margin enabled
worstCaseUp - worst case upstream target SNR margin worstCaseUp - worst-case upstream target SNR margin
enabled." enabled."
DEFVAL { { currCondDown } } DEFVAL { { currCondDown } }
::= { hdsl2ShdslSpanConfProfileEntry 13 } ::= { hdsl2ShdslSpanConfProfileEntry 13 }
hdsl2ShdslSpanConfReferenceClock OBJECT-TYPE hdsl2ShdslSpanConfReferenceClock OBJECT-TYPE
SYNTAX Hdsl2ShdslClockReferenceType SYNTAX Hdsl2ShdslClockReferenceType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object configures the clock reference for the STU-C "This object configures the clock reference for the STU-C
in a SHDSL Line." in an SHDSL Line."
DEFVAL { localClk } DEFVAL { localClk }
::= { hdsl2ShdslSpanConfProfileEntry 14 } ::= { hdsl2ShdslSpanConfProfileEntry 14 }
hdsl2ShdslSpanConfLineProbeEnable OBJECT-TYPE hdsl2ShdslSpanConfLineProbeEnable OBJECT-TYPE
SYNTAX INTEGER SYNTAX INTEGER
{ {
disable(1), disable(1),
enable(2) enable(2)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object enables/disables support for Line Probe of "This object enables/disables support for Line Probe of
the units in a SHDSL line. When Line Probe is enabled, the the units in an SHDSL line. When Line Probe is enabled, the
system performs Line Probing to find the best possible system performs Line Probing to find the best possible
rate. If Line probe is disabled, the rate adaptation phase rate. If Line Probe is disabled, the rate adaptation phase
is skipped to shorten set up time." is skipped to shorten set up time."
DEFVAL { disable } DEFVAL { disable }
::= { hdsl2ShdslSpanConfProfileEntry 15 } ::= { hdsl2ShdslSpanConfProfileEntry 15 }
hdsl2ShdslSpanConfProfileRowStatus OBJECT-TYPE hdsl2ShdslSpanConfProfileRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object controls creation/deletion of the associated "This object controls creation/deletion of the associated
skipping to change at page 51, line 21 skipping to change at page 51, line 4
hdsl2ShdslEndpointAlarmConfProfileRowStatus RowStatus hdsl2ShdslEndpointAlarmConfProfileRowStatus RowStatus
} }
hdsl2ShdslEndpointAlarmConfProfileName OBJECT-TYPE hdsl2ShdslEndpointAlarmConfProfileName OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE(1..32)) SYNTAX SnmpAdminString (SIZE(1..32))
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is the unique index associated with this profile." "This object is the unique index associated with this profile."
::= { hdsl2ShdslEndpointAlarmConfProfileEntry 1 } ::= { hdsl2ShdslEndpointAlarmConfProfileEntry 1 }
hdsl2ShdslEndpointThreshLoopAttenuation OBJECT-TYPE hdsl2ShdslEndpointThreshLoopAttenuation OBJECT-TYPE
SYNTAX Integer32(-127..128) SYNTAX Integer32(-127..128)
UNITS "dB" UNITS "dB"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object configures the loop attenuation alarm threshold. "This object configures the loop attenuation alarm threshold.
When the current value of hdsl2ShdslEndpointCurrAtn reaches When the current value of hdsl2ShdslEndpointCurrAtn reaches
or exceeds this threshold, a hdsl2ShdslLoopAttenCrossing or exceeds this threshold, an hdsl2ShdslLoopAttenCrossing
MAY be generated." MAY be generated."
DEFVAL { 0 } DEFVAL { 0 }
::= { hdsl2ShdslEndpointAlarmConfProfileEntry 2 } ::= { hdsl2ShdslEndpointAlarmConfProfileEntry 2 }
hdsl2ShdslEndpointThreshSNRMargin OBJECT-TYPE hdsl2ShdslEndpointThreshSNRMargin OBJECT-TYPE
SYNTAX Integer32(-127..128) SYNTAX Integer32(-127..128)
UNITS "dB" UNITS "dB"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 52, line 7 skipping to change at page 51, line 37
DEFVAL { 0 } DEFVAL { 0 }
::= { hdsl2ShdslEndpointAlarmConfProfileEntry 3 } ::= { hdsl2ShdslEndpointAlarmConfProfileEntry 3 }
hdsl2ShdslEndpointThreshES OBJECT-TYPE hdsl2ShdslEndpointThreshES OBJECT-TYPE
SYNTAX Hdsl2ShdslPerfIntervalThreshold SYNTAX Hdsl2ShdslPerfIntervalThreshold
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object configures the threshold for the number of "This object configures the threshold for the number of
errored seconds (ES) within any given 15-minute performance Errored Seconds (ES) within any given 15-minute performance
data collection interval. If the value of errored seconds data collection interval. If the value of Errored Seconds
in a particular 15-minute collection interval reaches/ in a particular 15-minute collection interval reaches/
exceeds this value, a hdsl2ShdslPerfESThresh MAY be exceeds this value, an hdsl2ShdslPerfESThresh MAY be
generated. At most one notification will be sent per generated. At most, one notification will be sent per
interval per endpoint." interval per endpoint."
DEFVAL { 0 } DEFVAL { 0 }
::= { hdsl2ShdslEndpointAlarmConfProfileEntry 4 } ::= { hdsl2ShdslEndpointAlarmConfProfileEntry 4 }
hdsl2ShdslEndpointThreshSES OBJECT-TYPE hdsl2ShdslEndpointThreshSES OBJECT-TYPE
SYNTAX Hdsl2ShdslPerfIntervalThreshold SYNTAX Hdsl2ShdslPerfIntervalThreshold
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object configures the threshold for the number of "This object configures the threshold for the number of
severely errored seconds (SES) within any given 15-minute Severely Errored Seconds (SES) within any given 15-minute
performance data collection interval. If the value of performance data collection interval. If the value of
severely errored seconds in a particular 15-minute collection Severely Errored Seconds in a particular 15-minute collection
interval reaches/exceeds this value, a hdsl2ShdslPerfSESThresh interval reaches/exceeds this value, an hdsl2ShdslPerfSESThresh
MAY be generated. At most one notification will be sent per MAY be generated. At most, one notification will be sent per
interval per endpoint." interval per endpoint."
DEFVAL { 0 } DEFVAL { 0 }
::= { hdsl2ShdslEndpointAlarmConfProfileEntry 5 } ::= { hdsl2ShdslEndpointAlarmConfProfileEntry 5 }
hdsl2ShdslEndpointThreshCRCanomalies OBJECT-TYPE hdsl2ShdslEndpointThreshCRCanomalies OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "detected CRC Anomalies" UNITS "detected CRC Anomalies"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object configures the threshold for the number of "This object configures the threshold for the number of
CRC anomalies within any given 15-minute performance data CRC anomalies within any given 15-minute performance data
collection interval. If the value of CRC anomalies in a collection interval. If the value of CRC anomalies in a
particular 15-minute collection interval reaches/exceeds particular 15-minute collection interval reaches/exceeds
this value, a hdsl2ShdslPerfCRCanomaliesThresh MAY be this value, an hdsl2ShdslPerfCRCanomaliesThresh MAY be
generated. At most one notification will be sent per generated. At most, one notification will be sent per
interval per endpoint." interval per endpoint."
DEFVAL { 0 } DEFVAL { 0 }
::= { hdsl2ShdslEndpointAlarmConfProfileEntry 6 } ::= { hdsl2ShdslEndpointAlarmConfProfileEntry 6 }
hdsl2ShdslEndpointThreshLOSWS OBJECT-TYPE hdsl2ShdslEndpointThreshLOSWS OBJECT-TYPE
SYNTAX Hdsl2ShdslPerfIntervalThreshold SYNTAX Hdsl2ShdslPerfIntervalThreshold
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object configures the threshold for the number of "This object configures the threshold for the number of
Loss of Sync Word (LOSW) Seconds within any given 15-minute Loss of Sync Word (LOSW) Seconds within any given 15-minute
performance data collection interval. If the value of LOSW performance data collection interval. If the value of LOSW
in a particular 15-minute collection interval reaches/exceeds in a particular 15-minute collection interval reaches/exceeds
this value, a hdsl2ShdslPerfLOSWSThresh MAY be generated. this value, an hdsl2ShdslPerfLOSWSThresh MAY be generated.
At most one notification will be sent per interval per At most, one notification will be sent per interval per
endpoint." endpoint."
DEFVAL { 0 } DEFVAL { 0 }
::= { hdsl2ShdslEndpointAlarmConfProfileEntry 7 } ::= { hdsl2ShdslEndpointAlarmConfProfileEntry 7 }
hdsl2ShdslEndpointThreshUAS OBJECT-TYPE hdsl2ShdslEndpointThreshUAS OBJECT-TYPE
SYNTAX Hdsl2ShdslPerfIntervalThreshold SYNTAX Hdsl2ShdslPerfIntervalThreshold
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object configures the threshold for the number of "This object configures the threshold for the number of
unavailable seconds (UAS) within any given 15-minute Unavailable Seconds (UAS) within any given 15-minute
performance data collection interval. If the value of UAS performance data collection interval. If the value of UAS
in a particular 15-minute collection interval reaches/exceeds in a particular 15-minute collection interval reaches/exceeds
this value, a hdsl2ShdslPerfUASThresh MAY be generated. this value, an hdsl2ShdslPerfUASThresh MAY be generated.
At most one notification will be sent per interval per At most, one notification will be sent per interval per
endpoint." endpoint."
DEFVAL { 0 } DEFVAL { 0 }
::= { hdsl2ShdslEndpointAlarmConfProfileEntry 8 } ::= { hdsl2ShdslEndpointAlarmConfProfileEntry 8 }
hdsl2ShdslEndpointAlarmConfProfileRowStatus OBJECT-TYPE hdsl2ShdslEndpointAlarmConfProfileRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object controls creation/deletion of the associated "This object controls creation/deletion of the associated
skipping to change at page 55, line 5 skipping to change at page 54, line 35
hdsl2ShdslPerfSESThresh NOTIFICATION-TYPE hdsl2ShdslPerfSESThresh NOTIFICATION-TYPE
OBJECTS OBJECTS
{ {
hdsl2ShdslEndpointCurr15MinSES, hdsl2ShdslEndpointCurr15MinSES,
hdsl2ShdslEndpointThreshSES hdsl2ShdslEndpointThreshSES
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification indicates that the severely errored seconds "This notification indicates that the severely errored seconds
threshold (as per the hdsl2ShdslEndpointThreshSES value) has threshold (as per the hdsl2ShdslEndpointThreshSES value) has
been reached/exceeded for the HDSL2/SHDSL Segment Endpoint." been reached/exceeded for the HDSL2/SHDSL segment endpoint."
::= { hdsl2ShdslNotifications 4 } ::= { hdsl2ShdslNotifications 4 }
hdsl2ShdslPerfCRCanomaliesThresh NOTIFICATION-TYPE hdsl2ShdslPerfCRCanomaliesThresh NOTIFICATION-TYPE
OBJECTS OBJECTS
{ {
hdsl2ShdslEndpointCurr15MinCRCanomalies, hdsl2ShdslEndpointCurr15MinCRCanomalies,
hdsl2ShdslEndpointThreshCRCanomalies hdsl2ShdslEndpointThreshCRCanomalies
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification indicates that the CRC anomalies threshold "This notification indicates that the CRC anomalies threshold
(as per the hdsl2ShdslEndpointThreshCRCanomalies value) has (as per the hdsl2ShdslEndpointThreshCRCanomalies value) has
been reached/exceeded for the HDSL2/SHDSL Segment Endpoint." been reached/exceeded for the HDSL2/SHDSL segment endpoint."
::= { hdsl2ShdslNotifications 5 } ::= { hdsl2ShdslNotifications 5 }
hdsl2ShdslPerfLOSWSThresh NOTIFICATION-TYPE hdsl2ShdslPerfLOSWSThresh NOTIFICATION-TYPE
OBJECTS OBJECTS
{ {
hdsl2ShdslEndpointCurr15MinLOSWS, hdsl2ShdslEndpointCurr15MinLOSWS,
hdsl2ShdslEndpointThreshLOSWS hdsl2ShdslEndpointThreshLOSWS
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification indicates that the LOSW seconds threshold "This notification indicates that the LOSW Seconds threshold
(as per the hdsl2ShdslEndpointThreshLOSWS value) has been (as per the hdsl2ShdslEndpointThreshLOSWS value) has been
reached/exceeded for the HDSL2/SHDSL segment endpoint." reached/exceeded for the HDSL2/SHDSL segment endpoint."
::= { hdsl2ShdslNotifications 6 } ::= { hdsl2ShdslNotifications 6 }
hdsl2ShdslPerfUASThresh NOTIFICATION-TYPE hdsl2ShdslPerfUASThresh NOTIFICATION-TYPE
OBJECTS OBJECTS
{ {
hdsl2ShdslEndpointCurr15MinUAS, hdsl2ShdslEndpointCurr15MinUAS,
hdsl2ShdslEndpointThreshUAS hdsl2ShdslEndpointThreshUAS
} }
skipping to change at page 56, line 8 skipping to change at page 55, line 38
hdsl2ShdslSpanInvalidNumRepeaters NOTIFICATION-TYPE hdsl2ShdslSpanInvalidNumRepeaters NOTIFICATION-TYPE
OBJECTS OBJECTS
{ {
hdsl2ShdslSpanConfNumRepeaters hdsl2ShdslSpanConfNumRepeaters
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification indicates that a mismatch has been detected "This notification indicates that a mismatch has been detected
between the number of repeater/regenerator units configured between the number of repeater/regenerator units configured
for a HDSL2/SHDSL line via the hdsl2ShdslSpanConfNumRepeaters for an HDSL2/SHDSL line via the hdsl2ShdslSpanConfNumRepeaters
object and the actual number of repeater/regenerator units object and the actual number of repeater/regenerator units
discovered via the EOC." discovered via the EOC."
::= { hdsl2ShdslNotifications 8 } ::= { hdsl2ShdslNotifications 8 }
hdsl2ShdslLoopbackFailure NOTIFICATION-TYPE hdsl2ShdslLoopbackFailure NOTIFICATION-TYPE
OBJECTS OBJECTS
{ {
hdsl2ShdslMaintLoopbackConfig hdsl2ShdslMaintLoopbackConfig
} }
STATUS current STATUS current
skipping to change at page 58, line 21 skipping to change at page 58, line 4
-- conformance information -- conformance information
-- --
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 deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The compliance statement for SNMP entities which implement "The compliance statement for SNMP entities that implement
HDSL2 and SHDSL. The version of SHDSL supported in this HDSL2 and SHDSL. The version of SHDSL supported in this
compliance statement is g.shdsl. compliance statement is g.shdsl.
**** This compliance statement is deprecated. ****" **** This compliance statement is deprecated. ****"
MODULE MODULE
MANDATORY-GROUPS MANDATORY-GROUPS
{ {
hdsl2ShdslSpanConfGroup, hdsl2ShdslSpanConfGroup,
hdsl2ShdslSpanStatusGroup, hdsl2ShdslSpanStatusGroup,
hdsl2ShdslInventoryGroup, hdsl2ShdslInventoryGroup,
skipping to change at page 60, line 4 skipping to change at page 59, line 33
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 hdsl2GshdslbisLineMibCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for SNMP entities which implement "The compliance statement for SNMP entities that implement
HDSL2 and SHDSL. The version of SHDSL supported in this HDSL2 and SHDSL. The version of SHDSL supported in this
compliance statement is g.shdsl.bis." compliance statement is g.shdsl.bis."
MODULE MODULE
MANDATORY-GROUPS MANDATORY-GROUPS
{ {
hdsl2ShdslSpanConfGroup, hdsl2ShdslSpanConfGroup,
hdsl2ShdslSpanStatusGroup, hdsl2ShdslSpanStatusGroup,
hdsl2ShdslInventoryGroup, hdsl2ShdslInventoryGroup,
hdsl2ShdslEndpointConfGroup, hdsl2ShdslEndpointConfGroup,
hdsl2ShdslEndpointCurrGroup, hdsl2ShdslEndpointCurrGroup,
skipping to change at page 61, line 16 skipping to change at page 60, line 46
hdsl2ShdslSpanConfGroup OBJECT-GROUP hdsl2ShdslSpanConfGroup OBJECT-GROUP
OBJECTS OBJECTS
{ {
hdsl2ShdslSpanConfNumRepeaters, hdsl2ShdslSpanConfNumRepeaters,
hdsl2ShdslSpanConfProfile, hdsl2ShdslSpanConfProfile,
hdsl2ShdslSpanConfAlarmProfile hdsl2ShdslSpanConfAlarmProfile
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group supports objects for configuring span related "This group supports objects for configuring span-related
parameters for HDSL2/SHDSL lines." parameters for HDSL2/SHDSL lines."
::= { hdsl2ShdslGroups 1 } ::= { hdsl2ShdslGroups 1 }
hdsl2ShdslSpanStatusGroup OBJECT-GROUP hdsl2ShdslSpanStatusGroup OBJECT-GROUP
OBJECTS OBJECTS
{ {
hdsl2ShdslStatusNumAvailRepeaters hdsl2ShdslStatusNumAvailRepeaters
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group supports objects for retrieving span related "This group supports objects for retrieving span-related
status for HDSL2/SHDSL lines." status for HDSL2/SHDSL lines."
::= { hdsl2ShdslGroups 2 } ::= { hdsl2ShdslGroups 2 }
hdsl2ShdslInventoryShdslGroup OBJECT-GROUP hdsl2ShdslInventoryShdslGroup OBJECT-GROUP
OBJECTS OBJECTS
{ {
hdsl2ShdslInvTransmissionModeCapability hdsl2ShdslInvTransmissionModeCapability
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 62, line 4 skipping to change at page 61, line 34
hdsl2ShdslSpanShdslStatusGroup OBJECT-GROUP hdsl2ShdslSpanShdslStatusGroup OBJECT-GROUP
OBJECTS OBJECTS
{ {
hdsl2ShdslStatusMaxAttainableLineRate, hdsl2ShdslStatusMaxAttainableLineRate,
hdsl2ShdslStatusActualLineRate, hdsl2ShdslStatusActualLineRate,
hdsl2ShdslStatusTransmissionModeCurrent hdsl2ShdslStatusTransmissionModeCurrent
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group supports objects for retrieving SHDSL-specific "This group supports objects for retrieving SHDSL-specific
span related status." span-related status."
::= { hdsl2ShdslGroups 4 } ::= { hdsl2ShdslGroups 4 }
hdsl2ShdslInventoryGroup OBJECT-GROUP hdsl2ShdslInventoryGroup OBJECT-GROUP
OBJECTS OBJECTS
{ {
hdsl2ShdslInvVendorID, hdsl2ShdslInvVendorID,
hdsl2ShdslInvVendorModelNumber, hdsl2ShdslInvVendorModelNumber,
hdsl2ShdslInvVendorSerialNumber, hdsl2ShdslInvVendorSerialNumber,
hdsl2ShdslInvVendorEOCSoftwareVersion, hdsl2ShdslInvVendorEOCSoftwareVersion,
hdsl2ShdslInvStandardVersion, hdsl2ShdslInvStandardVersion,
skipping to change at page 63, line 16 skipping to change at page 62, line 46
hdsl2ShdslEndpointCurr15MinUAS, hdsl2ShdslEndpointCurr15MinUAS,
hdsl2ShdslEndpointCurr1DayTimeElapsed, hdsl2ShdslEndpointCurr1DayTimeElapsed,
hdsl2ShdslEndpointCurr1DayES, hdsl2ShdslEndpointCurr1DayES,
hdsl2ShdslEndpointCurr1DaySES, hdsl2ShdslEndpointCurr1DaySES,
hdsl2ShdslEndpointCurr1DayCRCanomalies, hdsl2ShdslEndpointCurr1DayCRCanomalies,
hdsl2ShdslEndpointCurr1DayLOSWS, hdsl2ShdslEndpointCurr1DayLOSWS,
hdsl2ShdslEndpointCurr1DayUAS hdsl2ShdslEndpointCurr1DayUAS
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group supports objects which provide current status and "This group supports objects that provide current status and
performance measurements relating to segment endpoints in performance measurements relating to segment endpoints in
HDSL2/SHDSL lines." HDSL2/SHDSL lines."
::= { hdsl2ShdslGroups 7 } ::= { hdsl2ShdslGroups 7 }
hdsl2Shdsl15MinIntervalGroup OBJECT-GROUP hdsl2Shdsl15MinIntervalGroup OBJECT-GROUP
OBJECTS OBJECTS
{ {
hdsl2Shdsl15MinIntervalES, hdsl2Shdsl15MinIntervalES,
hdsl2Shdsl15MinIntervalSES, hdsl2Shdsl15MinIntervalSES,
hdsl2Shdsl15MinIntervalCRCanomalies, hdsl2Shdsl15MinIntervalCRCanomalies,
hdsl2Shdsl15MinIntervalLOSWS, hdsl2Shdsl15MinIntervalLOSWS,
hdsl2Shdsl15MinIntervalUAS hdsl2Shdsl15MinIntervalUAS
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group supports objects which maintain historic "This group supports objects that maintain historic
performance measurements relating to segment endpoints in performance measurements relating to segment endpoints in
HDSL2/SHDSL lines in 15-minute intervals." HDSL2/SHDSL lines in 15-minute intervals."
::= { hdsl2ShdslGroups 8 } ::= { hdsl2ShdslGroups 8 }
hdsl2Shdsl1DayIntervalGroup OBJECT-GROUP hdsl2Shdsl1DayIntervalGroup OBJECT-GROUP
OBJECTS OBJECTS
{ {
hdsl2Shdsl1DayIntervalMoniSecs, hdsl2Shdsl1DayIntervalMoniSecs,
hdsl2Shdsl1DayIntervalES, hdsl2Shdsl1DayIntervalES,
hdsl2Shdsl1DayIntervalSES, hdsl2Shdsl1DayIntervalSES,
hdsl2Shdsl1DayIntervalCRCanomalies, hdsl2Shdsl1DayIntervalCRCanomalies,
hdsl2Shdsl1DayIntervalLOSWS, hdsl2Shdsl1DayIntervalLOSWS,
hdsl2Shdsl1DayIntervalUAS hdsl2Shdsl1DayIntervalUAS
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group supports objects which maintain historic "This group supports objects that maintain historic
performance measurements relating to segment endpoints in performance measurements relating to segment endpoints in
HDSL2/SHDSL lines in 1-day intervals." HDSL2/SHDSL lines in 1-day intervals."
::= { hdsl2ShdslGroups 9 } ::= { hdsl2ShdslGroups 9 }
hdsl2ShdslMaintenanceGroup OBJECT-GROUP hdsl2ShdslMaintenanceGroup OBJECT-GROUP
OBJECTS OBJECTS
{ {
hdsl2ShdslMaintLoopbackConfig, hdsl2ShdslMaintLoopbackConfig,
hdsl2ShdslMaintTipRingReversal, hdsl2ShdslMaintTipRingReversal,
hdsl2ShdslMaintPowerBackOff, hdsl2ShdslMaintPowerBackOff,
skipping to change at page 65, line 42 skipping to change at page 65, line 24
hdsl2ShdslSpanConfCurrCondTargetMarginUp, hdsl2ShdslSpanConfCurrCondTargetMarginUp,
hdsl2ShdslSpanConfWorstCaseTargetMarginUp, hdsl2ShdslSpanConfWorstCaseTargetMarginUp,
hdsl2ShdslSpanConfUsedTargetMargins, hdsl2ShdslSpanConfUsedTargetMargins,
hdsl2ShdslSpanConfReferenceClock, hdsl2ShdslSpanConfReferenceClock,
hdsl2ShdslSpanConfLineProbeEnable, hdsl2ShdslSpanConfLineProbeEnable,
hdsl2ShdslSpanConfProfileRowStatus hdsl2ShdslSpanConfProfileRowStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group supports objects that constitute configuration "This group supports objects that constitute configuration
profiles for configuring span related parameters in SHDSL profiles for configuring span-related parameters in SHDSL
lines." lines."
::= { hdsl2ShdslGroups 13 } ::= { hdsl2ShdslGroups 13 }
hdsl2ShdslWirePairGroup OBJECT-GROUP hdsl2ShdslWirePairGroup OBJECT-GROUP
OBJECTS OBJECTS
{ {
hdsl2ShdslEndpointCurrTipRingReversal, hdsl2ShdslEndpointCurrTipRingReversal,
hdsl2ShdslEndpointCurrActivationState hdsl2ShdslEndpointCurrActivationState
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group supports objects which provide the status "This group supports objects that provide the status
of SHDSL-specific wire pairs." of SHDSL-specific wire pairs."
::= { hdsl2ShdslGroups 14 } ::= { hdsl2ShdslGroups 14 }
hdsl2ShdslPayloadRateGroup OBJECT-GROUP hdsl2ShdslPayloadRateGroup OBJECT-GROUP
OBJECTS OBJECTS
{ {
hdsl2ShdslStatusMaxAttainablePayloadRate, hdsl2ShdslStatusMaxAttainablePayloadRate,
hdsl2ShdslStatusActualPayloadRate hdsl2ShdslStatusActualPayloadRate
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group supports object for retrieving payload rates "This group supports objects for retrieving payload rates
which excludes any framing overhead." that exclude any framing overhead."
::= { hdsl2ShdslGroups 15 } ::= { hdsl2ShdslGroups 15 }
END END
4. Implementation Analysis 4. Implementation Analysis
A management application which supports RFC 3276 could mistakenly A management application that supports RFC 3276 could mistakenly flag
flag a unit which responds with a rate or wire pair which exceeds the a unit that responds with a rate or wire pair that exceeds the ranges
ranges and/or enumerations specified in RFC 3276. For example, a 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
might return might return
hdsl2ShdslEndpointCurrAtn.1.1.1.3 = 0 hdsl2ShdslEndpointCurrAtn.1.1.1.3 = 0
skipping to change at page 67, line 8 skipping to change at page 66, line 36
INDEX { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslendpointSide, INDEX { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslendpointSide,
hdsl2ShdslEndpointWirePair } hdsl2ShdslEndpointWirePair }
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.
5. 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
skipping to change at page 67, line 31 skipping to change at page 67, line 15
o hdsl2ShdslSpanConfTable o hdsl2ShdslSpanConfTable
The table consists of the following objects that support SET The table consists of the following objects that support SET
operations: operations:
* hdsl2ShdslSpanConfNumRepeaters * hdsl2ShdslSpanConfNumRepeaters
* hdsl2ShdslSpanConfProfile * hdsl2ShdslSpanConfProfile
* hdsl2ShdslSpanConfAlarmProfile * hdsl2ShdslSpanConfAlarmProfile
Unauthorized changes to hdsl2ShdslSpanConfNumRepeaters could Unauthorized changes to hdsl2ShdslSpanConfNumRepeaters could
result in a hdsl2ShdslSpanInvalidNumRepeaters notification. Note result in an hdsl2ShdslSpanInvalidNumRepeaters notification. Note
the discussion on hdsl2ShdslSpanInvalidNumRepeaters in the the discussion on hdsl2ShdslSpanInvalidNumRepeaters in the
Notifications Section above. Notifications section above.
Unauthorized changes to hdsl2ShdslSpanConfProfile could have an Unauthorized changes to hdsl2ShdslSpanConfProfile could have an
adverse operational effect on a span. Reference the adverse operational effect on a span. Reference the
hdsl2ShdslSpanConfProfileTable discussion below. hdsl2ShdslSpanConfProfileTable discussion below.
Unauthorized changes to hdsl2ShdslSpanConfAlarmProfile could have Unauthorized changes to hdsl2ShdslSpanConfAlarmProfile could have
a contrary effect on notifications. Reference the a contrary effect on notifications. Reference the
hdsl2ShdslEndpointAlarmConfProfileTable discussion below. hdsl2ShdslEndpointAlarmConfProfileTable discussion below.
o hdsl2ShdslEndpointConfTable o hdsl2ShdslEndpointConfTable
skipping to change at page 69, line 19 skipping to change at page 68, line 50
Unauthorized changes to the hdsl2ShdslSpanConfWireInterface could Unauthorized changes to the hdsl2ShdslSpanConfWireInterface could
result in the failure of a span to achieve activation to a state result in the failure of a span to achieve activation to a state
that would permit data flow. For example, setting this object to that would permit data flow. For example, setting this object to
six-wire or eight-wire operation when one of the units in the span six-wire or eight-wire operation when one of the units in the span
only supports two-wire or four-wire operation would likely prevent only supports two-wire or four-wire operation would likely prevent
an expected end-to-end data transfer capability. an expected end-to-end data transfer capability.
Unauthorized changes to hdsl2ShdslSpanConfMinLineRate or Unauthorized changes to hdsl2ShdslSpanConfMinLineRate or
hdsl2ShdslSpanConfMaxLineRate could have an adverse effect on hdsl2ShdslSpanConfMaxLineRate could have an adverse effect on
performance. The range of allowable line rates could be altered performance. The range of allowable line rates could be altered
such that the span may not be able to train to an line rate that such that the span may not be able to train to a line rate that
would permit any end-user data to traverse the span or the span would permit any end-user data to traverse the span or the span
could train to a line rate that is either greater than or less could train to a line rate that is either greater than or less
than the line rate that the provider has pledged. than the line rate that the provider has pledged.
Unauthorized changes to hdsl2ShdslSpanConfPSD or Unauthorized changes to hdsl2ShdslSpanConfPSD or
hdsl2ShdslSpanConfTransmissionMode could have a detrimental effect hdsl2ShdslSpanConfTransmissionMode could have a detrimental effect
loop reach, performance, or spectral compatibility. on loop reach, performance, or spectral compatibility.
Unauthorized changes to hdsl2ShdslSpanConfRemoteEnable could alter Unauthorized changes to hdsl2ShdslSpanConfRemoteEnable could alter
the remote management ability of units. the remote management ability of units.
Unauthorized changes to hdsl2ShdslSpanConfPowerFeeding could Unauthorized changes to hdsl2ShdslSpanConfPowerFeeding could
shutdown units that are expected to be feed power remotely. shutdown units that are expected to be fed power remotely.
Changing the configuration such that wetting current is not Changing the configuration such that wetting current is not
supplied may result in corrosion of electrical contacts. supplied may result in corrosion of electrical contacts.
Unauthorized changes to Unauthorized changes to
hdsl2ShdslSpanConfCurrCondTargetMarginDown, hdsl2ShdslSpanConfCurrCondTargetMarginDown,
hdsl2ShdslSpanConfWorstCaseTargetMarginDown, hdsl2ShdslSpanConfWorstCaseTargetMarginDown,
hdsl2ShdslSpanConfCurrCondTargetMarginUp, hdsl2ShdslSpanConfCurrCondTargetMarginUp,
hdsl2ShdslSpanConfWorstCaseTargetMarginUp, or hdsl2ShdslSpanConfWorstCaseTargetMarginUp, or
hdsl2ShdslSpanConfUsedTargetMargins could result in invalid hdsl2ShdslSpanConfUsedTargetMargins could result in invalid
parameters used to determine if a data rate can be supported under parameters used to determine if a data rate can be supported under
current and worst-case noise. current and worst-case noise.
Unauthorized changes to hdsl2ShdslSpanConfReferenceClock could Unauthorized changes to hdsl2ShdslSpanConfReferenceClock could
result in the selection of a clock source which might either result in the selection of a clock source that might either
prevent any data from being transferred or impair data transfer. prevent any data from being transferred or impair data transfer.
In addition, an increase in CRC anomalies may be experienced. In addition, an increase in CRC anomalies may be experienced.
Unauthorized changes to hdsl2ShdslSpanConfLineProbeEnable could Unauthorized changes to hdsl2ShdslSpanConfLineProbeEnable could
have a negative effect on selecting the optimum rate or power have a negative effect on selecting the optimum rate or power
level based on current line conditions. level based on current line conditions.
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
skipping to change at page 70, line 25 skipping to change at page 70, line 9
* hdsl2ShdslEndpointThreshLoopAttenuation * hdsl2ShdslEndpointThreshLoopAttenuation
* hdsl2ShdslEndpointThreshSNRMargin * hdsl2ShdslEndpointThreshSNRMargin
* hdsl2ShdslEndpointThreshES * hdsl2ShdslEndpointThreshES
* hdsl2ShdslEndpointThreshSES * hdsl2ShdslEndpointThreshSES
* hdsl2ShdslEndpointThreshCRCanomalies * hdsl2ShdslEndpointThreshCRCanomalies
* hdsl2ShdslEndpointThreshLOSWS * hdsl2ShdslEndpointThreshLOSWS
* hdsl2ShdslEndpointThreshUAS * hdsl2ShdslEndpointThreshUAS
* hdsl2ShdslEndpointAlarmConfProfileRowStatus * hdsl2ShdslEndpointAlarmConfProfileRowStatus
Increasing any of the threshold values could result a notification Increasing any of the threshold values could result in a
being suppressed or deferred. Setting a threshold to 0 could notification being suppressed or deferred. Setting a threshold to
result in a notification being suppressed. Suppressing or 0 could 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 that provides general guidance to the rate limiting of
notifications. Agent implementations not adhering to the rate- notifications. Agent implementations not adhering to the rate-
limiting desires could result in notifications being generated at limiting desires could result in notifications being generated at
an uncontrolled rate. Unauthorized changes to a threshold value an uncontrolled rate. Unauthorized changes to a 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.
skipping to change at page 71, line 27 skipping to change at page 71, line 11
* hdsl2ShdslInvVendorEOCSoftwareVersion * hdsl2ShdslInvVendorEOCSoftwareVersion
* hdsl2ShdslInvStandardVersion * hdsl2ShdslInvStandardVersion
* hdsl2ShdslInvVendorListNumber * hdsl2ShdslInvVendorListNumber
* hdsl2ShdslInvVendorIssueNumber * hdsl2ShdslInvVendorIssueNumber
* hdsl2ShdslInvVendorSoftwareVersion * hdsl2ShdslInvVendorSoftwareVersion
* hdsl2ShdslInvEquipmentCode * hdsl2ShdslInvEquipmentCode
* hdsl2ShdslInvVendorOther * hdsl2ShdslInvVendorOther
* hdsl2ShdslInvTransmissionModeCapability * hdsl2ShdslInvTransmissionModeCapability
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPSec), Even if the network itself is secure (for example by using IPsec),
even then, there is no control as to who on the secure network is even then, there is no control as to who on the secure network is
allowed to access and GET/SET (read/change/create/delete) the objects allowed to access and GET/SET (read/change/create/delete) the objects
in this MIB module. in this MIB module.
It is RECOMMENDED that implementers consider the security features as It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework (see [RFC3410], Section 8), provided by the SNMPv3 framework (see [RFC3410], Section 8),
including full support for the SNMPv3 cryptographic mechanisms (for including full support for the SNMPv3 cryptographic mechanisms (for
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.
6. Acknowledgments 6. Acknowledgements
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 originate 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.
skipping to change at page 72, line 34 skipping to change at page 72, line 23
Mark Johnson (Red Point) Mark Johnson (Red Point)
Sharon Mantin (Orckit) Sharon Mantin (Orckit)
Moti Morgenstern (ECI) Moti Morgenstern (ECI)
Raymond Murphy (Ericsson) Raymond Murphy (Ericsson)
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)
Bert Wijnen (Lucent) Bert Wijnen (Lucent)
Jim Wilson (for Mindspeed)
Michael Wrobel (Memotec) Michael Wrobel (Memotec)
7. References 7. References
7.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., Ed., Perkins, D., Ed., and J. [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
Schoenwaelder, Ed., "Structure of Management Information "Structure of Management Information Version 2 (SMIv2)",
Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. STD 58, RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
Schoenwaelder, Ed., "Textual Conventions for SMIv2", "Textual Conventions for SMIv2", STD 58, RFC 2579, April
STD 58, RFC 2579, April 1999. 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
RFC 3593, September 2003. 3593, September 2003.
[T1E1.4] American National Standards Institute, "ANSI T1E1.4/ [T1E1.4] American National Standards Institute, "ANSI T1E1.4/2000-
2000-006", February 2000. 006", February 2000.
7.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 Internet- "Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002. Standard Management Framework", RFC 3410, 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
RFC 3418, December 2002. 3418, December 2002.
Authors' Addresses Authors' Addresses
Clay Sikes Clay Sikes
Paradyne Networks, Inc. Zhone Technologies, Inc.
Florida Design Center
8454 126th Ave. N. 8454 126th Ave. N.
Largo, FL 33773 Largo, FL 33773
US US
Phone: +1 727 530 8257 Phone: +1 727 530 8257
Fax: +1 727 532 5698 Fax: +1 727 532 5698
Email: csikes@paradyne.com EMail: csikes@zhone.com
Bob Ray Bob Ray
PESA Switching Systems, Inc. PESA Switching Systems, Inc.
330-A Wynn Drive 330-A Wynn Drive
Huntsville, AL 35805 Huntsville, AL 35805
US US
Phone: +1 256 726 9200 ext. 142 Phone: +1 256 726 9200 ext. 142
Fax: +1 256 726 9271 Fax: +1 256 726 9271
Email: rray@pesa.com EMail: rray@pesa.com
Rajesh Abbi Rajesh Abbi
Alcatel USA Alcatel USA
2912 Wake Forest Road 2301 Sugar Bush Road
Raleigh, NC 27609-7860 Raleigh, NC 27612
US US
Phone: +1 919-850-6194 Phone: +1 919-850-6194
Fax: +1 919-850-6670 Fax: +1 919-850-6670
Email: Rajesh.Abbi@alcatel.com EMail: Rajesh.Abbi@alcatel.com
Intellectual Property Statement Full Copyright Statement
Copyright (C) The Internet Society (2005).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at ietf-
ietf-ipr@ietf.org. ipr@ietf.org.
The IETF has been notified of intellectual property rights claimed in
regard to some or all of the specification contained in this
document. For more information consult the online list of claimed
rights.
Disclaimer of Validity
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement
Copyright (C) The Internet Society (2005). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
Acknowledgment Acknowledgement
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 176 change blocks. 
296 lines changed or deleted 282 lines changed or added

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