Internal Use Only

R&B Split Operation

Applicable to Staff with Skill Certificate Level II or Lower
Released by GU Product Support Dept.

Internal Use Only

Version Introduction
Version

Date

Author

Checked by

R1.0

2011-02-10

Chen Qi

***

Amendment Record
First published

References:
1.

071 ZXG10 ISMG Board Server (SBCX) Commissioning Guide (Professional)V3.2.doc

Internal Use Only

Course Objectives:
To understand the version knowledge and background
of R&B split
To know the preparation for R&B split
To master the operation of R&B split
To understand R&B split scripts

Internal Use Only

Contents
Introduction to R&B Split
Preparation for R&B Split
Operation of R&B Split

Internal Use Only

Introduction to R&B SplitBasic Concepts

R&B Integrated Version

OMCB Version

R&B integrated version refers to one set of software that integrates the fun
ctions of OMCR and OMCB; the OMCB part manages SDRV4.00 series. F
or example: iOMCRV6.20.614c-OMCBV4.00.200m.
OMCB version refers to the software that only has the function of OMCB. F
or example, ZXOMCBV4.09.21.05.

Transformation to R&B Split

Improve the SBCX that is only installed with iOMCRV6.20.61 R&B integrat
ed version; install both R&B integrated version and OMCB version on the s
ame SBCX.
After the transformation, the following improvements can be realized:
Management of SDR4.09 series;
Decoupling of SDR version and iBSC version, synchronous upgrade of O
MCB and SDR, synchronous upgrade of OMCR and iBSC.

Introduction to R&B SplitStructure of R&B Spl

it
Internal Use Only

Internal Use Only

Contents
Introduction to R&B Split
Preparation for R&B Split
Operation of R&B Split

Preparation for R&B SplitResource Allocati

on 1

Internal Use Only

Application program & user: R&B integrated version and OMCB

version respectively use their own user. Their application progra
ms should be respectively installed under their user directory.

Database instance: R&B integrated version and OMCB version u

se their own database instance.

R&B integrated version: user-gomcr, installation directory- /home/gomcr

OMCB version: user- gomcb, installation directory- /home/gomcb/ZXGOMCB

Instance name of R&B integrated version: gomcr

Instance name of OMCB version: gomcb

Disk: Disk partition remains unchanged; the storage paths for dat
abase table space files are different.

R&B integrated version: /oracledata/gomcr (Note: In the original inst

allation environment the data files may be stored under /oracledata,
which can remain unchanged during the transformation to R&B spli
t.)
OMCB version: /oracledata/gomcb

Preparation for R&B SplitResource Allocati

on 2

Internal Use Only

Memory: The memory is mainly used by database SGA and PG

A, and JVM of the application program. Except for the physical
memory consumed by the operation system, the rest physical
memory is distributed between OMCR R&B integrated version
and OMCB version.

The distribution formulas of 8G and 4G memory are as follows:

Distribution of
8G

R&B
Combined
Version

OMCB
version

Distribution of
4G

R&B
Combined
Version

OMCB
version

Database
instance

30%

20%

Database
instance

20%

20%

CONSOLE JVM

128M

128M

CONSOLE JVM

128M

128M

FTPSERVER
JVM

128M

128M

FTPSERVER
JVM

128M

128M

BACKUP JVM

256M

128M

BACKUP JVM

256M

128M

UMS-SVR JVM

1400M

1024M

UMS-SVR JVM

1000M

512M

Note: 8G memory should be used for the commercial environment of R&B

split.

Preparation for R&B SplitResource Allocati

on 3

Internal Use Only

CPU: R&B integrated version and OMCB version share the

CPU resource.
Network: R&B integrated version and OMCB version share
one physical interface, but use different IP addresses.

Preparation for R&B SplitResource Allocati

on 4

Internal Use Only

Network card of R&B integrated version

Network card

Remarks

Instance of IP address

eth3

The IP for the communication with EMS

and the Client of R&B integrated
version.

10.128.41.223

eth4

The IP for the communication with

V4.00 series base stations.

