IPOA-MIB :: ipoaArpClientInArpInReqs

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsIPOA-MIBipoaArpClientInArpInReqs

ipoaArpClientInArpInReqs

Module: IPOA-MIB

OID (symbolic): IPOA-MIB::ipoaArpClientInArpInReqs

OID (numeric): 1.3.6.1.2.1.10.46.1.4.1.3

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: The number of InATMARP requests received by this client.

What is ipoaArpClientInArpInReqs?

Counts InATMARP requests received by this client, useful for confirming that inverse-ARP address discovery traffic is actually reaching this interface.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.10.46.1.4.1.3
snmpwalk -v2c -c public <target> IPOA-MIB::ipoaArpClientInArpInReqs

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.10.46.1.4.1.3.1
snmpget -v2c -c public <target> IPOA-MIB::ipoaArpClientInArpInReqs.1

Start monitoring Vendor-neutral IETF standard (ATM-attached routing equipment, Classical IP/ARP over ATM) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the IPOA-MIB::ipoaArpClientInArpInReqs OID value, configure state conditions and alerts, and monitor any Vendor-neutral IETF standard (ATM-attached routing equipment, Classical IP/ARP over ATM) from a single console.

How to Use in IPNetwork Monitor

Select a device implementing IPOA-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 ipoaArpClientInArpInReqs 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 InATMARP requests received by this client. 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 (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.2mgmtAXON-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.46ipoaMIBIPOA-MIB
1.3.6.1.2.1.10.46.1ipoaObjectsIPOA-MIB
1.3.6.1.2.1.10.46.1.4ipoaArpClientTableIPOA-MIB
1.3.6.1.2.1.10.46.1.4.1ipoaArpClientEntryIPOA-MIB
1.3.6.1.2.1.10.46.1.4.1.3ipoaArpClientInArpInReqsIPOA-MIB