Application & Tools - Siemens · PDF file5.2 WinCC Server and one WinCC Client ... – Windows XP or Windows 7 2.2.2 ESX server with WinCC guest systems

Applications & Tools

Answers for Industry.

Cover

WinCC/Server Virtualization

WinCC

Technical Information April 2011

2 WinCC/Server Virtualization

V1.0, Entry ID: 49368181

Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

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:

[email protected]

http://support.automation.siemens.com/WW/view/en/49368181�

mailto:[email protected]�

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

Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

s

SIMATIC WinCC/Server Virtualization

Automation Task

1

Automation Solution

2 Procedure for the Virtualization

3

Framework Conditions for the Measurements

4

Test Scenarios and Basic Performance Data

5

Diagnostic Capabilities

6

Glossary

7

Links & Literature

8

History

9

Warranty and Liability


V1.0, Entry ID: 49368181

Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

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


Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

49

368

181

_W

inC

C_S

erve

r_vi

rtu

aliz

atio

n_en

.do

c

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:

Display of typical configurations

Display of performance data in the various configurations

Monitoring the performance of all guest systems

Validity

This document is valid for WinCC/Server V7.0 SP2.

Table of Contents


V1.0, Entry ID: 49368181

Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

Table of Contents Warranty and Liability ................................................................................................. 4 Preface .......................................................................................................................... 5 1 Automation Task................................................................................................ 8

1.1 Overview .............................................................................................. 8 1.2 Virtualization requirements................................................................... 8

2 Automation Solution ......................................................................................... 9 2.1 What is virtualization? .......................................................................... 9 2.1.1 Definition .............................................................................................. 9 2.1.2 Advantages of the virtualization ......................................................... 11 2.2 Requirements ..................................................................................... 12 2.2.1 Required software .............................................................................. 12 2.2.2 ESX server with WinCC guest systems ............................................. 12 2.2.3 Guest systems.................................................................................... 13 2.2.4 Further information ............................................................................. 13

3 Procedure for the Virtualization ..................................................................... 14 3.1 Process and required software .......................................................... 14 3.2 Procedure in detail ............................................................................. 15

4 Framework Conditions for the Measurements ............................................. 19 4.1 Hardware used ................................................................................... 19 4.2 Configuration of the guest systems.................................................... 21 4.3 Used software .................................................................................... 23

5 Test Scenarios and Basic Performance Data ............................................... 25 5.1 WinCC standalone ............................................................................. 27 5.2 WinCC Server and one WinCC Client................................................ 28 5.3 WinCC Server and two WinCC Standard Clients .............................. 29 5.4 WinCC Server and three WinCC Standard Clients............................ 32 5.5 WinCC Server on ESXi (1) and four WinCC Clients on ESXi (2)....... 36 5.5.1 WinCC Server on ESXi (1) and four WinCC Standard Clients on ESXi

(2) ....................................................................................................... 36 5.5.2 WinCC Server on ESXi (1) and four WinCC Multi Clients on ESXi (2)39 5.5.3 WinCC Server and four WinCC Standard Clients.............................. 42 5.5.4 WinCC Server and four WinCC Multi Clients on one ESXi................ 44 5.5.5 WinCC Server on ESXi (1) and five WinCC Standard Clients on ESXi

(2) ....................................................................................................... 46 5.5.6 WinCC Server on ESXi (1) and five WinCC Standard Clients on ESXi

(2) ....................................................................................................... 49 5.5.7 WinCC Server and six WinCC Standard Clients on one ESXi........... 52 5.5.8 WinCC Server and six WinCC Multi Clients on one ESXi.................. 55 5.6 Using redundant server on one or two ESXi servers ......................... 58 5.6.1 Effects of the redundancy switch-over on the CPU load.................... 58 5.6.2 Two redundant servers as stand-alone stations on an ESXi server .. 61 5.6.3 Two redundant server without operation as stand-alone stations on

ESXi (1) with four WinCC Multi Clients on ESXi (2)........................... 64 5.6.4 Two ESXi servers with one redundant server each and two WinCC

clients ................................................................................................. 69 5.6.5 Two redundant WinCC servers without operation with six WinCC multi

clients on one ESXi server ................................................................. 72 5.6.6 Two ESXi servers with one redundant server each and three WinCC

clients each ........................................................................................ 75

Table of Contents


Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

5.6.7 Two redundant WinCC servers on ESXi (1) and one WinCC client with WinCC/Webnavigator, as well as 3 WinCC WebClients on ESXi (2) 78

5.6.8 Two redundant WinCC servers and one WinCC client with WinCC/Webnavigator, as well as 3 WinCC WebClients on one ESXi82

5.6.9 Using one (external) engineering station for downloading the projects85 6 Diagnostic Capabilities ................................................................................... 86

6.1 Diagnosis with VMware vSphere Client ............................................. 86 6.2 Diagnosis in the virtual system........................................................... 88

7 Glossary ........................................................................................................... 89 8 Links & Literature ............................................................................................ 91

8.1 Literature ............................................................................................ 91 8.2 Internet links ....................................................................................... 91

9 History............................................................................................................... 91

1 Automation Task

1.1 Overview


V1.0, Entry ID: 49368181

Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

1 Automation Task

1.1 Overview

Introduction

Virtualization of servers are already of high importance in information technology. In automation technology the advantages of virtualization shall also be reached.

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?


Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d



2.1.1 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 n

Netw

ork card

CP

Us

Mem

ory

Hard disks

Graphics card

Sound card

…

Netw

ork card

CP

Us

Mem

ory

Hard d

isks

Graphics card

Sound card

…

Physical PC

Virtualized System 1

Netw

ork card

CP

Us

Mem

ory

Hard disks

Graphics card

Sound card

…

PhysicalHardware

A physical PC provides its hardware to several virtualized systems.




V1.0, Entry ID: 49368181

Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

Differences between server-based and client-based virtualization

Figure 2-2

Client-based Virtualization Server-based Virtualization

Physical PC Physical PC

Hardware Hardware

Application for Virtualization (=operating system)Operating System (e.g. Windows)

Application for virtualization(z.B. VMware Workstation)

Application for virtualization(z.B. VMware Workstation)

Application for virtualization(e.g. VMware Workstation)Virtualized system

Virtualized Hardware

Operating system(e.g. Windows)

App. n(e.g.Word)

App. 1(e.g.Word)Application n(e.g. MS Word)

Application 1(e.g. MS Word)

Virtualisiertes System nVirtualisiertes System 3Virtualisiertes System 2Virtualized System 1

Virtualized Hardware

Operating system(e.g. Windows)

App. n(e.g.Word)

App. 1(e.g.Word)

Operation directly at the PC via graphics card and monitor.

No direct operation.Operation e.g. via one or several RDP clients.

RDP




Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

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.1

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:

– RDP2/VNC3-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 When using the respective virtualization hardware. 2 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.


2.2 Requirements


V1.0, Entry ID: 49368181

Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

2.2 Requirements

Note 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

ATTENTION The application/administration is required to supply and ensure sufficient system resources on the virtualization server and the virtual systems.

Table 2-1

Features Requirements

Number of CPU cores For the ESX server at least two real CPU cores are required.

Separation of networks Terminal bus and plant network must be separated with separate real network cards.

Graphics card settings 32MB

VMware Tools VMWare tools must be installed on the guest computers.

CPU load The CPU load system must not exceed a load of >75%. (source: according to VMWare)

RAM 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.)


2.2 Requirements


Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

2.2.3 Guest systems

Table 2-2

Features Requirements

Number of CPU cores 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.

Modules At least 2 physical modules are required. (one of which exclusively for the PLC bus)

Separation of networks Separation of terminal, PLC and Windows networks. If necessary, the terminal and Windows network can be combined.

CPU load 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 VMWare tools must be installed on the guest computers. (This yields a better performance.)

Hard disk storage management

If you are not using a dynamic storage management (the size of the hard disk file adjusts dynamically to the used capacity.).

Operating states 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.

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=16509462027&TopicId=14329600907

Note Chapter “4.2 Configuration of the guest systems” contains the properties employed for the measurements used in this document.

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

https://www.automation.siemens.com/mdm/default.aspx?DocVersionId=16509462027&TopicId=14329600907�


http://www.vmware.com/support�

http://www.vmware.com/resources/compatibility/search.php�


3.1 Process and required software


V1.0, Entry ID: 49368181

Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d


Content

This chapter shows you how to create virtual WinCC systems.

3.1 Process and required software

