Troubleshooting active partition mobility

HSCL3656 There is an insufficient amount of memory available on the destination managed system for the configuration of the partition. Please perform one or both of the following actions: 1. Remove memory from any shutdown dedicated memory partitions on the destination managed system. 2. Remove memory from any running dedicated memory partitions on the destination managed system.

1. To make physical memory available for the mobile partition, dynamically remove physical memory from inactive logical partitions that use dedicated memory (subsequently referred to as dedicated memory partitions) on the destination server by running the chhwres command from the HMC command line. For example, chhwres -r mem -m <destination_server> -o r -p <logical_partition> -q <memory>, where:
   • <destination_server> is the name of the server to which you want to move the mobile partition.
   • <logical_partition> is the name of the logical partition from which you want to remove physical memory.
   • <memory> is the amount of physical memory, in MB, that you want to remove from the logical partition.
2. If you cannot satisfy the memory requirement of the mobile partition by removing physical memory from dedicated memory partitions that are inactive, dynamically remove physical memory from dedicated memory partitions that are active on the destination server by performing one of the following tasks:
   • Removing dedicated memory dynamically using the HMC
   • Running the chhwres command from the HMC command line.

HSCL03EC There is not enough memory: Obtained : xxxx, Required : xxxx. Check that there is enough memory available to activate the partition. If not, create a new profile or modify the existing profile with the available resources, then activate the partition. If the partition must be activated with these resources, de-activate any running partition(s) using the resource then activate this partition.

1. To make physical memory available for the mobile partition, dynamically remove physical memory from inactive logical partitions that use dedicated memory (subsequently referred to as dedicated memory partitions) on the destination server by running the chhwres command from the HMC command line. For example, chhwres -r mem -m <destination_server> -o r -p <logical_partition> -q <memory>, where:
   • <destination_server> is the name of the server to which you want to move the mobile partition.
   • <logical_partition> is the name of the logical partition from which you want to remove physical memory.
   • <memory> is the amount of physical memory, in MB, that you want to remove from the logical partition.
2. If you cannot satisfy the memory requirement of the mobile partition by removing physical memory from dedicated memory partitions that are inactive, dynamically remove physical memory from dedicated memory partitions that are active on the destination server by performing one of the following tasks:
   • Removing dedicated memory dynamically using the HMC
   • Running the chhwres command from the HMC command line.
3. If you cannot satisfy the memory requirement of the mobile partition by dynamically removing physical memory from dedicated memory partitions that are active on the destination server, dynamically remove memory from the mobile partition. For instructions, see Removing dedicated memory dynamically using the HMC.
4. If you cannot reduce the amount of memory required by the mobile partition to an amount that is equal to or less than the amount of memory that is available on the destination server, shut down logical partitions on the destination server until enough memory is available for the mobile partition to activate on the destination server.
5. If you cannot satisfy the memory requirement of the mobile partition by shutting down logical partitions on the destination server, move the mobile partition to the destination server by using inactive partition mobility.

HSCLA319 The migrating partition's virtual Fibre Channel client adapter cannot be hosted by the existing Virtual I/O Server (VIOS) partitions on the destination managed system.

• The storage area network (SAN) employs port zoning. The target server ports and source server ports are not zoned identically. To host the migrating virtual adapter, the list of Fibre Channel targets in a port on the target server must exactly match the list of Fibre Channel targets in the current mapped port of the migrating virtual adapter on the source server.
• The two worldwide port names (WWPNs) assigned to the virtual adapter are not zoned identically. The two WWPNs must be interchangeable from both SAN and storage point of view.
• The target server does not have a port that can meet or exceed the maximum transfer size of the source server port. The maximum transfer size is an attribute of the Fibre Channel port and can be viewed by running the lsattr command on a Fibre Channel device.
• A switch on the SAN might be configured to use features that extend the Fibre Channel standard in ways that are not compatible with Live Partition Mobility. For example, a port binding feature that tracks WWPN-to-port mappings. This feature can cause problems because Live Partition Mobility validation requires that all ports must be explored through a series of login and logout operations. If the switch tries to track the WWPN-to-port mappings, it might run out of resources and not permit login operations. Disabling this type of feature solves some problems related to failed Fibre Channel login operations.

• Move the logical partition to another system.
• Update the operating system to a level that supports the target system processor version registers.

1. Examine the operating system error logs for operating system-related failures.
2. Examine the HMC log for application-related failures.

1. In the navigation pane, open Systems Management.
2. Select Servers.
3. In the work pane, select the source server. If the source server is unavailable, select the destination server.
4. In the Tasks menu, select Mobility > Recover. The Migration Recovery window is displayed.
5. Click Recover.
6. If you recovered the migration from the HMC that manages the destination server (and a different HMC manages the source server), you might have to manually perform additional recovery tasks on the source server to finish the recovery. For example, even though the migration occurs and the mobile partition runs on the destination server, the mobile partition might appear as an inactive logical partition on the source server. In this situation, remove the mobile partition from the source server to finish the recovery.

This error typically occurs when there is a network connection problem between the logical partitions and the HMC. To resolve this error, check your system network setup.