ZXWR RNC R3 Remote Upgrade Guide (V3.12 or V3.13 To V3.14) - R1.0

ZXWR RNC R3 Remote
Upgrade Guide (V3.12/13-toV3.14)
LEGAL INFORMATION
By accepting this certain document of ZTE CORPORATION you agree to the following
terms. If you do not agree to the following terms, please notice that you are not
allowed to use this document.
Copyright 2016 ZTE CORPORATION. Any rights not expressly granted herein are
reserved. This document contains proprietary information of ZTE CORPORATION. Any
reproduction, transfer, distribution, use or disclosure 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.
is the registered trademark of ZTE CORPORATION. ZTEs company name, logo
and product names referenced herein are either trademarks or registered trademarks
of ZTE CORPORATION. Other product and company names mentioned herein may be
trademarks or trade names of their respective owners. Without the prior written
consent of ZTE CORPORATION or the third party owner thereof, anyones access to this
document should not be construed as granting, by implication, estoppel or otherwise,
any license or right to use any marks appearing in the document.
The design of this product complies with requirements of environmental protection and
personal security. This product shall be stored, used or discarded in accordance with
product manual, relevant contract or laws and regulations in relevant country
(countries).
This document is provided as is and as available. Information contained in this
document is subject to continuous update without further notice due to improvement
and update of ZTE CORPORATIONs products and technologies.
Product Type Technical Proposal
ZTE CORPORATION
Addres
s:
Websit
e:
Email:
NO. 55
Hi-tech Road South
ShenZhen
P.R.China
518057
http://support.zte.com.cn
800@zte.com.cn
ZTE Confidential Proprietary
2015 ZTE Corporation. All rights reserved.
1(60)
Revision History
Product Version
V3.14
Document Version
Serial Number
Reason for Revision
R1.0
First published
Author
Date
2015-5-30
Document Version
R1.0
Prepared by
Reviewed by
Wang Wenqiong
Xiang Huiping
Approved by
Chen Taiming
Intended audience: UMTS commissioning & maintenance engineers
2(60)
About This Document

Summary
Chapter
Description
1 Overview
Provides an overview of the guide.
2 Preparations for Version Upgrade
Describes the preparations needed for the version upgrade.
3 RNC3IN1 Upgrade Step by Step
Describes the steps of RNC3IN1 upgrade in detail.
4 LOGSVR Upgrade Step by Step
Describes the steps of LOGSVR upgrade in detail.
5 FAQ
Introduces some FAQs.
3(60)
TABLE OF CONTENT
Overview...........................................................................................................1
2
2.1
2.2
2.3
2.4
2.5
2.6
2.7
Preparations for Version Upgrade..................................................................2

Preparation of Tools...........................................................................................2
Preparation of Important Spare Boards..............................................................2
Preparation of Software Version........................................................................3
Preparation of Documents.................................................................................3
License File Update and EMS Upgrade.............................................................3
ICM Configuration Data Model Upload...............................................................3
RNC Configuration File Backup.........................................................................4
3
3.1
3.1.1
3.1.2
3.1.3
3.1.4
3.1.5
3.1.6
3.1.7
3.1.8
3.2
3.2.1
3.3
3.3.1
3.4
3.4.1
3.5
3.5.1
3.6
3.6.1
RNC3IN1 Upgrade Step by Step......................................................................5

Preparations for RNC3IN1 Upgrade...................................................................6
Step 101 Performing Logservice Upgrade Modification.....................................
Step 102 Checking Logservice Configuration File..............................................
Step 103 Deploying updateAgent.....................................................................
Step 104 Checking Whether User zte Exists....................................................
Step 105 Registering Version...........................................................................
Step 106 Clearing Backup Software Version of RNC.......................................
Step 107 Deactivating Special Versions...........................................................
Step 108 Confirming the Quality of the Communications Between OMM and
OMP................................................................................................................
Step 109 Confirming the Left Slot of Master OMM/ROMB...............................
Step 110 Performing OMM Board Modification (only for single OMM
scenario)..........................................................................................................
RNC3IN1 Version Download............................................................................19
Step 111 RNC3IN1 Version Download.............................................................
RNC3IN1 Check Before Upgrade....................................................................23
Step 114 RNC3IN1 Check Before Upgrade.....................................................
RNC3IN1 Version Upgrade..............................................................................25
Step 113 RNC3IN1 Version Upgrade...............................................................
RNC3IN1 Confirm After Upgrade.....................................................................28
Step 114 Performing RNC3IN1 Confirm After Upgrade.................................
RNC3IN1 Version Upgrade Rollback...............................................................28
Step 151 RNC3IN1 Version Upgrade Rollback................................................
4
4.1
4.1.1
4.1.2
4.1.3
4.1.4
4.1.5
LOGSVR Upgrade Step by Step....................................................................31

LOGSVR Upgrade Preparations......................................................................31
Step 201 Performing LOGSVR Upgrade & Modifications.................................
Step 202 Checking Logservice Configuration File............................................
Step 203 Deploying updateAgent.....................................................................
Step 204 Checking Whether User zte Exists....................................................
Step 205 Registering Version...........................................................................
3.1.9
3.1.10
4(60)
4.2
4.2.1
4.3
4.3.1
4.4
4.4.1
LOGSVR Upgrade...........................................................................................32
Step 206 Creating and Executing the RNCXX_LOG Upgrade Task.................
LOGSVR Confirm After Upgrade......................................................................35
Step 207 Executing Upgrade Task RNCXX_LOG............................................
LOGSVR Upgrade Rollback.............................................................................36
Step 251 Performing RNCXX_LOG Upgrade Rollback....................................
5
5.1
5.2
5.3
5.4
FAQ................................................................................................................. 37
Q1: Can the version file storage location be set to SBCX?..............................37
Q02: How to acquire all the logs of the upgrade task?.....................................39
Q03: What should be down about ZDB generation failure?.............................40
Q04: How to process the issue that the OMP left board is not the master and the
right board is not the slave after OMM upgrade?.............................................41
Q05: How to fix the problem that some data is not reported after the upgrade?41
Q06: How to collect alarm information and NE status information?..................41
Q7: How to set left/right ROMP to left/right domains?......................................42
Q08: What are the contents of manual health status information collection?. . .44
Q09: How to perform pre-upgrade data check on the OMM board?.................45
Q10: How to restore the post-upgrade/rollback Iub NCP bearerer of master link?
47
Q11: What measures can be taken about RNC version activation failure?......47
Q12: How to compare alarm information and NE status information after
upgrade/rollback with a tool?...........................................................................49
Q13: How to perform KPI comparison after upgrade/rollback with a tool?.......51
Q14: What measures can be taken about LOGSVR pre-upgrade check failures?
52
Q15: How to perform local OMMR rollback?....................................................53
Q16: How to perform local logservice rollback?...............................................57
Q17: The base station reports the 1588 clock alarm after the upgrade. What
measures should be taken?.............................................................................58
Q18: RNCXX_3IN1 Upgrade Task Troubleshooting Guide...............................58
Q19: RNCXX_LOG Upgrade Task Troubleshooting Guide...............................62
5.5
5.6
5.7
5.8
5.9
5.10
5.11
5.12
5.13
5.14
5.15
5.16
5.17
5.18
5.19
5(60)
ZXWR RNC R3 Remote Upgrade Guide (V3.12/13-to-V3.14) Internal Use Only
Overview
This guide applies to the remote upgrade from V3 RNC V3.12/V3.13 to V3.14.
The
upgrade
consists
of
two
operations,
i.e.,
RNC3IN1
upgrade
(logservice+OMMR+RNC) and LOGSVR upgrade, as shown in the table below:
Upgrade Operation
Operation Steps
RNC3IN1(logservice+O
MMR+RNC) upgrade
Preparations for upgrade

