5.0

n
All destinations supported in Converter Standalone
Along with the higher security level and much larger address space, IPv6 brings about some compatibility
tasks that have not been resolved yet. For example, IPv4-only nodes cannot communicate directly with IPv6
nodes and need additional routing. This makes the end-to-end support of mixed IPv4 and IPv6 environments
precarious.
To reduce this complexity, Converter Standalone supports only pure IPv6 or IPv4 environments, where the
protection source, the protection destination, and the Converter Standalone server and agent must run the
same version of IP.
NOTE You cannot use IPv6 to customize the guest operating systems of virtual machines.
TCP/IP and UDP Port Requirements for Conversion
To enable conversion, the Converter Standalone server and client must be able to send data to each other, to
remote physical machines, and to vCenter Server. Also, the source and destination hosts must receive data
from each other. Designated ports are reserved for this communication.
If any of these ports is blocked, the corresponding conversion task fails.
Ports Used When Converting a Powered-On Physical Machine Running Windows
Table 2-8 contains a list of the ports that must be open during the conversion of physical machine sources
running Windows.
Table 2-8. Ports Required During Windows P2V
Communication Paths
Communication
Ports Notes
Converter Standalone server to
powered-on source machine
TCP - 445, 139,
9089
UDP - 137, 138
If the source computer uses NetBIOS, port 445 is not required. If
NetBIOS is not being used, ports 137, 138, and 139 are not
required. When in doubt, make sure that none of the ports are
blocked.
NOTE Unless you have installed Converter Standalone server or
agent on the source computer, the account used for
authentication to the source computer must have a password,
network file sharing must be enabled on the source computer,
and Simple File Sharing must not be used.
Converter Standalone server to
vCenter Server
TCP - 443 Required only if the conversion destination is a vCenter Server.
Converter Standalone client to
vCenter Server
TCP - 443 Required only if the Converter Standalone server and client
components are on different machines.
Powered-on source machine to
ESX/ESXi
TCP - 443, 902 If the conversion destination is vCenter Server, only port 902 is
required.
Ports Used When Converting a Powered-On Physical Machine Running Linux
Table 2-9 contains a list of the ports that must be open during the conversion of physical machine sources
running Linux.
Table 2-9. Ports Required During Linux P2V
Communication Paths TCP Ports Notes
Converter Standalone server to
powered-on source machine
22 Used to establish an SSH connection between the Converter
Standalone server and the source machine.
Converter Standalone client to Converter
Standalone server
443 Required only if the Converter Standalone server and client
components are on different machines.
VMware vCenter Converter Standalone User's Guide
26 VMware, Inc.