SJ-20121213161606-007-ZXWR RNC (V3.12.10) OMM Software Installation Guide

ZXWR RNC
Radio Network Controller

OMM Software Installation Guide
Version:V3.12.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: support@zte.com.cn
LEGAL INFORMATION
Copyright 2013 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by
contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided as is, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No. Revision Date Revision Reason
R1.0 20130314 First Edition
Serial Number: SJ-20121213161606-007
Publishing Date: 2013-03-14(R1.0)
SJ-20121213161606-007|2013-03-14(R1.0) ZTE Proprietary and Confidential

Contents
About This Manual ......................................................................................... I
Chapter 1 Overview .................................................................................... 1-1
1.1 Network Management System ............................................................................ 1-1
1.1.1 Overview ................................................................................................. 1-1
1.1.2 OMM Software Architecture ...................................................................... 1-2
1.1.3 OMM Active/Standby Hardware Architecture.............................................. 1-2
1.2 Conventions and Factory Settings ....................................................................... 1-3
Chapter 2 Software Installation................................................................. 2-1

2.1 Installation Flow ................................................................................................. 2-1
2.2 Checks Before Software Installation .................................................................... 2-2
2.2.1 Installing Tool Software ............................................................................. 2-2
2.2.2 Installing the Software Script ..................................................................... 2-2
2.2.3 Viewing the System Version ...................................................................... 2-2
2.2.4 Modifying the Startup Mode ...................................................................... 2-2
2.2.5 Debugging Network Interfaces .................................................................. 2-2
2.2.6 Configuring a Database Listener ............................................................... 2-3
2.3 LogService Installation...................................................................................... 2-10
2.3.1 Checking the LogService Program .......................................................... 2-10
2.3.2 Stopping and Deleting the LogService Program ....................................... 2-10
2.3.3 Installing the LogService Program ............................................................2-11
2.3.4 Modifying Configuration Files .................................................................. 2-13
2.4 OMM Server and Client Program Installation...................................................... 2-19
2.4.1 Installing the OMM Program.................................................................... 2-19
2.4.2 Standby OMM Program Installation ......................................................... 2-27
2.4.3 Installing the OMM Client Program .......................................................... 2-33
Figures............................................................................................................. I
Glossary ........................................................................................................ III

II

About This Manual
Purpose
This manual provides information about the ZXWR RNC system software architecture,
LogService installation procedure, andOMM server and client program installation
procedures.
Intended Audience
This manual is intended for:
l Network planning engineers

l Installation engineers
l Maintenance engineers
What Is in This Manual

This manual contains the following chapters:
Chapter Summary
1, Overview Describes the network management system, system architecture,

and installation conventions and factory settings.
2, Software Installation Describes the checks before software installation, LogService in-
stallation, and OMM server and client program installations.
Related Documentation
ZXWR RNC(V3.12.10) Radio Network Controller Product Description
ZXWR RNC(V3.12.10) Radio Network Controller Hardware Description

ZXWR RNC(V3.12.10) Radio Network Controller Hardware Installation
Conventions
This manual uses the following typographical convention:
Typeface Meaning
Note: provides additional information about a certain topic.

II

Chapter 1
Overview
Table of Contents
Network Management System....................................................................................1-1
Conventions and Factory Settings ..............................................................................1-3
1.1 Network Management System

1.1.1 Overview
1. The LogService program and OMM program are running on the OMM board.
l The LogService program supports the system operations, and ensures that the
OMM program can be running properly.
The LogService program collects various information of the ZXWR RNC,
including logs, real-time tracing data, and network optimization data. Some of the
data are saved as files in accordance with the actual requirement. It improves
the system performance by reducing the workload of sending a large amount of
printing information and tracing information to the network management system
through the O&M board.
l The OMM program is responsible for maintaining RNC configuration data,

collecting performance data, and presenting alarm data.
The OMM uses C/S architecture, namely, multiple clients and the server are
connected via a LAN or WAN. A user can operate on resources stored on the
server after logging to the server from a client. The server then returns the
operation result.
Server
In C/S architecture, the server consists of server hardware and server
software. The server software refers to the network management system
server program. The server hardware refers to the computer or work station
on which the server program is running.
Client
In C/S architecture, the client refers to the client program. Users can install
and run the client program on the computer where the server program is
located, or install the client program on a separate computer.
1-1

ZXWR RNC OMM Software Installation Guide
1.1.2 OMM Software Architecture

Figure 1-1 shows the OMM software architecture, which includes the OMM server program
and OMM client programs.
Figure 1-1 OMM Software Architecture
The OMM server program supports the Linux operating system and Oracle database.
The OMM client program supports the Windows operating system. In practical
applications, the server program and client programs must be supported by Java virtual
machines.
1.1.3 OMM Active/Standby Hardware Architecture

The OMM hardware platform uses the active/standby SBCX2 board configuration, see
Figure 1-2.
1-2

Chapter 1 Overview
Figure 1-2 Active/Standby OMM Architecture
1. Data is exchanged between the active OMM and the standby OMM. In this version,
internal data exchange is used.
2. The IP address of the left board must be set to 128.0.30.1 or 128.0.28.1, and the IP
address of the right board must be set to 128.0.30.9 or 128.0.28.9.
3. To handle route problems due to that multiple network adapters are located in the same
network segment, NETMASK is set to 255.255.255.0.
1.2 Conventions and Factory Settings

Default Conventions
l Command conventions
// represents comment or note.
Starting with [root]: The command is executed by the root user.
Starting with [oracle]: The command is executed by the oracle user.
Starting with [womcr]: The command is executed by the omm user.
Starting with [zte]: The command is executed by the zte user.
Starting with SQL>: The command uses SQL statements executed by the oracle
user.
l Name conventions
The SBCX/SBCX2 board is of the OMM type (called OMM board or OMM for short).
OMM Factory Settings

The following describes the OMM factory settings:
l RAID1 is created for the board.
l The LogService program is installed.
1-3

