Top
ServerView Resource Coordinator VE Installation Guide
Appendix B Manager Cluster Operation Settings and Deletion > B.3 Configuration > B.3.1 Configuration [Windows]
PreviousNext

B.3.1 Configuration [Windows]

Perform setup on the admin server.
The flow of setup is as shown below.

Figure B.1 Manager Service Setup Flow


Setup of managers as cluster services (cluster applications) is performed using the following procedure.
This explanation assumes that the shared disk for managers has been allocated to the primary node.


Create Cluster Resources

  1. Store the generic scripts.

    Store the generic scripts created in "B.2.1 Preparations" in the manager installation folders on the primary node and the second node.
    After storing the scripts, set the access rights for the script files.
    Use the command prompt to execute the following command on each script file.

    >cacls File_name /P "NT AUTHORITY\SYSTEM:F" "BUILTIN\Administrators:F" <RETURN>

  2. Open the [Failover Cluster Management] window and connect to the cluster system.

  3. Configure a manager "service or application".

    1. Right-click [Services and applications] on the [Failover Cluster Management] tree, and select [More Actions]-[Create Empty Service or Application].

      [New Service or Application] will be created under [Services and Applications].

    2. Right-click [New Service or Application], and select [Properties] from the displayed menu.

      The [New Service or Application Properties] dialog is displayed.

    3. Change the "Name" on the [General] tab, select the resource name of the primary node from "Preferred owners", and click <Apply>.

    4. When the settings have been applied, click <OK>.

    From this point, this explanation assumes that the name of the "service or application" for Resource Coordinator VE has been configured as "RC-manager".

  4. Allocate the shared disk to the manager "service or application".

    1. Right-click [Services and Applications] - [Rc-manager], and select [Add Storage] from the displayed menu.

      The [Add Storage] window will be displayed.

    2. From the "Available disks:", select the shared disk for managers and click <OK>.

  5. Allocate the IP address to the manager "service or application".

    1. Right-click [Services and Applications] - [Rc-manager], select [Add Resource] - [Other Resources] - [4 - Add IP Address] from the displayed menu.

      "IP Address: <Not configured>" will be created in the "Other Resources" of the "Summary of RC-manager" displayed in the center of the window.

    2. Right-click "IP Address: <Not configured>", and select [Properties] from the displayed menu.

      The [IP Address: <Not configured> Properties] window is displayed.

    3. Configure the following parameters on the [General] tab and then click <Apply>.

      Resource Name

      Set the network name prepared in "B.2.1 Preparations".

      Network

      Select the network to use from the pull-down menu.

      Static IP Address

      Set the IP address prepared in "B.2.1 Preparations".

    4. When the settings have been applied, click <OK>.

    Note

    When a network other than the admin LAN has been prepared for RC console access, repeat steps a. to d. of the process.


Copy Dynamic Disk Files

Copy the files from the dynamic disk of the manager on the primary node to the shared disk for managers.

  1. Use Explorer to create the "Drive_name:\RCoordinator\" folder on the shared disk.

  2. Use Explorer to copy the files and folders from the local disk of the primary node to the folder on the shared disk.

    Local disk (Source)

    Shared disk (Target)

    Installation_folder\Manager\etc\opt\FJSVssmgr\current\certificate

    Drive_name:\RCoordinator\certificate

    Installation_folder\Manager\Rails\config\rcx_secret.key

    Drive_name:\RCoordinator\rcx_secret.key

    Installation_folder\Manager\Rails\db

    Drive_name:\RCoordinator\db

    Installation_folder\Manager\Rails\log

    Drive_name:\RCoordinator\log

    Installation_folder\Manager\Rails\tmp

    Drive_name:\RCoordinator\tmp

    Installation_folder\Manager\sys\apache\conf

    Drive_name:\RCoordinator\conf

    Installation_folder\Manager\sys\apache\logs

    Drive_name:\RCoordinator\logs

    Installation_folder\Manager\var

    Drive_name:\RCoordinator\var

    Installation_folder\ScwPro\Bin\ipTable.dat (*1)

    Drive_name:\RCoordinator\ipTable.dat

    Installation_folder\ScwPro\scwdb (*1)

    Drive_name:\RCoordinator\scwdb

    Installation_folder\ScwPro\tftp\rcbootimg (*1)

    Drive_name:\RCoordinator\rcbootimg

    User_specified_folder\ScwPro\depot (*1)

    Drive_name:\RCoordinator\depot

    *1: Not necessary when ServerView Deployment Manager is used in the same subnet.

  3. Release the sharing settings of the following folder:

    Not necessary when ServerView Deployment Manager is used in the same subnet.

    • Installation_folder\ScwPro\scwdb

      Execute the following command using the command prompt:

      >net share ScwDB$ /DELETE <RETURN>

  4. Use Explorer to change the names of the folders below that were copied.

    • Installation_folder\Manager\etc\opt\FJSVssmgr\current\certificate

    • Installation_folder\Manager\Rails\config\rcx_secret.key

    • Installation_folder\Manager\Rails\db

    • Installation_folder\Manager\Rails\log

    • Installation_folder\Manager\Rails\tmp

    • Installation_folder\Manager\sys\apache\conf

    • Installation_folder\Manager\sys\apache\logs

    • Installation_folder\Manager\var

    • Installation_folder\ScwPro\Bin\ipTable.dat (*1)

    • Installation_folder\ScwPro\scwdb (*1)

    • Installation_folder\ScwPro\tftp\rcbootimg (*1)

    *1: Not necessary when ServerView Deployment Manager is used in the same subnet.

    Note

    When folders or files are in use by another program, attempts to change folder names and file names may fail.
    If attempts to change names fail, change the names after rebooting the server.

  5. Delete the following file from the shared disk:

    • Drive_name:\RCoordinator\db\rmc_key


