Vous êtes sur la page 1sur 77

NetNumen M31(RAN)

Mobile Network Element Management System


Software Installation

Version: 12.10.032

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 Date Revision Reason

R1.0 2011-03-11 First Edition

R1.1 2011-04-18 This revision adds, reorganises, or modify the following topics
to optimise the configuration procedure of the Oracle database
and provide additional function of saving server information for
convenient login to the client:
l Net Configuration of the Database
l Adding a Listener and Local Net Service Name for the
Database
l Modifying the Listener and Local Net Service Name for the
Database
l Starting the EMS Client

Serial Number: SJ-20101227165724-003

Publishing Date: 2011-04-18(R1.1)


Contents
About This Manual ......................................................................................... I
Chapter 1 System Overview ...................................................................... 1-1
1.1 Introduction to the Network Element Management System.................................... 1-1
1.2 System Architecture ........................................................................................... 1-1
1.2.1 Hardware Architecture .............................................................................. 1-2
1.2.2 Software Architecture ............................................................................... 1-2
1.3 Configuration Requirements................................................................................ 1-3
1.3.1 Configuration Requirements of the Server.................................................. 1-3
1.3.2 Configuration Requirements of the Client ................................................... 1-4
1.4 Software Installation Flow ................................................................................... 1-5

Chapter 2 Database Instance Configuration............................................ 2-1


2.1 Introduction to Database Instance Configuration................................................... 2-1
2.2 Prerequisites for Database Instance Creation....................................................... 2-1
2.3 Creating an Oracle Database Instance ................................................................ 2-2
2.4 Net Configuration of the Database..................................................................... 2-15
2.4.1 Adding a Listener and Local Net Service Name for the Database .............. 2-15
2.4.2 Modifying the Listener and Local Net Service Name for the Database........ 2-24
2.5 Inspections After Database Instance Configuration............................................. 2-28

Chapter 3 Installation of the EMS Server Software ................................. 3-1


3.1 Introduction to the Installation of EMS Server Software ......................................... 3-1
3.2 Preparations Before Installing the EMS Server Software ....................................... 3-1
3.3 Installing the EMS Server Program...................................................................... 3-2
3.4 Checking the Installation Directory of Server Software ........................................ 3-13
3.5 Starting the EMS Server ................................................................................... 3-13

Chapter 4 Installation of the EMS Client Software .................................. 4-1


4.1 Introduction to the Installation of EMS Client Software .......................................... 4-1
4.2 Installing the EMS Client Program ....................................................................... 4-1
4.3 Checking the Installation Directory of Client Software ........................................... 4-7
4.4 Starting the EMS Client ...................................................................................... 4-8

Appendix A Uninstallation of the EMS Client Software ......................... A-1


Figures............................................................................................................. I
Tables .............................................................................................................V

I
Glossary .......................................................................................................VII

II
About This Manual
The NetNumen M31 Mobile Network Element Management System (hereinafter called
NetNumen M31 or EMS for short) is a network management system for managing mobile
network elements. It is an intermediate system between the upper-layer operation support
system and lower-layer network element management systems. By using NetNumen M31,
you may perform the integrated and centralised management operations on the network
elements, including:
l Configuration management
l Fault management
l Performance management
l Security management
l Log management
l Report management.
NetNumen M31 uses object-oriented technologies. It is designed on the advanced J2EE
platform, providing unified standard interfaces to external devices.

Purpose
This manual provides the procedures and guidelines that support the installation of
the NetNumen M31 mobile network element management system, including an Oracle
database instance, and the EMS server and client programs.

Intended Audience
l Maintenance engineers
l Debugging engineers

What Is in This Manual

Chapter/Appendix Summary

Chapter 1 System Introduction Gives an brief introduction to the architecture, and configuration
requirements of the NetNumen M31 system, and provides a
general software installation flow of the system.

Chapter 2 Database Instance Describes the preparation and configuration procedure of an


Configuration Oracle database instance for the NetNumen M31 system.

Chapter 3 Installation of the EMS Describes the preparation and installation procedure of the
Server Software NetNumen M31 server program in an Advanced Interactive
eXecutive (AIX) operating system.

I
Chapter/Appendix Summary

Chapter 4 Installation of the EMS Provides the procedure for installing the NetNumen M31 client
Client Software program in a Windows operating system.

Appendix A Uninstallation of the Describes how to remove the EMS client software from a
EMS Client Software computer.

Conventions
This document employs the following mouse operation conventions.

Typeface Meaning

Italics References to other manuals and documents.

“Quotes” Links on screens.

Bold Menus, menu options, function names, input fields, option button names,
check boxes, drop-down lists, dialogue box names, window names.

CAPS Keys on the keyboard and buttons on screens and company name.

Note: Provides additional information about a certain topic.

Checkpoint: Indicates that a particular step needs to be checked before


proceeding further.

Tip: Indicates a suggestion or hint to make things easier or more productive


for the reader.

II
Chapter 1
System Overview
Table of Contents
Introduction to the Network Element Management System.........................................1-1
System Architecture ...................................................................................................1-1
Configuration Requirements .......................................................................................1-3
Software Installation Flow...........................................................................................1-5

1.1 Introduction to the Network Element Management


System
NetNumen M31 Mobile Network Element Management System (hereinafter referred to
NetNumen M31 or EMS) is a network element management system offered by ZTE
Corporation for the unified management and maintenance of network elements in wireless
networks. In addition to management functions on the network element level, it provides
some management functions on the network level.
The following explains some concepts that you may encounter while using this manual.
l Client/Server Architecture
In a client/server architecture, multiple clients are connected to a server over a local
area network or metro area network. You can operate resources stored on the server
after logging in to a client. The server returns the operation result on request.

l Server
NetNumen M31 adopts the client/server architecture. The server in such architecture
includes both hardware and software. NetNumen M31 provides a program running
on the server, that is, the server software. And the computer or workstation where the
program is running is the server hardware.

l Client

The client in the client/server architecture is a client program. You can install and
run the client program on the computer where the server software is, or install it
independently on another computer.

1.2 System Architecture


Understanding the software and hardware architecture of NetNumen M31 is necessary
before the installation and application of the system. The following sections describes the
hardware architecture and software architecture of NetNumen M31 system respectively.

1-1

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


NetNumen M31(RAN) Software Installation

1.2.1 Hardware Architecture


NetNumen M31 is designed with a client/server architecture. Generally, a PC workstation
is deployed at the client and a Sun or IBM server is deployed at the server.
The NetNumen M31 system requires a high configuration server because the server
supports the running of all core functional modules of the system besides the maintenance
and storage of massive data. The configuration of the client is relatively lower because
the major task of the client is connecting the server and displaying the operation results.
The actual hardware configuration at the server and the client depends on the scale of
the managed network and the load of the system.
In terms of logical architecture, two types of devices are deployed at the server: host and
storage device.
l The host is the physical foundation of the system. It processes data in the system.
The system performance greatly depends on the processor speed of the host.
l Storage devices are used to save the data in the system. For storing large amounts
of important data in the system, external data storage devices with high capacity and
reliability are required besides the built-in disks in the host.
In terms of function, a server cluster, including application server, database server, and
File Transfer Protocol (FTP) server, can be deployed at the server. These servers can be
configured together on the same host, or independently on different hosts.

1.2.2 Software Architecture


The software of NetNumen M31 consists of two parts: server program and client program,
as illustrated in Figure 1-1.

Figure 1-1 Software Architecture of NetNumen M31

As shown in Figure 1-1, the server program runs in a UNIX or Linux operating system. And
Oracle database is used on the server. The client program runs in a Windows operating

1-2

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


