The type of error that was last seen on this interface. The error types are
as follows:
receiveShort: This error indicates a received frame was discarded
because it was less than four octets long or it was missing the
Organizationally Unique Identifier (OUI) for a SNAP header.
receiveLong: This error indicates a received frame was discarded
because it was longer than expected. This error is currently not used on
this interface.
illegalDlci: This error indicates that a received frame was discarded
because it's Q.922 address was not two octets in length. This error could
also indicate that a frame was discarded because it was received on a
DLCI reserved for LMI which had not been provisioned active.
dlcmiProtoErr: This error indicates an LMI frame was received with
contents formatted incorrectly.
dlcmiUnknownIe: This error indicates that an LMI frame was received
which contained an unsupported Information Element (IE) type
dlcmiSequenceErr: This error indicates that an LMI frame was received
whose Keep Alive Sequence was incorrect.
dlcmiUnknownRpt: This error indicates that an LMI frame was received
which contained a Report-type Information Element with an invalid type
of report.
noErrorSinceReset: This error type indicates that there has not been an
error since the interface has been reset.
unknownError: This error type contains the cumulation of receive
frame errors that did not fit one of the MIB error descriptions above.
These errors include those counted by the following attributes:
ulpUnknownProtocol - A received frame was discarded because the
Upper Level Protocol (ULP) encapsulation used was unsupported.
badFc - A received frame was discarded because the frame control
character was incorrect.
defragSequenceErrors - A fragment was received which was discarded
due to an out of sequence error detection.
Parsed from file nortelPC-frameRelayDteV1.mib.txt
Company: None
Module: Nortel-MsCarrier-MscPassport-FrameRelayDteMIB
The type of error that was last seen on this interface. The error types are
as follows:
receiveShort: This error indicates a received frame was discarded
because it was less than four octets long or it was missing the
Organizationally Unique Identifier (OUI) for a SNAP header.
receiveLong: This error indicates a received frame was discarded
because it was longer than expected. This error is currently not used on
this interface.
illegalDlci: This error indicates that a received frame was discarded
because it's Q.922 address was not two octets in length. This error could
also indicate that a frame was discarded because it was received on a
DLCI reserved for LMI which had not been provisioned active.
dlcmiProtoErr: This error indicates an LMI frame was received with
contents formatted incorrectly.
dlcmiUnknownIe: This error indicates that an LMI frame was received
which contained an unsupported Information Element (IE) type
dlcmiSequenceErr: This error indicates that an LMI frame was received
whose Keep Alive Sequence was incorrect.
dlcmiUnknownRpt: This error indicates that an LMI frame was received
which contained a Report-type Information Element with an invalid type
of report.
noErrorSinceReset: This error type indicates that there has not been an
error since the interface has been reset.
unknownError: This error type contains the cumulation of receive
frame errors that did not fit one of the MIB error descriptions above.
These errors include those counted by the following attributes:
ulpUnknownProtocol - A received frame was discarded because the
Upper Level Protocol (ULP) encapsulation used was unsupported.
badFc - A received frame was discarded because the frame control
character was incorrect.
defragSequenceErrors - A fragment was received which was discarded
due to an out of sequence error detection.
Parsed from file Nortel-MsCarrier-MscPassport-FrameRelayDteMIB.mib
Module: Nortel-MsCarrier-MscPassport-FrameRelayDteMIB
Vendor: Northern Telecom, Ltd.
Module: Nortel-MsCarrier-MscPassport-FrameRelayDteMIB
[Automatically extracted from oidview.com]
mscFrDteErrType OBJECT-TYPE SYNTAX INTEGER { unknownError(1), receiveShort(2), receiveLong(3), illegalDlci(4), dlcmiProtoErr(5), dlcmiUnknownIe(6), dlcmiSequenceErr(7), dlcmiUnknownRpt(8), noErrorSinceReset(9) } ACCESS read-only STATUS mandatory DESCRIPTION "The type of error that was last seen on this interface. The error types are as follows: receiveShort: This error indicates a received frame was discarded because it was less than four octets long or it was missing the Organizationally Unique Identifier (OUI) for a SNAP header. receiveLong: This error indicates a received frame was discarded because it was longer than expected. This error is currently not used on this interface. illegalDlci: This error indicates that a received frame was discarded because it's Q.922 address was not two octets in length. This error could also indicate that a frame was discarded because it was received on a DLCI reserved for LMI which had not been provisioned active. dlcmiProtoErr: This error indicates an LMI frame was received with contents formatted incorrectly. dlcmiUnknownIe: This error indicates that an LMI frame was received which contained an unsupported Information Element (IE) type dlcmiSequenceErr: This error indicates that an LMI frame was received whose Keep Alive Sequence was incorrect. dlcmiUnknownRpt: This error indicates that an LMI frame was received which contained a Report-type Information Element with an invalid type of report. noErrorSinceReset: This error type indicates that there has not been an error since the interface has been reset. unknownError: This error type contains the cumulation of receive frame errors that did not fit one of the MIB error descriptions above. These errors include those counted by the following attributes: ulpUnknownProtocol - A received frame was discarded because the Upper Level Protocol (ULP) encapsulation used was unsupported. badFc - A received frame was discarded because the frame control character was incorrect. defragSequenceErrors - A fragment was received which was discarded due to an out of sequence error detection." DEFVAL { noErrorSinceReset } ::= { mscFrDteErrEntry 2 }
mscFrDteErrType OBJECT-TYPE SYNTAX INTEGER { unknownError(1), receiveShort(2), receiveLong(3), illegalDlci(4), dlcmiProtoErr(5), dlcmiUnknownIe(6), dlcmiSequenceErr(7), dlcmiUnknownRpt(8), noErrorSinceReset(9) } ACCESS read-only STATUS mandatory DESCRIPTION "The type of error that was last seen on this interface. The error types are as follows: receiveShort: This error indicates a received frame was discarded because it was less than four octets long or it was missing the Organizationally Unique Identifier (OUI) for a SNAP header. receiveLong: This error indicates a received frame was discarded because it was longer than expected. This error is currently not used on this interface. illegalDlci: This error indicates that a received frame was discarded because it's Q.922 address was not two octets in length. This error could also indicate that a frame was discarded because it was received on a DLCI reserved for LMI which had not been provisioned active. dlcmiProtoErr: This error indicates an LMI frame was received with contents formatted incorrectly. dlcmiUnknownIe: This error indicates that an LMI frame was received which contained an unsupported Information Element (IE) type dlcmiSequenceErr: This error indicates that an LMI frame was received whose Keep Alive Sequence was incorrect. dlcmiUnknownRpt: This error indicates that an LMI frame was received which contained a Report-type Information Element with an invalid type of report. noErrorSinceReset: This error type indicates that there has not been an error since the interface has been reset. unknownError: This error type contains the cumulation of receive frame errors that did not fit one of the MIB error descriptions above. These errors include those counted by the following attributes: ulpUnknownProtocol - A received frame was discarded because the Upper Level Protocol (ULP) encapsulation used was unsupported. badFc - A received frame was discarded because the frame control character was incorrect. defragSequenceErrors - A fragment was received which was discarded due to an out of sequence error detection." DEFVAL { noErrorSinceReset } ::= { mscFrDteErrEntry 2 }
OID | Name | Sub children | Sub Nodes Total | Description |
---|---|---|---|---|
1.3.6.1.4.1.562.36.2.1.101.26.1.3 | mscFrDteErrData | 0 | 0 | An octet string containing the first part of the frame in which an error was last detected. |
1.3.6.1.4.1.562.36.2.1.101.26.1.4 | mscFrDteErrTime | 0 | 0 | The time at which the last error was detected and recorded in errType. |
1.3.6.1.4.1.562.36.2.1.101.26.1.6 | mscFrDteErrDiscards | 0 | 0 | Number of inbound frames dropped because of format errors or because the virtual circuit was not known. Format errors, in this c… |
1.3.6.1.4.1.562.36.2.1.101.26.1.7 | mscFrDteErrFaults | 0 | 0 | This attribute counts the number of times LMI has taken down the interface. When the procedure attribute of the Lmi component is… |
1.3.6.1.4.1.562.36.2.1.101.26.1.8 | mscFrDteErrFaultTime | 0 | 0 | The last time the errFaults counter was incremented. |