Configure Folders on the Shared Disk (Primary node)

  1. On the primary node, configure symbolic links to the files and folders on the shared disk.

    Use the command prompt to configure a symbolic link from the files and folders on the local disk of the primary node to the files and folders on the shared disk.

    Execute the following command.

    • Folder

      >mklink /d Link_source Link_target <RETURN>

    • File

      >mklink Link_source Link_target <RETURN>

      Specify the folders or files copied in "Copying Dynamic Disk Files" for Link_source.

      Specify the folders or files copied to the shared disk in "Copying Dynamic Disk Files" for Link_target.

    The folders and files to specify are as given below:

    Table B.1 Folders to Specify

    Local disk (Link source)

    Shared disk (Link target)

    Installation_folder\Manager\etc\opt\FJSVssmgr\current\certificate

    Drive_name:\RCoordinator\certificate

    Installation_folder\Manager\Rails\db

    Drive_name:\RCoordinator\db

    Installation_folder\Manager\Rails\log

    Drive_name:\RCoordinator\log

    Installation_folder\Manager\Rails\tmp

    Drive_name:\RCoordinator\tmp

    Installation_folder\Manager\sys\apache\conf

    Drive_name:\RCoordinator\conf

    Installation_folder\Manager\sys\apache\logs

    Drive_name:\RCoordinator\logs

    Installation_folder\Manager\var

    Drive_name:\RCoordinator\var

    Installation_folder\ScwPro\scwdb (*1)

    Drive_name:\RCoordinator\scwdb

    Installation_folder\ScwPro\tftp\rcbootimg (*1)

    Drive_name:\RCoordinator\rcbootimg

    *1: Not necessary when ServerView Deployment Manager is used in the same subnet.

    Table B.2 Files to Specify

    Local disk (Link source)

    Shared disk (Link target)

    Installation_folder\Manager\Rails\config\rcx_secret.key

    Drive_name:\RCoordinator\rcx_secret.key

    Installation_folder\ScwPro\Bin\ipTable.dat (*1)

    Drive_name:\RCoordinator\ipTable.dat

    *1: Not necessary when ServerView Deployment Manager is used in the same subnet.

    Note

    Before executing the above command, move to a folder one level higher than the link source folder.

    Example

    When specifying a link from "Installation_folder\Manager\sys\apache\logs" on the local disk to "Drive_name:\RCoordinator\logs" on the shared disk

    >cd Installation_folder\Manager\sys\apache <RETURN>
    >mklink /d logs Drive_name:\RCoordinator\logs <RETURN>

  2. Change the registry of the primary node.

    Not necessary when ServerView Deployment Manager is used in the same subnet.

    1. Backup the registry to be changed.

      Execute the following command.

      • x64

        >reg save HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Fujitsu\SystemcastWizard scw.reg <RETURN>

      • x86

        >reg save HKEY_LOCAL_MACHINE\SOFTWARE\Fujitsu\SystemcastWizard scw.reg <RETURN>

    2. Change the registry.

      Execute the following command.

      • x64

        >reg add HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Fujitsu\SystemcastWizard\ResourceDepot /v BasePath /d Drive_name:\RCoordinator\depot\ /f <RETURN>

        >reg add HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Fujitsu\SystemcastWizard\DatabaseBroker\Default /v LocalPath /d Drive_name:\RCoordinator\scwdb /f <RETURN>

        >reg add HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Fujitsu\SystemcastWizard\DHCP /v IPtableFilePath /d Drive_name:\RCoordinator /f <RETURN>

      • x86

        >reg add HKEY_LOCAL_MACHINE\SOFTWARE\Fujitsu\SystemcastWizard\ResourceDepot /v BasePath /d Drive_name:\RCoordinator\depot\ /f <RETURN>

        >reg add HKEY_LOCAL_MACHINE\SOFTWARE\Fujitsu\SystemcastWizard\DatabaseBroker\Default /v LocalPath /d Drive_name:\RCoordinator\scwdb /f <RETURN>

        >reg add HKEY_LOCAL_MACHINE\SOFTWARE\Fujitsu\SystemcastWizard\DHCP /v IPtableFilePath /d Drive_name:\RCoordinator /f <RETURN>

        Change Drive_name based on your actual environment.

    3. If changing the registry fails, restore the registry.

      Execute the following command.

      • x64

        >reg restore HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Fujitsu\SystemcastWizard scw.reg <RETURN>

      • x86

        >reg restore HKEY_LOCAL_MACHINE\SOFTWARE\Fujitsu\SystemcastWizard scw.reg <RETURN>

      Note

      Do not use the backup registry file created using this procedure for any other purposes.


