Submit a ticketCall us

Cloud Workloads: Meet Your New Hybrid IT Reality
Have you found yourself in that evolving, hybrid IT grey area and wondering if cloud workloads are now part of your purview? And if so, will monitoring cloud workloads require a new set of dedicated cloud monitoring tools? Your answers: yes, they should be, and no, they don’t.

Find out how SolarWinds® Server & Application Monitor (SAM) can help you monitor your cloud workloads side by side with your on-premises workloads. Register Now.

Home > Success Center > Virtualization Manager (VMAN) > Virtualizaton Manager (VMAN) Installation Guide > VMAN licensing information

VMAN licensing information

Updated: 9-13-2017 | VMAN Installation Guide

SolarWinds Virtualization Manager is licensed according to the number of CPU sockets per monitored host. When you monitor a virtual host, VMAN collects metrics and data for all children VMs. If you try to monitor more sockets or virtual machines than your license allows, you will not be able to add more data sources or apply VMAN upgrades.

VMAN includes two licenses for VMAN 6.2 through 8.0:

  • Primary license to be installed on the Orion Web Console for a stand-alone VMAN installation.
  • Secondary license to be installed on the VMAN appliance.

If you are integrating VMAN into an existing Orion Platform such as NPM, SAM, or NCM, you do not need to install the secondary license.

Virtualization Manager is licensed according to the number of processor sockets on your physical hardware. Physical hardware is ESX hosts for VMware or Windows Servers for Hyper-V.

VMAN is available in the following license sizes:

License Tier Sockets
VMS8 8
VMS16 16
VMS32 32
VMS64 64
VMS112 112
VMS192 192
VMS320 320
VMS480 480
VMS640 640
VMS800 800
VMS1120 1120
VMS1440 1440
VMS1680 1680
VMS1920 1920
VMS2400 2400
VMS3040 3040
VMS3840 3840
VMS4800 4800

Get your license key

You can obtain the primary and secondary license keys through the Customer Portal.

  1. Log in to the SolarWinds Customer Portal.
  2. Select Licenses > Manage Licenses.
  3. Locate an unregistered Virtualization Manager activation key. Make note of the license key.

Add primary license to stand-alone Orion Platform

The stand-alone deployment for VMAN includes installing a dedicated Orion Platform with an Orion Web Console. You receive this Orion Platform as the Virtual Infrastructure Monitor (VIM). You only need to add the primary VMAN license in a stand-alone deployment, not in an existing Orion Platform.

  1. Access the Orion Web Console of the stand-alone Orion Platform.
  2. Click Settings > All Settings, and click License Manager.
  3. In the License Manager, click Add/Upgrade License.
  4. Enter the Activation Key and Registration Information for the VMAN primary license, and click Activate.

Add a secondary license key for the VMAN appliance online

You will add the secondary license key on the VMAN appliance using the VMAN console. These instructions walk through adding the license online.

  1. Log in to the VMAN console.
  2. Click the Setup tab and select License Information.
  3. Click Activate License.
  4. Enter the secondary license key.
  5. In the Computer Name field, enter localhost.
  6. Enter the other required information, and click Send Activation Request.

Add a secondary license key for the VMAN appliance offline

You will add the secondary license key on the VMAN appliance using the VMAN console. These instructions walk through adding the license offline.

  1. Log in to the VMAN console.
  2. Click the Setup tab and select License Information.
  3. Click Unique Machine ID, copy the machine ID, and save it on a flash device.
  4. From a computer with Internet access, log in to the SolarWinds Customer Portal.
  5. Click Licenses > Manage Licenses, and locate an unregistered Virtualization Manager activation key.
  6. Click Manually Register License, and enter the required information.
  7. In the Computer Name field, enter localhost.
  8. In the Unique Machine ID field, paste the machine ID copied from VMAN.
  9. Click Generate License File, and download the license file.
  10. Transfer the license file to a computer with access to VMAN.
  11. Click Upload License File, select the license file, and click Open.

Exclude hosts from monitoring

If there are not enough SolarWinds Virtualization Manager licenses to cover every powered on virtual machine managed by a vCenter server, change the access permissions of the vCenter user account to limit what it can access.

Restricting the virtual machines accessible by the user account reduces the number of virtual machines or sockets SolarWinds Virtualization Manager can collect data from. This way you can control which virtual machines are being monitored.

You can control access permissions in the VMware client by assigning the No Access role to the vCenter account for the hosts and virtual machines you want to restrict.

 
Last modified

Tags

Classifications

Public