Technical Information

(1)

Information

TI 30A01A10-01E

(2)

(3)

Preface

This document is to be used as a guideline for applying virtualization to Yokogawa IA system products.

Virtualization is a technique for running multiple logical computers on one physical computer to reduce the number of computers.

This document describes how to apply virtualization to an OTS (operator training system) and a real plant system.

This document is suitable for readers who have basic knowledge of: • Plant Instrumentation Systems.

• Information technology (IT) including the computer, networking, security, etc.

• Yokogawa’s industrial automation systems (e.g. CENTUM VP, ProSafe-RS, Exa Series software packages).

n

Drawing conventions

Some drawings may be partially emphasized, simplified, or omitted, for the convenience of

description.

n

Trademark

• CENTUM, ProSafe, Exaopc, Exaquantum, Exapilot, Exasmoc, Exarqe, Exaplog, FAST/ TOOLS, and PRM are registered trademarks of Yokogawa Electric Corporation.

• OmegaLand is a registered trademark of Yokogawa Electric Corporation and Omega Simulation Co.,Ltd.

• VMware is a trademark or registered trademark of VMware, Inc. in the United States and other countries.

• All other company and product names mentioned in this document are trademarks or registered trademarks of their respective companies.

• Yokogawa does not use TM or ® marks to indicate those trademarks or registered trademarks in this document.

(4)

n

Glossary

The following table describes words and terms commonly used in this document.

Table Words and terms

Term Description

ENG CENTUM VP Engineering Station FCS CENTUM VP Field Control Station

Guest OS Operating System running on a virtual machine HIS CENTUM VP Human Interface Station

Hypervisor A method of implementing virtualization software that runs directly on the _{hardware independently of the operating system} NIC Network Interface Card

OPKB CENTUM VP Operation Keyboard OS Operating System of a computer OTS Operator Training Simulator/System Physical Server A server computer that exists physically

Real Environment An environment where the computer running the operating system is the actual physical computer or an environment which is composed of physical computers only

SCS ProSafe-RS Safety Control Station SENG ProSafe-RS Safety Engineering Station

SSH (Secure Shell)

A protocol to safely communicate with a remote computer using cryptographic and authentication technologies where every network communication including authentication of a password for example, is to be encrypted.

Server Virtualization A technique for dividing a single physical server into multiple logical servers Thin Client A client terminal implementing just the minimum necessary functions for the _{user to connect to and use a server} Virtual Disk Storage used by a virtual machine

Virtual Environment An environment where the computer running the operating system is _{implemented as a virtual machine} Virtual Machine A machine with the actual physical computer running the operating system _{implemented virtually by software} Virtualization Environment An environment with the same computer configuration as a real environment _{implemented in a virtualization server} Virtualization Server A physical server with the virtualization software installed

Virtualization Software Software for dividing physical resources such as the CPU, memory, and network resources of a physical server and assigning them to virtual machines

Virtualization Technology Software technology independent of the actual physical hardware for virtually implementing the same functions and services as the physical hardware

VM Abbreviation for ‘Virtual Machine’

(5)

Virtualization Guideline for

Yokogawa System Products

CONTENTS

1.

Overview of Virtualization ... 1-1

1.1 What is Virtualization?...1-1 1.2 Merits of Virtualization ...1-3 1.3 Concerns for Virtualization ...1-3

2.

Target Products for Virtualization... 2-1

2.1 Target Products ...2-1 2.2 Target System ...2-2 2.3 Virtualization System ...2-4

3.

Operating Environment of a Virtualized System ... 3-1

3.1 Hardware Requirements ...3-1

3.1.1 Virtualization Server (ESXi Host) ...3-1 3.1.2 Management Client ...3-8 3.1.3 Centralized Management Server ...3-8 3.1.4 HMI Client ...3-9 3.1.5 Peripheral Devices ...3-9 3.2 Software Requirements ...3-10 3.2.1 Virtual Machine ...3-10 3.2.2 Virtualization Server ...3-10 3.2.3 Management Client ... 3-11 3.2.4 Centralized Management Server ... 3-11 3.2.5 HMI Client ...3-12 3.2.6 Concerns for Operating Yokogawa Products ...3-12

3.2.7 Concerns for the Virtualization Server Management...3-13

4.

Guidelines for Considering a Virtualization System ... 4-1

4.1 Virtualization System Viewed from RAS Viewpoints ...4-1

4.1.1 Reliability ...4-1 4.1.2 Availability ...4-2 4.1.3 Serviceability ...4-3 4.1.4 Performance ...4-3

4.2 Improved Reliability in Virtualized Systems ...4-4

4.2.1 Availability ...4-4

(6)

4.3 Examples of Virtualization System used for Yokogawa Products ...4-6

4.3.1 Operator Training System (OTS) ...4-6 4.3.2 Real Plant System ...4-7

4.4 Allotting Resources to Virtual Machines ...4-8 4.5 Implementation Considerations ...4-10

4.5.1 Virtualization Target Considerations ...4-10

4.5.2 Estimating the Hardware Resources of the Physical Server ...4-10

4.5.3 Peripheral Devices ...4-13 4.5.4 Time Synchronization ...4-14 4.6 Other Information ...4-15 4.6.1 Licenses ...4-15 4.6.2 Support Contract ...4-16

5.

Implementation Procedure ... 5-1

5.1 Setup Preparation ...5-2 5.1.1 IP Address ...5-2 5.1.2 Administrator Account and Password ...5-2 5.1.3 Virtualization Software ...5-2 5.1.4 Centralized Management Server Software ...5-3 5.1.5 Other Software ...5-4

5.2 ESXi Host Implementation ...5-5

5.2.1 Hardware Setup ...5-5 5.2.2 Installing VMware ESXi ...5-8

5.2.3 Configuring the Management Network ...5-16

5.3 Setting up a Management Client ...5-25

5.3.1 Installing VMware vSphere Client ...5-25 5.3.2 Installing Tera Term ...5-29

5.4 Setting up the ESXi Host ...5-34

5.4.1 Adoption of License ...5-34 5.4.2 Time Settings ...5-38 5.4.3 ESXi Host Security Settings ...5-41

5.5 Setting up a Virtual Machine Environment ...5-49 5.5.1 Virtual Network Settings ...5-49

5.6 Setting up a Centralized Management Server ...5-57 5.6.1 Virtual Network Settings ...5-57 5.6.2 Deploying the vCenter Server ...5-60 5.6.3 Activating vCenter Server ...5-67 5.6.4 vCenter Server Security Settings...5-78

5.7 Managing ESXi Host with vCenter Server ...5-86

5.7.1 Application of license ...5-86 5.7.2 Registration of ESXi Host ...5-89

(7)

5.8 Setting up the Guest OS ...5-96

5.8.1 Creating the Virtual Machine...5-96 5.8.2 Installing the Guest OS ...5-107 5.8.3 Installing the VMware Tools ... 5-115

5.8.4 Configuring the Guest OS ... 5-118

5.9 Setting up Yokogawa Products ...5-126

5.9.1 Installing Yokogawa Products ...5-126 5.9.2 Settings after Installing Yokogawa Products ...5-131

5.10 Setting up the HMI Client ...5-132

5.10.1 Setting up the Wyse TCX Suite ...5-133 5.10.2 Wyse T10 Setup...5-139 5.10.3 Setting up a Windows PC ...5-141

5.11 Operation Checks ...5-141

5.11.1 Checking the Connection between the HMI Client and Guest OS ...5-141

5.11.2 Check Yokogawa Product Startup ...5-141

6. Operation ... 6-1

6.1 Backup/Restore ...6-1 6.2 Security ...6-2 6.2.1 Guest OS Security ...6-2 6.2.2 Hypervisor Security ...6-2 6.2.3 Client Security ...6-3 6.2.4 Virtual Appliance Security ...6-4

6.3 Applying the Virtual Machine Technology ...6-5

6.3.1 Snapshots ...6-5 6.3.2 Clones ...6-5

6.4 Performance Management ...6-6 6.5 Updating Virtualization Software ...6-7

7. Maintenance ... 7-1

7.1 Startup and Shutdown of the Virtualization Server ...7-1

7.1.1 Virtualization Server Startup Procedure ...7-1 7.1.2 Virtualization Server Shutdown Procedure ...7-2

7.2 Changing the Virtual Machine Configuration ...7-5 7.3 Using an External Storage Device ...7-8

7.3.1 USB Device ...7-8 7.3.2 Optical Drives ...7-17

7.4 Acquiring Performance Information ...7-20 7.5 Acquiring Virtualization Server Logs ...7-23 7.6 Operating the ESXi Shell ...7-24 7.7 Executing a Backup or Restore ...7-25 7.8 Using the vSphere Web Client ...7-30

(8)

7.8.2 Setting up the WEB Browser ...7-31 7.8.3 Logging in to vCenter Server ...7-31

7.9 Adding VMkernel Port for Time Synchronization of ESXi Host ...7-33 7.10 Using Windows OS as an NTP Server ...7-40

(9)

1.

Overview of Virtualization

1.1

What is Virtualization?

Virtualization is a technique used to make a single piece of physical hardware look like multiple pieces of logical hardware or multiple pieces of physical hardware look like a single piece of logical hardware. Well-known examples of the virtualization technique include server virtualization, desktop virtualization, storage virtualization, and network virtualization. This document describes the YOKOGAWA IA system which uses the server virtualization technique.

l

Server Virtualization

Server virtualization is a technique used to divide the hardware resources of a single physical server into multiple logical resources using virtualization software. A virtual hardware environment created using the logical resources is called a virtual machine, and an operating system installed on the virtual machine is called the guest OS.

Computer performance enhancements and the advancement of virtualization enables multiple virtual machines to on a single physical server. This allows hardware resources, different operating systems and applications to run independently from each other.

l

Virtualization Software

A variety of software is currently available for the virtualization technique. Since they all have their advantages and disadvantages, there is a need to select the appropriate virtualization software according to the virtualization purpose.

Virtualization software for virtualizing servers is classified into two types according to the

implementation method: Host and Hypervisor. They have features such as those described in the following table.

Table 1-1 Comparison of Virtualization Software Characteristics of the

virtualization software Host Hypervisor

Host OS Required Not required Software manageability Easy Need knowledge Resource control of the physical

server Overhead is big Overhead is small Scale of intensity Small scale Large scale Virtualization machine performance Low, not stable High, stable

This document describes how to configure server virtualization using hypervisor virtualization

(10)

Hypervisor App. Guest OS Virtual Machine App. Guest OS Virtual Machine App. Guest OS Virtual Machine NIC CPU Memory Disk Hardware Physical Server F010101.ai

Figure 1-1 Server Virtualization (Hypervisor type)

Physical Server NIC CPU Memory Disk Hardware App. Guest OS Virtual Machine App. Guest OS Virtual Machine Host OS Application Virtualization Software F010102.ai

(11)

1.2

Merits of Virtualization

One of the advantages of virtualization is the ability to reduce the user’s total cost of ownership (TCO) as described below.

l

Reducing the Number of Physical Servers

Multiple virtual machines can be created on a single physical server and the hardware resources can be utilized. In addition, operating systems can be run independently on virtual machines, reducing the number of physical servers. Costs are also reduced by lowering the footprint and power consumption.

l

Reducing the Management Costs

Maintenance and other management costs can be lowered by reducing the number of physical servers. Power consumption can also be reduced.

l

Reducing the Lifecycle Costs

Since virtualization software exists between the physical server hardware and each OS, the relationship between the software (guest OSs and applications) and hardware is loose. A smooth migration to a new physical server from an old one is possible without updating the software. As a result, the maintenance costs can be reduced.

l

Easy Backup and Restoration

All virtual machine data is handled as files, facilitating easy backup. Furthermore, since

dependence on the physical server hardware is low, restoration can be performed quickly in the event of a failure or disaster. Productivity can be improved by reducing the downtime of the system.

1.3

Concerns for Virtualization

The following issues must be considered when introducing virtualization.

l

Initial cost

Hardware or a client device with superior specifications, virtualization software, and a Windows

license not bundled with the computer itself are required for virtualization. The initial cost can be higher than using non-virtualization.

l

Influence upon Virtualization Server Failure

Multiple systems are integrated within a single server, thus when hardware fails it may cause

significant influences over the entire system. These influences may be reduced by taking

measures in system configuration, but cannot be fully eliminated. For details, refer to Chapter 4 -

Guidelines for Considering a Virtualization System.

l

Performance

Virtualization enables emulation to be performed without using hardware, which may slow down the server performance, such as screen display speed.

(12)

2.

Target Products for Virtualization

This chapter describes Yokogawa IA system products that support virtualization and the application range.

A virtualization applicable range differs depending on the real plant system and operator training system (OTS). Even in the real plant, virtualization is available for a component which is not directly connected with a control bus (Vnet/IP).

2.1

Target Products

The following table shows the Yokogawa system products that are compatible with virtualization.

Table Target Products for Virtualization

Product Release No. Model Name Software Name Operator Training System Real Plant System CENTUM VP R5.03.00 or later LHS1100/LHM1101,

etc. Standard Operation and Monitoring Function, other HIS software Yes – LHS5100/LHM5100,

etc. Standard Builder Function, other ENG software Yes – LHS5420/LHM5150 Test Function Yes – LHS5425

LHS5426 LHS5427

Expanded Test Functions FCS Simulator Package

HIS Simulator Package Yes –

ProSafe-RS R3.02.00 or later

CHS5100 Safety System Generation and Maintenance _{Function Package} Yes – CHS5200 CENTUM VP/CS 3000 Integration _{Engineering Package} Yes – Exaopc R3.71 or later NTPF100 OPC Interface Package Yes – Exaquantum R2.80 or later NTPP001, etc. Plant Information Management System Yes Yes Exapilot R3.96 or later NTPS200 Operation Efficiency Improvement Package Yes Yes Exasmoc R4.03.20 or later NTPS410 Multivariable Optimising Control Package Yes Yes Exarqe R4.03.20 or later NTPS420 Robust Quality Estimator Package Yes Yes Exaplog R3.40 or later NTPS100 Event Analysis Package Yes Yes FAST/TOOLS R10.01 or later RVSVRN-S11-SA, etc._{HMIWEB-S11-001, etc.} Windows Server Package_{Web-HMI Server Package} – Yes