Configure Access Authority for Folders and Files

Change the Manager Admin LAN IP Address (Primary node)

Change the admin LAN IP address of the manager.

Specify the admin LAN IP address set in step 5. of "Create Cluster Resources".

  1. Bring the admin LAN IP address for the manager "service or application" online.

  2. Execute the following command using the command prompt of the primary node:

    >Installation_folder\Manager\bin\rcxadm mgrctl modify -ip IP_address <RETURN>

  3. Allocate the shared disk to the secondary node.

    Right-click [Services and applications]-[RC-manager] on the Failover Cluster Manager tree, and select [Move this service or application to another node]-[1- Move to node node_name] from the displayed menu.

    The name of the secondary node is displayed for node_name.


Configure Folders on the Shared Disk (Secondary node)

Change the Manager Admin LAN IP Address (Secondary node)

Change the admin LAN IP address of the manager.

Specify the admin LAN IP address set in step 5. of "Create Cluster Resources".

  1. Execute the following command using the command prompt of the secondary node:

    >Installation_folder\Manager\bin\rcxadm mgrctl modify -ip IP_address <RETURN>

  2. Allocate the shared disk to the primary node.

    Right-click [Services and Applications]-[RC-manager] on the Failover Cluster Management tree, and select [Move this service or application to another node]-[1- Move to node node_name] from the displayed menu.
    The name of the primary node is displayed for node_name.


