Skip to Content

HANA specific Cluster Configuration

The next steps are the configuration of the SUSE HANA specific services. These steps need to be executed on one node of the cluster. It's typically the first node.

They are described in section 5.3 of the SUSE Setup Guide (SAP HANA SR Performance Optimized Scenario)

Modify the first step 5.3.1 (Cluster bootsrap and more) requires an AWS specific stonith-action. Use this file for an installation on AWS:

suse01:~ # vi crm-bs.txt
# enter the following to crm-bs.txt
property $id="cib-bootstrap-options" \
              no-quorum-policy="ignore" \
              stonith-enabled="true" \
              stonith-action="poweroff" \
stonith-timeout="150s"
rsc_defaults $id="rsc-options" \
resource-stickiness="1000" \
migration-threshold="5000"
op_defaults $id="op-options" \ timeout="600"

The setting poweroff forces the agents to shutdown the instance. This is desirable in order to avoid split brain scenarios on AWS.

Add the configuration to the cluster.

suse01:~ # crm configure load update crm-bs.txt

Ignore the following sections for an AWS installation

  • 5.3.2 (STONITH device) not needed for AWS
  • 5.3.3 (Using IPMI as fencing mechanism) not used in AWS configurations
  • 5.3.4 (Using other fencing mechanisms) This section explains that there are other mechanism as we use them for AWS 

Implement the following sections as described in the manual

  • 5.3.5 SAPHanaTopology
  • 5.3.6 SAPHana

Ignore the sections

  • 5.3.7 (Virtual IP address). This section does not apply for AWS installations
  • 5.3.8 (Constraints). This section is different on AWS. Use the next page to perform the configuration of constraints


book | by Dr. Radut