PRM R3.12 or later SSS7700 SSS7710 SSS7740 SSS7780 PRM Server PRM Client

PRM Advanced Diagnosis Server PST Scheduler Package

– Yes

OmegaLand V2.5SP3 or later Visual Modeler, etc. _(*1) Integrated Environment for Dynamic _Simulation Yes – Exatif R5.03.00 or later LOM9001 (*1) DCS Connection Interface for Training _Simulator Yes –

(13)

2.2

Target System

This Section describes examples of Yokogawa IA system configuration using virtualization.

n

Operator Training System (OTS)

Virtualization is applicable to an OTS using the expanded test functions of CENTUM VP or ProSafe-RS and the Exa series target products shown in Section 2.1.

The following Figure shows a typical OTS example.

HMI Client - CENTUM VP

ENG/HIS

Management Client - VMware vSphere Client

Virtualization Server (ESXi Host)

Virtualization Server (ESXi Host) OmegaLand - Visual Modeler - EXEC - DB - ITK Exaquantum - PIMS Server - Web Server Exatif

- Link Software Lib CENTUM VP - Builder Func. - Test Func. - Expanded Test Exatif - FCS Interface CENTUM VP - FCS Simulator Exatif - HIS Interface CENTUM VP - Standard O&M - HIS Simulator Exaopc - OPC Server HMI Client - Exaquantum Client HMI Client - OmegaLand Operation RDP Network

RDP Network Management NetworkManagement Network

Hypervisor (VMware ESXi)

F020201.ai

Figure 2-1 Example of OTS Using Virtualization

For details on an operator training system using the test functions of CENTUM VP, refer to the following GSs.

• GS 33K10D50-50E LHS5420 Test Function

• GS 33K10D60-50E LHS5425, LHS5426, LHS5427 Expanded Test Functions, FCS Simulator Package, HIS Simulator Package

(14)

n

Real Plant System

Virtualization is applicable to a real plant system using the Exa series, PRM and other target products shown in Section 2.1.

The following Figure shows a typical Real Plant system example.

Management Client - VMware vSphere Client - SSH Client

- WEB Client

Exaopc - OPC Server

Virtualization Server (ESXi Host) Exaquantum - PIMS Server - Web Server PRM - Field Communication Server

Hypervisor (VMware ESXi)

CENTUM VP / HIS - Standard Operation & Monitoring Function

Control Network (Vnet/IP)

Management Network Centralized Management Server - vCenter Server PRM - Device Management Server Exaquantum - Explorer Client - Web Client PRM - Device Management Client CENTUM VP / FCS - Control Function for Field Control Station Application Network (Ethernet)

F020202.ai

(15)

2.3

Virtualization System

Yokogawa has adopted the VMware vSphere as the virtualization software approved for Yokogawa system products as other competitor products resulted in failures during the evaluation tests.

The components that will make up the virtualization system are described below.

l

Virtual Machine

In an environment without virtualization, this component would itself exist as a single computer. In virtualization, it refers to the combination of a guest OS that runs on the virtualization server and the software that runs within the guest OS.

l

Virtualization Server

This is the physical server on which the virtualization software and virtual machine are run. Multiple virtual machines can be run on one virtualization server.

The virtual server in which VMware vSphere was installed is called an ESXi host.

l

Management Client

This is the PC used to manage the virtualization server (ESXi host) over the network. The virtualization server is accessed via a vSphere Client running on the PC.

l

Centralized Management Server

This is the server in which VMware vCenter Server is installed. The introduction of this server to a virtualization environment enhances the management/monitoring function provided for virtualization software.

l

HMI Client

This is the terminal which works as a Human Machine Interface (HMI) of the software on a virtual machine. It connects via a Remote Desktop Protocol (RDP) network.

A thin client (dedicated client device) needs to be provided or a PC compatible with Windows 7 or later.

l

Virtual Network

A virtual network is a software-based network configured in a virtualization server. The virtual

network connects between a virtual machine and a physical NIC, or among virtual machines, and it consists of a virtual NIC and a virtual switch. The virtual switch is connected to an external physical network via the physical NIC connected to it. The virtual machine on the virtual network can be operated in the same way as if connected to the conventional physical network.

(16)

F020301.png Figure 2-3 Virtual Network

l

USB Redirection

The function to connect an USB device connected to an HMI client’s USB port with the virtual machine via a network is called USB Redirection. For this function, the USB Redirection Software has to be installed on the guest OS of the virtual machine where the USB devices are connected.

F020302.png Figure 2-4 USB Redirection

(17)

3.

Operating Environment of a

Virtualized System

3.1

Hardware Requirements

3.1.1

Virtualization Server (ESXi Host)

l

Virtualization Server Models

A VMware adaptable computer is required for use as a virtualization server. An HP or Dell server computer based on Intel CPU is recommended.

Please refer to the following VMware Compatibility Guide, and select the server in this list. • http://www.vmware.com/resources/compatibility/search.php

If the latest model is not found at the above website, please contact the server vendor.

l

Requirements for the Virtualization Server

Software for virtualization to be installed on the server has to be determined prior to defining the virtualization server specifications.

Required hardware specifications differ by Yokogawa products and related software. The virtualization server specifications must fulfill all requirements.

Hardware resources required for Yokogawa products are described below. The calculation method and technique for determining the virtual server are described in Chapter 4.

The hardware resources used were contained in each product’s GS as of August 31st, 2014. To obtain the latest hardware resources, refer to the current product(s) GS. Hardware resources were determined from each GS by using the following rules:

• CPU

The frequency is the same numeric value as described in the GS and the number of cores is 2 times that described in the GS. This is true if the hyper-threading function of a virtualization server is enabled. If the hyper-threading function is disabled, the number of cores needs to be estimated at half.

• Video memory

If the GS describes graphics specifications such as CRT resolution and display color then

the video memory capacity is 128MB or more. In other cases, the memory capacity is 8MB or more.

• Essential and recommended resources

If the GS describes both essential and recommended hardware resource values, the recommended values are used.

• OS

If hardware resource values differ between operating systems, the numeric values of Windows 7 and Windows Server 2008 R2 are used.

(18)

• Disk

The disk space shown in each table is the amount of free disk space required to install the product. The amount of space required to store the data used by the product needs to be estimated separately.

n

CENTUM VP

l

ENG Station

Resources Requirements

CPU 4 cores or more, at least 2.93 GHz (for Windows Server OS)_{4 cores or more, at least 2.13 GHz (for Windows Desktop OS)} Memory At least 8 GB (for Windows Server OS)_{At least 6 GB (for Windows Desktop OS)}

