HP Insight Control - Manual (Page 65)

• Automatic booting fails with the error Could not get timely response from remote
management. Please try again or use manual boot option.
in the migration
wizard.
• Automatic booting continues for over 40 minutes without any error messages displayed in
the migration wizard.
Suggested action
Reset the iLO on the destination server, and then reboot the destination server or manually boot
the destination server. For more information on iLO, see the iLO user guide.
Destination server fails to boot while loading initrd.img
The destination server fails to boot when connecting the ProLiant Boot CD ISO through Insight
Control remote management Virtual Media or by choosing the Auto Boot option in the migration
wizard.
Suggested action
To resolve this issue, access the Insight Control server migration ProLiant Boot CD ISO file in
the \root directory and restart the boot.
Insight Control server migration stops responding during auto-booting of Microsoft
Hyper-V virtual machine
Insight Control server migration might stop responding during auto-booting of a Microsoft
Hyper-V virtual machine for an X2V migration.
Suggested action
To resolve this, ensure the following:
• File-sharing is enabled on the application station and the Microsoft Hyper-V host.
• The Server or Workstation service is started on the application station and the Microsoft
Hyper-V host.
• A "Client for Microsoft Networks" client is added to the network interface properties on the
application station and on the Microsoft Hyper-V host.
Application station fails to connect to the destination server when the server is
auto-booted for a P2P or V2P migration
The application station can fail to connect to the destination server when the server is auto-booted
for a P2P or V2P migration, even though the destination server boots up and the agent starts up.
Cause
This might happen if the destination server has multiple NICs connected to different networks
and the IP address gets configured to a NIC which is not on the same network as the application
station.
Suggested action
To resolve this issue, manually boot the destination server, and then manually assign the IP
address to the NIC that is on the same network as the application station.
Destination preparation 65