WinCC Virtualisation DOC En

7/25/2019 WinCC Virtualisation DOC En

1/55

https://support.industry.siemens.com/cs/ww/en/view/49368181

White Paper 05/2015

WinCC in virtual

EnvironmentsWinCC V7.2, WinCC V7.3 and WinCC Runtime Professional V13
https://support.industry.siemens.com/cs/ww/en/view/49368181https://support.industry.siemens.com/cs/ww/en/view/49368181


2/55

S

iemens

AG2

015Allrightsreserved

This entry is taken from Siemens Industry Online Support. The following Terms ofUse apply:http://www.siemens.com/terms_of_use

Security

informa-tion

Siemens provides products and solutions with industrial security functions that

support the secure operation of plants, solutions, machines, equipment and/ornetworks. They are important components in a holistic industrial securityconcept. With this in mind, Siemens' products and solutions undergo continuousdevelopment. Siemens recommends strongly that you regularly check forproduct updates.

For the secure operation of Siemens products and solutions, it is necessary totake suitable preventive action (e.g. cell protection concept) and integrate eachcomponent into a holistic, state-of-the-art industrial security concept. Third-partyproducts that may be in use should also be considered. For more informationabout industrial security, visithttp://www.siemens.com/industrialsecurity.

To stay informed about product updates as they occur, sign up for a product-specific newsletter. For more information, visit

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

WinCC VirtualizationEntry ID: 49368181, V2.02, 05/2015 2
http://www.siemens.com/terms_of_usehttp://www.siemens.com/terms_of_usehttp://www.siemens.com/terms_of_usehttp://www.siemens.com/industrialsecurityhttp://www.siemens.com/industrialsecurityhttp://www.siemens.com/industrialsecurityhttps://support.industry.siemens.com/cs/%23?lc=en-UShttps://support.industry.siemens.com/cs/%23?lc=en-UShttps://support.industry.siemens.com/cs/%23?lc=en-UShttp://www.siemens.com/industrialsecurityhttp://www.siemens.com/terms_of_use


3/55

S

iemens

AG2


Table of Contents1 Preface ................................................................................................................ 5

1.1

Purpose of the document ..................................................................... 5

1.2 Main contents ....................................................................................... 51.3

Validity .................................................................................................. 5

2 General................................................................................................................ 6

2.1

What is virtualization? .......................................................................... 6

2.1.1 Definition............................................................................................... 62.1.2 Virtualization in detail ........................................................................... 72.2

Difference between client-based and server-based virtualization ....... 7

2.2.1 Client-based virtualization (Type 2: hosted) ......................................... 82.2.2 Server-based virtualization (Type 1: native)......................................... 82.3 Why virtualization ................................................................................. 92.4

What you should know about virtualization ........................................ 10

3

Requirements ................................................................................................... 11

3.1.1

Software for the use of virtualization .................................................. 11

3.1.2

ESX(i) Server (vSphere HyperVisor) .................................................. 12

3.1.3

Guest systems .................................................................................... 12

3.1.4 Related information ............................................................................ 133.2 Procedure for virtualization................................................................. 153.2.1

Creating a virtual machine and transferring it to the server ............... 15

3.2.2 Setting up the virtual network ............................................................. 173.2.3 Creating the virtual switch .................................................................. 183.2.4

Configuring the virtual machine .......................................................... 20

4 Possible Applications ..................................................................................... 22

4.1 Test scenarios and performance data ................................................ 22

4.2

Options of WinCC in virtual environments ......................................... 23

4.2.1

WinCC single-user system ................................................................. 24

4.2.2 WinCC Server and two standard clients ............................................ 274.2.3 Two HyperVisors with two WinCC Clients and each with one

redundant WinCC Server ................................................................... 304.2.4

Summary ............................................................................................ 36

4.3 Options of VMware (vSphere vCenter Server)................................... 374.3.1 VMware functionalities in detail .......................................................... 374.4

Options of Microsoft ........................................................................... 41

5 Optional additional Options............................................................................ 43

5.1 PassThrough (VMDirectPath IO) ....................................................... 435.2 Managed USB HUB ........................................................................... 44

6

Dependencies & Alternatives ......................................................................... 46

6.1 How can I remotely access WinCC stations? .................................... 466.2 Using ASIA dongles for ESX(i) or Hyper-V ........................................ 46

7 Diagnostic Capabilities ................................................................................... 47

7.1

Diagnostics using VMware vSphere Client ........................................ 47

7.2 Diagnostics in the virtual system ........................................................ 49

8

Licensing .......................................................................................................... 51

8.1 Licensing of SIMATIC products .......................................................... 518.1.1

Licensing with a single license ........................................................... 51

8.1.2 Licensing with floating licenses .......................................................... 51

9

Glossary ........................................................................................................... 52



4/55

S

iemens

AG2


10 References ....................................................................................................... 55

11 History............................................................................................................... 55



5/55

1 Preface

1.1 Purpose of the document

CopyrightS

iemensAG2


1 Preface

1.1 Purpose of the document

The aim of this document is to provide an overview of WinCC virtualization. Theobjective is to show appropriate options despite general dependencies. Providingrelevant recommendations and explanations, this document is intended to serve as

a guide.

Virtualization software and technology allow numerous configurations. However,this document focuses on the most useful ones.

1.2 Main contents

Requirements for running WinCC in virtual environments

Possible applications of WinCC in virtual environments

Configurations of virtualization servers

Explanation of VMware functions and the importance in the industrialenvironment (SCADA)

Diagnostics of virtual machines and virtualization servers

1.3 Validity

This document is valid for:

WinCC V7.2

WinCC V7.3

WinCC Runtime Professional V13



6/55

2 General

2.1 What is virtualization?

CopyrightS

iemensAG2


2 General

2.1 What is virtualization?

2.1.1 Definition

In computing, virtualization refers to creating and running virtual (i.e. non-physical)things such as emulated hardware, operating systems, data storage devices ornetwork resources.Therefore, virtualization separates software from hardware.

Figure 2-1; Physical and virtual configuration

Operating System

Application

Operating System

Application

Operating System

Application

Operating System

Application

Operating System

Application

Operating System

Application

PROFINET IE

Hypervisor

OS

Appl.

OS

Appl.

OS

Appl.



7/55

2 General

2.2 Difference between client-based and server-based virtualization

CopyrightS

iemensAG2


2.1.2 Virtualization in detail

Virtual machines are referred to as a virtual instance with a specific hardware

configuration and used with an operating system that can be used for this purpose.

General

The figure below shows the difference between a standard (physical) PC station(left-hand side) and a virtualization server with virtual sessions (right-hand side).

Figure 2-2

Hardware (physical)Hardware (physical resources)

RAM Processors HDD Network

Virtual Sessions

Virtual

Machine

Application

Guest OS

Virtual

