draft-ietf-adslmib-vdsl-02.txt   draft-ietf-adslmib-vdsl-03.txt 
Network Working Group R. Abbi Network Working Group B. Ray
Category: Internet Draft Alcatel Category: Internet Draft PESA Switching Systems
R. Abbi
B. Ray Alcatel
April 2002 June 2002
Definitions of Managed Objects for VDSL Lines Definitions of Managed Objects for Very High
draft-ietf-adslmib-vdsl-02.txt Speed Digital Subscriber Lines (VDSL)
draft-ietf-adslmib-vdsl-03.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is subject to all provisions This document is an Internet-Draft and is subject to all provisions
of Section 10 of RFC2026. of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as other groups may also distribute working documents as Internet-
Internet-Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six months
months and may be updated, replaced, or obsoleted by other and may be updated, replaced, or obsoleted by other documents at any
documents at any time. It is inappropriate to use Internet-Drafts time. It is inappropriate to use Internet-Drafts as reference
as reference material or to cite them other tan as "work in material or to cite them other than as "work in progress."
progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/1id-abstracts.html http://www.ietf.org/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2002). All Rights Reserved. Copyright (C) The Internet Society (2002). All Rights Reserved.
Table of Contents Abstract
1. Abstract .................................................. 2 This document defines a Management Information Base (MIB) module for
2. The SNMP Network Management Framework ..................... 2 use with network management protocols in the Internet community. In
3. Introduction .............................................. 3 particular, it describes objects used for managing Very high speed
3.1 IANA Considerations ....................................... 3 Digital Subscriber Line (VDSL) interfaces [T1E1311, T1E1011, T1E1013,
3.2 Relationship of the VDSL Line MIB to other MIBs ........... 4 ETSI2701, ETSI2702, ITU9931].
4. Conventions used in the MIB ............................... 5
4.1 Naming Conventions ........................................ 5
4.2 Textual Conventions ....................................... 5
4.3 Structure ................................................. 6
4.4 Counters, Interval Buckets and Thresholds ................. 7
4.5 Profiles .................................................. 8
4.6 Notifications ............................................. 9
5. Conformance and Compliance ................................ 9
6. Definitions ............................................... 10
7. Security Considerations ................................... 48
8. Acknowledgments ........................................... 49
9. References ................................................ 49
10. Intellectual Property Notice .............................. 51
11. Authors' Addresses ........................................ 51
12. Full Copyright Statement .................................. 51
1. Abstract This document specifies a MIB module in a manner that is compliant
to the SMIv2 (STD 58 [RFC2578, RFC2579, RFC2580]).
This document defines a portion of the Management Information Base Table of Contents
(MIB) module for use with network management protocols in the
Internet community. In particular, it describes objects used for
managing Very high speed Digital Subscriber Line (VDSL) interfaces
[18, 19, 20].
This document specifies a MIB module in a manner that is compliant 1. The SNMP Management Framework ............................. 2
to the SMIv2 (STD 58 [5, 6, 7]). 2. Overview .................................................. 3
2.1 Relationship of the VDSL Line MIB to other MIBs ........... 3
2.2 Conventions used in the MIB ............................... 5
2.3 Structure ................................................. 6
2.4 Counters, Interval Buckets and Thresholds ................. 8
2.5 Profiles .................................................. 8
2.6 Notifications ............................................. 10
2.7 Persistence ............................................... 10
3. Conformance and Compliance ................................ 12
4. Definitions ............................................... 12
References ................................................ 66
Security Considerations ................................... 68
IANA Considerations ....................................... 69
Acknowledgments ........................................... 69
Intellectual Property Notice .............................. 69
Authors' Addresses ........................................ 70
Full Copyright Statement .................................. 70
2. The SNMP Management Framework 1. The SNMP Management Framework
The SNMP Management Framework presently consists of five major The SNMP Management Framework presently consists of five major
components: components:
o An overall architecture, described in RFC 2571 [1]. o An overall architecture, described in RFC 2571 [RFC2571].
o Mechanisms for describing and naming objects and events for the o Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in Management Information (SMI) is called SMIv1 and described in
STD 16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4]. STD 16 [RFC1155, RFC1212] and RFC 1215 [RFC1215]. The second
The second version, called SMIv2, is described in STD 58, RFC version, called SMIv2, is described in STD 58 [RFC2578, RFC2579,
2578 [5], STD 58, RFC 2579 [6] and STD 58, RFC 2580 [7]. RFC2580].
o Message protocols for transferring management information. The o Message protocols for transferring management information. The
first version of the SNMP message protocol is called SNMPv1 and first version of the SNMP message protocol is called SNMPv1 and
described in STD 15, RFC 1157 [8]. A second version of the SNMP described in STD 15 [RFC1157]. A second version of the SNMP
message protocol, which is not an Internet standards track message protocol, which is not an Internet standards track
protocol, is called SNMPv2c and described in RFC 1901 [9] and protocol, is called SNMPv2c and described in RFC 1901 [RFC1901]
RFC 1906 [10]. The third version of the message protocol is and RFC 1906 [RFC1906]. The third version of the message
called SNMPv3 and described in RFC 1906 [10], RFC 2572 [11] and protocol is called SNMPv3 and described in RFC 1906 [RFC1906],
RFC 2574 [12]. RFC 2572 [RFC2572] and RFC 2574 [RFC2574].
o Protocol operations for accessing management information. The o Protocol operations for accessing management information. The
first set of protocol operations and associated PDU formats is first set of protocol operations and associated PDU formats is
described in STD 15, RFC 1157 [8]. A second set of protocol described in STD 15 [RFC1157]. A second set of protocol
operations and associated PDU formats is described in RFC 1905 operations and associated PDU formats is described in RFC 1905
[13]. [RFC1905].
o A set of fundamental applications described in RFC 2573 [14] o A set of fundamental applications described in RFC 2573 [RFC2573]
and the view-based access control mechanism described in RFC and the view-based access control mechanism described in RFC
2575 [15]. 2575 [RFC2575].
A more detailed introduction to the current SNMP Management Framework A more detailed introduction to the current SNMP Management Framework
can be found in RFC 2570 [16]. can be found in RFC 2570 [RFC2570].
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. Objects in the MIB are the Management Information Base or MIB. Objects in the MIB are
defined using the mechanisms defined in the SMI. defined using the mechanisms defined in the SMI.
This memo specifies a MIB module that is compliant to the SMIv2. A This memo specifies a MIB module that is compliant to the SMIv2. A
MIB conforming to the SMIv1 can be produced through the appropriate MIB conforming to the SMIv1 can be produced through the appropriate
translations. The resulting translated MIB must be semantically translations. The resulting translated MIB must be semantically
equivalent, except where objects or events are omitted because no equivalent, except where objects or events are omitted because no
translation is possible (use of Counter64). Some machine readable translation is possible (use of Counter64). Some machine readable
information in SMIv2 will be converted into textual descriptions in information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of machine SMIv1 during the translation process. However, this loss of machine
readable information is not considered to change the semantics of the readable information is not considered to change the semantics of the
MIB. MIB.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
this document are to be interpreted as described in RFC 2119 [17]. this document are to be interpreted as described in RFC 2119
[RFC2119].
3. Introduction 2. Overview
This document describes an SNMP MIB for managing VDSL Lines. These This document describes an SNMP MIB for managing VDSL Lines. These
definitions are based upon the specifications for VDSL as defined definitions are based upon the specifications for VDSL as defined
in [18, 19, 20]. in T1E1, ETSI, and ITU documentation [T1E1311, T1E1011, T1E1013,
ETSI2701, ETSI2702, ITU9931].
The MIB is located in the MIB tree under MIB 2 transmission, as The MIB is located in the MIB tree under MIB 2 transmission, as
discussed in the MIB-2 Integration (RFC 2863 [23]) section of this discussed in the MIB-2 Integration (RFC 2863 [RFC2863]) section of
document. this document.
3.1 IANA Considerations
The SNMPv2-TM MIB module requires the allocation of a single object
identifier for its MODULE-IDENTITY. IANA should allocate this object
identifier in the snmpModules subtree, defined in the SNMPv2-SMI MIB
module.
3.2. Relationship of the VDSL Line MIB to other MIBs 2.1 Relationship of the VDSL Line MIB to other MIBs
This section outlines the relationship of this MIB with other MIBs This section outlines the relationship of this MIB with other MIBs
described in RFCs. Specifically, IF-MIB as presented RFC 2863 [23] described in RFCs. Specifically, IF-MIB as presented RFC 2863
is discussed. [RFC2863] is discussed.
3.2.1 General IF-MIB Integration (RFC 2863) 2.1.1 General IF-MIB Integration (RFC 2863)
The VDSL Line MIB specifies the detailed attributes of a data The VDSL Line MIB specifies the detailed attributes of a data
interface. As such, it needs to integrate with RFC 2863 [23]. The interface. As such, it needs to integrate with RFC 2863 [RFC2863].
IANA has assigned the following ifType to VDSL: The IANA has assigned the following ifType to VDSL:
IANAifType ::= TEXTUAL-CONVENTION IANAifType ::= TEXTUAL-CONVENTION
... ...
SYNTAX INTEGER { SYNTAX INTEGER {
... ...
vdsl(97), -- Very H-speed Digital Subscrib. Loop vdsl(97), -- Very H-speed Digital Subscrib. Loop
... ...
} }
3.2.2 Usage of ifTable Additionally, a VDSL line may contain an optional fast channel
and an optional interleaved channel which also integrate into RFC
2863 [RFC2863]. The IANA has assigned the following ifTypes to these
channels:
IANAifType ::= TEXTUAL-CONVENTION
...
SYNTAX INTEGER {
...
interleave (124), -- Interleave channel
fast (125), -- Fast channel
...
}
2.1.2 Usage of ifTable
The MIB branch identified by this ifType contains tables appropriate The MIB branch identified by this ifType contains tables appropriate
for this interface type. Most such tables extend the ifEntry table, for this interface type. Most such tables extend the ifEntry table,
and are indexed by ifIndex. For interfaces in systems implementing and are indexed by ifIndex. For interfaces in systems implementing
this MIB, those table entries indexed by ifIndex MUST be persistent. this MIB, those table entries indexed by ifIndex MUST be persistent.
The following attributes are part of the mandatory ifGeneral group in The following attributes are part of the mandatory ifGeneral group in
RFC 2863 [23], and are not duplicated in the VDSL Line MIB. RFC 2863 [RFC2863], and are not duplicated in the VDSL Line MIB.
=================================================================== ===================================================================
ifIndex Interface index. ifIndex Interface index.
ifDescr See interfaces MIB [21]. ifDescr See interfaces MIB [RFC2863].
ifType vdsl(97) ifType vdsl(97),
interleaved(124), or
fast(125)
ifSpeed Set as appropriate. ifSpeed Set as appropriate.
ifPhysAddress This object MUST have an octet string ifPhysAddress This object MUST have an octet string
with zero length. with zero length.
ifAdminStatus See interfaces MIB [21]. ifAdminStatus See interfaces MIB [RFC2863].
ifOperStatus See interfaces MIB [21]. ifOperStatus See interfaces MIB [RFC2863].
ifLastChange See interfaces MIB [21]. ifLastChange See interfaces MIB [RFC2863].
ifName See interfaces MIB [21]. ifName See interfaces MIB [RFC2863].
ifLinkUpDownTrapEnable Default to enabled(1). ifLinkUpDownTrapEnable Default to enabled(1).
ifHighSpeed Set as appropriate. ifHighSpeed Set as appropriate.
ifConnectorPresent Set as appropriate. ifConnectorPresent Set as appropriate.
=================================================================== ===================================================================
Figure 1: Use of ifTable Objects Figure 1: Use of ifTable Objects
4. Conventions used in the MIB Section 2.3, below, describes the structure of this MIB in relation
to ifEntry in greater detail.
4.1. Naming Conventions 2.2 Conventions used in the MIB
2.2.1 Naming Conventions
A. Vtuc -- (VTUC) modem at near (Central) end of line A. Vtuc -- (VTUC) modem at near (Central) end of line
B. Vtur -- (VTUR) modem at Remote end of line B. Vtur -- (VTUR) modem at Remote end of line
C. Vtu -- One of either Vtuc or Vtur C. Vtu -- One of either Vtuc or Vtur
D. Curr -- Current D. Curr -- Current
E. Prev -- Previous E. Prev -- Previous
F. Atn -- Attenuation F. Atn -- Attenuation
G. ES -- Errored Second. G. ES -- Errored Second
H. LCS -- Line Code Specific H. SES -- Severely Errored Second
I. Lof -- Loss of Frame I. UAS -- Unavailable Second
J. Lol -- Loss of Link J. LCS -- Line Code Specific
K. Los -- Loss of Signal K. Lof -- Loss of Frame
L. Lpr -- Loss of Power L. Lol -- Loss of Link
M. xxxs -- interval of Seconds in which xxx occurs M. Los -- Loss of Signal
N. Lpr -- Loss of Power
O. xxxs -- interval of Seconds in which xxx occurs
(e.g., xxx=Lof, Los, Lpr) (e.g., xxx=Lof, Los, Lpr)
N. Max -- Maximum P. Max -- Maximum
O. Mgn -- Margin Q. Mgn -- Margin
P. Min -- Minimum R. Min -- Minimum
Q. Psd -- Power Spectral Density S. Psd -- Power Spectral Density
R. Snr -- Signal to Noise Ratio T. Snr -- Signal to Noise Ratio
S. Tx -- Transmit U. Tx -- Transmit
T. Blks -- Blocks, a data unit, see vdslVtuXChanCrcBlockLength V. Blks -- Blocks
4.2. Textual Conventions 2.2.2 Textual Conventions
The following textual conventions are defined to reflect the line The following textual conventions are defined to reflect the line
topology in the MIB (further discussed in the following section) topology in the MIB (further discussed in the following section)
and to define the behavior of the statistics to be maintained and to define the behavior of the statistics to be maintained
by an agent. by an agent.
o VdslLineCodingType : o VdslLineCodingType :
Attributes with this syntax identify the line coding used. Attributes with this syntax identify the line coding used.
Specified as an INTEGER, the three values are: Specified as an INTEGER, the three values are:
skipping to change at page 6, line 4 skipping to change at page 6, line 33
Attributes with this syntax identify the line coding used. Attributes with this syntax identify the line coding used.
Specified as an INTEGER, the three values are: Specified as an INTEGER, the three values are:
other(1) -- none of the following other(1) -- none of the following
mcm(2) -- Multiple Carrier Modulation mcm(2) -- Multiple Carrier Modulation
scm(3) -- Single Carrier Modulation scm(3) -- Single Carrier Modulation
o VdslLineEntity : o VdslLineEntity :
Attributes with this syntax reference the two sides of a line. Attributes with this syntax reference the two sides of a line.
Specified as an INTEGER, the two values are: Specified as an INTEGER, the two values are:
vtuc(1) -- central site modem vtuc(1) -- central site modem
vtur(2) -- remote site modem vtur(2) -- remote site modem
4.3. Structure 2.3 Structure
The MIB is structured into following MIB groups: The MIB is structured into following MIB groups:
o vdslGroup : o vdslGroup :
This group supports all line code independent MIB objects found This group supports all line code independent MIB objects found
in this MIB. It contains the following tables: in this MIB. The following tables contain objects permitted for
ifType vdsl(97):
- vdslLineTable - vdslLineTable
- vdslPhysTable - vdslPhysTable
- vdslChanTable
- vdslPerfDataTable - vdslPerfDataTable
- vdslPerfIntervalTable - vdslPerfIntervalTable
- vdslChanPerfDataTable - vdslPerf1DayIntervalTable
- vdslChanPerfIntervalTable
- vdslLineConfProfileTable - vdslLineConfProfileTable
- vdslLineAlarmConfProfileTable - vdslLineAlarmConfProfileTable
The following tables contain objects permitted for ifTypes
interleaved(124) and (fast):
- vdslChanTable
- vdslChanPerfDataTable
- vdslChanPerfIntervalTable
- vdslChanPerf1DayIntervalTable
o vdslMCMGroup : o vdslMCMGroup :
This group supports MIB objects for defining configuration profiles This group supports MIB objects for defining configuration profiles
for Multiple Carrier Modulation (MCM) VDSL modems. It contains the for Multiple Carrier Modulation (MCM) VDSL modems. It contains the
following tables: following tables:
- vdslLineMCMConfProfileTable - vdslLineMCMConfProfileTable
- vdslLineMCMConfProfileTable
- vdslLineMCMConfProfileTxBandTable - vdslLineMCMConfProfileTxBandTable
- vdslLineMCMConfProfileRxBandTable - vdslLineMCMConfProfileRxBandTable
- vdslLineMCMConfProfileTxPSDTable - vdslLineMCMConfProfileTxPSDTable
- vdslLineMCMConfProfileMaxTxPSDTable - vdslLineMCMConfProfileMaxTxPSDTable
- vdslLineMCMConfProfileMaxRxPSDTable - vdslLineMCMConfProfileMaxRxPSDTable
Objects in this group MUST be implemented for MCM VDSL lines. Objects in this group MUST be implemented for MCM VDSL lines.
o vdslSCMGroup : o vdslSCMGroup :
This group supports MIB objects for defining configuration profiles This group supports MIB objects for defining configuration profiles
for Single Carrier Modulation (SCM) VDSL modems. It contains the for Single Carrier Modulation (SCM) VDSL modems. It contains the
following tables: following tables:
- vdslLineSCMConfProfileTable - vdslLineSCMConfProfileTable
- vdslLineSCMConfProfileTxBandTable
This group also supports the following line code dependent tables:
- vdslSCMPhysBandTable
Objects in this group MUST be implemented for SCM VDSL lines. Objects in this group MUST be implemented for SCM VDSL lines.
4.3.1 Line Topology Figure 2, below, displays the relationship of the tables in the
vdslGroup to ifEntry (and each other):
ifEntry(ifType=97) ----> vdslLineTableEntry 1:(0..1)
vdslLineTableEntry ----> vdslPhysTableEntry 1:(0..2)
----> vdslPerfDataEntry 1:(0..2)
----> vdslLineConfProfileEntry 1:(0..1)
----> vdslLineAlarmConfProfileEntry 1:(0..1)
vdslPhysTableEntry ----> vdslPerfIntervalEntry 1:(0..96)
----> vdslPerf1DayIntervalEntry 1:(0..30)
ifEntry(ifType=124) ----> vdslChanEntry 1:(0..2)
----> vdslChanPerfDataEntry 1:(0..2)
ifEntry(ifType=125) ----> vdslChanEntry 1:(0..2)
----> vdslChanPerfDataEntry 1:(0..2)
vdslChanEntry ----> vdslchanPerfIntervalEntry 1:(0..96)
----> vdslchan1DayPerfIntervalEntry 1:(0..30)
Figure 2: Table Relationships
2.3.1 Line Topology
A VDSL Line consists of a two units - Vtuc (the central termination A VDSL Line consists of a two units - Vtuc (the central termination
unit) and a Vtur (the remote termination unit). unit) and a Vtur (the remote termination unit).
<-- Network Side Customer Side --> <-- Network Side Customer Side -->
|<////////// VDSL Line ///////////>| |<////////// VDSL Line ///////////>|
+-------+ +-------+ +-------+ +-------+
| | | | | | | |
| Vtuc +------------------+ Vtur | | Vtuc +------------------+ Vtur |
| | | | | | | |
+-------+ +-------+ +-------+ +-------+
Figure 2: General topology for a VDSL Line Figure 3: General topology for a VDSL Line
4.4. Counters, Interval Buckets and Thresholds 2.4 Counters, Interval Buckets and Thresholds
For Loss of Frame (lof), Loss of Link (lol), Loss of Signal (los), For Loss of Frame (lof), Loss of Link (lol), Loss of Signal (los),
and Loss of Power (lpr), there are event counters, current 15-minute and Loss of Power (lpr), Errored Seconds (ES), Severely Errored
and 0 to 96 15-minute history bucket(s) of "interval-counters". Seconds (SES), and Unavailable Seconds (UAS) there are event counters,
Each current 15-minute event bucket has an associated threshold current 15-minute, 0 to 96 15-minute history bucket(s), and 0 to 30
notification. 1-day history bucket(s) of "interval-counters". Each current
15-minute event bucket has an associated threshold notification.
Each of these counters uses the textual conventions defined in the Each of these counters uses the textual conventions defined in the
HC-PerfHist-TC-MIB. The HC-PerfHist-TC-MIB is a work-in-progress, HC-PerfHist-TC-MIB. The HC-PerfHist-TC-MIB is a work-in-progress,
but simply defines 64-bit versions of the textual conventions but simply defines 64-bit versions of the textual conventions
found in RFC 2493 [21]. found in RFC 2493 [RFC2493].
Unlike RFC 2493 [21] and RFC 2662 [22], there is no representation
in the MIB for invalid buckets. In those cases where the data for
an interval is suspect or known to be invalid, the agent MUST NOT
report the interval. If the current 15-minute event bucket is
determined to be invalid, notifications based upon the value of the
event bucket MUST NOT be generated.
Not reporting an interval will result in holes in the associated
table. For example, the table, vdslPerfIntervalTable, is indexed
by { ifIndex, vdslPhysSide, vdslIntervalNumber }. If interval 12
is determined to be invalid but intervals 11 and 13 are valid, a
Get Next operation on the indices .1.1.11 would return indices
.1.1.13.
There is no requirement for an agent to ensure a fixed relationship There is no requirement for an agent to ensure a fixed relationship
between the start of a fifteen minute and any wall clock; however between the start of a fifteen minute and any wall clock; however
some implementations may align the fifteen minute intervals with some implementations may align the fifteen minute intervals with
quarter hours. Likewise, an implementation may choose to align one quarter hours. Likewise, an implementation may choose to align one
day intervals with the start of a day. day intervals with the start of a day.
Counters are not reset when an Vtu is reinitialized, only when the Counters are not reset when an Vtu is reinitialized, only when the
agent is reset or reinitialized (or under specific request outside agent is reset or reinitialized (or under specific request outside
the scope of this MIB). the scope of this MIB).
4.5. Profiles 2.5 Profiles
As a managed node can handle a large number of Vtus, (e.g., hundreds As a managed node can handle a large number of Vtus, (e.g., hundreds
or perhaps thousands of lines), provisioning every parameter on every or perhaps thousands of lines), provisioning every parameter on every
Vtu may become burdensome. Moreover, most lines are provisioned Vtu 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 makes use of profiles. A profile is a provisioning process, this MIB makes use of profiles. A profile is a
set of parameters that can be shared by multiple lines using the same set of parameters that can be shared by multiple lines using the same
configuration. configuration.
The following profiles are used in this MIB: The following profiles are used in this MIB:
o Line Configuration Profiles - Line configuration profiles contain o Line Configuration Profiles - Line configuration profiles contain
parameters for configuring VDSL lines. They are defined in eight parameters for configuring VDSL lines. They are defined in nine
tables: tables:
- vdslLineConfProfileTable - vdslLineConfProfileTable
- vdslLineMCMConfProfileTable - vdslLineMCMConfProfileTable
- vdslLineMCMConfProfileTxBandTable - vdslLineMCMConfProfileTxBandTable
- vdslLineMCMConfProfileRxBandTable - vdslLineMCMConfProfileRxBandTable
- vdslLineMCMConfProfileTxPSDTable - vdslLineMCMConfProfileTxPSDTable
- vdslLineMCMConfProfileMaxTxPSDTable - vdslLineMCMConfProfileMaxTxPSDTable
- vdslLineMCMConfProfileMaxRxPSDTable - vdslLineMCMConfProfileMaxRxPSDTable
- vdslLineSCMConfProfileTable - vdslLineSCMConfProfileTable
- vdslLineSCMConfProfileTxBandTable
As noted above, the latter seven tables in the above list are As noted above, the latter eight tables in the above list are
line code specific. line code specific.
The object, vdslLineConfProfileIndex, is used as a common
index for all of the above tables. A profile, then, consists
of the combination of a line code independent configuration
(i.e. an entry in vdslLineConfProfileTable) and a set of line
code dependent configurations (i.e. entries in either
vdslLineMCMConfProfilexxx or vdslLineSCMConfProfilexxx).
o Alarm Configuration Profiles - These profiles contain parameters o Alarm Configuration Profiles - These profiles contain parameters
for configuring alarm thresholds for VDSL modems. These profiles for configuring alarm thresholds for VDSL modems. These profiles
are defined in the vdslLineAlarmConfProfileTable. are defined in the vdslLineAlarmConfProfileTable.
One or more lines may be configured to share parameters of a single One or more lines may be configured to share parameters of a single
profile by setting its vdslLineConfProfile objects to the value of profile by setting its vdslLineConfProfile objects to the value of
this profile. If a change is made to the profile, all lines that this profile. If a change is made to the profile, all lines that
refer to it will be reconfigured to the changed parameters. Before refer to it will be reconfigured to the changed parameters. Before
a profile can be deleted or taken out of service it must be first a profile can be deleted or taken out of service it must be first
unreferenced from all associated lines. unreferenced from all associated lines.
skipping to change at page 9, line 9 skipping to change at line 449
defined in this MIB. defined in this MIB.
Profiles are created, assigned, and deleted dynamically using the Profiles are created, assigned, and deleted dynamically using the
profile name and profile row status in each of the four profile profile name and profile row status in each of the four profile
tables. tables.
Profile changes MUST take effect immediately. These changes MAY Profile changes MUST take effect immediately. These changes MAY
result in a restart (hard reset or soft restart) of the units on the result in a restart (hard reset or soft restart) of the units on the
line. line.
4.6. Notifications 2.6 Notifications
The ability to generate the SNMP notifications coldStart/WarmStart The ability to generate the SNMP notifications coldStart/WarmStart
(per [21]) which are per agent (e.g., per Digital Subscriber Line (per [RFC2863]) which are per agent (e.g., per Digital Subscriber Line
Access Multiplexer, or DSLAM, in such a device), and linkUp/linkDown Access Multiplexer, or DSLAM, in such a device), and linkUp/linkDown
(per [21]) which are per interface (i.e., VDSL line) is required. (per [RFC2863]) which are per interface (i.e., VDSL line) is required.
For Loss of Frame (lof), Loss of Link (lol), Loss of Signal (los),
and Loss of Power (lpr),
A linkDown notification MAY be generated whenever any of lof, lol,
los, or lpr event occurs. The corresponding linkUp notification MAY
be sent when all link failure conditions are cleared.
The notifications defined in this MIB are for initialization failure The notifications defined in this MIB are for initialization failure
and for the threshold crossings associated with the following events: and for the threshold crossings associated with the following events:
lof, lol, los, and lpr. Each threshold has its own enable/threshold lof, lol, los, lpr, ES, SES, and UAS. Each threshold has its own
value. When that value is 0, the notification is disabled. enable/threshold value. When that value is 0, the notification is
disabled.
A linkDown notification MAY be generated whenever any of lof, lol,
los, lpr, ES, SES, or UAS threshold crossing event (as defined
in this MIB) occurs. The corresponding linkUp notification MAY be
sent when all link failure conditions are cleared.
The vdslCurrStatus is a bitmask representing all outstanding error The vdslCurrStatus is a bitmask representing all outstanding error
conditions associated with a particular VDSL modem. Note that since conditions associated with a particular VDSL modem. Note that since
status of remote modems is obtained via the EOC, this information status of remote modems is obtained via the EOC, this information
may be unavailable for units that are unreachable via EOC during a may be unavailable for units that are unreachable via EOC during a
line error condition. Therefore, not all conditions may always be line error condition. Therefore, not all conditions may always be
included in its current status. Notifications corresponding to the included in its current status. Notifications corresponding to the
bit fields in this object are defined. bit fields in this object are defined.
A threshold notification occurs whenever the corresponding current A threshold notification occurs whenever the corresponding current
skipping to change at page 9, line 48 skipping to change at line 487
threshold value. One notification may be sent per interval per threshold value. One notification may be sent per interval per
interface. Since the current 15-minute counter are reset to 0 every interface. Since the current 15-minute counter are reset to 0 every
15 minutes, if the condition persists, the notification may recur as 15 minutes, if the condition persists, the notification may recur as
often as every 15 minutes. For example, to get a notification often as every 15 minutes. For example, to get a notification
whenever a "loss of" event occurs (but at most once every 15 whenever a "loss of" event occurs (but at most once every 15
minutes), set the corresponding threshold to 1. The agent will minutes), set the corresponding threshold to 1. The agent will
generate a notification when the event originally occurs. generate a notification when the event originally occurs.
Note that the Network Management System, or NMS, may receive a Note that the Network Management System, or NMS, may receive a
linkDown notification, as well, if enabled (via linkDown notification, as well, if enabled (via
ifLinkUpDownTrapEnable [23]). At the beginning of the next 15 minute ifLinkUpDownTrapEnable [RFC2863]). At the beginning of the next 15 minute
interval, the counter is reset. When the first second goes by and interval, the counter is reset. When the first second goes by and
the event occurs, the current interval bucket will be 1, which the event occurs, the current interval bucket will be 1, which
equals the threshold and the notification will be sent again. equals the threshold and the notification will be sent again.
5. Conformance and Compliance 2.7 Persistence
Expires December 17, 2002 [PAGE 10]
All objects defined in this MIB which may be set (read-write or
read-create), should be stored persistently. Following is an
exhaustive list of these persistent objects:
vdslLineConfProfile
vdslLineAlarmConfProfile
vdslLineConfProfileIndex
vdslLineConfProfileName
vdslLineConfTargetSnrMgn
vdslLineConfUpstreamTxSpeed
vdslLineConfDownstreamTxSpeed
vdslLineConfUpstreamPboControl
vdslLineConfDownstreamPboControl
vdslLineConfDeploymentScenario
vdslLineConfAdslOccupy
vdslLineConfApplicableStandard
vdslLineConfBandPlan
vdslLineConfBandPlanFx
vdslLineConfBandU0Usage
vdslLineConfUpstreamPsdTemplate
vdslLineConfDownstreamPsdTemplate
vdslLineConfProfileRowStatus
vdslMCMConfProfileTxWindowLength
vdslMCMConfProfileRowStatus
vdslMCMConfProfileTxBandNumber
vdslMCMConfProfileTxBandStart
vdslMCMConfProfileTxBandStop
vdslMCMConfProfileTxBandRowStatus
vdslMCMConfProfileRxBandNumber
vdslMCMConfProfileRxBandStart
vdslMCMConfProfileRxBandStop
vdslMCMConfProfileRxBandRowStatus
vdslMCMConfProfileTxPSDNumber
vdslMCMConfProfileTxPSDTone
vdslMCMConfProfileTxPSDPSD
vdslMCMConfProfileTxPSDRowStatus
vdslMCMConfProfileMaxTxPSDNumber
vdslMCMConfProfileMaxTxPSDTone
vdslMCMConfProfileMaxTxPSDPSD
vdslMCMConfProfileMaxTxPSDRowStatus
vdslMCMConfProfileMaxRxPSDNumber
vdslMCMConfProfileMaxRxPSDTone
vdslMCMConfProfileMaxRxPSDPSD
vdslMCMConfProfileMaxRxPSDRowStatus
vdslSCMConfProfileInterleaveDepth
vdslSCMConfProfileFastCodewordSize
vdslSCMConfProfileTransmitPSDMask
vdslSCMConfProfileBands
vdslSCMConfProfileFastFecSize
vdslSCMConfProfileRowStatus
vdslSCMConfProfileTxBandNumber
vdslSCMConfProfileTxBandTransmitPSDLevel
vdslSCMConfProfileTxBandSymbolRateProfile
Expires December 17, 2002 [PAGE 11]
vdslSCMConfProfileTxBandConstellationSize
vdslSCMConfProfileTxBandCenterFrequency
vdslSCMConfProfileTxBandRowStatus
vdslLineAlarmConfProfileIndex
vdslLineAlarmConfProfileName
vdslThresh15MinLofs
vdslThresh15MinLoss
vdslThresh15MinLprs
vdslThresh15MinESs
vdslThresh15MinSESs
vdslThresh15MinUASs
vdslInitFailureNotificationEnable
vdslLineAlarmConfProfileRowStatus
It should also be noted that interface indices in this MIB are
maintained persistently. VACM data relating to these should be
stored persistently as well.
3. Conformance and Compliance
For VDSL lines, the following group is mandatory: For VDSL lines, the following group is mandatory:
- vdslGroup - vdslGroup
For MCM VDSL lines, the following group is optional: For MCM VDSL lines, the following group is optional:
- vdslSCMGroup - vdslSCMGroup
For SCM VDSL lines, the following group is optional: For SCM VDSL lines, the following group is optional:
- vdslMCMGroup - vdslMCMGroup
6. Definitions 4. Definitions
VDSL-LINE-MIB DEFINITIONS ::= BEGIN VDSL-LINE-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
OBJECT-TYPE, OBJECT-TYPE,
Counter64, Counter64,
Gauge32, Gauge32,
Integer32,
Unsigned32,
NOTIFICATION-TYPE, NOTIFICATION-TYPE,
transmission FROM SNMPv2-SMI transmission FROM SNMPv2-SMI
TEXTUAL-CONVENTION, TEXTUAL-CONVENTION,
RowStatus, RowStatus,
TruthValue FROM SNMPv2-TC TruthValue FROM SNMPv2-TC
HCPerfCurrentCount, HCPerfCurrentCount,
HCPerfIntervalCount FROM HC-PerfHist-TC-MIB HCPerfIntervalCount FROM HC-PerfHist-TC-MIB
MODULE-COMPLIANCE, MODULE-COMPLIANCE,
OBJECT-GROUP, OBJECT-GROUP,
Expires December 17, 2002 [PAGE 12]
NOTIFICATION-GROUP FROM SNMPv2-CONF NOTIFICATION-GROUP FROM SNMPv2-CONF
ifIndex FROM IF-MIB ifIndex FROM IF-MIB
SnmpAdminString FROM SNMP-FRAMEWORK-MIB; SnmpAdminString FROM SNMP-FRAMEWORK-MIB;
vdslMIB MODULE-IDENTITY vdslMIB MODULE-IDENTITY
LAST-UPDATED "200204090000Z" -- April 9, 2002 LAST-UPDATED "200204090000Z" -- April 9, 2002
ORGANIZATION "ADSLMIB Working Group" ORGANIZATION "ADSLMIB Working Group"
CONTACT-INFO "WG-email: adslmib@ietf.org CONTACT-INFO "WG-email: adslmib@ietf.org
Info: https://www1.ietf.org/mailman/listinfo/adslmib Info: https://www1.ietf.org/mailman/listinfo/adslmib
Chair: Mike Sneed Chair: Mike Sneed
Inovia Telecoms Postal: P.O. Box 37324
Postal: 1017 Main Campus Drive Raleigh NC 27627-7324
Raleigh NC 27606 USA Email: sneedmike@hotmail.com
Email: Mike.Sneed@go.ecitele.com
Phone: +1 919 513 1435 Co-editor: Bob Ray
PESA Switching Systems, Inc.
Postal: 330-A Wynn Drive
Huntsville, AL 35805 USA
Email: rray@pesa.com
Phone: +1 256 726 9200 ext. 142
Co-editor: Rajesh Abbi Co-editor: Rajesh Abbi
Alcatel USA Alcatel USA
Postal: 2912 Wake Forest Road Postal: 2912 Wake Forest Road
Raleigh, NC 27609-7860 USA Raleigh, NC 27609-7860 USA
Email: Rajesh.Abbi@usa.alcatel.com Email: Rajesh.Abbi@alcatel.com
Phone: +1 919 850 6194 Phone: +1 919 850 6194
Co-editor: Bob Ray
Email: bob_ray_99@yahoo.com
" "
DESCRIPTION DESCRIPTION
"The MIB module defining objects for the management of a pair of "The MIB module defining objects for the management of a pair of
VDSL modems at each end of the VDSL line. Each such line has VDSL modems at each end of the VDSL line. Each such line has
an entry in an ifTable which may include multiple modem lines. an entry in an ifTable which may include multiple modem lines.
An agent may reside at either end of the VDSL line however the An agent may reside at either end of the VDSL line however the
MIB is designed to require no management communication between MIB is designed to require no management communication between
them beyond that inherent in the low-level VDSL line protocol. them beyond that inherent in the low-level VDSL line protocol.
The agent may monitor and control this protocol for its needs. The agent may monitor and control this protocol for its needs.
skipping to change at page 11, line 31 skipping to change at line 658
ifTable, one for each physical, fast, and interleaved, whose ifTable, one for each physical, fast, and interleaved, whose
ifType values are equal to vdsl(97), fast(125), and ifType values are equal to vdsl(97), fast(125), and
interleaved(124), respectively. The ifStackTable is used to interleaved(124), respectively. The ifStackTable is used to
represent the relationship between the entries. represent the relationship between the entries.
Naming Conventions: Naming Conventions:
Vtuc -- (VTUC) modem at near (Central) end of line Vtuc -- (VTUC) modem at near (Central) end of line
Vtur -- (VTUR) modem at Remote end of line Vtur -- (VTUR) modem at Remote end of line
Vtu -- One of either Vtuc or Vtur Vtu -- One of either Vtuc or Vtur
Curr -- Current Curr -- Current
Expires December 17, 2002 [PAGE 13]
Prev -- Previous Prev -- Previous
Atn -- Attenuation Atn -- Attenuation
ES -- Errored Second. ES -- Errored Second.
LCS -- Line Code Specific LCS -- Line Code Specific
Lof -- Loss of Frame Lof -- Loss of Frame
Lol -- Loss of Link Lol -- Loss of Link
Los -- Loss of Signal Los -- Loss of Signal
Lpr -- Loss of Power Lpr -- Loss of Power
xxxs -- interval of Seconds in which xxx occurs xxxs -- interval of Seconds in which xxx occurs
(e.g., xxx=Lof, Los, Lpr) (e.g., xxx=Lof, Los, Lpr)
Max -- Maximum Max -- Maximum
Mgn -- Margin Mgn -- Margin
Min -- Minimum Min -- Minimum
Psd -- Power Spectral Density Psd -- Power Spectral Density
Snr -- Signal to Noise Ratio Snr -- Signal to Noise Ratio
Tx -- Transmit Tx -- Transmit
Blks -- Blocks, a data unit, see vdslVtuXChanCrcBlockLength Blks -- Blocks
" "
REVISION "200111010000Z" -- November 1, 2001 REVISION "200111010000Z" -- November 1, 2001
DESCRIPTION "Initial draft." DESCRIPTION "Initial draft."
REVISION "200203310000Z" -- March 31, 2002 REVISION "200203310000Z" -- March 31, 2002
DESCRIPTION "Added R. Abbi as co-author." DESCRIPTION "Added R. Abbi as co-author."
REVISION "200204090000Z" -- April 9, 2002 REVISION "200204090000Z" -- April 9, 2002
DESCRIPTION "Removed use of IMPLIED profile indices." DESCRIPTION "Removed use of IMPLIED profile indices."
REVISION "200206160000Z" -- June 16, 2002
DESCRIPTION "Revised per input from DSL Forum."
::= { transmission xxxx } ::= { transmission xxxx }
vdslLineMib OBJECT IDENTIFIER ::= { vdslMIB 1 } vdslLineMib OBJECT IDENTIFIER ::= { vdslMIB 1 }
vdslMibObjects OBJECT IDENTIFIER ::= { vdslLineMib 1 } vdslMibObjects OBJECT IDENTIFIER ::= { vdslLineMib 1 }
-- --
-- textual conventions used in this MIB -- textual conventions used in this MIB
-- --
VdslLineCodingType ::= TEXTUAL-CONVENTION VdslLineCodingType ::= TEXTUAL-CONVENTION
skipping to change at page 12, line 30 skipping to change at line 713
Line Code." Line Code."
SYNTAX INTEGER SYNTAX INTEGER
{ {
other(1), -- none of the following other(1), -- none of the following
mcm(2), -- Multiple Carrier Modulation mcm(2), -- Multiple Carrier Modulation
scm(3) -- Single Carrier Modulation scm(3) -- Single Carrier Modulation
} }
VdslLineEntity ::= TEXTUAL-CONVENTION VdslLineEntity ::= TEXTUAL-CONVENTION
STATUS current STATUS current
Expires December 17, 2002 [PAGE 14]
DESCRIPTION DESCRIPTION
"Identifies a modem as being either Vtuc or Vtur. A "Identifies a modem as being either Vtuc or Vtur. A
VDSL line consists of two modems, a Vtuc and a Vtur." VDSL line consists of two modems, a Vtuc and a Vtur."
SYNTAX INTEGER SYNTAX INTEGER
{ {
vtuc(1), -- central site modem vtuc(1), -- central site modem
vtur(2) -- remote site modem vtur(2) -- remote site modem
} }
-- --
skipping to change at page 13, line 31 skipping to change at line 768
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the VDSL coding type used on this line." "Specifies the VDSL coding type used on this line."
REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec
::= { vdslLineEntry 1 } ::= { vdslLineEntry 1 }
vdslLineType OBJECT-TYPE vdslLineType OBJECT-TYPE
SYNTAX INTEGER SYNTAX INTEGER
{ {
Expires December 17, 2002 [PAGE 15]
noChannel(1), -- no channels exist noChannel(1), -- no channels exist
fastOnly(2), -- fast channel only fastOnly(2), -- fast channel only
slowOnly(3), -- slow channel only slowOnly(3), -- slow channel only
either(4), -- either fast or slow channel exist either(4), -- either fast or slow channel exist
both(5) -- both fast and slow channels exist both(5) -- both fast and slow channels exist
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Defines the type of VDSL physical line "Defines the type of VDSL physical line
skipping to change at page 14, line 33 skipping to change at line 824
SYNTAX SEQUENCE OF VdslPhysEntry SYNTAX SEQUENCE OF VdslPhysEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table provides one row for each Vtu. Each row "This table provides one row for each Vtu. Each row
contains the Physical Layer Parameters table for that contains the Physical Layer Parameters table for that
Vtu. VDSL physical interfaces are those ifEntries where Vtu. VDSL physical interfaces are those ifEntries where
ifType is equal to vdsl(97)." ifType is equal to vdsl(97)."
::= { vdslMibObjects 2 } ::= { vdslMibObjects 2 }
Expires December 17, 2002 [PAGE 16]
vdslPhysEntry OBJECT-TYPE vdslPhysEntry OBJECT-TYPE
SYNTAX VdslPhysEntry SYNTAX VdslPhysEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION "An entry in the vdslPhysTable." DESCRIPTION "An entry in the vdslPhysTable."
INDEX { ifIndex, INDEX { ifIndex,
vdslPhysSide } vdslPhysSide }
::= { vdslPhysTable 1 } ::= { vdslPhysTable 1 }
VdslPhysEntry ::= VdslPhysEntry ::=
SEQUENCE SEQUENCE
{ {
vdslPhysSide VdslLineEntity, vdslPhysSide VdslLineEntity,
vdslInvSerialNumber SnmpAdminString, vdslInvSerialNumber SnmpAdminString,
vdslInvVendorID SnmpAdminString, vdslInvVendorID SnmpAdminString,
vdslInvVersionNumber SnmpAdminString, vdslInvVersionNumber SnmpAdminString,
vdslCurrSnrMgn INTEGER, vdslCurrSnrMgn Integer32,
vdslCurrAtn Gauge32, vdslCurrAtn Gauge32,
vdslCurrStatus BITS, vdslCurrStatus BITS,
vdslCurrOutputPwr INTEGER, vdslCurrOutputPwr Integer32,
vdslCurrAttainableRate Gauge32 vdslCurrAttainableRate Gauge32
} }
vdslPhysSide OBJECT-TYPE vdslPhysSide OBJECT-TYPE
SYNTAX VdslLineEntity SYNTAX VdslLineEntity
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Identifies whether the modem is the Vtuc or Vtur." "Identifies whether the modem is the Vtuc or Vtur."
::= { vdslPhysEntry 1 } ::= { vdslPhysEntry 1 }
vdslInvSerialNumber OBJECT-TYPE vdslInvSerialNumber OBJECT-TYPE
SYNTAX SnmpAdminString(SIZE (0..32)) SYNTAX SnmpAdminString(SIZE (0..32))
skipping to change at page 15, line 28 skipping to change at line 872
vendor equipment." vendor equipment."
REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec
::= { vdslPhysEntry 2 } ::= { vdslPhysEntry 2 }
vdslInvVendorID OBJECT-TYPE vdslInvVendorID OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..16)) SYNTAX SnmpAdminString (SIZE (0..16))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The vendor ID code is a copy of the binary vendor "The vendor ID code is a copy of the binary vendor
identification field defined by the PHY[10] and identification field expressed as readable characters."
expressed as readable characters."
REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec
::= { vdslPhysEntry 3 } ::= { vdslPhysEntry 3 }
vdslInvVersionNumber OBJECT-TYPE vdslInvVersionNumber OBJECT-TYPE
Expires December 17, 2002 [PAGE 17]
SYNTAX SnmpAdminString (SIZE (0..16)) SYNTAX SnmpAdminString (SIZE (0..16))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The vendor specific version number sent by this Vtu "The vendor specific version number sent by this Vtu
as part of the initialization messages. It is a copy as part of the initialization messages. It is a copy
of the binary version number field defined by the of the binary version number field expressed as
PHY[10] and expressed as readable characters." readable characters."
REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec
::= { vdslPhysEntry 4 } ::= { vdslPhysEntry 4 }
vdslCurrSnrMgn OBJECT-TYPE vdslCurrSnrMgn OBJECT-TYPE
SYNTAX INTEGER(-640..640) SYNTAX Integer32(-640..640)
UNITS "tenth dB" UNITS "0.25dB"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Noise Margin as seen by this Vtu with respect to its "Noise Margin as seen by this Vtu with respect to its
received signal in tenth dB." received signal in 0.25dB."
REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec
::= { vdslPhysEntry 5 } ::= { vdslPhysEntry 5 }
vdslCurrAtn OBJECT-TYPE vdslCurrAtn OBJECT-TYPE
SYNTAX Gauge32(0..630) SYNTAX Gauge32(0..630)
UNITS "tenth dB" UNITS "0.25dB"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Measured difference in the total power transmitted by "Measured difference in the total power transmitted by
the peer Vtu and the total power received by this Vtu." the peer Vtu and the total power received by this Vtu."
REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec
::= { vdslPhysEntry 6 } ::= { vdslPhysEntry 6 }
vdslCurrStatus OBJECT-TYPE vdslCurrStatus OBJECT-TYPE
SYNTAX BITS SYNTAX BITS
skipping to change at page 16, line 36 skipping to change at line 933
protocolInitFailure(8), protocolInitFailure(8),
noPeerVtuPresent(9) noPeerVtuPresent(9)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates current state of the Vtu line. This is a "Indicates current state of the Vtu line. This is a
bit-map of possible conditions. The various bit bit-map of possible conditions. The various bit
positions are: positions are:
Expires December 17, 2002 [PAGE 18]
0 noDefect There no defects on the line 0 noDefect There no defects on the line
1 lossOfFraming Vtu failure due to not receiving 1 lossOfFraming Vtu failure due to not receiving
valid frame. valid frame.
2 lossOfSignal Vtu failure due to not receiving 2 lossOfSignal Vtu failure due to not receiving
signal. signal.
3 lossOfPower Vtu failure due to loss of power. 3 lossOfPower Vtu failure due to loss of power.
skipping to change at page 17, line 22 skipping to change at line 973
9 noPeerVtuPresent Vtu failure during initialization 9 noPeerVtuPresent Vtu failure during initialization
due to no activation sequence due to no activation sequence
detected from peer Vtu. detected from peer Vtu.
This is intended to supplement ifOperStatus." This is intended to supplement ifOperStatus."
REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec
::= { vdslPhysEntry 7 } ::= { vdslPhysEntry 7 }
vdslCurrOutputPwr OBJECT-TYPE vdslCurrOutputPwr OBJECT-TYPE
SYNTAX INTEGER (-310..310) SYNTAX Integer32(-310..310)
UNITS "tenth dBm" UNITS "0.25dBm"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Measured total output power transmitted by this ATU. "Measured total output power transmitted by this ATU.
This is the measurement that was reported during This is the measurement that was reported during
the last activation sequence." the last activation sequence."
REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec
::= { vdslPhysEntry 8 } ::= { vdslPhysEntry 8 }
vdslCurrAttainableRate OBJECT-TYPE vdslCurrAttainableRate OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
Expires December 17, 2002 [PAGE 19]
UNITS "bps" UNITS "bps"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the maximum currently attainable data rate "Indicates the maximum currently attainable data rate
by the Vtu. This value will be equal or greater than by the Vtu. This value will be equal or greater than
the current line rate." the current line rate. Note that for SCM, the minimum
and maximum data rates are equal."
REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec
::= { vdslPhysEntry 9 } ::= { vdslPhysEntry 9 }
vdslChanTable OBJECT-TYPE vdslChanTable OBJECT-TYPE
SYNTAX SEQUENCE OF VdslChanEntry SYNTAX SEQUENCE OF VdslChanEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table provides one row for each Vtu channel. "This table provides one row for each Vtu channel.
VDSL channel interfaces are those ifEntries where VDSL channel interfaces are those ifEntries where
skipping to change at page 18, line 34 skipping to change at line 1041
DESCRIPTION DESCRIPTION
"Interleave Delay for this channel. "Interleave Delay for this channel.
Interleave delay applies only to the interleave Interleave delay applies only to the interleave
(slow) channel and defines the mapping (relative (slow) channel and defines the mapping (relative
spacing) between subsequent input bytes at the spacing) between subsequent input bytes at the
interleaver input and their placement in the bit interleaver input and their placement in the bit
stream at the interleaver output. Larger numbers stream at the interleaver output. Larger numbers
provide greater separation between consecutive provide greater separation between consecutive
input bytes in the output bit stream allowing for input bytes in the output bit stream allowing for
Expires December 17, 2002 [PAGE 20]
improved impulse noise immunity at the expense of improved impulse noise immunity at the expense of
payload latency. payload latency.
In the case where the ifType is fast(125), use In the case where the ifType is fast(125), use
noSuchObject." noSuchObject."
REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec
::= { vdslChanEntry 1 } ::= { vdslChanEntry 1 }
vdslChanCrcBlockLength OBJECT-TYPE vdslChanCrcBlockLength OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
skipping to change at page 19, line 23 skipping to change at line 1085
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the vdslPerfDataTable." "An entry in the vdslPerfDataTable."
INDEX { ifIndex, INDEX { ifIndex,
vdslPhysSide } vdslPhysSide }
::= { vdslPerfDataTable 1 } ::= { vdslPerfDataTable 1 }
VdslPerfDataEntry ::= VdslPerfDataEntry ::=
SEQUENCE SEQUENCE
{ {
vdslPerfValidIntervals INTEGER, vdslPerfValidIntervals Unsigned32,
vdslPerfInvalidIntervals INTEGER, vdslPerfInvalidIntervals Unsigned32,
vdslPerfLofs Counter64, vdslPerfLofs Counter64,
vdslPerfLoss Counter64, vdslPerfLoss Counter64,
vdslPerfLprs Counter64, vdslPerfLprs Counter64,
vdslPerfESs Counter64, vdslPerfESs Counter64,
vdslPerfSESs Counter64,
vdslPerfUASs Counter64,
vdslPerfInits Counter64, vdslPerfInits Counter64,
vdslPerfCurr15MinTimeElapsed INTEGER, vdslPerfCurr15MinTimeElapsed Unsigned32,
vdslPerfCurr15MinLofs HCPerfCurrentCount, vdslPerfCurr15MinLofs HCPerfCurrentCount,
Expires December 17, 2002 [PAGE 21]
vdslPerfCurr15MinLoss HCPerfCurrentCount, vdslPerfCurr15MinLoss HCPerfCurrentCount,
vdslPerfCurr15MinLprs HCPerfCurrentCount, vdslPerfCurr15MinLprs HCPerfCurrentCount,
vdslPerfCurr15MinESs HCPerfCurrentCount, vdslPerfCurr15MinESs HCPerfCurrentCount,
vdslPerfCurr15MinInits HCPerfCurrentCount vdslPerfCurr15MinSESs HCPerfCurrentCount,
vdslPerfCurr15MinUASs HCPerfCurrentCount,
vdslPerfCurr15MinInits HCPerfCurrentCount,
vdslPerf1DayValidIntervals Unsigned32,
vdslPerf1DayInvalidIntervals Unsigned32,
vdslPerfCurr1DayTimeElapsed Unsigned32,
vdslPerfCurr1DayLofs Counter64,
vdslPerfCurr1DayLoss Counter64,
vdslPerfCurr1DayLprs Counter64,
vdslPerfCurr1DayESs Counter64,
vdslPerfCurr1DaySESs Counter64,
vdslPerfCurr1DayUASs Counter64,
vdslPerfCurr1DayInits Counter64
} }
vdslPerfValidIntervals OBJECT-TYPE vdslPerfValidIntervals OBJECT-TYPE
SYNTAX INTEGER(0..96) SYNTAX Unsigned32(0..96)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Valid Intervals per xxxValidInterval definition "Valid Intervals per xxxValidInterval definition
found in HC-PerfHist-TC-MIB." found in HC-PerfHist-TC-MIB."
::= { vdslPerfDataEntry 1 } ::= { vdslPerfDataEntry 1 }
vdslPerfInvalidIntervals OBJECT-TYPE vdslPerfInvalidIntervals OBJECT-TYPE
SYNTAX INTEGER(0..96) SYNTAX Unsigned32(0..96)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Invalid Intervals per xxxInvalidInterval definition "Invalid Intervals per xxxInvalidInterval definition
found in HC-PerfHist-TC-MIB." found in HC-PerfHist-TC-MIB."
::= { vdslPerfDataEntry 2 } ::= { vdslPerfDataEntry 2 }
vdslPerfLofs OBJECT-TYPE vdslPerfLofs OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
UNITS "seconds" UNITS "seconds"
skipping to change at page 20, line 20 skipping to change at line 1151
was Loss of Framing." was Loss of Framing."
REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec
::= { vdslPerfDataEntry 3 } ::= { vdslPerfDataEntry 3 }
vdslPerfLoss OBJECT-TYPE vdslPerfLoss OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
Expires December 17, 2002 [PAGE 22]
"Count of seconds since the unit was last reset that there "Count of seconds since the unit was last reset that there
was Loss of Signal." was Loss of Signal."
REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec
::= { vdslPerfDataEntry 4 } ::= { vdslPerfDataEntry 4 }
vdslPerfLprs OBJECT-TYPE vdslPerfLprs OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 20, line 44 skipping to change at line 1177
::= { vdslPerfDataEntry 5 } ::= { vdslPerfDataEntry 5 }
vdslPerfESs OBJECT-TYPE vdslPerfESs OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of Errored Seconds since the unit was last reset. "Count of Errored Seconds since the unit was last reset.
An Errored Second is a one-second interval containing one An Errored Second is a one-second interval containing one
or more crc anomalies, or one or more los defects." or more crc anomalies, or one or more los or lof defects."
REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec
::= { vdslPerfDataEntry 6 } ::= { vdslPerfDataEntry 6 }
vdslPerfSESs OBJECT-TYPE
SYNTAX Counter64
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Count of Severely Errored Seconds since the unit was last
reset."
::= { vdslPerfDataEntry 7 }
vdslPerfUASs OBJECT-TYPE
SYNTAX Counter64
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Count of Unavailable Seconds since the unit was last
reset."
::= { vdslPerfDataEntry 8 }
vdslPerfInits OBJECT-TYPE vdslPerfInits OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
Expires December 17, 2002 [PAGE 23]
"Count of the line initialization attempts since the unit "Count of the line initialization attempts since the unit
was last reset. This count includes both successful and was last reset. This count includes both successful and
failed attempts." failed attempts."
REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec
::= { vdslPerfDataEntry 7 } ::= { vdslPerfDataEntry 9 }
vdslPerfCurr15MinTimeElapsed OBJECT-TYPE vdslPerfCurr15MinTimeElapsed OBJECT-TYPE
SYNTAX INTEGER(0..899) SYNTAX Unsigned32(0..899)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Total elapsed seconds in this interval." "Total elapsed seconds in this interval."
REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec
::= { vdslPerfDataEntry 8 } ::= { vdslPerfDataEntry 10 }
vdslPerfCurr15MinLofs OBJECT-TYPE vdslPerfCurr15MinLofs OBJECT-TYPE
SYNTAX HCPerfCurrentCount SYNTAX HCPerfCurrentCount
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of seconds during this interval that there "Count of seconds during this interval that there
was Loss of Framing." was Loss of Framing."
REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec
::= { vdslPerfDataEntry 9 } ::= { vdslPerfDataEntry 11 }
vdslPerfCurr15MinLoss OBJECT-TYPE vdslPerfCurr15MinLoss OBJECT-TYPE
SYNTAX HCPerfCurrentCount SYNTAX HCPerfCurrentCount
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of seconds during this interval that there "Count of seconds during this interval that there
was Loss of Signal." was Loss of Signal."
REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec
::= { vdslPerfDataEntry 10 } ::= { vdslPerfDataEntry 12 }
vdslPerfCurr15MinLprs OBJECT-TYPE vdslPerfCurr15MinLprs OBJECT-TYPE
SYNTAX HCPerfCurrentCount SYNTAX HCPerfCurrentCount
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of seconds during this interval that there "Count of seconds during this interval that there
was Loss of Power." was Loss of Power."
REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec
::= { vdslPerfDataEntry 11 } ::= { vdslPerfDataEntry 13 }
vdslPerfCurr15MinESs OBJECT-TYPE vdslPerfCurr15MinESs OBJECT-TYPE
SYNTAX HCPerfCurrentCount SYNTAX HCPerfCurrentCount
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
Expires December 17, 2002 [PAGE 24]
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of Errored Seconds during this interval. An Errored "Count of Errored Seconds during this interval. An Errored
Second is a one-second interval containing one or more crc Second is a one-second interval containing one or more crc
anomalies, or one or more los defects." anomalies, or one or more los or lof defects."
REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec
::= { vdslPerfDataEntry 12 } ::= { vdslPerfDataEntry 14 }
vdslPerfCurr15MinSESs OBJECT-TYPE
SYNTAX HCPerfCurrentCount
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Count of Severely Errored Seconds during this interval."
::= { vdslPerfDataEntry 15 }
vdslPerfCurr15MinUASs OBJECT-TYPE
SYNTAX HCPerfCurrentCount
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Count of Unavailable Seconds during this interval."
::= { vdslPerfDataEntry 16 }
vdslPerfCurr15MinInits OBJECT-TYPE vdslPerfCurr15MinInits OBJECT-TYPE
SYNTAX HCPerfCurrentCount SYNTAX HCPerfCurrentCount
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of the line initialization attempts during this "Count of the line initialization attempts during this
interval. This count includes both successful and interval. This count includes both successful and
failed attempts." failed attempts."
REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec
::= { vdslPerfDataEntry 13 } ::= { vdslPerfDataEntry 17 }
vdslPerf1DayValidIntervals OBJECT-TYPE
SYNTAX Unsigned32(0..30)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Valid Intervals per xxxValidInterval definition
found in HC-PerfHist-TC-MIB."
::= { vdslPerfDataEntry 18 }
vdslPerf1DayInvalidIntervals OBJECT-TYPE
SYNTAX Unsigned32(0..30)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Invalid Intervals per xxxInvalidInterval definition
found in HC-PerfHist-TC-MIB."
Expires December 17, 2002 [PAGE 25]
::= { vdslPerfDataEntry 19 }
vdslPerfCurr1DayTimeElapsed OBJECT-TYPE
SYNTAX Unsigned32(0..86399)
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of seconds that have elapsed since the beginning
of the current 1-day interval."
::= { vdslPerfDataEntry 20 }
vdslPerfCurr1DayLofs OBJECT-TYPE
SYNTAX Counter64
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Count of Loss of Framing (LOF) Seconds since the
beginning of the current 1-day interval."
::= { vdslPerfDataEntry 21 }
vdslPerfCurr1DayLoss OBJECT-TYPE
SYNTAX Counter64
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Count of Loss of Signal (LOS) Seconds since the beginning
of the current 1-day interval."
::= { vdslPerfDataEntry 22 }
vdslPerfCurr1DayLprs OBJECT-TYPE
SYNTAX Counter64
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Count of Loss of Power (LPR) Seconds since the beginning
of the current 1-day interval."
::= { vdslPerfDataEntry 23 }
vdslPerfCurr1DayESs OBJECT-TYPE
SYNTAX Counter64
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Count of Errored Seconds (ES) since the beginning
of the current 1-day interval."
::= { vdslPerfDataEntry 24 }
vdslPerfCurr1DaySESs OBJECT-TYPE
Expires December 17, 2002 [PAGE 26]
SYNTAX Counter64
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Count of Severely Errored Seconds (SES) since the
beginning of the current 1-day interval."
::= { vdslPerfDataEntry 25 }
vdslPerfCurr1DayUASs OBJECT-TYPE
SYNTAX Counter64
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Count of Unavailable Seconds (UAS) since the beginning
of the current 1-day interval."
::= { vdslPerfDataEntry 26 }
vdslPerfCurr1DayInits OBJECT-TYPE
SYNTAX Counter64
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Count of the line initialization attempts since the
beginning of the current 1-day interval. This count
includes both successful and failed attempts."
::= { vdslPerfDataEntry 27 }
vdslPerfIntervalTable OBJECT-TYPE vdslPerfIntervalTable OBJECT-TYPE
SYNTAX SEQUENCE OF VdslPerfIntervalEntry SYNTAX SEQUENCE OF VdslPerfIntervalEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table provides one row for each Vtu performance "This table provides one row for each Vtu performance
data collection interval. VDSL physical interfaces are data collection interval. VDSL physical interfaces are
those ifEntries where ifType is equal to vdsl(97)." those ifEntries where ifType is equal to vdsl(97)."
::= { vdslMibObjects 5 } ::= { vdslMibObjects 5 }
skipping to change at page 22, line 43 skipping to change at line 1426
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the vdslPerfIntervalTable." "An entry in the vdslPerfIntervalTable."
INDEX { ifIndex, INDEX { ifIndex,
vdslPhysSide, vdslPhysSide,
vdslIntervalNumber } vdslIntervalNumber }
::= { vdslPerfIntervalTable 1 } ::= { vdslPerfIntervalTable 1 }
VdslPerfIntervalEntry ::= VdslPerfIntervalEntry ::=
SEQUENCE SEQUENCE
Expires December 17, 2002 [PAGE 27]
{ {
vdslIntervalNumber INTEGER, vdslIntervalNumber Unsigned32,
vdslIntervalLofs HCPerfIntervalCount, vdslIntervalLofs HCPerfIntervalCount,
vdslIntervalLoss HCPerfIntervalCount, vdslIntervalLoss HCPerfIntervalCount,
vdslIntervalLprs HCPerfIntervalCount, vdslIntervalLprs HCPerfIntervalCount,
vdslIntervalESs HCPerfIntervalCount, vdslIntervalESs HCPerfIntervalCount,
vdslIntervalSESs HCPerfIntervalCount,
vdslIntervalUASs HCPerfIntervalCount,
vdslIntervalInits HCPerfIntervalCount vdslIntervalInits HCPerfIntervalCount
} }
vdslIntervalNumber OBJECT-TYPE vdslIntervalNumber OBJECT-TYPE
SYNTAX INTEGER(1..96) SYNTAX Unsigned32(1..96)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Performance Data Interval number 1 is the the most "Performance Data Interval number 1 is the the most
recent previous interval; interval 96 is 24 hours ago. recent previous interval; interval 96 is 24 hours ago.
Intervals 2..96 are optional." Intervals 2..96 are optional."
::= { vdslPerfIntervalEntry 1 } ::= { vdslPerfIntervalEntry 1 }
vdslIntervalLofs OBJECT-TYPE vdslIntervalLofs OBJECT-TYPE
SYNTAX HCPerfIntervalCount SYNTAX HCPerfIntervalCount
skipping to change at page 23, line 42 skipping to change at line 1482
SYNTAX HCPerfIntervalCount SYNTAX HCPerfIntervalCount
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of seconds in the interval when there was Loss "Count of seconds in the interval when there was Loss
of Power." of Power."
REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec
::= { vdslPerfIntervalEntry 4 } ::= { vdslPerfIntervalEntry 4 }
Expires December 17, 2002 [PAGE 28]
vdslIntervalESs OBJECT-TYPE vdslIntervalESs OBJECT-TYPE
SYNTAX HCPerfIntervalCount SYNTAX HCPerfIntervalCount
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of Errored Seconds in the interval. An Errored "Count of Errored Seconds (ES) in the interval. An Errored
Second is a one-second interval containing one or more crc Second is a one-second interval containing one or more crc
anomalies, or one or more los defects." anomalies, one or more los or lof defects."
REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec
::= { vdslPerfIntervalEntry 5 } ::= { vdslPerfIntervalEntry 5 }
vdslIntervalSESs OBJECT-TYPE
SYNTAX HCPerfIntervalCount
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Count of Severely Errored Seconds in the interval."
::= { vdslPerfIntervalEntry 6 }
vdslIntervalUASs OBJECT-TYPE
SYNTAX HCPerfIntervalCount
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Count of Unavailable Seconds in the interval."
::= { vdslPerfIntervalEntry 7 }
vdslIntervalInits OBJECT-TYPE vdslIntervalInits OBJECT-TYPE
SYNTAX HCPerfIntervalCount SYNTAX HCPerfIntervalCount
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of the line initialization attempts during this "Count of the line initialization attempts during this
interval. This count includes both successful and interval. This count includes both successful and
failed attempts." failed attempts."
REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec
::= { vdslPerfIntervalEntry 6 } ::= { vdslPerfIntervalEntry 8 }
vdsl1DayIntervalTable OBJECT-TYPE
SYNTAX SEQUENCE OF Vdsl1DayIntervalEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table provides one row for each VDSL performance
data collection interval. This table contains live data
from equipment. As such, it is NOT persistent."
::= { vdslMibObjects 6 }
vdsl1DayIntervalEntry OBJECT-TYPE
Expires December 17, 2002 [PAGE 29]
SYNTAX Vdsl1DayIntervalEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the vdsl1DayIntervalTable."
INDEX { ifIndex,
vdslPhysSide,
vdsl1DayIntervalNumber }
::= { vdsl1DayIntervalTable 1 }
Vdsl1DayIntervalEntry ::=
SEQUENCE
{
vdsl1DayIntervalNumber Unsigned32,
vdsl1DayIntervalMoniSecs Unsigned32,
vdsl1DayIntervalLofs Counter64,
vdsl1DayIntervalLoss Counter64,
vdsl1DayIntervalLprs Counter64,
vdsl1DayIntervalESs Counter64,
vdsl1DayIntervalSESs Counter64,
vdsl1DayIntervalUASs Counter64,
vdsl1DayIntervalInits Counter64
}
vdsl1DayIntervalNumber OBJECT-TYPE
SYNTAX Unsigned32(1..30)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"History Data Interval number. Interval 1 is the the most
recent previous day; interval 30 is 30 days ago. Intervals
2..30 are optional."
::= { vdsl1DayIntervalEntry 1 }
vdsl1DayIntervalMoniSecs OBJECT-TYPE
SYNTAX Unsigned32(0..86400)
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The amount of time in the 1-day interval over which the
performance monitoring information is actually counted.
This value will be the same as the interval duration except
in a situation where performance monitoring data could not
be collected for any reason."
::= { vdsl1DayIntervalEntry 2 }
vdsl1DayIntervalLofs OBJECT-TYPE
SYNTAX Counter64
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
Expires December 17, 2002 [PAGE 30]
"Count of Loss of Frame (LOF) Seconds during the 1-day
interval as measured by vdsl1DayIntervalMoniSecs."
REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec
::= { vdsl1DayIntervalEntry 3 }
vdsl1DayIntervalLoss OBJECT-TYPE
SYNTAX Counter64
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Count of Loss of Signal (LOS) Seconds during the 1-day
interval as measured by vdsl1DayIntervalMoniSecs."
REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec
::= { vdsl1DayIntervalEntry 4 }
vdsl1DayIntervalLprs OBJECT-TYPE
SYNTAX Counter64
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Count of Loss of Power (LPR) Seconds during the 1-day
interval as measured by vdsl1DayIntervalMoniSecs."
REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec
::= { vdsl1DayIntervalEntry 5 }
vdsl1DayIntervalESs OBJECT-TYPE
SYNTAX Counter64
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Count of Errored Seconds (ES) during the 1-day
interval as measured by vdsl1DayIntervalMoniSecs."
REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec
::= { vdsl1DayIntervalEntry 6 }
vdsl1DayIntervalSESs OBJECT-TYPE
SYNTAX Counter64
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Count of Severely Errored Seconds (SES) during the 1-day
interval as measured by vdsl1DayIntervalMoniSecs."
::= { vdsl1DayIntervalEntry 7 }
vdsl1DayIntervalUASs OBJECT-TYPE
SYNTAX Counter64
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
Expires December 17, 2002 [PAGE 31]
DESCRIPTION
"Count of Unavailable Seconds (UAS) during the 1-day
interval as measured by vdsl1DayIntervalMoniSecs."
::= { vdsl1DayIntervalEntry 8 }
vdsl1DayIntervalInits OBJECT-TYPE
SYNTAX Counter64
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Count of the line initialization attempts during the
1-day interval as measured by vdsl1DayIntervalMoniSecs.
This count includes both successful and failed attempts."
REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec
::= { vdsl1DayIntervalEntry 9 }
vdslChanPerfDataTable OBJECT-TYPE vdslChanPerfDataTable OBJECT-TYPE
SYNTAX SEQUENCE OF VdslChanPerfDataEntry SYNTAX SEQUENCE OF VdslChanPerfDataEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table provides one row for each Vtu channel. "This table provides one row for each Vtu channel.
VDSL channel interfaces are those ifEntries where VDSL channel interfaces are those ifEntries where
ifType is equal to interleave(124) or fast(125)." ifType is equal to interleave(124) or fast(125)."
::= { vdslMibObjects 6 } ::= { vdslMibObjects 7 }
vdslChanPerfDataEntry OBJECT-TYPE vdslChanPerfDataEntry OBJECT-TYPE
SYNTAX VdslChanPerfDataEntry SYNTAX VdslChanPerfDataEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the vdslChanPerfDataTable." "An entry in the vdslChanPerfDataTable."
INDEX { ifIndex, INDEX { ifIndex,
vdslPhysSide } vdslPhysSide }
::= { vdslChanPerfDataTable 1 } ::= { vdslChanPerfDataTable 1 }
VdslChanPerfDataEntry ::= VdslChanPerfDataEntry ::=
SEQUENCE SEQUENCE
{ {
vdslChanPerfValidIntervals INTEGER, vdslChanPerfValidIntervals Unsigned32,
vdslChanPerfInvalidIntervals INTEGER, vdslChanPerfInvalidIntervals Unsigned32,
vdslChanCorrectedOctets Counter64, vdslChanCorrectedOctets Counter64,
vdslChanUncorrectBlks Counter64, vdslChanUncorrectBlks Counter64,
vdslChanPerfCurr15MinTimeElapsed INTEGER, vdslChanPerfCurr15MinTimeElapsed Unsigned32,
vdslChanPerfCurr15MinCorrectedOctets HCPerfCurrentCount, vdslChanPerfCurr15MinCorrectedOctets HCPerfCurrentCount,
vdslChanPerfCurr15MinUncorrectBlks HCPerfCurrentCount vdslChanPerfCurr15MinUncorrectBlks HCPerfCurrentCount,
vdslChanPerf1DayValidIntervals Unsigned32,
vdslChanPerf1DayInvalidIntervals Unsigned32,
vdslChanPerfCurr1DayTimeElapsed Unsigned32,
vdslChanPerfCurr1DayCorrectedOctets HCPerfCurrentCount,
vdslChanPerfCurr1DayUncorrectBlks HCPerfCurrentCount
} }
Expires December 17, 2002 [PAGE 32]
vdslChanPerfValidIntervals OBJECT-TYPE vdslChanPerfValidIntervals OBJECT-TYPE
SYNTAX INTEGER(0..96) SYNTAX Unsigned32(0..96)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Valid Intervals per xxxValidInterval definition "Valid Intervals per xxxValidInterval definition
found in HC-PerfHist-TC-MIB." found in HC-PerfHist-TC-MIB."
::= { vdslChanPerfDataEntry 1 } ::= { vdslChanPerfDataEntry 1 }
vdslChanPerfInvalidIntervals OBJECT-TYPE vdslChanPerfInvalidIntervals OBJECT-TYPE
SYNTAX INTEGER(0..96) SYNTAX Unsigned32(0..96)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Invalid Intervals per xxxInvalidInterval definition "Invalid Intervals per xxxInvalidInterval definition
found in HC-PerfHist-TC-MIB." found in HC-PerfHist-TC-MIB."
::= { vdslChanPerfDataEntry 2 } ::= { vdslChanPerfDataEntry 2 }
vdslChanCorrectedOctets OBJECT-TYPE vdslChanCorrectedOctets OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 25, line 28 skipping to change at line 1739
vdslChanUncorrectBlks OBJECT-TYPE vdslChanUncorrectBlks OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of uncorrected blocks since the unit was last reset." "Count of uncorrected blocks since the unit was last reset."
REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec
::= { vdslChanPerfDataEntry 4 } ::= { vdslChanPerfDataEntry 4 }
vdslChanPerfCurr15MinTimeElapsed OBJECT-TYPE vdslChanPerfCurr15MinTimeElapsed OBJECT-TYPE
SYNTAX INTEGER(0..899) SYNTAX Unsigned32(0..899)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Total elapsed seconds in this interval." "Total elapsed seconds in this interval."
::= { vdslChanPerfDataEntry 5 } ::= { vdslChanPerfDataEntry 5 }
vdslChanPerfCurr15MinCorrectedOctets OBJECT-TYPE vdslChanPerfCurr15MinCorrectedOctets OBJECT-TYPE
SYNTAX HCPerfCurrentCount SYNTAX HCPerfCurrentCount
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of corrected octets in this interval." "Count of corrected octets in this interval."
REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec
Expires December 17, 2002 [PAGE 33]
::= { vdslChanPerfDataEntry 6 } ::= { vdslChanPerfDataEntry 6 }
vdslChanPerfCurr15MinUncorrectBlks OBJECT-TYPE vdslChanPerfCurr15MinUncorrectBlks OBJECT-TYPE
SYNTAX HCPerfCurrentCount SYNTAX HCPerfCurrentCount
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of uncorrected blocks in this interval." "Count of uncorrected blocks in this interval."
REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec
::= { vdslChanPerfDataEntry 7 } ::= { vdslChanPerfDataEntry 7 }
vdslChanPerf1DayValidIntervals OBJECT-TYPE
SYNTAX Unsigned32(0..30)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Valid Intervals per xxxValidInterval definition
found in HC-PerfHist-TC-MIB."
::= { vdslChanPerfDataEntry 8 }
vdslChanPerf1DayInvalidIntervals OBJECT-TYPE
SYNTAX Unsigned32(0..30)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Invalid Intervals per xxxInvalidInterval definition
found in HC-PerfHist-TC-MIB."
::= { vdslChanPerfDataEntry 9 }
vdslChanPerfCurr1DayTimeElapsed OBJECT-TYPE
SYNTAX Unsigned32(0..86399)
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of seconds that have elapsed since the beginning
of the current 1-day interval."
::= { vdslChanPerfDataEntry 10 }
vdslChanPerfCurr1DayCorrectedOctets OBJECT-TYPE
SYNTAX HCPerfCurrentCount
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Count of corrected octets since the beginning of the
current 1-day interva."
REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec
::= { vdslChanPerfDataEntry 11 }
vdslChanPerfCurr1DayUncorrectBlks OBJECT-TYPE
SYNTAX HCPerfCurrentCount
MAX-ACCESS read-only
STATUS current
Expires December 17, 2002 [PAGE 34]
DESCRIPTION
"Count of uncorrected blocks since the beginning of the
current 1-day interva."
REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec
::= { vdslChanPerfDataEntry 12 }
vdslChanIntervalTable OBJECT-TYPE vdslChanIntervalTable OBJECT-TYPE
SYNTAX SEQUENCE OF VdslChanIntervalEntry SYNTAX SEQUENCE OF VdslChanIntervalEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table provides one row for each Vtu channel data "This table provides one row for each Vtu channel data
collection interval. VDSL channel interfaces are those collection interval. VDSL channel interfaces are those
ifEntries where ifType is equal to interleave(124) or ifEntries where ifType is equal to interleave(124) or
fast(125)." fast(125)."
::= { vdslMibObjects 7 } ::= { vdslMibObjects 8 }
vdslChanIntervalEntry OBJECT-TYPE vdslChanIntervalEntry OBJECT-TYPE
SYNTAX VdslChanIntervalEntry SYNTAX VdslChanIntervalEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the vdslChanIntervalTable." "An entry in the vdslChanIntervalTable."
INDEX { ifIndex, INDEX { ifIndex,
vdslPhysSide, vdslPhysSide,
vdslChanIntervalNumber } vdslChanIntervalNumber }
::= { vdslChanIntervalTable 1 } ::= { vdslChanIntervalTable 1 }
VdslChanIntervalEntry ::= VdslChanIntervalEntry ::=
SEQUENCE SEQUENCE
{ {
vdslChanIntervalNumber INTEGER, vdslChanIntervalNumber Unsigned32,
vdslChanIntervalCorrectedOctets HCPerfIntervalCount, vdslChanIntervalCorrectedOctets HCPerfIntervalCount,
vdslChanIntervalUncorrectBlks HCPerfIntervalCount vdslChanIntervalUncorrectBlks HCPerfIntervalCount
} }
vdslChanIntervalNumber OBJECT-TYPE vdslChanIntervalNumber OBJECT-TYPE
SYNTAX INTEGER(1..96) SYNTAX Unsigned32(0..96)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Performance Data Interval number 1 is the the most "Performance Data Interval number 1 is the the most
recent previous interval; interval 96 is 24 hours ago. recent previous interval; interval 96 is 24 hours ago.
Intervals 2..96 are optional." Intervals 2..96 are optional."
::= { vdslChanIntervalEntry 1 } ::= { vdslChanIntervalEntry 1 }
vdslChanIntervalCorrectedOctets OBJECT-TYPE vdslChanIntervalCorrectedOctets OBJECT-TYPE
SYNTAX HCPerfIntervalCount SYNTAX HCPerfIntervalCount
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of corrected octets in this interval." "Count of corrected octets in this interval."
REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec
Expires December 17, 2002 [PAGE 35]
::= { vdslChanIntervalEntry 2 } ::= { vdslChanIntervalEntry 2 }
vdslChanIntervalUncorrectBlks OBJECT-TYPE vdslChanIntervalUncorrectBlks OBJECT-TYPE
SYNTAX HCPerfIntervalCount SYNTAX HCPerfIntervalCount
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of uncorrected blocks in this interval." "Count of uncorrected blocks in this interval."
REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec
::= { vdslChanIntervalEntry 3 } ::= { vdslChanIntervalEntry 3 }
vdslChan1DayIntervalTable OBJECT-TYPE
SYNTAX SEQUENCE OF VdslChan1DayIntervalEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table provides one row for each VDSL performance
data collection interval. This table contains live data
from equipment. As such, it is NOT persistent."
::= { vdslMibObjects 9 }
vdslChan1DayIntervalEntry OBJECT-TYPE
SYNTAX VdslChan1DayIntervalEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the vdslChan1DayIntervalTable."
INDEX { ifIndex,
vdslPhysSide,
vdslChan1DayIntervalNumber }
::= { vdslChan1DayIntervalTable 1 }
VdslChan1DayIntervalEntry ::=
SEQUENCE
{
vdslChan1DayIntervalNumber Unsigned32,
vdslChan1DayIntervalMoniSecs Unsigned32,
vdslChan1DayIntervalCorrectedOctets HCPerfCurrentCount,
vdslChan1DayIntervalUncorrectBlks HCPerfCurrentCount
}
vdslChan1DayIntervalNumber OBJECT-TYPE
SYNTAX Unsigned32(1..30)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"History Data Interval number. Interval 1 is the the most
recent previous day; interval 30 is 30 days ago. Intervals
2..30 are optional."
::= { vdslChan1DayIntervalEntry 1 }
vdslChan1DayIntervalMoniSecs OBJECT-TYPE
SYNTAX Unsigned32(0..86400)
Expires December 17, 2002 [PAGE 36]
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The amount of time in the 1-day interval over which the
performance monitoring information is actually counted.
This value will be the same as the interval duration except
in a situation where performance monitoring data could not
be collected for any reason."
::= { vdslChan1DayIntervalEntry 2 }
vdslChan1DayIntervalCorrectedOctets OBJECT-TYPE
SYNTAX HCPerfCurrentCount
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Count of corrected octets in this interval."
REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec
::= { vdslChan1DayIntervalEntry 3 }
vdslChan1DayIntervalUncorrectBlks OBJECT-TYPE
SYNTAX HCPerfCurrentCount
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Count of uncorrected blocks in this interval."
REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec
::= { vdslChan1DayIntervalEntry 4 }
--
-- SCM physical band status
--
vdslSCMPhysBandTable OBJECT-TYPE
SYNTAX SEQUENCE OF VdslSCMPhysBandEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table provides one row for each SCM Vtu band."
::= { vdslMibObjects 10 }
vdslSCMPhysBandEntry OBJECT-TYPE
SYNTAX VdslSCMPhysBandEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the vdslSCMPhysBandTable."
INDEX { ifIndex,
vdslPhysSide,
vdslSCMPhysTxBandNumber }
::= { vdslSCMPhysBandTable 1 }
VdslSCMPhysBandEntry ::=
Expires December 17, 2002 [PAGE 37]
SEQUENCE
{
vdslSCMPhysTxBandNumber INTEGER,
vdslSCMPhysBandSnrMgn Integer32,
vdslSCMPhysBandAtn Unsigned32
}
vdslSCMPhysTxBandNumber OBJECT-TYPE
SYNTAX INTEGER
{
band1(1),
band2(2),
upstreamU0(3)
}
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The SCM transmit band number for this entry."
::= { vdslSCMPhysBandEntry 1 }
vdslSCMPhysBandSnrMgn OBJECT-TYPE
SYNTAX Integer32(-127..127)
UNITS "0.25 dB"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Noise margin as seen by this Vtu and band with respect
to its received signal in 0.25 dB."
::= { vdslSCMPhysBandEntry 2 }
vdslSCMPhysBandAtn OBJECT-TYPE
SYNTAX Unsigned32(0..255)
UNITS "0.25 dB"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Measured difference in the total power transmitted by
the peer Vtu on this band and the total power received
by this Vtu on this band in 0.25 dB."
::= { vdslSCMPhysBandEntry 3 }
--
-- profile tables
--
vdslLineConfProfileTable OBJECT-TYPE vdslLineConfProfileTable OBJECT-TYPE
SYNTAX SEQUENCE OF VdslLineConfProfileEntry SYNTAX SEQUENCE OF VdslLineConfProfileEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains information on the VDSL line "This table contains information on the VDSL line
configuration. One entry in this table reflects a configuration. One entry in this table reflects a
profile defined by a manager which can be used to profile defined by a manager which can be used to
Expires December 17, 2002 [PAGE 38]
configure the VDSL line." configure the VDSL line."
::= { vdslMibObjects 8 } ::= { vdslMibObjects 11 }
vdslLineConfProfileEntry OBJECT-TYPE vdslLineConfProfileEntry OBJECT-TYPE
SYNTAX VdslLineConfProfileEntry SYNTAX VdslLineConfProfileEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each entry consists of a list of parameters that "Each entry consists of a list of parameters that
represents the configuration of a VDSL modem. A represents the configuration of a VDSL line. A
default profile with an index of 1 will always exist default profile with an index of 1 will always exist
and its parameters will be set to vendor specific and its parameters will be set to vendor specific
values, unless otherwise specified in this document." values, unless otherwise specified in this document."
INDEX { vdslLineConfProfileNameIndex, INDEX { vdslLineConfProfileIndex }
vdslPhysSide }
::= { vdslLineConfProfileTable 1 } ::= { vdslLineConfProfileTable 1 }
VdslLineConfProfileEntry ::= VdslLineConfProfileEntry ::=
SEQUENCE SEQUENCE
{ {
vdslLineConfProfileIndex Integer32, vdslLineConfProfileIndex Unsigned32,
vdslLineConfProfileName SnmpAdminString, vdslLineConfProfileName SnmpAdminString,
vdslLineConfTargetSnrMgn INTEGER, vdslLineConfTargetSnrMgn Unsigned32,
vdslLineConfTxSpeed INTEGER, vdslLineConfUpstreamTxSpeed Unsigned32,
vdslLineConfRxSpeed INTEGER, vdslLineConfDownstreamTxSpeed Unsigned32,
vdslLineConfUpstreamPboControl INTEGER,
vdslLineConfDownstreamPboControl INTEGER,
vdslLineConfDeploymentScenario INTEGER,
vdslLineConfAdslOccupy TruthValue,
vdslLineConfApplicableStandard INTEGER,
vdslLineConfBandPlan INTEGER,
vdslLineConfBandPlanFx Unsigned32,
vdslLineConfBandU0Usage INTEGER,
vdslLineConfUpstreamPsdTemplate INTEGER,
vdslLineConfDownstreamPsdTemplate INTEGER,
vdslLineConfProfileRowStatus RowStatus vdslLineConfProfileRowStatus RowStatus
} }
vdslLineConfProfileIndex OBJECT-TYPE vdslLineConfProfileIndex OBJECT-TYPE
SYNTAX Integer32 SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is used by the line configuration table "This object identifies a row in this table. A
in order to identify a row in that table. The system default profile with an index of 1 MUST always
will always provide a default profile whose value is 1." exist and its parameters will be set to vendor
specific values, unless otherwise specified in
this document."
::= { vdslLineConfProfileEntry 1 } ::= { vdslLineConfProfileEntry 1 }
vdslLineConfProfileName OBJECT-TYPE vdslLineConfProfileName OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (1..32)) SYNTAX SnmpAdminString (SIZE (1..32))
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
Expires December 17, 2002 [PAGE 39]
DESCRIPTION DESCRIPTION
"The name for this profile as specified by a user." "The name for this profile as specified by a user."
::= { vdslLineConfProfileEntry 2 } ::= { vdslLineConfProfileEntry 2 }
vdslLineConfTargetSnrMgn OBJECT-TYPE vdslLineConfTargetSnrMgn OBJECT-TYPE
SYNTAX INTEGER (0..310) SYNTAX Unsigned32(0..310)
UNITS "tenth dB" UNITS "0.25dB"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Configured Target Signal/Noise Margin. This is the "Configured Target Signal/Noise Margin. This is the
Noise Margin the modem must achieve with a BER of 10-7 Noise Margin the modems must achieve with a BER of 10-7
or better to successfully complete initialization." or better to successfully complete initialization."
REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec
::= { vdslLineConfProfileEntry 3 } ::= { vdslLineConfProfileEntry 3 }
vdslLineConfTxSpeed OBJECT-TYPE vdslLineConfUpstreamTxSpeed OBJECT-TYPE
SYNTAX INTEGER SYNTAX Unsigned32
UNITS "bits per second" UNITS "bits per second"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Transmit speed for this modem. The corresponding modem "Upstream transmit speed for this line."
on the other end of the VDSL line will have an equal
vdslLineConfRxSpeed value."
REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec
::= { vdslLineConfProfileEntry 4 } ::= { vdslLineConfProfileEntry 4 }
vdslLineConfRxSpeed OBJECT-TYPE vdslLineConfDownstreamTxSpeed OBJECT-TYPE
SYNTAX INTEGER SYNTAX Unsigned32
UNITS "bits per second" UNITS "bits per second"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Receive speed for this modem. The corresponding modem "Downstream transmit speed for this line."
on the other end of the VDSL line will have an equal
vdslLineConfTxSpeed value."
REFERENCE "T1E1.4/2000-009R3" -- Part 1, common spec
::= { vdslLineConfProfileEntry 5 } ::= { vdslLineConfProfileEntry 5 }
vdslLineConfUpstreamPboControl OBJECT-TYPE
SYNTAX INTEGER
{
disabled(1),
enabled(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Upstream power backoff (PBO) control for this
line. For modems which do not support upstream
PBO control, this object MUST be fixed at disabled(1)."
::= { vdslLineConfProfileEntry 6 }
vdslLineConfDownstreamPboControl OBJECT-TYPE
SYNTAX INTEGER
{
disabled(1),
enabled(2)
Expires December 17, 2002 [PAGE 40]
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Downstream power backoff (PBO) control for this
line. For modems which do not support downstream
PBO control, this object MUST be fixed at disabled(1)."
::= { vdslLineConfProfileEntry 7 }
vdslLineConfDeploymentScenario OBJECT-TYPE
SYNTAX INTEGER
{
fttCab(1),
fttEx(2),
other(3)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The VDSL line deployment scenario. When using
fttCab(1), the VTU-C is located in a street cabinet.
When using fttEx(2), the VTU-C is located at the
central office."
::= { vdslLineConfProfileEntry 8 }
vdslLineConfAdslOccupy OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Indicates if the VDSL line can occupy the ADSL
frequency range."
::= { vdslLineConfProfileEntry 9 }
vdslLineConfApplicableStandard OBJECT-TYPE
SYNTAX INTEGER
{
ansi(1),
etsi(2),
itu(3),
other(4)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The VDSL standard to be used for the line."
::= { vdslLineConfProfileEntry 10 }
vdslLineConfBandPlan OBJECT-TYPE
SYNTAX INTEGER
{
bandPlan997(1),
bandPlan998(2),
Expires December 17, 2002 [PAGE 41]
bandPlanFx(3),
other(4)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The VDSL band plan to be used for the line."
::= { vdslLineConfProfileEntry 11 }
vdslLineConfBandPlanFx OBJECT-TYPE
SYNTAX Unsigned32
UNITS "kHz"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The frequency limit between bands D2 and U2 when
vdslLineConfBandPlan is set to bandPlanFx(3)."
::= { vdslLineConfProfileEntry 12 }
vdslLineConfBandU0Usage OBJECT-TYPE
SYNTAX INTEGER
{
unused(1),
upstream(2),
downstream(3)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Defines the VDSL link use of the frequency range
[25kHz - 138kHz] (U0)."
::= { vdslLineConfProfileEntry 13 }
vdslLineConfUpstreamPsdTemplate OBJECT-TYPE
SYNTAX INTEGER
{
templateMask1(1),
templateMask2(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The upstream PSD template to be used for the line."
::= { vdslLineConfProfileEntry 14 }
vdslLineConfDownstreamPsdTemplate OBJECT-TYPE
SYNTAX INTEGER
{
templateMask1(1),
templateMask2(2)
}
MAX-ACCESS read-create
STATUS current
Expires December 17, 2002 [PAGE 42]
DESCRIPTION
"The downstream PSD template to be used for the line."
::= { vdslLineConfProfileEntry 15 }
vdslLineConfProfileRowStatus OBJECT-TYPE vdslLineConfProfileRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is used to create a new row or modify or "This object is used to create a new row or modify or
delete an existing row in this table. delete an existing row in this table.
A profile activated by setting this object to `active'. A profile activated by setting this object to `active'.
When `active' is set, the system will validate the profile. When `active' is set, the system will validate the profile.
Before a profile can be deleted or taken out of Before a profile can be deleted or taken out of
service, (by setting this object to `destroy' or service, (by setting this object to `destroy' or
`outOfService') it must be first unreferenced `outOfService') it must be first unreferenced
from all associated lines." from all associated lines."
::= { vdslLineConfProfileEntry 6 } ::= { vdslLineConfProfileEntry 16 }
-- --
-- Multiple carrier modulation (MCM) configuration profile tables -- Multiple carrier modulation (MCM) configuration profile tables
-- --
vdslLineMCMConfProfileTable OBJECT-TYPE vdslLineMCMConfProfileTable OBJECT-TYPE
SYNTAX SEQUENCE OF VdslLineMCMConfProfileEntry SYNTAX SEQUENCE OF VdslLineMCMConfProfileEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains information on the VDSL line "This table contains information on the VDSL line
configuration. One entry in this table reflects a configuration. One entry in this table reflects a
profile defined by a manager which can be used to profile defined by a manager which can be used to
configure the VDSL line. configure the VDSL line.
This table MUST be implemented for multiple carrier VDSL This table MUST be implemented for multiple carrier VDSL
lines. This table MUST NOT be implemented for Single lines. This table MUST NOT be implemented for Single
carrier VDSL lines." carrier VDSL lines."
::= { vdslMibObjects 9 } ::= { vdslMibObjects 12 }
vdslLineMCMConfProfileEntry OBJECT-TYPE vdslLineMCMConfProfileEntry OBJECT-TYPE
SYNTAX VdslLineMCMConfProfileEntry SYNTAX VdslLineMCMConfProfileEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each entry consists of a list of parameters that "Each entry consists of a list of parameters that
represents the configuration of a multiple carrier represents the configuration of a multiple carrier
modulation VDSL modem. A default profile with an modulation VDSL modem. A default profile with an
index of 1 will always exist and its parameters will index of 1 will always exist and its parameters will
be set to vendor specific values, unless otherwise be set to vendor specific values, unless otherwise
specified in this document." specified in this document."
INDEX { vdslLineConfProfileIndex, INDEX { vdslLineConfProfileIndex }
vdslPhysSide }
::= { vdslLineMCMConfProfileTable 1 } ::= { vdslLineMCMConfProfileTable 1 }
Expires December 17, 2002 [PAGE 43]
VdslLineMCMConfProfileEntry ::= VdslLineMCMConfProfileEntry ::=
SEQUENCE SEQUENCE
{ {
vdslMCMConfProfileTxWindowLength INTEGER, vdslMCMConfProfileTxWindowLength Unsigned32,
vdslMCMConfProfileRowStatus RowStatus vdslMCMConfProfileRowStatus RowStatus
} }
vdslMCMConfProfileTxWindowLength OBJECT-TYPE vdslMCMConfProfileTxWindowLength OBJECT-TYPE
SYNTAX INTEGER(1..255) SYNTAX Unsigned32(1..255)
UNITS "samples" UNITS "samples"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the length of the transmit window, counted "Specifies the length of the transmit window, counted
in samples at the sampling rate corresponding to the in samples at the sampling rate corresponding to the
negotiated value of N." negotiated value of N."
REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM
::= { vdslLineMCMConfProfileEntry 1 } ::= { vdslLineMCMConfProfileEntry 1 }
skipping to change at page 30, line 39 skipping to change at line 2357
"This table contains transmit band descriptor configuration "This table contains transmit band descriptor configuration
information for a VDSL line. Each entry in this table information for a VDSL line. Each entry in this table
reflects the configuration for one of possibly many bands reflects the configuration for one of possibly many bands
with a multiple carrier modulation (MCM) VDSL line. with a multiple carrier modulation (MCM) VDSL line.
These entries are defined by a manager and can be used to These entries are defined by a manager and can be used to
configure the VDSL line. configure the VDSL line.
This table MUST be implemented for multiple carrier This table MUST be implemented for multiple carrier
modulation (MCM) VDSL lines. This table MUST NOT be modulation (MCM) VDSL lines. This table MUST NOT be
implemented for single carrier modulation VDSL lines." implemented for single carrier modulation VDSL lines."
::= { vdslMibObjects 10 } ::= { vdslMibObjects 13 }
Expires December 17, 2002 [PAGE 44]
vdslLineMCMConfProfileTxBandEntry OBJECT-TYPE vdslLineMCMConfProfileTxBandEntry OBJECT-TYPE
SYNTAX VdslLineMCMConfProfileTxBandEntry SYNTAX VdslLineMCMConfProfileTxBandEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each entry consists of a transmit band descriptor, which "Each entry consists of a transmit band descriptor, which
is defined by a start and a stop tone index. is defined by a start and a stop tone index.
A default profile with an index of 1 will always exist and A default profile with an index of 1 will always exist and
its parameters will be set to vendor specific values, its parameters will be set to vendor specific values,
unless otherwise specified in this document." unless otherwise specified in this document."
INDEX { vdslLineConfProfileIndex, INDEX { vdslLineConfProfileIndex,
vdslPhysSide,
vdslMCMConfProfileTxBandNumber } vdslMCMConfProfileTxBandNumber }
::= { vdslLineMCMConfProfileTxBandTable 1 } ::= { vdslLineMCMConfProfileTxBandTable 1 }
VdslLineMCMConfProfileTxBandEntry ::= VdslLineMCMConfProfileTxBandEntry ::=
SEQUENCE SEQUENCE
{ {
vdslMCMConfProfileTxBandNumber INTEGER, vdslMCMConfProfileTxBandNumber Unsigned32,
vdslMCMConfProfileTxBandStart INTEGER, vdslMCMConfProfileTxBandStart Unsigned32,
vdslMCMConfProfileTxBandStop INTEGER, vdslMCMConfProfileTxBandStop Unsigned32,
vdslMCMConfProfileTxBandRowStatus RowStatus vdslMCMConfProfileTxBandRowStatus RowStatus
} }
vdslMCMConfProfileTxBandNumber OBJECT-TYPE vdslMCMConfProfileTxBandNumber OBJECT-TYPE
SYNTAX INTEGER SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The index for this band descriptor entry." "The index for this band descriptor entry."
::= { vdslLineMCMConfProfileTxBandEntry 1 } ::= { vdslLineMCMConfProfileTxBandEntry 1 }
vdslMCMConfProfileTxBandStart OBJECT-TYPE vdslMCMConfProfileTxBandStart OBJECT-TYPE
SYNTAX INTEGER SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Start tone index for this band." "Start tone index for this band."
REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM
::= { vdslLineMCMConfProfileTxBandEntry 2 } ::= { vdslLineMCMConfProfileTxBandEntry 2 }
vdslMCMConfProfileTxBandStop OBJECT-TYPE vdslMCMConfProfileTxBandStop OBJECT-TYPE
SYNTAX INTEGER SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Stop tone index for this band." "Stop tone index for this band."
REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM
::= { vdslLineMCMConfProfileTxBandEntry 3 } ::= { vdslLineMCMConfProfileTxBandEntry 3 }
vdslMCMConfProfileTxBandRowStatus OBJECT-TYPE vdslMCMConfProfileTxBandRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
Expires December 17, 2002 [PAGE 45]
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is used to create a new row or modify or "This object is used to create a new row or modify or
delete an existing row in this table. delete an existing row in this table.
A profile activated by setting this object to `active'. A profile activated by setting this object to `active'.
When `active' is set, the system will validate the profile. When `active' is set, the system will validate the profile.
Before a profile can be deleted or taken out of Before a profile can be deleted or taken out of
skipping to change at page 32, line 18 skipping to change at line 2444
"This table contains receive band descriptor configuration "This table contains receive band descriptor configuration
information for a VDSL line. Each entry in this table information for a VDSL line. Each entry in this table
reflects the configuration for one of possibly many bands reflects the configuration for one of possibly many bands
with a multiple carrier modulation (MCM) VDSL line. with a multiple carrier modulation (MCM) VDSL line.
These entries are defined by a manager and can be used to These entries are defined by a manager and can be used to
configure the VDSL line. configure the VDSL line.
This table MUST be implemented for multiple carrier This table MUST be implemented for multiple carrier
modulation (MCM) VDSL lines. This table MUST NOT be modulation (MCM) VDSL lines. This table MUST NOT be
implemented for single carrier modulation VDSL lines." implemented for single carrier modulation VDSL lines."
::= { vdslMibObjects 11 } ::= { vdslMibObjects 14 }
vdslLineMCMConfProfileRxBandEntry OBJECT-TYPE vdslLineMCMConfProfileRxBandEntry OBJECT-TYPE
SYNTAX VdslLineMCMConfProfileRxBandEntry SYNTAX VdslLineMCMConfProfileRxBandEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each entry consists of a transmit band descriptor, which "Each entry consists of a transmit band descriptor, which
is defined by a start and a stop tone index. is defined by a start and a stop tone index.
A default profile with an index of 1 will always exist and A default profile with an index of 1 will always exist and
its parameters will be set to vendor specific values, its parameters will be set to vendor specific values,
unless otherwise specified in this document." unless otherwise specified in this document."
INDEX { vdslLineConfProfileIndex, INDEX { vdslLineConfProfileIndex,
vdslPhysSide,
vdslMCMConfProfileRxBandNumber } vdslMCMConfProfileRxBandNumber }
::= { vdslLineMCMConfProfileRxBandTable 1 } ::= { vdslLineMCMConfProfileRxBandTable 1 }
VdslLineMCMConfProfileRxBandEntry ::= VdslLineMCMConfProfileRxBandEntry ::=
SEQUENCE SEQUENCE
{ {
vdslMCMConfProfileRxBandNumber INTEGER, vdslMCMConfProfileRxBandNumber Unsigned32,
vdslMCMConfProfileRxBandStart INTEGER, vdslMCMConfProfileRxBandStart Unsigned32,
vdslMCMConfProfileRxBandStop INTEGER, vdslMCMConfProfileRxBandStop Unsigned32,
Expires December 17, 2002 [PAGE 46]
vdslMCMConfProfileRxBandRowStatus RowStatus vdslMCMConfProfileRxBandRowStatus RowStatus
} }
vdslMCMConfProfileRxBandNumber OBJECT-TYPE vdslMCMConfProfileRxBandNumber OBJECT-TYPE
SYNTAX INTEGER SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The index for this band descriptor entry." "The index for this band descriptor entry."
::= { vdslLineMCMConfProfileRxBandEntry 1 } ::= { vdslLineMCMConfProfileRxBandEntry 1 }
vdslMCMConfProfileRxBandStart OBJECT-TYPE vdslMCMConfProfileRxBandStart OBJECT-TYPE
SYNTAX INTEGER SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Start tone index for this band." "Start tone index for this band."
REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM
::= { vdslLineMCMConfProfileRxBandEntry 2 } ::= { vdslLineMCMConfProfileRxBandEntry 2 }
vdslMCMConfProfileRxBandStop OBJECT-TYPE vdslMCMConfProfileRxBandStop OBJECT-TYPE
SYNTAX INTEGER SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Stop tone index for this band." "Stop tone index for this band."
REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM
::= { vdslLineMCMConfProfileRxBandEntry 3 } ::= { vdslLineMCMConfProfileRxBandEntry 3 }
vdslMCMConfProfileRxBandRowStatus OBJECT-TYPE vdslMCMConfProfileRxBandRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
skipping to change at page 33, line 42 skipping to change at line 2522
from all associated lines." from all associated lines."
::= { vdslLineMCMConfProfileRxBandEntry 4 } ::= { vdslLineMCMConfProfileRxBandEntry 4 }
vdslLineMCMConfProfileTxPSDTable OBJECT-TYPE vdslLineMCMConfProfileTxPSDTable OBJECT-TYPE
SYNTAX SEQUENCE OF VdslLineMCMConfProfileTxPSDEntry SYNTAX SEQUENCE OF VdslLineMCMConfProfileTxPSDEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains transmit PSD mask descriptor "This table contains transmit PSD mask descriptor
configuration information for a VDSL line. Each entry in configuration information for a VDSL line. Each entry in
Expires December 17, 2002 [PAGE 47]
this table reflects the configuration for one tone within this table reflects the configuration for one tone within
a multiple carrier modulation (MCM) VDSL line. These a multiple carrier modulation (MCM) VDSL line. These
entries are defined by a manager and can be used to entries are defined by a manager and can be used to
configure the VDSL line. configure the VDSL line.
This table MUST be implemented for multiple carrier This table MUST be implemented for multiple carrier
modulation (MCM) VDSL lines. This table MUST NOT be modulation (MCM) VDSL lines. This table MUST NOT be
implemented for single carrier modulation VDSL lines." implemented for single carrier modulation VDSL lines."
::= { vdslMibObjects 12 } ::= { vdslMibObjects 15 }
vdslLineMCMConfProfileTxPSDEntry OBJECT-TYPE vdslLineMCMConfProfileTxPSDEntry OBJECT-TYPE
SYNTAX VdslLineMCMConfProfileTxPSDEntry SYNTAX VdslLineMCMConfProfileTxPSDEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each entry consists of a transmit PSD mask descriptor, "Each entry consists of a transmit PSD mask descriptor,
which defines the power spectral density (PSD) for a tone. which defines the power spectral density (PSD) for a tone.
A default profile with an index of 1 will always exist and A default profile with an index of 1 will always exist and
its parameters will be set to vendor specific values, its parameters will be set to vendor specific values,
unless otherwise specified in this document." unless otherwise specified in this document."
INDEX { vdslLineConfProfileIndex, INDEX { vdslLineConfProfileIndex,
vdslPhysSide,
vdslMCMConfProfileTxPSDNumber } vdslMCMConfProfileTxPSDNumber }
::= { vdslLineMCMConfProfileTxPSDTable 1 } ::= { vdslLineMCMConfProfileTxPSDTable 1 }
VdslLineMCMConfProfileTxPSDEntry ::= VdslLineMCMConfProfileTxPSDEntry ::=
SEQUENCE SEQUENCE
{ {
vdslMCMConfProfileTxPSDNumber INTEGER, vdslMCMConfProfileTxPSDNumber Unsigned32,
vdslMCMConfProfileTxPSDTone INTEGER, vdslMCMConfProfileTxPSDTone Unsigned32,
vdslMCMConfProfileTxPSDPSD INTEGER, vdslMCMConfProfileTxPSDPSD Unsigned32,
vdslMCMConfProfileTxPSDRowStatus RowStatus vdslMCMConfProfileTxPSDRowStatus RowStatus
} }
vdslMCMConfProfileTxPSDNumber OBJECT-TYPE vdslMCMConfProfileTxPSDNumber OBJECT-TYPE
SYNTAX INTEGER SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The index for this mask descriptor entry." "The index for this mask descriptor entry."
::= { vdslLineMCMConfProfileTxPSDEntry 1 } ::= { vdslLineMCMConfProfileTxPSDEntry 1 }
vdslMCMConfProfileTxPSDTone OBJECT-TYPE vdslMCMConfProfileTxPSDTone OBJECT-TYPE
SYNTAX INTEGER SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The tone index for which the PSD is being specified." "The tone index for which the PSD is being specified."
REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM
::= { vdslLineMCMConfProfileTxPSDEntry 2 } ::= { vdslLineMCMConfProfileTxPSDEntry 2 }
vdslMCMConfProfileTxPSDPSD OBJECT-TYPE vdslMCMConfProfileTxPSDPSD OBJECT-TYPE
SYNTAX INTEGER SYNTAX Unsigned32
Expires December 17, 2002 [PAGE 48]
UNITS "0.5dB" UNITS "0.5dB"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Power Spectral Density level in steps of 0.5dB with "Power Spectral Density level in steps of 0.5dB with
an offset of -140dbm/Hz." an offset of -140dbm/Hz."
REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM
::= { vdslLineMCMConfProfileTxPSDEntry 3 } ::= { vdslLineMCMConfProfileTxPSDEntry 3 }
vdslMCMConfProfileTxPSDRowStatus OBJECT-TYPE vdslMCMConfProfileTxPSDRowStatus OBJECT-TYPE
skipping to change at page 35, line 31 skipping to change at line 2620
"This table contains transmit maximum PSD mask descriptor "This table contains transmit maximum PSD mask descriptor
configuration information for a VDSL line. Each entry in configuration information for a VDSL line. Each entry in
this table reflects the configuration for one tone within this table reflects the configuration for one tone within
a multiple carrier modulation (MCM) VDSL modem. These a multiple carrier modulation (MCM) VDSL modem. These
entries are defined by a manager and can be used to entries are defined by a manager and can be used to
configure the VDSL line. configure the VDSL line.
This table MUST be implemented for multiple carrier This table MUST be implemented for multiple carrier
modulation (MCM) VDSL lines. This table MUST NOT be modulation (MCM) VDSL lines. This table MUST NOT be
implemented for single carrier modulation VDSL lines." implemented for single carrier modulation VDSL lines."
::= { vdslMibObjects 13 } ::= { vdslMibObjects 16 }
vdslLineMCMConfProfileMaxTxPSDEntry OBJECT-TYPE vdslLineMCMConfProfileMaxTxPSDEntry OBJECT-TYPE
SYNTAX VdslLineMCMConfProfileMaxTxPSDEntry SYNTAX VdslLineMCMConfProfileMaxTxPSDEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each entry consists of a transmit PSD mask descriptor, "Each entry consists of a transmit PSD mask descriptor,
which defines the maximum power spectral density (PSD) which defines the maximum power spectral density (PSD)
for a tone. for a tone.
A default profile with an index of 1 will always exist and A default profile with an index of 1 MUST always exist and
Expires December 17, 2002 [PAGE 49]
its parameters will be set to vendor specific values, its parameters will be set to vendor specific values,
unless otherwise specified in this document." unless otherwise specified in this document."
will be set to `DEFVAL' and its parameters will be set to
INDEX { vdslLineConfProfileIndex, INDEX { vdslLineConfProfileIndex,
vdslPhysSide,
vdslMCMConfProfileMaxTxPSDNumber } vdslMCMConfProfileMaxTxPSDNumber }
::= { vdslLineMCMConfProfileMaxTxPSDTable 1 } ::= { vdslLineMCMConfProfileMaxTxPSDTable 1 }
VdslLineMCMConfProfileMaxTxPSDEntry ::= VdslLineMCMConfProfileMaxTxPSDEntry ::=
SEQUENCE SEQUENCE
{ {
vdslMCMConfProfileMaxTxPSDNumber INTEGER, vdslMCMConfProfileMaxTxPSDNumber Unsigned32,
vdslMCMConfProfileMaxTxPSDTone INTEGER, vdslMCMConfProfileMaxTxPSDTone Unsigned32,
vdslMCMConfProfileMaxTxPSDPSD INTEGER, vdslMCMConfProfileMaxTxPSDPSD Unsigned32,
vdslMCMConfProfileMaxTxPSDRowStatus RowStatus vdslMCMConfProfileMaxTxPSDRowStatus RowStatus
} }
vdslMCMConfProfileMaxTxPSDNumber OBJECT-TYPE vdslMCMConfProfileMaxTxPSDNumber OBJECT-TYPE
SYNTAX INTEGER SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The index for this band descriptor entry." "The index for this band descriptor entry."
::= { vdslLineMCMConfProfileMaxTxPSDEntry 1 } ::= { vdslLineMCMConfProfileMaxTxPSDEntry 1 }
vdslMCMConfProfileMaxTxPSDTone OBJECT-TYPE vdslMCMConfProfileMaxTxPSDTone OBJECT-TYPE
SYNTAX INTEGER SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The tone index for which the PSD is being specified." "The tone index for which the PSD is being specified."
REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM
::= { vdslLineMCMConfProfileMaxTxPSDEntry 2 } ::= { vdslLineMCMConfProfileMaxTxPSDEntry 2 }
vdslMCMConfProfileMaxTxPSDPSD OBJECT-TYPE vdslMCMConfProfileMaxTxPSDPSD OBJECT-TYPE
SYNTAX INTEGER SYNTAX Unsigned32
UNITS "0.5dB" UNITS "0.5dB"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Power Spectral Density level in steps of 0.5dB with "Power Spectral Density level in steps of 0.5dB with
an offset of -140dbm/Hz." an offset of -140dbm/Hz."
REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM
::= { vdslLineMCMConfProfileMaxTxPSDEntry 3 } ::= { vdslLineMCMConfProfileMaxTxPSDEntry 3 }
vdslMCMConfProfileMaxTxPSDRowStatus OBJECT-TYPE vdslMCMConfProfileMaxTxPSDRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is used to create a new row or modify or "This object is used to create a new row or modify or
delete an existing row in this table. delete an existing row in this table.
A profile activated by setting this object to `active'. A profile activated by setting this object to `active'.
When `active' is set, the system will validate the profile. When `active' is set, the system will validate the profile.
Expires December 17, 2002 [PAGE 50]
Before a profile can be deleted or taken out of Before a profile can be deleted or taken out of
service, (by setting this object to `destroy' or service, (by setting this object to `destroy' or
`outOfService') it must be first unreferenced `outOfService') it must be first unreferenced
from all associated lines." from all associated lines."
::= { vdslLineMCMConfProfileMaxTxPSDEntry 4 } ::= { vdslLineMCMConfProfileMaxTxPSDEntry 4 }
vdslLineMCMConfProfileMaxRxPSDTable OBJECT-TYPE vdslLineMCMConfProfileMaxRxPSDTable OBJECT-TYPE
SYNTAX SEQUENCE OF VdslLineMCMConfProfileMaxRxPSDEntry SYNTAX SEQUENCE OF VdslLineMCMConfProfileMaxRxPSDEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 37, line 14 skipping to change at line 2710
"This table contains maximum receive PSD mask descriptor "This table contains maximum receive PSD mask descriptor
configuration information for a VDSL line. Each entry in configuration information for a VDSL line. Each entry in
this table reflects the configuration for one tone within this table reflects the configuration for one tone within
a multiple carrier modulation (MCM) VDSL modem. These a multiple carrier modulation (MCM) VDSL modem. These
entries are defined by a manager and can be used to entries are defined by a manager and can be used to
configure the VDSL line. configure the VDSL line.
This table MUST be implemented for multiple carrier This table MUST be implemented for multiple carrier
modulation (MCM) VDSL lines. This table MUST NOT be modulation (MCM) VDSL lines. This table MUST NOT be
implemented for single carrier modulation VDSL lines." implemented for single carrier modulation VDSL lines."
::= { vdslMibObjects 14 } ::= { vdslMibObjects 17 }
vdslLineMCMConfProfileMaxRxPSDEntry OBJECT-TYPE vdslLineMCMConfProfileMaxRxPSDEntry OBJECT-TYPE
SYNTAX VdslLineMCMConfProfileMaxRxPSDEntry SYNTAX VdslLineMCMConfProfileMaxRxPSDEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each entry consists of a transmit PSD mask descriptor, "Each entry consists of a transmit PSD mask descriptor,
which defines the power spectral density (PSD) for a which defines the power spectral density (PSD) for a
tone. tone.
A default profile with an index of 1 will always exist and A default profile with an index of 1 will always exist and
its parameters will be set to vendor specific values, its parameters will be set to vendor specific values,
unless otherwise specified in this document." unless otherwise specified in this document."
INDEX { vdslLineConfProfileIndex, INDEX { vdslLineConfProfileIndex,
vdslPhysSide,
vdslMCMConfProfileMaxRxPSDNumber } vdslMCMConfProfileMaxRxPSDNumber }
::= { vdslLineMCMConfProfileMaxRxPSDTable 1 } ::= { vdslLineMCMConfProfileMaxRxPSDTable 1 }
VdslLineMCMConfProfileMaxRxPSDEntry ::= VdslLineMCMConfProfileMaxRxPSDEntry ::=
SEQUENCE SEQUENCE
{ {
vdslMCMConfProfileMaxRxPSDNumber INTEGER, vdslMCMConfProfileMaxRxPSDNumber Unsigned32,
vdslMCMConfProfileMaxRxPSDTone INTEGER, vdslMCMConfProfileMaxRxPSDTone Unsigned32,
vdslMCMConfProfileMaxRxPSDPSD INTEGER, vdslMCMConfProfileMaxRxPSDPSD Unsigned32,
vdslMCMConfProfileMaxRxPSDRowStatus RowStatus vdslMCMConfProfileMaxRxPSDRowStatus RowStatus
} }
vdslMCMConfProfileMaxRxPSDNumber OBJECT-TYPE vdslMCMConfProfileMaxRxPSDNumber OBJECT-TYPE
SYNTAX INTEGER SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
Expires December 17, 2002 [PAGE 51]
DESCRIPTION DESCRIPTION
"The index for this band descriptor entry." "The index for this band descriptor entry."
::= { vdslLineMCMConfProfileMaxRxPSDEntry 1 } ::= { vdslLineMCMConfProfileMaxRxPSDEntry 1 }
vdslMCMConfProfileMaxRxPSDTone OBJECT-TYPE vdslMCMConfProfileMaxRxPSDTone OBJECT-TYPE
SYNTAX INTEGER SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The tone index for which the PSD is being specified." "The tone index for which the PSD is being specified."
REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM
::= { vdslLineMCMConfProfileMaxRxPSDEntry 2 } ::= { vdslLineMCMConfProfileMaxRxPSDEntry 2 }
vdslMCMConfProfileMaxRxPSDPSD OBJECT-TYPE vdslMCMConfProfileMaxRxPSDPSD OBJECT-TYPE
SYNTAX INTEGER SYNTAX Unsigned32
UNITS "0.5dB" UNITS "0.5dB"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Power Spectral Density level in steps of 0.5dB with "Power Spectral Density level in steps of 0.5dB with
an offset of -140dbm/Hz." an offset of -140dbm/Hz."
REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM REFERENCE "T1E1.4/2000-013R4" -- Part 3, MCM
::= { vdslLineMCMConfProfileMaxRxPSDEntry 3 } ::= { vdslLineMCMConfProfileMaxRxPSDEntry 3 }
vdslMCMConfProfileMaxRxPSDRowStatus OBJECT-TYPE vdslMCMConfProfileMaxRxPSDRowStatus OBJECT-TYPE
skipping to change at page 38, line 35 skipping to change at line 2785
A profile activated by setting this object to `active'. A profile activated by setting this object to `active'.
When `active' is set, the system will validate the profile. When `active' is set, the system will validate the profile.
Before a profile can be deleted or taken out of Before a profile can be deleted or taken out of
service, (by setting this object to `destroy' or service, (by setting this object to `destroy' or
`outOfService') it must be first unreferenced `outOfService') it must be first unreferenced
from all associated lines." from all associated lines."
::= { vdslLineMCMConfProfileMaxRxPSDEntry 4 } ::= { vdslLineMCMConfProfileMaxRxPSDEntry 4 }
-- --
-- Single carrier modulation (SCM) configuration profile table -- Single carrier modulation (SCM) configuration profile tables
-- --
vdslLineSCMConfProfileTable OBJECT-TYPE vdslLineSCMConfProfileTable OBJECT-TYPE
SYNTAX SEQUENCE OF VdslLineSCMConfProfileEntry SYNTAX SEQUENCE OF VdslLineSCMConfProfileEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains information on the VDSL line "This table contains information on the VDSL line
configuration. One entry in this table reflects a configuration. One entry in this table reflects a
profile defined by a manager which can be used to profile defined by a manager which can be used to
Expires December 17, 2002 [PAGE 52]
configure the VDSL line. configure the VDSL line.
This table MUST be implemented for single carrier This table MUST be implemented for single carrier
modulation (SCM) VDSL lines. This table MUST NOT be modulation (SCM) VDSL lines. This table MUST NOT be
implemented for multiple carrier modulation (MCM) VDSL implemented for multiple carrier modulation (MCM) VDSL
lines." lines."
::= { vdslMibObjects 15 } ::= { vdslMibObjects 18 }
vdslLineSCMConfProfileEntry OBJECT-TYPE vdslLineSCMConfProfileEntry OBJECT-TYPE
SYNTAX VdslLineSCMConfProfileEntry SYNTAX VdslLineSCMConfProfileEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each entry consists of a list of parameters that "Each entry consists of a list of parameters that
represents the configuration of a single carrier represents the configuration of a single carrier
modulation VDSL modem. modulation VDSL modem.
A default profile with an index of 1 will always exist and A default profile with an index of 1 MUST always exist and
its parameters will be set to vendor specific values, its parameters will be set to vendor specific values,
unless otherwise specified in this document." unless otherwise specified in this document."
INDEX { vdslLineConfProfileIndex, INDEX { vdslLineConfProfileIndex }
vdslPhysSide }
::= { vdslLineSCMConfProfileTable 1 } ::= { vdslLineSCMConfProfileTable 1 }
VdslLineSCMConfProfileEntry ::= VdslLineSCMConfProfileEntry ::=
SEQUENCE SEQUENCE
{ {
vdslSCMConfProfileInterleaveDepth INTEGER, vdslSCMConfProfileInterleaveDepth Unsigned32,
vdslSCMConfProfileFastCodewordSize INTEGER, vdslSCMConfProfileFastCodewordSize Unsigned32,
vdslSCMConfProfileTransmitPSDMask BITS, vdslSCMConfProfileTransmitPSDMask BITS,
vdslSCMConfProfileTransmitPSDLevel INTEGER, vdslSCMConfProfileBands INTEGER,
vdslSCMConfProfileSymbolRateProfile INTEGER, vdslSCMConfProfileFastFecSize INTEGER,
vdslSCMConfProfileConstellationSize INTEGER,
vdslSCMConfProfileCenterFrequency INTEGER,
vdslSCMConfProfileRowStatus RowStatus vdslSCMConfProfileRowStatus RowStatus
} }
vdslSCMConfProfileInterleaveDepth OBJECT-TYPE vdslSCMConfProfileInterleaveDepth OBJECT-TYPE
SYNTAX INTEGER SYNTAX Unsigned32
UNITS "octets" UNITS "octets"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the interleaving depth." "Specifies the interleaving depth."
REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM
::= { vdslLineSCMConfProfileEntry 1 } ::= { vdslLineSCMConfProfileEntry 1 }
vdslSCMConfProfileFastCodewordSize OBJECT-TYPE vdslSCMConfProfileFastCodewordSize OBJECT-TYPE
SYNTAX INTEGER(0..180) SYNTAX Unsigned32(0..180)
UNITS "octets" UNITS "octets"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the length in octets of the fast codeword. "Specifies the length in octets of the fast codeword.
A value of 0 indicates that the single latency transport A value of 0 indicates that the single latency transport
class is to be utilized." class is to be utilized."
Expires December 17, 2002 [PAGE 53]
REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM
::= { vdslLineSCMConfProfileEntry 2 } ::= { vdslLineSCMConfProfileEntry 2 }
vdslSCMConfProfileTransmitPSDMask OBJECT-TYPE vdslSCMConfProfileTransmitPSDMask OBJECT-TYPE
SYNTAX BITS SYNTAX BITS
{ {
vendorNotch1(0), -- vendor specific notch vendorNotch1(0), -- vendor specific notch
vendorNotch2(1), -- vendor specific notch vendorNotch2(1), -- vendor specific notch
amateurBand30m(2), -- amateur radio band notch amateurBand30m(2), -- amateur radio band notch
amateurBand40m(3), -- amateur radio band notch amateurBand40m(3), -- amateur radio band notch
amateurBand80m(4), -- amateur radio band notch amateurBand80m(4), -- amateur radio band notch
amateurBand160m(5) -- amateur radio band notch amateurBand160m(5) -- amateur radio band notch
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The transmit power spectral density mask code." "The transmit power spectral density mask code."
REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM
::= { vdslLineSCMConfProfileEntry 3 } ::= { vdslLineSCMConfProfileEntry 3 }
vdslSCMConfProfileTransmitPSDLevel OBJECT-TYPE vdslSCMConfProfileBands OBJECT-TYPE
SYNTAX INTEGER SYNTAX INTEGER
UNITS "dBm/Hz" {
oneBand(1),
twoBands(2),
upstreamU0(3)
}
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The transmit power spectral density for the VDSL modem." "Specifies the number of bands used to transmit."
REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM
::= { vdslLineSCMConfProfileEntry 4 } ::= { vdslLineSCMConfProfileEntry 4 }
vdslSCMConfProfileSymbolRateProfile OBJECT-TYPE vdslSCMConfProfileFastFecSize OBJECT-TYPE
SYNTAX INTEGER
{
noFEC(1),
fecSize2(2),
fecSize4(3),
fecSize16(4)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"When fast channel is being used, this object specifies
the size of the forward error correction (FEC) codeword."
REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM
::= { vdslLineSCMConfProfileEntry 5 }
vdslSCMConfProfileRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
Expires December 17, 2002 [PAGE 54]
STATUS current
DESCRIPTION
"This object is used to create a new row or modify or
delete an existing row in this table.
A profile activated by setting this object to `active'.
When `active' is set, the system will validate the profile.
Before a profile can be deleted or taken out of
service, (by setting this object to `destroy' or
`outOfService') it must be first unreferenced
from all associated lines."
::= { vdslLineSCMConfProfileEntry 6 }
vdslLineSCMConfProfileTxBandTable OBJECT-TYPE
SYNTAX SEQUENCE OF VdslLineSCMConfProfileTxBandEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains transmit band descriptor configuration
information for a VDSL line. Each entry in this table
reflects the configuration for one of possibly three bands
with a single carrier modulation (SCM) VDSL line. These
entries are defined by a manager and can be used to configure
the VDSL line.
This table MUST be implemented for single carrier
modulation (SCM) VDSL lines. This table MUST NOT be
implemented for multiple carrier modulation (MCM) VDSL
lines."
::= { vdslMibObjects 19 }
vdslLineSCMConfProfileTxBandEntry OBJECT-TYPE
SYNTAX VdslLineSCMConfProfileTxBandEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Each entry consists of a list of parameters that
represents the configuration of a single carrier
modulation VDSL modem transmit band.
A default profile with an index of 1 MUST always exist and
its parameters will be set to vendor specific values,
unless otherwise specified in this document."
INDEX { vdslLineConfProfileIndex,
vdslSCMConfProfileTxBandNumber }
::= { vdslLineSCMConfProfileTxBandTable 1 }
VdslLineSCMConfProfileTxBandEntry ::=
SEQUENCE
{
vdslSCMConfProfileTxBandNumber INTEGER,
vdslSCMConfProfileTxBandTransmitPSDLevel Unsigned32,
Expires December 17, 2002 [PAGE 55]
vdslSCMConfProfileTxBandSymbolRateProfile Unsigned32,
vdslSCMConfProfileTxBandConstellationSize Unsigned32,
vdslSCMConfProfileTxBandCenterFrequency Unsigned32,
vdslSCMConfProfileTxBandRowStatus RowStatus
}
vdslSCMConfProfileTxBandNumber OBJECT-TYPE
SYNTAX INTEGER SYNTAX INTEGER
{
band1(1),
band2(2),
upstreamU0(3)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The SCN transmit band number for this entry."
::= { vdslLineSCMConfProfileTxBandEntry 1 }
vdslSCMConfProfileTxBandTransmitPSDLevel OBJECT-TYPE
SYNTAX Unsigned32
UNITS "-dBm/Hz"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The transmit power spectral density for the VDSL modem."
REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM
::= { vdslLineSCMConfProfileTxBandEntry 2 }
vdslSCMConfProfileTxBandSymbolRateProfile OBJECT-TYPE
SYNTAX Unsigned32
UNITS "kbaud" UNITS "kbaud"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The symbol rate profile calculated as S = SR/BSR, where "The symbol rate profile calculated as S = SR/BSR, where
SR is the required symbol rate in kbaud, BSR = 67.5." SR is the required symbol rate in kbaud, BSR = 67.5."
REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM
::= { vdslLineSCMConfProfileEntry 5 } ::= { vdslLineSCMConfProfileTxBandEntry 3 }
vdslSCMConfProfileConstellationSize OBJECT-TYPE vdslSCMConfProfileTxBandConstellationSize OBJECT-TYPE
SYNTAX INTEGER(0..15) SYNTAX Unsigned32(0..8)
UNITS "log2" UNITS "log2"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the constellation size." "Specifies the constellation size."
REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM
::= { vdslLineSCMConfProfileEntry 6 } ::= { vdslLineSCMConfProfileTxBandEntry 4 }
vdslSCMConfProfileCenterFrequency OBJECT-TYPE vdslSCMConfProfileTxBandCenterFrequency OBJECT-TYPE
SYNTAX INTEGER(0..511) SYNTAX Unsigned32(0..511)
UNITS "kHz" UNITS "33.75kHz"
Expires December 17, 2002 [PAGE 56]
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the center frequency profile K." "Specifies the center frequency profile K."
REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM REFERENCE "T1E1.4/2000-011R3" -- Part 2, SCM
::= { vdslLineSCMConfProfileEntry 7 } ::= { vdslLineSCMConfProfileTxBandEntry 5 }
vdslSCMConfProfileRowStatus OBJECT-TYPE
vdslSCMConfProfileTxBandRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is used to create a new row or modify or "This object is used to create a new row or modify or
delete an existing row in this table. delete an existing row in this table.
A profile activated by setting this object to `active'. A profile activated by setting this object to `active'.
When `active' is set, the system will validate the profile. When `active' is set, the system will validate the profile.
Before a profile can be deleted or taken out of Before a profile can be deleted or taken out of
service, (by setting this object to `destroy' or service, (by setting this object to `destroy' or
`outOfService') it must be first unreferenced `outOfService') it must be first unreferenced
from all associated lines." from all associated lines."
::= { vdslLineSCMConfProfileEntry 8 } ::= { vdslLineSCMConfProfileTxBandEntry 6 }
-- --
-- Alarm configuration profile table -- Alarm configuration profile table
-- --
vdslLineAlarmConfProfileTable OBJECT-TYPE vdslLineAlarmConfProfileTable OBJECT-TYPE
SYNTAX SEQUENCE OF VdslLineAlarmConfProfileEntry SYNTAX SEQUENCE OF VdslLineAlarmConfProfileEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains information on the VDSL line alarm "This table contains information on the VDSL line alarm
configuration. One entry in this table reflects a profile configuration. One entry in this table reflects a profile
defined by a manager which can be used to configure the defined by a manager which can be used to configure the
VDSL line alarm thresholds." VDSL line alarm thresholds."
::= { vdslMibObjects 16 } ::= { vdslMibObjects 20 }
vdslLineAlarmConfProfileEntry OBJECT-TYPE vdslLineAlarmConfProfileEntry OBJECT-TYPE
SYNTAX VdslLineAlarmConfProfileEntry SYNTAX VdslLineAlarmConfProfileEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each entry consists of a list of parameters that "Each entry consists of a list of parameters that
represents the configuration of a VDSL line alarm represents the configuration of a VDSL line alarm
profile. profile.
A default profile with an index of 1 will always exist and A default profile with an index of 1 MUST always exist and
its parameters will be set to vendor specific values, its parameters will be set to vendor specific values,
unless otherwise specified in this document." unless otherwise specified in this document."
INDEX { vdslLineAlarmConfProfileIndex, INDEX { vdslLineAlarmConfProfileIndex }
vdslPhysSide }
::= { vdslLineAlarmConfProfileTable 1 } ::= { vdslLineAlarmConfProfileTable 1 }
Expires December 17, 2002 [PAGE 57]
VdslLineAlarmConfProfileEntry ::= VdslLineAlarmConfProfileEntry ::=
SEQUENCE SEQUENCE
{ {
vdslLineAlarmConfProfileIndex Integer32, vdslLineAlarmConfProfileIndex Unsigned32,
vdslLineAlarmConfProfileName SnmpAdminString, vdslLineAlarmConfProfileName SnmpAdminString,
vdslThresh15MinLofs INTEGER, vdslThresh15MinLofs Unsigned32,
vdslThresh15MinLoss INTEGER, vdslThresh15MinLoss Unsigned32,
vdslThresh15MinLprs INTEGER, vdslThresh15MinLprs Unsigned32,
vdslThresh15MinESs INTEGER, vdslThresh15MinESs Unsigned32,
vdslThresh15MinSESs Unsigned32,
vdslThresh15MinUASs Unsigned32,
vdslInitFailureNotificationEnable TruthValue, vdslInitFailureNotificationEnable TruthValue,
vdslLineAlarmConfProfileRowStatus RowStatus vdslLineAlarmConfProfileRowStatus RowStatus
} }
vdslLineAlarmConfProfileIndex OBJECT-TYPE vdslLineAlarmConfProfileIndex OBJECT-TYPE
SYNTAX Integer32 SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is used by the line alarm configuration table "This object is used by the line alarm configuration table
in order to identify a row in that table. The system will in order to identify a row in that table. The system MUST
always provide a default profile whose index is 1." provide a default profile whose index is 1."
::= { vdslLineAlarmConfProfileEntry 1 } ::= { vdslLineAlarmConfProfileEntry 1 }
vdslLineAlarmConfProfileName OBJECT-TYPE vdslLineAlarmConfProfileName OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (1..32)) SYNTAX SnmpAdminString (SIZE (1..32))
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The name for this profile as specified by a user." "The name for this profile as specified by a user."
::= { vdslLineAlarmConfProfileEntry 2 } ::= { vdslLineAlarmConfProfileEntry 2 }
vdslThresh15MinLofs OBJECT-TYPE vdslThresh15MinLofs OBJECT-TYPE
SYNTAX INTEGER(0..899) SYNTAX Unsigned32(0..899)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object configures the threshold for the number of "This object configures the threshold for the number of
loss of frame seconds (lofs) within any given 15-minute loss of frame seconds (lofs) within any given 15-minute
performance data collection interval. If the value of performance data collection interval. If the value of
loss of frame seconds in a particular 15-minute collection loss of frame seconds in a particular 15-minute collection
interval reaches/exceeds this value, a interval reaches/exceeds this value, a
vdslPerfLofsThreshNotification notification will be vdslPerfLofsThreshNotification notification will be
generated. No more than one notification will be sent generated. No more than one notification will be sent
per interval." per interval."
::= { vdslLineAlarmConfProfileEntry 3 } ::= { vdslLineAlarmConfProfileEntry 3 }
vdslThresh15MinLoss OBJECT-TYPE vdslThresh15MinLoss OBJECT-TYPE
SYNTAX INTEGER(0..899) SYNTAX Unsigned32(0..899)
UNITS "seconds" UNITS "seconds"
Expires December 17, 2002 [PAGE 58]
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object configures the threshold for the number of "This object configures the threshold for the number of
loss of signal seconds (loss) within any given 15-minute loss of signal seconds (loss) within any given 15-minute
performance data collection interval. If the value of performance data collection interval. If the value of
loss of frame seconds in a particular 15-minute collection loss of frame seconds in a particular 15-minute collection
interval reaches/exceeds this value, a interval reaches/exceeds this value, a
vdslPerfLossThreshNotification notification will be vdslPerfLossThreshNotification notification will be
generated. One notification will be sent per interval generated. One notification will be sent per interval
per endpoint." per endpoint."
::= { vdslLineAlarmConfProfileEntry 4 } ::= { vdslLineAlarmConfProfileEntry 4 }
vdslThresh15MinLprs OBJECT-TYPE vdslThresh15MinLprs OBJECT-TYPE
SYNTAX INTEGER(0..899) SYNTAX Unsigned32(0..899)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object configures the threshold for the number of "This object configures the threshold for the number of
loss of power seconds (lprs) within any given 15-minute loss of power seconds (lprs) within any given 15-minute
performance data collection interval. If the value of performance data collection interval. If the value of
loss of frame seconds in a particular 15-minute collection loss of frame seconds in a particular 15-minute collection
interval reaches/exceeds this value, a interval reaches/exceeds this value, a
vdslPerfLprsThreshNotification notification will be vdslPerfLprsThreshNotification notification will be
generated. No more than one notification will be sent generated. No more than one notification will be sent
per interval." per interval."
::= { vdslLineAlarmConfProfileEntry 5 } ::= { vdslLineAlarmConfProfileEntry 5 }
vdslThresh15MinESs OBJECT-TYPE vdslThresh15MinESs OBJECT-TYPE
SYNTAX INTEGER(0..899) SYNTAX Unsigned32(0..899)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object configures the threshold for the number of "This object configures the threshold for the number of
errored seconds (lofs) within any given 15-minute errored seconds (ESs) within any given 15-minute
performance data collection interval. If the value of performance data collection interval. If the value of
loss of frame seconds in a particular 15-minute collection errored seconds in a particular 15-minute collection
interval reaches/exceeds this value, a interval reaches/exceeds this value, a
vdslPerfESsThreshNotification notification will be vdslPerfESsThreshNotification notification will be
generated. No more than one notification will be sent generated. No more than one notification will be sent
per interval." per interval."
::= { vdslLineAlarmConfProfileEntry 6 } ::= { vdslLineAlarmConfProfileEntry 6 }
vdslThresh15MinSESs OBJECT-TYPE
SYNTAX Unsigned32(0..899)
UNITS "seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object configures the threshold for the number of
severely errored seconds (SESs) within any given 15-minute
Expires December 17, 2002 [PAGE 59]
performance data collection interval. If the value of
severely errored seconds in a particular 15-minute
collection interval reaches/exceeds this value, a
vdslPerfSESsThreshNotification notification will be
generated. No more than one notification will be sent
per interval."
::= { vdslLineAlarmConfProfileEntry 7 }
vdslThresh15MinUASs OBJECT-TYPE
SYNTAX Unsigned32(0..899)
UNITS "seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object configures the threshold for the number of
unavailable seconds (UASs) within any given 15-minute
performance data collection interval. If the value of
unavailable seconds in a particular 15-minute collection
interval reaches/exceeds this value, a
vdslPerfUASsThreshNotification notification will be
generated. No more than one notification will be sent
per interval."
::= { vdslLineAlarmConfProfileEntry 8 }
vdslInitFailureNotificationEnable OBJECT-TYPE vdslInitFailureNotificationEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies if a vdslInitFailureNotification "This object specifies if a vdslInitFailureNotification
notification will be generated if an initialization notification will be generated if an initialization
failure occurs." failure occurs."
::= { vdslLineAlarmConfProfileEntry 7 } ::= { vdslLineAlarmConfProfileEntry 9 }
vdslLineAlarmConfProfileRowStatus OBJECT-TYPE vdslLineAlarmConfProfileRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is used to create a new row or modify or "This object is used to create a new row or modify or
delete an existing row in this table. delete an existing row in this table.
A profile activated by setting this object to `active'. A profile activated by setting this object to `active'.
When `active' is set, the system will validate the profile. When `active' is set, the system will validate the profile.
Before a profile can be deleted or taken out of Before a profile can be deleted or taken out of
service, (by setting this object to `destroy' or service, (by setting this object to `destroy' or
`outOfService') it must be first unreferenced `outOfService') it must be first unreferenced
from all associated lines." from all associated lines."
::= { vdslLineAlarmConfProfileEntry 8 } ::= { vdslLineAlarmConfProfileEntry 10 }
-- Notification definitions -- Notification definitions
Expires December 17, 2002 [PAGE 60]
vdslNotifications OBJECT IDENTIFIER ::= { vdslLineMib 0 } vdslNotifications OBJECT IDENTIFIER ::= { vdslLineMib 0 }
vdslPerfLofsThreshNotification NOTIFICATION-TYPE vdslPerfLofsThreshNotification NOTIFICATION-TYPE
OBJECTS { OBJECTS {
vdslPerfCurr15MinLofs, vdslPerfCurr15MinLofs,
vdslThresh15MinLofs vdslThresh15MinLofs
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Loss of Framing 15-minute interval threshold reached." "Loss of Framing 15-minute interval threshold reached."
skipping to change at page 44, line 56 skipping to change at line 3275
"Loss of Power 15-minute interval threshold reached." "Loss of Power 15-minute interval threshold reached."
::= { vdslNotifications 3 } ::= { vdslNotifications 3 }
vdslPerfESsThreshNotification NOTIFICATION-TYPE vdslPerfESsThreshNotification NOTIFICATION-TYPE
OBJECTS { OBJECTS {
vdslPerfCurr15MinESs, vdslPerfCurr15MinESs,
vdslThresh15MinESs vdslThresh15MinESs
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Errored Second 15-minute interval threshold reached." "Errored Seconds 15-minute interval threshold reached."
::= { vdslNotifications 4 } ::= { vdslNotifications 4 }
vdslPerfSESsThreshNotification NOTIFICATION-TYPE
OBJECTS {
vdslPerfCurr15MinSESs,
vdslThresh15MinSESs
}
STATUS current
DESCRIPTION
"Severely Errored Seconds 15-minute interval threshold
reached."
::= { vdslNotifications 5 }
Expires December 17, 2002 [PAGE 61]
vdslPerfUASsThreshNotification NOTIFICATION-TYPE
OBJECTS {
vdslPerfCurr15MinUASs,
vdslThresh15MinUASs
}
STATUS current
DESCRIPTION
"Unavailable Seconds 15-minute interval threshold reached."
::= { vdslNotifications 6 }
vdslInitFailureNotification NOTIFICATION-TYPE vdslInitFailureNotification NOTIFICATION-TYPE
OBJECTS { OBJECTS {
vdslCurrStatus vdslCurrStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Vtu initialization failed. See vdslCurrStatus for "Vtu initialization failed. See vdslCurrStatus for
potential reasons." potential reasons."
::= { vdslNotifications 5 } ::= { vdslNotifications 7 }
-- conformance information -- conformance information
vdslConformance OBJECT IDENTIFIER ::= { vdslLineMib 3 } vdslConformance OBJECT IDENTIFIER ::= { vdslLineMib 3 }
vdslGroups OBJECT IDENTIFIER ::= { vdslConformance 1 } vdslGroups OBJECT IDENTIFIER ::= { vdslConformance 1 }
vdslCompliances OBJECT IDENTIFIER ::= { vdslConformance 2 } vdslCompliances OBJECT IDENTIFIER ::= { vdslConformance 2 }
vdslLineMibCompliance MODULE-COMPLIANCE vdslLineMibCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 45, line 49 skipping to change at line 3343
This group should not be implemented for VDSL lines This group should not be implemented for VDSL lines
which utilize single carrier modulation." which utilize single carrier modulation."
GROUP vdslSCMGroup GROUP vdslSCMGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for VDSL lines which "This group is mandatory for VDSL lines which
utilize single carrier modulation. utilize single carrier modulation.
This group should not be implemented for VDSL lines This group should not be implemented for VDSL lines
which utilize multiple carrier modulation" which utilize multiple carrier modulation"
Expires December 17, 2002 [PAGE 62]
::= { vdslCompliances 1 } ::= { vdslCompliances 1 }
-- units of conformance -- units of conformance
vdslGroup OBJECT-GROUP vdslGroup OBJECT-GROUP
OBJECTS OBJECTS
{ {
vdslLineCoding, vdslLineCoding,
vdslLineType, vdslLineType,
vdslLineConfProfile, vdslLineConfProfile,
skipping to change at page 46, line 24 skipping to change at line 3373
vdslCurrOutputPwr, vdslCurrOutputPwr,
vdslCurrAttainableRate, vdslCurrAttainableRate,
vdslChanInterleaveDelay, vdslChanInterleaveDelay,
vdslChanCrcBlockLength, vdslChanCrcBlockLength,
vdslPerfValidIntervals, vdslPerfValidIntervals,
vdslPerfInvalidIntervals, vdslPerfInvalidIntervals,
vdslPerfLofs, vdslPerfLofs,
vdslPerfLoss, vdslPerfLoss,
vdslPerfLprs, vdslPerfLprs,
vdslPerfESs, vdslPerfESs,
vdslPerfSESs,
vdslPerfUASs,
vdslPerfInits, vdslPerfInits,
vdslPerfCurr15MinTimeElapsed, vdslPerfCurr15MinTimeElapsed,
vdslPerfCurr15MinLofs, vdslPerfCurr15MinLofs,
vdslPerfCurr15MinLoss, vdslPerfCurr15MinLoss,
vdslPerfCurr15MinLprs, vdslPerfCurr15MinLprs,
vdslPerfCurr15MinESs, vdslPerfCurr15MinESs,
vdslPerfCurr15MinSESs,
vdslPerfCurr15MinUASs,
vdslPerfCurr15MinInits, vdslPerfCurr15MinInits,
vdslPerf1DayValidIntervals,
vdslPerf1DayInvalidIntervals,
vdslPerfCurr1DayTimeElapsed,
vdslPerfCurr1DayLofs,
vdslPerfCurr1DayLoss,
vdslPerfCurr1DayLprs,
vdslPerfCurr1DayESs,
vdslPerfCurr1DaySESs,
vdslPerfCurr1DayUASs,
vdslPerfCurr1DayInits,
vdslIntervalLofs, vdslIntervalLofs,
vdslIntervalLoss, vdslIntervalLoss,
vdslIntervalLprs, vdslIntervalLprs,
vdslIntervalESs, vdslIntervalESs,
Expires December 17, 2002 [PAGE 63]
vdslIntervalSESs,
vdslIntervalUASs,
vdslIntervalInits, vdslIntervalInits,
vdsl1DayIntervalMoniSecs,
vdsl1DayIntervalLofs,
vdsl1DayIntervalLoss,
vdsl1DayIntervalLprs,
vdsl1DayIntervalESs,
vdsl1DayIntervalSESs,
vdsl1DayIntervalUASs,
vdsl1DayIntervalInits,
vdslChanPerfValidIntervals, vdslChanPerfValidIntervals,
vdslChanPerfInvalidIntervals, vdslChanPerfInvalidIntervals,
vdslChanCorrectedOctets, vdslChanCorrectedOctets,
vdslChanUncorrectBlks, vdslChanUncorrectBlks,
vdslChanPerfCurr15MinTimeElapsed, vdslChanPerfCurr15MinTimeElapsed,
vdslChanPerfCurr15MinCorrectedOctets, vdslChanPerfCurr15MinCorrectedOctets,
vdslChanPerfCurr15MinUncorrectBlks, vdslChanPerfCurr15MinUncorrectBlks,
vdslChanPerf1DayValidIntervals,
vdslChanPerf1DayInvalidIntervals,
vdslChanPerfCurr1DayTimeElapsed,
vdslChanPerfCurr1DayCorrectedOctets,
vdslChanPerfCurr1DayUncorrectBlks,
vdslChanIntervalCorrectedOctets, vdslChanIntervalCorrectedOctets,
vdslChanIntervalUncorrectBlks, vdslChanIntervalUncorrectBlks,
vdslChan1DayIntervalMoniSecs,
vdslChan1DayIntervalCorrectedOctets,
vdslChan1DayIntervalUncorrectBlks,
vdslLineConfProfileIndex, vdslLineConfProfileIndex,
vdslLineConfProfileName, vdslLineConfProfileName,
vdslLineConfTargetSnrMgn, vdslLineConfTargetSnrMgn,
vdslLineConfTxSpeed, vdslLineConfUpstreamTxSpeed,
vdslLineConfRxSpeed, vdslLineConfDownstreamTxSpeed,
vdslLineConfUpstreamPboControl,
vdslLineConfDownstreamPboControl,
vdslLineConfDeploymentScenario,
vdslLineConfAdslOccupy,
vdslLineConfApplicableStandard,
vdslLineConfBandPlan,
vdslLineConfBandPlanFx,
vdslLineConfBandU0Usage,
vdslLineConfUpstreamPsdTemplate,
vdslLineConfDownstreamPsdTemplate,
vdslLineConfProfileRowStatus, vdslLineConfProfileRowStatus,
vdslLineAlarmConfProfileIndex, vdslLineAlarmConfProfileIndex,
vdslLineAlarmConfProfileName, vdslLineAlarmConfProfileName,
vdslThresh15MinLofs, vdslThresh15MinLofs,
vdslThresh15MinLoss, vdslThresh15MinLoss,
vdslThresh15MinLprs, vdslThresh15MinLprs,
vdslThresh15MinESs, vdslThresh15MinESs,
vdslThresh15MinSESs,
vdslThresh15MinUASs,
vdslInitFailureNotificationEnable, vdslInitFailureNotificationEnable,
Expires December 17, 2002 [PAGE 64]
vdslLineAlarmConfProfileRowStatus vdslLineAlarmConfProfileRowStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing information about "A collection of objects providing information about
a VDSL Line." a VDSL Line."
::= { vdslGroups 1 } ::= { vdslGroups 1 }
vdslMCMGroup OBJECT-GROUP vdslMCMGroup OBJECT-GROUP
OBJECTS OBJECTS
skipping to change at page 47, line 49 skipping to change at line 3499
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing configuration "A collection of objects providing configuration
information for a VDSL line based upon multiple carrier information for a VDSL line based upon multiple carrier
modulation modem." modulation modem."
::= { vdslGroups 2 } ::= { vdslGroups 2 }
vdslSCMGroup OBJECT-GROUP vdslSCMGroup OBJECT-GROUP
OBJECTS OBJECTS
{ {
vdslSCMPhysBandSnrMgn,
vdslSCMPhysBandAtn,
vdslSCMConfProfileInterleaveDepth, vdslSCMConfProfileInterleaveDepth,
vdslSCMConfProfileFastCodewordSize, vdslSCMConfProfileFastCodewordSize,
vdslSCMConfProfileTransmitPSDMask, vdslSCMConfProfileTransmitPSDMask,
vdslSCMConfProfileTransmitPSDLevel, vdslSCMConfProfileBands,
vdslSCMConfProfileSymbolRateProfile, vdslSCMConfProfileFastFecSize,
vdslSCMConfProfileConstellationSize, vdslSCMConfProfileRowStatus,
vdslSCMConfProfileCenterFrequency, vdslSCMConfProfileTxBandNumber,
vdslSCMConfProfileRowStatus
Expires December 17, 2002 [PAGE 65]
vdslSCMConfProfileTxBandTransmitPSDLevel,
vdslSCMConfProfileTxBandSymbolRateProfile,
vdslSCMConfProfileTxBandConstellationSize,
vdslSCMConfProfileTxBandCenterFrequency,
vdslSCMConfProfileTxBandRowStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing configuration "A collection of objects providing configuration
information for a VDSL line based upon single carrier information for a VDSL line based upon single carrier
modulation modem." modulation modem."
::= { vdslGroups 3 } ::= { vdslGroups 3 }
vdslNotificationGroup NOTIFICATION-GROUP vdslNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS NOTIFICATIONS
{ {
vdslPerfLofsThreshNotification, vdslPerfLofsThreshNotification,
vdslPerfLossThreshNotification, vdslPerfLossThreshNotification,
vdslPerfLprsThreshNotification, vdslPerfLprsThreshNotification,
vdslPerfESsThreshNotification, vdslPerfESsThreshNotification,
vdslPerfSESsThreshNotification,
vdslPerfUASsThreshNotification,
vdslInitFailureNotification vdslInitFailureNotification
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group supports notifications of significant "This group supports notifications of significant
conditions associated with VDSL Lines." conditions associated with VDSL Lines."
::= { vdslGroups 4 } ::= { vdslGroups 4 }
END END
7. Security Considerations Normative References
1) Blocking unauthorized access to the VDSL MIB via the element [ETSI2701] ETSI TS 101 270-1 V1.2.1 "Transmission and Multiplexing
management system is outside the scope of this document. It should (TM); Access transmission systems on metallic access
be noted that access to the MIB permits the unauthorized entity to cables; Very high speed Digital Subscriber Line (VDSL);
modify the profiles (section 6.4) such that both subscriber service Part 1: Functional requirements", October 1999.
and network operations can be interfered with. Subscriber service
can be altered by modifying any of a number of service
characteristics such as rate partitioning and maximum transmission
rates. Network operations can be impacted by modification of
notification thresholds such as lof thresholds.
2) There are a number of managed objects in this MIB that may be [ETSI2702] ETSI TS 101 270-2 V1.1.1 "Transmission and Multiplexing
considered to contain sensitive information. In particular, the (TM); Access transmission systems on metallic access
certain objects may be considered sensitive in many environments, cables; Very high speed Digital Subscriber Line (VDSL);
since it would allow an intruder to obtain information about which Part 1: Transceiver specification", February 2001.
vendor's equipment is in use on the network. Therefore, it may be
important in some environments to control read access to these
objects and possibly to even encrypt the values of these object
when sending them over the network via SNMP. Not all versions of
SNMP provide features for such a secure environment.
It is recommended that the implementors consider the security [ITU9931] ITU-T G.993.1 "Very-high-speed digital subscriber line
features as provided by the SNMPv3 framework. Specifically, the foundation", November 2001.
use of the User-based Security Model RFC 2574 [12] and the
View-based Access Control Model RFC 2575 [15] is recommended.
It is then a customer/user responsibility to ensure that the SNMP [RFC1901] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
entity giving access to an instance of this MIB, is properly "Introduction to Community-based SNMPv2", RFC 1901,
configured to give access to those objects only to those principals January 1996.
(users) that have legitimate rights to access them.
3) VDSL layer connectivity from the Vtur will permit the subscriber [RFC1905] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
to manipulate both the VDSL link directly and the VDSL embedded "Protocol Operations for Version 2 of the Simple Network
operations channel (EOC) for their own loop. For example, unchecked
or unfiltered fluctuations initiated by the subscriber could generate
sufficient notifications to potentially overwhelm either the
management interface to the network or the element manager.
It should be noted that interface indices in this MIB are maintained Expires December 17, 2002 [PAGE 66]
persistently. VACM data relating to these should be stored Management Protocol (SNMPv2)", RFC 1905, January 1996.
persistently.
8. Acknowledgments [RFC1906] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
"Transport Mappings for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1906, January 1996.
David Horton (CiTR) [RFC2119] Bradner, S., "Key Words for use in RFCs to Indicate
Requirement Levels", RFC 2119, March 1997.
9. References [RFC2493] Tesink, K., "Textual Conventions for MIB Modules Using
Performance History Based on 15 Minute Intervals", RFC
2493, January 1999.
[1] Harrington, D., Presuhn, R., and Wijnen, B., "An Architecture [RFC2571] Harrington, D., Presuhn, R. and B. Wijnen, "An
for Describing SNMP Management Frameworks", RFC 2571, April 1999. Architecture for Describing SNMP Management Frameworks",
RFC 2571, April 1999.
[2] Rose, M., and McCloghrie, K., "Structure and Identification of [RFC2572] Case, J., Harrington D., Presuhn, R. and B. Wijnen,
Management Information for TCP/IP-based Internets", STD 16, RFC "Message Processing and Dispatching for the Simple Network
1155, May 1990. Management Protocol (SNMP)", RFC 2572, April 1999.
[3] Rose, M., and McCloghrie, K., "Concise MIB Definitions", STD 16, [RFC2574] Blumenthal, U. and B. Wijnen, "User-based Security Model
RFC 1212, March 1991. (USM) for version 3 of the Simple Network Management
Protocol (SNMPv3)", RFC 2574, April 1999.
[4] Rose, M., "A Convention for Defining Traps for use with the [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
SNMP", RFC 1215, March 1991. Rose, M. and S. Waldbusser, "Structure of Management
Information Version 2 (SMIv2)", STD 58, RFC 2578, April
1999.
[5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
M., and Waldbusser, S., "Structure of Management Information Version Rose, M. and S. Waldbusser, "Textual Conventions for
2 (SMIv2)", STD 58, RFC 2578, April 1999. SMIv2", STD 58, RFC 2579, April 1999.
[6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
M., and Waldbusser, S., "Textual Conventions for SMIv2", STD 58, Rose, M. and S. Waldbusser, "Conformance Statements for
RFC 2579, April 1999. SMIv2", STD 58, RFC 2580, April 1999.
[7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, [RFC2662] Bathrick, G. and F. Ly, "Definitions of Managed Objects
M., and Waldbusser, S., "Conformance Statements for SMIv2", STD 58, for the ADSL Lines", RFC 2662, August 1999.
RFC 2580, April 1999.
[8] Case, J., Fedor, M., Schoffstall, M., and Davin, J., "Simple [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, June 2000.
[T1E1311] ANSI T1E1.4/2001-311, "Very-high-bit-rate Digital
Subscriber Line (VDSL) Metallic Interface, Part 1:
Functional Requirements and Common Specification", February
2001.
[T1E1011] ANSI T1E1.4/2001-011R3, "VDSL Metallic Interface, Part 2:
Technical Specification for a Single-Carrier Modulation
(SCM) Transceiver", November 2001.
Expires December 17, 2002 [PAGE 67]
[T1E1013] ANSI T1E1.4/2001-013R4, "VDSL Metallic Interface, Part 3:
Technical Specification for a Multi-Carrier Modulation
(MCM) Transceiver", November 2000.
Informative References
[RFC1155] Rose, M. and K. McCloghrie, "Structure and Identification
of Management Information for TCP/IP-based Internets", STD
16, RFC 1155, May 1990.
[RFC1157] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple
Network Management Protocol", STD 15, RFC 1157, May 1990. Network Management Protocol", STD 15, RFC 1157, May 1990.
[9] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., [RFC1212] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD
"Introduction to Community-based SNMPv2", RFC 1901, January 1996. 16, RFC 1212, March 1991.
[10] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., [RFC1215] Rose, M., "A Convention for Defining Traps for use with
"Transport Mappings for Version 2 of the Simple Network Management the SNMP", RFC 1215, March 1991.
Protocol (SNMPv2)", RFC 1906, January 1996.
[11] Case, J., Harrington D., Presuhn, R., and Wijnen, B., "Message [RFC2570] Case, J., Mundy, R., Partain, D. and B. Stewart,
Processing and Dispatching for the Simple Network Management "Introduction to Version 3 of the Internet-standard Network
Protocol (SNMP)", RFC 2572, April 1999. Management Framework", RFC 2570, April 1999.
[12] Blumenthal, U., and Wijnen, B., "User-based Security Model (USM) [RFC2573] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 Applications",
for version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 2573, April 1999.
RFC 2574, April 1999.
[13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol [RFC2575] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based
Operations for Version 2 of the Simple Network Management Protocol Access Control Model (VACM) for the Simple Network
(SNMPv2)", RFC 1905, January 1996. Management Protocol (SNMP)", RFC 2575, April 1999.
[14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC Security Considerations
2573, April 1999.
[15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access There are a number of management objects defined in this MIB that
Control Model (VACM) for the Simple Network Management Protocol have a MAX-ACCESS clause of read-write and/or read-create. Such
(SNMP)", RFC 2575, April 1999. objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on
network operations.
[16] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction VDSL layer connectivity from the Vtur will permit the subscriber
to Version 3 of the Internet-standard Network Management Framework", to manipulate both the VDSL link directly and the VDSL embedded
RFC 2570, April 1999. operations channel (EOC) for their own loop. For example, unchecked
or unfiltered fluctuations initiated by the subscriber could generate
sufficient notifications to potentially overwhelm either the
management interface to the network or the element manager.
[17] Bradner, S., "Key Words for use in RFCs to Indicate Requirement For this reason, there are a number of managed objects in this MIB
Levels", RFC 2119, March 1997. that may contain sensitive information. These are:
[18] Wang, Q., editor, Committee T1 - Telecommunications, vdslThresh15MinLofs
T1E1.4/2000-009R3, "VDSL Metallic Interface, Part 1: Functional vdslThresh15MinLoss
Requirements and Common Specification", February 19-23, 2001. vdslThresh15MinLprs
vdslThresh15MinESs
[19] Oksman, V., editor, Committee T1 - Telecommunications, Expires December 17, 2002 [PAGE 68]
T1E1.4/2000-011R3, "VDSL Metallic Interface, Part 2: Technical vdslThresh15MinSESs
Specification for a Single-Carrier Modulation (SCM) Transceiver", vdslThresh15MinUASs
February 19-23, 2001.
[20] Schelstraete, S., editor, Committee T1 - Telecommunications, It is thus important to control even GET access to these objects and
T1E1.4/2000-013R4, "VDSL Metallic Interface, Part 3: Technical possibly to even encrypt the values of these objects when sending
Specification of a Multi-Carrier Modulation Transceiver", November them over the network via SNMP. Not all versions of SNMP provide
13-17, 2000. features for such a secure environment.
[21] Tesink, K., "Textual Conventions for MIB Modules Using Further, notifications generated by agents implementing this MIB
Performance History Based on 15 Minute Intervals", RFC 2493, will contain the above threshold information.
January 1999.
[22] Bathrick, G., Ly, F., "Definitions of Managed Objects for the SNMPv1 by itself is not a secure environment. Even if the network
ADSL Lines", RFC 2662, August 1999. itself is secure (for example by using IPSec), even then, there is no
control as to who on the secure network is allowed to access and
GET/SET (read/change/create/delete) the objects in this MIB.
[23] McCloghrie, K., and Kastenholz, F., "The Interfaces Group MIB", It is recommended that the implementers consider the security
RFC 2863, June 2000. features as provided by the SNMPv3 framework. Specifically, the use
of the User-based Security Model RFC 2574 [12] and the View-
based Access Control Model RFC 2575 [15] is recommended.
10. Intellectual Property Notice It is then a customer/user responsibility to ensure that the SNMP
entity giving access to an instance of this MIB, is properly
configured to give access to the objects only to those principals
(users) that have legitimate rights to indeed GET or SET
(change/create/delete) them.
IANA Considerations
The VDSL-LINE-MIB MIB module requires the allocation of a single
object identifier for its MODULE-IDENTITY. IANA should allocate
this object identifier in the transmission subtree.
Acknowledgments
David Horton (CiTR)
Moti Morgenstern (Inovia)
Intellectual Property Notice
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances of claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to licenses to be made available, or the result of an attempt made to
obtain a general license or permission for the use of such obtain a general license or permission for the use of such
proprietary rights by implementors or users of this specification can proprietary rights by implementors or users of this specification can
Expires December 17, 2002 [PAGE 69]
be obtained from the IETF Secretariat. be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF Executive
Director. Director.
11. Authors' Addresses Authors' Addresses
Bob Ray
PESA Switching Systems, Inc.
330-A Wynn Drive
Huntsville, AL 35805 USA
Phone: +1 256 726 9200 ext. 142
Fax: +1 256 726 9271
EMail: rray@pesa.com
Rajesh Abbi Rajesh Abbi
Alcatel USA Alcatel USA
2912 Wake Forest Road 2912 Wake Forest Road
Raleigh, NC 27609-7860 USA Raleigh, NC 27609-7860 USA
Email: Rajesh.Abbi@usa.alcatel.com
Phone: +1 919 850 6194
Bob Ray Phone: +1 919 850 6194
E-mail: bob_ray_99@yahoo.com EMail: Rajesh.Abbi@alcatel.com
12. Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2002). All Rights Reserved. Copyright (C) The Internet Society (2002). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
skipping to change at line 2673 skipping to change at line 3782
English. English.
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Expires December 17, 2002 [PAGE 70]
 End of changes. 

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