LPAR Migration Error Messages
DanielJMartin 060001XHWG Visits (4476)
Error Message - HSCLA24E
This week we where trying to migrate some VIO hosted LPARs using XIV disk from one POWER 7 system to another. The disk is hosted on a VIO server via the fabric, then using vscsi devices to map up to the servers. Unfortunately the migration failed and the message we got was -
HSCLA24E The migrating partition's virtual SCSI adapter 2 cannot be hosted by the existing virtual I/O server (VIOS) partition on the destination managed system. To migrate the partition, set up the necessary VIOS hosts on the destination managed system, then try the operation again.
1) On the source Virtual I/O Server partition, do not set the adapter as required and do not select Any client partition can connect when you create a virtual SCSI adapter. (can cause the error code).
2) max transfer size of the used hdisk may not be different on source and destination VIOS.
3) The VIO Servers may not have set the reserve_policy to single_path, no_reserve is required.
4) Destination VIO Servers are not able to see the disks the client needs.
5) the same VTD (Virtual target devices) names may not exist on the destination system.
But as we have XIV disk you also need to ensure that the following matches up on the source and destination system else it will fail as above, so on the target and host machines run the following (from oem_setup_env)-
# lsattr -El hdisk<#>
Look at the following values and make sure they match up between the systems on all the disks you will be using.
algorithm fail_overmax_transfer 0x100000
Data disks -
Setting the 'fail_over' on the boot disks is important as while you might be able to see the disk, 'round_robin' will cause the OS to fail to boot. If the information is different between the VIO Server you are migrating too and from then the migration will fail, so this means your need to perform some pre-activities to ensure it works.
The command to change the values is -
# chdev -l hdisk<#> -a <field>=<vaule>
For example -
# chdev -l hdisk43 -a algo
HSCLA27C The operation to get the physical device location for adapter U911
In this case it was simply that one of the disks for the migration had been missed when we had set them to 'no_reserve'. This meant I had to bring the system down rather then doing a live move, then removing the assigned disk device, making the attribute change and then using the mkvdev to recreate it from the old information. After this the migration went along all OK, but below is a example of the commands -
# lsmap -vadapter vhost#
# rmvdev -vtd <server-id>
# chdev -dev hdisk## -attr rese
# mkvdev -vdev hdisk## -vadapter vhost# -dev <ser
Error Message - HSCLA2B7
I've hit another issue on another migration this week, so I thought I should post what I found -
HSCLA2B7 - The HMC was unable to find a valid mover service partition (MSP) on managed system ****
In this case it was easy to resolve. From the HMC Gui just find your VIO server, 'right click' it and select properties. You should then get a little window pop up and showing you the LPAR details of you VIO server, and in my case the 'Mover' service was not enabled. So just select the tick box, then click OK and the service should start. Happy days again, you migration should now work all lovely again.