Troubleshooting
Problem
I am trying to perform Live Partition Mobility on my LPAR and it fails with HSCLA24E error on my HMC.
Symptom
HSCLA24E The migrating partition's virtual SCSI adapter 5 cannot be
hosted by the existing virtual I/O server (VIOS) partitions 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.
HSCLA24E The migrating partition's virtual SCSI adapter 4 cannot be
hosted by the existing virtual I/O server (VIOS) partitions 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.
Cause
Here are the most common causes for this error code.
Environment
The environment is usually using VSCSI adapters.
Diagnosing The Problem
Checks for HSCLA24E using VSCSI adapters.
1. Common configuration checks to make is to ensure that none of the virtual scsi adapters are set to "Any client partition can connect" and that the adapters are NOT set to required.
2. Determine the max_transfer size of the disks exported thru vhost adapters serving the mobile partition. Then ensure the same value is used on the destination VIO(s):
$ lsdev -dev hdisk# -attr | grep max_transfer
3. Make sure that the disks on the source and destination are configured with reserve_policy = no. If this attribute changed while the disks are mapped or part of a volume group, a reboot of the VIO server will be required in order for the attribute change to take place on the device.
To change the reserve policy to no, run:
$ chdev -dev hdisk# -attr reserve_policy=no_reserve
If the hdisk# is in used (i.e. exported via the vhost#), add -perm option. Then reboot the VIOS at your earliest convenience for the change to take effect.
4. Check that the destination VIO servers are able to see the same storage exported thru the vhost#(s) hosting the mobile partition (on source VIOS). Typically, this can be verified by making sure the disk unique_IDs of the backing devices on the source VIO(s) are accounted for on the target VIO(s). To check UDID value, run:
$ lsdev -dev hdisk# -attr | grep unique_id
5. The same VTD name on a source VIOS cannot be used on the destination VIOS.
(Use lsmap to make sure the VTDs are unique)
6. Make sure that any storage device drivers or multipathing software on the VIO servers is the same version and level, as software version mismatch may cause inconsistencies.
Resolving The Problem
Make any recommended changes for any of the possible problems in the list above.
Related Information
Was this topic helpful?
Document Information
Modified date:
19 February 2022
UID
isg3T1019383