FRAME-RELAY-DTE-MIB

All MIBs › FRAME-RELAY-DTE-MIB

Organization: IETF IPLPDN Working Group

Last Updated: 1997-05-01

Category: Frame Relay, MPLS and Traffic Engineering, Network Interfaces

Description:

Covers managed objects for Frame Relay Data Terminal Equipment (DTE) interfaces, including DLCI status and error statistics.

Imported Objects

From IF-MIB

InterfaceIndex

From RFC1213-MIB

transmission

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Integer32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE

From SNMPv2-TC

RowStatus
TEXTUAL-CONVENTION
TimeStamp

What Is FRAME-RELAY-DTE-MIB?

FRAME-RELAY-DTE-MIB is a vendor-neutral IETF standards MIB defining managed objects for a device acting as Frame Relay Data Terminal Equipment, covering the DTE's view of its Frame Relay interfaces and permanent virtual circuits (DLCIs). It exposes data on DLCI (data link connection identifier) operational status, configured committed information rate parameters, and per-circuit error/discard statistics for frames crossing the Frame Relay interface. In terms of monitoring device status, it is used mainly for software/protocol-layer health — tracking whether individual DLCIs are up, down, or in a deleted state, and counting frame errors that indicate congestion or link-layer faults — rather than physical hardware sensors. It builds directly on and extends the standard IF-MIB, since Frame Relay DTE interfaces are represented as ifTable entries with this MIB adding DLCI-level detail beneath them. It is deployed on routers and other DTE equipment connected to a Frame Relay network, common in legacy WAN environments, and the FRAME-RELAY-DTE-MIB OID list centers on per-DLCI status and error counters layered beneath the standard ifTable entries.

IPNetwork Monitor allows you to monitor SNMP objects defined in FRAME-RELAY-DTE-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

What Can Be Monitored

DLCI operational status
committed/excess burst size configuration
frame discard counts
frame error counts
Frame Relay circuit up/down state

Supported Devices

vendor-neutral, standards-based MIB, not tied to a specific manufacturer
routers and DTE equipment on Frame Relay WAN links

Monitoring Examples

An administrator would poll a DLCI status table (indexed by interface and DLCI number) to see whether a given permanent virtual circuit is active, inactive, or has been deleted by the network, and cross-reference committed and excess burst size settings against observed throughput. Rising discard or error counters on a specific DLCI would indicate the circuit is exceeding its committed information rate or experiencing carrier-side congestion. No sample_objects were provided for this module, so these table/column names are inferred from the standard Frame Relay DTE MIB structure rather than confirmed here.

OIDs

