test

Sun Cluster Data Service for SWIFTAlliance Gateway Guide for Solaris OS

Installing and Configuring Sun Cluster HA for SWIFTAlliance Gateway

This chapter explains how to install and configure Sun Cluster HA for SWIFTAlliance Gateway.

This chapter contains the following sections.

Sun Cluster HA for SWIFTAlliance Gateway Overview

The Sun Cluster HA for SWIFTAlliance Gateway data service provides a mechanism for orderly startup, shutdown, fault monitoring, switchover, and failover of the Sun Cluster data service.

Sun Cluster HA for SWIFTAlliance Gateway provides software for fault monitoring by checking the status of the Alliance Gateway service. The values `running' and `partial' are considered healthy; values other than these will force a restart or failover to another node in the cluster. By accepting a partial status, operators may temporarily disable portions of the service without informing the cluster. You do not need an user id and password for monitoring.

For conceptual information about failover data services and scalable data services, see Sun Cluster Concepts Guide for Solaris OS.

Each component of SWIFTAlliance Gateway has a data service that protects the component when the component is configured in a Sun Cluster environment. See the following table.

Table 1 Protection of SWIFTAlliance Gateway Components

Component 

Protected by 

SWIFTNet Link 

Sun Cluster HA for SWIFTAlliance Gateway 

SWIFTAlliance Gateway 

Sun Cluster HA for SWIFTAlliance Gateway 

Overview of Installation and Configuration Process for Sun Cluster HA for SWIFTAlliance Gateway

The following table summarizes the tasks for installing and configuring Sun Cluster HA for SWIFTAlliance Gateway and provides cross-references to detailed instructions for performing these tasks. Perform the tasks in the order that they are listed in the table.

Table 2 Tasks for Installing and Configuring Sun Cluster HA for SWIFTAlliance Gateway

Task 

Instructions 

Plan the SWIFTAlliance Gateway installation 

Planning the Sun Cluster HA for SWIFTAlliance Gateway Installation and Configuration

Install and configure SWIFTAlliance Gateway 

Installing and Configuring SWIFTAlliance Gateway

Install the Sun Cluster HA for SWIFTAlliance Gateway packages 

Installing and Configuring SWIFTAlliance Gateway

Register the Sun Cluster HA for SWIFTAlliance Gateway data service and configure the cluster for the data service 

Registering and Configuring the Sun Cluster HA for SWIFTAlliance Gateway

Verify Sun Cluster HA for SWIFTAlliance Gateway 

Verifying the Sun Cluster HA for SWIFTAlliance Gateway Installation and Configuration

Tune the Sun Cluster HA for SWIFTAlliance Gateway fault monitor 

Tuning the Sun Cluster HA for SWIFTAlliance Gateway Fault Monitor

(Optional) Debug Sun Cluster HA for SWIFTAlliance Gateway 

Debugging Sun Cluster HA for SWIFTAlliance Gateway

Planning the Sun Cluster HA for SWIFTAlliance Gateway Installation and Configuration

This section contains the information that you need to plan your Sun Cluster HA for SWIFTAlliance Gateway installation and configuration.

Note –

Before you begin, consult your SWIFTAlliance Gateway documentation for configuration restrictions and requirements that are not imposed by Sun Cluster software. For information about restrictions that the Sun Cluster software imposes, see the Sun Cluster documentation.

Configuration Restrictions

The configuration restrictions in this section apply only to Sun Cluster HA for SWIFTAlliance Gateway.

Caution – Caution –

If your data service configuration does not conform to these restrictions, the data service configuration might not be supported.

For restrictions that apply to all data services, see Sun Cluster 3.1 8/05 Release Notes for Solaris OS.

Configuration Requirements

The configuration requirements in this section apply only to Sun Cluster HA for SWIFTAlliance Gateway.

Caution – Caution –

If your data service configuration does not satisfy these requirements, the data service configuration might not be supported.

For requirements that apply to all data services, see Configuration Guidelines for Sun Cluster Data Services in Sun Cluster Data Services Planning and Administration Guide for Solaris OS.

Configuration Considerations

The configuration considerations in the subsections that follow affect the installation and configuration of Sun Cluster HA for SWIFTAlliance Gateway.

Resource Dependencies

Configure Sun Cluster HA for SWIFTAlliance Gateway to protect a Sun Cluster instance and its respective components. The following table outlines these components and their dependencies.

Table 3 Sun Cluster Components

Component 

Dependencies 

SWIFTAlliance Gateway 

This component includes the SWIFTNet Link instance. 

  • SUNW.LogicalHost resource

  • SUNW.HAStoragePlus resource

Configuration Files and Registration Script

The Sun Cluster component has two configuration files and a registration script.

/opt/SUNWscsag/etc/settings

This configuration file contains settings to enable the data service to find the correct instance of SWIFTAlliance Gateway and the necessary user and password combination. 

/opt/SUNWscsag/util/sag_config

This configuration file contains settings to register the data service and the application in the Sun Cluster framework. 

/opt/SUNWscsag/util/sag_register

This registration script enables you to register the data service. 

Configuration Planning Questions

Use the questions in this section to plan the installation and configuration of Sun Cluster HA for SWIFTAlliance Gateway. Write the answers to these questions in the space that is provided on the data service worksheets in Configuration Worksheets in Sun Cluster Data Services Planning and Administration Guide for Solaris OS.

Installing and Configuring SWIFTAlliance Gateway

To enable Sun Cluster HA for SWIFTAlliance Gateway to make SWIFTAlliance Gateway highly available, additional installation and configuration operations are required. These operations supplement the standard installation and standard configuration of SWIFTAlliance Gateway.

During a standard installation, SWIFTAlliance Gateway is installed with a physical hostname. To enable SWIFTAlliance Gateway to run in a cluster, you must modify SWIFTAlliance Gateway to use a logical hostname.

For information about the standard installation and standard configuration of SWIFTAlliance Gateway, see the appropriate documentation available in the SWIFTAlliance Gateway CD-ROM.

To perform this procedure, you need the server root directory (the path to the application binaries). You can install the binaries on the local disks or on the cluster file system. For a discussion of the advantages and disadvantages of each location, see Chapter 1, Planning for Sun Cluster Data Services, in Sun Cluster Data Services Planning and Administration Guide for Solaris OS.

ProcedureHow to Install and Configure SWIFTAlliance Gateway

  1. Create a resource group for SWIFTAlliance Gateway.


    # scrgadm -a -g sag-rg

  2. Create a logical host.

    A logical host is required before you install SWIFTAlliance Gateway.

    1. Add the hostname and the IP address in the /etc/inet/hosts file on both cluster nodes.

    2. Register the logical host, and then add the logical host resource to the resource group.


      # scrgadm -a -L -g sag-rg -j sag-lh-rs -l swiftgatewayhost

  3. Create the device group and file systems.

    Although you can use a global file system, create an HAStoragePlus failover resource to contain the SWIFTAlliance Gateway application and configuration data.

    This procedure uses /swift/SWIFTAlliance/Gateway as the path.


    # scrgadm -a -g sag-rg -j sag-ds -t SUNW.HAStoragePlus -x FilesystemMountPoints=/swift

  4. Bring the resource group online to enable the IP address and access to the storage.


    # scswitch -Z -g sag-rg

  5. Create the following directories and symbolic links before the installation.

    Without these symbolic links, the SWIFTAlliance Gateway application will not be installed in the correct location. You must install the SWIFTAlliance Gateway application in the correct location to ensure failover capabilities.

    Perform this procedure on the node where the resource group for SWIFTAlliance Gateway is online.


    # mkdir -p /swift/etc/opt/swnet
# chown root:swnetg /swift/etc/opt/swnet
# chmod -R 0555 /swift/etc
# chmod 0775 /swift/etc/opt/swnet
# mkdir -p /swift/var/opt/swnet
# chown root:swnetg /swift/var/opt/swnet
# chmod -R 0555 /swift/var
# chmod 0775 /swift/var/opt/swnet
# mkdir -p /swift/home/swnet
# chown swnet:swnetg /swift/home/swnet

    Perform this procedure on all cluster nodes.


    # ln -s /swift/home/swnet /home/swnet
# ln -s /swift/etc/opt/swnet /etc/opt/swnet
# ln -s /swift/var/opt/swnet /var/opt/swnet

  6. If necessary, install the Websphere MQ client packages.

    Websphere MQ client software is software that guarantees and load-balances connections between the gateway and remote SWIFTNet Link systems. If you chose this type of SWIFTAlliance Gateway installation and have the appropriate license, install the Websphere MQ client packages. The Websphere MQ client package must be installed locally on all nodes using the same installation directory.

  7. Install SWIFTNet Link.

    Note –

    You must install SWIFTNet Link on the node where the resource group for SWIFTAlliance Gateway is online. You must also install SWIFTNet Link in the directory on the file system managed by the HAStoragePlus resource created in Step 3.

    • Follow the instructions in your SWIFTNet Link documentation. To refer the SWIFTNet Link documentation, obtain the SWIFTNet Link CD-ROM.

    • Specify the directory on which to install the failover data service: /swift/snl.

    • If necessary, install any patches for SWIFTNet Link.

  8. Configure and register HSM on the primary node as follows:

    • Log on to the primary node as the SWIFTNet Link instance owner with the swnet account.

    • Run the following command:


      # perl SwHSMDiskClone.pl -a SETUP

    • Log off.

    • Log on as the SWIFTNet Link instance owner with the swnet account.

    • Use the HSM administration tool SwHSM to configure and register the HSM boxes connected to the primary node. See the SWIFTNet Link Installation and Administration Guide for UNIX for details.

      Note –

      During the configuration and registration of the HSM, you must enter the boot IP address of the primary node in the SWIFTNet Link host IP address field of the Register screen. This source IP address is used to establish the connection. Do not use the logical host address that is used by the service.

  9. Register HSM on the secondary node or nodes.

    • Switch the resource group for SWIFTAlliance Gateway to the secondary node.


      # scswitch -z -g sag-rg -h node2

    • Log on to the secondary node as the SWIFTNet Link instance owner with the swnet account.

    • Run the following command:


      # perl SwHSMDiskClone.pl -a SETUP

    • Log off.

    • Log on as the SWIFTNet Link instance owner with the swnet account.

    • Use the HSM administration tool SwHSM to register the HSM boxes connected to the secondary node or nodes. See the SWIFTNet Link Installation and Administration Guide for UNIX for details.

      Note –

      During the registration of the HSM, you must enter the boot IP address of the secondary node in the SWIFTNet Link host IP address field of the Register screen. This source IP address is used to establish the connection. Do not use the logical host address that is used by the service.

      Note –

      You need to be aware that the only difference here is that you configure and register the HSM on the first node, whereas you only register the HSM on the secondary node or nodes.

  10. Install SWIFTAlliance Gateway software.

    Note –

    You must install SWIFTAlliance Gateway on the node where the resource group for SWIFTAlliance Gateway is online. You must also install SWIFTAlliance Gateway in a directory on the file system managed by the HAStoragePlus resource created in Step 3. You may install the SWIFTAlliance Gateway patches, if necessary.

    • Follow the instructions in your SWIFTAlliance Gateway documentation. To refer the SWIFTAlliance Gateway documentation, obtain the SWIFTAlliance Gateway CD-ROM.

    • Use the logical IP address as the IP with which the SWIFTAlliance Gateway software communicates with remote hosts.

  11. Synchronize all nodes with installation specific changes to user files and system files.

    • The ~root/vpd.properties has been replaced by the ~root/InstallShield directory structure. This directory structure needs to be copied on all nodes that are part of the cluster. This will enable you to install patches in the future.

    • Add all entries in /etc/system and /etc/services added by the installation on the first node to the secondary node or nodes.

Next Steps

Go to How to Verify the SWIFTAlliance Gateway Installation and Configuration.

ProcedureHow to Verify the SWIFTAlliance Gateway Installation and Configuration

