draft-ietf-adslmib-xdsl-vop-01.txt   draft-ietf-adslmib-xdsl-vop-02.txt 
Network Working Group M. Morgenstern Network Working Group M. Morgenstern
Internet-Draft ECI Telecom Ltd. Internet-Draft ECI Telecom Ltd.
Intended status: Standards Track S. Baillie Intended status: Standards Track S. Baillie
Expires: December 27, 2013 Expires: February 02, 2014
M. Freudenberger M. Freudenberger
T-Systems International GmbH T-Systems International GmbH
June 25, 2013 August 01, 2013
Definitions of Managed Objects for Definitions of Managed Objects for
Very High Speed Digital Subscriber Line 2 (VDSL2) Very High Speed Digital Subscriber Line 2 (VDSL2)
draft-ietf-adslmib-xdsl-vop-01.txt draft-ietf-adslmib-xdsl-vop-02.txt
Abstract Abstract
This document defines a Management Information Base (MIB) module for This document defines a Management Information Base (MIB) module for
use with network management protocols in the Internet community. In use with network management protocols in the Internet community. In
particular, it describes objects used for managing parameters of the particular, it describes objects used for managing parameters of the
"Very High Speed Digital Subscriber Line 2 (VDSL2)" interface type, "Very High Speed Digital Subscriber Line 2 (VDSL2)" interface type,
which are also applicable for managing Asymmetric Digital Subscriber which are also applicable for managing Asymmetric Digital Subscriber
Line (ADSL), ADSL2, and ADSL2+ interfaces. Line (ADSL), ADSL2, and ADSL2+ interfaces.
skipping to change at page 1, line 39 skipping to change at page 1, line 39
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on December 27, 2013. This Internet-Draft will expire on February 02, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 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 Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 15 skipping to change at page 2, line 15
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. The Internet-Standard Management Framework . . . . . . . . . 2 1. The Internet-Standard Management Framework . . . . . . . . . 2
2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Relationship to Other MIBs . . . . . . . . . . . . . . . 4 2.1. Relationship to Other MIBs . . . . . . . . . . . . . . . 4
2.2. IANA Considerations . . . . . . . . . . . . . . . . . . . 9 2.2. IANA Considerations . . . . . . . . . . . . . . . . . . . 10
2.3. Conventions Used in the MIB Module . . . . . . . . . . . 9 2.3. Conventions Used in the MIB Module . . . . . . . . . . . 10
2.4. Structure . . . . . . . . . . . . . . . . . . . . . . . . 13 2.4. Structure . . . . . . . . . . . . . . . . . . . . . . . . 14
2.5. Persistence . . . . . . . . . . . . . . . . . . . . . . . 16 2.5. Persistence . . . . . . . . . . . . . . . . . . . . . . . 17
2.6. Line Topology . . . . . . . . . . . . . . . . . . . . . . 19 2.6. Line Topology . . . . . . . . . . . . . . . . . . . . . . 20
2.7. Counters, Interval Buckets, and Thresholds . . . . . . . 19 2.7. Counters, Interval Buckets, and Thresholds . . . . . . . 20
2.8. Overview of the Vector of Profiles Management Model . . . 22 2.8. Profiles . . . . . . . . . . . . . . . . . . . . . . . . 23
2.9. Profiles ( Legacy Method ) . . . . . . . . . . . . . . . 23 2.9. Overview of the Vector of Profiles Management Model . . . 27
2.10. Notifications . . . . . . . . . . . . . . . . . . . . . . 27 2.10. Notifications . . . . . . . . . . . . . . . . . . . . . . 28
3. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 28 3. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 29
4. Implementation Analysis . . . . . . . . . . . . . . . . . . . 226 4. Implementation Analysis . . . . . . . . . . . . . . . . . . . 251
5. Security Considerations . . . . . . . . . . . . . . . . . . . 227 5. Security Considerations . . . . . . . . . . . . . . . . . . . 252
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 238 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 263
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 238 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 263
7.1. Normative References . . . . . . . . . . . . . . . . . . 238 7.1. Normative References . . . . . . . . . . . . . . . . . . 263
7.2. Informative References . . . . . . . . . . . . . . . . . 239 7.2. Informative References . . . . . . . . . . . . . . . . . 264
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 240 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 265
1. The Internet-Standard Management Framework 1. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to Section 7 of Internet-Standard Management Framework, please refer to Section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
skipping to change at page 4, line 48 skipping to change at page 4, line 48
by the Vector of Profiles management model. Some of the management by the Vector of Profiles management model. Some of the management
objects defined in RFC 5650 have been changed to correct errors and objects defined in RFC 5650 have been changed to correct errors and
some of the management objects defined in RFC 5650 have been extended some of the management objects defined in RFC 5650 have been extended
to support new functionality defined in ITU-T G.997.1 since the to support new functionality defined in ITU-T G.997.1 since the
publication of RFC 5650. publication of RFC 5650.
Each XDSL line requires a large amount of configuration data to Each XDSL line requires a large amount of configuration data to
operate correctly. In RFC 5650, the configuration data required by operate correctly. In RFC 5650, the configuration data required by
each line is stored in an object called a template. In this MIB each line is stored in an object called a template. In this MIB
module, the configuration data required by each line is stored in an module, the configuration data required by each line is stored in an
object called a vector of profiles ( or a vector for short ). Hence object called a Vector of Profiles ( or a vector for short ). Hence
one of the major differences between this MIB module and RFC 5650 is one of the major differences between this MIB module and RFC 5650 is
that configuration data is stored in a vector in this MIB module and that configuration data is stored in a vector in this MIB module and
configuration data is stored in a template in the RFC 5650 MIB configuration data is stored in a template in the RFC 5650 MIB
module. For the purpose of backward compatability, the template module. For the purpose of backward compatability, the template
management objects remain defined in this MIB module but are management objects remain defined in this MIB module but are
described as belonging to the legacy management model. described as belonging to the legacy management model.
New implementations of the VDSL2-LINE-MIB, should use the vector of New implementations of the VDSL2-LINE-MIB, should use the Vector of
profiles management model instead of the template management model Profiles management model instead of the template management model
because it is a much more efficient way to store the configuration because it is a much more efficient way to store the configuration
data. In addition, new implementations should use the vector of data. In addition, new implementations should use the Vector of
profiles management model because new management objects defined in Profiles management model because new management objects defined in
ITU-T G.997.1 have been added to the vector model and have not been ITU-T G.997.1 have been added to the vector model and have not been
added to the template model. added to the template model.
In order for the SNMP manager (the management system) be able to
determine whether a specific DSLAM supports the Vector of Profiles
management model, or the template management model, it can GET the
value of xdsl2ScalarVopAttachmentMethodCapabilties which also selects
between two modes of the Vector of Profiles, as explained later on in
this document. If a DSLAM does not support the Vector of Profiles
management mode then access to that managed object is supposed to
fail with SNMP error-code='noSuchName'.
2.1.1.1. New management objects defined in this MIB module 2.1.1.1. New management objects defined in this MIB module
This MIB module defines a number of additional management objects This MIB module defines a number of additional management objects
compared to RFC 5650. The following management objects are required compared to RFC 5650. The following management objects are required
by the vector of profiles management model and are defined in this by the Vector of Profiles management model and are defined in this
module. module.
xdsl2ScalarVopAttachmentMethodCapabilties xdsl2ScalarVopAttachmentMethodCapabilties
xdsl2ScalarVopAttachmentMethodConfigured xdsl2ScalarVopAttachmentMethodConfigured
xdsl2ScalarVopAttachmentMethodCurrent xdsl2ScalarVopAttachmentMethodCurrent
xdsl2VopVectorIndexNext xdsl2VopVectorIndexNext
xdsl2VopLineTable xdsl2VopLineTable
xdsl2VopVectorTable xdsl2VopVectorTable
xdsl2VopVectorActualTable xdsl2VopVectorActualTable
xdsl2VopDataRateProfilesTable
xdsl2VopLSpectrumProfilesTable
xdsl2VopModeSpecMapTable
xdsl2VopModeSpecProfilesTable
2.1.1.2. Legacy management objects defined in this MIB module 2.1.1.2. Legacy management objects defined in this MIB module
This MIB module continues to define the management objects required This MIB module continues to define the management objects required
by the legacy management model for the purpose of backward by the legacy management model for the purpose of backward
compatibility. The legacy management objects are listed here : compatibility. The legacy management objects are listed here :
xdsl2LineConfTemplate xdsl2LineConfTemplate
xdsl2LineConfFallbackTemplate xdsl2LineConfFallbackTemplate
skipping to change at page 13, line 26 skipping to change at page 14, line 14
o Xdsl2LineTxRefVnDs o Xdsl2LineTxRefVnDs
o Xdsl2LineTxRefVnUs o Xdsl2LineTxRefVnUs
o Xdsl2BitsAlloc o Xdsl2BitsAlloc
o Xdsl2MrefPsdDs o Xdsl2MrefPsdDs
o Xdsl2MrefPsdUs o Xdsl2MrefPsdUs
o Xdsl2RtxModes
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 22, line 10 skipping to change at page 23, line 10
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, in addition to reporting that the of seconds the interval lasted, in addition to reporting that the
interval is Valid. interval is Valid.
2.8. Overview of the Vector of Profiles Management Model 2.8. Profiles
The vector of profiles management model provides an alternative to
the legacy template management model. The vector of profile
management model provides a more efficient way to store
configuration. The vector of profiles management model is also more
up to date because it contains configuration data that was defined in
the most recent versions of ITU-T G.997.1.
The template management model is not efficient in the way
configuration data is stored. In the template model, line level
configuration data is stored in a line profile and channel level
configuration data is stored in a channel profile. It is quite
common for two XDSL lines to require almost identical configuration
data but having a slightly different value for one or two parameters.
The template model will require two profiles to satisfy the
requirements of the two XDSL lines and hence a large amount of data
is duplicated in the two profiles. The vector of profiles management
model attempts to solve this problem of duplicated data by splitting
the large line profile and large channel profiles into many smaller
profiles.
The vector that is defined in the vector of profiles management model
is a management object that contains only pointers. The vector
contains pointers to the smaller profile objects mentioned in the
paragraph above. There are two methods that can be used to associate
a vector with a XDSL line, the methods are called direct attachment
method and indirect attachment method.
2.8.1. The Direct Attachment Method
For the direct attachment method, one vector object is automatically
created for each XDSL line. The SNMP agent creates the vector
objects and hence the SNMP manager is not permitted to write to the
Row Status attribute of the vector object.
Each XDSL line is associated with one vector object because the
vector object will have the same index as the XDSL line.
2.8.2. The Indirect Attachment Method
For the indirect attachment method, the SNMP manager is responsible
for creating and deleting the vector objects using the Row Status
attribute. The SNMP manager then uses the xdsl2VopLineVectorId
attribute to associate a XDSL line with a vector object.
Initially, the SNMP agent will create one single vector object (
called the default vector and having an index of 1 ) and all XDSL
lines will refer to this vector. The default vector cannot be
deleted.
2.9. Profiles ( Legacy Method )
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. In one implementation mode of this MIB (legacy
level provisioning and another type of profile that addresses management model) there are two types of configuration profiles: a
channel-level provisioning parameters. configuration profile that addresses line-level
provisioningparameters and another profile that addresses channel-
level parameters. The Vector of Profiles (VoP) management model, for
reasons described later on in this document, breaks the set of
configuration parameters into many more profile types, where each
profile type is more homogenous, i.e., it contains parameters that
share a common function (e.g., all the parameters that are required
for provisioning the upstream power backoff feature).
A configuration template is actually a profile-of-profiles. That is, A configuration template in the legacy management model is actually a
a template is comprised of one-line configuration profile and one or profile-of-profiles. It is comprised of a single line configuration
more channel configuration profiles. A template provides the profile and one or more channel configuration profiles. The template
complete configuration of a line. The same configuration can be provides the complete configuration of a line and the same
shared by multiple lines. configuration can be shared by multiple lines if the management
system associates them with the same configuration template.
Similarly, the configuration VoP provides a complete configuration
for a line. However, in the VoP case sharing the same configuration
with multiple lines depends on the specific mode of VoP attachement
method, which is explained in the "Overview of the Vector of Profiles
Management Model" chapter.
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. Note that alarm profiles and
templates are being used also by Network Elements that use the VoP
for configuring the line.
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.9.1. Configuration Profiles and Templates ( Legacy Method ) 2.8.1. Configuration Profiles and Templates ( Legacy Method )
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
skipping to change at page 24, line 34 skipping to change at page 25, line 5
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 indices 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
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.9.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. For example, there are thresholds for failed anomalies. For example, there are thresholds for failed
initializations and LOS seconds, but not for the aggregate number initializations and LOS seconds, but not for the aggregate number
of full initializations. These profiles are defined in the of full initializations. These profiles are defined in the
xdsl2LineAlarmConfProfileTable. xdsl2LineAlarmConfProfileTable.
skipping to change at page 25, line 20 skipping to change at page 25, line 34
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 indices of line-level alarm configuration profile and one to four indices of
channel-level alarm configuration profiles. channel-level alarm configuration profiles.
2.9.3. Managing Profiles and Templates ( Legacy Method ) 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 In the legacy management model one or more lines may be configured to
configuration template (e.g., xdsl2LConfTempTemplateName = 'silver') share parameters of a single configuration template (e.g.,
by setting its xdsl2LineConfTemplate object to the value of this xdsl2LConfTempTemplateName = 'silver') by setting its
template. xdsl2LineConfTemplate object to the value of this template. Sharing
the same configuration with multiple lines in the Vector of Profiles
(VoP) model depends on the specific mode of VoP attachement method,
which is explained in the "Overview of the Vector of Profiles
Management Model" chapter.
One or more lines may be configured to share parameters of a single In both legacy management model and VoP model one or more lines may
Alarm configuration template (e.g., xdsl2LAlarmConfTempTemplateName = be configured to share parameters of a single alarm configuration
'silver') by setting its xdsl2LineAlarmConfTemplate object to the template (e.g., xdsl2LAlarmConfTempTemplateName = 'silver') by
value of this template. setting its xdsl2LineAlarmConfTemplate object to the value of this
template.
Before a template can be deleted or taken out of service, it MUST be In any case, before a template can be deleted or taken out of
first unreferenced from all associated lines. Implementations MAY service, it MUST be first unreferenced from all associated lines.
also reject template modification while it is associated with any Implementations MAY also reject template modification while it is
line. associated with any line.
Before a profile can be deleted or taken out of service, it MUST be Similarly, before a profile can be deleted or taken out of service,
first unreferenced from all associated templates. Implementations it MUST be first unreferenced from all associated templates.
MAY also reject profile modification while it is referenced by any Implementations MAY also reject profile modification while it is
template. referenced by any template.
Implementations MUST provide a default profile whose name is 'DEFVAL' Implementations MUST provide a default profile whose name is 'DEFVAL'
for each profile and template type. The values of the associated for each profile and template type. The values of the associated
parameters will be vendor-specific unless otherwise indicated in this parameters will be vendor-specific unless otherwise indicated in this
document. Before a line's templates have been set, these templates document. Before a line's templates have been set, these templates
will be automatically used by setting xdsl2LineConfTemplate and will be automatically used by setting xdsl2LineConfTemplate and
xdsl2LineAlarmConfTemplate to 'DEFVAL' where appropriate. This xdsl2LineAlarmConfTemplate to 'DEFVAL' where appropriate. This
default profile name, 'DEFVAL', is considered reserved in the context default profile name, 'DEFVAL', is considered reserved in the context
of profiles and templates defined in this MIB module. of profiles and templates defined in this MIB module.
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 optionally implement a fallback line Network Elements MAY optionally implement a fallback line
configuration template (see xdsl2LineConfFallbackTemplate). The configuration template (see xdsl2LineConfFallbackTemplate) or a
fallback template will be tried if the xDSL2 line fails to operate fallback line configuration Vector of Profiles (VoP), in certain
using the primary template. If the xDSL2 line fails to operate using conditions. The fallback template/VoP will be tried if the xDSL2
the fallback template, then the primary template should be retried. line fails to operate using the primary template/VoP. If the xDSL2
The xTU-C SHOULD continue to alternate between the primary and line fails to operate using the fallback template/VoP, then the
fallback templates until one of them succeeds. primary template should be retried. The xTU-C SHOULD continue to
alternate between the primary and fallback templates/VoPs until one
of them succeeds.
2.9.4. Managing Multiple Bearer Channels ( Legacy Method ) 2.8.4. Managing Multiple Bearer Channels ( Legacy Method [only??] )
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
with one bearer channel, there will be zero rows in channel-related with one bearer channel, there will be zero rows in channel-related
skipping to change at page 27, line 5 skipping to change at page 27, line 25
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 that the xdsl2ChannelStatusTable and xdsl2PMChCurrTable tables for 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. Overview of the Vector of Profiles Management Model
The Vector of Profiles management model provides an alternative to
the legacy template management model. The vector of profile
management model provides a more efficient way to store
configuration. The vector of profiles management model is also more
up to date because it contains configuration data that was defined in
the most recent versions of ITU-T G.997.1.
The template management model is not efficient in the way
configuration data is stored. In the template model, line level
configuration data is stored in a line profile and channel level
configuration data is stored in a channel profile. It is quite
common for two XDSL lines to require almost identical configuration
data but having a slightly different value for one or two parameters.
The template model will require two profiles to satisfy the
requirements of the two XDSL lines and hence a large amount of data
is duplicated in the two profiles. The Vector of Profiles management
model attempts to solve this problem of duplicated data by splitting
the large line profile and large channel profiles into many smaller
profiles.
The vector that is defined in the Vector of Profiles management model
is a management object that contains only pointers. The vector
contains pointers to the smaller profile objects mentioned in the
paragraph above. There are two methods that can be used to associate
a vector with a XDSL line, the methods are called direct attachment
method and indirect attachment method.
2.9.1. The Direct Attachment Method
For the direct attachment method, one vector object is automatically
created for each XDSL line. The SNMP agent creates the vector
objects and hence the SNMP manager is not permitted to write to the
Row Status attribute of the vector object.
Each XDSL line is associated with one vector object because the
vector object will have the same index as the XDSL line.
2.9.2. The Indirect Attachment Method
For the indirect attachment method, the SNMP manager is responsible
for creating and deleting the vector objects using the Row Status
attribute. The SNMP manager then uses the xdsl2VopLineVectorId
attribute to associate a XDSL line with a vector object.
Initially, the SNMP agent will create one single vector object (
called the default vector and having an index of 1 ) and all XDSL
lines will refer to this vector. The default vector cannot be
deleted.
2.10. Notifications 2.10. 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 events occur. The corresponding linkUp anomaly, LOS, LOF, or UAS events occur. The corresponding linkUp
skipping to change at page 28, line 21 skipping to change at page 29, line 46
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 "201306250000Z" -- June 25, 2013 LAST-UPDATED "201308010000Z" -- August 1, 2013
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: Menachem Dodge Chair: Menachem Dodge
ECI Telecom Ltd. ECI Telecom Ltd.
Postal: 30 Hasivim St. Postal: 30 Hasivim St.
Petach Tikva 4959388, Petach Tikva 4959388,
Israel Israel
Email: menachemdodge1@gmail.com Email: menachemdodge1@gmail.com
Phone: +972 52 6448463 Phone: +972 52 6448463
Co-editor: Moti Morgenstern Co-editor: Moti Morgenstern
ECI Telecom Ltd. ECI Telecom Ltd.
skipping to change at page 30, line 4 skipping to change at page 31, line 29
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This version of this MIB module is part of RFC XXXX; This version of this MIB module is part of RFC XXXX;
see the RFC itself for full legal notices." see the RFC itself for full legal notices."
-- RFC Ed.: replace XXXX with assigned RFC number everywhere -- RFC Ed.: replace XXXX with assigned RFC number everywhere
-- : it appears in this document & remove this note -- : it appears in this document & remove this note
REVISION "201306250000Z" -- June 25, 2013 REVISION "201308010000Z" -- August 1, 2013
DESCRIPTION "Initial version, published as RFC XXXX." DESCRIPTION "Initial version, published as RFC XXXX."
::= { transmission 251 3} -- vdsl2MIB 3 ::= { transmission 251 3} -- vdsl2MIB 3
------------------------------------------------ ------------------------------------------------
-- Textual Conventions -- -- Textual Conventions --
------------------------------------------------ ------------------------------------------------
Xdsl2VopAttachmentMethods ::= TEXTUAL-CONVENTION Xdsl2VopAttachmentMethods ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 30, line 48 skipping to change at page 32, line 25
direct(0), direct(0),
indirect(1) indirect(1)
} }
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
also called atuc and atur. are 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.
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
skipping to change at page 31, line 19 skipping to change at page 32, line 43
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
direction is a transmission from the xTU-C towards the xTU-R. downstream 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
of us0(3), us1(5), us2(7), us3(9), or us4(11), and a band in any of us0(3), us1(5), us2(7), us3(9), or us4(11), and a band
the downstream direction is indicated by any of ds1(4), in the downstream direction is indicated by any of ds1(4),
ds2(6), 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
when there is a need to refer to the whole upstream or used 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
-- (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
skipping to change at page 38, line 42 skipping to change at page 40, line 19
} }
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),
l1(2), l1(2),
l2(3), l2(3),
l3(4) l3(4)
} }
Xdsl2ConfPmsForce ::= TEXTUAL-CONVENTION Xdsl2ConfPmsForce ::= TEXTUAL-CONVENTION
skipping to change at page 47, line 51 skipping to change at page 49, line 28
reserved12(31) reserved12(31)
} }
Xdsl2SymbolProtection ::= TEXTUAL-CONVENTION Xdsl2SymbolProtection ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This type specifies the minimum impulse noise protection "This type specifies the minimum impulse noise protection
for the bearer channel if it is transported over DMT symbols for the bearer channel if it is transported over DMT symbols
with a subcarrier spacing of 4.3125 kHz. with a subcarrier spacing of 4.3125 kHz.
The possible values are: The possible values are:
'noProtection' (i.e., INP not required), 'halfSymbol' (i.e., INP 'noProtection' (i.e., INP not required), 'halfSymbol' (i.e.,
length is 1/2 symbol), and 1-16 symbols in steps of 1 INP length is 1/2 symbol), and 1-16 symbols in steps of 1
symbol." symbol."
SYNTAX INTEGER { SYNTAX INTEGER {
noProtection(1), noProtection(1),
halfSymbol(2), halfSymbol(2),
singleSymbol(3), singleSymbol(3),
twoSymbols(4), twoSymbols(4),
threeSymbols(5), threeSymbols(5),
fourSymbols(6), fourSymbols(6),
fiveSymbols(7), fiveSymbols(7),
skipping to change at page 50, line 15 skipping to change at page 51, line 39
direction. A bit value of one indicates that a subcarrier direction. A bit value of one indicates that a subcarrier
is masked." is masked."
SYNTAX OCTET STRING (SIZE(0..8)) SYNTAX OCTET STRING (SIZE(0..8))
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
a 16-bit stop subcarrier index. by a 16-bit stop subcarrier index.
The 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))
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.
skipping to change at page 50, line 41 skipping to change at page 52, line 17
The 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
breakpoint. The third octet holds the PSD reduction at the the breakpoint. The third octet holds the PSD at the
breakpoint from 0 (0 dBm/Hz) to 255 (-127.5 dBm/Hz) using units breakpoint with valid values from 0 (0 dBm/Hz) to 190
of 0.5 dBm/Hz. (-95 dBm/Hz) using units of 0.5 dBm/Hz.
The 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." NSds."
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
index of the subcarrier associated with the breakpoint. The the index of the subcarrier associated with the breakpoint.
third octet holds the PSD reduction at the breakpoint from 0 The third octet holds the PSD at the breakpoint with valid
(0 dBm/Hz) to 255 (-127.5 dBm/Hz) using units of values from 0 (0 dBm/Hz) to 190 (-95 dBm/Hz) using units of
0.5 dBm/Hz. 0.5 dBm/Hz.
The 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." NSus."
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
following structure: the 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
the breakpoint. of 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.5 dB). The special value 127 indicates that the subcarrier is -0.5 dB). The special value 127 indicates that the subcarrier
not transmitted. is not transmitted.
The 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
skipping to change at page 55, line 4 skipping to change at page 56, line 29
according to the INP_no_erasure formula (9.6/G.993.2). 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 the Transmission Convergence (TC) reflect the failure status for the Transmission Convergence
layer of a given ATM interface (data path over a VDSL2/ADSL/ (TC) layer of a given ATM interface (data path over a VDSL2/
ADSL2 or ADSL2+ link). 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 reports that no defect or failure
exists. 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
associated ATM data path. associated ATM data path.
lossOfCellDelineation (2)- Loss of cell delineation on the lossOfCellDelineation (2)- Loss of cell delineation on the
skipping to change at page 55, line 39 skipping to change at page 57, line 15
} }
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
reports that no defect or failure exists. 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).
skipping to change at page 57, line 18 skipping to change at page 58, line 42
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
cyclic extension values may be used. Otherwise, the cyclic optional cyclic extension values may be used. Otherwise,
extension shall be forced to the mandatory length (5N/32). the cyclic extension shall be forced to the mandatory
length (5N/32).
enableCyclicExtension (0) - Enable use of optional enableCyclicExtension (0) - Enable use of optional
Cyclic Extension values." Cyclic Extension values."
SYNTAX BITS { SYNTAX BITS {
enableCyclicExtension(0) enableCyclicExtension(0)
} }
Xdsl2LineSnrMode ::= TEXTUAL-CONVENTION Xdsl2LineSnrMode ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 57, line 48 skipping to change at page 59, line 25
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
index of the subcarrier associated with the breakpoint. The the index of the subcarrier associated with the breakpoint.
third octet holds the PSD reduction at the breakpoint from 0 The third octet holds the PSD reduction at the breakpoint
(-40 dBm/Hz) to 200 (-140 dBm/Hz) using units of 0.5 dBm/Hz. from 0 (-40 dBm/Hz) to 200 (-140 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.
The 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
index of the subcarrier associated with the breakpoint. The the index of the subcarrier associated with the breakpoint.
third octet holds the PSD reduction at the breakpoint from 0 The third octet holds the PSD reduction at the breakpoint
(-40 dBm/Hz) to 200 (-140 dBm/Hz) using units of 0.5 dBm/Hz. from 0 (-40 dBm/Hz) to 200 (-140 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.
The 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))
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.
skipping to change at page 58, line 52 skipping to change at page 60, line 29
Octets 0-1 -\u002D Index of the first subcarrier used in the Octets 0-1 -\u002D Index of the first subcarrier used in the
context of a first breakpoint. context of a first breakpoint.
Octets 2-3 -\u002D The PSD level for the subcarrier indicated Octets 2-3 -\u002D The PSD level for the subcarrier indicated
in octets 0-1. in octets 0-1.
Octets 4-7 -\u002D Same, for a second breakpoint Octets 4-7 -\u002D Same, for a second breakpoint
Octets 8-11 -\u002D Same, for a third breakpoint Octets 8-11 -\u002D Same, for a third breakpoint
And so on until And so on until
Octets 188-191 -\u002D Same, for a 48th breakpoint. Octets 188-191 -\u002D Same, for a 48th breakpoint.
The subcarrier index is an unsigned number in the range 0 The subcarrier index is an unsigned number in the range 0
to NSCds-1. to NSCds-1.
The PSD level is an integer value in the 0 to 4095 range. It is The PSD level is an integer value in the 0 to 4095 range.
represented in units of 0.1 dB offset from -140 dBm/Hz." 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
skipping to change at page 59, line 26 skipping to change at page 61, line 5
Octets 0-1 -\u002D Index of the first subcarrier used in the Octets 0-1 -\u002D Index of the first subcarrier used in the
context of a first breakpoint. context of a first breakpoint.
Octets 2-3 -\u002D The PSD level for the subcarrier indicated Octets 2-3 -\u002D The PSD level for the subcarrier indicated
in octets 0-1. in octets 0-1.
Octets 4-7 -\u002D Same, for a second breakpoint Octets 4-7 -\u002D Same, for a second breakpoint
Octets 8-11 -\u002D Same, for a third breakpoint Octets 8-11 -\u002D Same, for a third breakpoint
And so on until And so on until
Octets 124-127 -\u002D Same, for a 32nd breakpoint. Octets 124-127 -\u002D Same, for a 32nd breakpoint.
The subcarrier index is an unsigned number in the range 0 The subcarrier index is an unsigned number in the range 0
to NSCus-1. to NSCus-1.
The PSD level is an integer value in the 0 to 4095 range. It is The PSD level is an integer value in the 0 to 4095 range. It
represented in units of 0.1 dB offset from -140 dBm/Hz." 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))
Xdsl2RtxModes ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Objects with this syntax are configuration parameters
that select the mode of ITU-T G.998.4 (retransmission) to be
used in either upstream or downstream transmit-direction.
The possible retransmission modes are:
forbidden (1) - G.998.4 retransmission is not allowed.
preferred (2) - G.998.4 retransmission is preferred
by the operator. I.e. if both xTUs
support it then they shall employ it on
the relevant transmit direction
forced (3) - G.998.4 retransmission shall be used.
I.e. if any xTU does not support it
or if the xTUs in practice did not
select it, then initialization
shall fail.
testMode (4) - The G.998.4 retransmission shall be
used in test-mode."
SYNTAX INTEGER {
forbidden (1),
preferred (2),
forced (3),
testMode (4)
}
END END
VDSL2-LINE-MIB DEFINITIONS ::= BEGIN VDSL2-LINE-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
OBJECT-TYPE, OBJECT-TYPE,
transmission, transmission,
Unsigned32, Unsigned32,
NOTIFICATION-TYPE, NOTIFICATION-TYPE,
skipping to change at page 61, line 18 skipping to change at page 63, line 22
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 "201306250000Z" -- June 25, 2013 LAST-UPDATED "201308010000Z" -- August 1, 2013
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: Menachem Dodge Chair: Menachem Dodge
ECI Telecom Ltd. ECI Telecom Ltd.
Postal: 30 Hasivim St. Postal: 30 Hasivim St.
Petach Tikva 4959388, Petach Tikva 4959388,
Israel Israel
Email: menachemdodge1@gmail.com Email: menachemdodge1@gmail.com
skipping to change at page 62, line 21 skipping to change at page 64, line 26
objects used for managing Asymmetric Bit-Rate DSL (ADSL) objects used for managing Asymmetric Bit-Rate DSL (ADSL)
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].
is also capable of managing ADSL interfaces per [T1E1.413], That MIB is also capable of managing ADSL interfaces per
[G.992.1], and [G.992.2]. [T1E1.413], [G.992.1], and [G.992.2].
This document does not obsolete RFC 2662 [RFC2662] or 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 the ITU-T G.997.1 standard [G.997.1] and framework is based on the ITU-T G.997.1 standard [G.997.1]
its amendment 1 [G.997.1-Am1]. and 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
[RFC2863]) section of this document. (RFC 2863 [RFC2863]) section of this document.
Copyright (c) 2009 IETF Trust and the persons identified Copyright (c) 2009 IETF Trust and the persons identified
as authors of the code. All rights reserved. as authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with Redistribution and use in source and binary forms, with
or without modification, are permitted provided that the or without modification, are permitted provided that the
following conditions are met: following conditions are met:
- Redistributions of source code must retain the above - Redistributions of source code must retain the above
copyright notice, this list of conditions and the copyright notice, this list of conditions and the
skipping to change at page 63, line 34 skipping to change at page 65, line 38
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This version of this MIB module is part of RFC XXXX; This version of this MIB module is part of RFC XXXX;
see the RFC itself for full legal notices." see the RFC itself for full legal notices."
REVISION "201306250000Z" -- June 25, 2013 REVISION "201308010000Z" -- August 1, 2013
DESCRIPTION "Initial version, published as RFC XXXX." DESCRIPTION "Initial version, published as RFC XXXX."
::= { transmission 251 } ::= { 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 }
skipping to change at page 64, line 28 skipping to change at page 66, line 32
-- 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
manner." persistent 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(251)." interface has an ifType of vdsl2(251)."
INDEX { ifIndex } INDEX { ifIndex }
skipping to change at page 66, line 21 skipping to change at page 68, line 26
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 fall back to a template with a For example, a xDSL2 line may fall back to a template with a
lower rate if the rate specified in the primary template lower rate if the rate specified in the primary template
cannot be 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
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
fall-back template. a fall-back template.
If the xDSL2 line fails to operate using the fall-back template, If the xDSL2 line fails to operate using the fall-back
then the primary template should be retried. 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
fall-back 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
fall-back template is defined and only the primary template will fall-back template is defined and only the primary template
be used. will 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.
NOTE : This object belongs only to the legacy management model NOTE : This object belongs only to the legacy management model
: that was originally specified in RFC 5650. : that was originally specified in RFC 5650.
This object MUST be maintained in a persistent manner." This object MUST be maintained in a persistent manner."
::= { xdsl2LineEntry 2 } ::= { xdsl2LineEntry 2 }
skipping to change at page 67, line 32 skipping to change at page 69, line 36
SYNTAX Xdsl2LineLdsf SYNTAX Xdsl2LineLdsf
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Loop diagnostic state 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 diagnostic 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'
'l3' state and the xdsl2LineCmndConfPmsf object is in the 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
mode procedures. Upon successful completion of the loop diagnostic mode procedures. Upon successful completion of the
diagnostic mode procedures, the Access Node shall set this loop diagnostic mode procedures, the Access Node shall set
object to 'inhibit', and xdsl2LineStatusPwrMngState will this 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
procedure 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
skipping to change at page 68, line 26 skipping to change at page 70, line 31
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. "Request a bits-per-subcarrier measurement to be made.
A request for a bits-per-subcarrier measurement is made by A request for a bits-per-subcarrier measurement is made by
setting this object to the value of 'measure'. Upon 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
this object to 'idle'. set 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-
measurement already running, and respond with an SNMP error subcarrier measurement already running, and respond with an
(e.g., wrongValue) otherwise. SNMP error (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.
additional mechanism is provided so that bits-per-subcarrier This additional mechanism is provided so that bits-per-
data may be fetched without forcing the line into no power state. subcarrier data may be fetched without forcing the line into
This is useful because the bits-per-subcarrier allocation may be no power state.
adjusted at show time due to rate adaption and bit swapping. This is useful because the bits-per-subcarrier allocation
may be 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
xdsl2LineSegmentTable. The status of the bits-per-subcarrier in xdsl2LineSegmentTable. The status of the bits-per-
measurement is indicated by subcarrier 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
skipping to change at page 69, line 22 skipping to change at page 71, line 29
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 bits-per-subcarrier measurement is made. A measurement
is made by modifying the xdsl2LineCmndConfBpsc object from request is made by modifying the xdsl2LineCmndConfBpsc object
idle(1) to the value measure(2). 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.
An 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.
skipping to change at page 70, line 13 skipping to change at page 72, line 20
::= { 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' to indicate a change Change the value of this parameter to 'true' to indicate a
in loop conditions applied to the devices under the test. The change in loop conditions applied to the devices under the
xTUs shall reset any historical information used for automode test. The xTUs shall reset any historical information used
and for shortening G.994.1 handshake and initialization. for automode 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
through the xdsl2LConfProfXtuTransSysEna object in the line enabled through the xdsl2LConfProfXtuTransSysEna object in the
configuration profile being used for the line, and where the line configuration profile being used for the line, and where
selection of the actual operation-mode depends not only on the the selection of the actual operation-mode depends not only on
common capabilities of both xTUs (as exchanged in G.994.1), but the common capabilities of both xTUs (as exchanged in
also on achievable data rates under given loop conditions." G.994.1), but 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
skipping to change at page 71, line 27 skipping to change at page 73, line 36
::= { 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 bitmap representation with one bit set to 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
in Recommendation G.994.1. A set of xDSL line transmission defined in Recommendation G.994.1. A set of xDSL line
modes, with one bit per mode." transmission 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
SYNTAX Xdsl2PowerMngState SYNTAX Xdsl2PowerMngState
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 72, line 29 skipping to change at page 74, line 39
(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
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
the line." on 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
skipping to change at page 73, line 46 skipping to change at page 76, line 7
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 Spectral 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
It ranges from -900 to 0 units of 0.1 dBm/Hz (physical values are downstream. It ranges from -900 to 0 units of 0.1 dBm/Hz
-90 to 0 dBm/Hz). (physical values are -90 to 0 dBm/Hz).
A value of 0x7FFFFFFF (2147483647) indicates the measurement is A value of 0x7FFFFFFF (2147483647) indicates the measurement
out of range to be represented." is out of range to be represented."
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.21 (ACTPSDds)" REFERENCE "ITU-T G.997.1, paragraph #7.5.1.21 (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 Spectral 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
-90 to 0 dBm/Hz). are -90 to 0 dBm/Hz).
A value of 0x7FFFFFFF (2147483647) indicates the measurement is A value of 0x7FFFFFFF (2147483647) indicates the measurement
out of range to be represented." is out of range to be represented."
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.22 (ACTPSDus)" REFERENCE "ITU-T G.997.1, paragraph #7.5.1.22 (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"
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
to 31 dBm). -31 to 31 dBm).
A value of 0x7FFFFFFF (2147483647) indicates the measurement is A value of 0x7FFFFFFF (2147483647) indicates the measurement
out of range to be represented." is out of range to be represented."
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.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
U-R reference point, at the instant of measurement. It ranges the U-R reference point, at the instant of measurement. It
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
to 31 dBm). -31 to 31 dBm).
A value of 0x7FFFFFFF (2147483647) indicates the measurement is A value of 0x7FFFFFFF (2147483647) indicates the measurement
out of range to be represented." is out of range to be represented."
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.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.
skipping to change at page 76, line 43 skipping to change at page 78, line 51
::= { 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
electrical length was not forced by the CO-MIB. the 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
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 78, line 27 skipping to change at page 80, line 37
DEFVAL { false } DEFVAL { false }
::= { xdsl2LineEntry 37 } ::= { xdsl2LineEntry 37 }
xdsl2LineStatusActualCe OBJECT-TYPE xdsl2LineStatusActualCe OBJECT-TYPE
SYNTAX Unsigned32 (2..16) SYNTAX Unsigned32 (2..16)
UNITS "N/32 samples" UNITS "N/32 samples"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"(ACTUALCE) "(ACTUALCE)
This parameter reports the cyclic extension used on the line. It This parameter reports the cyclic extension used on the line.
is coded as an unsigned integer from 2 to 16 in units of N/32 It is coded as an unsigned integer from 2 to 16 in units of
samples, where 2N is the Inverse Discrete Fourier Transform N/32 samples, where 2N is the Inverse Discrete Fourier
(IDFT) size." Transform (IDFT) size."
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.32 (ACTUALCE)" REFERENCE "ITU-T G.997.1, paragraph #7.5.1.32 (ACTUALCE)"
DEFVAL { 2 } DEFVAL { 2 }
::= { xdsl2LineEntry 38 } ::= { xdsl2LineEntry 38 }
------------------------------------------------ ------------------------------------------------
-- xdsl2VopLineTable -- -- xdsl2VopLineTable --
------------------------------------------------ ------------------------------------------------
xdsl2VopLineTable OBJECT-TYPE xdsl2VopLineTable OBJECT-TYPE
SYNTAX SEQUENCE OF Xdsl2VopLineEntry SYNTAX SEQUENCE OF Xdsl2VopLineEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
skipping to change at page 79, line 30 skipping to change at page 81, line 38
} }
xdsl2VopLineVectorId OBJECT-TYPE xdsl2VopLineVectorId OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-write MAX-ACCESS read-write
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
xdsl2VopVectorTable that applies for this line. xdsl2VopVectorTable that applies for this line.
Supporting this object is mandatory when the VoP
attachment method is indirect. in case of direct attachment
the row in xdsl2VopVectorTable which applies to this line
has the same (ifIndex) index.
This object MUST be maintained in a persistent manner." This object MUST be maintained in a persistent manner."
DEFVAL { 1 } DEFVAL { 1 }
::= { xdsl2VopLineEntry 1 } ::= { xdsl2VopLineEntry 1 }
xdsl2VopLineFallbackVectorId OBJECT-TYPE xdsl2VopLineFallbackVectorId OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"" ""
skipping to change at page 80, line 8 skipping to change at page 82, line 22
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.
additional mechanism is provided so that bits-per-subcarrier This additional mechanism is provided so that bits-per-
data may be fetched without forcing the line into no power state. subcarrier data may be fetched without forcing the line into
This is useful because the bits-per-subcarrier allocation may be no power state.
adjusted at Showtime due to rate adaption and bit swapping. This is useful because the bits-per-subcarrier allocation may
be 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
to the selected implementation profile. For ADSL, NSus is equal according to the selected implementation profile. For ADSL,
to NSCus-1 and NSds is equal to NSCds-1. NSus is equal to NSCus-1 and NSds is equal to NSCds-1.
One index of this table is an interface index where the interface One index of this table is an interface index where the
has an ifType of vdsl2(251). A second index of this table is the interface has an ifType of vdsl2(251). A second index of this
transmission direction. A third index identifies the specific table is the transmission direction. A third index identifies
segment of the subcarriers status addressed." the specific segment of the subcarriers status addressed."
INDEX { ifIndex, INDEX { ifIndex,
xdsl2LineSegmentDirection, xdsl2LineSegmentDirection,
xdsl2LineSegment } xdsl2LineSegment }
::= { xdsl2LineSegmentTable 1 } ::= { xdsl2LineSegmentTable 1 }
Xdsl2LineSegmentEntry ::= Xdsl2LineSegmentEntry ::=
SEQUENCE { SEQUENCE {
xdsl2LineSegmentDirection Xdsl2Direction, xdsl2LineSegmentDirection Xdsl2Direction,
xdsl2LineSegment Unsigned32, xdsl2LineSegment Unsigned32,
xdsl2LineSegmentBitsAlloc Xdsl2BitsAlloc, xdsl2LineSegmentBitsAlloc Xdsl2BitsAlloc,
skipping to change at page 81, line 22 skipping to change at page 83, line 37
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)
respond with a zero-length OCTET STRING." will respond with a zero-length OCTET STRING."
::= { xdsl2LineSegmentEntry 2 } ::= { xdsl2LineSegmentEntry 2 }
xdsl2LineSegmentBitsAlloc OBJECT-TYPE xdsl2LineSegmentBitsAlloc OBJECT-TYPE
SYNTAX Xdsl2BitsAlloc SYNTAX Xdsl2BitsAlloc
UNITS "bits" UNITS "bits"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The bits allocation per 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)
skipping to change at page 82, line 14 skipping to change at page 84, line 29
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
set the row status to 'notInService'. In the first case, or set the row status to 'notInService'. In the first
if the SNMP manager tries to create a new row, the SNMP agent case, if the SNMP manager tries to create a new row, the SNMP
responds with the value 'noCreation' in the error status agent responds with the value 'noCreation' in the error
field of the response-PDU. In the latter case, the SNMP agent status field of the response-PDU. In the latter case, the SNMP
responds with the value 'wrongValue' in the error status agent responds with the value 'wrongValue' in the error
field of the response-PDU. status field of the response-PDU.
The SNMP agent may have limited resources; therefore, if multiple The SNMP agent may have limited resources; therefore, if
rows coexist in this table, it may fail to add new rows to this multiple rows coexist in this table, it may fail to add new
table or allocate memory resources. rows to this 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. For example, after retrieving table according to any scheme. For example, after retrieving
the results. the results.
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
skipping to change at page 82, line 48 skipping to change at page 85, line 15
------------------------------------------------ ------------------------------------------------
-- 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 initialization The parameters in this table are updated at line
time and at Showtime." initialization 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(251). A second index of this table is a has an ifType of vdsl2(251). A second index of this table is
per-band index covering both VDSL2 and ADSL/ADSL2/ADSL2+." a 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
} }
skipping to change at page 83, line 51 skipping to change at page 86, line 18
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Line Attenuation. "Line Attenuation.
When referring to a band in the downstream direction, it is When referring to a band in the downstream direction, it is
the measured difference in the total power transmitted by the the measured difference in the total power transmitted by the
xTU-C and the total power received by the xTU-R over all 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
and the total power received by the xTU-C over all subcarriers of xTU-R and the total power received by the xTU-C over all
that band during initialization. subcarriers of 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
are 0 to 127 dB). values are 0 to 127 dB).
A special value of 0x7FFFFFFF (2147483647) indicates the line A special value of 0x7FFFFFFF (2147483647) indicates the line
attenuation is out of range to be represented. attenuation is out of range to be represented.
A special value of 0x7FFFFFFE (2147483646) indicates the line A special value of 0x7FFFFFFE (2147483646) indicates the line
attenuation measurement is unavailable." attenuation measurement is unavailable."
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.9 (LATNds) REFERENCE "ITU-T G.997.1, paragraph #7.5.1.9 (LATNds)
and paragraph #7.5.1.10 (LATNus)6" and paragraph #7.5.1.10 (LATNus)6"
DEFVAL { 2147483646 } DEFVAL { 2147483646 }
::= { xdsl2LineBandEntry 2 } ::= { xdsl2LineBandEntry 2 }
xdsl2LineBandStatusSigAtten OBJECT-TYPE xdsl2LineBandStatusSigAtten OBJECT-TYPE
skipping to change at page 84, line 31 skipping to change at page 86, line 46
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
measured difference in the total power transmitted by the xTU-R measured difference in the total power transmitted by the
and the total power received by the xTU-C over all subcarriers of xTU-R and the total power received by the xTU-C over all
that band during Showtime. subcarriers of 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
are 0 to 127 dB). values 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
and xTU-C for a band in the upstream direction), such that the direction and xTU-C for a band in the upstream direction),
BER requirements are met for all bearer channels received at the such that the BER requirements are met for all bearer channels
xTU. Values range from -640 to 630 in units of 0.1 dB (physical received at the xTU. Values range from -640 to 630 in units
values are -64 to 63 dB). of 0.1 dB (physical 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 }
skipping to change at page 87, line 16 skipping to change at page 89, line 30
::= { xdsl2ChannelStatusEntry 3 } ::= { xdsl2ChannelStatusEntry 3 }
xdsl2ChStatusActDelay OBJECT-TYPE xdsl2ChStatusActDelay OBJECT-TYPE
SYNTAX Unsigned32(0..8176) SYNTAX Unsigned32(0..8176)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The actual one-way interleaving delay introduced by the "The actual one-way interleaving delay introduced by the
PMS-TC in the direction of the bearer channel, if in L0 power PMS-TC in the direction of the bearer channel, if in L0 power
management state. In L1 or L2 states, it relates to the previous management state. In L1 or L2 states, it relates to the
L0 state. It is coded in ms (rounded to the nearest ms)." previous L0 state. It is coded in ms (rounded to the nearest
ms)."
REFERENCE "ITU-T G.997.1, paragraph #7.5.2.3 REFERENCE "ITU-T G.997.1, paragraph #7.5.2.3
(Actual interleaving delay)" (Actual interleaving delay)"
DEFVAL { 0 } DEFVAL { 0 }
::= { xdsl2ChannelStatusEntry 4 } ::= { xdsl2ChannelStatusEntry 4 }
xdsl2ChStatusActInp OBJECT-TYPE xdsl2ChStatusActInp OBJECT-TYPE
SYNTAX Unsigned32(0..255) SYNTAX Unsigned32(0..255)
UNITS "0.1 symbols" UNITS "0.1 symbols"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"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
on the bearer channel in the L0 state. In the L1 or L2 state, (INP) on the bearer channel in the L0 state. In the L1 or L2
the parameter contains the INP in the previous L0 state. For state, the parameter contains the INP in the previous L0 state.
ADSL, this value is computed according to the formula specified For ADSL, this value is computed according to the formula
in the relevant Recommendation based on the actual framing specified in the relevant Recommendation based on the actual
parameters. For ITU-T Recommendation G.993.2, the method to framing parameters. For ITU-T Recommendation G.993.2, the
report this value is according to the INPREPORT parameter. method to report this value is according to the INPREPORT
parameter.
The value is coded in fractions of DMT symbols with a The value is coded in fractions of DMT symbols with a
granularity of 0.1 symbols. The range is from 0 to 25.4. granularity of 0.1 symbols. The range is from 0 to 25.4.
The special value of 255 indicates an ACTINP higher The special value of 255 indicates an ACTINP higher
than 25.4." 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
skipping to change at page 88, line 16 skipping to change at page 90, line 32
::= { xdsl2ChannelStatusEntry 6 } ::= { xdsl2ChannelStatusEntry 6 }
xdsl2ChStatusNFec OBJECT-TYPE xdsl2ChStatusNFec OBJECT-TYPE
SYNTAX Unsigned32(0..255) SYNTAX Unsigned32(0..255)
UNITS "bytes" UNITS "bytes"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"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
the bearer channel is transported. The value is coded in bytes. which the bearer channel is transported. The value is
It ranges from 0 to 16. coded in bytes. 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.
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
the bearer channel is transported. The value is coded in bytes. which the bearer channel is transported. The value is
It ranges from 0 to 16. coded in bytes. 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.
value is coded in bits. The value is coded in bits.
It ranges from 0 to 65535." It ranges from 0 to 65535."
REFERENCE "ITU-T G.997.1, paragraph #7.5.2.6.3 (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
in the latency path in which the bearer channel is transported. used 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
used in the latency path in which the bearer channel is interleaver used in the latency path in which the bearer
transported. channel is transported.
The value ranges from 4 to 255 in steps of 1." The value ranges from 4 to 255 in steps of 1."
REFERENCE "ITU-T G.997.1, paragraph #7.5.2.6.5 (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
index 1." latency 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
skipping to change at page 91, line 35 skipping to change at page 94, line 4
diagnostic procedure, MAY be updated after a line diagnostic procedure, MAY be updated after a line
initialization, 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
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 has an ifType of vdsl2(251). A second index of this interface has an ifType of vdsl2(251). A second index of
table is the transmission direction." this table is the 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 92, line 22 skipping to change at page 94, line 39
"The direction of the subcarrier either "The direction of the subcarrier either
upstream or downstream." upstream or downstream."
::= { xdsl2SCStatusEntry 1 } ::= { xdsl2SCStatusEntry 1 }
xdsl2SCStatusLinScale OBJECT-TYPE xdsl2SCStatusLinScale OBJECT-TYPE
SYNTAX Unsigned32 (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
This parameter is only available after a loop diagnostic direction. This parameter is only available after
procedure. It is represented as an unsigned integer in the range a loop diagnostic procedure. It is represented as an
from 1 to 2^16-1." unsigned integer in the range from 1 to 2^16-1."
REFERENCE "ITU-T G.997.1, paragraph #7.5.1.26.1 (HLINSCds) REFERENCE "ITU-T G.997.1, paragraph #7.5.1.26.1 (HLINSCds)
and paragraph #7.5.1.26.7 (HLINSCus)" and paragraph #7.5.1.26.7 (HLINSCus)"
::= { xdsl2SCStatusEntry 2 } ::= { xdsl2SCStatusEntry 2 }
xdsl2SCStatusLinScGroupSize OBJECT-TYPE xdsl2SCStatusLinScGroupSize OBJECT-TYPE
SYNTAX Unsigned32(1 | 2 | 4 | 8) SYNTAX Unsigned32(1 | 2 | 4 | 8)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of 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,
parameter is equal to one and, for VDSL2, it is equal to the size this parameter is equal to one and, for VDSL2, it is equal
of a subcarrier group used to compute these parameters. to the size 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.,
number of symbols in 1 s time interval for ITU-T Recommendation. 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.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)
skipping to change at page 106, line 28 skipping to change at page 108, line 47
"This object reflects the VoP attachment-method(s) this "This object reflects the VoP attachment-method(s) this
Network Element supports. Network Element supports.
Two attachment methods, 'direct' and 'indirect' are available Two attachment methods, 'direct' and 'indirect' are available
and each Network Element MAY be able to support both and each Network Element MAY be able to support both
attachment-methods (but not at the same time). attachment-methods (but not at the same time).
The capability to support a specific attachment-method is The capability to support a specific attachment-method is
indicated by the respective bit-position set to '1'. indicated by the respective bit-position set to '1'.
Particularly, a network element that supports both methods Particularly, a network element that supports both methods
SHOULD indicate that by both bit-positions set to '1'." SHOULD indicate that by both bit-positions set to '1'.
Note that a Network Element that does not support this
object can be managed only with the legacy management mode,
using a line configuration template."
::= { xdsl2ScalarVop 1 } ::= { xdsl2ScalarVop 1 }
xdsl2ScalarVopAttachmentMethodConfigured OBJECT-TYPE xdsl2ScalarVopAttachmentMethodConfigured OBJECT-TYPE
SYNTAX Xdsl2VopAttachmentMethods SYNTAX Xdsl2VopAttachmentMethods
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object configures the VoP attachment-method to be "This object configures the VoP attachment-method to be
used by this Network Element. used by this Network Element.
Two attachment methods, 'direct' and 'indirect' are available Two attachment methods, 'direct' and 'indirect' are available
skipping to change at page 108, line 22 skipping to change at page 110, line 44
"" ""
INDEX { xdsl2VopVectorIndex } INDEX { xdsl2VopVectorIndex }
::= { xdsl2VopVectorTable 1 } ::= { xdsl2VopVectorTable 1 }
Xdsl2VopVectorEntry ::= Xdsl2VopVectorEntry ::=
SEQUENCE { SEQUENCE {
xdsl2VopVectorIndex Unsigned32, xdsl2VopVectorIndex Unsigned32,
xdsl2VopVectorRowStatus RowStatus, xdsl2VopVectorRowStatus RowStatus,
xdsl2VopVectorDescription OCTET STRING, xdsl2VopVectorDescription OCTET STRING,
xdsl2VopVectorUsDataRateProfId1 Unsigned32, xdsl2VopVectorUsDataRateProfId1 Unsigned32,
xdsl2VopVectorUsRaRatio1 Unsigned32,
xdsl2VopVectorDsDataRateProfId1 Unsigned32, xdsl2VopVectorDsDataRateProfId1 Unsigned32,
xdsl2VopVectorDsRaRatio1 Unsigned32,
xdsl2VopVectorInpDelayProfId1 Unsigned32, xdsl2VopVectorInpDelayProfId1 Unsigned32,
xdsl2VopVectorUsDataRateProfId2 Unsigned32, xdsl2VopVectorUsDataRateProfId2 Unsigned32,
xdsl2VopVectorUsRaRatio2 Unsigned32,
xdsl2VopVectorDsDataRateProfId2 Unsigned32, xdsl2VopVectorDsDataRateProfId2 Unsigned32,
xdsl2VopVectorDsRaRatio2 Unsigned32,
xdsl2VopVectorInpDelayProfId2 Unsigned32, xdsl2VopVectorInpDelayProfId2 Unsigned32,
xdsl2VopVectorUsDataRateProfId3 Unsigned32, xdsl2VopVectorUsDataRateProfId3 Unsigned32,
xdsl2VopVectorUsRaRatio3 Unsigned32,
xdsl2VopVectorDsDataRateProfId3 Unsigned32, xdsl2VopVectorDsDataRateProfId3 Unsigned32,
xdsl2VopVectorDsRaRatio3 Unsigned32,
xdsl2VopVectorInpDelayProfId3 Unsigned32, xdsl2VopVectorInpDelayProfId3 Unsigned32,
xdsl2VopVectorUsDataRateProfId4 Unsigned32, xdsl2VopVectorUsDataRateProfId4 Unsigned32,
xdsl2VopVectorUsRaRatio4 Unsigned32,
xdsl2VopVectorDsDataRateProfId4 Unsigned32, xdsl2VopVectorDsDataRateProfId4 Unsigned32,
xdsl2VopVectorDsRaRatio4 Unsigned32,
xdsl2VopVectorInpDelayProfId4 Unsigned32, xdsl2VopVectorInpDelayProfId4 Unsigned32,
xdsl2VopVectorLSpectrumProfId Unsigned32, xdsl2VopVectorLSpectrumProfId Unsigned32,
xdsl2VopVectorNoiseMarginProfId Unsigned32,
xdsl2VopVectorVirtualNoiseProfId Unsigned32,
xdsl2VopVectorUpboProfId Unsigned32, xdsl2VopVectorUpboProfId Unsigned32,
xdsl2VopVectorDpboProfId Unsigned32, xdsl2VopVectorDpboProfId Unsigned32,
xdsl2VopVectorRfiProfId Unsigned32, xdsl2VopVectorRfiProfId Unsigned32,
xdsl2VopVectorNoiseMarginProfId Unsigned32, xdsl2VopVectorSosProfId Unsigned32,
xdsl2VopVectorVNoiseProfId Unsigned32 xdsl2VopVectorInmProfId Unsigned32,
xdsl2VopVectorVectoringProfId Unsigned32,
xdsl2VopVectorReinitProfId Unsigned32
} }
xdsl2VopVectorIndex OBJECT-TYPE xdsl2VopVectorIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"" "The index of this Vector of Profiles (VoP) row.
In case the implementation uses a direct attachment
of VoP to each xDSL line then the value of this object
is an ifIndex pattern and this row is associated with
a respective row in xdsl2VopLineTable (which has the
same index). In such a case all rows in this table are
created automatically by the Network Element and the
SNMP manager is allowed only to activate a row and
modify the values of objects in a row (i.e., this
excludes creating and deleting rows in the table).
In case the implementation uses an indirect
attachment of VoP to xDSL lines then the value of this
object is a unique ordered number and it can be
referenced by multiple rows in the xdsl2VopLineTable. In
such a case all rows are created, modified, activated
and deleted by the SNMP manager."
::= { xdsl2VopVectorEntry 1 } ::= { xdsl2VopVectorEntry 1 }
xdsl2VopVectorRowStatus OBJECT-TYPE xdsl2VopVectorRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"" "The row status of this row.
In case the implementation uses a direct attachment
of VoP to each xDSL line then all rows are created
automatically by the Network Element and the SNMP manager
is allowed only to activate a row and modify the values
of objects in a row (i.e., this excludes creating and
deleting rows in the table).
In case the implementation uses an indirect
attachment of VoP to xDSL lines then rows are created,
modified, activated and deleted by the SNMP manager."
::= { xdsl2VopVectorEntry 2 } ::= { xdsl2VopVectorEntry 2 }
xdsl2VopVectorDescription OBJECT-TYPE xdsl2VopVectorDescription OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (0..128)) SYNTAX OCTET STRING (SIZE (0..128))
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"" "This object serves for optionally attaching a description
to the related Vector of Profiles. "
DEFVAL { "" } DEFVAL { "" }
::= { xdsl2VopVectorEntry 3 } ::= { xdsl2VopVectorEntry 3 }
xdsl2VopVectorUsDataRateProfId1 OBJECT-TYPE xdsl2VopVectorUsDataRateProfId1 OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"" "Upstream data rate configuration profile for bearer channel
number 1 of the xDSL line that is associated with this VoP.
The value of this object is a row index in
xdsl2VopDataRateProfilesTable."
DEFVAL { 1 } DEFVAL { 1 }
::= { xdsl2VopVectorEntry 4 } ::= { xdsl2VopVectorEntry 4 }
xdsl2VopVectorUsRaRatio1 OBJECT-TYPE xdsl2VopVectorDsDataRateProfId1 OBJECT-TYPE
SYNTAX Unsigned32 (0..100) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"" "Downstream data rate configuration profile for bearer channel
DEFVAL { 100 } number 1 of the xDSL line that is associated with this VoP.
The value of this object is a row index in
xdsl2VopDataRateProfilesTable."
DEFVAL { 2 }
::= { xdsl2VopVectorEntry 5 } ::= { xdsl2VopVectorEntry 5 }
xdsl2VopVectorDsDataRateProfId1 OBJECT-TYPE xdsl2VopVectorInpDelayProfId1 OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"" ""
DEFVAL { 2 } DEFVAL { 1 }
::= { xdsl2VopVectorEntry 6 } ::= { xdsl2VopVectorEntry 6 }
xdsl2VopVectorDsRaRatio1 OBJECT-TYPE xdsl2VopVectorUsDataRateProfId2 OBJECT-TYPE
SYNTAX Unsigned32 (0..100) SYNTAX Unsigned32 (0..4294967295)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"" "Upstream data rate configuration profile for bearer channel
DEFVAL { 100 } number 2 of the xDSL line that is associated with this VoP.
The value of this object is a row index in
xdsl2VopDataRateProfilesTable."
DEFVAL { 0 }
::= { xdsl2VopVectorEntry 7 } ::= { xdsl2VopVectorEntry 7 }
xdsl2VopVectorInpDelayProfId1 OBJECT-TYPE xdsl2VopVectorDsDataRateProfId2 OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (0..4294967295)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"" "Downstream data rate configuration profile for bearer channel
DEFVAL { 1 } number 2 of the xDSL line that is associated with this VoP.
The value of this object is a row index in
xdsl2VopDataRateProfilesTable."
DEFVAL { 0 }
::= { xdsl2VopVectorEntry 8 } ::= { xdsl2VopVectorEntry 8 }
xdsl2VopVectorUsDataRateProfId2 OBJECT-TYPE xdsl2VopVectorInpDelayProfId2 OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295) SYNTAX Unsigned32 (0..4294967295)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"" ""
DEFVAL { 0 } DEFVAL { 0 }
::= { xdsl2VopVectorEntry 9 } ::= { xdsl2VopVectorEntry 9 }
xdsl2VopVectorUsRaRatio2 OBJECT-TYPE xdsl2VopVectorUsDataRateProfId3 OBJECT-TYPE
SYNTAX Unsigned32 (0..100) SYNTAX Unsigned32 (0..4294967295)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"" "Upstream data rate configuration profile for bearer channel
number 3 of the xDSL line that is associated with this VoP.
The value of this object is a row index in
xdsl2VopDataRateProfilesTable."
DEFVAL { 0 } DEFVAL { 0 }
::= { xdsl2VopVectorEntry 10 } ::= { xdsl2VopVectorEntry 10 }
xdsl2VopVectorDsDataRateProfId2 OBJECT-TYPE xdsl2VopVectorDsDataRateProfId3 OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295) SYNTAX Unsigned32 (0..4294967295)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"" "Downstream data rate configuration profile for bearer channel
number 3 of the xDSL line that is associated with this VoP.
The value of this object is a row index in
xdsl2VopDataRateProfilesTable."
DEFVAL { 0 } DEFVAL { 0 }
::= { xdsl2VopVectorEntry 11 } ::= { xdsl2VopVectorEntry 11 }
xdsl2VopVectorDsRaRatio2 OBJECT-TYPE xdsl2VopVectorInpDelayProfId3 OBJECT-TYPE
SYNTAX Unsigned32 (0..100) SYNTAX Unsigned32 (0..4294967295)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"" ""
DEFVAL { 0 } DEFVAL { 0 }
::= { xdsl2VopVectorEntry 12 } ::= { xdsl2VopVectorEntry 12 }
xdsl2VopVectorInpDelayProfId2 OBJECT-TYPE xdsl2VopVectorUsDataRateProfId4 OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295) SYNTAX Unsigned32 (0..4294967295)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"" "Upstream data rate configuration profile for bearer channel
number 4 of the xDSL line that is associated with this VoP.
The value of this object is a row index in
xdsl2VopDataRateProfilesTable."
DEFVAL { 0 } DEFVAL { 0 }
::= { xdsl2VopVectorEntry 13 } ::= { xdsl2VopVectorEntry 13 }
xdsl2VopVectorUsDataRateProfId3 OBJECT-TYPE xdsl2VopVectorDsDataRateProfId4 OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295) SYNTAX Unsigned32 (0..4294967295)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"" "Downstream data rate configuration profile for bearer channel
number 4 of the xDSL line that is associated with this VoP.
The value of this object is a row index in
xdsl2VopDataRateProfilesTable."
DEFVAL { 0 } DEFVAL { 0 }
::= { xdsl2VopVectorEntry 14 } ::= { xdsl2VopVectorEntry 14 }
xdsl2VopVectorUsRaRatio3 OBJECT-TYPE xdsl2VopVectorInpDelayProfId4 OBJECT-TYPE
SYNTAX Unsigned32 (0..100) SYNTAX Unsigned32 (0..4294967295)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"" ""
DEFVAL { 0 } DEFVAL { 0 }
::= { xdsl2VopVectorEntry 15 } ::= { xdsl2VopVectorEntry 15 }
xdsl2VopVectorDsDataRateProfId3 OBJECT-TYPE xdsl2VopVectorLSpectrumProfId OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"" "Line Spectrum configuration profile for the xDSL line that
DEFVAL { 0 } is associated with this VoP.
The value of this object is a row index in
xdsl2VopLSpectrumProfilesTable."
DEFVAL { 1 }
::= { xdsl2VopVectorEntry 16 } ::= { xdsl2VopVectorEntry 16 }
xdsl2VopVectorDsRaRatio3 OBJECT-TYPE xdsl2VopVectorNoiseMarginProfId OBJECT-TYPE
SYNTAX Unsigned32 (0..100) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"" ""
DEFVAL { 1 }
DEFVAL { 0 }
::= { xdsl2VopVectorEntry 17 } ::= { xdsl2VopVectorEntry 17 }
xdsl2VopVectorInpDelayProfId3 OBJECT-TYPE xdsl2VopVectorVNoiseProfId OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"" ""
DEFVAL { 0 } DEFVAL { 1 }
::= { xdsl2VopVectorEntry 18 } ::= { xdsl2VopVectorEntry 18 }
xdsl2VopVectorUsDataRateProfId4 OBJECT-TYPE xdsl2VopVectorUpboProfId OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"" ""
DEFVAL { 0 } DEFVAL { 1 }
::= { xdsl2VopVectorEntry 19 } ::= { xdsl2VopVectorEntry 19 }
xdsl2VopVectorUsRaRatio4 OBJECT-TYPE xdsl2VopVectorDpboProfId OBJECT-TYPE
SYNTAX Unsigned32 (0..100)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
""
DEFVAL { 0 }
::= { xdsl2VopVectorEntry 20 }
xdsl2VopVectorDsDataRateProfId4 OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
""
DEFVAL { 0 }
::= { xdsl2VopVectorEntry 21 }
xdsl2VopVectorDsRaRatio4 OBJECT-TYPE
SYNTAX Unsigned32 (0..100)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
""
DEFVAL { 0 }
::= { xdsl2VopVectorEntry 22 }
xdsl2VopVectorInpDelayProfId4 OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
""
DEFVAL { 0 }
::= { xdsl2VopVectorEntry 23 }
xdsl2VopVectorLSpectrumProfId OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"" ""
DEFVAL { 1 } DEFVAL { 1 }
::= { xdsl2VopVectorEntry 24 } ::= { xdsl2VopVectorEntry 20 }
xdsl2VopVectorUpboProfId OBJECT-TYPE xdsl2VopVectorRfiProfId OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"" ""
DEFVAL { 1 } DEFVAL { 1 }
::= { xdsl2VopVectorEntry 25 } ::= { xdsl2VopVectorEntry 21 }
xdsl2VopVectorDpboProfId OBJECT-TYPE xdsl2VopVectorSosProfId OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"" ""
DEFVAL { 1 } DEFVAL { 1 }
::= { xdsl2VopVectorEntry 26 } ::= { xdsl2VopVectorEntry 22 }
xdsl2VopVectorRfiProfId OBJECT-TYPE xdsl2VopVectorInmProfId OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"" ""
DEFVAL { 1 } DEFVAL { 1 }
::= { xdsl2VopVectorEntry 27 } ::= { xdsl2VopVectorEntry 23 }
xdsl2VopVectorNoiseMarginProfId OBJECT-TYPE xdsl2VopVectorVectoringProfId OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"" ""
DEFVAL { 1 } DEFVAL { 1 }
::= { xdsl2VopVectorEntry 28 } ::= { xdsl2VopVectorEntry 24 }
xdsl2VopVectorVNoiseProfId OBJECT-TYPE xdsl2VopVectorReinitProfId OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"" ""
DEFVAL { 1 } DEFVAL { 1 }
::= { xdsl2VopVectorEntry 29 } ::= { xdsl2VopVectorEntry 25 }
------------------------------------------------ ------------------------------------------------
-- xdsl2VopVectorActualTable -- -- xdsl2VopVectorActualTable --
------------------------------------------------ ------------------------------------------------
xdsl2VopVectorActualTable OBJECT-TYPE xdsl2VopVectorActualTable OBJECT-TYPE
SYNTAX SEQUENCE OF Xdsl2VopVectorActualEntry SYNTAX SEQUENCE OF Xdsl2VopVectorActualEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"" ""
skipping to change at page 114, line 43 skipping to change at page 117, line 29
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"" ""
INDEX { xdsl2VopVectorActualIndex } INDEX { xdsl2VopVectorActualIndex }
::= { xdsl2VopVectorActualTable 1 } ::= { xdsl2VopVectorActualTable 1 }
Xdsl2VopVectorActualEntry ::= Xdsl2VopVectorActualEntry ::=
SEQUENCE { SEQUENCE {
xdsl2VopVectorActualIndex Unsigned32, xdsl2VopVectorActualIndex Unsigned32,
xdsl2VopVectorActualUsDataRateProfId1 Unsigned32, xdsl2VopVectorActualUsDataRateProfId1 Unsigned32,
xdsl2VopVectorActualUsRaRatio1 Unsigned32,
xdsl2VopVectorActualDsDataRateProfId1 Unsigned32, xdsl2VopVectorActualDsDataRateProfId1 Unsigned32,
xdsl2VopVectorActualDsRaRatio1 Unsigned32,
xdsl2VopVectorActualInpDelayProfId1 Unsigned32, xdsl2VopVectorActualInpDelayProfId1 Unsigned32,
xdsl2VopVectorActualUsDataRateProfId2 Unsigned32, xdsl2VopVectorActualUsDataRateProfId2 Unsigned32,
xdsl2VopVectorActualUsRaRatio2 Unsigned32,
xdsl2VopVectorActualDsDataRateProfId2 Unsigned32, xdsl2VopVectorActualDsDataRateProfId2 Unsigned32,
xdsl2VopVectorActualDsRaRatio2 Unsigned32,
xdsl2VopVectorActualInpDelayProfId2 Unsigned32, xdsl2VopVectorActualInpDelayProfId2 Unsigned32,
xdsl2VopVectorActualUsDataRateProfId3 Unsigned32, xdsl2VopVectorActualUsDataRateProfId3 Unsigned32,
xdsl2VopVectorActualUsRaRatio3 Unsigned32,
xdsl2VopVectorActualDsDataRateProfId3 Unsigned32, xdsl2VopVectorActualDsDataRateProfId3 Unsigned32,
xdsl2VopVectorActualDsRaRatio3 Unsigned32,
xdsl2VopVectorActualInpDelayProfId3 Unsigned32, xdsl2VopVectorActualInpDelayProfId3 Unsigned32,
xdsl2VopVectorActualUsDataRateProfId4 Unsigned32, xdsl2VopVectorActualUsDataRateProfId4 Unsigned32,
xdsl2VopVectorActualUsRaRatio4 Unsigned32,
xdsl2VopVectorActualDsDataRateProfId4 Unsigned32, xdsl2VopVectorActualDsDataRateProfId4 Unsigned32,
xdsl2VopVectorActualDsRaRatio4 Unsigned32,
xdsl2VopVectorActualInpDelayProfId4 Unsigned32, xdsl2VopVectorActualInpDelayProfId4 Unsigned32,
xdsl2VopVectorActualLSpectrumProfId Unsigned32, xdsl2VopVectorActualLSpectrumProfId Unsigned32,
xdsl2VopVectorActualNoiseMarginProfId Unsigned32,
xdsl2VopVectorActualVNoiseProfId Unsigned32,
xdsl2VopVectorActualUpboProfId Unsigned32, xdsl2VopVectorActualUpboProfId Unsigned32,
xdsl2VopVectorActualDpboProfId Unsigned32, xdsl2VopVectorActualDpboProfId Unsigned32,
xdsl2VopVectorActualRfiProfId Unsigned32, xdsl2VopVectorActualRfiProfId Unsigned32,
xdsl2VopVectorActualNoiseMarginProfId Unsigned32, xdsl2VopVectorActualSosProfId Unsigned32,
xdsl2VopVectorActualVNoiseProfId Unsigned32 xdsl2VopVectorActualInmProfId Unsigned32,
xdsl2VopVectorActualVectoringProfId Unsigned32,
xdsl2VopVectorActualReinitProfId Unsigned32
} }
xdsl2VopVectorActualIndex OBJECT-TYPE xdsl2VopVectorActualIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"" "The index of this Vector of Profiles (VoP) row.
This table is required on in case the implementation
uses a direct attachment of VoP to each xDSL line
and the value of this object is an ifIndex pattern
that identifies the associated DSL line and the
respective row in xdsl2VopLineTable.
In case the implementation uses an indirect
attachment of VoP to xDSL lines then the actual VoP
used for each line is reported via XXXXXXXX in
xdsl2VopLineTable. "
::= { xdsl2VopVectorActualEntry 1 } ::= { xdsl2VopVectorActualEntry 1 }
xdsl2VopVectorActualUsDataRateProfId1 OBJECT-TYPE xdsl2VopVectorActualUsDataRateProfId1 OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"" "Upstream data rate configuration profile for bearer channel
number 1 of the xDSL line that is associated with this VoP.
The value of this object is a row index in
xdsl2VopDataRateProfilesTable."
::= { xdsl2VopVectorActualEntry 2 } ::= { xdsl2VopVectorActualEntry 2 }
xdsl2VopVectorActualUsRaRatio1 OBJECT-TYPE xdsl2VopVectorActualDsDataRateProfId1 OBJECT-TYPE
SYNTAX Unsigned32 (0..100) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"" "Downstream data rate configuration profile for bearer channel
number 1 of the xDSL line that is associated with this VoP.
The value of this object is a row index in
xdsl2VopDataRateProfilesTable."
::= { xdsl2VopVectorActualEntry 3 } ::= { xdsl2VopVectorActualEntry 3 }
xdsl2VopVectorActualDsDataRateProfId1 OBJECT-TYPE xdsl2VopVectorActualInpDelayProfId1 OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"" ""
::= { xdsl2VopVectorActualEntry 4 } ::= { xdsl2VopVectorActualEntry 4 }
xdsl2VopVectorActualDsRaRatio1 OBJECT-TYPE xdsl2VopVectorActualUsDataRateProfId2 OBJECT-TYPE
SYNTAX Unsigned32 (0..100) SYNTAX Unsigned32 (0..4294967295)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"" "Upstream data rate configuration profile for bearer channel
number 2 of the xDSL line that is associated with this VoP.
The value of this object is a row index in
xdsl2VopDataRateProfilesTable."
::= { xdsl2VopVectorActualEntry 5 } ::= { xdsl2VopVectorActualEntry 5 }
xdsl2VopVectorActualInpDelayProfId1 OBJECT-TYPE xdsl2VopVectorActualDsDataRateProfId2 OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (0..4294967295)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"" "Downstream data rate configuration profile for bearer channel
number 2 of the xDSL line that is associated with this VoP.
The value of this object is a row index in
xdsl2VopDataRateProfilesTable."
::= { xdsl2VopVectorActualEntry 6 } ::= { xdsl2VopVectorActualEntry 6 }
xdsl2VopVectorActualUsDataRateProfId2 OBJECT-TYPE xdsl2VopVectorActualInpDelayProfId2 OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295) SYNTAX Unsigned32 (0..4294967295)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"" ""
::= { xdsl2VopVectorActualEntry 7 } ::= { xdsl2VopVectorActualEntry 7 }
xdsl2VopVectorActualUsRaRatio2 OBJECT-TYPE xdsl2VopVectorActualUsDataRateProfId3 OBJECT-TYPE
SYNTAX Unsigned32 (0..100) SYNTAX Unsigned32 (0..4294967295)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"" "Upstream data rate configuration profile for bearer channel
number 3 of the xDSL line that is associated with this VoP.
The value of this object is a row index in
xdsl2VopDataRateProfilesTable."
::= { xdsl2VopVectorActualEntry 8 } ::= { xdsl2VopVectorActualEntry 8 }
xdsl2VopVectorActualDsDataRateProfId2 OBJECT-TYPE xdsl2VopVectorActualDsDataRateProfId3 OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295) SYNTAX Unsigned32 (0..4294967295)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"" "Downstream data rate configuration profile for bearer channel
number 3 of the xDSL line that is associated with this VoP.
The value of this object is a row index in
xdsl2VopDataRateProfilesTable."
::= { xdsl2VopVectorActualEntry 9 } ::= { xdsl2VopVectorActualEntry 9 }
xdsl2VopVectorActualDsRaRatio2 OBJECT-TYPE xdsl2VopVectorActualInpDelayProfId3 OBJECT-TYPE
SYNTAX Unsigned32 (0..100) SYNTAX Unsigned32 (0..4294967295)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"" ""
::= { xdsl2VopVectorActualEntry 10 } ::= { xdsl2VopVectorActualEntry 10 }
xdsl2VopVectorActualInpDelayProfId2 OBJECT-TYPE xdsl2VopVectorActualUsDataRateProfId4 OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295) SYNTAX Unsigned32 (0..4294967295)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"" "Upstream data rate configuration profile for bearer channel
number 4 of the xDSL line that is associated with this VoP.
The value of this object is a row index in
xdsl2VopDataRateProfilesTable."
::= { xdsl2VopVectorActualEntry 11 } ::= { xdsl2VopVectorActualEntry 11 }
xdsl2VopVectorActualUsDataRateProfId3 OBJECT-TYPE xdsl2VopVectorActualDsDataRateProfId4 OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295) SYNTAX Unsigned32 (0..4294967295)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"" "Downstream data rate configuration profile for bearer channel
number 4 of the xDSL line that is associated with this VoP.
The value of this object is a row index in
xdsl2VopDataRateProfilesTable."
::= { xdsl2VopVectorActualEntry 12 } ::= { xdsl2VopVectorActualEntry 12 }
xdsl2VopVectorActualUsRaRatio3 OBJECT-TYPE xdsl2VopVectorActualInpDelayProfId4 OBJECT-TYPE
SYNTAX Unsigned32 (0..100) SYNTAX Unsigned32 (0..4294967295)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"" ""
::= { xdsl2VopVectorActualEntry 13 } ::= { xdsl2VopVectorActualEntry 13 }
xdsl2VopVectorActualDsDataRateProfId3 OBJECT-TYPE xdsl2VopVectorActualLSpectrumProfId OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"" "Line Spectrum configuration profile for the xDSL line that
is associated with this VoP.
The value of this object is a row index in
xdsl2VopLSpectrumProfilesTable."
::= { xdsl2VopVectorActualEntry 14 } ::= { xdsl2VopVectorActualEntry 14 }
xdsl2VopVectorActualDsRaRatio3 OBJECT-TYPE xdsl2VopVectorActualNoiseMarginProfId OBJECT-TYPE
SYNTAX Unsigned32 (0..100) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"" ""
::= { xdsl2VopVectorActualEntry 15 } ::= { xdsl2VopVectorActualEntry 15 }
xdsl2VopVectorActualInpDelayProfId3 OBJECT-TYPE xdsl2VopVectorActualVNoiseProfId OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"" ""
::= { xdsl2VopVectorActualEntry 16 } ::= { xdsl2VopVectorActualEntry 16 }
xdsl2VopVectorActualUsDataRateProfId4 OBJECT-TYPE xdsl2VopVectorActualUpboProfId OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"" ""
::= { xdsl2VopVectorActualEntry 17 } ::= { xdsl2VopVectorActualEntry 17 }
xdsl2VopVectorActualUsRaRatio4 OBJECT-TYPE xdsl2VopVectorActualDpboProfId OBJECT-TYPE
SYNTAX Unsigned32 (0..100) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"" ""
::= { xdsl2VopVectorActualEntry 18 } ::= { xdsl2VopVectorActualEntry 18 }
xdsl2VopVectorActualDsDataRateProfId4 OBJECT-TYPE xdsl2VopVectorActualRfiProfId OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"" ""
::= { xdsl2VopVectorActualEntry 19 } ::= { xdsl2VopVectorActualEntry 19 }
xdsl2VopVectorActualDsRaRatio4 OBJECT-TYPE xdsl2VopVectorActualSosProfId OBJECT-TYPE
SYNTAX Unsigned32 (0..100) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"" ""
::= { xdsl2VopVectorActualEntry 20 } ::= { xdsl2VopVectorActualEntry 20 }
xdsl2VopVectorActualInpDelayProfId4 OBJECT-TYPE xdsl2VopVectorActualInmProfId OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"" ""
::= { xdsl2VopVectorActualEntry 21 } ::= { xdsl2VopVectorActualEntry 21 }
xdsl2VopVectorActualLSpectrumProfId OBJECT-TYPE xdsl2VopVectorActualVectoringProfId OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"" ""
::= { xdsl2VopVectorActualEntry 22 } ::= { xdsl2VopVectorActualEntry 22 }
xdsl2VopVectorActualUpboProfId OBJECT-TYPE xdsl2VopVectorActualReinitProfId OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"" ""
::= { xdsl2VopVectorActualEntry 23 } ::= { xdsl2VopVectorActualEntry 23 }
xdsl2VopVectorActualDpboProfId OBJECT-TYPE ------------------------------------------------
-- xdsl2VopDataRateProfilesTable --
------------------------------------------------
xdsl2VopDataRateProfilesTable OBJECT-TYPE
SYNTAX SEQUENCE OF Xdsl2VopDataRateProfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
""
::= { xdsl2VopProfile 1 }
xdsl2VopDataRateProfEntry OBJECT-TYPE
SYNTAX Xdsl2VopDataRateProfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
""
INDEX { xdsl2VopDataRateProfIndex }
::= { xdsl2VopDataRateProfilesTable 1 }
Xdsl2VopDataRateProfEntry ::=
SEQUENCE {
xdsl2VopDataRateProfIndex Unsigned32,
xdsl2VopDataRateProfRowStatus RowStatus,
xdsl2VopDataRateProfDescription OCTET STRING,
xdsl2VopDataRateProfMinDataRate Unsigned32,
xdsl2VopDataRateProfMinResDataRate Unsigned32,
xdsl2VopDataRateProfMaxDataRate Unsigned32,
xdsl2VopDataRateProfRaRatio Unsigned32,
xdsl2VopDataRateProfMinDataRateLowPower
Unsigned32,
xdsl2VopDataRateProfMaxBer Unsigned32,
xdsl2VopDataRateProfUsDataRate Unsigned32,
xdsl2VopDataRateProfDsDataRate Unsigned32,
xdsl2VopDataRateProfMinSosDataRate Unsigned32,
xdsl2VopDataRateProfMinEtr Unsigned32,
xdsl2VopDataRateProfMaxEtr Unsigned32,
xdsl2VopDataRateProfMaxNdr Unsigned32,
xdsl2VopDataRateProfTargetNdr Unsigned32,
xdsl2VopDataRateProfTargetEtr Unsigned32
}
xdsl2VopDataRateProfIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The index of this data rate profile row."
::= { xdsl2VopDataRateProfEntry 1 }
xdsl2VopDataRateProfRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object is used to create a new row or to modify or
delete an existing row in this table.
A profile is activated by setting this object to 'active'.
Before a profile can be deleted or taken out of service (by
setting this object to 'destroy' or 'notInService'), it MUST be
first unreferenced from all Vector of Profiles.
A row in this table is said to be unreferenced when there is no
instance of xdsl2VopVectorTable or xdsl2VopVectorActualTable
that refers to the row."
::= { xdsl2VopDataRateProfEntry 2 }
xdsl2VopDataRateProfDescription OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (0..128))
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object serves for optionally attaching a description
to the related row. "
DEFVAL { "" }
::= { xdsl2VopDataRateProfEntry 3 }
xdsl2VopDataRateProfMinDataRate OBJECT-TYPE
SYNTAX Unsigned32
UNITS "bits/second"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Minimum Data Rate. The minimum net data rate for
a bearer channel that uses this profile, coded in
bit/s, if retransmission is not used in the relevant
transmit direction."
REFERENCE "ITU-T G.997.1, paragraph #7.3.2.1.1
(Minimum data rate)"
::= { xdsl2VopDataRateProfEntry 4 }
xdsl2VopDataRateProfMinResDataRate OBJECT-TYPE
SYNTAX Unsigned32
UNITS "bits/second"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Minimum Reserved Data Rate. The minimum reserved
net data rate for the bearer channel, coded in bit/s.
This parameter is used only if the Rate Adaptation
Mode in the direction of the bearer channel is set
to 'dynamicRa'."
REFERENCE "ITU-T G.997.1, paragraph #7.3.2.1.2
(Minimum reserved data rate)"
::= { xdsl2VopDataRateProfEntry 5 }
xdsl2VopDataRateProfMaxDataRate OBJECT-TYPE
SYNTAX Unsigned32
UNITS "bits/second"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Maximum Data Rate. The maximum net data rate for
a bearer channel that uses this profile, coded in
bit/s, if retransmission is not used in the relevant
transmit direction."
REFERENCE "ITU-T G.997.1, paragraph #7.3.2.1.3
(Minimum data rate)"
::= { xdsl2VopDataRateProfEntry 6 }
xdsl2VopDataRateProfRaRatio OBJECT-TYPE
SYNTAX Unsigned32 (0..100)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Rate Adaptation Ratio. The ratio (in percent) that should be
taken into account for a bearer channel that uses this profile,
when performing rate adaptation in the transmission direction
of the bearer channel. The ratio refers to the available data
rate in excess of the Minimum Data Rate, summed over all bearer
channels in the relevant transmission direction.
Also, the sum of rate adaptation ratios over all
bearers on the same direction shall be equal to 100%."
REFERENCE "ITU-T G.997.1, paragraph #7.3.2.1.4
(Rate adaptation ratio)"
DEFVAL { 100 }
::= { xdsl2VopDataRateProfEntry 7 }
xdsl2VopDataRateProfMinDataRateLowPower OBJECT-TYPE
SYNTAX Unsigned32
UNITS "bits/second"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Minimum Data Rate in Low Power. This parameter specifies
the minimum net data rate for a bearer channel that uses this
profile during the low power state (L1/L2). The power
management low power states L1 and L2 are defined in ITU-T
Recommendations G.992.2 and G.992.3, respectively.
The data rate is coded in steps of bit/s."
REFERENCE "ITU-T G.997.1, paragraph #7.3.2.1.5
(Minimum Data Rate in low power state)"
::= { xdsl2VopDataRateProfEntry 8 }
xdsl2VopDataRateProfMaxBer OBJECT-TYPE
SYNTAX Xdsl2MaxBer
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Maximum Bit Error Ratio . If retransmission is not
used in the relevant transmit direction by the bearer
channel that uses this profile, this parameter specifies
the Maximum Bit Error Ratio. "
REFERENCE "ITU-T G.997.1, paragraph #7.3.2.6
(Maximum bit error ratio)"
DEFVAL { eminus5 }
::= { xdsl2VopDataRateProfEntry 9 }
xdsl2VopDataRateProfUsDataRate OBJECT-TYPE
SYNTAX Unsigned32
UNITS "bits/second"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Data Rate Threshold Upshift. An
'Up-Shift rate change' event is triggered
(if retransmission is not used in the relevant transmit
direction) when the actual data rate for a bearer channel
that uses this profile exceeds, by more than the
threshold, the data rate at the last entry into Showtime.
The parameter is coded in bit/s."
REFERENCE "ITU-T G.997.1, paragraph #7.3.2.8.1
(Data rate threshold upshift)"
::= { xdsl2VopDataRateProfEntry 10 }
xdsl2VopDataRateProfDsDataRate OBJECT-TYPE
SYNTAX Unsigned32
UNITS "bits/second"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Data Rate Threshold Downshift. An
'Down-Shift rate change' event is triggered
(if retransmission is not used in the relevant transmit
direction) when the actual data rate for a bearer channel
that uses this profile is below the data rate at the last
entry into Showtime, by more than the threshold.
The parameter is coded in bit/s."
REFERENCE "ITU-T G.997.1, paragraph #7.3.2.8.2
(Data rate threshold downshift)"
::= { xdsl2VopDataRateProfEntry 11 }
xdsl2VopDataRateProfMinSosDataRate OBJECT-TYPE
SYNTAX Unsigned32
UNITS "bits/second"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Minimum SOS Bit Rate. This parameter specifies
the minimum net data rate for a valid SOS request, for a
bearer channel that uses this profile.
The value is coded in steps of bit/s.
"
REFERENCE "ITU-T G.997.1, paragraph #7.3.2.1.6
and #7.3.2.1.7 (MIN-SOS-BR-ds/us)"
::= { xdsl2VopDataRateProfEntry 12 }
xdsl2VopDataRateProfMinEtr OBJECT-TYPE
SYNTAX Unsigned32
UNITS "bits/second"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Minimum Expected Throughput for retransmission.
If retransmission is used in the relevant transmit
direction by the bearer channel that uses this profile,
this parameter specifies the minimum expected
throughput, coded in bits/s."
REFERENCE "ITU-T G.997.1, paragraph #7.3.2.1.8
(MINETR_RTX)"
::= { xdsl2VopDataRateProfEntry 13 }
xdsl2VopDataRateProfMaxEtr OBJECT-TYPE
SYNTAX Unsigned32
UNITS "bits/second"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Maximum Expected Throughput for retransmission.
If retransmission is used in the relevant transmit
direction by the bearer channel that uses this profile,
this parameter specifies the maximum expected
throughput, coded in bits/s."
REFERENCE "ITU-T G.997.1, paragraph #7.3.2.1.9
(MAXETR_RTX)"
::= { xdsl2VopDataRateProfEntry 14 }
xdsl2VopDataRateProfMaxNdr OBJECT-TYPE
SYNTAX Unsigned32
UNITS "bits/second"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Maximum Net Data Rate for retransmission.
If retransmission is used in the relevant transmit
direction by the bearer channel that uses this profile,
this parameter specifies the net data rate, coded in
bits/s."
REFERENCE "ITU-T G.997.1, paragraph #7.3.2.1.10
(MAXNDR_RTX)"
::= { xdsl2VopDataRateProfEntry 15 }
xdsl2VopDataRateProfTargetNdr OBJECT-TYPE
SYNTAX Unsigned32
UNITS "bits/second"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Target Net Data Rate for retransmission.
If G.998.4 retransmission is unused in the related
transmit direction, this parameter specifies the target
net data rate (NDR) expected for the bearer channel
that uses this profile while all lines in the
vectored-lines group are active.
Otherwise, this parameter is ignored.
The value is coded in bits/second.
The value 0xFFFFFFFF (4294967295) indicates that
target NDR is not configured for the related bearer
channel. This attribute and the target ETR assist in planning
the resource allocation of the vectoring mechanism."
REFERENCE "ITU-T G.997.1, paragraph #7.3.2.20.1
(???)"
DEFVAL { 4294967295 }
::= { xdsl2VopDataRateProfEntry 16 }
xdsl2VopDataRateProfTargetEtr OBJECT-TYPE
SYNTAX Unsigned32
UNITS "bits/second"
MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Target Expected Throughput for retransmission.
If G.998.4 retransmission is unused in the related
transmit direction, this parameter specifies the target
expected throughput (ETR) for the bearer channel
that uses this profile while all lines in the
vectored-lines group are active.
Otherwise, this parameter is ignored.
The value is coded in bits/second.
The value 0xFFFFFFFF (4294967295) indicates that
target ETR is not configured for the related bearer
channel.
This attribute and the target ETR assist in planning
the resource allocation of the vectoring mechanism."
REFERENCE "ITU-T G.997.1, paragraph #7.3.2.20.2
(???)"
DEFVAL { 4294967295 }
::= { xdsl2VopDataRateProfEntry 17 }
------------------------------------------------
-- xdsl2VopLSpectrumProfilesTable --
------------------------------------------------
xdsl2VopLSpectrumProfilesTable OBJECT-TYPE
SYNTAX SEQUENCE OF Xdsl2VopLSpectrumProfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The xdsl2VopLSpectrumProfilesTable contains configuration
parameters that realize a Line Spectrum Profile which is being
used as part of the Vector of Profiles (VoP).
This is a dynamic table and rows can be added and removed by
the management system. It should always include a default
profile number 1 for the default setup of rows in
xdsl2VopVectorTable.
The xdsl2VopLSpectrumProfilesTable includes configuration
parameters that are independent of the specific transmission
mode(s) enabled by the XTSE configuration parameter (i.e.,
xdsl2VopLSpectrumProfXtuTransSysEna). However, there are
configuration parameters where their setup depends on a
transmission mode. Therefore, each Line Spectrum Profile is also
associated with one or more Mode Specific PSD Profiles. When
the vector of profiles refers to a Line Spectrum Profile it also
implicitly refers to all Mode Specific PSD Profiles associated
with it.
The Mode Specific PSD Profiles are defined in
xdsl2VopModeSpecProfilesTable. The association between these two
tables, i.e., between each row in the Line Spectrum Profiles table
and one or more rows in the Mode Specific PSD Profiles table, is
by, a third table, xdsl2VopModeSpecMapTable. "
::= { xdsl2VopProfile 2 }
xdsl2VopLSpectrumProfEntry OBJECT-TYPE
SYNTAX Xdsl2VopLSpectrumProfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"" ""
::= { xdsl2VopVectorActualEntry 24 } INDEX { xdsl2VopLSpectrumProfIndex }
::= { xdsl2VopLSpectrumProfilesTable 1 }
xdsl2VopVectorActualRfiProfId OBJECT-TYPE Xdsl2VopLSpectrumProfEntry ::=
SEQUENCE {
xdsl2VopLSpectrumProfIndex Unsigned32,
xdsl2VopLSpectrumProfRowStatus RowStatus,
xdsl2VopLSpectrumProfDescription OCTET STRING,
xdsl2VopLSpectrumProfXtuTransSysEna
Xdsl2TransmissionModeType,
xdsl2VopLSpectrumProfPmMode Xdsl2LinePmMode,
xdsl2VopLSpectrumProfL0Time Unsigned32,
xdsl2VopLSpectrumProfL2Time Unsigned32,
xdsl2VopLSpectrumProfL2Atpr Unsigned32,
xdsl2VopLSpectrumProfL2Atprt Unsigned32,
xdsl2VopLSpectrumProfScMaskDs Xdsl2ScMaskDs,
xdsl2VopLSpectrumProfScMaskUs Xdsl2ScMaskUs,
xdsl2VopLSpectrumProfVdsl2CarMask Xdsl2CarMask,
xdsl2VopLSpectrumProfMsgMinUs Unsigned32,
xdsl2VopLSpectrumProfMsgMinDs Unsigned32,
xdsl2VopLSpectrumProfProfiles Xdsl2LineProfiles,
xdsl2VopLSpectrumProfUs0Mask Xdsl2LineUs0Mask,
xdsl2VopLSpectrumProfCeFlag Xdsl2LineCeFlag,
xdsl2VopLSpectrumProfRtxModeUs Xdsl2RtxModes,
xdsl2VopLSpectrumProfRtxModeDs Xdsl2RtxModes
}
xdsl2VopLSpectrumProfIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The index of this line spectrum profile row."
::= { xdsl2VopLSpectrumProfEntry 1 }
xdsl2VopLSpectrumProfRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object is used to create a new row or to modify or
delete an existing row in this table.
A profile is activated by setting this object to 'active'.
Before a profile can be deleted or taken out of service (by
setting this object to 'destroy' or 'notInService'), it MUST be
first unreferenced from all Vector of Profiles.
A row in this table is said to be unreferenced when there is no
instance of xdsl2VopVectorTable or xdsl2VopVectorActualTable
that refers to the row."
::= { xdsl2VopLSpectrumProfEntry 2 }
xdsl2VopLSpectrumProfDescription OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (0..128))
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object serves for optionally attaching a description
to the related row. "
DEFVAL { "" }
::= { xdsl2VopLSpectrumProfEntry 3 }
xdsl2VopLSpectrumProfXtuTransSysEna OBJECT-TYPE
SYNTAX Xdsl2TransmissionModeType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"xTU Transmission System Enabling (XTSE). A list of the
different coding types enabled in this profile. It is coded in a
bitmap representation with 1 or more bits set. A bit set to
'1' means that the xTUs may apply the respective
coding for the DSL line. A bit set to '0' means that
the xTUs cannot apply the respective coding for the ADSL line.
All 'reserved' bits should be set to '0'."
REFERENCE "ITU-T G.997.1, paragraph #7.3.1.1.1 (XTSE)"
::= { xdsl2VopLSpectrumProfEntry 4 }
xdsl2VopLSpectrumProfPmMode OBJECT-TYPE
SYNTAX Xdsl2LinePmMode
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Power management state Enabling (PMMode). Defines the power
states the xTU-C or xTU-R may autonomously transition to on
this line.
This is a set of bits, where any bit with a '1' value
means that the xTU is allowed to transit into the respective
state and any bit with a '0' value means that the xTU
is not allowed to transit into the respective state."
REFERENCE "ITU-T G.997.1, paragraph #7.3.1.1.4 (PMMode)"
DEFVAL { { allowTransitionsToIdle, allowTransitionsToLowPower } }
::= { xdsl2VopLSpectrumProfEntry 5 }
xdsl2VopLSpectrumProfL0Time OBJECT-TYPE
SYNTAX Unsigned32 (0..255)
UNITS "seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The minimum time (in seconds) between an Exit from the L2
state and the next Entry into the L2 state.
It ranges from 0 to 255 seconds."
REFERENCE "ITU-T G.997.1, paragraph #7.3.1.1.5 (L0-TIME)"
DEFVAL { 255 }
::= { xdsl2VopLSpectrumProfEntry 6 }
xdsl2VopLSpectrumProfL2Time OBJECT-TYPE
SYNTAX Unsigned32 (0..255)
UNITS "seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The minimum time (in seconds) between an Entry into the
L2 state and the first Power Trim in the L2 state and between two
consecutive Power Trims in the L2 state.
It ranges from 0 to 255 seconds."
REFERENCE "ITU-T G.997.1, paragraph #7.3.1.1.6 (L2-TIME)"
DEFVAL { 255 }
::= { xdsl2VopLSpectrumProfEntry 7 }
xdsl2VopLSpectrumProfL2Atpr OBJECT-TYPE
SYNTAX Unsigned32 (0..31)
UNITS "dB"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The maximum aggregate transmit power reduction (in dB) that
can be performed at transition of L0 to L2 state or through a
single Power Trim in the L2 state.
It ranges from 0 dB to 31 dB."
REFERENCE "ITU-T G.997.1, paragraph #7.3.1.1.7 (L2-ATPR)"
DEFVAL { 10 }
::= { xdsl2VopLSpectrumProfEntry 8 }
xdsl2VopLSpectrumProfL2Atprt OBJECT-TYPE
SYNTAX Unsigned32 (0..31)
UNITS "dB"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The total maximum aggregate transmit power reduction (in dB)
that can be performed in an L2 state. This is the sum of all
reductions of L2 Requests (i.e., at transition of L0 to L2 state)
and Power Trims."
REFERENCE "ITU-T G.997.1, paragraph #7.3.1.1.9 (L2-ATPRT)"
DEFVAL { 31 }
::= { xdsl2VopLSpectrumProfEntry 9 }
xdsl2VopLSpectrumProfScMaskDs OBJECT-TYPE
SYNTAX Xdsl2ScMaskDs
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Subcarrier mask. A bitmap of 512 bits that allows masking
up to 512 downstream subcarriers. If bit i (0 <= i <
NSCds) is set to '1', the respective downstream
subcarrier is masked, and if set to '0', the respective
subcarrier is unmasked.
Note that there should always be unmasked subcarriers (i.e.,
this object cannot be all 1's).
Also note that if NSCds < 512, all bits i
(NSCds < i <= 512) should be set to '1'."
REFERENCE "ITU-T G.997.1, paragraph #7.3.1.2.6 (CARMASKds)"
::= { xdsl2VopLSpectrumProfEntry 10 }
xdsl2VopLSpectrumProfScMaskUs OBJECT-TYPE
SYNTAX Xdsl2ScMaskUs
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Subcarrier mask. A bitmap of 64 bits that allows masking
up to 64 upstream subcarriers. If bit i (0 <= i < NSCus)
is set to '1', the respective upstream subcarrier is
masked, and if set to '0', the respective subcarrier
is unmasked.
Note that there should always be unmasked subcarriers (i.e.,
this object cannot be all 1's).
Also note that if NSCus < 64, all bits i
(NSCus < i <= 64) should be set to '1'."
REFERENCE "ITU-T G.997.1, paragraph #7.3.1.2.7 (CARMASKus)"
::= { xdsl2VopLSpectrumProfEntry 11 }
xdsl2VopLSpectrumProfVdsl2CarMask OBJECT-TYPE
SYNTAX Xdsl2CarMask
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"VDSL2-specific subcarrier mask. This configuration
parameter defines the restrictions, additional to the band plan,
to determine the set of subcarriers allowed for transmission in
both the upstream and downstream directions.
The parameter shall describe the not masked subcarriers as one or
more frequency bands. Each band is represented by start and stop
subcarrier indices with a subcarrier spacing of 4.3125 kHz. The
valid range of subcarrier indices runs from 0 to at least the
index of the highest allowed subcarrier in both transmission
directions among all profiles enabled by the parameter
xdsl2LConfProfProfiles.
Up to 32 bands may be specified. Other subcarriers shall be
masked."
REFERENCE "ITU-T G.997.1, paragraph #7.3.1.2.8 (VDSL2-
CARMASK)"
::= { xdsl2VopLSpectrumProfEntry 12 }
xdsl2VopLSpectrumProfMsgMinUs OBJECT-TYPE
SYNTAX Unsigned32(4000..248000)
UNITS "bits/second"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Minimum Overhead Rate Upstream. Defines the minimum rate of
the message-based overhead that shall be maintained by the xTU in
upstream direction. Expressed in bits per second and ranges from
4000 to 248000 bits/s."
REFERENCE "ITU-T G.997.1, paragraph #7.3.1.5.1 (MSGMINus)"
DEFVAL { 4000 }
::= { xdsl2VopLSpectrumProfEntry 13 }
xdsl2VopLSpectrumProfMsgMinDs OBJECT-TYPE
SYNTAX Unsigned32(4000..248000)
UNITS "bits/second"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Minimum Overhead Rate Downstream. Defines the minimum rate
of the message-based overhead that shall be maintained by the xTU
in the downstream direction. Expressed in bits per second and
ranges from 4000 to 248000 bits/s."
REFERENCE "ITU-T G.997.1, paragraph #7.3.1.5.2 (MSGMINds)"
DEFVAL { 4000 }
::= { xdsl2VopLSpectrumProfEntry 14 }
xdsl2VopLSpectrumProfProfiles OBJECT-TYPE
SYNTAX Xdsl2LineProfiles
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The configuration parameter contains the G.993.2 profiles
to be allowed by the near-end xTU on this line.
It is coded in a bitmap representation (0 if not allowed, 1 if
allowed)."
REFERENCE "ITU-T G.997.1, paragraph #7.3.1.1.11 (PROFILES)"
DEFVAL { { profile8a, profile8b, profile8c,
profile8d, profile12a, profile12b,
profile17a, profile30a } }
::= { xdsl2VopLSpectrumProfEntry 15 }
xdsl2VopLSpectrumProfUs0Mask OBJECT-TYPE
SYNTAX Xdsl2LineUs0Mask
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The configuration parameter contains 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. It is represented as a bitmap (0
if not allowed and 1 if allowed)."
REFERENCE "ITU-T G.997.1 Amendment 1, paragraph #7.3.1.2.18
(US0MASK)"
DEFVAL { {} }
::= { xdsl2VopLSpectrumProfEntry 16 }
xdsl2VopLSpectrumProfCeFlag OBJECT-TYPE
SYNTAX Xdsl2LineCeFlag
MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This parameter is a bit that enables the use of the optional
cyclic extension values."
REFERENCE "ITU-T G.997.1, paragraph #7.3.1.6.1 (CEFLAG)"
DEFVAL { { } }
::= { xdsl2VopLSpectrumProfEntry 17 }
xdsl2VopLSpectrumProfRtxModeUs OBJECT-TYPE
SYNTAX Xdsl2RtxModes
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"RTX_MODE upstream.
This object controls the enabling and mode of G.998.4
retransmission in upstream transmit-direction.
In G.992.3 and G992.5 transmission modes this object
shall be ignored."
REFERENCE "ITU-T G.997.1, paragraph #7.3.1.11
(RTX_MODE)"
DEFVAL { forbidden }
::= { xdsl2VopLSpectrumProfEntry 18 }
xdsl2VopLSpectrumProfRtxModeDs OBJECT-TYPE
SYNTAX Xdsl2RtxModes
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"RTX_MODE downstream.
This object controls the enabling and mode of G.998.4
retransmission in downstream transmit-direction.
In G.992.3 and G992.5 transmission modes this object
shall be ignored."
REFERENCE "ITU-T G.997.1, paragraph #7.3.1.11
(RTX_MODE)"
DEFVAL { forbidden }
::= { xdsl2VopLSpectrumProfEntry 19 }
------------------------------------------------
-- xdsl2VopModeSpecMapTable --
------------------------------------------------
xdsl2VopModeSpecMapTable OBJECT-TYPE
SYNTAX SEQUENCE OF Xdsl2VopModeSpecMapEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The xdsl2VopModeSpecMapTable serves for associating
rows from xdsl2VopLSpectrumProfilesTable with row(s) in
xdsl2VopModeSpecProfilesTable.
This is a dynamic table and rows are automatically added
and removed by the SNMP agent as result of changes made to
the XTSE configuration parameter, while the status or the
respective row in xdsl2VopLSpectrumProfilesTable is either
notReady or notInService. Modifying a row in this table is
blocked if the related row in xdsl2VopLSpectrumProfilesTable
is active.
When the SNMP manager adds one or more transmission-modes via
xdsl2VopLSpectrumProfXtuTransSysEna object, the SNMP agent
creates a row in this table for each transmission-mode and
maps it (by default) to row number 1 in
xdsl2VopModeSpecProfilesTable.
When the SNMP manager removes one or more transmission-modes via
xdsl2VopLSpectrumProfXtuTransSysEna object, the SNMP agent
deletes all associated rows from this table."
::= { xdsl2VopProfile 3 }
xdsl2VopModeSpecMapEntry OBJECT-TYPE
SYNTAX Xdsl2VopModeSpecMapEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"" ""
::= { xdsl2VopVectorActualEntry 25 } INDEX { xdsl2VopModeSpecMapIndex, xdsl2VopModeSpecMapMode }
::= { xdsl2VopModeSpecMapTable 1 }
xdsl2VopVectorActualNoiseMarginProfId OBJECT-TYPE Xdsl2VopModeSpecMapEntry ::=
SEQUENCE {
xdsl2VopModeSpecMapIndex Unsigned32,
xdsl2VopModeSpecMapMode Xdsl2OperationModes,
xdsl2VopModeSpecMapProfId Unsigned32
}
xdsl2VopModeSpecMapIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"" "The index of the Line Spectrum Profile
::= { xdsl2VopVectorActualEntry 26 } associated with this row."
::= { xdsl2VopModeSpecMapEntry 1 }
xdsl2VopVectorActualVNoiseProfId OBJECT-TYPE xdsl2VopModeSpecMapMode OBJECT-TYPE
SYNTAX Xdsl2OperationModes
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The DSL transmission mode associated with this row.
When a Line Spectrum Profile enables one or more
transmission-modes (via xdsl2VopLSpectrumProfXtuTransSysEna)
then the SNMP agent creates a row in this table for each of
them in order to map each transmission-mode with the
mode-specific configuration applicable for it.
When a Line Spectrum Profile disables one or more,
previously enabled, transmission-modes then the SNMP agent
deletes all rows in this table that are associated with them.
Note that multiple transmission-modes may share the same
mode-specific configuration."
::= { xdsl2VopModeSpecMapEntry 2 }
xdsl2VopModeSpecMapProfId OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS read-only MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object associates, for the Line Spectrum Profile
given by xdsl2VopModeSpecMapIndex object in this row and
the transmission mode given by xdsl2VopModeSpecMapMode
object in this row, a mode-specific profile from
xdsl2VopModeSpecProfilesTable."
DEFVAL { 1 }
::= { xdsl2VopModeSpecMapEntry 3 }
------------------------------------------------
-- xdsl2VopModeSpecProfilesTable --
------------------------------------------------
xdsl2VopModeSpecProfilesTable OBJECT-TYPE
SYNTAX SEQUENCE OF Xdsl2VopModeSpecProfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The xdsl2VopModeSpecProfilesTable extends the
xdsl2VopLSpectrumProfilesTable by mode-specifc configuration
parameters, i.e., parameters that their setup depends on the
specific transmission-mode used by the DSL line. The
relationship between the tables is explained in the
following paragraphs.
The xdsl2VopLSpectrumProfilesTable includes Line Spectrum
configuration parameters that are independent of the
specific transmission-mode(s) enabled by the XTSE configuration
parameter (i.e., xdsl2VopLSpectrumProfXtuTransSysEna). However,
there are configuration parameters where their setup depends on
a transmission-mode. Therefore, each Line Spectrum Profile is
also associated with one or more Mode Specific PSD Profiles
from this table (xdsl2VopModeSpecProfilesTable). When the
vector of profiles (VoP) refers to a Line Spectrum Profile it
also implicitly refers to all rows in
xdsl2VopModeSpecProfilesTable that are associated with that
Line Spectrum Profile.
The association between each row in the Line Spectrum Profiles
table and one or more rows in this table, is performed by, a
third table, xdsl2VopModeSpecMapTable.
The xdsl2VopModeSpecProfilesTable is a stand-alone dynamic
table and basically rows can always be added to it. Similarly,
rows can be removed from the table by the SNMP manager, as
long as they are not referenced by any row in the
xdsl2VopModeSpecMapTable.
In particular, this table should always include profile
number 1 serving for the default setup of rows in
xdsl2VopModeSpecMapTable.
Entries in this table MUST be maintained in a persistent
manner."
::= { xdsl2VopProfile 4 }
xdsl2VopModeSpecProfEntry OBJECT-TYPE
SYNTAX Xdsl2VopModeSpecProfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"" ""
::= { xdsl2VopVectorActualEntry 27 } INDEX { xdsl2VopModeSpecProfIndex }
::= { xdsl2VopModeSpecProfilesTable 1 }
Xdsl2VopModeSpecProfEntry ::=
SEQUENCE {
xdsl2VopModeSpecProfIndex Unsigned32,
xdsl2VopModeSpecProfRowStatus RowStatus,
xdsl2VopModeSpecProfDescription OCTET STRING,
xdsl2VopModeSpecProfModes Xdsl2TransmissionModeType,
xdsl2VopModeSpecProfMaxNomPsdDs Integer32,
xdsl2VopModeSpecProfMaxNomPsdUs Integer32,
xdsl2VopModeSpecProfMaxNomAtpDs Unsigned32,
xdsl2VopModeSpecProfMaxNomAtpUs Unsigned32,
xdsl2VopModeSpecProfMaxAggRxPwrUs Integer32,
xdsl2VopModeSpecProfPsdMaskDs Xdsl2PsdMaskDs,
xdsl2VopModeSpecProfPsdMaskSelectUs
Xdsl2LinePsdMaskSelectUs,
xdsl2VopModeSpecProfPsdMaskUs Xdsl2PsdMaskUs,
xdsl2VopModeSpecProfLimitMask Xdsl2LineLimitMask,
xdsl2VopModeSpecProfUs0Disable Xdsl2LineUs0Disable,
xdsl2VopModeSpecProfClassMask Xdsl2LineClassMask
}
xdsl2VopModeSpecProfIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The index of this Mode Specific configuration
profile row."
::= { xdsl2VopModeSpecProfEntry 1 }
xdsl2VopModeSpecProfRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object is used to create a new row or to modify or
delete an existing row in this table.
A profile is activated by setting this object to 'active'.
Before a profile can be deleted or taken out of service (by
setting this object to 'destroy' or 'notInService'), it MUST be
first unreferenced from all Vector of Profiles.
A row in this table is said to be unreferenced when there is no
instance of xdsl2VopModeSpecMapTable that refers to the row."
::= { xdsl2VopModeSpecProfEntry 2 }
xdsl2VopModeSpecProfDescription OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (0..128))
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object serves for optionally attaching a description
to the related row. "
DEFVAL { "" }
::= { xdsl2VopModeSpecProfEntry 3 }
xdsl2VopModeSpecProfModes OBJECT-TYPE
SYNTAX Xdsl2TransmissionModeType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object is a list of the different coding types
(DSL transmission-modes) that the SNMP manager assumes may be
associated with this profile. It is coded in a
bitmap representation with 1 or more bits set. A bit set to
'1' means that the profile is applicable for the
respective transmission mode. A bit set to '0' means
that the profile is not applicable for the respective
transmission mode.
All 'reserved' bits should be set to '0'.
The default value '0' cannot serve as a valid setup
for this object and should be changed prior to activating the
profile."
DEFVAL { 0 }
::= { xdsl2VopModeSpecProfEntry 4 }
xdsl2VopModeSpecProfMaxNomPsdDs OBJECT-TYPE
SYNTAX Integer32(-600..-300)
UNITS "0.1 dBm/Hz"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The maximum nominal transmit PSD in the downstream direction
during initialization and Showtime. It ranges from -600 to -300
units of 0.1 dBm/Hz (physical values are -60 to -30 dBm/Hz)."
REFERENCE "ITU-T G.997.1, paragraph #7.3.1.2.1 (MAXNOMPSDds)"
DEFVAL { -380 }
::= { xdsl2VopModeSpecProfEntry 5 }
xdsl2VopModeSpecProfMaxNomPsdUs OBJECT-TYPE
SYNTAX Integer32(-600..-300)
UNITS "0.1 dBm/Hz"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The maximum nominal transmit PSD in the upstream direction
during initialization and Showtime. It ranges from -600 to -300
units of 0.1 dBm/Hz (physical values are -60 to -30 dBm/Hz)."
REFERENCE "ITU-T G.997.1, paragraph #7.3.1.2.2 (MAXNOMPSDus)"
DEFVAL { -380 }
::= { xdsl2VopModeSpecProfEntry 6 }
xdsl2VopModeSpecProfMaxNomAtpDs OBJECT-TYPE
SYNTAX Unsigned32 (0..255)
UNITS "0.1 dBm"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The maximum nominal aggregate to transmit power in the
downstream direction during initialization and Showtime. It
ranges from 0 to 255 units of 0.1 dBm (physical values are 0
to 25.5 dBm)."
REFERENCE "ITU-T G.997.1, paragraph #7.3.1.2.3 (MAXNOMATPds)"
DEFVAL { 145 }
::= { xdsl2VopModeSpecProfEntry 7 }
xdsl2VopModeSpecProfMaxNomAtpUs OBJECT-TYPE
SYNTAX Unsigned32 (0..255)
UNITS "0.1 dBm"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The maximum nominal aggregate transmit power in the upstream
direction during initialization and Showtime. It ranges from
0 to 255 units of 0.1 dBm (physical values are 0 to 25.5 dBm)."
REFERENCE "ITU-T G.997.1, paragraph #7.3.1.2.4 (MAXNOMATPus)"
DEFVAL { 145 }
::= { xdsl2VopModeSpecProfEntry 8 }
xdsl2VopModeSpecProfMaxAggRxPwrUs OBJECT-TYPE
SYNTAX Integer32(-255..255 | 2147483647)
UNITS "0.1 dBm"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The maximum upstream aggregate receive power over the
relevant set of subcarriers. The xTU-C should verify that the
upstream power cutback is such that this maximum aggregate
receive power value is honored. It ranges from -255 to 255
units of 0.1 dBm (physical values are -25.5 to 25.5 dBm).
A value of 0x7FFFFFFF (2147483647) means that there is no
limit."
REFERENCE "ITU-T G.997.1, paragraph #7.3.1.2.5 (MAXRXPWRus)"
DEFVAL { 145 }
::= { xdsl2VopModeSpecProfEntry 9 }
xdsl2VopModeSpecProfPsdMaskDs OBJECT-TYPE
SYNTAX Xdsl2PsdMaskDs
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The downstream PSD mask applicable at the U-C2 reference
point.
This parameter is used only for G.992.5 and G.993.2 and it
may impose PSD restrictions (breakpoints) in addition to the
Limit PSD mask defined in G.992.5 and G.993.2.
This is a string of 32 pairs of values in the following
structure:
Octets 0-1 - Index of the first subcarrier used in the context of
a first breakpoint.
Octet 2 - The PSD reduction for the subcarrier indicated in
octets 0 and 1.
Octets 3-5 - Same, for a second breakpoint.
Octets 6-8 - Same, for a third breakpoint.
This architecture continues until octets 94-95, which are
associated with a 32nd breakpoint.
Each subcarrier index is an unsigned number in the range 0 and
NSds. Each PSD reduction value is in the range 0 (0 dBm/Hz) to
255 (-127.5 dBm/Hz) with steps of 0.5 dBm/Hz. Valid values are in
the range 0 to 190 (0 to -95 dBm/Hz).
When the number of breakpoints is less than 32, all remaining
octets are set to the value '0'. Note that the content of this
object should be correlated with the subcarrier mask and with
the RFI setup."
REFERENCE "ITU-T G.997.1, paragraph #7.3.1.2.9 (PSDMASKds)"
::= { xdsl2VopModeSpecProfEntry 10 }
xdsl2VopModeSpecProfPsdMaskSelectUs OBJECT-TYPE
SYNTAX Xdsl2LinePsdMaskSelectUs
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The selected upstream PSD mask. This parameter is used only
for Annexes J and M of G.992.3 and G.992.5, and the same
selection is used for all relevant enabled bits in
xdsl2VopLSpectrumProfXtuTransSysEna.
If xdsl2VopModeSpecProfPsdMaskUs is also specified then
the final upstream PSD mask is the minimum mask derived from
both parameters."
REFERENCE "ITU-T G.997.1, paragraph #7.3.1.2.11
(Upstream PSD mask selection)"
DEFVAL { adlu32Eu32 }
::= { xdsl2VopModeSpecProfEntry 11 }
xdsl2VopModeSpecProfPsdMaskUs OBJECT-TYPE
SYNTAX Xdsl2PsdMaskUs
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The downstream PSD mask applicable at the U-R2 reference
point.
This parameter is used only for G.992.5 and G.993.2 and it
may impose PSD restrictions (breakpoints) in addition to the
Limit PSD mask defined in G.992.5 and G.993.2.
This is a string of 16 pairs of values in the following
structure:
Octets 0-1 - Index of the first subcarrier used in the context of
a first breakpoint.
Octet 2 - The PSD reduction for the subcarrier indicated in
octets 0 and 1.
Octets 3-5 - Same, for a second breakpoint.
Octets 6-8 - Same, for a third breakpoint.
This architecture continues until octets 46-47, which are
associated with a 16th breakpoint.
Each subcarrier index is an unsigned number in the range 0 and
NSds. Each PSD reduction value is in the range 0 (0 dBm/Hz) to
255 (-127.5 dBm/Hz) with steps of 0.5 dBm/Hz. Valid values are in
the range 0 to 190 (0 to -95 dBm/Hz).
When the number of breakpoints is less than 16, all remaining
octets are set to the value '0'. Note that the content of this
object should be correlated with the subcarrier mask and with
the RFI setup."
REFERENCE "ITU-T G.997.1, paragraph #7.3.1.2.12 (PSDMASKus)"
::= { xdsl2VopModeSpecProfEntry 12 }
xdsl2VopModeSpecProfLimitMask OBJECT-TYPE
SYNTAX Xdsl2LineLimitMask
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This configuration parameter contains the G.993.2 limit
PSD masks of the selected PSD mask class, enabled by the near-end
xTU on this line for each class of profiles.
This parameter is defined per VDSL2 Annex enabled in the
xdsl2VopLSpectrumProfXtuTransSysEna object.
Through this parameter, several limit PSD masks of the selected
PSD mask class (xdsl2VopModeSpecProfClassMask) may be enabled.
The enabling parameter is coded in a bitmap representation (0
if the associated mask is not allowed, 1 if it is allowed)."
REFERENCE "ITU-T G.997.1 Amendment 1, paragraph #7.3.1.2.16
(LIMITMASK)"
DEFVAL { {} }
::= { xdsl2VopModeSpecProfEntry 13 }
xdsl2VopModeSpecProfUs0Disable OBJECT-TYPE
SYNTAX Xdsl2LineUs0Disable
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This configuration parameter indicates if the use of the US0 is
disabled for each limit PSD mask enabled in the
xdsl2VopModeSpecProfLimitMask parameter.
This parameter is defined per VDSL2 Annex enabled in the
xdsl2VopLSpectrumProfXtuTransSysEna object.
For each limit PSD mask enabled in the xdsl2VopModeSpecProfLimitMask
parameter, a bit shall indicate if the US0 is disabled. The
disabling parameter is coded as a bitmap. The bit is set to '1'
if the US0 is disabled for the associated limit mask."
REFERENCE "ITU-T G.997.1, paragraph #7.3.1.2.17 (US0DISABLE)"
DEFVAL { {} }
::= { xdsl2VopModeSpecProfEntry 14 }
xdsl2VopModeSpecProfClassMask OBJECT-TYPE
SYNTAX Xdsl2LineClassMask
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"In order to reduce the number of configuration
possibilities, the limit Power Spectral Density masks (see
LIMITMASK) are grouped in PSD mask classes.
Each class is designed such that the PSD levels of each limit PSD
mask of a specific class are equal in their respective passband
above 552 kHz.
This parameter is defined per VDSL2 Annex enabled in the
xdsl2VopLSpectrumProfXtuTransSysEna object. It selects a single
PSD mask class per Annex that is activated at the VTU-O."
REFERENCE "ITU-T G.997.1 Amendment 1, paragraph #7.3.1.2.15
(CLASSMASK)"
DEFVAL { a998ORb997M1cORc998B }
::= { xdsl2VopModeSpecProfEntry 15 }
------------------------------------------------ ------------------------------------------------
-- xdsl2LineConfTemplateTable -- -- xdsl2LineConfTemplateTable --
------------------------------------------------ ------------------------------------------------
xdsl2LineConfTemplateTable OBJECT-TYPE xdsl2LineConfTemplateTable OBJECT-TYPE
SYNTAX SEQUENCE OF Xdsl2LineConfTemplateEntry SYNTAX SEQUENCE OF Xdsl2LineConfTemplateEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The table xdsl2LineConfTemplateTable contains VDSL2/ADSL/ "The table xdsl2LineConfTemplateTable contains VDSL2/ADSL/
 End of changes. 220 change blocks. 
513 lines changed or deleted 1698 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/