Administration and troubleshooting - SAP HANA on Amazon
Monitor the status of the cluster
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).

Administration and troubleshooting

Monitor the status of the cluster

You can check the status of the cluster with the following commands: 

prihana:~ # crm status
Stack: corosync
Current DC: prihana (version 1.1.18+20180430.b12c320f5-3.24.1-b12c320f5) - partition with quorum
Last updated: Thu Nov 12 12:35:56 2020
Last change: Thu Nov 12 12:34:57 2020 by root via crm_attribute on prihana

2 nodes configured
6 resources configured

Online: [ prihana sechana ]

Full list of resources:

 res_AWS_STONITH        (stonith:external/ec2): Started prihana
 res_AWS_IP     (ocf::suse:aws-vpc-move-ip):    Started prihana
 Clone Set: cln_SAPHanaTopology_HDB_HDB00 [rsc_SAPHanaTopology_HDB_HDB00]
     Started: [ prihana sechana ]
 Master/Slave Set: msl_SAPHana_HDB_HDB00 [rsc_SAPHana_HDB_HDB00]
     Masters: [ prihana ]
     Slaves: [ sechana ]
prihana:~ # crm_mon -1
Stack: corosync
Current DC: prihana (version 1.1.18+20180430.b12c320f5-3.24.1-b12c320f5) - partition with quorum
Last updated: Thu Nov 12 12:36:24 2020
Last change: Thu Nov 12 12:36:01 2020 by root via crm_attribute on prihana

2 nodes configured
6 resources configured

Online: [ prihana sechana ]

Active resources:

 res_AWS_STONITH        (stonith:external/ec2): Started prihana
 res_AWS_IP     (ocf::suse:aws-vpc-move-ip):    Started prihana
 Clone Set: cln_SAPHanaTopology_HDB_HDB00 [rsc_SAPHanaTopology_HDB_HDB00]
     Started: [ prihana sechana ]
 Master/Slave Set: msl_SAPHana_HDB_HDB00 [rsc_SAPHana_HDB_HDB00]
     Masters: [ prihana ]
     Slaves: [ sechana ]

Check the status of replication with the following command: 

prihana:~ # crm_mon -A1
Stack: corosync
Current DC: prihana (version 1.1.18+20180430.b12c320f5-3.24.1-b12c320f5) - partition with quorum
Last updated: Thu Nov 12 12:37:28 2020
Last change: Thu Nov 12 12:37:04 2020 by root via crm_attribute on prihana

2 nodes configured
6 resources configured

Online: [ prihana sechana ]

Active resources:

 res_AWS_STONITH        (stonith:external/ec2): Started prihana
 res_AWS_IP     (ocf::suse:aws-vpc-move-ip):    Started prihana
 Clone Set: cln_SAPHanaTopology_HDB_HDB00 [rsc_SAPHanaTopology_HDB_HDB00]
     Started: [ prihana sechana ]
 Master/Slave Set: msl_SAPHana_HDB_HDB00 [rsc_SAPHana_HDB_HDB00]
     Masters: [ prihana ]
     Slaves: [ sechana ]

Node Attributes:
* Node prihana:
    + hana_hdb_clone_state              : PROMOTED
    + hana_hdb_op_mode                  : logreplay
    + hana_hdb_remoteHost               : sechana
    + hana_hdb_roles                    : 4:P:master1:master:worker:master
    + hana_hdb_site                     : PRI
    + hana_hdb_srmode                   : sync
    + hana_hdb_sync_state               : PRIM
    + hana_hdb_version                  : 2.00.030.00.1522209842
    + hana_hdb_vhost                    : prihana
    + lpa_hdb_lpt                       : 1605184624
    + master-rsc_SAPHana_HDB_HDB00      : 150
* Node sechana:
    + hana_hdb_clone_state              : DEMOTED
    + hana_hdb_op_mode                  : logreplay
    + hana_hdb_remoteHost               : prihana
    + hana_hdb_roles                    : 4:S:master1:master:worker:master
    + hana_hdb_site                     : SEC
    + hana_hdb_srmode                   : sync
    + hana_hdb_sync_state               : SOK
    + hana_hdb_version                  : 2.00.030.00.1522209842
    + hana_hdb_vhost                    : sechana
    + lpa_hdb_lpt                       : 30
    + master-rsc_SAPHana_HDB_HDB00      : 100