ZXUN USPP

Universal Subscriber Profile Platform

Software Installation Guide

Version: V4.11.10

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: [email protected]
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.3 2011-07-27 l Modified the virtual IPs and ports of the DBIO and the Web
agent server (WEBAGNET) in “1.2 Networking Planning”
l Updated the version packages in “5.2.2 Setting the DTF Tool”
and “5.2.6 Loading and Activating OMP Versions”
l Updated “7.4 Web Agent Installaion”

R1.2 2011-06-09 Updated the steps of “7.3.3 Installing a GUI Agent”.

R1.1 2011-05-30 Modified the description about the network planning and the Web
agent.

R1.0 2011-04-07 First edition.

Serial Number: SJ-20110105143446-003

Publishing Date: 2011-07-27(R1.3)

Contents
About This Manual ......................................................................................... I
Declaration of RoHS Compliance ................................................................. I
Chapter 1 Introduction to Software Installation ...................................... 1-1
1.1 System Architecture ........................................................................................... 1-1
1.2 Networking Planning........................................................................................... 1-7
1.3 Naming Rules .................................................................................................. 1-15
1.3.1 Naming Rule for Device Names .............................................................. 1-15
1.3.2 Rules for Operating System Password..................................................... 1-16
1.4 Installation Flow ............................................................................................... 1-17

Chapter 2 OMM Installation ....................................................................... 2-1

2.1 Introduction to OMM ........................................................................................... 2-1
2.1.1 Introduction to OMM ................................................................................. 2-1
2.1.2 OMM Installation and Configuration Requirements ..................................... 2-1
2.2 OMM Software Installation Flow .......................................................................... 2-3
2.3 Preparations ...................................................................................................... 2-4
2.3.1 Preparations before OMM Software Installation.......................................... 2-4
2.3.2 Configuring System Services .................................................................... 2-4
2.3.3 Disabling the Linux firewall........................................................................ 2-5
2.3.4 Disabling the Linux Security Policy ............................................................ 2-5
2.3.5 Optimizing Linux Kernel Parameters.......................................................... 2-6
2.3.6 Setting the HTTP Service.......................................................................... 2-7
2.3.7 Setting FTP Service on CGSL ................................................................... 2-9
2.3.8 Installing JRE on the Debugging PC .........................................................2-11
2.4 FireBird Database Installation ............................................................................2-11
2.4.1 Checking the Sqlite Database ..................................................................2-11
2.4.2 Installing the Firebird Database ............................................................... 2-13
2.5 OMM Server Installation ................................................................................... 2-15
2.5.1 Installing OMM Server Installation Agent.................................................. 2-15
2.5.2 Installing OMM Server ............................................................................ 2-16
2.5.3 Setting FTP after Installing OMM Server .................................................. 2-21
2.6 Starting the OMM Server .................................................................................. 2-22
2.7 OMM Client Setting and Login........................................................................... 2-23
2.7.1 Setting Internet Explorer for an OMM Client ............................................. 2-23

I
 2.7.2 Logging In to OMM................................................................................. 2-25

Chapter 3 EMS Installation ........................................................................ 3-1

3.1 Introduction to EMS ............................................................................................ 3-1
3.1.1 Introduction to EMS .................................................................................. 3-1
3.1.2 EMS Installation and Configuration Requirements ...................................... 3-1
3.2 EMS Software Installation Flow ........................................................................... 3-3
3.3 EMS Server Installation ...................................................................................... 3-3
3.3.1 Installing EMS Server ............................................................................... 3-3
3.3.2 Starting EMS Server............................................................................... 3-15
3.4 EMS Client Installation...................................................................................... 3-17
3.4.1 Installing Operating System for an EMS Client ......................................... 3-17
3.4.2 Installing Antivirus Software .................................................................... 3-18
3.4.3 Installing EMS Client .............................................................................. 3-18
3.4.4 EMS Client Login ................................................................................... 3-24

Chapter 4 Configuration for OMM Accessing to EMS............................. 4-1

4.1 Introduction to OMM Access ............................................................................... 4-1
4.2 Importing the License ......................................................................................... 4-2
4.3 Creating a USPP Node ....................................................................................... 4-3
4.4 Creating a Network Element Agent...................................................................... 4-4
4.5 Starting a Network Element Agent ....................................................................... 4-6
4.6 Updating USPP Version Number ......................................................................... 4-8
4.7 Synchronizing the License .................................................................................. 4-9
4.8 Adding an NE Office of USPP ............................................................................4-11

Chapter 5 Version Loading ........................................................................ 5-1

5.1 Introduction to Version Loading ........................................................................... 5-1
5.2 Version Loading for OMP .................................................................................... 5-2
5.2.1 Checking the DTF Port ............................................................................. 5-2
5.2.2 Setting the DTF Tool................................................................................. 5-3
5.2.3 Setting OMP Bootup Mode ....................................................................... 5-9
5.2.4 Checking the first Power-on of OMP ........................................................ 5-10
5.2.5 Formatting a Hard Disk ........................................................................... 5-12
5.2.6 Loading and Activating OMP Versions ..................................................... 5-16
5.2.7 Setting the OMP..................................................................................... 5-21
5.2.8 Powering on the Standby OMP Blade ...................................................... 5-24
5.3 Version Loading for other Modules .................................................................... 5-24
5.3.1 Checking Module and Unit Configuration ................................................. 5-24
5.3.2 Loading SWBB1 Versions ....................................................................... 5-25

II
 5.3.3 Loading Versions for a Module or Unit over a Non-CGSL Operating
System................................................................................................. 5-27
5.3.4 Loading Module Versions on the CGSL Operating System ........................ 5-29
5.4 DBIO Configuration .......................................................................................... 5-33
5.4.1 Configuring a DBIO Module .................................................................... 5-33
5.4.2 Checking DBIO Bootup........................................................................... 5-33
5.5 Interface Processor Configuration ..................................................................... 5-34
5.5.1 Configuring an Interface Processor.......................................................... 5-34
5.5.2 Checking Interface Processor Bootup ...................................................... 5-36

Chapter 6 HSM Installation ........................................................................ 6-1

6.1 Introduction to HSM............................................................................................ 6-1
6.1.1 HSM Overview ......................................................................................... 6-1
6.1.2 HSM Installation and Configuration Requirements ...................................... 6-2
6.2 HSM Software Installation Flow........................................................................... 6-3
6.3 Installing LunaPCI .............................................................................................. 6-3
6.4 HSM Initial Settings ............................................................................................ 6-6
6.4.1 Introduction to HSM Initialization ............................................................... 6-6
6.4.2 Initializing an HSM.................................................................................... 6-6
6.5 Configuring an HSM Client.................................................................................6-11
6.6 HSM Key Backup and Restoration..................................................................... 6-13
6.6.1 Introduction to the Backup and Restoration of Keys .................................. 6-13
6.6.2 Backing up Keys .................................................................................... 6-13
6.6.3 Restoring Keys....................................................................................... 6-14
6.7 HSMAPP Installation and Configuration ............................................................. 6-16
6.7.1 Installing HSMAPP ................................................................................. 6-16
6.7.2 Starting the HSSAPP.............................................................................. 6-19

Chapter 7 Agent Installation...................................................................... 7-1

7.1 Introduction to Agent .......................................................................................... 7-1
7.1.1 Description .............................................................................................. 7-1
7.1.2 Agent Installation and Configuration Requirements..................................... 7-2
7.2 Agent Installation Flow........................................................................................ 7-3
7.3 GUI Agent Installation......................................................................................... 7-4
7.3.1 Installing Operating System for an Agent ................................................... 7-4
7.3.2 Antivirus Software Installation ................................................................... 7-5
7.3.3 Installing a GUI Agent............................................................................... 7-5
7.3.4 Introduction to GUI Agent Configuration File .............................................7-11
7.3.5 Logging In to a GUI Agent....................................................................... 7-14

III
 7.4 Web Agent Installation...................................................................................... 7-15
7.4.1 Data Configuration Check Items Related to Web Agent Server.................. 7-15
7.4.2 Checking Listen of Web Agent Server...................................................... 7-17
7.4.3 Modifying configuration file for Web Resource Server ............................... 7-19
7.4.4 Logging In to a Web Client ...................................................................... 7-21

Chapter 8 CGSL Operating System Installation ...................................... 8-1

8.1 Introduction to CGSL Installation ......................................................................... 8-1
8.2 Checking Hard Disk Mirroring.............................................................................. 8-3
8.3 Change BIOS Settings........................................................................................ 8-9
8.4 Installing from DVD Drive.................................................................................. 8-12
8.4.1 Setting Boot Mode.................................................................................. 8-12
8.4.2 Installing the Operating System............................................................... 8-14
8.5 Operating System Configuration........................................................................ 8-24
8.5.1 Configuring General Settings .................................................................. 8-24
8.5.2 Checking the Operating System .............................................................. 8-29
8.5.3 Modifying Character Set ......................................................................... 8-29
8.6 Network Configuration ...................................................................................... 8-31
8.6.1 Installing the Patch for Renaming Network Adaptors................................. 8-31
8.6.2 Identifying Network Adaptors on CGSL .................................................... 8-32
8.6.3 Teaming Network Adapters on CGSL ...................................................... 8-33
8.6.4 Setting IP Addresses for a Network Adaptor on CGSL .............................. 8-36
8.6.5 Setting Routes on CGSL......................................................................... 8-40
8.6.6 Modifying the hosts file .......................................................................... 8-42
8.7 LED Driver Update ........................................................................................... 8-43
8.7.1 Updating LED Driver for DPBX0 and OPBA1 ........................................... 8-43
8.7.2 Updating LED Driver for DPBX1 and OPBB1 ........................................... 8-44

Chapter 9 Oracle Database Installation.................................................... 9-1

9.1 Introduction to Oracle Installation ........................................................................ 9-1
9.2 Preparations ...................................................................................................... 9-3
9.2.1 Updating Kernel of the CGSL Operating System ........................................ 9-3
9.2.2 Creating User Oracle and Its Groups ......................................................... 9-5
9.2.3 Setting Environment Variables for User Oracle ........................................... 9-6
9.3 Installing Oracle 10g........................................................................................... 9-7
9.4 Installing Oracle 10204 Patch............................................................................ 9-15
9.5 Creating an Oracle Instance.............................................................................. 9-19
9.6 Configuring Oracle Database Listener ............................................................... 9-29
9.7 Configuring a Name for Local Oracle Service ..................................................... 9-34

IV
 9.8 Checking Oracle Installation.............................................................................. 9-39
9.9 Configuring Autostart of Oracle Services Upon Starting ...................................... 9-39

Appendix A General Operations .............................................................. A-1

A.1 Accessing a Shared Directory on Windows from CGSL ........................................ A-1
A.2 Establishing a Remote Control Connection to CGSL ............................................ A-3
A.3 Transferring Files to a CGSL Host....................................................................... A-7
A.4 Restarting CGEL................................................................................................ A-9
A.5 Setting IP Address on Windows ........................................................................ A-11
A.6 Setting a Route on Windows............................................................................. A-14
A.7 Introduction to Files for EMS Clock Configuration............................................... A-14
A.8 Installation and Configuration of a Secondary Forwarding Module....................... A-16

Appendix B Service Set Check ................................................................ B-1

B.1 Basic Concepts.................................................................................................. B-1
B.2 Checking a Service Set with Ushell ..................................................................... B-1
B.3 Introduction to Service Sets ................................................................................ B-3

Appendix C Network Adaptors of Processing Blades ........................... C-1

Figures............................................................................................................. I
Tables ...........................................................................................................VII
Glossary ........................................................................................................IX

V
VI
About This Manual
Purpose
This manual introduces how to install the software of the NMS and the agent, as well as
how to load the versions onto the FE boards and the configuration for OMM Accessing to
EMS.

Intended Audience
This manual is suitable for:
l Telecommunication engineers
l Technology specialists or maintenance personnel who need knowledge of the
installation of the software of ZXUN USPP

Prerequisite Skill and Knowledge

To use this manual effectively, users should have a general understanding of wireless
telecommunications technology. Familiarity with the following is helpful:
l The ZXUN USPP system and its various components
l The Linux operating system, the Windows operating system and the Oracle database

What Is in This Manual

This manual contains the following chapters:

Chapter Summary

Chapter 1, Introduction to Introduces the system structure of the ZXUN USPP NE management
Software Installation subsystems, the IP plan and network plan needed to get familiar with
before installation.

Chapter 2, OMM Installation Introduces how to install the software on the OMM server and the
OMM client.

Chapter 3, EMS Installation Introduces how to install the software on the EMS server and the
EMS client.

Chapter 4, Configuration for Introduces how to access OMM to EMS.

OMM Accessing to EMS

Chapter 5, Version Loading Introduces how to load versions onto the boards in the cabinet.

Chapter 6, HSM Installation Introduces how to install the software of a Hardware Security Module
(HSM).

Chapter 7, Agent Installation Introduces how to install a ZXUN USPP agent.

Chapter 8, CGSL Operating Introduces how to install the software on the CGSL system.
System Installation

I
 Chapter Summary

Chapter 9, Oracle Database Introduces how to install Oracle 10g and the update version Oracle
Installation 10.2.0.4 on the CGSL system, and how to create an instance and
local services.

Appendix A, General Introduces some general operations during installing the NE

Operations management server.

Appendix B, Service Set Introduces basic concepts about service sets, how to check service
Check sets, and the service set of each module or unit.

Appendix C, Network Introduces the detailed information about the network adaptors of
Adaptors of Processing data processing blades and OSS processing blades.
Blades

FCC Compliance Statement

This device complies with part 15 of the FCC Rules. Operation is subject to the following
two conditions.

1. This device may not cause harmful interference.

2. This device must accept any interference received, including interference that may
cause undesired operation.
Changes or modifications not expressly approved by the party responsible for compliance
could void the user’s authority to operate the equipment.

Conventions
ZTE documents employ the following typographical conventions.

Typeface Meaning

Italics References to other manuals or documents.

“Quotes” Links on screens.

Bold Menus, menu options, function names, input fields, radio button
names, check boxes, dropdown lists, dialog 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
Declaration of RoHS
Compliance
To minimize environmental impacts and take more responsibilities to the earth we live
on, this document shall serve as a formal declaration that ZXUN USPP manufactured
by ZTE CORPORATION is in compliance with the Directive 2002/95/EC of the European
Parliament - RoHS (Restriction of Hazardous Substances) with respect to the following
substances:
l Lead (Pb)
l Mercury (Hg)
l Cadmium (Cd)
l Hexavalent Chromium (Cr (VI))
l PolyBrominated Biphenyls (PBBs)
l PolyBrominated Diphenyl Ethers (PBDEs)

ZXUN USPP manufactured by ZTE CORPORATION meets the requirements of EU 2002/95/EC;

however, some assemblies are customized to client specifications. Addition of specialized,
customer-specified materials or processes which do not meet the requirements of EU 2002/95/EC
may negate RoHS compliance of the assembly. To guarantee compliance of the assembly, the need
for compliant product must be communicated to ZTE CORPORATION in written form.
This declaration is issued based on our current level of knowledge. Since conditions of use are
outside our control, ZTE CORPORATION makes no warranties, express or implied, and assumes no
liability in connection with the use of this information.

I
II
 Chapter 1
Introduction to Software
Installation
Table of Contents
System Architecture ...................................................................................................1-1
Networking Planning ..................................................................................................1-7
Naming Rules...........................................................................................................1-15
Installation Flow .......................................................................................................1-17

1.1 System Architecture

System Architecture
The ZXUN USPP system consists of one or more FE subsystems, a UDS subsystem, one
or more POVISION subsystems, a network element management subsystem (NMS) and
a fault recovery subsystem.
The UDS subsystem, the POVISION subsystems and the NMS are generally called the
Back End (BE).

The following figure illustrates the system architecture of ZXUN USPP.

Figure 1-1 ZXUN USPP System Architecture

1-1

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

The FE subsystem, the UDS subsystem, the POVISION subsystems and the NMS of
ZXUN USPP are respectively responsible for signaling and service processing, data
management, service provision handling, O&M functions and the fault recovery function.
From the view of hardware, these functions are realized by the processing blades that
comply with the ETCA architecture.
The Hardware Security Module (HSM) subsystem is optional, and is used to ensure the
security of keys and other sensitive data.

FE Subsystem
The FE subsystem functions to process protocols and services relating to ZXUN USPP
applications.
The FE subsystem of ZXUN USPP uses DPBA2 blades, SLB blades and SWBB1 blades
(with the DACM daughter card). The functions of the units or modules of ZXUN USPP are
as follows.
l CMP modules process services.
l SMP modules process SCTP (Carried by IP), MTP3 (Carried by E1/T1), MTP3B
(Carried by ATM over E1) and MAP signaling.
l SIPI units, which are used in case of IP access, provide fast Ethernet interfaces, and
forward the SCTP packets (received from the IP network) to SMPs for processing.
l Used in case of E1/T1 access, an SLB unit provides 32 E1 or T1 links for the
connection with the SS7 network, performs HDLC processing on SS7 signaling at the
HDLC or MTP2 layer and lower layers, and sends MTP3 signaling packets to SMP.
In case of the access mode of ATM over E1, when ATM cells enter an SLB unit through
the E1/T1 interfaces, they are distributed to the TDM interfaces of the corresponding
SLB blade after time slot switching. The SLB blade converts the TDM signals into ATM
cells, performs framing and encapsulation over AAL5, and then sends service-related
data to SMPs.
l The clock unit (realized by the DACM daughter card of SWI2) provides clock
functions including BITS clock lead-in, clock extraction, synchronous phase lock, and
clock distribution, ensuring clock synchronization of the equipment with the external
network.
l The RPU module maintains the routing tables of the entire NE. When an SIPI
receives routing packets, it forwards the packets to the RPU module. The RPU
module refreshes the routing tables in real time. Based on routing tables, it creates
forwarding tables, and synchronizes the tables to each SIPI.
l The OMP module performs system control and management. It saves the
configuration information and version files of devices, and sends alarm messages
and statistical data to the NMS.

PROVISION Subsystem
The PROVISION subsystem is composed of one or more DBIO servers, interface
processors and agents. The functions of the PROVISION subsystem include adding,

1-2

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 1 Introduction to Software Installation

modifying and deleting subscriber data. Its system structure is shown in the following
figure.

Figure 1-2 PROVISION Subsystem Structure

UDS Subsystem
The UDS subsystem is the database subsystem of ZXUN USPP. The following figure
shows the composition of the UDS subsystem.

1-3

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Figure 1-3 UDS Subsystem Architecture

A UDS consists of one or more DSAs. DSA here refers to a DSA cluster that includes
1–80 DSA nodes.
There are two types of DSAs:
l Identity DSA (IDSA): Stores subscriber data routing information and transfers the
directory data access requests of FE or PROVISION to PDSA.
l Profile DSA (PDSA): Stores subscriber data.
In UDS, data may be stored in the following modes:
l Local storage: Data is saved on the hard disks of the DSA node.
l Storage transfer: Data is transferred by the DST node onto the hard disks of the DST
node or on the disk array connected to the DST.
With the UAGW modules, UDS supports the access from third-party devices.
It is strongly recommended that the software of UDS subsystem be installed by specialists.
The installation of UDS software is not introduced in this manual. Contact ZTE for details
about the installation of UDS software.

Network Element Management Subsystem

The network element management subsystem performs the integrated and local
management of the modules of ZXUN USPP.
The network element management subsystem may adopt distributed networking (that is,
dual-Layer networking) or single-layer networking.
l Distributed Networking

1-4

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 1 Introduction to Software Installation

In the distributed networking mode, the network element management subsystem

adopts a dual-layer structure, including an EMS and multiple OMMs. The following
figure shows the architecture of the network element management subsystem. This
structure is suitable for a large-scale commercial office with NEs deployed at different
places.

Figure 1-4 Architecture of Network Element Management Subsystem (Distributed

Networking)

1-5

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Note:
à The EMS server software installation described in this manual is based on a single
EMS server. For EMS server software installation on a dual-server cluster, refer
to the user documents for EMS, or contact ZTE for help.
à An OMM server generally uses a single blade. If you want to use a dual-computer
cluster as an OMM server, contact ZTE for help.

l Single-Layer Networking

When the network element management subsystem adopts the single-layer structure,
its architecture is as shown in the following figure. This structure is suitable for a
small-scale office or a trial office. And OMM may manage all NEs.

Figure 1-5 Architecture of Network Element Management Subsystem (Single-Layer

Networking)

1-6

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 1 Introduction to Software Installation

Note:
An OMM server generally uses a single blade. If you want to use a dual-computer
cluster as an OMM server, contact ZTE for help.

Fault Recovery Subsystem

ZXUN USPP supports two fault recovery modes.
l Self-contained redundancy function of ZXUN USPP: The UDS consists of multiple
DSA clusters. A DSA cluster may include multiple DSA nodes, with the data
synchronization function among the DSA nodes through data duplication. This
redundancy protection function does not need any modules like DRSync, DRManager
or out-of-sync buffer database.
l DRSync-based redundancy protection: This mode provides the compatibility with
the redundancy protection functions of converged versions and the possibility for
redundancy protection by networking with NEs of other vendors. The Fault Recovery
subsystem is composed of one ICC and one or more DRSync modules.

The redundancy protection scheme may vary with different redundancy protection modes.
The installation of redundancy protection software not introduced in this manual. For the
details about the installation of redundancy protection software, refer to your redundancy
protection scheme and contact ZTE.

HSM Subsystem
An HSM is a device that encrypts and decrypts sensitive data of ZXUN USPP, which
features fast encryption and decryption rates.

Note:
HSM configuration is optional for ZXUN USPP. Whether HSM modules can be configured
or not is determined by your License.

1.2 Networking Planning

Introduction to ZXUN USPP Networking
According to their functions, the involved IP networks are divided into the following
categories.
l Local network

1-7

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Consists of equipment in one or more ETCA shelves, local switches, disk arrays
located at a same place, and implements local data loading and service processing.
l Data network
Consists of ETCA equipment of multiple offices at different places, and the IP
carrier network between them, and implements inter-office data control, access and
synchronization.
l Network element (NE) management and monitoring network
Consists of an integrated network management center (NMC), EMS,OMM
subsystems, and the IP carrier network. It implements the network communication
for inter-office network element management and monitoring, as well as integrated
management, monitoring and maintenance of network elements.
As described in this manual, the NE management network is divided into two parts:

à Northbound NE management network: the NE management network between

OMMs/EMSs and the NMC
à Inter-office NE management network: the NE management network between
OMMs and the EMS

l IP signaling network
Consists of the signaling modules of each FE and each network element, as well as the
IP carrier network. It implements the IP association-based communication between
ZXUN USPP and its peer ends.
l Accounting network
Consists of PROVISION modules, BOSS, and the IP carrier network. It carries the
TCP/IP interworking between ZXUN USPP and BOSS for the implementation of BOSS
service handling.
l Third-party access network
Consists of PROVISION modules, third-party applications and the IP carrier network.
It carries the TCP/IP interworking between ZXUN USPP and third-party applications.

IP Address Planning
For the IP addresses that need to be configured for EMS and OMM, see the following table.

1-8

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 1 Introduction to Software Installation

Table 1-1 IP Address Planning

Module Type Module No. Physical Address Virtual Address and port Note

OMP+RPU+ 1 l Slot 9, shelf 2, rack 1: - Base IP address,

DMCC 128.0.31.1 automatically
l Slot 10, shelf 2, rack 1: created
128.0.31.9
l Other positions
128.(128+RackNumb-
er).17.(128+ShelfNum-
ber*32+SlotNumber)

192.168.OfficeID.1 - Fabric IP address for

communication with
the OMM server

- Internal: For communication

192.168.OfficeID.2 in the data network
60000+ModuleNumber
External:
IP 2 for the data network
50000+ModuleNumber

CMM - 190.0.ShelfNumber.1 - Base IP address for

communication with
the OMM server

128.129.ShelfNumber.1 IP address of the left

CMM for debugging

128.129.ShelfNumber.1 IP address of the

right CMM for
debugging

SMP+CMP 3-59 (for - Internal: 30 modules in a shelf

shelves 1 and 192.168.OfficeID.2 in total
2) 60000+ModuleNumber (Recommended:
300-599 (for External: The first 10 are for
shelves 3–12) IP 2 for the data network SMP modules, and
660-689 and 50000+ModuleNumber the last 20 are for
760-789 CMP modules.)
(for shelves
13–14)

1-9

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Module Type Module No. Physical Address Virtual Address and port Note

IDSA 60–89 (for - Internal: Modules 60–69 and

shelves 1 and 192.168.OfficeID.2 600–659 are active
2) 60000+ModuleNumber modules.
600–659, External: Modules 70–79 and
700–759 and IP 2 for the data network 700–759 are standby
800–859 (for 50000+ModuleNumber modules.
shelves 3–14) Modules 80–89
and 800–859
PDSA 90–119 (for - Internal:
are redundancy
shelves 1 and 192.168.OfficeID.2
protection modules.
2) 60000+ModuleNumber
600–659, External:
700–759 and IP 2 for the data network
800–859 (for 50000+ModuleNumber
shelves 3–14)

Aggregation – Aggregation IP address: – A port for data sync

port of SIPI for 192.168.OfficeID.100 is an aggregation
data sync port.

IP 1 for the data network – –

Aggregation – Aggregation IP address: – –

port of SIPI IP 6 for the inter-office NE
to Web management network
agnet server
(WEBAGENT)

Aggregation – IP for signaling Internal: –

port of SIPI to inter-connection –
IP signaling External:
network Signaling IP (TCP/SCTP
virtual address)

Aggregation – Aggregation IP address: – –

port of SIPI IP 1 for the accounting
to accounting network
network

Web agent 120, 121 – Internal: For communication

server 192.168.OfficeID.2 in the local network
(WEBAGENT) 3000+ModuleNumber or the inter-office
External: network
IP 7 for the inter-office NE
management network
3000+ModuleNumber

1-10

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 1 Introduction to Software Installation

Module Type Module No. Physical Address Virtual Address and port Note

OMM server 1000 128.128+RackNumber.17 - Base IP address for

(single +ShelfNumber*32+SlotNu communication with
computer) mber the base plane of
other blades.
The system creates
it automatically.

190.0.1.129 - Base IP address for

communication with
the CMMs

192.168.OfficeID.129 - Fabric IP address for

communication with
OMP, EMS server
and OMM client

IP 1 for the inter-office NE - IP address of Bond0

management network of the rear board,
for communication
between
network element
management
subsystems at
different places

EMS server - 192.168.OfficeID.128 - Fabric IP address for

(single communication with
computer) OMM servers and
EMS clients

IP 2 for the inter-office NE - IP address of Bond0

management network of the rear board,
for communication
between
network element
management
subsystems at
different places

IP for the Northbound NE - IP address of Bond1

management network of the rear board,
for communication
with the superior
network element
management
subsystem

1-11

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Module Type Module No. Physical Address Virtual Address and port Note

DBIO 130–139 (for - Internal: For communication

shelves 1–9) 192.168.OfficeID.2 in the data network
150–154 60000+ModuleNumber and the accounting
(for shelves External: network
10–14) l For data network:
IP 2 for the data
network
50000+ModuleNum-
ber
l For accounting
network:
IP 3 for the accounting
network
60000+ModuleNum-
ber

Interface 140–149 (for - l For data For communication

processor shelves 1–9) network:Internal: in the data network
155–159 192.168.OfficeID.2 and the accounting
(for shelves 60000+ModuleNum- network
10–14) ber
External:
IP 2 for the data
network
50000+ModuleNum-
ber
l For accounting
network:Internal:
192.168.OfficeID.2
3000+ModuleNumber
External:
IP 2 for the accounting
network
3000+ModuleNumber

GUI Agent 200–229 192.168.OfficeID.ModuleN - For communication

umber in the local network

1-12

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 1 Introduction to Software Installation

Module Type Module No. Physical Address Virtual Address and port Note

EMS client 230–239 192.168.OfficeID.ModuleN – For communication

umber with EMS server

IP 4 for the inter-office NE – For communication

management network between
network element
management
subsystems at
different places

HSM 240, 241 192.168.OfficeID.ModuleN – For communication

umber in the local network

IP 10 and IP 11 (of modules – For inter-office

240 and 241 respectively) communication
for the inter-office NE
management network

IP 3 and IP 4 (of modules – For communication

240 and 241 respectively) in the data network
for the data network
5000+ModuleNumber

OMM client 242–249 192.168.OfficeID.ModuleN – For communication

umber with OMM server

IP 5 for the inter-office NE – For communication

management network between
network element
management
subsystems at
different places

Maintenance 200–249, not Set according to your actual – For maintenance

modules used by other applications modules such as a
modules secondary transfer
module

Reserved 256–260, Set according to your actual Set according to your For UAGW modules
modules 262–299 applications actual applications and others

1-13

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Module Type Module No. Physical Address Virtual Address and port Note

DST 170–199 – Internal: For communication

(dual-computer 192.168.OfficeID.2 in the data network
cluster + disk 60000+ModuleNumber
array) External:
IP 2 for the data network
50000+ModuleNumber

Refer to Table 1-2. Internal: For communication

192.168.201.ModuleNum with the Oracle
ber database
External: -

• IP addresses of the 192 segment are for local communication.

• When an OMP is powered on for the first time, the DTF tool creates a temporary IP address (129.0.254.1). You
should change it to 192.168.OfficeID.1 after you load the versions onto the OMP and activate them.
• Your company (the operator) should provide the IP addresses for the data network, the NE management network,
the accounting network and the IP signaling network.
• EMS server, bond0 refers to the network interface team made of network interfaces 1 and 2 of the rear board, and
bond1 refers to the network interface team made of network interfaces 3 and 4 of the rear board.
• The virtual addresses are loopback addresses configured during the IP stack configuration on the network element
management system. Different modules use the same virtual address, with different port numbers.
• An aggregation IP address of an SIPI is the IP address of an aggregation port configured on the network element
management system.

Table 1-2 Physical IP Address Planning for Network Interfaces of DST

DST Modules Physical IP Addresses Note

(170–199) (192.168.(201–203).(100–159))

Left Board Right Board

Assume that there are 170 192.168.201.100 192.168.201.101 For connection

two DST nodes, 170 with the Oracle
and 171. The physical database
IP address planning for
192.168.202.100 192.168.202.101 For connection
more DST nodes are
with the disk array
similar.
192.168.203.100 192.168.203.101 For connection
with the disk array

171 192.168.201.102 192.168.201.103 For connection

with the Oracle
database

192.168.202.102 192.168.202.103 For connection

with the disk array

192.168.203.102 192.168.203.103 For connection

with the disk array

1-14

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 1 Introduction to Software Installation

Route Planning
The following table shows the routes that need be configured for the modules involved
during the software installation. For the next-hop IP addresses, you need set them
according to your actual network.

Table 1-3 Route Planning

Module Configuration Item Note

DSA Routes to remote sites in the data For inter-office communication

OMP network
SMP

OMM server Routes to remote sites in the For communication in the inter-office
OMM client inter-office NE management network NE management network
EMS server
EMS client

EMS server Route to the superior network

management center

Interface processor Routes to remote sites in the For communication in the accounting
accounting network network

Routes to BOSS

DBIO Routes to interface processors at

remote sites

GUI Agent Routes to DBIO severs at remote

sites

Secondary forwarding Routes to remote agents

module

1.3 Naming Rules

1.3.1 Naming Rule for Device Names

Note:

This rule is for your reference only. You may name the devices according to your needs.

1-15

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Description
For the convenience of maintenance, it is recommended to use “Office abbreviation_Fu
nction+Module No.” as device names. In case that multiple modules are using a same
device, the smallest module number is recommended.

Example
For example, the name for the OMM server of a ZXUN USPP office whose name
abbreviation is HN may be HN_OMM1000.

1.3.2 Rules for Operating System Password

Note:
These rules are for your reference only. You may name the devices according to your
needs.

CGSL
The following rule for the setting of CGSL user password is recommended.
l Set the password for user root according to the “Uspp_Office ID” rule. An office ID of
three digits is recommended. If the office ID is less than three digits, you may add 0s
to fill up, for example, Uspp_006.
l For other users, you may set the passwords according to your needs. Note that the
password should meet complexity requirements (consisting of letters of both upper
and lower letters and digits).

Windows
After the operating system is installed, you should enable Password must meet
complexity requirements in Local Security Policy.
The following rule for the setting of Windows user password is recommended.

l Set the password for user administrator according to the “Uspp_Office ID” rule. An
office ID of three digits is recommended. If the office ID is less than three digits, you
may add 0s to fill up, for example, Uspp_006.
l For the client, besides user administrator, you need add another administrator, uspp.
User uspp is used for maintenance purpose. The password for uspp may be the
same as the password for administrator.

1-16

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 1 Introduction to Software Installation

Tip:
You may change the password as required. But the password must meet complexity
requirements.

1.4 Installation Flow

Prerequisites
This manual introduces how to install the software of ZXUN USPP after the hardware is
installed, including the installation of the NMS subsystem, the loading of versions, and the
installation of the agent software.
Before installing the software, you should confirm the following.
1. The hardware of ZXUN USPP is installed. The equipment is powered on. For details
about how to do these, refer to the Hardware Installation Guide.
2. A PC for debugging purpose is ready. The following is the requirements for the PC:
l A Windows operating system is installed.
l Supports connection with the serial port.
l Three IP addresses in different network sections are configured, as shown in the
following table.

Table 1-4 IP Addresses of the Debugging PC

IP Address Subnet Mask Description

129.0.254.100 255.0.0.0 For communication with the OMP

(129.0.254.1)

192.168.OfficeID.101 255.255.255.0 IP address in the local network, for

communication with the local OMM server,
the OMP (after version loading) and other
modules

192.168.201.200 255.255.255.0 For communication with the DST

l A remote control program such as SecureCRT is installed, which must support

Telnet or SSH2. You may use it to log in to a blade. For the details about how to log
in to a blade with SecureCRT, see A.2 Establishing a Remote Control Connection
to CGSL.
l An FTP program such as WinSCP is installed, which must support SFTP. You
may use it to upload files to a blade. For the details about how to upload files with
WinSCP, see A.3 Transferring Files to a CGSL Host.
3. The blade type and boot mode in the CMM configuration (for a 13U shelf) or the NCMM
configuration (for a 17U shelf) accord with the hardware actually installed.
CMM and NCMM configuration is generally done by ZTE engineers.

1-17

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Installation Flow
The flow to install the software is shown in the following figure.

Figure 1-6 Software Installation Flow

1. Install the NMS subsystem, including OMM installation, EMS installation, and the
configuration for OMM Accessing to EMS. The configuration for OMM Accessing to
EMS need be carried out after OMM and EMS are installed.
l For details about how to install OMM software, refer to Chapter 2 OMM
Installation.
l For details about how to install EMS software, refer to Chapter 3 EMS Installation.
l For details about how to do the configuration for OMM Accessing to EMS, refer
to Chapter 4 Configuration for OMM Accessing to EMS.
2. Load the versions, that is, load and set the versions for each module in ETCA shelves.

1-18

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 1 Introduction to Software Installation

Caution!
Before loading the versions, you should make sure that the physical configuration (on
OMM) is completed. For the details about physical configuration, refer to the Data
Configuration Guide manual.

For details about how to load the versions, refer to Chapter 5 Version Loading.
3. Install the HSM software.
HSM modules are optional. Install the HSM software according to your actual
applications.

For details about how to install the HSM software, refer to Chapter 6 HSM Installation.
4. Install agents.
There are two types of agents: GUI agents and Web agents. The software installation
procedures for the two types of agents are different. The types of agents that ZXUN
USPP supports depend on specific NEs. Contact ZTE to confirm the agent type.
For details about how to install an agent software, refer to Chapter 7 Agent Installation.

1-19

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

This page intentionally left blank.

1-20

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 2
OMM Installation
Table of Contents
Introduction to OMM...................................................................................................2-1
OMM Software Installation Flow .................................................................................2-3
Preparations...............................................................................................................2-4
FireBird Database Installation...................................................................................2-11
OMM Server Installation ...........................................................................................2-15
Starting the OMM Server..........................................................................................2-22
OMM Client Setting and Login..................................................................................2-23

2.1 Introduction to OMM

2.1.1 Introduction to OMM
The local OMM adopts the Browser/Server architecture.
l The OMM server is accessible to the OMM client and stores local equipment
data. It implements management of local FE, PROVISION and UDS subsystems,
including daily maintenance, signaling trace, failure observation, alarm management,
performance management, MML terminal, log management, professional
maintenance, security management, system management, report management and
license management.
The OMM sever provides interfaces to the superior network element management
system (NMS) and transfers data to the superior NMS, such as performance
management data, fault management data, and service observation data.
l The OMM client is the client of local network element management system. Service
personnel can configure and analyze ZXUN USPP devices to obtain alarm and
statistics data after logging in to the OMM client.

2.1.2 OMM Installation and Configuration Requirements

OMM Server Hardware Requirements
The following table shows the requirements for the hardware environment of OMM server.
Table 2-1 OMM Server Hardware Requirements

Hardware Configuration

Model DPBX0/DPBX1

2-1

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Hardware Configuration

Mouse 1 each

Keyboard

Monitor

USB CD-ROM drive 1

Note:
A PC is required for debugging during the installation of OMM server software. The PC
should have a Windows operating system and can communicate with the computer for the
OMM server.

OMM Server Software Requirements

The following table shows the requirements for the software environment of OMM server.

Table 2-2 OMM Server Software Requirements

Software Configuration

Operating system EmbSys CGS Linux V3.02.00.p1 (32–bit) or a later edition

Database Firebird 2.1.3

OMM Client Hardware Requirements

The following table shows the requirements for the hardware environment of OMM client.

Table 2-3 OMM Client Hardware Requirements

Hardware Configuration

Model Common PC

CPU Main frequency 1.8 GHz or above

RAM 1G or above

Hard disk One 80 G hard disk

Network adapter One 10/100M adaptive NIC

CD-ROM drive One 16X or above CD-ROM

Mouse One each

Keyboard

Monitor

OMM Client Software Requirements

The following table shows the requirements for the software environment of OMM client.

2-2

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 2 OMM Installation

Table 2-4 OMM Client Software Requirements

Software Configuration

Operating system Windows Server 2003 or Windows XP and the latest patches

Antivirus software Trend Micro or McAfee

Web browser Microsoft Internet Explorer 6.0 or later

Hard disk partitions Partition C 20 G

Partition D 30 G

Partition E Remaining disk space

Installation path Windows and the antivirus software are installed on Partition C.

Network services and protocols TCP/IP

2.2 OMM Software Installation Flow

The software installation flow of OMM is shown in the following table.

Table 2-5 OMM Software Installation Flow

Step Description Instructions

1 Install the operating system See Chapter 8 CGSL Operating System

Installation.

2 Prepare for OMM software installation See Section 2.3 Preparations.

3 Install the FireBird database See Section FireBird Database Installation

in Chapter 2 OMM Installation.

4 Install the OMM server See Section OMM Server Installation in

Chapter 2 OMM Installation.

