| Measures reported by vCldVimConnTest
This test reports the numerical statistics of the user connections that were successful and the connections that were disconnected in this vCenter. Additionally, using this test, you can identify the number of times the VC Listener Service was started in this vCenter and the number of times the vCenter was reconnected to the vCloud Director cell.
The measures made by this test are as follows:
| Measurement |
Description |
Measurement Unit |
Interpretation |
| Connected_count |
Indicates the number of user connections that were successful in this vCenter. |
Number |
These measures are a good indicator for identifying the load on the vCenter.
Compare the values of these measures across the Virtual Centers to identify which Virtual Center is more resource-intensive. |
| Disconnected_count |
Indicates the number of user connections that were disconnected in this vCenter. |
Number |
| Start_count |
Indicates the number of times the VC listener service was started in this vCenter. |
Number |
vCloud Director has a service called VC Listener (inventory service) through which it monitors and aggregates changes of vCenter Server entities. Each VC Listener service is capable of listening for changes from one or more vCenter Server instances. However there is only one VC Listener Service that is listening to a given vCenter Server. Whenever the connection is broken between the vCenter and the vCloud Director cell, you would need to restart the VC Listener service. |
| Ui_vim_reconnect_count |
Indicates the number of times this vCenter was reconnected through the UI to the vCloud Director cell. |
Number |
Ideally, the value of this measure should be low. Frequently reconnecting the Virtual Center results in the disconnection of the vApp sessions from the vCloud Director cell thus leading to a poor Cloud computing experience for the users. |
|