SJ-20141110151550-018-ZXSDR UniRAN TDD-LTE (V3.20.50) Call Data Tracing Operation Guide

ZXSDR OMMB
Software Installation Guide

Version: V12.13.62
ZTE CORPORATION
No. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://support.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright 2015 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 the ZTE technical support website http://support.zte.com.cn to inquire for related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No.
Revision Date
Revision Reason
R1.0
2015-05-10
First Edition
Serial Number: SJ-20150317102154-002

Publishing Date: 2015-05-10 (R1.0)
SJ-20150317102154-002|2015-05-10 (R1.0)
ZTE Proprietary and Confidential
Contents
About This Manual ......................................................................................... I
Chapter 1 Software Installation Content .................................................. 1-1
Chapter 2 Installation Procedure .............................................................. 2-1
Chapter 3 Installation Preparations .......................................................... 3-1
3.1 System Requirements ........................................................................................ 3-1
3.2 Making Installation Preparations in Linux ............................................................. 3-2
3.3 Making Installation Preparations in Solaris ........................................................... 3-4
3.4 Installation Precautions....................................................................................... 3-5
Chapter 4 Installing the OMMB System.................................................... 4-1

4.1 Performing Initial Installation ............................................................................... 4-1
4.2 Performing Upgrade Installation ........................................................................ 4-16
4.3 Installing updateAgent ...................................................................................... 4-18
Chapter 5 Starting the OMMB System...................................................... 5-1

Chapter 6 Performing Automatic Client Upgrade.................................... 6-1
Appendix A Uninstalling the OMMB System .......................................... A-1
Figures............................................................................................................. I
Tables ............................................................................................................ III
Glossary .........................................................................................................V
I
SJ-20150317102154-002|2015-05-10 (R1.0)
This page intentionally left blank.
II
SJ-20150317102154-002|2015-05-10 (R1.0)
About This Manual

Purpose
This manual describes how to install the ZXSDR OMMB software.
Intended Audience
This manual is intended for:
l
l
Installation supervision engineers

Commissioning engineers
Prerequisite Skills and Knowledge

Familiarity with the following is required/helpful:
l
l
Basic operations of the SUSE Linux/Solaris system

Basic operations of the Oracle database
What Is in This Manual

This manual contains the following chapters and appendix.
Chapter 1, Software Installation
Describes the ZXSDR OMMB software installation content.
Content
Chapter 2, Installation Procedure
Describes the ZXSDR OMMB software installation procedure.
Chapter 3, Installation
Describes the ZXSDR OMMB software installation preparations.
Preparations
Chapter 4, Installing the OMMB
Describes how to install, and upgrade the ZXSDR OMMB system.
System
Chapter 5, Starting the OMMB
Describes how to start the ZXSDR OMMB server and client.
System
Chapter 6, Performing Automatic
Describes how to perform automatic client upgrade.
Client Upgrade
A, Uninstalling the OMMB
Describes how to uninstall the OMMB system.
System
Conventions
This manual uses the following conventions.
Note: provides additional information about a certain topic.
I
SJ-20150317102154-002|2015-05-10 (R1.0)
II
SJ-20150317102154-002|2015-05-10 (R1.0)
Chapter 1
Software Installation Content

Software to be Installed on the Server
l
l
l
Operating systems:
Linux: SUSE, RED HAT, and CGSL
Solaris
Windows: Windows Server 2003
Database:
Oracle database 11.2.0.3.0
SQL Server 2005
SQL Server 2008
SybaseIQ 15.4
Antivirus software
ZXSDR OMMB server software
Software to be Installed on the Client

l
l
l
Operating systems: Windows XP and Windows Server 2003

Antivirus software
ZXSDR OMMB client software
Software Tools
For the software tools to be used during installation and maintenance, refer to Table 1-1.
Table 1-1 Software Tools
Software
Function
VNC
Remote management tool
CuteFTP
Download tool
winScp
Download tool
1-1
SJ-20150317102154-002|2015-05-10 (R1.0)
ZXSDR OMMB Software Installation Guide
1-2
SJ-20150317102154-002|2015-05-10 (R1.0)
Chapter 2
Installation Procedure
For the initial installation procedure of the ZXSDR OMMB server, see Figure 2-1.
Figure 2-1 Initial Installation Procedure of the ZXSDR OMMB Server
2-1
SJ-20150317102154-002|2015-05-10 (R1.0)
2-2
SJ-20150317102154-002|2015-05-10 (R1.0)
Chapter 3
Installation Preparations
Table of Contents
System Requirements ................................................................................................3-1
Making Installation Preparations in Linux....................................................................3-2
Making Installation Preparations in Solaris .................................................................3-4
Installation Precautions ..............................................................................................3-5
3.1 System Requirements

For the ZXSDR OMMB client and server requirements for operating systems, refer to Table
3-1.
Table 3-1 Requirements for Operating Systems
Operating System
Linux
File System
Whether the OS
Whether the OS
supports the
supports the
server
client
SUSE
SLES 11 sp1
EXT3
Yes
No
RED HAT
4.5/4.7
EXT3
Yes
No
CGSL
V3
EXT3
Yes
No
Solaris 10 U10
UFS
Yes
No
SP3
NTFS/FAT32
No
Yes
SP2
NTFS
Yes
Yes
Solaris
Windows
Version
Windows
XP
Windows
Server
2003
For the database types supported by the ZXSDR OMMB server, refer to Table 3-2.
Table 3-2 ZXSDR OMMB Server Requirements for Databases
Database
Version
The operating system supports the

