IBM Support

VCenter Sensor performance

Troubleshooting


Problem

VCenter sensor performance.

Cause

This has been identified as a product defect under APAR IV49853

Resolving The Problem


What exactly does the sensor discover? Ensure it is really a performance issue with the sensor. In order to do so, try to rule out the environment being at fault. Perhaps timing is normal for this sensor.

Lets take a look at he sensor and what it actually does:

The VCenter sensor discovers not only distributed virtual switches in an ESX server, but also for each ESX server, the sensor discovers information about networking, storage, etc. Therefore the sensor is not only providing a list of VMs, but rather Virtual Machines are
discovered with configuration information like the number of CPUs and memory assigned etc.

When looking at the logs it usually should show that each VM is discovered in around 3 secs (idle system).

It has been found that in most environments, most of the time is consumed on direct VC server communication though. In other words the sensor is sending requests for data to the VC server and waits for response. Delay in responds usually is due to the VC server being busy (heavy usage ) and therefore can't respond adequately. There is currently an efix (APAR IV49853) available which reduces the number of requests to the ESX servers. Please contact support to request this enhancement if needed. This eFix IV49853 will be generally available with TADDM 7.2.1 fixpack 06 and TADDM 7.2.2 fixpack 01

If a time-out occurs, check the The VCenter time-out parameter in collation.properties. It is very possible with the size and load of some VCenters, the sensor could run longer than the allowed specified time. In this case, the following time-out value in the $COLLATION_HOME/dist/etc/collation.properties file should be increased.

com.collation.discover.agent.VirtualCenterSensor.timeout=

Starting with TADDM 721 fixpack 05 it is also possible to reduce the amount of data discovered for each VM, reducing it to only the fqdn and the naming rule. If performance is an issue, this options could also be considered by the customer in order to improve performance concerns.

[{"Product":{"code":"SSPLFC","label":"Tivoli Application Dependency Discovery Manager"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"--","Platform":[{"code":"PF033","label":"Windows"}],"Version":"7.2.1;7.2.2","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
17 June 2018

UID

swg21652977