ZXWR RNC-SBCX master/slave configuration

Product

ZXWR RNC/GUBSC/GU Wireless

System/GU

Network
Management
Version

Equipment
Hardware
Version

V3

Equipment
Software
Version

V3.11.10.11P04

Board
Hardware
Version

Board Software
Version

Incident Error
Code

Page Views

51

Knowledge No.

WHD20130723652587

Author

ChenShi

Incident Description (Incident Phenomena)

Configure two OMM SBCX from cold master/slave to real master/salve relation which is controlled
by OMMHost.
Networking Environment

Problem Cause Analysis

The general configuration document is only related to old RNC version.

But current RNC version of THU is V3.11.10.11P04, so we supply a new operation document to
customer about the configuration.
Solution
This document will describe the procedure of correcting SBCX from single configuration to
master/slave configuration. In this document, the used SBCX in single SBCX mode is called
master SBCX, and another SBCX is called slave SBCX.
1. Pre-work

Currently, the new OMCR and OMCB server are running in master SBCX, and old
OMCR and OMCB server are running in slave SBCX. To correction, the OMM server
version and configuration should be the same in both SBCXs.

There are two methods to make sure the consistence in both SBCX:

Using mirror copy from master SBCX to slave SBCX

Upgrade OMM in slave SBCX and install necessary patches, then restore oracle data from
master SBCX to slave SBCX
The 1st method is recommended.
For the 2nd method, following steps should be considered:
The OMM upgrade guide
For new version OMCR, following patch should be installed:
For new version OMCR, following patch should be installed:
The oracle data export/import scripts are stored in /home/oracle directory

2. Master/slave configuration in slave SBCX

2.1 Check zte user in system, if the user is not exist, create it and add it to ftp and root group.
[Sector 4.1 of the document OMM installation]
2.2 Check /etc/rc.d/rc.local. Add command . /etc/profile in the file, comment the commands
which are used to start OMM server and add static route together with system reboot. And other
custom defined commands can be left.
[Sector 4.1 of the document OMM installation]
2.3 Upload and unzip OmmHost package.
The package can be found in directory \WRNCV3.11.10.11P07_0315\Ver.ext\RncTools\OmmHost
of RNC version package. The version of OmmHost should be same as RNC real running version.
[Sector 4.3 of the document OMM installation]
2.4 Install OmmHost, the root user is used to install. [Sector 4.4 of the document OMM
installation]
2.5 Modify the OmmHost configuration by Master/Slave tool.
The tool is in the some directory of OMMR software package, not the directory of OMMR server.
The detail directory is usually /home/WOMCR3.11.10.11P02/zxwomc/ums-svr/tools/zxwomc-

tools-rnc/MasterSlaveCfgTool. Run script bin/MasterSlaveCftTool.sh to start tool.

Please use the tool in OMCR version package, and dont use the tool in document.
Choose type of SBCX, all 3G SBCXs in Hungary are SBCX(060202). Then click [OK].
Some remark:
The OmmHost Install Path is depend on where OmmHost.zip is unzipped.
In live SBCX, the OMMR and OMMB server install paths are usually /home/womc/ZXWRRB/WOMC and /home/ZX-OMMB. The command ps- A | grep java can be used to check
real path.
The value of Province RNC No. and Local RNC No. should be in the range of [0, 63].
The SID of OMMR is womc and SID of OMMB is womcb.
Select [Left Board] or [Right Board] according to real situation.
The button [Load from File] will fill parameters automatically to Ethernet card
configuration. But after loading, please check the configuration one card by one card, and
correct the mistakes.
The OMCB Gateway, OMCB Subnet Prefix and OMCB Subnet Mask can be configured in one
of the eth6:1 and eth6;2 page. Configuring in one page is enough.
After click button [Modify Files], the related files will be modified automatically, and you
can find the modification result from [Files Browser] page.
2.6 Modify parameters manually
After configuration by Master/Slave Config tool, some files still should be checked and modified
manually. The related parameters are followed:
Disable Ethernet port auto-start except Eth2. [Sector 4.9 of the document OMM
installation].
Check binding IP in OMCR server. The full path OMCR IP binding file is /home/womc/ZXWRRB/WOMC/ums-svr/deploy/deploy-999split.properties. The IP which marked red below
should be the same as IP in eth6:1. If not equal, modify them.

[root@ZRNC98 deploy]# pwd

