MPC-MIB :: mpcStatTxMpoaResolveRequests

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsMPC-MIBmpcStatTxMpoaResolveRequests

mpcStatTxMpoaResolveRequests

Module: MPC-MIB

OID (symbolic): MPC-MIB::mpcStatTxMpoaResolveRequests

OID (numeric): 1.3.6.1.4.1.353.5.8.1.1.2.5.1.1

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: The number of MPOA Resolve Requests transmitted by this MPC.

Discontinuities in the value of this counter can occur at re-initialization of the management system, and/or re-initialization of the MPC, and at other times, as indicated by the value of mpcDiscontinuityTime.

What is mpcStatTxMpoaResolveRequests?

A running count of MPOA Resolution Requests this MPC has transmitted trying to establish ATM shortcuts. Admins watch this alongside the various resolve-reply counters to see how many of the MPC's resolution attempts are succeeding versus failing.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.353.5.8.1.1.2.5.1.1
snmpwalk -v2c -c public <target> MPC-MIB::mpcStatTxMpoaResolveRequests

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.353.5.8.1.1.2.5.1.1.1
snmpget -v2c -c public <target> MPC-MIB::mpcStatTxMpoaResolveRequests.1

Start monitoring Vendor-neutral ATM Forum standard (MPOA-capable ATM switch/edge device) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the MPC-MIB::mpcStatTxMpoaResolveRequests OID value, configure state conditions and alerts, and monitor any Vendor-neutral ATM Forum standard (MPOA-capable ATM switch/edge device) from a single console.

How to Use in IPNetwork Monitor

Select a device implementing MPC-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 mpcStatTxMpoaResolveRequests 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. The number of MPOA Resolve Requests transmitted by this MPC. 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 (8 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.353atmForumATM-FORUM-ILMI40-MIB
1.3.6.1.4.1.353.5atmForumNetworkManagementATM-FORUM-SNMP-M4-MIB
Numeric OIDNameModule
1.3.6.1.4.1.353.5.8atmfMpoaMPC-MIB
1.3.6.1.4.1.353.5.8.1mpoaMIBMPC-MIB
1.3.6.1.4.1.353.5.8.1.1mpoaMIBObjectsMPC-MIB
1.3.6.1.4.1.353.5.8.1.1.2mpcObjectsMPC-MIB
1.3.6.1.4.1.353.5.8.1.1.2.5mpcStatisticsTableMPC-MIB
1.3.6.1.4.1.353.5.8.1.1.2.5.1mpcStatisticsEntryMPC-MIB
1.3.6.1.4.1.353.5.8.1.1.2.5.1.1mpcStatTxMpoaResolveRequestsMPC-MIB