RNC3IN1 version download
RNC3IN1 check before upgrade
RNC3IN1 upgrade
Confirm or rollback after upgrade
LOGSVR upgrade
Preparations for upgrade

LOGSVR upgrade
Confirm or rollback after upgrade
Note:
1. Before a remote upgrade, the OSS module must be installed on EMS.
2. Run logservice on OMM and LOGSVR respectively. For the OMM board, the
logservice is running in the OMM mode, and is marked as logservice(OMM) in this
manual. For the LOGSVR board, logservice is marked as logservice(LOG) in this
manual.
Preparations for Version Upgrade
2.1
Preparation of Tools
Tool Name
2.2
Recommended Quantity
Test handset
SIM card for test
2~3
Data card for test (supporting HSPA)
Client PC (in Windows OS)
Test NodeB
ROMP Debug cable
PC or laptop with 9-pin serial port
Screw driver
SIM card or landline using other

networks
Preparation of Important Spare Boards

Prepare necessary spare boards before RNC upgrade, so as to replace the boards
damaged in the upgrade process. The types of boards needed depend on the on-site
configuration. Prepare at least one board for each of the following boards.
Board Name
2.3
Quantity
ROMB
RCB
RUB
GIPI
SDTA
DTB
APBE
Preparation of Software Version

Prepare the target version package of the upgrade.
Software Package Name
2.4
RNC software version
Including:
RNC software version
RNC firmware version
LogService version
OMMR software version
Including:
OMMR version
Preparation of Documents
Document Name
RNC Version Release
Description
2.5
Description
Description
Introduces the new functions, the problems solved in the
version, version compatibility, etc.
License File Update and EMS Upgrade

Before the remote upgrade, it is necessary to update the License file, so that it is
compatible with the upgraded OMMR.
If necessary, upgrade the LCC to the version that is compatible with the License file.
If it is necessary, upgrade the EMS to the version that is compatible with the upgraded
OMMR.
2.6
ICM Configuration Data Model Upload

After the first V3 RNC on the same EMS is upgraded, upload the configuration model of
the version in ICM Configuration Model Management. Otherwise, some configuration
functions related to the new version of ICM cannot be used due to the lack of
configuration model.
2.7
RNC Configuration File Backup

Before RNC upgrade, back up the RNC configuration file manually and save the zip file
acquired to other places (e.g. another PC).
RNC3IN1 Upgrade Step by Step

The steps of RNC3IN1 upgrade (including the upgrade of logservice(OMM), OMMR,
RNC ) are listed in the table below:
Procedure
Step
Operatio
n Time
Details
101
-1
Performing Logservice Upgrade

Modification
102
-1
Checking Logservice Configuration

File
103
-1
Deploying updateAgent.
104
-1
Checking Whether User zte Exists
105
-1
Registering Version
106
-1
Clearing the Backup RNC

Software Version
107
-1
Canceling the Special Version of

Peripheral Boards
108
-1
Confirming the Quality of the

Communications Between OMM
and OMP
109
-1
Confirming the Left Slot of Master

OMM/ROMB
110
-1
Performing OMM Board

Modification (only for single OMM
scenario)
RNC3IN1 version
download
111
-1
Creating and Executing the

RNCXX_3IN1 Upgrade Task
Check before
RNC3IN1 upgrade
112
-1
Resetting the RNCXX_3IN1

Upgrade Task and Executing
RNCXX_3IN1_reset_1
113
Resetting the
RNCXX_3IN1_reset_1 Upgrade
Task and Executing
RNCXX_3IN1_reset_2
114
Executing the
RNCXX_3IN1_reset_2 Upgrade
Task
151
Performing RNCXX_3IN1_reset_2
Upgrade Rollback
Preparations for
RNC3IN1 upgrade
RNC3IN1 version
upgrade
Confirmatio
n After
Upgrade
Upgrade Rollback
Note:
The Execution Time here is the recommended time. -1 means one day before the
upgrade, 0 means the day of the upgrade, and 2 means two days after the upgrade.
3.1
Preparations for RNC3IN1 Upgrade
3.1.1
Step 101 Performing Logservice Upgrade Modification

The modification of Logservice is performed on the OMM board. If OMM is in
master/slave configuration, the modification should be performed on both the master
OMM and the slave OMM.
The modification package logsvr_rmtupdate_modpkg.zip needs to be extracted
from folder RncTools\LogService of RNC package, as shown in the figure below:
Upload modification package logsvr_rmtupdate_modpkg.zip to the /home/zte

directory of SBCX and unzip it.
#cd /home/zte
#unzip logsvr_rmtupdate_modpkg.zip
Execute the modpkg package as user root with the sh

OMM modify command.
rmtupdateadapt
sbcx
#cd /home/zte/logsvr_rmtupdate_modpkg
#sh rmtupdateadapt sbcx OMM modify
The remote updata adapt finish print should be outputted at the end of the execution
process, which means the modification is completed. Otherwise, fix the fault according to
the prompt and perform the upgrade modification again.
2014-08-20 11:58:18: ---------- remote updata adapt starting ---------2014-08-20 11:58:18: <function adapt_arg_check at 0xb7c9764c> OK!
/home/zte/logservice
ls: /home/zte/LogService: No such file or directory
ls: /home/zte/OmmHost: No such file or directory
2014-08-20 11:58:18: <function check_run_path at 0xb7c97534> OK!

2014-08-20 11:58:18: <function run_path_slink_adapt at 0xb7c975dc> OK!
Shutting down vsftpd:
[ OK ]
Starting vsftpd for vsftpd:
[ OK ]
iptables: Bad rule (does a matching rule exist in that chain?)

Flushing firewall rules:
Setting chains to policy ACCEPT: filter nat
Applying iptables firewall rules:
[ OK ]
[ OK ]
[ OK ]
2014-08-20 11:58:18: no line match the key_head_word disable

Stopping xinetd:
Starting xinetd:
[ OK ]
[ OK ]
2014-08-20 11:58:18: <function adapt_telnet_login at 0xb7c974c4> OK!

uid=500(zte) gid=500(zte) groups=500(zte),0(root),50(ftp)
Changing password for user zte.
passwd: all authentication tokens updated successfully.
2014-08-20 11:58:18: <function set_ftp_user at 0xb7c974fc> OK!
2014-08-20 11:58:18: <function start_script_updata at 0xb7c9756c> OK!
dos2unix: converting file /home/zte/logservice/bin/conf/system.conf to UNIX format ...
ShareBoardMode =0 ; 0: OMM, 1: LogSvr, 2: LogSvr&OMM, 3: FST
BoardType =1 ; 1: sbcx, 2: sbcw, 3: sbcj , 4: pcv3, 5: pcv4
2014-08-20 11:58:18: <function system_conf_modify at 0xb7c975a4> OK!
2014-08-20 11:58:18: <function uninstall_script_adapt at 0xb7c97614> OK!
2014-08-20 11:58:18: ---------- remote updata adapt finish ----------
3.1.2
Step 102 Checking Logservice Configuration File

