SNMP-TSM-MIB :: snmpTsmInvalidCaches

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › SNMP-TSM-MIB › snmpTsmInvalidCaches

snmpTsmInvalidCaches

Module: SNMP-TSM-MIB

OID (symbolic): SNMP-TSM-MIB::snmpTsmInvalidCaches

OID (numeric): 1.3.6.1.2.1.190.1.1.1

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: The number of incoming messages dropped because the

tmStateReference referred to an invalid cache.

What is snmpTsmInvalidCaches?

This read-only Counter32 tallies incoming SNMP messages dropped because the tmStateReference pointed to an invalid or expired cache entry in the Transport Security Model. Admins monitor this counter to detect problems in the underlying transport security session state, such as stale or mismatched cache references between the transport layer and TSM. For example, a rising count after a network device reboot could indicate transport sessions were torn down while stale cache references were still being used.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.190.1.1.1
snmpwalk -v2c -c public <target> SNMP-TSM-MIB::snmpTsmInvalidCaches

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.190.1.1.1.1
snmpget -v2c -c public <target> SNMP-TSM-MIB::snmpTsmInvalidCaches.1

Start monitoring vendor-neutral, standards-based MIB, SNMPv3 agents/managers using transport-based security, SSH/TLS (security-event statistics) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the SNMP-TSM-MIB::snmpTsmInvalidCaches OID value, configure state conditions and alerts, and monitor any vendor-neutral, standards-based MIB, SNMPv3 agents/managers using transport-based security, SSH/TLS (security-event statistics) from a single console.

How to Use in IPNetwork Monitor

Select a device implementing SNMP-TSM-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 snmpTsmInvalidCaches into the Find box to locate it in the OID tree, then select it and click OK. The number of incoming messages dropped because the tmStateReference referred to an invalid 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 (6 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
Numeric OIDNameModule
1.3.6.1.2.1.190snmpTsmMIBSNMP-TSM-MIB
1.3.6.1.2.1.190.1snmpTsmMIBObjectsSNMP-TSM-MIB
1.3.6.1.2.1.190.1.1snmpTsmStatsSNMP-TSM-MIB
1.3.6.1.2.1.190.1.1.1snmpTsmInvalidCachesSNMP-TSM-MIB