Christie DS4K Bedienungsanleitung

ibm.com/redbooksPowerVM Migration from Physical to Virtual StorageAbid KhwajaDominic LancasterMoving to a Virtual I/O Server managed environmentReady-

viii PowerVM Migration from Physical to Virtual Storagetechniques on various operating platforms. You may copy, modify, and distribute these sample p

86 PowerVM Migration from Physical to Virtual Storage Serial Number... Device Specific.(Z0)...0000053245005032

Chapter 4. Standalone SCSI data to virtual SCSI 87On the HMC4. Map a virtual SCSI adapter from the Virtual I/O Server to the client logical partitio

88 PowerVM Migration from Physical to Virtual StorageOn the client partitionThe SAN LUN will be visible to the client as a SCSI disk. 6. Verify that

© Copyright IBM Corp. 2010. All rights reserved. 89Chapter 5. Logical partition migrationsIn this chapter we describe the methods for moving data from

90 PowerVM Migration from Physical to Virtual Storage5.1 Direct-attached SCSI partition to virtual SCSIThis migration method describes a scenario wh

Chapter 5. Logical partition migrations 91c. Check whether the disks to be migrated have a unique ID using the lsattr command:# lsattr -El hdisk0PCM

92 PowerVM Migration from Physical to Virtual Storage2. Identify the parent device to which hdisk0 is connected. This is done using the lsdev command

Chapter 5. Logical partition migrations 93 Serial Number...YL10C4061142 Manufacture ID...000C EC Level..

94 PowerVM Migration from Physical to Virtual StorageOn the HMCThe HMC is now used to create client and server virtual SCSI adapters and migrate the

Chapter 5. Logical partition migrations 95slot number is 15 and the free client slot number is 5. Figure 5-3 shows the required properties to create

© Copyright IBM Corp. 2010. All rights reserved. ixPrefaceIT environments in organizations today face more challenges than ever before. Server rooms a

96 PowerVM Migration from Physical to Virtual Storage10.Modify the Virtual I/O Server to add the SCSI adapter to the profile.Figure 5-4 shows the sto

Chapter 5. Logical partition migrations 9712.Create a client virtual SCSI adapter. Select your client partition and navigate through, selecting your

98 PowerVM Migration from Physical to Virtual Storageb. Use the lsmap command to ensure that vhost4 is the correct virtual adapter:$ lsmap -all | gre

Chapter 5. Logical partition migrations 9915.Create a mapping from the physical disk and verify that the mapping is correct:a. Use the mkvdev comman

100 PowerVM Migration from Physical to Virtual StorageIn the previous output the C5 is the client slot number and 8100000000000000 matches the value

Chapter 5. Logical partition migrations 101already have a physical Fibre Channel adapter on the Virtual I/O Server, you may do the migration by mapp

102 PowerVM Migration from Physical to Virtual StorageOn the source partitionThe following series of commands show us the pre-migration state of the

Chapter 5. Logical partition migrations 103hdisk1 Available 00-08-02 MPIO Other FC SCSI Disk Drivehdisk2 Available 00-08-02 MPIO Other FC SC

104 PowerVM Migration from Physical to Virtual StorageFilesystem 1024-blocks Free %Used Iused %Iused Mounted on/dev/hd4 196608

Chapter 5. Logical partition migrations 105On the HMCThe Fibre Channel adapter must now be remapped from the source partition to the Virtual I/O Ser

x PowerVM Migration from Physical to Virtual Storagestep-by-step and allow the reader to determine which migration techniques will work best for them

106 PowerVM Migration from Physical to Virtual Storage2. Dynamically add the physical Fibre Channel adapter removed from the source partition profile

Chapter 5. Logical partition migrations 1073. Dynamically add two virtual SCSI server adapters to the Virtual I/O Server, one for rootvg and the oth

108 PowerVM Migration from Physical to Virtual StorageFigure 5-10 shows the Virtual Adapters panel with our two server SCSI adapters added.Figure 5-1

