CISCO-CONFIG-MAN-MIB

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › CISCO-CONFIG-MAN-MIB

Organization: Cisco Systems, Inc.

Last Updated: 2007-04-27

Category: Cisco Devices, Device Management

Description: Tracks changes and saves of the running configuration, maintaining a history table of configuration management events with details about each change.

IPNetwork Monitor uses several OIDs from this MIB in network discovery and polling the applicable devices. Start monitoring CISCO-CONFIG-MAN-MIB with a free 30-day trial of IPNetwork Monitor.

What Is CISCO-CONFIG-MAN-MIB?

CISCO-CONFIG-MAN-MIB is a Cisco proprietary configuration-management MIB that models where a device's configuration data lives — running, terminal, local (NVRAM/flash), or remote — and records a history of configuration change and save events. It exposes timestamps of the last running-config change and save, the last startup-config change, and a history table of individual change events with their source and destination. It is squarely a software/configuration status MIB: it lets an operator detect drift between running and startup configuration, confirm that changes were actually saved, and identify who or what triggered each change. It has no strong dependency on other MIBs beyond general SNMP conventions, though it is often deployed alongside logging/AAA instrumentation to correlate config events with the user or session responsible. It is widely deployed on Cisco routers and switches for change-tracking, compliance auditing, and triggering automatic configuration backups. Engineers researching cisco-config-man-mib specifically use its ciscoConfigManEvent notification to get alerted whenever a device's running configuration changes.

IPNetwork Monitor allows you to monitor SNMP objects defined in CISCO-CONFIG-MAN-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

  • Cisco routers
  • Cisco switches (IOS/IOS-XE)

Monitoring Examples

ccmHistoryRunningLastChanged versus ccmHistoryRunningLastSaved lets an admin detect that the running configuration was modified but never saved, risking loss on reload. ccmHistoryEventTable/ccmHistoryEventEntry records each change with ccmHistoryEventTime, ccmHistoryEventCommandSource and ccmHistoryEventConfigSource/ccmHistoryEventConfigDestination, allowing a monitoring system to alert on unexpected out-of-band changes. A rising ccmHistoryEventEntriesBumped counter would indicate config changes are occurring faster than the history table (sized by ccmHistoryMaxEventEntries) can retain.

What Can Be Monitored

  • last configuration change time
  • last configuration save time
  • startup vs running configuration drift
  • configuration change history
  • source of configuration changes
Imported Objects

From CISCO-SMI

ciscoMgmtOBJECT-IDENTITY

From CISCO-TC

Unsigned64

From INET-ADDRESS-MIB

InetAddress
InetAddressType

From SNMP-FRAMEWORK-MIB

SnmpAdminString

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Gauge32
Integer32
IpAddress
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
TimeTicks
Unsigned32

From SNMPv2-TC

DateAndTime
DisplayString
TEXTUAL-CONVENTION
TruthValue

How to Use in IPNetwork Monitor

Example using ccmHistoryEventEntriesBumped OID:

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.
OIDs

RFC description

Configuration management and tracking for running, local, and remote configuration storage.

Start monitoring Cisco routers and switches (IOS/IOS-XE config management) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download CISCO-CONFIG-MAN-MIB