U31 V12!11!40 SoftwareInstallationGuide en

NetNumen U31 R22
Unified Network Management System
Software Installation Guide

Product Version: V12.11.40
ZTE CORPORATION
NO. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright 2011 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited.
Additionally, the contents of this document are protected by
contractual confidentiality obligations.

All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided as is, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No.
Revision Data
Revision Reason
R1.0
2012-01-10
NetNumen U31 R22 (V12.11.40) Issued
Serial Number: SJ-20111118090716-003

Publishing Date: 2012-01-10 (R1.0)
About This Manual

Purpose
This manual is applicable to NetNumen U31 R22(V12.11.40) Unified Network
Management System (hereinafter referred to U31 R22).
U31 R22 is a network-level network management system based on the distributed,
multi-process and modular design. It can exercise unified management over the CTN,
SDH, WDM/OTN, Router, BAS and Switch series of optical transmission equipment from
ZTE.
Introduction
This manual is NetNumen U31 R22 (V12.11.40) Unified Network Management System
Software Installation Guide. It contains the following contents:
Chapter
Summary
1, Installing U31 R22
Describes how to install the U31 R22 server and U31 R22 client.
2, Starting and Quitting U31 R22
Describes how to start up and shut down U31 R22 server, and
how to log in to or exit U31 R22 client.
3, Uninstalling U31 R22
Describes how to uninstalling the U31 R22 server and U31 R22
client.
Intended Audience
This manual is intended for:
l
l
l
Planning Engineers
U31 R22 Monitoring Personnel
Maintenance Engineers
Conventions
The following safety signs may appear in this manual.
Safety Sign
Meaning
A serious accident, such as casualties or equipment damage may
Danger
occur if you ignore this safety warning.

A major accident, such as casualties or equipment damage may oc-
Warning
cur if you ignore this safety warning.

Equipment damage, data loss, degradation of equipment perfor-
Caution
mance, or other unpredictable result may occur if you ignore this

safety warning.
I
Safety Sign
Meaning
Provides additional information about a topic.

Note
Indicates a suggestion or hint to make things easier or more producTip
tive.
II
Table of Contents
About This Manual ......................................................................................... I
Chapter 1 Installing the U31 R22............................................................... 1-1
1.1 Software Installation Flow ................................................................................... 1-1
1.2 Installing the U31 R22 On the Windows OS ......................................................... 1-2
1.2.1 Installing the U31 R22 Server and Client.................................................... 1-2
1.2.2 Installing the U31 R22 Client ................................................................... 1-13
1.3 Installing the U31 R22 On the Solaris OS........................................................... 1-19
1.3.1 Installation Instructions ........................................................................... 1-19
1.3.2 Server Configuration............................................................................... 1-20
1.3.3 Preparation Before Installation ................................................................ 1-23
1.3.4 Installing the U31 R22 Server.................................................................. 1-27
1.3.5 Installing Licenses .................................................................................. 1-33
1.4 Installing the U31 R22 On the Linux OS............................................................. 1-33
1.4.1 Installation Instruction ............................................................................. 1-33
1.4.2 Configuration Requirement for the Server ................................................ 1-34
1.4.3 Preparation Before Installation ................................................................ 1-36
1.4.4 Installing the U31 R22 Server.................................................................. 1-37
1.4.5 Installing License.................................................................................... 1-45
Chapter 2 Starting and Exiting the U31 R22 ............................................ 2-1

2.1 Starting and exiting the U31 R22 On the Windows OS.......................................... 2-1
2.1.1 Starting the U31 R22 Server ..................................................................... 2-1
2.1.2 Logging in to the U31 R22 Client ............................................................... 2-1
2.1.3 Exiting the U31 R22 Client ........................................................................ 2-2
2.1.4 Exiting the U31 R22 Server....................................................................... 2-3
2.2 Starting and exiting the U31 R22 On the Solaris OS ............................................. 2-4
2.2.2 Exiting the U31 R22 Server....................................................................... 2-4
2.3 Starting and exiting the U31 R22 On the Linux OS ............................................... 2-5
2.3.2 Quitting the U31 R22 Server ..................................................................... 2-6
Chapter 3 Uninstalling the U31 R22.......................................................... 3-1

3.1 Uninstalling the U31 R22 On the Windows OS ..................................................... 3-1
3.1.1 Uninstalling the U31 R22 Server and Client................................................ 3-1
3.1.2 Uninstalling the U31 R22 Client................................................................. 3-2

3.2 Uninstalling the U31 R22 On the Solaris OS ........................................................ 3-3
3.2.1 Uninstalling the U31 R22 Server Software ................................................. 3-3
3.3 Uninstalling the U31 R22 On the Linux OS........................................................... 3-4
3.3.1 Uninstalling the U31 R22 Server Software ................................................. 3-4
Figures............................................................................................................. I
Tables ............................................................................................................ III
Glossary .........................................................................................................V
II
Chapter 1
Installing the U31 R22

Table of Contents
Software Installation Flow...........................................................................................1-1
Installing the U31 R22 On the Windows OS ...............................................................1-2
Installing the U31 R22 On the Solaris OS .................................................................1-19
Installing the U31 R22 On the Linux OS ...................................................................1-33
1.1 Software Installation Flow

The software installation flow of the U31 R22 system is shown in Figure 1-1.
Figure 1-1 Software Installation Flow of the U31 R22 System
The software installation of the U31 R22 system includes two parts: software installation
on the server, and software installation on the client.
l
l
On the server, install the operating system, database, and U31 R22 server software.
On the client, install the operating system and the U31 R22 client software.
1-1
SJ-20111118090716-003|2012-01-10 (R1.0)
ZTE Proprietary and Confidential
NetNumen U31 R22 Software Installation Guide
1.2 Installing the U31 R22 On the Windows OS

1.2.1 Installing the U31 R22 Server and Client
1.2.1.1 Hardware Configuration Requirement for the U31 R22 Server
On the Windows OS, the hardware platform of the U31 R22 server software and that of
the U31 R22 client can be integrated or be separated. For different numbers of NEs to
be managed, the recommended hardware configurations are different. Table 1-1 lists the
typical hardware configurations of the U31 R22 server.
Table 1-1 Hardware Configuration Requirement for the U31 R22 Server
The Number of
Maximum
Windows Server
Equivalent NEs
Number of
(For Integrated
Windows Server (For Separated
Clients
Configuration)
Configuration)
16
CPU: dual-core
CPU: dual-core
Main frequency 3 GHz
Memory 4 GB
Memory 4 GB
Hard disk 200 GB
Hard disk 200 GB
CPU: 2 x dual-core or
CPU: 2 x dual-core or four-core
300
1000
32
four-core
3000
8000
64
128
CPU frequency 3 GHz
CPU frequency 3 GHz
Memory 4 GB
Memory 4 GB
Hard disk 200 GB
Hard disk 200 GB
CPU: 2 x four-core
CPU: 2 x four-core
Memory 8 GB
Memory 8 GB
Hard disk 200 GB
Hard disk200 GB
CPU: 4 x four-core
Memory 16 GB
Hard disk 200 GB
Disk array sub-card
At least three hard disks (SCSI
SAS interfaces) of the same
configuration.
1-2
SJ-20111118090716-003|2012-01-10 (R1.0)
Chapter 1 Installing the U31 R22
The Number of
Maximum
Windows Server
Equivalent NEs
Number of
(For Integrated
Clients
Configuration)
Configuration)
200
CPU: 4 x four-core
20000
CPU frequency 3 GHz

