FRAME-RELAY-DTE-MIB

MIB Reference — IPNetwork Monitor · Updated September 09, 2026

All MIBsFRAME-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.

IPNetwork Monitor uses several OIDs from this MIB in network discovery and polling the applicable devices. Start monitoring FRAME-RELAY-DTE-MIB with a free 30-day trial of IPNetwork Monitor.

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.

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.

What Can Be Monitored

  • DLCI operational status
  • committed/excess burst size configuration
  • frame discard counts
  • frame error counts
  • Frame Relay circuit up/down state
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
OIDs

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