1.6 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 platforms (for automated migrations)

  • PlateSpin Migrate servers

In addition, review the security guidelines in Security Guidelines in the PTM 2 Administrator Guide.

Your environment must meet the following requirements for network connectivity and access:

1.6.1 Ports and Protocols: Event Messaging

PlateSpin Transformation Manager publishes workload workflow state change messages for its registered listeners. Each PlateSpin Migrate Connector instance registers with its assigned Transformation Manager server or project and listens for events and performs the appropriate actions.

In a PlateSpin Migration Factory environment, each PlateSpin Migrate server publishes workload migration state change messages for its registered listeners. Each PlateSpin Migrate Connector instance registers with its assigned Migrate servers, then listens for messages and delivers them to the appropriate project and workload in Transformation Manager.

PlateSpin uses RabbitMQ for event messaging. The event message queues are pre-configured on the PTM Server and the PlateSpin Migrate Server. The messaging function starts, stops, and restarts automatically with its parent PTM service or Migrate service, respectively.

NOTE:Do not modify the PlateSpin default settings for the RabbitMQ message service.

The PlateSpin Migrate message queues are inactive unless you open the required STOMP port on the Migrate Server. When the port is open, one or more PlateSpin Migrate Connector instances can register as subscribers for the event messages.

Table 1-4 shows the protocol and port required for event messaging between the PTM Server and the PlateSpin Migrate Connector instances registered with PTM Server. Each Migrate Connector instance also handles event messages for its assigned PlateSpin Migrate servers.

NOTE:The messages reflect events and state changes and do not contain sensitive information.

Table 1-4 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 PTM Appliance VM.

Open this port on all other Connector host servers, the PlateSpin Migrate servers configured for the project, and the firewalls between them.

1.6.2 Ports and Protocols: 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 1-5.

Table 1-5 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.

1.6.3 Ports and Protocols: Target Platform Resource Discovery

Platform resource discovery requires that you enable incoming ping (ICMP echo reply and ICMPv4-In echo request) traffic for platforms and firewalls. PlateSpin supports only IPv4. For information about required software, network, and port settings for platform discovery, see Table 1-6.

Table 1-6 Target Platform 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

Physical hosts

  • ICMP, incoming

  • SMB (TCP 445 or 139, incoming)

Local Administrator or Domain credentials

Microsoft Azure host

  • ICMP, incoming

  • SMB (TCP 445 or 139, incoming)

  • Azure account and subscription ID

  • PlateSpin Replication Environment enabled for the subscriber account

  • PlateSpin Migrate server in Azure

See Prerequisites for Migration to Microsoft Azure in the PlateSpin Migrate 2018.11 User Guide.

1.6.4 Ports and Protocols: Workload Migration

Table 1-7 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 1-7 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

Ensure that you open the port required for event messaging on the PlateSpin Transformation Manager server and on each PlateSpin Migrate server. See Ports and Protocols: Event Messaging.

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 2018.11 User Guide.