USR-FCNI-MIB

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › USR-FCNI-MIB

Organization: CommWorks Corporation, a 3Com Company

Last Updated: 2002-08-23

Category: CommWorks/3Com Access Equipment

Description: Manages Frame Relay/ATM convergence network interface parameters on CommWorks/3Com equipment.

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 USR-FCNI-MIB?

USR-FCNI-MIB is a vendor-specific enterprise module from CommWorks (formerly US Robotics, later 3Com) that manages Frame Relay/ATM convergence network interface parameters, specifically for wireless FACN (Frame Relay/ATM Convergence Network) interfaces on CommWorks carrier equipment. It exposes configuration objects controlling how frame relay and ATM traffic are converged and mapped for wireless backhaul or carrier interconnect purposes. Its role in hardware/software status monitoring centers on confirming interface configuration is correctly applied, letting an administrator verify convergence parameters match the network design and detect a misconfigured interface that could disrupt frame relay/ATM interworking for wireless traffic. It likely builds conceptually on standard Frame Relay and ATM interworking concepts (e.g., FRF.5/FRF.8) though implemented as a CommWorks-proprietary MIB. It is typically deployed on CommWorks/3Com carrier equipment supporting wireless network backhaul over converged Frame Relay/ATM infrastructure. Network engineers evaluating or troubleshooting this functionality can download the USR-FCNI-MIB file directly to load it into their MIB browser.

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

  • CommWorks/3Com wireless backhaul/carrier gateway equipment

Monitoring Examples

An administrator would check the FACN interface configuration objects in this MIB to confirm frame relay-to-ATM convergence parameters are correctly set for a given wireless backhaul interface, ensuring DLCI-to-VC mappings and interworking parameters match the carrier's network design. An interface showing unexpected or default convergence parameters would reveal an interface that was never fully provisioned, a likely cause of dropped or misrouted wireless backhaul traffic. No sample objects were provided for this MIB, so this description is grounded in its stated configuration purpose.

What Can Be Monitored

  • Frame Relay/ATM convergence interface configuration
  • DLCI-to-VC mapping parameters
  • wireless FACN interface status
Imported Objects

From SNMPv2-SMI

Counter32
Integer32
IpAddress
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-IDENTITY
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

DateAndTime
DisplayString
RowStatus
TruthValue

From USR-DEFINITIONS-MIB

Time1900
UsrConfigStatus
UsrRegID
UsrSpecialU32
commonOBJECT-IDENTITY

How to Use in IPNetwork Monitor

Example using usrFCNIRegReqSent OID:

Select a CommWorks/3Com carrier gateway as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type usrFCNIRegReqSent into the Find box to locate it in the OID tree, then select it and click OK. It reports the total number of Registration Requests sent by the PDSN to the FACN. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.
OIDs

RFC description

Wireless Forwarding Agent Control Network Interface (FACN) management for CommWorks/3Com devices.

Start monitoring CommWorks/3Com carrier gateways 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 USR-FCNI-MIB