Validating the configuration for partition mobility
You can use the Partition Migration wizard on the Hardware Management Console (HMC) to validate the configuration of the source and destination systems for partition mobility. If the HMC detects a configuration or connection problem, it displays an error message with information to help you resolve the problem.
Before you begin
If the source and destination servers are managed by different Hardware Management Consoles, verify that the Secure Shell (SSH) authentication keys are set up correctly between the Hardware Management Consoles. For instructions, see Verifying SSH authentication between the source and destination HMC.
You must be a super administrator to validate the partition mobility environment.
About this task
Procedure
Results
Where possible, the HMC Version 7 Release 3.5.0, or later, preserves the virtual slot assignments of the virtual server adapters on the destination system. However, in some situations the HMC might not be able to preserve a virtual slot ID. For example, when the slot ID is already occupied on the destination VIOS logical partition. When the HMC cannot preserve a virtual slot ID, you receive an error message, and the HMC assigns an available slot ID. You can override the assignments by completing the following steps from the HMC command-line interface:
- Run the lslparmigr command to show a list of available slot IDs for a VIOS partition.
- Run the migrlpar command
to accomplish the
following tasks:
- Specify virtual slot IDs for one or more virtual adapter mappings.
- Validate the specified slot IDs.Note: You can specify the port name of the Fibre Channel to be used for creating Fibre Channel mapping on the destination server when you are performing partition migration.
You can use the HMC command-line interface to specify the port name.
- List all the valid port names of the Fibre Channel by running the lsnports command.
- From the list of valid port names, specify the port name that you want to use in the
vios_fc_port_name attribute, by running the following
command:
For example:migrlpar -o v -m <srcCecName> -t <dstCecName> -p <lparName> -i "virtual_fc_mappings= <Client_slot_num>/<target_vios_name>/<target_vios_id>/<target_slot_num>/<vios_fc_port_name>"
migrlpar -o v -m vrml13-fsp -t vrml11-fsp -p vrml11lp03 -i "virtual_fc_mappings= 3/vrml11-vios1/1/8/fcs0"
- To
validate the override concurrency level to be used for the
partition mobility operation,
run the following command:
For example:migrlpar -o v -m <srcCecName> -t <dstCecName> -p <lparName> -f "concurr_migration_perf_level=<overrideValue>"
migrlpar -o v -m vrml13-fsp -t vrml11-fsp -p vrml11lp03 -i "concurr_migration_perf_level=3"
- When the mobile partition is configured with the Physical Page Table (PPT) ratio, you can use the migrlpar command to validate the partition mobility operation. When the hypervisor on the destination server does not support PPT ratio, a warning message is displayed. However, the validation operation succeeds. During Live Partition Mobility, the Physical Page Table (PPT) ratio is used to translate effective addresses to physical real addresses. The PPT ratio is the ratio of the PPT size to the maximum memory value for the logical partition. The PPT ratio is used by the hypervisor for paging during Live Partition Mobility. For more information about PPT ratio and migration, see Migration and PPT ratio.