Perform this procedure on each node that can master the SWIFTAlliance Gateway resource group.

  1. Log in as superuser to a node that can master the SWIFTAlliance Gateway resource group.

  2. Switch the SWIFTAlliance Gateway resource group to the node that you logged in to in Step 1.


    # scswitch -z -g sag-rg -h node
    -z

    Specifies that the node that masters a resource group is to be switched

    -g sag-rg

    Specifies that the SWIFTAlliance Gateway resource group is to be switched to another node

    -h node

    Specifies the node to which the SWIFTAlliance Gateway resource group is to be switched

  3. Confirm that the SWIFTAlliance Gateway instance can be started.


    # su - swnet
# cd /swift/SWIFTAlliance/Gateway/bin
# ./sag_bootstrap -startsag start
# ./sag_system -- status system
    Note –

    The application starts successfully if the preceding command returns a started status. This status indicates that the SWIFTAlliance Gateway is operational.

  4. Create another SWIFTAlliance Gateway operator with an operating profile that contains only the functions to start and stop the application.

  5. Confirm that the SWIFTAlliance Gateway instance can be stopped.


    # su - swnet
# cd /swift/SWIFTAlliance/Gateway/bin
# ./sag_bootstrap stop
Next Steps

Go to Installing the Sun Cluster HA for SWIFTAlliance Gateway Packages.

Installing the Sun Cluster HA for SWIFTAlliance Gateway Packages

If you did not install the Sun Cluster HA for SWIFTAlliance Gateway packages during your initial Sun Cluster installation, perform this procedure to install the packages. Perform this procedure on each cluster node where you are installing the Sun Cluster HA for SWIFTAlliance Gateway packages. To complete this procedure, you need the Sun Cluster Agents CD-ROM.

Note –

The SUNWscsag package is available on the CD-ROM for Solaris 8 and 9. On Solaris 10, install either of them (the packages are identical for all Solaris versions) using the pkgadd -G command.

Note –

Patch 118984–04 or a later patch must be installed. On Solaris 8 and 9, the patch must be installed using the patchadd command and on Solaris 10, the patch must be installed using the patchadd -G command.

If you are installing more than one data service simultaneously, perform the procedure in Installing the Software in Sun Cluster Software Installation Guide for Solaris OS.

Install the Sun Cluster HA for SWIFTAlliance Gateway packages by using one of the following installation tools:

Note –

The Web Start program is not available in releases earlier than Sun Cluster 3.1 Data Services 10/03.

ProcedureHow to Install Sun Cluster HA for SWIFTAlliance Gateway Packages by Using the Web Start Program

You can run the Web Start program with a command-line interface (CLI) or with a graphical user interface (GUI). The content and sequence of instructions in the CLI and the GUI are similar. For more information about the Web Start program, see the installer(1M) man page.

  1. On the cluster node where you are installing the Sun Cluster HA for SWIFTAlliance Gateway packages, become superuser.

  2. (Optional) If you intend to run the Web Start program with a GUI, ensure that your DISPLAY environment variable is set.

  3. Insert the Sun Cluster Agents CD-ROM into the CD-ROM drive.

    If the Volume Management daemon vold(1M) is running and configured to manage CD-ROM devices, it automatically mounts the CD-ROM on the /cdrom/cdrom0 directory.

  4. Change to the Sun Cluster HA for SWIFTAlliance Gateway component directory of the CD-ROM.

    The Web Start program for the Sun Cluster HA for SWIFTAlliance Gateway data service resides in this directory.


    # cd /cdrom/cdrom0/components/SunCluster_HA_SAG_3.1

  5. Start the Web Start program.


    # ./installer

  6. When you are prompted, select the type of installation.

    • To install only the C locale, select Typical.

    • To install other locales, select Custom.

  7. Follow the instructions on the screen to install the Sun Cluster HA for SWIFTAlliance Gateway packages on the node.

    After the installation is finished, the Web Start program provides an installation summary. This summary enables you to view logs that the Web Start program created during the installation. These logs are located in the /var/sadm/install/logs directory.

  8. Exit the Web Start program.

  9. Remove the Sun Cluster Agents CD-ROM from the CD-ROM drive.

    1. To ensure that the CD-ROM is not being used, change to a directory that does not reside on the CD-ROM.

    2. Eject the CD-ROM.


      # eject cdrom
