VDSL-LINE-MIB

MIB Reference — IPNetwork Monitor

All MIBsVDSL-LINE-MIB

Organization: ADSLMIB Working Group

Last Updated: 2004-02-19

Category: DSL and Broadband, Network Interfaces

Description:

Manages Very High Speed DSL (VDSL) line interfaces, providing configuration and monitoring of VDSL physical-layer parameters (RFC 3728).

Imported Objects

From HC-PerfHist-TC-MIB

HCPerfCurrentCount
HCPerfIntervalCount
HCPerfIntervalThreshold
HCPerfInvalidIntervals
HCPerfTimeElapsed
HCPerfValidIntervals

From HCNUM-TC

ZeroBasedCounter64

From IF-MIB

ifIndexOBJECT-TYPE

From SNMP-FRAMEWORK-MIB

SnmpAdminString

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

Gauge32
Integer32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
Unsigned32
transmission

From SNMPv2-TC

RowStatus
TEXTUAL-CONVENTION
TruthValue

What Is VDSL-LINE-MIB?

VDSL-LINE-MIB is an IETF standards-based MIB (RFC 3728) for managing Very High Speed Digital Subscriber Line (VDSL) physical-layer transceivers, applicable to any vendor's VDSL modem or DSLAM line card rather than a single manufacturer. It exposes configuration and physical-layer data for each VDSL line, including line coding, line type, configuration/alarm profiles, and per-transceiver physical inventory such as vendor ID and serial number, tracked per line-end (CO or CPE side) via vdslPhysSide. For monitoring, it lets an operator watch the software/configuration status of each line (profile assignment, coding mode) and hardware identity/inventory (transceiver vendor and serial number), which supports fault isolation when a line degrades or a transceiver is replaced/swapped unexpectedly. It is designed to require no management communication between the two line-end agents, relying instead on standard ifTable integration (IF-MIB) since each VDSL line appears as an interface. It is typically deployed on DSLAMs and VDSL customer-premises modems in broadband access networks, and an operator troubleshooting a single vdsl line typically polls this MIB per interface to confirm its coding and profile settings match provisioning intent.

IPNetwork Monitor allows you to monitor SNMP objects defined in VDSL-LINE-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

What Can Be Monitored

  • line coding/type
  • configuration and alarm profiles
  • per-side transceiver inventory (vendor ID, serial number)
  • line alarms/notifications

Supported Devices

  • vendor-neutral, standards-based MIB, not tied to a specific manufacturer, applies to DSLAMs and VDSL modems/transceivers

Monitoring Examples

An operator can poll vdslLineTable/vdslLineEntry for vdslLineCoding and vdslLineType to confirm a line's modulation and configuration profile (vdslLineConfProfile, vdslLineAlarmConfProfile) match provisioning intent, and detect drift after a firmware update. Querying vdslPhysTable/vdslPhysEntry with vdslPhysSide distinguishes the CO-end from the CPE-end transceiver on the same line, while vdslPhysInvVendorID and vdslPhysInvSerialNumber reveal the actual hardware installed -- useful for spotting an unauthorized or mismatched transceiver swap. Alarms surfaced under vdslNotifications combined with the alarm configuration profile indicate when a line has crossed a fault threshold.