Memory 32 GB
Hard disk 200 GB
Disk array sub-card
At least three hard disks (SCSI
SAS interfaces) of the same
configuration.
The two servers employ the
distributed mode.
1.2.1.2 Software Configuration of the Server

Table 1-2 lists the software required on the U31 R22 server.
Table 1-2 Software Configuration of the Server
Managed Object
Windows Server Configuration
Operating system
Windows 2003 Server (SP2 or above, operating system of 32

bits)/Windows 2008 Server: the SQL Server2005 database is
required.
Solaris: the Oracle database is required.
Database
SQL Server 2005 or Oracle
Redundancy scheme
Veritas
software
1.2.1.3 Preparation Before Installation

1. Install the Windows OS according to the requirements in "Software Configuration of
the Server".
2. Install the database according to the requirements in "Software Configuration of the
Server".
3. Check the network connection to ensure normal network communication.
a. Log in to the Windows operating system as the system administrator.
b. Select Start > Settings > Network Connections. The Network Connections
dialog box appears.
1-3
SJ-20111118090716-003|2012-01-10 (R1.0)
c.
Check whether the status of "Local Area Connection" is normal and whether the
network communication is normal.
1.2.1.4 Installing U31 R22 Server and Client Software

This section provides instructions for installing the U31 R22 server and client software on a
PC. After this PC is connected to the bearer transmission network, it can manage devices
on the network through the U31 R22 server.
Prerequisite
l
l
l
l
The PC hardware meets the requirements described in Typical Hardware

Configurations of the Server section.
The PC software meets the requirements described in Typical Software Configurations of the Server section.
The database services are terminated.
The FTP publishing service is terminated in the operating system.
Context
If U31 R22 has been installed in the server, please uninstall the program at first and then
delete it. Afterwards, do the following steps.
Steps
1. Log in to the Windows operating system as the administrator role.
2. Get the installation package from the U31 R22 installation CD. Run the setup.bat
program.
3. When prompted to open the unzip path, press the Enter key to unzip the installation
files under the default path.
4. After the installation files are unzipped, the Select language window appears. Select
English.
1-4
SJ-20111118090716-003|2012-01-10 (R1.0)
5. Click Next to open the License agreement page.

6. Select I accept the license agreement.
7. Click Next to open the Select installation style page.

8. In Available installation styles, select Normal Installation. In Available installation
types, select Client And Server Program.
1-5
SJ-20111118090716-003|2012-01-10 (R1.0)
9. Click Next. The Hierarchy Configuration window appears.

10. Keep the default setting, click Next. The Network Scale window appears.
11. Select the network scale in accordance with Table 1-3.
l
l
Caution!
Currently, only Scale 2 is supported when U31 R22 is managing BN-xTN
(IPTN&OTN) products.
U31 R22 does not support cross-scale data backup restoration or the incremental
upgrades of different scales.
Table 1-3 Description of Network Scales

Scale
Description
Scale 1
Only BN-IP (IP) products are installed: The installation is applicable

to applicable to computers with 2 G to 3 G physical memory.
l
Scale 2
This scale is not applicable to install BN-xTN (IPTN&OTN) products.

BN-xTN (IPTN&OTN) products are installed: The installation is

applicable to applicable to computers with 8 G or above physical
memory.
1-6
SJ-20111118090716-003|2012-01-10 (R1.0)
Scale
Description
Scale 3

Scale 4

Scale 5

Under the scale, the database must run in 64-bit operating systems,
and server process would be best run in 64-bit operating systems,
otherwise it will affect the network operation performance.
12. Click Next to open the Select Product page.

13. Select the products to be installed as required, and set the installation path.
Caution!
When only BN-xTN is installed (BN-IP is not selected), do not select Wireline
Management components.
1-7
SJ-20111118090716-003|2012-01-10 (R1.0)
14. Click Next to open the Database connection config page.

15. Configure the database connection parameters, which are described in Table 1-4.
Table 1-4 Explanations of Parameters in the Database Connection Config Page

Parameter
Database type
Database IP or hostname
Explanation
Select the database type of the U31 R22 server, options: Oracle
and Microsoft SQL Server.
Enter the IP address or host name of the computer on which the
U31 R22 server database is installed.
Set the port number of the database instance. The default value
Database port
is recommended.
If several database instances have been created, use the port
number of the instance used by the U31 R22 system.
SID(Only for oracle)
Enter the System Identifier (SID) of the database. Only applies

to the Oracle database.
Database superuser name
Enter the superuser name of the database.
Password
Enter the password of the superuser.
16. After configuring the parameters, click Test Database Connection to check if the
database can be successfully connected.
1-8
SJ-20111118090716-003|2012-01-10 (R1.0)
17. If the Message dialog box appears, indicating that the connection is successful, click
OK to return to the Database connection config window. Then click Next to open
the Database config page.
Note:
If the connection fails, remove the database connection fault first, and then continue
the installation of U31 R22.
18. Set the save paths and sizes of database files as needed.
19. Click Next to open the Host information config page.

20. Configure the server host information by referring to Table 1-5.
1-9
SJ-20111118090716-003|2012-01-10 (R1.0)
Table 1-5 Description of Configuring the Host Information

Parameter
Description
Main process server address
Enter the IP address of the main server.
Main process standby server
Enter the IP address of the standby server when configuring
address
the U31 R22 active/standby servers.
Please input EMS ID
The unique ID of the U31 R22 server. Only one EMS ID in

the entire network.
Distributed servers
When U31 R22 is deployed in distributed mode, you can
configuration
click Add to add the IP address of other host deployed in

distributed mode.
21. Click Next to open the System information detection page.
1-10
SJ-20111118090716-003|2012-01-10 (R1.0)
22. If the detection result of each Detect Item is Pass, click Next to open the Installation
Information Confirm page.
Note:
If the detection result of any Detect Item is Not Pass, remove the fault according to the
indication, and then continue to install U31 R22.
23. After confirming that the installation information is correct, click Install to open the
Unzip and copy files page.
24. After all files are unzipped and copied, click Next. The Confirm dialog box appears,
asking you whether to execute the SQL scripts now.
25. Click Yes to open the Install database page, and the installation of database starts.
26. After the SQL scripts are executed, click Next to open the Parameter Set page.
1-11
SJ-20111118090716-003|2012-01-10 (R1.0)
Note:
After the installation you may run NetNumen Configuration Center to modify the
parameters.
27. Click Next to open the System initialization page. The Confirm dialog box appears,
asking you whether to initialize all client scenes.
28. Click Yes.
29. After the system is initialized, click Next to open the Installation finished page.
30. Click Finish.
End of Steps
Result
The selected components of U31 R22 are installed on the computer.
1.2.1.5 Installing The License

Prerequisite
l
l
The U31 R22 server has been installed successfully.

