Merge pull request #217109 from dennispadia/depadia-azurelb

Update monitor parameter in azure-lb resource

Author: prmerger-automator[bot]

articles/virtual-machines/workloads/sap/dbms-guide-ha-ibm.md

@@ -349,7 +349,8 @@ sudo crm configure primitive rsc_ip_db2ptr_<b>PTR</b> IPaddr2 \
         params ip="<b>10.100.0.10</b>"
 
 # Configure probe port for Azure load Balancer
-sudo crm configure primitive rsc_nc_db2ptr_<b>PTR</b> azure-lb port=<b>62500</b>
+sudo crm configure primitive rsc_nc_db2ptr_<b>PTR</b> azure-lb port=<b>62500</b> \
+        op monitor timeout=20s interval=10
 
 sudo crm configure group g_ip_db2ptr_<b>PTR</b> rsc_ip_db2ptr_<b>PTR</b> rsc_nc_db2ptr_<b>PTR</b>
 

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

@@ -13,7 +13,7 @@ ms.service: virtual-machines-sap
 ms.topic: tutorial
 ms.tgt_pltfrm: vm-windows
 ms.workload: infrastructure-services
-ms.date: 01/24/2022
+ms.date: 11/03/2022
 ms.author: radeltch
 
 ---
@@ -454,10 +454,11 @@ The following items are prefixed with either **[A]** - applicable to all nodes,
       params ip=10.90.90.10 \
       op monitor interval=10 timeout=20
     
-    sudo crm configure primitive nc_NW1_ASCS azure-lb port=62000
+    sudo crm configure primitive nc_NW1_ASCS azure-lb port=62000 \
+      op monitor timeout=20s interval=10
     
     sudo crm configure group g-NW1_ASCS fs_NW1_ASCS nc_NW1_ASCS vip_NW1_ASCS \
-       meta resource-stickiness=3000
+      meta resource-stickiness=3000
     ```
 
    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.
@@ -508,7 +509,8 @@ The following items are prefixed with either **[A]** - applicable to all nodes,
       params ip=10.90.90.9 \
       op monitor interval=10 timeout=20
    
-    sudo crm configure primitive nc_NW1_ERS azure-lb port=62101
+    sudo crm configure primitive nc_NW1_ERS azure-lb port=62101 \
+      op monitor timeout=20s interval=10
     
     sudo crm configure group g-NW1_ERS fs_NW1_ERS nc_NW1_ERS vip_NW1_ERS
     ```

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

@@ -13,7 +13,7 @@ ms.service: virtual-machines-sap
 ms.topic: tutorial
 ms.tgt_pltfrm: vm-windows
 ms.workload: infrastructure-services
-ms.date: 11/01/2022
+ms.date: 11/03/2022
 ms.author: radeltch
 
 ---
@@ -524,10 +524,11 @@ The instructions in this section are applicable only if you're using Azure NetAp
       params ip=10.27.0.9 \
       op monitor interval=10 timeout=20
     
-    sudo crm configure primitive nc_NW1_ASCS azure-lb port=62000
+    sudo crm configure primitive nc_NW1_ASCS azure-lb port=62000 \
+      op monitor timeout=20s interval=10
     
     sudo crm configure group g-NW1_ASCS nc_NW1_ASCS vip_NW1_ASCS \
-       meta resource-stickiness=3000
+      meta resource-stickiness=3000
     ```
 
    Make sure that the cluster status is OK and that all resources are started. It isn't important which node the resources are running on.
@@ -573,7 +574,8 @@ The instructions in this section are applicable only if you're using Azure NetAp
       params ip=10.27.0.10 \
       op monitor interval=10 timeout=20
    
-    sudo crm configure primitive nc_NW1_ERS azure-lb port=62101
+    sudo crm configure primitive nc_NW1_ERS azure-lb port=62101 \
+      op monitor timeout=20s interval=10
     
     sudo crm configure group g-NW1_ERS nc_NW1_ERS vip_NW1_ERS
     ```

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

@@ -9,7 +9,7 @@ ms.service: virtual-machines-sap
 ms.topic: article
 ms.tgt_pltfrm: vm-windows
 ms.workload: infrastructure-services
-ms.date: 09/07/2022
+ms.date: 11/03/2022
 ms.author: radeltch
 
 ---
@@ -919,6 +919,7 @@ Create a dummy file system cluster resource, which will monitor and report failu
         params ip="10.23.0.27"
 
       sudo crm configure primitive rsc_nc_HN1_HDB03 azure-lb port=62503 \
+        op monitor timeout=20s interval=10 \
         meta resource-stickiness=0
 
       sudo crm configure group g_ip_HN1_HDB03 rsc_ip_HN1_HDB03 rsc_nc_HN1_HDB03