Cross vCenter migration fails with "A general system error occurred: No such host is known"

[gbeke]

Hi,

I'm attempting to migrate a vm between two vCenter Servers with different SSO domains. I've found a script here that I'm sure will do what I want. However, when running the script I get the following error "A general system error occurred: No such host is known". There are a firewall between these two vCenter environments and I have so far opened port 8000 between the two hosts that I want to use as migration hosts. Is there any other ports that need to be opened between the two environments to be able to perform a cross vcenter migration? Do the vCenter servers need to talk to each other?

I use a Windows server that has access to both vCenters to run the migration script. My assumption was that as long as it can connect to both vCenters is should work. Is here any further requirements for cross vCenter vmotion to work?

Any help and insight will be greatly appreciated. If you need more details let me know.

Regards,

GB

[daphnissov]

There are *lots* of other requirements for cross-vCenter vMotion to work. Read this KB.

[gbeke]

Thanks for the reply.

Yes, I've read that KB and, as far as I can tell, we are good on everything in the article. But the article doesn't say anything about what ports need to be open between the different components. Google doesn't reveal any information regarding communication when doing cross vCenter vmotion. What components need to talk to each other at which ports? Since this information is hard to come by I started with opening port 8000 for vMotion between the hosts. I've not opened any ports between the two vCenters. Do they need to talk to each other? What about the Windows server I'm running the script on? Is it enough that the server is able to connect to the two vCenters?

Regards,

GB