Table 3-1

No. Step Virtualization SW Guest SW

1. Establishing and creating the Management Station

VMware Workstation or VMware Player VMware Converter VMware vSphere Client

2. Creating the virtual system

--

3. Installation and configuration of the operating system on the virtual system

Depending on the application:

Windows XP

Windows 7

Windows 2003 Server

Windows 2008 Server

4. Installation of WinCC on the virtual system

VMware Workstation or VMware Player

Respective WinCC version depending on the application.

5. Installation and configuration of the virtualization server

VMware ESXi and VMware vSphere client

6. Transferring the virtual system onto the virtualization server

VMware Converter and VMware ESXi

7. Adjusting the configuration of the virtual system to the virtualization server

8. Start and operation of the virtual system

9. Checking the system load of the virtual system and the virtualization server.

VMware ESXi and VMware vSphere client

--

10. Operating the virtual system.

Windows Remote Desktop.

WinCC

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


3.2 Procedure in detail


Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d


Note 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. Step/Action

1. 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

2. 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”.





V1.0, Entry ID: 49368181

Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

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”.

4. 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=16509462027& TopicId=14291213323

5. 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.




https://www.automation.siemens.com/mdm/default.aspx?DocVersionId=16509462027&%20TopicId=14291213323�

https://www.automation.siemens.com/mdm/default.aspx?DocVersionId=16509462027&%20TopicId=14291213323�




Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

No. Step/Action

Transferring the virtual system onto the virtualization server 6.

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 user-defined 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”.




V1.0, Entry ID: 49368181

Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

No. Step/Action

7. 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”.

8. Start and operation of the virtual system [management station]



Select your transferred virtual system in the tree.

Start your virtual system by clicking the “Play” button. Your system is now restarted.

9. Checking the system load of the virtual system and the virtualization server. [management station] Diagnostics information is available in chapter “6 Diagnostic Capabilities”.

10. 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.

4 Framework Conditions for the Measurements

4.1 Hardware used


Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d


4.1 Hardware used

Configuration 1, IPC 647C

Table 4-1

Component ESX-Server 1 ESX-Server 2

Processor Intel Core i7-610E

2Cores/4Threads

2.53MHz cycle frequency with Turbo Boost

4MB Cache

VT-d and EM64T as expanded command sets

Intel Core i7-610E

2Cores/4Threads

2.53MHz cycle frequency with Turbo Boost

4MB Cache

VT-d and EM64T as expanded command sets

RAM 8 Gbytes DDR3 1066 SD-RAM 8 Gbytes DDR3 1066 SD-RAM

Hard disks 2x 500GB 2x 1000GB

Network cards 1x Onboard 82574L the only one accepted by VMware.

2x Intel PRO/1000GT (1000Base-T PCI), additionally plugged.

1x Onboard 82574L the only one accepted by VMware.

2x Intel PRO/1000GT (1000Base-T PCI), additionally plugged.

The network cards were used as follows:

Table 4-2

Network card Usage

Onboard 82574L Management network e.g. for vSpereClient access to ESXi

Intel PRO/1000GT Terminal Bus

Intel PRO/1000GT PLC Bus

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/industrial-pc/rack-pc/simatic-ipc647c/Pages/Default.aspx

http://www.automation.siemens.com/mcms/pc-based-automation/en/industrial-pc/rack-pc/simatic-ipc647c/Pages/Default.aspx�

http://www.automation.siemens.com/mcms/pc-based-automation/en/industrial-pc/rack-pc/simatic-ipc647c/Pages/Default.aspx�


4.1 Hardware used


V1.0, Entry ID: 49368181

Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

Configuration 2, HP Blade System “C7000 Enclosure G2”

Two Blade ESXi servers as cluster.

Table 4-3

Component Property

Processor 16 Cores (Intel Xeon Core i7 L5520, 2.27GHz)

RAM 192 GB

Processor 8 Cores (Intel Xeon Core i7 L5520, 2.27GHz)

RAM 98GByte

Hard disks No local hard disks, ESXi servers work with SAN (Storage Area Network).

Use

d fo

r E

SX

i

Network cards HP VC-Flags-10 ENET module 1GB (for management and communication with the PLCs).

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.

Note Further information on the used HP Blade system is available in the following link. http://h18004.www1.hp.com/products/blades/bladesystem/

Configuration 3, Fujitsu Primergy “RX 300 S6”

An ESXi server is used here.

Table 4-4

Component Property

Processor 12 Cores (Intel Xeon CPU 5650 2.67GHz)

RAM 24 GB

Hard disks 6x 600GB SATA (local)

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

Note 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.

http://h18004.www1.hp.com/products/blades/bladesystem/�

http://de.fujitsu.com/products/standard_servers/rack/primergy_rx300s6.html�


4.2 Configuration of the guest systems


Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d


Note For the settings of the guest systems please follow the installation notes and quantity frameworks of WinCC.


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 Setting

RAM 3072MB

CPUs 2

Graphics card 32MB

Hard disk 1 Virtual hard disk, not dynamic


CD/DVD drive ISO Image (with image of the WinCC DVD)

Network adapter 1 Terminal bus

Network adapter 2 PLC network

Disk drive 1 Client device





V1.0, Entry ID: 49368181

Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

Figure 4-1

WinCC Client (Windows 7)

Table 4-6

Hardware Setting

RAM 2048 MB

CPUs 2

Graphics card 32MB





WinCC Client (Windows XP SP3)

Table 4-7

Hardware Setting

RAM 1024MB

CPUs 2

Graphics card 32MB

VMCI device





4.3 Used software


Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

Hardware Setting

Network adapter 2 PLC network


4.3 Used software

Operating systems

Table 4-8

Type Operating system

Windows 2003R2 Server with SP2 WinCC Server

Windows 2008 Server (standard) with SP2

Windows 7 WinCC Client

Windows XP Professional +SP3

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 Property

Number of connection with CPUs 2

Number of external S7 variables 64000

Curve archiving 4200 values/second


4.3 Used software


V1.0, Entry ID: 49368181

Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

Criterion Property

Message archiving 8 messages/second

UserAchive 25 sets with two values in 5 seconds

Picture change In 5 seconds interval; Or whichever deviating value is given in the subsequent tests.

5 Test Scenarios and Basic Performance Data

4.3 Used software


Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d


Determining the basic performance data of the guest systems

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.)

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


4.3 Used software


V1.0, Entry ID: 49368181

Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

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


5.1 WinCC standalone


Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

5.1 WinCC standalone

Overview

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

SIMATIC IPC 647C

ESXi (1)

WinCCServer

Win 2008Server

SIMATIC IPC 647C

ESXi (2)

WinCCServer

Win 2003Server

Basic performance data

Table 5-1

PC Host/ Guest

PC Ø CPU in % Max. CPU in % Active RAM

ESXi (1) 36% 58% 1.3 GB (max. 2 GB)

Ho

st WinCC Server

Win Server 2008

35% 57% 1.2 GB (max. 1.9 GB)

IPC

647

C:

ES

Xi (

1)

Gu

est WinCC Server

Win Server 2008

25% 50% 1.9 GB

ESXi (2) 39% 65% 665 MB (max. 1.3 GB)

Ho

st WinCC Server

Win Server 2003

38% 64% 595 MB (max. 1.2 GB)

IPC

647

C:

EX

Si (

2)

Gu

est WinCC Server

Win Server 2003

27% 44% 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.


5.2 WinCC Server and one WinCC Client


V1.0, Entry ID: 49368181

Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

5.2 WinCC Server and one WinCC Client

Overview

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).


Figure 5-4

SIMATIC IPC 647C

ESXi (1)

WinCCServer

Win 2008Server

SIMATIC IPC 647C

ESXi (2)

WinCCServer

Win 2003Server

WinCCClient

Win XP

WinCCClient

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.


Table 5-2

PC Host/ Guest


ESXi (1) 56% 85% 1.4GB (max. 2GB)

WinCC Server Win Server 2008

34% 59% 1GB (max. 1.6GB)

Ho

st

WinCC Client Windows XP

21% 35% 235MB (max. 315MB)


29% 59% 1.9GB

IPC

647

C:

ES

Xi (

1)

Gu

est


11% 19% 485MB

EXSi (2) 59% 90% 970MB (max. 1.6GB)


37% 61% 220MB (max. 515MB)

Ho

st


21% 40% 320MB (max. 515MB)


37% 63% 1.4GB

IPC

647

C:

EX

Si (

2)

Gu

est