Video memory At least 128 MB Disk At least 50 GB

l

FCS Simulator

Resources Requirements

l

HIS Simulator

Resources Requirements

Video memory At least 128 MB Disk At least 50GB

n

ProSafe-RS

l

SENG Station

Resources Requirements

CPU 4 cores or more, at least 2.93 GHz (for Windows Server OS)_{4 cores or more, at least 2.13 GHz (for Windows Desktop OS)} Memory At least 4 GB

Video memory At least 128 MB Disk At least 50GB

(19)

l

SCS Simulator

Resources Requirements

n

Exaopc

Without the CAMS for HIS Support function (NTPF100-S1/S3/SB)

Resources Requirements

With the CAMS for HIS Support function (NTPF100-S6)

Resources Requirements

n

Exaquantum

l

PIMS Server

Resources Requirements

CPU (*1) Less than 20,000 tags: 20,000 to 50,000 tags: 4 cores, at least 2.13 GHz4 cores, at least 3.00 GHz More than 50,000 tags: 8 cores, at least 3.00 GHz

Memory (*1) (*2)

Less than 20,000 tags: At least 4 GB (till Windows Server 2008 R2) (ditto) At least 8 GB (from Windows Server 2012) 20,000 tags or more: At least 6 GB (till Windows Server 2008 R2)

(ditto) At least 10 GB (from Windows Server 2012) Video memory At least 8 MB

Disk At least 10 GB

*1: The requirements for the PIMS server for Exaquantum vary by the volume of the data.

*2: When the PIMS server and Web server coexist (combined server), sum the required memory sizes. It is not need to add the memory for clients.

(20)

l

Web Server

Resources Requirements

CPU 4 cores, at least 2.13 GHz Memory (*1) At least 2GB

*1: When the PIMS server and Web server coexist (combined server), sum the required memory sizes. It is not need to add the memory for clients.

l

Client

Resources Requirements

CPU 2 cores, at least 2.0 GHz Memory (*1) At least 2 GB

*1: When the PIMS server and Web server coexist (combined server), sum the required memory sizes.

n

Exapilot

Resources Requirements

CPU 4 cores, at least 2.66 GHz Memory At least 2 GB

n

Exasmoc

l

APC Server

Resources Requirements

l

Web Server

Resources Requirements

(21)

l

Client

Resources Requirements

n

Exarqe

l

APC Server

Resources Requirements

l

Web Server

Resources Requirements

l

Client

Resources Requirements

n

Exaplog

Resources Requirements

(22)

n

FAST/TOOLS

l

SCADA Server

Resources Requirements

l

Web-HMI Server

Resources Requirements

l

Web-HMI Client

Resources Requirements

n

PRM

l

PRM Server

Resources Requirements

CPU (*1) 2 cores, at least 1.00 GHz (300 units or less)2 cores, at least 2.80 GHz (1000 units or less) 4 cores, at least 2.80 GHz (3000 units or less) Memory (*2) At least 2 GB (for Windows Server OS)_{At least 4 GB (for Windows Desktop OS)} Video memory At least 128 MB

Disk (*2) At least 6 GB (300 units or less)At least 8 GB (1000 units or less) At least 13 GB (3000 units or less)

(23)

l

PRM Client

Resources Requirements

CPU (*1) 2 cores, at least 1.00 GHz

Memory (*2) At least 2 GB (for Windows Server OS)_{At least 4 GB (for Windows Desktop OS)} Video memory At least 128 MB

Disk (*2) At least 2 GB

l

PRM Advanced Diagnosis Server

Resources Requirements

l

Device Diagnosis Data Historian Server

Resources Requirements

l

PST Scheduler Server

Resources Requirements

(24)

l

PST Scheduler Client

Resources Requirements

Disk (*2) At least 1 GB

*1: If multiple resources are installed together, select a resource that requires the highest specification among those resources.

*2: If multiple resources are installed together, sum the capacities of each resources.

n

OmegaLand

Resources Requirements

CPU 4 cores or more, at least 2.13 GHz Memory At least 2 GB

3.1.2

Management Client

The management client sets up and manages the virtualization server via a network using VMware dedicated software (vSphere Client). The setting up of this component is not always necessary because it is used just for management. For a security and management operation, a notebook PC can also be used. Select a management client that meets the following condition:

• PC running Windows 7 or later

3.1.3

Centralized Management Server

A Centralized Management server is a server to enhance the management/monitoring function provided for virtualization software, using the VMware-dedicated software (VMware vCenter Server). This server uses a physical server on which Windows Server OS operates or a

virtualization server as one of virtual machines. Hardware requirements differ depending on the number of virtualization servers or virtual machines to be managed. To select a server that meets the requirements, refer to VMware vCenter Server Installation Manual “Installation and Setup of vSphere” at:

• https://www.vmware.com/support/pubs/vsphere-esxi-vcenter-server-pubs.html

l

Physical Server

• Server computer on which a 64-bit Windows Server OS operates

• For details about other requirements, refer to the VMware manual described above.

l

Virtualization Server

• Server computer on which the VMware vSphere ESXi host operates

(25)

3.1.4

HMI Client

An HMI client is a device for operation and monitoring of the software installed in the virtualization machine via a network. A Windows PC or a dedicated Thin Client can be used as the HMI client. The followings describe the hardware requirement:

l

PC:

• Windows 7 or later

l

Thin Client:

• T10 from Wyse Technology Inc.

3.1.5

Peripheral Devices

n

OPKB

An OPKB may be used with the operation monitoring function (HIS) of CENTUM VP. In this case,

a USB connection type OPKB should be prepared. Specifically, the following models can be

used: • AIP827

• AIP830/AIP831

The HMI client using AIP830 or AIP831 as the OPKB needs to have at least two available USB ports.

n

Sound

Hardware for playing sound needs to be installed on the HMI client.

n

Multiple Monitors

The HMI client needs to meet the following requirements. • Compatible with multiple monitors

• Capable of displaying a resolution of 1280x1024 or better on each screen

n

USB Hardware Key

A hardware key for a network license is necessary to use OmegaLand. The key will connect to a USB port on a virtualization server.

(26)

3.2

Software Requirements

3.2.1

Virtual Machine

l

OS

The software executing environment for Yokogawa system products apply to the Guest OS on the virtual machine. If the client uses multiple monitors, Windows Server 2008 R2 has to be used as the Guest OS.

l

Software products

The same software environment is required for each software product in a virtual implementation as in the real environment.

l

Additional Virtualization Software

To use an OPKB connected to a HMI client for HIS, software capable of USB redirection is required.

• Wyse TCX Suite 5.1 or later

This software has to be installed on the Guest OS of HIS.

l

Patch Software

• CENTUM VP R5.03.xx Patch

This patch software is required when using the HIS test function installed in the guest OS of Windows Server 2008 R2 from the HMI client connected via the remote desk top.

This patch was applied by CENTUM VP R5.04. • Microsoft KB2927767

Applying this patch to the guest OS is suggested when the HMI client connected via the remote desk top is used for audio playing.