5 Set the OMM client See 2.7.1 Setting Internet Explorer for an
OMM Client.

Caution!

FireBird and the installation agent program must be installed on the OMM server, and
jre1.6 must be installed on the PC that is for debugging. Then you can install the OMM
server software by operating on the debugging PC.

2-3

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

2.3 Preparations
2.3.1 Preparations before OMM Software Installation
Before installing the OMM server software, you must make the following preparations.

Table 2-6 Preparations before OMM Software Installation

Location Operation Remarks

OMM Server Set the character set of the CGSL You can also set it when you are
operating system. installing the CGSL operating system.

Set the system services. -

Disable the Linux firewall. -

Disable the Linux security policy. Theses settings are already set when
you are setting the system services.
Optimize Linux kernel parameters.
You only need to check the settings.
Set the HTTP service.

Set the FTP service.

Debugging PC Install JRE (Java SE Runtime -

Environment)

2.3.2 Configuring System Services

Abstract
The CGSL operating system provides a script for setting the kernel parameters, firewall,
VSFTPD service, HTTPD service and installing the Firebird database. You should run this
script before installing the OMM server.
This topic describes how to run this script.

Prerequisites
l The CGSL operating system is installed.
l You have logged on to zte01 as user root.

Steps
1. In the terminal window, run the following command to enter the /opt/CNV4WG
directory.

[root@zte01 ~]# cd /opt/CNV4WG

2. Run the ./CNV4WG_config to configure the system services.

2-4

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 2 OMM Installation

[root@zte01 CNV4WG~]# ./CNV4WG_config

=========== Starting Configure! ============
Configuring kernel.sem ...
Configuring selinux ...
Configuring vsftpd ...
Configuring httpd ...
Installing Firebird ...
=========== Configure Completed! ============
[root@zte01 CNV4WG]#

– End of Steps –

2.3.3 Disabling the Linux firewall

Abstract
This topic describes how to disable the self-contained fireway of the Linux operating
system.

Prerequisites
l The CGSL operating system is installed.
l You have logged on to zte01 as user root.

Steps
1. In the terminal window, run the service iptables stop command to stop the firewall.
2. Run the chkconfig --level 35 iptables off command to make the firewall
disabled permanently.
3. Run the service iptables status command to check the status of the firewall and
make sure that the firewall is stopped, as shown in the following.

[root@zte01 ~]# service iptables status

Firewall is stopped.
[root@zte01 ~]#

– End of Steps –

2.3.4 Disabling the Linux Security Policy

Abstract
Before installing the OMM software, you should disable the security policy. Otherwise, the
system might not permit you to install the software.
This topic describes how to disable the Linux security policy.

2-5

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Note:
If you have completed the system service configuration (see 2.3.2 Configuring System
Services for details), the Linux security policy is already disabled, and you just need to
confirm it.

Prerequisites
l The CGSL operating system is installed.
l You have logged on to zte01 as user root.

Steps
1. Open the /etc/selinux/config file and find the following.

# This file controls the state of SELinux on the system.

# SELINUX= can take one of these three values:
# enforcing - SELinux security policy is enforced.
# permissive - SELinux prints warnings instead of enforcing.
# disabled - SELinux is fully disabled.
SELINUX=enforcing

2. Change the SELINUX value to disable, as shown in the following.

# SELINUX=enforcing
/* Adding a # mark to disable this setting and make it a note only.*/
SELINUX=disable /* Add this line.*/

– End of Steps –

Follow-Up Action
When all necessary software is installed on the OMM server, enable the security policy by
changing the SELINUX setting back to enforcing.

2.3.5 Optimizing Linux Kernel Parameters

Abstract
To make the CGSL operating system work in an optimal way, you should change the
settings of two kernel parameters: the size of shared memory and the semaphores.

2-6

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 2 OMM Installation

Note:
If have already configured the system services (see 2.3.2 Configuring System Services
for details), the Linux kernel parameters are already optimized. You need only to check
whether the settings are correct.

Prerequisites
l The CGSL operating system is installed.
l You have logged on to zte01 as user root.

Steps
l Open the /etc/sysctl.conf file and set the kernel parameters as follows.

– End of Steps –

2.3.6 Setting the HTTP Service

Abstract
By default, the self-contained HTTP service package (httpd) of the CGSL operating system
is already installed when the CGSL operating system is installed.
To make the HTTP service work properly, you may need to change the settings of the
HTTP services.

Note:
If have already configured the system services (see 2.3.2 Configuring System Services for
details), the HTTP service is already set. You need only to check whether the settings are
correct.
Among the system service settings, the default directory for OMM server is /home/ngo
mm. If you want to install the OMM server under another directory, change the directory
accordingly when you do the steps described in this topic.

Prerequisites
l The CGSL operating system is installed.
l You have logged on to zte01 as user root.

2-7

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Context
The OMM server has the following requirements for HTTP service:
l Port: 2323
l DocumentRoot: Set it to the folder of OMM server applications, for example, /home/
ngomm.

Steps
1. Open the /etc/httpd/conf/httpd.conf file and find the following.

# Change this to Listen on specific IP addresses as shown below to

#prevent Apache from glomming onto all bound IP addresses(0.0.0.0)

# Listen 12.34.56.78:80
# Listen 80

2. Add Listen 2323, as shown in the following.

# Listen 80
Listen 2323

3. Find the following.

# DocumentRoot: The directory out of which you will serve your

# documents. By default, all requests are taken from this
# directory, but symbolic links and aliases may be used to
# point to other locations.

DocumentRoot "/var/www/html"

4. Change DocumentRoot "/var/www/html" as follows.

# DocumentRoot "/var/www/html"
DocumentRoot "/home/ngomm"

5. Find the following.

# This should be changed to whatever you set DocumentRoot to.

#
<Directory "/var/www/html">

6. Change DocumentRoot "/var/www/html" as follows.

# <Directory "/var/www/html">
<Directory "/home/ngomm">

7. Save and close the /etc/httpd/conf/httpd.conf file.

8. On the terminal, run the service httpd restart command to restart the HTTP service.

2-8

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 2 OMM Installation

Stopping httpd: [OK]

Starting httpd: [OK]

Note:
If alarm “httpd: Could not reliably determine the server's fully qualified domain name,
using 127.0.0.1 for ServerName.” appears, it indicates that the server has no device
name or its device name is the same as an existing one. This problem does not affect
the HTTP access.
To remove this alarm, you can do either of the following:

l Change the device name in files /etc/sysconfig/network and etc/hosts

and then reboot the host.
l Change the setting of parameter Server-Name in file /etc/httpd/conf/httpd.conf to
the actual IP address of the server and then restart the HTTP service.

9. Run the netstat -na|grep 2323 command to check the whether the HTTP service has
started. The result is as shown in the following.

tcp 0 0 :::2323 :::* LISTEN

Note:
The HTTP service does not starts automatically after the operating system starts. You
must run the service httpd start to start the HTTP service if the operating system
restarts.

– End of Steps –

2.3.7 Setting FTP Service on CGSL

Abstract
This topic describes how to enable the FTP service on CGSL.
By default, the FTP service is already installed on the CGSL system but not enabled. To
make the FTP service work properly, you may need to change the settings of the FTP
services.

2-9

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Note:
If have already configured the system services (see 2.3.2 Configuring System Services for
details), the FTP service is already set. You need only to check whether the settings are
correct.

Prerequisites
l The CGSL operating system is installed.
l You have logged into the CGSL system as user root.

Steps
1. In the Terminal window, carry out the vi command to edit the /etc/vsftpd/vsftp
d.conf file to change the settings of userlist_enable and userlist_deny, as shown
in the following.

userlist_enable=YES
userlist_deny=NO

2. Carry out the vi command to edit the /etc/vsftpd/ftpusers, as shown in the

following.

[root@zte01 ~]# vi /etc/vsftpd/ftpusers

# Users that are not allowed to login via ftp
#root /* Disable this command with #.*/
bin
daemon
adm
......

3. In the Terminal window, carry out the service vsftpd start command to start
the FTP service, as shown in the following.

[root@hn_omm1000 ~]# service vsftpd start

Starting vsftpd for vsftpd: [ OK ]

4. Check for and delete temporary files (with “~” in the file names) in the /etc/vsftpd folder.

– End of Steps –

2-10

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 2 OMM Installation

2.3.8 Installing JRE on the Debugging PC

Abstract
Java SE Runtime Environment (JRE) version 1.6 or a later version must be installed on
the debugging PC.

Prerequisites
The jre-6u11-windows-i586-p.exe (or another version meeting the requirement) file
is ready on the debugging PC.

Steps
1. On the debugging PC, run the jre-6u11-windows-i586-p.exe file to install the
JRE. The Welcome dialog box opens.
2. View the license agreement and click Accept to proceed. The Progress dialog box
opens.
3. Wait a moment when the installation program is installing Java. When the installation
progress is complete, the Complete dialog box opens.
4. Click Finish to complete the installation.
5. Click Start > Run to open the Run dialog box.
6. Type cmd in the input field and click OK to pen the cmd window.
7. Run the java -version command to check the version of the JRE and confirm that the
version is 1.6 or later, as shown in the following.

C:\Documents and Settings\Administrator>java -version

java version "1.6.0_05"
Java(TM) SE Runtime Environment (build 1.6.0_05-b13)
Java HotSpot(TM) Client VM (build 10.0-b19, mixed mode, sharing)

C:\Documents and Settings\Administrator>

– End of Steps –

2.4 FireBird Database Installation

2.4.1 Checking the Sqlite Database
Abstract
Sqlite is generally built in the CGSL installation CD and is automatically installed when the
operating system is installed. So you need to check and confirm that the Sqlite database
is installed.

2-11

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

This topic describes how to check the sqlite database and how to install it if it does not
already exist.

Prerequisites
l The operating system is installed.
l You have logged on to zte01 as user root.
l The sqlite-3.6.4.tar.gz file is ready on the computer for the OMM server. The
version may be different from this.

Steps
1. In the terminal window, run the rpm -qa|grep sqlite command, and check whether the
output is as follows.

python-sqlite-1.1.7-1.2.1
sqlite-devel-3.3.6-5
sqlite-3.3.6-5

Note:
Your Sqlite version may be different from this (“3.3.6–5”).

l Yes: Sqlite is installed. Go to step 5.

l No: Sqlite is not installed. Go to step 2.
2. Copy the installation file (sqlite-3.6.4.tar.gz) into the /opt directory (on the computer
for the OMM server) in binary mode with an FTP tool.
3. Run the following commands to enter the /soft directory and install Sqlite.

Caution!
Before installing Sqlite, you should clear the contents in file /etc/unixODBC/odbc
.ini if you have ever installed Oracle on this computer.

[root@zte01 ~]# cd /opt

[root@zte01 opt]# tar zxvf sqlite-3.6.4.tar.gz
[root@zte01 opt]# cd sqlite-3.6.4
[root@zte01 sqlite-3.6.4]# ./configure
[root@zte01 sqlite-3.6.4]# make
[root@zte01 sqlite-3.6.4]# make install

4. Run the reboot command to restart the system.

5. Run the sqlite3 command to confirm that Sqlite is successfully connected.

2-12

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 2 OMM Installation

[root@zte01 ~]# sqlite3

SQLite version 3.6.17
Enter ".help" for instructions
sqlite>

6. Run the ./exit command to quit Sqlite.

– End of Steps –

2.4.2 Installing the Firebird Database

Abstract
The CGSL operating system may have already a self-contained Firebird database
(generally Firebird 2.1.1).
You must uninstall it first and then install Firebird 2.1.3.

Prerequisites
l The operating system is installed.
l You have logged on to zte01 as user root.
l The Firebird 2.1.3 installation package (FirebirdSS-2.1.3.18185–0.i686.ta
r) is ready on the computer for the OMM server. The version may be different from
this.

Steps
1. In the terminal window, run the following commands to enter the /opt/Firebird/b
in directory and uninstall Firebird 2.1.1.
[root@zte01 ~]# cd /opt/Firebird/bin
[root@zte01 bin]# ./uninstall.sh
Firebird super 2.1.1.17910-0.i686 Uninstall program

Are you sure you want to proceed?

Press Enter to start uninstall or ^C to abort

2. Press Enter to uninstall Firebird 2.1.1. The screen display is as follows.

Extracting install data
Stopping Firebird server [default] [ OK ]
Saved a copy of SecurityDatabase (security2.fdb) in /tmp
Uninstall completed

3. Check whether the operating system has the Firebird2.1.3 installation program (Fire
birdSS-2.1.3.18185–0.i686.tar) in the /opt/CNV4WG folder.

2-13

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

l Yes: Go to Step 3.
l No: Transfer the installation package of Firebird (FirebirdSS-2.1.3.1818
5–0.i686.tar) to the the /opt/CNV4WG directory. and go to Step 3. (The
version may be different.)
4. Run the following commands to enter the /opt/CNV4WG directory and unzip the files.
root@zte01 bin]# cd /opt/CNV4WG
[root@zte01 CNV4WG]# tar -xvf FirebirdSS-2.1.3.18185-0.i686.tar

5. Run the following commands to install Firebird 2.1.3.

[root@zte01 CNV4WG]# cd FirebirdSS-2.1.3.18185-0.i686
[root@zte01 FirebirdSS-2.1.3.18185-0.i686]# ./install.sh
Firebird super 2.1.3.18185-0.i686 Installation

Press Enter to start installation or ^C to abort

6. Press Enter to start installation. The screen display is as follows.

Extracting install data
Starting Firebird server [default] check $FIREBIRD/firebird.log file for errors
can not start server
[ OK ]
Please enter new password for SYSDBA user:

7. Enter a new password for user SYSDBA (the password should be shorter than 8
characters, and mastkey is recommended), and then press Enter to complete the
installation.
8. Confirm that the FirBird database of the correct version is installed with either of the
following methods.
l Enter the /opt/firebird/bin directory, connect ISQL and confirm the version,
as shown in the following.
[root@zte01 FirebirdSS-2.1.3.18185-0.i686]# cd /opt/firebird/bin
[root@zte01 bin]./isql -z
ISQL Version: LI-V2.1.3.18185 Firebird 2.1
Use CONNECT or CREATE DATABASE to specify a database
SQL>

Tip:
To quit ISQL, press <Ctrl+D>.

l Enter the /opt/Firebird directory and open the WhatsNew file and find the
paragraph that shows the FireBird version, as shown in the following.

2-14

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 2 OMM Installation

***************************
* v2.1.3
***************************

– End of Steps –

2.5 OMM Server Installation

2.5.1 Installing OMM Server Installation Agent
Abstract
The OMM server installation agent enables you to install OMM server onto the CGSL
operating system from the debugging PC.

The OMM server installation agent should be installed on the CGSL operating system
where you want to install the OMM server.

Prerequisites
l The CGSL operating system is installed.
l You have logged on to zte01 as user root.
l You have transferred the installation file of the installation agent (installagent.4.
10.10.P2.B3a.tar.gz in the \zxver_V4\setup\omc folder in the ZXUN USPP
installation file. The version may be different from this) into the /home/installage
nt folder on the blade for the OMM sever.

Steps
1. In the terminal window, run the following commands to enter the /omm/installage
nt directory, and then run run.sh to install the installation agent.

[root@zte01 ~]# cd /omm/installagent

[root@zte01 installagent]# tar zxvf installagent.4.10.10.P2.B3a.tar.gz
[root@zte01 installagent]# chmod 777 /omm/installagent/*
/* Assign the execution permission to the files in this folder. */
[root@zte01 installagent]# ./run.sh
Set agent auto start
Start setup
OK /* OK indicates that the installation progress has completed. */
[root@zte01 installagent]#

2. Run the ps -ef|grep setup command to check and confirm that the installation agent
process (./setup) has started up.

2-15

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

[root@zte01 installagent]# ps -ef|grep setup

root 9151 1 0 23:17 pts/0 00:00:00 ./setup
root 9163 4053 0 23:21 pts/0 00:00:00 grep setup

– End of Steps –

2.5.2 Installing OMM Server

Abstract
With the OMM server installation agent on the blade for the OMM server, you can install
the OMM server onto the blade by running the installation program on the debugging PC.

Prerequisites
l You have copied the OMM server installation files (in the \zxver_V4\setup\omc
folder in the ZXUN USPP installation file folder) onto the debugging PC.
l The Firebird database is installed.
l The OMM server installation agent is installed and running.
l You know the node number (6 digits) for the OMM server.

Steps
1. On the debugging PC, run the install.bat file in the omc folder. The dialog box for
logging in to the installation agent opens, as shown in the following figure.

Figure 2-1 Login

2. Set the parameters by referring to the following table.

2-16

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 2 OMM Installation

Table 2-7 OMM Login Parameters

Parameter Description

Language The language of the OMM server to be installed. Select English from
the drop-down list.

root password The password of user root of the blade for the OMM server

IP address IP address of the OMM server. The debugging PC must be able to

communicate with this IP address.

3. Click OK. The Server Environment dialog box opens, as shown in the following figure.

Figure 2-2 Server Environment

Note:
Network elements (NEs) existing on this server are list in this dialog box, and there is
no network element in this dialog box if this OMM server is being newly installed.

4. Click Install to open the Choose package dialog box.

2-17

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Note:
Available applications and patches are listed in this dialog box. To see the
corresponding NEs and versions of an application or patches, select this application
or patches.

5. Select the application to install, and click Next to open the Parameters dialog box as
shown in the following figure.

Figure 2-3 Parameters

6. Set the parameters. For details about the parameters, refer to the following table.

Table 2-8 OMM Server Installation Parameters

Parameter type Description

Base Basic parameters:

l Ne ID: OMM office ID. Set it according to your networking plan.
l Path: The path to install the OMM server. This manual takes
/home/ngomm as example.
l Server ID: Node ID of the OMM server, 6 digits, must be
unique in the network.
l FTP server type: Set it according to your actual network
conditions, generally FTP.

2-18

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 2 OMM Installation

Parameter type Description

l Choose the NE type: NE types that this OMM server should

support. Set it according to your networking plan.

Database Database parameters:

l Choose target database: File system DB is selected by
default and can not be changed.
l DB system user password: Type the password of user
SYSDBA that is set when you are installing the Firebird
database.
l Database file location: Type the path for the database
files. This path should not be the same as that for the OMM
server. This topic takes /home/ngomm_data/ngomm_db
for example.

Macros for SQL NE Alias: Alias of the NE to install

NetworkType Network Type: Single Network (single-layer) or Distributed

Network (dual-layer). Select according to your networking mode
of the network element management subsystem.

7. Click Next. If the installation path does not exist, a dialog box for confirming the
creation of this path opens. Click Yes in this case. The dialog box for confirming
the parameters opens, as shown in the following figure.

2-19

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Figure 2-4 Parameters Configuration

8. Check whether the parameters are correct.

l Yes: Click Next to start installation.

Note:
During the installation process, a dialog box opens, prompting you whether to
make the OMM server start along with the operating system.
For a single-computer OMM server, you are recommended to click Yes. For an
OMM server deployed on a dual-computer cluster, you are recommended to click
No.

l No: Click Cancel to go back and modify the settings.

9. When the installation process is finished, click Finish to proceed. The OMM server
you have just installed appears.
10. Click Exit to close the OMM server installation dialog box.

2-20

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 2 OMM Installation

11. When a dialog box for confirmation appears, click Yes.

– End of Steps –

2.5.3 Setting FTP after Installing OMM Server

Abstract
After an OMM server is installed, the chroo_list file is created in the /etc/vsftpd/
folder. For a distributed NMS, the settings in the FTP configuration file (/etc/vsftpd/v
sftpd.conf) should be modified so that the OMM can be accessed into the EMS.

Caution!
The FTP setting to be made is required for a distributed (dual-layer) NMS only, and is not
required for a single-layer NMS.

Prerequisites
l The OMM server is installed.
l You have logged on to zte01 as user root.

Steps
1. Open the FTP configuration file (/etc/vsftpd/vsftpd.conf) and add the
following.

chroot_local_user=NO
chroot_list_enable=YES
chroot_list_file=/etc/vsftpd/chroot_list

Tip:
l If the setting items already exist, you can just change the settings.
l If a setting item is disabled with a “#” at the beginning, you can delete the “#” to
enable this item and change the setting.

2. Open the /etc/vsftpd/ftpusers file and add a “#” before “root” at the beginning
to enable user root to log in via FTP.
3. In the terminal window, run service vsftpd restart to restart the FTP services, as
shown in the following.

2-21

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

[root@zte01 ~]# service vsftpd restart

Shutting down vsftpd: [ OK ]
Starting vsftpd for vsftpd: [ OK ]
[root@zte01 ~]#

4. Check for and delete temporary files (with “~” in the file names) in the /etc/vsftpd
folder.
– End of Steps –

2.6 Starting the OMM Server

Abstract
This topic introduces how to start the OMM server.

Prerequisites
l The OMM server is successfully installed.
l You have logged on to zte01 as user root.

Steps
1. In the terminal window, run the cd /home/ngomm command to enter the /home/ng
omm directory.

2. Run the run.sh command to start the OMM server, as shown in the following.

[root@zte01 ngomm]# ./run.sh

ZXHOME CHECK OK
Check Ne Config Ok
Start SWD OK
uspp_203
CREATE MD5 OK
[root@zte01 ngomm]#

– End of Steps –

Result
In the terminal window, run the ps -ef|grep service command to check the processes. The
OMM server has successfully started up if the following 15 processes exist.

2-22

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 2 OMM Installation

root 6939 1 0 18:33 ? 00:00:00 ./swdservice

root 6947 6939 0 18:33 ? 00:00:01 /home/ngomm/oms/bin/omsservice
root 6975 6939 0 18:33 ? 00:00:01 /home/ngomm/ndf/bin/ndfservice
root 6999 6939 16 18:34 ? 00:00:38 /home/ngomm/uspp_203/server/atcaommservice
root 7009 6939 4 18:34 ? 00:00:10 /home/ngomm/uspp_203/server/brmservice
root 7021 6939 4 18:34 ? 00:00:09 /home/ngomm/uspp_203/server/clisservice
root 7034 6939 4 18:34 ? 00:00:10 /home/ngomm/uspp_203/server/cmservice
root 7050 6939 2 18:34 ? 00:00:05 /home/ngomm/uspp_203/server/corbaservice
root 7080 6939 1 18:34 ? 00:00:02 /home/ngomm/uspp_203/server/dmservice
root 7091 6939 1 18:34 ? 00:00:02 /home/ngomm/uspp_203/server/fmservice
root 7107 6939 3 18:34 ? 00:00:06 /home/ngomm/uspp_203/server/hlrservice
root 7117 6939 1 18:34 ? 00:00:02 /home/ngomm/uspp_203/server/iuservice
root 7143 6939 4 18:34 ? 00:00:09 /home/ngomm/uspp_203/server/logservice
root 7179 6939 1 18:35 ? 00:00:02 /home/ngomm/uspp_203/server/rackviewservice
root 7199 6939 1 18:35 ? 00:00:02 /home/ngomm/uspp_203/server/smservice
root 8156 6725 0 18:37 pts/0 00:00:00 grep service

2.7 OMM Client Setting and Login

2.7.1 Setting Internet Explorer for an OMM Client
Abstract
This topic introduces how to set Microsoft Internet Explorer for an OMM client.

Prerequisites
l Adobe Flash Player of the latest version is installed on the OMM client.
l Microsoft Internet Explorer 6.0 or a later version is installed on the OMM client.

Steps
1. Open Internet Explorer, and select menu Tools > Internet Options to open the
Internet Options dialog box.

2. On the General tab, click the Settings button in the Temporary Internet files field to
open the dialog box as shown in the following figure.

2-23

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Figure 2-5 Settings

3. Set Check for newer versions of stored pages to Every visit to the page.
4. Click OK to close the Settings dialog box and return to the Internet Options dialog
box.
5. On the Security tab, select the Trusted sites icon and do the following.

Operation Steps

Add the Web site of the OMM i. Click the Sites button to open the Trusted sites dialog box.
server to trusted sites.
ii. In the Add this Web site to the zone field, type Web site of
the OMM server (for example, http://192.168.203.129) and
click Add to add it.

iii. Click OK to close the Trusted sites dialog box and return to
the Internet Options dialog box.

Set custom security level. i. Click the Custom Level button to open the Security Set-
tings dialog box.

ii. Enable all items of ActiveX controls and plug-ins.

iii. Click OK to close the Security Settings dialog box and return
to the Internet Options dialog box.

6. In the Internet Options dialog box, click OK to save the settings and close the dialog
box.
7. Restart Internet Explorer.
– End of Steps –

2-24

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 2 OMM Installation

2.7.2 Logging In to OMM

Abstract
This topic describes how to log in to the OMM server from the client with Microsoft Internet
Explorer.

Prerequisites
l The OMM server has started up.
l The HTTP service of the OMM server has started up.
l The communication between the OMM client and the OMM server is normal.
l You have set Internet Explorer of the OMM client.

Steps
1. Open Internet Explorer on the client, and type the address of the OMM server in the
Address field and press Enter. The page as shown in Figure 2-6 appears.
The format of the address is http://[OMM server IP address]:[http service port
number]/uspp_[NE ID]/client/. For the details about the address, see the following
table.

Table 2-9 OMM Server Address Parameters

Parameter Description

OMM server IP address Set it according to your network deployment, for example,
192.168.203.129

http service port number The Listen port number that is set when you are setting the
HTTP service, for example, 2323

NE ID NE ID that is set when the OMM server is being installed

Figure 2-6 Login

2-25

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

2. Type the user name and password. For details about the parameters, see the following
table.

Table 2-10 OMM Login Parameters

Parameter Description Default

User Name User name that you want to use to log in to admin
the OMM

Password Password of the user null

Note:
You can use the default user name and password when you are log in for the first time.

3. Click Login to log in to the OMM.

Note:
When you are log in for the first time, the system prompts you to change the password.
Change the password and log in again.

The page after you successfully log in is as shown in the following figure.

2-26

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 2 OMM Installation

Figure 2-7 OMM Main Page

– End of Steps –

2-27

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

This page intentionally left blank.

2-28

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 3
EMS Installation
Table of Contents
Introduction to EMS....................................................................................................3-1
EMS Software Installation Flow ..................................................................................3-3
EMS Server Installation ..............................................................................................3-3
EMS Client Installation .............................................................................................3-17

3.1 Introduction to EMS

3.1.1 Introduction to EMS
EMS adopts the Client/Server structure.
l The EMS server stores data of all devices of ZXUN USPP, and implements
various maintenance functions including performance statistics, fault management,
service observation (including failure observation), signaling trace, configuration
management, and log management.
l The EMS client is the client of EMS, a centralized network element management
system. Operation and maintenance personnel can perform data configuration, data
analysis and data synchronization on local OMM subsystems and equipment that
access to the EMS system through the EMS client. Operation and maintenance
personnel can also obtain log, alarm and statistic data from the local OMM
subsystems and perform related operation and maintenance.

3.1.2 EMS Installation and Configuration Requirements

EMS Server Hardware Requirements
The following table shows the requirements for the hardware environment of EMS server.

Table 3-1 EMS Server Hardware Requirements

Hardware Configuration

Model OPBA1/OPBB1

Mouse 1 each

Keyboard

Monitor

USB CD-ROM drive 1

3-1

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Note:
A PC is required for debugging during the installation of EMS server software. The PC
should have a Windows operating system and can communicate with the computer for the
EMS server.

EMS Server Software Requirements

The following table shows the requirements for the software environment of EMS server.

Table 3-2 EMS Server Software Requirements

Software Configuration

Operating system EmbSys CGS Linux V3.02.00.p1 (32–bit) or later

Database Oracle 10g + the Oracle 10.2.0.4 patch (for 32–bit Linux)

EMS Client Hardware Requirements

The following table shows the requirements for the hardware environment of EMS client.

Table 3-3 EMS Client Hardware Requirements

Hardware Configuration

Model Common PC

CPU Main frequency 1.8 GHz or above

RAM 1G or above

Hard disk One 80 G hard disk

Network adapter One 10/100M adaptive NIC

CD-ROM drive One 16X or above CD-ROM

Mouse One each

Keyboard

Monitor

EMS Client Software Requirements

The following table shows the requirements for the software environment of EMS client.

Table 3-4 EMS Client Software Requirements

Software Configuration

Operating system Windows Server 2003 or Windows XP and the latest patches

Antivirus software Trend Micro or McAfee

3-2

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 3 EMS Installation

Software Configuration

Hard disk partitions Partition C 20 G

Partition D 30 G

Partition E Remaining disk space

Windows and the antivirus software are installed on Partition C, and

Installation path
the EMS client is installed on Partition D.

Network services and protocols TCP/IP

3.2 EMS Software Installation Flow

EMS Server Software Installation Flow
The software installation flow of EMS server is shown in the following table.

Table 3-5 EMS Server Software Installation Flow

Step Description Instructions

1 Install the operating system See Chapter 8 CGSL Operating System

Installation.

2 Install the Oracle database See Chapter 9 Oracle Database Installation

3 Install the EMS server See 3.3.1 Installing EMS Server.

EMS Client Software Installation Flow

The software installation flow of EMS client is shown in the following table.

Table 3-6 EMS Client Software Installation Flow

Step Description Instructions

1 Install the operating system (Windows) See 3.4.1 Installing Operating System for
an EMS Client.

2 Install the antivirus software See 3.4.2 Installing Antivirus Software.

3 Install the EMS client See 3.4.3 Installing EMS Client.

3.3 EMS Server Installation

3.3.1 Installing EMS Server
Abstract
This topic introduces how to install the EMS server.

3-3

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

The installation path is /ems. After the installation, the files may occupy a space of about
731.7 MB.

Note:
l The directories and instance names involved during the installation can be modified
as desired.
l This topic introduces a completely new installation process.

Prerequisites
l You have logged on to zte01 as user root.
l The EMS server application (the ems_verision folder in EMS version file folder) has
been uploaded to the /soft folder on the EMS server through FTP in binary mode.
l The Oracle database is installed, and you know the IP address (or machine name)
of the Oracle database, the password of the system user, and the database instance
(SID).
l You know the ID of the EMS server.
l You know the IP address of the superior clock server (SNTP server). The clock server
should be provided by your company (the operator). If it is not provided, use the EMS
server as the clock server.
l The installation directory /ems has been created when the operating system is
installed.
l The local FTP server (vsftpd) is stopped. You can run the service vsftpd stop command
to stop the service.
l In the local /etc/host file, the current host IP address (with localhost followed) is
the IP address of the inter-office NE management network. If the current IP address
is not the IP address of the NE management network, modify the hosts file and run
command /etc/rc.d/init.d/network restart to restart the network and make
the configuration effective.

Steps
1. In the terminal window, open the directory for saving the installation script setup.sh
to modify the authority of the script, as shown in the following.
[root@zte01 ~]# cd /soft/ems_version

[root@zte01 ems_version]# chmod 777 setup.sh

2. Enter command ./setup.sh to run the installation script. The system prompts you
to enter the unzip path, as shown in the following.

3-4

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 3 EMS Installation

[root@zte01 ems_version]# ./setup.sh

******************************************
*********** WELCOME TO INSTALL ***********
******************************************
unzip default path:/tmp/zte_install_tmp,press enter key,
using unzip default path Please input the unzip absolute path:

3. Press Enter key to unzip the files to the default path /tmp/zte_install_tmp. Wait
until the file unzipping is complete. The NetNumen Setup dialog box appears.
4. Choose English from the dropdown list and click Next to open the License agreement
dialog box.
5. Select the I accept the license agreement check box and click Next to open the
Select installation style dialog box as shown in the following figure.

Figure 3-1 Select Installation Style

6. In the Available installation styles field, select Normal Installation (that is,
completely new installation). In the Available installation types field, select Server
Program. Click Next to open the Network scale dialog box as shown in the following
figure.

3-5

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Figure 3-2 Network Scale

7. Select the proper scale according to the practical physical memory.

l Scale 1: for 4 GB – 7 GB RAM
l Scale 2: for 8 GB – 15 GB RAM
8. Click Next to open the Installation product dialog box as shown in the following figure.

3-6

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 3 EMS Installation

Figure 3-3 Installation Product

9. Select product options and set the installation directory according to your needs.

Operation Steps

Select product options l Select All Products > CN > HLR > USPP.
The system automatically selects All Products > UCA > uca
(Unified Common Applications) and All Products > CN >
COMMON.
l To enable the northbound adapter function, select All Products
> CN > CN NAF.
The system automatically selects All Products > Component >
CORBA notify service.

Set the installation l Enter the path for installing the EMS server in the Installation
directory path box, such as /ems.
l By default, the path for saving the NMS data is the same as the
EMS program path. If you want to change it, deselect the check
box before Both the program area and the data area use the
same path and enter the path.

10. Click Next. (If the path does not exist, a dialog box appears, prompting you to create
the path or select another.) The Database connection config dialog box appears, as
shown in the following figure.

3-7

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Figure 3-4 Database Connection Configuration

11. Set the parameters by referring to the following table.

Table 3-7 Parameters for Database Connection Configuration

Parameter Instructions

Database Type Select Oracle from the dropdown list.

Database IP or hostname Type the IP address or hostname of the local Oracle service.

Database port Type the port of the local Oracle service. Generally the default
(1521) is accepted.

SID Type the name of the database instance, for example, ems.

Database superuser name Type system.

Password Enter the password for user system of the database instance.

12. Click Test Database Connection. The system opens a message box prompting you
perform operations according to the output content on the message box.
l If a message box prompting the success of the connection appears, go to Step
13.
l If the database connection fails. A message box appears displaying the causes.
You can modify the database configuration according to the message, and then
test the database connection again.
13. Click Next to open the Database config dialog box as shown in the following figure.

3-8

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 3 EMS Installation

Figure 3-5 Database Configuration

14. Keep the default setting and then click Next to open the Host information config
dialog box as shown in the following figure.

Figure 3-6 Host Information Configuration

3-9

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

15. Set the parameters by referring to the following table.

Table 3-8 Parameters for Host Configuration

Parameter Instructions

Main process server address Set it to the IP address for the EMS server host.

For an EMS using a dual-server cluster only, and useless for a

VCS configuration single-computer EMS. Set it to the IP address for the standby
EMS server.

EMS ID configuration ID of the EMS server. It is 10000 by default if you do not set it.
To set it, select the Please input EMS ID check box and type
an ID.

Distributed servers Not required for a non-distributed EMS server.

configuration

16. Click Next to open the System information detection dialog box as shown in the
following figure.

Figure 3-7 System Information Detection

3-10

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 3 EMS Installation

Note:
If any detection item is not passed, the server application may fail to be installed. Do
troubleshooting according to the messages displayed at the lower part of the window.
If you cannot remove the faults, contact ZTE after-sales personnel.

17. Confirm that every detection item has a Detect Result of Pass, and then click Next
to open the Installation information confirm dialog box.
18. Check whether the installation information is correct.
l Yes: Click Install to unzip and copy files.
l No: Click Back and go back to proper steps to redo the configuration.
19. When the progress reaches 100%, click Next. A message box appears, asking
whether to execute the SQL scripts immediately or not. Click Yes to execute SQL
scripts.
20. When the progress reaches 100%, click Next to open the Parameter set window.

Figure 3-8 Parameter Settings

21. Set the parameters as needed.

3-11

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Note:
l This step involves may parameters. This manual describes the parameters for
commonly-used Northbound interfaces and clock servers only. If you need to
change other parameter settings, contact ZTE for help.
l You may not set the parameters right now, and set them later after the EMS
server is installed. To do this, run runPlugCenter.sh in the installation directory
/ems/uif in the terminal window, and open the Unified Installation Frame
Configuration Center

Item Steps

CN NAF Configuration If you has enabled the northbound adapter function (NAF) at Step 9,
you should perform the following.
i. On the Configuration Center navigation tree, select Products
Configuration > CN NAF Configuration. The northbound inter-
face parameter setting dialog box is displayed in the Server field,
as shown in Figure 3-9.

ii. Select northbound interfaces as needed. The following options

are available.
l Northbound CORBA Specifications: Select a CORBA spec-
ification as needed and type the IP address for communi-
cating with the superior CORBA (that is, an IP address for
the northbound NE management network) in the CORBA IP
field.
l Northbound UNIEMI FM Interface: Northbound Unified El-
ement Management Interface (UNIEMI) Fault Management
(FM) interface
l Northbound SNMP FM Interface
l Northbound MML Interface
l Northbound MML Inventory Management
l Northbound Topology File Interface
You may need to set some configuration files according to the
Northbound interfaces that you have selected. Contact ZTE to help
you to do so.

3-12

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 3 EMS Installation

Item Steps

SNTP information Do the following to set NTP clock synchronization.

i. On the Configuration Center navigation tree, select OS NTP

Configuration > OS NTP Configuration to open the interface
for setting clock server parameters, as shown in Figure 3-10.

ii. Set the clock server parameters.

l If the superior clock server exists, select the Enable exter-
nal clock source radio box and type the IP address of the
superior clock server in the Main clock server IP text field.
If there is also a standby clock server, select the Standby
clock server IP and type its IP address.
l If there is no superior clock server, select the Enable the
local clock source radio box.

iii. Click the Start button to start the NTP service. A dialog box noti-
fying success opens if the clock server settings are valid.
Note that the NTP service status displayed on this dialog box
indicates the status of the NTP service process only. To check
the actual NTP service status, carry out the ntpq -p in the CGSL
Terminal window several minutes later after you started the NTP
service. If the command execution result contains “*”, the NTP
service is successfully started.
The settings of superior clock server or the local clock server are
saved in file /ums-server/works/cluster/deploy/deploy-c
luster.properties. For details about the contents in this file,
refer to A.7 Introduction to Files for EMS Clock Configuration.

3-13

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Figure 3-9 CN NAF Parameter Settings

3-14

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 3 EMS Installation

Figure 3-10 Clock Server Parameter Settings

22. Click Next. A dialog box asking for your confirmation on the parameter settings
appears.

Note:
Depending on the parameters you have set, the confirmation dialog box may not open.

23. Click Yes on the confirmation dialog box. The system initialization progress begins.

24. When the progress indicator reaches 100%, click Next to open the Installation
finished dialog box.
25. Click Finish to complete the installation of the EMS server.

– End of Steps –

3.3.2 Starting EMS Server

Abstract
This topic introduces how to start the EMS server.

3-15

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Prerequisites
l You have logged in to zte01 as user root.
l You have completed the installation of the EMS server software.
l The Oracle database has been properly started.

Steps
1. On the terminal window, run the cd /ems/ums-server command to open the
directory in which the boot scripts are saved.
2. Run the ./console.sh command to start the EMS server console.

Tip:
l If the system reminds you that the authorities are not enough, run the chmod 777
console.sh command to modify the authority on the boot scripts.
l While connecting to the server to start the EMS server application through
the remote connecting tool, run the ./console.sh & command to start the
program at the background, avoiding the stop of the process after the connection
is removed.

– End of Steps –

Result
Click CONSOLE > Console to view the process boot information, as shown in the following
figure. The Operation Result of each processes is Successful, indicating that the EMS
server has been started.

3-16

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 3 EMS Installation