/home/womc/ZXWR-RB/WOMC/ums-svr/deploy
[root@ZRNC98 deploy]# more deploy-999split.properties
ums.systemproperty.com.zte.ums.uep.localaddress=10.28.31.204
ums.systemproperty.com.zte.ums.bind.socket.client.ip=10.9.98.146
ums.services.bind.multi.local.addresses=10.9.98.131,10.9.98.146,128.0.30.1,128.0.30.9
[root@ZRNC98 deploy]#
The Ethernet card control files NetIf00.conf, NetIf01.conf and NetIf02.conf in OmmHost are
stored in /home/zte/OmmHost/bin/conf. Copy NetIf00.conf to NetIf01.conf and NetIf02.conf
to make sure the three files are same.
[root@ZRNC98 deploy]# cd /home/zte/OmmHost/bin/conf/
[root@ZRNC98 conf]# pwd
/home/zte/OmmHost/bin/conf
[root@ZRNC98 conf]# ls
BrdPhyAddr.conf
NetIf00.conf

NetIf01.conf

OmmProcConfig.conf

system.conf

NetIf01.conf.bak OmmProcConfig.conf.bak system.conf.bak

NetIf00.conf.bak NetIf02.conf

SysPrnCtrl.conf

[root@ZRNC98 conf]# cp NetIf00.conf NetIf01.conf

cpwhether coverNetIf01.conf? y
[root@ZRNC98 conf]# cp NetIf00.conf NetIf02.conf
cpwhether coverNetIf02.conf? y
[root@ZRNC98 conf]#

2.7 Basic Test

Reboot slave SBCX, checking following issues after restart:
Checking the running status of slave SBCX according to sector 8.2 of the document OMM
installation;
The green run light in SBCX will be flashing one time per second.
The master/slave SBCXs will be displayed in rack view of EMS client after OmmHost is
running;
Check route configuration, including default route and the route to NodeB management IP
subnet;
Try to connect OMCR and OMCB server by client to confirm the server is running normally.
3. Master/slave configuration in master SBCX
3.1 Unplug the cables which are connected OMC2 and OMP1 in master SBCX, and plug the cables
to connect OMC2 and OMP1 ports in slave SBCX. Using EMS client to check OMM status, following
issues should be checked:
Ping OMCB and OMCR external IPs to make sure both external IPs are accessible;
Try to start NE Management;
Check the link status of RNC and NodeB in OMCR and OMCB;
Check alarms, some alarms like slave board offline will be reported.
3.2 Configure master/slave according to the same procedure as 2.1~2.6. During the
configuration, it is not necessary to stop OMCR and OMCB in SBCX since only some files will be
modified. But after modification, please restart SBCX.
3.3 Check running status of SBCX according to sector 8.3 of document OMM installation.
3.4 Data Synchronization, the synchronization procedure includes two parts:
Stop OmmHost in slave SBCX to synchronize all oracle data;
Start OmmHost in slave SBCX to synchronize data in running time.

Both the data in OMCR and OMCB should be synchronized, the synchronization tool is stored in
ums-svr/tools/backup/, there are four options for synchronization script:
The option 1 and 2 are used to synchronize all oracle data, the exp/imp function is used;
The option 3 is used to synchronize running time data, the ftp service is used;
The option 4 is used to compare data in both SBCX.
[root@ZRNC98 backup]# ./dbsync-linux.sh oracle
@WORK_DIR@ /home/womcb/ums-svr/tools/backup
@JAVA_CMD@
2013-06-13 14:05:42,184 INFO [DBSyncProcess] Welcome to use the database synchronise
tool.
2013-06-13 14:05:42,186 INFO [DBSyncProcess] 1. Synchronise all tables which configed by
the tableConfig-dbsync*.properties.
2013-06-13 14:05:42,187 INFO [DBSyncProcess] 2. Synchronise the history tables of Fault
Management(FM) and Performance Management(PM)
2013-06-13 14:05:42,187 INFO [DBSyncProcess] 3. Synchronise the Performance
Management(PM) file
2013-06-13 14:05:42,188 INFO [DBSyncProcess] 4. Compare the local database data and the
remote.
2013-06-13 14:05:42,188 INFO [DBSyncProcess] Please select 1 , 2 , 3 or 4:
3.5 Changeover Test: Two ways are described in chapter 10 of OMM installation document, and
invoking changeover from EMS client is also available.

3.6 Smartdaemon should be installed in both SBCX.