Cisco Bug: CSCuq34687 - ccmHistoryRunningLastChanged is not equal to "0" upon reload
Last Modified
Nov 27, 2020
Products (1)
- Cisco 2600 Series Multiservice Platforms
Known Affected Releases
15.0(2)SG8.0.100
Description (partial)
Symptom: After the reload of the switch ccmHistoryRunningLastSaved is equal to "0" where ccmHistoryRunningLastChanged" is not equal to "0", hence ccmHistoryRunningLastChanged > ccmHistoryRunningLastSaved NMS stations recognize such a situation as running-config was changed but not saved after the restart due to MIB definition: "Object ccmHistoryRunningLastChanged OID 1.3.6.1.4.1.9.9.43.1.1.1 "The value of sysUpTime when the running configuration was last changed. If the value of ccmHistoryRunningLastChanged is greater than ccmHistoryRunningLastSaved, the configuration has been changed but not saved." Conditions: - 4500 running any IOS image including the latest one - 15.0(2)SG8
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Status
- Severity
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases