2.3 Network Connectivity and Access Requirements

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 PTM server

  • Source workloads

  • Target VMware cluster hosts

  • PlateSpin Migrate servers

In addition, review the security guidelines in Section 2.4, Security Guidelines.

Your environment must meet the requirements described in this section for network connectivity and access. Refer to the ports map in Figure 2-1.

Figure 2-1 Ports Map for PlateSpin Migration Factory

2.3.1 Event Messaging

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.

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.

2.3.2 Workload Discovery

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

  • ICMP, incoming

  • SMB (TCP 445 or 139)

  • Microsoft .NET Framework 2.0 SP2, 3.5 SP1 or 4.0

  • Credentials with Domain Admin or built-in Administrator privileges

Linux workloads

  • ICMP, incoming

  • SSH (TCP 22, incoming)

Root-level access. For information on using an account other than root, see KB Article 7920711.

2.3.3 Target Host Discovery

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

  • ICMP, incoming

  • SMB (TCP 445 or 139, incoming)

VMware account with an Administrator role

2.3.4 Workload Migration

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

In addition, Transformation Manager requires that your migration environment meets the PlateSpin Migrate requirements for network communications. See Requirements for Migration in the PlateSpin Migrate 12.2.1 User Guide.