Sunteți pe pagina 1din 181

The privilege of HCNA/HCNP/HCIE:

With any Huawei Career Certification, you have the privilege on http://learning.huawei.com/en to enjoy:
n
1e-Learning Courses Logon http://learning.huawei.com/en and enter Huawei Training/e-Learning
/e

o m
If you have the HCNA/HCNP certificateYou can access Huawei Career Certification and Basic Technology e-Learning
courses.
e i .c
If you have the HCIE certificate: You can access all the e-Learning courses which marked for HCIE Certification Users.

aw

Methods to get the HCIE e-Learning privilege : Please associate HCIE certificate information with your Huawei account, and

hu

email the account to Learning@huawei.com to apply for HCIE e-Learning privilege.


g .
2 Training Material Download
i n

arn
Content: Huawei product training material and Huawei career certification training material.

//le
MethodLogon http://learning.huawei.com/en and enter Huawei Training/Classroom Training ,then you can download
training material in the specific training introduction page.
p :
3 Priority to participate in Huawei Online Open Class (LVC)
t t

s :h
The Huawei career certification training and product training covering all ICT technical domains like R&S, UC&C, Security,

4Learning Tools: rc e
Storage and so on, which are conducted by Huawei professional instructors.

s o
eNSP Simulate single Router&Switch device and large network.

R e
WLAN Planner Network planning tools for WLAN AP products.

n g
In addition, Huawei has built up Huawei Technical Forum which allows candidates to discuss technical issues with Huawei experts ,

ni
share exam experiences with others or be acquainted with Huawei Products.

a r
Statement:
L e
r e
This material is for personal use only, and can not be used by any individual or organization for any commercial purposes.
o
M
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 1
FusionSphere
Lab Guide

Issue: 01
Date: 2015-07

n
Introduction to FusionSphere /e
o m
i.c
The FusionSphere solution consists of the FusionManager
cloud OS software FusionCompute and
cloud management software FusionManager. APP
VM
APP APP
VM
APP
w e APP
VM
APP
FusionCompute is deployed on physical Guest OS Guest OS
u a Guest OS

.h
servers to virtualize the server hardware

g
CPU CPU CPU
resources, including CPUs, memory, and
network interface cards (NICs).
i n
FusionManager schedules and manages

arn Resource pool

le
computing, network, and storage resources

//
CPU CPU CPU
in the underlying resource pools in a
centralized manner. On FusionManager,

p :
t
users can create VMs for tenants, allocate
resources for the VMs, and manage the
t
:h
FusionCompute
VMs based on the service requirements.
Virtualized Virtualized Virtualized
FusionSphere improves hardware resource
e s Server Server Server

r
utilization, shortens the service launch period,
c 1 2 3

ou
simplifies maintenance, and reduces the
maintenance costs.

es
Objectives
R
n g
ni
This document illustrates how to quickly install and configure FusionSphere and provision services using

r
FusionSphere. There are some tasks label as optional, which means trainees can skip this task. However,

a
the instructor must prepare those tasks earlier.
e
1.
e L
Install FusionCompute (Optional)--------------------------------------------------------------------------------------P12

o
2.
3.
r
Configure FusionCompute-----------------------------------------------------------------------------------------------P18
Install FusionManager (Optional)--------------------------------------------------------------------------------------P39
M
4.
5.
Install the VSAM VM (Optional)----------------------------------------------------------------------------------------P43
FusionComputeVSAM Configure the Alarm Reporting Function (Optional)------------------------------P46
6. Add Resources to FusionManager-------------------------------------------------------------------------------------P47
7. Configure Resource Pools------------------------------------------------------------------------------------------------P52
8. Prepare a VM Template--------------------------------------------------------------------------------------------------P55
9. Create a VDC----------------------------------------------------------------------------------------------------------------P63
10. Create a VPC and Networks---------------------------------------------------------------------------------------------P64
11. Provision VM----------------------------------------------------------------------------------------------------------------P67

Copyright Huawei Technologies Co., Ltd. 2014.


All rights reserved.
1 Background
Resource utilization of traditional servers is mostly 5% to 25%, which swells a company's operating
expenditure with the increase of servers required by the growing services of the company. This is a
common problem challenging most companies nowadays.
Using virtualization technologies, FusionSphere enables one physical server to function as multiple or even
hundreds of isolated virtual servers providing the same functions as a traditional server. Besides,
FusionSphere is able to pool and dynamically manage the CPU, memory, disk, and NIC resources of these
virtual servers in a centralized manner, thereby improving resource utilization and helping companies
reduce hardware investment costs as well as operating expenditures.
Example Scenario
n
Company A has three departments: Business, Development, and Maintenance. Business Department is
/e
responsible for product sales; Development Department is responsible for product development; and
Maintenance Department is responsible for after-sales services.
o m
i.c
The company has an X6000 server and an IP SAN storage device deployed in the equipment room to
support services of all these three departments.

w e
u a
g .h
n
Business Dept

i
X6000 server
arn
le
Maintenance Dept
IP SAN

Development Dept

: //
t t p
With the growth of services, the three departments apply for new servers to handle new services. The

:h
server requirements of the three departments are as follows.

Department
e
Server Requirementss
r c
ou
One server to deploy a website system for showcasing products and handling
Business Dept
online orders. The server is required to be accessible to public network users.

es
One server to deploy databases
Development Dept
R
One server to serve as the file server

n g
ni
Maintenance Dept One server to serve as the file server

a r
The Company A is facing the following problems:

L e
Resource utilization of the existing servers is low, while purchasing new servers requires additional
capital investment.

r e
Servers, storage devices, and switches cannot be managed in a centralized manner, resulting in slow

oservice response and low maintenance efficiency.

M
Therefore, Company A expects to optimize service deployment of its three departments by improving the
resource utilization of its existing servers.
FusionSphere is able to virtualize physical resources to enable a physical server to run multiple VMs that
carry different servers. This solution improves the server utilization and reduces the hardware investment
cost. Moreover, FusionSphere is able to manage both physical and virtual resources to improve the
company's maintenance efficiency and service response capability.
Next, we are going to show how to deploy FusionSphere on Company A's existing servers and use
FusionSphere to allocate resources and provision service VMs to the company's three core departments.

2
2 Preparations
2.1 Deployment Plan
1. Physical Device Networking

Company A's network devices include an aggregation switch and an access switch. Servers and the IP
SAN storage device are connected to the access switch over their network ports to allow data access to
the switch from the management, storage, and service planes of the devices.

Aggregation switch
192.168.210.132 Internet
n
VLAN 2000 VLAN 2004
/e
Administrator
o m
Access switch
e i.c
eth0 (Management NIC 1)
eth1 (Management NIC 2)
aw
Controller A Storage links (4)
eth2 (Storage NIC 1)
u
.h
Management
eth3 (Storage NIC 2)
link
g
eth4 (Service NIC 1)

n
eth5 (Service NIC 2)
BMC
i
rn
Management
link

le a
//
Controller B Storage links (4)

p : IP SAN
t t
:h
Management BMC
Blade 1
e s
Blade 2 plane
Service
c
Storage plane
X6000 server
r plane

s ou
Network
Plane
Re
Configuration Information Remarks

Management
i n g
VLAN 2000
The company's management plane network.
You can set the host IP addresses and management
plane
r n
Subnet: 192.168.210.0/24 node IP addresses in the FusionSphere system in the

e a management plane.

e L VLAN 13
Server BMC plane, which communicates with the
management plane.

or
BMC
Subnet: 192.168.13.0/24 X6000 blade 1 BMC IP address: 192.168.13.105
X6000 blade 2 BMC IP address: 192.168.13.106

M Network segments, VLANs, and


subnet masks applicable to the
storage planes:
The storage IP addresses on the four storage planes
are:
Storage 172.20.100.100
172.20.0.0 VLAN 4 255.255.0.0
planes 172.30.100.100
172.30.0.0 VLAN 5 255.255.0.0
172.40.100.100
172.40.0.0 VLAN 6 255.255.0.0
172.50.100.100
172.50.0.0 VLAN 7 255.255.0.0
Subnet 192.168.214.0/24 under VLAN 2004 can
Service directly connect to the Internet.
2004~2019
planes VLANs 2011 to 2019 can be used for service
provisioning.

3
2. Installation Plan Description
Install FusionCompute virtualization software on the servers in the system so the servers become hosts
providing virtual resources in the FusionCompute hypervisor. Then, install the FusionSphere
management components, including Virtualization Resource Management (VRM), Virtual Service
Appliance Management (VSAM), and FusionManager on Host 1, as shown in the following figure.
VSAM management
VRM management IP address:
IP address: 192.168.210.50 FusionManager
192.168.210.30 management IP address:
192.168.210.60

n
/e
Virtualization
software
FusionCompute
o m
Host 1 Host 2
e i.c
Management IP address
Management IP address
(eth0): 192.168.210.22
aw
(eth0): 192.168.210.21
u
Access switch

g .h
i n
arn
le
IP SAN
Aggregation switch

192.168.210.132
: //
t t p
:h
Component Description Data Plan

e s Host 1
Name: Host01

r c Management IP address:

ou
192.168.210.21
Two blades in the X6000 server function as two hosts in
root user password: Admin@1234
Host the FusionCompute hypervisor after having the

s
Host 2
FusionCompute software installed.

e
Name: Host02

R
Management IP address:
192.168.210.22

n g root user password: Admin@1234

ni
Management component in the FusionCompute

r
hypervisor.

a
VRM can be deployed in either standalone or

e
active/standby mode. In this example task, VRM is

eL
deployed on only one host (Host01) in standalone mode,
and the VRM management IP address is configured to Management IP address:

or
the management plane IP address. 192.168.210.30
VRM
Notes: In active/standby mode, the management Subnet mask: 255.255.255.0
Gateway: 192.168.210.1

M
node is deployed on two physical servers or VMs. If
the active node is faulty, the system rapidly switches
services to the standby node to ensure service
continuity. Therefore, the active/standby mode
provides high service reliability.

Cloud management component, which can be deployed


in either standalone or active/standby mode to manage
VM name: FM01
and maintain physical resources, virtual resources, and
Node name: FMN
services in a centralized manner.
Management IP address:
FusionManager In this example task, less than 200 VMs are required.
192.168.210.50
Therefore, only one FusionManager node is needed. It is
Subnet mask: 255.255.255.0
deployed on a VM on Host01, and its management IP
Gateway: 192.168.210.1
address is configured to the management plane IP
address.

4
Component Description Data Plan
The Virtual Service Appliance (VSA) management
component, which is deployed on a VM to
automatically configure and manage system service
VMs that provide software router, virtual load
VM name: VSAM01
balancer (VLB), and Dynamic Host Configuration
Node name: VSAM
Protocol (DHCP) functions.
VSAM Management IP address:
After VSAM is deployed in the system, users can
192.168.210.60
apply for software routers, bind a public IP address to
Subnet mask: 255.255.255.0
a VM, and configure access control list (ACL) rules to
Gateway: 192.168.210
improve network access security.
In this example task, VSAM is deployed on a single
n
/e
VM on Host01, and its management IP address is
configured to a management plane IP address.

o m
The host storage port names and

i.c
IP addresses for communicating
Storage
The storage device is connected to hosts through the
switch storage plane network to provide virtualized
w e
with the storage devices:
StoragePort1 172.20.123.123

a
device
storage resources for the VMs running on the hosts. StoragePort2 172.30.123.123

u
StoragePort3 172.40.123.123

.h
StoragePort4 172.50.123.123

g
Connect servers to the storage device to enable
i n
rn
Switch intercommunication among different planes in the N/A

a
FusionSphere system.

// le
p :
t t
s :h
r ce
s ou
Re
n g
rni
e a
e L
o r
M

5
2.2 Service Deployment Plan
1. Add resources to FusionManager.
After installing FusionSphere, add the FusionCompute hypervisor to FusionManager, so that
FusionManager can manage clusters and hosts resources in the FusionCompute hypervisor and provide
virtualized resources for users.
The following figure shows the process of adding virtualized resources to FusionManager.

FusionManager

FusionManager
FusionCompute
Resource Resource
n
/e
zone 1 zone 2
(zone)
Cluster 1 Cluster 2 Cluster 3
o m
i.c
Create resource zones. Add Add the hypervisor.

e
resources.

zone FusionManager
aw
AZ 2
u
.h
AZ 1 zone
(az)

i n g
rn
Resource Resource
cluster 1 cluster 2

Create AZs.
le a
Associate resource clusters

//
with resource zones.
1. Create resource zones in FusionManager.

p :
t
A resource zone in the FusionManager system is a logical zone to manage all resources in an

t
independent layer 2 network in the system. All resources in the system must belong to one or multiple

:h
resource zones.

e s
2. Add the FusionCompute hypervisor to FusionManager.

r c
Add the FusionCompute hypervisor to FusionManager to provide virtualized resources in the

ou
FusionManager system. A hypervisor contains all the cluster resources managed by a set of VRM
system in FusionCompute.

es
3. Associate resource clusters with resource zones in FusionManager.

R
After adding the hypervisor to FusionManager, associate resource clusters in the hypervisor with the

g
resource zones in FusionManager, then the resources in the clusters can be automatically added to the

n
ni
resource pools in the zones.

a r
4. Create availability zones (AZs) in FusionManager.
An AZ is a collection of resources available to users in a resource zone. If a resource zone contains

L e
multiple resource clusters, you can create multiple AZs to accommodate different resource clusters. An

e
AZ can contain one or multiple resource clusters. By selecting an AZ for a user, you can specify the

o r
source of resources available to the user.
In this step, you need to plan data for the following objects.

M
Object Description Data Plan
Plan the following information for each resource zone:
Resource Name: identifies a resource zone. Name: zone
zone Location: identifies the location of the physical resources in Location: HT2
the resource zone.

Plan the names of the FusionCompute hypervisor and the Hypervisor name: FC
Hypervisor
VSAM node. VSAM name: VSAM

AZ Plan the names of the AZs to be created. AZ name: az

6
2. Configure resource pools and divide resources into VDCs.
After adding resources to FusionManager, resource pools in each resource zone have available virtual
resources. Then, the administrator can include resources in the resource pools into different virtual data
centers (VDCs) and allocate the resources to organizations by VDC.
Zone
AZ VDC01
Resource pools

VDC02
Computing Storage Network

n
/e
resource pool resource pool resource pool

Resource VDC03

o m
i.c
cluster

1. Configure resource pools.


w e
Resource pools are classified into computing resource pools, storage resource pools, and network

u a
resource pools. Resources in the resource pools are from the resource clusters virtualized by the

.h
hypervisor.

g
Computing resource pool: contains virtual CPU and memory resources on the hosts in the resource
clusters.
i n
rn
Storage resource pool: contains data store resources in the resource clusters.
Network resource pool: contains distributed virtual switches created in the hypervisor. The virtual local

a
area networks (VLANs) used for creating service networks on FusionManager must also be added to

le
//
the network resource pool for creating external networks and the VSA management network.

:
2. Create VDCs.

t t p
VDC is the unit for using virtual resources in the resource pools. For example, to provide virtual
resources for three departments of a company, you can create a VDC for each department, with each

:h
VDC containing isolated computing, storage, and network resources required for the VMs used by each
department.

e s
In this step, you need to plan data for the following objects.
Object Description
r c Data Plan

networks.
s ou
Plan the start VLAN ID and end VLAN ID for the service
VLAN pool name: VLAN_pool

e
VLAN pool Start VLAN ID: 2004
All VLANs must be allowed to pass through the service

R
End VLAN ID: 2019
plane ports on the switch.

i n g
Plan Company A's existing network that can connect to
the Internet as the external network, and add the
External network name:
external_network01
External
n
external network to the company's network resource

r
VLAN: 2004

a
network pool to provide IP addresses for the VMs to access Subnet IP address: 192.168.214.0

e
public networks. Subnet mask: 255.255.255.0

L
Gateway: 192.168. 214.1

e The VSA management network assigns management

or
IP addresses for software routers. The configuration
VSA management network name: VSAnet
requirements are as follows:
VLAN: 2001

M
The VSA management network must be configured
VSA Subnet IP address: 192.168.214.0
on the aggregation switch to communicate with the
management Subnet mask: 255.255.255.0
network (VLAN 2000) of the management
network Available IP addresses:
components at layer 3.
192.168.211.101-192.168.211.150
The VLAN planned for the VSA management
Gateway: 192.168. 214.1
network cannot be added to FusionManager VLAN
pools.
VDC names:
Business Dept: VDC01
Plan an independent VDC each for the Business
Development Dept: VDC02
Department, Development Department, and
Maintenance Dept: VDC03
VDC Maintenance Department.
VDC quotas: 12 CPUs, 12 GB memory, and
Resources in each VDC are managed by the
300 GB storage for each department
administrator of the VDC respectively.
VDC administrator names: VDC01_admin;
VDC02_admin; VDC03_admin

7
3. Deploy services.
After creating VDCs, create a network in each VDC and provision VMs for users in the VDC. The following
figure uses the VDC (VDC01) for the Business Department as an example.
VDC01
VPC01
Routed
Router
VM01 network
External
VLAN 2016 network

Business Dept VlAN 2004

n
192.168.214.0/24

/e
CPU

o m
i.c
The VDC administrator can create a network and required VMs in the VDC based on the CPU, memory,
storage, and network resources allocated to the VDC.
In this step, you need to plan data for the following objects.
w e
Object Description
u a
Data Plan

VPC01
Plan a virtual private cloud (VPC) for creating secure service
g .h
VPC name: VPC01
networks for the VDC.
i n
Apply for a software router in VPC01.
A software router can be used to bind an elastic IP address to
arn
Router

//
a VM so the VM can connect to the public network. The router
le N/A

:
also supports the ACL function, which allows the system to use

t t p
ACL rules to control data packets to be sent to the VMs.

:h
Routed network name:
Route_network01

e s
Create a routed service network in VPC01. VLAN 2016
Routed
c
Select a VLAN, for example, VLAN 2016, for the routed
r
Subnet IP address:

ou
network network from the service plane VLAN pool. The subnet IP 192.168.16.0
address can be specified by the VDC administrator as desired. Subnet mask: 255.255.255.0

es Gateway: 192.168.16.1

R
g
Create a VM for deploying the website system in the routed

n
ni
network.
VM VM name: VM001
The VM can be created using a VM template that has been

a r
published on FusionManager.

L e
r e
o
M

8
2.3 Process Overview
Use FusionSphere to deploy services for the Business Department involves three phases: install
FusionSphere, add and configure resources, and create the network and VMs. The entire process is as
follows.

Install FusionSphere.
Install Install Configure the alarm
FusionCompute. Install VSAM.
FusionManager. reporting function.
Install the Install FusionManager Configure the function
FusionCompute software Install VSAM to that allows
n
/e
to manage physical
on hosts, deploy the VRM and virtual resources configure and manage FusionCompute and
component, and

m
as well as services in software routers VSAM nodes to report

o
configure virtual storage a centralized manner. requested by tenants. alarms to

i.c
resoruces. FusionManager.

Add and configure resources.


w e
Add resources to Configure Prepare template
u a
.h
Create a VDC.
FusionManager resource pools. resources.
Create resource zones
in FusionMananger
Configure resource
pools containing
n g
Import the VSA template

i
Create a VDC for
tenants, configure the

rn
required by the software
and add the required computing, allowed resource
router and the

a
hypervisor to it to storage, and network quota, and add VDC
application VM template

le
provide virtualized resources in the users.

//
to FusionManager.
resoruces. resource zone.

p :
t t
:h
Create the required service network and VMs.
Create a VPC and
e s
Provision VMs.
required network.
r c
ou
Create an isolated Use the imported VM
network for the VDC template to create VMs
and create the service
network required for
es
and configure elastic IP

R
addresses and ACL
provisioning rules for the VMs.
applications.

i n g System
administrator
VDC
administrator

r n
e a
e L
or
M

9
2.4 Software Preparation
Obtain the following software files for installing FusionSphere.

Software Type Software Package How to Obtain


FusionCompute FusionCompute
host OS V100R005C00SPC100_CNA.iso Visit http://support.huawei.com and choose
Enterprise > Software > IT > FusionCloud
FusionCompute FusionCompute
> FusionSphere > FusionCompute >
installation wizard V100R005C00SPC100_Tools.zip
V100R005C00SPC100.
VRM VM template FusionCompute
n
/e
file V100R005C00SPC100_VRM.zip

o
Visit http://support.huawei.com and choosem
i.c
FusionManager FusionManager Enterprise > Software > IT > FusionCloud

e
installation file V100R005C00SPC200_SV.zip > FusionSphere > FusionManager >
V100R005C00SPC200.

aw
u
.h
Visit http://support.huawei.com and choose

g
VSAM VM template FusionCompute Enterprise > Software > IT > FusionCloud

n
file V100R005C00SPC100_VSAM.zip > FusionSphere > FusionCompute >
i
rn
V100R005C00SPC100.

le a
//
Obtain the following software files for provisioning services using FusionSphere.

Software Type Description


p : How to Obtain

t t
:h
Used to install an OS on a VM.
This task uses the SUSE Linux
OS image file

e s
Enterprise Server 11 OS as an
Provided by the lab administrator.
example.
r c
ou
Application software to be installed

Application software MySQL s


on VMs, for example:

e Provided by the lab administrator.


R
WinRAR

g
Apache
n
r ni Visit http://support.huawei.com/enterprise,

a
choose Software > IT > FusionCloud >
FusionCompute
Tools
L e V100R005C00SPC100_GuestOS
FusionSphere > FusionCompute >
V100R005C00SPC100 and download

e
Drivers.zip

r
FusionCompute

o V100R005C00SPC100_GuestOSDrivers.zip.

M Visit http://support.huawei.com/enterprise,
choose Software > IT > FusionCloud >
FusionCompute
VSA VM template FusionSphere > FusionCompute >
V100R005C00SPC100_VSA.zip
V100R005C00SPC100 and download
FusionCompute V100R005C00_VSA.zip.

10
Obtain the following tools before installing FusionSphere:

Tool Type Tool Name How to Obtain


Cross-platform remote access tool PuTTY http://www.putty.org

File decompression tool 7-Zip http://sparanoid.com/lab/7z/

Ensure that the local PC used for installing FusionSphere software meets the following requirements:

Item Requirement
Uses 32-bit CPUs with a minimum of 2 GB memory.
n
/e
Hardware The system disk has a minimum of 1 GB free space, and one another service disk has a

m
minimum of 30 GB free space.
32-bit Windows XP or Windows 7
o
i.c
OS
Windows firewall is disabled.

Network
w e
The PC can communicate with the planned management plane and the host BMC plane

a
properly.

u
g .h
In the following operation instruction slides, the left column provides the procedure, and the right
column provides the operation background, principle, and other related information. The following

i n
table explains the icons used in the provisioning process. It is recommended that you familiarize yourself

rn
with the icon descriptions before proceeding.

le a
//
Icon Description

p :
t
1 2 3 Operation sequence

t
:h
Transition between different sections of
s
e
the web interface

r c
ou
Skip to step

es
R
Example:

n g
ni
1

a r
e
eL
2

or
M
Step 1: Click Resource.
Step 2: Click Resource Zones.

11
NOTE: The screenshots in the steps below include sample parameter values, which may vary
from the actual parameter values onsite.

3 Install FusionCompute(Optional Task)

3.1 Install an OS on the Host


Step 1: Mount an ISO file to the host.
1. Set the local PC to ensure that the PC can ping the host where
FusionCompute is to be installed.
Connect the PC and the host to the
Ensure that the IP address of the PC is in the same network
n
/e
same switch.
segment as the host management IP address, and the PC IP

m
address can ping the host BMC system.

o
i.c
2. Open a web browser on the PC, then enter the BMC IP address First configure the first blade of the
into the address bar to access the host BMC system. X6000 server.
3. Log in to the BMC system using an administrator account.
w e
u a
g .h
Administrator root is used as an

i n
example in this task.

arn
//le
p :
4. Open the Remote Control window.
t t
:h
You may need to click Remote

s
Virtual Console (requiring JRE) on

r ce the Remote Control page of some


Huawei server BMCs.

s ou
Re
5. Mount an ISO image to the host. 3 Select FusionCompute

g
1 V100R005C00SPC100_CNA.iso.

ni n 4 4 When Connect turns to


2
a r Disconnect, the ISO file is mounted

e 3 to the host successfully,

e L
r
Step 2: Upload the OS installation file.
o
M
1. Restart the host after the ISO file is mounted to it. Note
The host BIOS password may be
required during the restart. Obtain
1 the password in advance.
When the host begins to The default BIOS password for
3
restart, press F11 repeatedly 2 Huawei RH-series rack servers, X-
until the screen for selecting series high-density servers, and
boot device is displayed. E6000 blade server is uniBIOS123.
The default BIOS password for
Huawei Tecal E9000 blade server is
Huawei12#$ or uniBIOS123.

12
Step 2: Start to install the OS on the host.
2. Set DVD-ROM as the boot device.
Note
The DVD-ROM name and the
configuration screen may vary
depending on the server used.

3. Select Install. The system begins automatic


data loading, which takes
n
about 2 minutes.
/e
1
o m
e i.c
Step 3: Configure host information.

