adding host to vCenter times out
Hi,
I had to move a local vSphere host to a colo facility, while leaving vCenter here at the office. I mapped an external IP address on port 443 to it and can see it with the vSphere client in stand-alone mode. Trying to add it to vCenter doesn't work; it seems to see it but then times out when trying to complete the importing. I'm assuming I need to open more ports for vCenter's use, or is this something else I'm missing?
vSphere 5.5.0 and vCenter 5.5.0 build 2001466
Thanks!
--Ben
I had to move a local vSphere host to a colo facility, while leaving vCenter here at the office. I mapped an external IP address on port 443 to it and can see it with the vSphere client in stand-alone mode. Trying to add it to vCenter doesn't work; it seems to see it but then times out when trying to complete the importing. I'm assuming I need to open more ports for vCenter's use, or is this something else I'm missing?
vSphere 5.5.0 and vCenter 5.5.0 build 2001466
Thanks!
--Ben
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Good lord. The 2nd link goes on forever on ports. It would be easier to try to set up a VPN between the two locations. Will try to open the ports in the 1st link and see if that works; otherwise will pursue a VPN solution.
Thanks!
--Ben
Thanks!
--Ben
is there a reason, vCenter Server is not on the same site as the hosts?
ASKER
Hi Andrew,
I had placed vCenter on a physical box so I could do maintenance more easily on the hosts. And that box also was the backup target for my other physical workstations.
I also came to the same question--why not put it on one of the hosts? So I ran a copy of the vCenter converter standalone (vsn 5.5.1 build 1682692) on it into a VMWare workstation instance I have to make sure it works. It had issues--the vCenter server would not come up. Thought I might have messed something up so I removed and reinstalled vCenter. That went great...until I tried to log in. No combination I could think of worked, much less what I gave it as the original password. Sigh.
So I blew that VM off and started over. Re-converted the physical box, but this time un-joined the domain and rejoined it with a different machine name. And chose an older machine architecture (vsn 9). That just came up a few seconds ago.
Trying to log in to that I get the same thing: vSphere Client could not connect to "vcenter" An unknown connection error occurred. (The request failed because of a connection failure. ( Unable to connect to the remote server).
Finally dawned on me this may not have been a vCenter issue--and sure enough it wasn't. It was a dns issue. The ptr record was not updated, pointing to an IP that isn't here now. It's in the colo facility.
Updating the ptr record in the AD server got me to the right machine, and it logged in just fine. Now I can shut this down, take it over there, and load the VM onto that network.
Thanks, Andrew. You've been quite helpful, as always!
--Ben
I had placed vCenter on a physical box so I could do maintenance more easily on the hosts. And that box also was the backup target for my other physical workstations.
I also came to the same question--why not put it on one of the hosts? So I ran a copy of the vCenter converter standalone (vsn 5.5.1 build 1682692) on it into a VMWare workstation instance I have to make sure it works. It had issues--the vCenter server would not come up. Thought I might have messed something up so I removed and reinstalled vCenter. That went great...until I tried to log in. No combination I could think of worked, much less what I gave it as the original password. Sigh.
So I blew that VM off and started over. Re-converted the physical box, but this time un-joined the domain and rejoined it with a different machine name. And chose an older machine architecture (vsn 9). That just came up a few seconds ago.
Trying to log in to that I get the same thing: vSphere Client could not connect to "vcenter" An unknown connection error occurred. (The request failed because of a connection failure. ( Unable to connect to the remote server).
Finally dawned on me this may not have been a vCenter issue--and sure enough it wasn't. It was a dns issue. The ptr record was not updated, pointing to an IP that isn't here now. It's in the colo facility.
Updating the ptr record in the AD server got me to the right machine, and it logged in just fine. Now I can shut this down, take it over there, and load the VM onto that network.
Thanks, Andrew. You've been quite helpful, as always!
--Ben
ASKER
Dang. Well, I thought this would be easy. After verifying the Workstation version of vCenter came up fine, I uploaded it to the host, gave it a static IP address, had it join the domain, verified the IP addresses were correct, and neither vCenter Server nor the vCenter Management Webservices will start.
The Application event log isn't terribly helpful. I see the following error entries in it for the vCenter Server:
and earlier in the System event log I found:
?
--Ben
The Application event log isn't terribly helpful. I see the following error entries in it for the vCenter Server:
The description for Even ID 1000 from source VMware VirtualCenter Server cnanot be found. Either the component that raises this event is not installed on your local compute or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: Error getting configuration info from the database the message resource is present but the message is not found in the string/message table.
and earlier in the System event log I found:
The VMware VirtualCenter Server service terminated with service-specific error. The system cannot find the file specified.
?
--Ben
ASKER
Didn't think that would be the issue since I can use the client directly to pull them up. Will check out the links. Thanks!
--Ben