Professional Documents
Culture Documents
21 Version
Upgrade Guide
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.
and
are registered trademarks 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, estopped 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.
ZTE CORPORATION
Addres
s:
Websit
e:
Email:
NO. 55
Hi-tech Road South
ShenZhen
P.R.China
518057
http://dms.zte.com.cn
TSM.Aftersales@zte.com.cn
Revision History
Product Version
V1.00
Document Version
Serial Number
R1.0
First published
R1.1
Author
Date
Document Version
Prepared
by
Reviewed by
2010-12-30
R1.0
Zhao
Yanghao
Chen Qi, Hu
Xiaolan
2011-3-31
R1.1
Zhao
Yanghao
Chen Qi, Hu
Xiaolan
Approved by
II
Description
1 Overview
Overview
3 Scenario 2: Upgrading
SDRV4.09.21.05 to
SDRV4.09.21.08
4 Scenario 3: Commissioning
Newly Established SDRV4.09 Base
Stations
5 Remarks
Remarks
Pre-Upgrade Checklist
III
TABLE OF CONTENTS
1
1.1
1.2
1.3
1.3.1
1.3.2
1.3.3
1.3.4
1.3.5
Overview...........................................................................................................1
Scope of Application..........................................................................................1
Required NE Version.........................................................................................1
Notice................................................................................................................. 2
Version Confirmation..........................................................................................
Operating Interface............................................................................................
SDR Base Station Type.....................................................................................
Remarks for 4.09.21.08P07...............................................................................
Upgrade Method................................................................................................
2
2.1
2.1.1
2.1.2
2.2
2.2.1
2.2.2
2.2.3
2.2.4
2.2.5
2.3
2.3.1
2.3.2
2.3.3
2.3.4
2.4
2.4.1
2.4.2
2.5
2.5.1
2.5.2
2.5.3
2.6
2.6.1
2.6.2
2.6.3
3
3.1
3.1.1
3.1.2
3.2
3.2.1
3.2.2
3.2.3
IV
3.2.4
3.3
3.3.1
3.3.2
3.3.3
3.3.4
3.3.5
3.4
3.4.1
3.4.2
3.4.3
3.5
3.5.1
3.5.2
3.5.3
3.5.4
Status Check...................................................................................................
Software Upgrade (OMCBV4.09).....................................................................71
Version Package Upload..................................................................................
Version Package Download.............................................................................
Version Activation.............................................................................................
Version Confirmation........................................................................................
Data Upload.....................................................................................................
Version Upgrade Completion...........................................................................76
Service Test.....................................................................................................
Upgrade Report...............................................................................................
Post-Upgrade On-Duty Arrangement...............................................................
Version Rollback Procedure.............................................................................77
Version Switch (OMCBV4.09)..........................................................................
Rollback Confirmation......................................................................................
Service Test.....................................................................................................
Rollback Finished.............................................................................................
4
4.1
4.1.1
4.1.2
4.2
4.2.1
4.2.2
4.2.3
4.3
4.3.1
4.3.2
4.3.3
4.4
4.4.1
4.4.2
4.5
4.5.1
4.5.2
4.5.3
4.6
4.6.1
4.6.2
Remarks........................................................................................................117
AppA
A.1
A.2
Pre-Upgrade Checklist.................................................................................119
Pre-Upgrade Checking Items.........................................................................119
Post-Upgrade Checking Items.......................................................................120
FIGURES
Figure 2-1 Choosing Mutex Central Manager.........................................................................7
Figure 2-2 Applying for Mutex Right in Batch..........................................................................7
Figure 2-3 Base Station Configuration Wizard........................................................................8
Figure 2-4 Online Upload Data...............................................................................................8
Figure 2-5 Selecting Managed Element to Upload Data.........................................................9
Figure 2-6 Switching to Master Configuration Set.................................................................10
Figure 2-7 Status Synchronization........................................................................................11
Figure 2-8 Status Synchronization Result.............................................................................12
Figure 2-9 Uploaded Data Created as Master Config Sets...................................................13
Figure 2-10 Choosing Data Backup......................................................................................14
Figure 2-11 Selecting the Path for Data Backup...................................................................14
Figure 2-12 Selecting Managed Elements............................................................................15
Figure 2-13 Managed Elements Backed up Succeessfully...................................................15
Figure 2-14 Choosing Base Station Software Management.................................................17
Figure 2-15 Creating Base Station Version Package............................................................18
Figure 2-16 Selecting the Transition Software Package to Be Uploaded..............................18
Figure 2-17 Version Package Check....................................................................................19
Figure 2-18 Naming Version Package..................................................................................19
Figure 2-19 Uploading Version Package...............................................................................20
Figure 2-20 New Version Package Uploaded.......................................................................20
Figure 2-21 Selecting the Formal Version Package to be Uploaded.....................................21
Figure 2-22 The Same Software Package for All Base Stations of SDRV4.09......................22
Figure 2-23 Selecting Supported BTS Type during the Upload of Formal SDRV4.09 Series
(Important)............................................................................................................................. 22
Figure 2-24 Choosing Batch Export Ne Data........................................................................24
Figure 2-25 Setting the NE to Be Exported and the Export Directory....................................24
Figure 2-26 Operation Result................................................................................................25
Figure 2-27 ZXOMCBSmoothTool Interface.........................................................................26
Figure 2-28 Setting Source Directory and Destination Directory...........................................26
Figure 2-29 Offline Upgrade.................................................................................................27
Figure 2-30 Upgraded XML Files Generated Under the Destination Directory......................27
VI
VII
VIII
IX
TABLES
Table 1-1 SDR Base Station Types & Software Packages......................................................3
XI
Overview
This guide describes three scenarios of SDR upgrade.
Scenario 1: Upgrading V4.00.30 series to V4.09.21 series
Scenario 2: Upgrading SDRV4.09.21.05 to SDRV4.09.21.08
Scenario 3: Commissioning newly established SDRV4.09 base stations (the SDR
delivered to the field is of V4.00.30 series).
Compared with SDRV4.00 series, there are some changes in SDRV4.09 series, that is,
the platform of SDRV4.09 series is changed, and an independent OMCB is installed on
the server to perform the function of the OMCB in iSMG (OMCR & OMCB split).
Therefore, the upgrade from SDRV4.00 series to SDRV4.09 series is more complex
than the upgrade from SDRV4.00.20 series to SDRV4.00.30 series. Two extra
operations are needed: upgrade the transition version package before upgrading SDR
software, and then upgrade SDR configuration data with the offline upgrade tool
(ZXOMCBSmoothTool).
1.1
Scope of Application
Base Station type: BS8700, BS8800, BS8900 (including BS8900A), and BS8906.
Requirements for SDR version: For SDRV4.00.30.08 and later versions, the SDR can be
upgraded to SDRV4.09.21.05/08 directly with the steps in this guide. For SDRV4.00.10x
and SDRV4.00.20x series, the SDR must be upgraded to SDRV4.00.30.08 before they
are upgraded to SDRV4.09.21.05/08, and the iSMG version should also be upgraded
accordingly. Please refer to ZXG10-BSS Version Upgrade Steps-SDR (V4.00.30.08P13)
for details.
1.2
Required NE Version
iBSC
iOMCR
iOMCRV6.20.614c-OMCBV4.00.200m,
OMCBV4.00.200mP004 patched
with
iOMCRV6.20.614c-
OMCB
The
download
path
of
the
latest
version:
http://tsm.zte.com.cn/tsm/FileCenter/File.aspx?Mode=read&FileID=30325094
1.3
Notice
1.3.1
Version Confirmation
Make sure that the name, size and date of the software package are correct, and that
the software package is not damaged by virus.
1.3.2
Operating Interface
All upgrades should be performed on OMCB.
1.3.3
2.
Table 1 -1 shows the specifications of SDR software package for each software
package (based on V4.09.21.05).
1.3.4
SW-BS8700-4.09.21.05-101030.pkg
SW-BS8700E-4.09.21.05-101030.pkg
SW-BS8800_GU360-4.09.21.05-101030.pkg
SW-BS8800_GU360_E-4.09.21.05-101030.pkg
SW-BS8900A-4.09.21.05-101030.pkg
SW-BS8900_GU360-4.09.21.05-101030.pkg
SW-BS8900_GU360_E-4.09.21.05-101030.pkg
SW-BS8906_G060-4.09.21.05-101030.pkg
SW-BS8906_GU060-4.09.21.05-101030.pkg
1.3.5
Upgrade Method
Select a site to perform single-site upgrade. Upgrade all sites in batch after the upgrade
succeeds.
The upgrade method for special BTS versions is omitted in this Guide.
2.1
Upgrade Flow
2.1.1
Upgrade Items
2.1.2
1.
Data upgrade: Upgrade the data from SDRV4.00.30 series to SDRV4.09.21 series
with ZXOMCBSmoothTool.
2.
Software upgrade: Software upgrade falls into two steps. Step 1: upgrade the
transition version on iSMG. Step 2: upgrade the formal version on OMCBV4.09.
(For versions lower than SDRV4.00.30, the SDR must be upgraded to
SDRV4.00.30 before these two steps)
3.
Key Steps
1.
Perform pre-upgrade check, including status check (data, performance, alarm, and
dynamic) and Ismg & OMCB configuration file check.
2.
Upload version package to the database. For iSMG & OMCB, please upload the
version package under the UAPtoL3\Software_Package directory. For
OMCBV4.09, please upload the version package under the Software_Package
directory.
3.
Upgrade data with the ZXOMCBSmoothTool. Upgrade the data from SDRV4.00.30
series to SDRV4.09.21 series, and import the upgraded data into iSMG and
OMCBV4.09 respectively.
4.
Upgrade transition version. Download the transition version from iSMG and activate
the UAPtoL3 version package.
5.
6.
Steps 1, 2 and 3 will not affect service and can be performed in advance. Steps 4 and 5
will interrupt the service of a single site (IPOE, 1 E1) for about 30 minutes.
2.2
Upgrade Preparations
2.2.1
2.2.1.1
iSMG
1.
2.
the
2.2.1.2
OMCBV4.09
1.
the
ums.systemproperty.com.zte.ums.bind.socket.client.ip=*.*.*.*
the internal IP of OMCBV4.09
ums.services.bind.multi.local.addresses=*.*.*.*,*.*.*.*
first IP is the internal network IP of OMCBV4.09
2.
the
Check
the
configuration
file
ums-svr/deploy/deploy020sdrmap.properties on the OMCBV4.09 server, and pay close attention to
the following line:
userdefined-zxwomc-common-nodeb-api.omcb-ftpserver-ip=*.*.*.*
the internal IP of OMCBV4.09
Specifications:
External network IP of iSMG: the IP for the communication between iSMG and MINOS,
that is, the IP of eth3.
Internal network IP of iSMG: the IP for the communication between iSMG and IPBB, that
is, the IP of eth4.
External network IP of OMCBV4.09: the IP for the communication between OMCBV4.09
and EMSV12, that is, the IP of eth3.0.
Internal network IP of OMCBV4.09: the IP for the communication between OMCBV4.09
and IPBB, that is, the IP of eth4.0.
2.2.2
2.2.2.1
On iSMG, click View > Configuration Management, and then click Management
> Mutex Management > Mutex Central Manager, as shown in Figure 2 -1.
2.
In the pop-up Mutex Management dialog box, select the Select All check box, and
then click Apply to apply for mutex right in batch
Note:
If the mutex right of the SDR base station is occupied by other user, we should release
the mutex right before applying for mutex right again.
2.2.2.2
2.
3.
Select the managed elements of which the data needs to be uploaded, and then
click Next.
4.
In the pop-up Parallel Online Upload Data Result dialog box, select the Select All
check box (on the upper right corner) to select all the Switch To Master options of
the ManagedElement items, and then click OK. During the process of SDR data
upload, iSMG will create a new configuration set under the SDR for the uploaded
data. This step is used to switch the new configuration sets to master configuration
sets.
10
5.
In the pop-up Master/Slave switch result dialog box, select the Select All check
box (on the upper right corner) to select all the Status Synchronization options of
the ManagedElement items, and then click OK.
11
6.
In the pop-up Status Synchronization Result dialog box, click OK. Do not select
the All Table Synchronization options. Otherwise, the SDR will reboot.
12
7.
Figure 2 -9 shows that the master configuration sets of all SDR base stations have
been the lastet data uploaded.
13
Note: SDR data upload failure of base stations should be handled immediately.
Otherwise, the following upgrade of these base stations will fail.
2.2.3
On iSMG, click View > Configuration Management, and then click Management
> Data Management > Data Backup, as shown in Figure 2 -10.
14
2.
Select a storage path for data backup, and then click Open.
3.
Select the SDR of which the data needs to be backed up, and then click OK.
15
4.
Check data backup result and see whether all of the configuration sets are backed
up successfully.
16
2.2.4
2.2.4.1
On iSMG, click View > Base Station Software Management, as shown in Figure
2 -14.
17
2.
18
3.
4.
After a version is selected, the system will check the version package, as shown in
Figure 2 -17. About half a minute later, a dialog box for naming the version
19
package pops up, as shown in Figure 2 -18. Do not type in anything, and click OK
directly.
5.
The pop-up Progress message box displays the name of the version package
being uploaded and the upload progress, as shown in Figure 2 -19.
20
6.
About three minutes later, after the version package upload finishes, we can see
the new software package under the SDR Base Station Version Package
Management node.
2.2.4.2
2.
21
3.
22
Figure 2-22 The Same Software Package for All Base Stations of SDRV4.09
Figure 2-23 Selecting Supported BTS Type during the Upload of Formal SDRV4.09
Series (Important)
23
2.2.5
2.2.5.1
Alarm Check
Check the current alarms of SDR base stations in the OMCB and OMCR of iSMG
respectively, and record these alarms.
The broken links in base stations must be handled immediately. Otherwise, the following
upgrade of these base stations will fail.
2.2.5.2
Performance Check
Export the KPI statistics of the base stations from iSMG, analyze and handle the
abnormal statistics immediately, and compare the pre-upgrade and post-upgrade data
upon the completion of upgrade.
2.2.5.3
Dynamic Check
Check whether the base stations work normally on iSMG, for example, whether there
are cells or TRXs blocked abnormally.
2.3
Data Upgrade
Because data is upgraded offline, which will not affect the services of the existing
network, data upgrade can be performed in advance. Do not change the data of the
existing network after the data upgrade is started.
2.3.1
2.3.1.1
On iSMG, click View > Configuration Management, and then click SDR
Management > Data Configuration > Batch Export Ne Data, as shown in Figure
2 -24.
24
2.
In the pop-up Batch Export Ne Data dialog box, set Select Ne and Export
Directory, as shown in Figure 2 -25.
3.
Click OK after finishing the setting, and the Operation Result message box will
pop up, as shown in Figure 2 -26.
25
2.3.2
Offline Upgrade
Upgrade the data from
ZXOMCBSmoothTool
2.3.2.1
SDRV4.00.30
series
to
SDRV4.09.21.05
with
the
Starting ZXOMCBSmoothTool
1.
26
2.3.2.2
Data Upgrade
1.
2.
During the upgrade, the Upgrade Information message box will display the
upgrade progress and upgrade errors, as shown in Figure 2 -29. Please check the
information in the message box carefully, and make sure all data is successfully
upgraded.
27
3.
After finishing the data upgrade, open the destination directory and make sure that
the upgraded XML files exist in the directory, as shown in Figure 2 -30.
Figure 2-30 Upgraded XML Files Generated Under the Destination Directory
28
2.3.3
On iSMG, click View > Configuration Management, and then click SDR
Management > Data Configuration > Batch Input Smooth Upgrade Data, as
shown in Figure 2 -31.
2.
In the pop-up Batch Input Smooth Upgrade Data dialog box, select the data files
generated by ZXOMCBSmoothTool.
29
3.
Click OK, and observe the input result. Make sure that the data is imported
successfully
Batch Input Smooth Upgrade Data will not affect the data in the configuration set of
the SDR. Instead, it will generate a configuration file under the
\tmp\ftp\fulldata409\subnetX\nodeb\nodebX\ directory on iSMG. The
configuration file will be downloaded to the SDR together with the transition version.
2.3.4
30
2.3.4.1
2.
Set Alias, SubNetwork ID, and SETOFMCC in the pop-up UTRAN SubNetwork
dialog box, and then click OK.
31
3.
4.
In the Batch Offline Reverse dialog box, click the Data directory button and
select the files to be loaded into OMCB, that is, the files generated with
ZXOMCBSmoothTool. Set ConfigSet Label (type in the current date to facilitate
identification), and select the subnetwork into which the data will be imported, and
then click OK, as shown in Figure 2 -38.
32
5.
After the SDR base station data is imported successfully, the managed elements
and configuration sets of these base stations will be created automatically under
the Subnetwork node of the Configuration Resource Tree on the left, and the
Operation Result message box will pop up, as shown in Figure 2 -39. Make sure
the data of all base stations is uploaded successfully with the Batch Offline
Reverse function.
33
2.4
Software Upgrade
2.4.1
2.4.1.1
2.4.1.2
On iSMG, choose Base Station Version Management > SDR Base Station
Software Version Management. Then double-click the uploaded software version
package, and click the
34
2.
A Confirm dialog box pops up, indicating that if the Base Stations running version
package No. is the same as that of the version package to be downloaded, the
Base Station may need to restart after main board software is downloaded. Click
OK to confirm it.
3.
Right-click the Base Station of which the version package needs to be downloaded,
and choose Package Download, as shown in Figure 2 -42. Then, the prompt
mesage Download command sent successfully will appear in the right pane, as
shown in Figure 2 -43.
35
Tips:
1.
The version packages of at most 50 base stations can be downloaded at the same time.
2.
3. After the download is finished, it will take several minutes to synchronize the software
version of the master and slave CC boads before the version is activated.
4. In Base Station Software Version Management, different types of base stations are
different in version package, and therefore, it is necessary to download a version package for
each base station type.
4.
During the version package download process, the download progress can be
checked in the Version Package Operation Log window, as shown in Figure 2
-44. After the download is finished, the content of the Result will be Operation
Successfully, as shown in Figure 2 -45. Make sure the version packages of all
base stations are downloaded successfully.
36
2.4.1.3
Version Activation
1.
in
2.
A Confirm dialog box appears, suggesting that acitivating the version package will
synchronize the base station data and restart the base station. Click OK.
37
3.
Right-click the base station of which the version package needs to be activated in
the pop-up Package Activation dialog box, as shown in Figure 2 -48. Then, a
prompt message Activation successful, Base Station is restarting will appear in
the right pane, as shown in Figure 2 -49.
38
4.
During the version package activation, the package activation progress can be
seen in the Result of the Version Package Operation Log tab; after the version
package is activated, a prompt message Operation successful will appear in the
Result, as shown in Figure 2 -50. Make sure that the version packages of all base
stations are activated.
2.4.1.4
Re-downloading
Unlike common upgrade, the version package needs to be downloaded again here (this
operation will cause board reboot and affect services)
1.
Download the version package again (refer to section 2.4.1.2). Because the version
package has been in SDR, the re-download will cause base station reboot (refer to
Figure 2 -41).
2.
After the base station is rebooted, it will automatically break the link with iSMG, and
establish a link with OMCBV4.09.
3.
If SDR base station cannot automatically establish a link with OMCBV4.09, and the
icon is dimmed (as shown in Figure 2 -51), it is necessary to click the Restore
Connection icon
in the right pane to restore the link between the base station
and OMCBV4.09, as shown in Figure 2 -51 & Figure 2 -52.
Figure 2-51 Link Broken between SDR Base station and OMCBV4.09
39
Figure 2-52 Link Established between SDR Base station and OMCBV4.09
in SDR Dynamic Data Management. Select the NEs of which the links need to be
restored, and click Manaul Link Restore, as shown in Figure 2 -53.
After the transition version is upraded, the running SDR software version information
can be queried in SDR Software Version Management window, as shown in Figure
2 -54.
Figure 2-54 Querying Running Main Version Information after Transition Version
Upgrade
40
2.4.2
2.4.2.1
Version Upload
To reduce the workload at the night of upgrade, please perform version upload in
advance. Refer to section 2.2.4.2 for details.
2.4.2.2
2.
A Confirm dialog box appears, indicating that if the Base Stations running version
package No. is the same as that of the version package to be downloaded, the
base station may need to restart after the main board software is downloaded.
Click OK to confirm it.
41
3.
Right-click the base station of which the version package needs to be downloaded,
and then click Package Download.
Tips:
1.
The version packages of at most 50 base stations can be downloaded at the same time.
2.
3. After the download is finished, it will take several minutes to synchronize the software
version of the master and slave CC boards before the version is activated.
42
4. In Base Station Software Version Management, different types of base stations are
different in version package, and therefore, it is necessary to download a version package for
each base station type.
4.
Check whether the download command is sent successfully in Result, and make
sure that the version packages of all base stations are downloaded successfully.
2.4.2.3
Version Activation
It is unnecessary to activate the version manually.
For SDR base stations, the version Nos. of the formal version and the transition version
are the same. During the download process of formal version package on OMCBV4.09,
SDR detects that the version of the running SDR package No. is the same as that of the
version package No. to be downloaded. Therefore, after the software is downloaded, the
base station is restarted directly and the version is also activated. Refer to Figure 2 -55
for the prompt message.
2.4.2.4
Version Confirmation
1.
43
2.
3.
Select the base station of which the version information needs to be queried in the
pop-up Set the querying Condition dialog box, and then click OK.
44
4.
The query result is as shown in Figure 2 -62. Make sure that the Running Main
Version No. of all base stations isV4.09.21.05.
2.4.2.5
2.4.2.5.1
Data Upload
Applying for Mutex Right
1.
2.
Select the Select All check box in the pop-up Mutex Management dialog box, and
then click Apply to apply for mutex right in batch.
45
2.4.2.5.2
Data Upload
1.
46
2.
Choose Configure by Base Station data > Online Upload Data, and then click
Next.
3.
Select all managed elements of which the data needs to be uploaded, and then
click Next.
47
4.
In the pop-up Parallelly Online Upload Data Result dialog box, select the Select
All check box to select all the Switch To Master options, and then click OK.
48
5.
In the pop-up Parallel online upload data Master/Slave switch result dialog
box, select the Select All check box (on the upper right corner) to select all the
Status Synchronization options, and click OK.
49
6.
2.5
2.5.1
Service Test
Service test is performed either by the customer or by our network optimization team.
The test details are omitted here.
2.5.2
Upgrade Report
After the upgrade succeeds, send the Major Operation Implementation Report to
relevant staff.
50
2.5.3
2.6
2.6.1
2.6.1.1
Package Switch
1.
51
2.
Right-click the managed element of which the software version needs to be rolled
back, and choose Package Switch. Then a Confirm dialog box pops up, as shown
in Figure 2 -72.
3.
Click OK to switch the version packages and reboot the base station.
52
2.6.1.2
Batch Package Switch will roll back the software versions of all base stations in
the query list. Do not use Batch Package Switch if the version of some base
stations in the query list does not need to be rolled back.
2.
In the query result interface of Section 2.6.1.1, right-click the version information,
and then choose Package Batch Switch, as shown in Figure 2 -74.
53
3.
4.
It takes a little while to reboot SDR after the version package switch. Please wait.
54
2.6.2
iSMG-to-OMCBV4.09 Swith
1.
After the version rollback, the link between OMCBV4.09 and the base station will
be automatically released (if it cannot be released, please select the managed
element in Configuration Management, and click the
icon in the right pane to
release the link manually), and the link between iSMG and the base station will be
automatically established.
2.
If the link between iSMG and the base station cannot be restored, please restore
the link manually. Click View > Configuration Management, and then double-click
the managed element of which the version needs to be rolled back, and then click
the Link Restore icon
3.
on the right.
55
4.
5.
After the version rollback, the link between SDR base station and iSMG will be
restored, but the icon before the managed element is still
2 -79.
, as shown in Figure
If there are many base station to be rolled back, the link can be restored by restoring
links in batch in Base Sattion Centralized Management. Select the NEs of which
the links need to be restored, and click Recover Connection, as shown in Figure 2
-81.
56
2.6.3
2.
Double-click SDR Software Version Management, and then click the Information
Query icon
3.
Make sure that the running main version No. of all base stations is V4.00.30.08.
3.1
Upgrade Flow
3.1.1
Upgrade Items
1.
2.
57
3.
3.1.2
Key Steps
1.
Perform pre-upgrade check, including status check (data, performance, alarm, and
dynamic).
2.
Upload version package to the database. For OMCBV4.09, please upload the
version package under the Software_Package directory of SDRV4.09.21.08.
3.
4.
Perform data upload again on OMCBV4.09, and make sure the data in SDR is the
same as that in OMCBV4.09.
5.
Steps 1, 2 and 3 will not affect service and can be performed in advance. Steps 3 and 4
will interrupt service.
3.2
Upgrade Preparations
3.2.1
3.2.1.1
58
2.
In the pop-up Mutex Management dialog box, select the Select All check box, and
then click Apply to apply for mutex right in batch
3.2.1.2
59
2.
3.
Select the managed elements of which the data needs to be uploaded, and then
click Next.
60
61
4.
In the pop-up Parallel Online Upload Data Result dialog box, select the Select All
check box (on the upper right corner) to select all the Switch To Master options of
the ManagedElement items, and then click OK.
5.
In the pop-up Master/Slave switch result dialog box, select the Select All check
box (on the upper right corner) to select all the Status Synchronization options of
the ManagedElement items, and then click OK.
62
6.
In the pop-up Status Synchronization Result dialog box, click OK. Do not select
the All Table Synchronization options. Otherwise, the SDR will reboot.
63
7.
Figure 3 -90 shows that the master configuration sets of all SDR base stations
have been the lastet data uploaded.
64
Note: SDR data upload failure of base stations should be handled immediately.
Otherwise, the following upgrade of these base stations will fail.
3.2.2
65
2.
Select a storage path for data backup, and then click Open.
3.
Select the SDR of which the data needs to be backed up, and then click OK.
66
4.
Check data backup result and see whether all of the configuration sets are backed
up successfully.
67
3.2.3
package
under
the
\Software_Package
directory
Click View > Base Station Software Management, as shown in Figure 3 -95.
68
on
2.
3.
But under the Software_Package directory, the software package is the same
for all SDR base station types, as shown in Figure 3 -97. After the version package
passes the check (refer to Figure 2 -17), select the Supported BTS Type in the
69
pop-up SDR Base Station Version Package dialog box as shown in Figure 3 -98.
If there are two or more base station types in the network, each type of version
packages must be uploaded.
Note: On OMCBV4.09.21.08, the software package is the same for dual-rack SDR and
single-rack SDR.
Figure 3-97 The Same Software Packages for All Base Stations of SDRV4.09
70
Figure 3-98 The Same Software Packages for All Base Stations of SDRV4.09
3.2.4
Status Check
3.2.4.1
Alarm Check
Check the current alarms of SDR base stations on OMCBV4.09, and record these
alarms.
The broken links in base stations must be handled immediately. Otherwise, the following
upgrade of these base stations will fail.
3.2.4.2
Performance Check
Export the KPI statistics of the base stations from iSMG, analyze and handle the
abnormal statistics immediately, and compare the pre-upgrade and post-upgrade data
upon the completion of upgrade.
3.2.4.3
Dynamic Check
Check whether the base stations work normally on OMCBV4.09, for example, whether
there are cells or TRXs blocked abnormally.
71
3.3
3.3.1
3.3.2
On OMCBV4.09, click View > Configuration Management, and then choose Base
Station Version Management > SDR Base Station Software Version
Management. Then double-click the uploaded software version package, and click
the
2.
A Confirm dialog box pops up, indicating that if the Base Stations running version
package No. is the same as that of the version package to be downloaded, the
Base Station may need to restart after main board software is downloaded. Click
OK to confirm it.
72
3.
Right-click the Base Station of which the version package needs to be downloaded,
and choose Package Download, as shown in Figure 3 -101.
Tips:
1.
The version packages of at most 50 base stations can be downloaded at the same time.
2.
3. After the download is finished, it will take several minutes to synchronize the software
version of the master and slave CC boards before the version is activated.
4. In Base Station Software Version Management, different types of base stations are
different in version package, and therefore, it is necessary to download a version package for
each base station type.
73
4.
Check whether the download command is sent successfully in the Result. Make
sure the version packages of all base stations are downloaded successfully.
3.3.3
Version Activation
1.
2.
in
A Confirm dialog box appears, suggesting that acitivating the version package will
synchronize the base station data and restart the base station. Click OK.
3.
Right-click the base station of which the version package needs to be activated in
the pop-up Direct Package Activation dialog box, as shown in Figure 3 -104.
Then, a prompt message Activation successful, Base Station is restarting will
appear in the right pane.
74
4.
During the activation process, system will prompt Synchronize tables or not? as
shown in Figure 3 -105.
3.3.4
Version Confirmation
1.
75
2.
3.
Select the base station of which the version information needs to be queried in the
pop-up Set the querying condition dialog box, and then click OK.
76
4.
The query result is as shown in Figure 3 -109. Make sure that the Running Main
Version No. of all base stations is V4.09.21.08.
3.3.5
Data Upload
Perform data upload again and make sure the data in SDR is the same as that on
OMCB.
3.4
3.4.1
Service Test
Service test is performed either by the customer or by our network optimization team.
The test details are omitted here.
3.4.2
Upgrade Report
After the upgrade succeeds, send the Major Operation Implementation Report to
relevant staff.
3.4.3
77
3.5
3.5.1
3.5.1.1
Package Switch
1.
78
2.
Right-click the managed element of which the software version needs to be rolled
back, and choose Package Switch. Then a Confirm dialog box pops up, as shown
in Figure 3 -111.
3.
Click OK to switch the version packages and reboot the base station.
3.5.1.2
Batch Package Switch will roll back the software versions of all base stations in
the query list. Do not use Batch Package Switch if the version of some base
stations in the query list does not need to be rolled back.
2.
In the query result interface as shown in Section 3.5.1.1, right-click the version
information, and then choose Package Batch Switch, as shown in Figure 3 -113.
79
3.
4.
It takes a little while to reboot SDR after the version package switch. Please wait.
80
3.5.2
Rollback Confirmation
Query the running version of a base station, and make sure that the version rollback is
successful.
3.5.3
Service Test
Service test is performed either by the customer or by our network optimization team.
The test details are omitted here.
3.5.4
Rollback Finished
4.1
Upgrade Flow
4.1.1
Upgrade Items
1.
Data configuation: configure SDR physical data with SDR Physical Data Quick
Configuration Tool (ZXSDRConfTool).
81
4.1.2
2.
Software upgrade: Software upgrade falls into two steps. Step 1: upgrade the
transition version on iSMG. Step 2: upgrade the formal version on OMCBV4.09
(For versions lower than SDRV4.00.30 series, the SDR must be upgraded to
SDRV4.00.30 series before these two steps).
3.
Key Steps
1.
Perform pre-upgrade check, including mainly BSC status check and iSMG & OMCB
configuration file check (for newly established sites).
2.
Upload version package to the database. For iSMG, please upload the version
package under the UAPtoL3\Software_Package directory. For OMCBV4.09,
please upload the version package under the Software_Package directory.
3.
Configure SDR physical data with ZXSDRConfTool, and import the configured data
to iSMG and OMCBV4.09 respectively.
4.
Upgrade transition version. Download the transition version from iSMG and activate
the UAPtoL3 version package.
5.
Upgrade software. Download and activate the version package under the
Software_Package directory on OMCBV4.09.
6.
Steps 1, 2 and 3 will not affect service and can be performed in advance. Steps 4 and 5
will interrupt the service of a single site (IPOE, 1 E1) for about 30 minutes.
4.2
Upgrade Preparations
4.2.1
4.2.1.1
iSMG
1.
82
ums.systemproperty.com.zte.ums.bind.socket.client.ip=*.*.*.*
the internal network IP of iSMG
ums.services.bind.multi.local.addresses=*.*.*.*,*.*.*.*
the first IP is the internal network IP of iSMG
2.
4.2.1.2
OMCBV4.09
1.
2.
Check
the
configuration
file
ums-svr/deploy/deploy020sdrmap.properties on the OMCBV4.09 server, and pay close attention to
the following line:
userdefined-zxwomc-common-nodeb-api.omcb-ftpserver-ip=*.*.*.*
the internal network IP of OMCBV4.09
Specifications:
External network IP of iSMG: the IP for the communication between iSMG and MINOS,
that is, the IP of eth3.
Internal network IP of iSMG: the IP for the communication between iSMG and IPBB, that
is, the IP of eth4.
External network IP of OMCBV4.09: the IP for the communication between OMCBV4.09
and EMSV12, that is, the IP of eth3.0.
Internal network IP of OMCBV4.09: the IP for the communication between OMCBV4.09
and IPBB, that is, the IP of eth4.0.
83
4.2.2
4.2.2.1
On iSMG, click View > Base Station Software Management, as shown in Figure
4 -116.
2.
84
3.
4.
After a version is selected, the system will check the version package, as shown in
Figure 4 -119. About half a minute later, a dialog box for naming the version
85
package pops up, as shown in Figure 4 -120. Do not type in anything, and click OK
directly.
5.
The pop-up Progress message box displays the name of the version package
being uploaded and the upload progress, as shown in Figure 4 -121.
86
6.
About three minutes later, after the version package upload finishes, we can see
the new software package under the SDR Base Station Version Package
Management node.
4.2.2.2
2.
87
3.
88
Figure 4-124 The Same Software Packages for All Base Stations of SDRV4.09
Figure 4-125 Selecting Supported BTS Type during the Upload of Formal SDRV4.09
Series (Important)
89
4.2.3
4.2.3.1
Alarm Check
Check whether there are BSC alarms on iSMG, and handle these alarms.
4.3
4.3.1
Configurating Data
Finish SDR physical data configuration with ZXSDRConfTool.
4.3.1.1
Editing Template
Start ZXSDRConfTool (please use ZXSDRConfTool3.2.4 or later versions), select
SDR_4.09.21.08_QUICKCONF_TEMPLATE_GSM.xls
or
SDR_4.09.21.08_QUICKCONF_TEMPLATE_GU.xls to edit data.
4.3.1.2
90
4.3.2
On iSMG, click View > Configuration Management, and then click SDR
Management > Data Configuration > Batch Input Smooth Upgrade Data, as
shown in Figure 4 -127.
2.
In the pop-up Batch Input Smooth Upgrade Data dialog box, select the data files
generated by the ZXSDRConfTool.
91
3.
Click OK, and observe the input result. Make sure that the data is imported
successfully
4.
4.3.3
Batch Input Smooth Upgrade Data will not affect the data in the configuration set
of the SDR. Instead, it will generate a configuration file under the
\tmp\ftp\fulldata409\subnetX\nodeb\nodebX\ directory on the iSMG.
The configuration file will be downloaded to the SDR together with the transition
version.
92
2.
Set Alias, SubNetwork ID, and SETOFMCC in the pop-up UTRAN SubNetwork
dialog box, and then click OK.
3.
93
4.
In the Batch Offline Reverse dialog box, click the Data directory button and
select the files to be loaded into OMCB, that is, the files generated with
ZXOMCBSmoothTool. Set ConfigSet Label (type in the current date to facilitate
identification), select the subnetwork into which the data will be imported, and then
click OK, as shown in Figure 4 -134.
94
5.
After the SDR base station data is imported successfully, the managed elements
and configuration sets of these base stations will be created automatically under
the Subnetwork node of the Configuration Resource Tree on the left, and the
Operation Result message box will pop up, as shown in Figure 4 -135. Make sure
the data of all base stations is uploaded successfully with the Batch Offline
Reverse function.
95
4.4
Software Upgrade
4.4.1
4.4.1.1
4.4.1.2
On iSMG, click View > Configuration Management, and then choose Base
Station Version Management > SDR Base Station Software Version
Management. Then double-click the uploaded software version package, and click
the
2.
A Confirm dialog box pops up, indicating that if the Base Stations running version
package No. is the same as that of the version package to be downloaded, the
Base Station may need to restart after main board software is downloaded. Click
OK to confirm it.
96
3.
Right-click the Base Station of which the version package needs to be downloaded,
and choose Package Download, as shown in Figure 4 -138. Then, the prompt
mesage Download command sent successfully will appear in the right pane, as
shown in Figure 4 -139.
Tips:
ZTE Confidential Proprietary
97
1.
The version packages of at most 50 base stations can be downloaded at the same time.
2.
3. After the download is finished, it will take several minutes to synchronize the software
version of the master and slave CC boards before the version is activated.
4. In Base Station Software Version Management, different types of base stations are
different in version package, and therefore, it is necessary to download a version package for
each base station type.
4.
During the version package download process, the download progress can be
checked in the Version Package Operation Log window, as shown in Figure 4
-140. After the download is finished, the content of the Result will be Operation
Successfully, as shown in Figure 2 -45. Make sure the version package of all
base stations is downloaded successfully.
4.4.1.3
Version Activation
1.
98
in
2.
A Confirm dialog box appears, suggesting that acitivating the version package will
synchronize the base station data and restart the base station. Click OK.
3.
Right-click the base station of which the version package needs to be activated in
the pop-up Package Activation dialog box, as shown in Figure 4 -144. Then, a
prompt message Activation successful, Base Station is restarting will appear in
the right pane, as shown in Figure 4 -145.
99
4.
During the version package activation, the package activation progress can be
seen in the Result of the Version Package Operation Log tab; after the version
package is activated, a prompt message Operation successful will appear in the
Result, as shown in Figure 4 -146. Make sure that the version packages of all
base stations are activated.
4.4.1.4
Re-downloading
Unlike common upgrade, the version package needs to be downloaded again here (this
operation will cause board reboot and affect services)
100
1.
Download the version package again (refer to section 4.4.1.2). Because the version
package has been in SDR, the re-download will cause base station reboot (refer to
Figure 4 -137).
2.
After the base station is rebooted, it will automatically break the link with iSMG, and
establish a link with OMCBV4.09.
3.
If the SDR base station cannot automatically establish a link with OMCBV4.09, and
the
Figure 4-147 Link Broken between SDR Base station and OMCBV4.09
Figure 4-148 Link Established between SDR Base station and OMCBV4.09
After the transition version is upraded, the running SDR software version information
can be queried in SDR Software Version Management window, as shown in Figure
4 -149.
101
Figure 4-149 Querying Running Main Version Information after Transition Version
Upgrade
4.4.2
4.4.2.1
Version Upload
To reduce the workload at the night of upgrade, please perform version upload in
advance. Refer to section 2.2.4.2 for details.
4.4.2.2
On OMCBV4.09, click View > Configuration Management, and then choose Base
Station Version Management > SDR Software Version Management. Then
double-click the uploaded software version package, and click the
download the software version package.
icon to
2.
A Confirm dialog box appears, indicating that if the Base Stations running version
package No. is the same as that of the version package to be downloaded, the
base station may need to restart after the main board software is downloaded.
Click OK to confirm it.
102
3.
Right-click the base station of which the version package needs to be downloaded,
and then choose Package Download.
Tips:
1.
The version packages of at most 50 base stations can be downloaded at the same time.
2.
3. After the download is finished, it will take several minutes to synchronize the software
version of the master and slave CC boards before the version is activated.
4. In Base Station Software Version Management, different types of base stations are
different in version package, and therefore, it is necessary to download a version package for
each base station type.
103
4.
Check whether the download command is sent successfully in Result, and make
sure that the version packages of all base stations are downloaded successfully.
4.4.2.3
Version Activation
It is unnecessary to activate the version manually.
For SDR base stations, the version Nos. of the formal version and the transition version
are the same. During the download process of formal version package on OMCBV4.09,
SDR detects that the version of the running SDR package No. is the same as that of the
version package No. to be downloaded. Therefore, after the software is downloaded, the
base station is restarted directly and the version is also activated. Refer to Figure 4 -151
for the prompt message.
4.4.2.4
Version Confirmation
1.
2.
104
3.
Select the base station of which the version information needs to be queried in the
pop-up Set the querying condition dialog box, and then click OK.
4.
The query result is as shown in Figure 4 -157. Make sure that the Running Main
Version No. of all base stations is V4.09.21.05.
105
4.4.2.5
Data Upload
2.
Select the Select All check box in the pop-up Mutex Management dialog box, and
then click Apply to apply for mutex right in batch.
106
107
2.
Choose Configure by Base Station data > Online Upload Data, and then click
Next.
3.
Select all managed elements of which the data needs to be uploaded, and then
click Next.
108
4.
In the pop-up Parallelly Online Upload Data Result dialog box, select the Select
All check box to select the Switch To Master options, and then click OK.
109
5.
In the pop-up Parallel online upload data Master/Slave switch result dialog
box, select the Select All check box (at the upper right side) to select all Status
Synchronization options, and click OK.
110
6.
4.5
4.5.1
Service Test
Service test is performed either by the customer or by our network optimization team.
The test details are omitted here.
4.5.2
Upgrade Report
After the upgrade succeeds, send the Major Operation Implementation Report to
relevant staff.
111
4.5.3
4.6
4.6.1
4.6.1.1
Package Switch
1.
112
2.
Right-click the managed element of which the software version needs to be rolled
back, and choose Package Switch. Then a Confirm dialog box pops up, as shown
in Figure 4 -167.
3.
Click OK to switch the version packages and reboot the base station.
113
4.6.1.2
Batch Package Switch will roll back the software versions of all base stations in
the query list. Do not use Batch Package Switch if the version of some base
stations in the query list does not need to be rolled back.
2.
In the query result interface as shown in section 4.6.1.1, right-click the version
information, and then choose Package Batch Switch, as shown in Figure 4 -169.
114
Figure 4-169 Choosing Package Batch Switch in the Running Version Query Result
Interface
3.
4.
It takes a little while to reboot SDR after the version package switch. Please wait.
115
4.6.2
2.
Double-click SDR Software Version Management, and then click the Information
Query icon
Remarks
For SDRV4.09.21.08P07 and later versions, there are three disk space optimization
methods.
System automatically deletes the CPU & FPGA version files of the CC board in the
SW1 and SW2 folders of the disk under certain certain circumstances.
Excute a disk cleanup command manually on OMCB to clear the junk files in
the disk. This solution is applicable to OMCBV4.09.21.11/SDRV4.09.21.08P07.
The third method deletes only junk files and logs, and will not affect the running and
switch of versions. The possible influences of the first two solutisons are listed below.
METHOD 1
116
Optimization Description:
Take the upgrade from SDRV4.00.3008 (hereafter referred to as 3008) to
SDRV4.00.21.08P07 (hereafter referred to as 2108P07) as an example. During the
activation of 2108P07, the 2108P07 version file of the CC board in the SW1or SW2
folder, including CPU & FPGA version files, will be deleted. But because these two files
still exist in the BIN directory, 2108P07 can also be run and started. Meanwhile, because
the files of 3008 were not deleted, version rollback is also possible.
Problem:
If it is necessary to switch to 2108P07 after version rollback, the switch will fail, because
there is no 2108P07 version file for the CC board in the disk.
Solution:
The switch failure occurs because the 2108P07 version file of the CC board was deleted
in the disk of SDR. This problem can be solved by downloading the version package
again from OMCB. After the version package is downloaded, please select the slave
main version package to activate the vesion, and it is not necessary to select version
switch.
METHOD 2
Optimization Description:
Because the running & slave main version packages of the RRU have been stored in the
RRU, deleting the running main version package will not affect the running of the RRU
and the version switch.
Problem:
When it is necessary to repace the RRU or expand the RRU capacity due to fault, if the
version of the RRU is not the same as the running version in SDR, the RRU will send a
request for the version to CC board. But because the version has been deleted in the
CC board, RRU cannot acquire the version, and therefore cannot work properly.
Solution:
Download the version package from OMCB.
117
Items
Record
FinishedUnfinished
FinishedUnfinished
FinishedUnfinished
YesNo
NormalAbnormal
NormalAbnormal
NormalAbnormal
Record
interrupted/uncommissioned
base stations
FinishedUnfinished
YesNo
10
YesNo
11
Remarks
The running
SDR
software
version
information
can be
queried on
OMCB
Upload the
data
configured on
SDR before
upgrade, and
export the
data for later
data
restoration
YesNo
118
SN
Items
Record
Remarks
A.2
YesNo
Items
Record
YesNo
YesNo
YesNo
YesNo
YesNo
NormalAbnormal
NormalAbnormal
10
NormalAbnormal
11
NormalAbnormal
Remarks
119