USR-FCNI-MIB :: usrFCNIRegReqSent

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › USR-FCNI-MIB › usrFCNIRegReqSent

usrFCNIRegReqSent

Module: USR-FCNI-MIB

OID (symbolic): USR-FCNI-MIB::usrFCNIRegReqSent

OID (numeric): 1.3.6.1.4.1.429.4.85.2.1

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: Total number of Registration Requests sent by the PDSN to the FACN.

What is usrFCNIRegReqSent?

Total number of Mobile IP Registration Requests the PDSN has sent to the 1st configured FACN. A count that isn't climbing at all despite active subscribers can indicate the PDSN isn't attempting registration with this FACN.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.429.4.85.2.1
snmpwalk -v2c -c public <target> USR-FCNI-MIB::usrFCNIRegReqSent

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.429.4.85.2.1.1
snmpget -v2c -c public <target> USR-FCNI-MIB::usrFCNIRegReqSent.1

Start monitoring CommWorks/3Com carrier gateways with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the USR-FCNI-MIB::usrFCNIRegReqSent OID value, configure state conditions and alerts, and monitor any CommWorks/3Com carrier gateways from a single console.

How to Use in IPNetwork Monitor

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.

OID Breakdown

Upper-level ancestors (9 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.429usrANIC-MIB
1.3.6.1.4.1.429.4commonHDR2-MIB
1.3.6.1.4.1.429.4.85usrFCNIUSR-DEFINITIONS-MIB
Numeric OIDNameModule
1.3.6.1.4.1.429.4.85.2usrFCNIRegReqRepStatsUSR-FCNI-MIB
1.3.6.1.4.1.429.4.85.2.1usrFCNIRegReqSentUSR-FCNI-MIB