CISCO-CONFIG-MAN-MIB :: ccmHistoryEventEntriesBumped

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › CISCO-CONFIG-MAN-MIB › ccmHistoryEventEntriesBumped

ccmHistoryEventEntriesBumped

Module: CISCO-CONFIG-MAN-MIB

OID (symbolic): CISCO-CONFIG-MAN-MIB::ccmHistoryEventEntriesBumped

OID (numeric): 1.3.6.1.4.1.9.9.43.1.1.5

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: The number of times the oldest entry in ccmHistoryEventTable was deleted to make room for a new entry.

What is ccmHistoryEventEntriesBumped?

Counts how many times the oldest entry in the configuration change history table was discarded to make room for a new event, indicating history table churn.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.43.1.1.5
snmpwalk -v2c -c public <target> CISCO-CONFIG-MAN-MIB::ccmHistoryEventEntriesBumped

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.43.1.1.5.1
snmpget -v2c -c public <target> CISCO-CONFIG-MAN-MIB::ccmHistoryEventEntriesBumped.1

SNMPv3 example:

snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> ccmHistoryEventEntriesBumped.1

Start monitoring Cisco routers and switches (IOS/IOS-XE config management) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-CONFIG-MAN-MIB::ccmHistoryEventEntriesBumped OID value, configure state conditions and alerts, and monitor any Cisco routers and switches (IOS/IOS-XE config management) from a single console.

How to Use in IPNetwork Monitor

Select a Cisco router or switch (IOS/IOS-XE config management) 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 ccmHistoryEventEntriesBumped into the Find box to locate it in the OID tree, then select it and click OK. The number of times the oldest entry in ccmHistoryEventTable was deleted to make room for a new entry. 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.43ciscoConfigManMIBCISCO-CONFIG-MAN-MIB
1.3.6.1.4.1.9.9.43.1ciscoConfigManMIBObjectsCISCO-CONFIG-MAN-MIB
1.3.6.1.4.1.9.9.43.1.1ccmHistoryCISCO-CONFIG-MAN-MIB
1.3.6.1.4.1.9.9.43.1.1.5ccmHistoryEventEntriesBumpedCISCO-CONFIG-MAN-MIB