14% 24% 490GB


5.3 WinCC Server and two WinCC Standard Clients


Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d


Overview

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

SIMATIC IPC 647C

ESXi (1)

WinCCServer

Win 2008Server

SIMATIC IPC 647C

ESXi (2)

WinCCServer

Win 2003Server

WinCCClient

Win XP

WinCCClient

Win XP

WinCCClient

Win 7

WinCCClient

Win 7

HP Blade Server

ESXi (1) ESXi (2)

WinCCServer

Win 2008Server

WinCCServer

Win 2003Server

WinCCClient

Win XP

WinCCClient

Win 7

WinCCClient

Win XP

WinCCClient

Win 7

Fujitsu Primergy

ESXi (1)

WinCCServer

Win 2008Server

Fujitsu Primergy

ESXi (2)

WinCCServer

Win 2003Server

WinCCClient

Win XP

WinCCClient

Win XP

WinCCClient

Win 7

WinCCClient

Win 7




V1.0, Entry ID: 49368181

Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

Description

Operator actions occur at the server and both clients. On both stations pictures change in 5 seconds intervals for simulating an operation.


Table 5-3

PC Host/ Guest


ESXi (1) 70% 92% 2.2GB (max. 2.7GB)


34% 51% 1.4GB (max. 1.9GB)


19% 40% 210MB (max. 305MB)

Ho

st

WinCC Client Windows 7

17% 41% 455MB (max. 965MB)


39% 70% (max. 2.7GB)


20% 30% (max. 2.7GB)

IPC

647

C:

ES

Xi (

1)

Gu

est


16% 60% (max. 2.7GB)

EXSi (2) 78% 100% 2.0 GB (max. 2.8GB)


38% 63% 770MB (max. 1.3GB)


23% 40% 320MB (max. 515MB)

Ho

st


16% 26% 800MB (max. 1GB)


51% 74% (max. 2.7GB)


18% 45% (max. 2.7GB)

IPC

647

C:

EX

Si (

2)

Gu

est


14% 40% (max. 2.7GB)

ESXi 17% 27% 2 GB (max. 2.4GB)


34% 57% 975MB (max. 1.3GB)


20% 40% 220MB (max. 295MB)

Ho

st


13% 31% 840MB (max. 1GB)


36% 67% 1.6 GB


19% 34% 460 MB

HP

Bla

de:

ES

Xi

(1)

Gu

est


14% 26% 880 MB




Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

PC Host/ Guest


ESXi 17% 26% 1.6GB (max. 2GB)


37% 59% 535MB (max. 880MB)


17% 36% 180MB (max. 285MB)

Ho

st


13% 30% 800MB (max. 1.1GB)


42% 51% 1.2 GB


17% 36% 500 MB

HP

Bla

de:

ES

Xi

(2)

Gu

est


11% 25% 860 MB

ESXi 11% 19% 1.9GB (max. 2.4GB)


33% 50% 1.3GB (max. 1.6GB)


17% 38% 215MB (max. 515MB)

Ho

st


12% 28% 405MB (max. 525MB)


23% 42% 1.6 GB


12% 24% 465 MB

Fu

jitsu

Pri

mer

gy:

ES

Xi

(1)

Gu

est


7% 13% 910 MB

ESXi 11% 18% 1.3GB (max. 1.9GB)


36% 48% 670MB (max. 1GB)


17% 39% 215MB (max. 305MB)

Ho

st


12% 29% 400MB (max. 600MB)


26% 36% 1.3GB


12% 23% 480MB

Fu

jitsu

Pri

mer

gy:

ES

Xi

(2)

Gu

est


7% 14% 920MB

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.


5.4 WinCC Server and three WinCC Standard Clients


V1.0, Entry ID: 49368181

Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

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.


Overview

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).


SIMATIC IPC 647C

HP Blade Server

Fujitsu Primergy

Figure 5-6

SIMATIC IPC 647C

ESXi (1)

WinCCServer

Win 2008Server

WinCCClient

Win XP

WinCCClient

Win 7

WinCCClient

Win XP

SIMATIC IPC 647C

ESXi (2)

WinCCServer

Win 2003Server

WinCCClient

Win XP

WinCCClient

Win 7

WinCCClient

Win XP

HP Blade Server

ESXi (1) ESXi (2)

WinCCServer

Win 2008Server

WinCCClient

Win XP

WinCCClient

Win 7

WinCCClient

Win XP

WinCCServer

Win 2003Server

WinCCClient

Win XP

WinCCClient

Win 7

WinCCClient

Win XP




Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

Fujitsu Primergy

ESXi (1)

Fujitsu Primergy

ESXi (2)

WinCCServer

Win 2008Server

WinCCClient

Win XP

WinCCClient

Win 7

WinCCClient

Win XP

WinCCServer

Win 2003Server

WinCCClient

Win XP

WinCCClient

Win 7

WinCCClient

Win XP

Description

The clients are WinCC standard clients.

There is no operation at the server, on the clients pictures change every 5 seconds.


PC Host/ Guest

Computer Ø CPU in % Max. CPU in % Active RAM

ESXi (1) 76% 100% 2.8 GB (max. 3.7 GB)


30% 45% 1 GB (max. 1.4 GB)


14% 41% 570 MB (max. 725 MB)


15% 31% 595 MB (max. 755 MB)

Ho

st


16% 30% 515 MB (max. 1.1 GB)


41% 80% 1.9 GB


12% 51% 510 MB


17% 36% 510 MB

ICP

647

C:

ES

Xi (

1)

Gu

est


14% 59% 950 MB




V1.0, Entry ID: 49368181

Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

PC Host/ Guest


EXSi (2) 73% 100% 2 GB (max. 2.8 GB)


29% 48% 620 MB (max. 1 GB)


19% 35% 430 MB (max. 525 MB)


13% 32% 565 MB (max. 675 MB)

Ho

st


10% 16% 320 MB (max. 525 MB)


41% 80% 1.9 GB


12% 51% 510 MB


17% 36% 510 MB

ICP

647

C:

EX

Si (

2)

Gu

est


14% 59% 950 MB

ESXi 19% 28% 2.3 GB (max. 2.7 GB)


30% 43% 1.2 GB (max. 1.6 GB)


13% 22% 215 MB (max. 315 MB)


15% 38% 215 MB (max. 305 MB)

Ho

st


19% 32% 670 MB (max. 880 MB)


32% 54% 1.5 GB


10% 16% 460 MB


14% 41% 460 MB

HP

Bla

de:

ES

Xi

(1)

Gu

est


13% 26% 890 MB

ESXi 20% 29% 1.5 GB (max. 2 GB)


31% 39% 455 MB (max. 720 MB)


19% 33% 220 MB (max. 325 MB)


15% 34% 225 MB (max. 400 MB)

Ho

st


11% 35% 545 MB (max. 880 MB)


32% 54% 1.1 GB


10% 16% 460 MB


14% 41% 460 MB

HP

Bla

de:

ES

Xi

(2)

Gu

est


13% 26% 870 MB




Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

PC Host/ Guest


ESXi 11% 19% 1.8 GB (max. 2.3 GB)


24% 34% 1.2 GB (max. 1.6 GB)


11% 16% 150 MB (max. 230 MB)


14% 43% 180 MB (max. 315 MB)

Ho

st


12% 29% 330 MB (max. 590 MB)


17% 29% 1.5 GB


7% 10% 460 MB


8% 24% 480 MB

Fu

jitsu

Pri

mer

gy:

ES

Xi

(1)

Gu

est


7% 14% 910 MB

ESXi 12% 19% 1.3 GB (max. 2 GB)


30% 38% 490 MB (max. 690 MB)


18% 41% 205 MB (max. 350 MB)


14% 39% 205 MB (max. 295 MB)

Ho

st


9% 11% 305 MB (max. 465 MB)


20% 29% 1.2 GB


11% 21% 470 MB


9% 20% 485 MB

Fu

jitsu

Pri

mer

gy:

ES

Xi

(2)

Gu

est


4% 6% 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.


5.5 WinCC Server on ESXi (1) and four WinCC Clients on ESXi (2)


V1.0, Entry ID: 49368181

Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d


5.5.1 WinCC Server on ESXi (1) and four WinCC Standard Clients on ESXi (2)

Overview

The figure below shows a schematic illustration of the virtual components of this solution.


SIMATIC IPC 647C

HP Blade Server

Figure 5-7

SIMATIC IPC 647C

ESXi (1)

WinCCServer

Win 2008Server