database
Oracle
Oracle 10g or later.
Linux
Oracle 11.2.0.3.0 is recommended.
Solaris
Windows Server 2003
SQL Server
SQL Server 2005, SQL Server 2008.
Windows Server 2003
3-1
SJ-20150317102154-002|2015-05-10 (R1.0)
3.2 Making Installation Preparations in Linux

This procedure describes preparations for installing the ZXSDR OMMB in Linux.
Steps
1. Close the hosts cache function in Linux.
Before installing the ZXSDR OMMB in Linux, you must close the cache function of the
hosts, so that the ZXSDR OMMB can acquire the IP address of the server.
This operation is not required in Solaris.
a. Use the root account to log in to the Linux system.
b. Use the text editor to open the /etc/nscd.conf file, and change the
enable-cache hosts yes parameter to enable-cache hosts no.
c.
Restart the nscd service.

l In the SUSE and CGSL systems, execute the rcnscd restart command on
the command terminal to restart the nscd service. The result is displayed as
follows:
#rcnscd restart
Shutting down Name Service Cache Daemon
done
Starting Name Service Cache Daemon
done
In the RED HAT system, execute the service nscd restart command on the
command terminal to restart the nscd service. The result is displayed as
follows:
#service nscd restart
Shutting down Name Service Cache Daemon
done
Starting Name Service Cache Daemon
done
2. Create an omc account and assign permissions to this account.

It is recommended to log in to OMMB by using the omc account from a security
perspective. If the omc account exists, skip this step.
a. Log in to the Linux system by using the root account, and execute the following
command on the command terminal to create an omc account.
#useradd -d /home/omc -m -G dba omc
#chown -R omc/home/omc
b. Execute the following command on the command terminal, and enter a new
password for the omc account.
#passwd omc
Changing password for omc.
New Password:
Reenter New Password:
Password changed.
3-2
SJ-20150317102154-002|2015-05-10 (R1.0)
Chapter 3 Installation Preparations
l
l
l
Note:
The length of the password must be no less than six characters.
The password must contain digits, capital letters, and lowercase letters.
The password must not contain more than four continuous digits or letters, for
example, 12345* or abcde*.
3. Obtain the ZXSDR OMMB installation package.

a. Use the omc account to log in to the Linux system.
b. Enter the /home/omc directory, and create an OMMB-Installer folder.
c.
Use an FTP tool, such as winScp or CuteFTP, to upload the ZXSDR OMMB
installation package in binary mode in the OMMB-Installer folder and unzip it.
If the operating system provides the SFTP service, the ZXSDR OMMB installation
package can be directly uploaded without binary option.
d. Use MD5 code to check whether the package has been damaged or not in the
transmission.
Compute the MD5 code of the package and compare it with the code in the file
MD5.txt. If they are the same, the package is complete, If they are different, the
version must be uploaded again.
The method to calculate MD5 code by taking test.zip for example is shown as
follows.
Execute the following command on the command terminal.
#md5sum test.zip
The MD5 code of test.zip is displayed as follows.

7cffeaab4ffe1848c618537580c24113 test.zip
4. (Optional) Configure the DHCP relay function.
Note:
Before the Linux and Solaris systems assign IP addresses dynamically for NEs through
DHCP, the DHCP relay function must be configured.

b. Enter the /home/omc/OMMB-Installer/Installer/install/tools/dhc
p directory.
c.
Execute the #./dhcp.sh command to start the script file.

3-3
SJ-20150317102154-002|2015-05-10 (R1.0)
d. After the system displays Please input eth name which connects to NE:, enter
the number of the network card that is connected to the base station, for example,
eth0.
The Solaris systems do not require the number of the network card that is
connected to the base station.
If the DHCP relay function has been configured, the command terminal will display
DHCP relay had been configured, input "y" to re-configure it, input "n" to
exit:. To reconfigure the DHCP forwarding function, enter y. To exit, enter n.
5. (Optional) Configure the clock synchronization function.
If clock synchronization is activated in the Linux and Solaris systems, OMMB not only
acquires a clock from the external clock source but also serves as a clock source for
other devices.
To make the operating system provide a clock source for OMMB, execute the NTP
script as follows.
b. Enter the /home/omc/OMMB-Installer/Installer/install/tools/ntp
directory.
c.
Execute the #./ntp.sh 10.9.176.55 command to start the script file.

The IP address of the computer providing the clock source is 10.9.176.55.
If master and slave clock sources are required, use the following command:
#./ntp.sh 10.9.176.5510.9.176.56.
10.9.176.55 is the IP address of the master clock source. 10.9.176.56 is the IP
address of the slave clock source.
Execute the following commands to view the configuration:
#ntpq p
remote
refid
st t when poll reach delay offset jitter
=================================================================
10.9.176.55 10.9.176.56 2
u 23
64
0.310 2.203
0.077
remote is the IP address of NTP server that has responded the request, which is
also the IP address of clock source configured.
refid is the server of higher level than NTP server. If there is no ntp server, Refid
is empty.
End of Steps
3.3 Making Installation Preparations in Solaris

