WinCC Server Virtualization en PDF

Cover
WinCC/Server Virtualization
WinCC Technical Information April 2011
Applications & Tools

Answers for Industry.
Industry Automation and Drive Technologies Service & Support Portal This article is taken from the Service Portal of Siemens AG, Industry Automation and Drive Technologies. The following link takes you directly to the download page of this document. http://support.automation.siemens.com/WW/view/en/49368181
If you have any questions about this document, please contact us at the following e-mail address: online-support.automation@siemens.com
Copyright Siemens AG 2011 All rights reserved
WinCC/Server Virtualization V1.0, Entry ID: 49368181
Automation Task Automation Solution Procedure for the Virtualization Framework Conditions for the Measurements Test Scenarios and Basic Performance Data Diagnostic Capabilities Glossary
1 2 3 4 5 6 7 8 9
SIMATIC WinCC/Server Virtualization
Links & Literature History
Warranty and Liability
Warranty and Liability

Note The application examples are not binding and do not claim to be complete regarding configuration, equipment and any eventuality. The application examples do not represent customer-specific solutions. They are only intended to provide support for typical applications. You are responsible for ensuring that the described products are used correctly. These application examples do not relieve you of the responsibility to use sound practices in application, installation, operation and maintenance. When using these Application Examples, you recognize that we cannot be made liable for any damage/claims beyond the liability clause described. We reserve the right to make changes to these application examples at any time without prior notice. If there are any deviations between the recommendations provided in this application example and other Siemens publications e.g. Catalogs the contents of the other documents have priority. We accept no liability for information contained in this document. Any claims against us based on whatever legal reason resulting from the use of the examples, information, programs, engineering and performance data etc., described in this Application Example shall be excluded. Such an exclusion shall not apply in the case of mandatory liability, e.g. under the German Product Liability Act (Produkthaftungsgesetz), in case of intent, gross negligence, or injury of life, body or health, guarantee for the quality of a product, fraudulent concealment of a deficiency or breach of a condition which goes to the root of the contract (wesentliche Vertragspflichten). However, claims arising from a breach of a condition which goes to the root of the contract shall be limited to the foreseeable damage which is intrinsic to the contract, unless caused by intent or gross negligence or based on mandatory liability for injury of life, body or health. The above provisions do not imply a change in the burden of proof to your detriment. It is not permissible to transfer or copy these Application Examples or excerpts thereof without express authorization from Siemens Industry Sector.
Preface
Preface
Objective of this application This document provides an overview over the WinCC/Server Virtualization. Typical configurations on virtualized servers are displayed and measured performance data is represented.
Core topics of this application The following main points are discussed in this application: Validity This document is valid for WinCC/Server V7.0 SP2. Display of typical configurations Display of performance data in the various configurations Monitoring the performance of all guest systems
Copyright Siemens AG 2011 All rights reserved 49368181_WinCC_Server_virtualization_en.doc
Table of Contents
Table of Contents
Warranty and Liability ................................................................................................. 4 Preface .......................................................................................................................... 5 1 Automation Task................................................................................................ 8 1.1 1.2 2 2.1 2.1.1 2.1.2 2.2 2.2.1 2.2.2 2.2.3 2.2.4 3 3.1 3.2
Overview .............................................................................................. 8 Virtualization requirements................................................................... 8 What is virtualization? .......................................................................... 9 Definition .............................................................................................. 9 Advantages of the virtualization ......................................................... 11 Requirements ..................................................................................... 12 Required software .............................................................................. 12 ESX server with WinCC guest systems ............................................. 12 Guest systems.................................................................................... 13 Further information ............................................................................. 13 Process and required software .......................................................... 14 Procedure in detail ............................................................................. 15 Hardware used ................................................................................... 19 Configuration of the guest systems.................................................... 21 Used software .................................................................................... 23 WinCC standalone ............................................................................. 27 WinCC Server and one WinCC Client................................................ 28 WinCC Server and two WinCC Standard Clients .............................. 29 WinCC Server and three WinCC Standard Clients............................ 32 WinCC Server on ESXi (1) and four WinCC Clients on ESXi (2)....... 36 WinCC Server on ESXi (1) and four WinCC Standard Clients on ESXi (2) ....................................................................................................... 36 WinCC Server on ESXi (1) and four WinCC Multi Clients on ESXi (2)39 WinCC Server and four WinCC Standard Clients.............................. 42 WinCC Server and four WinCC Multi Clients on one ESXi................ 44 WinCC Server on ESXi (1) and five WinCC Standard Clients on ESXi (2) ....................................................................................................... 46 WinCC Server on ESXi (1) and five WinCC Standard Clients on ESXi (2) ....................................................................................................... 49 WinCC Server and six WinCC Standard Clients on one ESXi........... 52 WinCC Server and six WinCC Multi Clients on one ESXi.................. 55 Using redundant server on one or two ESXi servers ......................... 58 Effects of the redundancy switch-over on the CPU load.................... 58 Two redundant servers as stand-alone stations on an ESXi server .. 61 Two redundant server without operation as stand-alone stations on ESXi (1) with four WinCC Multi Clients on ESXi (2)........................... 64 Two ESXi servers with one redundant server each and two WinCC clients ................................................................................................. 69 Two redundant WinCC servers without operation with six WinCC multi clients on one ESXi server ................................................................. 72 Two ESXi servers with one redundant server each and three WinCC clients each ........................................................................................ 75
Automation Solution ......................................................................................... 9
Procedure for the Virtualization ..................................................................... 14
Framework Conditions for the Measurements ............................................. 19 4.1 4.2 4.3
Test Scenarios and Basic Performance Data ............................................... 25 5.1 5.2 5.3 5.4 5.5 5.5.1 5.5.2 5.5.3 5.5.4 5.5.5 5.5.6 5.5.7 5.5.8 5.6 5.6.1 5.6.2 5.6.3 5.6.4 5.6.5 5.6.6
Table of Contents 5.6.7 5.6.8 5.6.9 6 6.1 6.2 7 8 Two redundant WinCC servers on ESXi (1) and one WinCC client with WinCC/Webnavigator, as well as 3 WinCC WebClients on ESXi (2) 78 Two redundant WinCC servers and one WinCC client with WinCC/Webnavigator, as well as 3 WinCC WebClients on one ESXi82 Using one (external) engineering station for downloading the projects85 Diagnosis with VMware vSphere Client ............................................. 86 Diagnosis in the virtual system........................................................... 88
Diagnostic Capabilities ................................................................................... 86
Glossary ........................................................................................................... 89 Links & Literature ............................................................................................ 91 8.1 8.2 Literature ............................................................................................ 91 Internet links ....................................................................................... 91
History............................................................................................................... 91
1 Automation Task 1.1 Overview
1
1.1
Automation Task
Overview
Virtualization of servers are already of high importance in information technology. In automation technology the advantages of virtualization shall also be reached.
Introduction
Description of the automation task Typical configurations of WinCC systems shall be virtualized. Which infrastructure and which configuration steps are necessary in order to virtualize WinCC plants?
1.2
Virtualization requirements
The requirements for virtualized computers are identical to those for real computers. During runtime no difference to real computers shall be noticeable.
2 Automation Solution 2.1 What is virtualization?
2
2.1
2.1.1
Automation Solution
What is virtualization?
Definition
Virtualization Virtualization refers to the runnable mapping of one or several computers on a real computer. On a real computer a special software runs which provides one or several virtual computers parallel. The virtual computers can be started and stopped independent of each other. Even after a crash only the respective virtual computer is affected.
Layout for virtualization

Figure 2-1
Virtualized System 1
Virtualized System n Graphics card Network card Network card Network card
Sound card
Hard disks
Memory Memory
A physical PC provides its hardware to several virtualized systems.
CPUs CPUs
Graphics card
Sound card
Hard disks
Memory Sound card
CPUs
Graphics card
Physical PC
Hard disks
Physical Hardware
2 Automation Solution 2.1 What is virtualization? Differences between server-based and client-based virtualization
Figure 2-2
Client-based Virtualization
Applicat ion for v Applica tio A tualizatio (z.B n for ir pM lic .p aa V v tio n (z.B nW w alizatio foo r ir .V vtu ir M tu (e.g wre are liza st .V aa ti tin Wrk M on ork w ) are st aon W tio ork n) st a tio n) Virtualiz ed syste m App App . . 1 n (e.g (e.g .W o .W o rd) rd) Operatin g sy (e.g. W in stem dows)
Virtualiz ed Hard ware
Server-based Virtualization
Virtualized Virtualisiertes System Virtualisiertes Virtualisiertes System 1 System 2 System 3 n

