This section provides information about setting up user authorization and authentication, configuring your network environment, and managing your product’s default settings and behavior.
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 the actual discovery procedures, see Discovering Source Workloads and Migration Targets
in your User Guide.
Table 2-4 Network Communication Prerequisites for Discovery Operations
System |
Prerequisites |
---|---|
All workloads |
Ping (ICMP echo request and response) support |
All Windows sources |
|
Windows Vista Windows 7; Windows Server 2008; Windows Server 2008 R2; Windows Server 2012 |
|
All Linux sources Citrix Xen Server |
|
VMware ESX/ESXi Servers VMware vCenter Servers |
|
The following table lists firewall requirements that systems in your environment must meet for problem-free operation during workload migration jobs.
Table 2-5 Network Communication Prerequisites for Workload Portability
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. |
All targets |
TCP 3725 |
Required for:File-based Server Sync / Image Sync
|
All Windows sources and targets |
NetBIOS 137 - 139 |
Required for NetBIOS communications. |
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 |
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. |
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: n your server’s PlateSpin Server Configuration tool, record the additional IP addresses assigned to that host:
From any Web browser, open the https://Your_PlateSpin_Server/platespinconfiguration/tool.
Locate the
server parameter, click , then add additional IP addresses, delimited by a a semicolon (;), for example:204.50.186.147;204.50.186.148
Source: As part of that specific migration job, record the additional IP addresses assigned to that workload. See Specifying Network Options.
Target: When you are attempting to discover a target, such as VMware ESX, specify the public (or external) IP address in the discovery parameters.