VMAN Licensing Question

Question

When I go into VMAN I found that some of our key servers are not being monitored. "not licensed". Looking at license manager I saw that we were licenced for 192 core and we have 224. The issue is it seems like VMAN randomly chose what servers/blades to monitor and which not. So I have critical infrastructure not monitor and test/dev stuff fully monitored. Is there a way to move things around so that VMAN is giving me full stats on my critical servers? We'll probably upgrade to allow for more cores in the spring when our license comes up. But want to get by for now. Thank you.

shuth · Accepted Answer

You can restrict the account that VMAN is using to communicate with your vCenter instance. Currently the account would have access to all of your hosts. If you block the account from having access to the non-critical servers in vCenter, VMAN won't see them and they won't draw down the licenses. This is also mentioned on the VMAN licensing page here: https://documentation.solarwinds.com/en/Success_Center/VMAN/Content/VMAN_Licensing_Model.htm 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.

VMAN Licensing Question

Top Replies