Skip to content

Commit 19311cf

Browse files
Xelu86Xelu86
committed
Freshness
1 parent c020996 commit 19311cf

1 file changed

Lines changed: 86 additions & 83 deletions

File tree

‎articles/sap/monitor/provider-ha-pacemaker-cluster.md‎

Lines changed: 86 additions & 83 deletions
Original file line numberDiff line numberDiff line change
@@ -1,20 +1,21 @@
11
---
2-
title: Create a High Availability Pacemaker cluster provider for Azure Monitor for SAP solutions
3-
description: Learn how to configure high-availability (HA) Pacemaker cluster providers for Azure Monitor for SAP solutions.
2+
title: Create a high-availability Pacemaker cluster provider for Azure Monitor for SAP solutions
3+
description: Learn how to configure a high-availability (HA) Pacemaker cluster provider for Azure Monitor for SAP solutions.
44
author: MightySuz
55
ms.service: sap-on-azure
66
ms.subservice: sap-monitor
77
ms.topic: how-to
8-
ms.date: 08/21/2024
8+
ms.date: 03/18/2026
99
ms.author: jacobjaygbay
1010
ms.custom: sfi-image-nochange
11-
#Customer intent: As a developer, I want to create a high-availability Pacemaker cluster so that I can use the resource with Azure Monitor for SAP solutions.
1211
# Customer intent: As a system administrator, I want to configure a high-availability Pacemaker cluster for Azure Monitor for SAP solutions, so that I can ensure reliable and continuous monitoring of my SAP systems.
1312
---
1413

15-
# Create high-availability cluster provider for Azure Monitor for SAP solutions
14+
# Create a high-availability cluster provider for Azure Monitor for SAP solutions
1615

17-
In this how-to guide, you learn how to create a high-availability (HA) Pacemaker cluster provider for Azure Monitor for SAP solutions. You install the HA agent and then create the provider for Azure Monitor for SAP solutions.
16+
[Azure Monitor for SAP solutions](about-azure-monitor-sap-solutions.md) lets you monitor SAP landscapes running on Azure. A high-availability (HA) Pacemaker cluster provider collects metrics from your cluster nodes so you can track cluster health and resource status.
17+
18+
In this article, you install the HA agent on each cluster node and then create the provider in Azure Monitor for SAP solutions.
1819

1920
## Prerequisites
2021

@@ -23,141 +24,143 @@ In this how-to guide, you learn how to create a high-availability (HA) Pacemaker
2324

2425
## Install an HA agent
2526