Machine

Application

Guest OS

Host OS

Applications

HyperVisor (provides virtual resources)

Virtual

Machine

Virtual

Machine

RAM Processors HDD Network

RAM

Sharing

ProcessorLoad

Sharing

HDD

2.2 Difference between client-based and server-basedvirtualization

General

Basically, there are two types of virtualization, which differ in terms of configurationand structure.



8/55

2 General

2.2 Difference between client-based and server-based virtualization

CopyrightS

iemensAG2


2.2.1 Client-based virtualization (Type 2: hosted)

General

Client-based virtualization means that a client operating system is installed on thephysical platform; an application running one or more virtual clients runs on thisoperating system.

Figure 2-3

App.VM Monitor

(Hypervisor)

Operating system

Hardware

VM VM

ApplicationType 2 Principle Example

Operating system

VMwareWorkstation

Can be run directly

on the PC

2.2.2 Server-based virtualization (Type 1: native)

General

Server-based virtualization means that a server operating system on which no

client application can be run is installed on the physical platform. The operatingsystem, referred to as a HyperVisor by experts, requires fewer resources (as onlythe physical hardware is provided to the VM as a virtual resource); however, it mustat least have the drivers of the physical hardware.

Figure 2-4

Hypervisor

Hardware

VM VMESXi / Hyper-V

Application

VMNo direct input possible,

operation via RDP or VNC

clients.

ExampleType 1 Principle

Operating system



9/55

2 General

2.3 Why virtualization

CopyrightS

iemensAG2


2.3 Why virtualization

Reduction of hardware costs

Cost-effective hardware is possible on the client side.

Expanded areas of application: SIMATIC Thin Client solutions (PC, panels,smart mobile devices).

Reduced hardware costs by consolidating multiple physical computers. (Costreduction due to improved hardware usage.)

Reduction of the time required for service and maintenance

Shorter times for updates and backups as they can be made centrally.

Reduced maintenance costs and time through central administration.

Server configuration using remote management tools.

Increased security

Increased security due to remote access and centralized rights management.

Thin clients are virtually invulnerable to attacks, central protection on the virtualserver.

Increased availability

The hardware on the virtual server can be replaced during operation.1

Increased flexibility

If required, additional clients can be added simply by starting another VMwaresession.

Additional clients for special tasks can simply run in the background:

RDP2/VNC

3solutions for remote or mobile access.

Provision of backup computers as virtual systems. For example, duringmaintenance of a system, a backup system can be used instead.

1When using appropriate virtualization hardware.

2Windows Remote Desktop Protocol: A large number of possible clients is available for various operating systems or

mobile devices. (The server is in the Windows operating system.)3

Virtual Network Computing: Alternative option for remote control of operating systems. (A server is required on theoperating system. Viewing requires a client; clients are also available for various operating systems or mobile devices.)



10/55

2 General

2.4 What you should know about virtualization

CopyrightS

iemensAG2



General

Installing, configuring and managing a virtualization structure - regardless of thesize - requires in-depth knowledge of virtualization systems.

Meaning

When planning a virtualization structure, many factors need to be considered,which can be decisive.

Costs

New structures or existing ones - license costs, hardware costs, administrationcosts always have to be considered in total.

Especially license fees in conjunction with the manufacturer's support contract arenot insignificant and must be included in long-term planning.

The larger the planned structure or the more virtual machines will be used in a

structure, the higher the costs for the required hardware.

For example: The more virtual machines are used, the higher the requirements forthe storage systems and their connection.

Making the best use of small virtualization systems

In the industrial environment, it is not always necessary to build large virtualizationstructures. Mostly, the requirements to be met in the industrial environment are theavailability and operating capability of SCADA systems, stable, uninterrupted

communication and stable archiving of messages and process values.In most cases, small virtualization servers and a small range of functions from thesoftware vendors of virtualization systems are sufficient to achieve this.

Security

Due to the current requirements for security - not only in the office environment, butalso in the industrial environment -, a virtual infrastructure needs to be protected aswell.

Increased security can only be achieved if various virtualization properties andrequirements of the SCADA stations are considered according to the defense indepth strategy.

Note For more information and help on security strategies,

please visit:http://www.siemens.com/industrialsecurity

http://www.siemens.com/industrialsecurityhttp://www.siemens.com/industrialsecurityhttp://www.siemens.com/industrialsecurityhttp://www.siemens.com/industrialsecurity


11/55

3 Requirements


CopyrightS

iemensAG2


3 Requirements

3.1.1 Software for the use of virtualization

Virtualization software

VMware Player or VMware Workstation and VMware Converter

VMware vSphere client

VMware vSphere Server ESX(i)

Microsoft Hyper-V

Note The dependencies that apply to VMware apply in equal measure to Hyper-V.(See Chapter4.3)

SIMATIC software and operating system

WinCC (version depending on the use and release)

Windows operating system (depending on the use)

Windows 2008 Server or Windows 2012 Server

Windows 7 or Windows 8.1



12/55

3 Requirements


CopyrightS

iemensAG2


3.1.2 ESX(i) Server (vSphere HyperVisor)

NOTICE The user and administrator are required to provide and ensure sufficient

system resources on the virtualization server and the virtual systems.

For more information, visit:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003661

and

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2052329

Table 3-1

Properties Requirements

Number of CPU cores The ESX(i) Server requires at least two realCPU cores.

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

CPU load The CPU load system should not permanently exceed a load>75%.

Main memory For secure operation, a 2 GB main memory must bereserved for the ESX(i) Server. (For communication/networkactivities and management of the ESX(i) Server.)

3.1.3 Guest systems

Table 3-2


Number of CPU cores WinCC Server: A WinCC Server guest system requires atleast two logicalCPU cores.

WinCC Client: A WinCC Client guest system requires atleast one logicalCPU core.

The hardware requirements of the respective WinCCsoftware apply that are required as a basis for the

calculation of the number of physical processor cores.

The requirements for the virtual hardware are the same asthe requirements for physical hardware.

Ethernet ports At least 2 physical Ethernet ports are required. One of theseports is for the PLC bus only.

Separation of networks It is recommended to separate terminal, PLC and Windowsnetworks.

CPU load The maximum CPU load of the assigned logical CPU coresmust not exceed 70%-80%.

NoteWhen archiving large data volumes, an appropriate reserveis required in the storage system (high IO load).

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003661http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003661http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2052329http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2052329http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2052329http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2052329http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003661http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003661


13/55

3 Requirements


CopyrightS

iemensAG2



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

(This improves performance.)

Operating states Pausing the guest systems with WinCC installations is notreleased. The guest systems must be treated like realWinCC Servers/Clients.

Hard drive storagemanagement

Do not use Dynamic Memory Control.

(The size of the hard drive file dynamically adjusts to theused capacity.)

