VDSL-LINE-MIB :: vdslPhysCurrStatus

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsVDSL-LINE-MIBvdslPhysCurrStatus

vdslPhysCurrStatus

Module: VDSL-LINE-MIB

OID (symbolic): VDSL-LINE-MIB::vdslPhysCurrStatus

OID (numeric): 1.3.6.1.2.1.10.97.1.1.2.1.7

Node type: OBJECT-TYPE

Type: Bits

Access: read-only

Description: 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.

What is vdslPhysCurrStatus?

Encodes the VTU's current defect state as a bitmap, with individual bits flagging conditions such as loss of framing, loss of signal, loss of power, poor signal quality, loss of link, or failures during data/config/protocol initialization or peer detection. An admin polls this alongside ifOperStatus to pinpoint why a VDSL line is down or degraded, for example distinguishing a dead peer (noPeerVtuPresent) from a configuration mismatch (configInitFailure).

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.10.97.1.1.2.1.7
snmpwalk -v2c -c public <target> VDSL-LINE-MIB::vdslPhysCurrStatus

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.10.97.1.1.2.1.7.1
snmpget -v2c -c public <target> VDSL-LINE-MIB::vdslPhysCurrStatus.1

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. Create custom SNMP monitor using the VDSL-LINE-MIB::vdslPhysCurrStatus OID value, configure state conditions and alerts, and monitor any vendor-neutral, standards-based MIB, DSLAMs and VDSL modems/transceivers (line coding/profile/transceiver-inventory status) from a single console.

OID Breakdown

Upper-level ancestors (7 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.2mgmtAXON-MIB
1.3.6.1.2.1mib_2AXON-MIB
1.3.6.1.2.1.10transmissionCHECKPOINT-MIB-2
Numeric OIDNameModule
1.3.6.1.2.1.10.97vdslMIBVDSL-LINE-MIB
1.3.6.1.2.1.10.97.1vdslLineMibVDSL-LINE-MIB
1.3.6.1.2.1.10.97.1.1vdslMibObjectsVDSL-LINE-MIB
1.3.6.1.2.1.10.97.1.1.2vdslPhysTableVDSL-LINE-MIB
1.3.6.1.2.1.10.97.1.1.2.1vdslPhysEntryVDSL-LINE-MIB
1.3.6.1.2.1.10.97.1.1.2.1.7vdslPhysCurrStatusVDSL-LINE-MIB