This patch is automatically installed in CENTUM VP R5.04 or later.

3.2.2

Virtualization Server

l

Virtualization software

• VMware vSphere 5.5 Standard

This software is the first to be installed on the ESXi host to configure hypervisor type

virtualization system.

(27)

3.2.3

Management Client

l

Virtualization server management software

This software monitors, maintains, and sets up the virtualization server for the VMWare vSphere 5.5 virtualization software. It is divided into two types by the interface format as the following:

• VMware vSphere Client 5.5

This is the software that operates on the Windows OS. To use this software, install it in the Management Client. This software is essentially required in the initial stage of system construction.

• VMware Web Client 5.5

This software is the Web interface of the virtualization server centralized management software VMware vCenter Server. To use this software, an Web browser and Adobe Flash

Player needs to be installed first in the Management Client. For information on the Web

browser type and version and Adobe Flash Player version, refer to the following. [VMware vSphere Documentation] - [vSphere Installation and Setup Guide] https://www.vmware.com/support/pubs/vsphere-esxi-vcenter-server-pubs.html

The VMware vSphere Client is essentially required. The VMware Web Client is also required essentially for a virtualization system in which to set up the centralized management server.

l

SSH Connection Software

This is the software for use in case of problems the Virtualization Server Management software cannot remedy or system maintenance. To use this software, install it in the Management Client.

• Tera Term 4.83 or later

This is a terminal emulator to be connected from a management client to a virtualization server with SSH.

3.2.4

Centralized Management Server

l

Virtualization Server Centralized Management Software

• VMware vCenter Server 5.5

This is the software for automating the operation/management of virtual machines and ESXi host, setting the availability function and centralizing management of multiple virtualization servers. To use this software, install it in the Centralized Management server.

The Windows version and virtual appliance version are provided for VMware vCenter Server software. The Windows version is compatible with every scale system, but rather a package for a large-scale system (a few thousand VMs or more). This virtual appliance version is oriented for a system of middle scale or less (1000VMs or less). This version is also an all-in package where an OS and software have been set up, thus being easy to introduce and manage and advantageous in cost reduction. Therefore, the virtual appliance version is used for the virtualization of the Yokogawa IA system due to the scale of system and usability of software.

(28)

3.2.5

HMI Client

A Windows PC or a dedicated thin client can be used as an HMI Client. The followings describe the software environment.

l

PC

• Windows 7 SP1 32bit/64bit or later • Windows Server 2008 R2

l

Thin Client

• Wyse ThinOS 8.0

3.2.6

Concerns for Operating Yokogawa Products

Concerns for using Yokogawa products in the virtualization environment are described as follows:

l

CENTUM VP

• When an HIS is used, the following limitations are applied. 1) Panel set does not function.

2) Execution function from the scheduler will not be implemented. 3) Sequence message request (%RQ) cannot be implemented. 4) A window cannot be displayed for calling up other HIS windows.

5) When a new message is generated, the message window is not automatically displayed.

• When an HIS is used, an adoption of an OPKB is recommended. Select the OPKB as the destination for output buzzer sounds.

l

Exapilot

• When the remote desk top is connected, the task bar icon does not blink, but will light up upon receiving a new message.

• VoiceExe2 for Exapilot cannot be used because it fails to output a sound.

l

OmegaLand

• OmegaLand software, with the standard software license, cannot be launched from the remote desk top. OmegaLand has to be launched from the management client which directly accesses the VM on the virtualization environment.

(29)

3.2.7

Concerns for the Virtualization Server Management

Accumulated data may be lost or data display stop when the following actions are taken while Yokogawa products are in operation on the virtualization server. Ensure that Yokogawa products are stopped prior to implementing them, or implement them under conditions that data loss or

display stop do not influence the operation.

• Creation of a new virtual machine • File uploading to the data store (*1) • Execution of clone/snapshot

(30)

4.

Guidelines for Considering a

Virtualization System

This Chapter provides guidelines for building a virtualization system.

A real plant system requires a high degree of availability as a control system, thus the high reliability of the system becomes increasingly important. There needs to be a system

configuration study taking the above into account, even if using the virtualization technology. However, some system configuration may be difficult to implement due to the virtualization

technology.

Since an OTS is not a real control system but a simulation system, it may not require a system

configuration that achieves high availability.

As guidelines to evaluate computer system performance, viewpoints of RAS (Reliability, Availability and Serviceability) are commonly used. The next Section describes the characteristics of a virtualization system from RAS viewpoints.

4.1

Virtualization System Viewed from RAS

Viewpoints

Individual viewpoints of RAS, they will be ‘minimum failure occurrence’, ‘continued operation with minimum effect after failure occurrence’ and ‘fastest recovery from failure’, respectively.

4.1.1 Reliability

It can be considered that a virtualization system improves reliability more than a real environment. The following describes reliability for both the software and hardware.

n

Software

Software failure means ‘User requirements/needs are not met’, notifying the user of software perfection level. A virtualization system requires 3 pieces of software, namely a Guest OS, Yokogawa System Product, and Virtualization Software. A virtualization environment also uses the same programs of Guest OS and Yokogawa System Product as used in a real environment. As a result, this system seems to have the same level of software perfection as that in a real environment. VMware vSphere Virtualization Software is a tried-and-true technologie for Server Virtualization and has a large track record in real environments. As long as Yokogawa has implemented in-company tests, vSphere is the software that meets the needs most satisfactorily and seems to have a high level of perfection. However, vSphere has little track record when used for a control system, thus having some possibilities of encountering unexpected problems.

n

Hardware

A basic strategy to reduce hardware failure is to use high-reliability components and reduce the number of hardware components. In server virtualization, the frequency of hardware failures has reduced thanks to “use of a higher-reliability server machine than a PC” and reduction of the number of PCs through integration. It is also considered that a Thin Client has a lower failure rate than a PC used as an HMI client.

(31)

4.1.2 Availability

The probability of occurrence of the event where the whole system halts due to server failure increases steadily in server virtualization, compared with that in a real environment. The graph in Figure 4-1 shows the probability of occurrence of the event where the whole system function stops. It shows the calculation results of event probability in systems with 3 PCs and 10 PCs in use respectively and the system that has adopted server virtualization. It is clear that the difference in probability increases as the number of integrated PCs increases.

0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1 1 0.8 0.6 0.4 0.2 0

Event Probability of System Halt

3 PCs all failure

Server 10 PCs all failure

PC Failure Rate

Event Probability of System Halt

F040101.ai

Figure 4-1 Image of Event Probability of Virtualization System Halt

Consequently, there is a need to reduce system halt time upon system operation. Common measures against this are as follows.

• Eliminate the period until time to replace spare parts through hardware redundancy. • Reduce time to detect a system malfunction.

• Reduce time to switch to a backup system.

• Reduce time to restore the system from backup data.

(32)

4.1.3 Serviceability

The distributed physical PCs can be integrated in a virtualization server using the Server Virtualization technique. This allows control target physical PCs to be reduced in number and brought into uniform management. There will need to begin management/monitoring of virtualization layers such as the virtual machine and hypervisor. Under server virtualization, the user cannot directly view PCs, network, etc. physically existing in a real environment, since they