Chapter 5. Logical partition migrations 1094. Since our destination partition is currently shut down, add two virtual SCSI client adapters to the de

110 PowerVM Migration from Physical to Virtual Storagebelow, the PHYS2VIRT_CAPABLE field for both disks show a state of YES. This tells us that it is

Chapter 5. Logical partition migrations 111vhost7 U8204.E8A.10FE411-V2-C18 0x00000000VTD NO VIRTUAL T

112 PowerVM Migration from Physical to Virtual Storage8. Activate the destination client partition in SMS mode and select the disk to boot from that

Chapter 5. Logical partition migrations 113Compare the output below to the output gathered from the pre-migration source partition.The tail command

114 PowerVM Migration from Physical to Virtual StorageIn Figure 5-12, a direct-attached Fibre Channel adapter is shown with SAN disks for the client

Chapter 5. Logical partition migrations 115On the client partitionOn the client logical partition first capture details of the resources that are go

Preface xileading-edge technologies. Your efforts will help to increase product acceptance and customer satisfaction, as you expand your network of

116 PowerVM Migration from Physical to Virtual Storage hdisk LUN # Ownership User Label hdisk4 1 B (preferred

Chapter 5. Logical partition migrations 117identification refer to 2.2, “Checking unique disk identification” on page 13. The key values to record f

118 PowerVM Migration from Physical to Virtual StorageFC World Wide Name False#6. Now capture details about the Fibre Channel card if y

Chapter 5. Logical partition migrations 119 Device Specific.(ZM)...3 Network Address...10000000C9738E84 ROS Leve

120 PowerVM Migration from Physical to Virtual Storageprofile of the running Virtual I/O Server immediately so that on a restart, the Fibre Channel r

Chapter 5. Logical partition migrations 121a. Enter the required slot numbers into the Create Virtual Fibre Channel Adapter panel, as in Figure 5-14

122 PowerVM Migration from Physical to Virtual Storageb. The HMC panel that is displayed is to the panel in Figure 5-15 and shows that the virtual Fi

Chapter 5. Logical partition migrations 12312.Modify the profile of the client logical partition and create a virtual Fibre Channel client adapter.

124 PowerVM Migration from Physical to Virtual Storagea. Select the Virtual Adapters tab, as in Figure 5-17.Figure 5-17 Virtual Adapters tab

Chapter 5. Logical partition migrations 125b. Using the Actions drop-down box, as in Figure 5-18, select Create  Fibre Channel Adapter.Figure 5-18

xii PowerVM Migration from Physical to Virtual Storage

126 PowerVM Migration from Physical to Virtual Storagec. In the Fibre Channel resource panel (Figure 5-19) enter the slot numbers that match the numb

Chapter 5. Logical partition migrations 127As shown in Figure 5-20, you can now see that a Client Fibre Channel Adapter has been created.Figure 5-20

128 PowerVM Migration from Physical to Virtual Storaged. Once you have clicked OK on the above panel, reselect the Virtual Adapters tab and select th

Chapter 5. Logical partition migrations 129The resulting panel displays the assigned WWPNs, as shown in Figure 5-22.Figure 5-22 Virtual Fibre Chan

130 PowerVM Migration from Physical to Virtual Storagevhost3 Available Virtual SCSI Server Adaptervhost4 Available Virtual SC

Chapter 5. Logical partition migrations 131Create the mapping between the resources:a. Use the lsmap command to view the newly added virtual Fibre C

132 PowerVM Migration from Physical to Virtual Storagecannot see them at this stage). For further information refer to 2.4, “Virtual Fibre Channel an

Chapter 5. Logical partition migrations 133򐂰 Mapped a physical Fibre Channel port to the virtual Fibre Channel host with the vfcmap command򐂰 Started

134 PowerVM Migration from Physical to Virtual Storaged. Type 3 and press Enter to use SAN media.At this point, the following screen is displayed:---