For the running Logservice, all the following configuration files must exist.
(under the /home/zte/logservice/bin/conf directory)
LogNetIf00.conf
LogNetIf01.conf
LogNetIf02.conf
NetIf00.conf
NetIf01.conf
NetIf02.conf
If some file is missing, e.g., NetIf02.conf, which can be an empty file.

#cd /home/zte/logservice/bin/conf
#touch NetIf02.conf
Each channel of the configuration files (LogNetIfxx.conf and NetIfxx.conf) should meet
the following requirements:
1.
The value of NeedSetDefaultGateWay must be 0 or 1." It cannot be left blank.
2.
If the value of NeedSetDefaultGateWay is 1 (the default route), the IP defined by

GateWay must in the same subnet as the IP of the channel. Besides, the IP must
be set to unshared (ShareIP=0).
3.
If the value of NeedSetDefaultGateWay is 0 (the common route) and the value of

GateWay is not blank, the GateWay IP must in the same subnet as the IP of the
channel. Besides, the IPs of NextSkipIP and NextSkipNetMask must be configured
(not null).
4.
Each OMM can only be configured with one default route (i.e., among all the
channels, the NeedSetDefaultGateWay of only one channel can be set to 1).
5.
If the IP of the above-mentioned channel is configured (not blank), the NETMASK

should also be configured (not blank).
6.
The destination subnet must be unique within all the routes, and it cannot be
nested.
The following is an example:

Configuration of IP and the default route (for the same conf(LogNetIfxx and NetIfxx), only
one channel can be configured with the default route).
[Channeln]
ChannelName= VNC
NetIfName = eth4
IP = 10.63.208.166
NETMASK = 255.255.255.0
The IP field and NETMASK field (valid

IP/NETMASK combination) must be configured
or be blank at the same time
MacAddr =
ShareIP = 0
It must be set to 0
GateWay = 10.63.208.254
It should be in the same subnet of the IP field
NextSkipIP =
NextSkipNetMask =
It must be blank
NeedSetDefaultGateWay = 1
It can only be set to 1
Configuration of common routes:
[Channel6]
ChannelName= OMM_OMCB
NetIfName = eth6:2
IP =
NETMASK =
MacAddr =
ShareIP = 1
GateWay = 10.9.11.145
The next-hop IP must be in the same subnet as

the IP of at least one channel.
NextSkipIP = 110.9.12.0
NextSkipNetMask =
255.255.255.0
If GateWay is configured, NextSkipIP and

NetSkipNetMask cannot be left blank.
The destination subnet should not be the same
as that of other channels and it should not be
nested.
NeedSetDefaultGateWay = 0
If the NeedSetDefaultGateWay of another

channel is set to 1, this parameter should be
set to 0 here.
The following table provides the LogNetIfxx.conf

corresponding to different SBCX batches.
SBCX PCB Batch
3.1.3
and NetIfxx.conf
files
Configuration Files Used During Logservice Startup
SBCX060602
LogNetIf00.conf NetIf00.conf
SBCX090606
SBCX2
Step 103 Deploying updateAgent

This step needs to be performed on the OMM board. If OMM is in master/slave
configuration, this step must be performed on both the master OMM and the slave OMM.
1.
Get updateAgent.zip from EMS.

Get the updateAgent.zip file from the ums-server/utils/updateAgent/
directory of the EMS server.
Upload updateAgent.zip to the /home/ directory on the server of OMM.
2.
Make sure there is no updateAgent running. If there is, kill it and delete the
/home/updateAgent folder.
#pids=`ps -ef | grep updateAgent|grep -v grep| awk '{print $2}'`

#for pid in ${pids}; do kill -9 $pid ; done
#rm rf /home/updateAgent
3.
Unzip updateAgent.zip, and copy jdk-linux of the current OMM to the

/home/updateAgent/jdk-linux directory, and modify the owner of
updateAgent to user root.
#unzip d /home /home/updateAgent.zip

#cp r /home/womc/ZXWR-RB/WOMC/jdk-linux /home/updateAgent/
#chown R root:root /home/updateAgent
4.
Grant the execute permission to updateAgent.
#chmod R 777 /home/updateAgent
5.
Configure updateAgent auto-start.

Add the following lines at the end of the /etc/rc.local file.
#UPDATEAGENT_BEGIN
#config updateAgent auto-start when start system
nohup /home/updateAgent/startagent-linux.sh &
#UPDATEAGENT_END
6.
Start updateAgent.
Start the updateAgent as the root user.
#nohup sh /home/updateAgent/startagent-linux.sh &
3.1.4
Step 104 Checking Whether User zte Exists

This step needs to be performed on the OMM board. If OMM is in master/slave
configuration, it should be performed on both the master OMM and the slave OMM.
If LOGSVR needs to be upgraded, this step needs also to be performed on LOGSVR.
Check whether user zte exists with the id zte command.
In the following example, user zte exists.
#id zte
uid=503(zte) gid=504(zte) groups=504(zte)
In the following example, user zte does not exist.

#id zte
id: zte: No such user
If user zte does not exist, create it.

# groupadd zte
# useradd -g zte -m zte
# chmod R 777 /home/zte
Modify the password of user zte to Zte_1234.

# passwd zte
Changing password for user zte.
New UNIX password:Zte_1234
Retype new UNIX password:Zte_1234
passwd: all authentication tokens updated successfully.
3.1.5
Step 105 Registering Version

This step is to register the target version files for upgrade on EMS.
The following version files need to be registered.
1.
logservice
2.
OMMR
3.
RNC SW
4.
RNC_FW
The registering steps (V3.12 is taken as the example in the following description. In
actual operation, modify the versions to be upgraded to the ones planned).
1.
Upload the version description file (xml) and version file (zip file or folder) to the
storage directory according to the table below.
The IPs in red are EMS IPs. They need to be modified according to the configuration in the
existing network.
Version
Type
Description File
Storage Address
Requirements
logservice_softwaredesc.xml
ftp://mossIus:mossIus@10.63.208.41:21111/logservice_V3.12.10.14P06/
The software version description file and version package are under the
same directory level.
logservice
OMMR(R3)V12.12.49P02_softwaredesc
ftp://mossIus:mossIus@10.63.208.41:21111/OMMR.R3V12.12.49P02/
The software version description file and version package are under the
same directory level.
OMMR
WRNCV3.12.10.14P06_1606_softwaredesc.xml
ftp://mossIus:mossIus@10.63.208.41:21111/WRNCV3.12.10.14P06/
The software version description file and folder are under the same
directory level.
RNC SW
3.1.6
2.
Click Maintenance > Remote Upgrade > Software Version Management in the
EMS client interface.
3.
Register the version with the following steps.

