As per Relevance of the word reference, we have this rfc below:
Network Working Group B.
Request for Comments: 3276 PESA Switching
Category: Standards Track R.
May 2002
Definitions of Managed Objects for High Bit-Rate DSL - 2nd
(HDSL2) and Single-Pair High-Speed Digital
Line (SHDSL)
Status of this
This document specifies an Internet standards track protocol for
Internet community, and requests discussion and suggestions
improvements. Please refer to the current edition of the "
Official Protocol Standards" (STD 1) for the standardization
and status of this protocol. Distribution of this memo is unlimited
Copyright
Copyright (C) The Internet Society (2002). All Rights Reserved
This document defines a portion of the Management Information
(MIB) module for use with network management protocols in
Internet community. In particular, it describes objects used
managing High Bit-Rate DSL - 2nd generation (HDSL2) and Single-
High-Speed Digital Subscriber Line (SHDSL) interfaces
Table of
1. Introduction ............................................. 2
2. The SNMP Network Management Framework .................... 2
3. Introduction ............................................. 3
3.1 Relationship of the HDSL2/SHDSL Line MIB to other MIBs ... 3
3.2 IANA Considerations ...................................... 5
4. Conventions used in the MIB .............................. 5
4.1 Naming Conventions ....................................... 5
4.2 Textual Conventions ...................................... 6
4.3 Structure ................................................ 7
4.4 Counters, Interval Buckets and Thresholds ................ 10
4.5 Profiles ................................................. 11
4.6 Notifications ............................................ 12
5. Conformance and Compliance ............................... 14
6. Definitions .............................................. 14
7. Security Considerations .................................. 60
Ray & Abbi Standards Track [Page 1]
RFC 3276 HDSL2-SHDSL-LINE MIB May 2002
8. Acknowledgments .......................................... 62
9. References ............................................... 63
10. Intellectual Property Notice ............................. 65
11. Authors' Addresses ....................................... 65
12. Full Copyright Statement ................................. 66
1.
This document defines a portion of the Management Information
(MIB) module for use with network management protocols in
Internet community. In particular, it describes objects used
managing High Bit-Rate DSL - 2nd generation (HDSL2) [18] and Single
Pair High-Speed Digital Subscriber Line (SHDSL) interfaces [19].
2. The SNMP Management
The SNMP Management Framework presently consists of five
components
o An overall architecture, described in RFC 2571 [1].
o Mechanisms for describing and naming objects and events for
purpose of management. The first version of this Structure
Management Information (SMI) is called SMIv1 and is described
STD 16, RFC 1155 [2], STD 16, RFC 1212 [3], and RFC 1215 [4].
second version, called SMIv2, is described in STD 58, RFC 2578
[5], RFC 2579 [6], and RFC 2580 [7].
o Message protocols for transferring management information.
first version of the SNMP message protocol is called SNMPv1 and
described in STD 15, RFC 1157 [8]. A second version of the
message protocol, which is not an Internet standards
protocol, is called SNMPv2c and described is in RFC 1901 [9]
RFC 1906 [10]. The third version of the message protocol
called SNMPv3 and is described in RFC 1906 [10], RFC 2572 [11],
and RFC 2574 [12].
o Protocol operations for accessing management information.
first set of protocol operations and associated PDU formats
described in STD 15, RFC 1157 [8]. A second set of
operations and associated PDU formats is described in RFC 1905
[13].
o A set of fundamental applications described in RFC 2573 [14]
the view-based access control mechanism described in RFC 2575
[15].
Ray & Abbi Standards Track [Page 2]
RFC 3276 HDSL2-SHDSL-LINE MIB May 2002
A more detailed introduction to the current SNMP Management
can be found in RFC 2570 [16].
Managed objects are accessed via a virtual information store,
the Management Information Base or MIB. Objects in the MIB
defined using the mechanisms defined in the SMI
This memo specifies a MIB module that is compliant to the SMIv2.
MIB conforming to the SMIv1 can be produced through the
translations. The resulting translated MIB must be
equivalent, except where objects or events are omitted because
translation is possible (use of Counter64). Some machine
information in SMIv2 will be converted into textual descriptions
SMIv1 during the translation process. However, this loss of
readable information is not considered to change the semantics of
MIB
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
document are to be interpreted as described in RFC 2119 [17].
3.
This document describes an SNMP MIB for managing HDSL2/SHDSL Lines
These definitions are based upon the specifications for the HDSL2
SHDSL Embedded Operations Channel (EOC) as defined in
T1E1.4/2000-006 [18] and ITU G.991.2 [19].
The MIB is located in the MIB tree under MIB 2 transmission,
discussed in the MIB-2 Integration (RFC 1213 [20] and RFC 2863 [21])
section of this document
3.1. Relationship of the HDSL2/SHDSL Line MIB to other
This section outlines the relationship of this MIB with other
described in RFCs. Specifically, IF-MIB as presented in RFC 2863
[21] is discussed
3.1.1 General IF-MIB Integration (RFC 2863)
The HDSL2/SHDSL Line MIB specifies the detailed attributes of a
interface. As such, it needs to integrate with RFC 2863 [21].
IANA has assigned the following ifTypes to HDSL2 and SHDSL
Ray & Abbi Standards Track [Page 3]
RFC 3276 HDSL2-SHDSL-LINE MIB May 2002
IANAifType ::= TEXTUAL-
...
SYNTAX INTEGER {
...
hdsl2 (168), -- High Bit-Rate DSL, 2nd
shdsl (169), -- Multirate HDSL
...
}
Note that the ifFixedLengthGroup from RFC 2863 [21] MUST be
and that the ifRcvAddressGroup does not apply to this MIB
3.1.2 Usage of
The MIB branch identified by this ifType contains tables
for this interface type. Most such tables extend the ifEntry table
and are indexed by ifIndex. For interfaces in systems
this MIB, those table entries indexed by ifIndex MUST be persistent
The following attributes are part of the mandatory ifGeneral group
RFC 2863 [21], and are not duplicated in the HDSL2/SHDSL Line MIB
Ray & Abbi Standards Track [Page 4]
RFC 3276 HDSL2-SHDSL-LINE MIB May 2002
===================================================================
ifIndex Interface index
ifDescr See interfaces MIB [21].
ifType hdsl2(168) or shdsl(169).
ifSpeed Set as appropriate
(This is fixed at 1552000 for HDSL
lines
ifPhysAddress This object MUST have an octet
with zero length
ifAdminStatus See interfaces MIB [21].
ifOperStatus See interfaces MIB [21].
ifLastChange See interfaces MIB [21].
ifName See interfaces MIB [21].
ifLinkUpDownTrapEnable Default to enabled(1).
ifHighSpeed Set as appropriate
(For HDSL2 lines, this is fixed at 2)
ifConnectorPresent Set as appropriate
===================================================================
Figure 1: Use of ifTable
3.2 IANA
The HDSL2-SHDSL-LINE-MIB module requires the allocation of a
object identifier for its MODULE-IDENTITY. The IANA has
this object identifier in the transmission subtree (48), defined
the SNMPv2-SMI MIB module
4. Conventions used in the
4.1. Naming
A. xtuC refers to a central site terminal unit
H2TU-C for HDSL2, or STU-C for SHDSL
B. xtuR refers to a remote site terminal unit
H2TU-R for HDSL2, or STU-R for SHDSL
C. xtu refers to a terminal unit; either an xtuC or xtuR
Ray & Abbi Standards Track [Page 5]
RFC 3276 HDSL2-SHDSL-LINE MIB May 2002
D. xru refer to a regenerator unit
H2RU for HDSL2, or SRU for SHDSL
E. xU refers to any HDSL2/SHDSL unit; either an xtu or xru
F. CRC is cyclic redundancy check [19].
G. ES means errored second [19].
H. LOSW means loss of sync word [19].
I. LOSWS means LOSW seconds [19].
J. SES means severely errored second [19].
K. SNR means signal-to-noise ratio [19].
L. UAS means unavailable second [19].
4.2. Textual
The following textual conventions are defined to reflect the
topology in the MIB (further discussed in the following section)
to define the behavior of the statistics to be maintained by
agent
o Hdsl2ShdslUnitId
Attributes with this syntax uniquely identify each unit in
HDSL2/SHDSL span. It mirrors the EOC addressing mechanism
xtuC(1) - CO terminal
xtuR(2) - CPE terminal
xru1(3) .. xru8(10) - regenerators, numbered
central office
o Hdsl2ShdslUnitSide
Attributes with this syntax reference the two sides of a unit
networkSide(1) - N in figure 2,
customerSide(2) - C in figure 2,
o Hdsl2ShdslWirePair
Attributes with this syntax reference the wire-pairs connecting
units
wirePair1(1) - First pair for HDSL2/SHDSL
wirePair2(2) - Optional second pair for SHDSL only
o Hdsl2ShdslTransmissionModeType
Attributes with this syntax specify the regional setting for a
line. Specified as a BITS construct, the two mode types are
Ray & Abbi Standards Track [Page 6]
RFC 3276 HDSL2-SHDSL-LINE MIB May 2002
region1 - ITU-T G.991.2 Annex
region2 - ITU-T G.991.2 Annex
o Hdsl2ShdslPerfCurrDayCount
Attributes with this syntax define the behavior of the 1-day (24
hour) gauges found in the MIB
o Hdsl2Shdsl1DayIntervalCount
Attributes with this syntax define the behavior of the 1-day (24
hour) interval counters found in the MIB
o Hdsl2ShdslPerfTimeElapsed
Attributes with this syntax define the behavior of the elapsed
counters found in the MIB
o Hdsl2ShdslPerfIntervalThreshold
Attributes with this syntax define the behavior of the
thresholds found in the MIB
o Hdsl2
Attributes with this syntax define the clock references for
HDSL2/SHDSL span
4.3.
The MIB is structured into following MIB groups
o Span Configuration Group
This group supports MIB objects for configuring parameters for
HDSL2/SHDSL span. It contains the following table
- hdsl2
o Span Status Group
This group supports MIB objects for retrieving span
information. It contains the following table
- hdsl2
Ray & Abbi Standards Track [Page 7]
RFC 3276 HDSL2-SHDSL-LINE MIB May 2002
o Unit Inventory Group
This group supports MIB objects for retrieving unit
information about units in HDSL2/SHDSL lines via the EOC. It
the following table
- hdsl2
o Segment Endpoint Configuration Group
This group supports MIB objects for configuring parameters for
HDSL2/SHDSL segment endpoints. It contains the following table
- hdsl2
o Segment Endpoint Current Status/Performance Group
This group supports MIB objects that provide the
status/performance information relating to segment endpoints.
contains the following table
- hdsl2
o Segment Endpoint 15-Minute Interval Status/Performance Group
This group supports MIB objects that provide
status/performance information relating to segment endpoints in 15-
minute intervals. It contains the following table
- hdsl2Shdsl15
o Segment Endpoint 1-Day Interval Status/Performance Group
This group supports MIB objects that provide
status/performance information relating to segment endpoints in 1-
intervals. It contains the following table
- hdsl2Shdsl1
o Maintenance Group
This group supports MIB objects for performing maintenance
such as loopbacks for HDSL2/SHDSL lines. It contains the
table(s):
- hdsl2
- hdsl2
Ray & Abbi Standards Track [Page 8]
RFC 3276 HDSL2-SHDSL-LINE MIB May 2002
o Span Configuration Profile Group
This group supports MIB objects for defining configuration
for HDSL2/SHDSL Spans. It contains the following table
- hdsl2
o Segment Endpoint Alarm Configuration Profile Group
This group supports MIB objects for defining alarm
profiles for HDSL2/SHDSL Segment Endpoints. It contains
following table
- hdsl2
o Notifications Group
This group defines the notifications supported for HDSL2/SHDSL lines
- hdsl2
- hdsl2
- hdsl2
- hdsl2
- hdsl2
- hdsl2
- hdsl2
- hdsl2
- hdsl2
- hdsl2
- hdsl2
- hdsl2
- hdsl2
- hdsl2
- hdsl2
- hdsl2
4.3.1 Line
An HDSL2/SHDSL Line consists of a minimum of two units - xtuC (
central termination unit) and an xtuR (the remote termination unit).
The line may optionally support up to 8 repeater/regenerator
(xru) as shown in the figure below
Ray & Abbi Standards Track [Page 9]
RFC 3276 HDSL2-SHDSL-LINE MIB May 2002
<-- Network Side Customer Side -->
||
<~~~> <~~~> HDSL2/SHDSL Segments <~~~>
+-------+ +-------+ +-------+ +-------+ +-------+
+ C=1=N C=1=N C=..1..=N C=1=N +
| xtuC | | xru1 | | xru2 | | xru8 | | xtuR |
+ C=2=N C=2=N C=..2..=N C=2=N +
+-------+ +-------+ +-------+ +-------+ +-------+
Key: HDSL2/SHDSL
<~~~~> HDSL2/SHDSL
=1= HDSL2/SHDSL wire-pair-1
=2= SHDSL optional wire-pair-2 (Not applicable to HDSL2)
C Customer Side Segment Endpoint (modem
N Network Side Segment Endpoint (modem
Figure 2: General topology for an HDSL2/SHDSL
4.4. Counters, Interval Buckets and
For SNR Margin, Loop Attenuation, ES, SES, CRC anomalies, LOSW,
UAS, there are event counters, current 15-minute and 0 to 96 15-
minute history bucket(s) of "interval-counters", as well as
and 0 to 30 previous 1-day interval-counter(s). Each current 15-
minute event bucket has an associated threshold notification
Unlike RFC 2493 [22] and RFC 2662 [23], there is no representation
the MIB for invalid buckets. In those cases where the data for
interval is suspect or known to be invalid, the agent MUST NOT
the interval. If the current 15-minute event bucket is determined
be invalid, notifications based upon the value of the event
MUST NOT be generated
Not reporting an interval will result in holes in the
table. For example, the table, hdsl2Shdsl15MinIntervalTable,
indexed by { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide
hdsl2ShdslEndpointWirePair, hdsl2Shdsl15MinIntervalNumber}.
interval 12 is determined to be invalid but intervals 11 and 13
valid, a Get Next operation on the indices .1.1.1.1.11 would
indices .1.1.1.1.13.
Ray & Abbi Standards Track [Page 10]
RFC 3276 HDSL2-SHDSL-LINE MIB May 2002
There is no requirement for an agent to ensure a fixed
between the start of a fifteen minute interval and any wall clock
however some implementations may align the fifteen minute
with quarter hours. Likewise, an implementation may choose to
one day intervals with the start of a day
Counters are not reset when an xU is reinitialized, only when
agent is reset or reinitialized (or under specific request
the scope of this MIB).
4.5.
As a managed node can handle a large number of xUs, (e.g.,
or perhaps thousands of lines), provisioning every parameter on
xU may become burdensome. Moreover, most lines are
identically with the same set of parameters. To simplify
provisioning process, this MIB makes use of profiles. A profile is
set of parameters that can be shared by multiple lines using the
configuration
The following profiles are used in this MIB
o Span Configuration Profiles - Span configuration profiles
parameters for configuring HDSL2/SHDSL spans. They are defined
the hdsl2ShdslSpanConfProfileTable. Since span
parameters are only applicable for SHDSL, the support for
configuration profiles are optional for HDSL2 interfaces
Note that the configuration of the span dictates the behavior
each individual segment end point in the span. If a
configuration is provisioned for any given segment end
within the span, the new configuration for this segment end
will override the span configuration for this segment end
only
o Segment Endpoint Alarm Configuration Profiles - These
contain parameters for configuring alarm thresholds
HDSL2/SHDSL segment endpoints. These profiles are defined in
hdsl2ShdslEndpointAlarmConfProfileTable
The index value for this profile is a locally-
administratively assigned name for the profile having the
convention `SnmpAdminString' (RFC 2571 [1]).
One or more lines may be configured to share parameters of a
profile (e.g., hdsl2ShdslEndpointAlarmConfProfile = `silver')
setting its hdsl2ShdslEndpointAlarmConfProfile objects to the
of this profile. If a change is made to the profile, all lines
Ray & Abbi Standards Track [Page 11]
RFC 3276 HDSL2-SHDSL-LINE MIB May 2002
refer to it will be reconfigured to the changed parameters. Before
profile can be deleted or taken out of service it must be
unreferenced from all associated lines
Implementations MUST provide a default profile whose name is `DEFVAL
for each profile type. The values of the associated parameters
be vendor specific unless otherwise indicated in this document
Before a line's profiles have been set, these profiles will
automatically used by setting hdsl2ShdslEndpointAlarmConfProfile
hdsl2ShdslSpanConfProfile to `DEFVAL' where appropriate.
default profile name, 'DEFVAL', is considered reserved in the
of profiles defined in this MIB
Profiles are created, assigned, and deleted dynamically using
profile name and profile row status in each of the four
tables
Profile changes MUST take effect immediately. These changes
result in a restart (hard reset or soft restart) of the units on
line
4.6.
The ability to generate the SNMP notifications coldStart/
(per [21]) which are per agent (e.g., per Digital Subscriber
Access Multiplexer, or DSLAM, in such a device), and linkUp/
(per [21]) which are per interface (i.e., HDSL2/SHDSL line)
required
A linkDown notification MAY be generated whenever any of ES, SES,
Anomaly, LOSW, or UAS event occurs. The corresponding
notification MAY be sent when all link failure conditions
cleared
The notifications defined in this MIB are for initialization
and for the threshold crossings associated with the following events
ES, SES, CRC Anomaly, LOSW, and UAS. Each threshold has its
enable/threshold value. When that value is 0, the notification
disabled
The hdsl2ShdslEndpointCurrStatus is a bitmask representing
outstanding error conditions associated with a particular
Endpoint. Note that since status of remote endpoints is obtained
the EOC, this information may be unavailable for units that
unreachable via EOC during a line error condition. Therefore,
all conditions may always be included in its current status
Notifications corresponding to the bit fields in this object
defined
Ray & Abbi Standards Track [Page 12]
RFC 3276 HDSL2-SHDSL-LINE MIB May 2002
Two alarm conditions, SNR Margin Alarm and Loop Attenuation Alarm
are organized in a manner slightly different from that implied in
EOC specifications. In the MIB, these alarm conditions are tied
the two thresholds hdsl2ShdslEndpointThreshSNRMargin
hdsl2ShdslEndpointThreshLoopAttenuation found in
hdsl2ShdslEndpointAlarmConfProfileTable. In the EOC, the
conditions associated with these thresholds are per-unit. In
MIB, these alarm conditions are per-endpoint. For terminal units
this has no impact. For repeaters, this implies an
variance where the agent in the terminal unit is responsible
detecting a threshold crossing. As the reporting of a
detected alarm condition to the polling terminal unit occurs in
same EOC message as the reporting of the current SNR Margin and
Attenuation values, it is anticipated that this will have very
impact on agent implementation
A threshold notification occurs whenever the corresponding
15-minute interval error counter becomes equal to, or exceeds
threshold value. One notification may be sent per interval
interface. Since the current 15-minute counter is reset to 0
15 minutes, and if the condition persists, the notification may
as often as every 15 minutes. For example, to get a
whenever a "loss of" event occurs (but at most once every 15
minutes), set the corresponding threshold to 1. The agent
generate a notification when the event originally occurs
Note that the Network Management System, or NMS, may receive
linkDown notification, as well, if enabled (
ifLinkUpDownTrapEnable [21]). At the beginning of the next 15
interval, the counter is reset. When the first second goes by
the event occurs, the current interval bucket will be 1, which
the threshold, and the notification will be sent again
A hdsl2ShdslSpanInvalidNumRepeaters notification may be
following completion of the discovery phase if the number
repeaters discovered on the line differs from the number of
specified in hdsl2ShdslSpanConfNumRepeaters. For those
where the number of provisioned repeaters is greater than
encountered during span discovery, all table entries associated
the nonexistent repeaters are to be discarded. For those
where the number of provisioned repeaters is less than
encountered during span discovery, additional table entries are to
created using the default span configuration profile
Ray & Abbi Standards Track [Page 13]
RFC 3276 HDSL2-SHDSL-LINE MIB May 2002
5. Conformance and
For both HDSL2 and SHDSL lines, the following group(s) are mandatory
hdsl2
hdsl2
hdsl2
hdsl2
hdsl2Shdsl15
hdsl2Shdsl1
hdsl2
hdsl2
hdsl2
For HDSL2 lines, the following group(s) are optional
hdsl2
hdsl2
6.
HDSL2-SHDSL-LINE-MIB DEFINITIONS ::=
MODULE-IDENTITY
OBJECT-TYPE
Counter32,
Unsigned32,
Gauge32,
NOTIFICATION-TYPE
Integer32,
transmission FROM SNMPv2-
RowStatus
TEXTUAL-CONVENTION FROM SNMPv2-
ifIndex FROM IF-
PerfCurrentCount
PerfIntervalCount FROM PerfHist-TC-
SnmpAdminString FROM SNMP-FRAMEWORK-
MODULE-COMPLIANCE
OBJECT-GROUP
NOTIFICATION-GROUP FROM SNMPv2-CONF
hdsl2ShdslMIB MODULE-
LAST-UPDATED "200205090000Z" -- May 9, 2002
ORGANIZATION "ADSLMIB Working Group
CONTACT-INFO "WG-email: adslmib@ietf.
Info: https://www1.ietf.org/mailman/listinfo/
Chair: Mike
Ray & Abbi Standards Track [Page 14]
RFC 3276 HDSL2-SHDSL-LINE MIB May 2002
Postal: P.O. Box 37324
Raleigh NC 27627-7324
Email: sneedmike@hotmail.
Co-editor: Bob
PESA Switching Systems, Inc
Postal: 330-A Wynn
Huntsville, AL 35805
Email: rray@pesa.
Phone: +1 256 726 9200 ext. 142
Co-editor: Rajesh
Alcatel
Postal: 2912 Wake Forest
Raleigh, NC 27609-7860
Email: Rajesh.Abbi@alcatel.
Phone: +1 919 850 6194
"
"This MIB module defines a collection of objects for
HDSL2/SHDSL lines. An agent may reside at either end of
line, however the MIB is designed to require no
communication between the modems beyond that inherent in
low-level EOC line protocol as defined in ANSI T1E1.4/2000-006
(for HDSL2 lines), or in ITU G.991.2 (for SHDSL lines)."
REVISION "200205090000Z" -- May 9, 2002
DESCRIPTION "Initial version, published as RFC 3276."
::= { transmission 48 }
hdsl2ShdslMibObjects OBJECT IDENTIFIER ::= { hdsl2ShdslMIB 1 }
-- Textual Conventions used in this
--
Hdsl2ShdslPerfCurrDayCount ::= TEXTUAL-
STATUS
"A gauge associated with interface performance measurements
a current 1-day (24 hour) measurement interval
The value of this gauge starts at zero at the beginning of
interval and is increased when associated events occur,
the end of the 1-day interval. At that time the value of
gauge is stored in the previous 1-day history interval,
defined in a companion object of
Ray & Abbi Standards Track [Page 15]
RFC 3276 HDSL2-SHDSL-LINE MIB May 2002
Hdsl2Shdsl1DayIntevalCount, and the current interval
is restarted at zero
In the case where the agent has no valid data available
this interval the corresponding object instance is
available and upon a retrieval request a corresponding
message shall be returned to indicate that this instance
not exist. Please note that zero is a valid value."
SYNTAX Gauge32
Hdsl2Shdsl1DayIntervalCount ::= TEXTUAL-
STATUS
"A counter associated with interface performance
during the most previous 1-day (24 hour) measurement interval
The value of this gauge is equal to the value of the
day gauge, as defined in a companion object of
Hdsl2ShdslPerfCurrDayCount, at the end of its most
interval
In the case where the agent has no valid data available
this interval the corresponding object instance is
available and upon a retrieval request a corresponding
message shall be returned to indicate that this instance
not exist."
SYNTAX Gauge32
Hdsl2ShdslPerfTimeElapsed ::= TEXTUAL-
STATUS
"The number of seconds that have elapsed since the beginning
the current measurement period. If, for some reason, such
an adjustment in the system's time-of-day clock or the
of a leap second, the current interval exceeds the
value, the agent will return the maximum value
For 15 minute intervals, the range is limited to (0..899).
For 24 hour intervals, the range is limited to (0..86399)."
SYNTAX Unsigned32(0..86399)
Hdsl2ShdslPerfIntervalThreshold ::= TEXTUAL-
STATUS
"This convention defines a range of values that may be set
a fault threshold alarm control. As the number of seconds
a 15-minute interval numbers at most 900, objects of this
may have a range of 0...900, where the value of 0 disables
alarm."
Ray & Abbi Standards Track [Page 16]
RFC 3276 HDSL2-SHDSL-LINE MIB May 2002
SYNTAX Unsigned32(0..900)
Hdsl2ShdslUnitId ::= TEXTUAL-
STATUS
"This is the unique identification for all units in
HDSL2/SHDSL Span. It is based on the EOC unit
scheme with reference to the xtuC."
SYNTAX
{
xtuC(1),
xtuR(2),
xru1(3),
xru2(4),
xru3(5),
xru4(6),
xru5(7),
xru6(8),
xru7(9),
xru8(10)
}
Hdsl2ShdslUnitSide ::= TEXTUAL-
STATUS
"This is the referenced side of a HDSL2/SHDSL unit -
or Customer side. The side facing the Network is the
side, while the side facing the Customer is the Customer side."
SYNTAX
{
networkSide(1),
customerSide(2)
}
Hdsl2ShdslWirePair ::= TEXTUAL-
STATUS
"This is the referenced pair of wires in a HDSL2/SHDSL Segment
HDSL2 only supports a single pair (wirePair1), while
supports an optional second pair (wirePair2)."
SYNTAX
{
wirePair1(1),
wirePair2(2)
}
Hdsl2ShdslTransmissionModeType ::= TEXTUAL-
STATUS
Ray & Abbi Standards Track [Page 17]
RFC 3276 HDSL2-SHDSL-LINE MIB May 2002
"Contains the regional setting of the HDSL2/SHDSL span
represented as a bit-map of possible settings. The
bit positions are
Bit Meaning
1 region 1 Indicates ITU-T G.991.2 Annex A
2 region 2 Indicates ITU-T G.991.2 Annex B."
SYNTAX
{
region1(0),
region2(1)
}
Hdsl2ShdslClockReferenceType ::= TEXTUAL-
STATUS
"The various STU-C symbol clock references for
HDSL2/SHDSL span, represented as an enumeration."
SYNTAX
{
localClk(1), -- Mode-1 per G991.2
networkClk(2), -- Mode-2 per G991.2
dataOrNetworkClk(3), -- Mode-3a per G991.2
dataClk(4) -- Mode-3b per G991.2
}
-- Span Configuration
--
hdsl2ShdslSpanConfTable OBJECT-
SYNTAX SEQUENCE OF Hdsl2
MAX-ACCESS not-
STATUS
"This table supports overall configuration of HDSL2/
Spans. Entries in this table MUST be maintained in
persistent manner."
::= { hdsl2ShdslMibObjects 1 }
hdsl2ShdslSpanConfEntry OBJECT-
SYNTAX Hdsl2
MAX-ACCESS not-
STATUS
"An entry in the hdsl2ShdslSpanConfTable. Each
represents the complete Span in a single HDSL2/SHDSL line
It is indexed by the ifIndex of the associated HDSL2/
Ray & Abbi Standards Track [Page 18]
RFC 3276 HDSL2-SHDSL-LINE MIB May 2002
line."
INDEX { ifIndex }
::= { hdsl2ShdslSpanConfTable 1 }
Hdsl2ShdslSpanConfEntry ::=
{
hdsl2ShdslSpanConfNumRepeaters Unsigned32,
hdsl2ShdslSpanConfProfile SnmpAdminString
hdsl2ShdslSpanConfAlarmProfile
}
hdsl2ShdslSpanConfNumRepeaters OBJECT-
SYNTAX Unsigned32(0..8)
UNITS "repeaters
MAX-ACCESS read-
STATUS
"This object provisions the number of repeaters/
in this HDSL2/SHDSL Span."
::= { hdsl2ShdslSpanConfEntry 1 }
hdsl2ShdslSpanConfProfile OBJECT-
SYNTAX SnmpAdminString (SIZE(1..32))
MAX-ACCESS read-
STATUS
"This object is a pointer to a span configuration profile
the hdsl2ShdslSpanConfProfileTable, which applies to this span
The value of this object is the index of the referenced
in the hdsl2ShdslSpanConfProfileTable. Note that
configuration profiles are only applicable to SHDSL lines
HDSL2 lines MUST reference the default profile, 'DEFVAL'.
By default, this object will have the value 'DEFVAL' (the
of the default profile).
Any attempt to set this object to a value that is not the
of the index for an active entry in the profile table
hdsl2ShdslSpanConfProfileTable, MUST be rejected."
::= { hdsl2ShdslSpanConfEntry 2 }
hdsl2ShdslSpanConfAlarmProfile OBJECT-
SYNTAX SnmpAdminString (SIZE(1..32))
MAX-ACCESS read-
STATUS
"This object is a pointer to an Alarm configuration profile
Ray & Abbi Standards Track [Page 19]
RFC 3276 HDSL2-SHDSL-LINE MIB May 2002
the hdsl2ShdslEndpointAlarmConfProfileTable. The value of
object is the index of the referenced profile in
hdsl2ShdslEndpointAlarmConfProfileTable. The alarm
configuration in the referenced profile will be used by
for all segment endpoints in this span. Individual
may override this profile by explicitly specifying some
profile in the hdsl2ShdslEndpointConfTable. By default,
object will have the value 'DEFVAL' (the index of the
profile).
Any attempt to set this object to a value that is not the
of the index for an active entry in the profile table
hdsl2ShdslEndpointAlarmConfProfileTable, MUST be rejected."
::= { hdsl2ShdslSpanConfEntry 3 }
-- Span Status
--
hdsl2ShdslSpanStatusTable OBJECT-
SYNTAX SEQUENCE OF Hdsl2
MAX-ACCESS not-
STATUS
"This table provides overall status information
HDSL2/SHDSL spans. This table contains live data
equipment. As such, it is NOT persistent."
::= { hdsl2ShdslMibObjects 2 }
hdsl2ShdslSpanStatusEntry OBJECT-
SYNTAX Hdsl2
MAX-ACCESS not-
STATUS
"An entry in the hdsl2ShdslSpanStatusTable. Each
represents the complete span in a single HDSL2/SHDSL line
It is indexed by the ifIndex of the associated HDSL2/
line."
INDEX { ifIndex }
::= { hdsl2ShdslSpanStatusTable 1 }
Hdsl2ShdslSpanStatusEntry ::=
{
hdsl2ShdslStatusNumAvailRepeaters Unsigned32,
hdsl2ShdslStatusMaxAttainableLineRate Unsigned32,
hdsl2ShdslStatusActualLineRate Unsigned32,
hdsl2
Hdsl2
Ray & Abbi Standards Track [Page 20]
RFC 3276 HDSL2-SHDSL-LINE MIB May 2002
}
hdsl2ShdslStatusNumAvailRepeaters OBJECT-
SYNTAX Unsigned32(0..8)
MAX-ACCESS read-
STATUS
"Contains the actual number of repeaters/
discovered in this HDSL2/SHDSL span."
::= { hdsl2ShdslSpanStatusEntry 1 }
hdsl2ShdslStatusMaxAttainableLineRate OBJECT-
SYNTAX Unsigned32(0..4112000)
UNITS "bps
MAX-ACCESS read-
STATUS
"Contains the maximum attainable line rate in this HDSL2/
span. This object provides the maximum rate the line
capable of achieving. This is based upon measurements
during line probing."
::= { hdsl2ShdslSpanStatusEntry 2 }
hdsl2ShdslStatusActualLineRate OBJECT-
SYNTAX Unsigned32(0..4112000)
UNITS "bps
MAX-ACCESS read-
STATUS
"Contains the actual line rate in this HDSL2/SHDSL span.
should equal ifSpeed."
::= { hdsl2ShdslSpanStatusEntry 3 }
hdsl2ShdslStatusTransmissionModeCurrent OBJECT-
SYNTAX Hdsl2
MAX-ACCESS read-
STATUS
"Contains the current Power Spectral Density (PSD)
setting of the HDSL2/SHDSL span."
::= { hdsl2ShdslSpanStatusEntry 4 }
-- Unit Inventory
--
hdsl2ShdslInventoryTable OBJECT-
SYNTAX SEQUENCE OF Hdsl2
MAX-ACCESS not-
Ray & Abbi Standards Track [Page 21]
RFC 3276 HDSL2-SHDSL-LINE MIB May 2002
STATUS
"This table supports retrieval of unit inventory
available via the EOC from units in a HDSL2/SHDSL line
Entries in this table are dynamically created during
line discovery process. The life cycle for these
is as follows
- xtu discovers a device, either a far-end xtu or an
- an inventory table entry is created for the
- the line goes down for whatever
- inventory table entries for unreachable devices
destroyed
As these entries are created/destroyed dynamically,
are NOT persistent."
::= { hdsl2ShdslMibObjects 3 }
hdsl2ShdslInventoryEntry OBJECT-
SYNTAX Hdsl2
MAX-ACCESS not-
STATUS
"An entry in the hdsl2ShdslInventoryTable. Each
represents inventory information for a single unit in
HDSL2/SHDSL line. It is indexed by the ifIndex of
HDSL2/SHDSL line and the Hdsl2ShdslUnitId of
associated unit."
INDEX { ifIndex, hdsl2ShdslInvIndex }
::= { hdsl2ShdslInventoryTable 1 }
Hdsl2ShdslInventoryEntry ::=
{
hdsl2ShdslInvIndex Hdsl2ShdslUnitId
hdsl2ShdslInvVendorID OCTET STRING
hdsl2ShdslInvVendorModelNumber OCTET STRING
hdsl2ShdslInvVendorSerialNumber OCTET STRING
hdsl2ShdslInvVendorEOCSoftwareVersion Integer32,
hdsl2ShdslInvStandardVersion Integer32,
hdsl2ShdslInvVendorListNumber OCTET STRING
hdsl2ShdslInvVendorIssueNumber OCTET STRING
hdsl2ShdslInvVendorSoftwareVersion OCTET STRING
hdsl2ShdslInvEquipmentCode OCTET STRING
hdsl2ShdslInvVendorOther OCTET STRING
hdsl2
Hdsl2
Ray & Abbi Standards Track [Page 22]
RFC 3276 HDSL2-SHDSL-LINE MIB May 2002
}
hdsl2ShdslInvIndex OBJECT-
SYNTAX Hdsl2
MAX-ACCESS not-
STATUS
"Each entry in this table corresponds to a physical
in a HDSL2/SHDSL Span. It is based on the EOC unit
scheme with reference to the xtuC."
::= { hdsl2ShdslInventoryEntry 1 }
hdsl2ShdslInvVendorID OBJECT-
SYNTAX OCTET STRING(SIZE(8))
MAX-ACCESS read-
STATUS
"Vendor ID as reported in an Inventory Response message."
::= { hdsl2ShdslInventoryEntry 2 }
hdsl2ShdslInvVendorModelNumber OBJECT-
SYNTAX OCTET STRING(SIZE(12))
MAX-ACCESS read-
STATUS
"Vendor model number as reported in an Inventory
message."
::= { hdsl2ShdslInventoryEntry 3 }
hdsl2ShdslInvVendorSerialNumber OBJECT-
SYNTAX OCTET STRING(SIZE(12))
MAX-ACCESS read-
STATUS
"Vendor serial number as reported in an Inventory
message."
::= { hdsl2ShdslInventoryEntry 4 }
hdsl2ShdslInvVendorEOCSoftwareVersion OBJECT-
SYNTAX Integer32
MAX-ACCESS read-
STATUS
"Vendor EOC version as reported in a Discovery
message."
::= { hdsl2ShdslInventoryEntry 5 }
hdsl2ShdslInvStandardVersion OBJECT-
Ray & Abbi Standards Track [Page 23]
RFC 3276 HDSL2-SHDSL-LINE MIB May 2002
SYNTAX Integer32
MAX-ACCESS read-
STATUS
"Version of the HDSL2/SHDSL standard implemented, as
in an Inventory Response message."
::= { hdsl2ShdslInventoryEntry 6 }
hdsl2ShdslInvVendorListNumber OBJECT-
SYNTAX OCTET STRING(SIZE(3))
MAX-ACCESS read-
STATUS
"Vendor list number as reported in an Inventory
message."
::= { hdsl2ShdslInventoryEntry 7 }
hdsl2ShdslInvVendorIssueNumber OBJECT-
SYNTAX OCTET STRING(SIZE(2))
MAX-ACCESS read-
STATUS
"Vendor issue number as reported in an Inventory
message."
::= { hdsl2ShdslInventoryEntry 8 }
hdsl2ShdslInvVendorSoftwareVersion OBJECT-
SYNTAX OCTET STRING(SIZE(6))
MAX-ACCESS read-
STATUS
"Vendor software version as reported in an Inventory
message."
::= { hdsl2ShdslInventoryEntry 9 }
hdsl2ShdslInvEquipmentCode OBJECT-
SYNTAX OCTET STRING(SIZE(10))
MAX-ACCESS read-
STATUS
"Equipment code conforming to ANSI T1.213, Coded
of Equipment Entities."
::= { hdsl2ShdslInventoryEntry 10 }
hdsl2ShdslInvVendorOther OBJECT-
SYNTAX OCTET STRING(SIZE(12))
MAX-ACCESS read-
STATUS
Ray & Abbi Standards Track [Page 24]
RFC 3276 HDSL2-SHDSL-LINE MIB May 2002
"Other vendor information as reported in an Inventory
message."
::= { hdsl2ShdslInventoryEntry 11 }
hdsl2ShdslInvTransmissionModeCapability OBJECT-
SYNTAX Hdsl2
MAX-ACCESS read-
STATUS
"Contains the transmission mode capability of the SHDSL unit."
::= { hdsl2ShdslInventoryEntry 12 }
-- Segment Endpoint Configuration
--
hdsl2ShdslEndpointConfTable OBJECT-
SYNTAX SEQUENCE OF Hdsl2
MAX-ACCESS not-
STATUS
"This table supports configuration parameters for
endpoints in a HDSL2/SHDSL line. As this table is
by ifIndex, it MUST be maintained in a persistent manner."
::= { hdsl2ShdslMibObjects 4 }
hdsl2ShdslEndpointConfEntry OBJECT-
SYNTAX Hdsl2
MAX-ACCESS not-
STATUS
"An entry in the hdsl2ShdslEndpointConfTable. Each
represents a single segment endpoint in a HDSL2/SHDSL line
It is indexed by the ifIndex of the HDSL2/SHDSL line,
UnitId of the associated unit, the side of the unit, and
wire-pair of the associated modem."
INDEX { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide
hdsl2ShdslEndpointWirePair
::= { hdsl2ShdslEndpointConfTable 1 }
Hdsl2ShdslEndpointConfEntry ::=
{
hdsl2ShdslEndpointSide Hdsl2ShdslUnitSide
hdsl2ShdslEndpointWirePair Hdsl2ShdslWirePair
hdsl2ShdslEndpointAlarmConfProfile
}
Ray & Abbi Standards Track [Page 25]
RFC 3276 HDSL2-SHDSL-LINE MIB May 2002
hdsl2ShdslEndpointSide OBJECT-
SYNTAX Hdsl2
MAX-ACCESS not-
STATUS
"The side of the unit associated with this segment endpoint -
Network/Customer side - as per the Hdsl2ShdslUnitSide
convention."
::= { hdsl2ShdslEndpointConfEntry 1 }
hdsl2ShdslEndpointWirePair OBJECT-
SYNTAX Hdsl2
MAX-ACCESS not-
STATUS
"The wire-pair of the modem associated with this
endpoint as per the Hdsl2ShdslWirePair textual convention."
::= { hdsl2ShdslEndpointConfEntry 2 }
hdsl2ShdslEndpointAlarmConfProfile OBJECT-
SYNTAX SnmpAdminString (SIZE(0..32))
MAX-ACCESS read-
STATUS
"This object configures the alarm threshold values to be
for this segment endpoint. The values are obtained from
alarm configuration profile referenced by this object.
value of this object is the index of the referenced profile
the hdsl2ShdslEndpointAlarmConfProfileTable, or NULL (a zero
length SnmpAdminString). If the value is a zero-
SnmpAdminString, the endpoint uses the default
Configuration Profile for the associated span as per
hdsl2ShdslSpanConfAlarmProfile object in
hdsl2ShdslSpanConfTable. The default value of this object
a zero-length SnmpAdminString
Any attempt to set this object to a value that is not the
of the index for an active entry in the profile table
hdsl2ShdslEndpointAlarmConfProfileTable, MUST be rejected."
::= { hdsl2ShdslEndpointConfEntry 3 }
-- Segment Endpoint Current Status/Performance
--
hdsl2ShdslEndpointCurrTable OBJECT-
SYNTAX SEQUENCE OF Hdsl2
MAX-ACCESS not-
STATUS
Ray & Abbi Standards Track [Page 26]
RFC 3276 HDSL2-SHDSL-LINE MIB May 2002
"This table contains current status and performance
for segment endpoints in HDSL2/SHDSL Lines. As with
tables in this MIB indexed by ifIndex, entries in this
MUST be maintained in a persistent manner."
::= { hdsl2ShdslMibObjects 5 }
hdsl2ShdslEndpointCurrEntry OBJECT-
SYNTAX Hdsl2
MAX-ACCESS not-
STATUS
"An entry in the hdsl2ShdslEndpointCurrTable. Each
contains status and performance information relating to
single segment endpoint. It is indexed by the ifIndex of
HDSL2/SHDSL line, the UnitId of the associated unit, the
of the unit, and the wire-pair of the associated modem."
INDEX { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide
hdsl2ShdslEndpointWirePair }
::= { hdsl2ShdslEndpointCurrTable 1 }
Hdsl2ShdslEndpointCurrEntry ::=
{
hdsl2ShdslEndpointCurrAtn Integer32,
hdsl2ShdslEndpointCurrSnrMgn Integer32,
hdsl2ShdslEndpointCurrStatus BITS
hdsl2ShdslEndpointES Counter32,
hdsl2ShdslEndpointSES Counter32,
hdsl2ShdslEndpointCRCanomalies Counter32,
hdsl2ShdslEndpointLOSWS Counter32,
hdsl2ShdslEndpointUAS Counter32,
hdsl2ShdslEndpointCurr15
Hdsl2ShdslPerfTimeElapsed
hdsl2ShdslEndpointCurr15MinES PerfCurrentCount
hdsl2ShdslEndpointCurr15MinSES PerfCurrentCount
hdsl2ShdslEndpointCurr15MinCRCanomalies PerfCurrentCount
hdsl2ShdslEndpointCurr15MinLOSWS PerfCurrentCount
hdsl2ShdslEndpointCurr15MinUAS PerfCurrentCount
hdsl2ShdslEndpointCurr1
Hdsl2ShdslPerfTimeElapsed
hdsl2ShdslEndpointCurr1
Hdsl2ShdslPerfCurrDayCount
hdsl2ShdslEndpointCurr1
Hdsl2ShdslPerfCurrDayCount
hdsl2ShdslEndpointCurr1
Hdsl2ShdslPerfCurrDayCount
hdsl2ShdslEndpointCurr1
Ray & Abbi Standards Track [Page 27]
RFC 3276 HDSL2-SHDSL-LINE MIB May 2002
Hdsl2ShdslPerfCurrDayCount
hdsl2ShdslEndpointCurr1
Hdsl2
}
hdsl2ShdslEndpointCurrAtn OBJECT-
SYNTAX Integer32(-127..128)
UNITS "dB
MAX-ACCESS read-
STATUS
"The current loop attenuation for this endpoint as reported
a Network or Customer Side Performance Status message."
REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7"
::= { hdsl2ShdslEndpointCurrEntry 1 }
hdsl2ShdslEndpointCurrSnrMgn OBJECT-
SYNTAX Integer32(-127..128)
UNITS "dB
MAX-ACCESS read-
STATUS
"The current SNR margin for this endpoint as reported in
Status Response/SNR message."
REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7"
::= { hdsl2ShdslEndpointCurrEntry 2 }
hdsl2ShdslEndpointCurrStatus OBJECT-
SYNTAX
{
noDefect(0),
powerBackoff(1),
deviceFault(2),
dcContinuityFault(3),
snrMarginAlarm(4),
loopAttenuationAlarm(5),
loswFailureAlarm(6),
configInitFailure(7),
protocolInitFailure(8),
noNeighborPresent(9),
loopbackActive(10)
}
MAX-ACCESS read-
STATUS
"Contains the current state of the endpoint. This is
bitmap of possible conditions. The various bit
are
Ray & Abbi Standards Track [Page 28]
RFC 3276 HDSL2-SHDSL-LINE MIB May 2002
noDefect There no defects on the line
powerBackoff Indicates enhanced Power Backoff
deviceFault Indicates a vendor-
diagnostic or self-test
has been detected
dcContinuityFault Indicates vendor-
conditions that interfere
span powering such as short
open circuits
snrMarginAlarm Indicates that the SNR
has dropped below the alarm threshold
loopAttenuationAlarm Indicates that the loop
exceeds the alarm threshold
loswFailureAlarm Indicates a forward LOSW alarm
configInitFailure Endpoint failure during
due to paired endpoint not able
support requested configuration
protocolInitFailure Endpoint failure during
due to incompatible protocol used
the paired endpoint
noNeighborPresent Endpoint failure during
due to no activation sequence
from paired endpoint
loopbackActive A loopback is currently active at
Segment Endpoint
This is intended to supplement ifOperStatus. Note that
is a 1-1 relationship between the status bits defined in
object and the notification thresholds defined elsewhere
this MIB."
REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7"
::= { hdsl2ShdslEndpointCurrEntry 3 }
hdsl2ShdslEndpointES OBJECT-
SYNTAX Counter32
UNITS "seconds
MAX-ACCESS read-
STATUS
Ray & Abbi Standards Track [Page 29]
RFC 3276 HDSL2-SHDSL-LINE MIB May 2002
"Count of Errored Seconds (ES) on this endpoint since the
was last restarted."
REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7"
::= { hdsl2ShdslEndpointCurrEntry 4 }
hdsl2ShdslEndpointSES OBJECT-
SYNTAX Counter32
UNITS "seconds
MAX-ACCESS read-
STATUS
"Count of Severely Errored Seconds (SES) on this
since the xU was last restarted."
REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7"
::= { hdsl2ShdslEndpointCurrEntry 5 }
hdsl2ShdslEndpointCRCanomalies OBJECT-
SYNTAX Counter32
UNITS "detected CRC Anomalies
MAX-ACCESS read-
STATUS
"Count of CRC anomalies on this endpoint since the xU
last restarted."
REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7"
::= { hdsl2ShdslEndpointCurrEntry 6 }
hdsl2ShdslEndpointLOSWS OBJECT-
SYNTAX Counter32
UNITS "seconds
MAX-ACCESS read-
STATUS
"Count of Loss of Sync Word (LOSW) Seconds on this
since the xU was last restarted."
REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7"
::= { hdsl2ShdslEndpointCurrEntry 7 }
hdsl2ShdslEndpointUAS OBJECT-
SYNTAX Counter32
UNITS "seconds
MAX-ACCESS read-
STATUS
"Count of Unavailable Seconds (UAS) on this endpoint
the xU was last restarted."
REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7"
Ray & Abbi Standards Track [Page 30]
RFC 3276 HDSL2-SHDSL-LINE MIB May 2002
::= { hdsl2ShdslEndpointCurrEntry 8 }
hdsl2ShdslEndpointCurr15MinTimeElapsed OBJECT-
SYNTAX Hdsl2
UNITS "seconds
MAX-ACCESS read-
STATUS
"Total elapsed seconds in the current 15-minute interval."
::= { hdsl2ShdslEndpointCurrEntry 9 }
hdsl2ShdslEndpointCurr15MinES OBJECT-
SYNTAX
UNITS "seconds
MAX-ACCESS read-
STATUS
"Count of Errored Seconds (ES) in the current 15-
interval."
REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7"
::= { hdsl2ShdslEndpointCurrEntry 10 }
hdsl2ShdslEndpointCurr15MinSES OBJECT-
SYNTAX
UNITS "seconds
MAX-ACCESS read-
STATUS
"Count of Severely Errored Seconds (SES) in the
15-minute interval."
REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7"
::= { hdsl2ShdslEndpointCurrEntry 11 }
hdsl2ShdslEndpointCurr15MinCRCanomalies OBJECT-
SYNTAX
UNITS "detected CRC Anomalies
MAX-ACCESS read-
STATUS
"Count of CRC anomalies in the current 15-minute interval."
REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7"
::= { hdsl2ShdslEndpointCurrEntry 12 }
hdsl2ShdslEndpointCurr15MinLOSWS OBJECT-
SYNTAX
UNITS "seconds
MAX-ACCESS read-
STATUS
Ray & Abbi Standards Track [Page 31]
RFC 3276 HDSL2-SHDSL-LINE MIB May 2002
"Count of Loss of Sync Word (LOSW) Seconds in the
15-minute interval."
REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7"
::= { hdsl2ShdslEndpointCurrEntry 13 }
hdsl2ShdslEndpointCurr15MinUAS OBJECT-
SYNTAX
UNITS "seconds
MAX-ACCESS read-
STATUS
"Count of Unavailable Seconds (UAS) in the current 15-
interval."
REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7"
::= { hdsl2ShdslEndpointCurrEntry 14 }
hdsl2ShdslEndpointCurr1DayTimeElapsed OBJECT-
SYNTAX Hdsl2
UNITS "seconds
MAX-ACCESS read-
STATUS
"Number of seconds that have elapsed since the beginning
the current 1-day interval."
::= { hdsl2ShdslEndpointCurrEntry 15 }
hdsl2ShdslEndpointCurr1DayES OBJECT-
SYNTAX Hdsl2
UNITS "seconds
MAX-ACCESS read-
STATUS
"Count of Errored Seconds (ES) during the current day
measured by hdsl2ShdslEndpointCurr1DayTimeElapsed."
REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7"
::= { hdsl2ShdslEndpointCurrEntry 16 }
hdsl2ShdslEndpointCurr1DaySES OBJECT-
SYNTAX Hdsl2
UNITS "seconds
MAX-ACCESS read-
STATUS
"Count of Severely Errored Seconds (SES) during the
day as measured by hdsl2ShdslEndpointCurr1DayTimeElapsed."
REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7"
::= { hdsl2ShdslEndpointCurrEntry 17 }
Ray & Abbi Standards Track [Page 32]
RFC 3276 HDSL2-SHDSL-LINE MIB May 2002
hdsl2ShdslEndpointCurr1DayCRCanomalies OBJECT-
SYNTAX Hdsl2
UNITS "detected CRC Anomalies
MAX-ACCESS read-
STATUS
"Count of CRC anomalies during the current day as
by hdsl2ShdslEndpointCurr1DayTimeElapsed."
REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7"
::= { hdsl2ShdslEndpointCurrEntry 18 }
hdsl2ShdslEndpointCurr1DayLOSWS OBJECT-
SYNTAX Hdsl2
UNITS "seconds
MAX-ACCESS read-
STATUS
"Count of Loss of Sync Word (LOSW) Seconds during the
day as measured by hdsl2ShdslEndpointCurr1DayTimeElapsed."
REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7"
::= { hdsl2ShdslEndpointCurrEntry 19 }
hdsl2ShdslEndpointCurr1DayUAS OBJECT-
SYNTAX Hdsl2
UNITS "seconds
MAX-ACCESS read-
STATUS
"Count of Unavailable Seconds (UAS) during the current day
measured by hdsl2ShdslEndpointCurr1DayTimeElapsed."
REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7"
::= { hdsl2ShdslEndpointCurrEntry 20 }
-- Segment Endpoint 15-Minute Interval Status/Performance
--
hdsl2Shdsl15MinIntervalTable OBJECT-
SYNTAX SEQUENCE OF Hdsl2Shdsl15
MAX-ACCESS not-
STATUS
"This table provides one row for each HDSL2/SHDSL
performance data collection interval. This table
live data from equipment. As such, it is NOT persistent."
::= { hdsl2ShdslMibObjects 6 }
hdsl2Shdsl15MinIntervalEntry OBJECT-
SYNTAX Hdsl2Shdsl15
Ray & Abbi Standards Track [Page 33]
RFC 3276 HDSL2-SHDSL-LINE MIB May 2002
MAX-ACCESS not-
STATUS
"An entry in the hdsl2Shdsl15MinIntervalTable."
INDEX { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide
hdsl2ShdslEndpointWirePair, hdsl2Shdsl15MinIntervalNumber
::= { hdsl2Shdsl15MinIntervalTable 1 }
Hdsl2Shdsl15MinIntervalEntry ::=
{
hdsl2Shdsl15MinIntervalNumber Unsigned32,
hdsl2Shdsl15MinIntervalES PerfIntervalCount
hdsl2Shdsl15MinIntervalSES PerfIntervalCount
hdsl2Shdsl15MinIntervalCRCanomalies PerfIntervalCount
hdsl2Shdsl15MinIntervalLOSWS PerfIntervalCount
hdsl2Shdsl15MinIntervalUAS
}
hdsl2Shdsl15MinIntervalNumber OBJECT-
SYNTAX Unsigned32(1..96)
MAX-ACCESS not-
STATUS
"Performance Data Interval number. 1 is the the most
previous interval; interval 96 is 24 hours ago.
2..96 are optional."
::= { hdsl2Shdsl15MinIntervalEntry 1 }
hdsl2Shdsl15MinIntervalES OBJECT-
SYNTAX
UNITS "seconds
MAX-ACCESS read-
STATUS
"Count of Errored Seconds (ES) during the interval."
REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7"
::= { hdsl2Shdsl15MinIntervalEntry 2 }
hdsl2Shdsl15MinIntervalSES OBJECT-
SYNTAX
UNITS "seconds
MAX-ACCESS read-
STATUS
"Count of Severely Errored Seconds (SES) during the interval."
REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7"
::= { hdsl2Shdsl15MinIntervalEntry 3 }
Ray & Abbi Standards Track [Page 34]
RFC 3276 HDSL2-SHDSL-LINE MIB May 2002
hdsl2Shdsl15MinIntervalCRCanomalies OBJECT-
SYNTAX
UNITS "detected CRC Anomalies
MAX-ACCESS read-
STATUS
"Count of CRC anomalies during the interval."
REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7"
::= { hdsl2Shdsl15MinIntervalEntry 4 }
hdsl2Shdsl15MinIntervalLOSWS OBJECT-
SYNTAX
UNITS "seconds
MAX-ACCESS read-
STATUS
"Count of Loss of Sync Word (LOSW) Seconds during
interval."
REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7"
::= { hdsl2Shdsl15MinIntervalEntry 5 }
hdsl2Shdsl15MinIntervalUAS OBJECT-
SYNTAX
UNITS "seconds
MAX-ACCESS read-
STATUS
"Count of Unavailable Seconds (UAS) during the interval."
REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7"
::= { hdsl2Shdsl15MinIntervalEntry 6 }
-- Segment Endpoint 1-Day Interval Status/Performance
--
hdsl2Shdsl1DayIntervalTable OBJECT-
SYNTAX SEQUENCE OF Hdsl2Shdsl1
MAX-ACCESS not-
STATUS
"This table provides one row for each HDSL2/SHDSL
performance data collection interval. This table
live data from equipment. As such, it is NOT persistent."
::= { hdsl2ShdslMibObjects 7 }
hdsl2Shdsl1DayIntervalEntry OBJECT-
SYNTAX Hdsl2Shdsl1
MAX-ACCESS not-
STATUS
Ray & Abbi Standards Track [Page 35]
RFC 3276 HDSL2-SHDSL-LINE MIB May 2002
"An entry in the hdsl2Shdsl1DayIntervalTable."
INDEX { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide
hdsl2ShdslEndpointWirePair, hdsl2Shdsl1DayIntervalNumber }
::= { hdsl2Shdsl1DayIntervalTable 1 }
Hdsl2Shdsl1DayIntervalEntry ::=
{
hdsl2Shdsl1DayIntervalNumber Unsigned32,
hdsl2Shdsl1DayIntervalMoniSecs Hdsl2ShdslPerfTimeElapsed
hdsl2Shdsl1DayIntervalES Hdsl2Shdsl1DayIntervalCount
hdsl2Shdsl1DayIntervalSES Hdsl2Shdsl1DayIntervalCount
hdsl2Shdsl1DayIntervalCRCanomalies Hdsl2Shdsl1DayIntervalCount
hdsl2Shdsl1DayIntervalLOSWS Hdsl2Shdsl1DayIntervalCount
hdsl2Shdsl1DayIntervalUAS Hdsl2Shdsl1
}
hdsl2Shdsl1DayIntervalNumber OBJECT-
SYNTAX Unsigned32(1..30)
MAX-ACCESS not-
STATUS
"History Data Interval number. Interval 1 is the the
recent previous day; interval 30 is 30 days ago.
2..30 are optional."
::= { hdsl2Shdsl1DayIntervalEntry 1 }
hdsl2Shdsl1DayIntervalMoniSecs OBJECT-
SYNTAX Hdsl2
UNITS "seconds
MAX-ACCESS read-
STATUS
"The amount of time in the 1-day interval over which
performance monitoring information is actually counted
This value will be the same as the interval duration
in a situation where performance monitoring data could
be collected for any reason."
::= { hdsl2Shdsl1DayIntervalEntry 2 }
hdsl2Shdsl1DayIntervalES OBJECT-
SYNTAX Hdsl2Shdsl1
UNITS "seconds
MAX-ACCESS read-
STATUS
"Count of Errored Seconds (ES) during the 1-day interval
Ray & Abbi Standards Track [Page 36]
RFC 3276 HDSL2-SHDSL-LINE MIB May 2002
measured by hdsl2Shdsl1DayIntervalMoniSecs."
REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7"
::= { hdsl2Shdsl1DayIntervalEntry 3 }
hdsl2Shdsl1DayIntervalSES OBJECT-
SYNTAX Hdsl2Shdsl1
UNITS "seconds
MAX-ACCESS read-
STATUS
"Count of Severely Errored Seconds (SES) during the 1-
interval as measured by hdsl2Shdsl1DayIntervalMoniSecs."
REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7"
::= { hdsl2Shdsl1DayIntervalEntry 4 }
hdsl2Shdsl1DayIntervalCRCanomalies OBJECT-
SYNTAX Hdsl2Shdsl1
UNITS "detected CRC Anomalies
MAX-ACCESS read-
STATUS
"Count of CRC anomalies during the 1-day interval
measured by hdsl2Shdsl1DayIntervalMoniSecs."
REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7"
::= { hdsl2Shdsl1DayIntervalEntry 5 }
hdsl2Shdsl1DayIntervalLOSWS OBJECT-
SYNTAX Hdsl2Shdsl1
UNITS "seconds
MAX-ACCESS read-
STATUS
"Count of Loss of Sync Word (LOSW) Seconds during the 1-
interval as measured by hdsl2Shdsl1DayIntervalMoniSecs."
REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7"
::= { hdsl2Shdsl1DayIntervalEntry 6 }
hdsl2Shdsl1DayIntervalUAS OBJECT-
SYNTAX Hdsl2Shdsl1
UNITS "seconds
MAX-ACCESS read-
STATUS
"Count of Unavailable Seconds (UAS) during the 1-day
as measured by hdsl2Shdsl1DayIntervalMoniSecs."
REFERENCE "HDSL2 Section 7.5.3.7; SHDSL Section 9.5.5.7"
::= { hdsl2Shdsl1DayIntervalEntry 7 }
Ray & Abbi Standards Track [Page 37]
RFC 3276 HDSL2-SHDSL-LINE MIB May 2002
-- Maintenance
--
hdsl2ShdslEndpointMaintTable OBJECT-
SYNTAX SEQUENCE OF Hdsl2
MAX-ACCESS not-
STATUS
"This table supports maintenance operations (eg. loopbacks
to be performed on HDSL2/SHDSL segment endpoints. This
contains live data from equipment. As such, it is
persistent."
::= { hdsl2ShdslMibObjects 8 }
hdsl2ShdslEndpointMaintEntry OBJECT-
SYNTAX Hdsl2
MAX-ACCESS not-
STATUS
"An entry in the hdsl2ShdslEndpointMaintTable. Each
corresponds to a single segment endpoint, and is indexed by
ifIndex of the HDSL2/SHDSL line, the UnitId of the
unit and the side of the unit."
INDEX { ifIndex, hdsl2ShdslInvIndex, hdsl2ShdslEndpointSide }
::= { hdsl2ShdslEndpointMaintTable 1 }
Hdsl2ShdslEndpointMaintEntry ::=
{
hdsl2ShdslMaintLoopbackConfig INTEGER
hdsl2ShdslMaintTipRingReversal INTEGER
hdsl2ShdslMaintPowerBackOff INTEGER
hdsl2ShdslMaintSoftRestart
}
hdsl2ShdslMaintLoopbackConfig OBJECT-
SYNTAX
{
noLoopback(1),
normalLoopback(2),
specialLoopback(3)
}
MAX-ACCESS read-
STATUS
"This object controls configuration of loopbacks for
associated segment endpoint. The status of the
is obtained via the hdsl2ShdslEndpointCurrStatus object."
Ray & Abbi Standards Track [Page 38]
RFC 3276 HDSL2-SHDSL-LINE MIB May 2002
::= { hdsl2ShdslEndpointMaintEntry 1 }
hdsl2ShdslMaintTipRingReversal OBJECT-
SYNTAX
{
normal(1),
reversed(2)
}
MAX-ACCESS read-
STATUS
"This object indicates the state of the tip/ring pair at
associated segment endpoint."
::= { hdsl2ShdslEndpointMaintEntry 2 }
hdsl2ShdslMaintPowerBackOff OBJECT-
SYNTAX
{
default(1),
enhanced(2)
}
MAX-ACCESS read-
STATUS
"This object configures the receiver at the
segment endpoint to operate in default or enhanced
backoff mode."
::= { hdsl2ShdslEndpointMaintEntry 3 }
hdsl2ShdslMaintSoftRestart OBJECT-
SYNTAX
{
ready(1),
restart(2)
}
MAX-ACCESS read-
STATUS
"This object enables the manager to trigger a soft
of the modem at the associated segment endpoint. The
may only set this object to the 'restart(2)' value,
initiates a restart. The agent will perform a restart
approximately 5 seconds. Following the 5 second period,
agent will restore the object to the 'ready(1)' state."
::= { hdsl2ShdslEndpointMaintEntry 4 }
hdsl2ShdslUnitMaintTable OBJECT-
SYNTAX SEQUENCE OF Hdsl2
Ray & Abbi Standards Track [Page 39]
RFC 3276 HDSL2-SHDSL-LINE MIB May 2002
MAX-ACCESS not-
STATUS
"This table supports maintenance operations for units in
HDSL2/SHDSL line. Entries in this table MUST be
in a persistent manner."
::= { hdsl2ShdslMibObjects 9 }
hdsl2ShdslUnitMaintEntry OBJECT-
SYNTAX Hdsl2
MAX-ACCESS not-
STATUS
"An entry in the hdsl2ShdslUnitMaintTable. Each
corresponds to a single unit, and is indexed by the
of the HDSL2/SHDSL line and the UnitId of the
unit."
INDEX { ifIndex, hdsl2ShdslInvIndex }
::= { hdsl2ShdslUnitMaintTable 1 }
Hdsl2ShdslUnitMaintEntry ::=
{
hdsl2ShdslMaintLoopbackTimeout Integer32,
hdsl2ShdslMaintUnitPowerSource
}
hdsl2ShdslMaintLoopbackTimeout OBJECT-
SYNTAX Integer32(0..4095)
UNITS "minutes
MAX-ACCESS read-
STATUS
"This object configures the timeout value for
initiated at segments endpoints contained in the
unit. A value of 0 disables the timeout."
::= { hdsl2ShdslUnitMaintEntry 1 }
hdsl2ShdslMaintUnitPowerSource OBJECT-
SYNTAX
{
local(1),
span(2)
}
MAX-ACCESS read-
STATUS
"This object indicates the DC power source being used by
Ray & Abbi Standards Track [Page 40]
RFC 3276 HDSL2-SHDSL-LINE MIB May 2002
associated unit."
::= { hdsl2ShdslUnitMaintEntry 2 }
-- Span Configuration Profile
--
hdsl2ShdslSpanConfProfileTable OBJECT-
SYNTAX SEQUENCE OF Hdsl2
MAX-ACCESS not-
STATUS
"This table supports definitions of span
profiles for SHDSL lines. HDSL2 does not support
configuration options. This table MUST be
in a persistent manner."
::= { hdsl2ShdslMibObjects 10 }
hdsl2ShdslSpanConfProfileEntry OBJECT-
SYNTAX Hdsl2
MAX-ACCESS not-
STATUS
"Each entry corresponds to a single span
profile. Each profile contains a set of span
parameters. The configuration parameters in a profile
applied to those lines referencing that profile (see
hdsl2ShdslSpanConfProfile object). Profiles may
created/deleted using the row creation/deletion
via hdsl2ShdslSpanConfProfileRowStatus. If an
entry is referenced in hdsl2ShdslSpanConfProfile,
entry MUST remain active until all references are removed."
INDEX { IMPLIED hdsl2ShdslSpanConfProfileName }
::= { hdsl2ShdslSpanConfProfileTable 1 }
Hdsl2ShdslSpanConfProfileEntry ::=
{
hdsl2ShdslSpanConfProfileName SnmpAdminString
hdsl2ShdslSpanConfWireInterface INTEGER
hdsl2ShdslSpanConfMinLineRate Unsigned32,
hdsl2ShdslSpanConfMaxLineRate Unsigned32,
hdsl2ShdslSpanConfPSD INTEGER
hdsl2
Hdsl2ShdslTransmissionModeType
hdsl2ShdslSpanConfRemoteEnabled INTEGER
hdsl2ShdslSpanConfPowerFeeding INTEGER
hdsl2ShdslSpanConfCurrCondTargetMarginDown Integer32,
hdsl2ShdslSpanConfWorstCaseTargetMarginDown Integer32,
Ray & Abbi Standards Track [Page 41]
RFC 3276 HDSL2-SHDSL-LINE MIB May 2002
hdsl2ShdslSpanConfCurrCondTargetMarginUp Integer32,
hdsl2ShdslSpanConfWorstCaseTargetMarginUp Integer32,
hdsl2ShdslSpanConfUsedTargetMargins BITS
hdsl2
Hdsl2ShdslClockReferenceType
hdsl2ShdslSpanConfLineProbeEnable INTEGER
hdsl2ShdslSpanConfProfileRowStatus
}
hdsl2ShdslSpanConfProfileName OBJECT-
SYNTAX SnmpAdminString (SIZE(1..32))
MAX-ACCESS not-
STATUS
"This object is the unique index associated with this profile
Entries in this table are referenced via the
hdsl2ShdslSpanConfProfile in Hdsl2ShdslSpanConfEntry."
::= { hdsl2ShdslSpanConfProfileEntry 1 }
hdsl2ShdslSpanConfWireInterface OBJECT-
SYNTAX
{
twoWire(1),
fourWire(2)
}
MAX-ACCESS read-
STATUS
"This object configures the two-wire or optional four-
operation for SHDSL Lines."
DEFVAL { twoWire }
::= { hdsl2ShdslSpanConfProfileEntry 2 }
hdsl2ShdslSpanConfMinLineRate OBJECT-
SYNTAX Unsigned32(0..4112000)
UNITS "bps
MAX-ACCESS read-
STATUS
"This object configures the minimum transmission rate
the associated SHDSL Line in bits-per-second (bps).
the minimum line rate equals the maximum line
(hdsl2ShdslSpanMaxLineRate), the line rate is
'fixed'. If the minimum line rate is less than the
line rate, the line rate is considered 'rate-adaptive'."
DEFVAL { 1552000 }
::= { hdsl2ShdslSpanConfProfileEntry 3 }
Ray & Abbi Standards Track [Page 42]
RFC 3276 HDSL2-SHDSL-LINE MIB May 2002
hdsl2ShdslSpanConfMaxLineRate OBJECT-
SYNTAX Unsigned32(0..4112000)
UNITS "bps
MAX-ACCESS read-
STATUS
"This object configures the maximum transmission rate
the associated SHDSL Line in bits-per-second (bps).
the minimum line rate equals the maximum line
(hdsl2ShdslSpanMaxLineRate), the line rate is
'fixed'. If the minimum line rate is less than the
line rate, the line rate is considered 'rate-adaptive'."
DEFVAL { 1552000 }
::= { hdsl2ShdslSpanConfProfileEntry 4 }
hdsl2ShdslSpanConfPSD OBJECT-
SYNTAX
{
symmetric(1),
asymmetric(2)
}
MAX-ACCESS read-
STATUS
"This object configures use of symmetric/asymmetric PSD (
Spectral Density) Mask for the associated SHDSL Line.
for symmetric PSD is mandatory for all supported data rates
Support for asymmetric PSD is optional."
DEFVAL { symmetric }
::= { hdsl2ShdslSpanConfProfileEntry 5 }
hdsl2ShdslSpanConfTransmissionMode OBJECT-
SYNTAX Hdsl2
MAX-ACCESS read-
STATUS
"This object specifies the regional setting for the
line."
DEFVAL { { region1 } }
::= { hdsl2ShdslSpanConfProfileEntry 6 }
hdsl2ShdslSpanConfRemoteEnabled OBJECT-
SYNTAX
{
enabled(1),
disabled(2)
}
MAX-ACCESS read-
Ray & Abbi Standards Track [Page 43]
RFC 3276 HDSL2-SHDSL-LINE MIB May 2002
STATUS
"This object enables/disables support for remote
of the units in a SHDSL line from the STU-R via the EOC."
DEFVAL { enabled }
::= { hdsl2ShdslSpanConfProfileEntry 7 }
hdsl2ShdslSpanConfPowerFeeding OBJECT-
SYNTAX
{
noPower(1),
powerFeed(2),
wettingCurrent(3)
}
MAX-ACCESS read-
STATUS
"This object enables/disables support for optional
feeding in a SHDSL line."
DEFVAL { noPower }
::= { hdsl2ShdslSpanConfProfileEntry 8 }
hdsl2ShdslSpanConfCurrCondTargetMarginDown OBJECT-
SYNTAX Integer32(-10..21)
UNITS "dB
MAX-ACCESS read-
STATUS
"This object specifies the downstre