Migration Agent deployment fails

3.Verify that the source server can be reached from the application station. Communication on network ports 51125 and 51126 must be enabled by any firewall between the application station and the source server.

4.Verify that the agent status messages do not indicate that the source server is locked to another server.

The migration Agent might fail deployment for several reasons, including:

•Incorrect password

•Reserved ports

•Insufficient disk space

•Network issues

•Special characters in the source password, like colon (:), quotation marks (“), or backslash

(\)

•A situation in which source server is inside a VPN and the CMS is outside the VPN

•Missing 32–bit libraries on a 64–bit Linux source server

Suggested action

Try the following:

•Verify that you have provided valid credentials with administrative rights for the source server for the migration agent deployment.

•If the source server has Insight Control server migration installed, make sure that you have disabled the server migration application and web services from the Windows Services console.

•Other processes might use the ports reserved for the migration agent (51124 through 51126). Make sure that these ports are free on the source server. A reboot might resolve port locks by other processes. If the issue persists, you must identify and disable other processes that are using the ports.

•Sufficient disk space exists for the agent to be copied and installed properly.

•Make sure that the networks on both the source and the server migration application station work properly.

•Make sure that the source server password does not contain special characters like colon (:), quotation marks (“), or backslash (\).

•Make sure the source server and CMS are both either inside the same VPN or outside the VPN.

•Make sure that 32-bit glibc is installed on 64-bit Linux source servers before Source Agent deployment.

•In the source server, clear the Don’t allow exceptions check box under the General tab of the Windows Firewall section.

•In the source server, select the File and Printer Sharing check box under the Exceptions tab of the Windows Firewall section.

Linux Source Agent window does not appear on RHEL 64–bit

On 64–bit RHEL, the Linux Source Agent window does not appear after deployment, although it is not impeding the migration.

52 Troubleshooting