Register Service Resources

  1. Add the manager service to the manager "service or application".
    Add the following five services.

    • Resource Coordinator Manager

    • Resource Coordinator Task Manager

    • Deployment Service (*1)

    • TFTP Service (*1)

    • PXE Services (*1)

    *1: Not necessary when ServerView Deployment Manager is used in the same subnet.

    Perform the following procedure for each of the above services:

    1. Right-click [Services and Applications]-[RC-manager] on the Failover Cluster Management tree, and select [Add a resource]-[4 - Generic Service] from the displayed menu.

      The [New Resource Wizard] window will be displayed.

    2. Select the above services on "Select Service" and click <Next>>.

      "Confirmation" will be displayed.

    3. Check the information displayed for "Confirmation" and click <Next>>.

      If configuration is successful, the "Summary" window will be displayed.

    4. Click <Finish>.

      After completing the configuration of all of the services, check that the added services are displayed in "Other Resources" of the "Summary of RC-manager" displayed in the center of the window.

  2. Configure registry replication as a service in the manager "service or application".

    Not necessary when ServerView Deployment Manager is used in the same subnet.

    Configure the registry replication of resources based on the following table.

    • x64

      Resource for Configuration

      Registry Key

      Deployment Service

      [HKEY_LOCAL_MACHINE\]SOFTWARE\Wow6432Node\Fujitsu\SystemcastWizard\ResourceDepot

      [HKEY_LOCAL_MACHINE\]SOFTWARE\Wow6432Node\Fujitsu\SystemcastWizard\DatabaseBroker\Default

      PXE Services

      [HKEY_LOCAL_MACHINE\]SOFTWARE\Wow6432Node\Fujitsu\SystemcastWizard\DHCP

      [HKEY_LOCAL_MACHINE\]SOFTWARE\Wow6432Node\Fujitsu\SystemcastWizard\PXE\ClientBoot\

    • x86

      Resource for Configuration

      Registry Key

      Deployment Service

      [HKEY_LOCAL_MACHINE\]SOFTWARE\Fujitsu\SystemcastWizard\ResourceDepot

      [HKEY_LOCAL_MACHINE\]SOFTWARE\Fujitsu\SystemcastWizard\DatabaseBroker\Default

      PXE Services

      [HKEY_LOCAL_MACHINE\]SOFTWARE\Fujitsu\SystemcastWizard\DHCP

      [HKEY_LOCAL_MACHINE\]SOFTWARE\Fujitsu\SystemcastWizard\PXE\ClientBoot\

      During configuration, enter the section of the registry keys after the brackets ([ ]).

    Perform the following procedure for each of the above resources:

    1. Right-click the target resource on "Other Resources" on the "Summary of RC-manager" displayed in the middle of the [Failover Cluster Manager] window, and select [Properties] from the displayed menu.

      The [target_resource Properties] window will be displayed.

    2. Click <Add> on the [Registry Replication] tab.

      The [Registry Key] window will be displayed.

    3. Configure the above registry keys on "Root Registry Keys" and click <OK>.

      When configuring the second registry key, repeat steps b. and c.

    4. After configuration of the registry keys is complete, click <Apply>.

    5. When the settings have been applied, click <OK> and close the dialog.

  3. Add the generic scripts to the manager "service or application".

    Add the three generic scripts from the script files that were created in step 1. of "Create Cluster Resources". Perform the following procedure for each generic script.

    1. Right-click [Services and Applications]-[RC-manager] on the Failover Cluster Management tree, and select [Add a resource]-[3 - Generic Script] from the displayed menu.

      The [New Resource Wizard] window will be displayed.

    2. Set the script files created in step 1. of "Create Cluster Resources" in the "Script File Path" of the "Generic Script Info", and click <Next>>.

      "Confirmation" will be displayed.

    3. Check the information displayed for "Confirmation" and click <Next>>.

      If configuration is successful, the "Summary" will be displayed.

    4. Click <Finish>.

      After completing the configuration of all of the generic scripts, check that the added generic scripts are displayed in "Other Resources" of the "Summary of RC-manager" displayed in the center of the window.

  4. Configure the dependencies of the resources of the manager "service or application".

    Configure the dependencies of resources based on the following table.

    Table B.5 Configuring Resource Dependencies

    Resource for Configuration

    Dependent Resource

    Resource Coordinator Manager

    Shared Disks

    Resource Coordinator Task Manager

    Shared Disks

    Resource Coordinator Sub Web Server (Mongrel) Script

    Resource Coordinator Task Manager

    Resource Coordinator Sub Web Server (Mongrel2) Script

    Resource Coordinator Task Manager

    Resource Coordinator Web Server (Apache) Script

    Shared Disks

    Deployment Service (*1)

    PXE Services

    TFTP Service (*1)

    Deployment Service

    PXE Services (*1)

    Admin LAN IP Address

    *1: Not necessary when ServerView Deployment Manager is used in the same subnet.

    Perform the following procedure for each of the above resources:

    1. Right-click the target resource on "Other Resources" on the "Summary of RC-manager" displayed in the middle of the [Failover Cluster Manager] window, and select [Properties] from the displayed menu.

      The [target_resource Properties] window will be displayed.

    2. From the "Resource" of the [Dependencies] tab select the name of the "Dependent Resource" from "Table B.5 Configuring Resource Dependencies" and click <Apply>.

    3. When the settings have been applied, click <OK>.


Start Cluster Services

  1. Right-click [Services and Applications]-[RC-manager] on the Failover Cluster Management tree, and select [Bring this service or application online] from the displayed menu.

    Confirm that all resources have been brought online.

  2. Switch the manager "service or application" to the secondary node.

    Confirm that all resources of the secondary node have been brought online.

PreviousNext
Copyright 2007-2010 FUJITSU LIMITED