aw
1. Select Network, then select a management plane port, for example,
u
Tip
eth0.
g.h
When configuring host data on
the configuration screen:
2
i n
Press Tab or the up and

rn
down arrow keys to move
1 the cursor.

le a Press Enter to expand or

//
execute the highlighted item.

p : Press the space bar to


toggle between options.

t t
s :h
2. On the IP Configuration for eth0 screen, configure the IP address
and subnet mask for the management plane network port.

r ce Note: The management


plane VLAN must be set to

ou
the tagged type on the

s
switch port to which the
1

Re management network port is


connected.
2

n g
ni
ar
Use the

e 3 number pad

e L on the
keyboard to

or
enter numbers.

M
3. On the Network Configuration screen, configure the management
plane gateway.
N/A

13
Step 3: Configure host information.
4. Select Hostname, then set the host name. N/A

2
1
3

n
5. Select Timezone, then set the local time zone and time. N/A

/e
2
o m
e i.c
w
1
3
u a
4

g .h
i n
6. Select Password, then set the password for user root.
arn NOTE

le
Note: Exercise caution when entering the password to avoid incorrect intput. The password must contain

//
at least:

p : Eight characters

t
One space or one of the

t following special characters:

:h
2 `~!@#$%^&*()-_=
+\|[{}];:'",<.>/?
1
3
e s At least two of the following:

c
lowercase letters,

r uppercase letters, and

ou
numbers.

Step 4: Install the host OS.


es
R
1. Select OK in the bottom right corner of the screen, then select Yes in the displayed 2 Ensure that the OS is

n g
dialog box to install the OS on the host. installed on the default disk

ni
1 partition.

ar
3 Confirm the configuration,

e
then select Yes to install the

L
OS.

e
The installation takes about

or
10 minutes.
2 After the installation is
3

M
complete, the host
automatically restarts.

2. Repeat the above procedure to install OSs on additional hosts. N/A


When the OS installation progress bar for a host is displayed, you can begin installing
an OS on the other host.

3. If the host running the VRM node is also planned to carry service VMs and the TIP
service VMs need to use Huawei storage area network (SAN) devices, use After installing the OS on
commands to switch the multipathing mode of the VRM host to Huawei multipathing Host01, you can immediately
start to install the VRM node
mode after installing the OS on the two hosts. on Host01. During VRM
You can also switch the multipathing mode for the non-VRM host on the installation, you can install
FusionCompute web client. the OS on the other host at
the same time.

14
3.2 Install VRM
Step 1: Decompress the software packages.
1. Decompress FusionCompute V100R005C00SPC100_Tools.zip onto
the PC to obtain the Installer, ModCNABFileTool, PlugIn, ToDPS, N/A
and HostInstaller folders.

2. Decompress FusionCompute_V100R005C00SPC100_VRM.zip into a


new folder to obtain two VRM VM template files whose file name N/A
extensions are .ovf and .vhd, respectively.

Step 2: Initialize the installation wizard.


n
/e
m
The installation wizard is

o
opened.

i.c
Note

e
If an error is displayed
indicating that the .net
1. Run FusionComputeInstaller.exe in the Installer folder.

aw
Framework program is not

u
installed, run

.h
dotNetFx40_Full_x86_x64.e

i n g
xe in the PlugIn folder. Then
manually restart the local PC.
2. Select a language.
arn N/A
3. Select an installation mode.

//le
p :
t t
:h
The system begins to install
1 system components, which

e s takes about 30 seconds.

r c
ou
2

es
R The Configure Host page is

i n g
4. Click Next after the components are installed.
displayed.

r n
a
Step 3: Configure the host.

e Le
1. Configure the host where the VRM VM is deployed, then click Next. 1 Enter the management IP
address you set during host

o r installation.
2 Enter the password (not

M 1 the host BMC password) you


set during host installation.
Note
If a message is displayed
2 indicating that the host is
unreachable, ensure that the
IP address set in 1 is
3
correct and can be pinged
from the local PC.

15
Step 4: Configure a data store.

1. Select Local disk/FC SAN, then click Next.


You are advised to use local
2. The storage devices are automatically refreshed, and the system disks to install VRM.
adds the storage device in the first row as the data store by default. A VRM node requires 80 GB
space on the local disk.
If local disks are used, the active
and standby VRM nodes use
different disks, which provide
higher reliability.
You are advised to select disks
that constitute RAID 1 to
enhance reliability.
n
/e
The length of a RAID 1 disk is

m
generally twice as that of
common disks.
o
i.c
For details about VM storage

e
working principles, see

w
Appendix 2.

u a
Step 5: Configure VRM VM information.
g .h
i n
rn
1. Configure VRM VM template information.

le a 1 Select

://
FusionCompute_V100R005C0

tp
1 0SPC100_VRM.ovf.

t
2. Set the VRM VM management IP address.
s :h
r ce
s ou N/A

Re
n g
ni
3. Set VRM VM specifications.
r
e a You can set the specifications

L
based on the deployment scale

e
or customize the specifications.

o r VM to the right of By
deployment scale indicates the

M number of VMs required. PM


refers to the number of hosts
deployed.

4. Click Verify Configuration and click Next after the verification


N/A
succeeds.

16
Step 6: Configure the rights management mode.

1. Select a rights management mode as instructed.

N/A

n
/e
o m
e i.c
aw
u
g .h
Step 7: Install the VRM VM.
i n
arn The installation takes about 50

le
1. Click Next to start installing the VRM VM.
minutes.

: //
2. After the installation is complete, click the link on the displayed page
and log in to FusionCompute.

t t p Enter http://VRM

:h
Common mode
1 management IP address in

e s the address bar of the browser,

c
and enter the username and

r password to log in to

ou
2 FusionCompute.

es
Enter the username and password to log in to
The default username and
password are shown in the
FusionCompute.
R figure on the left.

n g
ni
3. Click Finish to finish the VRM VM installation.

a r
L e
r e
o
M

17
4 Configure FusionCompute
4.1 Log in to the FusionCompute Web Client.

To use Internet Explorer Step 1: Configure the Internet Explorer browser.


To use Mozilla Firefox Step 2: Configure the Mozilla Firefox browser.

Step 1: Configure the Internet Explorer browser.

1. Enter http://VRM floating IP address, for example, http://188.100.4.30/, in


n
/e
Internet Explorer 9 is
the address bar of the browser, press Enter, and select Continue to this
recommended.

m
website (not recommended).

o
2. In the upper right corner of the browser, click Certificate Error, and click
View certificates in the dialog box displayed. e i.c
1
aw
u
.h
After the certificate is
installed, FusionCompute

i n g will be recognized as a
secure site so users do not

arn need to install this


certificate again for

// le subsequent logins.

p :
2
t t
s :h
e
3. Click Install Certificate and click Next in the dialog box displayed.

r c
ou
4. Import the certificate to the system as the following figures instruct.

es
R
n g
r ni
e a1

eL
N/A
2

or
M 3

18
5. Click Finish, then click Yes in the dialog box displayed. A message is
displayed indicating that the import is successful. N/A

6. Click OK to close the certificate dialog box.

7. Hold down and press Shift+Ctrl+Delete.


8. Select the following options and click Delete to delete historical records. After the historical records
Preserve Favorites website data are deleted, restarting the
Temporary Internet files browser will make the
Cookies
n
/e
previous settings take
History effect.
9. Click Close to close Internet Explorer and open it again.
o m
10. Go to Step 3: Log in to the FusionCompute Web Client. N/A

e i.c
Step 2: Configure the Mozilla Firefox browser.
aw
u
.h
1. Enter http://VRM floating IP address, for example, http://188.100.4.30/ , in
With this setting
the address bar of the browser, press Enter, and select Continue to this
website (not recommended).
i n g configured, the
FusionCompute Web

rn
Client login page can
2. Expand I Understand the Risks and click Add Exception.

le a directly display when you


intent to log in to the client

//
3. Click Permanently store this exception in the dialog box displayed and
:
the next time.

p
click Confirm Security Exception.

t t
:h
Step 3: Log in to the FusionCompute Web Client.

e s
1.Enter http://VRM floating IP address in the address bar of the browser and

r c
ou
press Enter.
N/A

es
2. Enter the admin username and its password to log in to the Web Client.
The system asks you to change the initial password upon your first log in to
the system.
R
n g
r ni
e a
e L
o r
M

19
4.2 Add Hosts to the Cluster of Host01

Step 1: Add hosts.


Add all hosts other than the
1. On the FusionCompute web client, select Computing Pool. host running the VRM VM
to clusters.

2. Go to the Add Host page.

n
Right-click the cluster.

/e
2

m
3 N/A

o
e i.c
aw
u
.h
3. Set the host parameters, then click OK to complete the adding.

i n g
arn
//le
1
p :
t
After you set the host BMC

t
:h
information, you can power

s
on or off the host on

2
r ce FusionCompute.

s ou
Re
i n g 3

r n
e a
L
Step 2: Bind host management ports.

e
or
1. Go to the Bind Network Port page.
If ports eth0 and eth1 are

M 1
2 4
both common ports on the
management plane of the
host, bind them in
3
active/standby mode to
5 improve network reliability.
6

20
2. Locate the row that contains Mgnt_Aggr, then open the Add Network Mgnt_Aggr is a bound
Port dialog box. port automatically created
during host OS installation
that contains the
1 management port eth0
you configured. Select
2 another management port
eth1 and bind it to eth0 as
Mgnt-Aggr to improve
network reliability.

n
/e
3. Select the port name for eth1 to bind it to the management plane network
port PORTX in the displayed port list represents the network port ethx on
the host.
o m
e i.c
aw
u
1
g .h
i n
rn
N/A

le a
: //
t t p
:h
2

e s
r c
4. Click OK on the Bind Network Port page.

s ou
5. Bind eth0 and eth1 on the other host. For details, see 1 to 4.

Re
n g
r ni
e a
e L
o r
M

21
4.3 Add Storage Resources to a Site (SAN Storage)

1. Open the Add Storage Resource dialog box.

For details about network


communication between
2
hosts and storage devices,

n
/e
see Appendix 3.

o m
i.c
3

w e
2. Set the storage resource type to IP SAN, then click Next.
u3a The management IP
3. Set the storage device parameters, then click Add.

g.h address specifies the

i n storage device.

rn
1
2 4 5 An IP storage
3
le a area network (SAN) device

://
4
connects to a host through

tp
multiple storage links.
5
t
:h
Enter the information for all

s
links at one time.

r ce
ou
4. Click Next. N/A

es
5. Select the host to be connected to, then click Next.

R
6. Obtain the generated world wide name (WWN), then click Finish.

n g
r ni
e a
e L
o r
M

22
4.4 Add a Data Store to the Host (SAN Storage)
Step 1: Change the host multipathing mode.

1. Go to the Getting Started page of the host.


The default multipathing
mode for FusionCompute is
1 Universal. If a Huawei IP
SAN device is deployed,
change the mode to Huawei
to improve storage
2
n
performance. If non-Huawei

/e
3 storage devices are
deployed, skip this step.
m
4

o
2. Open the Configure Storage Multipathing dialog box. N/A
e i.c
3. Select Huawei.
aw
u
g .h
Restart the host for the
settings to take effect. The

i n restart process takes about

rn
1 3 minutes.

le a You can ping the IP address


of the host to check whether

: // the host has restarted. If the

t t p host can be pinged, the host


has successfully restarted.

:h
2

e s
r c
ou
Step 2: Add storage ports to the host.

es
R
1. Go to the Add Storage Port page of the host.

g
If you changed the multipathing mode of the host, perform this step after the

n
host restarts.

ni
ar
After storage ports are

L e added to the host, the host


can communicate with the

e
1

or
IP SAN device.

M 2

23
2. Select the host storage plane network , then click Next. The page for connection
PORTX indicates the network port ethX on the host. configuration is displayed.
3. Set the storage port parameters, then click Next.

The page for information


conformation is displayed.
The IP address is used to

n
communicate with the

/e
storage device. Set it to an
idle IP address on the

m
2
storage plane.
o
i.c
3

w e
u a
.h
The Finish page is displayed,

g
4. Confirm the information, then click Add. indicating that the port has

i n been added to the host.

arn
5. If multipathing mode is selected, click Continue and repeat 2 to 4 to add
multiple storage ports to the host. Click Close on the Finish page after all N/A
ports are added.

// le
p :
t
Step 3: Associate storage resources with the host.
t
:h
1. Go to the Associate Storage Resource page of the host.

e s
r c 1 After a storage device is

ou
associated with a host, the

es 2
host can discover all storage
resources on the device.

R
n g
ni
3

ar
The storage resource is

L e
2. Select the added storage resources, click Association, then click OK on
associated with the host.
After association, all

e
or
the displayed dialog box. associated storage
resources are displayed on
the Storage Resource page.
M
Step 4: Configure the initiator.
1. Choose Configuration > Storage Resource and record the host WWN
displayed in the bottom right corner of the page.
Storage devices identify a
host using the WWN of the
host.

24
2. Enter the storage device management IP address in the address bar of the
browser, then press Enter to load the storage device management software.
NOTE
The initiator can be
configured only on the
management interface of
the storage device.

The storage device

n
3. Select a language, then click OK. management software is

/e
open.
4. Click Discover Device. N /A

o m
i.c
5. Enter the administrator username and password to scan the storage

e
device.

aw
u
1
g .h
i n
arn
le
2 Enter the management

//
IP address of the storage

p : device.
2
t t
s :h
r ce
s ou
Re 3

n g
ni
6. Enter logical host view, then click Initiator Configuration.

1
a r
e 2 6

eL
5 Select the logical host

or
that matches the logical
unit number (LUN). The

M
selected host in the figure
3 is only an example.
5
4

25
7. Add the host WWN to the initiator.
1

2 Select the host WWN


you have recorded.

n
2
/e
o m
3
e i.c
aw
u
.h
Step 5: Add a data store.
1. Switch to FusionCompute and scan storage devices available to the host.

i n g
rn
A data store is used to
1

a
create user disks on VMs.

le
You can view the task

: // 2 progress on the Task

p
Tracing page.

t t
:h
3

e s
2. After the scan is complete, go to the Add Data Store page of the host.

r c
ou
1

es 2

R
N/A

n g
ni
3

a r
e
eL
3. Select a SAN device and add it to the host as a data store. 2 A virtualized SAN

or
storage device supports
advanced storage features,

M
such as thin provisioning,
1 snapshots, and live
storage migration, and
provides high resource
utilization. However, disk
creation on it is slow.
If you set this parameter to
Virtualization, you can
select whether to format
2
the data store. When a
data store is added to the
host the first time, the data
3 store must be formatted.

26
4.5 Add Virtual Network Resources to the Site
ISO
NOTE: If the service plane and the management plane are deployed on the same network plane, no service plane
distributed virtual switch (DVS) is required. Instead, you only need to add a service plane VLAN pool to the
management plane DVS.

Step 1: Create a DVS.


1. Go to the Create DVS page. Create a DVS that connects to
the service plane to provide
network resources for user VMs.
1
A DVS named
ManagementDVS for the
n
/e
management plane has been
automatically created during

o m
VRM installation, the bound

i.c
network port Mgnt_Aggr has
been added to the uplink group
e
on the DVS, and a
w
a
management plane port group

u
2 managePortgroup has been

.h
created.

g
For details about VM network

i n
access, see Appendix 1.

rn
2. Set the DVS name, then check the boxes next to Add uplink and
Add VLAN pool.

le a
1
: //
2
t t p
s :h N/A

e
3
4
r c
s 5
ou
Re
n g
ni
3. Select a service port for each host on the Add uplink page.

a r
e
An uplink is a physical port on a

eL
1 host that connects to a DVS.
VMs connect to the network

or
through the physical ports on
the host.

M Add all the hosts in a cluster to


the same uplink group on a
2 DVS. This allows VMs in the
cluster to have the most
migration options if a fault
occurs.

4. Click Next.
N/A
5. Click Add.

27
6. Set a VLAN pool on the DVS.
A VLAN pool defines the allowed
VLAN range for a DVS.
During service provisioning,
create port groups on the DVS for
1 each service. This allows each
port group to use VLANs from
2 different VLAN pools.
The VLAN pool set on the DVS
must be the same as the VLANs
set on the physical switch to which
n
/e
3 the host connects.

o m
i.c
7. Click Next.

8. Click Create.
N/A

w e
u a
g .h
i n
arn
//le
p :
t t
s:h
r ce
s ou
Re
n g
r ni
e a
e L
o r
M

28
4.6 Configure the NTP Clock Source and Time Zone

Step 1: Configure the Network Time Protocol (NTP) clock source.


1. On FusionCompute, click System. After an NTP clock source is
set, the time on all nodes in
2. Choose System Configuration > Time Management. the system is the same.
If multiple NTP servers are to
3. Set the NTP server information. be deployed, ensure that all
the NTP servers use the
same upper-layer clock
1 source to ensure time
n
/e
consistency.
This configuration requires a

m
restart of the FusionCompute

o
i.c
service process, which
2 interrupts services for about 2

w e
minutes. After the restart, log
in to FusionCompute and

a
continue to the next step.
u
.h
For details about time
3
synchronization, see

i n g
Appendix 4.

arn
le
Step 2: Configure the time zone.

: //
1. On the System page, choose System Configuration > Time Zone.

t t p
:h
2. Configure the time zone settings.

e s
1
r c 2 N/A

s ou
Re
3

n g
rni
e a
e L
o r
M

29
4.7 Create a Bare VM

Step 1: Select a VM Location


1. Go to the Create VM page. -
1

Right click
2
3

n
/e
o m
i.c
2. Select the location at which to create the VM. After the VM is bound to a host,
the VM can only run on this

e
A cluster is a group of hosts. host and cannot be migrated to
1
w
If there are no specific requirements for another host.
2
the location of a VM host, select Cluster.
The system will select a suitable host in
u a
.h
the cluster to create the VM on.

i n g
To deploy the VM on a specified host,
select Host. You can also check the box

rn
next to Bind to Host to bind the VM to
the host.

le a
3
: //
t t p
s :h
Step 2: Configure the VM Attributes
r ce
ou
1. Configure the VM attributes in the figure below based on the planned data. All other VM -

s
attributes use the default configuration.

e
R
1
n g
r ni
2
e a
e L
o r
M
2. Click Next to go to the Set VM page. -

30
Step 3: Configure VM Network Attributes
1. Select a VM NIC port group according to the VM network configuration requirements of A DVS is similar to a switch used
the customer. for communications on the
layer 2 network. The DVS allows
1 the VM to communicate with
the physical network.

2 A port group is a logical port of


the VM. The port group is used
to define the mode the VM NIC
3 uses to connect to the network.

n
/e
For details, see Principles of VM
Network Access.

o m
e i.c
aw
4
u
2. Repeat the above procedure to configure the port groups for other VM NICs.
g .h
i n
arn
Step 4: Configure VM Disk Attributes
// le
p : 2 The storage resource pool

t
1. Configure the VM attributes in the figure below based on the planned data.

t
associated with the host is used

:h
as the data store. The data
store is used to create VM disks.

e s For details, see Principles of VM

c
Storage Access.

r
ou
1 4 5 For virtualized data stores,
6
es VM4 disks can use the following
configuration modes:

R Common: Distributes disk

i n g 7
space according to capacity.
Immediate disk formatting.

r n Thick provisioning lazy

a
zeroed: Distributes disk space
2
e
according to capacity.

e L Delayed formatting. Above


average disk creation speed.

or
Thin provisioning: Distributes
disk space according to actual

M
usage.

3
2. Repeat the above procedure to configure the attributes of other VM disks.

3. After configuring all disks, click Next. Confirm the configuration information, then click -
Finish.

31
Step 5: Confirm VM Creation
1. Click Query Task. Enter the task center and check the progress of VM creation. -

The creation time of a bare VM depends on the VM disk size and disk storage type. The
formatting process for thin provisioning disks is relatively slow, please wait a moment.

4.8 Install an OS on the VM (Using a Windows VM as an Example)

n
Step 1: Log In to the VM Using VNC

/e
m
1. Use Virtual Network Computing (VNC) to log in to the VM, as shown in the following figure. VNC login refers to the process

o
1 of using VNC protocol to

i.c
remotely access a VM. VNC
login allows you to log in to the

w e
VM and locate faults through
the management plane when
2
u a
the VM network is unavailable.

g .h
i n
arn
le
://
3
4

t tp
:h
2. Select noVNC in the displayed dialog box. -
Accept the operation risks as prompted to open to the VNC window.

e s
r c
s ou
Click here for help with VNC login

Re
g
Step 2: Install an OS on the VM
n
rni
1. Mount the OS image from the CD/DVD-ROM drive to the VM. If only the OS installation disc is

a
available, insert the disc into
1
e
the CD/DVD-ROM drive, select

L
2 CD/DVD-ROM, and then specify

e
the drive name.

r
3

o 4

M 5

2. Restart the VM, then follow the instructions below to install the OS on the VM. -
Do not close the VNC window before the OS installation completes.
Otherwise, the CD/DVD-ROM drive is automatically unmounted from the VM,
NOTICE which causes the installation to fail.

3. After the OS is installed, click on the top of the VNC window, then select Do not close the VNC
window, as it is needed for
Unmount CD/DVD-ROM Drive. subsequent operations.

32
Step 3: Install Tools on the VM
1. Locate the row that contains the VM, click Mount Tools, then follow the procedure to Tools contains the
complete installation. paravirtualized (PV) driver for
the VM.
The PV driver improves I/O
processing, hardware
monitoring, and other high-
level functions on the VM.
Mounting Tools mounts a PV
driver to the VM.
1

n
/e
2. Open the CD-ROM drive on the VM. Right-click Setup, select Run as Administrator, and -
follow the procedure to complete installation.

o m
e i.c
aw
u
g .h
i n
arn
3. Restart the VM according to the procedure for Tools to take effect.

//le -

:
VMs running Windows Server 2008 must be restarted twice.

t t p
Step 4: Initialize the User Disk
s :h
r ce
1. On the OS interface on the VM, click Start, right-click Computer, and click Manage. The user disk refers to a disk
drive other than the C drive. If

ou
the VM does not have any user

s
disks, skip this step.

Re
2. Initialize the user disk. (Windows 7 is used as an example below.) 3 Select the layout of disk
partitions according to the user

n g requirements.

r ni
e a
e L
o r 2
M 1

3. Right-click the disk space that has not been distributed, select New Simple Volume, and -
follow the procedure to complete volume creation.

33
Step 5: Install Applications
1. If the VM uses VLAN to access the network, configure an IP address for the VM. This allows -
the VM to intercommunicate with external networks.

2. Install applications on the VM. Applications are installed on the


If the application is an ISO file or on a disc, you must use the CD/DVD-ROM mounting VM.
method to install the application.
All other types of installation files must be copied onto the VM before proceeding with
installation.

4.9 Create a Template n


/e
Step 1: Select the template creation plan.
o m
1. Select either of the plans to create a template based on actual requirements:
e
NOTE:
i.c
Convert a VM to a template:

w
Convert a VM to a template, select Plan 1.

a
All parameters of the template

u
Clone a VM to a template, select Plan 2. are from the VM. After a VM is

.h
converted to a template, the
VM is automatically deleted.

i n g Clone a VM to a template: A
copy of the VM is created, and

rn
you can customize some

a
parameters to make the

le
template different from the

//
original VM. After the VM is

p : cloned to a template, the

t
original VM can still be used.

t
Plan 1: Convert a VM to a template.
s :h
r ce
1. Locate the row that contains the VM, and choose More > Stop to stop the VM. When you convert a VM to a

ou
template, the VM must be in
the Stopped state.

es
1
R
n g
ni
ar
2

Le
2. Locate the row that contains the VM to be converted to a template and choose More > -
Convert to Template.

r e
o
M
1

3. Click OK in the displayed dialog box. -

4. Click OK in the displayed dialog box. -

5. Check whether the VM is successfully converted to a template on the Task Center page. -

34
Plan 2: Clone a VM to a Template

1. Locate the row that contains the VM and choose More > Stop to stop the VM. When you clone a VM to a
template, the VM must be in
the Stopped state.

2. Locate the row that contains the VM to be cloned to a template, and choose More > Clone -
to Template.
n
/e
o m
1
e i.c
aw
u
3. Select the template creation location. After the VM is bound to a host,

.h
the VM can only run on this
host and cannot be migrated to

g
1 A cluster is a group of hosts.
another host.
2
i n
If there are no specific requirements for

rn
the location of a VM host, select Cluster.

a
The system will select a suitable host in

le
the cluster to create the VM on.

//
To deploy the VM on a specified host,
:
p
select Host. You can also check the box

t t
next to Bind to Host to bind the VM to

:h
the host.
3

e s
r c
4. Configure the template name and hardware specifications based on the obtained data, -

ou
and click Next.

1
es
R
n g
ni
2

a r
L e
r e
o
5. Select the port group to which the VM NIC belongs based on customer requirements on A DVS is similar to a switch used
the network configuration of the template. for communications on the

M 1
layer 2 network. The DVS allows
the VM to communicate with
the physical network.
A port group is a logical port of
2 the VM. The port group is used
to define the mode the VM NIC
3 uses to connect to the network.
For details, see Principles of VM
Network Access.

4
35
Plan 2: Clone a VM to a Template

6. Configure disk attributes of the template based on obtained data. The parameters to be 2 The storage resource pool
configured are shown as follows. associated with the host is used
as the data store. The data
store is used to create VM disks.
For details, see Principles of VM
Storage Access.

n
/e
1

o m
i.c
4

w e
u a
g .h
n
2

i
arn
// le
p :
t t
:h
3

e s
c
7. Repeat the above procedure to configure attributes of other disks on the template.

r
ou
8. Click Next after all disks are configured, confirm the configurations, and click Finish. -

es
R
9. Check whether the VM is successfully cloned to a template on the Task Center page. -

n g
r ni
a
4.10 Create a VM Using the Template

L e
r e
o
Step 1: Create a VM Using the Template

M 1. Locate the row that contains the template and choose More > Deploy VM Using Template. This starts the process of
creating a VM using a template.

1
2

36
Step 1: Create a VM Using the Template
2. Select the VM creation location. After the VM is bound to a host,
the VM can only run on this
A cluster is a group of hosts. host and cannot be migrated to
1
If there are no specific requirements for another host.
2 the location of a VM host, select Cluster.
The system will select a suitable host in
the cluster to create the VM on.
To deploy the VM on a specified host,
select Host. You can also check the box
next to Bind to Host to bind the VM to
the host.
n
/e
3
o m
i.c
3. Configure the VM name and hardware specifications based on obtained data, and click Use the default values for all

e
Next. other attributes configurations.
You cannot set the number of

aw
disks or NICs when creating a

u
VM using a template.
1

.h
After the VM is created, you
can add disks and NICs to it.

2
i n g
arn
// le
p :
t t
s :h
r ce
ou
Step 2: Configure VM Network Attributes

es
1. Select the port group to which the VM NIC belongs based on customer requirements on A DVS is similar to a switch used

R
the VM network configurations. for communications on the
layer 2 network. The DVS allows

n g the VM to communicate with

ni
1 the physical network.

ar
A port group is a logical port of
2 the VM. The port group is used

L e to define the mode the VM NIC


uses to connect to the network.

e
3

or
For details, see Principles of VM
Network Access.

M
4

37
Step 3: Configure VM Disk Attributes

1. Configure the VM disk attributes based on the obtained data. The parameters to be 2 The storage resource pool
associated with the host is used
configured are as follows: as the data store. The data
store is used to create VM disks.
For details, see Principles of VM
Storage Access.

n
/e
1

o m
i.c
4

w e
u a
2
g .h
i n
arn
// le
p :
t t
:h
3

e s
c
2. Repeat the above procedure to configure attributes of other disks on the VM.

r
ou
3. Click Next after all disks are configured, confirm the configurations, and click Finish. -

es
4. Check whether the VM is successfully created on the Task Center page. -

R
n g
r ni
e a
e L
o r
M

38
5 Install FusionManager(Optional Task)

5.1 Install FusionManager Using a Template

Step 1: Decompress the FusionManager installation package.


Ensure that the folder
1. Create a folder named share on the local PC.
space is greater than 10 GB.

2.Use 7-Zip to decompress the FusionManager

n
V100R005C00SPC200_SV.zip file.

/e
The FusionManager V100R005C00SPC200_SV.7z file is obtained.

m
N/A

o
3. Use 7-Zip to decompress the FusionManager V100R005C00_SV.7z file.

i.c
The following files are obtained:
FusionManager V100R005C00SPC200_SV.ovf

FusionManager V100R005C00SPC200_SV-xvda.vhd

w e
4.Move the two files to the share folder, and share the folder with the
u a
The shared folder path

.h
cannot contain Chinese
current login user of the local PC.
characters.

i n g
Step 2: Create a FusionManager VM on FusionCompute.
arn
1. On FusionCompute, click VM and Template.
//le
p :
2. Click Import VM.
t t N/A

3. Select Shared directory, then click Next.


s :h
4. Configure template information.
r ce
s ou 1

Re
i n g 2 The path format is
\\Local PC IP

n
2

r
address\Name of the

e a folder containing the


template file.

e L
or
3 If the user account is
registered in multiple

M
domains, enter the
3 username with the
specified domain name,
for example,
CHINA\w00123456.

5. Set the creation location to Host.

39
Step 2: Create a FusionManager VM on FusionCompute.

6. Click Bind to the selected host and select Permanently reserve


resources for the VM.

7. Bind the FusionManager NIC to the DVS port group of the


management plane.

8. Configure the data store and configuration mode (Common or


Thick provisioning lazy zeroed) for the disk, and select N/A
Persistency.

n
The options Persistent and Nonpersistent are available for a VM

/e
disk only when the disk type is set to Common and the data store type
is set to Local Pome, LUN Pome, or NAS. For such disks, set
Persistency to Persistent. For disks using other types of storage

o m
i.c
resources, the Persistency attribute can only be Persistent, which is
the default setting and not available for selection.

w e
a
9. Configure VM information.

u
.h
3 This parameter is available if

g
1 the cluster has the GuestNUMA

i n
function enabled. The CPUs of a

rn
VM can be divided into multiple

a
groups. The one or multiple CPU

le
cores in each group are provided

//
by one or multiple cores of a
2
p : physical CPU. The number of
3
t t CPU cores in each group

:h
determines the number of CPU
4 cores allowed in a socket. The
5
e s number of sockets and the

c
number of CPU cores allowed in

r a socket vary depending on the

ou
OS capabilities. Set this

es parameter based on the actual

R
capability of the in-use OS. The
VM CPUs are recommended to

n g be evenly provided by the

ni
physical CPU.

e ar 5 In the CPU Resource

L
Control area, move the

e
Reserved (MHz) slider to the

or
maximum value. In the Memory
Resource Control area, move

M the Reserved (MB) slider to the


required value.

10. Keep the default values of other parameters, then click Next.

N/A
11. Click Create.
The creation process takes about 40 minutes.

40
5.2 Configure FusionManager

1: Configure the FusionManager VM.

1. On FusionCompute, log in to the FusionManager VM using VNC.


The login username is galaxmanager, and the default password is
Huawei@CLOUD8.

2. Run the following command to disable user logout upon system timeout:
TMOUT=0 N/A

n
3. Run the following command to start the configuration wizard:
/e
fmconfig
o m
4. Select OK to enter the configuration wizard.
e i.c
5. Select Next to enter the page for selecting the deployment mode.
aw
u
.h
6. Select Single mode.

i n g N/A

arn
// le
7. Select Next.
p :
t t
:h
8. Configure FusionManager VM information.

e s
c
1
r
ou
2

es 3

R
4 N/A

n g
r ni
e a
e L
o r 5

M If the entered
configuration information
9. Confirm that the configuration information is correct, then select Next. is incorrect, run stopALL
The system begins to configure the FusionManager VM. The configuration is to stop the process and
successful when the progress reaches 100% and the system displays a perform the configuration
success message. procedure again from
running the fmconfig
command.

41
5.3 Configure Time Synchronization and Time Zone

Step 1: Log in to the FusionManager web client.


1. Enter the FusionManager management IP address in the address box,
then press Enter.
The address format is http://FusionManager management node IP address, Internet Explorer 9 is
for example, http://192.168.210.60. recommended.
2. If no security certificate has been installed, click Continue to this website
(not recommended).
3. Enter the username and password.
n
4. Enter the displayed verification code. /e
Default username: admin
Default password:
Huawei@CLOUD8!
o m
i.c
5. Click Login.
If the system displays a message indicating that the login password must be
changed upon the first login or be reset, change the password as prompted.

w e
Step 2: Configure the time zone.
u a
1. On FusionManager, select System.
g .h
i n
rn
2. Choose System Configuration > Time Management.

le a
3. In the Time Zone area in the lower part of the page, check whether the

//
current time zone is the same as the local time zone. If different, change the
system time zone to the local time zone.

p :
t
N/A

t
s :h
r ce
s ou
Re
n g
Step 3: Configure the time server.

r ni
a
1. Configure the time synchronization function.
e
eL
1

or
M
2

42
6 Install the VSAM VM(Optional Task)

Step 1: Decompress the VSAM installation package.


1. Decompress the FusionCompute V100R005C00SPC100_VSAM.zip file.
The following files are obtained:
FusionCompute_V100R005C00SPC100_VSAM.ovf

FusionCompute_V100R005C00SPC100_VSAM-1.vhd N/A

2. Create a folder named share, move the two files into the folder, and share
the folder with the current login user of the local PC.

n
Step 2: Create the VSAM VM on FusionCompute.
/e
1. On FusionCompute, select VM and Template.
o m
2. Click Import VM. N/A

e i.c
3. Select Shared directory, then click Next.

aw
4. Configure template information.
u
g .h
n
1

i
rn
2 The path format is

a
\\Local PC IP

le
address\Name of the

//
2 folder containing the

p : template file.

t t
:h
3 If the user account is
registered in multiple

e s domains, enter the

r c 3
username with the

ou
specified domain name,
for example,

es CHINA\w00123456.

R
i n g 4

r n
5. Set the creation location to Host.

e a
6. Click Bind to the selected host and select Permanently reserve resources for the
VM.

e L
or
7. Configure the FusionManager NIC information on the management plane
DVS and port group.

M
8. Configure the data store and configuration mode (Common or Thick
provisioning lazy zeroed) for the disk, and select Persistency.
N/A

The options Persistent and Nonpersistent are available for a VM disk only
when the disk type is set to Common and the data store type is set to Local
Pome, LUN Pome, or NAS. For such disks, set Persistency to Persistent.
For disks using other types of storage resources, the Persistency attribute
can only be Persistent, which is the default setting and not available for
selection.

43
9. Configure VM information.

3 In the CPU Resource


n
/e
Control area, move the
2
m
Reserved (MHz) slider to

o
i.c
the maximum value.

e
4 In the Memory

3
aw
Resource Control area,
move the Reserved (MB)
u
.h
slider to the required value.

i n g
arn
// le
4

p :
t t
:h
10. Keep the default values of other parameters, select Customize using
s
e
the Customization Wizard, then click Next.

r c
11. Enter the VSAM VM name, leave Save as computer attributes
N/A

ou
unchecked, and click Next.

es
12. Configure VSAM VM NIC information.
R
n g
r ni
e a
eL
N/A

or
M

13. Click Next.

14. Confirm that the entered information is correct, then click Create. N/A

The creation process takes about 20 minutes.

44
Step 3: Configure the NTP server and time zone.
1. On FusionCompute, log in to the VSAM VM as user root using VNC.
The default root user password is Huawei@CLOUD8!.
2. Run the following command to disable user logout upon system timeout:
TMOUT=0
3. Run the following command to enter the configuration interface: N/A
python /opt/galax/vsam/tomcat/script/configvsam/ConfigVSAM.py
The following information is displayed:
START TO CONFIG VSAM !

n
please input the user gesysman's password[q/Q]:

/e
Password:

4. Enter the gesysman user password, which is GeEnginE@123 by default.


o m
i.c
The following information is displayed:
**************************************
* please choose your operation: *
w e
*
*
SET HA
SET NTP
:
:
0
1
*
*
u a
.h
* SET FTP : 2 *

g
* SET Time Zone : 3 *

i n
* SHOW ALL : 4 *
N/A

rn
* SHOW HA : 5 *
* SHOW NTP : 6 *
* SHOW FTP : 7 *

le a
//
* SHOW Time Zone : 8 *

:
* EXIT : 9 *

p
**************************************

t t
:h
please input your choice[0~9]:

5. Enter 1, then press Enter.

e s
r c
6. Enter the NTP server IP address, then press Enter.

ou
start to config ntp ! Configure the NTP clock

es
please input the ntp ip address: source preferentially to the

R
same external clock
7. Press Enter, set the synchronization interval (default: 64s), then press source used by both
Enter.

n g FusionCompute and

ni
8. Enable forcible clock synchronization (which is disabled by default), then FusionManager. If no
press Enter.
a r external NTP clock source
is available, configure the

L e
9. Configure the NTP network bridge address (which is not configured by clock source to the host

e
default), then press Enter. running the active VSAM

o r
10. Confirm that the entered information is correct, then press Enter.
VM.

M
The system begins to configure the NTP server.
11. Enter 3 and press Enter to configure the time zone.

start to config time zone info !


please input the time zone info [example:Asia/Hong_Kong]:
For more information about time zone, please refer to the following
directory :/usr/share/zoneinfo N/A

12. Enter the time zone, then press Enter.


13. Confirm that the entered information is correct, then press Enter.

45
7 Configure the Alarm Reporting Function
After installing FusionCompute, FusionManager, and VSAM, configure the function that allows
FusionCompute and VSAM to report alarms to FusionManager.
Step 1: Log in to FusionCompute.
1. Enter http://VRM IP address, for example, http://192.168.210.30, in the address box,
then press Enter. Internet Explorer
9 is
2. Enter the username and password and set the user type and login type. recommended.
3. Click Login.

n
/e
Step 2: Configure the FusionCompute alarm reporting function.

1. On FusionManager, select System.


o m
i.c
N/A
2. Choose Connect To > FusionManager.

w e
a
3. Configure the alarm reporting function.
1
u
.h
2 Set it to the
2

i n g FusionManager
management IP

rn
address if only

le a one

//
FusionManager

:
VM is deployed.
3
t t p
:h
Note: Before configure the alarm reporting function, enable port 18080 to allow VSAM to report alarms
s
e
to FusionManager. However, port 18080 is based on the insecure protocol HTTP. Therefore exercise

c
caution when deciding to enable this port.

r
ou
Step 3: Configure the VSAM alarm reporting function.

es
1. On FusionCompute, log in to the VSAM VM as user root using VNC.

R
The default root user password is Huawei@CLOUD8!.

n g
2. Run the following command to disable user logout upon system timeout:

ni
TMOUT=0

ar
3. Run the following command to query whether port 18080 is disabled.
e
N/A

L
iptables -S|grep 18080

e
If the following command output is displayed, the port is enabled. Go to Step 5.

or
-A VSAM_INPUT_CONTROL -p tcp -m multiport --dports 18080 -j ACCEPT

M
If no command output is displayed, the port is disabled. Go to Step 4.
4. Run the following command to enable port 18080:
sh /opt/galax/vsam/tomcat/script/setVsamHttpPort.sh open
If the following command output is displayed, the port is successfully enabled: N/A
modify config file success

5. Run the following command to configure the function that allows VSAM to report
alarms to FusionManager in real time:
sh /opt/galax/vrm/om/fms/bin/modGMIp.sh FusionManager management IP address
N/A
The configuration is successful if the following information is displayed:
modify GM IP Success.........

46
8 Add Resources to FusionManager

8.1 Create resource zones.


A resource zone is a logical container of resources virtualized in the hypervisor. Resources in a resource
zone belong to an independent layer 2 network and are managed as resource pools, including computing
resource pool, storage resource pool, and storage resource pools.

Step 1: Log in to the FusionManager .Web Client.


1. In the address bar of Internet Explorer, enter http://FusionManager

n
management IP address, press Enter, then select Continue to this This task uses Internet

/e
website (not recommended) to switch to the FusionManager Web Client Explorer 9.0 as an
login page. example.
For example, enter http://192.168.210.60.
o m
i.c
2. Log in to FusionManager as user admin.
The default password of user admin is Huawei@CLOUD8!.
After logging in to FusionManager for the first time, you need to change
N/A

w e
the login password as requested.

u a
Step 2: Create a resource zone.
g .h
i n
rn
1. On FusionManager, go to the Resource Zones page.

le a
1
: //
t t p N/A

s :h 2

r ce
ou
2. Click Create on the displayed page.

e
3. Configure zone information.s
R
n g
r ni
e a 1

eL
3 In this task, a

or
2 software VSA node
functions as the gateway
3

M
of the service network,
and no physical
networking is required.
Therefore, use the default
physical networking mode.

47
8.2 Add the Hypervisor to FusionManager
Add FusionCompute and VSAM to FusionManager so FusionManager can manage resources in the
hypervisor.

Step 1: Add the hypervisor to FusionManager.


1. Switch to the Hypervisor page.

n
2 -
/e
o m
e i.c
2. Click Add on the hypervisor page.
aw
u
.h
3. Configure the hypervisor access information.

1
i n g
rn
5 If only one VRM node
2
le a is deployed, enter the

//
VRM management IP
3

p : address and the default

t
port number 7443.

t
:h
4
6 Enter the name for

e s connecting the hypervisor


to FusionManager. The

r c 5 default username for

ou
connecting the

s
FusionCompute

Re hypervisor is gmsysman,
and the default password

i n g 6 is GMEnginE@123.

rn
8 If Update data

e a immediately after data


saving is not checked, the

e L system automatically

r 7 updates the hypervisor

o data periodically (every six

M
hours) to ensure data
consistency between
FusionManager and the
8
hypervisor.

4. Click Next.

48
Step 2: Add VSAM to FusionManager.
1. Configure VSAM access information.

3 5 If only one VSAM node


is deployed, enter the VSAM
4 management IP address and
the default port number
n
/e
18443.

m
5
6 The default username
o
i.c
for connecting VSAM to

e
FusionManager is gmsysman,
and the default password is

aw
GMEnginE@123.

u
6

g.h
i n
rn
7

le a
//
6. Click Next.

:
N/A

p
7. Confirm that the entered information is correct, then click Add.

t t
s :h
r ce
s ou
Re
n g
r ni
e a
e L
o r
M

49
8.3 Associate the Resource Cluster with a Resource Zone
Associate the resource cluster in the added hypervisor with a resource zone in FusionManager, so the
computing, storage, and DVS resources virtualized in the hypervisor are added to the computing, storage, and
network resource pools in FusionManager, respectively.

Step 1: Associate the resource cluster with a resource zone in FusionManager.

1. Go to the Resource Clusters page.

n
/e
N/A

o m
2

e i.c
aw
u
.h
2. Click Associate.

3. Associate the added resource cluster with a resource zone.


i n g
1
arn
// le
p :
t t
2

s :h N/A

r ce
s ou
3
Re
n g
ni
4. Click OK.

a r
L e
r e
o
M

50
8.4 Create AZs.
An availability zone (AZ) is a collection of logical resources that can be allocated to users.

Step 1: Create an AZ.

1. Go to the Resource Zones page.

n
2
/e
N/A
o m
2. Click the name of the target resource zone.
e i.c
The Summary page for the resource zone is displayed.
aw
u
3. Select Availability Zones.
g .h
i n
rn
4. Click Create.

5. Configure basic information for the AZ.


le a
1
: //
t t p
s :h
r ce N/A

s ou
Re
2
n g
r ni
e a
6. Add resource clusters to the AZ.

e L
o r 1
M The resource clusters
contained in an AZ must
2 be provided by the same
hypervisor.
4
3

7. Confirm that the entered information is correct, then click Add.

51
9 Configure Resource Pools

9.1 Add a VLAN Pool


To create service networks (external networks, internal networks, and routed networks) on FusionManager,
the VLANs used by these networks must be first added to the VLAN pools in FusionManager. Then
FusionManager can manage and allocate VLAN resources to the requested service networks in a unified
manner. VLAN pools in FusionManager are available only after being associated with the DVSs.

Step 1: Add a VLAN pool.

1. On FusionManager, choose Resource > Resource Zones, select a


n
/e
resource zone, then choose Network Resource Pools > VLAN Pools.
N/A

2. Click Create.
o m
3. Configure the VLAN pool information.
e i.c
aw
u
g .h
i n
rn
1

le a
3
: //
t t p
:h
4 4 Enter the service

e s plane VLAN range


configured on the switch.

r c
s ou
Re
n g5

r ni
e a
e L
o r
4. Click Create.
M

52
9.2 Create an External Network
Add an existing network that is connected to the Internet as the external network. After the external network is
added to FusionManager, FusionManager can manage the public IP addresses in the network and provide
public IP addresses for VMs to connect to the Internet through the software router.
Step 1: Create an external network.

1. On FusionManager, choose Resource > Resource Zones, select a


resource zone, and choose Network Resource Pools > External Networks.

2. Click Create. N/A

n
3. Set Connection Mode to Subnet (common VLAN) and Connect to
/e
Internet to Yes.
o m
4. Enter the external network name.
e i.c
1
aw
u
g .h
N/A

i n
arn
2
//le
p :
t t
:h
5. Select the required DVS, then click Next. Select the DVS with which
the external network

e s
6. Enter the external network VLAN, then click Next. VLAN is associated.

r c
ou
7. External subnet information for the external network.

es
R
n g
r ni1

e a
e L N/A

o r 2

8. Click Next.

9. Use the default QoS settings, then click Next.


N/A
10.Confirm that the entered information is correct, then click Create.

53
9.3 Create a VSA Management Network
The VSA management network communicates with the system management plane and assigns IP addresses
for system service VMs, such as the software router VM and internal DHCP server VM, so the system service
VMs can communicate with the VSAM and FusionManager nodes.
Step 1: Add a VSA management network.

1.On FusionManager, choose Resource > Resource Zones, select a


resource zone, and choose Network Resource Pools > VSA Network. N/A

2. Click Create VSA Management Network.

n
4. Enter the external network name.
/e
1
o m
e i.c
N/A

aw
u
g .h
2
i n
arn
le
5. Configure the VSA management network.

: //
1
t t p
s :h 6 Ensure that the VLAN

r ce of the VSA management


network has been added

ou
2 to the DVS in the

s
hypervisor

e
3
4 (FusionCompute) and the

R 4 VLAN is not contained in

i n g 5
the FusionManager VLAN
pool.

rn
6

e a
L
re
7

o
M
9. Remain the default settings for network port rate limit, then click Next.
N/A
10. Confirm that the entered information is correct, then click Create.

54
10 Prepare a VM Template

10.1 Import a VSA VM Template


The VSAM template is a system service VM template. When a tenant applies for a software router, the system
uses the imported VSA VM template to automatically create a system service VM functioning as a software
router for the tenant.

Step 1: Import a VSA VM template to FusionCompute.


1.Decompress FusionCompute V100R005C00SPC100_VSA.zip on the

n
local PC.

/e
The following files are obtained:
FusionCompute_V100R005C00SPC100_VSA.ovf
FusionCompute_V100R005C00SPC100_VSA-1.vhd
o m
i.c
2.Create a new folder, move the two files to the folder, and share the folder
with the current user of the local PC. N/A

w e
a
3. Log in to FusionCompute.

u
.h
4. On FusionCompute, choose VM and Template.
5. Click Import Template.

i n g
rn
6. Select Shared directory, then click Next.
7.Configure the template information.

le a
1
: //
t t p
2
s :h
e
3 Enter the username

r c and password for logging

ou
in to the local PC.

es
R 3

n g
r ni
e a 4

L
8.Select the creation location, then click Next.
e
o r
9.Configure the data store and configuration mode for the VM disks, then
select Persistent.
M
You are advised to deploy the VSA VM using a shared storage resource.
Otherwise, deploying the VSA VM concurrently in multiple clusters may fail.
N/A

10.Remain the default values of other parameters, then click Next.


11.Enter the name of the VSA VM template.
12.Remain the default values of other parameters, then click Next.
N/A
13.Confirm that the entered information is correct, then click Finish.
The creation process takes about 10 minutes.

55
Step 2: Discover the VSA template on FusionManager.

1. Log in to FusionManager.

2. Choose Resource > VM Templates.

3. Click Discover.

4. Discover the VM template available in the hypervisor.

n
1
/e
o m
2
ei.c
5. Click OK.
aw
u
g.h
Step 3: Change the VM template type.
i n
arn
1. Locate the row that contains the discovered VSA template, then choose
More > Modify VM Template Information.

//le
2. Change the template type.
p :
t t
s :h
r ce
s ou
Re
i n g 1

r n
e a
e L
or 2
M

56
10.2 Create a VM Template
Create a VM template based on the OS type and VM specification requirements of the needed VMs. The
template can then be used to create new VMs with the same specifications as the template, which
significantly shortens the time for configuring new VMs and installing OSs on them.

Step 1: Create a VM template.


1. On FusionManager, choose Resources > VM Templates.
Note: FusionManager
does not support VM
2. Click Create. template creation if it
uses local disks as

n
3. Configure basic information for the VM. storage resources.
1
/e
o m
i.c
2

w e
a
3

u
4
g.h
i n
arn
//le
p :
5
t t
4. Configure the VM template specifications.
s :h
1
r ce
s ou
2

3
Re
n g
ni
4

ar
5

L e 6

e
or
7

M 8

5. After the VM is created, click Next.


The Install Software page is displayed. On this page, you can log in to the
VM using VNC and install an OS and Tools and configure NICs and disks for
the VM.

57
Step 2: Install an OS for the VM.

1. Click on top of the VNC window and mount the OS CD/DVD-ROM


drive or ISO image file to the VM.

SUSE Linux Enterprise


Server 11 is used as an
2 example in this task.

n
3 /e
4
o m
5
e i.c
aw
Note: Do not close the
u
2. After the VM restarts, install the OS on the VM as prompted.

.h
The OS installation method for a VM is similar to that for a physical computer. VNC login window before
OS installation is

3. After the OS is installed, click on the top of the VNC window, then
i n g complete. Otherwise, the
CD/DVD-ROM drive is

rn
select Unmount CD/DVD-ROM Drive. automatically unmounted

a
from the VM

// le
4. Install the OS patch. The patch file must be mounted to the VM as an ISO
file.
p : N/A

t t
Step 3: Disable the firewall on the VM.
s :h
1. Log in to the VM as user root.
r ce
ou
2. On the VM desktop, choose Computer > YaST.
s
e
The YaST2 Control Center window is displayed.

R
3. Select Security and Users from Groups and click Firewall in the right

g
pane. The YaST2 window is displayed.
n
rni
4. Select Disable Firewall Automatic Starting from Start-Up and click Stop

a
Firewall Now.

Le
5. Click Save Settings and Restart Firewall Now.

r e
6. Click Next.
o
A confirmation dialog box is displayed.

M
7. Click Yes.
A confirmation dialog box is displayed.

8. Click Finish.
The YaST2 window is closed.
9. Right-click the VM desktop and choose Open in terminal from the
shortcut menu.
The system switches to the CLI.

10. Run the reboot command to restart the VM.

58
Step 4: Install Tools.
1.Decompress the FusionCompute
V100R005C00SPC100_GuestOSDrivers.zip software package on the local
PC.
The FusionCompute V100R005C00_GuestOS.iso file is obtained.
2.Use VNC to log in to the VM as user root and mount the ISO image
FusionCompute V100R005C00SPC100_GuestOS.iso to the VM.
3.Right-click on the VM desktop and select Open in terminal from the
shortcut menu.
The system switches to the CLI.
4.Run the following command to create the xvdd directory:
n
mkdir xvdd
/e
5.Run the following command to mount the ISO image to the VM:
o m
i.c
mount Target directory xvdd
For example, run mount /dev/sr0 xvdd to mount the ISO file to the /dev
directory on the VM running SUSE Linux Enterprise Server 11.

w e
a
6.Run the following command to switch to the xvdd/pvDriver/linux directory:

u
cd xvdd/pvDriver/linux
7.Run the following command to view the required Tools installation package:
ls
g.h Tools improve I/O
processing, hardware
The following information is displayed:
i n monitoring, and other

rn
... advanced functions on a

a
uvp-tools-linux-xxx.tar.bz2 VM.

le
uvp-tools-linux-xxx.tar.bz2.sha256

: //
8.Run the following commands to copy the Tools installation package to the
root directory:
cp uvp-tools-linux-xxx.tar.bz2 /root
t t p
:h
cd /root

e s
9.Run the following command to decompress the Tools software package:

c
tar -xjvf uvp-tools-linux-xxx.tar.bz2

r
ou
10.Run the following command to switch to the Tools installation directory:

s
cd uvp-tools-linux-xxx

Re
11.Run the following command to install Tools:
./install

g
Tools installation is complete if the following command output is displayed:

n
ni
The PV driver is installed successfully. Reboot

r
the system for the installation to take effect.

a
L e
12. Run the following command to restart the VM for Tools to take effect:

e
reboot

o r
13.Use VNC to log in to the VM as user root again.

M
14.Right-click the VM desktop and choose Open in terminal from the
shortcut menu.
15.Run the following command to check whether Tools installation is
successful: N/A
ps -ef | grep uvp-monitor
Tools installation is successful if the command output contains the bold
characters as follows:
root 4561 1 0 Jun29 ? 00:00:00 /usr/bin/uvp-monitor
root 4567 4561 0 Jun29 ? 00:00:00 /usr/bin/uvp-monitor
root 6185 6085 0 03:04 pts/2 00:00:00 grep uvp-monitor

59
Step 5: Configure the VM NIC.
1. Run the following command on the VM to view the files in the network rule
directory:
ls l /etc/udev/rules.d
2. Run the following commands to delete the rule files whose file names contain
persistent and net in the network rule directory:
For example:
rm -r /etc/udev/rules.d/30-net_persistent-names.rules
rm -r /etc/udev/rules.d/70-persistent-net.rules
The italicized content in the command varies depending on the actual service

n
environment

/e
N/A

m
3. Decompress the software package FusionCompute
V100R005C00SPC100_GuestOSDrivers.zip on the local PC.
o
i.c
The FusionCompute V100R005C00SPC100_Customization.iso file is obtained.

4. Mount the FusionCompute V100R005C00SPC100_Customization.iso file to


w e
the VM.
u a
.h
This file is used to configure the VM to automatically obtain an IP address using
the DHCP service.

i n
5. Copy the linux folder in the ISO file to the /home directory on the VM. g
arn
6. Run the following command to back up the original NIC configuration file and

le
create a new configuration file for the NIC:

//
sh /home/linux/autoConfigLinuxNetwork.sh /etc/sysconfig/network

p :
The command is executed successfully if the following information is displayed N/A
backup old config files ...
t t
:h
create new config files ...

s
done !!!

r ce
7. Run the following command on the VM to switch to the control center:

ou
yast

s
8. Choose Network Devices > Network Settings.
e
R
9. Hold down Alt and press G on the Network Settings page. N/A
g
The Global Options page is displayed.
n
r ni
10. Hold down Alt and press T, and select Traditional Method with ifup.

e a
11. Press F10 to save the configurations and exit the control center.

e L
o r
M

60
Step 6: Configure the VM template.
1. Run the following command on the VM to open the rc file using the visual
interface (vi) editor: Note:
vi /etc/init.d/rc Back up the rc file before
editing it.
2. Press i to enter editing mode.

3. Add a command statement based on the following requirements:


If exit 0 is displayed at the end of the file, add sh
/etc/init.d/setpasswd.sh in the line before exit 0.
If exit 0 is not displayed at the end of the file, add sh
/etc/init.d/setpasswd.sh at the end of the file.
n
4. Press Esc, enter :wq, and press Enter.
/e
The system saves the configurations and exits the vi editor.
o m
Step 7: Initialize the user disk.
e i.c
1. Run the following command on the VM to query user disk information:
aw
u
.h
ll /dev/xvd*
brw-rw---- 1 root disk 202, 0 08-15 16:13 /dev/xvda
brw-rw---- 1 root disk 202, 1 08-15 16:13 /dev/xvda1
brw-rw---- 1 root disk 202, 2 08-15 16:13 /dev/xvda2
i n g xvda indicates a system
disk, xvdd indicates the
brw-rw---- 1 root disk 202, 48 08-15 16:13 /dev/xvdd
brw-rw---- 1 root disk 202, 64 08-15 16:13 /dev/xvde
arn CD/DVD-ROM drive, and
xvde indicates a user disk.
brw-rw---- 1 root disk 202, 65 08-15 16:13 /dev/xvde1

// le
brw-rw---- 1 root disk 202, 66 08-15 16:13 /dev/xvde2

p :
t t
:h
2. Run the following command to format the user disk:
mkfs.ext3 -F /dev/xvde

e s
c
3. Run the following commands to attach the user disk to the VM:
mkdir /usr/xvde
r
ou
mount /dev/xvde /usr/xvde/

es
4. Run the following command to query the information about the user disk:
df h
R N/A
g
The user disk is successfully attached to the VM if a capacity value is displayed for

n
ni
the xvde disk.
File System Capacity Used Available Usage Mounting Point

a r
/dev/xvda2 19G 3.1G 15G 18% /
devtmpfs
tmpfs
L e 465M 108K 465M 1%
465M 100K 465M 1%
/dev
/dev/shm

r e
/dev/xvde 20G 173M 19G 1% /usr/xvde

o
M
5. Run the following command to open the fstab file using the vi editor and
enable automatic disk attaching:
vi /etc/fstab

6. Move the cursor to the end of the file, press Enter, and enter the following
N/A
line:
/dev/xvde /usr/xvde/ ext3 defaults 0 0

7. Press Esc, enter :wq, and press Enter.


The system saves the configurations and exits the vi editor.

61
Step 8: Complete VM template creation.

1. FusionManager, choose Resource > Templates and Specs .

2. Locate the row that contains the VM template, then choose More > Install
Software.
N/A
The Install Software page is displayed.

3. Click Complete.
The VM Templates page is displayed., on which the VM template status is
Complete. After the VM is created, the CD/DVD-ROM mounted to the VM is
automatically unmounted.
n
/e
o m
ei.c
aw
u
g .h
i n
arn
// le
p :
t t
s :h
r ce
s ou
Re
n g
r ni
e a
e L
o r
M

62
11 Create a VDC
A virtual data center (VDC) is the unit of using virtual resources on FusionManager. Create a VDC for a
service department and create a VDC administrator. Then the VDC administrator can manage resources in
the VDC and allocate the resources to user VMs in the VDC.
Step 1: Create a VDC.
1. On FusionManager, choose VDC > VDCs.
The VDC management page is displayed.

2. Click Create VDC.

n
/e
3. Configure the VDC information.

1
o m
2
e i.c
aw
u
g.h 3 Configure the

i n maximum amount of

rn
resources allowed for the

a
3 VDC. These settings can

le
also be modified after the

: // VDC is created.

t t p
s :h
r ce
s ou
4. Click Next.
Re
g
5. Select an AZ, then click Next.
n
ni
6. Select an external network, then click Next.
r
e a
7. Select VDC members, then click Next.

L
8. Confirm that the entered information is correct, then click Create.
e
o r
9. Repeat step 2 to step 8 to create VDC02 and VDC03.

MStep 2: Create the VDC administrator.


1.Locate the row that contains the created VDC, then choose More >
Member Management. The created VDC
administrator can manage
2. Click Create User.
the resources available in
3. Set the username, password, and role, then click Create. the VDC.
To create a VDC administrator, select the vdcmanager role.

63
12 Create a VPC and Networks

12.1 Create a VPC


Create a VPC to provide VDC tenants with a secure and isolated network environment. The VDC
administrator can create virtual networks in a VPC to provide VDC tenant VMs with the same network
functions as those provided by a traditional network.

Step 1: Log in to FusionManager.


After logging in to
n
/e
FusionManager for the
1. Log in to FusionManager as the VDC administrator. first time, you need to

o m
change the default login
password as requested.

Step 2: Create a VPC. e i.c


aw
1. Choose VPC > My VPC.
u
2. Click Create VPC.
g .h
i n
rn
3. Configure the VPC information.

le a
//
1

p :
2
t t
3
s :h
r ce
s ou
R
4e
n g
ni
5. choose Custom, then click Next.

ar
N/A
6. Click Create.

L e
e
or
M

64
12.2 Apply for a Router
Apply for a router for the VPC so that the router can serve as a gateway for the routed networks created in the
VPC. The router also supports the elastic IP address function, which allows an elastic IP address to be bound
to the VM so the VM can connect to public networks.

Step 1: Go to the VPC configuration page.


ISO
1. Click the name of the created VPC (VPC01).

n
/e
o m
i.c
1

w e
a
2. On the displayed VPC01 configuration page, choose Routers.

u
3. Click Apply for Router.

g .h
4. Apply for a router.
i n
arn 1 A software router is

le
deployed on a VSA VM to

//
provide firewall functions.

p : The administrator can

t
1 apply for a software router

t only after creating the

:h
VSA management

e s network and importing the

c
VSA template to the

r system. For details about

ou
the software router
2

es functions, see Appendix 6.

R
n g
ni
3

a r
L e
r e
o
M

65
12.3 Create a Routed Network
VMs deployed in a routed network can have their private IP addresses bind to an elastic IP address through
a router, so the VMs can use the elastic IP address to provide public network access services.

Step 1: Create a routed network.

1. On the VPC01 page, choose Network> Network.


A routed network can
provide VMs with elastic
2. Click Create.
IP address and destination
network address
3. Enter the routed network name and set the network type to Routed
translation (DNAT)
n
/e
Network. functions through the
router. The router also

m
supports configuration of

o
i.c
access control list (ACL)
rules to control the data
4. Click Next.

w e
traffic inbound to or
outbound from the routed

a
network to improve
u
.h
network security.

4. Configure VLAN information for the routed network.


i n g
1

arn
//le
:
2

p
2

t t Enter a VLAN ID

:h
planned for routed
networks.

e s
r c
3
s ou
5. Configure subnet information.
Re
n g
ni
ar
1

L e 2
The VDC

e
or
administrator can
2 customize the subnet IP

M
address for the routed
network.

6. Click Next.

7. Confirm that the entered information is correct, then click Create.

66
13 Provision VM

13.1 Create the VM


The VDC administrator can select a created VM template and specify the specifications and network to
create a VM with the same configuration as the template.

Step 1: Create the required VM.

1.On the web client page in tenant view, choose Resources > Computing > N/A
VMs.

n
/e
2.Click Create.

3.Select a VM template, then click Next.


o m
4. Configure the VM specifications.
e i.c
aw
1
u
g .h
2
i n
arn
3
//le
p :
t t
s :h
4

r ce
5. Select a network. 1
s ou
Re
i n g 2
Add the VM NIC to

r n 3 3 routed network
the

e a created in 11.3.

e L
or 4

M
6. Enter the VM name, then click Next.

7. Confirm that the entered information is correct, then click Complete.


The system begins to create the VM.

Step 2: Install the application software.


1. Mount the ISO file of the application software to the VM to install the
application software on the VM.
You can use any ISO image creation tool, such as UltraISO and ISOMaker, to create
an ISO file for the desired application software.

67
13.2 Bind an Elastic IP Address to a VM
Elastic IP address is a public IP address that can be bound to a VM or a private IP address to enable the VM
to provide external services using the public IP address. Apply for an elastic IP address before binding the
elastic IP address to a VM.

Step 1: Apply for an elastic IP address.

1. On the VPC01 configuration page, choose Network > Elastic IP


Addresses.
2. Click Apply For.
A message is displayed indicating that elastic IP address application is
n
/e
successful.

m
3. Click OK.
The requested elastic IP address is displayed.
o
The requested elastic IP

i.c
address is obtained from a

e
subnet from the created

w
external network.

u a
Step 2: Bind the elastic IP address to the VM.
g .h
i n
1. Locate the row that contains the obtained elastic IP address, then click

rn
N/A
Bind.

2. Bind the elastic IP address to the VM.


le a
: //
t t p
:h
1

e s
r c
s ou
2
Re
n g
rni 3

e a
L
4

r e
o
MVerify the Elastic IP Address Bound to the VM
Ping an IP address in the external network using the elastic IP address
bound to the VM to check whether the VM can communicate with the external
network using the bound elastic IP address.

68
13.3 Add ACL Rules
Add ACL rules in the VPC to allow users to access the web services deployed on a specific VM using only
the TCP protocol and port 80. This configuration prevents unauthorized users from accessing the web
services and thereby improves network access security.
Note: The system allows services access using any supported port and protocol by default. To allow VMs to
access services using only the specified protocol and port number, you need to first add an ACL rule that
prohibits service access using any protocol or port, and then add another higher-priority ACL rule that
specifies the protocol and port number allowed for service access.

Step 1: Prohibit access to the web-service-deployed VM using any protocol and port.
IN indicates the control for
1. On the VPC01 configuration page, choose Security > ACLs.
network packets inbound to

n
the VM. OUT indicates the

/e
2. On the IN page, click Add Rule. control for network packets
outbound from the VM.

3. Configure ACL rules.


o
1 Set the ACL rule ID m
i.c
representing the rule priority.

1
w e
If multiple ACL rules contain
the same rule configuration,

u a
the rule with the smaller rule
ID takes effect preferentially.
2
g .h
You are advised to number
two adjacent rules with a
3
i nstep of 10 numbers to

rn
4 facilitate adding more sub-

5
le a rules in future.

: // 5 Set the elastic IP

t t p 6 address bound to the VM on


which the configured ACL

:h
rule takes effect.

s
7

e
6 Set the IP address of the

r c VMs to access the services.

ou
8 0.0.0.0 indicates all IP

s
addresses.

Re
Step 2: Specify the protocol and port number allowed for VM access.

n g
1. On the IN page, click Add Rule.

r ni
2. Configure the ACL rules.

e a 1 The ACL rule configured

e L 1
in the preceding step

r
prohibits the access to the

o web service VM. The ACL

M
2 rule to be configured in this
step allows access to the
3
VM using the TCP protocol
4 and port number 80. This
5 ACL rule (10) has the higher
priority than the ACL rule 20
6 configured in the preceding
step.
7
8

69
Appendix

Appendix 1 Principles of VM Network Access


A virtual NIC of a VM communicates with an external network by connecting to the DVS through the
port group, then by connecting to the physical NIC of a host through the DVS uplink. These connections
are shown in the following figure.

Host1 Host2

VM1 VM2
VPC
n
/e
o m
i.c
Routed network1 Routed network2
Router VLAN 11
192.168.11.0/24
VLAN 12

w e
192.168.12.0/24

Gateway 192.168.11.1; 192.168.12.1


u a
External network
g .h
VLAN 2 192.168.2.0/24
i n
Port Group VLAN 2 VLAN 11
arn
le
VLAN 12

Virtual
: //
resources

t t p DVS

s :h Uplink

Physical
resources
r ce
s ou
Re Physical network

n g
r ni
Network
e a Description
L
Element

r e A software router functions as a gateway that enables VMs in a VPC to communicate

o
Software with VMs in other routed networks. The software router connects to the public network

M
router through the external network and therefore provides IP addresses for VMs to access
external networks.
A port group is a virtual logical port similar to a template with network attributes. A port
Port group group is used to define VM NIC attributes and uses a DVS to connect to the network:
Each service network (internal, routed, and external networks) created on
FusionManager maps a port group on the DVS.
A DVS provides the same functions as a physical layer 2 switch. A DVS links port groups
DVS
to VMs and connects to the physical network through uplink channels.
An uplink connects the DVS to the physical network NIC and therefore can transmit the
Uplink
data from the VMs connected to the DVS to the physical network.

70
Appendix 2 Principles of VM Storage Access
A data store is a logical storage unit on FusionCompute. A data store is used to universally define all
types of storage resources.
You can create a virtual disk on a data store for use by a VM.

Host local disk

n
/e
VM
LUN
Virtual disk
o m
Data store
IP SAN storage
e i.c
aw
u
g .h
Host

ni n Shared storage

ar
e
/: /l
Appendix 3 Network Communication Between Hosts and IP SAN Devices

Logical layer:
t tp
h
After a storage device is
associated with a host, the host
bus adapter (HBA) generates a
s : Host IP SAN device
WWN for the host.

r ce
After an initiator is added to the LUN01
u
logical host on the storage device

o
s
using the host WWN, the host can
WWN

LUN02

e
access the storage resources
Initiator

R
(LUNs) that match the logical host

g
on the storage device and add the

n
LUNs as data stores.
Controller

ni
HBA

a r Logical host

L e
e
Logical association

or Physical association

MPhysical layer:
A host connects to an IP
SAN device through
multipathing.
Switch

Storage NICs on the host


connect to the storage
NICs on the storage device
controller.

71
Appendix 4 Principle of Clock Synchronization

After the NTP clock source is


NTP clock
configured, all hosts, VRM source
VMs, and FusionManager
VMs synchronize time from FusionManager
the NTP clock source to
VRM
n
ensure system time accuracy.

/e
o m
e i.c
aw
u
Hosts in the management cluster

g .h Other hosts

i n
arnCommands
e
/: /l
Appendix 5 Setting Multipathing Mode for a Host Using

tp
1. After the OS is installed on the host and the host restarts, log in to the host as user

t
root in the remote control window, and run TMOUT=0 to disable logout on timeout.

h
:
The password of user root

e s is the password you set

c
during host OS installation.

ur
s o
e
2. Run the following command to set the multipathing mode to Huawei mode:

R
sh /opt/uvp/multipath/change_multipath_mode.sh 1

n g N/A

r ni
The command is executed successfully if the message "Enable ultrapath

e a
successfully" is displayed.

L
3. Run reboot to restart the host for the mode to take effect:

e
or
M
N/A

72
Appendix 6 VSAM and VSA

The VSAM node is deployed on the FusionManager management plane to manage VMs that provide VSA
system services, including software router and DHCP.

Management VSA management


network network

VSA VSA

n
/e
DHCP VSA

VPC1 VPC2

VPCn
o m
i.c
FusionManager
node VSAM node

w e
VM
u a
.h
VM VM
Service networks

i n g
rn
VM VM VM

Network
le
Network Network a
1 2
: //
n

t t p
:h
The VSA management network connects to the management networks of the FusionManager node and the
VSAM node to enable communication between VSA VMs and the VSAM node. When a tenant applies for a

s
software router or the DHCP service for a VPC, FusionManager creates a VSA VM using the VSAM node
e
c
and automatically deploys the virtual firewall or DHCP service on t he VSA VM. A software router functions
r
ou
as a firewall that connects to the Internet-accessible external network to provide public IP addresses for
VMs in the VPC to access public networks.

es
R
n g
r ni
e a
e L
o r
M

73
02 HCNA-Cloud V2.0
FusionAccess Installation

Issue: 01
Date: 2015-07
e n
/
m
.i co
Introduction to the FusionAccess

w e
Huawei FusionAccess is virtual machine (VM)
u a
management software deployed on a virtualization
. h
platform. It enables users to access virtual desktops
n g
ni
by using networked client devices, such as thin

r
clients (TCs), desktop computers, laptops, and
smartphones.

le a
FusionAccess transforms the traditional PC-
: //
dominated office model with features such as
security, investment, and office efficiency. It is an
t t p
:h
optimal choice for large- and medium-sized

s
enterprises, government agencies, and mobile
offices.

r ce
s ou
Objectives
Re
This guide helps you quickly deploy FusionAccess. For more information about the installation and

Guide.
i n g
configuration of FusionAccess, see the FusionCloud Desktop Solution V100R005C20 Software Installation

r n
1. Preparing Network Resources------------------------------------------------------------------------------------- P8

e a
2. Installing Linux Infrastructure Components-----------------------------------------------------------------------P10

e L
1) Creating Linux VMS-------------------------------------------------------------------------------------------P10
2) Installing the GuassDB/HDC/WI/License Components-----------------------------------------------P17

or 3) Installing the vAGyLB Components------------------------------------------------------------------------P20

M
3. Installing Windows OS Infrastructure Components--------------------------------------------------------------P24
1) Creating an Infrastructure VM Template----------------------------------------------------------------P24
2) Creating and Setting Infrastructure VMs----------------------------------------------------------------P30
3) Installing the AD/DNS Services-----------------------------------------------------------------------------P34
4) Installing the DHCP Service----------------------------------------------------------------------------------P41
5) Creating Domain Accounts----------------------------------------------------------------------------------P45
6) Configuring Backup and Perfoming Security Hardening---------------------------------------------P50
7) Configuring DNS Policies------------------------------------------------------------------------------------P52
8) Installing the ITA----------------------------------------------------------------------------------------------P54
4. Initial Configuration-----------------------------------------------------------------------------------------------------P62

1
1 Overview
FusionAccess consists of the access control layer, virtual desktop management layer, and operation and
maintenance (O&M) layer.

WI
The WI provides an interface for users to
access their VMs.
ITA
The IT adapter (ITA) provides an interface

e n
/
for virtual desktop management. The ITA
works with the Huawei Desktop Controller
m
.i co
(HDC) and the virtualization software
FusionCompute to implement functions,
such as VM creation and provisioning, VM
status and image management, and virtual
w e
a
desktop O&M.

HDC
hu
g .
The HDC processes VM registration requests, manages desktop groups, and assigns and unassigns VMs

n
for users.

ni
License
The license server manages and distributes licenses for the HDC.
ar
le
GaussDB

//
The GaussDB stores data for the ITA and HDC.
Loggetter

p :
t
The Loggetter records information about user operations, key points, and information returned during the

t
system installation and operating process. The information helps locate faults.

:h
vAG/vLB

s
The vLB provides the load balancing function and selects a proper WI for end users. The vAG provides an

e
c
access gateway to ensure the security when end users access VMs, and provides the Virtual Network

r
Computing (VNC) access gateway function. When a VM is faulty, the user can log in to the VM by using

ou
VNC.
TCM

es
The thin client manager (TCM) centrally manages TCs, for example, delivering TC certificates and
R
collecting logs. For the TCM installation, see the related TCM documents.

i n g
The deployment of the components in a typical desktop cloud scenario is as follows:

Component
rn Number of VMs Software

e a Windows operating system (OS) and AD/DNS/DHCP

L
AD/DNS/DHCP 2
component software

e
or
Linux OS andGauss DB/HDC/WI/License component
GaussDB/HDC/WI/License 1
software

M DB/HDC/WI 1

2
Linux OS and DB/HDC/WI component software

Windows OS and ITA component software


ITA

Loggetter 1 Windows OS and Loggetter component software

vAG/vLB 2 Linux OS and vAG/vLB component software

Note: When the vAG does not provide the Huawei Desktop Protocol (HDP) access gateway function, the
preceding deployment scheme supports a maximum of 5000 users; when the vAG provides the HDP access
gateway function, the preceding deployment scheme supports a maximum of 500 users.

2
2 Installation Process
1. Install FusionCompute.
During the desktop cloud environment deployment, you need to install and configure the low-layer
virtualization platform, that is, FusionCompute. For details about the installation, see the (Quick Guide)
FusionCompute V100R005C00 Quick User Guide. The following table describes some data
requirements for the FusionCompute Installation.
Item Requirement
Installation mode Install active and standby VRM modes.
e n
/
Domain 0
m
The Domain 0 specifications of the management, and user clusters, and gateway clusters

.i co
specifications vary with the number of VMs on a host:
max_vcpus and reserve_vcpus: 6VCPU

e
mem(MB): 5120 MB

w
mem_for_icache(MB)

a
Common VM: Default 0

u
Linked clones: 12288

VRM VM 200 VMs, 20 physical hosts: 2 VCPUs, 3 GB memory


. h
specification 1000 VMs, 50 physical hosts: 4 VCPUs, 5 GB memory

n g
ni
requirements: 3000 VMs, 100 physical hosts: 8 VCPUs, 8 GB memory

r
5000 VMs, 200 physical hosts: 12 VCPUs, 16 GB memory

Add Data Store

le a
FusionAccess infrastructure VMs must use unvirtualized storage. When adding data

//
storage for a FusionAccess VM, set Storage mode to Non-virtualization.

NTP server of
p :
If the Network Time Protocol (NTP) server is available on the site, set this parameter to
FusionCompute the site NTP server.

t t
:h
If no NTP server is available on the site, set this parameter to VRM.

process is as follows:
e s
2. Install FusionAccess. Install FusionAccess according to the description in this document. The installation

r c
s ou
Re
i n g
r n
e a
e L
or
M

3
3 Preparations
3.1 Obtaining Software Packages
Document or Software How to Obtain
For an enterprise user, download it from:
http://support.huawei.com/enterprise > Product

n
Support > IT > FusionCloud > FusionSphere

e
FusionCompute document FusionCompute
(Quick Guide) FusionCompute V100R005C00 Quick
/
User Guide 01 For a carrier user, download it from:
m
.i co
http://support.huawei.com > Product Support >
Carrier IT > FusionCloud > FusionSphere >
FusionCompute

w e
FusionCompute software
1. CNA OS software:FusionCompute
u a
V100R005C00SPCxxx_CNA.iso
. h
For an enterprise user, download it from:
2. FusionCompute installation wizard tool:
g
http://support.huawei.com/enterprise > Downloads

n
ni
FusionCompute > IT > FusionCloud > FusionSphere >

r
100R005C00SPCxxx_Tools.zip FusionCompute
3. Virtual Resource Management (VRM) VM
template file:FusionCompute
le a
For a carrier user, download it from:
V100R005C00SPCxxx_VRM.zip
: //
http://support.huawei.com > Software > Carrier IT

p
4. Intelligent network interface card (iNIC) driver > FusionCloud > FusionSphere > FusionCompute
software:FusionCompute
t t
:h
V100R003C10SPCxxx_GuestOSDrivers.zip

e s For an enterprise user, download it from:

c
FusionAccess software http://support.huawei.com/enterprise > Software >

r
1.Linux OS component installation software: IT > FusionCloud > FusionAccess > FusionAccess

ou
FusionAccess_Installer_Linux_V100R005C20SPC > V100R005C20SPCxxx
xxx.iso
es
2.Windows OS component installation software: For a carrier user, download it from:
R
FusionAccess_Installer_Win_V100R005C200SPCx http://support.huawei.com > Software > Carrier IT
xx.iso

i n g > FusionCloud > FusionAccess > FusionAccess >


V100R005C20SPCxxx
n
ar
For an enterprise user, download it from:

L e
FusionAccess Tool software
OS installation files:
http://support.huawei.com/enterprise > Software > IT
> FusionCloud > FusionSphere > FusionTool >

e
or
Windows2008R2SP1_EN.part1.rar V100R005C00SPCxxx
Windows2008R2SP1_EN.part2.rar
For a carrier user, download it from:
M
Decompress the two files to obtain
Windows2008R2SP1_EN.iso.
http://support.huawei.com > Software > Carrier IT >
FusionCloud > FusionSphere > FusionTool >
V100R005C00SPCxxx

4
3.2 Local PC Requirements
Item Requirement

OS Windows XP or Windows 7 32-bit

The partition for installing the OS must have more than 1 GB free space.
Hard disk space Excluding the partition for the OS, at least one partition must have more than 40 GB free
space.

Network The local PC can access the network segment of the desktop cloud management plane.
e n
/
m
Internet Explorer 8 or later is installed.

.i co
The software used to decompress .rar and .zip packages is installed.
Application software
Antivirus software and firewall software are disabled.
The Telnet tool is installed.

w e
3.3 Obtaining a License
u a
Time required: 3 to 5 days after application
. h
Application method: Huawei technical support engineers apply for the licenses.
n g
ni
Reference: FusionCloud Desktop Solution V100R005C10SPCXXX License Usage Guide.

r
Download path: http://support.huawei.com/enterprise > Software > IT > FusionCloud > FusionAccess >
FusionCloud Desktop Solution > V100R005C20

le a
3.4 Preparing for Required Data
: //
t
Before the installation, plan the following data with customers:

t p
:h
Category Parameter Example Value and Planned Value
(A1) VLAN pool
e s
c
181 to 189

r
VLAN pool of the infrastructure VM
Planned value: __________________

ou
service plane.

es
(A2) Port group name and port group
Infrastructure VMs that connect to the
R
same port group belong to the same
Name: VDIPort

g
VLAN ID: 181
network and can communicate with each
A. Network

n i n
other. This port group is created for the
Planned value: __________________

r
information VM service plane.

e a (A3) Service plane gateway and

e L subnet mask

or
Service plane gateway and subnet mask Gateway: 192.168.181.1
of the infrastructure VM, used to Subnet mask: 255.255.255.0
configure a VLANIF interface for the Planned value: __________________
M VLAN ID used by the infrastructure VM
service plane.
B. VM user (B1) User disk name
ITA: FA-ITA-DISK
disk, IP Specifies the name of a user disk
Loggetter: FA-LOG-DISK
address, and attached to an infrastructure VM running
Planned value: __________________
name Windows OS.

5
3.4 Preparing for Required Data
Category Parameter Example Value and Planned Value
Name IP
FA-AD-1 Service: 192.168.181.66
FA-AD-2 Service: 192.168.181.67
FA- Service: 192.168.181.61

e n
/
DBHDCWILI Floating: 192.168.181.60
(B2) VM names and IP addresses
Service: 192.168.181.63
m
.i co
AD/DNS/DHCP VM name and FA-DBHDCWI
service IP address Floating: 192.168.181.60
DB/HDC/WI/License VM name,
e
Service: 192.168.181.62
service IP address, and floating IP FA-ITA-1

w
Management: 192.168.180.62

a
address
B. VM user
u
ITA VM name, management IP Service: 192.168.181.64
FA-ITA-2
h
disk, IP Management: 192.168.180.64
.
address, and service IP address
address,

g
Loggetter VM name and service IP FA-Log Service: 192.168.181.65
and name
address
vAG/vLB VM name, service IP
ni n
Service: 192.168.181.68
address, management IP address, FA-vAGvLB-1
ar Management: 192.168.180.68

le
and vLB floating IP address Floating: 192.168.181.70

//
Service plane mask and gateway
Management plane mask
p : Service: 192.168.181.69

t
FA-vAGvLB-2 Management: 192.168.180.69

t Floating: 192.168.181.70

s :h Service plane
Mask: 255.255.255.0

e
Gateway: 192.168.181.1

r c Management

ou
Mask: 255.255.255.0
plane

es
(C1) Password of the administrator account Huawei123

R
Specifies the Windows OS system administrator Planned value:
C. OS
account
i n g
account. This account has the highest rights. __________________

n
(C2) root user password Huawei@123

a r
Specifies the Linux OS system administrator account. Planned value:

e
This account has the highest rights. __________________

e L (D1) Infrastructure domain name

or
Specifies the AD domain name. The AD domain vdesktop.huawei.com
manages the accounts of Windows servers and clients. Planned value:

M
All server and client computers must be added to the ______________
D. AD/DNS domain for management.
installation (D2) DSRM password
In directory services restore mode (DSRM), all domain Huawei@123
accounts are unavailable. You must use the DSRM Planned value:
administrator account and the AD DSRM password to ______________
log in to the OS.

6
3.4 Preparing for Required Data
Example Value and Planned
Category Parameter
Value
(D3) IP address segment for reverse lookup
Specifies the network segment of the IP address that 192.168.181
is translated from the domain name by the DNS. It is Planned value: ______________
D. AD/DNS the IP address segment of the VM.
installation

n
(D4) WI login domain name

e
fa.vdesktop.huawei.com

/
Specifies the cloud server address to be entered
Planned value: ______________
when a client user tries to log in to the VM.
m
.i co
(E1) Scope name DHCP1
Specifies the DHCP scope name. Planned value: ______________

(E2) Start and end IP addresses


w e
a
192.168.181.50 to
Specifies the IP address pool of the service plane.

u
E. DHCP 192.168.181.100
This address pool is used to dynamically assign IP
installation addresses to VMs.
. h
Planned value: ______________

n g
ni
(E3) Subnet mask and gateway IP address of the
Subnet mask: 255.255.255.0
address pool
Specifies the subnet mask and gateway IP address
ar Gateway: 192.168.181.1
Planned value: ______________

le
of an address pool.
(F1) Server login account and password
: // ITA: itauser Huawei123!

t p
Specifies the login account of each Windows

t
infrastructure VM, except the AD/DNS/DHCP server.
Loggetter: loguser Huawei123
Planned value: ______________

s :h
(F2) Domain administrator account and password
Vdsadmin Huawei123

e
Specifies the system administrator of a Linux OS VM.

c
Planned value: ______________

r
This account has the highest rights for the VM OSs.

ou
F. Domain (F3) Domain account and password of the

s
account Tomcat service ITAServiceUser Huawei123

Re
Specifies the account for starting the Tomcat service
on the ITA server.
Planned value: ______________

i n g
(F4) Domain account and password of the log LogServiceUser Huawei123

n
service
r
Planned value: ____________

a
Specifies the account for accessing the backup

L e service when the Loggetter server is deployed.

e
(G1) HDC database name HDCGaussDB01

or
HDC database instance created on the GaussDB. Planned value: _______________

M
G. (G2) ITA database name FusionAccess
Database ITA database instance created on the GaussDB. Planned value: _______________
informatio
(G3) Account for connecting the ITA to the Username: ITALoginUser
n
database Password: Huawei@123
Account for ITA server connecting to the database Planned value: _______________
instance and the password.

7
4 Preparing Network Resources
Step 1: Create a port group for the service plane.
1. In the address box of your browser, enter http://floating IP address of the Ensure that the local PC
VRM and press Enter to log in to the FusionCompute. can properly
communicate with the
desktop cloud
management plane.

e n
/
2. On the FusionCompute, choose Network Pool > Network Pool -
3. Create a port group for the infrastructure VM service plane. 1 When deploying
m
.i co
FusionCompute,
determine whether to
1
w e
deploy a service plane
distributed switch based

a
on the actual plan.
u
h
If a service plane

2
g . distributed switch is
created, select the

ni n distributed switch of the

ar service plane VLAN.


If no service plane

//le distributed switch is

:
created, select the

t t p distributed switch of the


management plane.
4. Set the port group Name (A2), click Next.
s :h The port group is used

e
for the service plane NIC

r c communication of

ou
infrastructure VMs.
5. Set the VLAN ID (A2).

es 2 The VLAN ID must


be in the VLAN pool
R range of the distributed

i n g 1
switch.

r n After the distributed

e a 2 switch is selected, the

L
VLAN pool range is
3 displayed in the
e
or
Resource Statistics
area on the Summary

M
tab page on the right.
6. Confirm the settings and click Create. After the port group is
created, close the page.

8
4 Preparing Network Resources
Step 2: Configure the information about the service plane port group on the aggregation
switch.
1. On the local PC, click Start, enter telnet switch IP address in the See more -
results dialog box, and press Enter to log in to the aggregation switch.

e n
/
m
.i co
2. On the aggregation switch, run the following commands to configure the The display this

e
gateway and subnet mask (A3) used by the infrastructure VM service command is used to
plane: view the gateway and
<Quidway>system-view
aw
subnet configuration
[Quidway] interface vlanif Service plane vlan id
u
information of the

h
.
[Quidway-Vlanifvlanid] ip address Service plane gateway Subnet mask VLANIF interface.
[Quidway-Vlanifvlanid] display this

n g
ni
[Quidway-Vlanifvlanid] quit

ar
3. Configure that the port for the aggregation switch allows the port group (A2) -

le
to pass, tagged.

//
<Quidway>system-view
[Quidway] interface GigabitEthernet0/0/x

p :
t
[Quidway-GigabitEthernet0/0/x] port hybrid tagged vlan-id
[Quidway] quit
t
:h
<Quidway>save

e s
r c
s ou
Re
i n g
r n
e a
e L
or
M

9
5 Installing Linux Infrastructure Components
5.1 Creating Linux VMs
Step 1: Create a bare VM.
1. On the FusionCompute portal, choose VM and Template. -
2. Create a VM. -

e n
/
1

m
e .i co
2

aw
3. Select a host.
hu
1

g. The

n
GaussDB/WI/HDC/Lice

ni
2 nse VM and

ar GaussDB/WI/HDC VM

le
must be deployed on

//
different hosts.

p : The two vAG/vLB VMs

t
must be deployed on

t
3
different hosts.
4. Set VM properties.
s:h GaussDB/WI/HDC/License

e
VM and GaussDB/WI/HDC

1
r c VM:

ou
Name:

s
FA-DBHDCWILI

e 1 FA-DBHDCWI

R Type:

g
Novell SUSE Linux

n
Enterprise Server 11 SP1

n i 2
64-bit

ar
4 vCPUs/8 GB memory/1

Le
2 disk/1 NIC
3

e 4 128000 5 8192

o r Two vAG/vLB VMs:

M 4

1
Name:
FA-vAGvLB-1
FA-vAGvLB-2
Type:
Novell SUSE Linux
Enterprise Server 11 SP1
64-bit

5 4 vCPUs/4 GB memory/1
2 disk/2 NICs

4 128000 5 4096

10
5.1 Creating Linux VMs

Step 1: Create a bare VM.

5. (Only for vAG, vLB, vAG/vLB) Set 'NIC type' to 'HW_V_NET'. When create vAG, vLB,
vAG/vLB VMs, you should set
'NIC type' to 'HW_V_NET.

e n
/
m
.i co
1

w e
u a
. h
n g
r ni
2
le a
: //
3
t t p
s:h
6. Configure NICs.
r ce 2 Select port groups based

ou
on actual plan.
3 Select the service plane
1

es port group for the first NIC;

R
Select the management
plane port group for the

i n g second NIC. Among the


Linux VMs in the

r n scenarios described in

e a 2 this document, only

e L vAG/vLB VMs have


management plane NICs.

or
3

M 4

7. Click Next.

11
5.1 Creating Linux VMs
Step 1: Create a bare VM.
5. Configure disks. 1 Select a non-
virtualization data store. and
set the Configuration
1 mode to Common.
2 3 CAUTION
Select data stores in different
RAID groups for the VMs

e n
/
working in active/standby mode.
4
3 30
m
.i co
9. Confirm the settings, and click Finish. Record the VM ID. For example: i-0000006

w e
a
1

hu
2

g.
3

ni n
ar
//le
p :
t t
:h
10. Click Create Another and refer to the preceding steps to create the -

s
GaussDB/WI/HDC, active and standby vAG/vLB VMs. Record the VM ID.

e
r c
ou
Step 2 Set the automatic recovery attribute for Linux infrastructure VMs.

es
1. Log in to the VRM active node by using PuTTY with the VRM floating IP Default password:

R
address. The login account is gandalf. Huawei@CLOUD8

ing
2. Run the following command to switch to the root user. Default password:
su root Huawei@CLOUD8!
TMOUT=0
r n
a
Le
3. For each newly created infrastructure VM, run the following command: This command must be run
sh /opt/galax/vrm/tomcat/script/modifyRecover.sh vmId true for each infrastructure VM.

r e
vmId is the ID of the VM.

o
4. Restart the VRM process.

M service vrmd restart


Run this command only after the previous step is complete on all the VMs.
5. On the FusionCompute portal, choose VM and Template, click the VM Stop and restart the VM for
tab, locate the row that contains the GaussDB/WI/HDC/License VM, the configuration to take
choose More > Forcibly stop. effect.
6. After Status of the VM changes to Stopped, locate the row that contains -
the VM, choose Start.
7. Refer to 5 to 6 to stop and start all Linux infrastructure VMs. -

12
5.1 Creating Linux VMs
Step 3 Set VMs to be mutually exclusive.
1. Choose Computing Pool > Host and Cluster.
2. Open the window for setting resource scheduling policies. To ensure reliability, set
the VMs of the same
2 component to be mutually

n
1 exclusive so that the VMs

e
are always on different
3
/
host nodes. When a host

m
is faulty, FusionAccess

.i co
can continue to work
properly.

w e
u a
5
. h
n g
4
r ni
le a
6

: //
t t p
s :h
e
3. Add a rule. -

r c
s ou 2

Re
i n
1
g
r n
e a
L
4. Set Type to Keep VMs mutually exclusive.

e
or 1

M 2

5. Add the GaussDB/WI/HDC/License and GaussDB/WI/HDC VMs to -


Selected VMs.
6. Click OK as prompted to add the rule. -
7. Refer to 3 to 6 to set vAG/vLB VMs to be mutually exclusive. -
8. On the lower part of the page, click OK. -

13
5.1 Creating Linux VMs
Step 4 Install the OS.
1. Log in to the GaussDB/WI/HDC/License component VM. 3 Locate the row that
1 contains the VM.

e n
/
3

m
e .i co
w
2. Mount a CD-ROM drive. -

u a
h
1 3
2
4
g.
ni n
ar
5

//le
6
p :
t t 1

s :h
3. Select Install within 30 seconds, and press Enter. Within 30 seconds
1

r ce
s ou
Re Repeat 2 3 4 5 6
g
4. Configure the service IP address and gateway (B2).

n
to configure the

n i 2
management IP for the

a r vAG/vLB VM, where 2

e
1 is eth1: not configured.

e L Keyboard operations:
Press Tab, , or to

or
move the cursor.
3 Press Enter to select

M 4 5
or execute the item
that the cursor
selects.
Press the space key
to select the item
selected by the
6
cursor.
When you enter a digit,
use the digital keys in
the upper part of the
main keyboard area.

14
5.1 Creating Linux VMs
Step 4 Install the OS.
5. Configure the gateway. 1 Service plane gateway.
1

e n
6. Configure the host name (B2). -
/
m
.i co
2

1
3

w e
u a
. h
n g
ni
7. Configure the time zone. -

ar
//le
p :
1
t t
2
s :h
r ce 3

ou
4

es
R
ing
8. Configure the password (C2). -

r n
e a
e L
or
2
1

M 3

9. Press F12 and press Enter twice to start the OS installation. About 8 minutes.

10. Log in to the VM using the root account and the password configured in -
step 8.

15
5.1 Creating Linux VMs
Step 5: Install the PV-Driver.
1. On the FusionCompute portal, mount tools on the 4 Locate the row that
GaussDB/WI/HDC/License VM. contains the
GaussDB/WI/HDC/Licens
e VM.
1
2

e n
/
m
4 3

e .i co
aw
hu
2. Click OK twice.
g .
-

3. In the VNC window on the VM, install the PV-Driver.


ni n
ar
// le
:
1

t t p
s :h
r ce
2
s ou
Re
i n g
r n
4. Press Enter twice to install the PV-Driver. -

e a
L
5. After the PV-Driver is installed, press F8 as prompted to restart the VM. -

e
or
6. After the restart, log in to the VM as the root user. -

M
Step 6 Install other VMs.
1. Refer to step 4 to step 5 in this section to install the following software on You can install OS on
the GaussDB/HDC/WI VM and the active and standby vAG/vLB VMs: different VMs at the same
1. Install the OS. time. After OS installation,
2. Install the PV-Driver. perform subsequent
operation.

16
5.2 Installing the GaussDB/HDC/WI/License Components
Step 1 Install components.

1. In the VNC window on the VM, enter startTools to start the installation -
tool.
2. Select Software > INSTALL All in sequence. -

e n
/
m
.i co
1

2
w e
3. Press Enter, after the installation finished and press Enter.
u
- a
. h
n g
r ni
3

le a
: //
t t p
:h
4

e s
Step 2 Configure the GaussDB
r c
1. Configure HA information (B2).
s ou -

1 Re
i n g
r n
e a 2

e L
or
M
3

17
5.2 Installing the GaussDB/HDC/WI/License Components

Step 2 Configure the GaussDB


2. Configure HA information (B2). 1
Local HA IP Address
is the service plane IP
1 address of this VM.
Peer HA IP address is
the service plane IP
e n
/
address of the peer VM

m
that works with this

.i co
GaussDB in
active/standby mode.

2
w e
Gateway: service
plane gateway

u a
. h
g
3. Configure the floating IP address of GaussDB (B2). -

ni n
1
ar
//le
p :
t
2

t
s :h
r ce
s ou
e
3

R
i n g
rn
e a
4. Configure the floating IP address of GaussDB (B2).

e L 1
Floating IP address

or 1 and subnet mask of


GaussDB

18
5.2 Installing the GaussDB/HDC/WI/License Components
Step 3 Install the GaussDB/HDC/WI server.
1. Refer to the previous information in this section, and log in to the The procedure for
GaussDB/HDC/WI component server to perform the following operations: installing both the
active and standby
1. Select install all to install all components.
servers are the same,
2. Configure the GaussDB HA information and floating IP address.
except for the data
planning. You can
e n
/
obtain the data from

m
the data planning table.

.i co
The GaussDB
components on the two

w e
servers work in
active/standby mode. If

u a HA is configured, the
two servers are peers.

. h
n g
r ni
le a
: //
t t p
s :h
r ce
s ou
Re
i n g
r n
e a
e L
or
M

19
5.3 Installing the vAGvLB Components
Step 1 Install vAG.
1. In the VNC window on the VM, enter startTools to start the installation tool. -
2. Go to the installation directory.

1
e n
2
/
m
e.i co
3
aw
hu
g .
ni n
ar
// le
:
4

t t p
s :h
5

r ce
ou
Step 2 Install vLB.
1. Run the installation program.
es -

R
i n g 2

r n
e a
L
1

e
or
M
4

20
5.3 Installing the vAGvLB Components
Step 3 Configure the IP address of the WI/UNS servers.
1. Go to the installation directory. -

e n
/
1
m
e .i co
aw
hu
g.
2

ni n
ar
// le
p :
3
t t
s:h
r ce
s ou
e
2. Configure the IP address of the WI/UNS servers (B2). 5 Service plane IP

R addresses of the WI/UNS

g
servers.

n i n 4

a r
L e
e
or
M

21
5.3 Installing the vAGvLB Components
Step 4 Configure the HA of the vLB.
1. Configure the HA of the vLB (B2). -

e n
/
m
.i co
1

w e
u a
. h
n g
ni
2

ar
//le
p :
t t
:h
3

e s
r c
s ou 5

e
2. Configure the IP address of the HA (B2). Local HA IP Address is

R the service plane IP

g
address of this VM.

n i n 4
Peer HA IP address is
the service plane IP

a r address of the peer VM

L e that works with this vLB in


load balancing mode.

e Gateway: Service plane

or
gateway

M
5

22
5.3 Installing the vAGvLB Components
Step 5 Configure the Float IP addresses for the vLB servers.
1. Go to the installation directory. -

e n
/
m
.i co
1

w e
u a
. h
n g
ni
2

ar
// le
p :
3

t t
s :h
r ce
ou
2. Configure the Float IP addresses for the vLB servers. Service plane Float IP

s
addresses of the vLB

Re 4
servers.

i n g
r n
e a
e L
or 5

M
Step 6 Install the vAG/vLB servers.
1. Refer to the previous information in this section, and perform the following The procedure for
operations to install the standby vAG/vLB component: installing both the
active and standby
1. Install the vAG component.
servers are the same,
2. Install the vLB component.
except for the data
3. Configure IP addresses for the WI servers.
planning. You can
4. Configure the HA for the vLB servers.
obtain the data from
5. Configure the floating IP address for the vLB servers.
the data planning table.
23 The vLB components
6 Installing Windows OS Infrastructure Components
6.1 Creating an Infrastructure VM Template
Step 1 Create a bare VM.
1. On the FusionCompute portal, choose VDC Management > VM and -
Template.

n
2. On the Summary page, click Create VM. -

/ e
m
.i co
1

w e
u a
h
2

g.
3. On the Create VM page, click Next.

ni n -

4. Set the VM properties.

ar VM name:

le
Customized

://
OS version:
1 1
Windows Server

tp
2008 R2 Standard

t 64bit

s :h 4 VCPU/4 GB

e
2 memory/1 disk/1 NIC

r c 3

ou
Select Restart.

s
2

Re
i n g
r n
e a
e L
or
M 3

24
6.1 Creating an Infrastructure VM Template
Step 1 Create a bare VM.
5. Set NICs. 2 Select the value based
on the data plan.
1

3 Select the service


plane port group.

e n
/
2
m
3

e .i co
aw
hu
.
4

n g
ni
6. Set the disk. 1 Select a non-

1 2
ar 3
virtualization data store.
The selected data store

// le must ensure that the2

p : configuration mode

t
can be set to Common.
4
t
:h
3 Set the disk capacity to

e s 50 GB.

r c
7. Confirm the entered information, and click Finish. -

Step 2 Install the OS.


s ou
Re
1. Log in to the VM created in step 1 using VNC. -

ing
2. Mount the Windows Server 2008 ISO file, select Restart the VM now to Windows2008R2SP1_EN.

n
install the OS, and click OK. iso

a r
3. Install the OS as promoted, retain the default values of the parameters, The installation takes

L e
set the password of Administrator, and log in to the VM. about 50 minutes.

e
or
M

25
6.1 Creating an Infrastructure VM Template
Step 3 Modify the group policies.
1. Click Start, enter gpedit.msc in Search programs and files, and press -
Enter.

2. Disable the services in 4 and 5 . 4 5 Double-click the


1 service and select

n
Disabled.
2
/ e
m
.i co
3

w e
4
u a
. h
g
5
3. Disable the firewall.
ni n 6 8 Double-click the
1

ar service and select


Disabled.
2
6

//le
p :
t
3

t
s:h
4

r ce
ou
5
7

es
R
g
8

n i n
a r
L e
e
or
M
4. Close the Local Group Policy Editor window. -

26
6.1 Creating an Infrastructure VM Template
Step 4 Disable services.
1. Click Start, enter services.msc in Search programs and files, and -
press Enter.
2. Disable the Application Layer Gateway Service. 1 Double-click the
service, select Disabled in

n
Startup type, and click

e
OK.
/
1
m
e .i co
aw
hu
g.
ni n
2
ar
//le
p :
t t
s :h
r ce
3
s ou
Re
ing
3. Disable the Windows Firewall service in the same way. -

rn
4. Close the Services window. -

e a
Step 5 Install the paravirtualized (PV) driver.

e L
1. On the FusionCompute portal, mount tools to the VM. 3 Locate the row that

o r contains the VM.

M 2
1

4 3

2. Click OK twice. -

27
6.1 Creating an Infrastructure VM Template
Step 5 Install the PV driver.
3. On the VM, run the PV driver installation program.
1

2
e n
/
m
.i co
3

4. Install the PV driver as prompted and restart the VM.


e
The VM restarts twice

w
during the installation.

Step 6 Copy the log collecting tool and health check tool.
u a
. h
g
1. In the VNC login window, mount Do not select Restart the
FusionAccess_Installer_Win_V100R005C20SPC100.iso.

ni n VM now to install the OS

under the tools folder to drive C on the VM.


ar
2. Switch to the CD-ROM drive directory and copy the FusionCare folder

//le
:
Step 7 Install .NET Framework 3.5.1.
1. Install NET Framework 3.5.1.
t t p 1 is displayed in

:h
1
2 the lower left corner on the

e s VM screen.

r c
sou 3

4 Re
i n g
r n
e a
e L
or
M
5

2. Click Next and complete the installation as prompted. -


3. Close the Server Manager window. -

28
6.1 Creating an Infrastructure VM Template
Step 8 Encapsulate the template.
1. On the VM, run sysprep. 2 Double-click sysprep.
1

e n
/
m
.i co
2

2. Set parameters.
e
The VM shuts down

w
automatically after

a
sysprep is executed.

u
. h
n g
ni
1

ar
2
//le
p :
3
t t
s :h
Step9 Create an infrastructure template.

r ce
ou
1. On the FusionCompute portal, choose VM and Template. -
2. Convert the VM into a template.

es
R
g
1
2

n i n
a r
e
3 4

e L
or 5

M
3. Query the template status in the navigation tree. If the template VM is
displayed in Recently
2 Viewed Templates, the
1 template VM is converted
into a template.
3

29
6.2 Creating and Setting Infrastructure VMs
Step 1 Create infrastructure VMs.
1. On the FusionCompute portal, choose VM and Template> Template and -
Specifications.
2. Select Deploy VM Using Template. 3 Select the appropriate
template.
1

e n
/
3
6
2
m
4
5

e .i co
aw
3. Select the host.
hu
2 The VMs working in
1

g. active/standby mode must

n
be deployed on different

ni
2
CNAs.

ar
//le
3

p :
t t
:h
4. On the Create VM page, click Next. -
5. Set the VM properties.

e s 1
Two AD/DNS/DHCP VMs:

r c 1 FA-AD-1/FA-AD-2

ou 2 2 VCPUs/2 GB

es memory

R 4 128000

ing
2 5 2048

rn
Two ITA VMs:

e a 1 FA-ITA-1/FA-ITA-2

e L 2 4 VCPUs/4 GB

o r 3
memory

M
4 128000
5 4096
4
One Loggetter VM:
1 FA-LogTCM
2 VCPUs/2 GB
2
memory
5
4 128000

5 2048
30
6.2 Creating and Setting Infrastructure VMs
Step 1 Create infrastructure VMs.
5. Click Next. -
6. Set the disk. CAUTION
Select data stores in different RAID
groups for the VMs working in
1
active/standby
3 mode.

2 1 Select the data store.


e n
The selected data store
/
must ensure that the
m
.i co
configuration mode 2 can
7. Click Next, confirm the entered information, and click Finish. be set to Common.

8. Click Create Another and create the other infrastructure VMs in the -
w e
same way.
u a
.
Step 2 Set the automatic recovery attribute for infrastructure VMs and set VMs to beh
mutually exclusive.
n g
1. Set the automatic recovery for all the Windows infrastructure VMs,
r ni For details, see Set 5.1
and set the following Windows VMs to be mutually exclusive:
Set FA-AD-1 and FA-AD-2 to be mutually exclusive.
le a Creating Linux VMs.
automatic recovery: Step 2
Set FA-ITA-1 and FA-ITA-2 to be mutually exclusive.
: // Mutually exclusive: Step 3

Step 3 Set basic VM information.


t t p
:h
1. Log in to FA-AD-1 using VNC. -

e s
2. Set the region, time, and keyboard, enter the product key, and reset the -

r
administrator password as prompted.
c
ou
3. Set FA-AD-2, FA-ITA-1, FA-ITA-2, and FA-LogTCM in the same way. -

es
R
Step 4 Add user disks.

ing
1. Choose Storage Pool. -

n
2. Create disks. 1 Select a data store for

a r 1
the user disk. You can

e
select any type of data

e L 4
store for creating the user
disk.

or 2 5 Two AD/DNS/DHCP VMs:

M 3
4
5
FA-AD-1/FA-AD-2
20
One Loggetter VM:
4 FA-LogTCM
6
5 50
3. Click OK continuously and complete the disk creation for the active
AD/DNS/DHCP VM.

31
6.2 Creating and Setting Infrastructure VMs
Step 4 Add user disks.
4. Repeat steps 2 to 4 to create disks for the standby AD/DNS/DHCP VM -
and Loggetter VM.
5. Choose VM and Template > VM and click FA-AD-1 on the VM tab. -
6. Select the VMs.

e n
/
m
.i co
1

w e
2
u a
. h
n g
7. Select the disk.
r ni -

le a
: //
t t p
s :h
r ce
ou
8. Click OK to attach the disk to the VM. -

s
9. Log in to FA-AD-1 using VNC. -

Re
10.Open the Disk Management dialog box. -

1
i n g
r n
e a 2

e L 3

or
11.Set parameters as prompted.
12.Format the disk. 3 Shows the disk status

M 2 after formatting.

13.Repeat steps 5 to 12 to bind and format the disks of the standby -


AD/DNS/DHCP VM and the Loggetter VM.
32
6.2 Creating and Setting Infrastructure VMs
Step 5 Add NICs.
1. Choose VM and Template > VM and click FA-ITA-1 on the VM tab. -
2. Add NICs. Select the distributed
5
switch on the
4 management plane.
1

e n
3 /
5
m
2
6
e .i co
aw
3. Add NICs for the standby ITA VM FA-ITA-2 in the same way. -
hu
g .
n
Step 6 Set the VM time on all VMs. (Perform this operation on all VMs.)
1. Log in to the VM using VNC and set the VM time.
r ni -
2. (Optional) Set the daylight saving time (DST).
le a Set the VM time based on

//
If DST is observed by the time zone on Windows, select site requirements.
Automatically adjust clock for Daylight Saving Time and set the
p :
DST.
t t
If DST is not observed by the time zone on Windows, download

:h
TZEDIT.exe and set the DST.

e s
c
Step 7 Set VM IP addresses on all VMs. (Perform this operation on all VMs.)
r
ou
1. Set IP addresses.

s
Address First NIC (For all VMs) Second NIC (Only for ITA)

IP address/subnet mask

Re Service plane IP address Management plane IP address

g
Default gateway IP address Service plane gateway IP address N/A

Primary DNS server

n i n IP address of the active DNS server N/A

ar
Secondary DNS server IP address of the standby DNS server N/A

L e
e
Step 8 Activate the VM OS on all VMs. (Perform this operation on all VMs.)

or
1. On the Server Manager window, click Activate Windows. -

M
2
1

3
2. Enter the product key and activate the OS as prompted.
CAUTION
Use the correct product key for the OS. If a product key for an OS in the Chinese edition is
used to activate an OS in the English edition, the blue screen of death (BSOD) will occur on
the infrastructure VM.

33
6.3 Installing the AD/DNS Services
Step 1 Change the AD/DNS server names. (The operations on the active and standby
servers are the same.)
1. Log in to the FA-AD-1 using VNC. To change the standby
server name, log in to the
FA-AD-2 VM.

n
2. Click Start, enter sysdm.cpl in Search programs and files, and press -

e
Enter. Then, click Change in the System Properties dialog box.
/
m
3. Change the computer name for the VM. -

e .i co
aw
1

hu
g.
ni n
ar
//le
p :
t t
:h
2

e s
4. Restart the VM as prompted.
r c -

s ou
Step 2 Add the AD role. (The operations on the active and standby servers are the same.)
1. Add Roles.
Re -
2

i n g
rn
a
1

L e
e
3

or
M
2. Click Next. -

34
6.3 Installing the AD/DNS Services
Step 2 Add the AD role. (The operations on the active and standby servers are the same.)
3. Select Active Directory Domain Services. -
1

e n
/
4. Add the AD role as prompted. -
m
Step 3 Install the AD/DNS. (The second column describes the different operations on the
standby server.)
e .i co
1. Click Start, enter dcpromo.exe in Search programs and files, and
aw
The operations are the
press Enter.

hu
same on the standby

g. server.
2. Retain the default values and go to the following page as prompted.

ni n Standby server:
Select Existing forest >

ar Add a domain controller

le
to an exiting domain and

//
click Next.

p :
t t
s :h
r ce
ou
1

es
R 2

i n g
n
ar
3. Set a domain name. Standby server:

L e On Network credentials,
enter the FQDN of the

e
or
forest root domain and
click Set. Enter the

M
Administrator account
and password of the
active AD server and click
Next.
1 Proceed as prompted until
the dialog box shown in
Step 6 is displayed.
2

35
6.3 Installing the AD/DNS Services
Step 3 Install the AD/DNS. (The second column describes the different operations on the
standby server.)
4. Set the forest functional level. Standby server: No this
operation.

e n
/
1
m
e .i co
aw
hu
g.
2
ni n
ar
le
://
5. Set Forest functional level to Windows Server 2008 and click Next. Standby server: No this
operation.
6. Add the DNS server.
t tp The operations on the

:h
standby server are the

e s same.

r c
1

s ou
Re
i n g
r n
e a
e L
or
M 3

7. Click Next. Set the restore Directory Services Restore Mode (DSRM) The operations on the
password, install the services as prompted, and restart the VM. standby server are the
same.

36
6.3 Installing the AD/DNS Services
Step 4 Configure reverse DNS lookup. (Perform this operation only on the active server.)
1. Create a zone. -

1
2
e n
/
m
.i co
3
4

w e
2. Retain the default values and go to the page for setting the reverse lookup
zone as prompted.
-

u a
. h
n g
r ni
1
le a
: //
t t p
s :h
r ce
s ou 2

Re
ing
3. Complete the configuration as prompted. -

r n
e a
e L
or
M

37
6.3 Installing the AD/DNS Services
Step 5 Configure DNS advanced properties. (Perform this operation only on the active
server.)
1. Open the Properties window. -

e n
1
/
m
e .i co
aw
hu
2

g.
ni n
r
2. Set advanced properties. 6 Delete all files named

le a root-servers.net.

://
1 5

t tp
:h
2
6
e s
3
r c
s ou
4 Re
i n g 7

r n
e a 8

e L
or
3. Delete the CACHE.DNS file. -
1

38
6.3 Installing the AD/DNS Services
Step 6 Configure the winrm service. (The operations on the active and standby servers are
the same.)
1. On the AD server, click Start, enter cmd in Search programs and files, -
and press Enter.
2. Run winrm qc /q and view the information displayed. -

e n
/
m
e.i co
aw
u
3. Close the cmd window. -

. h
g
Step 7 Configure the remote assistant service. (Perform this operation only on the active
server.)

ni n
ar
1. On the active AD service, click Start, enter gpmc.msc in Search -

le
programs and file, and press Enter.

://
2. Create a group policy object (GPO). -

t tp
s :h
1
2
r ce
s ou
3. Set the GPO name.
Re -

1
i n g
r n
e a
e L 2

or
M
4. Set the GPO policies. -

2
3

39
6.3 Installing the AD/DNS Services
Step 7 Configure the remote assistant service. (Perform this operation only on the active
server.)
5. Enable Offer Remote Assistance. 8 Enter the domain
account of the Tomcat
1 service.
2

e n
/
5

3
m
e .i co
4

aw
hu
g.
6
ni n
ar
le
8

: //
t t p
:h
7

e s
r c 9

s ou
Re
i n g 10

rn
a
6. Enable Solicited Remote Assistance. See 5 6 10 in the previous

e
step to enable the solicited remote assistance service.
L
e
or
M
Step 8 Install the AD/DNS services on the standby server.
1. Install the AD/DNS services on the standby server. -
For details, see steps 1 to 7 in section 6.3 Installing the AD/DNS
Services. Pay attention to the information in the second column.

40
6.4 Installing the DHCP Service
Step 1 Configure functions of the active DHCP server.
(The second column describes the different operations on the standby server.)
1. Log in to the active AD/DNS/DHCP server using VNC. Log in to the standby
AD/DNS/DHCP server.
2. Add roles. 2 The operations on the

n
standby server are the
1
same.
/ e
m
.i co
3

w e
3. Click Next.
u a
4. Select DHCP Server.
. h
n g
r ni
le a
: //
t t p
:h
5. Open the Specify IPv4 DNS Server window as prompted.

e s
6. Set the service plane IP addresses for the active and standby DNS 1 Enter the service plane

c
servers. IP address of the active

r DNS server.

sou 4 Enter the service plane

Re IP address of the standby


DNS server.

i n g The operations on the

r n standby server are the

e a same.

e L
or 2

M
1
3
5
4
6
7

41
6.4 Installing the DHCP Service
Step 1 Configure functions of the active DHCP server.
(The second column describes the different operations on the standby server.)
7. Click Next. The operations on the
standby server are the
same.

n
8. Add the DHCP scope. On the standby server,
1 perform 5 .
/ e
m
2

e .i co
aw
hu
g.
ni n
3

ar
// le
4
p :
t t
:h
5

e s
r c
9. Select Disable DHCPv6 stateless mode for this server and click Next. The operations on the

ou
standby server are the
same.

es
R
i n g
r n
e a
e L
or 1

M
2

10.Complete the DHCP installation as prompted.

42
6.4 Installing the DHCP Service
Step 2 Configure functions of the standby DHCP server.
1. Log in to the standby AD/DNS/DHCP server using VNC. -
2. Configure the functions of the standby DHCP server. -
For details, see step 1 in section 6.4 Installing the DHCP Service. Pay
attention to the Second column.

Step 3 Synchronize the IP address pool from the active DHCP server to the standby DHCP
e n
server. /
m
.i co
1. Log in to the active AD/DNS/DHCP VM using VNC. -

e
2. Open the DHCP Split-Scope Configuration Wizard. -

aw
1
hu
g.
ni n
ar
le
2 3

: //
t
3. On the Additional DHCP Server dialog box, add a server.
t p 2 In the dialog box

:h
displayed, enter the IP
address or computer

e s name of the standby

c
DHCP server.

r
ou
1

es
R
i n g
r n
e a
L
4

e
or
M
2

43
6.4 Installing the DHCP Service
Step 3 Synchronize the IP address pool from the active DHCP server to the standby DHCP
server.
4. Click Next. -
5. Set Delay in DHCP Offer. 1 In this example, 1000
indicates that the standby
DHCP server waits 1000

e n
/
ms and starts to assign IP
addresses if the active
m
.i co
DHCP server does not
assign IP addresses.
1

w e
a
2

hu
g.
n
6. Complete the synchronization operation as prompted. -

ni
Step 4 Activate the IP address pool of the standby DHCP server.
ar
le
://
1. Log in to the standby AD/DNS/DHCP VM using VNC. -

tp
2. Activate the address pool.

t
s :h
e
1

r c
s ou
Re
i n g
n
2

a r
3. The status after the activation is as follows: -

L e
e
or
M

44
6.5 Creating Domain Accounts on only the Active Server
Step 1 Create an organization unit (OU).
1. Log in to the active AD server using VNC. -

2. Right-click the infrastructure domain name and choose New > If an OU already exists,
skip over this operation.
Organization Unit.

n
1

/ e
m
2
e .i co
aw
hu
g.
3
ni n
ar
//le
p :
t t 4

s :h
e
3. Enter the user OU name (B1), for example, UserOU, and click OK. Enter the planned user

r c OU name.

s ou
Re
i n g
r n
e a
e L
or
M

45
6.5 Creating Domain Accounts on only the Active Server
Step 2 Create users.
1. Right-click the user OU and choose New > User. 1 Select the OU created
in step 1.

e n
/
m
1
e .i co
aw
hu
2

g.
ni n
ar
//le
p :
t
3

t
s :h
2. Enter the username and user logon username (B3) and click Next. Add the following domain

r ce accounts:

ou
Account used for logging
in to the ITA server, for

es example, itauser
1
R Account used for logging

i n g in to the Loggetter server,


for example, loguser

n
ar
Domain management

L e account, for example,


vdsadmin

e2

or
Tomcat domain account,
for example,

M ITAServiceUser
Log service domain
account, for example,
3 LogServiceUser

46
6.5 Creating Domain Accounts on only the Active Server
Step 2 Create users.
3. Enter the user password (B3). 1 The passwords must
meet the following
conditions:
Consists of at least 6
characters.
Cannot be the same
n
1

/ e
as the username or the

m
username in reverse

.i co
2 order.
Contain at least three

e
of the following
combinations:

aw Lowercase letters

hu Uppercase letters
Digits

g. Space or special

n
3

ni
characters, including
`~!@#$%^&*()-

