HP Insight Control Software for Linux - Manual (Page 54)

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
make sure that certain preconditions are met.
Suggested action
Perform any one of the following on the source server:
•
Turn off the hypervisor by using the following command:
bcdedit /set hypervisorlaunchtype off
After the migration, you can re-enable the hypervisor by using the following command:
bcdedit /set hypervisorlaunchtype auto
•
Remove the Microsoft Hyper-V role from the source server.
Windows Migration agent successful, even when deployment fails
Auto deployment of the windows migration agent fails during one of the following scenarios:
•
Another instance of the agent is running on the source server.
•
Incorrect user credentials.
Cause
The SMP wizard ignores the error message displayed, as it connects to the previous instance of
the Windows migration agent running on the source server.
Suggested Action :
Stop any running instance of the Windows source agent and deploy a new agent from the SMP
wizard.
Destination preparation
Destination server identification fails
The destination server identification fails in step 3 of the wizard.
Suggested action
Try the following:
1.
Verify that the network adapter on the destination server is configured with a valid IP address,
subnet, and gateway.
2. Verify that the destination server is booted from the Insight Control server migration Boot CD
ISO and ready for migration.
3. Verify that the destination server can be reached from the application station and source
server. Communication on network ports 51125 and 51126 must be enabled by any firewall
between the CMS, the source server, and the destination server.
4. Verify that another Insight Control application is not already communicating with the destination
server.
IP address configuration fails on a manually booted virtual machine in Microsoft
Hyper-V for a P2V or V2V migration
You have manually created the virtual machine on Microsoft Hyper-V for a P2V or V2V migration
and booted the virtual machine manually with the Insight Control server migration Virtual Machine
Boot CD ISO. However, you cannot configure an IP address on the virtual machine.
54 Troubleshooting