The plan is to monitor:

OID: .1.3.6.1.4.1.9.9.43.1.1.1 | ccmHistoryRunningLastChanged | TimeTicks (SNMPv2-SMI)
OID: .1.3.6.1.4.1.9.9.43.1.1.2 | ccmHistoryRunningLastSaved| TimeTicks (SNMPv2-SMI)

If the value of ccmHistoryRunningLastChanged is greater than ccmHistoryRunningLastSaved, the configuration has been changed but not saved.

It’d be nice that if the above stayed in a problem state for >1 hour to send an alarm via NMS. One day! 🙂

If you do this – feel free to drop me a line.