172.30.3.254

eth6

The IP for the communication with OMP

Network card of OMCB version

Network card

Remarks

Instance of IP address

eth3:1

The IP for the communication with EMS

and the Client of OMCB version.

10.128.41.213

eth4:1

The IP for the communication with V4.09

series base stations.

172.30.3.253

Note: The newly-added IP address of OMCB version and the original

address should be in the same sub-network.

Preparation for R&B SplitOther Prerequisite

s

Internal Use Only

Before the transformation to R&B split, the R&B integrated versi

on is required to be upgraded to iOMCRV6.20.614c-OMCBV4.0
0.200m of the later version.
Before the transformation to R&B split, the appropriate network
cards must be adopted according to the SBCX installation speci
fications; use eth3 for external network, eth4 for OMCB channel
, and eth6 for internal network . Make adjustments, if the three
network cards are not adopted.
Before the transformation, eth4:1 and eth3:1 IP addresses are
obtained, and they should in the same sub-network with the ori
ginal network card.
Before the transformation, Minos is upgraded to EMSV12.
The password of root user should be obtained.

Internal Use Only

Contents
Introduction to R&B Split
Preparation for R&B Split
Operation of R&B Split

Operation of R&B SplitInstallation of OMCB

Version Database Instances

Internal Use Only

Install the database instances of OMCB version according to the Com

missioning Guide.
Installation method: Log in to VNC with user Oracle, run dbca, select C
reate Database.

Relevant parameters:
Database mode: transaction processing
Database instance name: gomcb
Data file storage path: /oracledata/gomcb
Memory: 4G 20% 8G 20%
Security check:

$ export ORACLE_SID=gomcb
$ sqlplus sys/oralce as sysdba
SQL> shutdown immediate
SQL> startup
SQL> quit
$ lsnrctl stop
$ lsnrctl start

Operation of R&B SplitOMCB Version Install

ation 1

Internal Use Only

Upload and unzip R&B split script- rb_split.zip

Uploading path: /home/installtmp/RB_split

Unzip script: unzip rb_split.zip
The script is composed of:

rb_split.sh main script for the R&B split

rb_split_gomcb.sh modifying parameters related to OMCB version
rb_split_gomcr.sh modifying parameters related to R&B integrated versi
on
rb_split_oracle.sh modifying parameters related to Oracle database inst
ances
rb_split_root.sh modifying parameters related to the user and environm
ent
dbora database auto-start script
ismg application program auto-start script

Run the script

Run the script with user root: [root]#sh rb_split.sh

Operation of R&B SplitOMCB Version Instal

lation 2

Internal Use Only

Pre-check the script execution

Print of failed check: PreCheck not passed,correct problems,then run rb_split.sh a

gain.

An instance of successful check:

**************************PreCheck Process************************
Checking ORACLE_HOME....../oracleapp/oracle/product/10.2.0
Checking OMCR user........success(GOMCR=gomcr)
Checking OMCR version
success(GOMCR_OMCHOME=/home/gomcr/ZXGOMCR/ums-svr)
Checking OMCR database....success(GOMCR_SID=gomcr)
Checking OMCB user........success(GOMCB=gomcb)
Checking OMCB version.....failure(OMCHOME not exists)
Checking OMCB database....failure(database not exists)
Checking interface eth3...success(IP 10.63.208.181 NETMASK 255.255.255.0)
Checking interface eth4...success(IP 172.29.11.1 NETMASK 255.255.255.0)
Checking interface eth6...success(IP 172.20.11.1. NETMASK 255.255.255.0)
PreCheck passed.
Confirm variables,and then type 'y' to continue,'q' to quit:

Note: It should be confirmed that the content of each checked item is con
sistent with the actual situation.
It is normal that the check of OMCB version and OMCB database fails.

Operation of R&B SplitOMCB Version Instal

lation 3

Internal Use Only

Network card setting 1: According to the IP planning, input the I

P addresses of eth3:1 and eth4:1.

Interface eth3:1 IP: 10.63.208.235

Interface eth4:1 IP: 172.29.11.2

