FusionCompute V100R005C00 Software Installation Guide 04

FusionCompute
V100R005C00
Software Installation Guide
Issue 04
Date 2015-07-17
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2015. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://enterprise.huawei.com
Issue 04 (2015-07-17) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
FusionCompute
Software Installation Guide About This Document
About This Document
Purpose
This document describes the FusionCompute installation in four stages: installation introduction,
preparations, installation process, and initial configuration.
Intended Audience
This document is intended for software commissioning engineers.
Symbol Conventions
The symbols that may be found in this document are defined as follows:
Symbol Description
Indicates an imminently hazardous situation which, if not

avoided, will result in death or serious injury.
DANGER
Indicates a potentially hazardous situation which, if not

avoided, could result in death or serious injury.
WARNING

avoided, may result in minor or moderate injury.
CAUTION

NOTICE avoided, could result in equipment damage, data loss,
performance deterioration, or unanticipated results.
NOTICE is used to address practices not related to
personal injury.
Issue 04 (2015-07-17) Huawei Proprietary and Confidential ii

FusionCompute
Software Installation Guide About This Document
Symbol Description
NOTE Calls attention to important information, best practices and

tips.
NOTE is used to address information not related to
personal injury, equipment damage, and environment
deterioration.
GUI Image Conventions

The GUI images that may be found in this document are for reference only. See the product GUI
in practice.
Change History
Changes between document issues are cumulative. The latest document issue contains all the
changes made in earlier issues.
Issue 04 (2015-07-17)
This issue is the fourth official release.
Change Description
Added description about the FusionSphere Installer.
Issue 03 (2015-05-08)
This issue is the third official release.
Change Description
Deleted description about the FusionSphere Installer.
Issue 02 (2015-03-12)
This issue is the second official release.
Issue 01 (2014-12-05)
This issue is the first official release.
Issue 04 (2015-07-17) Huawei Proprietary and Confidential iii

FusionCompute
Software Installation Guide Contents
Contents
About This Document.....................................................................................................................ii

1 Overview.........................................................................................................................................1
1.1 FusionCompute Overview..............................................................................................................................................2
1.2 Installation Process.........................................................................................................................................................3
2 Installation Preparations..............................................................................................................6
2.1 System Requirements.....................................................................................................................................................7
2.2 Recommended Configuration Policies.........................................................................................................................16
2.3 Software Packages........................................................................................................................................................16
2.4 Documents and Tools...................................................................................................................................................18
2.5 Data...............................................................................................................................................................................19
3 Software Installation...................................................................................................................22
3.1 Installing Hosts and VRM Nodes Using FusionSphere Installer.................................................................................23
3.2 Installing Hosts.............................................................................................................................................................49
3.2.1 Installing Hosts Using ISO Image.............................................................................................................................49
3.2.2 Installing Hosts in PXE Mode Using FusionCompute Host Installer (Recommended)............................................61
3.2.3 Installing Hosts in PXE Mode with a Third-Party Tool............................................................................................71
3.3 Installing VRM Nodes..................................................................................................................................................77
3.3.1 Installing VRM Nodes on VMs (Recommended).....................................................................................................78
3.3.2 Installing VRM Nodes on Servers...........................................................................................................................104
A Appendix....................................................................................................................................118
A.1 FAQs..........................................................................................................................................................................119
A.1.1 Storage Devices Cannot Be Detected on the FusionCompute................................................................................119
A.1.2 How to Configure an FC SAN Initiator..................................................................................................................125
A.1.3 How to Configure an IP SAN Initiator...................................................................................................................126
A.1.4 How to Create a Management Account for Advanced SAN Devices....................................................................127
A.1.5 How to Configure NIC Binding for the VRM Node..............................................................................................128
A.1.6 How to Setting Multipathing Mode for a Host Using Commands.........................................................................131
A.1.7 How to Cancel the Isolation Between the Service Plane and the Management Plane on a VRM Node................132
A.1.8 How to Troubleshoot the Occupied Port on the FusionCompute Installation Wizard...........................................135
A.1.9 How to Troubleshoot the VM that Failed to Be Initialized Using the FusionCompute Installation Wizard.........137
A.1.10 How to Reconfigure Host Parameters..................................................................................................................138
Issue 04 (2015-07-17) Huawei Proprietary and Confidential iv

FusionCompute
Software Installation Guide Contents
A.1.11 Troubleshooting the Tool of Deploying Hosts in Batches...................................................................................142

A.1.12 Manually Changing the System Time on a Node.................................................................................................145
A.1.13 Troubleshooting the FusionCompute Installation Wizard....................................................................................146
A.1.14 Creating a FusionCompute Tablespace in an Oracle Database............................................................................155
A.1.15 Recommended Configurations for Host Domain 0 Specifications.......................................................................158
A.1.16 Background Information.......................................................................................................................................158
A.1.17 Communication Principles....................................................................................................................................163
A.1.18 Compatibility........................................................................................................................................................168
A.1.19 Communication Principles....................................................................................................................................169
A.1.20 Binding Network Ports.........................................................................................................................................174
A.1.21 How to Handle FusionCompute Installation Failures Caused by a Change in the Local IP Address..................180
A.2 Common Operations..................................................................................................................................................180
A.2.1 Setting Internet Explorer Browser..........................................................................................................................180
A.2.2 Setting Mozilla Firefox Browser............................................................................................................................184
A.2.3 Logging In to FusionCompute..............................................................................................................................185
A.2.4 Verifying Software Packages.................................................................................................................................190
B Glossary......................................................................................................................................191
B.1 A-E.............................................................................................................................................................................192
B.2 F-J..............................................................................................................................................................................193
B.3 K-O............................................................................................................................................................................195
B.4 P-T..............................................................................................................................................................................196
B.5 U-Z.............................................................................................................................................................................197
Issue 04 (2015-07-17) Huawei Proprietary and Confidential v

FusionCompute
Software Installation Guide 1 Overview
1 Overview
About This Chapter
1.1 FusionCompute Overview
1.2 Installation Process
Issue 04 (2015-07-17) Huawei Proprietary and Confidential 1

FusionCompute
1.1 FusionCompute Overview

Logical Nodes
Figure 1-1 shows the logical nodes in the FusionCompute.
Figure 1-1 FusionCompute logical nodes
Site Cluster 1
Management Computing nodes
nodes
Host Host Host
VRM (active)
(Host)
VRM (standby) Cluster 2

Computing nodes
Host Host Host
(Host) …
Storage
…
resources
Cluster n
Computing nodes
Host Host Host
…
NOTE
Storage resources can be provided by storage area network (SAN) devices, network attached storage (NAS)
devices, or local storage devices.
Table 1-1 describes the logical nodes in the FusionCompute.

FusionCompute
Table 1-1 FusionCompute nodes
Node Description
Virtualization A node that implements centralized management of virtual resources.

Resource
Management
(VRM)
Host A physical server that provides computing resources for the

FusionCompute. Certain hosts can also provide storage resources.
Deployment Scheme
Table 1-2 describes the FusionCompute management modes deployment schemes.
Table 1-2 FusionCompute deployment schemes
Node Deployment Deployment Rule

Mode
Host Deployed on Multiple hosts can be deployed based on customer

servers. requirements for computing resources. Certain hosts can
also provide storage resources.
In virtualization deployment, a host must be specified for
creating a VRM VM.
If a small number of hosts (for example, less than 10) are
deployed, add all the hosts to the management cluster. If
a large number of hosts are deployed, create one or more
service clusters for different service types.
To optimize computing resource utilization of each
cluster, configure the same type of data stores and
distributed virtual switches (DVSs) for hosts in the same
cluster.
VRM Deployed on The active and standby VRMs must be deployed on two
VMs. VMs on different hosts in the management cluster.
You are advised to deploy VRMs on VMs.
Deployed on The active and standby VRMs must be deployed on

servers. different physical servers.
1.2 Installation Process

Installation Process
You are advised to use FusionSphere Installer to install FusionCompute. This tool enables the
one-stop installation of hosts and Virtualization Resource Management (VRM) nodes in the

FusionCompute
FusionCompute system. However, FusionSphere Installer cannot be used to install VRM nodes
on physical servers.
If you determine to install FusionCompute without this tool, install hosts and VRM nodes
separately. Figure 1-2 shows the installation process.
Figure 1-2 FusionCompute installation process
Start
Install hosts.
Install the VRM.
End
Installation Introduction (Not Using FusionSphere Installer)

Installing a host: You can install a host use either of the following methods:
l Install hosts in batches using preboot execution environment (PXE). To use this method,
perform the following operations:
– Enable the Dynamic Host Configuration Protocol (DHCP) and File Transfer Protocol
(FTP) services on the local PC.
– Install operating systems on all hosts to be installed.
This method is recommended when the system has a large number of hosts because it allows
concurrent operating system (OS) installation on multiple hosts.
l Install a host by manually mounting an ISO image to the host. This method is recommended
when the system has a small number of hosts.
Install a host by manually mounting an ISO image to the host. This method is recommended
when the system has a small number of hosts.
NOTE
For details about hardware versions, firmware versions, and VM OS versions supported by the
FusionCompute host OS, log in to compatibility check assistant.
Install the Virtualization Resource Management (VRM) node: You can install a VRM on a
VM or on a physical server.
l To install the VRM on a VM, use the FusionCompute installation wizard.
l To install the VRM on a physical server, manually mount an ISO image to the VRM and
configure the VRM.
Installing the VRM on a VM is recommended.

FusionCompute
NOTE
To enhance system security, change the default system account's passwords (for example, the passwords
of gandalf for logging in to a host or the VRM) after the FusionCompute is installed.
For details about how to change the passwords, see FusionCompute V100R005C00 Security Guide.

FusionCompute
Software Installation Guide 2 Installation Preparations
2 Installation Preparations
About This Chapter
2.1 System Requirements
2.2 Recommended Configuration Policies
2.3 Software Packages
2.4 Documents and Tools
2.5 Data

FusionCompute
2.1 System Requirements

Ensure that the PC, servers, storage devices, and networks meet FusionCompute installation
requirements.
PC Requirements
A PC is required for FusionCompute software installation and initial configuration. Table 2-1
lists the PC requirements.
Table 2-1 PC requirements
Item Requirements
CPU Intel or AMD x86 architecture CPU
Memory ≥ 2 GB
Hard disk l The partition for installing the operating system (OS) has more than
1 GB free space.
l Except the partition for the OS, at least one partition has more than
2 GB free space.
OS The PC runs one of the following OSs of 32-bit or 64-bit:

l Windows XP
l Windows 7
l Windows Server 2003
l Windows Server 2008
Network The PC is properly communicating with the management plane and the
baseboard management controller (BMC) plane of hosts. You are
advised to connect the PC and the hosts to be installed to the same switch
and set their IP addresses to the same management network segment.
Resolution To improve visual experience in using the FusionCompute installation

wizard, set the PC resolution to 1280p × 1024p or higher. If the PC runs
a Windows 7 OS, after the resolution is set, choose Start > Control
Panel > Appearance and Personalization > Display and select
Smaller or Medium.
Host Requirements
Table 2-2 lists the host requirements.
NOTE
If servers to be used are used before, restore the servers to factory settings before configuring the BIOS.

FusionCompute
Table 2-2 Host requirements
Item Requirements Remarks
CPU Intel or AMD 64-bit CPU Use CPUs of the same model in each
The CPU supports hardware cluster. If the CPU models of hosts to
virtualization technology, such as Intel be added to a cluster are different,
VT-x or AMD-V, and the CPU enable the incompatible migration
virtualization function must be enabled cluster (IMC) mode for the cluster. For
in the BIOS system. details, see FusionCompute
V100R005C00 Initial Configuration
Guide.
NOTICE
l If the CPU virtualization function is not
enabled for a host, VMs cannot be
created on the host.
l If the CPU models of hosts to be added
to a cluster are different, check whether
any hosts use the CPU model Intel
E5520 @ 2.27GHz or earlier.
If yes, add the hosts to another cluster.
Otherwise, VM migration between
hosts using these CPUs and hosts using
other CPUs may fail, because the CPU
clock mechanisms of the CPUs are
inconsistent.
Memory l Minimum memory size: 8 GB If the host is used to deploy VMs for
l Recommended memory size ≥ 48 management nodes, the host memory
GB must be 3 GB more than the VM
memory. Management nodes include
Virtualization Resource Management
(VRM), FusionManager, Virtual
Service Appliance Management
(VSAM), and FusionStorage Manager.
If the host is used to connected to
FusionStorage, the domain 0 must meet
the requirements listed in Host
Domain 0 Requirements in
FusionStorage V100R003C02 Product
Documentation.
Hard Hard disk size ≥ 16 GB If the VRM is deployed on a VM and

disk the VRM VM uses the local storage, the
hard disk size must be greater or equal
to 96 GB.

FusionCompute
Item Requirements Remarks
Network l Number of network ports ≥ 1 None

port l Recommended number of network
ports: 6
l Recommended network port rate >
1000 Mbit/s
If a host uses an iNIC and the iNIC
needs to be replaced, the iNIC must
meet compatibility requirements listed
in FusionSphere
V100R005C00SPC300 Version
Mapping. If the firmware or drive
version does not meet compatibility
requirements, upgrade it by following
the instructions described in the
supported hardware device document.
NOTICE
Do not deploy a common network interface
card (NIC) and an intelligent NIC (iNIC)
on the same host. If both common NICs and
iNICs are deployed on a host, common
NICs are unavailable.
Redunda l Configure hard disks 1 and 2 as The RAID cards on certain servers
nt array RAID 1 for installing the host OS to must be configured with RAID;
of improve storage reliability. otherwise, the host OS cannot be
independ When setting the boot device in the installed. For details about specific
ent disks host BIOS, set the first boot device requirements for RAID cards, see the
(RAID) to a RAID 1 disk. product documentation delivered with
the server.
l If the host has multiple disks, you
are advised to set up RAID 5 with If the VRM is deployed on a VM,
all the disks except disks 1 and 2. configure hard disks 1 and 2 as RAID
1 for both host OS installation and
l If the customer has special VRM VM disks to improve storage
requirements on RAID, follow the reliability.
requirements.
Table 2-3 lists the host BIOS configuration requirements.

FusionCompute
Table 2-3 Host BIOS configuration requirements
Item BIOS Configuration
Boot device Set the first boot device to a hard disk or a USB flash drive.
If the first boot device is a hard disk, you are advised to select a RAID
1 disk. If no RAID 1 disk is available, you are advised to retain the
default boot sequence unless the customer has special requirements for
the boot sequence.
NOTICE
Ensure that the first boot device of the host is the location where the host OS is
installed. Otherwise, the host may fail to start or use another OS.
For details about host OS installation, see Installing Hosts Using ISO Image or
Installing Hosts in PXE Mode Using FusionCompute Host Installer
(Recommended).
NIC Pre-boot l An onboard NIC driver is used if another OS has been previously
execution installed on the server.
environment l PXE is enabled for NIC1 and disabled for other NICs.
(PXE)
NOTE
If both common NICs and iNICs are deployed on a host, set PXE to Enabled for
the first iNIC and Disabled for other NICs. Otherwise, the PXE function may
become unavailable.
BIOS clock The BIOS clock is set to the local Coordinated Universal Time (UTC).
For example, if the local time is Beijing time (UTC +8) 2013-10-20
08:15:20, set the BIOS clock to 2013-10-20 00:15:20.
Table 2-4 lists the requirements for advanced CPU configurations of the host BIOS.
Table 2-4 Requirements for advanced CPU configurations of the host BIOS
Server Configuration Requirement Remarks

Model Item
Huawei C-State Disabled CPU power-saving function. Disable it

V2 server to prevent disk or NIC failures and clock
or servers inaccuracy.
of other
vendors Execute Disable Enabled Hardware-based security function,
Bit which is displayed as NX or XD on some
servers. Enable it to prevent the server
from restarting due to exceptions.
This function must be enabled if the
cluster where the host is located requires
the incompatible migration cluster
(IMC) mode. For details about the IMC
mode, see FusionCompute
Guide.

FusionCompute
Server Configuration Requirement Remarks

Model Item
Huawei Intel HT Enabled Intel hyper-threading technology.

V1 server technology Enable it to allow the server to support
multithreading, thereby improving CPU
performance.
Intel Enabled CPU virtualization technology. Enable it

Virtualization to allow the CPUs on the server to
tech support virtualization.
Execute Disable Enabled Hardware-based security function,

Bit which is displayed as NX or XD on some
servers. Enable it to prevent the server
from restarting due to exceptions.
This function must be enabled if the
cluster where the host is located requires
the IMC mode. For details about the
IMC mode, see FusionCompute
Guide.
Intel SpeedStep Disabled CPU working mode switching

tech technology, which is displayed as EIST
on newly developed servers. Disable it
to prevent disk or NIC failures.
C-State Disabled CPU power-saving function. Disable it

to prevent disk or NIC failures and clock
inaccuracy.
NOTE
The configuration item name may vary depending on different servers or BIOS versions. Therefore, check
the configuration item information before configuration. If a server does not support a technology or
function, do not configure the function.
If the FusionAccess interconnects to the FusionCompute hypervisor, the host BOIS must meet
the requirements listed in Table 2-5.
Table 2-5 Requirements for advanced CPU configurations of the host BIOS if the
FusionAccess interconnects to the FusionCompute
Configuration Requirement Remarks

Item
P-State Disabled CPU power saving feature.
DCU Streamer Disabled CPU data prefetch function.

Prefetcher

FusionCompute
Configuration Requirement Remarks

Item
DCU IP Prefetcher Disabled IP data prefetch function.
ACPI - MADT Legacy Mode Advanced configuration and power interface,

Mode which allows the OS to manage power
modules.
Memory Frequency 1066 MHz Memory operating frequency.
CLTT Disabled Closed-loop temperature control technology,

which lowers the memory frequency to lower
the system temperature if the system
temperature is excessively high.
NOTE
The configuration item name may vary depending on different servers or BIOS versions. Therefore, check
the configuration item information before configuration. If a server does not support a technology or
function, do not configure the function.
Management Node Requirements

The management nodes refer to the Virtualization Resource Management (VRM) nodes. The
requirements for management nodes are the same regardless of whether the VRM is deployed
on VMs or physical servers.
VRM VM specifications vary, depending on system capacity. Table 2-6 lists VRM VM
specifications.
Table 2-6 VRM VM specifications
System Capacity VRM VM Specifications
200 VMs on 20 physical servers l Number of CPUs ≥ 2

l Memory size ≥ 3 GB
l Disk size ≥ 80 GB




FusionCompute
System Capacity VRM VM Specifications

NOTE
If the VRM node is deployed on a VM, set the space of the system disk on the VRM VM to 80 GB.
If the VRM VM uses local storage on the host, you are advised to set the disk using RAID 1 on the host
(for example, the disk where the host OS is installed) to a data store and create the VRM VM using the
data store to improve VRM VM reliability.
Storage Device Requirements

l Shared storage devices
Shared storage devices include storage area network (SAN) devices, advanced SAN
devices, and network attached storage (NAS) devices. If shared storage devices are used,
configure the management IP addresses and storage IP addresses for the shared storage
devices. In addition, the following conditions must be met for specific storage devices:
– If SAN or advanced SAN devices are used, configure logical unit numbers (LUNs) or
storage pools and map them to hosts.
– If advanced SAN devices are used, create an administrator account for installing the
FusionCompute in addition to admin.
– If multiple IP SAN devices are used, configure the cascading between the IP SAN
devices after software installation.
– If NAS devices are used, configure the shared directories (data stores) and a list of hosts
that can access the shared directories.
– The operating system (OS) compatibility of some non-Huawei SAN devices varies
depending on LUN spaces. For example, if the storage space of a LUN on a certain SAN
device is greater than 2 TB, certain OSs can identify only 2 TB storage space on the
LUN. Therefore, read the storage device product documentation to understand the
Novell SUSE Linux OS compatibility of the non-Huawei SAN devices before you use
the devices.
– If SAN devices are used, use Internet Small Computer Systems Interface (iSCSI) to
connect hosts and storage devices. The iSCSI connection does not require additional
switches, thereby reducing costs.
l Local storage resources
If local storage resources are used, only the free space of the disk on which the host OS is
installed and other bare disks can be used as data stores.

FusionCompute
NOTE
Local storage resources are provided only to the host on which the local disks are located. Note the following
points if local storage resources are used:
l If the system uses only the non-virtualized local storage resources, VM migration cannot be performed.
l Configure local storage resources based on the host computing capability to prevent excess storage
resources when all computing resources on a host are used up.
You are advised to deploy shared storage for service VMs.
Network Requirements
The Simple Network Management Protocol (SNMP) and Secure Shell (SSH) are required for
the switch to enhance security. For SNMP, V3 is recommended.
The Spanning Tree Protocol (STP) protocol is disabled on the switch. Otherwise, an alarm
claiming that the host is faulty may be wrongly reported.
Table 2-7 lists the requirements for communication between network planes in the system.
Table 2-7 Requirements for each network plane
Communication Description Requirement

Plane
Baseboard Specifies the plane used by the Communication between the

management BMC network port on the host. management plane and the BMC
controller (BMC) This plane enables the remote plane of the Virtual Resource
plane access to the BMC system on a Management (VRM) node is
server. normal. The management plane
and the BMC plane can be
combined.

FusionCompute
Communication Description Requirement

Plane
Management Specifies the plane used by the Communication between VRMs

plane management system that manages and other Computing Node Agent
all nodes in a unified manner. All (CNA) nodes on the management
nodes communicate on this plane, plane is normal.
which provides the following IP
addresses:
l Management IP addresses of
all hosts, that is, IP addresses of
the management network ports
on hosts.
l IP addresses of VMs on which
management nodes are
deployed.
l IP addresses of storage device
controllers.
You are advised to configure the
eth0 on a host to the management
network port. If a host has more
than four network ports, you are
advised to configure both eth0 and
eth1 on the host to the management
network ports, and bind them after
the FusionCompute is installed so
that they can work in active/
standby mode.
Storage plane Specifies the plane on which hosts Communication between hosts
and storage units on storage and storage devices on the storage
devices communicate. This plane plane is normal.
provides the following IP
addresses:
l Storage IP addresses of all
hosts, that is, IP addresses of
the storage network ports on
hosts.
l Storage IP addresses of storage
devices.
If the multipathing mode is in use,
multiple VLANs must be
configured for the storage plane.
Service plane Specifies the plane used by user Communication between VRMs
VMs on which services are and host on the service plane is
deployed. normal if VRM nodes are required
to assign IP addresses to service
plane NICs.

FusionCompute
For details about communication principles for different network planes, see Communication
Principles.
2.2 Recommended Configuration Policies

To obtain optimal system performance, you are advised to configure the system adopting the
following policies:
l To enhance network reliability, configure switches in stacking mode and ensure that a host
uses at least two NICs to communicate with each plane when NICs are sufficient.
l Use GE or 10GE ports depends on the estimated network load. Huawei suggests that the
network load be less than 60% of the network port bandwidth. Do not deploy a common
network interface card (NIC) and an intelligent NIC (iNIC) on the same host.
l Deploy the same model of CPUs in one cluster. Otherwise, the VM migration between
hosts may fail. Therefore, deploy host of the same model in a cluster.
l If storage area network (SAN) devices are used, use Internet Small Computer Systems
Interface (iSCSI) to connect hosts and storage devices. The iSCSI connection does not
require additional switches, thereby reducing costs.
l In a system that uses data stores provided by shared storage, add the data stores to all hosts
in the same cluster to allow VM migration between hosts in a cluster.
l Add one data store to a maximum of 16 hosts, because a virtualized data store provides
high performance when it serves a small number of hosts.
l Select an independent LUN on a SAN device to create a data store for a management VM.
Do not use a virtualized data store for a management VM.
l Deploy shared storage for service VMs.
l If the system has Fibre Channel (FC) SAN devices in use, divide zones on the FC switch
to separate networks, enhance FC network security, and facilitate management. If no zones
are divided, an FC disconnection alarm may be incorrectly reported on FusionCompute,
but this alarm does not have adverse impact on storage.
2.3 Software Packages

The software packages vary with the Virtualization Resource Management (VRM) deployment
mode.
Before installing software, you must verify the integrity and validity of software packages. For
details, see Verifying Software Packages.
VRM in Virtualization Deployment

Table 2-8 lists the software packages required for VRM virtualization deployment.

FusionCompute
Table 2-8 Software packages required for VRM virtualization deployment
Software Package Description How to Obtain
FusionCompute Installation wizard for For enterprise users, visit http://

V100R005C00SPC30 FusionCompute support.huawei.com/enterprise and
0_Tools.zip choose Downloads > IT >
FusionCloud > FusionSphere >
FusionCompute Operating system (OS) for FusionCompute >
V100R005C00SPC30 FusionCompute hosts V100R005C00SPC300.
0_CNA.iso
For telecom carrier users, visit http://
FusionCompute VRM VM template files support.huawei.com and choose
V100R005C00SPC30 Software > Carrier IT >
0_VRM.zip FusionCloud > FusionSphere >
FusionCompute >
V100R005C00SPC300.
FusionSphereInstaller. FusionSphere Installation l For enterprises, visit http://

zip tool. support.huawei.com/enterprise
and choose Software > IT >
FusionSphere Tool >
V100R005C00SPC300.
l For carriers, visit http://
support.huawei.com and choose
Software > Carrier IT >
FusionSphere Tool >
FusionSphere Tool
V100R005C00SPC300
.
VRM in Physical Deployment

Table 2-9 lists the software packages required for VRM physical deployment.
Table 2-9 Software packages required for VRM physical deployment
FusionCompute Installation wizard for For enterprise users, visit http://

V100R005C00SPC30 FusionCompute support.huawei.com/enterprise and
0_Tools.zip choose Downloads > IT >
FusionCompute OS for FusionCompute FusionCompute >
V100R005C00SPC30 hosts V100R005C00SPC300.
0_CNA.iso
For telecom carrier users, visit http://

FusionCompute
FusionCompute System image file of the FusionCloud > FusionSphere >

V100R005C00SPC30 VRM FusionCompute >
0_VRM.iso V100R005C00SPC300.
FusionSphereInstaller. FusionSphere Installation l For enterprises, visit http://

zip tool. support.huawei.com/enterprise
and choose Software > IT >
FusionSphere Tool >
V100R005C00SPC300.
l For carriers, visit http://
FusionSphere Tool >
FusionSphere Tool
V100R005C00SPC300
.
2.4 Documents and Tools

Documents
Obtain the documents listed in Table 2-10 before system installation.
Table 2-10 Documents required for system installation
Document Description How to Obtain
Network Design Provides the software Contact the engineering supervisor.

deployment plan.
Integration Design Provides data plan information.

Data Plan Template
FusionCompute Provides information about the For enterprise users, visit http://
V100R005C00SPC mapping between software and support.huawei.com/enterprise
300 Version hardware versions. and choose Downloads > IT >
Mapping FusionCloud > FusionSphere >
FusionCompute >
V100R005C00SPC300.
For telecom carrier users, visit
http://support.huawei.com and
choose Software > Carrier IT >
FusionCompute >
V100R005C00SPC300.

FusionCompute
Tools
Obtain the tools listed in Table 2-11 before system installation.
Table 2-11 Tools required for system installation
Tool Description How to Obtain
PuTTY A cross-platform tool used for Visit http://www.putty.org/ and

accessing nodes on a Windows download this tool.
platform during software installation The tool must be PuTTY Release
0.59 or later. You are advised to
download the latest version from its
official website.
2.5 Data
Table 2-12 describes the data required for installing the FusionCompute.
NOTE
Management planes and storage planes in the FusionCompute system do not support IPv6 addresses.
Table 2-12 Data required for FusionCompute installation
Category Paramete Description Example Value

r
Host Host name Identifies a server in the system. CNA01

informatio l The host name can contain only digits,
n letters, hyphen (-), and underscores (_).
It must start with a letter or a digit, and
cannot exceed 63 characters.
l The host name must be unique in the
system.
This parameter is mandatory.
Managem Specifies the IP address of the host 192.168.4.21

ent IP management network port.
address This parameter is mandatory.
Subnet Specifies the subnet mask of the host 255.255.255.0

mask of management plane.
the This parameter is mandatory.
managem
ent plane

FusionCompute

r
Gateway Specifies the gateway address of the host 192.168.4.1

address of management plane.
managem
ent plane
Virtualiza VRM Identifies a VRM node in the system. VRM01

tion name the VRM node name can contain only
Resource digits, letters, and hyphen (-). It must start
Managem with a letter and cannot exceed 32
ent characters.
(VRM)
informatio This parameter is mandatory.
n Managem Specifies the IP address of the VRM 192.168.4.31
ent IP management network port if the VRM is
address deployed on a physical server or the IP
address of the VRM VM if the VRM is
deployed on a VM.
Subnet Specifies the subnet mask of the VRM 255.255.255.0

managem
ent plane
Gateway Specifies the gateway address of the VRM 192.168.4.1

address of management plane.
managem
ent plane
Floating Specifies the management plane floating 192.168.4.30

IP address IP address of the VRMs.
This parameter is mandatory when VRMs
are deployed in active/standby mode.
Shared Storage Specifies the IP address of the storage 192.168.60.10

storage managem management device.
informatio ent IP The IP address identifies the added storage
n address device.
This parameter is mandatory when shared
storage resources are used in the system.
Storage Specifies the storage port IP address of the 172.20.100.100

port IP storage device.
address This parameter is mandatory when shared

FusionCompute

r
NOTE Storage Specifies the storage device type. IP SAN
These device
paramete Value:
rs are not
type
l IP SAN
required
when FC l Advanced SAN
SAN This parameter is mandatory when shared
storage is
in use.
Storage Value: Huawei
device l Huawei
vendor
l Non-Huawei
This parameter is mandatory when shared

FusionCompute
Software Installation Guide 3 Software Installation
3 Software Installation
About This Chapter
3.1 Installing Hosts and VRM Nodes Using FusionSphere Installer
3.2 Installing Hosts
3.3 Installing VRM Nodes

FusionCompute
3.1 Installing Hosts and VRM Nodes Using FusionSphere

Installer
Scenarios
Use FusionSphere Installer to install hosts and Virtualization Resource Management (VRM)
nodes in the FusionCompute system.
The FusionSphere Installer provides the installation modes described in Table 3-1:
Table 3-1 Installation Mode
Installation Mode Description
Typical installation l Management node location: local disks on

hosts
l Rights management mode: common
Custom installation l Management node location: custom (such

as local disks, and IP SAN and FC SAN
storage devices)
l Rights management mode: custom
(common or rights separation mode)
l Host OS specifications: custom
(Customize the host OS when
FusionAccess or FusionStorage is in-use)
FusionSphere Installer integrates the Dynamic Host Configuration Protocol (DHCP), Trivial
File Transfer Protocol (TFTP), File Transfer Protocol over SSL (FTPS) services. This tool
installs hosts in preboot execution environment (PXE) mode.
NOTE
Prerequisites
Conditions
– Storage media (such as a hard disk or USB flash drive) has been planned for the OS to be
installed on the host.
NOTE
If the space of a hard disk or RAID disk is greater than 2 TB, the system identifies it only as a 2 TB
disk.
– Hosts have been configured based on requirements. For details about the requirements, see
Host Requirements.

FusionCompute
– Hosts to be installed support booting from the network.

– You have obtained the base board management controller (BMC) IP address of the host if
the host has BMC installed.
NOTE
The baseboard management controller (BMC) manages host hardware using Intelligent Platform
Management Interfaces (IPMIs), and is responsible for remote access, control, and management
functions of a host.
– You have obtained the basic input/output system (BIOS) password of the host if the password
has been configured.
– The local PC meets the following requirements:
– The PC runs one of the following OSs of 32-bit or 64-bit:
– Windows XP
– Windows 7
– Windows Server 2003
– The Windows firewall and other network management software of the local PC are
disabled.
– The local PC has a minimum of one disk with available space of greater than 5 GB.
– The DHCP, TFTP, or FTP service is not installed and started on the local PC.
– The local PC is properly communicating with the management plane and BMC plane of
the hosts. You are advised to connect the PC and the hosts to be installed to the same
switch and set their IP addresses to the same management network segment, unless the
management plane has a virtual local area network (VLAN) configured.
– The local PC is properly communicating with the installation plane, which is the network
plane that assigns DHCP addresses and is used for installing hosts. You are advised to
use the management plane as the installation plane. If the IP address of the local PC is
not in the installation plane network segment, configure the DHCP relay on the switch.
NOTE
l Do not add VLAN tags to packets passing through the PXE port during the PXE boot process.
Configure network settings to allow these packets to pass through the port.
– The system time is set correctly on the local PC.
– Except the DHCP server provided by this tool, no other DHCP servers are running in the
installation plane subnet during host installation.
– Servers in the installation plane network, except hosts to be installed, do not require DHCP
addresses.
Data
Table 3-2 describes the data required for performing this operation.

FusionCompute
Table 3-2 Data required for performing this operation

r
DHCP IP pool Specifies the start IP address of the 192.168.60.6

service starting DHCP IP pool and the number of IP
parameter address addresses in the DHCP IP address pool.
s The addresses in this pool can be
Size of allocated to the hosts to be installed. 50
pool
The two parameters determine the IP
address segment that can be allocated by
the DHCP service.
The IP address pool must meet the
following requirements:
l The IP address pool belongs to the
management IP address segment
planned for the hosts and does not
overlap other planned IP addresses in
the management IP address segment,
such as the management IP address
of planned hosts or VRMs.
l All the IP addresses in the pool are
idle.
l The DHCP IP addresses may be used
by devices not included in the
original plan. Therefore, configure
the number of IP addresses in the
DHCP address pool to at least twice
the number of physical nodes.
The parameters are mandatory.
Mask Specifies the subnet mask for the IP 255.255.255.0

addresses in the DHCP IP address pool.
Default Specifies the gateway address of the 192.168.60.1

router DHCP server, that is, the gateway
address of the management plane.

FusionCompute

r
Host Host name Identifies a host. CNA01

informatio l The host name can contain only
n digits, letters, hyphen (-), and
underscores (_). It must start with a
letter or a digit, and cannot exceed 63
characters.
system.
Managem Identifies a physical port. eth0

ent plane The value consists of two parts, eth or
port ID inic and a sequence number, for
example, eth0 or inic0.
The tool uses installation plane ports as
management plane ports by default. You
can change the default ports to other
physical ports on the hosts.
This parameter is optional.
Managem This parameter is mandatory. 192.168.60.21

ent IP
address
Subnet This parameter is mandatory. 255.255.255.0

mask of
the
manageme
nt plane
Gateway This parameter is mandatory. 192.168.60.1

address of
the
manageme
nt plane

FusionCompute

r
Managem Specifies the VLAN used by the 0

ent plane management plane.
VLAN Default value: 0
This parameter is mandatory only when
the management plane VLAN is
specified.
NOTE
If you determine to specify a management
plane VLAN, set the type of the VLAN to
tagged on the connected access switch port
to enable communication between the
management plane and the switch.
If you determine not to specify a
management plane VLAN, set the type of a
configured VLAN on the connected access
switch port to untagged to enable the
management plane to communicate with the
aggregation switch through this VLAN.
Data store Name Specifies the name of the data store to be DataStore01
informatio added to the host.
n This parameter is mandatory.

FusionCompute

r
Storage Specifies the type of the storage device N/A

device used for VRM VM disks.
type Value:
l Local disk: This configuration for
local disks is simple but the
reliability and performance are lower
than that of shared storage devices.
l Shared storage device (SAN and
advanced SAN): The reliability and
storage performance of shared
storage devices are higher than that
of local disks but the configuration
for share storage devices is complex.
However, shared storage devices are
dependent on networks.
You are advised to set the VRM VM to
exclusively use a data store created from
an independent LUN on a SAN device
(recommended) or created from a local
disk. The required RAID configuration
for the data store used by a VRM VM
varies depending on the number of hosts
or VMs in the system. However, the
actual number of hosts and VMs may
vary from the following typical
configurations. You need to configure
RAID to match the higher configuration.
For example, if you have 100 hosts and
200 VMs in your system, select the
recommended RAID configuration for
100 hosts or 3000 VMs. If you have 100
hosts and 5000 VMs, select the
recommended RAID configuration for
256 hosts or 5000 VMs.
l 20 hosts or 200 VMs: RAID 1
consisting of two hard disks
consisting of four data disks and one
hot spare disk
consisting of nine data disks and one
hot spare disk
consisting of nine data disks and one
hot spare disk

FusionCompute

r

consisting of ten hard disks
All the above mentioned disks must be
15000-RPM Serial Attached SCSI
(SAS) disks.
Enable It takes time to create a common disk on N/A

virtualizati a virtualized data store. However, a thin
on provisioning disk can be quickly created
on a virtualized data store, taking the
same time as a common disk on a non-
virtualized data store takes. In addition,
a thin provisioning disk supports
advanced features that improve storage
utilization and system security and
reliability, such as thin provisioning,
snapshots, and live storage migration. A
common disk created on a non-
virtualized data store has higher I/O
performance than disks created on
virtualized data stores but it does not
support the advanced features.
This parameter is deselected by default.
local disks are used.
VRM VM Managem Specifies the IP address of the VRM 192.168.60.31

informatio ent IP VM.
n address Ensure that the IP address belongs to the
management plane network segment.
You are advised to select the
management IP address from a private
network segment, because a
management IP address from a public
network segment may pose security
risks.
Managem This parameter is optional. 2

ent plane Specifies the VLAN of the management
VLAN plane. If you do not specify the value, the
system uses VLAN 0 by default.

FusionCompute

r
VM Specifies the method used to configure Customized

specificati VRM VM specifications. configuration
ons Value:
configurat
ion l By deployment scale
method l Customized configuration
CPU, Specify the number of CPUs and the Eight CPUs, and 8 GB
Memory memory size of a VRM VM. memory
(GB) To configure CPU and memory
specifications by the VM deployment
scale, use the following specifications:
l 200 VMs, 20 physical machines
(PMs): 2 CPUs, 3 GB memory
NOTE
If the VRM VM has two CPUs and 3 GB
memory, the health check tool may
become unavailable.
l 1000 VMs, 50 PMs: 4 CPUs, 5 GB
memory
l 3000 VMs, 100 PMs: 8 CPUs, 8 GB
memory
l 5000 VMs, 200 PMs: 12 CPUs, 16
GB memory
l 30000 VMs, 1280 PMs: 20 CPUs, 30
GB memory
To customize CPU and memory
specifications, refer to the preceding
specifications.
Active/ Floating Specifies the floating IP address of the 192.168.60.30

standby IP address active and standby VRM nodes.
VRM This parameter is mandatory when the
node site has two VRM nodes working in
informatio active/standby mode.
n

FusionCompute

r
Arbitratio Specifies the IP address used to 192.168.60.1

n IP determine the status of the active and
address standby VRM nodes.
This parameter is mandatory when the
site has two VRM nodes working in
active/standby mode.
A maximum of three arbitration IP
addresses can be specified.
The active and standby VRM nodes
periodically send a ping command to all
arbitration IP addresses. An active/
standby switchover is triggered if the
active VRM node cannot be pinged from
any arbitration IP address and the
standby VRM node can be pinged from
at least one arbitration IP address.
You are advised to set the first arbitration
IP address to the gateway address of the
management plane, and set other
arbitration IP addresses to IP addresses
of servers that communicate with the
management plane, such as the active
directory (AD) server or the domain
name server (DNS).
VLAN Specifies the VLAN used by the VLAN 0

management plane.
Default value: 0
specified.
NOTE

FusionCompute
NOTE
l During host installation, after the boot device is set to network, information about the relevant hosts is
displayed on the tool operation interface.
l The tool provides recommended configurations for hosts based on the IP addresses assigned to the
hosts and the sequence in which the hosts are reported to the tool. You can install the hosts using the
recommended configurations or using the configurations modified based on the planned data.
l If you install the hosts using the recommended configurations, IP addresses assigned to the hosts by
the tool during host installation serve as management plane IP addresses of the hosts.
l If multiple hard disks are located on a host, the tool automatically installs the host OS on the hard disk
that locates in the first boot position. For details, see requirements for BIOS boot mode settings in Host
Requirements.
l If both a hard disk and a USB flash drive are located on a host, the tool automatically installs the host
OS on the USB flash drive.
Software
The following software packages are available:
– FusionCompute V100R005C00SPC300_CNA.iso
– FusionCompute V100R005C00SPC300_VRM.zip
– FusionSphereInstaller.zip
You have verified the software package. For details about the verification operations, see
Verifying Software Packages.
Procedure
Create a folder.
1 Create a folder on the local PC and copy FusionCompute
V100R005C00SPC300_CNA.iso and FusionCompute
V100R005C00SPC300_VRM.zip to this folder.
Decompress the software packages.
2 On the local PC, right-click FusionSphereInstaller.zip and choose Extract to
FusionSphereInstaller\ to extract the files in the package to the FusionSphereInstaller
folder.
Run FusionSphere Installer.
3 Run FusionSphereInstaller.exe in the FusionSphereInstaller folder.
NOTE
FusionSphere Installer automatically detects whether .Net Framework and JRE are installed on the
local PC. If they are not installed, you must manually install JRE as prompted and the system
automatically installs .Net Framework in silent mode.
If the automatic installation for Microsoft .Net Framework 4 fails, install Windows Imaging
Component. You can obtain the software from the Windows official website.
l If the PC runs a 32-bit OS, log in to the Microsoft Download Center at http://
www.microsoft.com/en-us/download/details.aspx, and search and download Windows
Imaging Component.
l If the PC runs a 64-bit OS, log in to the Microsoft Download Center at http://
www.microsoft.com/en-us/download/details.aspx, and search and download Windows
Imaging Component (64-bit).
4 Select a language, check the boxes of Host and VRM in the Select Component area, and
click Next.

FusionCompute
5 Select the installation mode.

– For a typical installation scenario, select Typical installation.
– For a custom installation scenario, select Custom installation.
6 Click Next.
The Select the installation path page is displayed, as shown in Figure 3-1.
Figure 3-1 Select the installation path
7 Select the folder you created in Step 1 and click Next.

The Install Host page is displayed.
8 Click next.
The Config Services page is displayed.
Configure services.
9 Specify the DHCP service configuration information, as shown in Figure 3-2.
The service IP address must be accessible to the local PC and the installation plane.

FusionCompute
Figure 3-2 Configure services
NOTE
You are advised to set the DHCP pool capacity to a value greater than or equal to twice of the number
of hosts to be installed.
10 Click Configure.
The system begins to apply the configurations.

NOTE
If the local service IP address resides on a different network segment from the IP addresses in the
DHCP pool, the system displays a dialog box asking you to configure the DHCP relay on the switch
after you click Configure. After configuring the DHCP relay, click OK.
11 After the preceding configuration is complete, click Next.
The Configure Hosts page is displayed.
Install hosts.
12 Boot hosts to be installed from network.
For example, if the Tecal RH2285 server serves as a host, you can restart the host using
the remote control interface of the host BMC system. During the host restart process, press
F11 repeatedly until the screen for selecting a boot mode is displayed, and enable the host
to start from the network.
After the hosts to be installed are booted from network, information about these hosts is
automatically displayed in the host list, and the status of these hosts is Detected.

FusionCompute
NOTE
l In the configuration plan, the first boot device of a host is set to hard disk or USB flash drive.
However, for hosts to be installed in PXE mode, you must set the first boot device to network.
After the hosts are installed, set the first boot device to hard disk or USB flash drive again.
l You are prompted to enter the basic input/output system (BIOS) password during the restart
of certain hosts. The default BIOS password of the Huawei RH series rack server, X series
high-density server, the E6000 blade server, and Huawei Tecal E9000 server is Huawei12#
$ or uniBIOS123.
l If you use another server model, set its boot device to network. For details, see the relevant
hardware information.
l If any of the following conditions are met, boot ten hosts per batch from the network to prevent
host information update failures due to network congestion:
l The local PC connects to the hosts to be installed over a virtual network, for example, the
virtual private network (VPN).
l The network plane used by the local PC, the management plane, and the installation plane
are not the same network plane; therefore, the communication between hosts and the local
PC involves multiple gateways and VLANs.
l The number of hosts to be installed exceeds 50.
13 Determine the installation mode.
– If Typical installation is used, go to Step 14.
– If Custom installation is used, go to Step 17.
14 Determine whether to modify host information.
– If yes, go to Step 15.
– If no, go to Step 23.
15 Configure a host.
In the host list, select a host and right-click Modify, or double-click the host to modify host
information on the displayed Configure Hosts page, as shown in Figure 3-3.

FusionCompute
Figure 3-3 Configure Hosts
16 Click OK after the modification to switch to the Install Host page.

After this step is complete, go to Step 22.
17 Determine whether to modify host information.
18 Configure a host.
In the host list, select a host and right-click Modify, or double-click the host to modify host
information on the displayed Configure Hosts page, as shown in Figure 3-4.

FusionCompute
Figure 3-4 Configure Hosts
19 Determine whether to configure the management plane VLAN tag or the Domain 0
specifications.
20 On the Configure Hosts page, click Display Advanced Settings and drag the scroll bar
downwards, as shown in Figure 3-5.

FusionCompute
Figure 3-5 Advanced settings
21 Configure the management plane VLAN tag or the Domain 0 specifications and click
OK.
The Configure Hosts page is displayed.
– Management plane VLAN tag:
The management plane uses VLAN 0 to communicate with other planes by default. To
use a custom VLAN for the management plane, change this parameter to the desired
value.
– dom0_max_vcpus: specifies the maximum number of supported VCPUs in Domain 0.
If the host uses 10GE common NICs, and the VMs to be created on the host require
HW_V_NET NICs, set max_vcpus to 6.
For details about HW_V_NET NICs, see the FusionCompute V100R005C00 Virtual
Machine Management Guide.
– dom0_reserve_vcpus: specifies the number of reserved VCPUs for Domain 0.
– dom0_mem(MB): specifies the memory size of Domain 0.
If the VMs to be created on the host require HW_V_NET NICs, set the Domain 0
memory as follows:
– If the host total memory is less than 1024 GB, set dom0_mem(MB) to 4 GB.
– If the host total memory is greater than or equal to 1024 GB, set dom0_mem
(MB) to the following size: 3 + Host total memory/512 GB.
If the host total memory is 2048 GB, set dom0_mem(MB) to 7 GB (3 + 2048/512
= 7 GB).
If the estimated number of VM disks on the host in the future is greater than 300, expand
the memory size of Domain 0.

FusionCompute
The memory size to be added (M) can be calculated according the following formula:
M = [50 + 2 + (Number of total virtual disks – 300) x 3] MB
– dom0_mem_for_icache(MB): specifies memory size reserved for the iCache function.
– dom0_ramdisk(MB): specifies the available memory for the system if the host
operating system (OS) is installed on a USB flash drive.
– dom0_udisk_tmpfs(MB): specifies the available tmpfs size for the /tmp/udisk
directory if the host OS is installed on a USB flash drive.
– dom0_log_tmpfs(MB): specifies the available tmpfs size for the /var/log directory if
the host OS is installed on a USB flash drive.
To connect the system to FusionAccess, the Domain 0 must meet requirements listed
in Software Installation Process in the FusionCloud Desktop V100R005C20 Software
Deployment Instruction.
If FusionStorage is used to provide storage for the system, the Domain 0 must meet
requirements listed in Installation and Commissioning in FusionStorage
V100R003C02 Product Documentation.
For details about the Domain 0 configuration, see Recommended Configurations for
Host Domain 0 Specifications.
22 (Optional) Configure hosts in batches.
Click Export to export the host configurations as an Excel file.
To identify the host, use the host installation port MAC address. Edit the host configurations
in the Excel file based on the planned host information and click Import to import the data
to the system.
23 Install hosts.
In the host list, select one or multiple hosts and right-click Start Install one by one. The
host installation automatically starts.
NOTE
l On the host information table, you can click the column header to sort the hosts by order.
l To select multiple hosts, hold down Ctrl or Shift and click the left mouse button.
l To select all hosts at a time, hold down Ctrl and press A.
l If the number of hosts to be installed is greater than 10, the tool automatically installs 10 hosts
in a batch, which usually takes a maximum of 20 minutes.
Install the VRM node.

24 After the hosts are installed, click Next.
A dialog box is displayed, the following information:
Click OK to finish host installation, click Cancel to install other hosts.

25 Click OK.
The Install VRM page is displayed.
26 Click Next.
The Config VRM page is displayed.
27 Determine the installation mode.
– If Typical installation is used, go to Step 28.

FusionCompute
– If Custom installation is used, go to Step 35.

28 Determine the subsequent operation based on the VRM deployment mode.
– To make the VRM node works in standalone mode, go to Step 29.
– To make the VRM nodes work in active/standby mode, go to Step 31.
29 Select A Single VRM Node.
30 Configure the following parameters:
– Install Scales
– The VRM node IP
– Netmask
– Gateway
After this step, go to Step 33.
31 Select Active & standby VRM.
– Install Scales
– The float IP address: Enter the floating IP address of the active and standby VRM
nodes.
– The active VRM node IP
– The standby VRM node IP
– Netmask
– Gateway
33 Click Next to verify the configurations.
After the verification succeeds, the Choose Host page is displayed.
34 Click Config VRM on the Chose Host page as instructed and wait until the VRM node is
installed.
– To make the VRM node works in standalone mode, go to Step 36.
– To make the VRM nodes work in active/standby mode, go to Step 40.
36 Select A Single VRM Node.
37 Set VRM VM specifications.
Select pre-defined VM specifications or customize VM specifications based on the system
deployment scale. The mappings between the system capacity and VRM VM specifications
are as follows:
– 200 VMs, 20 physical machines (PMs): 2 CPUs, 3 GB memory
NOTE
If the VRM VM has two CPUs and 3 GB memory, the health check tool may become unavailable.
– 1000 VMs, 50 PMs: 4 CPUs, 5 GB memory

FusionCompute
VRM VM specifications can be modified.

– Node Name
– Node IP
– Netmask
– Gateway
39 To specify the management virtual local area network (VLAN) for the VRM VM, select
Config Management VLAN Tag and set VLAN ID.
If you do not specify the management VLAN, the system uses VLAN 0 by default for the
management plane.
40 Select Active & standby VRM.
41 Set VRM VM specifications.
Select pre-defined VM specifications or customize VM specifications based on the system
deployment scale. The mappings between the system capacity and VRM VM specifications
are as follows:
NOTE
VRM VM specifications can be modified in future.
– The float IP: Enter the floating IP address of the active and standby VRM nodes.
– The active node name
– The active node IP
– The standby node name: Set it to a name that is different from the active node name.
– The standby node IP
– Netmask
– Gateway
– Arbitration IP01: Set it to the gateway of the management plane.
– Arbitration IP02 and Arbitration IP03: Set them to the IP addresses of any servers
that can communicate with the management plane, such as the AD server or the DNS
server. These parameters are optional.
NOTE
If all the arbitration IP addresses fail, the system fails to recognize the active VRM. Therefore, both
VRM nodes become standby nodes and stop providing services.
If any of the arbitration IP addresses of the devices are to be changed, you are advised to change the
VRM arbitration IP addresses to the new ones before the IP addresses are changed.

FusionCompute
43 To specify the management virtual local area network (VLAN) for the VRM VM, select
Config Management VLAN Tag and set VLAN ID.
If you do not specify the management VLAN, the system uses VLAN 0 by default for the
management plane.
44 Click Next to verify the configurations.
After the verification succeeds, the Choose Host page is displayed.
45 Select the host where the VRM VM is to be deployed and click Config Host.
46 After "Host Configure Successfully" is displayed, click Next to switch to the Choose Store
Type page.
Figure 3-6 Choose Store Type
47 Check the type of the storage used.

– Local-Storage: The configuration process is simple, but the reliability and storage
performance are subtly lower than those of shared storage.
If host local storage is used, go to Step 48.
– Shared storage (FC SAN and IP SAN): The configuration process is complex, but the
reliability and storage performance are higher than those of local storage.
– If FC SAN storage is used, go to Step 50.
– If IP SAN storage is used, go to Step 55.
The RAID 1 disk using local storage is recommended for the VRM node.
48 Select Local-Storage, and click Next.

FusionCompute
The Configure Data Store window is displayed.

49 Select a data store on the host where the VRM VM is to be created and leave Enable
Virtualization unchecked.
Go to Step 74.
50 Select FC SAN, and click Next.
The Configure DataStore(FC SAN) window is displayed.
51 Click Obtain Host Initiator.
The WWN value of the FC SAN initiator connected to the host is displayed.
52 Configure the FC initiator based on the WWN value.
Configure the obtained host WWN as a new initiator on the logical host (group) initiator
of the storage device.
For details, see the documentation delivered with the storage device.
53 Click Fresh Storage.
Information about all available storage devices is displayed.
54 Select a data store on the host where the VRM VM is to be created.
Go to Step 74.
55 Select IP SAN, and click Next.
The Configure Storage Interface window is displayed.
56 (Optional) If networking binding is required, click SetBinding to configure.
The following binding modes are available for common network interface cards (NICs):
– Active-backup: applies to scenarios where two network ports are to be bound. This
mode provides high reliability. The bandwidth of the bound port in this mode equals to
that of a member port.
– Round-robin: applies to scenarios where two or more network ports are to be bound.
The bandwidth of the bound port in this mode is higher than that of a member port,
because the member ports share workloads in sequence.
This mode may result in data packet disorder because traffic is evenly sent to each port.
Therefore, MAC address based load balancing prevails over Polling in load sharing
modes.
– IP address and port-based load balancing: applies to scenarios where two or more
network ports are to be bound. The bandwidth of the bound port in this mode is higher
than that of a member port, because the member ports share workloads based on the
source-destination-port-based load sharing algorithm.
Source-destination-port-based load balancing algorithm: When the packets contain
IP addresses and ports, the member ports share loads based on the source and destination
IP addresses, ports, and MAC addresses. When the packets contain IP addresses, the
member ports share loads based on the IP addresses and MAC addresses. When the
packets contain only MAC addresses, the member ports share loads based on the MAC
addresses.
This mode is recommended when the virtual extensible LAN (VXLAN) function is
enabled. This mode allows network traffic to be evenly distributed based on the source
and destination port information in the packets.
– MAC address-based load balancing: applies to scenarios where two or more network
ports are to be bound. The bandwidth of the bound port in this mode is higher than that

FusionCompute
of a member port, because the member ports share workloads based on the MAC
addresses of the source and destination ports.
This mode is recommended when most network traffic is on the layer 2 network. This
mode allows network traffic to be evenly distributed based on the MAC addresses.
– MAC address-based LACP: This mode is developed based on the MAC address
based load balancing mode. In MAC address-based LACP mode, the bound port can
automatically detect faults on the link layer and trigger a switchover if a link fails using
the LACP protocol.
– IP address-based LACP: applies to scenarios where two or more network ports are to
be bound. The bandwidth of the bound port in this mode is higher than that of a member
port, because the member ports share workloads based on the source-destination-IP-
address-based load sharing algorithm. When the packets contain IP addresses, the
addresses. In this mode, the bound port can also automatically detect faults on the link
layer and trigger a switchover if a link fails using the LACP protocol.
This mode is recommended when most network traffic goes across layer 2 and layer 3
networks.
The following binding modes are available for intelligent network interface cards (iNICs):
– Source MAC address-based load balancing: applies to scenarios where two or more
MAC address of the source port.
– Destination MAC address-based load balancing: applies to scenarios where two or
more network ports are to be bound. The bandwidth of the bound port in this mode is
higher than that of a member port, because the member ports share workloads based on
the MAC address of the destination port.
– Source IP address-based load balancing: applies to scenarios where two or more
than that of a member port, because the member ports share workloads based on the IP
address of the source port.
– Destination IP address-based load balancing: applies to scenarios where two or more
address of the destination port.
mode allows network traffic to be evenly distributed based on the destination IP
addresses.
57 Click Add Interface.
A dialog box is displayed, as shown in Figure 3-7.

FusionCompute
Figure 3-7 System interface configuration
58 Set the host storage port name, select the network port, and set IP address, Mask, and
VLAN for the storage interface on the host.
– IP address: Specifies the IP address used for communication between the host and the
storage device.
– If the storage plane uses a layer 2 network, set it to an idle IP address that
communicates with the storage plane. For example, if the storage IP address of the
storage device is 172.20.100.100 and subnet mask is 255.255.0.0, set the IP address
to 172.20.XXX.XXX.
– If the storage plane uses a layer 3 network, set it to an IP address that communicates
with the storage IP address of the storage device.
– Mask: specifies the subnet mask for the storage ports.
– VLAN: specifies the virtual local area network (VLAN) of the storage plane.
– Routing Configuration: specifies the route information for layer 3 network
communication.
NOTE
If the host storage plane uses intelligent NICs (iNICs), the layer 3 routed network cannot be
configured.
– Network destination: specifies the first IP address of the network segment that the
target storage device uses, for example, 192.168.0.0.
– NetMask: specifies the subnet mask of the subnet network segment.

FusionCompute
– Gateway: specifies the gateway of the storage ports. The gateway address and the
storage IP address must belong to the same network segment.
If SAN devices are used and multipathing is required, configure multiple storage interfaces
for a single storage network port.
For example, if a storage device has four storage paths, using VLAN4, VLAN5, VLAN6,
and VLAN7, respectively, the network port eth2 on the host is to be configured to
intercommunicate with VLAN4 and VLAN5, and eth3 to intercommunicate with VLAN6
and VLAN7, configure storage interfaces VLAN4 and VLAN5 on eth2, and VLAN6 and
VLAN7 on eth3.
NOTE
The parameters of all the storage ports (except the host management port Mgnt-0) can be modified
after they are set.
59 Click OK.
60 Check whether all the planned storage ports have been added.
– If no, perform Step 57 to Step 59.
61 Click Next.
The Configure Storage Resources window is displayed.
62 Click Add.
A dialog box is displayed.
63 Select the storage resource (indicating a physical storage device)type.
– SAN: common IP SAN device like S5600 or S5500T of V100 version.
– Advanced SAN: eXtreme Virtualization Engine (XVE) storage devices like S5500T
of V2 version.
In a system that uses advanced SAN devices, if advanced features (for example,
snapshots and linked clones) are not required, you can follow the common IP SAN
device configuration method.
64 Set the parameters of the storage resource (indicating a physical storage device).
– Set the following parameters for a SAN device:
– Vendor
– Name
– Management IP address and Port number: identify the added storage device.
Enter the management IP address of one controller.
– Storage IP address and Port number: If multipathing is used, enter all storage IP
addresses and port numbers of the storage device controller at a time. For example,
in a system that uses OceanStor S5500T, if multipathing is used, you must enter
eight storage IP addresses and port numbers of the OceanStor S5500T controllers A
and B. The storage IP address in-use cannot be changed.

FusionCompute
NOTE
Each logical unit number (LUN) of an HP P4300G2 SAN device uses an iSCSI link to connect
to the host. However, all these links are presented as one IP address. Therefore, this IP address
can be used as the management IP address and the storage IP address.
If HP P4300G2 SAN devices are to be added, set Management IP address and Storage IP
address to the same IP address. Do not add other storage IP addresses.
– Set the following parameters for an Advanced SAN device:
– Name
– Management IP address and Port number: identify the added storage device and
can be used to access the storage device. Enter one or more storage IP addresses and
port numbers of the storage device controller.
– Username: specifies the username of the storage device administrator account. Do
not set it to admin.
– Password: specifies the password of the storage device administrator account.
65 Click OK.
The added storage resources are displayed.
66 Check whether to change the host multipathing mode based on the type of storage resources
to be added.
SAN devices require the multipathing function. In the FusionCompute, the default
multipathing mode of hosts is universal multipathing. If Huawei SAN storage devices are
to be added, set the multipathing mode of the hosts to Huawei multipathing to improve
multipathing performance.
– If Huawei SAN devices or advanced SAN devices are to be added, go to Step 67.
– If other SAN devices are to be added, go to Step 68.
67 Set the multipathing mode to Huawei multipathing if you did not perform this operation
after the host OS was installed. For details, see How to Setting Multipathing Mode for
a Host Using Commands.
68 Select the added storage resources, right-click the selected resources, and choose
Associate.
69 After the association is complete, click Next.
The Configure Data Store window is displayed.
70 Click Obtain Host Initiator.
The WWN value of the IP SAN initiator connected to the host is displayed.
71 Make a note of the world wide name (WWN) of the host in the upper corner of the page,
and log in to the storage device management software to configure the storage device
initiator.
For details, see How to Configure an IP SAN Initiator.
NOTE
If the storage device management software does not support the JRE version running on the PC, do
not replace the JRE on the PC. Otherwise, the installation fails. To resolve this issue, prepare another
PC that is in the same network segment as the current PC and install the JRE version supported by
the storage device management software. Then, use this PC to configure the storage device initiator.
72 Click Fresh Storage.

FusionCompute
73 Select a data store on the host where the VRM VM is to be created.

74 Click Next to switch to the Rights Management page.
75 Select a rights management mode for the VRM node.
– Common mode: This mode implements high usability. One account can be granted all
operation rights in the system.
– Rights separation mode: This mode implements high security. One account can be
granted rights of only the administrator sysadmin, secadmin, or secauditor, so that
administrator rights are isolated from each other and mutually supervised.
– System administrator (sysadmin): has permission to operate and maintain system
services and create and delete user accounts. The created user accounts are locked
and do not belong to any role.
– Security administrator (secadmin): has permission to manage rights of user accounts
and roles but has no rights to create user accounts. A user account created by the
system administrator can be used only after the security administrator assigns a role
to it and unlocks it.
– Security auditor (secauditor): has permission to view and export logs and audit other
administrators' operations.
Rights separation mode is recommended when users have high requirements on
security.
NOTE
l Before selecting Rights separation mode for FusionCompute, ensure that components that
interconnect to the FusionCompute (such as the FusionManager and the FusionAccess) support
this mode.
l After the FusionCompute installation is complete, the rights management mode cannot be
changed.
76 Click Next to switch to the Create VRM page.
77 Click Install VRM as instructed and wait until the VRM node is installed.
78 Determine whether to deploy the FusionCompute data services on an independent Oracle
database.
FusionCompute data services run in the embedded database by default. You can also set
the data services to run on an independent Oracle 11gR2 database server or cluster.

NOTE
Before deploying an Oracle database to run the FusionCompute data services, create a
FusionCompute tablespace in the database. For details, see Creating a FusionCompute
Tablespace in an Oracle Database.
79 Click Configure Oracle DB.
The Oracle DB Configuration dialog box is displayed.
– IP address: specifies the IP address of the Oracle server.
– Port: specifies the port number of the Oracle server.

FusionCompute
– Instance Name or Service Name: specifies the instance or service created on the Oracle
server and has the FusionCompute tablespace created. For details, see Creating a
FusionCompute Tablespace in an Oracle Database.
The Oracle database configuration start and takes about 5 minutes.
82 Close the Oracle DB Configuration dialog box after the database is configured.
83 Click Finish.
Close the FusionSphere Installer.
To ensure system security, you are not allowed to log in to the VRM node using Secure
Shell (SSH) as user root. Instead, you can log in to the VRM node using SSH as user
gandalf. You can also switch to user root when required.
The default password for user root to log in to the VRM VM is Huawei@CLOUD8!. The
default password for user gandalf to log in to the VRM VM is Huawei@CLOUD8.
Change the password as soon as possible to ensure system security.
----End
3.2 Installing Hosts
3.2.1 Installing Hosts Using ISO Image
3.2.2 Installing Hosts in PXE Mode Using FusionCompute Host Installer (Recommended)
3.2.3 Installing Hosts in PXE Mode with a Third-Party Tool
3.2.1 Installing Hosts Using ISO Image
Scenarios
When there are a small number of hosts in the system, install the operating systems (OSs) on
the hosts by mounting an ISO image to them. The OS provides hardware virtualization services.
NOTE
Prerequisites
Conditions
Host Requirements.
– The PC is properly communicating with the management plane and the baseboard
management controller (BMC) plane of hosts. You are advised to connect the PC and the
hosts to be installed to the same switch and set their IP addresses to the same management
network segment.

FusionCompute
– You have obtained the IP address, username, and password for logging in to the BMC of the
physical servers.
Data
You have obtained the following data about the host:
– Host name
– Information about the management network interface card (NIC), including the IP address,
gateway address, and subnet mask. Usually, eth0 is set to the management NIC.
– User root password
– The planned management plane VLAN (if you need to specify the host management plane
VLAN).
NOTE
If you determine to specify a management plane VLAN, set the type of the VLAN to tagged on the connected
access switch port to enable communication between the management plane and the switch.
If you determine not to specify a management plane VLAN, set the type of a configured VLAN on the
connected access switch port to untagged to enable the management plane to communicate with the
Software
FusionCompute V100R005C00SPC300_CNA.iso
Procedure
Switch to the host installation window.
NOTE
The following example describes how to install the host OS on a Tecal RH2285 server by mounting an
image file to the host using the BMC remote control function. eth0 serves as the management NIC.
1 Disable the Windows firewall on the local PC.

2 Open the browser on the PC, enter http://BMC IP address of the host in the address box,
and press Enter.
NOTE
The baseboard management controller (BMC) manages host hardware using Intelligent Platform
Management Interfaces (IPMIs), and is responsible for remote access, control, and management
functions of a host.
The login page is displayed.
3 Log in to the BMC system on the host.
The default username is root, and the default password is Huawei12#$.
The host management page is displayed.
NOTE
If you cannot log in to the BMC system of a single blade server, log in to the Subrack Management
Module (SMM) of the blade server and open the remote control window of the server.
4 Click Remote Control.

FusionCompute
You may need to click Remote Virtual Console (requiring JRE) on the Remote Control
page of some Huawei server BMCs.
The remote control window is displayed.
5 Click on the toolbar.

6 Select Image File in the image dialog box and click Browse.
7 Select the image FusionCompute V100R005C00SPC300_CNA.iso and click Open.
8 Click Connect in the image dialog box.
When Connect changes to Disconnect, the image is mounted to the host.
9 On the toolbar, click , choose Cold Reset, and click Yes in the displayed dialog box.
The host begins to restart.
10 During the restart, press F11 repeatedly until the boot device selection screen is displayed.
Then set the boot device to CD/DVD-ROM or DVD-ROM, as shown in Figure 3-8.
Figure 3-8 Select Boot Device
The installation page is displayed.
NOTE
You are prompted to enter the basic input/output system (BIOS) password during the restart of certain
hosts. The default BIOS password of the Huawei RH series rack server, X series high-density server,
the E6000 blade server, and Huawei Tecal E9000 is Huawei12#$ or uniBIOS123.
11 Select Install within 30 seconds after the page is displayed, and press Enter.
NOTE
If you do not select Install within 30 seconds after the installation page is displayed, the host starts
from the local disk by default. If this occurs, restart the host, select the CD/DVD-ROM as the boot
device, and select Install.
The system automatically loads the ISO image file, which takes about 3 minutes. When the
loading is complete, Main Installation Window is displayed, as shown in Figure 3-9.

FusionCompute
Figures in this section include sample parameter values, which may vary from the actual
parameter values on the site.
Figure 3-9 Main Installation Window
NOTE
During the host configuration process, the following parameters are mandatory: Hard Drive, Network,
Hostname, Timezone, Password, and Dom0 setting.
You configure LogServer to set a third-party save path on the log server and configure Driver to allow
users to install additional drivers. The two configuration items are not required during the
FusionCompute host OS installation.
Configure the disk information.
You are advised to set Hard Disk to its default value. Then, the system installs the OS on the
first identified disk, which is usually a disk using RAID 1. If the server has a built-in USB flash
drive, the OS will be installed on this drive.
NOTE
If the space of a hard disk or RAID disk is greater than 2 TB, the system identifies it only as a 2 TB disk.
If no disk information needs modification, simply run the Configure network information for
the host. command.
NOTE
When configuring host data:
l Press Tab or the up and down arrow keys to move the cursor.
l Press Enter to expand or execute the highlighted item.
l Press the space bar to toggle between options.
12 Select Hard Drive to switch to the disk selection page.

13

FusionCompute
NOTICE
Ensure that the selected disk is the location where the host OS is installed. Otherwise, the
host may fail to start or use another OS.
Select the disk where the OS is to be installed, press Tab to move the cursor to OK, and
select OK.
Configure network information for the host.
14 Select Network and the management port (for example, eth0).
The eth0 configuration screen is displayed.
NOTE
Configure an IP address for only one NIC of each host. Otherwise, network communication may fail.
If both common NICs and iNICs are deployed on a host, set the first iNIC (usually named inic0) to
the management NIC.
15 Determine whether to specify a VLAN for the management plane.
The management plane VLAN must be designed in advance, and the management plane
used by the active and standby management nodes must use the same management plane
VLAN. The management VLAN used by hosts can be different than that used by the
management nodes, but the VLANs must be connected.
NOTE
If you determine to specify a management plane VLAN, set the type of the VLAN to tagged on the
connected access switch port to enable communication between the management plane and the switch.
16 Place the cursor between the brackets preceding Manual address configuration, and press
the space bar to select it.
17 Configure the IP address and subnet mask for eth0, as shown in Figure 3-10.
– IP Address: Enter the host management IP address.
– Netmask: Enter the subnet mask of the host.
NOTE
To prevent invalid entering, use number keys on the keyboard rather than the numeric keypad to
enter numbers.

FusionCompute
Figure 3-10 IP Configuration for eth0
18 Select OK to finish the eth0 configuration.

Go to Step 22 after this step.
19 Place the cursor between the brackets preceding Manual address configuration with
VLAN, and press the space bar to select it.
20 Configure the IP address, subnet mask, and VLAN for eth0, as shown in Figure 3-11.
– VLAN: Enter the planned management plane VLAN.
NOTE
enter numbers.

FusionCompute

22 On the network configuration screen, enter the gateway address of the management plane
in Default Gateway, as shown in Figure 3-12.
Figure 3-12 Network Configuration
23 Select OK to finish the gateway configuration.

Configure the host name.
24 On the host name configuration screen, select Hostname, delete the original information,
and enter the host name, as shown in Figure 3-13.
Figure 3-13 Hostname Configuration
25 Select OK.
Configure the time zone.
26 Select Timezone to enter the Time Zone Selection screen, as shown in Figure 3-14.

FusionCompute
Figure 3-14 Time Zone Selection
27 Select the time zone for the current site.

28 In Date/Time, enter the current time in the format YYYY-MM-DD/HH:MM:SS.
29 Select OK to finish the time zone configuration.
Configure the password for user root.
30
NOTICE
The entered password is encrypted. If you enter an unwanted password by mistake and do
not notice it, you cannot log in to the host after installation. Therefore, the following
suggestions are provided to prevent this issue:
l Enter the password slowly and carefully.
l To enter an uppercase letter, use the shift key rather than the Caps Lock key.
Select Password and enter the password and the confirm password, as shown in Figure
3-15.

FusionCompute
Figure 3-15 Root Password Configuration
NOTE
The password must contain at least:
l Eight characters
l One space or one of the following special characters: ~!@#$%^&*()-_=+\|[{}];:'",<.>/?
l Two of the following combinations:
l Lowercase letters
l Uppercase letters
l Digits
31 Select OK to finish the password configuration.
Configure the log server.
NOTE
A log server is required only when the host OS is installed on a USB flash disk.
32 Determine whether to configure a log server.

33 Select LogServer to switch to the log server configuration page.
Figure 3-16 shows the log server configuration page.

FusionCompute
Figure 3-16 LogServer Configuration
34 Enter the information about the log server in correct format as prompted.
– LogServer: Enter the transport protocol and IP address of the log server.
– LogServerPath: Enter the directory where logs will be stored on the log server.
– LogServerUsername: Enter the username of log server.
– LogServerPassword: Enter the password of the log server.
Configure Domain 0.
By default, host Domain 0 has two virtual CPUs (vCPUs) and 3 GB memory, and has no memory
configured for iCache. The Domain 0 specifications need to be configured if FusionAccess or
FusionStorage storage is used.
35 Determine whether to interconnect with the FusionAccess.

36 Select Dom0 setting to enter the Domain 0 configuration screen.
37 Set the Domain 0 parameters, as shown in Figure 3-17.
– max_vcpus: specifies the maximum number of supported VCPUs in Domain 0.
If the host NIC is a 10GE common NIC and the NIC model of VMs planned to be created
on the host is HW_V_NET, set max_vcpus to 6.
For details about HW_V_NET, see FusionCompute V100R005C00 Virtual Machine
Management Guide.
– reserve_vcpus: specifies the number of VCPUs reserved for Domain 0.
– mem(MB): specifies the memory size of Domain 0.
If the host NIC model of VMs planned to be created on the host is HW_V_NET,
configure the Domain 0 memory based on the following configuration rules:

FusionCompute
– If the total host memory is less than 1024 GB, set the Domain 0 memory size to 4
GB.
– If the total host memory is greater than or equal to 1024 GB, set the Domain 0
memory size to (3 + Total host memory/512) GB.
For example, if the total host memory is 2048 GB, set the Domain 0 memory size
to (3 + 2048/512) GB, that is, 7 GB.
If the estimated number of VM disks on the host in the future is greater than 300, expand
the memory size of Domain 0.
The memory size to be added (M) can be calculated according the following formula:
M = [50 + 2 + (Number of total virtual disks – 300) x 3] MB
– mem_for_icache(MB): specifies memory size reserved for the iCache function.
– If the host provides storage for FusionStorage and the main memory is an SSD card,
move the cursor to SSD for storage and press the space bar to select this option.
Figure 3-17 Configure Domain 0
If the host OS is installed on a USB flash drive, the following parameters are displayed:
– ramdisk(MB): specifies the root partition size of the USB flash drive.
– udisk_tmpfs(MB): specifies the tmp partition size of the USB flash drive.

FusionCompute
– log_tmpfs(MB): specifies the log partition size of the USB flash drive.
38 Select OK to finish the domain 0 specifications.
Install the host.
39 Select OK.
A dialog box is displayed asking you whether to install the OS on the default disk partition.
40 Select Yes.
A dialog box is displayed, asking you whether all configurations are complete.
41 Select Yes.
42 Check whether the following information box is displayed:
Figure 3-18 shows the Warning dialog box.
Figure 3-18 Warning dialog box
– If yes, select Yes. The host OS installation begins.

– If no, no further action is required. The host OS installation begins.
The installation process takes about 10 minutes. After the installation, the host restarts
automatically. When the login information is displayed, the host installation is complete.
During the host restart, Failed may be displayed for some items. Failed items do not have
adverse impact on the host.
If no operation is performed on the interface for a long period of time, a black screen is
displayed. Press ctrl to switch to the installation page.
If the mounted CD/DVD-ROM driver is lost during installation due to a network failure,
reinstall the host.
Install other hosts.
43 Install all the other hosts.
Repeat Step 2 to Step 42 for each host to be added.
To ensure system security, you are not allowed to log in to the host using Secure Shell
(SSH) as user root. Instead, you can log in to the host using SSH as user gandalf. During
the installation process, you can switch to user root if required.
The default password for user gandalf to log in to the host is Huawei@CLOUD8.

FusionCompute
NOTE
If in the date plan, the two VRM hosts are used to create user VMs and the user VMs use Huawei
SAN storage devices, set the multipathing mode to Huawei mode by running commands after the
OSs are installed on the two hosts. For details, see How to Setting Multipathing Mode for a Host
Using Commands.
You can set the multipathing mode for non-VRM hosts on the management web client.
NOTE
After the host installation is complete, the NIC state is Down if the NIC has DHCP disabled and is
not assigned any IP address. If the network connection is normal, the NIC will be automatically
activated in subsequent operations and change to the Up state.
----End
3.2.2 Installing Hosts in PXE Mode Using FusionCompute Host

Installer (Recommended)
Scenarios
Install operating systems (OSs) on hosts to provide hardware virtualization services.
This section describes the conditions, configurations, and operations required when you use the
FusionCompute Host Installer tool to install hosts in the FusionCompute system.
The FusionCompute Host Installer tool integrates the Dynamic Host Configuration Protocol
(DHCP), Trivial File Transfer Protocol (TFTP), and File Transfer Protocol (FTP), and File
Transfer Protocol server (FTPS) services, and uses pre-boot execution environment (PXE) to
install hosts. The FTPS username is install and its default password is Install_123. In FTPS
mode, transferred data is encrypted using the self-signed certificate. The FTPS account is used
only during the host installation. Therefore, you do not need to change or reset the password and
replace the certificate.
If you have a PXE server deployed or have the preceding three services deployed, you can install
hosts in PXE mode without FusionCompute Host Installer. For details, see Installing Hosts in
PXE Mode with a Third-Party Tool.
NOTE
Prerequisites
Conditions
– Storage media (such as a hard disk or USB flash drive) has been planned for the OS to be
installed on the host.
NOTE
If the space of a hard disk or RAID disk is greater than 2 TB, the system identifies it only as a 2 TB
disk.
Host Requirements.
– Hosts to be installed support booting from the network.

FusionCompute
– You have obtained the base board management controller (BMC) IP address of the host if
the host has BMC installed.
– The local PC must meet the following requirements:
– Windows XP
– Windows 7
– The Windows firewall and other network management software of the local PC are
disabled.
– The local PC has a minimum of one disk with available space of greater than 5 GB.
– The DHCP, TFTP, or FTP service is not installed and started on the local PC.
– The local PC is properly communicating with the management plane and BMC plane of
the hosts. You are advised to connect the PC and the hosts to be installed to the same
switch and set their IP addresses to the same management network segment, unless the
management plane has a virtual local area network (VLAN) configured.
– The local PC is properly communicating with the installation plane, which is the network
plane that assigns DHCP addresses and is used for installing hosts. You are advised to
use the management plane as the installation plane. If the IP address of the local PC is
not in the installation plane network segment, configure the DHCP relay on the switch.
NOTE
l Do not add VLAN tags to packets passing through the PXE port during the PXE boot process.
Configure network settings to allow these packets to pass through the port.
– The system time is set correctly on the local PC.
– Except the DHCP server provided by this tool, no other DHCP servers are running in the
installation plane subnet during host installation.
– Servers in the installation plane network, except hosts to be installed, do not require DHCP
addresses.
Data

r
DHCP IP pool Specifies the start IP address of the 192.168.4.50

service starting DHCP IP pool and the number of IP
parameter address addresses in the DHCP IP address pool.
s The addresses in this pool can be
allocated to the hosts to be installed.

FusionCompute

r
Size of The two parameters determine the IP 50

pool address segment that can be allocated by
the DHCP service.
The IP address pool must meet the
following requirements:
l The IP address pool belongs to the
management IP address segment
planned for the hosts and does not
overlap other planned IP addresses in
the management IP address segment,
such as the management IP address
of planned hosts or VRMs.
l All the IP addresses in the pool are
idle.
l The DHCP IP addresses may be used
by devices not included in the
original plan. Therefore, configure
the number of IP addresses in the
DHCP address pool to at least twice
the number of physical nodes.
The parameters are mandatory.
Default Specifies the gateway address of the 192.168.4.1

router DHCP server, that is, the gateway
address of the management plane.
Mask Specifies the subnet mask for the IP 255.255.255.0

addresses in the DHCP IP address pool.
Host Host name Identifies a host. CNA01

informatio l The host name can contain only
n digits, letters, hyphen (-), and
underscores (_). It must start with a
letter or a digit, and cannot exceed 63
characters.
system.

FusionCompute

r
Managem Identifies a physical port. eth0

ent plane The value consists of two parts, eth or
port ID inic and a sequence number, for
example, eth0 or inic0.
The tool uses installation plane ports as
management plane ports by default. You
can change the default ports to other
physical ports on the hosts.
Managem This parameter is mandatory. 192.168.4.21

ent IP
address
Subnet This parameter is mandatory. 255.255.255.0

mask of
the
manageme
nt plane
Gateway This parameter is mandatory. 192.168.4.1

address of
the
manageme
nt plane
Managem Specifies the VLAN used by the 0

ent plane management plane.
VLAN Default value: 0
specified.
NOTE

FusionCompute
NOTE
l During host installation, after the boot device is set to network, information about the relevant hosts is
displayed on the tool operation interface.
l The tool provides recommended configurations for hosts based on the IP addresses assigned to the
hosts and the sequence in which the hosts are reported to the tool. You can install the hosts using the
recommended configurations or using the configurations modified based on the planned data.
l If you install the hosts using the recommended configurations, IP addresses assigned to the hosts by
the tool during host installation serve as management plane IP addresses of the hosts.
l If multiple hard disks are located on a host, the tool automatically installs the host OS on the hard disk
that locates in the first boot position. For details, see requirements for BIOS boot mode settings in Host
Requirements.
l If both a hard disk and a USB flash drive are located on a host, the tool automatically installs the host
OS on the USB flash drive.
l If exceptions, such as error messages displayed on the tool operation interface or host installation failed
or timed out, occurred on the tool, handle the faults by following operations provided in
Troubleshooting the Tool of Deploying Hosts in Batches.
Software
– FusionCompute V100R005C00SPC300_CNA.iso
– FusionCompute V100R005C00SPC300_Tools.zip
Procedure
Decompress software packages.
1 Decompress FusionCompute V100R005C00SPC300_Tools.zip on the PC.
The HostInstaller, Installer, PlugIn, and ToDPS folders are generated.
Run FusionCompute Host Installer.
2 Run FusionComputeHostInstaller.exe in the HostInstaller folder.
The Select Language dialog box is displayed.
NOTE
If a message is displayed indicating that .net Framework is not installed, run
dotNetFx40_Full_x86_x64.exe in the PlugIn folder to install the plug-in. After the plug-in is
installed, restart the local PC.
3 Select a language and click OK.
The Install Components page is displayed, and the system automatically installs the
required components.
4 After the components are installed, click Next.
The Configure Services page, as shown in Figure 3-19, is displayed.

FusionCompute
Figure 3-19 Configure Services
Configure services.
5 Set the installation source.
Set the installation source to the directory that contains FusionCompute

V100R005C00SPC300_CNA.iso on the local PC.
6 Configure the DHCP service.
Set the IP address that is used by the local PC to communicate with the installation plane
as the service IP address.
Enter the DHCP service configuration information.

7 Click Configure Services.
The service configuration starts.

8 After the service is configured, click Next.
The Install Hosts page, as shown in Figure 3-20, is displayed.

FusionCompute
Figure 3-20 Install Hosts
Install hosts.
9 Boot hosts to be installed from network.
After the hosts to be installed are booted from network, information about these hosts is
automatically displayed in the host list, and the status of these hosts is Detected.

FusionCompute
NOTE
l In the configuration plan, the first boot device of a host is set to hard disk or USB flash drive.
However, for hosts to be installed in PXE mode, you must set the first boot device to network.
After the hosts are installed, set the first boot device to hard disk or USB flash drive again.
l For example, if the Tecal RH2285 server serves as a host, you can restart the host using the
remote control interface of the host BMC system. During the host restart process, press
F11 repeatedly until the screen for selecting a boot mode is displayed, and enable the host to
start from the network.
NOTE
The baseboard management controller (BMC) manages host hardware using Intelligent
Platform Management Interfaces (IPMIs), and is responsible for remote access, control,
and management functions of a host.
l You are prompted to enter the basic input/output system (BIOS) password during the restart
of certain hosts. The default BIOS password of the Huawei RH series rack server, X series
high-density server, the E6000 blade server, and Huawei Tecal E9000 server is Huawei12#
$ or uniBIOS123.
l If you use another server model as a host, set its boot device to network. For details, see the
relevant hardware information.
l If information about hosts to be installed failed to display in the host list, handle the fault by
following operations provided in Host information cannot be automatically displayed on the
Install Hosts page..
l If any of the following conditions are met, boot ten hosts per batch from the network to prevent
host information update failures due to network congestion:
l The local PC connects to the hosts to be installed over a virtual network, for example, the
virtual private network (VPN).
l The network plane used by the local PC, the management plane, and the installation plane
are not the same network plane; therefore, the communication between hosts and the local
PC involves multiple gateways and VLANs.
l The number of hosts to be installed exceeds 50.
10 (Optional) Configure a host.
In the host list, select a record and right-click Modify, or double-click the record to modify
host information on the displayed Configure Hosts page.
11 (Optional) Configure hosts in batches.
Click Export. The configuration information in the host list is exported into an excel file.
Edit the excel file, click Import, and select the excel file.
12 Install hosts.
Click Install, as shown in Figure 3-21. Host installation begins.

FusionCompute
Figure 3-21 Install Hosts
NOTE
If the number of hosts to be installed is greater than 10, the tool automatically installs 10 hosts as a
batch, which usually takes a maximum of 20 minutes.
13 (Optional) Install another batch.
Click Install Another Batch.

14 After the hosts are successfully installed, click Next.
Click Finish to exit the FusionCompute Host Installer tool.
NOTE
To ensure system security, the installed hosts do not support direct login using Secure Shell (SSH)
as user root. You can log in to the installed hosts using SSH as user gandalf, and then switch to user
root if required.
The default password of user gandalf is Huawei@CLOUD8.
After hosts are installed in batches, the default root user password is Huawei@CLOUD8!.
Configure Domain 0.
By default, host Domain 0 has two virtual CPUs (vCPUs) and 3 GB memory, and has no memory
configured for iCache. The Domain 0 specifications need to be configured if FusionAccess or
FusionStorage storage is used.
15 Determine whether to set Domain 0 specifications.

FusionCompute

– If no, no further action is required.
16 In the remote control window, log in to an installed host as user gandalf.
17 Run the su - root command and enter the password of user root to switch to user root.
18 Run the following command to configure Domain 0 specifications:
/usr/sbin/modifyUVPSpec.sh -m max_vcpus -m mem -i mem_for_icache -l log_tmpfs
-r ramdisk -t udisk_tmpfs
– max_vcpus (parameter after -u): specifies the maximum number of supported VCPUs
in Domain 0.
If the host NIC is a 10GE common NIC and the NIC model of VMs planned to be created
on the host is HW_V_NET, set max_vcpus to 6.
For details about HW_V_NET, see FusionCompute V100R005C00 Virtual Machine
Management Guide.
– mem (parameter after -m): specifies the memory size of Domain 0.
If the host NIC model of VMs planned to be created on the host is HW_V_NET,
configure the Domain 0 memory based on the following configuration rules:
– If the total host memory is less than 1024 GB, set the Domain 0 memory size to 4
GB.
– If the total host memory is greater than or equal to 1024 GB, set the Domain 0
memory size to (3 + Total host memory/512) GB.
For example, if the total host memory is 2048 GB, set the Domain 0 memory size
to (3 + 2048/512) GB, that is, 7 GB.
– mem_for_icache (parameter after -i): specifies memory size reserved for the iCache
function.
The following parameters are required only when the host OS is installed on a USB flash
drive:
– log_tmpfs (on the right of -l): specifies the log partition size of the USB flash drive.
– ramdisk (on the right of -r): specifies the root partition size of the USB flash drive.
– udisk_tmpfs (on the right of -t): specifies the tmp partition size of the USB flash drive.
NOTICE
Ensure that the mem and mem_for_icache values are followed by a unit without a space.
If you do not specify a unit (K, M, or G), the unit is KB by default. If the value of either
of the memory parameters is too small, the system may fail to start.
K indicates KB; M indicates MB; and G indicates GB.
For example, if you want to set the memory size to 12 GB, enter 12288M or 12G.
For example, if the Domain 0 has two VCPUs, 3584 MB memory, and 12288 MB reserved
for the iCache function, run the following command:
/usr/sbin/modifyUVPSpec.sh -u 2 -m 3584M -i 12288M
The configuration is successful if the following information is displayed:

FusionCompute
modify system dom0 specification success
19 If the host uses a solid-state drive (SSD) as the data disk, run the following command to
configure the storage type for Domain 0:
/usr/sbin/modifySpec -p on
20 Run the following command to restart the host for the configuration to take effect:
reboot
21 configure other hosts.
For details, see Step 16 to Step 20.
----End
3.2.3 Installing Hosts in PXE Mode with a Third-Party Tool
Scenarios
Hosts in the FusionCompute system require operating systems (OS) to provide virtualized
services using hardware resources on the hosts.
This topic describes how to use a third-party tool to deploy a preboot execution environment
(PXE) server and install OSs on hosts in the FusionCompute system in PXE mode.
This PXE server must have the File Transfer Protocol (FTP), Trivial File Transfer Protocol
(TFTP), and Dynamic Host Configuration Protocol (DHCP) services deployed.
If you want to install hosts in PXE mode but have no PXE server deployed, you can use the host
installation tool provided by FusionCompute to install hosts in batches in PXE mode. For details,
see Installing Hosts in PXE Mode Using FusionCompute Host Installer (Recommended).
Prerequisites
l Hosts to be installed support booting from the network.
l You have planned the storage media (hard disks or USB flash disks) for storing host OSs.
l You have obtained host configuration data, including host names, management IP
addresses, subnet masks, gateways, and virtual local area network (VLAN) IDs.
l You have obtained the host baseboard management controller (BMC) IP address, user
name, and password for logging in to the BMC.
l You have obtained the password for logging into the host basic input/output system (BIOS)
if the password has been configured.
l You have obtained the planned management plane VLAN (if you need to specify the host
management plane VLAN).

FusionCompute
NOTE
l You have obtained the MAC addresses of the network ports on the hosts used for PXE
loading.
l No DHCP server is running on the management plane subnet. Ensure that only one DHCP
server (on the PXE server) is enabled during the installation process. If the DHCP server
is not deployed on the management plane, configure DHCP relay on the switch to ensure
that hosts on the management plane can obtain IP addresses from the DHCP server.
l A decompression software application that can decompress .iso files has been installed on
the PC.
l You have deployed the PXE server, which has the FTP, TFTP, and DHCP services
deployed. The PXE server can be deployed on the local PC.
l The PXE server meets the following requirements:
– The PXE server can communicate with the planned management plane and the host
BMC plane. You are advised to connect the PXE server to the switch that connects to
the target hosts and set the PXE server IP address to the planned management network
segment.
– The system time of the PXE server is correct, so that the hosts can synchronize correct
time from the server.
Software
You have obtained the following software:
l FusionCompute V100R005C00SPC300_CNA.iso
l pxelinux.0 (Optional. If the PXE server has other PXE boot files, the software is not
required). You can obtain it from the PlugIn folder in the FusionCompute
V100R005C00SPC300_Tools.zip package.
Procedure
Decompress installation package.
1 Decompress FusionCompute V100R005C00SPC300_CNA.iso on the local PC.
The following file and folders are obtained:
– all (folder)
– boot (folder)
– isolinux (folder)
– repo (folder)
– TRANS.TBL (file)
Configure the FTP service.

FusionCompute
2 Copy all the obtained file and folders to the shared directory of the FTP service on the PXE
server.
NOTICE
This shared directory cannot contain any other files or folders. Otherwise, the host OS
installation may fail.
3 In the shared directory, make N – 1 copies of the all folder and name all the all folders the
planned host names, respectively.
N indicates the number of hosts to be installed.
For example, three hosts (Host01, Host02, and Host03) are to be installed. In this case,
make two copies of the all folder, and name the three folders Host01, Host02, and
Host03, respectively.
4 Based o the host data plan, modify the host configuration files in the folders named host
names.
Path to a host configuration file: Host name/cfg/UVPOSsetup.conf
For example, if a host is named Host02, the path to its configuration file is Host02/cfg/
UVPOSsetup.conf.
NOTICE
After a configuration file is modified, save it as a UNIX file. Otherwise, the configuration
file cannot be resolved.
For details about saving a file as a UNIX file, see Saving a Configuration File as a UNIX
File.
Edit the following items in the configuration file:
– Edit the <sysconfig> field to set the basic information. The following content is an
example:
<sysconfig>
HOSTNAME=""
TIMEZONE="Asia/Beijing"
UTC="1"
</sysconfig>
– Enter the host name on the right of HOSTNAME. The host name must be the same
as the name of the folder housing the configuration file.
– Enter the time zone in the format of Continent/City on the right of TIMEZONE,
for example, Asia/Beijing.
– Edit the field to set the network information for the network interface card (NIC) used
for PXE loading. The following content is an example:
<netconfig-0>
BOOTPROTO="dhcp"
DEVICE="eth0"
IPADDR=""
NETMASK=""

FusionCompute
STARTMODE="onboot"
</netconfig-0>
– netconfig-X: specifies the serial number of the NIC used for PXE loading.
DEVICE: specifies the name of this NIC. The default values of the two parameters
are eth0. For example, if the NIC used for PXE loading is eth0, set netconfig-X to
netconfig-0 and DEVICE to eth0.
– BOOTPROTO: specifies the method of obtaining IP address for the host NIC used
for PXE loading. To assign a fixed IP address and a default VLAN ID (VLAN 0) to
the NIC, set BOOTPROTO to static; to assign a fixed IP address and a custom
VLAN ID to the NIC, set BOOTPROTO to none; to make the NIC automatically
obtains an IP address, set BOOTPROTO to dhcp. You are advised to assign a fixed
IP address to the NIC based on the data plan.
– IPADDR: specifies the host IP address. If BOOTPROTO is set to static, set
IPADDR to the management IP address of the host.
– NETMASK: specifies the subnet mask of the host IP address. If BOOTPROTO is
set to static, set NETMASK to the subnet mask of the management plane.
– VLANID: specifies the VLAN assigned to the host NIC used for PXE loading.If
the management plane VLAN is specified, add the VLANID="" field under the
row that contains NETMASK and set the VLAN ID.
– If the management plane VLAN is required, add the <vlanconfig-X> field. X indicates
the management plane VLAN.
The management plane uses VLAN 0 by default. If the management plane VLAN is
not required, do not add the field. The following content is an example:
<vlanconfig-X>
STARTMODE="auto"
ETHERDEVICE="eth0"
IPADDR=""
NETMASK=""
</vlanconfig-X>
– vlanconfig-X: specifies the management plane VLAN. For example, if the planned
management VLAN ID is 800, set it to vlanconfig-800.
– ETHERDEVICE: specifies the name of the NIC of the management plane. The
name must be the same as the NIC name set in <netconfig-0>.
– IPADDR: specifies the IP address of the NIC of the management plane. The value
must be the same as the IP address set in <netconfig-0>.
– NETMASK: specifies the subnet mask of the management plane. The value must
be the same as the subnet mask set in <netconfig-0>.
– Add the <routes> field to configure the default gateway. If you determine to make the
host NIC automatically obtains its IP address, that is, BOOTPROTO is set to dhcp,
do not add this field. The following content is an example:
<routes>
default X.X.X.X - -
</routes>
Enter the gateway address of the host management plane on the right of default, for
example, default 192.168.0.1 - -.
Configure the TFTP service.
5 Copy the following files to the shared directory of the TFTP service on the PXE server:
– linux: Decompress Step 1 and obtain it in the boot folder.

FusionCompute
– initrd: Obtain it in the boot folder.

– pxelinux.0: (Optional. If the PXE server has other PXE boot files, the software is not
required). Decompress FusionCompute V100R005C00SPC300_Tools.zip and obtain
it in the PlugIn folder.
6 To use the pxelinux.0 file in the FusionCompute V100R005C00SPC300_Tools.zip
package, set the boot file of the DHCP service on the PXE server to pxelinux.0.
7 Create a folder named pxelinux.cfg in the shared directory of the TFTP service.
8 In the newly created pxelinux.cfg folder, create N empty files (.txt files are recommended)
to configure PXE installation policies and name them according the PXE boot file types
(N indicates the number of hosts to be installed). The naming policies are as follows:
– If you determine to use the pxelinux.0 file obtained in Step 5, the file name format is
01-Host NIC MAC address.
Host NIC MAC address indicates the MAC address of the host NIC used for PXE
loading.
For example, if NIC MAC address of a host is 1A-2B-3C-4D-5E-6F, name the .txt file
01-1A-2B-3C-4D-5E-6F.
NOTICE
Delete the file name extension for the .txt files. If file name extensions are set to be
hidden on the PXE server OS, cancel the setting first and then change the file names.
– If you determine to use another PXE boot file other than pxelinux.0, name the .txt files
according to the naming rule defined for the PXE boot file.
9 Use a text editor to edit a host PXE configuration file created in Step 8.
NOTICE
The FTP username and password can contain only digits, letters, and following special
characters: ~!@#$%^*-_+.
DEFAULT linux
LABEL linux
KERNEL linux
APPEND initrd=initrd install_mode=install install_media=PXE
install_target=Storage medium install_disk=Disk drive letter root=/dev/ram0 rw
install_repo=ftp://FTP service IP address/?u=FTP service username&p=FTP
service password install_cfg=ftp://FTP service IP address/Host name/?u=FTP
service username&p=FTP service password net_cfg=eth0,,dhcp,,log_level=7
– Storage medium specifies the storage medium used for installing the host OS.
– If Storage medium is set to hdisk, the system will install the OS on the first hard
disk. If disks are grouped as RAID 1, the system will install the OS on its first member
disk.
– If Storage medium is set to udisk, the system will install the OS on the first USB
flash disk.

FusionCompute
– Disk drive letter specifies the disk used for installing the host OS, for example, /dev/
sda.
NOTE
If the space of a hard disk or RAID disk is greater than 2 TB, the system identifies it only as a 2
TB disk.
– Host name specifies the host name. The system obtains the corresponding configuration
file using the host name during the PXE installation process.
NOTE
l Storage medium and Disk drive letter substitutes. Set either of the two parameters.
l If both the parameters are set and the storage medium does not provides the drive letter, the
system displays an error message.
l The OS installation location of a host must be consistent with the first boot device set in the host
BIOS system. Otherwise, the host may fail to boot.
Example 1: If the local PC IP address is 192.168.4.8, the FTP service username and
password are install and Huawei@123, respectively, and you determine to install the host
OS on the default disk on the host, edit the configuration file content as follows:
DEFAULT linux
LABEL linux
KERNEL linux
APPEND initrd=initrd install_mode=install install_media=PXE
install_target=hdisk root=/dev/ram0 rw install_repo=ftp://192.168.4.8/?
u=install&p=Huawei@123 install_cfg=ftp://192.168.4.8/Host01
/?u=install&p=Huawei@123 net_cfg=eth0,,dhcp,,log_level=7
Example 2: If the local PC IP address is 192.168.4.8, the FTP service username and
password are install and Huawei@123, respectively, and you determine to install the host
OS on the /dev/sdb disk on the host, edit the configuration file content as follows:
DEFAULT linux
LABEL linux
KERNEL linux
APPEND initrd=initrd install_mode=install install_media=PXE install_disk=/dev/
sdb root=/dev/ram0 rw install_repo=ftp://192.168.4.8/?u=install&p=Huawei@123
install_cfg=ftp://192.168.4.8/Host01/?u=install&p=Huawei@123
net_cfg=eth0,,dhcp,,log_level=7
10 Edit the PXE configuration files for the other hosts one by one. For details, see Step 9.
Install host OSs.
11 Restart each host and set it to boot from the network.

The host OS installations begin.
NOTICE
After an OS is installed on a host, the host automatically restarts. In this case, change the
host boot device. Otherwise, the host will boot from the network and begin to install the
OS again.
----End

FusionCompute
Additional Information
Saving a Configuration File as a UNIX File
Use a text editor, such as Notepad++, to convert the original file as a UNIX file and save it.
You can also copy the edited configuration file to a Linux OS, and run commands to convert it
as a UNIX file.
l Converting the File Format Using a Text Editor

The following steps take Notepad++ as an example.
1. On the status bar at the lower part of the editing window, check whether the file is in
the UNIX format, as shown in Figure 3-22.
Figure 3-22 Status bar of a text editor
– If yes, save the file after the editing is complete.

2. On the menu bar, choose Edit > EOL Conversion > Convert to UNIX Format,
convert the file to a UNIX file, and save the file after the editing is complete.
l Converting the File Format Using the Linux OS
1. After the configuration file is edited, save it and copy it to a Linux OS.
2. Run the following command to convert the file to a UNIX file:
dos2unix File name
For example, if the file name is UVPOSsetup.conf, run the following command:
dos2unix UVPOSsetup.conf
----End
3.3 Installing VRM Nodes
3.3.1 Installing VRM Nodes on VMs (Recommended)
3.3.2 Installing VRM Nodes on Servers

FusionCompute
3.3.1 Installing VRM Nodes on VMs (Recommended)
Scenarios
Use the FusionCompute installation wizard to create Virtualization Resource Management
(VRM) VMs on specified hosts. A VRM node installed on a VM is easy to maintain and requires
less resources from a physical server.
During the installation, a management cluster is automatically created, which contains the host
for creating the VRM VM. A distributed virtual switch (DVS) and a port group on the
management plane are also automatically created.
If any exception occurs when you use the FusionCompute installation wizard, handle the fault
by following operations provided in Troubleshooting the FusionCompute Installation
Wizard.
Prerequisites
Conditions
– The host on which the VRM VM is to be created must meet the following requirements:
– You have obtained the management IP address, and the password of user root of the host.
– The password of user gandalf remains the default value.
– The local PC must meet the following requirements:
– Windows XP
– Windows 7
– You have disabled the Windows firewall on the local PC.
– The management network port on the host can be pinged from the PC.
– If advanced storage area network (SAN) devices are used for VRM VM creation, you have
created an administrator account for adding storage resources in addition to admin. For
details about how to create the management account, see How to Create a Management
Account for Advanced SAN Devices.
Data
Category Parameter Description Example Value
Data store Name Specifies the name of the data DataStore01

information store to be added to the host.

FusionCompute
Storage device Specifies the type of the N/A

type storage device used for VRM
VM disks.
Value:
l Local disk: This
configuration for local
disks is simple but the
reliability and
performance are lower
than that of shared storage
devices.
l Shared storage device
(SAN and advanced SAN):
The reliability and storage
performance of shared
storage devices are higher
than that of local disks but
the configuration for share
storage devices is
complex. However, shared
storage devices are
dependent on networks.
You are advised to set the
VRM VM to exclusively use a
data store created from an
independent LUN on a SAN
device (recommended) or
created from a local disk. The
required RAID configuration
for the data store used by a
VRM VM varies depending
on the number of hosts or VMs
in the system. However, the
actual number of hosts and
VMs may vary from the
following typical
configurations. You need to
configure RAID to match the
higher configuration. For
example, if you have 100 hosts
and 200 VMs in your system,
select the recommended
RAID configuration for 100
hosts or 3000 VMs. If you
have 100 hosts and 5000 VMs,
select the recommended
RAID configuration for 256
hosts or 5000 VMs.

FusionCompute
l 20 hosts or 200 VMs:

RAID 1 consisting of two
hard disks
RAID 5 consisting of four
data disks and one hot
spare disk
RAID 5 consisting of nine
spare disk
RAID 5 consisting of nine
spare disk
RAID 10 consisting of ten
hard disks
All the abovementioned disks
must be 15000-RPM Serial
Attached SCSI (SAS) disks.

FusionCompute
Enable It takes time to create a N/A

virtualization common disk on a virtualized
data store. However, a thin
provisioning disk can be
quickly created on a
virtualized data store, taking
the same time as a common
disk on a non-virtualized data
store takes. In addition, a thin
provisioning disk supports
advanced features that
improve storage utilization
and system security and
reliability, such as thin
provisioning, snapshots, and
live storage migration. A
common disk created on a
non-virtualized data store has
higher I/O performance than
disks created on virtualized
data stores but it does not
support the advanced features.
This parameter is deselected
by default.
This parameter is mandatory
only when local disks are used.
VRM VM Management Specifies the IP address of the 192.168.4.41

information IP address VRM VM.
Ensure that the IP address
belongs to the management
plane network segment. You
are advised to select the
management IP address from
a private network segment,
because a management IP
address from a public network
segment may pose security
risks.

FusionCompute
VM Specifies the method used to Customized

specifications configure VRM VM configuration
configuration specifications.
method Value:
l By deployment scale
l Customized configuration
CPU, Memory Specify the number of CPUs 8 vCPUs, 8 GB

(GB) and the memory size of a VRM
VM.
To configure CPU and
memory specifications by the
VM deployment scale, use the
following specifications:
l 200 VMs, 20 physical
machines (PMs): 2 CPUs,
3 GB memory
NOTE
If the VRM VM has two
CPUs and 3 GB memory, the
health check tool may
become unavailable.
l 1000 VMs, 50 PMs: 4
CPUs, 5 GB memory
l 3000 VMs, 100 PMs: 8
CPUs, 8 GB memory
l 5000 VMs, 200 PMs: 12
CPUs, 16 GB memory
l 30000 VMs, 1280 PMs: 20
CPUs, 30 GB memory
To customize CPU and
memory specifications, refer
to the preceding
specifications.
Host storage Name This parameter is mandatory storagePort01

port when shared storage resources
are used.

FusionCompute

NOTE Port Specifies the port on the host, PORT2
You are advised which connects to the storage
to plan for host
storage ports in
plane. Set it to the planned
advance to port.
facilitate IP This parameter is mandatory
address
when shared storage resources
assignment and
management.
are used.
If SAN devices IP address This parameter is mandatory 172.20.50.51
are used and
multipathing is
required,
are used.
configure IP address: Set it to an idle IP
multiple storage address that communicates
interfaces for a
with the storage plane. For
single storage
network port. example, if the storage IP
address of the storage device is
172.20.100.100 and subnet
mask is 255.255.0.0, set the IP
address to 172.20.XXX.XXX.
VLAN Specifies the VLAN that is VLAN 4

used for the storage port IP
address.
are used.
Shared storage Device type Specifies the type of the SAN

information shared storage device.
are used.
Value:
l SAN
l Advanced SAN

FusionCompute
Device vendor Specifies the vendor who Huawei

provides the devices.
Value:
l Huawei
l Non-Huawei
when the device type is SAN.
If it is set to Huawei, the
system uses Huawei
multipathing mode. If it is set
to Non-Huawei, the system
uses universal multipathing
mode.
Management Specifies the management IP 192.168.60.4/5988

IP address and address and port number of the
port number storage device.
Default port number: 5988
If Device type is SAN and
multiple controllers are
deployed, enter the
management IP address of one
controller.
If Device type is Advanced
SAN, enter the two
management IP addresses of
the storage device.

FusionCompute
Storage IP Specifies the storage IP 172.20.100.100/3260

address and address and port number of the
port number storage device.
Default port number: 3260
If Device type is SAN and the
storage devices use multiple
storage links managed by
multiple controllers, configure
all the storage IP addresses.
For example, if the system
uses OceanStor S5500T
devices, you must enter all the
eight storage IP addresses
managed by controllers A and
B. The configured storage IP
addresses cannot be changed.
when Device type is set to
SAN.
VLAN The VLAN ID of the storage VLAN 4

plane.
Active/standby Floating IP Specifies the floating IP 192.168.60.30

VRM node address address of the active and
information standby VRM nodes.
when the site has two VRM
nodes working in active/
standby mode.
Management This parameter is optional. 2

plane VLAN Specifies the VLAN of the
management plane. If you do
not specify the value, the
system uses VLAN 0 by
default.

FusionCompute
Arbitration IP Specifies the IP address used 192.168.60.1

address to determine the status of the
active and standby VRM
nodes.
when the site has two VRM
nodes working in active/
standby mode.
A maximum of three
arbitration IP addresses can be
specified.
The active and standby VRM
nodes periodically send a
ping command to all
arbitration IP addresses. An
active/standby switchover is
triggered if the active VRM
node cannot be pinged from
any arbitration IP address and
the standby VRM node can be
pinged from at least one
arbitration IP address.
You are advised to set the first
arbitration IP address to the
gateway address of the
management plane, and set
other arbitration IP addresses
to IP addresses of servers that
communicate with the
management plane, such as the
active directory (AD) server or
the domain name server
(DNS).

FusionCompute
VLAN Specifies the VLAN used by VLAN 0

the management plane.
Default value: 0
only when the management
plane VLAN is specified.
NOTE
If you determine to specify a
management plane VLAN, set
the type of the VLAN to tagged
on the connected access switch
port to enable communication
between the management plane
and the switch.
management plane VLAN, set
the type of a configured VLAN
on the connected access switch
port to untagged to enable the
management plane to
communicate with the
aggregation switch through this
VLAN.
Software
You have obtained the following files:
– FusionCompute V100R005C00SPC300_VRM.zip
– FusionCompute V100R005C00SPC300_Tools.zip
Procedure
Decompress software packages.
1 Decompress FusionCompute V100R005C00SPC300_Tools.zip on the PC.

The HostInstaller, Installer, PlugIn, and ToDPS folders are generated.
2 Decompress FusionCompute V100R005C00SPC300_VRM.zip on the PC.
The generated folder contains FusionCompute_V100R005C00SPC300_VRM.ovf and
FusionCompute_V100R005C00SPC300_VRM-1.vhd.
NOTE
Do not change the names of the preceding files. Otherwise, the system cannot identify the files during
the installation.
Run the FusionCompute installation wizard.

FusionCompute
NOTICE
Do not change the PC IP address when the installation wizard is running. If the IP address is
automatically or maliciously changed, the installation will fail. To resolve this issue, see How
to Handle FusionCompute Installation Failures Caused by a Change in the Local IP
Address.
3 Run FusionComputeInstaller.exe in the Installer folder.

The Select Language dialog box is displayed.
NOTE
If a message is displayed indicating that .net Framework is not installed, run
dotNetFx40_Full_x86_x64.exe in the PlugIn folder to install the plug-in. After the plug-in is
installed, restart the local PC.
4 Select a language and click OK.
The FusionCompute Installation Wizard page is displayed.
If a dialog box is displayed indicating that port 5432 is in use, address this issue by following
steps provided in How to Troubleshoot the Occupied Port on the FusionCompute
Installation Wizard.
If a message is displayed indicating that JRE is not installed, run the JRE file in the
PlugIn folder to install the plug-in. After the plug-in is installed, run the FusionCompute
installation wizard again.
5 Determine the VRM deployment mode, as shown in Figure 3-23.
NOTE
After VRM installation is complete, you can connect an external Oracle database to the VRM system.
If only one VRM node is deployed in standalone mode and has an external Oracle database connected,
you cannot add another VRM node and deploy the two nodes in active/standby mode. Therefore, the
active/standby deployment mode is recommended.

FusionCompute
Figure 3-23 Select installation mode
6 Click Next.
The Install Components page is displayed, and the system automatically installs the
required components.
7 After the components are installed, click Next.
The Configure Host window is displayed, as shown in Figure 3-24.

FusionCompute
Figure 3-24 Configure Host
Configure the host.

8 Enter the host management IP address and the password of user root.
9 Click Configure Host.
The host configuration starts.

10 After the host configuration is complete, click Next.
The Select Storage Device Type window is displayed.
Configure storage resources.
11 Determine the storage device type based on site requirements.
You are advised to set the VRM VM to exclusively use a data store created from an
independent LUN on a SAN device (recommended) or created from a local disk. The
required RAID configuration for the data store used by a VRM VM varies depending on
the number of hosts or VMs in the system. However, the actual number of hosts and VMs
may vary from the following typical configurations. You need to configure RAID to match
the higher configuration. For example, if you have 100 hosts and 200 VMs in your system,
select the recommended RAID configuration for 100 hosts or 3000 VMs. If you have 100
hosts and 5000 VMs, select the recommended RAID configuration for 256 hosts or 5000
VMs.
– 20 hosts or 200 VMs: RAID 1 consisting of two hard disks

FusionCompute
– 50 hosts or 1000 VMs: RAID 5 consisting of four data disks and one hot spare disk
– 100 hosts or 3000 VMs: RAID 5 consisting of nine data disks and one hot spare disk
– 1280 hosts or 30000 VMs: RAID 10 consisting of ten hard disks
All the abovementioned disks must be 15000-RPM Serial Attached SCSI (SAS) disks.
– Local disk: This configuration for local disks is simple but the reliability and
performance are lower than that of shared storage devices. However, the active and
standby VRM nodes are deployed on different local disks to enhance VRM reliability.
To use local disks on the host, go to Step 35
– Shared storage device (SAN and advanced SAN): The reliability and storage
performance of shared storage devices are higher than that of local disks but the
configuration is complex. However, shared storage devices are dependent on networks.
– To use fiber channel storage area network (FC SAN) devices, go to Step 30.
– To use IP SAN or Advanced SAN devices, go to Step 12.
NOTE
Configuration of the OceanStor 18000 series storage device or OceanStor VIS6600T storage device
varies depending on the cables used. If the storage devices use network cables, follow the IP SAN
device configuration method. If the storage devices use optical cables, follow the FC SAN device
configuration method.
12 Select Shared storage device, and click Next.
The Configure Storage Interface window is displayed, as shown in Figure 3-25.

FusionCompute
Figure 3-25 Configuring host storage port
13 (Optional) If networking binding is required, click SetBinding to configure.
modes.
addresses.

FusionCompute
the LACP protocol.
networks.

FusionCompute
addresses.
14 Click Create.
A dialog box is displayed, as shown in Figure 3-26.
Figure 3-26 System interface configuration
15 Set the host storage port name, select the network port, and set IP address, Mask, and
VLAN for the storage interface on the host.
– IP address: Specifies the IP address used for communication between the host and the
storage device.
– If the storage plane uses a layer 2 network, set it to an idle IP address that communicates
with the storage plane. For example, if the storage IP address of the storage device is
172.20.100.100 and subnet mask is 255.255.0.0, set the IP address to
172.20.XXX.XXX.
– If the storage plane uses a layer 3 network, set it to an IP address that communicates
with the storage IP address of the storage device.
– Mask: Specifies the subnet mask for the storage ports.
– VLAN: Specifies the virtual local area network (VLAN) of the storage plane.
– Routing Configuration: Specifies the route information for layer 3 network
communication.

FusionCompute
NOTE
If the host storage plane uses intelligent NICs (iNICs), the layer 3 routed network cannot be
configured.
– Network destination: Specifies the first IP address of the network segment that the
target storage device uses, for example, 192.168.0.0.
– NetMask: Specifies the subnet mask of the subnet network segment.
– Gateway: Specifies the gateway of the storage ports. The gateway address and the
storage IP address must belong to the same network segment.
If SAN devices are used and multipathing is required, configure multiple storage interfaces
for a single storage network port.
For example, if a storage device has four storage paths, using VLAN4, VLAN5, VLAN6,
and VLAN7, respectively, the network port eth2 on the host is to be configured to
intercommunicate with VLAN4 and VLAN5, and eth3 to intercommunicate with VLAN6
and VLAN7, configure storage interfaces VLAN4 and VLAN5 on eth2, and VLAN6 and
VLAN7 on eth3.
NOTE
The parameters of all the storage ports (except the host management port Mgnt-0) can be modified
after they are set.
16 Click OK.
17 Check whether all the planned storage ports have been added.
– If no, perform Step 14 to Step 16.
18 Click Next.
The Configure Storage Resources window is displayed, as shown in Figure 3-27.

FusionCompute
Figure 3-27 Configure Storage Resources
19 Click Add.
20 Select the storage resource (indicating a physical storage device)type.
– SAN: common IP SAN device like S5600 or S5500T of V100 version.
– Advanced SAN: eXtreme Virtualization Engine (XVE) storage devices like S5500T
of V2 version.
In a system that uses advanced SAN devices, if advanced features (for example,
snapshots and linked clones) are not required, you can follow the common IP SAN
device configuration method.
21 Set the parameters of the storage resource (indicating a physical storage device).
– Set the following parameters for a SAN device:
– Vendor
– Name
– Management IP address and Port number: identify the added storage device.
Enter the management IP address of one controller.
– Storage IP address and Port number: If multipathing is used, enter all storage IP
addresses and port numbers of the storage device controller at a time. For example,
in a system that uses OceanStor S5500T, if multipathing is used, you must enter

FusionCompute
eight storage IP addresses and port numbers of the OceanStor S5500T controllers A
and B. The storage IP address in-use cannot be changed.
NOTE
Each logical unit number (LUN) of an HP P4300G2 SAN device uses an iSCSI link to connect
to the host. However, all these links are presented as one IP address. Therefore, this IP address
can be used as the management IP address and the storage IP address.
If HP P4300G2 SAN devices are to be added, set Management IP address and Storage IP
address to the same IP address. Do not add other storage IP addresses.
– Set the following parameters for an Advanced SAN device:
– Name
– Management IP address and Port number: identify the added storage device and
can be used to access the storage device. Enter one or more storage IP addresses and
port numbers of the storage device controller.
– Username: specifies the username of the storage device administrator account. Do
not set it to admin.
– Password: specifies the password of the storage device administrator account.
22 Click OK.
The added storage resources are displayed.
23 Check whether to change the host multipathing mode based on the type of storage resources
to be added.
SAN devices require the multipathing function. In the FusionCompute, the default
– If Huawei SAN devices or advanced SAN devices are to be added, go to Step 24.
– If other SAN devices are to be added, go to Step 25.
25 Select the added storage resources and click Associate.
An information dialog box is displayed after the devices are associated.
26 Click OK.
27 Check whether the storage type is IP SAN.
28 Make a note of the world wide name (WWN) of the host in the upper corner of the page,
and log in to the storage device management software to configure the storage device
initiator.
For details, see How to Configure an IP SAN Initiator.
NOTE
If the storage device management software does not support the JRE version running on the PC, do
not replace the JRE on the PC. Otherwise, the installation fails. To resolve this issue, prepare another
PC that is in the same network segment as the current PC and install the JRE version supported by
the storage device management software. Then, use this PC to configure the storage device initiator.

FusionCompute
29 After the storage device initiator configuration is complete, click Next on the installation
wizard page.
The Configure Data Store page is displayed.
Go to Step 36.
30 Select Local disk/FC SAN, and click Next.
After Local disk/FC SAN is selected, the system automatically adds the remaining space
on the OS-installed hard disk, or the first local storage device on the page (if the host OS
is installed on an internal USB flash disk) as a data store to the host.
31 Determine whether to use Huawei FC SAN devices.
FC SAN devices require the multipathing function. In the FusionCompute, the default
– If Huawei SAN devices are to be added, go to Step 24.
– If other FC SAN devices are to be added, go to Step 33.
33 Click Obtain FC Initiator.
The WWN value of the FC SAN initiator connected to the host is displayed.
Go to Step 36.
35 Select Local disk/FC SAN, and click Next.
NOTE
After Local disk/FC SAN is selected, the system automatically adds the remaining space on the OS-
installed hard disk, or the first local storage device on the page (if the host OS is installed on an
internal USB flash disk) as a data store to the host. If no additional data stores are required, go to
Step 42.
The remaining space on the local disk where the host OS is installed can be added as a data store of
the local storage type. If the space of the disk is greater than 2 TB, the system identifies the disk only
as a 2 TB disk during the host OS installation process. Therefore, the remaining space on this disk
after the OS installation is less than 2 TB. Other local disks on the host are not affected by the OS
installation. Therefore, they can provide all of their space.
36 In the Storage Device area, click Refresh Storage Device.

FusionCompute
NOTE
If no available storage device is displayed after the scan if a SAN device has been associated with
the host or the host uses local disks or FC SAN resources, follow the operations provided in Storage
Devices Cannot Be Detected on the FusionCompute to address this issue. if abnormal storage
devices or no storage devices are detected, follow operations described in A Host Detects Non-
Existent Storage Devices or Storage Devices with an Incorrect Name on the FusionCompute Portal
to address this issue.
37
NOTICE
l Multiple sites cannot share the same data stores. Otherwise, data on the data stores may
be overwritten.
l If the VRM VM uses a non-virtualized local disk, ensure that the local disk has no
residual data. For details, see Storage Devices Cannot Be Detected on the
FusionCompute.
In the Data Store area, click Add.
The Add Data Store dialog box is displayed.
You are advised to add a data store to the host to provide storage resources to VRM VMs.
You can add other data stores for user VMs after the FusionCompute is installed.
38 Select the data store in the list, set its name, determine whether to virtualize the data store
based on user requirements, and click OK to add the data store to the host.
It takes time to create a common disk on a virtualized data store. However, a thin
provisioning disk can be quickly created on a virtualized data store, taking the same time
as a common disk on a non-virtualized data store takes. In addition, a thin provisioning
disk supports advanced features that improve storage utilization and system security and
reliability, such as thin provisioning, snapshots, and live storage migration. A common disk
created on a non-virtualized data store has higher I/O performance than disks created on
virtualized data stores but it does not support the advanced features.
A VRM node cannot be deployed on a VM that uses a LUN Pome data store.
39 Check whether to add other data stores.
40 Repeat Step 37 to Step 38 for each data store to be added.
41 In the Data Store area, select the data store for the VRM VM disks.
42 Click Next.
The Configure VRM VM window is displayed, as shown in Figure 3-28.

FusionCompute
Figure 3-28 Configure VRM VM
Configure a VRM VM.

43 Click Browse on the right of Template file and select the
FusionCompute_V100R005C00SPC300_VRM.ovf file in the displayed dialog box.
44 In the Configure Network area, set the management IP address of the VRM VM.
NOTE
You are advised to select the management IP address from a private network segment, because a
management IP address from a public network segment may pose security risks.
45 To specify the management plane VLAN for the VRM VM, select Config Management
VLAN in the VLAN area and set VLAN ID.
If you do not specify the management plane VLAN, the system uses VLAN 0 by default.
46 Set the VRM VM specifications.
You can select the system-defined specifications or customize the VM specifications. The
system-defined mappings between the system capacity and VRM VM specifications are as
follows:
NOTE

FusionCompute

VRM VM specifications can be modified later.
47 Click Verify Configuration.
The parameters are correct if the system displays "Configuration information verified."
If "Failed to connect to the shared directory or the template file does not exist. Check that
the entered template file path is correct" is displayed and the entered template file path is
correct, contact technical support.
– If Install a single VRM node is selected, go to Step 55.
– If Install active and standby VRM nodes is selected, go to Step 49.
Configure the standby VRM node.
49 Click Next and configure the standby VRM node.
Configure the active/standby parameters.
50 Click Next.
The Configure Active/Standby Parameters window is displayed, as shown in Figure
3-29.
Figure 3-29 Configure Active/Standby Parameters
51 Set the following parameters:

FusionCompute
– Active Node Name

– Standby Node Name: Set it to a name different from the active node name.
– Floating IP Address: Enter the floating IP address of the active and standby VRM
nodes.
– Mask
– Arbitration IP01: Set it to the gateway IP address of management plane.
– Arbitration IP02 and Arbitration IP03: Set them to the IP addresses of servers that
can communicate with the management plane, such as the IP address of the active
directory (AD) domain server, domain name server (DNS) server.
NOTE
If any of the arbitration IP addresses of the devices is to be changed, you are advised to change the
VRM arbitration IP addresses to the new address before the device is changed. If any of the IP
addresses of the servers providing the arbitration IP addresses is about to be changed to another
planned IP address, change the values of corresponding arbitration IP address on the FusionCompute
first based on the data plan.
52 Click Verify Configuration.
The parameters are correct if the system displays "Active/standby configuration
verification succeeded."
Configure the rights management mode.
53 Click Next.
The rights management mode configuration window is displayed.
– Common mode: This mode implements high usability. One account can be granted all
operation rights in the system.
– Rights separation mode: This mode implements high security. One account can be
granted rights of only the administrator sysadmin, secadmin, or secauditor, so that
administrator rights are isolated from each other and mutually supervised.
– System administrator (sysadmin): has rights to operate and maintain system services
and create and delete user accounts. The created user accounts are locked and do not
belong to any role.
– Security administrator (secadmin): has rights to manage rights of user accounts and
roles but has no rights to create user accounts. A user account created by the system
administrator can be used only after the security administrator assigns a role to it
and unlocks it.
– Security auditor (secauditor): has rights to view and export logs and audit other
administrators' operations.
Rights separation mode is recommended when users have high requirements on
security.

FusionCompute
NOTE
l Before selecting Rights separation mode for the FusionCompute, ensure that components that
interconnect to the FusionCompute (such as the FusionManager and the FusionAccess) support
this mode.
l After the FusionCompute installation is complete, the rights management mode cannot be
changed.
Create a VRM VM.

55 Click Next.
The system starts to create the VRM VM.
NOTE
During the creation process, if the VRM VM fails to create due to a system fault, do not close the
installation wizard.
After the fault is rectified, click Previous to return to the previous page, and click Next to create the
VM again.
If the creation fails again, contact technical support.
The Finish window is displayed after the VM is created. You can log in to the
FusionCompute as prompted.
The passwords of default users for logging in to the FusionCompute are:

– If the rights management mode is set to the common mode, the default user is admin
and its initial password is Huawei@CLOUD8!.
– If the rights management mode is set to the high security mode,
– The default system administrator is sysadmin and its initial password is
Sysadmin#.
– The default security administrator is secadmin and its initial password is
Secadmin#.
– The default security auditor is secauditor and its initial password is Secauditor#.
Initial passwords must be changed upon first login.
database.
FusionCompute data services run in the embedded database by default. You can also set
the data services to run on an independent Oracle 11gR2 database server or cluster.

NOTE
The Oracle DB Configuration dialog box is displayed.

FusionCompute
The Oracle database configuration start and takes about 5 minutes.
60 Close the Oracle DB Configuration dialog box after the database is configured.
61 Click Finish.
Close the FusionCompute installation wizard.
The default password for user root to log in to the VRM VM is Huawei@CLOUD8!. The
default password for user gandalf to log in to the VRM VM is Huawei@CLOUD8.
Change the password as soon as possible to ensure system security.
----End
3.3.2 Installing VRM Nodes on Servers
Scenarios
Install the Virtualization Resource Management (VRM) node on a physical server and mount
an image to it to install the operating system (OS) on it. If active and standby VRM nodes are
to be deployed, configure them in active/standby mode.
Prerequisites
Conditions
– The first boot device is set to Hard disk, the second boot device is set to Network, and the
third boot device is set to CD/DVD-ROM for the server.
– You have obtained the IP address, username, and password for logging in to the baseboard
management controller (BMC) of the physical servers.
– You have obtained the basic input/output system (BIOS) password of the physical server if
the password has been configured.
– A tool that can be used for remote access on various platforms, such as PuTTY, is available.
– You have disabled the Windows firewall on the local PC.
– You have configured RAID for the physical servers. The required RAID configuration for
the data store used by a VRM VM varies depending on the number of hosts or VMs in the
system. However, the actual number of hosts and VMs may vary from the following typical
configurations. You need to configure RAID to match the higher configuration. For example,
if you have 100 hosts and 200 VMs in your system, select the recommended RAID
configuration for 100 hosts or 3000 VMs. If you have 100 hosts and 5000 VMs, select the
recommended RAID configuration for 256 hosts or 5000 VMs.
– 20 hosts or 200 VMs: RAID 1 consisting of two hard disks
– 50 hosts or 1000 VMs: RAID 5 consisting of four data disks and one hot spare disk

FusionCompute
– 1280 hosts or 30000 VMs: RAID 10 consisting of ten hard disks
All the abovementioned disks must be 15000-RPM Serial Attached SCSI (SAS) disks.
Data

r
VRM VRM Identifies a VRM node in the system. VRM01

informatio name the VRM node name can contain only
n digits, letters, and hyphen (-). It must
start with a letter and cannot exceed 32
characters.
Managem Specifies the management IP address of 192.168.4.31

ent IP the VRM node.
address If two VRM nodes are deployed, their
management port numbers must be the
same. You are advised to configure eth0
or bond0 as the management ports of the
two VRM nodes.
Subnet Specifies the subnet mask of the VRM 255.255.255.0

managem
ent plane
Gateway Specifies the gateway address of the 192.168.4.1

address of VRM management plane.
managem
ent plane
Managem Specifies the VLAN of the management 2

ent plane plane. If you do not specify the value, the
VLAN system uses VLAN 0 by default.

FusionCompute

r
Active/ Floating Specifies the floating IP address of the 192.168.60.10

standby IP address active and standby VRM nodes. It must
VRM be an idle IP address in the management
node IP address segment planned for the
informatio VRM node.
n This parameter is mandatory when the
Arbitratio Specifies the IP address used to 192.168.4.1

n IP determine the status of the active and
address standby VRM nodes.
A maximum of three arbitration IP
addresses can be specified.
The active and standby VRM nodes
periodically send a ping command to all
arbitration IP addresses. An active/
standby switchover is triggered if the
active VRM cannot be pinged from any
arbitration IP address and the standby
VRM can be pinged from at least one
arbitration IP address.
You are advised to set the first
arbitration IP address to the gateway
address of the management plane, and
set other arbitration IP addresses to IP
addresses of servers that communicate
with the management plane, such as the
active directory (AD) server or the
domain name server (DNS).
This parameter is mandatory when the
Software
You have obtained the FusionCompute V100R005C00SPC300_VRM.iso file.
Workflow
Figure 3-30 shows the process for installing the VRM nodes on servers.

FusionCompute
Figure 3-30 Process for installing the VRM nodes on servers
Start
Install the VRM.
Are active and standby No

VRMs required?
Yes
Install the second VRM.
Configure the active and standby

VRMs.
End
Procedure
Switch to the host installation window.
NOTE
l If two VRM nodes are required, install the active VRM first and then the standby VRM.
l The following example describes how to deploy VRM nodes on Tecal RH2285 servers by mounting
an image file to the host using the BMC remote control function. The VRM nodes use eth0 as the
management network interface card (NIC).
1 Open Internet Explorer on the PC, enter http://BMC IP address of the server and press
Enter.
2 Log in to the BMC on the server as prompted.
The iMana Web page is displayed.
NOTE
4 Click on the toolbar.

FusionCompute
5 Select Image File in the image dialog box and click Browse.
6 Select the image FusionCompute V100R005C00SPC300_VRM.iso and click Open.
7 Click Connect in the image dialog box.
When Connect changes to Disconnect, the image is mounted to the host.
8 On the toolbar, click , choose Cold Reset, and click Yes in the displayed dialog box.
The server begins to restart.
9 During the restart, press F11 repeatedly until the boot device selection screen is displayed.
Then set the boot device to CD/DVD-ROM or DVD-ROM, as shown in Figure 3-31.
Figure 3-31 Select Boot Device
The installation page is displayed.

NOTE
You are prompted to enter the basic input/output system (BIOS) password during the restart of certain
hosts. The default BIOS password of the Huawei RH series rack server, X series high-density server, the
E6000 blade server, and Huawei Tecal E9000 is Huawei12#$ or uniBIOS123.
10 Select Install within 30 seconds after the page is displayed, and press Enter.
NOTE
If you do not select Install within 30 seconds after the installation page is displayed, the server starts
from the local disk by default. If this occurs, restart the server, select the CD/DVD-ROM as the boot
device, and select Install.
The system automatically loads the ISO image file, which takes about 3 minutes. When the
loading is complete, the host configuration screen is displayed, as shown in Figure 3-32.
Figures in this section include sample parameter values, which may vary from the actual
parameter values on the site.

FusionCompute
Figure 3-32 Main Installation Window
Configure network information for the VRM node.

NOTE
When configuring host data:
l Press Enter to expand or execute the highlighted item.
l Press the space bar to toggle between options.
11 Select Network and the management port (for example, eth0).

The eth0 configuration screen is displayed.
NOTE
the management NIC.
12 Determine whether to specify a VLAN for the management plane.
The management plane VLAN must be designed in advance, and the management plane
used by the active and standby management nodes must use the same management plane
VLAN. The management VLAN used by hosts can be different than that used by the
management nodes, but the VLANs must be connected.
NOTE
13 Place the cursor between the brackets preceding Manual address configuration, and press
the space bar to select it.
14 Configure the IP address and subnet mask for eth0, as shown in Figure 3-33.

FusionCompute

NOTE
enter numbers.

Go to Step 19 after this step.
16 Place the cursor between the brackets preceding Manual address configuration with
VLAN, and press the space bar to select it.
17 Configure the IP address, subnet mask, and VLAN for eth0, as shown in Figure 3-34.
– VLAN: Enter the planned management plane VLAN.
NOTE
enter numbers.

FusionCompute

in Default Gateway, as shown in Figure 3-35.
Figure 3-35 Network Configuration

Configure host name for the VRM node.
21 On the host name configuration screen, select Hostname, delete the original information,
and enter the host name, as shown in Figure 3-36.

FusionCompute
Figure 3-36 Host name configuration for the VRM node
22 Select OK.
Configure the time zone.
23 Select Timezone to enter the Time Zone Selection screen, as shown in Figure 3-37.
Figure 3-37 Time Zone Selection
24 Select the time zone for the current site.

25 In Date/Time, enter the current time in the format YYYY-MM-DD/HH:MM:SS.
26 Select OK to finish the time zone configuration.
Configure the password for user root.
27 On the Root Password Configuration screen, select Password and enter the password
and confirm password of user root, as shown in Figure 3-38.

FusionCompute
Figure 3-38 Root Password Configuration
NOTE
The password must meet the following requirements:
l Contain 8 to 32 characters.
l Contain the following four types of characters:
l Lowercase letters
l Uppercase letters
l Digits
l Spaces or special characters `~!@#$%^&*()-_=+\|[{}];:'",<.>/?
28 Select OK to finish the password configuration.
Install the VRM node.
29 Select OK.
A dialog box is displayed asking you whether to install the OS on the default disk partition.
30 Select Yes.
– If a dialog box is displayed, informing you that the current disk partitions do not meet
VRM requirements and the new partitioning will delete original disk data, go to Step
31.
This dialog box will be displayed if the system disk has not been partitioned or the
partitions do not meet VRM requirements.
– If a dialog box is displayed, asking you whether all configurations are complete, go to
Step 36.
This dialog box will be displayed if the system disk had the VRM node or a similar OS
installed before.
31 Select Yes.
A dialog box is displayed, asking you whether all configurations are complete.
32 Select Yes.
The system starts to install the VRM node.
The installation process takes about 10 minutes. After the installation, the server restarts
automatically. When the login information is displayed, the VRM installation is complete.

FusionCompute
If no operation is performed on the interface for a long period of time, a black screen is
displayed. Press ctrl to switch to the installation page.
If the mounted CD/DVD-ROM driver is lost during installation due to a network failure,
reinstall the VRM node.
The default password for user gandalf to log in to the VRM VM is Huawei@CLOUD8.
Configure the VRM node specifications.
Configure the maximum memory resources for each services in the VRM node based on the
VRM memory size.
33 If the VRM node is successfully installed and automatically restarts, use the remote control
window to log in to the node as user root.
34 Run the following command to switch to the /opt/galax/vrm/tomcat/script directory:
cd /opt/galax/vrm/tomcat/script/
35 Run the following command to run the configuration script:
sh modifyVrmNodeMemory.sh Memory size
Memory size can be set to S, M, L, or XL based on the VRM memory size.
– S: 3 GB ≤ VRM memory size < 5 GB
– M: 5 GB ≤ VRM memory size < 8 GB
– L: 8 GB ≤ VRM memory size < 16 GB
– XL: VRM memory size ≥ 16 GB
For example, run sh modifyVrmNodeMemory.sh XL
The command is successfully executed if the following information is displayed:

modify vrm java heap success
modify OM java heap success
modify Portal java heap success
36 Run the following command to restart the VRM node:

reboot
Configure management NIC binding for the VRM node.
To improve VRM reliability, this operation is required when two NICs are deployed on the VRM
management plane.
37 Determine whether to bind NICs on the VRM management plane.
38 Bind NICs on the VRM management plane.
Configure the rights management mode.
NOTE
If the VRM nodes work in active/standby mode, configure the rights management mode only on the active
VRM. The standby VRM will automatically synchronize data from the active one.

FusionCompute
There are two rights management modes:

– Common mode: The default admin account has all operation rights in the system. This
mode applies to the FusionSphere solution and the FusionCube solution.
– Rights separation mode: Administrators are categorized into system administrators,
security administrators, and security auditors. Administrators of different types have
different operation rights. No account in the system has all operation rights. This mode
applies to the FusionAccess solution or the systems that have only the
FusionCompute deployed.
– To select the common mode, go to Step 43.

– To select the secure mode, go to Step 40.
40 In the remote control window, log in to the VRM node as user gandalf.
The default password of user gandalf is Huawei@CLOUD8.
41 Run the following command and enter the password of user root to switch to user root:
su - root
42 Run the following command to set the secure mode for the VRM node:
sh /opt/galax/vrm/tomcat/script/omsconfig/bin/createSecuritySMTbl.sh -r
The command is executed successfully if the following information is displayed:

create sm's security tables success.
Install the second VRM.
After VRM installation is complete, you can connect an external Oracle database to the VRM
system.
If only one VRM node is deployed in standalone mode and has an external Oracle database
connected, you cannot add another VRM node and deploy the two nodes in active/standby mode.
Therefore, the active/standby deployment mode is recommended.
43 Determine whether to deploy two VRM nodes on one site.

44 Repeat Step 1 to Step 38 to install the second VRM on another physical server.
Configure the active/standby VRM nodes.
NOTICE
Before this configuration, ensure that both VRM nodes are powered on. During the
configuration, do not power them off. Otherwise, the system will break down.
45 Log in to the FusionCompute using the management IP address of the active VRM.
For details, see Logging In to FusionCompute.
46 On the FusionCompute, choose System > System Configuration > Services and Mgt.
Nodes.
The Services & Mgt. Nodes page is displayed.

FusionCompute
47 Locate the row that contains VRM service in Service list, click Configure Deployment
Mode.
48 Set the following parameters:
– Floating IP address: Enter the floating IP address of the active and standby VRM
nodes.
– Subnet mask: Enter the subnet mask of the management plane.
49 Enter the management IP address of the standby VRM in Peer IP address, and click Obtain
Host Name.
If "The node name already exists. Please change the name of the peer node" is displayed,
enter a new host name for the standby VRM in Host name of peer node.
50 Set Arbitration IP address.
Arbitration IP address: You can enter up to three arbitration IP addresses. Set the first
arbitration IP address to the gateway address of the management plane and set other
arbitration IP addresses to IP addresses of servers that communicate with the management
plane, such as the AD or DNS server.
NOTE
If any of the arbitration IP addresses of the devices is to be changed, you are advised to change the
VRM arbitration IP addresses to the new address before the device is changed. If any of the IP
addresses of the servers providing the arbitration IP addresses is about to be changed to another
planned IP address, change the values of corresponding arbitration IP address on the FusionCompute
first based on the data plan.
51 Click Modify.
52 Click OK.
The VRM active/standby mode configuration starts, which takes about 5 minutes. The
FusionCompute is not available during the configuration process.
Configure an Oracle database to interwork with FusionCompute.
FusionCompute data services run in the embedded database by default. You can also set the data
services to run on an independent Oracle 11gR2 database server or cluster.

database.
NOTE
54 Use PuTTY to log in to the VRM VM.
Ensure that the management IP address and username gandalf are used to establish the
connection.

FusionCompute
su - root
56 Run the following command to disable logout on timeout:
TMOUT=0
57 Run the following command to switch to the /opt/galax/vrm/tomcat/script/db_shift
directory:
cd /opt/galax/vrm/tomcat/script/db_shift
58 Configure the Oracle database.
– Run the following command on the VRM node (active VRM node if the VRM nodes
are deployed in active/standby mode):
sh switchDbToOracle.sh -mode "primary" -dbtype "oracle" -ipaddress "IP
address" -port "Port" -instance "Instance Name"
or
sh switchDbToOracle.sh -mode "primary" -dbtype "oracle" -ipaddress "IP
address" -port "Port" -service "Service Name"
– Run the following command on the standby VRM node:
sh switchDbToOracle.sh -mode "slave" -dbtype "oracle" -ipaddress "IP address"
-port "Port" -instance "Instance Name"
or
sh switchDbToOracle.sh -mode "slave" -dbtype "oracle" -ipaddress "IP address"
-port "Port" -service "Service Name"

For example, if the IP address, port number, instance name of the Oracle database server
are 192.168.40.4, 5432, and instance, respectively, run the following command on the
active VRM node:
sh switchDbToOracle.sh -mode "primary" -dbtype "oracle" -ipaddress

"192.168.40.4" -port "5432" -instance "instance"
The command takes about 5 minutes to execute on the active VRM node, and takes about
10 seconds on the standby VRM node.

Switch DB to Oracle succeeded!
59 If the VRM nodes work in active/standby mode, configure the database on the standby
node. For details, see Step 53 to Step 58.
----End

FusionCompute
Software Installation Guide A Appendix
A Appendix
A.1 FAQs
A.2 Common Operations

FusionCompute
A.1 FAQs
A.1.1 Storage Devices Cannot Be Detected on the FusionCompute
A.1.2 How to Configure an FC SAN Initiator
A.1.3 How to Configure an IP SAN Initiator
A.1.4 How to Create a Management Account for Advanced SAN Devices
A.1.5 How to Configure NIC Binding for the VRM Node
A.1.6 How to Setting Multipathing Mode for a Host Using Commands
A.1.7 How to Cancel the Isolation Between the Service Plane and the Management Plane on a
VRM Node
A.1.8 How to Troubleshoot the Occupied Port on the FusionCompute Installation Wizard
A.1.9 How to Troubleshoot the VM that Failed to Be Initialized Using the FusionCompute
Installation Wizard
A.1.10 How to Reconfigure Host Parameters
A.1.11 Troubleshooting the Tool of Deploying Hosts in Batches
A.1.12 Manually Changing the System Time on a Node
A.1.13 Troubleshooting the FusionCompute Installation Wizard
A.1.14 Creating a FusionCompute Tablespace in an Oracle Database
A.1.15 Recommended Configurations for Host Domain 0 Specifications
A.1.16 Background Information
A.1.17 Communication Principles
A.1.18 Compatibility
A.1.20 Binding Network Ports
A.1.21 How to Handle FusionCompute Installation Failures Caused by a Change in the Local
IP Address
A.1.1 Storage Devices Cannot Be Detected on the FusionCompute
Symptom
On the FusionCompute, a host cannot detect storage devices.
Possible Causes
A host cannot detect the storage devices in storage resources in either of the following scenarios:

FusionCompute
l When a host uses a local disk as the storage device, the disk has residual partition or logical
volume manager (LVM) information.
l When a host uses a storage area network (SAN) device as the storage device, LUNs on the
SAN device have residual partition or LVM information.
Fault Diagnosis
Manually delete residual information from the undetected storage device.
Prerequisites
Prerequisites
l You have obtained the management IP address of the host.

l You have obtained the login passwords of user gandalf and user root.
l For the undetected storage device serving as a local disk, you have obtained the logical
device name of the local disk.
l For the undetected storage device serving as a shared disk, you have obtained the logical
device name of the shared disk.
Data
Data preparation is not required for this operation.
Procedure
Check whether the undetected storage device is mapped to the host.
1 Use PuTTY to log in to the operating system (OS) of the host.
connection.
su - root
TMOUT=0
4 Check whether the undetected storage device serves as a shared disk.
5 Determine which multipathing mode is used as the storage path of the shared disk.
– If the universal multipathing mode is used, go to Step 6.
– If the Huawei multipathing mode is used, go to Step 7.
6 Run the following command to check whether the undetected storage device is mapped to
the host:
multipath -ll
– If yes, obtain the world wide name (WWN) of the undetected storage device based on
its name, make a note of the WWN (for example,
6925805100a122002ae31e4e0000006e), and go to Step 8.

FusionCompute
– If no, check whether the storage device is configured correctly. No further action is
required.
Information similar to the following is displayed:

36925805100a122002ae31e4e0000006e dm-6 HUASY,S5600T
size=20G features='1 queue_if_no_path' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
|- 7:0:0:8 sdi 8:128 active ready running
|- 8:0:0:8 sdq 65:0 active ready running
|- 9:0:0:8 sdy 65:128 active ready running
|- 10:0:0:8 sdag 66:0 active ready running
|- 11:0:0:8 sdao 66:128 active ready running
|- 12:0:0:8 sdaw 67:0 active ready running
|- 13:0:0:8 sdbe 67:128 active ready running
`- 14:0:0:8 sdbm 68:0 active ready running
36925805100a1220006b8b70500000064 dm-4 HUASY,S5600T
size=10G features='1 queue_if_no_path' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
|- 7:0:0:2 sde 8:64 active ready running
|- 8:0:0:2 sdm 8:192 active ready running
|- 9:0:0:2 sdu 65:64 active ready running
|- 10:0:0:2 sdac 65:192 active ready running
|- 11:0:0:2 sdak 66:64 active ready running
|- 12:0:0:2 sdas 66:192 active ready running
|- 13:0:0:2 sdba 67:64 active ready running
`- 14:0:0:2 sdbi 67:192 active ready running
7 Run the following command to check whether the undetected storage device is mapped to
the host:
upadmin show vlun
– If yes, obtain the WWN of the undetected storage device based on its name, make a
note of the WWN (for example, 6925805100a12200000af4ee00000012), and go to
Step 8.
– If no, check whether the storage device is configured correctly. No further action is
required.

------------------------------------------------------------------------------
------------------------------------------------------
Vlun ID Disk Name Lun WWN
Status Capacity Ctrl(Own/Work) Array Name
0 sdc LUN_019 6925805100a12200000af4ee00000012
Normal 500.00GB 0A/0A SN_210235G6EAZ0B4000006
1 sdd LUN_020 6925805100a12200000af53300000013
Normal 500.00GB 0B/0B SN_210235G6EAZ0B4000006
2 sde LUN004--test 6925805100a1220006b8b70500000064
3 sdf LUN_BRM_C02_03_002
6925805100a122000e8b90da00000075 Normal 20.00GB 0B/0B
SN_210235G6EAZ0B4000006
4 sdg qr_lun004 6925805100a122000012d6a100000072
5 sdh qr_lun002 6925805100a122002ae4e1f60000006f
6 sdi qr_lun001 6925805100a122002ae31e4e0000006e
7 sdj qr_lun_r2_001 6925805100a122000171e05800000077
------------------------------------------------------------------------------
------------------------------------------------------
Check whether the disk has residual LVM information.

FusionCompute
8 Run the following information to obtain the logical device name of the undetected device
based on its WWN:
ll /dev/disk/by-id |grep scsi-3wwn

scsi-36925805100a12200000af4ee00000012 -> ../../sdb
In the example, sdb is the logical device name of the undetected device whose WWN is
6925805100a12200000af4ee00000012.
9 Run the following command to check whether the undetected device has the physical
volume (PV) information:
pvdisplay /dev/Name of the logical device
– If yes, information similar to the following is displayed. Then, go to Step 10.
This command takes the logical device name /sdb as an example.

--- Physical volume ---
PV Name /dev/sdb
VG Name 3
PV Size 931.51 GiB / not usable 1.71 MiB
Allocatable yes
PE Size 4.00 MiB
Total PE 238467
Free PE 387
Allocated PE 238080
PV UUID LZJQFe-lrRT-hvnc-81RN-Y2Dz-Dres-CkXVTc
10 Check whether the command output in Step 9 contains the VG Name information, for
example, VG Name 3:
11 Run the following command to obtain LV Name based on VG Name:
lvdisplay
This command takes VG Name 3 as an example. If multiple LV Name results are displayed
for VG Name 3, make a note of all the logical volume (LV) names.
Check whether the command output contains at least one LV name in the format /dev/VG/
LV, for example, LV Name /dev/3/3.

--- Logical volume ---
LV Name /dev/3/3
VG Name 3
LV UUID vizADs-wqLO-ct34-4gp5-LieF-HZ7s-Rza12a
LV Write Access read/write
LV Status available
# open 1
LV Size 930.00 GiB
Current LE 238080
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 1024
Block device 253:9

FusionCompute
12 Run the following command to delete the LV based on the obtained LV name:
lvremove /dev/VG/LV
For example, run lvremove /dev/3/3.
Check whether the command output contains Can't remove open logical volume.

13 Run the following command to obtain the name of the undetected storage device based on
the logical device name:
ll /dev/disk/by-id/ | grep Name of the logical device

lrwxrwxrwx 1 root root 9 Oct 10 16:10 scsi-36925805100a12200000af4ee00000012
-> ../../sdb
In the example, scsi-36925805100a12200000af4ee00000012 is the name of the undetected

device whose logical device name is sdb.
14 On FusionCompute, click the Computing Pool tab. In the navigation tree on the left, click
the target host, and choose Configuration > Data Store to check whether the storage device
has been added in the data store.
15 Run the following command to change LV status:
lvchange -an /dev/VG/LV
16 Run the following command to delete the LV:
lvremove /dev/VG/LV
17 Enter y as instructed and press Enter.
18 If the VG contains multiple LVs as shown in the command output in Step 11, check whether
all the LVs are deleted.
19 Repeat Step 12 to Step 18 to delete other LVs.
20 Run the following command to delete the VG:
vgremove VG
21 Enter y as instructed and press Enter.
22 Run the following command to delete the PV:
pvremove /dev/Name of the logical device
23 On FusionCompute, click the Computing Pool tab. In the navigation tree on the left, click
the target host, and choose Configuration > Storage Device, and click Scan. Then, check
whether the storage device can be detected after the scan.
Delete the disk partitions of the host.

FusionCompute
NOTICE
Do not delete the partitions from the system disk when deleting host partitions. Otherwise, the
host will become unavailable and OSs must be reinstalled for it.
By default, /dev/sda is the system disk. However, it changes when the system uses another disk
as the system disk (for example, the host installs OSs using the internal USB disk), or when the
user changes the system disk during host installation. Therefore, you must differentiate the
system disk and user disks when deleting host partitions.
24 Run the following command to view the partition information of the undetected device on
the host based on the logical device name:
fdisk -l /dev/Name of the logical device

Disk /dev/sdb: 300.0 GB, 300000000000 bytes
256 heads, 63 sectors/track, 36330 cylinders, total 585937500 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System

/dev/sdb1 * 1 583983103 291991551+ ee GPT
/dev/sdb2 583983104 824621840 291991551+ ee Linux
...
This command takes the logical device name /sdb as an example. Check whether partition
information is displayed for the Device column, for example, dev/sdb1. If a partition exists
for the device, make a note of the device name. If no partition exists for the device, no
further action is required.
25 Run the following command to switch to the disk that has been cleaned up:
fdisk Device name
Command (m for help):
26 Enter d and press Enter.

– If information similar to the following is displayed, the disk has multiple partitions.
Then, go to Step 27.
Partition number (1-4)
– If information similar to the following is displayed, the disk has only one partition, and
the partition has been deleted. Then, go to Step 29.
Selected partition 1
27 Enter the number of the partition to be deleted, and press Enter.

Check whether all the partitions are deleted.
28 Repeat Step 26 to Step 27 to delete the rest partitions.
29 Enter w, save the settings, and exit the fdisk mode.
30 Run the following command to save the previous configurations:
partprobe /dev/Name of the logical device

FusionCompute
31 Check whether the local disk resources can be used normally.

– If no, contact Technical Support.
32 Check whether other storage devices still cannot be detected.
– If yes, repeat Step 1 to Step 32.
----End
A.1.2 How to Configure an FC SAN Initiator
Scenarios
A fiber channel storage area network (FC SAN) initiator is used to map hosts and FC SAN
storage devices using world wide names (WWNs), which are generated after the storage devices
are associated with hosts. This section describes how to obtain the WWN of the host and
configure the FC SAN initiator.
Prerequisites
Conditions
– The host has been added to the FusionCompute.
– You have logged in to the FusionCompute.
– You have configured the logic host (group) and logical unit numbers (LUNs) on the storage
management system, including creating a logical host (group), dividing LUNs, and
configuring the mapping between LUNs and the logical host (group).
Data
Procedure
1 Choose Computing Pool on the FusionCompute.

The Computing Pool page is displayed.
2 In the navigation tree, select the site, cluster, and host.
3 Choose Configuration > Storage Resource.
The storage resource page is displayed.
4 Click View Storage Adapter.
The Storage Adapter dialog box is displayed.
5 Click Scan.
6 Click OK.
You can view the task progress on the Task Tracing page.
7 Make a note of the WWN value of the host displayed on the Storage Adapter dialog box.
If the system uses FC SAN devices, the host WWN cannot be customized.

FusionCompute

----End
A.1.3 How to Configure an IP SAN Initiator
Scenarios
An IP storage area network (SAN) initiator is used to map hosts and IP SAN storage devices
using world wide names (WWNs), which are generated after the storage devices are associated
with hosts.
This section uses the S5500T storage device and the ISM V100R005C00SPC012 storage
management system as an example to describe how to configure the IP SAN initiator. For more
details, see the documentation delivered with the storage device.
Prerequisites
Conditions
– You have logged in to the storage management system, and the storage devices have been
discovered.
– You have obtained the host WWN.
– You have configured the logic host (group) and logical unit numbers (LUNs) on the storage
management system, including creating a logical host (group), dividing LUNs, and
configuring the mapping between LUNs and the logical host (group).
Data
Procedure
1 In the navigation tree on the left in the Oceanspace ISM window, choose All Devices,
select the storage device, click SAN Services, click Mappings, and click Hosts.
2 In the list displayed in the right pane, select the host that is associated with the storage
device.
3 Click Initiator Configuration on the menu bar.
4 Click Add.
5 Select the initiator based on the WWN value, and click OK.
An information dialog box is displayed.
6 Click OK.
The Result information dialog box is displayed.

FusionCompute
7 After the initiator is added, click Close.

8 Close the Initiator Configuration dialog box.
----End
A.1.4 How to Create a Management Account for Advanced SAN

Devices
Scenarios
If the system uses advanced storage area network (SAN) devices, you must create a management
account in addition to admin. This account is used to connect to the storage devices when the
FusionCompute is installed.
This section uses the OceanStor S5500T as an example to describe how to create a management
account for advanced SAN devices.
Prerequisites
Conditions
You have obtained the management IP address of the advanced SAN device controller.
Data
You have obtained the username and password for the account to be created.
Procedure
1 In the browser address box, enter http://management IP address of the advanced SAN
device controller/start.html, and press Enter.
The OceanStor Integrated Storage Management (ISM) login page is displayed.
2 Enter the username and password, and click Login.
The default username is admin, and the password is Admin@storage.
The OceanStor ISM page is displayed, as shown in Figure A-1.

FusionCompute
Figure A-1 OceanStor ISM page
3 Click on the right.

The Settings page is displayed.
4 In the View and settings area, click Permission Settings.
The Permission Settings page is displayed.
5 Choose User Management in the navigation tree on the left, and click Add in the lower
right corner.
6 Set Type to Local user.
7 Enter the username and password of the management account to be added.
8 Set User level to Administrator.
9 Click OK.
10 Click OK.
The management account is created.
----End
A.1.5 How to Configure NIC Binding for the VRM Node

FusionCompute
Scenarios
In the scenario where the Virtual Resource Management (VRM) node is deployed on a physical
server, deploy two network interface cards (NICs) on the management plane and bind them to
improve network reliability for the VRM node. NIC binding on the management plane is
recommended for both the standalone mode and the active/standby mode for the VRM node. To
bind other NICs, refer to this section.
Comply with the following principles when binding NICs for the VRM node:
l In the scenario where VRM nodes are deployed in active/standby mode, ensure that the
names of NICs to be bound (such as eth0 and eth1) on one node are consistent with the
other or no NICs are bound both nodes.
l In the scenario where the VRM node is deployed on a physical server, intelligent NICs
(iNICs) cannot be bound.
Impact on the System

NIC binding or unbinding interrupts VRM services for about 3 minutes.
Prerequisites
Conditions
– The VRM node has been installed.
– The VRM node has been configured with two NICs.
– You have obtained the password for user root of the VRM node.
Data
You have obtained the names of the bound NICs, for example, bond0.
NOTE
When you configure active/standby mode on the FusionCompute, the bound NICs to be selected are named
bond0, bond1, and bond2. Therefore, you are advised to name the bound NICs bond0, bond1, and
bond2, respectively when you configure NIC binding, to ease identification.
Procedure
Log in to the VRM node.
1 Open Internet Explorer on a local PC, enter http://VRM server BMC IP address in the
address box, and press Enter.
2 Log in to the BMC on the server as prompted.
The iMana Web page is displayed.
NOTE

FusionCompute
4 Log in to the host as user root.

Configure NIC binding for the VRM.
5 Run the following command to switch to the directory containing the script for NIC binding:
cd /opt/galax/vrm/tomcat/script/nrm/
6 Run the following command to bind the NICs for the VRM node:
sh bondNic.sh "Bound NIC name" "NIC to be bound 1 NIC to be bound 2" -NIC type
The description of the parameters in this command is as follows:

– Bound NIC name: When you configure active/standby mode on the FusionCompute,
the bound NICs to be selected are named bond0, bond1, and bond2. Therefore, you
are advised to name the bound NICs bond0, bond1, and bond2, respectively when you
configure NIC binding, to ease identification.
– NIC to be bound: To bind NICs on the management plane, enter the management NIC
configured during VRM installation for NIC to bound 1.
– NIC type: To bind NICs on the management plane, enter m. To bind other NICs, enter
o.
For example, to bind eth0 and eth1 on the management plane, run the following command:
sh bondNic.sh "bond0" "eth0 eth1" -m
If the following command output is displayed, the command is executed successfully and
you can close the remote control window:
bond success!
----End
Verification
After you bind the NICs, run the following command to query the NIC binding status:
cat /proc/net/bonding/Bound NIC name
For example, run the following command to check the binding status of bond0:
cat /proc/net/bonding/bond0

...
Bonding Mode: fault-tolerance (active-backup)
Primary Slave: None
Currently Active Slave: eth0
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0
Slave Interface: eth0

MII Status: up
Link Failure Count: 0
Permanent HW addr: 28:6e:d4:f2:76:00
Slave Interface: eth1

MII Status: up
Link Failure Count: 0
Permanent HW addr: 28:6e:d4:f2:76:01

FusionCompute
The information about the NICs that are bound and the current NIC in use is displayed in the
command output.
Related Tasks
Unbind NICs.
To unbind NICs, perform the following operations:
1. Switch to the directory containing the script for NIC binding. For details about the
operation, see Step 5.
2. Run the following command to unbind the NICs:
sh unbondNic.sh "Bound NIC name" -NIC type
To bind NICs on the management plane, set NIC type to m. To bind other NICs, set NIC
type to o.
For example, to unbind bond0 on the management plane, run the following command:
sh unbondNic.sh "bond0" -m
If the following command output is displayed, the command is executed successfully:
unbond success
NOTE
If the unbinding fails, rectify the fault. For details, see the operation for rectifying the fault that the binding
fails.
A.1.6 How to Setting Multipathing Mode for a Host Using

Commands
Scenarios
The multipathing mode cannot be changed on the FusionCompute for a host where the
Virtualization Resource Management (VRM) is deployed. Therefore, you need to set the
multipathing mode using commands.
Impact on the System

Services on VMs on the host will be interrupted, because the operation results in host restart.
Prerequisites
Conditions
– You have installed the host operating system (OS).
– You have obtained the password for user root of the host.
Procedure
Log in to the host.
1 Use PuTTY to log in to the host.
connection.

FusionCompute
su - root
TMOUT=0
Set the multipathing mode for the host.
4 Run the following command to change the multipathing mode to Huawei multipathing:
sh /opt/uvp/multipath/change_multipath_mode.sh 1
Enable ultrapath successfully.
5 Run the following command to restart the host:

reboot
----End
A.1.7 How to Cancel the Isolation Between the Service Plane and
the Management Plane on a VRM Node
Scenarios
To resume the communication between the service plane and the management plane on a
Virtualization Resource Management (VRM), cancel the isolation between them.
After the cancelation, the VRM node uses its management plane network interface card (NIC)
to provide the Dynamic Host Configuration Protocol (DHCP) service to subnets in the
FusionCompute system again.
Prerequisites
l The isolation between the service plane and the management plane on the VRM node has
been implemented.
l The active and standby VRM nodes are running properly.
l You have obtained the passwords for users gandalf and root of the active and standby
VRM nodes.
l You have obtained the passwords of users gandalf and root for logging in to the hosts on
which the VRM VMs run.
Procedure
Cancel the isolation between the service plane and the management plane on the VRM node.
1 On the FusionCompute, choose System > System Configuration > Services & Mgt.
Nodes, and make a note of the active and standby VRM nodes and their IP addresses.
2 Use PuTTY to log in to the active VRM node.
connection.

FusionCompute
su - root
TMOUT=0
5 Run the following command to cancel the isolation between the service plane and the
management plane on the VRM node:
sh /opt/galax/vrm/tomcat/script/clear_isolation.sh
The command is executed if the following information is displayed:
clear isolation done.
6 Perform the following operations to ensure that Step 5 is executed successfully.

– Run the cat /etc/crontab command to check whether the scheduled task of the
startDHCP.sh script has been deleted.
The scheduled task of the startDHCP.sh script has been deleted if the command output
contains no information about startDHCP.sh.
– Run the ifconfig -a command to check whether the IP address of the service plane NIC
has been deleted.
The IP address of the service plane NIC has been deleted if the command output contains
no information about IP address of the service NIC (usually named eth1).
– Run the route command to check whether the route to the service plane NIC has been
deleted.
The route to the service plane NIC has been deleted if the the last column (Iface) in the
command output contains no information about the service NIC (usually named eth1).
If any of the check items does not meet its requirement, repeat Step 5.
7 Run the following command to delete the NIC from the service plane:
sh /opt/galax/vrm/tomcat/script/nrm/rmNetDevFromFW.sh "ethID"
ethID indicates the ID of the VM NIC that connects to the service plane.
The command is executed successfully if no command output is displayed:
8 Run the following command to check whether the VRM node uses the management plane
NIC to provide the DHCP service to subnets:
ps -ef | grep dhcp | grep pid | awk '{print $NF}'
The VRM node uses the management plane NIC to provide the DHCP service to subnets
if the command output contains no information about the management plane NIC (usually
named eth0).
9 Cancel the isolation between the service plane and the management plane on the standby
VRM node. For details, see Step 2 to Step 7.
Delete the service plane NICs on the active and standby VRM VMs.
If you do not want to implement the isolation between the management plane and the service
plane, delete the service plane NIC. Otherwise, skip this operation.
10 Determine whether to delete the service plane NICs on the VRM VMs.
11 Log in to the FusionCompute.
12 Select VM and Template and click the active VRM VM on the VM page.
The Summary page of the VM is displayed.

FusionCompute
NOTE
Make a note of the active VM ID on the Summary page. This ID will be used when you backup the
VRM node information.
13 On the Hardware page, click NIC, locate the row that contain the service plane NIC, click
Operation, and click Delete NIC.
14 Click OK.
The deletion starts and a dialog box is displayed.
15 Click OK.
View the task progress on the Task Tracing page and ensure that the NIC is successfully
deleted.
16 Delete the service plane NIC on the standby VRM VM. For details, see Step 11 to Step
15.
Update the VRM node information.
17 In the PuTTY window on the active VRM node, run the following commands to update
the active and standby VRM nodes information:
perl /opt/galax/vrm/tomcat/script/vrmWindowsInstall/bin/importVrmDb.pl -g -i
Active VRM VM ID
Standby VRM VM ID
For example, if the active and standby VRM VM IDs are i-00000001 and i-00000002, run
the following command:
i-00000001
i-00000002
VRM VM configuration files named VM ID.xml are generated in the /home folder.
18 Run the following commands in sequence to copy the active and standby VM configuration
files to the hosts on which the active and standby VMs run, respectively:
scp /home/Active VRM VM ID.xml gandalf@Host IP address:/home/GalaX8800
scp /home/Standby VRM ID.xml gandalf@Host IP address:/home/GalaX8800
For example, if the VM ID and host IP address for the active VRM node are i-00000001
and 192.168.200.21, respectively, and the VM ID and host IP address for the standby VRM
node are i-00000002 and 192.168.200.22, respectively, run the following commands in
sequence:
scp /home/i-00000001.xml gandalf@192.168.200.21:/home/GalaX8800
scp /home/i-00000002.xml gandalf@192.168.200.22:/home/GalaX8800
19 Use PuTTY to log in to the host on which the active VRM VM runs.
20 Run the following command to back up the VRM VM configuration file stored on the host:
cp /etc/galax/eucalyptus/Active VRM VM ID.xml /etc/galax/eucalyptus/Active VRM VM
ID.xml.bak

FusionCompute
If the VRM VM is incorrectly configured, the backup file can be used to restore the VRM
node to the state when the backup file is created.
21 Run the following command to copy the new VRM VM configuration file to the /etc/galax/
eucalyptus/ directory:
mv /home/GalaX8800/VM ID.xml /etc/galax/eucalyptus/
22 Log in to the host on which the standby VRM VM runs, back up the original VRM VM
configuration file, and copy the new VRM VM configuration file to the /etc/galax/
eucalyptus/ directory.
23 Log in to the active VRM node and run the following commands to copy the configuration
files of the active and standby VRM nodes to the /etc/galax/vm_xml/ directory:
cp /home/Active VRM VM ID.xml /etc/galax/vm_xml/
cp /home/Standby VRM VM ID.xml /etc/galax/vm_xml/
----End
A.1.8 How to Troubleshoot the Occupied Port on the

FusionCompute Installation Wizard
Symptom
The installation is interrupted by a message displayed on the FusionCompute installation wizard
indicating that a port has been occupied.
Possible Causes
The default port used by the postgresql service is 5432. If the postgresql service has been installed
on the local PC or a program on the local PC uses port 5432, the postgresql service used by the
FusionCompute installation wizard cannot start.
Fault Diagnosis
None
Procedure
1 On the local PC, click Start, enter cmd in Search programs and files, and press Enter to
open the command-line interface (CLI).
2 Run the following command to view ID of the process that is using port 5432:
netstat -ano | findstr :5432
If information similar to the following is displayed, note down the process ID (the figure
displayed in the last column):
TCP 127.0.0.1:5432 0.0.0.0:0 LISTENING 9912
TCP [::1]:5432 [::]:0 LISTENING 9912
3 Right-click the blank area on the task bar, select Start Task Manager to open the Windows
Task Manager.

FusionCompute
4 On the Processes page, choose View > Select Columns on the upper part, select PID
(Process Identifier) in the Select Process Page Columns window, and click OK.
5 On the Processes page, select Show processes from all users and locate the process in the
PID column based on the ID obtained in Step 2, as shown in Figure A-2.
Figure A-2 Windows Task Manager
6 If ending process does not exert adverse impact on the local PC, end the process.
NOTE
If ending process exerts adverse impact on the local PC, run the FusionCompute installation wizard
on another PC.
7 Close the Windows Task Manager and run the FusionCompute installation wizard again.
If the installation still fails, contact technical support.
----End

FusionCompute
A.1.9 How to Troubleshoot the VM that Failed to Be Initialized

Using the FusionCompute Installation Wizard
Symptom
The error message "Failed to initialize the the management VM" is displayed during VM
installation using the FusionCompute installation wizard.
Possible Causes
The FusionCompute installation wizard failed to communicate with the host using Secure Shell
(SSH).
Fault Diagnosis
None
Procedure
1 On the page where the error message is displayed, click Show Logs in the lower left corner
to open the log file.
2 Check whether the log contains the following information:
YYYY-MM-DD HH:MM:SS.SSS> [DEBUG] Connect to [Host IP] fail...
Or
YYYY-MM-DD HH:MM:SS.SSS> [ERROR] get session of [Host IP] failed...
3 Obtain the host IP address (Host IP) in the log and use PuTTY to log in the host.
Perform the following operations to check the host:
– Log to the host as user gandalf using the default password Huawei@CLOUD8. The
login is successful.
– Run the su - root command and enter the password of user root set during host OS
installation to switch to user root. The switching is successful.
If the above check items fail, check whether the passwords have been changed or locked.
If yes, troubleshoot the passwords and go to Step 4.

If no, go to Step 8.
4 On the page where the error message is displayed, click Previous, then Next to initialize
the management VM again.
5 Check whether the management VM installation is successful.
– If yes, no further action is required.
6 Close the installation wizard, open it again, and select Continue. Retain all default settings,
click all the Next buttons displayed to initialize the management VM again.
7 Check whether the VRM installation is successful.

FusionCompute
– If yes, no further action is required.

8 Contact technical support.
----End
A.1.10 How to Reconfigure Host Parameters
Scenarios
During the host installation process, some parameters are mistakenly configured. As a result,
the host cannot be added to FusionCompute. In this case, run the hostconfig command to
reconfigure the host parameters.
The following parameters can be reconfigured:
l Management IP address of the host

l Management plane gateway address
l Host name
l Password of user root of the host
Prerequisites
l The operating system has been installed on the host.
l You have obtained the IP address, username, and password for logging in to the BMC of
the host.
l You have obtained the passwords for user root of the host.
l The host has not been added to a site nor a cluster in the FusionCompute system.
Procedure
Log in to the host.
1 Open the browser on the PC, enter http://BMC IP address of the host in the address box,
and press Enter.
2 Log in to the BMC system on the host.
The default username is root, and the password is Huawei12#$.
The host management page is displayed.
NOTE
4 Log in to the host as user root in the remote control window.

FusionCompute

TMOUT=0
Modify the configuration for the host.
6 Run the following command to enter the Main Installation Window screen, as shown in
Figure A-3.
hostconfig
Figure A-3 Main Installation Window
NOTE
When configuring host data on the Main Installation Window screen:
l Use number keys on the keyboard to enter numbers.
l Press Enter to select or set an option.
7 Choose Network > eth0 to enter the eth0 configuration screen, as shown in Figure A-4.
NOTE
the management NIC.

FusionCompute
Figure A-4 IP Configuration for eth0
8 Configure the IP address and subnet mask for eth0.

NOTE
enter numbers.
in Default Gateway, as shown in Figure A-5.
Figure A-5 Network Configuration screen

NOTE
After the network configuration is complete, you can set the gateway address of the management
plane and IP addresses of other planes in Test Network to check whether the newly configured IP
addresses are available.
12 Select Hostname to enter the Hostname Configuration screen, as shown in Figure A-6.

FusionCompute
Figure A-6 Hostname Configuration
13 Delete the original information, enter the host name, and select OK to finish the host name
configuration.
14 Select Password.
The Root Password Configuration screen is displayed, as shown in Figure A-7.
Figure A-7 Root Password Configuration
15 Enter the password and the confirm password, and select OK to finish the password
configuration.
NOTE
The password must contain at least:
l Eight characters
l One space or one of the following special characters: ~!@#$%^&*()-_=+\|[{}];:'",<.>/?
l Two of the following combinations:
l Lowercase letters
l Uppercase letters
l Digits
16 Press ESC to exit the host configuration window.

FusionCompute
The configurations take effect immediately. The host name will be displayed the next time
you log in to the system.
----End
A.1.11 Troubleshooting the Tool of Deploying Hosts in Batches

The following faults may occur when you are using the tool of deploying hosts in batches:
l The "XXX service already exists in the system. Uninstall the service and try again"
message is displayed on the Install Components page.
l The "Port XXX occupied. Check whether another XXX service is started" message is
displayed on the Install Components page.
l The "Failed to decompress the host ISO image" message is displayed on the Configure
Services page.
l Host information cannot be automatically displayed on the Install Hosts page.
l The "Installation of certain hosts failed or timed out. Address the issue and try
again" message is displayed on the Install Hosts page.
The "XXX service already exists in the system. Uninstall the service and try
again" message is displayed on the Install Components page.
l Possible cause: The target service installed on the local PC conflicts with the tool. The
service must be uninstalled before you run the tool.
Solution:
– Check whether the service can be uninstalled.
– If yes, uninstall the service, and click Retry on the Install Components page of the
tool.
– If no, use another PC that does not have the service installed and run the tool again.
The "Port XXX occupied. Check whether another XXX service is started" message
is displayed on the Install Components page.
l Possible cause: A File Transfer Protocol (FTP), Trivial File Transfer Protocol (TFTP), or
Dynamic Host Configuration Protocol (DHCP) process is running on the local PC system
and conflicts with the tool.
Solution:
1. On the local PC, click Start, enter cmd in Search programs and files, and press
Enter to open the command-line interface (CLI).
2. Run the netstat -ano | findstr :Port number command to view the ID of the process
that is using port. For example, if the target port number is 21, run netstat -ano |
findstr :21.
3. Make a note of the target process ID (the figure displayed in the last column in the
command output).
4. Right-click the blank area on the task bar, and select Start Task Manager to open
the Windows Task Manager.
5. On the Processes tab, choose View > Select Columns, select PID (Process
Identifier) in the dialog box, and click OK.

FusionCompute
6. On the Processes tab, select Show processes from all users, and locate the obtained
target process ID in the PID column.
7. If ending process does not exert adverse impact on the local PC, end the process.
8. Click Retry on the Install Components page of the tool.
The "Failed to decompress the host ISO image" message is displayed on the
Configure Services page.
l Possible cause: The Computing Node Agent (CNA) software package (ISO image) has
been damaged.
Solution: Use the sha256 tool to verify the CNA software package. If the package is
damaged, obtain a new CNA software package.
Host information cannot be automatically displayed on the Install Hosts page.

l Possible cause: The firewall on the local PC blocks the communication between the PC
and the host.
Solution: Disable the Windows firewall and other software firewalls on the local PC and
start the hosts over the network.
l Possible cause: The local PC IP address, that is, the DHCP service IP address, cannot
communicate with the installation plane.
Solution:
1. Check the physical cabling between the local PC and the hosts to be installed and
ensure that network cables, ports, and other cabling devices are working properly.
2. Check the physical devices that connect the local PC to the hosts to be installed and
ensure that the physical devices, such as switches and firewalls, are working properly,
DHCP, TFTP, and FTP ports are enabled, and the port traffic rates are not limited.
3. If the local PC IP address does not belong to the installation plane network segment,
ensure that DHCP relay is configured on the switches.
4. If the host management plane has a virtual local area network (VLAN) configured,
ensure that the installation network plane and the host management plane use different
VLANs, and the local PC PC can communicate with both the network planes.
NOTE
l Do not add VLAN tags to packets passing through the preboot execution environment
(PXE) port during the PXE boot process. Configure network settings to allow these packets
to pass through the port.
5. Start the hosts again through the network.
l Possible cause: Multiple DHCP servers are deployed on the installation plane.
Solution: Disable redundant DHCP servers and use the tool of deploying hosts in batches
on the local PC to provide DHCP services.
l Possible cause: The host to be installed supports booting from network, but it did not boot
from the network.
Solution: Boot the host from the network. For details, see the corresponding hardware
documentation.
l Possible cause: Hosts to be installed do not support booting from the network.
Solution: Install the hosts by mounting ISO images.

FusionCompute
l Possible cause: Hosts to be installed fail to boot from the network.

Solution: Use the remote control interface of the host baseboard management controller
(BMC) to observe the host boot process and troubleshoot the hosts based on the messages
displayed on the interface and the host hardware documentation.
l Possible cause: Network congestion or packet loss or delay occurred due to high loads on
the switch.
Solution: Ensure that the network workloads are light during the installation process. If
the number of hosts to be installed is greater than 50, boot ten hosts per batch from the
network.
l Possible cause: The network interface card (NIC) order on the local PC is incorrect, which
makes the DHCP server IP address obtained by hosts different than that provided by the
local PC.
Solution: Change the NIC order for the local PC. The following operations use a local PC
running Windows 7 as an example to illustrate how to change the NIC order:
1. On the local PC, choose Start > Run, enter ncpa.cpl, and press Enter.
The Network Connections window is displayed.
2. Press Alt to show the menu bar and choose Advanced > Advanced Settings.
The Advanced Settings window is displayed.
3. In the Connections area on the Adapters and Bindings page, change the NIC that
uses the service IP address set on the Configure Service page of the installation tool
to the first place.
The "Installation of certain hosts failed or timed out. Address the issue and try
again" message is displayed on the Install Hosts page.
l Possible cause: The host installation status is Failed in the host information table.
Solution:
1. Right-click the host whose installation status is Failed and choose View Logs.
2. View the logs of the [ERROR] level in the View Logs window and troubleshoot the
host based on the logs.
3. If The log file does not exist. is displayed, contact the technical support.
l Possible cause: The host installation status is Timeout in the host information table.
Solution:
1. Check whether any host is unexpectedly powered off. If yes, start the host through the
network.
2. Check the host BIOS configurations. If the first boot device is not a hard disk or a
USB device, change the first boot device to a hard disk or a USB device, and boot the
host from the network.
3. Use the host BMC remote control interface to log in to the host, run the cat /opt/galax/
version/GalaxVersion.cfg command to check the system version, and ensure that the
host is installed.
4. If the host is installed, run the ifconfig and route commands to check whether the host
management plane configurations are correct, and run the ping command to check
whether the network connection between the host and the local PC is normal.

FusionCompute
5. If the network connection between the host and the local PC is abnormal, ensure that
the local PC IP address can communicate with the host management plane.
6. If no fault is found, contact the technical support.
A.1.12 Manually Changing the System Time on a Node
Scenarios
If no external clock source is deployed, the host or physical server where the Virtualization
Resource Management (VRM) node is deployed must be set as the Network Time Protocol
(NTP) clock source node. In this case, the system time on the target host or server must be
accurate.
Prerequisites
l You have obtained the passwords of users gandalf and root of the node that serves as the
NTP clock source.
Procedure
Log in to the operating system (OS) of the node that serves as the NTP clock source.
1 Use PuTTY to log in to the node that serves as the NTP clock source.
connection.
su - root
TMOUT=0
Manually change the system time on the node.
4 Check whether any external NTP clock source is configured for the node.
5 Run the following command to set the NTP clock source for the node to the node itself:
perl /opt/galax/gms/common/config/configNtp.pl -ntpip 127.0.0.1 -cycle 6 -timezone

Local time zone -force true
The local time zone must be set in Continent/Region format.
For example, if the local time zone is Asia/Beijing, run the following command:
perl /opt/galax/gms/common/config/configNtp.pl -ntpip 127.0.0.1 -cycle 6 -timezone

Asia/Beijing -force true
6 Run the date command to check whether the current system time is accurate.
7 Run a command to stop a corresponding process based on the node type:

FusionCompute
– If the node is a host, run the following command:

perl /opt/galax/gms/common/config/restartCnaProcess.pl
– If the node is a physical server, run the following command:
sh /opt/omm/ha/module/hacom/script/stop_ha.sh
8 Run the following command to rectify the system time of the node:
date -s Current time
The current time must be set in HH:MM:SS format.
For example, if the current time is 16:20:15, run the following command:
date -s 16:20:15
9 Run the following command to synchronize the new time to the basic input/output system
(BIOS) clock:
/sbin/hwclock -w -u
10 Run a command to start a corresponding process based on the node type:
– If the node is a host, run the following command:
service monitord start
– If the node is a physical server, run the following command:
service had start
11 After 3 minutes, run the ntpq -p command.
remote refid st t when poll reach delay offset jitter
==============================================================================
*LOCAL(0) .LOCL. 5 l 58 64 377 0.000 0.000 0.001
If * is displayed on the left of LOCAL, the time service is running properly on the node.
The node can be used as an NTP clock source.
If * is not displayed, run the ntpq -p command five to ten minutes later again to check the
time service running status.
----End
A.1.13 Troubleshooting the FusionCompute Installation Wizard

The following errors are displayed when you use the FusionCompute installation wizard:
l An error occurs when you install the .NET Framework 4.0 installation package.
l "The Java environment variables in the system are incorrect. Check the
JAVA_HOME or JRE_HOME environment variable." is displayed when the wizard
starts.
l "Environment variable CATALINA_HOME is in use. Please delete this variable
first." is displayed when the wizard starts.
l "The JRE program is not installed in the system. Please install the JRE program
l "Port 5432 is in use. Please disable the program using this port first." is displayed
when the wizard starts.
l "Failed to extract components." is displayed on the Install Components page.

FusionCompute
l "Failed to install components." is displayed on the Install Components page.

l "Failed to start the component service." is displayed on the Install Components page.
l "Failed to load components configuration information." is displayed on the Install
Components page.
l "Failed to switch to root user." is displayed on the Configure Host page.
l "Failed to update the site IP address." is displayed on the Configure Host page.
l "Failed to send messages to the host." is displayed on the Configure Host or Configure
Data Store page.
l "The host has already been added to another site." is displayed on the Configure
Host page.
l "The host returns an error message." is displayed on the Configure Host page.
l "Failed to refresh resources when the Host is being added. Please check the host
status." is displayed on the Configure Host page.
l "The host gateway is incorrectly configured or not configured. Please configure it
again." is displayed on the Configure Host page.
l "No storage device available." is displayed on the Configure Data Store page.
l "Failed to create VM." is displayed on the Install VM page.
l "Failed to start the VM." is displayed on the Install VM page.
l "VRM vm is unreachable." is displayed on the Install VM page.
l "Failed to Configuring active and standby nodes." is displayed on the Install VM
page.
l "Failed to initialize the management VM." is displayed on the Install VM page.
l "Initialize the management VM timeout." is displayed on the Install VM page.
l "Failed to Uninstall component." is displayed on the Install VM page.
l "Failed to query Vms." is displayed on the Install VM page.
An error occurs when you install the .NET Framework 4.0 installation package.
Possible cause: The windows imaging component (WIC) is not installed.
Solution:
1. Download the WIC from the official website of the Microsoft and install the WIC.
l If the PC runs a 32–bit OS, log in to http://www.microsoft.com/en-us/download/
default.aspx and search and download Windows Imaging Component.
l If the PC runs a 64–bit OS, log in to http://www.microsoft.com/en-us/download/
default.aspx and search and download Windows Imaging Component (64-bit).
"The Java environment variables in the system are incorrect. Check the
JAVA_HOME or JRE_HOME environment variable." is displayed when the wizard
starts.
Possible cause: A necessary Java file (such as java.exe, jre.exe, javaw.exe, or jvm.dll) is
unavailable in the directory to which the PC environment variables JAVA_HOME or
JRE_HOME points.

FusionCompute
Solution:
1. On the local (Windows) PC, click Start, enter path in Search programs and files, and
press Enter to open the Environment Variables window.
2. Delete JAVA_HOME and JRE_HOME from System variables and start the wizard
again.
3. If the fault persists, query JAVA_HOME and JRE_HOME, respectively, in
HKEY_LOCAL_MACHINE\SYSTEM\. If the variable definition of JAVA_HOME or
JRE_HOME exists, check whether the definition contains the correct Java installation
path. If the path is incorrect, correct the value or delete the variable, and run the installation
wizard again.
"Environment variable CATALINA_HOME is in use. Please delete this variable

Possible cause: The wizard contains the environment variable CATALINA_HOME, which
conflicts with the environment variable defined in the local PC.
Solution:
1. On the local (Windows) PC, click Start, enter path in Search programs and files, and
press Enter to open the Environment Variables window.
2. Delete CATALINA_HOME from System variables and start the wizard again.
"The JRE program is not installed in the system. Please install the JRE program
Possible cause: The JRE is not installed.
Solution:
1. Install the JRE file in the PlugIn directory and then start the wizard.
"Port 5432 is in use. Please disable the program using this port first." is displayed
when the wizard starts.
Possible cause: The default port used by the postgresql service is 5432. If the postgresql service
has been installed on the local PC or a program on the local PC uses port 5432, the postgresql
service used by the FusionCompute installation wizard cannot start.
Solution:
1. For details, see How to Troubleshoot the Occupied Port on the FusionCompute
Installation Wizard.
"Failed to extract components." is displayed on the Install Components page.

Possible cause: The CloudComponent directory in the root directory on the disk where you
install the wizard is occupied by another process.
Solution:
1. In the root directory on the disk where you install the wizard, delete the
CloudComponent directory.

FusionCompute
2. Click Previous on the wizard and then click Next to install the components again.
"Failed to install components." is displayed on the Install Components page.

Possible cause: An error occurs when you install the GaussDB or Virtualization Resource
Management (VRM) service.
Solution:
1. Close the installation wizard and then run it again. If the issue persists, use another PC and
then start the wizard.
"Failed to start the component service." is displayed on the Install Components

page.
Possible cause: Before the environment construction is complete, the CloudComponent
directory in the root directory on the disk where you install the wizard is incorrectly deleted.
The CloudComponent directory contains program files required by the VRM service and the
database service. Therefore, the services cannot start.
Solution:
1. On the local (Windows) PC, click Start, enter cmd in Search programs and files, and
press Enter to open the command-line interface (CLI) window.
2. Run the following commands to delete VRM service and the database service:
sc delete win_vrm
sc delete win_psql
3. On the local PC, click Start, enter regedit.exe in Search programs and files, and press
Enter to open the Registry Editor.
4. Delete the GalaxEngineInstaller folder in the HKEY_LOCAL_MACHINE
\SOFTWARE\Huawei\ directory.
5. Start the wizard again.
"Failed to load components configuration information." is displayed on the Install

Components page.
Possible cause: The Java or Tomcat process required by the wizard is abnormal.
Solution: If the Java or Tomcat process is abnormal, delete Java JDK or Java JRE on the local
PC, and install the JRE in the PlugIn folder of the wizard. After JRE is installed, start the wizard
again.
NOTE
The wizard supports only java JRE 1.7 or JDK 1.7.
"Failed to switch to root user." is displayed on the Configure Host page.

l Possible cause: The entered management IP address of the host is incorrect. For example,
the host baseboard management controller (BMC) IP address is incorrectly entered as the
host management IP address.

FusionCompute
Solution: Check whether you can use PuTTY to log in to the host through the entered IP
address as user gandalf. If the login fails, the entered IP address is not the host management
IP address. Enter the correct host management IP address on the wizard.
l Possible cause: IP addresses in the environment conflict.
Solution: Remotely log in to the host using the host BMC and run the ifconfig ethX
down command to stop the host NIC. On the local PC, ping the host management IP address.
If the IP address can be pinged, IP addresses in the environment conflict. Change the host
management IP address or the existing IP address that conflicts with the host management
IP address.
l Possible cause: The host OS is not from the FusionCompute Computing Node Agent
(CNA) software package.
Solution: Log in to the host OS and run the service vnad status command to check whether
the vnad service exists in the system. If not, the host OS is not the FusionCompute CNA.
Reinstall the host OS.
l Possible cause: The wizard was installed from a network path.
Solution: Start the wizard on the local PC.
l Possible cause: The DNS server configured in the /etc/resolve.conf file on the host is
unavailable. As a result, the connection of the wizard to the host timed out.
Solution: Delete or modify the DNS configuration and try to log in to the host using the
wizard again.
l Possible cause: The firewall or other security software of the system prevents the SSH
component of the wizard from connecting to the host.
Solution: Disable the firewall or other security software.
l Possible cause: Java 1.8 or higher is installed on the local PC.
Solution: Delete Java JDK or Java JRE on the local PC, and install the JRE in the
PlugIn folder of the wizard. After JRE is installed, start the wizard again.
NOTE
"Failed to update the site IP address." is displayed on the Configure Host page.
Possible cause: The following conditions may result in VRM exceptions:
l The memory is insufficient on the local PC.
l The free space on the disk where the PC OS is installed is insufficient.
l The Java or Tomcat process required by the wizard is abnormal.
l The local PC has residual data of an earlier version wizard.
Solution:
l If the memory or the disk space is insufficient, clear up the memory space or the disk space.
l If the Java or Tomcat process is abnormal, delete Java JDK or Java JRE on the local PC,
and install the JRE in the PlugIn folder of the wizard. After JRE is installed, start the wizard
again.
NOTE

FusionCompute
l If the local PC has residual data of an earlier version wizard, close the wizard and start it
again. Then, choose Uninstall. The wizard automatically clears the residual data.
"Failed to send messages to the host." is displayed on the Configure Host or

Configure Data Store page.
l Possible cause: The firewall on the local PC blocks the communication between the PC
and the host.
Solution: Disable the Windows firewall and other software firewalls on the local PC and
click Configure Host on the wizard again.
l Possible cause: The IP address of the local PC cannot be pinged from the host.
Solution: Log in to the host OS, ping the IP address of the local PC. If the IP address of
the local PC cannot be pinged from the host, troubleshoot the network and click Configure
Host on the wizard again.
l Possible cause: The host is faulty.
Solution: Check whether the host is faulty, for example, whether it is restarted or stopped.
Ensure that the host is functional and then click Configure Host or Refresh Storage
Device.
"The host has already been added to another site." is displayed on the Configure
Host page.
l Possible cause: During the installation process, a second PC is used to continue the
installation. If the host is configured on the first PC, and the host is configured on the second
PC, an error message is displayed.
Solution: Continue the installation on the first PC.
l Possible cause: The host has been added to and deleted from a site, but the site configuration
data on the host has not been cleared up.
Solution: Install the host again.
l Possible cause: The network is disconnected when you configure the host. After the
network is reconnected, the IP address of the local PC changes.
Solution:
1. Log in to the host and check whether the vrm-info file exists in the /opt/galax/data/
hostinfo directory.
– If yes, go to 2.
– If no, install the host again.
2. Check whether the IP address of the local PC is the same as the IP address recorded
in the vrm-info file.
– If yes, install the host again.
– If no, go to 3.
3. Delete all files in the /opt/galax/data/hostinfo directory and run the service vnad
restart command to restart the vna process. Wait for 1 minute and then configure the
host again.
"The host returns an error message." is displayed on the Configure Host page.
Possible cause: An internal error occurs when you configure the host.

FusionCompute
Solution: Contact Huawei technical support.
"Failed to refresh resources when the Host is being added. Please check the host
status." is displayed on the Configure Host page.
Possible cause:
l The firewall on the local PC blocks the communication between the PC and the host.
l The IP address of the local PC cannot be pinged from the host.
l The host is faulty.
Solution: For details, see "Failed to send messages to the host." is displayed on the Configure
Host or Configure Data Store page..
"The host gateway is incorrectly configured or not configured. Please configure it

again." is displayed on the Configure Host page.
Possible cause: No gateway is configured on the host, the host gateway address is incorrect, or
the host gateway is unreachable.
Solution: Log in to the host OS, run the cat /etc/sysconfig/network/routes command to check
whether the gateway is configured correctly.
l If the gateway is configured correctly, ping the gateway address from the host. If the
gateway address cannot be pinged, troubleshoot the network.
l If the gateway is configured incorrectly, reconfigure the gateway. For details, see How to
Reconfigure Host Parameters.
"No storage device available." is displayed on the Configure Data Store page.
Possible cause: The host has residual data of the storage device.
Solution: For details, see Storage Devices Cannot Be Detected on the FusionCompute.
"Failed to create VM." is displayed on the Install VM page.

l Possible cause: The network between the local PC and host is disconnected.
Solution: After the network is reconnected. Click Previous on the wizard and then click
Next to switch to the Install VM page.
l Possible cause: The host time has changed.
Solution: Click Previous on the wizard and then click Next to switch to the Install VM
page.
l Possible cause: The IP address of the local PC has changed.
Solution: Close the wizard and then start it again. Choose Continue and click Next until
the Install VM page is displayed.
l Possible cause: The host OS has been reinstalled after the host is configured on the wizard.
Solution:
1. Close the wizard and then start it again. Choose Uninstall. If "Failed to clear hosts."
is displayed during uninstallation, click Yes to continue to clear the wizard.
2. Install the OS on the host again.

FusionCompute
3. Deploy the system again using the wizard.
"Failed to start the VM." is displayed on the Install VM page.

l Possible cause: The VM slowly starts up, and therefore the ping operation for the VM IP
address times out.
Solution: Click Previous on the wizard and then click Next to switch to the Install VM
page.
l Possible cause: The Virtual-Machine Extensions (VMX) function of the server is not
enabled.
Solution: Enable the VMX function. The following steps take a Huawei server as an
example:
1. Use the BMC to log in to the host where the VM failed to start up. Restart the host
and switch to the BIOS screen.
2. Choose Advanced > CPU Configuration > Intel Virtualization Technology and
change Disabled to Enabled. Save the configuration and restart the host.
3. After the host is restarted, click Previous on the wizard and then click Next to switch
to the Install VM page.
"VRM vm is unreachable." is displayed on the Install VM page.

l Possible cause: The VLAN configured for the VRM VM is incorrect.
Solution: Click Previous until the Configure VRM VM page for the first host is displayed.
Cancel or modify the VLAN configuration based on the actual situation. After the VRM
configuration is verified, click Next until the Install VM page is displayed.
l Possible cause: The IP address of the VRM VM conflicts with another IP address.
Solution: After the IP conflict issue is resolved, click Previous on the wizard and then
click Next to switch to the Install VM page.
NOTE
If you need to change the IP address of the VRM VM, install the host again and start the wizard
again.
l Possible cause: The IP address of the VRM VM is incorrect.
Solution: Install the host again and start the wizard again.
"Failed to Configuring active and standby nodes." is displayed on the Install VM

page.
l Possible cause: All arbitration IP addresses of the VRM VM are unreachable.
Solution: Ensure that the gateway of the VRM VM can be pinged. Click Previous on the
wizard and then click Next to switch to the Install VM page.
l Possible cause: After you log in to the VRM VM or VRM host using SSH and invoke the
shell script, the script fails to invoke due to network interruption.
Solution:
1. View the log. The failure is caused by network interruption if the log contains the
following operation:
System.Net.Sockets.SocketException (0x80004005): A connection attempt
failed because the connected party did not properly respond after a period

FusionCompute
of time, or established connection failed because connected host has

failed to respond.
2. After the network is reconnected, click Previous on the wizard and then click Next
to switch to the Install VM page.
"Failed to initialize the management VM." is displayed on the Install VM page.

Possible cause: After you log in to the VRM VM or VRM host using SSH and invoke the shell
script, the script fails to invoke due to network interruption.
Solution:
1. View the log.
The failure is caused by network interruption if the log contains the following operation:
System.Net.Sockets.SocketException (0x80004005): A connection attempt failed
because the connected party did not properly respond after a period of time,
or established connection failed because connected host has failed to respond.
2. After the network is reconnected, click Previous on the wizard and then click Next to
switch to the Install VM page again.
"Initialize the management VM timeout." is displayed on the Install VM page.

l Possible cause: Active and standby VRM nodes failed to be configured.
Solution: For details, see "Failed to Configuring active and standby nodes." is displayed
on the Install VM page.
l Possible cause: The management node VM failed to be initialized.
Solution: For details, see "Failed to initialize the management VM." is displayed on the
Install VM page.
"Failed to Uninstall component." is displayed on the Install VM page.

Possible cause: Stop VRM service timeout.
Solution:
1. Run the sc query win_vrm command in the CLI to query the VRM service:
2. Check whether the VRM service is running:
l If yes, run the sc stop win_vrm command to stop the VRM service and go to Step 3.
l If no, go to Step 3.
3. Run the sc start win_vrm command to start the VRM service.
4. Click Previous on the wizard and then click Next to switch to the Install VM page.
"Failed to query Vms." is displayed on the Install VM page.

Possible cause: The VRM service is not started.
Solution:
1. Run the sc start win_vrm command in the CLI to start the VRM service.
2. Click Previous on the wizard and then click Next to switch to the Install VM page.

FusionCompute
A.1.14 Creating a FusionCompute Tablespace in an Oracle

Database
Scenarios
Before deploying FusionCompute data services on an independent Oracle database, create a
FusionCompute tablespace and users who can access and use the tablespace.
The system of this version supports only the Oracle 11g R2 database.
You are advised to create a dedicated instance in the Oracle database for FusionCompute, so
that FusionCompute does not compete database resources with other database services, thereby
preventing deteriorating FusionCompute performance.
NOTE
When creating the instance in the database for FusionCompute, set the character set to AL32UTF8 to allow
the Oracle database to support multiple languages.
After the database instance is created, you can run the following command to check whether the character
set is set successfully:
select value from v$NLS_PARAMETERS where parameter = 'NLS_CHARACTERSET';
Prerequisites
l You have obtained the IP address of the Oracle database server.
l You have obtained the password of user oracle for logging into the Oracle database server.
Procedure
Log in to the Oracle database.
You can use any available method to log in to the Oracle database. This step describes how to
log in to the Oracle database using PuTTY in Secure Shell (SSH) mode.
1 Use PuTTY to log in to the Oracle database server.

Ensure that the server IP address and username oracle are used to establish the connection.
2 Run the following command to enter the database operation view:
sqlplus /nolog
3 Run the following command to connect to the database as database administrator sysdba:
connect /as sysdba
Create a FusionCompute tablespace.
4 Run the following command to create a FusionCompute tablespace:

CREATE TABLESPACE VRM DATAFILE 'Path to the database/Tablespace name'
SIZE 30G AUTOEXTEND ON NEXT 10M MAXSIZE UNLIMITED LOGGING
EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO;
– Path to the database indicates the path to the tablespace to be created in the database.
This path can be a absolute path in the database or an automatic storage management
(ASM) disk group.

FusionCompute
The format of an absolute path is /home/oracle/db, and the format of an ASM disk
group is +DATADisk group name, for example, +DATA. + indicates that the disk group
is enabled.
– Tablespace name indicates the VRM tablespace name, which can be customized.
The tablespace name format is Name+.dbf, for example, vrm.dbf.
For example, to create a tablespace named vrm.dbf in the ASM disk group DATA, run the
following command:
CREATE TABLESPACE VRM DATAFILE '+DATA/VRM.DBF' SIZE 30G

AUTOEXTEND ON NEXT 10M MAXSIZE UNLIMITED LOGGING EXTENT
MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO;
NOTE
Before you create a tablespace, ensure that the disk space is sufficient.
Create users who can access the FusionCompute tablespace.

5 Run the following command to create the user named fc_vrm:
CREATE USER "FC_VRM" IDENTIFIED BY "SingleLOUD!1" DEFAULT
TABLESPACE VRM ACCOUNT UNLOCK;
User fc_vrm can manage Virtualization Resource Management (VRM) services.

6 Run the following commands to grant tablespace operation permission to user fc_vrm:
GRANT CONNECT,RESOURCE TO "FC_VRM";
GRANT CREATE VIEW TO "FC_VRM";

7 Run the following command to create the user named omcommon:
CREATE USER OMCOMMON IDENTIFIED BY "SingleLOUD!1" DEFAULT
User omcommon can manage alarm Simple Network Management Protocol (SNMP) and
alarm dump services in the FusionCompute system.
8 Run the following command to grant tablespace operation permission to user
omcommon:
GRANT CONNECT,RESOURCE TO OMCOMMON;
9 Run the following command to create the user named sm:
CREATE USER SM IDENTIFIED BY "SingleLOUD!1" DEFAULT TABLESPACE
VRM ACCOUNT UNLOCK;
User sm can manage other users in the FusionCompute system.

10 Run the following command to grant tablespace operation permission to user sm:
GRANT CONNECT,RESOURCE TO SM;
11 Run the following command to create the user named cm:
CREATE USER CM IDENTIFIED BY "SingleLOUD!1" DEFAULT
User cm can manage the FusionCompute configuration channel tablespace.

12 Run the following command to grant tablespace operation permission to user cm:
GRANT CONNECT,RESOURCE TO CM;

FusionCompute
13 Run the following command to create the user named tm:

CREATE USER TM IDENTIFIED BY "SingleLOUD!1" DEFAULT TABLESPACE
VRM ACCOUNT UNLOCK;
User tm can manage the FusionCompute task management tablespace.
14 Run the following command to grant tablespace operation permission to user tm:
GRANT CONNECT,RESOURCE TO TM;
15 Run the following command to create the user named lm:
CREATE USER LM IDENTIFIED BY "SingleLOUD!1" DEFAULT TABLESPACE
VRM ACCOUNT UNLOCK;
User lm can manage the FusionCompute license service tablespace.
16 Run the following command to grant tablespace operation permission to user lm:
GRANT CONNECT,RESOURCE TO LM;
17 Run the following command to create the user named olm:
CREATE USER OLM IDENTIFIED BY "SingleLOUD!1" DEFAULT
User olm can manage the FusionCompute internal log service tablespace.
18 Run the following command to grant tablespace operation permission to user olm:
GRANT CONNECT,RESOURCE TO OLM;
19 Run the following command to create the user named pms:
CREATE USER PMS IDENTIFIED BY "SingleLOUD!1" DEFAULT
User pms can manage the FusionCompute monitoring service tablespace.
20 Run the following command to grant tablespace operation permission to user pms:
GRANT CONNECT,RESOURCE TO PMS;
21 Run the following command to create the user named omm:
CREATE USER OMM IDENTIFIED BY "SingleLOUD!1" DEFAULT
User omm can manage FusionCompute alarms, events, and email service tablespace.
22 Run the following command to grant tablespace operation permission to user omm:
GRANT CONNECT,RESOURCE TO OMM;
----End
Delete a database tablespace user.
You can perform the following operations to delete a database tablespace user
(FusionCompute service will be affected due to the user deletion):
1 Log in to the active VRM node and run the following command to stop the VRM process:
service vrmd stop
2 Log in to the Oracle database server, connect to the database, and run the following
command to delete the target user:
DROP USER Target user name CASCADE

FusionCompute
To delete user omm, for example, you can run the follow command:
DROP USER OMM CASCADE
----End
A.1.15 Recommended Configurations for Host Domain 0

Specifications
During the host installation, host Domain 0 has two vCPUs and 3 GB memory by default.
Software commissioning engineers need to configure the host Domain 0 specifications
depending on the application scenarios. Table A-1 lists the recommended configurations for
Domain 0 in different application scenarios.
Table A-1 Domain 0 specifications
Domain 0 Specifications Application Scenario
l Two vCPUs Default configuration. The configuration applies to

l 3 GB memory most computing-intensive, low network bandwidth,
and low storage bandwidth scenarios.
l Six vCPUs (maximum, two are The configuration is recommended for 10GE
reserved) networks and applies to the scenarios requiring high
l 4 GB memory network bandwidth.
l Four vCPUs The configuration is recommended for enabling I/O

l 5 GB memory rings and applies to the scenarios requiring high
storage bandwidth.
l Two vCPUs The configuration is recommended for host disaster

l 3 GB to 7 GB memory (memory recovery (DR).
scaling)
l Two vCPUs The configuration can be selected depending on the

l 3 GB memory block storage or virtualized storage in use.
or l Block storage: attach 256 data stores when

Domain 0 has two vCPUs and 3 GB memory.
l Six vCPUs
l Virtualized storage:
l 6 GB memory
– Scan 256 data stores and attach 64 data stores
when Domain 0 has two vCPUs and 3 GB
memory.
– Attach 256 data stores when Domain 0 has six
vCPUs and 6 GB memory.
A.1.16 Background Information

FusionCompute
Storage Resources
The FusionCompute can use storage resources provided by dedicated storage devices or local
disks on hosts. Dedicated storage devices are connected to hosts through network cables or fiber
cables.
Data Store
A data store is a storage unit that is converted from a storage resource by FusionCompute. After
a data store is associated with a host, the data store can be used to create virtual disks for VMs.
Raw device mapping (RDM) allows logical unit numbers (LUNs) on SAN devices can serve as
data stores without creating virtual disks. This technology applies to large disk capacity
scenarios, for example, the database server construction. RDM can be used only for VMs that
run certain operating systems (OSs), such as Red Hat Linux Enterprise 5.4/5.5/6.1/6.2 64-bit.
For details about the supported OS list, see the OS description for PVSCSI in the FusionAdaptor
Compatibility List. To download the FusionAdaptor Compatibility List, visit http://
support.huawei.com/enterprise and choose Product Support > Cloud Computing & Data
Centers > FusionCloud > FusionSphere > FusionAdaptor. If RDM storage is used to deploy
application cluster services, such as Oracle RAC, it is recommended that you not use the VM
snapshot creation function and not restore a VM using a snapshot. If you use a snapshot to restore
a VM, the application cluster service may become faulty.
After storage resources are converted to data stores, the difference between virtual disks created
using different resources are hidden from VM OSs.
Storage resources that can be converted to data stores are:

l LUNs on SAN devices, including Internet Small Computer Systems Interface (iSCSI)
storage devices and fiber channel (FC) storage devices.
l File systems on NAS devices.
l Storage pools on FusionStorage
l Local hard disks on hosts
l Local RAM disk on hosts
Table A-2 shows the relationship between data resources, storage devices and data stores.

FusionCompute
Table A-2 The storage devices, storage resources, and data stores support for the FusionCompute
Storage Storage Data Store Storage Space

Device Resource Required By Data
Store
Local N/A Local (Non-virtualization) Local: ≥2 GB

Local Pome Local Pome: [2 GB, 16
(Virtualization) TB)
NOTE
The remaining space on the
local disk where the host OS
is installed can be added as a
data store of the local
storage type. If the space of
the disk is greater than 2 TB,
the system identifies the disk
only as a 2 TB disk during
the host OS installation
process. Therefore, the
remaining space on this disk
after the OS installation is
less than 2 TB. Other local
disks on the host are not
affected by the OS
installation. Therefore, they
can provide all of their
space.
SAN device (IP SAN SAN (Non-virtualization) SAN: ≥ 2 GB

SAN or FC LUN Pome LUN Pome: [5 GB, 96 TB]
SAN) (Virtualization) NOTE
RDM (Raw device After a logical unit number
(LUN) on virtualized SAN
mapping)
storage (LUN Pome) is
added as a data store, the
Virtual Image Management
System (VIMS) takes up
about 4 GB storage space on
the data store. Therefore, the
actual available storage
space of the data store is less
than that of the LUN.
RDM: ≥ 2 GB
Advanced SAN Advanced Advanced SAN device Not limited

device SAN device
NAS NAS NAS
FusionStorage FusionStorage FusionStorage
Local RAM N/A Local RAM disk (non- Local RAM disk: [16 GB,
disk virtualization) 512 GB]

FusionCompute
Figure A-8 Data store association model
Data store association

RDM
VMs
File systems
Virtual disks
NAS devices
Hosts LUN
Data stores LUN
Local disks on hosts

SAN devices
Storage Port
A storage port on a host connects the host to a storage device. One physical NIC or a group of
physical NICs that are bound together on the host can be set as a storage port.
If iSCSI storage devices are used, two physical NICs on a host can be connected to multiple
storage NICs on the storage devices, working in multipathing mode. Binding of physical NICs
is not required in this mode.
If NAS devices are to be used, you are advised to bind the storage plane NICs in active/standby
mode and set the storage port to connect to the NAS devices to enhance reliability.
iSCSI Storage
An iSCSI storage device is connected to a host through network cables. The host accesses the
storage device using the TCP/IP protocol.
To ensure efficient access to an iSCSI storage device, configure an iSCSI initiator using the
world wide name (WWN) generated after the storage device is associated to the host.
Typical iSCSI storage devices include IP SAN devices and OceanStor 18000 series storage
devices.
FC Storage
An FC storage device is connected to the FC host bus adapter (HBA) on a host through optical
cables, which provide high data transmission rate.
To ensure efficient access to an FC storage device, configure an FC initiator using the WWN
generated after the storage device is connected to the host FC HBA.
Typical FC storage devices include FC SAN devices and OceanStor 18000 series storage
devices.

FusionCompute
Multipathing
Multipathing is a storage access mechanism that provides more than one physical path to connect
a network storage device to one or more host network interface cards (NICs), enabling load
sharing for data flows and thereby enhancing reliability for storage access.
Usually, multipathing is supported by storage devices using iSCSI and Fibre Channel (FC), such
as IP SAN devices, FC SAN devices, and OceanStor 18000 series storage devices.
Sample Multipathing Networking

This section uses Huawei OceanStor S5500T in Figure A-9 as an example to describe the
multipathing networking. The storage device in Figure A-9 has two controllers, A and B. Each
controller controls four storage NICs. The four NICs are assigned four VLANs, which constitute
the storage plane.
On a host, two NICs connect to the storage plane. Each host NIC communicates with two storage
NICs. In this case, two storage ports are required to be configured for each host NIC.
Figure A-9 Sample multipathing networking

IP SAN
VLAN 4 Controller A
172.20.10.10
Host
VLAN 5
172.30.10.10
VLAN 6
Eth2 172.40.10.10
172.20.100.100
172.30.100.100 VLAN 7
172.50.10.10
Eth3 VLAN 4 Controller B

172.20.10.11
172.40.100.100
172.50.100.100 VLAN 5
172.30.10.11
VLAN 6
172.40.10.11
VLAN 7
172.50.10.11
The IP addresses shown in the figure are only used as examples.
NAS Storage
NAS storage devices use the network file sharing (NFS) protocol to provide shared folders over
a network.
A NAS storage device is connected to a host through network cables. A host accesses the storage
device using TCP/IP.

FusionCompute
Local Storage
Disks on hosts provide local storage resources.
The FusionCompute can identify the following local storage resources:

l Free space on the disk on which the host operating system is installed
NOTE
The remaining space on the local disk where the host OS is installed can be added as a data store of
the local storage type. If the space of the disk is greater than 2 TB, the system identifies the disk only
as a 2 TB disk during the host OS installation process. Therefore, the remaining space on this disk
after the OS installation is less than 2 TB. Other local disks on the host are not affected by the OS
installation. Therefore, they can provide all of their space.
l Bare disks or unpartitioned redundant array of independent disks (RAID) on the host
Local storage can be provided only to the host housing the disks.
Local RAM Disk

A local random access memory (RAM) disk is generated from memory resources on a host and
provides storage resources for VMs only on the host.
For details about adding local RAM disks on a host, see Creating Local RAM Disks on a Host.
Communication Planes
The FusionCompute system consists of the following communication planes:
l Management plane: provides a communication plane to implement system monitoring,
operation and maintenance (including system configuration, system loading, and alarm
reporting), and VM management (such as creating, deleting, and scheduling VMs).
l Storage plane: provides a communication plane for the storage system and storage resources
for VMs. This plane is used for storing and accessing VM data (including data in the system
disk and user disk of VMs).
l Service plane: provides a plane for virtual network interface cards (VNICs) of VMs to
communicate with external devices.
Figure A-10, Figure A-11, and Figure A-12 show the communication between planes in the
FusionCompute system.
NOTE
This section uses IP storage area network (SAN) devices as an example to describe how storage devices
in the FusionCompute system communicate with other planes.

FusionCompute
Figure A-10 Communication between planes (two NICs)
VRM
eth0
BMC
eth1
Management
Service plane
plane
Host eth0
SAN
BMC
Storage A1～A4
eth1
plane B1～B4
Figure A-11 Communication between planes (four NICs)
VRM
eth0
BMC
Management
Service plane
plane
Host eth1
eth0
SAN
BMC Storage A1～A4

eth2
plane B1～B4
eth3

FusionCompute
Figure A-12 Communication between planes (six NICs)
VRM
eth0
BMC
Management
Service plane
plane
eth4 eth5
Host bond0
eth0 SAN
eth1
Storage A1～A4
BMC eth2
plane B1～B4
eth3
NOTE
VLAN Planning Rules

Table A-3, Table A-4 and Table A-5 list the virtual local area network (VLAN) plan for the
planes.
Table A-3 VLAN plan (two NICs)
Pla Network Ports VLAN Planning Rules

ne
Man Network port eth0 on The network port eth0 on each node are assigned to the
age the host management plane VLAN, which then become the default
men VLAN of the management plane.
t Network port eth0 on
plan the active and standby
e Virtualization
Resource
Management (VRM)
nodes

FusionCompute

ne
BMC network ports The switch port connected to the BMC network port on each
on the VRM and host node is assigned to the BMC plane VLAN, which then
becomes the of the default VLAN for the BMC plane.
NOTE
The BMC network ports can be assigned to an independent BMC
plane or to the same VLAN as management network ports. The
specific assignment depends on the actual network plan.
Stor Storage network ports The storage plane is divided into four VLANs:
age A1, A2, A3, A4, B1, l A1 and B1 are assigned to VLAN 1.
plan B2, B3, and B4 on the
l A2 and B2 are assigned to VLAN 2.
e SAN storage devices
Storage network port l A4 and B4 are assigned to VLAN 4.
eth1 on the host
l eth1 is assigned to VLAN 1, VLAN 2, VLAN 3 and
VLAN 4.
Serv Service network port The service plane is divided into multiple VLANs to isolate
ice eth0 on the host VMs. All data packets from different VLANs are forwarded
plan over the service network ports on the CNA. The data packets
e are marked with VLAN tags and sent to the service network
port of the switch on the access layer.
Table A-4 VLAN plan (four NICs)

ne
e VRM nodes
NOTE

FusionCompute

ne
Storage network ports l A4 and B4 are assigned to VLAN 4.

eth2 and eth3 on the l eth2 is assigned to VLAN 1 and VLAN 2.
host
l eth3 is assigned to VLAN 3 and VLAN 4.
The network port eth2 can communicate with ports A1, A2,
B1, and B2 over the layer 2 network. The network port eth3
can communicate with ports A3, A4, B3, and B4 over the
layer 2 network. This allows computing resources to access
storage resources through multiple paths. (Each computing
server has eight Internet Small Computer Systems Interface
(iSCSI) links to connect to the same storage device.)
Therefore, the storage network reliability is ensured.
Table A-5 VLAN plan (six NICs)
Pl Network Ports Virtual VLAN Planning Rules

an Network
e Port
Ma Network ports bond0 The network ports eth0 and eth1 on each node are
na eth0 and eth1 on assigned to the management plane VLAN, which
ge the host then become the default VLAN of the management
me plane.
nt Network port eth0 -
pla on the active and
ne standby VRM
nodes
BMC network - The switch port connected to the BMC network

ports on the VRM port on each node is assigned to the BMC plane
and host VLAN, which then becomes the of the default
VLAN for the BMC plane.
NOTE
The BMC network ports can be assigned to an
independent BMC plane or to the same VLAN as
management network ports. The specific assignment
depends on network planning.

FusionCompute

an Network
e Port
Sto Storage network - The storage plane is divided into four VLANs:
rag ports A1, A2, A3, l A1 and B1 are assigned to VLAN 1.
e A4, B1, B2, B3,
pla and B4 on the
ne SAN storage l A3 and B3 are assigned to VLAN 3.
devices l A4 and B4 are assigned to VLAN 4.
Storage network -
ports eth2 and l eth3 is assigned to VLAN 3 and VLAN 4.
eth3 on the host The network port eth2 can communicate with ports
A1, A2, B1, and B2 over the layer 2 network. The
network port eth3 can communicate with ports A3,
A4, B3, and B4 over the layer 2 network. This
allows computing resources to access storage
resources through multiple paths. (Each
computing server has eight iSCSI links to connect
to the same storage device.) Therefore, the storage
network reliability is ensured.
Ser Service network - The service plane is divided into multiple VLANs
vic ports eth4 and to isolate VMs. All data packets from different
e eth5 on the host VLANs are forwarded over the service network
pla ports on the CNA. The data packets are marked
ne with VLAN tags and sent to the service network
A.1.18 Compatibility
For details about the compatibility for servers, I/O devices, storage devices. and operating
systems (OSs), log in to compatibility check assistant.
Table A-6 lists OSs that support the PVSCSI.
Table A-6 OSs that support PVSCSI
Type OS
Windows Windows 2012 64-bit
Windows 2012 Standard R2 64-bit
Windows 2012 DataCenter R2 64-bit
Windows Server 2008 Enterprise R2 64-bit
Windows Server 2008 Enterprise R2 SP1 64-bit
Windows Server 2008 Standard R2 64-bit

FusionCompute
Type OS
Windows Server 2008 Standard R2 SP1 64-bit
Windows Server 2008 WEB R2 64-bit
Windows Server 2008 DataCenter R2 64-bit
Windows Server 2008 DataCenter R2 SP1 64-bit
Linux Red Hat Enterprise Linux 5.4/5.5 64-bit
Red Hat Enterprise Linux 6.1/6.2/6.3 64-bit
Communication Planes
The FusionCompute system consists of the following communication planes:
l Management plane: provides a communication plane to implement system monitoring,
operation and maintenance (including system configuration, system loading, and alarm
reporting), and VM management (such as creating, deleting, and scheduling VMs).
l Storage plane: provides a communication plane for the storage system and storage resources
for VMs. This plane is used for storing and accessing VM data (including data in the system
disk and user disk of VMs).
l Service plane: provides a plane for virtual network interface cards (VNICs) of VMs to
communicate with external devices.
Figure A-13, Figure A-14, and Figure A-15 show the communication between planes in the
FusionCompute system.
NOTE
This section uses IP storage area network (SAN) devices as an example to describe how storage devices
in the FusionCompute system communicate with other planes.

FusionCompute
Figure A-13 Communication between planes (two NICs)
VRM
eth0
BMC
eth1
Management
Service plane
plane
Host eth0
SAN
BMC
Storage A1～A4
eth1
plane B1～B4
Figure A-14 Communication between planes (four NICs)
VRM
eth0
BMC
Management
Service plane
plane
Host eth1
eth0
SAN
BMC Storage A1～A4

eth2
plane B1～B4
eth3

FusionCompute
Figure A-15 Communication between planes (six NICs)
VRM
eth0
BMC
Management
Service plane
plane
eth4 eth5
Host bond0
eth0 SAN
eth1
Storage A1～A4
BMC eth2
plane B1～B4
eth3
NOTE
VLAN Planning Rules

Table A-7, Table A-8 and Table A-9 list the virtual local area network (VLAN) plan for the
planes.
Table A-7 VLAN plan (two NICs)

ne
e Virtualization
Resource
Management (VRM)
nodes

FusionCompute

ne
NOTE
Storage network port l A4 and B4 are assigned to VLAN 4.
eth1 on the host
l eth1 is assigned to VLAN 1, VLAN 2, VLAN 3 and
VLAN 4.
Table A-8 VLAN plan (four NICs)

ne
e VRM nodes
NOTE

FusionCompute

ne
Storage network ports l A4 and B4 are assigned to VLAN 4.

eth2 and eth3 on the l eth2 is assigned to VLAN 1 and VLAN 2.
host
The network port eth2 can communicate with ports A1, A2,
B1, and B2 over the layer 2 network. The network port eth3
can communicate with ports A3, A4, B3, and B4 over the
layer 2 network. This allows computing resources to access
storage resources through multiple paths. (Each computing
server has eight Internet Small Computer Systems Interface
(iSCSI) links to connect to the same storage device.)
Therefore, the storage network reliability is ensured.
Table A-9 VLAN plan (six NICs)

an Network
e Port
Ma Network ports bond0 The network ports eth0 and eth1 on each node are
na eth0 and eth1 on assigned to the management plane VLAN, which
ge the host then become the default VLAN of the management
me plane.
nt Network port eth0 -
pla on the active and
ne standby VRM
nodes
BMC network - The switch port connected to the BMC network

ports on the VRM port on each node is assigned to the BMC plane
and host VLAN, which then becomes the of the default
VLAN for the BMC plane.
NOTE
The BMC network ports can be assigned to an
independent BMC plane or to the same VLAN as
management network ports. The specific assignment
depends on network planning.

FusionCompute

an Network
e Port
Sto Storage network - The storage plane is divided into four VLANs:
rag ports A1, A2, A3, l A1 and B1 are assigned to VLAN 1.
e A4, B1, B2, B3,
pla and B4 on the
ne SAN storage l A3 and B3 are assigned to VLAN 3.
devices l A4 and B4 are assigned to VLAN 4.
Storage network -
ports eth2 and l eth3 is assigned to VLAN 3 and VLAN 4.
eth3 on the host The network port eth2 can communicate with ports
A1, A2, B1, and B2 over the layer 2 network. The
network port eth3 can communicate with ports A3,
A4, B3, and B4 over the layer 2 network. This
allows computing resources to access storage
resources through multiple paths. (Each
computing server has eight iSCSI links to connect
to the same storage device.) Therefore, the storage
network reliability is ensured.
Ser Service network - The service plane is divided into multiple VLANs
vic ports eth4 and to isolate VMs. All data packets from different
e eth5 on the host VLANs are forwarded over the service network
pla ports on the CNA. The data packets are marked
ne with VLAN tags and sent to the service network
A.1.20 Binding Network Ports
Scenarios
On FusionCompute, bind network ports on a host to improve network reliability.
NOTE
If the host uses intelligent network interface cards (iNICs), bind the uplink network ports on the host together.
Otherwise, the broadcast suppression function of the port group may be adversely affected.
Prerequisites
Conditions
– You have logged in to FusionCompute.
– The host has been added to a cluster.
Procedure
Determine the method of binding network ports.

FusionCompute
1 Determine the method of binding network ports.

– To bind network ports in batches, go to Step 10.
This method is recommended when multiple bound ports are to be added to hosts or the
hosts are large in number.
– To bind network ports one by one, go to Step 2.
This method is recommended when the hosts are small in number and each host requires
a few bound ports.
Bind network ports one by one.
2 On FusionCompute, click Computing Pool.
3 In the navigation tree on the left, select the site, the cluster, and the host.
The Getting Started page is displayed.
4 Choose Configuration > System Port > Bind Network Port.
The Bind Network Port page is displayed, as shown in Figure A-16.
Figure A-16 Bind Network Port
5 In the Network Port list, select the physical network ports to be bound.
6 In the middle of the page, set Name and Binding Mode for the network ports.
NOTICE
l In all load sharing modes, aggregation must be configured on the switch to which
network ports are connected, that is, the ports to be bound must be configured on the
same Eth-trunk port on the switch. Otherwise, network exception may occur.
l In the Link Aggregation Control Protocol (LACP) mode, create an Eth-trunk in LACP
mode on the switch to which network ports are connected, configure ports to be bound
on the same Eth-trunk, and enable the bridge protocol data unit (BPTU) protocol packet
forwarding function on the Eth-trunk. For example, if the switch is Huawei S5300, run
the following commands:
<S5352_01>sys
[S5352_01]interface Eth-Trunk x
[S5352_01-Eth-Trunkx]mode lacp-static
[S5352_01-Eth-Trunkx]bpdu enable
For details about how to configure port aggregation on a switch, see the switch user guide.

FusionCompute
modes.
addresses.
the LACP protocol.
networks.

FusionCompute
addresses.
7 Click Bind.
8 Click OK.
The Bind Network Port page is displayed.
To change the binding mode of a bound port, locate the row that contains the bound port,
click Operation, and click Modifying binding mode. You can change the binding mode
in the displayed dialog box.

FusionCompute
NOTICE
l If the binding mode is changed from the active/standby mode to load sharing mode,
port aggregation must be configured on the switch to which network ports are connected.
If the binding mode is changed from the load sharing mode to active/standby mode, the
aggregation configured on the switch must be canceled. Otherwise, network exception
may occur.
l If the binding mode is changed from the LACP mode to another mode, port
configuration must be changed on the switch to which network ports are connected. If
the binding mode is changed from another mode to the LACP mode, port aggregation
in LACP mode on the switch. Otherwise, network exception may occur.
Configuration operations on the switch may interrupt the network communication. After
the configurations are complete, the network communication is automatically restored. If
the network communication is not restored, perform either of the following methods to
troubleshoot the network:
l Ping the destination IP address from the switch to trigger a MAX table update.
l Select a member port in port aggregation, disable other ports on the switch, change the
binding mode, and enable those ports.
9 Click OK.
The network ports on the host are bound.
After this step is complete, no further action is required.

Bind network ports in batches.
10 On FusionCompute, click Computing Pool.

11 In the navigation tree on the left, select the site and cluster.
The Getting Started page is displayed.
12 In the Operation list of the cluster, click Bind Network Ports in Batches.
The Bind Network Ports in Batches page is displayed, as shown in Figure A-17.
Figure A-17 Bind Network Ports in Batches

FusionCompute
13 Click Obtain the Bind Network Ports in Batches template file.

The page for downloading templates is displayed.
14 Save the template on the local PC.
The default file name of the template is BindNetworkPortYYYY-MM-DD
HHMMSSXXX.xls.
15 Open the template file and set the network port parameters on the Config sheet based on
the information provided on the Host_NetworkPort page.
The parameters include Host IP Address, Host ID, Network Port Name, Network Port
IDs, Bound Network Port Name, and Binding Mode.
16 Save and close the template file.
17 Click Browse on the right of Import template file on the Bind Network Ports in
Batches page.
18 Select the configured template file and click Open.
19 Click OK.
20 Click OK.
You can choose System > Tasks and Logs > Task Center to view the task progress.
----End
Related Tasks
Removing a Default Network Port from a Bound Port
The default network port is the first port added to the bound port. To remove the default port,
unbind the bound port and then bind the other non-default member ports. If the bound port is
used by any services, you must remove the services first.
1. Locate the row that contains the bound port, choose More > Unbind Port, and check
whether The network port aggregation is in use is displayed.
– If yes, the bound port is in use. Go to 2.
– If no, go to 7.
2. Switch to the page for the host, choose Configuration > System Port, and check whether
the bound port is used as a storage port or a service management port or not.
– If no, go to 4.
3. Migrate all the VMs from the host to other hosts or stop all the VMs on the host, disassociate
all the virtualized SAN storage from the host, and delete the storage port or service
management port from the bound port.
4. In Network Pool, select the uplink of the DVS and check whether the bound port is used
by the uplink.
– If no, go to 6.

FusionCompute
5. Delete the uplink. If the uplink is used by VMs, migrate the VMs to other hosts or delete
the VM NICs, and then delete the uplink.
6. Locate the row that contains the bound port and choose More > Unbind Port.
7. Bind the other member ports of the bound port other than the default port.
8. If you remove the services on the original bound port before you unbind the port, restore
the services on the newly bound port, for example, creating the system interface on the
bound port, associating with the uplink, and migrating the original VMs back to the host.
A.1.21 How to Handle FusionCompute Installation Failures Caused

by a Change in the Local IP Address
Symptom
The installation of the FusionCompute using the installation wizard failed because the IP address
of the local PC was changed.
Possible Causes
The IP address of the local PC was reassigned or manually changed.
Procedure
1 Close the FusionCompute installation wizard.

2 In the root directory where the FusionCompute installation wizard is located, open
changeVrmip.bat in CloudComponents\bin\lib.
3 Enter the IP address of the local PC as instructed, and press Enter.
4 Run the installation wizard again to install the FusionCompute.
----End
A.2 Common Operations
A.2.1 Setting Internet Explorer Browser
A.2.2 Setting Mozilla Firefox Browser
A.2.3 Logging In to FusionCompute
A.2.4 Verifying Software Packages
A.2.1 Setting Internet Explorer Browser
Scenarios
Set Internet Explorer browser before logging in to FusionCompute the first time. After the
setting, you can use Internet Explorer to perform operations on FusionCompute.

FusionCompute
This section uses Internet Explorer 9.0 as an example to describe how to configure Internet
Explorer settings.
If you have configured Internet Explorer, do not configure Google Chrome, because Google
Chrome inherits all the Internet Explorer settings, such as certificate settings.
NOTE
If the security certificate has not been installed during Internet Explorer configuration, the browser may
prompt users with a web page display exception message when they log in to FusionCompute for the first
time or log in to VMs using Virtual Network Computing (VNC). In this case, press F5 to refresh the web
page.
Prerequisites
Conditions
– The Internet Explorer browser used for logging in to FusionCompute is an official release
from Internet Explorer 9.0 to Internet Explorer 11.0.
– You have obtained the IP address of the VRM node.
Data
Procedure
Enter the login page.
1 Open Internet Explorer.
2 Enter http://IP address of the VRM node and press Enter.
NOTE
l If the local PC uses the Windows Server 2003 or Windows XP operating system (OS), connection
to FusionCompute from the PC using the Hypertext Transfer Protocol Secure (HTTPS) protocol
may file. In such cases, if the connection is triggered through an Internet Explorer browser, the
PC prompts the user to choose a digital certificate. If the connection is triggered through a Google
Chrome browser, the PC displays a message indicating that the server certificate is invalid. To
address this issue, see http://support.microsoft.com/kb/968730/zh-cn.
l The HTTPS protocol used by FusionCompute supports only TLS 1.0. If SSL 2.0, SSL 3.0, TLS
1.1, or TLS 1.2 is used, the FusionCompute system cannot be accessed. You must open the
browser, choose Internet Options > Advanced > Security, and select only Use TLS 1.0 among
the protocols.
l If Internet Explorer slows down after running for a period of time and no data is required to be
saved, press F6 on the current page to move the cursor to the address bar of the browser. Then,
press F5 to refresh the page and increase the browser running speed.
3 Click Continue to this website (not recommended).
In common mode, the FusionCompute login page is displayed, as shown in Figure A-18.
In single sign-on (SSO) mode, the FusionManager login page is displayed, as shown in
Figure A-19.

FusionCompute
Figure A-18 FusionCompute login page

FusionCompute
Figure A-19 FusionManager login page
Install the security certificate.

4 In the address box of Internet Explorer, click Certificate Error and click View
certificates in the dialog box displayed.
The Certificate dialog box is displayed.
5 Click Install Certificate.
The Certificate Import Wizard dialog box is displayed.
6 Click Next.
The Certificate Store dialog box is displayed.
7 Select Place all certificates in the following store and click Browse.
The Select Certificate Store dialog box is displayed.
8 Select Trusted Root Certification Authorities and click OK.
The Certificate Store dialog box is displayed.
9 Click Next.
The Completing the Certificate Import Wizard dialog box is displayed.
10 Click Finish.
The Security Warning dialog box is displayed.
11 Click Yes.

FusionCompute
The system displays "The import was successful."

12 Click OK.
13 Click OK in the Certificate dialog box.
The browser page is displayed.
Delete historical data.
14 Press Ctrl+Shift+Delete.
The Delete Browsing History dialog box is displayed.
15 Select the following options:
– Preserve Favorites website data
– Temporary Internet files
– Cookies
– History
16 Click Delete.
Historical data is deleted.
Configure compatibility view settings.
17 On the right upper part of the browser, choose Tools > Compatibility View Settings.
The Compatibility View Settings dialog box is displayed.
18 Click Add.
The address for logging in to the current system is added to the compatibility view.
19 Click Close.
20 Close Internet Explorer, open it again, and log in to the FusionCompute.
The settings take effect after the browser is restarted.
----End
A.2.2 Setting Mozilla Firefox Browser
Scenarios
Set Mozilla Firefox browser before logging in to the FusionCompute the first time. After the
setting, you can use Firefox browser to perform operations on the FusionCompute.
Prerequisites
Conditions
– The Firefox browser used for logging in to FusionCompute is an official release from
Mozilla Firefox 21.0 to Mozilla Firefox 30.0.
– You have obtained the floating IP address of the VRM.
Data
Procedure

FusionCompute
1 Open Mozilla Firefox.

2 Enter http://VRM node IP address and press Enter.
3 Expand I Understand the Risks and click Add Exception.
The Add Security Exception window is displayed.
4 Verify that Permanently store this exception is selected and click Confirm Security
Exception.
Mozilla Firefox setting is complete.
----End
A.2.3 Logging In to FusionCompute
Scenarios
Log in to FusionCompute to manage virtual, service, and user resources in a centralized manner.
Prerequisites
Conditions
– The browser for logging in to FusionCompute is available.
– The Internet Explorer or Mozilla Firefox is set properly. For details, see Setting Internet
Explorer Browser in the FusionCompute V100R005C00 Software Install Guide or
FusionCompute V100R005C00 Software Install Guide.
– The browser resolution is set to 1280 x 1024 or higher based on the service requirement to
ensure the optimum display effect on the FusionCompute.
NOTE
If the security certificate has not been installed during Internet Explorer configuration, the browser may
prompt users with a web page display exception message when they log in to FusionCompute for the first
time or log in to VMs using Virtual Network Computing (VNC). In this case, press F5 to refresh the web
page.
The system supports the following browsers:
l Internet Explorer 9.0 to Internet Explorer 11.0
l Mozilla Firefox 21.0 to Mozilla Firefox 30.0
l Google Chrome 21.0 to Google Chrome 35.0
Data
Table A-10 lists the data required for performing this operation.

FusionCompute
Table A-10 Data required for performing this operation
Parameter Description Example Value
IP address of the VRM Specifies the floating IP 192.168.40.3

node address of the Virtual Resource
Management (VRM) nodes if
the VRM nodes are deployed in
active/standby mode, or the
management IP address of the
VRM node if only one VRM
mode is deployed.
Username/Password Specifies the username and In common mode, the

password used for logging in to username and password are
FusionCompute. admin/
Huawei@CLOUD8!.
In rights separation mode, the
username and password is as
follows:
l sysadmin/Sysadmin#
for a system administrator
l secadmin/Secadmin#
for a security
administrator
l secauditor/Secauditor#
for a security auditor
User type Specifies the type of the user to Local user

log in to the system.
Value:
l Local user: logs in to the
system using a local
username and password.
l Domain user: logs in to the
system using a domain
username and password.
Login type Specifies the login type. Local

Value:
l Local: used to log in to the
FusionCompute of the
current site.
l VRM domain: used to log in
to the FusionCompute of
any site using the VRM
domain username.

FusionCompute
Procedure
1 Open Internet Explorer.

2 Enter http://VRM node IP address and press Enter.
If two VRM nodes are deployed, the IP address is the floating IP address of the VRM nodes.
If only one VRM node is deployed, the IP address is the management IP address of the
VRM mode.
NOTE
If Internet Explorer slows down after running for a period of time and no data is required to be saved,
press F6 on the current page to move the cursor to the address bar of the browser. Then, press F5 to
refresh the page and increase the browser running speed.
After the SSO is configured, if you open the login page of the FusionCompute, the system
switches to the login page of the FusionManager. However, multiple users cannot log in to
the FusionCompute using the same account.
3 Perform the required operation based on the login page.
– If the FusionCompute login page shown in Figure A-20 is displayed, single sign-on
(SSO) is not configured. Go to Step 4.
– If the FusionManager login page shown in Figure A-21 is displayed, SSO has been
configured. Go to Step 5.

FusionCompute
Figure A-20 FusionCompute login page

FusionCompute
Figure A-21 FusionManager login page
4 Set the Username and Password, select the required User type and Login type, and click
Login. If you attempt to log in to the system again after the initial login fails, you also need
to set the Verification code.
Enter the username and password based on the rights management mode configured during
VRM installation.
– Common login mode: The initial login username is admin and the password is
Huawei@CLOUD8!.
– Rights separation login mode: The username and password of the system administrator
is sysadmin/Sysadmin#, the username and password of the security administrator is
secadmin/Secadmin#, and the username and password of the security auditor is
secauditor/Secauditor#.

FusionCompute
NOTE
l If it is your first login using the admin username, the system asks you to change the password
of the admin username.
l The new password must meet the following requirements:
l It contains a minimum of eight characters and a maximum of 32 characters.
l It contains at least one space or one of the following special characters: `~!@#$%^&*()-_=
+\|[{}];:'",<.>/?.
l It contains at least two of the following character types:
l Uppercase letters
l Lowercase letters
l Digits
The FusionCompute operation page is displayed after you log in to the system.
The login operation is complete.
5 Set the Username, Password, and Verification code.
– Common login mode: Log in to the system using the FusionManager system account.
After the login, you can only perform query-related operations.
– Rights separation login mode: The username and password of the system administrator
is sysadmin/Sysadmin#, the username and password of the security administrator is
secadmin/Secadmin#, and the username and password of the security auditor is
secauditor/Secauditor#.
6 Click Login.
The FusionCompute operation page is displayed.
----End
A.2.4 Verifying Software Packages
Scenarios
To prevent the carrier's network from being attacked by software packages that are maliciously
modified or destroyed during transfer, verify the integrity of software packages after
downloading them. Software packages can be deployed only after their integrity is verified.
There is a one-to-one mapping between a software package and a signature file. A signature file
is an asc file generally named after a software package. For example, the signature file for the
software package V100R001C04.zip is V100R001C04.zip.asc.
Procedure
Step 1 Login to http://support.huawei.com/enterprise.
Step 2 Download OpenPGP Signature Verification Guide.
The download path is http://support.huawei.com/enterprise/toolsinfo?

idAbsPath=0602_ROOT|
8221819&pid=8221819&show=showServiceDetail&versionid=TV1000000016.
Step 3 Verifying the software package integrity by referring OpenPGP Signature Verification Guide.
----End

FusionCompute
Software Installation Guide B Glossary
B Glossary
B.1 A-E
B.2 F-J
B.3 K-O
B.4 P-T
B.5 U-Z

FusionCompute
B.1 A-E
A
active directory A directory service created by Microsoft for Windows domain networks. It is included
in most Windows Server operating systems, such as Windows Standard Server, Windows
Enterprise Server, and Windows Datacenter Server.
AD See active directory
B
bare VM A VM that has an identity but does not occupy any CPU, memory, storage, or network
resource in the system.
Baseboard A dedicated micro controller embedded in the main board of a computer (especially a
Management server).
Controller
BMC See Baseboard Management Controller
C
CBT See Changed Block Tracking
Changed Block An incremental data backup function. With this function enabled, the system uses a
Tracking bitmap to keep track of VM storage blocks as they change following the last backup.
Therefore, the system only backs up the data blocks that have been changed since the
last backup.
CNA See Computing Node Agent
Computing Node Agent This is deployed on a computing node and used to manage the VMs and VM mounting
on the computing node.
D
disk The logical storage disk of a VM, which can either be a system disk or user disk.
distributed virtual A virtual switch (created on a physical server) that uses software to implement data
switch switching between VMs on the same or different servers.
Distributed Virtual A module used to manage distributed virtual switches (DVSs). Deployed in the same
Switch Management cluster with the Virtual Resource Management (VRM) node, the DVSM creates, deletes,
maintains, and presents DVSs in the system. Each cluster has a DVSM module.
Dom0 See Domain 0
Domain Domain includes Dom0 and DomU.
Domain 0 A modified Linux kernel and the only VM that operates on the Xen Hypervisor. Dom0
can access physical I/O resources and interwork with other VMs operating on the system.
Dom0 must be started before other domains.

FusionCompute
Domain U Paravirtualized VMs operating on the Xen Hypervisor are called Domain U PV Guests,
which supports the operating system whose kernel has been modified, such as Linux,
Solaris, FreeBSD, and other UNIX operating systems. Fully virtualized VMs are called
Domain U HVM Guests, which supports the operating system whose kernel does not
need to be modified, for example, Windows.
DomU See Domain U
DPM See Dynamic Power Management
DRS See Dynamic Resource Scheduler
DVS See distributed virtual switch
DVSM See Distributed Virtual Switch Management
Dynamic Power A module that intelligently powers on or off idle physical servers based on the system
Management load on the network.
Dynamic Resource A module that uses intelligent scheduling algorithms to flexibly schedule resources and
Scheduler dynamically balance system load to improve user experience.
Elastic Load Balancer A component that provides load balancing services for tenants. End users can apply for
an ELB and associate their hosts with the ELB. The ELB evenly distributes service
requests to the associated hosts based on customized load balancing policies. The ELB
helps improve service stability and reliability.
Elastic Service A point from which to control VM resources and virtual block storage resources. It
Controller provides an open ECi interface.
elastic virtual switch A virtual switch that implements data switching, virtual local area network (VLAN)
isolation, Dynamic Host Configuration Protocol (DHCP) isolation, bandwidth limiting,
and priority setting.
ELB See Elastic Load Balancer
Equipment Serial This uniquely identifies a set of equipment.
Number
ESC See Elastic Service Controller
ESN See Equipment Serial Number
EVS See elastic virtual switch
B.2 F-J
F
FCSAN See fibre channel storage area network

fiber channel storage A type of storage area network (SAN) that uses fiber channels between servers and
area network storage devices. FC SAN devices provide high performance but high costs, and are
gradually replaced by IP SAN devices.

FusionCompute
full clone Full copy of the consolidated sum of delta disks and base disk of a virtual machine. Each
full clone is entirely separated from the parent VM and can have different system disks
or software from the parent VM. Full clones apply to common office automation
scenarios.
G
GPU See graphics processing unit
graphics processing A specialized electronic circuit designed to accelerate the building of three dimensional
unit and special-effect images. A GPU works for a video card as a CPU works for a computer.
Guest OS See guest OS
guest OS An OS running on a VM.
H
hierarchical storage A storage mechanism that stores the most-frequently accessed IP SAN data on a solid-
state drive (SSD) to speed up access, stores the less-frequently accessed data on a Serial
Attached SCSI (SAS) drive, and stores the seldom accessed data on a Serial Advanced
Technology Attachment (SATA) drive.
Host A physical server that runs virtual software. VMs can be created on a host.
Hypervisor The software layer on a virtual server, which manages the VMs on the server and helps
VMs share the hardware resources of the virtual server. The Xen Hypervisor is a software
layer between the hardware and operating system, which performs CPU scheduling and
partitioning between VMs. The Xen Hypervisor controls VM migration between
hardware devices and other VM-related operations (because the VMs share a processing
environment). The Xen Hypervisor does not process networks, storage devices, videos,
or other I/O resources.
I
Image An exact copy of all running software on a server used for quick installation of the VM
operating system and software.
iNIC Intelligent Network Interface Card
Integrated Storage This centrally manages multiple storage systems.
Management
IP storage area A type of storage area network (SAN) that uses IP channels between servers and storage
network devices. IP SAN device performance is not as good as the FC SAN device performance,
but the use of IP SAN devices is not restricted by transmission distances. With the IP
bandwidth improvement, IP SAN devices will gradually replace FC SAN devices.
IP SAN See IP storage area network
iSCSI Internet Small Computer Systems Interface
ISM See Integrated Storage Management

FusionCompute
B.3 K-O
L
LB Load Balancer
linked clone A duplicate of a virtual machine that uses the same base disk as the original and a chain
of delta disks to keep track of the differences between the original and the clone. This
reduces the need for disk space and allows multiple VMs to use the same software
installation. Linked clones apply to scenarios that require VMs using the same software
installation, for example, call centers. System disks on linked clones can have slight
differences from the system disk on the parent VM. The differences are stored on delta
disks of the linked clones.
linked cloning A technology used to generate a quick copy of VMs by creating a delta disk instead of
copying an entire virtual hard disk.
linked snapshot A snapshot taken only for the memory or storage changes of a VM. A VM can be restored
using multiple relevant linked snapshots. A snapshot can be taken for the memory or
storage resource.
Live Migration Also known as hot migration, this is a method of migrating virtual machines (VMs)
without interrupting services.
local storage Storage space provided by a computing node agent (CNA).
logical cluster A logical group consisting of servers with the same attributes, such as CPU, storage, and
distributed virtual switch (DVS), in a physical cluster. The VM HA function takes effect
only for servers in the same logical cluster.
LUN Logical Unit Number
Management Module The management module of the server.

MM See Management Module
NAS See network attached storage

network attached A storage device that provides shared disk space on the network. It functions as file
storage sharing on a Windows system or the Network File System (NFS) on a Linux system.
Network Interface In the virtual system, this is identified as ethN, where N indicates a certain digit.
Card
Network Time Protocol An application-layer protocol which uses IP and UDP to synchronize the time between
the distributed time server and the client. NTP is evolved from Time Protocol and ICMP
Timestamp Message and features high protocol accuracy and good health.
NIC See Network Interface Card

FusionCompute
NTP See Network Time Protocol
B.4 P-T
P
POE See Provisioning Orchestration Engine

port group A group of ports with the same attributes on a distributed virtual switch (DVS) or virtual
software switch (VSS). In a hypervisor, all DVS settings, such as virtual local area
network (VLAN) and network flow control, are configured on a port group basis.
PortGroup See port group
Pre-boot Execution This technology enables computers to boot from the network. This technology is the
Environment successor of Remote Initial Program Load (RPL). The PXE works in client/server mode.
The PXE client resides in the ROM of a network card. When the computer boots up, the
BIOS invokes the PXE client to the memory. The PXE client obtains an IP address from
the DHCP server and downloads the operating system from the remote server through
TFTP.
Provisioning This exposes the unified service provisioning interface and synchronizes services
Orchestration Engine between components in the SingleCLOUD system.
PXE See Pre-boot Execution Environment
QoS See Quality of Service

Quality of Service A service that allows virtual storage device to migrate from one physical storage node
to another without interrupting the VM running. With the QoS enabled, users can control
the resources in a better way with costs reduced and a higher customer satisfaction.
SAN See Storage Area Network

SC See Software Client
Site A group of servers at the same physical location.
Snapshot A reproduction of the memory or storage data on a VM created at a specific time point.
Snapshots can be used to restore VMs to a state when these snapshots were taken.
Software Client Software running on a common PC to process the virtual desktop protocol.
Storage Area Network A network dedicated to transporting data for storage and retrieval.
storage cold migration A storage migration mode that allows data migration on a disk only after all VMs on the
disk are stopped.
storage resource pool A collection of storage resources. For example, an IP storage area network (IP SAN)
functions as a storage resource pool for a cluster.

FusionCompute
Storage Thin Storage thin provisioning is the act of using virtualization technology to give the
Provisioning appearance of more physical storage resources than is actually available. It allows storage
space to be easily allocated to users on an on-demand and auto-scale basis. This optimizes
utilization of available storage resources.
TC See Thin Client

Thin Client A terminal with lower processing power than a Thick Client that processes the virtual
desktop protocol, serves as the client of the remote desktop, and provides an access
method for users.
Thin LUN A logical storage unit created in the thin pool. The thin LUN is accessible to the host.
Thin Pool A thin pool is implemented based on storage thin provisioning. It allows storage space
to be dynamically allocated to users on demand. This optimizes utilization of available
storage resources.
Tools Tools is a virtualized driver for VMs. Tools improves VM performance, enables VM
hardware monitoring and advanced VM functions, such as migration, snapshot taking,
and on-line CPU adjustment.
B.5 U-Z
U
Unified Virtualization Virtual management software that divides the computing resource into multiple VM
Platform resources.
UVP See Unified Virtualization Platform
vCPU See Virtual CPU

VDS See Virtual Distributed Switch
vFW See Virtual Firewall
VIMS See Virtual Image Management System
Virtual CPU A hyper-thread on a server with multiple physical CPUs, which have multiple physical
cores on each CPU and multiple hyper-threads on each core.
Virtual Disk A file in the host file system. For a customer operating system, it functions as a physical
disk drive. The file can be configured on the host or a remote file system. After
configuring a VM with a virtual disk, you can install a new operating system to the disk
file without having to repartition a physical disk or restart the host. Virtual disks on the
VMware Workstation can be mapped to the partitions on the host.
Virtual Distributed A virtual switch (created on a physical server) that uses software to implement data
Switch switching between VMs on the same or different servers.

FusionCompute
Virtual Firewall A network firewall service or appliance running in a virtualized environment to provide
the usual packet filtering and monitoring functions like a physical network firewall.
Virtual Image A high-performance cluster file system that enables the FusionManager to connect to
Management System storage resources through a unified interface, which allows multiple VMs to gain access
to an integrated storage pool to improve resource utilization efficiency. The VIMS, as
the basis for virtualizing multiple storage servers, provides services such as live
migration, dynamic resources scheduling, and high availability for storage devices.
Virtual Local Area An end-to-end logical network across different network segments and networks,
Network constructed using the network management software based on the switching LAN.
Network resources and users are logically divided based on a certain principle and a
physical LAN is logically divided into multiple broadcasting domains (VLANs). The
hosts on a VLAN can directly communicate with each other whereas different VLANs
cannot. This efficiently suppresses broadcasting packets.
Virtual Machine One or multiple computer systems virtualized from a physical server.
Virtual Machine A function that controls the scheduling policy configuration and the control points of the
Dispatch policy dispatching.
Virtual Machine An operation that can be performed to a running VM. After the hibernated VM is started,
Hibernate it restores all programs before the hibernation.
Virtual Machine IP The IP address assigned to a VM, corresponding to the IP address of a physical machine.
Address The VM can communicate with other devices on the network through the IP address.
Virtual Memory Virtualized memory for a VM allocated based on the physical memory. Even if the
memory is not physically contiguous, it is contiguous for the VM. The VM can randomly
save and obtain data in its virtual memory without affecting the memory accessibility of
other VMs on the same physical machine.
Virtual Network Card A network card for VMs that corresponds to that of a physical machine. Multiple virtual
network cards can be created for a single VM. The virtual network card can connect to
the physical network card in bridge mode for data transmission.
Virtual Resource Huawei-developed virtualization management software, which comprises Huawei
Management infrastructure products and the Unified Virtualization Platform (UVP).
Virtual Server This is where the operating system and applications run based on various virtualization
technologies, unlike the original physical server. When using certain resources of the
physical server, the virtual server is the same as the physical server for users. Both
partitions and VMs are considered virtual servers.
Virtual Service A virtual appliance that provides layer 3 or layer 4 services on a virtual network. It can
Gateway contain one or multiple service instances including vRouter, vFirewall, vDHCP, NAT,
and VPN. The FusionManager supports VSG service implementation through a
vFirewall or a system VM.
Virtual Software This is deployed on a computing node and performs the virtual network switching
Switch function for the VMs on the node.
VLAN See Virtual Local Area Network
VM See Virtual Machine
VM High Availability With this, the O&M system continuously monitors all physical hosts and automatically
migrates all VMs off a faulty host.

FusionCompute
VM Migration A technology used to migrate VMs to another hardware resource for VM operations.
VM Specifications A set of pre-defined VM attributes for creating VMs with unified specifications.
VM template A template used to create VMs that have the same specifications. A VM template is a
VM in essence. A VM and a VM template can convert to each other as required. After
a VM is converted to a VM template, only its isTemplate attribute is changed to true.
VMD See Virtual Machine Dispatch
VRM See Virtual Resource Management
VSG See Virtual Service Gateway
VSS See Virtual Software Switch


FusionCompute V100R005C00 Software Installation Guide 04

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

FusionCompute V100R005C00 Software Installation Guide 04

Încărcat de

Drepturi de autor:

Formate disponibile

FusionCompute

Software Installation Guide

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 04 (2015-07-17) Huawei Proprietary and Confidential i

About This Document

Indicates an imminently hazardous situation which, if not

Indicates a potentially hazardous situation which, if not

Indicates a potentially hazardous situation which, if not

Indicates a potentially hazardous situation which, if not

Issue 04 (2015-07-17) Huawei Proprietary and Confidential ii

NOTE Calls attention to important information, best practices and

GUI Image Conventions

Added description about the FusionSphere Installer.

Deleted description about the FusionSphere Installer.

Issue 04 (2015-07-17) Huawei Proprietary and Confidential iii

About This Document.....................................................................................................................ii

Issue 04 (2015-07-17) Huawei Proprietary and Confidential iv

A.1.11 Troubleshooting the Tool of Deploying Hosts in Batches...................................................................................142

Issue 04 (2015-07-17) Huawei Proprietary and Confidential v

About This Chapter

1.1 FusionCompute Overview

1.2 Installation Process

Issue 04 (2015-07-17) Huawei Proprietary and Confidential 1

1.1 FusionCompute Overview

Figure 1-1 FusionCompute logical nodes

VRM (standby) Cluster 2

Table 1-1 describes the logical nodes in the FusionCompute.

Issue 04 (2015-07-17) Huawei Proprietary and Confidential 2

Table 1-1 FusionCompute nodes

Virtualization A node that implements centralized management of virtual resources.

Host A physical server that provides computing resources for the

Table 1-2 FusionCompute deployment schemes

Node Deployment Deployment Rule

Host Deployed on Multiple hosts can be deployed based on customer

Deployed on The active and standby VRMs must be deployed on

1.2 Installation Process

Issue 04 (2015-07-17) Huawei Proprietary and Confidential 3

Figure 1-2 FusionCompute installation process

Install the VRM.

Installation Introduction (Not Using FusionSphere Installer)

Issue 04 (2015-07-17) Huawei Proprietary and Confidential 4

Issue 04 (2015-07-17) Huawei Proprietary and Confidential 5

About This Chapter

2.1 System Requirements

2.2 Recommended Configuration Policies

2.3 Software Packages

2.4 Documents and Tools

Issue 04 (2015-07-17) Huawei Proprietary and Confidential 6

2.1 System Requirements

Table 2-1 PC requirements

CPU Intel or AMD x86 architecture CPU

OS The PC runs one of the following OSs of 32-bit or 64-bit:

Resolution To improve visual experience in using the FusionCompute installation

Issue 04 (2015-07-17) Huawei Proprietary and Confidential 7

Table 2-2 Host requirements

Item Requirements Remarks

Hard Hard disk size ≥ 16 GB If the VRM is deployed on a VM and

Issue 04 (2015-07-17) Huawei Proprietary and Confidential 8

Item Requirements Remarks

Network l Number of network ports ≥ 1 None

Table 2-3 lists the host BIOS configuration requirements.

Issue 04 (2015-07-17) Huawei Proprietary and Confidential 9