HP Insight Control - Manual (Page 149)

1. Verify the identifier entered. If the name is entered for a source server that is in a domain, be sure that
the Fully Qualified Domain Name (FQDN) is entered.
2. Verify that the migration agent has been installed on the identified source server. For more information
about running the migration agent, see the
Insight Control server migration User Guide.
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 computer.
Migration agent deployment fails
The migration agent might fail deployment because of the following:
•
The user name or password is incorrect. Verify that you have provided valid credentials with
administrative rights for the source physical machine for the migration agent deployment.
•
The Insight Control application station server is not a valid source physical machine for migrations.
•
The ports reserved for the migration agent (51124 through 51126) might be used by other processes.
These ports are reserved during installation and a reboot usually resolves the issue. 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.
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. For
the file share to operate, the following conditions must be 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 added to the network interface properties on the source
server.
•
A "Client for Microsoft Networks" client must be added to the network interface properties on the
application station.
Remote deployment of Linux source agent using non-root credentials fails
Remote deployment of Linux source agent using non-root credentials fails with the error:
Failed to Deploy SMP Agent. Error while installing the SMP 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.
To resolve this issue, the Linux source agent must be deployed using root privileges.
Linux server migration Source Agent deployment from a Windows 2003 Application
station to a SLES 10 SP2 source server fails
If the Linux server migration Source Agent deployment from a Windows 2003 Application station to a SLES
10 SP2 source server fails, try deploying the Agent from the Migration Wizard again.
Incorrect LUN size detected in step 2 of the Migration Wizard
If the size of the source Logical Unit Number (LUN) detected during step 2 of the Migration Wizard is
incorrect, then you may be attempting to initialize the LUN with GUID partition tables (GPT). LUNs initialized
with GPTs are not supported, even if they contain partitions with file-systems supported by SMP. Those
Source preparation 149