| Sun Mainframe Transaction Processing Software High Availability Data Service for Sun Cluster |    
|
| Sun Mainframe Transaction Processing Software High Availability Data Service for Sun Cluster |
|
|
Installing and Configuring the Sun MTP HA Data Service |
This document provides instructions for setting up and administering the Sun MTP high availability (HA) data service on your Sun Cluster nodes. It contains the following topics:
The Sun MTP HA data service works with the Sun Cluster hardware and software to make one or more Sun MTP regions highly available.
A Sun Cluster system can host multiple Sun MTP HA data service instances distributed across the entire cluster. Even when the same cluster node hosts several instances, each instance uses only the resources available on that node.
The Sun MTP data service starts, stops, restarts, and fails over the Sun MTP application among the nodes of the cluster in response to cluster events, such as administrative actions, application failures, or cluster node failure.
The Sun MTP application restart is managed by the Sun Cluster resource group manager (RGM).
If the Sun MTP application deaths exceed the failure count within the failure time window, the resource group containing the Sun MTP application is automatically failed over to another cluster node.
The fault monitor is provided using the probe method.
The Sun MTP data service provides:
For general information about data services, resource groups, resources, and other related topics, refer to the Sun Cluster 3.1 Concepts document.
TABLE 1 lists the tasks for installing and configuring Sun MTP HA data service. Perform these tasks in the order that they are listed.
|
Chapter 1 of Sun Cluster 3.1 Data Service Planning and Administration Guide Planning the Sun MTP HA Data Service Installation and Configuration |
|
|
Register and configure Sun MTP HA data service as a failover data service |
|
|
Verify Sun MTP HA data service Installation and configuration |
|
To upgrade a previous version of the Sun MTP HA data service, see Upgrading the Sun MTP HA Data Service.
This section contains the information you need to plan your Sun MTP HA data service installation and configuration.
|
Note - Check the SunSolveSM web site at http://sunsolve.sun.com on a regular basis for any patches that are available, and apply the recommended patches. Refer to the patch README files for additional information about latest releases and any software interdependencies. |
To use this version of the Sun MTP HA data service, your environment must have the following:
If you are also using Sun MBM and the Sun MBM HA data service, you must use Sun MBM 10.0.0, minimum patch level of 7, and the Sun MBM HA data service, release 1.0, minimum patch level of 1. Make sure to configure the Sun MBM HA data service as described in the Sun Mainframe Batch Manager Software High Availability Data Service for Sun Cluster document (part number 817-3505-10).
This section describes the configuration components that have been qualified with this release. It also lists components and packages that will be qualified in a future release, and components or functionality that are not supported.
The Sun MTP HA data service has been qualified with the following components and functionality:
The following components and functionality have not yet been qualified:
The following Sun mainframe rehosting software components will be qualified when there are highly available versions:
The following functionality is not supported:
Your data service configuration might not be supported if you do not observe these guidelines.
|
Note - For restrictions that apply to all data services, refer to the Sun Cluster Release Notes. |
This section describes the tasks you must perform before you install and configure the Sun MTP HA data service.
Contact your system administrator to create the Sun MTP administrator (using the useradd command), if one does not already exist. This user is specified in the EMP_ADMIN property when the data service is registered. See Registering and Configuring the Sun MTP HA Data Service.
|
Note - The Sun MTP administrator's login shell must be Korn shell (/bin/ksh). |
Because the Sun MTP HA data service uses the su EMP_ADMIN command when starting and stopping the Sun MTP system, the su(1M) command must not refer to the network information name service (NIS/NIS+). This is because NIS/NIS+ might not be available because of a failure of the public network on the cluster node, and it is, therefore, a potential single point of failure for a Sun Cluster system.
The following entries in the /etc/nsswitch.conf configuration file removes the dependency for contacting an NIS/NIS+ master server over public network adapters. However, the functionality these fields provide will not be available from the NIS server. Adding the entries ensures that the su command does not refer to the NIS/NIS+ name services if the network information name service is unavailable.
passwd: files [NOTFOUND=return] nis group: files [NOTFOUND=return] nis publickey: files [NOTFOUND=return] nis project: files [NOTFOUND=return] nis |
This section describes how to update the region setup file to include the appropriate startup options. It also provides information about where to maintain the region setup file in the Sun Cluster environment.
To ensure that the Sun MTP region is restarted with the appropriate unikixmain (kixstart) options, add the HA_MTP_START_OPTS environment variable to your region's setup file. This setup file is specified in the EMP_SETUP property when the data service is registered. See Registering and Configuring the Sun MTP HA Data Service.
The last line in the following example setup file shows the HA_MTP_START_OPTS environment variable. The value of this variable is a list of unikixmain options you normally use to start the region. The value must be enclosed in double quotes.
|
Caution - Make sure to include $PATH in the PATH statement so that the inherited Sun Cluster environment is not overridden. |
The setup file is dynamically loaded at execution time by the Sun MTP probe process. Changes to the setup file while the Sun MTP resource is enabled can result in unpredictable behavior. Therefore, if the setup file is located on the HAStoragePlus file service, you must disable the Sun MTP resource before changing any information in the setup file.
1. Log in to the system as superuser.
2. Disable the resource by typing the following command:
3. Edit the setup file and save it.
4. Enable the resource by typing the following command:
|
Note - If you maintain the region setup file on the HAStoragePlus file service, it is a good idea to locate it in the $KIXSYS directory. |
A less preferable alternative is to have a copy of the setup file on each local node. This alternative requires the contents of the setup files to be consistent. The advantage of maintaining separate setup files is that you can modify the setup file on the secondary node without disabling the resource on the primary node. If you want to keep separate setup files, use the following procedure to maintain them:
1. On the secondary node, modify the setup file.
2. As superuser, move the Sun MTP resource to the secondary node.
3. Check that Sun MTP is up and running with the new setup file.
4. Move the Sun MTP resource back to the primary node.
The installation procedure for Sun MTP in a Sun Cluster environment is the same as the normal installation procedure. Refer to the Sun Mainframe Transaction Processing Software Installation Guide for detailed information.
Also, refer to Usage Considerations, which contains information about where to locate the Sun MTP binaries ($UNIKIX), configuration directory ($KIXSYS), and the region setup file. The $UNIKIX directory is specified in the EMP_BASEDIR property when the data service is registered. See Registering and Configuring the Sun MTP HA Data Service.
Make sure to verify your installation on each node as described in the Sun Mainframe Transaction Processing Software Installation Guide.
When upgrading Sun MTP in the Sun Cluster environment, you must disable the Sun MTP resource before performing the normal upgrade process. Refer to the Sun Mainframe Transaction Processing Software Installation Guide for information about upgrading the software.
|
Note - Make sure to upgrade Sun MTP on each node of the cluster. |
You must be superuser to perform this procedure.
1. Load the distribution CD into the CD-ROM, or download the SUNWscmtp package from SunSolve.
2. Run the pkgadd command on each cluster node on which the data service will be configured to run.
Refer to the pkgadd(1M) man page for information on how to install a package using this administrative command.
The installation creates the /opt/SUNWscmtp directory, which contains the following:
The Sun MTP HA data service must be registered and configured as a failover data service. To ensure optimal performance and data integrity, you must associate the data service with the HAStoragePlus file service (SUNW.HAStoragePlus).
You must be superuser to perform the procedures in this section.
1. Register the SUNW.scmtp resource type:
|
Specifies the predefined resource type name for your data service. |
2. Create the SUNW.HAStoragePlus resource type:
4. Define the logical host name.
a. Make sure that the logical host name is defined in the cluster's /etc/hosts file.
b. Set up the logical host name on the client system.
5. Add the logical host name to the failover resource group:
|
Specifies a host name that can apply to any node in the cluster, and which is assigned dynamically. |
6. Create a disk device group resource:
# scrgadm -a -j disk-device-group-name -g resource-group-name \ -t SUNW.HAStoragePlus -x FileSystemMountPoints=ha-filesystem \ -x AffinityOn=True |
The -x options used in this command are extension properties for SUNW.HAStoragePlus.
|
Note - The -x FileSystemMountPoints option identifies the cluster failover file system. |
7. Turn the resource group online:
8. Create the Sun MTP application resource in the failover resource group:
where the -x values are the following extension properties:
9. Turn the Sun MTP resource online:
See Configuring the Sun MTP HA Data Service Properties for a complete list of the extension and standard properties and their valid values.
The following example shows the commands needed to register and configure the mtp-rg-1 resource group and associate it with a SUNW.HAStoragePlus resource type.
1. Log in as the Sun MTP administrator.
2. Type the following command to bring online the resource group where the Sun MTP application resource is defined:
where the -Z option enables all resources of the resource group and their monitors, and moves the resource group into the managed state.
3. Shut down the Sun MTP application by killing one of the Sun MTP system processes, such as the unikixstrt process.
4. Verify that Sun Cluster restarts the region.
Execute the following command to move the Sun MTP application to another node:
1. Execute the following command to determine if the Sun MTP application is online on the selected cluster node:
2. Confirm that the resource group is now online on the new primary node.
The Sun MTP HA data service contains a built-in fault monitor (or fault probe). The fault monitor is a process that probes the health of the Sun MTP HA data service.
The fault monitor is invoked by the RGM when you bring the resource group and its associated resources online. This invocation causes the RGM to internally call the Monitor_Start method for the Sun MTP HA data service.
The fault monitor is stopped by RGM when you bring the resource group and its associated resources offline. This invocation causes the RGM to internally call the Monitor_Stop method for the Sun MTP HA data service.
The fault monitor uses the following standard properties:
You might be able to tune these properties. Refer to the Sun Cluster documentation to review or set resource properties. Also see Configuring the Sun MTP HA Data Service Properties to review or set resource properties.
The fault monitor uses the following Sun MTP extension properties:
You might be able to tune these properties. Refer to Configuring the Sun MTP HA Data Service Properties to review or set extension properties.
The monitor functionality of the Sun MTP HA data service consists of two components: the Process Monitor Facility (PMF) and the fault monitor.
|
Note - These components are not activated if the Monitor extended property is set to None. |
PMF monitors the abnormal exit of all Sun MTP system processes. On any abnormal exit, the PMF tries to restart the data service up to PMF_Retry_Count times in a period of Retry_interval. If Sun MTP crashes more often than the retry interval period, the PMF stops trying to restart it.
This feature relies on the Sun MTP main server process (unikixmain) monitoring capabilities. If any Sun MTP system process dies, unikixmain evaluates whether the failure is critical, and decides whether to restart the dead process or shut down Sun MTP.
The fault monitor performs health checks on the data service. The logic followed by the fault monitor is as follows:
1. Sleep Probe_start_interval number of seconds before going into an infinite loop.
2. Sleep Thorough_probe_interval number of seconds.
3. Perform health check under the time out property Probe_timeout using the Sun MTP entry point mtp_probe.
The mtp_probe command checks the health of the Sun MTP system by performing the following checks according to the options set in the Monitor extended property:
Typically, you configure properties using the options on the scrgadm command at the time you create the Sun MTP resource.
The following table describes the standard tunable properties that you can configure for the Sun MTP HA data service. Standard properties are default resource properties. To set or modify this property, use the -y parameter=value option.
The following table describes the tunable extension properties that you can configure for the Sun MTP HA data service. Extension properties are additional properties specific to the Sun MTP resource. To set or modify this property, use
the -x parameter=value option.
The terms used in the tables are defined as follows:
Property: Name of the resource property.
Description: A brief description of the property.
Default: The default value for the property.
Tunable: Indicates when the cluster administrator can set or modify the value of this property for the Sun MTP resource. Values that allow administrator tuning are: Anytime (at any time), At creation (only when the resource is created), or When disabled (when the resource is offline).
Optional: These properties are set to the default values at creation time. They can be changed after the resource is created.
Required: The property must be specified when creating the resource.
When managing Sun MTP as a Sun Cluster resource, Sun Cluster management facilities must be used to start and stop the region. Do not use the standard Sun MTP commands, such as kixstart, unikixmain, kixclean, and kixstop. Using these commands will conflict with the Sun Cluster management facilities, and might fail to provide a highly available operational environment.
1. Log in to the system as the superuser.
2. Disable and remove all Sun MTP resources on the entire cluster.
Type the following commands for each resource, using the names you gave to your resources when you originally configured them:
3. Remove the Sun MTP HA data service.
4. Remove the SUNWscmtp package from each node of the cluster.
5. Verify that the package removal was successful for each node of the cluster by executing the following command:
An error message indicating that the directory does not exist should be displayed.
6. Install the new SUNWscmtp package.
See Installing the Sun MTP HA Data Service.
This procedure enables you to run the Micro Focus COBOL Animator on a node in a Sun Cluster environment. However, due to the Sun Cluster restriction on animating processes while they are being monitored by PMF, using Animator to debug COBOL programs on a production Sun Cluster region is strongly discouraged.
|
Caution - Failure to observe this guideline could result in data corruption. |
1. Log in to the system as superuser.
2. Change directory to $UNIKIX/scbin.
3. Change the owner of the kxchg_dbg module to root:
4. Change permissions on the kxchg_dbg module:
|
Note - This procedure must be performed on each node where you are using Sun MTP and Animator. |
If you encounter problems that cannot be resolved by means of the Sun Cluster or Sun MTP troubleshooting facilities, run the Sun Explorer facility (SUNWexplo). You can download the SUNWexplo package, including information on installing and using it, from the SunSolve web site:
Also run the kixsnap utility on the node where Sun MTP is running.
Both utilities generate zip files.
Collect all the output and send the files, along with the information noted in Help, to your authorized service provider.
| Sun Mainframe Transaction Processing Software High Availability Data Service for Sun Cluster | 817-3504-12 |
|
Copyright © 2004, Sun Microsystems, Inc. All rights reserved.
To Install the Sun MTP HA Data Service