I just setup our two new ESX servers with VC. I am however having trouble setting up vmotion. I have included as much info about my setup as possible. AFAIK the VMFS labels need to be the same in order for vmotion to work. I can get the volumes to match up no problem and access them from both servers but vmotion isnt happening. Hopefully someone here can point me in the direction of what im doing wrong.
Do all servers (both ESX servers and the VC server) have full DNS name resolution?
I always start by ensuring that all three servers have entries in the 'hosts' file for each of the others.
Name resolution is often a cause of Vmotion failures.
Yes they all have DNS resolution, how does DNS work with vmotion? The vmotion network is completely private, crossover from one server to another.
Also when I try to add the same storage so both servers can access it, it trys to format it like its new instead of just adding it. Any ideas?
Name resolution is required between ESX servers for Vmotion.
What is the exact error message or behaviour you are getting? Please provide details on what is happening.
Paul is correct name resolution is important. I've also had to all the short hostnames to /etc/hosts file on ESX and on hosts file on VC server of all servers involved for it to work correctly in some cases.
I was having trouble mapping the same LUN to both ESX servers, I think the problem was the LVM.EnableResignature. I changed it 1 on VMWR02, looks like it worked. I will report back in a few
looks like I got vMotion working, was definitely the problem stated above. First time seeing it work, thats amazing.
I verified with a test server but when i had it ping the server it did go down for a bit, i thought it was seamless?
There is a small "hiccup" when networking comes over to the new physical switch port. Another cool test is to add a new disk to the vm, start a format and vmotion at the same time.