SIMATIC IPC 647C

ESXi (2)

WinCCClient

Win 7

WinCCClient

Win XP

WinCCClient

Win 7

WinCCClient

Win XP

HP Blade Server

ESXi (1) ESXi (2)

WinCCServer

Win 2008Server

WinCCClient

Win 7

WinCCClient

Win XP

WinCCClient

Win 7

WinCCClient

Win XP

Description

No operation occurs at the server.

The clients are standard clients.




Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d


PC Host/ Guest


ESXi (1) 33% 55% 1.2 GB (max. 1.75 GB)

Ho

st WinCC Server

Win Server 2008

33% 54% 1.1 GB (max. 1.7 GB)

IPC

647

C:

ES

Xi (

1)

Gu

est WinCC Server

Win Server 2008

31% 45% 1.9 GB

EXSi (2) 60% 80% 1.6 GB (max. 1.9 GB)


11% 13% 440 MB (max. 570 MB)


14% 28% 400 MB (max. 545 MB)


20% 34% 215 MB (max. 295 MB)

Ho

st


13% 35% 485 MB (max. 590 MB)


10% 14% 915 MB


14% 40% 955 MB


20% 31% 485 MB

IPC

647

C:

EX

Si (

2)

Gu

est


15% 31% 490 MB

ESXi 8% 16% 1.5 GB (max. 2 GB)

Ho

st WinCC Server

Win Server 2008

27% 52% 1.1 GB (max. 1.5 GB)

HP

Bla

de:

ES

Xi

(1)

Gu

est WinCC Server

Win Server 2008

29% 62% 1.8 GB

ESXi 15% 26% 1 GB (max. 1.4 GB)


11% 14% 320 MB (max. 482 MB)


14% 27% 320 MB (max. 440 MB)


18% 32% 203 MB (max. 294 MB)

Ho

st


14% 24% 200 MB (max. 252 MB)


9% 14% 1 GB

HP

Bla

de:

ES

Xi

(2)

Gu

est


14% 21% 1 GB




V1.0, Entry ID: 49368181

Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

PC Host/ Guest



20% 38% 560 MB


15% 31% 560 MB




Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

5.5.2 WinCC Server on ESXi (1) and four WinCC Multi Clients on ESXi (2)

Overview



SIMATIC IPC 647C

HP Blade Server

Figure 5-8

SIMATIC IPC 647C

ESXi (1)

WinCCServer

Win 2008Server

SIMATIC IPC 647C

ESXi (2)

WinCCClient

Win 7

WinCCClient

Win XP

WinCCClient

Win 7

WinCCClient

Win XP

HP Blade Server

ESXi (1) ESXi (2)

WinCCServer

Win 2008Server

WinCCClient

Win XP

WinCCClient

Win 7

WinCCClient

Win XP

WinCCClient

Win 7

Description


The clients are multi clients.




V1.0, Entry ID: 49368181

Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d


PC Host/ Guest


ESXi (1) 37% 55% 1.3 GB (max. 1.9 GB)

Ho

st WinCC Server

Win Server 2008

37% 54% 1.2 GB (max. 1.8 GB)

IPC

647

C:

ES

Xi (

1)

Gu

est WinCC Server

Win Server 2008

30% 44% 1.9 GB

EXSi (2) 69% 89% 1.8 GB (max. 2.2 GB)


15% 30% 460 MB (max. 650 MB)


10% 27% 485 MB (max. 675 MB)


16% 35% 390 MB (max. 475 MB)

Ho

st


18% 33% 410 MB (max. 570 MB)


10% 30% 975 MB


15% 30% 990 MB


20% 28% 565 MB

IPC

647

C:

EX

Si (

2)

Gu

est


16% 38% 550 MB

ESXi 8% 17% 1.5 GB (max. 2 GB)

Ho

st WinCC Server

Win Server 2008

28% 43% 1.1 GB (max. 1.6 GB)

HP

Bla

de:

ES

Xi

(1)

Gu

est WinCC Server

Win Server 2008

28% 50% 1.6 GB

ESXi 15% 23% 1 GB (max. 1.3 GB)


11% 14% 330 MB (max. 505 MB)


14% 27% 340 MB (max. 505 MB)


18% 24% 205 MB (max. 295 MB)

Ho

st


13% 37% 185 MB (max. 275 MB)


8% 14% 1 GB

HP

Bla

de:

ES

Xi

(2)

Gu

est


14% 27% 1 GB




Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

PC Host/ Guest



19% 30% 580 MB


14% 38% 570 MB

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.




V1.0, Entry ID: 49368181

Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

5.5.3 WinCC Server and four WinCC Standard Clients

Overview



HP Blade Server

Fujitsu Primergy Server

Figure 5-9

HP Blade Server

ESXi

WinCCServer

Win 2008Server

WinCCClient

Win 7

WinCCClient

Win XP

WinCCClient

Win 7

WinCCClient

Win XP

Fujitsu Primergy

ESXi

WinCCServer

Win 2008Server

WinCCClient

Win 7

WinCCClient

Win XP

WinCCClient

Win 7

WinCCClient

Win XP

Description


The clients are standard clients with operation.




Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d


PC Host/ Guest


ESXi 24% 39% 2.9 GB (max. 3.4 GB)


30% 44% 1.3 GB (max. 1.6 GB)


14% 26% 685 MB (max. 880 MB)


13% 27% 470 MB (max. 610 MB)


18% 34% 185 MB (max. 350 MB)

Ho

st


17% 36% 205 MB (max. 360 MB)


32% 55% 1.6 GB


11% 15% 900 MB


13% 27% 880 MB


19% 37% 470 MB

HP

Bla

de

Gu

est


16% 38% 470 MB

ESXi 13% 22% 2.2 GB (max. 2.6 GB)


25% 44% 1.1 GB (max. 1.4 GB)


8% 11% 240 MB (max. 380 MB)


12% 39% 375 MB (max. 715 MB)


18% 34% 200 MB (max. 305 MB)

Ho

st


14% 39% 190 MB (max. 325 MB)


17% 32% 1.4 GB


4% 6% 910 MB


8% 33% 900 MB


13% 23% 475 MB

Fu

jitsu

Pri

mer

gy

Gu

est


8% 26% 485 MB




V1.0, Entry ID: 49368181

Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

5.5.4 WinCC Server and four WinCC Multi Clients on one ESXi

Overview



HP Blade Server

Fujitsu Primergy Server

Figure 5-10

HP Blade Server

ESXi

WinCCServer

Win 2008Server

WinCCClient

Win XP

WinCCClient

Win 7

WinCCClient

Win XP

WinCCClient

Win 7

Fujitsu Primergy

ESXi

WinCCServer

Win 2008Server

WinCCClient

Win XP

WinCCClient

Win 7

WinCCClient

Win XP

WinCCClient

Win 7

Description


The clients are multi clients with operation.




Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d


PC Host/ Guest


ESXi 22% 40% 2.4 GB (max. 2.8 GB)


29% 46% 1.1 GB (max. 1.5 GB)


10% 80% 430 MB (max. 695 MB)


13% 30% 365 MB (max. 570 MB)


18% 32% 225 MB (max. 325 MB)

Ho

st


16% 35% 210 MB (max. 315 MB)


31% 67% 1.7 GB


8% 68% 1 GB


13% 23% 1 GB


18% 32% 580 MB

HP

Bla

de

Gu

est


16% 35% 590 MB

ESXi 13% 22% 2.3 GB (max. 2.8 GB)


25% 40% 1.2 GB (max. 1.5 GB)


9% 12% 330 MB (max. 550 MB)


12% 22% 320 MB (max. 485 MB)


17% 35% 230 MB (max. 305 MB)

Ho

st


14% 40% 205 MB (max. 285 MB)


18% 36% 1.6 GB


4% 7% 1 GB


6% 10% 1 GB


12% 21% 590 MB

Fu

jitsu

Pri

mer

gy

Gu

est


8% 23% 580 MB




V1.0, Entry ID: 49368181

Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

5.5.5 WinCC Server on ESXi (1) and five WinCC Standard Clients on ESXi (2)

Overview



SIMATIC IPC 647C

HP Blade Server

Figure 5-11

SIMATIC IPC 647C

ESXi (1)

WinCCServer

Win 2008Server

SIMATIC IPC 647C

ESXi (2)

WinCCClient

Win 7

WinCCClient

Win XP

WinCCClient

Win 7

WinCCClient

Win XP

WinCCClient

Win XP