This procedure describes preparations for installing the ZXSDR OMMB in Solaris. The
preparations for installing the ZXSDR OMMB in Solaris are similar in Linux, and then the
difference between the two systems are highlighted.
3-4
SJ-20150317102154-002|2015-05-10 (R1.0)
Chapter 3 Installation Preparations
Steps
1. Create an omc account.
a. Use the root account to log in to the Solaris system.
b. In the command terminal, execute the following commands to create an omc
account.
#mkdir /export/home/omc
#useradd -G dba omc
#chown -R omc /export/home/omc
2. Obtain the ZXSDR OMMB installer.

package in Linux.
For details, refer to Obtain the installation
Validate the MD5 code of the installation package in Solaris

a. Execute the following command on the command terminal.
#digest -v -a md5 test.zip
The MD5 code of test.zip is displayed as follows.

7cffeaab4ffe1848c618537580c24113 test.zip
b. Compare it with the code in the file MD5.txt. If they are the same, the package
is complete, If they are different, the package must be uploaded again.
Note:
In the Solaris system, you can create an OMMB-Installer folder, download the
OMMB installation package, and configure the DHCP relay function and the clock
synchronization function in the /export/home/omc directory.
3. (Optional) Configure the DHCP relay function. For details, refer to Configure the
DHCP relay function in Linux.
4. (Optional) Configure the clock synchronization function. For details, refer to Configure
the Clock Synchronization function in Linux.
End of Steps
3.4 Installation Precautions

l
l
l
When the installation package is uploaded by an FTP tool, the file should be
transferred in binary mode.
To install the ZXSDR OMMB software, use the omc account to log in to the operating
system.
After the ZXSDR OMMB software is installed, do not modify the name or path of the
installation directory. Failure to comply with this can result in upgrade patch installation
failure or configuration modification failure.
3-5
SJ-20150317102154-002|2015-05-10 (R1.0)
3-6
SJ-20150317102154-002|2015-05-10 (R1.0)
Chapter 4
Installing the OMMB System

Table of Contents
Performing Initial Installation.......................................................................................4-1
Performing Upgrade Installation ...............................................................................4-16
Installing updateAgent ..............................................................................................4-18
4.1 Performing Initial Installation

This procedure describes how to install the ZXSDR OMMB software in the Linux system.
Initial installation procedures in Solaris and Windows are similar.
Steps
1. Use the omc account to log in to the operating system.
2. Open the /home/omc/OMMB-Installer/Installer folder, and then double-click
linux-setup.sh to start the installation package. The language selection dialog
box is displayed.
Note:
The installation path in Solaris is /export/home/omc/OMMB-Installer/Instal
ler.
The installation files in Solaris and Windows systems are solaris-setup.sh, and
windows-setup.exe respectively.
3. Select English, see Figure 4-1, and then click Next. The license agreement dialog
box is displayed.
4-1
SJ-20150317102154-002|2015-05-10 (R1.0)
Figure 4-1 Select Language
4. Select I accept the license agreement, and then click Next. The installation type and
installation path selection dialog box is displayed, see Figure 4-2.
4-2
SJ-20150317102154-002|2015-05-10 (R1.0)
Chapter 4 Installing the OMMB System
Figure 4-2 Installation Type and Installation Path Selection Dialog Box
5. Select an installation type and installation path.

a. Select an installation type. For a description of installation types, refer to Table
4-1.
Table 4-1 Installation Type Description
Installation Type
Description
Initial
Installs the OMMB software for the first time or reinstalls the
OMMB software.
Upgrade
Upgrades the OMMB version.
Incremental
Adds radio services.
Patch
Installs patches for the existing OMMB software.
b. Select the installation path. The installation path must be under /home/omc of
the omc account.
4-3
SJ-20150317102154-002|2015-05-10 (R1.0)
l
l
Note:
In Solaris, the installation path must be under the /export/home/omc
directory.
The length of the installation path must not exceed 30 characters, and the
installation path must not contain any spaces.
6. Click Next. The radio standard and installation mode dialog box is displayed, see
Figure 4-3.
Figure 4-3 Radio Standard and Installation Mode Selection Dialog Box
7. Select a radio standard and an installation mode.

a. Under the Radio Standard node, select the radio standards.
b. In the Installation mode area, select an installation mode.
l In Server and client mode, the ZXSDR OMMB software must be installed on
the server that connects NEs to manage NEs.
l In Client mode, the ZXSDR OMMB client can be installed on any computer
that remotely connects the ZXSDR OMMB server to operate and maintain
NEs.
It is recommended that the ZXSDR OMMB client should be installed and run
in the Windows system.
4-4
SJ-20150317102154-002|2015-05-10 (R1.0)
8. Click Next. The database configuration dialog box is displayed, see Figure 4-4.
Figure 4-4 Database Configuration Dialog Box
Note:
If you need to install the client only, the database configurations, OMMB configuration
center configurations, and automatic client upgrade are not required. The environment
detection dialog box can be displayed after you click Next.
9. Select a database type, and then enter proper values in the Database IP, Port, SID,
User, and Password text boxes. For the parameter descriptions, refer to Table 4-2.
Table 4-2 Database Parameters
Parameter
Description
Database type
Supports Oracle and MS SQL Server databases.
Database IP
Enter the IP address of the computer where the database is located.

