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
Store

NPM / SAM Integration - Design Question

Hi All,

In the process of setting up a new environment. Will be running NPM, NCM, NTA, IPAM, SAM and VMAN. The intention is to segregate NPM/NCM/NTA and potentially IPAM on its own server, while running SAM/VMAN on its own server. This is being done to limit the dependencies and interaction between the network team and systems operations team for system availability, while still providing integration under a single platform.

Ultimately I want to be sure that this approach is sound, and that so long each product points to the same shared Orion database, and enabling integration from within the respective products, that this scenario will work as intended - which is an integrated platform for all products within the Orion framework.

Last question, is there anything prohibiting IPAM from running on the NPM/NCM server, if the server is spec'ed accordingly? I have only skimmed the technical documents so I am sure this documented but easier to ask.

Thanks

Find more posts tagged with

Accepted answers

jblankjblank

crw You cannot install NPM, NTA, NCM, and IPAM on one server, and have them sharing the same Orion Database for a SAM, VMAN installation on a separate server. Installing the modules on separate instances would require separate databases. If you are looking for a single centralized monitoring platform, each module should be installed on the same server, and point to a single database. Custom accounts,views, and access can then be created to limit visibility between your Network and Systems team if you wish to do so.

All comments

jblankjblank

crw

Thank you. So in other words, there is no way to provide a distributed platform by product/server (split between Network and Infrastructure Operations teams) while keeping a seamless and integrated experience between all the products? If that is the case so than so be it. Would like to confirm before naming the hosts and moving forward.

Thanks

jblankjblank

Correct. You cannot share the same database between two separate instances. If you did decide to deploy two separate instances, you could ultimately leverage the Enterprise Operations Console. EOC would provide an extended layer of visibility for both instances, but not provide a single management/ administration layer. EOC will roll up data in order to allow users the ability to begin investigation from a single, consolidated dashboard, but then drill down to deeper information by directing the user to the instance that is responsible for monitoring a particular entity. It is another option, but simply customizing accounts along with unique views and limitations may be easier.

crw

Thank you for the explanation, very helpful!