Ensure that your network environment meets the following requirements for access, discovery, and migration.
The following table lists software, network, and firewall requirements that systems in your environment must meet for the discovery and inventory process. For information about discovery procedures, see Section IV, Discovering and Preparing Workloads and Targets.
Table 2-17 Network Communication Prerequisites for Discovery Operations
System |
Prerequisites |
---|---|
All workloads |
Ping (ICMP echo request and response) support |
All Windows sources and Hyper-V hosts |
|
All Linux sources Citrix XenServer Linux Xen or KVM servers |
|
VMware ESX/ESXi Servers |
|
VMware vCenter Servers |
The user with access must be assigned the appropriate roles and permissions. Refer to the pertinent release of VMware documentation for more information. |
The following table lists firewall requirements that systems in your environment must meet for problem-free operation during workload migration jobs.
Table 2-18 Network Communication Prerequisites for Workload Migration
System |
Open Port (Default) |
Remarks |
---|---|---|
PlateSpin Server hosts |
Either TCP 80 or TCP 443 TCP |
|
All source workloads except those in image deployment jobs. |
TCP 3725 |
Required for targets to initiate communication during file-level data transfer, except for I2X jobs, during which this port needs to be open on the migration target only. For Server Sync jobs, this port is required for both sources and targets. The port number is configurable by setting the FileTransferPort parameter in the PlateSpin Configuration settings for the Migrate server. When the PlateSpin Migrate server is installed on-premise, by default the target workload will connect to the source workload on port 3725 (TCP), although this setting can be reversed (source workload connects to target workload) by changing the SourceListensForConnection parameter setting from True to False. When the PlateSpin Migrate server is deployed in the cloud from the provided cloud-based PlateSpin Migrate server image, the default direction of this connection is reversed automatically: the on-premise source workload will connect to the target workload in the cloud on port 3725 (TCP). |
All targets |
TCP 3725 |
Required for:
|
All Windows sources and targets |
NetBIOS 137 - 139 |
Required for NetBIOS communications. |
All Windows Server Cluster workloads. See Clusters. |
Ensure that the PlateSpin Server can resolve DNS forward lookup and reverse lookup for the IP addresses of the Windows Server Cluster and its cluster nodes. You can update the DNS server or update the local hosts file (%systemroot%\system32\drivers\etc\hosts) on the PlateSpin Server. |
|
All sources |
SMB (TCP 139, 445 and UDP 137, 138) |
Required for communication and file-level data transfer during offline migration. |
All Linux sources Citrix Xen Server Linux Xen or KVM servers |
TCP 22 |
Required for communication during offline migration. |
PlateSpin Server hosts; All Windows sources |
TCP 135/445 |
For DCOM/RPC communication between PlateSpin Server and a source for taking control of and rebooting the workload through WMI. NOTE:WMI (RPC/DCOM) can use TCP ports 135 and 445 as well as random/dynamically assigned ports above 1024. |
Table 2-19 shows the protocol and port required for event messaging in a PlateSpin Migration Factory environment. These messages reflect events and state changes and do not contain sensitive information.
Table 2-19 Event Messaging Requirements for Network Protocols and Ports
Traffic |
Network Protocol and Port |
Other Requirements |
---|---|---|
Event Messaging |
Stomp, port 61613, TCP incoming (not secure) |
This port is open by default on the PlateSpin Transformation Manager Appliance, which includes a pre-installed instance of PlateSpin Migrate Connector. You must manually open the port on the following:
|
In some cases, a source, a target, or PlateSpin Migrate itself, might be located in an internal (private) network behind a network address translator (NAT) device, unable to communicate with its counterpart during migration.
PlateSpin Migrate enables you to address this issue, depending on which of the following hosts is located behind the NAT device:
PlateSpin Server: In your server’s PlateSpin Server Configuration tool, record the additional IP addresses assigned to that host:
Log in as Administrator to the PlateSpin Migrate Web Interface, then open the PlateSpin Server Configuration page at:
https://Your_PlateSpin_Server/PlateSpinConfiguration/
Locate the AlternateServerAddresses server parameter, click Edit, then add additional IP addresses, delimited by a a semicolon (;), for example:
10.50.186.147;10.50.186.148
Source: As part of that specific migration job, record the additional IP addresses assigned to that workload. See Network Identification (Network Connections).
Target: When you are attempting to discover a target, such as VMware ESX, specify the public (or external) IP address in the discovery parameters.