Chapter 1 System Overview

system. In actual application, both the client and the server need the support of Java virtual
machine.

1.3 Configuration Requirements


1.3.1 Configuration Requirements of the Server
1.3.1.1 Server Configuration Solution
NetNumen M31 has a client/server architecture. The server implements the management
functions, acting as the core of the system. A Sun or IBM server is used as the NetNumen
M31 server, which uses Oracle database for data storage.
The NetNumen M31 server provides two kinds of services:
l Database services
The server provides the access and storage services via commercial database
software.
l Application services
The application services provided by the server include performance management,
fault management, configuration management, security management, topology
management, and system management. The server implements not only the basic
network management functions, but also the management and analysis of the
system.
Two configuration solutions are optional for the server: integrated configuration and
dual-server configuration for hot-backup.
l Integrated Configuration
l Dual-Server Configuration for Hot Backup

Integrated Configuration
The integrated configuration solution is a simple solution that integrates the database
services and the application services on the same server. It is low-cost but less reliable.
However, a Redundant Array of Independent Disks (RAID) scheme (RAID1 or RAID5) can
be used to greatly improve the server reliability.

Dual-Server Configuration for Hot Backup


In the dual-server configuration solution, two servers providing the same services are used.
One acts as the primary server, and the other acts as the standby one. The primary server
provides application services when the system runs properly. The standby server monitors
the working status of the primary one. And at the same time, the primary server checks
whether the standby server is working properly. If the primary server fails to support the
applications, the standby server takes over the primary one to provide key application
services and ensure the continuous running of the system.

1-3

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


NetNumen M31(RAN) Software Installation

To achieve a high reliability of the system, the dual-server configuration solution also
supports the hot backup of data. The data in the database is stored in an RAID storage
device. When the primary server fails, the standby server takes over the primary server
and accesses the data in the RAID.

1.3.1.2 Software Configuration of the Server


The software configuration on the NetNumen M31 server is listed in Table 1-1.

Table 1-1 Software Configuration of the Server

Software Server Type

UNIX Server Linux Server

Operating System Solaris 10, or AIX SUSE Linux Enterprise 11 SP1 or


later versions

Database Oracle database 10g, or Oracle Oracle database 10g, or Oracle


database 11g for UNIX database 11g for Linux

Antivirus Software - -

Disaster Recovery Software Veritas, or Legato Veritas, or Legato

1.3.2 Configuration Requirements of the Client


1.3.2.1 Hardware Configuration of the Client
A PC workstation is used as the NetNumen M31 client. Table 1-2 lists the requirements
for the minimal hardware configuration of a PC workstation used as the client.

Table 1-2 Minimal Hardware Configuration of the Client

Hardware Configuration

CPU PentiumIV 3.0 GHz

Memory 2 GB

Built-in Hard Disk 500 GB

Disk Array None

1.3.2.2 Software Configuration of the Client


The software configuration on the NetNumen M31 client is listed in Table 1-3.

1-4

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


Chapter 1 System Overview

Table 1-3 Software Configuration of the Client

Software Configuration

Operating System Windows XP, or Windows 7

Browser Internet Explorer 7.0

Document Viewer Microsoft Office 2003 or 2007

Antivirus Software McafeeVirusScan 8.5, Norton, or Trend

1.4 Software Installation Flow


Figure 1-2 illustrates a general flow for installing the software of the NetNumen M31 system
on field.

Figure 1-2 Software Installation Flow of NetNumen M31

This flowchart only contains the software that shall be installed on field, except the software
pre-installed on the server and the client before the delivery of the NetNumen M31 system.
The following lists the software pre-installed on the server and the client.

1-5

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


NetNumen M31(RAN) Software Installation

l Server:
à IBM Advanced Interactive eXecutive (AIX) operating system
à Oracle database with an instance configured (SID: minos)
l Client: Microsoft Windows operating system on the client

Note:

Generally, a default instance (SID: minos) has been created on the server before delivery.
And the net configuration of the database, including listener and local net service name,
has also been completed.

If no instance is available on the server, you need to create an instance on field and
implement the net configuration for the database before installing the EMS server program.

1-6

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


Chapter 2
Database Instance
Configuration
Table of Contents
Introduction to Database Instance Configuration ........................................................2-1
Prerequisites for Database Instance Creation.............................................................2-1
Creating an Oracle Database Instance .......................................................................2-2
Net Configuration of the Database............................................................................2-15
Inspections After Database Instance Configuration ..................................................2-28

2.1 Introduction to Database Instance Configuration


In general, the operating system and Oracle database software have been installed on
the server of the NetNumen M31 system before delivery. If the default database instance
(SID: minos) has not been created on the server, you need to create an Oracle database
instance on field for storing all kinds of management data before installing the NetNumen
M31 system software.

Note:
It is recommended to store all data files on a disk array instead of the NetNumen M31
server because the disk array can provide enough space for large amounts of data.

The following gives a general flow for creating and configuring a database instance.
1. Check that all prerequisites are met.
2. Create an Oracle database instance.
3. Configure a listener and local net service name for the database.
4. Inspect the configuration of the database instance.

2.2 Prerequisites for Database Instance Creation


Before creating a database instance, make sure that the installation environment meets
the following requirements.

l The IBM AIX operating system has been installed on the server.
l The Oracle database software has been installed on the server.

2-1

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


NetNumen M31(RAN) Software Installation

l TCP/IP services have been installed.


l Sufficient disk space is available on the server. The following gives the requirements
for the size of some partitions.

Space Size

System partition ≥500 MB

Home directory of Oracle ≥3 GB

Tablespace partition ≥10 GB

l A new user “oracle” with dba role has been created on the server.

2.3 Creating an Oracle Database Instance


To create an Oracle database instance in the AIX operating system, perform the following
steps:

1. Log in to the AIX operating system as oracle user via a graphic interface, and then
enter the command as follows:
$ dbca
The Database Configuration Assistant: Welcome window appears, as shown in
Figure 2-1. Click Next to continue.

Figure 2-1 Database Configuration Assistant: Welcome

2. On the Database Configuration Assistant, Step 1 of 12: Operations window, select


Create a Database, as shown in Figure 2-2. Then click Next to continue.

2-2

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


Chapter 2 Database Instance Configuration

Figure 2-2 Database Configuration Assistant, Step 1 of 12: Operations

3. On the Database Configuration Assistant, Step 2 of 12: Database Templates


window, select General Purpose and click Next, as shown in Figure 2-3.

Figure 2-3 Database Configuration Assistant, Step 2 of 12: Database Templates

4. On the Database Configuration Assistant, Step 3 of 12: Database Identification


window, set the global database name and SID of the database to be created and then
click Next.

For example, enter ems in the Global Database Name and SID text boxes, as shown
in Figure 2-4.

2-3

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


NetNumen M31(RAN) Software Installation

Figure 2-4 Database Configuration Assistant, Step 3 of 12: Database Identification

5. On the Database Configuration Assistant, Step 4 of 12: Management Options


window, keep the default settings and click Next, as shown in Figure 2-5.

Figure 2-5 Database Configuration Assistant, Step 4 of 12: Management Options

6. On the Database Configuration Assistant, Step 5 of 12: Database Credentials


window, set the database password, confirm the password and then click Next.

For example, enter the recommended password oracle in the Password and
Confirm Password text boxes, as shown in Figure 2-6.

2-4

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


Chapter 2 Database Instance Configuration

Figure 2-6 Database Configuration Assistant, Step 5 of 12: Database Credentials

7. On the Database Configuration Assistant, Step 6 of 12: Storage Options window,


keep the default settings and click Next, as shown in Figure 2-7.