are configured in a virtualization server just like software. For this reason, it is important that the system administrator must fully grasp the whole plant system configuration and be familiar

with the architecture of virtualization software in addition to the conventional knowledge of real environments.

n

Management/Monitoring/Diagnostics

Various types of sensors are mounted on the hardware of physical servers. The system monitors the hardware using these sensors. The system administrator can gain information such as resource state and performance status from virtualization layers by comprehensively monitoring the information. As the number of virtualization servers increases and the integration quantity becomes massive, there will be a need to select and introduce software to aid these monitoring tasks.

n

Server Replacement

A virtual machine is encapsulated and independent of the virtualization server hardware. Thus, a shift to a new server or restoration from a backup is easily made. A current server can also be replaced easily with an alternative.

n

Software Maintenance

A virtualization server and virtual machine can be remotely managed using a management client. The clone/snap technology of a virtual machine can also be used for reducing administrator’s workload.

4.1.4 Performance

Various pieces of hardware are emulated as software in a virtualization system. Screen transfer or mouse/keyboard operation of a virtual machine is always performed through an HMI client via the network. Consequently, screen drawing performance and operability in the HMI environment are inferior to those in a real environment where real hardware operates.

(33)

4.2

Improved Reliability in Virtualized Systems

This Section introduces measures to improve virtualization reliability.

4.2.1 Availability

The following will improve availability.

n

Measure 1 - Hardware Failure

When using server virtualization, all virtual machines that use redundant hardware can receive

the benefits of redundancy. There is no need to change any applications, including the guest OS,

before and after implementing redundancy. Use hot-swappable hardware, if available. Examples include:

• Hot swappable disks with RAID (RAID 1 or RAID 1+0 is recommended)

• Hot swappable dual configuration power supply

• Use of ECC memory.

n

Measure 2 - Server Failure due to Hardware Life

The probability of server failure due to hardware usage can be reduced by replacing the

hardware within its expected life. At the time of replacement, virtualization software maintenance can be performed. A server is commonly provided with a mechanism that manages hardware status. Examples include the periodic replacement of the:

• Cooling fans • Power units • Disks

• Solid State memory, if used.

n

Measure 3 - System Halt Time Reduction

<<Currently under study>>

n

Measure 4 - Reduce Unexpected Troubles

Implement backup procedures to deal with non-redundant hardware and accidental failures. Examples include:

• Store backup data within a redundant external network-link storage device. It can be

difficult to restore data to a standby system when using a disk(s) in the physical server of a

virtualization server.

• If using a UPS, each virtual machine (vMA) is required to run a UPS agent program. If a power outage results in the UPS being used then the virtualization server will be shut down via this agent as the UPS power begins to fail.

(34)

4.2.2 Serviceability

The following measures will improve serviceability.

n

Measure 1 - Understanding System Conditions

Performance and event logs for hypervisor and virtual machines are useful for checking the state of the virtualization system daily and isolating individual problems in a physical server.

To understand the condition of a virtualized server, consider the installation of a vCenter Server. Virtualization layers information would be collected within the vCenter Server database to provide an alarm mechanism to continually monitor the collected data, allowing the administrator to be informed of changes in virtualization layer state and any event occurrences.

The information provided is futher enhanced if used in combination with monitoring mechanisms (hardware and software) provided with the virtualized server.

n

Measure 2 - System Restoration onto Alternative Server

A virtual machine is encapsulated and independent of the virtualization server hardware. When

restoring the system to an alternative server, the physical server hardware specification must

be identical to the failed server. A virtual machine can be restored onto multiple distributed virtualization servers.

n

Measure 3 - Recovery from an Operating Error

If a system error occurs during a software patch, application work, guest OS or Yokogawa IA product update, etc, the use of a clone or snapshot to restore the system to its pre-operation state can be used.

(35)

4.3

Examples of Virtualization System used for

Yokogawa Products

This Section shows examples of systems implemented to apply virtualization to Yokogawa products.

4.3.1

Operator Training System (OTS)

Figure 4-2 shows an example of an OTS implemented with one virtualization server and Figure 4-3 shows an OTS implemented with two virtualization servers.

RDP Network

F040301.ai

ENG/SENG OmegaLand

PlantSimulator

VMKernel APP Network

Management Network

Hypervisor

HMI Client (PC or Thin client) Management Client

(vSphere Client) OmegaLand_View-PC _SimulatorHIS FCS/SCS_Simulator HMI Client for HIS(Thin client)

OPKB

L2SW Virtual Machine Virtualization Server

Virtual Switch

Figure 4-2 Example of OTS Implemented with One Virtualization Server

RDP Network ENG/SENG OmegaLand PlantSimulator VMKernel APP Network Management Network Hypervisor Virtual Machine Virtual Switch Virtualization Server HMI Client (PC or Thin client) Management Client

(vSphere Client) OmegaLandView-PC SimulatorHIS FCS/SCSSimulator

HMI Client for HIS (Thin client) OPKB L2SW Exaopc Exaquantum VMKernel Exapilot Exasmoc/Exareq F040302.ai

Figure 4-3 Example of OTS Implemented with Two Virtualization Servers

Both of these examples are composed of HMI clients and a virtualization server(s) to allow easy

replacement of an operator training system. Each system has confi guration that concentrates

(36)

4.3.2

Real Plant System

The following fi gures show examples in which virtualization is applied to a real plant system.

Management Client (vSphere Client)

RDP Network HMI Client

(PC or Thin client) PRM Client PRM Server Exaquantum Server Exaquantum Client Exaopc HIS FCS APP Network Management Network Vnet/IP Virtual Machine Virtual Switch L2SW Virtualization Server Ethernet vCenter Server Hypervisor Hypervisor VMkernel VMkernel Data Store Field Communications Server F040303.ai CS

Figure 4-4 Example of Real Plant System Confi guration Using Exaquantum and PRM

Management Client (vSphere Client) RDP Network HMI Client (PC or Thin client) FAST/TOOLS - SCADA Server - Web HMI Server

STARDOM APP Network Management Network Hypervisor Virtual Switch L2SW Virtualization Server Ethernet Control Network (Ethernet) FAST/TOOLS - Web HMI Client Virtual Machine vCenter Server Hypervisor VMkernel VMkernel Data Store F040304.ai M

Figure 4-5 Example of Real Plant System Confi guration Using FAST/TOOLS

• Yokogawa IA system products used in direct connection with the control bus (V net or Vnet/ IP) are not targeted for virtualization.

• The introduction of vCenter Server allows constant collection and long storage of performance data of virtualization layers, thus increasing serviceability.

(37)

• The client products in the Yokogawa IA system individually require a monitor, and therefore

may not receive a great benefit from integration.

• The system stores data (ESXi configuration information, virtual machine clone in the

power-off state) into a network-linked data storage and a local disk in the virtualization server that is used as simple backup data.

4.4

Allotting Resources to Virtual Machines

