CISCO-RF-MIB :: cRFHistoryColdStarts

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-RF-MIBcRFHistoryColdStarts

cRFHistoryColdStarts

Module: CISCO-RF-MIB

OID (symbolic): CISCO-RF-MIB::cRFHistoryColdStarts

OID (numeric): 1.3.6.1.4.1.9.9.176.1.3.3

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: Indicates the number of system cold starts. This includes the number of system cold starts due to switchover failure and the number of manual restarts.

What is cRFHistoryColdStarts?

Reports the cumulative count of system cold starts, including those caused by failed switchovers and manual restarts, useful for tracking system stability.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.176.1.3.3
snmpwalk -v2c -c public <target> CISCO-RF-MIB::cRFHistoryColdStarts

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.176.1.3.3.1
snmpget -v2c -c public <target> CISCO-RF-MIB::cRFHistoryColdStarts.1

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

How to Use in IPNetwork Monitor

Select a Cisco routers/switch 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 cRFHistoryColdStarts into the Find box to locate it in the OID tree, then select it and click OK. Indicates the number of system cold starts. This includes the number of system cold starts due to switchover failure and the number of manual restarts. 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.9ciscoCAT2600-MIB
1.3.6.1.4.1.9.9ciscoMgmtCISCO-SMI
Numeric OIDNameModule
1.3.6.1.4.1.9.9.176ciscoRFMIBCISCO-RF-MIB
1.3.6.1.4.1.9.9.176.1ciscoRFMIBObjectsCISCO-RF-MIB
1.3.6.1.4.1.9.9.176.1.3cRFHistoryCISCO-RF-MIB
1.3.6.1.4.1.9.9.176.1.3.3cRFHistoryColdStartsCISCO-RF-MIB