The print of successful network card setting:

Create interface eth3:1 success
Bring up interface eth3:1 success
Modify /etc/hosts success
Create interface eth4:1 success
Bring up interface eth4:1 success
File /etc/host.conf already configured
rb_split_root ip success.

Relevant configuration files:

/etc/sysconfig/network-scripts/eth3:1
/etc/sysconfig/network-scripts/eth4:1
/etc/host.conf
/etc/hosts

Operation of R&B SplitOMCB Version Instal

lation 4

Internal Use Only

Network card setting 2: instances of configuration files

/etc/sysconfig/network-scripts/eth3:1
DEVICE=eth3:1
BOOTPROTO=none
BROADCAST=10.63.208.255
HWADDR=00:19:C6:3E:68:AC
IPADDR=10.63.208.213
NETMASK=255.255.255.0
NETWORK=10.63.208.0
ONBOOT=yes
TYPE=Ethernet
USERCTL=no
IPV6INIT=no
PEERDNS=yes
GATEWAY=10.63.208.254

/etc/host.conf
order hosts,bind
multi on

/etc/hosts
10.62.102.55
10.62.102.155
127.0.0.1

sbcx55
sbcx55
localhost.localdomain localhost

Note: When R&B

split is adopted, it is
forbidden to modify
network card settings
through graphical
interfaces. Otherwise,
the records of hosts
will be lost.

Operation of R&B SplitOMCB Version Installatio

n5

Internal Use Only

NTP server setting: After the transformation to R&B split, the NTP serve
r attached to the OMM program will be stopped, and the NTP server att
ached to the operation system will be started.

Modify iptables server, and cancel the port mapping from 20123 to 123.
Modify /etc/sysconfig/iptables success
Restart iptables success

Input EMSIP as the NTP server IP, complete the settings of NTP client and server, an
d start NTPD server.
Upper NTP Server IP=10.62.100.45,are you sure? [y|n]: y
Modify /etc/ntp.conf success
Restart ntpd success
rb_split_root ntp success.

An instance of the configuration file after the execution of script:

#vi /etc/ntp.conf
server 10.62.100.45
#server 0.rhel.pool.ntp.org
#server 1.rhel.pool.ntp.org
#server 2.rhel.pool.ntp.org
#server 127.127.1.0
#fudge 127.127.1.0 stratum 10

Operation of R&B SplitOMCB Version Installati

on 6

Internal Use Only

Modify /etc/profile

No information needs to be input in this step. The prompt of successful modification of

/etc/profile is shown below:
Modify /etc/profile success
rb_split_root profile success.

An instance of /etc/profile is as follows:

#SPLIT MODIFICATION BEGIN
ORACLE_BASE=/oracleapp/oracle
ORACLE_HOME=/oracleapp/oracle/product/10.2.0
NLS_LANG=AMERICAN_AMERICA.ZHS16GBK
if [ "$USER" = "gomcb" ]; then
ORACLE_SID=gomcb
OMCHOME=/home/gomcb/ZXGOMCB/ums-svr #gomcb installation path is fixed; the future gomcb insta
llation path shall be consistent.
else
ORACLE_SID=gomcr
OMCHOME=/home/gomcr/zxgomcr/ums-svr
#gomcr installation path is automaticallyacquired from th
e current environment variables.
fi
PATH=$PATH:/bin:/usr/bin:/sbin:/usr/sbin:/usr/local/sbin:$ORACLE_HOME/bin:$OMCHOME/bin:$OMCHOM
E/../jdk-linux/bin
export ORACLE_SID ORACLE_BASE ORACLE_HOME NLS_LANG PATH OMCHOME
#SPLIT MODIFICATION END

Operation of R&B SplitOMCB Version Instal

lation 7

Internal Use Only

Stop R&B integrated versio

n
Stop GOMCR version. After confir
mation, input y to continue the ex
ecution of the script.
Stop GOMCR version,are you sure? [y
|n]: y
......
Stop GOMCR version success
rb_split_gomcr stop success.

Modify the database parameters of