OID symbolic	OID numeric	Type	Access	Description
frameRelayDTE	1.3.6.1.2.1.10.32			The MIB module to describe the use of a Frame Relay interface by a DTE.
frameRelayTrapControl	1.3.6.1.2.1.10.32.4
frameRelayTraps	1.3.6.1.2.1.10.32.0
I32 frCircuitCommittedBurst	1.3.6.1.2.1.10.32.2.1.12	Integer32	read-create	This variable indicates the maximum amount of data, in bits, that the network agrees to transfer under normal conditions, during the measurement interval.
TIM frCircuitCreationTime	1.3.6.1.2.1.10.32.2.1.10	TimeStamp	read-only	The value of sysUpTime when the virtual circuit was created, whether by the Data Link Connection Management Interface or by a SetRequest.
C32 frCircuitDiscards	1.3.6.1.2.1.10.32.2.1.17	Counter32	read-only	The number of inbound frames dropped because of format errors, or because the VC is inactive.
DLC frCircuitDlci	1.3.6.1.2.1.10.32.2.1.2	DLCI	read-only	The Data Link Connection Identifier for this virtual circuit.
frCircuitEntry	1.3.6.1.2.1.10.32.2.1		not-accessible	The information regarding a single Data Link Connection. Discontinuities in the counters contained in this table are indicated by the value in frCircuitCreationTime.
I32 frCircuitExcessBurst	1.3.6.1.2.1.10.32.2.1.13	Integer32	read-create	This variable indicates the maximum amount of uncommitted data bits that the network will attempt to deliver over the measurement interval. By default, if not configured when creating the entry, the Excess Information Burst Size is set to the value of ifSpeed.
frCircuitGroup	1.3.6.1.2.1.10.32.6.1.2			The objects necessary to control the Virtual Circuits layered onto a Frame Relay Interface.
frCircuitGroup0	1.3.6.1.2.1.10.32.6.1.7			The objects necessary to control the Virtual Circuits layered onto a Frame Relay Interface from RFC 1315.
NUM frCircuitIfIndex	1.3.6.1.2.1.10.32.2.1.1	InterfaceIndex	read-only	The ifIndex Value of the ifEntry this virtual circuit is layered onto.
TIM frCircuitLastTimeChange	1.3.6.1.2.1.10.32.2.1.11	TimeStamp	read-only	The value of sysUpTime when last there was a change in the virtual circuit state
NUM frCircuitLogicalIfIndex	1.3.6.1.2.1.10.32.2.1.20	InterfaceIndex	read-create	Normally the same value as frDlcmiIfIndex, but different when an implementation associates a virtual ifEntry with a DLC or set of DLCs in order to associate higher layer objects such as the ipAddrEntry with a subset of the virtual circuits on a Frame Relay interface. The type of such ifEntries is defined by the higher layer object; for example, if PPP/Frame Relay is implemented, the ifType of this ifEntry would be PPP. If it is not so defined, as would be the case with an ipAddrEntry, it should be of type Other.
INT frCircuitMulticast	1.3.6.1.2.1.10.32.2.1.15	INTEGER	read-create	This indicates whether this VC is used as a unicast VC (i.e. not multicast) or the type of multicast service subscribed to
C32 frCircuitReceivedBECNs	1.3.6.1.2.1.10.32.2.1.5	Counter32	read-only	Number of frames received from the network indicating backward congestion since the virtual circuit was created. This occurs when the remote DTE sets the BECN flag, or when a switch in the network receives the frame from a trunk whose transmission queue is congested.
C32 frCircuitReceivedDEs	1.3.6.1.2.1.10.32.2.1.18	Counter32	read-only	Number of frames received from the network indicating that they were eligible for discard since the virtual circuit was created. This occurs when the remote DTE sets the DE flag, or when in remote DTE's switch detects that the frame was received as Excess Burst data.
C32 frCircuitReceivedFECNs	1.3.6.1.2.1.10.32.2.1.4	Counter32	read-only	Number of frames received from the network indicating forward congestion since the virtual circuit was created. This occurs when the remote DTE sets the FECN flag, or when a switch in the network enqueues the frame to a trunk whose transmission queue is congested.
C32 frCircuitReceivedFrames	1.3.6.1.2.1.10.32.2.1.8	Counter32	read-only	Number of frames received over this virtual circuit since it was created.
C32 frCircuitReceivedOctets	1.3.6.1.2.1.10.32.2.1.9	Counter32	read-only	Number of octets received over this virtual circuit since it was created. Octets counted include the full frame relay header, but do not include the flag characters or the CRC.
ROW frCircuitRowStatus	1.3.6.1.2.1.10.32.2.1.21	RowStatus	read-create	This object is used to create a new row or modify or destroy an existing row in the manner described in the definition of the RowStatus textual convention. Writable objects in the table may be written in any RowStatus state.
C32 frCircuitSentDEs	1.3.6.1.2.1.10.32.2.1.19	Counter32	read-only	Number of frames sent to the network indicating that they were eligible for discard since the virtual circuit was created. This occurs when the local DTE sets the DE flag, indicating that during Network congestion situations those frames should be discarded in preference of other frames sent without the DE bit set.
C32 frCircuitSentFrames	1.3.6.1.2.1.10.32.2.1.6	Counter32	read-only	The number of frames sent from this virtual circuit since it was created.
C32 frCircuitSentOctets	1.3.6.1.2.1.10.32.2.1.7	Counter32	read-only	The number of octets sent from this virtual circuit since it was created. Octets counted are the full frame relay header and the payload, but do not include the flag characters or CRC.
INT frCircuitState	1.3.6.1.2.1.10.32.2.1.3	INTEGER	read-create	Indicates whether the particular virtual circuit is operational. In the absence of a Data Link Connection Management Interface, virtual circuit entries (rows) may be created by setting virtual circuit state to 'active', or deleted by changing Circuit state to 'invalid'. Whether or not the row actually disappears is left to the implementation, so this object may actually read as 'invalid' for some arbitrary length of time. It is also legal to set the state of a virtual circuit to 'inactive' to temporarily disable a given circuit. The use of 'invalid' is deprecated in this SNMP Version 2 MIB, in favor of frCircuitRowStatus.
frCircuitTable	1.3.6.1.2.1.10.32.2		not-accessible	A table containing information about specific Data Link Connections (DLC) or virtual circuits.
I32 frCircuitThroughput	1.3.6.1.2.1.10.32.2.1.14	Integer32	read-create	Throughput is the average number of 'Frame Relay Information Field' bits transferred per second across a user network interface in one direction, measured over the measurement interval. If the configured committed burst rate and throughput are both non-zero, the measurement interval, T, is T=frCircuitCommittedBurst/frCircuitThroughput. If the configured committed burst rate and throughput are both zero, the measurement interval, T, is T=frCircuitExcessBurst/ifSpeed.
INT frCircuitType	1.3.6.1.2.1.10.32.2.1.16	INTEGER	read-only	Indication of whether the VC was manually created (static), or dynamically created (dynamic) via the data link control management interface.
frCompliance	1.3.6.1.2.1.10.32.6.2.1			The compliance statement
frCompliance0	1.3.6.1.2.1.10.32.6.2.2			The compliance statement for objects and the trap defined in RFC 1315.
frCompliances	1.3.6.1.2.1.10.32.6.2
frConformance	1.3.6.1.2.1.10.32.6
NTF frDLCIStatusChange	1.3.6.1.2.1.10.32.0.1			This trap indicates that the indicated Virtual Circuit has changed state. It has either been created or invalidated, or has toggled between the active and inactive states. If, however, the reason for the state change is due to the DLCMI going down, per-DLCI traps should not be generated.
INT frDlcmiAddress	1.3.6.1.2.1.10.32.1.1.3	INTEGER	read-create	This variable states which address format is in use on the Frame Relay interface.
INT frDlcmiAddressLen	1.3.6.1.2.1.10.32.1.1.4	INTEGER	read-create	This variable states the address length in octets. In the case of Q922 format, the length indicates the entire length of the address including the control portion.
frDlcmiEntry	1.3.6.1.2.1.10.32.1.1		not-accessible	The Parameters for a particular Data Link Connection Management Interface.
I32 frDlcmiErrorThreshold	1.3.6.1.2.1.10.32.1.1.7	Integer32	read-create	This is the maximum number of unanswered Status Enquiries the equipment shall accept before declaring the interface down.
I32 frDlcmiFullEnquiryInterval	1.3.6.1.2.1.10.32.1.1.6	Integer32	read-create	Number of status enquiry intervals that pass before issuance of a full status enquiry message.
NUM frDlcmiIfIndex	1.3.6.1.2.1.10.32.1.1.1	InterfaceIndex	read-only	The ifIndex value of the corresponding ifEntry.
DLC frDlcmiMaxSupportedVCs	1.3.6.1.2.1.10.32.1.1.9	DLCI	read-create	The maximum number of Virtual Circuits allowed for this interface. Usually dictated by the Frame Relay network. In response to a SET, if a value less than zero or higher than the agent's maximal capability is configured, the agent should respond badValue
I32 frDlcmiMonitoredEvents	1.3.6.1.2.1.10.32.1.1.8	Integer32	read-create	This is the number of status polling intervals over which the error threshold is counted. For example, if within 'MonitoredEvents' number of events the station receives 'ErrorThreshold' number of errors, the interface is marked as down.
INT frDlcmiMulticast	1.3.6.1.2.1.10.32.1.1.10	INTEGER	read-create	This indicates whether the Frame Relay interface is using a multicast service.
I32 frDlcmiPollingInterval	1.3.6.1.2.1.10.32.1.1.5	Integer32	read-create	This is the number of seconds between successive status enquiry messages.
ROW frDlcmiRowStatus	1.3.6.1.2.1.10.32.1.1.12	RowStatus	read-create	SNMP Version 2 Row Status Variable. Writable objects in the table may be written in any RowStatus state.
INT frDlcmiState	1.3.6.1.2.1.10.32.1.1.2	INTEGER	read-create	This variable states which Data Link Connection Management scheme is active (and by implication, what DLCI it uses) on the Frame Relay interface.
INT frDlcmiStatus	1.3.6.1.2.1.10.32.1.1.11	INTEGER	read-only	This indicates the status of the Frame Relay interface as determined by the performance of the dlcmi. If no dlcmi is running, the Frame Relay interface will stay in the running state indefinitely.
frDlcmiTable	1.3.6.1.2.1.10.32.1		not-accessible	The Parameters for the Data Link Connection Management Interface for the frame relay service on this interface.
OCT frErrData	1.3.6.1.2.1.10.32.3.1.3	OCTET STRING	read-only	An octet string containing as much of the error packet as possible. As a minimum, it must contain the Q.922 Address or as much as was delivered. It is desirable to include all header and demultiplexing information.
frErrEntry	1.3.6.1.2.1.10.32.3.1		not-accessible	The error information for a single frame relay interface.
C32 frErrFaults	1.3.6.1.2.1.10.32.3.1.5	Counter32	read-only	The number of times the interface has gone down since it was initialized.
TIM frErrFaultTime	1.3.6.1.2.1.10.32.3.1.6	TimeStamp	read-only	The value of sysUpTime at the time when the interface was taken down due to excessive errors. Excessive errors is defined as the time when a DLCMI exceeds the frDlcmiErrorThreshold number of errors within frDlcmiMonitoredEvents. See FrDlcmiEntry for further details.
frErrGroup	1.3.6.1.2.1.10.32.6.1.4			Objects designed to assist in debugging Frame Relay Interfaces.
frErrGroup0	1.3.6.1.2.1.10.32.6.1.8			Objects designed to assist in debugging Frame Relay Interfaces from RFC 1315.
NUM frErrIfIndex	1.3.6.1.2.1.10.32.3.1.1	InterfaceIndex	read-only	The ifIndex Value of the corresponding ifEntry.
frErrTable	1.3.6.1.2.1.10.32.3		not-accessible	A table containing information about Errors on the Frame Relay interface. Discontinuities in the counters contained in this table are the same as apply to the ifEntry associated with the Interface.
TIM frErrTime	1.3.6.1.2.1.10.32.3.1.4	TimeStamp	read-only	The value of sysUpTime at which the error was detected.
INT frErrType	1.3.6.1.2.1.10.32.3.1.2	INTEGER	read-only	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.
frGroups	1.3.6.1.2.1.10.32.6.1
frNotificationGroup	1.3.6.1.2.1.10.32.6.1.5			Traps which may be used to enhance event driven management of the interface.
frPortGroup	1.3.6.1.2.1.10.32.6.1.1			The objects necessary to control the Link Management Interface for a Frame Relay Interface as well as maintain the error statistics on this interface.
frPortGroup0	1.3.6.1.2.1.10.32.6.1.6			The objects necessary to control the Link Management Interface for a Frame Relay Interface as well as maintain the error statistics on this interface from RFC 1315.
frTrapGroup	1.3.6.1.2.1.10.32.6.1.3			The objects necessary to control a Frame Relay Interface's notification messages.
frTrapGroup0	1.3.6.1.2.1.10.32.6.1.9			The objects necessary to control a Frame Relay Interface's notification messages from RFC 1315.
I32 frTrapMaxRate	1.3.6.1.2.1.10.32.4.2	Integer32	read-write	This variable indicates the number of milliseconds that must elapse between trap emissions. If events occur more rapidly, the impementation may simply fail to trap, or may queue traps until an appropriate time.
INT frTrapState	1.3.6.1.2.1.10.32.4.1	INTEGER	read-write	This variable indicates whether the system produces the frDLCIStatusChange trap.