NOTICE Please consider the standard requirements for WinCC installations. Theycan be found in the WinCC Release Notes or at the following link.

WinCC 7.2: Installation / Release Notes


WinCC 7.3: General Information and Installation


TIA Portal V13 Professional: SIMATIC WinCC V13 Released for Delivery


Productive use of WinCC in virtual environments

WinCC was compatibility-tested and released for productive use with a HyperVisor

(server-based virtualization).

For testing and commissioning purposes, VMware Player or VMware Workstationcan also be used; however, this is not possible for productive use.

3.1.4 Related information

Optimum operation of ESX(i) Server and VMware

Related information on optimum operation can be found on the VMware support

website:

http://www.vmware.com/support

Released hardware for VMware

A list of the hardware components validated and released by VMware can be foundon the VMware support website:

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

Released hardware for Microsoft Hyper-V

For Microsoft Hyper-V, several technical descriptions have to be considered;however, there is no exact certification list as is the case with VMware.

The following links provide information on the Technical Resources.

http://www.microsoft.com/en-us/server-cloud/solutions/virtualization.aspx

https://support.industry.siemens.com/cs/ww/en/view/37437018https://support.industry.siemens.com/cs/ww/en/view/37437018https://support.industry.siemens.com/cs/ww/en/view/88360672https://support.industry.siemens.com/cs/ww/en/view/88360672http://www.vmware.com/supporthttp://www.vmware.com/supporthttp://www.vmware.com/resources/compatibility/search.phphttp://www.microsoft.com/en-us/server-cloud/solutions/virtualization.aspxhttp://www.microsoft.com/en-us/server-cloud/solutions/virtualization.aspxhttp://www.vmware.com/resources/compatibility/search.phphttp://www.vmware.com/supporthttps://support.industry.siemens.com/cs/ww/en/view/88360672https://support.industry.siemens.com/cs/ww/en/view/37437018


14/55

3 Requirements


CopyrightS

iemensAG2


https://technet.microsoft.com/en-us/virtualization/dd565807.aspx

ESX(i) Server time synchronization

Basically, each ESX(i) Server (single server or multiple servers in a cluster) shouldbe synchronized by a time server.

NOTICE The time of a virtual machine can be synchronized with the ESX(i)-Server'stime using, for example, VMware Tools.

The ESX(i) Server must have the same time source as the guest systems aswhen starting up the guest systems, the host's time (ESXi) is always set first onthe guest system.

This may cause problems if an alternative (second) time source is used inthe guest operating system.

https://technet.microsoft.com/en-us/virtualization/dd565807.aspxhttps://technet.microsoft.com/en-us/virtualization/dd565807.aspxhttps://technet.microsoft.com/en-us/virtualization/dd565807.aspx


15/55

3 Requirements

3.2 Procedure for virtualization

CopyrightS

iemensAG2



Contents

This chapter shows you how to create virtual WinCC systems.

3.2.1 Creating a virtual machine and transferring it to the server

General

Running a virtual machine on a VMware vSphere Server (ESX) requires a numberof preparations. This includes installing the VMware vSphere Server (ESXi) andcreating and transferring the virtual machine(s).

In addition, a management station/PC should be set up where the virtualizationsoftware to be used is installed. You need this software to create, transfer and

manage the virtualization structure.

Note The VMware Workstation software is recommended for creating a virtualsystem.

Make sure not to add or remove unused hardware (e.g., floppy drive, HD audio,shared folders, etc.) when creating a virtual machine.

Alternatively, a virtual machine can also be created directly on the ESX(i)host with the aid of the vSphere Client



16/55

3 Requirements


CopyrightS

iemensAG2


The procedure in detail

No. Step Comment

1. Use the VMware Player or VMware

Workstation to create a virtual machine.

https://www.vmware.com/support/ws55/

doc/newguest_ws.html

2. Install VMware vSphere Server (ESXi). http://kb.vmware.com/kb/2052439

3. Configure VMware vSphere Server(ESXi).

Assign IP address; set administratorpassword

4. Transfer your virtual machine (created inStep 1) to the server using the VMwareStandalone Converter.

Source: virtual machine (local)

Target: VMware infrastructure (server)

(manual:

http://www.vmware.com/products/converter)

Note Depending on the number of internal hard drives or RAIDs, the virtual machines

should be assigned to different data storage components to distribute thewrite/read load accordingly (monitoring of IOPS/data store/HDD).



17/55

3 Requirements


CopyrightS

iemensAG2


3.2.2 Setting up the virtual network

General

The figure below shows how a virtualization server is connected to the surroundingnetworks.

Depending on the requirements, provide an appropriate minimum number ofnecessary network cards.

Figure 3-1

Note Split up the terminal bus and process bus between two physical network cards.



18/55

3 Requirements


CopyrightS

iemensAG2


3.2.3 Creating the virtual switch

The figure below shows a sample configuration with a single VMware vSphere

Server (ESX).It shows three different virtual standard switches (VSS), one for each physicalnetwork adapter.

Figure 3-2, Configuration of the virtual network

Note Network separation:

In this example, the vSphere Server (ESXi) is separated from the terminal busand process bus. The ESX(i) Server can only be accessed via the network card

of the Management Network virtual switch and the associated IP address.


Adding a virtual switch.

No. Step Comment

1. Log on to your VMware vSphere Server(ESXi) with the root user.

Navigate to Inventory, click theConfiguration tab and select Network.

Here you can see the overview of thevirtual switches and physical networkadapters.

2. Open the Add Network wizard.

3. Select the Virtual Machine connectiontype and click Next.

4. Select the physical network adapter to beused for your respective bus type.

5. Repeat steps 1-4 until you have assigneda network card to all bus types.

Terminal bus

Process bus

Redundancy bus



19/55

3 Requirements


CopyrightS

iemensAG2


3.2.3.1 Process communication

The following virtual adapters were compatibility-tested for process communication:

- E1000 virtual adapter

Note Communication via:

VDS (virtual distributed switch, cluster)The VDS was not compatibility-tested for process communication and is therefore notrecommended.See also Chapter5.1 (Simatic Net - notes/releases).

VSS (virtual standard switch, see also Chapter3.2.3)The VSS was compatibility-tested for communication.

For more information, please refer to the SIMATIC NET readme file

or Chapter5.1 (Note).

3.2.3.2 Terminal bus and redundancy bus

The following virtual adapters were compatibility-tested for the terminal bus andredundancy bus:

E1000 virtual adapter

VMXNET3 virtual adapter



20/55

3 Requirements


CopyrightS

iemensAG2


3.2.4 Configuring the virtual machine

General

Using the example of a virtual machine (e.g.: WinCC Server): This VM has twovirtual network cards that are connected to the Terminal Bus virtual switch and

the Process Bus virtual switch.

Figure 3-3


No. Step Comment

1. Log on to your VMware vSphere Server(ESXi) with the root user.

Navigate to Inventory, click theConfiguration tab and select Network.

Here you can see the overview of thevSphere ESX(i) Server.

2. Select the virtual machine you want toconfigure.

3. Select Summary > Edit Settings to openthe settings of the virtual machine.

4. Select the virtual network adapter to beused for your respective bus type.

NoteIf no virtual network adapter exists, selectAdd to add a new one. Refer to the SIMATIC NET release to

see which adapter type is released.

5. In Network Connection, select therespective virtual standard switch (VSS).

6. Repeat steps 1-5 for each virtual networkadapter.



21/55

3 Requirements


CopyrightS

iemensAG2


Note Remove unnecessary virtual hardware such as

HD audio

floppy drive

or similar components.Such virtual hardware may cause problems.



22/55

4 Possible Applications

4.1 Test scenarios and performance data

CopyrightS

iemensAG2



General

The use of virtualization servers (HyperVisors) offers a large range of possibleapplications.

The following chapter shows various configurations of HyperVisors and WinCCstations that were also tested for functionality, performance and plausibility.

The requirements for virtual hardware of a virtual machine do not differ from therequirements for a physical system.

The requirements for WinCC in a virtual environment are the same as the ones fora physical system.

A virtual WinCC station should not feature less hardware than it would feature withthe same project in a physical environment.

Example

PC Virtual machine

Station name WinCC Server

Operating system Server 2012 R2

CPU (2.4 Ghz for eachcore)

4 cores 4 vCores

Main memory At least 4 GB

Disk space Minimum of 10 GB

- for installing WinCC4)

- for working with WinCC5) 6)

Note For related information on the WinCC installation requirements and hardwarerequirements, please refer to the appropriate online help or manual.

4.1 Test scenarios and performance data

Explanation

Each project used in WinCC is different and has different quantity frameworks.

The following project quantity framework was used with WinCC in the optionsshown in this document. It is used as a guide and for reference regarding thehardware used, the number of virtual machines and the configuration of the virtualmachine.

4 During the installation, the drive on which the operating system is installed requires at least 100 Mbytes of free diskspace for additional system files. In most cases, the operating system is installed on drive C:.5 Depending on the project size and the size of the archives and packages. When activating a project, at least

100 Mbytes of free disk space must be additionally available.6 WinCC projects must not be saved to compressed drives or directories.



23/55


4.2 Options of WinCC in virtual environments

CopyrightS

iemensAG2


WinCC quantity framework/project

Criterion Properties

Number of connections to CPUs 2

Number of external S7 tags 128000

Trend archiving 4000 values/second

Alarm archiving 10 messages/second

User Archive 12 data records, each with 4 elements in 5seconds, writing.

Screens 40 screens with: Trend views, alarm view,User Archive Control, screen windows,animated objects, VBS, C scripts

Screen change and screen change toscreens with 12 screen windows (indicatedby the temporary peaks)

At intervals of 20 seconds;

Or different interval as listed in the followingtests.

Determining the performance data of the ESX(i) Server

When monitoring the ESX(i) Server, the following data was logged in the testscenarios:

CPU load in % (MHZ varies depending on the automatic clocking of the CPUor the set power plan)

Active main memory


The following chapter shows in which configurations WinCC could be used invirtual environments.

In addition to the options shown, various presentations and lists are included for

reference and recommendation:

Used hardware of the vSphere Server (ESXi)

Used configuration of the virtual machine

Used network cards

Graphical representation of the server load and the load of the virtual machines



24/55



CopyrightS

iemensAG2


4.2.1 WinCC single-user system

Figure 4-1

4.2.1.1 Hardware used

Component ESX(i) Server 1 IPC 847D

Processor Xeon E3-1268L v3 4 cores/8 threads

2.3 GHz / 3.3 GHz clock frequency with Intel Turbo Boost

8 Mbyte cache

TB, VT-x, VT-d and AMT as enhanced command sets

Main memory 16 GB DDR3 SDRAM (2 x 8 GB), dual channel, ECC;

Hard drives RAID5, 2 TB (3 x 1 TB HDD, striping with parity)removable disk, Hot-Swap, frontside mounted;

Network cards 1 x Onboard 82574L

t2 x Intel PRO/1000GT (1000B ase-T PCI), additionallyinserted.

4.2.1.2 Configuration of virtual machines

Component VM WinCC Server

Processor 4 vCores (1 vSocket)

Main memory 4 GB RAM

Hard drives 250 GB

Network cards 2 x E1000

The network cards were used as follows:

Table 4-1

Network card Use

Onboard 82574L Management network, for example, for vSphere Client access toESX(i)-Server

Intel PRO/1000GT Terminal bus

Intel PRO/1000GT Process bus



25/55



CopyrightS

iemensAG2


4.2.1.3 Network configuration of virtual machines

Figure 4-2, Overview of the vSphere Client network configuration for single-userconfiguration

4.2.1.4 Performance data

Server load Configuration Average in % Maximumin %

CPU 4 cores 33.5 % 62 %

Main memory 16 GB 34 % 34 %



26/55



CopyrightS

iemensAG2


4.2.1.5 Performance data graph

Figure 4-3, Graphical representation of the server CPU usage

Overview of the hardware used

Figure 4-4, Graphical overview of the performance data



27/55



CopyrightS

iemensAG2


4.2.2 WinCC Server and two standard clients

Figure 4-5


Component ESX(i) Server 1 - IPC847D

Processor Xeon E3-1268L v3 4 cores/8 threads

2.3 GHz / 3.3 GHz clock frequency with Intel Turbo Boost

8 Mbyte cache

TB, VT-x, VT-d and AMT as enhanced command sets

Main memory 32 GB DDR3 1600 SD-RAM

Hard drives Adaptec Raid Controller (RAID 5 with hot spare)

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

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


Component WinCC Server WinCC Client 1 WinCC Client 2

Virtual processor 4 vCores 2 vCores 2 vCores

Virtual main memory 4096 MB 2048 MB 2048 MB

Virtual hard drives 250 GB 100 GB 100 GB

Virtual network card 2 x E1000 1 x E1000 1 x E1000


Table 4-2

Network card Use

Onboard 82574L Management network, for example, for vSphere Client access toESX(i)-Server

Intel PRO/1000GT Terminal bus

Intel PRO/1000GT PLC bus



28/55



CopyrightS

iemensAG2



Figure 4-6, Overview of the vSphere Client network configuration in server/client mode

4.2.2.4 Performance data table

Server load Configuration Average in % Maximumin %

CPU 8 vCPU 55 % 100 %




29/55



CopyrightS

iemensAG2


4.2.2.5 Performance data graph

Figure 4-7, Performance data for server/client mode


Figure 4-8



30/55



CopyrightS

iemensAG2