HP Blade Server

ESXi (1) ESXi (2)

WinCCServer

Win 2008Server

WinCCClient

Win 7

WinCCClient

Win XP

WinCCClient

Win 7

WinCCClient

Win XP

WinCCClient

Win XP

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.


The clients are standard clients.




Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d


PC Host/ Guest


ESXi (1) 39% 57% 1.45 GB (max. 1.8 GB)

Ho

st


38% 56% 1.4 GB (max. 1.7 GB)

IPC

647

C:

ES

Xi (

1)

Gu

est WinCC Server

Win Server 2008

37% 46% 1.9 GB

EXSi (2) 81% 100% 2 GB (max. 2.4 GB)


15% 26% 520 MB (max. 665 MB)


14% 23% 425 MB (max. 630 MB)


17% 30% 200 MB (max. 305 MB)


16% 31% 470 MB (max. 580 MB)

Ho

st


18% 32% 325 MB (max. 430 MB)


15% 43% 940 MB


14% 57% 960 MB


22% 42% 485 MB


22% 53% 495 MB

IPC

647

C:

EX

Si (

2)

Gu

est


20% 47% 450 MB

ESXi 9% 17% 1.8 GB (max. 2.2 GB)

Ho

st WinCC Server

Win Server 2008

32% 53% 1.4 GB (max. 1.8 GB)

HP

Bla

de:

ES

Xi

(1)

Gu

est WinCC Server

Win Server 2008

33% 61% 1.8 GB

ESXi 22% 31% 1.4 GB (max. 1.9 GB)


14% 28% 355 MB (max. 485 MB)


14% 30% 320 MB (max. 505 MB)


19% 35% 215 MB (max. 305 MB)


17% 31% 210 MB (max. 275 MB)

HP

Bla

de:

ES

Xi

(2)

Ho

st


19% 35% 215 MB (max. 545 MB)




V1.0, Entry ID: 49368181

Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

PC Host/ Guest



33% 61% 1.8 GB


14% 27% 1 GB


14% 28% 1 GB


21% 35% 570 MB

Gu

est


20% 35% 560 MB




Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

5.5.6 WinCC Server on ESXi (1) and five WinCC Standard Clients on ESXi (2)

Overview



SIMATIC IPC 647C

HP Blade Server

Figure 5-12

SIMATIC IPC 647C

ESXi (1)

WinCCServer

Win 2008Server

SIMATIC IPC 647C

ESXi (2)

WinCCClient

Win 7

WinCCClient

Win XP

WinCCClient

Win 7

WinCCClient

Win XP

WinCCClient

Win XP

HP Blade Server

ESXi (1) ESXi (2)

WinCCServer

Win 2008Server

WinCCClient

Win 7

WinCCClient

Win XP

WinCCClient

Win 7

WinCCClient

Win XP

WinCCClient

Win XP

Description


The clients are standard clients, a picture change occurs every 20 seconds.




V1.0, Entry ID: 49368181

Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d


PC Host/ Guest


ESXi (1) 31% 55% 1 GB (max. 1.7 GB)

Ho

st WinCC Server

Win Server 2008

30% 54% 950 MB (max. 1.6 GB)

IPC

647

C:

ES

Xi (

1)

Gu

est WinCC Server

Win Server 2008

35% 45% 1.9 GB

EXSi (2) 59% 88% 1.9 GB (max. 2.5 GB)


11% 31% 470 MB (max. 650 MB)


9% 31% 370 MB (max. 545 MB)


13% 38% 310 MB (max. 485 MB)


11% 33% 445 MB (max. 570 MB)

Ho

st


14% 26% 215 MB (max. 370 MB)


10% 25% 940 MB


11% 45% 955 MB


14% 29% 490 MB


12% 21% 490 MB

IPC

647

C:

EX

Si (

2)

Gu

est


13% 19% 455 MB

ESXi 8% 16% 1.5 GB (max. 1.9 GB)

Ho

st WinCC Server

Win Server 2008

28% 48% 1.1 GB (max. 1.4 GB)

HP

Bla

de:

ES

Xi

(1)

Gu

est WinCC Server

Win Server 2008

30% 76% 1.8 GB

ESXi 17% 38% 1.4 GB (max. 2.2 GB)


10% 47% 320 MB (max. 400 MB)


12% 99% 440 MB (max. 1GB)


14% 45% 195 MB (max. 325 MB)

HP

Bla

de:

ES

Xi

(2)

Ho

st


12% 45% 230 MB (max. 370 MB)




Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

PC Host/ Guest



15% 46% 185 MB (max. 275 MB)


9% 48% 1 GB


10% 65% 1 GB


14% 42% 570 MB


13% 50% 560 MB

Gu

est


12% 45% 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.




V1.0, Entry ID: 49368181

Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

5.5.7 WinCC Server and six WinCC Standard Clients on one ESXi

Overview


The HP Blade server is used as the test platform.

Figure 5-13

HP Blade Server

ESXi

WinCCServer

Win 2008Server

WinCCClient

Win 7

WinCCClient

Win 7

WinCCClient

Win 7

WinCCClient

Win XP

WinCCClient

Win XP

WinCCClient

Win XP

Fujitsu Primergy

ESXi

WinCCServer

Win 2008Server

WinCCClient

Win 7

WinCCClient

Win 7

WinCCClient

Win 7

WinCCClient

Win XP

WinCCClient

Win XP

WinCCClient

Win XP

Description




PC Host/ Guest


ESXi 30% 39% 3.5 GB (max. 4.3 GB)


31% 43% 1.3 GB (max. 1.6 GB)

HP

Bla

de

Ho

st


14% 28% 690 MB (max. 880 MB)




Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

PC Host/ Guest



11% 36% 370 MB (max. 545 MB)


12% 34% 410 MB (max. 610 MB)


17% 33% 190 MB (max. 260 MB)


15% 31% 200 MB (max. 260 MB)


13% 17% 180 MB (max. 325 MB)


34% 61% 1.5 GB


13% 25% 900 MB


12% 52% 900 MB


9% 43% 880 MB


20% 37% 470 MB


17% 39% 470 MB

Gu

est


13% 19% 470 MB

ESXi 19% 28% 2.8 GB (max. 3.4 GB)


27% 40% 1.3 GB (max. 1.6 GB)


12% 27% 315 MB (max. 465 MB)


10% 24% 300 MB (max. 485 MB)


11% 18% 330 MB (max. 610 MB)


17% 38% 205 MB (max. 305 MB)


18% 35% 195 MB (max. 275 MB)

Ho

st


12% 18% 165 MB (max. 255 MB)


18% 33% 1.4 GB


7% 13% 930 MB


5% 17% 900 MB


3% 8% 880 MB

Fu

jitsu

Pri

mer

gy

Gu

est


13% 23% 480 MB




V1.0, Entry ID: 49368181

Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

PC Host/ Guest



9% 26% 500 MB


7% 11% 450 MB




Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

5.5.8 WinCC Server and six WinCC Multi Clients on one ESXi

Overview



Figure 5-14

HP Blade Server

ESXi

WinCCServer

Win 2008Server

WinCCClient

Win 7

WinCCClient

Win 7

WinCCClient

Win 7

WinCCClient

Win XP

WinCCClient

Win XP

WinCCClient

Win XP

Fujitsu Primergy

ESXi

WinCCServer

Win 2008Server

WinCCClient

Win 7

WinCCClient

Win 7

WinCCClient

Win 7

WinCCClient

Win XP

WinCCClient

Win XP

WinCCClient

Win XP

Description




PC Host/ Guest


ESXi 28% 36% 3 GB (max. 3.6 GB)


29% 48% 1.3 GB (max. 1.9 GB)

HP

Bla

de

Ho

st


14% 29% 490 MB (max. 690 MB)




V1.0, Entry ID: 49368181

Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

PC Host/ Guest



10% 30% 315 MB (max. 440 MB)


11% 40% 295 MB (max. 480 MB)


17% 23% 220 MB (max. 315 MB)


15% 36% 210 MB (max. 315 MB)


13% 39% 205 MB (max. 265 MB)


32% 68% 1.7 GB


13% 25% 1 GB


10% 33% 1 GB


9% 40% 1 GB


19% 34% 580 MB


14% 38% 580 MB

Gu

est


13% 38% 565 MB

ESXi 18% 28% 2.9 GB (max. 3.5 GB)


27% 41% 1.3 GB (max. 1.5 GB)


12% 25% 360 MB (max. 525 MB)