Figure 2-7 Database Configuration Assistant, Step 6 of 12: Storage Options

8. On the Database Configuration Assistant, Step 7 of 12: Database File Location


window, select Use Common Location for All Database Files, specify the location
in the Database Files Location box (for example, /datafile/ems), and then click
Next, as shown in Figure 2-8.

2-5

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


NetNumen M31(RAN) Software Installation

Figure 2-8 Database Configuration Assistant, Step 7 of 12: Database File Location

Note:
It is recommended to specify a location on a disk array with enough space for the
storage of all database files. A database files location on the NetNumen M31 server
needs much space on the server, which may influence the running of the system.

9. On the Database Configuration Assistant, Step 8 of 12: Recovery Configuration


window, cancel the selection of the Specify Flash Recovery Area check box and then
click Next, as shown in Figure 2-9.

2-6

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


Chapter 2 Database Instance Configuration

Figure 2-9 Database Configuration Assistant, Step 8 of 12: Recovery Configuration

10. On the Database Configuration Assistant, Step 9 of 12: Database Content


window, cancel the selection of the Sample Schemas check box and then click Next,
as shown in Figure 2-10.

Figure 2-10 Database Configuration Assistant, Step 9 of 12: Database Content

11. On the Database Configuration Assistant, Step 10 of 12: Initialization Parameters


window, do the following:

a. On the Memory tab, select Custom, select Automatic, and then set the size for
the System Global Area (SGA) in the SGA Size box according to the actual size
of the physical memory, as shown in Figure 2-11. The size of the Program Global
Area (PGA) is automatically given by the installation wizard.

2-7

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


NetNumen M31(RAN) Software Installation

Figure 2-11 Database Configuration Assistant, Step 10 of 12: Initialization


Parameters (Memory Tab)

The following table gives a reference setting of the SGA size.

Physical Memory (GB) Management Scale (Quantity of SGA Size (MB)


Managed Cells)

4 1000 900

16 5000 4096

32 10000 8192

64 15000 11264

64 20000 16384

b. On the Sizing tab, set the number of processes to the recommended value “500”,
as show in Figure 2-12.

2-8

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


Chapter 2 Database Instance Configuration

Figure 2-12 Database Configuration Assistant, Step 10 of 12: Initialization


Parameters (Sizing Tab)

c. On the Character Sets tab, select Choose from the list of character sets and
then select “ZHS16GBK - GBK 16-bit Simplified Chinese” from the Database
Character Set drop-down list box. Make sure that the national character set is
“AL16UTF16”, as shown in Figure 2-13.

Figure 2-13 Database Configuration Assistant, Step 10 of 12: Initialization


Parameters (Character Sets Tab)

d. On the Connection Mode tab, keep the default settings, as shown in Figure 2-14.

2-9

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


NetNumen M31(RAN) Software Installation

Figure 2-14 Database Configuration Assistant, Step 10 of 12: Initialization


Parameters (Connection Mode Tab)

e. Click the All Initialization Parameters button to open the All Initialization
Parameters dialogue box. Then click the Show Advanced Parameters button,
and set the value of the following two parameters:
l filesystemio_options: setall
l nls_date_format: 'YYYY-MM-DD HH24:MI:SS'

Caution!

Be sure to add the single quotation marks before and after YYYY-MM-DD
HH24:MI:SS, that is, type ‘YYYY-MM-DD HH24:MI:SS’ in the corresponding
cell.

2-10

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


Chapter 2 Database Instance Configuration

Figure 2-15 Database Configuration Assistant, Step 10 of 12: Initialization


Parameters (All Initialization Parameters)

f. Click Close to close the All Initialization Parameters dialogue box, and then click
Next on the Database Configuration Assistant, Step 10 of 12: Initialization
Parameters window.
12. On the Database Configuration Assistant, Step 11 of 12: Database Storage
window, do the following:
a. Click Controlfile on the Storage tree and click the Options tab on the right pane,
as shown in Figure 2-16. Then do the following to set the control file.
i. Enter 254 in the Maximum Datafiles box.
ii. Enter 32 in the Maximum Redo Log Files box.

iii. Enter 2 in the Maximum Log Member box.

2-11

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


NetNumen M31(RAN) Software Installation

Figure 2-16 Database Configuration Assistant, Step 11 of 12: Database Storage


(Controlfile)

b. Click Datafiles on the Storage tree, check that the file directory of all datafiles is
/datafile/ems/, as shown in Figure 2-17.

Figure 2-17 Database Configuration Assistant, Step 11 of 12: Database Storage


(File Directory of Datafiles)

c. Expand Redo Log Groups on the Storage tree, and then set the file size for each
redo log group, and create a redo log for the database.

For example, to set the file size of the redo log group 1, click 1, and then type 2048
in the File Size box, and select M Bytes from the drop-down box.

2-12

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


Chapter 2 Database Instance Configuration

To create a redo log group, click Create, and set the information for the new redo
log in the pop-up dialogue box, including its name and file size. The fourth redo
log group appears, as shown in Figure 2-18.

Figure 2-18 Database Configuration Assistant, Step 11 of 12: Database Storage


(File Directory of Redo Logs)

After the database storage setting is completed, click Next.

13. On the Database Configuration Assistant, Step 12 of 12: Creation Options


window, keep the default settings and click Finish, as shown in Figure 2-19.

Figure 2-19 Database Configuration Assistant, Step 12 of 12: Creation Options

14. On the Confirmation window, check that all options are properly set and then click
OK, as shown in Figure 2-20.

2-13

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


NetNumen M31(RAN) Software Installation

Figure 2-20 Confirmation Window

15. The Database Configuration Assistant window shows the process of copying
database files and creating Oracle instance, as shown in Figure 2-21.

Figure 2-21 Database Configuration Assistant (Creation Process)

16. After the creation is completed, the Database Configuration Assistant window
shows the database information, as shown in Figure 2-22. Click Exit to complete the
creation of the database instance.

2-14

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


Chapter 2 Database Instance Configuration

Figure 2-22 Database Configuration Assistant

2.4 Net Configuration of the Database


To connect the Oracle database via remote clients and use the database with a net service
name across the network, an Oracle net listener and local net service name must be
configured.
l If no listener or local net service name is configured on the server, you need to add a
listener and a local net service name for the database on the server.
l If a listener and local net service name has already been configured on the server
but the IP address of the server or the database instance name changes, you need to
modify the listener and local service name accordingly for using the database properly.
The later sections describes how to add and modify a listener and local net service name
for the Oracle database.

2.4.1 Adding a Listener and Local Net Service Name for the
Database
Prerequisites
You have successfully created the Oracle database instance.

Context
If no listener or local net service name has been created for the Oracle database, you need
to add a listener and configure a local net service name for connecting the database via
remote clients and accessing the database across a network.

Steps
1. Log in to the AIX operating system as oracle user via a graphic interface, and then
enter the command as follows:
$ netca

2-15

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


NetNumen M31(RAN) Software Installation

2. In the Oracle Net Configuration Assistant: Welcome window, select Listener


configuration and click Next, as shown in Figure 2-23.

Figure 2-23 Oracle Net Configuration Assistant: Welcome

3. In the Oracle Net Configuration Assistant: Listener Configuration window, select


Add and click Next, as shown in Figure 2-24.

Figure 2-24 Oracle Net Configuration Assistant: Listener Configuration

4. In the Oracle Net Configuration Assistant: Listener Configuration. Listener


Name window, type a name for the listener to be added in the Service Name text box
(for example, LISTENER), and click Next, as shown in Figure 2-25.

2-16

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


Chapter 2 Database Instance Configuration

