Stop ASCS on the primary node - SAP NetWeaver 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.

Stop ASCS on the primary node

Description – stop ASCS on the primary node by using sapcontrol.

Run node – primary node where ASCS is running.

Run steps

hahost01:ha1adm ~> sapcontrol -nr -00 -function Stop 12.05.2021 02:54:58 Stop OK hahost01:ha1adm ~> sapcontrol -nr -00 -function GetProcessList 12.05.2021 02:55:14 GetProcessList OK name, description, dispstatus, textstatus, starttime, elapsedtime, pid msg_server, MessageServer, GRAY, Stopped, , , 3613 enq_server, Enqueue Server 2, GRAY, Stopped, , , 3614

Expected result – the cluster should stop performing all activities.

[root@hahost01 ~]# pcs status Cluster name: rhelha Stack: corosync Current DC: hahost02 (version 1.1.19-8.el7_6.5-c3c624ea3d) - partition with quorum Last updated: Wed May 12 02:55:29 2021 Last change: Wed May 12 02:54:58 2021 by ha1adm via crm_resource on hahost01 2 nodes configured 7 resources configured (1 DISABLED) Online: [ hahost01 hahost02 ] Full list of resources: clusterfence (stonith:fence_aws): Started hahost02 Resource Group: rsc_ASCS00_group rsc_fs_ascs00 (ocf::heartbeat:Filesystem): Started hahost01 rsc_vip_ascs00 (ocf::heartbeat:aws-vpc-move-ip): Started hahost01 rsc_ascs00 (ocf::heartbeat:SAPInstance): Stopped (disabled) Resource Group: rsc_ERS10_group rsc_fs_ers10 (ocf::heartbeat:Filesystem): Started hahost02 rsc_vip_ers10 (ocf::heartbeat:aws-vpc-move-ip): Started hahost02 rsc_ers10 (ocf::heartbeat:SAPInstance): Started hahost02 Daemon Status: corosync: active/enabled pacemaker: active/enabled pcsd: active/enabled

Recovery procedure – start ASCS with sapcontrol.