i.
Click Register software version.
ii.
Fill in the name of the software version description file.
iii.
Fill in the storage path of the software version package.
iv.
Click OK to finish the registering.
Step 106 Clearing Backup Software Version of RNC

1.
Clear all inactivated software versions on ROMB through Software Version

Management, so as to release the storage space on ROMB.
2.
3.1.7
Delete all backup versions in OMMR to release the storage space of the OMM
board, so as to save some space for the backup in the upgrade process.
Step 107 Deactivating Special Versions

If there is some special version running, deactivate the version.
3.1.8
Step 108 Confirming the Quality of the Communications Between

OMM and OMP
Switch the left ROMB and the right ROMB to the master state respectively, and perform
ping 32K packet test to the master board. When there are no services (such as version
download, and fault/alarm/performance data reporting) occupying the OMM-OMP
communications bandwidth, the packet loss rate of these two ROMB boards should be
smaller than 20%, otherwise the remote upgrade may fail.
This operation can be performed at Section 3.1.9. Suppose ROMP IP is 10.9.11.129,
refer to the following example:
#ping 10.9.11.129 -s 32767
PING 10.9.11.129 (10.9.11.129) 32767(32795) bytes of data.
32775 bytes from 10.9.11.129: icmp_seq=0 ttl=64 time=8.77 ms
--- 10.9.11.129 ping statistics --8 packets transmitted, 8 received, 0% packet loss, time 7011ms
rtt min/avg/max/mdev = 6.210/7.681/8.776/1.027 ms, pipe 2
3.1.9
Step 109 Confirming the Left Slot of Master OMM/ROMB

In the remote upgrade process, the following two requirements should be satisfied:
3.1.10
1.
The left OMM should be the master board. Otherwise, perform master/slave OMM
changeover and switch the left OMM to the master state. This requirement is not
applicable to single-OMM configuration.
2.
The left ROMB should be the master board. Otherwise, perform master/slave
ROMB changeover and switch the left ROMB to the master state.
Step 110 Performing OMM Board Modification (only for single OMM
scenario)
For single-OMM configuration, the BackMode of Logservice must be set to the single
mode (0), and modify the floating IP to the static IP. Otherwise, the communications
between OMMR and EMS will break in the upgrade process, which will lead to the
upgrade failure.
The modification method is as shown below:
#cd /home/zte/logservice/bin/conf
#sed -i "s/BackupMode = 1/BackupMode = 0/" system.conf
The modification can only take effect after Logservice is restarted. Because OMM will
also be upgraded in the process of OMM restart, it is recommended that the step be
performed before the upgrade.
#cd /home/zte/logservice/bin
#./stopsys
#./startsys
3.2
RNC3IN1 Version Download
3.2.1
Step 111 RNC3IN1 Version Download

Create the RNCXX_3IN1 upgrade task, select and download the version, and execute
the task. The steps are as listed below.
1.
Click Maintenance > Remote Upgrade > Upgrade Management.
2.
Create a task.
i.
Click New.
ii.
Set Job Name (recommended name: RNCXX_3IN1). "XX" is the ID of the

RNC to be upgraded.
iii.
Set Object Type to BUILDINSERVER+OMM+[RNC/BSC].
iv.
Select the Target Version for BUILDINSERVER to 3.14.10.15.
v.
Set the Target Version for OMM to OMMR(R3)V12.14.15.
vi.
Set the Target Version

WRNCV3.14.10.15_sw.
vii.
Select the NE to be upgraded.
for
RNC
to
WRNCV3.14.10.15_firm
and
viii. Click Next.
3.
Set parameters for the task.

i.
Keep Route Address as 0.0.0.0 (default), which does not need to be

modified.
ii.
Set the OMMR installation path (OMC Server Running Path) to

/home/womc/ZXWR-RB/WOMC.
iii.
Set the folder for saving the version file during the upgrade to
/home/rmtupd/ver.
iv.
SID: womc
v.
Set DB Password to oracle.
vi.
Set the folder for saving the data file during the upgrade (Backup Data File
Path) to /home/rmtupd/ver.
vii.
OMM Type: Select Single for non-master-slave OMM and Master/Slave for
master-slave OMM.
viii. For RNC Update Schema, select Isolate master and backup domain.
ix.
4.
Click Next, and the system will test whether the configuration of Steps i-viii is
correct. If not, the incorrect items will be displayed in the prompt box. In this
case, correct these items, and click Next to proceed to the next step.
Set contents of the task.
i.
Select the following steps and finish task creation.
OMM version package download

BuildInServer version package download;
RNC version package download
ii.
Finish the following steps .
Select task RNCXX_3IN1.
Click Start.
Observer the execution result.
3.3
RNC3IN1 Check Before Upgrade
3.3.1
Step 114 RNC3IN1 Check Before Upgrade

This step must be performed in advance, so that problems can be located and fixed.
1.
Reset the RNCXX_3IN1 task. The new task is RNCXX_3IN1_Reset_1. The

operation steps are listed below.
i.
Select task RNCXX_3IN1.
ii.
Select Reset.
iii.
The steps are listed in the table below.
BuildInServer check before upgrade

OMM check before upgrade
RNC check before upgrade
2.
Execute the RNCXX_3IN1_Reset_1 task.

i.
Select task RNCXX_3IN1_Reset_1.
ii.
Start task RNCXX_3IN1_Reset_1.
iii.
Observe the task execution result.
If some error is found, extract the upgrade check report (right-click the faulty step, and
select Get Step Result).
After the fault is fixed, retry the faulty steps until the step passes the check.
Note: In the Retry process, the system will prompt Are you sure to execute? Click
Retry to retry the current step or click Cancel to skip the current step.
Select OK here to retry the current step.
3.4
RNC3IN1 Version Upgrade

Note: In the following upgrade process, it is prohibited to run OMMR and OMMB clients
on SBCX. Shut down the clients if they have been started. Otherwise, upgrade or
rollback failures may occur.
3.4.1
Step 113 RNC3IN1 Version Upgrade

Note: This step will continue until the stop OMM+logservice process step. The services
will not be interrupted before this step.
1.
Reset the RNCXX_3IN1_Reset_1 task (refer to step 112 for the reset method). The
new task is RNCXX_3IN1_Reset_2, of which the configuration steps are as listed
below.
Note: The upgrade will pause when the execution proceeds to the key steps. Type in the
verification code and continue the execution.
Select different key steps for single-OMM configuration and master/slave OMM
configuration.
OMM version package download

BuildInServer version package download
BuildInServer check before upgrade
OMM check before upgrade
RNC check before upgrade
OMM data backup
Alarm collection
Stop OMM+LOGSERVICE process
Key step (only for single OMM

configuration)
OMM+LOGSERVICE Upgrade
Start process
Key step (only for single-OMM

configuration)
Check OMM process

BuildInServer check after upgrade
OMM check after upgrade
RNC version package download
RNC upgrade prepare
RNC version package activate
RNC check after upgrade
RNC confirm after upgrade
OMM+LOGSERVICE confirm after upgrade:
Key step.
2.
After the task is started:

