High-availability clusters on SLES diagnostic information
Stay organized with collections
Save and categorize content based on your preferences.
For problems that are related to a SUSE Linux Enterprise Server (SLES)
high-availability cluster for SAP, provide the
following information to Cloud Customer Care as soon as you can:
A complete and detailed description of the problem or error, including the
following:
If you aren't using Google Cloud's Agent for SAP,
then collect information about the cluster, including configuration details,
system information, and diagnostic information, which includes the following:
From each node in the cluster, the TAR archive of the system report that
you generate by running the SUSE supportconfig command line tool:
supportconfig -l
The TAR archive of log files and node configurations that you generate by
running the hb_report utility.
Specify a start time (from time) that is approximately 1 hour before
the issue occurred. Specify an end time (to time) that is at least an hour
after the issue was resolved.
Use the following command to run the hb_report utility, specifying
the from time and to time on the '-f' and '-t' flags, respectively.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 UTC."],[],[],null,["# High-availability clusters on SLES diagnostic information\n\nFor problems that are related to a SUSE Linux Enterprise Server (SLES)\nhigh-availability cluster for SAP, provide the\nfollowing information to Cloud Customer Care as soon as you can:\n\n- A complete and detailed description of the problem or error, including the\n following:\n\n - The current application or system state.\n - The date and time when the error occurred.\n - If you're facing a performance issue with your SAP workload, then [gather diagnostic information about SAP workload performance](/sap/docs/getting-support-diag-info-performance).\n- If you are using\n [Google Cloud's Agent for SAP](/sap/docs/agent-for-sap/latest/planning),\n then you can generate and share the\n [support bundle](/sap/docs/agent-for-sap/latest/getting-support-diag-info#support_bundle).\n\n- If you aren't using [Google Cloud's Agent for SAP](/sap/docs/agent-for-sap/latest/planning),\n then collect information about the cluster, including configuration details,\n system information, and diagnostic information, which includes the following:\n\n - From each node in the cluster, the TAR archive of the system report that\n you generate by running the SUSE `supportconfig` command line tool:\n\n ```sh\n supportconfig -l\n ```\n - The TAR archive of log files and node configurations that you generate by\n running the `hb_report` utility.\n\n Specify a start time (*from time* ) that is approximately 1 hour before\n the issue occurred. Specify an end time (*to time*) that is at least an hour\n after the issue was resolved.\n\n Use the following command to run the `hb_report` utility, specifying\n the *from time* and *to time* on the '-f' and '-t' flags, respectively. \n\n ```sh\n hb_report -f \"yyyy/mm/dd hh:mm\" -t \"yyyy/mm/dd hh:mm\"\n ```\n\n For more information from SUSE about both the `supportconfig` tool and\n the `hb_report` utility, see\n [Indepth HANA Cluster Debug Data Collection (PACEMAKER, SAP)](https://www.suse.com/support/kb/doc/?id=000019142)."]]