R&B integrated version
The script automatically modifies the memory
parameters of R&B integrated version database.
Current system memory=4G
SGA_TARGET=960M PGA_TARGET=240M
System altered.
System altered.
System altered.
Database closed.
Database dismounted.
ORACLE instance shut down.
ORACLE instance started.
Total System Global Area 1006632960 bytes
Fixed Size
1271228 bytes
Variable Size
620759620 bytes
Database Buffers
377487360 bytes
Redo Buffers
7114752 bytes
Database mounted.
Database opened.
Modify GOMCR database parameters success
rb_split_oracle gomcr success.

Operation of R&B SplitOMCB Version Instal

lation 8

Internal Use Only

Confirm that R&B integrated versi

on is one of V 6.20.61 series
When the OMCR integrated version is one
of V6.20.6xx series, input y to continue th
e execution; otherwise, open a new login w
indow, and upgrade OMCR version. After t
he upgrade is completed, return to the exe
cution window of R&B split script, and inpu
t y to continue the execution.
step 6:
Upgrade OMCR version first,and then type 'y' to
continue.
OMCR version already upgraded? [y|n]: y
OMCR version upgrade confirmed.
rb_split_prompt upgrade_omcr_ver success.

Note: Upgrade of R&B integrated version i

s required to be completed before the tran
sformation, so that we can directly input y
and continue the script execution.

Modify the JVM parameters of

R&B integrated version
Based on the current memory status,
the script automatically modifies the
JVM parameters of R&B integrated
version.
Current system memory=4G
UMS-SVR JVM=-Xmx1000m
Modify set-jvm.param.sh success
BACKUP JVM=-Xms128m -Xmx256m
Modify backup-linux.sh success
FTPSERVER JVM=$JAVA_OPTS
-Xmx128m -Xms64m
Modify ftpserver-linux.sh success
CONSOLE JVM=-Xms64m -Xmx128m
Modify run-linux.sh success
rb_split_gomcr jvm success.

Operation of R&B SplitOMCB Version Instal

lation 9

Internal Use Only

Modify the IP address binding of R&B integrated version

Modification of the following version files is completed in this step.

/ums-svr/deploy/deploy-010muep.properties
muep-install-issplit=1 1 represents R&B split
/ums-svr/deploy/deploy-gsmomcr01.properties
muep-common-sbcx-type=0 represents R&B integrated version in R&B split process
userdefined-uep-psl-clocksync.port=0 means that NTP server is not to be started
/ums-svr/deploy/deploy-999split.properties
ums.systemproperty.com.zte.ums.uep.localaddress=10.63.208.181 eth3 IP address
ums.systemproperty.com.zte.ums.bind.socket.client.ip=128.0.30.8
eth4 IP address
ums.services.bind.multi.local.addresses=128.0.30.8, 129.0.0.3 eth4,eth6 IP address

The modification process is as follows:

Modify deploy-010muep.properties success
Modify deploy-gsmomcr01.properties success
Modify deploy-999split.properties success
rb_split_gomcr ip success.

Operation of R&B SplitOMCB Version Instal

lation 10

Internal Use Only

Start R&B integrated version: The script automatically starts R&

B integrated version. The execution of the script is as follows:
GOMCR version is running,restart
If GOMCR is running, make sure it can be stopped, and input y and continue th
e execution.
Stop GOMCR version,are you sure? [y|n]: y
......
Stop GOMCR version success
Start GOMCR version success
rb_split_gomcr start success.

Create gomcb user: The script automatically creates gomcb us

er, with default initial password-gomcb123. The creation proces
s is as follows:
Create group gomcb success
Create user gomcb success
rb_split_root gomcb success.

Operation of R&B SplitOMCB Version Instal

lation 11

Internal Use Only

Create gomcb database instance

As gomcb database instance is created previously, input y and continue
the execution of the script. The execution process is shown below:
Install OMCB database first,and then type y to continue
OMCB database already installed? [y|n]:
Checking OMCB database success(GOMCB_SID=gomcb)
OMCB database installation confirmed.
rb_split_prompt install_omcb_db success.