Figure 2-25 Oracle Net Configuration Assistant: Listener Configuration. Listener


Name

5. In the Oracle Net Configuration Assistant: Listener Configuration. Select


Protocol window, make sure that TCP is added into the Selected Protocols list box,
and then click Next, as shown in Figure 2-26.

Figure 2-26 Oracle Net Configuration Assistant: Listener Configuration. Select


Protocol

6. In the Oracle Net Configuration Assistant: Listener Configuration. TCP/IP


Protocol window, select Use the standard port number of 1521 and then click
Next, as shown in Figure 2-27.

2-17

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


NetNumen M31(RAN) Software Installation

Figure 2-27 Oracle Net Configuration Assistant: Listener Configuration. TCP/IP


Protocol

7. In the Oracle Net Configuration Assistant: Listener Configuration. Another


Listener window, select No and click Next, as shown in Figure 2-28.

Figure 2-28 Oracle Net Configuration Assistant: Listener Configuration. Another


Listener

8. In the Oracle Net Configuration Assistant: Listener Configuration Done window


as shown in Figure 2-29, click Next.

2-18

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


Chapter 2 Database Instance Configuration

Figure 2-29 Oracle Net Configuration Assistant: Listener Configuration Done

9. In the Oracle Net Configuration Assistant: Welcome window, select Local Net
Service Name configuration and click Next, as shown in Figure 2-30.

Figure 2-30 Oracle Net Configuration Assistant: Welcome (Net Service Name)

10. In the Oracle Net Configuration Assistant: Net Service Name Configuration
window, select Add and then click Next, as shown in Figure 2-31.

2-19

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


NetNumen M31(RAN) Software Installation

Figure 2-31 Oracle Net Configuration Assistant: Net Service Name Configuration

11. In the Oracle Net Configuration Assistant: Net Service Name Configuration,
Service Name window, type the name of the database instance that you want to
access across the network in the Service Name box (for example, minos), and then
click Next, as shown in Figure 2-32.

Figure 2-32 Oracle Net Configuration Assistant: Net Service Name Configuration,
Service Name

12. In the Oracle Net Configuration Assistant: Net Service Name Configuration,
Select Protocols window, select a protocol used for accessing the database, (TCP
is recommended), as shown in Figure 2-33. Then click Next.

2-20

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


Chapter 2 Database Instance Configuration

Figure 2-33 Oracle Net Configuration Assistant: Net Service Name Configuration,
Select Protocols

13. In the Oracle Net Configuration Assistant: Net Service Name Configuration,
TCP/IP Protocol window, type the host name of the server where the database is
installed in the Host name box (for example, gsma), and select Use the standard
port number of 1521, as shown in Figure 2-34. Then click Next.

Figure 2-34 Oracle Net Configuration Assistant: Net Service Name Configuration,
TCP/IP Protocol

14. In the Oracle Net Configuration Assistant: Net Service Name Configuration, Test
window, select Yes, perform a test and then click Next, as shown in Figure 2-35.

2-21

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


NetNumen M31(RAN) Software Installation

Figure 2-35 Oracle Net Configuration Assistant: Net Service Name Configuration,
Test

15. In the Oracle Net Configuration Assistant: Net Service Name Configuration,
Connecting window, which shows the test result, click Next, as shown in Figure 2-36.

Figure 2-36 Oracle Net Configuration Assistant: Net Service Name Configuration,
Connecting

16. In the Oracle Net Configuration Assistant: Net Service Name Configuration, Net
Service Name window, use the default net service name, that is, the name of the
database instance, and then click Next, as shown in Figure 2-37.

2-22

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


Chapter 2 Database Instance Configuration

Figure 2-37 Oracle Net Configuration Assistant: Net Service Name Configuration,
Net Service Name

17. In the Oracle Net Configuration Assistant: Net Service Name Configuration,
Another Net Service Name? window, select No and then click Next, as shown in
Figure 2-38.

Figure 2-38 Oracle Net Configuration Assistant: Net Service Name Configuration,
Another Net Service Name?

18. In the Oracle Net Configuration Assistant: Net Service Name Configuration Done
window, click Next, as shown in Figure 2-39.

2-23

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


NetNumen M31(RAN) Software Installation

Figure 2-39 Oracle Net Configuration Assistant: Net Service Name Configuration
Done

19. In the Oracle Net Configuration Assistant: Welcome window, click Finish to
complete the configuration of listener and net service name.
– End of Steps –

Result
A listener.ora configuration file and a tnsnames.ora configuration file appear under
the ORACLE_HOME/network/admin/ directory on the server.

2.4.2 Modifying the Listener and Local Net Service Name for the
Database
Prerequisites
The listener and local net service name has been created for the pre-installed instance
before the delivery of the server. But the IP address of the server or the instance name
changes on field.

Context
If the IP address of the server or the instance name changes, it is required to modify the
original listener and local net service name accordingly for using the database instance.

Note:
Modifying the listener configuration will stop the listener. The database cannot be accessed
via remote client before the listener is started again.

2-24

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


Chapter 2 Database Instance Configuration

Steps
1. Log in to the AIX operating system as oracle user via a graphic interface, and then
enter the command as follows:
$ netca
2. In the Oracle Net Configuration Assistant: Welcome window, select Listener
configuration and click Next.
3. In the Oracle Net Configuration Assistant: Listener Configuration window, select
Reconfigure and click Next, as shown in Figure 2-40.

Figure 2-40 Oracle Net Configuration Assistant: Listener Configuration


(Reconfigure)

4. In the Oracle Net Configuration Assistant: Select Listener window, select the
listener to be modified from the drop-down box, and then click Next, as shown in
Figure 2-41.

2-25

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


NetNumen M31(RAN) Software Installation

Figure 2-41 Oracle Net Configuration Assistant: Select Listener

5. In the Oracle Net Configuration Assistant dialogue box, prompting you to stop the
listener or not, click Yes, as shown in Figure 2-42.

Figure 2-42 Oracle Net Configuration Assistant

6. The consequent steps for modifying the listener are similar to those for creating a
new listener. Refer to the previous section “Adding Listener and Net Services for the
Database” for detailed instructions.
7. After modifying the listener successfully, select Local Net Service Name
configuration, and click Next in the Oracle Net Configuration Assistant: Welcome
window.

8. In the Oracle Net Configuration Assistant: Net Service Name Configuration


window, select Reconfigure and then click Next, as shown in Figure 2-43.

2-26

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


Chapter 2 Database Instance Configuration

Figure 2-43 Oracle Net Configuration Assistant: Net Service Name Configuration
(Reconfigure)

9. In the Oracle Net Configuration Assistant: Net Service Name Configuration,


Select Net Service Name window, select the net service name to be modified from
the drop-down box and click Next, as shown in Figure 2-44.

Figure 2-44 Oracle Net Configuration Assistant: Net Service Name Configuration,
Select Net Service Name

10. The consequent steps for modifying the net service name are similar to those for
adding a new net service name. Refer to the previous section “Adding Listener and
Net Services for the Database” for detailed instructions.
– End of Steps –

2-27

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


NetNumen M31(RAN) Software Installation

2.5 Inspections After Database Instance Configuration


After the configuration of an Oracle database instance, you need do the following
inspections to ensure that the instance can be properly used.
l Check whether the database instance can be successfully connected, started up, and
shut down.
l Check whether the listener can be successfully started and stopped for the database
instance.
l Check whether the character set of the database instance is correctly set.
l Check whether the date format of the database instance is correctly set.

Note:
The following check procedures are based on the supposition that:
l The database SID is “ems”.
l The listener name is “LISTENER”.

Checking the Database Service