l The Oracle database program and Oracle patch are installed, and the version is
V10.2.0.4.0.
l A database instance whose name is "womcr" is created. "womcr" is considered as
the default Oracle database instance, and is set to starting automatically.
Installation Directory Conventions

The Oracle database program and the ZXM-OMMR(R3)(V12.12.40) server program must
be installed in the following directories:
l The ZXM-OMMR(R3)(V12.12.40) server program is installed under the /home/wom
cr/ directory, which is the home directory of the womcr user.
l Database files are installed under the /oracledata/womcr directory.
The network management installation startup script is installed under the /home/womcr/
zxommr directory.
1-4

Chapter 2
Software Installation
Table of Contents
Installation Flow .........................................................................................................2-1
Checks Before Software Installation ...........................................................................2-2
LogService Installation .............................................................................................2-10
OMM Server and Client Program Installation............................................................2-19
2.1 Installation Flow

Figure 2-1 shows the OMM installation flow.
Figure 2-1 OMM Installation Flow
2-1

The OMM server and client can be installed simultaneously or separately. Normally, the
OMM server is installed in the Linux operating system while the OMM client is installed in
the Windows operating system.
2.2 Checks Before Software Installation

2.2.1 Installing Tool Software
The following software must be installed:
l Windows command line terminal or SecureCRT software
l FTP tool such as FileZilla
l Remote GUI management tool such as vncviewer
2.2.2 Installing the Software Script

The system must be installed with the legitimate ZXM-OMM(R3)(V12.11.40) network
management installation software.
2.2.3 Viewing the System Version

Execute the [root]cat /etc/redhat-release command to view the system version.
The system output information is as follows:
Red Hat Enterprise Linux AS release 4 (Nahant Update 7)
2.2.4 Modifying the Startup Mode

By default, the OMM program is started in text mode. Execute the [root] vi/etc/inittab
command to modify that OMM is started in GUI mode.
Set id:5:initdefault:.
After the modification is completed, restart the server.
2.2.5 Debugging Network Interfaces

The corresponding relationship between network interfaces and IP addresses are
described as follows:
Network Interface eth3(SBCX)/eth0(SBCX2)
O&M IP address 10.x.x.x, for example, 10.62.102.51
(Left board)
O&M IP address 10.x.x.x, for example, 10.62.102.52
(Right board)
2-2

Chapter 2 Software Installation
Note:
The left board and the right board cannot have the same IP address.
2.2.6 Configuring a Database Listener

Perform the following configuration operations:
Note:
The modification of database configuration files involves the name of the machine where
the OMM board is located. Therefore, it is recommended to ensure that the machine name
of the board is unique and the database instances of the active/standby boards are the
same.
1. Modify the /etc/rc.d/rc.local configuration file.

Verify that the following configuration information is added before the LogService
program is installed:
ulimit n 4096
./etc/profile
The configuration file contents are as follows:
#!/bin/sh
# This script will be executed *after* all the other init scripts.
# You can put your own initialization stuff in here if you don't
# want to do the full Sys V style init stuff.
ulimit -n 4096
touch /var/lock/subsys/local
/etc/profile
2. Check the /etc/hosts configuration file.

In the Linux operating system, this file maps machine names to IP addresses.
Execute the #cat /etc/hosts command. The following information is outputted:
l The left board configuration is as follows:
#IP address #Machine name

10.62.102.51 tdrnc13_L
127.0.0.1 localhost.localdomain localhost
l The right board configuration is as follows:
2-3

#IP address #Machine name

10.62.102.52 tdrnc13_R
127.0.0.1 localhost.localdomain localhost
Note:
The IP addresses and machine names of the left and right boards depend on the actual
condition.
The IP address in the first line is the O&M IP address of the SBCX system. The left
board and the right board have different O&M IP addresses.
If the system output differs from the above listed, execute the vi command to modify
the configuration file.
To avoid exceptions, it is recommended that users should not modify the file.
3. Check the /etc/sysconfig/network configuration file.

Execute the [root] cat/etc/sysconfig/network command, and verify that the following
information is outputted:
l The left board information:
NETWORKING=yes
HOSTNAME=tdrnc13_L
l The right board information:

NETWORKING=yes
HOSTNAME=tdrnc13_R
Note:
If the system output differs from the above listed, execute the vi command to modify
the configuration file.
In the above three steps, if modification is made, restart the system.
4. Modify the listener configuration file.

Modify the /oracleapp/oracle/product/10.2.0/network/admin/listene
r.ora file, and verify that the HOST value is consistent with the host name in the
hosts file.
l Left board:
(ADDRESS = (PROTOCOL = TCP)(HOST = tdrnc13_L)(PORT = 1521))
l Right board:
2-4

(ADDRESS = (PROTOCOL = TCP)(HOST = tdrnc13_R)(PORT = 1521))
5. Configure the database NET service name.

Perform the following configurations for the left board and the right board:
a. Execute the following commands:
#xhost +
#su oracle
$netca
The Oracle Net Configuration Assistant: Welcome window is displayed, see
Figure 2-2.
Figure 2-2 Oracle Net Configuration Assistant: Welcome Window
b. Select Local Net Service Name configuration, and click Next. The Oracle
Net Configuration Assistant: Net Service Name Configuration window is
displayed, see Figure 2-3.
2-5

Figure 2-3 Oracle Net Configuration Assistant: Net Service Name Configuration
Window
c. Select Add, and click Next.

d. Set Service Name to the Oracle database instance name.
e. Click Next. The Oracle Net Configuration Assistant: Net Service Name
Configuration, Select Protocol window is displayed, see Figure 2-4.
Figure 2-4 Oracle Net Configuration Assistant: Net Service Name Configuration,
Select Protocol Window
f. Select TCP, and click Next. The Oracle Net Configuration Assistant: Net
Service Name Configuration, TCP/IP Protocol window is displayed, see Figure
2-5.
2-6

TCP/IP Protocol Window
g. Set Host name to 128.0.30.1, and click Next. The Oracle Net Configuration
Assistant: Net Service Name Configuration, Test window is displayed, see
Figure 2-6.
Test Window
h. Select No, do not test, and click Next.

