There use to be a scheduled task I ran that imported the NPM nodes to NCM, how is this done now? I have many new nodes in NPM that are not in NCM.
On a first time installation/upgrade to NCM 7.0, a synchronization must be run.
Synchronization will update the NPM database with NCM nodes and other properties that are not currently present in the NPM database.
From this point forward you will not need to run synchronize and you can only use the website to add/remove nodes.
Adding a new node, you use NPM to add and there is an option to also add to NCM.
Deleting an NPM node will also delete the NCM node.
If you have NPM nodes that are not a part of NCM, you can go to Settings/NCM Settings/Manage nodes/ then select the nodes you want and simply click add to NCM.
Go to your NPM website
Click on the up right side where it reads Settings
Click on NCM settings
Go to the NCM Node management section and click on Add or Manage Nodes
On the right hand side click on Node Sync
Click on Synchronize database
NCM nodes must also be managed in the Orion Core database. In case there is any disparity between the databases, we run a node synchronization next.
I had a question regarding the synchronization between NCM & NPM. This is now the second time I have ran into this particular issue and am wondering if I am doing something wrong or if there is something missing in the process:
Node X is in NPM and is also in NCM. (Not positive if node was added to NCM after the fact - after being added to NPM or if it was added to NCM at the time the node was created and added to NPM). Several months later Node X is now going to be decommissioned. I go into NPM node management and delete the node.
Next day I see an exception report with Node X on it. The nightly backup job kicked off and attempted to download Node X configuration and failed. I check both NPM & NCM databases and sure enough - Node X was not in NPM database but it still resided within NCM. To correct this issue I must re-synchronize the NCM to the NPM database. After performing this task Node X is now back in NPM database. I then go to NCM and delete the node from NCM database which in turn removes it from NPM and all is good.
I believe that all documentation states that by deleting Node X within NPM it will then automatically delete the node from NCM, but I have not found that yet. Is it supposed to work like that or am I mistaken? Also, have you heard of this scenario happening to other users or am I just special ?
Sincerely,
NetEng33
Hi NetEng33,
What version of NCM and NPM do you have?
Regards,
Jiri
Woops, Sorry:
NPM 10.4 and NCM 7.1
I ran into this while on NPM 10.3 as well.
I recently had an issue like this. It turned out to be we had about 3 years of back up configs from each device and when we would go to delete a node, it would delete out of npm but then would end up timing out and not deleting out of ncm because of too much data.
So my questions are: How often are you downloading configs and how often are you then purging those configs?
Ah...interesting. So I am configured to download each evening on every Cisco device. I remember setting up the retention for no longer than 30 days. But I will have to dig where that setting is again to confirm. We have not been performing backups through the NCM product for even a year now, however there are multiple config files.
Question???: So how do you know NCM was timing out when deleting? Is there a place to go and see the exception/warning of the timeout - like a log file or something?
Respectfully,
It took some troubleshooting with support but we actually saw the time out on the sql server itself. From what i was told by support a good way to gauge is to check to see the size of config archive.
If you are in your orion server and open up Database manager, expand down to see config management section and right click and do database details and then take a look at the tables tab. If Config archive and cachediffresults are over 4 gb's that will probably be your problem. If your still having troubles i would suggest opening up a case from what my support engineer was saying is this is a pretty common occurrence.
Very helpful fletcher, thanks. Looks like I am running under 1GB so I will definitely open a case just to see what they say. However, I will be covering with my NMS Team of this anomaly and it appears of we delete from NCM first then it all works great with no hiccup - so to watch for this when deleting nodes and head off any exceptions on the nightly backup results.
Peace,
Thank you
">LorenzoBrizeno
'
This was so excellent!!!!!
Cheryl
You are very welcome. I hope all threads helped. I enjoy Thwack as it is
one of the most active communities I've ever been a part of. This is a big
part of why the solutions work so well; the excellent collaboration between
the users as well as Solarwinds.
Chad Warner
On Jan 9, 2014 9:32 AM, "cmatrask" <
