Merge pull request #251718 from dennispadia/depadia-sles15sp05update

Update in SLES documentation

Author: prmerger-automator[bot]

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: 07/17/2023
+ms.date: 09/15/2023
 ms.author: radeltch
 ---
 
@@ -663,6 +663,8 @@ The following items are prefixed with either **[A]** - applicable to all nodes,
    sudo crm configure colocation col_sap_QAS_no_both -5000: g-QAS_ERS g-QAS_ASCS
    sudo crm configure location loc_sap_QAS_failover_to_ers rsc_sap_QAS_ASCS00 rule 2000: runs_ers_QAS eq 1
    sudo crm configure order ord_sap_QAS_first_start_ascs Optional: rsc_sap_QAS_ASCS00:start rsc_sap_QAS_ERS01:stop symmetrical=false
+
+   sudo crm_attribute --delete --name priority-fencing-delay
       
    sudo crm node online anftstsapcl1
    sudo crm configure property maintenance-mode="false"

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

@@ -9,7 +9,7 @@ ms.service: sap-on-azure
 ms.subservice: sap-vm-workloads
 ms.topic: tutorial
 ms.workload: infrastructure-services
-ms.date: 07/17/2023
+ms.date: 09/15/2023
 ms.author: radeltch
 ---
 
@@ -569,6 +569,8 @@ The following items are prefixed with either **[A]** - applicable to all nodes,
     sudo crm configure colocation col_sap_NW1_no_both -5000: g-NW1_ERS g-NW1_ASCS
     sudo crm configure location loc_sap_NW1_failover_to_ers rsc_sap_NW1_ASCS00 rule 2000: runs_ers_NW1 eq 1
     sudo crm configure order ord_sap_NW1_first_start_ascs Optional: rsc_sap_NW1_ASCS00:start rsc_sap_NW1_ERS01:stop symmetrical=false
+
+    sudo crm_attribute --delete --name priority-fencing-delay
    
     sudo crm node online sap-cl1
     sudo crm configure property maintenance-mode="false"

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

@@ -9,7 +9,7 @@ ms.service: sap-on-azure
 ms.subservice: sap-vm-workloads
 ms.topic: tutorial
 ms.workload: infrastructure-services
-ms.date: 07/17/2023
+ms.date: 09/15/2023
 ms.author: radeltch
 ---
 
@@ -700,6 +700,8 @@ The instructions in this section are applicable only if you're using Azure NetAp
     sudo crm configure location loc_sap_NW1_failover_to_ers rsc_sap_NW1_ASCS00 rule 2000: runs_ers_NW1 eq 1
     sudo crm configure order ord_sap_NW1_first_start_ascs Optional: rsc_sap_NW1_ASCS00:start rsc_sap_NW1_ERS01:stop symmetrical=false
    
