Sun Cluster Data Service for SWIFTAlliance Access Guide for Solaris OS

Previous: Preface

Installing and Configuring Sun Cluster HA for SWIFTAlliance Access

This Chapter explains how to install and configure Sun Cluster HA for SWIFTAlliance Access.

This Chapter contains the following sections.

Overview of the tasks needed to install and configure Sun Cluster HA for SWIFTAlliance Access.

Table 1 Lists the tasks for installing and configuring Sun Cluster HA for SWIFTAlliance Access. Perform these tasks in the order that they are listed.

Table 1 Task Map: Installing and Configuring Sun Cluster HA for SWIFTAlliance Access


Task	For Instructions, Go To
1.Plan the installation.	Planning the Sun Cluster HA for SWIFTAlliance Access Installation and Configuration
2.Install Sun Cluster HA for SWIFTAlliance Access Packages.	How to Install and Configure SWIFTAlliance Access
3.Verify installation and configuration.	Verifying the Installation and Configuration of SWIFTAlliance Access
4.Register and Configure Sun Cluster HA for SWIFTAlliance Access.	Registering and Configuring Sun Cluster HA for SWIFTAlliance Access
5.Verify Sun Cluster HA for SWIFTAlliance Access Installation and Configuration.	Verifying the Sun Cluster HA for SWIFTAlliance Access Installation and Configuration
6.Understand Sun Cluster HA for SWIFTAlliance Access fault monitor.	Understanding the Sun Cluster HA for SWIFTAlliance Access Fault Monitor
7.Debug Sun Cluster HA for SWIFTAlliance Access.	Debug Sun Cluster HA for SWIFTAlliance Access

Sun Cluster HA for SWIFTAlliance Access Overview

The HA agent is written to work with SWIFTAlliance Access version 5.5 and 5.9, version 5.5 of SWIFTAlliance Access is dependent on DCE, you must also install the IBM DCE version v3.2 software for Solaris. SWIFTAlliance Access^TMis a trademark of SWIFT.

The Sun Cluster HA for SWIFTAlliance Access data service provides a mechanism for orderly startup and shutdown, fault monitoring, and automatic failover of the Sun Cluster service. TheSun Cluster components protected by the Sun Cluster HA for SWIFTAlliance Access data service.

Table 2 Protection of Components


Component	Protected by
DCE daemon	Sun Cluster HA for SWIFTAlliance Access
SWIFT Alliance Access	Sun Cluster HA for SWIFTAlliance Access

Note –

The HA agent provides a fault monitor for the DCE component only. If the SWIFTAlliance Access stops, it will not be restarted automatically. This behavior was explicitly requested by SWIFT. It will allow users unfamiliar with the Sun Cluster software to operate the application as if it is not running on a cluster. The HA agent provides the start, stop, failover, and switchover functionality. This means that when a node fails, the other node will automatically start the application.

Planning the Sun Cluster HA for SWIFTAlliance Access Installation and Configuration

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

Configuration Restrictions

This section provides a list of software and hardware configuration restrictions that apply to Sun Cluster HA for SWIFTAlliance Access only.

Caution –

Your data service configuration might not be supported if you do not observe these restrictions.

You can configure the Sun Cluster HA for SWIFTAlliance Access only as a HA agent and not as a scalable agent.
You can install the SWIFTAlliance Access software on a global file system. Best practice is to use a failover file system. You must install the IBM DCE software on local storage.

For restrictions that apply to all data services, see the Sun Cluster Release Notes.

Configuration Requirements

These requirements apply to Sun Cluster HA for SWIFTAlliance Access only. You must meet these requirements before you proceed with your Sun Cluster HA for SWIFTAlliance Access installation and configuration. Follow the SWIFTAlliance Access installation guide for the installation of the mandatory patch levels and the installation of the software itself.

Caution –

Your data service configuration might not be supported if you do not adhere to these requirements.

Sun Cluster components and their dependencies —Configure the Sun Cluster HA for SWIFTAlliance Access data service to protect a Sun Cluster instance and its respective components. These components, and their dependencies, are briefly described below.

