Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

vCenter Converter

Posted on 2010-09-21
8
Medium Priority
?
3,689 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
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 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
Migrating Your Company's PCs

To keep pace with competitors, businesses must keep employees productive, and that means providing them with the latest technology. This document provides the tips and tricks you need to help you migrate an outdated PC fleet to new desktops, laptops, and tablets.

 
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 24

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 24

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 24

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

Use Case: Protecting a Hybrid Cloud Infrastructure

Microsoft Azure is rapidly becoming the norm in dynamic IT environments. This document describes the challenges that organizations face when protecting data in a hybrid cloud IT environment and presents a use case to demonstrate how Acronis Backup protects all data.

Question has a verified solution.

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

Veeam Backup & Replication has added a new integration – Veeam Backup for Microsoft Office 365.  In this blog, we will discuss how you can benefit from Office 365 email backup with the Veeam’s new product and try to shed some light on the needs and …
When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed." When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
Teach the user how to delpoy the vCenter Server Appliance and how to configure its network settings Deploy OVF: Open VM console and configure networking:
Teach the user how to use create log bundles for vCenter Server or ESXi hosts Open vSphere Web Client: Generate vCenter Server and ESXi host log bundle:  Open vCenter Server Appliance Web Management interface and generate log bundle: Open vCenter Se…

722 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