You have obtained the License ums-license.LCS authorized by ZTE.
1-12
SJ-20111118090716-003|2012-01-10 (R1.0)
Context
Caution!
To run U31 R22 server, License must have been installed, while to run U31 R22 client
License is not necessary.
Steps
1. Log in the Windows operating system as Administrator.
2. Search the ums-license.LCS file in the U31 R22 directory where the server has been
installed.
Note:
During the process for installing U31 R22, License may be saved at different directories
based on different network scales.
For example, when you select Scale 1 for the network scale, License will be saved in
ums-server\works\uep\deploy. While, when you select Scale 2/Scale 3/Scale 4/Scale
5, License will be saved in ums-server\works\main\deploy.
3. Copy the authorized License ums-license.LCS, and use it to replace the default file of
the same name.
l
l
Note:
License must be named as ums-license.LCS, otherwise, the user cannot use it
properly.
The default ums-license.LCS file does not support any U31 R22 operation.
Therefore, you must replace it with the authorized License.
End of Steps
1.2.2 Installing the U31 R22 Client

1.2.2.1 Hardware Configuration of the Client
A Personal Computer (PC) workstation can serve as the U31 R22 client. Table 1-6 lists
the minimal hardware configuration of the client PC workstation.
1-13
SJ-20111118090716-003|2012-01-10 (R1.0)
Table 1-6 Hardware Configuration of U31 R22 Client

The Number of Equivalent NEs
Configuration of Independent Client (Workstation)
300
CPU: dual-core
CPU frequency3 GHz
Memory1 GB
Hard disk80 GB
1000
CPU: dual-core
CPU frequency3 GHz
Memory1 GB
Hard disk80 GB
3000
CPU: dual-core
CPU frequency3 GHz
Memory2 GB
Hard disk80 GB
8000
CPU: dual-core
CPU frequency3 GHz
Memory4 GB
Hard disk80 GB
20000
CPU: dual-core
CPU frequency3 GHz
Memory8 GB
Hard disk80 GB
1.2.2.2 Software Configuration of the Client

Table 1-7 lists the software required on the client computer.
Table 1-7 Software Configuration of the Client
Managed Object
Configuration
Operating system
Windows 2003 Server (SP2 or above, operating system of

32 bits)/Windows 2008 Server/Windows XP/Window 7
Browser
Netscape, or Internet Explorer 6.0 or later
Document viewer
Microsoft Office 2000 or later
Antivirus software
Mcafee VirusScan8.5, Norton, or Trend
1-14
SJ-20111118090716-003|2012-01-10 (R1.0)
1.2.2.3 Installing the Client Software

Install a U31 R22 client program alone, so you may access the server on another PC
through this client.
Prerequisite
l
l
The PC hardware meets the requirements described in Hardware Configuration of the

Client.
The PC software meets the requirements described in Software Configuration of the
Client.
Steps
1. Log in to the Windows operating system as the administrator role.
2. Get the installation package from the U31 R22 installation CD. Run the setup.bat
program.
3. When prompted to enter the unzip path, press the ENTER key to unzip the installation
files under the default path.
4. After the installation files are unzipped, the Select language window appears. Select
English.
5. Click Next to enter the License agreement page.

6. Select I accept the license agreement.
1-15
SJ-20111118090716-003|2012-01-10 (R1.0)
7. Click Next to enter the Select installation style page.

8. In Available installation styles, select Normal Installation; In Available installation
types, select Client Program.
9. Click Next. The Select Product window appears.

10. Select the products to be installed as required, and set the installation path.
1-16
SJ-20111118090716-003|2012-01-10 (R1.0)
Note:
Select product: Select the device types in the network and the U31 R22 product
components to install. It is recommended to select BN-MSTP, BN-CTN, and
BN-OTN below BN-xTN. The user can select BN Northbound Interface
(NetNumen T37) according to the needs. It is recommended to select E2E.
Set the installation path: Select the default path for installing the program, or click
Browse... to set other installation paths.
11. Click Next to enter the System information detection page.
1-17
SJ-20111118090716-003|2012-01-10 (R1.0)
12. If the detection result of each Detect Item is Pass, click Next to enter the Installation
Information Confirm page.
Note:
If the detection result of any Detect Item is Not Pass, remove the fault according to the
indication, and then continue to install U31 R22.
13. After confirming that the installation information is correct, click Install to enter the
Unzip and copy files page.
14. After all files are unzipped and copied, click Next to enter the Parameter Set page.
1-18
SJ-20111118090716-003|2012-01-10 (R1.0)
15. The default settings are recommended. Click Next to enter the System initialization
page. The Confirm dialog box appears, asking you whether to initialize all client
scenes.
16. Click Yes.
17. After the system is initialized, click Next to enter the Installation finished page.
18. Click Finish.
End of Steps
Result
The selected components of the U31 R22 client are installed on the computer.
1.3 Installing the U31 R22 On the Solaris OS

1.3.1 Installation Instructions
Note:
It is recommended that you install the U31 R22 server on the Solaris operating system and
install a standalone U31 R22 client on the Windows operating system.
1-19
SJ-20111118090716-003|2012-01-10 (R1.0)
1.3.2 Server Configuration

1.3.2.1 Hardware Configuration Requirement for the U31 R22 Server
It is recommended that you install the U31 R22 server software on the Solaris operating
system and install the U31 R22 client software on the Windows operating system. For
different numbers of NEs to be managed, the recommended hardware configurations are
different. Table 1-8 lists several typical hardware configurations of the server computer.
Table 1-8 Hardware Configuration Requirement for the U31 R22 Server
Number of
Number of U31 R22
Windows Server
Equivalent NEs
Clients That Can Be
(For Integrated
Configuration)
Connected
Configuration)
16
CPU: dual-core
CPU: dual-core
Main frequency 2
300
GHz
1000
32
Memory 8 GB
Memory 8 GB
Hard disk 200 GB
Hard disk 200 GB
CPU: dual-core or
CPU: dual-core or four-core
four-core
Main frequency 2
GHz
Memory 8 GB
Memory 8 GB
Single computer:
Hard disk
300G
l
Local dual
Local dual computer: Disk

array
computer: Disk
Specification: SAS hard disk
array
Quantity: Four, in RAID 5
Specification:
mode
SAS hard disk
Capacity 300G
l
Quantity:
Single computer: Hard disk

300G
Remote dua computer: Each
Four, in RAID
sever is configured with the
5+SPARE mode
same hard disk (SCSI SAS
Capacity 300G
interface) 2 x 300G
Remote dual
computer:
Each sever is
configured with
the same hard
disk (SCSI SAS
1-20
SJ-20111118090716-003|2012-01-10 (R1.0)
Number of
Number of U31 R22
Windows Server
Equivalent NEs
Clients That Can Be
(For Integrated
Configuration)
Connected
Configuration)
interface) 2 x
300G
3000
64
CPU: 4 x four-core
Memory 16 GB
Hard disk 300 GB
l
(Optional) Single computer:

Disk array sub-card (The
RAID1 mode requires at
least two hard disks, while
the RAID 0+1 mode requires
at least four hard disks)