This Section describes important points to be considered when allocating hardware resources to virtual machines in order to run Yokogawa products in a virtualized environment.

Virtualization software is designed to use the hardware of the physical server as effectively as possible. There is therefore the possibility that the resources available for a certain machine

will be insufficient because of the operating state of another virtual machine. To guarantee

the operation of Yokogawa products on a virtual machine, it is necessary to ensure that the virtual machine has the necessary resources. Be sure to allocate the hardware resources for the corresponding Yokogawa products contained in Chapter 3 (Operating Environment of a Virtualized System) to the virtual machine.

n

CPU

Allocate the number of cores shown in the hardware requirements to the virtual machine. Also specify [Reservation] of CPU resource allocation to ensure that the resources are allocated to the virtual machine. The frequency to set is calculated as follows.

(CPU reservation frequency) = (CPU frequency) x (Number of cores) ÷ 2 Use the CPU frequency and number of cores shown in the hardware requirements.

If the frequency of the CPU installed in the physical server differs from the CPU frequency shown in the hardware requirements, change the number of cores to allocate to the virtual machine as follows.

(Preliminary number of cores) = (CPU reservation frequency) ÷ (Frequency of CPU of physical server)

Obtain the required number of cores by multiplying by a coefficient depending on whether

hyper-threading (HT) of the physical server is enabled or disabled and is to be rounded up. When HT is enabled: (Number of cores) = (Preliminary number of cores) x 2 When HT is disabled: (Number of cores) = (Preliminary number of cores)

Example: When the required CPU resources are 3.00 GHz and 4 cores, the CPU frequency of the physical server is 2.8 GHz, and HT is enabled

(CPU reservation frequency) = 3.00 GHz x 4 cores ÷ 2 = 6000 MHz (Preliminary number of cores) = 6000 ÷ 2800 = 2.14

(Number of cores) = 2.14 × 2 = 4.28 → 5 (rounded up)

n

Memory

Allocate the memory size shown in the hardware requirements to the virtual machine. Also specify [Reserve all guest memory (All locked)] to ensure that the resources are allocated to the virtual machine.

(38)

n

Video Memory

Allocate the video memory size shown in the hardware requirements to the virtual machine.

n

Storage

There are three format types available for a virtual disk.

Type Description

Thin provisioning Enables expanding just the used portion of the disk area until it reaches _{the maximum capacity because space is allocated on demand.}

Thick provisioning

Lazy Zeroed The specified space is allocated when the virtual disk is created. The data remaining on the physical disk is not deleted during creation, but is deleted on demand at a later time when the virtual machine writes. Eager Zeroed The specified space is allocated and the data remaining on the physical disk is zeroed out when the virtual disk is created. It may take longer to

create disks in this format.

For the disk format of a virtual machine that will run Yokogawa products, specify thick

provisioning (eager zeroed) to secure the area to be used in advance and zero format the target area. Securing the area before use ensures that the disk area resources are available. The disk area resources can also be secured before use with thick provisioning (lazy zeroed) but it is recommended thick provisioning (eager zeroed) is used because of the advantages in terms of performance.

(39)

4.5

Implementation Considerations

This Section describes important points to be considered with regards to estimating the hardware

specifications of the virtualization server implementing the system and the related devices.

4.5.1

Virtualization Target Considerations

Take the following steps when defining a virtualization server. 1. Decide which products to be virtualized.

Refer to Section 2.1 for the applicable Yokogawa Products and their release numbers that are compliant with virtualization.

2. Confirm if the hardware resources (CPU, memory, video memory, hard disk capacity) of the applicable product are sufficient for virtualization. Refer to Section 3.1.1 for the required hardware resource of Yokogawa products.

3. Finalize the CPU specifications, memory capacity, and hard disk capacity in accordance with Sections 4.4 and 4.5.2.

4. Finalize the required number of network ports in accordance with the guideline described in Section 4.5.2.

5. Find a server machine suitable for virtualization that fulfills the above conditions. 6. In the case of a server that satisfies the required hardware resources, the virtualization

server has to be divided.

4.5.2

Estimating the Hardware Resources of the Physical

Server

This Section describes the estimating of hardware resources for the physical server for implementing the virtualization server. Estimate the hardware resources for the physical server based on the hardware resources investigated in Section 4.5.1 (Virtualization Target Considerations) as required for each Yokogawa product to be virtualized.

n

CPU

Calculate the sum of CPU reservation frequencies of all the Yokogawa products that work on a virtualization server, compare the CPU resources of the physical servers, and select a CPU that satisfies the CPU reservation frequency.

l

If only Yokogawa products are installed on a server

Σ [CPU reservation frequency of Yokogawa Products] x 1.25 < [CPU resource]

l

If Yokogawa products and vCenter Server are installed on the same server

(Σ [CPU reservation frequency of Yokogawa Products] + 4 GHz) x 1.25 < [CPU resource] For instance, when an ENG station and an FCS simulator are working on virtual machines respectively;

ENG Station: 3.00 GHz x 4 cores / 2 = 6.00 GHz FCS Simulator: 3.00 GHz x 4 cores / 2 = 6.00 GHz

(40)

VMware’s overhead has to be taken into consideration for configuring the virtualization server,

which is equivalent to 25% of the Yokogawa products.

Therefore, multiply 1.25 to the sum of the CPU reservation frequency calculated above. 12.00 x 1.25 = 16.00 GHz

Find a server machine with the CPU resource higher than the above value from the computer vendors in the market.

The CPU resource is calculated as follows:

[CPU resource] = [CPU frequency - in GHz] x [No. of cores] x [No. of CPUs]

For instance, the CPU resource for a server machine with frequency 2.60 GHz and 8 cores is calculated as:

2.6 GHz x 8 cores = 20.8 GHz

In this case, a server machine with this CPU specification can be selected.

n

Memory

In a virtual environment, it is possible to assign a memory size that is larger than the size of the physical memory installed in the physical server to a virtual machine. However, to guarantee the operation of Yokogawa products, that virtual machine needs to have the memory available for use.

Calculate the total memory size required to run the nodes (Yokogawa products) on one virtual server. Then add the memory size used by Hypervisor to that total. The physical server just needs enough memory to cover this total value.

l

If only Yokogawa products are installed on a server

[the physical server’s memory size] ≥ 6 GB + Σ[Yokogawa product’s memory size] + Σ[Yokogawa product’s video memory]

l

If Yokogawa products and vCenter Server are installed on the same server

• Virtual machine (*1): 100 pieces or less

[the physical server’s memory size] ≥ 14 GB + Σ [Yokogawa product’s memory size] + Σ [Yokogawa product’s video memory]

• Virtual machine (*1): 100 to 1500 pieces

[the physical server’s memory size] ≥ 22 GB + Σ [Yokogawa product’s memory size] + Σ [Yokogawa product’s video memory]

(41)

n

Disk

Calculate the total disk size required to run the nodes (Yokogawa products) on one physical server. Then add the disk size used by virtualization software to that total. The physical server just needs enough disk space to cover this total value. Furthermore, the disk (storage) device is the slowest device in the hardware resources. Care is required concerning equipment selection and virtual machine placement. Consider selecting a high-speed serial attached SCSI (SAS)

