You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/sap/center-sap-solutions/register-existing-system.md
+11-11Lines changed: 11 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,13 +11,13 @@ author: kalyaninamuduri
11
11
---
12
12
13
13
# Register existing SAP system
14
-
In this how-to guide, you learn how to register an existing SAP system with *Azure Center for SAP solutions*. After you register an SAP system with Azure Center for SAP solutions, you can use its visualization, management and monitoring capabilities through the Azure portal. For example, you can:
14
+
In this how-to guide, you learn how to register an existing SAP system with *Azure Center for SAP solutions*. After you register an SAP system with Azure Center for SAP solutions, you can use its visualization, management, and monitoring capabilities through the Azure portal. For example, you can:
15
15
16
16
- View and track the SAP system as an Azure resource, called the *Virtual Instance for SAP solutions (VIS)*.
17
17
- Get recommendations for your SAP infrastructure, Operating System configurations etc. based on quality checks that evaluate best practices for SAP on Azure.
18
18
- Get health and status information about your SAP system.
19
19
- Start and Stop SAP application tier.
20
-
- Start and Stop individual instances of ASCS, App server and HANA Database.
20
+
- Start and Stop individual instances of ASCS, App server, and HANA Database.
21
21
- Monitor the Azure infrastructure metrics for the SAP system resources.
22
22
- View Cost Analysis for the SAP system.
23
23
@@ -34,7 +34,7 @@ When you register a system with Azure Center for SAP solutions, the following re
34
34
35
35
## Prerequisites
36
36
37
-
### Azure infrastructure level pre-requisites
37
+
### Azure infrastructure level prerequisites
38
38
39
39
- Check that you're trying to register a [supported SAP system configuration](#supported-systems)
40
40
- Grant access to Azure Storage accounts, Azure Resource Manager and Microsoft Entra services from the virtual network where the SAP system exists. Use one of these options:
@@ -50,7 +50,7 @@ When you register a system with Azure Center for SAP solutions, the following re
50
50
- A **User-assigned managed identity** which has **Azure Center for SAP solutions service role** access on the Compute resource group and **Reader** role access on the Virtual Network resource group of the SAP system. Azure Center for SAP solutions service uses this identity to discover your SAP system resources and register the system as a VIS resource.
51
51
- Make sure ASCS, Application Server and Database virtual machines of the SAP system are in **Running** state.\
52
52
53
-
### SAP system level pre-requisites
53
+
### SAP system level prerequisites
54
54
55
55
- sapcontrol and saphostctrl exe files must exist on ASCS, App server and Database.
56
56
- File path on Linux VMs: /usr/sap/hostctrl/exe
@@ -59,7 +59,7 @@ When you register a system with Azure Center for SAP solutions, the following re
59
59
- To start hostctrl sapstartsrv, use this command for Linux VMs: 'hostexecstart -start'
60
60
- To start instance sapstartsrv, use the command: 'sapcontrol -nr 'instanceNr' -function StartService S0S'
61
61
- To check status of hostctrl sapstartsrv use this command for Windows VMs: C:\Program Files\SAP\hostctrl\exe\saphostexec –status
62
-
- For successful discovery and registration of the SAP system, ensure there's network connectivity between ASCS, App and DB VMs. 'ping' command for App instance hostname must be successful from ASCS VM. 'ping' for Database hostname must be successful from App server VM.
62
+
- For successful discovery and registration of the SAP system, ensure there's network connectivity between ASCS, App, and DB VMs. 'ping' command for App instance hostname must be successful from ASCS VM. 'ping' for Database hostname must be successful from App server VM.
63
63
- On App server profile, SAPDBHOST, DBTYPE, DBID parameters must have the right values configured for the discovery and registration of Database instance details.
64
64
65
65
## Supported systems
@@ -97,7 +97,7 @@ To provide permissions to the SAP system resources to a user-assigned managed id
97
97
1. Once the permissions are assigned, this managed identity can be used in Azure Center for SAP solutions to register and manage SAP systems.
ACSS deploys a **managed storage account** into your subscription, for each SAP system being registered. When you register your SAP system using Azure Portal, PowerShell or REST API, you have the option to choose **network access** setting for the storage account. You can choose either public network access or access from specific virtual networks.
100
+
ACSS deploys a **managed storage account** into your subscription, for each SAP system being registered. When you register your SAP system using Azure portal, PowerShell, or REST API, you have the option to choose **network access** setting for the storage account. You can choose either public network access or access from specific virtual networks.
101
101
102
102
To secure the managed storage account and limit access to only the virtual network that has your SAP virtual machines, you can choose the network access setting as **Enable access from specific Virtual Networks**. You can learn more about storage account network security in [this documentation](../../storage/common/storage-network-security.md).
103
103
@@ -140,8 +140,8 @@ If the registration doesn't succeed, see [what to do when an SAP system registra
140
140
141
141
## Fix registration failure
142
142
143
-
- The process of registering an SAP system with Azure Center for SAP solutions might fail when any of the [pre-requisites aren't met](#prerequisites).
144
-
- Review the pre-requisites and ensure the configurations are as suggested.
143
+
- The process of registering an SAP system with Azure Center for SAP solutions might fail when any of the [prerequisites aren't met](#prerequisites).
144
+
- Review the prerequisites and ensure the configurations are as suggested.
145
145
- Review any error messages displayed on the VIS resource on Azure portal. Follow any recommended actions.
146
146
- Once you have fixed the configuration causing the issue, retry registration using the **Retry** action available on the Virtual Instance for SAP solutions page on Azure portal.
147
147
@@ -181,19 +181,19 @@ This error happens when the Database identifier is incorrectly configured on the
181
181
1. Log in to the VM using bastion or serial console.
182
182
2. If the VM agent exists and isn't running, then restart the waagent.
183
183
- sudo systemctl status waagent.
184
-
3. If the service isn't running then restart this service. To restart use the following steps:
184
+
3. If the service isn't running then restart this service. To restart, use the following steps:
185
185
- sudo systemctl stop waagent
186
186
- sudo systemctl start waagent
187
187
4. If this doesn't solve the issue, try updating the VM Agent using [this document](/azure/virtual-machines/extensions/update-linux-agent)
188
-
5. If the VM agent doesn't exist or needs to be re-installed, then follow [this documentation](/azure/virtual-machines/extensions/update-linux-agent).
188
+
5. If the VM agent doesn't exist or needs to be reinstalled, then follow [this documentation](/azure/virtual-machines/extensions/update-linux-agent).
189
189
190
190
To fix the Windows VM Agent, follow [Troubleshooting Azure Windows VM Agent](/troubleshoot/azure/virtual-machines/windows-azure-guest-agent).
191
191
192
192
### Error - Misconfigured SAP System
193
193
**Cause:** This issue occurs when multiple ASCS (MESSAGESERVER and/or ENQREP) instances present in the configured SAP, which isn't a valid configuration. Ensure that there exists only one ASCS instance for the SID.
194
194
195
195
**Solution:** To fix the issue, you'll need to reconfigure the SAP system so that there's only one ASCS instance present for the SID. Perform below steps:
196
-
1.Logon to the affected server, at operating system level, as "'sid'adm";
196
+
1.Log on to the affected server, at operating system level, as "'sid'adm";
197
197
2. Run "ps -ef | grep sapstartsrv", and take note of the command line related to the sapstartsrv process from the affected instance;
198
198
3. Run "sapcontrol -nr <$$> -function StopService". Run the "ps" command again (see the previous step), and ensure that the sapstartsrv process was stopped (<$$> is the number of the affected instance);
199
199
4. Access the folder "/usr/sap/'SID'/SYS/global/sapcontrol".
0 commit comments