4.2.3 Two HyperVisors with two WinCC Clients and each with oneredundant WinCC Server

Figure 4-9

The figure shows two ESX(i) Servers that were used in the test. Another WinCCClient station could run on the second ESX(i) Server, but this was not implementedin the test.

As this test focuses on redundancy switchover, no automatic screen changes wereimplemented in the test project to show the performance when performing aswitchover more clearly.


Component ESX(i) Server 1 - IPC 847D ESX(i) Server 2 IPC 847D

Processor Intel Xeon E3-1268L v3 4 cores

2.3 GHz / 3.3 GHz

8 Mbyte cache

VT-d and EM64T asenhanced command sets

Intel Xeon E3-1268L v3 4 cores

2.3 GHz / 3.3 GHz

8 Mbyte cache

VT-d and EM64T asenhanced commandsets

Main memory 32 GB DDR3 1066 SD-RAM 16 GB DDR3 1066 SD-RAM

Hard drives 960 GB 930 GB

Network cards 1 x Onboard 82574Lthe only one accepted byVMware.

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

1 x Onboard 82574Lthe only one accepted byVMware.

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


Component VM server VM client 1&2

Processor (vCPU) 4 2

Main memory 4096 MB 2096 MB

Hard drives 90 GB 64 GB

Network cards 3 x E1000 1 x E1000 each



31/55



CopyrightS

iemensAG2



Table 4-3

Network card Use Use

Onboard 82574L Management network, forexample, for vSphere Clientaccess to ESX(i)-Server

Management network, forexample, for vSphere Clientaccess to ESX(i)-Server

IntelPRO/1000GT

Terminal bus Terminal bus

IntelPRO/1000GT

PLC bus PLC bus



32/55



CopyrightS

iemensAG2



Figure 4-10, Network configuration of ESX(i) Server 1 and ESX(i) Server 2



33/55



CopyrightS

iemensAG2


4.2.3.4 Performance data table

Master usage - normal

mode

Configuration Average in % Maximum in %

CPU 4 vCPU 56 % 60 %


Redundancy partner usage

- normal mode


CPU 4 vCPU 52 % 55 %


4.2.3.5 Performance data graph - normal mode

Figure 4-11, Master usage

Figure 4-12, Redundancy partner usage



34/55



CopyrightS

iemensAG2



Figure 4-13, ESX(i) Server 1

Figure 4-14, ESX(i) Server 2



35/55



CopyrightS

iemensAG2


4.2.3.6 Performance data table when redundancy switchover is performed

Master usage - redundancy

scenario


CPU 4 vCPU 73 % 78 %


Slave usage - redundancy

scenario


CPU 4 vCPU 37 % 42 %


4.2.3.7 Performance data graph when redundancy switchover is performed

Figure 4-15, Master usage after redundancy switchover

Figure 4-16, Redundancy partner usage after redundancy switchover

Redundancy scenario

Redundancy scenario



36/55



CopyrightS

iemensAG2


4.2.4 Summary

As can be seen in the above performance charts of the previous options, theredundancy scenario or screen change to screens with a lot of animation, screenwindows, faceplates, etc. requires temporarily increased CPU and main memorycapacity.

This means an appropriate reserve (approx. 25 % CPU, RAM, memory) shouldbe additionally included when planning the hardware of a HyperVisor to avoidunwanted system behavior due to performance bottlenecks.

Note It must be noted that, according to the WinCC hardware requirement, the virtualmachines are assigned at least as much hardware as the physical systems.

If more virtual hardware (e.g., virtual CPUs, vCPU) is assigned to the virtual

machines than exists physically in the host, full load of each VM may cause ahypervisor overload, which can have a negative effect on all virtual systems.



37/55


4.3 Options of VMware (vSphere vCenter Server)

CopyrightS

iemensAG2



General

The options shown in Chapter4.2 can be used with the HyperVisor Serversoftware from VMware vSphere.

Note Ensure compatibility of the VMware vSphere Server (ESXi) versions that wererecommended and compatibility-tested for the WinCC version to be used.

Compatibility information

www.siemens.com/kompatool

Running one or more vSphere Servers (ESXi), single server or multiple servers in acluster, can include different functionalities - depending on the structure andlicensing of the vSphere vCenter Server.

A single vSphere Server (ESXi) has only a few options compared to a cluster withmultiple vSphere Servers (ESXi).

The basis of this document is the smallest possible licensing and the associatedpossible functions.

However, implementing multiple WinCC stations in a new or existing cluster

solution may be planned.

WinCC in the environment of a VMware vSphere vCenter Server cluster involves anumber of dependencies that have to be considered separately in the automationenvironment. For example, the priorities of office applications mostly differ fromthose in the automation environment.

To avoid unwanted system behavior in WinCC, please follow the informationbelow.

4.3.1 VMware functionalities in detail

General

VMware vSphere functionalities offer numerous options to reduce administrative

overhead.

However, these functionalities are designed with a strong focus on officeenvironments, which may cause difficulties in automation.

Please follow the applicable instructions for your virtual infrastructure.

4.3.1.1 Virtual network

An ESX(i) host can have any number of network cards that are available to thevirtual network structure.

https://support.industry.siemens.com/kompatool/pages/main/index.jsfhttps://support.industry.siemens.com/kompatool/pages/main/index.jsf


38/55



CopyrightS

iemensAG2


When using multiple ESX(i) hosts in a cluster7, make sure that the network

configuration of each host is identical.

If a virtual distributed switch is used, the switch simplifies the configuration: Thereis only one central switch that allows you to configure all ESX(i) hosts at the same

time.

Note When using a distributed switch that is used for AS communication of WinCC,make sure that it complies with the requirements and dependencies of therespective SIMATIC NET release. See also Chapter5.1 (SIMATIC NET -notes/releases).

7vSphere vCenter Server is required for creating, configuring, managing an ESX(i) host cluster.



39/55



CopyrightS

iemensAG2


4.3.1.2 vMotion

When running a host cluster, vMotion offers the option to migrate virtual machines

during operation from one physical server (ESXi host) to another withoutdowntimes.

Note Migrating virtual machines with WinCC installed is not released.

The following risks occurred in the compatibility test:

When migrating virtual machines between two ESX(i) hosts, brief interruptions mayoccur. This can have negative effects, for example, on alarm archiving or similarfeatures.

A WinCC Server with an AS OS connection via a PN CP cannot perform hostmigration as the used CP does either not exist on the second host or the CPs PCI IDdiffers from the one originally assigned to the VM.

Virtual machine is slowing down

vMotion operation is interrupted, virtual machine must be restarted.

4.3.1.3 HA High Availability

Monitoring guest operating system failures and reducing downtime throughautomatic restart in the event of an operating system failure.

Automatic restart will only be performed if the guest operating system or the ESX(i)host on which the virtual machine runs fails.

