Top
PRIMECLUSTER  Installation and Administration Guide4.5
FUJITSU Software

17.3.2 Performing Cold Migration of the Cluster on a Control Domain

17.3.2.1 Operation before Performing Cold Migration

This section describes the operation before performing the Cold Migration in an Oracle VM Server for SPARC Environment.

Note

  • Prerequisites in "17.2.1 Performing Live Migration of the Cluster on the Control Domains" are required before performing this operation.

  • Make sure that following items are consistent on all control domains of the target clusters: a combination of a user name and password for the XSCF that is registered in the shutdown facility, and the connection method to the XSCF.

  • Check that the following settings have been performed for the destination servers:

  • Before performing this operation, make sure that the target guest domain to be migrated is stopped.
    Use the ldm list-domain command to check if STATE is displayed as the bound state.
    If the state of STATE is inactive, change its state to bound. The configuration information of the logical domains can be identified by XSCF when the STATE is in the bound state.

  • If you cancel the Cold Migration after performing this operation, "17.3.2.2 Operation after Performing Cold Migration" is unnecessary.

  1. Changing the cluster configuration (control domain)

    Change the cluster configuration before performing the Cold Migration.

    Execute the following command on the cluster nodes of the source control domain.

    When the guest domain is stopped, check that the command exists with the return value of 1.

    # /etc/opt/FJSVcluster/bin/clovmmigrate -p source-ldom
    source-ldom

    The guest domain name to be migrated.

    By executing this command, you can check if the guest domain specified for source-ldom is stopped.

17.3.2.2 Operation after Performing Cold Migration

This section describes the operation after performing the Cold Migration in an Oracle VM Server for SPARC Environment.

Note

  • These steps are unnecessary if you cancel the Cold Migration after performing "17.3.2.1 Operation before Performing Cold Migration."

  • Perform steps 1 through 3 on a control domain.

  • Perform step 4 on a guest domain.

  • Before performing this operation, the configuration information of the saved logical domain needs to be less than six or less. Execute the following command to check it. Also, check that "config_tmp" does not exist in the saved configuration information name of the logical domains.

    # ldm list-spconfig

    If the configuration information of the saved logical domain is 7 or more, execute the following command to delete the configuration information to make them 6 or less.

    # ldm remove-spconfig configuration name

    If "config_tmp" exists in the configuration name of the logical domain, execute the following command to delete it.

    # ldm remove-spconfig config_tmp

    For details on the configuration information of the logical domain, see "Operations and Commands Related to Logical Domain Configurations" in "Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 Domain Configuration Guide."

  1. Changing the cluster configuration (control domain)

    Change the cluster configuration after performing the Cold Migration.

    Execute the following command on the cluster nodes of the source control domain.

    When the guest domain is stopped, the return value of the command is 1.

    # /etc/opt/FJSVcluster/bin/clovmmigrate -u source-ldom target-host
    source-ldom

    The target guest domain name to be migrated

    target-host

    The host name registered to the IP address or the /etc/inet/hosts file of the destination control domain

    If you execute this command, information of the logical domains is saved both by the source control domain and the destination control domain.

  2. Checking the state of the guest domain and saving the configuration information (control domain)

    Execute the following command on the destination control domain to check the state of the guest domain that was migrated by the Cold Migration.

    # ldm list-domain

    If the migrated guest domain is in the bound state, proceed to the following steps.
    If the migrated guest domain is in the inactive state, change its state to bound. After changing the state of the guest domain to bound, save the configuration information of the logical domains on the source control domain and the destination control domain. The configuration information of the logical domains can be identified by XSCF when the guest domain is in the bound state. For details, see "Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 System Operation and Administration Guide."

  3. Starting the guest domain (control domain)

    Start the stopped guest domain that was migrated by the Cold Migration.
    When the guest domain is started, the following cluster configuration is changed on all nodes of the cluster between guests.

    • Change the setting of the shutdown facility (IP address of XSCF-LAN#0, IP address of XSCF-LAN#1, and the SF weight)

  4. Checking the state of the shutdown facility (guest domain)

    Execute the following commands on each node of a guest domain to check if the cluster is configured correctly after the Cold Migration.

    # /etc/opt/FJSVcluster/bin/clsnmpsetup -l
    # /opt/SMAW/bin/sdtool -s

    Note

    If TestFailed or InitFailed is displayed, the setting of the shutdown facility could have been unchanged.
    If the message 7245 is output in the /var/adm/messages file, the first SSH connection to XSCF has not completed yet. For details, see "PRIMECLUSTER Messages."

    For all other circumstances, go back to step 1 and try again.

    Example: When the Migration is performed for guest 2 in the two-node cluster between guest domains ("Figure 17.1 Cluster configuration example")

    guest2 # /etc/opt/FJSVcluster/bin/clsnmpsetup -l
    device-name cluster-host-name  PPAR-ID  domain-name  IP-address1  IP-address2  user-name  connection-type
    -------------------------------------------------------------------------------------------------------------------
    xscf        cfguest1             0        guest1       10.20.30.71  10.20.40.71  xuser   ssh
    xscf        cfguest2             1        guest2       10.20.30.73  10.20.40.73  xuser   ssh
    guest2 #                         ^^                    ^^^^^^^^^^^^^^^^^^^^^^^^
    guest2 #                                                The target XSCF IP address to be migrated
    guest2 #                        The target PPAR-ID to be migrated
    guest2 # /opt/SMAW/bin/sdtool -s
    Cluster Host      Agent                SA State      Shut State  Test State  Init State
    ------------      -----                --------      ----------  ----------  ----------
    cfguest1          SA_xscfsnmpg0p.so    Idle          Unknown     TestWorked  InitWorked
    cfguest1          SA_xscfsnmpg1p.so    Idle          Unknown     TestWorked  InitWorked
    cfguest1          SA_xscfsnmpg0r.so    Idle          Unknown     TestWorked  InitWorked
    cfguest1          SA_xscfsnmpg1r.so    Idle          Unknown     TestWorked  InitWorked
    cfguest2          SA_xscfsnmpg0p.so    Idle          Unknown     TestWorked  InitWorked
    cfguest2          SA_xscfsnmpg1p.so    Idle          Unknown     TestWorked  InitWorked
    cfguest2          SA_xscfsnmpg0r.so    Idle          Unknown     TestWorked  InitWorked
    cfguest2          SA_xscfsnmpg1r.so    Idle          Unknown     TestWorked  InitWorked
    guest2 #