For single-OMM configuration, the upgrade task will pause after the OMM data backup
step is finished.
For master/slave OMM configuration, the upgrade task will pause automatically after the
OMM+LOGSERVICE upgrade step is executed on the slave board.
After the verification code is inputted, the task will continue and stop before the
OMM+LOGSERVICE confirm after upgrade step.
Remarks: After the RNC confirm after upgrade step is finished, if the system reports
alarms and the cause is: Version activation information: BOOTROM version, reset the
left ROMB (on the Status Management interface of OMMR) to fix the alarms
3.5
RNC3IN1 Confirm After Upgrade
3.5.1
Step 114 Performing RNC3IN1 Confirm After Upgrade

1.
Type in the verification code, and finish the OMM+LOGSERVICE confirm after upgrade
step.
This is the end of the whole upgrade process.
Note: After the RNC confirm after upgrade" step, version rollback cannot be
performed anymore.
3.6
RNC3IN1 Version Upgrade Rollback
3.6.1
Step 151 RNC3IN1 Version Upgrade Rollback

Roll back the RNCXX_3IN1_Reset_2 task.
1.
Select the RNCXX_3IN1_Reset_2 task, and click Rollback.
2.
Type in the verification code.
3.
Select the BUILDINSERVER+OMM+[RNC/BSC] rollback mode.
4.
Select Rollback with OMC backup.
5.
Select Continue to perform rollback.
The following modification

RNCXX_3IN1_Reset_2.
has been
made
to
the steps of
Skip the OMM+LOGSERVICE confirm after upgrade step.

Add the RNC rollback with OMC backup step.
Add the OMM+LOGSERVICE rollback step.
upgrade
task
LOGSVR Upgrade Step by Step

The steps of LOGSVR upgrade (including the upgrade of logservice(LOG)) are listed in
the table below:
Procedure
LOGSVR Upgrade
Preparations
LOGSVR upgrade
Confirmatio
n After
Upgrade
Upgrade Rollback
step
Operation
Time
Execution Steps
201
-1
Performing LOGSVR Upgrade &

Modifications
202
-1
Checking Logservice Configuration

File
203
-1
Deploying updateAgent.
204
-1
Checking Whether User zte Exists
205
-1
Registering Version
206
Creating and Executing the

RNCXX_LOG Upgrade Task
207
Executing Upgrade Task

RNCXX_LOG
251
Performing RNCXX_LOG Upgrade

Rollback
Note: The Execution Time here is the recommended time. -1 means one day before
the upgrade, 0 means the day of the upgrade, and 2 means two days after the
upgrade.
4.1
LOGSVR Upgrade Preparations
4.1.1
Step 201 Performing LOGSVR Upgrade & Modifications

Execute the following command on the LOGSVR board.
sh
rmtupdateadapt
sbcx
LOG
modify
Refer to Step 101 for the output of the command.
4.1.2
Step 202 Checking Logservice Configuration File

Perform this step on the LOGSVR board.
Refer to Step 102.
Modify the master/slave mode of Logservice to Single and set the IP to fixed
configuration.
Refer to step 110
4.1.3
Step 203 Deploying updateAgent

updateAgent must be deployed on the OMM board. Refer to Step 103.
If Step 103 has been executed, ignore this step.
4.1.4
Step 204 Checking Whether User zte Exists

Perform this step on the LOGSVR board.
Refer to Step 104.
4.1.5
Step 205 Registering Version

For LOGSVR upgrade, it is only necessary to register the Logservice file. Refer to Step
105.
If Logservice version file has been registered at Step 105, skip this step.
4.2
LOGSVR Upgrade
4.2.1
Step 206 Creating and Executing the RNCXX_LOG Upgrade Task

Create and execute the RNCXX_LOG upgrade task. The steps are as listed below.
1.
Create the RNCXX_LOG task.

i.
Click New.
ii.
Set Job Name (recommended name: RNCXX_LOG). "XX" is the ID of the

RNC to be upgraded.
iii.
Set Object Type to BUILDINSERVER.
iv.
Set the Target Version for BUILDINSERVER to 3.14.10.xx.
v.
Select the NE to be upgraded.
vi.
Click Next.
2.
Set task parameters.

i.
Set the OMMR installation path (OMC Server Running Path) to

/home/womc/ZXWR-RB/WOMC.
ii.
Set the folder for saving the Logservice version file during the upgrade to
/home/rmtupd/ver.
iii.
Set Logservice Type to Single.
iv.
Set the logservice IP as the control-plane IP 128.0.200.200.
v.
Leave Root Password of Logservice blank or set it to the password of the

root user that can logs into Logsvr.
vi.
Click Next, and the system will test whether the configuration of Steps i-iv is
correct. If not, the incorrect items will be displayed in the prompt box. In this
case, correct these items, and click Next to proceed to the next step.
3.
The configuration steps are listed in the table below.
Note: If Step 111 has been executed, skip the version package download" step.
Version Package Download
Check Before Upgrade
Stop BuildInServer process.
Upgrade
Start BuildInServer process
Check after upgrade
Confirm after Upgrade
4.
Key step
Execute task RNCXX_LOG until the confirm after upgrade step is finished.
i.
Select task RNCXX_LOG, and click Continue.
ii.
Observe the task execution result.
Because the confirm after upgrade step has been marked as the key step, the task will
pause at this step.
4.3
LOGSVR Confirm After Upgrade
4.3.1
Step 207 Executing Upgrade Task RNCXX_LOG

1.
Select Task RNCXX_LOG, and click Continue.
2.
Type in the verification code to finish the confirm after upgrade step.
Note: Rollback cannot be performed after the confirm after upgrade step is finished.
4.4
LOGSVR Upgrade Rollback
4.4.1
Step 251 Performing RNCXX_LOG Upgrade Rollback

Roll back the RNCXX_LOG task.
1.
Select Task RNCXX_LOG, and click Continue.
2.
Click OK to start the rollback.

At this time, the following modifications have been made to the steps of upgrade task
RNCXX_LOG. Execute the modified steps directly.
The Confirm After Upgrade step is skipped.
The Rollback step is added.
FAQ
5.1
Q1: Can the version file storage location be set

to SBCX?
(If yes, during the upgrade process, the SBCX can acquire the version file locally, and an
overlong transmission of version file due to insufficient EMS-OMM transmission
bandwidth can be avoided.)
A: Yes. The operations steps are as detailed below (the version in the following
descriptions is an example).
1.
Create the folder /home/zte/vertmp on the left SBCX.
#mkdir p /home/zte/vertmp
2.
Modify the version description file, including file name and content.
Add Left before the file