10% 29% 325 MB (max. 505 MB)


12% 40% 310 MB (max. 485 MB)


17% 35% 210 MB (max. 305 MB)


18% 41% 230 MB (max. 380 MB)

Ho

st


13% 55% 215 MB (max. 305 MB)


19% 38% 1.6 GB


8% 13% 1 GB


5% 17% 1 GB


4% 24% 1 GB

Fu

jitsu

Pri

mer

gy

Gu

est


12% 21% 590 MB




Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

PC Host/ Guest



9% 22% 580 MB


7% 26% 570 MB


5.6 Using redundant server on one or two ESXi servers


V1.0, Entry ID: 49368181

Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d


5.6.1 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 Event

8:50 Server 2 (the master at this point in time) is deactivated

8:50 Server 1 becomes the master

8:55 Server 2 is activated

8:56 to 8:57 On both servers the new archives are created

9:00 Beginning of the archive synchronization

9:04 End of the archive synchronization




Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

CPU load curve server 1 (new master)

Figure 5-15

CPU load curve server 2 (old master, new standby)

Figure 5-16




V1.0, Entry ID: 49368181

Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

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).




Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

5.6.2 Two redundant servers as stand-alone stations on an ESXi server

Overview



SIMATIC IPC 647C

HP Blade Server

Figure 5-18

SIMATIC IPC 647C

ESXi

WinCCServer (M)

Win 2008Server

WinCCServer (S)

Win 2008Server

Redundancy connection

HP Blade Server

ESXi (1)

WinCCServer (M)

Win 2008Server

WinCCServer (S)

Win 2008Server


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=16484401291&TopicId=12262626827

Table 5-5

No. Failure scenarios Function Remark

1. Project on server computer not in runtime

Yes






V1.0, Entry ID: 49368181

Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d


2. Connection fault to partner server

No No test since a virtual terminal bus is used virtually.

3. Faulty network connection to client

No No test since stand-alone.

4. Faulty process connection No No function since both servers loose the connection.

5. Software error Yes


Table 5-6

PC Host/ Guest


ESXi 66% 98% 1 GB (max. 1.5 GB)

WinCC Server Win Server 2008(Master)

34% 48% 490 MB (max. 690 MB)

Ho

st WinCC Server

Win Server 2008(Standby)

32% 49% 475 MB (max. 725 MB)


45% 71% 1 GB

IPC

647

C:

ES

Xi b

efo

re c

han

ge

Gu

est WinCC Server


37% 46% 1.2 GB

ESXi 69% 95% 1 GB (max. 1.6 GB)


33% 59% 515 MB (max. 1 GB)

Ho

st WinCC Server


35% 50% 515 MB (max. 690 MB)


41% 53% 1.2 GB

IPC

647

C:

EX

Si (

afte

r ch

ang

e)45

4

Gu

est WinCC Server


41% 54% 1.2 GB

ESXi 18% 26% 1.2 GB (max. 1.5 GB)

WinCC Server Win Server 2008(Standby)

33% 53% 600 MB (max. 1 GB)

HP

Bla

de:

ES

Xi

bef

. ch

ang

e

Ho

st WinCC Server

Win Server 2008(Master)

35% 59% 570 MB (max. 1 GB)




Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

PC Host/ Guest



37% 50% 1.5 GB

Gu

est WinCC Server


42% 54% 1.5 GB

ESXi 18% 26% 1.2 GB (max. 1.5 GB)


33% 53% 600 MB (max. 1 GB)

Ho

st WinCC Server


35% 59% 570 MB (max. 1 GB)


38% 51% 1.5 GB

HP

Bla

de:

ES

Xi a

fter

ch

ang

e

Gu

est WinCC Server


39% 51% 1.5 GB




V1.0, Entry ID: 49368181

Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

5.6.3 Two redundant server without operation as stand-alone stations on ESXi (1) with four WinCC Multi Clients on ESXi (2)

Overview



SIMATIC IPC 647C

HP Blade Server

Figure 5-19

SIMATIC IPC 647C

ESXi (1)

WinCCServer (M)

Win 2008Server

WinCCServer (S)

Win 2008Server


SIMATIC IPC 647C

ESXi (2)

WinCCClient

Win 7

WinCCClient

Win XP

WinCCClient

Win 7

WinCCClient

Win XP

HP Blade Server

ESXi (1)

WinCCServer (M)

Win 2008Server

WinCCServer (S)

Win 2008Server


ESXi (2)

WinCCClient

Win 7

WinCCClient

Win XP

WinCCClient

Win 7

WinCCClient

Win XP

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.







Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

Table 5-7



Yes


No No test since a virtual terminal bus is used virtually.


No No test since stand-alone.

4. Faulty process connection No No function since both servers loose the connection.





V1.0, Entry ID: 49368181

Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d


Table 5-8

PC Host/ Guest


ESXi (1) 63% 82% 1 GB (max. 1.7 GB)


33% 50% 555 MB (max. 975 MB)

Ho

st WinCC Server


29% 48% 475 MB (max. 850 MB)


40% 56% 1.4 GB

IPC

647

C:

ES

Xi (

1) b

efo

re c

han

ge

Gu

est WinCC Server


34% 38% 1.4 GB

ESXi (2) 59% 90% 1.4 GB (max. 1.7 GB)


13% 31% 290 MB (max. 380 MB)


15% 36% 435 MB (max. 755 MB)


15% 31% 265 MB (max. 420 MB)

Ho

st


15% 29% 325 MB (max. 420 MB)


11% 43% 1 GB


12% 41% 1 GB


18% 31% 535 MB

IPC

647

C:

EX

Si (

2) b

efo

re c

han

ge

Gu

est


17% 31% 535 MB

ESXi (1) 62% 81% 1 GB (max. 1.8 GB)


31% 50% 455 MB (max. 1 GB)

Ho

st WinCC Server


30% 47% 495 MB (max. 850 MB)


35% 54% 1.3 GB

IPC

647

C:

ES

Xi (

1) a

fter

ch

ang

e5

Gu

est WinCC Server


37% 42% 1.3 GB




Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

PC Host/ Guest


ESXi (2) 58% 96% 1.5 GB (max. 1.8 GB)


13% 26% 425 MB (max. 545 MB)


14% 35% 430 MB (max. 610 MB)


15% 35% 230 MB (max. 350 MB)

Ho

st


14% 40% 360 MB (max. 555 MB)


10% 48% 1 GB


12% 34% 1 GB


18% 45% 545 MB

IPC

647

C:

EX

Si (

2) (

afte

r ch

ang

e)6

Gu

est


14% 32% 540 MB

ESXi (1) 17% 26% 1.5 GB (max. 2.3 GB)


29% 52% 570 MB (max. 1 GB)

Ho

st WinCC Server


32% 56% 560 MB (max. 1 GB)


32% 50% 1.4 GB

HP

Bla

de:

ES

Xi

(1)

bef

ore

ch

ang

e

Gu

est WinCC Server


38% 50% 1.4 GB

ESXi (2) 14% 22% 1.2 GB (max. 1.5 GB)


12% 34% 320 MB (max. 465 MB)


12% 33% 425 MB (max. 590 MB)


16% 38% 215 MB (max. 295 MB)

Ho

st


13% 36% 215 MB (max. 295 MB)


10% 33% 1 GB


11% 36% 950 MB


16% 41% 560 MB

HP

Bla

de:

ES

Xi

(2)

bef

ore

ch

ang

e

Gu

est


15% 39% 540 MB




V1.0, Entry ID: 49368181

Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

PC Host/ Guest


ESXi (1) 16% 24% 1.5 GB (max. 2.1 GB)


30% 52% 550 MB (max. 940 MB)

Ho

st WinCC Server


27% 53% 560 MB (max. 1.1 GB)


33% 51% 1.4 GB

HP

Bla

de:

ES

Xi (

1) a

fter

ch

ang

e7

Gu

est WinCC Server


31% 47% 1.4 GB

ESXi (2) 14% 22% 1.1 GB (max. 1.4 GB)


11% 35% 320 MB (max. 505 MB)


12% 35% 375 MB (max. 525 MB)


16% 32% 210 MB (max. 325 MB)

Ho

st


13% 32% 200 MB (max. 295 MB)


9% 23% 1 GB


11% 35% 950 MB


16% 32% 560 MB

HP

Bla

de:

ES

Xi (

2) a

fter

ch

ang

e 89

8

Gu

est


13% 32% 550 MB




Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

5.6.4 Two ESXi servers with one redundant server each and two WinCC clients

