HP Virtual Connect Enterprise Manager Software manual Destination preparation

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

To resolve this issue, the Linux Source Agent must be deployed 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 with proper root user privileges.

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).

Cause

LUNs initialized with GPTs are not supported, even if they contain partitions with file-systems supported by server migration. Those partitions appear as RAW partitions in the migration wizard, and data might be incomplete after the migration.

Suggested action

You must deselect LUNs initialized with GPTs in step 2 of the migration wizard, and manually copy data on GPT disks after the migration.

Migrating a source server fails with the Microsoft Hyper-V role enabled

If you are trying to migrate a source server with the Microsoft Hyper-V role enabled, you must ensure certain preconditions are met.

Suggested action

Perform any one of the following on the source server:

•Turn off the hypervisor using the following command: bcdedit /set hypervisorlaunchtype off

After the migration, you can re-enable the hypervisor using the following command: bcdedit /set hypervisorlaunchtype auto

•Remove the Microsoft Hyper-V role from the source server.

Destination preparation

Destination server identification fails

The destination server identification fails in step 3 of the Wizard.

Suggested action

1.Verify that the network adapter on the destination server is configured with a valid IP address, subnet, and gateway.

Destination preparation 49