SAP Basis Tech Supports

Symptom

You operate an SAP system with Microsoft Windows and virtualized hardware. The previously-available tools and transactions for monitoring an SAP system are insufficient for this purpose.
Other terms

Virtualization, Windows, VMware ESX Server, vSphere, Hyper-V, Windows Server 2008
Reason and Prerequisites

In the SAP transactions that monitor the system configuration, you could not distinguish between a system operating on physical hardware and a system operating on virtual hardware.
If you operate a system on physical hardware, all the existing resources are available to the operating system.
If you operate a system on virtual hardware, subareas of the underlying physical hardware can be assigned to the virtual guest operating system.
Since you can assign the physical hardware to several guest operating systems at the same time, there is important information missing about which native resources are available to the virtual system.
Solution

To monitor an SAP system on virtual hardware, you must set up the extended SAP System Monitoring.
The first section of this note lists all of the steps that you must perform for VMware and for Hyper-V. Both of the sections that follow list the additional steps that are also required for VMware or Hyper-V.

Work steps for all virtualization solutions
1. Installing the Microsoft runtime environment.
To operate the new data collector, you require C-runtime 8.0 (vcredist_ .exe) from Microsoft.
You will find the program under the following link: http://www.microsoft.com/downloads/details.aspx?FamilyID=EB4EBE2D-3 3C0-4A47-9DD4-B9A6D7BD44DA&displaylang=en
Download the installation program for Windows x64 from the Microsoft download page and execute it on each of the virtual machines that are to be monitored.2. Check the Support Package level.
Transaction OS07 was revised to display system-specific data in a virtual operating system environment. It is available in the following Basis Support Packages. Ensure that you have imported at least the required Support Package version into your SAP system:SAP NetWeaver 7.10
As of Support Package SAPKB71007SAP NetWeaver 7.01 (SAP NetWeaver 7.0)
As of Support Package SAPKB70102SAP NetWeaver 7.00 (SAP NetWeaver 7.0); transaction OS07N
As of Support Package SAPKB70017SAP NetWeaver 6.40; transaction OS07N
as of Support Package SAPKB640233. Checking the kernel patch
To use the new transaction, OS07 (OS07N), in Unicode systems, you require at least the following patch levels for the SAP kernel:Release 7.10: Patch level 119Release 7.01: Patch level 11Release 7.00: Patch level 178Release 6.40: Patch level 2514. Replacing the version of the data collector SAPOSCOL
You can use the command “saposcol.exe -v” to display the version of the data collector SAPOSCOL.
Use at least the following SAPOSCOL version that has been enhanced to collect and write virtualization-specific data:
VMware ESX Server 3.x: Version COLL 20.95 710 – 21.00 NT … patch number:143
VMware vSphere: Version COLL 20.95 710 – 21.03 NT … patch number:154
Hyper-V: not yet available
You can download SAPOSCOL from SAP Service Marketplace by choosing:
Download -> Support Packages and Patches -> Entry by Application Group -> Additional Components -> SAP Kernel -> SAP KERNEL 64-BIT -> SAP KERNEL 7.10 64-BIT -> SAP KERNEL 7.10 64-BIT -> Windows Server on x64 64bit -> #Database independent -> SAPOSCOL_-xxx.SAR
You can also use this version of SAPOSCOL for SAP releases that are based on kernels 6.40 and 7.00 When you use SAPOSCOL for these releases, problems may occur when attaching to the shared memory of the SAP system. In this situation, start SAPOSCOL before you start the SAP system.
To replace SAPOSCOL, proceed as follows:For SAP systems that do not have an SAP host agent installed (default: SAP systems below SAP Kernel Version 7.10), the following applies:
Stop the SAP service SAPOSCOL and replace the SAPOSCOL version.
Start the SAP service SAPOSCOL again.For SAP systems with installed SAP host agents, the following applies:
Stop the SAP service SAPHostExec and replace the SAPOSCOL version.
Start the SAP service SAPHostExec again.5. Importing the new version of the agent SAPCCMSR
The agent SAPCCMSR collects the 24h data and continues to process this.
The new version of the agent SAPCCMSR is provided in Patch Collection 2008/4 (or higher). For information about replacing the agent, see Note 1129577.
Additional work steps on VMware