+    sudo crm_attribute --delete --name priority-fencing-delay
+
     sudo crm node online sap-cl1
     sudo crm configure property maintenance-mode="false"
     ```

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

@@ -10,7 +10,7 @@ ms.subservice: sap-vm-workloads
 ms.topic: article
 ms.workload: infrastructure-services
 ms.custom: devx-track-azurepowershell
-ms.date: 06/23/2023
+ms.date: 09/15/2023
 ms.author: radeltch
 ---
 
@@ -50,7 +50,7 @@ You can configure the SBD device by using either of two options:
 
 - SBD with an Azure shared disk:
 
-  To configure an SBD device, you need to attach at least one [Azure shared disk](https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/virtual-machines/disks-shared.md) to all virtual machines that are part of Pacemaker cluster. The advantage of SBD device using an Azure shared disk is that you don’t need to deploy additional virtual machines.
+  To configure an SBD device, you need to attach at least one [Azure shared disk](https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/virtual-machines/disks-shared.md) to all virtual machines that are part of Pacemaker cluster. The advantage of SBD device using an Azure shared disk is that you don't need to deploy additional virtual machines.
 
   ![Diagram of the Azure shared disk SBD device for SLES Pacemaker cluster.](./media/high-availability-guide-suse-pacemaker/azure-shared-disk-sbd-device.png)
 
@@ -63,7 +63,7 @@ You can configure the SBD device by using either of two options:
   - An SBD device using LRS for Azure premium shared disk (skuName - Premium_LRS) is only supported with deployment in availability set.
   - An SBD device using ZRS for an Azure premium shared disk (skuName - Premium_ZRS) is recommended with deployment in availability zones.
   - A ZRS for managed disk is currently unavailable in all regions with availability zones. For more information, review the ZRS "Limitations" section in [Redundancy options for managed disks](../../virtual-machines/disks-redundancy.md#limitations).
-  - The Azure shared disk that you use for SBD devices doesn’t need to be large. The [maxShares](../../virtual-machines/disks-shared-enable.md#disk-sizes) value determines how many cluster nodes can use the shared disk. For example, you can use P1 or P2 disk sizes for your SBD device on two-node cluster such as SAP ASCS/ERS or SAP HANA scale-up.
+  - The Azure shared disk that you use for SBD devices doesn't need to be large. The [maxShares](../../virtual-machines/disks-shared-enable.md#disk-sizes) value determines how many cluster nodes can use the shared disk. For example, you can use P1 or P2 disk sizes for your SBD device on two-node cluster such as SAP ASCS/ERS or SAP HANA scale-up.
   - For [HANA scale-out with HANA system replication (HSR) and Pacemaker](sap-hana-high-availability-scale-out-hsr-suse.md), you can use an Azure shared disk for SBD devices in clusters with up to four nodes per replication site because of the current limit of [maxShares](../../virtual-machines/disks-shared-enable.md#disk-sizes).
   - We do *not* recommend attaching an Azure shared disk SBD device across Pacemaker clusters.
   - If you use multiple Azure shared disk SBD devices, check on the limit for a maximum number of data disks that can be attached to a VM.
@@ -239,6 +239,12 @@ Run the following commands on the nodes of the new cluster that you want to crea
 > - **[1]**: Applies only to node 1.
 > - **[2]**: Applies only to node 2.
 
+1. **[A]** Install iSCSI package.
+
+   ```bash
+   sudo zypper install open-iscsi
+   ```
+
 1. **[A]** Connect to the iSCSI devices. First, enable the iSCSI and SBD services.
 
    ```bash
