From 5f41baccf62048cfd7419344b8fbab5a7b6bdb74 Mon Sep 17 00:00:00 2001 From: lpinne Date: Wed, 10 Jan 2024 12:33:38 +0100 Subject: [PATCH] removed convergent-mediation draft --- DC-SAP-convergent-mediation-ha-setup-sle15 | 18 - ...rgent-mediation-ha-setup-sle15-docinfo.xml | 77 -- ...P-convergent-mediation-ha-setup-sle15.adoc | 667 ------------------ adoc/SAPNotes-convergent-mediation.adoc | 73 -- adoc/Var_SAP-convergent-mediation.adoc | 67 -- 5 files changed, 902 deletions(-) delete mode 100644 DC-SAP-convergent-mediation-ha-setup-sle15 delete mode 100644 adoc/SAP-convergent-mediation-ha-setup-sle15-docinfo.xml delete mode 100644 adoc/SAP-convergent-mediation-ha-setup-sle15.adoc delete mode 100644 adoc/SAPNotes-convergent-mediation.adoc delete mode 100644 adoc/Var_SAP-convergent-mediation.adoc diff --git a/DC-SAP-convergent-mediation-ha-setup-sle15 b/DC-SAP-convergent-mediation-ha-setup-sle15 deleted file mode 100644 index 577bcc2c..00000000 --- a/DC-SAP-convergent-mediation-ha-setup-sle15 +++ /dev/null @@ -1,18 +0,0 @@ -MAIN="SAP-convergent-mediation-ha-setup-sle15.adoc" - -ADOC_TYPE="article" - -ADOC_POST="yes" - -ADOC_ATTRIBUTES="--attribute docdate=2022-02-28" - -# stylesheets -STYLEROOT=/usr/share/xml/docbook/stylesheet/sbp -FALLBACK_STYLEROOT=/usr/share/xml/docbook/stylesheet/suse2022-ns - -XSLTPARAM="--stringparam publishing.series=sbp" - -ROLE="sbp" -#PROFROLE="sbp" - -DOCBOOK5_RNG_URI="http://docbook.org/xml/5.2/rng/docbookxi.rnc" diff --git a/adoc/SAP-convergent-mediation-ha-setup-sle15-docinfo.xml b/adoc/SAP-convergent-mediation-ha-setup-sle15-docinfo.xml deleted file mode 100644 index 8ba32678..00000000 --- a/adoc/SAP-convergent-mediation-ha-setup-sle15-docinfo.xml +++ /dev/null @@ -1,77 +0,0 @@ - - - https://github.com/SUSE/suse-best-practices/issues/new - SAP Convergent Mediation ControlZone High Availability Cluster - Setup Guide SLES15 - - - - - - - SUSE Linux Enterprise Server for SAP Applications - 15 - - -SUSE Best Practices -SAP - -SUSE Linux Enterprise Server for SAP Applications 15 -SAP HANA - - - - - Fabian - Herschel - - - Distinguished Architect SAP - SUSE - - - - - Lars - Pinne - - - Systems Engineer - SUSE - - - - - - - - - - - - - - - - - - - - - SUSE® Linux Enterprise Server for SAP Applications is - optimized in various ways for SAP* applications. - This document explains how to deploy an SAP - Convergent Mediation ControlZone High Availability Cluster solution. - It is based on SUSE Linux Enterprise Server for SAP Applications 15. The concept however can also be used with - newer service packs of SUSE Linux Enterprise Server for SAP Applications. - - - Disclaimer: - Documents published as part of the SUSE Best Practices series have been contributed voluntarily - by SUSE employees and third parties. They are meant to serve as examples of how particular - actions can be performed. They have been compiled with utmost attention to detail. - However, this does not guarantee complete accuracy. SUSE cannot verify that actions described - in these documents do what is claimed or whether actions described have unintended consequences. - SUSE LLC, its affiliates, the authors, and the translators may not be held liable for possible errors - or the consequences thereof. - - diff --git a/adoc/SAP-convergent-mediation-ha-setup-sle15.adoc b/adoc/SAP-convergent-mediation-ha-setup-sle15.adoc deleted file mode 100644 index f19b1e12..00000000 --- a/adoc/SAP-convergent-mediation-ha-setup-sle15.adoc +++ /dev/null @@ -1,667 +0,0 @@ -:docinfo: - -:localdate: - -// Document Variables -:slesProdVersion: 15 -// - -= SAP Convergent Mediation ControlZone High Availability Cluster: Setup Guide - -// Revision {Revision} from {docdate} -// Standard SUSE includes -// include::common_copyright_gfdl.adoc[] - -// :toc: - -include::Variables_s4_2021.adoc[] -// - -//// -TODO PRIOx: example -//// - -== About this guide - -The following sections focus on background information and the purpose of the document at hand. - -=== Introduction - -{sles4sapReg} is the optimal platform to -run {sapReg} applications with high availability. Together with a redundant layout -of the technical infrastructure, single points of failure can be eliminated. - -TODO - - -=== Abstract - -This guide describes planning, setup, and basic testing of {sles4sap} 15 (TODO variable) -as an high availability cluster for an {sap} Convergent Mediation ControlZone platform. - -TODO - -From the application perspective the following variants are covered: - -- Convergent Mediation platform service running alone - -- Convergent Mediation platform and UI services running together - -- Convergent Meditation binaries stored and started on central NFS (not recommended) - -- Convergent Meditation binaries copied to and started from local disks - -- TODO - -From the infrastructure perspective the following variants are covered: - -- 2-site cluster with disk-based SBD fencing - -- 3-site cluster with disk-based or diskless SBD fencing, not explaind in detail here - -- Other fencing is possible, but not explained here - -- On-premises deployment on physical and virtual machines - -- Public cloud deployment (usually needs additional documentation on cloud specific details) - -Deployment automation simplifies roll-out. There are several options available, particularly on public cloud platfoms. Ask your public cloud provider or your SUSE contact for details. - - -[id="sec.resources"] -=== Additional documentation and resources - -Several chapters in this document contain links to additional documentation resources that -are either available on the system or on the Internet. - -For the latest product documentation updates, see https://documentation.suse.com/. - -More whitepapers, guides and best practices documents referring to SUSE Linux Enterprise Server and SAP can be -found and downloaded at the SUSE Best Practices Web page: -https://documentation.suse.com/sbp/sap/ - -Here you can access guides for {SAPHANA} system replication -automation and High Availability (HA) scenarios for {SAPNw} and {s4hana}. - -Additional resources, such as customer references, brochures or flyers, can be found at -the {sles4sap} resource library: -https://www.suse.com/products/sles-for-sap/resource-library/. - -Supported high availability solutions by {sles4sap} overview: -https://documentation.suse.com/sles-sap/sap-ha-support/html/sap-ha-support/article-sap-ha-support.html - -Lastly, there are manual pages shipped with the product. - - -// Standard SUSE includes -=== Feedback -include::common_intro_feedback.adoc[] - - - -== Overview - -TODO -Convergent Mediation (CM) - -The CM ControlZone platform is responsible for providing services to other instances. -Several platform containers may exist in a CM system, for high availability, -but only one is active at a time. The CM central ControlZone UI is used to query, edit, -import, and export data. - -NFS shares with work directories can be mounted statically on all nodes. The HA cluster -does not need to control that filesystems. -TODO - -=== High availabilty for the Convergent Mediation ControlZone platform - -TODO -The ControlZone services platform, and optinally UI, are handled as active/passive -resources. The related virtual IP adress is managed by the HA cluster as well. -The HA cluster does not control filesystems used by the ControlZone services. However, -optionally this filesystem could be monitored. - -TODO picture - -=== Handling of NFS failures - -A shared filesystem migth be statically mounted by OS on both cluster nodes. This -filesystem holds work directories. It must not be confused with the ControlZone -application itself. Client-side write caching has to be disabled. - -A Filesystem resource is configured for a bind-mount of the real NFS share. This resource -is grouped with the ControlZone platform and IP address. In case of filesystem failures, -the whole group gets restarted. No mount or umount on the real NFS share is done. - -TODO this filesyetm resource is optional - - -=== Scope of this document - -The document at hand explains how to: - -TODO - -[id="sec.prerequisites"] -=== Prerequisites - -TODO Requirements of Convergent Mediation ControlZone - -TODO Requirements of the SUSE high availability solution for CM ControlZone are: - -- Convergent Mediation ControlZone version 9.0.0.0 or higher is installed and -configured on both cluster nodes. If the software is installed into a shared NFS -filesystem, the binaries are copied into both cluster nodes´ local filesystems. - -- Only one ControlZone instance per Linux cluster. - -- Technical users and groups are defined locally in the Linux system. If users are -resolved by remote service, local caching is neccessary. Substitute user (su) to -the mz-user (e.g. "mzadmin") needs to work reliable and without customized actions or -messages. - -- Strict time synchronization between the cluster nodes, e.g. NTP. All nodes of a -cluster have configured the same timezone. - -- Needed NFS shares (e.g. /mnt/platform/) mounted statically or by automounter. -No client-side write caching. - -- The RA monitoring operations have to be active. - -- RA runtime almost completely depends on call-outs to controlled resources, OS and -Linux cluster. The infrastructure needs to allow these call-outs to return in time. - -- The ControlZone application is not started/stopped by OS. Thus there is no SystemV, -systemd or cron job. - -- As long as the ControlZone application is managed by the Linux cluster, the application -is not started/stopped/moved from outside. Thus no manual actions are done. - -- Interface for the RA to the ControlZone platform is the command mzsh. -The mzsh is accessed on the cluster nodes´ local filesystems. The mzsh is called -with the arguments startup, shutdown, status and kill. Its output is parsed by the RA. -Thus the command and its output needs to be stable. - -- The mzsh is called on the active node with a defined interval for regular resource -monitor operations. It also is called on the active or passive node in certain situations. Those calls might run in parallel. - -- TODO - - -=== The setup procedure at a glance - -TODO - -- Checking the operating system -// [id="sec.os-basic-check"] - -- Checking the HA cluster basic setup -// [id="sec.ha-basic-check"] - -- Preparing the OS for NFS monitoring -// [id="sec.ha-filsystem-monitor"] - -- Adapting the cluster basic configuration -// [id="sec.basic-ha-cib"] - -- Configuring the ControlZone cluster resources -// [id="sec.cm-ha-cib"] - -- Testing the HA cluster -// [id="sec.testing"] - - -== Checking the operating system and the HA cluster basic setup - -TODO - -[id="sec.os-basic-check"] -=== Checking the operating system - -TODO on both nodes - -==== IP addresses and virtual names - -Check if the file _/etc/hosts_ contains at least the following address resolutions. -Add those entries if they are missing. - -[subs="attributes"] ----- -{myIPNode1} {myNode1} -{myIPNode2} {myNode2} - -{myVipAAscs} sap{mySidLc}as ----- - -==== Mount points and NFS shares - -TODO - -==== Linux user and group number scheme - -TODO - -==== Password-free ssh login - -TODO - -==== Time synchronisation - -TODO - -[id="sec.ha-basic-check"] -=== Checking the HA cluster basic setup - -TODO on both nodes - -==== Watchdog - -TODO - -==== SBD device - -TODO - -==== Corosync cluster communication - -TODO - -==== systemd cluster services - -TODO - -==== Basic Linux cluster configuration - -TODO on one node - - -== Integrating Convergent Mediation ControlZone with the Linux cluster - -TODO - -[id="sec.ha-filsystem-monitor"] -=== Preparing the OS for NFS monitoring - -TODO on both nodes - -[id="sec.basic-ha-cib"] -=== Adapting the cluster basic configuration - -TODO - -==== Adapting cluster bootstrap options and resource defaults - -TODO - -[subs="specialchars,attributes"] ----- -property cib-bootstrap-options: \ - have-watchdog=true \ - cluster-infrastructure=corosync \ - cluster-name=hacluster \ - dc-deadtime=20 \ - stonith-enabled=true \ - stonith-timeout=150 \ - priority-fencing-delay=30 \ - stonith-action=reboot -rsc_defaults rsc-options: \ - resource-stickiness=1 \ - migration-threshold=3 \ - failure-timeout=86400 -op_defaults op-options: \ - timeout=120 ----- - -==== Adapting SBD STONITH resource - -TODO for priority fencing - -[subs="specialchars,attributes"] ----- -primitive rsc_stonith_sbd stonith:external/sbd \ - params pcmk_delay_max=15 ----- - -[id="sec.cm-ha-cib"] -=== Configuring ControlZone cluster resources - -TODO - -==== Virtual IP address resource - -TODO - -[subs="specialchars,attributes"] ----- -primitive rsc_ip_{mySid} ocf:heartbeat:IPaddr2 \ - op monitor interval=60 timeout=20 on-fail=restart \ - params ip={myVipAAscs} ----- - -See manual page ocf_heartbeat_IPAddr2(7) for more details. - -==== Filesystem resource (only monitoring) - -TODO - -[subs="specialchars,attributes"] ----- -primitive rsc_fs_{mySid} ocf:heartbeat:Filesystem \ - params device=/mnt/platform/check/ directory=/mnt/check/ \ - fstype=nfs4 options=bind,rw,noac,sync,defaults \ - op monitor interval=120 timeout=120 on-fail=restart \ - op_params OCF_CHECK_LEVEL=20 \ - op start timeout=120 \ - op stop timeout=120 \ - meta target-role=stopped ----- - -See manual page ocf_heartbeat_Filesystem(7) for more details. - -==== SAP Convergent Mediation ControlZone resource - -TODO - -[subs="specialchars,attributes"] ----- -primitive rsc_cz_{mySid} ocf:suse:SAPCMControlZone \ - params SERVICE=platform MZSHELL=/opt/mz/bin/mzsh \ - op monitor interval=60 timeout=120 on-fail=restart \ - op start timeout=120 interval=0 \ - op stop timeout=120 interval=0 \ - meta priority=100 maintenance=true ----- - -// [cols="1,2", options="header"] -[width="100%",cols="30%,70%",options="header"] -.Table Description of important resource agent parameters -|=== -|Name -|Description - -|USER -|OS user who calls mzsh, owner of $MZ_HOME. -Optional. Unique, string. Default value: "mzadmin". - -|SERVICE -|The ControlZone service to be managed by the resoure agent. -Optional. Unique, [ platform \| ui ]. Default value: "platform". - -|MZSHELL -|Path to mzsh. -Optional. Unique, string. Default value: "/usr/bin/mzsh". - -|CALL_TIMEOUT -|Define timeout how long calls to the ControlZone platform for checking the -status can take. If the timeout is reached, the return code will be 124. If you -increase this timeout for ControlZone calls, you should also adjust the monitor -operation timeout of your Linux cluster resources. (Not yet implemented.) -Optional. Unique, integer. Default value: 60. - -|SHUTDOWN_RETRIES -|Number of retries to check for process shutdown. Passed to mzsh. -If you increase the number of shutdown retries, you should also adjust the stop -operation timeout of your Linux cluster resources. (Not yet implemented.) -Optional. Unique, integer. Default: mzsh builtin value. -|=== - -See manual page ocf_suse_SAPCNControlZone(7) for more details. - -==== ControlZone resource group - -TODO - -[subs="specialchars,attributes"] ----- -group grp_cz_{mySid} rsc_fs_{mySid} rsc_ip_{mySid} rsc_cz_{mySid} \ - meta maintenance=true ----- - -=== Activating the cluster resources - -TODO - -[subs="specialchars,attributes"] ----- -# crm resource maintenance grp_cz_{mySid} off ----- - -=== Checking the cluster resource configuration - -TODO - -[subs="specialchars,attributes"] ----- -# crm_mon -1r ----- - -TODO Congratulations! - -[subs="specialchars,attributes"] ----- -# crm configure show ----- - -[id="sec.testing"] -=== Testing the cluster - -TODO - -==== Manually restarting ControlZone resources in-place - -TODO - -==== Manually migrating ControlZone resources - -TODO - -==== Testing ControlZone restart by cluster on application failure - -TODO - -==== Testing ControlZone migration by cluster on operating system failure - -TODO - -==== Testing ControlZone migration by cluster on NFS failure - -TODO - -==== Testing cluster reaction on network split-brain - -TODO - -==== Additional tests - -TODO basic cluster tests - -TODO - - -== Administration - -=== Dos and don'ts - -TODO - -==== Stopping an starting the ControlZone resources - -TODO - -==== Migrating the ControlZone resources - -TODO - -==== Setting ControlZone resources into maintenance mode - -TODO - -==== Ending ControlZone resources maintenance - -TODO - -==== Cleaning up resources - -TODO - - - -[id="sec.references"] -== References - -For more information, see the documents listed below. - -=== Pacemaker -- Pacemaker documentation online: -https://clusterlabs.org/pacemaker/doc/ - -:leveloffset: 2 -include::SAPNotes-convergent-mediation.adoc[] - -++++ - -++++ - -//// -############################ -# -# APPENDIX -# -############################ -//// - -:leveloffset: 0 -[id="sec.appendix"] -== Appendix - -=== CRM configuration for a minimal setup - -Find below a minimal CRM configuration for an CM ControlZone platform instance, -with the platform service and its IP address. -Ideally a filesystem resource would be included in the group. Also an UI instance -could be included. - -[subs="specialchars,attributes"] ----- -{myNode1}:~ # crm configure show -node 1: {myNode1} -node 2: {myNode2} -# -primitive rsc_cz_{mySid} ocf:suse:SAPCMControlZone \ - params SERVICE=platform MZSHELL="/opt/mz/bin/mzsh" \ - op monitor interval=60 timeout=120 on-fail=restart \ - op start timeout=120 interval=0 \ - op stop timeout=120 interval=0 \ - meta priority=100 -# -primitive rsc_ip_{mySid} IPaddr2 \ - params ip={myVipAAscs} \ - op monitor interval=60 timeout=20 on-fail=restart -# -primitive rsc_stonith_sbd stonith:external/sbd \ - params pcmk_delay_max=15 -# -group grp_cz_{mySid} rsc_ip_{mySid} rsc_cz_{mySid} -# -property cib-bootstrap-options: \ - have-watchdog=true \ - dc-version="2.1.2+20211124.ada5c3b36-150400.2.43-2.1.2+20211124.ada5c3b36" \ - cluster-infrastructure=corosync \ - cluster-name=hacluster \ - dc-deadtime=20 \ - stonith-enabled=true \ - stonith-timeout=150 \ - stonith-action=reboot \ - last-lrm-refresh=1704707877 \ - priority-fencing-delay=30 -rsc_defaults rsc-options: \ - resource-stickiness=1 \ - migration-threshold=3 \ - failure-timeout=86400 -op_defaults op-options: \ - timeout=120 ----- - -=== Corosync configuration of the two-node cluster - -Find below the corosync configuration for one corosync ring. Ideally two rings would be used. - -[subs="specialchars,attributes"] ----- -{myNode1}:~ # cat /etc/corosync/corosync.conf -# Read the corosync.conf.5 manual page -totem { - version: 2 - secauth: on - crypto_hash: sha1 - crypto_cipher: aes256 - cluster_name: hacluster - clear_node_high_bit: yes - token: 5000 - token_retransmits_before_loss_const: 10 - join: 60 - consensus: 6000 - max_messages: 20 - interface { - ringnumber: 0 - mcastport: 5405 - ttl: 1 - } - transport: udpu -} - -logging { - fileline: off - to_stderr: no - to_logfile: no - logfile: /var/log/cluster/corosync.log - to_syslog: yes - debug: off - timestamp: on - logger_subsys { - subsys: QUORUM - debug: off - } -} - -nodelist { - node { - ring0_addr: {myIP2nd1} - nodeid: 1 - } - - node { - ring0_addr: {myIP2nd2} - 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 -} ----- - -++++ - -++++ - -// Standard SUSE Best Practices includes -== Legal notice -include::common_sbp_legal_notice.adoc[] - -++++ - -++++ - -// Standard SUSE Best Practices includes -:leveloffset: 0 -include::common_gfdl1.2_i.adoc[] - -// -// REVISION 0.1 2024/01 -// diff --git a/adoc/SAPNotes-convergent-mediation.adoc b/adoc/SAPNotes-convergent-mediation.adoc deleted file mode 100644 index 5ae396d7..00000000 --- a/adoc/SAPNotes-convergent-mediation.adoc +++ /dev/null @@ -1,73 +0,0 @@ -// TODO: unify with HANA setup guides - -= Related Manual Pages - -- chronyc(8) -- chrony.conf(5) -- corosync.conf(8) -- corosync-cfgtool(8) -- corosync_overview(8) -- cibadmin(8) -- crm(8) -- crm_mon(8) -- crm_report(8) -- crm_simulate(8) -- cs_clusterstate(8) -- cs_man2pdf(8) -- cs_show_sbd_devices(8) -- cs_wait_for_idle(8) -- fstab(5) -- ha_related_sap_notes(7) -- ha_related_suse_tids(7) -- hosts(5) -- mount.nfs(8) -- nfs(5) -- ocf_heartbeat_Filesystem(7) -- ocf_heartbeat_IPAddr2(7) -- ocf_heartbeat_ping(7) -- ocf_suse_SAPCMControlZone(7) -- passwd(5) -- SAPCMControlZone_basic_cluster(7) -- SACMPControlZone_maintenance_procedures(7) -- saptune(8) -- sbd(8) -- stonith_sbd(7) -- supportconfig(8) -- systemctl(8) -- systemd-cgls(8) -- usermod(8) -- votequorum(5) -- zypper(8) - - -= Related SUSE TIDs - -Diagnostic Data Collection Master TID (https://www.suse.com/support/kb/doc/?id=000019514) -How to enable cluster resource tracing (https://www.suse.com/support/kb/doc/?id=000019138) -NFS file system is hung. New mount attempts hang also. (https://www.suse.com/support/kb/doc/?id=000019722) - -= Related SUSE Documentation - -SUSE Linux Enterprise Server for SAP Applications (https://documentation.suse.com/sles-sap/) -SUSE Linux Enterprise High Availability (https://documentation.suse.com/sle-ha) - -= Related Digital Route Documentation - -ControlZone tool mzsh (https://infozone.atlassian.net/wiki/spaces/MD9/pages/4881672/mzsh) -TODO installation - -= Related SAP Documentation - -- SAP Product Availability Matrix (https://support.sap.com/en/release-upgrade-maintenance.html#section_1969201630) -- SAP BRIM Convergent Mediation (https://www.sap.com/products/financial-management/convergent-mediation.html) - -= Related SAP Notes - -- 1552925 - Linux: High Availability Cluster Solutions (https://launchpad.support.sap.com/#/notes/1552925) -- 1763512 - Support details for SUSE Linux Enterprise for SAP Applications (https://launchpad.support.sap.com/#/notes/1763512) -- 2369910 - SAP Software on Linux: General information (https://launchpad.support.sap.com/#/notes/2369910) -- 2578899 - SUSE Linux Enterprise Server 15: Installation Note (https://launchpad.support.sap.com/#/notes/2578899) -- 3079845 - Standard Practices for SAP CM High Availability (https://launchpad.support.sap.com/#/notes/3079845) - -// REVISION 0.1 2024/01 - diff --git a/adoc/Var_SAP-convergent-mediation.adoc b/adoc/Var_SAP-convergent-mediation.adoc deleted file mode 100644 index bd002349..00000000 --- a/adoc/Var_SAP-convergent-mediation.adoc +++ /dev/null @@ -1,67 +0,0 @@ -:mySid: EN2 -:mySidLc: en2 -:mySapAdm: {mySidLc}adm -:mySapPwd: -:hanaSidDB: HA1 - -:mzadm: mzadm - -:myDev: /dev/sda -:myDevA: /dev/disk/by-id/SUSE-Example-A - -:myDevPartSbd: {myDevA}-part1 - -:mzsh: mzsh -:mzhome: /opt/mz/ -:mzshpath: {mzhome}bin/ -:mzdata: /platform/ - -:myNFSSrv: 192.168.1.1 -:myNFSSapmedia: /sapmedia -:mySAPinst: /sapmedia/SWPM20_P9/ - -:myVipNAscs: sap{mySidLc}as -:myVipNDb: sap{mySidLc}db - -:myNode1: valuga01 -:myNode2: valuga02 - -:myIPNode1: 192.168.1.100 -:myIPNode2: 192.168.1.101 - -:myVipAAscs: 192.168.1.112 -:myVipNM: /24 - -:myHaNetIf: eth0 - -:sap: SAP -:sapReg: SAP* -:sapBS: {SAP} Business Suite -:sapBSReg: {SAPReg} Business Suite -:sapNW: {SAP} NetWeaver -:sapS4: {sap} S/4HANA -:sapS4insm: {sap} S/4HANA Server 2021 -:sapS4pl: {sap} S/4HANA ABAP Platform -:sapCert: {SAP} S/4-HA-CLU 1.0 -:sapERS: {sap} Enqueue Replication Server 2 -:sapHana: {sap} HANA -:s4Hana: {sap} S/4HANA - -:linux: Linux - -:suse: SUSE -:SUSEReg: SUSE(R) -:sleAbbr: SLE -:sle: SUSE Linux Enterprise -:sleReg: {SUSEReg} Linux Enterprise -:slesAbbr: SLES -:sles: {sle} Server -:slesReg: {sleReg} Server -:sles4sapAbbr: {slesAbbr} for {SAP} -:sles4sap: {sles} for {SAP} Applications -:sles4sapReg: {slesReg} for {SAP} Applications -:sleHA: {sle} High Availability -:sapHanaSR: {sap}HanaSR -:DigRoute: Digital Route -:ConMed: Convergent Mediation -