ar _=+\|[{}];:'",<.>/?

le
://
2 Deselect this option.

tp
4. Click Finish. -
5. Add the following accounts in the same way:
t
:h
-
Account used for logging in to the ITA server, for example, itauser

s
Account used for logging in to the Loggetter server, for example,
e
c
loguser

r
Domain management account, for example, vdsadmin

ou
Tomcat domain account, for example, ITAServiceUser

s
Log service domain account, for example, LogServiceUser

e
R
Step 3 Set the domain administrator properties.

i n g
1. Right-click the username and choose Properties. 1 This account (for

r n example, vdsadmin) is

e a used to add VMs to a


domain.

e L
or
2

M 1

47
6.5 Creating Domain Accounts on only the Active Server
Step 3 Set the domain administrator properties.
2. Add this user to the Domain Admins group. -

e n
/
m
2
e .i co
aw
hu
g.
6
ni n
ar
//le
p :
t t
s :h
3

r ce 4

sou 5

Re
g
3. Add the Tomcat domain account, for example ITAServiceUser, to the -

n
Domain Admins and DHCP Users groups.

n i
r
Step 4 Set user rights.
a
L e
1. Right-click the OU and choose Delegate Control. 1 Select the newly

e
created OU.

or
M
1
2

48
6.5 Creating Domain Accounts on only the Active Server
Step 4 Set user rights.
2. Open the Users or Groups window as prompted. -
3. Add an account. 2 Enter a domain
management account,
such as vdsadmin.