Component	Description
DCE daemon	-> SUNW.LogicalHost resource
SWIFTAlliance Access	-> SUNW.LogicalHostresource -> SUNW.HAStoragePlus resource The SUNW.HAStoragePlus resource manages the SWIFTAlliance Access System Mount points and ensures that Sun Cluster is not started until these are mounted. -> DCE daemon

Component

Description

DCE daemon

-> SUNW.LogicalHost resource

SWIFTAlliance Access

-> SUNW.LogicalHostresource

-> SUNW.HAStoragePlus resource

The SUNW.HAStoragePlus resource manages the SWIFTAlliance Access System Mount points and ensures that Sun Cluster is not started until these are mounted.

-> DCE daemon

The Sun Cluster component has two configuration and registration files under /opt/SUNWscsaa/util. These files allow you to register the Sun Cluster component with Sun Cluster with default values.

Within these files, the appropriate dependencies have already been defined. If you use different names for the resources, you must update the saa_config file before you run the saa_register script.

Installing and Configuring SWIFTAlliance Access

This section contains the procedures you need to install and configure SWIFTAlliance Access.

Throughout the following sections, references will be made to certain directories for SWIFTAlliance Access, which can be selected by the user.

How to Install and Configure SWIFTAlliance Access

Use this procedure to install and configure SWIFTAlliance Access.

Create the resources for SWIFTAlliance Access.
- Create a resource group for SWIFTAlliance Access:
  # clresourcegroup create swift-rg
- Create a logical host – A logical host is required for DCE. Add the hostname and IP address in the /etc/hosts file on both cluster nodes. Register the logical host and add it to the resource group.
  # clreslogicalhostname create -g swift-rg -l swift-lh swift-saa-lh-rs
- Create the device group and filesystem —See Sun Cluster Data Services Installation and Configuration Guide for instructions on how to create global file systems.
- Create an HAstoragePlus resource – Although one can use global storage, it is recommended to create a HAStoragePlus failover resource to contain the SWIFTAlliance Access application and configuration data.
  
  In the example, we use /global/saadg/alliance as the path, but you can choose the location.
  # clresource create -g swift-rg \ -t SUNW.HAStoragePlus \ -x FilesystemMountPoints=/global/saadg/alliance swift-ds
- Bring the resource group online —
  # clresouregroup online swift-rg
- Create configuration directory —to hold SWIFTAlliance Access information and create a link from /usr
  # cd /global/saadg/alliance
  # mkdir swa
  # ln -s /global/saadg/alliance /usr/swa
Install IBM DCE client software on all the nodes.

Caution –
This is only valid for versions below 5.9 and should only been installed when needed.

Skip this step if using version 5.9.

IBM DCE client software is a prerequisite for SWIFTAlliance Access. It must be installed and configured before the SWIFTAlliance Access application.
- Install IBM DCE client software Use local disks to install this software. The software comes in Sun package format (IDCEclnt). Because the installed files will reside at various locations on your system, it is not practical to have this installed on global file systems. Install this software on both cluster nodes.
  # pkgadd -d ./IDCEclnt.pkg
- Configure DCE client RPC.
  # /opt/dcelocal/tcl/config.dce —cell_name swift —dce_hostname swift-lh RPC
- Test DCE.
  
  Run the tests on both nodes.
  # /opt/dcelocal/tcl/start.dce
  Verify that the dced daemon is running.
  # /opt/dcelocal/tcl/stop.dce
Install SWIFTAlliance Access software.

Use shared storage for the installation of this software. The installation procedure will modify system files and will also reboot the system. After the reboot, you must continue with the installation on the same node. Repeat the installation of the software on the second node, but you must end the installation before the specification of the access codes.
Additional configuration for SWIFTAlliance Access

To enable clients to connect to the failover IP address, create a file named .alliance_ip_name on the data subdirectory of the SWIFTAlliance Access software.

When you are using the same file system as shown in the examples, this directory will be/global/saadg/alliance/data. This file must contain the IP address of the logical host as configured within the SAA resource.

Verifying the Installation and Configuration of SWIFTAlliance Access

This section contains the procedure you need to verify the installation and configuration.

How to Verify the Installation and Configuration of SWIFTAlliance Access

This procedure does not verify that your application is highly available because you have not yet installed your data service.

