SUSE Support

Here When You Need Us

Integration of sap-suse-cluster-connector does not work as expected

This document (7023149) is provided subject to the disclaimer at the end of this document.


SUSE Linux Enterprise Server for SAP Applications Service Pack 4
SUSE Linux Enterprise Server for SAP Applications Service Pack 3
SUSE Linux Enterprise Server for SAP Applications Service Pack 2
SUSE Linux Enterprise Server for SAP Applications Service Pack 1


SAP Netweaver 7.40 Enqueue Replication should be integrated with SLE-HA according to SAP cluster certification by using the sap-suse-cluster-connector.

When testing the setup, an error is shown. If one does as user <sid>adm the following command:

# sapcontrol -nr <instance_nr> -function HACheckFailoverConfig
FAIL: HA product checks not implemented

And, in consequence, no information on versions and configuration of the connector is available. The output is instead empty. This can be seen if one invoked the following command as user <sid>adm:

# sapcontrol -nr <instance_nr> -function HAGetFailoverConfig


Technical Overview:

With SLES-for-SAP 12 two different versions of the SAP SUSE Cluster Connector are shipped.

This connector is used for setting up an HA cluster for SAP Netweaver Enqueue Replication according to the SAP cluster certification.

The appropriate RPM in fact is named  sap-suse-cluster-connector-3.x.x-x.x.noarch.rpm

(with dashes "-" instead of underscores "_").

It is available via the SLES-for-SAP 12 update channels. This version is needed for SAP Netweaver 7.40 and newer.

An older version comes with the SLES-for-SAP 12 DVD and the product channels and will subsequently be installed by default. It is named  sap_suse_cluster_connector-1.x.x-x.x.noarch.rpm

   (with underscores "_").

This version was intended for SAP Netweaver 7.30.

If one faces an error when testing the setup like mentioned above, the most likely reason is that the necessary RPM


is not installed.

How to install the sap-suse-cluster-connector-3.x.x-x.x

The first action should be to check which package is installed, and which are available

As user root one checks with:

# zypper se /sap.suse/
S | Name                       |Summary
  | sap-suse-cluster-connector | SUSE High Availability Setup for SAP Products
i | sap_suse_cluster_connector | Connector between sapstartsrv and corosync/pacem...

# zypper se -t package --details /sap.suse/
S | Name                       | Type    | Version | Arch   | Repository          
  | sap-suse-cluster-connector | package | 3...    | noarch | SLE-12-SP2-SAP-Updates
i | sap_suse_cluster_connector | package | 1...    | noarch | SLE12-SP2-SAP-Pool

if there is no sap-suse-cluster-connector package available then there are no update channels. In this case one should contact the Linux System Administrator and ensure that the proper update channels are available.

The next step is the Removal of the old package

As user root one does:

# zypper rm sap_suse_cluster_connector

then install the new package

# zypper in sap-suse-cluster-connector

# zypper se -t package --details /sap.suse/
S  | Name                       | Type    | Version | Arch   | Repository          
i  | sap-suse-cluster-connector | package | 3...    | noarch | SLE-12-SP2-SAP-Up...
   | sap_suse_cluster_connector | package | 1...    | noarch | SLE12-SP2-SAP-Pool

Alternatively one could just invoke

# zypper in sap-suse-cluster-connector

and then let zypper resolve the error by deinstalling the older sap_suse_cluster_connector.

Activation of new package

it is necessary to restart the sapstartsrv process associated with the SAP Instance.

To do this first the process is identified with

   ps aux | grep <SID>adm | grep sapstartsrv

which results in an output like this, in this example the SID is HA1

   ardmore:~ # ps aux | grep ha1adm | grep sapstartsrv
   ha1adm     561 20.0  0.1 864312 76092 ?        Ssl  16:09   0:00 /usr/sap/HA1/SYS/exe/run/sapstartsrv pf=/sapmnt/HA1/profile/HA1_ASCS00_sapro0as -D -u ha1adm

the process is then killed with

   kill -9 <PID-sapstartsrv>

in the above example

   kill -9 561

and then the log is checked for an entry like

   Jul 03 16:11:58 ardmore SAPInstance(rsc_sap_S97_ASCS97)[12599]: INFO: sapstartsrv for instance HA1-S00 was restarted !

which confirms that the sapstartsrv is restarted

Verification of installed package

As user <sid>adm one does:

# sapcontrol -nr <instance_nr> -function StopService

# sapcontrol -nr <instance_nr> -function StartService <SID>

# sapcontrol -nr <instance_nr> -function HACheckFailoverConfig
state, category, description, comment
SUCCESS, SAP CONFIGURATION, SAPInstance RA sufficient version,
SAPInstance includes is-ers patch

Optional restart of cluster resource agent

Usually the cluster connector should have been tested before integration with the cluster. In case the cluster already is running, the resource agent should be restarted. For details, the respective cluster documentation explains this.

Additional Information

Online documentation

Technical Information Documents


Manual pages



This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:7023149
  • Creation Date: 03-Jul-2018
  • Modified Date:03-Mar-2020
    • SUSE Linux Enterprise Server for SAP Applications

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.