1. Installing VMware Tools
To use an SAP system on VMware, the data collector SAPOSCOL requires access to the data in the virtualization layer. This data can be retrieved only if the VMware tools are installed in the relevant virtual machine.
When Windows 64-bit is the guest operating system, you can install the VMware tools as of the following ESX version only:
ESX Version 3.0.1: Patch ESX-1002082 at least
ESX Version 3.0.2: Patch ESX-1002086 at least
For more information about installing the tools, see the VMware documentation.
2. Activating the host parameter on VMware vSphere
To make the configuration data and performance data of the host available, you must configure the following parameter:
Host: Misc.GuestLibAllowHostInfoVirtual Machine: tools.guestlib.enableHostInfo

Configuration of the host to activate the host accessor functions
The transfer of host data is permitted by the following configuration of the host.
a) Select the host in the vSphere client window.b) Choose the “Configuration” tab page.c) In the listof software options, choose “Advanced Settings”.d) Choose the “Misc” window in “Advanced Settings”.e) Scroll down to Misc.GuestLibAllowHostInfo.f) Set the value to 1.

Configuration of the virtual machine to activate the accessor functions
Use the configuation editor in the vSphere client to edit the configuration file of the virtual machine. Deactivate the virtual machine before you use the configuration editor.
a) Right-click in the vSphere client window to select the virtual machine in the list.b) Choose “Edit Settings” in the dropdown menu.c) Choose the “Options” tab page.d) Under “Advanced” -> “General”, open the “Configuration Parameters” window.e) In the “Configuration Parameters” window, insert the following line (or set the value to TRUE if the line already exists):
tools.guestlib.enableHostInfo = “TRUE”

Additional work steps for Hyper-V
1. Installing the Hyper-V integration services in the VM
The data in the virtualization layer can be retrieved only if the Hyper-V integration services are installed on the relevant virtual host.
Install the Hyper-V integration services as follows:On the parent partition:
Open the Hyper-V manager and connect to the virtual host.
In the administration window of the virtual host, choose “Action -> Insert Integration Services Setup Disk”.In the client partition:
In Windows Explorer, switch to the DVD drive. Choose: Right-click -> “Install Hyper-V Integration Services”.2. Configuring the data collector SAPOSCOL
To access the data that is relevant for virtualization on Hyper-V, the system must read the SAPOSCOL data directly from the parent partition. To enable this access via the network, you must start SAPOSCOL in the user account LOCALSYSTEM. This is the case for a standard installation as of SAP kernel release 7.10.
If you use an SAP system that is based on SAP Kernel 6.40 or 7.00, SAPOSCOL is started as the Windows service SAPOSCOL in the following users:
SAP Kernel 6.40: SAPService
SAP Kernel 7.00: ADM
Therefore, for these systems, change the user in which the service SAPOSCOL is started to LOCALSYSTEM.3. Setting up the user rights on the parent partition
To ensure that the data can be determined from the host using WMI, you must provide the user “NetworkService” with rights for the virtual host that is to be monitored.
To do this, open the Computer Management Tool (Start -> Administrative Tools -> Computer Management).
If you use the parent partition Windows 2008 Core as the operating system, you must perform the following steps remotely in the Computer Management Tool of a different Windows Server 2008 host. In this situation, switch to a Windows Server 2008 installation, open the Computer Management Tool, and choose: Right-click -> “Connect to another computer”. Connect to the host of the parent partition.a) Add the user “NetworkService” of the virtual host that is to be monitored to the group of local administrators.
Choose “System Tools -> Local Users and Groups -> Groups -> Administrators”.
In the “Administrator Properties” window, choose “Add”.
In the “Select Users, Computers, or Groups” window, choose “Object Types” to activate the “Computers” type.
Choose “OK” to close the window.
In the “Object Names” field, enter the name of the parent position with the additional character “$”. Choose “Check Names” and choose “OK” to close all windows.b) Provide the user \$ with the right to use WMI to read data from the parent partition.
Proceed as follows:Open the Server Manager.
Choose “Configuration -> WMI Control”.
Right-click and choose “Properties”.In the “WMI Control Properties” window, choose the “Security” tab.In the “Namespace navigation” window, select “Root -> CIMV2″. Choose “Security”.In the “Group or user names” window, add the user \$. (Select “computers” as the object type.)
For the newly-created user, select all of the rights in the “Permissions” window and grant the “remote enable” right.Choose “Advanced” to grant this user the rights for all subnamespaces; to do this, select “apply to this namespace and all subnamespaces”.