Next Steps

Go to Registering and Configuring the Sun Cluster HA for SWIFTAlliance Gateway.

ProcedureHow to Install Sun Cluster HA for SWIFTAlliance Gateway Packages by Using scinstall Utility

Perform this procedure on all of the cluster members that can master Sun Cluster HA for SWIFTAlliance Gateway.

Before You Begin

Ensure that you have the Sun Cluster Agents CD-ROM.

  1. Load the Sun Cluster Agents CD-ROM into the CD-ROM drive.

  2. Run the scinstall utility with no options.

    This step starts the scinstall utility in interactive mode.

  3. Select the menu option, Add Support for New Data Service to This Cluster Node.

    The scinstall utility prompts you for additional information.

  4. Provide the path to the Sun Cluster Agents CD-ROM.

    The utility refers to the CD as the “data services cd.”

  5. Specify the data service to install.

    The scinstall utility lists the data service that you selected and asks you to confirm your choice.

  6. Exit the scinstall utility.

  7. Unload the CD from the drive.

Next Steps

Go to Registering and Configuring the Sun Cluster HA for SWIFTAlliance Gateway.

Registering and Configuring the Sun Cluster HA for SWIFTAlliance Gateway

This section contains the procedures that you need to configure Sun Cluster HA for SWIFTAlliance Gateway.

To enable Sun Cluster HA for SWIFTAlliance Gateway to make SWIFTAlliance Gateway highly available, configure the Sun Cluster HA for SWIFTAlliance Gateway data service as a failover data service.

Before you perform this procedure, ensure that the Sun Cluster HA for SWIFTAlliance Gateway data service packages are installed.

ProcedureHow to Register and Configure Sun Cluster HA for SWIFTAlliance Gateway as a Failover Service

Use this procedure to configure the Sun Cluster HA for SWIFTAlliance Gateway data service as a failover service.

  1. Become superuser on one of the nodes in the cluster that is the host for SWIFTAlliance Gateway.

  2. Register the SUNW.gds resource type.


    # scrgadm -a -t SUNW.gds
    -a

    Specifies that a new configuration is to be added.

    -t SUNW.HAStoragePlus

    Specifies that the resource is an instance of the SUNW.HAStoragePlus resource type.

  3. Register the SUNW.HAStoragePlus resource type.


    # scrgadm -a -t SUNW.HAStoragePlus

  4. Create the failover resource group.


    # scrgadm -a -g sag-rg

  5. Create a resource for the Sun Cluster Disk Storage.


    # scrgadm -a -j sag-ds-rs \
-g sag-rg \
-t SUNW.HAStoragePlus \
-x FilesystemMountPoints=/swift
    -a

    Specifies that a new configuration is to be added.

    -j hsp-resource

    Specifies that the resource that you are creating is named hsp-resource.

    -g sag-rg

    Specifies that the resource is to be added to the SWIFTAlliance Gateway resource group.

    -t SUNW.HAStoragePlus

    Specifies that the resource is an instance of the SUNW.HAStoragePlus resource type.

    -x filesystemmountpoints=mountpoint-list

    Specifies a list of valid mount points for the file system. For more information, see the SUNW.HAStoragePlus(5) man page.

  6. Create a resource for the Sun Cluster logical hostname.


    # scrgadm -a -L -j sag-lh-rs \
-g sag-rg \
-l gatewayhostname

  7. Enable the failover resource that contains the Sun Cluster Disk Storage and the Logical hostname resources.


    # scswitch -Z -g sag-rg

  8. Create a resource for SWIFTAlliance Gateway.

    1. Change the user name, password, and path variable in the /opt/SUNWscsag/etc/settings file on all nodes.

      For information about this file, see Configuration Files and Registration Script.

    2. Change the variables in the /opt/SUNWscsag/util/sag_config file.

      For information about this file, see Configuration Files and Registration Script.

    3. Run the registration script to register the data service and application.

      For information about this script, see Configuration Files and Registration Script.


      # /opt/SUNWscsag/util/sag_register

  9. Enable the SWIFTAlliance Gateway resource.


    # scswitch -e -j sag-resource-rs
