Merge pull request #268228 from M2skills/Padmaja-Document

HA Provider Steps added for RHEL/SUSE based OS specifics

Author: Stacyrch140

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

@@ -21,53 +21,86 @@ In this how-to guide, you learn how to create a high-availability (HA) Pacemaker
 
 ## Install an HA agent
 
-Before you add providers for HA (Pacemaker) clusters, install the appropriate agent for your environment in each cluster node.
+Before you add providers for HA (Pacemaker) clusters, install the appropriate agent for RHEL/SUSE in your environment in each of the cluster node.
 
 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.
 
+For SUSE-based Pacemaker clusters, Please follow below steps to install in each of the cluster node
+
+### Install an HA cluster exporter on SUSE
+
+1. Install the required packages for Prometheus cluster exporter on the system.
+
+    ```bash
+    sudo zypper install prometheus-ha_cluster_exporter
+    ```
+
+1. Enable and start the Prometheus cluster exporter as service
+
+    ```bash
+    sudo systemctl start prometheus-ha_cluster_exporter
+    ```
+
+    ```bash
+    sudo systemctl enable prometheus-ha_cluster_exporter
+    ```
+
+1. Data is then collected in the system by ha_cluster_exporter. You can export the data via URL `http://<ip address of the server>:9644/metrics`. 
+To check if the metrics are fetched via URL on the server where the ha_cluster_exporter is installed, Run below command on the server.
+
+    ```bash
+     curl http://localhost:9644/metrics
+    ```
+
 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.
 
-For RHEL-based Pacemaker clusters, also install [PMProxy](https://access.redhat.com/articles/6139852) in each node.
+For RHEL-based Pacemaker clusters, Please follow below steps to install in each of the cluster node
 
 ### Install an HA cluster exporter on RHEL
 
-1. Install the required packages on the system.
+1. Install the required packages for PCP on the system.
 
     ```bash
-    yum install pcp pcp-pmda-hacluster
+    sudo yum install pcp pcp-pmda-hacluster
     ```
 
 1. Enable and start the required PCP Collector Services.
 
     ```bash
-    systemctl enable pmcd
+    sudo systemctl start pmcd
     ```
 
     ```bash
-    systemctl start pmcd
+    sudo systemctl enable pmcd
     ```
 
-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.
+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 will be in path "/var/lib/pcp/pmdas".
+Example : cd /var/lib/pcp/pmdas/hacluster
 
     ```bash
     cd $PCP_PMDAS_DIR/hacluster
     ```
 
     ```bash
-    ./Install
+    sudo ./Install
     ```
 
 1. Enable and start the `pmproxy` service.
 
     ```bash
-    systemctl enable pmproxy
+    sudo systemctl start pmproxy
     ```
 
     ```bash
-    systemctl start pmproxy
+    sudo systemctl enable pmproxy
     ```
 
-1. Data is then collected in the system by PCP. You can export the data by using `pmproxy` at `http://<SERVER-NAME-OR-IP-ADDRESS>:44322/metrics?names=ha_cluster`. Replace `<SERVER-NAME-OR-IP-ADDRESS>` with your server name or IP address.
+1. Data is then collected in the system by PCP. You can export the data by using `pmproxy` via URL `http://<ipaddress of the serrver>:44322/metrics?names=ha_cluster`. 
+To check if the metrics are fetched via URL on the server where the hacluster is installed, Run below command on the server.
+    
+    ```bash
+     curl http://localhost:44322/metrics?names=ha_cluster
+    ```
 
 ## Prerequisites to enable secure communication
 
@@ -88,22 +121,20 @@ To [enable TLS 1.2 or higher](enable-tls-azure-monitor-sap-solutions.md), follow
 1. Configure providers for each node of the cluster by entering the endpoint URL for **HA Cluster Exporter Endpoint**.
 
     1. For SUSE-based clusters, enter `http://<IP-address>:9664/metrics`.
-
+    
         ![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)
 
     1. For RHEL-based clusters, enter `http://<'IP address'>:44322/metrics?names=ha_cluster`.
 
         ![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)
 
-1. Enter the system identifiers, host names, and cluster names. For the system identifier, enter a unique SAP system identifier for each cluster. For the hostname, the value refers to an actual hostname in the VM. Use `hostname -s` for SUSE- and RHEL-based clusters.
-
-1. Select **Add provider** to save.
-
-1. Continue to add more providers as needed.
+1. Enter the SID - SAP system ID, Hostname - SAP hostname of the Virtual machine (Command `hostname -s` for SUSE and RHEL based servers will give hostname detail.), Cluster - Provide any custom name that is easy to identify the SAP system cluster - this Name will be visible in the workbook for metrics (need not have to be the cluster name configured on the server). 
 
-1. Select **Review + create** to review the settings.
+1. Click on "Start test" under "Prerequisite check (Preview) - highly recommended" - This test will help validate the connectivity from AMS subnet to the SAP source system and list out if any error's found - which need to be addressed before provider creation otherwise the provider creation will fail with error.
+1. Select **Create** to finish creating the Provider.
 
-1. Select **Create** to finish creating the resource.
+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.
 
 ## Troubleshooting
 
@@ -116,13 +147,13 @@ When the provider settings validation operation fails with the code `PrometheusU
 1. Restart the HA cluster exporter agent.
 
     ```bash
-    systemctl start pmproxy
+    sudo systemctl start pmproxy
     ```
 
 1. Reenable the HA cluster exporter agent.
 
     ```bash
-    systemctl enable pmproxy
+    sudo systemctl enable pmproxy
     ```
 
 1. Verify that the Prometheus endpoint is reachable from the subnet that you provided when you created the Azure Monitor for SAP solutions resource.