draft-ietf-adslmib-vdsl2-07.txt   rfc5650.txt 
Network Working Group M. Morgenstern Network Working Group M. Morgenstern
Internet-Draft ECI Telecom Ltd. Request for Comments: 5650 ECI Telecom Ltd.
Intended status: Standards Track S. Baillie Category: Standards Track S. Baillie
Expires: November 13, 2009 U. Bonollo U. Bonollo
NEC Australia NEC Australia
May 12, 2009 September 2009
Definitions of Managed Objects for Very High Speed Digital Subscriber
Line 2 (VDSL2)
draft-ietf-adslmib-vdsl2-07.txt
Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Definitions of Managed Objects for
Task Force (IETF), its areas, and its working groups. Note that Very High Speed Digital Subscriber Line 2 (VDSL2)
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Abstract
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at This document defines a Management Information Base (MIB) module for
http://www.ietf.org/ietf/1id-abstracts.txt. use with network management protocols in the Internet community. In
particular, it describes objects used for managing parameters of the
"Very High Speed Digital Subscriber Line 2 (VDSL2)" interface type,
which are also applicable for managing Asymmetric Digital Subscriber
Line (ADSL), ADSL2, and ADSL2+ interfaces.
The list of Internet-Draft Shadow Directories can be accessed at Status of This Memo
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on November 13, 2009. This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice Copyright and License Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of Provisions Relating to IETF Documents
publication of this document (http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info) in effect on the date of
Please review these documents carefully, as they describe your rights publication of this document. Please review these documents
and restrictions with respect to this document. carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
Abstract include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the BSD License.
This document defines a Management Information Base (MIB) module for RFC 5650 VDSL2-LINE MIB September 2009
use with network management protocols in the Internet community. In
particular, it describes objects used for managing parameters of the
"Very High Speed Digital Subscriber Line 2 (VDSL2)" interface type,
which are also applicable for managing ADSL, ADSL2, and ADSL2+
interfaces.
Table of Contents Table of Contents
1. The Internet-Standard Management Framework . . . . . . . . . 3 1. The Internet-Standard Management Framework ......................2
2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Overview ........................................................2
2.1. Relationship to other MIBs . . . . . . . . . . . . . . . 4 2.1. Relationship to Other MIBs .................................4
2.2. IANA Considerations . . . . . . . . . . . . . . . . . . . 7 2.2. IANA Considerations ........................................7
2.3. Conventions Used in the MIB Module . . . . . . . . . . . 8 2.3. Conventions Used in the MIB Module .........................7
2.4. Structure . . . . . . . . . . . . . . . . . . . . . . . . 10 2.4. Structure .................................................11
2.5. Persistence . . . . . . . . . . . . . . . . . . . . . . . 13 2.5. Persistence ...............................................13
2.6. Line Topology . . . . . . . . . . . . . . . . . . . . . . 16 2.6. Line Topology .............................................16
2.7. Counters, Interval Buckets, and Thresholds . . . . . . . 16 2.7. Counters, Interval Buckets, and Thresholds ................17
2.8. Profiles . . . . . . . . . . . . . . . . . . . . . . . . 18 2.8. Profiles ..................................................19
2.9. Notifications . . . . . . . . . . . . . . . . . . . . . . 22 2.9. Notifications .............................................23
3. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 23 3. Definitions ....................................................24
4. Implementation Analysis . . . . . . . . . . . . . . . . . . . 203 4. Implementation Analysis .......................................204
5. Security Considerations . . . . . . . . . . . . . . . . . . . 204 5. Security Considerations .......................................204
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 212 6. Acknowledgments ...............................................215
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 213 7. References ....................................................216
7.1. Normative References . . . . . . . . . . . . . . . . . . 213 7.1. Normative References .....................................216
7.2. Informative References . . . . . . . . . . . . . . . . . 214 7.2. Informative References ...................................217
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 215
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).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579], and STD 58, RFC 2580
[RFC2580]. [RFC2580].
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
2. Overview 2. Overview
This document defines a Management Information Base (MIB) module for This document defines a Management Information Base (MIB) module for
use with network management protocols in the Internet community for use with network management protocols in the Internet community for
the purpose of managing VDSL2, ADSL, ADSL2, and ADSL2+ lines. the purpose of managing VDSL2, ADSL, ADSL2, and ADSL2+ lines.
RFC 5650 VDSL2-LINE MIB September 2009
The MIB module described in RFC 2662 [RFC2662] describes objects used The MIB module described in RFC 2662 [RFC2662] describes objects used
for managing Asymmetric Bit-Rate DSL (ADSL) interfaces per for managing Asymmetric Bit-Rate DSL (ADSL) interfaces per
[T1E1.413], [G.992.1], and [G.992.2]. These object descriptions are [T1E1.413], [G.992.1], and [G.992.2]. These object descriptions are
based upon the specifications for the ADSL Embedded Operations based upon the specifications for the ADSL Embedded Operations
Channel (EOC) as defined in American National Standards Institute Channel (EOC) as defined in American National Standards Institute
(ANSI) T1E1.413/1995 [T1E1.413] and International Telecommunication (ANSI) T1E1.413/1995 [T1E1.413] and International Telecommunication
Union (ITU-T) G.992.1 [G.992.1] and G.992.2 [G.992.2]. Union (ITU-T) G.992.1 [G.992.1] and G.992.2 [G.992.2].
The MIB module described in RFC 4706 [RFC4706] is a wider management The MIB module described in RFC 4706 [RFC4706] is a wider management
model that includes, in addition to ADSL technology, the ADSL2 and model that includes, in addition to ADSL technology, the ADSL2 and
ADSL2+ technologies per G.992.3, G.992.4, and G.992.5 ([G.992.3], ADSL2+ technologies per G.992.3, G.992.4, and G.992.5 ([G.992.3],
[G.992.4], and [G.992.5] respectively). [G.992.4], and [G.992.5], respectively).
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.
This document does not obsolete RFC 2662 [RFC2662], or RFC 4706 This document does not obsolete RFC 2662 [RFC2662] or RFC 4706
[RFC4706]. RFC2662 is relevant only for managing modems that do not [RFC4706]. RFC 2662 is relevant only for managing modems that do not
support any DSL technology other than ADSL (e.g., G.992.1 [G.992.1] support any DSL technology other than ADSL (e.g., G.992.1 [G.992.1]
and G.992.2 [G.992.2]) especially if were produced prior to approval and G.992.2 [G.992.2]) especially if the modems were produced prior
of ITU-T G.997.1 standard revision 3 [G.997.1]. RFC 4706 is more to approval of ITU-T G.997.1 standard revision 3 [G.997.1]. RFC 4706
appropriate for managing modems that support ADSL2 technology is more appropriate for managing modems that support ADSL2 technology
variants (with or without being able to support the legacy ADSL). variants (with or without being able to support the legacy ADSL).
This document supports all ADSL, ASDSL2 and VDSL2 standards but it This document supports all ADSL, ADSL2, and VDSL2 standards, but it
assumes a more sophisticated management model, which older modems assumes a more sophisticated management model, which older modems
(even ADSL2 ones) may not be able to support. The selection of the (even ADSL2 ones) may not be able to support. The selection of the
appropriate MIB mopdule for any DSL modem is based on the ifType appropriate MIB module for any DSL modem is based on the ifType value
value it reports, as explained in the next section. it reports, as explained in the next section.
The management framework for VDSL2 lines [TR-129] specified by the The management framework for VDSL2 lines [TR-129] specified by the
Digital Subscriber Line Forum (DSLF) has been taken into Digital Subscriber Line Forum (DSLF) has been taken into
consideration. That framework is based on ITU-T G.997.1 standard consideration. That framework is based on the ITU-T G.997.1 standard
[G.997.1] and its amendment 1 [G.997.1-Am1]. [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 RFC 5650 VDSL2-LINE MIB September 2009
2.1. Relationship to Other MIBs
This section outlines the relationship of this MIB module with other This section outlines the relationship of this MIB module with other
MIB modules described in RFCs. Specifically, IF-MIB as defined in MIB modules described in RFCs. Specifically, IF-MIB as defined in
RFC 2863 [RFC2863] and ENITY-MIB as defined in RFC 4133 [RFC4133] are RFC 2863 [RFC2863] and ENTITY-MIB as defined in RFC 4133 [RFC4133]
discussed. are discussed.
2.1.1. Relationship with IF-MIB (RFC 2863) 2.1.1. Relationship with IF-MIB (RFC 2863)
2.1.1.1. General IF-MIB Integration 2.1.1.1. General IF-MIB Integration
The VDSL2 Line MIB specifies the detailed objects of a data The VDSL2 Line MIB specifies the detailed objects of a data
interface. As such, it needs to integrate with RFC 2863 [RFC2863]. interface. As such, it needs to integrate with RFC 2863 [RFC2863].
The IANA has assigned the following ifTypes, which may be applicable The IANA has assigned the following ifTypes, which may be applicable
for VDSL2 lines as well as for ADSL, ADSL2 and ADSL2+ lines: for VDSL2 lines as well as for ADSL, ADSL2, and ADSL2+ lines:
IANAifType ::= TEXTUAL-CONVENTION IANAifType ::= TEXTUAL-CONVENTION
... ...
SYNTAX INTEGER { SYNTAX INTEGER {
... ...
channel(70), -- Channel channel(70), -- Channel
adsl(94), -- Asymmetric Digital Subscriber Loop adsl(94), -- Asymmetric Digital Subscriber Loop
... ...
interleave(124), -- Interleaved Channel interleave(124), -- Interleaved Channel
fast(125), -- Fast Channel fast(125), -- Fast Channel
... ...
adsl2plus(238), -- Asymmetric Digital Subscriber Loop Version 2, adsl2plus(238), -- Asymmetric Digital Subscriber Loop Version 2,
Version 2 Plus, and all variants Version 2 Plus, and all variants
vdsl2(xxx), -- Very High Speed Digital Subscriber Loop 2 vdsl2(251), -- Very High Speed Digital Subscriber Loop 2
... ...
} }
ADSL lines that are identified with ifType=adsl(94) MUST be managed ADSL lines that are identified with ifType=adsl(94) MUST be managed
with the MIB specified by RFC2662. ADSL, ADSL2, and ADSL2+ lines with the MIB specified by RFC 2662. ADSL, ADSL2, and ADSL2+ lines
identified with ifType=adsl2plus(238) MUST be managed with the MIB identified with ifType=adsl2plus(238) MUST be managed with the MIB
specified by RFC 4706 [RFC4706]. VDSL2, ADSL, ADSL2, and ADSL2+ specified by RFC 4706 [RFC4706]. VDSL2, ADSL, ADSL2, and ADSL2+
lines identified with ifType=vdsl2(xxx) MUST be managed with the MIB lines identified with ifType=vdsl2(251) MUST be managed with the MIB
specified by this document. specified by this document.
In any case, the SNMP agent may use either ifType=interleave(124) or In any case, the SNMP agent may use either ifType=interleave(124) or
fast(125) for each channel, e.g., depending on whether or not it is fast(125) for each channel, e.g., depending on whether or not it is
capable of using an interleaver on that channel. It may use the capable of using an interleaver on that channel. It may use the
ifType=channel (70) when all channels are capable of using an ifType=channel (70) when all channels are capable of using an
interleaver (e.g., for ADSL2 xTUs). interleaver (e.g., for ADSL2 xTUs).
Note that the ifFixedLengthGroup from RFC 2863 [RFC2863] MUST be Note that the ifFixedLengthGroup from RFC 2863 [RFC2863] MUST be
supported and that the ifRcvAddressGroup does not apply to this MIB supported and that the ifRcvAddressGroup does not apply to this MIB
module. module.
RFC 5650 VDSL2-LINE MIB September 2009
2.1.1.2. Usage of ifTable 2.1.1.2. Usage of ifTable
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 objects are part of the mandatory The following objects 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), channel(70), ifType vdsl2(251), channel(70),
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 ifPhysAddress This object MUST have an octet
string with zero length. string with zero length.
ifAdminStatus See interfaces MIB. ifAdminStatus See interfaces MIB.
ifOperStatus See interfaces MIB. ifOperStatus See interfaces MIB.
skipping to change at page 6, line 39 skipping to change at page 5, line 53
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.1.3. Usage of ifStackTable 2.1.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 the ifStackTable is necessary because configuration
is stored in profile tables associated with the physical-layer information is stored in profile tables associated with the physical-
ifEntry only. The channels' ifEntrys need the ifStackTable to find
their associated physical-layer entry and thus their configuration RFC 5650 VDSL2-LINE MIB September 2009
parameters. The following example shows the ifStackTable entries for
an xDSL line with a single channel that uses an ATM data path. layer ifEntry only. The channels' ifEntrys need the ifStackTable to
find their associated physical-layer entry and thus their
configuration parameters. The following example shows the
ifStackTable entries for an xDSL line with a single channel that uses
an ATM data path.
HigherLayer LowerLayer HigherLayer LowerLayer
----------------------------- -----------------------------
0 ATM 0 ATM
ATM XdslChannel ATM XdslChannel
XdslChannel XdslPhysical XdslChannel XdslPhysical
XdslPhysical 0 XdslPhysical 0
Figure 2: ifStackTable entries for ATM path over a single xDSL Figure 2: ifStackTable Entries for ATM Path over a Single xDSL
channel Channel
2.1.2. Relationship with the ENTITY-MIB (RFC 4133) 2.1.2. Relationship with the ENTITY-MIB (RFC 4133)
Implementation of the Entity MIB [RFC4133] is optional. It in no way Implementation of the Entity MIB [RFC4133] is optional. It in no way
alters the information required in the VDSL2 Line MIB, nor does it alters the information required in the VDSL2 Line MIB, nor does it
alter the relationship with IF-MIB. alter the relationship with IF-MIB.
The Entity MIB introduces a standardized way of presenting the The Entity MIB introduces a standardized way of presenting the
components of complex systems, such as a Digital Subscriber Line components of complex systems, such as a Digital Subscriber Line
Access Multiplexer (DSLAM), that may contain multiple racks, shelves, Access Multiplexer (DSLAM), that may contain multiple racks, shelves,
line cards, and/or ports. The Entity MIB's main goal is to present line cards, and/or ports. The Entity MIB's main goal is to present
these system components, their containment relationship, and mapping these system components, their containment relationship, and mapping
information with other MIBs such as the Interface MIB and the VDSL2 information with other MIBs such as the Interface MIB and the VDSL2
Line MIB. Line MIB.
The Entity MIB is capable of supporting the local DSL termination The Entity MIB is capable of supporting the local DSL termination
unit. Thus, assuming the SNMP agent is in the DSLAM, the Entity MIB unit. Thus, assuming the SNMP agent is in the DSLAM, the Entity MIB
should include entities for the xTU-C in the entPhysicalTable. The should include entities for the xTU-C in the entPhysicalTable. The
MIB's entAliasMappingTable would contain mapping information MIB's entAliasMappingTable would contain mapping information
identifying the 'ifIndex' object associated with each xTU-C. In case identifying the 'ifIndex' object associated with each xTU-C. In case
the SNMP agent is actually in the CPE the Entity MIB should include the SNMP agent is actually in the Customer Premise Equipment (CPE),
entities for the xTU-R in the entPhysicalTable. In this case, the the Entity MIB should include entities for the xTU-R in the
MIB's entAliasMappingTable would contain mapping information entPhysicalTable. In this case, the MIB's entAliasMappingTable would
identifying the 'ifIndex' object associated with each xTU-R. contain mapping information identifying the 'ifIndex' object
associated with each xTU-R.
Also associating the relationship between the ifTable and Entity MIB, Also associating the relationship between the ifTable and Entity MIB,
the entPhysicalTable contains an 'entPhysicalName' object, which the entPhysicalTable contains an 'entPhysicalName' object, which
approximates the semantics of the 'ifName' object from the Interface approximates the semantics of the 'ifName' object from the Interface
MIB. MIB.
RFC 5650 VDSL2-LINE MIB September 2009
2.2. IANA Considerations 2.2. IANA Considerations
The VDSL2-LINE-MIB module requires the allocation of a new ifType A new ifType value (251) for Very High Speed Digital Subscriber Loop
value for Very High Speed Digital Subscriber Loop Version 2, to Version 2 has been allocated for the VDSL2-LINE-MIB module, to
distinguish between ADSL lines that are managed with the RFC2662 distinguish between ADSL lines that are managed with the RFC 2662
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 has been assigned a single object
object identifier for its MODULE-IDENTITY. The IANA should allocate identifier (251) for its MODULE-IDENTITY. The IANA has allocated
this object identifier in the transmission subtree. this object identifier in the transmission subtree.
As performed in the past for the ADSL2-LINE-MIB module, the IANA is As performed in the past for the ADSL2-LINE-MIB module, the IANA has
kindly requested to ensure that the allocated ifType value is the ensured that the allocated ifType value is the same as the allocated
same as the allocated branch number in the transmission subtree. branch number 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
ADSL Asymmetric (bit rate) DSL ADSL Asymmetric (bit rate) DSL
ATM Asynchronous Transfer Mode ATM Asynchronous Transfer Mode
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
BER Bit Error Rate BER Bit Error Rate
CO Central Office CO Central Office
CPE Customer Premise Equipment CPE Customer Premise Equipment
CRC Cyclic Redundancy Check CRC Cyclic Redundancy Check
DELT Dual Ended Loop Test DELT Dual Ended Loop Test
DMT Discrete Multitone DMT Discrete Multitone
DPBO Downstream PBO DPBO Downstream PBO
DRA Dynamic Rate Adaptation DRA Dynamic Rate Adaptation
DSL Digital Subscriber Line/Loop DSL Digital Subscriber Line/Loop
DSLF DSL Forum DSLF DSL Forum
EOC Embedded Operations Channel EOC Embedded Operations Channel
ES Errored Second ES Errored Second
FE Far-End (unit) FE Far-End (unit)
FEBE Far-End Block Error FEBE Far-End Block Error
FEC Forward Error Correction FEC Forward Error Correction
FFEC Far-End FEC FFEC Far-End FEC
IMA Inverse Multiplexing over ATM IMA Inverse Multiplexing over ATM
INP Inpulse Noise Protection INP Impulse Noise Protection
ISDN Integrated Services Digital Network ISDN Integrated Services Digital Network
LDSF Loop Diagnostic State Forced LDSF Loop Diagnostic State Forced
LOF Loss Of Frame
LOS Loss Of Signal RFC 5650 VDSL2-LINE MIB September 2009
LOSS LOS Seconds
LPR Loss of Power LOF Loss Of Frame
NE Netwrok Element or Near-End (unit) LOS Loss Of Signal
NSC Highest transmittible subcarriers index LOSS LOS Seconds
NSCds NSC for downstream transmission direction LPR Loss of Power
NSCus NSC for upstream transmission direction NE Network Element or Near-End (unit)
OLR Online Reconfiguration NSC Highest transmittable subcarriers index
PBO Power Backoff NSCds NSC for downstream transmission direction
PM Performance Monitoring NSCus NSC for upstream transmission direction
PMS-TC Physical Media Specific-Transmission Convergence OLR Online Reconfiguration
POTS Plain Old Telephone Service PBO Power Backoff
PSD Power Spectral Density PM Performance Monitoring
PTM Packet Transfer Mode PMS-TC Physical Media Specific-Transmission Convergence
QLN Quiet Line POTS Plain Old Telephone Service
RDI Remote Defect Indication PSD Power Spectral Density
RFI Radio Frequency Interference PTM Packet Transfer Mode
SEF Severely Errored Frame QLN Quiet Line
SES Severely-Errored Second RDI Remote Defect Indication
SNR Signal-to-Noise Ratio RFI Radio Frequency Interference
TC Transmission Convergence (e.g., ATM sub layer) SEF Severely Errored Frame
TCM (TCM-ISDN) Time Compression Multiplexed ISDN SES Severely Errored Second
UAS Unavailable Seconds SNR Signal-to-Noise Ratio
UPBO Upstream PBO TC Transmission Convergence (e.g., ATM sub layer)
US0 Upstream band number 0 TCM (TCM-ISDN) Time Compression Multiplexed ISDN
VDSL Very high speed DSL UAS Unavailable Seconds
vtuc VDSL2 line termination unit - Central office U-C Loop interface-central office end
vtur VDSL2 line termination unit - Remote site UPBO Upstream PBO
xDSL Either VDSL2, ADSL, ADSL2 or ADSL2+ U-R Loop interface-remote side (i.e., subscriber end of the loop)
xTU-C ADSL/ADSL2/ADSL2+ or VDSL2 line termination unit - US0 Upstream band number 0
Central office VDSL Very high speed DSL
xTU-R ADSL/ADSL2/ADSL2+ or VDSL2 line termination unit - VTU-O VDSL2 Transceiver Unit - central office or
Remote site Network Element End
xTU A line termination unit; either an xTU-C or xTU-R VTU-R VTU at the remote site (i.e., subscriber end of the loop)
vtuc VDSL2 line termination unit - central office
vtur VDSL2 line termination unit - Remote site
xDSL Either VDSL2, ADSL, ADSL2 or ADSL2+
xTU-C ADSL/ADSL2/ADSL2+ or VDSL2 line termination unit -
central office
xTU-R ADSL/ADSL2/ADSL2+ or VDSL2 line termination unit -
Remote site
xTU A line termination unit; either an xTU-C or xTU-R
RFC 5650 VDSL2-LINE MIB September 2009
2.3.2. Textual Conventions 2.3.2. Textual Conventions
The following lists the textual conventions defined by VDSL2-LINE-TC- The following lists the textual conventions defined by VDSL2-LINE-TC-
MIB in this document: MIB in this document:
o Xdsl2Unit o Xdsl2Unit
o Xdsl2Direction o Xdsl2Direction
o Xdsl2Band o Xdsl2Band
o Xdsl2TransmissionModeType o Xdsl2TransmissionModeType
o Xdsl2RaMode o Xdsl2RaMode
o Xdsl2InitResult o Xdsl2InitResult
o Xdsl2OperationModes o Xdsl2OperationModes
o Xdsl2PowerMngState o Xdsl2PowerMngState
o Xdsl2ConfPmsForce o Xdsl2ConfPmsForce
o Xdsl2LinePmMode o Xdsl2LinePmMode
o Xdsl2LineLdsf o Xdsl2LineLdsf
o Xdsl2LdsfResult o Xdsl2LdsfResult
o Xdsl2LineBpsc o Xdsl2LineBpsc
o Xdsl2BpscResult o Xdsl2BpscResult
o Xdsl2LineReset o Xdsl2LineReset
o Xdsl2LineProfiles o Xdsl2LineProfiles
o Xdsl2LineClassMask o Xdsl2LineClassMask
o Xdsl2LineLimitMask o Xdsl2LineLimitMask
o Xdsl2LineUs0Disable o Xdsl2LineUs0Disable
o Xdsl2LineUs0Mask o Xdsl2LineUs0Mask
o Xdsl2SymbolProtection o Xdsl2SymbolProtection
o Xdsl2SymbolProtection8 o Xdsl2SymbolProtection8
RFC 5650 VDSL2-LINE MIB September 2009
o Xdsl2MaxBer o Xdsl2MaxBer
o Xdsl2ChInitPolicy o Xdsl2ChInitPolicy
o Xdsl2ScMaskDs o Xdsl2ScMaskDs
o Xdsl2ScMaskUs o Xdsl2ScMaskUs
o Xdsl2CarMask o Xdsl2CarMask
o Xdsl2RfiBands o Xdsl2RfiBands
o Xdsl2PsdMaskDs o Xdsl2PsdMaskDs
o Xdsl2PsdMaskUs o Xdsl2PsdMaskUs
o Xdsl2Tssi o Xdsl2Tssi
o Xdsl2LastTransmittedState o Xdsl2LastTransmittedState
o Xdsl2LineStatus o Xdsl2LineStatus
o Xdsl2ChInpReport o Xdsl2ChInpReport
o Xdsl2ChAtmStatus o Xdsl2ChAtmStatus
o Xdsl2ChPtmStatus o Xdsl2ChPtmStatus
o Xdsl2UpboKLF o Xdsl2UpboKLF
o Xdsl2BandUs o Xdsl2BandUs
o Xdsl2LinePsdMaskSelectUs o Xdsl2LinePsdMaskSelectUs
o Xdsl2LineCeFlag o Xdsl2LineCeFlag
o Xdsl2LineSnrMode o Xdsl2LineSnrMode
o Xdsl2LineTxRefVnDs o Xdsl2LineTxRefVnDs
o Xdsl2LineTxRefVnUs o Xdsl2LineTxRefVnUs
o Xdsl2BitsAlloc o Xdsl2BitsAlloc
o Xdsl2MrefPsdDs o Xdsl2MrefPsdDs
o Xdsl2MrefPsdUs o Xdsl2MrefPsdUs
RFC 5650 VDSL2-LINE MIB September 2009
2.4. Structure 2.4. Structure
The MIB module is structured into the 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 Loop Test (DELT) requested power state or initiating a Dual Ended Loop Test (DELT)
skipping to change at page 11, line 29 skipping to change at page 11, line 53
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, unit and channel levels. It contains the following tables: line, unit, and channel levels. It contains the following tables:
RFC 5650 VDSL2-LINE MIB September 2009
- xdsl2PMLineCurrTable - xdsl2PMLineCurrTable
- xdsl2PMLineInitCurrTable - 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, unit and information relating to VDSL2/ADSL/ADSL2 and ADSL2+ line, unit,
channel levels in 15- minute intervals. It contains the following and channel levels in 15-minute intervals. It contains the
tables: following 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, unit and information relating to VDSL2/ADSL/ADSL2 and ADSL2+ line, unit,
channel levels in 1-day intervals. It contains the following and 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
well as configuration templates. Each configuration template is well as configuration templates. Each configuration template is
comprised of one line configuration profile and one or more comprised of a one-line configuration profile and one or more
channel configuration profiles. This group contains the following channel configuration profiles. This group contains the following
tables: tables:
- xdsl2LineConfTemplateTable - xdsl2LineConfTemplateTable
- xdsl2LineConfProfTable - xdsl2LineConfProfTable
- xdsl2LineConfProfModeSpecTable - xdsl2LineConfProfModeSpecTable
- xdsl2LineConfProfModeSpecBandUsTable - xdsl2LineConfProfModeSpecBandUsTable
- xdsl2ChConfProfileTable - xdsl2ChConfProfileTable
o Alarm Configuration Template and Profile Group: o Alarm Configuration Template and Profile Group:
This group supports MIB objects for defining alarm profiles for This group supports MIB objects for defining alarm profiles for
VDSL2/ADSL/ADSL2 and ADSL2+ lines and channels, as well as alarm VDSL2/ADSL/ADSL2 and ADSL2+ lines and channels, as well as alarm
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:
RFC 5650 VDSL2-LINE MIB September 2009
- xdsl2LineAlarmConfTemplateTable - xdsl2LineAlarmConfTemplateTable
- xdsl2LineAlarmConfProfileTable - xdsl2LineAlarmConfProfileTable
- xdsl2ChAlarmConfProfileTable - xdsl2ChAlarmConfProfileTable
o Notifications Group: o Notifications Group:
This group defines the notifications supported for VDSL2/ADSL/ This group defines the notifications supported for VDSL2/ADSL/
ADSL2 and ADSL2+ lines: ADSL2 and ADSL2+ lines:
- xdsl2LinePerfFECSThreshXtuc - xdsl2LinePerfFECSThreshXtuc
skipping to change at page 13, line 27 skipping to change at page 13, line 38
- xdsl2LinePerfCorrectedThreshXtuc - xdsl2LinePerfCorrectedThreshXtuc
- xdsl2LinePerfCorrectedThreshXtur - xdsl2LinePerfCorrectedThreshXtur
- xdsl2LinePerfFailedFullInitThresh - xdsl2LinePerfFailedFullInitThresh
- xdsl2LinePerfFailedShortInitThresh - xdsl2LinePerfFailedShortInitThresh
- xdsl2LineStatusChangeXtuc - xdsl2LineStatusChangeXtuc
- xdsl2LineStatusChangeXtur - xdsl2LineStatusChangeXtur
2.5. Persistence 2.5. Persistence
All read-create objects and most read-write objects defined in this All read-create objects and most read-write objects defined in this
MIB module SHOULD be stored persistently. Following is an exhaustive MIB module SHOULD be stored persistently. The following is an
list of these persistent objects: exhaustive list of these persistent objects:
xdsl2LineConfTemplate xdsl2LineConfTemplate
xdsl2LineAlarmConfTemplate xdsl2LineAlarmConfTemplate
xdsl2LineCmndConfPmsf xdsl2LineCmndConfPmsf
xdsl2LConfTempTemplateName xdsl2LConfTempTemplateName
xdsl2LConfTempLineProfile xdsl2LConfTempLineProfile
xdsl2LConfTempChan1ConfProfile xdsl2LConfTempChan1ConfProfile
xdsl2LConfTempChan1RaRatioDs xdsl2LConfTempChan1RaRatioDs
xdsl2LConfTempChan1RaRatioUs xdsl2LConfTempChan1RaRatioUs
xdsl2LConfTempChan2ConfProfile xdsl2LConfTempChan2ConfProfile
xdsl2LConfTempChan2RaRatioDs xdsl2LConfTempChan2RaRatioDs
xdsl2LConfTempChan2RaRatioUs xdsl2LConfTempChan2RaRatioUs
xdsl2LConfTempChan3ConfProfile xdsl2LConfTempChan3ConfProfile
xdsl2LConfTempChan3RaRatioDs xdsl2LConfTempChan3RaRatioDs
xdsl2LConfTempChan3RaRatioUs xdsl2LConfTempChan3RaRatioUs
RFC 5650 VDSL2-LINE MIB September 2009
xdsl2LConfTempChan4ConfProfile xdsl2LConfTempChan4ConfProfile
xdsl2LConfTempChan4RaRatioDs xdsl2LConfTempChan4RaRatioDs
xdsl2LConfTempChan4RaRatioUs xdsl2LConfTempChan4RaRatioUs
xdsl2LConfTempRowStatus xdsl2LConfTempRowStatus
xdsl2LConfProfProfileName xdsl2LConfProfProfileName
xdsl2LConfProfScMaskDs xdsl2LConfProfScMaskDs
xdsl2LConfProfScMaskUs xdsl2LConfProfScMaskUs
xdsl2LConfProfVdsl2CarMask xdsl2LConfProfVdsl2CarMask
xdsl2LConfProfRfiBandsDs xdsl2LConfProfRfiBandsDs
xdsl2LConfProfRaModeDs xdsl2LConfProfRaModeDs
skipping to change at page 14, line 43 skipping to change at page 15, line 4
xdsl2LConfProfDpboEsCableModelC xdsl2LConfProfDpboEsCableModelC
xdsl2LConfProfDpboMus xdsl2LConfProfDpboMus
xdsl2LConfProfDpboFMin xdsl2LConfProfDpboFMin
xdsl2LConfProfDpboFMax xdsl2LConfProfDpboFMax
xdsl2LConfProfUpboKL xdsl2LConfProfUpboKL
xdsl2LConfProfUpboKLF xdsl2LConfProfUpboKLF
xdsl2LConfProfUs0Mask xdsl2LConfProfUs0Mask
xdsl2LConfProfRowStatus xdsl2LConfProfRowStatus
xdsl2LConfProfXdslMode xdsl2LConfProfXdslMode
xdsl2LConfProfMaxNomPsdDs xdsl2LConfProfMaxNomPsdDs
RFC 5650 VDSL2-LINE MIB September 2009
xdsl2LConfProfMaxNomPsdUs xdsl2LConfProfMaxNomPsdUs
xdsl2LConfProfMaxNomAtpDs xdsl2LConfProfMaxNomAtpDs
xdsl2LConfProfMaxNomAtpUs xdsl2LConfProfMaxNomAtpUs
xdsl2LConfProfMaxAggRxPwrUs xdsl2LConfProfMaxAggRxPwrUs
xdsl2LConfProfPsdMaskDs xdsl2LConfProfPsdMaskDs
xdsl2LConfProfPsdMaskUs xdsl2LConfProfPsdMaskUs
xdsl2LConfProfPsdMaskSelectUs xdsl2LConfProfPsdMaskSelectUs
xdsl2LConfProfClassMask xdsl2LConfProfClassMask
xdsl2LConfProfLimitMask xdsl2LConfProfLimitMask
xdsl2LConfProfUs0Disabl xdsl2LConfProfUs0Disabl
skipping to change at page 15, line 43 skipping to change at page 16, line 4
xdsl2LAlarmConfTempLineProfile xdsl2LAlarmConfTempLineProfile
xdsl2LAlarmConfTempChan1ConfProfile xdsl2LAlarmConfTempChan1ConfProfile
xdsl2LAlarmConfTempChan2ConfProfile xdsl2LAlarmConfTempChan2ConfProfile
xdsl2LAlarmConfTempChan3ConfProfile xdsl2LAlarmConfTempChan3ConfProfile
xdsl2LAlarmConfTempChan4ConfProfile xdsl2LAlarmConfTempChan4ConfProfile
xdsl2LAlarmConfTempRowStatus xdsl2LAlarmConfTempRowStatus
xdsl2LineAlarmConfProfileName xdsl2LineAlarmConfProfileName
xdsl2LineAlarmConfProfileXtucThresh15MinFecs xdsl2LineAlarmConfProfileXtucThresh15MinFecs
xdsl2LineAlarmConfProfileXtucThresh15MinEs xdsl2LineAlarmConfProfileXtucThresh15MinEs
xdsl2LineAlarmConfProfileXtucThresh15MinSes xdsl2LineAlarmConfProfileXtucThresh15MinSes
RFC 5650 VDSL2-LINE MIB September 2009
xdsl2LineAlarmConfProfileXtucThresh15MinLoss xdsl2LineAlarmConfProfileXtucThresh15MinLoss
xdsl2LineAlarmConfProfileXtucThresh15MinUas xdsl2LineAlarmConfProfileXtucThresh15MinUas
xdsl2LineAlarmConfProfileXturThresh15MinFecs xdsl2LineAlarmConfProfileXturThresh15MinFecs
xdsl2LineAlarmConfProfileXturThresh15MinEs xdsl2LineAlarmConfProfileXturThresh15MinEs
xdsl2LineAlarmConfProfileXturThresh15MinSes xdsl2LineAlarmConfProfileXturThresh15MinSes
xdsl2LineAlarmConfProfileXturThresh15MinLoss xdsl2LineAlarmConfProfileXturThresh15MinLoss
xdsl2LineAlarmConfProfileXturThresh15MinUas xdsl2LineAlarmConfProfileXturThresh15MinUas
xdsl2LineAlarmConfProfileThresh15MinFailedFullInt xdsl2LineAlarmConfProfileThresh15MinFailedFullInt
xdsl2LineAlarmConfProfileThresh15MinFailedShrtInt xdsl2LineAlarmConfProfileThresh15MinFailedShrtInt
xdsl2LineAlarmConfProfileRowStatus xdsl2LineAlarmConfProfileRowStatus
skipping to change at page 16, line 18 skipping to change at page 16, line 30
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.
RFC 5650 VDSL2-LINE MIB September 2009
<-- 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.
RFC 5650 VDSL2-LINE MIB September 2009
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 and (i.e., FEC events), there are event counters, current 15-minute
0 to 96 15-minute history bucket(s) of "interval- counters", as and 0 to 96 15-minute history bucket(s) of "interval-counters", as
well as current and 0 to 30 previous 1-day interval- counter(s). well as current and 0 to 30 previous 1-day interval-counter(s).
Each current 15-minute event bucket has an associated threshold Each current 15-minute event bucket has an associated 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 bucket. 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 1-day
day intervals with the start of a 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
the value of the event bucket. the value of the event bucket.
A valid 15-minute event bucket SHOULD usually count the events for A valid 15-minute event bucket SHOULD usually count the events for
exactly 15 minutes. Similarly, a valid 1-day event bucket SHOULD exactly 15 minutes. Similarly, a valid 1-day event bucket SHOULD
usually count the events for exactly 24 hours. However, the usually count the events for exactly 24 hours. However, the
following scenarios are exceptional: following scenarios are exceptional:
RFC 5650 VDSL2-LINE MIB September 2009
1) For implementations that align the 15-minute intervals with 1) For implementations that align the 15-minute intervals with
quarter hours, and the 1-day intervals with start of a day, the quarter hours and the 1-day intervals with start of a day, the
management system may still start the PM process not aligned with management system may still start the PM process not aligned with
the wall clock. Such a management system may wish to retrieve the wall clock. Such a management system may wish to retrieve
even partial information for the first event buckets, rather than even partial information for the first event buckets, rather than
declaring them all as invalid. declaring them all as invalid.
2) For an event bucket that suffered relatively short outages, the 2) For an event bucket that suffered relatively short outages, the
management system may wish to retrieve the available PM outcomes, management system may wish to retrieve the available PM outcomes,
rather than declaring the whole event bucket as invalid. This is rather than declaring the whole event bucket as invalid. This is
more important for 1-day event buckets. more important for 1-day event buckets.
3) An event bucket may be shorter or longer than the formal duration 3) An event bucket may be shorter or longer than the formal duration
if a clock adjustment was performed during the interval. if a clock adjustment was performed during the interval.
This MIB module allows supporting the exceptional scenarios described This MIB module allows supporting the exceptional scenarios described
above by reporting the actual Monitoring Time of a monitoring above by reporting the actual Monitoring Time of a monitoring
interval. This parameter is relevant only for Valid intervals, but interval. This parameter is relevant only for Valid intervals, but
is useful for these exceptional scenarios: is useful for these exceptional scenarios:
a) The management system MAY still declare a partial PM interval as a) The management system MAY still declare a partial PM interval as
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, in addition to reporting that the
is Valid. interval 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 is a configuration profile to address line- multiple entities. There is a configuration profile to address line-
level provisioning and another type of profile that addresses level provisioning and another type of profile that addresses
channel-level provisioning parameters. channel-level provisioning parameters.
A configuration template is actually a profile-of-profiles. That is, A configuration template is actually a profile-of-profiles. That is,
a template is comprised of one line configuration profile and one or a template is comprised of one-line configuration profile and one 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.
RFC 5650 VDSL2-LINE MIB September 2009
In a similar manner to the configuration profiles and templates, this In a similar manner to the configuration profiles and templates, this
MIB module makes use of templates and profiles for specifying the MIB module makes use of templates and profiles for specifying the
alarm thresholds associated with performance parameters. This allows alarm 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
line-level parameters for configuring VDSL2/ADSL/ADSL2 and ADSL2+ line-level parameters for configuring VDSL2/ADSL/ADSL2 and ADSL2+
lines. They are defined in the xdsl2LineConfProfTable. lines. They are defined in the xdsl2LineConfProfTable.
The line configuration includes settings such as the specific The line configuration includes settings such as the specific
VDSL2/ADSL/ADSL2 or ADSL2+ modes to enable on the respective line, VDSL2/ADSL/ADSL2 or ADSL2+ modes to enable on the respective line,
power spectrum parameters, rate adaptation criteria, and SNR power spectrum parameters, rate adaptation criteria, and SNR
margin-related parameters. A subset of the line configuration margin-related parameters. A subset of the line configuration
parameters depends upon the specific xDSL Mode allowed (i.e., Does parameters depends upon the specific xDSL Mode allowed (i.e., does
the profile allow VDSL2, ADSL, ADSL2 and/or ADSL2+?) as well as the profile allow VDSL2, ADSL, ADSL2 and/or ADSL2+?) as well as
what annex/annexes of the standard are allowed. This is the what annex/annexes of the standard are allowed. This is the
reason a line profile MUST include one or more mode-specific reason a line profile MUST include one or more mode-specific
extensions. 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.
skipping to change at page 20, line 12 skipping to change at page 20, line 49
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 into a comprehensive configuration of the VDSL2/ADSL/ profiles into a comprehensive configuration of the VDSL2/ADSL/
ADSL2 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 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 indices 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
RFC 5650 VDSL2-LINE MIB September 2009
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. For example, there are thresholds for failed
and LOS seconds, but not for the aggregate number of full initializations and LOS seconds, but not for the aggregate number
initializations. These profiles are defined in the of full 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 into a and channel-level alarm configuration profiles into a
comprehensive configuration of the PM thresholds for the VDSL2/ comprehensive configuration of the PM thresholds for the VDSL2/
ADSL/ADSL2 and ADSL2+ line. They are defined in the ADSL/ADSL2 and ADSL2+ line. They are defined in the
xdsl2LineAlarmConfTemplateTable. xdsl2LineAlarmConfTemplateTable.
The line alarm configuration template includes one index of a The line alarm configuration template includes one index of a
line-level alarm configuration profile and one to four indexes of line-level alarm configuration profile and one to four indices 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 xdsl2LineConfTemplate object to the value of this by setting its xdsl2LineConfTemplate 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 xdsl2LineAlarmConfTemplate object to the 'silver') by setting its xdsl2LineAlarmConfTemplate object to the
value of this template. value of this template.
RFC 5650 VDSL2-LINE MIB September 2009
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.
skipping to change at page 21, line 44 skipping to change at page 22, line 35
Profiles and templates are created, assigned, and deleted dynamically Profiles and templates are created, assigned, and deleted dynamically
using the profile name and profile row status in each of the profile using the profile name and profile row status in each of the profile
tables. tables.
If the implementation allows modifying a profile or template while it If the implementation allows modifying a profile or template while it
is associated with a line, then such changes MUST take effect is associated with a line, then such changes MUST take effect
immediately. These changes MAY result in a restart (hard reset or immediately. These changes MAY result in a restart (hard reset or
soft restart) of the units on the line. soft restart) of the units on the line.
Network Elements MAY optionaly implement a fallback line Network Elements MAY optionally implement a fallback line
configuration template ( See xdsl2LineConfFallbackTemplate ). The configuration template (see xdsl2LineConfFallbackTemplate). The
fallback template will be tried if the xDSL2 line fails to operate fallback template will be tried if the xDSL2 line fails to operate
using the primary template. If the xDSL2 line fails to operate using using the primary template. If the xDSL2 line fails to operate using
the fallback template then the primary template should be retried. the fallback template, then the primary template should be retried.
The xTU-C SHOULD continue to alternate between the primary and The xTU-C SHOULD continue to alternate between the primary and
fallback templates until one of them succeeds. fallback templates until one of them succeeds.
2.8.4. Managing Multiple Bearer Channels 2.8.4. Managing Multiple Bearer Channels
The number of bearer channels is configured by setting the template The number of bearer channels is configured by setting the template
objects xdsl2LConfTempChan1ConfProfile, objects 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 xdsl2LineConfTemplate object. When the number of DSL line using the xdsl2LineConfTemplate object. When the number of
bearer channels for a DSL line changes, the SNMP agent will 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
RFC 5650 VDSL2-LINE MIB September 2009
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
that line. 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.
2.9. Notifications 2.9. Notifications
The ability to generate the SNMP notifications coldStart/WarmStart The ability to generate the SNMP notifications coldStart/WarmStart
(per [RFC3418]), which are per agent (e.g., per Digital Subscriber (per [RFC3418]), which are per agent (e.g., per Digital Subscriber
Line Access Multiplexer, or DSLAM, in such a device), and linkUp/ Line Access Multiplexer, or DSLAM, in such a device), and linkUp/
linkDown (per [RFC2863]), which are per interface (i.e., VDSL2/ADSL/ linkDown (per [RFC2863]), which are per interface (i.e., VDSL2/ADSL/
ADSL2 or ADSL2+ line) is required. ADSL2 or ADSL2+ line) is required.
A linkDown notification MAY be generated whenever any of ES, SES, CRC A linkDown notification MAY be generated whenever any of ES, SES, CRC
Anomaly, LOS, LOF, or UAS event occurs. The corresponding linkUp anomaly, LOS, LOF, or UAS events occur. The corresponding linkUp
notification MAY be sent when all link failure conditions are notification MAY be sent when all link failure conditions are
cleared. cleared.
The notifications defined in this MIB module are for 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, LOS Seconds, UAS, FEC short initialization failures, ES, SES, LOS seconds, UAS, FEC
Seconds, FEC events, and CRC anomalies. Each threshold has its own seconds, FEC events, and CRC anomalies. Each threshold has its own
enable/threshold value. When that value is 0, the notification is enable/threshold value. When that value is 0, the notification is
disabled. 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
xTU-R and xTU-C (respectively). Note that since the xTU-R 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
xTU-R 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.
RFC 5650 VDSL2-LINE MIB September 2009
Note that there are other status parameters that refer to the xTU-R 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.
Note that the Network Management System, or NMS, may receive a Note that the Network Management System, or NMS, may receive a
linkDown notification, as well, if enabled (via linkDown notification, as well, if enabled (via
ifLinkUpDownTrapEnable [RFC2863]). At the beginning of the next 15 ifLinkUpDownTrapEnable [RFC2863]). At the beginning of the next 15-
minute interval, the counter is reset. When the first second goes by minute interval, the counter is reset. When the first second goes by
and the event occurs, the current interval bucket will be 1, which and the event occurs, the current interval bucket will be 1, which
equals the threshold, and the notification will be sent again. equals the threshold, and the notification will be sent again.
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 "200905100000Z" -- May 10, 2009 LAST-UPDATED "200909300000Z" -- September 30, 2009
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
Co-Chair: Menachem Dodge Co-Chair: Menachem Dodge
RFC 5650 VDSL2-LINE MIB September 2009
ECI Telecom Ltd. ECI Telecom Ltd.
Postal: 30 Hasivim St. Postal: 30 Hasivim St.
Petach Tikva 49517, Petach Tikva 49517,
Israel. Israel.
Email: mbdodge@ieee.org Email: mbdodge@ieee.org
Phone: +972 3 926 8421 Phone: +972 3 926 8421
Co-editor: Moti Morgenstern Co-editor: Moti Morgenstern
ECI Telecom Ltd. ECI Telecom Ltd.
Postal: 30 Hasivim St. Postal: 30 Hasivim St.
skipping to change at page 24, line 48 skipping to change at page 25, line 41
NEC Australia NEC Australia
Postal: 649-655 Springvale Road, Postal: 649-655 Springvale Road,
Mulgrave, Victoria 3170, Mulgrave, Victoria 3170,
Australia. Australia.
Email: umberto.bonollo@nec.com.au Email: umberto.bonollo@nec.com.au
Phone: +61 3 9264 3385 Phone: +61 3 9264 3385
" "
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) 2009 IETF Trust and the persons
this MIB module is part of RFC XXXX: see the RFC itself for identified as authors of the code. All rights
full legal notices." reserved.
REVISION "200905100000Z" -- May 10, 2009 Redistribution and use in source and binary
DESCRIPTION "Initial version, published as RFC XXXX." forms, with or without modification, are
::= { transmission yyy 2} -- vdsl2MIB 2 permitted provided that the following
conditions are met:
- Redistributions of source code must retain the
above copyright notice, this list of conditions
and the following disclaimer.
RFC 5650 VDSL2-LINE MIB September 2009
- Redistributions in binary form must reproduce
the above copyright notice, this list of
conditions and the following disclaimer in
the documentation and/or other materials provided
with the distribution.
- Neither the name of Internet Society, IETF or
IETF Trust, nor the names of specific contributors,
may be used to endorse or promote products derived
from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
CONTRIBUTORS 'AS IS' AND ANY EXPRESS OR IMPLIED
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This version of this MIB module is part of RFC 5650;
see the RFC itself for full legal notices."
REVISION "200909300000Z" -- September 30, 2009
DESCRIPTION "Initial version, published as RFC 5650."
::= { transmission 251 3} -- vdsl2MIB 3
------------------------------------------------ ------------------------------------------------
-- Textual Conventions -- -- Textual Conventions --
------------------------------------------------ ------------------------------------------------
Xdsl2Unit ::= TEXTUAL-CONVENTION Xdsl2Unit ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Identifies a transceiver as being either xTU-C or xTU-R. "Identifies a transceiver as being either xTU-C or xTU-R.
A VDSL2/ADSL/ADSL2 or ADSL2+ line consists of two A VDSL2/ADSL/ADSL2 or ADSL2+ line consists of two
transceivers, an xTU-C and an xTU-R. transceivers: an xTU-C and an xTU-R.
In the case of ADSL/ADSL2 and ADSL2+ those two transceivers are In the case of ADSL/ADSL2 and ADSL2+, those two transceivers are
also called atuc and atur. also called atuc and atur.
In the case of VDSL2 those two transceivers are also called In the case of VDSL2, those two transceivers are also called
vtuc and vtur. vtuc and vtur.
RFC 5650 VDSL2-LINE MIB September 2009
Specified as an INTEGER, the two values are: 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 in a VDSL2/ADSL/ADSL2/ "Identifies the direction of a band in a VDSL2/ADSL/ADSL2/
ADSL2+ link. ADSL2+ link.
The upstream direction is a transmission from the remote end The upstream direction is a transmission from the remote end
(xTU-R) towards the central office end (xTU-C). The downstream (xTU-R) towards the central office end (xTU-C). The downstream
direction is a transmission from the xTU-C towards the xTU-R. direction is a transmission from the xTU-C towards the xTU-R.
Specified as an INTEGER, the values are defined as Specified as an INTEGER, the values are defined as
follows:" 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 VDSL2/ADSL/ADSL2/ADSL2+ link. "Identifies a band in a VDSL2/ADSL/ADSL2/ADSL2+ link.
For a band in the upstream direction, transmission is from the For a band in the upstream direction, transmission is from the
remote end (xTU-R) towards the central office end (xTU-C). remote end (xTU-R) towards the central office end (xTU-C).
For a band in the downstream direction, transmission is from For a band in the downstream direction, transmission is from
the xTU-C towards the xTU-R. the xTU-C towards the xTU-R.
For ADSL, ADSL2 and ADSL2+, which use a single band in the For ADSL, ADSL2 and ADSL2+, which use a single band in the
upstream direction and a single band upstream direction and a single band
in the downstream direction, in the downstream direction,
the only relevant values are upstream(1) and downstream(2). the only relevant values are upstream(1) and downstream(2).
For VDSL2, which uses multiple bands in each transmission For VDSL2, which uses multiple bands in each transmission
direction, a band in the upstream direction is indicated by any direction, a band 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 of us0(3), us1(5), us2(7), us3(9), or us4(11), and a band in
downstream direction is indicated by any of ds1(4), ds2(6), the downstream direction is indicated by any of ds1(4),
ds3(8) or ds4(10). ds2(6), ds3(8), or ds4(10).
For VDSL2, the values upstream(1) and downstream(2) may be used For VDSL2, the values upstream(1) and downstream(2) may be used
when there is a need to refer to the whole upstream or when there is a need to refer to the whole upstream or
downstream traffic (e.g., report the average signal-to-noise downstream traffic (e.g., report the average signal-to-noise
ratio on any transmission direction). ratio on any transmission direction).
Specified as an INTEGER, the values are defined as Specified as an INTEGER, the values are defined as
follows:" 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
RFC 5650 VDSL2-LINE MIB September 2009
-- (refers to the single upstream band for -- (refers to the single upstream band for
-- ADSL/ADSL2/ADSL2+ or 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+ or 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).
skipping to change at page 27, line 8 skipping to change at page 28, line 30
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 and per mode. The notes (F) and (L) denote Full-Rate 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 27, line 33 skipping to change at page 29, line 4
Bit 18 : G.992.3 POTS non-overlapped (F) Bit 18 : G.992.3 POTS non-overlapped (F)
Bit 19 : G.992.3 POTS overlapped (F) Bit 19 : G.992.3 POTS overlapped (F)
Bit 20 : G.992.3 ISDN non-overlapped (F) Bit 20 : G.992.3 ISDN non-overlapped (F)
Bit 21 : G.992.3 ISDN overlapped (F) Bit 21 : G.992.3 ISDN overlapped (F)
Bit 22-23: Reserved Bit 22-23: Reserved
Bit 24 : G.992.4 POTS non-overlapped (L) Bit 24 : G.992.4 POTS non-overlapped (L)
Bit 25 : G.992.4 POTS overlapped (L) Bit 25 : G.992.4 POTS overlapped (L)
Bit 26-27: Reserved Bit 26-27: Reserved
Bit 28 : G.992.3 Annex I All-Digital non-overlapped (F) Bit 28 : G.992.3 Annex I All-Digital non-overlapped (F)
Bit 29 : G.992.3 Annex I All-Digital overlapped (F) Bit 29 : G.992.3 Annex I All-Digital overlapped (F)
RFC 5650 VDSL2-LINE MIB September 2009
Bit 30 : G.992.3 Annex J All-Digital non-overlapped (F) Bit 30 : G.992.3 Annex J All-Digital non-overlapped (F)
Bit 31 : G.992.3 Annex J All-Digital overlapped (F) Bit 31 : G.992.3 Annex J All-Digital overlapped (F)
Bit 32 : G.992.4 Annex I All-Digital non-overlapped (L) Bit 32 : G.992.4 Annex I All-Digital non-overlapped (L)
Bit 33 : G.992.4 Annex I All-Digital overlapped (L) Bit 33 : G.992.4 Annex I All-Digital overlapped (L)
Bit 34 : G.992.3 Annex L POTS non-overlapped, mode 1, Bit 34 : G.992.3 Annex L POTS non-overlapped, mode 1,
wide U/S (F) wide U/S (F)
Bit 35 : G.992.3 Annex L POTS non-overlapped, mode 2, Bit 35 : G.992.3 Annex L POTS non-overlapped, mode 2,
narrow U/S(F) narrow U/S(F)
Bit 36 : G.992.3 Annex L POTS overlapped, mode 3, Bit 36 : G.992.3 Annex L POTS overlapped, mode 3,
wide U/S (F) wide U/S (F)
skipping to change at page 28, line 32 skipping to change at page 30, line 4
g9921tcmIsdnNonOverlapped(6), g9921tcmIsdnNonOverlapped(6),
g9921tcmIsdnOverlapped(7), g9921tcmIsdnOverlapped(7),
g9922potsNonOverlapped(8), g9922potsNonOverlapped(8),
g9922potsOverlapped(9), g9922potsOverlapped(9),
g9922tcmIsdnNonOverlapped(10), g9922tcmIsdnNonOverlapped(10),
g9922tcmIsdnOverlapped(11), g9922tcmIsdnOverlapped(11),
g9921tcmIsdnSymmetric(12), g9921tcmIsdnSymmetric(12),
reserved1(13), reserved1(13),
reserved2(14), reserved2(14),
reserved3(15), reserved3(15),
RFC 5650 VDSL2-LINE MIB September 2009
reserved4(16), reserved4(16),
reserved5(17), reserved5(17),
g9923PotsNonOverlapped(18), g9923PotsNonOverlapped(18),
g9923PotsOverlapped(19), g9923PotsOverlapped(19),
g9923IsdnNonOverlapped(20), g9923IsdnNonOverlapped(20),
g9923isdnOverlapped(21), g9923isdnOverlapped(21),
reserved6(22), reserved6(22),
reserved7(23), reserved7(23),
g9924potsNonOverlapped(24), g9924potsNonOverlapped(24),
g9924potsOverlapped(25), g9924potsOverlapped(25),
skipping to change at page 29, line 32 skipping to change at page 31, line 4
reserved14(54), reserved14(54),
reserved15(55), reserved15(55),
g9932AnnexA(56), g9932AnnexA(56),
g9932AnnexB(57), g9932AnnexB(57),
g9932AnnexC(58), g9932AnnexC(58),
reserved16(59), reserved16(59),
reserved17(60), reserved17(60),
reserved18(61), reserved18(61),
reserved19(62), reserved19(62),
reserved20(63) reserved20(63)
RFC 5650 VDSL2-LINE MIB September 2009
} }
Xdsl2RaMode ::= TEXTUAL-CONVENTION Xdsl2RaMode ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the rate adaptation behavior for the line. "Specifies the rate adaptation behavior for the line.
The three possible behaviors are: The three possible behaviors are:
manual (1) - No Rate-Adaptation. The initialization manual (1) - No Rate-Adaptation. The initialization
process attempts to synchronize to a process attempts to synchronize to a
specified rate. 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."
SYNTAX INTEGER { SYNTAX INTEGER {
manual(1), manual(1),
raInit(2), raInit(2),
dynamicRa(3) dynamicRa(3)
} }
Xdsl2InitResult ::= TEXTUAL-CONVENTION Xdsl2InitResult ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the result of full initialization attempt; the "Specifies the result of full initialization attempt; the
six possible result values are: six possible result values are:
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 otherCause (5) - Other initialization failure reason"
reason"
SYNTAX INTEGER { SYNTAX INTEGER {
noFail(0), noFail(0),
configError(1), configError(1),
configNotFeasible(2), configNotFeasible(2),
commFail(3), commFail(3),
noPeerAtu(4), noPeerAtu(4),
otherCause(5) otherCause(5)
} }
Xdsl2OperationModes ::= TEXTUAL-CONVENTION Xdsl2OperationModes ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The VDSL2 management model specified includes an xDSL Mode "The VDSL2 management model specified includes an xDSL Mode
object which identifies an instance of xDSL Mode-Specific object that 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
RFC 5650 VDSL2-LINE MIB September 2009
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)
skipping to change at page 31, line 31 skipping to change at page 33, line 4
wide U/S (F) wide U/S (F)
37 - G.992.3 Annex L POTS non-overlapped, mode 2, 37 - G.992.3 Annex L POTS non-overlapped, mode 2,
narrow U/S(F) narrow U/S(F)
38 - G.992.3 Annex L POTS overlapped, mode 3, 38 - G.992.3 Annex L POTS overlapped, mode 3,
wide U/S (F) wide U/S (F)
39 - G.992.3 Annex L POTS overlapped, mode 4, 39 - G.992.3 Annex L POTS overlapped, mode 4,
narrow U/S (F) narrow U/S (F)
40 - G.992.3 Annex M POTS non-overlapped (F) 40 - G.992.3 Annex M POTS non-overlapped (F)
41 - G.992.3 Annex M POTS overlapped (F) 41 - G.992.3 Annex M POTS overlapped (F)
42 - G.992.5 POTS non-overlapped (F) 42 - G.992.5 POTS non-overlapped (F)
RFC 5650 VDSL2-LINE MIB September 2009
43 - G.992.5 POTS overlapped (F) 43 - G.992.5 POTS overlapped (F)
44 - G.992.5 ISDN non-overlapped (F) 44 - G.992.5 ISDN non-overlapped (F)
45 - G.992.5 ISDN overlapped (F) 45 - G.992.5 ISDN overlapped (F)
46-47 - Unused. Reserved for future ITU-T specification. 46-47 - Unused. Reserved for future ITU-T specification.
48 - G.992.5 Annex I All-Digital non-overlapped (F) 48 - G.992.5 Annex I All-Digital non-overlapped (F)
49 - G.992.5 Annex I All-Digital overlapped (F) 49 - G.992.5 Annex I All-Digital overlapped (F)
50 - G.992.5 Annex J All-Digital non-overlapped (F) 50 - G.992.5 Annex J All-Digital non-overlapped (F)
51 - G.992.5 Annex J All-Digital overlapped (F) 51 - G.992.5 Annex J All-Digital overlapped (F)
52 - G.992.5 Annex M POTS non-overlapped (F) 52 - G.992.5 Annex M POTS non-overlapped (F)
53 - G.992.5 Annex M POTS overlapped (F) 53 - G.992.5 Annex M POTS overlapped (F)
skipping to change at page 32, line 31 skipping to change at page 34, line 4
g9923AnnexJAllDigNonOverlapped(32), g9923AnnexJAllDigNonOverlapped(32),
g9923AnnexJAllDigOverlapped(33), g9923AnnexJAllDigOverlapped(33),
g9924AnnexIAllDigNonOverlapped(34), g9924AnnexIAllDigNonOverlapped(34),
g9924AnnexIAllDigOverlapped(35), g9924AnnexIAllDigOverlapped(35),
g9923AnnexLMode1NonOverlapped(36), g9923AnnexLMode1NonOverlapped(36),
g9923AnnexLMode2NonOverlapped(37), g9923AnnexLMode2NonOverlapped(37),
g9923AnnexLMode3Overlapped(38), g9923AnnexLMode3Overlapped(38),
g9923AnnexLMode4Overlapped(39), g9923AnnexLMode4Overlapped(39),
g9923AnnexMPotsNonOverlapped(40), g9923AnnexMPotsNonOverlapped(40),
g9923AnnexMPotsOverlapped(41), g9923AnnexMPotsOverlapped(41),
RFC 5650 VDSL2-LINE MIB September 2009
g9925PotsNonOverlapped(42), g9925PotsNonOverlapped(42),
g9925PotsOverlapped(43), g9925PotsOverlapped(43),
g9925IsdnNonOverlapped(44), g9925IsdnNonOverlapped(44),
g9925isdnOverlapped(45), g9925isdnOverlapped(45),
g9925AnnexIAllDigNonOverlapped(48), g9925AnnexIAllDigNonOverlapped(48),
g9925AnnexIAllDigOverlapped(49), g9925AnnexIAllDigOverlapped(49),
g9925AnnexJAllDigNonOverlapped(50), g9925AnnexJAllDigNonOverlapped(50),
g9925AnnexJAllDigOverlapped(51), g9925AnnexJAllDigOverlapped(51),
g9925AnnexMPotsNonOverlapped(52), g9925AnnexMPotsNonOverlapped(52),
g9925AnnexMPotsOverlapped(53), g9925AnnexMPotsOverlapped(53),
skipping to change at page 33, line 4 skipping to change at page 34, line 28
g9932AnnexB(59), g9932AnnexB(59),
g9932AnnexC(60) g9932AnnexC(60)
} }
Xdsl2PowerMngState ::= TEXTUAL-CONVENTION Xdsl2PowerMngState ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects with this syntax uniquely identify each power "Objects 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. Synchronized and l0(1) - L0: Full power. Synchronized and
full transmission (i.e., Showtime). full transmission (i.e., Showtime).
l1(2) - L1: Low power with reduced net data rate l1(2) - L1: Low power with reduced net data rate
(for G.992.2 only). (for G.992.2 only).
l2(3) - L2: Low power with reduced net data rate l2(3) - L2: Low power with reduced net data rate
(for G.992.3, G.992.4 and G.992.5). (for G.992.3, G.992.4 and G.992.5).
l3(4) - L3: Idle power management state / No l3(4) - L3: Idle power management state / No
power." power."
SYNTAX INTEGER { SYNTAX INTEGER {
l0(1), l0(1),
skipping to change at page 33, line 31 skipping to change at page 34, line 54
} }
Xdsl2ConfPmsForce ::= TEXTUAL-CONVENTION Xdsl2ConfPmsForce ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects with this syntax are configuration parameters "Objects with this syntax are configuration parameters
that specify the desired power management state transition that specify the desired power management state transition
for the VDSL2/ADSL/ADSL2 or ADSL2+ link. for the 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).
RFC 5650 VDSL2-LINE MIB September 2009
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),
l0orL2toL3 (3) l0orL2toL3 (3)
} }
Xdsl2LinePmMode ::= TEXTUAL-CONVENTION Xdsl2LinePmMode ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 34, line 31 skipping to change at page 36, line 4
force (1) - Force/Initiate Loop Diagnostic mode" force (1) - Force/Initiate Loop Diagnostic mode"
SYNTAX INTEGER { SYNTAX INTEGER {
inhibit(0), inhibit(0),
force(1) force(1)
} }
Xdsl2LdsfResult ::= TEXTUAL-CONVENTION Xdsl2LdsfResult ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
RFC 5650 VDSL2-LINE MIB September 2009
"Possible failure reasons associated with performing "Possible failure reasons associated with performing
Dual Ended Loop Test (DELT) on a DSL line. Dual Ended Loop Test (DELT) on a DSL line.
Possible values are: 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
skipping to change at page 35, line 29 skipping to change at page 36, line 52
adminUp (9), adminUp (9),
tableFull (10), tableFull (10),
noResources (11) noResources (11)
} }
Xdsl2LineBpsc ::= TEXTUAL-CONVENTION Xdsl2LineBpsc ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects with this syntax are configuration parameters "Objects with this syntax are configuration parameters
that control the bits per subcarrier 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 subcarrier" measure (2) - Measure the bits per subcarrier"
RFC 5650 VDSL2-LINE MIB September 2009
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 subcarrier measurement on a DSL line. a bits per subcarrier measurement on a DSL line.
skipping to change at page 36, line 32 skipping to change at page 38, line 4
idle (1) - This state indicates that there is idle (1) - This state indicates that there is
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."
SYNTAX INTEGER { SYNTAX INTEGER {
idle(1), idle(1),
reset(2) reset(2)
} }
Xdsl2LineProfiles ::= TEXTUAL-CONVENTION Xdsl2LineProfiles ::= TEXTUAL-CONVENTION
RFC 5650 VDSL2-LINE MIB September 2009
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects with this syntax reference the list of "Objects with this syntax reference the list of
ITU-T G.993.2 implementation profiles supported by an ITU-T G.993.2 implementation profiles supported by an
xTU, enabled on the VDSL2 line or active on that line." xTU, enabled on the VDSL2 line or active on that line."
SYNTAX BITS { SYNTAX BITS {
profile8a(0), profile8a(0),
profile8b(1), profile8b(1),
profile8c(2), profile8c(2),
skipping to change at page 37, line 32 skipping to change at page 39, line 4
998ADE30-M2x-NUS0-A, 998ADE30-M2x-NUS0-A,
998ADE30-M2x-NUS0-M. 998ADE30-M2x-NUS0-M.
Class 998-B Annex C: POTS-138b, POTS-276b per C.2.1.1 Class 998-B Annex C: POTS-138b, POTS-276b per C.2.1.1
in G.993.2, TCM-ISDN per C.2.1.2 in G.993.2, TCM-ISDN per C.2.1.2
in G.993.2. in G.993.2.
Class 998-CO Annex C: POTS-138co, POTS-276co per C.2.1.1 Class 998-CO Annex C: POTS-138co, POTS-276co per C.2.1.1
in G.993.2. in G.993.2.
Class HPE-M1 Annex B: HPE17-M1-NUS0, HPE30-M1-NUS0." Class HPE-M1 Annex B: HPE17-M1-NUS0, HPE30-M1-NUS0."
SYNTAX INTEGER { SYNTAX INTEGER {
RFC 5650 VDSL2-LINE MIB September 2009
none(1), none(1),
a998ORb997M1cORc998B(2), a998ORb997M1cORc998B(2),
b997M1xOR998co(3), b997M1xOR998co(3),
b997M2x(4), b997M2x(4),
b998M1x(5), b998M1x(5),
b998M2x(6), b998M2x(6),
b998AdeM2x(7), b998AdeM2x(7),
bHpeM1(8) bHpeM1(8)
} }
Xdsl2LineLimitMask ::= TEXTUAL-CONVENTION Xdsl2LineLimitMask ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The G.993.2 limit PSD mask for each class of profile. "The G.993.2 limit PSD mask for each class of profile.
The profiles are grouped in following profile classes: The profiles are grouped in following profile classes:
- Class 8: Profiles 8a, 8b, 8c, 8d - Class 8: Profiles 8a, 8b, 8c, 8d.
- Class 12: Profiles 12a, 12b - Class 12: Profiles 12a, 12b.
- Class 17: Profile 17a - Class 17: Profile 17a.
- Class 30: Profile 30a." - Class 30: Profile 30a."
SYNTAX BITS { SYNTAX BITS {
profile8Limit1(0), profile8Limit1(0),
profile8Limit2(1), profile8Limit2(1),
profile8Limit3(2), profile8Limit3(2),
profile8Limit4(3), profile8Limit4(3),
profile8Limit5(4), profile8Limit5(4),
profile8Limit6(5), profile8Limit6(5),
profile8Limit7(6), profile8Limit7(6),
profile8Limit8(7), profile8Limit8(7),
profile8Limit9(8), profile8Limit9(8),
skipping to change at page 38, line 32 skipping to change at page 40, line 4
profile12Limit1(16), profile12Limit1(16),
profile12Limit2(17), profile12Limit2(17),
profile12Limit3(18), profile12Limit3(18),
profile12Limit4(19), profile12Limit4(19),
profile12Limit5(20), profile12Limit5(20),
profile12Limit6(21), profile12Limit6(21),
profile12Limit7(22), profile12Limit7(22),
profile12Limit8(23), profile12Limit8(23),
profile12Limit9(24), profile12Limit9(24),
profile12Limit10(25), profile12Limit10(25),
RFC 5650 VDSL2-LINE MIB September 2009
profile12Limit11(26), profile12Limit11(26),
profile12Limit12(27), profile12Limit12(27),
profile12Limit13(28), profile12Limit13(28),
profile12Limit14(29), profile12Limit14(29),
profile12Limit15(30), profile12Limit15(30),
profile12Limit16(31), profile12Limit16(31),
-- --
profile17Limit1(32), profile17Limit1(32),
profile17Limit2(33), profile17Limit2(33),
profile17Limit3(34), profile17Limit3(34),
skipping to change at page 39, line 31 skipping to change at page 40, line 54
profile30Limit14(61), profile30Limit14(61),
profile30Limit15(62), profile30Limit15(62),
profile30Limit16(63) profile30Limit16(63)
} }
Xdsl2LineUs0Disable ::= TEXTUAL-CONVENTION Xdsl2LineUs0Disable ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates if US0 is disabled for each limit PSD mask. "Indicates if US0 is disabled for each limit PSD mask.
The profiles are grouped in following profile classes: The profiles are grouped in following profile classes:
- Class 8: Profiles 8a, 8b, 8c, 8d - Class 8: Profiles 8a, 8b, 8c, 8d.
- Class 12: Profiles 12a, 12b
- Class 17: Profile 17a RFC 5650 VDSL2-LINE MIB September 2009
- Class 12: Profiles 12a, 12b.
- Class 17: Profile 17a.
- Class 30: Profile 30a." - Class 30: Profile 30a."
SYNTAX BITS { SYNTAX BITS {
profile8Us0Disable1(0), profile8Us0Disable1(0),
profile8Us0Disable2(1), profile8Us0Disable2(1),
profile8Us0Disable3(2), profile8Us0Disable3(2),
profile8Us0Disable4(3), profile8Us0Disable4(3),
profile8Us0Disable5(4), profile8Us0Disable5(4),
profile8Us0Disable6(5), profile8Us0Disable6(5),
profile8Us0Disable7(6), profile8Us0Disable7(6),
skipping to change at page 40, line 32 skipping to change at page 42, line 4
-- --
profile17Us0Disable1(32), profile17Us0Disable1(32),
profile17Us0Disable2(33), profile17Us0Disable2(33),
profile17Us0Disable3(34), profile17Us0Disable3(34),
profile17Us0Disable4(35), profile17Us0Disable4(35),
profile17Us0Disable5(36), profile17Us0Disable5(36),
profile17Us0Disable6(37), profile17Us0Disable6(37),
profile17Us0Disable7(38), profile17Us0Disable7(38),
profile17Us0Disable8(39), profile17Us0Disable8(39),
profile17Us0Disable9(40), profile17Us0Disable9(40),
RFC 5650 VDSL2-LINE MIB September 2009
profile17Us0Disable10(41), profile17Us0Disable10(41),
profile17Us0Disable11(42), profile17Us0Disable11(42),
profile17Us0Disable12(43), profile17Us0Disable12(43),
profile17Us0Disable13(44), profile17Us0Disable13(44),
profile17Us0Disable14(45), profile17Us0Disable14(45),
profile17Us0Disable15(46), profile17Us0Disable15(46),
profile17Us0Disable16(47), profile17Us0Disable16(47),
-- --
profile30Us0Disable1(48), profile30Us0Disable1(48),
profile30Us0Disable2(49), profile30Us0Disable2(49),
skipping to change at page 41, line 14 skipping to change at page 42, line 37
profile30Us0Disable13(60), profile30Us0Disable13(60),
profile30Us0Disable14(61), profile30Us0Disable14(61),
profile30Us0Disable15(62), profile30Us0Disable15(62),
profile30Us0Disable16(63) profile30Us0Disable16(63)
} }
Xdsl2LineUs0Mask ::= TEXTUAL-CONVENTION Xdsl2LineUs0Mask ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The US0 PSD masks to be allowed by the near-end xTU on "The US0 PSD masks to be allowed by the near-end xTU on
the line. This parameter is only defined for G.993.2 Annex A. the line. This parameter is only defined for G.993.2 Annex A.
It is represented as a bitmap (0 if not allowed and 1 if It is represented as a bitmap (0 if not allowed and 1 if
allowed) with the following definitions." allowed) with the following definitions."
SYNTAX BITS { SYNTAX BITS {
eu32(0), eu32(0),
eu36(1), eu36(1),
eu40(2), eu40(2),
eu44(3), eu44(3),
eu48(4), eu48(4),
eu52(5), eu52(5),
eu56(6), eu56(6),
eu60(7), eu60(7),
-- --
eu64(8), eu64(8),
eu128(9), eu128(9),
reserved1(10), reserved1(10),
reserved2(11), reserved2(11),
RFC 5650 VDSL2-LINE MIB September 2009
reserved3(12), reserved3(12),
reserved4(13), reserved4(13),
reserved5(14), reserved5(14),
reserved6(15), reserved6(15),
-- --
adlu32(16), adlu32(16),
adlu36(17), adlu36(17),
adlu40(18), adlu40(18),
adlu44(19), adlu44(19),
adlu48(20), adlu48(20),
skipping to change at page 42, line 32 skipping to change at page 44, line 4
singleSymbol (3), singleSymbol (3),
twoSymbols (4), twoSymbols (4),
threeSymbols (5), threeSymbols (5),
fourSymbols (6), fourSymbols (6),
fiveSymbols (7), fiveSymbols (7),
sixSymbols (8), sixSymbols (8),
sevenSymbols (9), sevenSymbols (9),
eightSymbols (10), eightSymbols (10),
nineSymbols (11), nineSymbols (11),
tenSymbols (12), tenSymbols (12),
RFC 5650 VDSL2-LINE MIB September 2009
elevenSymbols (13), elevenSymbols (13),
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
skipping to change at page 43, line 28 skipping to change at page 44, line 51
fifteenSymbols (16), fifteenSymbols (16),
sixteenSymbols (17) sixteenSymbols (17)
} }
Xdsl2MaxBer ::= TEXTUAL-CONVENTION Xdsl2MaxBer ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects with this syntax are configuration parameters "Objects with this syntax are configuration parameters
that reference the maximum Bit Error Rate (BER). that reference the maximum Bit Error Rate (BER).
The possible values are: The possible values are:
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"
SYNTAX INTEGER { SYNTAX INTEGER {
RFC 5650 VDSL2-LINE MIB September 2009
eminus3(1), eminus3(1),
eminus5(2), eminus5(2),
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 policy1 (2) - Policy 1 according to the applicable
standard" 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 STRING array "Each one of the 4096 bits in this OCTET STRING array
represents the corresponding subcarrier in the downstream represents the corresponding subcarrier in the downstream
direction. direction.
A bit value of one indicates that a subcarrier is masked." A bit value of one indicates that a subcarrier is masked."
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 STRING array "Each one of the 4096 bits in this OCTET STRING array
represents the corresponding subcarrier in the upstream direction. represents the corresponding subcarrier in the upstream
A bit value of one indicates that a subcarrier is masked." direction. A bit value of one indicates that a subcarrier
is masked."
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. Each band is "This type defines an array of bands. Each band is
represented by 4 octets and there is a maximum of 32 bands represented by 4 octets and there is a maximum of 32 bands
allowed. allowed.
Each band consists of a 16 bit start subcarrier index followed by Each band consists of a 16-bit start subcarrier index followed by
a 16 bit stop subcarrier index. a 16-bit stop subcarrier index.
Subcarrier index is an unsigned number in the range 0 to The subcarrier index is an unsigned number in the range 0 to
NSC-1." NSC-1."
SYNTAX OCTET STRING (SIZE(0..128)) SYNTAX OCTET STRING (SIZE(0..128))
RFC 5650 VDSL2-LINE MIB September 2009
Xdsl2RfiBands ::= TEXTUAL-CONVENTION Xdsl2RfiBands ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This type defines a subset of downstream PSD mask "This type defines a subset of downstream PSD mask
breakpoints used to notch radio frequency interference (RFI) breakpoints used to notch radio frequency interference (RFI)
bands. bands.
Each RFI band is represented by 4 octets: 16 bit start subcarrier Each RFI band is represented by 4 octets: a 16-bit start
index followed by a 16 bit stop subcarrier index. subcarrier 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.
Subcarrier index is an unsigned number in the range 0 to The subcarrier index is an unsigned number in the range 0 to
NSC-1." NSC-1."
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 32 PSD Mask "This is a structure that represents up to 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 subcarrier associated with the two octets hold the index of the subcarrier associated with the
breakpoint. The third octet holds the PSD reduction at the breakpoint. The third octet holds the PSD reduction at the
breakpoint from 0 (0dBm/Hz) to 255 (-127.5 dBm/Hz) using units of breakpoint from 0 (0 dBm/Hz) to 255 (-127.5 dBm/Hz) using units
0.5dBm/Hz. of 0.5 dBm/Hz.
Subcarrier index is an unsigned number in the range 0 to The subcarrier index is an unsigned number in the range 0 to
NSCds-1." NSCds-1."
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 16 PSD Mask "This is a structure that represents up to 16 PSD mask
breakpoints. breakpoints.
Each breakpoint occupies 3 octets: The first two octets hold the Each breakpoint occupies 3 octets: The first two octets hold the
index of the subcarrier associated with the breakpoint. The index of the subcarrier associated with the breakpoint. The
third octet holds the PSD reduction at the breakpoint from 0 third octet holds the PSD reduction at the breakpoint from 0
(0dBm/Hz) to 255 (-127.5 dBm/Hz) using units of (0 dBm/Hz) to 255 (-127.5 dBm/Hz) using units of
0.5dBm/Hz. 0.5 dBm/Hz.
Subcarrier index is an unsigned number in the range 0 to The subcarrier index is an unsigned number in the range 0 to
NSCus-1." NSCus-1."
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 32 transmit "This is a structure that represents up to 32 transmit
spectrum shaping (TSSi) breakpoints. spectrum shaping (TSSi) breakpoints.
Each breakpoint is a pair of values occupying 3 octets with the Each breakpoint is a pair of values occupying 3 octets with the
RFC 5650 VDSL2-LINE MIB September 2009
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.
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 is -0.5 dB). The special value 127 indicates that the subcarrier is
not transmitted. not transmitted.
Subcarrier index is an unsigned number in the range 0 to The subcarrier index is an unsigned number in the range 0 to
NSC-1." NSC-1."
SYNTAX OCTET STRING (SIZE(0..96)) SYNTAX OCTET STRING (SIZE(0..96))
Xdsl2LastTransmittedState ::= TEXTUAL-CONVENTION Xdsl2LastTransmittedState ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This parameter represents the last successful transmitted "This parameter represents the last successful transmitted
initialization state in the last full initialization performed initialization state in the last full initialization performed
on the line. States are per the specific xDSL technology and on the line. States are per the specific xDSL technology and
are are numbered 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 -- -- 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),
skipping to change at page 46, line 34 skipping to change at page 48, line 4
atucReverb3(17), atucReverb3(17),
atucTref2(18), atucTref2(18),
atucReverb4(19), atucReverb4(19),
atucSegue1(20), atucSegue1(20),
atucMsg1(21), atucMsg1(21),
atucReverb5(22), atucReverb5(22),
atucSegue2(23), atucSegue2(23),
atucMedley(24), atucMedley(24),
atucExchmarker(25), atucExchmarker(25),
atucMsg2(26), atucMsg2(26),
RFC 5650 VDSL2-LINE MIB September 2009
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 -- -- ADSL family ATU-R side --
aturG9941(100), aturG9941(100),
aturQuiet1(101), aturQuiet1(101),
aturComb1(102), aturComb1(102),
skipping to change at page 47, line 33 skipping to change at page 49, line 4
aturShowtime(131), aturShowtime(131),
-- VDSL2 VTU-C side -- -- VDSL2 VTU-C side --
vtucG9941(200), vtucG9941(200),
vtucQuiet1(201), vtucQuiet1(201),
vtucChDiscov1(202), vtucChDiscov1(202),
vtucSynchro1(203), vtucSynchro1(203),
vtucPilot1(204), vtucPilot1(204),
vtucQuiet2(205), vtucQuiet2(205),
vtucPeriodic1(206), vtucPeriodic1(206),
vtucSynchro2(207), vtucSynchro2(207),
RFC 5650 VDSL2-LINE MIB September 2009
vtucChDiscov2(208), vtucChDiscov2(208),
vtucSynchro3(209), vtucSynchro3(209),
vtucTraining1(210), vtucTraining1(210),
vtucSynchro4(211), vtucSynchro4(211),
vtucPilot2(212), vtucPilot2(212),
vtucTeq(213), vtucTeq(213),
vtucEct(214), vtucEct(214),
vtucPilot3(215), vtucPilot3(215),
vtucPeriodic2(216), vtucPeriodic2(216),
vtucTraining2(217), vtucTraining2(217),
skipping to change at page 48, line 27 skipping to change at page 49, line 49
vturSynchro5(317), vturSynchro5(317),
vturMedley(318), vturMedley(318),
vturSynchro6(319), vturSynchro6(319),
vturShowtime(320) vturShowtime(320)
} }
Xdsl2LineStatus ::= TEXTUAL-CONVENTION Xdsl2LineStatus ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects with this syntax are status parameters "Objects with this syntax are status parameters
that reflect the failure status for a given end point of a that reflect the failure status for a given endpoint 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
RFC 5650 VDSL2-LINE MIB September 2009
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 compute the "This type is used to indicate the method used to compute the
ACTINP. If set to 'inpComputedUsingFormula', the ACTINP is Actual Impulse Noise Protection (ACTINP). If set to
computed according to the INP_no_erasure formula (9.6/G.993.2). 'inpComputedUsingFormula', the ACTINP is computed
according to the INP_no_erasure formula (9.6/G.993.2).
If set to 'inpEstimatedByXtur', the ACTINP is the value If set to 'inpEstimatedByXtur', the ACTINP is 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
"Objects with this syntax are status parameters that "Objects with this syntax are status parameters that
reflect the failure status for Transmission Convergence (TC) reflect the failure status for the 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. exists.
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
RFC 5650 VDSL2-LINE MIB September 2009
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
"Objects with this syntax are status parameters that "Objects with this syntax are status parameters that
reflect the failure status for a given PTM interface (packet reflect the failure status for a given PTM interface (packet
data path over a VDSL2/ADSL/ADSL2 or ADSL2+ link). data path over a 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 noDefect (0) - This bit position positively
reports that no defect or failure exist. reports that no defect or failure exists.
outOfSync (1) - Out of synchronization." outOfSync (1) - Out of synchronization."
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 VDSL Transceiver Unit (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)
} }
Xdsl2BandUs ::= TEXTUAL-CONVENTION Xdsl2BandUs ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each value identifies a specific band in the upstream "Each value identifies a specific band in the upstream
transmission direction (Excluding US0 band.).
The possible values which identify a band are as follows: RFC 5650 VDSL2-LINE MIB September 2009
transmission direction (excluding the US0 band.).
The possible values that identify a band are as follows:
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)."
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 mask is "This type is used to define which upstream PSD mask is
enabled. This type is used only for Annexes J and M of ITU-T Recs enabled. This type is used only for Annexes J and M of ITU-T
G.992.3 and G.992.5. Recommendations 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-64" 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)
} }
Xdsl2LineCeFlag ::= TEXTUAL-CONVENTION Xdsl2LineCeFlag ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This type is used to enable the use of the optional "This type is used to enable the use of the optional
cyclic extension values. If the bit is set to 1, the optional cyclic extension values. If the bit is set to '1', the optional
cyclic extension values may be used. Otherwise, the cyclic cyclic extension values may be used. Otherwise, the cyclic
extension shall be forced to the mandatory length (5N/32). extension shall be forced to the mandatory length (5N/32).
enableCyclicExtension (0) - Enable use of optional RFC 5650 VDSL2-LINE MIB September 2009
Cyclic Extension values."
enableCyclicExtension (0) - Enable use of optional
Cyclic Extension values."
SYNTAX BITS { SYNTAX BITS {
enableCyclicExtension(0) enableCyclicExtension(0)
} }
Xdsl2LineSnrMode ::= TEXTUAL-CONVENTION Xdsl2LineSnrMode ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This type is used to enable the transmitter referred "This type is used to enable the transmitter-referred
virtual noise. The value of 1, indicates that virtual virtual noise. The value of 1, indicates that virtual
noise is disabled. The value of 2, indicates that virtual noise is disabled. The value of 2, indicates that virtual
noise is enabled. noise is enabled.
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 32 PSD Mask "This is a structure that represents up to 32 PSD mask
breakpoints. breakpoints.
Each breakpoint occupies 3 octets: The first two octets hold the Each breakpoint occupies 3 octets: The first two octets hold the
index of the subcarrier associated with the breakpoint. The index of the subcarrier associated with the breakpoint. The
third octet holds the PSD reduction at the breakpoint from 0 third octet 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 0.5 dBm/Hz.
A special value of 255 indicates a noise level of 0 W/Hz. A special value of 255 indicates a noise level of 0 W/Hz.
Subcarrier index is an unsigned number in the range 0 to The subcarrier index is an unsigned number in the range 0 to
NSCds-1." NSCds-1."
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 16 PSD Mask "This is a structure that represents up to 16 PSD mask
breakpoints. breakpoints.
Each breakpoint occupies 3 octets: The first two octets hold the Each breakpoint occupies 3 octets: The first two octets hold the
index of the subcarrier associated with the breakpoint. The index of the subcarrier associated with the breakpoint. The
third octet holds the PSD reduction at the breakpoint from 0 third octet 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 0.5 dBm/Hz.
A special value of 255 indicates a noise level of 0 W/Hz. A special value of 255 indicates a noise level of 0 W/Hz.
Subcarrier index is an unsigned number in the range 0 to The subcarrier index is an unsigned number in the range 0 to
NSCus-1." NSCus-1."
SYNTAX OCTET STRING (SIZE(0..48)) SYNTAX OCTET STRING (SIZE(0..48))
RFC 5650 VDSL2-LINE MIB September 2009
Xdsl2BitsAlloc ::= TEXTUAL-CONVENTION Xdsl2BitsAlloc ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This type specifies an array of nibbles, where each nibble "This type specifies an array of nibbles, where each nibble
indicates the bits allocation for a subcarrier. indicates the bits allocation for a subcarrier.
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
"Objects with this syntax are MEDLEY Reference PSD status "Objects with this syntax are MEDLEY Reference PSD status
parameters in the downstream direction. This is expressed as parameters in the downstream direction. This is expressed as
the set of the set of
breakpoints exchanged at initialization. breakpoints exchanged at initialization.
The OCTET STRING contains up to 48 pairs of values in the The OCTET STRING contains up to 48 pairs of values in the
following structure: following structure:
Octets 0-1 -- Index of 1st subcarrier used in the Octets 0-1 -- Index of the first subcarrier used in the
context of a first breakpoint. context of a first breakpoint.
Octets 2-3 -- The PSD level for the subcarrier indicated Octets 2-3 -- The PSD level for the subcarrier indicated
in octets 0-1. in octets 0-1.
Octets 4-7 -- Same, for a 2nd breakpoint Octets 4-7 -- Same, for a second breakpoint
Octets 8-11 -- Same, for a 3rd breakpoint Octets 8-11 -- Same, for a third 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.
Subcarrier index is an unsigned number in the range 0 to NSCds-1. The subcarrier index is an unsigned number in the range 0
The PSD level is an integer value in the 0 to 4095 range. It is to NSCds-1.
represented in units of 0.1 dB offset from -140dBm/Hz." The PSD level is an integer value in the 0 to 4095 range. It is
represented in units of 0.1 dB offset from -140 dBm/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
"Objects with this syntax are MEDLEY Reference PSD status "Objects with this syntax are MEDLEY Reference PSD status
parameters in the upstream direction. This is expressed parameters in the upstream direction. This is expressed
as the set of as the set of
breakpoints exchanged at initialization. breakpoints exchanged at initialization.
The OCTET STRING contains up to 32 pairs of values in the The OCTET STRING contains up to 32 pairs of values in the
following structure: following structure:
Octets 0-1 -- Index of 1st subcarrier used in the Octets 0-1 -- Index of the first subcarrier used in the
context of a first breakpoint. context of a first breakpoint.
Octets 2-3 -- The PSD level for the subcarrier indicated Octets 2-3 -- The PSD level for the subcarrier indicated
in octets 0-1. in octets 0-1.
Octets 4-7 -- Same, for a 2nd breakpoint Octets 4-7 -- Same, for a second breakpoint
Octets 8-11 -- Same, for a 3rd breakpoint Octets 8-11 -- Same, for a third breakpoint
And so on until And so on until
RFC 5650 VDSL2-LINE MIB September 2009
Octets 124-127 -- Same, for a 32nd breakpoint. Octets 124-127 -- Same, for a 32nd breakpoint.
Subcarrier index is an unsigned number in the range 0 to NSCus-1. The subcarrier index is an unsigned number in the range 0
The PSD level is an integer value in the 0 to 4095 range. It is to NSCus-1.
represented in units of 0.1 dB offset from -140dBm/Hz." The PSD level is an integer value in the 0 to 4095 range. It is
represented in units of 0.1 dB offset from -140 dBm/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 54, line 32 skipping to change at page 56, line 4
Xdsl2TransmissionModeType, Xdsl2TransmissionModeType,
Xdsl2RaMode, Xdsl2RaMode,
Xdsl2InitResult, Xdsl2InitResult,
Xdsl2OperationModes, Xdsl2OperationModes,
Xdsl2PowerMngState, Xdsl2PowerMngState,
Xdsl2ConfPmsForce, Xdsl2ConfPmsForce,
Xdsl2LinePmMode, Xdsl2LinePmMode,
Xdsl2LineLdsf, Xdsl2LineLdsf,
Xdsl2LdsfResult, Xdsl2LdsfResult,
Xdsl2LineBpsc, Xdsl2LineBpsc,
RFC 5650 VDSL2-LINE MIB September 2009
Xdsl2BpscResult, Xdsl2BpscResult,
Xdsl2LineReset, Xdsl2LineReset,
Xdsl2SymbolProtection, Xdsl2SymbolProtection,
Xdsl2SymbolProtection8, Xdsl2SymbolProtection8,
Xdsl2MaxBer, Xdsl2MaxBer,
Xdsl2ChInitPolicy, Xdsl2ChInitPolicy,
Xdsl2ScMaskDs, Xdsl2ScMaskDs,
Xdsl2ScMaskUs, Xdsl2ScMaskUs,
Xdsl2CarMask, Xdsl2CarMask,
Xdsl2RfiBands, Xdsl2RfiBands,
skipping to change at page 55, line 25 skipping to change at page 56, line 49
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 "200905100000Z" -- May 10, 2009 LAST-UPDATED "200909300000Z" -- September 30, 2009
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
RFC 5650 VDSL2-LINE MIB September 2009
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
Co-Chair: Menachem Dodge Co-Chair: Menachem Dodge
ECI Telecom Ltd. ECI Telecom Ltd.
Postal: 30 Hasivim St. Postal: 30 Hasivim St.
skipping to change at page 56, line 31 skipping to change at page 58, line 4
" "
DESCRIPTION DESCRIPTION
" "
This document defines a Management Information Base (MIB) This document defines a Management Information Base (MIB)
module for use with network management protocols in the module for use with network management protocols in the
Internet community for the purpose of managing VDSL2, ADSL, Internet community for the purpose of managing VDSL2, ADSL,
ADSL2, and ADSL2+ lines. ADSL2, and ADSL2+ lines.
The MIB module described in RFC 2662 [RFC2662] defines The MIB module described in RFC 2662 [RFC2662] defines
objects used for managing Asymmetric Bit-Rate DSL (ADSL) objects used for managing Asymmetric Bit-Rate DSL (ADSL)
RFC 5650 VDSL2-LINE MIB September 2009
interfaces per [T1E1.413], [G.992.1], and [G.992.2]. interfaces per [T1E1.413], [G.992.1], and [G.992.2].
These object descriptions are based upon the specifications These object descriptions are based upon the specifications
for the ADSL Embedded Operations Channel (EOC) as defined for the ADSL Embedded Operations Channel (EOC) as defined
in American National Standards Institute (ANSI) T1E1.413 in American National Standards Institute (ANSI) T1E1.413
[T1E1.413] and International Telecommunication Union (ITU-T) [T1E1.413] and International Telecommunication Union (ITU-T)
G.992.1 [G.992.1] and G.992.2 [G.992.2]. G.992.1 [G.992.1] and G.992.2 [G.992.2].
The MIB module described in RFC 4706 [RFC4706] defines The MIB module described in RFC 4706 [RFC4706] defines
objects used for managing ADSL2 interfaces per [G.992.3] objects used for managing ADSL2 interfaces per [G.992.3]
and [G.992.4], and ADSL2+ interfaces per [G.992.5]. That MIB and [G.992.4], and ADSL2+ interfaces per [G.992.5]. That MIB
is also capable of managing ADSL interfaces per [T1E1.413], is also capable of managing ADSL interfaces per [T1E1.413],
[G.992.1], and [G.992.2]. [G.992.1], and [G.992.2].
This document does not obsolete RFC 2662 [RFC2662] and This document does not obsolete RFC 2662 [RFC2662] or
RFC 4706 [RFC4706], but rather provides a more comprehensive RFC 4706 [RFC4706], but rather provides a more comprehensive
management model that manages VDSL2 interfaces per G.993.2 management model that manages VDSL2 interfaces per G.993.2
[G.993.2] as well as ADSL, ADSL2 and ADSL2+ technologies [G.993.2] as well as ADSL, ADSL2, and ADSL2+ technologies
per T1E1.413, G.992.1, G.992.2, G.992.3, G.992.4, and per T1E1.413, G.992.1, G.992.2, G.992.3, G.992.4, and
G.992.5 G.992.5
([T1E1.413], [G.992.1], [G.992.2], [G.992.3], [G.992.4], and ([T1E1.413], [G.992.1], [G.992.2], [G.992.3], [G.992.4], and
[G.992.5] respectively). [G.992.5], respectively).
Additionally, the management framework for VDSL2 lines Additionally, the management framework for VDSL2 lines
specified by the Digital Subscriber Line Forum specified by the Digital Subscriber Line Forum
(DSLF) has been taken into consideration [TR-129]. That (DSLF) has been taken into consideration [TR-129]. That
framework is based on ITU-T G.997.1 standard [G.997.1] and framework is based on the ITU-T G.997.1 standard [G.997.1] and
its amendment 1 [G.997.1-Am1]. its amendment 1 [G.997.1-Am1].
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) 2009 IETF Trust and the persons identified
this MIB module is part of RFC XXXX: see the RFC itself for as authors of the code. All rights reserved.
full legal notices."
REVISION "200905100000Z" -- May 10, 2009 Redistribution and use in source and binary forms, with
DESCRIPTION "Initial version, published as RFC XXXX." or without modification, are permitted provided that the
::= { transmission yyy } following conditions are met:
- Redistributions of source code must retain the above
copyright notice, this list of conditions and the
following disclaimer.
- Redistributions in binary form must reproduce the above
copyright notice, this list of conditions and the
following disclaimer in the documentation and/or other
materials provided with the distribution.
RFC 5650 VDSL2-LINE MIB September 2009
- Neither the name of Internet Society, IETF or IETF Trust,
nor the names of specific contributors, may be used to
endorse or promote products derived from this software
without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
CONTRIBUTORS 'AS IS' AND ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This version of this MIB module is part of RFC 5650;
see the RFC itself for full legal notices."
REVISION "200909300000Z" -- September 30, 2009
DESCRIPTION "Initial version, published as RFC 5650."
::= { transmission 251 }
xdsl2Notifications OBJECT IDENTIFIER ::= { vdsl2MIB 0 } xdsl2Notifications OBJECT IDENTIFIER ::= { vdsl2MIB 0 }
xdsl2Objects OBJECT IDENTIFIER ::= { vdsl2MIB 1 } xdsl2Objects OBJECT IDENTIFIER ::= { vdsl2MIB 1 }
xdsl2Conformance OBJECT IDENTIFIER ::= { vdsl2MIB 2 } xdsl2Conformance OBJECT IDENTIFIER ::= { vdsl2MIB 2 }
------------------------------------------------ ------------------------------------------------
xdsl2Line OBJECT IDENTIFIER ::= { xdsl2Objects 1 } xdsl2Line OBJECT IDENTIFIER ::= { xdsl2Objects 1 }
xdsl2Status OBJECT IDENTIFIER ::= { xdsl2Objects 2 } xdsl2Status OBJECT IDENTIFIER ::= { xdsl2Objects 2 }
xdsl2Inventory OBJECT IDENTIFIER ::= { xdsl2Objects 3 } xdsl2Inventory OBJECT IDENTIFIER ::= { xdsl2Objects 3 }
xdsl2PM OBJECT IDENTIFIER ::= { xdsl2Objects 4 } xdsl2PM OBJECT IDENTIFIER ::= { xdsl2Objects 4 }
xdsl2Profile OBJECT IDENTIFIER ::= { xdsl2Objects 5 } xdsl2Profile OBJECT IDENTIFIER ::= { xdsl2Objects 5 }
skipping to change at page 57, line 45 skipping to change at page 60, line 4
xdsl2PMChannel OBJECT IDENTIFIER ::= { xdsl2PM 2 } xdsl2PMChannel OBJECT IDENTIFIER ::= { xdsl2PM 2 }
------------------------------------------------ ------------------------------------------------
xdsl2ProfileLine OBJECT IDENTIFIER ::= { xdsl2Profile 1 } xdsl2ProfileLine OBJECT IDENTIFIER ::= { xdsl2Profile 1 }
xdsl2ProfileChannel OBJECT IDENTIFIER ::= { xdsl2Profile 2 } xdsl2ProfileChannel OBJECT IDENTIFIER ::= { xdsl2Profile 2 }
xdsl2ProfileAlarmConf OBJECT IDENTIFIER ::= { xdsl2Profile 3 } xdsl2ProfileAlarmConf OBJECT IDENTIFIER ::= { xdsl2Profile 3 }
------------------------------------------------ ------------------------------------------------
xdsl2ScalarSC OBJECT IDENTIFIER ::= { xdsl2Scalar 1 } xdsl2ScalarSC OBJECT IDENTIFIER ::= { xdsl2Scalar 1 }
------------------------------------------------ ------------------------------------------------
------------------------------------------------ ------------------------------------------------
RFC 5650 VDSL2-LINE MIB September 2009
-- 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, command and "The table xdsl2LineTable contains configuration, command and
status parameters of the VDSL2/ADSL/ADSL2 or ADSL2+ line. status parameters of the VDSL2/ADSL/ADSL2 or ADSL2+ line.
Several objects in this table MUST be maintained in a persistent Several objects in this table MUST be maintained in a persistent
manner." manner."
skipping to change at page 58, line 16 skipping to change at page 60, line 27
Several objects in this table MUST be maintained in a persistent Several objects in this table MUST be maintained in a 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 index of this table is an interface index where the "The index of this table is an interface index where the
interface has an ifType of vdsl2(xxx)." interface has an ifType of vdsl2(251)."
INDEX { ifIndex } INDEX { ifIndex }
::= { xdsl2LineTable 1 } ::= { xdsl2LineTable 1 }
Xdsl2LineEntry ::= Xdsl2LineEntry ::=
SEQUENCE { SEQUENCE {
xdsl2LineConfTemplate SnmpAdminString, xdsl2LineConfTemplate SnmpAdminString,
xdsl2LineConfFallbackTemplate SnmpAdminString, xdsl2LineConfFallbackTemplate SnmpAdminString,
xdsl2LineAlarmConfTemplate SnmpAdminString, xdsl2LineAlarmConfTemplate SnmpAdminString,
xdsl2LineCmndConfPmsf Xdsl2ConfPmsForce, xdsl2LineCmndConfPmsf Xdsl2ConfPmsForce,
xdsl2LineCmndConfLdsf Xdsl2LineLdsf, xdsl2LineCmndConfLdsf Xdsl2LineLdsf,
skipping to change at page 58, line 43 skipping to change at page 61, line 4
xdsl2LineStatusActTemplate SnmpAdminString, xdsl2LineStatusActTemplate SnmpAdminString,
xdsl2LineStatusXtuTransSys Xdsl2TransmissionModeType, xdsl2LineStatusXtuTransSys Xdsl2TransmissionModeType,
xdsl2LineStatusPwrMngState Xdsl2PowerMngState, xdsl2LineStatusPwrMngState Xdsl2PowerMngState,
xdsl2LineStatusInitResult Xdsl2InitResult, xdsl2LineStatusInitResult Xdsl2InitResult,
xdsl2LineStatusLastStateDs Xdsl2LastTransmittedState, xdsl2LineStatusLastStateDs Xdsl2LastTransmittedState,
xdsl2LineStatusLastStateUs Xdsl2LastTransmittedState, xdsl2LineStatusLastStateUs Xdsl2LastTransmittedState,
xdsl2LineStatusXtur Xdsl2LineStatus, xdsl2LineStatusXtur Xdsl2LineStatus,
xdsl2LineStatusXtuc Xdsl2LineStatus, xdsl2LineStatusXtuc Xdsl2LineStatus,
xdsl2LineStatusAttainableRateDs Unsigned32, xdsl2LineStatusAttainableRateDs Unsigned32,
xdsl2LineStatusAttainableRateUs Unsigned32, xdsl2LineStatusAttainableRateUs Unsigned32,
RFC 5650 VDSL2-LINE MIB September 2009
xdsl2LineStatusActPsdDs Integer32, xdsl2LineStatusActPsdDs Integer32,
xdsl2LineStatusActPsdUs Integer32, xdsl2LineStatusActPsdUs Integer32,
xdsl2LineStatusActAtpDs Integer32, xdsl2LineStatusActAtpDs Integer32,
xdsl2LineStatusActAtpUs Integer32, xdsl2LineStatusActAtpUs Integer32,
xdsl2LineStatusActProfile Xdsl2LineProfiles, xdsl2LineStatusActProfile Xdsl2LineProfiles,
xdsl2LineStatusActLimitMask Xdsl2LineLimitMask, xdsl2LineStatusActLimitMask Xdsl2LineLimitMask,
xdsl2LineStatusActUs0Mask Xdsl2LineUs0Mask, xdsl2LineStatusActUs0Mask Xdsl2LineUs0Mask,
xdsl2LineStatusActSnrModeDs Xdsl2LineSnrMode, xdsl2LineStatusActSnrModeDs Xdsl2LineSnrMode,
xdsl2LineStatusActSnrModeUs Xdsl2LineSnrMode, xdsl2LineStatusActSnrModeUs Xdsl2LineSnrMode,
xdsl2LineStatusElectricalLength Unsigned32, xdsl2LineStatusElectricalLength Unsigned32,
skipping to change at page 59, line 20 skipping to change at page 61, line 32
xdsl2LineStatusTrellisUs TruthValue, xdsl2LineStatusTrellisUs TruthValue,
xdsl2LineStatusActualCe Unsigned32 xdsl2LineStatusActualCe Unsigned32
} }
xdsl2LineConfTemplate OBJECT-TYPE xdsl2LineConfTemplate 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 Configuration Templates Table, xdsl2LineConfTemplateTable, Line Configuration Template Table, xdsl2LineConfTemplateTable,
that applies for this line. that 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 }
xdsl2LineConfFallbackTemplate OBJECT-TYPE xdsl2LineConfFallbackTemplate 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 will be "This object is used to identify the template that will be
used if the xDSL2 line fails to operate using the primary used if the xDSL2 line fails to operate using the primary
template. The primary template is identified using the template. The primary template is identified using the
xdsl2LineConfTemplate object. xdsl2LineConfTemplate object.
For example, a xDSL2 line may fallback to a template with a lower For example, a xDSL2 line may fall back to a template with a
rate if the rate specified in the primary template cannot be lower rate if the rate specified in the primary template
achieved. cannot be achieved.
The value of this object identifies a row in the xDSL2 Line The value of this object identifies a row in the xDSL2 Line
RFC 5650 VDSL2-LINE MIB September 2009
Configuration Template Table, xdsl2LineConfTemplateTable. Configuration Template Table, xdsl2LineConfTemplateTable.
Any row in the xdsl2LineConfTemplateTable table may be used as a Any row in the xdsl2LineConfTemplateTable table may be used as a
fallback template. fall-back template.
If the xDSL2 line fails to operate using the fallback template If the xDSL2 line fails to operate using the fall-back template,
then the primary template should be retried. then the primary template should be retried.
The xTU-C should continue to alternate between the primary and The xTU-C should continue to alternate between the primary and
fallback templates until one of them succeeds. fall-back templates until one of them succeeds.
If the value of this object is a zero-length string then no If the value of this object is a zero-length string, then no
fallback template is defined and only the primary template will fall-back template is defined and only the primary 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 }
xdsl2LineAlarmConfTemplate OBJECT-TYPE xdsl2LineAlarmConfTemplate OBJECT-TYPE
skipping to change at page 60, line 44 skipping to change at page 63, line 4
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.
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 (PMSF)" 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
RFC 5650 VDSL2-LINE MIB September 2009
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Loop diagnostics mode forced (LDSF). "Loop diagnostic state 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 any a loop diagnostic may be initiated by the far-end xTU at any
time. time.
Only when the xdsl2LineStatusPwrMngState object is in the Only when the xdsl2LineStatusPwrMngState object is in the
'l3' state and the xdsl2LineCmndConfPmsf object is in the 'l3' state and the xdsl2LineCmndConfPmsf object is in the
'l0orL2toL3' state, can the line be forced into loop diagnostic 'l0orL2toL3' state, can the line be forced into loop diagnostic
mode procedures. Upon successful completion of the loop mode procedures. Upon successful completion of the loop
diagnostic mode procedures, the Access Node shall set this diagnostic mode procedures, the Access Node shall set this
object to 'inhibit', and xdsl2LineStatusPwrMngState will object to 'inhibit', and xdsl2LineStatusPwrMngState will
remain in the 'l3' state. The loop diagnostic data shall be remain in the 'l3' state. The loop diagnostic data shall be
available at least until xdsl2LineCmndConfPmsf is set to the available at least until xdsl2LineCmndConfPmsf is set to the
'l3toL0' state. 'l3toL0' state.
The results of the loop diagnostic procedure are stored in the The results of the loop diagnostic procedure are stored in the
tables xdsl2SCStatusTable, xdsl2SCStatusBandTable and tables xdsl2SCStatusTable, xdsl2SCStatusBandTable, and
xdsl2SCStatusSegmentTable. The status of the loop diagnostic xdsl2SCStatusSegmentTable. The status of the loop diagnostic
procedue is indicated by xdsl2LineCmndConfLdsfFailReason. procedure is indicated by 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 (LDSF)" 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 most recent occasion when the Loop "The status of the most recent occasion when the loop
diagnostics mode forced (LDSF) command was issued for the diagnostics state forced (LDSF) command was issued for the
associated line." associated line."
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 subcarrier measurement to be made.
A request for a bits per subcarrier measurement is made by RFC 5650 VDSL2-LINE MIB September 2009
setting this object to the value of 'measure'. Upon
"Request a bits-per-subcarrier measurement to be made.
A request for a bits-per-subcarrier measurement is made by
setting this object to the value of 'measure'. Upon
completion of the measurement request, the Access Node shall set completion of the measurement request, the Access Node shall set
this object to 'idle'. this object to 'idle'.
The SNMP agent should allow initiating a bits per subcarrier The SNMP agent should allow initiating a bits-per-subcarrier
measurement process only if there is no other bits per subcarrier measurement process only if there is no other bits-per-subcarrier
measurement already running, and respond with an SNMP error measurement already running, and respond with an SNMP error
(e.g., wrongValue) otherwise. (e.g., wrongValue) otherwise.
Note that a bits per subcarrier measurement is also performed Note that a bits-per-subcarrier measurement is also performed
during a line diagnostic procedure. This object provides an during a line diagnostic procedure. This object provides an
additional mechanism to fetch the bits per subcarrier data. This additional mechanism to fetch the bits-per-subcarrier data. This
additional mechanism is provided so that bits per subcarrier additional mechanism is provided so that bits-per-subcarrier
data may be fetched without forcing the line into no power state. data may be fetched without forcing the line into no power state.
This is useful because the bits per subcarrier allocation may be This is useful because the bits-per-subcarrier allocation may be
adjusted at show time due to rate adaption and bit swapping. adjusted at show time due to rate adaption and bit swapping.
The implementation of this additional mechanism for measuring The implementation of this additional mechanism for measuring
bits per subcarrier is not mandatory. bits per subcarrier is not mandatory.
The results of the bits per subcarrier measurement are stored in The results of the bits-per-subcarrier measurement are stored in
xdsl2LineSegmentTable. The status of the bits per subcarrier xdsl2LineSegmentTable. The status of the bits-per-subcarrier
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 subcarrier "The status of the most recent bits-per-subcarrier
measurement request issued for the associated line." measurement request issued for the associated line."
DEFVAL { none } DEFVAL { none }
::= { xdsl2LineEntry 8 } ::= { xdsl2LineEntry 8 }
xdsl2LineCmndConfBpscRequests OBJECT-TYPE xdsl2LineCmndConfBpscRequests OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
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 for a This counter is incremented by one every time a request for a
bits per subcarrier measurement is made. A measurement request is bits-per-subcarrier measurement is made. A measurement request
made by modifying the xdsl2LineCmndConfBpsc object from idle(1)
to the RFC 5650 VDSL2-LINE MIB September 2009
value measure(2).
is made by modifying the xdsl2LineCmndConfBpsc object from
idle(1) to the value measure(2).
The measurement results may be very large and will not fit The measurement results may be very large and will not fit
into a single PDU hence multiple SNMP GET requests may be into a single PDU; hence, multiple SNMP GET requests may be
required to fetch the measurement results. required to fetch the measurement results.
Because the measurement results cannot be fetched atomically, Because the measurement results cannot be fetched atomically,
it is possible for a second manager to start a new measurement it is possible for a second manager to start a new measurement
before a first manager has fetched all of its results. before a first manager has fetched all of its results.
A SNMP manager can use this object to ensure that the An SNMP manager can use this object to ensure that the
measurement results retrieved using one or more GET requests measurement results retrieved using one or more GET requests
all belong to the measurement initiated by that manager. all belong to the measurement initiated by that manager.
The following steps are suggested in order for the SNMP The following steps are suggested in order for the SNMP
manager to initiate the bits per subcarrier measurement: manager to initiate the bits-per-subcarrier measurement:
1. Wait for xdsl2LineCmndConfBpsc value to be idle(1). 1. Wait for xdsl2LineCmndConfBpsc value to be idle(1).
2. Perform a SNMP GET for xdsl2LineCmndConfBpscRequests. 2. Perform an SNMP GET for xdsl2LineCmndConfBpscRequests.
3. Wait a short delay ( 4 -> 8 seconds ). 3. Wait a short delay (4 -> 8 seconds).
4. Perform a SNMP SET on xdsl2LineCmndConfBpsc with 4. Perform an SNMP SET on xdsl2LineCmndConfBpsc with
the value measure(2). the value measure(2).
5. If step 4 returns an error then goto step 1. 5. If step 4 returns an error, then go to step 1.
6. Wait for xdsl2LineCmndConfBpsc value to be idle(1). 6. Wait for xdsl2LineCmndConfBpsc value to be idle(1).
7. Fetch measurement results using one or more GET PDUs. 7. Fetch measurement results using one or more GET PDUs.
8. Perform a SNMP GET for xdsl2LineCmndConfBpscRequests. 8. Perform an SNMP GET for xdsl2LineCmndConfBpscRequests.
9. Compute the difference between the two values of 9. Compute the difference between the two values of
xdsl2LineCmndConfBpscRequests. If the value is one xdsl2LineCmndConfBpscRequests. If the value is one,
then the results are valid else goto step 1." then the results are valid, else go to step 1."
::= { 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 in "Automode cold start forced. This parameter is defined in
order to improve testing of the performance of xTUs supporting order to improve testing of the performance of xTUs 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 a change Change the value of this parameter to 'true' to indicate a change
in loop conditions applied to the devices under test. The xTUs in loop conditions applied to the devices under the test. The
shall reset any historical information used for automode and for xTUs shall reset any historical information used for automode
shortening G.994.1 handshake and initialization. and for shortening G.994.1 handshake and initialization.
Automode is the case where multiple operation-modes are enabled Automode is the case where multiple operation-modes are enabled
through the xdsl2LConfProfXtuTransSysEna object in the line through the xdsl2LConfProfXtuTransSysEna object in the line
configuration profile being used for the line, and where the configuration profile being used for the line, and where the
selection of the actual operation-mode depends not only on the selection of the actual operation-mode depends not only on the
common capabilities of both xTUs (as exchanged in G.994.1), but common capabilities of both xTUs (as exchanged in G.994.1), but
RFC 5650 VDSL2-LINE MIB September 2009
also on achievable data rates under given loop conditions." also on achievable data rates under given loop conditions."
REFERENCE "ITU-T G.997.1, paragraph #7.3.1.1.10 REFERENCE "ITU-T G.997.1, paragraph #7.3.1.1.10
(Automode Cold Start Forced)" (Automode Cold Start Forced)"
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 object is set to the value of 'reset', then force If this object is set to the value of 'reset', then 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 object to 'idle'. set the value of this object to 'idle'.
Note that the xdsl2LineCmndConfPmsf object will always take Note that the xdsl2LineCmndConfPmsf object will always take
precedence over this object. precedence over this object.
If the xdsl2LineCmndConfPmsf object is set to the value If the xdsl2LineCmndConfPmsf object is set to the value
'l0orL2toL3', then the line MUST NOT return to the showtime 'l0orL2toL3', then the line MUST NOT return to the Showtime
state due to a reset request action performed using this state due to a reset request action performed using this
object." object."
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 is "This object is used to identify the template that is
currently in use for this line. currently in use for this line.
This object is updated when a successfull line initialisation This object is updated when a successful line initialization
occurs. occurs.
This object indicates if the primary template This object indicates if the primary template
(xdsl2LineConfTemplate) is in use or the fallback template (xdsl2LineConfTemplate) is in use or the fall-back template
(xdsl2LineConfFallbackTemplate) is in use. (xdsl2LineConfFallbackTemplate) is in use.
If the line is not successfully initialised then the value of If the line is not successfully initialized, then the value of
this object will be a zero-length string." 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
RFC 5650 VDSL2-LINE MIB September 2009
It is coded in a bitmap 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 may be derived from the handshaking procedures defined parameter may be derived from the handshaking procedures defined
in Recommendation G.994.1. A set of xDSL line transmission in 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)" (xDSL transmission system)"
DEFVAL { {} } DEFVAL { {} }
::= { xdsl2LineEntry 13 } ::= { xdsl2LineEntry 13 }
xdsl2LineStatusPwrMngState OBJECT-TYPE xdsl2LineStatusPwrMngState OBJECT-TYPE
skipping to change at page 65, line 44 skipping to change at page 68, line 4
"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)" (Downstream last transmitted state)"
DEFVAL { atucG9941 } DEFVAL { atucG9941 }
::= { xdsl2LineEntry 16 } ::= { xdsl2LineEntry 16 }
xdsl2LineStatusLastStateUs OBJECT-TYPE xdsl2LineStatusLastStateUs OBJECT-TYPE
SYNTAX Xdsl2LastTransmittedState SYNTAX Xdsl2LastTransmittedState
RFC 5650 VDSL2-LINE MIB September 2009
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 on upstream direction in the last full initialization performed 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)" (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 the current state (existing failures) of the xTU-R.
This is a bit-map of possible conditions." This is a bitmap 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)" (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 the current state (existing failures) of the xTU-C.
This is a bit-map of possible conditions." This is a bitmap 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)" (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
"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 (ATTNDRds) REFERENCE "ITU-T G.997.1, paragraph #7.5.1.19 (ATTNDRds)"
"
DEFVAL { 0 } DEFVAL { 0 }
::= { xdsl2LineEntry 20 } ::= { xdsl2LineEntry 20 }
RFC 5650 VDSL2-LINE MIB September 2009
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
"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 (ATTNDRus) 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
"Actual Power Spectrum Density (PSD) Downstream. The average "Actual Power Spectral Density (PSD) Downstream. The average
downstream transmit PSD over the subcarriers used for downstream. downstream transmit PSD over the subcarriers used for downstream.
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 are
-90 to 0 dBm/Hz). -90 to 0 dBm/Hz).
A value of 0x7FFFFFFF (2147483647) indicates the measurement is A value of 0x7FFFFFFF (2147483647) indicates the measurement is
out of range to be represented." 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 (ACTPSDds)"
"
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
"Actual Power Spectrum Density (PSD) Upstream. The average "Actual Power Spectral Density (PSD) Upstream. The average
upstream transmit PSD over the subcarriers used for upstream. upstream transmit PSD over the subcarriers 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 are
-90 to 0 dBm/Hz). -90 to 0 dBm/Hz).
A value of 0x7FFFFFFF (2147483647) indicates the measurement is A value of 0x7FFFFFFF (2147483647) indicates the measurement is
out of range to be represented." 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 (ACTPSDus)"
"
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"
RFC 5650 VDSL2-LINE MIB September 2009
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Actual Aggregate Transmit Power Downstream. "Actual Aggregate Transmit Power Downstream.
The total amount of transmit power delivered by the xTU-C at The total amount of transmit power delivered by the xTU-C at
the U-C reference point, at the instant of measurement. It the U-C reference point, at the instant of measurement. It
ranges from -310 to 310 units of 0.1 dBm (Physical values are -31 ranges 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 is A value of 0x7FFFFFFF (2147483647) indicates the measurement is
out of range to be represented." out of range to be represented."
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.24 (ACTATPds) 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
"Actual Aggregate Transmit Power Upstream. "Actual Aggregate Transmit Power Upstream.
The total amount of transmit power delivered by the xTU-R at the The total amount of transmit power delivered by the xTU-R at the
U-R reference point, at the instant of measurement. It ranges U-R 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 is A value of 0x7FFFFFFF (2147483647) indicates the measurement is
out of range to be represented." out of range to be represented."
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.25 (ACTATPus) 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 Recommendation G.994.1."
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.2 (VDSL2 Profile) 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
RFC 5650 VDSL2-LINE MIB September 2009
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 This parameter indicates the limit PSD mask in use on 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)" (VDSL2 Limit PSD Mask and Band plan)"
skipping to change at page 69, line 27 skipping to change at page 71, line 30
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 line. This parameter indicates the US0 PSD mask 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 Recommendation 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)" (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
referred virtual noise is active on the line in the downstream virtual noise is active on the line in the downstream
direction. direction.
The configuration parameter xdsl2LConfProfSnrModeDs is used to The configuration parameter xdsl2LConfProfSnrModeDs 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 referred virtual
RFC 5650 VDSL2-LINE MIB September 2009
"This parameter indicates if the transmitter-referred virtual
noise is active on the line in the upstream direction. noise is active on the line in the upstream direction.
The configuration parameter xdsl2LConfProfSnrModeUs is used to The configuration parameter xdsl2LConfProfSnrModeUs is used to
configure referred virtual noise." 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
"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 the length that would have been sent from the VTU-O to VTU-R if 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 (UPBOKLE)" 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
skipping to change at page 71, line 6 skipping to change at page 73, line 4
DESCRIPTION DESCRIPTION
"The transmit spectrum shaping (TSSi) breakpoints expressed "The transmit spectrum shaping (TSSi) breakpoints expressed
as the set of breakpoints exchanged as the set of breakpoints exchanged
during G.994.1 (Upstream)." during G.994.1 (Upstream)."
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
RFC 5650 VDSL2-LINE MIB September 2009
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The MEDLEY Reference PSD status parameters "The MEDLEY Reference PSD status parameters
in the downstreasm in the downstream
direction expressed as the set of breakpoints exchanged at direction expressed as the set of breakpoints exchanged at
initialization." initialization."
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 (MREFPSDds)"
"
::= { 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 in the "The MEDLEY Reference PSD status parameters in the
upstreasm direction expressed as the set of breakpoints upstream direction expressed as the set of breakpoints
exchanged at initialization." exchanged at initialization."
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 (MREFPSDus)"
"
::= { 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 is in use in "This parameter reports whether trellis coding is in use in
the downstream direction." the downstream direction."
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.30 (TRELLISds) 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 is in use in "This parameter reports whether trellis coding is in use in
the upstream direction." the upstream direction."
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.31 (TRELLISus) 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
RFC 5650 VDSL2-LINE MIB September 2009
"(ACTUALCE) "(ACTUALCE)
This parameter reports the cyclic extension used on the line. It This parameter reports the cyclic extension used on the line. It
is coded as an unsigned integer from 2 to 16 in units of N/32 is coded as an unsigned integer from 2 to 16 in units of N/32
samples, where 2N is the IDFT size." samples, where 2N is the Inverse Discrete Fourier Transform
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.32 (ACTUALCE) (IDFT) size."
" 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 parameters "The table xdsl2LineSegmentTable contains status parameters
of VDSL2/ADSL/ADSL2 and ADSL2+ subcarriers. of VDSL2/ADSL/ADSL2 and ADSL2+ subcarriers.
The parameters in this table are updated when a measurement The parameters in this table are updated when a measurement
request is made using the xdsl2LineCmndConfBpsc object. request is made using the xdsl2LineCmndConfBpsc object.
skipping to change at page 72, line 33 skipping to change at page 74, line 30
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 parameters "The table xdsl2LineSegmentTable contains status parameters
of VDSL2/ADSL/ADSL2 and ADSL2+ subcarriers. of VDSL2/ADSL/ADSL2 and ADSL2+ subcarriers.
The parameters in this table are updated when a measurement The parameters in this table are updated when a measurement
request is made using the xdsl2LineCmndConfBpsc object. request is made using the xdsl2LineCmndConfBpsc object.
Note that a bits per subcarrier measurement is also performed Note that a bits-per-subcarrier measurement is also performed
during a line diagnostic procedure. This table provides an during a line diagnostic procedure. This table provides an
additional mechanism to fetch the bits per subcarrier data. This additional mechanism to fetch the bits-per-subcarrier data. This
additional mechanism is provided so that bits per subcarrier additional mechanism is provided so that bits-per-subcarrier
data may be fetched without forcing the line into no power state. data may be fetched without forcing the line into no power state.
This is useful because the bits per subcarrier allocation may be This is useful because the bits-per-subcarrier allocation may be
adjusted at show time due to rate adaption and bit swapping. adjusted at Showtime due to rate adaption and bit swapping.
The implementation of this additional mechanism for measuring The implementation of this additional mechanism for measuring
bits per subcarrier 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 parameters "The table xdsl2LineSegmentEntry contains status parameters
of VDSL2/ADSL/ADSL2 and ADSL2+ subcarriers. 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 of the value of NSus and NSds are, respectively, the indices of the
highest supported upstream and downstream subcarriers according highest supported upstream and downstream subcarriers according
to the selected implementation profile. For ADSL, NSus is equal to the selected implementation profile. For ADSL, NSus is equal
to NSCus-1 and NSds is equal to NSCds-1. to NSCus-1 and NSds is equal to NSCds-1.
RFC 5650 VDSL2-LINE MIB September 2009
One index of this table is an interface index where the interface One index of this table is an interface index where the interface
has an ifType of vdsl2(xxx). A second index of this table is the has an ifType of vdsl2(251). A second index of this table is the
transmission direction. A third index identifies the specific transmission direction. A third index identifies the specific
segment of the subcarriers 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,
skipping to change at page 73, line 47 skipping to change at page 75, line 43
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 subcarriers status information "The segment of the subcarriers status information
provided by this row. provided by this row.
Status parameters in this table are retrieved in segments. Status parameters in this table are retrieved in segments.
The first segment of the status information is retrieved with The first segment of the status information is retrieved with
xdsl2LineSegment=1, the second segment is retrieved with xdsl2LineSegment=1, the second segment is retrieved with
xdsl2LineSegment=2, and so on. When a status parameter is xdsl2LineSegment=2, and so on. When a status parameter is
retrieved in n segments where n<8) then, for that parameter, retrieved in n segments where n<8) then, for that parameter,
GET operations for the remaining segment numbers (n+1 to 8) will GET operations for the remaining segment numbers (n+1 to 8) will
respond with a zero-length OCTET STRING." 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
RFC 5650 VDSL2-LINE MIB September 2009
"The bits allocation per subcarrier. 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)
subcarriers. When more than 512 subcarriers are supported, the subcarriers. When more than 512 subcarriers are supported, 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
subcarriers. The second segment is used for the subcarriers 512 to subcarriers. The second segment is used for the subcarriers
1023 and so on. 512 to 1023 and so on.
The aggregate number of utilized nibbles on downstream direction The aggregate number of utilized nibbles in the downstream
(in all segments) depends on NSds, and on upstream direction it direction (in all segments) depends on NSds; in the
depends on NSus. upstream direction, it depends on NSus.
This value is referred here as NS. The segment number is in This value is referred to here as NS. The segment number is in
xdsl2SCStatusSegment. xdsl2SCStatusSegment.
Nibble i (0 <= i < MIN((NS+1)-(segment-1)*512,512)) in each Nibble i (0 <= i < MIN((NS+1)-(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 subcarrier 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 agent will create a row in this table "Row Status. The SNMP agent will create a row in this table
for storing the results of a measurement performed on the for storing the results of a measurement performed on the
associated line, if the row does not already exist. associated line, if the row does not already exist.
The SNMP manager is not permitted to create rows in this table or The SNMP manager is not permitted to create rows in this table or
set the row status to 'notInService'. In the first case, set the row status to 'notInService'. In the first case,
if the SNMP manager tries to create a new row, the SNMP agent if the SNMP manager tries to create a new row, the SNMP agent
responds with the value 'noCreation' in the error status responds with the value 'noCreation' in the error status
field of the response-PDU. In the latter case the SNMP agent field of the response-PDU. In the latter case, the SNMP agent
responds with the value 'wrongValue' in the error status responds with the value 'wrongValue' in the error status
field of the response-PDU. field of the response-PDU.
The SNMP agent may have limited resources; therefore, if multiple The SNMP agent may have limited resources; therefore, if multiple
rows co-exist in this table, it may fail to add new rows to this rows coexist in this table, it may fail to add new rows to this
table or allocate memory resources. table or allocate memory resources.
If that occurs, the SNMP agent responds with the value If that occurs, the SNMP agent responds with the value
'noResources' (for the xdsl2LineCmndConfBpscFailReason 'noResources' (for the 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. E.g., after retrieving the results. table according to any scheme. For example, after retrieving
the results.
RFC 5650 VDSL2-LINE MIB September 2009
When the SNMP manager deletes any row in this table, the SNMP When the SNMP manager deletes any row in this table, the SNMP
agent MUST delete all rows in this table that have the same agent MUST delete all rows in this table that have 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, per-band line "The table xdsl2LineBandTable contains the, per-band line
status parameters of the VDSL2/ADSL/ADSL2 or ADSL2+ line. status parameters of the VDSL2/ADSL/ADSL2 or ADSL2+ line.
The parameters in this table are updated at line initialisation The parameters in this table are updated at line initialization
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
"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 table is a has an ifType of vdsl2(251). A second index of this table is a
per-band index covering both VDSL2 and ADSL/ADSL2/ADSL2+." per-band index covering both VDSL2 and ADSL/ADSL2/ADSL2+."
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' and 'downstream' For ADSL/ADSL2/ADSL2+, the values 'upstream' and 'downstream'
will always be present. will always be present.
RFC 5650 VDSL2-LINE MIB September 2009
For VDSL2, a subset of {'us0', 'ds1', 'us1' ... 'ds4', 'us4' } For VDSL2, a subset of {'us0', 'ds1', 'us1' ... 'ds4', 'us4' }
will always will always be present, together with rows for
be present, together with rows for
'upstream' and 'downstream', in which only the 'upstream' and 'downstream', in which only the
xdsl2LineBandStatusSnrMargin object is expected to hold a valid xdsl2LineBandStatusSnrMargin object is 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
skipping to change at page 76, line 34 skipping to change at page 78, line 31
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 xTU-C and the total power received by the xTU-R over all
subcarriers 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 xTU-R measured difference in the total power transmitted by the xTU-R
and the total power received by the xTU-C over all subcarriers of and the total power received by the xTU-C over all subcarriers of
that band during initialization. that band during initialization.
Values range from 0 to 1270 in units of 0.1 dB (Physical values Values range from 0 to 1270 in units of 0.1 dB (physical 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 }
skipping to change at page 77, line 4 skipping to change at page 78, line 49
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 xTU-C and the total power received by the xTU-R over all
subcarriers 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
RFC 5650 VDSL2-LINE MIB September 2009
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 subcarriers of and the total power received by the xTU-C over all subcarriers of
that band during Showtime. that band during Showtime.
Values range from 0 to 1270 in units of 0.1 dB (Physical values Values range from 0 to 1270 in units of 0.1 dB (physical 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"
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 direction received at the xTU (xTU-R for a band in the downstream direction
and xTU-C for a band in the upstream direction), such that the and xTU-C for a band in the upstream direction), such that the
BER requirements are met for all bearer channels received at the BER requirements are met for all bearer channels received at the
xTU. Values range from -640 to 630 in units of 0.1 dB (Physical xTU. Values range from -640 to 630 in units of 0.1 dB (physical
values are -64 to 63 dB). values are -64 to 63 dB).
A special value of 0x7FFFFFFF (2147483647) indicates the SNR A special value of 0x7FFFFFFF (2147483647) indicates the 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 SNR A special value of 0x7FFFFFFE (2147483646) indicates the 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 --
------------------------------------------------ ------------------------------------------------
xdsl2ChannelStatusTable OBJECT-TYPE xdsl2ChannelStatusTable OBJECT-TYPE
SYNTAX SEQUENCE OF Xdsl2ChannelStatusEntry SYNTAX SEQUENCE OF 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
RFC 5650 VDSL2-LINE MIB September 2009
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
"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 a DSL channel. A second index of
has an ifType of a DSL channel. A second index of this table is this table is the termination unit."
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 79, line 11 skipping to change at page 80, line 54
DESCRIPTION DESCRIPTION
"The termination unit." "The termination unit."
::= { xdsl2ChannelStatusEntry 1 } ::= { xdsl2ChannelStatusEntry 1 }
xdsl2ChStatusActDataRate OBJECT-TYPE xdsl2ChStatusActDataRate 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
"The actual net data rate that the bearer channel is "The actual net data rate at which the bearer channel is
operating at, if in L0 power management state. In L1 or L2
RFC 5650 VDSL2-LINE MIB September 2009
operating, if in L0 power management state. In L1 or L2
states, it relates to the previous L0 state. The data rate is states, it relates to the previous L0 state. The data rate is
coded in bit/s." coded in 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)" (Actual data rate)"
DEFVAL { 0 } DEFVAL { 0 }
::= { xdsl2ChannelStatusEntry 2 } ::= { xdsl2ChannelStatusEntry 2 }
xdsl2ChStatusPrevDataRate OBJECT-TYPE xdsl2ChStatusPrevDataRate OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "bits/second" UNITS "bits/second"
skipping to change at page 80, line 11 skipping to change at page 82, line 4
::= { 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
"Actual impulse noise protection. "Actual impulse noise protection.
This parameter reports the actual impulse noise protection (INP) This parameter reports the actual impulse noise protection (INP)
on the bearer channel in the L0 state. In the L1 or L2 state, the
parameter contains the INP in the previous L0 state. For ADSL, RFC 5650 VDSL2-LINE MIB September 2009
this value is computed according to the formula specified in the
relevant Recommendation based on the actual framing parameters. on the bearer channel in the L0 state. In the L1 or L2 state,
For ITU-T Rec. G.993.2, the method to report this value is the parameter contains the INP in the previous L0 state. For
according to the INPREPORT parameter. The value is coded in ADSL, this value is computed according to the formula specified
fractions of DMT symbols with a granularity of 0.1 symbols. in the relevant Recommendation based on the actual framing
The range is from 0 to 25.4. The special value of 255 indicates parameters. For ITU-T Recommendation G.993.2, the method to
an ACTINP higher than 25.4." report this value is according to the INPREPORT parameter.
The value is coded in fractions of DMT symbols with a
granularity of 0.1 symbols. 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 (ACTINP)" REFERENCE "ITU-T G.997.1, paragraph #7.5.2.4 (ACTINP)"
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
"Impulse noise protection reporting mode." "Impulse noise protection reporting mode."
skipping to change at page 80, line 44 skipping to change at page 82, line 41
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
"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 in which redundancy bytes per codeword used in the latency path in which
the bearer channel is transported. The value is coded in bytes. the bearer channel is transported. The value is 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 (NFEC)" 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
"Actual number of Reed-Solomon redundancy bytes. "Actual number of Reed-Solomon redundancy bytes.
RFC 5650 VDSL2-LINE MIB September 2009
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 in which redundancy bytes per codeword used in the latency path in which
the bearer channel is transported. The value is coded in bytes. the bearer channel is transported. The value is 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 (RFEC)" 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
"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 symbol
assigned to the latency path in which the bearer channel is assigned to the latency path in which the bearer channel is
transported. This value does not include trellis overhead. The transported. This value does not include trellis overhead. The
value is coded in bits. 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 (LSYMB)" 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
"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 used
in the latency path in which the bearer channel is transported. in the latency path in which the bearer channel is transported.
The value ranges from 1 to 4096 in steps of 1. 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 (INTLVDEPTH) 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
"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 interleaver
used in the latency path in which the bearer channel is used in the latency path in which the bearer channel is
transported. transported.
RFC 5650 VDSL2-LINE MIB September 2009
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 (INTLVBLOCK) 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
"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 path in
which the bearer is transported. 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 latency index 0, and the INTERLEAVED path shall be mapped to the 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)" (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 bitmap of
possible conditions. possible conditions.
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)" (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).
This is a bit-map of possible conditions. This is a bitmap of possible conditions.
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)"
RFC 5650 VDSL2-LINE MIB September 2009
(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 84, line 7 skipping to change at page 85, line 49
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
status parameters for VDSL2/ADSL/ADSL2 and ADSL2+ that status parameters for VDSL2/ADSL/ADSL2 and ADSL2+ that
provide information about the size of parameters in provide information about the size of parameters in
xdsl2SCStatusSegmentTable. xdsl2SCStatusSegmentTable.
The parameters in this table MUST be updated after a loop The parameters in this table MUST be updated after a loop
diagnostic procedure and MAY be updated after a line diagnostic procedure, MAY be updated after a line
initialisation and MAY be updated at showtime." initialization, and MAY be updated at Showtime."
::= { xdsl2Status 3 } ::= { xdsl2Status 3 }
xdsl2SCStatusEntry OBJECT-TYPE xdsl2SCStatusEntry OBJECT-TYPE
SYNTAX Xdsl2SCStatusEntry SYNTAX Xdsl2SCStatusEntry
RFC 5650 VDSL2-LINE MIB September 2009
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"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(251). 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 85, line 7 skipping to change at page 86, line 48
::= { xdsl2SCStatusEntry 1 } ::= { xdsl2SCStatusEntry 1 }
xdsl2SCStatusLinScale OBJECT-TYPE xdsl2SCStatusLinScale OBJECT-TYPE
SYNTAX Unsigned32 (1..65535) 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. It is represented as an unsigned integer in the range procedure. It is represented as an unsigned integer in the range
from 1 to 2^16-1." 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
RFC 5650 VDSL2-LINE MIB September 2009
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 subcarriers 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 size parameter is equal to one and, for VDSL2, it is equal to the size
of a subcarrier 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 (1..65535) 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 an unsigned measure the Hlog(f) values. It is represented as 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 contain After a loop diagnostic procedure, this parameter shall contain
the number of symbols used to measure the Hlog(f). It should the number of symbols used to measure the Hlog(f). It should
correspond to the value specified in the Recommendation (e.g., the correspond to the value specified in the Recommendation (e.g., the
number of symbols in 1 s time interval for ITU-T Rec. number of symbols in 1 s time interval for ITU-T Recommendation.
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 subcarriers 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 1, and for VDSL2, it is
equal to the size of a subcarrier 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
RFC 5650 VDSL2-LINE MIB September 2009
SYNTAX Unsigned32 (1..65535) 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 in the range measure the QLN(f) values. It is an unsigned integer in the range
from 1 to 2^16-1. After a loop diagnostic procedure, this from 1 to 2^16-1. After a loop diagnostic procedure, this
parameter shall contain the number of symbols used to measure the parameter shall contain the number of symbols used to measure the
QLN(f). It should correspond to the value specified in the QLN(f). It should correspond to the value specified in the
Recommendation (e.g., the number of symbols in 1 s time interval Recommendation (e.g., the number of symbols in 1 s time interval
for ITU-T Rec. G.992.3)." for ITU-T Recommendation 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 subcarriers 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 1, and for VDSL2, it is
equal to the size of a subcarrier 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 (1..65535) 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 to measure "This parameter contains the number of symbols used to measure
the SNR(f) values. It is an unsigned integer in the range from 1 the SNR(f) values. It is an unsigned integer in the range from 1
to 2^16-1. After a loop diagnostic procedure, this parameter shall to 2^16-1. After a loop diagnostic procedure, this parameter
contain the number of symbols used to measure the SNR(f). shall contain the 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 Recommendation
(e.g., the number of symbols in 1 s time interval for ITU-T Rec. (e.g., the number of symbols in 1 s time interval for ITU-T
G.992.3)." Recommendation 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
RFC 5650 VDSL2-LINE MIB September 2009
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 subcarriers per group used to report the SNR values "Number of subcarriers per group used to report the SNR 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 1, and for VDSL2, it is
equal to the size of a subcarrier 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 receiver currently attainable by the xTU-C transmitter and xTU-R receiver
(when referring to downstream direction) or by the xTU-R (when referring to downstream direction) or by the xTU-R
transmitter and xTU-C receiver (when referring to upstream transmitter and xTU-C receiver (when referring to 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 the DELT most recent DELT performed on the associated line. Once the DELT
process is over, the parameter no longer changes until the row is process is over, the parameter no longer changes 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 agent will create a row in this table "Row Status. The SNMP agent will create a row in this table
for storing the results of a DELT performed on the associated for storing the results of a DELT performed on the associated
line, if the row does not already exist. line, if the row does not already exist.
When a row is created in this table, the SNMP agent should also When a row is created in this table, the SNMP agent should also
create corresponding rows in the tables xdsl2SCStatusBandTable and create corresponding rows in the tables xdsl2SCStatusBandTable and
xdsl2SCStatusSegmentTable. xdsl2SCStatusSegmentTable.
The SNMP manager is not permitted to create rows in this table or The SNMP manager is not permitted to create rows in this table or
set the row status to 'notInService'. In the first case, set the row status to 'notInService'. In the first case,
RFC 5650 VDSL2-LINE MIB September 2009
if the SNMP manager tries to create a new row, the SNMP agent if the SNMP manager tries to create a new row, the SNMP agent
responds with the value 'noCreation' in the error status responds with the value 'noCreation' in the error status
field of the response-PDU. In the latter case the SNMP agent field of the response-PDU. In the latter case the SNMP agent
responds with the value 'wrongValue' in the error status responds with the value 'wrongValue' in the error status
field of the response-PDU. field of the response-PDU.
When a row is deleted in this table, the SNMP agent should also When a row is deleted in this table, the SNMP agent should also
delete corresponding rows in the tables xdsl2SCStatusBandTable and delete corresponding rows in the tables xdsl2SCStatusBandTable and
xdsl2SCStatusSegmentTable. xdsl2SCStatusSegmentTable.
The SNMP agent may have limited resources; therefore, if multiple The SNMP agent may have limited resources; therefore, if multiple
rows co-exist in this table, it may fail to add new rows to this rows coexist in this table, it may fail to add new rows to this
table or allocate memory resources for a new DELT process. If table or allocate memory resources for a new DELT process. If
that occurs, the SNMP agent responds with either the value that occurs, the SNMP agent responds with either the value
'tableFull' or the value 'noResources' (for 'tableFull' or the value 'noResources' (for
the xdsl2LineCmndConfLdsfFailReason object in xdsl2LineTable). the xdsl2LineCmndConfLdsfFailReason 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. E.g., after retrieving the table according to any scheme. For example, 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
skipping to change at page 89, line 16 skipping to change at page 91, line 4
diagnostic procedure." 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
"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 table is the
RFC 5650 VDSL2-LINE MIB September 2009
has an ifType of vdsl2(251). A second index of this table is the
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 89, line 50 skipping to change at page 91, line 41
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 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 xTU-C and the total power received by the xTU-R over all
subcarriers during diagnostics mode. subcarriers 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 subcarriers 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 0 It ranges from 0 to 1270 units of 0.1 dB (physical values 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 the DELT most recent DELT performed on the associated line. Once the DELT
process is over, the parameter no longer changes until the row is process is over, the parameter no longer changes 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 }
RFC 5650 VDSL2-LINE MIB September 2009
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 in the downstream direction, it is the
measured difference in the total power transmitted by the xTU-C measured difference in the total power transmitted by the xTU-C
and the total power received by the xTU-R over all subcarriers and the total power received by the xTU-R over all subcarriers
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 xTU-R and the difference in the total power transmitted by the xTU-R and the
total power received by the xTU-C over all subcarriers during total power received by the xTU-C over all subcarriers during
Showtime after the diagnostics mode. Showtime after the diagnostics mode.
It ranges from 0 to 1270 units of 0.1 dB (Physical values are 0 It ranges from 0 to 1270 units of 0.1 dB (physical values 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 the DELT most recent DELT performed on the associated line. Once the DELT
process is over, the parameter no longer changes until the row is process is over, the parameter no longer changes 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)
skipping to change at page 91, line 9 skipping to change at page 92, line 48
------------------------------------------------ ------------------------------------------------
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+ subcarriers. parameters of VDSL2/ADSL/ADSL2 and ADSL2+ subcarriers.
Several objects in the table refer to NSus and NSds. For G.993.2, Several objects in the table refer to NSus and NSds. For
the value of NSus and NSds are respectively the indices of the G.993.2, the value of NSus and NSds are, respectively, the
highest supported upstream and downstream subcarriers according indices of the highest supported upstream and downstream
to the selected implementation profile. subcarriers according to the selected implementation profile.
For 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.
The parameters in this table MUST be updated after a loop The parameters in this table MUST be updated after a loop
RFC 5650 VDSL2-LINE MIB September 2009
diagnostic procedure and MAY be updated after a line diagnostic procedure and MAY be updated after a line
initialisation and MAY be updated at showtime." initialization 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
"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(251). 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 subcarriers 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 92, line 9 skipping to change at page 93, line 47
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 subcarriers status information provided by "The segment of the subcarriers status information provided by
this row. this row.
Several status parameters in this table are retrieved in segments. Several status parameters in this table are retrieved in segments.
The first segment of the status information is retrieved with The first segment of the status information is retrieved with
xdsl2SCStatusSegment=1, the second segment is retrieved with xdsl2SCStatusSegment=1, the second segment is retrieved with
xdsl2SCStatusSegment=2, and so on. When any status parameter is xdsl2SCStatusSegment=2, and so on. When any status parameter is
retrieved in n segments where n<8) then, for that parameter, retrieved in n segments where n<8), then for that parameter,
GET operations for the remaining segment numbers (n+1 to 8) will GET operations for the remaining segment numbers (n+1 to 8) will
respond with a zero-length OCTET STRING." 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))
RFC 5650 VDSL2-LINE MIB September 2009
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 direction. values in linear scale for the respective transmission direction.
It is designed to support up to 512 (downstream) subcarriers It is designed to support up to 512 (downstream) subcarrier
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 on The number of utilized values in the downstream direction depends
NSds, and on upstream direction it depends on NSus. This value is on NSds; in the upstream direction, it depends on NSus. This
referred here as NS. value is referred to here as NS.
Each array entry represents the real component [referred here as Each array entry represents the real component (referred to here
a(i)] of Hlin(f = i*Df) value for a particular subcarrier group as a(i)) of Hlin(f = i*Df) value for a particular subcarrier
index i (0 <= i <= NS). 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) 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 subcarriers group because it is out of the could be done for the subcarrier group because it is out of 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 direction. values in linear scale for the respective transmission direction.
It is designed to support up to 512 (downstream) subcarrier
It is designed to support up to 512 (downstream) subcarriers
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 on The number of utilized values in the downstream direction depends
NSds, and on upstream direction it depends on NSus. This value is on NSds; in the upstream direction, it depends on NSus. This
referred here as NS. value is referred to here as NS.
Each array entry represents the imaginary component [referred Each array entry represents the imaginary component (referred to
here as b(i)] of Hlin(f = i*Df) value for a particular here as b(i)) of Hlin(f = i*Df) value for a particular
subcarrier 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 the where scale is xdsl2SCStatusLinScale and a(i) (provided by the
xdsl2SCStatusSegmentLinReal object] and b(i) are in the range xdsl2SCStatusSegmentLinReal object) and b(i) are in the 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 subcarriers group because it is out of the
RFC 5650 VDSL2-LINE MIB September 2009
could be done for the subcarrier group because it is out of 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) subcarriers groups designed to support up to 512 (downstream) subcarrier 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 in the downstream direction depends
on NSds, and on upstream direction it depends on NSus. This on NSds; in the upstream direction, it depends on NSus. This
value is referred here as NS. value is referred to 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 subcarrier 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 subcarrier 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 in big Each value in this array is 16 bits wide and is stored in big
endian format." endian format."
skipping to change at page 94, line 15 skipping to change at page 95, line 52
::= { 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 up for the respective transmission direction. It is designed for up
to 512 (downstream) subcarriers groups and can be retrieved in a to 512 (downstream) subcarrier groups and can be retrieved in a
single segment. single segment.
The number of utilized values on downstream direction depends on The number of utilized values in the downstream direction depends
NSds, and on upstream direction it depends on NSus. This value is
referred here as NS. RFC 5650 VDSL2-LINE MIB September 2009
on NSds; in the upstream direction, it depends on NSus. This
value is referred to 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 subcarrier 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 range The QLN(f) is represented as ( -23-n(i)/2), with n(i) in the range
0 to 254. A special value n(i)=255 indicates that no measurement 0 to 254. A special value n(i)=255 indicates that no measurement
could be done for the subcarrier group because it is out of the could be done for the subcarrier group because it is out of the
passband or that the noise PSD is out of range to be represented. passband or that the noise PSD is out of range 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)"
skipping to change at page 94, line 41 skipping to change at page 96, line 30
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 subcarrier group, expressing the ratio "The SNR Margin per subcarrier group, expressing the ratio
between the received signal power and received noise power per between the received signal power and received noise power per
subscriber group. It is an array of 512 octets, designed for subscriber group. It is an array of 512 octets, designed for
supporting up to 512 (downstream) subcarriers groups and can be supporting up to 512 (downstream) subcarrier groups and can be
retrieved in a single segment. retrieved in a single segment.
The number of utilized octets on downstream direction depends on The number of utilized octets in the downstream direction depends
NSds, and on upstream direction it depends on NSus. This value is on NSds; in the upstream direction, it depends on NSus. This
referred here as NS. value is referred to 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 254 to indicate that the respective downstream or upstream
subcarrier group i has SNR of: subcarrier group i has an SNR of:
(-32 + xdsl2SCStatusSegmentSnr(i)/2) in dB (i.e., -32 to 95dB). (-32 + xdsl2SCStatusSegmentSnr(i)/2) in dB (i.e., -32 to 95 dB).
The special value 255 means that no measurement could be done for The special value 255 means that no measurement could be done for
the subcarrier group because it is out of the PSD mask passband or the subcarrier group because it is out of the PSD mask passband or
that the noise PSD is out of range to be represented. Each value that the noise PSD is out of range to be 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 subcarrier. 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)
subcarriers. When more then 512 subcarriers are supported, the
RFC 5650 VDSL2-LINE MIB September 2009
subcarriers. When more than 512 subcarriers are supported, 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
subcarriers. The second segment is used for the subcarriers 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 direction The aggregate number of utilized nibbles in the downstream
(in all segments) depends on NSds, and on upstream direction it direction (in all segments) depends on NSds; in the 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 to here as NS. The segment number is in
xdsl2SCStatusSegment. xdsl2SCStatusSegment.
Nibble i (0 <= i < MIN((NS+1)-(segment-1)*512,512)) in each Nibble i (0 <= i < MIN((NS+1)-(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 subcarrier 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 subcarrier. An array of 512 16-bits "The gain allocation per subcarrier. An array of 512 16-bit
values, designed for supporting up to 512 (downstream) values, designed for supporting up to 512 (downstream)
subcarriers. When more then 512 subcarriers are supported, the subcarriers. When more then 512 subcarriers are supported, 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
subcarriers. The second segment is used for the subcarriers 512 to subcarriers. The second segment is used for the subcarriers 512
1023 and so on. to 1023 and so on.
The aggregate number of utilized octets on downstream direction The aggregate number of utilized octets in the downstream
depends on NSds, and on upstream direction it depends on NSus. direction depends on NSds; in the upstream direction, it depends
This value is referred here as NS. The segment number is in on NSus. This value is referred to here as NS. The segment
xdsl2SCStatusSegment. number is in xdsl2SCStatusSegment.
Value i (0 <= i < MIN((NS+1)-(segment-1)*512,512)) in each Value i (0 <= i < MIN((NS+1)-(segment-1)*512,512)) in each
segment is set to a value in the range 0 to 4093 to indicate that segment is set to a value in the range 0 to 4093 to indicate that
the respective downstream or upstream subcarrier 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 linear The gain value is represented as a multiple of 1/512 on a linear
scale. Each value in this array is 16 bits wide and is stored in scale. Each value in this array is 16 bits wide and is 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 --
RFC 5650 VDSL2-LINE MIB September 2009
------------------------------------------------ ------------------------------------------------
xdsl2LineInventoryTable OBJECT-TYPE xdsl2LineInventoryTable OBJECT-TYPE
SYNTAX SEQUENCE OF Xdsl2LineInventoryEntry SYNTAX SEQUENCE OF Xdsl2LineInventoryEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The table xdsl2LineInventoryTable contains inventory of the "The table xdsl2LineInventoryTable contains an inventory of the
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
"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 table is the has an ifType of vdsl2(251). A second index of this table is the
termination unit." termination unit."
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,
skipping to change at page 97, line 16 skipping to change at page 98, line 53
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The termination unit." "The termination unit."
::= { xdsl2LineInventoryEntry 1 } ::= { xdsl2LineInventoryEntry 1 }
xdsl2LInvG994VendorId OBJECT-TYPE xdsl2LInvG994VendorId 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 G.994.1 Vendor ID as inserted in the G.994.1 CL/CLR "The ADSL Transceiver Unit (ATU) G.994.1 Vendor ID as
message. It consists of 8 binary octets, including a country
RFC 5650 VDSL2-LINE MIB September 2009
inserted in the G.994.1 CL/CLR message.
It consists of 8 binary octets, including a country
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 for integrator) as 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 G.992.3, 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). 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 to 16 Channel (xTU-R in G.992.1 and G.992.2). It consists of up 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 specific Channel (xTU-R in G.992.1 and G.992.2). It is vendor-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
RFC 5650 VDSL2-LINE MIB September 2009
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 passed, and '1' if the self-test failed. The self-test 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 or coding types. It is coded in a bitmap representation with 1 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 from supports the respective coding. The value may be derived from
the handshaking procedures defined in G.994.1. A set of xDSL the handshaking procedures defined in G.994.1. A set 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 --
------------------------------------------------ ------------------------------------------------
skipping to change at page 99, line 9 skipping to change at page 100, line 47
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 templates. 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 agent When the number of bearer channels is increased, the SNMP agent
SHOULD create rows in all tables indexed by a channel index. When SHOULD create rows in all tables indexed by a channel index.
the number of bearer channels is decreased, the SNMP agent SHOULD When the number of bearer channels is decreased, the SNMP agent
delete rows in all tables indexed by a channel index. SHOULD delete rows in all tables indexed by a 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 tables xdsl2ChannelStatusTable, xdsl2PMChCurrTable, and all other tables
indexed by a channel index. indexed by a channel index.
RFC 5650 VDSL2-LINE MIB September 2009
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 persistent Entries in this table MUST be maintained in a 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
"A default template with an index of 'DEFVAL' will always "A default template with an index of 'DEFVAL' will always
exist exist, and its parameters will be set to vendor-specific values,
and its parameters will be set to vendor-specific values, unless 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 100, line 17 skipping to change at page 102, line 5
xdsl2LConfTempTemplateName OBJECT-TYPE xdsl2LConfTempTemplateName OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE(1..32)) SYNTAX SnmpAdminString (SIZE(1..32))
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object 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 }
RFC 5650 VDSL2-LINE MIB September 2009
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/ADSL2 and ADSL2+ line configuration Profile Table, VDSL2/ADSL/ADSL2 and ADSL2+ line configuration Profile Table
(xdsl2LineConfProfTable) that applies for this DSL line." (xdsl2LineConfProfTable) that 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 VDSL2/ "The value of this object identifies the row in the VDSL2/
ADSL/ADSL2 and ADSL2+ channel configuration Profile Table, ADSL/ADSL2 and ADSL2+ channel configuration Profile Table
(xdsl2ChConfProfileTable) that applies to DSL bearer channel #1. (xdsl2ChConfProfileTable) that applies to DSL bearer channel #1.
The channel profile name specified here MUST match the name of an The channel profile name specified here MUST match the name of an
existing row in the xdsl2ChConfProfileTable table." 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 "percent" 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 percent) that should be
taken into account for the bearer channel #1 when performing rate taken into account for the bearer channel #1 when performing rate
adaptation on Downstream. The ratio refers to the available data adaptation on Downstream. The ratio refers to the available data
rate in excess of the Minimum Data Rate, summed over all bearer rate in excess of the Minimum Data Rate, summed 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 on excess data rate to be assigned to all other bearer channels on
Downstream direction. The sum of rate adaptation ratios over all Downstream direction. The sum of rate adaptation ratios over all
bearers on the same direction shall be equal to 100%. bearers on the sam