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

Destination server does not boot even though the automatic booting option was
chosen during X2P migrations
During X2P migrations, if the automatic booting option was chosen during the Identify Destination
Server step of the migration wizard and if the destination server does not boot, either of the following
scenarios might occur:
•
Automatic booting fails with the following error in the migration wizard: Could not get
timely response from remote management. Please try again or use
manual boot option.
•
Automatic booting continues for more than 40 minutes without any error messages displayed
in the migration wizard.
Suggested action
Reset the iLO network settings on the destination server, and then retry the automatic booting or
manually boot the destination server. For more information on iLO, see the iLO user guide.
Insight Control server migration stops responding during automatic booting of
Microsoft Hyper-V virtual machine
Insight Control server migration might stop responding during automatic booting of a Microsoft
Hyper-V virtual machine for an X2V migration.
Suggested action
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
automatically booted for an X2P migration
The application station can fail to connect to the destination server when the server is automatically
booted for a P2P or V2P migration, even though the destination server boots and the agent starts.
Cause
This issue might happen if the destination server has multiple NICs connected to different networks
and the IP address is configured to a NIC that is not on the same network as the application station
and the source server. Make sure that the duplex settings on the destination server match the duplex
settings on the network switch in your environment. You can also use the autonegotiate option at
either end to ensure proper communication between the destination server and the network switch.
The application station might also fail to connect if you have a gateway in your network and the
gateway value is not specified in the migration wizard when you are identifying the destination
server.
Suggested action
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.
To resolve the gateway issue, make sure that you enter the gateway IP address in the migration
wizard when you are identifying the destination server.
58 Troubleshooting