FRX-MIB

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › FRX-MIB

Description: FRX-MIB module

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) 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.

What Is FRX-MIB?

FRX-MIB is a legacy vendor MIB (associated with Netrix/FastComm-style FRX frame relay switch/multiplexer nodes) that manages and monitors a frame relay switching node, covering hardware identity, software version, and node-level operational state alongside protocol-specific groups for network protocols such as SPX/IPX and LAT-style extensions (net, spx, lwx). It exposes clear hardware/software status objects: nodeSoftwareRelease and nodeSoftwareReleaseDate report the running firmware version, nodeBootVersion and nodeCardType identify the boot code and installed card type, and nodeUpTime tracks how long the node has been running since last restart. Operationally it also reports nodeCongestionLevel and nodeBuffersUsed, giving direct visibility into frame relay network congestion and buffer exhaustion, both classic causes of frame relay service degradation. It predates modern standard frame-relay MIBs and is largely self-contained, though nodeIPAddress ties it into standard IP addressing conventions. It was deployed on legacy frame relay switch/access nodes in carrier or enterprise WAN frame relay networks. Engineers can download the FRX-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in FRX-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

  • legacy frame relay switch/access node (Netrix/FastComm-style FRX platform)

Monitoring Examples

An administrator would poll nodeUpTime and nodeSoftwareRelease/nodeSoftwareReleaseDate to confirm a node hasn't unexpectedly rebooted and is running the expected firmware version. nodeCongestionLevel and nodeBuffersUsed would be watched together - a high congestion level paired with high buffer usage on a node indicates the frame relay switch is nearing capacity and may start dropping or marking frames as discard-eligible. nodeCardType and nodeBootVersion would be checked after a hardware swap to confirm the replacement card and boot image match expectations.

What Can Be Monitored

  • node uptime
  • software release version and date
  • boot version
  • card type
  • network congestion level
  • buffer utilization
Imported Objects

From RFC-1212

OBJECT-TYPE

From RFC-1215

TRAP-TYPE

From RFC1155-SMI

Counter
Gauge
IpAddress
enterprises

From RFC1213-MIB

DisplayString
OIDs

RFC description

Manages Frame Relay Exchange (FRX) devices from NET with port, circuit and T1/E1 backcard monitoring.

Start monitoring Legacy frame relay switch/access node (Netrix/FastComm-style FRX platform) 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 FRX-MIB