If the database is located on the computer where the ZXSDR OMMB
software is installed, you can set the database IP address to 127.0.0.1.
Port
For Oracle, the default port is 1521.

For MS SQL Server, the default port is 1433.
4-5
SJ-20150317102154-002|2015-05-10 (R1.0)
Parameter
Description
SID
Enter an instance name of the database.

This procedure uses ommb as an example.
User
Enter the user of the database.

This procedure uses system as an example.
Password
l
l
Enter the password of the database user.
Only the CDMA, TD-LTE, and LTE FDD modes support the MS SQL Server
database.
If you fail to enter the correct password 10 times in succession, the user of
the Oracle database will be locked. In this case, you need to use the sysdba
administrator account to log in to the corresponding instance, and then execute
the alter user system account unlock command in sqlplus to unlock the user. The
operation is as follows:
>export ORACLE_SID=ommb
//Specify the instance to be unlocked.
>sqlplus sys/password as sysdba
//Enter the password of sys.
SQL>alter user system account unlock;
10. Click Next. The environment detection dialog box is displayed, see Figure 4-5.
Figure 4-5 Environment Detection Dialog Box
11. (Optional) If an alarm or warning occurs (see Figure 4-5), make modifications in
accordance with the error or warning information.
4-6
SJ-20150317102154-002|2015-05-10 (R1.0)
The detection result includes the following three states:

l Successful indicates that the detection result meets the installation requirements.
l Warning indicates that differences exist between the detection result and the
installation requirements. For example, the database version is earlier than the
required version. When a warning occurs, you need to fix it before proceeding
with the installation, otherwise the ZXSDR OMMB may not run properly.
l Error indicates that the detection result does not meet the installation
requirements. If an error occurs, you cannot proceed with the installation.
After fixing all warnings, you can click Redetect to perform environment detection
again.
For a description of the warnings, refer to Table 4-3.
Table 4-3 Warnings in Environment Detection
Operation
Detection Criteria
Solution
Remarks
Free space of
Client: The free disk space
Clear the disk space.
To check the disk space,
installation disk for
should be 1 GB or more.
programs/database
execute the df-h command.
Server and client:

l
If the database is installed

on the same disk, the free
disk space should be 3
GB or more.
If the database is not

installed on the same
disk, the free disk space
should be 2 GB or more.
Oracle version
The Oracle version should be
Install a later version of the
To check database version,
11.2.0.3.0 or later.
Oracle database.
execute the select version

from PRODUCT_COMP
ONENT_VERSION where
product like '%Oracle%'
command.
Oracle date format
If the Oracle date format is not
Create a new instance that
Execute the following
YYYY-MM-DD HH24:MI:SS,
complies with the format.
commands:
an alarm is reported.
Oracle character set
If the Oracle character set is

not ZHS16GBK, an alarm is
i.
sqlplus /nolog
ii.
connect
sys/pass-
word@netservicename
reported.
iii. To check the date format:

show parameter
nls_date_format;
iv. To check the character
set:
4-7
SJ-20150317102154-002|2015-05-10 (R1.0)
Operation
Detection Criteria
Solution
Remarks
select userenv('language') from dual;
The password and
netservicename are
the password and network
service name of the
database respectively.
Oracle database
During the installation of a new
free status
OMMB, if an OMMB instance
in use. Close the current
that is running is selected, an
connection or create a new
alarm is reported.
instance.
If the host name is not bound
i.
File of hosts
configuration
The Oracle database is
Execute
the
ifconfig
To check the quantity of
to two IP addresses, an alarm
command to check the
IP addresses, execute the
is reported.
IP configuration. If the
hostname i command.
host name is not bound

to two IP addresses, add
the current IP address.
ii.
Map the host name to

the IP address of the local computer in the /etc
/hosts file, and place it
before the mapping relation of the IP address of
127.0.0.1.
iii. In the Linux system, if

multiple IP addresses
are mapped to the same
host name, write multi
on into the /etc/host
.conf file.
iv. Stop the nscd service.
Hostname
The host name cannot be
Modify the /etc/hosts file.
localhost.
4-8
SJ-20150317102154-002|2015-05-10 (R1.0)
Operation
Detection Criteria
Solution
Remarks
Oracle network
If the Oracle database is
Configure a network service
Execute the tnsping
service name
used, this instance should be
name for this instance.
sid_oracleIP command
properly configured with the
at the command terminal
network service name.
and check whether the

Oracle network service
name is properly fed back.
sid is the Oracle instance
name configured for the
database and oracleIP is the
IP address of the database.
Suse character set
If the OMME (Chinese
Execute the # vi /etc/pr
Execute the locale
version) is installed on Suse,
ofile command with root
command.
an alarm is reported if the
authority.
Suse character set is not
i.
ii.
zh_CN.GBK.
Add export LANG=zh_C

N.GBK at the end of the
file opened, save the file
and exit.
iii. Execute the # source /etc

/profile command.
OS swap space (a
If the system memory
Execute the free b or
special detection
ranges from 0 GB to 4
free g command. The
item for Linux)
GB, the minimum swap
parameter after free is the
space should be 2 GB.
size of swap space.




