HP Virtual Connect Enterprise Manager Software manual ILO boot prerequisites

Page 30

Booting a physical destination server automatically using the migration wizard

1.Identify the source server and select volumes to migrate in steps 1 and 2 in the server migration wizard.

2.In step 3 of the P2P or V2P migration wizard, select Auto Boot - Let server migration boot the destination server.

3.Enter the iLO IP address and iLO credentials.

4.Enter the static IP address, subnet mask, and default gateway (if needed). If there is a gateway in the network, enter it here to ensure connectivity. Optionally, you can also select the Duplex Settings.

5.Click Next.

6.To view the boot progress, click Launch iLO, and then log in to the iLO Remote Console.

iLO boot prerequisites

The following requirements must be met to use the boot from iLO feature:

The iLO user credentials provided must have Virtual Power and Reset and Virtual Media access applied.

The browser must be configured to support HTTP 1.1. To add this support:

1.On your web browser, open Internet Options, and then select the Advanced tab.

2.As appropriate, select Use HTTP 1.1 and Use HTTP 1.1 through proxy connections .

An iLO Advanced license must be applied to the destination server iLO.

At least 300MB of free space must exist on the application station for each iLO boot. This free space should exist on the partition on which Insight Control server migration is installed. This space is recovered once the migration is complete or the boot job times out.

After the destination server is booted to the proper Boot CD ISO, use the Boot CD application to configure the destination server and launch the destination agent. From the Boot CD application, click Help for instructions.

If the migration is not started within two hours of the server being powered up through iLO, the server migration will time-out and power down the destination server.

Manually creating and booting a virtual destination server

Prerequisites for manually creating and booting a destination virtual machine

This section lists the prerequisites for manually creating a virtual machine for different migrations.

To manually create and boot a destination virtual machine, you must create the virtual machine with the prerequisites specified, and then attach the Insight Control server migration Virtual Machine Boot CD ISO to the virtual machine.

The following sections list the special steps required to prepare virtual machines for boot to the Insight Control server migration Virtual Machine Boot CD ISO.

Prerequisites for booting a virtual machine in Microsoft Hyper-V

Ensure that the following parameters are met:

The virtual machine does not have more than three disks attached.

The virtual machine has at least 1024 MB of memory.

The network adapter is a legacy network adapter.

Connect the network adapter to a virtual network switch that is connected to an external network.

Attach the virtual disks that you create to an IDE controller.

30 Preparing the destination server and deploying the destination agent

Image 30
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