High-availability clusters on RHEL diagnostic information
Stay organized with collections
Save and categorize content based on your preferences.
For problems that are related to a Red Hat Enterprise Linux (RHEL)
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:
If you have the Red Hat sos package or can install it, use the
sosreport tool to collect the cluster information.
To install the sos package:
sudo yum install -y sos
Run the sosreport tool on all cluster nodes:
sosreport
If don't have the sos package, you can run the crm_report tool
on all cluster nodes and provide the Corosync logs.
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.
Run the crm_report on all nodes, 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 RHEL diagnostic information\n\nFor problems that are related to a Red Hat Enterprise Linux (RHEL)\nhigh-availability cluster for SAP, provide the following 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\n [Google Cloud's Agent for SAP](/sap/docs/agent-for-sap/latest/all-guides),\n then collect information about the cluster, including configuration details,\n system information, and diagnostic information, which includes the following:\n\n - If you have the Red Hat `sos` package or can install it, use the\n `sosreport` tool to collect the cluster information.\n\n - To install the `sos` package:\n\n ```sh\n sudo yum install -y sos\n ```\n - Run the `sosreport` tool on all cluster nodes:\n\n ```sh\n sosreport\n ```\n - If don't have the `sos` package, you can run the `crm_report` tool\n on all cluster nodes and provide the Corosync logs.\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\n an hour after the issue was resolved.\n - Run the `crm_report` on all nodes, specifying the *from time*\n and *to time* on the '-f' and '-t' flags, respectively.\n\n ```sh\n crm_report -f \"yyyy/mm/dd hh:mm\" -t \"yyyy/mm/dd hh:mm\"\n ```\n - For RHEL 7, additionally provide the log file `/var/log/cluster/corosync.log` for the cluster software from each cluster\n node.\n\n For more information about the `sosreport` tool, see\n [What is an sos report and how to create one in Red Hat Enterprise Linux?](https://access.redhat.com/solutions/3592)."]]