OID symbolic	OID numeric	Type	Access	Description
frameRelayDTE	1.3.6.1.2.1.10.32			The MIB module to describe the use of a Frame Relay interface by a DTE.
frameRelayTraps	1.3.6.1.2.1.10.32.0
NTF frDLCIStatusChange	1.3.6.1.2.1.10.32.0.1			This trap indicates that the indicated Virtual Circuit has changed state. It has either been created or invalidated, or has toggled between the active and inactive states. If, however, the reason for the state change is due to the DLCMI going down, per-DLCI traps should not be generated.
frDlcmiTable	1.3.6.1.2.1.10.32.1		not-accessible	The Parameters for the Data Link Connection Management Interface for the frame relay service on this interface.
frDlcmiEntry	1.3.6.1.2.1.10.32.1.1		not-accessible	The Parameters for a particular Data Link Connection Management Interface.
NUM frDlcmiIfIndex	1.3.6.1.2.1.10.32.1.1.1	InterfaceIndex	read-only	The ifIndex value of the corresponding ifEntry.
INT frDlcmiState	1.3.6.1.2.1.10.32.1.1.2	INTEGER	read-create	This variable states which Data Link Connection Management scheme is active (and by implication, what DLCI it uses) on the Frame Relay interface.
INT frDlcmiAddress	1.3.6.1.2.1.10.32.1.1.3	INTEGER	read-create	This variable states which address format is in use on the Frame Relay interface.
INT frDlcmiAddressLen	1.3.6.1.2.1.10.32.1.1.4	INTEGER	read-create	This variable states the address length in octets. In the case of Q922 format, the length indicates the entire length of the address including the control portion.
I32 frDlcmiPollingInterval	1.3.6.1.2.1.10.32.1.1.5	Integer32	read-create	This is the number of seconds between successive status enquiry messages.
I32 frDlcmiFullEnquiryInterval	1.3.6.1.2.1.10.32.1.1.6	Integer32	read-create	Number of status enquiry intervals that pass before issuance of a full status enquiry message.
I32 frDlcmiErrorThreshold	1.3.6.1.2.1.10.32.1.1.7	Integer32	read-create	This is the maximum number of unanswered Status Enquiries the equipment shall accept before declaring the interface down.
I32 frDlcmiMonitoredEvents	1.3.6.1.2.1.10.32.1.1.8	Integer32	read-create	This is the number of status polling intervals over which the error threshold is counted. For example, if within 'MonitoredEvents' number of events the station receives 'ErrorThreshold' number of errors, the interface is marked as down.
DLC frDlcmiMaxSupportedVCs	1.3.6.1.2.1.10.32.1.1.9	DLCI	read-create	The maximum number of Virtual Circuits allowed for this interface. Usually dictated by the Frame Relay network. In response to a SET, if a value less than zero or higher than the agent's maximal capability is configured, the agent should respond badValue
INT frDlcmiMulticast	1.3.6.1.2.1.10.32.1.1.10	INTEGER	read-create	This indicates whether the Frame Relay interface is using a multicast service.
INT frDlcmiStatus	1.3.6.1.2.1.10.32.1.1.11	INTEGER	read-only	This indicates the status of the Frame Relay interface as determined by the performance of the dlcmi. If no dlcmi is running, the Frame Relay interface will stay in the running state indefinitely.
ROW frDlcmiRowStatus	1.3.6.1.2.1.10.32.1.1.12	RowStatus	read-create	SNMP Version 2 Row Status Variable. Writable objects in the table may be written in any RowStatus state.
frCircuitTable	1.3.6.1.2.1.10.32.2		not-accessible	A table containing information about specific Data Link Connections (DLC) or virtual circuits.
frCircuitEntry	1.3.6.1.2.1.10.32.2.1		not-accessible	The information regarding a single Data Link Connection. Discontinuities in the counters contained in this table are indicated by the value in frCircuitCreationTime.
NUM frCircuitIfIndex	1.3.6.1.2.1.10.32.2.1.1	InterfaceIndex	read-only	The ifIndex Value of the ifEntry this virtual circuit is layered onto.
DLC frCircuitDlci	1.3.6.1.2.1.10.32.2.1.2	DLCI	read-only	The Data Link Connection Identifier for this virtual circuit.
INT frCircuitState	1.3.6.1.2.1.10.32.2.1.3	INTEGER	read-create	Indicates whether the particular virtual circuit is operational. In the absence of a Data Link Connection Management Interface, virtual circuit entries (rows) may be created by setting virtual circuit state to 'active', or deleted by changing Circuit state to 'invalid'. Whether or not the row actually disappears is left to the implementation, so this object may actually read as 'invalid' for some arbitrary length of time. It is also legal to set the state of a virtual circuit to 'inactive' to temporarily disable a given circuit. The use of 'invalid' is deprecated in this SNMP Version 2 MIB, in favor of frCircuitRowStatus.
C32 frCircuitReceivedFECNs	1.3.6.1.2.1.10.32.2.1.4	Counter32	read-only	Number of frames received from the network indicating forward congestion since the virtual circuit was created. This occurs when the remote DTE sets the FECN flag, or when a switch in the network enqueues the frame to a trunk whose transmission queue is congested.
C32 frCircuitReceivedBECNs	1.3.6.1.2.1.10.32.2.1.5	Counter32	read-only	Number of frames received from the network indicating backward congestion since the virtual circuit was created. This occurs when the remote DTE sets the BECN flag, or when a switch in the network receives the frame from a trunk whose transmission queue is congested.
C32 frCircuitSentFrames	1.3.6.1.2.1.10.32.2.1.6	Counter32	read-only	The number of frames sent from this virtual circuit since it was created.
C32 frCircuitSentOctets	1.3.6.1.2.1.10.32.2.1.7	Counter32	read-only	The number of octets sent from this virtual circuit since it was created. Octets counted are the full frame relay header and the payload, but do not include the flag characters or CRC.
C32 frCircuitReceivedFrames	1.3.6.1.2.1.10.32.2.1.8	Counter32	read-only	Number of frames received over this virtual circuit since it was created.
C32 frCircuitReceivedOctets	1.3.6.1.2.1.10.32.2.1.9	Counter32	read-only	Number of octets received over this virtual circuit since it was created. Octets counted include the full frame relay header, but do not include the flag characters or the CRC.
TIM frCircuitCreationTime	1.3.6.1.2.1.10.32.2.1.10	TimeStamp	read-only	The value of sysUpTime when the virtual circuit was created, whether by the Data Link Connection Management Interface or by a SetRequest.
TIM frCircuitLastTimeChange	1.3.6.1.2.1.10.32.2.1.11	TimeStamp	read-only	The value of sysUpTime when last there was a change in the virtual circuit state
I32 frCircuitCommittedBurst	1.3.6.1.2.1.10.32.2.1.12	Integer32	read-create	This variable indicates the maximum amount of data, in bits, that the network agrees to transfer under normal conditions, during the measurement interval.
I32 frCircuitExcessBurst	1.3.6.1.2.1.10.32.2.1.13	Integer32	read-create	This variable indicates the maximum amount of uncommitted data bits that the network will attempt to deliver over the measurement interval. By default, if not configured when creating the entry, the Excess Information Burst Size is set to the value of ifSpeed.
I32 frCircuitThroughput	1.3.6.1.2.1.10.32.2.1.14	Integer32	read-create	Throughput is the average number of 'Frame Relay Information Field' bits transferred per second across a user network interface in one direction, measured over the measurement interval. If the configured committed burst rate and throughput are both non-zero, the measurement interval, T, is T=frCircuitCommittedBurst/frCircuitThroughput. If the configured committed burst rate and throughput are both zero, the measurement interval, T, is T=frCircuitExcessBurst/ifSpeed.
INT frCircuitMulticast	1.3.6.1.2.1.10.32.2.1.15	INTEGER	read-create	This indicates whether this VC is used as a unicast VC (i.e. not multicast) or the type of multicast service subscribed to
INT frCircuitType	1.3.6.1.2.1.10.32.2.1.16	INTEGER	read-only	Indication of whether the VC was manually created (static), or dynamically created (dynamic) via the data link control management interface.
C32 frCircuitDiscards	1.3.6.1.2.1.10.32.2.1.17	Counter32	read-only	The number of inbound frames dropped because of format errors, or because the VC is inactive.
C32 frCircuitReceivedDEs	1.3.6.1.2.1.10.32.2.1.18	Counter32	read-only	Number of frames received from the network indicating that they were eligible for discard since the virtual circuit was created. This occurs when the remote DTE sets the DE flag, or when in remote DTE's switch detects that the frame was received as Excess Burst data.
C32 frCircuitSentDEs	1.3.6.1.2.1.10.32.2.1.19	Counter32	read-only	Number of frames sent to the network indicating that they were eligible for discard since the virtual circuit was created. This occurs when the local DTE sets the DE flag, indicating that during Network congestion situations those frames should be discarded in preference of other frames sent without the DE bit set.
NUM frCircuitLogicalIfIndex	1.3.6.1.2.1.10.32.2.1.20	InterfaceIndex	read-create	Normally the same value as frDlcmiIfIndex, but different when an implementation associates a virtual ifEntry with a DLC or set of DLCs in order to associate higher layer objects such as the ipAddrEntry with a subset of the virtual circuits on a Frame Relay interface. The type of such ifEntries is defined by the higher layer object; for example, if PPP/Frame Relay is implemented, the ifType of this ifEntry would be PPP. If it is not so defined, as would be the case with an ipAddrEntry, it should be of type Other.
ROW frCircuitRowStatus	1.3.6.1.2.1.10.32.2.1.21	RowStatus	read-create	This object is used to create a new row or modify or destroy an existing row in the manner described in the definition of the RowStatus textual convention. Writable objects in the table may be written in any RowStatus state.
frErrTable	1.3.6.1.2.1.10.32.3		not-accessible	A table containing information about Errors on the Frame Relay interface. Discontinuities in the counters contained in this table are the same as apply to the ifEntry associated with the Interface.
frErrEntry	1.3.6.1.2.1.10.32.3.1		not-accessible	The error information for a single frame relay interface.
NUM frErrIfIndex	1.3.6.1.2.1.10.32.3.1.1	InterfaceIndex	read-only	The ifIndex Value of the corresponding ifEntry.
INT frErrType	1.3.6.1.2.1.10.32.3.1.2	INTEGER	read-only	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.
OCT frErrData	1.3.6.1.2.1.10.32.3.1.3	OCTET STRING	read-only	An octet string containing as much of the error packet as possible. As a minimum, it must contain the Q.922 Address or as much as was delivered. It is desirable to include all header and demultiplexing information.
TIM frErrTime	1.3.6.1.2.1.10.32.3.1.4	TimeStamp	read-only	The value of sysUpTime at which the error was detected.
C32 frErrFaults	1.3.6.1.2.1.10.32.3.1.5	Counter32	read-only	The number of times the interface has gone down since it was initialized.
TIM frErrFaultTime	1.3.6.1.2.1.10.32.3.1.6	TimeStamp	read-only	The value of sysUpTime at the time when the interface was taken down due to excessive errors. Excessive errors is defined as the time when a DLCMI exceeds the frDlcmiErrorThreshold number of errors within frDlcmiMonitoredEvents. See FrDlcmiEntry for further details.
frameRelayTrapControl	1.3.6.1.2.1.10.32.4
INT frTrapState	1.3.6.1.2.1.10.32.4.1	INTEGER	read-write	This variable indicates whether the system produces the frDLCIStatusChange trap.
I32 frTrapMaxRate	1.3.6.1.2.1.10.32.4.2	Integer32	read-write	This variable indicates the number of milliseconds that must elapse between trap emissions. If events occur more rapidly, the impementation may simply fail to trap, or may queue traps until an appropriate time.
frConformance	1.3.6.1.2.1.10.32.6
frGroups	1.3.6.1.2.1.10.32.6.1
frPortGroup	1.3.6.1.2.1.10.32.6.1.1			The objects necessary to control the Link Management Interface for a Frame Relay Interface as well as maintain the error statistics on this interface.
frCircuitGroup	1.3.6.1.2.1.10.32.6.1.2			The objects necessary to control the Virtual Circuits layered onto a Frame Relay Interface.
frTrapGroup	1.3.6.1.2.1.10.32.6.1.3			The objects necessary to control a Frame Relay Interface's notification messages.
frErrGroup	1.3.6.1.2.1.10.32.6.1.4			Objects designed to assist in debugging Frame Relay Interfaces.
frNotificationGroup	1.3.6.1.2.1.10.32.6.1.5			Traps which may be used to enhance event driven management of the interface.
frPortGroup0	1.3.6.1.2.1.10.32.6.1.6			The objects necessary to control the Link Management Interface for a Frame Relay Interface as well as maintain the error statistics on this interface from RFC 1315.
frCircuitGroup0	1.3.6.1.2.1.10.32.6.1.7			The objects necessary to control the Virtual Circuits layered onto a Frame Relay Interface from RFC 1315.
frErrGroup0	1.3.6.1.2.1.10.32.6.1.8			Objects designed to assist in debugging Frame Relay Interfaces from RFC 1315.
frTrapGroup0	1.3.6.1.2.1.10.32.6.1.9			The objects necessary to control a Frame Relay Interface's notification messages from RFC 1315.
frCompliances	1.3.6.1.2.1.10.32.6.2
frCompliance	1.3.6.1.2.1.10.32.6.2.1			The compliance statement
frCompliance0	1.3.6.1.2.1.10.32.6.2.2			The compliance statement for objects and the trap defined in RFC 1315.

