FR-MFR-MIB :: mfrBundleResequencingErrors

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › FR-MFR-MIB › mfrBundleResequencingErrors

mfrBundleResequencingErrors

Module: FR-MFR-MIB

OID (symbolic): FR-MFR-MIB::mfrBundleResequencingErrors

OID (numeric): 1.3.6.1.2.1.10.47.2.3.1.19

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: A count of the number of resequencing errors. Each event may correspond to multiple lost frames. Example: Say sequence number 56, 59 and 60 is received for DLCI 100. It is decided by some means that sequence 57 and 58 is lost. This counter should then be incremented by ONE, even though two frames were lost.

What is mfrBundleResequencingErrors?

A count of resequencing error events on this bundle, where one or more consecutive frames were found missing; each gap counts as one event even if multiple frames were lost.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.10.47.2.3.1.19
snmpwalk -v2c -c public <target> FR-MFR-MIB::mfrBundleResequencingErrors

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.10.47.2.3.1.19.1
snmpget -v2c -c public <target> FR-MFR-MIB::mfrBundleResequencingErrors.1

Start monitoring Vendor-neutral Frame Relay WAN router/access device, any manufacturer (Multilink Frame Relay, RFC 3020) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the FR-MFR-MIB::mfrBundleResequencingErrors OID value, configure state conditions and alerts, and monitor any Vendor-neutral Frame Relay WAN router/access device, any manufacturer (Multilink Frame Relay, RFC 3020) from a single console.

How to Use in IPNetwork Monitor

Select a device implementing FR-MFR-MIB 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 mfrBundleResequencingErrors into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. It reports a count of the number of resequencing errors. 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 between polls, since a rising count of errors, failures, or discards often points to a real underlying problem. Click Finish to create the monitor; you can adjust any parameter later.

OID Breakdown

Upper-level ancestors (7 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.2mgmtAPERTUS-NPG-MIB
1.3.6.1.2.1mib_2AXON-MIB
1.3.6.1.2.1.10transmissionCHECKPOINT-MIB-2
Numeric OIDNameModule
1.3.6.1.2.1.10.47mfrMibFR-MFR-MIB
1.3.6.1.2.1.10.47.2mfrMibBundleObjectsFR-MFR-MIB
1.3.6.1.2.1.10.47.2.3mfrBundleTableFR-MFR-MIB
1.3.6.1.2.1.10.47.2.3.1mfrBundleEntryFR-MFR-MIB
1.3.6.1.2.1.10.47.2.3.1.19mfrBundleResequencingErrorsFR-MFR-MIB