Hardware configuration

The hardware configuration is a basic two-node IRIX FailSafe configuration:

The following is a sample configuration for a primary companion named spinnaker and a secondary companion named mizzen. For information about this configuration, consult your SGI documentation.

Configuration

Primary Companion

Secondary Companion

Logical Name

spinnaker

mizzen

Host Name

spinnaker

mizzen

$DSQUERY

SPINNAKER

MIZZEN

Node ID

1

2

Logical Volume

xlv1

xlv2

Mount Point

/vol1

/vol2

Public IP address

10.22.110.133

10.22.110.132

Private IP address

130.214.121.79

130.214.121.114

Public Network Accepts

Heartbeat and Control

Heartbeat and Control

Private Network Accepts

Heartbeat and Control

Heartbeat and Control

Port Type

MSC

MSC

Port Password

“‘”

“‘”

Logical Name of Reset Owner

mizzen

spinnaker

TTY Device

/dev/ttyd2

/dev/ttyd2

set reset parameter

Checked

Checked

NoteYou can configure IRIX FailSafe using either a GUI (with the fstask utility) or the command line (using the cluster_mgr utility). Examples for both methods are included for each step.For more information about the command-line arguments, see your SGI documentation.

SGI provides unsupported, template command line files. Although these files are not supported by either SGI or Sybase, they have been used and tested within our Engineering organization. You can download these files from:

www.sybase.com/detail?id=1022631

NoteIn the examples below, when the command line argument is called for, it is assumed that the corresponding script has been previously been edited to reflect your environment.

The following list provides a high-level overview of the steps required to setup IRIX FailSafe. The details of each action are listed in the subsequent sections:

  1. Install the FailSafe scripts

  2. Start FailSafe Configuration Tool

  3. Define the primary and secondary nodes

  4. Define the failover policies for the primary and secondary nodes

  5. Define the cluster

  6. Define the logical volume resources for the primary and secondary nodes

  7. Define the failsafe resources for the primary and secondary nodes

  8. Define the Adaptive Server resources for the primary and secondary nodes

  9. Define the resource groups for the primary and secondary nodes

  10. Start the high availability Services

  11. Bring the resource groups online