The following describes how to use the command line utility, SQL Plus, to check whether
the database service can be successfully connected, started, and stopped.
1. Log in to the operating system as oracle user via a graphic interface, open a terminal
window, and then run the following command to log in to the SQL Plus.
$ sqlplus /nolog
After successful login, the terminal shows the release and copyright information of
SQL Plus followed by the following prompt:
SQL>
2. Check whether the database instance can be successfully connected by the following
command:
SQL> connect sys/oracle@ems as sysdba
The returned message Connected. indicates that the database is successfully
connected.
3. Check whether the database can be properly shut down by the following command:
SQL> shutdown immediate;
If the database is successfully shut down, the following messages are returned.

Database closed.
Database dismounted.
ORACLE instance shut down.

4. Check whether the database can be successfully started up by the following command:

2-28

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


Chapter 2 Database Instance Configuration

SQL> startup
If the database is successfully started, the following messages are returned.

ORACLE instance started.

Total System Global Area 2550136832 bytes


Fixed Size 1980808 bytes
Variable Size 553649784 bytes
Database Buffers 1979711488 bytes
Redo Buffers 14794752 bytes
Database mounted.
Database opened.

5. After completing the previous checks, run the following command to exit the SQL Plus.
SQL> exit

Checking the Listener Service


The following describes how to check whether the listener service can be successfully
started and stopped.
1. Start the listener by the following command:
$ lsnrctl start
The system starts the listener for the Oracle database and shows the status of the
listener. And finally, the message The command completed successfully is returned.
2. Stop the listener by the following command:
$ lsnrctl stop
After the listener is stopped, the message The command completed successfully is
returned.

Checking the Character Set


The following describes how to check whether the character set of the database server
and client is correctly set.
1. Run the following command to log in to the database (SID: ems) as sys user.
$ sqlplus sys/oracle@ems as sysdba
After successful login, the terminal shows the release and copyright information of
SQL Plus and the connection information followed by the following prompt:
SQL>
2. Check the character set of the server by the following command:
SQL> select userenv('language') from dual;
The following information is returned as follows:

2-29

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


NetNumen M31(RAN) Software Installation

USERENV('LANGUAGE')
-------------------------------------------
AMERICAN_AMERICA.ZHS16GBK

The returned character set AMERICAN_AMERICA.ZHS16GBK indicates that the


character set of the database server is correct.
3. Run the following command to exit the SQL Plus.
SQL> exit
4. Check the character set of the client by the following command:
$ echo $NLS_LANG
The returned character set AMERICAN_AMERICA.ZHS16GBK indicates that the
character set of the database client is correct.

Checking the Date Format


The following describes how to check the date format of the database.
1. Run the following command to log in to the database (SID: ems) as sys user.
$ sqlplus sys/oracle@ems as sysdba
After successful login, the terminal shows the release and copyright information of
SQL Plus and the connection information followed by the following prompt:
SQL>
2. View the date format of the database by the following command:
SQL> show parameter nls_date_format
The parameter value is returns as follows:
NAME TYPE VALUE
---------------------- ------------------- -----------------------
nls_date_format string YYYY-MM-DD HH24:MI:SS

3. Check whether the returned date format is 'YYYY-MM-DD HH24:MI:SS'.


If yes, run the following command to exit the SQL Plus. And the inspections of the
database are completed.
SQL> exit
If no, do the following to change the date format of the datebase to 'YYYY-MM-DD
HH24:MI:SS'.
a. Shut down the database by the following command:
SQL> shutdown immediate
b. Create a pfile from the spfile by the following command:
SQL> create pfile from spfile;
An init${ORACLESID}.ora file is generated under the default directory. In the
AIX operating system, the default directory is ${ORACLE_HOME}/dbs/.

2-30

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


Chapter 2 Database Instance Configuration

c. Add the following line to the init${ORACLESID}.ora file.


*.nls_date_format='YYYY-MM-DD HH24:MI:SS'
d. Save the modification to the spfile by the following command:
SQL> create spfile from pfile;
e. Start the database by the following command:
SQL> startup;

2-31

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


NetNumen M31(RAN) Software Installation

This page intentionally left blank.

2-32

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


Chapter 3
Installation of the EMS Server
Software
Table of Contents
Introduction to the Installation of EMS Server Software ..............................................3-1
Preparations Before Installing the EMS Server Software ............................................3-1
Installing the EMS Server Program.............................................................................3-2
Checking the Installation Directory of Server Software .............................................3-13
Starting the EMS Server...........................................................................................3-13

3.1 Introduction to the Installation of EMS Server


Software
The installation of server software in the AIX operating system on the server includes three
procedures:
1. Preparation before the installation
2. Installation of the EMS server software
3. Inspection after the installation

3.2 Preparations Before Installing the EMS Server


Software
Before you install the NetNumen M31 server software, do the following check and
preparation works:
1. Check that the AIX operating system and Oracle Database 10g or 11g have been
properly installed on the IBM server.
2. Obtain the installation CD of the NetNumen M31 server software.
3. Log in to the AIX operating system as root, and then create an “omc” user for installing
the EMS server software as follows:
a. Use the following command to create an omc user:

useradd -u 101 -g other -d /export/home/omc -m omc

b. Change the owner of the directory /export/home/omc/ to “omc” by the following


command:

chown -R omc /export/home/omc/

3-1

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


NetNumen M31(RAN) Software Installation

c. Change the group ownership of the directory /export/home/omc/ to “other” by


the following command:
chgrp -R other /export/home/omc/

3.3 Installing the EMS Server Program


Prerequisites
l The operating system has been installed on the server and is running properly.
l The hardware configuration of the server meets the installation requirements of the
EMS server program.
l The installation files have been transferred to the server.
l The Oracle database service has been started.
l The omc user has been created with the authority of installing the EMS server
software.

Context

Note:
The installation procedure varies depending on the version of the EMS software you are
installing.

Steps
1. Log in to the AIX operating system as the omc user.
2. Use the cd command to change the current directory to the directory where the
installation files are located.
3. Run the setup.sh file to start the installation of the EMS server software as follows.
$ setup.sh
The system starts unzipping the installation files and after the completion of unzipping,
the NetNumen Setup-Select language window appears.

4. On the NetNumen Setup-Select language window, select “English” from the


drop-down list box and click Next, as shown in Figure 3-1.

3-2

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


Chapter 3 Installation of the EMS Server Software

Figure 3-1 NetNumen Setup-Select Language Window

5. On the NetNumen Setup-License agreement window, select I accept the license


agreement and click Next, as shown in Figure 3-2.

Figure 3-2 NetNumen Setup-License Agreement Window

6. On the NetNumen Setup-Select installation style window, select Normal


Installation and Server Program, and then click Next, as shown in Figure 3-3.

3-3

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


NetNumen M31(RAN) Software Installation

Figure 3-3 NetNumen Setup-Select Installation Style Window

Two installation styles are optional as explained below.

l Normal Installation: This installation style requires you to complete the whole
procedure step by step for installing a new version of the EMS, including selecting
a language, and setting an installation path.
l Delta Installation: This installation style is generally used to update a previous
installation of the EMS. Only new functions will be installed on the base of the
previous version. It is unnecessary to set some basic information again, such as
the language and the installation path.
Three installation types are optional as explained below.
l Client And Server Program: Select this installation type if you want to install
both the client and server programs on the server.
l Server Program: Select this installation type if you want to install only the server
program on the server.
l Client Program: Select this installation type if you want to install only the client
program on the server.

7. On the NetNumen Setup-Network scale window, select a network scale according


to the actual situation of the network to be managed, and then click Next, as shown
in Figure 3-4.