26-
Before you add providers for HA (Pacemaker) clusters, install the appropriate agent for RHEL/SUSE in your environment in each of the cluster node.
27-
28-
For SUSE-based clusters, install **ha_cluster_provider** in each node. For more information, see the [HA cluster exporter installation guide](https://github.com/ClusterLabs/ha_cluster_exporter#installation). Supported SUSE versions include SLES for SAP 12 SP3 and later versions.
27+
Before you add providers for HA (Pacemaker) clusters, install the appropriate agent for RHEL or SUSE in each cluster node.
2928

30-
For SUSE-based Pacemaker clusters, Please follow below steps to install in each of the cluster node
29+
For SUSE-based clusters, install `ha_cluster_provider` in each node. For more information, see the [HA cluster exporter installation guide](https://github.com/ClusterLabs/ha_cluster_exporter#installation). Supported SUSE versions include SLES for SAP 12 SP3 and later versions.
3130

32-
### Install an HA cluster exporter on SUSE
31+
For RHEL-based clusters, install Performance Co-Pilot (PCP) and the `pcp-pmda-hacluster` subpackage in each node. For more information, see the [PCP HACLUSTER agent installation guide](https://access.redhat.com/articles/6139852). Supported RHEL versions include 8.2, 8.4, and later versions.
3332

34-
1. Install the required packages for Prometheus cluster exporter on the system.
33+
### Install an HA cluster exporter
3534

36-
```bash
37-
sudo zypper install prometheus-ha_cluster_exporter
38-
```
35+
# [SUSE](#tab/suse)
3936

40-
1. Enable and start the Prometheus cluster exporter as service
37+
1. Install the required packages for the Prometheus cluster exporter.
4138

42-
```bash
43-
sudo systemctl start prometheus-ha_cluster_exporter
44-
```
39+
```bash
40+
sudo zypper install prometheus-ha_cluster_exporter
41+
```
4542

46-
```bash
47-
sudo systemctl enable prometheus-ha_cluster_exporter
48-
```
43+
1. Enable and start the Prometheus cluster exporter service.
4944

50-
1. Data is collected in the system through the ha_cluster_exporter. You can export the data via URL `http://<ip address of the server>:9664/metrics`.
51-
To check if the metrics are fetched via URL on the server where the ha_cluster_exporter is installed, Run the following command on the server.
45+
```bash
46+
sudo systemctl start prometheus-ha_cluster_exporter
47+
```
5248

53-
```bash
54-
curl http://localhost:9664/metrics
55-
```
49+
```bash
50+
sudo systemctl enable prometheus-ha_cluster_exporter
51+
```
5652

57-
For RHEL-based clusters, install **performance co-pilot (PCP)** and the **pcp-pmda-hacluster** subpackage in each node. For more information, see the [PCP HACLUSTER agent installation guide](https://access.redhat.com/articles/6139852). Supported RHEL versions include 8.2, 8.4, and later versions.
53+
1. The `ha_cluster_exporter` collects data. Export the data by using the URL `http://<ip-address>:9664/metrics`. To check that the metrics are accessible on the server where `ha_cluster_exporter` is installed, run the following command:
5854

59-
For RHEL-based Pacemaker clusters, Please follow below steps to install in each of the cluster node
55+
```bash
56+
curl http://localhost:9664/metrics
57+
```
6058

61-
### Install an HA cluster exporter on RHEL
59+
# [RHEL](#tab/rhel)
6260

63-
1. Install the required packages for PCP on the system.
61+
1. Install the required packages for PCP.
6462

65-
```bash
66-
sudo yum install pcp pcp-pmda-hacluster
67-
```
63+
```bash
64+
sudo yum install pcp pcp-pmda-hacluster
65+
```
6866

69-
1. Enable and start the required PCP Collector Services.
67+
1. Enable and start the required PCP collector services.
7068

71-
```bash
72-
sudo systemctl start pmcd
73-
```
69+
```bash
70+
sudo systemctl start pmcd
71+
```
7472

75-
```bash
76-
sudo systemctl enable pmcd
77-
```
73+
```bash
74+
sudo systemctl enable pmcd
75+
```
7876

79-
1. Install and enable the HA cluster PMDA. Replace `$PCP_PMDAS_DIR` with the path where `hacluster` is installed. Use the `find` command in Linux to find the path of "hacluster" bits. Usually hacluster is in path "/var/lib/pcp/pmdas".
80-
Example: cd /var/lib/pcp/pmdas/hacluster
77+
1. Install and enable the HA cluster PMDA. Replace `$PCP_PMDAS_DIR` with the path where `hacluster` is installed. Use the `find` command in Linux to find the path. The path is usually `/var/lib/pcp/pmdas`.
8178

82-
```bash
83-
cd $PCP_PMDAS_DIR/hacluster
84-
```
79+
```bash
80+
cd $PCP_PMDAS_DIR/hacluster
81+
```
8582

86-
```bash
87-
sudo ./Install
88-
```
83+
```bash
84+
sudo ./Install
85+
```
8986

9087
1. Enable and start the `pmproxy` service.
9188

92-
```bash
93-
sudo systemctl start pmproxy
94-
```
89+
```bash
90+
sudo systemctl start pmproxy
91+
```
9592

96-
```bash
97-
sudo systemctl enable pmproxy
98-
```
93+
```bash
94+
sudo systemctl enable pmproxy
95+
```
9996

100-
1. Data gets collected in the system by PCP. You can export the data by using `pmproxy` via URL `http://<ipaddress of the server>:44322/metrics?names=ha_cluster`.
101-
To check if the metrics are fetched via URL on the server where the hacluster is installed, Run the following command on the server.
102-
103-
```bash
104-
curl http://localhost:44322/metrics?names=ha_cluster
105-
```
97+
1. PCP collects data. Export the data by using `pmproxy` at the URL `http://<ip-address>:44322/metrics?names=ha_cluster`. To check that the metrics are accessible on the server where `hacluster` is installed, run the following command:
10698

107-
## Prerequisites to enable secure communication
99+
```bash
100+
curl http://localhost:44322/metrics?names=ha_cluster
101+
```
102+
103+
---
108104

109-
To [enable TLS 1.2 or higher](enable-tls-azure-monitor-sap-solutions.md), follow the steps in [this article](https://github.com/ClusterLabs/ha_cluster_exporter#tls-and-basic-authentication).
105+
## Enable secure communication (optional)
106+
107+
To [enable TLS 1.2 or higher](enable-tls-azure-monitor-sap-solutions.md), follow the steps described in the [HA cluster exporter TLS and basic authentication guide](https://github.com/ClusterLabs/ha_cluster_exporter#tls-and-basic-authentication).
110108

111109
## Create a provider for Azure Monitor for SAP solutions
112110

111+
After you install the HA agent on each cluster node, create a provider in Azure Monitor for SAP solutions to start collecting cluster metrics.
112+
113113
1. Sign in to the [Azure portal](https://portal.azure.com).
114114
1. Go to the Azure Monitor for SAP solutions service.
115115
1. Open your Azure Monitor for SAP solutions resource.
116116
1. On the resource menu, under **Settings**, select **Providers**.
117117
1. Select **Add** to add a new provider.
118118

119-
![Diagram that shows Azure Monitor for SAP solutions resource in the Azure portal, showing button to add a new provider.](./media/provider-ha-pacemaker-cluster/azure-monitor-providers-ha-cluster-start.png)
119+
![Screenshot that shows the Azure Monitor for SAP solutions resource in the Azure portal, with the button to add a new provider.](./media/provider-ha-pacemaker-cluster/azure-monitor-providers-ha-cluster-start.png)
120120

121121
1. For **Type**, select **High-availability cluster (Pacemaker)**.
122122
1. (Optional) Select **Enable secure communication** and choose a certificate type.
123123
1. Configure providers for each node of the cluster by entering the endpoint URL for **HA Cluster Exporter Endpoint**.
124124

125-
1. For SUSE-based clusters, enter `http://<IP-address>:9664/metrics`.
126-
127-
![Diagram that shows the setup for an Azure Monitor for SAP solutions resource, showing the fields for SUSE-based clusters.](./media/provider-ha-pacemaker-cluster/azure-monitor-providers-ha-cluster-suse.png)
125+
1. For SUSE-based clusters, enter `http://<IP-address>:9664/metrics`.
126+
127+
![Screenshot that shows the setup for an Azure Monitor for SAP solutions provider, with the fields for SUSE-based clusters.](./media/provider-ha-pacemaker-cluster/azure-monitor-providers-ha-cluster-suse.png)
128128

129-
1. For RHEL-based clusters, enter `http://<'IP address'>:44322/metrics?names=ha_cluster`.
129+
1. For RHEL-based clusters, enter `http://<IP-address>:44322/metrics?names=ha_cluster`.
130130

131-
![Diagram that shows the setup for an Azure Monitor for SAP solutions resource, showing the fields for RHEL-based clusters.](./media/provider-ha-pacemaker-cluster/azure-monitor-providers-ha-cluster-rhel.png)
131+
![Screenshot that shows the setup for an Azure Monitor for SAP solutions provider, with the fields for RHEL-based clusters.](./media/provider-ha-pacemaker-cluster/azure-monitor-providers-ha-cluster-rhel.png)
132132

133-
1. Enter the SID - SAP system ID, Hostname - SAP hostname of the Virtual machine (Command `hostname -s` for SUSE and RHEL based servers provide hostname detail), and Cluster - Provide any custom name that is easy to identify the SAP system cluster - this Name is visible in the workbook for metrics (need not have to be the cluster name configured on the server).
133+
1. Enter the following values:
134134

135-
1. Select "Start test" under "Prerequisite check (Preview) - highly recommended" - This test helps validate the connectivity from AMS subnet to the SAP source system and list out if any errors are found - which need to be addressed before provider creation otherwise the provider creation will fail with error.
136-
1. Select **Create** to finish creating the Provider.
135+
- **SID**: The SAP system ID.
136+
- **Hostname**: The SAP hostname of the virtual machine. Run `hostname -s` on SUSE or RHEL servers to get the hostname.
137+
- **Cluster**: A custom name that identifies the SAP system cluster. This name appears in the workbook for metrics and doesn't need to match the cluster name configured on the server.
137138

138-
1. Create provider for each of the servers in the cluster to be able to see the metrics in the workbook. For example, if the Cluster has three servers configured, Create three providers for each of the three servers with all of the above steps followed.
139+
1. Under **Prerequisite check (Preview) - highly recommended**, select **Start test**. This test validates connectivity from the Azure Monitor for SAP solutions subnet to the SAP source system and identifies any errors that you must address before you create the provider.
140+
1. Select **Create** to finish creating the provider.
141+
1. Repeat these steps for each server in the cluster. Create a provider for each server to see all metrics in the workbook.
139142

140-
## Troubleshooting
143+
## Troubleshoot common errors
141144

142-
Use the following troubleshooting steps for common errors.
145+
Use the following steps to resolve common errors.
143146

144147
### Unable to reach the Prometheus endpoint
145148

146149
When the provider settings validation operation fails with the code `PrometheusURLConnectionFailure`:
147150

148151
1. Restart the HA cluster exporter agent.
149152

150-
```bash
151-
sudo systemctl start pmproxy
152-
```
153+
```bash
154+
sudo systemctl start pmproxy
155+
```
153156

154-
1. Reenable the HA cluster exporter agent.
157+
1. Re-enable the HA cluster exporter agent.
155158

156-
```bash
157-
sudo systemctl enable pmproxy
158-
```
159+
```bash
160+
sudo systemctl enable pmproxy
161+
```
159162

160-
1. Verify that the Prometheus endpoint is reachable from the subnet that you provided when you created the Azure Monitor for SAP solutions resource.
163+
1. Check that the Prometheus endpoint is reachable from the subnet that you provided when you created the Azure Monitor for SAP solutions resource.
161164

162165
## Next steps
163166

0 commit comments

Comments
 (0)