FusionCompute V100R003C00 FusionStack User Guide 01.pdf

FusionCompute
V100R003C00
FusionStack User Guide
Issue 01
Date 2013-04-10
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2013. 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 01 (2013-04-10) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
FusionCompute
FusionStack User Guide About This Document
About This Document
Purpose
This document describes how to install the FusionStack software and configure, operate, and
maintain the FusionStack system.
Intended Audience
This document is intended for:
l Installation and commissioning engineers

l Technical support engineers
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Alerts you to a high risk hazard that could, if not avoided,

result in serious injury or death.
DANGER
Alerts you to a medium or low risk hazard that could, if

not avoided, result in moderate or minor injury.
WARNING
Alerts you to a potentially hazardous situation that could,

if not avoided, result in equipment damage, data loss,
CAUTION
performance deterioration, or unanticipated results.
TIP Provides a tip that may help you solve a problem or save
time.
NOTE Provides additional information to emphasize or

supplement important points in the main text.
Issue 01 (2013-04-10) Huawei Proprietary and Confidential ii

FusionCompute
FusionStack User Guide About This Document
Change History
Changes between document issues are cumulative. The latest document issue contains all the
changes made in earlier issues.
Issue 01 (2013-04-10)
This issue is the first official release.
Issue 01 (2013-04-10) Huawei Proprietary and Confidential iii

FusionCompute
FusionStack User Guide Contents
Contents
About This Document.....................................................................................................................ii

1 Description......................................................................................................................................1
1.1 Product Introduction...........................................................................................................................................2
1.2 Product Architecture...........................................................................................................................................3
1.3 Deployment Scheme...........................................................................................................................................3
1.4 Product Functions...............................................................................................................................................5
1.5 Reliability...........................................................................................................................................................6
1.6 Technical Indicators...........................................................................................................................................6
2 Software Commissioning.............................................................................................................8
2.1 Overview............................................................................................................................................................9
2.1.1 Solution Overview.....................................................................................................................................9
2.1.2 Installation Process..................................................................................................................................10
2.2 Preparations......................................................................................................................................................11
2.2.1 System Requirements..............................................................................................................................11
2.2.2 Software Packages...................................................................................................................................13
2.2.3 Documents and Tools..............................................................................................................................15
2.2.4 Data..........................................................................................................................................................15
2.3 Software Installation in Virtualization Deployment.........................................................................................17
2.3.1 Installation Overview..............................................................................................................................17
2.3.2 Creating VMs..........................................................................................................................................18
2.3.3 Installing ESC Nodes...............................................................................................................................21
2.3.4 Installing IMGS Nodes............................................................................................................................25
2.3.5 Installing the ESC and IMGS Based VM Templates..............................................................................29
2.4 Software Installation in Physical Deployment.................................................................................................32
2.4.1 Installing ESC Nodes...............................................................................................................................32
2.4.2 Installing IMGS Nodes............................................................................................................................37
2.5 Initial Configuration.........................................................................................................................................42
2.5.1 Configuration Overview..........................................................................................................................42
2.5.2 Configuring the License Server...............................................................................................................44
2.5.3 Configure the active and standby ESCs..................................................................................................46
2.5.4 Configuring a Virtual Firewall................................................................................................................47
2.5.5 Configuring Resource Access Points......................................................................................................56
Issue 01 (2013-04-10) Huawei Proprietary and Confidential iv

FusionCompute
2.5.6 Adding an L2Area Network....................................................................................................................60

2.5.7 Adding Site Resources.............................................................................................................................66
2.5.8 Creating a Service Cluster.......................................................................................................................67
2.5.9 Configuring Time Synchronization and Time Zone................................................................................71
2.5.10 Adding an Image Server........................................................................................................................73
2.5.11 Configuring a Backup Server................................................................................................................74
2.6 FAQ..................................................................................................................................................................76
2.6.1 Verifying Software Packages..................................................................................................................76
2.6.2 Logging In to the FusionStack...............................................................................................................78
2.6.3 Logging In to the FusionCompute.........................................................................................................80
3 Feature Configuration.................................................................................................................84
3.1 VPC Feature Configuration..............................................................................................................................85
3.1.2 Adding a VPC Subnet Pool.....................................................................................................................85
3.1.3 Configuring a Bandwidth Template........................................................................................................86
3.1.4 Configuring VPC Network Specifications..............................................................................................88
3.1.5 Adding Default DHCP Options...............................................................................................................89
3.2 Security Group Feature Configuration.............................................................................................................91
3.2.2 Configuring a Bandwidth Template........................................................................................................92
3.2.3 Configuring Security Group Network.....................................................................................................93
3.2.4 Adding Default DHCP Options...............................................................................................................94
3.2.5 Adding a Security Group Subnet.............................................................................................................96
3.2.6 Enabling the Public IP Address...............................................................................................................98
3.3 LB Feature Configuration.................................................................................................................................99
3.3.2 Registering an LB VM Image...............................................................................................................100
3.3.3 Configuring the LB Manager................................................................................................................101
3.3.4 Adding LB Instance Specifications.......................................................................................................103
3.3.5 Adding LB VM Specifications..............................................................................................................104
3.3.6 Adding a Management Subnet..............................................................................................................106
3.3.7 Adding a Service Subnet.......................................................................................................................107
3.3.8 Configuring the LB Instance Limit.......................................................................................................109
4 Operation and Maintenance....................................................................................................111

4.1 Quick Start......................................................................................................................................................112
4.1.1 About FusionStack................................................................................................................................112
4.1.2 Logging In to the System.......................................................................................................................112
4.1.3 Function Description.............................................................................................................................114
4.2 Image Management........................................................................................................................................126
4.2.1 Making an Image...................................................................................................................................126
4.2.2 Registering an Image.............................................................................................................................128
4.2.3 Deregistering or Deleting an Image.......................................................................................................129
Issue 01 (2013-04-10) Huawei Proprietary and Confidential v

FusionCompute
4.2.4 Freezing or Unfreezing an Image..........................................................................................................130

4.3 Configuration Management............................................................................................................................131
4.3.1 Configuring the System Logo................................................................................................................132
4.3.2 Configuring the Charging Function.......................................................................................................132
4.3.3 Configuring the Subscription Server.....................................................................................................134
4.3.4 Configuring Domain Authentication Information.................................................................................136
4.3.5 Configuring the Session Timeout Duration...........................................................................................137
4.3.6 Modifying Time Synchronization and Time Zone Settings..................................................................138
4.3.7 Synchronizing Time Forcibly................................................................................................................140
4.3.8 Modifying ESC VM Specifications.......................................................................................................141
4.4 Image Server Management.............................................................................................................................143
4.4.1 Adding an Image Server........................................................................................................................143
4.4.2 Deleting an Image Server......................................................................................................................144
4.4.3 Modifying an Image Server...................................................................................................................145
4.4.4 Adding or Deleting a Disk.....................................................................................................................146
4.4.5 Adding Secondary-Tier Storage Resources...........................................................................................149
4.5 Operation Log Management...........................................................................................................................155
4.5.1 Viewing Operation Logs.......................................................................................................................155
4.6 Subscription Management..............................................................................................................................156
4.6.1 Adding an Alarm Subscription Task.....................................................................................................156
4.6.2 Modifying an Alarm Subscription Task................................................................................................158
4.6.3 Suspending or Deleting an Alarm Subscription Task...........................................................................159
4.7 User Management...........................................................................................................................................160
4.7.1 Creating a Role......................................................................................................................................160
4.7.2 Creating a User......................................................................................................................................161
4.7.3 Configuring Password Policies..............................................................................................................163
4.7.4 Modifying User Information.................................................................................................................166
4.7.5 Modifying the Rights of a Role.............................................................................................................168
4.7.6 Resetting User Password.......................................................................................................................169
4.7.7 Changing the User Password.................................................................................................................170
4.7.8 Locking a User Account........................................................................................................................171
4.7.9 Unlocking the Locked User Account....................................................................................................172
4.7.10 Deleting a User....................................................................................................................................173
4.8 Health Check..................................................................................................................................................174
4.8.1 Viewing Alarms.....................................................................................................................................174
5 Fault Management.....................................................................................................................176
5.1 Alarm Handling..............................................................................................................................................177
5.1.1 ALM-15.1000077 License Is About to Expire......................................................................................177
5.1.2 ALM-15.1000078 License Has Expired................................................................................................178
5.1.3 ALM-15.1001000 VRM Node Unreachable.........................................................................................180
5.1.4 ALM-15.1001004 LDAP Database Unreachable..................................................................................183
5.1.5 ALM-15.1001005 License File Not Loaded.........................................................................................185
Issue 01 (2013-04-10) Huawei Proprietary and Confidential vi

FusionCompute
5.1.6 ALM-15.1001007 Failure in Recovering VM Data from the Database During ESC Start...................187
5.1.7 ALM-15.1001010 FTP Server Unreachable.........................................................................................189
5.1.8 ALM-15.1001013 Image Storage Server Unreachable.........................................................................192
5.1.9 ALM-15.1001014 Image Storage Space Insufficient............................................................................195
5.1.10 ALM-15.1001015 Data Store Space Insufficient................................................................................197
5.1.11 ALM-15.1001020 SLB Node Unreachable.........................................................................................199
5.1.12 ALM-15.1002000 Heartbeat Communication Between Active and Standby Nodes Interrupted.......201
5.1.13 ALM-15.1002006 Heartbeat Communication Between the Node and the NTP Server Interrupted
........................................................................................................................................................................206
5.1.14 ALM-15.1004000 Invalid License File...............................................................................................209
5.1.15 ALM-15.1007004 NOTIFY Process Abnormal..................................................................................211
5.1.16 ALM-15.1007005 System Time Offset Exceeds One Minute............................................................213
5.1.17 ALM-15.1007006 Abnormal Clock Synchronization Process............................................................216
5.1.18 ALM-15.1007007 Abnormal System Timing Service Process...........................................................218
5.1.19 ALM-15.1007011 Configuration Channel Client Process Is Abnormal.............................................220
5.1.20 ALM-15.1007012 NFS Service Process on the Image Storage Server Abnormal..............................222
5.1.21 ALM-15.1007013 Image Management (IMGM) Process Abnormal..................................................224
5.1.22 ALM-15.1007014 Elastic Computing Service Process on the ESC Node Abnormal.........................225
5.1.23 ALM-15.1007015 UPF Service Process Abnormal............................................................................227
5.1.24 ALM-15.1007016 ELB Service Process Abnormal............................................................................229
5.1.25 ALM-15.1007099 Failure in Backing up or Uploading Key Data......................................................231
5.1.26 ALM-15.1008000 Communication with License Server Is Abnormal...............................................233
5.1.27 ALM-15.1008001 Free Upgrade Service Is About to Expire..............................................................235
5.1.28 ALM-15.1008002 Free Upgrade Service Has Expired.......................................................................236
5.1.29 ALM-15.3002005 Number of In-Use CPUs on the CNA Exceeds 90% of the Licensed Total Number
........................................................................................................................................................................238
5.2 Troubleshooting..............................................................................................................................................240
5.2.1 ESC VM Fault.......................................................................................................................................240
5.2.2 IMGS VM Fault.....................................................................................................................................244
5.2.3 LB VM Faulty.......................................................................................................................................244
5.2.4 Active and Standby ESC Faults.............................................................................................................247
5.3 Backup and Restoration..................................................................................................................................248
5.3.1 Backup and Restoration Policy..............................................................................................................248
5.3.2 Backing up Data....................................................................................................................................250
5.3.3 Restoring Data.......................................................................................................................................253
A Glossary......................................................................................................................................257
A.1 A-E.................................................................................................................................................................258
A.2 F-J..................................................................................................................................................................259
A.3 K-O................................................................................................................................................................260
A.4 P-T.................................................................................................................................................................261
A.5 U-Z.................................................................................................................................................................263
Issue 01 (2013-04-10) Huawei Proprietary and Confidential vii

FusionCompute
FusionStack User Guide 1 Description
1 Description
About This Chapter
1.1 Product Introduction

1.2 Product Architecture
1.3 Deployment Scheme
1.4 Product Functions
1.5 Reliability
1.6 Technical Indicators
Issue 01 (2013-04-10) Huawei Proprietary and Confidential 1

FusionCompute
1.1 Product Introduction
Overview
The FusionStack is based on the basic virtualization capabilities provided by the Huawei
virtualization software (FusionCompute), and provides customers with elastic computing
services, such as VMs, disks, security groups, elastic IP addresses.
Position in the FusionCompute

Figure 1-1 shows the FusionStack position in the FusionCompute.
Figure 1-1 FusionCompute components

FusionCompute
Cloud computing infrastructure platform
Image management Backup ELB
VPC Multi-Tenant Elastic IP
Basic services
Virtualization infrastructure platform
Resource management
Availability Security Expandability
Computing Storage Network

Virtualization Virtualization Virtualization
Technical Features
Cloud Security
The FusionStack adopts various security measures and policies and complies with local
information security laws and regulations to provide end-to-end protection for user access,
management and maintenance, data, networks, and virtualization.
Scalability
Based on the Huawei virtualization service clusters, the maximum number of sites the
FusionStack supports can be expanded to 16. With application programming interfaces (APIs),
VMs can be migrated between hosts on one site.
Fine-Grained Charging
The FusionStack provides different types of charging services based on service types:
l Charging by service resources
l Charging by hours

FusionCompute
1.2 Product Architecture
Software Components
The FusionStack consists of Elastic Service Controller (ESC), Image Storage (IMGS), User
Profile Function (UPF), Provisioning Orchestration Engine (POE), and other logical units.
Figure 1-2 shows the logical architecture of the FusionStack.
Figure 1-2 Logical architecture of the FusionStack
FusionStack
IMGS UPF POE
IMGM ESC ESC-OM
UHM VRM LBManager
IMGS: Image Storage UPF: User Profile Function POE: Provisioning

Orchestration Engine
IMGM: Image Management ESC: Elastic Service ESC-OM: ESC Operation and
Controller Maintenance Management
UHM: Unified Hardware VRM: Virtual Resource LBManager: Elastic Load

Management (The Management (The Balancing Manager
FusionStack uses the UHM to FusionStack uses the VRM as
configure and manage firewall the access point to add Huawei
services.) virtualization resources.)
1.3 Deployment Scheme
Logical Nodes
The management nodes of the FusionStack are Elastic Service Controller (ESC) and Image
Storage (IMGS). Figure 1-3 shows their logical relationships.

FusionCompute
Figure 1-3 Logical nodes of the FusionStack
Cloud basic services
...
Active Standby IMGS1 IMGS2

ESC ESC
Virtual infrastructure
Site 1 Site 2 Site n
...
Active Standby Active Standby Active Standby
VRM VRM VRM VRM VRM VRM
Virtual resources Virtual resources Virtual resources
Deployment Principles
Table 1-1 lists the node deployment principles for cloud basic services.
Table 1-1 Deployment Principles

Node Deployment principles
Elastic Service Controller (ESC) One or two ESCs (active and standby) can be deployed in
the system.
In virtualization deployment, the ESC is deployed on a
VM in the management cluster.
In physical deployment, the ESC is deployed on a physical
server.
Image Storage (IMGS) In virtualization deployment, the IMGS is deployed on a

VM in the management cluster. The specifications of an
IMGS VM cannot be modified after the VM is created.
New IMGS can be added if required.
In physical deployment, the IMGS is deployed on a
physical server.
Table 1-2 lists the VM specifications requirements when the ESC and IMGS are deployed on
VMs.

FusionCompute
Table 1-2 VM specifications

Node VM VM VM VM
Specifications Specifications Specifications Specifications
(more than (2000 to 5000 (5000 to 16000 (16000 to 80000
2000 VMs) VMs) VMs) VMs)
ESC 4 CPUs and 8 6 CPUs and 12 8 CPUs and 32 16 CPUs and 64

GB memory GB memory GB memory GB memory
IMGS 4 CPUs and 4 4 CPUs and 4 4 CPUs and 4 4 CPUs and 4 GB

GB memory GB memory GB memory memory
1.4 Product Functions
VPC
A virtual private cloud (VPC) is a private cloud constructed for a customer within a public cloud,
and can connect to the customer networks. A private cloud is entirely isolated from all VMs that
are not hosted by this private cloud. An enterprise can apply for virtual private clouds on the
public cloud platform and use independent IP addresses on its private cloud networks.
The enterprise can connect the private cloud to their own network using the Virtual Private
Network (VPN) gateway, and use VMs on the private cloud like using IT devices on its own
networks.
Security Group
Public cloud tenants can apply for security groups based on their VM security requirements, and
set access policies for the obtained security groups to enhance VM security. VMs that are added
to a security group implement security isolation and access control under the protection of the
access policies.
ELB
The Elastic Load Balancing (ELB) function provides load balancing services for tenants, so that
end users can apply for virtual load balancers and associate them with their hosts. Based on the
customized load balancing policies, the obtained load balancer evenly sends service requests to
associated hosts to enhance service stability and reliability.
Image Management
Using an Image Storage (IMGS) node, the FusionStack manages images offering different types
of operating systems (OSs), and supports image registration, deregistration, query, and deletion.
On the FusionCompute, users can create customized VMs and deploy applications, and
download and save images exported by the VMs to the IMGS node.
Registered images can be updated in the system. To modify an image in use, users can freeze
the image, modify the image, and then unfreeze the image to resume image services.
To expand the image server capacity, users can configure storage path that saves images using
ports provided by the image server.

FusionCompute
Elastic IP address
The FusionStack assigns a public IP address for each user VM. The assigned public IP address
can be used as an elastic IP address to be bound with a user account, so that users can connect
to the VM using this IP address through Internet. Bound IP addresses can be unbound to release
the public IP address.
If a running VM is faulty, the elastic IP address of the fault VM can be rapidly mapped to another
VM, so that the user can use a VM without service interruption.
Charging
The FusionStack generates charging data records (CDRs) according to the usage of VMs, disks,
elastic IP addresses, virtual local area networks (VLANs), VPCs, security groups, VM snapshots,
LB instances, and other service resource, and send the CDRs to the billing center. The billing
center generates bills based on the CDRs.
1.5 Reliability
Management Node HA
Management nodes work in active/standby mode to ensure high availability (HA). If the active
node is faulty, the standby node takes over services from the active node, ensuring uninterrupted
service processing of management nodes.
The active and standby nodes check the status of each other using the heartbeat messages sent
over the management plane. The active node is automatically determined based on the heartbeat
messages.
l Only the active node provides services. The standby node only provides basic functions
and periodically synchronizes data with the active node.
l If the active node is faulty, the standby node takes over services from the active node and
changes to the active state. The original active node changes to the idle state.
The active node faults include the network interruption, abnormal state, or faulty service
process of the active node.
Snapshot
The snapshot feature enables the FusionStack to recover a damaged virtual machine (VM) by
using its snapshots.
A snapshot is a set of system files and directories of a VM kept in storage as they were some
time in the past.
l When a VM is faulty, a user can quickly create a VM based on the backed-up VM snapshot.
l A user can also restore a VM to the time the snapshot is created.
1.6 Technical Indicators

FusionCompute
Table 1-3 Capacity Indicators

Indicator Value
Maximum number of sites supported by the 16

system
Maximum number of servers supported by 5,000

the system
Maximum number of VMs supported by the 80,000

system

FusionCompute
FusionStack User Guide 2 Software Commissioning
2 Software Commissioning
About This Chapter
2.1 Overview
2.2 Preparations
2.3 Software Installation in Virtualization Deployment
2.4 Software Installation in Physical Deployment
2.5 Initial Configuration
2.6 FAQ

FusionCompute
2.1 Overview
2.1.1 Solution Overview
Logical Nodes
Figure 2-1 shows the logical nodes of cloud basic services.
Figure 2-1 Logical nodes of cloud basic services
Cloud basic services
...
Active Standby IMGS1 IMGS2

ESC ESC
Virtual infrastructure
Site 1 Site 2 Site n
...
Active Standby Active Standby Active Standby
VRM VRM VRM VRM VRM VRM
Virtual resources Virtual resources Virtual resources
Deployment Principles
Table 2-1 lists the node deployment principles for cloud basic services.
Table 2-1 Deployment Principles

Elastic Service Controller (ESC) One or two ESCs (active and standby) can be deployed in
the system.
In virtualization deployment, the ESC is deployed on a
VM in the management cluster.
In physical deployment, the ESC is deployed on a physical
server.

FusionCompute
Image Storage (IMGS) In virtualization deployment, the IMGS is deployed on a

VM in the management cluster. The specifications of an
IMGS VM cannot be modified after the VM is created.
New IMGS can be added if required.
In physical deployment, the IMGS is deployed on a
physical server.
Table 2-2 lists the VM specifications requirements when the ESC and IMGS are deployed on
VMs.
Table 2-2 VM specifications

Node VM VM VM VM
Specifications Specifications Specifications Specifications
(more than (2000 to 5000 (5000 to 16000 (16000 to 80000
2000 VMs) VMs) VMs) VMs)
ESC 4 CPUs and 8 6 CPUs and 12 8 CPUs and 32 16 CPUs and 64

GB memory GB memory GB memory GB memory
IMGS 4 CPUs and 4 4 CPUs and 4 4 CPUs and 4 4 CPUs and 4 GB

GB memory GB memory GB memory memory
2.1.2 Installation Process
Installation Process
Figure 2-2 shows the software installation process of cloud basic services.
Figure 2-2 The software installation process of cloud basic services
Start
Prepare for the installation.
Install ESCs and IMGSs.
Perform initial configuration.
End

FusionCompute
Installation Process Description

Table 2-3 lists the differences in installing cloud basic services between different deployment
modes.
Table 2-3 Differences between the two deployment modes

Node Virtualization Deployment Physical Deployment
Elastic Service The ESC is deployed on a VM in The ESC is deployed on a

Controller (ESC) a management cluster. physical server.
The VMs on which the active and
standby ESCs are deployed must
be created on different hosts.
Image Storage The IMGS is deployed on a VM The IMGS is deployed on a

(IMGS) in a management cluster. physical server.
2.2 Preparations
2.2.1 System Requirements

Ensure that the local PC, servers, storage devices, and networks meet the requirements for
installing the FusionCompute system.
Requirements for the Local PC

Table 2-4 lists the requirements for the local PC.
Table 2-4 Local PC requirements

Item Requirement
CPU Intel or AMD x86 architecture 32-bit CPU
Memory ≥ 2 GB
Hard disk l The partition in which the operating system (OS) is installed 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 Windows XP 32-bit or Windows 7 32-bit
System software l JRE 1.6 or later has been installed.

l Microsoft .NET Framework 4.0 or later has been installed.
Network The local PC and the available host are connected to the same switch,
and their IP addresses belong to the same management network segment.

FusionCompute
Requirements for Hosts

Table 2-5 and Table 2-6 list the server configuration requirements and BIOS configuration
requirements respectively.
Table 2-5 Server configuration requirements

Item Requirement
CPU Intel or AMD 64-bit CPU

The CPU supports hardware virtualization technology, such as Intel VT-
x or AMD-V.
The CPUs of the same model must be used in a cluster.
Memory ≥ 16 GB
The recommended memory size is greater than 48 GB.
Hard disk ≥ 50 GB
Network port l The number of network ports is greater than or equal to 1.

l The recommended number of network ports is six. The
recommended network port rate is greater than 1000 Mbit/s.
Redundant Array You are advised to use RAID 1 that consists of hard disks 1 and 2 to
of Independent install host OS and software to enhance reliability.
Disks (RAID) If the host uses local storage resources, ensure that the host still has
unpartitioned disks after the OS and software is installed, because the
host OS and software require a whole physical hard disk.
Table 2-6 BIOS configuration requirements

Item Requirement
Boot device Set the first boot device to Hard disk, the second boot device to
Network, and the third boot device to CD-ROM.
NIC Pre-boot l Enable PXE for NIC1.

execution l Disable PXE for other NICs.
environment
(PXE)
Requirements for Networks

Table 2-7 lists the requirements for networks.

FusionCompute
Table 2-7 Requirements for networks
Item Requirements
Device model and The FusionStack supports the following firewalls:

version l Eudemon 1000E-U V2R1
requirements
l Eudemon 1000E-X V2R1
l Eudemon 1000E-X V3R1
l Eudemon 8000E V2R1
NOTE
l Eudemon 1000E-U V2R1 and Eudemon 1000E-X V2R1 do not support
virtual firewall bandwidth limit. To implement the Network Address
Translation (NAT) function, you need to modify the configuration file of the
firewall of Eudemon 1000E-U V2R1 or Eudemon 1000E-X V2R1.
l If Eudemon 1000E is used, one VM or private IP address can be bound to
only one elastic IP address with bandwidth limit.
The FusionStack supports most of the S93- and S53- series switches
that provide functions including stacking, Open Shortest Path First
(OSPF), and VLANIF.
Basic device l Two firewall devices (active and standby) must be mounted to the
networking service and management switches in offline mode.
requirements l The network has two service switches stacked and two management
switches stacked.
l The FusionStack does not support a single firewall or two switches
deployed in active/standby mode.
2.2.2 Software Packages
VRM in Virtualization Deployment

Table 2-8 lists the software packages required for VRM virtualization deployment.
Table 2-8 Software packages required for VRM virtualization deployment
Installation Software Description How to Obtain

Mode
Install using an FusionCompute ESC VM image Visit http://

ISO file V100R003C00_ files support.huawei.com/
ESC.iso enterprise, and choose
FusionCompute Software > IT > Cloud
V100R003C00_ Computing >
ESC.sha256 Infrastructure
Virtualization >
FusionCompute >
FusionCompute
V100R003C00.

FusionCompute
Installation Software Description How to Obtain

Mode
FusionCompute IMGS VM image Visit http://

V100R003C00_I files support.huawei.com/
MGS.iso enterprise, and choose
V100R003C00_I Computing >
MGS.sha256 Infrastructure
Virtualization >
FusionCompute >
FusionCompute
V100R003C00.
Install using a FusionCompute ESC VM template Visit http://

template V100R003C00_ files support.huawei.com/
ESC.zip enterprise, and choose
ESC.zip.sha256 Infrastructure
Virtualization >
FusionCompute >
FusionCompute
V100R003C00.
FusionCompute IMGS VM template Visit http://

V100R003C00_I files support.huawei.com/
MGS.zip enterprise, and choose
V100R003C00_I Computing >
MGS.zip.sha256 Infrastructure
Virtualization >
FusionCompute >
FusionCompute
V100R003C00.
FusionCompute LB VM template Visit http://

V100R003C00_ files support.huawei.com/
SLB.zip enterprise, and choose
SLB.zip.sha256 Infrastructure
Virtualization >
FusionCompute >
FusionCompute
V100R003C00.

FusionCompute
NOTE
l To ensure that the obtained software packages are valid for use, you need to verify the software package
integrity and validity. For details, see Verifying Software Packages.
l After downloading the template file package, decompress the package, which must contain a .xml file
and a .vhd file.
2.2.3 Documents and Tools

Obtaining Documents
Table 2-9 Documents required for system installation

Document Description How to Obtain
Network Design Provides the software Obtain the document from the
deployment plan. engineering supervisor.
Integration Design Provides data plan information.

Data Plan Template
GalaxEngine Provides information about the Software > IT > Cloud

V100R003C00 mapping between software and Computing > Infrastructure
Version Mapping hardware versions. Virtualization > FusionCompute
Template > FusionCompute V100R003C00
Obtaining Tools
Table 2-10 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 Windows during download this tool.
the software installation.
WinSCP A tool used for transferring files Visit http://winscp.net and

between Windows and Linux download this tool.
operating systems.
2.2.4 Data
Table 2-11 lists the data required for installing the cloud basic services.

FusionCompute
Table 2-11 Data required for installing the cloud basic services.
Category Paramete Description Example Value
r
VM VM name Specifies the name of the management ESC01

informatio VM.
n Value: a string of 1 to 32 characters
The VM name can contain only digits,
letters, and underscores (_) and must start
with a letter.
The VM name must be unique and
different from the name of the cluster.
ESC ESC node Specifies the name of the Elastic Service ESC01
informatio name Controller (ESC) node.
n Value: a string of 1 to 32 characters
The node name can contain only digits,
with a letter.
The node name must be unique and
different from the cluster name.
Managem Specifies the IP address of the ESC 188.100.4.38

ent IP management network port if the ESC is
address deployed on a physical server.
Specifies the IP address of the VM if the
ESC is deployed on a VM.
Subnet Specifies the subnet mask of the ESC 255.255.255.0

mask of management plane.
the
managem
ent plane
Gateway Specifies the gateway address of the ESC 188.100.4.1

address of management plane.
the
managem
ent plane
Floating Is required only when the ESCs are 188.100.4.30

IP address deployed in the active and standby mode.
Specifies the floating IP address for the
ESCs.

FusionCompute
Category Paramete Description Example Value

r
IMGS IMGS Specifies the name of the Image Storage IMGS01

Informati node name (IMGS) node.
on Value: a string of 1 to 32 characters
with a letter.
The node name must be unique and
different from the name of the cluster.
Managem Specifies the IP address of the IMGS 188.100.4.34

ent IP management network port if the IMGS is
address deployed on a physical server.
Specifies the IP address of the VM if the
IMGS is deployed on a VM.
Subnet Specifies the subnet mask of the IMGS 255.255.255.0

mask of management plane.
the
managem
ent plane
Gateway Specifies the gateway address of the IMGS 188.100.4.1

address of management plane.
the
managem
ent plane
2.3 Software Installation in Virtualization Deployment
2.3.1 Installation Overview
Installation Process
The Elastic Service Controller (ESC) node and Image Storage (IMGS) node can be installed
using a template or an ISO file. Figure 2-3 shows the process for installing the two nodes.

FusionCompute
Figure 2-3 Process for installing the ESC and IMGS nodes
Start
Determine Yes
Whether to use templates
to install.
No
Creating VMs
Installing the ESC and IMGS

Installing ESC Nodes
Based VM Templates
Installing IMGS Nodes
End
2.3.2 Creating VMs

Scenarios
On the FusionCompute, create VMs for deploying the Elastic Service Controller (ESC) and
Image Storage (IMGS) nodes.
Prerequisites
Conditions
– You have installed and configured the FusionCompute.
– You have configured the IP address of the local PC to communicate with the management
plane of FusionCompute.
– You have installed the JRE 1.6 or a later version on the local PC.
– You have logged in to the FusionCompute.
Data
Table 2-12 lists the data required for performing this operation.

FusionCompute
Table 2-12 Data required for performing this operation

Category Parameter Description Example Value
Basic VM name Specifies the name of the management ESC01, IMGS01

information VM.
Value: a string of 1 to 32 characters
The VM name can contain only digits,
letters, and underscores (_) and must
start with a letter.
The VM name must be unique and
different from the cluster name.
Specification CPU The specifications of VMs created to l ESC VMs

s deploy the ESC and IMGS are listed have 4 CPUs
Memory(MB) as follows: and 8192 MB
l If the number of the supported memory.
VMs is no more than 2000, the l IMGS VMs
ESC VMs have 4 CPUs and 8 GB have 4 CPUs
memory. and 4096 MB
l If the number of the supported memory.
VMs is between 2000 and 5000,
the ESC VMs have 6 CPUs and 12
GB memory.
l If the number of the supported
the ESC VMs have 8 CPUs and 32
GB memory.
l If the number of the supported
the ESC VMs have 16 CPUs and
64 GB memory.
l The IMGS VMs have 4 CPUs and
4 GB memory.
NIC Settings Distributed The NIC attributes are determined by ManagementDV

switch the port group on the distributed S
virtual switch (DVS) used by the NIC.
Port Group Portgroup01
Data storage Data storage Specifies the data storage for the disk. datastore01
information
Procedure
1 On the FusionCompute, choose VDC Management > Cluster and Host.

2 In the navigation tree on the left, choose Site > Cluster and select a host.

FusionCompute
NOTE
You must create VMs for deploying the active and standby ESCs on different hosts.
3 On the Getting Started page, click Create VM.
The Create VM page is displayed.
4 Select the required host and Bind to the select host, and click Next.
The Properties page is displayed.
5 Set the VM name, and select the Operating System (OS) type and version.
– VM name: Enter the name of the management VM, for example, ESC01.
– OS type: Select Linux.
– OS version: Select Novell SUSE Linux Enterprise Server 11 SP1 64bit.
6 Configure the hardware specifications of the VM.
– CPU: Select the required number of CPUs based on the data plan, for example, 4.
– Memory (MB): Enter the memory size based on the data plan, for example, 8192.
– Number of disks: Set the number of disks to 1.
– Number of NICs: Set the number of NICs to 1.
7 Click QoS Settings, and set CPU Resource Control and Memory Resource Control.
CPU Resource Control
– Quota: Select Medium.

– Reserved (MHz): Set this parameter to the maximum value.
– Limit (MHz): Select No limit.
Memory Resource Control
– Quota: Select Medium.

– Reserved (MHz): Set this parameter to the maximum value.
8 Configure the advanced attributes of the VM.
– HA: Select Enable.
– Policy for handling the blue screen of death (BSOD): Select No processing.
– Clock synchronization policy: Select Synchronize with host clock.
Set the other parameters to default values.

9 Click Next.
The Set VM page is displayed.
10 In the NIC Settings area, click in NIC1.

The Select Port Group dialog box is displayed.
11 Select the DVS and port group of the management plane.
For example, select ManagementDVS for DVS and Portgroup01 for port group.
12 Click OK.
13 Set the following parameters:
– Data storage: Select the created data storage, for example, datastore01.
– Configuration mode: Select Ordinary.

FusionCompute
– Capacity (GB): Enter 50. The disk capacity of the VM is 50 GB.

14 Click Next.
15 Confirm the information and click Finish.
16 Click Close.
The system starts to create VMs. You can choose VDC Management > VM and
Template > Task Tracing to view the creation progress.
17 Create VMs for deploying other management nodes.
For details, see Step 1 to Step 16.
----End
2.3.3 Installing ESC Nodes
Scenarios
Install Elastic Service Controller (ESC) nodes on VMs. When the ESCs are deployed in the
active and standby mode, the VMs on which the active and standby ESCs are deployed must
run on different hosts.
Prerequisites
Conditions
– You have created the VMs for installing ESCs.
Data
Parameter Description Example Value
ESC node name Specifies the name of the ESC. ESC01

with a letter.
The node name must be unique and different
from the cluster name.
This parameter is mandatory.
ESC management Specifies the IP address of the VM on which 188.100.200.35

IP address the ESC is deployed.
Set the IP address to be within the
management plane network segment.

FusionCompute
Subnet mask of the Specifies the subnet mask of the ESC 255.255.255.0
management plane management plane.
Gateway address of Specifies the gateway address of the ESC 188.100.200.1

the management management plane.
plane This parameter is mandatory.
Software
FusionCompute V100R003C00_ESC.iso
Procedure
Mount a CD-ROM drive to the VM.
1 Share the folder containing the FusionCompute V100R003C00_ESC.iso file with the
administrator of the local PC.
2 On the FusionCompute, choose VDC Management > VM and Template.
3 In the navigation tree on the left, expand Site, and click the name of the VM on which the
ESC is to be deployed.
4 In the Operation area on the right, click Mount CD-ROM.
5 In the displayed dialog box, enter the ISO file path: \\IP address of the local PC\name of
the shared folder\name of the image file,
for example, \\182.168.5.5\soft\FusionCompute V100R003C00_ESC.iso. The IP address
of the local PC communicates with that of the management plane.
6 Select Use the username and password of the local computer.
7 Enter the username and the password shared in Step 1.
8 Select Restart the VM now to install the OS and click OK.
Install the ESC.
9 Click Log In Using VNC.
The system installation window is displayed, as shown in Figure 2-4.

FusionCompute
Figure 2-4 System installation window
NOTE
l If you select Boot from local disk, the system skips the installation and starts from the local disk.
l If you select Install, the system performs the installation.
l If you do not perform any operation during 30 seconds, the system starts from the local disk by
default. Then you must restart the VM before performing the subsequent operations.
10 Select Install and press Enter.
It takes about 3 minutes for the automatic loading of the system. After the loading is
complete, the Main Installation Window is displayed, as shown in Figure 2-5.
Figure 2-5 Main Installation Window

FusionCompute
TIP
You can refer to the following tips when performing operations on the Main Installation
Window:
l Press Tab or up and down arrow keys to move the cursor.
l Press Enter to enter or perform the items that the cursor pointing at.
l Press the space bar to select the items that the cursor pointing at.
11 Select Network and press Enter.
The Network Configuration window is displayed.
12 Select the network interface card (NIC) eth0 and press Enter.
The IP Configuration for eth0 window is displayed.
13 Use the arrow keys to locate Manual address configuration and press the space bar to
select it.
14 Press Tab to set the following parameters:
– IP address: Enter the planned ESC management IP address.
– Netmask: Enter the subnet mask of the management plane.
15 Press F12.
16 Select Default Gateway and set the gateway of the ESC management plane.
17 Press F12.
The Main Installation Window is displayed.
18 Select Hostname and press Enter.
The Hostname Configuration window is displayed.
19 Enter the planned ESC node name, for example, ESCO1, and press F12.
20 Select Timezone and press Enter.
The Time Zone Selection window is displayed.
21 Select the local time zone and set the time.
22 Press F12.
23 Select Password and press Enter.
The Root Password Configuration window is displayed.
24 Enter the password for user root and confirm the password, and press F12.
NOTE
The password must meet the following requirements:

l The password contains a minimum of 8 characters and a maximum of 32 characters.
l The password must contain at least three of the following combinations:
l At least one lowercase letter
l At least one uppercase letter
l At least one digit
l At least one space or special character ~!@#$%^&*()-_=+\|[{}];:'",<.>/?
25 Press F12.

FusionCompute
26 Select Yes and press Enter.

The system displays a message, asking you whether the configuration is complete.
27 Select Yes.
The Package Installation window is displayed, and the system starts to install the operating
system (OS) of the ESC.
The installation takes about 15 minutes. After the installation, the VM restarts
automatically. When the login information is displayed, the installation of the ESC is
complete.
28 Determine whether to deploy the ESC in the active and standby mode.
– If yes, go to Step 29.
– If no, go to Step 30.
Install the standby ESC.
29 Install the standby ESC. For details, see Step 2 to Step 27.
Unmount a CD-ROM drive from the VM.
30 On the GalaxEngine, choose VDC Management > VM and Template.
31 In the navigation tree, expand Site and click the VM on which the ESC is deployed.
32 In the Operation area on the right, select Unmount CD-ROM.
A confirmation dialog box is displayed.
33 Click OK.
A dialog box is displayed, indicating that the system begins to unmount the CD-ROM drive.
You can view the task progress in the Task Tracing page.
34 Click OK.
NOTE
If the ESCs are deployed in the active and standby mode, you need to unmount the CD-ROM drives
from both the active standby nodes.
----End
2.3.4 Installing IMGS Nodes
Scenarios
Install Image Storage (IMGS) nodes on VMs.
Prerequisites
Conditions
– You have created the VMs for installing IMGSs.
Data

FusionCompute
IMGS node name Specifies the name of the IMGS node. IMGS01
with a letter.
Management IP Specifies the IP address of the VM on which 188.100.200.40

address the IMGS is deployed.
Set the IP address to be within the
management plane network segment.
Subnet mask of the Specifies the subnet mask of the IMGS 255.255.255.0
Gateway address of Specifies the gateway address of the IMGS 188.100.200.1

Software
FusionCompute V100R003C00_IMGS.iso
Procedure
Mount a CD-ROM drive to the VM.
1 Share the folder containing the FusionCompute V100R003C00_IMGS.iso file with the
administrator of the local PC.
3 In the navigation tree on the left, expand Site, and click the names of the VMs to be deployed
with the IMGSs.
4 In the Operation area on the right, click Mount CD-ROM.
5 In the displayed dialog box, enter the ISO file path. The format of the path is \\IP address
of the local PC\name of the shared folder\name of the image file,
for example, \\182.168.5.5\soft\FusionCompute V100R003C00_IMGS.iso. The IP address
of the local PC communicates with that of the management plane.
6 Select Use the username and password of the local computer.
7 Enter the username and the password shared in Step 1.
8 Select Restart the VM now to install the OS and click OK.
Install the IMGS.

FusionCompute
9 Click Log In Using VNC.

NOTE
default. Then you must restart the VM before performing the subsequent operations.
10 Select Install and press Enter.

FusionCompute
TIP
Window:
select it.
– IP address: Enter the planned IMGS management IP address.
15 Press F12.
17 Press F12.
19 Enter the planned IMGS name, for example, IMGSO1, and press F12.
22 Press F12.
NOTE

25 Press F12.

FusionCompute

27 Select Yes.
system (OS) of the IMGS.
automatically. When the login information is displayed, the installation of the IMGS is
complete.
Unmount a CD-ROM drive from the VM.
28 On the GalaxEngine, choose VDC Management > VM and Template.
29 In the navigation tree, expand Site and click the VM on which the ESC is deployed.
30 In the Operation area on the right, select Unmount CD-ROM.
31 Click OK.
A dialog box is displayed, indicating that the system begins to unmount the CD-ROM drive.
You can view the task progress in the Task Tracing page.
32 Click OK.
Install other IMGSs.
33 Install other IMGSs.
----End
2.3.5 Installing the ESC and IMGS Based VM Templates

Scenarios
On the FusionCompute, install an Image Storage (IMGS) node and an Elastic Service Controller
(ESC) node on VMs using VM templates.
You can modify the parameters listed in Table 2-16, so that they are different from that of the
templates.
Prerequisites
Conditions
– You have installed and configured the FusionCompute.
– You have obtained and shared the VM template file, and the VM template file is accessible
to the FusionCompute. The shared template name is the same as the name of the folder in
which the template file is stored.
– You have disabled the firewall on the local PC.
Data
– Table 2-15 lists the data required for importing the template.

FusionCompute
– Table 2-16 lists the data required for creating a VM.
Table 2-15 Data required for importing the template
Template ESC template file: FusionCompute_V100R

configure file FusionCompute_V100R003C00_ESC.xml. 003C00_ESC.xml
IMGS template file:
FusionCompute_V100R003C00_IMGS.x
ml.
File path Specifies the shared path of the template file. \\192.168.100.11\Share
The path format is \\IP address of the shared
server\Name of the folder in which the
template file is located.
Username and Specifies the username and password for N/A

password logging in to the shared server.
If a user account is registered in multiple
domains, enter the username with the
specified domain name. For example, enter
Domain\w00123456.
This parameter is optional.
Table 2-16 Data required for creating a VM
Basic VM name Specifies the name of the ESC01

informatio management VM. IMGS01
n The VM name cannot start or end
with spaces or exceed 128 characters.
It cannot contain any of the following
special characters: \/'"[]<>;&=,?*#|
%~^{}$!.
Computer Specifies the computer name of the ESC01

name ESC VM or IMGS VM. IMGS01
Creation Location Specifies the host where the VM is to Host

position be created.
NIC Distributed Specify the distributed virtual switch ManagementDVS

Settings switch (DVS) and the port group to be
configured for the network interface
Port Group card (NIC). Portgroup01
IP address Specifies the management IP address N/A

of the planned ESC VM or IMGS
VM.

FusionCompute
Data Data storage Specifies the data storage selected for datastore01
storage the disk.
informatio
n
Procedure
Create a VM.
The VM and Template page is displayed.
2 Click Create VM Using Template in the Operation area on the Summary tab page.
The Import Template page is displayed.
3 Configure the template importing information.
– Template configure file: Select a template file based on the type of the node to be
installed.
– File path: The path format is \\IP address of the shared server\Name of the folder in
which the template file is located.
– Username and password: If a user account is registered in multiple domains, enter the
username with the specified domain name. For example, enter Domain\w00123456.
4 Click Next.
The VM Settings page is displayed.
5 Enter the VM name.
6 In Select a location for creating a VM, select a host to create the VM on it.
NOTE
Create VMs for deploying the active and standby ESCs on different hosts.
7 In the NIC Settings area, click in NIC 1.

The Select Port Group dialog box is displayed.
8 Select the DVS and port group for the management plane, and click OK.
9 In the Disk Settings area, click in Disk 1.

The Select Data Store dialog box is displayed.
10 Select a data store to be created, for example, datastore01, and click OK.
11 Select Synchronize with host clock in the Clock synchronization policy area, and set
CPU hot swap to Disable.
12 Select Customize using the Customization Wizard in VM Attributes, and click Next.
The Customized Settings page is displayed.
13 Enter the computer name.
The password is not required. You can use the default password Galax@8800 of user
root for logging in to the ESC and IMGS nodes. To ensure system security, change the
default password after the two nodes are installed.

FusionCompute
14 Ensure that Save as computer attributes is deselected, and click Next.

The NIC Settings page is displayed.
15 Locate the row that contains NIC 01, and click NIC Settings.
A dialog box is displayed.
16 Click Use the following IP address and set the following parameters:
– IP address: Specifies the management IP address of the planned ESC VM or IMGS
VM.
– Subnet mask
– Default gateway
17 Click OK.
18 Click Next.
The Confirm page is displayed.
19 Click Complete.
The VM creation starts.
20 Click Query Task.
You can view the creation process on the Task Center page.
----End
2.4 Software Installation in Physical Deployment
2.4.1 Installing ESC Nodes
Scenarios
Install Elastic Service Controller (ESC) nodes on physical servers.
Prerequisites
Conditions
– You have set the first boot device of the physical server on which the ESC is to be installed
to hard disk, the second boot device to network, and the third one to CD-ROM drive.
– You have obtained the BMC IP address of the physical server.
– You have obtained the username and password for logging in to the BMC system of the
physical server.
Data

FusionCompute
ESC node name Specifies the name of the ESC. ESC01

with a letter.
Management IP Specifies the IP address of the ESC 188.100.4.35

address of the ESC management network port.
node This parameter is mandatory.
Subnet mask of the Specifies the subnet mask of the ESC 255.255.255.0
Gateway address of Specifies the gateway address of the ESC 188.100.4.1

Software
FusionCompute V100R003C00_ESC.iso
Procedure
Load the ISO file.
NOTE
The following operations use Tecal RH2285 server as an example to describe how to attach and install the
image file using the remote control function of BMC system.
1 In the address box of your web browser, enter http://BMC IP address of the host, and
press Enter.
2 Log in to the BMC system of the server as instructed.
3 Click Remote Control.
The Remote Control command window is displayed.
4 On the tool bar of the Remote Control command window, click .
The Image file selection dialog box is displayed, as shown in Figure 2-8.
Figure 2-8 Image file selection dialog box
5 In the image file selection dialog box, choose Image File, and click Browse.

FusionCompute
The Open dialog box is displayed.

6 Select the image file FusionCompute V100R003C00_ESC.iso, and click Open.
7 In the image file selection dialog box, click Connect.
The virtual drive is connected to the server when Connection changes to Disconnect.
Install the ESC.
8 On the tool bar, click and select Cold Reset.
9 Click Yes to restart the server.
10 When the host begins to restart, press F11 repeatedly until the window for selecting boot
device is displayed, as shown in Figure 2-9.
Figure 2-9 Please select boot device window
11 Select CD-ROM as the boot device, for example, USB:HUAWEI DVD-ROM VM

1.1.0, and press Enter.

FusionCompute
NOTE
default. Then you must restart the VM before performing the following operations:
12 Choose Install and press Enter.

FusionCompute
TIP
Window:

select it.
– IP address: Enter the planned ESC management IP address.
17 Press F12.
19 Press F12.
21 Enter the planned ESC node name, for example, ESC01, and press F12.
24 Press F12.
NOTE


FusionCompute
27 Press F12.
29 Select Yes.
system (OS) of the ESC.
automatically. When the login information is displayed, the installation of the ESC is
complete.
30 Determine whether to deploy the ESC in the active and standby mode.
– If no, no further action is required.
Install the standby ESC.
31 Install the standby ESC.
----End
2.4.2 Installing IMGS Nodes
Scenarios
Install Image Storage (IMGS) nodes on physical servers.
Prerequisites
Conditions
– You have set the first boot device of the physical server on which the ESC is to be installed
to hard disk, the second boot device to network, and the third one to CD-ROM drive.
– You have obtained the BMC IP address of the physical server.
– You have obtained the username and password for logging in to the BMC system of the
physical server.
Data

FusionCompute
IMGS node name Specifies the name of the IMGS node. IMGS01
with a letter.
Management IP Specifies the IP address of the IMGS 188.100.4.38

address of the management network port.
IMGS This parameter is mandatory.
Subnet mask of the Specifies the subnet mask of the IMGS 255.255.255.0
Gateway address of Specifies the gateway address of the IMGS 188.100.4.1

Software
FusionCompute V100R003C00_IMGS.iso
Procedure
Load the ISO file.
NOTE
The following operations use Tecal RH2285 server as an example to describe how to attach and install the
image file using the remote control function of BMC system.
1 In the address box of your web browser, enter http://BMC IP address of the host, and
press Enter.
2 Log in to the BMC system of the server as instructed.
3 Click Remote Control.
The Remote Control command window is displayed.
4 On the tool bar of the Remote Control command window, click .
The Image file selection dialog box is displayed, as shown in Figure 2-12.
Figure 2-12 Image file selection dialog box
5 In the image file selection dialog box, choose Image File, and click Browse.

FusionCompute
The Open dialog box is displayed.

6 In the displayed dialog box, select FusionCompute V100R003C00_IMGS.iso and click
Open.
7 Click Connect.
When Connection changes to Disconnect, the virtual drive is connected to the server.
Install the IMGS.
8 On the tool bar, click and select Cold Reset.
9 Click Yes to restart the server.
10 When the host begins to restart, press F11 repeatedly until the window for selecting boot
device is displayed, as shown in Figure 2-13.
Figure 2-13 Please select boot device window
11 Select CD-ROM as the boot device, for example, USB:HUAWEI DVD-ROM VM

1.1.0, and press Enter.

FusionCompute
NOTE
default. Then you must restart the VM before performing the following operations:
12 Choose Install and press Enter.

FusionCompute
TIP
Window:

select it.
– IP address: Enter the planned IMGS management IP address.
17 Press F12.
19 Press F12.
21 Enter planned IMGS node name, for example, IMGS01, and press F12.
24 Press F12.
NOTE


FusionCompute
27 Press F12.
29 Select Yes.
system (OS) of the IMGS.
The installation takes about 10 minutes. After the installation, the server restarts
automatically. When the login information is displayed, the installation of the IMGS is
complete.
Install other IMGSs.
30 Install other IMGSs.
----End
2.5 Initial Configuration
2.5.1 Configuration Overview
Initial Configuration Process

After the FusionStack is installed, initial configuration is required. Figure 2-16 show the initial
configuration process.

FusionCompute
Figure 2-16 Initial configuration process
Start
Configuring the License Server
Adding Site Resources

Configure the active and standby
ESCs
Creating a Service Cluster

Do you want to use No
the firewall function?
Configuring Time
Yes
Synchronization and Time Zone
Configuring a Virtual Firewall

Adding an Image Server
Configuring Resource Access

Points
Configuring a Backup Server
Adding an L2Area Network

End
Initial Configuration Overview

Table 2-19 lists the configuration items and descriptions.
Table 2-19 Initial configuration overview

Initial Configuration Item Description
Configuring the License Server Configure the license server to provide licensed services
in the specified period.
Configure the active and Configure the active and standby Elastic Service
standby ESCs Controllers (ESCs) on the FusionStack to improve
system reliability.
After the configuration, users can log in to the active ESC
or the FusionStack using the floating IP address.

FusionCompute
Configuring a Virtual Firewall After performing basic configuration for the physical
firewalls, such as creating a Secure Shell (SSH) user,
configuring the Simple Network Management Protocol
(SNMP), and configuring the Huawei Redundancy
Protocol (HRP) for the active and standby firewalls,
create and configure virtual firewalls of the required
number so that users can connect to the virtual private
cloud (VPC) or VMs in the security group through an
external network.
Configuring Resource Access Add virtualization resource access points and firewall
Points access points on the FusionStack. Before adding a
virtualization resource access point, create an interface
interconnection user to access the virtualization
resources.
Adding an L2Area Network Add a layer 2 network (L2Area network), which contains
all network resources on the aggregation switches
deployed in the system.
Adding Site Resources Add site resources on the FusionCompute.
Creating a Service Cluster Create a service cluster for providing users with
virtualization resources.
Configuring Time Configure the system time synchronization and the time
Synchronization and Time Zone zone to ensure the FusionStack services run properly.
Adding an Image Server Add an image server that is used to manage images stored
on it.
Configuring a Backup Server To enhance the reliability of the FusionStack, deploy a

backup File Transfer Protocol (FTP) server for it. After
the backup FTP server is configured, core data of the
FusionStack is transmitted to it. Once a system
exception occurs, the system can be restored using the
data backup.
This configuration is required only when a backup FTP
server has been deployed.
2.5.2 Configuring the License Server

Scenarios
Configure the license server to provide licensed services in the specified period.
Prerequisites
Conditions
– You have loaded a license file to a site on the FusionCompute.

FusionCompute
– You have logged in to the FusionStack.

Data
License server IP Specifies the management IP address of the 188.100.4.31

address Virtual Resource Management (VRM)
node on the site to which the license file is
loaded. Set it to the management IP address
of the VRM if the site has only one VRM,
or to the floating IP address of the VRMs if
the site has two VRMs working in active/
standby mode.
Username Specifies the name of a user who has all administrator

licensed operation rights on the
FusionCompute.
Password Specifies the password of a user who has N/A

all licensed operation rights on the
FusionCompute.
Procedure
1 On the FusionStack, choose System > License.

The License page is displayed.
2 Click Configure License Server.
The Configure License Server dialog box is displayed.

3 Set the following configuration parameters:
– License server IP address: specifies the management IP address of the VRM on the
site to which the license file is loaded. Set it to the management IP address of the VRM
if the site has only one VRM, or to the floating IP address of the VRMs if the site has
two VRMs working in active/standby mode.
– Username: specifies the name of a user who has all licensed operation rights on the
FusionCompute.
– Password: specifies the password of a user who has all licensed operation rights on the
FusionCompute.
4 Click OK.
An information dialog box is displayed indicating that the license server is configured
successfully.

FusionCompute
5 Click OK.
----End
2.5.3 Configure the active and standby ESCs
Scenarios
Configure the active and standby Elastic Service Controllers (ESCs) on the FusionStack. After
the configuration, users can log in to the active ESC or the FusionStack using the floating IP
address.
Prerequisites
Conditions
The active and standby ESCs haven been installed.
Data
Floating IP Specifies the floating IP address of the 188.100.200.36

address active and standby ESCs. It must be an idle
IP address that belongs to the management
IP address segment planned for the ESCs.
This parameter is required only when two
ESCs are deployed on one site.
Arbitration IP Specifies the IP address that is used to 188.100.200.1

Address determine the status of the active and
standby ESCs.
This parameter is required only when two
ESCs are deployed on one site. Enter one to
three arbitration IP addresses.
The active and standby ESCs periodically
send a ping command to all arbitration IP
addresses. If the active ESC cannot ping any
arbitration IP address, but the standby ESC
can ping at least one arbitration IP address,
the active and standby switchover is
triggered.
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
can communicate with the management
plane, such as the AD server or the DNS
server.

FusionCompute
Procedure
Configure the active and standby ESCs.
NOTE
Before this configuration, ensure that both ESC nodes are powered on. During the configuration, do not
power them off. Otherwise, the system will break down.
1 Log in to the FusionStack using the management IP address of the planned active ESC.
For details, see Logging In to the FusionStack.
2 On the FusionStack, choose System > Service Configuration.
The Service Configuration page is displayed.
3 In the navigation tree on the left, choose Service and Management Node.
4 In Service list locate the row that contains ESC, click Operation, and select Configure
Deployment Mode.
– Network port: specifies the management network port of the active and standby ESCs.
– Floating IP address: specifies the floating IP address of the active and standby ESCs.
It must be an idle IP address that belongs to the management IP address segment planned
for the ESCs.
– Subnet mask: specifies the subnet mask of the floating IP address.
6 Enter the management IP address of the planned standby ESC in Peer IP address, and
click Obtain Host Name.
7 Check whether a dialog box is displayed indicating that the node names are duplicate.
8 Enter a new node name of the standby ESC in Peer node name.
9 Specifies the Arbitration IP address that is used to determine the status of the active and
standby ESCs.
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 can
communicate with the management plane, such as the AD server or the DNS server.
10 Click Modify.
11 Click OK.
The active and standby ESC configuration is complete.
----End
2.5.4 Configuring a Virtual Firewall
Scenarios
Create and configure a virtual firewall. This section uses Eudemon 1000E-X as an example to
describe how to use commands to create and configure a virtual firewall.
Figure 2-17 shows the standard networking for firewalls.

FusionCompute
Figure 2-17 Networking for firewalls
Operation and
maintenance Internet
Firewall (active) Firewall (standby)
Stack Stack
Management Service aggregation

aggregation Switch Switch
SSMC service plane

SSMC management plane
Service network (untrust zone) Service network (trust zone)

Management network (mgnt zone)
NOTE
If the Eudemon 8000E is used as the firewall, it can connect to switches using Eth-Trunk links. If the
Eudemon 1000E is used as the firewall, it can connect to switches only using physical network ports.
Prerequisites
Conditions
Before configuring the virtual firewall, you have completed the following basic configurations
for the firewall by referring to the documentation related to the Eudemon firewall version.
– Secure shell (SSH) users have been created on the firewall. This allows you to log in to the
firewall to perform basic configurations and add firewalls on the FusionStack.
– The information about the simple network management protocol (SNMP) has been
configured on the firewall. The information is used to add firewalls on the FusionStack.
– The reliability configuration, including Huawei redundancy protocol (HRP), interface
tracking, and link-group configuration, has been implemented on active and standby
firewalls.
– If the Eudemon 1000E firewall is used, you must run the undo packet sequence-kept
enable command on the system view interface to disable the packet sequence function.
You have logged in to the firewall devices using hyperterminals.
Data

FusionCompute

Virtual firewall Virtual firewall Specifies the name of a virtual vfw101

name firewall.
l The virtual firewall name can
contain only digits, letters, and
underscores (_). It must start
with a letter and cannot exceed
32 characters.
l The virtual firewall name must
be unique in the system.
Routing ID Specifies the routing ID for the 101:1

virtual firewall after the virtual
firewall is created. Otherwise, you
cannot perform the subsequent
configuration.
Sub-interface Specifies the sub-interface created 2.101

number of the on the firewall interface. It is used to
firewall bind the virtual firewall.
IP address and Specifies the IP address of the sub- 192.168.101.1

subnet mask of interface used to bind the virtual
the firewall firewall.
interface This parameter is mandatory.
Backup group Specifies the ID of a backup group. 1

ID It is used to determine the priority of
active and standby firewall so that
the active firewall can bear the
network traffic.
Backup group Specifies the IP address of a backup 192.168.101.3

IP address group. Ensure that the IP address of
the backup group and the IP address
of the firewall sub-interface belong
to the same network segment.
Workflow
Figure 2-18 shows the operation process of Configuring a Virtual Firewall.

FusionCompute
Figure 2-18 Operation process

Start
Create a virtual firewall.

Configure the service sub-interface of the uplink
trust zone for the virtual firewall.
Configure the network forwarding policy for the
virtual firewall.
Configure the OSPF instance of the
virtual firewall.
Configure the service sub-interface of the uplink
untrust domain for the virtual firewall.
Enable the traffic-restricted policy.
Configure the VM to communicate with external
networks.
Configure basic services for the service
convergence LAN switch.
Configure the management sub-interface of the
downlink mgnt domain for the virtual firewall.
Configure basic services for the management
convergence LAN switch.
Configure the VM to communicate with the
management plane of servers.
End
Procedure
Create a virtual firewall.
1 Run the following command to switch to the system view:
<Eudemon>system-view
2 Run the following command to create a virtual firewall:
[Eudemon]ip vpn-instance vpn-instance-name
For example, create a virtual firewall named vfw101.
[Eudemon]ip vpn-instance vfw101

3 Run the following command to create the routing ID of the virtual firewall:
[Eudemon-vpn-instance-vfw101]route-distinguisher vpn-route-distinguisher
For example, configure the routing ID of the virtual firewall as 101:1.
[Eudemon-vpn-instance-vfw101]route-distinguisher 101:1
The virtual firewall can be created on the active firewall and it can be synchronously created
on the standby firewall.
4 Run the following command to switch to the system view:
[Eudemon-vpn-instance-vfw101]quit
Configure the network forwarding policy for the virtual firewall.
5 Run the following commands to filter packets between trust and untrust zones for the virtual
firewall:
[Eudemon]firewall packet-filter default permit interzone vpn-instance vpn-instance-

name trust untrust direction inbound

FusionCompute

name trust untrust direction outbound
For example, run the following commands to filter default packets between trust and untrust
zones for virtual firewall vfw101:
[Eudemon]firewall packet-filter default permit interzone vpn-instance vfw101 trust
untrust direction inbound
[Eudemon]firewall packet-filter default permit interzone vpn-instance vfw101 trust
untrust direction outbound
6 Run the following commands to filter default packets between trust and mgnt zones for the
virtual firewall:
name trust mgnt direction inbound
7 Run the following commands to filter default packets between local and mgnt zones for
the virtual firewall:
name local mgnt direction inbound
Configure the service sub-interface of the uplink untrust zone for the virtual firewall.
8 Run the following command to create the Ethernet sub-interface view and then switch to
the view:
[Eudemon]interface interface-type interface-number.subinterface-number
For example, run the following command to configure the Ethernet sub-interface whose
number is 2.101 and whose type is interface GigabitEthernet:
[Eudemon]interface GigabitEthernet0/0/2.101
9 Run the following command to configure a service-plane VLAN ID of the firewall sub-
interface:
[Eudemon-interface GigabitEthernet0/0/2.101]vlan-type dot1q vlan-id
For example, run the following command to configure the service-plane VLAN whose ID
is 101:
[Eudemon-interface GigabitEthernet0/0/2.101]vlan-type dot1q 101
10 To ensure that the interface that connects the network of the virtual firewall and devices
belong to the corresponding firewall, run the following commands to bind the interface to
[Eudemon-interface GigabitEthernet0/0/2.101]ip binding vpn-instance vpn-instance-
name
[Eudemon-interface GigabitEthernet0/0/2.101]ip address ip-address mask
For example, run the following commands to bind the sub-interface to virtual firewall
vfw101 and configure the IP address of the sub-interface to be 192.168.101.1:
[Eudemon-interface GigabitEthernet0/0/2.101]ip binding vpn-instance vfw101
[Eudemon-interface GigabitEthernet0/0/2.101]ip address 192.168.101.1 255.255.255.248
11 Run the following command to configure a virtual router redundancy protocol (VRRP)
backup group and the virtual IP address of the backup group:

FusionCompute
[Eudemon-interface GigabitEthernet0/0/2.101]vrrp vrid backup group ID virtual-ip

virtual IP address of the backup group {master|slave }
For example, run the following command to configure a backup group (whose ID is 1 and
whose virtual IP address is 192.168.101.3) on the active firewall:
[Eudemon-interface GigabitEthernet0/0/2.101]vrrp vrid 1 virtual-ip 192.168.101.3
master
Configure the backup group ID and its virtual IP address on both active and standby
firewalls.
12 Run the following commands to add a service uplink port to the untrust zone of the virtual
private network (VPN):
[Eudemon]firewall zone vpn-instance vfw101 untrust
[Eudemon-zone-vfw101-untrust]add interface interface GigabitEthernet0/0/2.101
13 According to Step 8 to Step 12, configure the service sub-interface of the uplink untrust
zone for the virtual firewall on the active firewall.
Configure the VM to communicate with external networks.
14 Run the following command to switch to the view of the service LAN switch system:
<Quidway>system-view
15 Run the following command to create and run the open shortest path first (OSPF) process
on the service LAN switch:
[Quidway]ospf 1
16 Run the following command to configure static routes:
[Quidway-ospf-1]import-route static
17 Run the following command to create the OSPF area and switch to the OSPF view:
[Quidway-ospf-1]area 0.0.0.1
18 Run the following command to configure the static route of the OSPF area:
[Quidway-ospf-1–area-0.0.0.1]network 192.168.101.1 0.0.0.7
NOTE
The service-plane open shortest path first (OSPF) instances share an area corresponding to the service
area ID of the firewall.
Configure the management sub-interface of the downlink mgnt zone for the virtual firewall.
the view:
[Eudemon]interface interface GigabitEthernet0/0/3.101
20 Run the following command to configure a management-plane VLAN ID of the firewall
sub-interface:
For example, run the following command to configure the management-plane VLAN
whose ID is 201:

FusionCompute


name

22 Run the following command to configure a VRRP backup group and the virtual IP address
of the backup group:

backup group virtual IP address {master|slave }

master
firewalls.
23 Run the following commands to add a service downlink port to the mgnt zone of the VPN:
[Eudemon]firewall zone vpn-instance vfw101 mgnt
[Eudemon-zone-vfw101-mgnt]add interface interface GigabitEthernet0/0/3.101

24 According to Step 19 to Step 23, configure the management sub-interface of the downlink
untrust zone for the virtual firewall on the active firewall.
Configure the VM to communicate with the management plane of servers.
25 Run the following command to switch to the view of the service LAN switch system:
<Quidway>
26 Run the following command to create and run the OSPF process on the service LAN switch:
[Quidway]ospf 1
27 Run the following command to configure static routes:
[Quidway-ospf-1]import-route static
28 Run the following command to create the OSPF area and switch to the OSPF view:
[Quidway-ospf-1]area 0.0.0.2
29 Run the following command to configure the static route of the OSPF area:
[Quidway-ospf-1-area-0.0.0.2]network 192.168.201.1 0.0.0.7
NOTE
The management-plane OSPF instances share an area corresponding to the service area ID of the
firewall.

FusionCompute
Configure the service sub-interface of the uplink trust zone for the virtual firewall.
30 Perform the configurations based on network types.
– Perform Step 31 for the security group network.
– Perform Step 37 for the VPC network.
the view:
[Eudemon]interface interface GigabitEthernet0/0/4.101

32 Run the following command to configure a service-plane VLAN ID of the firewall sub-
interface:
For example, run the following command to configure the service-plane VLAN whose ID
is 301:


name

34 Run the following command to configure a VRRP backup group and the virtual IP address
of the backup group:

virtual IP address of the backup group {master|slave }

master
firewalls.
35 Run the following commands to add a service uplink port to the untrust zone of the virtual
private network (VPN):
[Eudemon]firewall zone vpn-instance vfw101 trust

FusionCompute
[Eudemon-zone-vfw101-trust]add interface interface GigabitEthernet0/0/4.101

36 According to Step 31 to Step 35, configure the service sub-interface of the uplink untrust
zone for the virtual firewall on the active firewall.
Go to Step 38 after this step.
37 Run the following commands to add the physical trunk interface to the trust zone.
If the physical trunk interface has been added into the trust zone when the firewall of the
VPC network was configured at the first time, this step can be ignored.
[Eudemon]firewall zone trust
[Eudemon-zone-trust]set priority 80
[Eudemon-zone-trust]add interface interface GigabitEthernet0/0/4

Configure the OSPF instance of the virtual firewall.
38 Run the following commands to send the static routes of the network address translation
(NAT) mapping address pool to the service convergence LAN switch through the uplink
service interface:
[Eudemon]ospf 1 vpn-instance vfw101
[Eudemon-ospf-1]import-route static
[Eudemon-ospf-1]area 1
[Eudemon-ospf-1-area-0.0.0.1]network 192.168.128.0 0.0.0.7 is corresponding to the IP

address network segment of the sub-interface for the virtual firewall.
39 Run the following commands to send the direct routes of the subnet to the management
convergence LAN switch through the management uplink port:
[Eudemon]ospf 1 vpn-instance vfw101
[Eudemon-ospf-1]import-route static
[Eudemon-ospf-1]area 2
[Eudemon-ospf-area-0.0.0.2]network 192.168.129.0 0.0.0.7 is corresponding to the IP

address network segment of the sub-interface for the virtual firewall.
40 According to Step 38 and Step 39, configure the OSPF instance for the virtual firewall on
the standby firewall.
Enable the traffic-restricted policy.
41 Run the following command on the active firewall to enable the traffic restricted policy:
[Eudemon]traffic-policy enable
After the policy is enabled on the active firewall, it will be automatically synchronized on
the standby firewall.
Configure basic services for the service convergence LAN switch.
42 Run the following commands to configure the service LAN switch to communicate with
service planes of the firewall and servers in the layer-2 network:
[Quidway_A]interface interface GigabitEthernet0/0/4
[Quidway_A-interface GigabitEthernet0/0/4]port hybrid tagged vlan 101

FusionCompute
[Quidway_A-interface GigabitEthernet0/0/4]quit
43 Run the following commands to enable the OSPF process of the firewall trust-zone sub-
interface:
[Quidway_A]ospf 1
[Quidway_A-ospf-1]area 1
[Quidway_A-ospf-1-area-0.0.0.2]network 192.168.128.0 0.0.0.7

Configure basic services for the management convergence LAN switch.
44 Run the following commands to configure the management LAN switch to communicate
with management planes of the firewall and servers in the layer-3 network:
[Quidway_B]interface interface GigabitEthernet0/0/3
[Quidway_B-interface GigabitEthernet0/0/4]port hybrid tagged vlan 201
[Quidway_B-interface GigabitEthernet0/0/4]quit
45 Run the following commands to enable the OSPF process of the firewall trust-zone sub-
interface:
[Quidway_B]ospf 1
[Quidway_B-ospf-1]area 1
[Quidway_B-ospf-1-area-0.0.0.2]network 192.168.128.0 0.0.0.7
----End
2.5.5 Configuring Resource Access Points
Scenarios
After the FusionStack is installed, add virtualization resource access points and firewall access
points on the FusionStack. Before adding a virtualization resource access point, create an
interface interconnection user to access the virtualization resources.
Prerequisites
Conditions
– The FusionManager has been installed, because the FusionStack manages firewalls using
the Unified Hardware Manager (UHM) that is regarded as a firewall access point. For details,
see Software Installation in the product documentation of the FusionManager.
Data

FusionCompute

Category Parameter Parameter Example Value
Virtualization Name l Specifies the name of the VRM01

resource virtualization resource
access point access point.
l This parameter is
mandatory.
IP address l Specifies the IP address 192.168.84.70

of the Virtual Resource
Management (VRM).
Set it to the management
IP address of the VRM if
the site has only one
VRM, or to the floating
IP address of the VRMs
if the site has two VRMs
working in active/
standby mode.
l If a VRM domain is to be
added, Set it to
management IP address
of the domain controller.
l This parameter is
mandatory.
Port ID l Specifies the port ID of 7070

the northbound interface
provided by the
hypervisor for the
interconnection with the
FusionStack. The
default value is 7070.
l This parameter is
mandatory.
Username l Specifies username of an administrator

administrator account of
the FusionCompute.
l This parameter is
mandatory.
Password l Specifies the password Admin@1234

of the administrator
account of the
FusionCompute.
l This parameter is
mandatory.

FusionCompute
Category Parameter Parameter Example Value
Description l Provides supplementary N/A

information about the
virtualization resource
access point.
l This parameter is
optional.
Firewall Name l Specifies the name of the fw

access point firewall access point.
l This parameter is
mandatory.
Management IP l Specifies the floating IP 192.168.84.64

Address address of the
FusionManager.
l This parameter is
mandatory.
Port l Specifies the 8088

management port ID of
the firewall access point.
The default value is
8088.
l This parameter is
mandatory.
Username l Specify the username N/A

and password for
Password logging in to the firewall
access point. The default
username is
GmUhmRest and the
default password is
Rest@GmUhm123.
l This parameter is
mandatory.
Description Provides supplementary N/A

information about the
firewall access point.
Procedure
Create an interface interconnection user.
1 On the FusionCompute, choose System Management > Rights Management.
The Rights Management page is displayed.
2 Click Add user.

FusionCompute
The Add user page is displayed.

3 Set User Type to Interface interconnection user, and set the following parameters:
– Username: specifies the name of the interface interconnection user.
– Password: specifies the password the interface interconnection user.
– Confirm password: specifies the password the interface interconnection user.
4 Select administrator in the Subrole area.
5 Set the following parameters: Mobile Number, Maximum number of concurrent logins
of a user, Email, and Description.
6 Click OK.
An information dialog box is displayed indicating that the account is added.
7 Click OK.
Add a virtualization resource access point.
8 On the FusionStack, choose System > System Configuration.
9 Click Add Virtual Access Point.
– Name: specifies the name of the virtualization resource access point.
– IP address: specifies the IP address of the VRM. Set it to the management IP address
of the VRM if the site has only one VRM, or to the floating IP address of the VRMs if
the site has two VRMs working in active/standby mode. If a VRM domain is to be
added, Set it to management IP address of the domain controller.
– Port ID: specifies the port ID of the northbound interface provided by the hypervisor
for the interconnection with the FusionStack. The default value is 7070.
– Username: specifies the name of the interface interconnection user.
– Password: specifies the password the interface interconnection user.
– Description: provides supplementary information about the virtualization resource
access point.
The username and password of the account created for Interface interconnection user.
11 Click OK.
An information dialog box is displayed indicating that the access point is added.
12 Click OK.
13 Do you want to use the firewall function?
– If yes, go to Step 14
Add a firewall access point.
14 Click Add Firewall Access Point.
15 Set the following parameters as planned:
– Name: specifies the name of the firewall access point.
– Management IP Address: specifies the floating IP address of the FusionManager.

FusionCompute
– Port: Specifies the management port ID of the firewall access point. The default value
is 8088.
– Username: specify the username for logging in to the firewall access point. The default
username is GmUhmRest.
– Password: specify the password for logging in to the firewall access point. The default
password is Rest@GmUhm123.
– Description: provides supplementary information about the firewall access point.
16 Click OK.
An information dialog box is displayed indicating that the access point is added.
17 Click OK.
----End
2.5.6 Adding an L2Area Network
Scenarios
On the FusionStack, add a layer 2 network (L2Area network), which contains all network
resources on the aggregation switches deployed in the system.
Prerequisites
Conditions
– All the created virtual firewalls have been configured based on the data plan. For details, see
Configuring a Virtual Firewall.
Data
L2Area Name Specifies the name of the L2Area L2Area01

information network.

information about the L2Area
network.
Firewall Firewall Specifies the name of the firewall uhm

information Access Point access point.

FusionCompute
Management Specifies the management IP 10.144.188.252

IP Address addresses of the active and standby
physical firewalls.
Protocol Specifies the firewall connection ssh

mode.
Username Specifies the management user sshuser

created on the physical firewall.
Password Specifies the password for logging N/A

in to the firewall.
SNMP Version Specifies the Simple Network V3

Management Protocol (SNMP)
version used by the physical
firewall.
SNMP Port Identifies the SNMP port used by 161

the firewall management. The
default port number is 161.
SNMP Specifies the SNMP 10

Timeout (s) communication timeout duration.
Read Specifies the read community name public

community for communicating with the
firewall.
Write Specifies the write community private

community name for communicating with the
firewall.
Context Specifies a collection of N/A

management information accessible
by an SNMP entity.

FusionCompute
Correlation Identifies the correlation engine for N/A

engine ID SNMP message processing,
security authentication, and access
control.
SNMP Specifies the username for logging N/A

username in to the firewall that is managed
using SNMP.
Authentication Specifies the algorithm for checking HMACMD5

algorithm whether the transmitted data is
valid.
Authentication Specifies the key for checking N/A

key whether the transmitted data is
valid.
Encrypted Specifies the algorithm for DES

algorithm encrypting transmitted data.
Encrypted key Specifies the data encryption key. N/A

Rack ID This parameter is optional. –
Subrack ID This parameter is optional. –
Public IP pool Name Specifies the name of the public IP publicIp01

pool.
Start IP Specifies the start IP address of the 10.144.185.0

Address public IP pool.
End IP Address Specifies the end IP address of the 10.144.185.200

public IP pool.

information about the public IP
pool.

FusionCompute
Virtual private Name Specifies the name of the VPC subnet01

cloud (VPC) subnet pool.
subnet pool This parameter is mandatory.
(required only
when a VPC is IP address Specifies the IP address segment of 128.4.42.0
deployed) the VPC subnet pool.
Subnet mask Specifies the IP address subnet 255.255.255.0

mask of the VPC subnet pool.

information about the VPC subnet
pool.
Procedure
Configure L2Area information.
2 In the navigation tree on the left, choose L2Area Network Resources > L2Area, and click
Add L2Area.
3 Set Name and Description for the L2Area network.
4 Click Next.
5 Check whether a firewall access point is configured.
Configure physical firewalls.
6 Click Add Physical Firewall.
The Add Physical Firewall dialog box is displayed.
7 Select a firewall access point and set the following information:
– Management IP Address: specifies the management IP address of the physical
firewall.
– Protocol: specifies the firewall connection mode.
– Username: specifies the management user created on the physical firewall.
– Password: specifies the user password for logging in to the physical firewall.
8 Determine the SNMP version to be used and configure the required SNMP information.
SNMPv2 or a later version is recommended. Table 2-25 lists the configuration information
required by each SNMP version.

FusionCompute
Table 2-25 SNMP configuration

SNMP Version Configuration Description
Parameter
V1, V2, and V3 SNMP Port Identifies the SNMP port used by
the physical firewall. The default
port number is 161.
SNMP Timeout (s) Specifies the SNMP

communication timeout duration.
V1 and V2 Read community l All functional modules of a

managed device require access
permission. If you use the read
community name for
authentication, you only have
permission to view the status of
each module.
l The default read community
name is public.
Write community l All functional modules of a

managed device require access
permission. If you use the write
community name for
authentication, you have
permission to configure or
operate each module.
l The default write community
name is public.
V3 Context Specifies a collection of

management information
accessible by an SNMP entity.
Correlation engine ID Identifies the correlation engine

for SNMP message processing,
security authentication, and access
control.
SNMP username Specifies the username for logging

in to the firewall that is managed
using SNMP.
Authentication algorithm Specifies the algorithm for

checking whether the transmitted
data is valid.
Authentication key Specifies the key for checking

whether the transmitted data is
valid.
Encrypted algorithm Specifies the algorithm for

encrypting transmitted data.

FusionCompute
SNMP Version Configuration Description

Parameter
Encrypted key Specifies the data encryption key.

– Rack ID
– Subrack ID
– Description
10 Click Add.
A dialog box is displayed indicating that the physical firewall is added.
11 Click OK.
12 Add the standby firewall by repeating Step 6 to Step 10.
13 Click Next.
Configure a public IP address pool.
14 Click Add Public IP Address Pool.
The Add Public IP Address Pool dialog box is displayed.
– Name: specifies the name of the public IP pool.
– Start IP Address: specifies the start IP address of the public IP pool.
– End IP Address: specifies the end IP address of the public IP pool.
– Description: provides supplementary information about the public IP pool.
16 Click Add.
A dialog box is displayed indicating that the physical firewall is added.
17 Click OK.
18 Click Next.
19 Determine whether to configure a VPC subnet pool.
Configure a VPC subnet pool.
20 Click Add Subnet Pool.
The Add Subnet Pool dialog box is displayed.
– Name: specifies the name of the VPC subnet pool, for example, subnet01.
– IP address: specifies the IP address segment of the VPC subnet pool.
– Subnet mask: specifies the IP address segment subnet mask of the VPC subnet pool.
– Description: provides supplementary information about the VPC subnet pool.
22 Click Add.
A dialog box is displayed indicating that the VPC subnet pool is added.
23 Click OK.

FusionCompute
24 Repeat Step 20 to Step 23 to configure another subnet pool if required.

25 Click Next.
26 Click Complete.
27 Select an operation based on the task to be performed.
– To add a L2Area network, click Add Another L2Area.
– To add site resources, click Add Site Resource Now. For details, see Adding Site
Resources.
– To enter the system configuration page, click Close.
----End
2.5.7 Adding Site Resources
Scenarios
Add site resources on the FusionStack.
Prerequisites
Conditions
The virtualization resource access point and the L2Area network have been configured.
Data

L2Area l Specifies the layer 2 network of the L2Area01

aggregation switch.
l This parameter is mandatory.
Access point l Specifies the access point for site VRM01

resources.
l If one site is used as the access point, the
access point contains only information
about the site.
l If a domain controller of a Virtual
Resource Management (VRM) domain is
used as the access point, the access point
contains information about all sites in the
VRM domain.
Site l Specifies the site to be added. Site01


FusionCompute
Description l Provides supplementary information N/A

about the site resources.
l This parameter is optional.
Procedure

2 In the navigation tree on the left, choose Site Resources > Site.
3 Click Add Site.
The Add Site dialog box is displayed.
– L2Area: identifies a created L2Area network.
– Access point: specifies a created virtualization resource access point.
– Site: specifies a site displayed under the specified access point.
– Description: provides supplementary information about the site resources.
5 Click Add.
An information dialog box is displayed indicating that the site resource is added.
6 Click OK.
----End
2.5.8 Creating a Service Cluster
Scenarios
On the FusionStack, create a service cluster for providing users with virtualization resources.
Prerequisites
Conditions
– A site has been added.
Data

Basic Name Specifies the name of the service serviceCluster01

information cluster to be created.

FusionCompute

information about the service
cluster.
Cluster Select Site Specifies the name of the site where Site 01
information the service cluster to be created is
located.
Select Cluster Specifies the name of the service Cluster 01

cluster to be created.
Data store Data Store Specifies the data store required for datastore01
providing storage resources for
VMs on the service cluster to be
created.
NOTE
l Local hard disks do not apply to
cloud infrastructure services. User
disks created on a local hard disk
can be attached to only VMs on the
host that provides the local hard
disk.
l Data stores created on a local hard
disk or a Logic unit number (LUN)
on an IP storage area network (IP
SAN) device do not support the VM
snapshot function. When selecting
data stores for a service cluster, the
selected data stores must all support
or do not support VM snapshot.
Network Pool Name Specifies the name of the VLAN LANswitch01

pool to be configured.
DVS Specifies the virtual distributed VLAN pool 01

switch (DVS) configured for the
service cluster.
VLAN Pool Specifies the available VLANs 120; 123 to 300

provided by the DVSs for use by the
service cluster.
The VLANs in this pool can only be
used by virtual private cloud (VPC)
and security group networks.

FusionCompute

information about the VLAN pool.
Security group Name Specifies the name of the security Security group
subnet group subnet. subnet 01
(required only This parameter is mandatory.
when a security
group network Subnet IP Specifies the IP address segment of 10.85.52.0
is configured) address the security group subnet.
Subnet mask Specifies the subnet mask of the 255.255.0.0

security group subnet IP address
segment.
Gateway Specifies the IP network segment 10.85.52.1

gateway of the security group
subnet.
VLAN ID Identifies the VLAN to which the 100

security group subnet belongs,
which must be a default VLAN.

information about the security
group subnet.
DHCP options Specify DHCP parameters for DHCP01

assigning IP addresses to user VMs.
Select an option in the created
DHCP options.
Select a configured DHCP option or
set it to Custom to configure
network information for user VMs.
Domain name Specifies the name of the domain to china.huawei.co

which the specified user VM is to be m
added.
This parameter is valid only when
DHCP options is set to Custom.

FusionCompute
Active DNS Specifies the IP address of the N/A

and Standby domain name server (DNS) to
DNS which the specified user VM
connects.
Active WINS Specifies the IP address of the N/A

and Standby Windows Internet Name Service
WINS (WINS) server to which the
specified user VM connects.
Procedure

2 In the navigation tree on the left, choose Cloud Services > Service Cluster.
3 Click Add Service Cluster.
4 Set Name and Description and click Next.
The Select Cluster page is displayed.
5 Choose Site > Cluster, and click Next.
6 Selected the required data store, and click Next.
NOTE
l Local hard disks do not apply to cloud infrastructure services. User disks created on a local hard
disk can be attached to only VMs on the host that provides the local hard disk.
l Data stores created on a local hard disk or a Logic unit number (LUN) on an IP storage area
network (IP SAN) device do not support the VM snapshot function. When selecting data stores
for a service cluster, the selected data stores must all support or do not support VM snapshot.
7 Enter the Network Pool name and select the required DVS from the drop-down list.
The VLANs available on the DVS are displayed in a list.
8 Enter the supported VLAN pool range based on the VLAN list information.
9 Enter the descriptive information, and click Next.
The page for configuring a security group subnet is displayed.
10 Determine whether to configure a security group subnet.
11 Click Add.
The Add Security Group Subnet dialog box is displayed.
12 Set the following security group subnet parameters:
– Name: specifies the name of the security group subnet.

FusionCompute
– Subnet IP address: specifies the IP address segment of the security group subnet.
– Subnet mask: specifies the subnet mask of the security group subnet IP address
segment.
– Gateway: specifies the gateway address of the security group subnet.
– VLAN ID: identifies the VLAN to be used by the security group subnet.
– Description: provides supplementary information about the security group subnet.
– DHCP options: specify DHCP parameters for assigning IP addresses to user VMs.
Select an option in the created DHCP options. If DHCP options is set to Custom,
specify Domain name, DNS, and WINS.
13 Click OK.
A dialog box is displayed indicating that the security group subnet is added.
14 Click OK.
15 Click Next.
16 Click Complete.
The service cluster creation progress is displayed.
17 Click Close.
----End
2.5.9 Configuring Time Synchronization and Time Zone
Scenarios
On the FusionStack, configure the system time synchronization and the time zone to ensure the
FusionStack services run properly.
Prerequisites
Conditions
– The network communication between the clock source and the system is normal.
– If multiple Network Time Protocol (NTP) servers are to be deployed, ensure that all the NTP
servers use the same upper-layer clock source so that the system times of the NTP servers
are the same.
Data

FusionCompute
Time NTP server Specifies the IP 192.168.40.3

Synchronization address of the NTP
server.
Enter one to three IP
addresses of the NTP
servers.
This parameter is
mandatory.
Time Specifies the interval 64

synchronization for time
interval (s) synchronization
(seconds).
This parameter is
mandatory.
Configure Time Time Zone Specifies the local Asia

Zone time zone of the
system. The system Beijing
determines whether
to enable the
Daylight Saving
Time (DST) based on
the time zone you set.
This parameter is
mandatory.
Procedure
Configure the time synchronization.
2 In the navigation tree on the left, choose Configure Time Zone > Time
Synchronization.
The information about the time synchronization and time zone is displayed on the right of
the page.
CAUTION
If multiple Network Time Protocol (NTP) servers are to be deployed, ensure that all the
NTP servers use the same upper-layer clock source so that the system times of the NTP
servers are the same.

FusionCompute
– NTP server: specifies the IP address of the NTP server. Enter one to three IP addresses
of the NTP servers.
– Time synchronization interval (s): specifies the interval for time synchronization
(seconds), which is two to the power of n.
4 Click Save.
5 Click OK.
An information dialog box is displayed indicating that the configuration is successful.
6 Click OK.
Configure the Time Zone.
7 In the navigation tree on the left, choose Configure Time Zone > Time Zone.
the page.
8 Configure the time zone parameters.
9 Click Save.
10 Click OK.
11 Click OK.
----End
2.5.10 Adding an Image Server
Scenarios
On the FusionStack, add an image server that is used to manage images stored on it.
Prerequisites
Conditions
– The image server has been installed.
Data
Name Specifies the name of the image server that IMGS01

is registered on the FusionStack.

FusionCompute
IP address of image Specifies the management IP address of the 188.100.200.40

server image server.
Procedure

2 In the navigation tree on the left, choose Image Server.
3 Click Add.
The Add Image Server dialog box is displayed.

– Name: specifies the name of the image server that is registered on the FusionStack.
– IP address of image server: specifies the management IP address of the image server.
5 Click Add.
An information dialog box is displayed indicating that the image server is added.
6 Click OK.
The newly added image server is displayed in the list.
----End
2.5.11 Configuring a Backup Server
Scenarios
Configure a third-party backup server to back up critical data on the Elastic Service Controller
(ESC) node. After the backup File Transfer Protocol (FTP) server is configured, critical ESC
data is automatically transmitted to it at 02:00:00 every day. If a system exception occurs, the
system can be restored using the data backup.
The configuration is required only when a backup FTP server is deployed.
Impact on the System

This operation has no adverse impact on the system.
Prerequisites
Conditions
– The ESC has been installed.
– A tool that can be used for remote access on various platforms, such as PuTTY, is available.
– You have obtained the IP address and port ID of the third-party backup server.

FusionCompute
– You have obtained the username and password for logging in to the FTP server and the user
account has the following rights: read, write, and delete files; add permission for files; create,
delete, and access sub-directories; and add permission for sub-directories.
Data
You have planned the directory where the data backup is to be stored on the backup server, for
example, /Backup/ESC/.
If multiple sites share one backup server, you are advised to set the directory to /Backup/ESC-
IP address of the ESC/ to differentiate them. IP address of the ESC refers to the ESC
management IP address when one ESC is deployed on one site, and refers to the ESC floating
IP address when two ESCs are deployed on one site.
NOTE
The data backup will be stored in /Directory of the data backup/YYYY-MM-DD_sn on the backup server.
Procedure
1 Use PuTTY to log in to the active ESC node.

Ensure that the management plane floating IP address and username gandalf are used to
establish the connection.
2 Run the following command and enter password of user root to switch to root user
interface:
su - root
3 Run the following command to disable logout on timeout:
TMOUT=0
4 Run the following command to configure the FTP backup server:
setConfig
The following information is displayed:
Should we upload the backups to ftp server? (yes/no)
5 Enter yes, and press Enter.

Please input the upload network protocol[ ftp or ftps ], press enter and
default value [ftps] :
NOTE
If you press Enter without performing the subsequent operations, the system uses the default values
displayed at the end of each command output.
6 Enter the protocol type of the FTP backup server, and press Enter.
The protocol types include ftp and ftps. You can enter a type based on the actual situation.
Please input the ftp server ip address, press enter and default value
[127.0.0.1] :
7 Enter the IP address of the FTP backup server, and press Enter.
Please input the ftp server port, press enter and default value [21] :
8 Enter the port ID of the FTP backup service, and press Enter.
Please input the ftp upload user name, press enter and default value [ftp] :

FusionCompute
9 Enter the username of the FTP backup server, and press Enter.
Please input the ftp upload user password, press enter and default value
[XXX] :
10 Enter the password of the FTP backup server, and press Enter.
Please input the ftp upload root directory, press enter and default value [/
GalaxEngineBackup/ESC/] :
11
CAUTION
If multiple sites share one FTP backup server, do not set the default root directory to the
directory where the data backup is to be stored on the backup server. Otherwise, data
backups will overwrite each other and get mixed up.
Enter the root directory where the data backup is to be stored on the FTP backup server,
and press Enter.
If you press Enter without entering any information, the root directory is set to /
GalaxEngineBackup/ESC/ by default.
Backup configure :
1.Upload network protocol : ftp
2.Ftp server IP : xxx.xxx.xxx.xxx
3.Ftp server port : xx
4.Ftp server user name : XXX
5.Ftp server user password : XXX
6.Ftp server upload root directory : XXX
Are you sure Save ? (yes/no)
12 Ensure that all configuration information is correct, enter yes, and press Enter.
The FTP backup server is configured.
----End
2.6 FAQ
2.6.1 Verifying Software Packages
Scenarios
Verify the obtained software packages using sha256deep.
NOTE
This section uses the local PC that runs Windows 7 as an example to describe how to verify software packages.
Prerequisites
Conditions

FusionCompute
You have obtained the software package to be verified, and the verification file whose name is
the same as the software package and whose file name extension is *.sha256.
Data
Data preparation is not required for this operation.
Software
You have obtained sha256deep.exe. It is a free tool, and can be obtained by visiting http://
sourceforge.net/projects/md5deep/files/ to download md5deep-x.x.zip.
NOTE
After decompressing the md5deep-x.x.zip, select the sha256deep tool whose version matches the OS of
the local PC. If the local PC runs Windows XP or Windows 7 32-bit, select sha256deep.exe. If the local
PC runs Windows 7 64-bit, select sha256deep64.exe.
Procedure
Step 1 On the local PC, choose Start > Run.
Step 2 Enter cmd, and click OK.
Step 3 Run the following command to switch to the disk containing sha256deep:
Drive letter of the drive containing sha256deep:
For example, if sha256deep is located in drive D. Run the following command:
D:
Step 4 Run the following command to switch to the directory containing sha256deep:
cd / directory containing sha256deep
For example, if sha256deep is located in the admin/test/ directory. Run the following command:
cd /admin/test/
Step 5 Run the following command to verify the software package:
sha256deep.exe -x Path of the verification file Path of the software package
For example, if the path of the verification file is FusionCompute
V100R003C00_ESC.sha256, and the path of the software package is FusionCompute
V100R003C00_ESC.iso, run the following command:
sha256deep.exe -x "D:\software\FusionCompute V100R003C00_ESC.sha256" "D:
\software\FusionCompute V100R003C00_ESC.iso"
If the following information is displayed, which does not contain the path of the software
package, the verification succeeds.
D:\>
If the following information is displayed, which contains the path of the software package, the
verification fails.
D:\software\FusionCompute V100R003C00_ESC.iso
Step 6 Check whether the path of the software package is contained in the command output.
l If yes, go to Step 7.
l If no, no further action is required.

FusionCompute
Step 7 Download the software package again.
----End
2.6.2 Logging In to the FusionStack
Scenarios
Log in to the FusionStack to manage virtual, service, and user resources in a centralized manner.

Prerequisites
Conditions
The browser for logging in to the FusionStack is available.
NOTE
The FusionStack is compatible with the following browsers:

l Internet Explorer 8.0 or later
l Mozilla Firefox 8.0 or later
This task uses Internet Explorer 8.0 as an example.
Data
IP address of the ESC node Specifies the floating IP 192.168.40.3

address of the Elastic Service
Controller (ESC) nodes if the
ESC nodes are deployed in
active/standby mode, or the
management IP address of the
ESC node if only one ESC
mode is deployed.
Username Specifies the username used for Default username in common

logging in to the FusionStack. mode: admin
Default username in single
sign-on mode: geadmin
Password Specifies the password used for Default password in common

logging in to the FusionStack. mode: Admin@123
Default password in single
sign-on mode: Admin@123

FusionCompute
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
Procedure
Enter the login page.
1 Open Internet Explorer.
2 Enter http://IP address of the ESC node, and press Enter.
3 Click Continue to this website (not recommended).
The FusionStack login page is displayed in common mode.
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.
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.
The system displays "The import was successful."
12 Click OK.
13 Click OK in the Certificate dialog box.
The GalaxEngine login page is displayed.
14 Close Internet Explorer, open it again, and log in to the FusionStack.
The configuration takes effect after Internet Explorer is restarted.
Log in to the system.

FusionCompute
15 Set the Username, Password, and Verification code, select the required User type and
Login type, and click Login.
– Common login mode: The initial login username is admin and the password is
Admin@123.
– High-security login mode: Three types of users can log in to the system in this mode:
system administrator, security administrator, and security auditor. The login username
and password are the respective user's username and password.
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 6 characters and a maximum of 32 characters.
l It must contain at least three of the following combinations:
l Lowercase letters
l Uppercase letters
l Digits
l Spaces or special characters `~!@#$%^&*()-_=+\|[{}];:'",<.>/?
The main page of the FusionCompute is displayed.
----End
2.6.3 Logging In to the FusionCompute
Scenarios
Log in to the FusionCompute to manage virtual, service, and user resources in a centralized
manner.
Prerequisites
Conditions
– The browser for logging in to the FusionCompute is available.
– The Internet Explorer or Mozilla Firefox is set properly.
NOTE
The GalaxEngine is compatible with the following browsers:

l Google Chrome 18.0 or later
Data

FusionCompute

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
VRM node if only one VRM
mode is deployed.
Username Specifies the username used for admin

logging in to the
FusionCompute.
Password Specifies the password used for Admin@123

logging in to the
FusionCompute.

Value:
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.
Procedure

2 Enter http://VRM IP address and press Enter.
If two VRM nodes are deployed, the VRM IP address is the floating IP address of the VRM
nodes. If only one VRM node is deployed, the VRM IP address is the management IP
address of the VRM mode.

FusionCompute
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.
The login page is displayed.
In the FusionCube, FusionSphere, and FusionCloud Desktop solutions, after
FusionCompute and FusionManager are deployed, you can determine whether to configure
single sign-on (SSO).
After the SSO is configured, if you open the login page of the FusionCompute, the system
switches to the login page of the FusionManager. Log in to the FusionManager as user
geadmin, you can enter the FusionCompute and perform operations. However, multiple
users cannot log in to the FusionCompute using the same account.
4 Perform the required operation based on the login page.
– If the FusionCompute login page shown in Figure 2-19 is displayed, go to Step 5.
– If the FusionManager login page shown in Figure 2-20 is displayed, go to Step 6.
Figure 2-19 FusionCompute login page

FusionCompute
Figure 2-20 FusionManager login page
Enter the username and password based on the rights management mode configured during
VRM installation.
Admin@123.
– High-security login mode: The username of the system administrator is sysadmin, the
username of the security administrator is secadmin, and the username of the security
auditor is auditor. The initial passwords are all Admin@123.
NOTE
l Lowercase letters
l Uppercase letters
l Digits
The FusionCompute operation page is displayed after you log in to the system.
The login operation is complete.
6 Set the Username and Password and select the user domain from User domain.
The default username is geadmin and password is Admin@123.
If the user fails to log in to the system the first time, Verification code is displayed under
User domain.
7 Click Login.
The FusionCompute operation page is displayed.
----End

FusionCompute
FusionStack User Guide 3 Feature Configuration
3 Feature Configuration
About This Chapter
3.1 VPC Feature Configuration

3.2 Security Group Feature Configuration
3.3 LB Feature Configuration

FusionCompute
3.1 VPC Feature Configuration
Configure resources in the virtual private cloud (VPC) to provide them for users, such as subnet
pools and bandwidth templates.
Table 3-1 lists the items to be configured.
Table 3-1 Initial configuration items
Adding a VPC Subnet Pool In the specified L2Area, add subnet resources
used for VPC services.
Configuring a Bandwidth Template Configure a bandwidth template for

providing services.
Configuring VPC Network Specifications Configure bandwidth templates for elastic IP

addresses in the VPC network and port
number ranges for the destination network
address translation (DNAT) function.
Adding Default DHCP Options Add default Dynamic Host Configuration

Protocol (DHCP) options for users, so that
users can use the specified default DHCP
options to configure the domain name server
(DNS), Windows Internet Name Service
(WINS) server, and domain for user VMs.
3.1.2 Adding a VPC Subnet Pool
Scenarios
On the FusionStack, add a virtual private cloud (VPC) subnet pool to provide subnet resources
for VPC services.
Prerequisites
Conditions
You have logged in to the FusionStack.
Data

FusionCompute
L2Area l Specifies a created L2Area. L2Area01

Name l Identifies the name of a subnet pool. SubnetPool01

IP address l Specifies the IP address segment of the 128.4.42.0

VPC subnet pool.
Subnet mask l Specifies the subnet mask of the VPC 255.255.255.0

subnet pool IP address segment.

about the VPC subnet pool.
Procedure

The System Configuration page is displayed.
2 In the navigation tree on the left, choose L2Area Network Resources > VPC Subnet
Pool.
3 Click Add Subnet Pool on the right.
The Add Subnet Pool dialog box is displayed.
– L2Area: identifies a created L2Area.
– Name: specifies the name of a subnet pool.
– IP address: specifies the IP address segment of the VPC subnet pool.
– Subnet mask: specifies the subnet mask of the VPC subnet pool IP address segment.
– Description: provides supplementary information about the VPC subnet pool.
5 Click Add.
An information dialog box is displayed indicating that the subnet pool is added.
6 Click OK.
The newly added subnet pool is displayed in the list.
----End
3.1.3 Configuring a Bandwidth Template

FusionCompute
Scenarios
On the FusionStack, configure a bandwidth template to set bandwidth for VMs.
Prerequisites
Conditions
Data
Name l Identifies the name of a bandwidth bandwidthl01

template.
Type l VPC: Specifies the bandwidth for virtual VPC

private cloud (VPC) VMs.
l Elastic IP address: Specifies the
bandwidth for VMs that provides elastic
IP addresses service.
Maximum l Specifies the maximum bandwidth for 200 kbit/s

bandwidth (kbit/s) VMs running VPC or elastic IP address
services.

about the bandwidth template.
Procedure

2 In the navigation tree on the left, choose Network Configuration > Bandwidth
Template.
3 Click Add Bandwidth Template.
The Add Bandwidth Template dialog box is displayed.
4 Configure the following parameters:
– Name: identifies the name of a bandwidth template.

FusionCompute
– Type: specifies the type of the bandwidth template. Select Elastic IP address to set the
bandwidth for VMs that provides elastic IP addresses service; select VPC to set the
bandwidth for VPC VMs.
– Maximum bandwidth (kbit/s): specifies the maximum bandwidth for VMs running
VPC or elastic IP address services.
– Description: provides supplementary information about the bandwidth template.
5 Click OK.
An information dialog box is displayed indicating that the bandwidth template is added.
6 Click OK.
The newly added bandwidth template is displayed in the list.
----End
3.1.4 Configuring VPC Network Specifications
Scenarios
On the FusionStack, configure bandwidth templates for elastic IP addresses in the VPC network
and port number ranges for the destination network address translation (DNAT) function.
Prerequisites
Conditions
Data
Elastic IP Default l Specifies the default maximum N/A

Address maximum receive bandwidth for an elastic
Configuration receive IP address.
bandwidth l This parameter is optional.
template
Default l Specifies the default maximum N/A

maximum transmit bandwidth for an elastic
transmit IP address.
template
DNAT DNAT start l Specifies the start port number to 1

Configuration port which an internal IP address is
mapped on the public network
using the destination network
address translation (DNAT)
function.

FusionCompute
DNAT end port l Specifies the end port number to 65535

which an internal IP address is
using the DNAT function.
Procedure

2 In the navigation tree on the left, choose Network Configuration > VPC Network
Specifications.
3 On the right of the page, set the following parameters:
Elastic IP Address Configuration
– Default maximum receive bandwidth template

– Default maximum transmit bandwidth template
DNAT Configuration
– DNAT start port: Enter the start port number to which an internal IP address is mapped
on the public network using the DNAT function. For example, enter 1.
– DNAT end port: Enter the end port number to which an internal IP address is mapped
4 Click Save.
5 Click OK.
----End
3.1.5 Adding Default DHCP Options
Scenarios
On the FusionStack, add default Dynamic Host Configuration Protocol (DHCP) options for
users, so that users can use the specified default DHCP options to configure the domain name
server (DNS), Windows Internet Name Service (WINS) server, and domain for user VMs.

Prerequisites
Conditions

FusionCompute

Data
Name l Identifies the name of a DHCP option. DHCP01

Domain name l Specifies the name of the domain to which china.huawei.com

the specified user VM is to be added.
Active DNS l Specifies the IP address of the active DNS 192.168.100.1

for creating user VMs.
Standby DNS l Specifies the IP address of the standby 192.168.100.2

DNS.
Active WINS l Specifies the IP address of the active 192.168.100.3

WINS server for creating user VMs.
Standby WINS l Specifies the IP address of the standby 192.168.100.4

WINS server.

about DHCP options.
Procedure

2 In the navigation tree on the left, choose Network Configuration > Default DHCP
Options.
3 Click Add Default DHCP Options on the right of the page.
The Add Default DHCP Options dialog box is displayed.
– Name: identifies the name of a DHCP option.
– Domain name: specifies the name of the domain to which a specified user VM is to be
added.

FusionCompute
– Active DNS: specifies the IP address of the active DNS for creating user VMs.
– Standby DNS: specifies the IP address of the standby DNS.
– Active WINS: specifies the IP address of the active WINS server for creating user VMs.
– Standby WINS: specifies the IP address of the standby WINS.
– Description: provides supplementary information about DHCP options.
5 Click OK.
An information dialog box is displayed indicating that the DHCP options are added.
6 Click OK.
The newly added DHCP options are displayed in the list.
----End
3.2 Security Group Feature Configuration
Configure resources in the security group network to provide them for users, such as bandwidth
templates and network specifications.
Configuring a Bandwidth Template Configure a bandwidth template for

providing services.
Configuring Security Group Network Configure bandwidth templates for elastic IP

addresses in the security group network and
port number ranges for the destination
network address translation (DNAT)
function.
Adding Default DHCP Options Add default Dynamic Host Configuration

Protocol (DHCP) options for users, so that
users can use the specified default DHCP
options to configure the domain name server
(DNS), Windows Internet Name Service
(WINS) server, and domain for user VMs.
Adding a Security Group Subnet Add subnet resources used for security group
services.
Enabling the Public IP Address Enable the public IP address to assign public
IP addresses for VMs in the security group.

FusionCompute
3.2.2 Configuring a Bandwidth Template
Scenarios
On the FusionStack, configure a bandwidth template to set bandwidth for VMs.
Prerequisites
Conditions
Data

Name l Identifies the name of a bandwidth bandwidthl01

template.
Type l Specifies the type of the bandwidth Elastic IP address

template.
l Set it to Elastic IP address to configure
the bandwidth for security group VMs
that provide elastic IP addresses service.
Maximum l Specifies the maximum bandwidth for 200 kbit/s

bandwidth (kbit/s) VMs running elastic IP address services.
Description Provides supplementary information about N/A

the bandwidth template.
Procedure

2 In the navigation tree on the left, choose Network Configuration > Bandwidth
Template.
3 Click Add Bandwidth Template.
The Add Bandwidth Template dialog box is displayed.
4 Configure the following parameters:
– Name: identifies the name of a bandwidth template.

FusionCompute
– Type: specifies the type of the bandwidth template. Select Elastic IP address to set the
bandwidth for VMs that provides elastic IP addresses service; select VPC to set the
bandwidth for VPC VMs.
– Maximum bandwidth (kbit/s): specifies the maximum bandwidth for VMs running
VPC or elastic IP address services.
– Description: provides supplementary information about the bandwidth template.
5 Click OK.
An information dialog box is displayed indicating that the bandwidth template is added.
6 Click OK.
The newly added bandwidth template is displayed in the list.
----End
3.2.3 Configuring Security Group Network
Scenarios
On the FusionStack, configure bandwidth templates for elastic IP addresses in the security group
network and port number ranges for the destination network address translation (DNAT)
function.
Prerequisites
Conditions
Data
Network L2Area l Specifies a layer 2 network. L2Area01

l N/A
Virtual l Specifies the name of the virtual vFirewall01

Firewall firewall for the security group
network.
Elastic IP Default l Specifies the default maximum N/A

Address maximum receive bandwidth for an elastic
Configuration receive IP address.
template

FusionCompute
Default l Specifies the default maximum N/A

maximum transmit bandwidth for an elastic
transmit IP address.
template
DNAT DNAT start l Specifies the start port number to 1

Configuration port which an internal IP address is
DNAT end port l Specifies the end port number to 65535

which an internal IP address is
Procedure

2 In the navigation tree on the left, choose Network Configuration > Security Group
Network Specifications.
3 Select Enable for Elastic IP address service.
The configuration parameters are displayed on the lower part of the page.
4 Select L2Area.
5 Select he virtual firewall for the security group network in the Virtual Firewall list.
6 Set the following parameters in the Elastic IP Address Configuration area:
– Default maximum receive bandwidth template
– Default maximum transmit bandwidth template
7 Set the following parameters in the DNAT Configuration area:
– DNAT start port: Enter the start port number to which an internal IP address is mapped
– DNAT end port: Enter the end port number to which an internal IP address is mapped
8 Click Save.
9 Click OK.
----End
3.2.4 Adding Default DHCP Options

FusionCompute
Scenarios
On the FusionStack, add default Dynamic Host Configuration Protocol (DHCP) options for
users, so that users can use the specified default DHCP options to configure the domain name
server (DNS), Windows Internet Name Service (WINS) server, and domain for user VMs.

Prerequisites
Conditions
Data

Name l Identifies the name of a DHCP option. DHCP01

Domain name l Specifies the name of the domain to which china.huawei.com

the specified user VM is to be added.
Active DNS l Specifies the IP address of the active DNS 192.168.100.1

for creating user VMs.
Standby DNS l Specifies the IP address of the standby 192.168.100.2

DNS.
Active WINS l Specifies the IP address of the active 192.168.100.3

WINS server for creating user VMs.
Standby WINS l Specifies the IP address of the standby 192.168.100.4

WINS server.

about DHCP options.
Procedure

FusionCompute

2 In the navigation tree on the left, choose Network Configuration > Default DHCP
Options.
3 Click Add Default DHCP Options on the right of the page.
The Add Default DHCP Options dialog box is displayed.
– Name: identifies the name of a DHCP option.
– Domain name: specifies the name of the domain to which a specified user VM is to be
added.
– Active DNS: specifies the IP address of the active DNS for creating user VMs.
– Standby DNS: specifies the IP address of the standby DNS.
– Active WINS: specifies the IP address of the active WINS server for creating user VMs.
– Standby WINS: specifies the IP address of the standby WINS.
– Description: provides supplementary information about DHCP options.
5 Click OK.
An information dialog box is displayed indicating that the DHCP options are added.
6 Click OK.
The newly added DHCP options are displayed in the list.
----End
3.2.5 Adding a Security Group Subnet
Scenarios
On the FusionStack, add a security group subnet to provide network resources for security group
services.
Prerequisites
Conditions
Data
Name l Identifies the name of a security group seg_subnet01

subnet.

FusionCompute
Subnet IP address l Indicates the IP address segment of the 128.4.41.0

security group subnet.
Subnet mask l Specifies the subnet mask of the security 255.255.255.0

group subnet IP address segment.
Gateway l Specifies the gateway address of the 128.4.41.1

security group subnet.
VLAN ID l Specifies the virtual local area network 1301

(VLAN) ID of the security group subnet.
The VLAN ID must be selected from the
displayed default list.

about the security group subnet.
DHCP options l Specifies the DHCP configuration for DHCP01

user VMs in security groups.
Domain name Specifies the name of the domain to which the china.huawei.com
specified user VM is to be added. This
parameter is valid only when DHCP
options is set to Custom.
Active and standby Specify the IP addresses of the active and N/A
DNSs standby domain name servers (DNSs) to
which the specified user VM connects. The
parameters are valid only when DHCP
options is set to Custom.
Active and standby Specify the IP addresses of the active and N/A
WINSs standby Windows Internet Name Service
(WINS) servers to which the specified user
VM connects. The parameters are valid only
when DHCP options is set to Custom.
Procedure


FusionCompute
2 In the navigation tree on the left, choose Cloud Service > Add Service Cluster > Cluster
name.
3 Click Add Security Group Subnet on the Security Group Subnet tab page.
The Add Security Group Subnet dialog box is displayed.
4 Set the following subnet parameters:
– Name: identifies the name of a security group subnet.
– Subnet IP address: specifies the IP address segment of the security group subnet.
– Subnet mask: specifies the subnet mask of the security group subnet IP address
segment.
– Gateway: specifies the gateway address of the security group subnet.
– VLAN ID: specifies the virtual local area network (VLAN) ID of the security group
subnet. The VLAN ID must be selected from the displayed default list.
– Description: provides supplementary information about the security group subnet.
– DHCP options: specifies the DHCP configuration for user VMs in security groups.
Select an option in the created DHCP options. If it is set to Custom, specify Domain
name, DNS, and WINS.
5 Click OK.
An information dialog box is displayed indicating that the security group subnet is added.
6 Click OK.
The newly added security group subnet is displayed in the list.
----End
3.2.6 Enabling the Public IP Address
Scenarios
On the FusionStack, enable the public IP address for VMs in the security group.

Prerequisites
Conditions
Data
Procedure

2 In the navigation tree on the left, choose Public IP Address.
3 Select Enable public IP address.

FusionCompute
4 Click Save.
5 Click OK.
----End
3.3 LB Feature Configuration

The load balancer (LB) feature provides load balancing services for tenants, so that users can
apply for virtual load balancers and associate them with their hosts. Based on the customized
load balancing policies, the obtained load balancer evenly sends service requests to associated
hosts to enhance service stability and reliability.
Registering an LB VM Image Register an LB VM image so that users can

use the image to create LB VMs.
Configuring the LB Manager Configure the LB Manager for one Elastic

Service Controller (ESC) system to provide
management services, such as real-time
resource monitoring, LB life cycle
management, Secure Sockets Layer (SSL)
certificate management, LB-VM association
management, listener management, session
persistence, traffic statistics, and health
check.
Adding LB Instance Specifications Add LB instance specifications, which

include the maximum concurrent logins per
user and the maximum concurrent logins for
an LB instance. The specifications are
required when users add LB VM
specifications.
Adding LB VM Specifications Add LB VM specifications, which include

LB instance specifications, images, CPUs,
memory, and disk capacity, so that users can
use the specifications when they create LB
VMs.
Adding a Management Subnet Add a management subnet, so that users can

use the subnet when they create LB VMs.
Adding a Service Subnet Add a service subnet, so that users can use the
subnet when they create LB VMs.

FusionCompute
Configuring the LB Instance Limit Configure the maximum number of LB

instances for a service cluster.
3.3.2 Registering an LB VM Image

Scenarios
On the FusionStack, register a load balancer (LB) VM image so that users can use the image
to create LB VMs.

Prerequisites
Conditions
– The LB VM image is available on the local PC.
Data

Image Name Specifies the name of the 84lb-manager

image to be registered.
This parameter is
mandatory.
OS Type Specifies the type of the Novell SUSE Linux

operating system (OS) on Enterprise Server 11 SP1
the LB VM image. 64bit
This parameter is
mandatory.
Image Type Specifies the type of the LB vhd

VM image.
This parameter is
mandatory.
Description Provides supplementary 192.168.84.60

information about the LB
VM image.

FusionCompute
Tools
You have obtained WinSCP.
Software
– FusionCompute V100R003C00_SLB.zip
– FusionCompute V100R003C00_SLB.zip.sha256
Procedure
1 Decompress the image file FusionCompute V100R003C00_SLB.zip on the local PC.

Ensure that the obtained xml and vhd files are in the
FusionCompute_V100R003C00_SLB folder.
2 Use WinSCP to copy the GalaX_Engine_V100R003C00_SLB folder to /image/base/
omsportal on the image storage (IMGS) node.
NOTE
If the /image/base/ directory does not contain the omsportal folder, create a folder named
omsportal in the directory.
3 On the FusionStack, choose Service Catalog.
The Service Catalog page is displayed.
4 Locate the row that contains the image to be registered, choose Operation, and click
Register Image.
– Image Name: specifies the name of the image to be registered.
– OS Type
– Image Type: specifies the type of the LB VM image. Set it to vhd for LB VMs.
6 Click Register Image.
An information dialog box is displayed indicating that the image is registered.
7 Click OK.
----End
3.3.3 Configuring the LB Manager

Scenarios
On the FusionStack, configure the load balancer (LB) Manager to provide management
services, such as real-time resource monitoring, LB life cycle management, LB-VM association
management, listener management, session persistence, traffic statistics, and health check.

Prerequisites
Conditions

FusionCompute

Data

Name Specifies the name of the LB lb-manager01

Manager.
This parameter is
mandatory.
IP Specifies the IP address of 192.168.84.60

the ESC. Set it to the
management IP address of
the ESC if the site has only
one ESC, or to the floating
IP address of the ESCs if the
site has two ESCs working
in active/standby mode.
This parameter is
mandatory.
Procedure

2 In the navigation tree on the left, choose LB Instance > LB Manager Management.
3 Click Add.
– Name: specifies the name of the LB Manager.
– IP: specifies the IP address of the ESC. Set it to the management IP address of the ESC
if the site has only one ESC, or to the floating IP address of the ESCs if the site has two
ESCs working in active/standby mode.
5 Click OK.
6 Click OK.
The newly configured LB Manager is displayed in the list.
----End

FusionCompute
3.3.4 Adding LB Instance Specifications
Scenarios
On the FusionStack, configure load balancer (LB) instance specifications, which include the
bandwidth, maximum concurrent logins per user, and the maximum concurrent logins for an LB
instance.

Prerequisites
Conditions
Data
Name Specifies the name of the LB lbs_temp

instance.
This parameter is
mandatory.
Bandwidth (Mbit/s) Specifies the upper 10

bandwidth limit for an LB
instance. The value range is
0 to 10240. 0 indicates that
the bandwidth is not limited.
Max. concurrent logins per Specifies the maximum 10000

user number of concurrent logins
for a user every second.
This parameter is
mandatory.
Max. concurrent logins Specifies the maximum 5000

number of concurrent logins
supported by the system.
This parameter is
mandatory.
Procedure

FusionCompute

2 In the navigation tree on the left, choose LB Instance > LB Instance Specifications.
3 Click Add.
– Name: specifies the name of the LB instance.
– Bandwidth (Mbit/s): specifies the upper bandwidth limit for an LB instance. The value
range is 0 to 10240. 0 indicates that the bandwidth is not limited.
– Max. concurrent logins per user: specifies the maximum number of concurrent logins
for a user.
– Max. concurrent logins: specifies the maximum number of concurrent logins
supported by the system.
5 Click OK.
A dialog box is displayed indicating that the LB instance specifications are added.
6 Click OK.
The newly added LB instance specifications are displayed in the list.
----End
3.3.5 Adding LB VM Specifications
Scenarios
On the FusionStack, add (load balancer) LB VM specifications, so that users can use the
specifications when they create LB VMs.

Prerequisites
Conditions
– The LB instance specifications have been created.
Data
Name l Specifies the name of a lbvm_temp

set of the LB VM
specifications.
l This parameter is
mandatory.

FusionCompute
LB instance specifications l Specifies a set of LB lbs_temp

instance specifications.
Select one set from the
created specifications.
l This parameter is
mandatory.
Image l Specifies the ID of the FusionCompute_V100R003

image for creating an LB C00_SLB
VM.
l This parameter is
mandatory.
CPU l Specifies the number of 2

the CPUs on an LB VM.
l This parameter is
mandatory.
Memory size (MB) l Specifies the memory 2048

size of an LB VM.
l This parameter is
mandatory.
Disk size (GB) l Specifies the disk size of 10

an LB VM. The value
range is 5 to 30720.
l This parameter is
mandatory.
Procedure

2 In the navigation tree on the left, choose LB Instance > LB VM Specifications.
3 Click Add.
– Name: specifies the name of a set of the LB VM specifications.
– LB instance specifications: specifies the LB instance template. Select one from the
created templates.
– Image: specifies the ID of the image for creating an LB VM.
– CPU: specifies the specifications of the CPU on an LB VM.
– Memory size (MB): specifies the memory size of an LB VM.
– Disk size (GB): specifies the disk size of an LB VM. The value range is 5 to 30720.
5 Click OK.

FusionCompute
A dialog box is displayed indicating that the LB VM specifications are added.

6 Click OK.
The newly added LB VM specifications are displayed in the list.
----End
3.3.6 Adding a Management Subnet
Scenarios
On the FusionStack, add a management subnet, so that users can use the subnet when they create
LB VMs.

Prerequisites
Conditions
Data

Site Identifies the ID of the site to which the site-482A09CD

management subnet belongs.
Name Specifies the name of the management managesb1

subnet.
Subnet IP address Specifies the IP address segment 128.4.50.0

planned for the management subnet.
Subnet mask Specifies the mask of the management 255.255.255.0

subnet.
Gateway Specifies the gateway address of the 128.4.50.1

management subnet.

FusionCompute
VLAN ID Identifies the ID of the virtual local area 1348

network (VLAN) used by the
management subnet. Select a VLAN in
the VLAN pool on the distributed
virtual switch (DVS) used by the service
cluster. Ensure that this VLAN is not in-
use.
Description Provides supplementary information N/A

about the management subnet.
Procedure

2 In the navigation tree on the left, choose LB Instance > Management Subnet.
3 Click Add.
The Add LB Management Subnet page is displayed.
4 Set the following subnet parameters:
– Site: identifies the ID of the site to which the management subnet belongs.
– Name: specifies the name of the management subnet.
– Subnet IP address: specifies the IP address segment of the planned management
subnet.
– Subnet mask: specifies the mask of the management subnet.
– Gateway: specifies the gateway address of the management subnet.
– VLAN ID: identifies the ID of the VLAN used by the management subnet. Select a
VLAN in the VLAN pool on the DVS used by the service cluster. Ensure that this VLAN
is not in-use.
– Description
5 Click Add.
A dialog box is displayed indicating that the management subnet is added.
6 Click OK.
The newly added management subnet is displayed in the list.
----End
3.3.7 Adding a Service Subnet
Scenarios
On the FusionStack, add a service subnet, so that users can use the subnet when they create LB
VMs.

FusionCompute

Prerequisites
Conditions
Data

Site Identifies the ID of the site to which the site-482A09CD

service subnet belongs.
Name Specifies the name of the service seifsubnet1

subnet.
Subnet IP address Specifies the IP address segment 128.4.47.0

planned for the service subnet.
Subnet mask Specifies the mask of the service 255.255.255.0

subnet.
Gateway Specifies the gateway address of the 128.4.50.1

service subnet.
VLAN ID Identifies the ID of the virtual local area 1345

network (VLAN) used by the service
subnet. Select a VLAN in the VLAN
pool on the distributed virtual switch
(DVS) used by the service cluster.
Ensure that this VLAN is not in-use.
Description Provides supplementary information N/A

about the service subnet.
Procedure

FusionCompute
2 In the navigation tree on the left, choose LB Instance > Service Subnet.
3 Click Add.
The Add Service Subnet page is displayed.
– Site: identifies the ID of the site to which the service subnet belongs.
– Name: specifies the name of the service subnet.
– Subnet IP address: specifies the IP address segment of the planned service subnet.
– Subnet mask: specifies the mask of the service subnet.
– Gateway: specifies the gateway address of the service subnet.
– VLAN ID: identifies the ID of the VLAN used by the service subnet. Select a VLAN
in the VLAN pool on the DVS used by the service cluster. Ensure that this VLAN is
not in-use.
– Description
5 Click Add.
A dialog box is displayed indicating that the service subnet is added.
6 Click OK.
The newly added service subnet is displayed in the list.
----End
3.3.8 Configuring the LB Instance Limit
Scenarios
On the FusionStack, configure the maximum number of load balancer (LB) instances for a
service cluster.

Prerequisites
Conditions
Data

Service cluster Specifies name of the service cluster cluster-sg

that provides LB instances.
LB instance limit Specifies the upper limit of the LB 10

instances.

FusionCompute
Procedure

2 In the navigation tree on the left, choose LB Instance > LB Instance Limit.
3 Click Configure.
– Service cluster: specifies name of the service cluster that provides LB instances.
– LB instance limit: specifies the upper limit of the LB instances.
5 Click OK.
6 Click OK.
----End

FusionCompute
FusionStack User Guide 4 Operation and Maintenance
4 Operation and Maintenance
About This Chapter
4.1 Quick Start

4.2 Image Management
4.3 Configuration Management
4.4 Image Server Management
4.5 Operation Log Management
4.6 Subscription Management
4.7 User Management
4.8 Health Check

FusionCompute
4.1 Quick Start

4.1.1 About FusionStack
O&M engineers can use a web user interface (WebUI) to access the FusionStack to maintain
the entire system by performing O&M operations, such as resource monitoring and management
and system management.
4.1.2 Logging In to the System
Logging In to the FusionStack
Scenarios
Log in to the FusionStack to manage virtual, service, and user resources in a centralized manner.

Prerequisites
Conditions
The browser for logging in to the FusionStack is available.
NOTE
The FusionStack is compatible with the following browsers:

This task uses Internet Explorer 8.0 as an example.
Data
IP address of the ESC node Specifies the floating IP 192.168.40.3

address of the Elastic Service
Controller (ESC) nodes if the
ESC nodes are deployed in
ESC node if only one ESC
mode is deployed.

FusionCompute
Username Specifies the username used for Default username in common

logging in to the FusionStack. mode: admin
Default username in single
sign-on mode: geadmin
Password Specifies the password used for Default password in common

logging in to the FusionStack. mode: Admin@123
Default password in single
sign-on mode: Admin@123

Value:
Procedure
Enter the login page.
2 Enter http://IP address of the ESC node, and press Enter.
The FusionStack login page is displayed in common mode.
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.
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.
9 Click Next.
The Completing the Certificate Import Wizard dialog box is displayed.
10 Click Finish.

FusionCompute
The Security Warning dialog box is displayed.

11 Click Yes.
The system displays "The import was successful."
12 Click OK.
13 Click OK in the Certificate dialog box.
The GalaxEngine login page is displayed.
14 Close Internet Explorer, open it again, and log in to the FusionStack.
The configuration takes effect after Internet Explorer is restarted.
Log in to the system.
Admin@123.
– High-security login mode: Three types of users can log in to the system in this mode:
system administrator, security administrator, and security auditor. The login username
and password are the respective user's username and password.
NOTE
l Lowercase letters
l Uppercase letters
l Digits
The main page of the FusionCompute is displayed.
----End
4.1.3 Function Description
System
System Configuration
The System Configuration function allows you to configure system resources and manage
service clusters.

FusionCompute
System Configuration
Function Description Path Reference
Manage You can manage resource access System Software

resource points to add virtual resource Management > Commissioning
access points access points and firewall access System
points to the system. Configuration
Manage layer You can manage layer 2 network Software

2 network resources. Commissioning
(L2Area
network)
resources
Configure You can configure network

network specifications, including Feature
specifications bandwidth templates, security Configuration
groups, virtual private cloud
(VPC) network specifications,
and Dynamic Host
Configuration Protocol (DHCP)
specifications.
Managing site You can manage site resources in Software

resources a virtual environment. Commissioning
Manage You can manage service Software

service clusters. Commissioning
clusters

FusionCompute
Interface View
Figure 4-1 System Configuration
Service Configuration
The Service Configuration function allows you to adjust system service configurations.
Service Configuration
Configure You can configure the active/ System Software

service and standby relationship between Management > Commissioning
management Elastic Service Controller (ESC) Service
nodes nodes during software Configuration
installation.
Configure the You can configure the logo Operation and

system logo displayed on the system page. Maintenance >
Configuration
Management

FusionCompute
Configure the You can configure the LB Feature

load balancer Manager to provide Configuration
(LB) Manager management services, such as
real-time resource monitoring,
LB life cycle management,
Secure Sockets Layer (SSL)
certificate management, LB-VM
association management,
listener management, session
persistence, traffic statistics, and
health check.
Configure LB You can configure the Feature

instance bandwidth used by hibernated Configuration
specifications VMs to prevent them from
occupying excessive system
bandwidth and reducing the
performance of running VMs.
Configure LB You can configure the maximum Feature

VM number of connections and Configuration
specifications throughput for the LB service.
Add a You can add a management Feature

management subnet for an LB VM. Configuration
subnet
Add a service You can add a service subnet for Feature

subnet an LB VM. Configuration
Configure the You can configure the maximum Feature

LB instance number of LB instances for a Configuration
limit service cluster.
Manage the You can view the LB service list. -

LB service
Configure the You can configure the FTP Operation and

charging server and enable the charging Maintenance >
function function. Configuration
Management
Manage image You can manage image servers. Operation and

servers Maintenance >
Image Server
Management
Configure a You can configure mail server Operation and

subscription information used for Maintenance >
service subscription services. Configuration
Management

FusionCompute
Configure You can configure the domain Operation and

domain user's server authentication Maintenance >
authentication information for logging in to the Configuration
information system. Management
Configure the You can configure the session Operation and

session timeout duration. If users do not Maintenance >
timeout perform any operation within the Configuration
duration configured session timeout Management
duration, they automatically log
out of the system.
Configure the You can enable the public IP Feature

public IP address function so that VMs in Configuration
address switch a security group can obtain
public IP addresses.
Configure Configure a Network Time Operation and

time Protocol (NTP) clock source to Maintenance >
synchronizatio synchronize clocks on all VMs Configuration
n and management nodes at a site Management
with the NTP clock source.
Synchronize You can forcibly synchronize Operation and

time forcibly the system time with the clock Maintenance >
source. Configuration
Management
Select a time You can select the time zone of Operation and
zone the system. Maintenance >
Configuration
Management

FusionCompute
Interface View
Figure 4-2 Service Configuration
Operation Log
The Operation Log function allows you to query and export user operation records.
Operation Log Management

View You can view user operation logs System > Operation and
operation logs to trace historical operations Operation Log Maintenance >
performed by a user in the Operation Log
system. Management
Export You can export operation logs to

operation logs a local directory.

FusionCompute
Interface View
Figure 4-3 Operation Log Management
Rights Management
The Rights Management function allows you to manage users, roles, and password policies.
User Management
Manage users You can create users, modify System > Rights Operation and
user attributes, modify or reset Management > Maintenance >
user passwords, lock users, and User User
assign different roles for Management Management
different users to meet their
environment control
requirements.
Manage roles You can create and modify the

operation permissions of roles to
meet different users'
environment control
requirements.

FusionCompute
Password Policy
Configure You can manage user password System > Rights Operation and
password configuration policies in a Management > Maintenance >
policies system. Password Policy User
Management
Interface View
Figure 4-4 User Management

FusionCompute
Figure 4-5 Password Policy
Subscription Center
The Subscription Center function allows you to subscribe to alarm information.
Subscription Management
Configure You can configure mail server System > Operation and
mail server information used for Subscription Maintenance >
information subscription services. Center Subscription
Management
Configure You can configure subscription
subscription contents to determine which
contents alarms are sent to a specified
mail box for timely and efficient
system maintenance.

FusionCompute
Interface View
Figure 4-6 Subscription Management
License
The License function allows you to query and update license authorization information.
License Management
Query license You can query license System > License Software
information authorization information and Commissioning
configuration data so that you
can purchase or update a license
to obtain service usage
permission or prolong service
validity period before the current
license expires.
Configure the You can configure the license

license server server to obtain license
authorization information.

FusionCompute
Interface View
Figure 4-7 License Management
Service Catalog
Image
The Image function allows you to manage VM images.
Image Management
Manage You can manage images to Service Catalog > Operation and
images provide image resources used for Image Maintenance >
creating VMs for users. Image Image
management operations include Management
registering, deregistering,
freezing, and unfreezing images.

FusionCompute
Interface View
Figure 4-8 Image Management
Alarm
Alarm
The Alarm function allows you to query and handle alarms.
Alarm Management
View alarms You can view alarms to locate Alarm Operation and
and troubleshoot system faults in Maintenance >
a timely manner. Health Check
Export alarms You can export historical alarms

to a local directory.
Manually You can manually clear an alarm

clear an alarm that is not automatically cleared
after the fault is corrected to
facilitate future maintenance.

FusionCompute
Interface View
Figure 4-9 Alarm Management
4.2 Image Management
4.2.1 Making an Image
Scenarios
Make an image (also called a template) using an existing VM on the FusionCompute. This
image will be used for creating VMs.

Prerequisites
Conditions
You have logged in to the FusionCompute.
Data

FusionCompute

Name Specifies the name for the image file after it template01
is exported.
Folder Specifies the directory where the image file 192.168.80.5:/image/

is saved on the image server. The path to the base/omsportal/
directory is as follows: image server IP
address:/image/storage directory/omsportal/
NOTE
If /image/storage directory/ does not contain an
omsportal folder, create a folder named
omsportal in the directory.
Procedure
Create a VM.
1 Create a VM used for making an image of the required specifications on the
FusionCompute.
For details, see VM Creation in the Virtual Machine Management Guide.
Convert the VM to a template.
3 In the navigation tree on the left, right-click the VM to be converted, and choose Safely
stop.
4 When the VM status changes to Stopped, right-click the VM, and choose Convert to
Template.
5 Click OK.
An information dialog box is displayed.
6 Click OK.
The VM is converted to a template if the VM icon in the navigation tree changes from
to .
Export the template.
7 Right-click the template, and choose Export Template.
The Export Template page is displayed.
8 Select NFS from the Protocol drop-down list.
9 In the Name box, specify the name for the exported image file.
10 In the Folder box, specify the image server directory for saving the image file. The path
to the directory is as follows:
Image server IP address:/image/storage directory/omsportal/

FusionCompute
For example: 192.168.80.5:/image/base/omsportal/

11 Determine whether to overwrite an existing template with the same name in the specified
directory.
12 Select Overwrite existing template.
13 Click OK.
14 Click Query Task.
The Task Center page is displayed, where you can view the template exporting progress.
----End
4.2.2 Registering an Image
Scenarios
Register an image file on the FusionStack, providing a complete copy of the system disk
required for creating VMs.

Prerequisites
Conditions
– The image file to be registered has been saved in the /image/storage directory/omsportal/
directory on the image server.
Data
Image Name Specifies the name registered for the image. image001
OS Type Specifies the operating system (OS) version Windows Server 2008
for the VMs that can be created using the Enterprise 32bit
image to be registered.
Image Type Specifies the image type, which can only be vhd
vhd.

FusionCompute
Description Provides supplementary information about N/A

the image.
Procedure

2 In the navigation tree on the left, choose Image.
An image list is displayed on the right.
3 Locate the row that contains the image to be registered, click Operation, and select
Register.
The Register Image dialog box is displayed.
4 Set the following parameters based on the data in Table 4-3:
– Image Name: specifies the name of the image to be registered.
– OS Type: specifies the operating system type for the image.
– Image Type: specifies the image type, which can only be vhd.
– Description: provides supplementary information about the image.
5 Click Register.
An information dialog box is displayed, indicating that the image is registered.
6 Click OK.
----End
4.2.3 Deregistering or Deleting an Image
Scenarios
Deregister or delete an image on the FusionStack. A deregistered image will become available
only after it is registered again. A deleted image is removed from the image server permanently.
Before deregistering or deleting an image, check that the image is no longer needed.

Prerequisites
Conditions
– The name of the image to be deregistered or deleted has been obtained.
Data

FusionCompute
Procedure
Deregister an image.
NOTE
To delete a registered image, you must first deregister it.

3 Locate the row that contains the image to be deregistered, click Operation, and select
Deregister.
4 Click OK.
An information dialog box is displayed, indicating that the image is deregistered.
5 Click OK.
6 Determine whether to delete the image file.
Delete the image.
9 Locate the row that contains the image file to be deleted, click Operation, and select
Delete.
10 Click OK.
An information dialog box is displayed, indicating that the image is deleted.
11 Click OK.
----End
4.2.4 Freezing or Unfreezing an Image
Scenarios
Freeze or unfreeze an image on the FusionStack.
You may perform this operation to update a registered image file. The general procedure is as
follows:
1. On the FusionStack, freeze the image file (also called a template) you need to update.
2. On the FusionCompute, convert the template to a VM, reconfigure the software on the
VM, and then convert the VM back to a template. Then, export the template to the image

FusionCompute
server. When you export the template, set Name and Folder to be the same as those for
the old template, and select Overwrite existing template.
3. On the FusionStack, unfreeze the image file.
To modify an image file, you can first freeze the image, usage an image file of the same name
to replace the frozen image file, and then unfreeze the image.

Prerequisites
Conditions
– The name of the image to be frozen or unfrozen has been obtained.
Data
Procedure
1 Choose the operation you need to perform.

– To freeze an image, perform Step 2.
– To unfreeze an image, perform Step 5.
Freeze an image.
3 Locate the row that contains the image to be frozen, click Operation, and select Freeze.
An information dialog box is displayed indicating that the image is frozen.
4 Click OK.
No further action is required.
Unfreeze an image.
6 Locate the row that contains the image to be unfrozen, click Operation, and select
Unfreeze.
An information dialog box is displayed indicating that the image is unfrozen.
7 Click OK.
----End
4.3 Configuration Management

FusionCompute
4.3.1 Configuring the System Logo

Scenarios
On the FusionStack, configure the system logo. The configured logo will be displayed when
you log in to the system next time.
Prerequisites
Conditions
– The logo file to be uploaded is available.
– For the logo displayed in the address box of the browser, prepare an ICO image with a
size of 16 x 16.
– For the logo displayed on the login page, Version information page, and the upper-left
corner of the system page, prepare a PNG image with a size of 48 x 48.
Data
Procedure
1 On the FusionStack, choose System Management > Service Configuration.

2 In the navigation tree on the left, click System Logo.
Two system logos are displayed on the right of the page. One logo is for display in the
address bar, and the other is for display on the login page, the Version Information page,
and the upper right corner of system pages.
The methods of changing these two logos are the same. The following steps use the logo
for display in the address box as an example.
3 Click Modify under Displays the system logo in the address box.
4 Click Browse.
5 Select the logo file to be uploaded and click Open.
6 Click Confirm.
7 Click OK.
The system logo is configured.
----End
4.3.2 Configuring the Charging Function
Scenarios
Configure the file transfer protocol (FTP) server that receives charging bills from the billing
system and enable the charging function on the FusionStack. With the charging function

FusionCompute
enabled, the system periodically generates charging bills for service resources, including VM,
volume, elastic IP address, virtual LAN (VLAN), virtual private cloud (VPC), security group,
VM snapshot, and LB instance, and sends the charging bills to the configured FTP server.

Prerequisites
Conditions
– The ESC node is properly communicating with the third-party FTP server and traffic
measurement device.
Data

Operation Parameter Description Example Value
FTP server Protocol Specifies the communication FTP

protocol between the billing system
and the FTP server, which can be
FTP, FTPS-SSL, and FTPS-TLS.
IP address Specifies the IP address of the FTP 192.168.83.6

server.
Port Specifies the FTP service port. 21
Path Specifies the directory where the /bill/

charging bills are saved.
User name Specifies the user name and N/A

password for logging in to the FTP
Password server.
Enable Traffic Specifies the primary IP address of 192.168.83.7

charging by measurement the traffic measurement device.
traffic device primary
IP
Traffic Specifies the secondary IP address 192.168.83.8

measurement of the traffic measurement device.
device
secondary IP
Procedure

FusionCompute

2 In the navigation tree on the left, choose Charging.
3 Select Enable charging.
4 In the FTP server area, set the following parameters:
– Protocol: specifies the communication protocol between the billing system and the FTP
server.
– IP address: specifies the IP address of the FTP server.
– Port: specifies the FTP service port.
– Path: specifies the directory where the charging bills are saved.
– User name: specifies the user name for logging in to the FTP server.
– Password: specifies the password for logging in to the FTP server.
5 Determine whether to enable charging by traffic.
6 Select Enable charging by traffic, and specify the IP addresses of the traffic measurement
device, including:
– Traffic measurement device primary IP
– Traffic measurement device secondary IP
7 Click OK.
An information dialog box is displayed, indicating that the configuration is successful.
8 Click OK.
----End
4.3.3 Configuring the Subscription Server
Scenarios
On the FusionStack, configure the subscription server and the mailbox that send alarm
information. After the subscription server is configured, alarms and other maintenance
information can be sent from the configured mailbox.

Prerequisites
Conditions
A mail server is available and it is communicating properly with the FusionStack.
Data

FusionCompute

SMTP Server Specifies the address of the smtp.huawei.com or

subscription server that sends alarm 192.168.3.235
information.
Port ID Specifies the number of the SMTP port 25

that is automatically specified by the
system.
The port number is 456 when the server
uses Secure Sockets Layer (SSL) to
establish connections.
The port number is 25 when the server
does not establish SSL connections.
Sender mailbox Specifies the address of the mailbox galax@huawei.com

displayed in emails that sends alarm information. It is the
same as the mailbox from which emails
are sent when a user logs in to the
SMPT server.
This is a global parameter. For
example, if galax is the username used
for logging in to the SMTP server and
smtp.huawei.com is the address of the
SMTP server, the mailbox address is
galax@huawei.com.
Authentication Specifies whether to authenticate the N/A

user who uses the mailbox to send
emails.
User name Specifies the username used for huawei

logging in to the SMTP server.
This parameter is valid only when the
Authentication is selected.
Password Specifies the password for logging in huawei123

to the SMTP server.
This parameter is valid only when the
Authentication is selected.
SSL Specifies whether SSL is required N/A

when the user logs in to the SMTP
server. The value varies depending on
the SMPT server used for sending
emails.

FusionCompute
Test mailbox Specifies the address of the mailbox test@huawei.com

used to verify whether the SMTP
server functions properly.
Procedure

2 In the navigation tree on the left, choose Subscription Service.
– SMTP Server: specifies the domain name address or IP address of the subscription
server that sends alarm information.
– Port ID: specifies the number of the SMTP port that is automatically specified by the
system. The default value is 25.
– Sender mailbox displayed in emails: specifies the address of the mailbox that sends
alarm information.
– Authentication: specifies whether to authenticate the user who uses the mailbox to send
emails. When Authentication is selected, you must specify User name and
Password used for logging in to the mailbox.
– SSL: specifies whether SSL is required when the user logs in to the SMTP server.
– Test mailbox: specifies the address of the mailbox used to verify whether the SMTP
server functions properly.
4 Click OK.
5 Click OK.
----End
4.3.4 Configuring Domain Authentication Information
Scenarios
Configure domain authentication information on the FusionStack so that common users created
on the FusionStack by domain users can log in to the system.

Prerequisites
Conditions

FusionCompute

– The domain server and the ESC node are communicating properly.
Data
IP address Specifies the IP address of the domain server. ldap://

This parameter is mandatory. 192.131.10.10:389
Domain name Specifies the domain name where the domain china.huawei.com
server belongs.
Procedure

2 In the navigation tree on the left, choose Domain Authentication.
3 Specify the following parameters:
– IP address: specifies the IP address of the domain server, for example, ldap://
192.131.10.10:389.
– Domain name: specifies the domain name where the domain server belongs.
4 Click OK.
An information dialog box is displayed, indicating that the domain server is configured.
5 Click OK.
----End
4.3.5 Configuring the Session Timeout Duration
Scenarios
Configure the session timeout duration on the FusionStack. If users do not perform any
operation within the configured session timeout duration, they will be logged out automatically.

Prerequisites
Conditions

FusionCompute
Data

Session timeout Specifies the maximum delay users are 15 minutes

logged out automatically if they do not
perform any operation on the
FusionStack.
Procedure

2 In the navigation tree on the left, choose Session Timeout.
3 Specify the Session timeout parameter.
4 Click Save.
5 Click OK.
6 Click OK.
----End
4.3.6 Modifying Time Synchronization and Time Zone Settings
Scenarios
Modify the time synchronization and time zone settings on the FusionStack.

After the NTP clock source is changed, the system synchronizes time from the new NTP server.
After the time zone is changed, the system automatically changes the system time according to
the new time zone.
Prerequisites
Conditions
– Communication between the clock source and the system is normal.
– If multiple NTP servers are deployed, all the NTP servers use the same upper-layer clock
source so that the system time on all NTP servers is the same.
Data

FusionCompute

Time NTP server Specifies the IP 192.168.40.3

Synchronization address of the NTP
server.
Enter one to three IP
addresses of the NTP
servers.
This parameter is
mandatory.
Time Specifies the interval 64

synchronization for time
interval (s) synchronization
(seconds).
This parameter is
mandatory.
Configure Time Time Zone Specifies the local Asia

Zone time zone of the
system. The system Beijing
determines whether
to enable the
Daylight Saving
Time (DST) based on
the time zone you set.
This parameter is
mandatory.
Procedure
Configure the time synchronization.
2 In the navigation tree on the left, choose Configure Time Zone > Time
Synchronization.
the page.
CAUTION
If multiple Network Time Protocol (NTP) servers are to be deployed, ensure that all the
NTP servers use the same upper-layer clock source so that the system times of the NTP
servers are the same.

FusionCompute
– NTP server: specifies the IP address of the NTP server. Enter one to three IP addresses
of the NTP servers.
– Time synchronization interval (s): specifies the interval for time synchronization
(seconds), which is two to the power of n.
4 Click Save.
5 Click OK.
6 Click OK.
Configure the Time Zone.
7 In the navigation tree on the left, choose Configure Time Zone > Time Zone.
the page.
8 Configure the time zone parameters.
9 Click Save.
10 Click OK.
11 Click OK.
----End
4.3.7 Synchronizing Time Forcibly
Scenarios
Synchronize time forcibly on the FusionStack when the time on the NTP server changes or
when the system time is inconsistent with that on the NTP server.

Forcible time synchronization restarts service processes. Therefore, you are advised to perform
this operation when the traffic is low.
Prerequisites
Conditions
Data
Procedure


FusionCompute
2 In the navigation tree on the left, choose Configure Time Zone > Forcibly Synchronize
Time.
3 On the right panel, click Forcibly Synchronize Time.
An information dialog box is displayed indicating that the time is synchronized.
4 Click OK.
----End
4.3.8 Modifying ESC VM Specifications
Scenarios
On the FusionCompute, modify CPU and memory specifications of the Elastic Service
Controller (ESC) VM based on the number of VMs and hosts in the system.
NOTE
If two ESCs are deployed working in active/standby mode, modify the VM specifications of the standby
ESC and restart it, and then modify the VM specifications of the active ESC.

Relevant ESC services will be temporarily interrupted because the ESC VM must be restarted
after the modification. Therefore, perform the modification when no service is running.
Prerequisites
Conditions
– You have obtained the floating IP address of the active and standby VRMs if two VRM are
deployed working in active/standby mode; or you have obtained the management IP address
of the VRM if only one VRM is deployed.
Data
Table 4-9 lists the ESC VM configuration script data.

FusionCompute
Table 4-9 ESC VM configuration script data
Command parameter Specifies the VM S

specification parameter.
Value:
l S: indicates that the VM
has 4 CPUs and 8 GB
memory.
l M: indicates that the VM
has 6 CPUs and 12 GB
memory.
l L: indicates that the VM
memory.
l XL: indicates that the VM
memory.
Procedure
Modify VM specifications of the ESC.
2 On the VM page, obtain the name of the ESC VM using the IP address of the ESC whose
VM specifications are to be modified.
You can query the target VM by clicking Advanced, entering the IP address of the ESC
in IP, and then clicking Search.
3 In the navigation tree on the left, choose Site name > ESC VM name.
The Summary page is displayed.
4 On the Virtual Hardware page, click CPU, and select the number of CPUs of the ESC
VM from the Number of kernels drop-down list.
5 Click OK.
The modification is saved.
6 Click Memory, and modify the memory size of the ESC VM in the Size (MB) text box.
7 Click OK.
The modification is saved.
Run the ESC VM configuration script.
8 Use PuTTY to log in to the ESC whose VM specifications are to be modified.
After logging in to the ESC as user gandalf, run the su - root command to switch to the
root user interface.
TMOUT=0

FusionCompute
10 Run the following command to switch to the /opt/eucalyptus/conf directory:

cd /opt/eucalyptus/conf
11 Run the following command to run the configuration script:
sh modifyMemory.sh Command parameter
For example: sh modifyESCNodeMemory.sh S
The command is executed if the command output is as follows:
modify ESC java heap success
modify OM java heap success
modify Portal java heap success
12 Run the following command to restart the standby ESC:

reboot
Modify the VM specifications of the active ESC.
13 Repeat Step 1 to Step 12 to modify the VM specifications of the active ESC.
----End
4.4 Image Server Management
4.4.1 Adding an Image Server
Scenarios
Add an image server on the FusionStack.

Prerequisites
Conditions
– The Image Storage (IMGS) nodes have been installed.
Data
Name Specifies the name of the image server to IMGS01

be registered on the FusionStack.

FusionCompute

Procedure

3 Click Add.
The Add Image Server dialog box is displayed.

5 Click Add.
An information dialog box is displayed indicating that the image server is added.
6 Click OK.
The newly added image server is displayed in the list.
----End
4.4.2 Deleting an Image Server
Scenarios
Delete an image server that is no longer used on the FusionStack.

Prerequisites
Conditions
– Information about the image server to be deleted has been obtained.
Data
Procedure

FusionCompute

3 Locate the row that contains the image server to be deleted, click Operation, and select
Delete.
4 Click OK.
An information dialog box is displayed, indicating that the image server is deleted.
5 Click OK.
----End
4.4.3 Modifying an Image Server
Scenarios
Change the name and IP address of an image server on the FusionStack.

Prerequisites
Conditions
– To change the IP address of an image server on the FusionStack, change the management
IP address of the image server first.
Data
Name Specifies the name of the image server that IMGS01

is registered on the FusionStack.

Procedure

FusionCompute

3 Locate the row that contains the image server to be modified, click Operation, and select
Modify.
The Modify Image Server dialog box is displayed.
4 Modify the values of the following parameters:
5 Click OK.
An information dialog box is displayed, indicating the image server information is
modified.
6 Click OK.
----End
4.4.4 Adding or Deleting a Disk

Scenarios
Add or delete a disk on the Image Storage (IMGS) node to increase or decrease the storage space
of the IMGS.

Prerequisites
Conditions
– If the IMGS is deployed on a VM, the disk to be added or deleted has been bound to the VM
where the IMGS is deployed.
– If the IMGS is deployed on a physical server, the disk to be added or deleted has been installed
on the physical server.
– Before a disk is deleted, all the data on it has been backed up to other disks.
Data

Management IP address Specifies the IP address used for N/A

of the IMGS logging in to the IMGS.
Password of user root Specifies the password of user root for N/A
logging in to the IMGS.
Tools

FusionCompute
You have obtained PuTTY.
Procedure
Check the disk status.
1 Use PuTTY to log in to the IMGS.
Ensure that the management IP address and username gandalf are used to establish the
connection.
NOTE
The IMGS can be deployed either on a VM or a physical server. This section uses the IMGS deployed
on a VM as an example to describe how to add or delete a disk on the IMGS.
2 Run the following command and enter the password of user root to switch to user root:
su - root
TMOUT=0
4 Run the following command to view the disk partition information on the current server:
fdisk -l
Information similar to the following is displayed:
Disk /dev/xvda: 53.7 GB, 53687091200 bytes
...
Disk /dev/xvdd: 266 MB, 266182656 bytes
...
Disk /dev/xvde: 10.7 GB, 10737418240 bytes
...
Disk /dev/xvdf: 10.7 GB, 10737418240 bytes
...
5 Run the following command to view attached disks on the current server:
mount
/dev/xvda1 on / type ext3 (rw,errors=panic)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
...
/dev/xvdf on /image/third type ext3 (rw)
nfsd on /proc/fs/nfsd type nfsd (rw)
Through Step 4 and Step 5, you can now determine that disk xvde is not attached. Disk
xvdf is attached to the /image/third directory.
Typically, the disks that can be added or deleted for a VM are named xvde, xvdf, …, while
those that can be added or deleted for a physical server are named sdb, sdc, ….
6 Choose the task you need to perform.
– To add a disk, go to Step 7.
– To delete a disk, go to Step 15.
Add a disk.
7 Determine whether to format the disk.
NOTE
To attach a new disk, you must format it first. If you format a disk that contains data, all the data on
it will be cleared.

FusionCompute
8 Run the following command to format the disk:
mkfs.ext3 -F /dev/Disk name
For example, to format disk xvde, run the following command:
mkfs.ext3 -F /dev/xvde
The disk is formatted successfully if the following information is displayed:
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 22 mounts or

180 days, whichever comes first. Use tune2fs -c or -i to override.
If the disk formatting fails, restart the IMGS and try to format the disk again. If the disk
still cannot be formatted, contact Technical Support.
9 Run the following command to attach the disk to the image storage directory:
sh /opt/galax/imgs/script/initDisk.sh Directory name Disk name
Directory name varies depending on the image storage directory actually used. It must be
unique on the image server. For example, to attach disk xvde to the /image/second/
directory, run the following command:
sh /opt/galax/imgs/script/initDisk.sh second xvde
The disk is attached successfully if the following information is displayed:
begin mount /dev/disk/by-id/scsi-SATA_QEMU_HARDDISK_QM00005.
mount disk xvde to /image/second success.
modify fstab file success.
restart nfsserver begin.
restart nfsserver success.
SUCCESS:0
10 Use PuTTY to log in to the active Elastic Service Controller (ESC) node.
TMOUT=0
12 Run the following command to check the status of the newly added shared directory on the
image server:
ls -l /image/Image server name
Image server name is the name registered for the image server on the FusionStack.
The status of the shared directory is normal if information similar to the following is
displayed:
...
drwxrwxr-x 3 gandalf GalaX8800 4096 Feb 27 13:28 second
...
The status of the shared directory is abnormal if information similar to the following is
displayed:
ls: cannot access second: Stale NFS file handle
...

FusionCompute
d????????? ? ? ? ? ? second
...
13 Based on the displayed information, determine whether the status of the shared directory
is normal.
– If yes, no further action is required.
14 Run the following command to unmount the shared directory on the image server:
sudo umount -l /image/Image server name
After the shared directory is unmounted using this command, the system automatically
mounts the shared directory again.
About 1 minute later, check whether the status of the shared directory is normal. If no,
contact Technical Support.
Delete a disk.
15 Run the following command to detach a disk from the image storage directory and delete
the directory that corresponds to the disk:
sh /opt/galax/imgs/script/deleteDisk.sh Directory name Disk name
For example, to detach disk xvdf from the /image/third/ directory and delete the third
directory, run the following command:
sh /opt/galax/imgs/script/deleteDisk.sh second xvdf
The disk is detached successfully if information similar to the following is displayed:
try to umount /dev/xvdf.
try to umount /dev/xvdf success.
delete /image/third from /etc/fstab success
delete dir /image/third success.
restart nfsserver begin.
restart nfsserver success.
SUCCESS:0
16 Determine whether to format the disk.

----End
4.4.5 Adding Secondary-Tier Storage Resources

Scenarios
Add secondary-tier storage resources for the Image Storage (IMGS) node deployed on a physical
server.

Prerequisites
Conditions

FusionCompute
– Logical unit numbers (LUNs) have been created on the IP SAN. LUN mappings have been
created.
– No operations such as creating VMs, creating images, and registering images are being
performed.
Data
Operation Parameter Description Example Value
IMGS information Management IP address Specifies the IP address N/A

of the IMGS used for logging in to
the IMGS.
Password of user root Specifies the password N/A

of user root for logging
in to the IMGS.
NIC name Specifies the name of eth2

the network interface
card (NIC) used on the
storage plane of the
IMGS.
The NIC name must not
be eth0.
Storage IP address of Specifies the IP address 172.20.83.6

the IMGS used on the storage
plane of the IMGS.
Subnet mask Specifies the subnet 255.255.0.0

mask for the storage IP
address of the IMGS.
Storage device Storage plane VLAN Specifies the VLAN ID 5

information ID for multipath storage
resources on the IP
SAN.
Storage IP address Specifies the IP address 172.20.12.10

for multipath storage
resources on the IP
SAN.
Tools
You have obtained PuTTY.
Procedure
Configure the storage network for the IMGS.

FusionCompute
connection.
su - root
TMOUT=0
4 Run the following command to configure the storage network for the IMGS. If multipath
storage is configured, you can configure multiple storage paths using the following
command:
sh /opt/galax/imgs/script/config_network.sh NIC name Storage plane VLAN ID IMGS

storage IP address Subnet mask
For example: sh /opt/galax/imgs/script/config_network.sh eth2 5 172.20.83.6

255.255.0.0
The storage network is configured successfully if information similar to the following is

displayed:
Restarting network...
Restarting network completed
Success: Config network success.
5 Run the following command to verify the configuration of the storage network:
ping -c 3 -W 2 IP SAN storage IP address
For example, if the IP SAN storage IP address is 172.20.12.10, run the following command:
ping -c 3 -W 2 172.20.12.10
Check whether the IP SAN storage IP address can be pinged.
– If no, check the storage network configuration again.
Modify the system settings for the image server.
6 Run the following command to configure open-iscsi as a default startup service:
chkconfig open-iscsi on
7 Run the following command to configure multipathd as a default startup service:
chkconfig multipathd on
8 Run the following command to check the status of the open-iscsi service:
chkconfig --list open-iscsi
The open-iscsi service has started if items 3 and 5 in the following information are on:
open-iscsi 0:off 1:off 2:off 3:on 4:off 5:on 6:off
9 Run the following command to check the status of the multipathd service:
chkconfig --list multipathd
The multipathd service has started if items 3 and 5 in the following information are on:

FusionCompute
multipathd 0:off 1:off 2:off 3:on 4:off 5:on 6:off
10 Run the following command to restart the IMGS for the configuration to take effect:
reboot
Mount a newly created LUN.
connection.
su - root
TMOUT=0
14 Run the following command to discover storage devices on the IMGS:
iscsiadm -m discovery -t st -p Storage IP address
For example, if the storage IP address is 172.20.12.10, run the following command:
iscsiadm -m discovery -t st -p 172.20.12.10
172.20.12.10:3260,1 iqn.2006-08.com.huawei:oceanstor:
21000022a100d96b:notconfig:172.20.12.10
21000022a100d96b:notconfig:172.30.12.11
21000022a100d96b:notconfig:172.20.12.11
21000022a100d96b:notconfig:172.30.12.10
15 Run the following command to check the InitiatorName of the current IMGS node:
cat /etc/iscsi/initiatorname.iscsi
In the following output, InitiatorName is iqn.1996-04.de.suse:01:edf91db6a4b5.
##
## /etc/iscsi/iscsi.initiatorname
...
InitiatorName=iqn.1996-04.de.suse:01:edf91db6a4b5
16 Use the IP SAN client OceanStor ISM to log in to an IP SAN device.

This section uses a Huawei Symantec S5600 as an example.
17 In the logical view, right-click the newly added host under All Host Group and choose
Initiator Management, as shown in Figure 4-10.

FusionCompute
Figure 4-10 Initiator Management
18 On the Initiator tab page, select iSCSI as the HBA Card Type, select the
InitiatorName of the IMGS from Unconfigured Initiator and add it to Configured
Initiator.
19 Run the following command to log in to the iSCSI target:
iscsiadm -m node -l
20 Run the following command to view existing iSCSI sessions:
iscsiadm -m session
tcp:[1]172.20.12.10:3236,1 iqn.2006-08.com.huawei:oceanstor:
21000022a100d96b:notconfig:172.20.12.10
The preceding output contains the information about one link. If multiple links are
configured, the output will contain the information about multiple links.
21 Run the following command to enable automatic login over iSCSI links upon startup:
iscsiadm -m node -T iqn.2006-08.com.huawei:oceanstor:21000022a100d96b:notconfig:
172.20.12.10 -p 172.20.12.10:3260 --op update -n node.startup -v automatic
The variables in italics in the following command need to be replaced using the link
information obtained in Step 20. If multiple links are present, you need to run this command
multiple times.
Mount the LUN to the image storage directory.
22 Run the following command to query the scsi-id and volume label of the newly mounted
LUN:
ls -l /dev/disk/by-id/
In the following output, the scsi-id of the newly mounted LUN is
scsi-360022a110000d96b4e8bf2af00000034 and the volume label is dm-1.
total 0
...

FusionCompute
lrwxrwxrwx 1 root root 10 Jan 18 16:38 scsi-360022a110000d96b4e8bf2af00000034

-> ../../dm-1
...
23 Run the following command to format the newly mounted LUN:

mkfs.ext3 -F /dev/disk/by-id/scsi-id of the newly mounted LUN
For example, if the scsi-id of the LUN is scsi-360022a110000d96b4e8bf2af00000034, run
the following command:
mkfs.ext3 -F /dev/disk/by-id/scsi-360022a110000d96b4e8bf2af00000034
24 Run the following command to mount the LUN to the image storage directory:
sh /opt/galax/imgs/script/addLunDisk.sh scsi-id directory name
NOTE
The directory name varies depending on the image storage directory actually used. It consists of
letters, digits, and underscores (_). Its maximum length is 32 characters.
For example, to mount the LUN whose scsi-id is

scsi-360022a110000d96b4e8bf2af00000034 to the /image/second/ directory, run the
following command:
sh /opt/galax/imgs/script/addLunDisk.sh scsi-360022a110000d96b4e8bf2af00000034
second
25 Run the following command to view the result:
df -l
The secondary-tier storage path for the IMGS is added successfully if information similar
to the following is displayed:
Filesystem 1K-blocks Used Available Use% Mounted on
...
/dev/dm-1 20637308 176196 19412792 1% /image/second
...
You can then copy image files to the /image/second directory, and register and use them.
----End
Verification
Verify the stability of the IMGS upon restart.
1. Run the reboot command to restart the image server.
2. Log in to the BMC interface of the image server, and observe the image server restart
process on the remote control page.
If the screen stalls at the following line, try to restart the image server again on the BMC
remote management interface.
Unmounting file systems
Verify the status of the image server directory on the Elastic Service Controller (ESC). In this
example, the status of the /image/imgs01/second directory is verified, where imgs01 is the name
registered for the image server.
1. Use PuTTY to log in to the ESC, and run the following command to check the status of the
image server directory:

FusionCompute
ls /image/imgs01/second/
If information similar to the following is displayed, the directory has failed to be mounted,
and you need to mount it again.
Is:cannot access /image/imgs01/second/: Stale NFS file handle
2. Run the following command to unmount the /image/imgs01/second directory:

umount -nal /image/imgs01/
3. About 1 minute later, run the df command to check whether the /image/imgs01/second
directory is mounted successfully, as shown in the following output:
192.169.84.5:/image 516045824 45544448 444286976 10% /image/second
4. Run the ls /image/imgs01/second/ command again to verify that the /image/imgs01/

second directory is mounted successfully.
Verify the following functions:
1. Registering an image
2. Creating a VM
3. Exporting an image
4. Deleting an image
4.5 Operation Log Management
4.5.1 Viewing Operation Logs
Scenarios
View the logs about user operations on the FusionStack. The operation logs include a description
of each operation, the time when the operation was performed, and other details. You can save
the operation logs as files on the local PC.

Prerequisites
Conditions
Data
Procedure
View operation logs.
1 On the FusionStack, choose System > Operation Log.
The Operation Logs page is displayed.
2 Click Advanced Search.

FusionCompute
Advanced search options are displayed.

3 Enter the search criteria.
Parameters available include User, Operation period, Operation name, Level,
Operation result, UserIP, Cause of failure, and View details.
4 Click Search.
The query result is displayed.
View log details.
5 Locate the operation log whose details you want to view, and click Operation Name.
6 In the Operation Logs Details area at the lower part, view the log details.
7 Determine whether to export the operation logs and save them as local files.
Export operation logs.
8 Click on the right.

9 Click OK.
10 In the dialog box that appears, select the local directory for saving the log file.
11 Close the Download complete dialog box.
----End
4.6 Subscription Management
4.6.1 Adding an Alarm Subscription Task
Scenarios
Create an alarm subscription task on the FusionStack. Based on the subscription configuration,
the FusionStack:
l Collects alarms generated in the specified period of time.
l Reports the collected alarm information to the upper-layer management system or sends it
to the destination mailbox addresses specified in the subscription task.

Prerequisites
Conditions
– The subscription server has been configured.

FusionCompute
Data
Name Specifies the name of the subscription dingyue01

task. This parameter is mandatory.
My subscription Specifies the subscription mode, for By email

example, By email, which means to
send the subscribed information
through emails.
Email Specifies the mailbox address that N/A

receives the subscribed alarm
information.
Time period Specifies the subscribed period during 12:00:00-14:00:00

which alarms are generated.
Alarms Specifies the severities and names of Critical alarm

the alarms to subscribe to.
Procedure
1 On the FusionStack, choose System > Subscription Center.

The Subscription Center page is displayed.
2 Click Add Alarm Subscription.
The Add Alarm Subscription page is displayed.
3 Enter the subscription task name in Name.
4 Enter the mailbox address that receives the subscribed alarm information. You can also
click Import Email Address to add the mailbox addresses of existing administrator users.
5 Specify the subscribed period.
6 In the Alarms box, select the alarms to subscribe to, and click to add them.
7 Click OK.
An information dialog box is displayed indicating that the alarm subscription task is created.
8 Click OK.
----End

FusionCompute
4.6.2 Modifying an Alarm Subscription Task
Scenarios
On the FusionStack, modify an existing alarm subscription task.

Prerequisites
Conditions
Data
My subscription Specifies the subscription mode, for By email

example, By email, which means to
send the subscribed information
through emails.
Email Specifies the mailbox address that N/A

receives the subscribed alarm
information.
Time period Specifies the subscribed period during 12:00:00-14:00:00

which alarms are generated.
Alarms Specifies the severities and names of Critical alarm

the alarms to subscribe to.
Procedure

The Subscription Center page is displayed.
2 Locate the row that contains the alarm subscription task to be modified, click Operation,
and select Modify.
The Modify Alarm Subscription page is displayed.

FusionCompute
3 Modify the following parameters:

– Email: specifies the mailbox address that receives the subscribed alarm information.
You can also click Import Email Address to add the mailbox addresses of existing
administrator users.
– Time period: specifies the subscribed period during which alarms are generated.
– Alarms: specifies the severities and names of the alarms to subscribe to.
4 Click OK.
An information dialog box is displayed indicating the alarm subscription task is modified.
5 Click OK.
----End
4.6.3 Suspending or Deleting an Alarm Subscription Task
Scenarios
Suspend or delete an unused alarm subscription task on the FusionStack.

Prerequisites
Conditions
– The name of the alarm subscription task to be suspended or deleted has been obtained.
Data
Procedure
Suspend an alarm subscription task.
2 Locate the row that contains the alarm subscription task to be suspended, click
Operation, and select Deactivate.
3 Click OK.
The status of the alarm subscription task changes to Deactivate.
Delete an alarm subscription task.
4 Locate the row that contains the alarm subscription task to be deleted, click Operation,
and select Delete.
5 Click OK.
An information dialog box is displayed indicating that the task is deleted.
----End

FusionCompute
4.7 User Management
4.7.1 Creating a Role
Scenarios
On the FusionStack, create a role and specify its operation rights.

Prerequisites
Conditions
Data
Role name Specifies the name of administrator

the role. The value
must start with a
letter and can contain
only digits, letters,
and underscores(_).
Length: 6 to 20
characters.
This parameter is
mandatory.
Permission Specifies the l Alarm

operations rights Management
assigned to the role. l Operation Log
This parameter is Management
mandatory.
Description Provides System administrator

supplementary
information about
the role.
This parameter is
optional.

FusionCompute
Procedure
1 On the FusionStack, choose System > Rights Management.

2 Click Role in the user list on the left.
3 Click Add Role.
The Add Role page is displayed.
4 Set Role name and Description.
5 Select the operation rights to be assigned to the role from the Permission list.
6 Click OK.
7 Click OK.
----End
4.7.2 Creating a User
Scenarios
On the FusionStack, create a user and specify its role.

Prerequisites
Conditions
Data
User type l Local user: logs in to the system using a Local user
local username and password.
l Domain user: logs in to the system using
a domain username and password. The
domain user is created using a domain
username.
l Interface interconnection user: creates
an internal user account for interworking
with other components.

FusionCompute
Username Specifies the username. The value can contain user01

6 to 20 characters and consist of digits, letters,
and underscores (_).
The username of a domain user must be the
same as that created on the domain server.
Password Specifies the password of the user. The value Galax8800

must contain uppercase and lowercase letters
and digits. Its length is 6 to 32 characters.
This parameter is mandatory if you are
creating a local user.
Subrole Specifies the role of the administrator user. administrator

Set this parameter based on the type and
operation rights of the administrator.
Mobile number Specifies the mobile phone number of the 075512345678

user. The value is a number of a maximum of
25 digits.
Maximum number Specifies the maximum number of users Not limited

of concurrent allowed to concurrently log in to the system
logins of a user using the same username.
Email Specifies the email address used to receive user@example.com

system alarm notifications. The value must be
a valid email address.
Description Provides supplementary information about Has system

the username. administrator rights.
Procedure

2 In the user list on the left, click User.
3 Click Add User.
4 Set the User type parameter.
– Local user: logs in to the system using a local username and password.

FusionCompute
– Domain user: logs in to the system using a domain username and password. The domain
user is created using a domain username.
– Interface interconnection user: creates an internal user account for interworking with
other components.
5 Determine whether to use the current role to create a user.
6 Click Add Role.
For details, see Creating a Role.
7 Select a user role from the Subrole list.
Specify the role of the administrator user. Set this parameter based on the type and operation
rights of the administrator.
– Username: specifies the username. (The username of a domain user must be the same
as that created on the domain server.)
– Password: specifies the password of the user. (This parameter is not required when you
are creating a domain user.)
– Mobile number: specifies the mobile phone number of the user.
– Maximum number of concurrent logins of a user: specifies the maximum number
of users allowed to concurrently log in to the system using the same username.
– Email: specifies the email address used to receive system alarm notifications.
– Description: provides supplementary information about the username.
9 Click OK.
An information dialog box is displayed, indicating that the user is added.
10 Click OK.
----End
4.7.3 Configuring Password Policies

Scenarios
On the FusionStack, modify the policies for its login password.
Prerequisites
Conditions
– The system administrator has management permission for Password Policy.
Data
Procedure
Step 1 On the FusionStack, choose System Management > Right Management.
The Right Management page is displayed.

FusionCompute
Step 2 At the upper left corner of the page, click Password Policy.
The Password Policy page is displayed, on which you can check the current password policies.
Step 3 Click Modify.
The parameters on the Password Policy page can be edited.
Step 4 Enter the new parameter values and modify the password policies.
The parameters must meet the requirements in the following table:
Shortest period between each Specifies the minimum 5

password change (in interval between two
minutes) password changes.
Value range: 0 to 9999 (0
indicates that a new
password can be changed
immediately after it is set.)
Allow passwords to contain Specifies whether to allow No

the username or reversed passwords to contain the
username username or reversed
username
l Yes: The password is
allowed to contain the
username or reversed
username.
l No: The password is not
allowed to contain the
username or reversed
username.
Prompt users to change their Prompts users to change Yes

passwords after logging in their passwords after logging
for the first time or after their in for the first time or after
passwords were just reset their passwords were just
reset.
Allow special characters for Specifies whether to allow Yes

passwords special characters for
passwords.
Value:
l Yes: The password is
allowed to contain
special characters.
l No: The password is not
allowed to contain
special characters.

FusionCompute
Account lockout threshold Specifies the threshold for 3

the number of unsuccessful
login attempts.
When the number of
unsuccessful login attempts
is greater than the threshold,
the account will be locked.
When the parameter is set to
0, the account will not be
locked.
Value range: 0 to 10
Password expiry alert (days) Specifies the days in advance 7

when a password expiration
alert starts to be generated.
indicates that no alert will be
generated.)
Account lockout duration Specifies the duration in 5

(minutes) which the account is locked
due to incorrect inputs.
When the account is locked
for a specified period, it will
be unlocked automatically.
When this parameter is set to
0, the account must be
unlocked by the
administrator who has that
permission.
Value range: 0 to 1440
Password validity period Specifies the password 90

(days) validity period.
indicates that the password is
always valid.)
Password length Specifies the allowed 6-32

password range.
Format: m-n, in which m and
n are integers ranging from 6
to 32 and m must be less than
n.
Number of previous Specifies the number of 5

passwords that cannot be previous passwords that
repeated cannot be repeated.
Value range: 3-32

FusionCompute
Step 5 Click Save.

A dialog box is displayed indicating that the password policies are changed.
Step 6 Click OK.

The password policy modification task is complete.
----End
4.7.4 Modifying User Information
Scenarios
Modify user information on the FusionStack, including the user's password, role, mobile phone
number, email address, and username description.

Prerequisites
Conditions
– You have obtained the information about the user to be modified.
Data
Password Specifies the Galax8800

password of the user.
The value must
contain uppercase
and lowercase letters
and digits. Its length
is 6 to 32 characters.
Subrole Specifies the role of System administrator

the administrator
user. Set this
parameter based on
the type and
operation rights of
the administrator.

FusionCompute
Maximum number of concurrent logins of a Specifies the Not limited

user maximum number of
users allowed to
concurrently log in to
the system using the
same username.
The default value
Not limited
indicates that the
number of users
allowed to
concurrently log in to
the system using this
username is not
limited.
Mobile number Specifies the mobile 075512345678

phone number of the
user. The value is a
number of a
maximum of 25
digits.
Email Specifies the email abc@huawei.com

address used to
receive system alarm
notifications. The
value must be a valid
email address.
Description Provides Has system

supplementary administrator rights.
information about
the username.
Procedure

The user list is displayed on the right.
3 Determine whether the password must be changed.
4 Locate the row that contains the user to be modified, click Operation, and select Reset
password.

FusionCompute
The Reset Password dialog box is displayed.

5 Set Password, and click OK.
6 Locate the row that contains the user to be modified, click Operation, and select
Modify.
7 Modify user parameters based on the data in Table 4-18.
8 Click OK.
9 Click OK.
----End
4.7.5 Modifying the Rights of a Role
Scenarios
On the FusionStack, modify the operation rights of a non-default role for access control
purposes.

Prerequisites
Conditions
Data

Permission Specifies the operations rights l Alarm Management

assigned to the role. l Operation Log
Management
Description Provides supplementary System administrator

information about the role.
Procedure

2 In the navigation tree on the left, click Role.
3 Locate the row that contains the role to be modified, click Operation, and select Modify.

FusionCompute
The Modify Role page is displayed.

4 Select the operation rights to be assigned to the role from the Permission list, and provide
a brief description.
5 Click OK.
6 Click OK.
----End
4.7.6 Resetting User Password
Scenarios
On the FusionStack, reset the passwords for users who have forgotten their passwords and
assign new passwords to them.

Prerequisites
Conditions
You have logged in to the FusionStack as an authorized administrator.
Data
Username Specifies the username whose N/A

password you want to reset.
New password l Specifies the new password. The Galax8800

password contains a minimum of
6 characters and a maximum of 32
characters.
l The password must contain all the
following character types:
– Lowercase letter
– Uppercase letter
– Digit
l The new password must comply
with the pre-configured password
policies.

FusionCompute
Procedure

3 Locate the row that contains the user whose password you want to reset, click
Operation, and select Reset Password.
The Reset Password dialog box is displayed.
4 Enter the new password in Password and Confirm password, and click OK.
A dialog box is displayed, indicating that the password is reset.
5 Click OK.
----End
4.7.7 Changing the User Password

Scenarios
On the FusionStack, change your own password to improve system security.

Prerequisites
Conditions
Data

FusionCompute

New password l Specifies the new Galax8800

password. The password
contains a minimum of 6
characters and a maximum
of 32 characters.
l The password must contain
all the following character
types:
– Lowercase letter
– Uppercase letter
– Digit
l The new password must
comply with the pre-
configured password
policies.
Procedure
1 At the upper right corner of the FusionStack, click the username of the current user.
The information about the current user is displayed.
2 Click Modify in the Password row.
The Modify Password dialog box is displayed.
3 Enter the old and new passwords, and click Modify.
A dialog box is displayed, indicating that the password is changed.
4 Click OK.
----End
4.7.8 Locking a User Account

Scenarios
On the FusionStack, lock a user account. After being locked, the account cannot be used to log
in to the FusionStack.
The account is unlocked using either of the following methods:
l Automatically lock: Lock the account when the number of unsuccessful login attempts is
greater than Account lockout threshold set in the password policy. For details, see
Configuring Password Policies.
l Manually lock: Lock the account by the administrator who has that permission. The locked
user account can be used to log in to the FusionStack only after being unlocked by the
administrator.
This section describes how to lock the account manually.

FusionCompute
Prerequisites
Conditions
– The system administrator has been granted the lock or unlock permission.
Data
Procedure
Step 1 On the FusionStack, choose System Management > Rights Management.
Step 2 In the user list on the left, click User.
The User page is displayed.
Step 3 Locate the row that contains the account to be locked, click Operation, and select Lock user.
Step 4 Click OK.
The account is locked. The account is in the Manually locked status.
----End
4.7.9 Unlocking the Locked User Account

Scenarios
On the FusionStack, unlock the locked user account.
The account is unlocked using one of the following three methods:
l Automatically unlock: If Account lockout threshold is set in the password policy, the
system will automatically unlock the account when the locking time runs out.
l Manually unlock: If the account cannot be automatically unlocked, the administrator who
has the permission to unlock accounts can unlock it manually.
l Unlock using a script: If the accounts of all the administrators who have the permission to
unlock accounts are locked, the account of the administrator who has that permission by
default can be unlocked using a script. The administrator who has that permission by default
includes:
– Common mode: admin
– Secure mode: secadmin
This section describes how to unlock the account manually or using a script.

When an account is unlocked using a script, the Virtual Resource Management (VRM) process
restarts, and the services will be interrupted during the restart.
Prerequisites
Conditions

FusionCompute
– The system administrator has been granted the lock or unlock permission.
Data
Procedure
Choose a method to unlock the account.
1 Check whether any administrator who has the permission to unlock accounts can log in to
the system.
Unlock an account manually.
2 On the FusionStack, choose System Management > Rights Management.
The User page is displayed.
4 Locate the row that contains the account to be unlocked, click Operation, and select Unlock
user.
5 Click OK.
The account is unlocked. The account is in the Normal status.
Unlocking the account using a script.
6 Use PuTTY to log in to the active VRM.
interface:
su - root
TMOUT=0
9 Run the following command to switch to the /opt/galax/vrm/tomcat/script/omsconfig/bin
directory:
cd /opt/galax/vrm/tomcat/script/omsconfig/bin
10 Run the following command to run the script:
sh resetSystemManageUser.sh unlock
If the following information is displayed, the account is unlocked.
unlock user success.
----End
4.7.10 Deleting a User

FusionCompute
Scenarios
Delete an unused user account on the FusionStack. A user cannot delete their own account.

Prerequisites
Conditions
You have logged in to the FusionStack and are authorized to manage users.
Data
Procedure

2 Click User in the user list on the left.
3 Locate the row that contains the user to be deleted, click Operation, and select Delete.
4 Click OK.
An information dialog box is displayed, indicating that the user is deleted.
5 Click OK.
----End
4.8 Health Check
4.8.1 Viewing Alarms
Scenarios
View alarms on the FusionStack to detect and locate faults in a timely manner, improving system
stability.

Prerequisites
Conditions

FusionCompute
Data
Procedure
View alarms.
1 On the FusionStack, choose Alarm.
The Alarms page is displayed.
2 Click Advanced.
Advanced search options are displayed.
3 Enter the search criteria.
Parameters available include Alarm severity, Alarm type, Date generated range, Object
type, Alarm object URN, Alarm ID, and Alarm name.
4 Click Search.
The query result is displayed.
View detailed alarm information.
5 Locate the row that contains the alarm you want to view, and click Alarm Name.
6 Detailed information about the alarm is displayed in the Alarm Details area at the lower
part.
7 Click the alarm ID.
An alarm handling guide is displayed. Follow the guide to clear the alarm.
8 Determine whether to export the alarm information and save it as a local file.
Export alarms.
9 Click on the right.

10 Click Yes.
11 In the dialog box that appears, select the local file name for saving the alarms.
12 Close the Download complete dialog box.
----End

FusionCompute
FusionStack User Guide 5 Fault Management
5 Fault Management
About This Chapter
5.1 Alarm Handling

5.2 Troubleshooting
5.3 Backup and Restoration

FusionCompute
5.1 Alarm Handling
5.1.1 ALM-15.1000077 License Is About to Expire

Description
The alarm module verifies the license validity between 00:00 to 02:00 every day. This alarm is
generated when the license is about to expire for less than 60 days.
This alarm is cleared when a valid license file is loaded to the system.
Attribute
Alarm ID Alarm Severity
15.1000077 l Warning:30 ≤ Remaining days of license < 60

l Minor:0 ≤ Remaining days of license < 30
NOTE
The values 30 and 60 are the default alarm thresholds.
Parameters
Name Meaning
Additional Information Remaining days of license.
Alarm Object Specifies the physical or logical hierarchical relationship of the

alarm in the system.
Occur Time Specifies the time when the alarm is generated.
Clear Time Specifies the time when the alarm is cleared.
Clear Type Specifies whether the alarm is manually or automatically

cleared.
SN Specifies the number assigned to the alarm based on the

sequence that the alarm is generated.
Event Type Specifies the alarm type.
Cleared By Specifies the name of the operator who clears the alarm.
Update Time Specifies the time when the alarm occur time is updated.

FusionCompute
Name Meaning
Auto Clear Specifies whether the alarm can be cleared automatically.
Integrated Component Alarm Specifies whether the object for which the alarm is generated
is an integrated component.
Alarm Object Name Specifies the name of the object for which the alarm is
generated.

Services will not be affected. However, updating the license file is required.
Possible Causes
The license is about to expire.
Procedure
Update the license file.
1 Check whether the license is purchased.
2 Apply for a license.
See the FusionCompute V100R003C00 License Operation Guide.
3 Updating the License File.
4 After 5 or 6 minutes, check whether the alarm is cleared.
– If no, contact technical support.
----End
Related Information
None
5.1.2 ALM-15.1000078 License Has Expired
Description
generated when the system detects that the license has expired for 60 days or more.
This alarm is cleared when a valid license file has been loaded to the system.

FusionCompute
Attribute
15.1000078 Critical
Parameters
Name Meaning
Additional Information -


cleared.

generated.

Some functions that are authorized by the license are unavailable.
Possible Causes
The license has expired.

FusionCompute
Procedure
1 Check whether a new license is purchased.
For details about how to apply for a license, see FusionCompute V100R003C00 License
Operation Guide.
----End
Related Information
None
5.1.3 ALM-15.1001000 VRM Node Unreachable
Description
The alarm module checks the management services of a site every 20 seconds. This alarm is
generated when the system detects that the management services are interrupted, that is, the
Elastic Service Controller (ESC) module cannot access the Virtual Resource Management
(VRM) module.
This alarm is cleared when the management services become normal.
Attribute
Alarm ID Alarm Severity Auto Clear
15.1001000 Critical Yes
Parameters
Name Meaning
Additional Information Specifies the IP address of the server on which the cluster
management service is running.


FusionCompute
Name Meaning

cleared.

generated.

When the alarm is generated, the communication between the ESC and CRM is interrupted. In
addition, all services on the site, such as creating and starting the VM, are unavailable.
Possible Causes
l The network is faulty.
l The VRM service is not enabled or is disabled abnormally.
l The watchdog is abnormal.
Procedure
Check network status of the ESC and VRM.
1 Confirm information about the site whose network is disconnected.
You can obtain the ID of the site from Additional Information.
2 Locate the row that contains the alarm, and click Alarm Object.
The detailed information about this alarm object is displayed.

FusionCompute
3 On the FusionStack, choose System > System Configuration, and view information about
the site listed on the displayed page, and obtain the management IP address of the site whose
ID is the same as that of the alarm site.
4 Use PuTTY to log in to the alarm object.
connection.
5 Run the following command and enter the password of user root to switch to the user
root interface:
su - root
TMOUT=0
7 Check whether the communication between the ESC and the VRM is proper.
ping IP address of the VRM whose management services are interrupted
The communication is normal if the following information is displayed:
PING 192.100.41.10 (192.100.41.10) 56(84) bytes of data.
64 bytes from 192.100.41.10: icmp_seq=1 ttl=64 time=0.035 ms
Check whether the communication between the ESC and VRM is normal.
8 Check network connection status in the equipment room to detect and rectify network faults.
9 After 2 or 3 minutes, view real-time alarms and check whether the alarm is cleared.
10 Use PuTTY to log in to the server listed in Step 1.
connection.
root interface:
su - root
TMOUT=0
13 Run the following command to restart the VRM service:
service vrmd restart
Check the status of the watchdog.
15 Run the following command to query the watchdog status:
sh /opt/galax/gcs/watchdog/watchdog.sh -query
16 Check whether the following information is displayed:
WatchDog daemon is running.

FusionCompute
– If yes, contact technical support.

17 Run the following command to start the watchdog process:
sh /opt/galax/gcs/watchdog/watchdog.sh -start
----End
Related Information
None
5.1.4 ALM-15.1001004 LDAP Database Unreachable
Description
The alarm module checks the communication between the Elastic Service Controller (ESC)
module and the Lightweight Directory Access Protocol (LDAP) database every 30 seconds. This
alarm is generated when the system detects that the ESC module cannot communicate with the
LDAP database.
This alarm is cleared when the communication between the ESC module and the LDAP database
becomes normal.
Attribute
Parameters
Name Meaning
Additional Information N/A


cleared.

FusionCompute
Name Meaning

generated.

All operations of non-administrator users fail because they were not granted permissions.
Possible Causes
l The LDAP database service is not enabled or is disabled abnormally.
l The watchdog is abnormal.
Procedure
Start the User Profile Function (UPF) service process manually.
2 On the FusionStack, choose System > Service Configuration, and obtain the management
IP address of the active ESC from the Service and Management Node page.
connection.
root interface:
su - root
TMOUT=0
6 Run the following command to stop the UPF process:
service ldap stop

FusionCompute
7 Run the following command to start the UPF process:

service ldap start
Check the status of the watchdog.
9 Run the following command to check the status of the watchdog:
sh /opt/galax/gcs/watchdog/watchdog.sh -query
WatchDog daemon is running.

11 Run the following command to start the watchdog:
sh /opt/galax/gcs/watchdog/watchdog.sh -start
----End
Related Information
None
5.1.5 ALM-15.1001005 License File Not Loaded
Description
generated when the system detects that no license file has been loaded.
Attribute
15.1001005 Critical
Parameters
Name Meaning
Additional Information Remaining days of trial license

FusionCompute
Name Meaning


cleared.

generated.

Some functions that are authorized by the license are unavailable.
Possible Causes
The license file is not loaded to the system. As a result, the system cannot provide the functions
specified by the license.
Procedure

Operation Guide.

FusionCompute
NOTE

----End
Related Information
None
5.1.6 ALM-15.1001007 Failure in Recovering VM Data from the

Database During ESC Start
Description
The alarm module checks the status of VM data recovery every 2 minutes during Elastic Service
Controller (ESC) start. This alarm is generated when the system detects that the recovering VM
data from the database fails or expires (the maximum duration is 15 minutes) when the ESC
starts.
This alarm is cleared when VM data is successfully recovered.
Attribute
Parameters
Name Meaning
Alarm Object Specifies the physical or logical hierarchical relationship of the alarm
in the system.
Clear Type Specifies whether the alarm is manually or automatically cleared.
SN Specifies the number assigned to the alarm based on the sequence that
the alarm is generated.

FusionCompute
Name Meaning

The ESC does not enable the thread for periodical communication with the Computing Resource
Manager (CRM). Therefore, the system is unavailable.
Possible Causes
Data recovery fails or expires.
Procedure
Confirm the IP address of the server reporting the alarm.
2 Obtain the management IP address of the active node from the Basic Information area.
Check the database service of the ESC.
connection.
root interface:
su - root
TMOUT=0
6 Check whether the database is in the running status.
service postgresql status
7 Run the following command to restart the database service:
service postgresql restart
9 Run the following command to restart the ESC server:

FusionCompute
sh /opt/setup/eucalyptus-cloud restart
----End
Related Information
None
5.1.7 ALM-15.1001010 FTP Server Unreachable
Description
The alarm module checks the communication between the Elastic Service Controller (ESC) node
and the File Transfer Protocol (FTP) server every 5 minutes. The charging system communicates
with the FTP server and enables the charging bills saved in the ESC to be uploaded to the FTP
server. This alarm is generated when the system detects that the monitoring thread of the ESC
cannot connect to the FTP server.
This alarm is cleared when the monitoring thread properly connects to the FTP server.
Attribute
Parameters
Name Meaning
Additional Information Specifies the IP address and port number of the FTP server.


cleared.


FusionCompute
Name Meaning
generated.

The charging function enables the periodical charging bills saved in the /etc/bill/ready folder
of the active ESC node to be uploaded to the FTP server. If the ESC fails in communicating with
the FTP server, more and more spaces will be left in the the /etc/bill/ready folder, thereby greatly
affecting the services on the ESC. When the folder size is greater than 400 MB, charging bills
may be lost.
Possible Causes
l The network between the ESC node and the FTP server is faulty.
l The FTP server is powered off or is faulty.
l The FTP service is abnormal.
Procedure
Check the network status of the ESC node and FTP server.
1 Obtain the IP address and port number of the FTP server from Additional Information in
the alarm list.
3 On the FusionStack, choose System > Service Configuration, and obtain the management
IP address of the active ESC from the Service and Management Node page.
4 Use PuTTY to log in to the alarm object listed in Step 3.
connection.
root interface:
su - root

FusionCompute
TMOUT=0
7 Run the following command:
ping IP address of the FTP server
Check whether the communication between the ESC node and the FTP server is normal.
8 On the FusionCompute, check whether ALM-15.1000204 Ethernet Port Status Abnormal
is generated for the server on the Alarms page.
9 Handle the alarm by following the procedures in ALM-15.1000204 Ethernet Port Status
Abnormal.
10 After about 5 minutes, check whether the alarm is cleared.
Check the port status of the FTP server in the equipment room.
11 Check whether the FTP server is powered off or is faulty.
12 Power on the FTP server or contact the hardware maintenance personnel to rectify the faulty
FTP server.
14 Check whether the server reporting the alarm is not properly connected to the FTP server.
15 Reconnect the network cables.
Check the port status of the FTP server.
17 Use PuTTY to log in to the FTP server listed in Step 1.
Ensure that the management IP address and username root are used to establish the
connection.
18 Check whether the port on the FTP server is monitored.
When the port is monitored, the FTP service is enabled.
netstat -nlt | grep 22

FusionCompute
The port is monitored if information similar to the following is displayed:

tcp 0 0 192.168.85.10:22 0.0.0.0:* LISTEN
NOTE
22 is the port number of the FTP server in Step 1.

The description on the command output is as follows:
l The first column lists the protocol type.
l The third column lists the IP address of port number of the FTP server.
l The fifth column lists the port status. LISTEN indicates that the port is monitored.
Check whether the port is monitored.
19 Enable the FTP service by following the instructions in FTP product description.
----End
Related Information
None
5.1.8 ALM-15.1001013 Image Storage Server Unreachable
Description
The alarm module checks the communication between the Elastic Service Controller (ESC) node
and the Image Storage (IMGS) server every minute. This alarm is generated when the system
detects that the monitoring thread of the ESC cannot connect to the IMGS server.
This alarm is cleared when the monitoring thread properly connects to the IMGS server.
Attribute
Parameters
Name Meaning
Additional Information Specifies the IP address of the image server.


FusionCompute
Name Meaning

cleared.

generated.

The image service enables the IMGS server to share its image storage directory with the ESC
server in the /image/ folder on the ESC. If the ESC server fails to communicate with the IMGS
server, it cannot detect the image status and space usage of the IMGS, thereby greatly affecting
the ESC service.
Possible Causes
l The network between the ESC node and the IMGS server is faulty.
l The IMGS server is powered off or is faulty.
Procedure
Check the network status of the ESC node and IMGS server.
1 Obtain the IP address of the IMGS server from Additional Information in the alarm list.

FusionCompute
connection.
root interface:
su - root
TMOUT=0
ping IP address of the IMGS server
Check whether the communication between the ESC node and the IMGS server is normal.
7 On the FusionCompute, check whether ALM-15.1000204 Ethernet Port Status Abnormal
is generated on the Alarm page.
8 Handle the alarm by following the procedures in ALM-15.1000204 Ethernet Port Status
Abnormal.
Check the port status of the IMGS server in the equipment room.
10 Check whether the IMGS server is powered off or is faulty.
11 Power on the IMGS server or contact the hardware maintenance personnel to rectify the
faulty IMGS server.
13 Check whether the server reporting the alarm is not properly connected to the IMGS server.
14 Reconnect the network cables.
----End

FusionCompute
Related Information
None
5.1.9 ALM-15.1001014 Image Storage Space Insufficient
Description
The alarm module checks the usage of the image storage space of the Image Storage (IMGS)
node every minute. This alarm is generated when the system detects that the usage of the image
storage space exceeds the threshold.
This alarm is cleared when the Elastic Service Controller (ESC) monitoring thread detects that
the usage of the image storage space is less than the threshold.
Attribute
Parameters
Name Meaning
Additional Information Identifies the image storage server and the image storage.


cleared.


FusionCompute
Name Meaning
generated.

The image service enables the VM images used users to be stored under the /image/ directory
on the IMGS node. When the image storage space is insufficient, users cannot upload new VM
images to the IMGS node.
Possible Causes
l Too many image files are stored in the image storage space of the IMGS.
Procedure
Check the image files stored in the image storage space of the IMGS.
1 Obtain the IP address of the IMGS server from Additional Information in the alarm list.
Ensure that the management IP address of the IMGS server and username gandalf are used
to establish the connection.
root interface:
su - root
TMOUT=0
df /image/
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda1 10317828 5408480 4385232 56% /
Check whether the usage exceeds the threshold (the default threshold is 80%).
– If not, go to Step 7.
6 Deregister the unnecessary images on the ESC and delete unwanted image files from the
directory /image/.
–
----End

FusionCompute
Related Information
None
5.1.10 ALM-15.1001015 Data Store Space Insufficient
Description
The alarm module checks the usage of the data store registered in the Image Storage (IMGS)
node every minute. This alarm is generated when the system detects that the usage of the data
store is greater than the threshold.
This alarm is cleared when the Elastic Service Controller (ESC) monitoring thread detects that
the usage of all the data stores registered in the ESC is less than the threshold.
Attribute
15.1001015 Major Yes
Parameters
Name Meaning
Additional Information Provides supplementary information about the IP address and

port number of the File Transfer Protocol (FTP) server.


cleared.


FusionCompute
Name Meaning
generated.

A data store is registered in the ESC as a storage resource. VM or disk creation is performed on
the data store which has sufficient space. If the usage of the data store is too high, users cannot
create VMs or disks any more.
Possible Causes
l Too many VMs or disks are created on the data store.
Procedure
Check the usage of the data store in the ESC system.
1 In the alarm list, obtain the ID of the data store with insufficient space from Additional
Information.
2
Ensure that the username administrator is used to establish the connection.
3 On the FusionStack, select Service Cluster on the System Configuration page.
4 View the service clusters under Service Cluster, and select Data Store to view the space
usage of each data store.
5 Expand the capacity of the data store when its space usage is greater than the threshold
(80% by default). For details, see the data store capacity expansion guide. Or delete the
unnecessary VMs or disks from the data store in the system on which the VMs and disks
are created. Note that do not delete VMs or disks from the FusionCompute. Otherwise, data
inconsistency may occur between the ESC and the Virtual Resource Management (VRM).
Then check whether the alarm is cleared.
–
----End
Related Information
None

FusionCompute
5.1.11 ALM-15.1001020 SLB Node Unreachable
Description
The alarm module checks the status of the software load balancing (SLB) VM on the Elastic
Service Controller (ESC) node. This alarm is generated when the system detects that the SLB
VM is unreachable.
This alarm is cleared when the ESC monitoring thread detects that the SLB VM is reachable.
Attribute
15.1001020 Major Yes
Parameters
Name Meaning
Additional Information Specifies the SLB VM for which the alarm is generated.
Alarm Object Specifies the physical or logical hierarchical relationship of the alarm
in the system.
Clear Type Specifies whether the alarm is manually or automatically cleared.
SN Specifies the number assigned to the alarm based on the sequence that
the alarm is generated.

The load balancer service is transferred by SLB VMs. If the SLB VMs are unreachable, the load
balancer service is unavailable.

FusionCompute
Possible Causes
l The LB service process is abnormal.
l The operating system (OS) on the LB VM is faulty.
Procedure
1 On the FusionCompute, choose VDC Management > VM and Host.

2 Click the VM tab on the right.
The VM list is displayed.
3 Locate the faulty LB VM by its ID, and click the name of the VM.
4 In the Operation area, click Log In using VNC.
The VM desktop is displayed.
5 Check whether you can log in to the VM.
– If no, see the LB VM Faulty to reinstall the LB VM.
6 Run the following command to check the monitoring process status of the LB VM:
service monitord status
If unused is displayed, the LB VM is abnormal. If running is displayed, the LB VM is
normal.
7 Check whether the monitoring process is in the runningstate.
8 Run the following command to restart the monitoring process of the LB VM:
service monitord restart
9 Follow the instructions provided in Step 6 to check whether the monitoring process of the
LB VM is in the running state.
10 Three minutes after the monitoring process turns to the running state, check whether the
LB instance is in the READY state on the FusionStack.
11 Run the following commands to check the status of the corresponding LB VM process:
– Slb agent:service slbagentd status
– Slb:service slbd status
– Slb Portal:service slbportald status
12 For a process in the unused state, run the corresponding command as follows to restart it:
– Slb agent:service slbagentd restart
– Slb:service slbd restart

FusionCompute
– Slb Portal:service slbportald restart

13 Three minutes after the unused processes are restarted, check whether the LB instance is
in the READY state on the FusionStack.
----End
Related Information
None
5.1.12 ALM-15.1002000 Heartbeat Communication Between Active

and Standby Nodes Interrupted
Description
This alarm is generated when the active node detects that the management network connection
of the standby node is abnormal.
This alarm is generated when the active node detects that the management network connection
of the standby node becomes normal.
Attribute
15.1002000 Critical
Parameters
Name Meaning
Additional Information Specifies the IP address of the peer node.

generated.

FusionCompute
Name Meaning

cleared.


System reliability is affected.
Possible Causes
l The Computing Node Agent (CNA) where the standby node is located is powered off or
restarted.
l The operating system (OS) of the CNA where the standby node is located is faulty.
l The standby node is powered off or restarted.
l The OS of the standby node is faulty.
l The network is faulty.
Procedure
Obtain the data.
NOTE
The standby node described in this document refers to the standby node running on the current system, not
the default standby node configured during system installation.
1 Determine the deployment mode of the node.

a. Log in to the FusionStack. On the Alarm page, click Real-Time Alarm, and view
Additional Information in Alarm Details. Obtain the IP address of the peer node
from Additional Information, and consult the administrator to determine whether
the node is deployed in virtualization mode or physical mode.
b. If in virtualization mode, go to Step 2.
c. If in physical mode, go to Step 3.
2 Go following steps if the node is deployed in virtualization mode.

FusionCompute
a. Log in to the FusionCompute, choose VDC Management > VM and Template, and
click the VM tab. Click Advanced Search, enter the IP address of the standby node
in IP, and click Search to search the VMs on the standby node.
b. If the VM is in the stopped state, go to Step 19.
c. If the VM is in the running state, click the name of the VM to switch to the
Summary page. From Search under Basic Information, obtain the name of the CNA
where the VM is deployed.
d. Choose VDC Management > VM and Template, and click the Host tab. In the
Name text box, enter the name of the CNA where the standby node is located, click
Search to query the information about the CNA.
e. In the search result list, obtain the management IP address of the CNA from Host IP
Address, and the baseboard management controller (BMC) IP address of the CNA
from BMC IP. If the BMC IP address is null, contact the administrator to obtain the
BMC IP address of the CNA.
3 Go following steps if the node is deployed in physical mode.
a. Contact the administrator to obtain the BMC IP address of the standby node.
b. Open Internet Explorer on a local PC, enter http://BMC IP address of the standby
node in the address box, and press Enter.
c. Log in to the BMC system of the node as instructed.
d. If POWER OFF is displayed, power on the node.
e. If a message is displayed indicating that this OS is ready for login or the user has
logged in successfully, the OS status of the node is normal. After 5 minutes, check
whether the alarm is cleared. If yes, no further action is required. If no, contact
technical support.
f. If a message is displayed indicating that the OS is faulty, the node cannot be logged
in. Contact technical support.
4 Before clearing the alarm, contact administrator to obtain the data listed in Table 5-1.
Name Default Value
Specifies the floating IP address of the 192.168.40.3

node.
Specifies the management IP address of the 192.168.40.5

standby node.
Check the status of the CNA.

5 Check the status of the CNA queried.
– If the node is in the normal state, go to Step 19.
– If the node is in the power off or Fault state, go to Step 6.
Check the OS status of the CNA.
6 Open Internet Explorer, enter the following IP address in the address box, and press
Enter:
http://BMC IP address of the target CNA

FusionCompute
7 Log in to the BMC system of the CNA as instructed.

Both the default username and password for logging in to the BMC system are root. If the
default username and password are changed, please contact the administrator.
8 Click the link Remote Control on the left to open the remote control window.
9 Check the status of server in the remote control window.
– If POWER OFF is displayed, go to Step 11.
– If a message is displayed indicating that this OS is ready for login or the user has logged
in successfully, the OS status of the CNA is normal. Go to Step 10.
– If a message is displayed indicating that the OS is faulty, the CNA cannot be logged in
to. Contact technical support.
10 After 5 minutes, choose VDC Monitoring > Alarm.
Check whether the alarm is cleared automatically.
11 In the toolbar of the remote control window, click and select Power on. After power-
on, go to Step 9.
12 Use PuTTY to log in to the CNA.
connection.
interface:
su - root
14 Run the following command to check whether the management IP address of the CNA is
reachable:
ping floating IP address of the node
15 Use PuTTY to log in to the active node.
interface:
su - root
17 Run the following command to check whether the floating IP address of the CNA can be
pinged:
ping management IP address of the target CNA
18 Confirm whether Step 14 and Step 17 are pinged.
Check the VM status.
19 Check whether the VM on the standby node is in the Stopped state.

FusionCompute
20 Choose Operation > Power on.
Check whether the VM is powered on.

– If no, see ESC VM Fault and restore the VM.
Check whether the alarm is automatically cleared.

– If no, go to Step 22 and check the OS status of the node.
Check the OS status of the VM.
22 Locate the row that contains the VM which is deployed on the standby node, and choose
Operation > Log In Using VNC. Log in to the VNC page as user root and obtain the
password for the administrator.
Check whether the OS can be logged in.

– If yes, go to Step 23 and rectify the network.
– If no, see instructions in the ESC VM Fault and restore the VM.
Check the network.
interface:
su - root
cat /opt/galax/gcs/watchdog/conf/haconfig.xml | grep peerIp | awk -F "\"" {'print $4'}
The IP address obtained is the peer node management IP address configured in the software
monitoring process.
26 Check whether the management IP address is the same as that provided by the administrator.
interface:
su - root
vi /opt/galax/gcs/watchdog/conf/haconfig.xml
30 Press i to enter editing mode.

FusionCompute
In the opened file, change the value of peerIp to the management IP address of the standby
node provided by the administrator.
31 Press Esc and enter :wq to save the configuration and exit the vi editor.
32 Run the following command to restart the watchdog process:
service watchdog restart
Check whether the alarm is cleared automatically.

----End
Related Information
None
5.1.13 ALM-15.1002006 Heartbeat Communication Between the

Node and the NTP Server Interrupted
Description
This alarm is generated when the Network Time Protocol (NTP) service of the node or the
network between the node and the NTP is abnormal.
This alarm is cleared when the NTP service of the node and the network are functioning properly.
Attribute
15.1002006 Critical
Parameters
Name Meaning
Additional Information Specifies abnormal NTP service.

generated.

FusionCompute
Name Meaning

cleared.


The time accuracy of the node will be affected, if the heartbeat communication between the node
and the upper-layer clock source is interrupted. After the fault remains unrectified for 3 days,
the system time accuracy is affected.
Possible Causes
l The NTP service on the node is abnormal.
l The network between the node and the external NTP server is faulty.
Procedure
1 Select the current alarm on the Alarm page, and view Alarm Object in Alarm Details.
2 Choose System Management > System Configuration, and click Service and
Management Node. View information about the management node, and obtain the IP
address of the node whose name is the same as that of the Alarm Object in Step 1.
3 Use PuTTY to log in to the node.
connection.
interface:
su - root
5 Run the following command to check the NTP service status:
ntpq -p

FusionCompute
Determine the NTP service status according to the command output and go to the
corresponding step.
– If the information in the command output includes ntpq: read: Connection refused,
the NTP service on this node is abnormal. In this case, go to Step 9.
– If LOCAL is displayed in the remote column, the upper-layer clock source is not
configured in the system. In this case, contact the administrator to configure the clock
source.
remote refid st t when poll reach delay offset jitter
===========================================================================
===
*LOCAL(0) .LOCL. 5 l 32 64 377 0.000 0.000
0.001
– If the information in the remote column starts with *, the upper-layer clock source is
configured in the system, but the heartbeat communication is abnormal. In this case, go
to Step 6.
===========================================================================
=== *172.19.1.64 132.239.1.6 2 u 8 64 377 51.743 400.912
119.378
NOTE
l The information in the remote column indicates the remote NTP server connected to the
local computer.
l The NTP server column whose value starts with * displayed in the remote column is the
upper-layer NTP server in use.
– If the value in the reach column is 0, the heartbeat communication between the current
node and the NTP server may be interrupted. In this case, go to Step 6.
– If information in the remote column of the command output does not start with *, the
NTP service is abnormal or a heartbeat communication may be interrupted. In this case,
go to Step 6.
6 Contact the administrator to check whether the NTP server is available. After the NTP
server functions properly, obtain the IP address of the NTP server, run the following
command to check whether the heartbeat communication between the node and the upper-
layer NTP server is normal.
ping NTP server IP address
– If the heartbeat communication is abnormal, go to Step 7.
– If the heartbeat communication is normal, go to Step 8.
7 Contact the administrator to check the network between the node and the NTP server. After
the heartbeat communication is restored, go to Step 8.
NOTE
Do not perform any configuration operations when the alarm is being cleared.
8 Run the date command on the node to obtain the system time and compare the time with
the NTP server time to check whether the time difference is greater than 60 seconds.
– If yes, choose Service Configuration on the system page, choose Configure Time
Zone > Forcibly Synchronize Time, click Forcibly Synchronize Time, and click
OK in the displayed dialog box. After 60 seconds, go to Step 10.
NOTE
Forcibly synchronizing the system time with the NTP server will cause the service processes on
the node to restart. Therefore, the services that are being provided will be interrupted during the
forcible time synchronization. In addition, configuration operations are forbidden during the
alarm clearing.

FusionCompute
9 Run the following command to stop the NTP service:
service ntp stop
The NTP service is stopped if the following information is displayed:
Shutting down network time protocol daemon (NTPD) done
10 After 30 seconds, run the following command to obtain the synchronization cycle:
service ntp status
The value in the poll column of the command output indicates the synchronization cycle
in seconds.
If the information in the command output includes ntpq: read: Connection refused, go
to Step 12.
11 After five to ten synchronization cycles, check whether the alarm is cleared.
12 Contact technical support.
----End
Related Information
None
5.1.14 ALM-15.1004000 Invalid License File

Description
generated when the license file check fails or when the system fails to obtain the equipment
serial number (ESN).
Attribute
15.1004000 Major
Parameters
Name Meaning


FusionCompute
Name Meaning

cleared.

generated.

This alarm has no adverse impact on the system for 60 days after the license file is expired. After
60 days, some functions authorized by the license become unavailable.
Possible Causes
l The system fails to obtain the ESN.
l The device where the Virtual Resource Management (VRM) node is deployed has been
replaced but no license file has been loaded.
l The license file is lost or corrupted.
Procedure
Check whether the system can obtain the ESN.
1 Check whether the system can obtain the ESN.
Check whether the device where the VRM is deployed has been replaced.
2 Contact the administrator and check whether the device where the VRM is deployed has
been replaced.

FusionCompute
– If yes, obtain a new ESN and use the ESN to obtain a new license.
For details about how to obtain the ESN, see FusionCompute V100R003C00 License
Operation Guide.
Operation Guide.
----End
Related Information
None
5.1.15 ALM-15.1007004 NOTIFY Process Abnormal

Description
This alarm is generated when the system detects that the notify process stops or is faulty.
This alarm is cleared when the notify process becomes normal.
Attribute
15.1007004 Critical
Parameters
Name Meaning
Additional Information Abnormal process.


FusionCompute
Name Meaning

cleared.

generated.

If the notify process is abnormal, the alarm email notification function will be affected. The
alarm cannot be sent by emails.
Possible Causes
l The notify process stops abnormally.
l The notify process is faulty.
Procedure
Confirm the IP address of the faulty node.
2 Choose System > Service Configuration, and select Service and Management Node.
View information about the management nodes, and obtain the IP address of the node whose
name is the same as that of the Alarm Object in Step 1.
Restart the notify process.
connection.
interface:

FusionCompute
su - root
5 Run the following command to restart the process:
service notifyd restart

6 Run the following command to check the process status:
service notifyd status
Checking for notifyd: running
----End
Related Information
None
5.1.16 ALM-15.1007005 System Time Offset Exceeds One Minute
Description
The system checks the system time every 1 minute. This alarm is generated when the system
detects that the system time offset exceeds 1 minute.
Attribute
15.1007005 Major
Parameters
Name Meaning
Additional Information Specifies the time offset (in seconds).

generated.

FusionCompute
Name Meaning

cleared.


Services provided by the alarm-affected node are adversely affected.
The alarms generated during the time change/adjustment period sometimes need to be manually
cleared.
Possible Causes
l The administrator has changed the system time.
l The time on the clock source has changed.
l The administrator has changed the system time zone.
Procedure
Handle the alarm.
View information about the management nodes, and obtain the IP address of the
management node whose name is the same as that of the Alarm Object in Step 1.
connection.
interface:

FusionCompute
su - root
5 On the System Management page, choose Service Configuration > Time
Configuration > Time Synchronization and obtain the IP address of the NTP server.
6 Check whether the NTP server is configured for the system.
7 Run the ping NTP server IP address command to check whether the communication
between the node and the NTP server is normal.
8 Run the sh /usr/sbin/ntpdate NTP server IP address && /sbin/hwclock -w command
to synchronize the time between the node and the NTP server.
9 Check whether the command out contains sntp: not enough valid responses received in
time.

10 Run the following command to restart all the processes running on the node:
sh /opt/galax/gms/common/config/restartPorcess.sh
11 Check whether the command output is as follows:
restart all process success.

12 Three minutes later, go back to the Alarm page to manually clear this alarm.
13 Check whether the alarm is cleared.
Handle the alarm impact.
15 The alarm generation and handling are related to time change/adjustment. If the time is
adjusted backward, some alarms cannot be automatically cleared. For example, if the time
is adjusted from 09:00 (T1) to 08:00 (T2), the alarms generated from 08:00 (T0, original
08:00) to the current time after the adjustment cannot be automatically cleared. These
alarms need to be manually cleared. After the time reaches 09:00 (T3), on the Alarm page,
check whether the alarms generated from T2 to T3 are automatically cleared based on the
Online Help information. If not, manually clear the alarms.
----End
Related Information
None

FusionCompute
5.1.17 ALM-15.1007006 Abnormal Clock Synchronization Process

Description
This alarm is generated when the system detects that the clock synchronization process stops or
is faulty.
This alarm is cleared when the clock synchronization process becomes normal.
Attribute
15.1007006 Critical
Parameters
Name Meaning
Additional Information Identifies the abnormal process.

generated.

cleared.


FusionCompute

The time on the server node is inconsistent with that of other nodes. As a result, the monitoring
results and alarm information is inaccurate.
Possible Causes
l The clock synchronization process stops.
l The clock synchronization process is faulty.
Procedure
Restart the clock synchronization process.
connection.
interface:
su - root
5 Run the following command to restart the clock synchronization process:
service ntp restart

6 Run the following command to query the status of the time synchronization process:
service ntp status
==============================================================================
*LOCAL(0) .LOCL. 10 l 19 64 377 0.000 0.000
0.001
Checking for network time protocol daemon (NTPD): running
----End
Related Information
None

FusionCompute
5.1.18 ALM-15.1007007 Abnormal System Timing Service Process

Description
This alarm is generated when the system detects that the system timing service process stops or
is faulty.
This alarm is cleared when the system timing service process becomes normal.
Attribute
15.1007007 Critical
Parameters
Name Meaning

generated.

cleared.


FusionCompute

The scheduled tasks to be performed on the node may not be executed as scheduled, which will
affect the functionality and stability of the system.
Possible Causes
l The system timing service process stops.
l The system timing service process is faulty.
Procedure
Restart the system timing service process.
connection.
interface:
su - root
5 Run the following command to restart the system timing service process:
service cron restart

service cron status
Checking for Cron:
running
----End
Related Information
None

FusionCompute
5.1.19 ALM-15.1007011 Configuration Channel Client Process Is

Abnormal
Description
This alarm is generated when the system detects that the configuration channel client process
stops or is faulty.
This alarm is cleared when the configuration channel client process becomes normal.
Attribute
15.1007011 Critical
Parameters
Name Meaning


cleared.


FusionCompute
Name Meaning
generated.

The operations performed in the configuration channel and the data provisioning function will
be affected.
Possible Causes
l The configuration channel client process stopped abnormally.
l The configuration channel client process is faulty.
Procedure
Confirm the IP address of the Virtual Resource Management (VRM) node.
1 Select the current alarm, and view Alarm Object in Alarm Details.
2 Choose System Management > Service Configuration, and click Service and
Management. View information about the management nodes, and obtain the IP address
of the node whose name is the same as that of the Alarm Object in Step 1.
Restart the configuration channel client process.
connection.
interface:
su - root
5 Run the following command to restart the process:
service cmad restart

service cmad status
Checking for service cma:
running
9 Contact Huawei technical support.
----End

FusionCompute
Related Information
None
5.1.20 ALM-15.1007012 NFS Service Process on the Image Storage

Server Abnormal
Description
This alarm is generated when the system detects that the Network File Server (NFS) service on
the Image Storage (IMGS) server is abnormal.
Attribute
Parameters
Name Meaning
Additional Information Specifies the IP address of the object for which the alarm is
generated.


cleared.


FusionCompute
Name Meaning
generated.

NFS service on the IMGS server is required for loading images during VM creation. If the NFS
process is abnormal, VM creation will be affected.
Procedure
Restart the NFS process on the IMGS server.
1 On the FusionStack, locate the row that contains the alarm in the real-time alarm list, and
click Alarm Object.
2
The detailed information about this alarm object is displayed. Obtain the management IP
address of the alarm object from the Basic Information area.
3 Use PuTTY to log in to the alarm object listed in step 2. Ensure that the management IP
address and username gandalf are used to establish the connection. Run the su - root
command and enter the password of user root to switch to the user root interface:
4 Run the service nfsserver restart command to restart the process:
5 Run the service nfsserver status command to check the process status:

Checking for kernel based NFS server: idmapd runnning
mountd runnning
statd runnning
nfsd runnning
----End
Related Information
None

FusionCompute
5.1.21 ALM-15.1007013 Image Management (IMGM) Process

Abnormal
Description
This alarm is generated when the system detects that the Image Management (IMGM) process
is abnormal.
Attribute
Parameters
Name Meaning
generated.


cleared.


FusionCompute
Name Meaning
generated.

The IMGM process manages all the images in the Elastic Service Controller (ESC) node. If this
process is abnormal, VM creation will be affected.
Procedure
Restart the IMGM process.
click Alarm Object.
2
4 Run the service imgmd restart command to restart the process:
5 Run the service imgmd status command to check the process status:
Result:normal runnning
----End
Related Information
None
5.1.22 ALM-15.1007014 Elastic Computing Service Process on the

ESC Node Abnormal
Description
This alarm is generated when the system detects that the elastic computing service process on
the Elastic Service Controller (ESC) node is abnormal.

FusionCompute
Attribute
Parameters
Name Meaning
generated.


cleared.

generated.

The elastic computing service process implements computing resource scheduling and VM
creation. If this process is abnormal, the system is unavailable.
Procedure
Restart the elastic computing process on the ESC node.

FusionCompute
click Alarm Object.
2
4 Run the service cloudd restart command to restart the process:
5 Run the service cloudd status command to check the process status:
Checking for service cloud running
----End
Related Information
None
5.1.23 ALM-15.1007015 UPF Service Process Abnormal
Description
This alarm is generated when the system detects that the User Profile Function (UPF) service
process is abnormal.
Attribute
Parameters
Name Meaning
generated.

FusionCompute
Name Meaning


cleared.

generated.

UPF service process manages user's authentication and account application data. If this process
is abnormal, the system is unavailable.
Procedure
Restart the UPF service process.
click Alarm Object.
2
4 Run the service ldap restart command to restart the process:

FusionCompute
5 Run the service ldap status command to check the process status:
Checking for ldap: running
----End
Related Information
None
5.1.24 ALM-15.1007016 ELB Service Process Abnormal
Description
This alarm is generated when the system detects that the elastic load balancing (ELB) service
process is abnormal.
Attribute
Parameters
Name Meaning
generated.


cleared.

FusionCompute
Name Meaning

generated.

The ELB service process implements load balancing. If this process is abnormal, the ELB service
is unavailable.
Procedure
Restart the ELB service process.
click Alarm Object.
2
4 Run the service elbd restart command to restart the process:
5 Run the service elbd status command to check the process status:
Checking for service slb
Result:normal running
----End

FusionCompute
Related Information
None
5.1.25 ALM-15.1007099 Failure in Backing up or Uploading Key

Data
Description
This alarm is generated when the system detects that key data fails to be backed up or uploaded
to the File Transfer Protocol (FTP) server.
Attribute
15.1007099 Major
Parameters
Name Meaning

generated.

cleared.


FusionCompute
Name Meaning

Key data cannot be successful backed up or uploaded. As a result, data reliability cannot be
ensured. If the active and standby nodes are faulty on the day when data backup or upload failure
occurs, data generated on that day cannot be restored.
Possible Causes
l The remaining disk space on the node is insufficient.
l The FTP server is incorrectly configured.
l The network communication between the node and the FTP server is faulty.
l An error occurred when running the setConfig command to upload the FTP server
configurations.
Procedure
connection.
interface:
su - root
5 Run the df -h /var/backup command to check whether the remaining storage space is
available on the node. If yes, delete unnecessary files in this directory, or transfer the
existing flies under this directory to other directories.
6 Check whether the FTP server is correctly configured.
7 Run the ping FTP server's IP address command to check whether the network connection
between the local PC and the FTP server is normal. If no, check the network configuration
and cable connection, and recover the network connection.
8 Run the setConfig command to check whether the FTP client is correctly configured. If
no, run this command again to configure the FTP client correctly.
9 Manually clear the alarm.
10 Run the cronBackupUpload command to back up data, and check whether this alarm is
generated again. If yes, go to Step 11.

FusionCompute
----End
Related Information
None
5.1.26 ALM-15.1008000 Communication with License Server Is

Abnormal
Description
The license module checks the communication between the client and the license server every
5 minutes. This alarm is generated when the communication between the client and the license
server is interrupted for three consecutive times.
This alarm is cleared when the communication between the client and the license server becomes
normal.
Attribute
15.1008000 Major
Parameters
Name Meaning


cleared.


FusionCompute
Name Meaning
generated.

Adding hosts to the client is affected.
Possible Causes
l The IP address configured for the license server is incorrect.
l The time on the client is inconsistent with that on the license server.
l The username and password configured for the license server may be incorrect.
Procedure
Check the license configuration on the client.
1 Check whether the IP address is correctly configured for the license server.
2 Configure a correct IP address for the license server.
3 Check whether the time on the client is consistent with that on the license server.
– If no, configure the time on the client and ensure it is consistent with that on the license
server.
4 Check whether the username and password configured for the license server is correct.
– If no, obtain the correct username and password of the license server, and configure
them for the license server again.
----End
Related Information
None

FusionCompute
5.1.27 ALM-15.1008001 Free Upgrade Service Is About to Expire
Description
The alarm module verifies the validity of the license for free upgrade service between 00:00 and
02:00 every day. This alarm is generated when the free upgrade service is about to expire in less
than 60 days.
Attribute
15.1008001 l Threshold for a warning alarm: 30 ≤ Remaining days before free upgrade
service expiration < 60
l Threshold for a minor alarm: 0 ≤ Remaining days before free upgrade service
expiration < 30
NOTE
The values 30 and 60 are the default alarm thresholds.
Parameters
Name Meaning
Additional Information Remaining days before free upgrade service expiration


cleared.


FusionCompute
Name Meaning
generated.

Upgrade services will be affected after the free upgrade service expires.
Possible Causes
l The license for the free upgrade service is about to expire.
Procedure
Update the license for free upgrade service.
2 Apply for a new license.
Operation Guide.
----End
Related Information
None
5.1.28 ALM-15.1008002 Free Upgrade Service Has Expired
Description
The alarm module verifies the license validity during the hours from 00:00 to 02:00 every day.
This alarm is generated when the licensed free upgrade service has expired for at least 60 days.
This alarm is cleared when a valid license file is loaded to the system.

FusionCompute
Attribute
15.1008002 Major
Parameters
Name Meaning


cleared.

generated.

Upgrade services will be affected after the free upgrade service has expired.
Possible Causes
l The free upgrade service has expired.

FusionCompute
Procedure
Update the license for the free upgrade service.
1 Check whether the license for the free upgrade service is purchased.
See the FusionCompute V100R003C00 License Operation Guide.
----End
Related Information
None
5.1.29 ALM-15.3002005 Number of In-Use CPUs on the CNA

Exceeds 90% of the Licensed Total Number
Description
The alarm module checks the number of in-use CPUs on all the CNA nodes every 5 minutes.
This alarm is generated when the system detects that the number of in-use CPUs is greater than
90% of the licensed total number.
This alarm is cleared when the number of in-use CPUs is less than 90% of the licensed total
number.
Attribute
15.3002005 Warning
Parameters
Name Meaning
Additional Information Allowed CPU usage of the CNAs


FusionCompute
Name Meaning

Sprache

Willkommen bei Scribd!

FusionCompute V100R003C00 FusionStack User Guide 01.pdf

Hochgeladen von

Dokumentinformationen

Datum des Uploads

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Beschreibung:

Copyright:

Verfügbare Formate

FusionCompute V100R003C00 FusionStack User Guide 01.pdf

Hochgeladen von

Beschreibung:

Copyright:

Verfügbare Formate

Verwandte Titel

FusionCompute

FusionStack User Guide

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 01 (2013-04-10) Huawei Proprietary and Confidential i

About This Document

l Installation and commissioning engineers

Alerts you to a high risk hazard that could, if not avoided,

Alerts you to a medium or low risk hazard that could, if

Alerts you to a potentially hazardous situation that could,

NOTE Provides additional information to emphasize or

Issue 01 (2013-04-10) Huawei Proprietary and Confidential ii

Issue 01 (2013-04-10) Huawei Proprietary and Confidential iii

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

Issue 01 (2013-04-10) Huawei Proprietary and Confidential iv

2.5.6 Adding an L2Area Network....................................................................................................................60

4 Operation and Maintenance....................................................................................................111

Issue 01 (2013-04-10) Huawei Proprietary and Confidential v

4.2.4 Freezing or Unfreezing an Image..........................................................................................................130

Issue 01 (2013-04-10) Huawei Proprietary and Confidential vi

Issue 01 (2013-04-10) Huawei Proprietary and Confidential vii

About This Chapter

1.1 Product Introduction

Issue 01 (2013-04-10) Huawei Proprietary and Confidential 1

1.1 Product Introduction

Position in the FusionCompute

Figure 1-1 FusionCompute components

Image management Backup ELB

VPC Multi-Tenant Elastic IP

Virtualization infrastructure platform

Availability Security Expandability

Computing Storage Network

Issue 01 (2013-04-10) Huawei Proprietary and Confidential 2

1.2 Product Architecture

Figure 1-2 Logical architecture of the FusionStack

IMGS UPF POE

IMGM ESC ESC-OM

UHM VRM LBManager

IMGS: Image Storage UPF: User Profile Function POE: Provisioning

UHM: Unified Hardware VRM: Virtual Resource LBManager: Elastic Load

1.3 Deployment Scheme

Issue 01 (2013-04-10) Huawei Proprietary and Confidential 3

Figure 1-3 Logical nodes of the FusionStack

Cloud basic services

Active Standby IMGS1 IMGS2

Table 1-1 Deployment Principles

Image Storage (IMGS) In virtualization deployment, the IMGS is deployed on a

Issue 01 (2013-04-10) Huawei Proprietary and Confidential 4

Table 1-2 VM specifications

ESC 4 CPUs and 8 6 CPUs and 12 8 CPUs and 32 16 CPUs and 64

IMGS 4 CPUs and 4 4 CPUs and 4 4 CPUs and 4 4 CPUs and 4 GB

1.4 Product Functions

Issue 01 (2013-04-10) Huawei Proprietary and Confidential 5

1.6 Technical Indicators

Issue 01 (2013-04-10) Huawei Proprietary and Confidential 6

Table 1-3 Capacity Indicators

Maximum number of sites supported by the 16