---
oid: "1.3.6.1.2.1.10.97.1.1.11.1.31"
short-description: "vdslLineConfBandPlan OBJECT-TYPE"
last-modified: "2020-02-18"
parent-oid: "1.3.6.1.2.1.10.97.1.1.11.1"
---

## OID: `1.3.6.1.2.1.10.97.1.1.11.1.31`

```asn1
{iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) transmission(10) vdslMIB(97) vdslLineMib(1) vdslMibObjects(1) vdslLineConfProfileTable(11) vdslLineConfProfileEntry(1) vdslLineConfBandPlan(31)}
```

### Description

```asn1
vdslLineConfBandPlan OBJECT-TYPE
SYNTAX INTEGER
{
bandPlan997(1),
bandPlan998(2),
bandPlanFx(3),
other(4)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"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."
DEFVAL { bandPlan997 }
```

**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.
