Product data

Chapter 1. Introduction 5
A device is considered to be p2v compatible if it meets the following criteria:
򐂰 It is an entire physical volume (for example, a LUN).
򐂰 Device capacity is identical in both physical and virtual environments.
򐂰 The Virtual I/O Server is able to manage this physical volume using a UDID or
IEEE ID. For more information about determining whether a physical volume
has a UDID or IEEE identification field see 2.2, “Checking unique disk
identification” on page 13.
Devices managed by the following multipathing solutions within the Virtual I/O
Server are expected to be UDID devices:
򐂰 All multipath I/O (MPIO) versions, including Subsystem Device Driver Path
Control Module (SDDPCM), EMC PCM, and Hitachi Dynamic Link Manager
(HDLM) PCM
򐂰 EMC PowerPath 4.4.2.2 and later
򐂰 IBM Subsystem Device Driver (SDD) 1.6.2.3 and later
򐂰 Hitachi HDLM 5.6.1 and later
Virtual SCSI devices created with earlier versions of PowerPath, HDLM, and
SDD are not managed by UDID format and are not expected to be p2v compliant.
The operations mentioned previously (for example, data replication and
movement between Virtual I/O Server and non-Virtual I/O Server environments)
are not likely to work in these cases.
1.5 Overview of the physical-to-virtual migration
process
This section provides an overall set of instructions about how to transition the
various storage configurations in order to utilize Virtual I/O Server storage
functionality. These instructions point users to information that they should use
for their particular situations.
Note: If there is any doubt about device compatibility you should contact IBM
and your storage vendor before attempting physical-to-virtual migration. For
additional information refer to the InfoCenter POWER Systems Web site:
http://publib.boulder.ibm.com/infocenter/powersys/v3r1m5/index.jsp?
topic=/iphb1_vios_device_compat.htm