App. 1 App. n (e.g.W (e o.g rd.W ) ord)
Applicat Applicat ion 1 ion n (e (e.g. M .o M S S.g W rd ) W ord)
Operating system (e.g. Windows) Virtualized Hardware
Operating System (e.g. Windows)
Application for Virtualization (=operating system)
Hardware
Hardware
Physical PC
Physical PC No direct operation. Operation e.g. via one or several RDP clients.
Operation directly at the PC via graphics card and monitor.
RDP
10
2 Automation Solution 2.1 What is virtualization?
2.1.2
Advantages of the virtualization
Reduction of the hardware costs Reduced HW costs through consolidating several physical computers. (The cost reduction results from a better hardware utilization.) On the client side more cost-efficient hardware is possible. Expanded application areas: SIMATIC ThinClient solutions (PC, Panel, mobile PDA).
Reducing the time expenses for service and maintenance Shorter times for updates and backups since these are executed from a central place Reduced maintenance cost and time through central administration. Server configuration by means of remote management tools.
Increased safety
Increased safety through remote access and centralized rights management. Virtually no possible attacks for Thin Clients, central protection at the virtual server.
Increased availability Exchange of hardware at the virtual server is possible during runtime. Increased flexibility Additional clients can be added on demand simply by starting a further VMware session. Additional clients for special tasks can simply run in the background: RDP 2/VNC 3-solutions for remote or mobile accesses Provision of substitute computers as virtual systems, e.g. during maintenance of a system a substitute system can be used instead.
1
1 2
When using the respective virtualization hardware. Windows Remote Desktop protocol: There is a number of possible clients for various operating systems of for mobile devices. (The server is located in the Windows operating system.) 3 Virtual Network Computing: alternative option for remote control of operating systems. (A server is required on the operating system. Viewing requires a client, which are also available for various operating systems or for mobile devices.
11
2 Automation Solution 2.2 Requirements
2.2
Note
Requirements
WPF controls in VMware WinCC offers using WPF controls for the visualization. This option does not work on virtualized systems! (See Literature \4\.)
2.2.1
Required software
Virtualization software VMware Player and VMware Converter or VMware Workstation VMware vSphere Client
SIMATIC Software and operating system

WinCC (version depending on the application) Windows operating system (depending on the application) Windows 2003 Server or Windows 2008 Server Windows XP or Windows 7
2.2.2
ESX server with WinCC guest systems

The application/administration is required to supply and ensure sufficient system resources on the virtualization server and the virtual systems.
ATTENTION
Table 2-1 Features Number of CPU cores Separation of networks Graphics card settings VMware Tools CPU load RAM Requirements For the ESX server at least two real CPU cores are required. Terminal bus and plant network must be separated with separate real network cards. 32MB VMWare tools must be installed on the guest computers. The CPU load system must not exceed a load of >75%. (source: according to VMWare) For secure operation a work memory of 2 GB must be reserved for the ESXi server. (For communication/network activities and management of the ESXi.)
12
2 Automation Solution 2.2 Requirements
2.2.3
Guest systems
Table 2-2 Features Number of CPU cores Requirements WinCC server: a WinCC Server guest system requires at least two logic CPU cores. WinCC Client: a WinCC Server guest system requires at least one logic CPU core. At least 2 physical modules are required. (one of which exclusively for the PLC bus) Separation of terminal, PLC and Windows networks. If necessary, the terminal and Windows network can be combined. The CPU load of the assigned logic CPU cores must not exceed 70% to 80%. Note When archiving large data volumes a respective reserve is required (high I/O load). (This load is given at a capacity of 70%-80%.) VMWare tools must be installed on the guest computers. (This yields a better performance.) If you are not using a dynamic storage management (the size of the hard disk file adjusts dynamically to the used capacity.). Pausing of the guest systems, as well as VMWare options (vMotion) are not supported. The guest systems must be treated like real WinCC Server/Clients.
Modules Separation of networks
CPU load
VMware tools
Hard disk storage management Operating states
ATTENTION
Please note the standard requirements for WinCC installations. These are available in the release note on WinCC or under the following link. https://www.automation.siemens.com/mdm/default.aspx?DocVersionId=16509 462027&TopicId=14329600907 Chapter 4.2 Configuration of the guest systems contains the properties employed for the measurements used in this document.
Note
2.2.4
Further information
Optimal operation of ESXi server and VMWare Further information on the optimal operation is available on the support internet pages of VMWare under the following link. http://www.vmware.com/support Enabled hardware for VMware The following internet address contains a summary of the hardware validated and enabled by VMWare. http://www.vmware.com/resources/compatibility/search.php
13
3 Procedure for the Virtualization 3.1 Process and required software
3
Content
Procedure for the Virtualization

This chapter shows you how to create virtual WinCC systems.
3.1
Process and required software

Table 3-1 No. 1. Step Establishing and creating the Management Station Virtualization SW VMware Workstation or VMware Player VMware Converter VMware vSphere Client VMware Workstation or VMware Player Depending on the application: Windows XP Windows 7 Windows 2003 Server Windows 2008 Server Respective WinCC version depending on the application. VMware ESXi and VMware vSphere client VMware Converter and VMware ESXi VMware ESXi and VMware vSphere client --Guest SW
2. 3.
Creating the virtual system Installation and configuration of the operating system on the virtual system
4.
Installation of WinCC on the virtual system Installation and configuration of the virtualization server Transferring the virtual system onto the virtualization server Adjusting the configuration of the virtual system to the virtualization server Start and operation of the virtual system Checking the system load of the virtual system and the virtualization server. Operating the virtual system. Windows Remote Desktop.
5.
6.
7.
8. 9.
10.
WinCC
Note
The VMware Workstation software is recommended for creating a virtual system.
14
3 Procedure for the Virtualization 3.2 Procedure in detail
3.2
Note
Procedure in detail
The procedure described here is only an example and represents one possible approach. Scenarios leading to the same result are also possible.
Table 3-2 No. 1. Step/Action Establishing and creating the management station In addition to the virtualization server you require a PC in the same network as the virtualization server. Ensure that the following software has been installed on the management station. Operating system: Windows 7 or Windows XP VMware vSphere VMware Converter or VMware Workstation VMware Workstation or VMware Player Creating the virtual system on the management station Start the VMware Player. Select the Create a New Virtual Machine option. The New Virtual Machine Wizard appears. Here you select the point I will install the operating system later and click on Next. In the Guest operation system field you select Microsoft Windows and in the Version field you select your respective operating system. Then click on Next. (Information on the operating system compatibilities are available in the FAQ with entry ID: 21927773). Assign a unique name for your virtual system. Specify a local storage path and click on Next. (In the further course the virtual system is exclusively identified via this name.) Assign the hard disk size required for your combination and select the Store virtual disk as a single file option. Click on Next. An overview with the properties of the newly created virtual system appears. The properties must then still be adjusted! Click the Customize Hardware button. Another window with the option of configuring individual hardware components appears. Memory: here you assign the storage as specified in chapter 2.2.3 Guest systems. Processors: here you assign the number of processor cores as specified in chapter 2.2.3 Guest systems. CD/DVD: here you enter the physical drive you wish to use for installing the operating system and WinCC. Floppy: not mandatory, if it is not required remove the component with the Remove button. Network adapter: used here for the installation. (e.g. for activating the operating system.) Here in the Network connection field you select the type which is best for accessing your network. USB controller: is mandatory. (Installation of the license with USB stick.) Sound card: not mandatory, if no acoustic signaling is required remove this component with the Remove.
2.
15

No.
Step/Action Printer: not mandatory, if it is not required remove the component with the Remove button. Display: leave the settings. Add a second network cars if the virtual system shall have a terminal bus and a process bus. Confirm the Hardware window with OK. You are back in the window with the properties of the newly created virtual system. Click on Finish. You have now created a virtual system.
3.
Installation and configuration of the operating system on the virtual system [management station] Create the installation medium for the operating system in the physical drive. Start the newly created virtual system by clicking on Play virtual machine. Now you see the boot process of the virtual system. The installation of the operating system is now offered to you. Start the installation of the operating system. Follow all instructions as for a classic installation. Configure the operating system after completing the installation. Installing the VMware tools. Configure the operating system according to the requirements of WinCC Release and the installation notes. https://www.automation.siemens.com/mdm/default.aspx?DocVersionId= 16509462027&TopicId=14295778955 Install the required security patches. (Respective information is available in the FAQ with entry ID: 18752994. Installation of WinCC on the virtual system [management station] Place the WinCC installation medium into the physical drive. Start the virtual system by clicking Play virtual machine. Start the installation of WinCC. Follow the instructions from WinCC Release and the installation notes. https://www.automation.siemens.com/mdm/default.aspx?DocVersionId=165 09462027& TopicId=14291213323 Installation and configuration of the virtualization server The following steps require monitor and keyboard at the virtualization server. Place the VMware ESXi installation CD into the drive of the virtualization server and start it. In the BIOS you specify booting from CD. Follow the instructions of installation wizard. Perform the first basic configuration steps. Assign a root password. Adjust the network connection.
4.
5.
16

No. 6. Step/Action Transferring the virtual system onto the virtualization server Variant (A) [VMware Converter on the management station] Ensure that the VMware Player has been connected. Start the VMware converter. Click on the Convert machine button. The Conversion dialog appears. Select the source type VMware Virtual Workstation and select your virtual system in the storage location of your virtual system. Click on Next. Select VMware Virtual Infrastructure Machine. Enter the user data defined in step 5 as well as the IP address of the ESXi virtualization server. Click on Next. Keep the name of your virtual system or assign a new name. Click on Next. In the item list you select your ESXi, the respective data storage (the physical drive on which the virtual system shall be stored) and the VMware version (typical Version 7). An overview appears with all parameters for transferring the virtual machine to the virtualization server. Check the parameters and, if necessary, change unsuitable points. Click on Next. A list with all settings made appears. Start the process by clicking on Finish. The conversion process begins. Variant (B) [only VMware Workstation on the management station] Ensure that your virtual system is not active. Start the Conversion Wizard via VMware Workstation > File > Import/Export. The Wizard appears. In the overview you click on Next. Another overview appears for step 1. Click on Next. Select Virtual Appliance from the dropdown list and click on Next. In the following dialog your select your virtual system and click on Next. Information on your virtual system is collected. In the following step of the Wizard you select all required hard drives of the system and click on Next. The overview for step 2 appears. Select VMware Infrastructure Virtual Machine as a target type and click on Next. Enter the user data defined in step 5 as well as the IP address of the ESXi virtualization server. Click on Next. The Conversion Wizard connects with the virtualization server. In the following dialog you assign a unique name for your virtual system. Now you select the Host used and click on Next. The hard disk information of the virtualization server is called up. Select your target drive and click on Next. The target parameters are checked. Assign the required networks and click on Next. The dialog for making userdefined settings appears. Deactivate the options and click on Next. An overview of the settings made appears. Deactivate the Power on the new virtual machine after creation option and click on Finish.
17

No. 7. Step/Action Adjusting the configuration of the virtual system to the virtualization server [management station] Start your VMware VSphere client. The log-on dialog appears: Enter the IP address of your virtualization server and your user data. The vSphere client starts. Select your transferred virtual system in the tree. In the right window pane you navigate to the Overview tab. In the Commands field you select the Edit settings entry. Check whether the assigned resources match the requirements from chapter 2.2.3 Guest systems. Start and operation of the virtual system [management station] Start your VMware VSphere client. The log-on dialog appears: Enter the IP address of your virtualization server and your user data. The vSphere client starts. Select your transferred virtual system in the tree. Start your virtual system by clicking the Play button. Your system is now restarted. Checking the system load of the virtual system and the virtualization server. [management station] Diagnostics information is available in chapter 6 Diagnostic Capabilities. Operating the virtual system [management station] Ensure that your virtual system is active. Click Start > Run.... Enter mstsc /? in the dialog. Check whether the option /console or /admin must be used to administer your virtual system. Confirm the dialog with OK. Click Start > Run.... In the dialog you enter mstsc /admin or mstsc /console. Then the Windows Remote Desktop starts. Enter the Login data of your user. You can now use the virtual system as usual.
8.
9.
10.
18
4 Framework Conditions for the Measurements 4.1 Hardware used
4
4.1
Framework Conditions for the Measurements

Hardware used
Table 4-1 Component Processor ESX-Server 1 Intel Core i7-610E 2Cores/4Threads 2.53MHz cycle frequency with Turbo Boost 4MB Cache VT-d and EM64T as expanded command sets 8 Gbytes DDR3 1066 SD-RAM 2x 500GB 1x Onboard 82574L the only one accepted by VMware. 2x Intel PRO/1000GT (1000Base-T PCI), additionally plugged. ESX-Server 2 Intel Core i7-610E 2Cores/4Threads 2.53MHz cycle frequency with Turbo Boost 4MB Cache VT-d and EM64T as expanded command sets 8 Gbytes DDR3 1066 SD-RAM 2x 1000GB 1x Onboard 82574L the only one accepted by VMware. 2x Intel PRO/1000GT (1000Base-T PCI), additionally plugged.
Configuration 1, IPC 647C
RAM Hard disks Network cards

The network cards were used as follows:

Table 4-2 Network card Onboard 82574L Intel PRO/1000GT Intel PRO/1000GT Terminal Bus PLC Bus Usage Management network e.g. for vSpereClient access to ESXi
Note
Further information on the used SIMATIC Industry PC is available in the following link. http://www.automation.siemens.com/mcms/pc-based-automation/en/industrialpc/rack-pc/simatic-ipc647c/Pages/Default.aspx
19
4 Framework Conditions for the Measurements 4.1 Hardware used Configuration 2, HP Blade System C7000 Enclosure G2 Two Blade ESXi servers as cluster.
Table 4-3 Component Processor RAM Used for ESXi Processor RAM Hard disks Network cards 192 GB 8 Cores (Intel Xeon Core i7 L5520, 2.27GHz) 98GByte No local hard disks, ESXi servers work with SAN (Storage Area Network). HP VC-Flags-10 ENET module 1GB (for management and communication with the PLCs). Property 16 Cores (Intel Xeon Core i7 L5520, 2.27GHz)
For this HP Blade System Resources can be dynamically combined and assigned. The above table shows that only a part of the resources are used. Further information on the used HP Blade system is available in the following link. http://h18004.www1.hp.com/products/blades/bladesystem/
Note
Configuration 3, Fujitsu Primergy RX 300 S6 An ESXi server is used here.

Table 4-4 Component Processor RAM Hard disks 24 GB 6x 600GB SATA (local) Property 12 Cores (Intel Xeon CPU 5650 2.67GHz)
Note
Further information on the used Fujitsu Primergy system is available in the following link. http://de.fujitsu.com/products/standard_servers/rack/primergy_rx300s6.html When comparing the measuring data you will notice that the values of the better equipped HP Blade servers are slightly worse than those of the Fujitsu RX 300. This is, amongst other things, due to the fact that the ESX server on the Fujitsu RX 300 has over 12 CPUs. The ESX server of the HP Blade servers has only 8 CPUs available.
Note
20
4 Framework Conditions for the Measurements 4.2 Configuration of the guest systems
4.2
Note
Configuration of the guest systems

For the settings of the guest systems please follow the installation notes and quantity frameworks of WinCC. http://support.automation.siemens.com/WW/view/en/37437018
Remote Desktop Protocol (RDP) The operating stations can be operated via an opened Remote Desktop connection. The measurements listed below were measured with opened Remote Desktop window. Note Remote Desktop must only be used via mstsc /console or mstsc /admin. Continuing information is available in chapter 3.2 Procedure in detail, in chapter 3.2 Procedure in detail in table section 5 Operating the virtual system.
Reserved work memory for ESXi

For secure operation a work memory of 2 GB must be reserved for the ESXi server. In configuration 1, IPC 647C there are 6 GB available for the virtualization. This requirement was not met in some of the following scenarios since the limits also had to be tested.
WinCC Server (server operating system) Independent of whether Windows Server 2003 or Windows Server 2008 was used.
Table 4-5 Hardware RAM CPUs Graphics card Hard disk 1 Hard disk 2 CD/DVD drive Network adapter 1 Network adapter 2 Disk drive 1 3072MB 2 32MB Virtual hard disk, not dynamic Virtual hard disk, not dynamic ISO Image (with image of the WinCC DVD) Terminal bus PLC network Client device Setting
21
4 Framework Conditions for the Measurements 4.2 Configuration of the guest systems
Figure 4-1
WinCC Client (Windows 7)

Table 4-6 Hardware RAM CPUs Graphics card Hard disk 1 CD/DVD drive Network adapter 1 Disk drive 1 2048 MB 2 32MB Virtual hard disk, not dynamic ISO Image (with image of the WinCC DVD) Terminal bus Client device Setting
WinCC Client (Windows XP SP3)

Table 4-7 Hardware RAM CPUs Graphics card VMCI device Hard disk 1 CD/DVD drive Network adapter 1 Virtual hard disk, not dynamic ISO Image (with image of the WinCC DVD) Terminal bus 1024MB 2 32MB Setting
22
4 Framework Conditions for the Measurements 4.3 Used software

Hardware Network adapter 2 Disk drive 1 PLC network Client device Setting
4.3
Used software
Table 4-8 Type WinCC Server WinCC Client Operating system Windows 2003R2 Server with SP2 Windows 2008 Server (standard) with SP2 Windows 7 Windows XP Professional +SP3
Operating systems
Note
The measurements have yielded that the operating systems Windows 7 and Windows 2008 Server generally have a higher RAM demand than their predecessor.
Released WinCC software

Table 4-9 Product WinCC V7.0 with SP2 WinCC/Server WinCC/UserArchive WinCC/Redundancy WinCC/WebNavigator WinCC/DataMonitor WinCC/Connectivity Pack
Note
All further options of SIMATIC WinCC V7.0 SP2 are neither compatibility-tested nor approved for virtual environments.
WinCC quantity framework/project

Table 4-10 Criterion Number of connection with CPUs Number of external S7 variables Curve archiving 2 64000 4200 values/second Property
23
4 Framework Conditions for the Measurements 4.3 Used software

Criterion Message archiving UserAchive Picture change Property 8 messages/second 25 sets with two values in 5 seconds In 5 seconds interval; Or whichever deviating value is given in the subsequent tests.
24
5 Test Scenarios and Basic Performance Data 4.3 Used software
Test Scenarios and Basic Performance Data

The values shown in the subsequent test scenarios were determined in two different ways. It is differentiated between ... Host system (determined CPU values and active RAM with vSphere Client.) Guest system (determined values in the operating system using the performance monitor.)
Determining the basic performance data of the guest systems
The example in the following graphic displays the monitoring of the guest system with the performance monitor (in the operating system). Using the Microsoft performance monitor enables simple monitoring of the processes and the storage consumption in the operating system.
Figure 5-1
Determining the basic performance data of the ESXi server When monitoring the ESXi server the following recordings were made in the test scenarios: CPU load Active work memory
25
5 Test Scenarios and Basic Performance Data 4.3 Used software Interpretation of the measured values The following graphic represents an overloaded ESXi server. (Due to the overload the recording of archived data was stopped temporarily.) Note A CPU load of 75% should not be exceeded permanently.
Figure 5-2
26
5 Test Scenarios and Basic Performance Data 5.1 WinCC standalone
5.1
Overview
WinCC standalone
The figure below shows a schematic illustration of the virtual components of this solution. Two measurements are performed (with Windows 2008 server and Windows 2003 server). The SIMATIC IPC 647C is used as the test platform.
Figure 5-3
WinCC Server Win 2008 Server
ESXi (1)
ESXi (2) SIMATIC IPC 647C
SIMATIC IPC 647C
Basic performance data

Table 5-1 PC Host/ Guest PC ESXi (1) Host WinCC Server Win Server 2008 WinCC Server Win Server 2008 ESXi (2) Host WinCC Server Win Server 2003 WinCC Server Win Server 2003 CPU in % 36% 35% Max. CPU in % 58% 57% Active RAM 1.3 GB (max. 2 GB) 1.2 GB (max. 1.9 GB) 1.9 GB
IPC 647C: ESXi (1)
Guest
25%
50%
IPC 647C: EXSi (2)
39% 38%
65% 64%
665 MB (max. 1.3 GB) 595 MB (max. 1.2 GB) 1.4 GB
Conclusion Using Windows 2008 Server requires more storage on the ESXi server. This also applies for the client operating system Windows 7.
Guest
27%
44%
27
5 Test Scenarios and Basic Performance Data 5.2 WinCC Server and one WinCC Client
5.2
Overview
WinCC Server and one WinCC Client

The figure below shows a schematic illustration of the virtual components of this solution. Two measurements are performed (with Windows 2008 server and Windows 2003 server). The SIMATIC IPC 647C is used as the test platform.
Figure 5-4
WinCC Client Win XP
WinCC Client Win XP

Description Operations occur at the WinCC server and the WinCC client. On both stations pictures change in 5 seconds intervals for simulating an operation. Basic performance data
Table 5-2 PC Host/ Guest PC ESXi (1) WinCC Server Win Server 2008 Host WinCC Client Windows XP WinCC Server Win Server 2008 WinCC Client Windows XP EXSi (2) WinCC Server Win Server 2003 Host WinCC Client Windows XP WinCC Server Win Server 2003 WinCC Client Windows XP CPU in % 56% 34% 21% 29% 11% 59% 37% 21% 37% 14% Max. CPU in % 85% 59% 35% 59% 19% 90% 61% 40% 63% 24% Active RAM 1.4GB (max. 2GB) 1GB (max. 1.6GB) 235MB (max. 315MB) 1.9GB 485MB 970MB (max. 1.6GB) 220MB (max. 515MB) 320MB (max. 515MB) 1.4GB 490GB
IPC 647C: ESXi (1) IPC 647C: EXSi (2)
Guest
Guest
28
5 Test Scenarios and Basic Performance Data 5.3 WinCC Server and two WinCC Standard Clients
5.3
Overview
WinCC Server and two WinCC Standard Clients

The figure below shows a schematic illustration of the virtual components of this solution. Two measurements are performed per virtualization server (with Windows 2008 Server and Windows 2003 Server). The test platforms are: SIMATIC IPC 647C HP Blade Server Fujitsu Primergy
Figure 5-5
WinCC Client Win XP
WinCC Client Win 7
WinCC Client Win XP
WinCC Client Win 7
WinCC Client Win XP
WinCC Client Win 7
WinCC Client Win XP
WinCC Client Win 7
ESXi (1)
ESXi (2)
HP Blade Server
WinCC Client Win XP
WinCC Client Win 7
WinCC Client Win XP
WinCC Client Win 7
ESXi (1) Fujitsu Primergy
29
5 Test Scenarios and Basic Performance Data 5.3 WinCC Server and two WinCC Standard Clients Description Operator actions occur at the server and both clients. On both stations pictures change in 5 seconds intervals for simulating an operation. Basic performance data
Table 5-3 PC Host/ Guest PC ESXi (1) WinCC Server Win Server 2008 WinCC Client Windows XP Host IPC 647C: ESXi (1) WinCC Client Windows 7 WinCC Server Win Server 2008 Guest WinCC Client Windows XP WinCC Client Windows 7 EXSi (2) WinCC Server Win Server 2003 WinCC Client Windows XP Host IPC 647C: EXSi (2) WinCC Client Windows 7 WinCC Server Win Server 2003 Guest WinCC Client Windows XP WinCC Client Windows 7 ESXi WinCC Server Win Server 2008 WinCC Client Windows XP Host HP Blade: ESXi (1) WinCC Client Windows 7 WinCC Server Win Server 2008 Guest WinCC Client Windows XP WinCC Client Windows 7 CPU in % 70% 34% 19% 17% 39% 20% 16% 78% 38% 23% 16% 51% 18% 14% 17% 34% 20% 13% 36% 19% 14% Max. CPU in % 92% 51% 40% 41% 70% (max. 2.7GB) 30% (max. 2.7GB) 60% (max. 2.7GB) 100% 63% 40% 26% 74% (max. 2.7GB) 45% (max. 2.7GB) 40% (max. 2.7GB) 27% 57% 40% 31% 67% 34% 26% 2 GB (max. 2.4GB) 975MB (max. 1.3GB) 220MB (max. 295MB) 840MB (max. 1GB) 1.6 GB 460 MB 880 MB 2.0 GB (max. 2.8GB) 770MB (max. 1.3GB) 320MB (max. 515MB) 800MB (max. 1GB) Active RAM 2.2GB (max. 2.7GB) 1.4GB (max. 1.9GB) 210MB (max. 305MB) 455MB (max. 965MB)
30
5 Test Scenarios and Basic Performance Data 5.3 WinCC Server and two WinCC Standard Clients
PC Host/ Guest ESXi WinCC Server Win Server 2003 WinCC Client Windows XP Host HP Blade: ESXi (2) WinCC Client Windows 7 WinCC Server Win Server 2003 Guest WinCC Client Windows XP WinCC Client Windows 7 ESXi WinCC Server Win Server 2008
PC
CPU in % 17% 37% 17% 13% 42% 17% 11% 11% 33% 17% 12% 23% 12% 7% 11% 36% 17% 12% 26% 12% 7%
Max. CPU in % 26% 59% 36% 30% 51% 36% 25% 19% 50% 38% 28% 42% 24% 13% 18% 48% 39% 29% 36% 23% 14%
Active RAM 1.6GB (max. 2GB) 535MB (max. 880MB) 180MB (max. 285MB) 800MB (max. 1.1GB) 1.2 GB 500 MB 860 MB 1.9GB (max. 2.4GB) 1.3GB (max. 1.6GB) 215MB (max. 515MB) 405MB (max. 525MB) 1.6 GB 465 MB 910 MB 1.3GB (max. 1.9GB) 670MB (max. 1GB) 215MB (max. 305MB) 400MB (max. 600MB) 1.3GB 480MB 920MB
Fujitsu Primergy: ESXi (1)
WinCC Client Windows XP Host WinCC Client Windows 7 WinCC Server Win Server 2008 Guest WinCC Client Windows XP WinCC Client Windows 7 ESXi WinCC Server Win Server 2003
Fujitsu Primergy: ESXi (2)
WinCC Client Windows XP Host WinCC Client Windows 7 WinCC Server Win Server 2003 Guest WinCC Client Windows XP WinCC Client Windows 7
Conclusion SIMATIC IPC 647C This configuration puts considerable load on the ESXi server on the SIAMTIC IPC 647C.
ATTENTION
A permanent operation in this constellation is not recommended.
31
5 Test Scenarios and Basic Performance Data 5.4 WinCC Server and three WinCC Standard Clients Conclusion for HP Blade server and Fujitsu Primergy RX 300 Both computers in this configuration are not used to capacity. The active storage requirement is equally high as for SIMATIC IPC 647C. The basic performance data of the operating systems remain almost identical, the configuration of the guest systems remains unchanged.
5.4
Overview
WinCC Server and three WinCC Standard Clients

The figure below shows a schematic illustration of the virtual components of this solution. For each virtualization server two measurements are performed (with Windows 2008 Server and Windows 2003 Server). The test platforms are: SIMATIC IPC 647C HP Blade Server Fujitsu Primergy
Figure 5-6
WinCC Client Win XP
WinCC Client Win XP
WinCC Client Win 7
WinCC Client Win XP
WinCC Client Win XP
WinCC Client Win 7
WinCC Client Win XP
WinCC Client Win XP
WinCC Client Win 7
WinCC Client Win XP
WinCC Client Win XP
WinCC Client Win 7
ESXi (1)
ESXi (2)
HP Blade Server
32
5 Test Scenarios and Basic Performance Data 5.4 WinCC Server and three WinCC Standard Clients
WinCC Client Win XP
WinCC Client Win XP
WinCC Client Win 7
WinCC Client Win XP
WinCC Client Win XP
WinCC Client Win 7
Description The clients are WinCC standard clients. There is no operation at the server, on the clients pictures change every 5 seconds. Basic performance data
PC
Host/ Guest
Computer ESXi (1) WinCC Server Win Server 2008 WinCC Client Windows XP WinCC Client Windows XP
CPU in % 76% 30% 14% 15% 16% 41% 12% 17% 14%
Max. CPU in % 100% 45% 41% 31% 30% 80% 51% 36% 59%
Active RAM 2.8 GB (max. 3.7 GB) 1 GB (max. 1.4 GB) 570 MB (max. 725 MB) 595 MB (max. 755 MB) 515 MB (max. 1.1 GB) 1.9 GB 510 MB 510 MB 950 MB
Host
WinCC Client Windows 7 WinCC Server Win Server 2008 WinCC Client Windows XP
ICP 647C: ESXi (1)
Guest
WinCC Client Windows XP WinCC Client Windows 7
33
PC Host/ Guest Computer EXSi (2) WinCC Server Win Server 2003 WinCC Client Windows XP WinCC Client Windows XP WinCC Client Windows 7 WinCC Server Win Server 2003 WinCC Client Windows XP WinCC Client Windows XP WinCC Client Windows 7 ESXi WinCC Server Win Server 2008 WinCC Client Windows XP WinCC Client Windows XP WinCC Client Windows 7 WinCC Server Win Server 2008 WinCC Client Windows XP WinCC Client Windows XP WinCC Client Windows 7 ESXi WinCC Server Win Server 2008 WinCC Client Windows XP WinCC Client Windows XP WinCC Client Windows 7 WinCC Server Win Server 2008 WinCC Client Windows XP WinCC Client Windows XP WinCC Client Windows 7 CPU in % 73% 29% 19% 13% 10% 41% 12% 17% 14% 19% 30% 13% 15% 19% 32% 10% 14% 13% 20% 31% 19% 15% 11% 32% 10% 14% 13% Max. CPU in % 100% 48% 35% 32% 16% 80% 51% 36% 59% 28% 43% 22% 38% 32% 54% 16% 41% 26% 29% 39% 33% 34% 35% 54% 16% 41% 26% Active RAM 2 GB (max. 2.8 GB) 620 MB (max. 1 GB) 430 MB (max. 525 MB) 565 MB (max. 675 MB) 320 MB (max. 525 MB) 1.9 GB 510 MB 510 MB 950 MB 2.3 GB (max. 2.7 GB) 1.2 GB (max. 1.6 GB) 215 MB (max. 315 MB) 215 MB (max. 305 MB) 670 MB (max. 880 MB) 1.5 GB 460 MB 460 MB 890 MB 1.5 GB (max. 2 GB) 455 MB (max. 720 MB) 220 MB (max. 325 MB) 225 MB (max. 400 MB) 545 MB (max. 880 MB) 1.1 GB 460 MB 460 MB 870 MB
ICP 647C: EXSi (2)

HP Blade: ESXi (1) HP Blade: ESXi (2)
Guest
Host
Guest
Host
Guest
Host
34
PC Host/ Guest Computer ESXi WinCC Server Win Server 2008 WinCC Client Windows XP WinCC Client Windows XP Host Fujitsu Primergy: ESXi (1) WinCC Client Windows 7 WinCC Server Win Server 2008 WinCC Client Windows XP Guest WinCC Client Windows XP WinCC Client Windows 7 ESXi WinCC Server Win Server 2008 WinCC Client Windows XP WinCC Client Windows XP Host Fujitsu Primergy: ESXi (2) WinCC Client Windows 7 WinCC Server Win Server 2008 WinCC Client Windows XP Guest WinCC Client Windows XP WinCC Client Windows 7 CPU in % 11% 24% 11% 14% 12% 17% 7% 8% 7% 12% 30% 18% 14% 9% 20% 11% 9% 4% Max. CPU in % 19% 34% 16% 43% 29% 29% 10% 24% 14% 19% 38% 41% 39% 11% 29% 21% 20% 6% Active RAM 1.8 GB (max. 2.3 GB) 1.2 GB (max. 1.6 GB) 150 MB (max. 230 MB) 180 MB (max. 315 MB) 330 MB (max. 590 MB) 1.5 GB 460 MB 480 MB 910 MB 1.3 GB (max. 2 GB) 490 MB (max. 690 MB) 205 MB (max. 350 MB) 205 MB (max. 295 MB) 305 MB (max. 465 MB) 1.2 GB 470 MB 485 MB 900 MB
Conclusion for SIMATIC IPC 647C This configuration puts considerable load on the IPC 647C, the user must expect long delays when updating pictures. This also applies to updating the TagLogging and AlarmLogging controls. When reading data from the archive (selection of TagLogging picture) the CPU load of the ESXi server goes to 100% depending on the data volume.
ATTENTION
Operation in this constellation is not recommended.
35
5 Test Scenarios and Basic Performance Data 5.5 WinCC Server on ESXi (1) and four WinCC Clients on ESXi (2)
5.5
5.5.1
Overview
WinCC Server on ESXi (1) and four WinCC Clients on ESXi (2)
WinCC Server on ESXi (1) and four WinCC Standard Clients on ESXi (2)
The figure below shows a schematic illustration of the virtual components of this solution. The test platforms are: SIMATIC IPC 647C HP Blade Server
Figure 5-7
WinCC Server
WinCC Client Win 7
WinCC Client Win 7
WinCC Client Win XP
WinCC Client Win XP
Win 2008 Server
WinCC Client Win 7
WinCC Client Win 7
WinCC Client Win XP
WinCC Client Win XP
ESXi (1)
ESXi (2)
HP Blade Server
Description No operation occurs at the server. The clients are standard clients.
36
5 Test Scenarios and Basic Performance Data 5.5 WinCC Server on ESXi (1) and four WinCC Clients on ESXi (2) Basic performance data
PC Host/ Guest Computer ESXi (1) Host WinCC Server Win Server 2008 WinCC Server Win Server 2008 EXSi (2) WinCC Client Windows 7 WinCC Client Windows 7 WinCC Client Windows XP Host
CPU in % 33% 33%
Max. CPU in % 55% 54%
Active RAM 1.2 GB (max. 1.75 GB) 1.1 GB (max. 1.7 GB) 1.9 GB
IPC 647C: ESXi (1)
Guest
31%
45%
60% 11% 14% 20% 13% 10% 14% 20% 15% 8% 27%
80% 13% 28% 34% 35% 14% 40% 31% 31% 16% 52%
1.6 GB (max. 1.9 GB) 440 MB (max. 570 MB) 400 MB (max. 545 MB) 215 MB (max. 295 MB) 485 MB (max. 590 MB) 915 MB 955 MB 485 MB 490 MB 1.5 GB (max. 2 GB) 1.1 GB (max. 1.5 GB) 1.8 GB
WinCC Client Windows XP WinCC Client Windows 7 WinCC Client Windows 7
IPC 647C: EXSi (2)
Guest
WinCC Client Windows XP WinCC Client Windows XP ESXi
HP Blade: ESXi (1)
Host
WinCC Server Win Server 2008 WinCC Server Win Server 2008 ESXi WinCC Client Windows 7 WinCC Client Windows 7
Guest
29%
62%
15% 11% 14% 18% 14% 9% 14%
26% 14% 27% 32% 24% 14% 21%
1 GB (max. 1.4 GB) 320 MB (max. 482 MB) 320 MB (max. 440 MB) 203 MB (max. 294 MB) 200 MB (max. 252 MB) 1 GB 1 GB
HP Blade: ESXi (2)
WinCC Client Windows XP Host WinCC Client Windows XP WinCC Client Windows 7 WinCC Client Windows 7
Guest
37
PC Host/ Guest Computer WinCC Client Windows XP WinCC Client Windows XP CPU in % 20% 15% Max. CPU in % 38% 31% Active RAM 560 MB 560 MB
38
5.5.2
Overview
WinCC Server on ESXi (1) and four WinCC Multi Clients on ESXi (2)
Figure 5-8

WinCC Client Win 7
WinCC Client Win 7
WinCC Client Win XP
WinCC Client Win XP
WinCC Client Win XP
WinCC Client Win XP
WinCC Client Win 7
WinCC Client Win 7
ESXi (1)
ESXi (2)
HP Blade Server
Description No operation occurs at the server. The clients are multi clients.
39
PC Host/ Guest Computer ESXi (1) Host WinCC Server Win Server 2008 WinCC Server Win Server 2008 EXSi (2) WinCC Client Windows 7 WinCC Client Windows 7 WinCC Client Windows XP Host
CPU in % 37% 37%
Max. CPU in % 55% 54%
IPC 647C: ESXi (1)
Guest
30%
44%
69% 15% 10% 16% 18% 10% 15% 20% 16% 8% 28%
89% 30% 27% 35% 33% 30% 30% 28% 38% 17% 43%
1.8 GB (max. 2.2 GB) 460 MB (max. 650 MB) 485 MB (max. 675 MB) 390 MB (max. 475 MB) 410 MB (max. 570 MB) 975 MB 990 MB 565 MB 550 MB 1.5 GB (max. 2 GB) 1.1 GB (max. 1.6 GB) 1.6 GB
WinCC Client Windows XP WinCC Client Windows 7 WinCC Client Windows 7
IPC 647C: EXSi (2)
Guest
WinCC Client Windows XP WinCC Client Windows XP ESXi
HP Blade: ESXi (1)
Host
WinCC Server Win Server 2008 WinCC Server Win Server 2008 ESXi WinCC Client Windows 7 WinCC Client Windows 7
Guest
28%
50%
15% 11% 14% 18% 13% 8% 14%
23% 14% 27% 24% 37% 14% 27%
1 GB (max. 1.3 GB) 330 MB (max. 505 MB) 340 MB (max. 505 MB) 205 MB (max. 295 MB) 185 MB (max. 275 MB) 1 GB 1 GB
HP Blade: ESXi (2)
WinCC Client Windows XP Host WinCC Client Windows XP WinCC Client Windows 7 WinCC Client Windows 7
Guest
40
Conclusion As apparent in the following measurements in chapters 2.4.5.3 to 2.4.5.8 standard clients require more active RAM than multi clients.
41
5.5.3
Overview
WinCC Server and four WinCC Standard Clients
The figure below shows a schematic illustration of the virtual components of this solution. The test platforms are: HP Blade Server Fujitsu Primergy Server
Figure 5-9

WinCC Client Win 7
WinCC Client Win 7
WinCC Client
WinCC Client
Win XP Win XP
ESXi
HP Blade Server
WinCC Client Win 7
WinCC Client Win 7
WinCC Client
WinCC Client
Win XP Win XP
ESXi
Fujitsu Primergy
Description No operation occurs at the server. The clients are standard clients with operation.
42
PC Host/ Guest Computer ESXi WinCC Server Win Server 2008 WinCC Client Windows 7 WinCC Client Windows 7 WinCC Client Windows XP Host WinCC Client Windows XP WinCC Server Win Server 2008 WinCC Client Windows 7
CPU in % 24% 30% 14% 13% 18% 17% 32% 11% 13% 19% 16% 13% 25% 8% 12% 18% 14% 17% 4% 8% 13% 8%
Max. CPU in % 39% 44% 26% 27% 34% 36% 55% 15% 27% 37% 38% 22% 44% 11% 39% 34% 39% 32% 6% 33% 23% 26%
Active RAM 2.9 GB (max. 3.4 GB) 1.3 GB (max. 1.6 GB) 685 MB (max. 880 MB) 470 MB (max. 610 MB) 185 MB (max. 350 MB) 205 MB (max. 360 MB) 1.6 GB 900 MB 880 MB 470 MB 470 MB 2.2 GB (max. 2.6 GB) 1.1 GB (max. 1.4 GB) 240 MB (max. 380 MB) 375 MB (max. 715 MB) 200 MB (max. 305 MB) 190 MB (max. 325 MB) 1.4 GB 910 MB 900 MB 475 MB 485 MB
WinCC Client Windows 7 HP Blade Guest WinCC Client Windows XP WinCC Client Windows XP ESXi WinCC Server Win Server 2008 WinCC Client Windows 7 WinCC Client Windows 7 WinCC Client Windows XP Host WinCC Client Windows XP WinCC Server Win Server 2008 WinCC Client Windows 7 Fujitsu Primergy WinCC Client Windows 7 Guest WinCC Client Windows XP WinCC Client Windows XP
43
5.5.4
Overview
WinCC Server and four WinCC Multi Clients on one ESXi
The figure below shows a schematic illustration of the virtual components of this solution. The test platforms are: HP Blade Server Fujitsu Primergy Server
Figure 5-10

WinCC Client
WinCC Client
WinCC Client Win 7
WinCC Client Win 7
Win XP Win XP
ESXi
HP Blade Server
WinCC Client
WinCC Client
WinCC Client Win 7
WinCC Client Win 7
Win XP Win XP
ESXi
Fujitsu Primergy
Description No operation occurs at the server. The clients are multi clients with operation.
44
PC Host/ Guest Computer ESXi WinCC Server Win Server 2008 WinCC Client Windows 7 WinCC Client Windows 7 WinCC Client Windows XP Host WinCC Client Windows XP WinCC Server Win Server 2008 WinCC Client Windows 7
CPU in % 22% 29% 10% 13% 18% 16% 31% 8% 13% 18% 16% 13% 25% 9% 12% 17% 14% 18% 4% 6% 12% 8%
Max. CPU in % 40% 46% 80% 30% 32% 35% 67% 68% 23% 32% 35% 22% 40% 12% 22% 35% 40% 36% 7% 10% 21% 23%
Active RAM 2.4 GB (max. 2.8 GB) 1.1 GB (max. 1.5 GB) 430 MB (max. 695 MB) 365 MB (max. 570 MB) 225 MB (max. 325 MB) 210 MB (max. 315 MB) 1.7 GB 1 GB 1 GB 580 MB 590 MB 2.3 GB (max. 2.8 GB) 1.2 GB (max. 1.5 GB) 330 MB (max. 550 MB) 320 MB (max. 485 MB) 230 MB (max. 305 MB) 205 MB (max. 285 MB) 1.6 GB 1 GB 1 GB 590 MB 580 MB
WinCC Client Windows 7 HP Blade Guest WinCC Client Windows XP WinCC Client Windows XP ESXi WinCC Server Win Server 2008 WinCC Client Windows 7 WinCC Client Windows 7 WinCC Client Windows XP Host WinCC Client Windows XP WinCC Server Win Server 2008 WinCC Client Windows 7 Fujitsu Primergy WinCC Client Windows 7 Guest WinCC Client Windows XP WinCC Client Windows XP
45
5.5.5
Overview
WinCC Server on ESXi (1) and five WinCC Standard Clients on ESXi (2)
Figure 5-11

WinCC Client Win 7
WinCC Client Win 7
WinCC Client Win XP
WinCC Client Win XP
WinCC Client Win XP
WinCC Client Win 7
WinCC Client Win 7
WinCC Client Win XP
WinCC Client Win XP
WinCC Client Win XP
ESXi (1)
ESXi (2)
HP Blade Server
Description Test scenarios 2.4.5.1 and 2.4.5.2 illustrate the effects of the picture change to the CPU load of the WinCC server. An additional Windows XP client is added for these tests. The additional client with its picture changes produces a higher load at the server. No operation occurs at the server. The clients are standard clients.
46
PC IPC 647C: ESXi (1) Host/ Guest Computer ESXi (1) Host WinCC Server Win Server 2008 WinCC Server Win Server 2008 EXSi (2) WinCC Client Windows 7 WinCC Client Windows 7 WinCC Client Windows XP WinCC Client Windows XP
CPU in % 39% 38% 37%
Max. CPU in % 57% 56% 46%
Guest
81% 15% 14% 17% 16% 18% 15% 14% 22% 22% 20% 9% 32%
100% 26% 23% 30% 31% 32% 43% 57% 42% 53% 47% 17% 53%
2 GB (max. 2.4 GB) 520 MB (max. 665 MB) 425 MB (max. 630 MB) 200 MB (max. 305 MB) 470 MB (max. 580 MB) 325 MB (max. 430 MB) 940 MB 960 MB 485 MB 495 MB 450 MB 1.8 GB (max. 2.2 GB) 1.4 GB (max. 1.8 GB) 1.8 GB
Host
WinCC Client Windows XP WinCC Client Windows 7
IPC 647C: EXSi (2)
WinCC Client Windows 7 WinCC Client Windows XP Guest WinCC Client Windows XP WinCC Client Windows XP ESXi Host WinCC Server Win Server 2008 WinCC Server Win Server 2008 ESXi WinCC Client Windows 7
HP Blade: ESXi (1)
Guest
33%
61%
22% 14% 14% 19% 17% 19%
31% 28% 30% 35% 31% 35%
1.4 GB (max. 1.9 GB) 355 MB (max. 485 MB) 320 MB (max. 505 MB) 215 MB (max. 305 MB) 210 MB (max. 275 MB) 215 MB (max. 545 MB)
HP Blade: ESXi (2)
WinCC Client Windows 7 WinCC Client Windows XP WinCC Client Windows XP Host WinCC Client Windows XP
47
PC Host/ Guest Computer WinCC Client Windows 7 WinCC Client Windows 7 WinCC Client Windows XP Guest WinCC Client Windows XP WinCC Client Windows XP CPU in % 33% 14% 14% 21% 20% Max. CPU in % 61% 27% 28% 35% 35% Active RAM 1.8 GB 1 GB 1 GB 570 MB 560 MB
48
5.5.6
Overview
WinCC Server on ESXi (1) and five WinCC Standard Clients on ESXi (2)
Figure 5-12

WinCC Client Win 7
WinCC Client Win 7
WinCC Client Win XP
WinCC Client Win XP
WinCC Client Win XP
WinCC Client Win 7
WinCC Client Win 7
WinCC Client Win XP
WinCC Client Win XP
WinCC Client Win XP
ESXi (1)
ESXi (2)
HP Blade Server
Description No operation occurs at the server. The clients are standard clients, a picture change occurs every 20 seconds.
49
PC Host/ Guest Computer ESXi (1) Host WinCC Server Win Server 2008 WinCC Server Win Server 2008 EXSi (2) WinCC Client Windows 7 WinCC Client Windows 7 WinCC Client Windows XP
CPU in % 31% 30%
Max. CPU in % 55% 54%
Active RAM 1 GB (max. 1.7 GB) 950 MB (max. 1.6 GB) 1.9 GB
IPC 647C: ESXi (1)
Guest
35%
45%
59% 11% 9% 13% 11% 14% 10% 11% 14% 12% 13% 8% 28%
88% 31% 31% 38% 33% 26% 25% 45% 29% 21% 19% 16% 48%
1.9 GB (max. 2.5 GB) 470 MB (max. 650 MB) 370 MB (max. 545 MB) 310 MB (max. 485 MB) 445 MB (max. 570 MB) 215 MB (max. 370 MB) 940 MB 955 MB 490 MB 490 MB 455 MB 1.5 GB (max. 1.9 GB) 1.1 GB (max. 1.4 GB) 1.8 GB
WinCC Client Windows XP Host WinCC Client Windows XP WinCC Client Windows 7 IPC 647C: EXSi (2) WinCC Client Windows 7 WinCC Client Windows XP Guest WinCC Client Windows XP WinCC Client Windows XP ESXi Host WinCC Server Win Server 2008 WinCC Server Win Server 2008 ESXi WinCC Client Windows 7 WinCC Client Windows 7 WinCC Client Windows XP Host WinCC Client Windows XP
HP Blade: ESXi (1)
Guest
30%
76%
17% 10% 12% 14% 12%
38% 47% 99% 45% 45%
1.4 GB (max. 2.2 GB) 320 MB (max. 400 MB) 440 MB (max. 1GB) 195 MB (max. 325 MB) 230 MB (max. 370 MB)
HP Blade: ESXi (2)
50
PC Host/ Guest Computer WinCC Client Windows XP WinCC Client Windows 7 WinCC Client Windows 7 WinCC Client Windows XP Guest WinCC Client Windows XP WinCC Client Windows XP CPU in % 15% 9% 10% 14% 13% 12% Max. CPU in % 46% 48% 65% 42% 50% 45% Active RAM 185 MB (max. 275 MB) 1 GB 1 GB 570 MB 560 MB 500 MB
Conclusion Strong CPU load of the WinCC server for fast, continued picture changes.
Increasing the CPU load at WinCC/Server and the active work memory when selecting pictures with TagLogging and AlarmLogging controls for which values need to be read from the archive. Increasing CPU load also causes increased storage demand.
51
5.5.7
Overview
WinCC Server and six WinCC Standard Clients on one ESXi
The figure below shows a schematic illustration of the virtual components of this solution. The HP Blade server is used as the test platform.
Figure 5-13
WinCC Client Win 7
WinCC Client Win 7
WinCC Client Win 7
WinCC Client Win XP
WinCC Client Win XP
WinCC Client Win XP
ESXi
HP Blade Server
WinCC Client Win 7
WinCC Client Win 7
WinCC Client Win 7
WinCC Client Win XP
WinCC Client Win XP
WinCC Client Win XP
ESXi
Fujitsu Primergy
Description No operation occurs at the server. The clients are standard clients with operation. Basic performance data
PC Host/ Guest Computer ESXi WinCC Server Win Server 2008 Host WinCC Client Windows 7 CPU in % 30% 31% Max. CPU in % 39% 43% Active RAM 3.5 GB (max. 4.3 GB) 1.3 GB (max. 1.6 GB) 690 MB (max. 880 MB)
HP Blade
14%
28%
52
PC Host/ Guest Computer WinCC Client Windows 7 WinCC Client Windows 7 WinCC Client Windows XP WinCC Client Windows XP WinCC Client Windows XP WinCC Server Win Server 2008 WinCC Client Windows 7 WinCC Client Windows 7 WinCC Client Windows 7
CPU in % 11% 12% 17% 15% 13% 34% 13% 12% 9% 20% 17% 13% 19% 27% 12% 10% 11% 17% 18% 12% 18% 7% 5% 3% 13%
Max. CPU in % 36% 34% 33% 31% 17% 61% 25% 52% 43% 37% 39% 19% 28% 40% 27% 24% 18% 38% 35% 18% 33% 13% 17% 8% 23%
Active RAM 370 MB (max. 545 MB) 410 MB (max. 610 MB) 190 MB (max. 260 MB) 200 MB (max. 260 MB) 180 MB (max. 325 MB) 1.5 GB 900 MB 900 MB 880 MB 470 MB 470 MB 470 MB 2.8 GB (max. 3.4 GB) 1.3 GB (max. 1.6 GB) 315 MB (max. 465 MB) 300 MB (max. 485 MB) 330 MB (max. 610 MB) 205 MB (max. 305 MB) 195 MB (max. 275 MB) 165 MB (max. 255 MB) 1.4 GB 930 MB 900 MB 880 MB 480 MB
WinCC Client Windows XP Guest WinCC Client Windows XP WinCC Client Windows XP ESXi WinCC Server Win Server 2008 WinCC Client Windows 7 WinCC Client Windows 7 WinCC Client Windows 7 WinCC Client Windows XP WinCC Client Windows XP Host WinCC Client Windows XP WinCC Server Win Server 2008 WinCC Client Windows 7 Fujitsu Primergy WinCC Client Windows 7 Guest WinCC Client Windows 7 WinCC Client Windows XP
53
54
5.5.8
Overview
WinCC Server and six WinCC Multi Clients on one ESXi
Figure 5-14
WinCC Client Win 7
WinCC Client Win 7
WinCC Client Win 7
WinCC Client Win XP
WinCC Client Win XP
WinCC Client Win XP
ESXi
HP Blade Server
WinCC Client Win 7
WinCC Client Win 7
WinCC Client Win 7
WinCC Client Win XP
WinCC Client Win XP
WinCC Client Win XP
ESXi
Fujitsu Primergy
Description No operation occurs at the server. The clients are standard clients with operation. Basic performance data
PC Host/ Guest Computer ESXi HP Blade WinCC Server Win Server 2008 Host WinCC Client Windows 7 CPU in % 28% 29% 14% Max. CPU in % 36% 48% 29% Active RAM 3 GB (max. 3.6 GB) 1.3 GB (max. 1.9 GB) 490 MB (max. 690 MB)
55
PC Host/ Guest Computer WinCC Client Windows 7 WinCC Client Windows 7 WinCC Client Windows XP WinCC Client Windows XP WinCC Client Windows XP WinCC Server Win Server 2008 WinCC Client Windows 7 WinCC Client Windows 7 WinCC Client Windows 7
CPU in % 10% 11% 17% 15% 13% 32% 13% 10% 9% 19% 14% 13% 18% 27% 12% 10% 12% 17% 18% 13% 19% 8% 5% 4% 12%
Max. CPU in % 30% 40% 23% 36% 39% 68% 25% 33% 40% 34% 38% 38% 28% 41% 25% 29% 40% 35% 41% 55% 38% 13% 17% 24% 21%
Active RAM 315 MB (max. 440 MB) 295 MB (max. 480 MB) 220 MB (max. 315 MB) 210 MB (max. 315 MB) 205 MB (max. 265 MB) 1.7 GB 1 GB 1 GB 1 GB 580 MB 580 MB 565 MB 2.9 GB (max. 3.5 GB) 1.3 GB (max. 1.5 GB) 360 MB (max. 525 MB) 325 MB (max. 505 MB) 310 MB (max. 485 MB) 210 MB (max. 305 MB) 230 MB (max. 380 MB) 215 MB (max. 305 MB) 1.6 GB 1 GB 1 GB 1 GB 590 MB
WinCC Client Windows XP Guest WinCC Client Windows XP WinCC Client Windows XP ESXi WinCC Server Win Server 2008 WinCC Client Windows 7 WinCC Client Windows 7 WinCC Client Windows 7 WinCC Client Windows XP WinCC Client Windows XP Host WinCC Client Windows XP WinCC Server Win Server 2008 WinCC Client Windows 7 Fujitsu Primergy WinCC Client Windows 7 Guest WinCC Client Windows 7 WinCC Client Windows XP
56
57
5 Test Scenarios and Basic Performance Data 5.6 Using redundant server on one or two ESXi servers
5.6
5.6.1
Using redundant server on one or two ESXi servers

Effects of the redundancy switch-over on the CPU load
The graphics below display the CPU load curves during redundancy switch-over and recurring of the partner server. You can use these times for orientation.
Table 5-4 Time 8:50 8:50 8:55 8:56 to 8:57 9:00 9:04 Event Server 2 (the master at this point in time) is deactivated Server 1 becomes the master Server 2 is activated On both servers the new archives are created Beginning of the archive synchronization End of the archive synchronization
58
5 Test Scenarios and Basic Performance Data 5.6 Using redundant server on one or two ESXi servers CPU load curve server 1 (new master)
Figure 5-15
CPU load curve server 2 (old master, new standby)

Figure 5-16
59
5 Test Scenarios and Basic Performance Data 5.6 Using redundant server on one or two ESXi servers CPU load curve of the ESXi server
Figure 5-17
Conclusion While server 2 was deactivated, the CPU load increased at the master server. An increased CPU load occurred during startup of the standby server and during the archive synchronization (with the master server).
60
5.6.2
Overview
Two redundant servers as stand-alone stations on an ESXi server
Figure 5-18
Redundancy connection WinCC Server (M) Win 2008 Server
WinCC Server (S) Win 2008 Server
ESXi SIMATIC IPC 647C
Redundancy connection WinCC Server (M) Win 2008 Server WinCC Server (S) Win 2008 Server
ESXi (1)
HP Blade Server
Description The failure scenarios described in the following tests come from the WinCC Online documentation and can be read up there in detail. https://www.automation.siemens.com/mdm/default.aspx?DocVersionId=16484401 291&TopicId=12262626827
Table 5-5 No. 1. Failure scenarios Project on server computer not in runtime Function Yes Remark
61
No. 2. 3. 4. 5. Failure scenarios Connection fault to partner server Faulty network connection to client Faulty process connection Software error Function No No No Yes Remark No test since a virtual terminal bus is used virtually. No test since stand-alone. No function since both servers loose the connection.

Table 5-6 PC Host/ Guest Computer ESXi IPC 647C: ESXi before change WinCC Server Win Server 2008 (Master) WinCC Server Win Server 2008 (Standby) WinCC Server Win Server 2008 (Master) WinCC Server Win Server 2008 (Standby) ESXi IPC 647C: EXSi (after change) 4 WinCC Server Win Server 2008 (Master) WinCC Server Win Server 2008 (Standby) WinCC Server Win Server 2008 (Master) WinCC Server Win Server 2008 (Standby) ESXi WinCC Server Win Server 2008 (Standby) WinCC Server Win Server 2008 (Master) Guest Host
4 5
CPU in % 66% 34%
Max. CPU in % 98% 48%
Active RAM 1 GB (max. 1.5 GB) 490 MB (max. 690 MB) 475 MB (max. 725 MB) 1 GB
Host
32%
49%
45%
71%
Guest
37%
46%
1.2 GB
69% 33%
95% 59%
1 GB (max. 1.6 GB) 515 MB (max. 1 GB) 515 MB (max. 690 MB) 1.2 GB
35%
50%
41%
53%
41%
54%
1.2 GB
HP Blade: ESXi bef. change Host
18% 33%
26% 53%
1.2 GB (max. 1.5 GB) 600 MB (max. 1 GB) 570 MB (max. 1 GB)
35%
59%
62
PC Host/ Guest Computer WinCC Server Win Server 2008 (Standby) WinCC Server Win Server 2008 (Master) ESXi WinCC Server Win Server 2008 (Standby) WinCC Server Win Server 2008 (Master) WinCC Server Win Server 2008 (Standby) WinCC Server Win Server 2008 (Master) Guest Host
Guest
CPU in % 37%
Max. CPU in % 50%
Active RAM 1.5 GB
42%
54%
1.5 GB
18% 33%
26% 53%
1.2 GB (max. 1.5 GB) 600 MB (max. 1 GB) 570 MB (max. 1 GB) 1.5 GB
HP Blade: ESXi after change
35%
59%
38%
51%
39%
51%
1.5 GB
63
5.6.3
Overview
Two redundant server without operation as stand-alone stations on ESXi (1) with four WinCC Multi Clients on ESXi (2)
Figure 5-19
WinCC Client Win 7
WinCC Client Win 7
WinCC Client Win XP
WinCC Client Win XP
Redundancy connection WinCC Server (M) Win 2008 Server WinCC Server (S) Win 2008 Server WinCC Client Win 7 WinCC Client Win 7 WinCC Client Win XP WinCC Client Win XP
ESXi (1)
ESXi (2)
HP Blade Server
Description An operator action does not occur on the server. The clients are multi clients. Each client has a preferred server, so that two clients connect with one server. Every 10 seconds an operating action occurs at the client. The failure scenarios described in the following tests come from the WinCC Online documentation and can be read up there in detail. https://www.automation.siemens.com/mdm/default.aspx?DocVersionId=16484401 291&TopicId=12262626827
64
Table 5-7 No. 1. 2. 3. 4. 5. Failure scenarios Project on server computer not in runtime Connection fault to partner server Faulty network connection to client Faulty process connection Software error Function Yes No No No Yes No test since a virtual terminal bus is used virtually. No test since stand-alone. No function since both servers loose the connection. Remark
65
5 Test Scenarios and Basic Performance Data 5.6 Using redundant server on one or two ESXi servers Basic performance data
Table 5-8 PC Host/ Guest Computer ESXi (1) IPC 647C: ESXi (1) before change WinCC Server Win Server 2008 (Master) WinCC Server Win Server 2008 (Standby) WinCC Server Win Server 2008 (Master) WinCC Server Win Server 2008 (Standby) ESXi (2)
CPU in % 63% 33%
Max. CPU in % 82% 50%
Active RAM 1 GB (max. 1.7 GB) 555 MB (max. 975 MB) 475 MB (max. 850 MB) 1.4 GB
Host
29%
48%
40%
56%
Guest
34%
38%
1.4 GB
59% 13% 15% 15% 15% 11% 12% 18% 17% 62% 31%
90% 31% 36% 31% 29% 43% 41% 31% 31% 81% 50%
1.4 GB (max. 1.7 GB) 290 MB (max. 380 MB) 435 MB (max. 755 MB) 265 MB (max. 420 MB) 325 MB (max. 420 MB) 1 GB 1 GB 535 MB 535 MB 1 GB (max. 1.8 GB) 455 MB (max. 1 GB) 495 MB (max. 850 MB) 1.3 GB
WinCC Client Windows 7 WinCC Client Windows 7 IPC 647C: EXSi (2) before change WinCC Client Windows XP Host WinCC Client Windows XP WinCC Client Windows 7 WinCC Client Windows 7 Guest WinCC Client Windows XP WinCC Client Windows XP ESXi (1) IPC 647C: ESXi (1) after change5 WinCC Server Win Server 2008 (Standby) WinCC Server Win Server 2008 (Master) WinCC Server Win Server 2008 (Standby) WinCC Server Win Server 2008 (Master) Guest Host
30%
47%
35%
54%
37%
42%
1.3 GB
66
PC Host/ Guest Computer ESXi (2) WinCC Client Windows 7 WinCC Client Windows 7 IPC 647C: EXSi (2) (after change)6 WinCC Client Windows XP Host WinCC Client Windows XP WinCC Client Windows 7 WinCC Client Windows 7 Guest WinCC Client Windows XP WinCC Client Windows XP ESXi (1) HP Blade: ESXi (1) before change WinCC Server Win Server 2008 (Standby) WinCC Server Win Server 2008 (Master) WinCC Server Win Server 2008 (Standby) WinCC Server Win Server 2008 (Master) ESXi (2) WinCC Client Windows 7 WinCC Client Windows 7 HP Blade: ESXi (2) before change WinCC Client Windows XP Host WinCC Client Windows XP WinCC Client Windows 7 WinCC Client Windows 7 Guest WinCC Client Windows XP WinCC Client Windows XP Guest Host CPU in % 58% 13% 14% 15% 14% 10% 12% 18% 14% 17% 29% Max. CPU in % 96% 26% 35% 35% 40% 48% 34% 45% 32% 26% 52% Active RAM 1.5 GB (max. 1.8 GB) 425 MB (max. 545 MB) 430 MB (max. 610 MB) 230 MB (max. 350 MB) 360 MB (max. 555 MB) 1 GB 1 GB 545 MB 540 MB 1.5 GB (max. 2.3 GB) 570 MB (max. 1 GB) 560 MB (max. 1 GB) 1.4 GB
32%
56%
32%
50%
38%
50%
1.4 GB
14% 12% 12% 16% 13% 10% 11% 16% 15%
22% 34% 33% 38% 36% 33% 36% 41% 39%
1.2 GB (max. 1.5 GB) 320 MB (max. 465 MB) 425 MB (max. 590 MB) 215 MB (max. 295 MB) 215 MB (max. 295 MB) 1 GB 950 MB 560 MB 540 MB
67
PC Host/ Guest Computer ESXi (1) HP Blade: ESXi (1) after change 7 WinCC Server Win Server 2008 (Standby) WinCC Server Win Server 2008 (Master) WinCC Server Win Server 2008 (Standby) WinCC Server Win Server 2008 (Master) ESXi (2) WinCC Client Windows 7
CPU in % 16% 30%
Max. CPU in % 24% 52%
Active RAM 1.5 GB (max. 2.1 GB) 550 MB (max. 940 MB) 560 MB (max. 1.1 GB) 1.4 GB
Host
27%
53%
33%
51%
Guest
31%
47%
1.4 GB
14% 11% 12% 16% 13% 9% 11% 16% 13%
22% 35% 35% 32% 32% 23% 35% 32% 32%
1.1 GB (max. 1.4 GB) 320 MB (max. 505 MB) 375 MB (max. 525 MB) 210 MB (max. 325 MB) 200 MB (max. 295 MB) 1 GB 950 MB 560 MB 550 MB
WinCC Client Windows 7 HP Blade: ESXi (2) after change WinCC Client Windows XP Host WinCC Client Windows XP WinCC Client Windows 7 WinCC Client Windows 7 Guest WinCC Client Windows XP WinCC Client Windows XP
8
8 9
68
5.6.4
Overview
Two ESXi servers with one redundant server each and two WinCC clients
Figure 5-20
WinCC Client Win 7
WinCC Client Win XP
WinCC Client Win 7
WinCC Client Win XP
Redundancy connection WinCC Server (M) Win 2003 Server WinCC Client Win 7 WinCC Client Win XP WinCC Server (S) Win 2003 Server WinCC Client Win 7 WinCC Client Win XP
ESXi (1)
ESXi (2)
HP Blade Server
Description The failure scenarios described in the following tests come from the WinCC Online documentation and can be read up there in detail. https://www.automation.siemens.com/mdm/default.aspx?DocVersionId=16484401 291&TopicId=12262626827
69
Table 5-9 No. 1. 2. 3. Failure scenarios Project on server computer not in runtime Connection fault to partner server Faulty network connection to client Function Yes Yes No Function given. Client switch-over, see following scenario. No test, all clients run via one connection. Upon failure the clients want to switch over and become inoperable. Remark
4. 5.
Faulty process connection Software error
Yes Yes

Table 5-10 PC Host/ Guest Computer ESXi (1)
CPU in % 71% 39%
Max. CPU in % 97% 57%
Active RAM 1.5 GB (max. 2.1 GB) 600 MB (max. 940 MB) 516 MB (max. 713 MB) 380 MB (max. 524 MB) 1.4 GB
WinCC Server Win Server 2003 (Master) WinCC Client Windows 7 Host WinCC Client Windows XP WinCC Server Win Server 2003 (Master) Guest WinCC Client Windows 7 WinCC Client Windows XP ESXi (2) WinCC Server Win Server 2003 (Standby) WinCC Client Windows 7 Host WinCC Client Windows XP WinCC Server Win Server 2003 (Standby) Guest WinCC Client Windows 7 WinCC Client Windows XP
13% 18% 41%
38% 38% 70%
IPC 647C: ESXi (1)
15% 19% 71% 36%
38% 26% 92% 53%
1 GB 550 MB 1.4 GB (max. 2 GB) 590 MB (max. 1 GB) 430 MB (max. 610 MB) 300 MB (max. 470 MB) 1.4 GB
15% 19% 42%
36% 37% 67%
IPC 647C: EXSi (2)
15% 20%
56% 39%
1 GB 550 MB
70
PC Host/ Guest Computer ESXi (1) WinCC Server Win Server 2003 (Standby) WinCC Client Windows 7 Host WinCC Client Windows XP WinCC Server Win Server 2003 (Standby) Guest WinCC Client Windows 7 WinCC Client Windows XP ESXi (2)
CPU in % 17% 29%
Max. CPU in % 27% 48%
Active RAM 1.4 GB (max. 2.2 GB) 510 MB (max. 910 MB) 325 MB (max. 525 MB) 200 MB (max. 340 MB) 1.4 GB
15% 18% 39%
28% 34% 53%
HP Blade: ESXi (1)
13% 18% 16% 33%
23% 38% 26% 51%
1 GB 550 MB 1.6 GB (max. 2.2 GB) 562 MB (max. 1 GB) 750 MB (max. 925 MB) 210 MB (max. 315 MB) 1.4 GB
WinCC Server Win Server 2003 (Master) WinCC Client Windows 7 Host WinCC Client Windows XP WinCC Server Win Server 2003 (Master) Guest WinCC Client Windows 7 WinCC Client Windows XP
13% 16% 37%
31% 34% 53%
HP Blade (2)
13% 18%
25% 36%
935 MB 550 MB
71
5.6.5
Overview
Two redundant WinCC servers without operation with six WinCC multi clients on one ESXi server
The figure below shows a schematic illustration of the virtual components of this solution. The test platforms are: HP Blade Server Fujitsu Primergy
Figure 5-21
Redundancy connection WinCC Server (M) WinCC Server (S) WinCC Client Win 7 WinCC Client Win 7 WinCC Client Win 7 WinCC Client Win XP WinCC Client Win XP WinCC Client Win XP
Win 2003 Server

Win 2003 Server
ESXi
HP Blade Server
Redundancy connection WinCC Server (M) Win 2003 Server WinCC Server (S) Win 2003 Server WinCC Client Win 7 WinCC Client Win 7 WinCC Client Win 7 WinCC Client Win XP WinCC Client Win XP WinCC Client Win XP
ESXi Fujitsu Primergy

Table 5-11 PC Host/ Guest Computer ESXi WinCC Server Win Server 2003 (Master) WinCC Server Win Server 2003 (Standby) Host CPU in % 36% 29% Max. CPU in % 45% 55% Active RAM 2.7 GB (max. 3.4 GB) 660 MB (max. 1 GB) 510 MB (max. 1 GB)
HP Blade
30%
53%
72
PC Host/ Guest Computer WinCC Client Windows 7 WinCC Client Windows 7 WinCC Client Windows 7 WinCC Client Windows XP WinCC Client Windows XP WinCC Client Windows XP WinCC Server Win Server 2003 (Master) WinCC Server Win Server 2003 (Standby)
CPU in % 12% 10% 12% 14% 14% 16% 43%
Max. CPU in % 36% 30% 21% 35% 37% 38% 65%
Active RAM 335 MB (max. 465 MB) 330 MB (max. 525 MB) 305 MB (max. 440 MB) 215 MB (max. 295 MB) 215 MB (max. 350 MB) 210 MB (max. 275 MB) 1.4 GB
31%
46%
1.4 GB
WinCC Client Windows 7 WinCC Client Windows 7 WinCC Client Windows 7 WinCC Client Windows XP Guest WinCC Client Windows XP WinCC Client Windows XP ESXi WinCC Server Win Server 2003 (Master) WinCC Server Win Server 2003 (Standby) WinCC Client Windows 7 WinCC Client Windows 7 WinCC Client Windows 7 Fujitsu Primergy WinCC Client Windows XP WinCC Client Windows XP Host WinCC Client Windows XP
10% 10% 10% 15% 13% 15% 21% 29%
34% 15% 14% 36% 49% 35% 28% 40%
1 GB 1 GB 1 GB 600 MB 620 MB 580 MB 2.8 GB (max. 3.3 GB) 500 MB (max. 725 MB) 510 MB (max. 820 MB) 295 MB (max. 490 MB) 310 MB (max. 420 MB) 540 MB (max. 820 MB) 215 MB (max. 300 MB) 210 MB (max. 300 MB) 185 MB (max. 300 MB)
32%
42%
10% 8% 7% 14% 13% 11%
23% 38% 11% 42% 48% 15%
73
PC Host/ Guest Computer WinCC Server Win Server 2003 (Master) WinCC Server Win Server 2003 (Standby) WinCC Client Windows 7 WinCC Client Windows 7 WinCC Client Windows 7 WinCC Client Windows XP Guest WinCC Client Windows XP WinCC Client Windows XP CPU in % 20% Max. CPU in % 25% Active RAM 1.4 GB
23%
28%
1.4 GB
5% 4% 3% 9% 8% 6%
13% 18% 6% 27% 29% 9%
1 GB 1 GB 950 MB 560 MB 570 MB 550 MB
74
5.6.6
Overview
Two ESXi servers with one redundant server each and three WinCC clients each
Figure 5-22
Redundancy connection
WinCC Server (M) Win 2008 Server WinCC Client Win XP WinCC Client Win XP WinCC Client Win 7 WinCC Server (S) Win 2008 Server WinCC Client Win XP WinCC Client Win XP WinCC Client Win 7
ESXi (1)
ESXi (2)
Terminal bus HP Blade Server

Table 5-12 PC Host/ Guest Computer ESXi (1) WinCC Server Win Server 2003 (Standby) WinCC Client Windows XP WinCC Client Windows XP Host WinCC Client Windows 7 WinCC Server Win Server 2003 (Standby) WinCC Client Windows XP Guest WinCC Client Windows XP WinCC Client Windows 7 CPU in % 18% 29% Max. CPU in % 28% 47% Active RAM 1.6 GB (max. 2.5 GB) 515 MB (max. 1 GB) 215 MB (max. 325 MB) 190 MB (max. 340 MB) 320 MB (max. 610 MB) 1.4 GB
15% 13% 12% 34%
36% 23% 38% 50%
HP Blade: ESXi (1)
15% 14% 8%
42% 21% 36%
535 MB 535 MB 1 GB
75
PC Host/ Guest Computer ESXi (2) WinCC Server Win Server 2003 (Master) WinCC Client Windows XP WinCC Client Windows XP Host WinCC Client Windows 7 WinCC Server Win Server 2003 (Master) WinCC Client Windows XP Guest WinCC Client Windows XP WinCC Client Windows 7 CPU in % 19% 33% Max. CPU in % 28% 57% Active RAM 2 GB (max. 2.4 GB) 535 MB (max. 1 GB) 180 MB (max. 300 MB) 480 MB (max. 880 MB) 690 MB (max. 1 GB) 1.4 GB
16% 11% 11% 39%
38% 45% 31% 51%
HP Blade: ESXi (2)
14% 11% 8%
41% 51% 38%
545 MB 950 MB 920 MB
Description Startup of server and client guest systems at switched on High Available (HA). Via HA the load of the guest systems is distributed to the ESX servers of the clusters. After the startup both servers and the 6 WinCC clients are divided as follows. VMWare Option FT (Fault Tolerance) was not tested. On the clients, the picture changes occur as follows.
Table 5-13 PC ESXi (2) ESXi (1) ESXi (2) ESXi (1) ESXi (2) Client WinCC Client 1, Windows 7 WinCC Client 2, Windows XP WinCC Client 3, Windows 7 WinCC Client 4, Windows XP WinCC Client 5, Windows XP WinCC Client 6, Windows XP 10 10 15 20 15 20 Picture change, all [s]
76
Table 5-14 PC Host/ Guest Computer ESXi (1) WinCC Server Win Server 2003 (Master) WinCC Client 2 Windows XP Host WinCC Client 5 Windows 7 WinCC Server Win Server 2003 (Master) Guest WinCC Client 2 Windows 7 WinCC Client 5 Windows XP ESXi (2) WinCC Server Win Server 2003 (Standby) WinCC Client 1 Windows 7 WinCC Client 3 Windows 7 WinCC Client 4 Windows XP Host WinCC Client 6 Windows XP WinCC Server Win Server 2003 (Standby) HP Blade: ESXi (2) WinCC Client 1 Windows 7 WinCC Client 3 Windows 7 Guest WinCC Client 4 Windows XP WinCC Client 6 Windows XP CPU in % 15% 30% Max. CPU in % 27% 47% Active RAM 1.9 GB (max. 2 GB) 515 MB (max. 850 MB) 750 MB (max. 950 MB) 185 MB (max. 295 MB) 1.4 GB
11% 15% 34%
32% 20% 44%
HP Blade: ESXi (1)
10% 14% 21% 27%
16% 38% 20% 41%
960 MB 540 MB 2.1GB (max. 3.2 GB) 470 MB (max. 910 MB) 670 MB (max. 780 MB) 620 MB (max. 880 MB) 160 MB (max. 340 MB) 160 MB (max. 360 MB) 1.3 GB
11% 10% 14% 16% 33%
35% 38% 21% 24% 47%
9% 10% 11% 12%
18% 35% 36% 34%
980 MB 960 MB 540 MB 540 MB
77
5.6.7
Overview
Two redundant WinCC servers on ESXi (1) and one WinCC client with WinCC/Webnavigator, as well as 3 WinCC WebClients on ESXi (2)
Figure 5-23
Redundancy connection WinCC Server Win 2003 Server
Web Navigator WinCC Client Win XP WinCC WinCC WinCC WebClient WebClient WebClient Win 7 Win XP Win XP
WinCC Server red. Win 2003 Server
Redundancy connection WinCC Server Win 2003 Server WinCC Server red. Win 2003 Server
Web Navigator WinCC Client Win XP WinCC WinCC WinCC WebClient WebClient WebClient Win 7 Win XP Win XP
ESXi (1)
ESXi (2)
HP Blade Server
Description In this configuration no picture changes occur on the multi-client (web server). This must be taken into consideration for the subsequent values. Picture change on the web-clients after approx. 40 seconds.
78
Table 5-15 PC Host/ Guest Computer ESXi (1) WinCC Server Win Server 2003 (Standby) WinCC Server Win Server 2003 (Master) WinCC Server Win Server 2003 (Standby) WinCC Server Win Server 2003 (Master) ESXi (2)
CPU in % 62% 30%
Max. CPU in % 78% 39%
Active RAM 1 GB (max. 1.6 GB) 420 MB (max. 785 MB) 590 MB (max. 975 MB) 1.4 GB
IPC 647C: ESXi (1)
Host
31%
48%
30%
33%
Guest
37%
52%
1.4 GB
45% 8%
60% 10%
1.7 GB (max. 2 GB) 305 MB (max. 390 MB) 490 MB (max. 695 MB) 400 MB (max. 475 MB) 410 MB (max. 545 MB) 530 MB
WinCC Client and WebServer Windows XP WinCC Client Windows 7 WinCC Client Windows XP Host WinCC Client Windows XP WinCC Client and WebServer Windows XP WinCC Client Windows 7 Guest WinCC Client Windows XP WinCC Client Windows XP ESXi (1) IPC 647C: ESXi (1) (after change)9 WinCC Server Win Server 2003 (Master) WinCC Server Win Server 2003 (Standby) WinCC Server Win Server 2003 (Master) WinCC Server Win Server 2003 (Standby) Guest Host
11% 13% 11% 5%
23% 23% 22% 7%
IPC 647C: EXSi (2)
8% 15% 14% 65% 35%
27% 16% 19% 81% 51%
960 MB 380 MB 380 MB 1 GB (max. 1.6 GB) 590 MB (max. 975 MB) 430 MB (max. 880 MB) 1.4 GB
29%
39%
38%
47%
33%
35%
1.4 GB
79
PC Host/ Guest Computer ESXi (2) WinCC Client and WebServer Windows XP WinCC Client Windows 7 IPC 647C: EXSi (2) (after change)10 WinCC Client Windows XP Host WinCC Client Windows XP WinCC Client and WebServer Windows XP WinCC Client Windows 7 Guest WinCC Client Windows XP WinCC Client Windows XP ESXi (1) WinCC Server Win Server 2003 (Standby) WinCC Server Win Server 2003 (Master) WinCC Server Win Server 2003 (Standby) WinCC Server Win Server 2003 (Master) ESXi (2) WinCC Client and WebServer Windows XP WinCC Client Windows 7 WinCC Client Windows XP HP Blade: ESXi (2) Host WinCC Client Windows XP WinCC Client and WebServer Windows XP WinCC Client Windows 7 Guest Host CPU in % 47% 8% Max. CPU in % 89% 10% Active RAM 1.6 GB (max. 2 GB) 325 MB (max. 525 MB) 485 MB (max. 505 MB) 390 MB (max. 480 MB) 385 MB (max. 485 MB) 550 MB
12% 12% 11% 5%
22% 24% 21% 8%
8% 15% 14% 15% 31%
23% 18% 18% 23% 52%
950 MB 380 MB 380 MB 1.4 GB (max. 1.9 GB) 660 MB (max. 1 GB) 410 MB (max. 600 MB) 1.4 GB
26%
28%
HP Blade: ESXi (1)
34%
50%
29%
33%
1.4 GB
12% 9%
20% 11%
805 MB (max. 1 GB) 140 MB (max. 220 MB) 345 MB (max. 465 MB) 160 MB (max. 240 MB) 155 MB (max. 250 MB) 540 MB
9% 13% 14% 4%
18% 22% 25% 6%
Guest
7%
17%
820 MB
80
PC Host/ Guest Computer WinCC Client Windows XP WinCC Client Windows XP ESXi (1) HP Blade: ESXi (1) (after change) 11 WinCC Server Win Server 2003 (Standby) WinCC Server Win Server 2003 (Master) WinCC Server Win Server 2003 (Standby) WinCC Server Win Server 2003 (Master) ESXi (2)
CPU in % 13% 13% 15% 29%
Max. CPU in % 26% 25% 25% 51%
Active RAM 370 MB 370 MB 1.4 GB (max. 1.9 GB) 620 MB (max. 1 GB) 455 MB (max. 725 MB) 1.4 GB
Host
28%
30%
33%
49%
Guest
31%
36%
1.4 GB
12% 9%
20% 11%
820 MB (max. 1 GB) 145 MB (max. 220 MB) 340 MB (max. 485 MB) 160 MB (max. 240 MB) 150 MB (max. 265 MB) 540 MB
WinCC Client and WebServer Windows XP WinCC Client Windows 7 HP Blade: ESXi (2) after change 12 WinCC Client Windows XP Host WinCC Client Windows XP WinCC Client and WebServer Windows XP WinCC Client Windows 7 Guest WinCC Client Windows XP WinCC Client Windows XP
9% 13% 14% 3%
18% 23% 23% 6%
7% 13% 12%
16% 26% 25%
820 MB 370 MB 370 MB
81
5.6.8
Overview
Two redundant WinCC servers and one WinCC client with WinCC/Webnavigator, as well as 3 WinCC WebClients on one ESXi
The figure below shows a schematic illustration of the virtual components of this solution. The test platforms are: HP Blade Server Fujitsu Primergy
Figure 5-24
Redundancy connection WinCC Server Win 2003 Server
Web Navigator WinCC Client Win XP WinCC WinCC WinCC WebClient WebClient WebClient Win XP Win 7 Win 7
WinCC Server red. Win 2003 Server
ESXi
HP Blade Server
Redundancy connection WinCC Server Win 2003 Server WinCC Server red. Win 2003 Server
Web Navigator WinCC Client Win XP WinCC WinCC WinCC WebClient WebClient WebClient Win XP Win 7 Win 7
ESXi Fujitsu Primergy
Description The same test as in chapter 2.4.6.7, on the HP Blade server in only one ESXi. Basic performance data
Table 5-16 PC Host/ Guest Computer ESXi HP Blade WinCC Server Win Server 2003 (Standby) Host CPU in % 25% 28% Max. CPU in % 33% 48% Active RAM 2.3 GB (max. 3.3 GB) 575 MB (max. 1 GB)
82
PC Host/ Guest Computer WinCC Server Win Server 2003 (Master) WinCC Client and WebServer Windows XP WinCC Client Windows XP WinCC Client Windows 7 WinCC Client Windows 7 WinCC Server Win Server 2003 (Standby) WinCC Server Win Server 2008 (Master)
CPU in % 28%
Max. CPU in % 30%
Active RAM 395 MB (max. 505 MB) 170 MB (max. 325 MB) 155 MB (max. 235 MB) 495 MB (max. 695 MB) 500 MB (max. 800 MB) 1.4 GB
8%
26%
12% 10% 9% 36%
21% 19% 26% 52%
32%
33%
1.4 GB
WinCC Client and WebServer Windows XP WinCC Client Windows XP Guest WinCC Client Windows 7 WinCC Client Windows 7 ESXi WinCC Server Win Server 2003 (Standby) WinCC Server Win Server 2003 (Master) WinCC Client and WebServer Windows XP WinCC Client Windows XP WinCC Client Windows 7 Host Fujitsu Primergy WinCC Client Windows 7 WinCC Server Win Server 2003 (Standby) WinCC Server Win Server 2003 (Master) Guest
4%
30%
530 MB
13% 6% 9% 16% 27%
26% 15% 22% 23% 30%
365 MB 795 MB 820 MB 2.1 GB (max. 2.5 GB) 410 MB (max. 565 MB) 595 MB (max. 820 MB) 155 MB (max. 220 MB) 190 MB (max. 220 MB) 285 MB (max. 400 MB) 450 MB (max. 695 MB) 1.4 GB
32%
42%
7%
9%
13% 8% 9% 19%
21% 16% 17% 21%
22%
26%
1.4 GB
83
PC Host/ Guest Computer WinCC Client and WebServer Windows XP WinCC Client Windows XP WinCC Client Windows 7 WinCC Client Windows 7 CPU in % 2% Max. CPU in % 3% Active RAM 550 MB
8% 4% 4%
16% 11% 9%
480 MB 940 MB 720 MB
84
5.6.9
Overview
Using one (external) engineering station for downloading the projects
The figure below shows a schematic illustration of the most important components of this solution. The SIMATIC IPC 647C is used as the test platform.
Figure 5-25
Redundancy connection WinCC Server Win 2003 Server WinCC Client Win XP WinCC Server red. Win 2003 Server WinCC Client Win XP

Ethernet Engineering Station Win XP
Field PG
85
6 Diagnostic Capabilities 6.1 Diagnosis with VMware vSphere Client
6
6.1
Diagnostic Capabilities
Diagnosis with VMware vSphere Client
The vSphere client does not only enable configuring the virtual machines (guest systems) but also monitoring the ESXi server and the individual virtual machines (guest computers).
General information
Monitoring options Various curve displays are possible in the vSphere client:
Main memory load Operating state CPU load Hard disk Network load
Procedure in detail
Table 6-1 No. 1. Step/Action Logging on at the ESXi server Start your VMware VSphere client. The log-on dialog appears: Enter the IP address of your virtualization server and your user data. The vSphere client starts. Navigate to the ESXi server diagnostics In the navigation tree you select entry at the top. (The virtualization server) Then close the Performance tab. A diagram appears with the gradient of the performance data. Adjust the diagnostics of the ESXi server To monitor the values used at these measurements please proceed as follows: In the top most area you click on Trend settings. The Adjust performance trend dialog appears. Monitoring the work memory In the Trend settings tree you extend the RAM entry. In RAM you click on Realtime. In the Performance logs you unselect everything and then activate only active. Confirm with OK. In the diagram you can now monitor the active work memory. Monitor the CPU load In the Trend settings tree you extend the CPU entry. In CPU you click on Realtime. In the Performance logs you unselect everything and then activate only usage. Confirm with OK. In the diagram you can now monitor the CPU load.
2.
3.
86
6 Diagnostic Capabilities 6.1 Diagnosis with VMware vSphere Client

No. 4. Step/Action Navigate to the diagnosis of the virtual system In the navigation tree you select the entry of the virtual system to be monitored. Then close the Performance tab. A diagram appears with the gradient of the performance data. Adjusting the diagnostics of the virtual system To do this, proceed as in step 3.
5.
87
6 Diagnostic Capabilities 6.2 Diagnosis in the virtual system
6.2
Diagnosis in the virtual system

The Windows operating system provides a tool for diagnosis, the Windows Performance monitor
Procedure in detail
Table 6-2 No. 1. Step/Action Starting the tool Click on Start > Run.... The Run... dialog appears. Enter Perfmon and click on OK. The monitoring tool starts. Adjusting the performance logs Remove all performance logs in the bottom right area. Click right in this area. Select Add performance logs ... from the menu.
2.
The Add performance logs dialog appears. In order to display the CPU load as a percentage you select the Processor data object and select the performance indicator % Processor Time. Select _Total as the instance. Click on Add. To display the work memory assignment you select the Memory data object and select the Committed Bytes data object. Click on Add and close the dialog with Close.
Note It is a problem to display both values simultaneously in one diagram. The scaling of the axis differs. For an optimal display the scaling must be adjusted via the Properties button and the Graphics tab.
88
7 6BGlossary
7
ESXi
Glossary
This is a product by VMware. The software has/is an own operating system and provides virtual systems with work space. The software is used for virtualization on the server side.
Guest Refers to virtual system. Host Refers to virtualization server. Hyper Threading A technology for better processing of commands for the processor. One process core therefore appears as 2 process cores. Management Station
Refers to a PC which takes on the configuration, maintenance and monitoring of one or several virtualization servers. Applications VMware Converter or vSphere Client can be used here. Virtualization server (and virtual system) Refers to the real PC on which the VMware ESXi runs and who provides its resources to virtual systems. Computers which run within the VMware ESXi software are virtualized systems. Virtual hardware Real resources are not provided to the virtualized systems directly to enable joint usage. Such jointly used hardware can be network cards, process cores or hard disks. This can be proportionally and jointly by all virtualized systems. Virtual network A network which only exists within a virtualization server and enables a communication option with several virtual systems (within one virtualization server). Virtual processor core A processor core provided to the virtual machine. VMware A company and manufacturer for virtualization software. VMware vCenter Converter A product by VMware for converting, transferring and creating of virtual systems. VMware Workstation A product by VMware for creating and using virtual systems on already existing operating systems.
89
7 6BGlossary
vSphere Client A product by VMware for configuration, monitoring and operating a VMware ESXi servers.
90
8 7BLinks & Literature
8
8.1
Links & Literature

Literature
This list is by no means complete and only presents a selection of related references.
Table 8-1 Topic /1/ STEP7 Title Automatisieren mit STEP7 in AWL und SCL (Automating with STEP7 in STL and SCL) Hans Berger Publicis MCD Verlag ISBN 3-89578-113-4
8.2
Internet links
The following list is by no means complete and only provides a selection of related sources.
Table 8-2
Topic \1\ \2\ \3\ Reference to this document Siemens I IA/DT Customer Support Release for Server Virtualization WPF Controls for WinCC Configuration instruction for integrated working of WinCC in STEP 7.
Title
http://support.automation.siemens.com/WW/view/en/49368181 http://support.automation.siemens.com http://support.automation.siemens.com/WW/view/en/49370459
\4\ \5\
http://support.automation.siemens.com/WW/view/en/43101218 http://support.automation.siemens.com/WW/view/en/34995306
History
Table 9-1 Version V1.0 Date 04/2011 First issue Modification
91

WinCC Server Virtualization en PDF

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

WinCC Server Virtualization en PDF

Încărcat de

Drepturi de autor:

Formate disponibile

Cover

Applications & Tools

Copyright Siemens AG 2011 All rights reserved

WinCC/Server Virtualization V1.0, Entry ID: 49368181

SIMATIC WinCC/Server Virtualization

Copyright Siemens AG 2011 All rights reserved

Links & Literature History

WinCC/Server Virtualization V1.0, Entry ID: 49368181

Warranty and Liability

Warranty and Liability

Copyright Siemens AG 2011 All rights reserved

WinCC/Server Virtualization V1.0, Entry ID: 49368181

Copyright Siemens AG 2011 All rights reserved 49368181_WinCC_Server_virtualization_en.doc

WinCC/Server Virtualization V1.0, Entry ID: 49368181

Automation Solution ......................................................................................... 9

Procedure for the Virtualization ..................................................................... 14

Framework Conditions for the Measurements ............................................. 19 4.1 4.2 4.3

WinCC/Server Virtualization V1.0, Entry ID: 49368181

Diagnostic Capabilities ................................................................................... 86

Copyright Siemens AG 2011 All rights reserved

WinCC/Server Virtualization V1.0, Entry ID: 49368181

1 Automation Task 1.1 Overview

WinCC/Server Virtualization V1.0, Entry ID: 49368181

2 Automation Solution 2.1 What is virtualization?

Layout for virtualization

Copyright Siemens AG 2011 All rights reserved

A physical PC provides its hardware to several virtualized systems.

Memory Sound card

Virtualized Virtualisiertes System Virtualisiertes Virtualisiertes System 1 System 2 System 3 n

Applicat Applicat ion 1 ion n (e (e.g. M .o M S S.g W rd ) W ord)

Operating system (e.g. Windows) Virtualized Hardware

Operating System (e.g. Windows)

Application for Virtualization (=operating system)

Operation directly at the PC via graphics card and monitor.

WinCC/Server Virtualization V1.0, Entry ID: 49368181

2 Automation Solution 2.1 What is virtualization?

Advantages of the virtualization

WinCC/Server Virtualization V1.0, Entry ID: 49368181

2 Automation Solution 2.2 Requirements

SIMATIC Software and operating system

ESX server with WinCC guest systems

WinCC/Server Virtualization V1.0, Entry ID: 49368181

2 Automation Solution 2.2 Requirements

Modules Separation of networks

Hard disk storage management Operating states

WinCC/Server Virtualization V1.0, Entry ID: 49368181

3 Procedure for the Virtualization 3.1 Process and required software

Procedure for the Virtualization

Process and required software

Copyright Siemens AG 2011 All rights reserved

The VMware Workstation software is recommended for creating a virtual system.

WinCC/Server Virtualization V1.0, Entry ID: 49368181

3 Procedure for the Virtualization 3.2 Procedure in detail

WinCC/Server Virtualization V1.0, Entry ID: 49368181

3 Procedure for the Virtualization 3.2 Procedure in detail

Copyright Siemens AG 2011 All rights reserved

WinCC/Server Virtualization V1.0, Entry ID: 49368181

3 Procedure for the Virtualization 3.2 Procedure in detail

Copyright Siemens AG 2011 All rights reserved

WinCC/Server Virtualization V1.0, Entry ID: 49368181

3 Procedure for the Virtualization 3.2 Procedure in detail

WinCC/Server Virtualization V1.0, Entry ID: 49368181

4 Framework Conditions for the Measurements 4.1 Hardware used