Imanager U2000 V200R016C50 Single-Server System Software Installation and Commissioning Guide (Windows 7) 05 PDF

iManager U2000 Unified Network Management
System
V200R016C50
Single-Server System Software

Installation and Commissioning
Guide (Windows 7)
Issue 05
Date 2017-08-30
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2017. 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://www.huawei.com
Email: [email protected]
Issue 05 (2017-08-30) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
Single-Server System Software Installation and
Commissioning Guide (Windows 7) About This Document
About This Document
Related Version
The following table lists the product version related to this document.
Product Name Version
iManager U2000 V200R016C50
Intended Audience
This document describes how to install the U2000 and obtain the reference information
required during the installation.
This document is intended for:
l Technical support engineers

l Maintenance engineers
l Installation and commissioning engineers
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Indicates an imminently hazardous situation

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

which, if not avoided, could result in death
or serious injury.

which, if not avoided, may result in minor
or moderate injury.
Issue 05 (2017-08-30) Huawei Proprietary and Confidential ii

Symbol Description

which, if not avoided, could result in
equipment damage, data loss, performance
deterioration, or unanticipated results.
NOTICE is used to address practices not
related to personal injury.
Calls attention to important information,

best practices and tips.
NOTE is used to address information not
related to personal injury, equipment
damage, and environment deterioration.
Command Conventions
The command conventions that may be found in this document are defined as follows.
Convention Description
Boldface The keywords of a command line are in boldface.
Italic Command arguments are in italics.
[] Items (keywords or arguments) in brackets [ ] are optional.
{ x | y | ... } Optional items are grouped in braces and separated by

vertical bars. One item is selected.
[ x | y | ... ] Optional items are grouped in brackets and separated by

vertical bars. One item is selected or no item is selected.
{ x | y | ... }* Optional items are grouped in braces and separated by

vertical bars. A minimum of one item or a maximum of all
items can be selected.
[ x | y | ... ]* Optional items are grouped in brackets and separated by

vertical bars. Several items or no item can be selected.
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Boldface Buttons, menus, parameters, tabs, window, and dialog titles

are in boldface. For example, click OK.
Issue 05 (2017-08-30) Huawei Proprietary and Confidential iii

> Multi-level menus are in boldface and separated by the ">"

signs. For example, choose File > Create > Folder.
Change History
Updates between document issues are cumulative. Therefore, the latest document issue
contains all updates made in previous issues.
Changes in Issue 05 (2017-08-30) Based on Product Version V200R016C50

The fifth commercial release has the following updates:
Fixed some bugs.

The fourth commercial release has the following updates:
Fixed some bugs.

The third commercial release has the following updates:
Fixed some bugs.

The second commercial release has the following updates:
Fixed some bugs.

Initial release.
Issue 05 (2017-08-30) Huawei Proprietary and Confidential iv

Commissioning Guide (Windows 7) Contents
Contents
About This Document.....................................................................................................................ii

1 Performance indicators.................................................................................................................1
2 U2000 Management Capability...................................................................................................3
3 Installation Overview................................................................................................................... 5
4 Installation and Commissioning Process................................................................................. 7
5 Installation Preparations............................................................................................................ 10
5.1 Configuration Requirements.........................................................................................................................................11
5.2 Networking Structure................................................................................................................................................... 12
5.3 Collecting Installation Information.............................................................................................................................. 13
5.4 Checking Required Software........................................................................................................................................17
5.5 Checking Hardware Connections................................................................................................................................. 20
5.6 Applying for a U2000 License..................................................................................................................................... 21
6 Powering On a Server................................................................................................................. 23
7 Installing the U2000 Server........................................................................................................24
7.1 Preparing Software Packages....................................................................................................................................... 25
7.2 Pre-installation Check...................................................................................................................................................26
7.3 Starting the U2000 Installation Program...................................................................................................................... 28
7.4 Loading a U2000 License.............................................................................................................................................34
7.5 Verifying the U2000 Server Installation....................................................................................................................... 36
7.5.1 Checking Environment Variables.............................................................................................................................. 36
7.5.2 Checking the U2000 Version..................................................................................................................................... 37
8 Commissioning the U2000......................................................................................................... 38

8.1 Commissioning Preparation......................................................................................................................................... 39
8.1.1 Obtaining Commissioning Parameters...................................................................................................................... 39
8.1.2 Checking Hardware Connections.............................................................................................................................. 75
8.2 Performing Commissioning..........................................................................................................................................76
8.2.1 Powering On a Server................................................................................................................................................76
8.2.2 Configuring System Commissioning Parameters......................................................................................................76
8.2.3 Commissioning U2000 Parameters........................................................................................................................... 79
9 FAQ................................................................................................................................................ 82
Issue 05 (2017-08-30) Huawei Proprietary and Confidential v

9.1 Windows OS................................................................................................................................................................. 83

9.1.1 How to Change the IP Address of the Single-Server System....................................................................................83
9.1.2 Changing the Password of the MSuite...................................................................................................................... 85
9.1.3 Logging In to the MSuite Client................................................................................................................................85
9.1.4 Updating Network Configurations............................................................................................................................ 87
9.1.5 How to Add a Static Route........................................................................................................................................ 88
9.1.6 How to Convert the File System Type to NTFS........................................................................................................88
9.1.7 How to Change the Password of the OS Administrator............................................................................................ 89
9.1.8 How to Configure the Remote Login to the Windows OS........................................................................................ 89
9.1.9 How to Forcibly End a Process................................................................................................................................. 90
9.1.10 How to Configure the FTP or SFTP Service on Windows OS................................................................................90
9.1.11 How to Set the Virtual Memory to the System Managed Size................................................................................ 91
9.1.12 How to Query the Type of a Windows OS.............................................................................................................. 92
9.1.13 How to Log In to the CLI on Windows................................................................................................................... 92
9.1.14 How to Shut Down Automatic Update of the Windows OS................................................................................... 93
9.1.15 How do I to partition disks on Windows 7 without loss..........................................................................................93
9.2 SQL Server Database....................................................................................................................................................94
9.2.1 How to Check Whether the SQL Server Database Has Been Installed.....................................................................94
9.2.2 How to Shut Down the SQL Server Database...........................................................................................................94
9.2.3 How do I start the SQL Server database....................................................................................................................95
9.2.4 How to Check Whether the SQL Server Database Can Be Sorted in Binary Mode................................................. 95
9.2.5 How to Manually Uninstall the Microsoft SQL Server Database............................................................................. 96
9.2.6 How to check the name of the SQL Server database server......................................................................................99
9.2.7 How to Check the Version of the SQL Server Database Server................................................................................99
9.3 U2000 System.............................................................................................................................................................100
9.3.1 How do I verify that the processes of the U2000 single-server system are running on Windows.......................... 100
9.3.2 How do I start the processes of the U2000 single-server system............................................................................ 100
9.3.3 How do I end the processes of the U2000 single-server system............................................................................. 101
9.3.4 How to Resolve the Problem Wherein the Message "PATH environment's length is too long" Is Displayed During
.......................................................................................................................................................................................... 102
9.3.5 Which Installation Packages Are Required for U2000 Installation.........................................................................102
9.3.6 How to Process the Message Displayed During Installation of the U2000, Indicating That a Suspended File Has
Been Created.....................................................................................................................................................................105
9.3.7 How to Resolve the Problem that the Database Installation File Is Not Found During Installation.......................105
9.3.8 Failure to Connect to the Database When the Progress Bar for File Copy Reaches 80% During Installation of the
U2000 Server Software.................................................................................................................................................... 106
9.3.9 How to Handle the Problem Wherein the System Displays a Message Indicating That the Client Installation
Packages and Basic Packages Cannot Exist at the Same Time During Decompression..................................................106
9.3.10 How Do I Verify Downloaded Software Packages Using the PGPVerify Software............................................. 107
9.3.11 How to Set the Communication Mode on the U2000 server for the Single-Server System (Windows)...............109
9.3.12 How to Resolve the Problem that the License Does Not Take Effect................................................................... 110
9.3.13 How to Confirm the Encoding Format of the U2000 License File........................................................................111
9.3.14 Failure to Log In to the U2000 Server from a U2000 Client.................................................................................111
Issue 05 (2017-08-30) Huawei Proprietary and Confidential vi

9.3.15 How to Rectify the Failure to Open the CAU Download Web Page Because the Port Is Used............................114
9.3.16 How to Solve the Problem Where the U2000 Server Fails to Be Installed Due to a Network Issue.................... 114
9.4 Handling the Failure to Install the U2000 Server Software........................................................................................115
10 Uninstalling the U2000 Server.............................................................................................. 117

10.1 Uninstallation Preparations.......................................................................................................................................118
10.2 Uninstallation Procedure...........................................................................................................................................118
10.3 Verifying the U2000 Server Uninstallation.............................................................................................................. 119
11 Manual Commissioning Task............................................................................................... 121

11.1 Configuring a Digital Certificate.............................................................................................................................. 122
11.1.1 Replacing SSL Certificates Used for the U2000 Server........................................................................................122
11.1.2 Deploying the SSL Trust Certificate on the Internet Explorer.............................................................................. 125
12 Starting the U2000 Server in a Windows Single-Server System.................................... 127

12.1 Powering On the Server Safely................................................................................................................................ 128
12.2 Starting the Database................................................................................................................................................ 128
12.3 Starting the U2000 Server Processes........................................................................................................................128
13 Powering Off the System....................................................................................................... 131

13.1 Stopping the U2000 Server Processes...................................................................................................................... 132
13.2 Shutting Down the Database.................................................................................................................................... 132
13.3 Powering Off the Server Safely................................................................................................................................133
14 Glossary and Abbreviations..................................................................................................135
Issue 05 (2017-08-30) Huawei Proprietary and Confidential vii

Commissioning Guide (Windows 7) 1 Performance indicators
1 Performance indicators
This topic describes the performance indicators of the U2000.
Table 1-1 Performance indicators

Item Subitem Indicator
Database restoration time ≤ 60 minutes
Storage capacity Capacity of current alarms Maximum: 10000
Capacity of historical alarms Maximum: 100000

Storage period in the
database: 180 days
Capacity of logs, including Maximum: 50000

operation logs and system Storage period in the
logs database: 90 days
Link capacity Number of manageable Maximum: 500

links in the topology
Processing capability Response speed of handling Usually equal to or less than

an alarm 10 seconds.
Issue 05 (2017-08-30) Huawei Proprietary and Confidential 1

Commissioning Guide (Windows 7) 1 Performance indicators
Performance collection Maximum performance

capability collection capability in each
collection mode (Max
Equivalent Statistics
Record/15 Minutes):
l SNMP collection:
– Without Max/Min
Data Aggregation
Enabled: 5000.
– With Max/Min Data
Aggregation Enabled:
3000.
l BULK collection:
Unsupported.
l Qx collection: 5000
collection instances/30
minutes.
Alarm handling capability 10 alarms per second.
Concurrent NE upgrades Maximum: 20

Commissioning Guide (Windows 7) 2 U2000 Management Capability
2 U2000 Management Capability
This section describes U2000 Management Capability in Windows7 OS.

The key technical specifications include the number of equivalent NEs, number of clients, and
number of physical NEs. The management capability of the U2000 on a network that consists
of different types of NEs is affected by the following factors:
l If a client also runs on the computer where the server is running, the management
capability is reduced by 50%. Running the client and server on different computers is
recommended.
l The system limits the number of physical nodes, which in turn limits the management
capability.
l Windows 7 supports only single domain management instead of cross-domain
management.
Table 2-1 shows the management capability of a single U2000

Management capability Number of managed Maximum: 500 equivalent

equivalent NEs NEs
Number of managed Maximum: 500 physical

physical nodes NEs
Number of managed ONTs Maximum: 2000 ONTs
Service capability Number of managed SDH Maximum: 8000 SDH trails

trails
Number of managed WDM Maximum: 4000 WDM

trails trails
Number of managed IP Maximum: 20000 IP service

service access interfaces access interfaces (SAIs)
(SAIs)
Number of managed tunnels Maximum: 5000

Commissioning Guide (Windows 7) 2 U2000 Management Capability
Number of managed sites Maximum: 10000

(single-point services, such
as VRF and VSI)

Commissioning Guide (Windows 7) 3 Installation Overview
3 Installation Overview
This section explains the installation solution, the terms and restrictions involved with
installing the U2000 on Windows 7.
Installation Solution Overview

The U2000 can be installed in the Windows 7 Single-server system.
Terms
To ensure the U2000 install successfully, definitions for terms as used in this document before
introducing the U2000 scheme:
l Server: A server can refer to either hardware or software. In the client/server structure, a
server refers to the server program. The term refers to hardware when used in reference
to a computer where a server program runs.
l Workstation: A workstation refers to a high-end microcomputer equipped with a large
and high-resolution monitor, and large-capacity memory and hard disks. The workstation
has powerful functions of processing information, such as images, and network
connection functions.
NOTE
High-performance and cost-effective workstations always replace servers to serve the enterprise
network. Servers in this document refer to workstations unless otherwise specified. This complies
with the description in the U2000 Single-Server System Software Installation Guide (Windows).
l Server and host: A server functions the same as a host. Generally, a server or host refers
to the computer where services run in a Windows OS.
l Component: Refers to a functional unit of software that you can select to install. A
component can consist of multiple deployment packages.
l Deployment package: Refers to a software unit that is deployed on a computer.
Deployment packages are classified into the following types:
– System single-instance: These types of deployment packages can be installed on
only one server and each component can be deployed with only one instance.
– Single-server single-instance: These types of deployment packages can be installed
on multiple servers and each component can be deployed with only one instance on
each server.

Commissioning Guide (Windows 7) 3 Installation Overview
– Single-server multi-instance: These types of deployment packages can be installed

on multiple servers and each component can be deployed with multiple instances on
each server.
l Instance: It is a physical process that appears after the deployment package is deployed.
You can add the instance during the installation of the U2000, or add the instance
through the MSuite after the U2000 is installed.
NOTE
Generally, instances have relevant databases and processes. Some instances that have only
processes use the databases of other instances. Instance names are irrelevant with process names.
You can change instance names by using the MSuite.
Restrictions on Installation and Commissioning

You must learn the restrictions of the U2000 during the U2000 installation and
commissioning.Read carefully the following restrictions before installation and
commissioning:
l To prevent program conflict, it is recommended that other unnecessary software not be
installed on the U2000 server.
l Only one U2000 can be installed on a server.
l The U2000 software can be installed on the OS with either the simplified Chinese
version or English version.
l Installing the U2000 server software on Windows XP is not supported.

Commissioning Guide (Windows 7) 4 Installation and Commissioning Process
4 Installation and Commissioning Process
This section describes the process of installing the U2000 server software. The SQL Server
2008 database software and U2000 server software need to be installed. The pre-installation
schemes and installation scheme are available.
l Pre-installation scheme: The OS, patches, and U2000 software are pre-installed on
servers delivered by Huawei. Commission the servers directly.
l Installation scheme: If servers are purchased from other suppliers, install the U2000
server software according to a U2000 deployment plan. For details, see the associated
part in the manual.
Shows the installation flowchart for the U2000 software.

Figure 4-1 Installation flowchart for the single-server system (Windows 7)

NOTE
The installation of the U2000 server software includes installing the database software. If the database
has been installed on the system, check whether the database can meet U2000 installation requirements.
If the database does not meet the installation requirements, uninstall and then reinstall it.

Commissioning Guide (Windows 7) 5 Installation Preparations
5 Installation Preparations
About This Chapter
Before installing the U2000 server, you need to learn the configuration requirements and
networking structure of the U2000 server, collect installation information, check the software,
hardware, and environment, and apply for U2000 licenses.
5.1 Configuration Requirements
This section describes the configuration requirements on the hardware and software of the
server before installing the U2000.
5.2 Networking Structure
This section describes the networking structure of the single-server system.
5.3 Collecting Installation Information
This section describes how to collect installation information. Before installation, collect
required information, including the host name, IP address, time zone and time, user password,
and Disk Partition Scheme.
5.4 Checking Required Software
This section describes the software required to be checked. Ensure that the required software
is on-hand and meets the installation requirements before installing the U2000.
5.5 Checking Hardware Connections
This section describes how to check hardware installation and cable connections before
installing a U2000. If hardware is improperly installed or cable is improperly connected,
unexpected error may occur during installation of the U2000.
5.6 Applying for a U2000 License
The U2000 license file is used to control the functions and management capabilities of the
U2000. If the license file is unavailable, you cannot log in to the U2000 client, but can log in
to the System Monitor client and the MSuite.

5.1 Configuration Requirements

This section describes the configuration requirements on the hardware and software of the
server before installing the U2000.
Hardware Configuration
The following table shows the configuration requirements on the hardware for the U2000
server.
Table 5-1 Configuration requirements on the hardware for the U2000 server
Network Scale PC Server (Windows 7- Number of Clients

Supported)
Small-scale network: less HP Z230 5

than 2000 equivalent NEs l CPU: Xeon E3-1225 4
Core 3.20 GHz or above
l Memory: 16 GB or
above
l Hard disk: 1 TB or above
NOTE
l The preceding table shows the recommended delivery configuration. The compatible configuration
varies according to managed NEs and network size.
l For the incompatible servers with non-recommended configurations, you do not need to ensure that
the U2000 can be properly installed, deployed, and operated on servers whose configurations are not
compatible and recommended.
Software Configuration
The following table shows the configuration requirements on the software for the U2000
server.
Table 5-2 Configuration requirements on the software for the U2000 server
Configuration Item Typical Configurations
Database Delivered software platform: MS SQL

Server 2008 SP3 Personal
NMS software U2000 software
OS Windows 7 Professional

NOTE
l Installing the U2000 server software on Windows XP is not supported.

l Only one U2000 can be installed on a server.
l The U2000 software can be installed on the OS with either the simplified Chinese version or English
version.
5.2 Networking Structure

This section describes the networking structure of the single-server system.
Shows the networking structure of the Windows-based single-server system.

Figure 5-1 Networking diagram for a Windows-based single-server system
5.3 Collecting Installation Information

This section describes how to collect installation information. Before installation, collect
required information, including the host name, IP address, time zone and time, user password,
and Disk Partition Scheme.

Application Scenarios
The scenarios to which this document applies will be described.
The scenarios to describe are based on the following configurations:
l Hardware: one server and peripheral devices.

l Software: Windows 7 OS.
IP Address Planning
Planning Principles for IP Addresses are:
l The IP addresses must be unique on the network.

l The NMS application IP address communicate with the OSS in the normal state.
l The NMS application IP address communicate with the managed equipment in the
normal state.
l The NMS application IP address communicate with U2000 clients in the normal state.
NOTE
Log in to the server OS as user root, run the command ping -S NMS_application_IP
Destination_IP to ensure that NMS application IP address can be normal communicated.
l You can plan only one IP address for one network interface. It is not allowed to plan or
set multiple IP addresses for the same network interface.
Table 5-3 IP Address Type
IP Address Description
NMS application IP This IP address is used for external NMS services such as
address communication between the NMS server and clients or between the
NMS server and NEs.
System IP address This IP address is the IP address of the OS. You can use it to log in
to the server to manage and maintain the OS.
Table 5-4 System IP address list
Item Example Plan
System IP address 129.9.1.1/255.255.255.0/129

.9.1.254
NOTE
The IP address is in the format of IP address/subnet mask/gateway.

If multiple IP addresses are configured for the same network interface on the server, back up the current
IP address and delete all the IP addresses except the primary IP address. After the U2000 is installed,
add the deleted IP addresses.

Time Zone and Time Planning
Table 5-5 Time zone and time list
Item Example Plan
Time zone GMT+08:00
Time 14:00
User Name and Password Planning
NOTICE
l Recommended to install U2000 software as administrator user.
l The passwords are examples only. Change the passwords after completing the installation.
The default password indicates the initial password used when the U2000 is installed for
the first time. Production preinstallation indicates the U2000 software has been installed
initially.
Table 5-6 User and password list
User Default Password Password Set Planned Password

After
Preinstallation
OS super user Changeme_123 Changeme_123

administrator NOTE
During OS
installation, a
message will be
displayed asking you
whether to set the
password for the OS
user administrator.
OS user ossuser Changeme_123 Changeme_123
OS user dbuser Changeme_123 Changeme_123
OS user ftpuser Changeme_123 Changeme_123
Database user None. Changeme_123

dbuser
H2 database user Changeme_123 Changeme_123

dbuser
H2 database user Changeme_123 Changeme_123

ossuser

User Default Password Password Set Planned Password

After
Preinstallation
U2000 user admin Changeme_123 Admin_123

NOTE
You must change the
default password
during first-time
login.
The password for the
U2000 System
Monitor must be the
same as that for the
U2000 client.
Msuite user admin Changeme_123 Changeme_123

NOTE
You must change the
default password
during first-time
login.
Disk Partition Scheme
NOTICE
Partition OS disks according to the recommendations mentioned in the following table.
Table 5-7 Server disk partition list (1TB)

Partition Size (GB) Description
Disk C 100 It is used to store the OS.
Disk D 400 It is used to install the

U2000 software and
database software.
Disk E 500 It is used to back up data for

the U2000.
NOTE
For details about how to process server disk partition faults, see How to Partition Disks on Windows 7
Without Loss.

Installation Path Planning
Table 5-8 Installation path list

Software Installation Path
SQL Server 2008 database data The default installation path is C:

\MSSQL2008. It is recommended that you
install the software in D:\MSSQL2008.
NOTE
The software is installed in a disk with the largest
capacity except disk C, for example, disk D.
Data File Path The default path is D:\data. If you want to

use another path, click Browse to select that
path. To meet the requirements of long-term
operation, change the path to the disk that
has the largest free space according to the
disk partition scheme before the installation.
U2000 software D:\oss
NOTE
l The installation path, including the installation package path and the U2000 installation path, can
contain only letters, digits, and underscores (_). The installation path cannot contain spaces or
brackets; otherwise, the installation fails.
l The software is installed in a disk with the largest capacity except disk C, for example, disk D. All
operations in this guide are performed in disk D.
5.4 Checking Required Software

This section describes the software required to be checked. Ensure that the required software
is on-hand and meets the installation requirements before installing the U2000.
Installation engineers can install the U2000 in either of the following ways:
l Using software packages: Required software packages must be on-hand. Only Huawei
engineers have the permissions to download software packages. If the installation using
software packages is required, contact Huawei engineers to obtain software packages.
l Using DVDs: Required DVDs must be on-hand. The DVDs are delivered along with the
product.
Using Software Packages

Ensure that the ServerGuide boot disk software packages are on-hand before installing the
U2000.
Perform the following operations:

NOTE
If the Read Me_U2000 Version(English) file exists, read the Read Me_U2000 Version(Chinese) file
before downloading the software packages. The Read Me_U2000 Version(Chinese) file is stored in the
same path as software packages.
1. Log in to http://support.huawei.com/enterprise. Search for U2000 and select

iManager U2000 in the search box on the Support tab. Then, click Downloads and
select a desired version.
2. Download required software packages listed in Table 5-9. It is recommended that you
use the download tool (for example, NetAnts). If you use Windows Internet Explorer,
some software packages may be renamed automatically after being downloaded to the
local computer. In this case, you must manually change the software package names to
the same as those on the http://support.huawei.com/enterprise.
3. Use the PGPverify to verify correctness of the software packages. For details, see How
do I Verify Downloaded Software Packages Using the PGPVerify Software.
4. Obtain the 7-zip software. Use the 7-zip tool to decompress the software packages,
obtain the 7-zip tool with the latest version from Web site http://
downloads.sourceforge.net/sevenzip and install the tool. For more information about
software operation, see the software Help or go to the official website of the software for
technical support.
NOTE
In an installation DVD or installation package, version indicates the detailed version number of the
software.
Table 5-9 Software package list
Software Medium Name Description
Database software Microsoft SQL Server It must be available.It is

(personal-edition, installed used to install the database.
on Windows 7 OS):
U2000version_server_sqlser
ver2008_ dbper
_en_win64_x86.zip
NOTE
l The Windows 7 OS only
supports
U2000version_server_sqls
erver2008_dbper_en_win6
4_x86.zip.
l The standard database
erver2008_dbstd_en_win6
4_x86.zip is not supported.
U2000 server software Basic components: It must be available.It is

U2000version_server_nmsb used to install the U2000.
ase_win32_x86.7z
Core components: It must be available.It is

U2000version_server_nmsc used to install the U2000.
ore_win32_x86.7z

Access domain components: It is required only if the

U2000version_server_nmsa U2000 needs to manage
ccess_win32_x86.7z Huawei access equipment.
Huawei access equipment
includes:
l FTTx equipment
l MSAN equipment
l DSLAM equipment
l BITS equipment
IP domain components: It is required only if the

U2000version_server_nmsi U2000 needs to manage
p_win32_x86. 7z Huawei access equipment.
includes:
l ATN Series Equipment
l Routers
l Switches
l Metro service equipment
l Broadband access
equipment
l VoIP gateways
l Firewalls
l Service inspection
gateway
l SVN equipment
l Internet Cache System
Transport domain It is required only if the

component: U2000 needs to manage
U2000version_server_nmstr Huawei access equipment.
ans_win32_x86.7z Huawei access equipment
includes:
l MSTP equipment
l WDM equipment
l RTN equipment
l PTN equipment
NOTE
Software packages for the
transport and IP components
must be available to manage
PTN 6900 and PTN 7900
series NEs.

ESN tool software U2000version_ESN_win32 The ESN tool is required

_x86.zip only when you apply for
the U2000 License before
installing the U2000.
NOTE
The tool is a software package.
It will not be delivered as a
DVD-ROM. After the U2000
is installed, the ESN tool is
available in the U2000
installation path. Therefore, to
apply for the U2000 license
after the U2000 is installed,
use the ESN tool in this path
directly.
Using DVDs
Ensure that the following DVDs are on-hand before installing the U2000 by using DVDs.
Table 5-10 DVD list
Software Medium Name
Database software DVD Microsoft SQL Server (personal-edition,

installed on Windows 7 OS):
U2000version_server_dbper_win64_x86_d
vd2.
U2000 server software DVD U2000version_server_nms_win32_x86_dvd

3
ESN tool software U2000version_ESN_win32_x86.zip.The

ESN tool is required only when you apply
for the U2000 License before installing the
U2000.
NOTE
The tool is a software package. It will not be
delivered as a DVD-ROM. After the U2000 is
installed, the ESN tool is available in the U2000
installation path. Therefore, to apply for the
U2000 license after the U2000 is installed, use
the ESN tool in this path directly.
5.5 Checking Hardware Connections


Procedure
Step 1 Ensure that the power cables and ground wires for all components are tightly connected and in
good contact and that the polarities are properly placed.
Step 2 Ensure that all cables are bundled and free of visible damage.
Step 3 Check hardware connections and network cables according to the hardware connection
diagram.
Step 4 Check the plugs and sockets.

1. Ensure that the latches of cable plugs are locked fast.
2. Ensure that the pins in each socket are complete and in good order. Curved pins may
cause short circuits.
----End
Follow-up Procedure
Remove unnecessary items from the telecommunications room. The workbench must be neat
and the movable floor must be level and clean.
5.6 Applying for a U2000 License

The U2000 license file is used to control the functions and management capabilities of the
U2000. If the license file is unavailable, you cannot log in to the U2000 client, but can log in
to the System Monitor client and the MSuite.
Context
l The license file is not delivered to customers along with a U2000 installation DVD.
Contact Huawei engineers to apply for a license according to the contract number and
the equipment serial number (ESN) of the U2000 server.
l An ESN is a string consisting of 40-digit numerals or letters obtained through encrypted
calculation on the MAC addresses of the U2000 server network interface. The number of
ESNs is the same as the number of MAC addresses on the U2000 server. The ESN for
the USB interface of the IMM is also contained in the echo information. To avoid
applying for a new license due to replacing certain network interface cards (NICs), save
all the ESNs to ensure proper use of the U2000 license.
l A license needs to be bound to an ESN of the server. If an ESN is changed because an
NIC or server is replaced, contact Huawei technical support engineers to apply for a new
U2000 license.
Procedure
Step 1 Obtain the contract number.
Step 2 View ESNs.

NOTE
If the U2000 has been installed, using the ESN tool of the U2000 to view the ESN is recommended. The
directory of ESN tool of the U2000 is %IMAP_ROOT%\platform\bin. In the preceding directories,
%IMAP_ROOT% represents the installation directory of the U2000. Example: D:\oss\server.

Mode 1: View the ESN using the ESN tool of the NMS after installing the U2000.
On Windows, perform the following steps to obtain ESNs:
1. Choose Start > Run.
2. In theRun dialog box, enter cmd. A command line interface (CLI) is displayed.
3. Run the following commands:
> esn
A message similar to the following will be displayed:

ESN0:EBB74B99612CEDC82AD0A59886EC5018CE44DDD4
ESN1:BDA706C825FE0543DC028209778AA66396545412
ESN2:E1B00EEF6947DD95687AA5C608B72ACC532AB2BD
ESN3:F72F9EC08AEE78AA05A42EFD7BFD89F5E03139C4
......
Mode 2: Use the ESN tool to generate ESNs before installing the U2000.
1. You can contact Huawei engineers to obtain ESN tools.
NOTE
Log in to http://support.huawei.com/enterprise. Search for U2000 and select iManager U2000

in the search box on the Software tab and select a desired version. Download the official ESN
tool.
The ESN tool is named U2000version_ESN_win32_x86.zip.
The version indicates the detailed version number of the U2000. Example: V200R016C50SPCxxx.
2. Decompress the ESN tool package, and then double-click the esn.exe file to view ESNs.
A message similar to the following will be displayed:
ESN0:EBB74B99612CEDC82AD0A59886EC5018CE44DDD4
ESN1:BDA706C825FE0543DC028209778AA66396545412
ESN2:E1B00EEF6947DD95687AA5C608B72ACC532AB2BD
ESN3:F72F9EC08AEE78AA05A42EFD7BFD89F5E03139C4
......
Step 3 Send the project contract number and the preceding server ESNs to Huawei engineers or a
local Huawei office.
NOTE
Huawei engineers access http://license.huawei.com according to the information you provide to apply
for a license file. For details about how to apply for a license file, see the iManager U2000 License
Instructions archived athttp://support.huawei.com/enterprise.
Step 4 Huawei engineers send the license file to you after obtaining it.
The license file delivered along with the U2000 is in .dat format.
----End

Commissioning Guide (Windows 7) 6 Powering On a Server
6 Powering On a Server
This section describes how to power on a server and the position of a power button on a
server.
1. Press the power buttons on the external device and monitor of the server.
2. Press the power button on the server.
Highlights the power button on HP Z230 with a blue box.
Figure 6-1 Power button position of the HP Z230 server

Commissioning Guide (Windows 7) 7 Installing the U2000 Server
7 Installing the U2000 Server
About This Chapter
This section describes how to install the U2000 server, including the pre-installation check,
installation process, installation verification, and handling process when the installation fails.
7.1 Preparing Software Packages
The U2000 can be installed by using software packages or installation DVDs. Software
packages and the PGP verification files of the software file in the .asc format must be
uploaded to the server if the software packages are used to install the U2000. If the U2000 is
installed by using DVD-ROMs, skip this operation.
7.2 Pre-installation Check
This section describes the checks that need to be performed before you install the U2000 on
Windows 7.
7.3 Starting the U2000 Installation Program
This section describes how to install U2000 server software.
7.4 Loading a U2000 License
This section describes how to load a U2000 license. Before using a U2000, you must load a
U2000 license.
7.5 Verifying the U2000 Server Installation
After the U2000 server software is installed, verify the installation according to on-site
requirements. Operations including powering on the system and starting the database and
server are optional. For example, if the on-site U2000 server has powered on and the database
has started, skip this step.

7.1 Preparing Software Packages

The U2000 can be installed by using software packages or installation DVDs. Software
packages and the PGP verification files of the software file in the .asc format must be
uploaded to the server if the software packages are used to install the U2000. If the U2000 is
installed by using DVD-ROMs, skip this operation.
Prerequisites
Installation software is on-hand. For details, see Checking Required
SoftwareChecking_Required_Software..
Procedure
Step 1 Step 1 After downloading all of the required software packages and the PGP verification files
to the PC, copy the software packages and the PGP verification files of the software file in
the .asc format to the server, such as D:\oss.
NOTICE
l Do not upload and decompress client installation packages
U2000version_client_win32_x86.7z. Otherwise, the U2000 server software fails to be
installed.
l The installation path, including the installation package path and the U2000 installation
path, can contain only letters, digits, and underscores (_). The installation path cannot
contain spaces or brackets; otherwise, the installation fails.
l Do not save the installation package on disk C. The U2000 installation and operation may
be affected due to hard disk insufficiency. Files that are irrelevant to the installation
package cannot be saved to the directory where the installation package is stored. In
addition to insufficient C if other disk space, you can create a new disk to disk partitions,
see How to Partition Disks on Windows 7 Without Loss.
NOTE
Ensure that all mandatory software packages are uploaded. If a software package is not uploaded, the
U2000 installation may be interrupted because a file is lacked. Selecting the components of the
transport, IP, and access domains is recommended. After the components are selected, you only need not
to download software again when adding domains. In this situation, only the disk space, not the database
space, is occupied. The installation packages to be uploaded are as follows:
l Database software(Mandatory) : U2000version_server_sqlserver2008_dbper_en_win64_x86.zip
l Basic components (Mandatory) : U2000version_server_nmsbase_win32_x86.7z
l Core components (Mandatory) : U2000version_server_nmscore_win32_x86.7z
l Transport domain component (Optional). Prepare this component if managing transport or PTN
equipment: U2000version_server_nmstrans_win32_x86.7z
l IP domain components (Optional). Prepare these components if managing routers, switches, or
security equipment: U2000version_server_nmsip_win32_x86.7z
l Access domain components (Optional). Prepare this component if managing access equipment:
U2000version_server_nmsaccess_win32_x86.7z

Step 2 Use the PGPverify software to verify the uploaded software packages.
NOTE
1. Refer to visit http://support.huawei.com/enterprise/toolNewInfoAction!showDetail?

pid=8221819&show=showServiceDetail&versionid=TV1000000014 to download and decompress the
VerificationTools.zip.
2. Go to the VerificationTools folder that is generated after decompression and obtain different versions of
verification tools for different OSs.
3. KEYS is the public key file.
1. Upload the obtained PGPverify software and public key file KEYS to the C:\ directory
on the server.
2. Run the following commands to verify the installation software packages:
> "C:\PGPVerify.exe" -k "C:\KEYS" -d "D:\oss"
NOTE
– Assume that the signature file and software package are stored in the D:\oss directory, and the
PGPVerify tool and public key file are stored in the C:\ directory.
– To verify a single file, run the C:\PGPVerify.exe" -k "C:\KEYS" -f "C:\V200R016C50.zip.asc".
– For a certain file, if the command output does not contain WARN or FAIL, the signature file is
valid.
– If a version has multiple signature files to be verified, the version is secure only when the
verification results of all files are "PASS". If the verification results contain "WARN" or "FAIL",
the verification is not passed and security risks exist. In that event, re-download the software
package.
Step 3 Step 3 There is no requirement on the decompression sequence of software packages. It is

required that the installation software be decompressed to an NT file system (NTFS) partition.
Right-click a drive and choose Properties from the shortcut menu to check whether the file
system is in the NTFS partition. If the corresponding partition does not use the NTFS,
convert it to an NTFS partition before decompressing the installation package. For details, see
How to Partition Disks on Windows 7 Without Loss..
Step 4 Decompress all installation packages into the same directory.

NOTE
l There is no specific sequence for decompressing all software packages.

l 7-zip is recommended to decompress the software packages, obtain the 7-zip tool with the latest
version from Web site http://downloads.sourceforge.net/sevenzip and install the tool. For more
information about software operation, see the software Help or go to the official website of the
software for technical support. Perform the following operations to use the 7-zip. Choose Start > All
Programs > 7-Zip > 7-Zip File Manager. Select the directory where the installation package is
stored on the address bar. Select all the packages to be decompressed, right-click, and choose 7-Zip
> Extract Here from the shortcut menu.
l During the decompression of all selected software packages, if a message is displayed asking you
whether to overwrite an existing file, click Yes to overwrite the existing file.
----End
7.2 Pre-installation Check

This section describes the checks that need to be performed before you install the U2000 on
Windows 7.

Prerequisites
The U2000 server is powered on.
Procedure
Step 1 Check the OS version.
1. Right-click Computer on the desktop and choose Properties from the shortcut menu.
2. In the dialog box that is displayed, click the View basic information about your computer
tab and verify that the OS version is Windows 7 Professional.
Step 2 Verify that the type of Windows 7 is 64 bit. For details, see ow to Query the Type of a
Windows OS.
Step 3 Check whether the database has been installed. If the SQL Server database has not been
installed, the server software automatically installs the SQL Server database.
1. Choose Start > All Programs.
2. Check whether the Microsoft SQL Server program exists. If the program exists, the
database has been installed.
If the SQL Server database has been installed, check whether the database is installed in
binary mode. For details, see How to Check Whether the SQL Server Database Can
Be Sorted in Binary Mode.
3. 3. Run the following command to check whether the isql command can be executed:
C:\> isql -Usa -SDBSVR
NOTE
– DBSVR specifies the database name.

– Enter the database sa user password as prompted.
– The prompt C:\> varies according to on-site conditions. If the system is logged in to as the
Administrator user, the default prompt isC:\Users\Administrator>. You can run the
cd command to switch the directory. A command example is
C:\Users\Administrator> cd c:\
The command prompt switches to c:\>.
If 1>is displayed, the database can be accessed. Then, you can run the quit command.
Step 4 If the U2000 has been installed before, ensure that the U2000 database file has been deleted.
NOTE
If the database has been installed, uninstall it and then re-install it during the U2000 installation.
Step 5 Checking password policies.

1. Choose Start > All Programs > Administrator Tools > Local Security Policy. The
Local Security Policy displays.
2. Choose Security Settings > Account Policies > Password Policy from the navigation
tree as depicted in the image below.
3. Ensure that the value of Minimum password length is equal to or fewer than 12
characters.
----End

7.3 Starting the U2000 Installation Program

This section describes how to install U2000 server software.
Prerequisites
l The installation software is on-hand. For details about how to obtain the installation
software, see Preparing Software Packages.
l Pre-installation checks have been completed. For details about how to perform pre-
installation checks in Windows 7, see Pre-installation Check.
l At least one NIC has been started.
l If the database has been installed, exit the SQL Server enterprise manager before the
U2000 is installed. This operation prevents U2000 installation failures due to database
errors.
l Ensure that the system time of the U2000 server is set correctly. If the system time is
incorrect, the SSL authentication will fail and the U2000 cannot be installed. The system
time of the U2000 server is of great importance. Changing the system time during U2000
installation is prohibited.
Context
l In the installation process, the installation program needs to start certain services of a
network adapter. Therefore, the network adapter must be connected to the network;
otherwise, the U2000 server cannot be installed.
l If the U2000 software has been installed, the client is also installed on the server.
l If the SQL Server 2008 has not been installed, the U2000 server software will
automatically install the SQL Server 2008.
Procedure
Step 1 Log in to a Windows OS as an OS user with administrator rights.
NOTICE
The name of the directory where the installation packages are stored can contain only letters,
digits, and underscores (_). The directory name cannot contain spaces, brackets, or Chinese
characters; otherwise, the installation fails.
Step 2 Starting U2000 installation, as follows:

NOTE
When you run a .bat file on Windows 7, a user account control dialog box may be displayed. In this
case, click Yes to allow the program to make changes to the computer.
l Mode 1: Installation with a software package:
Double-click the install.bat file in the directory where the installation package is
decompressed. The Set the Installation Environment dialog box will be displayed. If
the database has been installed on the OS, wait 5 to 10 minutes. If no database has been
installed on the OS, wait about 20 to 30 minutes until database installation is complete.

l Mode 2: Installation with a DVD:

– If no database has been installed on the OS.
i. Insert a database installation DVD-ROM and copy the thirdparty folder to a
local directory, such as D:\oss.
ii. 2. Insert a U2000 installation DVD-ROM. Double-click the install.bat file in
the root directory of the installation DVD-ROM.
– − If database has been installed on the OS.
Insert a U2000 installation DVD into the DVD-ROM. Double-click the install.bat
file in the root directory of the installation disk. The Set the Installation
Environment dialog box will be displayed. Wait 5 to 10 minutes.
NOTE
l Double-click the install.bat file. If the PATH length exceeds 560 for a 32-bit Windows 7 OS, the
follow-up operations cannot be performed. In this case, shorten the PATH length.
l After double-click the install.bat file, the Decompressing the pack package. dialog box will be
displayed, ignore it.
Step 3 The Copyright dialog box will be displayed.

NOTE
Read the installation license agreement carefully. If you accept the agreement, click the I accept these
terms option button.
Step 4 Click I accept the terms, and click Next to continue. The Select Language dialog box will
be displayed.
NOTE
If a dialog box is displayed prompting you to select the directory of the installation package, enter the
directory where the installation files were uploaded to the server. For example, /opt/install.
Step 5 Select a language, such as English.

Step 6 Click Next. The Select Installation Type dialog box will be displayed.
NOTE
If Automatically configure the OSS license file during the installation needs to selected, upload the
license file to the server before selecting it.

Step 7 If the License file has been uploaded to the server, click Next. Otherwise, clear the selection
of Automatically configure the OSS license file during the installation, and then click
Next. The Configure Server dialog box will be displayed.
NOTE
The installation path is the directory where the installation package is decompressed, such as d:\oss. The
installation path, including the installation package path and the U2000 installation path, can contain
only letters, digits, and underscores (_). The installation path cannot contain spaces or brackets;
otherwise, the installation fails.
Step 8 Click Next. The Select Domain dialog box will be displayed.

NOTE
This section assumes that the access, IP, and transport packages are uploaded and decompressed. If only
the access package is uploaded and decompressed, the page will display Access domain alone. Select the
domain need to be deployed based on the managed devices. Selecting all the displayed domains is
recommended. To add other domains, upload and decompress the corresponding packages and perform
the installation again. Software packages for the transport and IP components must be selected so as to
manage PTN 6900 and PTN 7900 series NEs.
Step 9 Click Next. The Configure Database dialog box will be displayed.
NOTE
l If the uploaded and decompressed package involves the transport domain, the Version Style dialog
box is displayed.
l Select the time slot mode as required, such as Sequential mode. The Sequential mode, a timeslot
numbering policy recommended by the ITU-T.
The following table lists parameters for the database U2000 user and the database server.
Parameter Settings
Data File Path Specifies the path for storing data files. The default
installation path is D:\data.
NOTICE
l Please click Browse and change the data file save path. To
meet space requirements for long-term running, changing
this path to a path on another partition (especially the
partition with the largest remaining space) by referring to
the disk partition planning before installation is
recommended.
l Ensure that the disk for saving data files is not a compact
disk. If the disk is a compact disk, creating an instance
database will fail.
Server Address The default value is 127.0.0.1.
Server Name The default server name is DBSVR.

Parameter Settings
Server Port The default server port is 1433.
Administrator Name The default database administrator is sa.
Administrator Password Enter a password of the database administrator and

refer to the following operations to verify the password.
l If the database is installed together with the U2000,
enter the default password Changeme_123.
l If the database has been installed before the U2000
installation, and the administrator password meets
the following requirements, enter the database
administrator password.
OSS Database User Password The OSS database user password must meet the
requirements:
l The password contains a minimum of eight
characters and a maximum of 30 characters.
l The password must contain at least four of the
following combinations:
– At least one lower-case letter
– At least one upper-case letter
– At least one digit
– At least one special character ~@#^*-_+[{}]:./?
Other special characters are not supported. Do
not include other special characters, such as ()|
<>&`!$\"%'=;,space in passwords.
l The password must be different from the user name
or the user name in reverse order and cannot contain
the complete user name (case-insensitive).
Set a new password for OSS database user. For
example, Changeme_123.
NOTE
Plan and enter a new password according to the preceding
password rules to ensure system security. Make a note of your
password and keep it in a safe place. Do not share your
password with anyone.
Confirm OSS Database User Confirms the DB user password.

Password
Step 10 Set the installation parameters and click Next. The Preinstallation Check dialog box will be
displayed.

If a check item is abnormal, the Next button is unavailable and the installation fails to be
continued. Perform the following operations to solve the issue.
l If the remaining space of the OS is insufficient, release the space as required. Click
Retry in the Preinstallation Check dialog box until the check item is displayed
normally.
l If the user database is occupied, perform the following operations to solve the issue.
a. Choose Start > All Programs > Microsoft SQL Server 2008 > Configuration
Tools > SQL Server Configuration Manager > SQL Server Services. right-click
SQL Server (MSSQLSERVER) in the right pane, and then choose Stop from the
shortcut menu to stop the database server. Then, choose Start to start the database
server to ensure that no external user accesses the SQL Server database.
b. Click Retry in the Preinstallation Check dialog box until the check item is
displayed normally.
l If one item among the database command, database version number, database
environment variable, and database sorting rule is abnormal, uninstall the database and
then install the U2000 again. For details about the method of uninstalling the database,
see 9.2.5 How to Manually Uninstall the Microsoft SQL Server Database.
l If abnormal prompts to install the database, see software configurationto reinstall the
U2000 server software requirements after checking the operating system version.
Step 11 Click Next. Verify that the installation information is correct.
Step 12 Click Next. A progress bar will be displayed. The time required for the installation depends
on the number of components to be installed and the server configuration. Wait patiently.
The system will display a prompt indicating that installation was successfully completed.
Step 13 After the preceding settings, click Finish to complete U2000 installation. The Are you sure
you want to restart the operating system now? dialog box will be displayed.
Step 14 Click No and see 9.1.1 How to Change the IP Address of the Single-Server System to
Change the IP Address of the Single-Server System.
----End

7.4 Loading a U2000 License

This section describes how to load a U2000 license. Before using a U2000, you must load a
U2000 license.
Prerequisites
l The OS and database must run properly.
l The processes of the U2000 must be properly started.
If U2000 services have not been started, double-click the U2000 Server shortcut icon on
the desktop or run the startnms.bat file in the %IMAP_ROOT%\platform\bin to start
U2000 services manually.
NOTE
In the preceding directories, %IMAP_ROOT% represents the installation directory of the U2000.
Example: D:\oss\server.
l The U2000 license file must be ready. No space is allowed in a license file name. If any
space exists in a license file name, delete it or change it to an underscore (_).
Procedure
Step 1 Log in to the OS of the server as the ossuser user.
NOTE
The password must be changed during the first login to ensure system security. Change the password in
time, regularly update it, and keep it safe. For details, see A.1.7 How to Change the Password of the OS
Administrator.
Step 2 Load theU2000 license file.

NOTE
To make both the U2000 commercial and temporary licenses take effect, use the GUI mode.
Method one: Load the license in the GUI.

1. 1. Copy and paste the authorized license to the server where the U2000 client is installed.
If the U2000 and server are on the same computer, directly copying and pasting the
license file to the %IMAP_ROOT%\etc\conf\license path is prohibited, copy the
license file to another directory.
NOTE
– Do not modify the contents in the license file.

– Check whether a temporary license file exists in the %IMAP_ROOT%\etc\conf\license
folder. If the file exists, create a backup folder and then copy and paste the temporary license
file to it.
2. On the OS desktop, double-click the U2000 Client shortcut icon. The Login dialog box
is displayed.
3. In the Server drop-down list, select the server to be logged in to. Then, set User Name
and Password to the valid values, and click Login. Click Login.

NOTE
– If you have logged in to the System Monitor before, enter the password for logging in to the
System Monitor.
– The initial password of the admin user is Changeme_123 (It is Admin_123 for a U2000 that
comes preinstalled). The password must be changed during the first login to ensure system
security. Keep the password confidential and change it regularly.
4. Update the U2000 license.
– If a message indicating that no license is available is displayed when you log in to
the U2000 client.
i. In the Confirm dialog box, click Yes. The Open dialog box will be displayed.
ii. In the Open dialog box that is displayed, select the new license file and click
Open. The License Comparison Results dialog box will be displayed.
iii. Click OK.
iv. Click Yes and confirm the loaded license.
v. Click OK.
– If U2000 license is loaded before.
i. Choose Help > License Management > License Information from the main
menu (traditional style); alternatively, double-click System Management in
Application Center and choose License Management > License Information
from the main menu (application style).
ii. In the License Information dialog box, click Update License.
iii. Select the new license file and click Open.
iv. Click Next.
v. Select a scenario and perform the associated operations as required:
○ If Incremental is unavailable, click Next.
○ If Incremental is available and only the new U2000 license needs to be
effective, select Full and click Next.
○ If Incremental is available and both the new and in-use U2000 licenses
need to be effective, selectIncremental and click Next. If the in-use
U2000 license has a commercial license and a temporary license, the new
license will replace the license of the same type. For example, if the new
license is a commercial license, the commercial license in the in-use
U2000 license will be replaced.
vi. Click Finish.
vii. Click Yes and confirm the updated license.
viii. Click Yes to close all windows.
ix. Click Yes to log out of the system.
Method two: Use commands to load the license.
1. Copy the authorized license file to the U2000 server. Directly copying and pasting the
license file to the %IMAP_ROOT%\etc\conf\license path is prohibited.
NOTE
– Do not modify the contents in the license file.

– Check whether a temporary license file exists in the %IMAP_ROOT%\etc\conf\license
folder. If the file exists, create a backup folder and then copy and paste the temporary license
file to it.

2. Update the U2000 license.

a. Log in to the OS of the server.
b. Run the following command to update the U2000 license file:
> updateLicense -file License_file_name
NOTE
n the command, License_file_name indicates the combination of an absolute path and a file
name. For example, if the license fine is named license123.dat and stored in d:\, the
command to rename the U2000 license file is > updateLicense -file d:\license123.dat.
If illegible characters are displayed, set the environment variable:
FILEIO_LOCAL_CHARSET=1.
Information similar to the following is displayed:
state product feature item name
old value new value
no change: U2000 COMMON LSW1CAPA01 Client
500 500
no change: U2000 COMMON LSW1CAPA01 Client
1 1
no change: U2000 COMMON LSW1FMCLT01 Alarm
Export 1 1
no change: U2000 COMMON LSW1RENOTI01 Client
1 1
Are you sure to update the license?(Y/N)
c. Enter Y, and then press Enter.
NOTE
After the preceding operations are performed, the license file is automatically loaded to the
%IMAP_ROOT%\etc\conf\license path and renamed.
----End
7.5 Verifying the U2000 Server Installation

After the U2000 server software is installed, verify the installation according to on-site
requirements. Operations including powering on the system and starting the database and
server are optional. For example, if the on-site U2000 server has powered on and the database
7.5.1 Checking Environment Variables

This section describes how to check environment variables after the U2000 server software
has been installed.
Procedure
Step 1 Right-click Computer and choose Properties from the shortcut menu.
Step 2 Click Advanced system setting and click the Advanced tab.
Step 3 Click Environment Variables. In the dialog box that is displayed, the environment variables
shown in the following table must exist in the system environment variable area.

Table 7-1 Environment variables used for installing the U2000 server and client
Environment Variable Name Value
IMAP_CONFIG_PATH D:\oss\server\etc\conf
IMAP_ROOT D:\oss\server
IMAP_JAVA_HOME D:\oss\OSSJRE\jre_win
IMAP_LOCALE UTF-8
OSS_ROOT D:\oss
Path D:\oss\server\3rdTools\lib;D:\oss\server
\3rdTools\python\bin;D:\oss\server\3rdTools
\python\lib;D:\oss\server\3rdTools\bin;D:
\oss\server\platform\bin;D:\oss\server
\platform\lbin;D:\oss\server\platform\lib;D:
\oss\server\cbb\platform\lib;
PYTHONHOME D:\oss\server\3rdTools\python
NOTE
Use the installation of a U2000 in the D:\oss path as an example. If the U2000 server is installed in
another path, the D:\oss path values are different.
The environment variable in the Path folder is the oss core environment variable. If the actual Path
environment variable does not have the preceding information, uninstall and reinstall the U2000. If the
actual Path environment variable has more information than the preceding, ignore the variable setting
because it does not affect the U2000 operation.
----End
7.5.2 Checking the U2000 Version

This section describes how to check the U2000 version.
Procedure
Step 1 Log in to a client.
1. On the OS desktop, double-click the U2000 Client shortcut icon.
2. In the dialog box that is displayed, enter a user name and password.
Step 2 Choose Help > About from the main menu. In the About dialog box, check the U2000
version.
If the U2000 version information contains V200R016C50SPC×××, the installed U2000
version is correct. Otherwise, reinstall the U2000 version.
----End

Commissioning Guide (Windows 7) 8 Commissioning the U2000
8 Commissioning the U2000
About This Chapter
This topic describes how to commission the U2000. Usually, the server delivered by Huawei
has been preinstalled, and you do not need to reinstall the U2000 on the server.You can
directly commission the U2000 and modify the system and U2000 parameters according to
on-site requirements to allow for the normal use of the U2000.If the server has not been
preinstalled by Huawei, install the U2000 and commission the system. To allow the U2000 to
manage the network, you must commission the U2000 before using the U2000 to manage
NEs and configuring services.
NOTE
This chapter applies to commissioning of a newly installed U2000 server, instead of maintenance.
8.1 Commissioning Preparation

This topic describes the preparations for the commissioning of the U2000.
8.2 Performing Commissioning
This topic describes how to commission the U2000 and system parameters. If the system has
been preinstalled, perform U2000 commissioning only.

8.1 Commissioning Preparation

This topic describes the preparations for the commissioning of the U2000.
8.1.1 Obtaining Commissioning Parameters

Planning commissioning parameters is a prerequisite to U2000U2000 commissioning.
Table 8-1 U2000U2000 commissioning parameters
Item Parameter Planning Method Remarks
Access - As some of
the domains
Transport may not be
deployed
during
U2000
installation,
you can use
the domain
deployment
function to
deploy a
Deploy new domain
as needed so
IP that the
U2000 can
manage NEs
in this
domain.
NOTE
If some
domains are
gray, the
domains
have been
deployed.
Access - To disable
the U2000
from
managing
NEs in a
domain,
Undeploy
Transport undeploy
the domain
to improve
system
operation
efficiency.

Do not
select all the
domains
because
there must
be at least
one domain
IP deployed.
NOTE
If some
domains are
gray, the
domains
have not
been
deployed.
Configure CORBA NBI instance For details, see -

section Table 8-2.
Configure SNMP NBI instance
Configure XML NBI instance

XML NBI
Certificate Configure performance Text NBI
instance
XML NBI Certificate
CORBA NBI Certificate
Set Date For details, see l If only

Time Zone section Time and the time
Time Zone zone
Planning in U2000 needs to
Planning Guide. be
l Time zone: Set modified
this parameter to , restart
the local time the
zone, such as operatin
(UTC g system
+08:00)Beijing,C after the
Time zone:
hongqing,Hong modifica
Kong,Urumqi. tion so
that the
l Date Time: Set
time is
this parameter to
automati
the local time.
cally
adjusted
based on
the new
time
zone.

Date Time: l If the

time
zone and
time
both
need to
be
changed,
change
the time
first and
then the
time
zone.
After the
operatin
g system
is
restarted,
the new
time is
automati
cally
adjusted
based on
the new
time
zone.
Set DataBase Old New For details, see -

Password Administrato Passwo Password section U2000
r rd: : Server User
Password Planning
Old New in U2000 Planning
DataBase
Passwo Password Guide.
User
rd: :
MSuite Old New

Administrato Passwo Password
r rd: :
Internal Certificate List - Include two

NMS Certificates:
Certificate l Trust
Certifica
te.
l CRL.
Set SBI Certs folder l Default -

Certificate folder:default.

Certs Path l Default path:D:

\oss\server\etc\ssl
\nemanager
\default.
Set U2100 Identity File Name: - -

Certificate Certificate
PFX Password:
Trust File Name:

Certificate
Set Other SSL Client File Name: - -

Certificate Certificate
PFX Password:
SSL Server File Name:

Certificate
PFX Password:
The
Windows
OS does not
support
configuratio
n of the
U2000
server to
function as
the NTP
For details, see server.
section NTP Service Therefore,
Set NTP NTP server IP address:
Planning in U2000 you must
Planning Guide. configure
both the
U2000
server and
U2000
clients as
NTP clients
to trace
external
clock
sources.
Route -
network
segment 1 For details, see
section Route
Set Route Route
Planning in U2000
network
Planning Guide.
segment 2
...

Route
network
segment N
Set Network IP Address: For details, see After the

section IP Address server IP
Planning for the address is
Single-Server modified,
System (Windows) you can run
in U2000 Planning the
Guide. svc_deploy
-cmd
queryhost
command to
view the
server IP
address. If
the current
server IP
address is
inconsistent
with the
planned IP
address,
modify it.
For details, see -

Set Host section Host Name
Host Name:
Name Planning in U2000
Planning Guide.
Table 8-2 NBI commissioning parameters

Item Parameter Parameter Remarks
Naming service host address: It is recommended -

that all IP addresses
be the application IP
addresses used on
the U2000. If the IP
addresses to be
Configure
changed are in
CORBA NBI
Notify service host address: Configure
Instance
Network, the
commissioning tool
automatically
changes the IP
addresses. Manual
operations are not

required. The IP
addresses for the
notification service
and CORBA agent
are the same. The
naming service may
be deployed in
centralized mode.
You must confirm
the deployment
mode with upper-
layer OSS.
This IP address is
used to interconnect
with the upper-layer
OSS. It can be
different from the
U2000 application
IP address. It must
CORBA Agent Host Address: allow the upper-
layer OSS to use the
IP address and port
number to access the
U2000.
If address translation
exists, host names
can be used.
However, if host
names are used, you
must modify the host
files on the U2000
and upper-layer OSS
server and provide
the mappings
between host names
and IP addresses.
For details, see
U2000 CORBA NBI
User Guide.

Specifies the port

used by the upper-
layer OSS to obtain
the naming service
and to use CORBA
NBIs to access the
U2000. If this port is
shielded on the
firewall between the
upper-layer OSS and
Naming Service Port: U2000, the naming
service may become
unavailable. This
port cannot conflict
with ports used by
other services on the
U2000 server.
Default value: 12001
for the non-SSL
mode and 22001 for
the SSL mode.
Specifies the port

used by CORBA
NBIs to send
notifications to the
upper-layer OSS. If
this port is shielded
on the firewall
between the upper-
layer OSS and
U2000, no
Notify Service Port: notification is
received. This port
cannot conflict with
ports used by other
services on the
U2000 server.
for the non-SSL
mode and 22002 for
the SSL mode.

Specifies the port

used by the CORBA
service. This port
cannot conflict with
ports used by other
CORBA Agent Port: services on the
U2000 server.
for the non-SSL
mode and 22003 for
the SSL mode.
Specifies the
encoding format of
the information
reported by CORBA
NBIs. This
parameter must be
set according to the
on-site situations of
Character Set: the upper-layer OSS.
l UTF-8 If the character set
l GBK used by the upper-
layer OSS is
l ISO8859-1 different from that
used by CORBA
NBIs, garbled
characters may exist
on the upper-layer
OSS.
Default value:
UTF-8.
Set EMS Name: Specifies the

identifier used by the
upper-layer OSS to
distinguish different
sets of U2000. If
multiple sets of
Set U2000 are integrated
EMS into the same upper-
Name layer OSS, this
parameter must be
set based on carriers'
NMS planning.
Default value:
Huawei/U2000.

Specifies the
maximum size of a
log file, ranging
from 1 MB to 20
Maximum Capacity of a Log MB. Keeping the
File default value is
recommended.
Default value: 20
MB.
Specifies the mode

of generating logs.
Log l Log periodically Keeping the default
Output l Log value is
Mode immediately recommended.
Default value: Log
immediately.
l Assertion/
Internal Error Specifies the level of
Log generating logs. This
– Enable parameter is used for
troubleshooting.
– Disable
Keeping the default
l External Error value is
Log recommended.
– Enable l Assertion/
Log
Level – Disable Internal Error
Log: Enable
l I/O Error Log
l External Error
– Enable
Log: Enable
– Disable
l I/O Error Log:
l Runtime Trace Enable
Log
l Runtime Trace
– Enable Log: Disable.
– Disable

Specifies the type of

an NE ID. If the NE
ID type is incorrect,
the upper-layer OSS
fails to be parsed
correctly. Configure
this parameter after
confirming with the
upper-layer OSS.
Only transport NEs
have physical IDs.
l Physical ID: is
expressed in
dotted decimal
notation and
l Logic equals to the NE
al ID ID x 65536 +
NE ID extended ID. For
NE ID l Physi
Type example, if the
cal
ID NE ID is 1 and
the extended ID
is 9 for NE(9-1),
the physical ID is
65545.
l Physical ID: is
expressed in
dotted decimal
notation and is
automatically
assigned by the
U2000 to NEs.
For example,
3145765.
Default value:
Logical ID.

Specifies whether
virtual NEs are
enabled while
Specifie querying NEs, SDH
s paths, routes, and
whether fibers. If the upper-
Virtual the l Enabl
layer OSS uses
NE query e
virtual NEs or
Enablin results l Disab manages devices
g contain le from other vendors,
virtual enable this function.
SDH Otherwise, disable
Nes: this function.
Default value:
Enable.
Specifies whether
CORBA NBIs are
Enablin enabled with alarm
g correlative analysis
l All
Correla so that correlative
tive l Root alarms are reported
Alarm in alarm update
mode.
Default value: All.
Specifies whether
CORBA NBIs report
maintenance alarms
and need to be used
along with the
U2000 engineering
task. By default, all
alarms are reported.
l Disable: specifies
Engine that all alarms are
l Enable
ering queried and
Alarm l Disable reported.
l Enable: specifies
that all alarms
excluding
engineering
alarms are
queried and
reported.
Default value:
Disable.

Specifies the rule for

identifying objects
reported from
CORBA NBIs to the
U2000.
l Internal ID:
specifies that the
ID assigned by
the U2000 is the
unique identifier
of an object.
l Object name:
Object specifies that the
l Internal ID object name
Identifi
er l Object name displayed on the
U2000 is the
unique identifier
of an object. The
object name on
the U2000 client
must be the same
as that on the
U2000 server.
Otherwise, data
conflicts may
occur.
Default value:
Internal ID.
Specifies whether
information about
the fibers and paths
affected by alarms is
reported.
l Enable: specifies
that the names of
Alarm- the paths and
affecte fibers affected by
d l Disable alarms are
Object l Enable queried and
Reporti reported.
ng l Disable: specifies
that the names of
the paths and
fibers affected by
alarms are not
reported.
Default value:
Disable.

Specifies the IP -
address and port
number used by the
U2000 to
interconnect with the
upper-layer OSS.
Ensure that SNMP
NBIs can use the IP
address and port
number to send trap
messages to the
Trap Sending upper-layer OSS.
Address/Port:
Ensure that this port
is not shielded by the
upper-layer OSS and
U2000 and the port
does not conflict
with other ports used
by the services of the
upper-layer OSS.
Default value of
Configure port: 6666.
SNMP
SNMP NBI
Agent Specifies the IP
Instance
address and port
number used by the
U2000 to
interconnect with the
upper-layer OSS.
Ensure that upper-
layer OSS can use
the IP address and
port number to send
trap messages to the
Request Receiving U2000.
Address/Port:
upper-layer OSS and
U2000 and the port
does not conflict
with other ports used
by the services of the
upper-layer OSS.
Default value of
port: 9812.

SNMPv3 applies
user-based security
mechanism, and
Security USM is such a
USM security mechanism.
Model
Currently, only USM
is supported.
Default value: USM.
l With
out
authe Specifies the
nticat security level of
ion SNMPv3. After the
SNMP and security level is
v3 encry configured, you
Parame ption must selected a
ters l With required protocol
authe and set the
nticat password. The
Security security level
ion,
Level configured must be
witho
ut the same as that used
encry for the
ption interconnection with
the upper-layer OSS.
l With
authe Default value:
nticat Without
ion authentication and
and encryption.
encry
ption

Specifies the
authentication
protocol used for
users to access
SNMP NBIs. The
value of this
parameter must be
the same as the
l HMA
authentication
CMD
protocol used for the
Authent 5
interconnection with
ication l HMA the upper-layer OSS.
CSH
The authentication
A
protocol can be set
when the security
level is With
authentication,
without encryption
or With
authentication and
encryption.
Specifies the
protocol used for
encrypting
communication data.
The value of this
parameter must be
the same as the data
encryption protocol
used for the
Data interconnection with
l DES
Encrypt the upper-layer OSS.
ion l AES
The data encryption
protocol must be set
when the security
level is With
authentication and
encryption. The
AES protocol is
recommended
because it provides
better security.

Specifies the IP
address or port
number of the upper-
layer OSS. This
parameter is used to
receive trap
messages sent by
SNMP NBIs.
Trap Destination
Address/Port:
upper-layer OSS and
U2000 and the port
Third- does not conflict
Party with other ports used
NMS by the services of the
upper-layer OSS.
Default value of
port: 6666.
l v1 Specifies the
l v2c protocol version
used by SNMP
l v3 NBIs. SNMPv3 is
SNMP recommended
Version because it is more
secure than SNMPv1
and SNMPv2c.
Default value: v3.

Specifies the
password used for
the upper-layer OSS
to access the U2000
when the SNMPv1
and SNMPv2c use
read and write
community names.
If this parameter is
Read/Write set incorrectly, the
Community upper-layer OSS
cannot obtain U2000
information from
SNMP NBIs.
Default value of
Read Community:
Changeme_123.
Default value of
Write Community:
Changeme_123.
Specifies the user

name and password
used for SNMPv3–
based security
mechanism. If this
parameter is not set,
v3 User Name the upper-layer OSS
cannot obtain U2000
information from
SNMP NBIs.
Default value:
admin.
The authentication
password must be
set when the security
level is set to With
authentication,
without encryption
or With
v3 Authentication authentication and
Password encryption. This
parameter is used for
the upper-layer OSS
to access the U2000
using SNMP NBIs.
Default value:
Changeme_123.

The communication
encryption password
must be set if the
security level is
v3 Privacy With
Password authentication and
encryption.
Default value:
Changeme_123.
l Critic
al Specifies the levels
l Majo of the alarms
Alarm r reported by SNMP
Severity l Mino NBIs.
r The U2000 reports
l Warn all alarms by default.
ing

Specifies the types

of alarms reported
by SNMP NBIs.
l Fault: An alarm
is generated
when a fault
occurs.
l Acknowledged:
After an alarm is
confirmed,
SNMP NBIs
report an
l Fault acknowledged
alarm.
l Ackn
owle l Unacknowledged
dged : After an alarm
Alarm is reversely
Categor l Unac
confirmed,
y know
SNMP NBIs
ledge
report an
d
unacknowledged
l Chan alarm.
ged
l Changed: If
alarm
information is
changed, SNMP
NBIs report a
changed alarm
which contains
the alarm level
change, alarm
influence path,
and alarm root
cause identifier.
Default value: Fault
Specifies the period

of transmitting
heartbeat messages.
When the U2000
Heartb MIB is used, SNMP
eat Heartbeat period NBIs report
settings heartbeat messages
within the specified
period.
Default value: 60s

Specifies whether to
report heartbeat
messages. U2000
l Enabl MIB, instead of
e U2000–T MIB,
l Disab supports the
le reporting of
heartbeat messages.
Default value:
Enable
Specifies the binding

variables contained
in the alarm
information reported
by SNMP NBIs.
This parameter must
Alarm report field
be set according to
the alarm planning
for the upper-layer
OSS. For details, see
U2000 SNMP NBI
User Guide.

Specifies the mode

of reporting trap
messages by SNMP
NBIs. Keeping the
default value is
recommended.
l Trap: After trap
messages are
reported, the
system does not
need to report the
next trap message
until a response
is received from
l Trap
Report the upper-layer
mode l Infor OSS.
m
l Inform: After
trap messages are
reported, the
system starts to
report the next
trap message
until a response
Report is received from
settings the upper-layer
OSS or the
number of
attempts exceeds
the threshold.
Default value: Trap
l Yes Specifies whether

l No trap messages use
Whethe the event type and
r to use level defined by X.
X.733 733.
Default value: No
Specifies the interval

for sending
Trap sending messages in Trap
interval mode.
Default value: 0
Specifies the delay

for sending the next
Inform delay packet in Inform
mode.
Default value: 5

Specifies the number

of allowed re-
Inform retry connection times in
attempts Inform mode upon a
connection failure.
Default value: 3
l UTC
Time
l Local
Time
(with Specifies the format
Report Alarm out of the time used by
time Time time the upper-layer OSS.
format Format zone) Default value: UTC
l Local Time
Time
(with
time
zone)
Set this parameter

Alarm based on the
Encodi l UTF-
Encodin planning for the
ng 8
g upper-layer OSS.
Format l GBK
Format: Default value:
UTF-8
All: specifies that all

alarms, including the
root and correlative
alarms, are queried
Filterin and reported.
g l All Root: specifies that
correlat only root alarms and
ive l Root common alarms that
alarm have no correlative
relationship are
queried and
reported.
Default value: All

Default value:
Disable
Disable: specifies
that all alarms are
Filterin
queried and
g l Enable reported.
enginee
ring l Disable Enable: specifies
alarm that all alarms
except for
engineering alarms
are queried and
reported.
Set this parameter

based on the MIB
file used for the
integration of the
upper-layer OSS.
l U200 T2000-
0 NETMANAGEME
MIB MIB NT-MIB.mib:
MIB
Frame l U200 U2000-T MIB HW-
0-T IMAPV1NORTHBO
MIB UND-TRAP-
MIB.mib or HW-
IMAPV2NORTHBO
UND-TRAP-
MIB.mib: U2000
MIB
Whethe l Enabl Specifies whether to

r to e record logs.
Others
record l Disab Default value:
logs le Disable

Specifies the size of

the cache for real-
time alarms. Every
upper-layer OSS
user is assigned with
an independent
cache.
Real-time alarm
If the alarm
cache size
generation rate is
larger than the alarm
report rate, NBI
interfaces save alarm
information to the
cache.
Specifies whether to -
use the common or
SSL mode. The
default port used
varies according to
the mode. The SSL
Use SSL mode is
recommended
because it enables
better security.
Default value: Select
the Use SSL check
box.
Configure Specifies the

XML NBI JMS middleware type of
Instance teh JMS service.
activeM
Type Currently, the
Q
activeMQ
middleware is
supported.
Specifies the IP
address of the JMS
service. Set this
parameter to the IP
address of the
IP Address
U2000 server.
Ensure that the
upper-level OSS can
use this IP address to
access the U2000.

Specifics the number

of the port used by
the JMS
middleware. This
Port parameter is usedfor
sending notifications
to the upper-layer
OSS.
Specifies the IP
address of the Web
service. Set this
parameter to the IP
address of the
IP Address
U2000 server.
Ensure that the
upper-level OSS can
use this IP address to
access the U2000.
Specifies the number

of the port used by
XML NBIs. The
upper-layer OSS
HTTPS Port uses this port to
obtain Web service
Web data from XML
Service NBIs.
Default value: 9997
When the upper-

layer OSS needs to
use AFB-based
interface (such as
getInventory), the
JMS service needs to
be registered. If only
Register JMS the synchronization
service mode (such as SIT
or SRR) is used, do
not register the JMS
service in order to
save system
resources.
Default value: Yes.

Specifies the
protocol type of the
Web service. This
parameter is set
based on the
HTTP l Http protocol selected by
Protocol l Https the upper-layer OSS.
HTTPS is
recommended
because it is more
secure than HTTP.
Default value: Https
Specifies the level of

l Debug the logs generated
Product by XML NBIs. This
log l Warn parameter is used for
level l Error troubleshooting.
Default value: Warn
All: specifies that all

alarms, including the
root and correlative
alarms, are queried
Filterin and reported.
g l All Root: specifies that
correlat only root alarms and
ive l Root common alarms that
alarm have no correlative
relationship are
queried and
reported.
Default value: All
Encoding format: Set this parameter

l UTF-8 based on the
planning for the
l GBK upper-layer OSS.
Default value:
UTF-8

These parameters are

used to distinguish
different sets of
U2000 when they
are managed by the
Manag same upper-layer
ement Domain Name: OSS. Set the
domain parameters
according to carriers'
NMS planning.
Default value:
Huawei/U2000
When XML NBIs

are used to query
WDM routes, WDM
routes are returned
based on a specified
order, which is
convenient for the
analysis of the
upper-layer OSS.
WDM l None None: specifies that
route WDM routes are
l Forward
return sent randomly.
order l Backward
Forward: specifies
that WDM routes are
sent from the source
to the sink.
Backward: specifies
that WDM routes are
sent from the sink to
the source.
Default value: None

l Filter Out Alarm

Notification
– Enable
– Disable
l Filter Out
Inventory
Notification
– Enable
– Disable
l Filter Out filter out the
Filter Protection notifications for
notifica Notification these themes.
tion – Enable Default value: The
theme – Disable notification for all
these themes are
l Filter Out
filtered out.
Performance
Notification
– Enable
– Disable
l Filter Out
Maintenance
Notification
– Enable
– Disable

After this parameter

is set to Enable,
only users that have
related operation
rights can invoke the
XML NBI.
l Installation: By
default, this
parameter is set
to Enable.
l Version upgrade:
It is
recommended
that the value of
Authen l Enable this parameter be
tication retained the same
Switch l Disable
before and after
the upgrade.
Perform
automatic
upgrades with the
NMS upgrade
tool if possible. If
the manual
upgrade mode is
used, change this
parameter
manually to keep
consistency.
Default value:
Enable
Specifies whether
XML NBIs report
maintenance alarms
Filterin and the alarm
g reporting works
l Internal ID
enginee along with U2000
ring l Object name engineering tasks.
alarm By default, all
alarms are reported.
Default value:
Disable

Specifies the rule for

identifying objects.
l Internal ID:
specifies that the
IDs assigned by
the U2000
uniquely identify
objects.
Object l Object name:
l Enable specifies that the
identifi
er l Disable U2000 client
names are used to
identify objects.
The U2000 client
names must be
unique in order to
prevent data
conflicts.
Default value:
Internal ID
report the names of
the paths or services
affected by the
alarms.
l Enable: specifies
that if an alarm
affects paths or
fibers, the names
of the affected
Alarm paths and the
and l Enable fibers are
service contained in the
associa l Disable
alarm
tion information
during alarm
query and report.
l Disable: specifies
that the names of
the affected paths
and fibers are not
reported.
Default value:
Disable

Set this parameter to -

the collection period
for performance
l Single-period data. The U2000 can
l Multi-period be used to export
performance data
generated during one
or more periods.
Specifies the delay

mode for exporting
files. The value of
this parameter for
different device
types varies. If the
value of this
parameter is the
Duratio l Auto same for different
n l Manu device types, the
Settings al performance data
fail fails to be
Perfor exported. The Auto
Configure mance mode is
Performance data recommended. For
Text NBI exporti details, see U2000
Instance ng Performance Text
settings NBI User Guide.
Default value: Auto

l 5 of collecting
l 10 performance data
Collecti
l 15 using performance
on
text NBIs. The
Period l 30 performance data
(min)
l 60 can be exported
l 1440 based on the
collection period.
Specifies the interval

l 5 for generating
l 10 performance text
Data
l 15 files. This parameter
Export
can be customized. It
Period l 30 is recommended to
(min)
l 60 set this parameter to
l 1440 a value the same as
the collection period.

Specifies the
difference between
the time
performance data is
generated on NEs
and the time the
performance text file
is exported.
Data Export You must configure
Duration (min) Data Export
Duration (min)
according to on-site
requirements when
Duration Settings is
set to Manual. For
details, see U2000
Performance Text
NBI User Guide.
Specifies the time

the startup file is
exported for the first
time. This parameter
cannot be set to a
value ranging from
23:00:00 to
01:00:00. If the
value of this
Export Start Time parameter ranges
from 23:00:00 to
01:00:00, a data
error occurs during
DTS switching.
yyyy-mm-dd
hh:mm:ss
For example,
2009-09-01 01:00:00

Specifies the
performance
indicators that the
performance text file
can export.
Performance
indicators can be
configured in two
modes: template—
based or manual
configuration
l Template-based
configuration:
Before
commissioning,
you must confirm
the performance
indicators to be
monitored and
configure a
performance
indicator
template and use
the following
Indicator operations to
configure the
performance
indicators. For
details, see
U2000
Performance Text
NBI User Guide.
Full Import:
specifies that
performance
indicators are
fully imported to
the performance
indicator
template to
overwrite the
original indicator
template.
Incremental
Import: specifies
that performance
indicators are
incrementally
imported to the
performance

indicator
template and only
new indicators
are added to the
original indicator
template. Export:
The performance
indicator
template is
exported, backed
up, or provided to
another U2000
server.
l Manual
configuration:
Before
commissioning,
you must confirm
the performance
indicators to be
monitored and
print the
performance
data. Modify: In
the dialog box
that is displayed,
configure the
indicators as
required.
Set this parameter to

the directory where
□Export
File the performance data
ing to Exportin
exporti file is saved. The
the g
ng upper-layer OSS
local directory
settings accesses this
server
directory to obtain
performance data.

l FTP The U2000 uploads

Mode performance data to
: the FTP server. You
–F must create an FTP
T user and configure
P the FTP user
password on the
–S U2000.
F
T Using SFTP is
P recommended
because SFTP
l FTP/ provides higher
SFTP security than FTP.
Serve
□Export r IP:
ing to a l FTP/
remote SFTP
FTP Port:
server l FTP/
SFTP
User:
l FTP/
SFTP
Pass
word:
l FTP/
SFTP
Direc
tory:
l SFTP
Certif
icate:
Specifies the
Maximum number maximum number of
of backup product output logs.
logs
Log Default value: 20
file
settings Specifies the
Maximum size of maximum size of
product logs output logs.
Default value: 20

l Debu Specifies the lowest

g level of generating
Product l Info logs. The logs with
log the level lower than
l Warn the value cannot be
level
l Error recorded.
Default value: Info
Encoding format: Set this parameter

l UTF-8 based on the
planning for the
l GBK upper-layer OSS.
Default value:
UTF-8
Specifies the time

Time format encoding for
format the performance text
for file NBI file.
export Default value: UTC
time
Specifies the
maximum number of
records in a file.
If the value exceeds
the threshold, the
Maximum number
extra records are
of records in a file
stored in another file
whose serial number
is increased by 1.
Default value:
Others 100000

during which files
can be stored on the
local server. The
Number of days to system automatically
save exported files deletes the files
generated after the
period elapses.
Default value: 3
days

Specifies the start

time for deleting
files in a scheduled
task. The value of
Start time for file this parameter is the
deletion same as the server
time.
Format: yyyy-mm—
dd hh:mm:ss
XML NBI Identity Certificate Type Default certificate -

Certificate Certific Type: P12.
ate File Name
For details, see
section Security
Trust File Name
Certificate
Certific
Description.
ate
CRL File Name
CORBA NBI Identity Certificate Type Default certificate -

Certificate Certific Type: P1.
ate For details, see
section SSL
Principle and
Configuration.
8.1.2 Checking Hardware Connections

Procedure
Step 1 Ensure that the power cables and ground wires for all components are tightly connected and in
good contact and that the polarities are properly placed.
Step 2 Ensure that all cables are bundled and free of visible damage.
Step 3 Check hardware connections and network cables according to the hardware connection
diagram.
Step 4 Check the plugs and sockets.

1. Ensure that the latches of cable plugs are locked fast.
2. Ensure that the pins in each socket are complete and in good order. Curved pins may
cause short circuits.
----End

Follow-up Procedure
Remove unnecessary items from the telecommunications room. The workbench must be neat
and the movable floor must be level and clean.
8.2 Performing Commissioning

This topic describes how to commission the U2000 and system parameters. If the system has
been preinstalled, perform U2000 commissioning only.
8.2.1 Powering On a Server

This section describes how to power on a server and the position of a power button on a
server.
1. Press the power buttons on the external device and monitor of the server.
2. Press the power button on the server.
Highlights the power button on HP Z230 with a blue box.
Figure 8-1 Power button position of the HP Z230 server
8.2.2 Configuring System Commissioning Parameters

After the U2000 is installed initially, you must use the commissioning tool to adjust system
parameters, such as the IP address and host name. You do not need to modify parameters that
do not require adjustment.

Prerequisites
NOTICE
Manually changing the system IP address causes a failure to use the commissioning tool.
Therefore, configure the system IP address through the commissioning tool.
l The U2000 has been installed.

l Commissioning parameters have been planned and a commissioning parameter table is
obtained. For details, see Obtaining Commissioning Parameters.
l The server has been powered on. For details, see 6 Powering On a Server.
Context
The commissioning tool is used only after the initial installation of the U2000 is complete. Do
not use the commissioning tool after the U2000 has running for a period of time. If system
parameters need to be commissioned, see section MSuite in the U2000 Administrator Guide.
Procedure
Step 1 Log in to the OS as a user with administrator rights.
Step 2 Ensure that the U2000 is not running.

1. Choose Start > Run. The Run window will be displayed.
2. Enter cmd and click OK.
3. In the CLI, run the daem_ps command to check whether the U2000 process is stopped.
– If no command output is displayed, the U2000 process has stopped.
– If information similar to the following is displayed, the U2000 process is not
stopped. In the CLI, run the D:\oss\server\platform\bin\stopnms.bat command to
stop the U2000 process.
imapmrb.exe 30616 RDP-Tcp#1 3
19,252 K
imapeventmgr.exe 4392 RDP-Tcp#1 3
19,812 K
imapsysd.exe 27224 RDP-Tcp#1 3
39,720 K
imapwatchdog.exe 36812 RDP-Tcp#1 3
14,216 K
ResourceMonitor.exe 29472 RDP-Tcp#1 3
25,024 K
imap_sysmonitor.exe 8368 RDP-Tcp#1 3
36,628 K
python.exe 33732 RDP-Tcp#1 3
21,216 K
httpd.exe 14920 RDP-Tcp#1 3
11,140 K
java.exe 21572 RDP-Tcp#1 3
92,424 K
16,476 K

NOTE
n If information similar to the following is displayed, the U2000 process is not stopped.
Switch to the administrator and run the D:\oss\server\platform\bin\stopnms.bat command
to stop the U2000 process.
imapmrb.exe 11116 Services
0 30,392 K
imapeventmgr.exe 11164 Services
0 21,404 K
imapsysd.exe 10236 Services
0 42,116 K
imapwatchdog.exe 8584 Services
0 11,676 K
ResourceMonitor.exe 26056 Services
0 28,184 K
imap_sysmonitor.exe 13168 Services
0 39,632 K
n D:\oss specifies the installation path of the U2000.

n Stopping the U2000U2000 process takes about 3 minutes.
Step 3 Perform the following operations to ensure that the SQL Server database has been started.
Choose Start > All Programs > Microsoft SQL Server 2008 > Configuration Tools > SQL
Server Configuration Manager, choose SQL Server Services from the navigation tree,
right-click SQL Server (MSSQLSERVER) in the right pane, check whether the shortcut
menu option Start is grayed out.
l If Start is grayed out, the SQL Server database is started.

l If Start is not grayed out, the SQL Server database is stopped. Right-click SQL Server
(MSSQLSERVER) and choose Start from the shortcut menu.
Step 4 Ensure that the MSuite server has been started.
In the Windows Task Manager dialog box, check whether msdaemon.exe and msserver.exe
are listed.
l If the two processes are listed, the MSuite server has started.
l If the two processes are not listed, the MSuite server has not started. Navigate to the D:
\oss\engr\engineering directory and double-click startserver.bat to start the MSuite
server.
Step 5 Perform the following operations to log in to the MSuite client:

1. On a computer where the MSuite client is installed, double-click the U2000 NMS
Maintenance Suite shortcut icon on the desktop and then wait about one minute. The
Login dialog box is displayed.
2. Set the login parameters.
– IP Address: Use the default value 127.0.0.1.
– Port: Use the default value 12212.
– User Name: Use the default value admin.
– Password: The initial password of the admin user is Changeme_123. The
password must be changed during the first login to ensure system security. Keep the
password confidential and change it regularly.
3. Click Login.

NOTE
– When you log in to the MSuite client, a progress bar is displayed showing the progress of
Refresh Deployment Information. Wait until the operation is complete.
– The MSuite works in single-user mode. Specifically, only one MSuite client can log in to the
MSuite at one time.
Step 6 Perform the following operations to implement system commissioning:

1. Choose Tools > Commissioning Tool from the MSuite client main menu to access the
Information dialog box.
2. Read the information carefully and click Start to access the system commissioning
window.
Step 7 Configure the commissioning items based on the planned commissioning parameter table. For
details about the commissioning parameters, see Obtaining Commissioning Parameters.
NOTICE
l If a message asking you to refer to the associated section in the installation guide is
displayed during system commissioning, the system needs to be manually commissioned.
l After the host name is configured, you cannot come back to modify other configurations.
Otherwise, the commissioning may be abnormal. Configure the host name after other
commission items are configured.
Step 8 After system commissioning parameters are set, restart the system to make the modifications
take effect.
----End
8.2.3 Commissioning U2000 Parameters

This topic describes how to commission the U2000 parameters on a U2000 Client after the
U2000 is installed.
Prerequisites
l If the delivered server has been preinstalled, ensure that system commissioning is
performed. For details, see 8.2.2 Configuring System Commissioning Parameters.
l If the delivered server has not been preinstalled, ensure that the U2000 is installed. For
details, see 7 Installing the U2000 Server.
l Ensure that the U2000 license has been loaded. For details, see 7.4 Loading a U2000
License.
NOTE
Using the resolution 1024 x 768 or higher is recommended. If the resolution is not used, the U2000
client GUI may be incomplete.
Context
The U2000 commissioning parameters cover communication security, U2000 user security
policy, communication between the U2000 and NEs, alarm function, and common U2000
configurations.

Procedure
Step 1 Log in to the OS as a user with ossuser rights.
Step 2 Perform the following operations to ensure that the U2000 server processes have been started.
3. In the CLI, run the daem_ps command to check whether the U2000U2000 process is
started.
– If information similar to the following is displayed, the U2000U2000 process has
started.
imapmrb.exe 30616 RDP-Tcp#1 3
19,252 K
imapeventmgr.exe 4392 RDP-Tcp#1 3
19,812 K
imapsysd.exe 27224 RDP-Tcp#1 3
39,720 K
imapwatchdog.exe 36812 RDP-Tcp#1 3
14,216 K
ResourceMonitor.exe 29472 RDP-Tcp#1 3
25,024 K
imap_sysmonitor.exe 8368 RDP-Tcp#1 3
36,628 K
python.exe 33732 RDP-Tcp#1 3
21,216 K
11,140 K
java.exe 21572 RDP-Tcp#1 3
92,424 K
16,476 K
NOTE
If information similar to the following is displayed, the U2000 process also has started.
imapmrb.exe 11116 Services 0
30,392 K
imapeventmgr.exe 11164 Services 0
21,404 K
imapsysd.exe 10236 Services 0
42,116 K
imapwatchdog.exe 8584 Services 0
11,676 K
ResourceMonitor.exe 26056 Services 0
28,184 K
imap_sysmonitor.exe 13168 Services 0
39,632 K
– If no command output is displayed, the U2000U2000 process is not started. You can
run the D:\oss\server\platform\bin\startnms.bat command in the CLI to start the
U2000U2000 process.
If information similar to the following is displayed, the database has to be started.
For details, see Starting the Database. Then, execute the startnms.bat file to start
the U2000U2000 process.
Service MSSQLSERVER does not running,please start it first.
NOTE
n D:\oss specifies the installation path of the U2000.

n Starting the U2000U2000 process takes about 3 minutes.
Step 3 Perform the following operations to log in to the U2000 Client.

1. Double-click U2000 Client on the desktop to access the Login dialog box.
2. Choose the server on which the U2000 resides from the Server drop-down list.
3. Set User Name and Password and click Login.
NOTE
– The user name is admin, the same as the administrator name.

– The initial password of the admin user is Changeme_123.The password must be changed
during the first login to ensure system security. Keep the password confidential and change it
regularly.
– If a failure message is displayed during the login to the client, see Failure to Log In to the
U2000 Server from a U2000 Client to address the problem.
Step 4 Perform the following operations to change the display style to the traditional style for the
client:
1. Choose File > Preferences from the U2000 Client main menu.
2. Choose Client Display Style from the navigation tree on the Preferences page.
3. Select Traditional style and click OK.
4. Re-log in to the U2000 client.
Step 5 Choose Administration > NMS Commissioning Wizard from the U2000 Client main
menu.
Step 6 Commission U2000 parameters as prompted.
----End
Result
After U2000 parameters are commissioned, the U2000 and NEs can communicate with each
other properly, and the U2000 works properly.

Commissioning Guide (Windows 7) 9 FAQ
9 FAQ
About This Chapter
This section provides answers to the most frequent questions concerning the installation.
9.1 Windows OS
This section provides answers to FAQs about clients installed on Windows OS.
9.2 SQL Server Database
This section describes the FAQs about the SQL Server database.
9.3 U2000 System
This section covers FAQs about the U2000 system.
9.4 Handling the Failure to Install the U2000 Server Software
If the U2000 fails to be installed, you need to handle the problem and re-install the U2000.
This section describes how to handle the failure to install the U2000.

9.1 Windows OS
This section provides answers to FAQs about clients installed on Windows OS.
9.1.1 How to Change the IP Address of the Single-Server System
Question
How do I change the IP address of the single-server system
Answer
NOTE
Changing an IP address includes the following major steps:

1. Shut down the NMS server and all NMS clients, and ensure that the database is running.
2. Shut down the U2000 MSuite server.
3. Change the IP address of the U2000 server.
4. Start the U2000 MSuite server.
5. Log in to the U2000 MSuite client and synchronize update the network configuration files. If the
network configuration files are not synchronized update, the U2000 fails to start properly.
6. Restart the OS.
NOTICE
Using virtual network interfaces is prohibited.
Step 1 Shut down the NMS server and all NMS clients.
In the directory of the NMS software after the installation, for example, the D:\oss\server
\platform\bin directory, run the stopnms.bat file or run the D:\oss\server\platform\bin
\stopnms.bat command to end the NMS processes.
NOTE
Ensure that the database is started, do as follows:

1. Choose Start > All Programs > Microsoft SQL Server 2008 > Configuration Tools > SQL
Server Configuration Manager > SQL Server Services.
2. Right-click SQL Server (MSSQLSERVER) and choose Start to start the database. If the database
Step 2 End the server process of the MSuite.
In the D:\oss\engr\engineering directory, double-click the stopserver.bat file to end the

server process of the MSuite.
Step 3 Perform the following operations to change the IP address of the server:
1. Choose Start > Control Panel > Network and Internet > Network and Sharing
Center > Change adapter settings to access the Network Connections window.
2. In the Network and Sharing Center dialog box, click Change adapter settings.

3. In the Network Connections dialog box that is displayed, right-click the network
connection to be configured and choose Properties from the shortcut menu.
4. In the Local Area Connection Properties dialog box, click Internet Protocol Version
4 (TCP/IPv4) and then Properties.
5. In the Internet Protocol Version 4 (TCP/IPv4) Properties dialog box that is displayed,
enter the new IP address, subnet mask, and default gateway address, and perform the
related modification. Click OK.
6. Access the D:\oss\server\platform\conf directory. Change the values of
LOCALHOST_FIXSERVERNAME, MASTERHOST_FLOATSERVERNAME,
and MASTERHOST_FIXSERVERNAME in the watchdog.ini file from the default
value 127.0.0.1 to local IP address.
7. Access the D:\oss\server\etc\conf\ directory. Change the values of fixedServerName
and floatServerName in the sysconfigure.xml file from the default value 127.0.0.1 to
local IP address.
Step 4 Start the server process of the MSuite.
In the D:\oss\engr\engineering directory, double-click the startserver.bat file to start the
server process of the MSuite.
Step 5 Log in to the MSuite client.
1. On the computer where the MSuite client is installed, double-click the U2000 NMS
Maintenance Suite shortcut icon on the desktop. Wait about one minute. The Login
dialog box is displayed.
NOTICE
The Login dialog box that is displayed after the Network Management System
Maintenance Suite is logged out of cannot be used for login. Otherwise, network
configuration synchronization fails.
2. Set the related login parameters and click OK. The Management System Maintenance
Suite window is displayed.
– IP Address: Indicates the system IP address of the computer where the MSuite
server is installed.
– Port No.: The default port number is 12212. You do not need to change the default
value during login.
– User Name and Password: The default user name of the MSuite is admin and the
default password is Changeme_123. If the password has not been changed, for
system security, modify the default password and remember the new password. For
details, see Changing the Password of the MSuite.
NOTE
A dialog box may be displayed during the process of logging in to the MSuite client. Click
OK according to the prompt.
Step 6 On the Server tab page, right-click the server to be configured and choose Synchronize
Network Configuration from the shortcut menu. Click OK.
Step 7 Manually shut down the MSuite server and the database. Then, restart the OS.
1. Shut down the MSuite server. For details, see Step 2.

2. Shut down the database. For details, see How to Shut Down the SQL Server Database.
3. Restart the OS.
– If NBIs instances are deployed and the xFTP monitor is configured before the host
name and IP address are changed, you must re-configure NBIs on the MSuite client
and re-configure the xFTP monitor on the U2000 client after changing the IP
address and host name.
– The changed IP address will be used for re-configure an NBI. For details, see the
related NBI user guide. For details about how to configure the xFTP monitor, see
the U2000 Help.
----End
9.1.2 Changing the Password of the MSuite

This section describes how to change the password of the MSuite. To ensure the security of
the U2000, change the password of the MSuite immediately and record the password after
installing the U2000 server.
Context
In the high availability system, you only need to log in to the MSuite server on the primary
site and change the password of the MSuite. The password of the MSuite on the secondary
site is then automatically changed.
Procedure
Step 1 Log in to the MSuite client. For details, see Logging In to the MSuite Client.
Step 2 On the MSuite client, choose System > Change Passwordfrom the main menu. The Change
Password dialog box is displayed.
Step 3 Click OK. The Change Password dialog box is displayed.
Step 4 Enter the old password and new password.
NOTE
The initial password is Changeme_123.

The rules for modifying a password are as follows:
l The password contains a minimum of 8 characters and a maximum of 30 characters.
l The password must contain four of the following combinations:
– At least one lower-case letter
– At least one upper-case letter
– At least one digit
– At least one special character ~!@#$%^&*()-_=+\|[{}];:"',<.>/?
l The password cannot be the same as the user name written in either the forward or backward
format.
Step 5 Click OK. The password is changed.
----End
9.1.3 Logging In to the MSuite Client

This section describes how to log in to the MSuite client.

Prerequisites
l The MSuite server must be started.
l Port 12212 on the MSuite server is enabled.
l The MSuite client and the server communicate with each other properly.
Context
If you consecutively enter incorrect passwords three times, the IP address of the PC on which
the MSuite client is installed will be locked by the U2000. The U2000 will unlock this IP
address 5 minutes later.
Procedure
Step 1 On a computer where the MSuite client is installed, double-click the U2000 NMS
Maintenance Suite shortcut icon on the desktop and then wait about one minute. The Login
dialog box is displayed.
NOTE
l If a dialog box showing The client and server versions are different is displayed, upgrade the
client using the CAU. The method of upgrading the U2000 client by using the CAU is as follow:
– Install the U2000 client software in network mode: Enter https://server_IP_address/cau/
(more secure, recommended) or http://server_IP_address/cau/ in the address box of the
Internet Explorer, and press Enter to access the Web installation page. If you upgrade the
U2000 client software using the CAU, the MSuite client is also upgraded. For details, see
U2000 Client Software Installation Guide.
– Log in to a U2000 client, if the The client and server versions are different message is
displayed, click Yes. Follow the upgrade wizard to upgrade the client.
l Upgrading the U2000 client will also upgrade the U2000 NMS Maintenance Suite client.
Step 2 Set the login parameters.

l IP Address:
– To log in to the local MSuite server, use the default IP address 127.0.0.1.
– To log in to the remote MSuite server, enter the IP address of the computer where
the MSuite server is installed. If multiple IP addresses are configured for the
computer, use the NMS application IP address.
NOTE
The Login dialog box of the MSuite client has the function to keep the login list. Selecting
an IP address from the IP Address drop-down list is recommended. If the desired IP address
is not displayed in the drop-down list, enter an IP address.
l Port: The default port ID is 12212. There is no need to change the default value during
login but ensure that the port is not occupied.
l User Name: The default user name is admin.
l Password: The initial password of the admin user is Changeme_123 (It is Admin_123
for a U2000 that comes preinstalled). If you have changed the password, enter the
current password. The password must be changed during the first login to ensure system
security. Keep the password confidential and change it regularly.
Step 3 Click Login.

NOTE
l When you log in to the MSuite client, a progress bar is displayed showing the progress of Refresh
Deployment Information. Wait until the operation is complete.
l The MSuite works in single-user mode. Specifically, only one MSuite client can log in to the MSuite
at one time.
l Change the initial password upon your first login to ensure U2000 system security and remember the
new password. For details, see Changing the Password of the MSuite.
----End
Follow-up Procedure
If a dialog box is displayed during the login, indicating that network configuration
information is inconsistent and re-synchronization is required after login, read through the
message to learn the server that needs to be synchronized. Then, update the network
configuration, for details, see Updating Network Configurations.
9.1.4 Updating Network Configurations

When a network configuration of the NMS server changes, you need to update the network
configuration so that the IP addresses and host names of the MSuite and server are
synchronized. Otherwise, the system displays a failure message during the login to the MSuite
client.
Prerequisites
l Ensure that no client logins on the NMS server.
l Ensure that the NMS server programs are already stopped.
l Ensure that the database is running.
l Ensure that the network port for which a system IP address has been configured during
factory installation is connected to the network. Otherwise, the network configurations
will fail to be updated and the U2000 will fail to be started.
Procedure
Step 1 Log in to the MSuite client. For details, see Logging In to the MSuite Client.
Step 2 On the MSuite client, click the Server tab.
Step 3 Right-click the server whose network configuration needs to be updated and choose
Synchronize Configuration from the shortcut menu. A dialog box is displayed for you to
confirm the operation.
Step 4 Click OK. A progress bar showing the Synchronize progress is displayed.
NOTE
If a message is displayed indicating that you confirm no client logins on the NMS server and stop the
NMS service manually, click OK to stop the configuration synchronize. Synchronize network
configurations after the prerequisites are met.
Step 5 When the system displays Synchronize network configuration success, click OK.
----End

9.1.5 How to Add a Static Route
Question
If the network connection is unstable, intermittently disconnected, or unreachable, the static
route may be not added. How do I add a static route?
NOTICE
If there are multiple network interfaces and their IP addresses are within different network
segments, the static route can be configured on only one of these network interfaces. To
prevent the failure of one network interface from causing the disconnection of the entire
network, the static route needs to be added on other network interfaces.
Answer
Step 1 Run the following command on the command prompt window to view the existing routes:
C:\>route print
Step 2 Run the following command to add a route:

C:\>route -p addnetwork_IP_address masknetmask gateway_IP_address
NOTE
Set the following parameters:

l network_IP_address: An IP address on the network segment of the computer connected to the
U2000 server.
l netmask: subnet mask of the network segment on which the computer connected to the U2000 server
is located.
l gateway_IP_address: network management IP address for the network on which the U2000 server is
located.
To delete a route, run the following command:
C:\>route -p deletenetwork_IP_address masknetmask gateway_IP_address
----End
9.1.6 How to Convert the File System Type to NTFS
Question
How do I convert the file system type to NTFS?
Answer
Step 1 Choose Start > Run. The Run window will be displayed.
Step 2 Enter cmd and click OK.
Step 3 Enter convert Drive letter where the installation package is decompressed: /FS:NTFS. For
example, enter convert F: /FS:NTFS if you need to decompress the installation package into
disk F. Enter the corresponding information at the prompt.

Step 4 Restart the OS.
----End
9.1.7 How to Change the Password of the OS Administrator

Question
How to change the password of the OS administrator?
Answer
Step 1 Log in to the OS as the administrator user.
Step 2 Ensure that the SQL Server database is started.

NOTE
l If the database is not started, manually start it. Otherwise, login to the database fails after the
password is changed.
l If the password of the administrator is changed when the SQL Server database is not started, login
to the database fails. In this case, you need to change the password to the original one, start the SQL
Server database, and then change the password of the administrator. To ensure the security of the
U2000, passwords must be complex enough. For example, a password must contain eight or more
characters of two types. The allowed characters are digits, letters, and special characters. Remember
to change passwords regularly.
Step 3 Press Ctrl+Alt+Delete to lock the current interface.
Step 4 In the dialog box that is displayed, click Change Password.
Step 5 In the dialog box that is displayed, enter the old password and the new password, and confirm
the new password.
Step 6 Click OK.
----End
9.1.8 How to Configure the Remote Login to the Windows OS

Question
How to configure the remote login to the Windows OS?
Answer
Step 1 Log in to the OS as an administrator.
Step 3 In the System dialog box, click the Remote settings tab.
Step 4 System Properties dialog box, set the remote login right through the option button as
required.
Step 5 Click OK.
----End

9.1.9 How to Forcibly End a Process
Question
How to Forcibly End a Process
Answer
Step 1 Press Ctrl+Shift+Esc. The Windows Task Manager dialog box is displayed.
Step 2 Click the Processes tab. Right-click the process needs to be ended, and choose End Process.
----End
9.1.10 How to Configure the FTP or SFTP Service on Windows OS

This topic describes how do I configure the FTP or SFTP service on Windows OS.
Prerequisites
l To use the service of a third-party tool for file transfer, make sure that the third-party tool
configured as the FTP or SFTP service is started, and stop the FTP/SFTP service of the
U2000 server.
NOTE
The way of stop the FTP/SFTP service of the U2000 server is Stop the XftpDm process in the task
manager, configure the third-party FTP service, and then restart the ftpdaemon process.
l The file transfer parameters set on the U2000 must be the same as the parameters set on
the FTP or SFTP service.
l If FTP is used, perform operations as required. SFTP is recommended because it
provides better security.
– If the U2000 is not installed on the server, log in to http://mina.apache.org/
ftpserver-project/downloads.html to download the latest apache-ftpserver
compression package and refer to the documents on the website to configure the
FTP service. For more information about software operation, see the software Help
or go to the official website of the software http://mina.apache.org/ftpserver-
project/documentation.html for technical support. In addition to the apache-
ftpserver, the wftpd32.exe is another third-party tool used to configure the FTP
service. The wftpd32.exe cannot be used to configure the FTP service. Otherwise,
an abnormality occurs during remote database backup.
– If the U2000 has been installed on the server, apache-ftpserver will be
automatically installed along with U2000 installation. Therefore, you do not need to
manually configure the FTP service after the U2000 is installed.
Context
l The SFTP service is recommend because it provides better security.
l See operations in this topic on the windows server before U2000 data is backed up or
restored.
l User created for minasshd SFTP services is ftpuser by default and the default password
is Changeme_123. To ensure the security of the NMS, change the password for the
ftpuser user periodically.

NOTE
The password must meet the following rules:
l The password consists of 8 to 32 characters.
l The password must be a combination of three types of characters: digit, letter, and special character.
l Configuring the SFTP service key method is as follows, assuming the SFTP root
directory is D:
a. Log in to the NMS server as a NMS administrator account.
b. Copy the key file authorized_keys to the SFTP root directory.
c. Copy and paste the public key information to the .ssh file in the SFTP root
directory. If the .ssh file does not exist, run the following commands to create the
file and copy key information:
> cd d:
> mkdir .ssh
> copy authorized_keys .ssh
Procedure
l Optional: Configure the SFTP service.The SFTP service needs to be configured only
when SFTP is used on a server where the U2000 is not installed.
The minasshd software is automatically installed along with U2000 installation. The
SFTP services is automatically installed, and the user ftpuser is automatically created for
the services.
l Starting the SFTP service
a. Log in to the System Monitor client as a system administrator account.
b. Click the Service Monitor tab, right-click minasshd and choose Start the Service
from the shortcut menu to start the minasshd SFTP service.
l Stopping the SFTP service
a. Log in to the System Monitor client as a system administrator account.
b. Click the Service Monitortab, right-click minasshd and choose Stop the Service
from the shortcut menu to stop the minasshd SFTP service.
----End
9.1.11 How to Set the Virtual Memory to the System Managed

Size
Question
How to Set the Virtual Memory to the System Managed Size
Answer
Step 2 Click Start. Right-click Computer on the desktop and choose Properties from the shortcut
menu.
Step 3 In the System dialog box, click the Advanced system settings tab.

Step 4 In the System Properties dialog box, click the Advanced tab.
Step 5 In the Performance area, click Settings.
Step 6 In the Performance Options dialog box, click the Advanced tab.
Step 7 In the Virtual memory area, click Change.
Step 8 In the Virtual Memory dialog box , deselect Automatically manage paging file size for all
drives and click the System managed size option button.
Step 9 Click Set.
Step 10 Click OK.
----End
9.1.12 How to Query the Type of a Windows OS
Question
How to query the type of a Windows OS?
Answer
Step 3 In the System dialog box, view the value of System type and verify that the OS version is
Windows 7 Professional.
----End
9.1.13 How to Log In to the CLI on Windows
Question
Some system commands, such as ipconfig, can be run in the CLI on Windows. How do I log
in to the CLI on Windows?
Answer
Step 1 Choose Start > Run on Windows. The Run window will be displayed.

NOTE
To query the IP address and gateway information about the PC, enter ipconfig and press Enter.
----End

9.1.14 How to Shut Down Automatic Update of the Windows OS

Question
How to Shut Down Automatic Update of the Windows OS
Answer
Step 1 Log in to the OS as the administrator.
Step 3 Enter services.msc and click OK. The Services window will be displayed.
Step 4 Right-click Windows Update service and choose Properties from the shortcut menu.
Step 5 On the General tab, change the value of Startup type to Disabled.
Step 6 Click OK.
Step 7 Choose File > Exit.
----End
9.1.15 How do I to partition disks on Windows 7 without loss

Question
How do I to partition disks on Windows 7 without loss?
Answer
Step 2 Click Start. Right-click Computer and choose Manage from the shortcut menu.
Step 3 In the Server Manager dialog box, choose Storage > Disk Management from the
navigation tree.
Step 4 Right-click (C:) and choose Shrink Volume from the shortcut menu.
Step 5 After the Querying Shrink Space dialog box is displayed, wait for a while.
Step 6 In the Shrink C: dialog box, enter the disk space size to be released and click Shrink.
Step 7 In the Server Management dialog box, right-click Unlocated and choose New Simple
Volume from the shortcut menu.
Step 8 In the New Simple Volume Wizard dialog box, click Next.
Step 9 In the Specify dialog box, enter the size of space to be partitioned and click Next.
Step 10 In the Assign Drive Letter or Path dialog box, click the Assign the following drive letter
option button, select an assigned disk from the drop-down list, and click Next.
Step 11 In the Format Partition dialog box, click the Format this volume with the following
setting option button, select a disk name from the File system drop-down list, select the
Perform a quick format check box, and click Next.

Step 12 In the Completing the New Simple Volume Wizard dialog box, click Finish.
Step 13 After the new partition status turns to Formatting, click Action and choose Refresh in the
Server Manager dialog box.
NOTE
For each new partition, perform the refresh operation.
Step 14 Create partitions based on needs by repeating steps 4to 13.
----End
9.2 SQL Server Database

This section describes the FAQs about the SQL Server database.
9.2.1 How to Check Whether the SQL Server Database Has Been
Installed
Question
How do I check whether the SQL Server database has been installed?
Answer
NOTE
If the SQL Server database has not been installed, when you install the U2000, the SQL Server database
is automatically installed for the U2000.
l Consult the computer's administrator to learn whether the SQL Server database has been
installed.
l Check whether the installation directory and file of the SQL Server database exist. A
sample directory is C:\Program Files\Microsoft SQL Server.
l Manually start the SQL Server database. For details, see How to Start the SQL Server
Database.
l Check whether the database is installed in binary mode. For details, see How to Check
Whether the SQL Server Database Can Be Sorted in Binary Mode.
----End
9.2.2 How to Shut Down the SQL Server Database
Question
How to Shut Down the SQL Server Database?
Answer
Step 1 Log in to Windows7 OS as an OS user with administrator rights.
Step 2 Choose Start > All Programs > Microsoft SQL Server 2008 > Configuration Tools > SQL

Step 3 Perform the following operations to ensure that the SQL Server database has been stopped.
Right-click SQL Server (MSSQLSERVER) and check whether the shortcut menu option
Stop is grayed out.
l If Stop is grayed out, the SQL Server database is stopped.

l If Stop is not grayed out, the SQL Server database is not stopped. Right-click SQL
Server (MSSQLSERVER) and choose Stop from the shortcut menu.
----End
9.2.3 How do I start the SQL Server database
Question
How do I start the SQL Server database
Answer
Step 3 Perform the following operations to ensure that the database is started.
Start is grayed out.
l If Start is dimmed, the Microsoft SQL Server database is started.

l If Start is not dimmed, the Microsoft SQL Server database is not started. Right-click
SQL Server (MSSQLSERVER) and choose Start from the shortcut menu.
----End
9.2.4 How to Check Whether the SQL Server Database Can Be

Sorted in Binary Mode
Question
How to Check Whether the SQL Server Database Can Be Sorted in Binary Mode
Answer

Step 4 Run the following commands at the command prompt:
Password:
1> sp_helpsort
2> go
NOTE
l DBSVR specifies the database name.

l Enter the database sa user password as prompted.
l The prompt C:\> varies according to on-site conditions. If the system is logged in to as the
administrator user, the default prompt is C:\Users\Administrator>. You can run the cd
command to switch the directory. A command example is:
The command prompt switches to c:\>
Step 5 If the displayed information includes binary sort, the database is sorted in binary mode. If the
displayed information does not include binary sort, the database is not sorted in binary mode.
Then, run the quit command.
----End
9.2.5 How to Manually Uninstall the Microsoft SQL Server

Database
Question
How do I manually uninstall the Microsoft SQL Server database?
Answer
Step 2 Ensure that the database is uninstalled correctly by performing the following steps:
1. Choose Start > Control Panel > Uninstall a program. The Uninstall or change a
program window is displayed.
NOTE
The buttons displayed in Control Panel vary according to the check mode on the upper right
corner. Click the button similar to program.
2. Right-click Microsoft SQL Server 2008 (64-bit) and choose Uninstall/Change.
3. The SQL Server 2008 dialog box will be displayed. Click Remove.
4. The SQL Server 2008 Setup dialog box will be displayed. After operation completed,
click OK.
5. The Select Instance dialog box will be displayed. Select default values, click Next.
6. The Select Features dialog box will be displayed. Select default values, Select the
uninstalled SQL Server features, click Next.
7. The Removal Rules dialog box will be displayed. After operation completed, click
Next.
8. The Ready to Remove dialog box will be displayed. Click Remove.

9. The Removal Progress dialog box will be displayed. Wait for 3 minutes, after operation
completed, click Next.
10. The Complete dialog box will be displayed. Click Close. The SQL Server 2008 removal
completed successfully.
11. Uninstall all database components except Microsoft SQL Server 2008 (64-bit). Sort the
components by Name (with the arrow facing upwards), and uninstall the components
one by one from top to bottom. To uninstall a component, right-click it and choose
Uninstall/Change.
NOTE
During uninstallation, a message may be displayed indicating that the computer fails to be
restarted. See Step 4 to delete PendingFileRenameOperations.
12. Delete the database-related directories and registry information.
– If the database is installed using a software package, navigate to the directory where
the U2000 installation package is stored and double-click the
manual_clean_sqlserver.bat script in the engr\engineering\script directory.
– If the database is installed using a DVD-ROM, enter the U2000 installation DVD
and double-click the manual_clean_sqlserver.bat script in the engr\engineering
\script directory.

NOTE
– If the information indicating successful deletion is displayed, the database-related directories

and registry information are deleted successfully. Press any key to close the window.
– If the engr\engineering\script directory does not contain the manual_clean_sqlserver.bat
script, perform the following operations to delete the directories and registry information about
the database:
1. Delete the MSSQL2008, MSSQLX and MSSQL folders in the installation directory of
the database.
2. Delete the Microsoft SQL Server folder in the Program files folder that is in the
installation directory of the OS.
3. Delete the Microsoft SQL Server and Microsoft SQL Server Compact Edition folders
in the Program files (x86) folder that is in the installation directory of the OS.
4. Choose Start > All Programs. Check whether Microsoft SQL Server 2008 programs
have been deleted. If not, right-click Microsoft SQL Server 2008 and choose Delete from
the shortcut menu.
5. Click Start > Run. In the Run dialog box, enter regedit to open the registration table,
delete the following registry information:
1. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server
2. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server 2005
Redist
3. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server 2008
Redist
4. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server Native
Client 10.0
5. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\MSSQLSERVER
6. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services
\SQLSERVERAGENT
\MSSQLServerADHelper
\MSSQLServerADHelper100
9. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\MSDTC
10. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
\PendingFileRenameOperations
11. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup
\ExceptionComponents
12. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App
Paths\setup.exe\RunAsOnNonAdminInstall
13. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App
Paths\setup.exe\BlockOnTSNonInstallMode
14. HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\DBSVR
Step 3 After the preceding operations are performed, restart the OS.
Step 4 Ensure that the registries do not contain the PendingFileRenameOperations key value.
1. Click Start > Run. In the Run dialog box, enter regedit to open the registration table.
2. Ensure that the registries do not contain the PendingFileRenameOperations key value
in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session
Manager. If PendingFileRenameOperations is included, right-click it and choose
Delete from the shortcut menu.
----End

9.2.6 How to check the name of the SQL Server database server
Question
How to check the name of the SQL Server database server
Answer
Server Configuration Manager > SQL Native Client 10.0 Configuration.
Step 3 Click the Aliases tab page to check the name of the SQL Server database server.
----End
9.2.7 How to Check the Version of the SQL Server Database

Server
Question
How to Check the Version of the SQL Server Database Server
Answer
Step 4 In the CLI, run the following commands to check the database version information:
NOTE

administrator user, the default prompt is C:\Users\Administrator>. You can run the cd
command to switch the directory. A command example is:
The command prompt switches to c:\>
1> select @@version
2> go
l If the database version is correct, information similar to the following is displayed:

-----------------------------------------------------------------
Microsoft SQL Server 2008 (SP1) - 10.0.2531.0 (X64)
Mar 29 2009 10:11:52
Copyright (c) 1988-2008 Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601:
Service Pack 1)
(1 row affected)

l If the database version is not 10.0.2531.0, you must reinstall the database patch or
contact Huawei technical support engineers.
----End
9.3 U2000 System

This section covers FAQs about the U2000 system.
9.3.1 How do I verify that the processes of the U2000 single-server

system are running on Windows
Question
How do I verify that the processes of the U2000 single-server system are running on
Windows
Answer
Step 2 Check whether the U2000 server is started:

3. Run the daem_ps command in the CLI to check whether the U2000 process is started.
– If the process list contains imapmrb.exe, imapwatchdog.exe, imapsysd.exe,
imapeventmgr.exe, imap_sysmonitor.exe, and ResourceMonitor.exe processes,
the U2000 server has been started.
– If no command output is displayed, the U2000 process is not started yet. In this
case, run the D:\oss\server\platform\bin\startnms.bat command or double-click
startnms.bat in D:\oss\server\platform\bin\ to start the U2000 process.
NOTE
l D:\oss is the U2000 installation path.

l Starting the U2000 process takes about 3 minutes.
----End
9.3.2 How do I start the processes of the U2000 single-server

system
Question
How do I start the processes of the U2000 single-server system
Answer


Step 3 Check whether the U2000 server is started:

NOTE

l Starting the U2000 process takes about 3 minutes.
----End
9.3.3 How do I end the processes of the U2000 single-server

system
Question
How do I end the processes of the U2000 single-server system
NOTICE
You can stop all the services of the NMS, including the system monitoring process.
If you use the Stop All NMS Services function of the System Monitor, the system monitoring
process is not ended. Do not use this method if perform operations for shutting down the
NMS that is associated with the database.
Answer
Step 1 Exit all the U2000 clients.
Step 2 End the NMS processes.


3. Run the daem_ps command in the CLI to check whether the U2000 process is stopped.
the U2000 server has been started. In this case, run the D:\oss\server\platform\bin
\stopnms.bat command or double-click stopnms.bat in D:\oss\server\platform
\bin\ to stop the U2000 process.
– If no command output is displayed, the U2000 process is stopped yet.
NOTE

l Stopping the U2000 process takes about 3 minutes.
----End
9.3.4 How to Resolve the Problem Wherein the Message "PATH

environment's length is too long" Is Displayed During
Question
When the U2000 is installed on Windows OS, the following message is displayed and the
installation is paused. In this case, how do I resolve the problem?
PATH environment's length is too long. Please delete some useless fields and then
perform the installation.
Answer
Step 1 Right-click Computer on the desktop and choose Properties from the shortcut menu.
Step 2 Click Advanced system setting and click the Advanced tab.
Step 3 Click the Advanced tab.
Step 4 Click Environment Variables to check whether the environment variable exceeds the
maximum length. When you check the length of the PATH environment variable, you may
find that %PATH% is added to the environment variable. As a result, environment variable
exceeds the maximum length.
... C:\WINDOWS\system32;%PATH%; ...
In this case, delete %PATH% from the environment variable.
----End
9.3.5 Which Installation Packages Are Required for U2000

Installation
Question
Which installation packages are required for U2000 installation
Answer
Prepare installation packages according to the U2000 installation scheme.

Table 9-1 DVD list

Software Medium Name
Database software DVD Microsoft SQL Server (personal-edition,

installed on Windows 7 OS):
U2000version_server_dbper_win64_x86_d
vd2.
U2000 server software DVD U2000version_server_nms_win32_x86_dvd

3
ESN tool software U2000version_ESN_win32_x86.zip.The

ESN tool is required only when you apply
for the U2000 License before installing the
U2000.
NOTE
The tool is a software package. It will not be
delivered as a DVD-ROM. After the U2000 is
installed, the ESN tool is available in the U2000
installation path. Therefore, to apply for the
U2000 license after the U2000 is installed, use
the ESN tool in this path directly.
Table 9-2 Software package list

Database software Microsoft SQL Server It must be available.It is

(personal-edition, installed used to install the database.
on Windows 7 OS):
U2000version_server_sqlser
ver2008_ dbper
_en_win64_x86.zip
NOTE
l The Windows 7 OS only
supports
erver2008_dbper_en_win6
4_x86.zip.
l The standard database
erver2008_dbstd_en_win6
4_x86.zip is not supported.
U2000 server software Basic components: It must be available.It is

U2000version_server_nmsb used to install the U2000.
ase_win32_x86.7z
Core components: It must be available.It is

U2000version_server_nmsc used to install the U2000.
ore_win32_x86.7z

Access domain components: It is required only if the

U2000version_server_nmsa U2000 needs to manage
ccess_win32_x86.7z Huawei access equipment.
includes:
l FTTx equipment
l MSAN equipment
l DSLAM equipment
l BITS equipment
IP domain components: It is required only if the

U2000version_server_nmsi U2000 needs to manage
p_win32_x86. 7z Huawei access equipment.
includes:
l ATN Series Equipment
l Routers
l Switches
l Metro service equipment
l Broadband access
equipment
l VoIP gateways
l Firewalls
l Service inspection
gateway
l SVN equipment
l Internet Cache System
Transport domain It is required only if the

component: U2000 needs to manage
U2000version_server_nmstr Huawei access equipment.
ans_win32_x86.7z Huawei access equipment
includes:
l MSTP equipment
l WDM equipment
l RTN equipment
l PTN equipment
NOTE
Software packages for the
transport and IP components
must be available to manage
PTN 6900 and PTN 7900
series NEs.

ESN tool software U2000version_ESN_win32 The ESN tool is required

_x86.zip only when you apply for
the U2000 License before
installing the U2000.
NOTE
The tool is a software package.
It will not be delivered as a
DVD-ROM. After the U2000
is installed, the ESN tool is
available in the U2000
installation path. Therefore, to
apply for the U2000 license
after the U2000 is installed,
use the ESN tool in this path
directly.
9.3.6 How to Process the Message Displayed During Installation

of the U2000, Indicating That a Suspended File Has Been Created
Question
How do I process the message displayed during installation of the U2000, indicating that a
suspended file has been generated?
Answer
Step 1 On Windows OS, the system displays a message indicating that a suspended file is already
created during the reinstallation of the U2000. This is because the suspended file is generated
during the previous installation.
Enter the following command in the address bar and then press Enter:
%tmp%
Step 2 Query the ClearInstallDiskDir.bat file and delete it.
----End
9.3.7 How to Resolve the Problem that the Database Installation

File Is Not Found During Installation
Question
During NMS installation, a dialog box for selecting the database path is displayed on the
database service configuration page, indicating that the database installation file is not found.
How do I resolve this problem?

Answer
Step 1 Verify that this problem is caused by a failure to find the database installation file.
Step 2 Specify the database installation DVD-ROM path or the decompression path of the database
installation package.
Step 3 Verify that the database installation file matches the OS. If they do not match, reinstall the
database.
----End
9.3.8 Failure to Connect to the Database When the Progress Bar

for File Copy Reaches 80% During Installation of the U2000
Server Software
Question
During installation of the U2000 server software, the U2000 does not respond when the
progress bar for file copy reaches 80% and a message indicating a database connection failure
is displayed. How to solve this problem?
Answer
Step 1 View the U2000 installation logs. The installation logs show that the fault occurs because the
server memory does not meet the configuration requirement; as a result, the memory runs out
during installation of the U2000 server software.
Step 2 Ensure that server hardware and software meet configuration requirements. For details, see
the U2000 Single-Server System Software Installation Guide (Windows 7).
----End
9.3.9 How to Handle the Problem Wherein the System Displays a

Message Indicating That the Client Installation Packages and
Basic Packages Cannot Exist at the Same Time During
Decompression
Question
In a scenario where the U2000 server software is installed by using software packages,
software packages are decompressed, the system displays a message indicating that the client
installation packages and basic packages cannot exist at the same time. How do I handle this
problem?
Answer
This problem arises because both the server software packages and client software packages
are copied and then decompressed at the same time. To resolve this problem, delete client
software packages and then decompress them again.

9.3.10 How Do I Verify Downloaded Software Packages Using the

PGPVerify Software
Question
How do I verify downloaded software packages using the PGPVerify software?
Answer
l Software packages and signature files correspond to each other and are stored in the
same directory. A software package corresponds to a signature file. Signature files are
released with products and their software packages.
l The extension of signature files is .asc. Generally, the names of signature files are the
same as the names of software packages. That is, when the software package name is
V200R016C50.zip, the corresponding signature file name is V200R016C50.zip.asc.
l Obtain the PGPVerify tool that is used to verify the completeness of downloaded
software packages and its public key file KEYS.
a. Download and decompress the PGPVerify tool.
n For carrier: visit http://support.huawei.com/carrier/digitalSignatureAction
to download the OpenPGP Signature Verification Guide package and
decompress it. Continue to decompress the VerificationTools.zip package in
the current folder.
n For enterprise: visit http://support.huawei.com/enterprise/
toolNewInfoAction!showDetail?
pid=8221819&show=showServiceDetail&versionid=TV1000000016 to
download and decompress the VerificationTools.zip package.
b. Go to the VerificationTools folder that is generated after decompression and obtain
different versions of PGPVerify software for different OSs.
n Windows: PGPVerify.exe (in the Windows directory)
n Solaris: PGPVerify-sparc.tar.bz2 (in the solaris\PGPVerify TOOL directory)
n Linux: PGPVerify-x86_64.tar.gz (in the linux\X86\bit64\PGPVerify TOOL
directory)
c. Windows OS supports GUI-based verification and CLI-based verification. Solaris
and Linux OSs support CLI-based verification only.
d. KEYS is the public key file.
l PGPVerify is a digital signature verification tool released by Huawei. Users can select
third-party openPGP verification tools based on actual needs.
Tool OS Tool Description
PGPVerify Windows It is a simple PGP

verification tool released
by Huawei.

Tool OS Tool Description
GNU Privacy Guard for Windows It is an official version of

Windows (Gpg4Win) GnuPG for Windows.
Official website: http://
www.gpg4win.org/
Recommended version:
2.2.1
l GUI-based verification on Windows OS:

Files to be prepared before verification:
– PGPVerify software: PGPVerify.exe
– Public key file corresponding to the PGPVerify software: KEYS
– U2000 software package
– Signature file corresponding to the U2000 software package
a. Double-click PGPVerify.exe to start the PGPVerify tool.
b. Click Select Public Key, select the obtained public key file KEYS, and load it.
c. Click Multiple Verify and select the D:\oss\ directory to verify all files in it.
NOTE
l D:\oss\ indicates the directory that stores the signature file. Change it based on site
requirements. The signature file and software package must be stored in the same
directory.
l To verify a single file, click Single Verify and select the file to be verified.
n The green item indicates passed verification, that is, [PASS].
n The yellow item indicates unsupported verification, that is, [WARN]. For
example, the signature file or software version does not exist.
n The red item indicates failed verification, that is, [FAIL].
If no "WARN" or "FAIL" character is displayed, the signature file is valid. All items
are displayed in green.
NOTICE
If a version has multiple signature files to be verified, the version is secure only
when the verification results of all files are "PASS". If the verification results
contain "WARN" or "FAIL", the verification is not passed and security risks exist.
In that event, re-download the software package.
l CLI-based verification on Windows OS:

a. Open the CLI and run the following command to verify the signature file:
> "C:\PGPVerify.exe" -k "C:\KEYS" -d "D:\oss"

NOTE
l Assume that the signature file and software package are stored in the D:\oss\ directory, and
the PGPVerify tool and public key file are stored in the C:\ directory.
l To verify a single file, run the C:\PGPVerify.exe" -k "C:\KEYS" -f "D:\oss
\V200R016C50.zip.asc command.
Information similar to the following is displayed:

[INFO]:Filter file in directory, please wait...
[WARN]:Can't find signature file, signed file position: D:\oss
\V200R016C50.zip.
[WARN]:Can't find signed file, signature file position: D:\oss
\V200R015C51.zip.asc.
[FAIL]:Invalid Signature. File path: D:\oss\V200R015C52.zip.
[PASS]:Good Signature. File path: D:\oss\V200R015C53.zip, Public key
fingerprint: B1000AC3 8C41525A 19BDC087 99AD81DF 27A74824
INFO]: Verify Complete.
NOTE
In the preceding characters in bold, the RSA key ID is consistent with the public key ID. For
a certain file, if no "WARN" or "FAIL" character is contained in other information, the
signature file is valid.
NOTICE
If a version has multiple signature files to be verified, the version is secure only
when the verification results of all files are "PASS". If the verification results
contain "WARN" or "FAIL", the verification is not passed and security risks exist.
In that event, re-download the software package.
----End
9.3.11 How to Set the Communication Mode on the U2000 server

for the Single-Server System (Windows)
Question
The U2000 server and client can communicate with each other in common or Security Socket
Layer (SSL) mode. How to set the common or SSL mode?
Answer
Step 1 Log in to the OS on the U2000 server as an administrator and do as follows to query the
communication mode in use:
Choose Start > Run. In the Run dialog box, enter cmd to open the command line interface
(CLI). Enter ssl_adm -cmd query to query the communication mode that the U2000 server is
using.
Step 2 Stop U2000 processes.

In the U2000 software installation path, for example, D:\oss\server\platform\bin, run the
stopnms.bat file to stop U2000 processes.
Step 3 Set the communication mode for the U2000 server and client.

Choose Start > Run. In the Run dialog box, enter cmd to open the CLI. Enter ssl_adm -cmd
setmode mode parameter and set the communication mode for the U2000 server and client.
NOTE
The available options for mode parameter are common, ssl, and both.
l common: common mode. If mode parameter is set to common, the U2000 server and client can
communicate only in common mode, and http protocol must be used to download the U2000 client
in CAU mode.
l ssl: security mode. If mode parameter is set to ssl, the U2000 server and client can communicate
only in security mode, and https protocol must be used to download the U2000 client in CAU
mode. The security mode is recommended to ensure security for communication between the
U2000 server and client.
l both: indicates that the U2000 server and client can communicate with each other in either
common or SSL mode.
If the following information is displayed, the communication mode of the server has been set
successfully.
Operation succeeded. Please restart all services for the settings to take effect.
Step 4 If you need to install the client in CAU mode after the server communication mode is set, you
must perform the following operations as the administrator user:
In the U2000 software installation path, for example, D:\oss\cau\bin, run the cau.bat file to
update the CAU. If the following information is displayed, the operation has been set
successfully.
CAU is now updating resource, please wait...
Script is executed successfully.
Step 5 Start U2000 processes.

In the U2000 software installation path, run the D:\oss\server\platform\bin\startnms.bat
command or double-click startnms.bat in D:\oss\server\platform\bin to start the U2000
process.
----End
9.3.12 How to Resolve the Problem that the License Does Not
Take Effect
Question
A message is displayed indicating that the license of the U2000 is invalid. As a result, the
U2000 cannot be started or certain functions cannot be used.
How do I resolve this problem?
Answer
The possible causes are as follows:
l The license item is incorrect.
l The time setting of the OS is incorrect.
l Check for and rectify the fault on Windows according to the following precautions:
NOTE
Suppose that the U2000 is installed in the D:\oss directory.

a. Ensure that the date of the OS is the current date.

b. Check whether the ESN is correct.
You can obtain the ESN tool according to the U2000 License Instructions to check
the ESN.
c. A unique license file exists in theD:\oss\server\etc\conf\license path.
If more than one license files exist in the path, you must delete redundant license
files manually.
d. The NIC used during license application must be the NIC actually used on the
server.
If the NICs are different, you must apply for a new license.
e. The license file must comply with the U2000 version.
f. Check whether an error has occurred during the license file transfer.
If an error has occurred, transfer the license file again or download the license file
to the D:\oss\server\etc\conf\license directory. Restart the U2000 and check
whether the license takes effect.
----End
9.3.13 How to Confirm the Encoding Format of the U2000 License

File
Question
How do I confirm the encoding format of the U2000 license file?
Answer
The encoding format of the U2000 license file must be UNIX, not DOS.
9.3.14 Failure to Log In to the U2000 Server from a U2000 Client
Symptom
A user fails to log in to a U2000 client after a user name and a password have been entered in
the login window.
Possible Causes
The possible causes are as follows:
l The U2000 server does not work properly, the U2000 server fails to start properly, the
disk on the U2000 server is full, or the memory usage of the U2000 server is high
because many processes are started.
l An incorrect user name or password has been entered for logging in to the U2000 client.
l If the U2000 server runs on Windows, the dynamic port of the SQL Server is not 1433;
therefore, the U2000 server fails to connect to the database and login to the U2000 server
from a U2000 client fails.
l The network between the client and server does not function properly.

l The license file is a temporary one or is damaged.

l The number of clients allowed in the license is restricted.
l The port between the client and server is shielded by firewall or viruses. In common
mode, port 31037 is used by default. In SSL mode, port 31039 is used by default.
l The version of the client is inconsistent with that of the server.
l The communication protocol used by the client is inconsistent with that used by the
server.
l The user that logs in to the client is locked. This may be caused by too many times of
login failures.
l The IP address of the computer where the client is installed is not listed in the ACL.
l The OS time on the client is set incorrectly and the ILOG JTGO license is expired.
l The DCN is faulty.
l The 360 antivirus software has been installed on the server.
l The dfwModule fails to be loaded.
l The maximum client login limit has been reached.
Procedure
Step 1 If an error message is displayed, locate and rectify the fault as prompted.
Step 2 Check whether the server has been started properly. Ensure that the server runs properly, the
disk space of the server is not used up, and not many processes are started on the server. If
many processes are started on the server, the memory usage is high.
1. Ensure that the server has been started properly.
2. Ensure that the disk space of the server is not used up.
To troubleshoot the full disk space on the server on Windows, perform the following
operations:
Check that disk C is fully used, delete log files, and restart the U2000.
3. Ensure that not many processes are started on the server.
After the U2000 server is started, do not access the JDE desktop (switch to the CED
environment for the U2000 on the live network). Start the U2000 in CLI mode.
Step 3 Verify that the entered user name and password are correct.
Step 4 If a message indicating that the license file is invalid when you log in to the U2000 client,
rectify the license fault according to 9.3.12 How to Resolve the Problem that the License
Does Not Take Effect and log in to the U2000 client.
Step 5 Choose Help > License Management > License Information from the main menu
(traditional style); alternatively, double-click System Management in Application Center
and choose License Management > Licenes Information from the main menu (application
style).
If the number of clients to log in exceeds the maximum number of clients allowed in the
license, apply for a new license and update the U2000 license file.
Step 6 Check whether the versions of the client and server are consistent. If the versions are
inconsistent, a message will be displayed asking you to upgrade the client. In this case, try to
upgrade or reinstall the client.

Step 7 Check whether the versions of the client and server are consistent. If the versions are
inconsistent, a message will be displayed asking you to upgrade the client. In this case, try to
upgrade or reinstall the client.
NOTE
Run the ssl_adm -cmd query command on the U2000 server to view the communication mode of the
U2000 server. For details, see 9.3.11 How to Set the Communication Mode on the U2000 server for
the Single-Server System (Windows).
Step 8 Check the network between the client and server.
Generally, the communication bandwidth between the client and server is at least 2 Mbit/s and
the packet loss ratio is smaller than 0.1%.
To check the network between the client and server, run the following command on Windows:
> ping -t IP_address_of_the_NMS
Step 9 Check whether the port between the client and server is shielded by firewall or viruses. Install
a virus scanner, scan the entire disk, and remove viruses. If the client installed on the
computer where the server belongs can log in to the server, but other clients cannot log in,
check whether the port has been added to the Windows firewall. If not, perform the following
operations to add the port to the Windows firewall:
1. Choose Start > Control Panel.

2. In the Control Panel window, click windows Firewall.
3. In the windows Firewall window, click Advanced Setting.
4. In the Windows Firewall with Advanced Security dialog box, choose Inbound Rules
from the left navigation tree and from New Rule the right navigation tree.
5. In the New Inbound Pule Wizard dialog box, select Port and click Next.
6. In Specific local ports, set Ports and click Next.
7. Select Allow the connection and click Next.
8. Click Next, set Name, and click Finish.
Step 10 Log in to the U2000 client as the admin user and choose Administration > NMS Security >
ACL.
On the U2000, you can set the client IP addresses that can be accessed. If the IP address of a
client is not in the permitted range, the client cannot access the server. For details, see "Setting
the Access Control List" in Chapter "Security Management" in the U2000 Administrator
Guide. If NAT is used for IP address translation for communication between the client and
server, ensure that the translated IP address is permitted in the ACL.
Step 11 If the number of failed login attempts by using the same user exceeds 3, the login authority of
the user is locked.
You can log in to the client again in 30 minutes (default) or unlock the user as another user
that has the authority, such as user admin.
Step 12 Check whether the system time is the current time. If not, modify the system time.
Step 13 Check whether the 360 antivirus software has deleted some U2000 files. If yes, uninstall the
360 antivirus software and re-install the U2000.
Step 14 Log in to NE Software Management, check the process list, and start all the processes with
Automatic startup mode.

Step 15 Create a user and use it to log in. For details, see "Setting the Maximum Number of Sessions"
in U2000 Administrator Guide.
----End
9.3.15 How to Rectify the Failure to Open the CAU Download

Web Page Because the Port Is Used
Question
How do I rectify the failure to open the CAU download web page because the port is used?
Answer
Step 1 Run the netstat -aon|findstr port number command in the CLI.
If no information is displayed, the port is not used. If any information is displayed, the port is
in use and the information in the rightmost column is the PID of the process that uses the port.
Step 2 On the Processes tab page in Windows Task Manager, right-click the PID and choose End
Process from the shortcut menu.
NOTE
l Stop the process only after you confirm that it can be stopped. Otherwise, the U2000 may fail to run
properly.
l If the PID list is not displayed on the Processes tab page, choose View > Select Columns from the
menu bar and select PID.
Step 3 Log in to the server OS.
Step 4 Start the tomcat process.

1. Run the start_daem command in the CLI.
2. After the daem has been started successfully, run the daem_ps command in the CLI. The
tomcat process is running if the displayed information contains javaw.exe.
----End
9.3.16 How to Solve the Problem Where the U2000 Server Fails to
Be Installed Due to a Network Issue
Question
How do I solve the problem where the U2000 fails to be installed due to a network issue.
Answer
During installation of the U2000, some NIC services must be invoked during software
installation. If the NIC is not activated, the U2000 server cannot be installed properly.
Step 1 Resolve the network issue about the server and reinstall the U2000.
----End

9.4 Handling the Failure to Install the U2000 Server

Software
If the U2000 fails to be installed, you need to handle the problem and re-install the U2000.
This section describes how to handle the failure to install the U2000.
Context
Using the uninstall.bat program carried by the U2000 to uninstall software is recommended.
For details, see 10 Uninstalling the U2000 Server. If this method cannot be used to uninstall
software after installation fails, refer to the following operations:
Procedure
Step 1 End U2000 and MSuite processes.
Step 2 Press Ctrl+Shift+Esc. The Windows Task Manager dialog box is displayed.
Step 3 In the Windows Task Manager dialog box, click the Processes tab and check whether the
httpd and tomcat processes exist. If the two processes exist, manually end them.
Server Configuration Manager > SQL Server Services. right-click SQL Server
(MSSQLSERVER) in the right pane, and then choose Stop from the shortcut menu to stop
the database server. Then, choose Start to start the database server to ensure that no external
user accesses the SQL Server database.
Step 5 Delete database installation files.

l Delete the MSSQL2008, MSSQLX and MSSQL folders in the installation directory of
the database.
l Delete the Microsoft SQL Server folder in the Program files folder that is in the
installation directory of the OS.
l Delete the Microsoft SQL Server and Microsoft SQL Server Compact Edition
folders in the Program files (x86) folder that is in the installation directory of the OS.
l Choose Start > All Programs. Check whether Microsoft SQL Server 2008 programs
have been deleted. If not, right-click Microsoft SQL Server 2008 and choose Delete
from the shortcut menu.

Step 6 Restart the OS, log in to the OS as user administrator, and re-install the U2000.
----End

Commissioning Guide (Windows 7) 10 Uninstalling the U2000 Server
10 Uninstalling the U2000 Server
About This Chapter
This topic describes how to uninstall the U2000 server.

10.1 Uninstallation Preparations
This topic describes the preparations for uninstalling the U2000 server.
10.2 Uninstallation Procedure
This topic describes how to uninstall the U2000 server on a Windows OS.
10.3 Verifying the U2000 Server Uninstallation
This topic describes how to verify the U2000 server uninstallation.

10.1 Uninstallation Preparations

This topic describes the preparations for uninstalling the U2000 server.
Procedure
Step 1 Log out of all running U2000 clients.
Step 2 End U2000 services and processes. Double-click the stopserver.bat file in the U2000 path,
that is, D:\oss\engr\engineering, to end the U2000 MSuite processes.

NOTE

Server Configuration Manager > SQL Server Services. right-click SQL Server
(MSSQLSERVER) in the right pane, and then choose Stop from the shortcut menu to stop
the database server. Then, choose Start to start the database server to ensure that no external
user accesses the SQL Server database.
NOTE
When uninstalling the U2000 server, ensure that the database works properly. If the database has been
stopped, the uninstallation may fail.
----End
10.2 Uninstallation Procedure

This topic describes how to uninstall the U2000 server on a Windows OS.
Prerequisites
l Preparations for uninstalling the U2000 server software have been completed.
l Ensure that the NMS installation path has been stopped.

Context
l Do not uninstall databases when uninstalling the U2000. If the database needs to be
uninstalled, uninstall the U2000 and then the database. Otherwise, some data files cannot
be deleted.
l If the database and backup files need to be saved, manually back up the D:\backup
\dbbackup directory to a non-installation directory of the U2000 before uninstalling the
U2000.
l This operation will uninstall the U2000. Specifically, this operation will cause NEs fail
to be managed and monitored and cause the U2000 database information to be deleted.
Procedure
Step 1 Log in to a Windows OS as an OS user with administrator rights. Choose Start > Programs
> Network Management System > Uninstall U2000.
NOTE
If a message is displayed indicating that a process is not stopped and therefore the U2000 cannot be
uninstalled, right-click the taskbar and choose Start Task Manager from the shortcut menu. In the task
manager, click the Processes tab and select the Show processes from all users check box. Check
whether the ftpdaemon.exe process exists. If the process exists, select the process and click End
Process.
Step 2 Click Next. The Information dialog box will be displayed.
Step 3 Click OK. The Uninstalling dialog box will be displayed.
Step 4 After the uninstallation is complete, the Uninstallation Completed dialog box will be
displayed.
Step 5 Click Finish. The Confirm dialog box will be displayed.
Step 6 Click Yes to restart the OS.
----End
10.3 Verifying the U2000 Server Uninstallation

This topic describes how to verify the U2000 server uninstallation.
Procedure
Step 2 Ensure that the shortcut icons are deleted from the Windows desktop. In addition, ensure that
the U2000 menu item has been deleted from the Start > Programs menu.
Step 3 Ensure that the installation path of the U2000 server, such as the D:\oss path, is deleted.
Step 4 Ensure that the environment variables of the U2000 have been deleted.
1. Right-click Computer on the desktop and choose Properties from the shortcut menu.
2. Click Advanced system setting and click the Advanced tab.
3. Click Environment Variables. In the Environment Variables dialog box, verify that all
U2000 environment variables have been deleted For details, see 7.5.1 Checking
Environment Variables.

NOTICE
The path environment variable is carried by the system. During U2000 uninstallation, only
parameters newly added for the path environment variable will be deleted.
----End

Commissioning Guide (Windows 7) 11 Manual Commissioning Task
11 Manual Commissioning Task
About This Chapter
Some commissioning tasks need to be manually executed during U2000 system parameter
commissioning. This topic describes how to execute a manual commissioning task.
11.1 Configuring a Digital Certificate
The U2000 supports security encryption to ensure the communication security for the DCN
and the confidentiality and integrity for the transmitted data. A digital certificate is also used
to distribute public keys.

11.1 Configuring a Digital Certificate

The U2000 supports security encryption to ensure the communication security for the DCN
and the confidentiality and integrity for the transmitted data. A digital certificate is also used
to distribute public keys.
11.1.1 Replacing SSL Certificates Used for the U2000 Server

When the U2000 is installed, the SSL certificate developed by Huawei is loaded for
temporary communication. Do not use this certificate commercially. The U2000 supports
certificate replacement. Before enabling SSL communication, apply for a certificate from a
CA and use it to replace the temporary certificate in the commissioning phase, to improve the
communication security of U2000. This topic describes how to replace the Security Socket
Layer (SSL) certificates used by the U2000 server.
Prerequisites
l You have obtained the trust certificate (rootCA.cer, subCA1.cer) and identity certificate
(server.p12) used by the server and the encryption password for the identity certificate.
l The SSL certificates have been backed up.
l Use the FTP to upload the new SSL certificate files (server.p12, rootCA.cer and
subCA1.cer) to the following directory on the U2000 server as the ossuser user before
you replace the SSL certificate of server.
– Solaris/SUSE Linux: /opt/oss/server/certs.
NOTE
l The directory is true only if the U2000 on Solaris or SUSE Linux OS is installed in /opt/
oss. If the U2000 is not installed in partition /opt, change the partition in the directory
accordingly.
l If security hardening is performed, ossuser FTP/SFTP rights will be disabled. In this
case, you need to upload files to the backup directory in the FTP root directory as the
ftpuser user (the FTP root directory of ftpuser is /opt/backup/ftpboot) and then copy
files to the target directory as the ossuser user.
– Windows: D:\oss\server\certs.
NOTE
The directory is true only if the U2000 on Windows OS is installed in D:\oss. If the U2000 is
not installed in partition D, change the partition in the directory accordingly.
NOTICE
Place only the certificate files server.p12, rootCA.cer and subCA1.cer in this directory.
Do not place other files in it. Otherwise, the certificate replacement script will fail to be
executed.
l The U2000 processes have been shutdown.
Context
l By default, the U2000 client authenticates the U2000 server, but the U2000 server does
not authenticate the U2000 client.

l The Huawei-predefined SSL certificates used to safeguard communication between the

U2000 server and client are located in the following directory:
– On Solaris or SUSE Linux OS: /opt/oss/server/etc/ssl.
– On Windows OS: D:\oss\server\etc\ssl.
l The MSuite and the U2000 use the same SSL certificates.
l The following script-based replacement procedure assumes that your OS is Solaris or
SUSE Linux OS. If your OS is Windows, replace the certificates for the U2000 server in
a similar way.
NOTICE
After SSL Certificates for the U2000 server have been replaced, you may fail to log in to
the MSuite.
Procedure
l Replace SSL certificates for the U2000 server through the GUI.
a. Ensure that the MSuite servers on the primary and secondary sites have been
started.
Run the following command as the root user to check whether the MSuite servers
are started:
NOTE
If security hardening is enabled, log in to the OS as the ossuser user. Then run the su - root
command and enter the root user password to switch to the root user.
# ps -ef | grep java
NOTE
If the displayed information contains , the MSuite servers have been started.
If the MSuite servers have not been started, switch to the ossuser and run the
following commands as the root user to start the MSuite servers:
# su - ossuser
$ cd /opt/oss/engr/engineering
$ ./startserver.sh
b. Log in to the MSuite client from the U2000 server.

c. Choose Certificate File Management > Internal NMS Certificate.
d. In the Certificate Configuration dialog box, select the SSL certificates to be
replaced and click ReplaceAll.
e. In the Information Confirmation dialog box, enter the PFX password.
NOTE
The new encryption password for the identity certificate must meet the following
requirements:
l At least one space or one special character: `~!@#$%^&*()-_=+\|[{}];:'",<.>/?
l At least two of the following combinations: lowercase letters a to z, uppercase letters
A to Z, and digits 0 to 9.
l The password cannot be the same as the user name or the reverse of the user name.

f. Click OK.
g. Because the MSuite reuses the U2000 digital certificates, restart the MSuite server
for the certificates to take effect.
l Replace SSL certificates for the U2000 server using a script.
a. Use the PuTTY to log in to the U2000 server in SSH mode as the ossuser user.
b. Run the following command to end the U2000 processes:
Single-Server System:
$ cd /opt/oss/server/platform/bin
$ ./stopnms.sh
c. Use the FileZilla to upload certificates to /opt/oss/server/certs on the U2000 server.

d. Run the following command to back up the certificates (as the root user):
$ ssl_adm -cmd backup -backpath /opt/backup/dbbackup/ssl
NOTE
The certificates can be backed up to an absolute or relative directory. The following steps
assume that the certificates are backed up to /opt/backup/dbbackup/ssl.
e. Run the following command to replace the certificates used by the U2000 server (as
the root user):
$ ssl_adm -cmd replace_certs -dir /opt/oss/server/certs
Enter the encryption password for the identity certificate based on the prompt.
NOTE
l /opt/oss/server/certs is the path for saving certificates.

l Two formats are available for the identity certificate.
l If the identity certificate is server.p12 of the PKCS#12 type (single file in PFX
format), ensure that the certificate password obtained together with the certificate
is correct, because the password is verified during command execution.
l If the identity certificate file is server.cer, password is user-defined. The command
is run to convert the server.cer file into the server.p12 file of the PKCS#12 type.
f. Enter the encryption password for the identity certificate and press Enter.
The certificates are successfully replaced if the following information is displayed:
SSL certificates are deployed successfully
NOTE
The new encryption password for the identity certificate must meet the following
requirements:
l At least one space or one special character: `~!@#$%^&*()-_=+\|[{}];:'",<.>/?
l At least two of the following combinations: lowercase letters a to z, uppercase letters
A to Z, and digits 0 to 9.
l The password cannot be the same as the user name or the reverse of the user name.
If the certificates fail to be replaced, resolve the problem based on the prompt and run the
following command to restore the certificates before replacing them again:
$ ssl_adm -cmd restore -backpath /opt/backup/dbbackup/ssl
g. After the certificates are successfully replaced, run the following commands to
import environment variables and update the CAU configuration data (as the root
user).
# cd /opt/oss/cau/bin/
# ./cau.sh
h. Run the following commands to start U2000 processes for the replacement to take
effect:

Single-Server System (as the ossuser user):

$ cd /opt/oss/server/platform/bin
$ ./startnms.sh
----End
Follow-up Procedure
l After the trust and identity certificates used by the U2000 server are successfully
replaced, delete certificate files from /opt/oss/server/certs on the U2000 server.
l After the trust and identity certificates used by the U2000 server are successfully
replaced, replace the trust and identity certificates used by the U2000 client as well.
11.1.2 Deploying the SSL Trust Certificate on the Internet

Explorer
When the U2000 uses Hedex Help or uses the Web LCT to manage NE series, such as the NG
WDM, NG WDM (NA), RTN, and Marine, some functions of the NE Explorer must be
opened through an Internet Explorer. In this case, the SSL trust certificate of the Internet
Explorer must be deployed.
Context
The trust certificate preconfigured by Huawei consists of the root certificate
huaweiossCA.crt and intermediate certificate networkossCA.crt. All of the certificates need
to be deployed on the Internet Explorer.
Procedure
Step 1 Open the Internet Explorer of the U2000 client and choose Tool > Internet Options from the
main menu.
Step 2 In the Internet Options dialog box, select Content tab and click Certificates.
Step 3 In the Certificates dialog box, deploy the root certificate huaweiossCA.crt.
1. Select the Trusted Root Certification Authorities tab and click Import.
2. In the Certificate Import Wizard dialog box, click Next.
3. Click Browse..., select the trusted root certificate huaweiossCA.crt, and click Next.
NOTE
The trust root certificate preconfigured by Huawei, huaweiossCA.crt , is stored in the oss\client
\client\style\defaultstyle\conf\ssl\trust\PEM directory.
4. Click Next, and then click Finish.
5. In the Security Warning dialog box that is displayed, click Yes.
6. In the Certificate Import Wizard dialog box, click OK.
Step 4 Deploy the intermediate certificate networkossCA.crt.
1. Select the Intermediate Certification Authorities tab and click Import.
2. In the Certificate Import Wizard dialog box, click Next.
3. Click Browse..., select the trusted intermediate certificate networkossCA.crt, and click
Next.

NOTE
The trust intermediate certificate preconfigured by Huawei, networkossCA.crt, is stored in the

oss\client\client\style\defaultstyle\conf\ssl\trust\PEM diectory.
4. Click Next, and then click Finish.
5. In the Certificate Import Wizard dialog box that is displayed, click OK.
Step 5 Click Close.
Step 6 In the Internet Options dialog box, select the Advanced tab. Drag the scroll bar to Security
and clear the selection of the Warn about certificate address mismatch*.
Step 7 Click OK.
Step 8 Restart the Internet Explorer.
----End
Follow-up Procedure
l If the U2000 GUI is displayed abnormally, the SSL certificate fails to be uploaded. Refer
to the preceding operations to redeploy a digital certificate.
l If the dialog which prompted you need trusted certification is displayed in the U2000 NE
management, right-click Continue to this website (not recommended), and then click
Open in the New Window. In the dialog box that is displayed, click OK. If the Security
Alert dialog box for the installation certificate is displayed, click OK to display the
current function GUI. After finish the operation, the U2000 GUI will display normally.

Single-Server System Software Installation and 12 Starting the U2000 Server in a Windows Single-Server
Commissioning Guide (Windows 7) System
12 Starting the U2000 Server in a Windows

Single-Server System
About This Chapter
The U2000 server can be started in three steps: power on the server safely, start the database,
and start the U2000 server processes.
12.1 Powering On the Server Safely
This topic describes how to power on the server in a Windows 7 single-server system safely.
12.2 Starting the Database
This topic describes how to start the database in a Windows single-server system. The U2000
can start properly only after the database is started.
12.3 Starting the U2000 Server Processes
This topic describes how to start the U2000 server processes in a Windows single-server
system. You can log in to the U2000 to manage a network only after starting the U2000 server
processes on the computer on which the U2000 is installed.

12.1 Powering On the Server Safely

This topic describes how to power on the server in a Windows 7 single-server system safely.
1. Press workstation external devices and monitor power switch, to the external devices and
monitor electricity.
2. Press the power buttons on the peripherals and monitor connected to a server.
12.2 Starting the Database

This topic describes how to start the database in a Windows single-server system. The U2000
can start properly only after the database is started.
Prerequisites
The OS has been started.
Context
Generally, the database starts along with the OS.
Procedure
NOTE
The database can be started or stopped only by administrator.

----End
Result
Open the task manager of the server and click the Processes tab to check whether the
sqlserver.exe process is started by the dbuser user.
12.3 Starting the U2000 Server Processes

This topic describes how to start the U2000 server processes in a Windows single-server
system. You can log in to the U2000 to manage a network only after starting the U2000 server
processes on the computer on which the U2000 is installed.

Prerequisites
The OS on the computer on which the U2000 server processes are installed is running
properly, and the database has been started.
Context
l Generally, the U2000 server processes start along with the OS.
l Only one default NMS user, admin, is provided during U2000 software installation. The
admin user is a U2000 administrator with the highest rights on the U2000 system.
Procedure
Step 2 View the startup information about the U2000 server processes.
Step 3 Check the running status of every process on the System Monitor client.
1. Choose Start > All Programs > Network Management System > U2000 System
Monitor or click the shortcut icon on the desktop to start the U2000 System Monitor
client.
2. In the Login dialog box, enter a user name and a password.
NOTE
l Two data transmission modes are available: Common and Security(SSL) (more secure,
recommended). The default data transmission mode is Security(SSL). For details, see section 9.3.11
How to Set the Communication Mode on the U2000 server for the Single-Server System
(Windows) to query or change the communication mode of the server.
l The initial password of the admin user is Changeme_123 (It is Admin_123 for a U2000 that comes
preinstalled). The password must be changed during the first login to ensure system security. Keep
the password confidential and change it regularly.
----End
Result
l If the U2000 services with the startup type of Automatic have started properly, the
U2000 runs properly.
l If some services have not started, select them, right-click, and choose Start the Service
from the shortcut menu.
l If the U2000 does not run properly, contact Huawei engineers.

Follow-up Procedure
l The network management system maintenance suite is used for U2000
commissioning, maintenance, and redeployment.
Log in to the OS as a user with administrator rights, in the Windows Task Manager
dialog box, check whether msdaemon.exe and msserver.exe are listed.
– If the two processes are listed, the MSuite server has started.
– If the two processes are not listed, the MSuite server has not started. Navigate to the
D:\oss\engr\engineering directory of U2000 server and double-click
startserver.bat to start the MSuite server.
l If login to a U2000 client fails, see 9.3.14 Failure to Log In to the U2000 Server from
a U2000 Client.
l If the above checks have one does not meet the requirements, the installation was
abnormal, see 9.4 Handling the Failure to Install the U2000 Server Software.

Commissioning Guide (Windows 7) 13 Powering Off the System
13 Powering Off the System
About This Chapter
Three steps are required to shut down the U2000 server: stop the U2000 server processes, shut
down the database, and power off the server safely.
13.1 Stopping the U2000 Server Processes
Do not stop the U2000 server processes when the U2000 server is managing NEs. Stop the
U2000 server processes only for some special purposes, for example, changing the system
time of the computer where the server is installed or upgrading the version. This topic
describes how to stop the U2000 server processes on a Windows single-server system.
13.2 Shutting Down the Database
The U2000 can start properly only after the database is started. Before shutting down the
database, stop the U2000 server processes. This topic describes how to shut down the
database on a Windows single-server system.
13.3 Powering Off the Server Safely
Before shutting down the U2000 server, stop the U2000 server processes and the database.
This topic describes how to power off the Windows single-server system safely.

13.1 Stopping the U2000 Server Processes

Do not stop the U2000 server processes when the U2000 server is managing NEs. Stop the
U2000 server processes only for some special purposes, for example, changing the system
time of the computer where the server is installed or upgrading the version. This topic
describes how to stop the U2000 server processes on a Windows single-server system.
Prerequisites
Exit all running U2000 clients.
Procedure

NOTE

----End
Result
In Windows Task Manager, click the Processes tab and check that there is no process such as
imapmrb.exe, imapwatchdog.exe, imapsysd.exe, imapeventmgr.exe,
imap_sysmonitor.exe, and ResourceMonitor.exe. So the U2000 server processes have been
stopped.
13.2 Shutting Down the Database

The U2000 can start properly only after the database is started. Before shutting down the
database, stop the U2000 server processes. This topic describes how to shut down the
database on a Windows single-server system.
Prerequisites
The U2000 server processes must have been stopped.

Procedure
Step 2 Perform the following operations to ensure that the SQL Server database has been stopped.
Stop is grayed out.
l If Stop is grayed out, the SQL Server database is stopped.

l If Stop is not grayed out, the SQL Server database is not stopped. Right-click SQL
Server (MSSQLSERVER) and choose Stop from the shortcut menu.
----End
Follow-up Procedure
Two methods are available for checking whether the SQL Server database can connect
normally.
1. Choose Start > Run.

2. In the Run dialog box, enter cmd. A command line interface (CLI) is displayed.
3. Run the following commands:
> isql -Usa -SDBSVR
NOTE

administrator user, the default prompt is C:\Users\Administrator>. You can run the
cd command to switch the directory. A command example is
. The command prompt switches to c:\>.
If the displayed information includes 1>, you can connect to the database normally, that is, the
database is started. Otherwise, the database is shut down.
13.3 Powering Off the Server Safely

Before shutting down the U2000 server, stop the U2000 server processes and the database.
This topic describes how to power off the Windows single-server system safely.
Prerequisites
l The U2000 server processes must have been stopped.
l The database must have been shut down.
Procedure
Step 2 Choose Start > Shut down to shut down the Windows OS.

Step 3 If a KVM is equipped, power off the KVM switcher.
----End

Commissioning Guide (Windows 7) 14 Glossary and Abbreviations
14 Glossary and Abbreviations
A
access control list A list of entities, together with their access rights, which are authorized to have access
to a resource.
access control right The level of right granted to a user for his access to certain items.
ACL See access control list
advanced telecom A platform that is used by the hardware of the N2510. To expand the system capacity
application smoothly, you only need to add certain boards to the shelf and need not replace the
environment server. This helps reduce the investments of the customer.
AIS See Alarm Indication Signal
Alarm A message reported when a fault is detected by a device or by the network
management system during the process of polling devices. Each alarm corresponds to
a recovery alarm. After a recovery alarm is received, the status of the corresponding
alarm changes to cleared.
alarm An operation performed on an alarm. Through this operation, the status of an alarm is
acknowledgement changed from unacknowledged to acknowledged, which indicates that the user starts
handling the alarm. The process during which when an alarm is generated, the
operator needs to acknowledge the alarm and take the right step to clear the alarm.
alarm correlation rule A process of analyzing the alarms that meet alarm correlation rules. If alarm 2 is
analyzing generated within 5 seconds after alarm 1 is generated and meets the alarm correlation
analysis rules, the EMS masks alarm 2 or improves its severity level according to the
alarm correlation rules.
alarm delay time The alarm delay time consists of the start delay time and the end delay time. When an
NE detects an alarm for a period, the period is the start delay time. When an NE
detects that the alarm disappears for a period, the period is the end delay time.
Unnecessary alarms that are caused by error reports or jitters can be avoided by setting
the delay time.

alarm indication On the cabinet of an NE, there are four indicators in different colors indicating the
current status of the NE. When the green indicator is on, it indicates that the NE is
powered on. When the red indicator is on, it indicates that a critical alarm is generated.
When the orange indicator is on, it indicates that a major alarm is generated. When the
yellow indicator is on, it indicates that a minor alarm is generated. The ALM alarm
indicator on the front panel of a board indicates the current status of the board. (Metro)
Alarm Indication A code sent downstream in a digital network as an indication that an upstream failure
Signal has been detected and alarmed. It is associated with multiple transport layers. Note:
See ITU-T Rec. G.707/Y.1322 for specific AIS signals.
alarm mask On the host, an alarm management method through which users can set conditions for
the system to discard (not to save, display, or query for) the alarm information meeting
the conditions.
alarm reporting to the On a device, an alarm is reported to the EMS at once after the alarm is generated. On
EMS immediately the EMS client, the corresponding alarm information is displayed on the alarm panel.
alarm severity The significance of a change in system performance or events. According to ITU-T
recommendations, an alarm can have one of the following severities:Critical, Major,
Minor, Warning.
alarm status The devices in the network report traps to the NMS, which displays the alarm statuses
in the topological view. The status of an alarm can be critical, major, minor and
prompt.
alarm synchronization When alarm synchronization is implemented, the EMS checks the alarm information
in its database and on the NEs. If the alarm information on the two locations is
inconsistent, the alarm information on the NEs is synchronized to the EMS database to
replace the original records.
ALC link A piece of end-to-end configuration information, which exists in the equipment
(single station) as an ALC link node. Through the ALC function of each node, it
fulfils optical power control on the line that contains the link.
ARP Proxy When a host sends an ARP request to another host, the request is processed by the
DSLAM connected to the two hosts. The process is called ARP proxy. This protocol
helps save the bandwidth in the networking of a low-rate WAN or helps implement the
layer 3 communication between access devices in the networking of layer 2 isolation.
Asynchronous A data transfer technology based on cell, in which packets allocation relies on channel
Transfer Mode demand. It supports fast packet switching to achieve efficient utilization of network
resources. The size of a cell is 53 bytes, which consist of 48-byte payload and 5-byte
header.
ATAE See advanced telecom application environment
ATM See Asynchronous Transfer Mode
Authority and Domain The function of the NMS for authority management. With this function, you can:
Based Management
1. Partition and control the management authority
2. Manage device nodes and service data by region
3. Allocate users with different management and operation rights for different
regions
auto-negotiation An optional function of the IEEE 802.3u Fast Ethernet standard that enables devices
to automatically exchange information over a link about speed and duplex abilities.

bandwidth A range of transmission frequencies that a transmission line or channel can carry in a
network. In fact, it is the difference between the highest and lowest frequencies the
transmission line or channel. The greater the bandwidth, the faster the data transfer
rate.
BASE A kind of bus or plane used to load software, transmit alarms and maintain
information exchange.
basic input/output A firmware stored in the computer mainboard. It contains basic input/output control
system programs, power-on self test (POST) programs, bootstraps, and system setting
information. The BIOS provides hardware setting and control functions for the
computer.
BFD See Bidirectional Forwarding Detection
Bidirectional A simple Hello protocol, similar to the adjacent detection in the route protocol. Two
Forwarding Detection systems periodically send BFD detection messages on the channel between the two
systems. If one system does not receive the detection message from the other system
for a long time, you can infer that the channel is faulty. Under some conditions, the
TX and RX rates between systems need to be negotiated to reduce traffic load.
BIOS See basic input/output system
board Board refers to an electronic part that can be plugged in to provide new capability. It
comprises chips and electronic components and these components are always on a flat
and hard base and connected through conductive paths. A board provides ports for
upstream connections or service provisioning.
Bond Bond: On the SUSE Linux OS, the bond technology is used to form a virtual layer
between the physical layer and the data link layer. This technology allows two server
NICs connecting to a switch to be bound to one IP address. The MAC addresses of the
two NICs are also automatically bound as one MAC address. In this manner, a virtual
NIC is formed. The bond technology supports two modes: double-live and primary/
secondary. In double-live mode, after receiving request data from a remote server, the
virtual NIC on the server determines data transmission based on an algorithm,
improving network throughput and usability of the server. In primary/secondary mode,
if an NIC does not function properly, services will be automatically switched to the
other NIC, ensuring service protection. The SUSE Linux OS supports the binding of
NICs in primary/secondary mode.
C/S See client/server software architecture

CAR See committed access rate
CAU See Client Auto Update
CDE See Common Desktop Environment
CIR See Committed Information Rate
client A device that sends requests, receives responses, and obtains services from the server.
Client Auto Update This function helps you to automatically detect the update of the client version and
upgrade the client. This keeps the version of the client is the same as that of the server.

Client/Server The model of interaction in a distributed system in which a program at one site sends a
request to a program at another site and awaits a response. The requesting program is
called a client. The program satisfying the request is called the server. It is usually
easier to build client software than build the server software.
client/server software A message-based and modular software architecture that comprises servers and
architecture clients. Compared with the centralized, mainframe, and time sharing computing, the
client/server software architecture improves the usability, flexibility, interoperability,
and scalability. In this architecture, a client is defined as the party that requires
services and a server is defined as the party that provides services. The client/server
architecture reduces network traffic by providing a query response rather than
transferring all files.
cluster A mechanism adopted to improve the system performance. Several devices of the
same type form a cluster. The exterior of a cluster is some like a kind of equipment. In
the interior of a cluster, the nodes share the load.
committed access rate A traffic control method that uses a set of rate limits to be applied to a router interface.
CAR is a configurable method by which incoming and outgoing packets can be
classified into QoS (Quality of Service) groups, and by which the input or output
transmission rate can be defined.
Committed The rate at which a frame relay network agrees to transfer information in normal
Information Rate conditions. Namely, it is the rate, measured in bit/s, at which the token is transferred to
the leaky bucket.
Common Desktop The Common Desktop Environment (CDE) is an integrated graphical user interface
Environment for open systems desktop computing. It delivers a single, standard graphical interface
for the management of data and files (the graphical desktop) and applications. CDE's
primary benefits -- deriving from ease-of-use, consistency, configurability, portability,
distributed design, and protection of investment in today's applications -- make open
systems desktop computers as easy to use as PCs, but with the added power of local
and network resources available at the click of a mouse.
Common Object A specification developed by the Object Management Group in 1992 in which pieces
Request Broker of programs (objects) communicate with other objects in other programs, even if the
Architecture two programs are written in different programming languages and are running on
different platforms. A program makes its request for objects through an object request
broker, or ORB, and thus does not need to know the structure of the program from
which the object comes. CORBA is designed to work in object-oriented environments.
See also IIOP, object (definition 2), Object Management Group, object-oriented.
Common Object A specification developed by the Object Management Group in 1992 in which pieces
Request Broker of programs (objects) communicate with other objects in other programs, even if the
Architecture two programs are written in different programming languages and are running on
different platforms. A program makes its request for objects through an object request
broker, or ORB, and thus does not need to know the structure of the program from
which the object comes. CORBA is designed to work in object-oriented environments.
See also IIOP, object (definition 2), Object Management Group, object-oriented.
CORBA See Common Object Request Broker Architecture
CORBA See Common Object Request Broker Architecture

D
Data Communication Data Communications Channel. The data channel that uses the D1-D12 bytes in the
Channel overhead of an STM-N signal to transmit information on operation, management,
maintenance and provision (OAM&P) between NEs. The DCC channels that are
composed of bytes D1-D3 is referred to as the 192 kbit/s DCC-R channel. The other
DCC channel that are composed of bytes D4-D12 is referred to as the 576 kbit/s DCC-
M channel.
data communication A communication network used in a TMN or between TMNs to support the data
network communication function.
data replication link A link used for data replication between the production machine and redundancy
machine. It is separated from the network of the primary links.
DCC See Data Communication Channel
DCN See data communication network
DDN See digital data network
Delay An average time taken by the service data to transmit across the network.
DG disk group
DHCP See Dynamic Host Configuration Protocol
digital data network A high-quality data transport tunnel that combines the digital channel (such as fiber
channel, digital microwave channel, or satellite channel) and the cross multiplex
technology.
disk mirroring A technique in which all or part of a hard disk is duplicated onto one or more other
hard disks, each of which ideally is attached to its own controller. With disk mirroring,
any change made to the original disk is simultaneously made to the other disks so that
if the original disk becomes damaged or corrupted, the mirror disks will contain a
current, undamaged collection of the data from the original disk.
Dynamic Host A client-server networking protocol. A DHCP server provides configuration
Configuration Protocol parameters specific to the DHCP client host requesting, generally, information
required by the host to participate on the Internet network. DHCP also provides a
mechanism for allocation of IP addresses to hosts.
E
E1 A European standard for high-speed data transmission at 2.048 Mbit/s. It provides 32
x 64 kbit/s channels.
ECC See embedded control channel
embedded control A logical channel that uses a data communications channel (DCC) as its physical
channel layer, to enable transmission of operation, administration, and maintenance (OAM)
information between NEs.
Equipment Serial A 32-bit number assigned by the mobile station manufacturer, uniquely identifying the
Number mobile station equipment.
ESN See Equipment Serial Number

F
Fabric A kind of bus/plane used to exchange system service data.
File Transfer Protocol A member of the TCP/IP suite of protocols, used to copy files between two computers
on the Internet. Both computers must support their respective FTP roles: one must be
an FTP client and the other an FTP server.
FTP See File Transfer Protocol
G
gateway A device to connect two network segments which use different protocols. It is used to
translate the data in the two network segments.
gateway network A network element that is used for communication between the NE application layer
element and the NM application layer
GE The IEEE standard dubbed 802.3z, which includes support for transmission rates of1
Gbps (gigabit per second)--1,000 Mbps (megabits per second)--over an Ethernet
network.
GMT See Greenwich Mean Time
GNE See gateway network element
graphical user A visual computer environment that represents programs, files, and options with
interface graphical images, such as icons, menus, and dialog boxes, on the screen.
Greenwich Mean Time The mean solar time at the Royal Greenwich Observatory in Greenwich near London
in England, which by convention is at 0 degrees geographic longitude.
GUI See graphical user interface
H
HA See High Availability
HA system See high availability system
half-duplex A transmitting mode in which a half-duplex system provides for communication in
both directions, but only one direction at a time (not simultaneously). Typically, once a
party begins receiving a signal, it must wait for the transmitter to stop transmitting,
before replying.
High Availability The ability of a system to continuously perform its functions during a long period,
which may exceeds the suggested working time of the independent components. You
can obtain the high availability (HA) by using the error tolerance method. Based on
learning cases one by one, you must also clearly understand the limitations of the
system that requires an HA ability and the degree to which the ability can reach.
high availability The high availability system (HA) system indicates that two servers are adopted by a
system same computer. When the primary server is faulty, the secondary server provides the
environment on which the software runs through the related technology.
History alarm The confirmed alarms that have been saved in the memory and other external
memories.

host The computer system that is connected with disks, disk subsystems, or file servers and
on which data is stored and I/Os are accessed. A host can be a large computer, server,
workstation, PC, multiprocessor computer, and computer cluster system.
I
IANA See Internet assigned numbers authority
ICA See independent computing architecture
ICMP See Internet Control Message Protocol
IE See Internet Explorer
IEEE See Institute of Electrical and Electronics Engineers
iMAP See integrated management application platform
independent An architecture that logically separates application execution from user interfaces to
computing transmit only keyboard actions, mouse responses, and screen updates on the network.
architecture
Institute of Electrical A society of engineering and electronics professionals based in the United States but
and Electronics boasting membership from numerous other countries. The IEEE focuses on electrical,
Engineers electronics, computer engineering, and science-related matters.
integrated N/A
management
application platform
International Standard One of two international standards bodies responsible for developing international
Organization data communications standards. International Organization for Standardization (ISO)
works closely with the International Electro- technical Commission (IEC) to define
standards of computing. They jointly published the ISO/IEC SQL-92 standard for
SQL.
International An organization that establishes recommendations and coordinates the development of
Telecommunication telecommunication standards for the entire world.
Union
Telecommunication
Standardization
Internet assigned The organization operated under the IAB. IANA delegates authority for IP address-
numbers authority space allocation and domain-name assignment to the NIC and other organizations.
IANA also maintains a database of assigned protocol identifiers used in the TCP/IP
suite, including autonomous system numbers.
Internet Control A network-layer (ISO/OSI level 3) Internet protocol that provides error correction and
Message Protocol other information relevant to IP packet processing. For example, it can let the IP
software on one machine inform another machine about an unreachable destination.
See also communications protocol, IP, ISO/OSI reference model, packet (definition 1).
Internet Explorer Microsoft's Web browsing software. Introduced in October 1995, the latest versions of
Internet Explorer include many features that allow you to customize your experience
on the Web. Internet Explorer is also available for the Macintosh and UNIX platforms.

Internet Protocol The TCP/IP standard protocol that defines the IP packet as the unit of information sent
across an Internet and provides the basis for connectionless, best-effort packet delivery
service. IP includes the ICMP control and error message protocol as an integral part.
The entire protocol suite is often referred to as TCP/IP because TCP and IP are the
two fundamental protocols. IP is standardized in RFC 791.
Internet Protocol A update version of IPv4. It is also called IP Next Generation (IPng). The
Version 6 specifications and standardizations provided by it are consistent with the Internet
Engineering Task Force (IETF).Internet Protocol Version 6 (IPv6) is also called. It is a
new version of the Internet Protocol, designed as the successor to IPv4. The
specifications and standardizations provided by it are consistent with the Internet
Engineering Task Force (IETF).The difference between IPv6 and IPv4 is that an IPv4
address has 32 bits while an IPv6 address has 128 bits.
inventory A physical inventory in the U2000, that is, a physical resource such as a
telecommunications room, rack, NE, subrack, board, subboard, port, optical module,
fiber/cable, fiber and cable pipe, link resource, interface resource, access service,
ONU, or NE e-label that can be managed on the U2000, and the relationship between
resources.
IP See Internet Protocol
IPv4 The abbreviation of Internet Protocol version 4. IPv4 utilizes a 32bit address which is
assigned to hosts. An address belongs to one of five classes (A, B, C, D, or E) and is
written as 4 octets separated by periods and may range from 0.0.0.0 through to
255.255.255.255. Each address consists of a network number, an optional subnetwork
number, and a host number. The network and subnetwork numbers together are used
for routing, and the host number is used to address an individual host within the
network or subnetwork. IPv4 addresses may also be represented using CIDR
(Classless Inter Domain Routing).
IPv6 See Internet Protocol Version 6
ISO See International Standard Organization
ITU-T See International Telecommunication Union Telecommunication Standardization
J
Java Virtual Machine The environment in which Java programs run. The Java Virtual Machine gives Java
programs a software-based computer they can interact with. Because the Java Virtual
Machine is not a real computer but exists in software, a Java program can run on any
physical computing platform.
JRE Java runtime environment
JVM See Java Virtual Machine
K
keyboard, video, and A hardware device installed in the integrated configuration cabinet. KVM serves as
mouse the input and output device for the components inside the cabinet. It consists of a
screen, a keyboard, and a mouse.
KVM See keyboard, video, and mouse

L
LAN See Local Area Network
LCT See Local Craft Terminal
LDAP See Lightweight Directory Access Protocol
License A permission that the vendor provides for the user with a specific function, capacity,
and durability of a product. A license can be a file or a serial number. Usually the
license consists of encrypted codes, and the operation authority varies with different
level of license.
Lightweight Directory An TCP/IP based network protocol that enables access to a DSA. It involves some
Access Protocol reduced functionality from X.500 DAP specification.
Link Layer Discovery The Link Layer Discovery Protocol (LLDP) is an L2D protocol defined in IEEE
Protocol 802.1ab. Using the LLDP, the NMS can rapidly obtain the Layer 2 network topology
and changes in topology when the network scales expand.
LLDP See Link Layer Discovery Protocol
load balancing The distribution of activity across two or more servers or components in order to
avoid overloading any one with too many requests or too much traffic.
Local Area Network A network formed by the computers and workstations within the coverage of a few
square kilometers or within a single building. It features high speed and low error rate.
Ethernet, FDDI, and Token Ring are three technologies used to implement a LAN.
Current LANs are generally based on switched Ethernet or Wi-Fi technology and
running at 1,000 Mbit/s (that is, 1 Gbit/s).
Local Craft Terminal Local Craft Terminal. The terminal software that is used for local maintenance and the
management of NEs in the singer-user mode, to realize integrated management of
multi-service transmission network. See also U2000.
M
MAN See Metropolitan Area Network
MD5 See Message-Digest Algorithm 5
MDP See message dispatch process
message dispatch N/A
process
Message-Digest A one-way hashing algorithm that produces a 128-bit hash. Both MD5 and Secure
Algorithm 5 Hash Algorithm (SHA) are variations on MD4 and are designed to strengthen the
security of the MD5 hashing algorithm.
Metropolitan Area A metropolitan area network (MAN) is a network that interconnects users with
Network computer resources in a geographic area or region larger than that covered by even a
large local area network (LAN) but smaller than the area covered by a wide area
network (WAN). The term is applied to the interconnection of networks in a city into a
single larger network (which may then also offer efficient connection to a wide area
network). It is also used to mean the interconnection of several local area networks by
bridging them with backbone lines. The latter usage is also sometimes referred to as a
campus network.

modem A device or program that enables a computer to transmit data over, for example,
telephone or cable lines. Computer information is stored digitally, whereas
information transmitted over telephone lines is transmitted in the form of analog
waves. A modem converts between these two forms.
MS Manual Switch
MSTP See multi-service transmission platform
MSuite NMS maintenance suite
multi-service A platform based on the SDH platform, capable of accessing, processing and
transmission platform transmitting TDM services, ATM services, and Ethernet services, and providing
unified management of these services.
N
NBI See northbound interface
NE See network element
network element A network element (NE) contains both the hardware and the software running on it.
One NE is at least equipped with one system control board which manages and
monitors the entire network element. The NE software runs on the system control
board.
network layer The network layer is layer 3 of the seven-layer OSI model of computer networking.
The network layer provides routing and addressing so that two terminal systems are
interconnected. In addition, the network layer provides congestion control and traffic
control. In the TCP/IP protocol suite, the functions of the network layer are specified
and implemented by IP protocols. Therefore, the network layer is also called IP layer.
Network Management A system in charge of the operation, administration, and maintenance of a network.
System
Network Time The Network Time Protocol (NTP) defines the time synchronization mechanism. It
Protocol synchronizes the time between the distributed time server and the client.
new technology file An advanced file system designed for use specifically with the Windows NT operating
system system. It supports long filenames, full security access control, file system recovery,
extremely large storage media, and various features for the Windows NT POSIX
subsystem. It also supports object-oriented applications by treating all files as objects
with user-defined and system-defined attributes.
NMS See Network Management System
northbound interface The interface that connects to the upper-layer device to realize service provisioning,
report alarms and performance statistics.
NTFS See new technology file system
NTP See Network Time Protocol
O
OAM See operation, administration and maintenance

Object Set A collection of managed objects. Object sets are established to facilitate the user right
management. If a user (or user group) is authorized with the operation rights of an
object set, the user (or user group) can perform all the authorized operations on all the
objects within the object set. This saves you the trouble of setting the management
rights for each NE one by one. Object sets can be created by geographical area,
network layer, equipment type and so on.
OMC See Operation and Maintenance Center
ONU See Optical Network Unit
Operation and An Operations and Maintenance Centre is an element within a network management
Maintenance Center system responsible for the operations and maintenance of a specific element or group
of elements. For example an OMC-Radio may be responsible for the management of a
radio subsystem where as an OMC-Switch may be responsible for the management of
a switch or exchange. However, these will in turn be under the control of a NMC
(Network Management Centre) which controls the entire network.
Operation Rights Operation Rights specify the concrete operation that the user can perform. The
operation right aims at the security objects. If one user has no right to manage one
device, he or she cannot operate the device.
Operation Set A collection of operations. Classifying operations into operation sets helps to manage
user operation rights. Operations performed by different users have different impacts
on system security. Operations with similar impacts are classified into an operation
set. Users or user groups entitled to an operation set can perform all the operations in
the operation set. The NMS provides some default operation sets. If the default
operation sets cannot meet the requirements for right allocation, users can create
operation sets as required.
Operation System Operation System is abbreviated to OS. OS is the interface between users and
computers. It manages all the system resources of the computer, and also provides an
abstract computer for users. With the help of OS, users can use the computers without
any direct operation on hardware. For the computer system, OS is a set of programs
used to manage all system resources; for users, OS provides a simple and abstract
method to use the system resources.
operation, A group of network support functions that monitor and sustain segment operation,
administration and activities that are concerned with, but not limited to, failure detection, notification,
maintenance location, and repairs that are intended to eliminate faults and keep a segment in an
operational state and support activities required to provide the services of a subscriber
access network to users/subscribers.
Operations Support A system whose main function is to run applications that manage network elements,
System networks and services.
Optical Network Unit A form of Access Node that converts optical signals transmitted via fiber to electrical
signals that can be transmitted via coaxial cable or twisted pair copper wiring to
individual subscribers.
OS See Operation System
OSS See Operations Support System
P
packet loss ratio The ratio of total lost packet outcomes to total transmitted packets in a population of
interest.

packet transport N/A

network
PC See Personal Computer
Peak Information Rate Peak Information Rate . A traffic parameter, expressed in bit/s, whose value should be
not less than the committed information rate.
Personal Computer A computer used by an individual at a time in a business, a school, or at home.
PIR See Peak Information Rate
PMU The unit that is used to monitor power supply in the equipment.
Point-to-Point Protocol PPPoE, point-to-point protocol over Ethernet, is a network protocol for encapsulating
over Ethernet PPP frames in Ethernet frames. It is used mainly with DSL services. It offers standard
PPP features such as authentication, encryption, and compression.
port 1. Of a device or network, a point of access where signals may be inserted or
extracted, or where the device or network variables may be observed or
measured. (188)
2. In a communications network, a point at which signals can enter or leave the
network en
Power and The power and environment monitoring unit is installed at the top of the cabinet of the
environment SDH equipment and is used to monitor the environment variables, such as the power
monitoring unit supply and temperature. With external signal input through the relay, fire alarm,
smoke alarm, burglary alarm, etc. can be monitored as well. With the display on NMS
system, the change of environment can be monitored timely and accurately. For the
equipment installed with a power & environment monitoring board, the following
parameters can be set: relay switch output control, temperature alarm threshold, relay
usage and alarm setting, query of DIP switch status, etc.
PPPoE See Point-to-Point Protocol over Ethernet
private network A network which provides services to a specific set of users only (see
Recommendation I.570).
PSTN See public switched telephone network
PTN See packet transport network
public switched Public Switched Telephone Network. A telecommunications network established to
telephone network perform telephone services for the public subscribers.Sometimes called POTS.
R
RADIUS See remote authentication dial-in user service
RADIUS See Remote Authentication Dial in User Service
RAID See Redundant Arrays of Independent Disks

Redundant Arrays of A data storage scheme that allows data to be stored and replicated in a hardware disk
Independent Disks group (logical hard disk) consisting of multiple hard disks (physical hard disks). When
multiple physical disks are set up to use the RAID technique, they are said to be in a
RAID array. The hard disks in a RAID array provides higher data reliability and input/
output performance. There are various defined levels of RAID, each offering differing
trade-offs among access speed, reliability, and cost. At present, there are seven basic
RAID levels from RAID 0 to RAID 6. These basic RAID levels can be further
combined to form new RAID levels, such as RAID 10 (a combination of RAID 0 and
RAID 1).
Remote Authentication RADIUS was originally used to manage the scattered users who use the serial
Dial in User Service interface and modem, and it has been widely used in NAS. NAS delivers the
information of users on authentication, authorization and accounting to the RADIUS
server. RADIUS stipulates how the user and accounting information is transferred
between NAS and RADIUS. The RADIUS server is responsible for receiving the
connection request from users to complete authentication, and returning the
configurations of the users to NAS.
remote authentication A security service that authenticates and authorizes dial-up users and is a centralized
dial-in user service access control mechanism. RADIUS uses the User Datagram Protocol (UDP) as its
transmission protocol to ensure real-time quality. RADIUS also supports the
retransmission and multi-server mechanisms to ensure good reliability.
replicated volume N/A
group
replication link A link used for data replication between the production machine and redundancy
machine. It is physically separated from the network of the primary links.
Rlink See data replication link
RTN Radio Transmission Node
RVG See replicated volume group
S
Script file It is the text file describing the physical information and configuration information of
the entire network, including the NE configuration file, port naming file, end-to-end
configuration file, NE physical view script file, NMS information file and service
implementation data script file.
SDH See Synchronous Digital Hierarchy
Secure File Transfer A network protocol designed to provide secure file transfer over SSH.
Protocol (SFTP)
Secure Shell (SSH) A set of standards and an associated network protocol that allows establishing a secure
channel between a local and a remote computer. A feature to protect information and
provide powerful authentication function for a network when a user logs in to the
network through an insecure network. It prevents IP addresses from being deceived
and plain text passwords from being captured.
Secure Sockets Layer A protocol for ensuring security and privacy in Internet communications. SSL
supports authentication of client, server, or both, as well as encryption during a
communications session.

Security Log Security logs record the security operations on the NMS, such as logging in to the
server, modifying the password, and exiting from the NMS server.
Serial Line Interface Serial Line Interface Protocol, defines the framing mode over the serial line to
Protocol implement transmission of messages over the serial line and provide the remote host
interconnection function with a known IP address.
server 1. On a local area network, a computer running administrative software that
controls access to the network and its resources, such as printers and disk drives,
and provides resources to computers functioning as workstations on the network.
2. On the Internet or other network, a computer or program that responds to
commands from a client. For example, a file server may contain an archive of
data or program files; when a client submits a request for a file, the server
transfers a copy of the file to the client.
3. A network device that provides services to network users by managing shared
resources, often used in the context of a client-server architecture for a LAN.
SFTP See Secure File Transfer Protocol (SFTP)

SSH See Secure Shell (SSH)
shelf management The shelf management board of the ATAE server.
module
Signal Noise Ratio The SNR or S/N (Signal to Noise Ratio) of the amplitude of the desired signal to the
amplitude of noise signals at a given point in time. SNR is expressed as 10 times the
logarithm of the power ratio and is usually expressed in dB (Decibel).
Signal to Noise Ratio The signal-to-noise ratio margin represents the amount of increased received noise (in
Margin dB) relative to the noise power that the system is designed to tolerate and still meet the
target BER of accounting for all coding gains included in the design.
Simple Mail Transfer The TCP/IP (Transmission Control Protocol/Internet Protocol) protocol which
Protocol facilitates the transfer of electronic-mail messages, specifies how two systems are to
interact, and the format of messages used to control the transfer of electronic mail.
Simple Network A network management protocol of TCP/IP. It enables remote users to view and
Management Protocol modify the management information of a network element. This protocol ensures the
transmission of management information between any two points. The polling
mechanism is adopted to provide basic function sets. According to SNMP, agents,
which can be hardware as well as software, can monitor the activities of various
devices on the network and report these activities to the network console workstation.
Control information about each device is maintained by a management information
block.
Simple Network Time A protocol that is adapted from the Network Time Protocol (NTP) and synchronizes
Protocol the clocks of computers over the Internet.
SLIP See Serial Line Interface Protocol
SMM See shelf management module
SMTP See Simple Mail Transfer Protocol
SNMP See Simple Network Management Protocol
SNR See Signal Noise Ratio
SNRM See Signal to Noise Ratio Margin

SNTP See Simple Network Time Protocol

SONET See Synchronous Optical Network
SQL See structured query language
SSL See Secure Sockets Layer
static route A route that cannot adapt to the change of network topology. Operators must configure
it manually. When a network topology is simple, the network can work in the normal
state if only the static route is configured. It can improve network performance and
ensure bandwidth for important applications. Its disadvantage is as follows: When a
network is faulty or the topology changes, the static route does not change
automatically. It must be changed by the operators.
Stelnet Secure Shell Telnet
structured query A database query and programming language widely used for accessing, querying,
language updating, and managing data in relational database systems.
SVM Solaris Volume Manager
Switching restoration It refers to the period of time between the start of detecting and the moment when the
time line is switched back to the original status after protection switching occurs in the
MSP sub-network.
Synchronous Digital SDH is a transmission scheme that follows ITU-T G.707, G.708, and G.709. It defines
Hierarchy the transmission features of digital signals such as frame structure, multiplexing mode,
transmission rate level, and interface code. SDH is an important part of ISDN and B-
ISDN. It interleaves the bytes of low-speed signals to multiplex the signals to high-
speed counterparts, and the line coding of scrambling is only used only for signals.
SDH is suitable for the fiber communication system with high speed and a large
capacity since it uses synchronous multiplexing and flexible mapping structure.
Synchronous Optical Synchronous Optical Network, is a method for communicating digital information
Network using lasers or light-emitting diodes (LEDs) over optical fiber. The method was
developed to replace the Plesiochronous Digital Hierarchy (PDH) system for
transporting large amounts of telephone and data traffic and to allow for
interoperability between equipment from different vendors. SONET defines interface
standards at the physical layer of the OSI seven-layer model. The standard defines a
hierarchy of interface rates that allow data streams at different rates to be multiplexed.
SONET establishes Optical Carrier (OC) levels from 51.8 Mbps (OC-1) to 9.95 Gbps
(OC-192).
SYSLOG Syslog is an industry standard protocol for recording device logs.
T
TCP See Transmission Control Protocol
TCP/IP See Transmission Control Protocol/Internet Protocol
Telecommunication The Telecommunications Management Network is a protocol model defined by ITU-T
Management Network for managing open systems in a communications network.An architecture for
management, including planning, provisioning, installation, maintenance, operation
and administration of telecommunications equipment, networks and services.

Telnet Standard terminal emulation protocol in the TCP/IP protocol stack. Telnet is used for
remote terminal connection, enabling users to log in to remote systems and use
resources as if they were connected to a local system. Telnet is defined in RFC 854.
TFTP See Trivial File Transfer Protocol
Time zone A division of the earth's surface, usually extending across 15 degrees of longitude
devised such that the standard time is the time at a meridian at the centre of the zone.
timing task The system can create a timing task (such as backing up, loading and recovering a
management task), run a timing task automatically, and suspend or resume a timing task.
TMN See Telecommunication Management Network
Transmission Control One of the core protocols of the Internet protocol suite. Using TCP, applications on
Protocol networked hosts can create connections to one another, over which they can exchange
streams of data. TCP guarantees reliable and in-order delivery of data from the sender
to the receiver. TCP also distinguishes data for multiple connections by concurrent
applications running on the same host.
Transmission Control Common name for the suite of protocols developed to support the construction of
Protocol/Internet worldwide internetworks.
Protocol
Trivial File Transfer A small and simple alternative to FTP for transferring files. TFTP is intended for
Protocol applications that do not need complex interactions between the client and server.
TFTP restricts operations to simple file transfers and does not provide authentication.
TFTP is small enough to be contained in ROM to be used for bootstrapping diskless
machines.
U
UDP See User Datagram Protocol
UPS Uninterruptible Power Supply
User Datagram A TCP/IP standard protocol that allows an application program on one device to send
Protocol a datagram to an application program on another. User Datagram Protocol (UDP) uses
IP to deliver datagrams. UDP provides application programs with the unreliable
connectionless packet delivery service. Thus, UDP messages can be lost, duplicated,
delayed, or delivered out of order. UDP is used to try to transmit the data packet, that
is, the destination device does not actively confirm whether the correct data packet is
received.
V
VCS See Veritas Cluster Server
Veritas Cluster Server A High-availability cluster software, for Unix, Linux and Microsoft Windows
computer systems, created by Veritas Software. It provides application cluster
capabilities to systems running Databases, file sharing on a network, electronic
commerce websites or other applications.
Veritas Volume A software product from veritas Inc.. The Veritas Volume Manager is used to manage
Manager disk storage.
Veritas Volume A wide area network data replication solution offered by VERITAS for multiple
Replicator operating systems. These include. AIX, HPUX and Solaris .

Virtual Local Area A logical grouping of two or more nodes which are not necessarily on the same
Network physical network segment but which share the same IP network number. This is often
associated with switched Ethernet.
Virtual Router A protocol used for multicast or multicast LANs such as an Ethernet. A group of
Redundancy Protocol routers (including an active router and several backup routers) in a LAN is regarded as
a virtual router, which is called a backup group. The virtual router has its own IP
address. The host in the network communicates with other networks through this
virtual router. If the active router in the backup group fails, one of the backup routers
become the active one and provides routing service for the host in the network.
VLAN See Virtual Local Area Network
volume A logical unit for disk virtualization management, and basic object for host
applications.
VRRP See Virtual Router Redundancy Protocol
VVM See Veritas Volume Manager
W
WAN See Wide Area Network
wavelength division A technology that utilizes the characteristics of broad bandwidth and low attenuation
multiplexing of single mode optical fiber, uses multiple wavelengths as carriers, and allows
multiple channels to transmit simultaneously in a single fiber.
WDM See wavelength division multiplexing
Wide Area Network A network composed of computers which are far away from each other which are
physically connected through specific protocols. WAN covers a broad area, such as a
province, a state or even a country.
Wireless Local Area A generic term covering a multitude of technologies providing local area networking
Network via a radio link. Examples of WLAN technologies include WiFi (Wireless Fidelity),
802.11b and 802.11a, HiperLAN, Bluetooth, etc.
WLAN See Wireless Local Area Network
work station A terminal or microcomputer, usually one that is connected to a mainframe or to a
network, at which a user can perform applications.
WS See work station


Imanager U2000 V200R016C50 Single-Server System Software Installation and Commissioning Guide (Windows 7) 05 PDF

Uploaded by

Copyright:

Available Formats

Imanager U2000 V200R016C50 Single-Server System Software Installation and Commissioning Guide (Windows 7) 05 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Imanager U2000 V200R016C50 Single-Server System Software Installation and Commissioning Guide (Windows 7) 05 PDF

Uploaded by

Copyright:

Available Formats

iManager U2000 Unified Network Management

Single-Server System Software

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential i

About This Document

Product Name Version

iManager U2000 V200R016C50

This document is intended for:

l Technical support engineers

Indicates an imminently hazardous situation

Indicates a potentially hazardous situation

Indicates a potentially hazardous situation

Issue 05 (2017-08-30) Huawei Proprietary and Confidential ii

Indicates a potentially hazardous situation

Calls attention to important information,

Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

[] Items (keywords or arguments) in brackets [ ] are optional.

{ x | y | ... } Optional items are grouped in braces and separated by

[ x | y | ... ] Optional items are grouped in brackets and separated by

{ x | y | ... }* Optional items are grouped in braces and separated by

[ x | y | ... ]* Optional items are grouped in brackets and separated by

Boldface Buttons, menus, parameters, tabs, window, and dialog titles

Issue 05 (2017-08-30) Huawei Proprietary and Confidential iii

> Multi-level menus are in boldface and separated by the ">"

Changes in Issue 05 (2017-08-30) Based on Product Version V200R016C50

Changes in Issue 04 (2016-12-25) Based on Product Version V200R016C50

Changes in Issue 03 (2016-09-30) Based on Product Version V200R016C50

Changes in Issue 02 (2016-07-28) Based on Product Version V200R016C50

Changes in Issue 01 (2016-04-30) Based on Product Version V200R016C50

Issue 05 (2017-08-30) Huawei Proprietary and Confidential iv

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

8 Commissioning the U2000......................................................................................................... 38

Issue 05 (2017-08-30) Huawei Proprietary and Confidential v

9.1 Windows OS................................................................................................................................................................. 83

Issue 05 (2017-08-30) Huawei Proprietary and Confidential vi

10 Uninstalling the U2000 Server.............................................................................................. 117

11 Manual Commissioning Task............................................................................................... 121

12 Starting the U2000 Server in a Windows Single-Server System.................................... 127

13 Powering Off the System....................................................................................................... 131

14 Glossary and Abbreviations..................................................................................................135

Issue 05 (2017-08-30) Huawei Proprietary and Confidential vii

This topic describes the performance indicators of the U2000.

Table 1-1 Performance indicators

Database restoration time ≤ 60 minutes

Storage capacity Capacity of current alarms Maximum: 10000

Capacity of historical alarms Maximum: 100000

Capacity of logs, including Maximum: 50000

Link capacity Number of manageable Maximum: 500

Processing capability Response speed of handling Usually equal to or less than

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 1

Item Subitem Indicator

Performance collection Maximum performance

Alarm handling capability 10 alarms per second.

Concurrent NE upgrades Maximum: 20

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 2

2 U2000 Management Capability