7.3 Confirmation of Customization Items

The Managed Server transaction needs the following items for customization. Confirm and prepare items required for a cluster transaction which you use.

Table 7.3 Items Required for Customization
Item Name	Windows	Solaris		Linux	HP-UX
Item Name	Windows Server Failover Clustering	PRIMECLUSTER	VERITAS Cluster Server	PRIMECLUSTER	Serviceguard
Logical node name	R	R	R	R	R
Communication service/daemon port number for transaction	R	R	R	R	R
Transaction name	R	R	R	R	R
Logical IP address	R	R	R	R	R
Shared disk for shared data	R	R	R	R	R
Resource type	-	R	-	R	-
Installing user	R	-	-	-	-
Cluster name	R	-	-	-	-
Disk resource of shared disk for shared data	R	-	-	-	-
Network name	R	-	-	-	-
Network for external connections	R	-	-	-	-
Volume Group name	-	-	-	-	R
Generic script	-	R	R	R	R

R: Required item, -: Not required item

Each item is explained below.

Logical node name

Name of logical server for AdvancedCopy Manager.
The user can freely set any logical node name, consisting of alphanumeric characters up to 8 bytes.
Refer to "2.4.2 Cluster Transaction and Local Transaction" for information on the logical node name.

Note

13-character strings of the following list cannot be made into a logical node name for PRIMECLUSTER, VERITAS Cluster Server, or Serviceguard:
audit, cluster, cmdevs, config, daemon, data, java, log, pid, report, samp, sh, tmp

Communication service/daemon port number for transaction

Port number allocated to the communication service/daemon for transactions. Note that the same port number needs to be specified on both the primary and secondary nodes.
Specify the unused number (the number not used for ports of other daemons/services) between 1024 and 65535.

Point

Ensure that the port number of the communication service/daemon for transaction is different from the port number of the communication service/daemon for local transaction or the other communication services/daemons for transaction.

Transaction name

Name of cluster transaction.

Logical IP address

Refer to "Takeover IP address for AdvancedCopy Manager" in "7.1 Resources Required for Clustered System".

Point

When using Windows Server Failover Clustering (if IPv4 address is used) or Serviceguard, check also the subnet mask.

Shared disk for shared data

Refer to "Partitions for storing shared data of AdvancedCopy Manager" in "7.1 Resources Required for Clustered System".

Resource type

Cmdline resource for registering scripts that start or stop services/daemons (generic scripts).

Installing user

User name and password that were used when installing AdvancedCopy Manager.

Cluster name

Cluster name specified in Windows Server Failover Clustering. Refer to the Windows Server Failover Clustering manuals for details.

Disk resource of shared disk for shared data

Disk resource name of shared disk for shared data of AdvancedCopy Manager.

Network name

Dedicated network name for AdvancedCopy Manager that is specified when using a new logical IP address.
AdvancedCopy Manager creates a network resource under this network name. Refer to the Windows Server Failover Clustering manuals for details.

Network for external connections

Network name for external communication specified in Windows Server Failover Clustering, to be specified when using a new logical IP address of IPv4. Refer to the Windows Server Failover Clustering manuals for details.

Volume Group name

Volume Group name of shared disk for shared data.

Generic script

Script for starting or stopping services/daemon.

Create generic scripts (Start/Stop) for the following daemon:

Generic script for AdvancedCopy Manager daemon

Information

As a generic script sample, the following file is stored in the "/opt/FJSVswstf/cluster" directory.

File Name	Explanation
AgtCmdline	Sample file of the Start/Stop script for PRIMECLUSTER Cmdline resource

When using the above file, make sure to copy it to a different directory and use the copied file.

Generic Script for AdvancedCopy Manager Daemon

It is the script to start/stop the AdvancedCopy Manager daemon from the cluster application (transaction). Read the following explanation and create the start/stop script file for the AdvancedCopy Manager daemon.

Processing when starting cluster transactions

Configure the script so that AdvancedCopy Manager service of the Managed Server transaction starts.

Configure the script so that the AdvancedCopy Manager service start command (/opt/FJSVswstf/cluster/AgtStart) is executed when the cluster transaction starts.

Point

In order to have the AdvancedCopy Manager service start command executed, specify the logical node name of the Managed Server transaction to be started in the environment variable SWSTGNODE.

Note

Some cluster software requires a notification of start process result. If the process result notification is required, based on the exit status of the AdvancedCopy Manager service start command, configure an appropriate value to notify the cluster software.

Information required for starting the AdvancedCopy Manager service is as follows.

Item	Explanation
Environment variable SWSTGNODE	Logical node name
Name of AdvancedCopy Manager service start command	/opt/FJSVswstf/cluster/AgtStart
Exit status of AdvancedCopy Manager service start command	Completed successfully: 0 Terminated abnormally: 1

Processing when stopping cluster transactions

Configure the script so that AdvancedCopy Manager service of the Managed Server transaction stops.
Configure so that the following AdvancedCopy Manager service stop command is executed when the cluster transaction stops:

/opt/FJSVswstf/cluster/AgtStop
(However, for Serviceguard, /opt/FJSVswstf/cluster/mcsg/SmgrStop_mcsg)

Point

In order to have the AdvancedCopy Manager service stop command executed, specify the logical node name of the Managed Server transaction to be stopped in the environment variable SWSTGNODE.

Note

Information required for stopping the AdvancedCopy Manager service is as follows.

Item	Explanation
Environment variable SWSTGNODE	Logical node name
Name of AdvancedCopy Manager service stop command	/opt/FJSVswstf/cluster/AgtStop
Exit status of AdvancedCopy Manager service stop command	Completed successfully: 0 Terminated abnormally: 1

Example

The example of creating script as the Start/Stop script for PRIMECLUSTER Cmdline resource is shown below.

#!/bin/sh
SWSTGNODE=acmnode1
export SWSTGNODE

case $1 in
'start')
        /opt/FJSVswstf/cluster/AgtStart
        exit 0 ;;
'stop' )
        /opt/FJSVswstf/cluster/AgtStop
        exit 0 ;;
esac

For register a Cmdline resource, specify "start" to the argument for the Start script, specify "stop" to the argument for the Stop script.
Refer to your cluster software manuals for creating procedure of Start/Stop script.