ENSA1 and ENSA2 formatting changed to tab in other documents

Author: dennispadia

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

@@ -7,7 +7,7 @@ ms.service: sap-on-azure
 ms.subservice: sap-vm-workloads
 ms.topic: article
 ms.workload: infrastructure-services
-ms.date: 06/21/2023
+ms.date: 01/17/2024
 ms.author: radeltch
 ---
 
@@ -377,7 +377,9 @@ This documentation assumes that:
 
 8. **[1]** Create the SAP cluster resources for the newly installed SAP system.
 
-   If using enqueue server 1 architecture (ENSA1), define the resources for SAP systems **NW2** and **NW3** as follows:
+   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).
+
+   #### [ENSA1](#tab/ensa1)
 
     ```bash
     sudo crm configure property maintenance-mode="true"
@@ -424,8 +426,7 @@ This documentation assumes that:
     sudo crm configure property maintenance-mode="false"
     ```
 
-   SAP introduced support for enqueue server 2, including replication, as of SAP NW 7.52. Starting with ABAP Platform 1809, enqueue server 2 is installed by default. See SAP note [2630416](https://launchpad.support.sap.com/#/notes/2630416) for enqueue server 2 support.
-   If using enqueue server 2 architecture ([ENSA2](https://help.sap.com/viewer/cff8531bc1d9416d91bb6781e628d4e0/1709%20001/en-US/6d655c383abf4c129b0e5c8683e7ecd8.html)), define the resources for SAP systems **NW2** and **NW3** as follows:
+   #### [ENSA2](#tab/ensa2)
 
     ```bash
     sudo crm configure property maintenance-mode="true"
@@ -468,54 +469,57 @@ This documentation assumes that:
     sudo crm configure property maintenance-mode="false"
     ```
 
-   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).
+---
 
-   Make sure that the cluster status is ok and that all resources are started. It isn't important on which node the resources are running.
-   The following example shows the cluster resources status, after SAP systems **NW2** and **NW3** were added to the cluster.
+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).
 
-    ```bash
-    sudo crm_mon -r
-    
-    # Online: [ slesmsscl1 slesmsscl2 ]
-    
-    #Full list of resources:
-    
-    #stonith-sbd     (stonith:external/sbd): Started slesmsscl1
-    # Resource Group: g-NW1_ASCS
-    #     fs_NW1_ASCS        (ocf::heartbeat:Filesystem):    Started slesmsscl2
-    #     nc_NW1_ASCS        (ocf::heartbeat:azure-lb):      Started slesmsscl2
-    #     vip_NW1_ASCS       (ocf::heartbeat:IPaddr2):       Started slesmsscl2
-    #     rsc_sap_NW1_ASCS00 (ocf::heartbeat:SAPInstance):   Started slesmsscl2
-    # Resource Group: g-NW1_ERS
-    #     fs_NW1_ERS (ocf::heartbeat:Filesystem):    Started slesmsscl1
-    #     nc_NW1_ERS (ocf::heartbeat:azure-lb):      Started slesmsscl1
-    #     vip_NW1_ERS        (ocf::heartbeat:IPaddr2):       Started slesmsscl1
-    #     rsc_sap_NW1_ERS02  (ocf::heartbeat:SAPInstance):   Started slesmsscl1
-    # Resource Group: g-NW2_ASCS
-    #     fs_NW2_ASCS        (ocf::heartbeat:Filesystem):    Started slesmsscl1
-    #     nc_NW2_ASCS        (ocf::heartbeat:azure-lb):      Started slesmsscl1
-    #     vip_NW2_ASCS       (ocf::heartbeat:IPaddr2):       Started slesmsscl1
-    #     rsc_sap_NW2_ASCS10 (ocf::heartbeat:SAPInstance):   Started slesmsscl1
-    # Resource Group: g-NW2_ERS
-    #     fs_NW2_ERS (ocf::heartbeat:Filesystem):    Started slesmsscl2
-    #     nc_NW2_ERS (ocf::heartbeat:azure-lb):      Started slesmsscl2
-    #     vip_NW2_ERS        (ocf::heartbeat:IPaddr2):       Started slesmsscl2
-    #     rsc_sap_NW2_ERS12  (ocf::heartbeat:SAPInstance):   Started slesmsscl2
-    # Resource Group: g-NW3_ASCS
-    #     fs_NW3_ASCS        (ocf::heartbeat:Filesystem):    Started slesmsscl1
-    #     nc_NW3_ASCS        (ocf::heartbeat:azure-lb):      Started slesmsscl1
-    #     vip_NW3_ASCS       (ocf::heartbeat:IPaddr2):       Started slesmsscl1
-    #     rsc_sap_NW3_ASCS20 (ocf::heartbeat:SAPInstance):   Started slesmsscl1
-    # Resource Group: g-NW3_ERS
-    #     fs_NW3_ERS (ocf::heartbeat:Filesystem):    Started slesmsscl2
-    #     nc_NW3_ERS (ocf::heartbeat:azure-lb):      Started slesmsscl2
-    #     vip_NW3_ERS        (ocf::heartbeat:IPaddr2):       Started slesmsscl2
-    #     rsc_sap_NW3_ERS22  (ocf::heartbeat:SAPInstance):   Started slesmsscl2
-    ```
+Make sure that the cluster status is ok and that all resources are started. It isn't important on which node the resources are running.
 
-   The following picture shows how the resources would look like in the HA Web Konsole(Hawk), with the resources for SAP system **NW2** expanded.  
+The following example shows the cluster resources status, after SAP systems **NW2** and **NW3** were added to the cluster.
 
-   [![SAP NetWeaver High Availability overview](./media/high-availability-guide-suse/ha-suse-multi-sid-hawk.png)](./media/high-availability-guide-suse/ha-suse-multi-sid-hawk-detail.png#lightbox)
+```bash
+sudo crm_mon -r
+  
+# Online: [ slesmsscl1 slesmsscl2 ]
+ 
+#Full list of resources:
+   
+#stonith-sbd     (stonith:external/sbd): Started slesmsscl1
+# Resource Group: g-NW1_ASCS
+#     fs_NW1_ASCS        (ocf::heartbeat:Filesystem):    Started slesmsscl2
+#     nc_NW1_ASCS        (ocf::heartbeat:azure-lb):      Started slesmsscl2
+#     vip_NW1_ASCS       (ocf::heartbeat:IPaddr2):       Started slesmsscl2
+#     rsc_sap_NW1_ASCS00 (ocf::heartbeat:SAPInstance):   Started slesmsscl2
+# Resource Group: g-NW1_ERS
+#     fs_NW1_ERS (ocf::heartbeat:Filesystem):    Started slesmsscl1
+#     nc_NW1_ERS (ocf::heartbeat:azure-lb):      Started slesmsscl1
+#     vip_NW1_ERS        (ocf::heartbeat:IPaddr2):       Started slesmsscl1
+#     rsc_sap_NW1_ERS02  (ocf::heartbeat:SAPInstance):   Started slesmsscl1
+# Resource Group: g-NW2_ASCS
+#     fs_NW2_ASCS        (ocf::heartbeat:Filesystem):    Started slesmsscl1
+#     nc_NW2_ASCS        (ocf::heartbeat:azure-lb):      Started slesmsscl1
+#     vip_NW2_ASCS       (ocf::heartbeat:IPaddr2):       Started slesmsscl1
+#     rsc_sap_NW2_ASCS10 (ocf::heartbeat:SAPInstance):   Started slesmsscl1
+# Resource Group: g-NW2_ERS
+#     fs_NW2_ERS (ocf::heartbeat:Filesystem):    Started slesmsscl2
+#     nc_NW2_ERS (ocf::heartbeat:azure-lb):      Started slesmsscl2
+#     vip_NW2_ERS        (ocf::heartbeat:IPaddr2):       Started slesmsscl2
+#     rsc_sap_NW2_ERS12  (ocf::heartbeat:SAPInstance):   Started slesmsscl2
+# Resource Group: g-NW3_ASCS
+#     fs_NW3_ASCS        (ocf::heartbeat:Filesystem):    Started slesmsscl1
+#     nc_NW3_ASCS        (ocf::heartbeat:azure-lb):      Started slesmsscl1
+#     vip_NW3_ASCS       (ocf::heartbeat:IPaddr2):       Started slesmsscl1
+#     rsc_sap_NW3_ASCS20 (ocf::heartbeat:SAPInstance):   Started slesmsscl1
+# Resource Group: g-NW3_ERS
+#     fs_NW3_ERS (ocf::heartbeat:Filesystem):    Started slesmsscl2
+#     nc_NW3_ERS (ocf::heartbeat:azure-lb):      Started slesmsscl2
+#     vip_NW3_ERS        (ocf::heartbeat:IPaddr2):       Started slesmsscl2
+#     rsc_sap_NW3_ERS22  (ocf::heartbeat:SAPInstance):   Started slesmsscl2
+```
+
+The following picture shows how the resources would look like in the HA Web Konsole(Hawk), with the resources for SAP system **NW2** expanded.  
+
+[![SAP NetWeaver High Availability overview](./media/high-availability-guide-suse/ha-suse-multi-sid-hawk.png)](./media/high-availability-guide-suse/ha-suse-multi-sid-hawk-detail.png#lightbox)
 
 ### Proceed with the SAP installation
 

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

@@ -9,7 +9,7 @@ ms.service: sap-on-azure
 ms.subservice: sap-vm-workloads
 ms.topic: article
 ms.workload: infrastructure-services
-ms.date: 09/15/2023
+ms.date: 01/17/2024
 ms.author: radeltch
 ---
 
@@ -606,7 +606,9 @@ The following items are prefixed with either **[A]** - applicable to all nodes,
 
 9. **[1]** Create the SAP cluster resources.
 
-   If using enqueue server 1 architecture (ENSA1), define the resources as follows:
+   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).
+
+   #### [ENSA1](#tab/ensa1)
 
    ```bash
    sudo crm configure property maintenance-mode="true"
@@ -654,9 +656,7 @@ The following items are prefixed with either **[A]** - applicable to all nodes,
    sudo crm configure property maintenance-mode="false"
    ```
 
-   SAP introduced support for enqueue server 2, including replication, as of SAP NW 7.52. Starting with ABAP Platform 1809, enqueue server 2 is installed by default. See SAP note [2630416](https://launchpad.support.sap.com/#/notes/2630416) for enqueue server 2 support.
-
-   If using enqueue server 2 architecture ([ENSA2](https://help.sap.com/viewer/cff8531bc1d9416d91bb6781e628d4e0/1709%20001/en-US/6d655c383abf4c129b0e5c8683e7ecd8.html)), define the resources as follows:
+   #### [ENSA2](#tab/ensa2)
 
    > [!NOTE]
    > 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).
@@ -706,7 +706,9 @@ The following items are prefixed with either **[A]** - applicable to all nodes,
    sudo crm configure property maintenance-mode="false"
    ```
 
-   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).
+---
+
+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).
 
 > [!NOTE]
 > The higher timeouts, suggested when using NFSv4.1 are necessary due to protocol-specific pause, related to NFSv4.1 lease renewals. For more information, see [NFS in NetApp Best practice](https://www.netapp.com/media/10720-tr-4067.pdf).

articles/sap/workloads/high-availability-guide-suse-nfs-azure-files.md

@@ -523,7 +523,9 @@ The following items are prefixed with either **[A]** - applicable to all nodes,
 
 9. **[1]** Create the SAP cluster resources
 
-   If using enqueue server 1 architecture (ENSA1), define the resources as follows:
+   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).
+
+   #### [ENSA1](#tab/ensa1)
 
     ```bash
     sudo crm configure property maintenance-mode="true"
@@ -554,9 +556,7 @@ The following items are prefixed with either **[A]** - applicable to all nodes,
     sudo crm configure property maintenance-mode="false"
     ```
 
-   SAP introduced support for enqueue server 2, including replication, as of SAP NW 7.52. Starting with ABAP Platform 1809, enqueue server 2 is installed by default. See SAP note [2630416](https://launchpad.support.sap.com/#/notes/2630416) for enqueue server 2 support.  
-
-   If using enqueue server 2 architecture ([ENSA2](https://help.sap.com/viewer/cff8531bc1d9416d91bb6781e628d4e0/1709%20001/en-US/6d655c383abf4c129b0e5c8683e7ecd8.html)), define the resources as follows:
+   #### [ENSA2](#tab/ensa2)
 
    > [!NOTE]
    > 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).
@@ -590,26 +590,28 @@ The following items are prefixed with either **[A]** - applicable to all nodes,
     sudo crm configure property maintenance-mode="false"
     ```
 
-   If you are upgrading from an older version and switching to enqueue server 2, see SAP note [2641019](https://launchpad.support.sap.com/#/notes/2641019).
+---
 
-   Make sure that the cluster status is ok and that all resources are started. It is not important on which node the resources are running.
+If you are upgrading from an older version and switching to enqueue server 2, see SAP note [2641019](https://launchpad.support.sap.com/#/notes/2641019).
 
-    ```bash
-    sudo crm_mon -r
-    # Full list of resources:
-    # 
-    # stonith-sbd     (stonith:external/sbd): Started sap-cl2
-    #  Resource Group: g-NW1_ASCS
-    #      fs_NW1_ASCS        (ocf::heartbeat:Filesystem):    Started sap-cl1
-    #      nc_NW1_ASCS        (ocf::heartbeat:azure-lb):      Started sap-cl1
-    #      vip_NW1_ASCS       (ocf::heartbeat:IPaddr2):       Started sap-cl1
-    #      rsc_sap_NW1_ASCS00 (ocf::heartbeat:SAPInstance):   Started sap-cl1
-    #  Resource Group: g-NW1_ERS
-    #      fs_NW1_ERS (ocf::heartbeat:Filesystem):    Started sap-cl2
-    #      nc_NW1_ERS (ocf::heartbeat:azure-lb):      Started sap-cl2
-    #      vip_NW1_ERS        (ocf::heartbeat:IPaddr2):       Started sap-cl2
-    #      rsc_sap_NW1_ERS01  (ocf::heartbeat:SAPInstance):   Started sap-cl1
-    ```
+Make sure that the cluster status is ok and that all resources are started. It is not important on which node the resources are running.
+
+```bash
+sudo crm_mon -r
+# Full list of resources:
+# 
+# stonith-sbd     (stonith:external/sbd): Started sap-cl2
+#  Resource Group: g-NW1_ASCS
+#      fs_NW1_ASCS        (ocf::heartbeat:Filesystem):    Started sap-cl1
+#      nc_NW1_ASCS        (ocf::heartbeat:azure-lb):      Started sap-cl1
+#      vip_NW1_ASCS       (ocf::heartbeat:IPaddr2):       Started sap-cl1
+#      rsc_sap_NW1_ASCS00 (ocf::heartbeat:SAPInstance):   Started sap-cl1
+#  Resource Group: g-NW1_ERS
+#      fs_NW1_ERS (ocf::heartbeat:Filesystem):    Started sap-cl2
+#      nc_NW1_ERS (ocf::heartbeat:azure-lb):      Started sap-cl2
+#      vip_NW1_ERS        (ocf::heartbeat:IPaddr2):       Started sap-cl2
+#      rsc_sap_NW1_ERS01  (ocf::heartbeat:SAPInstance):   Started sap-cl1
+```
 
 ## SAP NetWeaver application server preparation
 

articles/sap/workloads/high-availability-guide-suse-nfs-simple-mount.md

@@ -644,9 +644,9 @@ The instructions in this section are applicable only if you're using Azure NetAp
 
 10. **[1]** Create the SAP cluster resources.
 
-    #### [ENSA1](#tab/ensa1)
+    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).
 
-    For ENSA1 architecture, define the resources as follows.
+    #### [ENSA1](#tab/ensa1)
 
     ```bash
     sudo crm configure property maintenance-mode="true"
@@ -702,8 +702,6 @@ The instructions in this section are applicable only if you're using Azure NetAp
 
     #### [ENSA2](#tab/ensa2)
 
-    For ENSA2 architecture, define the resources as follows.
-
     > [!NOTE]
     > 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).
     >