LDom migration in a VCS environment

VCS supports a warm LDom migration when VCS is installed in a logical domain. A warm migration of an LDom can take around some time. While the LDom is migrating, the LDom's software freezes the LDom and the application that runs inside the LDom.

You do not have to start and stop LLT and GAB. In a warm migration, LLT and GAB restart themselves gracefully.

To perform a warm migration for an LDom when VCS is installed in logical domains

  1. Stop VCS engine using hastop -local -force on the LDom system that you plan to migrate.

    Perform this step so that GAB does not have to kill the VCS engine process when the migration is complete. GAB wants all clients to reconfigure and restart when the configuration is not in sync with other members in the cluster.

  2. If CVM is configured inside the LDom, perform this step.

    Set LLT peerinact to 0 on all nodes in the cluster so that while the LDom is in migrating, the system is not thrown out of the cluster by the other members in the cluster. If the CVM stack is unconfigured, the applications can stop.

  3. If fencing is configured in single instance mode inside the LDom, perform this step.

    Unconfigure and unload the vxfen module in the LDom.

    Perform this step so that GAB does not panic the node when the LDom migration is complete.

  4. Migrate the logical domain from the control domain using the ldm interface. Wait for migration to complete.

  5. Perform this step if you performed step 3

    Load and configure vxfen module in the LDom.

  6. Perform this step if you performed step 2

    Reset LLT peerinact to the original value on all nodes in the cluster.

  7. Use the hastart command to start VCS engine inside the LDom.

VCS does not support LDom migration when VCS is installed in the control domain. If you plan to use the LDom migration feature in a VCS environment, however, follow these guidelines.

To migrate an LDOM when VCS is installed in the control domain

  1. Ensure that you have created an XML configuration file and have configured the CfgFile attribute of the LDom agent.

    Note:

    If you do not complete this step, VCS reports the status of the resource on the source node as UNKNOWN after the migration is complete.

  2. Before initiating migration, freeze the service group that contains LDom resources.

  3. Migrate the logical domain.

  4. After the migration is complete, VCS takes about five minutes to detect the online status of the service group. You may probe the resources on the target node to verify status.

  5. Unfreeze the service group.