Note This functionality would only be used if the VM itself has already failed (turnedoff) and has no influence on WinCC or if WinCC, too, was accidentally closed.

8

4.3.1.4 FT Fault Tolerance

Provides uninterrupted availability of a VM in the event of a server error.

Note This functionality is not supported by WinCC and was not compatibility-tested.

8

Siemens tests only functions that could influence WinCC. In this case, a compatibility test wasnot performed.



40/55



CopyrightS

iemensAG2


4.3.1.5 vSphere Distributed Resource Scheduler (DRS)

This functionality is included in the vSphere Enterprise and Enterprise Pluseditions.

It provides automated load balancing between all ESX(i) hosts in a vSphere CenterServer cluster.

Together with automatic migrating (moving) of virtual machines between storagelocations and between ESX(i) hosts, this results in optimized performance forESX(i) hosts, data stores and virtual machines.

Among other things, vMotion uses this functionality to relocate virtual machines.

Note It is recommended to allow only semi-automatic mode of the VM.(vMotion is not released while running WinCC)

4.3.1.6 vSphere Storage vMotion

This functionality allows automatic migration of files or virtual machines betweenstorage arrays without interrupting service. It allows you to use storage capacitymore effectively.

Note It is recommended to allow only semi-automatic mode of the VM.(vMotion is not released while running WinCC)

4.3.1.7 Cloning a virtual machine and creating snapshots

Cloning and creating snapshots of a virtual machine is not compatibility-tested and

not released.



41/55


4.4 Options of Microsoft

CopyrightS

iemensAG2



General

The options shown in Chapter4.2 can be used with Microsoft Hyper-V.

Note Ensure compatibility of the Microsoft Hyper-V versions.

Compatibility information

www.siemens.com/kompatool

Brief overview of possible Microsoft Hyper-V configurations:

Hyper-V Server 2012Core server (server-based virtualization)

Figure 4-17 Single Hyper-V host (core installation) and external Hyper-V Manager

PROFINET IE

https://support.industry.siemens.com/kompatool/pages/main/index.jsfhttps://support.industry.siemens.com/kompatool/pages/main/index.jsf


42/55



CopyrightS

iemensAG2


Server 2012 + Hyper-V Manager roleClient-based virtualization9

Figure 4-18

System Center 2012 - Virtual Machine ManagerVirtualization server cluster

management

This software environment provides the option to centrally manage multipleHyper-V hosts and combine them into a cluster.

Note The cluster functionality of VMware also applies to Microsoft Hyper-V.

Hyper-V Live Migration and Cloning Virtual Machines and Creating

Snapshots are not released!

Difference between Microsoft Hyper-V and VMware vSphere

The biggest difference between Microsoft Hyper-V and VMware is themanagement and provision of virtual machines of a Hyper-V system.

To manage and provide virtual machines, a Server at least 2012 R2 operatingsystem is required (similar to the explanation in Chapter3.2).

The Microsoft Hyper-V role or the System Center 2012 software - used tomanage a Microsoft Hyper-V host or cluster - must be installed on the Server 2012.

Note For more information on Microsoft Hyper-V:

https://www.microsoft.com/en-us/server-cloud/products/windows-server-2012-r2/default.aspx

9It is not allowed to install and run WinCC directly on network servers (such as domain

controllers, file and name service servers, routers, software firewalls, media servers, exchange

servers, Hyper-V, etc.).

https://www.microsoft.com/en-us/server-cloud/products/windows-server-2012-r2/default.aspxhttps://www.microsoft.com/en-us/server-cloud/products/windows-server-2012-r2/default.aspxhttps://www.microsoft.com/en-us/server-cloud/products/windows-server-2012-r2/default.aspxhttps://www.microsoft.com/en-us/server-cloud/products/windows-server-2012-r2/default.aspxhttps://www.microsoft.com/en-us/server-cloud/products/windows-server-2012-r2/default.aspx


43/55

5 Optional additional Options

5.1 PassThrough (VMDirectPath IO)

CopyrightS

iemensAG2



5.1 PassThrough (VMDirectPath IO)

General

As VMware vSphere Server (ESXi) supports passthrough, one option is to pass aspecific physical part of the server (in most cases USB or network cards) throughdirectly to a virtual machine.

The virtual machine automatically detects the new hardware (it may be necessaryto install appropriate drivers). When passthrough has been successfully configured,the HyperVisor can no longer access the part of the hardware that is passed

through.

In this case, the hardware passed through the HyperVisor to the VM is part of thevirtual machine, along with the rest of the virtual hardware.

Various SIMATIC NET CPs were, among other things, compatibility-tested and canbe used in virtual environments using passthrough.

Note For information on the passthrough configuration:

http://kb.vmware.com/kb/1010789

http://kb.vmware.com/kb/1010789http://kb.vmware.com/kb/1010789http://kb.vmware.com/kb/1010789


44/55


5.2 Managed USB HUB

CopyrightS

iemensAG2


Note When using SIMATIC NETCPs in virtual environments, make sure that theycomply with the requirements and dependencies of SIMATIC NET.

Make sure to use the correct SIMATIC NET version for the respectiveSIMATIC WinCC version.

The appropriate readme file lists the specific requirements anddependencies that need to be considered.

Information in the SIMATIC NET V12 SP2 readme file

SIMATIC NET DVD V12 + SP2 Released for Delivery.


Information in the SIMATIC NET V12 SP1 readme fileSIMATIC NET DVD V12 + SP1 Released for Delivery.


Information in SIMATIC NET V13 (incl. readme file)SIMATIC NET DVD V13 Released for Delivery


Information in SIMATIC NET V12SIMATIC NET DVD V12 Released for Delivery


Information in SIMATIC NET 8.2SIMATIC NET DVD V8.2 Released for Delivery


Installation, Configuration of SIMATIC NET CPs in a VMware vSphere Server(ESXi)SIMATIC NET PC Software SIMATIC NET PC Software V13 Installation Manual

Chapter 3 and 4


5.2 Managed USB HUB

The principle

The figure below illustrates how the USB HUB is connected to a virtualinfrastructure.

The Ethernet LAN is used to connect the USB HUB to the virtual machine.

In order to assign a USB port to a virtual machine, it is first necessary to configurethe USB HUB via the HUBs WEB interface.

Furthermore, each virtual machine to connect to the USB HUB requires appropriatesoftware. This software allows them to access the respective USB ports (portgroups). The USB devices connected to these ports are passed on to therespective VM via the Ethernet LAN.

https://support.industry.siemens.com/cs/ww/en/view/91112041https://support.industry.siemens.com/cs/ww/en/view/109346876https://support.industry.siemens.com/cs/ww/en/view/109346876https://support.industry.siemens.com/cs/ww/en/view/78822814https://support.industry.siemens.com/cs/ww/en/view/77377602https://support.industry.siemens.com/cs/ww/en/view/77377602https://support.industry.siemens.com/cs/ww/en/view/78822814https://support.industry.siemens.com/cs/ww/en/view/109346876https://support.industry.siemens.com/cs/ww/en/view/91112041


