@@ -2203,7 +2203,9 @@ In the following example, again {sapnode1} and {sapnode2} are used as the two ac
22032203# vi crm-con.txt
22042204# enter the following to crm-con.txt
22052205location loc_{sapnpsid}_never_on_{sapnode1} rsc_SAP_{sapnpsid}_HDB{sapnpino} -inf: {sapnode1}
2206- colocation col_{sapnpsid}_never_with_{sapsid}ip -inf: rsc_SAP_{sapnpsid}_HDB{sapnpino}:Started \
2206+ location loc_{sapnpsid}_never_on_promoted_node \
2207+ rsc_SAPInstance_{sapnpsid}_HDB{sapnpino} rule -inf: hana_{sapsid}_clone_state eq PROMOTED
2208+ colocation col_{sapnpsid}_never_with_{sapsid}_ip -inf: rsc_SAP_{sapnpsid}_HDB{sapnpino}:Started \
22072209 rsc_ip_{sapsid}_HDB{sapino}
22082210order ord_{sapnpsid}stop_before_{sapsid}-promote mandatory: rsc_SAP_{sapnpsid}_HDB{sapnpino}:stop \
22092211 msl_SAPHana_{sapsid}_HDB{sapino}:promote
@@ -3580,6 +3582,7 @@ In addition, there are {SUSE} support Technical Information Documents (TIDs) ava
35803582* Diagnostic Data Collection Master TID (7024037)
35813583* Indepth HANA Cluster Debug Data Collection (PACEMAKER, SAP) (7022702)
35823584* SLES for SAP - How To Engage SAP and SUSE to address Product Issues (7021182)
3585+ * Anti-colocation rule required for SAP Hana Cost Optimized Scenario as of SLE 15 SP6 (000021629)
35833586// * Basic health check for two-node SAP HANA performance based model (7022984)
35843587
35853588The SUSE support knowledgebase containing the TIDs is available at https://www.suse.com/support/kb/.
@@ -4000,4 +4003,5 @@ include::common_gfdl1.2_i.adoc[]
40004003// - HANA 2.0 SPS05 rev.059 Python 3 needed
40014004// REVISION 1.6c 2024/09
40024005// - requirements, dos and don´ts
4003- //
4006+ // REVISION 1.7 2026/02
4007+ // - location rule for 15sp6, TID 000021629
0 commit comments