Skip to content

Commit 1a3b8b6

Browse files
prmerger-automator[bot]prmerger-automator[bot]
authored
Merge pull request #281876 from dennispadia/dp-systemd
Include systemd instructions in SLES ASCS/ERS documents
2 parents e38bee6 + 2c3b391 commit 1a3b8b6

5 files changed

+189
-92
lines changed

‎articles/sap/workloads/high-availability-guide-suse-multi-sid.md

Lines changed: 23 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.service: sap-on-azure
77
ms.subservice: sap-vm-workloads
88
ms.custom: linux-related-content
99
ms.topic: article
10-
ms.date: 06/19/2024
10+
ms.date: 07/25/2024
1111
ms.author: radeltch
1212
---
1313

@@ -372,7 +372,28 @@ This documentation assumes that:
372372
sudo ssh slesmsscl1 "cat /usr/sap/sapservices" | grep ERS22 | sudo tee -a /usr/sap/sapservices
373373
```
374374

375-
8. **[1]** Create the SAP cluster resources for the newly installed SAP system.
375+
8. **[A]** Disabling `systemd` services of the ASCS and ERS SAP instance. This step is only applicable, if SAP startup framework is managed by systemd as per SAP Note [3115048](https://me.sap.com/notes/3115048)
376+
377+
> [!NOTE]
378+
> When managing SAP instances like SAP ASCS and SAP ERS using SLES cluster configuration, you would need to make additional modifications to integrate the cluster with the native systemd-based SAP start framework. This ensures that maintenance procedures do no compromise cluster stability. After installing or switching SAP startup framework to systemd-enabled setup as per SAP Note [3115048](https://me.sap.com/notes/3115048), you should disable the `systemd` services for the ASCS and ERS SAP instances.
379+
380+
```bash
381+
# Stop all ASCS and ERS instances using <sid>adm
382+
sapcontrol -nr 10 -function Stop
383+
sapcontrol -nr 10 -function StopService
384+
385+
sapcontrol -nr 12 -function Stop
386+
sapcontrol -nr 12 -function StopService
387+
388+
# Execute below command on VM where you have performed ASCS instance installation for each SAP system (e.g. slesmsscl1)
389+
sudo systemctl disable SAPNW2_10
390+
sudo systemctl disable SAPNW3_20
391+
# Execute below command on VM where you have performed ERS instance installation for each SAP system (e.g. slesmsscl2)
392+
sudo systemctl disable SAPNW2_12
393+
sudo systemctl disable SAPNW2_22
394+
```
395+
396+
9. **[1]** Create the SAP cluster resources for the newly installed SAP system.
376397

377398
Depending on whether you are running an ENSA1 or ENSA2 system, select respective tab to define the resources for **NW2** and **NW3** systems. SAP introduced support for [ENSA2](https://help.sap.com/docs/ABAP_PLATFORM_NEW/cff8531bc1d9416d91bb6781e628d4e0/6d655c383abf4c129b0e5c8683e7ecd8.html), including replication, in SAP NetWeaver 7.52. Starting with ABAP Platform 1809, ENSA2 is installed by default. For ENSA2 support, see SAP Note [2630416](https://launchpad.support.sap.com/#/notes/2630416).
378399

‎articles/sap/workloads/high-availability-guide-suse-netapp-files.md

Lines changed: 66 additions & 47 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.service: sap-on-azure
88
ms.subservice: sap-vm-workloads
99
ms.topic: article
1010
ms.custom: devx-track-azurecli, devx-track-azurepowershell, linux-related-content
11-
ms.date: 06/19/2024
11+
ms.date: 07/25/2024
1212
ms.author: radeltch
1313
---
1414

@@ -600,109 +600,128 @@ The following items are prefixed with either **[A]** - applicable to all nodes,
600600
sudo ssh anftstsapcl2 "cat /usr/sap/sapservices" | grep ERS01 | sudo tee -a /usr/sap/sapservices
601601
```
602602
603-
9. **[1]** Create the SAP cluster resources.
603+
9. **[A]** Disabling `systemd` services of the ASCS and ERS SAP instance. This step is only applicable, if SAP startup framework is managed by systemd as per SAP Note [3115048](https://me.sap.com/notes/3115048)
604604
605-
Depending on whether you are running an ENSA1 or ENSA2 system, select respective tab to define the resources. SAP introduced support for [ENSA2](https://help.sap.com/docs/ABAP_PLATFORM_NEW/cff8531bc1d9416d91bb6781e628d4e0/6d655c383abf4c129b0e5c8683e7ecd8.html), including replication, in SAP NetWeaver 7.52. Starting with ABAP Platform 1809, ENSA2 is installed by default. For ENSA2 support, see SAP Note [2630416](https://launchpad.support.sap.com/#/notes/2630416).
606-
607-
#### [ENSA1](#tab/ensa1)
605+
> [!NOTE]
606+
> When managing SAP instances like SAP ASCS and SAP ERS using SLES cluster configuration, you would need to make additional modifications to integrate the cluster with the native systemd-based SAP start framework. This ensures that maintenance procedures do no compromise cluster stability. After installation or switching SAP startup framework to systemd-enabled setup as per SAP Note [3115048](https://me.sap.com/notes/3115048), you should disable the `systemd` services for the ASCS and ERS SAP instances.
608607
609608
```bash
610-
sudo crm configure property maintenance-mode="true"
609+
# Stop ASCS and ERS instances using <sid>adm
610+
sapcontrol -nr 00 -function Stop
611+
sapcontrol -nr 00 -function StopService
612+
613+
sapcontrol -nr 01 -function Stop
614+
sapcontrol -nr 01 -function StopService
615+
616+
# Execute below command on VM where you have performed ASCS instance installation (e.g. anftstsapcl1)
617+
sudo systemctl disable SAPQAS_00
618+
# Execute below command on VM where you have performed ERS instance installation (e.g. anftstsapcl2)
619+
sudo systemctl disable SAPQAS_01
620+
```
621+
622+
10. **[1]** Create the SAP cluster resources.
623+
624+
Depending on whether you are running an ENSA1 or ENSA2 system, select respective tab to define the resources. SAP introduced support for [ENSA2](https://help.sap.com/docs/ABAP_PLATFORM_NEW/cff8531bc1d9416d91bb6781e628d4e0/6d655c383abf4c129b0e5c8683e7ecd8.html), including replication, in SAP NetWeaver 7.52. Starting with ABAP Platform 1809, ENSA2 is installed by default. For ENSA2 support, see SAP Note [2630416](https://launchpad.support.sap.com/#/notes/2630416).
625+
626+
#### [ENSA1](#tab/ensa1)
627+
628+
```bash
629+
sudo crm configure property maintenance-mode="true"
611630
612-
# If using NFSv3
613-
sudo crm configure primitive rsc_sap_QAS_ASCS00 SAPInstance \
631+
# If using NFSv3
632+
sudo crm configure primitive rsc_sap_QAS_ASCS00 SAPInstance \
614633
operations \$id=rsc_sap_QAS_ASCS00-operations \
615634
op monitor interval=11 timeout=60 on-fail=restart \
616635
params InstanceName=QAS_ASCS00_anftstsapvh START_PROFILE="/sapmnt/QAS/profile/QAS_ASCS00_anftstsapvh" \
617636
AUTOMATIC_RECOVER=false \
618637
meta resource-stickiness=5000 failure-timeout=60 migration-threshold=1 priority=10
619638
620-
# If using NFSv4.1
621-
sudo crm configure primitive rsc_sap_QAS_ASCS00 SAPInstance \
639+
# If using NFSv4.1
640+
sudo crm configure primitive rsc_sap_QAS_ASCS00 SAPInstance \
622641
operations \$id=rsc_sap_QAS_ASCS00-operations \
623642
op monitor interval=11 timeout=105 on-fail=restart \
624643
params InstanceName=QAS_ASCS00_anftstsapvh START_PROFILE="/sapmnt/QAS/profile/QAS_ASCS00_anftstsapvh" \
625644
AUTOMATIC_RECOVER=false \
626645
meta resource-stickiness=5000 failure-timeout=105 migration-threshold=1 priority=10
627646
628-
# If using NFSv3
629-
sudo crm configure primitive rsc_sap_QAS_ERS01 SAPInstance \
647+
# If using NFSv3
648+
sudo crm configure primitive rsc_sap_QAS_ERS01 SAPInstance \
630649
operations \$id=rsc_sap_QAS_ERS01-operations \
631650
op monitor interval=11 timeout=60 on-fail=restart \
632651
params InstanceName=QAS_ERS01_anftstsapers START_PROFILE="/sapmnt/QAS/profile/QAS_ERS01_anftstsapers" AUTOMATIC_RECOVER=false IS_ERS=true \
633652
meta priority=1000
634653
635-
# If using NFSv4.1
636-
sudo crm configure primitive rsc_sap_QAS_ERS01 SAPInstance \
654+
# If using NFSv4.1
655+
sudo crm configure primitive rsc_sap_QAS_ERS01 SAPInstance \
637656
operations \$id=rsc_sap_QAS_ERS01-operations \
638657
op monitor interval=11 timeout=105 on-fail=restart \
639658
params InstanceName=QAS_ERS01_anftstsapers START_PROFILE="/sapmnt/QAS/profile/QAS_ERS01_anftstsapers" AUTOMATIC_RECOVER=false IS_ERS=true \
640659
meta priority=1000
641660
642-
sudo crm configure modgroup g-QAS_ASCS add rsc_sap_QAS_ASCS00
643-
sudo crm configure modgroup g-QAS_ERS add rsc_sap_QAS_ERS01
661+
sudo crm configure modgroup g-QAS_ASCS add rsc_sap_QAS_ASCS00
662+
sudo crm configure modgroup g-QAS_ERS add rsc_sap_QAS_ERS01
644663
645-
sudo crm configure colocation col_sap_QAS_no_both -5000: g-QAS_ERS g-QAS_ASCS
646-
sudo crm configure location loc_sap_QAS_failover_to_ers rsc_sap_QAS_ASCS00 rule 2000: runs_ers_QAS eq 1
647-
sudo crm configure order ord_sap_QAS_first_start_ascs Optional: rsc_sap_QAS_ASCS00:start rsc_sap_QAS_ERS01:stop symmetrical=false
664+
sudo crm configure colocation col_sap_QAS_no_both -5000: g-QAS_ERS g-QAS_ASCS
665+
sudo crm configure location loc_sap_QAS_failover_to_ers rsc_sap_QAS_ASCS00 rule 2000: runs_ers_QAS eq 1
666+
sudo crm configure order ord_sap_QAS_first_start_ascs Optional: rsc_sap_QAS_ASCS00:start rsc_sap_QAS_ERS01:stop symmetrical=false
648667
649-
sudo crm_attribute --delete --name priority-fencing-delay
668+
sudo crm_attribute --delete --name priority-fencing-delay
650669
651-
sudo crm node online anftstsapcl1
652-
sudo crm configure property maintenance-mode="false"
653-
```
670+
sudo crm node online anftstsapcl1
671+
sudo crm configure property maintenance-mode="false"
672+
```
654673
655-
#### [ENSA2](#tab/ensa2)
674+
#### [ENSA2](#tab/ensa2)
656675
657-
> [!NOTE]
658-
> If you have a two-node cluster running ENSA2, you have the option to configure priority-fencing-delay cluster property. This property introduces additional delay in fencing a node that has higher total resoure priority when a split-brain scenario occurs. For more information, see [SUSE Linux Enteprise Server high availability extension administration guide](https://documentation.suse.com/sle-ha/15-SP3/single-html/SLE-HA-administration/#pro-ha-storage-protect-fencing).
659-
>
660-
> The property priority-fencing-delay is only applicable for ENSA2 running on two-node cluster.
676+
> [!NOTE]
677+
> If you have a two-node cluster running ENSA2, you have the option to configure priority-fencing-delay cluster property. This property introduces additional delay in fencing a node that has higher total resoure priority when a split-brain scenario occurs. For more information, see [SUSE Linux Enteprise Server high availability extension administration guide](https://documentation.suse.com/sle-ha/15-SP3/single-html/SLE-HA-administration/#pro-ha-storage-protect-fencing).
678+
>
679+
> The property priority-fencing-delay is only applicable for ENSA2 running on two-node cluster.
661680
662-
```bash
663-
sudo crm configure property maintenance-mode="true"
681+
```bash
682+
sudo crm configure property maintenance-mode="true"
664683
665-
sudo crm configure property priority-fencing-delay=30
684+
sudo crm configure property priority-fencing-delay=30
666685
667-
# If using NFSv3
668-
sudo crm configure primitive rsc_sap_QAS_ASCS00 SAPInstance \
686+
# If using NFSv3
687+
sudo crm configure primitive rsc_sap_QAS_ASCS00 SAPInstance \
669688
operations \$id=rsc_sap_QAS_ASCS00-operations \
670689
op monitor interval=11 timeout=60 on-fail=restart \
671690
params InstanceName=QAS_ASCS00_anftstsapvh START_PROFILE="/sapmnt/QAS/profile/QAS_ASCS00_anftstsapvh" \
672691
AUTOMATIC_RECOVER=false \
673692
meta resource-stickiness=5000 priority=100
674693
675-
# If using NFSv4.1
676-
sudo crm configure primitive rsc_sap_QAS_ASCS00 SAPInstance \
694+
# If using NFSv4.1
695+
sudo crm configure primitive rsc_sap_QAS_ASCS00 SAPInstance \
677696
operations \$id=rsc_sap_QAS_ASCS00-operations \
678697
op monitor interval=11 timeout=105 on-fail=restart \
679698
params InstanceName=QAS_ASCS00_anftstsapvh START_PROFILE="/sapmnt/QAS/profile/QAS_ASCS00_anftstsapvh" \
680699
AUTOMATIC_RECOVER=false \
681700
meta resource-stickiness=5000 priority=100
682701
683-
# If using NFSv3
684-
sudo crm configure primitive rsc_sap_QAS_ERS01 SAPInstance \
702+
# If using NFSv3
703+
sudo crm configure primitive rsc_sap_QAS_ERS01 SAPInstance \
685704
operations \$id=rsc_sap_QAS_ERS01-operations \
686705
op monitor interval=11 timeout=60 on-fail=restart \
687706
params InstanceName=QAS_ERS01_anftstsapers START_PROFILE="/sapmnt/QAS/profile/QAS_ERS01_anftstsapers" AUTOMATIC_RECOVER=false IS_ERS=true
688707
689-
# If using NFSv4.1
690-
sudo crm configure primitive rsc_sap_QAS_ERS01 SAPInstance \
708+
# If using NFSv4.1
709+
sudo crm configure primitive rsc_sap_QAS_ERS01 SAPInstance \
691710
operations \$id=rsc_sap_QAS_ERS01-operations \
692711
op monitor interval=11 timeout=105 on-fail=restart \
693712
params InstanceName=QAS_ERS01_anftstsapers START_PROFILE="/sapmnt/QAS/profile/QAS_ERS01_anftstsapers" AUTOMATIC_RECOVER=false IS_ERS=true
694713
695-
sudo crm configure modgroup g-QAS_ASCS add rsc_sap_QAS_ASCS00
696-
sudo crm configure modgroup g-QAS_ERS add rsc_sap_QAS_ERS01
714+
sudo crm configure modgroup g-QAS_ASCS add rsc_sap_QAS_ASCS00
715+
sudo crm configure modgroup g-QAS_ERS add rsc_sap_QAS_ERS01
697716
698-
sudo crm configure colocation col_sap_QAS_no_both -5000: g-QAS_ERS g-QAS_ASCS
699-
sudo crm configure order ord_sap_QAS_first_start_ascs Optional: rsc_sap_QAS_ASCS00:start rsc_sap_QAS_ERS01:stop symmetrical=false
717+
sudo crm configure colocation col_sap_QAS_no_both -5000: g-QAS_ERS g-QAS_ASCS
718+
sudo crm configure order ord_sap_QAS_first_start_ascs Optional: rsc_sap_QAS_ASCS00:start rsc_sap_QAS_ERS01:stop symmetrical=false
700719
701-
sudo crm node online anftstsapcl1
702-
sudo crm configure property maintenance-mode="false"
703-
```
720+
sudo crm node online anftstsapcl1
721+
sudo crm configure property maintenance-mode="false"
722+
```
704723
705-
---
724+
---
706725
707726
If you're upgrading from an older version and switching to enqueue server 2, see SAP note [2641019](https://launchpad.support.sap.com/#/notes/2641019).
708727

0 commit comments

Comments
 (0)