Chapter 5. Logical partition migrations 135These PVIDs match the values that were recorded prior to the migration.b. The AIX lsvg command also shows

© Copyright IBM Corp. 2010. All rights reserved. 1Chapter 1. IntroductionThis publication provides instructions on how to transition from direct-attac

136 PowerVM Migration from Physical to Virtual StorageThe previous steps prove conclusively that the migration from a logical partition with a direct

Chapter 5. Logical partition migrations 1375.4 Virtual SCSI rootvg and data to virtual Fibre ChannelIn this section a logical partition's virt

138 PowerVM Migration from Physical to Virtual StorageOn the source partitionThe following series of commands show us the pre-migration state of the

Chapter 5. Logical partition migrations 139# tail -2 /etc/hosts192.168.100.92 p2_411192.168.100.91 p1_411Having gathered the configuration and val

140 PowerVM Migration from Physical to Virtual Storagevhost7 U8204.E8A.10FE411-V2-C18 0x00000004VTD NO

Chapter 5. Logical partition migrations 141Figure 5-25 Virtual Fibre Channel adapter added to client profile6. Dynamically remove the virtual SCSI

142 PowerVM Migration from Physical to Virtual Storageare ported to the second port on the adapter, so fcs1 is the correct adapter to use.$ lsdev | g

Chapter 5. Logical partition migrations 143hdisk1 Available C8-T1-01 MPIO Other DS4K Array Disk# lsdev -l hdisk2hdisk2 Available C8-T1-01 MPIO Other

144 PowerVM Migration from Physical to Virtual Storage

© Copyright IBM Corp. 2010. All rights reserved. 145Chapter 6. Standalone SAN rootvg to virtual Fibre ChannelIn this chapter we show you how to migrat

2 PowerVM Migration from Physical to Virtual Storage1.1 DefinitionsThe following definitions will assist you in understanding the material located w

146 PowerVM Migration from Physical to Virtual StorageFigure 6-1 Migrate standalone SAN rootvg to client partition SAN rootvg over Virtual Fibre Ch

Chapter 6. Standalone SAN rootvg to virtual Fibre Channel 147On the standalone source hostThe lspv command below shows us that rootvg is on hdisk8.

148 PowerVM Migration from Physical to Virtual StorageOn the HMCCreate the virtual Fibre Channel mappings that will allow the client partition to see

Chapter 6. Standalone SAN rootvg to virtual Fibre Channel 149partition. Something similar to the highlighted portion in Figure 6-3 is what you shoul

150 PowerVM Migration from Physical to Virtual Storage6. Get the list of all available physical Fibre Channel server adapters. As you can see from th

Chapter 6. Standalone SAN rootvg to virtual Fibre Channel 15111.Verify that the client has booted with the same LUN that was on the standalone machi

152 PowerVM Migration from Physical to Virtual Storage

© Copyright IBM Corp. 2010. All rights reserved. 153Chapter 7. Direct attached Fibre Channel devices partition to virtual Fibre ChannelThis section pr

154 PowerVM Migration from Physical to Virtual StorageIn Figure 7-1, LPAR1 and the Virtual I/O Server can both access the LTO4 tape drive since both

Chapter 7. Direct attached Fibre Channel devices partition to virtual Fibre Channel 155The steps required to accomplish this are covered in the foll

Chapter 1. Introduction 31.3 Test environmentThe environment in which testing of the migration scenarios was performed is depicted in Figure 1-1.Fi

156 PowerVM Migration from Physical to Virtual Storage4. Remove the tape devices and library device, if present, from the system. The AIX rmdev comma

Chapter 7. Direct attached Fibre Channel devices partition to virtual Fibre Channel 157b. Select the Virtual I/O Server partition on which the virtu

158 PowerVM Migration from Physical to Virtual Storagec. Create a virtual Fibre Channel server adapter. Select Actions  Create  Fibre Channel Adapt

Chapter 7. Direct attached Fibre Channel devices partition to virtual Fibre Channel 159d. Enter the virtual slot number for the Virtual Fibre Channe

