As some of you know I spend a lot of time on the VMTN forums, helping people out and learning from other experts. Today someone posted about Storage VMotion not working after a Service Console IP change. It reminded me of a problem I faced a while ago. The solution wasn’t obvious but fairly easy, because the problem was solved with a slightly different approach I wrote it down:
Disconnect the ESX host from VirtualCenter
Stop the VMware VirtualCenter Server service
Remove the /etc/opt/vmware/vpxa/vpxa.cfg file from the ESX host that’s affected
Run this script on the database:
———–
UPDATE [VCDB].[dbo].[VPX_HOST]
SET [IP_ADDRESS] = ‘w.x.y.z’
WHERE [DNS_NAME] = ‘name of esx host as it is listed in the table’
———–
“w.x.y.z” above is the new ip address
Start the VMware VirtualCenter Server service
Add the host to the cluster again
Thanks goes out to BigRolTide for pointing me out to this solution. (In my case updating the database wasn’t necessarry)
Update: http://kb.vmware.com/kb/1006768
vSphere 4.0 Quick Start Guide
[...] alerts us to a potential failure of Storage VMotion after changing the Service Console IP address. I personally haven’t seen this behavior, but [...]
[...] over at yellow-bricks.com has also seen this and has a similar resolution listed on his website (http://www.yellow-bricks.com/2008/09/29/storage-vmotion-fails-after-service-console-ip-change/), it also includes a change to the VC database, but we both did not need this step for it to [...]
[...] Problèmes de Storage VMotion après changement d’ip de Service Console sur ESX 3.5 [...]
[...] over at yellow-bricks.com has also seen this and has a similar resolution listed on his website (http://www.yellow-bricks.com/2008/09/29/storage-vmotion-fails-after-service-console-ip-change/), it also includes a change to the VC database, but we both did not need this step for it to [...]
That is great. Thanks for the solution that will be very helpful.