Deleting objects in NPM

We're using the latest version of NPM. Several servers were added to the monitor database but have since been retired. I have followed the instructions for deleting a node through the Admin portion of the web interface, but when the screen refreshs, the servers are still there. How do I get rid of these nodes?

Thanks, Don

Find more posts tagged with

npm_9

Accepted answers

All comments

mcbridea

Are you using this method?

Admin -> Manage nodes.

Mark check box next to nodes to remove.
Click delete on for right.
Click OK

dcongleton

Yes. I get a popup that asks if I'm sure and I clcik OK. The screen refreshes and the node is still there. I've tried it on a couple of nodes and I get the same result.

mcbridea

Hmmm. I can't duplicate that behavior. I'd try a browser cache clear and if that does not work put a call into support.

viol8tor

Can I ask what version of browser you are using?

Unfortunately, I find different browsers have different results to the web admin functions. (For example, Safari can delete, unmanage but not add.)

Also, make sure you are not refreshing the screen manually. You have to wait for NPM to finish its procedures. It should automatically update the page when the deletes are complete.

I've learned to limit mass deletes to no more than 50 or 60 at a time, depending on how many interfaces a node has.

- v

dcongleton

I've tried with Firefox 3.5.5 and IE8. I am waiting for the screen to refresh on it's own. This is a new install of NPM so there isn't a lot in it right now. I have 8-10 nodes I am trying to edlete that are either retired or dev nodes I don't want clutering up the view.

Don

viol8tor

Couple of suggestions -

Check your browser's cache settings

From Web Console - select Admin, click on 'clear web cache'

If this does not help, delete one of the devices through the 'Orion System Manager' on the server itself.

If this works, then you may need to re-run configuration wizard and reinstall the website.

If this doesn't work then you may want to open a ticket, you may have a problem with your DB.

-v

RLM33

I have also had this same issue, using the latest version of the Orion package (the latest as of Dec 1, 2010). Continuous attempts at clearing the web cache in SW had no affect, and I do not cache my local pages for that very reason.

Attempts at rebooting the Orion server also produced no results. Using the "System Manager" is not not an option in this version if i recall correctly, so I edited the Nodes DB table directly to remove 3 separate IP's that were having this issue. This did correct it, and we havn't had any issues since. The delete node script from the GUI does seem to work right up to the very end, with the exception of not executing the delete process in the database.