Ensure that the network connections are working:
Between the PlateSpin Migrate Connector and the source workloads
Between the PlateSpin Migrate Connector and the PlateSpin Migrate servers
Between the source network and target network
PlateSpin Migrate Connector requires network connectivity to the following resources, based on its assignment to the PlateSpin Transformation Manager server or to a specific project:
Its assigned PlateSpin Transformation Manager server
Source workloads
Target VMware cluster hosts
PlateSpin Migrate servers
Your environment must meet the following requirements for network connectivity and access:
PlateSpin Migrate provides an event messaging service based on RabbitMQ for use in the PlateSpin Migration Factory environment. Each PlateSpin Migrate server can publish workload migration state change messages to PlateSpin Migrate Connector instances that subscribe to the service on behalf of PlateSpin Transformation Manager projects. For information about how communications work for PlateSpin Migration Factory, see Section 1.3, PlateSpin Migration Factory Environment.
Table 2-1 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-1 Event Messaging Requirements for Network Protocols and Ports
Traffic |
Network Protocol and Port |
Other Requirements |
---|---|---|
Event Messaging |
61613 (Stomp, allow 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. Open this port on all other Connector host servers, the PlateSpin Migrate servers configured for the project, and the firewalls between them. |
Workload discovery in PlateSpin Transformation Manager requires that you enable incoming ping (ICMP echo reply and ICMPv4-In echo request) traffic for source workloads and firewalls. PlateSpin supports only IPv4. For information about required software, network, and port settings for workload discovery, see Table 2-2.
Table 2-2 Workload Discovery Requirements for Network Access and Communications
Discovery Target |
Network Protocols and Ports |
Other Requirements |
---|---|---|
Windows workloads |
|
|
Linux workloads |
|
Root-level access. For information on using an account other than root, see KB Article 7920711. |
Host discovery requires that you enable incoming ping (ICMP echo reply and ICMPv4-In echo request) traffic for target VMware hosts and firewalls. PlateSpin supports only IPv4. For information about required software, network, and port settings for host discovery, see Table 2-3.
Table 2-3 Host Discovery Requirements for Network Access and Communications
Discovery Target |
Network Protocols and Ports |
Other Requirements |
---|---|---|
VMware Cluster hosts |
|
VMware account with an Administrator role |
Table 2-4 provides the ports to open in the firewall and on each of the Migrate servers in order for PlateSpin Transformation Manager to use the Migrate REST APIs for automated migration. In addition, the Migration Server resource for Migrate server must provide a valid Credentials resource for the Migrate Administrator user.
Table 2-4 REST API Requirements for Network Access and Communications
REST API Traffic |
Network Protocol and Port |
Access |
---|---|---|
HTTPS (secure) |
Port 443, TCP, incoming and outgoing |
Administrator login credentials for the Migrate server |
HTTP (non-secure) |
Port 80, TCP, incoming and outgoing |
Administrator login credentials for the Migrate server |
PlateSpin Transformation Manager requires that your migration environment meets the PlateSpin Migrate requirements for network communications. See Requirements for Migration
in the PlateSpin Migrate12.2.1 Beta User Guide.
For secure HTTPS connections between PlateSpin Migrate Connector and PlateSpin Transformation Manager, the Jetty SSL settings on the PlateSpin Transformation Manager Appliance VM are configured with the latest recommended security settings.
To run automated discovery on Windows workloads, you might need to exclude certain services, files, and folders from antivirus protection.
Service: Exclude the PTM Discovery Service (PTMDiscoverySvc.exe) from antivirus protection.
This service uses the PsExec utility to run remote commands on the target MachineDiscoveryReader.dll.
Files and Folders: Exclude the PlateSpinDiscovery directory, including any subdirectories and files, from antivirus protection.
During each discovery attempt, all binaries and services files the PTM Discovery Service creates and uses are located under the PlateSpinDiscovery directory in the first Windows share it discovers, such as Admin$.
Ports: The antivirus software must not restrict any of the ports needed for discovery. For port information, see Section 2.3.2, Workload Discovery.