Standard version of Azure VM extension for SAP solutions

Follow the steps described in Install the Azure PowerShell module.

Check frequently for updates to the Azure PowerShell cmdlets. Unless stated otherwise in SAP Note 1928533 or SAP Note 2015553, we recommend that you work with the latest version of Azure PowerShell cmdlets.

To check the version of the Azure PowerShell cmdlets that are installed on your computer, run the following command:

(Get-Module Az.Compute).Version

Follow the steps described in Install the Azure CLI. Check frequently for updates to the Azure CLI.

To check the version of Azure CLI that is installed on your computer, run the following command:

az --version

1. Make sure that you installed the latest version of the Azure PowerShell cmdlet. For more information, see Deploying Azure PowerShell cmdlets

2. Run the following cmdlet. For a list of available environments, run Get-AzEnvironment. If you want to use global Azure, your environment is AzureCloud. For Microsoft Azure operated by 21Vianet, select AzureChinaCloud.

   $env = Get-AzEnvironment -Name <name of the environment>
   Connect-AzAccount -Environment $env
   Set-AzContext -SubscriptionName <subscription name>
   Set-AzVMAEMExtension -ResourceGroupName <resource group name> -VMName <virtual machine name>
   

After you enter your account data, the script deploys the required extensions and enables the required features. The script can take several minutes. For more information, see Set-AzVMAEMExtension.

The Set-AzVMAEMExtension configuration does all the steps to configure host data collection for SAP.

The script output includes the following information:

• Confirmation that data collection for the OS disk and all other data disks are configured.
• The next two messages confirm the configuration of Storage Metrics for a specific storage account.
• One line of output gives the status of the actual update of the VM extension for SAP configuration.
• Another line of output confirms that the configuration is deployed or updated.
• The last line of output is informational. It shows your options for testing the VM extension for SAP configuration.
• Verify that the Azure VM extension for SAP configuration is complete and the Azure infrastructure is delivering the required data by running the Readiness check.
• Wait 15-30 minutes for Azure Diagnostics to collect the relevant data.

1. Make sure that you installed the latest version of the Azure CLI. For more information, see Deploy Azure CLI

2. Sign in with your Azure account:

   az login
   

3. Install the Azure CLI Azure Event Management (AEM) extension. Ensure that you use version 0.2.2 or later.

   az extension add --name aem
   

4. Enable the extension

   az vm aem set -g <resource-group-name> -n <vm name>
   

5. Verify that the Azure extension for SAP is active on the Azure Linux VM. Check whether the file /var/lib/AzureEnhancedMonitor/PerfCounters exists. If it exists, at a command prompt, run this command to display information collected by the Azure extension for SAP:

   cat /var/lib/AzureEnhancedMonitor/PerfCounters
   

   The output looks like this:

   ...
   2;cpu;Current Hw Frequency;;0;2194.659;MHz;60;1444036656;saplnxmon;
   2;cpu;Max Hw Frequency;;0;2194.659;MHz;0;1444036656;saplnxmon;
   ...
   

