I've having a problem that I've done many times before, but now that it's not working I don't know if I'm having a brain dump and missing something obvious or something changed in my environment that's causing it and I need feedback as to what direction I should look towards.
Here is my environment:
I have one vCenter 5.1 server in my TRUST (i.e. - internal private network) along with 2 clusters that I'm managing. One is a non-EVC enabled cluster that's running in the same TRUST network that my vCenter is on (i.e. - 10.x.x.x). The other cluster is an EVC enabled one that's located in my DMZ (i.e. - 192.x.x.x) and both environments are configured via a firewall for communication.
All ESXi host servers are running v5.1 U1 (1157734). I have 2 hosts in DMZ cluster and 4 hosts in TRUST cluster. I have 2 datastores for DMZ cluster that are shared and 10 datastores for TRUST cluster that are shared. I can vMotion and vStorage Motion successfully within each of the clusters with no problems. I'm also using the vSphere Web Client to manage all of this.
I recently moved a VM from TRUST network to DMZ successfully by doing a cold migration for various reasons such as both clusters are on separate networks, non-shared datastores between them, EVC vs. non-EVC, etc. Now, I'm trying to cold migrate the same VM back to the TRUST network and I'm getting the error "Cannot connect to host".
Is my only option here to remove VM from inventory, Import into TRUST cluster? Maybe that's what I did the first time around, just can't recall...again...possible brain dump here :smileylaugh:
**Update** - I just ran another test by moving another VM from TRUST to DMZ and it was successful. It's only when I try to move it back from DMZ to TRUST that it fails. I'm not getting much love from the community on this one, so looks like I'm just going to contact VMware support for this.
