---
oid: "1.3.6.1.2.1.10.166.22.1.3.1.8"
asn1-notation: "{iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) transmission(10) mplsStdMIB(166) mplsLpsMIB(22) mplsLpsObjects(1) mplsLpsStatusTable(3) mplsLpsStatusEntry(1) mplsLpsStatusCapabilitiesMismatch(8)}"
description: "mplsLpsStatusCapabilitiesMismatch OBJECT-TYPE"
classification: "MIB object for network management"
last-modified: "2017-04-21"
---

## OID : `1.3.6.1.2.1.10.166.22.1.3.1.8`

```asn1
{iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) transmission(10) mplsStdMIB(166) mplsLpsMIB(22) mplsLpsObjects(1) mplsLpsStatusTable(3) mplsLpsStatusEntry(1) mplsLpsStatusCapabilitiesMismatch(8)}
```

### Description

```asn1
mplsLpsStatusCapabilitiesMismatch OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates a provisioning mismatch in
Capabilities TLVs across the protection domain endpoints.
The value of this object becomes true when a PSC message with
an incompatible Capabilities TLV field is received or false
when a PSC message with a compatible Capabilities TLV field is
received.
The Capabilities TLV with 0xF8000000 indicates that the APS
mode is used for the MPLS-TP linear protection mechanism,
whereas the PSC mode either (1) uses the Capabilities TLV
with a value of 0x0 or (2) does not use the Capabilities TLV
because the TLV does not exist."
REFERENCE
"Section 12 of RFC 7271"
```

**Classification**: MIB object for network management

### Supplementary information

Automatically extracted from IETF [RFC 8150](http://tools.ietf.org/html/rfc8150).

### Child OIDs

No child OID

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