Figure 3-11 the EMS server Console

3.4 EMS Client Installation

3.4.1 Installing Operating System for an EMS Client
Requirements for OS
The EMS client OS requirements are as follows:
l Windows Server 2003 + Service Pack 2, or Windows XP
l The OS should be installed in the default directory on Partition C.
l Password for administrators: set according to your engineering specifications.
l Password for maintenance users: set according to your engineering specifications.

Installation of OS
1. For detailed operation steps, refer to the installation guide attached to the OS CD/DVD.
2. Set the IP address of the EMS client. Refer to A.5 Setting IP Address on Windows for
details.
3. If the EMS client is remote from the EMS server, a route to the EMS server need be
configured. Refer to A.6 Setting a Route on Windows for details.

3-17

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

3.4.2 Installing Antivirus Software

Antivirus Software Installation
After the operating system is installed, immediately install the antivirus software and the
latest virus updates. For detailed installation procedures, refer to the installation guide of
the antivirus software.

Antivirus Policies
The following policies are recommended:
l Turn on the real-time monitoring feature and do not scan zipped files.
l Shut down the scheduled scanning function.
l Change the manual scanning policy to report virus without deletion or quarantine.

3.4.3 Installing EMS Client

Abstract
This topic introduces how to install the EMS client application.
The installation directory is D:\netnumen\ems. After the installation, the files may occupy
a space of about 377 MB.

Note:
l The directory names involved during the installation can be modified as required.
l This topic introduces a completely new installation process.

Prerequisites
l The operating system and its patches have been installed, and the operating system
is running properly.
l The network element management programs of other versions on the client are
stopped.
l The installation software has been downloaded to the local disk or mapped as a
network driver.
l You known the IP address of the superior time server (SNTP server). The EMS server
generally acts as the timer server of EMS client, with port number 21124.

Steps
1. Open the ems_version folder in the installation directory, and then double-click set
up.bat. The Install windows opens.

3-18

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 3 EMS Installation

2. Input the disk where the temporary files are to be stored and press the Enter key, or
simply press the Enter key to select the default temporary directory. The file unzipping
starts. The NetNumen Setup dialog box appears.
3. Choose English from the dropdown list and click Next to open the License agreement
dialog box.
4. Select the I accept the license agreement check box and click Next to open the
Select installation style dialog box as shown in the following figure.

Figure 3-12 Select Installation Style

5. In the Available installation styles field, select Normal Installation (that is,
completely new installation). In the Available installation types field, select Client
Program. Click Next to open the Installation product dialog box as shown in the
following figure.

3-19

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Figure 3-13 Installation Product

6. Select product options and set installation paths according to your needs.

Operation Steps

Select product options Select All Products > CN > HLR > USPP.
The system automatically selects All Products > UCA > uca (Unified
Common Applications) and All Products > CN > COMMON.

Set installation paths l Enter the path for installing the EMS server in the Program Area
Path box, such as D:\netnumen\ems.
l By default, the setting of Data Area Path is the same as
Program Area Path. If you want to change the data area path,
select the check box at the end and enter the path that you want.

7. Click Next.

If the installation path does not exist or is not empty, a dialog box opens prompting you
whether to create it. Click Yes.
The System information detection dialog box as shown in the following figure.

3-20

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 3 EMS Installation

Figure 3-14 System Information Detection

Note:
If any detection item is not passed, the EMS client may fail to be installed. Do
troubleshooting according to the messages displayed at the lower part of the dialog
box. If you cannot remove the faults, contact ZTE after-sales personnel.

8. Confirm that every detection item has a Detect Result of Pass, and then click Next
to open the Installation information confirm dialog box.
9. Check whether the installation information is correct.
l Yes: Click Install to unzip and copy files.
l No: Click Back and go back to proper steps to redo the configuration.
10. When the progress indicator reaches 100%, click Next to open the Parameter set
dialog box as shown in the following figure.

3-21

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Figure 3-15 Parameter Settings

11. Set the parameters as needed.

This step involves may parameters. This manual describes the parameters clock
servers only. If you need to change other parameter settings, contact ZTE for help.

Note:
You can keep the default parameter settings and set them later after the EMS server is
installed. To do this, do either of the following to open the NetNumen Configuration
Center.
l Double-click the NetNumen Config Center short-cut menu on the desktop.
l Select menu Start > All programs > NetNumen Unified Management System
> NetNumen Config Center.

a. On the Configuration Center navigation tree, select OS NTP Configuration >

OS NTP Configuration to open the interface for setting clock server parameters,
as shown in the following figure.

3-22

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 3 EMS Installation

Figure 3-16 Clock Server Parameter Settings

b. Select the Enable external clock source radio box and type the IP address of
the superior clock server (generally the EMS server) in the Main clock server IP
text field.

Note:
The settings of superior clock server or the local clock server are saved in file \um
s-client\works\global\deploy\deploy-usf.properties. For details
about the contents in this file, refer to A.7 Introduction to Files for EMS Clock
Configuration.

12. Click Next. A dialog box opens, prompting you whether to initialize all client scenes.
13. Click Yes to start system initialization.

14. When the progress indicator reaches 100%, click Next to open the Installation
finished dialog box.
15. Click Finish to complete the installation of the EMS client.

– End of Steps –

3-23

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

3.4.4 EMS Client Login

3.4.4.1 Logging In to a EMS Client

Abstract
You can log in to the EMS in two ways:
l Logging in through the EMS client: All the functional modules of EMS are started.
l Logging in through the EMS client portal: You can select a wanted functional module
to start.
This topic introduces how to log in to the EMS through the EMS client.

Prerequisites
l You have installed the EMS client application.
l The EMS server has been successfully started.
l The EMS client communicates properly with the EMS server.
l The EMS client and the EMS server have consistent version and language.

Steps
1. Select one of the following ways to open the login dialog box as shown in Figure 3-18.
l Click Start > All Programs > NetNumen Unified Management System >
NetNumen Client.
l Double-click the shortcut icon on the desktop, as shown in Figure 3-17.

Figure 3-17 EMS Client Shortcut

3-24

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 3 EMS Installation

Figure 3-18 Login Dialog Box of EMS Client

2. Set parameters according to the following table.

Table 3-9 Description for Parameters Involved in Login Dialog Box

Parameter Description Default

User Name The name of the user who are logging in. admin

Password The password of the user. Null

Server Address The IP address of the EMS server. When the 127.0.0.1
EMS server and client are installed on different
computers, input the actual IP address of the
EMS server. When they are installed on the
same computer, input the actual IP address of
the EMS server or use the default IP address.

3. Click OK to log in. If this is the first time you log in, the system will update the service
model. After update, a message box for confirmation pops up.
4. Click OK to confirm the login.
– End of Steps –

Result
After a while, the client window opens, as shown in the following figure.

3-25

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Figure 3-19 NetNumen Unified Management System (EMS Client)

3.4.4.2 Logging In to a EMS Client Portal

Abstract
You can log in to the EMS in two ways:
l Logging in through the EMS client: All the functional modules of EMS are started.
l Logging in through the EMS client portal: You can select a wanted functional module
to start.
This topic introduces how to log in to the EMS through the EMS client portal.

Prerequisites
l You have installed the EMS client application.
l The EMS server has been successfully started.
l The EMS client communicates properly with the EMS server.
l The EMS client and the EMS server have consistent version and language.

3-26

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 3 EMS Installation

Steps
1. Select one of the following ways to open the login dialog box as shown in Figure 3-21.
l Click Start > All Programs > Netnumen Unified Management System >
Netnumen Client Portal.
l Double-click the shortcut icon on the desktop, as shown in Figure 3-20.

Figure 3-20 EMS Client Portal Shortcut

Figure 3-21 Login Dialog Box of EMS Client Portal

2. Set parameters according to Table 3-10.

Table 3-10 Description for Parameters Involved in Login Dialog Box

Parameter Description Default

User Name The name of the user who are logging in. admin

Password The password of the user. Null

Server Address The IP address of the EMS server. When the EMS 127.0.0.1
server and client are installed on different comput-
ers, input the actual IP address of the EMS server.
When they are installed on the same computer, in-
put the actual IP address of the EMS server or use
the default IP address.

3. Click OK to open the Portal window, as shown in the following figure.

3-27

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Figure 3-22 Portal

4. Click and select the corresponding functional module as needed. The functional
modules are as described in the following table.

Table 3-11 Description for Functional Modules

Module Description

CN Maintenance Clicking it, you can perform operations related to topology,

alarms, performance, configuration, and security.

EMS client Clicking it, you can enter the EMS client, which contains all
functional modules of EMS.

Fault Management Clicking it, you can query and set alarms and notifications.

Performance Management Clicking it, you can query and create a performance task.

Maintenance Clicking it, you can perform maintenance and security related
operations.

– End of Steps –

3-28

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 4
Configuration for OMM
Accessing to EMS
Table of Contents
Introduction to OMM Access.......................................................................................4-1
Importing the License .................................................................................................4-2
Creating a USPP Node...............................................................................................4-3
Creating a Network Element Agent.............................................................................4-4
Starting a Network Element Agent..............................................................................4-6
Updating USPP Version Number ................................................................................4-8
Synchronizing the License..........................................................................................4-9
Adding an NE Office of USPP ..................................................................................4-11

4.1 Introduction to OMM Access

Overview
After installation of the NMS subsystem software, it is necessary to configure the access
of OMM to EMS so that EMS can manage each OMM.

OMM Access Flow

The following table describes how to configure the access of OMM to EMS.

Table 4-1 Flow of OMM Access Configuration

Step Operation

1 Load the License onto the EMS server.

2 Create USPP nodes.

3 Create NE agents.

4 Start NE agents.

5 Update the USPP version number.

6 Validate the License.

7 Add physical USPP offices.

4-1

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

4.2 Importing the License

Abstract
Importing the License file onto the EMS server is to save the License file into the related
folder, so that the License may be synchronized later.

Prerequisites
l The License file is ready.
l You have logged in to the EMS client and have the right to maintain the core network.
l Both EMS and OMM NE management systems are correctly configured and
connected according to the networking plan.
l Both EMS and OMM NE management systems work properly.

Steps
1. On the main window of the EMS client, click Maintenance > CN Maintenance from
the menu bar to enter the CN Maintenance view.
2. On the NE list, select the EMS server node.
3. On the CN Maintenance navigation tree, click License Management to open the
License Management tab.
4. On the License Management tab, click the (Update License Info) button on the
tool bar to open the Please Choose License File dialog box. Double-click to select
the desired License file on the dialog box.
– End of Steps –

Result
After the License file is imported, the window is as shown in the following figure.

4-2

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 4 Configuration for OMM Accessing to EMS

Figure 4-1 License Imported Successfully

4.3 Creating a USPP Node

Abstract
This topic describes how to create a USPP node according to the networking plan, that is,
to create a network element node supporting all the NE types of the OMMs accessing to
EMS.

Prerequisites
l The License file is already imported.
l You have logged in to the EMS client and have the right to perform the USPP
configuration.
l Both EMS and OMM NE management systems are correctly configured and
connected according to the networking plan.
l Both EMS and OMM NE management systems work properly.

Steps
1. On the main window of the EMS client, choose Configuration > MML Terminal from
the menu bar to enter the MML Terminal view.

2. In the NE list, select the EMS Server node.

4-3

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

3. Select USPP Management > USPP Node Configuration Management > Create
USPP to open the CREATE USPP command configuration interface as shown below.

Figure 4-2 CREATE USPP Command Configuration Interface

4. Set the parameters referring to the following table.

Table 4-2 CREATE USPP Command Parameters

Parameter Configuration Description

TYPE Sets the sub-NE types of the USPP node, including all the NE types
of the accessing OMMs.
Click the to select the desired type in the dialog box that appears.
After the creation, you can only add but not delete the office subtypes.

USER LABEL Alias of the USPP node, valued with 0–50 characters.

5. Click Execute button to execute the command.

– End of Steps –

Result
In the NE list, a USPP node appears under the EMS Server node.

4.4 Creating a Network Element Agent

Abstract
In ZXUN USPP, the OMM NE management systems accesses to EMS NE management
system for integrated management, implementing centralized topology, centralized alarm,
centralized report, centralized security management, centralized log management, and
MML.

This topic describes how to create a network element agent (agent of the OMM server) on
EMS.

Prerequisites
l You have logged in to the EMS client and have the right to perform topology
management.
l Both EMS and OMM NE management systems are correctly configured and
connected according to the networking plan.
l Both EMS and OMM NE management systems work properly.
l The USPP node is created.

4-4

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 4 Configuration for OMM Accessing to EMS

Steps
1. On the main window of the EMS client, click Topology > View Topology from the
menu bar to enter the Topology Management view.
2. Right-click the EMS Server node on the NE Tree tab and then click Create Object >
CN NE Agent from the shortcut menu to open the Create NE Agent dialog box.
3. Click V4 OMS to open the V4 OMS tab, as shown in the following figure.

Figure 4-3 Create NE Agent

4. Set the parameters by referring to the following table.

Table 4-3 Parameters for Creating an NE Agent

Parameter Configuration Description

Basic Attributes Name Name of the NE agent, that is, the name of
the OMM server accessing to EMS, with 0–50
characters

Vendor Name of the vendor of the OMM server accessing

to EMS, with 0–100 characters

IpAddress IP address of the OMM server accessing to EMS,

IPv4 type

4-5

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Parameter Configuration Description

Location Location of the OMM server accessing to EMS,

with 0–100 characters

EMS Address IP address of the EMS server. Keep the default

value.

Memo Additional information of the network element

agent, with 0–200 characters

Extended Attributes Port Set it to 21125.

Time Zone Choose the time zone.

Time Zone ID

SSH Config Select SSH Config and set the SSH portif you
need to modify the SSH port.
SSH Port

5. Click OK to create the NE agent. The OK message box pops up prompting that the
user NE agent is successfully created but can be used only after restarted.

– End of Steps –

Result
In the NE list, the newly created NE agent appears under the EMS Sever node.

4.5 Starting a Network Element Agent

Abstract
This topic introduces how to start a network element agent on EMS so that OMM can be
connected to EMS.

Prerequisites
l You have logged in to EMS and have the right to perform topology management.
l Both the EMS client and OMM NE management systems are correctly configured and
connected according to the networking plan.
l Both EMS and OMM NE management systems work properly.
l The NE agent is created.

Steps
1. On the main window of the EMS client, click Topology > View Topology from the
menu bar to enter the Topology Management subview.
2. Right-click a created NE agent below the EMS server node on the NE Tree tab and
then choose Start from the popup menu. The Start NE Agent message box pops up.

4-6

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 4 Configuration for OMM Accessing to EMS

The start process is displayed in the box.

The NE agent startup is complete when “OMM Start Successfully” is displayed in the
message box, as shown in Figure 4-4

Figure 4-4 Start the OMM

3. When the NE agent has started up, click Close to close the message box.
– End of Steps –

Result
The icon of the NE agent (such as OMM203 in the following figure) on the NE Tree changes
to (bright), and under the NE agent node there are two more nodes, as shown in the
following figure.

Figure 4-5 NE Agent Node on the NE Tree

4-7

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Tip:
l When the NE agent node has started up as its icon shows but the nodes under it are
still (in grey), the system may be updating the service models. Wait patiently.
l If the service models are updated during te NE agent startup process, a dialog box
opens, prompting you to re-log in. Log out the EMS and log in again.

Follow-Up Action
If a dialog box opens after you re-log in, prompting you to synchronize the license, do not
synchronize the license right now. Update the USPP version first before synchronizing the
license.

4.6 Updating USPP Version Number

Abstract
Updating the USPP version No. is to query and get the latest version of OMM on EMS.

Prerequisites
l You have logged in to EMS NE management system and have the right to perform
the equipment configuration.
l Both EMS and OMM NE management systems are correctly configured and
connected according to the networking plan.
l Both EMS and OMM NE management systems work properly.
l The NE agent is started.

Steps
1. On the main window of the EMS client, click Configuration > MML Terminal from the
menu bar to enter the MML Terminal view.
2. In the NE list, select the EMS server node.

3. Select USPP Management > USPP SNO Management > Show USPP SNO to enter
the Show USPPSNO command configuration interface.
4. Click the Execute button on the interface to execute the command and then view the
execution result.

The version No. displayed indicates the latest version of the USPP.
5. Select USPP Management > USPP SNO Management > Update USPP to open the
UPDATE USPP command configuration interface as shown in the following figure.

4-8

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 4 Configuration for OMM Accessing to EMS

Figure 4-6 UPDATE USPP Command Configuration Interface

6. Set SNO (USPP version) to the latest version number obtained by the SHOW
USPPSNO command.
7. Click the Execute button on the interface to execute the UPDATE USPP command.
The Dangerous Command Configuration message box pops up, prompting that the
command execution may cause damage to the system.
8. Click OK to confirm the USPP SN update.

Note:
l The USPP update process may take a time. Wait patiently.
l When the update is complete, the system may present a message box with the
update service models and ask you to re-log in. Re-log in as the message box
prompts.

– End of Steps –

Result
On the MML command navigation tree, select USPP Management > USPP SNO
Management > Show USPP SNO to open the SHOW CURRENTUSPPSNO command
configuration interface, and click Execute to run the command. The serial number of the
currently loaded USPP version you queried should be the newly updated SN.

4.7 Synchronizing the License

Abstract
This topic describes how to synchronize the License on the EMS server database to the
OMM server, so that the License takes effect on the OMM server.

Prerequisites
l You have logged in to the EMS client and have the right to manage the License.
l Both EMS and OMM NE management systems are correctly configured and
connected according to the networking plan.
l Both EMS and OMM NE management systems work properly.
l The License is validated.

4-9

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Steps
1. On the main window of the EMS client, click Maintenance > CN Maintenance from
the menu bar to open the CN Maintenance view.
2. On the NE list, select the EMS server node.
3. On the CN Maintenance navigation tree, click License Management to open the
License Management tab.
4. Click the (Synchronization License Info) button to open the Synchronization Lice
nse Info window as shown in the following figure.

Figure 4-7 Synchronization License Info

5. Select the OMM server from the AMO List and click to move it to the Preparation
synchronized AMO list, and then click OK.
– End of Steps –

Result
A message box appears, prompting that the license synchronization is complete. To view
the synchronization details, click Details. After viewing, click OK to close the message
box.

4-10

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 4 Configuration for OMM Accessing to EMS

4.8 Adding an NE Office of USPP

Abstract
This topic introduces how to configure an office managed on EMS.

Prerequisites
l The NE office is already created on OMM.
l You have logged in to the EMS client and have the right to perform the data configu-
ration.
l Both EMS and OMM NE management systems are correctly configured and
connected according to the networking plan.
l Both EMS and OMM NE management systems work properly.

Steps
1. On the main window of the EMS client, click Configuration > MML Terminal from the
menu bar to enter the MML Terminal view.

2. In the NE list, click and select the EMS server node.

3. Select USPP Management > USPP NE Configuration Management > Add USP
PNE to open the ADD USPPNE command configuration interface as shown in the
following figure.

Figure 4-8 ADD USPPNE Command Configuration Interface

4. Set the related parameters by referring to the following table.

Table 4-4 ADD USPPNE Command Parameters

Parameter Configuration Description

AMO NAME Name of the AMO, 0–100 characters. The name of the node (on the NE
Tree) under which the AMO is to be accessed is recommended, such as
OMM203-USPP_203 in Figure 4-9.

BUREAU NO ID of the office on OMM which is managed on EMS, ranged in 1–254.

It should be consistent with the Bureau No. set during adding a network
element office on the OMM.

4-11

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Figure 4-9 An Example of AMO Name

5. Click the Execute button on the page to execute the command.

– End of Steps –

Result
The created NE office of USPP appears under the USPP > Manager Device node in the
NE list. The office name displayed is the alias of the office corresponding to the office ID
set by the ADD USPPNE command.

4-12

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 5
Version Loading
Table of Contents
Introduction to Version Loading ..................................................................................5-1
Version Loading for OMP ...........................................................................................5-2
Version Loading for other Modules ...........................................................................5-24
DBIO Configuration ..................................................................................................5-33
Interface Processor Configuration ............................................................................5-34

5.1 Introduction to Version Loading

Version Loading Flow
The following table shows the flow to load versions onto the boards.

Table 5-1 Version Loading Flow

Step Operation

1 Load versions onto the OMP board.

2 Load versions onto the SWBB1 blades.

3 Load versions onto other modules.

4 Configure the DBIO.

5 Configure the interface processor.

Note:
l You should load OMP versions with a DTF tool.
l The version files for the CGEL and CGSL operating systems should be uploaded to
the OMP board from the OMM.
l After OMP versions are loaded, you should load the versions for SWBB1 switching
blades. Only when the SWBB1 blades are working properly can other modules get
their versions.
l Other modules automatically get versions from the OMP board after they are
successfully powered on.
l To confirm whether a module is successfully powered on, you may need to use the
ushell tool.

5-1

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Necessary Operations
For version loading, you need to do the following:
l Log in to a blade.
You can use a remote control tool or use the command line window to log in to a
blade from the debugging PC. The procedure of logging in with a remote control tool
is similar to logging in to a CGSL host, you can see the description about SecureCRT
in A.2 Establishing a Remote Control Connection to CGSL for reference.
l Upload files.
This operation is similar to uploading files to a CGSL host, you can see A.3
Transferring Files to a CGSL Host for reference.
l To log in to a blade other than OMP, you can use the IP address (generated
automatically for the control plane) in the 128 network section. You need to connect
a Base network interface on the rear board of the blade to a network interface of the
debugging PC, and you need also set an IP address in the 128 network section on
the debugging PC.

Note:
Base network interfaces can be used only after the necessary versions are loaded
onto the SWBB1 switching board.

5.2 Version Loading for OMP

5.2.1 Checking the DTF Port
Abstract
You should load the versions of ZXUN USPP front end with a DTF tool using Port 21.
This topic describes how to check whether Port 21 of the debugging PC is occupied. The
DTF tool may fail to start if this port is occupied.

Prerequisites
You have logged on to the debugging PC.

Steps
1. Click Start > Run to open the Run dialog box.
2. Type cmd in the Open field and click OK to open the command line dialog box.
3. Run netstat -ano|find ":21"|find "LISTENING", and then check the result.

5-2

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 5 Version Loading

l If there is no output information, Port 21 is not occupied. The DTF port checking
is finished.
l If the following output information appears, Port 21 is occupied. Proceed with the
remaining steps.

C:\Documents and Settings\Administrator>netstat -ano|find ":21"|find

"LISTENING"
TCP 0.0.0.0:21 0.0.0.0:0 LISTENING 5780

Tip:
The last value is the identifier of the process (PID) that is using Port 21.

4. Right-click on any blank area of the Windows task bar, and choose Task Manager
from the shortcut menu to open the Windows Task Manager dialog box.
5. Open the Processes tab and select the process (by finding the PID) that is using Port
21.

Note:
If PIDs are not displayed, do the following.
i. From the menu of Windows Task Manager, choose View > Select Columns to
open the Select Columns dialog box.
ii. Select the PID (Process Identifier) check box.
iii. Click OK to return to the Windows Task Manager. PIDs are now displayed.

6. Click End Process. A dialog box prompting for your confirmation opens.
7. Click Yes to confirm.
– End of Steps –

5.2.2 Setting the DTF Tool

Abstract
The DTF tool can work as a DHCP server and an FTP server.
This topic describes how to set the DTF tool so as to make it ready for uploading the version
file package onto the OMP module.

5-3

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Prerequisites
l You have finished the CMM configuration. Contact ZTE for how to configure CMM.
l According to the blade model that the OMP uses, you have copied the right version
package onto the debugging PC from \zxver_v4\front\HLR\RELEASE in the
ZXUN USPP software package.
à DPBA2: ZXUN_USPP_DPBA_CGEL_EN_V4.11.10.P4.B1.pkg
à DPBB2: ZXUN_USPP_DPBB_CGEL_EN_V4.11.10.P4.B1.pkg
l The DTF Tool package (in the \tools\DTF folder of the ZXUN USPP software
package) is on the debugging PC.
l You have connected the network interface of the debugging PC to a Fabric network
interface of the OMP board with a network cable.
l You have checked the DTF port and have confirmed that Port 21 is not in use.

Steps
1. On the debugging PC, run the DTF tool (DTFserver.exe). The DHCP Server
interface appears by default, as shown in the following figure.

Figure 5-1 DTF Window

2. Start the DHCP server.

a. Click the DHCP Server options button to open the Options dialog box as shown
in the following figure.

5-4

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 5 Version Loading

Figure 5-2 DHCP Options

b. Set the parameters on the DHCP Options tab by referring to the following table.

Table 5-2 Parameters of DHCP Options

Parameter Description

Autorun when application start Select this check box.

Only reply DHCP request from Selected by default, and cannot be changed.
OMC

Listen IP You can type the IP address in the 129 network section
or select INADDR_ANY (listening all IP addresses).
INADDR_ANY is recommended. And then click
Apply.

c. Click the Board Options tab to open it, as shown in the following figure.

5-5

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Figure 5-3 Board Options

d. Set the parameters on the Board Options tab by referring to the following table.

Caution!
The bureau (office ID), rack and shelf that you enter on the Board Options tab
must exist in the configuration of the CMM/NCMM.

Table 5-3 Parameters of Board Options

Parameter Description

Board Type Select according to the actual hardware configuration.

l For DPBA2, select SBCO.
l For DPBB2, select SBCJ.

Bureau Office ID number (of the OMP) configured in the CMM/NCMM

Rack Rack number (of the OMP) configured in the CMM/NCMM

Shelf Shelf number (of the OMP) configured in the CMM/NCMM

Slot Slot number of the OMP

CPU CPU number of the OMP, generally 1

5-6

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 5 Version Loading

Parameter Description

Version Select the proper version file for CGEL according to your OMP
hardware model:
Click the button to select the version package file.

e. Click the Save Board button.

f. Click Close to close the Options dialog box.
g. In the DHCP server setting window, click the Start DHCP Server button, and
then check the operation result. If the DHCP server successfully starts up, the
information as shown in the following figure appears.

Figure 5-4 Start Up DHCP Server

3. Start the FTP server.

a. Click the FTP Server bar to open the FTP server setting window shown in the
following figure.

Figure 5-5 FTP Server

b. Click the FTP Server options button to open the Options dialog box as shown in
the following figure.

5-7

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Figure 5-6 FTP Options

c. Set the parameters by referring to the following table.

Table 5-4 Settings of FTP Options

Pane Description

FTP Settings l Max Conn.: Maximum number of connections. Keep the default
value (10).
l Timeout: Connection timeout time. Keep the default value (5
minutes).
l Welcome: Welcome information for successful connection. Keep
the default: Welcome to ZTE FTP Server
l Bye: Notification information for the case when you quit FTP. Keep
the default value: Bye Bye
l Autorun when application start: Whether to automatically start
the FTP server when the DTF tool starts. Select it.
Click Apply.

5-8

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 5 Version Loading

Pane Description

User Settings Select 3gplat in the text field on the up-right, and then set the following
user information:
l User: Keep the default: 3gplat
l Set/Change Password: Click it to set or change the user
password. The default password of user 3gplat is 3gplat
l Path: Set it to the path of the version files.
l This user can: User permissions. Select all.
Click Save User to save the user settings.

d. Click Close to close the Options dialog box and return to the FTP server setting
window.
e. In the FTP server setting window, click the Start FTP Server button, and then
check the operation result. If the FTP server successfully starts up, the information
as shown in the following figure appears.

Figure 5-7 Start Up FTP Server

4. Close the DTF tool and start it again.

– End of Steps –

Result
The setting of the DTF tool is complete, and the DHCP server and the FTP server have
started up.

5.2.3 Setting OMP Bootup Mode

Abstract
Before the OMP board is powered on for the first time, you must set its bootup mode to
DHCP so that it can get the version files from the DTF tool which is ready on the debugging
PC.
This topic describes how to set the OMP bootup mode.

Prerequisites
You have connected a display and a keyboard to the proper interfaces on the OMP rear
board.

Steps
1. Power on the blade for the OMP. The following boot information appears on the display.

5-9

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

+--------------------------------------------------------------+
| BOOT PASSWORD NOTICE |
|1. Password String: 3GPLAT (CASE NOT SENSITIVE) |
|2. Input Timeout :5 Seconds, or else autorun |
|3. Max Input Retry: 5 Times, or else Booting bypass boot menu |
+--------------------------------------------------------------+

2. Press any key to stop autoboot. The screen display is as follows.

Hit any key to stop autoboot: 5
Boot Password(3GPLAT or 3gplat)->

3. Type the boot password (3gplat) and press Enter, and then set the bootup mode of
the OMP blade to DHCP, as shown in the following.

BootMode Selection as follow:

0 -Auto boot
1 -Manual BOOT Config
2 -Show BOOT Config
? -Print this help list
[3GPlat BOOT]: 1 /*Type 1*/
Curr Bootmode(0:Local;3:DHCP;1:FTP;4:TFTP): 3 /*Select 3*/
OMC Port: eth4 /*Press Enter to accept the default value.*/
Ctrl Port: eth2 /*Press Enter to accept the default value.*/
Linux console(0:VGA;1:COM1;2:COM2): 0
/*Select output mode of the serial port, 0: Display, 1: Front board, 2: Rear board*/
[BSP]: SaveConfig OK!
Manual boot now?(Yy/Nn) Y /*Enter Y*/

– End of Steps –

Result
The blade where the OMP module is on reboots automatically.

5.2.4 Checking the first Power-on of OMP

Abstract
This topic describes how to check the result when the OMP is powered on for the first time.

Prerequisites
l You have set the DTF tool on the debugging PC.
l You have set the OMP bootup mode.
l The network connection between the OMP board and the debugging PC is normal.

5-10

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 5 Version Loading

Steps
1. Check the returned messages on the DTF tool on the debugging PC, and you can find
the following.
l On the DHCP Server tab, you can find “Send dbcp response ok”
l On the FTP Server tab, you can find a message notifying successful transfer of
the version files, such as “150 Opening BINARY mode data connection for file
transfer.”

Tip:
If the returned messages are not correct, you can do the following.
i. Check whether the settings of the DTF tool are correct.
l Yes: Go to Step 2.
l No: Correct the settings and restart the OMP blade.

ii. Contact ZTE.

2. Log on to the OMP blade, and confirm that the processes included in the service set
have already started up.

Note:
For details about how to check the service set and the information about the service
set, see Appendix B Checking Service Set.

3. Check the indicators on the panel of the OMP blade and confirm that status of each
indicator is normal.

Table 5-5 OMP Idicators

Indicator Status

OOS Off: The blade is working.

OK Flashing in green: The blade is healthy.

ACT Always on in green: The blade is active.

HOST Flashing in green: The blade is working normally.

H/S Off: The blade is not being hot-swapped.

– End of Steps –

5-11

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

5.2.5 Formatting a Hard Disk

Abstract
This topic describes how to format a hard disk.
The hard disk of a delivered blade is generally already formatted. You may just check the
disk and do not need to format it.

Caution!
If you format a hard disk, the data on the disk will be lost. Make sure that you really need
to do so.

Prerequisites
You have logged on to the OMP blade by using a remote control tool complying with the
SSH2 protocol.

Steps
1. Check the partitions, and then do according to the check result.
l No partition: Go to Step 4.
l Only partition /dev/sda1 exists: Go to Step 2.
l All other partitions except /dev/sda1 exist: Go to Step 3.
(none) login: zte /*User name*/
Password: /*User password, default: zte*/
Wind River Linux glibc_small (cgl) 1.3
$ su /*Change to User root.*/
# fdisk –l /*Check partitions*/
Disk /dev/sda: 147.0 GB, 147086327808 bytes
255 heads, 63 sectors/track, 17882 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 1 17882 143637133+ 83 Linux

2. Check the file system, and then do according to the check result.
l No error: You do not need to format the disk. Ignore the remaining steps.
l An error exists: Go to Step 3.
# cd /
# mkdir test /*Make Directory test.*/
# mount /dev/sda1 /test/ /*Mount the partition onto the directory.*/
# ls /test/ /*List the contents.*/
lost+found

5-12

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 5 Version Loading

3. Do the following to delete the partitions.

# fdisk -l /*Check partitions.*/

Disk /dev/sda: 146.9 GB, 146999869440 bytes

255 heads, 63 sectors/track, 17871 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sda1 * 1 2610 20964793+ 83 Linux
/dev/sda2 2611 4698 16771860 82 Linux swap
/dev/sda3 4699 17871 105812122+ f Win95 Ext'd (LBA)
/dev/sda5 4699 7308 20964793+ 83 Linux
/dev/sda6 7309 11876 36692428+ 83 Linux
/dev/sda7 11877 16444 36692428+ 83 Linux
# fdisk /dev/sda /*Open the Format menu.*/
ioctl32(exe:1305): Unknown cmd fd(3) cmd(80081272){00} arg(fffaa1ec)
on /dev/scsi/host0/bus1/target0/lun0/disc
Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel
Building a new DOS disklabel. Changes will remain in memory only,
until you decide to write them. After that, of course, the previous
content won't be recoverable.
The number of cylinders for this disk is set to 17871.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)
Command (m for help): p /*Check the contents of the partition table.*/
Disk /dev/sda: 146.9 GB, 146999869440 bytes
255 heads, 63 sectors/track, 17871 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 2610 20964793+ 83 Linux
/dev/sda2 2611 4698 16771860 82 Linux swap
/dev/sda3 4699 17871 105812122+ f Win95 Ext'd (LBA)
/dev/sda5 4699 7308 20964793+ 83 Linux
/dev/sda6 7309 11876 36692428+ 83 Linux
/dev/sda7 11877 16444 36692428+ 83 Linux
Command (m for help): d
/*The partition table is not empty. Enter d to delete the partition.*/
/*You can proceed only when the partition table is empty.*/
Partition number (1-7): 7
Command (m for help): d
Partition number (1-6): 6

5-13

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Command (m for help): d

Partition number (1-5): 5
Command (m for help): d
Partition number (1-5): 4
Command (m for help): d
Partition number (1-5): 3
Command (m for help): d
Partition number (1-5): 2
Command (m for help): d
Partition number (1-5): 1
Command (m for help): m /*See the help information.*/
Command action
a toggle a bootable flag
b edit bsd disklabel
c toggle the dos compatibility flag
d delete a partition
l list known partition types
m print this menu
n add a new partition
o create a new empty DOS partition table
p print the partition table
q quit without saving changes
s create a new empty Sun disklabel
t change a partition's system id
u change display/entry units
v verify the partition table
w write table to disk and exit
x extra functionality (experts only)
Command (m for help): p /*Check the contents of the partition table.*/
Disk /dev/sda: 146.9 GB, 146999869440 bytes
255 heads, 63 sectors/track, 17871 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/*All partitions are deleted, and the partition table is empty.*/

4. Do the following to format a hard disk that is not partitioned.

# fdisk /dev/sda /*Open the Partition menu.*/

Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel
Building a new DOS disklabel. Changes will remain in memory only,
until you decide to write them. After that the previous content
won't be recoverable.
The number of cylinders for this disk is set to 17882.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)

5-14

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 5 Version Loading

2) booting and partitioning software from other OSs

(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p /*Print the list of partitions.*/
Disk /dev/sda: 147.0 GB, 147086327808 bytes
255 heads, 63 sectors/track, 17882 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
Command (m for help): n /*Create a partition.*/
Command action
e extended
p primary partition (1-4)
p /*Set the partition as a primary partition.*/
Partition number (1-4): 1 /*Set the partition number to 1.*/
First cylinder (1-17882, default 1): Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-17882, default 17882):
Using default value 17882 /*Press Enter to accept the default value.*/
Command (m for help): w /*Perform the Write operation.*/
The partition table has been altered!
Calling ioctl() to re-read partition table
# mke2fs /dev/sda1 /*Create the file system on this partition.*/
mke2fs 1.38 (30-Jun-2005)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
17956864 inodes, 35909283 blocks
1795464 blocks (5.00%) reserved for the super user
First data block=0
1096 block groups
32768 blocks per group, 32768 fragments per group
16384 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Writing inode tables: done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 23 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.

5. Reboot the blade. For how to reboot a blade that has a CGEL operating system, see
A.4 Restarting CGEL.
– End of Steps –

5-15

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

5.2.6 Loading and Activating OMP Versions

Abstract
This topic describes how to load and activate OMP versions.

Prerequisites
l The basic processes of OMP have started up.
l The network connection between the OMM client and the OMM server is normal.
l The OMM server and the OMP are within the same network section and the connection
between them is normal.
l The versions to be uploaded to the front end are ready on the debugging PC. (The
version numbers of your files might be different from those mentioned in this topic.)
l The physical data configuration is complete. For details about physical data
configuration, see the Basic Data Configuration Guide manual.

Context
To load the versions of OMP only, you may just load the version for CGEL on DBBA2
(or DPBB2) onto the blade. But for the convenience for later loading versions for other
modules and units, you are recommended to upload all the required version packages
in \zxver_v4\front\HLR\RELEASE\ onto the OMP blade. See the following table for
blades and locations of corresponding version files.

Table 5-6 Blades and Version Packages

Blade Version Package

SWBB1 ZXUN_USPP_SWBB_EN_V4.11.10.P4.B1.pkg

DPBA2 (for CGEL) ZXUN_USPP_DPBA_CGEL_EN_V4.11.10.P4.B1.pkg

DPBA2 (for CGSL) ZXUN_USPP_DPBA_CGSL_EN_V4.11.10.P4.B1.pkg

DPBB0/DPBB2 (for CGEL) ZXUN_USPP_DPBB_CGEL_EN_V4.11.10.P4.B1.pkg

DPBB1 (for CGSL) ZXUN_USPP_DPBB_CGSL_EN_V4.11.10.P4.B1.pkg

DACM ZXUN_USPP_DACM_EN_V4.11.10.P4.B1.pkg

SLB ZXUN_USPP_ASPB_EN_V4.11.10.P4.B1.pkg

Steps
1. On the debugging PC, transfer (with an FTP tool and in binary mode) the version
packages onto the /uspp_203/covmverfile folder in the OMM server installation
path.

5-16

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 5 Version Loading

Note:
In the /uspp_203/covmverfile path, “203” is the NE ID that is set when the OMM
server is being installed.

2. Log in to the OMM client.

3. Set the IP address that the OMP uses to communicate withe the back end.
a. On the command navigation tree in the Terminal view, choose Configuration
Management > Device Configuration > Global Data Configuration > Set OMP
IP Address to open the SET OMP command interface as shown in the following
figure.

Figure 5-8 SET OMP Command Interface

b. In the OMP IP Address box, type 129.0.254.1, the sub-network mask in the
OMP IP Mask box and select Yes from the Re-establish Link to OMP drop-down
list.

Note:
l When the OMP starts for the first time, the DTF tool automatically assigns an
IP address (129.0.254.1) to the OMP. When you upload version files to the
OMP, you can only use this IP address. After the version files are uploaded,
you should change it to the OMP IP address for the local network.
l In case of inter-office network where there are more than one OMP, the IP
address may conflict. So you should remove all other OMPs, load versions
and change the IP address for one OMP, and then do the same operations
on another OMP.

