NCM 7.4 Daily Config Change Report says Cisco IOS version reverted to a previous IOS version after HF2 applied.

rschroeder‌,

Are you sure you are talking about NCM 7.4 HotFix2?

HF2 only formally ships device template for Allied Telesis.

Aren't you talking about HF1? NCM v7.4.0 Hot Fix 1 is Now Available

Jiri

Hi, Jiri,

Yes, that’s the item that was changed. We upgraded to HF2 so we could get the QoE additional licenses.

Should I have referenced NPM instead of NCM for that?

Rick

Rick,

Yes, I think you are talking about Core/NPM Hot Fix.

I believe you should open a support case so that we can investigate properly.

Jiri

Will do.  Actually, one of my co-workers, Joe P., will open that case.

The problem is identified, and is not an Orion issue, but caused by the PIBKAC.

My backup schedule has resulted in NCM comparing the startup config and running config on multiple devices that have been recently upgraded.  The running-config references the new code version, the startup-config references the old code version, NCM sees the difference and reports it.

The fix is two step: 

1. Always copy running-config to startup-config.  I've reminded the Technologists of this; hopefully it will stay with them.
2. Schedule the Config Comparison Report to run at a time where it compares only running-configs, rather than comparing current running-config to the last-downloaded-config (which may be a startup-config).

Thanks for your considerations!