Merge pull request #271540 from dennispadia/dp-hanatestcaseupdate

Minor changes in HANA test case and typo in SLES pacemaker document

Author: prmerger-automator[bot]

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

@@ -8,7 +8,7 @@ ms.service: sap-on-azure
 ms.subservice: sap-vm-workloads
 ms.topic: article
 ms.custom: devx-track-azurepowershell, linux-related-content
-ms.date: 02/08/2024
+ms.date: 04/08/2024
 ms.author: radeltch
 ---
 
@@ -342,7 +342,7 @@ Run the following commands on the nodes of the new cluster that you want to crea
     # lrwxrwxrwx 1 root root  9 Aug  9 13:32 /dev/disk/by-id/scsi-SLIO-ORG_sbdnfs_f88f30e7-c968-4678-bc87-fe7bfcbdb625 -> ../../sdf
     ```
 
-    The command lists three device IDs for every SBD device. We recommend using the ID that starts with scsi-1. In the preceding example, the IDs are:
+    The command lists three device IDs for every SBD device. We recommend using the ID that starts with scsi-3. In the preceding example, the IDs are:
 
     - **/dev/disk/by-id/scsi-36001405afb0ba8d3a3c413b8cc2cca03**
     - **/dev/disk/by-id/scsi-360014053fe4da371a5a4bb69a419a4df**
@@ -701,11 +701,10 @@ Make sure to assign the custom role to the service principal at all VM (cluster
 
 5. **[A]** Check the  *cloud-netconfig-azure* package version.
 
-   
    Check the installed version of the *cloud-netconfig-azure* package by running **zypper info cloud-netconfig-azure**. If the version is earlier than 1.3, we recommend that you update the *cloud-netconfig-azure* package to the latest available version.  
 
-   > [!TIP]   
-   > If the version in your environment is 1.3 or later, it's no longer necessary to suppress the management of network interfaces by the cloud network plug-in. 
+   > [!TIP]
+   > If the version in your environment is 1.3 or later, it's no longer necessary to suppress the management of network interfaces by the cloud network plug-in.
 
    **Only if the version of cloud-netconfig-azure is lower than 1.3**, change the configuration file for the network interface as shown in the following code to prevent the cloud network plug-in from removing the virtual IP address (Pacemaker must control the assignment). For more information, see [SUSE KB 7023633](https://www.suse.com/support/kb/doc/?id=7023633).
 
@@ -761,7 +760,7 @@ Make sure to assign the custom role to the service principal at all VM (cluster
    ```
 
    > [!IMPORTANT]
-   > The installed version of the *fence-agents* package must be 4.4.0 or later to benefit from the faster failover times with the Azure fence agent, when a cluster node is fenced. If you're running an earlier version, we recommend that you update the package.  
+   > The installed version of the *fence-agents* package must be 4.4.0 or later to benefit from the faster failover times with the Azure fence agent, when a cluster node is fenced. If you're running an earlier version, we recommend that you update the package.
 
    > [!IMPORTANT]
    > If using managed identity, the installed version of the *fence-agents* package must be -
@@ -947,7 +946,6 @@ Make sure to assign the custom role to the service principal at all VM (cluster
    > [!NOTE]
    > The 'pcmk_host_map' option is required in the command only if the hostnames and the Azure VM names are *not* identical. Specify the mapping in the format *hostname:vm-name*.
 
-
 #### [Managed identity](#tab/msi)
 
    ```bash

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

@@ -8,9 +8,10 @@ ms.service: sap-on-azure
 ms.subservice: sap-vm-workloads
 ms.topic: article
 ms.custom: devx-track-python, devx-track-azurecli, devx-track-azurepowershell, linux-related-content
-ms.date: 01/22/2024
+ms.date: 04/08/2024
 ms.author: radeltch
 ---
+
 # High availability of SAP HANA on Azure VMs on Red Hat Enterprise Linux
 
 [dbms-guide]:dbms-guide-general.md
@@ -760,7 +761,7 @@ pcs resource move SAPHana_HN1_03-master
 pcs resource move SAPHana_HN1_03-clone --master
 ```
 
-If you set `AUTOMATED_REGISTER="false"`, this command should migrate the SAP HANA master node and the group that contains the virtual IP address to `hn1-db-1`.
+The cluster would migrate the SAP HANA master node and the group containing virtual IP address to `hn1-db-1`. 
 
 After the migration is done, the `sudo pcs status` output looks like:
 
@@ -775,7 +776,7 @@ Resource Group: g_ip_HN1_03
     vip_HN1_03 (ocf::heartbeat:IPaddr2):       Started hn1-db-1
 ```
 
-The SAP HANA resource on `hn1-db-0` is stopped. In this case, configure the HANA instance as secondary by running these commands, as **hn1adm**:
+With `AUTOMATED_REGISTER="false"`, the cluster would not restart the failed HANA database or register it against the new primary on `hn1-db-0`. In this case, configure the HANA instance as secondary by running these commands, as **hn1adm**:
 
 ```bash
 sapcontrol -nr 03 -function StopWait 600 10

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

@@ -7,7 +7,7 @@ ms.service: sap-on-azure
 ms.subservice: sap-vm-workloads
 ms.topic: article
 ms.custom: devx-track-azurecli, devx-track-azurepowershell, linux-related-content
-ms.date: 04/02/2024
+ms.date: 04/08/2024
 ms.author: radeltch
 ---
 # High availability for SAP HANA on Azure VMs on SUSE Linux Enterprise Server
@@ -775,7 +775,7 @@ You can migrate the SAP HANA master node by running the following command:
 crm resource move msl_SAPHana_<HANA SID>_HDB<instance number> hn1-db-1 force
 ```
 
-If you set `AUTOMATED_REGISTER="false"`, this sequence of commands migrates the SAP HANA master node and the group that contains the virtual IP address to `hn1-db-1`.
+The cluster would migrate the SAP HANA master node and the group containing virtual IP address to `hn1-db-1`.
 
 When the migration is finished, the `crm_mon -r` output looks like this example:
 
@@ -797,7 +797,7 @@ Failed Actions:
     last-rc-change='Mon Aug 13 11:31:37 2018', queued=0ms, exec=2095ms
 ```
 
-The SAP HANA resource on `hn1-db-0` fails to start as secondary. In this case, configure the HANA instance as secondary by running this command:
+With `AUTOMATED_REGISTER="false"`, the cluster would not restart the failed HANA database or register it against the new primary on `hn1-db-0`. In this case, configure the HANA instance as secondary by running this command:
 
 ```bash
 su - <hana sid>adm