draft-ietf-adslmib-vdsl2-04.txt   draft-ietf-adslmib-vdsl2-05.txt 
Network Working Group M. Morgenstern Network Working Group M. Morgenstern
Internet-Draft ECI Telecom Ltd. Internet-Draft ECI Telecom Ltd.
Intended status: Standards Track S. Baillie Intended status: Standards Track S. Baillie
Expires: August 1, 2008 U. Bonollo Expires: December 3, 2008 U. Bonollo
NEC Australia NEC Australia
January 29, 2008 June 1, 2008
Definitions of Managed Objects for Very High Speed Digital Subscriber Definitions of Managed Objects for Very High Speed Digital Subscriber
Line 2 (VDSL2) Line 2 (VDSL2)
draft-ietf-adslmib-vdsl2-04.txt draft-ietf-adslmib-vdsl2-05.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware 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 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. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 37 skipping to change at page 1, line 37
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on August 1, 2008. This Internet-Draft will expire on December 3, 2008.
Copyright Notice
Copyright (C) The IETF Trust (2008).
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 IfQueueBlockernet use with network management protocols in the Internet community. In
community. In particular, it describes objects used for managing particular, it describes objects used for managing parameters of the
parameters of the "Very High Speed Digital Subscriber Line 2 (VDSL2)" "Very High Speed Digital Subscriber Line 2 (VDSL2)" interface type,
interface type, which are also applicable for managing ADSL, ADSL2, which are also applicable for managing ADSL, ADSL2, and ADSL2+
and ADSL2+ interfaces. interfaces.
Table of Contents Table of Contents
1. The Internet-Standard Management Framework . . . . . . . . . 3 1. The Internet-Standard Management Framework . . . . . . . . . 3
2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Relationship to other MIBs . . . . . . . . . . . . . . . 4 2.1. Relationship to other MIBs . . . . . . . . . . . . . . . 4
2.2. IANA Considerations . . . . . . . . . . . . . . . . . . . 7 2.2. IANA Considerations . . . . . . . . . . . . . . . . . . . 6
2.3. Conventions Used in the MIB Module . . . . . . . . . . . 7 2.3. Conventions Used in the MIB Module . . . . . . . . . . . 6
2.4. Structure . . . . . . . . . . . . . . . . . . . . . . . . 21 2.4. Structure . . . . . . . . . . . . . . . . . . . . . . . . 20
2.5. Persistence . . . . . . . . . . . . . . . . . . . . . . . 24 2.5. Persistence . . . . . . . . . . . . . . . . . . . . . . . 23
2.6. Line Topology . . . . . . . . . . . . . . . . . . . . . . 27 2.6. Line Topology . . . . . . . . . . . . . . . . . . . . . . 26
2.7. Counters, Interval Buckets, and Thresholds . . . . . . . 27 2.7. Counters, Interval Buckets, and Thresholds . . . . . . . 26
2.8. Profiles . . . . . . . . . . . . . . . . . . . . . . . . 29 2.8. Profiles . . . . . . . . . . . . . . . . . . . . . . . . 28
2.9. Notifications . . . . . . . . . . . . . . . . . . . . . . 33 2.9. Notifications . . . . . . . . . . . . . . . . . . . . . . 32
3. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 34 3. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 33
4. Implementation Analysis . . . . . . . . . . . . . . . . . . . 215 4. Implementation Analysis . . . . . . . . . . . . . . . . . . . 214
5. Security Considerations . . . . . . . . . . . . . . . . . . . 216 5. Security Considerations . . . . . . . . . . . . . . . . . . . 215
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 224 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 223
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 225 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 224
7.1. Normative References . . . . . . . . . . . . . . . . . . 225 7.1. Normative References . . . . . . . . . . . . . . . . . . 224
7.2. Informative References . . . . . . . . . . . . . . . . . 226 7.2. Informative References . . . . . . . . . . . . . . . . . 225
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 227 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 226
Intellectual Property and Copyright Statements . . . . . . . . . 229 Intellectual Property and Copyright Statements . . . . . . . . . 227
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 4, line 5 skipping to change at page 4, line 5
This document does not obsolete RFC 2662 [RFC2662], or RFC 4706 This document does not obsolete RFC 2662 [RFC2662], or RFC 4706
[RFC4706] but rather provides a more comprehensive management model [RFC4706] but rather provides a more comprehensive management model
that addresses the VDSL2 technology per G.993.2 ([G.993.2]) as well that addresses the VDSL2 technology per G.993.2 ([G.993.2]) as well
as ADSL, ADSL2 and ADSL2+ technologies. as ADSL, ADSL2 and ADSL2+ technologies.
Additionally, the management framework for VDSL2 lines [TR-129] Additionally, the management framework for VDSL2 lines [TR-129]
specified by the Digital Subscriber Line Forum (DSLF) has been taken specified by the Digital Subscriber Line Forum (DSLF) has been taken
into consideration. That framework is based on ITU-T G.997.1 into consideration. That framework is based on ITU-T G.997.1
standard [G.997.1] and its amendment 1 [G.997.1-Am1]. standard [G.997.1] and its amendment 1 [G.997.1-Am1].
Note that the management model according to this document does not Note that the management model, according to this document, does not
allow managing VDSL technology per G.993.1 ([G.993.1]). VDSL lines allow managing VDSL technology per G.993.1 ([G.993.1]). VDSL lines
MUST be managed by RFC 3728 [RFC3728]. MUST be managed by RFC 3728 [RFC3728].
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
skipping to change at page 5, line 22 skipping to change at page 5, line 22
The MIB branch identified by ifType contains tables appropriate for The MIB branch identified by ifType contains tables appropriate for
the interface types described above. Most such tables extend the the interface types described above. Most such tables extend the
ifEntry table, and are indexed by ifIndex. For interfaces in systems ifEntry table, and are indexed by ifIndex. For interfaces in systems
implementing this MIB module, those table entries indexed by ifIndex implementing this MIB module, those table entries indexed by ifIndex
MUST be persistent. MUST be persistent.
The following attributes are part of the mandatory The following attributes are part of the mandatory
ifGeneralInformationGroup in the Interfaces MIB [RFC2863], and are ifGeneralInformationGroup in the Interfaces MIB [RFC2863], and are
not duplicated in the VDSL2 Line MIB. not duplicated in the VDSL2 Line MIB.
===================================================================
ifIndex Interface index. ifIndex Interface index.
ifDescr See interfaces MIB. ifDescr See interfaces MIB.
ifType vdsl2(xxx) or ifType vdsl2(xxx), channel(70),
channel(70) or interleave(124), or fast(125)
interleave(124) or
fast(125)
ifSpeed Set as appropriate. ifSpeed Set as appropriate.
ifPhysAddress This object MUST have an octet string ifPhysAddress This object MUST have an octet
with zero length. string with zero length.
ifAdminStatus See interfaces MIB. ifAdminStatus See interfaces MIB.
ifOperStatus See interfaces MIB. ifOperStatus See interfaces MIB.
ifLastChange See interfaces MIB. ifLastChange See interfaces MIB.
ifName See interfaces MIB. ifName See interfaces MIB.
ifAlias See interfaces MIB. ifAlias See interfaces MIB.
ifLinkUpDownTrapEnable Default to enabled(1). ifLinkUpDownTrapEnable Default to enabled(1).
ifHighSpeed Set as appropriate. ifHighSpeed Set as appropriate.
ifConnectorPresent Set as appropriate. ifConnectorPresent Set as appropriate.
-------------------------------------------------------------------
===================================================================
Figure 1: Use of ifTable Objects Figure 1: Use of ifTable Objects
2.1.3. Usage of ifStackTable 2.1.3. Usage of ifStackTable
Use of the ifStackTable to associate the entries for physical, fast, Use of the ifStackTable to associate the entries for physical, fast,
interleaved channels, and higher layers (e.g., ATM) is shown below. interleaved channels, and higher layers (e.g., ATM) is shown below.
Use of ifStackTable is necessary, because configuration information Use of ifStackTable is necessary, because configuration information
is stored in profile tables associated with the physical-layer is stored in profile tables associated with the physical-layer
ifEntry only. The channels' ifEntrys need the ifStackTable to find ifEntry only. The channels' ifEntrys need the ifStackTable to find
their associated physical-layer entry and thus their configuration their associated physical-layer entry and thus their configuration
skipping to change at page 7, line 25 skipping to change at page 6, line 36
2.2. IANA Considerations 2.2. IANA Considerations
The VDSL2-LINE-MIB module requires the allocation of a new ifType The VDSL2-LINE-MIB module requires the allocation of a new ifType
value for Very High Speed Digital Subscriber Loop Version 2, to value for Very High Speed Digital Subscriber Loop Version 2, to
distinguish between ADSL lines that are managed with the RFC2662 distinguish between ADSL lines that are managed with the RFC2662
management model, ADSL/ADSL2 and ADSL2+ lines that are managed with management model, ADSL/ADSL2 and ADSL2+ lines that are managed with
the RFC 4706 [RFC4706] management model, and VDSL2/ADSL/ADSL2 and the RFC 4706 [RFC4706] management model, and VDSL2/ADSL/ADSL2 and
ADSL2+ lines that are managed with the model defined in this ADSL2+ lines that are managed with the model defined in this
document. document.
Also the VDSL2-LINE-MIB module requires the allocation of a single Also, the VDSL2-LINE-MIB module requires the allocation of a single
object identifier for its MODULE-IDENTITY. The IANA should allocate object identifier for its MODULE-IDENTITY. The IANA should allocate
this object identifier in the transmission subtree. this object identifier in the transmission subtree.
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
atuc ADSL/ADSL2 or ADSL2+ line termination unit - atuc ADSL/ADSL2 or ADSL2+ line termination unit -
Central office Central office
atur ADSL/ADSL2 or ADSL2+ line termination unit - atur ADSL/ADSL2 or ADSL2+ line termination unit -
Remote site Remote site
CRC Cyclical redundancy check CRC Cyclic Redundancy Check
DELT Dual Ended Loop Test DELT Dual Ended Loop Test
ES Errored second ES Errored Second
FEC Forward Error Correction FEC Forward Error Correction
LOF Loss of framing LOF Loss Of Frame
LOS Loss of signal LOS Loss Of Signal
LOSS LOS Second LOSS LOS Seconds
PTM Packet transfer mode PTM Packet Transfer Mode
SES Severely-errored second SES Severely-Errored Second
SNR Signal-to-noise ratio SNR Signal-to-Noise Ratio
UAS Unavailable second UAS Unavailable Seconds
US0 Upstream band number 0 US0 Upstream band number 0
vtuc VDSL2 line termination unit - Central office vtuc VDSL2 line termination unit - Central office
vtur VDSL2 line termination unit - Remote site vtur VDSL2 line termination unit - Remote site
Xtuc ADSL/ADSL2/ADSL2+ or VDSL2 line termination unit - xTU-C ADSL/ADSL2/ADSL2+ or VDSL2 line termination unit -
Central office Central office
Xtur ADSL/ADSL2/ADSL2+ or VDSL2 line termination unit - xTU-R ADSL/ADSL2/ADSL2+ or VDSL2 line termination unit -
Remote site Remote site
xtu A terminal unit; either an Xtuc or Xtur xTU A line termination unit; either an xTU-C or xTU-R
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), the various transmission modes, power states, section), the various transmission modes, power states,
synchronization states, possible values for various configuration synchronization states, possible values for various configuration
parameters, status parameters, and other parameter types. parameters, status parameters, and other parameter types.
o Xdsl2Unit: o Xdsl2Unit:
Attributes with this syntax uniquely identify each unit in the Attributes with this syntax uniquely identify each unit in the
VDSL2/ADSL/ADSL2/ADSL2+ link. It mirrors the EOC addressing VDSL2/ADSL/ADSL2/ADSL2+ link. This mirrors the EOC addressing
mechanism: mechanism:
xtuc(1) - central office (CO) terminal unit xtuc(1) - Central Office (CO) line termination
xtur(2) - customer premises equipment (CPE) unit.
terminal unit xtur(2) - Remote site line termination unit.
o Xdsl2Direction: o Xdsl2Direction:
Attributes with this syntax uniquely identify a transmission Attributes with this syntax uniquely identify a transmission
direction in a VDSL2/ADSL/ADSL2/ADSL2+ link. The upstream direction in a VDSL2/ADSL/ADSL2/ADSL2+ link. The upstream
direction is a transmission from the remote end (xTU-R) towards direction is a transmission from the remote end (xTU-R) towards
the central office end (xTU-C). The upstream direction is the central office end (xTU-C). The upstream direction is
indicated by upstream(1). The downstream direction is a indicated by upstream(1). The downstream direction is a
transmission from the xTU-C towards the xTU-R. The downstream transmission from the xTU-C towards the xTU-R. The downstream
direction is indicated by downstream(2). direction is indicated by downstream(2).
upstream(1) - Transmission from the xTU-R to the xTU-C. upstream(1) - Transmission from the xTU-R to the xTU-C.
downstream(2) - Transmission from the xTU-C to the xTU-R. downstream(2) - Transmission from the xTU-C to the xTU-R.
o Xdsl2Band: o Xdsl2Band:
Attributes with this syntax uniquely identify a band in a ADSL, Attributes with this syntax uniquely identify a band in an ADSL,
ADSL2, ADSL2+ or VDSL2 link. For a band in the upstream ADSL2, ADSL2+ or VDSL2 link. For a band in the upstream
direction, transmission is from the remote end (xTU-R) towards the direction, transmission is from the remote end (xTU-R) towards the
central office end (xTU-C). For a band in the downstream central office end (xTU-C). For a band in the downstream
direction, transmission is from the xTU-C towards the xTU-R. for direction, transmission is from the xTU-C towards the xTU-R. For
ADSL, ADSL2 and ADSL2+ which use a single band in the upstream ADSL, ADSL2 and ADSL2+ which use a single band in the upstream
direction and a single band in the downstream direction the only direction and a single band in the downstream direction, the only
relevant values are upstream(1) and downstream(2). For VDSL2, relevant values are upstream(1) and downstream(2). For VDSL2,
that uses multiple bands in each transmission direction, a band in which uses multiple bands in each transmission direction, a band
the upstream direction is indicated by any of us0(3), us1(5), in the upstream direction is indicated by any of us0(3), us1(5),
us2(7), us3(9), or us4(11) and a band in the downstream direction us2(7), us3(9), or us4(11) and a band in the downstream direction
is indicated by any of ds1(4), ds2(6), ds3(8), or ds4(10). For is indicated by any of ds1(4), ds2(6), ds3(8), or ds4(10). For
VDSL2 the values upstream(1) and downstream(2) may be used when VDSL2, the values upstream(1) and downstream(2) may be used when
there is a need to refer to the whole upstream or downstream there is a need to refer to the whole upstream or whole downstream
traffic (e.g., report the average signal-to-noise ratio on any traffic (e.g., report the average signal-to-noise ratio on any
transmission direction). transmission direction).
upstream(1) - Transmission from the xTU-R to the xTU-C upstream(1) - Transmission from the xTU-R to the xTU-C
(refers to the single upstream band for (refers to the single upstream band for
ADSL/ADSL2/ADSL2+ ot to the whole ADSL/ADSL2/ADSL2+ or to the whole upstream
upstream traffic for VDSL2). traffic for VDSL2).
downstream(2) - Transmission from the xTU-C to the xTU-R downstream(2) - Transmission from the xTU-C to the xTU-R
(refers to the single downstream band for (refers to the single downstream band for
ADSL/ADSL2/ADSL2+ ot to the whole ADSL/ADSL2/ADSL2+ or to the whole downstream
downstream traffic for VDSL2). traffic for VDSL2).
us0(3) - Upstream band number 0 (US0) (VDSL2). us0(3) - Upstream band number 0 (US0) (VDSL2).
ds1(4) - Downstream band number 1 (DS1) (VDSL2). ds1(4) - Downstream band number 1 (DS1) (VDSL2).
us1(5) - Upstream band number 1 (US1) (VDSL2). us1(5) - Upstream band number 1 (US1) (VDSL2).
ds2(6) - Downstream band number 2 (DS2) (VDSL2). ds2(6) - Downstream band number 2 (DS2) (VDSL2).
us2(7) - Upstream band number 2 (US2) (VDSL2). us2(7) - Upstream band number 2 (US2) (VDSL2).
ds3(8) - Downstream band number 3 (DS3) (VDSL2). ds3(8) - Downstream band number 3 (DS3) (VDSL2).
us3(9) - Upstream band number 3 (US3) (VDSL2). us3(9) - Upstream band number 3 (US3) (VDSL2).
ds4(10) - Downstream band number 4 (DS4) (VDSL2). ds4(10) - Downstream band number 4 (DS4) (VDSL2).
us4(11) - Upstream band number 4 (US4) (VDSL2). us4(11) - Upstream band number 4 (US4) (VDSL2).
o Xdsl2TransmissionModeType: o Xdsl2TransmissionModeType:
Attributes with this syntax reference the list of possible Attributes with this syntax reference the list of possible
transmission modes for VDSL2/ADSL/ADSL2 or ADSL2+. transmission modes for VDSL2/ADSL/ADSL2 or ADSL2+.
Specified as a BITS construct, there are currently a few dozen Specified as a BITS construct, there are currently a few dozen
transmission modes in the list. transmission modes in the list.
o Xdsl2RaMode: o Xdsl2RaMode:
Attributes with this syntax reference if and how Rate-Adaptive Attributes with this syntax describe how Rate-Adaptive
synchronization is being used on the respective VDSL2/ADSL/ADSL2 synchronization is being used on the respective VDSL2/ADSL/ADSL2
or ADSL2+ link: or ADSL2+ link:
manual (1) - No Rate-Adaptation. The initialization process manual (1) - No Rate-Adaptation. The initialization process
attempts to synchronize to a specified rate. attempts to synchronize to a specified rate.
raInit (2) - Rate-Adaptation during initialization process raInit (2) - Rate-Adaptation during initialization process
only, which attempts to synchronize to a rate only, which attempts to synchronize to a rate
between minimum and maximum specified values. between minimum and maximum specified values.
dynamicRa (3) - Dynamic Rate-Adaptation during initialization dynamicRa (3) - Dynamic Rate-Adaptation during initialization
process as well as during SHOWTIME. process as well as during SHOWTIME.
o Xdsl2InitResult: o Xdsl2InitResult:
Attributes with this syntax reference the recent result of a full Attributes with this syntax report the recent result of a full
initialization attempt: initialization attempt:
noFail (0) - Successful initialization noFail (0) - Successful initialization.
configError (1) - Configuration failure configError (1) - Configuration failure.
configNotFeasible (2) - Configuration details not supported configNotFeasible (2) - Configuration details not supported.
commFail (3) - Communication failure commFail (3) - Communication failure.
noPeerAtu (4) - Peer ATU not detected noPeerAtu (4) - Peer ATU not detected.
otherCause (5) - Other initialization failure reason otherCause (5) - Other initialization failure reason.
o Xdsl2OperationModes: o Xdsl2OperationModes:
Attributes with this syntax uniquely identify an xDSL mode, which Attributes with this syntax uniquely identify an xDSL mode, which
is a category associated with each transmission mode defined for is a category associated with each transmission mode defined for
the VDSL2/ADSL/ADSL2 or ADSL2+ link. Part of the line the VDSL2/ADSL/ADSL2 or ADSL2+ link. Part of the line
configuration profile depends on the xDSL Mode: configuration profile depends on the xDSL Mode:
Specified as an enumeration construct, there are currently a few Specified as an enumeration construct, there are currently a few
dozen transmission modes in the list. dozen transmission modes in the list.
o Xdsl2PowerMngState: o Xdsl2PowerMngState:
Attributes with this syntax uniquely identify each power Attributes with this syntax uniquely identify each power
management state defined for the VDSL2/ADSL/ADSL2 or ADSL2+ link. management state defined for the VDSL2/ADSL/ADSL2 or ADSL2+ link.
For VDSL2 links only L0 and L3 states are supported: For VDSL2 links only L0 and L3 states are supported:
l0(1) - L0 - Full power management state l0(1) - L0: Full power management state.
l1(2) - L1 - Low power management state (for G.992.2) l1(2) - L1: Low power management state (for G.992.2).
l2(3) - L2 - Low power management state (for G.992.3, l2(3) - L2: Low power management state (for G.992.3,
G.992.4, and G.992.5) G.992.4, and G.992.5).
l3(4) - L3 - Idle power management state l3(4) - L3: Idle power management state.
o Xdsl2ConfPmsForce: o Xdsl2ConfPmsForce:
Attributes with this syntax are configuration parameters that Attributes with this syntax are configuration parameters that
reference the desired power management state for the VDSL2/ADSL/ reference the desired power management state for the VDSL2/ADSL/
ADSL2 or ADSL2+ link. For VDSL2 links only L0 and L3 states are ADSL2 or ADSL2+ link. For VDSL2, only L0 and L3 states are
supported: supported:
l3toL0 (0) - Perform a transition from L3 to L0 (Full l3toL0 (0) - Perform a transition from L3 to L0 (Full
power management state) power management state).
l0toL2 (2) - Perform a transition from L0 to L2 (Low l0toL2 (2) - Perform a transition from L0 to L2 (Low
power management state) power management state).
l0orL2toL3 (3) - Perform a transition into L3 (Idle power l0orL2toL3 (3) - Perform a transition into L3 (Idle power
management state) management state).
o Xdsl2LinePmMode: o Xdsl2LinePmMode:
Attributes with this syntax are configuration parameters that Attributes with this syntax are configuration parameters that
reference the power modes/states into which the xTU-C or xTU-R may reference the power modes/states into which the xTU-C or xTU-R may
autonomously transit. autonomously transit.
This is a BITS structure that allows control of the following This is a BITS structure that allows control of the following
transit options: transit options:
skipping to change at page 11, line 45 skipping to change at page 10, line 45
to idle (L3) state. to idle (L3) state.
allowTransitionsToLowPower (1)- xTU may autonomously transit allowTransitionsToLowPower (1)- xTU may autonomously transit
to low-power (L1/L2) state. to low-power (L1/L2) state.
o Xdsl2LineLdsf: o Xdsl2LineLdsf:
Attributes with this syntax are configuration parameters that Attributes with this syntax are configuration parameters that
control the Loop Diagnostic mode for the VDSL2/ADSL/ADSL2 or control the Loop Diagnostic mode for the VDSL2/ADSL/ADSL2 or
ADSL2+ link: ADSL2+ link:
inhibit (0) - Inhibit Loop Diagnostic mode inhibit (0) - Inhibit Loop Diagnostic mode.
force (1) - Force/Initiate Loop Diagnostic mode force (1) - Force/Initiate Loop Diagnostic mode.
o Xdsl2LdsfResult: o Xdsl2LdsfResult:
Attributes with this syntax are status parameters that report the Attributes with this syntax are status parameters that report the
result of the recent Loop Diagnostic mode issued for the VDSL2/ result of the recent Loop Diagnostic mode issued for the VDSL2/
ADSL/ADSL2 or ADSL2+ link: ADSL/ADSL2 or ADSL2+ link:
none (1) - The default value, in case LDSF was never none (1) - The default value, in case LDSF was never
requested for the associated line. requested for the associated line.
success (2) - The recent command completed success (2) - The recent command completed successfully.
successfully. inProgress (3) - The Loop Diagnostics process is in progress.
inProgress (3) - The Loop Diagnostics process is in
progress.
unsupported (4) - The NE or the line card doesn't support unsupported (4) - The NE or the line card doesn't support
LDSF. LDSF.
cannotRun (5) - The NE cannot initiate the command, due cannotRun (5) - The NE cannot initiate the command, due to
to a non specific reason. a nonspecific reason.
aborted (6) - The Loop Diagnostics process aborted. aborted (6) - The Loop Diagnostics process aborted.
failed (7) - The Loop Diagnostics process failed. failed (7) - The Loop Diagnostics process failed.
illegalMode (8) - The NE cannot initiate the command, due illegalMode (8) - The NE cannot initiate the command, due
to the specific mode of the relevant to the specific mode of the relevant line.
line.
adminUp (9) - The NE cannot initiate the command because adminUp (9) - The NE cannot initiate the command because
the relevant line is administratively the relevant line is administratively
'Up'. 'Up'.
tableFull (10) - The NE cannot initiate the command, due tableFull (10) - The NE cannot initiate the command, due to
to reaching the maximum number of rows reaching the maximum number of rows in the
in the results table. results table.
noResources (11) - The NE cannot initiate the command, due noResources (11) - The NE cannot initiate the command, due to
to lack of internal memory resources. lack of internal memory resources.
o Xdsl2LineBpsc: o Xdsl2LineBpsc:
Attributes with this syntax are configuration parameters that Attributes with this syntax are configuration parameters that
control the bits per sub-carrier measurement for the VDSL2/ADSL/ control the bits per subcarrier measurement for the VDSL2/ADSL/
ADSL2 or ADSL2+ link: ADSL2 or ADSL2+ link:
idle (1) - Idle state idle (1) - Idle state.
measure (2) - Measure the bits per sub-carrier measure (2) - Measure the bits per subcarrier.
o Xdsl2BpscResult: o Xdsl2BpscResult:
Attributes with this syntax are status parameters that report the Attributes with this syntax are status parameters that report the
result of the recent bits per sub-carrier measurement issued for result of the recent bits per subcarrier measurement issued for
the VDSL2/ADSL/ADSL2 or ADSL2+ link: the VDSL2/ADSL/ADSL2 or ADSL2+ link:
none (1) - The default value, in case a measurement none (1) - The default value, in case a measurement
was never requested for the associated line. was never requested for the associated line.
success (2) - The recent measurement request completed success (2) - The recent measurement request completed
successfully. successfully.
inProgress (3) - The bits per sub-carrier measurement is in inProgress (3) - The bits per subcarrier measurement is in
progress. progress.
unsupported (4) - The bits per sub-carrier request mechanism unsupported (4) - The bits per subcarrier request mechanism
is not supported. is not supported.
failed (5) - The measurement request has failed and no failed (5) - The measurement request has failed and no
results are available. results are available.
noResources (6) - The NE cannot initiate the command, due noResources (6) - The NE cannot initiate the command, due
to lack of internal memory resources. to lack of internal memory resources.
o Xdsl2LineReset: o Xdsl2LineReset:
Attributes with this syntax are configuration parameters that Attributes with this syntax are configuration parameters that
control the line reset function. control the line reset function.
skipping to change at page 13, line 34 skipping to change at page 12, line 21
currently no request for a line reset. currently no request for a line reset.
reset (2) - This state indicates that a line reset reset (2) - This state indicates that a line reset
request has been issued. request has been issued.
o Xdsl2LineProfiles: o Xdsl2LineProfiles:
Attributes with this syntax reference the list of supported, Attributes with this syntax reference the list of supported,
enabled or active ITU-T G.993.2 implementation profiles. This is enabled or active ITU-T G.993.2 implementation profiles. This is
a BITS structure with the following values: a BITS structure with the following values:
profile8a (0) - Profile 8a profile8a (0) - Profile 8a.
profile8b (1) - Profile 8b profile8b (1) - Profile 8b.
profile8c (2) - Profile 8c profile8c (2) - Profile 8c.
profile8d (3) - Profile 8d profile8d (3) - Profile 8d.
profile12a (4) - Profile 12a profile12a (4) - Profile 12a.
profile12b (5) - Profile 12b profile12b (5) - Profile 12b.
profile17a (6) - Profile 17a profile17a (6) - Profile 17a.
profile30a (7) - Profile 30a profile30a (7) - Profile 30a.
o Xdsl2LineClassMask: o Xdsl2LineClassMask:
Attributes with this syntax are configuration parameters that Attributes with this syntax are configuration parameters that
specify the VDSL2 PSD Mask Class for a selected VDSL2 transmission specify the VDSL2 PSD Mask Class for a selected VDSL2 transmission
mode. The following classes are defined: mode. The following classes are defined:
none (1) - VDSL2 PSD Mask Class is unknown/irrelevant. none (1) - VDSL2 PSD Mask Class is unknown/irrelevant.
a998ORb997M1cORc998B (2)- a998ORb997M1cORc998B (2)-
For ITU-T G.993.2 Annex A this is the For ITU-T G.993.2 Annex A this is the
only applicable PSD class. only applicable PSD class.
ITU-T G.993.2 Annex B: 997-M1c-A-7 ITU-T G.993.2 Annex B: 997-M1c-A-7.
ITU-T G.993.2 Annex C: 998-B (POTS-138b, ITU-T G.993.2 Annex C: 998-B (POTS-138b,
POTS-276b, TCM-ISDN) POTS-276b, TCM-ISDN).
b997M1xOR998co (3) - b997M1xOR998co (3) -
ITU-T G.993.2 Annex B: 997-M1x-M-8 or ITU-T G.993.2 Annex B: 997-M1x-M-8 or
997-M1x-M 997-M1x-M.
ITU-T G.993.2 Annex C: 998-CO (POTS-138co, ITU-T G.993.2 Annex C: 998-CO (POTS-138co,
POTS-276co) POTS-276co).
b997M2x (4) - ITU-T G.993.2 Annex B: 997-M2x-M-8, 997-M2x-A, b997M2x (4) - ITU-T G.993.2 Annex B: 997-M2x-M-8, 997-M2x-A,
997-M2x-M, 997E17-M2x-NUS0, 997E30-M2x-NUS0 997-M2x-M, 997E17-M2x-NUS0, 997E30-M2x-NUS0.
b998M1x (5) - ITU-T G.993.2 Annex B: 998-M1x-A, 998-M1x-B, b998M1x (5) - ITU-T G.993.2 Annex B: 998-M1x-A, 998-M1x-B,
998-M1x-NUS0 998-M1x-NUS0.
b998M2x (6) - ITU-T G.993.2 Annex B: 998-M2x-A, 998-M2x-M, b998M2x (6) - ITU-T G.993.2 Annex B: 998-M2x-A, 998-M2x-M,
998-M2x-B, 998-M2x-NUS0, 998E17-M2x-NUS0, 998-M2x-B, 998-M2x-NUS0, 998E17-M2x-NUS0,
998E17-M2x-NUS0-M, 998E30-M2x-NUS0, 998E17-M2x-NUS0-M, 998E30-M2x-NUS0,
998E30-M2x-NUS0-M 998E30-M2x-NUS0-M.
b998AdeM2x(7)- ITU-T G.993.2 Annex B: 998-M2x-A, 998-M2x-M, b998AdeM2x(7)- ITU-T G.993.2 Annex B: 998-M2x-A, 998-M2x-M,
998-M2x-B, 998-M2x-NUS0, 998ADE17-M2x-A, 998-M2x-B, 998-M2x-NUS0, 998ADE17-M2x-A,
998ADE17-M2x-B, 998ADE17-M2x-NUS0-M, 998ADE17-M2x-B, 998ADE17-M2x-NUS0-M,
998ADE30-M2x-NUS0-A, 998ADE30-M2x-NUS0-M 998ADE30-M2x-NUS0-A, 998ADE30-M2x-NUS0-M.
bHpeM1 (8) - ITU-T G.993.2 Annex B: HPE17-M1-NUS0, bHpeM1 (8) - ITU-T G.993.2 Annex B: HPE17-M1-NUS0,
HPE30-M1-NUS0 HPE30-M1-NUS0.
o Xdsl2LineLimitMask: o Xdsl2LineLimitMask:
Attributes with this syntax are configuration parameters that Attributes with this syntax are configuration parameters that
specify the VDSL2 PSD Limit Mask for each PSD Mask Class and specify the VDSL2 PSD Limit Mask for each PSD Mask Class and
implementation profile. The VDSL2 implementation profiles are implementation profile. The VDSL2 implementation profiles are
grouped into 4 classes and each is allocated 16 PSD Limit Mask grouped into 4 classes and each is allocated 16 PSD Limit Mask
values in this textual convention. values in this textual convention.
o Xdsl2LineUs0Disable: o Xdsl2LineUs0Disable:
skipping to change at page 14, line 52 skipping to change at page 13, line 52
Attributes with this syntax are configuration parameters that Attributes with this syntax are configuration parameters that
indicate if US0 (upstream band number 0) is disabled for each indicate if US0 (upstream band number 0) is disabled for each
limit PSD mask. The VDSL2 implementation profiles are grouped limit PSD mask. The VDSL2 implementation profiles are grouped
into 4 classes and each is allocated 16 values in this textual into 4 classes and each is allocated 16 values in this textual
convention. convention.
o Xdsl2LineUs0Mask: o Xdsl2LineUs0Mask:
Attributes with this syntax are configuration parameters for ITU-T Attributes with this syntax are configuration parameters for ITU-T
G.993.2 Annex A transmission mode that specify the US0 PSD masks G.993.2 Annex A transmission mode that specify the US0 PSD masks
to be allowed by the near-end xTU on the line. It is a bit map to be allowed by the near-end xTU on the line. This syntax is a
that supports 20 possible US0 masks. bit map that supports 20 possible US0 masks.
o Xdsl2SymbolProtection: o Xdsl2SymbolProtection:
Attributes with this syntax are configuration parameters that Attributes with this syntax are configuration parameters that
reference the minimum length impulse noise protection (INP) in reference the minimum length impulse noise protection (INP) in
terms of number of symbols (subcarrier spacing of 4.3125 kHz): terms of number of symbols (subcarrier spacing of 4.3125 kHz):
noProtection (1) - INP not required noProtection (1) - INP not required
halfSymbol (2) - INP length = 1/2 symbol halfSymbol (2) - INP length =1/2 symbol.
singleSymbol (3) - INP length = 1 symbol singleSymbol (3) - INP length = 1 symbol.
twoSymbols (4) - INP length = 2 symbols twoSymbols (4) - INP length = 2 symbols.
threeSymbols (5) - INP length = 3 symbols threeSymbols (5) - INP length = 3 symbols.
fourSymbols (6) - INP length = 4 symbols fourSymbols (6) - INP length = 4 symbols.
fiveSymbols (7) - INP length = 5 symbols fiveSymbols (7) - INP length = 5 symbols.
sixSymbols (8) - INP length = 6 symbols sixSymbols (8) - INP length = 6 symbols.
sevenSymbols (9) - INP length = 7 symbols sevenSymbols (9) - INP length = 7 symbols.
eightSymbols (10) - INP length = 8 symbols eightSymbols (10) - INP length = 8 symbols.
nineSymbols (11) - INP length = 9 symbols nineSymbols (11) - INP length = 9 symbols.
tenSymbols (12) - INP length = 10 symbols tenSymbols (12) - INP length = 10 symbols.
elevenSymbols (13) - INP length = 11 symbols elevenSymbols (13) - INP length = 11 symbols.
twelveSymbols (14) - INP length = 12 symbols twelveSymbols (14) - INP length = 12 symbols.
thirteeSymbols (15)- INP length = 13 symbols thirteeSymbols (15) - INP length = 13 symbols.
fourteenSymbols (16)-INP length = 14 symbols fourteenSymbols (16)- INP length = 14 symbols.
fifteenSymbols (17)- INP length = 15 symbols fifteenSymbols (17) - INP length = 15 symbols.
sixteenSymbols (18)- INP length = 16 symbols sixteenSymbols (18) - INP length = 16 symbols.
o Xdsl2SymbolProtection8: o Xdsl2SymbolProtection8:
Attributes with this syntax are configuration parameters that Attributes with this syntax are configuration parameters that
reference the minimum length impulse noise protection (INP) in reference the minimum length impulse noise protection (INP) in
terms of number of symbols (subcarrier spacing of 8.625 kHz): terms of number of symbols (subcarrier spacing of 8.625 kHz):
noProtection (1) - INP not required noProtection (1) - INP not required.
singleSymbol (2) - INP length = 1 symbol singleSymbol (2) - INP length = 1 symbol.
twoSymbols (3) - INP length = 2 symbols twoSymbols (3) - INP length = 2 symbols.
threeSymbols (4) - INP length = 3 symbols threeSymbols (4) - INP length = 3 symbols.
fourSymbols (5) - INP length = 4 symbols fourSymbols (5) - INP length = 4 symbols.
fiveSymbols (6) - INP length = 5 symbols fiveSymbols (6) - INP length = 5 symbols.
sixSymbols (7) - INP length = 6 symbols sixSymbols (7) - INP length = 6 symbols.
sevenSymbols (8) - INP length = 7 symbols sevenSymbols (8) - INP length = 7 symbols.
eightSymbols (9) - INP length = 8 symbols eightSymbols (9) - INP length = 8 symbols.
nineSymbols (10) - INP length = 9 symbols nineSymbols (10) - INP length = 9 symbols.
tenSymbols (11) - INP length = 10 symbols tenSymbols (11) - INP length = 10 symbols.
elevenSymbols (12) - INP length = 11 symbols elevenSymbols (12) - INP length = 11 symbols.
twelveSymbols (13) - INP length = 12 symbols twelveSymbols (13) - INP length = 12 symbols.
thirteeSymbols (14)- INP length = 13 symbols thirteeSymbols (14) - INP length = 13 symbols.
fourteenSymbols (15)-INP length = 14 symbols fourteenSymbols (15)- INP length = 14 symbols.
fifteenSymbols (16)- INP length = 15 symbols fifteenSymbols (16) - INP length = 15 symbols.
sixteenSymbols (17)- INP length = 16 symbols sixteenSymbols (17) - INP length = 16 symbols.
o Xdsl2MaxBer: o Xdsl2MaxBer:
Attributes with this syntax are configuration parameters that Attributes with this syntax are configuration parameters that
reference the maximum Bit Error Rate (BER): reference the maximum Bit Error Rate (BER):
eminus3 (1) - Maximum BER=E^-3 eminus3 (1) - Maximum BER=E^-3.
eminus5 (2) - Maximum BER=E^-5 eminus5 (2) - Maximum BER=E^-5.
eminus7 (3) - Maximum BER=E^-7 eminus7 (3) - Maximum BER=E^-7.
o Xdsl2ChInitPolicy: o Xdsl2ChInitPolicy:
This syntax serves for channel configuration parameters that This syntax serves for channel configuration parameters that
reference the channel initialization policy. reference the channel initialization policy.
policy0 (1) - Policy 0 according to the applicable standard. policy0 (1) - Policy 0 according to the applicable standard.
policy1 (2) - Policy 1 according to the applicable standard. policy1 (2) - Policy 1 according to the applicable standard.
o Xdsl2ScMaskDs: o Xdsl2ScMaskDs:
Attributes with this syntax are configuration parameters that Attributes with this syntax are configuration parameters that
reference the downstream sub-carrier mask. It is a bitmap of up reference the downstream subcarrier mask. This syntax is a bitmap
to 4096 bits. of up to 4096 bits.
o Xdsl2ScMaskUs: o Xdsl2ScMaskUs:
Attributes with this syntax are configuration parameters that Attributes with this syntax are configuration parameters that
reference the upstream sub- carrier mask. It is a bitmap of up to reference the upstream subcarrier mask. This syntax is a bitmap
4096 bits. of up to 4096 bits.
o Xdsl2CarMask: o Xdsl2CarMask:
Attributes with this syntax is a configuration parameter for VDSL2 Attributes with this syntax are configuration parameters for VDSL2
transmission modes that defines an array of up to 32 bands. Each transmission modes that define an array of up to 32 bands. Each
band is represented by a start subcarrier index followed by a stop band is represented by a start subcarrier index followed by a stop
subcarrier index. subcarrier index.
o Xdsl2RfiBands: o Xdsl2RfiBands:
Attributes with this syntax are configuration parameters that Attributes with this syntax are configuration parameters that
define RFI bands. Each RFI band is represented by 4 octets: 16 define radio frequency interference (RFI) bands. Each RFI band is
bit start subcarrier index followed by a 16 bit stop subcarrier represented by 4 octets: 16 bit start subcarrier index followed by
index. a 16 bit stop subcarrier index.
o Xdsl2PsdMaskDs: o Xdsl2PsdMaskDs:
Attributes with this syntax are configuration parameters that Attributes with this syntax are configuration parameters that
reference the downstream power spectrum density (PSD) mask. It is reference the downstream power spectrum density (PSD) mask. This
a structure of up to 32 breakpoints, where each breakpoint syntax is a structure of up to 32 breakpoints, where each
occupies 3 octets. breakpoint occupies 3 octets.
o Xdsl2PsdMaskUs: o Xdsl2PsdMaskUs:
Attributes with this syntax are configuration parameters that Attributes with this syntax are configuration parameters that
reference the upstream power spectrum density (PSD) mask. It is a reference the upstream power spectrum density (PSD) mask. This
structure of up to 16 breakpoints, where each breakpoint occupies syntax is a structure of up to 16 breakpoints, where each
3 octets. breakpoint occupies 3 octets.
o Xdsl2Tssi: o Xdsl2Tssi:
Attributes with this syntax are status parameters that reference Attributes with this syntax are status parameters that reference
the transmit spectrum shaping (TSSi). It is a structure of up to the transmit spectrum shaping (TSSi). This syntax is a structure
32 breakpoints, where each breakpoint occupies 3 octets. of up to 32 breakpoints, where each breakpoint occupies 3 octets.
o Xdsl2LastTransmittedState: o Xdsl2LastTransmittedState:
Attributes with this syntax reference the list of initialization Attributes with this syntax reference the list of initialization
states for VDSL2/ADSL/ADSL2 or ADSL2+ modems. The list of states states for VDSL2/ADSL/ADSL2 or ADSL2+ modems. The list of states
for CO side modems is different from the list of states for the for CO side modems is different from the list of states for the
CPE side modems. CPE side modems. Also, the states for VDSL2 modems are not the
same as those for the ADSL/ADSL2 and ADSL2+ modems.
Specified as an enumeration type, there are currently a few dozen Specified as an enumeration type, there are currently a few dozen
states in the list per each unit side (i.e., CO and CPE). states in the list per each unit side (i.e., CO and CPE).
o Xdsl2LineStatus: o Xdsl2LineStatus:
Attributes with this syntax are status parameters that reflect the Attributes with this syntax are status parameters that reflect the
failure status for a given endpoint of VDSL2/ADSL/ADSL2 or ADSL2+ failure status for a given end point of a VDSL2/ADSL/ADSL2 or
link. ADSL2+ link.
This is a BITS structure that can report the following failures: This is a BITS structure that can report the following failures:
noDefect (0) - This bit position positively reports that noDefect (0) - This bit position positively reports that
no defect or failure exist. no defect or failure exist.
lossOfFraming (1) - Loss of frame synchronization lossOfFraming (1) - Loss of frame synchronization.
lossOfSignal (2) - Loss of signal lossOfSignal (2) - Loss of signal.
lossOfPower (3) - Loss of power. Usually this failure may lossOfPower (3) - Loss of power. Usually this failure may
be reported for CPE units only be reported for CPE units only.
initFailure (4) - Recent initialization process failed. initFailure (4) - Recent initialization process failed.
Never active on xTU-R. Never active on xTU-R.
o Xdsl2ChInpReport: o Xdsl2ChInpReport:
Attributes with this syntax are status parameters that report the Attributes with this syntax are status parameters that report the
method that ACTINP is computed with. method that ACTINP is computed with.
inpComputedUsingFormula (1) - ACTINP computed using inpComputedUsingFormula (1) - ACTINP computed using
INP_no_erasure formula INP_no_erasure formula.
inpEstimatedByXtur (2) - ACTINP estimated by inpEstimatedByXtur (2) - ACTINP estimated by the xTU
the xTU receiver. receiver.
o Xdsl2ChAtmStatus: o Xdsl2ChAtmStatus:
Attributes with this syntax are status parameters that reflect the Attributes with this syntax are status parameters that reflect the
failure status for Transmission Convergence (TC) layer of a given failure status for Transmission Convergence (TC) layer of a given
ATM interface (data path over a VDSL2/ADSL/ADSL2 or ADSL2+ link). ATM interface (data path over a VDSL2/ADSL/ADSL2 or ADSL2+ link).
This is a BITS structure that can report the following failures: This is a BITS structure that can report the following failures:
noDefect (0) - This bit position positively reports noDefect (0) - This bit position positively reports
that no defect or failure exist. that no defect or failure exists.
noCellDelineation (1) - The link was successfully noCellDelineation (1) - The link was successfully initialized
but cell delineation was never acquired
initialized but cell delineation on the associated ATM data path.
was never acquired on the
associated ATM data path.
lossOfCellDelineation (2)- Loss of cell delineation on the lossOfCellDelineation (2)- Loss of cell delineation on the
associated ATM data path associated ATM data path.
o Xdsl2ChPtmStatus: o Xdsl2ChPtmStatus:
Attributes with this syntax are status parameters that reflect the Attributes with this syntax are status parameters that reflect the
failure status for a given PTM interface (packet data path over a failure status for a given PTM interface (i.e., packet data path
VDSL2/ADSL/ADSL2 or ADSL2+ link). over a VDSL2/ADSL/ADSL2 or ADSL2+ link).
This is a BITS structure that can report the following failures: This is a BITS structure that can report the following failures:
noDefect (0) - This bit position positively reports that no noDefect (0) - This bit position positively reports that no
defect or failure exist. defect or failure exists.
outOfSync (1) - Out of synchronization. outOfSync (1) - Out of synchronization.
o Xdsl2UpboKLF: o Xdsl2UpboKLF:
Attributes with this syntax are configuration parameters referring Attributes with this syntax are configuration parameters referring
to whether or not upstream power backoff (UPBO) is enabled and how to whether or not upstream power backoff (UPBO) is enabled and how
electrical length in the context of UPBO is determined. electrical length in the context of UPBO is determined.
This enumeration type can have the following values: This enumeration type can have the following values:
auto(1) - The VTUs autonomously determine the electrical auto(1) - The VTUs autonomously determine the electrical
length. length.
override(2) - Forces the VTU-R to use the electrical length, override(2) - Forces the VTU-R to use the electrical length,
kl0, of the CO-MIB (UPBOKL) to compute the kl0, of the CO-MIB (UPBOKL) to compute the
UPBO. UPBO.
disableUpbo(3) - Disables UPBO. I.e., UPBO is not utilized. disableUpbo(3) - Disables UPBO. I.e., UPBO is not utilized.
o Xdsl2BandUs: o Xdsl2BandUs:
Attributes with this syntax are used as table indexes that refer Attributes with this syntax are used as table indexes that refer
to upstream bands of VDSL2 lines (Excluding US0 band.). to upstream bands of VDSL2 lines (excluding US0 band).
This enumeration type can have the following values: This enumeration type can have the following values:
us1(5) - Upstream band number 1 (US1). us1(5) - Upstream band number 1 (US1).
us2(7) - Upstream band number 2 (US2). us2(7) - Upstream band number 2 (US2).
us3(9) - Upstream band number 3 (US3). us3(9) - Upstream band number 3 (US3).
us4(11) - Upstream band number 4 (US4). us4(11) - Upstream band number 4 (US4).
o Xdsl2LinePsdMaskSelectUs: o Xdsl2LinePsdMaskSelectUs:
Attributes with this syntax are configuration parameters that Attributes with this syntax are configuration parameters that
control the upstream PSD mask selection for annexes J and M of control the upstream PSD mask selection for Annexes J and M of
G.992.3 and G.992.5. G.992.3 and G.992.5.
adlu32Eu32 (1), - ADLU-32 / EU-32 adlu32Eu32 (1), - ADLU-32 / EU-32.
adlu36Eu36 (2), - ADLU-36 / EU-36 adlu36Eu36 (2), - ADLU-36 / EU-36.
adlu40Eu40 (3), - ADLU-40 / EU-40 adlu40Eu40 (3), - ADLU-40 / EU-40.
adlu44Eu44 (4), - ADLU-44 / EU-44 adlu44Eu44 (4), - ADLU-44 / EU-44.
adlu48Eu48 (5), - ADLU-48 / EU-48 adlu48Eu48 (5), - ADLU-48 / EU-48.
adlu52Eu52 (6), - ADLU-52 / EU-52 adlu52Eu52 (6), - ADLU-52 / EU-52.
adlu56Eu56 (7), - ADLU-56 / EU-56 adlu56Eu56 (7), - ADLU-56 / EU-56.
adlu60Eu60 (8), - ADLU-60 / EU-60 adlu60Eu60 (8), - ADLU-60 / EU-60.
adlu64Eu64 (9) - ADLU-64 / EU-61 adlu64Eu64 (9) - ADLU-64 / EU-61.
o Xdsl2LineCeFlag: o Xdsl2LineCeFlag:
Attributes with this syntax are configuration parameters that Attributes with this syntax are configuration parameters that
control the optional cyclic extension values control the optional cyclic extension values.
enableCyclicExtension (0) - Enable use of optional enableCyclicExtension (0) - Enable use of optional
Cyclic Extension values. Cyclic Extension values.
o Xdsl2LineSnrMode o Xdsl2LineSnrMode
Attributes with this syntax are parameters related to the enabling Attributes with this syntax are parameters related to the enabling
and disabling of transmitter referred virtual noise. and disabling of transmitter referred virtual noise.
virtualNoiseDisabled (1) - virtual noise is disabled. virtualNoiseDisabled (1) - virtual noise is disabled.
virtualNoiseEnabled (2) - virtual noise is enabled. virtualNoiseEnabled (2) - virtual noise is enabled.
o Xdsl2LineTxRefVnDs o Xdsl2LineTxRefVnDs
Attributes with this syntax are configuration parameters that Attributes with this syntax are configuration parameters that
define the downstream transmitter referred virtual noise, which is define the downstream transmitter referred virtual noise, which is
specified through a set of breakpoints. Each breakpoint occupies specified through a set of breakpoints. Each breakpoint occupies
3 octets: The first two octets hold the index of the sub-carrier 3 octets: The first two octets hold the index of the subcarrier
associated with the breakpoint. The third octet holds the PSD associated with the breakpoint. The third octet holds the PSD
reduction at the breakpoint from 0 (-140 dBm/Hz) to 200 (-40 reduction at the breakpoint from 0 (-140 dBm/Hz) to 200 (-40
dBm/Hz) using units of 0.5dBm/Hz. A special value of 255 dBm/Hz) using units of 0.5dBm/Hz. A special value of 255
indicates a noise level of 0 W/Hz. indicates a noise level of 0 W/Hz.
o Xdsl2LineTxRefVnUs: o Xdsl2LineTxRefVnUs:
Attributes with this syntax are configuration parameters that Attributes with this syntax are configuration parameters that
define the upstream transmitter referred virtual noise, which is define the upstream transmitter referred virtual noise, which is
specified through a set of breakpoints. Each breakpoint occupies specified through a set of breakpoints. Each breakpoint occupies
3 octets: The first two octets hold the index of the sub-carrier 3 octets: The first two octets hold the index of the subcarrier
associated with the breakpoint. The third octet holds the PSD associated with the breakpoint. The third octet holds the PSD
reduction at the breakpoint from 0 (-140 dBm/Hz) to 200 (-40 reduction at the breakpoint from 0 (-140 dBm/Hz) to 200 (-40
dBm/Hz) using units of 0.5dBm/Hz. A special value of 255 dBm/Hz) using units of 0.5dBm/Hz. A special value of 255
indicates a noise level of 0 W/Hz. indicates a noise level of 0 W/Hz.
o Xdsl2LineForceInp: o Xdsl2LineForceInp:
Attributes with this syntax are configuration parameters that Attributes with this syntax are configuration parameters that
control the framer of a bearer channel. control the framer of a bearer channel.
forceFramerForInp (0) - Select framer setting to satisfy forceFramerForInp (0) - Select framer setting to satisfy
impulse noise protection requirements. impulse noise protection requirements.
o Xdsl2BitsAlloc: o Xdsl2BitsAlloc:
Attributes with this syntax are status parameters that report the Attributes with this syntax are status parameters that report the
bits allocation for each sub-carrier. The bits allocation for a bits allocation for each subcarrier. The bits allocation for a
sub-carrier is in the range 0 to 15. subcarrier is in the range 0 to 15.
o Xdsl2MrefPsdDs: o Xdsl2MrefPsdDs:
Attributes with this syntax are MEDLEY Reference PSD status Attributes with this syntax are MEDLEY Reference PSD status
parameters on downstream direction. It is expressed as the set of parameters in the downstream direction. This is expressed as the
breakpoints exchanged at initialization. The OCTET STRING set of breakpoints exchanged at initialization. The OCTET STRING
contains up to 48 pairs of values in the following structure: contains up to 48 pairs of values in the following structure:
Octets 0&1 -- Index of 1st subcarrier used in the context of a Octets 0-1 -- Index of 1st subcarrier used in the context of a
first breakpoint. Octets 2&3 -- The PSD level for the subcarrier first breakpoint. Octets 2-3 -- The PSD level for the subcarrier
indicated in octets 0&1. Octets 4-7 -- Same, for a 2nd breakpoint indicated in octets 0-1. Octets 4-7 -- Same, for a 2nd breakpoint
Octets 8-11 -- Same, for a 3rd breakpoint And so on until Octets Octets 8-11 -- Same, for a 3rd breakpoint And so on until Octets
188-191 -- Same, for a 48th breakpoint. Each subcarrier index is 188-191 -- Same, for a 48th breakpoint. Each subcarrier index is
an unsigned number in the range 1 and NSds (i.e., highest an unsigned number in the range 1 to NSds (i.e., highest supported
supported sub carrier index on downstream direction). The PSD subcarrier index in the downstream direction). The PSD level is
level is an integer value in the 0 to 4095 range. It is an integer value in the 0 to 4095 range. It is represented in
represented in units of 0.1 dB offset from -140dBm/Hz. units of 0.1 dB offset from -140dBm/Hz.
o Xdsl2MrefPsdUs : o Xdsl2MrefPsdUs :
Attributes with this syntax are MEDLEY Reference PSD status Attributes with this syntax are MEDLEY Reference PSD status
parameters on upstream direction. It is expressed as the set of parameters in the upstream direction. This is expressed as the
breakpoints exchanged at initialization. The OCTET STRING set of breakpoints exchanged at initialization. The OCTET STRING
contains up to 32 pairs of values in the following structure: contains up to 32 pairs of values in the following structure:
Octets 0&1 -- Index of 1st subcarrier used in the context of a Octets 0-1 -- Index of 1st subcarrier used in the context of a
first breakpoint. Octets 2&3 -- The PSD level for the subcarrier first breakpoint. Octets 2-3 -- The PSD level for the subcarrier
indicated in octets 0&1. Octets 4-7 -- Same, for a 2nd breakpoint indicated in octets 0-1. Octets 4-7 -- Same, for a 2nd breakpoint
Octets 8-11 -- Same, for a 3rd breakpoint And so on until Octets Octets 8-11 -- Same, for a 3rd breakpoint And so on until Octets
124-127 -- Same, for a 32nd breakpoint. Each subcarrier index is 124-127 -- Same, for a 32nd breakpoint. Each subcarrier index is
an unsigned number in the range 1 and NSus (i.e., highest an unsigned number in the range 1 to NSus (i.e., highest supported
supported sub carrier index on upstream direction). The PSD level subcarrier index in the upstream direction). The PSD level is an
is an integer value in the 0 to 4095 range. It is represented in integer value in the 0 to 4095 range. It is represented in units
units of 0.1 dB offset from -140dBm/Hz. of 0.1 dB offset from -140dBm/Hz.
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 Line Configuration, Maintenance, and Status Group: o Line Configuration, Maintenance, and Status Group:
This group supports MIB objects for configuring parameters for the This group supports MIB objects for configuring parameters for the
VDSL2/ADSL/ADSL2 or ADSL2+ line and retrieving line status VDSL2/ADSL/ADSL2 or ADSL2+ line and retrieving line status
information. It also supports MIB objects for configuring a information. It also supports MIB objects for configuring a
requested power state or initiating a Dual Ended Line Test (DELT) requested power state or initiating a Dual Ended Loop Test (DELT)
process in the VDSL2/ADSL/ADSL2 or ADSL2+ line. It contains the process in the VDSL2/ADSL/ADSL2 or ADSL2+ line. It contains the
following tables: following tables:
- xdsl2LineTable - xdsl2LineTable
- xdsl2LineSegmentTable - xdsl2LineSegmentTable
- xdsl2LineBandTable - xdsl2LineBandTable
o Channel Status Group: o Channel Status Group:
This group supports MIB objects for retrieving channel layer This group supports MIB objects for retrieving channel layer
status information. It contains the following table: status information. It contains the following table:
- xdsl2ChannelStatusTable - xdsl2ChannelStatusTable
o Subcarrier Status Group: o Subcarrier Status Group:
This group supports MIB objects for retrieving the sub-carrier This group supports MIB objects for retrieving the subcarrier
layer status information, mostly collected by a Dual Ended Line layer status information, mostly collected by a Dual Ended Loop
Test (DELT) process. It contains the following tables: Test (DELT) process. It contains the following tables:
- xdsl2SCStatusTable - xdsl2SCStatusTable
- xdsl2SCStatusBandTable - xdsl2SCStatusBandTable
- xdsl2SCStatusSegmentTable - xdsl2SCStatusSegmentTable
o Unit Inventory Group: o Unit Inventory Group:
This group supports MIB objects for retrieving Unit inventory This group supports MIB objects for retrieving Unit inventory
information about units in VDSL2/ADSL/ADSL2 or ADSL2+ lines via information about units in VDSL2/ADSL/ADSL2 or ADSL2+ lines via
the EOC. It contains the following table: the EOC. It contains the following table:
- xdsl2LineInventoryTable - xdsl2LineInventoryTable
o Current Performance Group: o Current Performance Group:
This group supports MIB objects that provide the current This group supports MIB objects that provide the current
performance information relating to VDSL2/ADSL/ADSL2 and ADSL2+ performance information relating to VDSL2/ADSL/ADSL2 and ADSL2+
line, units and channels level. It contains the following tables: line, unit and channel levels. It contains the following tables:
- xdsl2PMLineCurrTable - xdsl2PMLineCurrTable
- xdsl2PMLineCurrInitTable - xdsl2PMLineInitCurrTable
- xdsl2PMChCurrTable - xdsl2PMChCurrTable
o 15-Minute Interval Performance Group: o 15-Minute Interval Performance Group:
This group supports MIB objects that provide historic performance This group supports MIB objects that provide historic performance
information relating to VDSL2/ADSL/ADSL2 and ADSL2+ line, units information relating to VDSL2/ADSL/ADSL2 and ADSL2+ line, unit and
and channels level in 15- minute intervals. It contains the channel levels in 15- minute intervals. It contains the following
following tables: tables:
- xdsl2PMLineHist15MinTable - xdsl2PMLineHist15MinTable
- xdsl2PMLineInitHist15MinTable - xdsl2PMLineInitHist15MinTable
- xdsl2PMChHist15MinTable - xdsl2PMChHist15MinTable
o 1-Day Interval Performance Group: o 1-Day Interval Performance Group:
This group supports MIB objects that provide historic performance This group supports MIB objects that provide historic performance
information relating to VDSL2/ADSL/ADSL2 and ADSL2+ line, units information relating to VDSL2/ADSL/ADSL2 and ADSL2+ line, unit and
and channels level in 1-day intervals. It contains the following channel levels in 1-day intervals. It contains the following
tables: tables:
- xdsl2PMLineHist1DayTable - xdsl2PMLineHist1DayTable
- xdsl2PMLineInitHist1DayTable - xdsl2PMLineInitHist1DayTable
- xdsl2PMChHist1DTable - xdsl2PMChHist1DTable
o Configuration Template and Profile Group: o Configuration Template and Profile Group:
This group supports MIB objects for defining configuration This group supports MIB objects for defining configuration
profiles for VDSL2/ADSL/ADSL2 and ADSL2+ lines and channels, as profiles for VDSL2/ADSL/ADSL2 and ADSL2+ lines and channels, as
skipping to change at page 23, line 49 skipping to change at page 22, line 49
templates. Each alarm template is comprised of one line alarm templates. Each alarm template is comprised of one line alarm
profile and one or more channel alarm profiles. This group profile and one or more channel alarm profiles. This group
contains the following tables: contains the following tables:
- xdsl2LineAlarmConfTemplateTable - xdsl2LineAlarmConfTemplateTable
- xdsl2LineAlarmConfProfileTable - xdsl2LineAlarmConfProfileTable
- xdsl2ChAlarmConfProfileTable - xdsl2ChAlarmConfProfileTable
o Notifications Group: o Notifications Group:
This group defines the notifications supported for VDLS2/ADSL/ This group defines the notifications supported for VDSL2/ADSL/
ADSL2 and ADSL2+ lines: ADSL2 and ADSL2+ lines:
- xdsl2LinePerfFECSThreshXtuc - xdsl2LinePerfFECSThreshXtuc
- xdsl2LinePerfFECSThreshXtur - xdsl2LinePerfFECSThreshXtur
- xdsl2LinePerfESThreshXtuc - xdsl2LinePerfESThreshXtuc
- xdsl2LinePerfESThreshXtur - xdsl2LinePerfESThreshXtur
- xdsl2LinePerfSESThreshXtuc - xdsl2LinePerfSESThreshXtuc
- xdsl2LinePerfSESThreshXtur - xdsl2LinePerfSESThreshXtur
- xdsl2LinePerfLOSSThreshXtuc - xdsl2LinePerfLOSSThreshXtuc
- xdsl2LinePerfLOSSThreshXtur - xdsl2LinePerfLOSSThreshXtur
skipping to change at page 27, line 12 skipping to change at page 26, line 12
xdsl2LineAlarmConfProfileThresh15MinFailedFullInt xdsl2LineAlarmConfProfileThresh15MinFailedFullInt
xdsl2LineAlarmConfProfileThresh15MinFailedShrtInt xdsl2LineAlarmConfProfileThresh15MinFailedShrtInt
xdsl2LineAlarmConfProfileRowStatus xdsl2LineAlarmConfProfileRowStatus
xdsl2ChAlarmConfProfileName xdsl2ChAlarmConfProfileName
xdsl2ChAlarmConfProfileXtucThresh15MinCodingViolations xdsl2ChAlarmConfProfileXtucThresh15MinCodingViolations
xdsl2ChAlarmConfProfileXtucThresh15MinCorrected xdsl2ChAlarmConfProfileXtucThresh15MinCorrected
xdsl2ChAlarmConfProfileXturThresh15MinCodingViolations xdsl2ChAlarmConfProfileXturThresh15MinCodingViolations
xdsl2ChAlarmConfProfileXturThresh15MinCorrected xdsl2ChAlarmConfProfileXturThresh15MinCorrected
xdsl2ChAlarmConfProfileRowStatus xdsl2ChAlarmConfProfileRowStatus
Note also that the interface indices in this MIB are maintained Note, also, that the interface indices in this MIB are maintained
persistently. View-based Access Control Model (VACM) data relating persistently. View-based Access Control Model (VACM) data relating
to these SHOULD be stored persistently as well [RFC3410]. to these SHOULD be stored persistently as well [RFC3410].
2.6. Line Topology 2.6. Line Topology
A VDSL2/ADSL/ADSL2 and ADSL2+ Line consists of two units: atuc or A VDSL2/ADSL/ADSL2 and ADSL2+ Line consists of two units: atuc or
vtuc (a central office termination unit) and atur or vtur (a remote vtuc (a central office termination unit) and atur or vtur (a remote
termination unit). There are up to 4 channels (maximum number of termination unit). There are up to 4 channels (maximum number of
channels depends on the specific DSL technology), each carrying an channels depends on the specific DSL technology), each carrying an
independent information flow, as shown in the figure below. independent information flow, as shown in the figure below.
<-- Network Side Customer Side --> <-- Network Side Customer Side -->
|<///////////// VDSL2/ADSL/ADSL2/ADSL2+ Span //////////////>| |<///////////// VDSL2/ADSL/ADSL2/ADSL2+ Span //////////////>|
+-------+ +-------+ +-------+ +-------+
+ |<---------------------1------------------->| + | |<---------------------1------------------->| |
+ atuc |<---------------------2------------------->| atur + | atuc |<---------------------2------------------->| atur |
| or <~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~>| or | | or |<~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~>| or |
+ vtuc |<---------------------3------------------->| vtuc + | vtuc |<---------------------3------------------->| vtuc |
+ |<---------------------4------------------->| + | |<---------------------4------------------->| |
+-------+ +-------+ +-------+ +-------+
Key: <////> VDSL2/ADSL/ADSL2/ADSL2+ Span Key: <////> VDSL2/ADSL/ADSL2/ADSL2+ Span
<~~~~> VDSL2/ADSL/ADSL2/ADSL2+ twisted-pair <~~~~> VDSL2/ADSL/ADSL2/ADSL2+ twisted-pair
-1- Channel #1 carried over the line -1- Channel #1 carried over the line
-2- Optional channel #2 carried over the line -2- Optional channel #2 carried over the line
-3- Optional channel #3 carried over the line -3- Optional channel #3 carried over the line
-4- Optional channel #4 carried over the line -4- Optional channel #4 carried over the line
Figure 3: General topology for a VDSL2/ADSL/ADSL2/ADSL2+ Line Figure 3: General topology for a VDSL2/ADSL/ADSL2/ADSL2+ Line
2.7. Counters, Interval Buckets, and Thresholds 2.7. Counters, Interval Buckets, and Thresholds
2.7.1. Counters Managed 2.7.1. Counters Managed
There are various types of counters specified in this MIB. Each There are various types of counters specified in this MIB. Each
counter refers either to the whole VDSL2/ADSL/ADSL2/ADSL2+ line, to counter refers either to the whole VDSL2/ADSL/ADSL2/ADSL2+ line, to
one of the xtu entities, or to one of the bearer channels. one of the xTU entities, or to one of the bearer channels.
o On the whole line level o On the whole line level
For full initializations, failed full initializations, short For full initializations, failed full initializations, short
initializations, and for failed short initializations there are initializations, and for failed short initializations there are
event counters, current 15-minute and 0 to 96 15-minute history event counters, current 15-minute and 0 to 96 15-minute history
bucket(s) of "interval-counters", as well as current and 0 to 30 bucket(s) of "interval-counters", as well as current and 0 to 30
previous 1-day interval-counter(s). Each current 15- minute previous 1-day interval-counter(s). Each current 15- minute
"failed" event bucket has an associated threshold notification. "failed" event bucket has an associated threshold notification.
o On the xtu level o On the xTU level
For the LOS Seconds, ES, SES, FEC seconds, and UAS, there are For the LOS Seconds, ES, SES, FEC seconds, and UAS, there are
event counters, current 15-minute and 0 to 96 15-minute history event counters, current 15-minute and 0 to 96 15-minute history
bucket(s) of "interval-counters", as well as current and 0 to 30 bucket(s) of "interval-counters", as well as current and 0 to 30
previous 1-day interval-counter(s). Each current 15- minute event previous 1-day interval-counter(s). Each current 15- minute event
bucket has an associated threshold notification. bucket has an associated threshold notification.
o On the bearer channel level o On the bearer channel level
For the coding violations (CRC anomalies) and corrected blocks For the coding violations (CRC anomalies) and corrected blocks
(i.e., FEC events) there are event counters, current 15- minute (i.e., FEC events) there are event counters, current 15-minute and
and 0 to 96 15-minute history bucket(s) of "interval- counters", 0 to 96 15-minute history bucket(s) of "interval- counters", as
as well as current and 0 to 30 previous 1-day interval- well as current and 0 to 30 previous 1-day interval- counter(s).
counter(s). Each current 15-minute event bucket has an associated Each current 15-minute event bucket has an associated threshold
threshold notification. notification.
2.7.2. Minimum Number Of Buckets 2.7.2. Minimum Number Of Buckets
Although it is possible to support up to 96 15-minute history buckets Although it is possible to support up to 96 15-minute history buckets
of "interval-counters", systems implementing this MIB module SHOULD of "interval-counters", systems implementing this MIB module SHOULD
practically support at least 16 buckets, as specified in ITU-T practically support at least 16 buckets, as specified in ITU-T
G.997.1, paragraph #7.2.7.9. G.997.1, paragraph #7.2.7.9.
Similarly, it is possible to support up to 30 previous 1-day Similarly, it is possible to support up to 30 previous 1-day
"interval-counters", but systems implementing this MIB module SHOULD "interval-counters", but systems implementing this MIB module SHOULD
support at least 1 previous day buckets. support at least 1 previous day bucket.
2.7.3. Interval Buckets Initialization 2.7.3. Interval Buckets Initialization
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 15-minute interval and any wall clock; between the start of a 15-minute interval and any wall clock;
however, some implementations may align the 15-minute intervals with however, some implementations may align the 15-minute intervals with
quarter hours. Likewise, an implementation may choose to align one quarter hours. Likewise, an implementation may choose to align one
day intervals with the start of a day. day intervals with the start of a day.
Counters are not reset when an xtU is reinitialized, only when the Counters are not reset when an xTU 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.4. Interval Buckets Validity 2.7.4. Interval Buckets Validity
As in RFC 3593 [RFC3593] and RFC 2662 [RFC2662], in case the data for As in RFC 3593 [RFC3593] and RFC 2662 [RFC2662], in case the data for
an interval is suspect or known to be invalid, the agent MUST report an interval is suspect or known to be invalid, the agent MUST report
the interval as invalid. If the current 15-minute event bucket is the interval as invalid. If the current 15-minute event bucket is
determined to be invalid, the element management system SHOULD ignore determined to be invalid, the element management system SHOULD ignore
its content and the agent MUST NOT generate notifications based upon its content and the agent MUST NOT generate notifications based upon
skipping to change at page 29, line 48 skipping to change at page 28, line 48
Valid and report the actual number of seconds the interval lasted. Valid and report the actual number of seconds the interval lasted.
b) If the interval was shortened or extended due to clock b) If the interval was shortened or extended due to clock
corrections, the management system SHOULD report the actual number corrections, the management system SHOULD report the actual number
of seconds the interval lasted, beside reporting that the interval of seconds the interval lasted, beside reporting that the interval
is Valid. is Valid.
2.8. Profiles 2.8. Profiles
As a managed node can handle a large number of xtUs, (e.g., hundreds As a managed node can handle a large number of xtUs, (e.g., hundreds
or perhaps thousands of lines), provisioning every parameter on every or perhaps thousands of lines), provisioning every parameter on every
xtU may become burdensome. Moreover, most lines are provisioned xTU 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 and provisioning process, this MIB module makes use of profiles and
templates. templates.
A configuration profile is a set of parameters that can be shared by A configuration profile is a set of parameters that can be shared by
multiple entities. There are configuration profiles to address the multiple entities. There is a configuration profile to address line-
line level provisioning and another type of profile that addresses level provisioning and another type of profile that addresses
the channel level provisioning parameters. channel-level provisioning parameters.
A configuration template is actually a profile-of- profiles. That A configuration template is actually a profile-of-profiles. That is,
is, a template is comprised of one line configuration profile and one a template is comprised of one line configuration profile and one or
or more channel configuration profiles. A template provides the more channel configuration profiles. A template provides the
complete configuration of a line. The same configuration can be complete configuration of a line. The same configuration can be
shared by multiple lines. shared by multiple lines.
Similarly to the configuration profiles and templates, this MIB Similarly to the configuration profiles and templates, this MIB
module makes use of templates and profiles for specifying the alarm module makes use of templates and profiles for specifying the alarm
thresholds associated with performance parameters. This allows thresholds associated with performance parameters. This allows
provisioning multiple lines with the same criteria for generating provisioning multiple lines with the same criteria for generating
threshold crossing notifications. threshold crossing notifications.
The following paragraphs describe templates and profiles used in this The following paragraphs describe templates and profiles used in this
MIB module MIB module
2.8.1. Configuration Profiles And Templates 2.8.1. Configuration Profiles And Templates
o Line Configuration Profiles - Line configuration profiles contain o Line Configuration Profiles - Line configuration profiles contain
parameters for configuring the low layer of VDLS2/ADSL/ADSL2 and line-level parameters for configuring VDSL2/ADSL/ADSL2 and ADSL2+
ADSL2+ lines. They are defined in the xdsl2LineConfProfTable. lines. They are defined in the xdsl2LineConfProfTable.
The line configuration includes issues such as the specific VDSL2/ The line configuration includes settings such as the specific
ADSL/ADSL2 or ADSL2+ modes to enable on the respective line, power VDSL2/ADSL/ADSL2 or ADSL2+ modes to enable on the respective line,
spectrum parameters, rate adaptation criteria, and SNR margin power spectrum parameters, rate adaptation criteria, and SNR
related parameters. A subset of the line configuration parameters margin-related parameters. A subset of the line configuration
depends upon the specific xDSL Mode allowed (i.e., Does the parameters depends upon the specific xDSL Mode allowed (i.e., Does
profile allow VDSL2, ADSL, ADSL2 and/or ADSL2+?) as well as what the profile allow VDSL2, ADSL, ADSL2 and/or ADSL2+?) as well as
annex/annexes of the standard are allowed. This is the reason a what annex/annexes of the standard are allowed. This is the
line profile MUST include one or more mode-specific extensions. reason a line profile MUST include one or more mode-specific
extensions.
o Channel Configuration Profiles - Channel configuration profiles o Channel Configuration Profiles - Channel configuration profiles
contain parameters for configuring bearer channels over the VDSL2/ contain parameters for configuring bearer channels over the VDSL2/
ADSL/ADSL2 and ADSL2+ lines. They are sometimes considered as the ADSL/ADSL2 and ADSL2+ lines. They are sometimes considered as the
service layer configuration of the VDSL2/ADSL/ADSL2 and ADSL2+ service layer configuration of the VDSL2/ADSL/ADSL2 and ADSL2+
lines. They are defined in the xdsl2ChConfProfTable. lines. They are defined in the xdsl2ChConfProfTable.
The channel configuration includes issues such as the desired The channel configuration includes issues such as the desired
minimum and maximum rate on each traffic flow direction and minimum and maximum rate on each traffic flow direction and
impulse noise protection parameters. impulse noise protection parameters.
o Line Configuration Templates - Line configuration templates allow o Line Configuration Templates - Line configuration templates allow
combining line configuration profiles and channel configuration combining line configuration profiles and channel configuration
profiles to a comprehensive configuration of the VDSL2/ADSL/ADSL2 profiles into a comprehensive configuration of the VDSL2/ADSL/
and ADSL2+ line. They are defined in the ADSL2 and ADSL2+ line. They are defined in the
xdsl2LineConfTemplateTable. xdsl2LineConfTemplateTable.
The line configuration template includes one index (OID) of a line The line configuration template includes one index of a line
configuration profile and one to four indexes of channel configuration profile and one to four indexes of channel
configuration profiles. The template also addresses the issue of configuration profiles. The template also addresses the issue of
distributing the excess available data rate on each traffic flow distributing the excess available data rate on each traffic flow
direction (i.e., the data rate left after each channel is direction (i.e., the data rate left after each channel is
allocated a data rate to satisfy its minimum requested data rate) allocated a data rate to satisfy its minimum requested data rate)
among the various channels. among the various channels.
2.8.2. Alarm Configuration Profiles And Templates 2.8.2. Alarm Configuration Profiles And Templates
o Line Alarm Configuration Profiles - Line level Alarm configuration
o Line Alarm Configuration Profiles - Line-level Alarm configuration
profiles contain the threshold values for Performance Monitoring profiles contain the threshold values for Performance Monitoring
(PM) parameters, counted either on the whole line level or on an (PM) parameters, counted either on the whole line level or on an
xtu level. Thresholds are required only for failures and xTU level. Thresholds are required only for failures and
anomalies. E.g., there are thresholds for failed initializations anomalies. E.g., there are thresholds for failed initializations
and LOS seconds, but not for the aggregate number of full and LOS seconds, but not for the aggregate number of full
initializations. These profiles are defined in the initializations. These profiles are defined in the
xdsl2LineAlarmConfProfileTable. xdsl2LineAlarmConfProfileTable.
o Channel Alarm Configuration Profiles - Channel level Alarm o Channel Alarm Configuration Profiles - Channel-level Alarm
configuration profiles contain the threshold values for PM configuration profiles contain the threshold values for PM
parameters counted on a bearer channel level. Thresholds are parameters counted on a bearer channel level. Thresholds are
defined for two types of anomalies: corrected blocks and coding defined for two types of anomalies: corrected blocks and coding
violations. These profiles are defined in the violations. These profiles are defined in the
xdsl2ChAlarmConfProfileTable. xdsl2ChAlarmConfProfileTable.
o Line Alarm Configuration Templates - Line Alarm configuration o Line Alarm Configuration Templates - Line Alarm configuration
templates allow combining line level alarm configuration profiles templates allow combining line-level alarm configuration profiles
and channel level alarm configuration profiles to a comprehensive and channel-level alarm configuration profiles into a
configuration of the PM thresholds for VDSL2/ADSL/ADSL2 and ADSL2+ comprehensive configuration of the PM thresholds for the VDSL2/
line. They are defined in the xdsl2LineAlarmConfTemplateTable. ADSL/ADSL2 and ADSL2+ line. They are defined in the
xdsl2LineAlarmConfTemplateTable.
The line alarm configuration template includes one index (OID) of The line alarm configuration template includes one index of a
a line level alarm configuration profile and one to four indexes line-level alarm configuration profile and one to four indexes of
of channel level alarm configuration profiles. channel-level alarm configuration profiles.
2.8.3. Managing Profiles And Templates 2.8.3. Managing Profiles And Templates
The index value for each profile and template is a locally-unique, The index value for each profile and template is a locally-unique,
administratively assigned name having the textual convention administratively assigned name having the textual convention
'SnmpAdminString' (RFC 3411 [RFC3411]). '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
configuration template (e.g., xdsl2LConfTempTemplateName = 'silver') configuration template (e.g., xdsl2LConfTempTemplateName = 'silver')
by setting its xdsl2LineCnfgTemplate objects to the value of this by setting its xdsl2LineCnfgTemplate object to the value of this
template. template.
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
Alarm configuration template (e.g., xdsl2LAlarmConfTempTemplateName = Alarm configuration template (e.g., xdsl2LAlarmConfTempTemplateName =
'silver') by setting its xdsl2LineAlarmCnfgTemplate objects to the 'silver') by setting its xdsl2LineAlarmCnfgTemplate object to the
value of this template. value of this template.
Before a template can be deleted or taken out of service it MUST be Before a template can be deleted or taken out of service, it MUST be
first unreferenced from all associated lines. Implementations MAY first unreferenced from all associated lines. Implementations MAY
also reject template modification while it is associated with any also reject template modification while it is associated with any
line. line.
Before a profile can be deleted or taken out of service it MUST be Before a profile can be deleted or taken out of service, it MUST be
first unreferenced from all associated templates. Implementations first unreferenced from all associated templates. Implementations
MAY also reject profile modification while it is referenced by any MAY also reject profile modification while it is referenced by any
template. template.
Implementations MUST provide a default profile whose name is 'DEFVAL' Implementations MUST provide a default profile whose name is 'DEFVAL'
for each profile and template type. The values of the associated for each profile and template type. The values of the associated
parameters will be vendor-specific unless otherwise indicated in this parameters will be vendor-specific unless otherwise indicated in this
document. Before a line's templates have been set, these templates document. Before a line's templates have been set, these templates
will be automatically used by setting xdsl2LineCnfgTemplate and will be automatically used by setting xdsl2LineCnfgTemplate and
xdsl2LineAlarmCnfgTemplate to 'DEFVAL' where appropriate. This xdsl2LineAlarmCnfgTemplate to 'DEFVAL' where appropriate. This
skipping to change at page 33, line 11 skipping to change at page 32, line 17
The number of bearer channels is configured by setting the template The number of bearer channels is configured by setting the template
attributes xdsl2LConfTempChan1ConfProfile, attributes xdsl2LConfTempChan1ConfProfile,
xdsl2LConfTempChan2ConfProfile, xdsl2LConfTempChan3ConfProfile, and xdsl2LConfTempChan2ConfProfile, xdsl2LConfTempChan3ConfProfile, and
xdsl2LConfTempChan4ConfProfile and then assigning that template to a xdsl2LConfTempChan4ConfProfile and then assigning that template to a
DSL line using the xdsl2LineCnfgTemplate attribute. When the number DSL line using the xdsl2LineCnfgTemplate attribute. When the number
of bearer channels for a DSL line changes, the SNMP agent will of bearer channels for a DSL line changes, the SNMP agent will
automatically create or destroy rows in channel-related tables automatically create or destroy rows in channel-related tables
associated with that line. For example, when a DSL line is operating associated with that line. For example, when a DSL line is operating
with one bearer channel, there will be zero rows in channel- related with one bearer channel, there will be zero rows in channel- related
tables for channels two, three, and four. The SNMP agent MUST create tables for channels two, three, and four. The SNMP agent MUST create
and destroy channel related rows as follows : and destroy channel-related rows as follows:
o When the number of bearer channels for a DSL line changes to a o When the number of bearer channels for a DSL line changes to a
higher number, the SNMP agent will automatically create rows in higher number, the SNMP agent will automatically create rows in
the xdsl2ChannelStatusTable, and xdsl2PMChCurrTable tables for the xdsl2ChannelStatusTable, and xdsl2PMChCurrTable tables for
that line. that line.
o When the number of bearer channels for a DSL line changes to a o When the number of bearer channels for a DSL line changes to a
lower number, the SNMP agent will automatically destroy rows in lower number, the SNMP agent will automatically destroy rows in
the xdsl2ChannelStatusTable, the xdsl2ChannelStatusTable,
xdsl2PMChCurrTable,xdsl2PMChHist15MinTable and xdsl2PMChCurrTable,xdsl2PMChHist15MinTable and
xdsl2PMChHist1DTable tables for that line. xdsl2PMChHist1DTable tables for that line.
skipping to change at page 33, line 46 skipping to change at page 32, line 52
The notifications defined in this MIB module are for status change The notifications defined in this MIB module are for status change
(e.g., initialization failure) and for the threshold crossings (e.g., initialization failure) and for the threshold crossings
associated with the following events: Full initialization failures, associated with the following events: Full initialization failures,
short initialization failures, ES, SES, FEC Seconds, LOS Seconds, short initialization failures, ES, SES, FEC Seconds, LOS Seconds,
UAS, FEC Seconds, FEC events, and CRC anomalies. Each threshold has UAS, FEC Seconds, FEC events, and CRC anomalies. Each threshold has
its own enable/threshold value. When that value is 0, the its own enable/threshold value. When that value is 0, the
notification is disabled. notification is disabled.
The xdsl2LineStatusXtur and xdsl2LineStatusXtuc are bitmasks The xdsl2LineStatusXtur and xdsl2LineStatusXtuc are bitmasks
representing all outstanding error conditions associated with the representing all outstanding error conditions associated with the
AtuR and xtuc (respectively). Note that since the xtur status is xTU-R and xTU-C (respectively). Note that since the xTU-R status is
obtained via the EOC, this information may be unavailable in case the obtained via the EOC, this information may be unavailable in case the
xtur is unreachable via EOC during a line error condition. xTU-R is unreachable via EOC during a line error condition.
Therefore, not all conditions may always be included in its current Therefore, not all conditions may always be included in its current
status. Notifications corresponding to the bit fields in those two status. Notifications corresponding to the bit fields in those two
status objects are defined. status objects are defined.
Note that there are other status parameters that refer to the AtuR Note that there are other status parameters that refer to the xTU-R
(e.g., downstream line attenuation). Those parameters also depend on (e.g., downstream line attenuation). Those parameters also depend on
the availability of EOC between the central office xtu and the remote the availability of EOC between the central office xTU and the remote
xtu. xTU.
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 an SHOULD be rate-limited (throttled) such that there is an
implementation-specific gap between the generation of consecutive implementation-specific gap between the generation of consecutive
notifications of the same event. When notifications are rate notifications of the same event. When notifications are rate-
limited, they are dropped and not queued for sending at a future limited, they are dropped and not queued for sending at a future
time. This is intended to be a general rate-limiting statement for time. This is intended to be a general rate-limiting statement for
notifications that otherwise have no explicit rate limiting notifications that otherwise have no explicit rate limiting
assertions in this document. assertions in this document.
Note that the Network Management System, or NMS, may receive a Note that the Network Management System, or NMS, may receive a
linkDown notification, as well, if enabled (via linkDown notification, as well, if enabled (via
ifLinkUpDownTrapEnable [RFC2863]). At the beginning of the next 15 ifLinkUpDownTrapEnable [RFC2863]). At the beginning of the next 15
minute interval, the counter is reset. When the first second goes by minute interval, the counter is reset. When the first second goes by
and the event occurs, the current interval bucket will be 1, which and the event occurs, the current interval bucket will be 1, which
skipping to change at page 34, line 44 skipping to change at page 34, line 4
equals the threshold, and the notification will be sent again. equals the threshold, and the notification will be sent again.
3. Definitions 3. Definitions
VDSL2-LINE-TC-MIB DEFINITIONS ::= BEGIN VDSL2-LINE-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
transmission transmission
FROM SNMPv2-SMI FROM SNMPv2-SMI
TEXTUAL-CONVENTION TEXTUAL-CONVENTION
FROM SNMPv2-TC; FROM SNMPv2-TC;
vdsl2TCMIB MODULE-IDENTITY vdsl2TCMIB MODULE-IDENTITY
LAST-UPDATED "200801290000Z" -- January 29, 2008 LAST-UPDATED "200806010000Z" -- June 1, 2008
ORGANIZATION "ADSLMIB Working Group" ORGANIZATION "ADSLMIB Working Group"
CONTACT-INFO "WG-email: adslmib@ietf.org CONTACT-INFO "WG-email: adslmib@ietf.org
Info: https://www1.ietf.org/mailman/listinfo/adslmib Info: https://www1.ietf.org/mailman/listinfo/adslmib
Chair: Mike Sneed Chair: Mike Sneed
Sand Channel Systems Sand Channel Systems
Postal: P.O. Box 37324 Postal: P.O. Box 37324
Raleigh NC 27627-732 Raleigh NC 27627-732
Email: sneedmike@hotmail.com Email: sneedmike@hotmail.com
Phone: +1 206 600 7022 Phone: +1 206 600 7022
skipping to change at page 36, line 11 skipping to change at page 35, line 16
DESCRIPTION DESCRIPTION
"This MIB Module provides Textual Conventions to be "This MIB Module provides Textual Conventions to be
used by the VDSL2-LINE-MIB module for the purpose of used by the VDSL2-LINE-MIB module for the purpose of
managing VDSL2, ADSL, ADSL2 and ADSL2+ lines. managing VDSL2, ADSL, ADSL2 and ADSL2+ lines.
Copyright (C) The IETF Trust (2008). This version of Copyright (C) The IETF Trust (2008). This version of
this MIB module is part of RFC XXXX: see the RFC itself for this MIB module is part of RFC XXXX: see the RFC itself for
full legal notices." full legal notices."
-- RFC Ed.: replace XXXX with assigned number & remove this note -- RFC Ed.: replace XXXX with assigned number & remove this note
REVISION "200801290000Z" -- January 29, 2008 REVISION "200806010000Z" -- June 1, 2008
DESCRIPTION "Initial version, published as RFC XXXX." DESCRIPTION "Initial version, published as RFC XXXX."
-- RFC Ed.: replace XX with assigned number & remove this note -- RFC Ed.: replace XX with assigned number & remove this note
::= { transmission xxx 2} -- vdsl2MIB 2 ::= { transmission xxx 2} -- vdsl2MIB 2
-- IANA, the xxx here must be the same as the one assigned -- IANA, the xxx here must be the same as the one assigned
-- to the vdsl2MIB below. -- to the vdsl2MIB below.
-- RFC Ed.: Please fill in xxx once assigned by IANA. -- RFC Ed.: Please fill in xxx once assigned by IANA.
------------------------------------------------ ------------------------------------------------
-- Textual Conventions -- -- Textual Conventions --
------------------------------------------------ ------------------------------------------------
Xdsl2Unit ::= TEXTUAL-CONVENTION Xdsl2Unit ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Identifies a transceiver as being either xtuc or "Identifies a transceiver as being either xTU-C or xTU-R.
xtur.
A VDSL2/ADSL/ADSL2 or ADSL2+ line consists of two A VDSL2/ADSL/ADSL2 or ADSL2+ line consists of two
transceivers, an xtuc and an xtur. transceivers, an xTU-C and an xTU-R.
In the case of ADSL/ADSL2 and ADSL2+ those two In the case of ADSL/ADSL2 and ADSL2+ those two transceivers are
transceivers are also called atuc and atur. also called atuc and atur.
In the case of VDSL2 those two transceivers are In the case of VDSL2 those two transceivers are also called
also called vtuc and vtur. vtuc and vtur.
Attributes with this syntax reference the two Specified as an INTEGER, the two values are:
sides of a line. Specified as an INTEGER, the two values
are:
xtuc(1) -- central office transceiver xtuc(1) -- central office transceiver
xtur(2) -- remote site transceiver" xtur(2) -- remote site transceiver"
SYNTAX INTEGER { SYNTAX INTEGER {
xtuc(1), xtuc(1),
xtur(2) xtur(2)
} }
Xdsl2Direction ::= TEXTUAL-CONVENTION Xdsl2Direction ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Identifies the direction of a band "Identifies the direction of a band in a VDSL2/ADSL/ADSL2/
in a VDSL2/ADSL/ADSL2/ADSL2+ link. ADSL2+ link.
The upstream direction is a transmission The upstream direction is a transmission from the remote end
from the remote end (xTU-R) towards the (xTU-R) towards the central office end (xTU-C). The downstream
central office end (xTU-C). The direction is a transmission from the xTU-C towards the xTU-R.
downstream direction is a transmission Specified as an INTEGER, the values are defined as
from the xTU-C towards the xTU-R. follows:"
Specified as an INTEGER,
the values are defined as follows:"
SYNTAX INTEGER { SYNTAX INTEGER {
upstream(1), -- Transmission from the xTU-R to the xTU-C. upstream(1), -- Transmission from the xTU-R to the xTU-C.
downstream(2) -- Transmission from the xTU-C to the xTU-R. downstream(2) -- Transmission from the xTU-C to the xTU-R.
} }
Xdsl2Band ::= TEXTUAL-CONVENTION Xdsl2Band ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Identifies a band in a "Identifies a band in a VDSL2/ADSL/ADSL2/ADSL2+ link.
VDSL2/ADSL/ADSL2/ADSL2+ For a band in the upstream direction, transmission is from the
link. remote end (xTU-R) towards the central office end (xTU-C).
For a band in the upstream direction, For a band in the downstream direction, transmission is from
transmission is from the remote end (xTU-R) the xTU-C towards the xTU-R.
towards the central office end (xTU-C). For ADSL, ADSL2 and ADSL2+, which use a single band in the
For a band in the downstream direction, upstream direction and a single band
transmission is from the xTU-C towards the in the downstream direction,
xTU-R. the only relevant values are upstream(1) and downstream(2).
for ADSL, ADSL2 and ADSL2+ which use a For VDSL2, which uses multiple bands in each transmission
single band in the upstream direction and a direction, a band in the upstream direction is indicated by any
single band in the downstream direction the only of us0(3), us1(5), us2(7), us3(9) or us4(11) and a band in the
relevant values are upstream(1) and downstream(2). downstream direction is indicated by any of ds1(4), ds2(6),
For VDSL2, that uses multiple bands in each ds3(8) or ds4(10).
transmission direction, a band For VDSL2, the values upstream(1) and downstream(2) may be used
in the upstream direction is indicated by any when there is a need to refer to the whole upstream or
of us0(3), us1(5), us2(7), us3(9), or us4(11) and downstream traffic (e.g., report the average signal-to-noise
a band in the downstream direction is indicated ratio on any transmission direction).
by any of ds1(4), ds2(6), ds3(8), or ds4(10). Specified as an INTEGER, the values are defined as
For VDSL2 the values upstream(1) and downstream(2) follows:"
may be used when there is a need to refer to the
whole upstream or downstream traffic (e.g., report
the average signal-to-noise ratio on any transmission
direction).
Specified as an INTEGER,
the values are defined as follows:"
SYNTAX INTEGER { SYNTAX INTEGER {
upstream(1), -- Transmission from the xTU-R to the xTU-C upstream(1), -- Transmission from the xTU-R to the xTU-C
-- (refers to the single upstream band for -- (refers to the single upstream band for
-- ADSL/ADSL2/ADSL2+ ot to the whole -- ADSL/ADSL2/ADSL2+ or to the whole
-- upstream traffic for VDSL2). -- upstream traffic for VDSL2).
downstream(2), -- Transmission from the xTU-C to the xTU-R downstream(2), -- Transmission from the xTU-C to the xTU-R
-- (refers to the single downstream band -- (refers to the single downstream band
-- for ADSL/ADSL2/ADSL2+ ot to the whole -- for ADSL/ADSL2/ADSL2+ or to the whole
-- downstream traffic for VDSL2). -- downstream traffic for VDSL2).
us0(3), -- Upstream band number 0 (US0) (VDSL2). us0(3), -- Upstream band number 0 (US0) (VDSL2).
ds1(4), -- Downstream band number 1 (DS1) (VDSL2). ds1(4), -- Downstream band number 1 (DS1) (VDSL2).
us1(5), -- Upstream band number 1 (US1) (VDSL2). us1(5), -- Upstream band number 1 (US1) (VDSL2).
ds2(6), -- Downstream band number 2 (DS2) (VDSL2). ds2(6), -- Downstream band number 2 (DS2) (VDSL2).
us2(7), -- Upstream band number 2 (US2) (VDSL2). us2(7), -- Upstream band number 2 (US2) (VDSL2).
ds3(8), -- Downstream band number 3 (DS3) (VDSL2). ds3(8), -- Downstream band number 3 (DS3) (VDSL2).
us3(9), -- Upstream band number 3 (US3) (VDSL2). us3(9), -- Upstream band number 3 (US3) (VDSL2).
ds4(10), -- Downstream band number 4 (DS4) (VDSL2). ds4(10), -- Downstream band number 4 (DS4) (VDSL2).
us4(11) -- Upstream band number 4 (US4) (VDSL2). us4(11) -- Upstream band number 4 (US4) (VDSL2).
} }
Xdsl2TransmissionModeType ::= TEXTUAL-CONVENTION Xdsl2TransmissionModeType ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A set of xDSL line transmission modes, with one bit "A set of xDSL line transmission modes, with one bit
per mode. The notes (F) and (L) denote Full-Rate per mode. The notes (F) and (L) denote Full-Rate and
and Lite/splitterless respectively: Lite/splitterless respectively:
Bit 00 : Regional Std. (ANSI T1.413) (F) Bit 00 : Regional Std. (ANSI T1.413) (F)
Bit 01 : Regional Std. (ETSI DTS/TM06006) (F) Bit 01 : Regional Std. (ETSI DTS/TM06006) (F)
Bit 02 : G.992.1 POTS non-overlapped (F) Bit 02 : G.992.1 POTS non-overlapped (F)
Bit 03 : G.992.1 POTS overlapped (F) Bit 03 : G.992.1 POTS overlapped (F)
Bit 04 : G.992.1 ISDN non-overlapped (F) Bit 04 : G.992.1 ISDN non-overlapped (F)
Bit 05 : G.992.1 ISDN overlapped (F) Bit 05 : G.992.1 ISDN overlapped (F)
Bit 06 : G.992.1 TCM-ISDN non-overlapped (F) Bit 06 : G.992.1 TCM-ISDN non-overlapped (F)
Bit 07 : G.992.1 TCM-ISDN overlapped (F) Bit 07 : G.992.1 TCM-ISDN overlapped (F)
Bit 08 : G.992.2 POTS non-overlapped (L) Bit 08 : G.992.2 POTS non-overlapped (L)
Bit 09 : G.992.2 POTS overlapped (L) Bit 09 : G.992.2 POTS overlapped (L)
skipping to change at page 41, line 51 skipping to change at page 40, line 45
attribute which identifies an instance of xDSL Mode-Specific attribute which identifies an instance of xDSL Mode-Specific
PSD Configuration object in the xDSL Line Profile. The PSD Configuration object in the xDSL Line Profile. The
following classes of xDSL operating mode are defined. following classes of xDSL operating mode are defined.
The notes (F) and (L) denote Full-Rate and Lite/splitterless The notes (F) and (L) denote Full-Rate and Lite/splitterless
respectively: respectively:
+-------+--------------------------------------------------+ +-------+--------------------------------------------------+
| Value | xDSL operation mode description | | Value | xDSL operation mode description |
+-------+--------------------------------------------------+ +-------+--------------------------------------------------+
1 - The default/generic PSD configuration. Default 1 - The default/generic PSD configuration. Default
configuration will be used when no other matching configuration will be used when no other matching
mode specific configuration can be found. mode-specific configuration can be found.
2 - Regional Std. (ANSI T1.413) (F) 2 - Regional Std. (ANSI T1.413) (F)
3 - Regional Std. (ETSI DTS/TM06006) (F) 3 - Regional Std. (ETSI DTS/TM06006) (F)
4 - G.992.1 POTS non-overlapped (F) 4 - G.992.1 POTS non-overlapped (F)
5 - G.992.1 POTS overlapped (F) 5 - G.992.1 POTS overlapped (F)
6 - G.992.1 ISDN non-overlapped (F) 6 - G.992.1 ISDN non-overlapped (F)
7 - G.992.1 ISDN overlapped (F) 7 - G.992.1 ISDN overlapped (F)
8 - G.992.1 TCM-ISDN non-overlapped (F) 8 - G.992.1 TCM-ISDN non-overlapped (F)
9 - G.992.1 TCM-ISDN overlapped (F) 9 - G.992.1 TCM-ISDN overlapped (F)
10 - G.992.2 POTS non-overlapped (L) 10 - G.992.2 POTS non-overlapped (L)
11 - G.992.2 POTS overlapped (L) 11 - G.992.2 POTS overlapped (L)
skipping to change at page 44, line 16 skipping to change at page 43, line 11
g9932AnnexB(59), g9932AnnexB(59),
g9932AnnexC(60) g9932AnnexC(60)
} }
Xdsl2PowerMngState ::= TEXTUAL-CONVENTION Xdsl2PowerMngState ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Attributes with this syntax uniquely identify each power "Attributes with this syntax uniquely identify each power
management state defined for the VDSL2/ADSL/ADSL2 or ADSL2+ management state defined for the VDSL2/ADSL/ADSL2 or ADSL2+
link. link.
In VDSL2 only L0 and L3 states are defined. In VDSL2, only L0 and L3 states are defined.
The possible values are: The possible values are:
l0(1) - L0 - Full power management state l0(1) - (L0): Full power management state
l1(2) - L1 - Low power management state (for G.992.2) l1(2) - (L1): Low power management state
l2(3) - L2 - Low power management state (for G.992.3, (for G.992.2)
G.992.4, and G.992.5) l2(3) - (L2): Low power management state
l3(4) - L3 - Idle power management state" (for G.992.3, G.992.4 and G.992.5)
l3(4) - (L3): Idle power management state"
SYNTAX INTEGER { SYNTAX INTEGER {
l0(1), l0(1),
l1(2), l1(2),
l2(3), l2(3),
l3(4) l3(4)
} }
Xdsl2ConfPmsForce ::= TEXTUAL-CONVENTION Xdsl2ConfPmsForce ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Attributes with this syntax are configuration parameters "Attributes with this syntax are configuration parameters
that reference the desired power management state for the that reference the desired power management state for the
VDSL2/ADSL/ADSL2 or ADSL2+ link VDSL2/ADSL/ADSL2 or ADSL2+ link
In VDSL2 only L0 and L3 states are defined: In VDSL2, only L0 and L3 states are defined:
l3toL0 (0) - Perform a transition from L3 to L0 l3toL0 (0) - Perform a transition from L3 to L0
(Full power management state) (Full power management state)
l0toL2 (2) - Perform a transition from L0 to L2 l0toL2 (2) - Perform a transition from L0 to L2
(Low power management state) (Low power management state)
l0orL2toL3 (3) - Perform a transition into L3 (Idle l0orL2toL3 (3) - Perform a transition into L3 (Idle
power management state)" power management state)"
SYNTAX INTEGER { SYNTAX INTEGER {
l3toL0 (0), l3toL0 (0),
l0toL2 (2), l0toL2 (2),
skipping to change at page 46, line 36 skipping to change at page 45, line 31
illegalMode (8), illegalMode (8),
adminUp (9), adminUp (9),
tableFull (10), tableFull (10),
noResources (11) noResources (11)
} }
Xdsl2LineBpsc ::= TEXTUAL-CONVENTION Xdsl2LineBpsc ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Attributes with this syntax are configuration parameters "Attributes with this syntax are configuration parameters
that control the bits per sub-carrier measurement for a that control the bits per subcarrier measurement for a
VDSL2/ADSL/ADSL2 or ADSL2+ link. The possible values are: VDSL2/ADSL/ADSL2 or ADSL2+ link. The possible values are:
idle (1) - Idle state idle (1) - Idle state
measure (2) - Measure the bits per sub-carrier" measure (2) - Measure the bits per subcarrier"
SYNTAX INTEGER { SYNTAX INTEGER {
idle(1), idle(1),
measure(2) measure(2)
} }
Xdsl2BpscResult ::= TEXTUAL-CONVENTION Xdsl2BpscResult ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Possible failure reasons associated with performing "Possible failure reasons associated with performing
a bits per sub-carrier measurement on a DSL line. a bits per subcarrier measurement on a DSL line.
Possible values are: Possible values are:
none (1) - The default value, in case a measurement none (1) - The default value, in case a measurement
was never requested for the associated was never requested for the associated
line. line.
success (2) - The recent measurement request completed success (2) - The recent measurement request completed
successfully. successfully.
inProgress (3) - The bits per sub-carrier measurement is
inProgress (3) - The bits per subcarrier measurement is
in progress. in progress.
unsupported (4) - The bits per sub-carrier request unsupported (4) - The bits per subcarrier request
mechanism is not supported. mechanism is not supported.
failed (5) - The measurement request has failed and no failed (5) - The measurement request has failed and no
results are available. results are available.
noResources (6) - The NE cannot initiate the command, due noResources (6) - The NE cannot initiate the command, due
to lack of internal memory resources." to lack of internal memory resources."
SYNTAX INTEGER { SYNTAX INTEGER {
none(1), none(1),
success(2), success(2),
inProgress(3), inProgress(3),
unsupported(4), unsupported(4),
skipping to change at page 53, line 19 skipping to change at page 52, line 14
reserved8(27), reserved8(27),
reserved9(28), reserved9(28),
reserved10(29), reserved10(29),
reserved11(30), reserved11(30),
reserved12(31) reserved12(31)
} }
Xdsl2SymbolProtection ::= TEXTUAL-CONVENTION Xdsl2SymbolProtection ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" "This type specifies the minimum impulse noise protection
This type specifies the minimum impulse noise protection
for the bearer channel if it is transported over DMT symbols for the bearer channel if it is transported over DMT symbols
with a subcarrier spacing of 4.3125 kHz. with a subcarrier spacing of 4.3125 kHz.
The possible values are: The possible values are:
noProtection (i.e., INP not required), halfSymbol (i.e., INP noProtection (i.e., INP not required), halfSymbol (i.e., INP
length is 1/2 symbol), and 1-16 symbols in steps of 1 length is 1/2 symbol), and 1-16 symbols in steps of 1
symbol" symbol"
SYNTAX INTEGER { SYNTAX INTEGER {
noProtection (1), noProtection (1),
halfSymbol (2), halfSymbol (2),
skipping to change at page 54, line 4 skipping to change at page 52, line 46
twelveSymbols (14), twelveSymbols (14),
thirteeSymbols (15), thirteeSymbols (15),
fourteenSymbols (16), fourteenSymbols (16),
fifteenSymbols (17), fifteenSymbols (17),
sixteenSymbols (18) sixteenSymbols (18)
} }
Xdsl2SymbolProtection8 ::= TEXTUAL-CONVENTION Xdsl2SymbolProtection8 ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" "This type specifies the minimum impulse noise protection
This type specifies the minimum impulse noise protection
for the bearer channel if it is transported over DMT symbols for the bearer channel if it is transported over DMT symbols
with a subcarrier spacing of 8.625 kHz. with a subcarrier spacing of 8.625 kHz.
The possible values are: The possible values are:
noProtection (i.e., INP not required) and 1-16 symbols in noProtection (i.e., INP not required) and 1-16 symbols in
steps of 1 symbol" steps of 1 symbol"
SYNTAX INTEGER { SYNTAX INTEGER {
noProtection (1), noProtection (1),
singleSymbol (2), singleSymbol (2),
twoSymbols (3), twoSymbols (3),
threeSymbols (4), threeSymbols (4),
fourSymbols (5), fourSymbols (5),
fiveSymbols (6), fiveSymbols (6),
sixSymbols (7), sixSymbols (7),
sevenSymbols (8), sevenSymbols (8),
eightSymbols (9), eightSymbols (9),
skipping to change at page 55, line 7 skipping to change at page 53, line 47
eminus7(3) eminus7(3)
} }
Xdsl2ChInitPolicy ::= TEXTUAL-CONVENTION Xdsl2ChInitPolicy ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This syntax serves for channel configuration parameters "This syntax serves for channel configuration parameters
that reference the channel initialization policy. that reference the channel initialization policy.
The possible values are: The possible values are:
policy0 (1) - Policy 0 according to the applicable standard policy0 (1) - Policy 0 according to the applicable standard
policy1 (2) - Policy 1 according to the applicable standard" policy1 (2) - Policy 1 according to the applicable
standard"
SYNTAX INTEGER { SYNTAX INTEGER {
policy0(1), policy0(1),
policy1(2) policy1(2)
} }
Xdsl2ScMaskDs ::= TEXTUAL-CONVENTION Xdsl2ScMaskDs ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each one of the 4096 bits in this OCTET "Each one of the 4096 bits in this OCTET STRING array
STRING array represents the corresponding bin represents the corresponding bin in the downstream direction.
in the downstream direction. A value of one A value of one indicates that the bin is not in use."
indicates that the bin is not in use."
SYNTAX OCTET STRING (SIZE(0..512)) SYNTAX OCTET STRING (SIZE(0..512))
Xdsl2ScMaskUs ::= TEXTUAL-CONVENTION Xdsl2ScMaskUs ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each one of the 4096 bits in this OCTET "Each one of the 4096 bits in this OCTET STRING array
STRING array represents the corresponding bin represents the corresponding bin in the upstream direction.
in the upstream direction. A value of one A value of one indicates that the bin is not in use."
indicates that the bin is not in use."
SYNTAX OCTET STRING (SIZE(0..512)) SYNTAX OCTET STRING (SIZE(0..512))
Xdsl2CarMask ::= TEXTUAL-CONVENTION Xdsl2CarMask ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This type defines an array of bands. "This type defines an array of bands. Each band is
Each band is represented by 4 octets and there represented by 4 octets and there is a maximum of 32 bands
is a maximum of 32 bands allowed. allowed.
Each band consists of a 16 bit start subcarrier Each band consists of a 16 bit start subcarrier index followed by
index followed by a 16 bit stop subcarrier index." a 16 bit stop subcarrier index."
SYNTAX OCTET STRING (SIZE(0..128)) SYNTAX OCTET STRING (SIZE(0..128))
Xdsl2RfiBands ::= TEXTUAL-CONVENTION Xdsl2RfiBands ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This type defines a subset of downstream "This type defines a subset of downstream PSD mask
PSD mask breakpoints used to notch RFI bands. breakpoints used to notch radio frequency interference (RFI)
Each RFI band is represented by 4 octets: 16 bit bands.
start subcarrier index followed by a 16 bit stop Each RFI band is represented by 4 octets: 16 bit start subcarrier
subcarrier index. index followed by a 16 bit stop subcarrier index.
There is a maximum of 16 RFI bands allowed." There is a maximum of 16 RFI bands allowed."
SYNTAX OCTET STRING (SIZE(0..64)) SYNTAX OCTET STRING (SIZE(0..64))
Xdsl2PsdMaskDs ::= TEXTUAL-CONVENTION Xdsl2PsdMaskDs ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is a structure that represents up to "This is a structure that represents up to 32 PSD Mask
32 PSD Mask breakpoints. breakpoints.
Each breakpoint occupies 3 octets: The first Each breakpoint occupies 3 octets: The first
two octets hold the index of the sub-carrier two octets hold the index of the subcarrier associated with the
associated with the breakpoint. The third octet breakpoint. The third octet holds the PSD reduction at the
holds the PSD reduction at the breakpoint from 0 breakpoint from 0 (0dBm/Hz) to 255 (-127.5 dBm/Hz) using units of
(0dBm/Hz) to 255 (-127.5 dBm/Hz) using units of
0.5dBm/Hz." 0.5dBm/Hz."
SYNTAX OCTET STRING (SIZE(0..96)) SYNTAX OCTET STRING (SIZE(0..96))
Xdsl2PsdMaskUs ::= TEXTUAL-CONVENTION Xdsl2PsdMaskUs ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is a structure that represents up to "This is a structure that represents up to 16 PSD Mask
16 PSD Mask breakpoints. breakpoints.
Each breakpoint occupies 3 octets: The first Each breakpoint occupies 3 octets: The first two octets hold the
two octets hold the index of the sub-carrier index of the subcarrier associated with the breakpoint. The
associated with the breakpoint. The third octet third octet holds the PSD reduction at the breakpoint from 0
holds the PSD reduction at the breakpoint from 0
(0dBm/Hz) to 255 (-127.5 dBm/Hz) using units of (0dBm/Hz) to 255 (-127.5 dBm/Hz) using units of
0.5dBm/Hz." 0.5dBm/Hz."
SYNTAX OCTET STRING (SIZE(0..48)) SYNTAX OCTET STRING (SIZE(0..48))
Xdsl2Tssi ::= TEXTUAL-CONVENTION Xdsl2Tssi ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is a structure that represents up to "This is a structure that represents up to 32 transmit
32 transmit spectrum shaping (TSSi) breakpoints. spectrum shaping (TSSi) breakpoints.
Each breakpoint occupies 3 octets: The first Each breakpoint occupies 3 octets: The first two octets hold the
two octets hold the index of the sub-carrier index of the subcarrier associated with the breakpoint. The
associated with the breakpoint. The third octet third octet holds the shaping parameter at the breakpoint. It is
holds the shaping parameter at the breakpoint. It a value from 0 to 126 (units of -0.5dB). The special value 127
is a value from 0 to 126 (units of -0.5dB). The indicates that the subcarrier is not transmitted."
special value 127 indicates that the sub-carrier
is not transmitted."
SYNTAX OCTET STRING (SIZE(0..96)) SYNTAX OCTET STRING (SIZE(0..96))
------*****************************************************
------ The following TC we should add VDSL2 related states
------*****************************************************
Xdsl2LastTransmittedState ::= TEXTUAL-CONVENTION Xdsl2LastTransmittedState ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This parameter represents the last successful "This parameter represents the last successful transmitted
transmitted initialization state in the last full initialization state in the last full initialization performed
initialization performed on the line States are on the line. States are per the specific xDSL technology and
per the specific xDSL technology and are numbered are
from 0 (if G.994.1 is used) or 1 (if G.994.1 is numbered from 0 (if G.994.1 is used) or 1 (if G.994.1 is not
not used) up to Showtime." used) up to Showtime."
SYNTAX INTEGER { SYNTAX INTEGER {
-- ADSL family ATU-C side --
atucG9941(0), atucG9941(0),
atucQuiet1(1), atucQuiet1(1),
atucComb1(2), atucComb1(2),
atucQuiet2(3), atucQuiet2(3),
atucComb2(4), atucComb2(4),
atucIcomb1(5), atucIcomb1(5),
atucLineprob(6), atucLineprob(6),
atucQuiet3(7), atucQuiet3(7),
atucComb3(8), atucComb3(8),
atucIComb2(9), atucIComb2(9),
skipping to change at page 57, line 42 skipping to change at page 56, line 27
atucSegue2(23), atucSegue2(23),
atucMedley(24), atucMedley(24),
atucExchmarker(25), atucExchmarker(25),
atucMsg2(26), atucMsg2(26),
atucReverb6(27), atucReverb6(27),
atucSegue3(28), atucSegue3(28),
atucParams(29), atucParams(29),
atucReverb7(30), atucReverb7(30),
atucSegue4(31), atucSegue4(31),
atucShowtime(32), atucShowtime(32),
-- -- ADSL family ATU-R side --
aturG9941(100), aturG9941(100),
aturQuiet1(101), aturQuiet1(101),
aturComb1(102), aturComb1(102),
aturQuiet2(103), aturQuiet2(103),
aturComb2(104), aturComb2(104),
aturIcomb1(105), aturIcomb1(105),
aturLineprob(106), aturLineprob(106),
aturQuiet3(107), aturQuiet3(107),
aturComb3(108), aturComb3(108),
aturIcomb2(109), aturIcomb2(109),
skipping to change at page 58, line 26 skipping to change at page 57, line 11
aturSegue2(121), aturSegue2(121),
aturMsg1(122), aturMsg1(122),
aturMedley(123), aturMedley(123),
aturExchmarker(124), aturExchmarker(124),
aturMsg2(125), aturMsg2(125),
aturReverb6(126), aturReverb6(126),
aturSegue3(127), aturSegue3(127),
aturParams(128), aturParams(128),
aturReverb7(129), aturReverb7(129),
aturSegue4(130), aturSegue4(130),
aturShowtime(131) aturShowtime(131),
-- VDSL2 VTU-C side --
vtucG9941(200),
vtucQuiet1(201),
vtucChDiscov1(202),
vtucSynchro1(203),
vtucPilot1(204),
vtucQuiet2(205),
vtucPeriodic1(206),
vtucSynchro2(207),
vtucChDiscov2(208),
vtucSynchro3(209),
vtucTraining1(210),
vtucSynchro4(211),
vtucPilot2(212),
vtucTeq(213),
vtucEct(214),
vtucPilot3(215),
vtucPeriodic2(216),
vtucTraining2(217),
vtucSynchro5(218),
vtucMedley(219),
vtucSynchro6(220),
vtucShowtime(221),
-- VDSL2 VTU-R side --
vturG9941(300),
vturQuiet1(301),
vturChDiscov1(302),
vturSynchro1(303),
vturLineprobe(304),
vturPeriodic1(305),
vturSynchro2(306),
vturChDiscov2(307),
vturSynchro3(308),
vturQuiet2(309),
vturTraining1(310),
vturSynchro4(311),
vturTeq(312),
vturQuiet3(313),
vturEct(314),
vturPeriodic2(315),
vturTraining2(316),
vturSynchro5(317),
vturMedley(318),
vturSynchro6(319),
vturShowtime(320)
} }
Xdsl2LineStatus ::= TEXTUAL-CONVENTION Xdsl2LineStatus ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Attributes with this syntax are status parameters "Attributes with this syntax are status parameters
that reflect the failure status for a given endpoint of that reflect the failure status for a given end point of a
VDSL2/ADSL/ADSL2 or ADSL2+ link. VDSL2/ADSL/ADSL2 or ADSL2+ link.
This BITS structure can report the following failures: This BITS structure can report the following failures:
noDefect (0) - This bit position positively reports noDefect (0) - This bit position positively reports
that no defect or failure exist. that no defect or failure exist.
lossOfFraming (1) - Loss of frame synchronization lossOfFraming (1) - Loss of frame synchronization.
lossOfSignal (2) - Loss of signal lossOfSignal (2) - Loss of signal.
lossOfPower (3) - Loss of power. Usually this failure may lossOfPower (3) - Loss of power. Usually this failure may
be reported for CPE units only be reported for CPE units only.
initFailure (4) - Recent initialization process failed. initFailure (4) - Recent initialization process failed.
Never active on xTU-R." Never active on xTU-R."
SYNTAX BITS { SYNTAX BITS {
noDefect(0), noDefect(0),
lossOfFraming(1), lossOfFraming(1),
lossOfSignal(2), lossOfSignal(2),
lossOfPower(3), lossOfPower(3),
initFailure(4) initFailure(4)
} }
Xdsl2ChInpReport ::= TEXTUAL-CONVENTION Xdsl2ChInpReport ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This type is used to indicate the method used to "This type is used to indicate the method used to compute the
compute the ACTINP. If set to inpComputedUsingFormula(1), ACTINP. If set to inpComputedUsingFormula(1), the ACTINP is
the ACTINP is computed according to the INP_no_erasure formula computed according to the INP_no_erasure formula (9.6/G.993.2).
(9.6/G.993.2). If set to inpEstimatedByXtur(2), the ACTINP is If set to inpEstimatedByXtur(2), the ACTINP is the value
the value estimated by the xTU receiver. estimated by the xTU receiver.
inpComputedUsingFormula (1) - ACTINP computed using inpComputedUsingFormula (1) - ACTINP computed using
INP_no_erasure formula INP_no_erasure formula.
inpEstimatedByXtur (2) - ACTINP estimated by inpEstimatedByXtur (2) - ACTINP estimated by
the xTU receiver." the xTU receiver."
SYNTAX INTEGER { SYNTAX INTEGER {
inpComputedUsingFormula(1), inpComputedUsingFormula(1),
inpEstimatedByXtur(2) inpEstimatedByXtur(2)
} }
Xdsl2ChAtmStatus ::= TEXTUAL-CONVENTION Xdsl2ChAtmStatus ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 59, line 37 skipping to change at page 59, line 18
"Attributes with this syntax are status parameters that "Attributes with this syntax are status parameters that
reflect the failure status for Transmission Convergence (TC) reflect the failure status for Transmission Convergence (TC)
layer of a given ATM interface (data path over a VDSL2/ADSL/ layer of a given ATM interface (data path over a VDSL2/ADSL/
ADSL2 or ADSL2+ link). ADSL2 or ADSL2+ link).
This BITS structure can report the following failures: This BITS structure can report the following failures:
noDefect (0) - This bit position positively noDefect (0) - This bit position positively
reports that no defect or failure reports that no defect or failure
exist. exist.
noCellDelineation (1) - The link was successfully noCellDelineation (1) - The link was successfully
initialized but cell delineation initialized but cell delineation
was never acquired on the was never acquired on the
associated ATM data path. associated ATM data path.
lossOfCellDelineation (2)- Loss of cell delineation on the lossOfCellDelineation (2)- Loss of cell delineation on the
associated ATM data path" associated ATM data path."
SYNTAX BITS { SYNTAX BITS {
noDefect(0), noDefect(0),
noCellDelineation(1), noCellDelineation(1),
lossOfCellDelineation(2) lossOfCellDelineation(2)
} }
Xdsl2ChPtmStatus ::= TEXTUAL-CONVENTION Xdsl2ChPtmStatus ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Attributes with this syntax are status parameters that "Attributes with this syntax are status parameters that
skipping to change at page 60, line 24 skipping to change at page 59, line 50
SYNTAX BITS { SYNTAX BITS {
noDefect(0), noDefect(0),
outOfSync(1) outOfSync(1)
} }
Xdsl2UpboKLF ::= TEXTUAL-CONVENTION Xdsl2UpboKLF ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Defines the upstream power backoff force mode (UPBOKLF). "Defines the upstream power backoff force mode (UPBOKLF).
The three possible mode values are: The three possible mode values are:
auto(1) - The VTUS' will autonomously determine the auto(1) - The VTUs will autonomously determine the
electrical length. electrical length.
override(2) - Forces the VTU-R to use the electrical override(2) - Forces the VTU-R to use the electrical
length, kl0, of the CO-MIB (UPBOKL) to length, kl0, of the CO-MIB (UPBOKL) to
compute the UPBO. compute the UPBO.
disableUpbo(3) - Disables UPBO such that UPBO is not disableUpbo(3) - Disables UPBO such that UPBO is not
utilized." utilized."
SYNTAX INTEGER { SYNTAX INTEGER {
auto(1), auto(1),
override(2), override(2),
disableUpbo(3) disableUpbo(3)
skipping to change at page 61, line 9 skipping to change at page 60, line 34
SYNTAX INTEGER { SYNTAX INTEGER {
us1(5), us1(5),
us2(7), us2(7),
us3(9), us3(9),
us4(11) us4(11)
} }
Xdsl2LinePsdMaskSelectUs ::= TEXTUAL-CONVENTION Xdsl2LinePsdMaskSelectUs ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This type is used to define which upstream PSD "This type is used to define which upstream PSD mask is
mask is enabled. This type is used only for Annexes J and enabled. This type is used only for Annexes J and M of ITU-T Recs
M of ITU-T Recs G.992.3 and G.992.5. G.992.3 and G.992.5.
adlu32Eu32 (1), - ADLU-32 / EU-32 adlu32Eu32 (1), - ADLU-32 / EU-32
adlu36Eu36 (2), - ADLU-36 / EU-36 adlu36Eu36 (2), - ADLU-36 / EU-36
adlu40Eu40 (3), - ADLU-40 / EU-40 adlu40Eu40 (3), - ADLU-40 / EU-40
adlu44Eu44 (4), - ADLU-44 / EU-44 adlu44Eu44 (4), - ADLU-44 / EU-44
adlu48Eu48 (5), - ADLU-48 / EU-48 adlu48Eu48 (5), - ADLU-48 / EU-48
adlu52Eu52 (6), - ADLU-52 / EU-52 adlu52Eu52 (6), - ADLU-52 / EU-52
adlu56Eu56 (7), - ADLU-56 / EU-56 adlu56Eu56 (7), - ADLU-56 / EU-56
adlu60Eu60 (8), - ADLU-60 / EU-60 adlu60Eu60 (8), - ADLU-60 / EU-60
adlu64Eu64 (9) - ADLU-64 / EU-61" adlu64Eu64 (9) - ADLU-64 / EU-64"
SYNTAX INTEGER { SYNTAX INTEGER {
adlu32Eu32(1), adlu32Eu32(1),
adlu36Eu36(2), adlu36Eu36(2),
adlu40Eu40(3), adlu40Eu40(3),
adlu44Eu44(4), adlu44Eu44(4),
adlu48Eu48(5), adlu48Eu48(5),
adlu52Eu52(6), adlu52Eu52(6),
adlu56Eu56(7), adlu56Eu56(7),
adlu60Eu60(8), adlu60Eu60(8),
adlu64Eu64(9) adlu64Eu64(9)
skipping to change at page 62, line 18 skipping to change at page 61, line 43
virtualNoiseDisabled (1) - virtual noise is disabled. virtualNoiseDisabled (1) - virtual noise is disabled.
virtualNoiseEnabled (2) - virtual noise is enabled." virtualNoiseEnabled (2) - virtual noise is enabled."
SYNTAX INTEGER { SYNTAX INTEGER {
virtualNoiseDisabled(1), virtualNoiseDisabled(1),
virtualNoiseEnabled(2) virtualNoiseEnabled(2)
} }
Xdsl2LineTxRefVnDs ::= TEXTUAL-CONVENTION Xdsl2LineTxRefVnDs ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is a structure that represents up to "This is a structure that represents up to 32 PSD Mask
32 PSD Mask breakpoints. breakpoints.
Each breakpoint occupies 3 octets: The first Each breakpoint occupies 3 octets: The first two octets hold the
two octets hold the index of the sub-carrier index of the subcarrier associated with the breakpoint. The
associated with the breakpoint. The third octet third octet holds the PSD reduction at the breakpoint from 0
holds the PSD reduction at the breakpoint from 0 (-140 dBm/Hz) to 200 (-40 dBm/Hz) using units of 0.5dBm/Hz.
(-140 dBm/Hz) to 200 (-40 dBm/Hz) using units of A special value of 255 indicates a noise level of 0 W/Hz."
0.5dBm/Hz.
A special value of 255 indicates a noise level of
0 W/Hz."
SYNTAX OCTET STRING (SIZE(0..96)) SYNTAX OCTET STRING (SIZE(0..96))
Xdsl2LineTxRefVnUs ::= TEXTUAL-CONVENTION Xdsl2LineTxRefVnUs ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is a structure that represents up to "This is a structure that represents up to 16 PSD Mask
16 PSD Mask breakpoints. breakpoints.
Each breakpoint occupies 3 octets: The first Each breakpoint occupies 3 octets: The first two octets hold the
two octets hold the index of the sub-carrier index of the subcarrier associated with the breakpoint. The
associated with the breakpoint. The third octet third octet holds the PSD reduction at the breakpoint from 0
holds the PSD reduction at the breakpoint from 0 (-140 dBm/Hz) to 200 (-40 dBm/Hz) using units of 0.5dBm/Hz.
(-140 dBm/Hz) to 200 (-40 dBm/Hz) using units of A special value of 255 indicates a noise level of 0 W/Hz."
0.5dBm/Hz.
A special value of 255 indicates a noise level
of 0 W/Hz."
SYNTAX OCTET STRING (SIZE(0..48)) SYNTAX OCTET STRING (SIZE(0..48))
Xdsl2LineForceInp ::= TEXTUAL-CONVENTION Xdsl2LineForceInp ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" "
This type is being used for specifing that the framer This type is being used for specifing that the framer
settings of all the bearers of a line in any transmission settings of all the bearers of a line in any transmission
direction shall be selected such that the impulse noise direction shall be selected such that the impulse noise
protection computed according to the formula specified protection computed according to the formula specified
in the relevant Recommendation is greater than or equal in the relevant Recommendation is greater than or equal
to the minimal impulse noise protection requirement. to the minimal impulse noise protection requirement.
forceFramerForInp(0) - Select framer setting to satisfy forceFramerForInp(0) - Select framer setting to satisfy
impulse noise protection requirements." impulse noise protection
requirements."
SYNTAX BITS { SYNTAX BITS {
forceFramerForInp(0) forceFramerForInp(0)
} }
Xdsl2BitsAlloc ::= TEXTUAL-CONVENTION Xdsl2BitsAlloc ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" "This type specifies a array of nibbles, where each nibble
This type specifies a array of nibbles, where each nibble indicates the bits allocation for a subcarrier.
indicates the bits allocation for a sub-carrier.
Each nibble has a value in the range 0 to 15 to indicate Each nibble has a value in the range 0 to 15 to indicate
the bits allocation." the bits allocation."
SYNTAX OCTET STRING (SIZE(0..256)) SYNTAX OCTET STRING (SIZE(0..256))
Xdsl2MrefPsdDs ::= TEXTUAL-CONVENTION Xdsl2MrefPsdDs ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" "Attributes with this syntax are MEDLEY Reference PSD status
Attributes with this syntax are parameters in the downstream direction. This is expressed as
MEDLEY Reference PSD status parameters on the set of
downstream direction. It is expressed as breakpoints exchanged at initialization.
the set of breakpoints exchanged at The OCTET STRING contains up to 48 pairs of values in the
initialization. following structure:
The OCTET STRING contains up to 48 pairs
of values in the following structure: Octets 0-1 -- Index of 1st subcarrier used in the
Octets 0&1 -- Index of 1st subcarrier used context of a first breakpoint.
in the context of a first breakpoint. Octets 2-3 -- The PSD level for the subcarrier indicated
Octets 2&3 -- The PSD level for the in octets 0-1.
subcarrier indicated in octets 0&1.
Octets 4-7 -- Same, for a 2nd breakpoint Octets 4-7 -- Same, for a 2nd breakpoint
Octets 8-11 -- Same, for a 3rd breakpoint Octets 8-11 -- Same, for a 3rd breakpoint
And so on until And so on until
Octets 188-191 -- Same, for a 48th breakpoint. Octets 188-191 -- Same, for a 48th breakpoint.
Each subcarrier index is an unsigned number Each subcarrier index is an unsigned number in the range 1 to
in the range 1 and NSds (i.e., highest NSds (i.e., highest supported subcarrier index in the downstream
supported sub carrier index on downstream
direction). direction).
The PSD level is an integer value in the 0 to The PSD level is an integer value in the 0 to 4095 range. It is
4095 range. It is represented in units of 0.1 represented in units of 0.1 dB offset from -140dBm/Hz."
dB offset from -140dBm/Hz."
SYNTAX OCTET STRING (SIZE(0..192)) SYNTAX OCTET STRING (SIZE(0..192))
Xdsl2MrefPsdUs ::= TEXTUAL-CONVENTION Xdsl2MrefPsdUs ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" "Attributes with this syntax are MEDLEY Reference PSD status
Attributes with this syntax are parameters in the upstream direction. This is expressed
MEDLEY Reference PSD status parameters on as the set of
upstream direction. It is expressed as breakpoints exchanged at initialization.
the set of breakpoints exchanged at The OCTET STRING contains up to 32 pairs of values in the
initialization. following structure:
The OCTET STRING contains up to 32 pairs Octets 0-1 -- Index of 1st subcarrier used in the
of values in the following structure: context of a first breakpoint.
Octets 0&1 -- Index of 1st subcarrier used Octets 2-3 -- The PSD level for the subcarrier indicated
in the context of a first breakpoint. in octets 0-1.
Octets 2&3 -- The PSD level for the
subcarrier indicated in octets 0&1.
Octets 4-7 -- Same, for a 2nd breakpoint Octets 4-7 -- Same, for a 2nd breakpoint
Octets 8-11 -- Same, for a 3rd breakpoint Octets 8-11 -- Same, for a 3rd breakpoint
And so on until And so on until
Octets 124-127 -- Same, for a 32nd breakpoint. Octets 124-127 -- Same, for a 32nd breakpoint.
Each subcarrier index is an unsigned number Each subcarrier index is an unsigned number in the range 1 to
in the range 1 and NSus (i.e., highest NSus (i.e., highest supported subcarrier index in the upstream
supported sub carrier index on upstream
direction). direction).
The PSD level is an integer value in the 0 to The PSD level is an integer value in the 0 to 4095 range. It is
4095 range. It is represented in units of 0.1 represented in units of 0.1 dB offset from -140dBm/Hz."
dB offset from -140dBm/Hz."
SYNTAX OCTET STRING (SIZE(0..128)) SYNTAX OCTET STRING (SIZE(0..128))
END END
VDSL2-LINE-MIB DEFINITIONS ::= BEGIN VDSL2-LINE-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
OBJECT-TYPE, OBJECT-TYPE,
transmission, transmission,
skipping to change at page 66, line 22 skipping to change at page 65, line 33
Xdsl2MrefPsdUs Xdsl2MrefPsdUs
FROM VDSL2-LINE-TC-MIB -- [This document] FROM VDSL2-LINE-TC-MIB -- [This document]
MODULE-COMPLIANCE, MODULE-COMPLIANCE,
OBJECT-GROUP, OBJECT-GROUP,
NOTIFICATION-GROUP NOTIFICATION-GROUP
FROM SNMPv2-CONF; FROM SNMPv2-CONF;
vdsl2MIB MODULE-IDENTITY vdsl2MIB MODULE-IDENTITY
LAST-UPDATED "200801290000Z" -- January 29, 2008 LAST-UPDATED "200806010000Z" -- June 1, 2008
ORGANIZATION "ADSLMIB Working Group" ORGANIZATION "ADSLMIB Working Group"
CONTACT-INFO "WG-email: adslmib@ietf.org CONTACT-INFO "WG-email: adslmib@ietf.org
Info: https://www1.ietf.org/mailman/listinfo/adslmib Info: https://www1.ietf.org/mailman/listinfo/adslmib
Chair: Mike Sneed Chair: Mike Sneed
Sand Channel Systems Sand Channel Systems
Postal: P.O. Box 37324 Postal: P.O. Box 37324
Raleigh NC 27627-732 Raleigh NC 27627-732
Email: sneedmike@hotmail.com Email: sneedmike@hotmail.com
Phone: +1 206 600 7022 Phone: +1 206 600 7022
skipping to change at page 68, line 17 skipping to change at page 67, line 29
The MIB module is located in the MIB tree under MIB 2 The MIB module is located in the MIB tree under MIB 2
transmission, as discussed in the MIB-2 Integration (RFC 2863 transmission, as discussed in the MIB-2 Integration (RFC 2863
[RFC2863]) section of this document. [RFC2863]) section of this document.
Copyright (C) The IETF Trust (2008). This version of Copyright (C) The IETF Trust (2008). This version of
this MIB module is part of RFC XXXX: see the RFC itself for this MIB module is part of RFC XXXX: see the RFC itself for
full legal notices." full legal notices."
-- RFC Ed.: replace XXXX with assigned number & remove this note -- RFC Ed.: replace XXXX with assigned number & remove this note
REVISION "200801290000Z" -- January 29, 2008 REVISION "200806010000Z" -- June 1, 2008
DESCRIPTION "Initial version, published as RFC XXXX." DESCRIPTION "Initial version, published as RFC XXXX."
-- RFC Ed.: replace XXXX with assigned number & remove this note -- RFC Ed.: replace XXXX with assigned number & remove this note
::= { transmission xxx } ::= { transmission xxx }
-- IANA, we suggest to put it under { transmission xxx } because -- IANA, we suggest to put it under { transmission xxx } because
-- this is the first available number. -- this is the first available number.
-- RFC Ed.: Please fill in xxx once assigned by IANA. -- RFC Ed.: Please fill in xxx once assigned by IANA.
vdsl2 OBJECT IDENTIFIER ::= { vdsl2MIB 1 } vdsl2 OBJECT IDENTIFIER ::= { vdsl2MIB 1 }
------------------------------------------------ ------------------------------------------------
xdsl2Line OBJECT IDENTIFIER ::= { vdsl2 1 } xdsl2Line OBJECT IDENTIFIER ::= { vdsl2 1 }
skipping to change at page 69, line 7 skipping to change at page 68, line 18
------------------------------------------------ ------------------------------------------------
------------------------------------------------ ------------------------------------------------
-- xdsl2LineTable -- -- xdsl2LineTable --
------------------------------------------------ ------------------------------------------------
xdsl2LineTable OBJECT-TYPE xdsl2LineTable OBJECT-TYPE
SYNTAX SEQUENCE OF Xdsl2LineEntry SYNTAX SEQUENCE OF Xdsl2LineEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The table xdsl2LineTable contains configuration, "The table xdsl2LineTable contains configuration, command and
command and status parameters of the VDSL2/ADSL/ADSL2 status parameters of the VDSL2/ADSL/ADSL2 or ADSL2+ line.
or ADSL2+ line. The index of this table is an interface index where the interface
The index of this table is an interface index where the has an ifType of vdsl2(xxx).
interface has an ifType of vdsl2(xxx).
Several objects in this table MUST be maintained in a Several objects in this table MUST be maintained in a persistent
persistent manner. " manner."
::= { xdsl2Line 1 } ::= { xdsl2Line 1 }
xdsl2LineEntry OBJECT-TYPE xdsl2LineEntry OBJECT-TYPE
SYNTAX Xdsl2LineEntry SYNTAX Xdsl2LineEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The table xdsl2LineTable contains configuration, "The table xdsl2LineTable contains configuration, commands
commands and status parameters of the VDSL2/ADSL/ADSL2 and status parameters of the VDSL2/ADSL/ADSL2 or ADSL2+
or ADSL2+ line." line."
INDEX { ifIndex } INDEX { ifIndex }
::= { xdsl2LineTable 1 } ::= { xdsl2LineTable 1 }
Xdsl2LineEntry ::= Xdsl2LineEntry ::=
SEQUENCE { SEQUENCE {
xdsl2LineCnfgTemplate SnmpAdminString, xdsl2LineCnfgTemplate SnmpAdminString,
xdsl2LineCnfgFallbackTemplate SnmpAdminString, xdsl2LineCnfgFallbackTemplate SnmpAdminString,
xdsl2LineAlarmCnfgTemplate SnmpAdminString, xdsl2LineAlarmCnfgTemplate SnmpAdminString,
xdsl2LineCmndConfPmsf Xdsl2ConfPmsForce, xdsl2LineCmndConfPmsf Xdsl2ConfPmsForce,
xdsl2LineCmndConfLdsf Xdsl2LineLdsf, xdsl2LineCmndConfLdsf Xdsl2LineLdsf,
skipping to change at page 70, line 28 skipping to change at page 69, line 38
xdsl2LineStatusTrellisUs TruthValue, xdsl2LineStatusTrellisUs TruthValue,
xdsl2LineStatusActualCe Unsigned32 xdsl2LineStatusActualCe Unsigned32
} }
xdsl2LineCnfgTemplate OBJECT-TYPE xdsl2LineCnfgTemplate 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
"The value of this object identifies the row in the xDSL2 "The value of this object identifies the row in the xDSL2
Line Line Configuration Templates Table, xdsl2LineConfTemplateTable,
Configuration Templates Table, (xdsl2LineConfTemplateTable), that applies for this line.
which applies for this line.
This object MUST be maintained in a persistent manner." This object MUST be maintained in a persistent manner."
REFERENCE "DSL Forum TR-129, paragraph #5.1" REFERENCE "DSL Forum TR-129, paragraph #5.1"
DEFVAL { "DEFVAL" } DEFVAL { "DEFVAL" }
::= { xdsl2LineEntry 1 } ::= { xdsl2LineEntry 1 }
xdsl2LineCnfgFallbackTemplate OBJECT-TYPE xdsl2LineCnfgFallbackTemplate OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE(0..32)) SYNTAX SnmpAdminString (SIZE(0..32))
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is used to identify the template that "This object is used to identify the template that will be
will be used if the xDSL2 line fails to operate used if the xDSL2 line fails to operate using the primary
using the primary template. The primary template is template. The primary template is identified using the
identified using the xdsl2LineCnfgTemplate attribute. xdsl2LineCnfgTemplate attribute.
For example, a xDSL2 line may fallback to a template For example, a xDSL2 line may fallback to a template with a lower
with a lower rate if the rate specified in the primary rate if the rate specified in the primary template cannot be
template cannot be achieved. achieved.
The value of this object identifies a row in the xDSL2 The value of this object identifies a row in the xDSL2 Line
Line Configuration Template Table, Configuration Template Table, xdsl2LineConfTemplateTable.
xdsl2LineConfTemplateTable. Any row in the xdsl2LineConfTemplateTable table may be used as a
Any row in the xdsl2LineConfTemplateTable table may be fallback template.
used as a fallback template.
If the xDSL2 line fails to operate using the fallback If the xDSL2 line fails to operate using the fallback template
template then the primary template should be retried. then the primary template should be retried.
The xTU-C should continue to alternate between the The xTU-C should continue to alternate between the primary and
primary and fallback templates until one of them fallback templates until one of them succeeds.
succeeds.
If the value of this object is a zero length string then If the value of this object is a zero-length string then no
no fallback template is defined and only the primary fallback template is defined and only the primary template will
template will be used. be used.
Note that implementation of this object is not mandatory. Note that implementation of this object is not mandatory.
If this object is not supported, any attempt to modify this If this object is not supported, any attempt to modify this
object should result in the SET request being rejected. object should result in the SET request being rejected.
This object MUST be maintained in a persistent manner." This object MUST be maintained in a persistent manner."
::= { xdsl2LineEntry 2 } ::= { xdsl2LineEntry 2 }
xdsl2LineAlarmCnfgTemplate OBJECT-TYPE xdsl2LineAlarmCnfgTemplate 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
"The value of this object identifies the row in the xDSL2 "The value of this object identifies the row in the xDSL2
Line Line Alarm Configuration Template Table,
Alarm Configuration Template Table, xdsl2LineAlarmConfTemplateTable, which applies to this line.
(xdsl2LineAlarmConfTemplateTable), which applies to this line.
This object MUST be maintained in a persistent manner." This object MUST be maintained in a persistent manner."
REFERENCE "DSL Forum TR-129, paragraph #5.1" REFERENCE "DSL Forum TR-129, paragraph #5.1"
DEFVAL { "DEFVAL" } DEFVAL { "DEFVAL" }
::= { xdsl2LineEntry 3 } ::= { xdsl2LineEntry 3 }
xdsl2LineCmndConfPmsf OBJECT-TYPE xdsl2LineCmndConfPmsf OBJECT-TYPE
SYNTAX Xdsl2ConfPmsForce SYNTAX Xdsl2ConfPmsForce
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Power management state forced (PMSF). Defines the line "Power management state forced (PMSF). Defines the line
states to be forced by the near-end xTU on this line. states to be forced by the near-end xTU on this line.
The various possible values are: The various possible values are:
l3toL0 (0), l3toL0 (0),
l0toL2 (2), l0toL2 (2),
l0orL2toL3 (3). l0orL2toL3 (3).
This object MUST be maintained in a persistent manner." This object MUST be maintained in a persistent manner."
REFERENCE "ITU-T G.997.1, paragraph #7.3.1.1.3" REFERENCE "ITU-T G.997.1, paragraph #7.3.1.1.3 (PMSF)"
DEFVAL { l3toL0 } DEFVAL { l3toL0 }
::= { xdsl2LineEntry 4 } ::= { xdsl2LineEntry 4 }
xdsl2LineCmndConfLdsf OBJECT-TYPE xdsl2LineCmndConfLdsf OBJECT-TYPE
SYNTAX Xdsl2LineLdsf SYNTAX Xdsl2LineLdsf
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Loop diagnostics mode forced (LDSF). "Loop diagnostics mode forced (LDSF).
Defines whether the line should be forced into the loop Defines whether the line should be forced into the loop
diagnostics mode by the near-end xTU of this line. Note that diagnostics mode by the near-end xTU of this line. Note that
a loop diagnostics may be initiated by the far-end xTU at a loop diagnostics may be initiated by the far-end xTU at any
any time. time.
Only when the xdsl2LineStatusPwrMngState attribute is in Only when the xdsl2LineStatusPwrMngState attribute is in the
the l3(4) state and the xdsl2LineCmndConfPmsf attribute l3(4) state and the xdsl2LineCmndConfPmsf attribute is in the
is in the l0orL2toL3(3) state, can the line be forced into l0orL2toL3(3) state, can the line be forced into loop diagnostic
loop diagnostic mode procedures. Upon successful completion mode procedures. Upon successful completion of the loop
of the loop diagnostic mode procedures, the Access Node shall diagnostic mode procedures, the Access Node shall set this
set this attribute to inhibit(0), and attribute to inhibit(0), and xdsl2LineStatusPwrMngState will
xdsl2LineStatusPwrMngState will remain in the l3(4) state. The remain in the l3(4) state. The loop diagnostic data shall be
loop diagnostic data shall be available at least until available at least until xdsl2LineCmndConfPmsf is set to the
xdsl2LineCmndConfPmsf is set to the l3toL0(0) state. l3toL0(0) state.
The results of the loop diagnostic procedure are stored The results of the loop diagnostic procedure are stored in the
in the tables xdsl2SCStatusTable, xdsl2SCStatusBandTable tables xdsl2SCStatusTable, xdsl2SCStatusBandTable and
and xdsl2SCStatusSegmentTable. The status of the loop xdsl2SCStatusSegmentTable. The status of the loop diagnostic
diagnostic procedue is indicated by procedue is indicated by xdsl2LineCmndConfLdsfFailReason.
xdsl2LineCmndConfLdsfFailReason.
As long as loop diagnostic procedures are not completed As long as loop diagnostic procedures are not completed
successfully, attempts shall be made to do so, until the loop successfully, attempts shall be made to do so, until the loop
diagnostic mode is no longer forced on the line through this diagnostic mode is no longer forced on the line through this
configuration parameter." configuration parameter."
REFERENCE "ITU-T G.997.1, paragraph #7.3.1.1.8" REFERENCE "ITU-T G.997.1, paragraph #7.3.1.1.8 (LDSF)"
DEFVAL { inhibit } DEFVAL { inhibit }
::= { xdsl2LineEntry 5 } ::= { xdsl2LineEntry 5 }
xdsl2LineCmndConfLdsfFailReason OBJECT-TYPE xdsl2LineCmndConfLdsfFailReason OBJECT-TYPE
SYNTAX Xdsl2LdsfResult SYNTAX Xdsl2LdsfResult
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The status of the recent occasion the Loop diagnostics mode "The status of the most recent occasion when the Loop
forced (LDSF) was issued for the associated line. Possible diagnostics mode forced (LDSF) command was issued for the
values are: associated line.
Possible values are:
none (1) - The default value in case LDSF was never none (1) - The default value in case LDSF was never
requested for the associated line. requested for the associated line.
success (2) - The recent command completed success (2) - The recent command completed
successfully. successfully.
inProgress (3) - The Loop Diagnostics process is in inProgress (3) - The Loop Diagnostics process is in
progress. progress.
unsupported (4) - The NE or the line card doesn't support unsupported (4) - The NE or the line card doesn't support
LDSF. LDSF.
cannotRun (5) - The NE cannot initiate the command, due cannotRun (5) - The NE cannot initiate the command, due
to a non specific reason. to a non specific reason.
skipping to change at page 73, line 36 skipping to change at page 72, line 42
noResources (11)- The NE cannot initiate the command, due noResources (11)- The NE cannot initiate the command, due
to lack of internal memory resources." to lack of internal memory resources."
DEFVAL { none } DEFVAL { none }
::= { xdsl2LineEntry 6 } ::= { xdsl2LineEntry 6 }
xdsl2LineCmndConfBpsc OBJECT-TYPE xdsl2LineCmndConfBpsc OBJECT-TYPE
SYNTAX Xdsl2LineBpsc SYNTAX Xdsl2LineBpsc
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Request a bits per sub-carrier measurement to be made. "Request a bits per subcarrier measurement to be made.
A request for a bits per sub-carrier measurement is made A request for a bits per subcarrier measurement is made by
by setting this attribute to the value of measure(2). setting this attribute to the value of measure(2). Upon
Upon completion of the measurement request, completion of the measurement request, the Access Node shall set
the Access Node shall set this attribute to idle(1). this attribute to idle(1).
Note that a bits per sub-carrier measurement is also Note that a bits per subcarrier measurement is also performed
performed during a line diagnostic procedure. This during a line diagnostic procedure. This attribute provides an
attribute provides an additional mechanism to fetch additional mechanism to fetch the bits per subcarrier data. This
the bits per sub-carrier data. This additional additional mechanism is provided so that bits per subcarrier
mechanism is provided so that bits per sub-carrier data may be fetched without forcing the line into no power state.
data may be fetched without forcing the line into no This is useful because the bits per subcarrier allocation may be
power state. This is useful because the bits per adjusted at show time due to rate adaption and bit swapping.
sub-carrier allocation may be adjusted at show time
due to rate adaption and bit swapping.
The implementation of this additional mechanism for The implementation of this additional mechanism for measuring
measuring bits per sub-carrier is not mandatory. bits per subcarrier is not mandatory.
The results of the bits per sub-carrier measurement are The results of the bits per subcarrier measurement are stored in
stored in xdsl2LineSegmentTable. The status of the bits xdsl2LineSegmentTable. The status of the bits per subcarrier
per sub-carrier measurement is indicated by measurement is indicated by
xdsl2LineCmndConfBpscFailReason." xdsl2LineCmndConfBpscFailReason."
DEFVAL { idle } DEFVAL { idle }
::= { xdsl2LineEntry 7 } ::= { xdsl2LineEntry 7 }
xdsl2LineCmndConfBpscFailReason OBJECT-TYPE xdsl2LineCmndConfBpscFailReason OBJECT-TYPE
SYNTAX Xdsl2BpscResult SYNTAX Xdsl2BpscResult
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The status of the most recent bits per sub-carrier "The status of the most recent bits per subcarrier
measurement request issued for the associated line. measurement request issued for the associated line.
Possible values are: Possible values are:
none (1) - The default value, in case a measurement none (1) - The default value, in case a measurement
was never requested for the associated was never requested for the associated
line. line.
success (2) - The recent measurement request completed success (2) - The recent measurement request completed
successfully. successfully.
inProgress (3) - The bits per sub-carrier measurement is inProgress (3) - The bits per subcarrier measurement is
in progress. in progress.
unsupported (4) - The bits per sub-carrier request unsupported (4) - The bits per subcarrier request
mechanism is not supported. mechanism is not supported.
failed (5) - The measurement request has failed and no failed (5) - The measurement request has failed and no
results are available. results are available.
noResources (6) - The NE cannot initiate the command, due noResources (6) - The NE cannot initiate the command, due
to lack of internal memory resources." to lack of internal memory resources."
DEFVAL { none } DEFVAL { none }
::= { xdsl2LineEntry 8 } ::= { xdsl2LineEntry 8 }
xdsl2LineCmndConfBpscReqCount OBJECT-TYPE xdsl2LineCmndConfBpscReqCount OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Measurement request counter. "Measurement request counter.
This counter is incremented by one every time a request This counter is incremented by one every time a request for a
for a measurement is made. A measurement request is made measurement is made. A measurement request is made by setting the
by setting the xdsl2LineCmndConfBpsc attribute to the xdsl2LineCmndConfBpsc attribute to the value measure(2).
value measure(2).
SNMP managers can use this attribute to check that the SNMP managers can use this attribute to check that the
measurement results retrieved by the manager where not measurement results retrieved by the manager where not interupted
interupted by another measurement request." by another measurement request."
DEFVAL { 0 } DEFVAL { 0 }
::= { xdsl2LineEntry 9 } ::= { xdsl2LineEntry 9 }
xdsl2LineCmndAutomodeColdStart OBJECT-TYPE xdsl2LineCmndAutomodeColdStart OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Automode cold start forced. This parameter is defined "Automode cold start forced. This parameter is defined in
in order to improve testing of the performance of xTUs order to improve testing of the performance of xTUs supporting
supporting automode when it is enabled in the MIB. automode when it is enabled in the MIB.
Change the value of this parameter to 'true' indicates Change the value of this parameter to 'true' indicates a change
a change in loop conditions applied to the devices under in loop conditions applied to the devices under test. The xTUs
test. The xTUs shall reset any historical information shall reset any historical information used for automode and for
used for automode and for shortening G.994.1 handshake shortening G.994.1 handshake and initialization.
and initialization.
Automode is the case where multiple operation-modes are Automode is the case where multiple operation-modes are enabled
enabled through the xdsl2LConfProfXtuTransSysEna object through the xdsl2LConfProfXtuTransSysEna object in the line
in the line configuration profile being used for the configuration profile being used for the line, and where the
line, and where the selection of the actual selection of the actual operation-mode depends not only on the
operation-mode depends not only on the common common capabilities of both xTUs (as exchanged in G.994.1), but
capabilities of both xTUs (as exchanged in G.994.1), but also on achievable data rates under given loop conditions."
also on achievable data rates under given loop REFERENCE "ITU-T G.997.1, paragraph #7.3.1.1.10
conditions." (Automode Cold Start Forced)"
REFERENCE "ITU-T G.997.1, paragraph #7.3.1.1.10"
DEFVAL { false } DEFVAL { false }
::= { xdsl2LineEntry 10 } ::= { xdsl2LineEntry 10 }
xdsl2LineCmndConfReset OBJECT-TYPE xdsl2LineCmndConfReset OBJECT-TYPE
SYNTAX Xdsl2LineReset SYNTAX Xdsl2LineReset
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Request a line reset to occur. "Request a line reset to occur.
If this attribute is set to the value of reset(2), then If this attribute is set to the value of reset(2), then force
force the line to reset ( i.e. the modems will retrain ). the line to reset (i.e., the modems will retrain).
When the line has successfully reset, the SNMP agent will When the line has successfully reset, the SNMP agent will
set the value of this attribute to idle(1). set the value of this attribute to idle(1).
Note that the xdsl2LineCmndConfPmsf attribute will always Note that the xdsl2LineCmndConfPmsf attribute will always take
take precedence over this attribute. precedence over this attribute.
If the xdsl2LineCmndConfPmsf attribute is set to the value If the xdsl2LineCmndConfPmsf attribute is set to the value
l0orL2toL3(3), then the line must not return to the l0orL2toL3(3), then the line MUST NOT return to the showtime
showtime state due to a reset request action performed state due to a reset request action performed using this
using this attribute." attribute."
DEFVAL { idle } DEFVAL { idle }
::= { xdsl2LineEntry 11 } ::= { xdsl2LineEntry 11 }
xdsl2LineStatusActTemplate OBJECT-TYPE xdsl2LineStatusActTemplate OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE(0..32)) SYNTAX SnmpAdminString (SIZE(0..32))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is used to identify the template that "This object is used to identify the template that is
is currently in use for this line. currently in use for this line.
This attribute is updated when a successfull line This attribute is updated when a successfull line initialisation
initialisation occurs. occurs.
This attribute indicates if the primary template This attribute indicates if the primary template
( xdsl2LineCnfgTemplate ) is in use or the (xdsl2LineCnfgTemplate) is in use or the fallback template
fallback template ( xdsl2LineCnfgFallbackTemplate ) (xdsl2LineCnfgFallbackTemplate) is in use.
is in use. If the line is not successfully initialised then the value of
If the line is not successfully initialised then this object will be a zero-length string."
the value of this object will be a zero length string."
::= { xdsl2LineEntry 12 } ::= { xdsl2LineEntry 12 }
xdsl2LineStatusXtuTransSys OBJECT-TYPE xdsl2LineStatusXtuTransSys OBJECT-TYPE
SYNTAX Xdsl2TransmissionModeType SYNTAX Xdsl2TransmissionModeType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The xTU Transmission System (xTS) in use. "The xTU Transmission System (xTS) in use.
It is coded in a bit-map representation with one bit set to It is coded in a bit-map representation with one bit set to
'1' (the selected coding for the DSL line). This '1' (the selected coding for the DSL line). This
parameter parameter may be derived from the handshaking procedures defined
may be derived from the handshaking procedures defined in in Recommendation G.994.1. A set of xDSL line transmission
Recommendation G.994.1. A set of xDSL line transmission
modes, with one bit per mode. " modes, with one bit per mode. "
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.1" REFERENCE "ITU-T G.997.1, paragraph #7.5.1.1
(xDSL transmission system)"
DEFVAL { {} } DEFVAL { {} }
::= { xdsl2LineEntry 13 } ::= { xdsl2LineEntry 13 }
xdsl2LineStatusPwrMngState OBJECT-TYPE xdsl2LineStatusPwrMngState OBJECT-TYPE
SYNTAX Xdsl2PowerMngState SYNTAX Xdsl2PowerMngState
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current power management state. One of four possible "The current power management state. One of four possible
power management states: power management states:
L0 - Synchronized and full transmission (i.e., Showtime), L0 - Synchronized and full transmission (i.e., Showtime).
L1 - Low Power with reduced net data rate (G.992.2 only), L1 - Low Power with reduced net data rate (G.992.2 only).
L2 - Low Power with reduced net data rate (G.992.3 and L2 - Low Power with reduced net data rate (G.992.3 and
G.992.4 only), G.992.4 only).
L3 - No power L3 - No power.
The various possible values are:l0(1), l1(2), l2(3), l3(4)." The various possible values are:l0(1), l1(2), l2(3), l3(4)."
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.5" REFERENCE "ITU-T G.997.1, paragraph #7.5.1.5
(Line power management state)"
DEFVAL { l3 } DEFVAL { l3 }
::= { xdsl2LineEntry 14 } ::= { xdsl2LineEntry 14 }
xdsl2LineStatusInitResult OBJECT-TYPE xdsl2LineStatusInitResult OBJECT-TYPE
SYNTAX Xdsl2InitResult SYNTAX Xdsl2InitResult
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the result of the last full initialization "Indicates the result of the last full initialization
performed performed on the line. It is an enumeration type with the
on the line. It is an enumeration type with the following following values: noFail(0), configError(1),
values: noFail(0), configError(1), configNotFeasible(2), configNotFeasible(2), commFail(3), noPeerAtu(4),
commFail(3), noPeerAtu(4), otherCause(5)." otherCause(5)."
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.6" REFERENCE "ITU-T G.997.1, paragraph #7.5.1.6
(Initialization success/failure cause)"
DEFVAL { noFail } DEFVAL { noFail }
::= { xdsl2LineEntry 15 } ::= { xdsl2LineEntry 15 }
xdsl2LineStatusLastStateDs OBJECT-TYPE xdsl2LineStatusLastStateDs OBJECT-TYPE
SYNTAX Xdsl2LastTransmittedState SYNTAX Xdsl2LastTransmittedState
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The last successful transmitted initialization state in "The last successful transmitted initialization state in
the downstream direction in the last full initialization the downstream direction in the last full initialization
performed on the line." performed on the line."
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.7" REFERENCE "ITU-T G.997.1, paragraph #7.5.1.7
(Downstream last transmitted state)"
DEFVAL { atucG9941 } DEFVAL { atucG9941 }
::= { xdsl2LineEntry 16 } ::= { xdsl2LineEntry 16 }
xdsl2LineStatusLastStateUs OBJECT-TYPE xdsl2LineStatusLastStateUs OBJECT-TYPE
SYNTAX Xdsl2LastTransmittedState SYNTAX Xdsl2LastTransmittedState
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The last successful transmitted initialization state in the "The last successful transmitted initialization state in the
upstream direction in the last full initialization performed upstream direction in the last full initialization performed on
on the line." the line."
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.8" REFERENCE "ITU-T G.997.1, paragraph #7.5.1.8
(Upstream last transmitted state)"
DEFVAL { aturG9941 } DEFVAL { aturG9941 }
::= { xdsl2LineEntry 17 } ::= { xdsl2LineEntry 17 }
xdsl2LineStatusXtur OBJECT-TYPE xdsl2LineStatusXtur OBJECT-TYPE
SYNTAX Xdsl2LineStatus SYNTAX Xdsl2LineStatus
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates current state (existing failures) of the xTU-R. "Indicates current state (existing failures) of the xTU-R.
This is a bit-map of possible conditions. " This is a bit-map of possible conditions. "
REFERENCE "ITU-T G.997.1, paragraph #7.1.1.2" REFERENCE "ITU-T G.997.1, paragraph #7.1.1.2
(Line far-end failures)"
DEFVAL { { noDefect } } DEFVAL { { noDefect } }
::= { xdsl2LineEntry 18 } ::= { xdsl2LineEntry 18 }
xdsl2LineStatusXtuc OBJECT-TYPE xdsl2LineStatusXtuc OBJECT-TYPE
SYNTAX Xdsl2LineStatus SYNTAX Xdsl2LineStatus
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates current state (existing failures) of the xTU-C. "Indicates current state (existing failures) of the xTU-C.
This is a bit-map of possible conditions. " This is a bit-map of possible conditions. "
REFERENCE "ITU-T G.997.1, paragraph #7.1.1.1" REFERENCE "ITU-T G.997.1, paragraph #7.1.1.1
(Line near-end failures)"
DEFVAL { { noDefect } } DEFVAL { { noDefect } }
::= { xdsl2LineEntry 19 } ::= { xdsl2LineEntry 19 }
xdsl2LineStatusAttainableRateDs OBJECT-TYPE xdsl2LineStatusAttainableRateDs OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "bits/second" UNITS "bits/second"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"(ATTNDRds) "Maximum Attainable Data Rate Downstream.
Maximum Attainable Data Rate Downstream.
The maximum downstream net data rate currently attainable by The maximum downstream net data rate currently attainable by
the xTU-C transmitter and the xTU-R receiver, coded in the xTU-C transmitter and the xTU-R receiver, coded in
bit/s." bit/s."
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.19" REFERENCE "ITU-T G.997.1, paragraph #7.5.1.19 (ATTNDRds)
"
DEFVAL { 0 } DEFVAL { 0 }
::= { xdsl2LineEntry 20 } ::= { xdsl2LineEntry 20 }
xdsl2LineStatusAttainableRateUs OBJECT-TYPE xdsl2LineStatusAttainableRateUs OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "bits/second" UNITS "bits/second"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"(ATTNDRus) "Maximum Attainable Data Rate Upstream.
Maximum Attainable Data Rate Upstream.
The maximum upstream net data rate currently attainable by the The maximum upstream net data rate currently attainable by the
xTU-R transmitter and the xTU-C receiver, coded in bit/s." xTU-R transmitter and the xTU-C receiver, coded in bit/s."
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.20" REFERENCE "ITU-T G.997.1, paragraph #7.5.1.20 (ATTNDRus)
"
DEFVAL { 0 } DEFVAL { 0 }
::= { xdsl2LineEntry 21 } ::= { xdsl2LineEntry 21 }
xdsl2LineStatusActPsdDs OBJECT-TYPE xdsl2LineStatusActPsdDs OBJECT-TYPE
SYNTAX Integer32 (-900..0 | 2147483647) SYNTAX Integer32 (-900..0 | 2147483647)
UNITS "0.1 dBm/Hz" UNITS "0.1 dBm/Hz"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"(ACTPSDds) "Actual Power Spectrum Density (PSD) Downstream. The average
Actual Power Spectrum Density (PSD) Downstream. The average downstream transmit PSD over the subcarriers used for downstream.
downstream transmit PSD over the sub-carriers used for It ranges from -900 to 0 units of 0.1 dBm/Hz (Physical values are
downstream. It ranges from -900 to 0 units of 0.1 dBm/Hz -90 to 0 dBm/Hz).
(Physical values are -90 to 0 dBm/Hz). A value of 0x7FFFFFFF (2147483647) indicates the measurement is
A value of 0x7FFFFFFF (2147483647) indicates the measurement out of range to be represented."
is out of range to be represented." REFERENCE "ITU-T G.997.1, paragraph #7.5.1.21 (ACTPSDds)
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.21" "
DEFVAL { 2147483647 } DEFVAL { 2147483647 }
::= { xdsl2LineEntry 22 } ::= { xdsl2LineEntry 22 }
xdsl2LineStatusActPsdUs OBJECT-TYPE xdsl2LineStatusActPsdUs OBJECT-TYPE
SYNTAX Integer32 (-900..0 | 2147483647) SYNTAX Integer32 (-900..0 | 2147483647)
UNITS "0.1 dBm/Hz" UNITS "0.1 dBm/Hz"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"(ACTPSDus) "Actual Power Spectrum Density (PSD) Upstream. The average
Actual Power Spectrum Density (PSD) Upstream. The average upstream transmit PSD over the subcarriers used for upstream.
upstream transmit PSD over the sub-carriers used for upstream. It ranges from -900 to 0 units of 0.1 dBm/Hz (Physical values are
It ranges from -900 to 0 units of 0.1 dBm/Hz (Physical values -90 to 0 dBm/Hz).
are -90 to 0 dBm/Hz). A value of 0x7FFFFFFF (2147483647) indicates the measurement is
A value of 0x7FFFFFFF (2147483647) indicates the measurement out of range to be represented."
is out of range to be represented." REFERENCE "ITU-T G.997.1, paragraph #7.5.1.22 (ACTPSDus)
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.22" "
DEFVAL { 2147483647 } DEFVAL { 2147483647 }
::= { xdsl2LineEntry 23 } ::= { xdsl2LineEntry 23 }
xdsl2LineStatusActAtpDs OBJECT-TYPE xdsl2LineStatusActAtpDs OBJECT-TYPE
SYNTAX Integer32 (-310..310 | 2147483647) SYNTAX Integer32 (-310..310 | 2147483647)
UNITS "0.1 dBm" UNITS "0.1 dBm"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"(ACTATPds) "Actual Aggregate Transmit Power Downstream.
Actual Aggregate Transmit Power Downstream. The total amount The total amount of transmit power delivered by the xTU-C at
of transmit power delivered by the xTU-C at the U-C reference the U-C reference point, at the instant of measurement. It
point, at the instant of measurement. It ranges from -310 to ranges from -310 to 310 units of 0.1 dBm (Physical values are -31
310 units of 0.1 dBm (Physical values are -31 to 31 dBm). to 31 dBm).
A value of 0x7FFFFFFF (2147483647) indicates the measurement
is out of range to be represented." A value of 0x7FFFFFFF (2147483647) indicates the measurement is
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.24" out of range to be represented."
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.24 (ACTATPds)
"
DEFVAL { 2147483647 } DEFVAL { 2147483647 }
::= { xdsl2LineEntry 24 } ::= { xdsl2LineEntry 24 }
xdsl2LineStatusActAtpUs OBJECT-TYPE xdsl2LineStatusActAtpUs OBJECT-TYPE
SYNTAX Integer32 (-310..310 | 2147483647) SYNTAX Integer32 (-310..310 | 2147483647)
UNITS "0.1 dBm" UNITS "0.1 dBm"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"(ACTATPus) "Actual Aggregate Transmit Power Upstream.
Actual Aggregate Transmit Power Upstream. The total amount of The total amount of transmit power delivered by the xTU-R at the
transmit power delivered by the xTU-R at the U-R U-R reference point, at the instant of measurement. It ranges
reference point, at the instant of measurement. It ranges
from -310 to 310 units of 0.1 dBm (Physical values are -31 from -310 to 310 units of 0.1 dBm (Physical values are -31
to 31 dBm). to 31 dBm).
A value of 0x7FFFFFFF (2147483647) indicates the measurement A value of 0x7FFFFFFF (2147483647) indicates the measurement is
is out of range to be represented." out of range to be represented."
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.25" REFERENCE "ITU-T G.997.1, paragraph #7.5.1.25 (ACTATPus)
"
DEFVAL { 2147483647 } DEFVAL { 2147483647 }
::= { xdsl2LineEntry 25 } ::= { xdsl2LineEntry 25 }
xdsl2LineStatusActProfile OBJECT-TYPE xdsl2LineStatusActProfile OBJECT-TYPE
SYNTAX Xdsl2LineProfiles SYNTAX Xdsl2LineProfiles
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The G.993.2 profile in use. "The G.993.2 profile in use.
The configuration parameter xdsl2LConfProfProfiles defines The configuration parameter xdsl2LConfProfProfiles defines
the set of allowed G.993.2 profiles. This parameter indicates the set of allowed G.993.2 profiles. This parameter indicates
the profile in use on this line. the profile in use on this line.
This parameter may be derived from the handshaking procedures This parameter may be derived from the handshaking procedures
defined in ITU-T Rec. G.994.1." defined in ITU-T Rec. G.994.1."
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.2" REFERENCE "ITU-T G.997.1, paragraph #7.5.1.2 (VDSL2 Profile)
"
DEFVAL { {} } DEFVAL { {} }
::= { xdsl2LineEntry 26 } ::= { xdsl2LineEntry 26 }
xdsl2LineStatusActLimitMask OBJECT-TYPE xdsl2LineStatusActLimitMask OBJECT-TYPE
SYNTAX Xdsl2LineLimitMask SYNTAX Xdsl2LineLimitMask
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Limit PSD mask and band plan in use. "The Limit PSD mask and band plan in use.
The configuration parameter xdsl2LConfProfLimitMask defines The configuration parameter xdsl2LConfProfLimitMask defines
the set of allowed G.993.2 limit PSD masks. the set of allowed G.993.2 limit PSD masks.
This parameter indicates the limit PSD mask in use on This parameter indicates the limit PSD mask in use on this
this line." line."
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.3" REFERENCE "ITU-T G.997.1, paragraph #7.5.1.3
(VDSL2 Limit PSD Mask and Band plan)"
DEFVAL { {} } DEFVAL { {} }
::= { xdsl2LineEntry 27 } ::= { xdsl2LineEntry 27 }
xdsl2LineStatusActUs0Mask OBJECT-TYPE xdsl2LineStatusActUs0Mask OBJECT-TYPE
SYNTAX Xdsl2LineUs0Mask SYNTAX Xdsl2LineUs0Mask
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The US0 PSD mask in use. "The US0 PSD mask in use.
The configuration parameter xdsl2LConfProfUs0Mask defines The configuration parameter xdsl2LConfProfUs0Mask defines
the set of allowed US0 PSD masks. the set of allowed US0 PSD masks.
This parameter indicates the US0 PSD mask in use on This parameter indicates the US0 PSD mask in use on this line.
this line. This parameter may be derived from the handshaking procedures
This parameter may be derived from the handshaking defined in ITU-T Rec. G.994.1."
procedures defined in ITU-T Rec. G.994.1." REFERENCE "ITU-T G.997.1, paragraph #7.5.1.4
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.4" (VDSL2 US0 PSD Mask)"
DEFVAL { {} } DEFVAL { {} }
::= { xdsl2LineEntry 28 } ::= { xdsl2LineEntry 28 }
xdsl2LineStatusActSnrModeDs OBJECT-TYPE xdsl2LineStatusActSnrModeDs OBJECT-TYPE
SYNTAX Xdsl2LineSnrMode SYNTAX Xdsl2LineSnrMode
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This parameter indicates if the transmitter "This parameter indicates if the transmitter
referred virtual noise is active on the line in the referred virtual noise is active on the line in the downstream
downstream direction. direction.
The configuration parameter xdsl2LConfProfSnrModeDs The configuration parameter xdsl2LConfProfSnrModeDs is used to
is used to configure referred virtual noise." configure referred virtual noise."
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.15 (ACTSNRMODEds)" REFERENCE "ITU-T G.997.1, paragraph #7.5.1.15 (ACTSNRMODEds)
"
DEFVAL { virtualNoiseDisabled } DEFVAL { virtualNoiseDisabled }
::= { xdsl2LineEntry 29 } ::= { xdsl2LineEntry 29 }
xdsl2LineStatusActSnrModeUs OBJECT-TYPE xdsl2LineStatusActSnrModeUs OBJECT-TYPE
SYNTAX Xdsl2LineSnrMode SYNTAX Xdsl2LineSnrMode
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This parameter indicates if the transmitter "This parameter indicates if the transmitter referred virtual
referred virtual noise is active on the line in the noise is active on the line in the upstream direction.
upstream direction. The configuration parameter xdsl2LConfProfSnrModeUs is used to
The configuration parameter xdsl2LConfProfSnrModeUs is configure referred virtual noise."
used to configure referred virtual noise." REFERENCE "ITU-T G.997.1, paragraph #7.5.1.18 (ACTSNRMODEus)
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.18 (ACTSNRMODEus)" "
DEFVAL { virtualNoiseDisabled } DEFVAL { virtualNoiseDisabled }
::= { xdsl2LineEntry 30 } ::= { xdsl2LineEntry 30 }
xdsl2LineStatusElectricalLength OBJECT-TYPE xdsl2LineStatusElectricalLength OBJECT-TYPE
SYNTAX Unsigned32 (0..1280) SYNTAX Unsigned32 (0..1280)
UNITS "0.1 dB" UNITS "0.1 dB"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"(UPBOKLE) "This parameter contains the estimated electrical length
This parameter contains the estimated electrical length
expressed in dB at 1 MHz, kl0. This is the final electrical expressed in dB at 1 MHz, kl0. This is the final electrical
length that would have been sent from the VTU-O to VTU-R if length that would have been sent from the VTU-O to VTU-R if the
the electrical length was not forced by the CO-MIB. electrical length was not forced by the CO-MIB.
The value ranges from 0 to 128 dB in steps of 0.1 dB." The value ranges from 0 to 128 dB in steps of 0.1 dB."
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.23" REFERENCE "ITU-T G.997.1, paragraph #7.5.1.23 (UPBOKLE)"
DEFVAL { 0 } DEFVAL { 0 }
::= { xdsl2LineEntry 31 } ::= { xdsl2LineEntry 31 }
xdsl2LineStatusTssiDs OBJECT-TYPE xdsl2LineStatusTssiDs OBJECT-TYPE
SYNTAX Xdsl2Tssi SYNTAX Xdsl2Tssi
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The transmit spectrum shaping (TSSi) breakpoints expressed "The transmit spectrum shaping (TSSi) breakpoints expressed
as the set of breakpoints exchanged during G.994.1. as the set of breakpoints exchanged during G.994.1.
Each breakpoint is a pair of values occupying 3 octets with the Each breakpoint is a pair of values occupying 3 octets with the
following structure: following structure:
First 2 octets - Index of the subcarrier used in the context of First 2 octets - Index of the subcarrier used in the context of
the breakpoint. the breakpoint.
Third octet - The shaping parameter at the breakpoint. Third octet - The shaping parameter at the breakpoint.
Subcarrier index is an unsigned number in the range 1 to NSCds. Subcarrier index is an unsigned number in the range 1 to NSCds.
The shaping parameter value is in the range 0 to 126 (units of The shaping parameter value is in the range 0 to 126 (units of
-0.5dB). The special value 127 indicates that the subcarrier -0.5dB). The special value 127 indicates that the subcarrier is
is not transmitted." not transmitted."
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.29.5 (TSSpsds)" REFERENCE "ITU-T G.997.1, paragraph #7.5.1.29.5 (TSSpsds)"
::= { xdsl2LineEntry 32 } ::= { xdsl2LineEntry 32 }
xdsl2LineStatusTssiUs OBJECT-TYPE xdsl2LineStatusTssiUs OBJECT-TYPE
SYNTAX Xdsl2Tssi SYNTAX Xdsl2Tssi
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The transmit spectrum shaping (TSSi) breakpoints expressed "The transmit spectrum shaping (TSSi) breakpoints expressed
as the set of breakpoints exchanged during G.994.1. as the set of breakpoints exchanged during G.994.1.
skipping to change at page 82, line 41 skipping to change at page 82, line 4
xdsl2LineStatusTssiUs OBJECT-TYPE xdsl2LineStatusTssiUs OBJECT-TYPE
SYNTAX Xdsl2Tssi SYNTAX Xdsl2Tssi
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The transmit spectrum shaping (TSSi) breakpoints expressed "The transmit spectrum shaping (TSSi) breakpoints expressed
as the set of breakpoints exchanged during G.994.1. as the set of breakpoints exchanged during G.994.1.
Each breakpoint is a pair of values occupying 3 octets with the Each breakpoint is a pair of values occupying 3 octets with the
following structure: following structure:
First 2 octets - Index of the subcarrier used in the context of First 2 octets - Index of the subcarrier used in the context of
the breakpoint. the breakpoint.
Third octet - The shaping parameter at the breakpoint. Third octet - The shaping parameter at the breakpoint.
Subcarrier index is an unsigned number in the range 1 to NSCus. Subcarrier index is an unsigned number in the range 1 to NSCus.
The shaping parameter value is in the range 0 to 126 (units of The shaping parameter value is in the range 0 to 126 (units of
-0.5dB). The special value 127 indicates that the subcarrier -0.5dB). The special value 127 indicates that the subcarrier is
is not transmitted." not transmitted."
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.29.6 (TSSpsus)" REFERENCE "ITU-T G.997.1, paragraph #7.5.1.29.6 (TSSpsus)"
::= { xdsl2LineEntry 33 } ::= { xdsl2LineEntry 33 }
xdsl2LineStatusMrefPsdDs OBJECT-TYPE xdsl2LineStatusMrefPsdDs OBJECT-TYPE
SYNTAX Xdsl2MrefPsdDs SYNTAX Xdsl2MrefPsdDs
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The MEDLEY Reference PSD status parameters on "The MEDLEY Reference PSD status parameters
downstreasm direction expressed as the set of breakpoints in the downstreasm
exchanged at initialization. direction expressed as the set of breakpoints exchanged at
The OCTET STRING contains up to 48 pairs initialization.
of values in the following structure: The OCTET STRING contains up to 48 pairs of values in the
Octets 0&1 -- Index of 1st subcarrier used following structure:
in the context of a first breakpoint. Octets 0-1 -- Index of 1st subcarrier used in the context
Octets 2&3 -- The PSD level for the of a first breakpoint.
subcarrier indicated in octets 0&1. Octets 2-3 -- The PSD level for the subcarrier indicated
in octets 0-1.
Octets 4-7 -- Same, for a 2nd breakpoint Octets 4-7 -- Same, for a 2nd breakpoint
Octets 8-11 -- Same, for a 3rd breakpoint Octets 8-11 -- Same, for a 3rd breakpoint
And so on until And so on until
Octets 188-191 -- Same, for a 48th breakpoint. Octets 188-191 -- Same, for a 48th breakpoint.
Each subcarrier index is an unsigned number Each subcarrier index is an unsigned number in the range 1 to
in the range 1 and NSds (i.e., highest NSds (i.e., highest supported subcarrier index in the downstream
supported sub carrier index on downstream
direction). direction).
The PSD level is an integer value in the 0 to The PSD level is an integer value in the 0 to 4095 range. It is
4095 range. It is represented in units of 0.1 represented in units of 0.1 dB offset from -140dBm/Hz."
dB offset from -140dBm/Hz." REFERENCE "ITU-T G.997.1, paragraph #7.5.1.29.7 (MREFPSDds)
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.29.7 (MREFpsds)" "
::= { xdsl2LineEntry 34 } ::= { xdsl2LineEntry 34 }
xdsl2LineStatusMrefPsdUs OBJECT-TYPE xdsl2LineStatusMrefPsdUs OBJECT-TYPE
SYNTAX Xdsl2MrefPsdUs SYNTAX Xdsl2MrefPsdUs
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The MEDLEY Reference PSD status parameters on "The MEDLEY Reference PSD status parameters in the
upstreasm direction expressed as the set of breakpoints upstreasm direction expressed as the set of breakpoints
exchanged at initialization. exchanged at initialization.
The OCTET STRING contains up to 32 pairs The OCTET STRING contains up to 32 pairs of values in the
of values in the following structure: following structure:
Octets 0&1 -- Index of 1st subcarrier used
in the context of a first breakpoint. Octets 0-1 -- Index of 1st subcarrier used in the context
Octets 2&3 -- The PSD level for the of a first breakpoint.
subcarrier indicated in octets 0&1. Octets 2-3 -- The PSD level for the subcarrier indicated
in octets 0-1.
Octets 4-7 -- Same, for a 2nd breakpoint Octets 4-7 -- Same, for a 2nd breakpoint
Octets 8-11 -- Same, for a 3rd breakpoint Octets 8-11 -- Same, for a 3rd breakpoint
And so on until And so on until
Octets 124-127 -- Same, for a 32nd breakpoint. Octets 124-127 -- Same, for a 32nd breakpoint.
Each subcarrier index is an unsigned number Each subcarrier index is an unsigned number in the range 1 to
in the range 1 and NSus (i.e., highest NSus (i.e., highest supported subcarrier index in the upstream
supported sub carrier index on upstream
direction). direction).
The PSD level is an integer value in the 0 to The PSD level is an integer value in the 0 to 4095 range. It is
4095 range. It is represented in units of 0.1 represented in units of 0.1 dB offset from -140dBm/Hz."
dB offset from -140dBm/Hz." REFERENCE "ITU-T G.997.1, paragraph #7.5.1.29.8 (MREFPSDus)
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.29.8 (MREFpsus)" "
::= { xdsl2LineEntry 35 } ::= { xdsl2LineEntry 35 }
xdsl2LineStatusTrellisDs OBJECT-TYPE xdsl2LineStatusTrellisDs OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This parameter reports whether trellis coding "This parameter reports whether trellis coding is in use in
is in use in the downstream direction." the downstream direction."
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.30" REFERENCE "ITU-T G.997.1, paragraph #7.5.1.30 (TRELLISds)
"
DEFVAL { false } DEFVAL { false }
::= { xdsl2LineEntry 36 } ::= { xdsl2LineEntry 36 }
xdsl2LineStatusTrellisUs OBJECT-TYPE xdsl2LineStatusTrellisUs OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This parameter reports whether trellis coding "This parameter reports whether trellis coding is in use in
is in use in the upstream direction." the upstream direction."
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.31" REFERENCE "ITU-T G.997.1, paragraph #7.5.1.31 (TRELLISus)
"
DEFVAL { false } DEFVAL { false }
::= { xdsl2LineEntry 37 } ::= { xdsl2LineEntry 37 }
xdsl2LineStatusActualCe OBJECT-TYPE xdsl2LineStatusActualCe OBJECT-TYPE
SYNTAX Unsigned32 (2..16) SYNTAX Unsigned32 (2..16)
UNITS "N/32 samples" UNITS "N/32 samples"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"(ACTUALCE) "(ACTUALCE)
This parameter reports the cyclic extension This parameter reports the cyclic extension used on the line. It
used on the line. It is coded as an unsigned integer from is coded as an unsigned integer from 2 to 16 in units of N/32
2 to 16 in units of N/32 samples, where 2N is the IDFT size." samples, where 2N is the IDFT size."
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.32" REFERENCE "ITU-T G.997.1, paragraph #7.5.1.32 (ACTUALCE)
"
DEFVAL { 2 } DEFVAL { 2 }
::= { xdsl2LineEntry 38 } ::= { xdsl2LineEntry 38 }
------------------------------------------------ ------------------------------------------------
-- xdsl2LineSegmentTable -- -- xdsl2LineSegmentTable --
------------------------------------------------ ------------------------------------------------
xdsl2LineSegmentTable OBJECT-TYPE xdsl2LineSegmentTable OBJECT-TYPE
SYNTAX SEQUENCE OF Xdsl2LineSegmentEntry SYNTAX SEQUENCE OF Xdsl2LineSegmentEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The table xdsl2LineSegmentTable contains status "The table xdsl2LineSegmentTable contains status parameters
parameters of VDSL2/ADSL/ADSL2 and ADSL2+ sub-carriers. of VDSL2/ADSL/ADSL2 and ADSL2+ subcarriers.
The parameters in this table are updated when a The parameters in this table are updated when a measurement
measurement request is made using the request is made using the xdsl2LineCmndConfBpsc attribute.
xdsl2LineCmndConfBpsc attribute.
Note that a bits per sub-carrier measurement is also Note that a bits per subcarrier measurement is also performed
performed during a line diagnostic procedure. This during a line diagnostic procedure. This table provides an
table provides an additional mechanism to fetch additional mechanism to fetch the bits per subcarrier data. This
the bits per sub-carrier data. This additional additional mechanism is provided so that bits per subcarrier
mechanism is provided so that bits per sub-carrier data may be fetched without forcing the line into no power state.
data may be fetched without forcing the line into no This is useful because the bits per subcarrier allocation may be
power state. This is useful because the bits per adjusted at show time due to rate adaption and bit swapping.
sub-carrier allocation may be adjusted at show time
due to rate adaption and bit swapping.
The implementation of this additional mechanism for The implementation of this additional mechanism for measuring
measuring bits per sub-carrier is not mandatory." bits per subcarrier is not mandatory."
::= { xdsl2Status 1 } ::= { xdsl2Status 1 }
xdsl2LineSegmentEntry OBJECT-TYPE xdsl2LineSegmentEntry OBJECT-TYPE
SYNTAX Xdsl2LineSegmentEntry SYNTAX Xdsl2LineSegmentEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The table xdsl2LineSegmentEntry contains status "The table xdsl2LineSegmentEntry contains status parameters
parameters of VDSL2/ADSL/ADSL2 and ADSL2+ sub-carriers. of VDSL2/ADSL/ADSL2 and ADSL2+ subcarriers.
Objects in the table refer to NSus and NSds. For G.993.2, the Objects in the table refer to NSus and NSds. For G.993.2, the
value of NSus and NSds are respectively the indices value of NSus and NSds are respectively the indices of the
of the highest supported upstream and downstream subcarriers highest supported upstream and downstream subcarriers according
according to the selected implementation profile. For ADSL, to the selected implementation profile. For ADSL, NSus is equal
NSus is equal to NSCus-1 and NSds is equal to NSCds-1. to NSCus-1 and NSds is equal to NSCds-1.
One index of this table is an interface index where the One index of this table is an interface index where the interface
interface has an ifType of vdsl2(xxx). A second index of this has an ifType of vdsl2(xxx). A second index of this table is the
table is the transmission direction. A third index identifies transmission direction. A third index identifies the specific
the specific segment of the sub-carriers status addressed." segment of the subcarriers status addressed."
INDEX { ifIndex, INDEX { ifIndex,
xdsl2LineSegmentDirection, xdsl2LineSegmentDirection,
xdsl2LineSegment } xdsl2LineSegment }
::= { xdsl2LineSegmentTable 1 } ::= { xdsl2LineSegmentTable 1 }
Xdsl2LineSegmentEntry ::= Xdsl2LineSegmentEntry ::=
SEQUENCE { SEQUENCE {
xdsl2LineSegmentDirection Xdsl2Direction, xdsl2LineSegmentDirection Xdsl2Direction,
xdsl2LineSegment Unsigned32, xdsl2LineSegment Unsigned32,
xdsl2LineSegmentBitsAlloc Xdsl2BitsAlloc, xdsl2LineSegmentBitsAlloc Xdsl2BitsAlloc,
xdsl2LineSegmentRowStatus RowStatus xdsl2LineSegmentRowStatus RowStatus
} }
xdsl2LineSegmentDirection OBJECT-TYPE xdsl2LineSegmentDirection OBJECT-TYPE
SYNTAX Xdsl2Direction SYNTAX Xdsl2Direction
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The direction of the sub-carrier either "The direction of the subcarrier either
upstream or downstream" upstream or downstream."
::= { xdsl2LineSegmentEntry 1 } ::= { xdsl2LineSegmentEntry 1 }
xdsl2LineSegment OBJECT-TYPE xdsl2LineSegment OBJECT-TYPE
SYNTAX Unsigned32(1..8) SYNTAX Unsigned32(1..8)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The segment of the sub-carriers "The segment of the subcarriers status information
status information provided by this provided by this row.
row. Status parameters in this table are retrieved in segments.
Status parameters in this table The first segment of the status information is retrieved with
are retrieved in segments. The first segment xdsl2LineSegment=1, the second segment is retrieved with
of the status information is retrieved with xdsl2LineSegment=2, and so on. When a status parameter is
xdsl2LineSegment=1, the second segment retrieved in n segments where n<8) then, for that parameter,
is retrieved with xdsl2LineSegment=2, and GET operations for the remaining segment numbers (n+1 to 8) will
so on. When a status parameter is retrieved respond with a zero-length OCTET STRING."
in n segments where n<8) then, for that
parameter, GET operations for the remaining segment
numbers (n+1 to 8) will respond with a zero length
OCTET STRING."
::= { xdsl2LineSegmentEntry 2 } ::= { xdsl2LineSegmentEntry 2 }
xdsl2LineSegmentBitsAlloc OBJECT-TYPE xdsl2LineSegmentBitsAlloc OBJECT-TYPE
SYNTAX Xdsl2BitsAlloc SYNTAX Xdsl2BitsAlloc
UNITS "bits" UNITS "bits"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The bits allocation per sub-carrier. An array of 256 octets "The bits allocation per subcarrier. An array of 256 octets
(512 nibbles), designed for supporting up to 512 (downstream) (512 nibbles), designed for supporting up to 512 (downstream)
sub-carriers. When more then 512 sub-carriers are supported, subcarriers. When more then 512 subcarriers are supported, the
the status information is reported through multiple (up to 8) status information is reported through multiple (up to 8)
segments. The first segment is then used for the first 512 segments. The first segment is then used for the first 512
sub-carriers. The second segment is used for the sub-carriers subcarriers. The second segment is used for the subcarriers 512 to
512 to 1023 and so on. 1023 and so on.
The aggregate number of utilized nibbles on downstream direction
The aggregate number of utilized nibbles on downstream (in all segments) depends on NSds, and on upstream direction it
direction (in all segments) depends on NSds, and on upstream depends on NSus.
direction it depends on NSus.
This value is referred here as NS. The segment number is in This value is referred here as NS. The segment number is in
xdsl2SCStatusSegment. xdsl2SCStatusSegment.
Nibble i (0 <= i < MIN(NS-(segment-1)*512,512)) in each Nibble i (0 <= i < MIN(NS-(segment-1)*512,512)) in each
segment is set to a value in the range 0 to 15 to indicate that segment is set to a value in the range 0 to 15 to indicate that
the respective downstream or upstream sub-carrier j the respective downstream or upstream subcarrier j
(j=(segement-1)*512+i) has the same amount of bits (j=(segement-1)*512+i) has the same amount of bits
allocation." allocation."
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.29.1 (BITSpsds) REFERENCE "ITU-T G.997.1, paragraph #7.5.1.29.1 (BITSpsds)
and paragraph #7.5.1.29.2 (BITSpsus)" and paragraph #7.5.1.29.2 (BITSpsus)"
::= { xdsl2LineSegmentEntry 3 } ::= { xdsl2LineSegmentEntry 3 }
xdsl2LineSegmentRowStatus OBJECT-TYPE xdsl2LineSegmentRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Row Status. The SNMP manager is not permitted "Row Status. The SNMP manager is not permitted to create rows
to create rows in this table. The SNMP agent will create in this table. The SNMP agent will create a row in this table for
a row in this table for storing the results of a measurement storing the results of a measurement performed on the associated
performed on the associated line, if the row does not line, if the row does not already exist.
already exist.
The SNMP agent may have limited resources; therefore, if The SNMP agent may have limited resources; therefore, if multiple
multiple rows co-exist in this table, it may fail to add rows co-exist in this table, it may fail to add new rows to this
new rows to this table or allocate memory resources. table or allocate memory resources.
If that occurs, the SNMP agent responds with If that occurs, the SNMP agent responds with the value
the value 'noResources' (for 'noResources' (for the xdsl2LineCmndConfBpscFailReason
xdsl2LineCmndConfBpscFailReason object in xdsl2LineTable) object in xdsl2LineTable).
The management system (the operator) may delete rows from this The management system (the operator) may delete rows from this
table according to any scheme. table according to any scheme. E.g., after retrieving the results.
E.g., after retrieving the results.
When the SNMP manager deletes any row in this table, the When the SNMP manager deletes any row in this table, the SNMP
SNMP agent MUST delete all rows in this table that have agent MUST delete all rows in this table that have the same
the same ifIndex value." ifIndex value."
::= { xdsl2LineSegmentEntry 4 } ::= { xdsl2LineSegmentEntry 4 }
------------------------------------------------ ------------------------------------------------
-- xdsl2LineBandTable -- -- xdsl2LineBandTable --
------------------------------------------------ ------------------------------------------------
xdsl2LineBandTable OBJECT-TYPE xdsl2LineBandTable OBJECT-TYPE
SYNTAX SEQUENCE OF Xdsl2LineBandEntry SYNTAX SEQUENCE OF Xdsl2LineBandEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The table xdsl2LineBandTable contains the, "The table xdsl2LineBandTable contains the, per-band line
per-band line status parameters of the VDSL2/ADSL/ADSL2 status parameters of the VDSL2/ADSL/ADSL2 or ADSL2+ line.
or ADSL2+ line.
The indexes of this table consist of an interface index where The indexes of this table consist of an interface index where
the interface has an ifType of vdsl2(xxx), together with a the interface has an ifType of vdsl2(xxx), together with a
per-band index covering both VDSL2 and ADSL/ADSL2/ADSL2+. per-band index covering both VDSL2 and ADSL/ADSL2/ADSL2+.
The parameters in this table are updated at The parameters in this table are updated at line initialisation
line initialisation time and at showtime." time and at showtime."
::= { xdsl2Line 2 } ::= { xdsl2Line 2 }
xdsl2LineBandEntry OBJECT-TYPE xdsl2LineBandEntry OBJECT-TYPE
SYNTAX Xdsl2LineBandEntry SYNTAX Xdsl2LineBandEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The table xdsl2LineBandTable contains the, "The table xdsl2LineBandTable contains the, per-band line
per-band line status parameters of the VDSL2/ADSL/ADSL2 status parameters of the VDSL2/ADSL/ADSL2 or ADSL2+ line."
or ADSL2+ line."
INDEX { ifIndex, xdsl2LineBand } INDEX { ifIndex, xdsl2LineBand }
::= { xdsl2LineBandTable 1 } ::= { xdsl2LineBandTable 1 }
Xdsl2LineBandEntry ::= Xdsl2LineBandEntry ::=
SEQUENCE { SEQUENCE {
xdsl2LineBand Xdsl2Band, xdsl2LineBand Xdsl2Band,
xdsl2LineBandStatusLnAtten Unsigned32, xdsl2LineBandStatusLnAtten Unsigned32,
xdsl2LineBandStatusSigAtten Unsigned32, xdsl2LineBandStatusSigAtten Unsigned32,
xdsl2LineBandStatusSnrMargin Integer32 xdsl2LineBandStatusSnrMargin Integer32
} }
xdsl2LineBand OBJECT-TYPE xdsl2LineBand OBJECT-TYPE
SYNTAX Xdsl2Band SYNTAX Xdsl2Band
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Identifies the band(s) associated with this line. "Identifies the band(s) associated with this line.
For ADSL/ADSL2/ADSL2+ the values upstream(1) and downstream(2) For ADSL/ADSL2/ADSL2+ the values upstream(1) and downstream(2)
will always be present. will always be present.
For VDSL2, a subset of {us0(3), ds1(4), us1(5) ... } For VDSL2, a subset of {us0(3), ds1(4), us1(5) ... } will always
will always be present (See Xdsl2Band for more details) be present (See Xdsl2Band for more details) together with rows for
together with rows for upstream(1) and downstream(2) in upstream(1) and downstream(2) in which only the
which only the xdsl2LineBandStatusSnrMargin attribute is xdsl2LineBandStatusSnrMargin attribute is expected to hold a valid
expected to hold a valid (average) measurement." (average) measurement."
::= { xdsl2LineBandEntry 1 } ::= { xdsl2LineBandEntry 1 }
xdsl2LineBandStatusLnAtten OBJECT-TYPE xdsl2LineBandStatusLnAtten OBJECT-TYPE
SYNTAX Unsigned32 (0..1270 | 2147483646 | 2147483647) SYNTAX Unsigned32 (0..1270 | 2147483646 | 2147483647)
UNITS "0.1 dB" UNITS "0.1 dB"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Line Attenuation. "Line Attenuation.
When referring to a band in the downstream direction, it is When referring to a band in the downstream direction, it is
the measured difference in the total power transmitted by the the measured difference in the total power transmitted by the
xTU-C and the total power received by the xTU-R over all sub- xTU-C and the total power received by the xTU-R over all
carriers of that band during initialization. subcarriers of that band during initialization.
When referring to a band in the upstream direction, it is the When referring to a band in the upstream direction, it is the
measured difference in the total power transmitted by the measured difference in the total power transmitted by the xTU-R
xTU-R and the total power received by the xTU-C over all sub- and the total power received by the xTU-C over all subcarriers of
carriers of that band during initialization. that band during initialization.
Values range from 0 to 1270 in units of 0.1 dB (Physical Values range from 0 to 1270 in units of 0.1 dB (Physical values
values are 0 to 127 dB). are 0 to 127 dB).
A special value of 0x7FFFFFFF (2147483647) indicates the line A special value of 0x7FFFFFFF (2147483647) indicates the line
attenuation is out of range to be represented. attenuation is out of range to be represented.
A special value of 0x7FFFFFFE (2147483646) indicates the line A special value of 0x7FFFFFFE (2147483646) indicates the line
attenuation measurement is unavailable." attenuation measurement is unavailable."
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.9 (LATNds) REFERENCE "ITU-T G.997.1, paragraph #7.5.1.9 (LATNds)
and paragraph #7.5.1.10 (LATNus)6" and paragraph #7.5.1.10 (LATNus)6"
DEFVAL { 2147483646 } DEFVAL { 2147483646 }
::= { xdsl2LineBandEntry 2 } ::= { xdsl2LineBandEntry 2 }
xdsl2LineBandStatusSigAtten OBJECT-TYPE xdsl2LineBandStatusSigAtten OBJECT-TYPE
SYNTAX Unsigned32 (0..1270 | 2147483646 | 2147483647) SYNTAX Unsigned32 (0..1270 | 2147483646 | 2147483647)
UNITS "0.1 dB" UNITS "0.1 dB"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Signal Attenuation. "Signal Attenuation.
When referring to a band in the downstream direction, it is When referring to a band in the downstream direction, it is
the measured difference in the total power transmitted by the the measured difference in the total power transmitted by the
xTU-C and the total power received by the xTU-R over all sub- xTU-C and the total power received by the xTU-R over all
carriers of that band during Showtime. subcarriers of that band during Showtime.
When referring to a band in the upstream direction, it is the When referring to a band in the upstream direction, it is the
measured difference in the total power transmitted by the measured difference in the total power transmitted by the xTU-R
xTU-R and the total power received by the xTU-C over all sub- and the total power received by the xTU-C over all subcarriers of
carriers of that band during Showtime. that band during Showtime.
Values range from 0 to 1270 in units of 0.1 dB (Physical Values range from 0 to 1270 in units of 0.1 dB (Physical values
values are 0 to 127 dB). are 0 to 127 dB).
A special value of 0x7FFFFFFF (2147483647) indicates the line A special value of 0x7FFFFFFF (2147483647) indicates the line
attenuation is out of range to be represented. attenuation is out of range to be represented.
A special value of 0x7FFFFFFE (2147483646) indicates the line A special value of 0x7FFFFFFE (2147483646) indicates the line
attenuation measurement is unavailable." attenuation measurement is unavailable."
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.11 (SATNds) REFERENCE "ITU-T G.997.1, paragraph #7.5.1.11 (SATNds)
and paragraph #7.5.1.12 (SATNus)" and paragraph #7.5.1.12 (SATNus)"
DEFVAL { 2147483646 } DEFVAL { 2147483646 }
::= { xdsl2LineBandEntry 3 } ::= { xdsl2LineBandEntry 3 }
xdsl2LineBandStatusSnrMargin OBJECT-TYPE xdsl2LineBandStatusSnrMargin OBJECT-TYPE
SYNTAX Integer32 (-640..630 | 2147483646 | 2147483647) SYNTAX Integer32 (-640..630 | 2147483646 | 2147483647)
UNITS "0.1 dB" UNITS "0.1 dB"
skipping to change at page 90, line 16 skipping to change at page 89, line 19
DEFVAL { 2147483646 } DEFVAL { 2147483646 }
::= { xdsl2LineBandEntry 3 } ::= { xdsl2LineBandEntry 3 }
xdsl2LineBandStatusSnrMargin OBJECT-TYPE xdsl2LineBandStatusSnrMargin OBJECT-TYPE
SYNTAX Integer32 (-640..630 | 2147483646 | 2147483647) SYNTAX Integer32 (-640..630 | 2147483646 | 2147483647)
UNITS "0.1 dB" UNITS "0.1 dB"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"SNR Margin is the maximum increase in dB of the noise power "SNR Margin is the maximum increase in dB of the noise power
received at the XTU (xTU-R for a band in the downstream received at the xTU (xTU-R for a band in the downstream direction
direction and xTU-C for a band in the upstream direction), and xTU-C for a band in the upstream direction), such that the
such that the BER requirements are met for all bearer channels BER requirements are met for all bearer channels received at the
received at the XTU. Values range from -640 to 630 in units of xTU. Values range from -640 to 630 in units of 0.1 dB (Physical
0.1 dB (Physical values are -64 to 63 dB). values are -64 to 63 dB).
A special value of 0x7FFFFFFF (2147483647) indicates the A special value of 0x7FFFFFFF (2147483647) indicates the SNR
SNR Margin is out of range to be represented. Margin is out of range to be represented.
A special value of 0x7FFFFFFE (2147483646) indicates the A special value of 0x7FFFFFFE (2147483646) indicates the SNR
SNR Margin measurement is currently unavailable." Margin measurement is currently unavailable."
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.13 (SNRMds) REFERENCE "ITU-T G.997.1, paragraph #7.5.1.13 (SNRMds)
and paragraph #7.5.1.14 (SNRMpbds) and paragraph #7.5.1.14 (SNRMpbds)
and paragraph #7.5.1.16 (SNRMus) and paragraph #7.5.1.16 (SNRMus)
and paragraph #7.5.1.17 (SNRMpbus)" and paragraph #7.5.1.17 (SNRMpbus)"
DEFVAL { 2147483646 } DEFVAL { 2147483646 }
::= { xdsl2LineBandEntry 4 } ::= { xdsl2LineBandEntry 4 }
------------------------------------------------ ------------------------------------------------
-- xdsl2ChannelStatusTable -- -- xdsl2ChannelStatusTable --
------------------------------------------------ ------------------------------------------------
skipping to change at page 90, line 50 skipping to change at page 90, line 4
"The table xdsl2ChannelStatusTable contains status "The table xdsl2ChannelStatusTable contains status
parameters of VDSL2/ADSL/ADSL2 or ADSL2+ channel. parameters of VDSL2/ADSL/ADSL2 or ADSL2+ channel.
This table contains live data from equipment. " This table contains live data from equipment. "
::= { xdsl2Status 2 } ::= { xdsl2Status 2 }
xdsl2ChannelStatusEntry OBJECT-TYPE xdsl2ChannelStatusEntry OBJECT-TYPE
SYNTAX Xdsl2ChannelStatusEntry SYNTAX Xdsl2ChannelStatusEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The table xdsl2ChannelStatusTable contains status "The table xdsl2ChannelStatusTable contains status parameters
parameters of VDSL2/ADSL/ADSL2 or ADSL2+ channel. of VDSL2/ADSL/ADSL2 or ADSL2+ channel.
The index of this table is an interface index where the interface
The index of this table is an interface index where has an ifType value that is applicable for a DSL channel and the
the interface has an ifType value that is applicable termination unit."
for a DSL channel and the termination unit."
INDEX { ifIndex, xdsl2ChStatusUnit } INDEX { ifIndex, xdsl2ChStatusUnit }
::= { xdsl2ChannelStatusTable 1 } ::= { xdsl2ChannelStatusTable 1 }
Xdsl2ChannelStatusEntry ::= Xdsl2ChannelStatusEntry ::=
SEQUENCE { SEQUENCE {
xdsl2ChStatusUnit Xdsl2Unit, xdsl2ChStatusUnit Xdsl2Unit,
xdsl2ChStatusActDataRate Unsigned32, xdsl2ChStatusActDataRate Unsigned32,
xdsl2ChStatusPrevDataRate Unsigned32, xdsl2ChStatusPrevDataRate Unsigned32,
xdsl2ChStatusActDelay Unsigned32, xdsl2ChStatusActDelay Unsigned32,
xdsl2ChStatusActInp Unsigned32, xdsl2ChStatusActInp Unsigned32,
skipping to change at page 91, line 38 skipping to change at page 90, line 39
xdsl2ChStatusUnit OBJECT-TYPE xdsl2ChStatusUnit OBJECT-TYPE
SYNTAX Xdsl2Unit SYNTAX Xdsl2Unit
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The termination unit xtuc(1) or xtur(2)." "The termination unit xtuc(1) or xtur(2)."
::= { xdsl2ChannelStatusEntry 1 } ::= { xdsl2ChannelStatusEntry 1 }
xdsl2ChStatusActDataRate OBJECT-TYPE xdsl2ChStatusActDataRate OBJECT-TYPE
SYNTAX Unsigned32(0..200000000) SYNTAX Unsigned32
UNITS "bits/second" UNITS "bits/second"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The actual net data rate that the bearer channel is "The actual net data rate that the bearer channel is
operating operating at, if in L0 power management state. In L1 or L2
at, if in L0 power management state. In L1 or L2 states, it states, it relates to the previous L0 state. The data rate is
relates to the previous L0 state. The data rate is coded in coded in bit/s."
bit/s." REFERENCE "ITU-T G.997.1, paragraph #7.5.2.1
REFERENCE "ITU-T G.997.1, paragraph #7.5.2.1" (Actual data rate)"
DEFVAL { 0 } DEFVAL { 0 }
::= { xdsl2ChannelStatusEntry 2 } ::= { xdsl2ChannelStatusEntry 2 }
xdsl2ChStatusPrevDataRate OBJECT-TYPE xdsl2ChStatusPrevDataRate OBJECT-TYPE
SYNTAX Unsigned32(0..200000000) SYNTAX Unsigned32
UNITS "bits/second" UNITS "bits/second"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The previous net data rate that the bearer channel was "The previous net data rate that the bearer channel was
operating at just before the latest rate change event. This operating at just before the latest rate change event. This
could be a full or short initialization, fast retrain, DRA or could be a full or short initialization, fast retrain, DRA or
power management transitions, excluding transitions between L0 power management transitions, excluding transitions between L0
state and L1 or L2 states. The data rate is coded in state and L1 or L2 states. The data rate is coded in
bit/s." bit/s."
REFERENCE "ITU-T G.997.1, paragraph #7.5.2.2" REFERENCE "ITU-T G.997.1, paragraph #7.5.2.2
(Previous data rate)"
DEFVAL { 0 } DEFVAL { 0 }
::= { xdsl2ChannelStatusEntry 3 } ::= { xdsl2ChannelStatusEntry 3 }
xdsl2ChStatusActDelay OBJECT-TYPE xdsl2ChStatusActDelay OBJECT-TYPE
SYNTAX Unsigned32(0..8176) SYNTAX Unsigned32(0..8176)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The actual one-way interleaving delay introduced by the "The actual one-way interleaving delay introduced by the
PMS-TC in the direction of the bearer channel, if in L0 PMS-TC in the direction of the bearer channel, if in L0 power
power management state. In L1 or L2 states, it relates to management state. In L1 or L2 states, it relates to the previous
the previous L0 state. It is coded in ms (rounded to the L0 state. It is coded in ms (rounded to the nearest ms)."
nearest ms)." REFERENCE "ITU-T G.997.1, paragraph #7.5.2.3
REFERENCE "ITU-T G.997.1, paragraph #7.5.2.3" (Actual interleaving delay)"
DEFVAL { 0 } DEFVAL { 0 }
::= { xdsl2ChannelStatusEntry 4 } ::= { xdsl2ChannelStatusEntry 4 }
xdsl2ChStatusActInp OBJECT-TYPE xdsl2ChStatusActInp OBJECT-TYPE
SYNTAX Unsigned32(0..255) SYNTAX Unsigned32(0..255)
UNITS "0.1 symbols" UNITS "0.1 symbols"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"(ACTINP) "Actual impulse noise protection.
Actual impulse noise protection. This parameter reports the actual impulse noise protection (INP)
This parameter reports the actual impulse noise on the bearer channel in the L0 state. In the L1 or L2 state, the
protection (INP) on the bearer channel in the L0 parameter contains the INP in the previous L0 state. For ADSL,
state. In the L1 or L2 state, the parameter contains the this value is computed according to the formula specified in the
INP in the previous L0 state. For ADSL, this value is relevant Recommendation based on the actual framing parameters.
computed according to the formula specified in the For ITU-T Rec. G.993.2, the method to report this value is
relevant Recommendation based on the actual framing according to the INPREPORT parameter. The value is coded in
parameters. For ITU-T Rec. G.993.2, the method to fractions of DMT symbols with a granularity of 0.1 symbols.
report this value is according to the INPREPORT The range is from 0 to 25.4. The special value of 255 indicates
parameter. The value is coded in fractions of DMT an ACTINP higher than 25.4."
symbols with a granularity of 0.1 symbols. REFERENCE "ITU-T G.997.1, paragraph #7.5.2.4 (ACTINP)"
The range is from 0 to 25.4. The special value
of 255 indicates an ACTINP higher than 25.4."
REFERENCE "ITU-T G.997.1, paragraph #7.5.2.4"
DEFVAL { 0 } DEFVAL { 0 }
::= { xdsl2ChannelStatusEntry 5 } ::= { xdsl2ChannelStatusEntry 5 }
xdsl2ChStatusInpReport OBJECT-TYPE xdsl2ChStatusInpReport OBJECT-TYPE
SYNTAX Xdsl2ChInpReport SYNTAX Xdsl2ChInpReport
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"(INPREPORT) "Impulse noise protection reporting mode.
Impulse noise protection reporting mode. This parameter reports the method used to compute the ACTINP. If
This parameter reports the method used to compute set to inpComputedUsingFormula(1), the ACTINP is computed
the ACTINP. If set to inpComputedUsingFormula(1), according to the INP_no_erasure formula (9.6/G.993.2). If set to
the ACTINP is computed according to the INP_no_erasure inpEstimatedByXtur(2), the ACTINP is the value estimated by the
formula (9.6/G.993.2). If set to inpEstimatedByXtur(2), xTU receiver."
the ACTINP is the value estimated by the xTU receiver." REFERENCE "ITU-T G.997.1 Amendment 1, paragraph #7.5.2.5
REFERENCE "ITU-T G.997.1 Amendment 1, paragraph #7.5.2.5" (INPREPORT)"
DEFVAL { inpComputedUsingFormula } DEFVAL { inpComputedUsingFormula }
::= { xdsl2ChannelStatusEntry 6 } ::= { xdsl2ChannelStatusEntry 6 }
xdsl2ChStatusNFec OBJECT-TYPE xdsl2ChStatusNFec OBJECT-TYPE
SYNTAX Unsigned32(0..255) SYNTAX Unsigned32(0..255)
UNITS "bytes" UNITS "bytes"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"(NFEC) "Actual size of Reed-Solomon codeword.
Actual size of Reed-Solomon codeword.
This parameter reports the actual number of Reed-Solomon This parameter reports the actual number of Reed-Solomon
redundancy bytes per codeword used in the latency path redundancy bytes per codeword used in the latency path in which
in which the bearer channel is transported. The value is the bearer channel is transported. The value is coded in bytes.
coded in bytes. It ranges from 0 to 16. It ranges from 0 to 16.
The value 0 indicates no Reed-Solomon coding." The value 0 indicates no Reed-Solomon coding."
REFERENCE "ITU-T G.997.1, paragraph #7.5.2.6.1" REFERENCE "ITU-T G.997.1, paragraph #7.5.2.6.1 (NFEC)"
DEFVAL { 0 } DEFVAL { 0 }
::= { xdsl2ChannelStatusEntry 7 } ::= { xdsl2ChannelStatusEntry 7 }
xdsl2ChStatusRFec OBJECT-TYPE xdsl2ChStatusRFec OBJECT-TYPE
SYNTAX Unsigned32(0..16) SYNTAX Unsigned32(0..16)
UNITS "bits" UNITS "bits"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"(RFEC) "Actual number of Reed-Solomon redundancy bytes.
Actual number of Reed-Solomon redundancy bytes.
This parameter reports the actual number of Reed-Solomon This parameter reports the actual number of Reed-Solomon
redundancy bytes per codeword used in the latency path redundancy bytes per codeword used in the latency path in which
in which the bearer channel is transported. The value is the bearer channel is transported. The value is coded in bytes.
coded in bytes. It ranges from 0 to 16. It ranges from 0 to 16.
The value 0 indicates no Reed-Solomon coding." The value 0 indicates no Reed-Solomon coding."
REFERENCE "ITU-T G.997.1, paragraph #7.5.2.6.2" REFERENCE "ITU-T G.997.1, paragraph #7.5.2.6.2 (RFEC)"
DEFVAL { 0 } DEFVAL { 0 }
::= { xdsl2ChannelStatusEntry 8 } ::= { xdsl2ChannelStatusEntry 8 }
xdsl2ChStatusLSymb OBJECT-TYPE xdsl2ChStatusLSymb OBJECT-TYPE
SYNTAX Unsigned32(0..65535) SYNTAX Unsigned32(0..65535)
UNITS "bits" UNITS "bits"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"(LSYMB) "Actual number of bits per symbol.
Actual number of bits per symbol. This parameter reports the actual number of bits per symbol
This parameter reports the actual number of bits per assigned to the latency path in which the bearer channel is
symbol assigned to the latency path in which the bearer transported. This value does not include trellis overhead. The
channel is transported. This value does not include value is coded in bits.
trellis overhead. The value is coded in bits.
It ranges from 0 to 65535." It ranges from 0 to 65535."
REFERENCE "ITU-T G.997.1, paragraph #7.5.2.6.3" REFERENCE "ITU-T G.997.1, paragraph #7.5.2.6.3 (LSYMB)"
DEFVAL { 0 } DEFVAL { 0 }
::= { xdsl2ChannelStatusEntry 9 } ::= { xdsl2ChannelStatusEntry 9 }
xdsl2ChStatusIntlvDepth OBJECT-TYPE xdsl2ChStatusIntlvDepth OBJECT-TYPE
SYNTAX Unsigned32(1..4096) SYNTAX Unsigned32(1..4096)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"(INTLVDEPTH) "Actual interleaving depth.
Actual interleaving depth. This parameter reports the actual depth of the interleaver used
This parameter reports the actual depth of the interleaver in the latency path in which the bearer channel is transported.
used in the latency path in which the bearer channel is The value ranges from 1 to 4096 in steps of 1.
transported. The value ranges from 1 to 4096 in steps of 1.
The value 1 indicates no interleaving." The value 1 indicates no interleaving."
REFERENCE "ITU-T G.997.1, paragraph #7.5.2.6.4" REFERENCE "ITU-T G.997.1, paragraph #7.5.2.6.4 (INTLVDEPTH)
"
DEFVAL { 1 } DEFVAL { 1 }
::= { xdsl2ChannelStatusEntry 10 } ::= { xdsl2ChannelStatusEntry 10 }
xdsl2ChStatusIntlvBlock OBJECT-TYPE xdsl2ChStatusIntlvBlock OBJECT-TYPE
SYNTAX Unsigned32(4..255) SYNTAX Unsigned32(4..255)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"(INTLVBLOCK) "Actual interleaving block length.
Actual interleaving block length. This parameter reports the actual block length of the interleaver
This parameter reports the actual block length of the used in the latency path in which the bearer channel is
interleaver used in the latency path in which the bearer transported.
channel is transported.
The value ranges from 4 to 255 in steps of 1." The value ranges from 4 to 255 in steps of 1."
REFERENCE "ITU-T G.997.1, paragraph #7.5.2.6.5" REFERENCE "ITU-T G.997.1, paragraph #7.5.2.6.5 (INTLVBLOCK)
"
DEFVAL { 4 } DEFVAL { 4 }
::= { xdsl2ChannelStatusEntry 11 } ::= { xdsl2ChannelStatusEntry 11 }
xdsl2ChStatusLPath OBJECT-TYPE xdsl2ChStatusLPath OBJECT-TYPE
SYNTAX Unsigned32(0..3) SYNTAX Unsigned32(0..3)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"(LPATH) "Actual latency path.
Actual latency path. This parameter reports the index of the actual latency path in
This parameter reports the index of the actual latency which the bearer is transported.
path in which the bearer is transported.
The valid values are 0, 1, 2 and 3. The valid values are 0, 1, 2 and 3.
For G.992.1, the FAST path shall be mapped to the latency For G.992.1, the FAST path shall be mapped to the latency
index 0, and the INTERLEAVED path shall be mapped to the index 0, and the INTERLEAVED path shall be mapped to the latency
latency index 1." index 1."
REFERENCE "ITU-T G.997.1 amendment 1, paragraph #7.5.2.7" REFERENCE "ITU-T G.997.1 amendment 1, paragraph #7.5.2.7
(LPATH)"
DEFVAL { 0 } DEFVAL { 0 }
::= { xdsl2ChannelStatusEntry 12 } ::= { xdsl2ChannelStatusEntry 12 }
xdsl2ChStatusAtmStatus OBJECT-TYPE xdsl2ChStatusAtmStatus OBJECT-TYPE
SYNTAX Xdsl2ChAtmStatus SYNTAX Xdsl2ChAtmStatus
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates current state (existing failures) of the DSL "Indicates current state (existing failures) of the DSL
channel in case its Data Path is ATM. This is a bit-map of channel in case its Data Path is ATM. This is a bit-map of
possible conditions. The various bit positions are: possible conditions. The various bit positions are:
noDefect (0), noDefect (0),
noCellDelineation(1), noCellDelineation(1),
lossOfCellDelineation (2). lossOfCellDelineation (2).
In case the channel is not of ATM Data Path the object is set In case the channel is not of ATM Data Path the object is set
to '0'." to '0'."
REFERENCE "ITU-T G.997.1, paragraph #7.1.4" REFERENCE "ITU-T G.997.1, paragraph #7.1.4
(ATM data path failures)"
DEFVAL { { noDefect } } DEFVAL { { noDefect } }
::= { xdsl2ChannelStatusEntry 13 } ::= { xdsl2ChannelStatusEntry 13 }
xdsl2ChStatusPtmStatus OBJECT-TYPE xdsl2ChStatusPtmStatus OBJECT-TYPE
SYNTAX Xdsl2ChPtmStatus SYNTAX Xdsl2ChPtmStatus
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates current state (existing failures) of the DSL "Indicates current state (existing failures) of the DSL
channel in case its Data Path is PTM (Packet Transfer Mode). channel in case its Data Path is PTM (Packet Transfer Mode).
skipping to change at page 96, line 4 skipping to change at page 94, line 49
DEFVAL { { noDefect } } DEFVAL { { noDefect } }
::= { xdsl2ChannelStatusEntry 13 } ::= { xdsl2ChannelStatusEntry 13 }
xdsl2ChStatusPtmStatus OBJECT-TYPE xdsl2ChStatusPtmStatus OBJECT-TYPE
SYNTAX Xdsl2ChPtmStatus SYNTAX Xdsl2ChPtmStatus
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates current state (existing failures) of the DSL "Indicates current state (existing failures) of the DSL
channel in case its Data Path is PTM (Packet Transfer Mode). channel in case its Data Path is PTM (Packet Transfer Mode).
This is a bit-map of possible conditions. The various bit This is a bit-map of possible conditions. The various bit
positions are: positions are:
noDefect (0), noDefect (0),
outOfSync (1). outOfSync (1).
In case the channel is not of PTM Data Path the object is set In case the channel is not of PTM Data Path the object is set
to '0'." to '0'."
REFERENCE "ITU-T G.997.1, paragraph #7.1.5" REFERENCE "ITU-T G.997.1, paragraph #7.1.5
(PTM Data Path failures)"
DEFVAL { { noDefect } } DEFVAL { { noDefect } }
::= { xdsl2ChannelStatusEntry 14 } ::= { xdsl2ChannelStatusEntry 14 }
------------------------------------------------ ------------------------------------------------
-- Scalars that relate to the SC Status Tables -- Scalars that relate to the SC Status Tables
------------------------------------------------ ------------------------------------------------
xdsl2ScalarSCMaxInterfaces OBJECT-TYPE xdsl2ScalarSCMaxInterfaces OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 96, line 49 skipping to change at page 95, line 46
------------------------------------------------ ------------------------------------------------
-- xdsl2SCStatusTable -- -- xdsl2SCStatusTable --
------------------------------------------------ ------------------------------------------------
xdsl2SCStatusTable OBJECT-TYPE xdsl2SCStatusTable OBJECT-TYPE
SYNTAX SEQUENCE OF Xdsl2SCStatusEntry SYNTAX SEQUENCE OF Xdsl2SCStatusEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The table xdsl2SCStatusTable contains "The table xdsl2SCStatusTable contains
sub-carrier status parameters for VDSL2/ADSL/ADSL2 subcarrier status parameters for VDSL2/ADSL/ADSL2 and ADSL2+ that
and ADSL2+ that DO NOT refer to specific sub-carriers. DO NOT refer to specific subcarriers.
In addition, the table contains parameters In addition, the table contains parameters that provide
that provide information about the size of parameters information about the size of parameters in
in xdsl2SCStatusSegmentTable. xdsl2SCStatusSegmentTable.
The parameters in this table MUST be updated after
a loop diagnostic procedure and MAY be updated after The parameters in this table MUST be updated after a loop
a line initialisation and MAY be updated at showtime." diagnostic procedure and MAY be updated after a line
initialisation and MAY be updated at showtime."
::= { xdsl2Status 3 } ::= { xdsl2Status 3 }
xdsl2SCStatusEntry OBJECT-TYPE xdsl2SCStatusEntry OBJECT-TYPE
SYNTAX Xdsl2SCStatusEntry SYNTAX Xdsl2SCStatusEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The table xdsl2SCStatusTable contains sub-carrier "The table xdsl2SCStatusTable contains subcarrier status
status parameters for VDSL2/ADSL/ADSL2 and ADSL2+ parameters for VDSL2/ADSL/ADSL2 and ADSL2+ that DO NOT refer to
that DO NOT refer to specific sub-carriers. In addition, the specific subcarriers. In addition, the table contains parameters
table contains parameters that provide information about the that provide information about the size of parameters in
size of parameters in xdsl2SCStatusSegmentTable. xdsl2SCStatusSegmentTable.
One index of this table is an interface index where the One index of this table is an interface index where the interface
interface has an ifType of vdsl2(xxx). A second index of this has an ifType of vdsl2(xxx). A second index of this table is the
table is the transmission direction." transmission direction."
INDEX { ifIndex, xdsl2SCStatusDirection } INDEX { ifIndex, xdsl2SCStatusDirection }
::= { xdsl2SCStatusTable 1 } ::= { xdsl2SCStatusTable 1 }
Xdsl2SCStatusEntry ::= Xdsl2SCStatusEntry ::=
SEQUENCE { SEQUENCE {
xdsl2SCStatusDirection Xdsl2Direction, xdsl2SCStatusDirection Xdsl2Direction,
xdsl2SCStatusLinScale Unsigned32, xdsl2SCStatusLinScale Unsigned32,
xdsl2SCStatusLinScGroupSize Unsigned32, xdsl2SCStatusLinScGroupSize Unsigned32,
xdsl2SCStatusLogMt Unsigned32, xdsl2SCStatusLogMt Unsigned32,
xdsl2SCStatusLogScGroupSize Unsigned32, xdsl2SCStatusLogScGroupSize Unsigned32,
skipping to change at page 97, line 47 skipping to change at page 96, line 46
xdsl2SCStatusSnrScGroupSize Unsigned32, xdsl2SCStatusSnrScGroupSize Unsigned32,
xdsl2SCStatusAttainableRate Unsigned32, xdsl2SCStatusAttainableRate Unsigned32,
xdsl2SCStatusRowStatus RowStatus xdsl2SCStatusRowStatus RowStatus
} }
xdsl2SCStatusDirection OBJECT-TYPE xdsl2SCStatusDirection OBJECT-TYPE
SYNTAX Xdsl2Direction SYNTAX Xdsl2Direction
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The direction of the sub-carrier either "The direction of the subcarrier either
upstream or downstream" upstream or downstream."
::= { xdsl2SCStatusEntry 1 } ::= { xdsl2SCStatusEntry 1 }
xdsl2SCStatusLinScale OBJECT-TYPE xdsl2SCStatusLinScale OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32 (1..65535)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The scale factor to be applied to the H(f) linear "The scale factor to be applied to the H(f) linear
representation values for the respective transmission direction. representation values for the respective transmission direction.
This parameter is only available after a loop diagnostic This parameter is only available after a loop diagnostic
procedure." procedure. It is represented as an unsigned integer in the range
from 1 to 2^16-1."
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.26.1 (HLINSCds) REFERENCE "ITU-T G.997.1, paragraph #7.5.1.26.1 (HLINSCds)
and paragraph #7.5.1.26.7 (HLINSCus)" and paragraph #7.5.1.26.7 (HLINSCus)"
::= { xdsl2SCStatusEntry 2 } ::= { xdsl2SCStatusEntry 2 }
xdsl2SCStatusLinScGroupSize OBJECT-TYPE xdsl2SCStatusLinScGroupSize OBJECT-TYPE
SYNTAX Unsigned32(1 | 2 | 4 | 8) SYNTAX Unsigned32(1 | 2 | 4 | 8)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of sub-carriers per group used to report the H(f) "Number of subcarriers per group used to report the H(f)
linear representation values for the respective transmission linear representation values for the respective transmission
direction. The valid values are 1, 2, 4 and 8. For ADSL, this direction. The valid values are 1, 2, 4 and 8. For ADSL, this
parameter is equal to one and, for VDSL2, it is equal to the parameter is equal to one and, for VDSL2, it is equal to the size
size of a sub-carrier group used to compute these parameters. of a subcarrier group used to compute these parameters.
This parameter is only available after a loop diagnostic This parameter is only available after a loop diagnostic
procedure." procedure."
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.26.2 (HLINGds) REFERENCE "ITU-T G.997.1, paragraph #7.5.1.26.2 (HLINGds)
and paragraph #7.5.1.26.8 (HLINGus)" and paragraph #7.5.1.26.8 (HLINGus)"
::= { xdsl2SCStatusEntry 3 } ::= { xdsl2SCStatusEntry 3 }
xdsl2SCStatusLogMt OBJECT-TYPE xdsl2SCStatusLogMt OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32 (1..65535)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This parameter contains the number of symbols used to "This parameter contains the number of symbols used to
measure the Hlog(f) values. It is represented as measure the Hlog(f) values. It is represented as an unsigned
an unsigned integer in the range from 1 to 2^16-1. integer in the range from 1 to 2^16-1.
After a loop diagnostic procedure, this parameter shall After a loop diagnostic procedure, this parameter shall contain
contain the number of symbols used to measure the the number of symbols used to measure the Hlog(f). It should
Hlog(f). It should correspond to the value specified in the correspond to the value specified in the Recommendation (e.g., the
Recommendation (e.g., the number of symbols in 1 s time number of symbols in 1 s time interval for ITU-T Rec.
interval for ITU-T Rec. G.992.3)." G.992.3)."
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.26.4 (HLOGMTds) REFERENCE "ITU-T G.997.1, paragraph #7.5.1.26.4 (HLOGMTds)
and paragraph #7.5.1.26.10 (HLOGMTus)" and paragraph #7.5.1.26.10 (HLOGMTus)"
::= { xdsl2SCStatusEntry 4 } ::= { xdsl2SCStatusEntry 4 }
xdsl2SCStatusLogScGroupSize OBJECT-TYPE xdsl2SCStatusLogScGroupSize OBJECT-TYPE
SYNTAX Unsigned32(1 | 2 | 4 | 8) SYNTAX Unsigned32(1 | 2 | 4 | 8)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of sub-carriers per group used to report the H(f) "Number of subcarriers per group used to report the H(f)
logarithmic representation values for the respective logarithmic representation values for the respective
transmission direction. The valid values are 1, 2, 4 and 8. transmission direction. The valid values are 1, 2, 4 and 8.
For ADSL, this parameter is equal to one and, for VDSL2, it is For ADSL, this parameter is equal to one and, for VDSL2, it is
equal to the size of a sub-carrier group used to compute these equal to the size of a subcarrier group used to compute these
parameters." parameters."
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.26.5 (HLOGGds) REFERENCE "ITU-T G.997.1, paragraph #7.5.1.26.5 (HLOGGds)
and paragraph #7.5.1.26.11 (HLOGGus)" and paragraph #7.5.1.26.11 (HLOGGus)"
::= { xdsl2SCStatusEntry 5 } ::= { xdsl2SCStatusEntry 5 }
xdsl2SCStatusQlnMt OBJECT-TYPE xdsl2SCStatusQlnMt OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32 (1..65535)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This parameter contains the number of symbols used to "This parameter contains the number of symbols used to
measure the QLN(f) values. It is an unsigned integer measure the QLN(f) values. It is an unsigned integer in the range
in the range from 1 to 2^16-1. After a loop diagnostic from 1 to 2^16-1. After a loop diagnostic procedure, this
procedure, this parameter shall contain the number of symbols parameter shall contain the number of symbols used to measure the
used to measure the QLN(f). It should correspond to the value QLN(f). It should correspond to the value specified in the
specified in the Recommendation (e.g., the number of symbols Recommendation (e.g., the number of symbols in 1 s time interval
in 1 s time interval for ITU-T Rec. G.992.3)." for ITU-T Rec. G.992.3)."
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.27.1 (QLNMTds) REFERENCE "ITU-T G.997.1, paragraph #7.5.1.27.1 (QLNMTds)
and paragraph #7.5.1.27.4 (QLNMTus)" and paragraph #7.5.1.27.4 (QLNMTus)"
::= { xdsl2SCStatusEntry 6 } ::= { xdsl2SCStatusEntry 6 }
xdsl2SCStatusQlnScGroupSize OBJECT-TYPE xdsl2SCStatusQlnScGroupSize OBJECT-TYPE
SYNTAX Unsigned32(1 | 2 | 4 | 8) SYNTAX Unsigned32(1 | 2 | 4 | 8)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of sub-carriers per group used to report the Quiet "Number of subcarriers per group used to report the Quiet
Line Noise values for the respective transmission direction. Line Noise values for the respective transmission direction.
The valid values are 1, 2, 4 and 8. The valid values are 1, 2, 4 and 8.
For ADSL, this parameter is equal to one and, for VDSL2, it is For ADSL, this parameter is equal to one and, for VDSL2, it is
equal to the size of a sub-carrier group used to compute these equal to the size of a subcarrier group used to compute these
parameters." parameters."
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.27.2 (QLNGds) REFERENCE "ITU-T G.997.1, paragraph #7.5.1.27.2 (QLNGds)
and paragraph #7.5.1.27.5 (QLNGus)" and paragraph #7.5.1.27.5 (QLNGus)"
::= { xdsl2SCStatusEntry 7 } ::= { xdsl2SCStatusEntry 7 }
xdsl2SCStatusSnrMtime OBJECT-TYPE xdsl2SCStatusSnrMtime OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32 (1..65535)
UNITS "symbols" UNITS "symbols"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This parameter contains the number of symbols used "This parameter contains the number of symbols used to measure
to measure the SNR(f) values. It is an unsigned the SNR(f) values. It is an unsigned integer in the range from 1
integer in the range from 1 to 2^16-1. After a loop to 2^16-1. After a loop diagnostic procedure, this parameter shall
diagnostic procedure, this parameter shall contain the contain the number of symbols used to measure the SNR(f).
number of symbols used to measure the SNR(f). It should correspond to the value specified in the Recommendation
It should correspond to the value specified in the (e.g., the number of symbols in 1 s time interval for ITU-T Rec.
Recommendation (e.g., the number of symbols in 1 s time G.992.3)."
interval for ITU-T Rec. G.992.3)."
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.28.1 (SNRMTds) REFERENCE "ITU-T G.997.1, paragraph #7.5.1.28.1 (SNRMTds)
and paragraph #7.5.1.28.4 (SNRMTus)" and paragraph #7.5.1.28.4 (SNRMTus)"
::= { xdsl2SCStatusEntry 8 } ::= { xdsl2SCStatusEntry 8 }
xdsl2SCStatusSnrScGroupSize OBJECT-TYPE xdsl2SCStatusSnrScGroupSize OBJECT-TYPE
SYNTAX Unsigned32(1 | 2 | 4 | 8) SYNTAX Unsigned32(1 | 2 | 4 | 8)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of sub-carriers per group used to report the SNR "Number of subcarriers per group used to report the SNR values
values on the respective transmission direction. on the respective transmission direction.
The valid values are 1, 2, 4 and 8. The valid values are 1, 2, 4 and 8.
For ADSL, this parameter is equal to one and, for VDSL2, it is For ADSL, this parameter is equal to one and, for VDSL2, it is
equal to the size of a sub-carrier group used to compute these equal to the size of a subcarrier group used to compute these
parameters." parameters."
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.28.2 (SNRGds) REFERENCE "ITU-T G.997.1, paragraph #7.5.1.28.2 (SNRGds)
and paragraph #7.5.1.28.5 (SNRGus)" and paragraph #7.5.1.28.5 (SNRGus)"
::= { xdsl2SCStatusEntry 9 } ::= { xdsl2SCStatusEntry 9 }
xdsl2SCStatusAttainableRate OBJECT-TYPE xdsl2SCStatusAttainableRate OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "bits/second" UNITS "bits/second"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Maximum Attainable Data Rate. The maximum net data rate "Maximum Attainable Data Rate. The maximum net data rate
currently attainable by the XTU-C transmitter and XTU-R currently attainable by the xTU-C transmitter and xTU-R receiver
receiver (when referring to downstream direction) or by the (when referring to downstream direction) or by the xTU-R
XTU-R transmitter and XTU-C receiver (when referring to transmitter and xTU-C receiver (when referring to upstream
upstream direction). Value is coded in bits/s. direction). Value is coded in bits/s.
This object reflects the value of the parameter following the This object reflects the value of the parameter following the
most recent DELT performed on the associated line. Once most recent DELT performed on the associated line. Once the DELT
the DELT process is over, the parameter no longer changes process is over, the parameter no longer changes until the row is
until the row is deleted or a new DELT process is initiated. deleted or a new DELT process is initiated.
" "
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.19 (ATTNDRds) REFERENCE "ITU-T G.997.1, paragraph #7.5.1.19 (ATTNDRds)
and paragraph #7.5.1.20 (ATTNDRus)" and paragraph #7.5.1.20 (ATTNDRus)"
::= { xdsl2SCStatusEntry 10 } ::= { xdsl2SCStatusEntry 10 }
xdsl2SCStatusRowStatus OBJECT-TYPE xdsl2SCStatusRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Row Status. The SNMP manager is not permitted "Row Status. The SNMP manager is not permitted to create rows
to create rows in this table. The SNMP agent will create in this table. The SNMP agent will create a row in this table for
a row in this table for storing the results of a DELT storing the results of a DELT performed on the associated line, if
performed on the associated line, if the row does not the row does not already exist.
already exist.
When a row is created in this table, the SNMP agent should When a row is created in this table, the SNMP agent should also
also create corresponding rows in the tables create corresponding rows in the tables xdsl2SCStatusBandTable and
xdsl2SCStatusBandTable and xdsl2SCStatusSegmentTable. xdsl2SCStatusSegmentTable.
When a row is deleted in this table, the SNMP agent should When a row is deleted in this table, the SNMP agent should also
also delete corresponding rows in the tables delete corresponding rows in the tables xdsl2SCStatusBandTable and
xdsl2SCStatusBandTable and xdsl2SCStatusSegmentTable. xdsl2SCStatusSegmentTable.
The SNMP agent may have limited resources; therefore, if The SNMP agent may have limited resources; therefore, if multiple
multiple rows co-exist in this table, it may fail to add rows co-exist in this table, it may fail to add new rows to this
new rows to this table or allocate memory resources for table or allocate memory resources for a new DELT process. If
a new DELT process. If that occurs, the SNMP agent responds that occurs, the SNMP agent responds with either the value
with either the value 'tableFull' or the value 'tableFull' or the value 'noResources' (for
'noResources' (for xdsl2LineCmndConfLdsfFailReason the xdsl2LineCmndConfLdsfFailReason object in xdsl2LineTable).
object in xdsl2LineTable)
The management system (the operator) may delete rows from this The management system (the operator) may delete rows from this
table according to any scheme. table according to any scheme. E.g., after retrieving the
E.g., after retrieving the results." results."
::= { xdsl2SCStatusEntry 11 } ::= { xdsl2SCStatusEntry 11 }
------------------------------------------------ ------------------------------------------------
-- xdsl2SCStatusBandTable -- -- xdsl2SCStatusBandTable --
------------------------------------------------ ------------------------------------------------
xdsl2SCStatusBandTable OBJECT-TYPE xdsl2SCStatusBandTable OBJECT-TYPE
SYNTAX SEQUENCE OF Xdsl2SCStatusBandEntry SYNTAX SEQUENCE OF Xdsl2SCStatusBandEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The table xdsl2SCStatusBandTable contains "The table xdsl2SCStatusBandTable contains subcarrier status
sub-carrier status parameters for VDSL2/ADSL/ADSL2 parameters for VDSL2/ADSL/ADSL2 and ADSL2+ that are grouped per-
and ADSL2+ that are grouped per-band. band.
For ADSL/ADSL2/ADSL2+, there is a single For ADSL/ADSL2/ADSL2+, there is a single upstream band and a
upstream band and a single downstream band. single downstream band. For VDSL2, there are several downstream
For VDSL2, there are several downstream bands and bands and several upstream bands.
several upstream bands. The parameters in this table are only available after a loop
The parameters in this table are only available after diagnostic procedure."
a loop diagnostic procedure."
::= { xdsl2Status 4 } ::= { xdsl2Status 4 }
xdsl2SCStatusBandEntry OBJECT-TYPE xdsl2SCStatusBandEntry OBJECT-TYPE
SYNTAX Xdsl2SCStatusBandEntry SYNTAX Xdsl2SCStatusBandEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The table xdsl2SCStatusBandTable contains "The table xdsl2SCStatusBandTable contains subcarrier status
sub-carrier status parameters for VDSL2/ADSL/ADSL2 parameters for VDSL2/ADSL/ADSL2 and ADSL2+ that are grouped per-
and ADSL2+ that are grouped per-band. band.
For ADSL/ADSL2/ADSL2+, there is a single For ADSL/ADSL2/ADSL2+, there is a single upstream band and a
upstream band and a single downstream band. single downstream band.
For VDSL2, there are several downstream bands and For VDSL2, there are several downstream bands and several
several upstream bands. upstream bands.
One index of this table is an interface index where the One index of this table is an interface index where the interface
interface has an ifType of vdsl2(xxx). A second index of this has an ifType of vdsl2(xxx). A second index of this table is
table is transmission band." transmission band."
INDEX { ifIndex, xdsl2SCStatusBand } INDEX { ifIndex, xdsl2SCStatusBand }
::= { xdsl2SCStatusBandTable 1 } ::= { xdsl2SCStatusBandTable 1 }
Xdsl2SCStatusBandEntry ::= Xdsl2SCStatusBandEntry ::=
SEQUENCE { SEQUENCE {
xdsl2SCStatusBand Xdsl2Band, xdsl2SCStatusBand Xdsl2Band,
xdsl2SCStatusBandLnAtten Unsigned32, xdsl2SCStatusBandLnAtten Unsigned32,
xdsl2SCStatusBandSigAtten Unsigned32 xdsl2SCStatusBandSigAtten Unsigned32
} }
skipping to change at page 102, line 46 skipping to change at page 101, line 41
"The transmission band." "The transmission band."
::= { xdsl2SCStatusBandEntry 1 } ::= { xdsl2SCStatusBandEntry 1 }
xdsl2SCStatusBandLnAtten OBJECT-TYPE xdsl2SCStatusBandLnAtten OBJECT-TYPE
SYNTAX Unsigned32 (0..1270 | 2147483646 | 2147483647) SYNTAX Unsigned32 (0..1270 | 2147483646 | 2147483647)
UNITS "0.1 dB" UNITS "0.1 dB"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"When referring to a band in the downstream direction, it is "When referring to a band in the downstream direction, it is
the the measured difference in the total power transmitted by the
measured difference in the total power transmitted by the xTU-C xTU-C and the total power received by the xTU-R over all
and the total power received by the xTU-R over all sub-carriers subcarriers during diagnostics mode.
during diagnostics mode.
When referring to a band in the upstream direction, it is the When referring to a band in the upstream direction, it is the
measured difference in the total power transmitted by the xTU-R measured difference in the total power transmitted by the xTU-R
and the total power received by the xTU-C over all sub-carriers and the total power received by the xTU-C over all subcarriers
during diagnostics mode. during diagnostics mode.
It ranges from 0 to 1270 units of 0.1 dB (Physical values are It ranges from 0 to 1270 units of 0.1 dB (Physical values are 0
0 to 127 dB). to 127 dB).
A special value of 0x7FFFFFFF (2147483647) indicates the line A special value of 0x7FFFFFFF (2147483647) indicates the line
attenuation is out of range to be represented. attenuation is out of range to be represented.
A special value of 0x7FFFFFFE (2147483646) indicates the line A special value of 0x7FFFFFFE (2147483646) indicates the line
attenuation measurement is unavailable. attenuation measurement is unavailable.
This object reflects the value of the parameter following the This object reflects the value of the parameter following the
most recent DELT performed on the associated line. Once most recent DELT performed on the associated line. Once the DELT
the DELT process is over, the parameter no longer changes process is over, the parameter no longer changes until the row is
until the row is deleted or a new DELT process is initiated." deleted or a new DELT process is initiated."
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.9 (LATNds) REFERENCE "ITU-T G.997.1, paragraph #7.5.1.9 (LATNds)
and paragraph #7.5.1.10 (LATNus)" and paragraph #7.5.1.10 (LATNus)"
DEFVAL { 2147483646 } DEFVAL { 2147483646 }
::= { xdsl2SCStatusBandEntry 2 } ::= { xdsl2SCStatusBandEntry 2 }
xdsl2SCStatusBandSigAtten OBJECT-TYPE xdsl2SCStatusBandSigAtten OBJECT-TYPE
SYNTAX Unsigned32 (0..1270 | 2147483646 | 2147483647) SYNTAX Unsigned32 (0..1270 | 2147483646 | 2147483647)
UNITS "0.1 dB" UNITS "0.1 dB"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"When referring to a band the downstream direction, it is the "When referring to a band the downstream direction, it is the
measured difference in the total power transmitted by the measured difference in the total power transmitted by the xTU-C
xTU-C and the total power received by the xTU-R over all sub and the total power received by the xTU-R over all subcarriers
carriers during Showtime after the diagnostics mode. during Showtime after the diagnostics mode.
When referring to the upstream direction, it is the measured When referring to the upstream direction, it is the measured
difference in the total power transmitted by the difference in the total power transmitted by the xTU-R and the
xTU-R and the total power received by the xTU-C over all sub total power received by the xTU-C over all subcarriers during
carriers during Showtime after the diagnostics mode. Showtime after the diagnostics mode.
It ranges from 0 to 1270 units of 0.1 dB (Physical values It ranges from 0 to 1270 units of 0.1 dB (Physical values are 0
are 0 to 127 dB). to 127 dB).
A special value of 0x7FFFFFFF (2147483647) indicates the line A special value of 0x7FFFFFFF (2147483647) indicates the line
attenuation is out of range to be represented. attenuation is out of range to be represented.
A special value of 0x7FFFFFFE (2147483646) indicates the line A special value of 0x7FFFFFFE (2147483646) indicates the line
attenuation measurement is unavailable. attenuation measurement is unavailable.
This object reflects the value of the parameter following the This object reflects the value of the parameter following the
most recent DELT performed on the associated line. Once most recent DELT performed on the associated line. Once the DELT
the DELT process is over, the parameter no longer changes process is over, the parameter no longer changes until the row is
until the row is deleted or a new DELT process is initiated." deleted or a new DELT process is initiated."
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.11 (SATNds) REFERENCE "ITU-T G.997.1, paragraph #7.5.1.11 (SATNds)
and paragraph #7.5.1.12 (SATNus)" and paragraph #7.5.1.12 (SATNus)"
DEFVAL { 2147483646 } DEFVAL { 2147483646 }
::= { xdsl2SCStatusBandEntry 3 } ::= { xdsl2SCStatusBandEntry 3 }
------------------------------------------------ ------------------------------------------------
-- xdsl2SCStatusSegmentTable -- -- xdsl2SCStatusSegmentTable --
------------------------------------------------ ------------------------------------------------
xdsl2SCStatusSegmentTable OBJECT-TYPE xdsl2SCStatusSegmentTable OBJECT-TYPE
SYNTAX SEQUENCE OF Xdsl2SCStatusSegmentEntry SYNTAX SEQUENCE OF Xdsl2SCStatusSegmentEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The table xdsl2SCStatusSegmentTable contains status "The table xdsl2SCStatusSegmentTable contains status
parameters of VDSL2/ADSL/ADSL2 and ADSL2+ sub-carriers. parameters of VDSL2/ADSL/ADSL2 and ADSL2+ subcarriers.
The parameters in this table MUST be updated after The parameters in this table MUST be updated after a loop
a loop diagnostic procedure and MAY be updated after diagnostic procedure and MAY be updated after a line
a line initialisation and MAY be updated at showtime." initialisation and MAY be updated at showtime."
::= { xdsl2Status 5 } ::= { xdsl2Status 5 }
xdsl2SCStatusSegmentEntry OBJECT-TYPE xdsl2SCStatusSegmentEntry OBJECT-TYPE
SYNTAX Xdsl2SCStatusSegmentEntry SYNTAX Xdsl2SCStatusSegmentEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The table xdsl2SCStatusSegmentEntry contains status "The table xdsl2SCStatusSegmentEntry contains status
parameters parameters of VDSL2/ADSL/ADSL2 and ADSL2+ subcarriers.
of VDSL2/ADSL/ADSL2 and ADSL2+ sub-carriers.
Several objects in the table refer to NSus and NSds. For Several objects in the table refer to NSus and NSds. For G.993.2,
G.993.2, the value of NSus and NSds are respectively the the value of NSus and NSds are respectively the indices of the
indices of the highest supported upstream and downstream sub- highest supported upstream and downstream subcarriers according
carriers according to the selected implementation profile. For to the selected implementation profile.
ADSL, NSus is equal to NSCus-1 and NSds is equal to NSCds-1. For ADSL, NSus is equal to NSCus-1 and NSds is equal to NSCds-1.
One index of this table is an interface index where the One index of this table is an interface index where the interface
interface has an ifType of vdsl2(xxx). A second index of this has an ifType of vdsl2(xxx). A second index of this table is the
table is the transmission direction. A third index identifies transmission direction. A third index identifies the specific
the specific segment of the sub-carriers status addressed." segment of the subcarriers status addressed."
INDEX { ifIndex, INDEX { ifIndex,
xdsl2SCStatusDirection, xdsl2SCStatusDirection,
xdsl2SCStatusSegment } xdsl2SCStatusSegment }
::= { xdsl2SCStatusSegmentTable 1 } ::= { xdsl2SCStatusSegmentTable 1 }
Xdsl2SCStatusSegmentEntry ::= Xdsl2SCStatusSegmentEntry ::=
SEQUENCE { SEQUENCE {
xdsl2SCStatusSegment Unsigned32, xdsl2SCStatusSegment Unsigned32,
xdsl2SCStatusSegmentLinReal OCTET STRING, xdsl2SCStatusSegmentLinReal OCTET STRING,
xdsl2SCStatusSegmentLinImg OCTET STRING, xdsl2SCStatusSegmentLinImg OCTET STRING,
skipping to change at page 105, line 11 skipping to change at page 104, line 4
xdsl2SCStatusSegmentSnr OCTET STRING, xdsl2SCStatusSegmentSnr OCTET STRING,
xdsl2SCStatusSegmentBitsAlloc Xdsl2BitsAlloc, xdsl2SCStatusSegmentBitsAlloc Xdsl2BitsAlloc,
xdsl2SCStatusSegmentGainAlloc OCTET STRING xdsl2SCStatusSegmentGainAlloc OCTET STRING
} }
xdsl2SCStatusSegment OBJECT-TYPE xdsl2SCStatusSegment OBJECT-TYPE
SYNTAX Unsigned32(1..8) SYNTAX Unsigned32(1..8)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The segment of the sub-carriers "The segment of the subcarriers status information provided by
status information provided by this this row.
row. Several status parameters in this table are retrieved in segments.
Several status parameters in this table The first segment of the status information is retrieved with
are retrieved in segments. The first segment xdsl2SCStatusSegment=1, the second segment is retrieved with
of the status information is retrieved with xdsl2SCStatusSegment=2, and so on. When any status parameter is
xdsl2SCStatusSegment=1, the second segment retrieved in n segments where n<8) then, for that parameter,
is retrieved with xdsl2SCStatusSegment=2, and GET operations for the remaining segment numbers (n+1 to 8) will
so on. When any status parameter is retrieved respond with a zero-length OCTET STRING."
in n segments where n<8) then, for that
parameter, GET operations for the remaining segment
numbers (n+1 to 8) will respond with a zero length
OCTET STRING."
::= { xdsl2SCStatusSegmentEntry 1 } ::= { xdsl2SCStatusSegmentEntry 1 }
xdsl2SCStatusSegmentLinReal OBJECT-TYPE xdsl2SCStatusSegmentLinReal OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(0..1024)) SYNTAX OCTET STRING (SIZE(0..1024))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An array of up to 512 complex H(f) linear representation "An array of up to 512 complex H(f) linear representation
values in linear scale for the respective transmission values in linear scale for the respective transmission direction.
direction. It is designed to support up to 512 (downstream) It is designed to support up to 512 (downstream) subcarriers
sub-carriers groups and can be retrieved in a single segment. groups and can be retrieved in a single segment.
The number of utilized values on downstream direction depends The number of utilized values on downstream direction depends on
on NSds, and on upstream direction it depends on NSus. This NSds, and on upstream direction it depends on NSus. This value is
value is referred here as NS. referred here as NS.
Each array entry represents the real component [referred here as Each array entry represents the real component [referred here as
a(i)] of Hlin(f = i*Df) value for a particular sub-carrier group a(i)] of Hlin(f = i*Df) value for a particular subcarrier group
index i (0 <= i < NS). index i (0 <= i < NS).
Hlin(f) is represented as ((scale/2^15)*((a(i)+j*b(i))/2^15)), Hlin(f) is represented as ((scale/2^15)*((a(i)+j*b(i))/2^15)),
where scale is xdsl2SCStatusLinScale and a(i) and b(i) where scale is xdsl2SCStatusLinScale and a(i) and b(i)
[provided by the xdsl2SCStatusSegmentLinImg object] are in the [provided by the xdsl2SCStatusSegmentLinImg object] are in the
range (-2^15+1) to (+2^15-1). range (-2^15+1) to (+2^15-1).
A special value a(i)=b(i)= -2^15 indicates that no measurement A special value a(i)=b(i)= -2^15 indicates that no measurement
could be done for the sub-carriers group because it is out of could be done for the subcarriers group because it is out of the
the passband or that the attenuation is out of range to be passband or that the attenuation is out of range to be
represented. This parameter is only available after a loop represented. This parameter is only available after a loop
diagnostic procedure. diagnostic procedure.
Each value in this array is 16 bits wide and is stored in big Each value in this array is 16 bits wide and is stored in big
endian format." endian format."
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.26.3 (HLINpsds) REFERENCE "ITU-T G.997.1, paragraph #7.5.1.26.3 (HLINpsds)
and paragraph #7.5.1.26.9 (HLINpsus)" and paragraph #7.5.1.26.9 (HLINpsus)"
::= { xdsl2SCStatusSegmentEntry 2 } ::= { xdsl2SCStatusSegmentEntry 2 }
xdsl2SCStatusSegmentLinImg OBJECT-TYPE xdsl2SCStatusSegmentLinImg OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(0..1024)) SYNTAX OCTET STRING (SIZE(0..1024))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An array of up to 512 complex H(f) linear representation "An array of up to 512 complex H(f) linear representation
values in linear scale for the respective transmission values in linear scale for the respective transmission direction.
direction. It is designed to support up to 512 (downstream)
sub-carriers groups and can be retrieved in a single segment. It is designed to support up to 512 (downstream) subcarriers
The number of utilized values on downstream direction depends groups and can be retrieved in a single segment.
on NSds, and on upstream direction it depends on NSus. This The number of utilized values on downstream direction depends on
value is referred here as NS. NSds, and on upstream direction it depends on NSus. This value is
referred here as NS.
Each array entry represents the imaginary component [referred Each array entry represents the imaginary component [referred
here as b(i)] of Hlin(f = i*Df) value for a particular sub- here as b(i)] of Hlin(f = i*Df) value for a particular
carrier group index i (0 <= i < NS). subcarrier group index i (0 <= i < NS).
Hlin(f) is represented as ((scale/2^15)*((a(i)+j*b(i))/2^15)), Hlin(f) is represented as ((scale/2^15)*((a(i)+j*b(i))/2^15)),
where scale is xdsl2SCStatusLinScale and a(i) [provided by where scale is xdsl2SCStatusLinScale and a(i) [provided by the
the xdsl2SCStatusSegmentLinReal object] and b(i) are in the xdsl2SCStatusSegmentLinReal object] and b(i) are in the range
range (-2^15+1) to (+2^15-1). (-2^15+1) to (+2^15-1).
A special value a(i)=b(i)= -2^15 indicates that no measurement A special value a(i)=b(i)= -2^15 indicates that no measurement
could be done for the sub-carriers group because it is out of could be done for the subcarriers group because it is out of the
the passband or that the attenuation is out of range to be passband or that the attenuation is out of range to be
represented. This parameter is only available after a loop represented. This parameter is only available after a loop
diagnostic procedure. diagnostic procedure.
Each value in this array is 16 bits wide and is stored in big Each value in this array is 16 bits wide and is stored in big
endian format." endian format."
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.26.3 (HLINpsds) REFERENCE "ITU-T G.997.1, paragraph #7.5.1.26.3 (HLINpsds)
and paragraph #7.5.1.26.9 (HLINpsus)" and paragraph #7.5.1.26.9 (HLINpsus)"
::= { xdsl2SCStatusSegmentEntry 3 } ::= { xdsl2SCStatusSegmentEntry 3 }
xdsl2SCStatusSegmentLog OBJECT-TYPE xdsl2SCStatusSegmentLog OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(0..1024)) SYNTAX OCTET STRING (SIZE(0..1024))
UNITS "dB" UNITS "dB"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An array of up to 512 real H(f) logarithmic representation "An array of up to 512 real H(f) logarithmic representation
values in dB for the respective transmission direction. It is values in dB for the respective transmission direction. It is
designed to support up to 512 (downstream) sub-carriers groups designed to support up to 512 (downstream) subcarriers groups
and can be retrieved in a single segment. and can be retrieved in a single segment.
The number of utilized values on downstream direction depends The number of utilized values on downstream direction depends
on NSds, and on upstream direction it depends on NSus. This on NSds, and on upstream direction it depends on NSus. This
value is referred here as NS. value is referred here as NS.
Each array entry represents the real Hlog(f = i*Df) value for a Each array entry represents the real Hlog(f = i*Df) value for a
particular sub-carrier group index i, (0 <= i < NS). particular subcarrier group index i, (0 <= i < NS).
The real Hlog(f) value is represented as (6-m(i)/10), with m(i) The real Hlog(f) value is represented as (6-m(i)/10), with m(i)
in the range 0 to 1022. A special value m=1023 indicates that in the range 0 to 1022. A special value m=1023 indicates that
no measurement could be done for the sub-carrier group because no measurement could be done for the subcarrier group because
it is out of the passband or that the attenuation is out of it is out of the passband or that the attenuation is out of
range to be represented. This parameter is applicable in loop range to be represented. This parameter is applicable in loop
diagnostic procedure and initialization. diagnostic procedure and initialization.
Each value in this array is 16 bits wide and is stored Each value in this array is 16 bits wide and is stored in big
in big endian format." endian format."
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.26.6 (HLOGpsds) REFERENCE "ITU-T G.997.1, paragraph #7.5.1.26.6 (HLOGpsds)
and paragraph #7.5.1.26.12 (HLOGpsus)" and paragraph #7.5.1.26.12 (HLOGpsus)"
::= { xdsl2SCStatusSegmentEntry 4 } ::= { xdsl2SCStatusSegmentEntry 4 }
xdsl2SCStatusSegmentQln OBJECT-TYPE xdsl2SCStatusSegmentQln OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(0..512)) SYNTAX OCTET STRING (SIZE(0..512))
UNITS "dBm/Hz" UNITS "dBm/Hz"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An array of up to 512 real Quiet Line Noise values in dBm/Hz "An array of up to 512 real Quiet Line Noise values in dBm/Hz
for the respective transmission direction. It is designed for for the respective transmission direction. It is designed for up
up to 512 (downstream) sub-carriers groups and can be retrieved to 512 (downstream) subcarriers groups and can be retrieved in a
in a single segment. single segment.
The number of utilized values on downstream direction depends The number of utilized values on downstream direction depends on
on NSds, and on upstream direction it depends on NSus. This NSds, and on upstream direction it depends on NSus. This value is
value is referred here as NS. referred here as NS.
Each array entry represents the QLN(f = i*Df) value for a Each array entry represents the QLN(f = i*Df) value for a
particular sub-carrier index i, (0 <= i < NS). particular subcarrier index i, (0 <= i < NS).
The QLN(f) is represented as ( -23-n(i)/2), with n(i) in the The QLN(f) is represented as ( -23-n(i)/2), with n(i) in the range
range 0 to 254. A special value n(i)=255 indicates that no 0 to 254. A special value n(i)=255 indicates that no measurement
measurement could be done for the sub-carrier group because it could be done for the subcarrier group because it is out of the
is out of the passband or that the noise PSD is out of range passband or that the noise PSD is out of range to be represented.
to be represented.
This parameter is applicable in loop diagnostic procedure and This parameter is applicable in loop diagnostic procedure and
initialization. Each value in this array is 8 bits wide." initialization. Each value in this array is 8 bits wide."
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.27.3 (QLNpsds) REFERENCE "ITU-T G.997.1, paragraph #7.5.1.27.3 (QLNpsds)
and paragraph #7.5.1.27.6 (QLNpsus)" and paragraph #7.5.1.27.6 (QLNpsus)"
::= { xdsl2SCStatusSegmentEntry 5 } ::= { xdsl2SCStatusSegmentEntry 5 }
xdsl2SCStatusSegmentSnr OBJECT-TYPE xdsl2SCStatusSegmentSnr OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(0..512)) SYNTAX OCTET STRING (SIZE(0..512))
UNITS "0.5 dB" UNITS "0.5 dB"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The SNR Margin per sub-carrier group, expressing the "The SNR Margin per subcarrier group, expressing the ratio
ratio between the received signal power and received noise between the received signal power and received noise power per
power per sub-scriber group. It is an array of 512 octets, subscriber group. It is an array of 512 octets, designed for
designed for supporting up to 512 (downstream) sub-carriers supporting up to 512 (downstream) subcarriers groups and can be
groups and can be retrieved in a single segment. retrieved in a single segment.
The number of utilized octets on downstream direction depends The number of utilized octets on downstream direction depends on
on NSds, and on upstream direction it depends on NSus. This NSds, and on upstream direction it depends on NSus. This value is
value is referred here as NS. referred here as NS.
Octet i (0 <= i < NS) is set to a value in the range 0 to Octet i (0 <= i < NS) is set to a value in the range 0 to
254 to indicate that the respective downstream or upstream sub- 254 to indicate that the respective downstream or upstream
carrier group i has SNR of: subcarrier group i has SNR of:
(-32 + xdsl2SCStatusSegmentSnr(i)/2) in dB (i.e., -32 to 95dB). (-32 + xdsl2SCStatusSegmentSnr(i)/2) in dB (i.e., -32 to 95dB).
The special value 255 means that no measurement could be done The special value 255 means that no measurement could be done for
for the sub-carrier group because it is out of the PSD mask the subcarrier group because it is out of the PSD mask passband or
passband or that the noise PSD is out of range to be that the noise PSD is out of range to be represented. Each value
represented. Each value in this array is 8 bits wide." in this array is 8 bits wide."
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.28.3 (SNRpsds) REFERENCE "ITU-T G.997.1, paragraph #7.5.1.28.3 (SNRpsds)
and paragraph #7.5.1.28.6 (SNRpsus)" and paragraph #7.5.1.28.6 (SNRpsus)"
::= { xdsl2SCStatusSegmentEntry 6 } ::= { xdsl2SCStatusSegmentEntry 6 }
xdsl2SCStatusSegmentBitsAlloc OBJECT-TYPE xdsl2SCStatusSegmentBitsAlloc OBJECT-TYPE
SYNTAX Xdsl2BitsAlloc SYNTAX Xdsl2BitsAlloc
UNITS "bits" UNITS "bits"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The bits allocation per sub-carrier. An array of 256 octets "The bits allocation per subcarrier. An array of 256 octets
(512 nibbles), designed for supporting up to 512 (downstream) (512 nibbles), designed for supporting up to 512 (downstream)
sub-carriers. When more then 512 sub-carriers are supported, subcarriers. When more then 512 subcarriers are supported, the
the status information is reported through multiple (up to 8) status information is reported through multiple (up to 8)
segments. The first segment is then used for the first 512 segments. The first segment is then used for the first 512
sub-carriers. The second segment is used for the sub-carriers subcarriers. The second segment is used for the subcarriers
512 to 1023 and so on. 512 to 1023 and so on.
The aggregate number of utilized nibbles on downstream The aggregate number of utilized nibbles on downstream direction
direction (in all segments) depends on NSds, and on upstream (in all segments) depends on NSds, and on upstream direction it
direction it depends on NSus. depends on NSus.
This value is referred here as NS. The segment number is in This value is referred here as NS. The segment number is in
xdsl2SCStatusSegment. xdsl2SCStatusSegment.
Nibble i (0 <= i < MIN(NS-(segment-1)*512,512)) in each Nibble i (0 <= i < MIN(NS-(segment-1)*512,512)) in each
segment is set to a value in the range 0 to 15 to indicate that segment is set to a value in the range 0 to 15 to indicate that
the respective downstream or upstream sub-carrier j the respective downstream or upstream subcarrier j
(j=(segement-1)*512+i) has the same amount of bits (j=(segement-1)*512+i) has the same amount of bits
allocation." allocation."
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.29.1 (BITSpsds) REFERENCE "ITU-T G.997.1, paragraph #7.5.1.29.1 (BITSpsds)
and paragraph #7.5.1.29.2 (BITSpsus)" and paragraph #7.5.1.29.2 (BITSpsus)"
::= { xdsl2SCStatusSegmentEntry 7 } ::= { xdsl2SCStatusSegmentEntry 7 }
xdsl2SCStatusSegmentGainAlloc OBJECT-TYPE xdsl2SCStatusSegmentGainAlloc OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(0..1024)) SYNTAX OCTET STRING (SIZE(0..1024))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The gain allocation per sub-carrier. An array of 512 16-bits "The gain allocation per subcarrier. An array of 512 16-bits
values, designed for supporting up to 512 (downstream) sub- values, designed for supporting up to 512 (downstream)
carriers. When more then 512 sub-carriers are supported, subcarriers. When more then 512 subcarriers are supported, the
the status information is reported through multiple (up to 8) status information is reported through multiple (up to 8)
segments. The first segment is then used for the first 512 segments. The first segment is then used for the first 512
sub-carriers. The second segment is used for the sub-carriers subcarriers. The second segment is used for the subcarriers 512 to
512 to 1023 and so on. 1023 and so on.
The aggregate number of utilized octets on downstream direction The aggregate number of utilized octets on downstream direction
depends on NSds, and on upstream direction it depends on NSus. depends on NSds, and on upstream direction it depends on NSus.
This value is referred here as NS. The segment number is in This value is referred here as NS. The segment number is in
xdsl2SCStatusSegment. xdsl2SCStatusSegment.
Value i (0 <= i < MIN(NS-(segment-1)*512,512)) in each Value i (0 <= i < MIN(NS-(segment-1)*512,512)) in each
segment is set to a value in the range 0 to 4093 to indicate segment is set to a value in the range 0 to 4093 to indicate that
that the respective downstream or upstream sub-carrier j the respective downstream or upstream subcarrier j
(j=(segement-1)*512+i) has the same amount of gain value. (j=(segement-1)*512+i) has the same amount of gain value.
The gain value is represented as a multiple of 1/512 on The gain value is represented as a multiple of 1/512 on linear
linear scale. Each value in this array is 16 bits wide and is scale. Each value in this array is 16 bits wide and is stored in
stored in big endian format." big endian format."
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.29.3 (GAINSpsds) REFERENCE "ITU-T G.997.1, paragraph #7.5.1.29.3 (GAINSpsds)
and paragraph #7.5.1.29.4 (GAINSpsus)" and paragraph #7.5.1.29.4 (GAINSpsus)"
::= { xdsl2SCStatusSegmentEntry 8 } ::= { xdsl2SCStatusSegmentEntry 8 }
------------------------------------------------ ------------------------------------------------
-- xdsl2LineInventoryTable -- -- xdsl2LineInventoryTable --
------------------------------------------------ ------------------------------------------------
xdsl2LineInventoryTable OBJECT-TYPE xdsl2LineInventoryTable OBJECT-TYPE
SYNTAX SEQUENCE OF Xdsl2LineInventoryEntry SYNTAX SEQUENCE OF Xdsl2LineInventoryEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
skipping to change at page 109, line 46 skipping to change at page 108, line 35
DSL termination unit. " DSL termination unit. "
::= { xdsl2Inventory 1 } ::= { xdsl2Inventory 1 }
xdsl2LineInventoryEntry OBJECT-TYPE xdsl2LineInventoryEntry OBJECT-TYPE
SYNTAX Xdsl2LineInventoryEntry SYNTAX Xdsl2LineInventoryEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The table xdsl2LineInventoryTable contains inventory of DSL "The table xdsl2LineInventoryTable contains inventory of DSL
termination unit. termination unit.
The index of this table is an interface index where the The index of this table is an interface index where the interface
interface has an ifType of vdsl2(xxx)." has an ifType of vdsl2(xxx)."
INDEX { ifIndex, xdsl2LInvUnit } INDEX { ifIndex, xdsl2LInvUnit }
::= { xdsl2LineInventoryTable 1 } ::= { xdsl2LineInventoryTable 1 }
Xdsl2LineInventoryEntry ::= Xdsl2LineInventoryEntry ::=
SEQUENCE { SEQUENCE {
xdsl2LInvUnit Xdsl2Unit, xdsl2LInvUnit Xdsl2Unit,
xdsl2LInvG994VendorId OCTET STRING, xdsl2LInvG994VendorId OCTET STRING,
xdsl2LInvSystemVendorId OCTET STRING, xdsl2LInvSystemVendorId OCTET STRING,
xdsl2LInvVersionNumber OCTET STRING, xdsl2LInvVersionNumber OCTET STRING,
xdsl2LInvSerialNumber OCTET STRING, xdsl2LInvSerialNumber OCTET STRING,
xdsl2LInvSelfTestResult Unsigned32, xdsl2LInvSelfTestResult Unsigned32,
xdsl2LInvTransmissionCapabilities Xdsl2TransmissionModeType xdsl2LInvTransmissionCapabilities Xdsl2TransmissionModeType
} }
skipping to change at page 110, line 40 skipping to change at page 109, line 28
code followed by a (regionally allocated) provider code, as code followed by a (regionally allocated) provider code, as
defined in Recommendation T.35." defined in Recommendation T.35."
REFERENCE "ITU-T G.997.1, paragraph #7.4.1-7.4.2" REFERENCE "ITU-T G.997.1, paragraph #7.4.1-7.4.2"
::= { xdsl2LineInventoryEntry 2 } ::= { xdsl2LineInventoryEntry 2 }
xdsl2LInvSystemVendorId OBJECT-TYPE xdsl2LInvSystemVendorId 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
"The ATU System Vendor ID (identifies the XTU system "The ATU System Vendor ID (identifies the xTU system
integrator) as inserted in the Overhead Messages (both XTUs integrator) as inserted in the Overhead Messages (both XTUs for
for G.992.3, G.992.4, G.992.5 and G.993.2) or in the G.992.3, G.992.4, G.992.5 and G.993.2) or in the Embedded
Embedded Operations Channel (XTU-R in G.992.1 and G.992.2). Operations Channel (xTU-R in G.992.1 and G.992.2).
It consists of 8 binary octets, with same format as used for It consists of 8 binary octets, with same format as used for
Xdsl2InvG994VendorId." Xdsl2InvG994VendorId."
REFERENCE "ITU-T G.997.1, paragraph #7.4.3-7.4.4" REFERENCE "ITU-T G.997.1, paragraph #7.4.3-7.4.4"
::= { xdsl2LineInventoryEntry 3 } ::= { xdsl2LineInventoryEntry 3 }
xdsl2LInvVersionNumber OBJECT-TYPE xdsl2LInvVersionNumber OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(0..16)) SYNTAX OCTET STRING (SIZE(0..16))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The XTU version number (vendor specific information) as "The xTU version number (vendor-specific information) as
inserted in the Overhead Messages (both XTUs for G.992.3, inserted in the Overhead Messages (both XTUs for G.992.3,
G.992.4, G.992.5 and G.993.2) or in the Embedded Operations G.992.4, G.992.5 and G.993.2) or in the Embedded Operations
Channel (XTU-R in G.992.1 and G.992.2). It consists of up Channel (xTU-R in G.992.1 and G.992.2). It consists of up to 16
to 16 binary octets." binary octets."
REFERENCE "ITU-T G.997.1, paragraph #7.4.5-7.4.6" REFERENCE "ITU-T G.997.1, paragraph #7.4.5-7.4.6"
::= { xdsl2LineInventoryEntry 4 } ::= { xdsl2LineInventoryEntry 4 }
xdsl2LInvSerialNumber OBJECT-TYPE xdsl2LInvSerialNumber OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(0..32)) SYNTAX OCTET STRING (SIZE(0..32))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The XTU serial number (vendor specific information) as "The xTU serial number (vendor-specific information) as
inserted in the Overhead Messages (both XTUs for G.992.3, inserted in the Overhead Messages (both XTUs for G.992.3,
G.992.4, G.992.5 and G.993.2) or in the Embedded Operations G.992.4, G.992.5 and G.993.2) or in the Embedded Operations
Channel (XTU-R in G.992.1 and G.992.2). It is vendor Channel (xTU-R in G.992.1 and G.992.2). It is vendor specific
specific information consisting of up to 32 ASCII characters." information consisting of up to 32 ASCII characters."
REFERENCE "ITU-T G.997.1, paragraph #7.4.7-7.4.8" REFERENCE "ITU-T G.997.1, paragraph #7.4.7-7.4.8"
::= { xdsl2LineInventoryEntry 5 } ::= { xdsl2LineInventoryEntry 5 }
xdsl2LInvSelfTestResult OBJECT-TYPE xdsl2LInvSelfTestResult OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The XTU self-test result, coded as a 32-bit value. The "The xTU self-test result, coded as a 32-bit value. The
most significant octet of the result is '0' if the most significant octet of the result is '0' if the
self-test self-test passed, and '1' if the self-test failed. The
passed, and '1' if the self-test failed. The interpretation of the other octets is vendor discretionary."
interpretation
of the other octets is vendor discretionary."
REFERENCE "ITU-T G.997.1, paragraph #7.4.9-7.4.10" REFERENCE "ITU-T G.997.1, paragraph #7.4.9-7.4.10"
DEFVAL { 0 } DEFVAL { 0 }
::= { xdsl2LineInventoryEntry 6 } ::= { xdsl2LineInventoryEntry 6 }
xdsl2LInvTransmissionCapabilities OBJECT-TYPE xdsl2LInvTransmissionCapabilities OBJECT-TYPE
SYNTAX Xdsl2TransmissionModeType SYNTAX Xdsl2TransmissionModeType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The XTU transmission system capability list of the different "The xTU transmission system capability list of the different
coding types. It is coded in a bit-map representation with 1 coding types. It is coded in a bit-map representation with 1 or
or more bits set. A bit set to '1' means that the XTU more bits set. A bit set to '1' means that the xTU
supports the respective coding. The value may be derived supports the respective coding. The value may be derived from
from the handshaking procedures defined in G.994.1. A set the handshaking procedures defined in G.994.1. A set of xDSL
of xDSL line transmission modes, with one bit per mode." line transmission modes, with one bit per mode."
REFERENCE "ITU-T G.997.1, paragraph #7.4.11-7.4.12" REFERENCE "ITU-T G.997.1, paragraph #7.4.11-7.4.12"
::= { xdsl2LineInventoryEntry 7 } ::= { xdsl2LineInventoryEntry 7 }
------------------------------------------------ ------------------------------------------------
-- xdsl2LineConfTemplateTable -- -- xdsl2LineConfTemplateTable --
------------------------------------------------ ------------------------------------------------
xdsl2LineConfTemplateTable OBJECT-TYPE xdsl2LineConfTemplateTable OBJECT-TYPE
SYNTAX SEQUENCE OF Xdsl2LineConfTemplateEntry SYNTAX SEQUENCE OF Xdsl2LineConfTemplateEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The table xdsl2LineConfTemplateTable contains VDSL2/ADSL/ "The table xdsl2LineConfTemplateTable contains VDSL2/ADSL/
ADSL2 and ADSL2+ line configuration template. ADSL2 and ADSL2+ line configuration templates.
Note that this table is also used to configure the number of Note that this table is also used to configure the number of
bearer channels. bearer channels.
When the number of bearer channels is increased, the SNMP When the number of bearer channels is increased, the SNMP agent
agent SHOULD create rows in all tables indexed by a channel SHOULD create rows in all tables indexed by a channel index. When
index. When the number of bearer channels is decreased, the the number of bearer channels is decreased, the SNMP agent SHOULD
SNMP agent SHOULD delete rows in all tables indexed by a delete rows in all tables indexed by a channel index.
channel index.
For example, if the value of xdsl2LConfTempChan4ConfProfile is For example, if the value of xdsl2LConfTempChan4ConfProfile is
set to a non null value then rows SHOULD be created in set to a non null value then rows SHOULD be created in
xdsl2ChannelStatusTable, xdsl2PMChCurrTable, and all other xdsl2ChannelStatusTable, xdsl2PMChCurrTable, and all other tables
tables indexed by a channel index. indexed by a channel index.
For example, if the value of xdsl2LConfTempChan2ConfProfile is For example, if the value of xdsl2LConfTempChan2ConfProfile is
set to a null value then rows SHOULD be deleted in set to a null value then rows SHOULD be deleted in
xdsl2ChannelStatusTable, xdsl2PMChCurrTable, and all other xdsl2ChannelStatusTable, xdsl2PMChCurrTable, and all other
tables indexed by a channel index. tables indexed by a channel index.
Entries in this table MUST be maintained in a Entries in this table MUST be maintained in a persistent
persistent manner." manner."
::= { xdsl2ProfileLine 1 } ::= { xdsl2ProfileLine 1 }
xdsl2LineConfTemplateEntry OBJECT-TYPE xdsl2LineConfTemplateEntry OBJECT-TYPE
SYNTAX Xdsl2LineConfTemplateEntry SYNTAX Xdsl2LineConfTemplateEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The table xdsl2LineConfTemplateTable contains VDSL2/ADSL/ "The table xdsl2LineConfTemplateTable contains VDSL2/ADSL/
ADSL2 and ADSL2+ line configuration template. ADSL2 and ADSL2+ line configuration templates.
A default template with an index of 'DEFVAL' will A default template with an index of 'DEFVAL' will always exist
always exist and its parameters will be set to vendor-specific and its parameters will be set to vendor-specific values, unless
values, unless otherwise specified in this document" otherwise specified in this document."
INDEX { xdsl2LConfTempTemplateName } INDEX { xdsl2LConfTempTemplateName }
::= { xdsl2LineConfTemplateTable 1 } ::= { xdsl2LineConfTemplateTable 1 }
Xdsl2LineConfTemplateEntry ::= Xdsl2LineConfTemplateEntry ::=
SEQUENCE { SEQUENCE {
xdsl2LConfTempTemplateName SnmpAdminString, xdsl2LConfTempTemplateName SnmpAdminString,
xdsl2LConfTempLineProfile SnmpAdminString, xdsl2LConfTempLineProfile SnmpAdminString,
xdsl2LConfTempChan1ConfProfile SnmpAdminString, xdsl2LConfTempChan1ConfProfile SnmpAdminString,
xdsl2LConfTempChan1RaRatioDs Unsigned32, xdsl2LConfTempChan1RaRatioDs Unsigned32,
xdsl2LConfTempChan1RaRatioUs Unsigned32, xdsl2LConfTempChan1RaRatioUs Unsigned32,
skipping to change at page 113, line 40 skipping to change at page 112, line 25
"This object identifies a row in this table." "This object identifies a row in this table."
REFERENCE "DSL Forum TR-129, paragraph #5.4" REFERENCE "DSL Forum TR-129, paragraph #5.4"
::= { xdsl2LineConfTemplateEntry 1 } ::= { xdsl2LineConfTemplateEntry 1 }
xdsl2LConfTempLineProfile OBJECT-TYPE xdsl2LConfTempLineProfile OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE(1..32)) SYNTAX SnmpAdminString (SIZE(1..32))
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of this object identifies the row in the "The value of this object identifies the row in the
VDSL2/ADSL/ VDSL2/ADSL/ADSL2 and ADSL2+ line configuration Profile Table,
ADSL2 and ADSL2+ line configuration Profile Table, (xdsl2LineConfProfTable) that applies for this DSL line."
(Xdsl2LineConfProfTable),
which applies for this DSL line."
REFERENCE "DSL Forum TR-129, paragraph #5.4" REFERENCE "DSL Forum TR-129, paragraph #5.4"
DEFVAL { "DEFVAL" } DEFVAL { "DEFVAL" }
::= { xdsl2LineConfTemplateEntry 2 } ::= { xdsl2LineConfTemplateEntry 2 }
xdsl2LConfTempChan1ConfProfile OBJECT-TYPE xdsl2LConfTempChan1ConfProfile OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE(1..32)) SYNTAX SnmpAdminString (SIZE(1..32))
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of this object identifies the row in the "The value of this object identifies the row in the VDSL2/
VDSL2/ADSL/ ADSL/ADSL2 and ADSL2+ channel configuration Profile Table,
ADSL2 and ADSL2+ channel configuration Profile Table, (xdsl2ChConfProfileTable) that applies to DSL bearer channel #1.
(xdsl2ChConfProfileTable) that applies to DSL bearer The channel profile name specified here MUST match the name of an
channel #1. The channel profile name specified here must existing row in the xdsl2ChConfProfileTable table."
match the name of an existing row in the
xdsl2ChConfProfileTable table."
DEFVAL { "DEFVAL" } DEFVAL { "DEFVAL" }
::= { xdsl2LineConfTemplateEntry 3 } ::= { xdsl2LineConfTemplateEntry 3 }
xdsl2LConfTempChan1RaRatioDs OBJECT-TYPE xdsl2LConfTempChan1RaRatioDs OBJECT-TYPE
SYNTAX Unsigned32(0..100) SYNTAX Unsigned32(0..100)
UNITS "percents" UNITS "percent"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Rate Adaptation Ratio. The ratio (in %) that should be "Rate Adaptation Ratio. The ratio (in %) that should be
taken into account for the bearer channel #1 when performing taken into account for the bearer channel #1 when performing rate
rate adaptation on Downstream. The ratio refers to the adaptation on Downstream. The ratio refers to the available data
available data rate in excess of the Minimum Data Rate, summed rate in excess of the Minimum Data Rate, summed over all bearer
over all bearer channels. channels.
Also, the 100 - xdsl2LConfTempChan1RaRatioDs is the ratio of Also, the 100 - xdsl2LConfTempChan1RaRatioDs is the ratio of
excess data rate to be assigned to all other bearer channels excess data rate to be assigned to all other bearer channels on
on Downstream direction. The sum of rate adaptation ratios Downstream direction. The sum of rate adaptation ratios over all
over all bearers on the same direction shall be equal to 100%. bearers on the same direction shall be equal to 100%.
" "
REFERENCE "ITU-T G.997.1, paragraph #7.3.2.1.4" REFERENCE "ITU-T G.997.1, paragraph #7.3.2.1.4
(Rate adaptation ratio)"
DEFVAL { 100 } DEFVAL { 100 }
::= { xdsl2LineConfTemplateEntry 4 } ::= { xdsl2LineConfTemplateEntry 4 }
xdsl2LConfTempChan1RaRatioUs OBJECT-TYPE xdsl2LConfTempChan1RaRatioUs OBJECT-TYPE
SYNTAX Unsigned32(0..100) SYNTAX Unsigned32(0..100)
UNITS "percents" UNITS "percent"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Rate Adaptation Ratio. The ratio (in %) that should be "Rate Adaptation Ratio. The ratio (in %) that should be
taken into account for the bearer channel #1 when performing taken into account for the bearer channel #1 when performing
rate adaptation on Upstream. The ratio refers to the rate adaptation on Upstream. The ratio refers to the available
available data rate in excess of the Minimum Data Rate, summed data rate in excess of the Minimum Data Rate, summed over all
over all bearer channels. bearer channels.
Also, the 100 - xdsl2LConfTempChan1RaRatioUs is the ratio of Also, the 100 - xdsl2LConfTempChan1RaRatioUs is the ratio of
excess data rate to be assigned to all other bearer channels excess data rate to be assigned to all other bearer channels on
on Upstream direction. The sum of rate adaptation ratios over Upstream direction. The sum of rate adaptation ratios over all
all bearers on the same direction shall be equal to 100 %." bearers on the same direction shall be equal to 100 %."
REFERENCE "ITU-T G.997.1, paragraph #7.3.2.1.4" REFERENCE "ITU-T G.997.1, paragraph #7.3.2.1.4
(Rate adaptation ratio)"
DEFVAL { 100 } DEFVAL { 100 }
::= { xdsl2LineConfTemplateEntry 5 } ::= { xdsl2LineConfTemplateEntry 5 }
xdsl2LConfTempChan2ConfProfile OBJECT-TYPE xdsl2LConfTempChan2ConfProfile OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE(0..32)) SYNTAX SnmpAdminString (SIZE(0..32))
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of this object identifies the row in the "The value of this object identifies the row in the VDSL2/
VDSL2/ADSL/ ADSL/ADSL2 and ADSL2+ channel configuration Profile Table,
ADSL2 and ADSL2+ channel configuration Profile Table, (xdsl2ChConfProfileTable) that applies to DSL bearer channel #2.
(xdsl2ChConfProfileTable) that applies to DSL bearer If the channel is unused, then the object is set to a zero-length
channel #2. If the channel is unused, then the object is set string.
to a zero length string. This object may be set to a zero-length string only if
This object may be set to a zero length string only if xdsl2LConfTempChan3ConfProfile contains a zero-length
xdsl2LConfTempChan3ConfProfile contains a zero length
string." string."
DEFVAL { "" } DEFVAL { "" }
::= { xdsl2LineConfTemplateEntry 6 } ::= { xdsl2LineConfTemplateEntry 6 }
xdsl2LConfTempChan2RaRatioDs OBJECT-TYPE xdsl2LConfTempChan2RaRatioDs OBJECT-TYPE
SYNTAX Unsigned32(0..100) SYNTAX Unsigned32(0..100)
UNITS "percents" UNITS "percent"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Rate Adaptation Ratio. The ratio (in %) that should be "Rate Adaptation Ratio. The ratio (in %) that should be
taken into account for the bearer channel #2 when performing taken into account for the bearer channel #2 when performing
rate adaptation on Downstream. The ratio refers to the rate adaptation on Downstream. The ratio refers to the available
available data rate in excess of the Minimum Data Rate, data rate in excess of the Minimum Data Rate, summed over all
summed over all bearer channels. bearer channels.
Also, the 100 - xdsl2LConfTempChan2RaRatioDs is the ratio of Also, the 100 - xdsl2LConfTempChan2RaRatioDs is the ratio of
excess data rate to be assigned to all other bearer channels excess data rate to be assigned to all other bearer channels on
on Downstream direction. The sum of rate adaptation ratios Downstream direction. The sum of rate adaptation ratios over all
over all bearers on the same direction shall be equal to bearers on the same direction shall be equal to
100%." 100%."
REFERENCE "ITU-T G.997.1, paragraph #7.3.2.1.4" REFERENCE "ITU-T G.997.1, paragraph #7.3.2.1.4
(Rate adaptation ratio)"
DEFVAL { 0 } DEFVAL { 0 }
::= { xdsl2LineConfTemplateEntry 7 } ::= { xdsl2LineConfTemplateEntry 7 }
xdsl2LConfTempChan2RaRatioUs OBJECT-TYPE xdsl2LConfTempChan2RaRatioUs OBJECT-TYPE
SYNTAX Unsigned32(0..100) SYNTAX Unsigned32(0..100)
UNITS "percents" UNITS "percent"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Rate Adaptation Ratio. The ratio (in %) that should be "Rate Adaptation Ratio. The ratio (in %) that should be
taken into account for the bearer channel #2 when performing taken into account for the bearer channel #2 when performing
rate adaptation on Upstream. The ratio refers to the rate adaptation on Upstream. The ratio refers to the available
available data rate in excess of the Minimum Data Rate, data rate in excess of the Minimum Data Rate, summed over all
summed over all bearer channels. bearer channels.
Also, the 100 - xdsl2LConfTempChan2RaRatioUs is the ratio of Also, the 100 - xdsl2LConfTempChan2RaRatioUs is the ratio of
excess data rate to be assigned to all other bearer channels excess data rate to be assigned to all other bearer channels on
on Upstream direction. The sum of rate adaptation ratios over Upstream direction. The sum of rate adaptation ratios over all
all bearers on the same direction shall be equal to 100 %." bearers on the same direction shall be equal to 100 %."
REFERENCE "ITU-T G.997.1, paragraph #7.3.2.1.4" REFERENCE "ITU-T G.997.1, paragraph #7.3.2.1.4
(Rate adaptation ratio)"
DEFVAL { 0 } DEFVAL { 0 }
::= { xdsl2LineConfTemplateEntry 8 } ::= { xdsl2LineConfTemplateEntry 8 }
xdsl2LConfTempChan3ConfProfile OBJECT-TYPE xdsl2LConfTempChan3ConfProfile OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE(0..32)) SYNTAX SnmpAdminString (SIZE(0..32))
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of this object identifies the row in the "The value of this object identifies the row in the VDSL2/
VDSL2/ADSL/ ADSL/ADSL2 and ADSL2+ channel configuration Profile Table,
ADSL2 and ADSL2+ channel configuration Profile Table, (xdsl2ChConfProfileTable) that applies to DSL bearer channel #3.
(xdsl2ChConfProfileTable) that applies to DSL bearer If the channel is unused, then the object is set to a zero-length
channel #3. If the channel is unused, then the object is set
to a zero length string.
This object may be set to a zero length string only if
xdsl2LConfTempChan4ConfProfile contains a zero length
string. string.
This object may be set to a non-zero length string only if This object may be set to a zero-length string only if
xdsl2LConfTempChan2ConfProfile contains a non-zero length xdsl2LConfTempChan4ConfProfile contains a zero-length string.
This object may be set to a non-zero-length string only if
xdsl2LConfTempChan2ConfProfile contains a non-zero-length
string." string."
DEFVAL { "" } DEFVAL { "" }
::= { xdsl2LineConfTemplateEntry 9 } ::= { xdsl2LineConfTemplateEntry 9 }
xdsl2LConfTempChan3RaRatioDs OBJECT-TYPE xdsl2LConfTempChan3RaRatioDs OBJECT-TYPE
SYNTAX Unsigned32(0..100) SYNTAX Unsigned32(0..100)
UNITS "percents" UNITS "percent"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Rate Adaptation Ratio. The ratio (in %) that should be "Rate Adaptation Ratio. The ratio (in %) that should be
taken into account for the bearer channel #3 when performing taken into account for the bearer channel #3 when performing
rate adaptation on Downstream. The ratio refers to the rate adaptation on Downstream. The ratio refers to the available
available data rate in excess of the Minimum Data Rate, data rate in excess of the Minimum Data Rate, summed over all
summed over all bearer channels. bearer channels.
Also, the 100 - xdsl2LConfTempChan3RaRatioDs is the ratio of Also, the 100 - xdsl2LConfTempChan3RaRatioDs