Splitting Licenses for 2 Seperate Node

Hi All,

Apologies if this has been answered in a separate post. I have tried to look through the forum for an answer.

I have an SL2000 license for a single NPM Installation which was purchased several years ago. We are using 30% of the licences.

Since then we have acquired another site and have asked our account manager, to no avail, to split the license for 2000 node across 2 NPMs located on each site. This is not possible.

Has anyone else been successful in achieving this?

If it is not possible to split the licenses, is there any other way to do this with a central management server that connects to both nodes? The central management server I guess will also need to be available from either site if there was a WAN failure.

Any help is appreciated.

Find more posts tagged with

npm

Licenses

Accepted answers

All comments

mharvey

SolarWinds does not split the licenses. If you truly need a polling server at each location, you'd have to purchase a second SL2000. Just know that this would also require it's own database and will have it's own website. If you are wanting both connecting to a single database, you'd have to upgrade to a SLX license and purchase an additional polling engine in order to get two polling servers talking to the same database. That would be about the only way to do it. If you need a central web server accessible outside of either location, then you'd also need to pick up an Additional Webserver license. There's no way to have two SL2000, or primary polling servers talk to the same database, and no way to break the website out of the main polling server. This is what the additional polling engine and web server are for. The problem there is, as mentioned above, you'd have to upgrade the license from a SL2000 to a SLX.

HolyGuacamole

What is the concern in monitoring the new site from the current NPM install? Do you have redundant WAN links? How many elements (nodes, interfaces) do you have at the new site? How much bandwidth can you afford to use for monitoring?

ed.gumuskaya

Thanks mharvey, HolyGuacamole,

The business has stated that in an event of a DR scenario, visibility of the DR nodes needs to be operational from within the first hour.

Our comms circuits between sites is redundant with 10GB throughput, so no issues. Just need something operational in the event of a DR scenario, I can't really have the NPM hosted in the DR site either due to the requirement of having the hosted site accessible at all times.

HolyGuacamole

Sounds like what you need is an Orion Failover Engine - i.e., a standby server in the DR site. Have you discussed this option already?

mharvey

I would have to agree with HolyGuacamole here. The FailOver engine would be the better option to have for what you are looking for. Have everything monitored by one server and a failover sever configured as a standby.