This chapter explains how to install and configure Sun Cluster HA for SWIFTAlliance Gateway.
This chapter contains the following procedures.
How to Verify the SWIFTAlliance Gateway Installation and Configuration
How to Install Sun Cluster HA for SWIFTAlliance Gateway Packages by Using the Web Start Program
How to Install Sun Cluster HA for SWIFTAlliance Gateway Packages by Using scinstall Utility
How to Register and Configure Sun Cluster HA for SWIFTAlliance Gateway as a Failover Service
How to Verify the Sun Cluster HA for SWIFTAlliance Gateway Installation and Configuration
How to Set the Debug Flag for Sun Cluster HA for SWIFTAlliance Gateway
The Sun Cluster HA for SWIFTAlliance Gateway data service provides a mechanism for orderly startup, shutdown, switchover, and failover of the Sun Cluster data service.
Sun Cluster HA for SWIFTAlliance Gateway does not provide software fault monitoring. The purpose of the HA active standby installation of Sun Cluster HA for SWIFTAlliance Gateway is to detect and react to hardware failures.
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–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 |
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 1–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 | |
Install the Sun Cluster HA for SWIFTAlliance Gateway packages | |
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 |
This section contains the information that you need to plan your Sun Cluster HA for SWIFTAlliance Gateway installation and configuration.
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.
The configuration restrictions in this section apply only to Sun Cluster HA for SWIFTAlliance Gateway.
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 9/04 Release Notes for Solaris OS.
Sun Cluster HA for SWIFTAlliance Gateway supports SWIFTAlliance Gateway version 4.0.20 or higher and 5.0 or higher.
You can only install the SWIFTNet Link and the SWIFTAlliance Gateway software on a failover file system. If Websphere MQ client software is needed for the operation of SWIFTAlliance Gateway, install Websphere MQ client software on the local file system on each node and in the same path. The default path is /opt/mqm.
You cannot configure Sun Cluster HA for SWIFTAlliance Gateway as a scalable data service.
The configuration requirements in this section apply only to Sun Cluster HA for SWIFTAlliance Gateway.
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.
You must configure Sun Cluster HA for SWIFTAlliance Gateway as a failover data service.
If you are running SWIFTAlliance Gateway 4.0, create a SWIFTAlliance Gateway operator with an operator profile that contains only the functions to start and stop SWIFTAlliance Gateway. This operator is used to send start, stop, and status commands to SWIFTAlliance Gateway. For security reasons, do not use the administrator profile to start and stop the application.
If you are running SWIFTAlliance Gateway 5.0, an operator name and password are not necessary to send the sag_system commands directly from the SWIFTAlliance Gateway system.
The configuration considerations in the subsections that follow affect the installation and configuration of Sun Cluster HA for SWIFTAlliance Gateway.
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 1–3 Sun Cluster Components
Component |
Dependencies |
---|---|
SWIFTAlliance Gateway This component includes the SWIFTNet Link instance. |
|
The Sun Cluster component has two configuration files and a registration script.
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. |
|
This configuration file contains settings to register the data service and the application in the Sun Cluster framework. |
|
This registration script enables you to register the data service. |
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 3.1 Data Service Planning and Administration Guide.
Do you have a SWIFTNet connection and an Internet connection? The installation requires a secure server from SWIFT nv.
Do you have your SWIFTAlliance Gateway license key? If not, retrieve this information.
Do you have your SWIFTAlliance Gateway installation documentation? If not, download this documentation from http://www.swift.com.
Before you run Sun Cluster HA for SWIFTAlliance Gateway as a failover data service, answer the following questions:
Where will the system configuration files reside?
See “Configuration Guidelines for Sun Cluster Data Services” in Sun Cluster 3.1 Data Service Planning and Administration Guide for the advantages and disadvantages of using the local file system instead of the cluster file system.
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 http://www.swift.com.
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 “Planning for Sun Cluster Data Services” in Sun Cluster 3.1 Data Service Planning and Administration Guide.
Create a resource group for SWIFTAlliance Gateway.
# scrgadm -a -g sag-rg |
Create a logical host.
A logical host is required before you install SWIFTAlliance Gateway.
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.
To create a device group and a file system for SWIFTAlliance Gateway, see “Planning the Global Devices and Cluster File Systems” in Sun Cluster Software Installation Guide for Solaris OS.
To create an HAStoragePlus failover resource, see “Enabling Highly Available Local File Systems” in Sun Cluster Data Services Planning and Administration Guide for Solaris OS.
This procedure uses /swift/SWIFTAlliance/Gateway as the path.
# scrgadm -a -g sag-rg -j sag-ds -t SUNW.HAStoragePlus -x filesystemMountPoints=/swift |
Bring the resource group online to enable the IP address and access to the storage.
# scswitch -Z -g sag-rg |
Create the following 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.
# cd /swift # mkdir -p /swift/etc/opt/swnet # chown -R root:system /swift/etc # chown -R root:swnetg /swift/etc/opt/swnet # chmod -R 0555 /swift/etc # chmod -R 0775 /swift/etc/opt # cd /etc/opt # ln -s /swift/etc/opt/swnet swnet # mkdir -p /swift/var/opt/swnet # chown -R root:system /swift/var/ # chown -R root:swnetg /swift/var/opt/swnet # chmod -R 0775 /swift/var # cd /var/opt # ln -s /swift/var/opt/swnet swnet |
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.
Follow the instructions in your SWIFTNet Link documentation. To download the SWIFTNet Link documentation, see http://www.swift.com.
Specify the directory on which to install the failover data service: /swift/snl.
If necessary, install any patches for SWIFTNet Link before you proceed with the installation of SWIFTAlliance Gateway.
Install SWIFTAlliance Gateway software.
Follow the instructions in your SWIFTAlliance Gateway documentation. To download the SWIFTAlliance Gateway documentation, see http://www.swift.com.
Use the logical IP address as the IP with which the SWIFTAlliance Gateway software communicates with remote hosts.
If necessary, install Websphere MQ client software.
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.
Create the following symbolic links.
# 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 |
Copy the ~root/vpd.properties file from node2 to the ~root/ directory on node1.
This information enables you to install patches in the future.
Go to How to Verify the SWIFTAlliance Gateway Installation and Configuration.
Perform this procedure on each node that can master the SWIFTAlliance Gateway resource group.
Log in as superuser to a node that can master the SWIFTAlliance Gateway resource group.
Switch the SWIFTAlliance Gateway resource group to the node that you logged in to in Step 1.
# scswitch -z -g sag-rg -h node |
Specifies that the node that masters a resource group is to be switched
Specifies that the SWIFTAlliance Gateway resource group is to be switched to another node
Specifies the node to which the SWIFTAlliance Gateway resource group is to be switched
Confirm that the SWIFTAlliance Gateway instance can be started.
# su - swnet # cd /swift/SWIFTAlliance/Gateway/bin # ./sag_bootstrap start # ./sag_system -SagUser Administrator -SagPwd pwd-for-admin -- start |
The application started successfully if the following command returns a started status. This status indicates that the SWIFTAlliance Gateway is operational.
# ./sag_system -SagUser Administrator -SagPwd pwd-for-admin -- status system |
Create another SWIFTAlliance Gateway operator with an operating profile that contains only the functions to start and stop the application.
Confirm that the SWIFTAlliance Gateway instance can be stopped.
# su - swnet # cd /swift/SWIFTAlliance/Gateway/bin # ./sag_bootstrap stop |
Go to How to Install Sun Cluster HA for SWIFTAlliance Gateway Packages by Using the Web Start Program.
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.
If you are installing more than one data service simultaneously, perform the procedure in “Installing the Software” in Sun Cluster 3.1 Software Installation Guide.
Install the Sun Cluster HA for SWIFTAlliance Gateway packages by using one of the following installation tools:
Web Start program
scinstall utility
The Web Start program is not available in releases earlier than Sun Cluster 3.1 Data Services 10/03.
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.
If you are remotely connected to the machine where the CD-ROM
is loaded and you intend to run the Web Start program with a GUI,
ensure that your DISPLAY
environment
variable is set. Otherwise, the Web Start program runs with the CLI.
Become superuser on the cluster node where you are installing the Sun Cluster HA for SWIFTAlliance Gateway packages.
Load 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.
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 |
Start the Web Start program.
# ./installer |
When you are prompted, select the type of installation.
Follow 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.
Exit the Web Start program.
Unload the Sun Cluster Agents CD-ROM from the CD-ROM drive.
Go to Registering and Configuring the Sun Cluster HA for SWIFTAlliance Gateway.
Load the Sun Cluster Agents CD-ROM into the CD-ROM drive.
Run the scinstall utility with no options.
This step starts the scinstall utility in interactive mode.
Select the menu option, Add Support for New Data Service to This Cluster Node.
The scinstall utility prompts you for additional information.
Provide the path to the Sun Cluster Agents CD-ROM.
The utility refers to the CD as the “data services cd.”
Specify the data service to install.
The scinstall utility lists the data service that you selected and asks you to confirm your choice.
Exit the scinstall utility.
Unload the CD from the drive.
Go to How to Register and Configure Sun Cluster HA for SWIFTAlliance Gateway as a Failover Service.
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.
Use this procedure to configure the Sun Cluster HA for SWIFTAlliance Gateway data service as a failover service.
Become superuser on one of the nodes in the cluster that is the host for SWIFTAlliance Gateway.
Register the SUNW.gds resource type.
# scrgadm -a -t SUNW.gds |
Specifies that a new configuration is to be added.
Specifies that the resource is an instance of the SUNW.HAStoragePlus resource type.
Register the SUNW.HAStoragePlus resource type.
# scrgadm -a -t SUNW.HAStoragePlus |
Create the failover resource group.
# scrgadm -a -g sag-rg |
Create a resource for the Sun Cluster Disk Storage.
# scrgadm -a -j sag-ds-rs \ -g sag-rg \ -t SUNW.HAStoragePlus \ -x FilesystemMountPoints=/swift |
Specifies that a new configuration is to be added.
Specifies that the resource that you are creating is named hsp-resource.
Specifies that the resource is to be added to the SWIFTAlliance Gateway resource group.
Specifies that the resource is an instance of the SUNW.HAStoragePlus resource type.
Specifies a list of valid mount points for the file system. For more information, see the SUNW.HAStoragePlus(5) man page.
Create a resource for the Sun Cluster logical hostname.
# scrgadm -a -L -j sag-lh-rs \ -g sag-rg \ -l gatewayhostname |
Enable the failover resource that contains the Sun Cluster Disk Storage and the Logical hostname resources.
# scswitch -Z -g sag-rg |
Create a resource for SWIFTAlliance Gateway.
Change the user name, password, and path variable in the /opt/SUNWscsag/etc/settings.sh file.
For information about this file, see Configuration Files and Registration Script.
Change the group name, resource name and, if necessary, the port number in the /opt/SUNWscsag/util/sag_config file.
For information about this file, see Configuration Files and Registration Script.
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 |
Enable the SWIFTAlliance Gateway resource.
# scswitch -e -j sag-resource-rs |
Specifies that the HAStoragePlus resource that you created.
Go to 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.
Become superuser on one of the nodes in the cluster that hosts SWIFTAlliance Gateway.
Ensure that all the Sun Cluster resources are online.
# scstat # scswitch -e -jresource |
Move the Sun Cluster resource group to another cluster node, such as node1.
# scswitch -z -g sag-rg -h node1 |
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.
Go to Tuning the Sun Cluster HA for SWIFTAlliance Gateway Fault Monitor.
The Sun Cluster HA for SWIFTAlliance Gateway fault monitor detects the following faults:
Failure of a node
Failure of a network connection
Failure of a disk connection
Failure of the SWIFTAlliance Gateway application to start on a node.
The Sun Cluster HA for SWIFTAlliance Gateway fault monitor does not detect software failures.
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 SUNW.gds(1).
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:
Setting the interval between fault monitor probes
Setting the timeout for fault monitor probes
Defining the criteria for persistent faults
Specifying the failover behavior of a resource
Perform these tasks when you register and configure Sun Cluster HA for SWIFTAlliance Gateway. For more information, see the following sections:
Sun Cluster HA for SWIFTAlliance Gateway has 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.
Edit /etc/syslog.conf.
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 |
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 |
Edit the /opt/SUNWscsag/etc/config file.
Change the line DEBUG= to DEBUG=ALL or DEBUG=resource.