
So as of about 2 weeks ago, our NCM is showing the nodes (Switches, VGs, WLC, etc) that we download nightly configs from for backups as unmanaged or unknown. Because of this, NCM refuses to download their configs, but we're still able to ping, successfully test SNMP and validate login credentials.
Does anyone know how to change the device status? I've even attempted deleting and re-adding the nodes, but it's quite a long process to do for each individual one and doesn't really fix the issue as then it just shows as unknown.
Any advice?
If you are using NCM 7.0, make sure you have the latest 7.0.1 update applied.
Next make sure you have run a db synchronization on the web.
Hi
I´m running 7.0.2, and have the same issue.
Care to elaborate on the "run db sync on the web" ?
Hi Jesper,
7.0.2 is the internal version number and is actually 7.0 and not the follow up service release 7.0.1, which internally shows as v7.0.3. I know it’s a little confusing and we plan on changing how version numbers are displayed in future releases.
Therefor you should update to 7.0.1 available in your customer portal. What Lorenzo refers to, by node sync in web, has likely been done already when you first updated to 7.0 and likely does not need to be rerun. However if you do want to ever rerun the sync it is located in the Manage NCM nodes page on the top right. It should only need to be run once, but can be usefull if you ever restore from old database backups and the Nodes in the NCM and Orion Core databases are out of sync.
Hope this helps!
Matt