Top
PRIMECLUSTER  Installation and Administration Guide 4.3
FUJITSU Software

L.3.2 Setup in Single-User Mode

Execute the following procedure on all the nodes of the copy destination.

  1. Start the system in single-user mode.

  2. Change the host name.

    Change the host name in "/etc/hosts", "/etc/sysconfig/network (for RHEL6)", and "/etc/hostname (for RHEL7)".

  3. Change the primary management sever, secondary management server, httpip, and mip in the Web-Based Admin View.

    1. Set the IP addresses of the primary management server and secondary management server.

      # /etc/opt/FJSVwvbs/etc/bin/wvSetparam primary-server <IP-address-of-primary-management-server>
      # /etc/opt/FJSVwvbs/etc/bin/wvSetparam secondary-server <IP-address-of-secondary-management-server>
    2. Set httpip.

      # /etc/opt/FJSVwvbs/etc/bin/wvSetparam httpip <IP-address-used-for-a-client>
    3. Set mip.

      # /etc/opt/FJSVwvbs/etc/bin/wvSetparam mip <IP-address-for-identifying-own-host>
  4. Change the CF node name, CIP/SysNode name, and the cluster name.

    Note

    For the naming conventions (cluster name and CF node name), see "5.1.1 Setting Up CF and CIP."

    1. Change the string of the CF node name within the CF node name and the CIP/SysNode name that are described in /etc/cip.cf.

      [Before change]
      fuji2       fuji2RMS:netmask:255.255.255.0
      fuji3       fuji3RMS:netmask:255.255.255.0
      [After change]
      fuji4       fuji4RMS:netmask:255.255.255.0
      fuji5       fuji5RMS:netmask:255.255.255.0
    2. Change the string of the CF node name within the CIP/SysNode name that are described in /etc/hosts.

      [Before change]
      192.168.0.1     fuji2RMS
      192.168.0.2     fuji3RMS
      [After change]
      192.168.0.3     fuji4RMS
      192.168.0.4     fuji5RMS
    3. Change the CF node name and cluster name described in /etc/default/cluster.

      [Before change]
      nodename fuji2
      clustername PRIMECLUSTER1
      device eth2
      device eth3
      [After change]
      nodename fuji4
      clustername PRIMECLUSTER2
      device eth2
      device eth3
  5. Cancel the SF settings.

    Save "/etc/opt/SMAW/SMAWsf/rcsd.cfg" to the rcsd.org file.

    # mv /etc/opt/SMAW/SMAWsf/rcsd.cfg /etc/opt/SMAW/SMAWsf/rcsd.org
  6. Change the node name of the Cluster Resource Management Facility.

    Execute the following command to change the node name of the Cluster Resource Management Facility.

    # /etc/opt/FJSVcluster/bin/clchgnodename
  7. Delete the information in the management partition of GFS.

    Note

    This procedure is unnecessary when the GFS Shared File System is not being used.

    Delete the information in the management partition of the GFS Shared File System. Execute the following command on all the nodes.

    # rm /var/opt/FJSVsfcfs/sfcfsrm.conf
  8. Change the GDS settings.

    • When the mirroring among servers is not used

      Delete the local class and shared class definitions of GDS. Perform the following procedure on all the nodes.

      1. Delete the settings of class name in the "/etc/opt/FJSVsdx/sysdb.d/class.db" file.

        ...
        Class1          <- Delete all the lines of class name
        ...
      2. Delete all files named with the class name in the "/etc/opt/FJSVsdx/sysdb.d" directory.

        # cd /etc/opt/FJSVsdx/sysdb.d
        # rm Class1
      3. Delete all configuration information in the "/etc/sysconfig/devlabel" file.

        ...
        /etc/opt/FJSVsdx/.devlabel/Class1/sdx_dev...    <- Delete this line
        ...
      4. Delete all the directories named with the class name in "/etc/opt/FJSVsdx/.devlabel" directory.

        # cd /etc/opt/FJSVsdx/.devlabel
        # rm -rf Class1
    • When the mirroring among servers is used

      Change the settings for iSCSI targets used in GDS. Perform the following procedure on all the nodes.

      1. Delete the registered target portal.

        Example: The IP address used for the mirroring among servers of the copy source node is "192.168.56.20".

        # iscsiadm -m discovery --op delete --portal 192.168.56.20
      2. Start the network service.

        # service network start
      3. Change the IP address entries in /etc/tgt/targets.conf and the path of the by-id link.

        Example: Change the IP address to "192.168.56.21" and "192.168.56.11", and the path of the by-id link to " /dev/disk/by-id/scsi-3500000e111c56611".

      [Before change]
      # GDS netmirror definition start
      <target target-0101>
      initiator-address 192.168.56.20
      initiator-address 192.168.56.10
      write-cache off
       <backing-store /dev/disk/by-id/scsi-3500000e111e68e00>
        scsi_id SDX-01
       </backing-store>
      </target>
      # GDS netmirror definition end
      [After change]
      # GDS netmirror definition start
      <target target-0101>
      initiator-address 192.168.56.21
      initiator-address 192.168.56.11
      write-cache off
       <backing-store /dev/disk/by-id/scsi-3500000e111c56611>
        scsi_id SDX-01
       </backing-store>
      </target>
      # GDS netmirror definition end
      1. Start the tgtd service.

        # service tgtd start
      2. Establish the iSCSI session.

        For the procedure, see "Establishing iSCSI Session" in "PRIMECLUSTER Global Disk Services Configuration and Administration Guide."

  9. Prepare for changing the GLS settings.

    If you are using GLS, perform the following:

    1. Correct the "/etc/hosts" file

      [Before change]
      10.34.214.185 takeoverIP # Virtual IP
      10.34.214.181 primecl01  # primecl01 physical IP
      10.34.214.182 primecl02  # primecl02 physical IP
      10.34.214.188 swhub1     # primary HUB IP
      10.34.214.189 swhub2     # secondary HUB IP
      [After change]
      10.34.214.195 takeoverIP2 # Virtual IP
      10.34.214.191 primecl03   # primecl03 physical IP
      10.34.214.192 primecl04   # primecl04 physical IP
      10.34.214.188 swhub1      # primary HUB IP
      10.34.214.189 swhub2      # secondary HUB IP
    2. Isolate the copy destination system so that there are no IP addresses in duplicate with the copy source system.

      Beforehand, make sure that the NIC cables are disconnected or the copy source is stopped, or connect from the copy source system to an isolated network, taking care that there are no IP addresses in duplicate with the copy source system.

  10. Restrict the automatic startup of RMS.

    Check the settings of the current automatic startup of RMS and execute the following command according to the settings.

    # hvsetenv HV_RCSTART
    1 <- Check this value
    • If "0" is set, the automatic startup of RMS has been restricted. Go to Step 11.

    • If "1" is set, execute the following commands to restrict the automatic startup of RMS.

      # hvsetenv HV_RCSTART 0
      # hvsetenv HV_RCSTART
      0    <- Check "0" is output
  11. After completing above procedure on all the nodes of the copy destination, start up all the nodes in multi-user mode.