i. Set Net Service Name in the format of <SID>_<Host IP>. In this example, it is
set to womcr_128.0.30.1.
j. Click Next. The Oracle Net Configuration Assistant: Net Service Name
Configuration, Another Net Service Name window is displayed, see Figure 2-7.
2-7

Another Net Service Name Window
k. Select No.
l. Repeat the previous steps to configure local service names for the hosts whose
IP addresses are 127.0.0.1 and 128.0.30.9 respectively.
m. Execute the following commands to check the service name configurations of the
left board and the right board:
#cd /oracleapp/oracle/product/10.2.0/network/admin/
# cat tnsnames.ora
Verify that the following three results are outputted:
2-8

womcr_128.0.30.9 =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 128.0.30.9)(PORT = 1521))
)
(CONNECT_DATA =
(SERVICE_NAME = womcr)
)
)
womcr_128.0.30.1 =
(DESCRIPTION =
(ADDRESS_LIST =
)
(CONNECT_DATA =
)
womcr_127.0.0.1 =
(DESCRIPTION =
(ADDRESS_LIST =
)
(CONNECT_DATA =
)
)
In practical applications, the above operations depend on the actual database instances
of the left board and right board in active/standby operating environment.
Users can also add local service names for IP addresses of other network segments, for
example, the 129 network segment.
Switch to the oracle user, and execute the sqlplus /nolog command to open the database.
Execute the conn system/oracle@womcr_127.0.0.1 command to verify that the database
can be connected.
l If the database can be connected, skip the listener configuration process, and install
the network management program.
l If the database cannot be connected, check the database listener configuration, and
reconfigure the database listener.
2-9

2.3 LogService Installation

2.3.1 Checking the LogService Program
Prerequisite
1. The Linux operating system is running properly.
2. The OMM board is started properly.
3. The OMM board is configured with network interfaces properly.
Steps
1. Log in to the OMM system, and open the command line terminal window.
2. Execute the ps -ef | grep logservice | grep -v grep | wc -l command.
If the command result is not 0, it indicates that the LogService program is running and
must be stopped.
If the command result is 0, it indicates that the LogService program is stopped and
can be installed.
End of Steps
2.3.2 Stopping and Deleting the LogService Program

Prerequisite
Steps
1. Log in to the OMM system as the zte user and open the command line terminal window.
2. Execute the su - command to switch to the root user, and enter the password of the
root user.
3. Execute the [root] cd /home/zte/logservice/bin command. The LogService software
directory is entered.
4. Execute the [root] ./ stopsys command to stop the LogService program.
Note:
If the system prompts that you do not have the operation right, execute the chmod 755
stopsys command, and repeat step 4.
2-10

5. Execute the following commands to uninstall the LogService program:

[root] cd /home/zte/logservice/install
[root] ./uninstall
6. Execute the following commands to delete the LogService program.
[root] cd /home/zte/
[root] rm rf *
End of Steps
2.3.3 Installing the LogService Program

Prerequisite
4. The Logservice_Linux software installation package is available.
Steps
1. Start the FTP software on the PC connected to the OMM system.
2. Log in to the FTP server on the OMM board as the zte user, and upload the LogService
software to the home directory of the zte user. The default home directory of the zte
user is /home/zte.
3. Log in to the OMM system as the zte user and open the command line terminal window.
4. Execute the [zte] cd /home/zte command, and switch to the home directory of the zte
user.
5. Execute the following commands as the zte user to decompress the uploaded
compressed software package:
Note:
This procedure uses the LogService (V6.50.100b) software as an example, and the
compressed software package is named as logservice_V6.50.100b.zip.
[zte] mkdir BuiltinServer3.30.100g

[zte] mv BuiltinServer3.30.100g.zip BuiltinServer3.30.100g
[zte] cd BuiltinServer3.30.100g
[zte] unzip BuiltinServer3.30.100g.zip
2-11

After the package is decompressed, a folder named as logservice_V6.50.100b

is generated under the /home/zte directory.
6. Execute the [root] su - command to switch to the root user, and enter the password of
the root user. The default password of the root user is root123.
7. Execute the [root] cd /home/zte/BuiltinServer3.30.100g/install command to switch to the
installation directory.
8. Execute the [root] chmod +x install command to modify the install script to be
executable.
9. Run the LogService installation script.
Set the following two parameters in running the install script.
l Board type
l Installation type
The following gives an example:
[root] ./install sbcx LOGOMM
********************************************************
***************Logservice Install Start!****************
********************************************************
****** Step0 Check the input parameters ******

****** Step0 Finished ******
****** Step1 Check the Linux Kernel Version ******

The Linux Kernel is 2.6.18
****** Step2 check user zte and current user

****** ****** Step2 Finished ******
****** Step3 check whether directory logservice exist ******

****** Step4 Check logservice Version ******

****** Step5 check bins & libs ******

chmod: Unable to access the tmp directory: no such file or directory
****** Step6 add ftp user zternc and omc ******

Changing password for user zternc.
passwd: all authentication tokens updated successfully.
Changing password for user omc.
passwd: all authentication tokens updated successfully.
2-12

****** Step7 get system.conf ******

****** Step8 shut down arp proxy ******

****** Setp9 Adjust vsftpd listening port from 21 to 10021; And add prot
mapping from 21 to 10021 ******
Only sbcx support, install ignored!
****** Step10 Install New logservice Version ******

(1) Set Envirment Var ......
(2) Setup epld driver ,only sbcx need epld ......
only sbcx need epld , other board nothing to do!
(3) Add logservice to auto-start file......
****** Step11 last check ******

********************************************************
*******************Install Finished!********************
********************************************************
End of Steps
2.3.4 Modifying Configuration Files

The LogService-related configuration files are saved under the /home/zte/logservic
e/bin/conf directory.
Perform the following steps to modify the configuration files:
1. Modify the BrdPhyAddr.conf file. Set relevant parameters in accordance with the
slots where the boards are installed.
2. Modify the system.conf file.
This file is used to set the LogService boot information.
[system]
/* Set whether the LogService program and OMM are started simultaneously. */
ShareBoardMode = 2 ; 0: OMM, 1: LogSvr, 2: LogSvr&OMM
BackupMode = 1 ; 0: single, 1: 1+1 backup
2-13

BoardType = 1 ; 1: sbcx, 2: sbcw, 3: sbcj , 4pcv3, 5:pcv4

3. Modify the NetIf.conf file.
Enter the LogService installation directory, execute the gedit command or vi
command to open the NetIf00.conf, NetIf01.conf, and Netif02.conf files,
and perform the following operations to modify relevant configuration parameters:
Note:
The following uses the NetIf00.conf file as an example to describe how to modify
relevant configuration parameters.
a. The number of booting network interfaces
Note:
The number of booting network interfaces is the number of configured network
interfaces, and the booting sequence is: Channel1, ..., ChannelX.
In OMM, the number of booting network interfaces is set to 7.

[CommChannel]
count = 7
b. Channel1
#Control panel channel UIMC interface (FE)
#No modification is required.
[Channel1]
ChannelName = CtrlPlane
NetIfName = eth0
IP =
NETMASK =
MacAddr =
Mtu =
GateWay =
NextSkipIP =
NextSkipNetMask =
NeedSetDefaultGateWay = 0
2-14

ShareIP = 0
Note:
The control plane network interface needs not be configured. Its IP address and
NETMASK are automatically set in accordance with the rack, shelf, and slot of the
board, and the IP address does not correspond to the network interface ID of the
related rear board.
c. Channel2
#Platform log UDP channel -- UIMC interface (FE)
#No modification is required.
[Channel2]
ChannelName = UdpLog
NetIfName = eth0:1 #Multiplexes the eth0 interface of the
control plane.
IP = 128.200.31.1
NETMASK = 255.0.0.0
MacAddr =
Mtu =
GateWay =
NextSkipIP =
NextSkipNetMask =
ShareIP = 1
d. Channel3
#OMM active/standby channel -- HEART1 interface (FE) of the
rear board
#The active/standby channel is identified with OMM_MS. The
network interface IP address of the active/standby channel
is automatically loaded by the system, and needs not be
configured.
[Channel3]
ChannelName= OMM_MS
NetIfName = eth1
IP =
2-15

NETMASK =
MacAddr =
Mtu =
GateWay =
NextSkipIP =
NextSkipNetMask =
ShareIP = 0
e. Channel4
It is originally set to eth3. Because eth3 is configured for the network adapter, it is
modified to eth3:1.
#OMCR channel (used for the OMM function), connected to the
MINOS.
#OMM client server channel -- OMC1 (GE) interface on the
rear board
#OMM client server channel -- OMC1 (GE) interface on the
rear board
[Channel4]
ChannelName= OMM_OMCR
NetIfName = eth3:1
IP = 10.61.102.101 #Floating IP address. The configuration
is based on the Internet IP address connected to the MINOS,
and the Internet IP address is provided by the customer.
NETMASK = 255.255.255.0 #The configuration is based on the
Internet mask address provided by the customer.
MacAddr = #It must be set to NULL.
GateWay = #It needs not be configured because the channel
shares gateway with the eth3 network adapter.
NextSkipIP = #It needs not be configured if
NeedSetDefaultGateWay is set to 1.
NextSkipNetMask = #It needs not be configured if
NeedSetDefaultGateWay is set to 1.
NeedSetDefaultGateWay = 0 #It is set to 0, indicating that
the channel shares gateway with the eth3 network adapter.
#NextSkipIP and NextSkipNetMask need not be configured.
ShareIP = 1
2-16

f. Channel5
#OMP OMM channel (used for the OMM function)
[Channel5]
ChannelName= OMCR_OMP
NetIfName = eth6
IP = 129.0.11.8 #It is in the same network segment with
OMP, used for the communication between OMM and OMP.
#It is configured in accordance with the actual condition,
and the active board and standby board must be configured
with the same value.
NETMASK = 255.255.0.0 #It is in the same network segment
with OMP, used for the communication between OMM and OMP.
#The active board and standby board must be configured with
the same value.
MacAddr = It must be set to NULL.
GateWay = #It needs not be configured.
NextSkipIP = #It needs not be configured.
NextSkipNetMask = #It needs not be configured.
NeedSetDefaultGateWay = 0 #It must be set to 0.
ShareIP = 1
g. Channel6
#connnect to nodeb
#Connected to nodeb, and multiplexes eth6 with the OMP-OMM
channel.
#Connected to the GIPI board, and then the GIPI board is
connected to the OMCB.
[Channel6]
ChannelName=OMCB_OMCB
NetIfName = eth6:1
IP = 139.0.11.8 #OMCB channel configuration. This IP
address and the IP address of the GIPI gateway are in the
same network segment.
NETMASK = 255.255.0.0 #It must be in the same network
segment with OMP. The active board and standby board must
be configured with the same value.
MacAddr = It must be set to NULL.
2-17

GateWay = 10.9.1.145 #OMCB channel configuration; GIPI

gateway IP address, depending on the actual planning.
NextSkipIP = 11.11.0.0 #OMCB channel configuration; IPOA
destination subnetwork, depending on the actual planning.
NextSkipNetMask = 255.255.0.0 #OMCB channel configuration;
IPOA destination network segment, depending on the actual
planning.
NeedSetDefaultGateWay = 0 #It must be set to 0.
ShareIP = 1
h. Channel7
[Channel7]
ChannelName= VirtualIP_eth2
NetIfName = eth2IP =
#For the right board, the IP address is set to
192.168.61.2.
NETMASK =
MacAddr =
GateWay =
NextSkipIP =
NextSkipNetMask =
ShareIP = 0
Note:
1. If the gateway is required to set to the default gateway, set the
NeedSetDefaultGateWay field to 1.
If the NeedSetDefaultGateWay field of a network adapter is set to 0, it indicates that

the gateway is not the default gateway. If the NeedSetDefaultGateWay field is set to
1 for multiple network adapters, the last loaded gateway is considered as the default
gateway. OmmHost will ensure that there is only one default gateway in the system.
2. In the above configuration procedure, MacAddr, GateWay, NextSkipIP, and

NextSkipNetMask can be set to NULL if they need not be configured.
2-18

2.4 OMM Server and Client Program Installation

2.4.1 Installing the OMM Program
Steps
1. Log in to the FTP service on the OMM board as the womcr user, and upload the OMMR
software installation package to the home directory of the womcr user.
The default home directory of the womcr user is /home/womcr.
2. Log in to the OMM system as the root user, and open the command line terminal
window.
3. Execute the [root] cd /home/womcr command.
4. Execute the [root] chmod -R 777 zxommr.zip command.
zxommr.zip is the software installation package just uploaded.
5. Execute the [root] unzip zxommr.zip command.
The software installation package is decompressed, and the zxommr folder is
generated under the /home/womcr directory.
6. Right-click the blank area in the Linux operating system window, and select Open
Terminal from the shortcut menu.
7. Execute the cd /home/womcr/zxommr command to open the directory where the
version installation script install-linux.sh is located.
8. Execute the following command to modify the operation right of the install-linux
.sh file to be executable:
chmod +x install-linux.sh
or
chmod 755 install-linux.sh
9. Execute the ./install-linux.sh command to run the install-linux.sh file. The
installation process is started, and the Welcome - Please select language dialog
box is displayed.
10. Select the prompt language for installation environment, see Figure 2-8. This
procedure supposes that English is selected.
2-19

Figure 2-8 Welcome - Please Select Language Dialog Box
Note: Here, the language refers to the prompt language during the installation
procedure, not the OMM version language.
11. Click NEXT. The Welcome - You should accept the agreement to continue
installing dialog box is displayed, see Figure 2-9.
2-20

Figure 2-9 Welcome - You Should Accept the Agreement to Continue Installing
Dialog Box
12. Select Accept, and click NEXT. The Welcome - Please select product dialog box
is displayed, see Figure 2-10. This procedure supposes that English Version is
selected.
Figure 2-10 Welcome - Please Select Product Dialog Box
13. Click NEXT. The Welcome - Please select product module dialog box is displayed,
see Figure 2-11.
2-21

Figure 2-11 Welcome - Please Select Product Module Dialog Box
14. Select Server and Client, and click NEXT. The Welcome - Please set installation
path dialog box is displayed, see Figure 2-12.
Figure 2-12 Welcome - Please Set Installation Path Dialog Box
15. Set the installation path to /home/omm/ZXM-OMMR/, click NEXT. The system prompts
to create the /home/omm/ZXM-OMMR/ directory.
2-22

16. Click OK. The Welcome - Server Parameter Configuration dialog box is displayed,
see Figure 2-13.
Figure 2-13 Welcome - Server Parameter Configuration Dialog Box
17. Set UMS Type to wcdma.omm, set the board position and license server IP
addresses, and click NEXT. The Welcome - Set of application database dialog box
is displayed, see Figure 2-14.
Figure 2-14 Welcome - Set of Application Database Dialog Box
2-23

Set the database type to ORACLE.

Set the Oracle server IP address to 127.0.0.1.
Set the database instance ID (SID) to v4omcr.
Set the system password for installing the database.
If the OMM server and the database server are installed on the same machine, select
database and server on the same machine; otherwise, do not select database and
server on the same machine.
18. If the product data is already in the database, the tip dialog box will be displayed, see
Figure 2-15.
Figure 2-15 Tip Dialog Box
19. Click OK. The Welcome - Set of application database dialog box is displayed, see
Figure 2-14.
20. Click NEXT. The Welcome - Delete initial data dialog box is displayed. Select Clear
related data of the product in the database.
21. Click NEXT. The Welcome - Database Module Set dialog box is displayed, see Figure
2-16.
2-24

Figure 2-16 Welcome - Database Module Set Dialog Box
22. Select Normal from the Database Module Set drop-down list, and click NEXT. The
Welcome - Database Parameter Set dialog box is displayed, see Figure 2-17.
Figure 2-17 Welcome - Database Parameter Set Dialog Box
23. Set the database parameter set path to /oracledata/v4omcr , and click NEXT.
The Welcome - Please view install information dialog box is displayed, see Figure
2-18,
2-25

Figure 2-18 Welcome - Please View Install Information Dialog Box
24. Verify that the relevant parameters are set properly, and click NEXT. The Welcome -
Install application database server dialog box is displayed, showing the application
database server installation progress.
25. After the application database server is installed, click NEXT. The Welcome - Install
the application program dialog box is displayed.
26. After the application program is installed, click NEXT. The Welcome - Set the user
and group to run the program dialog box is displayed, see Figure 2-19.
2-26

Figure 2-19 Welcome - Set the User and Group to Run the Program Dialog Box
27. Enter gomcr in the user text box, and enter gomcr in the group text box, and click
NEXT. The Welcome - Config environment dialog box is displayed.
28. After the environment is configured, click NEXT. The Welcome - Setup finished
dialog box is displayed.
29. Click Finish. The installation is completed.
Note:
In the Linux operating system, the installation log path is /tmp/setup-log, the se
tup.log file is the installation program execution log, and other files are database
script execution logs.
End of Steps
2.4.2 Standby OMM Program Installation

2.4.2.1 Installing the Standby OMM Program
The following describes the precautions in running the omm_conf.py script:
l The left board and right board are set properly.
l The left board and right board have different VNC O&M IP addresses.
For operation details, refer to 2.4.1 Installing the OMM Software.
2-27

2.4.2.2 Checking the Active/Standby Operating Environment

1. After the OMM and LogService program are installed and configured, use either of the
following two methods to start the active/standby operating environment:
l Execute the following commands on the left board and right board respectively:
[root] cd /home/zte/logservice/bin/
./startsys
The active/standby process is started on the corresponding board. The board on
which the LogService program is running first works as the active board while the
other one works as the standby board.
l Reboot the boards.
The active/standby process is auto-starting. After the OMM boards are reset and
rebooted, the active/standby process will be automatically run. The board on
which the LogService program is started first works as the active board.
2. Verify that the active board is operating properly.

Telnet the LogService console, and execute the following command:
[omm] telnet localhost 5234
If you do not log in to the console from the local client, use the external IP address of
the board on which the LogService program is running as the localhost IP address.
Execute the SBCX->SCSShowMcmInfo command. If the system outputs the following
information, it indicates that the LogService program is running properly.
SCSMCProc: All 2 CThreads power on successfully.
Execute the SBCX->SCSShowBrdInfo command to view the board status information

in the current active/standby operating environment. The system outputs the following
information:
2-28

Physical address info:

Bureau: 1
rack: 1
shelf: 4
slot: 3
cpu: 1
board pos: 1
boardtype: 132
ipaddr: 0x80106301
ctrl plat mac addr: 00:d0:d0:90:70:03
Logical address info:
system: 0
subsystem: 255
module: 100
unit: 65535
board backup mode: 1+1
board ms state: master
board run mode: act as server, and share board with OMM
3. Verify that the OMM on the active board is operating properly.

Execute commands as the root user. This procedure supposes that /home/omm/ZX
M-OMMR/ is the OMM installation directory.
l Verify that the Backup process is started properly.
Execute the [omm] cd /home/omm/ZXM-OMMR/ums-svr/tools/backup/log/
command. If the system outputs the following information, the active/standby
process is started. The backup-timestamp.log file depends on the actual
environment.
[omm] cat backup-20110520-1459-19674.log |grep started

backup process is started...
[omm] cat backup-20110520-1459-19674.log |grep UmsStateManager
2011-05-20 15:25:42,080 INFO [UmsStateManager] Begin start ums process!
2011-05-20 15:28:22,025 INFO [UmsStateManager] Start ums successfully
2011-05-20 15:28:22,025 INFO [UmsStateManager] End start ums process!.
Execute the [omm] less backup-20110520-1459-19674.log command to view

detailed information.
l Verify that the UMS process is started properly.
Execute the [omm] cd /home/omm/ZXM-OMMR/ums-svr/log/ command. If the
system outputs the following information, the UMS process is started.
[omm] cat server-start.log |grep 'UMS-PLATFORM'|grep 'started'

UMS-PLATFORM (MX MicroKernel) [GUOMCRV1.01.00.05] started.
If the above information is not outputted, the system may be starting. You can
execute the [omm] tail -f server-start.log command to view detailed information.
2-29

4. Verify that the standby board is operating properly.

This procedure supposes that the right board is the standby board and the left board
is the active board. Only the LogService program and active/standby process are
running on the standby board, and the UMS process is not running on the standby
board. Because the network planning specifies that the standby board does not work
for external services, users must telnet the standby board from the active board to
perform relevant operations, or directly perform operations on the local machine.
l Verify that the LogService program on the standby board is operating properly.
Telnet the LogService console, and execute the following commands:
[omm] telnet 128.0.30.9 5234
SBCX->SCSShowMcmInfo
If the system outputs the following information, the LogService program is running
properly.
SCSMCProc: All 2 CThreads power on successfully.
Execute the SBCX->SCSShowBrdInfo command to view the board status

information in the current active/standby operating environment. The system
outputs the following information:
Physical address info:
Bureau: 1
rack: 1
shelf: 4
slot: 3
cpu: 1
board pos: 1
boardtype: 132
ipaddr: 0x80106301
ctrl plat mac addr: 00:d0:d0:90:70:03
Logical address info:
system: 0
subsystem: 255
module: 100
unit: 65535
board backup mode: 1+1
board ms state: slave
board run mode: act as server, and share board with OMM
l Verify that the Backup process is started properly.

Execute commands as the root user. This procedure supposes that /home/omm
/ZXM-OMMR/ is the OMM installation directory.
[omm] cd /home/omm/ZXM-OMMR/ums-svr/tools/backup/log/
If the system outputs the following information, the active/standby process is
started. The backup-timestamp.log file depends on the actual environment.
2-30

[omm] cat backup-20110520-1459-19674.log |grep started

backup process is started...
Execute the [omm] less backup-20110520-1459-19674.log command to view

detailed information.
5. Verify that the active/standby changeover function is normal.
Telnet the active board or log in to the active board through the VNC client, telnet the
LogService console as the root user, and execute the following commands:
[omm] telnet localhost 5234
SBCX->SCS_TestChgOver
If the active/standby changeover is initiated successfully, no prompt is outputted.
If the changeover is initiated from the LogService console on the standby board, the
system outputs the following information:
board status is not master,changeover forbidden
After the changeover is initiated, execute the following commands to view the
active/standby log of the active board and whether there is any information related
to error or fail:
[omm] cd /home/omm/ZXM-OMMR/ums-svr/tools/backup/log/
[omm] tail -f backup-20110520-1459-19674.log
If the files generated during the system running are not large, the active/standby
changeover time is short. The active board quickly disconnects its external network
interface, thus no operation can be performed on the active board until the UMS
process on the standby board is started and the external floating IP address of the
standby board becomes valid. After the standby board is started, the original standby
board becomes the active board while the original active board becomes the standby
board.
The LogService program has the following time restriction on the active/standby
changeover initiation: After an active/standby changeover is performed, the active
board must wait for 30 minutes before initiating another changeover. After 30 minutes,
the active board can initiate another active/standby changeover to make the original
active board work as the active board.
6. Perform the following operations to ensure that the active/standby operating
environment is normal:
l After the active/standby operating environment is started, ensure that it
is in normal operating status. Perform analysis in accordance with the
active/standby process logs, including active/standby database synchronization,
timed synchronization for files generated during system running, and timed
synchronization for special tables.
l Verify that the active board and standby board have the same data. If the data
on the standby board are incorrect, exceptions will occur at the OMM client after
the standby board becomes the active board due to active/standby changeover.
2-31

After the standby board is connected for the first time, data synchronization must
be performed manually, and no database operation can be performed during the
synchronization.
l The active/standby operating environment ensures that normal services will not
be interrupted when the OMM on the active board is not operating properly.
Therefore, it is prohibited to perform any manual extracting/inserting operation
on the active board or stop the LogService process except in the case of OMM
upgrade or the active board unable to provide services.
l In case of exceptions such as the active board being down or the rear board
being damaged, it is prohibited to perform active/standby changeover by
extracting/inserting the active board.
If the active/standby changeover cannot be initiated automatically due to that
the active board's performance is very poor or the OMM memory overflows, the
active/standby changeover can be manually initiated by commands.
l In the current version, if the standby OMM board is powered down and restarted,
the active board must initiate manual database synchronization to ensure the data
consistency between the active board and standby board.
l If any of the above operations fails, save the failure information in relevant logs
and contact ZTE Corporation for technical support.
2.4.2.3 Synchronizing Active Board Data

Database synchronization is implemented by a tool, which is delivered with the OMM
software. The tool path is ums-svr/tools/backup/.
Perform the following operations to synchronize active board data:
1. Execute the following script:
[omm] ./dbsync-linux.sh oracle
The following information is outputted:
@WORK_DIR@
/home/guomc/ZXGUOMCR-OMM/ums-svr/tools/backup
@JAVA_CMD@
2011-09-24 15:20:36,767 INFO [DBSyncProcess] Welcome to use the database
synchronize tool.
2011-09-24 15:20:36,768 INFO [DBSyncProcess] 1. Synchronise all tables which
configed by the tableConfig-dbsync*.properties.
2011-09-24 15:20:36,768 INFO [DBSyncProcess] 2. Synchronise the history tables
of Fault Management(FM) and Performance Management(PM)
2011-09-24 15:20:36,768 INFO [DBSyncProcess] 3. Synchronise the Performance
Management(PM) file
2011-09-24 15:20:36,768 INFO [DBSyncProcess] 4. Compare the local database
data and the remote.
2011-09-24 15:20:36,768 INFO [DBSyncProcess] Please select 1 , 2 , 3 or 4:
2-32

2. Enter 1, and press ENTER. The synchronization progress is printed on the screen,
indicating that the data synchronization is completed. Press ENTER to exit.
2011-09-24 15:29:15,609 INFO [DBSyncProcess] 100.0% (sync.allTable)import tables

to the remote IP sucess!
2011-09-24 15:29:15,609 INFO [DBSyncProcess] 100.0% (sync.allTable)db sync sucess!
----------------------------------
press Enter key to continue...
Note:
The data synchronization must be initiated by the active board, and the LogService
process on the standby board must be stopped.
2.4.3 Installing the OMM Client Program

Context
The OMM client program is installed in the Windows operating system.
Steps
1. Double-click the install.bat file under the software installation directory. The
Welcome - Please select language dialog box is displayed, see Figure 2-20.
Figure 2-20 Welcome - Please Select Language Dialog Box
2-33

2. Select the prompt language for installation environment. This procedure supposes
that English is selected.
Note:
Here, the language refers to the prompt language during the installation procedure,
not the OMM client version language.
3. Click NEXT. The Welcome - You should accept the agreement to continue
installing dialog box is displayed, see Figure 2-21.
Dialog Box
4. Select Accept, and click NEXT. The Welcome - Please select product dialog box
is displayed, see Figure 2-22. This procedure supposes that English Version is
selected.
2-34

Figure 2-22 Welcome - Please Select Product Dialog Box
5. Click NEXT. The Welcome - Please select product module dialog box is displayed,
see Figure 2-23.
Figure 2-23 Welcome - Please Select Product Module Dialog Box
6. Select Client, and click NEXT. The Welcome - Please set installation path dialog
box is displayed, see Figure 2-24.
2-35

Figure 2-24 Welcome - Please Set Installation Path Dialog Box
7. Set the installation path to C:\ZXM-OMMR, and click NEXT. The system prompts to
create the C:\ZXM-OMMR directory.
8. Click OK. The Welcome - Please set installation path dialog box is displayed, see
Figure 2-24.
9. Click NEXT. The Welcome - Please view install information dialog box is displayed,
see Figure 2-25.
2-36

Figure 2-25 Welcome - Please View Install Information Dialog Box
10. Verify that the relevant parameters are set properly, and click NEXT. The Welcome -
Install application database server dialog box is displayed, showing the application
database server installation progress.
11. After the application database server is installed, click NEXT. The Welcome - Install
the application program dialog box is displayed.
12. Click NEXT. The Welcome - Select function dialog box is displayed.
13. Select Add shortcut, and click NEXT. The Welcome - Setup finished dialog box is
displayed.
14. Click Finish. The OMM client software installation is completed.
End of Steps
2-37

This page intentionally left blank.
2-38

Figures
Figure 1-1 OMM Software Architecture ..................................................................... 1-2
Figure 1-2 Active/Standby OMM Architecture............................................................ 1-3
Figure 2-1 OMM Installation Flow ............................................................................. 2-1
Figure 2-2 Oracle Net Configuration Assistant: Welcome Window ............................ 2-5
Figure 2-3 Oracle Net Configuration Assistant: Net Service Name Configuration
Window................................................................................................... 2-6
Select Protocol Window .......................................................................... 2-6
TCP/IP Protocol Window......................................................................... 2-7
Test Window ........................................................................................... 2-7
Another Net Service Name Window ........................................................ 2-8
Figure 2-8 Welcome - Please Select Language Dialog Box..................................... 2-20
Dialog Box ........................................................................................... 2-21
Figure 2-10 Welcome - Please Select Product Dialog Box ...................................... 2-21
Figure 2-11 Welcome - Please Select Product Module Dialog Box .......................... 2-22
Figure 2-12 Welcome - Please Set Installation Path Dialog Box.............................. 2-22
Figure 2-13 Welcome - Server Parameter Configuration Dialog Box ....................... 2-23
Figure 2-14 Welcome - Set of Application Database Dialog Box ............................. 2-23
Figure 2-15 Tip Dialog Box ..................................................................................... 2-24
Figure 2-16 Welcome - Database Module Set Dialog Box ....................................... 2-25
Figure 2-17 Welcome - Database Parameter Set Dialog Box .................................. 2-25
Figure 2-18 Welcome - Please View Install Information Dialog Box......................... 2-26
Figure 2-19 Welcome - Set the User and Group to Run the Program Dialog
Box ....................................................................................................... 2-27
Figure 2-20 Welcome - Please Select Language Dialog Box.................................. 2-33
Dialog Box ........................................................................................... 2-34
Figure 2-22 Welcome - Please Select Product Dialog Box ...................................... 2-35
Figure 2-23 Welcome - Please Select Product Module Dialog Box.......................... 2-35
Figure 2-24 Welcome - Please Set Installation Path Dialog Box.............................. 2-36

Figure 2-25 Welcome - Please View Install Information Dialog Box......................... 2-37
II

Glossary
C/S
- Client/Server
FTP
- File Transfer Protocol
GUI
- Graphical User Interface
IP
- Internet Protocol
LAN
- Local Area Network
O&M
- Operation & Maintenance
OMM
- Operation & Maintenance Module
OMMR
- Operation & Maintenance Module (RNC)
SBCX
- X86 Single Board Computer
SBCX2
- X86 Single Board Computer 2
SID
- System IDentifier
UMS
- Unified Messaging Service
VNC
- Virtual Network Computing
WAN
- Wide Area Network
III

SJ-20121213161606-007-ZXWR RNC (V3.12.10) OMM Software Installation Guide

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

SJ-20121213161606-007-ZXWR RNC (V3.12.10) OMM Software Installation Guide

Загружено:

Авторское право:

Доступные форматы

ZXWR RNC

Radio Network Controller

Revision No. Revision Date Revision Reason

R1.0 20130314 First Edition

Serial Number: SJ-20121213161606-007

Publishing Date: 2013-03-14(R1.0)

SJ-20121213161606-007|2013-03-14(R1.0) ZTE Proprietary and Confidential

Chapter 2 Software Installation................................................................. 2-1

SJ-20121213161606-007|2013-03-14(R1.0) ZTE Proprietary and Confidential

SJ-20121213161606-007|2013-03-14(R1.0) ZTE Proprietary and Confidential

l Network planning engineers

What Is in This Manual

1, Overview Describes the network management system, system architecture,

ZXWR RNC(V3.12.10) Radio Network Controller Hardware Description

Note: provides additional information about a certain topic.

SJ-20121213161606-007|2013-03-14(R1.0) ZTE Proprietary and Confidential

SJ-20121213161606-007|2013-03-14(R1.0) ZTE Proprietary and Confidential

1.1 Network Management System

l The OMM program is responsible for maintaining RNC configuration data,

SJ-20121213161606-007|2013-03-14(R1.0) ZTE Proprietary and Confidential

1.1.2 OMM Software Architecture

Figure 1-1 OMM Software Architecture

1.1.3 OMM Active/Standby Hardware Architecture

SJ-20121213161606-007|2013-03-14(R1.0) ZTE Proprietary and Confidential

Figure 1-2 Active/Standby OMM Architecture

1.2 Conventions and Factory Settings

OMM Factory Settings

SJ-20121213161606-007|2013-03-14(R1.0) ZTE Proprietary and Confidential

Installation Directory Conventions

SJ-20121213161606-007|2013-03-14(R1.0) ZTE Proprietary and Confidential

2.1 Installation Flow

Figure 2-1 OMM Installation Flow

SJ-20121213161606-007|2013-03-14(R1.0) ZTE Proprietary and Confidential

2.2 Checks Before Software Installation

2.2.2 Installing the Software Script

2.2.3 Viewing the System Version

Red Hat Enterprise Linux AS release 4 (Nahant Update 7)

2.2.4 Modifying the Startup Mode

2.2.5 Debugging Network Interfaces

Network Interface eth3(SBCX)/eth0(SBCX2)

O&M IP address 10.x.x.x, for example, 10.62.102.51

O&M IP address 10.x.x.x, for example, 10.62.102.52

SJ-20121213161606-007|2013-03-14(R1.0) ZTE Proprietary and Confidential

2.2.6 Configuring a Database Listener

1. Modify the /etc/rc.d/rc.local configuration file.

2. Check the /etc/hosts configuration file.

#IP address #Machine name

l The right board configuration is as follows:

SJ-20121213161606-007|2013-03-14(R1.0) ZTE Proprietary and Confidential

#IP address #Machine name

3. Check the /etc/sysconfig/network configuration file.

l The right board information:

4. Modify the listener configuration file.

SJ-20121213161606-007|2013-03-14(R1.0) ZTE Proprietary and Confidential

(ADDRESS = (PROTOCOL = TCP)(HOST = tdrnc13_R)(PORT = 1521))

5. Configure the database NET service name.

Figure 2-2 Oracle Net Configuration Assistant: Welcome Window

SJ-20121213161606-007|2013-03-14(R1.0) ZTE Proprietary and Confidential

c. Select Add, and click Next.

SJ-20121213161606-007|2013-03-14(R1.0) ZTE Proprietary and Confidential

h. Select No, do not test, and click Next.

SJ-20121213161606-007|2013-03-14(R1.0) ZTE Proprietary and Confidential

SJ-20121213161606-007|2013-03-14(R1.0) ZTE Proprietary and Confidential

SJ-20121213161606-007|2013-03-14(R1.0) ZTE Proprietary and Confidential

Step0 Check the input parameters

Step1 Check the Linux Kernel Version

Step3 check whether directory logservice exist

Step4 Check logservice Version

Step5 check bins & libs

Step6 add ftp user zternc and omc

Step6 Finished

Step7 get system.conf

Step8 shut down arp proxy

Step10 Install New logservice Version

Step11 last check