Updated March 10, 2017
The data collection stopped for all devices assigned to the STM server.
The Collector service is under huge load, causing "data collection issues". First, we need to take care of the Collector. At the moment there is more than 300 VMs assigned for collection. Standalone agent with 4GB of RAM assigned can poll 300 VM's. Collector service has 2GB of RAM assigned by default. Collector shares memory between modules, that means collection is not possible from any other device.
services.msc stop "Solarwinds Storage Manager Collector" service. We need to edit config to add bit more memory:
SolarWinds.Storage.Collector.ini(by default in
c:\Program Files\SolarWinds\Storage Manager Server\webapps\ROOT\bin\).
See if devices restart collection (may take around 1 - 2h for SMI-S based devices). Once you see devices collecting, you can re-assign some of the ESX hosts to the agent. Make sure not to exceed 300 VM's per agent. To check current figures go to Reports, Quick Reports, check report "Vmware to Agent assignment".