Merge pull request #298005 from sanoop-t/sanoopt1

Add Timeout and Failure Policy to SAP HANA IP Resource Configuration

Author: prmerger-automator[bot]

articles/sap/workloads/get-started.md

@@ -55,7 +55,7 @@ In the SAP workload documentation space, you can find the following areas:
 
 ## Change Log
 
-
+- April 9, 2025: Add timeout and fail action to IP resource configuration for SAP HANA in [High availability for SAP HANA on Azure VMs on SUSE Linux Enterprise Server](./sap-hana-high-availability.md) and [High availability for SAP HANA scale-out system with HSR on SUSE Linux Enterprise Server](./sap-hana-high-availability-scale-out-hsr-suse.md)
 - March 31, 2025: Updated Azure NetApp Files Application Volume Group guidelines for SAP HANA in [FAQs for Virtual Machine Scale Set for SAP workload](./virtual-machine-scale-set-sap-faq.md)
 - March 27, 2025: Update meta attributes for health-azure-events resource and clone, to correctly operate with unhealthy nodes with pacemaker versions 2.1.3 and higher. Documents [Set up Pacemaker on Red Hat Enterprise Linux in Azure](./high-availability-guide-rhel-pacemaker.md) and [Set up Pacemaker on SUSE Linux Enterprise Server in Azure](./high-availability-guide-suse-pacemaker.md).
 - March 20, 2025: Spun off troubleshooting section from [New Version of Azure VM extension for SAP solutions](./vm-extension-for-sap-new.md) to its own article: [Troubleshooting the Azure VM Extension for SAP](./vm-extension-for-sap-troubleshooting.md) and added tab panels to [New Version of Azure VM extension for SAP solutions](./vm-extension-for-sap-new.md) for better readability.

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

@@ -953,6 +953,7 @@ You can adjust the behavior of susChkSrv with parameter action_on_lost. Valid va
 
       ```bash
       sudo crm configure primitive rsc_ip_HN1_HDB03 ocf:heartbeat:IPaddr2 \
+        op start timeout=60s on-fail=fence \
         op monitor interval="10s" timeout="20s" \
         params ip="10.23.0.27"
       

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

@@ -627,6 +627,7 @@ sudo crm configure clone cln_SAPHanaFil_<HANA SID>_HDB<instance number> rsc_SAPH
 sudo crm configure primitive rsc_ip_<HANA SID>_HDB<instance number> ocf:heartbeat:IPaddr2 \
   meta target-role="Started" \
   operations \$id="rsc_ip_<HANA SID>_HDB<instance number>-operations" \
+  op start timeout=60s on-fail=fence \
   op monitor interval="10s" timeout="20s" \
   params ip="<front-end IP address>"
 
@@ -658,6 +659,7 @@ sudo crm configure rsc_defaults migration-threshold=5000
 # Replace <placeholders> with your instance number, HANA system ID, and the front-end IP address of the Azure load balancer. 
 sudo crm configure primitive rsc_ip_<HANA SID>_HDB<instance number> ocf:heartbeat:IPaddr2 \
   meta target-role="Started" \
+  op start timeout=60s on-fail=fence \
   op monitor interval="10s" timeout="20s" \
   params ip="<front-end IP address>"