Top
PRIMECLUSTER  Installation and Administration Guide 4.7
Appendix K Copying the Cluster System Environment > K.5 Changing Cluster System Settings > K.5.10 Changing the Settings of Cluster Application Information
PreviousNext

K.5.10 Changing the Settings of Cluster Application Information

Change the setting of the cluster application information.

K.5.10.1 When copying from a physical environment to a virtual environment

If you are copying to a virtual environment and need to change the configuration of a cluster applications, use the configuration changes in the documentation for your environment to rebuild the cluster application.

If you want to use the I/O fencing function in the destination VMware environment, you must configure the I/O fencing function for the cluster application that has registered Gds or Fsystem resources when you build the cluster application.

See "G.2.4.1 Setting Up I/O Fencing Function" in "Appendix G Using PRIMECLUSTER in a VMware Environment" to build a cluster application.

After building the cluster application, use the following procedure to cancel the automatic startup of RMS.

  1. Execute the following commands on all the nodes as required to set the automatic startup of RMS.

    # hvsetenv HV_RCSTART 1
    # hvsetenv HV_RCSTART
    1    <- Make sure that "1" is output.

  2. Start RMS. Execute the following command on any one node. 

    # hvcm -a

K.5.10.2 When copying to the same environment

Execute the following procedure. The procedures vary depending on whether GLS is used, the takeover network is used, or neither of them is used.

K.5.10.2.1 When Using GLS

  1. Change the cluster application information.

    1. In order to change these settings with the RMS Wizard, execute the hvw command on any node.

      Specify the < configuration filename > you recorded in "K.3.2 Checking RMS configuration file name".

      Example) If < configuration filename > is config:

      # hvw -n config

    2. Select "Application-Create" from "Main configuration menu".

      fuji4: Main configuration menu, current configuration: config
No RMS active in the cluster
 1) HELP                                10) Configuration-Remove
 2) QUIT                                11) Configuration-Freeze
 3) Application-Create                  12) Configuration-Thaw
 4) Application-Edit                    13) Configuration-Edit-Global-Settings
 5) Application-Remove                  14) Configuration-Consistency-Report
 6) Application-Clone                   15) Configuration-ScriptExecution
 7) Configuration-Generate              16) RMS-CreateMachine
 8) Configuration-Activate              17) RMS-RemoveMachine
 9) Configuration-Copy
Choose an action: 4

    3. Select "APP1" from "Application selection menu".

      Edit: Application selection menu (restricted):
1) HELP
2) QUIT
3) RETURN
4) OPTIONS
5) APP1
Application Name: 5

    4. If you changed any IP addresses for GLS according to step 8 of "K.5.5 Setting up in Single-User Mode," change the settings for the takeover IP address for Gls resources.

      1. Select "Gls:Global-Link-Services". 

        Settings of turnkey wizard "STANDBY" (APP1:consistent)
 1) HELP                                10) Enterprise-Postgres(-)     
 2) READONLY                            11) Symfoware(-)                      
 3) SAVE+EXIT                           12) Procedure:SystemState3(-)         
 4) -                                   13) Procedure:SystemState2(-)         
 5) ApplicationName=APP1                14) Gls:Global-Link-Services(Gls_APP1)
 6) Machines+Basics(app1)               15) IpAddresses(-)                    
 7) CommandLines(-)                     16) LocalFileSystems(-)               
 8) Procedure:Application(-)            17) Gds:Global-Disk-Services(-)
 9) Procedure:BasicApplication(-)      
Choose the setting to process: 14

      2. Select "TakeoverIpaddress" to change the takeover IP address.

        At the right side of the menu, the original IP address is displayed.

        Gls (Gls_APP1:consistent)
1) HELP                                 5) AdditionalTakeoverIpaddress        
2) NO-SAVE+EXIT                         6) TakeoverIpaddress[0]=N,10.34.214.185
3) SAVE+EXIT                            7) (Timeout=60)                       
4) REMOVE+EXIT                          
Choose the setting to process: 6

      3. The IP address used after modification is displayed in the menu.

        Select the modified takeover IP address.

        1) HELP                                 4) FREECHOICE            
2) RETURN                               5) SELECTED(10.34.214.185)
3) NONE                                 6) 10.34.214.195          
Choose a takeover IP address for Gls: 6

      4. Confirm that the selected IP address has been set and then select "SAVE+RETURN".

        Set a flag for takeover IP address: 10.34.214.195