Start the SWIFTAlliance Access application
# su - all_adm
The application GUI should start. If DCE is not started yet, start it from the GUI: OS Configuration —> DCE RPC, Then select Alliance —> Start SWIFTAlliance Servers

Test the application

Start the GUI, then select the menu item: Alliance —> Start User Interface.

Stop the SWIFTAlliance Access application

If are not in the GUI, start the GUI:
# su - all_adm
Select the menu: Alliance —> Stop SWIFTAlliance Servers.

Installing the Sun Cluster HA for SWIFTAlliance Access Packages

If you did not install the Sun Cluster HA for SWIFTAlliance Access packages during your initial Sun Cluster installation, perform this procedure to install the packages. To install the packages, use the Sun Java^TM Enterprise System Installation Wizard.

How to Install the Sun Cluster HA for SWIFTAlliance Access Packages

Perform this procedure on each cluster node where you are installing the Sun Cluster HA for SWIFTAlliance Access packages.

You can run the Sun Java Enterprise System Installation Wizard 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.

Before You Begin

Ensure that you have the Sun Java Availability Suite DVD-ROM.

If you intend to run the Sun Java Enterprise System Installation Wizard with a GUI, ensure that your DISPLAY environment variable is set.

On the cluster node where you are installing the data service packages, become superuser.

Load the Sun Java Availability Suite DVD-ROM into the DVD-ROM drive.

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

Change to the Sun Java Enterprise System Installation Wizard directory of the DVD-ROM.
- If you are installing the data service packages on the SPARC® platform, type the following command:
  # cd /cdrom/cdrom0/Solaris_sparc
- If you are installing the data service packages on the x86 platform, type the following command:
  # cd /cdrom/cdrom0/Solaris_x86

Start the Sun Java Enterprise System Installation Wizard.
# ./installer

When you are prompted, accept the license agreement.

If any Sun Java Enterprise System components are installed, you are prompted to select whether to upgrade the components or install new software.

From the list of Sun Cluster agents under Availability Services, select the data service for SWIFTAlliance Access.

If you require support for languages other than English, select the option to install multilingual packages.

English language support is always installed.

When prompted whether to configure the data service now or later, choose Configure Later.

Choose Configure Later to perform the configuration after the installation.

Follow the instructions on the screen to install the data service packages on the node.

The Sun Java Enterprise System Installation Wizard displays the status of the installation. When the installation is complete, the wizard displays an installation summary and the installation logs.

(GUI only) If you do not want to register the product and receive product updates, deselect the Product Registration option.

The Product Registration option is not available with the CLI. If you are running the Sun Java Enterprise System Installation Wizard with the CLI, omit this step

Exit the Sun Java Enterprise System Installation Wizard.

Unload the Sun Java Availability Suite DVD-ROM from the DVD-ROM drive.
1. To ensure that the DVD-ROM is not being used, change to a directory that does not reside on the DVD-ROM.
2. Eject the DVD-ROM.
  # eject cdrom

Next Steps

Go to Registering and Configuring Sun Cluster HA for SWIFTAlliance Access

Registering and Configuring Sun Cluster HA for SWIFTAlliance Access

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

How to Register and Configure Sun Cluster HA for SWIFTAlliance Access as a Failover Service

This procedure assumes that you installed the data service packages during your initial Sun Cluster installation.

If you did not install the Sun Cluster HA for SWIFTAlliance Access packages as part of your initial Sun Cluster installation, go to Installing the Sun Cluster HA for SWIFTAlliance Access Packages.

Steps 1 to 6 will normally already be done in order to prepare for the installation of the IBM DCE and SWIFTAlliance Access software. See How to Install and Configure SWIFTAlliance Access. Typically, you should go directly to step 7.

Become superuser on one of the nodes in the cluster that will host Sun Cluster.

# clresourcetype register SUNW.HAStoragePlus

Create a failover resource group .
# clresourcegroup create swift-rg

Create a resource for the Sun Cluster Disk Storage.

# clresource create -g swift-rg  \
-t SUNW.HAStoragePlus  \
-x FilesystemMountPoints=/global/saadg/alliance swift-ds

