Product data

60 PowerVM Migration from Physical to Virtual Storage
9. Update the boot partition and reset the bootlist on the source standalone
system using the AIX bosboot and bootlist commands:
# bosboot -a -d hdisk8
bosboot: Boot image is 40810 512 byte blocks.
# bootlist -m normal hdisk8
#
10.Shut down the standalone client using the AIX shutdown command.
On the SAN disk storage controller
11.Using your SAN disk management software, you should now un-map the SAN
disk from the standalone server and present it to the Virtual I/O Server which
hosts the connections for your client logical partition.
It is important even while you are testing this procedure that an un-map and
re-map is performed. If there is a SCSI reserve on the rootvg in the SAN disk
at the SAN disk controller level then the Virtual I/O Server may not be able to
present the SAN disk correctly to the client logical partition. Any SCSI 2
reservation can be removed by using the appropriate SAN GUI or CLI.
On the Virtual I/O Server
Use the Virtual I/O Server to discover the correct disk:
12.Using the Virtual I/O Server, log in as the padmin user and use the cfgdev
command to ensure that the Virtual I/O Server re-scans for the newly
attached SAN disk.
13.Using the Virtual I/O Server chkdev command will also display the pvid and
unique ID that should match what you wrote down from a previous step:
$ chkdev -dev hdisk6 -verbose
NAME: hdisk6
IDENTIFIER: 3E213600A0B8000291B0800009AE303FEFAE10F1815
FAStT03IBMfcp
PHYS2VIRT_CAPABLE: NA
VIRT2NPIV_CAPABLE: YES
VIRT2PHYS_CAPABLE: YES
PVID: 000fe4016e0bb6e90000000000000000
UDID: 3E213600A0B8000291B0800009AE303FEFAE10F1815
FAStT03IBMfcp
IEEE:
VTD: vtscsi0
$