160 PowerVM Migration from Physical to Virtual Storagee. Remember to update the profile of the Virtual I/O Server partition so that the change is ref

Chapter 7. Direct attached Fibre Channel devices partition to virtual Fibre Channel 1618. To create the virtual Fibre Channel client adapter in the

162 PowerVM Migration from Physical to Virtual Storageb. To create the virtual Fibre Channel client adapter select the profile, then select Actions 

Chapter 7. Direct attached Fibre Channel devices partition to virtual Fibre Channel 163c. Enter the virtual slot number for the Virtual Fibre Channe

164 PowerVM Migration from Physical to Virtual Storage12.Run the lsnports command to check the Fibre Channel adapter NPIV readiness of the adapter an

Chapter 7. Direct attached Fibre Channel devices partition to virtual Fibre Channel 165On the HMC: part 2Now you have created the virtual Fibre Chan

4 PowerVM Migration from Physical to Virtual Storage1.4 Storage device compatibility in a Virtual I/O Server environmentPhysical-to-virtual (p2v) de

166 PowerVM Migration from Physical to Virtual Storageb. Figure 7-10 shows the properties of the virtual Fibre Channel client adapter. Here you can g

Chapter 7. Direct attached Fibre Channel devices partition to virtual Fibre Channel 167sub-command can be shortened from the prior example and typed

168 PowerVM Migration from Physical to Virtual StorageDrive Address 256 Drive State ... Normal ASC/ASCQ ... 00

© Copyright IBM Corp. 2010. All rights reserved. 169AIX Advanced Interactive ExecutiveAPAR Authorized Program Analysis ReportAPI Application Programm

170 PowerVM Migration from Physical to Virtual StorageSDD Subsystem Device DriverSMIT System Management Interface ToolSMS System Management ServicesS

© Copyright IBM Corp. 2010. All rights reserved. 171Related publicationsThe publications listed in this section are considered particularly suitable f

172 PowerVM Migration from Physical to Virtual StorageHelp from IBMIBM Support and downloadsibm.com/supportIBM Global Servicesibm.com/services

© Copyright IBM Corp. 2010. All rights reserved. 173IndexAAIXalt_disk_copy 68alt_rootvg_op 74bootlist 60, 71, 100, 115bosboot 60, 71, 100cfgd

174 PowerVM Migration from Physical to Virtual StorageBrocadeportcfgshow 37portLoginShow 39portshow 38telnet 37smittymkcd 46VIOScfgdev 24

Index 175NOT_LOGGED_IN 142NPIV 26, 147enabling 26requirements 26Ooem_setup_env 71Ppadmin 97PHYS2VIRT_CAPABLE 17, 72, 98, 110–111physic

