There are latency issues with storage collection from an HP EVA device.
The SMI-S provider is also receiving polls from multiple Storage Manager Proxy Agents.
The SMI-S provider for HP EVA should not have more than one Storage Manager Proxy Agent polling. The SMI-S provider for HP EVA is single threaded and this will cause latency issues with polling if found in multiple agents.
Why use the synchronous tags?
Most common reason to use this is to fix issues with storage array performance collection.
Most common array type you will see this happen on in HP EVA.
To set a module to synchronously open threads:
Stop the agent process and open the mod.sys.smis.Smis.xml configuration file found in
\Storage Manager Agent\systemic\mod.sys.smis.Smis_1.0\ in a text editor.
Add the tag <synchronous>true</synchronous> between
<mod.sys.smis.Smis> and </mod.sys.smis.Smis>.
*Note: if you are using the Storage Manager server to monitor the arrays, the path to the file would be
\Storage Manager Server\agent\systemic\mod.sys.smis.Smis_1.0\
Start the agent.
What does this do:
This will allow only 1 thread to connect to the provider at a time for each agent that is used. Data gathering is broken down into 3 threads - asset, storage, performance. If we had 5 arrays in an environment on 1 Command View, thats 15 threads potentially connected to the provider at the same time.
Setting <synchronous> flag to true limits the thread connection from 15 down to 1 on the provider.
This may throttle things down too much, so a second thing that can be done is add more agents in the environment.
Each provider ip creates a unique set for which a connection is allowed to the provider.
The SMI-S provider is a single threaded application.