OIDs
OID symbolicOID numericTypeAccessDescription
vdslMIB1.3.6.1.2.1.10.97The MIB module defining objects for the management of a pair of VDSL transceivers at each end of the VDSL line. Each such line has an entry in an ifTable which may include multiple transceiver lines. An agent may reside at either end of the VDSL line. However, the MIB is designed to require no management communication between them beyond that inherent in the low-level VDSL line protocol. The agent may monitor and control this protocol for its needs. VDSL lines may support optional Fast or Interleaved channels. If these are supported, additional entries corresponding to the supported channels must be created in the ifTable. Thus a VDSL line that supports both channels will have three entries in the ifTable, one for each physical, fast, and interleaved, whose ifType values are equal to vdsl(97), fast(125), and interleaved(124), respectively. The ifStackTable is used to represent the relationship between the entries. Naming Conventions: Vtuc -- (VTUC) transceiver at near (Central) end of line Vtur -- (VTUR) transceiver at Remote end of line Vtu -- One of either Vtuc or Vtur Curr -- Current Prev -- Previous Atn -- Attenuation ES -- Errored Second. SES -- Severely Errored Second UAS -- Unavailable Second LCS -- Line Code Specific Lof -- Loss of Frame Lol -- Loss of Link Los -- Loss of Signal Lpr -- Loss of Power xxxs -- Sum of Seconds in which xxx has occured (e.g., xxx = Lof, Los, Lpr, Lol) Max -- Maximum Mgn -- Margin Min -- Minimum Psd -- Power Spectral Density Snr -- Signal to Noise Ratio Tx -- Transmit Blks -- Blocks Copyright (C) The Internet Society (2004). This version of this MIB module is part of RFC 3728: see the RFC itself for full legal notices.
vdslLineMib1.3.6.1.2.1.10.97.1
vdslNotifications1.3.6.1.2.1.10.97.1.0
NTF vdslPerfLofsThreshNotification1.3.6.1.2.1.10.97.1.0.1Loss of Framing 15-minute interval threshold (vdslLineAlarmConfThresh15MinLofs) reached.
NTF vdslPerfLossThreshNotification1.3.6.1.2.1.10.97.1.0.2Loss of Signal 15-minute interval threshold (vdslLineAlarmConfThresh15MinLoss) reached.
NTF vdslPerfLprsThreshNotification1.3.6.1.2.1.10.97.1.0.3Loss of Power 15-minute interval threshold (vdslLineAlarmConfThresh15MinLprs) reached.
NTF vdslPerfLolsThreshNotification1.3.6.1.2.1.10.97.1.0.4Loss of Link 15-minute interval threshold (vdslLineAlarmConfThresh15MinLols) reached.
NTF vdslPerfESsThreshNotification1.3.6.1.2.1.10.97.1.0.5Errored Seconds 15-minute interval threshold (vdslLineAlarmConfThresh15MinESs) reached.
NTF vdslPerfSESsThreshNotification1.3.6.1.2.1.10.97.1.0.6Severely Errored Seconds 15-minute interval threshold (vdslLineAlarmConfThresh15MinSESs) reached.
NTF vdslPerfUASsThreshNotification1.3.6.1.2.1.10.97.1.0.7Unavailable Seconds 15-minute interval threshold (vdslLineAlarmConfThresh15MinUASs) reached.
NTF vdslDownMaxSnrMgnNotification1.3.6.1.2.1.10.97.1.0.8The downstream Signal to Noise Margin exceeded vdslLineConfDownMaxSnrMgn. The object vdslPhysCurrSnrMgn will contain the Signal to Noise margin as measured by the VTU-R.
NTF vdslDownMinSnrMgnNotification1.3.6.1.2.1.10.97.1.0.9The downstream Signal to Noise Margin fell below vdslLineConfDownMinSnrMgn. The object vdslPhysCurrSnrMgn will contain the Signal to Noise margin as measured by the VTU-R.
NTF vdslUpMaxSnrMgnNotification1.3.6.1.2.1.10.97.1.0.10The upstream Signal to Noise Margin exceeded vdslLineConfUpMaxSnrMgn. The object vdslPhysCurrSnrMgn will contain the Signal to Noise margin as measured by the VTU-C.
NTF vdslUpMinSnrMgnNotification1.3.6.1.2.1.10.97.1.0.11The upstream Signal to Noise Margin fell below vdslLineConfUpMinSnrMgn. The object vdslPhysCurrSnrMgn will contain the Signal to Noise margin as measured by the VTU-C.
NTF vdslInitFailureNotification1.3.6.1.2.1.10.97.1.0.12Vtu initialization failed. See vdslPhysCurrStatus for potential reasons.
vdslMibObjects1.3.6.1.2.1.10.97.1.1
vdslLineTable1.3.6.1.2.1.10.97.1.1.1not-accessibleThis table includes common attributes describing both ends of the line. It is required for all VDSL physical interfaces. VDSL physical interfaces are those ifEntries where ifType is equal to vdsl(97).
vdslLineEntry1.3.6.1.2.1.10.97.1.1.1.1not-accessibleAn entry in the vdslLineTable.
VDS vdslLineCoding1.3.6.1.2.1.10.97.1.1.1.1.1VdslLineCodingTyperead-onlySpecifies the VDSL coding type used on this line.
INT vdslLineType1.3.6.1.2.1.10.97.1.1.1.1.2INTEGERread-onlyDefines 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).
STR vdslLineConfProfile1.3.6.1.2.1.10.97.1.1.1.1.3SnmpAdminStringread-writeThe 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.
STR vdslLineAlarmConfProfile1.3.6.1.2.1.10.97.1.1.1.1.4SnmpAdminStringread-writeThe 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.
vdslPhysTable1.3.6.1.2.1.10.97.1.1.2not-accessibleThis table provides one row for each Vtu. Each row contains the Physical Layer Parameters table for that Vtu. VDSL physical interfaces are those ifEntries where ifType is equal to vdsl(97).
vdslPhysEntry1.3.6.1.2.1.10.97.1.1.2.1not-accessibleAn entry in the vdslPhysTable.
VDS vdslPhysSide1.3.6.1.2.1.10.97.1.1.2.1.1VdslLineEntitynot-accessibleIdentifies whether the transceiver is the Vtuc or Vtur.
STR vdslPhysInvSerialNumber1.3.6.1.2.1.10.97.1.1.2.1.2SnmpAdminStringread-onlyThe vendor specific string that identifies the vendor equipment.
STR vdslPhysInvVendorID1.3.6.1.2.1.10.97.1.1.2.1.3SnmpAdminStringread-onlyThe vendor ID code is a copy of the binary vendor identification field expressed as readable characters in hexadecimal notation.
STR vdslPhysInvVersionNumber1.3.6.1.2.1.10.97.1.1.2.1.4SnmpAdminStringread-onlyThe 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.
I32 vdslPhysCurrSnrMgn1.3.6.1.2.1.10.97.1.1.2.1.5Integer32read-onlyNoise 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.
G32 vdslPhysCurrAtn1.3.6.1.2.1.10.97.1.1.2.1.6Gauge32read-onlyMeasured 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.
BIT vdslPhysCurrStatus1.3.6.1.2.1.10.97.1.1.2.1.7Bitsread-onlyIndicates 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.
I32 vdslPhysCurrOutputPwr1.3.6.1.2.1.10.97.1.1.2.1.8Integer32read-onlyMeasured total output power transmitted by this VTU. This is the measurement that was reported during the last activation sequence.
G32 vdslPhysCurrAttainableRate1.3.6.1.2.1.10.97.1.1.2.1.9Gauge32read-onlyIndicates 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.
G32 vdslPhysCurrLineRate1.3.6.1.2.1.10.97.1.1.2.1.10Gauge32read-onlyIndicates 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.
vdslChanTable1.3.6.1.2.1.10.97.1.1.3not-accessibleThis table provides one row for each Vtu channel. VDSL channel interfaces are those ifEntries where ifType is equal to interleave(124) or fast(125).
vdslChanEntry1.3.6.1.2.1.10.97.1.1.3.1not-accessibleAn entry in the vdslChanTable.
G32 vdslChanInterleaveDelay1.3.6.1.2.1.10.97.1.1.3.1.1Gauge32read-onlyInterleave 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.
G32 vdslChanCrcBlockLength1.3.6.1.2.1.10.97.1.1.3.1.2Gauge32read-onlyIndicates the length of the channel data-block on which the CRC operates.
G32 vdslChanCurrTxRate1.3.6.1.2.1.10.97.1.1.3.1.3Gauge32read-onlyActual transmit data rate on this channel. Note: 1 kbps = 1000 bps.
G32 vdslChanCurrTxSlowBurstProtect1.3.6.1.2.1.10.97.1.1.3.1.4Gauge32read-onlyActual 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.
G32 vdslChanCurrTxFastFec1.3.6.1.2.1.10.97.1.1.3.1.5Gauge32read-onlyActual 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.
vdslPerfDataTable1.3.6.1.2.1.10.97.1.1.4not-accessibleThis table provides one row for each VDSL physical interface. VDSL physical interfaces are those ifEntries where ifType is equal to vdsl(97).
vdslPerfDataEntry1.3.6.1.2.1.10.97.1.1.4.1not-accessibleAn entry in the vdslPerfDataTable.
NUM vdslPerfDataValidIntervals1.3.6.1.2.1.10.97.1.1.4.1.1HCPerfValidIntervalsread-onlyValid Intervals per definition found in HC-PerfHist-TC-MIB.
NUM vdslPerfDataInvalidIntervals1.3.6.1.2.1.10.97.1.1.4.1.2HCPerfInvalidIntervalsread-onlyInvalid Intervals per definition found in HC-PerfHist-TC-MIB.
U32 vdslPerfDataLofs1.3.6.1.2.1.10.97.1.1.4.1.3Unsigned32read-onlyCount of seconds since the unit was last reset that there was Loss of Framing.
U32 vdslPerfDataLoss1.3.6.1.2.1.10.97.1.1.4.1.4Unsigned32read-onlyCount of seconds since the unit was last reset that there was Loss of Signal.
U32 vdslPerfDataLprs1.3.6.1.2.1.10.97.1.1.4.1.5Unsigned32read-onlyCount of seconds since the unit was last reset that there was Loss of Power.
U32 vdslPerfDataLols1.3.6.1.2.1.10.97.1.1.4.1.6Unsigned32read-onlyCount of seconds since the unit was last reset that there was Loss of Link.
U32 vdslPerfDataESs1.3.6.1.2.1.10.97.1.1.4.1.7Unsigned32read-onlyCount 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.
U32 vdslPerfDataSESs1.3.6.1.2.1.10.97.1.1.4.1.8Unsigned32read-onlyCount of Severely Errored Seconds since the unit was last reset.
U32 vdslPerfDataUASs1.3.6.1.2.1.10.97.1.1.4.1.9Unsigned32read-onlyCount of Unavailable Seconds since the unit was last reset.
U32 vdslPerfDataInits1.3.6.1.2.1.10.97.1.1.4.1.10Unsigned32read-onlyCount of the line initialization attempts since the unit was last reset. This count includes both successful and failed attempts.
HCP vdslPerfDataCurr15MinTimeElapsed1.3.6.1.2.1.10.97.1.1.4.1.11HCPerfTimeElapsedread-onlyTotal elapsed seconds in this interval.
HCP vdslPerfDataCurr15MinLofs1.3.6.1.2.1.10.97.1.1.4.1.12HCPerfCurrentCountread-onlyCount of seconds during this interval that there was Loss of Framing.
HCP vdslPerfDataCurr15MinLoss1.3.6.1.2.1.10.97.1.1.4.1.13HCPerfCurrentCountread-onlyCount of seconds during this interval that there was Loss of Signal.
HCP vdslPerfDataCurr15MinLprs1.3.6.1.2.1.10.97.1.1.4.1.14HCPerfCurrentCountread-onlyCount of seconds during this interval that there was Loss of Power.
HCP vdslPerfDataCurr15MinLols1.3.6.1.2.1.10.97.1.1.4.1.15HCPerfCurrentCountread-onlyCount of seconds during this interval that there was Loss of Link.
HCP vdslPerfDataCurr15MinESs1.3.6.1.2.1.10.97.1.1.4.1.16HCPerfCurrentCountread-onlyCount 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.
HCP vdslPerfDataCurr15MinSESs1.3.6.1.2.1.10.97.1.1.4.1.17HCPerfCurrentCountread-onlyCount of Severely Errored Seconds during this interval.
HCP vdslPerfDataCurr15MinUASs1.3.6.1.2.1.10.97.1.1.4.1.18HCPerfCurrentCountread-onlyCount of Unavailable Seconds during this interval.
HCP vdslPerfDataCurr15MinInits1.3.6.1.2.1.10.97.1.1.4.1.19HCPerfCurrentCountread-onlyCount of the line initialization attempts during this interval. This count includes both successful and failed attempts.
NUM vdslPerfData1DayValidIntervals1.3.6.1.2.1.10.97.1.1.4.1.20HCPerfValidIntervalsread-onlyValid Intervals per definition found in HC-PerfHist-TC-MIB.
NUM vdslPerfData1DayInvalidIntervals1.3.6.1.2.1.10.97.1.1.4.1.21HCPerfInvalidIntervalsread-onlyInvalid Intervals per definition found in HC-PerfHist-TC-MIB.
HCP vdslPerfDataCurr1DayTimeElapsed1.3.6.1.2.1.10.97.1.1.4.1.22HCPerfTimeElapsedread-onlyNumber of seconds that have elapsed since the beginning of the current 1-day interval.
U32 vdslPerfDataCurr1DayLofs1.3.6.1.2.1.10.97.1.1.4.1.23Unsigned32read-onlyCount of Loss of Framing (LOF) Seconds since the beginning of the current 1-day interval.
U32 vdslPerfDataCurr1DayLoss1.3.6.1.2.1.10.97.1.1.4.1.24Unsigned32read-onlyCount of Loss of Signal (LOS) Seconds since the beginning of the current 1-day interval.
U32 vdslPerfDataCurr1DayLprs1.3.6.1.2.1.10.97.1.1.4.1.25Unsigned32read-onlyCount of Loss of Power (LPR) Seconds since the beginning of the current 1-day interval.
U32 vdslPerfDataCurr1DayLols1.3.6.1.2.1.10.97.1.1.4.1.26Unsigned32read-onlyCount of Loss of Link (LOL) Seconds since the beginning of the current 1-day interval.
U32 vdslPerfDataCurr1DayESs1.3.6.1.2.1.10.97.1.1.4.1.27Unsigned32read-onlyCount of Errored Seconds (ES) since the beginning of the current 1-day interval.
U32 vdslPerfDataCurr1DaySESs1.3.6.1.2.1.10.97.1.1.4.1.28Unsigned32read-onlyCount of Severely Errored Seconds (SES) since the beginning of the current 1-day interval.
U32 vdslPerfDataCurr1DayUASs1.3.6.1.2.1.10.97.1.1.4.1.29Unsigned32read-onlyCount of Unavailable Seconds (UAS) since the beginning of the current 1-day interval.
U32 vdslPerfDataCurr1DayInits1.3.6.1.2.1.10.97.1.1.4.1.30Unsigned32read-onlyCount of the line initialization attempts since the beginning of the current 1-day interval. This count includes both successful and failed attempts.
vdslPerfIntervalTable1.3.6.1.2.1.10.97.1.1.5not-accessibleThis table provides one row for each Vtu performance data collection interval. VDSL physical interfaces are those ifEntries where ifType is equal to vdsl(97).
vdslPerfIntervalEntry1.3.6.1.2.1.10.97.1.1.5.1not-accessibleAn entry in the vdslPerfIntervalTable.
U32 vdslPerfIntervalNumber1.3.6.1.2.1.10.97.1.1.5.1.1Unsigned32not-accessiblePerformance Data Interval number 1 is the most recent previous interval; interval 96 is 24 hours ago. Intervals 2 to 96 are optional.
NUM vdslPerfIntervalLofs1.3.6.1.2.1.10.97.1.1.5.1.2HCPerfIntervalCountread-onlyCount of seconds in the interval when there was Loss of Framing.
NUM vdslPerfIntervalLoss1.3.6.1.2.1.10.97.1.1.5.1.3HCPerfIntervalCountread-onlyCount of seconds in the interval when there was Loss of Signal.
NUM vdslPerfIntervalLprs1.3.6.1.2.1.10.97.1.1.5.1.4HCPerfIntervalCountread-onlyCount of seconds in the interval when there was Loss of Power.
NUM vdslPerfIntervalLols1.3.6.1.2.1.10.97.1.1.5.1.5HCPerfIntervalCountread-onlyCount of seconds in the interval when there was Loss of Link.
NUM vdslPerfIntervalESs1.3.6.1.2.1.10.97.1.1.5.1.6HCPerfIntervalCountread-onlyCount 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.
NUM vdslPerfIntervalSESs1.3.6.1.2.1.10.97.1.1.5.1.7HCPerfIntervalCountread-onlyCount of Severely Errored Seconds in the interval.
NUM vdslPerfIntervalUASs1.3.6.1.2.1.10.97.1.1.5.1.8HCPerfIntervalCountread-onlyCount of Unavailable Seconds in the interval.
NUM vdslPerfIntervalInits1.3.6.1.2.1.10.97.1.1.5.1.9HCPerfIntervalCountread-onlyCount of the line initialization attempts during this interval. This count includes both successful and failed attempts.
vdslPerf1DayIntervalTable1.3.6.1.2.1.10.97.1.1.6not-accessibleThis table provides one row for each VDSL performance data collection interval. This table contains live data from equipment. As such, it is NOT persistent.
vdslPerf1DayIntervalEntry1.3.6.1.2.1.10.97.1.1.6.1not-accessibleAn entry in the vdslPerf1DayIntervalTable.
U32 vdslPerf1DayIntervalNumber1.3.6.1.2.1.10.97.1.1.6.1.1Unsigned32not-accessibleHistory Data Interval number. Interval 1 is the most recent previous day; interval 30 is 30 days ago. Intervals 2 to 30 are optional.
HCP vdslPerf1DayIntervalMoniSecs1.3.6.1.2.1.10.97.1.1.6.1.2HCPerfTimeElapsedread-onlyThe 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.
U32 vdslPerf1DayIntervalLofs1.3.6.1.2.1.10.97.1.1.6.1.3Unsigned32read-onlyCount of Loss of Frame (LOF) Seconds during the 1-day interval as measured by vdslPerf1DayIntervalMoniSecs.
U32 vdslPerf1DayIntervalLoss1.3.6.1.2.1.10.97.1.1.6.1.4Unsigned32read-onlyCount of Loss of Signal (LOS) Seconds during the 1-day interval as measured by vdslPerf1DayIntervalMoniSecs.
U32 vdslPerf1DayIntervalLprs1.3.6.1.2.1.10.97.1.1.6.1.5Unsigned32read-onlyCount of Loss of Power (LPR) Seconds during the 1-day interval as measured by vdslPerf1DayIntervalMoniSecs.
U32 vdslPerf1DayIntervalLols1.3.6.1.2.1.10.97.1.1.6.1.6Unsigned32read-onlyCount of Loss of Link (LOL) Seconds during the 1-day interval as measured by vdslPerf1DayIntervalMoniSecs.
U32 vdslPerf1DayIntervalESs1.3.6.1.2.1.10.97.1.1.6.1.7Unsigned32read-onlyCount of Errored Seconds (ES) during the 1-day interval as measured by vdslPerf1DayIntervalMoniSecs.
U32 vdslPerf1DayIntervalSESs1.3.6.1.2.1.10.97.1.1.6.1.8Unsigned32read-onlyCount of Severely Errored Seconds (SES) during the 1-day interval as measured by vdslPerf1DayIntervalMoniSecs.
U32 vdslPerf1DayIntervalUASs1.3.6.1.2.1.10.97.1.1.6.1.9Unsigned32read-onlyCount of Unavailable Seconds (UAS) during the 1-day interval as measured by vdslPerf1DayIntervalMoniSecs.
U32 vdslPerf1DayIntervalInits1.3.6.1.2.1.10.97.1.1.6.1.10Unsigned32read-onlyCount of the line initialization attempts during the 1-day interval as measured by vdslPerf1DayIntervalMoniSecs. This count includes both successful and failed attempts.
vdslChanPerfDataTable1.3.6.1.2.1.10.97.1.1.7not-accessibleThis table provides one row for each Vtu channel. VDSL channel interfaces are those ifEntries where ifType is equal to interleave(124) or fast(125).
vdslChanPerfDataEntry1.3.6.1.2.1.10.97.1.1.7.1not-accessibleAn entry in the vdslChanPerfDataTable.
NUM vdslChanValidIntervals1.3.6.1.2.1.10.97.1.1.7.1.1HCPerfValidIntervalsread-onlyValid Intervals per definition found in HC-PerfHist-TC-MIB.
NUM vdslChanInvalidIntervals1.3.6.1.2.1.10.97.1.1.7.1.2HCPerfInvalidIntervalsread-onlyInvalid Intervals per definition found in HC-PerfHist-TC-MIB.
NUM vdslChanFixedOctets1.3.6.1.2.1.10.97.1.1.7.1.3ZeroBasedCounter64read-onlyCount of corrected octets since the unit was last reset.
NUM vdslChanBadBlks1.3.6.1.2.1.10.97.1.1.7.1.4ZeroBasedCounter64read-onlyCount of uncorrectable blocks since the unit was last reset.
HCP vdslChanCurr15MinTimeElapsed1.3.6.1.2.1.10.97.1.1.7.1.5HCPerfTimeElapsedread-onlyTotal elapsed seconds in this interval.
HCP vdslChanCurr15MinFixedOctets1.3.6.1.2.1.10.97.1.1.7.1.6HCPerfCurrentCountread-onlyCount of corrected octets in this interval.
HCP vdslChanCurr15MinBadBlks1.3.6.1.2.1.10.97.1.1.7.1.7HCPerfCurrentCountread-onlyCount of uncorrectable blocks in this interval.
NUM vdslChan1DayValidIntervals1.3.6.1.2.1.10.97.1.1.7.1.8HCPerfValidIntervalsread-onlyValid Intervals per definition found in HC-PerfHist-TC-MIB.
NUM vdslChan1DayInvalidIntervals1.3.6.1.2.1.10.97.1.1.7.1.9HCPerfInvalidIntervalsread-onlyInvalid Intervals per definition found in HC-PerfHist-TC-MIB.
HCP vdslChanCurr1DayTimeElapsed1.3.6.1.2.1.10.97.1.1.7.1.10HCPerfTimeElapsedread-onlyNumber of seconds that have elapsed since the beginning of the current 1-day interval.
HCP vdslChanCurr1DayFixedOctets1.3.6.1.2.1.10.97.1.1.7.1.11HCPerfCurrentCountread-onlyCount of corrected octets since the beginning of the current 1-day interval.
HCP vdslChanCurr1DayBadBlks1.3.6.1.2.1.10.97.1.1.7.1.12HCPerfCurrentCountread-onlyCount of uncorrectable blocks since the beginning of the current 1-day interval.
vdslChanIntervalTable1.3.6.1.2.1.10.97.1.1.8not-accessibleThis table provides one row for each Vtu channel data collection interval. VDSL channel interfaces are those ifEntries where ifType is equal to interleave(124) or fast(125).
vdslChanIntervalEntry1.3.6.1.2.1.10.97.1.1.8.1not-accessibleAn entry in the vdslChanIntervalTable.
U32 vdslChanIntervalNumber1.3.6.1.2.1.10.97.1.1.8.1.1Unsigned32not-accessiblePerformance Data Interval number 1 is the most recent previous interval; interval 96 is 24 hours ago. Intervals 2 to 96 are optional.
NUM vdslChanIntervalFixedOctets1.3.6.1.2.1.10.97.1.1.8.1.2HCPerfIntervalCountread-onlyCount of corrected octets in this interval.
NUM vdslChanIntervalBadBlks1.3.6.1.2.1.10.97.1.1.8.1.3HCPerfIntervalCountread-onlyCount of uncorrectable blocks in this interval.
vdslChan1DayIntervalTable1.3.6.1.2.1.10.97.1.1.9not-accessibleThis table provides one row for each VDSL performance data collection interval. This table contains live data from equipment. As such, it is NOT persistent.
vdslChan1DayIntervalEntry1.3.6.1.2.1.10.97.1.1.9.1not-accessibleAn entry in the vdslChan1DayIntervalTable.
U32 vdslChan1DayIntervalNumber1.3.6.1.2.1.10.97.1.1.9.1.1Unsigned32not-accessibleHistory Data Interval number. Interval 1 is the most recent previous day; interval 30 is 30 days ago. Intervals 2 to 30 are optional.
HCP vdslChan1DayIntervalMoniSecs1.3.6.1.2.1.10.97.1.1.9.1.2HCPerfTimeElapsedread-onlyThe 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.
HCP vdslChan1DayIntervalFixedOctets1.3.6.1.2.1.10.97.1.1.9.1.3HCPerfCurrentCountread-onlyCount of corrected octets in this interval.
HCP vdslChan1DayIntervalBadBlks1.3.6.1.2.1.10.97.1.1.9.1.4HCPerfCurrentCountread-onlyCount of uncorrectable blocks in this interval.
vdslLineConfProfileTable1.3.6.1.2.1.10.97.1.1.11not-accessibleThis table contains information on the VDSL line configuration. One entry in this table reflects a profile defined by a manager which can be used to configure the VDSL line. Entries in this table MUST be maintained in a persistent manner.
vdslLineConfProfileEntry1.3.6.1.2.1.10.97.1.1.11.1not-accessibleEach entry consists of a list of parameters that represents the configuration of a VDSL line. 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.
STR vdslLineConfProfileName1.3.6.1.2.1.10.97.1.1.11.1.1SnmpAdminStringnot-accessibleThis 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.
INT vdslLineConfDownRateMode1.3.6.1.2.1.10.97.1.1.11.1.2INTEGERread-createSpecifies 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.
INT vdslLineConfUpRateMode1.3.6.1.2.1.10.97.1.1.11.1.3INTEGERread-createSpecifies 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.
U32 vdslLineConfDownMaxPwr1.3.6.1.2.1.10.97.1.1.11.1.4Unsigned32read-createSpecifies the maximum aggregate downstream power level in the range 0 to 14.5 dBm.
U32 vdslLineConfUpMaxPwr1.3.6.1.2.1.10.97.1.1.11.1.5Unsigned32read-createSpecifies the maximum aggregate upstream power level in the range 0 to 14.5 dBm.
U32 vdslLineConfDownMaxSnrMgn1.3.6.1.2.1.10.97.1.1.11.1.6Unsigned32read-createSpecifies the maximum downstream Signal/Noise Margin in units of 0.25 dB, for a range of 0 to 31.75 dB.
U32 vdslLineConfDownMinSnrMgn1.3.6.1.2.1.10.97.1.1.11.1.7Unsigned32read-createSpecifies the minimum downstream Signal/Noise Margin in units of 0.25 dB, for a range of 0 to 31.75 dB.
U32 vdslLineConfDownTargetSnrMgn1.3.6.1.2.1.10.97.1.1.11.1.8Unsigned32read-createSpecifies 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.
U32 vdslLineConfUpMaxSnrMgn1.3.6.1.2.1.10.97.1.1.11.1.9Unsigned32read-createSpecifies the maximum upstream Signal/Noise Margin in units of 0.25 dB, for a range of 0 to 31.75 dB.
U32 vdslLineConfUpMinSnrMgn1.3.6.1.2.1.10.97.1.1.11.1.10Unsigned32read-createSpecifies the minimum upstream Signal/Noise Margin in units of 0.25 dB, for a range of 0 to 31.75 dB.
U32 vdslLineConfUpTargetSnrMgn1.3.6.1.2.1.10.97.1.1.11.1.11Unsigned32read-createSpecifies 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.
U32 vdslLineConfDownFastMaxDataRate1.3.6.1.2.1.10.97.1.1.11.1.12Unsigned32read-createSpecifies the maximum downstream fast channel data rate in steps of 1000 bits/second.
U32 vdslLineConfDownFastMinDataRate1.3.6.1.2.1.10.97.1.1.11.1.13Unsigned32read-createSpecifies the minimum downstream fast channel data rate in steps of 1000 bits/second.
U32 vdslLineConfDownSlowMaxDataRate1.3.6.1.2.1.10.97.1.1.11.1.14Unsigned32read-createSpecifies 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.
U32 vdslLineConfDownSlowMinDataRate1.3.6.1.2.1.10.97.1.1.11.1.15Unsigned32read-createSpecifies 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.
U32 vdslLineConfUpFastMaxDataRate1.3.6.1.2.1.10.97.1.1.11.1.16Unsigned32read-createSpecifies 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.
U32 vdslLineConfUpFastMinDataRate1.3.6.1.2.1.10.97.1.1.11.1.17Unsigned32read-createSpecifies 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.
U32 vdslLineConfUpSlowMaxDataRate1.3.6.1.2.1.10.97.1.1.11.1.18Unsigned32read-createSpecifies the maximum upstream slow channel data rate in steps of 1000 bits/second.
U32 vdslLineConfUpSlowMinDataRate1.3.6.1.2.1.10.97.1.1.11.1.19Unsigned32read-createSpecifies the minimum upstream slow channel data rate in steps of 1000 bits/second.
U32 vdslLineConfDownRateRatio1.3.6.1.2.1.10.97.1.1.11.1.20Unsigned32read-createFor 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.
U32 vdslLineConfUpRateRatio1.3.6.1.2.1.10.97.1.1.11.1.21Unsigned32read-createFor 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.
U32 vdslLineConfDownMaxInterDelay1.3.6.1.2.1.10.97.1.1.11.1.22Unsigned32read-createSpecifies the maximum interleave delay for the downstream slow channel.
U32 vdslLineConfUpMaxInterDelay1.3.6.1.2.1.10.97.1.1.11.1.23Unsigned32read-createSpecifies the maximum interleave delay for the upstream slow channel.
INT vdslLineConfDownPboControl1.3.6.1.2.1.10.97.1.1.11.1.24INTEGERread-createDownstream 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.
INT vdslLineConfUpPboControl1.3.6.1.2.1.10.97.1.1.11.1.25INTEGERread-createUpstream 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.
U32 vdslLineConfDownPboLevel1.3.6.1.2.1.10.97.1.1.11.1.26Unsigned32read-createSpecifies the downstream backoff level to be used when vdslLineConfDownPboControl = manual(3).
U32 vdslLineConfUpPboLevel1.3.6.1.2.1.10.97.1.1.11.1.27Unsigned32read-createSpecifies the upstream backoff level to be used when vdslLineConfUpPboControl = manual(3).
INT vdslLineConfDeploymentScenario1.3.6.1.2.1.10.97.1.1.11.1.28INTEGERread-createThe 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.
INT vdslLineConfAdslPresence1.3.6.1.2.1.10.97.1.1.11.1.29INTEGERread-createIndicates 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
INT vdslLineConfApplicableStandard1.3.6.1.2.1.10.97.1.1.11.1.30INTEGERread-createThe 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.
INT vdslLineConfBandPlan1.3.6.1.2.1.10.97.1.1.11.1.31INTEGERread-createThe 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.
U32 vdslLineConfBandPlanFx1.3.6.1.2.1.10.97.1.1.11.1.32Unsigned32read-createThe frequency limit between bands D2 and U2 when vdslLineConfBandPlan is set to bandPlanFx(3).
INT vdslLineConfBandOptUsage1.3.6.1.2.1.10.97.1.1.11.1.33INTEGERread-createDefines 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.
INT vdslLineConfUpPsdTemplate1.3.6.1.2.1.10.97.1.1.11.1.34INTEGERread-createThe 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).
INT vdslLineConfDownPsdTemplate1.3.6.1.2.1.10.97.1.1.11.1.35INTEGERread-createThe 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).
BIT vdslLineConfHamBandMask1.3.6.1.2.1.10.97.1.1.11.1.36Bitsread-createThe 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.
U32 vdslLineConfCustomNotch1Start1.3.6.1.2.1.10.97.1.1.11.1.37Unsigned32read-createSpecifies the start frequency of custom HAM (Handheld Amateur Radio) notch 1. vdslLineConfCustomNotch1Start MUST be less than or equal to vdslLineConfCustomNotch1Stop.
U32 vdslLineConfCustomNotch1Stop1.3.6.1.2.1.10.97.1.1.11.1.38Unsigned32read-createSpecifies the stop frequency of custom HAM (Handheld Amateur Radio) notch 1. vdslLineConfCustomNotch1Stop MUST be greater than or equal to vdslLineConfCustomNotch1Start.
U32 vdslLineConfCustomNotch2Start1.3.6.1.2.1.10.97.1.1.11.1.39Unsigned32read-createSpecifies the start frequency of custom HAM (Handheld Amateur Radio) notch 2. vdslLineConfCustomNotch2Start MUST be less than or equal to vdslLineConfCustomNotch2Stop.
U32 vdslLineConfCustomNotch2Stop1.3.6.1.2.1.10.97.1.1.11.1.40Unsigned32read-createSpecifies the stop frequency of custom HAM (Handheld Amateur Radio) notch 2. vdslLineConfCustomNotch2Stop MUST be greater than or equal to vdslLineConfCustomNotch2Start.
U32 vdslLineConfDownTargetSlowBurst1.3.6.1.2.1.10.97.1.1.11.1.41Unsigned32read-createSpecifies the target level of impulse noise (burst) protection for an interleaved (slow) channel.
U32 vdslLineConfUpTargetSlowBurst1.3.6.1.2.1.10.97.1.1.11.1.42Unsigned32read-createSpecifies the target level of impulse noise (burst) protection for an interleaved (slow) channel.
U32 vdslLineConfDownMaxFastFec1.3.6.1.2.1.10.97.1.1.11.1.43Unsigned32read-createThis parameter provisions the maximum level of Forward Error Correction (FEC) redundancy related overhead to be maintained for a fast channel.
U32 vdslLineConfUpMaxFastFec1.3.6.1.2.1.10.97.1.1.11.1.44Unsigned32read-createThis parameter provisions the maximum level of Forward Error Correction (FEC) redundancy related overhead to be maintained for a fast channel.
INT vdslLineConfLineType1.3.6.1.2.1.10.97.1.1.11.1.45INTEGERread-createThis 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.
ROW vdslLineConfProfRowStatus1.3.6.1.2.1.10.97.1.1.11.1.46RowStatusread-createThis 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).
vdslLineAlarmConfProfileTable1.3.6.1.2.1.10.97.1.1.20not-accessibleThis table contains information on the VDSL line alarm configuration. One entry in this table reflects a profile defined by a manager which can be used to configure the VDSL line alarm thresholds. Entries in this table MUST be maintained in a persistent manner.
vdslLineAlarmConfProfileEntry1.3.6.1.2.1.10.97.1.1.20.1not-accessibleEach entry consists of a list of parameters that represents the configuration of a VDSL line alarm profile. 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.
STR vdslLineAlarmConfProfileName1.3.6.1.2.1.10.97.1.1.20.1.1SnmpAdminStringnot-accessibleThe name for this profile as specified by an administrator.
NUM vdslLineAlarmConfThresh15MinLofs1.3.6.1.2.1.10.97.1.1.20.1.2HCPerfIntervalThresholdread-createThis 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.
NUM vdslLineAlarmConfThresh15MinLoss1.3.6.1.2.1.10.97.1.1.20.1.3HCPerfIntervalThresholdread-createThis 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.
NUM vdslLineAlarmConfThresh15MinLprs1.3.6.1.2.1.10.97.1.1.20.1.4HCPerfIntervalThresholdread-createThis 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.
NUM vdslLineAlarmConfThresh15MinLols1.3.6.1.2.1.10.97.1.1.20.1.5HCPerfIntervalThresholdread-createThis 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.
NUM vdslLineAlarmConfThresh15MinESs1.3.6.1.2.1.10.97.1.1.20.1.6HCPerfIntervalThresholdread-createThis 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.
NUM vdslLineAlarmConfThresh15MinSESs1.3.6.1.2.1.10.97.1.1.20.1.7HCPerfIntervalThresholdread-createThis 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.
NUM vdslLineAlarmConfThresh15MinUASs1.3.6.1.2.1.10.97.1.1.20.1.8HCPerfIntervalThresholdread-createThis 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.
T/F vdslLineAlarmConfInitFailure1.3.6.1.2.1.10.97.1.1.20.1.9TruthValueread-createThis object specifies if a vdslInitFailureNotification notification will be generated if an initialization failure occurs.
ROW vdslLineAlarmConfProfRowStatus1.3.6.1.2.1.10.97.1.1.20.1.10RowStatusread-createThis 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.
vdslConformance1.3.6.1.2.1.10.97.1.3
vdslGroups1.3.6.1.2.1.10.97.1.3.1
vdslGroup1.3.6.1.2.1.10.97.1.3.1.1A collection of objects providing information about a VDSL Line.
vdslNotificationGroup1.3.6.1.2.1.10.97.1.3.1.2This group supports notifications of significant conditions associated with VDSL Lines.
vdslCompliances1.3.6.1.2.1.10.97.1.3.2
vdslLineMibCompliance1.3.6.1.2.1.10.97.1.3.2.1The compliance statement for SNMP entities which manage VDSL interfaces.

FAQ

How does VDSL-LINE-MIB help isolate a degrading VDSL line between a DSLAM and a customer-premises modem?
It exposes line coding/type and configuration/alarm profile assignment per line, plus per-transceiver physical inventory such as vendor ID and serial number tracked per line-end (CO or CPE side), letting an operator confirm a line's settings still match provisioning intent or spot an unexpectedly swapped transceiver.

Does VDSL-LINE-MIB require the CO-side and CPE-side agents to communicate with each other for management?
No — it's designed to require no management communication beyond what's inherent in the VDSL line protocol itself, relying instead on each VDSL line appearing as a standard ifTable entry via IF-MIB.

RFC description

IETF standard MIB for managing VDSL (Very-high-bit-rate DSL) line parameters and performance (RFC 3728).

Start monitoring vendor-neutral, standards-based MIB, DSLAMs and VDSL modems/transceivers (line coding/profile/transceiver-inventory status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download VDSL-LINE-MIB