c. Click to run this command.

4. Confirm that the link between the OMM server and the OMP is established.
a. In the command line in the Terminal view, type the SHOW OMSLINK command.
b. Click to run the command.
c. Check the result information displayed on the Text Result tab, and confirm that
the link status is “ESTABLISHED”.

5-17

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Note:
If the link is not established, do the following.
i. Confirm that the OMM server is configured with an IP address in the 129
section.
ii. Contact ZTE.

5. Upload the version files in the /uspp_203/covmverfile folder on the OMM server
onto the OMP and activate the version files.
a. On the command navigation tree in the Terminal view, choose Version
Management > Version Maintenance > Load Version Package to open the
LOAD PKG command interface as shown in the following figure.

Figure 5-9 LOAD PKG Command Interface

b. Click in the Operation of load box to open the Operation of load dialog box.
Select all the check boxes and click the Enter button. For details about the options,
see the following table.

Table 5-7 Operations for Package Loading

Option Meaning

Load to OMP (LOAD) Uploads the version packages to OMP

Dispatch to Makes the OMP to distribute the version packages to other

MP(DISPATCH) boards.

Active(ACTIVE) Activates the version packages on the OMP.

c. Click to run the command.

d. When a dialog box opens, prompting for your confirmation of loading the
packages, click Yes.

Tip:

The package loading may take a few minutes. When the packages are loaded,
a message notifying success appears on the Text Result tab of the command
interface.

5-18

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 5 Version Loading

6. When the version package loading finishes, do the following to confirm that the
packages are already activated.
a. On the command navigation tree in the Terminal view, choose Version
Management > Version Query > Show Packages Added to OMP to open the
SHOW ADDPKG command interface.
b. Click to run the command.
c. Check the result on the Text Result tab and confirm that the packages are
activated.
7. Do the following to enable the OMP packages.
a. On the command navigation tree in the Terminal view, choose Version
Management > Version Maintenance > Enable Assinged Package to open
the ENABLE APTPKG command interface as shown in the following figure.

Figure 5-10 ENABLE APTPKG Command Interface

b. Click in the Location box to open the Location dialog box. Type the location of
the OMP (including Rack, Shelf, Slot and CPU) and click the Add button and then
the Enter button.
c. Click to run the command.
d. When a dialog box opens, notifying you that this operation may make the blade
power off or reset, click Yes.
8. Check the versions and make sure that the version number is correct.
a. On the command navigation tree in the Terminal view, choose Version
Management > Version Query > Show Running Package to open the SHOW
RUNPKG command interface shown in the following figure.

Figure 5-11 SHOW RUNPKG Command Interface

b. Click in the Location box to open the Location dialog box. Type the location of
the OMP (including Rack, Shelf, Slot and CPU) and click the Add button and then
the Enter button.
c. Click to run the command.
d. Check the result on the Text Result tab and confirm that the version number is
correct.
9. Do the following to transfer the configuration data.
a. On the command navigation tree in the Terminal view, choose Configuration
Management > System Maintenance > Data Transfer > Sync Data(Only Used
By Admin) to open the SYNA command interface shown in the following figure.

5-19

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Figure 5-12 SYNA Command Interface

b. Set the parameters by referring to the following table.

Table 5-8 SYNA Command Interface

Parameter Description

User Name The user to synchronize the tables. Keep empty to use the
default user name (Admin).

Snyc Type The tables to be synchronized. Select All tables(ALL).

Module List List of destination modules. Keep empty to use the default
setting (all modules).

Save When Completed Whether the data is saved after synchronization. Select
Yes (YES).

Distribute when completed Whether to distribute data to other modules. Select

Yes(YES).

Database Type Databases to be synchronized. Select All Databases(YES).

First Sync Flag Whether this is the first time that the data is synchronized.
Select Yes(YES).

c. Click to run the command.

d. When a dialog box opens, prompting for your confirmation, click Yes.

e. Check the result on the Text Result tab and confirm that the data is synchronized.
10. Reboot the blade. For how to reboot a blade that has a CGEL operating system, see
A.4 Restarting CGEL.
– End of Steps –

Follow-Up Action
After the OMP blade is powered on, log in to the OMP blade and confirm that the 18
processes in the service set have started up.

5-20

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 5 Version Loading

Note:
For details about how to check the service set and the information about the service set,
see Appendix B Checking Service Set.

5.2.7 Setting the OMP

Abstract
This topic introduces how to set the OMP after loading versions onto the OMP, including:
l Set OMP bootup mode: After the OMP version are loaded, you need to set the OMP
boot mode to “LOCAL” (booting from the local disk).
l Set OMP IP address: After the OMP version are loaded, you need also to change the
Fabric IP address (129.0.254.1) to the one (192.168.OfficeID.1) for the local network
according to your network plan.

Prerequisites
l OMP version packages are already loaded, and the OMP has started up properly.
l You have logged in to the OMM client.

Steps
1. Do the following to set the OMP bootup mode.
a. On the command navigation tree in the Terminal view, choose Version
Management > Correlation Setting > Set OMP Boot Mode to open the SET
BOOTMODE command interface shown in the following figure.

Figure 5-13 SET BOOTMODE Command Interface

b. Select Master(MSTAER) from the Master or Slave drop-down list and boot from
local(LOCAL) from the Boot mode drop-down list.
c. Click to run the command.

2. Do the following to change the OMP IP address.

a. On the command navigation tree in the Terminal view, choose Configuration
Management > Device Configuration > Global Data Configuration > Set OMP
IP Address to open the SET OMP command interface shown in the following
figure.

5-21

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Figure 5-14 SET OMP Command Interface

b. Type the desired IP address in the OMP IP Address box, the sub-network mask
in the OMP IP Mask box, and select No(NO) from the Re-establish Link to OMP
drop-down list.

Note:
Only when the link is normal can the configuration data be synchronized to the
OMP module. So you should set Re-establish Link to OMP to No(NO).

c. Click to run the command.

d. On the command navigation tree in the Terminal view, choose Configuration
Management > System Maintenance > Data Transfer > Sync Data(Only Used
By Admin) to open the SYNA command interface shown in the following figure.

Figure 5-15 SYNA Command Interface

e. Set the parameters by referring to the following table.

Table 5-9 SYNA Command Interface

Parameter Description

User Name The user to synchronize the tables. Keep empty to use the
default user name (Admin).

Snyc Type The tables to be synchronized. Select All tables(ALL).

Module List List of destination modules. Keep empty to use the default
setting (all modules).

Save When Completed Whether the data is saved after synchronization. Select
Yes (YES).

Distribute when completed Whether to distribute data to other modules. Select

Yes(YES).

5-22

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 5 Version Loading

Parameter Description

Database Type Databases to be synchronized. Select All Databases(YES).

First Sync Flag Whether this is the first time that the data is synchronized.
Select No(NO).

f. Click to run the command.

g. When a dialog box opens, prompting for your confirmation, click Yes.
h. Check the result on the Text Result tab and confirm that the data is synchronized.

i. Reboot the blade. For how to reboot a blade that has a CGEL operating system,
see A.4 Restarting CGEL.
j. After the blade has rebooted up, on the command navigation tree in the Terminal
view, choose Configuration Management > Device Configuration > Global
Data Configuration > Set OMP IP Address to open the SET OMP command
interface shown in the following figure.

Figure 5-16 SET OMP Command Interface

k. Type the desired IP address in the OMP IP Address box, the sub-network mask in
the OMP IP Mask box, and select Yes(YES) from the Re-establish Link to OMP
drop-down list.

l. Click to run the command.

m. In the command line in the Terminal view, type the SHOW OMSLINK command.

n. Click to run the command.

o. Check the result information displayed on the Text Result tab, and confirm that
the link status is “ESTABLISHED”.

Note:
If the link is not established, do the following.

i. Confirm that the OMM server is configured with an IP address in the 192
section.
ii. Contact ZTE.

– End of Steps –

5-23

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

5.2.8 Powering on the Standby OMP Blade

Abstract
This topic describes how to power on the standby OMP blade after the version files are
loaded onto the active OMP blade.

Prerequisites
l The version files are already loaded onto the active OMP blade.
l The blade for the standby OMP is ready.

Steps
1. Plug in the standby OMP blade, and wait for the blade to get version files from the
active OMP and start up the basic processes.
2. Format the hard disk. For the details about how to format the hard disk, see 5.2.5
Formatting a Hard Disk.
3. Reboot the blade and wait for the blade to synchronize the data from the active OMP.

– End of Steps –

5.3 Version Loading for other Modules

5.3.1 Checking Module and Unit Configuration
Abstract
Before loading versions on other modules, you should confirm according to your
networking plan that all necessary modules and units are already configured.
This topic describes how to check the configuration of modules and units.

Prerequisites
l Physical data configuration is complete. For details about physical data configuration,
see the Basic Data Configuration Guide.
l You have logged in to the OMM client.

Steps
1. On the command navigation tree in the Terminal view, choose Configuration
Management > Device Configuration > Physical Configuration > Module
Configuration > Show Module Configuration to open the SHOW MODULE
command interface.
2. Click to run the command and show all the modules already configured.

5-24

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 5 Version Loading

3. On the Text Result tab, check whether all necessary modules are configured. If not,
configured the required modules.
4. On the command navigation tree in the Terminal view, choose Configuration
Management > Device Configuration > Physical Configuration > Unit
Configuration > Show Unit Configuration to open the SHOW UNIT command
interface.
5. Click to run the command and show all the units already configured.
6. On the Text Result tab, check whether all necessary units are configured. If not,
configured the required modules.
– End of Steps –

5.3.2 Loading SWBB1 Versions

Abstract
This topic describes how to loading the versions for an SWBB1 blade.

Prerequisites
l The OMP versions are loaded, and the SWBB1 versions are already uploaded onto
the OMP.
l The SWBB1 blade in Slot 8 is removed.
l The module and unit configuration is checked, and all necessary modules and units
are configured.
l You have logged in to the OMM client.

Context
The Fabric communication is normal as long as the SWBB1 blade is plugged in. But the
Base communication can be normal only after the versions are loaded.
You should load the versions for the active SWBB1 blade (in Slot 7) first and then for the
standby SWBB1 blade (in Slot 8).
You can load the versions for other modules only when you have loaded the versions for
the SWBB1 blades and the SWBB1 blades are working properly.

Steps
1. Do the following to enable the SWBB1 versions.

a. On the command navigation tree in the Terminal view, choose Version

Management > Version Maintenance > Enable Assinged Package to open
the ENABLE APTPKG command interface as shown in the following figure.

5-25

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Figure 5-17 ENABLE APTPKG Command Interface

b. Click in the Location box to open the Location dialog box. Type the location of
the SWBB1 blade (including Rack, Shelf, Slot and CPU) and click the Add button
and then the Enter button.

Tip:
The CPU number of an SWBB1 blade is the logic CPU number that the system
assigns when the unit corresponding to the SWBB1 blade is configured. You can
run the SHOW UNIT to view the CPU number.

c. Click to run the command.

d. When a dialog box opens, notifying you that this operation may make the blade
power off or reset, click Yes.
2. Check the versions and make sure that the version number is correct.
a. On the command navigation tree in the Terminal view, choose Version
Management > Version Query > Show Running Package to open the SHOW
RUNPKG command interface shown in the following figure.

Figure 5-18 SHOW RUNPKG Command Interface

b. Click in the Location box to open the Location dialog box. Type the location of
the SWBB1 blade (including Rack, Shelf, Slot and CPU) and click the Add button
and then the Enter button.
c. Click to run the command.
d. Check the result on the Text Result tab and confirm that the version number is
correct.

3. After the SWBB1 blade is powered on, log on to the SWBB1 blade and confirm that
the processes in the service set have started up.

Note:

For details about how to check the service set and the information about the service
set, see Appendix B Checking Service Set.

5-26

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 5 Version Loading

4. Plug the standby SWBB1 blade in Slot 8, and wait for the blade to start up and to
synchronize the data from the active SWBB1.
– End of Steps –

5.3.3 Loading Versions for a Module or Unit over a Non-CGSL

Operating System
Abstract
There are no special requirements for the sequence of loading versions for modules and
units other than OMP and SWBB1. The procedure to load the versions for such modules
and units are similar.
This topic describes the general procedure to load the versions for a module or unit.

Note:

You should load the versions for all modules and units other than OMP and SWBB1
according to your hardware configuration.

Prerequisites
l The OMP versions are loaded, and the versions for the modules and units are already
uploaded onto the OMP.
l The module and unit configuration is checked, and all necessary modules and units
are configured.
l You have logged in to the OMM client.

Steps
1. Do the following to enable the versions.
a. On the command navigation tree in the Terminal view, choose Version
Management > Version Maintenance > Enable Assinged Package to open
the ENABLE APTPKG command interface as shown in the following figure.

Figure 5-19 ENABLE APTPKG Command Interface

b. Click in the Location box to open the Location dialog box. Type the location of
the module or unit (including Rack, Shelf, Slot and CPU) and click the Add button
and then the Enter button.

5-27

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Tip:
The CPU number of a unit is the logic CPU number that the system assigns when
the unit is configured. You can run the SHOW UNIT to view the CPU number.

c. Click to run the command.

d. When a dialog box opens, notifying you that this operation may make the blade
power off or reset, click Yes.
2. Check the versions and make sure that the version number is correct.
a. On the command navigation tree in the Terminal view, choose Version
Management > Version Query > Show Running Package to open the SHOW
RUNPKG command interface shown in the following figure.

Figure 5-20 SHOW RUNPKG Command Interface

b. Click in the Location box to open the Location dialog box. Type the location of
the blade (including Rack, Shelf, Slot and CPU) and click the Add button and
then the Enter button.
c. Click to run the command.
d. Check the result on the Text Result tab and confirm that the version number is
correct.
3. After the blade of the module or unit is powered on again, log in to the blade and
confirm that the processes in the service set have started up.

Note:
For details about how to check the service set and the information about the service
set, see Appendix B Checking Service Set.

– End of Steps –

Follow-Up Action
Configure the modules and units. See the Data Configuration Guide manual for details.
For DIBO modules and interface processor modules, some configuration files must also
be set and uploaded. See the following sections for details.
l 5.4 DBIO Configuration

5-28

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 5 Version Loading

l 5.5 Interface Processor Configuration

5.3.4 Loading Module Versions on the CGSL Operating System

Abstract
This topic describes how to load the versions for the DST module over the CGSL operating
system.

Prerequisites
l The operating system, the cluster software and the database are already installed on
the DST. Contact ZTE for details.
l The OMP versions are loaded, and the CGSL versions are already uploaded onto the
OMP.
l You have already transferred (in binary mode) the package for installing the BOOT
simulator into the / directory of the DST blade. The version number of your file may
the same as the following or may be different.
à For DPBA2: SBCO-CGSL-X86_64-NULL-REL_2_2_21.rpm
à For DPBB1: SBCJ-CGSL-X86_64-NULL-REL_2_2_9.rpm
l The standby DST blade is removed.

Steps
1. Log on to the DST blade as user root.
2. In the Terminal window, run the following commands to install the BOOT simulator
installation package.

[root@zte01 home]# cd /
[root@zte01 /]# rpm -ivh --force SBCO-CGSL-X86_64-NULL-REL_2_2_21.rpm

Tip:
You should choose the proper BOOT simulator installation package according to the
model of your DST blade.

3. Run the following commands to set environment variables.

[root@wdst home]# cd /etc

[root@wdst etc]# touch division.profile /*Create the file*/
[root@wdst etc]# cat /oracle/.bash_profile>>division.profile
/*Write environment variables into the file.*/

5-29

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Note:
When the BOOT simulator is starting up, it needs the Oracle environment variables.
If the Oracle environment variables are incorrect, the DST may fail to boot up.

4. Modify the /etc/rc.d/rc.local file by removing the “#” before the zboot to enable
this line.
5. Run the reboot command to reboot the blade.
6. Log on to the DST blade as user root.
7. In the Terminal window, run the following commands to view the status of the Oracle
listener.

[root@zte01 ~]# su - oracle /*Change to user oracle.*/

-bash-3.2$ lsnrctl status /*View the status of the Oracle listener.*/

8. Check whether the Oracle listener has started up and then do accordingly, as shown
in the following.
l If the output information is as follows, the Oracle listener has started up. Go to
Step 10.

LSNRCTL for Linux: Version 10.2.0.4.0 - Production on 03-SEP-2010 15:36:04

Copyright (c) 1991, 2007, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=129.0.210.210)
(PORT=1521)))
STATUS of the LISTENER
……
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=129.0.210.210)(PORT=1521)))
Services Summary...
Service "hlr" has 1 instance(s). /*The Oracle listener has started up.*/
Instance "hlr", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully

l If the output information is as follows, the Oracle listener has not started up. Go
to Step 9.

LSNRCTL for Linux: Version 10.2.0.4.0 - Production on 03-SEP-2010 15:39:49

Copyright (c) 1991, 2007, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=129.0.210.210)
(PORT=1521)))
TNS-12541: TNS:no listener /*The Oracle listener has not started up.*/
TNS-12560: TNS:protocol adapter error

5-30

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 5 Version Loading

9. Do the following to start the Oracle listener.

-bash-3.2$ lsnrctl start /*Start the Oracle listener.*/
LSNRCTL for Linux: Version 10.2.0.4.0 - Production on 03-SEP-2010 15:47:05
Copyright (c) 1991, 2007, Oracle. All rights reserved.
Starting /oracle/product/10g/bin/tnslsnr: please wait...
……
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=129.0.210.210)(PORT=1521)))
Services Summary...
Service "hlr" has 1 instance(s).
Instance "hlr", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully

10. Run the following to enter SQL.

-bash-3.2$ sqlplus "/as sysdba" /*Enter SQL as user sysdba.*/
SQL*Plus: Release 10.2.0.4.0 - Production on Fri Sep 3 16:00:25 2010
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
Connected to an idle instance.
SQL>

11. Run the startup command to start the instance.

l If the output information is as follows, the instance has started up.
ORACLE instance started.
Total System Global Area 3690987520 bytes
Fixed Size 2088280 bytes
Variable Size 452985512 bytes
Database Buffers 3221225472 bytes
Redo Buffers 14688256 bytes
Database mounted.
Database opened.

l If the output information is as follows, this command failed because the instance
is already running.
ORA-01081: cannot start already-running ORACLE - shut it down first

12. Log in to the OMM client.

13. Do the following to enable the versions.
a. On the command navigation tree in the Terminal view, choose Version
Management > Version Maintenance > Enable Assinged Package to open
the ENABLE APTPKG command interface as shown in the following figure.

Figure 5-21 ENABLE APTPKG Command Interface

5-31

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

b. Click in the Location box to open the Location dialog box. Type the location of
the DST blade (including Rack, Shelf, Slot and CPU) and click the Add button
and then the Enter button.

Tip:
As in the data configuration, the module type of the DST module is “SAVE”.

c. Click to run the command.

d. When a dialog box opens, notifying you that this operation may make the blade
power off or reset, click Yes.
14. Do the following to check the versions and make sure that the version number is
correct.
a. On the command navigation tree in the Terminal view, choose Version
Management > Version Query > Show Running Package to open the SHOW
RUNPKG command interface shown in the following figure.

Figure 5-22 SHOW RUNPKG Command Interface

b. Click in the Location box to open the Location dialog box. Type the location of
the DST blade (including Rack, Shelf, Slot and CPU) and click the Add button
and then the Enter button.

c. Click to run the command.

d. Check the result on the Text Result tab and confirm that the version number is
correct.
15. After the blade of the DST blade is powered on again, log in to the blade and confirm
that the processes in the service set have started up.

Note:
For details about how to check the service set and the information about the service
set, see Appendix B Checking Service Set.

16. Plug the standby DST blade in, and wait for the blade to start up and to synchronize
the data from the active DST blade.
– End of Steps –

5-32

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 5 Version Loading

5.4 DBIO Configuration

5.4.1 Configuring a DBIO Module
Abstract
This topic describes how to configure a DBIO module.

Prerequisites
l The DBIO versions are loaded.
l The configuration files (originally in the zxver_v4\front\appconfig\provisio
n\dbio\config folder in the ZXUN USPP software package) are copied onto the
debugging PC.
l The network connection between the blade for the DBIO and the debugging PC is
normal.

Steps
1. On the debugging PC, log on to the DBIO blade as user root (default password: root)
with a remote control tool, and then change to user root.
2. Run the following command to create the folder for DBIO configuration files.

# mkdir /IDE0/ZTE_HLR/hlrserver_203_139/config –p

Note:
This topic assumes that the office ID is 203 and that the module number is 139. You
should change them according to your actual network solution.

3. With an FTP tool, upload the DBIO configuration files that are saved on the debugging
PC to into the folder created at the previous step.
4. With the remote control tool, run the dos2unix
/IDE0/ZTE_HLR/hlrserver_203_139/config/* command to convert all the
files in the folder into the Unix file format.
5. Reboot the DBIO blade.
– End of Steps –

5.4.2 Checking DBIO Bootup

Abstract
This topic describes how to check the bootup result of a DBIO module.

5-33

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Prerequisites
l The DBIO is configured.
l The network connection between the DBIO blade and the debugging PC is normal.

Steps
1. Log on to the DBIO blade and confirm that the processes in the service set have started
up.

Note:
For details about how to check the service set and the information about the service
set, see Appendix B Checking Service Set.

2. Run the sh 25 command to enter the DBIO process mode.

Here, 25 refers to the process number of the DBIO process. A DBIO process name
begins with “SBCO_DBIO” or “SBCJ_DBIO”, as you can see from the result of Step 1.
3. Run the SCSShowMcaInfo(1) command to check the status of each DBIO thread. The
DBIO has successfully started up if every DBIO thread is in Power On Succ status.
– End of Steps –

5.5 Interface Processor Configuration

5.5.1 Configuring an Interface Processor
Abstract
This topic describes how to configure an interface processor module.

Prerequisites
l The interface processor versions are loaded.
l The configuration files (originally in the zxver_v4\front\appconfig\provisio
n\hlrmi\config folder in the ZXUN USPP software package) are copied onto the
debugging PC .
l The network connection between the blade for the interface processor and the
debugging PC is normal.

Steps
1. On the debugging PC, open the config folder of the configuration files.

5-34

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 5 Version Loading

2. Modify the hlrinter.ini file to set the area code (for example, 25), office ID (for
example, 203) and module number (for example, 139) of the DBIO module, as shown
in the following.

...
;3GDBIO Defalt Bureau Number
DefaultBureau=203 /*Office ID*/

;3GDBIO Defalt Area Number(1-65535)

DefaultAera=25 /*Area code*/

;3GDBIO Defalt Module Number

DefaultModule=139 /*DBIO module number*/

...
3. Modify the s10plattcpout.ini file to set the links for the interface processor (as
the server) to interwork with the BOSS systems.
The following takes a link to a local BOSS (for example, node ID: 1) in the accounting
network and a link to a remote BOSS (for example, node ID: 2) in the accounting
network for example.

......
[localinfo]
local1=ip(192.168.203.2), localport(3148)
/*IP address and port used to communicate with the local BOSS*/
local2=ip(10.20.203.2), localport(3148)
/*IP address and port used to communicate with the remote BOSS*/

[remoteinfo]

remote1=nodeid(1), /*Node No. of the local BOSS*/

remoteip(192.168.203.252), /*IP address of the local BOSS*/
connect(S), /* Linking mode: S (listening)*/
linktype(L), /* Link type: L (long link)*/
hearttype(0), /* Heartbeat type: 0 (do not response)*/
filerecord(1) /* Whether to write log: 1 (Yes)*/

remote2=nodeid(2), /*Node No. of the remote BOSS*/

remoteip(10.20.203.252), /*IP address of the remote BOSS*/
connect(S), /* Linking mode: S (listening)*/
linktype(L), /* Link type: L (long link)*/
hearttype(0), /* Heartbeat type: 0 (do not response)*/
filerecord(1) /* Whether to write log: 1 (Yes)*/

4. On the debugging PC, log on to the interface processor blade as user root (default
password: root) with a remote control tool, and then change to user root.

5-35

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

5. Run the following command to create the folders for DBIO configuration files.

# mkdir /IDE0/ZTE_HLR/hlrmi_203_139/config –p
# mkdir /IDE0/ZTE_HLR/hlrmi_203_139/trace –p

6. With an FTP tool, upload the interface processor configuration files that are saved on
the debugging PC to into the config folder created at the previous step.
7. With the remote control tool, run the dos2unix
/IDE0/ZTE_HLR/hlrmi_203_139/config/* command to convert all the
files in the folder into the Unix file format.
8. Reboot the interface processor blade.
– End of Steps –

5.5.2 Checking Interface Processor Bootup

Abstract
This topic describes how to check the bootup result of an interface processor module.

Prerequisites
l The interface processor is configured.
l The network connection between the blade for the interface processor and the
debugging PC is normal.

Steps
1. Log on to the blade for the interface processor and confirm that the processes in the
service set have started up.

Note:
For details about how to check the service set and the information about the service
set, see Appendix B Checking Service Set.

2. Run the sh 51 command to enter the DBIO process mode.

Here, 51 refers to the process number of the interface processor process. The process
name of an interface processor begins with “SBCO_HLRMI” or “SBCJ_HLRMI”, as you
can see from the result of Step 1.
3. Run the SCSShowMcaInfo(1) command to check the status of each interface processor
thread. The interface processor has successfully started up if every thread is in Power
On Succ status.
– End of Steps –

5-36

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 6
HSM Installation
Table of Contents
Introduction to HSM....................................................................................................6-1
HSM Software Installation Flow ..................................................................................6-3
Installing LunaPCI ......................................................................................................6-3
HSM Initial Settings ....................................................................................................6-6
Configuring an HSM Client .......................................................................................6-11
HSM Key Backup and Restoration ...........................................................................6-13
HSMAPP Installation and Configuration ...................................................................6-16

6.1 Introduction to HSM

6.1.1 HSM Overview
Functions
An HSM is a hardware device of ZXUN USPP that implements sensitive data encryption
and decryption for the purpose of protecting the keys and accelerating the sensitive data
protection.
l The SMP modules of the FE subsystem and the DBIO modules of the PROVISION
subsystems send requests for data encryption and decryption to HSM PCI through
the encryption and decryption module (HSMAPP).
l The encrypted keys are saved in the HSMAPP module. During an encryption or
decryption process, only the serial number of a key is invoked, and therefore the
contents of the key is unknown and thus the sensitive data is protected against getting
the plain text from the cipher text.

Composition
l In hardware, an HSM consists of an HSM PCI, USB Keys and a PED key board:
à HSM PCI card: for key management, and data encryption and decryption.
à USB Keys: for user verification. The HSM supports three types of users: HSM
Admin, Domain and Partition Owner. Each user uses at least one USB Key.
à PED keyboard: connected to the HSM PCI card, for initialization and password
input.
l In software, an HSM consists of LunaPCI, HSM Client and the encryption and
decryption module (HSMAPP):

6-1

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

à LunaPCI: installed on the PC with the HSM PCI, for updating the driver of HSM
PCI and generating the HSM configuration tool (Lunacm).
à HSM Client: running on the PC with the HSM PCI, for generating serial numbers
of encrypted keys.
à Encryption and decryption module (HSMAPP): running on the PC with the HSM
PCI, for handling the encryption/decryption requests sent by FEs or DBIOs.

6.1.2 HSM Installation and Configuration Requirements

HSM Hardware Requirements
The following table shows the requirements for the hardware environment of HSM.

Table 6-1 HSM Hardware Requirements

Hardware Configuration

Model Common PC

CPU Main frequency 1.8 GHz or above

RAM 1G or above

Hard disk One 80 G hard disk

PCI slot 1

CD-ROM drive One, 16X or above

Mouse One each

Keyboard

Monitor

HSM Software Requirements

The following table shows the requirement for the software environment of HSM.

Table 6-2 HSM Software Requirement

Software Configuration

Operating system EmbSys CGS Linux V3.02.00.p1 (32-bit) or later

6-2

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 6 HSM Installation

6.2 HSM Software Installation Flow

Caution!
Before installing the HSM, you should log in to the EMS and check the License
Management to confirm that your ZXUN USPP system supports HSM.

The software installation flow of an HSM is shown in the following table.

Table 6-3 HSM Software Installation Flow

Step Description

1 Install the CGSL operating system

2 Install LunaPCI

3 Initialize the HSM

4 Configure HSM client

5 Back up and restore HSM keys

6 Install HSMAPP

Note:
Installing CGSL on a PC is similar to that on a blade. You can refer to Chapter 8 CGSL
Operating System Installation for details.

6.3 Installing LunaPCI

Abstract
This topic describes how to install LunaPCI (an attached program of HSM).

LunaPCI is used to update the driver of HSM PCI and to generate the HSM configuration
tool (that is, Lunacm).

Prerequisites
l The HSM PCI card is inserted in the PCI slot of the PC.
l The LunaPCI installation CD (that is, the attached CD of the HSM) is placed in the CD
drive.
l The CGSL operating system (32-bit) is installed.
l You have logged in to the PC as user root.

6-3

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Steps
1. In the Terminal window, carry out the cd /media/610075-005_RC2/linux/32
command to enter the folder of CGSL installation files.
2. Carry out the ls command to list all the files in this folder, and then check whether the
files are as follows.
l Yes: Proceed with the next step.
l No: The CD is not correct. Contact ZTE and ask for a correct CD.

[root@hn_hsm240 32]# ls
ckdemo-3.0.0-8.i386.rpm libshim-3.0.0-8.i386.rpm
cklog-3.0.0-8.i386.rpm lunacm-3.0.0-8.i386.rpm
ckSample-3.0.0-8.i386.rpm lunacmu-3.0.0-8.i386.rpm
configurator-3.0.0-8.i386.rpm lunadiag-3.0.0-8.i386.rpm
install.sh multitoken-3.0.0-8.i386.rpm
javasp uninstall.sh
libcryptoki-3.0.0-8.i386.rpm vkd-1.0.9-1.src.rpm

3. Run the sh install.sh command, as shown in the following.

[root@hn_hsm240 32]# sh install.sh

IMPORTANT: The terms and conditions of use outlined in the software
license agreement (Document #800230-003) shipped with the product
("License") constitute a legal agreement between you and SafeNet Inc.
Incorporated. Please read the License contained in the packaging of this
product in its entirety before before installing this product.
5．
Do you agree to the License contained in the product packaging?
If you select 'yes' or 'y' you agree to be bound by all the terms
and conditions set out in the License.
If you select 'no' or 'n', this product will not be installed.(y/n)

4. Type y and press the Enter key to start installation, as shown in the following.

6-4

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 6 HSM Installation

PKG_LST- = rpm -q --quiet

Checking for /etc/Chrystoki.conf.rpmsave
Using new /etc/Chrystoki.conf
Installed libcryptoki-3.0.0-8.i386.rpm
Installed ckdemo-3.0.0-8.i386.rpm
Installed multitoken-3.0.0-8.i386.rpm
Installed lunadiag-3.0.0-8.i386.rpm
Installed configurator-3.0.0-8.i386.rpm
Installed lunacmu-3.0.0-8.i386.rpm
Installed cklog-3.0.0-8.i386.rpm
Installed lunacm-3.0.0-8.i386.rpm
Installed ckSample-3.0.0-8.i386.rpm
Installed libshim-3.0.0-8.i386.rpm

Build driver source RPM ... Skipped

NOTE: the driver source RPM is built separately as follows:

# cd /usr/lunapci/pcidriver
# rpmbuild --rebuild vkd-1.0.9-1.src.rpm
# rpm -i ./i386/vkd-1.0.9-1.i386.rpm
Would you like to install the Luna JSP for Luna PCI? (y/n)

5. Type y and press the Enter key to proceed with the installation of Luna JSP, as shown
in the following.

Installed lunajsp-3.0.0-8.i386.rpm
Installed lunajmt-3.0.0-8.i386.rpm
Installed javaSAMP-3.0.0-8.i386.rpm
7．
Installation of the Luna JSP for Luna PCI - Release 3.0 successful.

Installation of the Luna PCI Software - Release 3.0 successful.

6. Carry out the following commands to enter the installation path and build the driver
package (*.rpm).

[root@hn_hsm240 32]# cd /usr/lunapci/pcidrive

[root@hn_hsm240 pcidrive]# rpmbuild --rebuild vkd-1.0.9-1.src.rpm

7. Carry out the following command to install the driver.

[root@hn_hsm240 pcidrive]#rpm -i ./i386/vkd-1.0.9-1.i386.rpm

– End of Steps –

6-5

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

6.4 HSM Initial Settings

6.4.1 Introduction to HSM Initialization
Operations
After the LunaPCI is installed, you should do the following HSM initial settings:
l Initializing HSM: Before the HSM is put into practical use, you must initialize the HSM
to clear the data in it.
l Creating HSM partitions: HSM supports multiple partitions. With multiple partitions,
an HSM can:
à Act as if there are multiple physical HSMs.
à Serve multiple applications.
à Provide an independent management mechanism for each partition.
l Setting the policy for HSM keys: Make the HSM buffer user passwords (the passwords
that the HSM client uses to generate keys), so that users do not have to enter their
passwords with the PED keyboard every time when they access the HSM.
à With the HSM key policy, a user needs to enter the password for the first time
when logging in. The user does not need to enter the password when logging in
again.
à The buffered passwords are lost after the HSM reboots. In this case, a user needs
to enter the password when logging in for the first time after the HSM reboots.

Users
During the HSM initial setting process, three types of users may be involved:
l SO/HSM Admin: super administrator, having the permission to initialize the HSM.
l Domain: domain operator, having the permission to back up and restore serial
numbers of keys. To restore key serial numbers, you must use the same user name
as has been used to back up the key serial numbers.
l USER/Partition Owner: partition user, having the permission to create a partition and
to set the password policy.
The three types of users use three types of USB keys. Every type of users has at least
one USB key. When you are logging in as a user of a type, you must insert the USB key
for this type of user in the PED keyboard and enter the password.
Originally, the USB keys of the three types users are all blank.

6.4.2 Initializing an HSM

Abstract
This topic describes how to initialize an HSM.

6-6

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 6 HSM Installation

Note:
To help you to know the information displayed and entered on the PC from the information
displayed and entered on the PED keyboard (the PED keyboard has a display), information
displayed and entered on the PED keyboard is italicized.

Prerequisites
l The LunaPCI is installed.
l You have logged in to the PC of the HSM as user root.
l The USB Key is ready.
l The PED keyboard is connected to the PC.
l A label with user identity on it is ready.

Steps
1. Start the configuration tool (Lunacm)
a. In the Terminal window, carry out the cd /usr/lunapci command to enter the
installation path of LunaPCI.

b. Carry out the ./lunacm command to start Lunacm, as shown in the following.

Note:
When you start Lunacm, if the system prompts that the libstdc++-libc6.2-2
.so.3 library file is missing, contact ZTE to get the compat-libstdc++-296-
2.96-138.i386.rpm patch for the operating system and then install the patch
as follows.
i. Upload (in binary mode) the file to the PC with an FTP tool.
ii. In the Terminal window, enter the folder of the file, and then carry out the
rpm -ivh compat-libstdc++-296-2.96-138.i386.rpm command to
install the patch.

6-7

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

[root@hn_hsm240 lunapci]# ./lunacm

LunaCM V2.3.3 - Copyright (c) 2006 SafeNet, Inc.
Available HSM's:
Slot Id -> 1
HSM Label -> no label
HSM Serial Number -> 500989
HSM Model -> K5Base
HSM Firmware Version -> 4.7.1
HSM Configuration -> Luna PCI (PW) Undefined Mode / Uninitialized
lunacm:>

2. Initialize the HSM.

a. Carry out the hsm init -l mypci command to start the initialization, as shown
in the following.

lunacm:> hsm init -l mypci

You are about to initialize the HSM that is in the factory reset (zeroized)
state.
Are you sure you wish to continue?
Type 'proceed' to continue, or 'quit' to quit now ->

b. Enter proceed. The system prompts you to note the PED keyboard for the
following output information.

Insert a SO/HSM Admin PED Key.Press ENTER.

c. Insert the USB key of an SO/HSM Admin user into the PED keyboard and then
press Enter to proceed, as shown in the following.

This PED Key is blank. Overwrite? YES/NO YES /*Press the YES key.*/
Enter new PED PIN: /*Set the password for the user.*/
Confirm new PED PIN:
Copy this PED Key,YES/NO NO
/*If you want to duplicate the USB keys for multiple SO/HSM Admin users, */
/*press the YES key.*/
/*In this instance, the NO key is pressed.*/
Insert a Domain PED Key. Press ENTER.

Caution!
Remember and do not forget the password you have set for the SO/HSM Admin
user.

d. Remove the USB Key, and stick a proper user label on it.

6-8

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 6 HSM Installation

e. Insert the USB key of a Domain user into the PED keyboard and press the Enter
key to confirm. The system detects the USB key and output accordingly as shown
in the following.
l If the USB key is blank: This PED Key is blank. Overwrite?
YES/NO
l If the USB key is not blank: This PED Key has a valid Identity
for Domain PED Key.Reuse Id? YES/NO
f. Press the YES key to confirm. When the processing is complete, the following
information appears on the display of the PED keyboard.

Copy this PED Key,YES/NO

g. If you want to duplicate the USB keys for multiple Domain users, press the YES
key. In this instance, the NO key is pressed. The following information appears in
the Terminal window on the PC, notifying you of success.

Command Result : No Error

h. Remove the USB Key, and stick a proper user label on it.
3. Log in as an SO/HSM Admin user.
a. In the Lunacm configuration tool in the Terminal window, carry out the hsm login
command to log in as an SO/HSM Admin user. The system prompts you to note
the PED keyboard for the following output information.

Insert a SO/HSM Admin PED Key. Press ENTER.

b. Insert the USB key of an SO/HSM Admin user into the key board and then press
Enter. The following information appears on the display of the PED keyboard.

Enter PED PIN:

c. Type the password of the SO/HSM Admin user, and then press the Enter key to
confirm. The following information appears in the Terminal window on the PC,
notifying you of success.

Command Result : No Error

4. Create HSM partitions.

a. In the Lunacm configuration tool in the Terminal window, carry out the partition
create command to create partitions. The system prompts you to note the PED
keyboard for the following output information.

Insert a USER/Partition Owner PED Key.Press ENTER.

b. Insert the USB key of a USER/Partition Owner into the key board and then press
Enter to proceed, as shown in the following.

6-9

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

This PED Key is blank. Overwrite? YEA/NO YES /*Press the YES key.*/
Enter new PED PIN: /*Set the password for the user.*/
Confirm new PED PIN:
Copy this PED Key,YES/NO NO
/*If you want to duplicate the USB keys for multiple USER/Partition Owner */
/*users, press the YES key.*/
/*In this instance, the NO key is pressed.*/
Command Result : No Error /*The Terminal window on the PC
notifies you of success.*/

Caution!
Remember and do not forget the password you have set for the USER/Partition
Owner user.

c. Remove the USB Key, and stick a proper user label on it.
5. Set the HSM key policy.
a. In the Lunacm configuration tool in the Terminal window, carry out the following
command to set the key policy.