3-4

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


Chapter 3 Installation of the EMS Server Software

Figure 3-4 NetNumen Setup-Network Scale Window

Table 3-1 provides the information of each scale for your reference, including the
physical memory of the server, the alarm pool capacity (quantity of alarm records),
the maximum number of concurrent clients, and the maximum number of managed
cells.

Table 3-1 Network Scale Parameters

Scale Physical Alarm Pool Concurrent Cell Management


Memory Capacity Clients Capacity

Scale1 4 GB 5000 20 1000

Scale2 16 GB 20000 50 5000

Scale3 32 GB 20000 100 10000

Scale4 64 GB 20000 200 15000

Scale5 64 GB 20000 200 20000

• Scale 1 is generally used in a development environment, laboratory, or pilot project.

8. On the NetNumen Setup-Select product window as shown in Figure 3-5, do the


following:
a. Select the products to be installed as needed. Generally, UCA and Mobile EMS
Platform are required for the installation of the server.
b. If you want to install the server program under another path instead of the default
one, type a new path in the Program Area Path box, or click Browse to select a
new path in the pop-up dialog box.
If you are prompted that the folder does not exist, click Yes in the Confirm dialogue
box to create the folder for the installation.
c. Click Next.

3-5

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


NetNumen M31(RAN) Software Installation

Figure 3-5 NetNumen Setup-Select Product Window

Note:
The optional products on the All Products tree vary with the actual installation
package for specific equipment, for example, WCDMA and GSM.

9. On the NetNumen Setup-Database connection config window, set the database


parameters according to the information of the actual database previously created, as
shown in Figure 3-6.

3-6

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


Chapter 3 Installation of the EMS Server Software

Figure 3-6 NetNumen Setup-Database Connection Config Window

Table 3-2 explains the parameters on the NetNumen Setup-Database connection


config window.

Table 3-2 Explanation of Parameters on the NetNumen Setup-Database Connection


Config Window

Parameter Description

Database type Select a database type according to the database installed for the
EMS, Oracle or SQL server. At present, the EMS only supports
Oracle database.

Database IP or hostname Enter the IP address or hostname of the server on which the EMS
database is installed.

Database port Set the port No. of the database instance. The default port No.
is 1521.
If several database instances have been created, use the port No.
of the instance used by the EMS.

SID Enter the System Identifier (SID) of the database.

Database superuser Enter the superuser name of the database.


name

Password Enter the password of the superuser.

10. Click Test Database Connection to check that the database can be successfully
connected. Click OK in the message box prompting the successful connection. Then
click Next on the NetNumen Setup-Database connection config window.
11. On the NetNumen Setup-Database config window, keep the default paths and size
of database files and tablespaces, or set them according to the actual requirements,
and then click Next, as shown in Figure 3-7.

3-7

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


NetNumen M31(RAN) Software Installation

Figure 3-7 NetNumen Setup-Database Config Window

12. On the NetNumen Setup-Host information config window, enter the IP address of
the EMS server in the The master server address box, and then click Next, as shown
in Figure 3-8.

Figure 3-8 NetNumen Setup-Host Information Config Window

13. On the NetNumen Setup-System information detection window, check the system
detection result, and then click Next, as shown in Figure 3-9,

3-8

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


Chapter 3 Installation of the EMS Server Software

Figure 3-9 NetNumen Setup-System Information Detection Window

14. On the NetNumen Setup-Installation Information Confirm window, check that the
installation information is correct and then click Install, as shown in Figure 3-10.

Figure 3-10 NetNumen Setup-Installation Information Confirm Window

15. The NetNumen Setup-Unzip and copy files window shows the unzipping and
copying process, as shown in Figure 3-11. After the file unzipping and copying is
completed, click Next.

3-9

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


NetNumen M31(RAN) Software Installation

Figure 3-11 NetNumen Setup-Unzip And Copy File Window

16. On the NetNumen Setup-Select EMS Install Type window, select Normal Install
and then click Next, as shown in Figure 3-12.

Figure 3-12 NetNumen Setup-Select EMS Install Type

17. In the pop-up Confirm dialogue box as shown in Figure 3-13, click Yes to execute
necessary SQL scripts. The NetNumen Setup-Installation database window shows
the running process of the SQL scripts, as shown in Figure 3-14. After the process is
completed, click Next.

3-10

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


Chapter 3 Installation of the EMS Server Software

Figure 3-13 Confirm Dialogue Box (Execute SQLs)

Figure 3-14 NetNumen Setup-Installation Database Window

18. On the NetNumen Setup-Parameter set window, keep the default settings of the
parameters and then click Next, as shown in Figure 3-15.

Figure 3-15 NetNumen Setup-Parameter Set Window

3-11

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


NetNumen M31(RAN) Software Installation

19. The NetNumen Setup-System initialization window shows the initialization process
of the system, as shown in Figure 3-16. After the initialization is completed, click Next.

Figure 3-16 NetNumen Setup-System Initialization Window

20. The NetNumen Setup-Installation finished window shows the installation result of
the EMS server program, as shown in Figure 3-17. Click Finish to complete the
installation and close the window.

Figure 3-17 NetNumen Setup-Installation Finished Window

– End of Steps –

3-12

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


Chapter 3 Installation of the EMS Server Software

3.4 Checking the Installation Directory of Server


Software
After the installation of the EMS server software is completed, check that the installation
directory on the server contains the following subdirectories:

Subdirectory Contents

jdk JAVA running environment for the AIX operating system

update Program for automatic upgrade of the EMS

ums-server EMS server program

ums-client EMS client program

ERT Program supporting the use of Embedded Remote Terminal


(ERT)

3.5 Starting the EMS Server


To start the EMS server, change the current directory to \ums-server and run the
following command:
$ console.sh
After the server is successfully started, the console window appears, listing the information
of started processes in the left pane, as shown in Figure 3-18. The icon before a process
name indicates that the process is successfully started.

Figure 3-18 NetNumen Unified Management System-Console

3-13

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


NetNumen M31(RAN) Software Installation

This page intentionally left blank.

3-14

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


Chapter 4
Installation of the EMS Client
Software
Table of Contents
Introduction to the Installation of EMS Client Software................................................4-1
Installing the EMS Client Program ..............................................................................4-1
Checking the Installation Directory of Client Software.................................................4-7
Starting the EMS Client ..............................................................................................4-8

4.1 Introduction to the Installation of EMS Client


Software
The client software is generally installed in a Windows operating system on a computer.
For the installation procedure of a Windows operating system, refer to the installation guide
of Microsoft.
The installation of the EMS client software in the Windows operating system includes three
procedures:
1. Preparation before the installation
2. Installation of the client software
3. Inspection after the installation

4.2 Installing the EMS Client Program


Prerequisites
l The Windows operating system has been installed on the client computer and is
running properly.
l The hardware configuration of the computer meets the installation requirements of
client program.
l The installation files are available on the client computer.

4-1

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


NetNumen M31(RAN) Software Installation

Warning!
Be sure to exit all the other programs before installing the client program to avoid possible
error during the installation.

Steps
1. Open the directory of the installation files, and then double-click the setup.bat
file. The Install window appears to prompt you to enter the path for unzipping the
installation files.
2. Press Enter to unzip the installation files to the default path, or type another path.
Then the system starts unzipping the installation files.
After the system completes the unzipping of files, the NetNumen Setup-Select
language window appears.
3. On the NetNumen Setup-Select Language window, select English from the
drop-down box, and then click Next, as shown in Figure 4-1.

Figure 4-1 NetNumen Setup-Select Language

4. On the NetNumen Setup-License agreement window, select I accept the license