Chapter 1. Introduction 5A device is considered to be p2v compatible if it meets the following criteria:򐂰 It is an entire physical volume (for examp

176 PowerVM Migration from Physical to Virtual Storagermvopt 12slot number 110unloadopt 13, 52vfcmap 31, 131, 150, 164viosbr 9viosbr 7, 9

PowerVM Migration from Physical to Virtual Storage

®SG24-7825-00 ISBN 0738433888INTERNATIONAL TECHNICALSUPPORTORGANIZATIONBUILDING TECHNICALINFORMATION BASED ONPRACTICAL EXPERIENCE IBM Redbooks are dev

6 PowerVM Migration from Physical to Virtual StorageIn Table 1-1 a number of migrations are presented from a source host configuration through to the

Chapter 1. Introduction 7The following is a suggested flow for using Table 1-1 on page 6:1. Learn how to use the virtual SCSI and virtual Fibre Chan

8 PowerVM Migration from Physical to Virtual Storage

© Copyright IBM Corp. 2010. All rights reserved. 9Chapter 2. Core proceduresThere are a number of core procedures that are used in multiple scenarios

10 PowerVM Migration from Physical to Virtual Storage2.1 File-backed optical for restorationFile-backed optical devices provide a clean, easy-to-use

Chapter 2. Core procedures 11Using the AIX mkcd command-line methodTo use the AIX mkcd command-line method, use the following procedures:1. Run the

12 PowerVM Migration from Physical to Virtual StorageOn the Virtual I/O ServerA media repository and a virtual optical device must now be created. Th

Chapter 2. Core procedures 1310.If you have multiple media created and the procedure that you are running asks for the next CD in the sequence, use

14 PowerVM Migration from Physical to Virtual Storage2.2.1 The physical volume identifier (PVID)The PVID is written to a disk when the disk has been

Chapter 2. Core procedures 15ieee_volname 600A0B8000110D0E0000000E47436859 IEEE Unique volume name Falselun_id 0x000

PowerVM Migration from Physical to Virtual StorageJanuary 2010International Technical Support OrganizationSG24-7825-00

16 PowerVM Migration from Physical to Virtual Storageclr_q no Device CLEARS its

Chapter 2. Core procedures 172.2.4 The chkdev commandAs of Virtual I/O Server Fix Pack 22, a new command has been introduced to assist with the ide

18 PowerVM Migration from Physical to Virtual Storage2.3 Creating a virtual SCSI deviceIn a virtual SCSI storage environment, the Virtual I/O Server

Chapter 2. Core procedures 19Figure 2-1 shows the relationship between physical SCSI disk and the target SCSI device on the Virtual I/O Server.Figur

20 PowerVM Migration from Physical to Virtual StorageFigure 2-2 shows the relationship between physical SCSI disk and the virtual SCSI devices on a c

Chapter 2. Core procedures 21On the HMCThe objective is to create the server and client adapters that will allow the disks being presented from a ph

22 PowerVM Migration from Physical to Virtual Storagewill be available to only a single partition since a specific partition was specified. This is t

Chapter 2. Core procedures 23For this example, the adapter was dynamically added. If you want your configuration to be permanent, add the adapter to

24 PowerVM Migration from Physical to Virtual Storage4. Create the virtual client adapter. You must use the same slot numbers that you selected in th

Chapter 2. Core procedures 25The first lsmap command in the following command output shows us that vhost6 is mapped to server slot C17 (as previousl

© Copyright International Business Machines Corporation 2010. All rights reserved.Note to U.S. Government Users Restricted Rights -- Use, duplication

26 PowerVM Migration from Physical to Virtual Storage2.4 Virtual Fibre Channel and N_Port ID virtualizationN_Port ID virtualization (NPIV) is a tech

Chapter 2. Core procedures 27Detailing the procedure to use NPIV follows. In the scenario described, it is assumed that you have:򐂰 A running standal

28 PowerVM Migration from Physical to Virtual StorageOn the HMCCreate the virtual Fibre Channel mappings that will allow the destination client parti

Chapter 2. Core procedures 292. Create the virtual Fibre Channel client adapter in the client partition profile. If you want the adapter and storage

30 PowerVM Migration from Physical to Virtual StorageOn the standalone source host3. Shut down the standalone host and remap the SAN rootvg LUN on th

Chapter 2. Core procedures 31To get to the above panel, on the HMC select the client partition, click Properties from the Tasks menu. Select the Vir

32 PowerVM Migration from Physical to Virtual StoragePorts logged in:7Flags:a<LOGGED_IN,STRIP_MERGE>VFC client name:fcs0 VFC client

Chapter 2. Core procedures 33At this point, the following SMS panel is displayed:-------------------------------------------------------------------

34 PowerVM Migration from Physical to Virtual StorageIn Figure 2-10, the relationship between the virtual Fibre Channel components and what the SAN s

Chapter 2. Core procedures 35Method 1: the SwitchExplorer Web Interfacea. Use your Web browser to point to the URL of your SAN switches’ IP address,

© Copyright IBM Corp. 2010. All rights reserved. iiiContentsFigures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

36 PowerVM Migration from Physical to Virtual Storageb. In Figure 2-11 on page 35, port 6 has been highlighted since this is our physical port from o

Chapter 2. Core procedures 37d. The panel shown in Figure 2-13 is displayed.Figure 2-13 SAN port device detailsThe highlighted device port WWN is

38 PowerVM Migration from Physical to Virtual StorageVC Link Init .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..Locked L_Port .. .. .

Chapter 2. Core procedures 39Lli: 109 Loss_of_sig: 7Proc_rqrd: 2422 Protocol_err: 0Timed_out: 0

40 PowerVM Migration from Physical to Virtual Storage Select Device Device Current

Chapter 2. Core procedures 4114.Enter option 1 to exit the SMS menu, as shown here:-----------------------------------------------------------------

42 PowerVM Migration from Physical to Virtual StorageThe remaining lsdev commands list out all Fibre Channel adapters and show how hdisk8 maps back t

© Copyright IBM Corp. 2010. All rights reserved. 43Chapter 3. Standalone SCSI rootvg to virtual SCSIThis chapter details the migration of a standalone

44 PowerVM Migration from Physical to Virtual StorageFigure 3-1 shows an overview of the process.Figure 3-1 Migration from standalone rootvg on loc

Chapter 3. Standalone SCSI rootvg to virtual SCSI 45As with any migration, planning is essential. Our instructions generally refer to a single disk

iv PowerVM Migration from Physical to Virtual Storage4.3 Transition raw data disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

46 PowerVM Migration from Physical to Virtual Storage3.1 Back up to CD and restoreThis migration uses the file backed optical feature of the Virtual

Chapter 3. Standalone SCSI rootvg to virtual SCSI 47d. For the File system to store final CD images question, you can leave it blank or chose to use

48 PowerVM Migration from Physical to Virtual Storagevasi0 Available Virtual Asynchronous Services Interface (VASI)vbsd0 Avai

Chapter 3. Standalone SCSI rootvg to virtual SCSI 499. Use the Virtual I/O Server lsmap command to verify that the device has been created:$ lsmap -

50 PowerVM Migration from Physical to Virtual Storaged. The lsrep command can be used to show which images you have loaded into the repository: $ lsr

Chapter 3. Standalone SCSI rootvg to virtual SCSI 5119.Type the 5, as shown in Example 3-1.Example 3-1 Main SMS Entry Panel-----------------------

52 PowerVM Migration from Physical to Virtual Storage24.In response to the Select Media Adapter panel, type the number that represents the virtual SC

Chapter 3. Standalone SCSI rootvg to virtual SCSI 53repository you can also create all the media up front and not revisit this step again: $ mkvopt

54 PowerVM Migration from Physical to Virtual Storagethe mirroring procedure is complete to allow the target client logical partition to access the S

Chapter 3. Standalone SCSI rootvg to virtual SCSI 55On the standalone serverStart by determining the size of the root volume group, then use the mig

© Copyright IBM Corp. 2010. All rights reserved. vFigures1-1 Test environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

56 PowerVM Migration from Physical to Virtual StorageNumber of running methods: 0----------------attempting to configure device 'fscsi0'Tim

Chapter 3. Standalone SCSI rootvg to virtual SCSI 574. List the disks using the AIX lsdev command to ensure that the SAN disk is presented correctly

58 PowerVM Migration from Physical to Virtual Storagemax_transfer 0x40000 Maximum TRANSFER

Chapter 3. Standalone SCSI rootvg to virtual SCSI 597. Use the AIX migratepv command to move the contents of the local SAS/SCSI disk to the SAN disk

60 PowerVM Migration from Physical to Virtual Storage9. Update the boot partition and reset the bootlist on the source standalone system using the AI

Chapter 3. Standalone SCSI rootvg to virtual SCSI 61Ensure that the UUID in this step matches that from step 5. This will confirm the same disk is m

62 PowerVM Migration from Physical to Virtual Storage15.Because there is a physical disk in use here, you must navigate to the Physical Volumes tab,

Chapter 3. Standalone SCSI rootvg to virtual SCSI 6316.Select the required hard disk, such as hdisk6, to map to the client partition and click Modif

64 PowerVM Migration from Physical to Virtual Storage17.Select the new partition assignment and click OK to accept that you are assigning this volume

Chapter 3. Standalone SCSI rootvg to virtual SCSI 65On the client partition18.You can now boot the client logical partition using the SMS option and

vi PowerVM Migration from Physical to Virtual Storage5-13 Add a Fibre Channel adapter to the Virtual I/O Server . . . . . . . . . . . . . 1205-14 C

66 PowerVM Migration from Physical to Virtual StorageFigure 3-8 provides an overview of this process.Figure 3-8 alt_disk_copy using SAN diskThe ste

Chapter 3. Standalone SCSI rootvg to virtual SCSI 67VG PERMISSION: read/write TOTAL PPs: 546 (139776 megabytes)MAX LVs:

68 PowerVM Migration from Physical to Virtual Storagehcheck_mode nonactive Health Check Mode

Chapter 3. Standalone SCSI rootvg to virtual SCSI 69Creating logical volume alt_hd9varCreating logical volume alt_hd3Creating logical volume alt_hd1

70 PowerVM Migration from Physical to Virtual Storagesystem console.forced unmount of /alt_inst/var/adm/ras/livedumpforced unmount of /alt_inst/var/a

Chapter 3. Standalone SCSI rootvg to virtual SCSI 717. One of the final actions of the alt_disk_copy command is to set the bootlist to the newly cre

72 PowerVM Migration from Physical to Virtual StorageThe other important output from the chkdev command is the PHYS2VIRT_CAPABLE field. In this examp

Chapter 3. Standalone SCSI rootvg to virtual SCSI 73VIRT2NPIV_CAPABLE: YESVIRT2PHYS_CAPABLE: YESPVID: 000fe4017e0037d700000000000

74 PowerVM Migration from Physical to Virtual StorageOn the standalone systemYou have now migrated this system to a logical partition. If you wish to

Chapter 3. Standalone SCSI rootvg to virtual SCSI 75NIM also allows you to perform functions such as:򐂰 Installation of system patch bundles򐂰 Install

© Copyright IBM Corp. 2010. All rights reserved. viiNoticesThis information was developed for products and services offered in the U.S.A. IBM may not

76 PowerVM Migration from Physical to Virtual StorageThe following notes apply to the use of a SAS-connected tape drive:򐂰 At the time of writing, onl

© Copyright IBM Corp. 2010. All rights reserved. 77Chapter 4. Standalone SCSI data to virtual SCSIThis chapter provides instructions for migrating a c

78 PowerVM Migration from Physical to Virtual Storageremaining disks are used as data disks. The SAN storage is provided by a DS4800. The destination

Chapter 4. Standalone SCSI data to virtual SCSI 794.1 Migration using a virtual media repositoryThe goal of this section is to make a backup of a u

80 PowerVM Migration from Physical to Virtual Storagemkrr_fs was successful.Removing temporary file system: /mkcd/cd_fs...Removing temporary file sys

Chapter 4. Standalone SCSI data to virtual SCSI 81$ mkvdev -fbo -vadapter vhost4 -dev vcd1vcd1 AvailableThe virtual optical device will appear as Vi

82 PowerVM Migration from Physical to Virtual StorageOn the HMC8. Map the vhost adapter from the previous step to a SCSI adapter on the client logica

Chapter 4. Standalone SCSI data to virtual SCSI 83 Preserve Physical Partitions for each Logical Volume: noEnter y to continue: y0516-1254

84 PowerVM Migration from Physical to Virtual Storagedatasrclv jfs2 1 1 1 open/syncd /mnt# cd /mnt# ls -ltotal 8-rw

Chapter 4. Standalone SCSI data to virtual SCSI 85Files are backed up by name.The user is root.x 14 ./tmp/vgdata/datasrcvg/image.infox