Skip to content

Commit 6cce7cf

Browse files
committed
Update formatting
1 parent c5ce6d9 commit 6cce7cf

File tree

1 file changed

+38
-5
lines changed

1 file changed

+38
-5
lines changed

articles/sap/workloads/sap-hana-high-availability-scale-out-hsr-suse.md

Lines changed: 38 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1008,7 +1008,7 @@ sudo crm configure primitive rsc_SAPHanaController_<SID>_HDB<InstNum> ocf:suse:S
10081008
DUPLICATE_PRIMARY_TIMEOUT="7200" AUTOMATED_REGISTER="false" \
10091009
HANA_CALL_TIMEOUT="120"
10101010
1011-
sudo crm configure clone msl_SAPHanaController_<SID>_HDB<InstNum> rsc_SAPHanaController_<SID>_HDB<InstNum> \
1011+
sudo crm configure clone mst_SAPHanaController_<SID>_HDB<InstNum> rsc_SAPHanaController_<SID>_HDB<InstNum> \
10121012
meta clone-node-max="1" interleave="true" promotable="true"
10131013
```
10141014
@@ -1047,7 +1047,7 @@ SAPHanaSR-angi adds a new resource agent SAPHanaFilesystem to monitor read/write
10471047
```bash
10481048
# Replace <placeholders> with your instance number and HANA system ID
10491049
1050-
sudo crm configure primitive rsc_SAPHanaFilesystem_SA5_HDB10 ocf:suse:SAPHanaFilesystem \
1050+
sudo crm configure primitive rsc_SAPHanaFilesystem_<SID>_HDB<InstNum> ocf:suse:SAPHanaFilesystem \
10511051
op start interval="0" timeout="10" \
10521052
op stop interval="0" timeout="20" \
10531053
op monitor interval="120" timeout="120" \
@@ -1126,14 +1126,14 @@ Create the cluster constraints
11261126
```bash
11271127
# Colocate the IP with primary HANA node
11281128
sudo crm configure colocation col_saphana_ip_<SID>_HDB<InstNum> 4000: g_ip_<SID>_HDB<InstNum>:Started \
1129-
msl_SAPHanaController_<SID>_HDB<InstNum>:Promoted
1129+
mst_SAPHanaController_<SID>_HDB<InstNum>:Promoted
11301130
11311131
# Start HANA Topology before HANA instance
11321132
sudo crm configure order ord_SAPHana_<SID>_HDB<InstNum> Optional: cln_SAPHanaTopology_<SID>_HDB<InstNum> \
1133-
msl_SAPHanaController_<SID>_HDB<InstNum>
1133+
mst_SAPHanaController_<SID>_HDB<InstNum>
11341134
11351135
# HANA resources don't run on the majority maker node
1136-
sudo crm configure location loc_SAPHanaController_not_on_majority_maker msl_SAPHanaController_<SID>_HDB<InstNum> -inf: hana-s-mm
1136+
sudo crm configure location loc_SAPHanaController_not_on_majority_maker mst_SAPHanaController_<SID>_HDB<InstNum> -inf: hana-s-mm
11371137
sudo crm configure location loc_SAPHanaTopology_not_on_majority_maker cln_SAPHanaTopology_<SID>_HDB<InstNum> -inf: hana-s-mm
11381138
```
11391139
@@ -1191,6 +1191,37 @@ sudo crm configure property maintenance-mode=false
11911191
11921192
7. **[1]** Verify the communication between the HANA HA hook and the cluster, showing status SOK for SID and both replication sites with status P(rimary) or S(econdary).
11931193
1194+
### [SAPHanaSR-angi](#tab/saphanasr-angi)
1195+
1196+
```bash
1197+
sudo SAPHanaSR-showAttr
1198+
Global cib-update dcid prim sec sid topology
1199+
----------------------------------------------------------
1200+
global 0.165361.0 7 HANA_S2 HANA_S1 HN1 ScaleOut
1201+
1202+
Resource promotable
1203+
-------------------------------------------
1204+
msl_SAPHanaController_HN1_HDB03 true
1205+
cln_SAPHanaTopology_HN1_HDB03
1206+
1207+
Site lpt lss mns opMode srHook srMode srPoll srr
1208+
----------------------------------------------------------------------
1209+
HANA_S2 1748611494 4 hana-s2-db1 logreplay PRIM sync PRIM P
1210+
HANA_S1 10 4 hana-s1-db1 logreplay SOK sync SFAIL S
1211+
1212+
Host clone_state roles score site srah version vhost
1213+
----------------------------------------------------------------------------------------------
1214+
hana-s1-db1 DEMOTED master1:master:worker:master 100 HANA_S1 - 2.00.074.00 hana-s1-db1
1215+
hana-s1-db2 DEMOTED slave:slave:worker:slave -12200 HANA_S1 - 2.00.074.00 hana-s1-db2
1216+
hana-s1-db3 DEMOTED slave:slave:worker:slave -12200 HANA_S1 - 2.00.074.00 hana-s1-db3
1217+
hana-s2-db1 PROMOTED master1:master:worker:master 150 HANA_S2 - 2.00.074.00 hana-s2-db1
1218+
hana-s2-db2 DEMOTED slave:slave:worker:slave -10000 HANA_S2 - 2.00.074.00 hana-s2-db2
1219+
hana-s2-db3 DEMOTED slave:slave:worker:slave -10000 HANA_S2 - 2.00.074.00 hana-s2-db3
1220+
hana-mm hana-mm
1221+
```
1222+
1223+
### [SAPHanaSR-ScaleOut](#tab/saphanasr-scaleout)
1224+
11941225
```bash
11951226
sudo /usr/sbin/SAPHanaSR-showAttr
11961227
# Expected result
@@ -1204,6 +1235,8 @@ sudo /usr/sbin/SAPHanaSR-showAttr
12041235
# HANA_S2 30 4 hana-s2-db1 SWAIT S
12051236
```
12061237
1238+
---
1239+
12071240
> [!NOTE]
12081241
> The timeouts in the above configuration are just examples and may need to be adapted to the specific HANA setup. For instance, you may need to increase the start timeout, if it takes longer to start the SAP HANA database.
12091242
> SAPHanaSR-angi allows further options for quicker action during a cluster event. See SUSE documentation for details about SAPHanaController's ON_FAIL_ACTION parameter, optional agent SAPHanaSR-alert-fencing and other options. Implementation should be followed by additional extensive cluster testing in your environment.

0 commit comments

Comments
 (0)