---
oid: "1.3.6.1.2.1.10.97.1.1.2.1.7"
short-description: "vdslPhysCurrStatus OBJECT-TYPE"
last-modified: "2020-02-18"
parent-oid: "1.3.6.1.2.1.10.97.1.1.2.1"
---

## OID: `1.3.6.1.2.1.10.97.1.1.2.1.7`

```asn1
{iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) transmission(10) vdslMIB(97) vdslLineMib(1) vdslMibObjects(1) vdslPhysTable(2) vdslPhysEntry(1) vdslPhysCurrStatus(7)}
```

### Description

```asn1
vdslPhysCurrStatus OBJECT-TYPE
SYNTAX BITS
{
noDefect(0),
lossOfFraming(1),
lossOfSignal(2),
lossOfPower(3),
lossOfSignalQuality(4),
lossOfLink(5),
dataInitFailure(6),
configInitFailure(7),
protocolInitFailure(8),
noPeerVtuPresent(9)
}
MAX-ACCESS read-only
STATUS current
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."
REFERENCE "T1E1.4/2000-009R3, Part 1, common spec"
```

**Classification:** MIB object for network management

### Supplementary information

Automatically extracted from IETF [RFC 3728](https://www.rfc-editor.org/rfc/rfc3728.html).

### Child OIDs

No child OID

### Terms of Use

[Terms of use](https://oid-base.com/disclaimer.htm.md)

**Note to implementers:**: The OID repository is constantly updated but does not necessarily store the latest (or most accurate) version of this formal description. For an implementation, it is recommended to search the web for a more recent description. If this is the case, please update the above description.