Modify net8 setting of gomcb instance

Add GOMCB, GOMCB_IP, and GOMCB_127.0.0.1 in tnsnames.ora. The
execution process is as follows:
Modify /oracleapp/oracle/product/10.2.0/network/admin/tnsnames.ora success
rb_split_oracle gomcb success.

Operation of R&B SplitOMCB Version Instal

lation 12

Internal Use Only

Install OMCB version

Currently the installation script of OMCB version is not available. Ope

n a new login window.
Install the server with OMCB version according to the Commissioning
Guide.
Install OMCB version first, and then type 'y' to continue.
OMCB version already installed? [y|n]: Do not fill it in immediately. Install OMCB vers
ion first in a new window, and then return to fill it in.

Operation of R&B SplitOMCB Version Instal

lation 13

Internal Use Only

Key points in OMCB version installation:

Use user root, and install through vnc.

Install OMCB version at both the server end and the client end.
It must be installed under the path: /home/gomcb/ZXGOMCB, because the environ
ment variables in profile adopt the fixed values.
Choose the IP address of eth3:1 as the database IP address.
Choose small mode as the database installation mode.
The database installation path is: /oracledata/gomcb.
OMCB server address is eth4:1 address.
The main clock address is eth3:1.
Set RB Split with Yes.

After OMCB version installation, return to the original execution windo

w.
Modify /home/gomcb priviledge success
Modify /home/gomcb owner success
OMCB version installation confirmed.
rb_split_prompt install_omcb_ver success.

Operation of R&B SplitOMCB Version Instal

lation 14

Internal Use Only

Modify the JVM parameters of OMCB version

According to the current memory status, the script automatically
modifies the JVM parameters.
Current system memory=4G
UMS-SVR JVM=-Xmx512m
Modify set-jvm.param.sh success
BACKUP JVM=-Xms64m Xmx128m
Modify backup-linux.sh success
FTPSERVER JVM=$JAVA_OPTS -Xmx128m -Xms64m
Modify ftpserver-linux.sh success
CONSOLE JVM=-Xms64m -Xmx128m
Modify run-linux.sh success
rb_split_gomcb jvm success.

Operation of R&B SplitOMCB Version Instal

lation 15

Internal Use Only

Modify the IP address binding of OMCB version

Modification of the following OMCB version files is completed in this step.

/ums-svr/deploy/deploy-010muep.properties
muep-install-issplit=1 1 represents R&B split
/ums-svr/deploy/ deploy-030guomcb.properties
muep-common-sbcx-type=1 represents R&B integrated version in R&B split process
/ums-svr/deploy/deploy-999split.properties
ums.systemproperty.com.zte.ums.uep.localaddress=10.63.208. 235 eth3:1 IP address
ums.systemproperty.com.zte.ums.bind.socket.client.ip= 172.29.11.2 eth4 :1IP address
ums.services.bind.multi.local.addresses= 172.29.11.2
eth4:1 IP address
/ums-svr/deploy/deploy-defaultproperties
userdefined-uep-psl-clocksync.port=0 means that adopted NTP server is not to be started

The modification process is as follows:

File deploy-010muep.properties already configured
Modify deploy-030guomcb.properties success
Modify deploy-999split.properties success
rb_split_gomcb ip success.

Operation of R&B SplitOMCB Version Instal

lation 16

Internal Use Only

Start OMCB version

The script automatically starts OMCB version. The execution of the script is as
follows:
GOMCB version is running,restart
If GOMCB is running, make sure it can be stopped, and input y and continue the execution.
Stop GOMCB version,are you sure? [y|n]: y
2010-12-16 13:27:56,668
Stopping result:
----------------------------Stop ums[PID=21936] successfully.
----------------------------Stop ftp[PID=21962] successfully.
----------------------------2010-12-16 13:27:57,051
Close console successfully.
Stop GOMCB version success
Start GOMCB version success
rb_split_gomcb start success.

Operation of R&B SplitOMCB Version Instal

lation 17

Internal Use Only

Set database instances and auto-start of R&B integrated version/OMC