Overview



SIMATIC IPC 647C

HP Blade Server

Figure 5-20

SIMATIC IPC 647C

ESXi (1)

WinCCServer (M)

Win 2003Server


SIMATIC IPC 647C

ESXi (2)

WinCCClient

Win XP

WinCCClient

Win 7

WinCCServer (S)

Win 2003Server

WinCCClient

Win XP

WinCCClient

Win 7

HP Blade Server

ESXi (1) ESXi (2)

WinCCServer (M)

Win 2003Server


WinCCClient

Win XP

WinCCClient

Win 7

WinCCServer (S)

Win 2003Server

WinCCClient

Win XP

WinCCClient

Win 7

Description







V1.0, Entry ID: 49368181

Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

Table 5-9



Yes


Yes Function given. Client switch-over, see following scenario.


No No test, all clients run via one connection. Upon failure the clients want to switch over and become inoperable.

4. Faulty process connection Yes



Table 5-10

PC Host/ Guest


ESXi (1) 71% 97% 1.5 GB (max. 2.1 GB)


39% 57% 600 MB (max. 940 MB)


13% 38% 516 MB (max. 713 MB)

Ho

st


18% 38% 380 MB (max. 524 MB)


41% 70% 1.4 GB


15% 38% 1 GB

IPC

647

C:

ES

Xi (

1)

Gu

est


19% 26% 550 MB

ESXi (2) 71% 92% 1.4 GB (max. 2 GB)


36% 53% 590 MB (max. 1 GB)


15% 36% 430 MB (max. 610 MB)

Ho

st


19% 37% 300 MB (max. 470 MB)


42% 67% 1.4 GB


15% 56% 1 GB

IPC

647

C:

EX

Si (

2)

Gu

est


20% 39% 550 MB




Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

PC Host/ Guest


ESXi (1) 17% 27% 1.4 GB (max. 2.2 GB)


29% 48% 510 MB (max. 910 MB)


15% 28% 325 MB (max. 525 MB)

Ho

st


18% 34% 200 MB (max. 340 MB)


39% 53% 1.4 GB


13% 23% 1 GB

HP

Bla

de:

ES

Xi

(1)

Gu

est


18% 38% 550 MB

ESXi (2) 16% 26% 1.6 GB (max. 2.2 GB)


33% 51% 562 MB (max. 1 GB)


13% 31% 750 MB (max. 925 MB)

Ho

st


16% 34% 210 MB (max. 315 MB)


37% 53% 1.4 GB


13% 25% 935 MB

HP

Bla

de

(2)

Gu

est


18% 36% 550 MB




V1.0, Entry ID: 49368181

Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

5.6.5 Two redundant WinCC servers without operation with six WinCC multi clients on one ESXi server

Overview



HP Blade Server

Fujitsu Primergy

Figure 5-21

HP Blade Server

ESXi

WinCCServer (M)

Win 2003Server


WinCCServer (S)

Win 2003Server

WinCCClient

Win XP

WinCCClient

Win 7

WinCCClient

Win 7

WinCCClient

Win 7

WinCCClient

Win XP

WinCCClient

Win XP

Fujitsu Primergy

ESXi

WinCCServer (M)

Win 2003Server


WinCCServer (S)

Win 2003Server

WinCCClient

Win XP

WinCCClient

Win 7

WinCCClient

Win 7

WinCCClient

Win 7

WinCCClient

Win XP

WinCCClient

Win XP


Table 5-11

PC Host/ Guest


ESXi 36% 45% 2.7 GB (max. 3.4 GB)


29% 55% 660 MB (max. 1 GB)

HP

Bla

de

Ho

st WinCC Server


30% 53% 510 MB (max. 1 GB)




Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

PC Host/ Guest



12% 36% 335 MB (max. 465 MB)


10% 30% 330 MB (max. 525 MB)


12% 21% 305 MB (max. 440 MB)


14% 35% 215 MB (max. 295 MB)


14% 37% 215 MB (max. 350 MB)


16% 38% 210 MB (max. 275 MB)


43% 65% 1.4 GB


31% 46% 1.4 GB


10% 34% 1 GB


10% 15% 1 GB


10% 14% 1 GB


15% 36% 600 MB


13% 49% 620 MB

Gu

est


15% 35% 580 MB

ESXi 21% 28% 2.8 GB (max. 3.3 GB)


29% 40% 500 MB (max. 725 MB)


32% 42% 510 MB (max. 820 MB)


10% 23% 295 MB (max. 490 MB)


8% 38% 310 MB (max. 420 MB)


7% 11% 540 MB (max. 820 MB)


14% 42% 215 MB (max. 300 MB)


13% 48% 210 MB (max. 300 MB)

Fu

jitsu

Pri

mer

gy

Ho

st


11% 15% 185 MB (max. 300 MB)




V1.0, Entry ID: 49368181

Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

PC Host/ Guest



20% 25% 1.4 GB


23% 28% 1.4 GB


5% 13% 1 GB


4% 18% 1 GB


3% 6% 950 MB


9% 27% 560 MB


8% 29% 570 MB

Gu

est


6% 9% 550 MB




Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

5.6.6 Two ESXi servers with one redundant server each and three WinCC clients each

Overview



Figure 5-22

HP Blade Server

ESXi (1) ESXi (2)

WinCCServer (M)

Win 2008Server

WinCCServer (S)

Win 2008Server

WinCCClient

Win XP

WinCCClient

Win XP

WinCCClient

Win 7

WinCCClient

Win XP

WinCCClient

Win XP

WinCCClient

Win 7

Terminal bus



Table 5-12

PC Host/ Guest


ESXi (1) 18% 28% 1.6 GB (max. 2.5 GB)


29% 47% 515 MB (max. 1 GB)


15% 36% 215 MB (max. 325 MB)


13% 23% 190 MB (max. 340 MB)

Ho

st


12% 38% 320 MB (max. 610 MB)


34% 50% 1.4 GB


15% 42% 535 MB


14% 21% 535 MB

HP

Bla

de:

ES

Xi

(1)

Gu

est


8% 36% 1 GB




V1.0, Entry ID: 49368181

Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

PC Host/ Guest


ESXi (2) 19% 28% 2 GB (max. 2.4 GB)


33% 57% 535 MB (max. 1 GB)


16% 38% 180 MB (max. 300 MB)


11% 45% 480 MB (max. 880 MB)

Ho

st


11% 31% 690 MB (max. 1 GB)


39% 51% 1.4 GB


14% 41% 545 MB


11% 51% 950 MB

HP

Bla

de:

ES

Xi

(2)

Gu

est


8% 38% 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 Client Picture change, all [s]

ESXi (2) WinCC Client 1, Windows 7 10

ESXi (1) WinCC Client 2, Windows XP 10

WinCC Client 3, Windows 7 15 ESXi (2)

WinCC Client 4, Windows XP 20






Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d


Table 5-14

PC Host/ Guest


ESXi (1) 15% 27% 1.9 GB (max. 2 GB)


30% 47% 515 MB (max. 850 MB)

WinCC Client 2 Windows XP

11% 32% 750 MB (max. 950 MB)

Ho

st

WinCC Client 5 Windows 7

15% 20% 185 MB (max. 295 MB)


34% 44% 1.4 GB


10% 16% 960 MB

HP

Bla

de:

ES

Xi

(1)

Gu

est


14% 38% 540 MB

ESXi (2) 21% 20% 2.1GB (max. 3.2 GB)


27% 41% 470 MB (max. 910 MB)


11% 35% 670 MB (max. 780 MB)


10% 38% 620 MB (max. 880 MB)


14% 21% 160 MB (max. 340 MB)

Ho

st


16% 24% 160 MB (max. 360 MB)


33% 47% 1.3 GB


9% 18% 980 MB


10% 35% 960 MB


11% 36% 540 MB

HP

Bla

de:

ES

Xi

(2)

Gu

est


12% 34% 540 MB




V1.0, Entry ID: 49368181

Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

5.6.7 Two redundant WinCC servers on ESXi (1) and one WinCC client with WinCC/Webnavigator, as well as 3 WinCC WebClients on ESXi (2)

Overview



SIMATIC IPC 647C

HP Blade Server

Figure 5-23

SIMATIC IPC 647C

ESXi (1)

WinCCServer

Win 2003Server


SIMATIC IPC 647C

ESXi (2)

WinCCWebClient

Win 7

WinCCServer red.

Win 2003Server

WinCCWebClient