45/55


5.2 Managed USB HUB

CopyrightS

iemensAG2


Note A guide showing the detailed configuration of the USB HUB is available on themanufacturers website:

http://www.digi.com/products/usb/anywhereusb#docs

http://www.digi.com/products/usb/anywhereusb#models

Figure 5-1

VM

VM VM VM VM

VM VM VM VM

Ethernet LAN

AnywhereUSB

Remote Client

SmartCard

USB Device

RealPort USB

software drivers

The following USB HUBs were compatibility-tested:

http://www.digi.com/products/usb/anywhereusb

http://www.digi.com/products/usb/anywhereusb%23docshttp://www.digi.com/products/usb/anywhereusb%23modelshttp://www.digi.com/products/usb/anywhereusb%23modelshttp://www.digi.com/products/usb/anywhereusbhttp://www.digi.com/products/usb/anywhereusbhttp://www.digi.com/products/usb/anywhereusbhttp://www.digi.com/products/usb/anywhereusb%23modelshttp://www.digi.com/products/usb/anywhereusb%23docs


46/55

6 Dependencies & Alternatives

6.1 How can I remotely access WinCC stations?

CopyrightS

iemensAG2


6 Dependencies & Alternatives

6.1 How can I remotely access WinCC stations?

To remotely access WinCC stations, you have the following options:

VNC (Real VNC)

RDP (Remote Desktop Protocol) -

vSphere Client

Note The dependencies of RDP in conjunction with a WinCC station have to beconsidered separately.

For more information on the subject, please refer the FAQ How can you

access WinCC stations remotely?:


6.2 Using ASIA dongles for ESX(i) or Hyper-V

Passthrough

One option is to use the passthrough option described in Chapter5.1.

The number of ASIA dongles depends on the number of int. USB hubs and not onthe number of USB ports (only an entire USB HUB can be passed through at atime).

Note Microsoft Hyper-V 2012 or 2008 does not support passthrough.

USB HUB

For the use of one or more ASIA dongles, the managed USB hub describedinChapter5.2 was tested for compatibility.

https://support.industry.siemens.com/cs/ww/en/view/78463889https://support.industry.siemens.com/cs/ww/en/view/78463889https://support.industry.siemens.com/cs/ww/en/view/78463889


47/55

7 Diagnostic Capabilities

7.1 Diagnostics using VMware vSphere Client

CopyrightS

iemensAG2




General

Using the vSphere Client, you can not only configure the virtual machines (guestsystems), but you can also monitor the ESX(i) Server and the individual virtualmachines (guest computers).

Monitoring options

Various trend displays are possible in the vSphere Client:

Main memory usage

Operating state

CPU load

Hard drive

Network utilization


Table 7-1

No. Step/action

1. Log on to the ESX(i) Server

Start your VMware VSphere Client.The Logon dialog appears.

Enter the IP address of your virtualization server and your user data.The vSphere Client starts.

2. Navigate to ESX(i) Server diagnostics

In the navigation tree, select the top item. (The virtualization server.)

Then select the Performance tab.A diagram appears that shows the performance data graph.

3. Customizing diagnostics of the ESX(i) Server

To monitor the values used for these measurements, proceed as follows:

In the top area of the tab, click Trend settings.The Adjust performance trend dialog appears.

Monitoring the RAM

In the Trend settings tree, expand the RAM item.

In RAM, click Realtime.

In the Performance logs fields, deselect everything and select onlyactive.

Confirm with OK.In the diagram, you can now monitor the active RAM.

Monitoring the CPU load

In the Trend settings tree, expand the CPU item.

In CPU, click Realtime.

In the Performance logs field, deselect everything and select onlyusage.

Confirm with OK.In the diagram, you can now monitor the CPU load.

4. Navigate to diagnostics of the virtual system



48/55



CopyrightS

iemensAG2


No. Step/action

In the navigation tree, select the item of the virtual system to be monitored.

Then select the Performance tab.A diagram appears that shows the performance data graph.

5. Customizing diagnostics of the virtual system

To do this, proceed as described in Step 3.



49/55


7.2 Diagnostics in the virtual system

CopyrightS

iemensAG2



The Windows operating system provides a diagnostics tool: Windows Performance

Monitor


Table 7-2

No. Step/action

1. Starting the toolClick Start > Run....The Run... dialog appears.

Enter Perfmon and click OK.The monitoring tool starts.

2. Customizing the performance logsIn the bottom right area, remove all performance logs.

In this area, right-click. In the menu, select Add performance logs ....

The Add performance logs dialog appears.

To display the CPU load as a percentage, select the Processor data objectand select the % Processor Time performance log. Select _Total as theinstance.

Click Add.

To display the main memory allocation, select the Memory data object and

select the Committed Bytes data object.



50/55



CopyrightS

iemensAG2


No. Step/action

Click Add and select Close to close the dialog.

Note

It is a problem to display both values simultaneously in one diagram. The axisscaling differs.

For optimum display, adjust the scaling using the Properties button and theGraphics tab.



51/55

8 Licensing

S

iemens

AG2


8 Licensing

General

All products/software must be licensed in accordance with the manufacturer'slicense terms and terms & conditions.

8.1 Licensing of SIMATIC products

General

In terms of licensing, a SIMATIC software installation on a virtual machine does notdiffer from the installation on a real machine. Therefore, each SIMATIC softwareinstallation on a virtual machine, e.g. SIMATIC WinCC and other SIMATICapplications, must be licensed accordingly.

Likewise, each SIMATIC WinCC Client installation on a virtual machine must belicensed accordingly.

8.1.1 Licensing with a single license

Unlimited duration standard license that can be transferred to any computer andused on this computer. The Certificate of License (CoL) defines the type of use.Licenses of the single license can only be used locally.

8.1.2 Licensing with floating licenses

Unlimited duration license that can be transferred to any computer and used on thiscomputer. The license can also be obtained from a license server over the network.

Note The freedom virtualization has brought involves the risk of easily running ordestroying created virtual machines. When things get serious, a virtual machinewill be irretrievably lost, including all installations and licenses.

To minimize the risk of losing licenses, use a license server with SIMATICfloating licenses. This additionally facilitates handling licenses.



52/55

9 Glossary

S

iemens

AG2


9 Glossary

ESX(i)

Product from VMware. The software has/is its own operating system and providesvirtual systems with workspace. The software is used for virtualization on the

server side.

Core installation

Operating system installation without a graphical user interface; replaced by a

simplified platform such as a CMD command prompt or PowerShell.

Guest

Equivalent tovirtual system.

Host

