Solved

vCenter Converter

Posted on 2010-09-21
8
3,454 Views
Last Modified: 2012-05-10
Having trouble with a P2V. Have been able to do it before, but now it is not working. When trying to connect to the physical box, get the message "Unable to contact the specified host '10.200.101.30'. The host might not be available on the network, there might be a network configuration problem, or the management services on this host are not responding."

I can ping the physical box. I've verified the correct ports are open on our firewall.

Any ideas? Thanks!
0
Comment
Question by:Flash3313
  • 3
  • 3
  • 2
8 Comments
 
LVL 2

Expert Comment

by:frevere
ID: 33728806
1) are you launching P2V converter from the VC?
2) are you using the local administrator account of the computer (although I've never had an issue using the domain admin)
0
 

Author Comment

by:Flash3313
ID: 33728823
Yes, doing it from the vCenter using my domain admin account
0
 
LVL 2

Expert Comment

by:frevere
ID: 33728883
Well, looking at your question closer, this is more of a networking problem.  Do you have the sshClient and sshServer open on the ESX firewall?  And by chance, have you restarted the hostd?
0
Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

 
LVL 2

Expert Comment

by:frevere
ID: 33728948
I believe you do not have all the ports open on the firewall.  Here is a document from VMWare listing everything out for you:

http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1010056&sliceId=1&docTypeID=DT_KB_1_1&dialogID=112086104&stateId=0 0 117036741
0
 
LVL 22

Expert Comment

by:Luciano Patrão
ID: 33729011
Hi

The P2V recommendation is to use local admin on the physical server. This on cold migration, but also online migration.

Disable any firewall on the physical server side.

You can ping the physical server from your vCenter? Can you ping from the physical server your vCenter IP??

Use only IPs, not dns names.

Jail
0
 
LVL 22

Expert Comment

by:Luciano Patrão
ID: 33729036
Hi

Forget to add, try to use the vConverter Standalone in the physical server, and migrate from there to the ESX host(not vCenter)

Jail
0
 

Accepted Solution

by:
Flash3313 earned 0 total points
ID: 33766243
Putting a colon and then 443 after the computer name of the physical machine I was importing seemed to work. Not sure why this worked or why it had to be done.
0
 
LVL 22

Expert Comment

by:Luciano Patrão
ID: 33766637
Hi

To connect the physical machine you use 10.200.101.30:443 this what you add in the vConverter settings?

Never seen this, and this has no reason to work like this.

vConverter only use this port if converter target is a vCenter. But it connects to this port, never need to add the IP and port.

Or do you not explain all the infrastructure, or this is very strange issue.

But glade that you complete the work

Jail
0

Featured Post

Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Exchange server is not supported in any cloud-hosted platform (other than Azure with Azure Premium Storage).
Last article we focus in how to VMware: How to create and use VMs TAGs – Part 1 so before follow this article and perform the next tasks, you should read the first article how to create the TAG before using them in Veeam Backup Jobs.
Teach the user how to use configure the vCenter Server storage filters Open vSphere Web Client:  Navigate to vCenter Server Advanced Settings: Add the four vCenter Server storage filters: Review the advanced settings: Modify the values of the four v…
Teach the user how to install and configure the vCenter Orchestrator virtual appliance Open vSphere Web Client: Deploy vCenter Orchestrator virtual appliance OVA file: Verify vCenter Orchestrator virtual appliance boots successfully: Connect to the …

777 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question