CISCO-TRUSTSEC-MIB :: ctsKeystoreFwAlerts

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-TRUSTSEC-MIBctsKeystoreFwAlerts

ctsKeystoreFwAlerts

Module: CISCO-TRUSTSEC-MIB

OID (symbolic): CISCO-TRUSTSEC-MIB::ctsKeystoreFwAlerts

OID (numeric): 1.3.6.1.4.1.9.9.730.1.3.6

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: This object indicates the number of hardware keystore alerts that occurred.

This object is only instantiated when the value of ctsKeystoreType is 'hardwareKeystore'.

What is ctsKeystoreFwAlerts?

Counts the number of alert conditions reported by the hardware keystore firmware, giving visibility into keystore health issues on devices with a hardware keystore.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.730.1.3.6
snmpwalk -v2c -c public <target> CISCO-TRUSTSEC-MIB::ctsKeystoreFwAlerts

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.730.1.3.6.1
snmpget -v2c -c public <target> CISCO-TRUSTSEC-MIB::ctsKeystoreFwAlerts.1

Start monitoring Cisco switches/routers with TrustSec support with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-TRUSTSEC-MIB::ctsKeystoreFwAlerts OID value, configure state conditions and alerts, and monitor any Cisco switches/routers with TrustSec support from a single console.

How to Use in IPNetwork Monitor

Select a Cisco switches/routers with TrustSec support 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 ctsKeystoreFwAlerts into the Find box to locate it in the OID tree, then select it and click OK. This object indicates the number of hardware keystore alerts that occurred. 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.9ciscoCAT2600-MIB
1.3.6.1.4.1.9.9ciscoMgmtCISCO-SMI
Numeric OIDNameModule
1.3.6.1.4.1.9.9.730ciscoTrustSecMIBCISCO-TRUSTSEC-MIB
1.3.6.1.4.1.9.9.730.1ciscoTrustSecMIBObjectsCISCO-TRUSTSEC-MIB
1.3.6.1.4.1.9.9.730.1.3ctsCredentialObjectsCISCO-TRUSTSEC-MIB
1.3.6.1.4.1.9.9.730.1.3.6ctsKeystoreFwAlertsCISCO-TRUSTSEC-MIB