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 (PDF).

Stop ASCS on the primary node

Description – stop ASCS on the primary node using sapcontrol.

Run node – primary node where ASCS is running.

Run steps

hahost01:ha1adm ~> sapcontrol -nr -00 -function Stop

Stop
OK
hahost01:ha1adm ~> sapcontrol -nr -00 -function GetProcessList

GetProcessList
OK
name, description, dispstatus, textstatus, starttime, elapsedtime, pid
msg_server, MessageServer, GRAY, Stopped, , , 11763
enq_server, Enqueue Server 2, GRAY, Stopped, , , 11764

Expected result – the cluster should stop performing all activities.

hahost01:~ # crm status
Cluster Summary:
  * Stack: corosync
  * Current DC: hahost02 (version 2.0.xxxxxxxxxxx) - partition with quorum
  * Last updated: 
  * Last change:  by ha1adm via cibadmin on hahost01
  * 2 nodes configured
  * 7 resource instances configured (1 DISABLED)

Node List:
  * Online: [ hahost01 hahost02 ]

Full List of Resources:
  * res_AWS_STONITH     (stonith:external/ec2):  Started hahost02
  * Resource Group: grp_HA1_ASCS00:
    * rsc_IP_HA1_ASCS00 (ocf::suse:aws-vpc-move-ip):     Started hahost01
    * rsc_FS_HA1_ASCS00 (ocf::heartbeat:Filesystem):     Started hahost01
    * rsc_SAP_HA1_ASCS00        (ocf::heartbeat:SAPInstance):    Stopped (disabled)
  * Resource Group: grp_HA1_ERS10:
    * rsc_IP_HA1_ERS10  (ocf::suse:aws-vpc-move-ip):     Started hahost02
    * rsc_FS_HA1_ERS10  (ocf::heartbeat:Filesystem):     Started hahost02
    * rsc_SAP_HA1_ERS10 (ocf::heartbeat:SAPInstance):    Started hahost02

Recovery procedure – start ASCS with sapcontrol.