unacm:> partition changePolicy -policy 22 value 1

Command Result : No Error
lunacm:>

b. Carry out the partition login command to log in as a USER/Partition Owner

user. The system prompts you to note the PED keyboard for the following output
information.

Insert a USER/Partition Owner PED Key.Press ENTER.

c. Insert the USB key of a USER/Partition Owner user into the key board and
then press Enter. The following information appears on the display of the PED
keyboard.

Enter PED PIN:

d. Type the password of the USER/Partition Owner user, and then press the Enter
key to confirm. The following information appears in the Terminal window on the
PC, notifying you of success.

Command Result : No Error

e. In the Lunacm configuration tool in the Terminal window, carry out the partition
createChallenge to create a password. (This password is the one that the
HSM client uses to generate keys.) After the system confirm that you have logged
in as a USER/Partition Owner user, the following information appears on the PED
key board.

6-10

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 6 HSM Installation

LOGIN SECRET VALUE...

PLY4-KsRE-Xpfa-q5EW /*Password*/
Please write it down Press ENTER.

f. Note down the password and then press ENTER to confirm. The following
information appears in the Terminal window on the PC, notifying you of success.
Command Result : No Error
g. In the Lunacm configuration tool in the Terminal window, carry out the partition
changepw -newpw password -oldpw PLY4-KsRE-Xpfa-q5EW command
to change password. (In the command, “password” refers to the new password
and “PLY4-KsRE-Xpfa-q5EW” is the password generated by the system.) After
the system confirm that you have logged in as a USER/Partition Owner user, the
following information appears on the PED key board.
Insert a USER/Partition Owner PED Key. Press ENTER.

h. Insert the USB key of a USER/Partition Owner user into the key board and
then press Enter. The following information appears on the display of the PED
keyboard.
Enter PED PIN:

a. Type the password of the USER/Partition Owner user, and then press the Enter
key to confirm. The following information appears in the Terminal window on the
PC, notifying you of success.
Command Result : No Error

– End of Steps –

6.5 Configuring an HSM Client

Abstract
This topic describes how to start an HSM client and how to generate keys with the HSM
client.

Prerequisites
l You have uploaded (in binary mode) the entire folder (/hlr) of HSM client files into
any folder (for example, /hsm) on the PC for the HSM with an FTP tool.
l You have logged in to the PC as user root.
l The HSM initialization is complete, and you know the password that is set during key
policy setting.

Context
HSM clients generate HSM keys. The keys have the following features:
l Every time when the HSM client generates a key, the serial number of the key
increments by one.

6-11

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

l Users can only query the serial number of a key and can not see the contents of the
key.

Steps
1. Enter the folder of the HSM client, and start the HSM client as shown in the following.

[root@hn_hsm240 ~]# cd /hsm/hlr /*Enter the folder.*/

[root@hn_hsm240 hlr]# ./HSMClient /*Start the HSM client.*/

2. Generates a key, as shown in the following.

Please input the user login password: password

/*Enter the password that is set during key policy setting.*/
HSM init success!
FUNCTIONS
(1) Generate Key (2) Display Key
(3) File Encry (4) File Decry
(5) Re-encrypting for new hsm key
(0) Quit
2． Enter your choice:1 /*Enter 1.*/
Select type of key to generate:
(1) DES (2) DES3 (3) AES3
3． Enter your choice:2 /*Select according to your needs.*/
Generate the new key success ! the keyid is 3

3. If necessary, repeat Step 2 to generate more keys.

4. Return to the FUNCTIONS list and show the serial numbers of the keys already
generated, as shown in the following.

FUNCTIONS
(1) Generate Key (2) Display Key
(3) File Encry (4) File Decry
(5) Re-encrypting for new hsm key
(0) Quit
4． Enter your choice:2
Select type of key to display:
(1) DES (2) DES3 (3) AES3
5． Enter your choice:2 /*Select according to your needs.*/
The KeyID list:
1
2
3

6-12

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 6 HSM Installation

Tip:
To make the keys available for encrypting subscriber authentication data, the keys
should be configured on the NMS.

– End of Steps –

6.6 HSM Key Backup and Restoration

6.6.1 Introduction to the Backup and Restoration of Keys
The backup and restoration of HSM keys refer to backing up and restoring the keys that
are created by an HSM client.

No matter the ZXUN USPP uses a single office or a distributed network, the keys stored
in each HSM must be the same. If the keys are not the same, subscriber authentication
may fail. You can use the backup and restoration function to ensure that the keys on each
HSM are the same.
When you are restoring the keys, you must make sure that the keys are for the same
domain.

6.6.2 Backing up Keys

Abstract
This topic describes how to back up the keys saved on an HSM.

Prerequisites
l The HSM client is configured.
l You have logged in to the PC of the HSM.

Steps
1. Start the Lunacm configuration tool.
a. In the Terminal window, carry out the cd /usr/lunapci command to enter the
installation path of LunaPCI.
b. Carry out the ./lunacm command to start Lunacm, as shown in the following.

6-13

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

[root@hn_hsm240 lunapci]# ./lunacm

LunaCM V2.3.3 - Copyright (c) 2006 SafeNet, Inc.
Available HSM's:
Slot Id -> 1
HSM Label -> no label
HSM Serial Number -> 500989
HSM Model -> K5Base
HSM Firmware Version -> 4.7.1
HSM Configuration -> Luna PCI (PW) Undefined Mode / Uninitialized
lunacm:>

2. Carry out the partition backup -objects 0 -fi /tmp/bakfile command to back up the keys
(in the command, /tmp/bakfile is the folder for saving the backup keys), as shown in
the following.

lunacm:>partition backup -objects 0 -fi /tmp/bakfile

You have not specified an authorization password. The default SIM Form
CKA_SIM_PORTABLE_NO_AUTHORIZATION will be used.
Are you sure you wish to continue?
Type 'proceed' to continue, or 'quit' to quit now ->proceed
/*Type proceed and press Enter to proceed.*/
All objects will be backed up.
The backed up objects have been written to the file /tmp/bakfile.
Command Result : No Error /*Operation succeeded.*/

– End of Steps –

Result
The backup keys exist in the /tmp/bakfile folder.

Follow-Up Action
To make the keys the same on each HSM, you can copy the backup keys on to the HSM
where the keys are to be restored.

6.6.3 Restoring Keys

Abstract
This topic describes how to restore the keys saved on an HSM.

Prerequisites
l You have logged in to the PC of the HSM.
l The backup keys exist on the HSM.

6-14

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 6 HSM Installation

Steps
1. Start the Lunacm configuration tool.

a. In the Terminal window, carry out the cd /usr/lunapci command to enter the
installation path of LunaPCI.
b. Carry out the ./lunacm command to start Lunacm, as shown in the following.

[root@hn_hsm240 lunapci]# ./lunacm

LunaCM V2.3.3 - Copyright (c) 2006 SafeNet, Inc.
Available HSM's:
Slot Id -> 1
HSM Label -> no label
HSM Serial Number -> 500989
HSM Model -> K5Base
HSM Firmware Version -> 4.7.1
HSM Configuration -> Luna PCI (PW) Undefined Mode / Uninitialized
lunacm:>

2. Carry out the partition restore -fi /tmp/bakfile to restore the keys (in the command,
/tmp/bakfile is the folder saving the backup keys), as shown in the following.

lunacm:>partition restore -fi /tmp/bakfile

Restored Object Count: 15 /*Quantity of keys to be restored*/
Restored Objects:
Object Handle: 6 (0x6)
Object Class: CKO_SECRET_KEY
Key Type: CKK_DES
Label: 1
Object Handle: 7 (0x7) ……
Object Class: CKO_SECRET_KEY
Key Type: CKK_DES3
Label: 1
Object Handle: 11 (0xb) ……
Object Class: CKO_SECRET_KEY
Key Type: CKK_AES
Label: 1
Object Handle: 15 (0xf) ……
Command Result : No Error /*Operation succeeded.*/

– End of Steps –

6-15

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

6.7 HSMAPP Installation and Configuration

6.7.1 Installing HSMAPP
Abstract
This topic describes how to install the encryption and decryption module (HSMAPP).

Prerequisites
l You have uploaded (in binary mode) the HSMAPP installation files (in the \zxver
_v4\setup\linux\HSM folder in the installation package of ZXUN USPP) into the
/hsm on the PC of the HSM.
l The HSM initialization is complete, and you know the password that is set during key
policy setting.
l You have logged in to the PC as user root.

Steps
1. Carry out the cd /hsm/HSM command to enter the folder saving the HSMAPP
installation files.

2. Carry out the ./install.sh command to install HSMAPP, as shown in the following.

Note:
If the system notifies insufficient permission, you can carry out the chmod 777
install.sh command to change the permission of the files.

6-16

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 6 HSM Installation

bin/
bin/HSM.out
bin/s10see.out
bin/s10dog.out
config/
config/prnlevel.conf
config/hsm.ini
config/s10platservice.ini
config/s10platcfg.ini
config/s10platdog.ini
config/s10plattcpout.ini
config/s10platsntp.ini
config/s10plattelnet.ini
config/s10publishnumber.ini
dos2unix: converting file hsm.ini to UNIX format ...
dos2unix: converting file s10platcfg.ini to UNIX format ...
dos2unix: converting file s10platdog.ini to UNIX format ...
dos2unix: converting file s10platservice.ini to UNIX format ...
dos2unix: converting file s10platsntp.ini to UNIX format ...
dos2unix: converting file s10plattcpout.ini to UNIX format ...
dos2unix: converting file s10plattelnet.ini to UNIX format ...
dos2unix: converting file s10publishnumber.ini to UNIX format ...

3. Carry out the cd /hsm/HSM/config command to enter the command saving the
configuration files.
4. Edit the hsm.ini file in this folder by changing the setting of “HsmPass” to the
password that is set during key policy setting, as shown in the following.

[HSM]
;log level [0,5], default 2
LogLevel=2
;Timer for scan message buffer [1000,60000], default 2000 (unit: 1ms)
ScanMsgBuf_Time=2000
;Timer for scan link [5000,600000], default 10000 (unit: 1ms)
ScanLink_Time=10000
;Max scan time of message in buff [2,50], default 10
LifeScanNum=10
;Normal scan time of check app status [2,60], default 30
NormalScanNum=30
;HSM login password ,default is "password"
HsmPass=password /*the password that is set during key policy setting*/

5. Edit the s10platcfg.ini file in this folder, as shown in the following.

6-17

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

......
area=25 /*Area code*/
bno=203 /*Office ID*/
module=240 /*HSM module Number*/
......
[localinfo]
local1=ip(192.168.203.240),port(5057)
/*Local IP address and port number of the HSM*/
local2=ip(10.10.1.240),port(50240)
/*IP address and port number (5000+module number) of the HSM for the data network*/
local3=ip(10.20.1.240),port(5057)
/*IP address and port number of the HSM for the inter-office NE management network*/

......
[remoteinfo]
/*Set the links between the HSM and remote nodes (DBIOs and SMPs). */
/*For details about the parameters, refer to Table 6-4.*/
/*Only the links to the local DBIOs and SMPs are required. Remote DBIOs and SMPs */
/*work as clients and actively create links to the HSM.*/
remote1=name(node_1_139), area(25),bno(1), module(138), unit(65535),
localip(192.168.1.240), remoteip(192.168.1.2), remoteport(60139),connect(c)

remote2=name(node_1_3), area(25),bno(1), module(3), unit(65535),

localip(192.168.1.240), remoteip(192.168.1.2), remoteport(60003),connect(c)
remote3=name(node_1_4), area(25),bno(1), module(4), unit(65535),
localip(192.168.1.240), remoteip(192.168.1.2), remoteport(60004),connect(c)

Table 6-4 Remoteinfo Parameters

Parameter Description

remote* Information of the remote node.

* refers a serial number, and cannot be duplicated.

name(node_x_y) Sets the name of the link.

x refers to the office ID of the remote node, and y refers to the module
number of the remote node.

area(x) Sets the area code.

x refers the area code.

bno(x) Sets the office ID.

Because the HSM needs to create the links to the local DBIOs and
SMPs only, x refers to the ID of the local office.

module(x) Sets the module number of the remote node.

x refers to the module number of the local DBIO or SMP.

unit(65535) Unit number, default: 65535

6-18

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 6 HSM Installation

Parameter Description

localip(a.b.c.d) Sets the IP address that the HSM uses to communicate with the
remote node.
Because the HSM needs to create the links to the local DBIOs and
SMPs only, a.b.c.d is the HSM IP for the local network.

remote(a.b.c.d) Sets the IP address of the remote node that the HSM communicates
with.
Because the HSM needs to create the links to the local DBIOs and
SMPs only, a.b.c.d is the IP of the remote node for the local network.

remoteport(x) Sets the port number of the remote node that the HSM communicates
with.
Because the HSM needs to create the links to the local DBIOs and
SMPs only, x is the port number (60000+port number) of the remote
node for the local network.

connect(c) Sets the link creating mode.

Default : c (creating actively)

– End of Steps –

6.7.2 Starting the HSSAPP

Abstract
This topic describes how to start the encryption and decryption module (HSMAPP).

Prerequisites
l The HSMAPP is installed.
l The HSMAPP data configuration is complete and synchronized up.
l You have logged in to the PC as user root.

Steps
1. In the Terminal window, carry out the cd /hsm/HSM/bin command to enter the folder
of HSMAPP program files.
2. Carry out the ./hsm.out command to start the HSMAPP.
3. When you have started the HSMAPP, in the Terminal window, carry out the ps -ef|g
rep out command. If the output information about processes contains “hsm.out”, the
HSMAPP has started up successfully.
4. (Optional) to view the status of the links between the HSMAPP and remote nodes, run
s10see.out.
a. Enter the folder of HSMAPP program files, and carry out the ./s10see.out
command.

6-19

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

b. In the window of this tool, check the link status on the Communication tab.
– End of Steps –

6-20

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 7
Agent Installation
Table of Contents
Introduction to Agent ..................................................................................................7-1
Agent Installation Flow ...............................................................................................7-3
GUI Agent Installation ................................................................................................7-4
Web Agent Installation..............................................................................................7-15

7.1 Introduction to Agent

7.1.1 Description
Overview
The agents of ZXUN USPP provides a man-machine interface to realize service
provisioning and subscriber management functions. ZXUN USPP have two types of
agents, GUI agents and Web agents.

GUI Agents
GUI Agents provide a GUI interface for you to manage subscriber data.
The agent module in ZXUN USPP only interacts with the DBIO module. The connection
mode among the modules is TCP/IP. The communication support of the lower layer of the
agent is wintcpip.
The interaction figure between the agent and the DBIO server is shown in the following
figure.

Figure 7-1 Agent-DBIO Interaction

In case that an agent cannot communicate with a DBIO, a secondary forwarding module
can be used, as shown in the following figure.

Figure 7-2 Agent-DBIO Interaction Through a Secondary Forwarding Module

7-1

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Web Agents
You can also use a Web agent to manage subscriber data with an Internet explorer.
A Web agent uses the browser/sever structure as shown in the following figure.

Figure 7-3 Web Agent Structure

Each module of the web agent realizes the following functions.

l Web client: provides the web interfaces for you to provision services provided by NEs.
l Web resource server: saves the programs and files of the web client, and allows the
web client to download these programs and files.
l Web agent server (WEBAGENT): communicates with the web client and the DBIO
to perform such functions as message forwarding, link management and web client
management.

7.1.2 Agent Installation and Configuration Requirements

Requirements of GUI Agents
l Hardware Requirements
The agent is generally installed on normal PCs.
The requirements for the agent hardware configuration are as provided in the following
table.

Table 7-1 Agent Hardware Configuration Requirements

Hardware Configuration

Physical model Normal PCs

Mouse One suit

Keyboard

Display

l Software Requirements
The software configuration required for agent installation is given in the following table.

7-2

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 7 Agent Installation

Table 7-2 Agent Software Configuration Requirements

Software Configuration

Operating system Windows Server 2003 Enterprise Edition, or Windows XP and

the corresponding latest patches

Hard disk partitions Disk C: NTFS format, 20G

Disk D: NTFS format, 40G

Disk E: NTFS format, remaining space

Installation path The operating system software should be installed on disk C

and the agent software could be installed on disk D.

Requirements of Web Agents

A Web agent consists of Web agent servers (WEBAGENT), Web resource servers and
Web clients. The configuration requirements are as follows:
l Web agent server (WEBAGENT): as an independent module, the Web agent server
is configured on a DPBA2 or DPBB2 data processing blade with a CGEL (64-bit)
operating system.

Tip:
The CGEL operating system is installed on the blade in the factory, and you do not
need to install it.

l Web resource server: The Web resource server is configured together with the OMM
server on the DPBX0 or DPBX1 blade. For the detailed installation and configuration
requirements, see 2.1.2 OMM Installation and Configuration Requirements.
l Web client: A Web client can be either configured together with an OMM client or on
an independent PC. For the detailed installation and configuration requirements, see
2.1.2 OMM Installation and Configuration Requirements.

7.2 Agent Installation Flow

GUI Agent Installation Flow
The following table shows the flow of agent software installation.

Step Operation Instructions

1 Install the operating system. See 7.3.1 Installing Operating System

for an Agent for details.

2 Install the antivirus software. See 7.3.2 Antivirus Software Installation

for details.

7-3

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Step Operation Instructions

3 Install the GUI agent software. See 7.3.3 Installing a GUI Agent for
details.

Web Agent Installation Flow

The following table shows the flow to install the Web agent.

Table 7-3 Web Agent Installation Flow

Step Operation Description

1 Install the Web agent In the Web agent, the agent server is implemented through
server. data configuration, without software installation involved. The
specific procedure is as described below:
1. Configure data. For details, refer to data configuration
manuals. This manual only describes the data
configuration items check. For details, refer to 7.4.1 Data
Configuration Check Items Related to Web Agent Server.
2. Synchronize the configuration data and restart the Web
agent server module. For specific operations, refer to
data configuration manuals.
3. Check the interception on the Web agent server. For
details, refer to 7.4.2 Checking Listen of Web Agent
Server.

2 Modify the configuration The Web resource server should be installed on the same
files for the Web blade with the OMM server after the OMM server is installed.
resource server. See 7.4.3 Modifying configuration file for Web Resource
Server for details.

3 Set the Internet Explorer l If the Web client is configured on the same PC with an
of a Web client. OMM client, the Internet Explorer is already set during
the Internet Explorer setting for the OMM client, and you
do not need to set it again.
l If the Web client is configured on an independent PC,
refer to 2.7.1 Setting Internet Explorer for an OMM Client
for details.

7.3 GUI Agent Installation

7.3.1 Installing Operating System for an Agent
Operating System Requirements
The requirements for the operating system of the agent are described as follows.

7-4

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 7 Agent Installation

l Windows Server 2003 and Service Pack 2, or Windows XP

l It should be installed in the default directory on disk C.
l The administrator password should be set based on the engineering specifications.
l The maintenance user and password should be set based on the engineering
specifications.

Operating System Installation

l For the details to install Windows operating system, refer to the self-contained
installation guide of the client computer. After this installation, you should immediately
install the patches for the operating system.
l To set the IP address of the agent, refer to A.5 Setting IP Address on Windows.
l To set the router of the agent, refer to A.6 Setting a Route on Windows.

7.3.2 Antivirus Software Installation

Antivirus Software Installation
When the operating system is installed, it is necessary to install the antivirus software and
update the virus database in time. For the procedure to install the antivirus software, refer
to the related documents.

Antivirus Strategies
It is recommended to adopt the following strategies:
l Enable the real-time antivirus function and set the compressed files to be excluded
from scanning.
l Disable the periodical scanning function.
l Set the antivirus software to give prompts instead of deleting or isolating the
corresponded file when a threat is found.

7.3.3 Installing a GUI Agent

Abstract
This topic describes the procedure to install the GUI agent software. The recommended
installation path is D:\ZTE_HLR. After the installation, the files may occupy a space of
about 42 MB.

Prerequisites
l The operating system and the anti-virus software are installed, and the operating
system is running normally.
l The installation file of ZXUN USPP agent (\zxver_v4\setup\windows\install)
is copied to the computer or mapped to a network drive of the computer.

7-5

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

l If the GUI agent is to communicate directly with a DBIO, you should know the module
numbers and the IP addresses of the GUI agent and the DBIO that the GUI agent is
to access.
l If the GUI agent is to communicate with a DBIO through a secondary forwarding
module, you should know the module number of the agent, the IP address of the
secondary forwarding module, and the module number of DBIO.

Context
The agent provides man-machine interfaces for provisioning various services and
management of subscriber data.
The agent can communicate with the DBIO directly or through the secondary forwarding
module.
If the agent is designed to communicate with a DBIO through a secondary forwarding
module, the agent software installation procedure is the same except that you should
configure (in the tcpseek3g.ini file) the link to the secondary forwarding module on
the agent during the installation. At the same time, you need to perform the corresponding
configuration on the secondary forwarding module (See A.8 Installation and Configuration
of a Secondary Forwarding Module for details).

Steps
1. In the \zxver_v4\setup\windows\install folder, double-click install.bat to
open the JAVA running window. After a short while, the Please Select Language
window appears, as shown in the following figure.

Figure 7-4 Please Select Language

2. Select English and then click NEXT to open the Welcome to Use the Software
window, as shown in the following figure.

7-6

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 7 Agent Installation

Figure 7-5 Welcome to Use the Software

3. Select Typical Setup and then click NEXT to open the Please Select Product Module
window, as shown in the following figure.

Note:
This topic takes a new agent installation as an example, so Typical Setup is selected.
If you want to update the agent, select Service Update.

Figure 7-6 Please Select Product Module

7-7

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

4. Select the HLRAgent check box and then click NEXT to open the Select Setup Item
window.
5. Keep the default setting and then click NEXT to open the Set Install Path window, as
shown in the following figure.

Figure 7-7

6. Select one of the following methods to set the installation path.

l Input the installation path D:\ZTE_HLR.
l Click and then select the installation path from the Please select install path
window that appears.
7. Click NEXT. If the installation directory does not exist, the prompt message The
installation folder D:\ZTE_HLR does not exist. Do you want to create it? will
appear. In that case, click Yes to open the Install Information window.
8. Check whether the installation information is correct.
l Yes: Click Install to unzip and copy files.
l No: Click Back and go back to proper steps to redo the configuration.
9. When the process indicator reaches 100%, click NEXT to open the HLRAgent:
tcpseek3g.ini window, as shown in the following figure.

7-8

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 7 Agent Installation

Figure 7-8 HLRAgent: tcpseek3g.ini

10. Configure the tcpseek3g.ini file.

a. Input the local area code (area), local office ID (bno) and module No. of this agent
(hlragent module). Keep default value of the Nexthop (forwarding node).
b. On the localinfo tab, click the Add button to open the LocalInfo dialog box, as
shown in the following figure.

Figure 7-9 Localnfo

c. Input the IP address of the agent in the ip input box and keep the default value of
port.
d. Click the OK button to add the local information.
e. If necessary, repeat substeps b-d to add more local IP addresses and ports.
f. On the remoteinfo tab, click the Add button to open the remoteinfo window, as
shown in the following figure.

7-9

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Figure 7-10 RemoteInfo

g. Refer to the following table to set the parameters of the DBIO node or secondary
forwarding module node that communicates with the agent.

Note:
If the agent needs to communicates with a secondary forwarding module, the
secondary forwarding module must be configured accordingly. See A.8 Installation
and Configuration of a Secondary Forwarding Module for details.

Table 7-4 Parameter Description of Remote Node Information

Parameter Meaning

Agent communicating with DBIO Agent communicating with

secondary forwarding module

bno ID of the visited office ID of the visited office

area Area code of the visited office Area code of the visited office

unit Keep the default value. Keep the default value.

module Module number of the DBIO module Module number of the DBIO module
that communicates with the agent that communicates with the agent
through a secondary forwarding
module.

connect Connection mode options: C or S Connection mode options: C or S

Select C for the communication Select C for the communication
between the agent and the DBIO between the agent and the secondary
forwarding module

remoteport Port number of the DBIO Port number of the secondary

forwarding module

7-10

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 7 Agent Installation

Parameter Meaning

Agent communicating with DBIO Agent communicating with

secondary forwarding module

localip The IP address of the agent that The IP address of the agent that
communicates with the DBIO. communicates with the secondary
forwarding module.

remoteip The IP address of the DBIO that The IP address of the secondary
communicates with the agent. forwarding module that
communicates with the agent.

h. Click OK to add the remote information.

11. Click NEXT to open the Please Coose Fnctions window.
12. Select required functions. The functions are described in the following table.

Table 7-5 Function Description

Function Description

Add the Program Group If you select this function, the HLRAgent menu item will be
added in the menu Start > All Programs.

Add the ShortCut Link If you select this function, the HLR Agent shortcut icon will
appear on the desktop.

13. Click NEXT to start configuration of the running environment.

14. When the process indicator reaches 100%, click NEXT to open the Setup Is Finished
window.
15. Click Finish to complete the agent software installation.
– End of Steps –

7.3.4 Introduction to GUI Agent Configuration File

Description
The tcpseek3g.ini file is used to set the parameters for communication between a GUI
agent and other modules like DBIOs and secondary forwarding modules. The parameters
include area code, office ID, agent module number, local IP and port, as well as peer-end
module number, IP, port and connection mode.
The tcpseek3g.ini configuration file is in the C:\WINDOWS folder.

Instance: Agent Communicating with DBIO

The parameter settings of this instance are given in the following table:

7-11

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Parameter Value

area code 25

office ID 203

Agent module number 200

local IP and port 192.168.203.200, 5057

DBIO module number 139

DBIO IP and port 192.168.203.2, 60139

The detailed configuration is given below:

[setup]
area=25/*Area Code*/
bno=203 /*Office ID*/
module=200 /*Agent module number*/
nexthop=0 /*Wether to transfer to another node, 0: No, 1:Yes. Set it to 0.*/

WriteDebug=1 /*Wether to record debugging information, 0: No, 1:Yes, recommended

setting: 1*/
WritebreakInfo=0 /*Wether to record link break information, 0: No, 1:Yes, recommended
setting: 0*/
[localinfo]
local1=ip(192.168.203.200),port(5057) /*IP and port used that the agent uses to
communicate with the DBIO*/
[remoteinfo]
remote1=name(node_203_139), area(25),bno(203), module(139), unit(65535),
localip(192.168.203.200), remoteip(192.168.203.2), remoteport(60139),connect(c)
/*Information of the DBIO node that communicates with the agent (node_area code_DBIO
module No. It is node_203_139 in this instance), area code (25), office ID (203), DBIO
module No. (139), unit No. (default 65535), the local IP address (192.168.203.200), DBIO
IP (192.168.203.2), DBIO port, and the connection mode (c means connecting actively.)*/

remote2= /*Information of another node that communicates with the agent. No other node
is set in this instance.*/

7-12

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 7 Agent Installation

Instance: Agent Communicating with Secondary Forwarding Module

Note:
In case an agent communicates with a secondary forwarding module, the secondary
forwarding module must also be configured. See A.8 Installation and Configuration of a
Secondary Forwarding Module for details.

The parameter settings of this instance are given in the following table:

Parameter Value

area code 25

office ID 203

Agent module number 200

local IP and port 10.40.86.200, 5057

Module number that communicates with the agent 139

through a secondary forwarding module

secondary forwarding module IP and port 10.40.86.230, 5057

The detailed configuration is given below:

[setup]
area=25/*Area Code*/
bno=203 /*Office ID*/
module=200 /*Agent module number*/
nexthop=0 /*Wether to transfer to another node, 0: No, 1:Yes. Set it to 0.*/
WriteDebug=1 /*Wether to record debugging information, 0: No, 1:Yes, recommended
setting: 1*/
WritebreakInfo=0 /*Wether to record link break information, 0: No, 1:Yes, recommended
setting: 0*/
[localinfo]
local1=ip(10.40.86.200),port(5057) /*IP and port used that the agent uses to communicate
with the */
[remoteinfo]
remote1=name(node_203_139), area(25),bno(203), module(139), unit(65535),
localip(10.40.86.200), remoteip(10.40.86.230), remoteport(5057),connect(c) /*Information
of the DBIO node that communicates with the agent through the secondary forwarding
module (node_area code_DBIO module No. It is node_203_139 in this instance), area
code (25), office ID (203),DBIO module No. (139), unit No. (default 65535), the local IP

7-13

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

address (10.40.86.200), IP of the secondary forwarding module (10.40.86.230), port of the

secondary forwarding module, and the connection mode (c means connecting actively.)*/

7.3.5 Logging In to a GUI Agent

Abstract
This topic descries how to log in to a GUI agent.

Prerequisites
l Make sure the GUI agent software is installed and configured correctly.
l The data configuration has been synchronized to the DBIO server and DBIO runs
normally.
l The software version of the agent is consistent with that of DBIO. The module No. of
the agent is unique in ZXUN USPP.
l The link communication between the agent and DBIO server is normal.
l The login user name and password are known.

Steps
1. Select one of the following modes to enter the USSP Agent System window shown
in Figure 7-12.
l Click Start > All programs > HLR Agent > HLR Agent.
l Double-click the shortcut icon on the desktop, as shown in Figure 7-11.

Figure 7-11 HLR Agent

Figure 7-12 Agent System

7-14

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 7 Agent Installation

2. Enter the user name and the password in the User Name and Password text boxes,
and then select the DBIO that you want to access from the Login HLR drop-down list.

Note:
l The format of a login HLR isnode_Office-ID_DBIO-module-number.
l The default parameter of the office could be set in the tcpseek3g.ini file in the
c:\windows folder.

3. Click the OK button to enter the 3G Communication System window.

– End of Steps –

Result
l The normal result: enter the main interface of the GUI agent.
l The faulty result: after a short while, the Server timeout prompt appears and the
subscriber could not enter the main interface of the agent. Please contact the service
personnel to solve the problem.

7.4 Web Agent Installation

7.4.1 Data Configuration Check Items Related to Web Agent Server
Description for Data Configuration Check
Before using the Web agent, you need check the configuration items related to the Web
agent server (WEBAGENT). Thus you can ensure that the WEBAGENT data configuration
is complete.
WEBAGENT data configuration items include:
l Module configuration
l IP stack configuration
l Provision web server configuration
l IPV4 dispatch configuration

Note:
In case of a dual-layer network, the data configuration check is better done on the EMS.

Data Configuration Check Items

For details of the data configuration check items to check, refer to Table 7-6.

7-15

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Note:
If the data configuration items are not configured or the configuration content is improper,
you can modify the items by referring to the data configuration manual.

Table 7-6 Data Configuration Check Items on Web Agent Server

Data Com- Purpose Check Requirements

Configuration mand
Check Items

Show Module SHOW To check l The module with Module Type being WEBAGENT is
Configuration MODULE whether at configured.
least one l Location and Module (generally 120 or 121) of the module
WEBAGENT meet the requirements of networking planning.
module is
configured

Show Interface SHOW IP To check In the query result, Interface of the aggregation port is
IPV4 Brief Info INTER- whether the port-channel:Aggregation Port Number.
FACE aggregation l Aggregation port of SIPI for data synchronization (local
BRIEF interface is network) is configured.
configured
à The aggregation port IP (generally 192.168.Office
ID.100) meets the requirements of the networking plan-
ning.

à Both Drv_STAT and NF_STAT are up.

l The aggregation port of SIPI for Web agent server is

configured.

à The aggregation port IP (IP6 of the inter-office NE man-

agement network) meets the requirements of the net-
working planning.

à Both Drv_STAT and NF_STAT are up.

To check In the query result, Interface of the virtual service address is

whether the loopback:Port.
virtual service l The local virtual service address (IP address configured on
address is the loopback interface) of WEBAGENT is configured.
configured
à IP (generally 192.168.Office ID.2) meets the require-
ments of the networking planning.

à Both Drv_STAT and NF_STAT are up.

l Inter-office virtual service address (IP address configured on

the loopback interface) of WEBAGENT is configured).

7-16

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 7 Agent Installation

Data Com- Purpose Check Requirements

Configuration mand
Check Items

à IP (IP7 for the inter-office NE management network)

meets the requirements of the networking planning.

à Both Drv_STAT and NF_STAT are up.

Show Provision SHOW To check l The agent Web server corresponding to WEBAGENT is
Web Server UWE- whether configured.
Configuraton BACFG WEBAGENT l The associated Bureau No and Web Agent Module (that is
is configured the module ID of WEBAGENT) are correctly configured.
l The IP address meets the requirements of the networking
planning, including:

à If the Web client is located in the local network, the

IP address is 192.168.Office ID.2, and the port ID is
3000+Module ID.

à If the Web client is located in the inter-office network man-

agement network, the IP address is the IP7 of the in-
ter-office network management network, and the port ID
is 3000+Module ID.
If Web clients are located in both the local office and inter-office
network management network, two records should be configured
on WEBAGENT for configuring the IP addresses of the local
office and inter-office network management network, respectively.

Show IPV4 SHOW To check The WEBAGENT IP address and port ID in “Provision Web
Dispatch IPV4D- whether the Server Configuration” are configured.
Configuration ISP virtual service
address of the
Web agent
is configured
in the IPV4
dispatch
configuration.

7.4.2 Checking Listen of Web Agent Server

Abstract
This topic describes how to check the listen of the Web agent server. Through this
operation, you can determine whether the Web agent server works properly.

7-17

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Prerequisites
You have completed the configuration data synchronization and restarted the Web agent
server.

Steps
1. Use the remote control tool (for example SecureCRT) on the debugging computer to
log in to the board where the Web agent server is located as root user (with the default
password root).
2. Run the ushell command to log in to ushell, as described below:

~ # ushell /*Log in to ushell*/

====================Notice===================
ushell tool is now replaced by telnet 10000.
=============================================
Entering character mode
Escape character is '^]'.
-----------------------------------------
Welcome to tulip ushell
-----------------------------------------
login: zte /*Login user zte*/
password: *** /*Default login password is zte*/
Successfully login into ushell!
[admin]#

3. Run the show command to query the start process of the Web agent server, as shown
below:

Note:
You can run the show command only in [admin] mode. In other modes, run the admin
command to switch off to [admin] mode and then run the show command.

……
65 SBCO_AGENTSERVER_CGEL_X86_64_64_R_ 7
66 EPU_CGEL_X86_64_64_R_V01.02.21.0 7
67 SMMAGT_CGEL_X86_64_64_R_V01.02.21. 7
68 OAMAGT_CGEL_X86_64_64_R_V01.02.21. 7
69 OSS_CGEL_X86_64_64_R_V01.02.21.0 7
70 FMM_CGEL_X86_64_64_R_V01.02.21.0 7
71 DBMS_CGEL_X86_64_64_R_V01.02.21.0 7
72 SMM_CGEL_X86_64_64_R_V01.02.21.0 7
……

7-18

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 7 Agent Installation

Note:
You can determine the process of the Web agent server by querying the last volume
(logic CPU) of the query result.
To query the logic CPU of the Web agent server, run the SHOW MODULE command
on the NMS.

4. Run sh 66 to open EPU_CGEL_X86_64_64_R_V01.02.21.0(66 is the process ID,

displayed in the first volume of the query result in Step 3).

5. Run tcp_show_tcbs(7)(7 is the logic CPU of the Web agent server) to determine that
the interception located in (lhost:lport) “Web agent server IP address:Port” is started,
as shown in Figure 7-13.

Figure 7-13 Interception Instance

– End of Steps –

7.4.3 Modifying configuration file for Web Resource Server

Abstract
The Web resource server is installed on the OMM server. It is simultaneously installed by
default when the OMM server is being installed. Before using the Web resource server,
you only need complete the file configuration operations mentioned in this topic.

Prerequisites
l The OMM server is installed, and you know the installation path of the OMM server.
l The provisioning server (WEBAGENT) is already configured (during basic data
configuration), and you know the IP address and port number of WEBAGENT.

Context
If you modify the configuration file on the OMM server directly, the file may become illegible
codes. As a result, you may fail to log in to the Web agent.
We suggest you to modify this file on a debugging computer first, and then upload the file
to the specified directory of the OMM server on which the Web resource server is located.

7-19

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Steps
1. Copy the configuration file main-frame-config.xml for the Web resource server
in any of the following folders to the debugging computer.
l \zxver_v4\setup\webagent\pub\main in the ZXUN USPP version folder.
l /uspp_x/webagent/pub/main (x stands for the office ID) in the OMM server
installation directory on the blade.
2. Edit the file as shown in the following and then save the file.
......
<product verMain=""
verBuild=""
commVerMain=""
commVerBuild=""
lang="en_US" /*The language of the Web agent: zh_CN: Chinese, en_US: English*/
name_en="HLR Agent System"
verSupport="6.0"/>
......
<emf path="core/EMF/EMF.swf">
<agentserver webindex="1" module="120" ip="192.168.1.2" iptype="0" port="3120"
clientnum="330"/>
/*Sets the IP address and port of WEBAGNET that the Web clients of the local
network connect to.*/
<agentserver webindex="2" module="120" ip="10.40.86.120" iptype="0" port="3120"
clientnum="330"/>
/*Sets the IP address and port of WEBAGNET that the Web clients of the
inter-office network management network connect to.*/
......

Note:
The values of ip and port on WEBAGENT must be consistent with the IP address and
port ID configured in “Provision Web Server Configuration” on the NMS.
To query the configuration of “Provision Web Server Configuration”, run the SHOW
UWEBACFG command on the NMS

