SAP HA Interface Script Connector for Pacemaker Based Cluster Setups

Purpose

This repo provides the componnents to integrate a SAP environment managed by a Pacemaker based cluster with the HA Interface provided by SAP.

This allows that SAP instance which are manged by a cluster to be controlled by SAP management tools like the SAP MMC. Also SAP tools like SUM are able to notifiy the cluster that during an update of an SAP instance activieties that can result in a restart of a SAP innstance which should not be acted upon by the cluster.

Resources

Using sap_vendor_cluster_connector for interaction between cluster framework and sapstartsrv

Manual Page of sap_vendor_cluster_connector

Important Resources about the HA-Interface Certification for Partners

SAP Note 1693245 - SAP HA Script Connector Library

SAP Note 1822055 - Enhanced SAP HA library interface

SAP Note 2464065 - Check of automatic maintenance mode for HA solutions

Installation

• copy the sap_cluster_connector script to /usr/bin/
• create the directory /usr/share/sap_cluster_connector/
• copy the run_checks script to /usr/share/sap_cluster_connector/
• copy the checks directory and all its contents to /usr/share/sap_cluster_connector/
• make sure /usr/bin/sap_cluster_connector, /usr/share/sap_cluster_connector/run_checks and all scripts in /usr/share/sap_cluster_connector/checks/ are executable by all users:

# chmod a+x /usr/bin/sap_cluster_connector
# chmod a+x /usr/share/sap_cluster_connector/run_checks
# chmod a+x /usr/share/sap_cluster_connector/checks/*

Cluster Configuration

• activate record-pending resource operation option:
  pcs (RHEL): # pcs resource op defaults record-pending=true
  crmsh (SLES): # crm configure op_defaults record-pending=true
  Note: on pacemaker 2.x and some pacemaker 1.x versions shipped with some Linux distributionsrecord-pending is already activated by default. Please check the release notes of your pacemaker version to see if this is the case or if record-pending needs to be activated manually.

• add SIDadm user to "haclient" group on each node:

# usermod -a -G haclient rh2adm

SAP Configuration

• make sure that the SAP HA Script Connector Library (saphascriptco.so) is available as part of the SAP Kernel of the SAP installation

• add the following to the instance profile of each SAP instance that should be managed via the SAP HA interface (for example /sapmnt/RH2/profile/RH2_ASCS00_rh2ascs):

service/halib = $(DIR_CT_RUN)/saphascriptco.so
service/halib_cluster_connector = /usr/bin/sap_cluster_connector

• restart the Instance (including the sapstartsrv for that instance)

Usage

The cluster connector is normally called automatically by the sapstartsrv of a SAP instance in case an action on the SAP instance is performed via the SAP management tools that requires some interaction with the cluster.

To verify that the cluster connector is working correctly it is also possible to run the sap_cluster_connector script manually or to trigger its execution via sapcontrol.

Examples for running sap_cluster_connector directly

Basic initialization:

# /usr/bin/sap_cluster_connector init

Get some basic information about the cluster product used:

#/usr/bin/sap_cluster_connector gvi --out /tmp/gvi.txt

Look-up the current cluster node and all possible cluster nodes to run the cluster resource named rsc_sap_C11_D02:

# /usr/bin/sap_cluster_connector lsn --out /tmp/lsn.txt --res rsc_sap_C11_D02

Look-up the SAP instance number 02 of the SAP system C11 and return the cluster resource name:

# /usr/bin/sap_cluster_connector lsr --out /tmp/lsr.txt --sid C11 --ino 02

Start the cluster resource rsc_sap_C11_D02:

# /usr/bin/sap_cluster_connector fra --res rsc_sap_C11_D02 --act start

Check if the cluster action to start the SAP instance for system C11 and instance number 02 is already in progress:

# /usr/bin/sap_cluster_connector cpa --res rsc_sap_C11_D02 --act start

Move the cluster resource rsc_sap_C11_D02 to the cluster node node2:

# /usr/bin/sap_cluster_connector fra --res rsc_sap_C11_D02 --act migrate --node node2

Check the status of maintenance mode:

# /usr/bin/sap_cluster_connector smm --out /tmp/smm.txt --sid C11 --ino 02 --mod -1

Activate maintenance mode:

# /usr/bin/sap_cluster_connector smm --out /tmp/smm.txt --sid C11 --ino 02 --mod 1

Deactivate maintenance mode:

# /usr/bin/sap_cluster_connector smm --out /tmp/smm.txt --sid C11 --ino 02 --mod 0

Examples for calling sap_cluster_connector via sapcontrol

Perform a check of the HA configuration:

# /usr/sap/C11/D02/exe/sapcontrol -nr 02 -function HACheckConfig

Trigger the failover of a SAP instance to another cluster node:

# /usr/sap/C11/D02/exe/sapcontrol -nr 02 -function HAFailoverToNode

Check status of maintenance mode:

# /usr/sap/C11/D02/exe/sapcontrol -nr 02 -function HACheckMaintenanceMode

Activate/Deactivate maintenance mode:
(if the '1' at the end is ommited sapstartsrv will attempt to carry out the command on all instances of the SAP environment, otherwise the command will only be run for the instance with the given instance number):

# /usr/sap/C11/D02/exe/sapcontrol -nr 02 -function HASetMaintenanceMode [1|0] {1}

TODO

• add check for record-pending option
• code cleanup