ranges from 256 GB to
512 GB, the minimum
swap space should be 32
GB.
4-9
SJ-20150317102154-002|2015-05-10 (R1.0)
12. After the environment detection is passed, click Next. The confirmation dialog box is
displayed.
13. Verify that the installation information is correct, and then click Install. When the
installation is completed, the ZXSDR OMMB configuration center dialog box is
displayed, see Figure 4-6.
Figure 4-6 OMMB Configuration Center Dialog Box
l
l
After the ZXSDR OMMB installation is completed, you can modify the database
configuration information in the configuration center.
After the ZXSDR OMMB installation is completed, you can start the configuration
center alone. The startup file is /install/bin/config-linux.sh in the installation path.
In Solaris, and Windows, the startup files are solaris-config.sh, and windowsconfig.exe respectively.
Caution!
In a master/slave scenario, the parameters for both master and slave devices should
be set in the Configuration Center dialog box, and the parameters configured in the
configuration center for the master device must be consistent with those for the slave
device.
4-10
SJ-20150317102154-002|2015-05-10 (R1.0)
14. In the configuration center, complete the following settings.

a. In the left navigation tree, select IP Configuration, and then set the cascade IP
address and the NE IP, see Figure 4-6.
Note:
The cascade IP is used to connect ZXSDR OMMB client or other offices.
The cascade IP supports IPv4 or IPv6.
The NE IP is used to connect ZXSDR OMMB server and NEs.

The NE IP supports both IPv4 and IPv6.
When the base station is commissioned, the NE IP supports only IPv4.
b. (Optional) Select Server Starting Mode Configuration, and then set the server
starting mode, see Figure 4-7.
Figure 4-7 Setting the Server Starting Mode
Server start modes include:

l
l
c.
GUI: When the server is starting, the starting window is displayed.

Non-GUI: The server starts in the back-end only, and the startup window is
not displayed.
Select Server Type Configuration, and set the server type, see Figure 4-8.
4-11
SJ-20150317102154-002|2015-05-10 (R1.0)
l
l
If the ZXSDR OMMB server is installed in SBCX/SBCX_2/SBCJ, you need to

select OMMB Server is installed in SBCX/SBCX_2/SBCJ.
If the master and slave SCBX/SBCX_2/SBCJ boards are configured, you
need to select Master and Slave.
Caution!
The server type is configured based on hardware.
Figure 4-8 Setting the Server Type
d. Select FTP Configuration, and set FTP, see Figure 4-9.

FTP can be configured in a secure or non-secure environment. SFTP provides
secure communication between the ZXSDR OMMB and NEs and between the
ZXSDR OMMB and the upper EMS. You can configure the option based on the
requirement of the field, that is, you can enable either FTP or SFTP. When the
ZXSDR OMMB communicates with NEs, FTP+SFTP can be selected if LTE uses
both V2 and V3 NEs.
4-12
SJ-20150317102154-002|2015-05-10 (R1.0)
Note:
SFTP is a secure FTP protocol based on SSH. SSH is a secure protocol based
on the application layer and transport layer. Currently, SSH is reliable. It ensures
security of Telnet sessions and other network services and effectively avoids
information disclosure during remote management.
Figure 4-9 Setting FTP
e. (Optional) Select License Center IP Configuration, and set license center IP,
see Figure 4-10.
Select the Enable and type the IP address which is used for connecting license
center.
4-13
SJ-20150317102154-002|2015-05-10 (R1.0)
Figure 4-10 Setting the License Center IP
l
l
f.
Note:
If there is only one license center, the IP address of the active license center
is set.
If there are two license centers (active and standby license centers), the IP
addresses of the two license centers are set.
(Optional) Enable NAT configuration. Select NAT Configuration, see Figure 4-11.
Select Start NAT and set IP and Subnet mask according to network planning.
NAT is a technology for accessing a WAN . NAT translates the private (reserved)
addresses into valid IP addresses and enables private networks to access public
networks. NAT can be used for the communication between NEs and the EMS.
NAT must be enabled if NAT devices are used between NEs and the EMS.
Note:
NAT can be configured only when IPv4 is used by the EMS and NE IP.
4-14
SJ-20150317102154-002|2015-05-10 (R1.0)
Figure 4-11 Enabling NAT
g. (Optional) Select DSCP Configuration and configure DSCP, see Figure 4-12.
In the TOS ID byte of the IP header of each packet, DSCP differentiates priority
levels by the code value of used 6 bits and unused 2 bits.
DSCP is used to set the priority level of transmission between NEs and the EMS
according to the user's planning.
l
l
l
Note:
DSCP supports only IPv4. If the cascade IP or NE IP uses IPv6, DSCP cannot
be configured.
DSCP is a required integer parameter ranging from 0 to 63.
DSCP configuration does not support the Windows operating system
currently.
4-15
SJ-20150317102154-002|2015-05-10 (R1.0)
Figure 4-12 Configuring DSCP
15. Click Next. The installation completion window is displayed.

16. Click Finish. The Confirm message box is displayed.
17. (Optional) Create an automatic client upgrade package.
Note:
If the server needs to support automatic client upgrade, an upgrade package must be
created.
a. Click Yes to start to create the upgrade package.