Currently set: 
1) HELP                                 5) AUTORECOVER(A)
2) -                                    
3) SAVE+RETURN                          
4) DEFAULT                              
Choose additonally one of the flags: 3

      5. Select "SAVE+EXIT" to save the settings of Gls resources and exit the menu.

        Gls (Gls_APP1:consistent)
1) HELP                                 5) AdditionalTakeoverIpaddress        
2) NO-SAVE+EXIT                         6) TakeoverIpaddress[0]=N,10.34.214.195
3) SAVE+EXIT                            7) (Timeout=60)                       
4) REMOVE+EXIT                          
Choose the setting to process: 3

    5. Select "SAVE+EXIT" to return to the "Application selection menu." After that, select "RETURN" to return to the "Main configuration menu."

    6. Change the SysNode that configures a cluster application.

      1. Select "RMS-CreateMachine".

      2. After selecting "ALL-CF-HOSTS", make sure that all the SysNode names, created based on the changed CF node name "Current set", are displayed.

        At this point, the SysNode names, created based on the original CF node name, are also displayed simultaneously; however, unnecessary SysNode names are deleted in Step 9.

      3. Select "RETURN".

      4. Select "Application-Edit".

      5. Select "APP1".

      6. Select "Machines+Basics(app1)".

      7. Select "Machines[0]" and set the SysNode names based on the changed CF node name. After that, also select "Machines[1]" simultaneously.

      8. Select "SAVE+EXIT" > "SAVE+EXIT" > "RETURN" to return to the menu immediately after the hvw command was started.

      9. After selecting "RMS-RemoveMachine", select unnecessary SysNode names in sequence to let the SysNode names, created based on the changed CF node name "Current set", only be displayed, and then select "RETURN".

    7. Execute "Configuration-Generate" and "Configuration-Activate" in sequence and make sure that each operation ended properly.

    8. Select "QUIT" to exit the hvw command.

  2. Execute the following commands on all the nodes as required to set the automatic startup of RMS.

    # hvsetenv HV_RCSTART 1
    # hvsetenv HV_RCSTART
    1    <- Make sure that "1" is output.

  3. Start RMS. Execute the following command on any one node.

    # hvcm -a
K.5.10.2.2 When Using the Takeover Network

  1. Changing the IP addresses and host names of public LANs with IP address takeover and node name takeover.

    Change the /usr/opt/reliant/etc/hvipalias file on all the nodes.

    See

    For details on the setting contents in the "hvipalias" file, see "6.7.3.6 Setting Up Takeover Network Resources."

    Change the entries below as required.

    <node name> : Change the value in this filed to the changed CF node name.
    <takeover> :  If you changed any host names associated with takeover IP addresses, change this host name.

  2. Changing the cluster application information

    1. In order to change these settings with the RMS Wizard, execute the hvw command on any node.

      Specify the < configuration filename > you recorded in "K.3.2 Checking RMS configuration file name".

      Example) If < configuration filename > is config:

      # hvw -n config

    2. Select "Application-Create" from "Main configuration menu".

      fuji4: Main configuration menu, current configuration: config
No RMS active in the cluster
 1) HELP                                10) Configuration-Remove
 2) QUIT                                11) Configuration-Freeze
 3) Application-Create                  12) Configuration-Thaw
 4) Application-Edit                    13) Configuration-Edit-Global-Settings
 5) Application-Remove                  14) Configuration-Consistency-Report
 6) Application-Clone                   15) Configuration-ScriptExecution
 7) Configuration-Generate              16) RMS-CreateMachine
 8) Configuration-Activate              17) RMS-RemoveMachine
 9) Configuration-Copy
Choose an action: 4

    3. Select "APP1" from "Application selection menu".

      Edit: Application selection menu (restricted):
1) HELP
2) QUIT
3) RETURN
4) OPTIONS
5) APP1
Application Name: 5

    4. Change the settings for the host names in the takeover network resources.

      1. Select "IpAddresses" from "turnkey wizard". 

        Consistency check ...
Settings of turnkey wizard "STANDBY" (APP1:consistent)
 1) HELP                                10) Enterprise-Postgres(-)
 2) READONLY                            11) Symfoware(-)
 3) SAVE+EXIT                           12) Procedure:SystemState3(-)
 4) -                                   13) Procedure:SystemState2(-)
 5) ApplicationName=APP1                14) Gls:Global-Link-Services(-)
 6) Machines+Basics(app1)               15) IpAddresses(Adr_APP1)
 7) CommandLines(-)                     16) LocalFileSystems(-)
 8) Procedure:Application(-)            17) Gds:Global-Disk-Services(-)
 9) Procedure:BasicApplication(-)
