SAP HANA system replication dashboard incorrect results

[ab-mohamed]

Used cloud platform GCP

Used SLES4SAP version SLES15SP2

Used client machine OS Google Cloud Shell

Expected behavior vs observed behavior Expected behavior: SAP HANA dashboard -> HANA System Replication Status shows the correct information for both HANA nodes.

Observed behavior: It shows incorrect info for the HOST and SECONDARY HOST columns.

How to reproduce

1. NetWeaver 7.5 normal deployment.

2. Here is a screenshot from the SAP HANA Dashboard:

3. HANA system replication status:

   
   /usr/sap/PRD/HDB00> HDBSettings.sh systemReplicationStatus.py 
   | Database | Host           | Port  | Service Name | Volume ID | Site ID | Site Name | Secondary      | Secondary | Secondary | Secondary | Secondary     | Replication | Replication | Replication    | 
   |          |                |       |              |           |         |           | Host           | Port      | Site ID   | Site Name | Active Status | Mode        | Status      | Status Details | 
   | -------- | -------------- | ----- | ------------ | --------- | ------- | --------- | -------------- | --------- | --------- | --------- | ------------- | ----------- | ----------- | -------------- | 
   | SYSTEMDB | default-hana01 | 30001 | nameserver   |         1 |       1 | NUE       | default-hana02 |     30001 |         2 | FRA       | YES           | SYNC        | ACTIVE      |                | 
   | PRD      | default-hana01 | 30007 | xsengine     |         2 |       1 | NUE       | default-hana02 |     30007 |         2 | FRA       | YES           | SYNC        | ACTIVE      |                | 
   | PRD      | default-hana01 | 30003 | indexserver  |         3 |       1 | NUE       | default-hana02 |     30003 |         2 | FRA       | YES           | SYNC        | ACTIVE      |                |

status system replication site "2": ACTIVE overall system replication status: ACTIVE

Local System Replication State

mode: PRIMARY
site id: 1
site name: NUE
```
```
# SAPHanaSR-showAttr 
Global cib-time                 
--------------------------------
global Wed Oct 20 10:55:11 2021 

Resource                      is-managed 
-----------------------------------------
cln_SAPHanaTopology_PRD_HDB00 true       

Sit srHook 
-----------
FRA SOK    

Hosts          clone_state lpa_prd_lpt node_state op_mode   remoteHost     roles                            score site srmode sync_state version                vhost          
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
default-hana01 PROMOTED    1634727311  online     logreplay default-hana02 4:P:master1:master:worker:master 150   NUE  sync   PRIM       2.00.052.00.1599235305 default-hana01 
default-hana02 DEMOTED     30          online     logreplay default-hana01 4:S:master1:master:worker:master 100   FRA  sync   SOK        2.00.052.00.1599235305 default-hana02 
```

[diegoakechi]

@ab-mohamed I cannot really spot what you reported as wrong. The systemReplicationStatus.py shows the same output as Grafana as much as I could see... Can you give more details?

[ab-mohamed]

@diegoakechi

1. The Second host value should be default-hana02 instead of default-hana01.
2. The Second Secondary host value should be default-hana01.

[diegoakechi]

@diegoakechi the info presented comes from HANA and seems to match the systemReplicationStatus.py. The SAPHanaSR-showAttrib provides a view centered on the pacemaker cluster, and the fields have different meanings here.

[yeoldegrove]

As Diego already pointed out, this comes directly from systemReplication.py. All tenant DB entries (for indexserver, xsengine in this case) are correctly present in the dashboard.

[ab-mohamed]

@diegoakechi and @yeoldegrove, Thank you for your update.

If this is the case and it presents the data comes from HDBSettings.sh systemReplicationStatus.py output, it may confuse some.

Can you add DATABASE and SERVICE NAME columns as the first two columns in the table? IMHO, this way it will be more clear.