Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Single NCM Multiple NPM

Hello,

Is anyone running a single instance of NCM with multiple installs of NPM? We only have 1:1 right now but since we are upgrading to v10 of NPM, we'd like to have or single NCM instance backup devices that are in our other NPM server. I'd like to enable the integration on the other server but how will it limit the view of nodes? I'm guessing I'll have to give the other users rights to NCM but I only want them to be able to see the configs for their nodes.

Thanks.

Find more posts tagged with

Accepted answers

christineb

Hi Ecornwell - I think what you're wanting to do is something like this:

In this scenario, you have multiple independent NPM instances. All these instances can be easily connected to a single NCM server. The NCM server will then manage devices from all NPM instances. Each integration module user will see only devices according to his NPM instance. Viewable nodes will also be limited by any limitations set via NPM account limitations. One thing to note though, if a user logs in to the NCM web interface or the NCM server application, they will be able to see all the nodes. You can only limit viewable nodes through the integration module (the tab on NPM).

Here's another option:

In this scenario, you would have one NPM main server instance and multiple NPM additional web servers connected to the same database. In this case, all NPM web servers could be connected to the same NCM instance. However, you'll need to do a little bit more in the setup stage - but it's not hard and it's outlined here in this KB article.

This scenario has the same caveats with node view limitations. Node view limitations work for the integration module - but if the user logs in to the standalone NCM website or the server app, they will be able to see all the nodes.

Let us know if this works out for you.

--Christine

All comments

christineb

Hi Ecornwell - I think what you're wanting to do is something like this:

Here's another option:

Let us know if this works out for you.

--Christine

ecornwell

Hi Christine,

The first option is what we wanted to / are now doing. I did the upgrade last Friday and so far everything has been working well. I have two import jobs, one for each server. I also was able to test the RTCN using forwarded syslog traps. (We forward from NPM Server B to NPM Server A retaining the IP address and Server A kicks off the configautodownload program.)

From the sounds of it, the views will be limited unless they log into the actual NCM page which can only be done to the NCM server correct?

Thanks,
Eric

christineb

Fantastic! I'm glad it is working. Yes, views will be limited by your the integration module *and* any account limitations you have set up in NPM unless they log in to the NCM server app or the stand alone NCM website. As long as the users use the integration module (the tab on NPM) they should only see their own nodes.

Let me know if you have any problems and we'll help you get them sorted out.

--Christine

ecornwell

So we've run into a little bit of an issue. Our NCM Server is located at our HQ in the US. The second NPM installation is in our Asian offices. The integration works but the staff at that site said that the server is pretty slow now. I'm guessing that its because it's trying to pull the data from the server across the 330ms link. Is there any way to help speed this up?

renjith

Hello Christneb

Do you have any KB article to point out , how we can achieve the first scenario.

Even we are looking for the same in our environment. So it will be great if you can point out any kb article/document to achieve the first scenario ?

Regards

Renjith

cvachovecj

Hi Renjith,

This deployment type is no longer supported. Please see NCM 7.3 Architecture and Deployment for all possible deployment scenarios.

Regards,

Jiri