HP PART NUMBER: 461487-401A manual Installing ProLiant Support Packs, Disabling antivirus software

Page 21

Figure 2 TCP ports in use during migration

NOTE: Insight Control uses the following encryption types:

•SSL RSA with RC4 128 MD5

•SSL RSA with RC4 128 SHA

•TLS RSA with AES 128 CBC SHA cipher suites. To enable the support of AES 256 and FIPS 140-2 cipher suites on server migration with strong cipher, use the utility: <Insight Control server migration Installation Folder>/bin/cipherutil.cmd

Disabling antivirus software

For optimal performance during migration, verify that real-time scanning is temporarily disabled. Also verify that no antivirus scans are running or are scheduled to run while the migration is performed on the application station, source server, or virtual machine hosts.

Generating static or dynamic certificates

Static certificates are used when you run the server migration Source Agent manually on the source server. However, dynamic certificates are generated and used when you use Insight Control server migration to automatically deploy agents to the source and destination servers. HP recommends that the agents be deployed automatically using Insight Control server migration.

Installing ProLiant Support Packs

PSPs contain sets of drivers to get a new ProLiant destination server running quickly after a migration. Windows PSP executables can automatically be installed at the end of a Windows X2P migration.

•For Windows X2P migrations, upload the PSP you plan to use on the Upload Drivers tab of the server migration UI. Also, Windows PSPs can be installed manually after migration.

•For Linux X2P migrations, you must manually apply the Linux PSP to the destination server after the migration is complete.

Installing Service Pack for ProLiant

SPP contains sets of drivers and firmwares to get a new ProLiant Gen8 destination server running quickly after a migration. SPP is installed automatically at the end of a Windows X2P migration.

•For Windows X2P migrations, upload the SPP you plan to use on the Upload Drivers tab of the server migration UI. You can also manually install Windows SPP after server migration

Installing ProLiant Support Packs

21

Image 21

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