B version
The script automatically sets database instances and auto-start of R&B integrated ver
sion/OMCB version. The script execution process is as follows:
rb_split_root autostart success.

The detailed operation is shown below:

Back up the original dbora file and ismg file under /etc/init.d.
Based on the actual situation of the equipment, make appropriate modifications to t
he new dbora file and ismg file.
Copy the new dbora file and ismg file to under /etc/init.d.
In /etc/rc0.d and /etc/rc6.d, create the links for closing the database and the applica
tion program.

lrwxrwxrwx 1 root root 17 Sep.10 13:49 K10dbora -> /etc/init.d/dbora

lrwxrwxrwx 1 root root 16 Sep. 11 11:51 K10ismg -> /etc/init.d/ismg

In /etc/rc3.d /etc/rc5.d, create the links for starting the database and the applicati
on program.

lrwxrwxrwx 1 root root 17 Sep. 10 12:46 S99dbora -> /etc/init.d/dbora

lrwxrwxrwx 1 root root 16 Sep. 10 12:46 S99ismg -> /etc/init.d/ismg

Operation of R&B SplitOMCB Version Instal

lation 18

Internal Use Only

Post-R&B split check

Perform a check after R&B split is completed. If the split is successful, it prints:
"Passed."
********************PostCheck Process**************************
Passed.
Split process recorded in log file /tmp/rb_split_xxxxxxxxx.log

The process files of R&B split

The process files are saved under /tmp.

Running log file rb_split_XXXXX.log
Running log file rb_split.dat is used to record the executed steps, which are skipped in the repe
titive script execution.
Running variable file rb_split.var is used to record the relevant variables, such as IP address, da
tabase instance name, etc.

When a problem appears, we can carry out investigation through the three files or send
them back to the technical support for analysis.
File packing methos: tar cvf rb_split.tar /tmp/rb_split*

Operation of R&B SplitCheck of OMCB Ver

sion Installation

Internal Use Only

Check OMCB version

Use user gomcb.

Check whether the process of OMCB version is normal.
$ps ef | grep java | grep gomcb
The result contains three processes:
BoostMain
FtpServer
BootMain

Stop OMCB version

$pkill -9 java //Use user gomcb only; user root will stop gomcr process.
pkill: 4273 - Operation not permitted
pkill: 5632 - Operation not permitted
pkill: 5645 - Operation not permitted //gomcr process can not be stopped.

Start OMCB version

$ cd /home/gomcb/ZXGOMCB/ums-svr/bin/
$ nohup ./console-linux.sh &

Internal Use Only

Operation of R&B SplitCheck of Auto-Start

Check

auto-start according to the following steps:

#cd /etc/init.d
#vi ismg
#vi dbora
In case of special on-site environment, modify environment variables GOMCR_HOME and GOMCB_HOME.
dbora
ORA_HOME=/oracleapp/oracle/product/10.2.0
ORA_OWNER=oracle
GOMCR_SID=gomcr
GOMCB_SID=gomcb
ismg
GOMCR=gomcr
GOMCR_OMCHOME=/home/gomcr/ums-svr
GOMCB=gomcb
GOMCB_OMCHOME=/home/gomcb/ZXGOMCB/ums-svr

Run

the following script to verify whether the database can be normally booted and
used.
#/etc/init.d/dbora stop
#/etc/init.d/dbora start
#/etc/init.d/ismg stop
#/etc/init.d/ismg start

Finally,

we can reboot the server and check whether it can be booted normally.

Operation of R&B SplitInstallation & Login o

f Client, Post-Installation

Internal Use Only

Install OMCB version client

Use R&B integrated version client and OMCB version c
lient to respectively log on to their server, and make su
re their logon process is normal.
Make sure links can be established in the SDR sites co
nfigured on R&B integrated version.
Create OMCB NE agent on EMSV12, and make sure it
can boot normally.

Internal Use Only

Course Review

What is the background and purpose of R&B split?

What preparations should be made before R&B split?
What are the operation procedures of R&B split?

Internal Use Only