You have reached your license limit for monitoring items using the VMAN Orion or Appliance poller.

oldefortran · 2018-04-20T13:42:11+00:00

* I have a new install without a pre-existing VMAN Appliance to integrate or migrate * "Virtualization Manager Primary v6 - Up to 112 Sockets" License is assigned to the Primary Orion Server * I do NOT get the error "Error: The virtualization manager primary license could not be validated." * Updating to VMAN 8.2 did not…

oldefortran

I have a new install without a pre-existing VMAN Appliance to integrate or migrate
"Virtualization Manager Primary v6 - Up to 112 Sockets" License is assigned to the Primary Orion Server
I do NOT get the error "Error: The virtualization manager primary license could not be validated."
Updating to VMAN 8.2 did not resolve the error
Only 80 out of 112 potential sockets used
1 vCenter 6.0.0 server and 8 ESXi blades
Moving monitoring from APE to Primary made no differerence

This article does not seem to apply Error: The virtualization manager primary license could not be validated - SolarWinds Worldwide, LLC. Help and Support I recently updated the Primary and all of the APEs to the latest versions to verify this could not be the issue.

When I try to switch vCenter server from Basic to VMAN Orion monitoring, I get the error "You have reached your license limit for monitoring items using the VMAN Orion or Appliance poller."

One would think that the license "Virtualization Manager Primary" would be the necessary license from the description, but I imagine as confusing as all of the docs are surrounding the transition from VMAN Appliance to VMAN Orion that some additional mysterious license is required.

If some additional license is required, I would appreciate it if someone could point me to how to get a Trial for this license to see if that solves the problem.

Thanks.

Find more posts tagged with

license manager

vmanage

Accepted answers

All comments

alang

You say that you have "Only 80 out of 112 potential sockets used". Does that mean that you have configured to monitor all your ESX servers with VMAN individually already? When you add VCenter monitoring through VMAN it will also monitor/add all ESX servers that are managed by that VCenter. Could it be that this creates some kind of a double count situation for licensing? Maybe you could try to change all ESX servers to basic licensing first to free up all VMAN licenses and then start by configuring your VCenter for VMAN monitoring? This should then automatically add all VCenter managed ESX hosts as well.

oldefortran

Thanks for the suggestion. All of the blades were already set to Basic. On a whim, I deleted all of the blades and left just the vCenter server then was indeed able to switch to VMAN Orion.

I believe that my confusion stemmed from a (possibly older) article that said in order to get detailed network statistics from ESXi, it was also necessary to monitor the ESXi hosts with SNMP, which I had set up in troubleshooting not having detailed interface statistics. I will revisit now that I have vCenter switched to VMAN Orion monitoring.

oldefortran

Here is the article that confused me Requirements for monitoring ESXi and ESX Servers - SolarWinds Worldwide, LLC. Help and Support I found that while troubleshooting the lack of detailed Volume and Interface information. It says that SNMP is required with ESXi 6.0, but does not explain how you are supposed to configure it. So, I set up an SNMP discovery. I see now that it is for SAM rather than VMAN. I wish it was a lot clearer in general which products different SolarWinds articles actually apply to with documentation out there for so many different versions.

mshaw1

I had this exact problem when I converted from the VMAN appliance 8.1 to VMAN Orion 8.1.

This issue I had was that all of our ESX hosts had gotten switched to direct VMware polling. I followed the 'instructions' to convert which said to change the polling method to VMAN Orion prior to disabling integration with the appliance. I did that, and everything looked fine. A week later I disabled integration, and everything still looked fine. A couple days later I shut down the appliance..... and THAT's when the licence issue showed up.

I opened a ticket - the technician wasn't very knowledgeable about it. In the end, he suggested we use node management to bulk disable VMWare polling on the esx hosts... .and viola the licensing was OK again. That is, until I re-ran a discovery on the subnet, and each host was polling directly again. The trick there is to disable vmware polling in the discovery job as it will revert when the job is run.

oldefortran

Another tip from our VMware admin is that if you want to exclude specific hosts under a vCenter from VMAN Orion monitoring, set No Access for the solarwinds user for those hosts, that can be set at the folder level for example we have a Maintenance folder. That is to work around the fact that VMAN Orion polling seems to be set at the vCenter level and applies to all the hosts under that vCenter. There does not seem to be any way to switch specific hosts to Basic, and if you remove the hosts they will just be rediscovered.