JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris Cluster Data Service for SWIFTAlliance Access Guide SPARC Platform Edition
search filter icon
search icon

Document Information

Preface

1.  Installing and Configuring Oracle Solaris Cluster HA for Alliance Access

Overview of Installing and Configuring HA for Alliance Access

Oracle Solaris Cluster HA for Alliance Access Overview

Planning the Oracle Solaris Cluster HA for Alliance Access Installation and Configuration

Configuration Restrictions

Configuration Requirements

Oracle Solaris Cluster components and their dependencies

Installing and Configuring Alliance Access

How to Install and Configure Alliance Access

Verifying the Installation and Configuration of Alliance Access

How to Verify the Installation and Configuration of Alliance Access

Installing the HA for Alliance Access Packages

How to Install the HA for Alliance Access Packages

Registering and Configuring Oracle Solaris Cluster HA for Alliance Access

How to Register and Configure Oracle Solaris Cluster HA for Alliance Access as a Failover Service

Verifying the Oracle Solaris Cluster HA for Alliance Access Installation and Configuration

How to Verify the Oracle Solaris Cluster HA for Alliance Access Installation and Configuration

Understanding the Oracle Solaris Cluster HA for Alliance Access Fault Monitor

Resource Properties

Probing Algorithm and Functionality

Debugging Oracle Solaris Cluster HA for Alliance Access

How to turn on debugging for Oracle Solaris Cluster HA for Alliance Access

Index

Understanding the Oracle Solaris Cluster HA for Alliance Access Fault Monitor

This section describes the Oracle Solaris Cluster HA for Alliance 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 Solaris Cluster Concepts Guide.

Resource Properties

The Oracle Solaris Cluster HA for Alliance 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

By default, the HA agent provides a fault monitor for the DCE component only when using Alliance Access 5.5. The fault monitoring for Alliance Access is switched off by default. If the Alliance Access application fails, the agent will not restart the Alliance Access application automatically. This behavior was explicitly requested by SWIFT. It will enable you to operate the application in a way that the probe does not interfere with the normal behavior of some Alliance Access features like:

The HA agent will update the resource status message to output Degraded - SAA Instance offline.

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

The HA agent provides an option to turn on fault monitoring for Alliance Access at registration time. However, this option is not recommended by SWIFT. The optional probing checks for the existence of the Alliance Access instance by calling the alliance command that is part of the application and by evaluating its return code. If the Alliance Access instance is not running, return code 100 is sent to SUNW.gds, which in turn will perform an automatic restart depending on the configuration of the resource properties.