array
Quantity: Five, in RAID 5
mode
Capacity 146G
Remote dual computer: Each

interface) 3 x 300G (RAID
0 mode)
8000
128
CPU: 4 x four-core
Memory 24 GB
Hard disk 600 GB
l
Single computer: Disk array

sub-card (The RAID 0+1
mode requires at least eight
hard disks)

array
Quantity: Seven, in RAID 5
mode
Capacity 300G
1-21
SJ-20111118090716-003|2012-01-10 (R1.0)
Number of
Number of U31 R22
Windows Server
Equivalent NEs
Clients That Can Be
(For Integrated
Configuration)
Connected
Configuration)
l
Remote dual computer: Each

interface) 5 x 600G (RAID
0 mode)
20000
200
CPU: 4 x six-core
Memory 48 GB
Hard disk 600 GB
Disk array for both single
computer and dual computer
Quantity: 11, in RAID 5 mode
Capacity 300G
l
l
Note:
Standard confutation for the Window server: Windows Server 2008 (64 bits) + SQL
Server 2008 (64 bits).
If the memory of the Windows server is larger than 4G, you need to configure the
enterprise edition operation system and the dual-computer software of the enterprise
edition Veritas.
For the dual-computer configuration of the EMS server whose manageable Equivalent
NE quantity is 1000 3000 or 8000, the remote dual-computer configuration mode is
recommended.
For the dual-computer configuration of the EMS server whose manageable Equivalent
NE quantity is 2000, the local dual-computer configuration mode is recommended.
1.3.2.2 Software Configuration Requirement for the U31 R22 Server

Table 1-9 lists the software required on the U31 R22 server.
1-22
SJ-20111118090716-003|2012-01-10 (R1.0)
Table 1-9 Software Requirement of the U31 R22 Server

Managed object
Operating
Solaris Server Configuration

Product and Version
Configuration
Solaris 10
The operating system must meet the following
system
requirements:
l
Capacity of the /export/home directory > 30 GB
User permission: root user permission
Language package: en_US.ISO8859-1
Database
Oracle 10g
Other software
FTP client
X graphical tool
FTP client: The U31 R22 installation package is

imported into the Solaris 10 operating system through
the FTP client.
X graphical tool: By using the X graphical tool, you

can install the U31 R22 remotely.
1.3.3 Preparation Before Installation

1.3.3.1 Configuring Xmanager
After configuring Xmanager, you can install the U31 R22 remotely through the Xmanager.
Prerequisite
The Solaris 10 operating system allows remote login of the root user.
Context
By default, the root user cannot log in to the system in remote login mode. If you want the
root user to log in to the server remotely, you are required to modify the server configuration
in the following way:
1. On the desktop of the server PC, navigate to the This Computer > File System > etc
> default directory.
2. Open the login file.
3. Find the CONSOLE=/dev/console line, and enter # at the beginning of the line. That
is, change CONSOLE=/dev/console into #CONSOLE=/dev/console.
The Xmanager mentioned in this section is version 3.0.
Steps
1. On the client PC, select Start > Programs > Xmanager Enterprise 3 > Xbrowser.
The Xbrowser dialog box appears.
2. On the Xmanager navigation tree in the left pane, select the static menu.
1-23
SJ-20111118090716-003|2012-01-10 (R1.0)
3. In the address bar, enter the server IP address and press Enter. A dialog box appear,
prompting you to enter the user name.
4. Enter the user name, and click OK. A dialog box appears, prompting you to enter the
password.
5. Enter the password and click OK to log in to the remote server.
End of Steps
1.3.3.2 Configuring the Oracle Database

During the installation of the U31 R22, certain tables and data need to be created in the
Oracle database. Therefore, the Oracle database should be in the running status so that
it can be configured.
Steps
1. On the server PC, select Launch > Applications > Utilities > Terminal. The Terminal
dialog box appears.
2. Enter the ps ef | grep oracle command, and then press the Enter key.
3. Set the Oracle database based on the command display.
If
Then
The command display is empty
To start the Oracle database process, enter the following

commands in turn:
i.
su - oracle
ii.
oracle
iii. lsnrctl start

iv. sqlplus system/password as sysdba
v.
The command display is not empty
startup
Note:
The Oracle database processes start with ora_. Oracle monitoring process is
/export/home/builder/oracle/product/10.2.0/db_1/bin/tnslsnr LISTENER inherit.
1-24
SJ-20111118090716-003|2012-01-10 (R1.0)
4. On the desktop of the server PC, double-click the This Computer icon. The This
Computer window appears.
5. Select the Edit > Preferences menu.
6. In the Views page of the dialog box that appears, select Show hidden and backup
files, and then click Close.
7. (Optional) If the .profile file does not exist, create the .profile file.
Note:
If the directory for installing the Oracle database is /export/home/builder/orac
le/product/10.2.0/db_1, create the .profile file in the /export/home/bui
lder/oracle/ directory.
8. In the .profile file, add the environment variables of the Oracle database.
1-25
SJ-20111118090716-003|2012-01-10 (R1.0)
Environment Variable
Description
ORACLE_HOME=/export/home/builder/ora-
Installation directory of the Oracle database
cle/product/10.2.0/db_1
ORACLE_BASE=/export/home/builder/oracle/
ORACLE_SID=uep
SID of the Oracle database
PATH=$PATH:$ORACLE_HOME/bin
LANG=zh_CN.GBK
The language environment of the operating

system. When the language environment is
English, set LANG=en_US.ISO8859-1.
NLS_LANG=AMERICAN_AMER-
The language environment of the Oracle
ICA.ZHS16GBK
database. When the language environment is

English, set NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1.
9. Save and close the .profile file.

End of Steps
1.3.3.3 Uploading the U31 R22 Installation Files

Upload the U31 R22 installation files from the FTP client to the FTP server.
Context
The FTP server refers to the PC on which the U31 R22 server is installed.
The FTP software used in this section is Filezilla.
Steps
1. On the FTP client, start the FTP software.
2. In the FTP window, enter the FTP server IP address, user name, password, and port
number.
3. Click the Fast Connect button to connect to the FTP server.
4. Drag the U31 R22 installation files from the FTP client to a directory of the FTP server.
End of Steps
1.3.3.4 Modifying the FTP Service Port

While the U31 R22 is installed on the Solaris 10 operating system, the FTP server needs
to be installed, occupying TCP port 21. To prevent conflict between the FTP server on the
Solaris 10 operating system and the FTP server on the U31 R22, the port number used by
the FTP server on the Solaris 10 operating system needs to be modified.
1-26
SJ-20111118090716-003|2012-01-10 (R1.0)
Steps
1. On the desktop of the server PC, navigate to the This Computer > File System > etc
> inet directory.
2. Open the service file in the directory.
3. Find the row of FTP, and change the port number to another idle port.
For example, you can change the port number to 2121.
4. Save and close the service file.

End of Steps
1.3.4 Installing the U31 R22 Server

