Errors when browsing VMware servers
The following table describes the problems that may occur when you click on a server under VMware servers.
Table: Errors browsing VMware servers
Error message or cause | Explanation and recommended action |
|---|
No VMs or other objects were discovered for the VMware server. | If the server was added recently, the VM discovery process for that server may not have completed yet. Recommended action: Wait for the discovery process to finish. The discovery of VMs and other objects in the vCenter or ESXi server begins when server credentials are added or updated through the web UI or an API. However, the server's VMs and other objects might not appear in the UI immediately. They appear after the discovery process for the VMware server completes. Discovery also occurs at set intervals according to the VMWARE_AUTODISCOVERY_INTERVAL option. (The default interval is every 8 hours.) To perform autodiscovery of VMware server objects at a different frequency: See Change the autodiscovery frequency. See VMWARE_AUTODISCOVERY_INTERVAL option for NetBackup servers. VMs or other objects of the VMware server may not be accessible for the added VMware server credentials. Recommended action: From the option menu on the right of the row, select . Review the VMware server credentials and correct them as needed.
|
