In SolarWinds, licensing is typically managed how?

In SolarWinds, licensing is typically managed how?

• A. Per-device only
• B. Per-node or per-probe, with licenses aligned to deployed modules (NPM, NTA, NetPath)
• C. Per-site license
• D. No licensing required

Answer: (B)

Licensing is tied to where you run the licensed modules, not just a flat count of devices. Each node or probe that hosts a licensed module consumes a license, and the license is assigned to the specific module deployed there. So if a node runs Network Performance Monitor and also has NetFlow Analysis or NetPath tests enabled, you need the corresponding licenses for NPM, NTA, and NetPath on that same node. This approach lets you scale by adding licenses for only the modules you actually use on each node or probe. In short, licensing is managed per-node or per-probe, with licenses allocated according to the modules deployed on each node. Per-device-only, per-site, or no licensing at all don’t accurately reflect how SolarWinds licenses are consumed.

Licensing is tied to where you run the licensed modules, not just a flat count of devices. Each node or probe that hosts a licensed module consumes a license, and the license is assigned to the specific module deployed there. So if a node runs Network Performance Monitor and also has NetFlow Analysis or NetPath tests enabled, you need the corresponding licenses for NPM, NTA, and NetPath on that same node. This approach lets you scale by adding licenses for only the modules you actually use on each node or probe. In short, licensing is managed per-node or per-probe, with licenses allocated according to the modules deployed on each node. Per-device-only, per-site, or no licensing at all don’t accurately reflect how SolarWinds licenses are consumed.