Free 30 Day Trial
Find the root-cause of your cloud, hybrid-cloudor on-prem performance issues
The VC Tab Page
Promptly detect issues with vCenter and swiftly diagnose the root-cause of these issues, using the vc tab page offered by the VM dashboard. This tab page lists one/all vCenter servers in the environment (depending upon the node chosen from the tree), and reports the number of ESX servers managed, the resource usage, and the overall health of each vCenter server.
This section discusses how the contents of this tab page change with the node chosen from the tree.
If the global Zones node is chosen from the tree, then the vc tab page will display the names of all vCenter servers included in all configured zones, and will report a default set of metrics per vCenter server, revealing the availability and resource usage of each server. Resource-intensive/unavailable vCenter servers in the target environment can thus be instantly identified.
Figure 1 : The VC tab page if the global Zones node is clicked
The default measure list that accompanies every vCenter listed in the vc tab page can be modified. For this purpose, follow the steps given below:
Click on the button at the right, top corner of the tab page. Figure 2 will appear.
In the event of a slowdown in the performance of a vCenter server, you can click on the name of that server in the vc tab page; this will lead you straight to the layer model of the vCenter server, which reveals the exact layer where the problem has originated. Click on the problem layer to view the problem test, and click on the problem test to view the measures (see Figure 3).
Alternatively, you can select the VMware vCenter sub-node under a zone node to see how all the vCenter servers in a zone are performing (see Figure 4).
If you want to check whether a particular vCenter server within a zone is available or not, and if available, how well its using the resources available to it, select the node representing a vCenter server under the VMware vCenter node in the tree structure (see Figure 5).