3. Upload the configuration file main-frame-config.xml for the Web resource server
into the directory /uspp_x/webagent/pub/main (x stands for the office ID) of the
OMM server installation directory in binary through FTP.
4. Log in to the blade of the OMM server as user root, and then carry out the following
command to modify the permissions of the webagent folder.
[root@zte01 ~]chmod –R 777 /home/ngomm/webagent/*

– End of Steps –

7-20

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 7 Agent Installation

7.4.4 Logging In to a Web Client

Abstract
This topic describes how to log in to a Web client.

Prerequisites
l (Optional) The IE browser of the Web client is correctly set if you log in to the agent
by the IE browser.
l The Web agent server (WEBAGENT) is already configured, and the configuration data
has been synchronized up.
l The Web resource server is installed.
l The links among the modules of ZXUN USPP are normal.
l You know the user name and password to log in to the agent.

Steps
1. According to different Web agent login mode, perform different operation to open the
Login window.

If Then

Log in to the agent i. Open an IE browser and type http://server IP address:HTTP server
by the IE browser port number/uspp_NE ID/webagent/ (Refer to Table 7-7 for parameter
description) in the Address box.

ii. Press Enter or click Go to go to the Login dialog box as shown in

Figure 7-14.

Log in to the agent i. On the EMS client, perform either of the following operations to open
by the EMS client the log-in window.
l Double-click the NetNumen Client Portal shortcut on the desk-
top.
l Select Start > All Programs > NetNumen Unified Management
System > NetNumen Client Portal

ii. Type the user name and the password in User Name and Password,
and type the IP address of the EMS server in the Server IP text box.

iii. Click the OK button to open the EMS client portal window

iv. Select CN Provision from the Clients list to open the NetNumen Uni-
fied Management System-CN Provision window.

v. Select EMS Server > OMM > omm-USPP_1 (OMM is the name of the
physical office and omm-USPP_1 is the AMO name of the physical
office) to open the Login window, as shown in Figure 7-14.

7-21

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Table 7-7 Descriptions of Web Agent Address Parameters

Parameter Description

Server IP address IP address of the OMM server where the web resource server is
located, for example: 192.168.1.129

HTTP server port number The Listen port number set in the HTTP service configuration
on the OMM server where the web resource server is located,
generally 2323

NE ID The NE ID (office ID) set on the OMM server where the web
resource server is located during the OMM server application
installation, for example: 1

Figure 7-14 Login Window

2. Set the login parameters by referring to Table 7-8.

Table 7-8 Login Parameters Description

Parameter Description

User Name User name for logging in to the web agent. Default: null

Password Password for logging in to the web agent. Default: null

Login HLR Select an office from the drop-down list. In the drop-down list,
the Bureau refers to the local office ID, Module refers to the
module number of the DBIO related to the local office ID. The
corresponding relationship between the local office and the DBIO is
set in FE/Provision Configuration on the NMS.

3. Click Login to open the main window of the Web agent.

– End of Steps –

7-22

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 8
CGSL Operating System
Installation
Table of Contents
Introduction to CGSL Installation ................................................................................8-1
Checking Hard Disk Mirroring.....................................................................................8-3
Change BIOS Settings ...............................................................................................8-9
Installing from DVD Drive .........................................................................................8-12
Operating System Configuration...............................................................................8-24
Network Configuration ..............................................................................................8-31
LED Driver Update ...................................................................................................8-43

8.1 Introduction to CGSL Installation

Overview
This chapter describes how to install the EmbSys CGS Linux (CGSL for short) operating
system on a data processing blade or an OSS processing blade.

Note:
l The user name and password, host names, and IP addresses mentioned in this
manual are for your reference only. You need to set and use these parameters
according to your networking specifications. All the operations mentioned in this
manual are done on a host called zte01.
l The commands for the Linux operating system are case-sensitive. Note to distinguish
them during installation.
l The commands on the CGSL operating system are done on the terminal window.
The method of opening the terminal window is to right-click on any blank area of
the desktop and select Open Terminal. This will not be further described during the
operations.

Requirements
Before installing the operating system, confirm that the blade is inserted in position in the
shelf, and the hardware is properly connected.
The following table shows the requirements for installing the operating system.

8-1

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Table 8-1 Requirements for the Installing Operating System

Item Description

Version EmbSys CGS Linux V3.02.00.p1 32-bit) or later

Language English

Partitions OMM swap 8 GB

server
/boot 1 GB

/ The root partition for OMM server software, the remaining

space,

EMS / The root partition, 30 GB

server
/boot 1 GB

/oracle A customized partition, 70 GB.

EMS server: used to install the Oracle database.
OMM server: for the data of the FireBird database. You
may change the partition name as required.

/ems A customized partition, the remaining disk space, used to

install the server application.

Patches Patch for renaming network cgsl-customize-1.0.0-el5.noarch.rpm

and adapters
drivers
LED atca-drivers-3.0.0-el5.i386.rpm (for a DPBX1
or OPBB1 blade)

IP Local IP for NMS Set according to your IP planning.

Data access and

synchronization network

Local IP for local network

• The operating system and the driver folder are depending on the practical software.
• The partition requirement is based on a hard disk of 146 GB.
• As sizes of the partitions given in the table, this topic assumes that the memory is 4 GB. The size
of the Swap partition is generally set to double of the memory size, or 1 to 1.5 times larger than the
memory size if the memory is larger than 16 GB.
• In IP setting, IP is generally set on the bond adapter. The specific correspondence between IP and
the bond adapter is based on the practical network construction.

Installation Flow
The following table shows the CGSL installation flow.

Table 8-2 CGSL Installation Flow

Step Operation Description

1 Burn BIOS. BIOS has been burnt before delivered.

On-site burning is not needed.

2 Check the hard disk mirroring The disk mirror is generally created in the
factory. You need to check it.

8-2

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 8 CGSL Operating System Installation

Step Operation Description

3 Configure BIOS. Set the system time and the optimization

invoking mode before installing the operating
system.

4 Install the operating system from a CD -

drive.

5 Check and configure the operating Configure and check the operating system,
system. and modify the character set.

6 Configure the network. Set the IP addresses and configure the

network connections.

7 Update the LED drivers. -

8.2 Checking Hard Disk Mirroring

Abstract
A processing blade has two SAS hard disks. A mirrored disk (that is a mirror disk array)
should be created with the two disks before you install the operating system.
Generally, the mirrored disk has been created in the factory. This topic describes how to
check the hard disk mirroring and how to create a mirrored disk if the disk mirroring is not
correct.

Prerequisites
l The blade is inserted in the slot, and the hardware connection is correct and secure.
l A display, a mouse and a keyboard are connected to the blade.

Steps
1. Reboot the blade. After a while, check the boot information for disk mirroring
information.
l As shown in the following figure, if the value of the PRODUCT attribute of a disk
is Logical Volume, this disk is a mirrored disk, and you do not need to create a
mirrored disk again. The operation is completed here.

8-3

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Figure 8-1 Disk Information with a Mirrored Disk

LSI Corporation MPT SAS BIOS
MPTBIOS-6.20.00.00 (2007.12.04)
Corpyright 2000-2007 LSI Corportation.

Integrated RAID exception detected:

Volume (00:000) is currently in state RESYNCING
enter the LSI Corp Configuration Utility to investigate!

SLOT ID LUN VENDOR PRODUCT REVISION SIZE \ NV

---- --- --- -------- --------------- ---------- ---------
34 0 0 LSILOGIC Logical Volume 3000 136 GB
34 LSILogic SAS1064E-IR 1.24.00.00 NV 2D:02
_

l As shown in the following figure, the values of the PRODUCT attribute of Disk 0
and Disk 1 are not Logical Volume, which indicates that the two disks are original
disks and no mirrored disk is created with them. You need to proceed with the
remaining steps to create a mirrored disk.

Figure 8-2 Disk Information without Mirrored Disk

LSI Corporation MPT SAS BIOS
MPTBIOS-6.20.00.00 (2007.12.04)
Corpyright 2000-2007 LSI Corportation.

SLOT ID LUN VENDOR PRODUCT REVISION SIZE \ NV

---- --- --- -------- ----------------- ---------- ---------
34 0 0 FUJITSU MBB2147RC 0105 136 GB
34 1 0 FUJITSU MBB2147RC 0105 136 GB
34 LSILogic SAS1064E-IR 1.24.00.00 NV 2D:02
_

2. Reboot the blade. When the boot information as shown in Figure 8-3 appears, press
<Ctrl+C> to enter the BIOS setting interface as shown in Figure 8-4.

Figure 8-3 Boot Information

LSI Logic Corp. MPT SAS BIOS MPTBIOS-6.14.00.00 (2007.02.05)
Copyright 2000-2007 LSI Logic Corp.
Press Ctrl-C to start SCSI Logic Configuration Utility...

Figure 8-4 SAS BIOS

8-4

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 8 CGSL Operating System Installation

3. Press arrow keys to select SAS1064E, and then press the Enter key to open the
properties of this device, as shown in the following figure.

Figure 8-5 Hard Disk Properties

4. Press arrow keys to select RAID Properties, and then press the Enter key to open
the Select New Array Type interface as shown in the following figure.

Figure 8-6 RAID Setting

5. Press arrow keys to select Create IM Volume, and then press the Enter key to open
the Create New Array interface as shown in the following figure.

8-5

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Figure 8-7 Create New Array-No RAID

6. Choose the disk with Slot Num being 0 as the primary disk. Press arrow keys to
select the RAID Disk setting of this record, and then press the Space key. Notification
information as shown in the following figure appears.

Figure 8-8 Notification for Creating New Array

7. Press arrow keys to select M (you can also select D if necessary), and then press
the Space key to return to the Create New Array interface. The information on this
interface is as shown in the following figure, where the RAID Disk setting of Disk 0 is
Yes.

8-6

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 8 CGSL Operating System Installation

Figure 8-9 Create New Array – With the Primary Disk Set

8. Repeat steps 6 and 7 to set the RAID Disk setting of Disk 1 to Yes, as shown in the
following figure.

Figure 8-10 Create New Array – With the Primary and Secondary Disks Set

9. Press the C to create a mirrored disk (that is, a disk array). Prompt information as
shown in the following figure appears.

8-7

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Figure 8-11 Operation Prompt

10. Press arrow keys to select Save changes then exit this menu, and then press the
Enter key. The View Array interface appears. Now the Drive Status of Disk 1 is
No Syncd, indicating that data is not synchronized between the primary disk and
secondary disk.

Tip:
If the current interface is Adapter Properties as shown in Figure 8-5, you can press
arrow keys to select RAID Properties and then press the Enter key to open the View
Array interface.

Note:
l You can now directly go to Step 15 to reboot the blade. After the blade has booted
up, the data is synchronized automatically. The data synchronization may take 40
to 60 minutes, depending on the size of data on the primary disk.
l If you have chosen D (deleting the data) in the Figure 8-8 interface, after the
mirrored disk is created the interface returns to Adapter Properties. Press the
Esc key till the Exit the Configuration Utility and Reboot option appears in the
interface, and then select it and press the Enter to reboot the blade. The operation
is completed here, and you do not need to do the remaining steps.

11. Press arrow keys to select Manage Array, and then press the Enter key to open the
Manage Array interface.

8-8

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 8 CGSL Operating System Installation

12. Press arrow keys to select Synchronize Array, and then press the Enter key to
synchronize the data between the disks. An interface prompting for your confirmation
appears.
13. Press the Y key to start array synchronization and exit this menu.

Note:
For hard disks of 146G, the data synchronization may take 40 to 60 minutes. During
the data synchronization process, hard disk indicators HD1 and HD2 on the panel of
the blade are always lighting. When the data synchronization completes, the indicators
turn off.

14. When the data synchronization completes, check the disk information in the View
Array interface. The Drive Status of Disk 1 should be Secondary.

Caution!
If you fail to do the steps above and need to redo them, you must use the same disk
as the primary disk. Otherwise, you may lose the data on the disk.

15. Press the Esc key till the Exit the Configuration Utility and Reboot option appears
in the interface, and then select it and press the Enter to reboot the blade.
– End of Steps –

8.3 Change BIOS Settings

Abstract
This topic introduces how to change the BIOS settings of the blade, including modifying
the system time and loading the optimal defaults.

Prerequisites
l The blade is inserted in a proper slot in an shelf, and the hardware connection is
normal.
l The display, the mouse and the keyboard are connected to the blade.

Steps
1. Power on the blade. When the information as shown in the following figure appears,
press Del to open the BIOS SETUP UTILITY window.

8-9

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Figure 8-12 Boot Information

2. On the Main tab, use the arrow keys to move the cursor to the System Time, as shown
in the following figure.

Figure 8-13 Modifying System Time

3. Use the + and - keys to set the system time to the current time, and press the Enter
key to confirm.
4. Set System Date to the current date by referring to steps 2 and 3.

8-10

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 8 CGSL Operating System Installation

5. Press the → key to move to the Exit tab, as shown in the following figure.

Figure 8-14 Exit Tab

6. Use the arrow keys to move the cursor to Load Optimal Defaults, and then press
Enter. A dialogue box for confirmation appears, as shown in the following figure.

Figure 8-15 Confirmation Dialogue Box

7. Use the arrow keys to move the cursor to [OK], and then press Enter to load the
optimal defaults.

8-11

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

8. Press Esc to exit BIOS SETUP UTILITY. A dialogue box for confirmation appears, as
shown in the following figure.

Figure 8-16 Confirmation for Exiting

9. Press the arrow keys to move the cursor to [OK], and then press Enter to complete.
The blade reboots.
– End of Steps –

8.4 Installing from DVD Drive

8.4.1 Setting Boot Mode
Abstract
Before installing the operating system from a USB DVD drive, you need change the boot
device priority of the blade so that it boots from the USB DVD drive. This topic introduces
how to set BIOS.

Prerequisites
l The blade has been inserted in a proper slot in the shelf, and the hardware connection
is normal.
l The USB DVD drive, display, the mouse and the keyboard are connected to the blade.

8-12

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 8 CGSL Operating System Installation

Steps
1. Power on the blade. When the information as shown in Figure 8-17 appears on the
display, press the F11 key to open the list of available boot devices as shown in Figure
8-18.

Figure 8-17 Boot Information

Figure 8-18 List of Available Boot Devices

2. Press the Up and Down arrow keys (↑↓) to select the USB DVD drive as the boot
device.

3. Press the Enter key to proceed with the boot procedure.

– End of Steps –

Follow-Up Action
The blade boots from the USB DVD drive.

8-13

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

8.4.2 Installing the Operating System

Abstract
This topic introduces how to install the CGSL operating system.

Prerequisites
l You have made the necessary preparations.
l You have changed the boot mode of the blade so that the blade tries to boot from the
DVD drive first.
l The operating system (EmbSys CGS Linux V3.0) installation CDs are ready. The
installation CDs may include 6 CDs or 1 DVD. The first CD or the DVD is placed in
the drive.

Steps
1. The blade reboots automatically after the boot mode is changed. When -Press
<ENTER> to start install... appears on the display, press ENTER to start
the installation. A moment later, the information as shown in the following figure
appears, asking you whether to perform media test to check the completeness of the
DVD.

Figure 8-19 Media Test

2. Perform one of the following operations.

If Then Next Step

CD check is Press the Tab key to select OK, and then press the Step 3
required, Space key to confirm and to open the window as
shown in Figure 8-20.

8-14

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 8 CGSL Operating System Installation

If Then Next Step

CD check is not Press the Tab key to select Skip, and then press the Step 6
required, Space key to proceed. The Language Selection
window as shown in Figure 8-21 opens.

Figure 8-20 Media Check

Figure 8-21 Language Selection

3. Press the Tab key to select Test, and then press the Space key to proceed. The
system starts the CD check. When the result appears, perform one of the following
operations.

If Then

No error is found, Go to the next step.

An error is found, Change the disk and perform the installation form the beginning.

8-15

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

The following figure shows a result without errors.

Figure 8-22 Media Check Result

4. Press the Space key to proceed. The system asks you whether to check another CD,
as shown in the following figure.

Figure 8-23 Whether to Check another CD

5. Press the Tab key to select Continue, and then press the Space key to proceed. The
Language Selection window shown in the following figure opens.

8-16

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 8 CGSL Operating System Installation

Figure 8-24 Language Selection

6. Press arrow keys ↓ or ↑ to select English and then press the Tab key to select OK and
press the Space key to proceed. The Partitioning Type window appears, as shown
in the following figure.

Figure 8-25 Partitioning Type

1. Partitioning options 2. Disk options

7. Set the partitioning type.

a. On the window as shown in Figure 8-25, press Tab to switch the cursor to the
partition option part (After that, the selected bar becomes red). In this example,
↑↓ is pressed to move the cursor onto Use free space on selected drives and
create default layout..
b. Press the Tab key to switch the cursor onto the hard disk option part. Press the
Space key to select sda (after selected, “[*] ” appears before sda).

8-17

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

c. Press the Tab key to select OK, and then press the Space key to proceed. The
Review Partition Layout window shown in the following figure appears.

Figure 8-26 Review Partition Layout

8. Press the Tab key to select Yes, and then press the Space key to proceed. The disk
partition information appears.
l If no operating system is installed on the disk, Free space is displayed. Go to
step 10.
l If an operating system is installed on the disk, the list of partitions appears. Go to
step 9.
9. Delete existing partitions.
a. Press arrow key ↑ or ↓ to select a partition, press the Tab key to select Delete,
and then press the Space key to confirm. The Confirm Delete window opens.
b. Press the Tab key to select Delete, and then press the Space key to confirm the
deletion.
c. Repeat the previous steps to delete other partitions.
10. Create a partition on sda.
a. On the Partitioning window, press the Tab key to select New. The Add Partition
window opens, as shown in the following figure.

8-18

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 8 CGSL Operating System Installation

Figure 8-27 Add Partition

Table 8-3 Partition Parameters

Parameter Description

Mount Point For the root partition, enter /; for the swap partition, leave it
empty.

File System type For the swap partition, select swap; for other partitions, ext3
is recommended.

Allowable Drives Disk drives on which you can create a partition

Size (MB) Size of the partition, default: 100M

Fixed Size Sets the size of this partition to be fixed.

Fill maximum size of (MB) The maximum size that this partition can be expanded to, valid
if selected

Fill all available space The size of this partition allowed to be expanded to the total
remaining space of the disk

Force to be a primary If selected, this partition is a primary partition; if not selected,

partition this partition is a logic partition. Linux supports maximum 4
primary partitions.

b. Refer to Table 8-4, Table 8-5 and Table 8-6 to set the partition.

Note:
l For an OMM server, you are recommended to create the root partition (/) first.
l For an EMS server, you are recommended to create the root partition (/) first
and then customized partitions /oracle and /ems.

8-19

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Table 8-4 Requirements for Partitions

Partition Requirement

OMM server swap The swap partition, 8 GB

/boot The Boot partition, 1 GB

/ The root partition, remaining space of sda

EMS server / The root partition, 30 GB

swap The swap partition, 8 GB

/boot The Boot partition, 1 GB

/oracle A customized partition, 70 GB

/ems A customized partition, remaining space of sda

Table 8-5 Partition Settings for OMM Server

Parameter Partition

/boot swap /

Mount Point /boot Do not select. /

File System type ext3 swap ext3

Allowable Drives sda sda sda

Size MB 1024 8192 You can enter any

value smaller than
the remaining disk
space.

Fixed Size Select. Select. Do not select.

Fill maximum size ofMB Do not select. Do not select. Do not select.

Fill all available space Do not select. Do not select. Select.

Force to be a primary Select. Select. Select.

partition

• Press the Tab key switch to another parameter, press the Space key to select, and then
click the OK button to create a partition.

Table 8-6 Partition Settings for EMS Server

Parameter Partition

/ swap /boot /oracle /ems

Mount Point / Do not /boot /oracle /ems

select.

File System type ext3 swap ext3 ext3 ext3

8-20

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 8 CGSL Operating System Installation

Parameter Partition

/ swap /boot /oracle /ems

Allowable Drives sda sda sda sda sda

SizeMB 30720 8192 1024 71680 You can

enter any
value
smaller
than the
remaining
disk space.

Fixed Size Select. Select. Select. Select. Do not

select.

Fill maximum Do not Do not Do not Do not Do not

size ofMB select. select. select. select. select.

Fill all available Do not Do not Do not Do not Select.

space select. select. select. select.

Force to be a Select. Select. Select. Do not Do not

primary partition select. select.

• Press the Tab key switch to another parameter, press the Space key to select, and then
click the OK button to create a partition.

11. After completing the partition, press the Tab key on the Partitioning window to select
OK, and then press the Space key to proceed. The Network Configuration window
appears, as shown in the following figure.

Figure 8-28 Network Configuration

8-21

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

12. You should perform network configuration later. Press the Tab key to select OK, and
then press the Space key to proceed. The Hostname Configuration opens.

Figure 8-29 Hostname Configuration

13. Press arrow key ↑ or ↓ to move the cursor onto manually and then press the Space
key to select it. Press the Tab key to select the input box and input the host name (i.e.
zte01). Press the Tab key to select OK, and then press the Space key to proceed.
The Root Password window opens.

Figure 8-30 Root Password

14. Input the password twice. Press the Tab key to select OK, and then press the Space
key to proceed. The file copying starts, as shown in the following figure (This may take
a long time, please wait).

8-22

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 8 CGSL Operating System Installation

Note:
If the password that you have entered is too short or too simple, or includes invalid
characters, a warning message will appear. You can modify the password according
to the prompt.

Figure 8-31 Package Installation

15. When the file copying process completes, the installation program asks you whether
to install third-party applications, as shown in the following figure.

Figure 8-32 Whether Install Third-Party Application

16. Press the Tab key to select No, thanks, and then press the Space key to proceed.
The Complete window shown in the following figure opens.

8-23

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Figure 8-33 Complete

17. Press the Enter key to reboot. The operating system installation is complete.

Note:
You may check the /root/install.log file to see the log about the operating
system installation.

– End of Steps –

8.5 Operating System Configuration

8.5.1 Configuring General Settings
Abstract
This topic describes the general configuration after the operating system is installed.

The general configuration of the operating system includes:

l Modifying the default boot level, and making the system open the GUI by default.
l Disabling the UTC clock and making the system time identical with the current time.
l Creating the folder for installation files: /soft.

8-24

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 8 CGSL Operating System Installation

Note:
The parameter settings mentioned in this topic, such as user name and password, and
machine name, are for your reference only. You may need to change the settings according
to your actual requirements.

Prerequisites
l The operating system is installed.
l The blade boots from the hard disk.

Steps
1. Modify boot level.
a. Reboot the operating system, and log in to the system as user root.

Embsys CGS Linux V3 (Released By ZTE)

Kernel 2.6.18-53.zte on an i686
zte01 login: root /*Enter user name: root*/
Password： /*Enter the password*/

b. Carry out the following command to open the GUI.

[root@zte01 ~]# startx
c. On the desktop, select Applications > Accessories > Terminal from the menu
to open the terminal.
d. Carry out the following commands to open the /etc/inittab editing window as
shown in the following figure.
[root@zte01 ~]# cd /etc
[root@zte01 etc]# gedit inittab

8-25

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Figure 8-34 Editing inittab

e. Find Default runlevel and set it to 5 (level 5): id:5:initdefault, as shown in Figure
8-34.
f. Click the Save button on the tool bar to save the setting.
g. Reboot the system. The system opens the GUI automatically.
2. Disable the UTC clock.
a. Right-click the time at the upper-right corner of the desktop, and select Adjust
Date & Time from the short-cut menu to open the Date/Time Properties window
as shown in the following figure.

8-26

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 8 CGSL Operating System Installation

Figure 8-35 Date/Time Properties

b. Set the date and time to the current time.

c. Select the Time Zone tab, as shown in the following figure.

8-27

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Figure 8-36 Date/Time Properties- Time Zone

d. Select the local time zone, do not select the System clock uses UTC check box,
and then click OK to save the settings. The system reboots.
3. Create the /soft folder.
a. On the desktop, select Applications > accessories > Terminal from the menu
to open the terminal.
b. Carry out the following command to create the /soft folder.
[root@zte01 ~]# mkdir /soft

– End of Steps –

Result
l The system automatically opens the GUI as it boots up.
l The date and time displayed at the upper-right corner of the desktop are the same as
the current time.
l The /soft folder is created.

8-28

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 8 CGSL Operating System Installation

8.5.2 Checking the Operating System

Abstract
The operating system for an NMS server should be 32-bit CGSL v3.00.02.p1 or a later
edition.
This topic describes how to check the operating system.

Prerequisites
You have logged in to the system as user root (on ZTE01, for example).

Steps
l On the Terminal, run the uname -a command to show the edition of the kernel, and
then check whether the operating system meets the requirements.
l Yes: The operating system is correct.
l No: Remove the operating system and install a proper one.
[root@zte01 ~]# uname -a
Linux zte01 2.6.18-53.ztePAE #1 SMP Mon May 11 14:17:45
CST 2009 i686 athlon i386 GNU/Linux
[root@zte01 ~]#

Note:
In the output information, “SMP” indicates CGSL, and “i386” indicates 32-bit

l On the Terminal, run the cat /etc/kliux-release command to show the edition
of the operating system, and then check whether the edition is “V3_02_00” or later.
l Yes: The operating system is correct.
l No: Contact ZTE to confirm whether you need to reinstall the operating system.
[root@zte01 ~]# cat /etc/klinux-release
TAG_CGS_MAIN_V3_02_00
[root@zte01 ~]#

– End of Steps –

8.5.3 Modifying Character Set

Abstract
This topic describes how to check and modify the character set by taking the EMS server
as an example.

8-29

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Note:
EMS servers and OMM servers have different requirements for the character set. You
must set the character set correctly.

Prerequisites
You have logged in to the system as user root.

Context
The following table shows the requirements of EMS servers and OMM servers for the
character set.

Table 8-7 Requirements for Character Set

Server Type Character Set

OMM server English en_US.UTF-8

Chinese zh_CN.UTF-8

EMS Server English en_US.ISO-8859-1

Chinese zh_CN.GBK

Steps
1. In the Terminal window, carry out the locale command to check the character set
currently used. The result is as follows.
[root@zte01 ~]# locale
LANG=en_US.ISO-8859-1
LC_CTYPE="en_US.ISO-8859-1"
LC_NUMERIC="en_US.ISO-8859-1"
LC_TIME="en_US.ISO-8859-1"
LC_COLLATE="en_US.ISO-8859-1"
LC_MONETARY="en_US.ISO-8859-1"
LC_MESSAGES="en_US.ISO-8859-1"
LC_PAPER="en_US.ISO-8859-1"
LC_NAME="en_US.ISO-8859-1"
LC_ADDRESS="en_US.ISO-8859-1"
LC_TELEPHONE="en_US.ISO-8859-1"
LC_MEASUREMENT="en_US.ISO-8859-1"
LC_IDENTIFICATION="en_US.ISO-8859-1"
LC_ALL=
[root@zte01 ~]#

2. Check whether the character set currently used is en_US.ISO-8859-1.

l Yes: This operation is complete.

8-30

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 8 CGSL Operating System Installation

l No: Proceed with the following steps.

3. Open the /etc/sysconfig/i18n file.
4. Change the value of LANG to en_US.ISO-8859-1, as follows.
LANG="en_US.ISO-8859-1"
SYSFONT="latarcyrheb-sun16"

5. Save the file.

6. In the Terminal window, carry out the reboot command to reboot the operating system
and make the changes effective.
– End of Steps –

8.6 Network Configuration

8.6.1 Installing the Patch for Renaming Network Adaptors
Abstract
This topic describes how to install the patch that you may use to rename network adaptors
(that is, to change the sequence of network adaptors).

Prerequisites
l You have logged in to the system as user root (on ZTE01, for example).
l You have uploaded (in binary mode) the patch (cgsl-customize-1.0.0-el5.no
arch.rpm) into the /tmp on zte01.

Context
In either of the following cases, the names of network adaptors are different from those of
earlier versions. For the purpose of convenient use and maintenance, you can install the
patch for renaming network adaptors.
l DPBA2, DPBX0 or OPBA1 processing blades are used together with DIP1 or OPI1
rear boards whose model number is “RSB11_090500_R5”.

Note:
The model number of a DPI1 or OPI1 board is located at on the board the edge away
from the panel.

l DPBB0, DPBB1, DPBB2, DPBX1 or OPBB1 blades are used.

For the details about the names of network adaptors in case that processing blades are
used together with rear boards, see C Network Adaptors of Processing Blades.

8-31

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Steps
1. Run the cd /tmp command to enter the directory where the patch is saved.
2. Run the rpm -ivh cgsl-customize-1.0.0-el5.noarch.rpm command to
install the patch.
3. Run the atca-rename-nic command to change the sequence of network adaptors.
4. Run the cat /var/log/CGSL/net_device_rename/rename.log command to
check the log file and confirm that the sequence of network adaptors are correctly
changed.
5. Run the reboot command to reboot the blade and to make the changes effective.

– End of Steps –

8.6.2 Identifying Network Adaptors on CGSL

Abstract
This topic describes how to identify a network adaptor on the CGSL operating system.
For the relation between network adaptors, buses and network ports, see C Network
Adaptors of Processing Blades.

Caution!
The network adaptor names mentioned in this topic refer to those that you have renamed.

Prerequisites
l You have logged on to the system as user root.
l You have renamed the network adaptors.

Steps
1. In the Terminal window, run the ethtool -i eth0 command to check the information of
network adaptor eth0. The result is as shown below.

[root@zte01 ~]# ethtool -i eth0

driver: e1000
version: 7.6.15.4-NAPI
firmware-version: 5.10-2
bus-info: 0000:09:00.0 /*Bus information of eth0*/

2. Check the information of other network adaptors by referring to step 1.

– End of Steps –

8-32

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 8 CGSL Operating System Installation

8.6.3 Teaming Network Adapters on CGSL

Abstract
In actual practice, you may need to team two network adapters for redundancy protection
purpose. Generally, two network adapters with the same bus are teamed as a bond, and
the adapters work in active/standby mode.
This topic takes network adapters eth6 and eth7 on the Base plane of a bade for example
to describe how to team network adapters.

Prerequisites
l You have logged in to zte01 as user root.
l You have renamed the network adaptors.
l You know the information about the network adapters. See 8.6.2 Identifying Network
Adaptors on CGSL for reference.

Steps
1. In the Terminal window, run the ict command to open the CGSL Integrated
Configuration Tool dialog box, as shown in the following figure.

Figure 8-37 CGSL Integrated Configuration Tool

2. In the left pane, click the icon before Network to expand the tree.
3. Double click Bonding Management under Network to open the NIC Bonding
Management Tool interface, as shown in the following figure.

8-33

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Figure 8-38 NIC Bonding Management Tool

4. Click Create to open the Create New Bonding dialog box, as shown in the following
figure.

Figure 8-39 Create New Bonding

5. Set the parameters by referring to the following table.

8-34

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 8 CGSL Operating System Installation

Table 8-8 Parameters for Binding Network Adaptors

Parameter Description

Please select devices to bond Select the network adaptors, for example, eht6 and eth7

Device Name Name of the binding of network adaptors, for example, trunk0

Please select bonding mode Select active-backup

Configure IP address now Select this check box and then type the static IP address, the
subnet mask and the gateway (optional) for the binding.

Use DHCP Do not select this check box.

6. Click Ok to bind the network adaptors. A dialog box opens, asking you whether to
immediately restart the network service.
7. Click NO and return to the NIC Bonding Management Tool interface. The newly
created network adaptor binding appears in the Bonding Devices list.
8. On the desktop, select Applications > Accessories > Terminal from the menu to
open the terminal.
9. Use the vi command to edit the configuration files of eth 6 and eth7, as shown in the
following.

[root@uds100 ~]# vi /etc/sysconfig/network-scripts/ifcfg-eth6

/*Edit configuration file of eth6.*/
DEVICE=eth6
ONBOOT=yes
#HWADDR=00:22:93:6F:6B:BC /*Disable this line with "#".*/
MASTER=trunk0
SLAVE=yes
BOOTPROTO=none
USERCTL=no
[root@uds100 ~]# vi /etc/sysconfig/network-scripts/ifcfg-eth7
/*Edit configuration file of eth7.*/
DEVICE=eth7
ONBOOT=yes
#HWADDR=00:22:93:6F:6B:BD /*Disable this line with "#".*/
MASTER=trunk0
SLAVE=yes
BOOTPROTO=none
USERCTL=no

10. Run the service network restart command to restart the network service.

– End of Steps –

8-35

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

8.6.4 Setting IP Addresses for a Network Adaptor on CGSL

Abstract
This topic describes how to set IP addresses for a network adaptor on a CGSL operating
system.

Prerequisites
l The patch for renaming network adaptors is installed.
l To add IP addresses for a network adaptor team (that is, bond network adaptors), you
should team the network adapters in advance.
l You have logged on to the system as user root.

Steps
1. On the desktop of the system, choose System > Administration > Network from the
menu to open Network Configuration window as shown in the following figure.

Figure 8-40 Network Configuration

2. Double-click the network adaptor that you want to add IP addresses for to open the
Ethernet Device dialog box shown in the following figure.

8-36

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 8 CGSL Operating System Installation

Figure 8-41 Ethernet Device

3. Select the Statically set IP addresses radio box, and then type the IP address, subnet
mask and default gateway (optional) in corresponding input fields.
4. Click OK to set the IP address and return to the Network Configuration window.
l To add more IP addresses for this network adaptor, repeat Steps 5–13.

Note:
The IP addresses mentioned in this topic are static IP addresses, which still work
after the system is restarted. To add a temporary IP address, which is removed
after the system is restarted, run the ifconfig Network_adaptor_name
IP_address netmask netmask_setting command as shown in the
following.

# ifconfig eth0 129.0.254.129 netmask 255.0.0.0

l To proceed with the remaining operation, go to Step 14.

5. Click the New button to open the Add new Device Type dialog box shown in the
following figure.

8-37

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Figure 8-42 Add new Device Type

6. From the Device Type list, select Ethernet connection, and then click Forward to
open the Select Ethernet Device dialog box.
7. From the Ethernet card list, select the network adaptor that you want to add IP
addresses for, and then click Forward to open the Configure Network Settings
dialog box as shown in the following figure.

8-38

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 8 CGSL Operating System Installation

Figure 8-43 Configure Network Settings

8. Select the Statically set IP addresses radio box, and then type the IP address, subnet
mask and default gateway (optional) in corresponding input fields.
9. Click Forward to open the Create Ethernet Device dialog box.
10. Click Apply to close the Create Ethernet Device dialog box and return to the Network
Configuration window. On the Devices tab, you can see the newly added Ethernet
device, which is in Inactive status.
11. To activate the Ethernet device, select it and click the Activate button. A dialog box
opens, prompting for your confirmation.
12. Click Yes. A dialog box opens, telling you that you need to restart the network or the
blade to make the changes effective.
13. Click OK. The Ethernet device should become activated.

14. Close the Network Configuration window. A dialog box opens, asking you whether
to save the modification in the configuration.
15. Click Yes. A dialog box opens, telling you that you need to restart the network or the
blade to make the changes effective.

16. Click OK to close the Network Configuration window.

8-39

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

17. In the terminal window, carry out the service network restart command to restart
the network and make the changes in the configuration effective.
– End of Steps –

8.6.5 Setting Routes on CGSL

Abstract
This topic describes how to set routes on a CGSL operating system.

Prerequisites
You have logged on to the system as user root.

Steps
1. On the desktop of the system, choose System > Administration > Network from the
menu to open Network Configuration window as shown in the following figure.

Figure 8-44 Network Configuration

2. Double-click the network adaptor that you want to add IP addresses for to open the
Ethernet Device dialog box.
3. Open the Route tab as shown in the following figure.

8-40

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 8 CGSL Operating System Installation

Figure 8-45 Ethernet Device–Route

4. Click the Add button to open the Add / Edit IP Address dialog box shown in the
following figure.

Figure 8-46 Add / Edit IP Address

5. Type the destination IP address in the Address input field, and then type the subnet
mask and the gateway.

6. Click OK to close the Add / Edit IP Address dialog box and return to the Route tab
of the Ethernet Device dialog box. The route newly added appears in the list.

7. To add more routes, repeat Steps 4–6.

8. Click OK to close the Ethernet Device dialog box.

8-41

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

9. Close the Network Configuration window. A dialog box opens, asking you whether
to save the modification in the configuration.
10. Click Yes. A dialog box opens, telling you that you need to restart the network or the
blade to make the changes effective.
11. Click OK to close the Network Configuration window.
12. In the terminal window, carry out the service network restart command to restart
the network and make the changes in the configuration effective.
– End of Steps –

8.6.6 Modifying the hosts file

Abstract
This topic describes how to modify the hosts file.

Prerequisites
l The IP address configuration is complete.
l You have logged in to zte01 as user root.

Context
The hosts file in the /etc folder provides the correlation between IP addresses and host
names.
If a blade is configured with multiple IP addresses, the IP address for the public network
should be set to “localhost”. (for an NMS server, the public network is the inter-office NE
management network.)

Steps
1. Open the /etc/hosts file.
2. Find the line that contains “hostname localhost.localdomain localhost” (hostname here
refers to the actual host name), and change the IP address in this line (originally
127.0.0.1) to the IP address to the IP address for the network management network.
3. Save and close the file.

4. In the Terminal window, run reboot command to reboot the blade.

– End of Steps –

8-42

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 8 CGSL Operating System Installation

8.7 LED Driver Update

8.7.1 Updating LED Driver for DPBX0 and OPBA1
Abstract
This topic describes how to update the LED driver for a DPBX0 or OPBA1 blade.

Prerequisites
You have logged in to the system as user root (on ZTE01, for example).

Context
Before the LED driver is updated, the “ACT” and “HOST” indicators on the panel are
orange. After the LED driver is updated, the “ACT” indicator flashes in green or is off,
and the “HOST” indicator is off.
Because the CGSL operating system has the LED driver for DPBX0 and OPBA1 blades,
you just need to run the sbcoled command to install the driver.

Steps
l In the terminal window, run the sbcoled command to update the LED driver, as shown
in the following.

[root@zte01 ~]# sbcoled

======================================================
leddriver configure shell
======================================================
Now begin to configure led_driver for sbco or sbcw board.
Please input Physical Board Type correctly (sbco or sbcw) :
sbco /*Enter sbco.*/
The Board type configured is: sbco
Attention: Delete module leddrv from memory first!
Finished: Led driver for sbco has been added to local system successfully.
Do some necessary check or test, please.

– End of Steps –

Result
Check the indicators on the panel. The “ACT” indicator should be flashing in green or off,
and the “HOST” indicator should be off.

8-43

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

8.7.2 Updating LED Driver for DPBX1 and OPBB1

Abstract
This topic describes how to update the LED driver for a DPBX1 or OPBB1 blade.

Prerequisites
l You have logged in to the system as user root (on ZTE01, for example).
l You have uploaded the installation package (atca-drivers-3.0.0-el5.i386.r
pm) into the /tmp folder on the blade with an FTP tool in binary mode.

Context
Before the LED driver is updated, the “ACT” and “HOST” indicators on the panel are
orange. After the LED driver is updated, the “ACT” indicator flashes in green or is off,
and the “HOST” indicator is off.
Because the CGSL operating system does not have the LED driver for DPBB0, DPBB1,
DPBB2, DPBX1 or OPBB1 blades, you must install and execute the driver.

Steps
1. In the terminal window, run the cd /tmp command to enter the directory.
2. Run the rpm -Uvh atca-drivers-3.0.0-el5.i386.rpm command to install
the driver.
3. Run the /usr/bin/sbcjled command to execute the driver program.
– End of Steps –

Example
Check the indicators on the panel. The “ACT” indicator should be flashing in green or off,
and the “HOST” indicator should be off.

8-44

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 9
Oracle Database Installation
Table of Contents
Introduction to Oracle Installation ...............................................................................9-1
Preparations...............................................................................................................9-3
Installing Oracle 10g...................................................................................................9-7
Installing Oracle 10204 Patch...................................................................................9-15
Creating an Oracle Instance .....................................................................................9-19
Configuring Oracle Database Listener ......................................................................9-29
Configuring a Name for Local Oracle Service ...........................................................9-34
Checking Oracle Installation .....................................................................................9-39
Configuring Autostart of Oracle Services Upon Starting............................................9-39

9.1 Introduction to Oracle Installation

Overview
This chapter describes how to install the Oracle database software on the blade.

Note:
During installing the database, you need distinguish the user root from the user oracle.
Note the description for the operations.

Installation Requirements
The requirements for installing the Oracle database are as listed in the following table.

Table 9-1 Requirements for Installing Oracle

Configuration Item Description

