Sei sulla pagina 1di 37

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 Amendment Record

R1.0 2011-02-10 Chen Qi *** 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 Split—Basic Concepts


 R&B Integrated Version
 R&B integrated version refers to one set of software that integrates the
functions of OMCR and OMCB; the OMCB part manages SDRV4.00
series. For example: iOMCRV6.20.614c-OMCBV4.00.200m.
 OMCB Version
 OMCB version refers to the software that only has the function of OMCB.
For example, ZXOMCBV4.09.21.05.
 Transformation to R&B Split
 Improve the SBCX that is only installed with iOMCRV6.20.61 R&B
integrated version; install both R&B integrated version and OMCB version
on the same 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
OMCB and SDR, synchronous upgrade of OMCR and iBSC.
Introduction to R&B Split—Structure of R&B Internal Use Only

Split
SBCX

OMCR OMCB

Database
Database

Disk Disk Memory Memory

CPU CPU Network Network


Internal Use Only▲

Contents

Introduction to R&B Split


Preparation for R&B Split
Operation of R&B Split
Preparation for R&B Split—Resource Internal Use Only

Allocation 1
 Application program & user: R&B integrated version and OMCB
version respectively use their own user. Their application
programs should be respectively installed under their user
directory.
 R&B integrated version: user-gomcr, installation directory- /home/gomcr
 OMCB version: user- gomcb, installation directory- /home/gomcb/ZXGOMCB
 Database instance: R&B integrated version and OMCB version
use their own database instance.
 Instance name of R&B integrated version: gomcr
 Instance name of OMCB version: gomcb
 Disk: Disk partition remains unchanged; the storage paths for
database table space files are different.
 R&B integrated version: /oracledata/gomcr (Note: In the original
installation environment the data files may be stored under
/oracledata, which can remain unchanged during the transformation
to R&B split.)
 OMCB version: /oracledata/gomcb
Preparation for R&B Split—Resource Internal Use Only

Allocation 2
 Memory: The memory is mainly used by database SGA and
PGA, 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 R&B OMCB Distribution of R&B OMCB
8G Combined version 4G Combined version
Version Version
Database 20% 20%
Database 30% 20%
instance
instance
CONSOLE JVM 128M 128M
CONSOLE JVM 128M 128M
FTPSERVER 128M 128M
FTPSERVER 128M 128M
JVM
JVM
BACKUP JVM 256M 128M
BACKUP JVM 256M 128M
UMS-SVR JVM 1000M 512M
UMS-SVR JVM 1400M 1024M

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


split.
Preparation for R&B Split—Resource Internal Use Only

Allocation 3
 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 Split—Resource Internal Use Only

Allocation 4
 Network card of R&B integrated version
Network card Remarks Instance of IP address
eth3 The IP for the communication with EMS 10.128.41.223
and the Client of R&B integrated version.
eth4 The IP for the communication with V4.00 172.30.3.254
series base stations.
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 10.128.41.213
and the Client of OMCB version.
eth4:1 The IP for the communication with V4.09 172.30.3.253
series base stations.

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


address should be in the same sub-network.
Preparation for R&B Split—Other Internal Use Only

Prerequisites
 Before the transformation to R&B split, the R&B integrated
version is required to be upgraded to iOMCRV6.20.614c-
OMCBV4.00.200m of the later version.
 Before the transformation to R&B split, the appropriate network
cards must be adopted according to the SBCX installation
specifications; 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
original 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 Split—Installation of OMCB Internal Use Only

Version Database Instances


 Install the database instances of OMCB version according to the
Commissioning Guide.
 Installation method: Log in to VNC with user Oracle, run dbca, select
Create 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 Split—OMCB Version Internal Use Only

Installation 1
 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
version
 rb_split_oracle.sh –modifying parameters related to Oracle database
instances
 rb_split_root.sh –modifying parameters related to the user and
environment
 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 Split—OMCB Version Internal Use Only

Installation 2
 Pre-check the script execution
 Print of failed check: PreCheck not passed,correct problems,then run rb_split.sh
again.
 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
consistent with the actual situation.
It is normal that the check of OMCB version and OMCB database fails.
Operation of R&B Split—OMCB Version Internal Use Only

Installation 3
 Network card setting 1: According to the IP planning, input the
IP 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 Split—OMCB Version Internal Use Only

Installation 4
 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
