Simatic Virtualization As A Service en-US
Simatic Virtualization As A Service en-US
___________________
Preface
1
___________________
Introduction
SIMATIC
SIMATIC Virtualization
as a Service
Operating Manual
02/2014
A5E32529703-AA
2
___________________
Commissioning
Configuration of the virtual
3
___________________
machines
Access to the virtual
___________________
4
machines
Switch off and start the
___________________
5
whole system
Data backup and restoring
___________________
6
the delivery status
Legal information
Warning notice system
This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent
damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert
symbol, notices referring only to property damage have no safety alert symbol. These notices shown below are
graded according to the degree of danger.
DANGER
indicates that death or severe personal injury will result if proper precautions are not taken.
WARNING
indicates that death or severe personal injury may result if proper precautions are not taken.
CAUTION
indicates that minor personal injury can result if proper precautions are not taken.
NOTICE
indicates that property damage can result if proper precautions are not taken.
If more than one degree of danger is present, the warning notice representing the highest degree of danger will
be used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to
property damage.
Qualified Personnel
The product/system described in this documentation may be operated only by personnel qualified for the specific
task in accordance with the relevant documentation, in particular its warning notices and safety instructions.
Qualified personnel are those who, based on their training and experience, are capable of identifying risks and
avoiding potential hazards when working with these products/systems.
Trademarks
All names identified by are registered trademarks of Siemens AG. The remaining trademarks in this publication
may be trademarks whose use by third parties for their own purposes could violate the rights of the owner.
Disclaimer of Liability
We have reviewed the contents of this publication to ensure consistency with the hardware and software
described. Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the
information in this publication is reviewed regularly and any necessary corrections are included in subsequent
editions.
Siemens AG
Industry Sector
Postfach 48 48
90026 NRNBERG
GERMANY
A5E32529703-AA
03/2014 Subject to change
Preface
Purpose of the manual
This document supports you in commissioning and configuring the virtualization system.
Core content
The following core issues are covered in this document:
What is SIMATIC Virtualization as a Service?
Which services are included?
How is the virtualization system commissioned?
How is the virtualization system configured in a PCS 7 environment?
How can the virtualization system be extended?
How does remote log in work on virtual machines (VMs)?
How is the data backed up?
Validity
This document is valid for the following components of the "SIMATIC Virtualization as a
Service V1.0" virtualization system:
SIMATIC PCS 7 V8.0 SP1
VMware vSphere 5.1
HP Proliant DL380P GEN8
HP T510 ThinClient
Preface
Table of contents
Preface ................................................................................................................................................... 3
1
Introduction ............................................................................................................................................. 7
1.1
1.2
1.2.1
1.2.2
Description ..................................................................................................................................... 8
The virtualization system ............................................................................................................... 8
Service ........................................................................................................................................... 9
1.3
1.4
Advantages ..................................................................................................................................11
1.5
1.5.1
1.5.2
Scope of delivery..........................................................................................................................12
Hardware and software components ...........................................................................................12
Services .......................................................................................................................................15
Commissioning ..................................................................................................................................... 17
2.1
2.1.1
2.1.2
2.1.3
Preparation...................................................................................................................................17
Unpack and check delivery unit ...................................................................................................17
Assemble devices ........................................................................................................................17
Additional components required ..................................................................................................18
2.2
2.2.1
2.2.2
2.2.3
2.2.4
2.2.5
2.2.6
2.3
2.4
2.5
2.5.1
2.5.2
3.2
3.3
3.4
3.5
Table of contents
3.6
3.6.1
3.6.2
3.7
Access to virtual PCS 7 ES, PCS 7 OS server, and PCS 7 web server ..................................... 59
4.2
4.2.1
4.2.2
5.2
6.2
6.2.1
6.2.2
6.3
6.3.1
6.3.2
6.3.3
Introduction
1.1
Introduction to virtualization
Virtualization is a method of dividing up physical hardware resources on one computer into
several logical (virtual) environments.
As a result of the virtualization the operating system and user software on a computer is
detached from its hardware and provided in the form of a virtual machine (VM).
A virtual machine refers to software that depicts a real computer and can itself execute
applications. Virtual machines have virtual hardware (e.g. graphics card, CPU, memory
(RAM), network cards, and hard disks on SCSI or IDE controllers) and standardized virtual
device drivers.
Several virtual machines can be implemented separately from each other on a real, physical
computer (host system). Isolation prevents conflicts from software dependencies and offers
the opportunity to start and stop virtual machines independently of each other. If there is a
crash only the relevant virtual machine is affected.
The physical computer (host system) can also be upgraded without affecting or modifying
the virtual machines.
Introduction
1.5 Scope of delivery
1.2
Description
SIMATIC Virtualization as a Service is a pre-configured immediately usable virtualization
system for realizing efficient automation solutions for SIMATIC PCS 7 systems.
1.2.1
Introduction
1.5 Scope of delivery
1.2.2
Service
With the purchase of "SIMATIC Virtualization as a Service" the following product groups are
supported as part of the "Product service & support" module:
SIMATIC PCS 7 V8.0 SP1
Hardware platform: HP ProLiant DL380P GEN8
Virtualization software: VMware vSphere Standard 5.1
HP ThinClient T510
The support is provided by a contact from Siemens Industry. The service and support
package offers advice and support for quickly resolved tasks (up to 2 hrs per case) by
telephone, support request, or fax. For requests that last longer than 2 hours Siemens will
submit a quotation for "extended support". The number of cases is not limited.
You can send your support requests via the Siemens Industry Online Portal
(https://support.automation.siemens.com).
1.3
Function principle
A hypervisor is installed on a high-performance server (HP Proliant DL380P GEN8) as an
additional software layer that manages the hardware resources and is dynamically
distributed across the virtual machines.
The central management, configuration, and maintenance of the virtual machines and the
virtualization server is undertaken via a management console and using the "VMware
vSphere Client" software. You can use the following hardware as a management console:
The supplied thin client if this is equipped with a Windows operating system. In this case
the thin client must be connected with the management bus.
Any computer that meets the requirements for the "VMware vSphere Client 5.1" software.
For additional information refer to
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayK
C&externalId=2005083.
The virtual machines are equipped with SIMATIC PCS 7 installations and pre-configured
depending on the automation task (e.g. engineering station, OS server, OS client, and web
server). The access to the virtual machines is provided via the "VMware vSphere Client"
software or a remote connection. The remote access by RDP is only permitted for virtual
PCS 7 OS clients and takes place via the thin client.
The communication between the virtual machines takes place via the communication buses
(management, terminal, redundancy buses) planned for this purpose.
The communication between the virtual machines and the available automation systems
takes place via the plant bus.
Introduction
1.5 Scope of delivery
The following figure shows schematically a configuration of the virtualization system for
which an additional computer is used as a management console. The thin clients are used to
operate and observe the virtual PCS 7 OS clients.
A highly available configuration can be realized via a second virtualization server. The virtual
redundant OS servers require the redundancy bus for the synchronization.
10
Introduction
1.5 Scope of delivery
1.4
Advantages
SIMATIC Virtualization as a Service offers the following advantages:
Solution from a single source
Life cycle services from a single source for all supplied hardware and software
components
Perfectly matched software and hardware components
Quick and safe integration of the system using pre-finished, configured, and tested
components
Reduction in costs
Reduction in life cycle costs by increasing energy efficiency
Reduction in investment and operating costs
Savings through the use of energy-saving and low-cost thin clients for operating and
observing the process
Higher performance
Optimal use and utilization of the hardware resources supplied
Increased flexibility and system availability
Cost-effective and quick expansion of system components using ready-to-run
templates
Simple transfer of a virtual machine to a new hardware environment
Lower cost for system modernization
Reduction in time required for maintenance and support
Reduction in the administrative costs by merging several systems onto one
virtualization server
Reduced maintenance costs and times using centralized administration
Increasing security
More security using remote access with centralized rights management and reduced
attack options for thin clients
Simple system management and extended support in cooperation with SIMATIC
remote services
11
Introduction
1.5 Scope of delivery
1.5
Scope of delivery
1.5.1
Hardware
The following variants of hardware components may be supplied:
Term
Host system/configuration
10600R (DDR-1333)
2x Ethernet 1 GB 4-port
iLo Advanced
Number
Comment
Virtualization server
6Cx2P HP Host
Processor Kit
10600R (DDR-1333)
2x Ethernet 1 GB 4-port
iLo Advanced
12
Introduction
1.5 Scope of delivery
Term
Host system/configuration
Number
Comment
Thin client
8Cx1P HP Host:
Processor Kit
10600R (DDR-1333)
2x Ethernet 1 GB 4-port
iLo Advanced
8Cx2P HP Host
Processor Kit
10600R (DDR-1333)
3x Ethernet 1 GB 4-port
iLo Advanced
VMware Software
The following VMware software is supplied:
Term
Host system
Number
Comment
6Cx1P HP Host,
8Cx1P HP Host
6Cx2P HP Host,
8Cx2P HP Host
13
Introduction
1.5 Scope of delivery
Number
Comment
Term
Number
Comment
Term
Number
Comment
Term
Number
Comment
14
Introduction
1.5 Scope of delivery
Number
Description
Product documentation
Networks
HP Thin Client
VMware
Backing up the delivery status of the ordered virtual machines as OVF files
SIMATIC software
1.5.2
Services
A service agreement for at least 2 years is supplied as standard. You can find detailed
information on the services it includes in the supplied service agreement.
15
Introduction
1.5 Scope of delivery
16
Commissioning
2.1
Preparation
2.1.1
2.1.2
Assemble devices
You will find information and safety instructions for assembling the devices supplied in the
manufacturer's product documentation:
HP ProLiant DL380p Gen 8-Server
(http://h20565.www2.hp.com/portal/site/hpsc/public/psi/manualsResults/?sp4ts.oid=5177
957)
HP t510 Flexible Thin Client
(http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?contentType=
SupportManual&lang=de&cc=de&docIndexId=65042&taskId=135&prodTypeId=12454&pr
odSeriesId=5226831)
17
Commissioning
2.5 Thin client configuration
2.1.3
18
Commissioning
2.5 Thin client configuration
2.2
2.2.1
19
Commissioning
2.5 Thin client configuration
2.2.2
Note
The redundancy bus is required if an additional virtualization server is used to set up a
redundant OS server pair. With a simple system configuration with one virtualization server,
the redundancy bus is not required.
20
Commissioning
2.5 Thin client configuration
The assignment of the bus systems to the ports on the virtualization server is displayed in
the "Configuration" tab in the "VMware vSphere Client" software:
21
Commissioning
2.5 Thin client configuration
The virtual machines use virtual network cards. The network connections are configured as
follows:
Information on the configuration of the network connections of the virtual machines can be
found in section "Setting the network connections (Page 47)".
2.2.3
Introduction
The virtualization server and management console are linked via the management bus. You
can connect the following hardware as a management console:
The supplied thin client if this is equipped with a Windows operating system.
A computer that meets the requirements for the "VMware vSphere Client 5.1" software.
22
Commissioning
2.5 Thin client configuration
Procedure
To connect the virtualization server and management console, follow these steps:
1. Insert the bus connection plug on the network cable into the following port on the
virtualization server:
2. Connect the virtualization server and management console via the relevant interface on
the management console.
3. If you want the management bus to be redundant connect a second network cable to the
following port on the virtualization server and connect it (e.g. via a switch) to the
management bus.
23
Commissioning
2.5 Thin client configuration
2.2.4
Introduction
If the thin client is used exclusively to operate and observe the virtual PCS 7 OS client this is
connected with the virtualization server via the terminal bus. In contrast when being used as
the management console the thin client must be connected with
the management bus.
Procedure
To connect the thin client supplied, follow these steps:
1. Insert the bus connection plug on the network cable into the following port on the
virtualization server:
2. Connect the virtualization server and thin client with the terminal bus. Use the following
interface on the thin client to do so:
24
Commissioning
2.5 Thin client configuration
3. If you want the terminal bus to be redundant connect a second network cable to the
following port on the virtualization server and connect it (e.g. via a switch) to the terminal
bus:
2.2.5
Introduction
Automation systems are connected with the virtualization server via the plant bus.
Procedure
To connect an automation system, follow these steps:
1. Insert the bus connection plug on the network cable into the following port on the
virtualization server:
25
Commissioning
2.5 Thin client configuration
3. If you want the plant bus to be redundant connect a second network cable to the following
port on the virtualization server and connect it (e.g. via a switch) to the plant bus.
2.2.6
Introduction
When operating a redundant OS server pair that is distributed over two virtualization servers,
the redundancy bus must be connected.
Procedure
To connect a virtualization server to the redundancy bus, follow these steps:
1. Insert the bus connection plug on the network cable into the following port on the
virtualization server:
26
Commissioning
2.5 Thin client configuration
2. Connect the virtualization server with the network cable on the redundancy bus.
3. If you want the redundancy bus to be double, connect a second network cable to the
following port on the virtualization server and connect it (e.g. via a switch) to the
redundancy bus:
2.3
Introduction
The virtualization server (HP ProLiant DL380p Gen8) is supplied with a password and a preconfigured IP address. The password and IP address must be modified for each user. The
data set on the virtualization server must be noted and treated in confidence. It is required
for additional configuration steps.
Note
Also observe the device-specific information and safety instructions from the manufacturer:
HP ProLiant DL380p Gen 8-Server
(http://h20565.www2.hp.com/portal/site/hpsc/public/psi/manualsResults/?sp4ts.oid=5177
957)
HP Integrated Lights-Out 4 (iLO 4)
(http://h20565.www2.hp.com/portal/site/hpsc/public/psi/manualsResults/?sp4ts.oid=5219
994)
27
Commissioning
2.5 Thin client configuration
Requirements
The following requirements must be met:
The virtualization server is assembled and commissioned according to the manufacturer's
regulations.
A monitor and keyboard are connected on the virtualization server.
Procedure
follow these steps to configure the virtualization server:
1. Switch the virtualization server on via the mains/standby switch.
The server's start-up application is displayed.
28
Commissioning
2.5 Thin client configuration
3. Enter the following log in data:
Login Name: root
Password: Siemens1234
4. Press Enter.
The options for modifying the system characteristics of the virtualization server are
displayed.
5. Navigate to the "Configure password" entry and press Enter.
Note
Use the <Arrow down> and <Arrow up> buttons to navigate between the individual
entries.
29
Commissioning
2.5 Thin client configuration
6. Enter the default password "Siemens1234" for the virtualization server in the "Old
Password" line.
7. Enter a new password for the virtualization server into the "New Password" and "Confirm
Password" lines.
30
Commissioning
2.5 Thin client configuration
9. Navigate to the "Configure Management Network" entry and press Enter.
31
Commissioning
2.5 Thin client configuration
11.Enter the desired IP address.
32
Commissioning
2.5 Thin client configuration
13.Press Enter to save the change.
A summary of the settings is shown under the "IP Configuration" entry.
2.4
Introduction
If you use a computer as a management console you must install the "VMware vSphere
Client 5.1" software on it.
You configure and manage the virtual machines that are pre-installed with the PCS 7
components and available on the virtualization server using the "VMware vSphere Client"
software.
If you want to use the supplied thin client as the management console, it is not necessary to
execute the steps described in this section. The "VMware vSphere Client 5.1" software is
pre-installed on the supplied thin clients with the Windows operating system. Thin clients
with the HP ThinPro operating system cannot be used as management consoles.
33
Commissioning
2.5 Thin client configuration
Requirements
The following requirements must be met:
The management console is operational.
The installation application for the "VMware vSphere Client 5.1" software is available.
You can find the installation application at https://www.vmware.com.
Procedure
To install the "VMware vSphere Client" software, follow these steps:
1. Start the management console.
2. Start the installation application of the "VMware vSphere Client" software.
3. Select the desired installation language.
34
Commissioning
2.5 Thin client configuration
6. Agree to the license agreement and click "Next".
35
Commissioning
2.5 Thin client configuration
8. Click the "Install" button.
36
Commissioning
2.5 Thin client configuration
2.5
2.5.1
Introduction
When commissioning the thin client, configure the thin client to your requirements with the
aid of the "HP Easy Tools" configuration wizard.
Requirements
The following requirements must be met:
The thin client is assembled and commissioned according to the manufacturer's
regulations.
The thin client is connected with the management bus (for use as a management
console) or with the terminal bus (for use as an operating and observation station).
A monitor, keyboard, and mouse are connected to the thin client.
Procedure
To configure the thin client, follow these steps:
1. Switch on the thin client.
The thin client is started in the restricted user mode. To configure the thin client, you must
switch to the administrator mode.
2. Log into the thin client as administrator. To do so use the following log in data:
User name: Administrator
Password: Administrator
37
Commissioning
2.5 Thin client configuration
3. Start the "HP Easy Tools" configuration wizard via the "Start > Control Panel > HP Easy
Tools" command.
The configuration wizard opens.
38
Commissioning
2.5 Thin client configuration
7. To save the configuration settings right click on the "lock" icon in the Windows task bar
and select the "Commit EWF(C)" command:
NOTICE
If you do not explicitly save the configuration settings these are lost when the thin client
starts next.
8. Switch to the thin client's user mode.
The default log in data are:
User name: User
Password: User
2.5.2
Introduction
When commissioning the thin client for the first time, the "HP Easy Tools" wizard is started
automatically. Use this wizard to configure the thin client to your requirements.
Requirements
The following requirements must be met:
The thin client is assembled and commissioned according to the manufacturer's
regulations.
The thin client is connected with the terminal bus.
A monitor, keyboard, and mouse are connected to the thin client.
39
Commissioning
2.5 Thin client configuration
Procedure
To configure the thin client, follow these steps:
1. Switch on the thin client.
The configuration wizard starts.
40
Introduction
In this section, you will learn how to start the "VMware vSphere Client" application and how
to access the virtual machines that are available on the virtualization server.
Requirements
The following requirements must be met:
The virtualization server and management console are operational.
The password and IP address for the virtualization server have been set and are
available.
See section "Configuring the virtualization server (Page 27)".
The server and management console are linked via the management bus.
The "VMware vSphere Client" application is installed on the management console.
41
Procedure
To start a virtual machine, follow these steps:
1. Start the management console.
2. Double-click the desktop icon for the "VMware vSphere Client" software or select "Start >
All Programs > VMware > VMware vSphere Client".
42
3.2
Introduction
When you start one of the virtual machines for the first time after commissioning an
installation setup executes automatically. The setup installs SIMATIC PCS 7 depending on
the automation task of the virtual machine (e.g. engineering station, OS server, OS client).
The setup must be executed for each virtual machine.
Requirements
The following requirements must be met:
The "VMware vSphere Client" application is started on the management console.
The connection to the virtualization server is established and the available virtual
machines are displayed in the left-hand navigation area of the "VMware vSphere Client"
application.
43
Procedure
To start a virtual machine and execute installation setup, follow these steps:
1. Select the virtual machine and click the "Power On" button.
44
4. Enter the computer name for the virtual machine in the "Computer name" field.
5. Select the desired language to install SIMATIC PCS 7.
45
46
3.3
Introduction
Depending on the automation task the individual virtual machines have the following network
connections:
PCS 7 ES/OS-Client
Terminal bus
Plant bus
Management bus
PCS 7 OS-Server
Terminal bus
Plant bus
Redundancy bus
Management bus
PCS 7 OS-Client
Terminal bus
Management bus
PCS 7 Web Server
Terminal bus
Management bus
So that the communication between the individual virtual machines can be implemented an
IP address must be set for each network connection. The configuration of the network
connections must be implemented individually for each virtual machine and network
connection.
Requirements
The following requirements must be met:
The "VMware vSphere Client" application is started on the management console.
The installation of the SIMATIC software was conducted without errors on all virtual
machines (see section "Start the virtual machines (Page 43)").
Procedure
To set the network connections, follow these steps:
1. Start the virtual machine.
2. Open the network connections via "Start > Control panel > Network and Internet >
Network Connections".
47
4. Select the "Internet Protocol Version 4 (TCP/IPv4)" element and click the "Properties"
button.
48
49
3.4
Using SOFTNET-IE
Introduction
The "SOFTNET-IE S7 REDCONNECT VM V8.2" software offers the option of realizing a
highly available connection to an automation system in the virtual environment. The
"SOFTNET-IE S7 REDCONNECT VM V8.2" software is part of the "SIMATIC NET V8.2"
software package. You can find information on the installation in the "PG/PC - Industrial
Ethernet / PROFIBUS SIMATIC NET PC Software V8.2
(http://support.automation.siemens.com/WW/view/en/61630923)" manual.
Requirements
The following requirements must be met:
The license package for highly available connections (MLFB: 6GK1704-0HB08-2AA0) is
available. One license package per virtual machine is required.
CPU firmware version is V6.0.0 or higher
50
51
3.5
Introduction
The virtual machines can be set such that they are executed automatically after the system
starts.
Requirements
The following requirements must be met:
The "VMware vSphere Client" application is started on the management console.
The connection to the virtualization server is established and the available virtual
machines are displayed in the left-hand navigation area of the "VMware vSphere Client"
application.
Procedure
To activate the automatic execution of a virtual machine, follow these steps:
1. Click the "Configuration" tab on the "VMware vSphere Client" application.
2. In the "Software" area click on "Virtual Machine Startup/Shutdown".
The available virtual machines are displayed in the "Startup order" area.
52
53
54
3.6
3.6.1
Introduction
To transfer the license to a virtual machine the use of USB devices must be configured for
each virtual machine.
Requirements
The following requirements must be met:
The "VMware vSphere Client" application is started on the management console.
The license USB stick for licensing the SIMATIC components is connected to the
management console.
Procedure
To connect a USB device with a virtual machine, follow these steps:
1. Start the virtual machine.
2. Click on the USB icon in the toolbar of the virtual machine and select the "Connect to
USB device" command.
3. Select the USB device that contains the necessary SIMATIC licenses.
4. Repeat steps 1 to 3 for all available virtual machines.
55
3.6.2
Introduction
The transfer of SIMATIC licenses from a license USB stick to a drive on a virtual machine
takes place with the aid of the SIMATIC Automation License Manager (ALM). The SIMATIC
Automation License Manager is pre-installed on all virtual machines.
Requirement
The following requirements must be met:
The "VMware vSphere Client" application is started on the management console.
The license USB stick for licensing the SIMATIC components is connected to the
management console.
The connection to USB devices is configured on the virtual machines
(See section "Connecting USB devices (Page 55)")
Procedure
To transfer the licenses to the drive, follow these steps:
1. Start one of the virtual machines.
2. Start the SIMATIC Automation License Manager via the following desktop icon:
3.7
56
57
Introduction
Access to the virtual PCS 7 ES, PCS 7 OS server, and PCS 7 web server is provided via the
"VMware vSphere Client" software. Access using RDP is not permitted.
Requirements
The following requirements must be met:
The virtual machines are configured.
(See section "Configuration of the virtual machines (Page 41)".)
The virtual machine that you want to access is activated.
The "VMware vSphere Client" software is started.
59
Procedure
To access a virtual machine, follow these steps:
1. Select the virtual machine that you want to access.
2. Click the "Launch Virtual Machine Console" button to display the virtual machine.
60
4.2
4.2.1
Introduction
You create and configure an RDP connection on the thin client for remote access to a virtual
PCS 7 OS client.
Requirements
The following requirements must be met:
The virtual PCS 7 OS client that you want to access is configured and activated.
(See section "Configuration of the virtual machines (Page 41)".)
The thin client is switched on.
61
62
63
Note
Via the "Settings" button in the "Remote audio" area you can set the device on which the
acoustic signals are played for messages and alarms from the PCS 7 notification system.
8. Activate the desired options under the "Programs", "Experience", and "Advanced" tab.
9. Click the "Connect" button to establish the connection to the PCS 7 OS client.
64
NOTICE
If you do not explicitly save the configuration settings, these are lost when the thin client
starts next.
11.Switch to the thin client's user mode.
65
66
67
6. Click "Next".
68
69
10.Set the desired settings for the speed of the connection and user interface.
70
71
4.2.2
Introduction
The remote connection is logged off and separated from the relevant virtual machine (e.g.
PCS 7 ES, PCS 7 OS client).
Requirements
The following requirements must be met:
The virtual machine is switched on.
There is a remote connection
Procedure
To disconnect a remote connection, follow these steps:
1. In the start menu of the virtual machine click on "Log off > Disconnect".
72
73
5.2
3. End the virtualization server via the "VMware vSphere Client" application.
Select the virtualization server and select the "Enter Maintenance Mode" command in
the context menu.
74
Note
Ensure that the maintenance mode of the virtualization server is not ended automatically
when closing down. After restarting the virtualization server, the maintenance mode must
be ended manually. Select the virtualization server in the "VMware vSphere Client"
software and select the "Exit Maintenance Mode" command in the context menu.
Select the virtualization server and select the "Shut Down" command in the context
menu.
75
In the following dialog click on the "No" button to end the "VMware vSphere Client"
software.
76
Introduction
You can back up the working status of a virtual machine by exporting an OVF template. You
export the OVF template with the aid of the "VMware vSphere Client" application.
Requirements
The following requirements must be met:
The "VMware vSphere Client" application is opened.
The process operation of the PCS 7 projects is ended (runtime is deactivated).
The virtual machines that you want to back up are switched off.
You can find information on this in section "Shut down the whole virtualization system
(Page 74)".
Procedure
To back up a virtual machine, follow these steps:
1. Select the virtual machine for which you want to back up the working status in the
"VMware vSphere Client" application.
2. Select the "File >Export > Export OVF Template" command in the menu bar.
The "Export OVF Template" dialog box opens.
3. In the "Name" field, type a name for the backup file.
4. In the "Directory" field, enter the desired storage location for the backup file.
5. Select the "Folder of files (OVF)" option in the drop-down list in the "Format" area.
6. In the "Description" field, enter a description for the virtual machine.
7. Click "OK".
The virtual machine is exported as an OVF file.
77
6.2
6.2.1
Procedure
To delete a virtual machine, follow these steps:
1. Open the "VMware vSphere Client" application.
2. Select the desired virtual machine and the "Delete from Disk" command in the context
menu.
78
6.2.2
Requirements
The following requirements must be met:
The "VMware vSphere Client" application is opened.
The virtual machines that are restored are removed from the hard disk of the virtualization
server.
The USB hard disk supplied with the backup data and the MAC addresses to restore the
virtual machines is at hand.
See the section titled "Scope of delivery (Page 12)" for more information.
Procedure
To restore the delivery status of a virtual machine, follow these steps:
1. Connect the supplied USB hard disk to the management console.
2. In the "VMware vSphere Client" application menu bar select the "File > Deploy OVF
Template" command.
79
4. Click "Next".
80
81
82
83
84
85
86
87
6.3
88
6.3.1
Introduction
By installing the "VMware vSphere ESXi" software all data on the virtualization server is
deleted and a new hypervisor is installed (see section "Function principle (Page 9)").
Requirements
The following requirements must be met:
The virtualization server is assembled and commissioned according to the manufacturer's
regulations.
A monitor, keyboard, and mouse are connected to the virtualization server.
The supplied CD with the installation of the "VMware vSphere ESXi 5.1" software is
available (see section "Scope of delivery (Page 12)").
Procedure
To install the "VMware vSphere ESXi" software and set the virtualization server, follow these
steps:
1. Switch the virtualization server on via the mains/standby switch. The server's start-up
application is displayed.
2. Insert the installation CD for the "VMware vSphere ESXi 5.1" software into the CD drive
of the virtualization server.
3. Open the boot menu via the F11 button
89
5. Select the target drive for installing the SD memory card for the virtualization server and
press Enter.
90
6.3.2
Introduction
After installing the "VMware vSphere ESXi 5.1" software you set the IP address and network
adapter of the virtualization server.
Requirement
The following requirements must be met:
The virtualization server is assembled and commissioned according to the manufacturer's
regulations.
The "VMware vSphere ESXi 5.1" software is installed.
91
Procedure
Proceed as follows to configure the virtualization server:
1. Switch the virtualization server on via the mains/standby switch. The server's start-up
application is displayed.
4. Press Enter.
The options for configuring the system properties of the virtualization server are
displayed.
92
93
94
10.Press the <Esc> button to reach the "Configure Management Network" initial dialog.
11.Navigate to the "Network Adapters" entry and press Enter.
95
6.3.3
Introduction
On the supplied USB hard disk you will find additional configuration data (incl. licenses,
network settings) that you can transfer to the virtualization server with the aid of the "VMware
vSphere Command-Line Interface" software.
Requirements
The following requirements must be met:
The instructions described in the sections "Installing the "VMware vSphere ESXi"
software (Page 89)" and "Configuration of the IP address and network adapter (Page 91)"
have been executed.
The supplied USB hard disk is available.
The installation application of the "VMware vSphere Command-Line Interface 5.1 Update
1" software is available.
You can find the installation application at
http://www.vmware.com/support/developer/vcli/.
96
Procedure
In order to transfer the configuration data on the supplied USB hard disk to the virtualization
server, proceed as follows:
1. Install the "VMware vSphere Command-Line Interface 5.1 Update 1" software on the
management console.
Additional information on this is provided in the manufacturer's documentation
(http://www.vmware.com/support/developer/vcli/).
2. Connect the supplied USB hard disk to the management console.
3. Open the Windows command line.
4. Enter the path to the installation folder for the "VMware vSphere Command-Line Interface
V5.1 Update1" software.
6. Press Enter.
97
8. Press Enter.
The configuration data is transferred to the virtualization server.
9. Restart the virtualization server.
98