swPackageName= (/zh /en).
names.
File Name
Add
Left
before
the
file
name
after
File Contents
Leftlogservice_softwaredesc.xml
swPackageName=Leftlogservice_V3.12.
10.10
LeftOMMR(R3)V12.12.10_softwaredesc.
xml
swPackageName=LeftOMMR(R3)V12.12
.10
LeftWRNCV3.12.10.10_0802_softwared
esc.xml
swPackageName=LeftWRNCV3.12.10.1
0_0802
LeftWRNCV3.12.10.10_firm0802_softwa
redesc.xml
swPackageName=LeftWRNCV3.12.10.1
0_firm0802
3.
Upload the version package and the modified version description file to
/home/zte/vertmp, as shown in the figure below.
4.
Register version on EMS.
Input the description file name of the software version and the storage location of the
software version package according to the following contents.
Version file
type
Description file
Storage Location
Leftlogservice_softwaredesc.xml
logservice
ftp://zte:Zte_1234@128.0.28.1:10021/home/zte/vertmp/logservice_V3.1
2.10.14P04/
LeftOMMR(R3)V12.12.48_softwaredesc.xml
OMMR
ftp://zte:Zte_1234@128.0.28.1:10021/home/zte/vertmp/OMMR.R3V12.1
2.48-2013-10-21/
LeftWRNCV3.12.10.14P04_0802_softwaredesc.xml
RNC SW
ftp://zte:Zte_1234@128.0.28.1:10021/home/zte/vertmp/WRNCV3.12.10.
14P04-1023/
LeftWRNCV3.12.10.14P04_firm0802_softwaredesc.xml
RNC_FW
5.
ftp://zte:Zte_1234@128.0.28.1:10021/home/zte/vertmp/WRNCV3.12.10.
14P04-1023/
Upgrade task: Select the versions starting with Left.
6.
5.2
When upgrading the SBCX of other RNCs, execute only Steps 1)-3). Version
registration is not required.
Q02: How to acquire all the logs of the upgrade

task?
To analyze the details of the steps in the task after the upgrade is finished, we can
export all the logs of the upgrade task and check them offline.
If there are errors in the upgrade task, which need to be analyzed by the support team in
HQ, we should provide the detailed logs of the upgrade task.
Method of acquiring all the logs of the upgrade task: on the Upgrade Management
interface, select the corresponding upgrade task, right-click it and choose Get Reports.
The result will display all the logs in a pop-up window.
Copy all the files in the window for backup. Send them to the support team for analysis
in necessary.
5.3
Q03: What should be down about ZDB

generation failure?
One step may fail during the RNC upgrade preparation. The details indicate the ZDB file
generation failure, and Interaction with data conversion module timeout is displayed in
the failure logs on OMMR.
In this case, first try to perform the upgrade preparation once again. If it still fails, use the
MML command to extend the timer for performance task synchronization according to
the following instructions.
Perform the operation on the MML client of EMS or OMMR.
Extend the timer to a longer time before the RNC upgrade, for example, 30 minutes.
SET PARAM:ID=2029,VALUE=30;
After the upgrade, change the timer back to 5 minutes. Otherwise, the performance data
will not be collected for a long time after the task is sent.
SET PARAM:ID=2029,VALUE=5;
5.4
Q04: How to process the issue that the OMP left

board is not the master and the right board is
not the slave after OMM upgrade?
Whether the left OMP is the master board and right OMP the slave board currently will
be checked during the RNC upgrade preparation. If not, an error will be reported. It can
be solved by adjusting the master-slave status of the OMP boards.
In the current state, after the OMM is upgraded, while the RNC is not upgraded and the
status management cannot be used, we cannot adjust the master-slave status of OMP
through OMM. In this case, telnet to the right OMP of RNC and use the reboot command
to reset the right board. After the right board is successfully started, wait for five minutes
until the data on the left board and the right board are synchronized, and then carry out
the RNC upgrade preparation. This error exerts no influence over the upgrade process.
5.5
Q05: How to fix the problem that some data is

not reported after the upgrade?
Perform measurement task synchronization on EMS after the upgrade. Otherwise, it is
possible that some performance data cannot be reported.
5.6
Q06: How to collect alarm information and NE

status information?
When creating the upgrade task, select "Check Alarm and Check Nestatus to collect
alarm information and NE status information once.
Besides, NE status and alarm information can be collected independently with the
following steps:
5.7
1.
Right-click the upgrade task and select Create Check Job.
2.
Select Check Alarm and Check Nestatus.
3.
Click Check Compare Job > Check Job Table, and check the task execution
status.
Q7: How to set left/right ROMP to left/right

domains?
Set left/right ROMPs to left/right domains, and set other CPUs to dynamic domains.
The left ROMP should be set to the left domain, and the right ROMP should be set to the
right domain.
The following figure shows the configuration, with the left board as the example.
5.8
Q08: What are the contents of manual health

status information collection?
Save the following contents:
1.
Synchronize alarms from OMM to RNC and keep a record.
Perform alarm synchronization, and then check real-time alarms and notifications
information in the system. Export and save real-time alarm records.
5.9
2.
Check the transmission status of each interface and keep a record.

Check the link status on the IUCS/IUPS/IUR interfaces and the status of SCTP. Export and
save the original information.
3.
Check the status of each board and keep a record.

Check the state of each board before the upgrade (master/slave state, CPU state, DSP state,
port state, blocked/unblocked state), and export and save the raw data.
4.
Keep a record about radio resource configuration (cell, NCP bearer link).
Click Status Management > Radio Resource Batch Query Status.
Q09: How to perform pre-upgrade data check on

the OMM board?
Use the upgrade check tool of OMMRV3.13 to check whether the current OMMRV3.12
can be upgraded. When the result of all check items is pass or there is no item with the
not pass information in the log file (ommr*.log in the upgdcheck folder) and the xml
file (OMMR_CheckBeforeUpdate_data.xml in the upgdcheck folder) generated after
the check, the OMMR can be upgraded. Otherwise, modify the not pass items and
perform the upgrade again until the result of all items becomes pass.
Suppose OMMRV3.13 is unzipped to the /home/zxommr directory. Execute the
upgdcheck.pl script. The parameter (highlighted in red) after upgdcheck.pl is the
parent directory of ums-svr under the installation path of the version to be upgraded.
#cd /home/zxommr/ums-svr/tools/upgdcheck/
#perl upgdcheck.pl /home/womc/ZXWR-RB/WOMC
Please input oracle sid: womc
Please input oracle system password: oracle
Initialize environment variables success
OMM Checker for Upgrade
-------------------------------------------------------------------------------Checking OS......
check OS--->OS_HostName
pass
check OS--->OS_KernelParameter
pass
check OS--->OS_LANGUAGE
pass
Checking ORACLE......
check ORACLE--->ORACLE_Version
pass
check ORACLE--->ORACLE_Variable
pass
check ORACLE--->ORACLE_DbParameter
pass
check ORACLE--->ORACLE_Temporary
pass
check ORACLE--->ORACLE_RedoLog
pass
check ORACLE--->ORACLE_AutoStart
pass
check ORACLE--->ORACLE_Constraint
pass
Checking OMM......
check OMM--->OMM_Variable
pass
check OMM--->OMM_DiskSpace
pass
check OMM--->OMM_Tnsname
pass
check OMM--->OMM_Tablespace
pass
check OMM--->OMM_Version
pass
Detail: R3V12.12.41P04
check OMM--->OMM_Path
pass
pass: /home/womc/ZXWR-RB/WOMC/ums-svr
check OMM--->OMM_Status
pass
Detail: Server is not running
check OMM--->OMM_CMDataGround
check pass
pass
check OMM--->OMM_CMDataRadio
check pass
pass
The faulty items are as follows in the log file.

checkItemName: XXXXXX
checkResult:
not
pass
failureReasons: XXXXXX
5.10
Q10: How to restore the post-upgrade/rollback

