STN-IPROUTING-MIB :: stnIpRtCacheMisses

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsSTN-IPROUTING-MIBstnIpRtCacheMisses

stnIpRtCacheMisses

Module: STN-IPROUTING-MIB

OID (symbolic): STN-IPROUTING-MIB::stnIpRtCacheMisses

OID (numeric): 1.3.6.1.4.1.3551.2.12.1.1.2

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: The number of failed attempts to locate an IP address in the route cache.

What is stnIpRtCacheMisses?

This counter tracks the number of failed lookups for an IP address in the route cache, meaning the router had to fall back to a slower full route lookup. A high miss rate relative to cache hits can indicate the cache is undersized for the traffic pattern.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.3551.2.12.1.1.2
snmpwalk -v2c -c public <target> STN-IPROUTING-MIB::stnIpRtCacheMisses

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.3551.2.12.1.1.2.1
snmpget -v2c -c public <target> STN-IPROUTING-MIB::stnIpRtCacheMisses.1

Start monitoring Spring Tide Networks (Lucent) multiservice edge router (route-cache/circuit status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the STN-IPROUTING-MIB::stnIpRtCacheMisses OID value, configure state conditions and alerts, and monitor any Spring Tide Networks (Lucent) multiservice edge router (route-cache/circuit status) from a single console.

How to Use in IPNetwork Monitor

Select a Spring Tide Networks (Lucent) multiservice edge router (route-cache/circuit status) 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 stnIpRtCacheMisses into the Find box to locate it in the OID tree, then select it and click OK. The number of failed attempts to locate an IP address in the route cache. 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 (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.3551springtidenetSPRING-TIDE-NETWORKS-SMI
1.3.6.1.4.1.3551.2stnSystemsSPRING-TIDE-NETWORKS-SMI
Numeric OIDNameModule
1.3.6.1.4.1.3551.2.12stnIpRoutingSTN-IPROUTING-MIB
1.3.6.1.4.1.3551.2.12.1stnIpSTN-IPROUTING-MIB
1.3.6.1.4.1.3551.2.12.1.1stnIpRtCacheSTN-IPROUTING-MIB
1.3.6.1.4.1.3551.2.12.1.1.2stnIpRtCacheMissesSTN-IPROUTING-MIB