---
oid: "1.3.6.1.2.1.10.166.5.1.1.2.1"
asn1-notation: "{iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) transmission(10) mplsStdMIB(166) mplsLdpAtmStdMIB(5) mplsLdpAtmObjects(1) mplsLdpEntityAtmObjects(1) mplsLdpEntityAtmLRTable(2) mplsLdpEntityAtmLREntry(1)}"
description: "mplsLdpEntityAtmLREntry OBJECT-TYPE"
classification: "MIB object for network management"
last-modified: "2020-02-07"
---

## OID : `1.3.6.1.2.1.10.166.5.1.1.2.1`

```asn1
{iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) transmission(10) mplsStdMIB(166) mplsLdpAtmStdMIB(5) mplsLdpAtmObjects(1) mplsLdpEntityAtmObjects(1) mplsLdpEntityAtmLRTable(2) mplsLdpEntityAtmLREntry(1)}
```

### Description

```asn1
mplsLdpEntityAtmLREntry OBJECT-TYPE
SYNTAX MplsLdpEntityAtmLREntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A row in the LDP Entity ATM Label
Range Table. One entry in this table contains
information on a single range of labels
represented by the configured Upper and Lower
Bounds VPI/VCI pairs. These are the same
data used in the Initialization Message.
NOTE: The ranges for a specific LDP Entity
are UNIQUE and non-overlapping. For example,
for a specific LDP Entity index, there could
be one entry having LowerBound vpi/vci == 0/32, and
UpperBound vpi/vci == 0/100, and a second entry
for this same interface with LowerBound
vpi/vci == 0/101 and UpperBound vpi/vci == 0/200.
However, there could not be a third entry with
LowerBound vpi/vci == 0/200 and
UpperBound vpi/vci == 0/300 because this label
range overlaps with the second entry (i.e., both
entries now have 0/200).
A row will not become active unless a unique and
non-overlapping range is specified.
At least one label range entry for a
specific LDP Entity MUST
include the default VPI/VCI values denoted
in the LDP Entity Table.
A request to create a row with an overlapping
range should result in an inconsistentValue
error."
INDEX { mplsLdpEntityLdpId,
mplsLdpEntityIndex,
mplsLdpEntityAtmLRMinVpi,
mplsLdpEntityAtmLRMinVci
}
```

**Classification**: MIB object for network management

### Supplementary information

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

### Child OIDs

- [OID `1.3.6.1.2.1.10.166.5.1.1.2.1.1`](https://oid-base.com/get-md/1.3.6.1.2.1.10.166.5.1.1.2.1.1): `mplsLdpEntityAtmLRMinVpi(1)`
- [OID `1.3.6.1.2.1.10.166.5.1.1.2.1.2`](https://oid-base.com/get-md/1.3.6.1.2.1.10.166.5.1.1.2.1.2): `mplsLdpEntityAtmLRMinVci(2)`
- [OID `1.3.6.1.2.1.10.166.5.1.1.2.1.3`](https://oid-base.com/get-md/1.3.6.1.2.1.10.166.5.1.1.2.1.3): `mplsLdpEntityAtmLRMaxVpi(3)`
- [OID `1.3.6.1.2.1.10.166.5.1.1.2.1.4`](https://oid-base.com/get-md/1.3.6.1.2.1.10.166.5.1.1.2.1.4): `mplsLdpEntityAtmLRMaxVci(4)`
- [OID `1.3.6.1.2.1.10.166.5.1.1.2.1.5`](https://oid-base.com/get-md/1.3.6.1.2.1.10.166.5.1.1.2.1.5): `mplsLdpEntityAtmLRStorageType(5)`
- [OID `1.3.6.1.2.1.10.166.5.1.1.2.1.6`](https://oid-base.com/get-md/1.3.6.1.2.1.10.166.5.1.1.2.1.6): `mplsLdpEntityAtmLRRowStatus(6)`

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