The host for virtual machines, regardless of whether this refers to the host fordesktop or server virtualization. In this document, host is equivalent to virtualization server.

Hyper-V This software environment is provided by Microsoft through different paths and

allows the user to provide, manage and run virtual machines on a Windows server

or core server.

HyperVisor

Software for virtualization (of a virtualization server).

Hyper-threading

Technology for better processing of commands for the processor. Withhyper-threading, one processor core appears as 2 process cores to the operatingsystem.

IOPS

Input/Output Operations per Second.

Management station

A PC that performs the configuration, maintenance and monitoring of one or morevirtualization servers.

The VMware Converter or vSphere Client applications can be used in this context.

RDP

Remote Desktop Protocol is a Microsoft solution for operator control andmonitoring of remote computers.

SCADA

SCADA stands for Supervisory Control and Data Acquisition.

VDS

Virtual Distributed Switch



53/55

9 Glossary

S

iemens

AG2


Virtualization server (and virtual system)

The real PC on which the VMware ESX(i) software runs that provides its resourcesto virtual systems.

Computers that run within the VMware ESXi software are virtualized systems.

Virtual hardware

Real resources are not directly provided to the virtualized systems to allow shareduse.

Such shared hardware can be network cards, processor cores or hard drives. This

hardware can be used partially and jointly by all virtualized systems.

Virtual processor core

A processor core provided to the virtual machine.

A vCPU is not equivalent to a pCPU or pCore. A vCPU also includes the doublecores due to HT. In addition, VMware does not distinguish between the core andthe CPU; this is only relevant to the guest system.

Virtual network

A network which only exists within a virtualization server and allows communication

between multiple virtual systems (within one virtualization server).

VNC

Virtual Network Control is an option for operator control and monitoring of remotecomputers.

VMware

Company and vendor of virtualization software.

VMware vCenter Converter

A VMware product for converting, transferring and creating virtual systems.

VMware Workstation

A VMware product for creating and using virtual systems on existing operatingsystems.

vSphere Client

A VMware product for configuring, monitoring and running a VMware ESXi Server.

vSphere Server

A VMware product that is installed on the server hardware. Also known as aHyperVisor, VMware ESX(i) Server or ESX(i) host.

vSphere vCenter Server

A VMware product that is used in order to manage multiple ESX(i) HyperVisorsusing a vSphere Client.

The vSphere VCenter Server is used to combine multiple ESX(i) hosts into acluster, which increases effectiveness based on the available functionality.



54/55

9 Glossary

S

iemens

AG2


VSS

Virtual Standard Switches



55/55

10 References

S

iemens

AG2


10 References

Internet links

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

Table 10-1

No. Subject Title

\1\ Siemens IndustryOnline Support

https://support.industry.siemens.com

\2\ WinCC 7.2 manual: Installation / Release Noteshttps://support.industry.siemens.com/cs/ww/en/view/37437018

\3\ WinCC 7.3 manual: General Information and Installationhttps://support.industry.siemens.com/cs/ww/en/view/102777629

\4\ TIA Portal V13Professional

product note: SIMATIC WinCC V13 Released for Deliveryhttps://support.industry.siemens.com/cs/ww/en/view/88360672

\5\ Compatibility Tool www.siemens.com/kompatool

\6\ Product note SIMATIC NET DVD V12 + SP2 Released for Deliveryhttps://support.industry.siemens.com/cs/ww/en/view/98163617

\7\ Product note SIMATIC NET DVD V12 + SP1 Released for Deliveryhttps://support.industry.siemens.com/cs/ww/en/view/91112041

\8\ Product note SIMATIC NET DVD V13 Released for Deliveryhttps://support.industry.siemens.com/cs/ww/en/view/109346876

\9\ Product note SIMATIC NET DVD V12 Released for Deliveryhttps://support.industry.siemens.com/cs/ww/en/view/78822814

\10\ Product note SIMATIC NET DVD V8.2 Released for Deliveryhttps://support.industry.siemens.com/cs/ww/en/view/63098071

\11\ Manual: SIMATIC NET PC Software SIMATIC NET PC Software V13

Installation Manualhttps://support.industry.siemens.com/cs/ww/en/view/77377602

\12\ FAQ How can I remotely access WinCC stations?https://support.industry.siemens.com/cs/ww/en/view/78463889

\13\ VMwareKnowledge Base

http://kb.vmware.com

\14\ Microsoft Support http://support.microsoft.com

11 HistoryTable 11-1

Version Date Modifications

V1.0 04/2011 First version

V2.0 05/2015 Second version
https://support.industry.siemens.com/https://support.industry.siemens.com/https://support.industry.siemens.com/cs/ww/en/view/37437018https://support.industry.siemens.com/cs/ww/en/view/37437018https://support.industry.siemens.com/cs/ww/en/view/102777629https://support.industry.siemens.com/cs/ww/en/view/102777629https://support.industry.siemens.com/cs/ww/en/view/88360672https://support.industry.siemens.com/cs/ww/en/view/88360672https://support.industry.siemens.com/kompatool/pages/main/index.jsfhttps://support.industry.siemens.com/cs/ww/en/view/98163617https://support.industry.siemens.com/cs/ww/en/view/98163617https://support.industry.siemens.com/cs/ww/en/view/91112041https://support.industry.siemens.com/cs/ww/en/view/91112041https://support.industry.siemens.com/cs/ww/en/view/109346876https://support.industry.siemens.com/cs/ww/en/view/109346876https://support.industry.siemens.com/cs/ww/en/view/78822814https://support.industry.siemens.com/cs/ww/en/view/78822814https://support.industry.siemens.com/cs/ww/en/view/63098071https://support.industry.siemens.com/cs/ww/en/view/63098071https://support.industry.siemens.com/cs/ww/en/view/77377602https://support.industry.siemens.com/cs/ww/en/view/77377602https://support.industry.siemens.com/cs/ww/en/view/78463889https://support.industry.siemens.com/cs/ww/en/view/78463889https://support.industry.siemens.com/cs/ww/en/view/78463889https://support.industry.siemens.com/cs/ww/en/view/77377602https://support.industry.siemens.com/cs/ww/en/view/63098071https://support.industry.siemens.com/cs/ww/en/view/78822814https://support.industry.siemens.com/cs/ww/en/view/109346876https://support.industry.siemens.com/cs/ww/en/view/91112041https://support.industry.siemens.com/cs/ww/en/view/98163617https://support.industry.siemens.com/kompatool/pages/main/index.jsfhttps://support.industry.siemens.com/cs/ww/en/view/88360672https://support.industry.siemens.com/cs/ww/en/view/102777629https://support.industry.siemens.com/cs/ww/en/view/37437018https://support.industry.siemens.com/

WinCC Virtualisation DOC En

Documents

Transcript of WinCC Virtualisation DOC En