HP Virtual Connect Enterprise Manager Software manual Cd Iso

Page 51

You can confirm this by accessing the Configure Destination Server screen and then clicking Launch Array Configuration Utility or by rebooting to Option ROM Configuration for many controllers (ORCA).

Primary controller configured in the system does not have drives attached

Suggested action

Confirm that your hardware setup is correct and that the correct controller is set to primary in ROM-Based Setup Utility (RBSU).

Primary controller in system is not supported by this version of Insight Control server migration

When the destination server is manually booted using the boot CD ISO, the error message The

primary controller in your system is not supported by this version of Insight Control server migration Boot CD might appear on the destination server

console.

When the auto-boot option is chosen in step 3 of the migration wizard, the auto-boot of the destination server fails, the destination server is powered off, and the error The Storage

controller is not supported with this version of Insight Control server

migration might be displayed.

Suggested action

1.Verify the primary controller is supported for Insight Control server migration. For a complete list of supported controllers, see the HP Insight Management Support Matrix at the following website:

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

2.Verify the latest firmware is installed on the storage controller.

3.If the Insight Control server migration Boot CD ISO cannot detect the storage controller, you may need to reconfigure the storage controller environment variable.

a.Reboot the destination server to Rom-Based Setup Utility (RBSU) by pressing the F9 key during POST.

b.Select the Boot Controller Order option and verify the proper boot order for the storage controllers.

c.Press Esc to exit RBSU, and then press F10 to confirm the exit and to save your changes.

d.Reboot the destination server using the Insight Control server migration Boot CD ISO. When the destination server boots, the Insight Control server migration Boot CD ISO will detect the storage controller.

The destination server displays a blank screen when booting to server migration Boot

CD ISO

The destination server might display a blank screen when booting to the server migration Boot CD ISO if the server has more than 64 GB of RAM.

Suggest action

Perform the following:

1.At the boot menu, press Esc to enter text mode.

2.At the text mode boot prompt, typesos mem=4G.

3.Press Enter.

Destination preparation

51

Image 51
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 Related products Installing and configuring server migration softwareServer migration introduction OverviewProduct Description Overview of migrating a server Migration checklistServer migration concepts Server migration componentsMigration screen HP Insight Control server migration software tabsServer 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 Disabling firewalls Preparing software for migrationVerifying licenses for software to be migrated Migration SecurityInstalling ProLiant Support Packs Disabling antivirus softwareGenerating static or dynamic certificates Part III Migration Preparing a Microsoft Hyper-V source server Preparing the source server and deploying the Source AgentVerifying Windows source server requirements Verifying Linux source server requirementsDeploying Agents Uninstalling guest toolsChoosing server migration Agents Deploying server migration AgentsNavigate to server migration Source Agent Server migration agent install dialog Navigate to server migration Source Agent Linux Source Agent screen Virtual machine hosts PrerequisitesLinux destination size requirement Physical destination serversBooting 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 migrationPreparing for a Linux server migration SAN migrations in Windows Starting the migration wizard Launching server migrations using the Deploy menuVerify Source Physical server Quick Launch Launching server migrations using Quick LaunchAvailable operations X2V post-migration tasks Windows Installing ProLiant Support Packs after migrationPost-migration tasks X2P post-migration tasks WindowsX2P post-migration tasks Linux Edit the boot.ini file to activate a graphical boot processValidating Linux migrations X2V post-migration tasks LinuxViewing migration logs Validating the migrationPost-migration tasks Part IV Troubleshooting and support Server migration wizard hangs TroubleshootingUser interface Source preparationMigration Agent deployment fails Source server identification failsSuggestion action Linux Source Agent window does not appear on Rhel 64-bitDestination 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 SAN-connected destination server displays blue screen Destination server boots with an invalid IP addressPerform one of the following Post-migrationHidusb.sys Hidkbd.sys Mouhid.sys Suggested action Drives do not appear on the migrated operating system Server is unresponsive during PSP installation Destination virtual machine fail to boot after X2V migrationReboot 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 Related documentation Typographic conventionsTIP Applying old server migration standalone licenses Basic hardware design of a three-node duster Pre-migration consideration steps for clustersPost migration considerations and steps Performing the migrationPost migration considerations and steps Glossary Index Index SIM Websites