Choose the setting to process: 15

      2. When the "Ipaddresses and ipaliase" menu is displayed, select the "Interfaces[X]" in which the host name to be changed is set.

        Consistency check ...
Yet to do: specify ping hosts of an interface using its P flag

Settings of application type "Ipaddress" (consistent)
 1) HELP                                 9) Interfaces[1]=V:takeover
 2) NO-SAVE+EXIT                        10) PingHostPool[0]=pinghost1
 3) SAVE+EXIT                           11) PingHostPool[1]=pinghost2
 4) ApplicationName=Adr_APP1            12) SubApplications[0]=Lfs_APP1
 5) AdditionalInterface                 13) (NeedAll=yes)
 6) AdditionalPingHost                  14) (Timeout=60)
 7) AdditionalSubApplication            15) (InterfaceFilter=)
 8) Interfaces[0]=V:tussd2af
Choose the setting to process:

      3. From the displayed menu, select the changed name of the host associated with the takeover IP address..

        (All host names in the "/etc/hosts" file are displayed in the menu.)

      4. Select "SAVE + RETURN".

      5. Check the setting value of "Interfaces [X]" to make sure that the host name at the modified position is correct.

        If there are multiple objects to be changed, repeat Steps 2 to 4 for each object.

        When all changes have been completed, select "SAVE + RETURN".

      6. Select "SAVE + EXIT".

      7. Select "RETURN".

    5. Change the SysNode that configures a cluster application.

      1. Select "RMS-CreateMachine".

      2. After selecting "ALL-CF-HOSTS", check that all the SysNode names, created based on the changed CF node name "Current set", are displayed.

        At this point, the SysNode names, created based on the original CF node name, are also displayed simultaneously; however, unnecessary SysNode names are deleted in Step 9.

      3. Select "RETURN".

      4. Select "Application-Edit".

      5. Select "APP1".

      6. Select "Machines+Basics(app1)".

      7. Select "Machines[0]" and set the SysNode names based on the changed CF node name. After that, also select "Machines[1]" simultaneously.

      8. Select "SAVE+EXIT" > "SAVE+EXIT" > "RETURN" to return to the menu immediately after the hvw command was started.

      9. After selecting "RMS-RemoveMachine", select unnecessary SysNode names in sequence to let the SysNode names, created based on the changed CF node name "Current set", only be displayed, and then select "RETURN".

    6. Execute the "Configuration-Generate" and "Configuration-Activate" in sequence to check that each operation ended properly.

    7. Select "QUIT" to exit the hvw command.

  3. Execute the following commands on all the nodes as required to set the automatic startup of RMS.

    # hvsetenv HV_RCSTART 1
    # hvsetenv HV_RCSTART
    1    <- Check "1" is output.

  4. Start RMS. Execute the following command on any one node.

    # hvcm -a
K.5.10.2.3 When Using neither GLS nor the Takeover Network

  1. Change the cluster application information.

    1. In order to change these settings with the RMS Wizard, execute the hvw command on any one node.

      Specify the < configuration filename > you recorded in "K.3.2 Checking RMS configuration file name".

      Example) If < configuration filename > is config:

      # hvw -n config

    2. Change the SysNode that configures a cluster application.

      1. Select "RMS-CreateMachine".

      2. After selecting "ALL-CF-HOSTS", make sure that all the SysNode names, created based on the changed CF node name "Current set", are displayed.

        At this point, the SysNode names, created based on the original CF node name, are also displayed simultaneously; however, unnecessary SysNode names are deleted in Step 9.

      3. Select "RETURN".

      4. Select "Application-Edit".

      5. Select "APP1".

      6. Select "Machines+Basics(app1)".

      7. Select "Machines[0]" and set the SysNode names based on the changed CF node name. After that, also select "Machines[1]" simultaneously.

      8. Select "SAVE+EXIT" > "SAVE+EXIT" > "RETURN" to return to the menu immediately after the hvw command was started.

      9. After selecting "RMS-RemoveMachine", select unnecessary SysNode names in sequence to let the SysNode names, created based on the changed CF node name "Current set", only be displayed, and then select "RETURN".

    3. Execute "Configuration-Generate" and "Configuration-Activate" in sequence and make sure that each operation ended properly.

    4. Select "QUIT" to exit the hvw command.

  2. Execute the following commands on all the nodes as required to set the automatic startup of RMS.

    # hvsetenv HV_RCSTART 1
    # hvsetenv HV_RCSTART
    1    <- Make sure that "1" is output.

  3. Start RMS. Execute the following command on any one node. 

    # hvcm -a
PreviousNext
Copyright Fujitsu Limited 2023-2024