2.2 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 PTM 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 Section 2.3, Security Guidelines.

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

2.2.1 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 message queues are inactive unless you open the required STOMP port to allow registration for the service and a PlateSpin Migrate Connector subscribes as a listener. A Connector instance subscribes automatically to the event service for its PTM Server and to the event services for its assigned PlateSpin Migrate servers.

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

2.2.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 How to use a non-root account with PlateSpin Migrate, Protect, or Forge (KB Article 7920711).

2.2.3 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 2-3.

Table 2-3 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

  • HTTPS (TCP 443)

  • 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 2019.2 User Guide.

2.2.4 Requirements for Automated Workload Migration

PlateSpin Transformation Manager uses REST APIs to communicate automation requests to the Platespin Migrate servers in your PlateSpin Migration Factory environment.

Table 2-4 provides the ports to open in the firewall and on each of the Migrate servers.

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

Before the migration begins, ensure that you have properly prepared your environment:

  • In PTM, provide valid credentials for the Migration Server resources.

  • On each PlateSpin Migrate server, open the port required for event messaging. See Event Messaging.

  • Ensure that your Migrate server setup meets the PlateSpin Migrate requirements for network communications between the Migrate server and the target platform. See Requirements for Migration in the PlateSpin Migrate 2019.2 User Guide: