IPXHOST-MIB :: usrIpxPortalLargeHopCount

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsIPXHOST-MIBusrIpxPortalLargeHopCount

usrIpxPortalLargeHopCount

Module: IPXHOST-MIB

OID (symbolic): IPXHOST-MIB::usrIpxPortalLargeHopCount

OID (numeric): 1.3.6.1.4.1.429.4.4.10.1.17

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: Displays number of IPX pkts with Large hop count.

What is usrIpxPortalLargeHopCount?

Counts IPX packets received on this interface whose hop count exceeded the normal maximum, typically indicating a routing loop. A rising count here is a strong signal to check for a routing loop somewhere in the IPX topology.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.429.4.4.10.1.17
snmpwalk -v2c -c public <target> IPXHOST-MIB::usrIpxPortalLargeHopCount

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.429.4.4.10.1.17.1
snmpget -v2c -c public <target> IPXHOST-MIB::usrIpxPortalLargeHopCount.1

Start monitoring 3Com/CommWorks broadband access device (IPX host addressing) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the IPXHOST-MIB::usrIpxPortalLargeHopCount OID value, configure state conditions and alerts, and monitor any 3Com/CommWorks broadband access device (IPX host addressing) from a single console.

How to Use in IPNetwork Monitor

Select a 3Com/CommWorks broadband access device (IPX host addressing) 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 usrIpxPortalLargeHopCount 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. Displays number of IPX pkts with Large hop count. 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.429usrCHS-MIB
1.3.6.1.4.1.429.4commonHDR2-MIB
Numeric OIDNameModule
1.3.6.1.4.1.429.4.4usrIpxIPXHOST-MIB
1.3.6.1.4.1.429.4.4.10usrIpxPortalTableIPXHOST-MIB
1.3.6.1.4.1.429.4.4.10.1usrIpxPortalEntryIPXHOST-MIB
1.3.6.1.4.1.429.4.4.10.1.17usrIpxPortalLargeHopCountIPXHOST-MIB