Create a resource for the Sun Cluster Logical Hostname.

# clreslogicalhostname create  -g swift-rg\
  -h swift-lh swift-lh-rs

Create a resource for SWIFTAlliance Access.

Run the registration script provided as part of the SWIFTAlliance Access HA agent. Before running this script.

Check that the names of the resources match what is configured in /opt/SUNWscsaa/util/saa_config
# /opt/SUNWscsaa/util/saa_register

Enable the failover resource group that now includes the Sun Cluster Disk Storage and Logical Hostname resources.
# clresourcegroup online swift-rg

Start the SWIFTAlliance Access instance manually.

su - all_adm
The GUI will open up. From within the GUI, select the menu
Alliance - Start Alliance Servers

Stop the SWIFTAlliance Access manually.

su - all_adm
 The GUI will come up. Stop the application from within the GUI.

Enable each Sun Cluster resource.

# clresourcegroup status -g sag-rg
# clresource enable Sun Cluster-resource

Verifying the Sun Cluster HA for SWIFTAlliance Access Installation and Configuration

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

How to Verify the Sun Cluster HA for SWIFTAlliance Access Installation and Configuration

Become superuser on one of the nodes in the cluster that will host Sun Cluster.

Ensure all the Sun Cluster resources are online with cluster status.
# clusterstatus
For each Sun Cluster resource that is not online, use the scswitch command as follows.
# clresource enable Sun Cluster- resource

Run the scswitch command to switch the Sun Cluster resource group to another cluster node, such as node2.
# clresourcegroup switch swift-rg -h node2

Check that SWIFTAlliance Access is stopped on the first node and that the application is restarted on the second node.

When using a failover file system, this should disappear on the first node and will be mounted on the second node.

Understanding the Sun Cluster HA for SWIFTAlliance Access Fault Monitor

This section describes the Sun Cluster HA for SWIFTAlliance Access fault monitor's probing algorithm or functionality, and states the conditions, messages, and recovery actions associated with unsuccessful probing.

For conceptual information on fault monitors, see the Sun Cluster Concepts Guide.

Resource Properties

The Sun Cluster HA for SWIFTAlliance Access fault monitor uses the same resource properties as resource type SUNW.gds, refer to the SUNW.gds(5) man page for a complete list of resource properties used.

Probing Algorithm and Functionality

The fault monitor checks only the DCE daemon. It does not check the executables that are part of SWIFTAlliance Access. This was explicitly requested by Swift. It allows the operator to start and stop SWIFTAlliance Access without paying attention to the cluster.

If an automatic failover occurs, it is most likely that there was a DCE problem. The SWIFTAlliance Access application will cause only a failover when it does not succeed to start on the current node.

Debug Sun Cluster HA for SWIFTAlliance Access

How to turn on debugging for Sun Cluster HA for SWIFTAlliance Access

Sun Cluster HA for SWIFTAlliance Access can be used by multiple Sun Cluster instances. However, it is possible to turn on debugging for all Sun Cluster instances or a particular Sun Cluster instance.

Each Sun Cluster component has a DEBUG file under /opt/SUNWscsaa/etc, where saa is a three-character abbreviation for the respective Sun Cluster component.

These files allow you to turn on debugging for all Sun Cluster instances or for a specific Sun Cluster instance on a particular node with Sun Cluster. If you require debug to be turned on for Sun Cluster HA for SWIFTAlliance Access across the whole Sun Cluster, repeat this step on all nodes within Sun Cluster.

Edit /etc/syslog.conf

Change daemon.notice to daemon.debug

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

Change the daemon.notice to daemon.debug and restart syslogd. The output below, from the command grep daemon /etc/syslog.conf, 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
#
# pkill -1 syslogd
#

Edit /opt/SUNWscsaa/etc/config

Change DEBUG= to DEBUG=ALL or DEBUG=resource

# cat /opt/SUNWscsaa/etc/config
#
# Copyright 2003 Sun Microsystems, Inc.  All rights reserved.
# Use is subject to license terms.
#
# Usage:
#       DEBUG=<RESOURCE_NAME> or ALL
#
DEBUG=ALL
#

Note –

To turn off debug,reverse the steps above.

Previous: Preface