This section describes how to install the U31 R22 server.
Steps
1. Navigate to the directory of the U31 R22 installation files, and double-click setup.sh
to start the U31 R22 installation.
2. In the Selection Language dialog box, set the language to English, and then click
Next.
1-27
SJ-20111118090716-003|2012-01-10 (R1.0)
3. In the License agreement dialog box, select I accept the license agreement, and
then click Next.
4. In the Select installation style dialog box, set Available installation styles to
Normal installation, and set Available installation types to Server Program, and
then click Next.
1-28
SJ-20111118090716-003|2012-01-10 (R1.0)
5. In the Hierarchy configuration dialog box, accept the default settings, and then click
Next.
6. In the Network Scale dialog box, set the required scale according to the network size
and the hardware configuration of the U31 R22 server, and then click Next.
l
l
Caution!
Currently, only Scale 2 is supported when U31 R22 is managing BN-xTN
(IPTN&OTN) products.
U31 R22 does not support cross-scale data backup restoration or the incremental
upgrades of different scales.
Table 1-10 Description of Network Scales

Scale
Description
Scale 1
Only the BN-IP (IP) products are installed: The installation is

applicable to computers with 2 G to 3 G physical memory.
Scale 2

BN-xTN (IPTN&OTN) products are installed: The installation is

applicable to applicable to computers with 16 G or above physical
memory.
Scale 3


1-29
SJ-20111118090716-003|2012-01-10 (R1.0)
Scale
Description
Scale 4
The installation is applicable to computers with 16 G to 31 G physical

memory.
Scale 5
The installation is applicable to computers with 32 G to 63 G physical

memory. Under the scale, the database must run in 64-bit operating
systems, server process would be best run in 64-bit operating
systems, otherwise it will affect the network operation performance.
7. In the Select product dialog box, set the functions of the U31 R22 server and
installation path, and then click Next.
Caution!
When only BN-xTN is installed (BN-IP is not selected), do not select Wireline
Management components.
8. In the Database connection config dialog box, set Database IP or hostname and
Password of the database superuser.
1-30
SJ-20111118090716-003|2012-01-10 (R1.0)
9. Click the Test Database Connection button to test the status of the connection
between the U31 R22 installation program and the database.
10. If the connection to the database is normal, click Next.
Note:
If the connection is abnormal, fix the database connection fault, and then continue the
U31 R22 installation.
11. In the Database config dialog box, modify the database saving paths and database
file sizes, and then click Next.
1-31
SJ-20111118090716-003|2012-01-10 (R1.0)
12. In the Host information config dialog box, enter the master server address, and then
click Next.
13. When the system information detection succeeds, click Next.

14. Click Install to start the U31 R22 installation.
15. Decompress and copy the files to the required directory, and then click Next. The
Confirm message dialog box appears.
16. Click Yes.
17. After the database script is executed successfully, click Next.
18. Click Next.
1-32
SJ-20111118090716-003|2012-01-10 (R1.0)
19. After the system initialization is completed, click Next.

20. Click Finish to complete the U31 R22 installation.
End of Steps
1.3.5 Installing Licenses

Licenses must be installed for the U31 R22 so that users can use the U31 R22.
Steps
1. Install licenses.
If
Then
The network scale of the U31 R22 is Scale1
The licenses are installed in the \ums-server\work

s\uep\deploy directory.
The network scale of the U31 R22 is not
The licenses are installed in the \ums-server\work
Scale1.
s\main\deploy directory.
Note:
If the network scale is Scale1 and the U31 R22 is installed in the /export/home/b
uilder/U31/ directory, the licenses are installed in the /export/home/builder
/U31/ums-server/works/uep/deploy/ directory.
End of Steps
1.4 Installing the U31 R22 On the Linux OS

1.4.1 Installation Instruction
Note:
It is recommended to install U31 R22 servers on the Linux operating systems, and install
independent U31 R22 clients on the Windows operating systems.
1-33
SJ-20111118090716-003|2012-01-10 (R1.0)
1.4.2 Configuration Requirement for the Server

1.4.2.1 Hardware Configuration Requirements on the Server
On the Linux platform, the hardware platforms of U31 R22 server software and client
software can be installed in one computer or in different computers. Because the numbers
of NEs managed by different U31 R22s are different, their hardware configurations are
recommended to be different. Refer to Table 1-11 for typical hardware configurations on
the server.
Table 1-11 Hardware Configuration Requirements on the U31 R22 Server
The
The
Linux Server (Server and Client
Number
Number of
Software in One Computer)
Software in Different Computers)
of Valid
Accessible
NEs
Clients
300
16
CPU: dual core
CPU: dual core
Main frequency 2GHz
Main frequency 2GHz
Memory 8G
Memory 8G
Hard disk 200G
Hard disk 200G
CPU: 2 * dual core or quad core
CPU: 2 * dual core or quad core
Main frequency 2GHz
Main frequency 2GHz
Memory 8G
Memory 8G
1000
32
Single server: hard disk

300G
300G
Local two-server cluster: disk
Two-server cluster: disk array
array
Quantity: 4 pcs in RAID 5
Quantity: 4 pcs in RAID 5+
mode
SPARE mode
Capacity 300G
l
Single server: hard disk
Capacity 300G
l
Remote two-server cluster:
same hard disk of each server
with SCSI SAS interface 2 *
with SCSI SAS interface 2
300G
* 300G
1-34
SJ-20111118090716-003|2012-01-10 (R1.0)
The
The
Number
Number of
of Valid
Accessible
NEs
Clients
3000
64
CPU: 2* quad core

Main frequency 2GHz
Memory 16G
Hard disk 300G
l
(Optional) single server: disk

array subcard. A minimum of
two hard disks are required
for the RAID mode, and a
minimum of four for the RAID
0+1 mode

Quantity: 5 pcs in RAID 5
mode
Capacity 146G

300G in RAID 0 mode
8000
128
CPU: 4* quad core

Main frequency 2GHz
Memory 32G
Hard disk 600G
l
Single server: disk array

subcard. A minimum of eight
hard disks are required for the
RAID 0+1 mode

Quantity: 7 pieces in RAID 5
mode
Capacity 300G

600G in RAID 0 mode
1-35
SJ-20111118090716-003|2012-01-10 (R1.0)
The
The
Number
Number of
of Valid
Accessible
NEs
Clients
20000
200
CPU: 4* hex core

Main frequency 2GHz
Memory 64G
Hard disk 600G
Disk arrays must be configured
for singer servers and two-server
clusters
Quantity: 11 pieces in RAID 5 mode
Capacity 300G
Note:
If performing cluster configurations on the NM servers, the numbers of valid NEs of
which are 1000, 3000 or 8000, it is recommended to use remote cluster configuration
mode.
If performing cluster configurations on the NM servers, the numbers of valid NEs of
which are 20000, it is recommended to use local cluster configuration mode.
1.4.2.2 Software Configuration Requirements on the Server

Refer to XXX for the software configurations on the NMS server.Table 1-12
Table 1-12 Software Configuration Requirements on the Server
Management
Windows server configurations
Object
Operating system
CGS Linux V3.02 64bit
Database
Oracle 10g (10.2.0.4 or 10.2.0.5) 64bit
Redundancy
Veritas Storage Foundation High Availability Solutions 5.1 SP1
solution software
1.4.3 Preparation Before Installation

