Sample working configuration - SAP HANA on Amazon
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Sample working configuration

The example of a working configuration:

prihana:~ # crm configure show node 1: prihana \ attributes lpa_hdb_lpt=30 hana_hdb_vhost=prihana hana_hdb_site=PRI hana_hdb_srmode=sync hana_hdb_remoteHost=sechana hana_hdb_op_mode=logreplay node 2: sechana \ attributes lpa_hdb_lpt=1605185144 hana_hdb_vhost=sechana hana_hdb_site=SEC hana_hdb_srmode=sync hana_hdb_remoteHost=prihana hana_hdb_op_mode=logreplay primitive res_AWS_IP ocf:suse:aws-vpc-move-ip \ params ip=192.168.10.16 routing_table=rtb-06ca3aca4c58bd17d interface=eth0 profile=cluster \ op start interval=0 timeout=180 \ op stop interval=0 timeout=180 \ op monitor interval=60 timeout=60 \ meta target-role=Started primitive res_AWS_STONITH stonith:external/ec2 \ op start interval=0 timeout=180 \ op stop interval=0 timeout=180 \ op monitor interval=120 timeout=60 \ meta target-role=Started \ params tag=pacemaker profile=cluster primitive rsc_SAPHanaTopology_HDB_HDB00 ocf:suse:SAPHanaTopology \ operations $id=rsc_sap2_HDB_HDB00-operations \ op monitor interval=10 timeout=600 \ op start interval=0 timeout=600 \ op stop interval=0 timeout=300 \ params SID=HDB InstanceNumber=00 primitive rsc_SAPHana_HDB_HDB00 ocf:suse:SAPHana \ operations $id=rsc_sap_HDB_HDB00-operations \ op start interval=0 timeout=3600 \ op stop interval=0 timeout=3600 \ op promote interval=0 timeout=3600 \ op monitor interval=60 role=Master timeout=700 \ op monitor interval=61 role=Slave timeout=700 \ params SID=HDB InstanceNumber=00 PREFER_SITE_TAKEOVER=true DUPLICATE_PRIMARY_TIMEOUT=7200 AUTOMATED_REGISTER=true ms msl_SAPHana_HDB_HDB00 rsc_SAPHana_HDB_HDB00 \ meta clone-max=2 clone-node-max=1 interleave=true clone cln_SAPHanaTopology_HDB_HDB00 rsc_SAPHanaTopology_HDB_HDB00 \ meta clone-node-max=1 interleave=true colocation col_IP_Primary 2000: res_AWS_IP:Started msl_SAPHana_HDB_HDB00:Master order ord_SAPHana 2000: cln_SAPHanaTopology_HDB_HDB00 msl_SAPHana_HDB_HDB00 property SAPHanaSR: \ hana_hdb_site_srHook_SEC=PRIM \ hana_hdb_site_srHook_PRI=SOK property cib-bootstrap-options: \ stonith-enabled=true \ stonith-action=off \ stonith-timeout=600s \ have-watchdog=false \ dc-version="1.1.18+20180430.b12c320f5-3.24.1-b12c320f5" \ cluster-infrastructure=corosync \ last-lrm-refresh=1605184909 rsc_defaults rsc-options: \ resource-stickiness=1000 \ migration-threshold=5000 op_defaults op-options: \ timeout=600

Corosync configuration file:

prihana:~ # cat /etc/corosync/corosync.conf # Please read the corosync.conf.5 manual page totem { version: 2 token: 30000 consensus: 36000 token_retransmits_before_loss_const: 6 crypto_cipher: none crypto_hash: none clear_node_high_bit: yes rrp_mode: passive interface { ringnumber: 0 bindnetaddr: 11.0.1.132 mcastport: 5405 ttl: 1 } transport: udpu } logging { fileline: off to_logfile: yes to_syslog: yes logfile: /var/log/cluster/corosync.log debug: off timestamp: on logger_subsys { subsys: QUORUM debug: off } } nodelist { node { ring0_addr: 11.0.1.132 ring1_addr: 11.0.1.75 nodeid: 1 } node { ring0_addr: 11.0.2.139 ring1_addr: 11.0.2.35 nodeid: 2 } } quorum { # Enable and configure quorum subsystem (default: off) # see also corosync.conf.5 and votequorum.5 provider: corosync_votequorum expected_votes: 2 two_node: 1 }