1. Sign in to the Azure VM (using an admin account isn't necessary).

2. Open a Command Prompt window.

3. At the command prompt, change the directory to the installation folder of the Azure extension for SAP:

   cd "C:\Packages\Plugins\Microsoft.AzureCAT.AzureEnhancedMonitoring.MonitorX64Windows\<version>\drop"
   

   The <version> in the path to the extension might vary. If you see folders for multiple versions of the extension in the installation folder, check the configuration of the AzureEnhancedMonitoring Windows service, and then switch to the folder indicated as Path to executable.

   

4. At the command prompt, run azperflib.exe without any parameters.

   Note

   Azperflib.exe runs in a loop and updates the collected counters every 60 seconds. To end the loop, close the command prompt window. Azperflib.exe is a component that can't be used for own purposes. It's a component that delivers Azure infrastructure data related to the VM for the SAP Host Agent exclusively.

If the Azure extension for SAP isn't installed, or the AzureEnhancedMonitoring service isn't running, the extension wasn't configured correctly. For detailed information about how to troubleshoot the extension, see Troubleshooting for Windows or Troubleshooting for Linux.

Check the output of azperflib.exe

The azperflib.exe output shows all populated Azure performance counters for SAP. At the bottom of the list of collected counters, a summary and health indicator show the status of Azure extension for SAP.

Check the result returned for the Counters total output, which is reported as empty, and for Health status, shown in the preceding figure.

Interpret the resulting values as follows:

If the Health status value isn't OK, follow the instructions in Health check for the Azure extension for SAP configuration.

1. Connect to the Azure VM by using SSH.

2. Check the output of the Azure extension for SAP.

   1. Run:

      more /var/lib/AzureEnhancedMonitor/PerfCounters
      

      Expected result: Returns list of performance counters. The file shouldn't be empty.

   2. Run:

      cat /var/lib/AzureEnhancedMonitor/PerfCounters | grep Error
      

      Expected result: Returns one line where the error is none, for example, 3;config;Error;;0;0;none;0;1456416792;tst-servercs;.

   3. Run:

      more /var/lib/AzureEnhancedMonitor/LatestErrorRecord
      

      Expected result: Returns as empty or doesn't exist.

If the preceding check wasn't successful, run these extra checks:

1. Make sure that the waagent is installed and enabled.

   1. Run:

      sudo ls -al /var/lib/waagent/
      

      Expected result: Lists the content of the waagent directory.

   2. Run:

      ps -ax | grep waagent
      

      Expected result: Displays one entry similar to: python /usr/sbin/waagent -daemon.

2. Make sure that the Azure extension for SAP is installed and running.

   1. Run:

      sudo sh -c 'ls -al /var/lib/waagent/Microsoft.OSTCExtensions.AzureEnhancedMonitorForLinux-*/'
      

      Expected result: Lists the content of the Azure extension for SAP directory.

   2. Run:

      ps -ax | grep AzureEnhanced
      

      Expected result: Displays one entry similar to: python /var/lib/waagent/Microsoft.OSTCExtensions.AzureEnhancedMonitorForLinux-2.0.0.2/handler.py daemon.

3. Install SAP Host Agent as described in SAP Note 1031096, and check the output of saposcol.

   1. Run:

      /usr/sap/hostctrl/exe/saposcol -d
      

   2. Run:

      dump ccm
      

   3. Check whether the Virtualization_Configuration\Enhanced Monitoring Access metric is true.

If you already have an SAP NetWeaver Advanced Business Application Programming (ABAP) application server installed, open transaction ST06 and check whether monitoring is enabled.

If any of these checks fail, and for detailed information about how to redeploy the extension, see Troubleshooting for Linux or Troubleshooting for Windows.

1. Make sure that you installed the latest version of the Azure PowerShell cmdlet, as described in Deploying Azure PowerShell cmdlets.

2. Run the following cmdlet. For a list of available environments, run the cmdlet Get-AzEnvironment. To use global Azure, select the AzureCloud environment. For Microsoft Azure operated by 21Vianet, select AzureChinaCloud.

   $env = Get-AzEnvironment -Name <name of the environment>
   Connect-AzAccount -Environment $env
   Set-AzContext -SubscriptionName <subscription name>
   Test-AzVMAEMExtension -ResourceGroupName <resource group name> -VMName <virtual machine name>
   

3. The script tests the configuration of the VM you select.

   

Make sure that every health check result is OK. If some checks don't display OK, run the update cmdlet as described in Configure the Azure VM extension for SAP solutions with Azure CLI or Configure the Azure VM extension for SAP solutions with PowerShell.

Wait 15 minutes, and repeat the checks described in Readiness check and this chapter. If the checks still indicate a problem with some or all counters, see Troubleshooting for Linux or Troubleshooting for Windows.

1. Install Azure CLI 2.0. Ensure that you use at least version 2.19.1 or later (use the latest version).

2. Sign in with your Azure account:

   az login
   

3. Install the Azure CLI AEM extension. Ensure that you use version 0.2.2 or later.

   az extension add --name aem
   

4. Verify the installation of the extension:

   az vm aem verify -g <resource-group-name> -n <vm name>
   

The script tests the configuration of the VM you select.

Make sure that every health check result is OK. If some checks don't display OK, run the update cmdlet as described in Configure the Azure VM extension for SAP solutions with Azure CLI or Configure the Azure VM extension for SAP solutions with PowerShell.

Wait 15 minutes, and repeat the checks described in Readiness check and this chapter. If the checks still indicate a problem with some or all counters, see Troubleshooting for Linux or Troubleshooting for Windows.

Azure performance counters don't show up at all

The AzureEnhancedMonitoring Windows service collects performance metrics in Azure. If the service wasn't installed correctly or if it isn't running in your VM, no performance metrics can be collected.

The installation directory of the Azure extension for SAP is empty

Issue:

The installation directory C:\Packages\Plugins\Microsoft.AzureCAT. AzureEnhancedMonitoring.AzureCATExtensionHandler\<version>\drop is empty.

Solution:

The extension isn't installed. Determine whether it's a proxy issue (as described earlier). You might need to restart the machine or rerun the Set-AzVMAEMExtension configuration script.

Service for Azure extension for SAP doesn't exist

Issue:

The AzureEnhancedMonitoring Windows service doesn't exist.

Azperflib.exe output throws an error:

Solution:

If the service doesn't exist, the Azure extension for SAP wasn't installed correctly. Redeploy the extension as described in Configure the Azure VM extension for SAP solutions with Azure CLI or Configure the Azure VM extension for SAP solutions with PowerShell.

After you deployed the extension, check again whether the Azure performance counters are provided in the Azure VM.

Service for Azure extension for SAP exists but fails to start

Issue:

The AzureEnhancedMonitoring Windows service exists and is enabled, but fails to start. For more information, check the Application event log.

Solution:

The configuration is incorrect. Restart the Azure extension for SAP in the VM, as described in Configure the Azure extension for SAP.

Some Azure performance counters are missing

The AzureEnhancedMonitoring Windows service collects performance metrics in Azure. The service gets data from several sources. Some configuration data is collected locally, and some performance metrics are read from Azure Diagnostics. Storage counters are used from your logging on the storage subscription level.

If troubleshooting by using SAP Note 1999351 doesn't resolve the issue, rerun the Set-AzVMAEMExtension configuration script. You might have to wait an hour because storage analytics or diagnostics counters might not be created immediately after they're enabled. If the problem persists, open an SAP customer support message on the component BC-OP-NT-AZR for Windows or BC-OP-LNX-AZR for a Linux VM.

Azure performance counters don't show up at all

A daemon collects the performance metrics in Azure. If the daemon isn't running, no performance metrics can be collected.

The installation directory of the Azure extension for SAP is empty

Issue:

The directory \var\lib\waagent\ doesn't have a subdirectory for the Azure extension for SAP.

Solution:

The extension isn't installed. Determine whether it's a proxy issue (as described earlier). You might need to restart the machine and/or rerun the Set-AzVMAEMExtension configuration script.

The execution of Set-AzVMAEMExtension and Test-AzVMAEMExtension show warning messages stating that Standard Managed Disks aren't supported

Issue:

When you execute Set-AzVMAEMExtension or Test-AzVMAEMExtension, messages like these are shown:

WARNING: [WARN] Standard Managed Disks are not supported. Extension will be installed but no disk metrics will be available.

WARNING: [WARN] Standard Managed Disks are not supported. Extension will be installed but no disk metrics will be available.

WARNING: [WARN] Standard Managed Disks are not supported. Extension will be installed but no disk metrics will be available.

When you run azperfli.exe, as described earlier, you can get a result that's indicating an unhealthy state.

Solution:

You receive these messages because the Standard Managed Disks aren't delivering the APIs used by the SAP extension for SAP to check on statistics of the Standard Azure Storage Accounts. Don't worry about these messages. The reason for introducing the collection of data for Standard Disk Storage accounts was throttling inputs and outputs that occurred frequently. Managed disks avoid such throttling by limiting the number of disks in a storage account. Therefore, not having that type of that data isn't critical.

Some Azure performance counters are missing

A daemon collects performance metrics in Azure, which retrieves data from several sources. Some configuration data is collected locally, and some performance metrics are read from Azure Diagnostics. Storage counters come from the logs in your storage subscription.

For a complete and up-to-date list of known issues, see SAP Note 1999351, which has more troubleshooting information for Azure extension for SAP.

If troubleshooting by using SAP Note 1999351 doesn't resolve the issue, rerun the Set-AzVMAEMExtension configuration script as described in Configure the Azure VM extension for SAP solutions with Azure CLI or Configure the Azure VM extension for SAP solutions with PowerShell. You might have to wait for an hour because storage analytics or diagnostics counters might not be created immediately after they're enabled. If the problem persists, open an SAP customer support message on the component BC-OP-NT-AZR for Windows or BC-OP-LNX-AZR for a Linux VM.