When the upgrade package is created, a message box is displayed.
b. Click OK. The creating upgrade package is completed.
End of Steps
4.2 Performing Upgrade Installation

This procedure describes the procedure of upgrade installation. After initial installation of
the OMMB system software, the OMMB software upgrade installation can be implemented.
The database and the ZXSDR OMMB configuration center use the parameters of the
original version by default.
4-16
SJ-20150317102154-002|2015-05-10 (R1.0)
Steps
1. Use the omc account to log in to the operating system.
2. Upload the OMMB installation package to the installation file directory in binary mode,
and unzip the files.
3. Open the folder of the unzipped upgrade installer, and then double-click the linuxsetup.sh file to start the installer. The language selection dialog box is displayed.
Note:
In Solaris, the path is /export/home/omc/OMMB-Installer/Installer.
The installation files for Solaris and Windows are solaris-setup.sh, and window
s-setup.exe respectively.
4. Select English, and then click Next. The license agreement dialog box is displayed.
5. Select I accept the license agreement, and then click Next. The installation type and
installation path selection dialog box is displayed.
6. Select upgrade in the Installation type area, and enter a directory to install the OMMB
software in the Installation path area. Alternatively, select the Browse button and
select a directory to install the OMMB software.
7. Click the Next button. The installation mode window is displayed.
8. (Optional) If other modes are required after the upgrade, select the corresponding
options in the Radio Standard node, and click Next. The database configuration
dialog box is displayed.
Note:
The system supports the radio modes set by the original version.
9. Use the default configuration, and click Next. The Environment Detection window is
displayed.
10. After the environment detection succeeded, click Next. The confirmation dialog box
is displayed.
11. Confirm that the installation information is correct, and then click Install to start the
installation. When the installation is completed, the ZXSDR OMMB configuration
center dialog box is displayed.
12. Review the setting of the ZXSDR OMMB configuration center, and click Next, the
installation completion window is displayed.
4-17
SJ-20150317102154-002|2015-05-10 (R1.0)
13. Click Finish to complete the ZXSDR OMMB system upgrade installation.
End of Steps
4.3 Installing updateAgent

The updateAgent tool is used to support remote upgrade and deployed in the OMMB
server. It is only applicable to Linux system.
If the server does not support updateAgent or the OMMB is planned to not support remote
upgrade, you can skip this section.
Steps
1. Use root account to log in to the Linux system.
2. Enter the path /home/oracle/Ommb_version/12.13.61/Installer/ums/um
s-svr/tools/updateAgent/.
3. Double-click the sh install.sh to install updateAgent, the terminal displays as
follows.
4-18
SJ-20150317102154-002|2015-05-10 (R1.0)

os : Linux
current_path=/home/oracle/Ommb_version/12.13.61/Installer/ums/ums-svr/tools/
updateAgent
* kill updateAgent process. pid: 19022
copy file and jdk to /home/updateAgent...
backup /etc/rc.d/rc.local to /home/updateAgent/tmp...
deploy updateAgent success...
Tip: please start updateAgent with root user by running "nohup startagent-linux.sh &"
in /home/updateAgent
Setting Environment Variables Begin
AGENT_ENV=/home/oracle/oracle/product/10.2.0/db_1:/home/oracle/oracle/product/
10.2.0/db_1/bin
Setting Environment Variables End
PATH=/home/updateAgent/jdk-linux/jre/bin:/oracleapp/product/10.2.0/bin:/home/hp/
hadoop/bin:/home/hp/jdk-linux/bin:/usr/sbin:/oracleapp/product/10.2.0/bin:/usr/sbin:/
oracleapp/product/10.2.0/bin:/usr/sbin:/usr/local/bin:/usr/bin:/sbin:/bin:/usr/bin/
X11:/usr/X11R6/bin:/usr/games:/usr/lib/mit/bin:/usr/lib/mit/sbin:/oracleapp/product/
10.2.0/bin:/usr/bin:/usr/sbin:/usr/ccs/bin:/usr/local/bin:/etc:/home/updateAgent/lib:
/home/oracle/oracle/product/10.2.0/db_1:/home/oracle/oracle/product/10.2.0/db_1/bin
=============================================================================
* * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * *
=============================================================================
Update Agent
2015-04-25 16:34:37,026 [AgentStart]

******************************************************************
NetNumen(TM)-updateAgent env:en_US
version:V12.13.62 patch: last update:20150429105900
Copyright(C) (2002-2010). All rights reserved.
******************************************************************
4-19
SJ-20150317102154-002|2015-05-10 (R1.0)
Note:
If updateAgent has been installed and started, it will be closed.
updateAgent deployment folder is /home/updateAgent/.
The default
4. Execute ps -ef|grep /home/updateAgent | grep -v grep to verify updateAgent has started

or not, the terminal displays as follows.
root 19242 19232 0 16:34 pts/3 00:00:00

