---
oid: "1.3.6.1.2.1.10.32.3.1.2"
short-description: "frErrType OBJECT-TYPE"
last-modified: "2021-01-12"
parent-oid: "1.3.6.1.2.1.10.32.3.1"
---

## OID: `1.3.6.1.2.1.10.32.3.1.2`

```asn1
{iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) transmission(10) frameRelayDTE(32) frErrTable(3) frErrEntry(1) frErrType(2)}
```

### Description

```asn1
frErrType OBJECT-TYPE
SYNTAX INTEGER {unknownError(1), receiveShort(2), receiveLong(3), illegalAddress(4), unknownAddress(5), dlcmiProtoErr(6), dlcmiUnknownIE(7), dlcmiSequenceErr(8), dlcmiUnknownRpt(9), noErrorSinceReset(10)}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The type of error that was last seen on this interface:
receiveShort: frame was not long enough to allow demultiplexing - the address field was incomplete, or for virtual circuits using Multiprotocol over Frame Relay, the protocol identifier was missing or incomplete.
receiveLong: frame exceeded maximum length configured for this interface.
illegalAddress: address field did not match configured format.
unknownAddress: frame received on a virtual circuit which was not active or administratively disabled.
dlcmiProtoErr: unspecified error occurred when attempting to interpret link maintenance frame.
dlcmiUnknownIE: link maintenance frame contained an Information Element type which is not valid for the configured link maintenance protocol.
dlcmiSequenceErr: link maintenance frame contained a sequence number other than the expected value.
dlcmiUnknownRpt: link maintenance frame contained a Report Type Information Element whose value was not valid for the configured link maintenance protocol.
noErrorSinceReset: no errors have been detected since the last cold start or warm start."
```

**Classification:** MIB object for network management

### Supplementary information

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