Core folder of the CGSL system linux_zh.zip

user oracle User name: oracle

Home groups: oinstall, dba

Oracle software requirements Oralce 10g and 10204 update patch (specific version is depending
on the practical software)

9-1

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Configuration Item Description

Home Directory Name: OraDb10g_home1

Path: /oracle/product/10gR2

Global database name, SID Configured as needed. It is suggested to be consistent.

Interception Name: LISTENER

Protocol: TCP
Port: 1521

Local service name of Oracle Service name, network service name: configured as needed. It
is suggested to be consistent.
Host name: the current IP of the host
Protocol: TCP
Port: 1521

Self-boot script of Oracle server oracle.sh, autostartoracl.sh

• When you are installing the Oracle database for EMS server, the local service name of the database
should be set to SID_HostName.

Installation Flow
The following table shows the Oracle installation flow.

Table 9-2 Oracle Installation Flow

Step Operation Description

1 Prepare for the installation. Before installing Oracle, replace the CGSL
system core file, create user oracle, and
configure the environment variable.

2 Install Oracle 10g. -

3 Install the Oracle 10204 patch. -

4 Create an Oracle instance. -

5 Configure interception. -

6 Configure local service of Oracle. -

7 Check the Oracle installation. -

8 Set self-boot for Oracle After installing Oracle, you can configure the
self-boot of the Oracle service after startup or not.

9-2

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 9 Oracle Database Installation

9.2 Preparations
9.2.1 Updating Kernel of the CGSL Operating System
Abstract
Before installing the Oracle database, the kernel of the CGSL operating system must be
updated.
This topic describes how to update the kernel of the operating system.

Prerequisites
l The kernel patch file (linux_en.zip) is ready.
l You have logged in to the system as user root (on ZTE01, for example).

Steps
1. Copy the kernel patch file to the /soft folder.
2. On the desktop, select Applications > Accessories > Terminal from the menu to
open the terminal.
3. Carry out the following command to extract the kernel files. Enter y to confirm
overwriting if the system prompts you to confirm during the extraction process.
[root@zte01 ~]# cd /soft
[root@zte01 soft]# unzip linux_en.zip
4. Carry out the following commands respectively to copy the patch files to corresponding
folders. Enter y to confirm overwriting if the system prompts you to confirm.
[root@zte01 ~]# cp /soft/linux_en/sysctl.conf /etc/sysctl.conf

[root@zte01 ~]# cp /soft/linux_en/limits.conf /etc/security/limits

.conf
[root@zte01 ~]# cp /soft/linux_en/login /etc/pam.d/login

[root@zte01 ~]# cp /soft/linux_en/config /etc/selinux/config

[root@zte01 ~]# cp /soft/linux_en/profile /etc/profile

5. Carry out the /sbin/sysctl –p command to show the contents of the /sbin/sy
sctl file. The settings in the contents should be identical with the following figure.

9-3

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Figure 9-1 Contents of the sysctl File

6. Reboot the system to make the configuration effective.

– End of Steps –

Result
When the system boots up, open the terminal and carry out the ulimit –a command to
check the configuration. The correct settings are as shown in the following figure.

Figure 9-2 Configuration Check

9-4

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 9 Oracle Database Installation

9.2.2 Creating User Oracle and Its Groups

Abstract
This topic describes how to create user oracle and its user groups.

Prerequisites
You have logged in to the system on ZTE01 as user root.

Steps
1. On the terminal window, carry out the cd / command to enter the system partition.
2. Create user groups oinstall (for data base installation) and dba (database
administrator). The commands are as follows.
[root@zte01 /]# groupadd oinstall
[root@zte01 /]# groupadd dba
[root@zte01 /]# groupadd oper
3. Create the oracle user, and add it to groups oinstall and dba. The command is as
follows.
[root@zte01 /]# useradd -g oinstall -G dba oracle
4. Modify the password of user oracle, as shown in the following.

[root@zte01 /]# passwd oracle

Changing password for user oracle.
New UNIX password:
Retype new UNIX password:
passwd:all authentication tokens updated successfully.

Note:
The password should meet the complexity requirements. If you set the password of
user oracle to “oracle”, the system prompts “bad password”. You may ignore the
prompt.

– End of Steps –

Result
On the desktop, select System > Administration > Users and Groups from the menu to
open the Users and Groups window.
l On the Users tab, user oracle exists.
l On the Groups tab, user oracle exists in groups oinstall and dba.

9-5

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

9.2.3 Setting Environment Variables for User Oracle

Abstract
This topic describes how to set folder authorities and other environment variables for user
oracle.

Prerequisites
l You have logged in to the system on ZTE01 as user root.
l The kernel of the CGSL operating system is updated.
l User oracle and its groups are created.

Steps
1. On the desktop, select Applications > Accessories > Terminal from the menu to
open the terminal.
2. Carry out the cd / command to enter the system partition.
3. Carry out the following commands to create the installation path for the Oracle
database, and then to modify the main attribute of this path to oracle (user group:
oinstall).
[root@zte01 /]# cd
[root@zte01 ~]# mkdir -p /oracle/product/10gR2
[root@zte01 ~]# chown -R oracle:oinstall /oracle
4. Carry out the following command to overwrite the /home/oracle/.bash_profile
file with the /soft/linux_en/.bash_profile file (created during 9.2.1 Updating
Kernel of the CGSL Operating System).
[root@zte01 ~]# cp /soft/linux_zh/.bash_profile /home/oracle/.bash
_profile
5. Carry out the following commands to change the main attribute of the .bash_profi
le file to oracle (group: oinstall).

[root@zte01 ~]# cd /home/oracle

[root@zte01 ~]# chown oracle:osinstall .bash_profile

6. Use the vi command to edit the /home/oracle/.bash_profile file and set the
environment variables as shown in the following table.

Table 9-3 Settings of Environment Variables for User oracle

Parameter Value Description

ORACLE_BASE /oracle -

ORACLE_HOME /oracle/product/10gR2 -

9-6

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 9 Oracle Database Installation

Parameter Value Description

ORACLE_SID omc Instance name, may be modified as

required but must be the same as those
used in the follow-up operations.

NLS_LANG AMERICAN_AMERICA.WE8M The English character set for the database

SWIN1252

7. Carry out the following command to copy the environment variables of user oracle to
the /root folder. Enter y to confirm overwriting if the system prompts you to confirm
during the process.
[root@zte01 ~]# cp /home/oracle/.bash_profile /root
8. Reboot the system to make the settings effective.
– End of Steps –

9.3 Installing Oracle 10g

Abstract
This topic describes how to install Oracle 10g on the CGSL operating system.

Prerequisites
l The preparations are made.
l You have logged in to the system as user root (on ZTE01, for example).
l You have uploaded the folder database in the folder Oracle 10g (for linux), and the
file Disk1 in the 10204 patch file to /soft on the server in binary through FTP.

Note:
The directory of the installer in /soft may vary, depending on your practical case.

Steps
1. On the terminal window, set the operating system of /etc/redhat-release as
“Embsys CGS Linux release V3.0”, as shown below.

[root@zte01 ~]# echo "Embsys CGS Linux release V3.0" > /etc/redhat
- release
[root@zte01 ~]# cat /etc/redhat-release
Embsys CGS Linux release V3.0
/*Confirm that the output information is correct.*

9-7

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

2. Execute the following commands to modify the file modification authority.

[root@zte01~]# cd /soft
[root@zte01 soft]# chmod -R 777 database
[root@zte01 soft]# chmod -R 777 Disk1
3. Execute the following commands to log off the user root and log in as user oracle.
The installer execution starts. Wait a moment, the window for selecting an installation
method appears, as shown in Figure 9-3.
[root@zte01 soft]# su - oracle
[root@zte01 soft]# cd database

[oracle@zte01 database]$ ./runInstaller

Figure 9-3 Select Installation Method

4. Select the Advanced Installation check box and then click Next to open the window
for specifying inventory directory and credentials, as shown in the following figure.

9-8

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 9 Oracle Database Installation

Figure 9-4 Specify Inventory Directory and Credentials

5. Enter the installation folder (the default /oracle/oraInverntory folder is

recommended), select oinstall from the Specify Operating System group name:
dropdown list, and then click Next to open the window for selecting an installation
type, as shown in the following figure.

Figure 9-5 Select Installation Type

9-9

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

6. Select the Standard Edition check box and click Next to open the window for
specifying home details, as shown in the following figure.

Figure 9-6 Specify Home Details

7. Check whether the Name is OraDb10g_home1 and that the Path is /oracle/produ
ct/10gR2. If not, modify the settings. Click Next to open the window for checking
product-specific prerequisites, as shown in the following figure.

9-10

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 9 Oracle Database Installation

Figure 9-7 Product-Specific Prerequisite Checks

8. If errors occur during the check process, eliminate the errors according to the prompts
and then re-install Oracle. If there is no error, click Next to open the window for
selecting configuration option, as shown in the following figure.

Figure 9-8 Select Configuration Option

9-11

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

9. Select the Install database Software only check box and then click Next to open the
Summary window as shown in the following figure.

Figure 9-9 Summary

10. Click the Install button to start the installation.

When the installation process is complete, the window prompting for executing the
scripts appears, as shown in the following figure.

9-12

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 9 Oracle Database Installation

Figure 9-10 Execute Configuration Scripts

Note:

Do not click OK here, the next operation is further needed.

11. Open a new terminal window, and execute the first script among those displayed in
Figure 9-10 as user root, as shown in the following.

Note:

If you do not log in as user root, you may carry out the su command and then switch
to user root according to the prompt information.

root@zte01 ~]# cd /oracle/oraInventory/

/*Open the directory for saving the scripts*/
[root@zte01 oraInventory]# ./orainstRoot.sh/*Execute the scripts*/
Changing permissions of /oracle/oraInventory to 770.
Changing groupname of /oracle/oraInventory to oinstall.
The execution of the script is complete

12. Execute the second script among those displayed in Figure 9-10, as shown in the
following.

9-13

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

[root@zte01 oraInventory]# cd /oracle/product/10gR2/

/*Open the directory for saving the scripts*/
[root@zte01 10gR2]# ./root.sh/*Execute the scripts*/
Running Oracle10 root.sh script...
The following environment variables are set as:
ORACLE_OWNER= oracle
ORACLE_HOME= /oracle/product/10gR2
Enter the full pathname of the local bin directory:
[/usr/local/bin]: /oracle/product/10gR2
/*Input the main directory path of Oracle*/
The file "dbhome" already exists in /oracle/product/10gR2.
Overwrite it? (y/n)
[n]: y /*Input yconfirm covering the existing dbhome*/
Copying dbhome to /oracle/product/10gR2 ...
The file "oraenv" already exists in /oracle/product/10gR2.
Overwrite it? (y/n)
[n]: y /*Input y to confirm covering the existing oraenv*/
Copying oraenv to /oracle/product/10gR2 ...
The file "coraenv" already exists in /oracle/product/10gR2.
Overwrite it? (y/n)
[n]: y /*Input y to confirm covering the existing coraenv*/
Copying coraenv to /oracle/product/10gR2 ...
Entries will be added to the /etc/oratab file as needed by
Database Configuration Assistant when a database is created
Finished running generic part of root.sh script.
/*The script running ends.*/

13. When all the scripts are executed, click OK on the window as shown in Figure 9-10 to
open the End of Installation window.

14. Click Exit to open the Exit dialogue box.

15. Click Yes to complete the installation of Oracle 10g.
16. On the terminal window, carry out the following commands as user root to modify
/etc/redhat-release, as shown in the following.

[root@zte01 ~]#su – root

[root@zte01 ~]#echo"Red Hat Enterprise Linux Server release 5
(Tikanga)" > /etc/redhat-release
[root@zte01 ~]#cat /etc/redhat-release
Red Hat Enterprise Linux Server release 5 (Tikanga)
/*Confirm that the output information is correct.*/

– End of Steps –

9-14

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 9 Oracle Database Installation

9.4 Installing Oracle 10204 Patch

Abstract
After you installed Oracle 10g, you need to update it to version 10.2.0.4. This topic
describes how to install the Oracle 10204 patch.

Prerequisites
l Oracle 10g is installed.
l You have logged in to the system as user oracle (on ZTE01, for example).

Steps
1. On the desktop, select Applications > Accessories > Terminal from the menu to
open the terminal.
2. Carry out the following commands in turn to enter the installation directory and run the
patch file to open the Welcome dialog box.
[oracle@zte01 ~]$ cd soft/Disk1
[oracle@zte01 Disk1]$ ./runInstaller
3. Click Next to open the dialog box for specifying home details, as shown in the following
figure.

Figure 9-11 Specify Home Details

4. Confirm that the name is OraDb10g_home1 and that the path is

/oracle/product/10gR2. Correct the name and path if necessary. Click Next to open

9-15

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

the dialog box for checking product-specific prerequisites, as shown in the following
figure.

Figure 9-12 Product-Specific Prerequisite Checks

5. If errors occur during the check process, eliminate the errors according to the
prompts and then re-install Oracle. If there is no error, click Next to open the Oracle
Configuration Manager dialog box shown in the following figure.

9-16

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 9 Oracle Database Installation

Figure 9-13 Oracle Configuration Manager Registration

6. Keep the default settings and click Next to open the Summary dialog box as shown
in the following figure.

Figure 9-14 Summary

7. Click the Install button to start the installation.

9-17

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

When the installation process is complete, a dialog box prompting for executing the
script appears, as shown in the following figure.

Note:
Do not click OK on the dialog box, keep the dialog box and proceed with the next step.

Figure 9-15 Execute Configuration Script

8. Open a new terminal, and execute the first script among those displayed in Figure
9-15 as user root, as shown in the following.

Note:
If you are not logged in the system as user root, and carry out the su command to
change to user root.

9-18

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 9 Oracle Database Installation

[root@zte01 ~]# cd /oracle/product/10gR2/

/*Open the directory for saving the scripts*/
[root@zte01 10gR2]#./root.sh
/*Run the script.*/
Running Oracle10 root.sh script...
The following environment variables are set as:
ORACLE_OWNER= oracle
ORACLE_HOME= /oracle/product/10gR2
Enter the full pathname of the local bin directory:
[/usr/local/bin]: /oracle/product/10gR2
/*Input the Oracle directory path*/
The file "dbhome" already exists in /oracle/product/10gR2.
Overwrite it? (y/n)
[n]: y /*Input y, confirm to cover the existing dbhome*/
Copying dbhome to /oracle/product/10gR2 ...
The file "oraenv" already exists in /oracle/product/10gR2.
Overwrite it? (y/n)
[n]: y /*Input y, confirm to cover the existing oraenv*/
Copying oraenv to /oracle/product/10gR2 ...
The file "coraenv" already exists in /oracle/product/10gR2.
Overwrite it? (y/n)
[n]: y /*Input y, confirm to cover the existing coraenv*/
Copying coraenv to /oracle/product/10gR2 ...
Entries will be added to the /etc/oratab file as needed by
Database Configuration Assistant when a database is created
Finished running generic part of root.sh script.
/*The script execution ends.*/

9. When all the script execution is complete, click OK on the dialog box shown in Figure
9-15 to open the End of Installation dialog box.
10. Click Exit to open the Exit dialogue box.
11. Click Yes to complete the installation of the patch.
– End of Steps –

9.5 Creating an Oracle Instance

Abstract
This topic introduces how to create an Oracle database instance on zte01.

9-19

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Note:
The instance name set during the installation can be modified as desired.

Prerequisites
l You have installed Oracle software.
l You have logged in to zte01 as user oracle.

Steps
1. On the terminal window, run the dbca command as user oracle to start the Database
Configuration Assistant: Welcome window.

Note:
If you are not user oracle, run the su - oracle command to switch to user oracle.

2. Click Next to open the Database Configuration Assistant, Step 1 of 12: Operations
window as shown below.

Figure 9-16 Operations

3. Click to select Create a Database, click Next to open the Database Templates
window, as shown below.

9-20

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 9 Oracle Database Installation

Figure 9-17 Database Templates

4. Click and select Custom Database and then click Next to open the Database
Identification window, as shown below.

Figure 9-18 Database Identification

5. Enter the instance name in the Global Database Name input box. In this topic, omc is
entered, and the default SID is inconsistent with Global Database Name. Click Next
to open the Management Options window as shown below.

9-21

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Figure 9-19 Management Options

6. Keep the default setting and then click Next to open the Database Credentials window
as shown below.

Figure 9-20 Database Credentials

7. Click and choose Use the Same Password for All Accounts. Enter the password in
the Password input box, and enter the password again in Confirm Password. Click
Next to open the Storage Options window as shown below.

9-22

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 9 Oracle Database Installation

Figure 9-21 Storage Options

8. Click and select File System and then click Next to open the Database File Locations
window, as shown below.

Figure 9-22 Database File Locations

9. Click and choose Use Database File Locations from Template. Click Next to open
the Recovery Configuration window as shown below.

9-23

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Figure 9-23 Recovery Configuration

10. Do not choose any option from the window. Click Next to open the Database Content
window as shown below.

Figure 9-24 Database Content

11. Set the database content.

9-24

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 9 Oracle Database Installation

Tab Operation

Database i. Check only Enterprise Manager Repository, do not check other param-
Components eters.

ii. Click Standard Database Components to open the Standard Database

Components dialog box, as shown below.

iii. Uncheck all the options and then click OK to return to the Database Con-
tent window.

Custom Scripts Script is not needed during installation, so it does not need to be set.

Figure 9-25 Standard Database Components

12. Click Next to open the Initialization Parameters window as shown below.

9-25

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Figure 9-26 Initialization Parameters

13. Set the initialization parameters.

Tab Operation

Memory i. Click the All Initialization Parameters button to open the All Initializa-
tion Parameters dialog box, as shown below.

ii. Click the Show Advanced Parameters button to show advanced param-
eters, as shown in Figure 9-27.

iii. Find the parameter option nls_date_format from the list and click Value
and enter ’YYYY-MM-DD HH24:MI:SS’ (including the single quotation
marks) in the input box, and check Override Default. Click Close to return
to the Initialization Parameters window.

Modify the Size Just accept the default value without modifying it.

Character sets Check whether the default character set is “WE8MSWIN1252”.

l Yes: click and choose Use Default.
l No: choose WE8MSWIN1252 from the Database Character Set
dropdown list.

Connection Click and choose Shared Server Mode with other parameters unchanged.
Mode

9-26

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 9 Oracle Database Installation

Figure 9-27 All Initialization Parameters-Show Advanced Parameters

14. Click Next to open the Database Storage window as shown below.

9-27

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Figure 9-28 Database Storage

15. Keep the default setting and then click Next to open the Creation Options window,
as shown below.

Figure 9-29 Creation Options

16. Keep the default settings, and click Finish, the OK window pops up.
17. Click OK to start database instance creation.

18. A message box opens prompting the details about the database creation when the
progress reaches 100%. Click Exit to finish Oracle instance creation.

9-28

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 9 Oracle Database Installation

– End of Steps –

9.6 Configuring Oracle Database Listener

Abstract
This topic introduces how to configure Oracle database listener.

Prerequisites
l The Oracle instance has been created.
l You have logged in to zte01 as user root.

Steps
1. On the terminal window, run the netca command as user oracle to start the Oracle
Net Configuration Assistant: Welcome window, as shown in the following figure.

Note:
If you are not user oracle, run the su - oracle command to switch to user oracle.

Figure 9-30 Oracle Net Configuration Assistant: Welcome

2. Select Listener configuration to open the Oracle Net Configuration Assistant:

Listener Configuration, Listener window, as shown in the following figure.

9-29

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Figure 9-31 Listener

3. Select Add and then click Next to enter the Oracle Net Configuration Assistant:
Listener Configuration, Listener Name window as shown in the following figure.

Figure 9-32 Listener Name

4. Enter LISTENER in the Listener name text box (generally you can accept the default
without modifying it). Click Next to open the Oracle Net Configuration Assistant:
Listener Configuration, Select Protocols window, as shown in the following figure.

9-30

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 9 Oracle Database Installation

Figure 9-33 Select Protocols

5. Accept TCP listed in Selected Protocols by default, without modification. Click Next
to open the Oracle Net Configuration Assistant: Listener Configuration, TCP/IP
Protocol configuration window, as shown in the following figure.

Figure 9-34 TCP/IP Protocol

6. Select Use the standard port number of 1521 and then click Next to enter the Oracle
Net Configuration Assistant: Listener Configuration, More Listeners window, as
shown in the following figure.

9-31

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Figure 9-35 More Listeners

7. Click No and then click Next to open the Oracle Net Configuration Assistant:
Listener Configuration Done window.

8. Click Next to return to the welcome window.

9. Click Finish to complete the listener configuration.
10. Run the command netmgr to open the Oracle Net Manager window, as shown in the
following figure.

9-32

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 9 Oracle Database Installation

Figure 9-36 Oracle Net Manager

11. On the Oracle Net Configuration navigation tree, click Local > Listeners >
LISTENER, opening the window as shown in the following figure.

Figure 9-37 LISTENER Configuration

9-33

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

12. Select Database Services from the dropdown menu list on the top of the configuration
pane, and set the parameters referring to Table 9-4.

Table 9-4 Description for Parameters of Database 1

Parameter Configuration Description

Global Database Name: Input the global database name set while creating the database
instance. Here, you can input omc.

Oracle Home Directory You can ignore this parameter without setting it.

SID Input the SID set while creating the database instance (generally it is
consistent with the global database name). Here, still input omc.

13. Click File > Save Network Configuration to save the configuration.
– End of Steps –

9.7 Configuring a Name for Local Oracle Service

Abstract
This topic describes how to configure a local service name on the Oracle database.

Note:
You can modify the service name, host name, and network service name involved in
configuration as needed.

Prerequisites
The database instance is created.

Steps
1. On the terminal window, execute the netca command as user oracle, to open the
Oracle Net Configuration Assistant: Welcome window, as shown in the following
figure.

Note:

If you are not user oracle, execute the su - oracle command to switch to user
oracle.

9-34

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 9 Oracle Database Installation

Figure 9-38 Welcome

2. Click and select Local Net Service Name Configuration to open the Net Service
Name Configuration window, as shown in the following figure.

Figure 9-39 Net Service Name Configuration

3. Click Next to open the window for setting the service name, as shown in the following
figure.

9-35

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Figure 9-40 Setting a Service Name

4. Enter the service name (generally the SID, such as omc in the instance in this manual),
and then click Next to open the window for selecting a protocol, as shown in the
following figure.

Figure 9-41 Selecting a Protocol

5. Select TCP and click Next to open the window for TCP/IP configuration, as shown in
the following figure.

9-36

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 9 Oracle Database Installation

Figure 9-42 TCP/IP Configuration

6. Enter the IP address of the current host in the Host name input box. Select the Use
the standard port number of 1521 check box. Click Next to open the window for
connection test, as shown in the following figure.

Figure 9-43 Connection Test

7. Select the No, do not test check box and click Next to open the window for setting
the net service name.

9-37

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Figure 9-44 Setting Net Service Name

8. Enter the net service name. (The default net service name is the same as the service
name set in Step 4, which is also recommended). Click Next to open the window for
selecting whether to set another net service name, as shown in the following figure.

Figure 9-45 Whether to Set Another Net Service Name

9. Select No and click Next. A window opens, notifying that the net service name
configuration is successful.
10. Click Next to return to the Welcome window of Oracle Net Configuration Assistant.

11. Click Finish to complete the local service name configuration.

– End of Steps –

9-38

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 9 Oracle Database Installation

9.8 Checking Oracle Installation

Abstract
After installing the Oracle database, you need check the installation to avoid problems in
later installation of the server software.
This topic introduces how to check the Oracle installation.

Prerequisites
l You have logged in to zte01 as user root.
l You have installed the Oracle database.

Steps
1. On the terminal windows, run the su - oracle command to switch to user Oracle.
2. Log in to sqlplus, as shown below.
[oracle@zte01 ~]$ sqlplus /nolog
SQL*Plus: Release 10.2.0.4.0 - Production on Fri Jan 29 10:28:00 2010
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.

Wherein, Release 10.2.0.4.0 is the version of Oracle.

3. Check whether you can properly log in to sqlplus and whether the database version is
10.2.0.4.0. If you fail, you need check the faults and perform troubleshooting according
to the error prompts on the window. If the database version is inconsistent, check the
Oracle installation procedure, or reinstall the database software.
4. In sqlplus, run the connect command to connect to the instance, as shown below.
Wherein, “sys/password” is the sys username and password of the instance, which
service name is “omc”.
SQL> connect sys/password@omc as sysdba
connected.

5. Check whether the instance can be connected. If not, check the database and remove
the errors according to the prompt on the window.
– End of Steps –

9.9 Configuring Autostart of Oracle Services Upon

Starting
Abstract
This topic introduces how to configure autostart of Oracle services upon starting the Oracle
server. After completing the configuration, you need not manually boot the Oracle services
any longer when you restart the operating system.

9-39

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Prerequisites
l You have checked the Oracle installation.
l You have logged in to zte01 as user root.
l You have uploaded the autostart scripts oracle.sh and autostartorcl.sh for
Oracle services to the /soft folder on the server in binary through FTP. Note that the
script names should be lower case.

Steps
1. On the terminal window, open the directory /soft where the autostart scripts are
stored and modify the authority of the scripts, as shown below.

[root@zte01 ~]# cd /soft

[root@zte01 soft]# chmod 777 autostartorcl.sh
[root@zte01 soft]# chmod 777 oracle.sh

2. Run the autostart scripts, as shown below.

[root@zte01 soft]# ./autostartorcl.sh

Note:
autostartorcl.sh re-execution will not affect the functions. When
the script is re-executed, a prompt similar to ln: creating symbolic link
`/etc/rc.d/rc2.d/S99oracle' to `../init.d/oracle': File exists will appear.

– End of Steps –

Result
After the operating system is restarted, the Oracle service will automatically start.

9-40

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Chapter 9 Oracle Database Installation

Note:
For some CGSL system of other versions, after the autostart scripts are executed, the
Oracle process cannot be stopped due to Oracle software itself. The prompt appearing on
the window is as shown below.

omm login: stopping oracle: Stopping Oracle Listeners ...

If this occurs, manually press the reset key.

And execute the following command on the terminal window when the system is restarted
the next time.
[root@zte01 ~]# rm -f /etc/rc.d/rc0.d/K01oracle
[root@zte01 ~]# rm -f /etc/rc.d/rc6.d/K01oracle

9-41

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

This page intentionally left blank.

9-42

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Appendix A
General Operations
Table of Contents
Ÿ Accessing a Shared Directory on Windows from CGSL .......................................... A-1
Ÿ Establishing a Remote Control Connection to CGSL .............................................. A-3
Ÿ Transferring Files to a CGSL Host .......................................................................... A-7
Ÿ Restarting CGEL .................................................................................................... A-9
Ÿ Setting IP Address on Windows............................................................................ A-11
Ÿ Setting a Route on Windows................................................................................. A-14
Ÿ Introduction to Files for EMS Clock Configuration ................................................. A-14
Ÿ Installation and Configuration of a Secondary Forwarding Module ........................ A-16

A.1 Accessing a Shared Directory on Windows from

CGSL
Abstract
When you are operating on CGSL, you might need to access a shared folder on a Windows
system, for example, to download script files. This topic describes how to access a shared
folder on a Windows system from a CGSL operating system.

Prerequisites
l You have logged in to the CGSL operating system as user root.
l You know the IP address and the domain name of the computer of the Windows
operating system, and know the user name and password to access the shared folder.
l The communication between the CGSL operating system and the Windows operating
system is normal.

Steps
1. On the CGSL desktop, select Places > Connect to Server from the menu to open the
Connect to Server window as shown in the following figure.

A-1

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Figure A-1 Connect to Server

2. Set the parameters.

a. Select Windows share from the Service Type drop-down list.
b. Type the IP address of the Windows system in the Server field.
c. Optional: Type the user name used to access the shared folder and the domain
name of the Windows system.
3. Click the Connect button to open the Authentication Required dialogue box as
shown in the following figure.

Figure A-2 Authentication Required

A-2

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Appendix A General Operations

Note:
If you have already set the user name and domain name, fields User Name and
Domain Name do not appear on this dialogue box.

4. Set the parameters.

Table A-1 Authentication Parameters

Parameter Description

Username The user name that you use to access the shared folder on the
Windows system

Domain The domain name of the Windows system

Password The password of the user name that you use to access the
shared folder on the Windows system

Remember password for this Whether to let the CGSL system remember the password
session

Save password in keyring Whether to save the user name and password in the key ring

5. Click the Connect button to access the shared folder.

– End of Steps –

A.2 Establishing a Remote Control Connection to

CGSL
Abstract
The blades of ZXUN USPP are installed in shelves. For the ease of maintenance and
operation on the operating system, this topic introduces two tools and methods to connect
to the CGSL operating system from a remote debugging PC.

Prerequisites
l You have logged on to system as user root.
l You have logged on to the debugging PC (the one for remote control, with a Windows
operating system).
l The remote control tool, SecureCRT 5.0 or Xmanager3 or any later version of them,
is installed on the debugging PC. (For how to install the tools, see their self-contained
instructions.)
l The communication between the debugging PC and the CGSL server is normal.

A-3

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Steps
l Use an SSH2-based Telnet tool (SecureCRT 5.0 or a later version) for remote control.

Note:
By default, the CGSL operating system supports and has enabled the SSH2 protocol,
so you do not need to do any remote control setting on the CGSL operating system.
SecureCRT supports command lines only and does not support GUI.

a. Run SecureCRT.exe, and choose File > Quick Connect from the menu to open
the Quick Connect dialog box as shown in the following figure.

Figure A-3 Quick Connect

b. Set the parameters by referring to the following table.

Table A-2 SecureCRT Parameters

Parameter Description

Protocol Select SSH2.

Hostname Type the IP address of the host.

Port Set the port that the SSH2 protocol uses.

Firewall Keep the default (None).

Username Type the user name.

A-4

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Appendix A General Operations

c. Click Connect to open the Enter Secure Shell Password dialog box as shown
in the following figure.

Figure A-4 Enter Secure Shell Password

d. Type the password for user in the Password input box, and click OK to log on.
l Use an XDMCP-based GUI access tool (Xmanager3 or a later version) for remote
control.

Note:
The CGSL operating system supports XDMCP but does not enable it by default.
To enable the XDMCP service, you must modify the configuration file. Xmanager
supports both command lines and GUI. You are recommended to use Xmanager.

a. Open the Terminal window of the CGSL operating system.

b. Use the vi command to edit the /etc/gdm/custom.conf file. Add a new line
after the [security] line: AllowRemoteRoot=true. And add another line after the
[xdmcp] line: Enable=true, as shown in the following.

...
[daemon]

[security]
AllowRemoteRoot=true

[xdmcp]
Enable=true

[gui]
...

c. Run the reboot command to restart the system and to make the configuration
effective.

A-5

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

d. On the debugging PC, run the Xbrower component of Xmanager, as shown in the
following figure.

Figure A-5 Xbroswer

e. In the Address input box, type the IP address of the server and click Go to open
the CGSL GUI window as shown in the following figure.

A-6

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Appendix A General Operations

Figure A-6 CGSL GUI

– End of Steps –

A.3 Transferring Files to a CGSL Host

Abstract
This topic describes how to transfer files to a CGSL host from Windows with WinSCP.

Prerequisites
l The FTP tool (for example, WinSCP) is installed on the debugging PC (with a
Windows operating system). For the details about how to install WinSCP, refer to the
self-contained instructions of the software.
l The communication between the debugging PC and the CGSL host is normal.
l The FTP service of the CGSL host is enabled. For details about how to enable the
FTP service, see 2.3.7 Setting FTP Service on CGSL.

Context
Because of the difference in the coding of Chinese file names between Windows and Linux,
if you copy files to a shared folder on the CGSL host, Chinese file names become illegible
codes. Therefore, you should transfer the files to the CGSL host with an FTP tool (for
example, WinSCP) in binary mode.

A-7

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Steps
1. On the debugging PC, run WinSCP.exe to open the WinSCP Login window as shown
in the following figure.

Figure A-7 WinSCP Login

2. Select Session on the navigation tree in the left pane, and then set the parameters by
referring to the following table.

Table A-3 WinSCP Login Parameters

Parameter Description

Host name The IP address of the CGSL host that the files are to be
transferred to

User name User name of the CGSL host, generally root

Password Password of the user

Protocol Select SFTP.

3. Click Login to log in to the CGSL host, as shown in the following figure.

A-8

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Appendix A General Operations

Figure A-8 Logged In to CGSL

4. Set the transfer parameters as follows.

l In the pane of local files and directories on the left, select the files to be transferred.
l In the pane of remote files and directories on the right, select the directory that
the files are to be transferred to.
l From the transfer mode drop-down list as marked in Figure A-8, select Binary.

5. Click the F5 Copy button. The Copy dialog box opens.

6. Confirm the copy information and then click the Copy button to transfer the files.
– End of Steps –

Follow-Up Action
The EMS server has a self-contained FTP service. To transfer files to the EMS server, you
must stop the FTP service in advance with the service vsftpd stop command.

A.4 Restarting CGEL

Abstract
The CGEL operating system does not support being restarted with the reboot command.
This topic describes how to restart CGEL.

A-9

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Prerequisites
The communication between the debugging PC and the blade is normal.

Steps
1. On the debugging PC, log in to the CGSL host as user root (default password: root)
with a remote control tool.
2. Carry out the ushell command to log in to Ushell, as shown in the following.

~ # ushell /*log in to Ushell.*/

====================Notice===================
ushell tool is now replaced by telnet 10000.
=============================================

Entering character mode

Escape character is '^]'.

-----------------------------------------
Welcome to tulip ushell
-----------------------------------------

login: zte /*User name: zte*/

password: *** /*Default password: zte*/
Successfully login into ushell!

[admin]#

3. Carry out the show command to show “SODAMGR” processes.

Note:
The show command can be carried out only in [admin] mode. In case of any another
mode, carry out the admin command to switch to the [admin] mode in advance.

4. Carry out the sh 1 command to enter the SODAMGR process, as shown in the
following.

[admin]# sh 1
Now switch to SODAMGR shell ...
[SODAMGR]#

5. Carry out the BSP_BoradReset() command to restart the blade.

A-10

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Appendix A General Operations

[SODAMGR]# BSP_BoardReset()
[SODAMGR][BSP]:lssp Board begin to Reset Please wait.....

– End of Steps –

A.5 Setting IP Address on Windows

Abstract
This topic describes how to set the IP address on a Windows operating system.

Prerequisites
l The network adapter is working properly.
l The IP address complying with your IP address plan is ready.

Steps
1. Right-click the My Network Places icon and select Properties from the shortcut menu
to open the Network Connections window.
2. Right-click the Local Area Connection icon and select Properties from the shortcut
menu to open the Local Area Connection Properties dialog box.
3. Select Internet Protocol (TCP/IP) and select the Properties button on the Local
Area Connection Properties dialog box. The Internet Protocol (TCP/IP) Properties
dialog box shown in the following figure opens.

A-11

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Figure A-9 Internet Protocol (TCP/IP) Properties

4. Set IP address and subnet mask of the host in the LAN of background system
according to your IP address plan.
5. If more IP addresses are required, you can click Advanced button for addition.
a. Click the Advanced button. The Advanced TCP/IP Settings dialog box shown
in the following figure opens.

A-12

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Appendix A General Operations

Figure A-10 Advanced TCP/IP Settings

b. In the IP address field, click Add. The TCP/IP Address dialog box shown in the
following figure opens.

Figure A-11 TCP/IP Address

c. Input IP address and subnet mask and click Add to return to the Advanced TCP/IP
Settings dialog box. More IP addresses can be added if necessary.
d. Click OK to return to the Internet Protocol (TCP/IP) Properties dialog box.
6. Click OK to close the dialog box and save the settings.

– End of Steps –

A-13

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

A.6 Setting a Route on Windows

Abstract
This topic describes how to add a static route on a Windows operating system.

Prerequisites
l The IP address configuration is complete.
l You know the network section, the subnet mask and the gateway address of the route
to set.

Steps
1. Click Start > Run to open the Run dialog box, type cmd and click OK to open the
cmd.exe window.
2. Carry out the following command to add a route.
>route -p add 10.20.0.0 mask 255.255.0.0 10.40.10.3
Wherein,
l 10.20.0.0 is the internal network section of the remote network management
subsystem.
l 255.255.0.0 is the net mask.
l 10.40.10.3 is the IP address of the gateway.
– End of Steps –

Result
l On the cmd.exe window, carry out the route print command to view the route
configuration. The configured route should exist in the Persistent Routes list, as
shown in the following.
Persistent Routes:
Network Address Netmask Gateway Address Metric
10.20.0.0 255.255.0.0 10.40.10.3 1

l Using the ping command, you can ping through to an existing IP addresses in the
network section (10.20.0.0).

A.7 Introduction to Files for EMS Clock Configuration

Overview
The files for EMS clock configuration are as follows.
l For EMS server: /ums-server/works/cluster/deploy/deploy-cluster.p
roperties in the root folder of the EMS server, used to set the address and port of
the superior clock source, as well as the port for providing clock source for other clock
clients when the EMS server acts a clock server

A-14

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Appendix A General Operations

l For EMS client: \ums-client\works\global\deploy\deploy-usf.propert

ies in the root folder of the EMS client, used to set the address and port of the superior
clock source

Introduction to the File for EMS Server Clock Configuration