agreement, and then click Next, as shown in Figure 4-2.

4-2

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


Chapter 4 Installation of the EMS Client Software

Figure 4-2 NetNumen Setup-License Agreement

5. On the NetNumen Setup-Select installation style window, select Normal


Installation and Client Program, and then click Next, as shown in Figure 4-3.

Figure 4-3 NetNumen Setup-Select Installation Style

6. On the NetNumen Setup-Installation product window as shown in Figure 4-4, do


the following:
a. Select the products to be installed as needed. Generally, UCA and Mobile EMS
Platform are required for the installation of the server.
b. If you want to install the server program under another path instead of the default
one, type a new path in the Program Area Path box, or click Browse to select a
new path in the pop-up dialog box.

4-3

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


NetNumen M31(RAN) Software Installation

If you are prompted that the folder does not exist, click Yes in the Confirm dialogue
box to create the folder for the installation.
c. Click Next.

Figure 4-4 NetNumen Setup-Installation Product

7. On the NetNumen Setup-System information detection window, check the


detection result and make sure that the environment of the operating system meets
the installation requirements, and then click Next, as shown in Figure 4-5.

Figure 4-5 NetNumen Setup-System Information Detection

4-4

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


Chapter 4 Installation of the EMS Client Software

8. On the NetNumen Setup-Installation Information Confirm window, check and make


sure that the installation information is correct, and then click Install, as shown in
Figure 4-6.

Figure 4-6 NetNumen Setup-Installation Information Confirm

9. The system starts unzipping and copying files to install the client program and shows
the process on the NetNumen Setup-Unzip and copy files window. After the
completion of unzipping and copying, click Next, as shown in Figure 4-7.

Figure 4-7 NetNumen Setup-Unzip and Copy File

10. On the NetNumen Setup-Parameter set window, keep the default settings and click
Next, as shown in Figure 4-8.

4-5

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


NetNumen M31(RAN) Software Installation

Figure 4-8 NetNumen Setup-Parameter Set

11. The NetNumen Setup-System initialization window shows the initialization process
of the client software, as shown in Figure 4-9. When prompted to initialize all client
scenes, click Yes. After the initialization of all client scenes is completed, click Next.

Figure 4-9 NetNumen Setup-System Initialization

12. On the NetNumen Setup-Installation finished window, click Finish to complete the
installation of the client software, as shown in Figure 4-10.

4-6

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


Chapter 4 Installation of the EMS Client Software

Figure 4-10 NetNumen Setup-Installation Finished

– End of Steps –

Result
The NetNumen Unified Management System program group appears under All
Programs on the Start menu. It contains the following four programs:

Program Function

NetNumen Client Run the NetNumen M31 client.

NetNumen Client Portal Run the NetNumen M31 client portal, which is used for Logging
in to a specific functional module, such as the fault management
module.

NetNumen Config Center Configure the system parameters of the client.

NetNumen Uninstall Tool Uninstall the client software.

4.3 Checking the Installation Directory of Client


Software
Prerequisites
The NetNumen M31 client software has been installed.

Context
Installation check is necessary to ensure that the client software has been correctly
installed.

4-7

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


NetNumen M31(RAN) Software Installation

Steps
l Check whether the following subdirectories are available in the installation directory of
the EMS client software:

Subdirectory Content

jdk Java running environment for Windows operating system

ums-client EMS client program

update-info Automatic upgrade application

– End of Steps –

4.4 Starting the EMS Client


Prerequisites
l The client software has been successfully installed.
l The communication between the client and the server is normal.

Steps
1. Do one of the following to open the Login dialogue box as shown in Figure 4-11:
l Double-click NetNumen Client on the desktop.
l Click the Start button, and then point to All Programs. Point to NetNumen
Unified Management System, and then click NetNumen Client.

Figure 4-11 Login Dialogue Box

The following explains the parameters in the Login dialogue box.


l User Name: The default initial user name is admin. Another user name that has
been authorized can also be used for login.
l Password: The initial password of the admin user is null, that is, no password.
Modify the password immediately after successfully logging in to the client.
l Server Address: It is the IP address of the NetNumen M31 server that is running
properly.

4-8

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


Chapter 4 Installation of the EMS Client Software

The client can be used to access multiple servers. To distinguish multiple servers in
different offices, you can edit the office information of a server and save the information
for convenient login. The following describes how to add the information of a server.
i. In the Login dialogue box, click to open the Config Bureau dialogue box,
as shown in Figure 4-12.

Figure 4-12 Config Bureau Dialogue Box

ii. Click Add. In the Config the bureau name and IP address dialogue box, type a
name for the server and the IP address of the server, and then click OK, as shown
in Figure 4-13.

Figure 4-13 Config the Bureau Name and IP Address Dialogue Box

iii. Click OK in the Config Bureau dialogue box.


Then the information of the server appears in the drop-down list after you click the
Server Address drop-down box. You can select it from the list, and then click OK to
log in to the server conveniently.
2. In the Login dialogue box, enter the user name, password, and the IP address of the
server, and then click OK.

– End of Steps –

Result
For the first login, a Confirm dialogue box appears, prompting that the client successfully
gets the configuration information from the server. Click OK to connect the server and
log in to the client. The NetNumen Unified Management System (EMS Client) window
appears.

4-9

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


NetNumen M31(RAN) Software Installation

This page intentionally left blank.

4-10

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


Appendix A
Uninstallation of the EMS
Client Software
Context
If you want to remove the EMS client software previously installed on your computer, you
can perform the uninstallation procedure as follows.

Steps
1. On the desktop of the Windows operating system, click the Start button, and then point
to All Programs. Point to NetNumen Unified Management System, and then click
NetNumen Uninstall Tool.
2. In the Uninstall-Uninstall database selection window, click Next.

3. In the Uninstall-Uninstall description window, click Start uninstall.


If a dialogue box appears, prompting you to shut down the Launcher.exe first, click
Yes.

4. In the pop-up Confirm dialogue box, click Yes to start the uninstallation.
The Uninstall-Start uninstall window shows the uninstallation process.
5. After the uninstallation is completed, click Finish.
– End of Steps –

A-1

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


NetNumen M31(RAN) Software Installation

This page intentionally left blank.

A-2

SJ-20101227165724-003|2011-04-18(R1.1) ZTE Proprietary and Confidential


Figures
Figure 1-1 Software Architecture of NetNumen M31 ................................................. 1-2
Figure 1-2 Software Installation Flow of NetNumen M31........................................... 1-5
Figure 2-1 Database Configuration Assistant: Welcome ........................................... 2-2
Figure 2-2 Database Configuration Assistant, Step 1 of 12: Operations .................... 2-3
Figure 2-3 Database Configuration Assistant, Step 2 of 12: Database
Templates ............................................................................................... 2-3
Figure 2-4 Database Configuration Assistant, Step 3 of 12: Database
Identification ........................................................................................... 2-4
Figure 2-5 Database Configuration Assistant, Step 4 of 12: Management
Options ................................................................................................... 2-4
Figure 2-6 Database Configuration Assistant, Step 5 of 12: Database
Credentials ............................................................................................. 2-5
Figure 2-7 Database Configuration Assistant, Step 6 of 12: Storage Options............ 2-5
Figure 2-8 Database Configuration Assistant, Step 7 of 12: Database File
Location.................................................................................................. 2-6
Figure 2-9 Database Configuration Assistant, Step 8 of 12: Recovery
Configuration .......................................................................................... 2-7
Figure 2-10 Database Configuration Assistant, Step 9 of 12: Database
Content................................................................................................... 2-7
Figure 2-11 Database Configuration Assistant, Step 10 of 12: Initialization
Parameters (Memory Tab) ...................................................................... 2-8
Figure 2-12 Database Configuration Assistant, Step 10 of 12: Initialization
Parameters (Sizing Tab) ......................................................................... 2-9
Figure 2-13 Database Configuration Assistant, Step 10 of 12: Initialization
Parameters (Character Sets Tab)............................................................ 2-9
Figure 2-14 Database Configuration Assistant, Step 10 of 12: Initialization
Parameters (Connection Mode Tab)...................................................... 2-10
Figure 2-15 Database Configuration Assistant, Step 10 of 12: Initialization
Parameters (All Initialization Parameters) ............................................. 2-11
Figure 2-16 Database Configuration Assistant, Step 11 of 12: Database Storage
(Controlfile) ........................................................................................... 2-12
Figure 2-17 Database Configuration Assistant, Step 11 of 12: Database Storage
(File Directory of Datafiles).................................................................... 2-12
Figure 2-18 Database Configuration Assistant, Step 11 of 12: Database Storage
(File Directory of Redo Logs) ................................................................ 2-13

