HP Insight Control - Manual (Page 48)

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. computer.
4. Verify that the agent status messages do not indicate that the source server is locked to another
Migration Agent deployment fails
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 (:) or quotes (“)
•
The source server is inside a VPN and the CMS is outside the VPN
•
Missing 32-bit libraries on 64-bit Linux source server
Suggestion 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, ensure that you have disabled
the server migration application and web services from the Windows services console.
•
The ports reserved for the migration agent (51124 through 51126) might be used by other
processes. Ensure that these ports are free on the source server. A reboot might resolve port
locks by other processes. If the issue persists, then other processes using the ports must be
identified and disabled.
•
There must be sufficient disk space for agent to be copied and installed properly.
•
The networks on both the source and the Insight Control station must be working properly.
•
If you are launching server migration Source Agent to a virtual machine, verify the virtual
machine console with virtual machine host management console does not have any errors.
•
Ensure that the source server password does not contain special characters like colon (:) or
quotes (“).
•
Ensure the source server and CMS are both either inside the same VPN or are both outside
the VPN.
•
Ensure that the 32-bit glibc is installed on 64-bit Linux source servers prior to Source Agent
deployment.
Server migration Source Agent deployment fails remotely from a Windows Server
2003 Application Station
Insight Control uses a file share on the source server to deploy the agent from the application
station.
Suggested action
For the file share to operate, verify that the following conditions have been met:
•
The Server or Workstation service must be started on the source server.
•
The Server or Workstation service must be started on the application station.
48 Troubleshooting