changes

Author: dennispadia

articles/sap/workloads/high-availability-guide-suse-pacemaker.md

@@ -1009,14 +1009,20 @@ Make sure to assign the custom role to the service principal at all VM (cluster
 
    #### [Managed identity](#tab/msi)
 
+   ##### [Non Scale-Out](#tab/non-scalout)
+
    ```bash
    # Adjust the command with your subscription ID and resource group of the VM
    sudo crm configure primitive rsc_st_azure stonith:fence_azure_arm \
    params msi=true subscriptionId="subscription ID" resourceGroup="resource group" \
    pcmk_monitor_retries=4 pcmk_action_limit=3 power_timeout=240 pcmk_reboot_timeout=900 pcmk_delay_max=15 pcmk_host_map="prod-cl1-0:prod-cl1-0-vm-name;prod-cl1-1:prod-cl1-1-vm-name" \
    meta failure-timeout=120s \
    op monitor interval=3600 timeout=120
-   
+   ```
+
+   ##### [Scale-Out](#tab/scalout)
+
+   ```bash
    # For SAP HANA scale-out only, configure fence_azure_arm using following command
    sudo crm configure primitive rsc_st_azure stonith:fence_azure_arm \
    params msi=true subscriptionId="subscription ID" resourceGroup="resource group" \
@@ -1025,16 +1031,24 @@ Make sure to assign the custom role to the service principal at all VM (cluster
    op monitor interval=3600 timeout=120
    ```
 
+    ---
+
    #### [Service principal](#tab/spn)
 
+   ##### [Non Scale-Out](#tab/non-scalout)
+
    ```bash
    # Adjust the command with your subscription ID, resource group of the VM, tenant ID, service principal application ID and password
    sudo crm configure primitive rsc_st_azure stonith:fence_azure_arm \
    params subscriptionId="subscription ID" resourceGroup="resource group" tenantId="tenant ID" login="application ID" passwd="password" \
    pcmk_monitor_retries=4 pcmk_action_limit=3 power_timeout=240 pcmk_reboot_timeout=900 pcmk_delay_max=15 pcmk_host_map="prod-cl1-0:prod-cl1-0-vm-name;prod-cl1-1:prod-cl1-1-vm-name" \
    meta failure-timeout=120s \
    op monitor interval=3600 timeout=120
+   ```
+
+   ##### [Scale-Out](#tab/scalout)
 
+   ```bash
    # For SAP HANA scale-out only, configure fence_azure_arm using following command
    sudo crm configure primitive rsc_st_azure stonith:fence_azure_arm \
    params subscriptionId="subscription ID" resourceGroup="resource group" tenantId="tenant ID" login="application ID" passwd="password" \
@@ -1045,6 +1059,8 @@ Make sure to assign the custom role to the service principal at all VM (cluster
 
     ---
 
+    ---
+
    ```bash
    sudo crm configure property stonith-enabled=true
    sudo crm configure property concurrent-fencing=true

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

@@ -524,13 +524,15 @@ Set up the disk layout with  **Logical Volume Manager (LVM)**. The following exa
 
 Follow the steps in [Setting up Pacemaker on SUSE Linux Enterprise Server in Azure](high-availability-guide-suse-pacemaker.md) to create the base Pacemaker cluster for HANA scale-out. Ensure that all virtual machines, including the majority maker, are added to the cluster.
 
-### Cluster specific considerations for HANA scale-out
+Few details to consider when setting up basic pacemaker cluster for HANA scale-out.
 
 * Don't set `quorum expected-votes` to 2, as this isn't a two node cluster.
 * Set the cluster property `concurrent-fencing=true` to enable deserialized node fencing.
 
-### Additional configuration steps
-
+  ```bash
+  sudo crm configure property concurrent-fencing=true
+  ```
+  
 After the base Pacemaker cluster is configured, complete the following additional steps.
 
 1. Configure a delayed start for pacemaker.service at boot by creating the file /etc/systemd/system/pacemaker.timer with the following content:
@@ -1296,8 +1298,8 @@ With susChkSrv implemented, an immediate and configurable action is executed. Th
      ---
 
     > [!NOTE]
-    >
     > 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.
+    >
     > With ON_FAIL_ACTION=fence on SAPHanaController or SAPHanaFilesystem, you must configure SAPHanaSR-alert-fencing. For more details, see the manual page "man SAPHanaSR-alert-fencing".
 
 ## Test SAP HANA failover