Iub NCP bearerer of master link?
Restore the post-upgrade/rollback bearer of master link of Iub NCP to the pre-upgrade
configuration.
If there are different bearer master links, we can trigger the change between them by
blocking/unblocking the NCP bearer link.
The following is an example: The NCP port bearing mode is link1 before the upgrade
and changes to link2 after the upgrade. Block the links except link1, wait for three
minutes until the NCP bearing mode changes to link1, and then unblock the previously
blocked links.
5.11
Q11: What measures can be taken about RNC

version activation failure?
Check the upgrade details.
If there is the Reset left OMP successful information, perform all-data synchronization
manually, and try to perform RNC version activation again. Then select NO to skip this
step.
Otherwise, roll back the task to the pre-upgrade state. The rollback steps are as shown
below:
1.
Click Rollback.
2.
Select RNC.
3.
Select Rollback with NE backup.
4.
Continue the upgrade task and finish RNC rollback.
5.
After the rollback is finished, reset this task, and execute the following steps:
RNC Version Package Activation

RNC check after upgrade
RNC confirm after upgrade
OMM+LOGSERVICE confirm after
upgrade:
5.12
Key step
Q12: How to compare alarm information and NE

status information after upgrade/rollback with a
tool?
To compare the data with the pre-upgrade data, the pre-upgrade data must be saved.
There are two ways of saving the pre-upgrade data.
1.
Select ne resource status check and alarm backup in the steps of task
RNCXX_3IN1_2.
2.
Before the step OMM+LOGSERVICE of the RNCXX_3IN1_2 task is executed,

create a data collection task according to Q09.
Compare the alarm data with the pre-upgrade alarm data:
In Check Job Table, right-click the alarm collection task and select Create Compare Job
to start the new alarm collection task and compare the collected data with the data of the
selected alarm collection task.
Find the comparison task in Compare Job Table. After the compare status of the task
becomes success, right-click the task and select Get Report Result.
Compare NE status with the pre-upgrade NE status.

The operation is similar to alarm comparison operation. Select Ne Status for Collect
Type.
5.13
Q13: How to perform KPI comparison after

upgrade/rollback with a tool?
In the Upgrade Management tab, right-click the target task and select KPI Compare.
Set the time of KPI comparison.
After the comparison tasks in Check Compare Job > Check Job Table are completed,
right-click the tasks and select Get Report Results.
5.14
Q14: What measures can be taken about

LOGSVR pre-upgrade check failures?
Check the LOGSVR pre-upgrade check result file (right-click the check step and select
Get Report Result.)
Cause of and solution to the Ping xx failed! prompt:

1.
The IP parameter is incorrectly configured in the independent LOGSVR upgrade

task created.
Modify the IP in the independent LOGSVR upgrade task.
2.
Logservice operation is abnormal, and this IP is not validated.

Check whether the IP is validated on the independent LOGSVR board, and whether this IP
is configured in the Ethernet port configuration file. If not, modify the configuration and
restart the Logservice program, and then perform this step again.
Cause of and solution to the telnet xx failed! prompt:

1.
The telnet server is not running.

Start and run the telnet service.
2.
The password of the root user is not root123.

Modify the password of the root user to root123.
Perform upgrade modification.
Perform this step again.
3.
The root user does not have the telnet permission.

Perform upgrade modification.
Cause of and solution to the XXX InitNetIfConf fail! prompt:

The configuration item in the Ethernet port configuration file is invalid. Correct the
configuration item according to the prompt and perform this step again.
Cause of and solution to the local logservice,read sysconf file failed! prompt:
The /home/zte/logservice/bin/conf/system.conf file does not exist or it is
damaged. Set this file to the following and perform this step again.
[system]
ShareBoardMode = 1 ; 0: OMM, 1: LogSvr, 2: LogSvr&OMM
BackupMode = 0 ; 0: single, 1: 1+1 backup
BoardType = 1 ; 1: sbcx, 2: sbcw, 3: sbcj , 4pcv3, 5:pcv4
Cause of and solution to the local logservice sysconf file check ShareBoardMode and
BoardType failed! prompt:
The value of the ShareBoardMode or BoardType field is not configured in the
/home/zte/logservice/bin/conf/system.conf
file.
Set
ShareBoardMode/BoardType to 1 and perform this step again.
5.15
Q15: How to perform local OMMR rollback?

Local OMMR rollback is performed when the OMMR rollback fails after a remote
upgrade failure.
For local OMMR rollback, use OMMR V3.12 of silent installation, and then restore the
configuration file backed up before the upgrade.
1.
Stop the running OMMR.
# perl /home/zte/logservice/bin/stopmodule.pl 4100
2.
Delete or rename the folder of the OMMR installed.
#cd /home/womc
#mv ZXWR-RB ZXWR-RB313
3.
Edit the zxommr/setup/solaris/product/ommr/install.rsp file of OMMR

V3.12 and modify the contents to the following:
Install_language=ENGLISH
# Language displayed during installation: if it is Chinese, select CHINESE.
Database_type=ORACLE
Product_language=ENGLISH
# Language displayed after installation: if it is Chinese, select CHINESE.
setup_set_user|user=root
#Perform the installation as user root.
setup_set_user|group=root
#Perform the installation as the root user group.
installdb_conf_panel|setup_db_ip=127.0.0.1
installdb_conf_panel|setup_db_sid=womc
#The database SID used: womc
installdb_conf_panel|setup_db_port=5000
installdb_conf_panel|setup_system_pwd=oracle
installdb_conf_panel|setup_db_locale=1
installdb_conf_panel|setup_db_destdir=/oracledata/womc
#Set the storage path of the database SID to /oracledata/womc
setup_path|setup_path_choice=/home/womc/ZXWR-RB/WOMC
#Set the installation path to /home/womc/ZXWR-RB/WOMC
dbModule=normal
install_module=c1,s1,database
path_num=1
db_path_0=/oracledata/womc
#Set the storage path of the database to /oracledata/womc
setup_minos_db_ora|setup_db_destdir_ora=
Setup_ExecSQL|is_uninstall_db=1
pathmode=fix_path
input_var|ftp_server_ip_info=FTP_SERVER_IP_INFO
setup_set_jvm_mem|jvm_mem_svr=1400
setup_set_jvm_mem|jvm_mem_clnt=512
licenseServer-ip=10.63.208.41
#license server IP
licenseServer-ip-spare=
# IP of the slave license server
is_backup=false
#For master/slave configuration, set it to true
omm-leftOrRight=left
#If omm-leftOrRight is set to left on the left board, set it to right on the right board
ums_type=wcdma.omm
4.
Perform silent installation
Because the storage space of the database may become insufficient in the installation
process, delete all the folders under /oracledata except womc and womcb before starting
silent installation.
Perform silent installation.
#dos2unix /home/zte/logservice/bin/conf/*.conf
#cd zxommr
#sh install-linux-silence.sh
After the installation succeeds, the following prompt appears.

