Novell PLATESPIN ORCHESTRATE 2.0.2 - HIGH AVAILABILITY CONFIGURATION GUIDE 06-17-2009, Configuration Manual

Page: 28 / 36

28 PlateSpin Orchestrate 2.0 High Availability Configuration Guide
no
vd
ocx
(e
n)
13
Ma
y 20
09
3. Shuts down the Orchestrate Server because you specified that this is a High-Availability
configuration
4. Unbinds the cluster IP on this server by issuing the following command internally:
IPaddr2 stop <IP_address_you_provided
>
1.2.6 Running the High Availability Configuration Script
Before you run the high availability configuration script, make sure that you have installed the
PlateSpin Orchestrate Server to a single node of your high availability cluster. For more information,
see
Section 1.2.5, “Installing and Configuring PlateSpin Orchestrate on the First Clustered Node,”
on page 15 .
IMPORTANT: The high availability configuration script asks for the mount point on the Fibre
Channel SAN. Make sure that you have that information (
/zos
) before you run the script.
The high availability script,
zos_server_ha_post_config
, is located in
/opt/novell/
zenworks/orch/bin
with the other configuration tools. You need to run this script on the first node
of the cluster (that is, the node where you installed PlateSpin Orchestrate Server) as the next step in
setting up PlateSpin Orchestrate to work in a high availability environment.
The script performs the following functions:
Š
Verifies that the Orchestrate Server is not running
Š Copies Apache files to shared storage
Š
Copies gmond and gmetad files to shared storage
Š Moves the PlateSpin Orchestrate files to shared storage (first node of the cluster)
Š
Creates symbolic links pointing to the location of shared storage (all nodes of the cluster)
The high availability configuration script must be run on all nodes of the cluster. Make sure that you
follow the prompts in the script exactly; do not misidentify a secondary node in the cluster as the
primary node.
1.2.7 Installing and Configuring Orchestrate Server Packages
on Other Nodes in the Cluster for High Availability
After you have followed the steps to set up the primary node in your planned cluster, you need to set
up the other nodes that you intend to use for failover in that cluster. Use the following sequence as
you set up other cluster nodes (the sequence is nearly identical to setting up the primary node):
1. Make sure that the SLES 10 SP2 nodes have the high availability pattern. For information, see
Section 1.2.2, “Installing the High Availability Pattern for SLES 10,” on page 12 .
2. Make sure that the SLES 10 SP2 nodes have been configured with time synchronization. For
information, see Section 1.2.3, “Configuring Nodes with Time Synchronization and Installing
Heartbeat 2 to Each Node,” on page 13 .
3. Set up OCFS2 on each node so that the nodes can communicate with the SAN, making sure to
designate
/zos
as the shared mount point. For more information, see Section 1.2.4, “Setting Up
OCFS2,” on page 14 .