usf.joss.jndi.server.prot=$[${usf.usf.ems.baseport+21101]
usf.components.clocksync.sync.port=$[${usf.components.clocksync.sync.internalport}+
${usf.usf.ems.baseport}]
usf.jboss.jndi.rmi.port=$[${usf.usf.ems.baseport} + 21102]
usf.jboss.jmxrmiadaptor.service.port=$[${usf.usf.ems.baseport} + 21114]
usf.components.clocksync.sync.port=21124
/*Add this line if the EMS server needs to work as a clock server.*/
/*The port is generally set to 21124, you can also change it if necessary.*/

usf.components.clocksync.source01.ip=127.0.0.1
/*IP of the superior primary clock source. Set it to 127.0.0.1 if you want to use
the self-contained clock synchronization service of the operating system.*/

usf.components.clocksync.source01.port=123
/*Port of the superior primary clock source. Set it to 123 if you want to use the
self-contained clock synchronization service of the operating system.*/

usf.components.clocksync.source02.ip=127.0.0.1
/*IP of the superior secondary clock source. Set it to 127.0.0.1 if you want to use
the self-contained clock synchronization service of the operating system.*/

usf.components.clocksync.source02.port=123
/*Port of the superior secondary clock source. Set it to 123 if you want to use the
self-contained clock synchronization service of the operating system.*/

A-15

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Introduction to the File for EMS Client Clock Configuration

......
#=================================================================================#
usf.components.clocksync.source01.ip=127.0.0.1
/*IP of the superior primary clock source, generally set to the IP of the EMS server*/

usf.components.clocksync.source01.port=123
/*Port of the superior primary clock source. It is generally 21124 if the EMS server
acts as the clock source.*/

usf.components.clocksync.source02.ip=127.0.0.1
/*IP of the superior secondary clock source. It is generally the same as the primary
clock source or the default.*/

usf.components.clocksync.source02.port=123
/*Port of the superior secondary clock source. It is generally the same as the primary
clock source or the default.*/
......

A.8 Installation and Configuration of a Secondary

Forwarding Module
Situation of Application
In the ZXUN USPP network, if a DBIO has only an IP address for the local network but
no IP address for the accounting network while an agent has only an IP address for the
accounting network but no IP address for the local network, a secondary forwarding module
can help the agent and the DBIO to communicate with each other.
It is recommended that you should install the secondary forwarding module on an
independent PC. The PC should have a Windows or CGSL (32-bit) operating system and
be able to communicate with both the remote agent and the DBIO.

Installation on Windows
You can follow the following procedure to install a secondary forwarding module on
Windows.
1. Copy the files in the \zxver_v4\setup\linux\routetrans folder in the ZXUN
USPP software package into any folder on the PC, such as D:\ZTE_HLR.
2. Set the configuration file (s10platcfg.ini in folder /routetrans/config) of the
secondary forwarding module. The contents of the file are as follows.
[Setup]
area=25 /*Area code*/

A-16

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Appendix A General Operations

bno=203 /*Office ID*/

module=230 /*Module number of the secondary forwarding module*/
isoutserver=0
runname=routetrans.exe /*The executable file*/
apptitle=routetrans /*Application name*/
maxappruntime=60

maxappcycleruntime=20
maxappexitwait=1
linkalarm=0
deh=1

prnlevel=5
[localinfo]
local2=ip(10.40.86.230),port(5057) /*IP address and port number that the secondary
forwarding module uses to communicate with the agent.*/

local1=ip(192.168.203.230),port(5057) /*IP address and port number that the

secondary forwarding module uses to communicate with the DBIO.*/
[remoteinfo]

remote1=name(node_203_139), area(25),bno(203), module(139), unit(65535),

localip(192.168.6.230), remoteip(192.168.203.139), remoteport(60139),connect(c)
/*Settings of the DBIO node that the secondary forwarding module communicates
with (Node number: node_AreaCode_DBIOModuleNumber, as node_203_139 in this
instance, area code: 25, office ID: 203, DBIO module number: 139, unit number:
65535 (default), local IP: 192.168.203.230, DBIO IP: 192.168.203.139, DBIO port
number: 60139, connection mode: c (connecting actively) */
......
3. Run \routetrans\bin\routetrans.exe to start the secondary forwarding
module.
The icon ( ) of the secondary forwarding module appears on the task bar of Windows.

4. Do the following to check the link status between the secondary forwarding module
and the remote node with s10see.exe.
a. Copy the zxver_v4\setup\windows\HSM\bin\s10see.exe file in the \rou
tetrans\bin\ folder.

b. Run s10see.exe and then open the Communication tab to view the link status.

Installation on CGSL
You can follow the following procedure to install a secondary forwarding module on CGSL.

A-17

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

1. Copy the files in the \zxver_v4\setup\linux\routetrans folder in the ZXUN

USPP software package into any folder on a debugging PC.
2. Set the configuration file (s10platcfg.ini in folder /routetrans/config) of the
secondary forwarding module. The contents of the file are as follows.
[Setup]
area=25 /*Area code*/
bno=203 /*Office ID*/
module=230 /*Module number of the secondary forwarding module*/
isoutserver=0
runname=routetrans.out /*The executable file*/
apptitle=routetrans /*Application name*/
maxappruntime=60
maxappcycleruntime=20
maxappexitwait=1
linkalarm=0
deh=1
prnlevel=5
[localinfo]
local2=ip(10.40.86.230),port(5057) /*IP address and port number that the secondary
forwarding module uses to communicate with the agent.*/
local1=ip(192.168.203.230),port(5057) /*IP address and port number that the
secondary forwarding module uses to communicate with the DBIO.*/
[remoteinfo]
remote1=name(node_203_139), area(25),bno(203), module(139), unit(65535),
localip(192.168.6.230), remoteip(192.168.203.139), remoteport(60139),connect(c)
/*Settings of the DBIO node that the secondary forwarding module communicates
with (Node number: node_AreaCode_DBIOModuleNumber, as node_203_139 in this
instance, area code: 25, office ID: 203, DBIO module number: 139, unit number:
65535 (default), local IP: 192.168.203.230, DBIO IP: 192.168.203.139, DBIO port
number: 60139, connection mode: c (connecting actively) */
......
3. Transfer (in binary mode) the routetrans folder and the files in it to any location (for
example, /zxhlr) on the CGSL host with an FTP tool.
4. In the Terminal window of the CGSL host, carry out the cd command to enter the rou
trans/config folder for the configuration files of the secondary forwarding module.
5. Carry out the dos2unix *.* command to convert the configuration files to UNIX format.
6. Carry out the cd command to enter the routrans/bin folder for the executive files
of the secondary forwarding module.

A-18

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Appendix A General Operations

7. Run ./routetrans.out to start the secondary forwarding module.

8. When the secondary forwarding module has started up, in the Terminal window
of the CGSL host, carry out the ps -ef|grep out command to view the process
information. If the process information contains “routetrans.out”, the secondary
forwarding module has started up successfully.
9. Do the following to check the link status between the secondary forwarding module
and the remote node with s10see.out.
a. Contact ZTE to get the s10see.out program.
b. Transfer the s10see.out file in binary mode into the routrans/bin folder on
the CGSL host.
c. Carry out the cd command to enter the routrans/bin folder for the executive
files of the secondary forwarding module.
d. Carry out the ./s10see.out command and then open the Communication tab to
view the link status.

A-19

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

This page intentionally left blank.

A-20

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Appendix B
Service Set Check
Table of Contents
Ÿ Basic Concepts ...................................................................................................... B-1
Ÿ Checking a Service Set with Ushell......................................................................... B-1
Ÿ Introduction to Service Sets .................................................................................... B-3

B.1 Basic Concepts

ZXUN USPP uses a service set to realize a specific logic function such as a module or a
unit. A service set consists one or more service types, as shown in the following figure.

Figure B-1 Structure of Service Set

A service type corresponds to a process. You check whether a module or unit has
successfully started up by checking the service types of the service set of this module or
unit.

B.2 Checking a Service Set with Ushell

Abstract
This topic describes how to log in to a blade and check the service set.

Prerequisites
Versions are loaded.

Steps
1. On a debugging PC, log in to the blade as user root (default password: root) with a
remote control tool (for example SecureCRT).

B-1

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

2. Carry out the ushell command to log in to Ushell, as shown in the following.

~ # ushell
====================Notice===================
ushell tool is now replaced by telnet 10000.
=============================================

Entering character mode

Escape character is '^]'.
-----------------------------------------
Welcome to tulip ushell
-----------------------------------------
login: zte /*User name: zte*/
password: *** /*Default password: zte*/
Successfully login into ushell!

[admin]#

3. Carry out the show command to show the processes, and then check whether the
module or unit has successfully started up by referring to “B.3 Introduction to Service
Sets”.

Note:
The show command can only be carried out in [admin] mode. In case of another mode,
carry out the admin command to switch to [admin] mode before carrying out the show
command.
The last volume of the query result is the logic CPU, with which, you can determine
the module or unit of the process.
l To query the logic CPU of a module, run the SHOW MODULE command on the
NMS.
l To query the logic CPU of a unit, run the SHOW UNIT command on the NMS.

– End of Steps –

B-2

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Appendix B Service Set Check

B.3 Introduction to Service Sets

Note:
l The version numbers (digits after “R_V”) of your service types may be different from
those described in this topic.
l Service types with a name beginning with “SBCO” or “SBCJ” are related to board
types.
à DPBA2: Relates to service types with a name beginning with “SBCO”.
à DPBB0, DPBB1 and DPBB2: Relate to service types with a name beginning with
“SBCJ”.
l The OMP in this table refers to an OMP with RPU and DMCC integrated.
l When an OMP has started for the first time, only 10 processes (the first 10 in the table)
are running. For an OMP working normally, the 18 processes are all running.

Table B-1 Service Types of Each Module and Unit

Module/Unit Service Types

Base process PLAT_CGEL_X86_64_64_R_V01.02.21.00

OMP SODAMGR
DBMS_CGEL_X86_64_64_R_V01.02.21.00
VMM_CGEL_X86_64_64_R_V01.02.21.00
SMM_CGEL_X86_64_64_R_V01.02.21.00
SYSCFG_CGEL_X86_64_64_R_V01.02.21.00
SMMAGT_CGEL_X86_64_64_R_V01.02.21.00
FMM_CGEL_X86_64_64_R_V01.02.21.00
SBCO_RSMM_CGEL_X86_64_64_R_V01.02.00 or
SBCJ_RSMM_CGEL_X86_64_64_R_V01.02.00
OAMMGR_CGEL_X86_64_64_R_V01.02.21.00
OSS_CGEL_X86_64_64_R_V01.02.21.00
SBCO_FEUDS_CGEL_X86_64_64_R_V01.02.21.00 or
SBCJ_FEUDS_CGEL_X86_64_64_R_V01.02.21.00
EPU_CGEL_X86_64_64_R_V01.02.21.00
SIGSVC_CGEL_X86_64_64_R_V01.02.21.00
BRSCFG_CGEL_X86_64_64_R_V01.02.21.00
RPU_CGEL_X86_64_64_R_V01.02.21.00
OAMAGT_CGEL_X86_64_64_R_V01.02.21.00
ATMMP_CGEL_X86_64_64_R_V01.02.21.00
SBCO_OMCPLAT_CGEL_X86_64_64_R_V01.02.21.00 or SBCJ_OMC-
PLAT_CGEL_X86_64_64_R_V01.02.21.00

B-3

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Module/Unit Service Types

SMP/CMP EPU_CGEL_X86_64_64_R_V01.02.21.00
SIGSVC_CGEL_X86_64_64_R_V01.02.21.00
3SMM_CGEL_X86_64_64_R_V01.02.21.00
SMMAGT_CGEL_X86_64_64_R_V01.02.21.00
OAMAGT_CGEL_X86_64_64_R_V01.02.21.00
OSS_CGEL_X86_64_64_R_V01.02.21.00
FMM_CGEL_X86_64_64_R_V01.02.21.00
DBMS_CGEL_X86_64_64_R_V01.02.21.00
ATMMP_CGEL_X86_64_64_R_V01.02.21.00
SBCO_FEUDS_CGEL_X86_64_64_R_V01.02.21 or
SBCJ_FEUDS_CGEL_X86_64_64_R_V01.02.21.00

SIPI SMMAGT_CGEL_X86_64_64_R_V01.02.21.00
OAMAGT_CGEL_X86_64_64_R_V01.02.21.00
OSS_CGEL_X86_64_64_R_V01.02.21.00
FMM_CGEL_X86_64_64_R_V01.02.21.00
DBMS_CGEL_X86_64_64_R_V01.02.21.00
EPU_CGEL_X86_64_64_R_V01.02.21.00

DBIO EPU_CGEL_X86_64_64_R_V01.02.21.00
SMMAGT_CGEL_X86_64_64_R_V01.02.21.00
OAMAGT_CGEL_X86_64_64_R_V01.02.21.00
OSS_CGEL_X86_64_64_R_V01.02.21.00
FMM_CGEL_X86_64_64_R_V01.02.21.00
DBMS_CGEL_X86_64_64_R_V01.02.21.00
SMM_CGEL_X86_64_64_R_V01.02.21.00
SBCO_DBIO_CGEL_X86_64_64_R_V01.02.21.00 or
SBCJ_DBIO_CGEL_X86_64_64_R_V01.02.21.00

Interface processor EPU_CGEL_X86_64_64_R_V01.02.21.00

SMMAGT_CGEL_X86_64_64_R_V01.02.21.00
OAMAGT_CGEL_X86_64_64_R_V01.02.21.00
OSS_CGEL_X86_64_64_R_V01.02.21.00
FMM_CGEL_X86_64_64_R_V01.02.21.00
DBMS_CGEL_X86_64_64_R_V01.02.21.00
SMM_CGEL_X86_64_64_R_V01.02.21.00
SBCO_HLRMI_CGEL_X86_64_64_R_V01.02.21.00 or
SBCJ_HLRMI_CGEL_X86_64_64_R_V01.02.21.00

B-4

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Appendix B Service Set Check

Module/Unit Service Types

DSA EPU_CGEL_X86_64_64_R_V01.02.21.00
SMM_CGEL_X86_64_64_R_V01.02.21.00
SMMAGT_CGEL_X86_64_64_R_V01.02.21.00
OAMAGT_CGEL_X86_64_64_R_V01.02.21.00
OSS_CGEL_X86_64_64_R_V01.02.21.00
FMM_CGEL_X86_64_64_R_V01.02.21.00
DBMS_CGEL_X86_64_64_R_V01.02.21.00
SBCO_UDS_CGEL_X86_64_64_R_V01.02.21.00 or
SBCJ_UDS_CGEL_X86_64_64_R_V01.02.21.00

DST SODAMGR
RSMM_CGEL_X86_64_64_R_V01.02.21.00
UDS_CGEL_X86_64_64_R_V01.02.21.00
EPU_CGEL_X86_64_64_R_V01.02.21.00
SMMAGT_CGEL_X86_64_64_R_V01.02.21.00
OAMAGT_CGEL_X86_64_64_R_V01.02.21.00
OSS_CGEL_X86_64_64_R_V01.02.21.00
FMM_CGEL_X86_64_64_R_V01.02.21.00
DBMS_CGEL_X86_64_64_R_V01.02.21.00
SMM_CGEL_X86_64_64_R_V01.02.21.00

SWBB_SWITCH SODAMGR
USCC_RSMM_CGEL_83XX_32_R_V01.02.21.00
SMMAGT_CGEL_83XX_32_R_V01.02.21.00
OAMAGT_CGEL_83XX_32_R_V01.02.21.00
OSS_CGEL_83XX_32_R_V01.02.21.00
FMM_CGEL_83XX_32_R_V01.02.21.00
DBMS_CGEL_83XX_32_R_V01.02.21.00
SWITCH_CGEL_83XX_32_R_V01.02.21.00

B-5

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

This page intentionally left blank.

B-6

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Appendix C
Network Adaptors of
Processing Blades
The blades that need the patch for renaming network adaptors can work properly only after
the patch is installed. And when such a blade works properly, you can use the network
adaptor names that you have renamed as.

Note:
l Rear-board network ports 1–4 are the four network ports (from the top down) on the
rear board.
l Base and Fabric plane network ports are internal network ports, and can also
communicate externally through the network ports on a rear board of switching board.
l Base network port 0 can communicate with the Base network port on the switching
board in slot 7.
l Base network port 1 can communicate with the Base network port on the switching
board in slot 8.
l Fabric network port 0 can communicate with the Fabric network port on the switching
board in slot 7.
l Fabric network port 1 can communicate with the Fabric network port on the switching
board in slot 8.
l Update-plane network ports are reserved.

C-1

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Table C-1 Network Adaptors of Processing Blades

Blade Rear Network Adaptor Network Port Type Bus Information Network
Type board Name Adaptor
S.N. (Not renamed) Name
(Renamed)

DPBX0 RSB11_0 eth0 Rear-board network 05:00.0 No need to

90300_R5 port 1 install the
patch for
eth1 Rear-board network 05:00.1
renaming
port 2
network
eth2 Rear-board network 06:00.0
adaptors
port 3

eth3 Rear-board network 06:00.1

port 4

eth4 Fabric network port 0 0b:00.0

eth5 Fabric network port 1 0b:00.1

eth6 Base network port 0 0c:00.0

eth7 Base network port 1 0c:00.1

RSB11_0 eth0 Fabric network port 0 0b:00.0 eth4

90500_R5
eth1 Fabric network port 1 0b:00.1 eth5

eth2 Base network port 0 0c:00.0 eth6

eth3 Base network port 1 0c:00.1 eth7

eth4 Rear-board network 05:00.0 eth0

port 1

eth5 Rear-board network 05:00.1 eth1

port 2

eth6 Rear-board network 06:00.0 eth2

port 3

eth7 Rear-board network 06:00.1 eth3

port 4

OPBA1 RSB11_0 eth0 Rear-board network 06:00.0 No need to

90300_R5 port 1 install the
patch for
eth1 Rear-board network 06:00.1
renaming
port 2
network
eth2 Rear-board network 07:00.0
adaptors
port 3

eth3 Rear-board network 07:00.1

port 4

C-2

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

 Appendix C Network Adaptors of Processing Blades

Blade Rear Network Adaptor Network Port Type Bus Information Network
Type board Name Adaptor
S.N. (Not renamed) Name
(Renamed)

eth4 Fabric network port 0 0c:00.0

eth5 Fabric network port 1 0c:00.1

eth6 Base network port 0 0d:00.0

eth7 Base network port 1 0d:00.1

RSB11_0 eth0 Fabric network port 0 0c:00.0 eth4

90500_R5
eth1 Fabric network port 1 0c:00.1 eth5

eth2 Base network port 0 0d:00.0 eth6

eth3 Base network port 1 0d:00.1 eth7

eth4 Rear-board network 06:00.0 eth0

port 1

eth5 Rear-board network 06:00.1 eth1

port 2

eth6 Rear-board network 07:00.0 eth2

port 3

eth7 Rear-board network 07:00.1 eth3

port 4

DPBX1/ RSB11_0 eth0 Update-plane network 03:00.0 eth8

OPBB1 90300_R5 port 0

eth1 Update-plane network 03:00.1 eth9

port 1

eth2 Fabric network port 0 04:00.0 eth4

eth3 Fabric network port 1 04:00.1 eth5

eth4 Rear-board network 09:00.0 eth0

port 1

eth5 Rear-board network 09:00.1 eth1

port 2

eth6 Rear-board network 0a:00.0 eth2

port 3

eth7 Rear-board network 0a:00.1 eth3

port 4

eth8 Base network port 0 0d:00.0 eth6

eth9 Base network port 1 0d:00.1 eth7

C-3

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

ZXUN USPP Software Installation Guide

Blade Rear Network Adaptor Network Port Type Bus Information Network
Type board Name Adaptor
S.N. (Not renamed) Name
(Renamed)

RSB11_0 eth0 Update-plane network 03:00.0 eth8

90500_R5 port 0

eth1 Update-plane network 03:00.1 eth9

port 1

eth2 Fabric network port 0 04:00.0 eth4

eth3 Fabric network port 1 04:00.1 eth5

eth4 Base network port 0 0d:00.0 eth6

eth5 Base network port 1 0d:00.1 eth7

eth6 Rear-board network 09:00.0 eth0

port 1

eth7 Rear-board network 09:00.1 eth1

port 2

eth8 Rear-board network 0a:00.0 eth2

port 3

eth9 Rear-board network 0a:00.1 eth3

port 4

C-4

SJ-20110105143446-003|2011-07-27(R1.3) ZTE Proprietary and Confidential

Figures
Figure 1-1 ZXUN USPP System Architecture............................................................ 1-1
Figure 1-2 PROVISION Subsystem Structure ........................................................... 1-3
Figure 1-3 UDS Subsystem Architecture................................................................... 1-4
Figure 1-4 Architecture of Network Element Management Subsystem (Distributed
Networking) ............................................................................................ 1-5
Figure 1-5 Architecture of Network Element Management Subsystem
(Single-Layer Networking)....................................................................... 1-6
Figure 1-6 Software Installation Flow ...................................................................... 1-18
Figure 2-1 Login ..................................................................................................... 2-16
Figure 2-2 Server Environment ............................................................................... 2-17
Figure 2-3 Parameters ............................................................................................ 2-18
Figure 2-4 Parameters Configuration ...................................................................... 2-20
Figure 2-5 Settings ................................................................................................. 2-24
Figure 2-6 Login ..................................................................................................... 2-25
Figure 2-7 OMM Main Page.................................................................................... 2-27
Figure 3-1 Select Installation Style ............................................................................ 3-5
Figure 3-2 Network Scale ......................................................................................... 3-6
Figure 3-3 Installation Product .................................................................................. 3-7
Figure 3-4 Database Connection Configuration......................................................... 3-8
Figure 3-5 Database Configuration ........................................................................... 3-9
Figure 3-6 Host Information Configuration................................................................. 3-9
Figure 3-7 System Information Detection ................................................................ 3-10
Figure 3-8 Parameter Settings ................................................................................ 3-11
Figure 3-9 CN NAF Parameter Settings .................................................................. 3-14
Figure 3-10 Clock Server Parameter Settings ......................................................... 3-15
Figure 3-11 the EMS server Console ...................................................................... 3-17
Figure 3-12 Select Installation Style ........................................................................ 3-19
Figure 3-13 Installation Product .............................................................................. 3-20
Figure 3-14 System Information Detection .............................................................. 3-21
Figure 3-15 Parameter Settings .............................................................................. 3-22
Figure 3-16 Clock Server Parameter Settings ......................................................... 3-23
Figure 3-17 EMS Client Shortcut............................................................................. 3-24

I
ZXUN USPP Software Installation Guide

Figure 3-18 Login Dialog Box of EMS Client ........................................................... 3-25

Figure 3-19 NetNumen Unified Management System (EMS Client)......................... 3-26
Figure 3-20 EMS Client Portal Shortcut .................................................................. 3-27
Figure 3-21 Login Dialog Box of EMS Client Portal ................................................. 3-27
Figure 3-22 Portal ................................................................................................... 3-28
Figure 4-1 License Imported Successfully................................................................. 4-3
Figure 4-2 CREATE USPP Command Configuration Interface .................................. 4-4
Figure 4-3 Create NE Agent...................................................................................... 4-5
Figure 4-4 Start the OMM ......................................................................................... 4-7
Figure 4-5 NE Agent Node on the NE Tree ............................................................... 4-7
Figure 4-6 UPDATE USPP Command Configuration Interface .................................. 4-9
Figure 4-7 Synchronization License Info ................................................................. 4-10
Figure 4-8 ADD USPPNE Command Configuration Interface.................................. 4-11
Figure 4-9 An Example of AMO Name .................................................................... 4-12
Figure 5-1 DTF Window............................................................................................ 5-4
Figure 5-2 DHCP Options ......................................................................................... 5-5
Figure 5-3 Board Options.......................................................................................... 5-6
Figure 5-4 Start Up DHCP Server ............................................................................. 5-7
Figure 5-5 FTP Server .............................................................................................. 5-7
Figure 5-6 FTP Options ............................................................................................ 5-8
Figure 5-7 Start Up FTP Server ................................................................................ 5-9
Figure 5-8 SET OMP Command Interface............................................................... 5-17
Figure 5-9 LOAD PKG Command Interface ............................................................ 5-18
Figure 5-10 ENABLE APTPKG Command Interface ............................................... 5-19
Figure 5-11 SHOW RUNPKG Command Interface.................................................. 5-19
Figure 5-12 SYNA Command Interface ................................................................... 5-20
Figure 5-13 SET BOOTMODE Command Interface ................................................ 5-21
Figure 5-14 SET OMP Command Interface............................................................. 5-22
Figure 5-15 SYNA Command Interface ................................................................... 5-22
Figure 5-16 SET OMP Command Interface............................................................. 5-23
Figure 5-17 ENABLE APTPKG Command Interface ............................................... 5-26
Figure 5-18 SHOW RUNPKG Command Interface.................................................. 5-26
Figure 5-19 ENABLE APTPKG Command Interface ............................................... 5-27
Figure 5-20 SHOW RUNPKG Command Interface.................................................. 5-28
Figure 5-21 ENABLE APTPKG Command Interface ............................................... 5-31

II
 Figures

Figure 5-22 SHOW RUNPKG Command Interface.................................................. 5-32

Figure 7-1 Agent-DBIO Interaction ............................................................................ 7-1
Figure 7-2 Agent-DBIO Interaction Through a Secondary Forwarding Module ........... 7-1
Figure 7-3 Web Agent Structure................................................................................ 7-2
Figure 7-4 Please Select Language .......................................................................... 7-6
Figure 7-5 Welcome to Use the Software.................................................................. 7-7
Figure 7-6 Please Select Product Module ................................................................. 7-7
Figure 7-7 ................................................................................................................ 7-8
Figure 7-8 HLRAgent: tcpseek3g.ini ......................................................................... 7-9
Figure 7-9 Localnfo................................................................................................... 7-9
Figure 7-10 RemoteInfo .......................................................................................... 7-10
Figure 7-11 HLR Agent ........................................................................................... 7-14
Figure 7-12 Agent System ...................................................................................... 7-14
Figure 7-13 Interception Instance............................................................................ 7-19
Figure 7-14 Login Window ...................................................................................... 7-22
Figure 8-1 Disk Information with a Mirrored Disk ....................................................... 8-4
Figure 8-2 Disk Information without Mirrored Disk ..................................................... 8-4
Figure 8-3 Boot Information ...................................................................................... 8-4
Figure 8-4 SAS BIOS................................................................................................ 8-4
Figure 8-5 Hard Disk Properties................................................................................ 8-5
Figure 8-6 RAID Setting............................................................................................ 8-5
Figure 8-7 Create New Array-No RAID ..................................................................... 8-6
Figure 8-8 Notification for Creating New Array .......................................................... 8-6
Figure 8-9 Create New Array – With the Primary Disk Set ........................................ 8-7
Figure 8-10 Create New Array – With the Primary and Secondary Disks Set ............ 8-7
Figure 8-11 Operation Prompt................................................................................... 8-8
Figure 8-12 Boot Information .................................................................................. 8-10
Figure 8-13 Modifying System Time ........................................................................ 8-10
Figure 8-14 Exit Tab................................................................................................ 8-11
Figure 8-15 Confirmation Dialogue Box .................................................................. 8-11
Figure 8-16 Confirmation for Exiting........................................................................ 8-12
Figure 8-17 Boot Information .................................................................................. 8-13
Figure 8-18 List of Available Boot Devices .............................................................. 8-13
Figure 8-19 Media Test ........................................................................................... 8-14
Figure 8-20 Media Check........................................................................................ 8-15

III
ZXUN USPP Software Installation Guide

Figure 8-21 Language Selection ............................................................................. 8-15

Figure 8-22 Media Check Result............................................................................. 8-16
Figure 8-23 Whether to Check another CD ............................................................. 8-16
Figure 8-24 Language Selection ............................................................................. 8-17
Figure 8-25 Partitioning Type .................................................................................. 8-17
Figure 8-26 Review Partition Layout ....................................................................... 8-18
Figure 8-27 Add Partition ........................................................................................ 8-19
Figure 8-28 Network Configuration ......................................................................... 8-21
Figure 8-29 Hostname Configuration ...................................................................... 8-22
Figure 8-30 Root Password .................................................................................... 8-22
Figure 8-31 Package Installation............................................................................. 8-23
Figure 8-32 Whether Install Third-Party Application ................................................ 8-23
Figure 8-33 Complete ............................................................................................. 8-24
Figure 8-34 Editing inittab ....................................................................................... 8-26
Figure 8-35 Date/Time Properties ........................................................................... 8-27
Figure 8-36 Date/Time Properties- Time Zone ........................................................ 8-28
Figure 8-37 CGSL Integrated Configuration Tool..................................................... 8-33
Figure 8-38 NIC Bonding Management Tool ........................................................... 8-34
Figure 8-39 Create New Bonding............................................................................ 8-34
Figure 8-40 Network Configuration ......................................................................... 8-36
Figure 8-41 Ethernet Device ................................................................................... 8-37
Figure 8-42 Add new Device Type .......................................................................... 8-38
Figure 8-43 Configure Network Settings.................................................................. 8-39
Figure 8-44 Network Configuration ......................................................................... 8-40
Figure 8-45 Ethernet Device–Route ........................................................................ 8-41
Figure 8-46 Add / Edit IP Address........................................................................... 8-41
Figure 9-1 Contents of the sysctl File ........................................................................ 9-4
Figure 9-2 Configuration Check ................................................................................ 9-4
Figure 9-3 Select Installation Method ........................................................................ 9-8
Figure 9-4 Specify Inventory Directory and Credentials............................................. 9-9
Figure 9-5 Select Installation Type ............................................................................ 9-9
Figure 9-6 Specify Home Details............................................................................. 9-10
Figure 9-7 Product-Specific Prerequisite Checks .................................................... 9-11
Figure 9-8 Select Configuration Option ................................................................... 9-11
Figure 9-9 Summary ............................................................................................... 9-12

IV
 Figures

Figure 9-10 Execute Configuration Scripts .............................................................. 9-13

Figure 9-11 Specify Home Details ........................................................................... 9-15
Figure 9-12 Product-Specific Prerequisite Checks .................................................. 9-16
Figure 9-13 Oracle Configuration Manager Registration.......................................... 9-17
Figure 9-14 Summary ............................................................................................. 9-17
Figure 9-15 Execute Configuration Script................................................................ 9-18
Figure 9-16 Operations ........................................................................................... 9-20
Figure 9-17 Database Templates ............................................................................ 9-21
Figure 9-18 Database Identification......................................................................... 9-21
Figure 9-19 Management Options........................................................................... 9-22
Figure 9-20 Database Credentials .......................................................................... 9-22
Figure 9-21 Storage Options................................................................................... 9-23
Figure 9-22 Database File Locations....................................................................... 9-23
Figure 9-23 Recovery Configuration........................................................................ 9-24
Figure 9-24 Database Content ................................................................................ 9-24
Figure 9-25 Standard Database Components ......................................................... 9-25
Figure 9-26 Initialization Parameters....................................................................... 9-26
Figure 9-27 All Initialization Parameters-Show Advanced Parameters .................... 9-27
Figure 9-28 Database Storage ................................................................................ 9-28
Figure 9-29 Creation Options.................................................................................. 9-28
Figure 9-30 Oracle Net Configuration Assistant: Welcome...................................... 9-29
Figure 9-31 Listener................................................................................................ 9-30
Figure 9-32 Listener Name ..................................................................................... 9-30
Figure 9-33 Select Protocols................................................................................... 9-31
Figure 9-34 TCP/IP Protocol ................................................................................... 9-31
Figure 9-35 More Listeners ..................................................................................... 9-32
Figure 9-36 Oracle Net Manager............................................................................. 9-33
Figure 9-37 LISTENER Configuration ..................................................................... 9-33
Figure 9-38 Welcome.............................................................................................. 9-35
Figure 9-39 Net Service Name Configuration .......................................................... 9-35
Figure 9-40 Setting a Service Name ....................................................................... 9-36
Figure 9-41 Selecting a Protocol ............................................................................. 9-36
Figure 9-42 TCP/IP Configuration ........................................................................... 9-37
Figure 9-43 Connection Test ................................................................................... 9-37
Figure 9-44 Setting Net Service Name.................................................................... 9-38

V
ZXUN USPP Software Installation Guide

Figure 9-45 Whether to Set Another Net Service Name .......................................... 9-38
Figure A-1 Connect to Server ...................................................................................A-2
Figure A-2 Authentication Required ..........................................................................A-2
Figure A-3 Quick Connect.........................................................................................A-4
Figure A-4 Enter Secure Shell Password ..................................................................A-5
Figure A-5 Xbroswer .................................................................................................A-6
Figure A-6 CGSL GUI ...............................................................................................A-7
Figure A-7 WinSCP Login .........................................................................................A-8
Figure A-8 Logged In to CGSL..................................................................................A-9
Figure A-9 Internet Protocol (TCP/IP) Properties ....................................................A-12
Figure A-10 Advanced TCP/IP Settings ..................................................................A-13
Figure A-11 TCP/IP Address ...................................................................................A-13
Figure B-1 Structure of Service Set...........................................................................B-1

VI
Tables
Table 1-1 IP Address Planning .................................................................................. 1-9
Table 1-2 Physical IP Address Planning for Network Interfaces of DST................... 1-14
Table 1-3 Route Planning........................................................................................ 1-15
Table 1-4 IP Addresses of the Debugging PC ......................................................... 1-17
Table 2-1 OMM Server Hardware Requirements ....................................................... 2-1
Table 2-2 OMM Server Software Requirements ........................................................ 2-2
Table 2-3 OMM Client Hardware Requirements ........................................................ 2-2
Table 2-4 OMM Client Software Requirements.......................................................... 2-3
Table 2-5 OMM Software Installation Flow ................................................................ 2-3
Table 2-6 Preparations before OMM Software Installation ......................................... 2-4
Table 2-7 OMM Login Parameters .......................................................................... 2-17
Table 2-8 OMM Server Installation Parameters ....................................................... 2-18
Table 2-9 OMM Server Address Parameters ........................................................... 2-25
Table 2-10 OMM Login Parameters......................................................................... 2-26
Table 3-1 EMS Server Hardware Requirements........................................................ 3-1
Table 3-2 EMS Server Software Requirements ......................................................... 3-2
Table 3-3 EMS Client Hardware Requirements ......................................................... 3-2
Table 3-4 EMS Client Software Requirements........................................................... 3-2
Table 3-5 EMS Server Software Installation Flow ...................................................... 3-3
Table 3-6 EMS Client Software Installation Flow ....................................................... 3-3
Table 3-7 Parameters for Database Connection Configuration .................................. 3-8
Table 3-8 Parameters for Host Configuration .......................................................... 3-10
Table 3-9 Description for Parameters Involved in Login Dialog Box......................... 3-25
Table 3-10 Description for Parameters Involved in Login Dialog Box ....................... 3-27
Table 3-11 Description for Functional Modules ........................................................ 3-28
Table 4-1 Flow of OMM Access Configuration........................................................... 4-1
Table 4-2 CREATE USPP Command Parameters ..................................................... 4-4
Table 4-3 Parameters for Creating an NE Agent ....................................................... 4-5
Table 4-4 ADD USPPNE Command Parameters..................................................... 4-11
Table 5-1 Version Loading Flow ................................................................................ 5-1
Table 5-2 Parameters of DHCP Options................................................................... 5-5
Table 5-3 Parameters of Board Options .................................................................. 5-6

VII
ZXUN USPP Software Installation Guide

Table 5-4 Settings of FTP Options ............................................................................ 5-8

Table 5-5 OMP Idicators ......................................................................................... 5-11
Table 5-6 Blades and Version Packages ................................................................. 5-16
Table 5-7 Operations for Package Loading ............................................................. 5-18
Table 5-8 SYNA Command Interface ...................................................................... 5-20
Table 5-9 SYNA Command Interface ...................................................................... 5-22
Table 6-1 HSM Hardware Requirements ................................................................... 6-2
Table 6-2 HSM Software Requirement ...................................................................... 6-2
Table 6-3 HSM Software Installation Flow ................................................................. 6-3
Table 6-4 Remoteinfo Parameters........................................................................... 6-18
Table 7-1 Agent Hardware Configuration Requirements............................................ 7-2
Table 7-2 Agent Software Configuration Requirements ............................................. 7-3
Table 7-3 Web Agent Installation Flow ...................................................................... 7-4
Table 7-4 Parameter Description of Remote Node Information................................ 7-10
Table 7-5 Function Description................................................................................ 7-11
Table 7-6 Data Configuration Check Items on Web Agent Server............................ 7-16
Table 7-7 Descriptions of Web Agent Address Parameters ..................................... 7-22
Table 7-8 Login Parameters Description.................................................................. 7-22
Table 8-1 Requirements for the Installing Operating System ..................................... 8-2
Table 8-2 CGSL Installation Flow .............................................................................. 8-2
Table 8-3 Partition Parameters................................................................................ 8-19
Table 8-4 Requirements for Partitions ..................................................................... 8-20
Table 8-5 Partition Settings for OMM Server ........................................................... 8-20
Table 8-6 Partition Settings for EMS Server ............................................................ 8-20
Table 8-7 Requirements for Character Set .............................................................. 8-30
Table 8-8 Parameters for Binding Network Adaptors ............................................... 8-35
Table 9-1 Requirements for Installing Oracle............................................................. 9-1
Table 9-2 Oracle Installation Flow ............................................................................. 9-2
Table 9-3 Settings of Environment Variables for User oracle ..................................... 9-6
Table 9-4 Description for Parameters of Database 1 ............................................... 9-34
Table A-1 Authentication Parameters ........................................................................A-3
Table A-2 SecureCRT Parameters ............................................................................A-4
Table A-3 WinSCP Login Parameters .......................................................................A-8
Table B-1 Service Types of Each Module and Unit ....................................................B-3
Table C-1 Network Adaptors of Processing Blades .................................................. C-2

VIII
Glossary
AAL5
- ATM Adaptation Layer type 5
AMO
- Access Managed Object
ATCA
- Advanced Telecommunications Computing Architecture
BIOS
- Basic Input/Output System
BOSS
- Business and Operation Support System
CD-ROM
- Compact Disc-Read Only Memory
CGEL
- Commuication Grade Embedded Linux
CGSL
- Carrier Grade Server Linux

CMM
- Chassis Management Module

CMP
- Calling Main Processor
CPU
- Central Processing Unit
DBIO
- DataBase Input & Output
DHCP
- Dynamic Host Configuration Protocol
DMCC
- Distributed Monitoring and Control Center
DRSync
- Disaster Reserved Sync

DSA
- Directory System Agent
DST
- Data Storage Transfer

IX
ZXUN USPP Software Installation Guide

EMS
- Network Element Management System
ETCA
- Enhanced ATCA
FE
- Front End
FTP
- File Transfer Protocol
GUI
- Graphical User Interface
HSM
- Hardware Security Module
ICC
- Inspect and Control Center
IDSA
- Identity DSA

IP
- Internet Protocol
JRE
- Java Runtime Environment
JSP
- Java Server Pages
MAP
- Mobile Application Part
MTP3
- Message Transfer Part layer 3
MTP3B
- B-ISDN Message Transfer Part level 3

NCMM
- New Chassis Management Module
NE
- Network Element
NIC
- Network Interface Card
NMS
- Network element Management System

NTP
- Network Time Protocol

X
 Glossary

O&M
- Operation & Maintenance
OMM
- Operation & Maintenance Module
OMP
- Operation & Maintenance Processor
OS
- Operating System
OSS
- Operation Support System
PC
- Personal Computer
PCI
- Peripheral Component Interconnect
PDSA
- Profile DSA

PED
- PIN Entry Device
PID
- Process Identifier
RAM
- Random Access Memory
RPU
- Router Process Unit
SAS
- Serial Attachment SCSI
SCTP
- Stream Control Transmission Protocol

SID
- System IDentifier
SIPI
- Signaling IP bearer Interface
SLB
- Service Load Balancing
SMP
- Signal Main Processor

SN
- Serial Number

XI
ZXUN USPP Software Installation Guide

SNMP
- Simple Network Management Protocol
SNTP
- Simple Network Time Protocol
SQL
- Structured Query Language
SS7
- Signaling System No. 7
SSH
- Secure Shell
TCP
- Transfer Control Protocol
TCP/IP
- Transfer Control Protocol/Internet Protocol
TDM
- Time Division Multiplexing

UDS
- Universal Directory Server
USPP
- Universal Subscriber Profile Platform
UTC
- Universal Time Coordinated
XDMCP
- X Display Manager Control Protocol
ZTE
- Zhongxing Telecommunications Equipment

XII