Shut down 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.

Shut down primary node

Description – shut down primary node where ASCS is running.

Run node – primary node where ASCS is running.

Run steps

Log in to the Amazon Web Services Management Console and stop the ASCS instance.

Expected result – the cluster will detect the failed ASCS node and start ASCS on the secondary node (node 2).

[root@hahost02 ~]# 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 21:39:30 2021 Last change: Wed May 12 21:27:27 2021 by root via crm_resource on hahost02 2 nodes configured 7 resources configured Online: [ hahost02 ] OFFLINE: [ hahost01 ] Full list of resources: clusterfence (stonith:fence_aws): Started hahost02 Resource Group: rsc_ASCS00_group rsc_fs_ascs00 (ocf::heartbeat:Filesystem): Started hahost02 rsc_vip_ascs00 (ocf::heartbeat:aws-vpc-move-ip): Started hahost02 rsc_ascs00 (ocf::heartbeat:SAPInstance): Started hahost02 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

  • Log in to the Amazon Web Services Management Console and start the ASCS instance.

  • The cluster will move ERS to node 1 when the instance is up.