Win XP

WinCCClient

Win XP

WebNavigator

WinCCWebClient

Win XP

HP Blade Server

ESXi (1) ESXi (2)

WinCCServer

Win 2003Server


WinCCWebClient

Win 7

WinCCServer red.

Win 2003Server

WinCCWebClient

Win XP

WinCCClient

Win XP

WebNavigator

WinCCWebClient

Win XP

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.




Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d


Table 5-15

PC Host/ Guest


ESXi (1) 62% 78% 1 GB (max. 1.6 GB)


30% 39% 420 MB (max. 785 MB)

Ho

st WinCC Server


31% 48% 590 MB (max. 975 MB)


30% 33% 1.4 GB

IPC

647

C:

ES

Xi (

1)

Gu

est WinCC Server


37% 52% 1.4 GB

ESXi (2) 45% 60% 1.7 GB (max. 2 GB)

WinCC Client and WebServer Windows XP

8% 10% 305 MB (max. 390 MB)


11% 23% 490 MB (max. 695 MB)


13% 23% 400 MB (max. 475 MB)

Ho

st


11% 22% 410 MB (max. 545 MB)


5% 7% 530 MB


8% 27% 960 MB


15% 16% 380 MB

IPC

647

C:

EX

Si (

2)

Gu

est


14% 19% 380 MB

ESXi (1) 65% 81% 1 GB (max. 1.6 GB)


35% 51% 590 MB (max. 975 MB)

Ho

st WinCC Server


29% 39% 430 MB (max. 880 MB)


38% 47% 1.4 GB

IPC

647

C:

ES

Xi (

1) (

afte

r ch

ang

e)9

Gu

est WinCC Server


33% 35% 1.4 GB




V1.0, Entry ID: 49368181

Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

PC Host/ Guest


ESXi (2) 47% 89% 1.6 GB (max. 2 GB)


8% 10% 325 MB (max. 525 MB)


12% 22% 485 MB (max. 505 MB)


12% 24% 390 MB (max. 480 MB)

Ho

st


11% 21% 385 MB (max. 485 MB)


5% 8% 550 MB


8% 23% 950 MB


15% 18% 380 MB

IPC

647

C:

EX

Si (

2) (

afte

r ch

ang

e)1

0

Gu

est


14% 18% 380 MB

ESXi (1) 15% 23% 1.4 GB (max. 1.9 GB)


31% 52% 660 MB (max. 1 GB)

Ho

st WinCC Server


26% 28% 410 MB (max. 600 MB)


34% 50% 1.4 GB

HP

Bla

de:

ES

Xi

(1)

Gu

est WinCC Server


29% 33% 1.4 GB

ESXi (2) 12% 20% 805 MB (max. 1 GB)


9% 11% 140 MB (max. 220 MB)


9% 18% 345 MB (max. 465 MB)


13% 22% 160 MB (max. 240 MB)

Ho

st


14% 25% 155 MB (max. 250 MB)


4% 6% 540 MB

HP

Bla

de:

ES

Xi

(2)

Gu

est


7% 17% 820 MB




Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

PC Host/ Guest



13% 26% 370 MB


13% 25% 370 MB

ESXi (1) 15% 25% 1.4 GB (max. 1.9 GB)


29% 51% 620 MB (max. 1 GB)

Ho

st WinCC Server


28% 30% 455 MB (max. 725 MB)


33% 49% 1.4 GB

HP

Bla

de:

ES

Xi (

1) (

afte

r ch

ang

e)1

1

Gu

est WinCC Server


31% 36% 1.4 GB

ESXi (2) 12% 20% 820 MB (max. 1 GB)


9% 11% 145 MB (max. 220 MB)


9% 18% 340 MB (max. 485 MB)


13% 23% 160 MB (max. 240 MB)

Ho

st


14% 23% 150 MB (max. 265 MB)


3% 6% 540 MB


7% 16% 820 MB


13% 26% 370 MB

HP

Bla

de:

ES

Xi

(2)

afte

r ch

ang

e1

2

Gu

est


12% 25% 370 MB




V1.0, Entry ID: 49368181

Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

5.6.8 Two redundant WinCC servers and one WinCC client with WinCC/Webnavigator, as well as 3 WinCC WebClients on one ESXi

Overview



HP Blade Server

Fujitsu Primergy

Figure 5-24

HP Blade Server

ESXi

WinCCServer

Win 2003Server


WinCCWebClient

Win XP

WinCCServer red.

Win 2003Server

WinCCWebClient

Win 7

WinCCClient

Win XP

WebNavigator

WinCCWebClient

Win 7

Fujitsu Primergy

ESXi

WinCCServer

Win 2003Server


WinCCWebClient

Win XP

WinCCServer red.

Win 2003Server

WinCCWebClient

Win 7

WinCCClient

Win XP

WebNavigator

WinCCWebClient

Win 7

Description

The same test as in chapter 2.4.6.7, on the HP Blade server in only one ESXi.


Table 5-16

PC Host/ Guest


ESXi 25% 33% 2.3 GB (max. 3.3 GB)

HP

Bla

de

Ho

st WinCC Server


28% 48% 575 MB (max. 1 GB)




Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

PC Host/ Guest



28% 30% 395 MB (max. 505 MB)


8% 26% 170 MB (max. 325 MB)


12% 21% 155 MB (max. 235 MB)


10% 19% 495 MB (max. 695 MB)


9% 26% 500 MB (max. 800 MB)


36% 52% 1.4 GB


32% 33% 1.4 GB


4% 30% 530 MB


13% 26% 365 MB


6% 15% 795 MB

Gu

est


9% 22% 820 MB

ESXi 16% 23% 2.1 GB (max. 2.5 GB)


27% 30% 410 MB (max. 565 MB)


32% 42% 595 MB (max. 820 MB)


7% 9% 155 MB (max. 220 MB)


13% 21% 190 MB (max. 220 MB)


8% 16% 285 MB (max. 400 MB)

Ho

st


9% 17% 450 MB (max. 695 MB)


19% 21% 1.4 GB

Fu

jitsu

Pri

mer

gy

Gu

est WinCC Server


22% 26% 1.4 GB




V1.0, Entry ID: 49368181

Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

PC Host/ Guest



2% 3% 550 MB


8% 16% 480 MB


4% 11% 940 MB


4% 9% 720 MB




Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

5.6.9 Using one (external) engineering station for downloading the projects

Overview

The figure below shows a schematic illustration of the most important components of this solution.


Figure 5-25

SIMATIC IPC 647C

ESXi (1)

WinCCServer

Win 2003Server


SIMATIC IPC 647C

ESXi (2)

WinCCClient

Win XP

WinCCServer red.

Win 2003Server

WinCCClient

Win XP

Field PG

EngineeringStation

Win XP

Ethernet

6 Diagnostic Capabilities

6.1 Diagnosis with VMware vSphere Client


V1.0, Entry ID: 49368181

Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d



General information

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).

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. Step/Action

1. Logging on at the ESXi server



2. 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.

3. 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.




Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

No. Step/Action

4. 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.

5. Adjusting the diagnostics of the virtual system To do this, proceed as in step 3.


6.2 Diagnosis in the virtual system


V1.0, Entry ID: 49368181

Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

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. Step/Action

1. Starting the tool Click on “Start > Run...”. The “Run...” dialog appears.

Enter “Perfmon” and click on OK. The monitoring tool starts.

2. 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.

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.

7 6BGlossary


Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

7 Glossary

ESXi

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.

7 6BGlossary


V1.0, Entry ID: 49368181

Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

vSphere Client

A product by VMware for configuration, monitoring and operating a VMware ESXi servers.

8 7BLinks & Literature


Co

pyr

igh

t

Sie

me

ns

AG

20

11

All

righ

ts r

ese

rve

d

8 Links & Literature

8.1 Literature

This list is by no means complete and only presents a selection of related references.

Table 8-1

Topic Title

/1/ STEP7 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 Title

\1\ Reference to this document


\2\ Siemens I IA/DT Customer Support

http://support.automation.siemens.com

\3\ Release for Server Virtualization


\4\ WPF Controls for WinCC


\5\ Configuration instruction for integrated working of WinCC in STEP 7.


9 History

Table 9-1

Version Date Modification

V1.0 04/2011 First issue


http://support.automation.siemens.com/�




Documents

Application & Tools - Siemens · PDF file5.2 WinCC Server and one WinCC Client ... – Windows XP or Windows 7 2.2.2 ESX server with WinCC guest systems