---
oid: "1.3.6.1.2.1.10.200.1.1.1.9"
short-description: "teLinkIncomingIfId OBJECT-TYPE"
last-modified: "2020-04-16"
parent-oid: "1.3.6.1.2.1.10.200.1.1.1"
---

## OID: `1.3.6.1.2.1.10.200.1.1.1.9`

```asn1
{iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) transmission(10) teLinkStdMIB(200) teLinkObjects(1) teLinkTable(1) teLinkEntry(1) teLinkIncomingIfId(9)}
```

### Description

```asn1
teLinkIncomingIfId OBJECT-TYPE
SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"For unnumbered links, the incoming interface is set to the
outgoing interface identifier chosen by the neighboring LSR
for the reverse link corresponding to this TE link. If the
link is numbered, the value of this object is 0 and the
address is stored in the teLinkRemoteIpAddr instead."
REFERENCE
"Link Bundling in MPLS Traffic Engineering (TE), RFC 4201"
```

**Classification:** MIB object for network management

### Supplementary information

Automatically extracted from IETF [RFC 4220](https://www.rfc-editor.org/rfc/rfc4220.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.