/home/updateAgent/jdk-linux/bin/java -Xms512m -Xmx768m -XX:PermSize=256M
-XX:MaxPermSize=256M
-classpath
/home/updateAgent/lib/commons-net.jar:/home/updateAgent/lib/concurrent.jar:/home
/updateAgent/lib/jakarta-oro.jar:/home/updateAgent/lib/jdom.jar:/home/updateAgent
/lib/log4j.jar:/home/updateAgent/lib/ojdbc14.jar:/home/updateAgent/lib/
uep-update-container-control.jar:/home/updateAgent/lib/uep-util-toolkit.jar:/home/
updateAgent/lib/uep-psl-ftpclient.jar:/home/updateAgent/lib/uep-psl-ssh.jar:/home/
updateAgent/lib/uep-protocol-icmp.jar:/home/updateAgent/lib/ant.jar:/home/updateAgent/
lib/uep-api.jar:/home/updateAgent/lib/jboss-common.jar:/home/updateAgent/lib/
uep-util-umdjps.jar:./moss-ivm-ius-agent.jar com.zte.ums.moss.ivm.ius.agent.AgentStart
5. Execute #cat /etc/rc.d/rc.local to verify that updateAgent has been set starting
automatically with the system, the terminal displays as follows.
#UPDATEAGENT_BEGIN
#config updateAgent auto-start when start system
nohup /home/updateAgent/startagent-linux.sh &
#UPDATEAGENT_END
End of Steps
4-20
SJ-20150317102154-002|2015-05-10 (R1.0)
Chapter 5
Starting the OMMB System

This procedure describes how to start the ZXSDR OMMB server in the Linux operating
system and start the ZXSDR OMMB client in the Windows operating system. The startup
procedures in Linux, Solaris, and Windows are similar.
Steps
l
Start the ZXSDR OMMB server.

In the /ums/ums-svr/bin directory under the ZXSDR OMMB installation path,
double-click console-linux.sh to start the ZXSDR OMMB server.
Note:
The ZXSDR OMMB server startup files for Windows, and Solaris are console-sol
aris.sh and console.exe respectively.
If GUI is selected in the Server Starting Mode Configuration, the status of

both the UMS and FTP processes is displayed as successful after the OMMB is
successfully started.
If Non-GUI is selected in the Server Starting Mode Configuration, you can

determine whether the server is started successfully in one of the following two
ways:
t
Wait for five minutes and attempt to log in to the OMMB server through a
client. If the login succeeds, the OMMB server is started successfully.
Go to the directory ums/ums-svr/bin/consolemml, and execute #sh status-lin

ux.sh.
If the status of both the UMS and FTP process is started, the OMMB server
is started successfully.
In the Solaris system, execute #sh status.sh directly.
Start the ZXSDR OMMB client.

1. Open the ZXSDR OMMB login dialog box by performing either of the following
operations.
In the Windows Start menu, select Programs > ZXSDR OMMB > Client.
5-1
SJ-20150317102154-002|2015-05-10 (R1.0)
In the /ums/ums-clnt/bin directory under the OMMB installation path,

double-click run.exe.
2. Enter User Name, Password, and Server Address to log in to the OMMB system.
End of Steps
5-2
SJ-20150317102154-002|2015-05-10 (R1.0)
Chapter 6
Performing Automatic Client

Upgrade
This procedure describes how to perform automatic client upgrade. If the version of the
client is earlier than that of the server, the client initiates an automatic upgrade task to
ensure that the versions of the client and the server are identical.
Prerequisite
l
l
Before the client automatically upgrades, you should make an automatic upgrade
package for the client on the server.
The version of the client is earlier than that of the server.
Steps
1. Start the OMMB client and log in to the server. For the corresponding operations, refer
to Chapter 5 Starting the OMMB System.
The Confirm message box is displayed, indicating that the versions are inconsistent
and asking whether you want to upgrade the client.
2. Click Yes. The system starts to obtain upgrade package information about the client
upgrade.
After the upgrade information is obtained, the Tip message box is displayed, indicating
that the automatic client upgrade will start.
3. Click OK. The Upgrade Software of UMS Platform window is displayed with the
welcome information in the window.
4. Click Next. After the upgrade information is initialized, a message box is displayed
with the upgrade version information.
5. Click Next to start the upgrade.
After the upgrade is completed, a message box is displayed, asking whether you want
to start the UMS client.
6. Select Yes, and click OK. The automatic client upgrade is completed.
End of Steps
6-1
SJ-20150317102154-002|2015-05-10 (R1.0)
6-2
SJ-20150317102154-002|2015-05-10 (R1.0)
Appendix A
Uninstalling the OMMB

System
This procedure takes Linux for example to describe how to uninstall the OMMB system.
Close OMMB server first before uninstallation.
Steps
1. Stop and close OMMB.
If...
Then...
If GUI is selected in the Server
the server console can be closed directly to stop the OMMB.
Starting Mode Configuration.

If
the
Non-GUI
Server
is
selected
Starting
Configuration.
in
i.
Mode
Log in to the system and enter the path /home/omc/netnum

en/ommb/ums/ums-svr/bin.
ii.
Execute sh close-console-linux.sh and type Y in the terminal to

stop the server. The terminal display
Close console successfully
means the server has been closed successfully.

Double-click close-console.bat in Windows system to close
OMMB.
iii. Click close button to stop the client directly.
2. Enter the path /home/omc/netnumen/ommb/install/bin

