HP Insight Control - Manual (Page 50)

Server migration Source Agent deployment fails remotely from a Windows Server
2003 Application Station
Insight Control server migration 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.
•
A "Client for Microsoft Networks" client must be present in the network interface properties
on the source server and the CMS.
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.
Suggested action
The server migration Source Agent uses a 32–bit Java Runtime Environment. In 64–bit RHEL, the
Linux source migration agent window does not appear, although the agent is running. To enable
the display of the agent, you must install the X.Org X11 libXtst runtime library,
libXtst-1.0.99.2-3.el6.i686.rpm
.
Remote deployment of Linux Source Agent using nonroot credentials fails
Remote deployment of Linux Source Agent using nonroot credentials fails with the following error:
Failed to deploy server migration Source Agent. Error while installing
the server migration Source Agent on the given Server : exec tar -zxf
hpsmpagent.tar.gz -C /tmp on the remote host failed. The ports 51124,
51125 and 51126 required by the agent might be in use. : exec tar -zxf
hpsmpagent.tar.gz -C /tmp on the remote host failed. The ports 51124,
51125 and 51126 required by the agent might be in use.
Suggested action
Deploy the Linux Source Agent by using root privileges.
Manual installation of Linux Source Agent using sudo user privileges fails
Manual installation of Linux Source Agent using sudo user privileges fails.
Suggested action
Launch the server migration Linux Source Agent by using proper root user privileges.
Incorrect LUN size is detected in step 2 of the migration wizard
If the size of the source LUN detected during step 2 of the migration wizard is incorrect, you might
be attempting to initialize the LUN by using GPTs.
Cause
LUNs initialized with GPTs are not supported, even if they contain partitions with filesystems that
server migration supports. Those partitions appear as RAW partitions in the migration wizard, and
data might be incomplete after the migration.
50 Troubleshooting