Next Steps

Go to Verifying the Sun Cluster HA for SWIFTAlliance Gateway Installation and Configuration.

Verifying the Sun Cluster HA for SWIFTAlliance Gateway Installation and Configuration

This section contains the procedure to verify that you installed and configured your data service properly.

ProcedureHow to Verify the Sun Cluster HA for SWIFTAlliance Gateway Installation and Configuration

  1. Become superuser on one of the nodes in the cluster that hosts SWIFTAlliance Gateway.

  2. Ensure that all the Sun Cluster resources are online.


    # scstat
# scswitch -e -j resource

  3. Move the Sun Cluster resource group to another cluster node, such as node1.


    # scswitch -z -g sag-rg -h node1

  4. Ensure that SWIFTAlliance Gateway stopped on node1 and that the application started on another node, such as node2.

    When using a failover file system, the file system disappears on node1 and mounts on node2.

Next Steps

Go to Tuning the Sun Cluster HA for SWIFTAlliance Gateway Fault Monitor.

Tuning the Sun Cluster HA for SWIFTAlliance Gateway Fault Monitor

Sun Cluster HA for SWIFTAlliance Gateway provides software for fault monitoring by checking the status of the Alliance Gateway service. The values `running' and `partial' are considered healthy; values other than these will force a restart or failover to another node in the cluster. By accepting a partial status, operators may temporarily disable portions of the service without informing the cluster. You do not need an user id and password for monitoring.

The Sun Cluster HA for SWIFTAlliance Gateway fault monitor is contained in the resource that represents SWIFTAlliance Gateway. You create this resource when you register and configure Sun Cluster HA for SWIFTAlliance Gateway. For more information, see Registering and Configuring the Sun Cluster HA for SWIFTAlliance Gateway.

System properties and extension properties of this resource control the behavior of the fault monitor. The default values of these properties determine the preset behavior of the fault monitor. The preset behavior should be suitable for most Sun Cluster installations. Therefore, tune the Sun Cluster HA for SWIFTAlliance Gateway fault monitor only if you need to modify this behavior.

Tuning the Sun Cluster HA for SWIFTAlliance Gateway fault monitor involves the following tasks:

Perform these tasks when you register and configure Sun Cluster HA for SWIFTAlliance Gateway. For more information, see the following sections:

Debugging Sun Cluster HA for SWIFTAlliance Gateway

ProcedureHow to Set the Debug Flag for Sun Cluster HA for SWIFTAlliance Gateway

Sun Cluster HA for SWIFTAlliance Gatewayhas an option file in /opt/SUNWscsag/etc directory that enables you to set a debug flag.

Normally, the debug information for Sun Cluster software does not reside in the log files. You must edit the syslog.conf file to enable logging of messages of level debug. You can edit the syslog.conf to log those messages in another file.

  1. Edit /etc/syslog.conf.

    1. Change daemon.notice to daemon.debug.

      The following output from the grep daemon /etc/syslog.conf command shows that daemon.debug has not been set.


      grep daemon /etc/syslog.conf
*.err;kern.debug;daemon.notice;mail.crit
/var/adm/messages
*.alert;kern.err;daemon.err
operator

    2. Restart syslogd.


      # pkill -1 syslogd

      The syslogd command forces syslog to reread its configuration file and account for changes.

      The following output from the grep daemon /etc/syslog.conf command shows that daemon.debug has been set.


      grep daemon /etc/syslog.conf
*.err;kern.debug;daemon.debug;mail.crit
/var/adm/messages
*.alert;kern.err;daemon.err
operator

  2. Edit the /opt/SUNWscsag/etc/config file.

    Change the line DEBUG= to DEBUG=ALL or DEBUG=resource.