Quantcast
Channel: VMware Communities: Message List
Viewing all articles
Browse latest Browse all 246801

Trouble Relocating existing ESX4 Host to a Moved vCenter 4 implementation.

$
0
0

Scenario - I needed to move my vCenter 4 to a different server.

  1. I backed up and moved the SQL DB (2005 Exp) to the new server. This went smoothly
  2. I installed same version of vCenter (4.0.0) on the new server and connected the moved DB - fine
  3. went to each ESX4 host (4) and edited the ...vpxa.cfg file to reflect the new vCenter and restarted Services -fine
  4. installed vSphere client on new vCenter and connected to the new vCenter.
    1. All of my Host from previous installation were visible (But Greyed out/ Disconnected as expected)
  5. I proceeded to connect them and got SSL warnings which I ignored (as instructed by several posts that I read)
  6. I confirmed the decision to pull administration from the previous vCenter.
    1. 3 out of 4 of the Host connected without issue (these were all on the same subnet as the vCenter [Not sure if this matters]The
  7. The fourth Host (on a different subnet) goes through the same prompts as the others and then states "in Progress" for a loooong time and then errors out with a "General system error occurred internal error vmodl.fault.hostcommunication"

 

Troubleshooting so far -

 

  1. First I tried removing the Host and added it again (this didn't help)
  2. I saw some post that stated it might be Name resolution issue -
    • I updated My Windows DNS to contain all Host Names and IPs (Forward and Reverse lookup). I am able to do nslookup and Ping this Host
    • I have checked the resolv.conf and it contains reference to my nameservers and domain.
    • host file is empty (just like the 3 Host that Connected) so I left it alone
  3. I restarted the vpxa and vmaware mgt. agents based on some posts iread (sorry of this i not the correct name, I'm still fairly new to VMware)
    • This did not work so I followed the direction in another post that said I could reinstall them but that did not work either.
  4. I turned off all VMs on this host and put the host in Maintenace mode then I rebooted this host - no luck

 

I'm at the end of my Rope. I just wanted to move the vCenter temporarily so that I could use the original server for vCenter 5.1 but I couldn't becuse it had 32 bit OS on it.

 

Any Help will be Greatly apreciated

Thanks in advance

 




Viewing all articles
Browse latest Browse all 246801

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>