Removing old Orion server

This is a bit of an odd one.. not a mjaor issue just a bit annoying... about 3 months ago I migrated Orion from the test enviroment onto a new production server.... all when perfectly and the new server was up and running same day...

However, during this process I renamed the old box and put it one the LAN to pull down some final bits of data and customisations.. during this period the new server found the old box and became 'aware' of its presence...

Since this happened everytime I open the Orion console on the server it opens a screen to ask which instance I would like to access (the old server or this server)... the old server is red because it no longer exists so I just select the new server and off I go....

I know it is just an extra step but I cannot see how to get rid of the old entry.. I have opened the polling engine manager tool and it even shows up there... I have tried to delete it from this tool but 20 seconds later it comes back...

Ideas or thoughts would be nice... it is probably very simple to get rid of I am just being too complicated in my approach.

Martin J. Hamilton... lost in a sea of snmp...

Find more posts tagged with

new_install

old_hardware

load_balancer

Accepted answers

All comments

Isaac

Hi Martin,

This may seem like a basic question but:
Have you checked the old server to verify that it does not have any of the SW services or processes still active?

I can't imagine what else could be responsible for this issue.

It sounds like a case for the SW support goons.

moedavis

I had the same problem. Give the folks at support a call, they will show you how to set your database to point to only one polling engine. The entries for the old server are still residing in the database.

I hope this helps,

Josh_Stephens

Martin,
To resolve this issue, open the Orion NPM database the Database Manager. View the "Engines" table by right-clicking on the table name and "querying" the table. You should see two entries - one for your test server and one for your production server. After you've verified which one you want to remove, simply right-click on the row for the test server and click "Delete". This should resolve the issue. As an extra safety measure, you could backup the database before completing this procedure.

HTH,
Josh

mjhamilton

magic.. jobs a good'un

Martin J. Hamilton... lost in a sea of snmp...

pozurita

I have a similar issue with 9.1 --new install to replace old server hardawre. First, the 9.1 server is still pre production while the "old" server is still the primary SW server I am trying to move all the objects via the "load balancer" method but when I do the objects do no shouw current statistics (charts and such) in web console or NPM sysmtem manager. I want to make sure this box is working fine with a few devices polling correctly before I move all via load balncer--is this the wrong approach? the old server just popped up when i installed the new one and restored the DB from the old one to the new box. If I delete the old one the way u suggest above will I make changes to the old one (i only plan to delete it from the new server) i will not make any changes to the production server itslef untill I get this issue resolved .