SAPStartSrv_m...ce_procedures(7)

📦 version 0.9.6+git.1791548114.2a86b96, in opensuse-leap 16.0

💖 NAME 💖

okay so bestie, this is SAPStartSrv_maintenance_procdures — the maintenance examples page for SAPStartSrv and SUSE HA for SAP Enqueue Standalone clusters. The page you're reading is SAPStartSrv_m...ce_procedures(7), and yes it's giving section 7 energy. 💅

✨ DESCRIPTION ✨

Maintenance examples for SAPStartSrv and SUSE HA for SAP Enqueue Standalone clusters. Please peep ocf_suse_SAPStartSrv(7), SAPStartSrv_basic_cluster(7) and sap_suse_cluster_connector(8) for more examples, and read the REQUIREMENTS section there. fr fr, that's where the important stuff lives.

🌸 EXAMPLES 🌸

  • Check status of Linux cluster and ENSA replication pair. Do these before you do anything with the cluster, and again after something's been done.
# cs_clusterstate -i
# crm_mon -1r
# crm configure show | grep cli-
# su - en1adm -c "sapcontrol -nr 00 -function GetSystemInstanceList"
# su - en1adm -c "sapcontrol -nr 00 -function GetProcessList"
# su - en1adm -c "sapcontrol -nr 00 -function HACheckMaintenanceMode"
# su - en1adm -c "sapcontrol -nr 00 -function HAGetFailoverConfig"
# cs_clusterstate -i
  • Set resource group of ASCS into maintenance. This is needed so you can do manual actions on the ASCS group's resources. In this example, SID is EN1, instance number of ASCS is 00. You gotta wait for each step to complete and check the result. Also peep the next example too. 🫶
# crm resource maintenance grp_EN1_ASCS00 on
# crm configure show grp_EN1_ASCS00
  • Get resource group of ASCS back from maintenance. This is needed to put the ASCS group's resources back under cluster control. In this example, SID is EN1, instance number of ASCS is 00. You gotta wait for each step to complete and check the result. Also peep the example above. ✨
# crm resource refresh grp_EN1_ASCS00
# crm resource maintenance grp_EN1_ASCS00 off
# crm configure show grp_EN1_ASCS00
  • Set whole Linux cluster into maintenance.
# crm configure property maintenance-mode=true
# crm_attribute --query -t crm_config -n maintenance-mode
  • Remove left-over maintenance attribute from overall Linux cluster. This could be done to avoid confusion caused by different maintenance procedures. Peep the overview above on maintenance procedures with a running Linux cluster. Before doing so, check for cluster attribute maintenance-mode="false".
# crm_attribute --delete -t crm_config -n maintenance-mode
# crm_attribute --query -t crm_config -n maintenance-mode
  • Remove left-over standby attribute from Linux cluster nodes. This could be done to avoid confusion caused by different maintenance procedures. Peep the overview above on maintenance procedures with a running Linux cluster. Before doing so for all nodes, check for node attribute standby="off" on all nodes.
# crm_attribute --delete -t node -N node1 -n standby
# crm_attribute --query -t node -N node1 -n standby
  • Remove left-over maintenance attribute from resource. This should usually not be needed. Peep the overview above on maintenance procedures with a running Linux cluster.
# crm_resource --resource grp_EN1_ASCS00 --delete-parameter maintenance --meta
  • Disable Linux cluster on all cluster nodes. On any cluster node the cluster will not start automatically on boot anymore. Nevertheless a currently running cluster will keep running.
# crm cluster run "crm cluster disable"
# crm cluster run "systemctl status pacemaker" | grep pacemaker.service
  • Start Linux cluster on all cluster nodes.
# crm cluster run "crm cluster start"
# crm cluster run "systemctl status pacemaker" | grep pacemaker.service
  • Perform an ASCS takeover by using SAP tools. In this example, SID is EN1, instance number of ASCS is 00, instance number of ERS is 10. Only two nodes are in the Linux cluster. As consequence of ASCS takeover, the cluster will move the ERS. You gotta wait for each step to complete and check the result. 🔥
# su - en1adm -c "sapcontrol -nr 00 -function HAFailoverToNode ''"
# crm resource clear rsc_sap_EN1_ASCS00
# crm resource cleanup rsc_sap_EN1_ERS10
  • Overview on simple procedure for stopping and temporarily disabling the Linux cluster. ASCS and ERS instances get fully stopped. This procedure can be used to update SAP instances, OS or hardware. ASCS and ERS roles and resource status remains unchanged. You gotta wait for each step to complete and check the result. You also gotta test and document the whole procedure before applying in production.
⚠️ The ASCS instance will not be available from step 1.2 to step 3.3. This is not compliant to official SAP upgrade procedures, like Rolling Kernel Switch. 💀
  • 1.1 stopping ERS instance
  • 1.2 stopping ASCS instance
  • 1.3 disabling pacemaker on all cluster nodes
  • 1.4 stopping cluster on all cluster nodes
  • 2. doing the maintenance activity
  • 3.1 enabling pacemaker on all cluster nodes
  • 3.2 starting cluster on all cluster nodes
  • 3.3 starting ASCS instance
  • 3.4 starting ERS instance
  • Overview on maintenance procedure for Linux cluster or OS. ASCS and ERS instances remain running. Here's the whole flow, bestie:
  1. Check status of Linux cluster and ASCS/ERS, see above.
  2. Set the Linux cluster into maintenance mode.
  3. Stop Linux Cluster on all nodes.
  4. Perform maintenance on Linux cluster or OS.
  5. Start Linux cluster on all nodes.
  6. Let Linux cluster detect status of ASCS/ERS resources.
  7. Set cluster ready for operations.
  8. Check status of Linux cluster and ASCS/ERS, see above.

🐛 BUGS 🐛

If anything goes sideways, please use your favourite SAP support process to open a request for the component BC-OP-LNX-SUSE. No cap, that's the move.

👀 SEE ALSO 👀

🫶 AUTHORS 🫶

F.Herschel, L.Pinne — iconic, honestly.

(c) 2020-2026 SUSE LLC

SAPStartSrv comes with ABSOLUTELY NO WARRANTY.

For details see the GNU General Public License at http://www.gnu.org/licenses/gpl.html.

mwah 💋 — this page was last updated on 15 Aug 2025 and it's literally SAPStartSrv_m...ce_procedures(7). bye bestie 🫶🎀

📦 where this page comes from