Stop ERS on the secondary 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 ERS on the secondary node

Description – stop ERS on the secondary node using sapcontrol.

Run node – secondary node where ERS is running.

Run steps

hahost02:ha1adm ~> sapcontrol -nr 10 -function Stop Stop OK hahost02:ha1adm ~> sapcontrol -nr 10 -function GetProcessList GetProcessList OK name, description, dispstatus, textstatus, starttime, elapsedtime, pid enq_replicator, Enqueue Replicator 2, GRAY, Stopped, , , 3219

Expected result – the cluster should stop performing all activities.

hahost02:~ # crm status Cluster Summary: * Stack: corosync * Current DC: hahost02 (version 2.0.xxxxxxxxxxxxxx) - partition with quorum * Last updated: * Last change: by ha1adm via cibadmin on hahost02 * 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): Started hahost01 * 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): Stopped (disabled)

Recovery procedure – start ERS with sapcontrol.