HP Virtual Connect Enterprise Manager Software Auto booting destination physical server fails

Page 52

Some storage volumes on the destination server are not available for selection

Some storage volumes configured on the destination server might not be available for selection in Step 5 (SpecifyDestination Disks and Resize NTFS Partitions) of the migration wizard.

Suggested action

If expected volumes do not appear, perform one of the following:

Verify that the storage controller is supported by Insight Control server migration. Volumes configured on an unsupported storage controller cannot be selected for migration. For more information about supported controllers, see HP Insight Management Support Matrix available at: http://www.hp.com/go/insightmanagement/docs.

Run the Array Configuration Utility (if your storage controller is supported), and verify the status of the volumes on the Smart Array controller to be sure that the volumes are not in a failed state. Also, verify that all volumes on the controller are numbered sequentially beginning with logical drive 1, as required by the Insight Control server migration. If volumes are not numbered sequentially, clear the configuration and re-create the necessary volumes.

Static IP address cannot be assigned on the destination server while booting using the Boot CD ISO

Assigning a static IP address on the destination server might result in an error similar to the following:

The IP address xxx.xxx.xxx.xxx you have entered for this network adapter is already assigned to another adapter.

Cause

This might occur if the IP address is assigned to another network adapter on the destination server.

Suggested action

To resolve this issue, 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 supported storage controllers for P2P or V2P migrations are blocked by the Insight Control server migration Boot CD ISO, the controller might appear as Unknown.

Suggested action

To correct this issue, reset NVRAM on the destination server:

1.Reboot destination server.

2.To enter ROM-Based Setup Utility (RBSU) during reboot, press F9.

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

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

Auto booting 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.

52 Troubleshooting

Image 52
Contents HP Insight Control Server Migration 7.0 User Guide Legal Notices Contents Migrating the servers IV Troubleshooting and supportPost-migration tasks ISO Contents Contents Applying old server migration standalone licenses Support and other resourcesGlossary Index Part I Overview and concepts Installing and configuring server migration software Server migration introductionOverview Related productsProduct Description Migration checklist Server migration conceptsServer migration components Overview of migrating a serverHP Insight Control server migration software tabs Migration screenServer migration concepts Part II Pre-migration tasks Verifying hardware and operating system support Preparing hardware for migrationVerifying application station system requirements Planning the migration Resizing Linux file systems Preparing software for migration Verifying licenses for software to be migratedMigration Security Disabling firewallsDisabling antivirus software Installing ProLiant Support PacksGenerating static or dynamic certificates Part III Migration Preparing the source server and deploying the Source Agent Verifying Windows source server requirementsVerifying Linux source server requirements Preparing a Microsoft Hyper-V source serverUninstalling guest tools Choosing server migration AgentsDeploying 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 Prerequisites Linux destination size requirementPhysical destination servers 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 Installing ProLiant Support Packs after migration Post-migration tasksX2P post-migration tasks Windows X2V post-migration tasks WindowsEdit the boot.ini file to activate a graphical boot process X2P post-migration tasks LinuxX2V post-migration tasks Linux Viewing migration logsValidating the migration Validating Linux migrationsPost-migration tasks Part IV Troubleshooting and support Troubleshooting User interfaceSource preparation Server migration wizard hangsSource server identification fails Migration Agent deployment failsLinux Source Agent window does not appear on Rhel 64-bit Suggestion action Incorrect LUN size detected in of the migration wizard Destination preparation Destination server identification fails Suggested action CD ISO Auto booting destination physical server fails Manually migrate these disks after a successful migration Large volumes fail with server thread error Drivers cannot be installed or injected onto boot diskMigration process Java.lang.OutOfMemoryError Java heap space ReiserFS volumes are blocked for Linux migration Ntfs resize error messageMigration 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 Support and other resources How to contact HPInformation to collect before contacting HP Documentation feedback HP authorized resellersRelated 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