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.
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.
Table 15-1 Common Reasons for a Status of Workload Discovery Failed
|
Reason |
Troubleshooting Tips |
|---|---|
|
Migration of a PlateSpin Server is not supported. |
|
|
Windows discovery was unable to authenticate to the source workload using the credentials provided. |
Retry the import with the appropriate credentials. |
|
Linux discovery was unable to authenticate to the source workload using the credentials provided. |
Retry the import with the appropriate credentials. |
|
Failed to create directory:/opt/PlateSpinDiscovery/ on host <IP address>. Error: mkdir: cannot create directory '/opt/PlateSpinDiscovery/': Read-only file system. |
PTM discovery creates a temporary directory, files, and service. Ensure that the username provided in the credentials has the administrator privileges necessary to perform these tasks. Ensure that the antivirus on the source workload is configured to permit discovery actions. See Section 1.7, Antivirus Setup for Discovery. |
|
Likely a duplicate of a workload currently being discovered. This workload might be deleted after discovery completes. |
PTM tries to identify and delete duplicate workloads if import is attempted in the same project. You can manually delete known duplicates. |
|
Migration of detected Linux OS type not supported. |
PTM discovery compares discovered Linux OS types to the PTM Operating Systems list. See |
|
Connection timeout of 15 seconds exceed while waiting for a response from the server. |
|
|
Error executing remote Linux command--:mkdir -p /opt/PlateSpinDiscovery/-- with error: Unable to open channel. |
SSH connection error for a Linux workload. |
|
The discovery failed to execute with an error: Error fetching remote file: [PlateSpinDiscovery_TIQD]result.xml; Error: SMB SessionError: STATUS_OBJECT_NAME_NOT_FOUND (The object name is not found.) |
SMB connection error for a Windows workload. |
|
An error occurred while connecting to the remote machine: ('Invalid response from server'...) |
|
|
Received unexpected status from the server: (3221225646) STATUS_PIPE_BUSY: 0xc00000ae |
|
Table 15-2 Common Reasons for a Status of Workload Not Found
|
Reason |
Troubleshooting Tips |
|---|---|
|
No response to a network ping. |
Verify network connectivity. |
|
Unable to detect OS type for <IP address>. Verify discovery ports are open. |
See Section 1.3, Requirements for Discovery and Section 1.6.2, Ports and Protocols: Workload Discovery. |
|
Possibly not a workload. |
Imports by IP address range might include network devices. Verify the IP address against your IP address assignments. |
|
Pre-import checks failed. |
Ensure that a PlateSpin Migrate Connector is installed in the source network. See |