Before installing the U31 R22 server on the Linux platform, the operator should:
l
Upload the installation files by referring to Preparation Before Installation in chapter

one.
1-36
SJ-20111118090716-003|2012-01-10 (R1.0)
Disable the FTP ports of the operating system.

1. Log in to the U31 R22 server as the root user.
2. Enter the following command on the terminal: svcadm disable network/ftp.
Note:
If the FTP ports of the operating system are not disabled, conflicts take place
between FTP ports of the operating system and U31 R22 FTP ports, which results in
unavailable U31 R22 FTP functions.
1.4.4 Installing the U31 R22 Server

This section describes how to install the U31 R22 server on the Linux platform.
Prerequisite
l
l
l
The U31 R22 disk for installation is available.

The License file is uploaded to the server.
The database is installed and configured.
Steps
2. Open the terminal, enter the directory for server installation, execute the following
command:
# ./setup.sh
The NetNumen Setup-Select Language dialog box is displayed, see Figure 1-2.
1-37
SJ-20111118090716-003|2012-01-10 (R1.0)
Figure 1-2 NetNumen Setup-Select Language Dialog Box
3. Select English, and click Next.

The License Agreement screen is displayed.
4. Select I accept the license agreement, and click Next.
The NetNumen Setup-Select Installation Style dialog box is displayed, see Figure
1-3.
1-38
SJ-20111118090716-003|2012-01-10 (R1.0)
Figure 1-3 NetNumen Setup-Select Installation Style Dialog Box
5. Select installation style and type, click Next.

The NetNumen Setup-Hierarchy Configuration dialog box is displayed, see Figure
1-4.
1-39
SJ-20111118090716-003|2012-01-10 (R1.0)
Figure 1-4 NetNumen Setup-Hierarchy Configuration Dialog Box
6. Leave the default configurations unchanged, and click Next.

The NetNumen Setup-Network Scale dialog box is displayed, see Figure 1-5.
Figure 1-5 NetNumen Setup-Network Scale Dialog Box
1-40
SJ-20111118090716-003|2012-01-10 (R1.0)
Note:
Each scale has different requirements for the server configurations. If the current
configuration is lower than the configuration requirements of corresponding scale, the
U31 R22 performance is affected.
7. Based on the tips in the left pane and current server configurations, select network
scale, and click Next.
The NetNumen Setup-Select Product dialog box is displayed, see Figure 1-6.
Figure 1-6 NetNumen Setup-Select Product Dialog Box
Note:
Because BN-xTN CTN and BN-IP Management are incompatible, only one of them
can be installed. When selecting all product, BN-xTN CTN is selected by default.
BN-IP Management and the Wireline Management cannot be installed independently.
As a result, they must be both selected if one of them is required to be installed.
The software installation path fails to support the following characters: Chinese, + in
English, !, @, # and &.
1-41
SJ-20111118090716-003|2012-01-10 (R1.0)
8. Select the products to be installed, set the installation path, and click Next.
The NetNumen Setup-Database Connection Configuration dialog box is displayed,
see Figure 1-7.
Figure 1-7 NetNumen Setup-Database Connection Configuration Dialog Box
Refer to Table 1-13 for parameter descriptions in the NetNumen Setup-Database

Connection Configuration dialog box.
Table 1-13 Parameter Descriptions for Database Connection Configuration
Parameter
Description
Database type
The type of the database to be connected. Options: Oracle

and Microsoft SQL Server.
Oracle connection type
The type of Oracle database connection. Default: sid.
Database IP or hostname
The IP address or host name of the database server.
Database port:
The database instance port ID. The default value is

recommended. In case of multiple instance installation,
enter the instance port ID of the corresponding database.
Oracle SID or service name
The SID or network service name of the Oracle database.

Default: uep.
Database superuser name
The database user with administrator permissions. Default:

system.
Password
The password of the database administrator system.
1-42
SJ-20111118090716-003|2012-01-10 (R1.0)
9. Set related parameters, click Test Database Connection to verify the connection.
l In case of successful connection, proceed the installation.
l In case of unsuccessful connection, troubleshoot the database connection and
proceed the connection.
10. Click Next
The NetNumen Setup-Host Information Configuration dialog box is displayed, see
Figure 1-8.
Figure 1-8 NetNumen Setup-Host Information Configuration Dialog Box
11. Set the address of the active server (U31 R22 server), and click Next.
The system starts to detect the database and operating system, and later displays the
detection results after completing the detection, see Figure 1-9.
1-43
SJ-20111118090716-003|2012-01-10 (R1.0)
Figure 1-9 NetNumen Setup-System Information Detection
12. Click Next.

The NetNumen Setup-Installation Information Confirmation dialog box is displayed.
13. Click Install, the system start to decompress files.
14. After file decompression, click Next.
A Confirm dialog box is displayed, asking whether to initialize the database
immediately.
15. Click Yes to initialize the database.
16. After initialization, click Next.
The NetNumen Setup-Parameter Set dialog box is displayed, see Figure 1-10.
1-44
SJ-20111118090716-003|2012-01-10 (R1.0)
Figure 1-10 NetNumen Setup-Parameter Set Dialog Box
17. Click Next.

U31 R22 starts running the upgrade program. After upgrade, a message box is
displayed, asking whether to initialize all client scenes.
18. Click Yes to initialize scenes.
19. After initialization, click Next.
The NetNumen Setup-Installation Finished dialog box is displayed.
20. Click Finish to complete the U31 R22 server installation.
End of Steps
1.4.5 Installing License

If the License file is not updated or out of date during U31 R22 server installation, refer to
this section for how to install License manually.
Prerequisite
l
l
The U31 R22 server is installed.

The License file is uploaded to the U31 R22 server.
Steps
1-45
SJ-20111118090716-003|2012-01-10 (R1.0)
2. Based on the scale selected during U31 R22 installation, copy the License file to a
corresponding directory.
l If selecting scale 1, copy License to the .../ums-server/works/uep/depl
oy directory.
l If selecting other scale, copy License to the .../ums-server/works/main/d
eploy directory.
For example, if selecting scale 1, U31 R22 is installed in the /opt/netnumen
directory, copy the License file to the /opt/netnumen/ums-server/works/uep/
deploy directory.
End of Steps
1-46
SJ-20111118090716-003|2012-01-10 (R1.0)
Chapter 2
Starting and Exiting the U31

R22
Table of Contents
Starting and exiting the U31 R22 On the Windows OS ...............................................2-1
Starting and exiting the U31 R22 On the Solaris OS...................................................2-4
Starting and exiting the U31 R22 On the Linux OS .....................................................2-5
2.1 Starting and exiting the U31 R22 On the Windows

OS
2.1.1 Starting the U31 R22 Server
Prerequisite
You have installed the U31 R22 server software successfully.
Steps
l
On the desktop of the Windows operating system, select Start > All Programs >
NetNumen Unified Management System > NetNumen Client, and the Login dialog
box appears.
End of Steps
2.1.2 Logging in to the U31 R22 Client

