HP Virtual Connect Enterprise Manager Software manual Migration process

Page 54

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.

To resolve the gateway issue, ensure that you enter the gateway IP address in the migration wizard when identifying the destination server.

Warning message is not displayed for unsupported servers when started using the Insight Control server migration ProLiant Boot CD

HP Insight Control server migration does not support HP ProLiant Server versions G1 to G4. When the unsupported server is started using the Insight Control server migration ProLiant Boot CD, the migration wizard does not display the message that the server is not supported.

Suggested action

Before starting the migration, verify if the server is supported. For a list of supported servers, see HP Insight Management Support Matrix available at: http://www.hp.com/go/insightmanagement/ docs.

Microsoft Windows 2008 OS migration results in a blue screen error on destination server configured with NC551m FCoE card

After a successful X2P migration with primary controller configured as NC551m FCoE Card, the migration results in a blue screen error.

Suggested action

Before you migrate, you must disable the AMD virtualization or Intel Hyper-Threading in the BIOS of the destination server.

Migration process

Drivers cannot be installed or injected onto boot disk

This error is reported if Insight Control fails to install or inject device drivers. In most cases, additional information is reported on the destination server.

Suggested action

Possible causes and solutions for this error include:

The boot partition was not migrated to the boot volume on the destination server. Verify that the boot partition is selected for migration and placed on the boot volume of the destination server.

The network connection failed during driver installation.

The destination server failed or was powered down during driver installation.

The storage controller where the boot partition was placed is not supported. For a complete list of supported controllers, see the HP Insight Management Support Matrix at:

http://www.hp.com/go/insightmanagement/docs

The iSCSI initiator failed to mount the disk. To resolve this issue, reinstall the iSCSI initiator on the application station.

Large volumes fail with server thread error

Migrating extremely large volumes (larger than 1 TB) can result in a failed migration with the following message:

54 Troubleshooting

Image 54
Contents HP Insight Control Server Migration 7.0 User Guide Legal Notices Contents IV Troubleshooting and support Migrating the serversPost-migration tasks ISO Contents Contents Support and other resources Applying old server migration standalone licensesGlossary Index 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 Preparing hardware for migration Verifying hardware and operating system supportVerifying application station system requirements Planning the migration Resizing Linux file systems Migration Security Preparing software for migrationVerifying licenses for software to be migrated Disabling firewallsInstalling ProLiant Support Packs Disabling antivirus softwareGenerating static or dynamic certificates 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 preparation Incorrect LUN size detected in of the migration wizardDestination server identification fails Suggested action CD ISO Auto booting destination physical server fails Manually migrate these disks after a successful migration Drivers cannot be installed or injected onto boot disk Large volumes fail with server thread errorMigration process Java.lang.OutOfMemoryError Java heap space Ntfs resize error message ReiserFS volumes are blocked for Linux migrationMigration hangs if source server is shut down 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 How to contact HP Support and other resourcesInformation to collect before contacting HP HP authorized resellers Documentation feedbackRelated information 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