Skip to content

Commit 3141cbb

Browse files
authored
pencil edits
1 parent b18676a commit 3141cbb

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -130,11 +130,11 @@ To [enable TLS 1.2 or higher](enable-tls-azure-monitor-sap-solutions.md), follow
130130
131131
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).
132132
133-
1. Click on "Start test" under "Pre-requisite 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.
133+
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.
134134
1. Select **Create** to finish creating the Provider.
135135

136136
1. Create provider for each of the servers in the cluster to be able to see the metrics in the workbook
137-
For example - If the Cluster has 3 servers configured, Create 3 providers for each of the 3 servers with all of the above steps followed.
137+
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.
138138

139139
## Troubleshooting
140140

0 commit comments

Comments
 (0)