Internal Only
ZXUR 9000 GSM OMM Commissioni
ng
Intended audience: Engineers Responsible for the ZXUR 9000 GSM
Commissioning
Released by GU Product Support Dept.
Internal Only
Version Introduction
Version
Date
Author
Checked by
R1.0
20120426
Sun Jingjing
***
Amendment Record
None
References:
1.
ZXM-OMMR (V4.12.11.40) Commissioning Guide_R1.0.doc
2.
V4 Omm and Logserver Installation Guide.docx
Internal Only
Course Objectives
:
To get to know the Logserver & OMM networking
To become familiar with the functions of the hard
ware interfaces of SBCJ and EGBS
To become familiar with the functions of the Logs
erver & OMM software
To master how to install the Logserver & OMM S
oftware
Internal Only
Contents
Introduction to the Logserver & OMM Networ
king
Introduction to the Hardware Information of t
he SBCJ and EGBS Board
Introduction to the Logserver & OMM Softwar
e
Introduction to the Installation of the Logserv
er & OMM Software
Internal Only
Structure of the Network System
NML
NMS
(CORBA/SNMP/DB/CSV
EML
NetNumen M31
DCN
iBSC
RNC
ZXUR 9000
NEL
BTS
BTS
Logserver&OMM
SBCJ
5
NodeB
Internal Only
Typical Example of the Networking of the Network Management Entities
Router
M31
Client
WAN
OMM(including the M31 client which is together
with the OMM - Bandwidth requirement of the
M31 Client
Server(far end) Bandwidth requirement of
the M31 Server
Bandwidth requirement of the NMS- M31 Server
Central Equipment Room
M31 Server
NE4 &
OMM4
NMS
M31 Client
Router
Switch
WAN
TCP/IP
LAN
WAN
Prefecture-Level City A
NE1 & OMM1
Router
Prefecture-Level City B
NE2 &
Router OMM2
NE3 &
OMM3
M31 Client
Switch
Switch
Internal Only
Contents
Introduction to the Logserver & OMM Networ
king
Introduction to the Hardware Information of t
he SBCJ and EGBS Board
Introduction to the Logserver & OMM Softwar
e
Introduction to the Installation of the Logserv
er & OMM Software
Internal Only
Location of the SBCJ and EGBS Board
When the SBCJ boards take the role of OMM, they are usually inserted in slot five and sl
ot six of the main shelf. The following work mode is adopted: 1 active board +1 standby b
oard.
The external interfaces of the SBCJ boards are provided by the EGBS boards in slot 19
and 20. The frequently-used interfaces include VGA, Keyboard, Mouse, and Ethnet.
SBCJ for OMM
Board
Shelf No.
Slot No.
Front/Rear Shelf
UMP
Main shelf
5/6
Front shelf
EGBS
Main shelf
19/20
Rear shelf
Board
Shelf No.
Slot No.
Front/Rear Shelf
UMP
Main shelf
7/8
Front shelf
EGFS
Main shelf
21/22
Rear shelf
SBCJ for OMP
The communication between OMM and OMP, or the communication between the active
and standby SBCJ is completed by the backplane of the shelf. Therefore, no cables are r
equired.
However, the network cables are required for the communication among the OMM server
, EMS Server, and OMMClient.
Internal Only
Physical Indicators and Functions of SBCJ
UMP (Universal Management Process Board)
Realize the functions of two logical boards (OMM, and OMP) by loading the software
version.
Physical board: SBCJ
Memory: 12 G; hard disk: 300G SAS*2
Function of OMM: It is responsible for the operation and maintenance of NEs. It provi
des the GE interface through the rear board EGBS, and it is connected to the EMS.
Function of OMP: It is responsible for handling the global processes and controlling t
he operation and maintenance of the whole system.
Support 1 active board + 1 standby board.
Internal Only
Introduction to the Interfaces of the EGBS Board
EGBS board
Corresponding relations between
the silkscreen of the network port and
the equipment name.
Silkscreen
Equipment Name
ETH-MP1
eth2
ETH-MP2
eth3
ETH-C1
eth4
ETH-C2
eth5
ETH-M
eth6
Internal Only
Introduction to the Hardware Information of th
e SBCJ and EGBS Board
How to use the network port equipment:
Name of the
Network Port
Equipment
Name of the
Logical
Network
Port
Function
eth2/eth3
eth2
eth3
External network port: OMC network port, EMS
and VNC access; the two network ports are not
bound, they use the active + standby mode.
eth4/eth5
bond1
Not used currently
eth6/eth7
bond2
eth6 and eth7 are bound as bond2. Several
logical network ports are mapped on bond2.
They mainly fall into two categories: 128 control
plane IP, 129 operation and maintenance
network port IP.
eth8/eth9
bond0
eth8 and eth9 are bound as 0. Several logical
network ports are mapped on bond2. They
mainly fall into two categories: the IP for the
communication between the active and standby
OMMR, and the IP for the communication
between the active and standby OMMB.
Internal Only
Introduction to Bond2
Function of the Port
Location in the
Configuration File
Channel
Number
Channel Name
NetIfName
IP
Board Ctrl Plane IP
bond2
The calculation is based on the
shelf number and slot number:
fixed IP 128.129. (16*CPU No.+1).
(128+32*shelf No. + slot No.
OMP-OMCR channel
NetIf.conf
Channel2
OMCR
bond2:1
129.200.0.1
OMP-CTS channel
NetIf.conf
Channel3
CTS
bond2:2
129.200.0.2
OMCB_TD channel
NetIf.conf
Channel4
OMCB_T
bond2:3
129.200.0.3
OMCB_UMTS
channel
NetIf.conf
Channel5
OMCB_U
bond2:4
129.200.0.4
OMCB_GSM channel
NetIf.conf
Channel6
OMCB_G
bond2:5
129.200.0.5
OMM Server
NetIf.conf
Channel1
OMM
bond2:6
129.0.100.100
RCT data switching
channel
LogNetIf.conf
Channel3
LogSvrToOMM
bond2:8
129.0.10.10
UDP Log receiving
LogNetIf.conf
Channel6
OMM_MS
bond2:7
128.0.200.200
Internal Only
Introduction to Bond0
Function of
the Port
Location in
the
Configuration
File
Channel
Number
Channel
Name
NetIfName
IP
OMM
Active/Standby
Channel
LogNetIf.conf
Channel 6
OMM_M
S
Bond0
128.0.28.1/9
OMM
Active/Standby
Channel
LogNetIf.conf
Channel 6
OMM_M
S
bond0:1
128.0.29.1/9
OMM
Active/Standby
Channel
LogNetIf.conf
Channel 6
OMM_M
S
bond0:2
128.0.30.1/9
Internal Only
External Addresses
Function of
the Port
Location in
the
Configuration
File
Channel
Number
Channel
Name
NetIfName
IP
OMM Server
LogNetIf.conf
Channel 7
OMMCLIENT
eth2:1;eth3:1
Plan it on site.
OMCB TD
CLIENT
LogNetIf.conf
Channel 8
OMCB_TCLIE
NT
eth2:2;eth3:2
Plan it on site.
OMCB UMTS
CLIENT
LogNetIf.conf
Channel 9
OMCB_UCLIE
NT
eth2:3;eth3:3
Plan it on site.
OMCB GSM
CLIENT
LogNetIf.conf
Channel 10
OMCB_GCLIE
NT
eth2:4;eth3:4
Plan it on site.
Network Port
for OMMClient
and Toolkit to
Connect to the
OMM Board
LogNetIf.conf
Channel 5
Nds
eth2:5;eth3:5
Plan it on site.
Visit the OMM
Board via the
VNC Mode
LogNetIf.conf
Channel 4
VNC
eth2;eth3
Plan it on site.
Internal Only
Contents
Introduction to the Logserver & OMM Networ
king
Introduction to the Hardware Information of t
he SBCJ and EGBS Board
Introduction to the Logserver & OMM Softwar
e
Introduction to the Installation of the Logserv
er & OMM Software
Internal Only
Structure of the Logserver & OMM Software
appli
catio
n
OM
M
database
OMMR&OMMB&Logserver
DBMS
Operating system
OS
Oracle 10g
Carrier Grade Server
Linux
Internal Only
Brief Introduction to the Logservice
The log collection function is integrated to the LogService: It collects the logs of the BSC
equipment, different kinds of real-time tracing data, or network optimization information.
Besides, it stores the data in form of data files if necessary. In this way, it can be avoided
that a lot of printed contents and tracing information are sent to the OMM through the op
eration and maintenance board. Otherwise, the system performance will be affected. On
the one hand, the maintenance engineers can check the data to improve their capability
of locating the problems more efficiently. On the other hand, the optimization engineers c
an make use of the data. They can do the statistical analysis of the data to carry out the
network optimization work. Besides, after the optimization data is analyzed, it can be pro
vided to the carrier. The carrier can make decisions (for example, expansion) on basis of
the data.
The OMMHOST function has been integrated into the Logservice, which manages the IP
addresses used by the OMM and monitors the operations status of the OMM.
The Logservice is responsible for starting and stopping the application programs like OM
MR and OMMB.
Requirements for the installation of the LogService:
Installation directory: /home/zte/logservice/
User : root
Internal Only
Introduction to the OMM
The OMM consists of OMMR and OMMB.
The OMMR is the network management software of the controller. It is responsible for the maint
enance of the data configuration of the controller, collection of the performance data, and repres
entation of the alarms.
The OMMB is the network management software of the base station. Its function is similar to th
at of the OMMR, that is, it is responsible for the daily maintenance of the base station.
After the two application programs are started, they provide the ftp service separately. They are
connected to different NEs, they visit different database instances, and they are bound to differe
nt logical network ports.
Requirements for the installation of the OMM
All the OMM application programs must be installed under the /home directory.
During the installation of the OMM, the installation path of the database files must be created on
the /oracledata partition.
It is suggested that the OMMR should be installed under the /home/omm/ZXM-OMMR directory
and the OMMB should be installed under the /home/ZX-OMMB/ directory. If several OMMBs are
installed, the operator can create a new file under the /home directory. It is forbidden to install th
e OMM processes under any other directory instead of the /home directory.
User: root
Internal Only
Important Logservice Configuration Files
The configuration files are under the following directory: /home/zte/log
service/bin/conf.
Network port address
configuration files
LogNetIf.conf and NetIf.conf
Mo and OMM process
startup configuration file
OmmProcConfig.conf
Log process startup
configuration file
Version information
configuration file
LogProcConfig.conf
LogserviceVerInfo.conf
Board location
configuration file
BrdPhyAddr.conf
Work mode configuration
file
System.conf
Internal Only
Function of the Py Script
Use the script to set the host name according to the location of the board (left
board or right board).
Use the script to complete the ip related configurations of the active/standby ch
annels according to the location of the board (left board or right board).
Set the port mapping: The mapping relation exists between 20021 and 21.
Set the oracle database instances which are started together with the system.
Complete the relevant configurations for the listener and tnsname.
Disable the ARP agent function of the system.
Modify the auto-start service type of the operating system.
Set the VNC IP address to do the operation and maintenance work. Set the tw
o floating IP addresses through which the OMMR and OMMB communicate wit
h the the EMS respectively.
Set the ntp clock server.
Internal Only
Contents
Introduction to the Logserver & OMM Networ
king
Introduction to the Hardware Information of t
he SBCJ and EGBS Board
Introduction to the Logserver & OMM Softwar
e
Introduction to the Installation of the Logserv
er & OMM Software
UMP (OMM) Environment Provided by the Ma
nufacturer
Internal Only
The 64-bit Linux operating system CGSL V3.01.12 provided by the Ch
engdu R & D Center is already installed.
The logservice is already installed, but it needs to be updated accordin
g to the planned version during the commissioning process.
The oracle is already installed.
Five database instances are already installed: v4omcr/gomcb/gultomc
b/tomb/womcb.
The following users and passwords are already created by the operati
ng system:
root/root123
omm/Omm_123(/home/omm)
oracle/Oracle_123
zte/Zte_1234
The following services are provided: VNC, SSH, FTP, and telnet.
By default, the external IP address is as follows: 119.0.200.200.
Installation of the OMM and Logserver Softwa
re
Internal Only
1.
2.
IP address planning
Do the IP address planning for the OMMServer service and for the active/standby SBCJ board
management.
For the control plane and media plane inside, the default configuration of the active/standby n
etwork port can be used directly without any planning or modification.
Install the target version of the Logservice
The Logservice software is released together with the software version of ZXUR 9000 : \GsmT
ools\logservice_V6.50.100*_SBCJ.zip
Check the Logservice version which is provided when the product is delivered. If it is not the ta
rget version, it should be uninstalled first and then the target version can be installed.
3.
Execute and set the script related to the OMM environment parameters.
The script is released together with the OMMR version: (\ums-svr\tools\ommconf).
omm_conf.py is the main script.
Main functions of the script:
Clarify the location of the board: left board or right board.
Configure the OMM related ip addresses. Actually, this is realized by modifying the configuration files (Lo
gNetIf.conf and NetIf.conf ) of the Logservice.
Configure the auto-start function of the database instances and the auto-start function of the omm. Confi
gure the relevant listener and tnsname file.
Internal Only
Installation of the OMM and Logserver Softwa
re
4.
5.
6.
Install the OMMR.
Install the OMMB.
Check and configure the environment parameters.
7.
Configure the OMCB channel.
8.
9.
Configure the OMCHOME parameter.
Configure the startup path of omm.
Configure the script which is capable of cleaning the database periodically.
Configure the OMCB route by using the content of the Netif file.
Configure /etc/sysctl.conf. Enable the IP forwarding function.
Set the OMMR configuration data.
Install the standby SBCJ board.
Check the active/standby environment and synchronize the data of the active
OMM.
Internal Only
Chapter/Course Review
Please make a brief description of the main installation procedures of the
OMM and Logservice software.
Internal Only