e n
5 /
m
1

e .i co
6

aw
hu
g.
ni n
ar
2 3
//le
p :
4
t t
s :h
such as ITAServiceUser, and click Next.
r ce
4. Repeat the previous step to add a Tomcat service domain account, -

ou
5. Select Create a custom task to delegate and click Next twice.

s
Re
6. Assign operation permissions to the user. -

i n g
rn
e a
e L
or
1

M
2

7. Complete the configuration as prompted. -

49
6.6 Configuring Backup and Performing Security Hardening
Step 1 Install the backup tool. (The operations on the active and standby servers are the
same except that the VMs you need to log in are different.)
1. Log in to the active AD/DNS/DHCP server using the Administrator Log in to the standby
account in VNC mode. server using the
SWMaster account.
2. On the active AD/DNS/DHCP server, mount You do not need to select

n
FusionAccess_Installer_Win_V100R005C10SPC100.iso. Restart the VM now to
install the OS.
/ e
m
3. Double-click the CD-ROM drive directory and click BackupTools in the -

.i co
Installation Wizard window.
4. Retain the default values and select the components for which the -
backup tool is to be installed.

w e
u a
. h
n g
1
r ni
le a
: //
2
t t p
s :h 2 Enter the log service
e
5. Set the backup path and shared domain user.

r c domain account, that is,

ou
the LogServer domain
account created when the
1
es Loggetter is installed. For

R
example, enter

g
vdesktop\LogServiceUs

n
2 er.

n i
a r
L e 3

e
or
6. Complete the installation as prompted. -

M
Step 2 Configure security hardening. (The operations on the active and standby servers
are the same.)

CAUTION -
Before performing security hardening, ensure that no user has logged in to the
standby AD/DNS/DHCP VM.
1. In the Installation Wizard window, click Security.

2. Perform security hardening as prompted. Restart the VM and log in the After the hardening, the
VM as user SWMaster. Administrator account
changes to Swmaster.

50
6.6 Configuring Backup and Performing Security Hardening
Step 3 Configure security information for the standby AD/DNS/DHCP server.
1. See step 1 to step 2 in 6.6 Configuring Backup and Performing Security
Hardening to install the backup tool on the standby server and perform
security hardening.

6.7 Configuring DNS Policies

e n
Step 1 Configure the forward and reverse DNS lookups.
/
(Perform this operation only on the active server.)
m
1. Log in to the active AD/DNS/DHCP VM using VNC.
2. Open the New Host window.
-
-
e .i co
aw
hu
g.
ni n
ar
1
// le
p :
2
t t
s :h
3. Add the active HDC server (B2).
r ce Repeat steps 1 2 4

ou
to add the following
information:
1
es 1 2

R
g
Active HDC Service

n i n server name IP
address
2

a r Standby HDC Service


3

L e server name IP

e
address

or Prefix of the vLB

M
domain name floating
used for IP
4 accessing the address
WI (D4)

4. Close the New Host window. In the navigation tree, expand Reverse -
Lookup Zones, right-click Reverse IP address segment, and choose
Refresh to check whether the reverse DNS lookup is automatically
added.

51
6.7 Configuring DNS Policies
Step 2 Enable the DNS aging and scavenging functions.
(Perform this operation only on the active server.)
1. Enable the DNS aging and scavenging functions. -

e n
/
m
1

e.i co
aw
u
2

. h
n g
r ni
le a
//
4
5

p :
t t
:h
6

e s
r c
ou
Step 3 Set the address on which the DNS server listens.

s
(The operations on the active and standby servers are the same.)

Re
1. Set the address on which the DNS server listens. -

i n g
r n
1
e a
e L
or 3

M 4

2 5

52
6.7 Configuring DNS Policies
Step 4 Modify the Start of Authority (SOA) record. (Perform this operation only on the
active server.)
1. Modify the SOA record. -

4
1

e n
/
m
2

e.i co
aw
hu
5
g.
ni n
3
ar
//le
p :
6
t t
s :h
r ce
ou
Step 5 Configure the DNS policies for the standby AD/DNS/DHCP server.

es
1. Log in to the standby AD/DNS/DHCP server as user Swmaster. -

R
2. See Step 3 Set the address on which the DNS server listens to -

i n g
complete the configuration on the standby server. You need to perform
only this step on the standby server.

r n
e a
e L
or
M

53
6.8 Installing the ITA
Step 1 Add the VM to the domain.
(The operations on the active and standby servers are the same, but the servers to be
logged in are different.)
1. Log in to the infrastructure VM hosting the active ITA service as user To install the standby ITA
Administrator. server, log in to the
infrastructure VM hosting
the standby ITA service.
e n
2. Click Start, enter sysdm.cpl in Search programs and files, and press - /
m
.i co
Enter. Then, click Change in the System Properties dialog box.
3. Add the infrastructure VM to the domain. 1 Enter the VM name.

3
w e
Enter the infrastructure

a
domain name.
u
. h5 Enter the domain
g
1

n
administrator username

ni
and password.

ar
5

// le
:
2

3
t t p
:h
6

4
e s
r c
s ou
4. Restart the VM and then log in to the VM as user Administrator. -

Re
Step 2 Add the domain account to the administrator group.

i n g
(The operations on the active and standby servers are the same.)

r n
1. Click Start, enter compmgmt.msc in Search programs and files, and -

a
press Enter.

L e
2. Open the Add to Group window. -

e
or
3
4

M 1

54
6.8 Installing the ITA
Step 2 Add the domain account to the administrator group.
(The operations on the active and standby servers are the same.)
3. Add the domain account to the administrator group. 2 Add the following
accounts:
Tomcat domain
account, for example,
ITAServiceUser
e n
Domain account used
/
m
for logging in to the ITA

.i co
server, for example,
itauser

w e
Repeat
1 2 3 4 5

7
u ato add the domain
accounts.

. h
n g
ni
1

6
ar
//le
p :
t t
:h
4

e s
2
r c
ou
5

es
R
3

i n g
rn
a
Step 3 Install the ITA.

e
(The operations are different on the active and standby servers.)
L
e
1. Log out of the VM and then log in to the infrastructure VM hosting the To install the standby ITA

or
active ITA service using an ITA server login account, such as itauser. server, log in to the
infrastructure VM hosting

M
2. On the active ITA server, mount
the standby ITA service.
You do not need to select
FusionAccess_Installer_Win_V100R005C10SPC100.iso. Restart the VM now to
install the OS.
3. Double-click the CD-ROM drive directory and click IT Adaptor in the -
Installation Wizard window.
4. Open the ITA Configuration window as prompted. -

55
6.8 Installing the ITA
Step 3 Install the ITA. (The operations are different on the active and standby servers.)
5. Configure the Tomcat account. 1 Enter the Tomcat
domain account, for
example, ITAServiceUser.
2 The rights
1 management mode must
e n
be the same as the mode
/
m
set when FusionCompute

.i co
is installed.

e
2

aw
hu
g.
ni n
ar
le
3

: //
6. Configure the database.

t t p 1 Select Create a
database for the active

:h
ITA and Use the

e s existing database for

c
the standby ITA.
1
r
ou
2 Enter the floating IP
2

es address of the
GaussDB
R
ing
3 3
Enter the ITA database
name (G2).

rn
4
4

ea
Set the password for

L
accessing the ITA
database (G3).
e
5

or
5
6
Enter the default

M
password, which is
7 Huawei@123.

7. Complete the ITA software installation as prompted. -

56
6.8 Installing the ITA
Step 4 Install the backup tool. (The operations on the active and standby servers are the
same.)
1. In the Installation Wizard window, click BackupTools. -

2. Select ITA and click Next. -

e n
/
m
1

e .i co
aw
hu
g.
ni n
r
2

le a
3. Set the backup path and shared domain user.
: // 2 Enter the log service

t t p domain account, that is,


the LogServer domain

:h
account created when the

e s Loggetter is installed. For


example, enter
1
r c vdesktop\LogServiceUs

ou
er.

2
es
R
i n g
r n
e a 3

e L
or
4. Complete the installation as prompted. -

M
Step 5 Perform security hardening. (The operations on the active and standby servers are
the same.)
1. In the Installation Wizard window, click Security. -

2. Complete the security hardening as prompted. -

3. Restart the VM and then log in to the VM using the domain account Vdesktop\SWMaster
SWMaster.

57
6.8 Installing the ITA
Step 6 Configure the remote assistant service. (The operations on the active and standby
servers are the same.)
1. On the active ITA server, choose Features > Add Features. -
1

e n
2
/
m
e.i co
w
3

u a
. h
2. Select Remote Assistance.

i n g -

n
1

ar
le
://
3. Click Next and complete the configuration as prompted. -

Step 7 Install the standby ITA server.


t tp
1. Log in to the standby ITA server.
s :h -

ce
2. Install the ITA on the standby server by following the operations in section
r
-

ou
6.8 Installing the ITA.

es
R
i n g
r n
e a
e L
or
M

58
6.9 Installing the Loggetter
Step 1 Add the VM to the domain.
1. Log in to the infrastructure VM hosting the Loggetter service as user
Administrator.

n
2. Click Start, enter sysdm.cpl in Search programs and files, and press -
Enter. Then, click Change in the System Properties dialog box.
/ e
3. Add the infrastructure VM to the domain. 1 Enter the VM name
m
.i co
(B2).

e
3 Enter the infrastructure

w
domain name (D1).
1
u
5 aEnter the domain

. hadministrator username
5
n g and password (F2).

r ni
2

le a
//
3 6

p :
t t
:h
4

e s
r c
4. Restart the VM and then log in to the VM as user Administrator. -

sou
e
Step 2 Add the domain account to the administrator group.
R
ing
1. Click Start, enter compmgmt.msc in Search programs and files, and -
press Enter.

r n
a
2. Open the Add to Group window. -

L e 3

e 4

or
M 1

59
6.9 Installing the Loggetter

Step 2 Add the domain account to the administrator group.


3. Add the domain account to the administrator group. 2 Add the following
accounts:
Tomcat domain
account, for example,
ITAServiceUser (F3)
Domain account used
e n
/
for logging in to the

m
Loggetter server, for

.i co
example, loguser (F1)
Log service domain

7
w e
account, for example,
LogServiceUser (F4)

u a
h
4 Enter the domain
1
g. management account

n
(F2).

ni
6

r Repeat 1 2 3 4 5

le a to add the domain

//
accounts.

p :
t t
:h
4

e s
2
r c
ou
5

es 3

R
i n g
rn
Step 3 Install the Loggetter.

e a
1. Log out of the VM and use the Loggetter login domain account, such -

L
as loguser, to log in to the infrastructure VM on which the Logggetter

e
or
service is deployed.
2. On the Loggetter server, mount You do not need to

M FusionAccess_Installer_Win_V100R005C10SPC100.iso. select Restart the VM


now to install the OS.
3. Double-click the CD-ROM drive directory and click Loggetter in the -
Installation Wizard window.
4. Open the Configure the FileZila and LogServer services window as -
prompted.

60
6.9 Installing the Loggetter
Step 3 Install the Loggetter.
5. Configure the Tomcat account. 2 Enter the log service
domain account, for
example,
LogServiceUser (F4).

e n
1
/
m
.i co
2

3
w e
u a
. h
n g
ni
4

ar
le
://
6. Complete the installation as prompted. -

Step 4 Configure the Loggetter backup task.


t tp
s :h
1. Choose Start > All Programs > Loggetter > Loggetter. -

r ce
2. Configure component IP addresses (B2). Enter the service plane

ou
IP addresses of the
components.

es Enter the floating IP

R address of the DB.


Enter the IP address of

i n g the active node in the

n
first row for the nodes

a r working in

e
active/standby mode.

e L FTP Data
Configuration:retain

or
the default value.

M
3. Click finish. -

Step 5 Perform security hardening.


1. In the Installation Wizard window, click Security. -

2. Complete the security hardening as prompted. -

3. Restart the VM and then log in to the VM using a domain account. -

61
7 Initial Configuration
7.1 Configuring the Virtualization Environment
Step 1 Configure the virtualization environment.
1. Enter http://Service plane IP address of the active ITA:8081 in the http://192.168.181.62:808
address box of your browser and press Enter. 1
2. Enter the username and password. The username and password vary Change the password

e n
/
with the Rights Management Mode set when the ITA is installed. after you log in to
FusionAccess for the first
Rights Management Mode Username Password
m
.i co
time.
Common mode admin Huawei123#
Rights separation mode sysadmin Sysadmin#

w e
3. Click System. -
u a
4. Configure the virtualization environment.
. h4 Enter the floating IP

n g address of the VRM node.

ni
1

r
5 The default password
2

le a is VdiEnginE@234.

3
: //
t t p
4
s :h
r ce
s ou
R
5e
i n g 6

r n
e a
e L 7

or
M

62
7.2 Configuring the Domain
Step 1 Configure the domain.
1. Add the domain information. 4 Enter the domain
1 information (D1).

5 Enter the domain


administrator username
2
3 and password (F2). The

e n
/
domain administrator is

m
used to add VMs to a

.i co
domain.
4
6 Enter the service plane
5
w e
IP addresses of the AD

a
server (B2).

hu
.
6

n g
r ni
le a
: //
7
t t p
s :h
r ce
s ou
Re
i n g
r n
e a
e L
or
M

63
7.3 Configuring Desktop Components
Step 1 Configure the ITA.
1. Configure the database. 4 Enter the service plane
IP addresses of the active
4 and standby GuassDBs.

1 5 Enter the password


e n
/
used for accessing the ITA

m
database. This password

.i co
is set when the ITA is
2 installed.

e
5
6
3
aw
hu
2. Configure the ITA.
g. 1 Enter the service plane

n
IP addresses of the

ni
1 active and standby

r
2
ITAs (B2).
3
le a 2

://
The default value is
8081.

tp
4
5 8
6
t 3 Enter the service plane

:h
7
IP addresses of the active

e s and standby DNSs (B2).

r c 4
Enter the service plane

ou
IP address of Loggerter

es (B2).

R
5
The default value is

i n g 989.

n
6

r
Enter the username of

e a the FTP service account

L
of the log server. The
default value is
e
or
ConfBack_User.

M
7 Enter the password of
the FTP service account
of the log server. The
default value is
Huawei123#.

64
7.3 Configuring Desktop Components
Step 2 Configure the license.
1. Add the license server. 3 Enter the service plane
IP address of the
License server (B2).

1 4 The password of SSH and


the default value is

e n
Huawei@123
/
3
m
.i co
2
4
5

w e
u a
2. Click Return. -
. h
n g
ni
3. Obtain the ESN. -

ar
//le
2
p : 1

t t
:h
4. Apply for a license based on the ESN. For details, see the FusionCloud -

s
Desktop Solution V100R005C20SPCXXX License User Guide, which is

e
c
available in the following path at http://support.huawei.com/enterprise:

r
Product Support > Cloud Computing & Data Centers > Cloud Computing

ou
> FusionAccess > FusionCloud Desktop Solution.
5. Load the license.
es -
1
R
i n g
r n
e a
e L 2

or
M 3

65
7.3 Configuring Desktop Components
Step 3 Configure the Desktop.
1. Add the Desktop information. 2 Enter the Desktop ID.

3 Enter the HDC


1
database instance name
(G1).

e n
/
4 Database IP: floating

m
IP address (B2)

.i co
Active database IP and
2 Standby database IP:

w e
service IP addresses of
the active and standby

4
u a
GaussDB server (B2)

. h5 Enter the HDC

n g database instance user

ni
5 password, which is
7

r
7 Huawei@123 by default.
6

le a 6
Enter the computer

: // name and IP address (B2)

p
8 8 of the service plane VM of

t t the HDC server. The value

:h
9 is the same as that of

s
Name in Configure the

r ce forward and reverse DNS


lookups.

sou 7 The default password

e
of SSH is Huawei@123.

R 8 Enter the name of the

i n g license added in Step 3.

n
ar
2. Click Return to Desktop Configuration List. -

L e
Step 4 Configure the vAG/vLB.

e
or
1. Add the vAGvLB.

M 1 2
2 Enter the service plane
IP address of the vAG
server (B2).

3
3 Select vAGvLB, vAG,
or vLB based on
deployment mode.
4
4
5 The default password
of SSH is Huawei@123.

2. Click Back. -
66
7.3 Configuring Desktop Components
Step 5 Configure the AUS.
1. Add the AUS.
2 Enter the service plane
2 IP address of the AUS
1 (B2).
3
4 The default password

e n
4
of SSH is Huawei@123.
/
m
.i co
5

2. Click Back. -

w e
Step 6 Configure the WI.
u a
. h
3 Enter the service plane IP

g
1. Add the WI information.

1
ni n addresses of the WI (B2).
6 Select Enable and enter the

ar service plane IP addresses

le
of the vAG (B2).

: // 4
7 If Support NAT Access is
selected after you select
p
2

t t Open, enter the public IP

:h
3 address of the firewall in
Service Access Gateway
5
e s config.

c
If Support NAT Access is

r not selected, enter the

ou
6
service IP address of the

es vAG in Service Access


Gateway config.
R Select Enable and enter the
7

i n g service plane IP addresses


of the vAG (B2).
n
ar
8 If Support NAT Access is
8
selected after you select

L e Open, enter the public IP

e
address of the firewall in

or
Self-help console
9 gateway config.

M If Support NAT Access is


not selected, enter the
service IP address of the
vAG in Self-help console
gateway config (B2).

Select Enable and enter the


login attempts based on site
requirements.
2. Click Return. -

67
7.4 Configuring Alarm Components
Step 1 Configure the alarm components.
1. Add the alarm components. 3 Enter the service plane
IP addresses of the
DNS servers (B2).

1 Enter the service plane


4
IP addresses of the

e n
/
DHCP servers (B2).
2
m
.i co
Enter the service plane
5
IP address of the
Loggetter server (B2).
3

w e
4
u a
. h
g
5

ni n
ar
le
6

: //
p
2. Complete the configuration as prompted. -

t t
:h
7.5 Configuring Time Synchronization
Step 1 Configure the DST rules.
e s
r c
ou
1. In the Time Management dialog box, set the time zone. 2 Set the time zone
based on actual

es conditions.

R 3 Select this option if the


1

i n g DST is observed in the

n
time zone.

a r
e
4 Set the data based on
2

e L actual conditions.

or
3

M 4

68
7.5 Configuring Time Synchronization
Step 1 Configure the DST rules.
2. Log in to the active ITA server over VNC using the domain account. -

3. Choose Start > Administrator Tools > Services. -

4. Restart the Apache Tomcat 7 service. -

e n
/
m
.i co
1

w e
u a
h
2

g.
ni
5. Log in to FusionAccess using the service plane IP address of the standby
n -

r
ITA server.
6. Repeat Steps 1 to 4 to configure the DST rules.
le a -

Step 2 Configure time synchronization.


: //
1. Set time synchronization information.
t t p 1
Enter the service plane

:h
IP addresses of the AD

s
servers (B2).
1

r ce 3 If the customer

ou
provides a stable clock
2
s
source, enter the

Re address or domain
name of the clock

ing
3 source.
If the customer does

r n not provide the clock

a 4 source, enter the

L e management IP
addresses or domain

e
or
name of the CNA
nodes hosting the

M
VRMs.

7.6 Checking Component Status


Step 1 Check the components.
1. Choose Alarm> Status Check. -
2. If the status is normal for all components, the components are -
successfully installed.

69
Appendix 1 Configuring the Desktop Cloud Address
(After configuration, you can access FusionAccess from FusionManager.)

Step 3 (Optional) Configure the maintenance network.


2. Log in to the active AD server as user SWMaster. -
3. On the DOS window, run the ipconfig /all command to query the MAC In this example, the
address of the management NIC of the infrastructure VM based on the system management
management plane IP network segment. plane IP network segment

n
is 192.136.1.XXX and the
MAC address of the
management NIC is 28-
/ e
2 6E-D4-88-C6-5C.
m
1
e .i co
aw
4. Run the route print command to query the management NIC interface ID

hu
In this example, the
based on the MAC address.

g. management NIC
interface ID is 13.
2 1
ni n
ar
// le
p :
5. Add route to the active AD server.
t t -

:h
route -p add System administrator PC network segment mask Subnet

s
mask Desktop cloud management plane gateway if Management NIC

e
c
interface ID

r
ou
For example, if the system administrator accesses FusionManager

es
through the 192.154.0.0/23 network segment, management plane
gateway IP address is 192.136.1.1, and the management NIC interface ID
R
is 13, run the following command:

i n g
route -p add 192.154.0.0 mask 255.255.254.0 192.136.1.1 if 13

n
6. If the system administrator needs to access FusionManager through -

a r
multiple network segments, add routes for all the network segments. For

e
details, see Step 5.

e L
7. Log in to the infrastructure VM hosting the standby AD, active ITA, -

or
standby ITA, and Loggetter, respectively and repeat steps 1 to 6 to add
the route data.

70
FusionAccess
Lab Guide

Issue 01
Date: 2015-07
e n
/
m
.i co
Introduction to FusionAccess

w e
Huawei FusionAccess is virtual machine (VM)
u a
management software deployed on a virtualization
. h
n g
ni
platform. It enables users to access virtual desktops

r
by using networked client devices, such as thin clients
(TCs), desktop computers, laptops, and smartphones.

le a
//
FusionAccess transforms the traditional PC-dominated
office model with features such as security,
p :
investment, and office efficiency. It is an optimal
t t
:h
choice for large- and medium-sized enterprises,
government agencies, and mobile offices.
e s
r c
Objectives s ou
Re
This guide help you quickly complete configuration and service provisioning tasks in FusionAccess.

n g
This guide focuses on provisioning and managing services. There are some tasks label as optional, which
i
n
means trainees can skip this task. However, the instructor must prepare those tasks earlier.

a r
1.
L e
Creating Network Resources(Optional)-----------------------------------------------------------------------------P5

e
2. Adding a DHCP Address Pool(Optional)-----------------------------------------------------------------------------P7

or
3. Creating a VM User------------------------------------------------------------------------------------------------------P11
4. Creating a Template-----------------------------------------------------------------------------------------------------P15
M 1) Creating a Template VM-------------------------------------------------------------------------------------P15
2) Installing a VM--------------------------------------------------------------------------------------------------P17
3) Configuring VMs------------------------------------------------------------------------------------------------P21
4) Creating a Full Copy VM Template-------------------------------------------------------------------------P23
5) Creating a Linked Clone VM Template(Optional)-------------------------------------------------------P25
5. Provisioning VMs----------------------------------------------------------------------------------------------------------P32

1
1 Service Provisioning Rulesand
Host Installation ISOApplication
Method Scenarios

1.1 Service Provisioning Rules


The following figure shows the relationships among the template, VM, VM group, user group, and linked clone.

3 4 5 1
User or user group: One or a

n
group of domain users who can

e
/
log in to VMs using domain
accounts.

m
.i co
2
1
Template VM: An empty VM on

e
2 FusionCompute for creating
various types of VM templates.

aw
hu 3
5
g . VM template: A template used
to create VMs for users. You
3
4
ni n can convert a template VM into
a template by configuring or

ar optimizing the template VM or

le
installing software on the

//
template VM.

p : 4

t t VM group: A group of user VMs

:h
created by using the same VM
2 1 template.

e s
c
5
r
ou
Desktop group: a group of VMs
assigned to users or user

s
groups.

Re
1.2 ApplicationgScenarios
n in
r
This document describes how to create and provision VMs by using a full copy template or a linked clone

a
template. The following table describes the functions of VMs created using the two types of templates.

e
e L
Template Application

r
Relationships Between End Users and VMs
Type Scenario
o
M Full copy
After a full copy VM is assigned to a user, the user can only log in to the assigned
VM. After the VM shuts down, the user data and customized configurations are stored.
Office automation
(OA)
Only a user who has Administrator rights can log in to a full copy VM.

If a VM is assigned to a user who is in the static pool, the user can log in to the same
VM each time. However, if the VM is assigned to a user who is in the dynamic
Linked
pool, the user can log in to a different VM each time. By default, the user data and Call center
clone
customized configuration are not stored after a VM shuts down.
Only a user who has Users rights can log in to a linked clone VM.

2
2 Preparations
2.1 Process

Templates include full copy templates and linked clone templates.


e n
Desktop service provisioning is quick provisioning.
/
m
.i co
2.2 Prerequisites
FusionAccess has been installed and configured.

w e
2.3 Obtaining Files
u a
. h
n g
The data planning template created during software installation. This template contains service provisioning

ni
information.

ar
// le
p :
This template is referred to as the Data Planning Template in this document.

t t
2.4 Obtaining Software
s :h
r ce
The VM described in this document runs Windows 7 operating system (OS).

Item Name
s ou Where to Obtain Description

Re Prepared by the lab

g
OS ISO file - -
administrator.

n i n http://support.huawei.com/ent

ar
erprise > Downloads > IT > This tool supports Chinese,
FusionAccess_Mirror_V10

e
Image-making tool FusionCloud > FusionAccess English, and Arabic OS
0R005C20SPCxxx.iso

L
> FusionAccess > image files.

e
V100R005C20SPCxxx

or
OS patches For versions earlier than
(Windows 7 32-bit) 976932: Windows 7 SP1, install

M 976932
2958122
http://www.microsoft.com/zh-
cn/download/details.aspx?id=58
42
976932. For Windows 7 SP1
and later versions, this patch
is not required.
Other path
OS patches 2958122: For Windows 7 SP1 version,
(Windows 7 64-bit) http://support.microsoft.com/kb install 2958122.
/2958122 Select OS patches by the
type and language of OSs.

Prepared by the lab


Application software - -
administrator.

3
2 Preparations (cont.)
2.5 Data
Before provisioning services, plan the following data with lab administrator:
Type Parameter Example Value and Planned Value
(A1) port group name portgrounp
Name of the port group for the service plane. Planned value: __________________

e n
(A2) port group
/
Number of the port group for the service
m
.i co
plane.
133
The VMs with ports in the same port group

e
Planned value: __________________
belong to the same virtual network even if the
VMs are deployed on different physical
servers.
aw
u
A. Network
information (A3) Scope Name
. h
g
UserVM_DHCP
Name of the IP address pool, from which IP

n
Planned value: __________________

ni
addresses are assigned to user VMs.

arIP address pool: 192.134.133.10 to

le
192.134.133.100
(A4) Scope

//
Gateway: 192.134.133.1

:
The IP address segment that can be
Planned value:

p
assigned to user VMs.

t
IP address pool: _________________

t Gateway: __________________
(B1) OU Name
s :h UserOU
a user VM belongs.
r e
Name of the organization unit (OU) to which

c
Planned value: __________________

ou
(B2) Group name vds
B. User
s
Name of a user group.
e
Planned value: __________________

R
information
Username: vdsuser

i n g
(B3) Domain user name and Password
Username and password for logging in to the
Password: Huawei123
Planned value:

r nuser VM. IP address pool: _________________

e a Gateway: __________________

e L (C1) VM name
full_copy
link2

or
C. Template Name of a template VM.
Planned value: __________________
VM

Minformation (C2) Serial number for the ISO VM that


runs Windows XP.
XXXXX-XXXXX-XXXXX-XXXXX-
XXXXX
Planned value: __________________
(D1) VM Group name vds_full
Name of a VM group. Planned value: __________________
D. VM
(D2) VM naming rule vm_namerule##
provisioning
Naming rule for VMs. Planned value: __________________
information
(D3) VM Group name Desktop
Name of a desktop group. Planned value: __________________

4
3 Creating NetworkHost
Resources(Optional Task)
Installation ISO Method

If the user VM uses the network resources created for the service plane during the FusionAccess installation, you
can skip over this section.

3.1 Creating a Port Group

Step 1: Create a port group.


1. Visit http://VRM floating IP address to log in to Obtain the VRM floating IP address from the
e n
FusionCompute. Data Planning Template.
/
m
.i co
2. Choose Network Pool. -

3. Go to the Create Port Group page. 1 Select the distributed virtual switch (DVS)
1
w e
connecting to the service plane.

2
u a
In this example, the management plane

h
3

.
and service plane belong to the same

g
network segment.

ni n
After you choose XXXDVS in the

r
navigation tree, the VLAN pool range is
a
le
displayed on the Summary tab page.

: //
p
4. Set the port group name (A1).

t t
s :h
1
r ce
s ou
Re
i n g
r n
e a
e L
or
M

5
Step 1: Create a port group.
5. Set the VLAN ID (A2). To view the VLAN ID range of the VLAN
pool, click View VLAN Pool.

1 The VLAN ID is used in subsequent


2 operations described in Configure an
aggregation switch, Creating a
Template, and Provisioning VMs.
3
e n
/
m
.i co
6. Confirm the settings and click Create. -

7. In the displayed dialog box, click OK. -

w e
u a
3.2 Configuring the Network Environment
. h
n g
ni
Step 1: Configure an aggregation switch.

ar
1. On the local PC, choose Start, enter telnet switch IP address in the

le
Search text box, and press Enter to log in to the aggregation switch.

//
p :
t t
s :h
e
2. On the DVS, configure IP addresses and gateway IP (A4) for the DHCP VLAN ID is the one

r c
server that allocates IP addresses for user VMs. created in 3.1 "Creating a

ou
<Quidway>system-view Port Group."
[Quidway] interface vlanif Service plane vlanid

es
[Quidway-Vlanifvlanid] ip address Gateway and subnet mask of the Enter the planned DHCP

R
DHCP address pool address pool data (A4).
[Quidway-Vlanifvlanid] dhcp select relay

n g
[Quidway-Vlanifvlanid] dhcp relay server-ip Service IP address of the
i
n
active DHCP server

r
[Quidway-Vlanifvlanid] dhcp relay server-ip Service IP address of the

a
e
standby DHCP server

e L
[Quidway-Vlanifvlanid] quit
[Quidway] quit

or
<Quidway>save

M
3. Run display this to query the configuration result. Before running this
command, run system-
view to go to [Quidway].

6
3.3 Adding a DHCP Address Pool(Optional Task)
Step 1 Create a DHCP address pool.
1. On FusionCompute, choose VM and Template > VM. -
2. Log in to the active DHCP server using virtual network computing (VNC). Login account:
If server security hardening
is performed, the account is
Swmaster.

n
If server security hardening
e
/
is not performed, the account

m
is Administrator.

.i co
Account password: obtained
from the Data Planning

e
Template.

w
a
In this document, the DHCP

u
h
server and AD server are

g. deployed on the same VM.

ni n
Enter to open the DHCP window.
ar
3. On the active DHCP server, enter DHCP in the Search text box and press -

//le
p :
t t
s :h
4. On the active DHCP server, open the New Scope window. -

1
r ce
2
s ou
Re
ing
5. Click Next. -
In the displayed dialog box, set Scope Name (A3) and click Next.

r n
a
6. Enter the start IP address, end IP address, and subnet mask (A4). 1 2

L e Enter the planned DHCP

e address pool data.

or
M 1

7
Step 1 Create a DHCP address pool. (cont.)
7. Specify Excluded address range and click Next. Retain the default values
Set Lease Duration and click Next. of the parameters.
Select Yes, I want to configure these options now and click Next.
8. Configure Router (Default Gateway) (A4). 1 Enter the planned
gateway IP address of the
DHCP address pool.

e n
/
m
.i co
1 2

w e
u a
. h
n g
r ni
3

le a
: //
t p
9. Configure the DNS server for the VMs in the DHCP address pool.

t
2 Enter the service IP
address of the DNS

:h
server.

e s
r c To configure both the

ou
active and standby

es DNS servers, repeat


1 2 3 .

R
ing
1 2 3 If the service IP
address of the DNS

r n server exists by

e a default, you do not


need to add the IP

e L address.

or 4

M
10.Create the DHCP address pool as instructed. Retain the default values of -
the parameters.

8
Step 2 Synchronize the IP address pool on the active DHCP server to the standby DHCP
server
1. Log in to the active DHCP server using virtual network computing (VNC). -
2. On the active DHCP server, enter DHCP in the Search text box and press
Enter to open the DHCP window.

e n
/
m
3. DHCP Split-Scope. -

.i co
1

w e
2 3
u a
. h
n g
r ni
le a
://
4. On the Additional DHCP Server dialog box, add a server. 2 In the dialog box

tp
displayed, enter the IP

t
address or computer

:h
name of the standby
DHCP server.

e s
r c 1

s ou
Re
i n g
n
ar
4

L e
e
or
M 2

5. Click Next. -

9
Step 2 Synchronize the IP address pool on the active DHCP server to the standby DHCP
server
6. On the Additional DHCP Server dialog box, set the Delay in DHCP Offer. 2 In this example, 1000
indicates that the standby
DHCP server starts to
assign IP addresses 1000
ms later.

e n
1 2
/
m
.i co
3

w e
7. Complete the synchronization operation as prompted. -

u a
. h
Step 3 Activate the standby DHCP IP address pool
n g
ni
1. Log in to the standby DHCP server using virtual network computing -
(VNC).
ar
// le
2. On the standby DHCP server, enter DHCP in the Search text box and -

:
press Enter to open the DHCP window.

t t p
s :h
ce
3. Activate the standby DHCP IP address pool.
r
-

ou
1

es
R
i n g
r n
e a 2

e L
or
4. Check that the IP address pool status is the same as follows. -

10
4 Creating a VM Installation ISO Method
User
Host
The relationship between the user OU, user group, and domain users in this document is only an example.
In actual service provisioning, create VM users based on the planned data.

Step 1: Create a user OU.


1. On the FusionCompute portal, choose VM and Template > VM. -

e n
/
2. Log in to the active AD server using VNC. Login account: Swmaster

m
.i co
Account password:
obtained from the Data
Planning Template.

w e
u a
. h
n g
r ni
le a
//
3. Click in the lower left corner of the active AD server desktop. -

p :
4. Create a user OU.
t t If the user OU already

:h
exists, skip over this step.

e s
1
r c
s ou
Re
i n g 2

r n
e a
e L
or
3

M
5. Enter the OU name (B1), for example UserOU, and click OK. Enter the planned name of
the user OU.

11
Step 2: Create a user group.
1. Right-click the created user OU, and choose New > Group. 1 Select the newly
created user OU.

e n
/
m
.i co
1

2
w e
u a
h
3

g.
2. Enter the user group name (B2).

ni n -

ar
//le
p :
t t
:h
1

e s
r c
s ou
Re
i n g
r n
e a 2

e L
or
M

12
Step 3: Create a user.
1. Right-click the created user OU, and choose New > User. 1 Select the newly
created user OU.

e n
/
m
.i co
1

w e
2
u a
. h
n g
r ni
le a
3
: //
t t p
:h
2. Enter the username and login account (B3). -

e s
r c
1
s ou
Re
i n g
r n
a
2

L e
e
or
M 3

13
Step 3: Create a user.
3. Set the account password (B3). 1
The password must:
Contain at least one
uppercase letter (A-Z),
one lowercase letter (a-
1 z), one digit (0-9), and
one space character or
special character
e n
2
(~!@#$%^&*()-
/
m
_=+\|{};:'",<.>/?).

.i co
Contain 8 to 32
characters.

w e
Cannot be same as the
recent three passwords.

u a
Cannot contain the
username or the

. h
username in reversed
3

n gorder.

ni
2

r
Select user password
4. Click Finish.
le a policies based on the
actual requirements.

: //
Step 4: Add the user to the user group.

t t p
:h
1. Add the user to the group. 2 Select the user to be

e s added.

r c
sou
Re 2

ing
3
1

r n
e a
L
2. Select a user group.

e
1 Enter the name of the

or
user group created on
the AD server.

M
1

3. Click OK. -

14
Host Installation ISO Method
5 Creating a Template
5.1 Creating a Template VM
Step 1: Create a template VM.
1. On the FusionCompute portal, choose VM and Template.

e n
/
2. On Getting Started, choose Create VM go to the Create VM page. -
m
3. Select the location for creating the VM.
.i co
Select a location for

e
creating a VM:
1 1

awCluster: The VM is

hu created on any host


2
g. that is under the

n
cluster.

ni
Host: The VM is
3
ar created on a specified
host.

//le
p :
4. Set the following parameters:
t t 1

:h
VM name: (C1)
OS type and version:
1

e s Set the parameters based

r c on the OS of the VM

ou
template to be created.
Note that the value must
2
es be the same as the OS to

R be loaded later.

ing
2

n
Hardware

a r specifications: Set the

e
parameters based on the

e L hardware configuration
requirements.

or
M
5. On the Properties tab page, click Next. -

15
Step 1: Create a template VM. (cont.)
6. Set the port group.
3
Select the port group
created in 3.1 "Creating a
Port Group."
1

e n
/
m
.i co
2

w e
a
3

hu
g.
ni n
4
ar
//le
p :
7. Set Data store, Configuration mode, and Capacity in sequence, and 4

t
click Next. Set Configuration

t
:h
mode to Common for
system disks.

s
1 4 5
When creating a full

r ce copy template, set

ou
Configuration mode to
6 Thick provisioning lazy

es zeroed for user disks if

R this option is available.

2
i n g
rn
e a
e L
or
M
3

8. Check the VM information and click Finish. The creation progress is


displayed in the Task
Center page.
9. In the displayed dialog box, click OK. -

10. Go to the VM tab page. If the VM status is Running,


you can perform subsequent
operations.

16
5.2 Installing a VM
Step 1: Install the OS.
1. Log in to template VM using VNC. In the row that contains
the newly created
1
template VM, click Log In
Using VNC.

e n
/
2

m
3
e .i co
aw
hu
g.
2. Attach the ISO file.
1
ni n 4 The type of the IOS file
must be the same as
2
ar that of the OS selected

le
in 5.1 "Creating a

//
Template VM."
3
p :
t t A host can be mounted to

:h
4
only one CD-ROM drive.

s
Before mounting the CD-

e
5 ROM drive, ensure that the

r c CD-ROM drive is not

ou
6 mounted to any other VM on
this host.

es
R
3. Install the VM OS. During the installation, set the parameters as follows: The VM automatically

ing
restarts multiple times
UI Information Value during installation.
Which type of installation do you want? Custom (advanced)

r
Type a user name
n LocalAccount (or customized)

e a
Help protect your computer and improve Use recommended settings

L
Windows automatically

e
Select your computer's current location Work network

or
4. Unmount the CD-ROM drive. -

M 1

17
Step 2: Activate the administrator account and set the password for this account.
1. On the template VM, go to the Computer Management window. compmgmt.msc

2. Go to the Administrator Properties window. -

e n
/
m
1

e .i co
w
3

u a
h
3. Activate the Administrator account. 1 Deselect this option.

g.
ni n
ar
//le
p :
t t
s :h
r ce
ou
1

es
R
i n g
r n
e a 2

e L
or
4. Set the password for the Administrator account. -

M 2
3

5. Click Proceed, set the password, and click OK twice as prompted. After -
the setting is complete, log off the VM and log in to the VM as
Administrator.

18
Step 3: Disable the firewall on the VM.
1. Click Start, enter gpedit.msc in Search programs and files, and press Enter. -
2. Disable Windows Firewall.

7
2

e n
3 /
m
e.i co
aw
4

hu
5
6
g.
8

ni n
ar
9

//le
p :
t t
s :h
r ce
sou
Re
i n g
n
3. Close the Local Group Policy Editor window. -

a r
L e
e
or
M

19
Step 4: Install the paravirtualized (PV) driver.
1. On the FusionCompute portal, install tools for the template VM. Template VM

e n
/
m
e .i co
aw
hu
2
g.
ni n
ar
le
://
2. On the template VM, install the PV driver according to the OS type. -

tp
1

t
s :h
2
r ce
s ou
e
3. After installation, restart the VM twice according to the displayed -

R
messages and log in to the VM as Administrator.

i n g
r n
a
Step 5: Copy software and install the OS patches.
e
e L
1. Copy the Windows 7 OS patches and application software (non-iso file) to -

or
disk C:\.

M
2. On the template VM, install the OS patches. -
iso file: Find the Windows 7 OS patches on the mounted CD-ROM drive.
Non-iso file: Find the Windows 7 OS patches in C:\ on the VM.

20
5.3 Configuring VMs
Step 1: Use Desktop Cloud Image Optimization Tool to configure the OS for the VM.
1. In the VNC window of the template VM, attach the -
FusionAccess_Mirror_V100R005C20SPCxxx.iso file of Desktop Cloud
Image Optimization Tool.

n
Do not select Restart the VM now to install the OS when attaching the tool or

e
mounting the CD-ROM drive.

/
2. On the VM, open the CD-ROM, double-click run.bat. -
m
.i co
3. Select the clone type. To create a full copy

e
template, select Full

w
copy.

u a To create a linked
clone template, select
1
. h Linked clone.

n g
ni
2

ar
// le
p :
t
4. Configure the OS. -

t
s :h
r ce
s ou
e
2
1
R
i n g
rn
e a
e L
5. Check the data configuration.
3
-

or
M

1
2

6. Restart the VM and log in to the VM as Administrator. -


21
Step 2: Optimize the ISO VM.
1. On the template VM, choose Start > All Programes > Huawei -
FusionAccess, and click Huawei vDesk to run the optimization tool.
2. Click Check. -

e n
/
m
e .i co
aw
hu
g.
ni n
ar
3. Click Optimize.

// le 1 Items marked by red

:
2 circles are

t t p recommended
optimization items

:h
identified by the

s
1 system. Select

r ce optimization items
based on the actual

ou
situation.

es 3 Manually optimize the

R items that cannot be

g
optimized automatically

n i n by the system.

a r
L e
e
or
M 3

Step 3: Install the application software.


1. Install the application software in C:\ on the template VM. -

22
To create a full copy VM, see section 5.4 Creating a Full Copy VM Template.
To create a linked clone VM, see section 5.5 Creating a Linked Clone VM Template.

5.4 Creating a Full Copy VM Template

Step 1: Encapsulate the VM OS.


1. In the VNC window of the template VM, attach If the iso file has been
e n
FusionAccess_Mirror_V100R005C20SPCxxx.iso.
/
mounted, skip this step.

m
.i co
2. In the CD-ROM window on the VM, double-click run.bat. -
3. Encapsulate the OS. 1 Select the clone type
1
w e
based on the template

a
type.

hu
4

g.
ni n After the encapsulation

r
is successful, do not

le a restart the VM.

: // For details about the

t t p application scenarios

:h
for the full copy

e s 2 template, see section 1

r c "Service Provisioning

s ou Rules and

Re Application

g
Scenarios."

n i n
ar
4

L e
e
or 3

M
5

4. Close the Desktop Cloud Image Optimization Tool window. -


5. Unmount the DVR-ROM drive and shut down the VM. -

23
Step 2: Convert the VM into a template.

1. On the FusionCompute portal, choose VM and Template > VM. -

2. Convert the VM into a template. You can view the


conversion progress on
the Task Center page.
The templates that are
1 converted successfully
will be displayed in
Template and
e n
Specifications > VM
/
Template.
m
.i co
2

w e
u a
. h
n g
ni
Step 3: Configure the template on FusionAccess.
1. Log in to FusionAccess.
ar -

le
The address format is https://service IP address of the ITA server:8448.

//
p :
t t
2. On FusionAccess, choose Desktop > Service Configuration > VM -

:h
Template.
1

e s
r c
s ou
3
2

Re
i n g
rn
e a
L
3. Configure a full copy VM template.

e
1 Set the type to Full

or
Copy Template.

M
2 1
1

24
5.5 Creating a Linked Clone VM Template(Optional Task)

Step 1: Set the login policies for the Users user group.
1. On the FusionCompute portal, log in to the active AD server using the -
VNC.
2. In Search programs and files, enter gpmc.msc and press Enter to -
open the Group Policy Management window.
3. Go to the Group Policy Management Editor window. 2
e
Select the group policy
n
/
that has taken effect for

m
the user VM. If there is

.i co
no group policy
available, select Default

e
2 Domain Policy.
3

aw
1

hu
g.
4. Go to the Allow log on locally Properties window.
ni n -

ar
// le
p :
t
2

t
3

s :h
1
r ce
s ou
Re
5. Set Allow log on locally to Not Defined. -

i n g
rn
a
1

L e
e
or
M 2

6. On the template VM, go to the Local Group Policy Editor window. -

25
Step 1: Set the login policies for the Users user group. (cont.)
7. Go to the Allow log on locally Properties window. -

2
3
e n
/
m
.i co
1

w e
8. Click Add User or Group.
u
-
a
9. Add a group.
. h2 Select Groups.

n g
ni
4 Enter Users.

1
ar
// le
p :
t t
:h
4

e s
r c
ou
5

es
R
i n g
r n
2

e a
e L
or
M 3

10. Click OK. The Allow log on locally Properties window is closed. -
11. Close the Local Group Policy Editor window. -

26
Step 2: Add the VM to a domain.
1. On the template VM, go to the System Properties window. sysdm.cpl

2. On the Computer Name tab, click Change, go to the Computer -


Name/Domain Changes window.

e n
1
/
m
e .i co
aw
hu
g.
2
ni n
ar
// le
p :
t t
s :h
r ce
ou
3. Enter the domain information. 1 Enter the
Infrastructure

es domain information

R
obtained from the
Data Planning

i n g Template. If the user


domain is planned,

r n enter the user

e a domain name.

e L 3

or
3 Enter the username
1 and password for the

M 4 domain administrator.
You can obtain this
information from the
Data Planning
2 Template.

4. Click OK twice. The System Properties window is closed. -


5. Click Restart Now to restart the VM, and log in to the VM as -
Administrator.
27
Step 3: Configure a user group.
1. On the template VM, go to the Computer Management window. compmgmt.msc

2. Select a group. 2 When selecting a user group,


note the following:

e
Do not add the user group to
n
the Guests group.
/
m
You can add the user group

.i co
to the Users group only after
the login policy of the Users
1

w e
group is configured.
The users in the Users

a
group do not have VM
u
h
administrator rights.

g .
2
ni n
r
3

le a
: //
p
3. Click Add. -

t t
:h
4. Enter the user group name. 1 The user group name must
be consistent with the user

e s group name added to the

c
user domain on the AD

r server.

ou
After a domain user is

es created on the AD server

R
later, add the domain user to
1 the user group created in this

i n g step. If linked clone VMs are


assigned to this user group,

rn 2 the domain users in this

e a group can log in to the linked

L
clone VMs.

e 1 Enter the username and

or
5. Enter the username and password for the domain administrator.
password for the domain

M
administrator. You can obtain
this information from the
Data Planning Template.

28
Step 3: Configure a user group. (cont.)
6. Delete the Domain Users group. -

e n
/
m
1
e .i co
aw
hu
g.
ni n
2
ar
// le
:
3

t t p
s :h
e
Step 4: Configure the Administrator group.

r c
ou
1. Select the Administrator group. -

es
2
3

R
i n g
r n
a
1

L e
e
or
2. Add the Tomcat account of the ITA service to the Administrator group. Example: ITAServiceUser

M
3. Delete the Domain Admins group. See the substep 6 in Step
3 "Configure a user
group."
4. Shut down the VM. -

29
Step 5: Convert the VM into a template.
1. On the FusionCompute portal, choose VM and Template > VM. -
2. Convert the VM into a template. You can view the
conversion progress on
the Task Center page.
The templates that are
1 converted successfully

n
will be displayed in
Template and
Specifications > VM
/ e
Template.
m
.i co
2

w e
a
Step 6: On FusionCompute, configure an iCache for the template to improve data access
u
h
efficiency.
1. On the FusionCompute portal, choose VM and Template > Template and
g. -
Specifications.
ni n
The VM Template page is displayed.
ar
le
://
2. Configure iCache for the template. The template is the one

tp
created in substep 2 of

t 1 Step 5 "Convert the VM

:h
into a template."

e s 3 Select the host to be

r c configured with the

ou
iCache. The system

es 2
automatically selects the

R host where the template is

ing
located.

r n
a
A VM created from a

e
template can use an

e L iCache only after the


template is configured

or
with an iCache and the
VM runs on a host with

M
3
an iCache.
The iCache can be
configured only when
the storage type is NAS,
virtual local disks, or
LUN Pome.
A template with an
iCache can be used to
4 create a maximum of
512 linked clones.

30
Step 7: Configure the template on FusionAccess.
1. Log in to FusionAccess. -
The address format is https://service IP address of the ITA server:8448.
2. On FusionAccess, choose Desktop > Service Configuration > VM -
Template.
1

e n
/
m
.i co
2

e
3

aw
hu
g .
n
1

i
3. Configure a linked clone VM template. Set the type to Link

r n Clone Template.

1
le a
//
2

p :
t t
s :h
r ce
s ou
Re
i n g
rn
e a
e L
or
M

31
6 Provisioning VMs
Step 1: Create a VM.

1. On the FusionAccess portal, choose Quick Provision, go to the Create This section describes
VM page. how to perform quick
provisioning of full copy
VMs.

e n
2. Set VM group information. Select Existing VM
/
m
Group: Indicates that

.i co
the VM group is
defined previously in

e
Desktop > VM Group

w
> Create VM Group.

a
Create VM Group:

hu Indicates that you need

.
to specify VM group

n g name (D1), VM group

ni
description, and VM

r
group type as planned.

3. Set the site, resource cluster, host, and local domain.


le a Local domain is the

//
domain to which the VM

p : belongs and is configured

t
previously in System >

t Rights Management >

:h
Role Management.

e s
r c
ou
4. Select a VM template. If you need to provision

es 1 full copy VMs, select a

R
template of the
fullcopy type.

ing
If you need to provision
linked clone VMs,
2
r n select a template of the

e a clonelink type.

e L
or
M

32
Step 1: Create a VM.
5. Specify the number of VM CPUs and memory size. Number of CPUs: 1 to 32
Memory size: 1024 MB to
524,288 MB

6. Set the system disk information. 3 If the disk is created based


on the default settings, the
values in 2 and 3 are
consistent with that on the
1 template. If the user changes
the settings in 2 , the
system automatically sets

e n
the value in 3 to the
/
m
recommended value. Retain

.i co
2 3 the recommended value.
If the VM template is full

e
copy template, and the mode

w
4 supports the common mode,

a
you are advised to set Mode

u
to Common.

h
.
If the VM template is full

n g
copy template, set Mode to

ni
Thin provisioning.
5
If the data storage type is

ar FusionStorage, set Mode to

le
Thin provisioning.

7. Set the user disk information.


: // 3 If the disk is created based

t t p on the default settings, the


values in 2 and 3 are

:h
consistent with that on the

e s template. If the user changes

c
the settings in 2 , the

r
1
system automatically sets

ou
the value in 3 to the

es 2 3
recommended value. Retain
the recommended value.
R If the VM template is full
4

i n g copy template, and the mode


supports the Thick

r n provisioning lazy zeroed

e a mode, you are advised to set

L
Mode to Thick provisioning
5 lazy zeroed.
e
or
If the VM template is full
copy template, you are

M
advised to set Mode to Thin
provisioning.
If the data storage type is
FusionStorage, you are
advised to set Mode to Thin
provisioning.

8. Add user disks. Perform this step when you


need to add multiple user disks.
Set the user disk information in
the displayed dialog box by
referring to step 7.
33
Step 1: Create a VM.
9. Set the NIC information. 2 Select the port group of
1 the service plane. Port
groups for the NICs on
the same VM must be
different.

e n
/
2

m
3
e .i co
aw
hu
4
g.
ni n
ar
le
10. Specify the number of VMs to be created. -

: // Select the GPU shared


p
11. Select the GPU shared type.
1
t t type only when you need to

:h
provision full copy VMs.
2

e s
r c
Step 2: Specify VM parameters.
s ou
Re
1. Set the VM computer name and domain. 1 You can define or select

ing
VM naming rule (D2)
from the drop-down list.
1
r n VM naming rule=Prefix

a
+ Number of digits

L e The prefix contains


a-z, A-Z, 0-9, and

e
or
hyphen (-).
Number of digits

M
contains one or
multiple number
signs (#).
The naming rule is
defined previously in
2 Desktop > Service
Configuration > VM
Naming Rule.

34
Step 3: Assign desktops.

1. Configure the desktop group information. Select Existing Desktop


Group: Indicates that
the desktop group is
defined previously in
Desktop > Desktop
1
Group > Create
Desktop Group.
2
Create Desktop Group:
3
e n
Indicates that you need

/
to specify Desktop

m
group type (D3),

.i co
Desktop group
description, and

e
Desktop group type
4

w
as planned.

u a Specify Set
assignment type when

. h you need to provision

n g full copy VMs.

ni
2. Provision VMs. Provision a full copy VM:

ar is1 the user created in 4

le
Creating a VM User. You

//
1 2 can find the user name on

p : the AD server.

t
is2 set to administrators.

t
:h
Provision a linked clone

e s VM:

c
is1 the user group created in

r 4 Creating a VM User. You

ou
can find the user group

es name on the AD server.


is set to users.
R 2

g
3. Click Next. After checking the VM information, click Submit. -

n i n
a r
L e
e
or
M

35
7 Other Service Provisioning Methods
For details about service provisioning, see the FusionCloud Desktop (Standard) V100R005C20 Virtual
Desktop Management Guide. The following tasks are described:
Provisioning VMs running Windows XP, Windows 8.1, Windows Server 2012 R2 or Windows Server
2008 R2 to users who have Administrator rights.
Provisioning VMs running Windows XP, Windows 7, Windows 8.1, Windows Server 2012 R2 or Windows
Server 2008 R2 to users who have Users rights.

e n
Creating VMs from other types of templates and provision the created VMs.
/
m
e .i co
aw
hu
g .
ni n
ar
//le
p :
t t
s :h
r ce
s ou
Re
i n g
r n
e a
e L
or
M

36
The privilege of HCNA/HCNP/HCIE:
With any Huawei Career Certification, you have the privilege on http://learning.huawei.com/en to enjoy:
n
1e-Learning Courses Logon http://learning.huawei.com/en and enter Huawei Training/e-Learning
/e

o m
If you have the HCNA/HCNP certificateYou can access Huawei Career Certification and Basic Technology e-Learning
courses.
e i .c
If you have the HCIE certificate: You can access all the e-Learning courses which marked for HCIE Certification Users.

aw

Methods to get the HCIE e-Learning privilege : Please associate HCIE certificate information with your Huawei account, and

hu

email the account to Learning@huawei.com to apply for HCIE e-Learning privilege.


g .
2 Training Material Download
i n

arn
Content: Huawei product training material and Huawei career certification training material.

//le
MethodLogon http://learning.huawei.com/en and enter Huawei Training/Classroom Training ,then you can download
training material in the specific training introduction page.
p :
3 Priority to participate in Huawei Online Open Class (LVC)
t t

s :h
The Huawei career certification training and product training covering all ICT technical domains like R&S, UC&C, Security,

4Learning Tools: rc e
Storage and so on, which are conducted by Huawei professional instructors.

s o
eNSP Simulate single Router&Switch device and large network.

R e
WLAN Planner Network planning tools for WLAN AP products.

n g
In addition, Huawei has built up Huawei Technical Forum which allows candidates to discuss technical issues with Huawei experts ,

ni
share exam experiences with others or be acquainted with Huawei Products.

a r
Statement:
L e
r e
This material is for personal use only, and can not be used by any individual or organization for any commercial purposes.
o
M
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 1

S-ar putea să vă placă și