IPAM licensing swap between separate environments with different license levels

Hello all,

I'm in a situation where I have two Solarwinds environments, existing has IPAM IPX (and corresponding licensing for NPM/NTA/NCM etc) in Production, and a new "to be Prod" environment with IP1000-level IPAM licensing-to-cover.

(Yes We're building the second environment to replace the first environment.)

The network manager would like to start using the IPAM on the replacement system ahead of us "officially" cutting over the entire environment, and it's pretty clear if we do that, the IP address count will quickly exceed the IP1000 limits.

Question is... Can I swap the licensing between these two environments for IPAM only, leaving the remaining NPM/NTA/NCM licensing in both deployments as-is, and succeed in using IPAM with the IPX license level on the newer environment, while putting the IP1000 on the other?

(Obviously, I realize the leftover IPs on the first environment will exceed the count.)

I've tried searching around, reviewed IPAM license docs, and I couldn't find a straight answer to this question.

First post, please forgive me.

Thanks.

Byron

Find more posts tagged with

Accepted answers

All comments

tallyrich

A call to support would allow them to walk you through this, but if you want to tackle it on your own you should be able to open your license manager and disconnect the license from the existing server and then connect it to your new environment. It entails online connectivity so that it can talk back to SolarWinds corporate, but should be pretty easy to accomplish.

frak

Additionally, a fresh install will work for a month in 'demo' mode before it stops working. If you can fit in the migration within a month it can be a valid strategy. You can also get that demo extended, though that can be a bit of a challenge to get an okay from SW on. Definitely worth talking to support first, though as @Richard suggests.

byronfelts

Thanks Richard. I'm familiar with performing the license swaps between environments, but typically it's retiring one license for the replacement of same strength. I'm mildly concerned about the mix of limits in the module licensing components overall, is all.

I'll log a case with support.

Thanks again!

Byron

byronfelts

I've definitely exceeded my demo limits with this particular deployment, due to the lapse in time as far as moving onto the new one. Won't get into details of that.

Logging a case with support at this point.

Thanks

Byron