@@ -911,7 +917,7 @@ Make sure to assign the custom role to the service principal at all VM (cluster
 
    ```bash
    sudo crm configure property stonith-enabled=true
-   crm configure property concurrent-fencing=true
+   sudo crm configure property concurrent-fencing=true
    ```
 
    > [!NOTE]
@@ -954,7 +960,7 @@ Make sure to assign the custom role to the service principal at all VM (cluster
 
 ## Configure Pacemaker for Azure scheduled events
 
-Azure offers [scheduled events](../../virtual-machines/linux/scheduled-events.md). Scheduled events are provided via the metadata service and allow time for the application to prepare for such events. Resource agent [azure-events-az](https://github.com/ClusterLabs/resource-agents/pull/1161) monitors for scheduled Azure events. If events are detected and the resource agent determines that another cluster node is available, it sets a cluster health attribute. When the cluster health attribute is set for a node, the location constraint triggers and all resources, whose name doesn’t start with “health-“ are migrated away from the node with scheduled event. Once the affected cluster node is free of running cluster resources, scheduled event is acknowledged and can execute its action, such as restart.
+Azure offers [scheduled events](../../virtual-machines/linux/scheduled-events.md). Scheduled events are provided via the metadata service and allow time for the application to prepare for such events. Resource agent [azure-events-az](https://github.com/ClusterLabs/resource-agents/pull/1161) monitors for scheduled Azure events. If events are detected and the resource agent determines that another cluster node is available, it sets a cluster health attribute. When the cluster health attribute is set for a node, the location constraint triggers and all resources, whose name doesn't start with "health-" are migrated away from the node with scheduled event. Once the affected cluster node is free of running cluster resources, scheduled event is acknowledged and can execute its action, such as restart.
 
 > [!IMPORTANT]
 > Previously, this document described the use of resource agent [azure-events](https://github.com/ClusterLabs/resource-agents/blob/main/heartbeat/azure-events.in). New resource agent [azure-events-az](https://github.com/ClusterLabs/resource-agents/blob/main/heartbeat/azure-events-az.in) fully supports Azure environments deployed in different availability zones.
@@ -978,6 +984,7 @@ Azure offers [scheduled events](../../virtual-machines/linux/scheduled-events.md
    ```bash
    #Place the cluster in maintenance mode
    sudo crm configure property maintenance-mode=true
+   ```
 
 3. **[1]** Set the pacemaker cluster health node strategy and constraint
 
@@ -989,7 +996,7 @@ Azure offers [scheduled events](../../virtual-machines/linux/scheduled-events.md
 
    > [!IMPORTANT]
    >
-   > Don't define any other resources in the cluster starting with “health-”, besides the resources described in the next steps of the documentation.
+   > Don't define any other resources in the cluster starting with "health-", besides the resources described in the next steps of the documentation.
 
 4. **[1]** Set initial value of the cluster attributes.
    Run for each cluster node. For scale-out environments including majority maker VM.
@@ -1000,7 +1007,7 @@ Azure offers [scheduled events](../../virtual-machines/linux/scheduled-events.md
    ```
 
 5. **[1]** Configure the resources in Pacemaker.
-   Important: The resources must start with ‘health-azure’.
+   Important: The resources must start with 'health-azure'.
 
    ```bash
    sudo crm configure primitive health-azure-events \

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

@@ -9,7 +9,7 @@ ms.service: sap-on-azure
 ms.subservice: sap-vm-workloads
 ms.topic: article
 ms.workload: infrastructure-services
-ms.date: 07/17/2023
+ms.date: 09/15/2023
 ms.author: radeltch
 ---
 
@@ -512,6 +512,8 @@ The following items are prefixed with either **[A]** - applicable to all nodes,
    sudo crm configure colocation col_sap_NW1_no_both -5000: g-NW1_ERS g-NW1_ASCS
    sudo crm configure location loc_sap_NW1_failover_to_ers rsc_sap_NW1_ASCS00 rule 2000: runs_ers_NW1 eq 1
    sudo crm configure order ord_sap_NW1_first_start_ascs Optional: rsc_sap_NW1_ASCS00:start rsc_sap_NW1_ERS02:stop symmetrical=false
+
+   sudo crm_attribute --delete --name priority-fencing-delay
    
    sudo crm node online nw1-cl-0
    sudo crm configure property maintenance-mode="false"

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

@@ -11,7 +11,7 @@ ms.service: sap-on-azure
 ms.subservice: sap-vm-workloads
 ms.topic: tutorial
 ms.workload: infrastructure-services
-ms.date: 07/11/2023
+ms.date: 09/15/2023
 ms.author: ampatel
 ---
 
@@ -473,7 +473,7 @@ Create a dummy file system cluster resource, which monitors and reports failures
    ```bash
    sudo crm configure primitive rsc_fs_check_HN1_HDB03 Filesystem params \
        device="/hana/shared/HN1/check/" \
-       directory="/hana/shared/check/" fstype=nfs4  \
+       directory="/hana/shared/check/" fstype=nfs  \
        options="bind,defaults,rw,hard,rsize=262144,wsize=262144,proto=tcp,noatime,_netdev,nfsvers=4.1,lock,sec=sys" \
        op monitor interval=120 timeout=120 on-fail=fence \
        op_params OCF_CHECK_LEVEL=20 \

articles/sap/workloads/sap-hana-high-availability.md

@@ -9,7 +9,7 @@ ms.service: sap-on-azure
 ms.subservice: sap-vm-workloads
 ms.topic: article
 ms.workload: infrastructure
-ms.date: 06/23/2023
+ms.date: 09/15/2023
 ms.author: radeltch
 
 ---
@@ -207,7 +207,7 @@ Replace `<placeholders>` with the values for your SAP HANA installation.
       sudo mkfs.xfs /dev/vg_hana_log_<HANA SID>/hana_log
       sudo mkfs.xfs /dev/vg_hana_shared_<HANA SID>/hana_shared
       ```
-    
+
    1. Create the mount directories and copy the universally unique identifier (UUID) of all the logical volumes:
 
       ```bash
@@ -499,8 +499,8 @@ With susChkSrv implemented, an immediate and configurable action is executed. Th
    Run the following command as root:
 
    ```bash
-   cat << EOF > /etc/sudoers.d/20-saphana
-   # Needed for SAPHanaSR and susChkSrv Python hooks
+    cat << EOF > /etc/sudoers.d/20-saphana
+    # Needed for SAPHanaSR and susChkSrv Python hooks
     hn1adm ALL=(ALL) NOPASSWD: /usr/sbin/crm_attribute -n hana_hn1_site_srHook_*
     hn1adm ALL=(ALL) NOPASSWD: /usr/sbin/SAPHanaSR-hookHelper --sid=HN1 --case=fenceMe
     EOF
@@ -513,34 +513,34 @@ With susChkSrv implemented, an immediate and configurable action is executed. Th
    Run the following command as \<SAP SID\>adm:
 
    ```bash
-   sapcontrol -nr <instance number> -function StartSystem 
+    sapcontrol -nr <instance number> -function StartSystem 
    ```
 
 1. **[1]** Verify the hook installation.
 
    Run the following command as \<SAP SID\>adm on the active HANA system replication site:
 
    ```bash
-     cdtrace
-     awk '/ha_dr_SAPHanaSR.*crm_attribute/ \
-     { printf "%s %s %s %s\n",$2,$3,$5,$16 }' nameserver_*
-     # Example output
-     # 2021-04-08 22:18:15.877583 ha_dr_SAPHanaSR SFAIL
-     # 2021-04-08 22:18:46.531564 ha_dr_SAPHanaSR SFAIL
-     # 2021-04-08 22:21:26.816573 ha_dr_SAPHanaSR SOK
+    cdtrace
+    awk '/ha_dr_SAPHanaSR.*crm_attribute/ \
+    { printf "%s %s %s %s\n",$2,$3,$5,$16 }' nameserver_*
+    # Example output
+    # 2021-04-08 22:18:15.877583 ha_dr_SAPHanaSR SFAIL
+    # 2021-04-08 22:18:46.531564 ha_dr_SAPHanaSR SFAIL
+    # 2021-04-08 22:21:26.816573 ha_dr_SAPHanaSR SOK
    ```
 
     Verify the susChkSrv hook installation.
 
    Run the following command as \<SAP SID\>adm on all HANA VMs:
 
    ```bash
-     cdtrace
-     egrep '(LOST:|STOP:|START:|DOWN:|init|load|fail)' nameserver_suschksrv.trc
-     # Example output
-     # 2022-11-03 18:06:21.116728  susChkSrv.init() version 0.7.7, parameter info: action_on_lost=fence stop_timeout=20 kill_signal=9
-     # 2022-11-03 18:06:27.613588  START: indexserver event looks like graceful tenant start
-     # 2022-11-03 18:07:56.143766  START: indexserver event looks like graceful tenant start (indexserver started)
+    cdtrace
+    egrep '(LOST:|STOP:|START:|DOWN:|init|load|fail)' nameserver_suschksrv.trc
+    # Example output
+    # 2022-11-03 18:06:21.116728  susChkSrv.init() version 0.7.7, parameter info: action_on_lost=fence stop_timeout=20 kill_signal=9
+    # 2022-11-03 18:06:27.613588  START: indexserver event looks like graceful tenant start
+    # 2022-11-03 18:07:56.143766  START: indexserver event looks like graceful tenant start (indexserver started)
    ```
 
 ## Create SAP HANA cluster resources