Should deleting a node in NPM automatically delete in NCM if the DBs are synced

mdriskell

Should deleting a node in NPM automatically delete in NCM if the DBs are synced?  Just had one of my engineers inform me that 11 old nodes were still in NCM.  Since I have the two systems integrated I had to sync them back into NPM (which triggered false alerts), remove them from NCM and then delete them from NPM.

Is that supposed to be the process?  I thought I could just delete from NPM.

bcorgey

mdriskell,

yes.  The intended design is to be able to do this from Manage Nodes.

There are acouple of scenerios which can prevent this.

1) On NPM 10.2.x and you have multiple pollers

   -- When deleting from an additional poller, there is a permission issue on the primary poller in the Message Queing.

       -- Fix: Thanks to Dev: "

1. on primary poller -> right click on this computer -> manage -> goto to Features -> Message Queuing -> Private Queues ->

SolarWinds/InformationService/Orion/IndicationReporter

2. right click -> Properties -> Security

3. add user ANONYMOUS LOGON with right "Send Message"

4. try to delete node from additional poller.

In case it doesn't help, I would try to add 'Full rights' and also allow user "Everyone". But according microsoft documentation it's enough "anonymous logon" with send rights. Not sure how strict your policy is.

2) There is a timeout when removing the node from the NCM database

  -- Generally due to too many configs in the database or the PolicyCacheResults table is corrupt

  -- For this I suggest opening a support ticket as some database Cleanup is going to be necesary

In either case, the only way to properly get the nodes properly removed from the NCM database will be to do a node sync again.  This will add the devices back to the core.

Then once the issue is resolved (1 or 2) the node can be succesfully removed from Manage Nodes in the Admin Settings.

If this is an issue realted to the polling engine as described in NPM 10.2, this issue is resolved in NPM 10.3