vdslLineCoding |
.1.3.6.1.2.1.10.97.1.1.1.1.1 |
Specifies the VDSL coding type used on this line.
|
vdslLineType |
.1.3.6.1.2.1.10.97.1.1.1.1.2 |
Defines the type of VDSL physical line entity that exists,
by defining whether and how the line is channelized. If
the line is channelized, the value will be other than
noChannel(1). This object defines which channel type(s)
are supported. Defined values are:
noChannel(1) -- no channels exist
fastOnly(2) -- only fast channel exists
interleavedOnly(3) -- only interleaved channel exists
fastOrInterleaved(4) -- either fast or interleaved channel
-- exist, but only one at a time
fastAndInterleaved(5) -- both fast and interleaved channels
-- exist
Note that 'slow' and 'interleaved' refer to the same
channel. In the case that the line is channelized, the
manager can use the ifStackTable to determine the ifIndex
for the associated channel(s).
|
vdslLineConfProfile |
.1.3.6.1.2.1.10.97.1.1.1.1.3 |
The value of this object identifies the row in the VDSL
Line Configuration Profile Table, vdslLineConfProfileTable,
which applies for this VDSL line, and channels if
applicable.
This object MUST be maintained in a persistent manner.
|
vdslLineAlarmConfProfile |
.1.3.6.1.2.1.10.97.1.1.1.1.4 |
The value of this object identifies the row in the VDSL
Line Alarm Configuration Profile Table,
vdslLineAlarmConfProfileTable, which applies to this
VDSL line, and channels if applicable.
This object MUST be maintained in a persistent manner.
|
vdslPhysSide |
.1.3.6.1.2.1.10.97.1.1.2.1.1 |
Identifies whether the transceiver is the Vtuc or Vtur.
|
vdslPhysInvSerialNumber |
.1.3.6.1.2.1.10.97.1.1.2.1.2 |
The vendor specific string that identifies the
vendor equipment.
|
vdslPhysInvVendorID |
.1.3.6.1.2.1.10.97.1.1.2.1.3 |
The vendor ID code is a copy of the binary vendor
identification field expressed as readable characters
in hexadecimal notation.
|
vdslPhysInvVersionNumber |
.1.3.6.1.2.1.10.97.1.1.2.1.4 |
The vendor specific version number sent by this Vtu
as part of the initialization messages. It is a copy
of the binary version number field expressed as
readable characters in hexadecimal notation.
|
vdslPhysCurrSnrMgn |
.1.3.6.1.2.1.10.97.1.1.2.1.5 |
Noise Margin as seen by this Vtu with respect to its
received signal in 0.25dB. The effective range is
-31.75 to +31.75 dB.
|
vdslPhysCurrAtn |
.1.3.6.1.2.1.10.97.1.1.2.1.6 |
Measured difference in the total power transmitted by
the peer Vtu and the total power received by this Vtu.
The effective range is 0 to +63.75 dB.
|
vdslPhysCurrStatus |
.1.3.6.1.2.1.10.97.1.1.2.1.7 |
Indicates current state of the Vtu line. This is a
bit-map of possible conditions. The various bit
positions are:
0 noDefect There are no defects on the line.
1 lossOfFraming Vtu failure due to not receiving
a valid frame.
2 lossOfSignal Vtu failure due to not receiving
signal.
3 lossOfPower Vtu failure due to loss of power.
4 lossOfSignalQuality Loss of Signal Quality is declared
when the Noise Margin falls below
the Minimum Noise Margin, or the
bit-error-rate exceeds 10^-7.
5 lossOfLink Vtu failure due to inability to
link with peer Vtu. Set whenever
the transceiver is in the 'Warm
Start' state.
6 dataInitFailure Vtu failure during initialization
due to bit errors corrupting
startup exchange data.
7 configInitFailure Vtu failure during initialization
due to peer Vtu not able to
support requested configuration.
8 protocolInitFailure Vtu failure during initialization
due to incompatible protocol used
by the peer Vtu.
9 noPeerVtuPresent Vtu failure during initialization
due to no activation sequence
detected from peer Vtu.
This is intended to supplement ifOperStatus.
|
vdslPhysCurrOutputPwr |
.1.3.6.1.2.1.10.97.1.1.2.1.8 |
Measured total output power transmitted by this VTU.
This is the measurement that was reported during
the last activation sequence.
|
vdslPhysCurrAttainableRate |
.1.3.6.1.2.1.10.97.1.1.2.1.9 |
Indicates the maximum currently attainable data rate
in steps of 1000 bits/second by the Vtu. This value
will be equal to or greater than vdslPhysCurrLineRate.
Note that for SCM, the minimum and maximum data rates
are equal. Note: 1 kbps = 1000 bps.
|
vdslPhysCurrLineRate |
.1.3.6.1.2.1.10.97.1.1.2.1.10 |
Indicates the current data rate in steps of 1000
bits/second by the Vtu. This value will be less than
or equal to vdslPhysCurrAttainableRate. Note: 1 kbps =
1000 bps.
|
vdslChanInterleaveDelay |
.1.3.6.1.2.1.10.97.1.1.3.1.1 |
Interleave Delay for this channel.
Interleave delay applies only to the interleave
(slow) channel and defines the mapping (relative
spacing) between subsequent input bytes at the
interleaver input and their placement in the bit
stream at the interleaver output. Larger numbers
provide greater separation between consecutive
input bytes in the output bit stream allowing for
improved impulse noise immunity at the expense of
payload latency.
In the case where the ifType is fast(125), return
a value of zero.
|
vdslChanCrcBlockLength |
.1.3.6.1.2.1.10.97.1.1.3.1.2 |
Indicates the length of the channel data-block
on which the CRC operates.
|
vdslChanCurrTxRate |
.1.3.6.1.2.1.10.97.1.1.3.1.3 |
Actual transmit data rate on this channel. Note: 1
kbps = 1000 bps.
|
vdslChanCurrTxSlowBurstProtect |
.1.3.6.1.2.1.10.97.1.1.3.1.4 |
Actual level of impulse noise (burst) protection
for an interleaved (slow) channel. This parameter is
not applicable to fast channels. For fast channels,
a value of zero shall be returned.
|
vdslChanCurrTxFastFec |
.1.3.6.1.2.1.10.97.1.1.3.1.5 |
Actual Forward Error Correction (FEC) redundancy
related overhead for a fast channel. This parameter
is not applicable to an interleaved (slow) channel.
For interleaved channels, a value of zero shall be
returned.
|
vdslPerfDataValidIntervals |
.1.3.6.1.2.1.10.97.1.1.4.1.1 |
Valid Intervals per definition found in
HC-PerfHist-TC-MIB.
|
vdslPerfDataInvalidIntervals |
.1.3.6.1.2.1.10.97.1.1.4.1.2 |
Invalid Intervals per definition found in
HC-PerfHist-TC-MIB.
|
vdslPerfDataLofs |
.1.3.6.1.2.1.10.97.1.1.4.1.3 |
Count of seconds since the unit was last reset that there
was Loss of Framing.
|
vdslPerfDataLoss |
.1.3.6.1.2.1.10.97.1.1.4.1.4 |
Count of seconds since the unit was last reset that there
was Loss of Signal.
|
vdslPerfDataLprs |
.1.3.6.1.2.1.10.97.1.1.4.1.5 |
Count of seconds since the unit was last reset that there
was Loss of Power.
|
vdslPerfDataLols |
.1.3.6.1.2.1.10.97.1.1.4.1.6 |
Count of seconds since the unit was last reset that there
was Loss of Link.
|
vdslPerfDataESs |
.1.3.6.1.2.1.10.97.1.1.4.1.7 |
Count of Errored Seconds since the unit was last reset.
An Errored Second is a one-second interval containing one
or more CRC anomalies, or one or more LOS or LOF defects.
|
vdslPerfDataSESs |
.1.3.6.1.2.1.10.97.1.1.4.1.8 |
Count of Severely Errored Seconds since the unit was last
reset.
|
vdslPerfDataUASs |
.1.3.6.1.2.1.10.97.1.1.4.1.9 |
Count of Unavailable Seconds since the unit was last
reset.
|
vdslPerfDataInits |
.1.3.6.1.2.1.10.97.1.1.4.1.10 |
Count of the line initialization attempts since the unit
was last reset. This count includes both successful and
failed attempts.
|
vdslPerfDataCurr15MinTimeElapsed |
.1.3.6.1.2.1.10.97.1.1.4.1.11 |
Total elapsed seconds in this interval.
|
vdslPerfDataCurr15MinLofs |
.1.3.6.1.2.1.10.97.1.1.4.1.12 |
Count of seconds during this interval that there
was Loss of Framing.
|
vdslPerfDataCurr15MinLoss |
.1.3.6.1.2.1.10.97.1.1.4.1.13 |
Count of seconds during this interval that there
was Loss of Signal.
|
vdslPerfDataCurr15MinLprs |
.1.3.6.1.2.1.10.97.1.1.4.1.14 |
Count of seconds during this interval that there
was Loss of Power.
|
vdslPerfDataCurr15MinLols |
.1.3.6.1.2.1.10.97.1.1.4.1.15 |
Count of seconds during this interval that there
was Loss of Link.
|
vdslPerfDataCurr15MinESs |
.1.3.6.1.2.1.10.97.1.1.4.1.16 |
Count of Errored Seconds during this interval. An Errored
Second is a one-second interval containing one or more CRC
anomalies, or one or more LOS or LOF defects.
|
vdslPerfDataCurr15MinSESs |
.1.3.6.1.2.1.10.97.1.1.4.1.17 |
Count of Severely Errored Seconds during this interval.
|
vdslPerfDataCurr15MinUASs |
.1.3.6.1.2.1.10.97.1.1.4.1.18 |
Count of Unavailable Seconds during this interval.
|
vdslPerfDataCurr15MinInits |
.1.3.6.1.2.1.10.97.1.1.4.1.19 |
Count of the line initialization attempts during this
interval. This count includes both successful and
failed attempts.
|
vdslPerfData1DayValidIntervals |
.1.3.6.1.2.1.10.97.1.1.4.1.20 |
Valid Intervals per definition found in
HC-PerfHist-TC-MIB.
|
vdslPerfData1DayInvalidIntervals |
.1.3.6.1.2.1.10.97.1.1.4.1.21 |
Invalid Intervals per definition found in
HC-PerfHist-TC-MIB.
|
vdslPerfDataCurr1DayTimeElapsed |
.1.3.6.1.2.1.10.97.1.1.4.1.22 |
Number of seconds that have elapsed since the beginning
of the current 1-day interval.
|
vdslPerfDataCurr1DayLofs |
.1.3.6.1.2.1.10.97.1.1.4.1.23 |
Count of Loss of Framing (LOF) Seconds since the
beginning of the current 1-day interval.
|
vdslPerfDataCurr1DayLoss |
.1.3.6.1.2.1.10.97.1.1.4.1.24 |
Count of Loss of Signal (LOS) Seconds since the beginning
of the current 1-day interval.
|
vdslPerfDataCurr1DayLprs |
.1.3.6.1.2.1.10.97.1.1.4.1.25 |
Count of Loss of Power (LPR) Seconds since the beginning
of the current 1-day interval.
|
vdslPerfDataCurr1DayLols |
.1.3.6.1.2.1.10.97.1.1.4.1.26 |
Count of Loss of Link (LOL) Seconds since the beginning
of the current 1-day interval.
|
vdslPerfDataCurr1DayESs |
.1.3.6.1.2.1.10.97.1.1.4.1.27 |
Count of Errored Seconds (ES) since the beginning
of the current 1-day interval.
|
vdslPerfDataCurr1DaySESs |
.1.3.6.1.2.1.10.97.1.1.4.1.28 |
Count of Severely Errored Seconds (SES) since the
beginning of the current 1-day interval.
|
vdslPerfDataCurr1DayUASs |
.1.3.6.1.2.1.10.97.1.1.4.1.29 |
Count of Unavailable Seconds (UAS) since the beginning
of the current 1-day interval.
|
vdslPerfDataCurr1DayInits |
.1.3.6.1.2.1.10.97.1.1.4.1.30 |
Count of the line initialization attempts since the
beginning of the current 1-day interval. This count
includes both successful and failed attempts.
|
vdslPerfIntervalNumber |
.1.3.6.1.2.1.10.97.1.1.5.1.1 |
Performance Data Interval number 1 is the most recent
previous interval; interval 96 is 24 hours ago.
Intervals 2 to 96 are optional.
|
vdslPerfIntervalLofs |
.1.3.6.1.2.1.10.97.1.1.5.1.2 |
Count of seconds in the interval when there was Loss
of Framing.
|
vdslPerfIntervalLoss |
.1.3.6.1.2.1.10.97.1.1.5.1.3 |
Count of seconds in the interval when there was Loss
of Signal.
|
vdslPerfIntervalLprs |
.1.3.6.1.2.1.10.97.1.1.5.1.4 |
Count of seconds in the interval when there was Loss
of Power.
|
vdslPerfIntervalLols |
.1.3.6.1.2.1.10.97.1.1.5.1.5 |
Count of seconds in the interval when there was Loss
of Link.
|
vdslPerfIntervalESs |
.1.3.6.1.2.1.10.97.1.1.5.1.6 |
Count of Errored Seconds (ES) in the interval. An Errored
Second is a one-second interval containing one or more CRC
anomalies, one or more LOS or LOF defects.
|
vdslPerfIntervalSESs |
.1.3.6.1.2.1.10.97.1.1.5.1.7 |
Count of Severely Errored Seconds in the interval.
|
vdslPerfIntervalUASs |
.1.3.6.1.2.1.10.97.1.1.5.1.8 |
Count of Unavailable Seconds in the interval.
|
vdslPerfIntervalInits |
.1.3.6.1.2.1.10.97.1.1.5.1.9 |
Count of the line initialization attempts during this
interval. This count includes both successful and
failed attempts.
|
vdslPerf1DayIntervalNumber |
.1.3.6.1.2.1.10.97.1.1.6.1.1 |
History Data Interval number. Interval 1 is the most
recent previous day; interval 30 is 30 days ago. Intervals
2 to 30 are optional.
|
vdslPerf1DayIntervalMoniSecs |
.1.3.6.1.2.1.10.97.1.1.6.1.2 |
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.
|
vdslPerf1DayIntervalLofs |
.1.3.6.1.2.1.10.97.1.1.6.1.3 |
Count of Loss of Frame (LOF) Seconds during the 1-day
interval as measured by vdslPerf1DayIntervalMoniSecs.
|
vdslPerf1DayIntervalLoss |
.1.3.6.1.2.1.10.97.1.1.6.1.4 |
Count of Loss of Signal (LOS) Seconds during the 1-day
interval as measured by vdslPerf1DayIntervalMoniSecs.
|
vdslPerf1DayIntervalLprs |
.1.3.6.1.2.1.10.97.1.1.6.1.5 |
Count of Loss of Power (LPR) Seconds during the 1-day
interval as measured by vdslPerf1DayIntervalMoniSecs.
|
vdslPerf1DayIntervalLols |
.1.3.6.1.2.1.10.97.1.1.6.1.6 |
Count of Loss of Link (LOL) Seconds during the 1-day
interval as measured by vdslPerf1DayIntervalMoniSecs.
|
vdslPerf1DayIntervalESs |
.1.3.6.1.2.1.10.97.1.1.6.1.7 |
Count of Errored Seconds (ES) during the 1-day
interval as measured by vdslPerf1DayIntervalMoniSecs.
|
vdslPerf1DayIntervalSESs |
.1.3.6.1.2.1.10.97.1.1.6.1.8 |
Count of Severely Errored Seconds (SES) during the 1-day
interval as measured by vdslPerf1DayIntervalMoniSecs.
|
vdslPerf1DayIntervalUASs |
.1.3.6.1.2.1.10.97.1.1.6.1.9 |
Count of Unavailable Seconds (UAS) during the 1-day
interval as measured by vdslPerf1DayIntervalMoniSecs.
|
vdslPerf1DayIntervalInits |
.1.3.6.1.2.1.10.97.1.1.6.1.10 |
Count of the line initialization attempts during the
1-day interval as measured by vdslPerf1DayIntervalMoniSecs.
This count includes both successful and failed attempts.
|
vdslChanValidIntervals |
.1.3.6.1.2.1.10.97.1.1.7.1.1 |
Valid Intervals per definition found in
HC-PerfHist-TC-MIB.
|
vdslChanInvalidIntervals |
.1.3.6.1.2.1.10.97.1.1.7.1.2 |
Invalid Intervals per definition found in
HC-PerfHist-TC-MIB.
|
vdslChanFixedOctets |
.1.3.6.1.2.1.10.97.1.1.7.1.3 |
Count of corrected octets since the unit was last reset.
|
vdslChanBadBlks |
.1.3.6.1.2.1.10.97.1.1.7.1.4 |
Count of uncorrectable blocks since the unit was last
reset.
|
vdslChanCurr15MinTimeElapsed |
.1.3.6.1.2.1.10.97.1.1.7.1.5 |
Total elapsed seconds in this interval.
|
vdslChanCurr15MinFixedOctets |
.1.3.6.1.2.1.10.97.1.1.7.1.6 |
Count of corrected octets in this interval.
|
vdslChanCurr15MinBadBlks |
.1.3.6.1.2.1.10.97.1.1.7.1.7 |
Count of uncorrectable blocks in this interval.
|
vdslChan1DayValidIntervals |
.1.3.6.1.2.1.10.97.1.1.7.1.8 |
Valid Intervals per definition found in
HC-PerfHist-TC-MIB.
|
vdslChan1DayInvalidIntervals |
.1.3.6.1.2.1.10.97.1.1.7.1.9 |
Invalid Intervals per definition found in
HC-PerfHist-TC-MIB.
|
vdslChanCurr1DayTimeElapsed |
.1.3.6.1.2.1.10.97.1.1.7.1.10 |
Number of seconds that have elapsed since the beginning
of the current 1-day interval.
|
vdslChanCurr1DayFixedOctets |
.1.3.6.1.2.1.10.97.1.1.7.1.11 |
Count of corrected octets since the beginning of the
current 1-day interval.
|
vdslChanCurr1DayBadBlks |
.1.3.6.1.2.1.10.97.1.1.7.1.12 |
Count of uncorrectable blocks since the beginning of the
current 1-day interval.
|
vdslChanIntervalNumber |
.1.3.6.1.2.1.10.97.1.1.8.1.1 |
Performance Data Interval number 1 is the most recent
previous interval; interval 96 is 24 hours ago.
Intervals 2 to 96 are optional.
|
vdslChanIntervalFixedOctets |
.1.3.6.1.2.1.10.97.1.1.8.1.2 |
Count of corrected octets in this interval.
|
vdslChanIntervalBadBlks |
.1.3.6.1.2.1.10.97.1.1.8.1.3 |
Count of uncorrectable blocks in this interval.
|
vdslChan1DayIntervalNumber |
.1.3.6.1.2.1.10.97.1.1.9.1.1 |
History Data Interval number. Interval 1 is the most
recent previous day; interval 30 is 30 days ago. Intervals
2 to 30 are optional.
|
vdslChan1DayIntervalMoniSecs |
.1.3.6.1.2.1.10.97.1.1.9.1.2 |
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.
|
vdslChan1DayIntervalFixedOctets |
.1.3.6.1.2.1.10.97.1.1.9.1.3 |
Count of corrected octets in this interval.
|
vdslChan1DayIntervalBadBlks |
.1.3.6.1.2.1.10.97.1.1.9.1.4 |
Count of uncorrectable blocks in this interval.
|
vdslLineConfProfileName |
.1.3.6.1.2.1.10.97.1.1.11.1.1 |
This object identifies a row in this table.
A default profile with an index of 'DEFVAL', will
always exist and its parameters will be set to vendor
specific values, unless otherwise specified in this
document.
|
vdslLineConfDownRateMode |
.1.3.6.1.2.1.10.97.1.1.11.1.2 |
Specifies the rate selection behavior for the line
in the downstream direction.
manual(1) forces the rate to the configured rate
adaptAtInit(2) adapts the line based upon line quality.
|
vdslLineConfUpRateMode |
.1.3.6.1.2.1.10.97.1.1.11.1.3 |
Specifies the rate selection behavior for the line
in the upstream direction.
manual(1) forces the rate to the configured rate
adaptAtInit(2) adapts the line based upon line quality.
|
vdslLineConfDownMaxPwr |
.1.3.6.1.2.1.10.97.1.1.11.1.4 |
Specifies the maximum aggregate downstream power
level in the range 0 to 14.5 dBm.
|
vdslLineConfUpMaxPwr |
.1.3.6.1.2.1.10.97.1.1.11.1.5 |
Specifies the maximum aggregate upstream power
level in the range 0 to 14.5 dBm.
|
vdslLineConfDownMaxSnrMgn |
.1.3.6.1.2.1.10.97.1.1.11.1.6 |
Specifies the maximum downstream Signal/Noise Margin
in units of 0.25 dB, for a range of 0 to 31.75 dB.
|
vdslLineConfDownMinSnrMgn |
.1.3.6.1.2.1.10.97.1.1.11.1.7 |
Specifies the minimum downstream Signal/Noise Margin
in units of 0.25 dB, for a range of 0 to 31.75 dB.
|
vdslLineConfDownTargetSnrMgn |
.1.3.6.1.2.1.10.97.1.1.11.1.8 |
Specifies the target downstream Signal/Noise Margin
in units of 0.25 dB, for a range of 0 to 31.75 dB.
This is the Noise Margin the transceivers must achieve
with a BER of 10^-7 or better to successfully complete
initialization.
|
vdslLineConfUpMaxSnrMgn |
.1.3.6.1.2.1.10.97.1.1.11.1.9 |
Specifies the maximum upstream Signal/Noise Margin
in units of 0.25 dB, for a range of 0 to 31.75 dB.
|
vdslLineConfUpMinSnrMgn |
.1.3.6.1.2.1.10.97.1.1.11.1.10 |
Specifies the minimum upstream Signal/Noise Margin
in units of 0.25 dB, for a range of 0 to 31.75 dB.
|
vdslLineConfUpTargetSnrMgn |
.1.3.6.1.2.1.10.97.1.1.11.1.11 |
Specifies the target upstream Signal/Noise Margin in
units of 0.25 dB, for a range of 0 to 31.75 dB. This
is the Noise Margin the transceivers must achieve with
a BER of 10^-7 or better to successfully complete
initialization.
|
vdslLineConfDownFastMaxDataRate |
.1.3.6.1.2.1.10.97.1.1.11.1.12 |
Specifies the maximum downstream fast channel
data rate in steps of 1000 bits/second.
|
vdslLineConfDownFastMinDataRate |
.1.3.6.1.2.1.10.97.1.1.11.1.13 |
Specifies the minimum downstream fast channel
data rate in steps of 1000 bits/second.
|
vdslLineConfDownSlowMaxDataRate |
.1.3.6.1.2.1.10.97.1.1.11.1.14 |
Specifies the maximum downstream slow channel
data rate in steps of 1000 bits/second.
The maximum aggregate downstream transmit speed
of the line can be derived from the sum of maximum
downstream fast and slow channel data rates.
|
vdslLineConfDownSlowMinDataRate |
.1.3.6.1.2.1.10.97.1.1.11.1.15 |
Specifies the minimum downstream slow channel
data rate in steps of 1000 bits/second.
The minimum aggregate downstream transmit speed
of the line can be derived from the sum of minimum
downstream fast and slow channel data rates.
|
vdslLineConfUpFastMaxDataRate |
.1.3.6.1.2.1.10.97.1.1.11.1.16 |
Specifies the maximum upstream fast channel
data rate in steps of 1000 bits/second.
The maximum aggregate upstream transmit speed
of the line can be derived from the sum of maximum
upstream fast and slow channel data rates.
|
vdslLineConfUpFastMinDataRate |
.1.3.6.1.2.1.10.97.1.1.11.1.17 |
Specifies the minimum upstream fast channel
data rate in steps of 1000 bits/second.
The minimum aggregate upstream transmit speed
of the line can be derived from the sum of minimum
upstream fast and slow channel data rates.
|
vdslLineConfUpSlowMaxDataRate |
.1.3.6.1.2.1.10.97.1.1.11.1.18 |
Specifies the maximum upstream slow channel
data rate in steps of 1000 bits/second.
|
vdslLineConfUpSlowMinDataRate |
.1.3.6.1.2.1.10.97.1.1.11.1.19 |
Specifies the minimum upstream slow channel
data rate in steps of 1000 bits/second.
|
vdslLineConfDownRateRatio |
.1.3.6.1.2.1.10.97.1.1.11.1.20 |
For dynamic rate adaptation at startup, the allocation
of data rate in excess of the minimum data rate for each
channel is controlled by the object. This object specifies
the ratio of the allocation of the excess data rate between
the fast and the slow channels. This allocation represents
downstream Fast Channel Allocation / Slow Channel
Allocation.
|
vdslLineConfUpRateRatio |
.1.3.6.1.2.1.10.97.1.1.11.1.21 |
For dynamic rate adaptation at startup, the allocation
of data rate in excess of the minimum data rate for each
channel is controlled by the object. This object specifies
the ratio of the allocation of the excess data rate between
the fast and the slow channels. This allocation represents
upstream Fast Channel Allocation/Slow Channel Allocation.
|
vdslLineConfDownMaxInterDelay |
.1.3.6.1.2.1.10.97.1.1.11.1.22 |
Specifies the maximum interleave delay for the
downstream slow channel.
|
vdslLineConfUpMaxInterDelay |
.1.3.6.1.2.1.10.97.1.1.11.1.23 |
Specifies the maximum interleave delay for the
upstream slow channel.
|
vdslLineConfDownPboControl |
.1.3.6.1.2.1.10.97.1.1.11.1.24 |
Downstream power backoff (PBO) control for this
line. For transceivers which do not support downstream
PBO control, this object MUST be fixed at disabled(1).
If auto(2) is selected, the transceiver will automatically
adjust the power backoff. If manual(3) is selected,
then the transceiver will use the value from
vdslLineConfDownPboLevel.
|
vdslLineConfUpPboControl |
.1.3.6.1.2.1.10.97.1.1.11.1.25 |
Upstream power backoff (PBO) control for this
line. For transceivers which do not support upstream
PBO control, this object MUST be fixed at disabled(1).
If auto(2) is selected, the transceiver will automatically
adjust the power backoff. If manual(3) is selected,
then the transceiver will use the value from
vdslLineConfUpPboLevel.
|
vdslLineConfDownPboLevel |
.1.3.6.1.2.1.10.97.1.1.11.1.26 |
Specifies the downstream backoff level to be used
when vdslLineConfDownPboControl = manual(3).
|
vdslLineConfUpPboLevel |
.1.3.6.1.2.1.10.97.1.1.11.1.27 |
Specifies the upstream backoff level to be used
when vdslLineConfUpPboControl = manual(3).
|
vdslLineConfDeploymentScenario |
.1.3.6.1.2.1.10.97.1.1.11.1.28 |
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. Changes to this value will have
no effect on the transceiver.
|
vdslLineConfAdslPresence |
.1.3.6.1.2.1.10.97.1.1.11.1.29 |
Indicates presence of ADSL service in the associated
cable bundle/binder.
none(1) indicates no ADSL service in the bundle
adslOverPots(2) indicates ADSL service over POTS is
present in the bundle
adslOverISDN(3) indicates ADSL service over ISDN is
present in the bundle
|
vdslLineConfApplicableStandard |
.1.3.6.1.2.1.10.97.1.1.11.1.30 |
The VDSL standard to be used for the line.
ansi(1) indicates ANSI standard
etsi(2) indicates ETSI standard
itu(3) indicates ITU standard
other(4) indicates a standard other than the above.
|
vdslLineConfBandPlan |
.1.3.6.1.2.1.10.97.1.1.11.1.31 |
The VDSL band plan to be used for the line.
bandPlan997(1) is to be used for
ITU-T G.993.1 Bandplan-B
ETSI Bandplan
ANSI Plan 997
bandPlan998(2) is to be used for
ITU-T G.993.1 Bandplan-A
ANSI Plan 998
bandPlanFx(3) is to be used for
ITU-T G.993.1 Bandplan-C.
other(4) is to be used for
non-standard bandplans.
If this object is set to bandPlanFx(3), then the
object vdslLineConfBandPlanFx MUST also be set.
|
vdslLineConfBandPlanFx |
.1.3.6.1.2.1.10.97.1.1.11.1.32 |
The frequency limit between bands D2 and U2 when
vdslLineConfBandPlan is set to bandPlanFx(3).
|
vdslLineConfBandOptUsage |
.1.3.6.1.2.1.10.97.1.1.11.1.33 |
Defines the VDSL link use of the optional frequency
range [25kHz - 138kHz] (Opt).
unused(1) indicates Opt is unused
upstream(2) indicates Opt usage is for upstream
downstream(3) indicates Opt usage is for downstream.
|
vdslLineConfUpPsdTemplate |
.1.3.6.1.2.1.10.97.1.1.11.1.34 |
The upstream PSD template to be used for the line.
Here, templateMask1(1) refers to a notched mask that
limits the transmitted PSD within the internationally
standardized HAM (Handheld Amateur Radio) radio bands,
while templateMask2(2) refers to an unnotched mask.
The masks themselves depend upon the applicable
standard being used (vdslLineConfApplicableStandard).
|
vdslLineConfDownPsdTemplate |
.1.3.6.1.2.1.10.97.1.1.11.1.35 |
The downstream PSD template to be used for the line.
Here, templateMask1(1) refers to a notched mask that
limits the transmitted PSD within the internationally
standardized HAM (Handheld Amateur Radio) radio bands,
while templateMask2(2) refers to an unnotched mask.
The masks themselves depend upon the applicable
standard being used (vdslLineConfApplicableStandard).
|
vdslLineConfHamBandMask |
.1.3.6.1.2.1.10.97.1.1.11.1.36 |
The transmit power spectral density mask code, used
to avoid interference with HAM (Handheld Amateur Radio)
radio bands by introducing power control (notching) in one
or more of these bands.
Amateur radio band notching is defined in the VDSL
spectrum as follows:
Band Start Frequency Stop Frequency
---- ------------------ --------------------------------
30m 1810 kHz 2000 kHz
40m 3500 kHz 3800 kHz (ETSI); 4000 kHz (ANSI)
80m 7000 kHz 7100 kHz (ETSI); 7300 kHz (ANSI)
160m 10100 kHz 10150 kHz
Notching for each standard band can be enabled or disabled
via the bit mask.
Two custom notches may be specified. If either of these
are enabled via the bit mask, then the following objects
MUST be specified:
If customNotch1 is enabled, then both
vdslLineConfCustomNotch1Start
vdslLineConfCustomNotch1Stop
MUST be specified.
If customNotch2 is enabled, then both
vdslLineConfCustomNotch2Start
vdslLineConfCustomNotch2Stop
MUST be specified.
|
vdslLineConfCustomNotch1Start |
.1.3.6.1.2.1.10.97.1.1.11.1.37 |
Specifies the start frequency of custom HAM (Handheld
Amateur Radio) notch 1. vdslLineConfCustomNotch1Start MUST
be less than or equal to vdslLineConfCustomNotch1Stop.
|
vdslLineConfCustomNotch1Stop |
.1.3.6.1.2.1.10.97.1.1.11.1.38 |
Specifies the stop frequency of custom HAM (Handheld
Amateur Radio) notch 1. vdslLineConfCustomNotch1Stop MUST
be greater than or equal to vdslLineConfCustomNotch1Start.
|
vdslLineConfCustomNotch2Start |
.1.3.6.1.2.1.10.97.1.1.11.1.39 |
Specifies the start frequency of custom HAM (Handheld
Amateur Radio) notch 2. vdslLineConfCustomNotch2Start MUST
be less than or equal to vdslLineConfCustomNotch2Stop.
|
vdslLineConfCustomNotch2Stop |
.1.3.6.1.2.1.10.97.1.1.11.1.40 |
Specifies the stop frequency of custom HAM (Handheld
Amateur Radio) notch 2. vdslLineConfCustomNotch2Stop MUST
be greater than or equal to vdslLineConfCustomNotch2Start.
|
vdslLineConfDownTargetSlowBurst |
.1.3.6.1.2.1.10.97.1.1.11.1.41 |
Specifies the target level of impulse noise (burst)
protection for an interleaved (slow) channel.
|
vdslLineConfUpTargetSlowBurst |
.1.3.6.1.2.1.10.97.1.1.11.1.42 |
Specifies the target level of impulse noise (burst)
protection for an interleaved (slow) channel.
|
vdslLineConfDownMaxFastFec |
.1.3.6.1.2.1.10.97.1.1.11.1.43 |
This parameter provisions the maximum level of Forward
Error Correction (FEC) redundancy related overhead to
be maintained for a fast channel.
|
vdslLineConfUpMaxFastFec |
.1.3.6.1.2.1.10.97.1.1.11.1.44 |
This parameter provisions the maximum level of Forward
Error Correction (FEC) redundancy related overhead to
be maintained for a fast channel.
|
vdslLineConfLineType |
.1.3.6.1.2.1.10.97.1.1.11.1.45 |
This parameter provisions the VDSL physical entity at
start-up by defining whether and how the line will be
channelized, i.e., which channel type(s) are supported.
If the line is to be channelized, the value will be other
than noChannel(1).
This configuration can be activated only during start-up.
Afterwards, the value of vdslLineType coincides with the
value of vdslLineConfLineType. Depending on this value,
the corresponding entries in the ifTable for the
interleaved and the fast channels are enabled or disabled
according to the value of their ifOperStatus.
Defined values are:
noChannel(1) -- no channels exist
fastOnly(2) -- only fast channel exists
interleavedOnly(3) -- only interleaved channel exists
fastOrInterleaved(4) -- either fast or interleaved channel
-- exists, but only one at a time
fastAndInterleaved(5) -- both fast and interleaved channels
-- exist
Note that 'slow' and 'interleaved' refer to the same
channel.
|
vdslLineConfProfRowStatus |
.1.3.6.1.2.1.10.97.1.1.11.1.46 |
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.
An 'active' profile may be modified at any time. Note
that some changes may require that any referenced lines be
restarted (e.g., vdslLineConfLineType).
|
vdslLineAlarmConfProfileName |
.1.3.6.1.2.1.10.97.1.1.20.1.1 |
The name for this profile as specified by an
administrator.
|
vdslLineAlarmConfThresh15MinLofs |
.1.3.6.1.2.1.10.97.1.1.20.1.2 |
This object configures the threshold for the number of
loss of frame seconds (lofs) within any given 15-minute
performance data collection interval. If the value of
loss of frame seconds in a particular 15-minute collection
interval reaches/exceeds this value, a
vdslPerfLofsThreshNotification notification will be
generated. No more than one notification will be sent
per interval.
|
vdslLineAlarmConfThresh15MinLoss |
.1.3.6.1.2.1.10.97.1.1.20.1.3 |
This object configures the threshold for the number of
loss of signal seconds (loss) within any given 15-minute
performance data collection interval. If the value of
loss of signal seconds in a particular 15-minute
collection interval reaches/exceeds this value, a
vdslPerfLossThreshNotification notification will be
generated. One notification will be sent per interval
per endpoint.
|
vdslLineAlarmConfThresh15MinLprs |
.1.3.6.1.2.1.10.97.1.1.20.1.4 |
This object configures the threshold for the number of
loss of power seconds (lprs) within any given 15-minute
performance data collection interval. If the value of
loss of power seconds in a particular 15-minute collection
interval reaches/exceeds this value, a
vdslPerfLprsThreshNotification notification will be
generated. No more than one notification will be sent
per interval.
|
vdslLineAlarmConfThresh15MinLols |
.1.3.6.1.2.1.10.97.1.1.20.1.5 |
This object configures the threshold for the number of
loss of link seconds (lols) within any given 15-minute
performance data collection interval. If the value of
loss of power seconds in a particular 15-minute collection
interval reaches/exceeds this value, a
vdslPerfLolsThreshNotification notification will be
generated. No more than one notification will be sent
per interval.
|
vdslLineAlarmConfThresh15MinESs |
.1.3.6.1.2.1.10.97.1.1.20.1.6 |
This object configures the threshold for the number of
errored seconds (ESs) within any given 15-minute
performance data collection interval. If the value of
errored seconds in a particular 15-minute collection
interval reaches/exceeds this value, a
vdslPerfESsThreshNotification notification will be
generated. No more than one notification will be sent
per interval.
|
vdslLineAlarmConfThresh15MinSESs |
.1.3.6.1.2.1.10.97.1.1.20.1.7 |
This object configures the threshold for the number of
severely errored seconds (SESs) within any given 15-minute
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.
|
vdslLineAlarmConfThresh15MinUASs |
.1.3.6.1.2.1.10.97.1.1.20.1.8 |
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.
|
vdslLineAlarmConfInitFailure |
.1.3.6.1.2.1.10.97.1.1.20.1.9 |
This object specifies if a vdslInitFailureNotification
notification will be generated if an initialization
failure occurs.
|
vdslLineAlarmConfProfRowStatus |
.1.3.6.1.2.1.10.97.1.1.20.1.10 |
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.
An 'active' profile may be modified at any time.
|