Prerequisite
Make sure that the U31 R22 server is running properly.
Steps
1. On the desktop of the Windows operating system, select Start > Programs >
NetNumen Unified Management System > NetNumen Client, and the Login dialog
box appears.
2-1
SJ-20111118090716-003|2012-01-10 (R1.0)
2. Enter User Name, Password, and Server Address in the Login window.
Caution!
In the U31 R22, the default user name is admin, and the password is null. Be sure to
modify the password of the admin user after successful login for the first time to ensure
the account security.
Tip:
on the right side of the server address to display
In the Login window, click
the Config Bureau dialog box. In the Config Bureau dialog box, you can configure
bureau name and the corresponding server address. The configuration information
will be displayed in the drop-down list of the Server Address to facilitate the user to
select.
3. Click OK.
End of Steps
2.1.3 Exiting the U31 R22 Client

This section describes how to close U31 R22 client.
Prerequisite
l
l
The client computer works normally, and the network communication is normal.
The client is connected to the server.
2-2
SJ-20111118090716-003|2012-01-10 (R1.0)
Chapter 2 Starting and Exiting the U31 R22
Steps
1. Select System > Exit in the U31 R22 client window.
2. Click OK in the Confirm message box to close the client.
End of Steps
2.1.4 Exiting the U31 R22 Server

Prerequisite
l
l
l
The U31 R22 server computer works normally, and the network communication is
normal.
Each process of U31 R22 server works normally.
Close all the clients that connect to the server.
Steps
1. You have already logged in to Windows operating system where the U31 R22 server
is installed.
2. Enter the console interface from Windows desktop.
3. Select each process in the console according to the following sequence, and then click
Stop.
Sequence
Process
BN-xTN northbound namingservice process 1
BN-xTN northbound notifyservice process 1
BN-xTN northbound process 1
U31 E2E process 1
BN CTN Adapter Proxy process 1
BN CTN Adapter process 1
BN SDH/OTN Adaptive 1
BN main process 1
UEP process 1
4. If the following requirements are satisfied at the same time, U31 R22 server is closed
successfully:
i.
The corresponding icon of each process is
ii.
The information xxx process - Stopped is displayed in the bottom of the window.
2-3
SJ-20111118090716-003|2012-01-10 (R1.0)
5. Select System > Exit, and then select OK in the message box that appears.
End of Steps
2.2 Starting and exiting the U31 R22 On the Solaris OS

This section describes how to start the U31 R22 server so that the U31 R22 client can
connect to the U31 R22 server.
Steps
1. Navigate to the startup directory of the U31 R22 server.
Note:
If the U31 R22 is installed in the /export/home/builder/U31/ directory, the
startup directory of the U31 R22 server is /export/home/builder/U31/ums-se
rver/.
2. Double-click the console.sh file to start the U31 R22 server.

End of Steps
2.2.2 Exiting the U31 R22 Server

This section describes how to exit the U31 R22 server.
Steps
1. In the U31 R22 console window, exit the following U31 R22 processes according to
the sequence in the following table.
Sequence
Process
BN-xTN northbound namingservice process 1
BN-xTN northbound notifyservice process 1
BN-xTN northbound process 1
U31 E2E process 1
BN CTN Adapter Process 1
BN CTN Adapter Proxy Process 1
BN SDH/OTN Adaptive 1
2-4
SJ-20111118090716-003|2012-01-10 (R1.0)
Chapter 2 Starting and Exiting the U31 R22
Sequence
Process
BN main process 1
UEP process 1
a. In the left navigation tree, click the name of the required process.
b. In the right pane, click Stop.
c. If the following requirements are met, repeat the above two steps to stop the other
processes in turn.
l In the process control operation column, the icon of the process is in the
state.
In the left pane, the icon before the process name is in the
state.
2. Select System > Exit. In the message box that appears, click Yes to exit the U31 R22
server.
End of Steps
2.3 Starting and exiting the U31 R22 On the Linux OS

This section describes how to start the U31 R22 server.
Steps
2. Open the terminal, enter the ums-server directory in the U31 R22 installation directory,
and execute the following commands to start the U31 R22 server.
# ./console.sh
During starting the server, the NetNumen U31 Unified Network Management
System-Console dialog box is displayed, see Figure 2-1.
2-5
SJ-20111118090716-003|2012-01-10 (R1.0)
Figure 2-1 Console Dialog Box
3. In the left navigation tree, select Console1.

The right pane shows detailed information of all running processes. If Operation res
ult is Successful, the process is started successfully.
End of Steps
2.3.2 Quitting the U31 R22 Server

This section describes how to quit the U31 R22 server.
Steps
2. Open the terminal, enter the ums-server directory in the U31 R22 installation directory,
and execute the following commands to quit the U31 R22 server.
# ./console.sh
End of Steps
2-6
SJ-20111118090716-003|2012-01-10 (R1.0)
Chapter 3
Uninstalling the U31 R22

Table of Contents
Uninstalling the U31 R22 On the Windows OS ...........................................................3-1
Uninstalling the U31 R22 On the Solaris OS...............................................................3-3
Uninstalling the U31 R22 On the Linux OS .................................................................3-4
3.1 Uninstalling the U31 R22 On the Windows OS

3.1.1 Uninstalling the U31 R22 Server and Client
Prerequisite
l
l
The U31 R22 server software has stopped working and the U31 R22 client has been
logged out.
You have logged into the Windows operating system as the administrator role.
Steps
1. In the Windows system of the computer installed with the U31 R22 server and client
software, select Start > Programs > NetNumen Unified Management System >
NetNumen Unintall Tool. The Uninstall dialog box appears.
2. Select whether to uninstall the database.
3-1
SJ-20111118090716-003|2012-01-10 (R1.0)
l
l
Select Uninstall database: delete all the datum in the database of U31 R22.
Clear Uninstall database: keep the datum in the database of U31 R22.
3. Click Next to open the Uninstall description page.

4. Click Start uninstall.
5. Optional: if you have selected Uninstall database in the previous steps, the Confirm
dialog box appears, prompting you to back up the data before uninstallation. Click
Yes.
6. The Confirm dialog box appears. Click Yes to display the Start uninstall page.
7. After uninstallation, click Finish.
8. Restart the computer.
End of Steps
Result
The U31 R22 server and client are uninstalled from the computer.
3.1.2 Uninstalling the U31 R22 Client

Prerequisite
l
l
The U31 R22 client software has been logged out.

You have logged into the Windows operating system as the administrator role.
3-2
SJ-20111118090716-003|2012-01-10 (R1.0)
Chapter 3 Uninstalling the U31 R22
Steps
1. In the Windows operating system on which the U31 R22 client software is installed,
select Start > Programs > NetNumen Unified Management System > NetNumen
Unintall Tool. The Uninstall dialog box appears.
2. Click Next. The Uninstall description window appears.
4. (Optional) If you have selected Uninstall database in the previous step, the Confirm
dialog box appears, prompting you to back up data before uninstallation. Click Yes.
5. The Confirm dialog box appears. Click Yes. The Start uninstall window appears.
6. After uninstallation, click Finish.
End of Steps
Result
The U31 R22 client is uninstalled from the computer.
3.2 Uninstalling the U31 R22 On the Solaris OS

