Symptom:
After I have added a vCenter Server connection under Administration, Configuration, the validation of the connection to the vCenter Server failed.
Solution:
The following procedures address the most common issues which can cause a connection failure:
To update the vCenter Server connection data:
The New or Edit vCenter Server dialog appears.
The connection data is updated.
If the connection to the vCenter Server cannot be established, continue with the next procedure.
To verify if the vCenter Server system is running and accessible:
nslookup <vCenter Server Name> ping <IP Address of vCenter Server>
If the vCenter Server is not in the DNS, add the vCenter Server to the Windows hosts file on the CA Server Automation manager system. Continue with Step 3.
If the vCenter Server is in the DNS, continue with Step 4.
ipaddress <vCenter Server Name>
Enter the correct IP address and vCenter Server name. For example:
192.168.50.50 myvCenter
If the vCenter Server credentials and connection data are correct and you can ping the vCenter Server, the connection can still fail. In this case, it is possible that the vCenter Server causes the problem. If the connection to the vCenter Server cannot be established, continue with the next procedure.
To verify, if the VMware Management Service on the vCenter Server system is running properly
The Services window opens.
CA Server Automation validates the vCenter Server connection.
If the connection to the vCenter Server fails, verify whether the data you gathered according to the requirements for this scenario is still valid.
Work with the vSphere administrator or VMware support to fix the vCenter Server connection problem.
Copyright © 2013 CA. All rights reserved. |
|