I
NetNumen M31(RAN) Software Installation

Figure 2-19 Database Configuration Assistant, Step 12 of 12: Creation


Options ................................................................................................. 2-13
Figure 2-20 Confirmation Window........................................................................... 2-14
Figure 2-21 Database Configuration Assistant (Creation Process) .......................... 2-14
Figure 2-22 Database Configuration Assistant ........................................................ 2-15
Figure 2-23 Oracle Net Configuration Assistant: Welcome...................................... 2-16
Figure 2-24 Oracle Net Configuration Assistant: Listener Configuration .................. 2-16
Figure 2-25 Oracle Net Configuration Assistant: Listener Configuration. Listener
Name.................................................................................................... 2-17
Figure 2-26 Oracle Net Configuration Assistant: Listener Configuration. Select
Protocol ................................................................................................ 2-17
Figure 2-27 Oracle Net Configuration Assistant: Listener Configuration. TCP/IP
Protocol ................................................................................................ 2-18
Figure 2-28 Oracle Net Configuration Assistant: Listener Configuration. Another
Listener................................................................................................. 2-18
Figure 2-29 Oracle Net Configuration Assistant: Listener Configuration
Done..................................................................................................... 2-19
Figure 2-30 Oracle Net Configuration Assistant: Welcome (Net Service
Name)................................................................................................... 2-19
Figure 2-31 Oracle Net Configuration Assistant: Net Service Name
Configuration ........................................................................................ 2-20
Figure 2-32 Oracle Net Configuration Assistant: Net Service Name Configuration,
Service Name ....................................................................................... 2-20
Figure 2-33 Oracle Net Configuration Assistant: Net Service Name Configuration,
Select Protocols.................................................................................... 2-21
Figure 2-34 Oracle Net Configuration Assistant: Net Service Name Configuration,
TCP/IP Protocol .................................................................................... 2-21
Figure 2-35 Oracle Net Configuration Assistant: Net Service Name Configuration,
Test....................................................................................................... 2-22
Figure 2-36 Oracle Net Configuration Assistant: Net Service Name Configuration,
Connecting ........................................................................................... 2-22
Figure 2-37 Oracle Net Configuration Assistant: Net Service Name Configuration,
Net Service Name................................................................................. 2-23
Figure 2-38 Oracle Net Configuration Assistant: Net Service Name Configuration,
Another Net Service Name? ................................................................. 2-23
Figure 2-39 Oracle Net Configuration Assistant: Net Service Name Configuration
Done..................................................................................................... 2-24
Figure 2-40 Oracle Net Configuration Assistant: Listener Configuration
(Reconfigure)........................................................................................ 2-25

II
Figures

Figure 2-41 Oracle Net Configuration Assistant: Select Listener ............................. 2-26
Figure 2-42 Oracle Net Configuration Assistant ...................................................... 2-26
Figure 2-43 Oracle Net Configuration Assistant: Net Service Name Configuration
(Reconfigure)........................................................................................ 2-27
Figure 2-44 Oracle Net Configuration Assistant: Net Service Name Configuration,
Select Net Service Name ...................................................................... 2-27
Figure 3-1 NetNumen Setup-Select Language Window ............................................ 3-3
Figure 3-2 NetNumen Setup-License Agreement Window ........................................ 3-3
Figure 3-3 NetNumen Setup-Select Installation Style Window .................................. 3-4
Figure 3-4 NetNumen Setup-Network Scale Window ................................................ 3-5
Figure 3-5 NetNumen Setup-Select Product Window ................................................ 3-6
Figure 3-6 NetNumen Setup-Database Connection Config Window .......................... 3-7
Figure 3-7 NetNumen Setup-Database Config Window............................................. 3-8
Figure 3-8 NetNumen Setup-Host Information Config Window .................................. 3-8
Figure 3-9 NetNumen Setup-System Information Detection Window......................... 3-9
Figure 3-10 NetNumen Setup-Installation Information Confirm Window .................... 3-9
Figure 3-11 NetNumen Setup-Unzip And Copy File Window ................................... 3-10
Figure 3-12 NetNumen Setup-Select EMS Install Type ........................................... 3-10
Figure 3-13 Confirm Dialogue Box (Execute SQLs) ................................................ 3-11
Figure 3-14 NetNumen Setup-Installation Database Window .................................. 3-11
Figure 3-15 NetNumen Setup-Parameter Set Window ............................................ 3-11
Figure 3-16 NetNumen Setup-System Initialization Window.................................... 3-12
Figure 3-17 NetNumen Setup-Installation Finished Window.................................... 3-12
Figure 3-18 NetNumen Unified Management System-Console ............................... 3-13
Figure 4-1 NetNumen Setup-Select Language.......................................................... 4-2
Figure 4-2 NetNumen Setup-License Agreement ...................................................... 4-3
Figure 4-3 NetNumen Setup-Select Installation Style ................................................ 4-3
Figure 4-4 NetNumen Setup-Installation Product ...................................................... 4-4
Figure 4-5 NetNumen Setup-System Information Detection ...................................... 4-4
Figure 4-6 NetNumen Setup-Installation Information Confirm.................................... 4-5
Figure 4-7 NetNumen Setup-Unzip and Copy File..................................................... 4-5
Figure 4-8 NetNumen Setup-Parameter Set ............................................................. 4-6
Figure 4-9 NetNumen Setup-System Initialization ..................................................... 4-6
Figure 4-10 NetNumen Setup-Installation Finished ................................................... 4-7
Figure 4-11 Login Dialogue Box ................................................................................ 4-8
Figure 4-12 Config Bureau Dialogue Box .................................................................. 4-9

III
NetNumen M31(RAN) Software Installation

Figure 4-13 Config the Bureau Name and IP Address Dialogue Box ......................... 4-9

IV
Tables
Table 1-1 Software Configuration of the Server ......................................................... 1-4
Table 1-2 Minimal Hardware Configuration of the Client ............................................ 1-4
Table 1-3 Software Configuration of the Client .......................................................... 1-5
Table 3-1 Network Scale Parameters ........................................................................ 3-5
Table 3-2 Explanation of Parameters on the NetNumen Setup-Database
Connection Config Window ...................................................................... 3-7

V
Tables

This page intentionally left blank.


Glossary
EMS
- Network Element Management System
FTP
- File Transfer Protocol
GSM
- Global System for Mobile Communication
J2EE
- JAVA 2 platform Enterprise Edition
PC
- Personal Computer
RAID
- Redundant Array of Independent Disks
WCDMA
- Wideband Code Division Multiple Access

VII

Vous aimerez peut-être aussi