HP Virtual Connect Enterprise Manager Software manual Suggested action

Page 50

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 a V2V migration

You have manually created the virtual machine on Microsoft Hyper-V for a P2V or a V2V migration and booted the virtual machine manually with the Insight Control server migration Virtual Machine Boot CD ISO, however, you are unable to configure an IP address on the virtual machine.

Suggested action

Perform the following:

Ensure that the virtual machine that you have manually created has a legacy network adapter.

Ensure that the legacy network adapter on the virtual machine is connected to the correct virtual network switch on the host.

Ensure that the Virtual network switch configuration on the Microsoft Hyper-V host is correct and the virtual switch is connected to a physical network adapter with external network connectivity.

Kernel panic occurs when booting a virtual machine to the Insight Control server migration Virtual Machine Boot CD ISO

Insight Control server migration requires that the destination virtual machine has at least 1024 MB of RAM to boot to the Insight Control server migration Virtual Machine Boot CD ISO.

Suggested action

To resolve this issue:

1.Power down the virtual machine.

2.Ensure that the virtual machine has at least 1024 MB of RAM.

3.Reboot to the Insight Control server migration Virtual Machine Boot CD ISO.

Mouse does not work on a virtual machine booted with the Insight Control server migration Virtual Machine Boot CD ISO

Cause

This issue occurs because virtual machine tools required for the mouse on certain virtualization layers are not available on the Insight Control server migration Virtual Machine Boot CD ISO.

Suggested action

Use the Tab and Enter/Return keys on the keyboard to navigate the user interface on the Insight Control server migration Virtual Machine Boot CD ISO.

Primary array controller does not have logical drives defined

Suggested action

Confirm that your array controller has at least one logical drive defined.

50 Troubleshooting

Image 50
Contents HP Insight Control Server Migration 7.0 User Guide Legal Notices Contents Post-migration tasks IV Troubleshooting and supportMigrating the servers ISO Contents Contents Glossary Index Support and other resourcesApplying old server migration standalone licenses Part I Overview and concepts Overview Installing and configuring server migration softwareServer migration introduction Related productsProduct Description Server migration components Migration checklistServer migration concepts Overview of migrating a serverHP Insight Control server migration software tabs Migration screenServer migration concepts Part II Pre-migration tasks Verifying application station system requirements Preparing hardware for migrationVerifying hardware and operating system support Planning the migration Resizing Linux file systems Migration Security Preparing software for migrationVerifying licenses for software to be migrated Disabling firewallsGenerating static or dynamic certificates Installing ProLiant Support PacksDisabling antivirus software Part III Migration Verifying Linux source server requirements Preparing the source server and deploying the Source AgentVerifying Windows source server requirements Preparing a Microsoft Hyper-V source serverDeploying server migration Agents Uninstalling guest toolsChoosing server migration Agents Deploying AgentsNavigate to server migration Source Agent Server migration agent install dialog Navigate to server migration Source Agent Linux Source Agent screen Physical destination servers PrerequisitesLinux destination size requirement Virtual machine hostsBooting the destination server Manually creating and booting a virtual destination server ILO boot prerequisitesPrerequisites for VMware ESX migration Page Migrating the servers Minimum source server prerequisites for all migrationsPreparing for a Windows server migration If you use a firewall, see Disabling firewallsPreparing for a Linux server migration SAN migrations in Windows Launching server migrations using the Deploy menu Starting the migration wizardVerify Source Physical server Launching server migrations using Quick Launch Quick LaunchAvailable operations X2P post-migration tasks Windows Installing ProLiant Support Packs after migrationPost-migration tasks X2V post-migration tasks WindowsEdit the boot.ini file to activate a graphical boot process X2P post-migration tasks LinuxValidating the migration X2V post-migration tasks LinuxViewing migration logs Validating Linux migrationsPost-migration tasks Part IV Troubleshooting and support Source preparation TroubleshootingUser interface Server migration wizard hangsSource server identification fails Migration Agent deployment failsLinux Source Agent window does not appear on Rhel 64-bit Suggestion actionDestination server identification fails Destination preparationIncorrect LUN size detected in of the migration wizard Suggested action CD ISO Auto booting destination physical server fails Manually migrate these disks after a successful migration Migration process Drivers cannot be installed or injected onto boot diskLarge volumes fail with server thread error Java.lang.OutOfMemoryError Java heap space Migration hangs if source server is shut down Ntfs resize error messageReiserFS volumes are blocked for Linux migration Migration fails during the disk cloning phase Error during data copy of Linux migration Destination server boots with an invalid IP address SAN-connected destination server displays blue screenPost-migration Perform one of the followingHidusb.sys Hidkbd.sys Mouhid.sys Suggested action Drives do not appear on the migrated operating system Destination virtual machine fail to boot after X2V migration Server is unresponsive during PSP installationReboot the server and then reinstall PSP manually Information to collect before contacting HP How to contact HPSupport and other resources Related information HP authorized resellersDocumentation feedback Typographic conventions Related documentationTIP Applying old server migration standalone licenses Pre-migration consideration steps for clusters Basic hardware design of a three-node dusterPerforming the migration Post migration considerations and stepsPost migration considerations and steps Glossary Index Index SIM Websites