Move NCM from main Orion poller server to my addtional webserver?

Hi all…

I have performance problems on my Orion pollers, so I am trying to share the load. I now have an SLX engine, with 4 additional SLX pollers and I have an additional web server installed to a separate server. I have NCM installed on the main poller, so I think I should move it off of this poller, and stick it somewhere else. I think the obvious choice is the additional web server, as it is not too busy.

Do you see any problems with this? I have installed the NCM/NPM integration module, so will this cause a problem when moving NCM?

Any assistance would be much appreciated

Cheers

dan

Find more posts tagged with

Accepted answers

All comments

chris.lapoint

There shouldn't be any problems with this deployment approach, but you'll need to take some manual steps to import the encryption certificate for the NCM credentials.

See this KB article for details: http://support.solarwinds.com/kbase/ProblemDetail.cfm?ID=1121

FormerMember

i should have stated also, that the current NCM is blank, i.e. no devices are held within it, but i am about to roll it out and replace kiwi backup on sever sites with my centralised NCM

i will read the link anyway an check if it is something I have to do being that my NCM is still virgin...

cheers for the reply mate!

dan

FormerMember

Hi Chris / Forum dudes

I have still not made this change but i am about to, and then i started to think about other potential issues. basically, I currently have the NCM installed on my main NPM server. this means I have a single syslog service that feeds both NCM and NPM, thus giving the NCM the support it needs for being notified of config changes etc. If i move NCM to the additional-webserver server, then it will have its own syslog service installed. I would then have to send ALL syslogs from ALL network devices to both servers.

My question, if i move NCM away from the NPM poller server, but still have the integration module installed, can i still send all syslog to the main NPM, and NCM will pick up the relevant syslogs?

i definitely do not want to store syslog twice in the database....

Also, what are the specific steps for moving NCM in this environment, i have checked the link above, and it gives information about the encryption etc, but what about trhe basic steps. do i have to uninstall and reinstall the NCM integration module, and i likely to hit any typical SolarWinds wizard hiccups when the database gets in a mess?

My NCM currently has zero devices within it, but the NPM is mission critical with 10-15k interfaces, volumes etc... so i can not afford much downtime...

any help would be much appreciated

cheers

dan

chris.lapoint

My question, if i move NCM away from the NPM poller server, but still have the integration module installed, can i still send all syslog to the main NPM, and NCM will pick up the relevant syslogs?

No. The NCM integration module is a website-only integration with Orion NPM. It doesn't provide any "server" capabilities so it won't forward Syslog messages received by Orion NPM to the NCM server.

Also, what are the specific steps for moving NCM in this environment, i have checked the link above, and it gives information about the encryption etc, but what about trhe basic steps. do i have to uninstall and reinstall the NCM integration module, and i likely to hit any typical SolarWinds wizard hiccups when the database gets in a mess?

You should be able to leave the NCM integration module installed on your main Orion NPM website. Once you move the NCM server over to the new system, you'll need to go to Admin > NCM settings in your Orion website and point the NCM integration module to the new NCM server.

mleinio

I have still not made this change but i am about to, and then i started to think about other potential issues. basically, I currently have the NCM installed on my main NPM server. this means I have a single syslog service that feeds both NCM and NPM, thus giving the NCM the support it needs for being notified of config changes etc. If i move NCM to the additional-webserver server, then it will have its own syslog service installed. I would then have to send ALL syslogs from ALL network devices to both servers.

My question, if i move NCM away from the NPM poller server, but still have the integration module installed, can i still send all syslog to the main NPM, and NCM will pick up the relevant syslogs?

Just an untested idea: Would it be possible to enter a syslog server rule in the NPM syslog server so that the config change notification syslog messages would be redirected/copied to the NCM syslog server?

You still were to be running two separate syslog servers but this way the devices would send the syslogs only to the NPM server, and NPM server is then responsible for notifying the NCM syslog server about the config changes.

Markku

mleinio

Actually I'm not sure if the NCM syslog server got the correct device IP address in that approach. I'm not near our servers so I cannot test this at the moment.

Markku