This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

SAM deployment with existing NPM

Hi Team,

We are already having NPM 12.5 in our environment.Now we are going to deploy SAM.Our requirement to have a consolidated view of SAM and NPM events in a single pane of glass.If we deploy SAM on a seperate orion server with two APEs and use the same database which NPM is using for deployment.Will it work or we have to deploy SAM on the NPM server to use existing NPM database and then we can add two APEs?

As we have to use same NPM database which is already in production. What all precautions has to be taken before deploying SAM on the same database so that we can restore NPM in case of any issues?

Please remember we are having component based licensing for NPM and node based licensing for SAM, we definitely need APEs for SAM.Do we need any license for APEs?

Thanks

Suman

  • 1. Deploy SAM on the NPM server to use existing NPM database and then install two APEs (which will again connect to same database).

    2. You need additional license for APE's (In total you will have your NPM license, SAM license and 2 X Additional poller license).

    Note: SAM on a seperate orion server with two APEs and use the same database which NPM - This will not work.

  • Hi Vinay,

    Thanks for your response.

    One thing to clarify, we have node based licensing for SAM and if we only use APEs for SAM polling,in that case do we still need license for APEs?

    Thanks

    Suman

  • For Node based licensing in SAM you may not need additional license for APEs. Refer SAM licensing model

  •   wrote:

    1. Deploy SAM on the NPM server to use existing NPM database and then install two APEs (which will again connect to same database).

    2. You need additional license for APE's (In total you will have your NPM license, SAM license and 2 X Additional poller license).

    Note: SAM on a seperate orion server with two APEs and use the same database which NPM - This will not work.

    You'll want to install SAM on the same server, but then you can ​assign​ your SAM monitors to the APEs if your concern is keeping the extra load of your primary NPM polling engine.

  • Hi,

    Hence we can conclude that SAM should be deployed on NPM server so that both can use same DB and we will get consolidated view of events from both the modules.In case of APEs  we can only utilize free APEs only for SAM polling as we have node based licensing for SAM.

    As i said we are already having NPM and need to deploy SAM on the same server, any precaution before doing this activity so that existing NPM doesn't get affected?

    Thanks

    Suman

  • No matter what you have if you need an additional poller you will have to purchase APE license.

  • Hence we can conclude that SAM should be deployed on NPM server so that both can use same DB and we will get consolidated view of events from both the modules. - Correct

    In case of APEs  we can only utilize free APEs only for SAM polling as we have node based licensing for SAM. - Makes sense to me now.

    As i said we are already having NPM and need to deploy SAM on the same server, any precaution before doing this activity so that existing NPM doesn't get affected?

    Use this -> Product Upgrade Advisor | SolarWinds Customer Portal and verify all pre-requisites for multi module installation, not sure how your NPM Server is sized at the moment, it should have enough capacity to hold SAM as well (hardware requirements).

  • vinay.by  wrote:

    No matter what you have if you need an additional poller you will have to purchase APE license.

    SAM's new node based licensing includes additional polling engines, similar to NAM.

  • Hi Suman,

    This is kinda weird but yes as sreenathmp​​​ has pointed out rightfully, i can now see what do you mean in saying so.

    **So if you want to balance out the load you can go for an additional poller which only holds SAM in it, i don't like this idea much but yup it works.

    1. Install SAM on your NPM Server, apply the SAM license.

    2. Then install SAM APE which does not include a separate license and add all your required nodes onto APE and apply templates accordingly. You could take this approach and all your pre-requisites will still be met as we discussed before.

    **** I was wrong in saying APE requires an additional license no matter what, for your requirement you could go with the above approach ************

    Below points have been picked up from the link

    With a node-based SAM license, you can add an Additional Polling Engine (APE) that does not require an extra license. By distributing polling away from the main polling engine, you can improve your monitoring capacity, boost the Orion Web Console performance, and help ensure high availability.

    To add the APE after applying the main SAM license:

    • Run the SolarWinds Orion Installer to set up the APE.
    • When prompted to select a Server Role, select the "Additional Polling Engine for Server & Application Monitor" option.

    Note the following details about adding a SAM APE that doesn't require an extra license:

    • If you use other Orion Platform products that offer "included" APEs, the exact text for the Server Role varies. For example, if Storage Resource Monitor (SRM) is also installed, the option appears as "Additional Polling engine for Server & Application Monitor, Storage Resource Monitor."
    • The APE only polls for SAM and basic Orion Platform data such as node status and volume. . For example, a SAM APE returns SAM data and basic node metrics, but doesn't return NPM node data such as interfaces.