---
oid: "1.3.6.1.4.1.6527.3.1.2.11.2.33.1.5"
asn1-notation: "{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 6527 timetraProducts(3) tmnxSRMIB(1) tmnxSRObjs(2) tmnxOamTestObjs(11) tmnxOamTraceRouteObjs(2) tmnxOamLspTrFecStackTable(33) tmnxOamLspTrFecStackEntry(1) tmnxOamLspTrFecStackPrefix(5)}"
description: "tmnxOamLspTrFecStackPrefix OBJECT-TYPE"
classification: "MIB object for network management"
last-modified: "2021-09-21"
---

## OID : `1.3.6.1.4.1.6527.3.1.2.11.2.33.1.5`

```asn1
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 6527 timetraProducts(3) tmnxSRMIB(1) tmnxSRObjs(2) tmnxOamTestObjs(11) tmnxOamTraceRouteObjs(2) tmnxOamLspTrFecStackTable(33) tmnxOamLspTrFecStackEntry(1) tmnxOamLspTrFecStackPrefix(5)}
```

### Description

```asn1
tmnxOamLspTrFecStackPrefix OBJECT-TYPE
SYNTAX InetAddress (SIZE (0\|4\|16))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of tmnxOamLspTrFecStackPrefix indicates the value of an IP
prefix (or IP address) field with the following encapsulation
(where +-\> indicates encapsulation):
'lspTraceRoute' reply PDU
+-\> RFC 6424 Downstream Detailed Mapping TLV
+-\> RFC 6424 FEC Stack Change sub-TLV
+-\> RFC 4379 Target FEC Stack TLV
+-\> RFC 4379 FEC-type-specific sub-TLV
(e.g. LDP IPv4 Prefix sub-TLV)
+-\> FEC-type-specific IP prefix field.
For example, the value returned could be the content of one of the
fields shown in the following table.
Field RFC 4379 Sub-TLV
\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-- \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\--
Extended Tunnel ID RSVP IPv4 LSP
IPv4 Prefix BGP Labeled IPv4 Prefix
IPv4 Prefix LDP IPv4 Prefix
If no IP prefix field is present in the reply PDU,
tmnxOamLspTrFecStackPrefixType contains 'unknown(1)'."
```

**Classification**: MIB object for network management

### Child OIDs

No child OID

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