Running vs Startup Config Conflicts 97% Unknown

Can anyone advise on how I can resolve this issue? (Running vs Startup Config Conflicts 97% Unknown)

Since backups are working 100% I don't understand why the Running vs Startup Config Conflicts cannot be ascertained. Do the two use differing methods of connectivity? I would have expected them to both use SSH? Any ideas?

Any assistance appreciated, our version info is Orion Platform 2014.2.0, SAM 6.1.1, QoE 1.0, IPAM 4.1, NCM 7.3, NPM 11.0, WPM 2.0.1, Toolset 11.0.0, IVIM 1.10.0 1995-2014 SolarWinds Worldwide, LLC. All Rights Reserved.

Find more posts tagged with

ncm

cisco

unknown

Accepted answers

clubjuggle

Yes, that is the reason. If you were downloading both the running and startup configs, you would see both on the NCM Nost List.

The comparison happens locally, so you need to have both the running and startup configurations downloaded in order to make use of the compare job.

All comments

clubjuggle

Have you selected to download both the startup and running configurations in your config backup job?

seabro

Thanks for your reply Terry. When I look at the configs under 'NCM Node List' I only see 'running' so maybe thats all we are backing up.

I take it this is the reason? (I can't check properly as I don't have NCM admin access).

clubjuggle

Yes, that is the reason. If you were downloading both the running and startup configs, you would see both on the NCM Nost List.

The comparison happens locally, so you need to have both the running and startup configurations downloaded in order to make use of the compare job.