linux-uninstall.sh to start the uninstallation.
and
click
3. Click Uninstall, a message displays to ensure that the ZXSDR OMMB system is not
running. Click OK to continue to uninstall.
4. Click Finish to complete the uninstallation and quit the program.
End of Steps
A-1
SJ-20150317102154-002|2015-05-10 (R1.0)
A-2
SJ-20150317102154-002|2015-05-10 (R1.0)
Figures
Figure 2-1 Initial Installation Procedure of the ZXSDR OMMB Server ...................... 2-1
Figure 4-1 Select Language...................................................................................... 4-2
Figure 4-2 Installation Type and Installation Path Selection Dialog Box..................... 4-3
Figure 4-3 Radio Standard and Installation Mode Selection Dialog Box .................... 4-4
Figure 4-4 Database Configuration Dialog Box ......................................................... 4-5
Figure 4-5 Environment Detection Dialog Box........................................................... 4-6
Figure 4-6 OMMB Configuration Center Dialog Box ................................................ 4-10
Figure 4-7 Setting the Server Starting Mode ........................................................... 4-11
Figure 4-8 Setting the Server Type ......................................................................... 4-12
Figure 4-9 Setting FTP............................................................................................ 4-13
Figure 4-10 Setting the License Center IP............................................................... 4-14
Figure 4-11 Enabling NAT ....................................................................................... 4-15
Figure 4-12 Configuring DSCP................................................................................ 4-16
I
SJ-20150317102154-002|2015-05-10 (R1.0)
Figures
II
SJ-20150317102154-002|2015-05-10 (R1.0)
Tables
Table 1-1 Software Tools........................................................................................... 1-1
Table 3-1 Requirements for Operating Systems ........................................................ 3-1
Table 3-2 ZXSDR OMMB Server Requirements for Databases ................................. 3-1
Table 4-1 Installation Type Description...................................................................... 4-3
Table 4-2 Database Parameters................................................................................ 4-5
Table 4-3 Warnings in Environment Detection ........................................................... 4-7
III
SJ-20150317102154-002|2015-05-10 (R1.0)
Tables
IV
SJ-20150317102154-002|2015-05-10 (R1.0)
Glossary
DHCP
- Dynamic Host Configuration Protocol
DSCP
- Differentiated Services Code Point
NAT
- Network Address Translation
OMMB
- Operation and Maintenance Module for BTS, NodeB and eNodeB
SBCJ
- Single Board Computer of Jasper Forest
SBCX
- X86 Single Board Computer
SFTP
- Secure File Transfer Protocol
SSH
- Secure Shell
WAN
- Wide Area Network
V
SJ-20150317102154-002|2015-05-10 (R1.0)

SJ-20141110151550-018-ZXSDR UniRAN TDD-LTE (V3.20.50) Call Data Tracing Operation Guide

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

SJ-20141110151550-018-ZXSDR UniRAN TDD-LTE (V3.20.50) Call Data Tracing Operation Guide

Hochgeladen von

Copyright:

Verfügbare Formate

ZXSDR OMMB

Software Installation Guide

Additionally, the contents of this document are protected by

contractual confidentiality obligations.

Serial Number: SJ-20150317102154-002

ZTE Proprietary and Confidential

Chapter 4 Installing the OMMB System.................................................... 4-1

Chapter 5 Starting the OMMB System...................................................... 5-1

ZTE Proprietary and Confidential

This page intentionally left blank.

ZTE Proprietary and Confidential

About This Manual

Installation supervision engineers

Prerequisite Skills and Knowledge

Basic operations of the SUSE Linux/Solaris system

What Is in This Manual

Describes the ZXSDR OMMB software installation content.

Describes the ZXSDR OMMB software installation procedure.

Describes the ZXSDR OMMB software installation preparations.

Describes how to install, and upgrade the ZXSDR OMMB system.

Describes how to start the ZXSDR OMMB server and client.

Describes how to perform automatic client upgrade.

Describes how to uninstall the OMMB system.

ZTE Proprietary and Confidential

This page intentionally left blank.

ZTE Proprietary and Confidential

Software Installation Content

Linux: SUSE, RED HAT, and CGSL

Windows: Windows Server 2003

Oracle database 11.2.0.3.0

SQL Server 2005

SQL Server 2008

Software to be Installed on the Client

Operating systems: Windows XP and Windows Server 2003

Remote management tool

ZTE Proprietary and Confidential

ZXSDR OMMB Software Installation Guide

This page intentionally left blank.

ZTE Proprietary and Confidential

ZTE Proprietary and Confidential

ZXSDR OMMB Software Installation Guide

This page intentionally left blank.

ZTE Proprietary and Confidential

3.1 System Requirements

The operating system supports the

Oracle 10g or later.

Oracle 11.2.0.3.0 is recommended.

SQL Server 2005, SQL Server 2008.

Windows Server 2003

ZTE Proprietary and Confidential

ZXSDR OMMB Software Installation Guide

3.2 Making Installation Preparations in Linux

Restart the nscd service.

Shutting down Name Service Cache Daemon

Starting Name Service Cache Daemon

Starting Name Service Cache Daemon

2. Create an omc account and assign permissions to this account.

ZTE Proprietary and Confidential

Chapter 3 Installation Preparations

3. Obtain the ZXSDR OMMB installation package.

The MD5 code of test.zip is displayed as follows.

4. (Optional) Configure the DHCP relay function.

a. Use the root account to log in to the Linux system.

Execute the #./dhcp.sh command to start the script file.