## 3.17.4  Troubleshooting Cluster Management Problems
This topic gives hints about how to approach troubleshooting replication issues when a third-party cluster management solution is in use.
## SAP Python API and Third Party Solutions
SAP provides a Python-based API which can be used to manage high availability and disaster recovery processes, this can be adapted and integrated into your existing scripts. Calls to the API ("hooks" or HA/DR providers) can be used for many operations that need to be executed, for example, to start tools and applications on certain hosts after failover, or to stop DEV or QA SAP HANA instances on secondary sites before takeover. For details of the scripts in the API and an example implementation please refer to section 'Implementing a HA/DR Provider' in the SAP HANA Administration Guide .
As an alternative to using the SAP API, cluster management solutions are also provided by third party suppliers and partners. A list of certified HA-interface partners is available in an SAP Community wiki article: Certified HA-Interface Partners .
##  Note
Support for partner solutions is provided by the supplier; SAP does not support third party solutions.
The following SAP notes give more information about third-party cluster management solutions:
- SAP Note 1552925 - Linux: High Availability Cluster Solutions - general information about available Linux suppliers.
- SAP Note 3007062 - FAQ list about Third Party Cluster Solutions.
- SAP Note 3288971 - FAQ SUSE HAE/RedHat HAA Pacemaker Cluster Resource Manager in SAP HANA System Replication Environments.
## Troubleshooting Connectivity Issues Related to Cluster and Pacemaker Tools
It may be difficult to diagnose the cause of issues when a third-party cluster management solution is in use. For example, a situation may arise where a cluster tool unexpectedly triggers an auto takeover or system stop. You analyze this event by looking at the var/log/messages of the host preceding the event and find the following message:
```
'WARNING: HANA_CALL timed out after 60 seconds running command 'hdbnsutil -sr_state'.
```
The cluster tool may be configured with thresholds that react to such a warning by automatically executing a system stop and auto takeover and is therefore functioning as designed.
It is then necessary to analyze the cause of the timeout, which may be related to a problem with the SAP HANA database. In this case, you can follow the troubleshooting procedures given in this guide.
## Automatic Trigger of a Runtime Dump
An enhancement introduced in SAP HANA SPS 05 revision 057.00 automatically triggers a runtime dump if a script takes longer than a given time. This feature is active by default and set to a delay value of 30 seconds. You can change the delay time in the system database by changing the value (a number of seconds) of the parameter automatic_rte_dump_delay (nameserver.ini ->= [timeout] section). The dump is triggered if the run time of any of the following scripts exceeds the configured delay value:
- landscapeHostConfiguration.py
- systemReplicationStatus.py
- getTakeoverRecommendation.py
- hdbnsutil -sr_state | -sr_stateConfiguration | -sr_stateHostMapping
If a dump is triggered it does not necessarily mean that there is a problem; it is triggered preemptively to support troubleshooting in case there is a problem. The name of the trace file has the following format: &lt;service>=_&lt;host>=.&lt;port>=.rtedump.&lt;timestamp>=.blocked_script.trc. See also question 4 in SAP Note 2400007 FAQ: SAP HANA Runtime Dumps .
## Related Information
Implementing a HA/DR Provider (SAP HANA Administration Guide for SAP HANA Platform)