3 Preparing hardware for migration
Verifying hardware and operating system support
Before starting an X2P (P2P or V2P) migration, verify the following:
•The source server operating system is supported on the destination server. To verify OS support on ProLiant destination servers, see the following website:
http://www.hp.com/go/ossupport
•For the supported hardware and software configurations of server migration, see HP Insight Management Support Matrix available at:
http://www.hp.com/go/insightmanagement/docs
Remove unsupported storage and NIC controllers from the destination server before performing a migration. Unsupported storage and NIC controllers can be added back on the destination server, with proper manual configuration, after performing a migration.
Verifying application station system requirements
The application station has the following prerequisites:
•A supported Windows operating system running on physical hardware or as a Windows guest on a supported hypervisor. For a list of supported operating systems, and CMS hardware and software requirements and caveats see the HP Insight Management Support Matrix at the following website:
http://www.hp.com/go/insightmanagement/docs
•Microsoft iSCSI Initiator, which you can download and install from http://www.microsoft.com if not already available with the operating system on your application station.
•Insight Control server migration installed on an NTFS partition
•Availability of ports 51124 and 51125 (or ports specified during Insight Control installation for agent communications and iLO booting)
•Availability of port 51127
•User account credentials with administrative rights
•Free disk space of at least 300 MB per iLO Boot, while booting a destination server for P2P and V2P
•The initial installation of Insight Control server migration can take 1GB of storage space, and each automatically booted destination server will need at least 300MB of storage space on the application station for
16 Preparing hardware for migration