hard disk drive and a fast RAID configuration.

The following shows the disk capacity the virtualization software requires. Disk size for Hypervisor] = 8 GB

[Disk size for virtual machine management] = 100 GB + 2 × Σ [memory size] + N × Σ [Disk size] (*1)(*2)

[Disk size for vCenter Server] = 160 GB

*1: Memory size and disk size indicate the memory capacity and disk capacity of each Yokogawa product. Each capacity is summed for the number of virtual machines to be created.

*2: N represents the maximum number of times a snapshot runs.

n

Network Card

For a network card (NIC) to be installed on a physical server for virtualization, provide one Ethernet card (minimum of 1 Gbps) so that it can collectively manage NICs of multiple virtual machines. In order to prevent the network overloading, segregation of network into three

categories is recommended. In such cases, select the kinds and quantity of NICs to have three or more physical LAN ports.

1. Management Network for the virtualization server

The management network is a network to manage the virtualization server. In the case where the network is overloaded and information management of the virtualization server cannot be performed, segregation from other networks is recommended.

2. APP Network for application data communication

The APP network is a data exchange network among the virtual machine, Yokogawa products and other applications. This is equivalent to the Ethernet communication network

in the real environment. In order to avoid influences from other networks, segregation from

other networks is recommended.

3. RDP Network for connecting virtual machines to HMI clients.

In the virtualization system, the guest OS is operated on the virtual machine via network. In

order to avoid the network overloading by the HMI client and/or influences caused by 1 or 2,

(42)

Management Network APP Network RDP Network F040501.ai HMI Client (RDP Client) Management Client (vSphere Client) Virtualization Server (ESXi host) VMKernel Hypervisor (ESXi) Physical hardware Virtual Machine Virtual Machine

Figure 4-6 Example of Network Card Usage

Figure 4-6 shows an example of a PC using three NIC with one LAN port; however, an NIC with multiple LAN ports is also available in the market.

4.5.3

Peripheral Devices

This Section provides important details regarding the peripheral devices used in the system.

n

HMI Client

A display cannot be connected to a virtual machine on a virtualization server. Therefore, an HMI client connected via a network is required to perform operation and monitoring while viewing the screens of Yokogawa products on a virtual machine. HMI client terminal types include not only ordinary PCs but also thin client terminals. There is a need to determine which type of client terminal is appropriate based on things like security, installation location, and function requirements of the client terminal.

n

Multiple Monitors

To use multiple monitors with the HMI client, the hardware of the client terminal needs to support multiple monitors and the guest OS of the virtual machine that the client will connect to needs to be Windows Server 2008 R2.

n

OPKB

For using a device which is USB-connected to the HMI client on the guest OS, the input/output signals of the USB device must be transmitted via a network. Multiple editions of software to enable such transmittal is available in the market; however, performance of the software is not

always guaranteed. The use of the software verifi ed by Yokogawa is recommended. When the

applied software, other than the one that Yokogawa recommended, does not function properly, contact each software vendor for technical support.

(43)

n

Printer

It is recommended using a network printer be used.

n

UPS

A UPS is recommended to protect the physical server implementing the virtualization server from power failures, lightning surges, and other power problems. Unlike in a conventional physical computer environment, multiple virtual machines (guest OSs) can be protected with one UPS.

n

Sound

There is no sound generator or speakers in a virtual machine of a virtualization server. Outputting sound from Yokogawa products on a virtual machine thus involves sending the sound data to the HMI client via a network and then playing the sound data with the sound generator and speakers of the HMI client. Sound dropouts, sound loss, and other problems tend to occur when sound is output via a network. Sufficient testing is required before introduction.

n

Remote Server Management Controller

A remote server management controller is commonly installed in a physical server to be used as a virtualization server. To refer to physical server logs the BIOS has recorded during operation of the virtualization server, perform this through the management controller for which a license is required. Purchase the license when the physical server(s) is purchased.

4.5.4

Time Synchronization

In the virtualization system, the time stamp of the virtual server and each virtual machine are independent from others, and time synchronization by the following method is needed. Time synchronization for the guest OS which tends to desynchronize is strongly recommended.

l

If the virtual machine is managed by the domain controller or multiple number

of virtualization servers exist

An NTP server has to be set outside of the virtualization server. Let the virtualization server time synchronize to the NTP server. The domain controller’s time also has to be synchronized to the NTP server. The time of each virtual machine is to be synchronized to the virtualization server. For detail setting, refer to Chapter 5 (Implementation Procedure).

l

If the system is composed of only one virtualization server with no domain

management.

Installation of an external NTP server is not mandatory unless time synchronization to the real time is needed. In such cases the virtualization server becomes the time master. Each virtual machine has to synchronize its time to the virtualization server. For detail setting, refer to Section 5.8.4 (Configuring the Guest OS).

l

If the system is composed of a virtualization server and real PCs

Installation of an external NTP server is not mandatory, but if time synchronization between each real PC and virtualization server is needed, install the NTP server.

Let each virtual machine time synchronize to the virtualization server.

(44)

4.6

Other Information

4.6.1 Licenses

The license information related to each software is described in this Section.

n

VMware License

Two types of VMware licenses are available – paid or free.

When the VMware is applied as a system, obtain the software and its paid license suitable for the virtualization server from the computer vendor. When the free license is needed for evaluation or demonstration purposes, it can be downloaded from the VMware, Inc. website. The free license key is also available from the same website.

The free software can be upgraded to the paid version. Obtain a license key from VMware, Inc. or its agent. For details, contact VMware, Inc. or its agent.

n

Windows OS License

Obtain Windows OS to be used as the guest OS from the computer vendor or other source when purchasing the virtualization server.

For cost saving, Microsoft has publicized the license guideline for a virtualization environment as shown below:

• http://www.microsoft.com/licensing/about-licensing/virtualization.aspx

A Windows OEM license bundled with the computer is valid only with the computer where the license is installed. It cannot be transferred to another computer, which is against the license policy. In order to transfer the Windows OEM license to another PC as the virtualization guest OS, a separate license for the virtualization server has to be provided.

Downgrading from the newest Windows OS to a previous OS is partly available. Refer to the Microsoft website for more details. Use the publicized information in accordance with Yokogawa products support environment.

• http://www.microsoft.com/licensing/about-licensing/briefs/downgrade-rights.aspx For more details, contact Microsoft or the computer vendor.

n

Yokogawa Product License

Yokogawa product licenses to be installed to each guest OS are the same as the real environment.

(45)

4.6.2

Support Contract

To receive the support service such as analysis of problems derived from virtualization software and supply of patch software, please purchase Support&Subscription (SnS) from VMware, Inc. Simultaneous purchase of SnS is essential upon purchase of a VMware product. Since SnS has an expiry date (one year at earliest), there is a requirement to repurchase SnS before expiration to extend the period of validity.

A service contact differs depending on the purchase method of virtualization soft