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

Shut down secondary node

Description – shut down secondary node where ERS is running.

Run node – secondary node where ERS is running.

Run steps

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

Expected result – the cluster will detect the failed ERS node and start ERS on the primary node (node 1).

[root@hahost01 ~]# pcs status Cluster name: rhelha Stack: corosync Current DC: hahost01 (version 1.1.19-8.el7_6.5-c3c624ea3d) - partition with quorum Last updated: Wed May 12 22:16:30 2021 Last change: Wed May 12 22:04:27 2021 by root via crm_resource on hahost01 2 nodes configured 7 resources configured Online: [ hahost01 ] OFFLINE: [ hahost02 ] Full list of resources: clusterfence (stonith:fence_aws): Started hahost01 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): Started hahost01 Resource Group: rsc_ERS10_group rsc_fs_ers10 (ocf::heartbeat:Filesystem): Started hahost01 rsc_vip_ers10 (ocf::heartbeat:aws-vpc-move-ip): Started hahost01 rsc_ers10 (ocf::heartbeat:SAPInstance): Started hahost01 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 ERS instance.

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