HP PART NUMBER: 461487-401A manual Automatic booting of the destination physical server fails

Page 57

Suggested action

Assign a different IP address to the network adaptor or reboot the server.

Supported storage controllers display Unknown on the Boot CD ISO

Cause

If the Insight Control server migration Boot CD ISO blocks the supported storage controllers for P2P or V2P migrations, the controller might appear as Unknown.

Suggested action

To reset NVRAM on the destination server:

1.Reboot the destination server.

2.Press F9 during reboot to enter ROM-Based Setup Utility (RBSU).

3.Open Advanced Options, and then select Restore Settings/Erase Boot Disk or Clear NVRAM.

4.Reboot the system by using the Insight Control server migration Boot CD ISO. The proper storage controller name is detected.

Automatic booting of the destination physical server fails

The destination server does not boot and no error message appears on the application station.

Suggested action

Reset the iLO network settings of the destination server and retry the automatic booting of the destination server.

3 Insight Control server migration might not detect virtual machines on mapped network drives

Cause

Insight Control server migration cannot locate virtual machines stored on mapped network drives if the service does not have access to the network shares.

Suggested action

Manually migrate these disks after a successful migration.

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.

Destination preparation

57

Image 57
Contents HP Insight Control Server Migration 7.2 User Guide Legal Notices Contents IV Troubleshooting and support Migrating the serversPostmigration tasks Contents CD ISO Contents Support and other resources Glossary Index Part I Overview and concepts Server migration introduction Installing and configuring server migration softwareOverview Related productsRight configuration Server migration concepts Migration checklistServer migration components Overview of migrating a serverMigration screen HP Insight Control server migration software tabsHP Insight Control server migration software tabs Part II Premigration tasks Preparing hardware for migration Verifying hardware and operating system supportVerifying system requirements for the application station Planning the migration Resizing Linux file systems Verifying licenses for software to be migrated Preparing software for migrationMigration security Disabling firewallsInstalling Service Pack for ProLiant Installing ProLiant Support PacksDisabling antivirus software Generating static or dynamic certificatesPreparing software for migration Part III Migration Verifying Windows source server requirements Preparing the source server and deploying the Source AgentVerifying Linux source server requirements Preparing a Microsoft Hyper-V source serverChoosing server migration Agents Removing guest toolsDeploying server migration Agents Deploying AgentsNavigate to server migration Source Agent Server migration agent install screen Navigate to server migration Source Agent Linux Source Agent screen Linux destination size requirement PrerequisitesPhysical destination servers Virtual machine hostsBooting the destination server ILO boot prerequisites Manually creating and booting a virtual destination serverPrerequisites for VMware ESX migration Page Minimum source server prerequisites for all migrations Migrating the serversIf you use a firewall, see Disabling firewalls Preparing for a Windows server migrationSource virtual machine prerequisites Preparing for a Linux server migrationSource physical server prerequisites SAN migrations in Windows Starting the migration wizard Launching server migration by using the Deploy menuIdentify the source server Launching server migration by using Quick LaunchQuick Launch Starting the migration wizard Installing Service Pack for ProLiant after migration Installing ProLiant Support Packs after migrationPostmigration tasks X2P postmigration tasks WindowsX2V postmigration tasks Windows Edit the boot.ini file to activate a graphical boot processX2V postmigration tasks Linux X2P postmigration tasks LinuxValidating the migration Viewing migration logsValidating Linux migrations Validating Windows migrationsPart IV Troubleshooting and support Troubleshooting User interfaceServer migration wizard hangs HP SIM Source server identification fails Source preparationLinux Source Agent window does not appear on Rhel 64-bit Migration Agent deployment failsPerform any one of the following on the source server Incorrect LUN size is detected in of the migration wizardUnable to boot Windows due to unsigned or corrupt drivers Destination preparationDestination server identification fails Migration might appear If expected volumes do not appear, try one of the following Automatic booting of the destination physical server fails Suggested action Drivers cannot be installed or injected onto a boot disk Large volumes fail with a server thread errorMigration process 2011/03/14 141934 The job failed Migration hangs if the source server is shut downReiserFS volumes are blocked for Linux migration Ntfs resize error message appearsMigration fails during the disk cloning phase SAN-connected destination server displays a blue screen Error occurs during data copy of Linux migrationHP Smart Array B320i controller name is not displayed Destination server boots with an invalid IP addressPostmigration Linux migration to servers with iSCSI storage fails to bootHidusb.sys Hidkbd.sys Mouhid.sys Suggested action Drives do not appear on the migrated operating system Guest OS ID guest name is not valid Server is unresponsive during PSP installation Multiboot kernel must be loaded before modules Suggested action Subscription service How to contact HPSupport and other resources Information to collect before contacting HPRelated information HP authorized resellersDocuments WebsitesRelated documentation Typographic conventionsTIP Documentation feedback Applying old server migration standalone licenses Basic hardware design of a three-node duster Premigration consideration steps for clustersPost migration considerations and steps Performing the migrationPost migration considerations and steps Page Glossary Index Page SPP Postmigration tasks Yellow bang ! appears on NIC adapter