succeed!
info:finish,setup success
f_final_env_conf end
f_finish begin
Exit!(The setup has been completed.)
5.
Restore the OMMR configuration files (file name: deploy) backed up before the
upgrade (the part in red is the name of the remote upgrade task auto-backup files,
of which folder name is in the YYYYMMDDHHMMSS format. If there are two or
more files, select the latest one).
#cd /home/rmtupd/bak/dbBackup/20141120121151/ums-svr/
#cp r deploy /home/womc/ZXWR-RB/WOMC/ums-svr
6.
Start OMMR.
# perl /home/zte/logservice/bin/startmodule.pl 4100
7.
Restore the RNC configuration file saved before the upgrade.

i.
Copy the RNC configuration file (.zip file) backed up before the upgrade to the
/home/womc/ZXWR-RB/WOMC/ums-svr/cmdata/cmbak directory.
# cp RNCXX_beforeUpd.zip /home/womc/ZXWR-RB/WOMC/ums-clnt/cmdata/cmbak/
ii.
Select Configuration Management > Data Restoration.
5.16
Q16: How to perform local logservice rollback?

For local Logservice rollback, use the method of Logservice upgrade (the existing
configuration files will be kept). This applies to the rollback of logservice(OMM) and
logservice(LOG).
1.
Upload the Logservice version used before the upgrade to the /home/zte folder of
SBCX as user root, and extract the following upgrade scripts to the /home/zte
directory.
autoupdate.sh
(Suppose the version package is logservice_V3.12.10.14P06.zip) Execute the

following commands to extract the files.
#cd /home/zte
#unzip -j logservice_V3.12.10.14P06.zip logservice_V3.12.10.14P06/install/autoupdate*
Archive: logservice_V3.12.10.14P06.zip
inflating: autoupdate.sh
2.
Execute upgrade script autoupdate.sh. In the execution process, the existing

logservice will be stopped automatically. Only the name of the Logservice package
(in red) can be modified in the command.
#cd /home/zte
#sh autoupdate.sh /home/zte/logservice_V3.12.10.14P06.zip small
3.
5.17
Start Logservice.
Q17: The base station reports the 1588 clock

alarm after the upgrade. What measures should
be taken?
If the 1588 clock alarm appears, take the following measures.
1.
If the NodeB uses only IP transmission, modify the clock reference mode to oneway.
2.
Switch over the clock board of RNC.
3.
Restart the clock board of RNC.
5.18
Q18: RNCXX_3IN1 Upgrade Task

Troubleshooting Guide
Step Name
FD(failure description) & S(solution)
OMM
version
package
download
FD: Version download failure

S:
Check the version file, user/password, and IP/port filled in at step 105.
Retry
buildInServ
er version
package
download
FD: failed to download the version

S:
Check the version file, user/password, and IP/port filled in at step 105.
Retry
buildInServ
er check
before
upgrade
FD: Fail to open the ./bin/conf/LogNetIf00.conf file, and the

system prompts that the file does not exist.
S:
Restart the update agent on OMM.
Retry
OMM
check
before
upgrade
FD:ERROR: parse 'result=1,detail=The NE Agent has not been started

or does not support MML.' failure. There is no ftpUrl flag.
(mmlCmd:setEnvCheckTask:TASKNAME="ommupdate_2014120815113
5545",NELIST="wcdma#wcdma.omm#R3.11.10.11P05B4.00.200n2#OMMOID=i3f8peaq-1#Y",ENV="ommupdate";)
Operation Result:Failed
S: Restart NE agent. Perform configuration synchronization and NE
upload on NE agent before the NE restart.
FD:
The command is executed successfully, but the Excel report contains
some error information.
Operation result: not pass
S:
Check and correct the error according to the error prompt.
Retry
RNC check
before
upgrade
Retry
OMM data
backup
Retry
Stop
OMM+LOG
SERVICE
process
Retry
OMM+LOG
SERVICE
upgrade
Retry
Start
process
Retry
Check
OMM
process
Retry
buildInServ
er check
after
upgrade
Retry
5.19
Q19: RNCXX_LOG Upgrade Task

Troubleshooting Guide
step name
FD(failure description) & S(solution)
Version Package Download
Retry
Check Before Upgrade
FD:
Ftp to Logservice remotely
S:
Restart the Logservice
Retry
Stop the BuildInServer

process.
Retry
Upgrade
Retry
Start BuildInServer process
FD:
S: Retry
Check after upgrade
Retry
Confirm after upgrade
Retry

ZXWR RNC R3 Remote Upgrade Guide (V3.12 or V3.13 To V3.14) - R1.0

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

ZXWR RNC R3 Remote Upgrade Guide (V3.12 or V3.13 To V3.14) - R1.0

Hochgeladen von

Copyright:

Verfügbare Formate

ZXWR RNC R3 Remote

Upgrade Guide (V3.12/13-toV3.14)

Product Type Technical Proposal

ZTE Confidential Proprietary

2015 ZTE Corporation. All rights reserved.

Product Type Technical Proposal

Reason for Revision

Intended audience: UMTS commissioning & maintenance engineers

ZTE Confidential Proprietary

2015 ZTE Corporation. All rights reserved.

Product Type Technical Proposal

About This Document

Provides an overview of the guide.

2 Preparations for Version Upgrade

Describes the preparations needed for the version upgrade.

3 RNC3IN1 Upgrade Step by Step

Describes the steps of RNC3IN1 upgrade in detail.

4 LOGSVR Upgrade Step by Step

Describes the steps of LOGSVR upgrade in detail.

Introduces some FAQs.

ZTE Confidential Proprietary

2015 ZTE Corporation. All rights reserved.

Product Type Technical Proposal

Preparations for Version Upgrade..................................................................2

RNC3IN1 Upgrade Step by Step......................................................................5

LOGSVR Upgrade Step by Step....................................................................31

ZTE Confidential Proprietary

2015 ZTE Corporation. All rights reserved.

Product Type Technical Proposal

ZTE Confidential Proprietary

2015 ZTE Corporation. All rights reserved.

ZXWR RNC R3 Remote Upgrade Guide (V3.12/13-to-V3.14) Internal Use Only

Preparations for upgrade

Preparations for upgrade

ZXWR RNC R3 Remote Upgrade Guide (V3.12/13-to-V3.14) Internal Use Only

Preparations for Version Upgrade

SIM card for test

Data card for test (supporting HSPA)

Client PC (in Windows OS)

ROMP Debug cable

PC or laptop with 9-pin serial port

SIM card or landline using other

Preparation of Important Spare Boards

Preparation of Software Version

ZXWR RNC R3 Remote Upgrade Guide (V3.12/13-to-V3.14) Internal Use Only

Software Package Name

RNC software version

OMMR software version

License File Update and EMS Upgrade

ICM Configuration Data Model Upload

RNC Configuration File Backup

ZXWR RNC R3 Remote Upgrade Guide (V3.12/13-to-V3.14) Internal Use Only

ZXWR RNC R3 Remote Upgrade Guide (V3.12/13-to-V3.14) Internal Use Only

RNC3IN1 Upgrade Step by Step

Performing Logservice Upgrade

Checking Logservice Configuration

Checking Whether User zte Exists

Clearing the Backup RNC

Canceling the Special Version of

Confirming the Quality of the

Confirming the Left Slot of Master

Performing OMM Board

Creating and Executing the