3.2.1 Uninstalling the U31 R22 Server Software
This section describes how to uninstall the U31 R22 server software.
Prerequisite
The services of the U31 R22 server have stopped and the U31 R22 client has exited.
Steps
1. Navigate to the uninstall directory of the U31 R22 server.
Note:
If the U31 R22 is installed in the /export/home/builder/U31/ directory, the
uninstall directory of the U31 R22 server is /export/home/builder/U31/uif/.
2. Double-click the uninstalltool.sh file to start uninstall the U31 R22 server.
l Select Uninstall database: After the database is uninstalled, the database data
related to the U31 R22 is also deleted.
l Do not select Uninstall database: After the database is uninstalled, the database
data related to the U31 R22 is also not deleted.
3. Click Next. The Uninstall description dialog box appears.
3-3
SJ-20111118090716-003|2012-01-10 (R1.0)

5. (Optional) If Uninstall database is selected in Step 2, the Confirm message box
appears, prompting you to back up important data before the uninstall. Click Yes.
6. In the Confirm message box, click Yes.
7. After the uninstall is completed, click Finish.
End of Steps
3.3 Uninstalling the U31 R22 On the Linux OS

3.3.1 Uninstalling the U31 R22 Server Software
This section describes how to uninstall the U31 R22 server software on the Linux platform.
Prerequisite
Both the U31 R22 server and clients have quit from the Linux platform.
Steps
2. Open the terminal, enter the uif directory in the U31 R22 installation directory, and
execute the following command.
# ./uninstalltool.sh
The Uninstall database selection dialog box is displayed, see Figure 3-1.
3-4
SJ-20111118090716-003|2012-01-10 (R1.0)
Chapter 3 Uninstalling the U31 R22
Figure 3-1 Uninstall Database Selection Dialog Box
l
l
Select Uninstall database to uninstall the U31 R22 software and the involved
database data.
Do not select Uninstall database to uninstall the U31 R22 software and keep the
involved database data.
3. Decide whether to uninstall the database based on actual situation, and click Next.
U31 R22The Uninstall description dialog box is displayed.
4. Click Start Install.
5. After completing uninstallation, click Finish.
End of Steps
3-5
SJ-20111118090716-003|2012-01-10 (R1.0)
This page intentionally left blank.
3-6
SJ-20111118090716-003|2012-01-10 (R1.0)
Figures
Figure 1-1 Software Installation Flow of the U31 R22 System ................................... 1-1
Figure 1-2 NetNumen Setup-Select Language Dialog Box ...................................... 1-38
Figure 1-3 NetNumen Setup-Select Installation Style Dialog Box ............................ 1-39
Figure 1-4 NetNumen Setup-Hierarchy Configuration Dialog Box ........................... 1-40
Figure 1-5 NetNumen Setup-Network Scale Dialog Box.......................................... 1-40
Figure 1-6 NetNumen Setup-Select Product Dialog Box ......................................... 1-41
Figure 1-7 NetNumen Setup-Database Connection Configuration Dialog
Box ....................................................................................................... 1-42
Figure 1-8 NetNumen Setup-Host Information Configuration Dialog Box................. 1-43
Figure 1-9 NetNumen Setup-System Information Detection .................................... 1-44
Figure 1-10 NetNumen Setup-Parameter Set Dialog Box........................................ 1-45
Figure 2-1 Console Dialog Box ................................................................................. 2-6
Figure 3-1 Uninstall Database Selection Dialog Box ................................................. 3-5
Figures
Tables
Table 1-1 Hardware Configuration Requirement for the U31 R22 Server................... 1-2
Table 1-2 Software Configuration of the Server ......................................................... 1-3
Table 1-3 Description of Network Scales ................................................................... 1-6
Table 1-4 Explanations of Parameters in the Database Connection Config
Page ........................................................................................................ 1-8
Table 1-5 Description of Configuring the Host Information....................................... 1-10
Table 1-6 Hardware Configuration of U31 R22 Client .............................................. 1-14
Table 1-7 Software Configuration of the Client ........................................................ 1-14
Table 1-8 Hardware Configuration Requirement for the U31 R22 Server................. 1-20
Table 1-9 Software Requirement of the U31 R22 Server ......................................... 1-23
Table 1-10 Description of Network Scales ............................................................... 1-29
Table 1-11 Hardware Configuration Requirements on the U31 R22 Server ............. 1-34
Table 1-12 Software Configuration Requirements on the Server ............................. 1-36
Table 1-13 Parameter Descriptions for Database Connection Configuration............ 1-42
III
Tables
Glossary
PC
- Personal Computer

U31 V12!11!40 SoftwareInstallationGuide en

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

U31 V12!11!40 SoftwareInstallationGuide en

Uploaded by

Copyright:

Available Formats

NetNumen U31 R22

Unified Network Management System

Software Installation Guide

Additionally, the contents of this document are protected by

contractual confidentiality obligations.

NetNumen U31 R22 (V12.11.40) Issued

Serial Number: SJ-20111118090716-003

About This Manual

1, Installing U31 R22

2, Starting and Quitting U31 R22

3, Uninstalling U31 R22

occur if you ignore this safety warning.

cur if you ignore this safety warning.

mance, or other unpredictable result may occur if you ignore this

Provides additional information about a topic.

Chapter 2 Starting and Exiting the U31 R22 ............................................ 2-1

Chapter 3 Uninstalling the U31 R22.......................................................... 3-1

3.1.2 Uninstalling the U31 R22 Client................................................................. 3-2

Installing the U31 R22

1.1 Software Installation Flow

ZTE Proprietary and Confidential

NetNumen U31 R22 Software Installation Guide

1.2 Installing the U31 R22 On the Windows OS

Windows Server (For Separated

Main frequency 3 GHz

Main frequency 3 GHz

Hard disk 200 GB

Hard disk 200 GB

CPU: 2 x dual-core or four-core

CPU frequency 3 GHz

CPU frequency 3 GHz

Hard disk 200 GB

Hard disk 200 GB

Main frequency 3 GHz

Main frequency 3 GHz

Hard disk 200 GB

ZTE Proprietary and Confidential

Chapter 1 Installing the U31 R22

Windows Server (For Separated

CPU frequency 3 GHz

1.2.1.2 Software Configuration of the Server

Windows Server Configuration

Windows 2003 Server (SP2 or above, operating system of 32

Solaris: the Oracle database is required.

SQL Server 2005 or Oracle

1.2.1.3 Preparation Before Installation

ZTE Proprietary and Confidential

NetNumen U31 R22 Software Installation Guide

1.2.1.4 Installing U31 R22 Server and Client Software

The PC hardware meets the requirements described in Typical Hardware

ZTE Proprietary and Confidential

Chapter 1 Installing the U31 R22

5. Click Next to open the License agreement page.

7. Click Next to open the Select installation style page.

ZTE Proprietary and Confidential

NetNumen U31 R22 Software Installation Guide

9. Click Next. The Hierarchy Configuration window appears.

Table 1-3 Description of Network Scales

Only BN-IP (IP) products are installed: The installation is applicable

This scale is not applicable to install BN-xTN (IPTN&OTN) products.

BN-xTN (IPTN&OTN) products are installed: The installation is

ZTE Proprietary and Confidential

Chapter 1 Installing the U31 R22