Note: When R&B
TYPE=Ethernet
USERCTL=no split is adopted, it is
IPV6INIT=no forbidden to modify
PEERDNS=yes network card settings
GATEWAY=10.63.208.254
through graphical
 /etc/host.conf
order hosts,bind
interfaces. Otherwise,
multi on the records of hosts
 /etc/hosts will be lost.
10.62.102.55 sbcx55
10.62.102.155 sbcx55
127.0.0.1 localhost.localdomain localhost
Operation of R&B Split—OMCB Version Internal Use Only

Installation 5
 NTP server setting: After the transformation to R&B split, the NTP
server attached to the OMM program will be stopped, and the NTP
server attached 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,
and 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 Split—OMCB Version Internal Use Only

Installation 6
 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
installation path shall be consistent.
else
ORACLE_SID=gomcr
OMCHOME=/home/gomcr/zxgomcr/ums-svr #gomcr installation path is automaticallyacquired from
the 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 Split—OMCB Version Internal Use Only

Installation 7
 Modify the database parameters of
 Stop R&B integrated
R&B integrated version
version
The script automatically modifies the memory
Stop GOMCR version. After parameters of R&B integrated version database.
confirmation, input ‘y’ to continue Current system memory=4G
the execution of the script. SGA_TARGET=960M PGA_TARGET=240M
Stop GOMCR version,are you sure? System altered.
[y|n]: y System altered.
...... System altered.
Stop GOMCR version success Database closed.
Database dismounted.
rb_split_gomcr stop success.
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 Split—OMCB Version Internal Use Only

Installation 8
 Confirm that R&B integrated  Modify the JVM parameters of
version is one of V 6.20.61 series R&B integrated version
When the OMCR integrated version is Based on the current memory status,
one of V6.20.6xx series, input ‘y’ to the script automatically modifies the
continue the execution; otherwise, open a JVM parameters of R&B integrated
new login window, and upgrade OMCR version.
version. After the upgrade is completed, Current system memory=4G
return to the execution window of R&B UMS-SVR JVM=-Xmx1000m
split script, and input ‘y’ to continue the Modify set-jvm.param.sh success
execution. BACKUP JVM=-Xms128m -Xmx256m
step 6: Modify backup-linux.sh success
Upgrade OMCR version first,and then type 'y' to FTPSERVER JVM=$JAVA_OPTS -
continue. Xmx128m -Xms64m
OMCR version already upgraded? [y|n]: y Modify ftpserver-linux.sh success
OMCR version upgrade confirmed. CONSOLE JVM=-Xms64m -Xmx128m
rb_split_prompt upgrade_omcr_ver success. Modify run-linux.sh success
Note: Upgrade of R&B integrated version rb_split_gomcr jvm success.
is required to be completed before the
transformation, so that we can directly
input ‘y’ and continue the script execution.
Operation of R&B Split—OMCB Version Internal Use Only

Installation 9
 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 Split—OMCB Version Internal Use Only

Installation 10
 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 the
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


user, with default initial password-gomcb123. The creation
process is as follows:
Create group gomcb success
Create user gomcb success
rb_split_root gomcb success.
Operation of R&B Split—OMCB Version Internal Use Only

Installation 11
 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 Split—OMCB Version Internal Use Only

Installation 12
 Install OMCB version
 Currently the installation script of OMCB version is not available.
Open 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
version first in a new window, and then return to fill it in.
Operation of R&B Split—OMCB Version Internal Use Only

Installation 13
 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
environment 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
window.
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 Split—OMCB Version Internal Use Only

Installation 14
 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 Split—OMCB Version Internal Use Only

Installation 15
 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 Split—OMCB Version Internal Use Only

Installation 16
 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 Split—OMCB Version Internal Use Only

Installation 17
 Set database instances and auto-start of R&B integrated
version/OMCB version
The script automatically sets database instances and auto-start of R&B integrated
version/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 the 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
application 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
application 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 Split—OMCB Version Internal Use Only

Installation 18
 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
repetitive script execution.
 Running variable file rb_split.var is used to record the relevant variables, such as IP address,
database 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 Split—Check of OMCB Internal Use Only

Version Installation
 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 Split—Check 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 Split—Installation & Login Internal Use Only

of Client, Post-Installation
 Install OMCB version client
 Use R&B integrated version client and OMCB version
client to respectively log on to their server, and make
sure their logon process is normal.
 Make sure links can be established in the SDR sites
configured 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▲

Potrebbero piacerti anche