If a PlateSpin Migrate Connector is available to your project, PlateSpin Transformation Manager provides automated discovery of source workloads as you import them into the project. You can also rediscover details for a workload if necessary.
Before you attempt an import with auto-discovery, you must configure your PlateSpin Discovery Environment:
PlateSpin Transformation Manager 1.1 SP1
Configure PlateSpin Transformation Manager and set up a project for the workloads you want to discover.
PlateSpin Migrate Connector 1.1
Deploy a Migrate Connector in the same network as the source workloads and assign it to the PTM Server or to your project on the server. For deployment information, see Deployment Requirements
in the PlateSpin Migrate Connector Quick Start.
PlateSpin Transformation Manager Appliance includes a Migrate Connector instance that is pre-configured to work with the PTM Server. If you have multiple projects, you can deploy a Migrate Connector instance for each project separately on your own SUSE Linux Enterprise Server 11 SP4 servers. See the PlateSpin Migrate Connector Quick Start.
NOTE:Ensure that the Migrate Connector is up and running before you attempt discovery or rediscovery or workloads.
Source Workloads
The Connector supports automated discovery of Windows and Linux source workloads for the following platforms:
Physical machines with x86 and x64 architectures
Virtual machines (VMs) with x86 and x64 architectures on VMware Cluster hosts
For cloud or other virtual workload types, you can use the Spreadsheet Import method to add workload details.
Ensure that the source workloads are up and running.
Ensure that the network connection is working between the PlateSpin Migrate Connector and the source workloads.
Credentials
Create a Credentials resource to use for source workload discovery. The Credentials resource is also used later for replication to the target VM on the host.
Network Connectivity and Access
For information about network connectivity and access information for automated discovery, see Workload Discovery.
The import and auto-discovery process performs the following actions:
The import creates a new Workload object unless it matches an existing workload.
The Workloads list displays the new workloads at the next page refresh, using the IP address as the workload name if the FQDN is not provided.
Auto-discovery begins for each new workload, using the provided Credentials resources to log in to the workload. Discovery status displays in the Workloads list and Workload dialog.
On successful workload discovery, the Workloads list or Workload dialog displays the newly discovered details at the next page refresh. The discovered host name replaces the IP address or FQDN as the workload name, as appropriate.
Discovery fails for any of the following conditions:
A Migrate Connector is not available.
The source workload is not supported for automated discovery.
The necessary ports are not open in the source workload’s operating system firewall.
The source workload Credentials resources are not provided.
The Credentials resource has an invalid value for the user name and password.
The source workload is not running at the time of discovery.
The provided IP address or FQDN is used by a non-computer device such as a UPS, printer, or network equipment. The workload is automatically removed from the database.
After you resolve Migrate Connector, network, or credentials issues, you can retry discovery for supported source workloads. See Section 20.6, Retrying Workload Discovery.
If you retry discovery for a workload that has failed discovery and the workload goes into a transformation workflow phase of Imported with a sub status of Workload Not Configured, it might be an indication that there is no valid Credential resource assigned to the workload. In order for the initial discovery to proceed, go to the Workload dialog and assign a Credential resource in the Workload panel. See Section 23.4.1, Associating Credentials and Workloads.