Counter32 (10)
C32 frCircuitDiscards	1.3.6.1.2.1.10.32.2.1.17	Counter32	read-only	The number of inbound frames dropped because of format errors, or because the VC is inactive.
C32 frCircuitReceivedBECNs	1.3.6.1.2.1.10.32.2.1.5	Counter32	read-only	Number of frames received from the network indicating backward congestion since the virtual circuit was created. This occurs when the remote DTE sets the BECN flag, or when a switch in the network receives the frame from a trunk whose transmission queue is congested.
C32 frCircuitReceivedDEs	1.3.6.1.2.1.10.32.2.1.18	Counter32	read-only	Number of frames received from the network indicating that they were eligible for discard since the virtual circuit was created. This occurs when the remote DTE sets the DE flag, or when in remote DTE's switch detects that the frame was received as Excess Burst data.
C32 frCircuitReceivedFECNs	1.3.6.1.2.1.10.32.2.1.4	Counter32	read-only	Number of frames received from the network indicating forward congestion since the virtual circuit was created. This occurs when the remote DTE sets the FECN flag, or when a switch in the network enqueues the frame to a trunk whose transmission queue is congested.
C32 frCircuitReceivedFrames	1.3.6.1.2.1.10.32.2.1.8	Counter32	read-only	Number of frames received over this virtual circuit since it was created.
C32 frCircuitReceivedOctets	1.3.6.1.2.1.10.32.2.1.9	Counter32	read-only	Number of octets received over this virtual circuit since it was created. Octets counted include the full frame relay header, but do not include the flag characters or the CRC.
C32 frCircuitSentDEs	1.3.6.1.2.1.10.32.2.1.19	Counter32	read-only	Number of frames sent to the network indicating that they were eligible for discard since the virtual circuit was created. This occurs when the local DTE sets the DE flag, indicating that during Network congestion situations those frames should be discarded in preference of other frames sent without the DE bit set.
C32 frCircuitSentFrames	1.3.6.1.2.1.10.32.2.1.6	Counter32	read-only	The number of frames sent from this virtual circuit since it was created.
C32 frCircuitSentOctets	1.3.6.1.2.1.10.32.2.1.7	Counter32	read-only	The number of octets sent from this virtual circuit since it was created. Octets counted are the full frame relay header and the payload, but do not include the flag characters or CRC.
C32 frErrFaults	1.3.6.1.2.1.10.32.3.1.5	Counter32	read-only	The number of times the interface has gone down since it was initialized.
DLCI (2)
DLC frCircuitDlci	1.3.6.1.2.1.10.32.2.1.2	DLCI	read-only	The Data Link Connection Identifier for this virtual circuit.
DLC frDlcmiMaxSupportedVCs	1.3.6.1.2.1.10.32.1.1.9	DLCI	read-create	The maximum number of Virtual Circuits allowed for this interface. Usually dictated by the Frame Relay network. In response to a SET, if a value less than zero or higher than the agent's maximal capability is configured, the agent should respond badValue
INTEGER (10)
INT frCircuitMulticast	1.3.6.1.2.1.10.32.2.1.15	INTEGER	read-create	This indicates whether this VC is used as a unicast VC (i.e. not multicast) or the type of multicast service subscribed to
INT frCircuitState	1.3.6.1.2.1.10.32.2.1.3	INTEGER	read-create	Indicates whether the particular virtual circuit is operational. In the absence of a Data Link Connection Management Interface, virtual circuit entries (rows) may be created by setting virtual circuit state to 'active', or deleted by changing Circuit state to 'invalid'. Whether or not the row actually disappears is left to the implementation, so this object may actually read as 'invalid' for some arbitrary length of time. It is also legal to set the state of a virtual circuit to 'inactive' to temporarily disable a given circuit. The use of 'invalid' is deprecated in this SNMP Version 2 MIB, in favor of frCircuitRowStatus.
INT frCircuitType	1.3.6.1.2.1.10.32.2.1.16	INTEGER	read-only	Indication of whether the VC was manually created (static), or dynamically created (dynamic) via the data link control management interface.
INT frDlcmiAddress	1.3.6.1.2.1.10.32.1.1.3	INTEGER	read-create	This variable states which address format is in use on the Frame Relay interface.
INT frDlcmiAddressLen	1.3.6.1.2.1.10.32.1.1.4	INTEGER	read-create	This variable states the address length in octets. In the case of Q922 format, the length indicates the entire length of the address including the control portion.
INT frDlcmiMulticast	1.3.6.1.2.1.10.32.1.1.10	INTEGER	read-create	This indicates whether the Frame Relay interface is using a multicast service.
INT frDlcmiState	1.3.6.1.2.1.10.32.1.1.2	INTEGER	read-create	This variable states which Data Link Connection Management scheme is active (and by implication, what DLCI it uses) on the Frame Relay interface.
INT frDlcmiStatus	1.3.6.1.2.1.10.32.1.1.11	INTEGER	read-only	This indicates the status of the Frame Relay interface as determined by the performance of the dlcmi. If no dlcmi is running, the Frame Relay interface will stay in the running state indefinitely.
INT frErrType	1.3.6.1.2.1.10.32.3.1.2	INTEGER	read-only	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.
INT frTrapState	1.3.6.1.2.1.10.32.4.1	INTEGER	read-write	This variable indicates whether the system produces the frDLCIStatusChange trap.
Integer32 (8)
I32 frCircuitCommittedBurst	1.3.6.1.2.1.10.32.2.1.12	Integer32	read-create	This variable indicates the maximum amount of data, in bits, that the network agrees to transfer under normal conditions, during the measurement interval.
I32 frCircuitExcessBurst	1.3.6.1.2.1.10.32.2.1.13	Integer32	read-create	This variable indicates the maximum amount of uncommitted data bits that the network will attempt to deliver over the measurement interval. By default, if not configured when creating the entry, the Excess Information Burst Size is set to the value of ifSpeed.
I32 frCircuitThroughput	1.3.6.1.2.1.10.32.2.1.14	Integer32	read-create	Throughput is the average number of 'Frame Relay Information Field' bits transferred per second across a user network interface in one direction, measured over the measurement interval. If the configured committed burst rate and throughput are both non-zero, the measurement interval, T, is T=frCircuitCommittedBurst/frCircuitThroughput. If the configured committed burst rate and throughput are both zero, the measurement interval, T, is T=frCircuitExcessBurst/ifSpeed.
I32 frDlcmiErrorThreshold	1.3.6.1.2.1.10.32.1.1.7	Integer32	read-create	This is the maximum number of unanswered Status Enquiries the equipment shall accept before declaring the interface down.
I32 frDlcmiFullEnquiryInterval	1.3.6.1.2.1.10.32.1.1.6	Integer32	read-create	Number of status enquiry intervals that pass before issuance of a full status enquiry message.
I32 frDlcmiMonitoredEvents	1.3.6.1.2.1.10.32.1.1.8	Integer32	read-create	This is the number of status polling intervals over which the error threshold is counted. For example, if within 'MonitoredEvents' number of events the station receives 'ErrorThreshold' number of errors, the interface is marked as down.
I32 frDlcmiPollingInterval	1.3.6.1.2.1.10.32.1.1.5	Integer32	read-create	This is the number of seconds between successive status enquiry messages.
I32 frTrapMaxRate	1.3.6.1.2.1.10.32.4.2	Integer32	read-write	This variable indicates the number of milliseconds that must elapse between trap emissions. If events occur more rapidly, the impementation may simply fail to trap, or may queue traps until an appropriate time.
InterfaceIndex (4)
NUM frCircuitIfIndex	1.3.6.1.2.1.10.32.2.1.1	InterfaceIndex	read-only	The ifIndex Value of the ifEntry this virtual circuit is layered onto.
NUM frCircuitLogicalIfIndex	1.3.6.1.2.1.10.32.2.1.20	InterfaceIndex	read-create	Normally the same value as frDlcmiIfIndex, but different when an implementation associates a virtual ifEntry with a DLC or set of DLCs in order to associate higher layer objects such as the ipAddrEntry with a subset of the virtual circuits on a Frame Relay interface. The type of such ifEntries is defined by the higher layer object; for example, if PPP/Frame Relay is implemented, the ifType of this ifEntry would be PPP. If it is not so defined, as would be the case with an ipAddrEntry, it should be of type Other.
NUM frDlcmiIfIndex	1.3.6.1.2.1.10.32.1.1.1	InterfaceIndex	read-only	The ifIndex value of the corresponding ifEntry.
NUM frErrIfIndex	1.3.6.1.2.1.10.32.3.1.1	InterfaceIndex	read-only	The ifIndex Value of the corresponding ifEntry.
OCTET STRING (1)
OCT frErrData	1.3.6.1.2.1.10.32.3.1.3	OCTET STRING	read-only	An octet string containing as much of the error packet as possible. As a minimum, it must contain the Q.922 Address or as much as was delivered. It is desirable to include all header and demultiplexing information.
RowStatus (2)
ROW frCircuitRowStatus	1.3.6.1.2.1.10.32.2.1.21	RowStatus	read-create	This object is used to create a new row or modify or destroy an existing row in the manner described in the definition of the RowStatus textual convention. Writable objects in the table may be written in any RowStatus state.
ROW frDlcmiRowStatus	1.3.6.1.2.1.10.32.1.1.12	RowStatus	read-create	SNMP Version 2 Row Status Variable. Writable objects in the table may be written in any RowStatus state.
TimeStamp (4)
TIM frCircuitCreationTime	1.3.6.1.2.1.10.32.2.1.10	TimeStamp	read-only	The value of sysUpTime when the virtual circuit was created, whether by the Data Link Connection Management Interface or by a SetRequest.
TIM frCircuitLastTimeChange	1.3.6.1.2.1.10.32.2.1.11	TimeStamp	read-only	The value of sysUpTime when last there was a change in the virtual circuit state
TIM frErrFaultTime	1.3.6.1.2.1.10.32.3.1.6	TimeStamp	read-only	The value of sysUpTime at the time when the interface was taken down due to excessive errors. Excessive errors is defined as the time when a DLCMI exceeds the frDlcmiErrorThreshold number of errors within frDlcmiMonitoredEvents. See FrDlcmiEntry for further details.
TIM frErrTime	1.3.6.1.2.1.10.32.3.1.4	TimeStamp	read-only	The value of sysUpTime at which the error was detected.
No type (24)
frameRelayDTE	1.3.6.1.2.1.10.32			The MIB module to describe the use of a Frame Relay interface by a DTE.
frameRelayTrapControl	1.3.6.1.2.1.10.32.4
frameRelayTraps	1.3.6.1.2.1.10.32.0
frCircuitEntry	1.3.6.1.2.1.10.32.2.1		not-accessible	The information regarding a single Data Link Connection. Discontinuities in the counters contained in this table are indicated by the value in frCircuitCreationTime.
frCircuitGroup	1.3.6.1.2.1.10.32.6.1.2			The objects necessary to control the Virtual Circuits layered onto a Frame Relay Interface.
frCircuitGroup0	1.3.6.1.2.1.10.32.6.1.7			The objects necessary to control the Virtual Circuits layered onto a Frame Relay Interface from RFC 1315.
frCircuitTable	1.3.6.1.2.1.10.32.2		not-accessible	A table containing information about specific Data Link Connections (DLC) or virtual circuits.
frCompliance	1.3.6.1.2.1.10.32.6.2.1			The compliance statement
frCompliance0	1.3.6.1.2.1.10.32.6.2.2			The compliance statement for objects and the trap defined in RFC 1315.
frCompliances	1.3.6.1.2.1.10.32.6.2
frConformance	1.3.6.1.2.1.10.32.6
NTF frDLCIStatusChange	1.3.6.1.2.1.10.32.0.1			This trap indicates that the indicated Virtual Circuit has changed state. It has either been created or invalidated, or has toggled between the active and inactive states. If, however, the reason for the state change is due to the DLCMI going down, per-DLCI traps should not be generated.
frDlcmiEntry	1.3.6.1.2.1.10.32.1.1		not-accessible	The Parameters for a particular Data Link Connection Management Interface.
frDlcmiTable	1.3.6.1.2.1.10.32.1		not-accessible	The Parameters for the Data Link Connection Management Interface for the frame relay service on this interface.
frErrEntry	1.3.6.1.2.1.10.32.3.1		not-accessible	The error information for a single frame relay interface.
frErrGroup	1.3.6.1.2.1.10.32.6.1.4			Objects designed to assist in debugging Frame Relay Interfaces.
frErrGroup0	1.3.6.1.2.1.10.32.6.1.8			Objects designed to assist in debugging Frame Relay Interfaces from RFC 1315.
frErrTable	1.3.6.1.2.1.10.32.3		not-accessible	A table containing information about Errors on the Frame Relay interface. Discontinuities in the counters contained in this table are the same as apply to the ifEntry associated with the Interface.
frGroups	1.3.6.1.2.1.10.32.6.1
frNotificationGroup	1.3.6.1.2.1.10.32.6.1.5			Traps which may be used to enhance event driven management of the interface.
frPortGroup	1.3.6.1.2.1.10.32.6.1.1			The objects necessary to control the Link Management Interface for a Frame Relay Interface as well as maintain the error statistics on this interface.
frPortGroup0	1.3.6.1.2.1.10.32.6.1.6			The objects necessary to control the Link Management Interface for a Frame Relay Interface as well as maintain the error statistics on this interface from RFC 1315.
frTrapGroup	1.3.6.1.2.1.10.32.6.1.3			The objects necessary to control a Frame Relay Interface's notification messages.
frTrapGroup0	1.3.6.1.2.1.10.32.6.1.9			The objects necessary to control a Frame Relay Interface's notification messages from RFC 1315.

RFC description

Defines managed objects for managing Frame Relay Data Terminal Equipment (DTE) interfaces, including DLCI status and error statistics.

Start monitoring Vendor-neutral Frame Relay DTE router/access device, any manufacturer with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download FRAME-RELAY-DTE-MIB

This MIB depends on

Related MIBs

What Is FRAME-RELAY-DTE-MIB?

What Can Be Monitored

Supported Devices

Monitoring Examples

RFC description