HP PART NUMBER: 461487-401A manual Destination server boots with an invalid IP address

Page 64

Out of memory error occurs on the application station during migration

The Insight Control application station requires a minimum of 1024 MB of free memory for Insight Control migrations.

Suggested action

Free memory or add memory to the application station, and then restart the migration.

Destination server boots with an invalid IP address

After a P2P migration, the destination server might boot with an invalid IP address (for example, 169.x.x.x), instead of using the IP address that was configured through the migration wizard.

Cause

This issue occurs if the destination IP address configuration fails or Dynamic Host Configuration Protocol (DHCP) is not enabled in the network. Whenever a NIC is added to the server, by default the NIC is assigned an IP address using the DHCP configuration. If no DHCP server is configured on the network, the server will boot with an invalid IP address.

Suggested action

After the P2P migration is complete, manually configure the IP address on the destination server. For specific instructions on performing this task, see the help files for the specific OS documentation.

Windows server migration Source Agent or PINT remote deployment is intermittent and deployment fails with a General failure occurred error

When you remotely deploy the Windows server migration Source Agent or PINT from the Insight Control server migration application station or from Systems Insight Manager, server migration Source Agent deployment fails with the error General failure occurred. In addition, the

<Insight Control server migration Installation

Folder>\log\AgentLogs\hp\log\<source IP>\timestamp_smp_log.txt file displays

the following exception:

Received Target Exception: UnknownException : SoapSession::SoapSession : unknown exception! No install was run, due to connection error

Suggested action

Manually install the server migration Source Agent or PINT on the source server.

Unable to detect HP FlexFabric 10Gb 2-port 554FLR-SFP+ Adapter configured as iSCSI disk in step 5 of migration wizard

When you start a P2P migration of any of the OS from any server to DL385p Gen8 with HP FlexFabric 10Gb 2-port 554FLR-SFP+ Adapter configured as iSCSI disk and then start an auto boot in step 3, you will observe that the adapter is not detected in step 5 of migration wizard and the following error message is displayed:

"HP Insight Control could not find any disks on destination server"

Suggested action

You must disable IOMMU in RBSU (System Config > Processor Settings > AMD–Vi).

HP Smart Array B320i controller name is not displayed

When you perform X2P migration to Gen8 server having HP Smart Array B320i as primary Controller, you will observe that the name of controller is not displayed in step 5 and 7 of the migration wizard.

64 Troubleshooting

Image 64
Contents HP Insight Control Server Migration 7.2 User Guide Legal Notices Contents Migrating the servers IV Troubleshooting and supportPostmigration tasks Contents CD ISO Contents Support and other resources Glossary Index Part I Overview and concepts Installing and configuring server migration software Server migration introductionOverview Related productsRight configuration Migration checklist Server migration conceptsServer migration components Overview of migrating a serverHP Insight Control server migration software tabs Migration screenHP Insight Control server migration software tabs Part II Premigration tasks Verifying hardware and operating system support Preparing hardware for migrationVerifying system requirements for the application station Planning the migration Resizing Linux file systems Preparing software for migration Verifying licenses for software to be migratedMigration security Disabling firewallsInstalling ProLiant Support Packs Installing Service Pack for ProLiantDisabling antivirus software Generating static or dynamic certificatesPreparing software for migration 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 serverRemoving guest tools Choosing server migration AgentsDeploying 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 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 Source virtual machine prerequisitesSource physical server prerequisites SAN migrations in Windows Launching server migration by using the Deploy menu Starting the migration wizardLaunching server migration by using Quick Launch Identify the source serverQuick Launch Starting the migration wizard Installing ProLiant Support Packs after migration Installing Service Pack for ProLiant after migrationPostmigration tasks X2P postmigration tasks WindowsEdit the boot.ini file to activate a graphical boot process X2V postmigration tasks WindowsX2P postmigration tasks Linux X2V postmigration tasks LinuxViewing migration logs Validating the migrationValidating Linux migrations Validating Windows migrationsPart IV Troubleshooting and support User interface TroubleshootingServer migration wizard hangs HP SIM Source preparation Source server identification failsMigration Agent deployment fails Linux Source Agent window does not appear on Rhel 64-bitIncorrect LUN size is detected in of the migration wizard Perform any one of the following on the source serverDestination preparation Unable to boot Windows due to unsigned or corrupt driversDestination 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 Large volumes fail with a server thread error Drivers cannot be installed or injected onto a boot diskMigration process Migration hangs if the source server is shut down 2011/03/14 141934 The job failedNtfs resize error message appears ReiserFS volumes are blocked for Linux migrationMigration fails during the disk cloning phase Error occurs during data copy of Linux migration SAN-connected destination server displays a blue screenDestination server boots with an invalid IP address HP Smart Array B320i controller name is not displayedLinux migration to servers with iSCSI storage fails to boot PostmigrationHidusb.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 How to contact HP Subscription serviceSupport and other resources Information to collect before contacting HPHP authorized resellers Related informationDocuments WebsitesTypographic conventions Related documentationTIP Documentation feedback Applying old server migration standalone licenses Premigration consideration steps for clusters Basic hardware design of a three-node dusterPerforming the migration Post migration considerations and stepsPost migration considerations and steps Page Glossary Index Page SPP Postmigration tasks Yellow bang ! appears on NIC adapter