SJ-20130704144811-005-ZXSDR OMMB (V12.13.30) Version Management Operation Guide

ZXSDR OMMB
Version Management Operation Guide
Version: V12.13.30
ZTE CORPORATION
No. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright © 2013 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution 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. Additionally, the contents of this document are protected by
contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No. Revision Date Revision Reason
R1.0 2013–08–30 First Edition
Serial Number: SJ-20130704144811-005
Publishing Date: 2013-08-30 (R1.0)
SJ-20130704144811-005|2013-08-30 (R1.0) ZTE Proprietary and Confidential

Contents
About This Manual ......................................................................................... I
Chapter 1 Software Version Management................................................ 1-1
Chapter 2 BS Version Upgrade ................................................................. 2-1
2.1 Upgrade Preparation .......................................................................................... 2-2
2.2 Adding a Version Package .................................................................................. 2-2
2.3 Viewing a Version Package................................................................................. 2-4
2.4 Creating an Upgrade Task .................................................................................. 2-6
Chapter 3 Common Operations ................................................................ 3-1

3.1 Exporting and Importing NE Status Information .................................................... 3-1
3.2 Querying an NE Version Package ....................................................................... 3-3
3.3 Creating a Deactivation Task............................................................................... 3-5
3.4 Creating a Package Deletion Task ....................................................................... 3-7
3.5 Creating a Rollback Task .................................................................................... 3-9
3.6 Creating a Special Firmware Pre-activate Task ...................................................3-11
3.7 Creating a Repository File Task......................................................................... 3-13
Figures............................................................................................................. I
Glossary ........................................................................................................ III

II

About This Manual
Purpose
This manual describes version management operations of the multimode Base Station
(BS) Operation & Maintenance Module (OMM).
Intended Audience
This manual is intended for:
l Commissioning engineers
l Maintenance engineers
Prerequisite Skills and Knowledge

To use this document effectively, users should have a general understanding of wireless
telecommunications technology. Familiarity with the multimode BS OMM and its related
components is helpful.
What Is in This Manual

This manual contains the following chapters:
Chapter Summary
1, Software Version Describes the software version management function, how to access the
Management software version management tab, and the related terms.
2, BS Version Upgrade Describes how to upgrade the BS version.
3, Common Operations Describes the common operations for version management.
Conventions
This manual uses the following typographical conventions:
Typeface Meaning
Bold Menus, menu options, function names, input fields, option button names, check
boxes, drop-down lists, dialog box names, window names, parameters, and
commands.
Note: provides additional information about a certain topic.

II

Chapter 1
Software Version
Management
Function
Software version management refers to managing version packages (version files of
boards) on the version library and NEs. It allows you to perform the following operations:
l Manage the version library.

l Download, pre-activate, validate, query, deactivate, roll back, and delete NE version
packages.
Software Version Management Tab

All software version management operations are performed on the Software Version
Management tab.
To access the Software Version Management tab, perform one of the following
operations:
1. On the Element Management System (EMS) client, right-click a multimode base
station NE agent and select NE Agent Management > Start from the shortcut menu.
After the NE agent is started successfully, the node icon changes color (red, blue, or
white, depending on the alarm that occurs on the NE).
2. Right-click the NE agent and select NE Management > Start NE Management from
the shortcut menu.
After the NE agent is started successfully, the green icon is displayed on the
lower-right corner of the NE agent node.
3. Right-click the NE agent and select NE Management > Software Version

Management from the shortcut menu. The Software Version Management tab is
displayed, see Figure 1-1.
Figure 1-1 Software Version Management Tab
1-1

ZXSDR OMMB Version Management Operation Guide
Terms
This manual uses the following terms:
l Version package
A version package is a set of files that contain the version information of some or all
boards.
l Version library
A version library is a database that stores version packages on the server.
l Adding a version package
Adding a version package refers to adding a version package to the version library.
l Deleting a version package
Deleting a server version package refers to deleting a version package from the
version library.
l NE
An NE is a Base Station (BS) managed by the EMS.
l Downloading a version package
Downloading a version package refers to downloading a version package from the
version library to NEs.
l Version package deletion task
A version package deletion task is used to delete a firmware version package and a
standby version package (not including a hotfix version package) from NEs.
l Querying an NE version package
Querying an NE version package refers to querying a version package that is stored
and running on NEs.
l Downloading configuration data
Downloading configuration data refers to downloading the configuration data to NEs
during pre-activation.
l Pre-activation
Pre-activation refers to setting a target version package to active status, and the
version package will be loaded when the NE is activated.
l Applying activation
Applying activation refers to changing the status of a version package from active
status to running status.
l Deactivation
Deactivation refers to changing the status of a version package from active status to
standby status.
l Failed NE
1-2

Chapter 1 Software Version Management
It is convenient for the users to check whether NEs fail or succeed in the operations
of task upgrade management, task query management or special task management.
1-3

This page intentionally left blank.
1-4

Chapter 2
BS Version Upgrade
The Base Station (BS) version upgrade flow is as follows:
1. Upgrade preparation:
a. Back up the configuration data of the Element Management System (EMS).
b. Prepare a version package for upgrade.
2. Add the version package: add the version package to the version library.
3. View the version package: view the version package that is added to the version library
and verify that it is correct.
4. Create an upgrade task:
a. Create a download and pre-activation task to download the version package to
NEs and pre-activate it.
b. Create a version package query task to verify that the pre-activated version
package is correct.
c. Create an activation task and activate the version package in active status during
the time with fewer users.
d. Create a version package query task and verify that the upgraded version package
is correct.
Figure 2-1 illustrates the package status conversion on an NE during upgrade.
Figure 2-1 Package Status Conversion Diagram
l After being pre-activated, the version package in standby status is changed to active
status.
2-1

l After being deactivated, the version package in active status is changed to standby
status and can be deleted.
l After activation is applied, the version package in active status is changed to running
status (the NE is restarted if a platform version package is included), and the NE loads
and runs the version package.
l After being upgraded, the original version package is changed to standby status and
can be deleted.
Note:
A hotfix version package cannot be pre-activated or deactivated. It only has standby status
and running status. The downloaded hotfix package is in running status if its father version
package is in running status; the hotfix package is in standby status if its father version
package is in standby status. The hotfix package can be deleted in both status.
Table of Contents
Upgrade Preparation ..................................................................................................2-2
Adding a Version Package .........................................................................................2-2
Viewing a Version Package ........................................................................................2-4
Creating an Upgrade Task..........................................................................................2-6
2.1 Upgrade Preparation

Before upgrading the NE version, you must perform the following operations:
l Copy the version package file required for the upgrade to the computer where the
client runs.
l Back up the configuration data of the EMS.
2.2 Adding a Version Package

This procedure describes how to add a version package to the version library of the server.
Context
You can add a version package through either the local path or the remote path.
Steps
1. On the Software Version Management tab, expand the Software Version
Management navigation tree in the left pane.
2. Select the Version Library Management node, and click the (Add Version
Package) icon on the right toolbar. The Add Version Package dialog box is
2-2

Chapter 2 BS Version Upgrade
Figure 2-2 Add Version Package Dialog Box
3. Set the path for adding a version package: local path or remote path (ftp://version:***
directory).
Note:
Before setting the remote path, you should upload the version package to the ums/u
ms-svr/version directory of the server.
4. Select the version package file to be added under the local path, and click the Open
button. The system automatically analyzes the version package and displays the
progress of adding the package.
5. After the version package is successfully added, click Close to close the Add Version
Package dialog box. The added version package is displayed in Version Package
List, see Figure 2-3.
Figure 2-3 Version Package List
2-3

6. (Optional) Click the (Export) icon on the toolbar to export the records in the version
package list to an HTML file or an XML file.
– End of Steps –
2.3 Viewing a Version Package

This procedure describes how to view the details of a version package file in the version
library, including the file name, software type, standard, version, parent version, and
application scope.
Steps
1. In the navigation tree of the Software Version Management view, select the Version
Library Management node.
2. Double-click a package record in Version Package List. The View Details dialog box
is displayed, see Figure 2-4. For the version package parameter descriptions, refer to
Table 2-1.
Figure 2-4 View Details Dialog Box
Table 2-1 Version Package Parameter Descriptions
Parameter Description
Version Package Package file name with the .pkg suffix.
2-4

Version Package Type Software type that the package applies to.
There are six types of software:
l BaseBand Unit (BBU)
l BBU patch
l Remote Radio Unit (RRU)
l RRU patch
l Firmware
l Hotfix
Version Package Standard There are two standards of version packages:

l Plat: the package including the version files of platform
boards and common-mode boards.
l UMTS/GSM/TD-SCDMA/CDMA/LTE FDD/LTE TDD:
the package including the version files of product
boards.
Version Package version number.
Father Version Version number of the parent package of the patch

package.
Created Time Package creation time.
Application Scope Indicates the NE standards that the package applies to.
The application scope can include one or multiple NE
standards. If the application scope is null, it indicates the
package applies to all standards. The NE standard can be
configured in Configuration Management.
For example, if the application scope of the package is
TD-SCDMA, only the single-mode TD-SCDMA BS can
download and activate the package.
NE Type NE types to which the version package is applicable.
3. In Version Package List, right-click the package record, and select View Version
Package Information from the shortcut menu. The software version details of the
package are displayed, see Figure 2-5.
2-5

Figure 2-5 Software Version Details of the Package
4. (Optional) Delete a version package in the version library.

a. In Version Package List, right-click a package record, and select Delete from the
shortcut menu. The Confirm dialog box is displayed.
b. Click Yes.
2.4 Creating an Upgrade Task

This procedure describes how to create an NE version upgrade task.
Steps
2. Select the Upgrade Task Management node. The upgrade task management window
is displayed, see Figure 2-6.
2-6

Figure 2-6 Upgrade Task Management Window
3. Click the (Create Upgrade Task) icon on the toolbar. The Create Upgrade Task
dialog box is displayed, see Figure 2-7.
Figure 2-7 Create Upgrade Task Dialog Box
4. Enter a name in the Task name text box. The task name is set to the current time
by default. When the task is created, the task name is displayed and the operation
information is added in Task List. By default, the task name is in the format of
“operation information + creation time”. If the task name is customized, it is in format
of “operation information + entered task name”, for example, see Figure 2-8.
2-7

5. In the Select NE area, select the NE that requires version upgrade.
Note:
l After an NE is selected, the version packages that do not comply with the
standards of the NE are automatically filtered.
l If multiple NEs are selected, you can import NE status information through an
Excel file. For the operation descriptions, refer to 3.1 Exporting and Importing NE
Status Information.
6. In the Select version package area, select one or multiple version packages for
upgrade.
Click Add Version Package to add additional version packages to the version library.
7. In the Select operation area, select the upgrade operations as required. For the
parameter descriptions, refer to Table 2-2.
Table 2-2 Parameter Descriptions for Version Upgrade Operations
Download Downloads the selected version package to the

corresponding NE.
Pre-activate Sets the status of the selected version package from

standby status to active status.
After the version package is pre-activated, the NE does not
run the pre-activated version until the Apply activation
operation is performed.
The Pre-activate operation allows you to check the version
packages in active status.
Apply activation Changes the version package from active status to running
status (the NE is restarted if a platform version package
is included).
Query version Queries the package version running on the NE.
Delete file before download Before downloading the version package, you should clean
up the disk by selecting the following items:
l Temp file
l Other file
l Backup file
l Log file
Download current data Generates a configuration data file based on the current
configuration data, and downloads the file to the NE.
2-8

Download off-line data Obtains the configuration data file saved under the default
path, and downloads the file to the NE.
Check configuration data Check whether the version of preupgrade configuration

and the version of current base station configuration are
consistent.
Board standard settings Select the board standard in accordance with the version
package.
Note:
l The items in the Delete file before download area can be selected, only when
Download is selected. Temp file, Other file, and Backup file are selected by
default.
l The Download current data, Download off-line data and Check configuration
data operations are available only when the Pre-activate operation is selected.
8. Select a board standard in the Board standard settings drop-down list.

9. Click OK. The Confirm dialog box is displayed.
10. Enter the verification code, and then click OK to create the upgrade task.
The successfully created upgrade task is displayed in Task List, and the upgrade
progress is displayed in the Progress column, see Figure 2-8
Figure 2-8 The Task List of Successfully Created Upgrade Tasks
11. (Optional) To easily view the upgrade task information in future, click the (Export)
icon on the toolbar to save the records in the task list in an HTML or XML file.
12. For optional operations after the upgrade task is created, refer to Table 2-3.
2-9

Table 2-3 Operations Related to Upgrade Task Creation
Operation Description
Create an upgrade task from The Download, Pre-activate, and Apply activation operations
the shortcut menu are performed separately. You can select the NEs included in the
previous upgrade task and perform the next operation.
Right-click a successfully downloaded task in Task List, and
select Create Upgrade Task from the shortcut menu. The
Create Upgrade Task dialog box is displayed. In the Select NE
area, the system automatically selects the corresponding NEs.
You can select the required operation and click OK.
Redo an upgrade task for Right-click a failed upgrade task in Task List, and select Redo
the failed NE Failed NE from the shortcut menu. The system performs the
upgrade task for the failed NE.
Redo a task Right-click a task in Task List, and select Redo from the shortcut
menu. The system performs the task again.
Stop a running task Right-click a running upgrade task in Task List, and select Stop
from the shortcut menu. A dialog box is displayed, indicating
whether to stop the running operation. Click Yes.
Note: You can only stop an upgrade task that is waiting for
upgrade, but the ongoing upgrade task cannot be stopped.
Detailed instruction is displayed in the message box.
Delete an executed task Right-click an upgrade task in Task List, and select Delete from
the shortcut menu. The task record is deleted from the task list.
2-10

Chapter 3
Common Operations
Table of Contents
Exporting and Importing NE Status Information ..........................................................3-1
Querying an NE Version Package ..............................................................................3-3
Creating a Deactivation Task ......................................................................................3-5
Creating a Package Deletion Task..............................................................................3-7
Creating a Rollback Task............................................................................................3-9
Creating a Special Firmware Pre-activate Task ........................................................3-11
Creating a Repository File Task ................................................................................3-13
3.1 Exporting and Importing NE Status Information

This procedure describes how to export and import NE status information for upgrade task
management. If multiple NEs need to be selected, you can export the NE selection status
to an Excel file, and then edit and save the NE selection status. The Excel file can be
imported when necessary, so the version upgrade and query operations can be performed
on the selected NEs in batches.
Steps
2. Select the Upgrade Task Management node, and click the (Create Upgrade Task)
icon on the right toolbar. The Create Upgrade Task dialog box is displayed.
3. In the Select NE area, click the (Selector) button, a submenu is displayed, providing
the Import Selected TreeNode and Export Selected TreeNode functions, see Figure
3-1.
3-1

Figure 3-1 Submenu of the Selector Button
4. Select Export Selected TreeNode to export the NE list and NE selection status
information to an Excel file. The default Excel format is “Export+Time”, for example,
Export_2013-08-29 14.41.25.xls.
5. Open the exported Excel file, and modify the corresponding value in the Select
NE(Y)/Deselect NE(N) column of the NE. If the value in the Select NE(Y)/Deselect
NE(N) column is Y, the corresponding NE node is selected in the Select NE area
after the Excel file is imported to the system. For the Excel file, see Figure 3-2.
Figure 3-2 Exported Excel File
Note:
l The NE sequences in the Excel file can be modified, which does not affect the
selection status of imported NEs.
l The NE nodes manually added to the Excel file cannot be imported.
3-2

Chapter 3 Common Operations
6. In the Select NE area, click the (Selector) button and select Import Selected
TreeNode from the submenu to import the NE list and NE selection status information.
The NE selection status is updated in the Select NE area in accordance with the
imported Excel file.
3.2 Querying an NE Version Package

This procedure describes how to query the details of a version package on an NE. This
operation helps you check the version package before or after performing the Apply
activation operation.
Steps
2. Select the Query Task Management node, and click the (Create Version Query
Task) icon on the right toolbar. The Create Version Query Task dialog box is
3-3

Figure 3-3 Create Version Query Task Dialog Box
3. Enter a name in the Task name text box. The task name is the current time by default.
The task name is set to the current time by default. When the task is created, the task
name is displayed and the querying operation information is added in Task List. By
default, the task name is in the format of “Query + creation time”. If the task name is
customized, it is in the format of “Query + entered task name”.
4. In the Select NE area, select the NE that requires version query.
Note:
If multiple NEs need to be selected, you can import NE selection status information
through an Excel file. For the operation descriptions, refer to 3.1 Exporting and
Importing NE Status Information.
3-4

6. Click OK to create the query task.

The successfully created query task is displayed in Task List, and the query progress
is displayed in the Progress column. The task execution results are displayed on the
Package Query Result, Package Status, and Board Running Version tabs.
icon on the toolbar to save the records in the task list as an HTML or XML file.
8. (Optional) Right-click a task in Task List. The shortcut menu that consists of Redo,
Redo Failed NE, Stop, and Delete is displayed. You can select an option as required.
3.3 Creating a Deactivation Task

This procedure describes how to create a deactivation task to change the status of a
version package from active status to standby status. If the pre-activated package has
problems, you must change the package status from active to standby through this
operation before deleting the package.
Prerequisite
l The version package is downloaded and pre-activated.
l An NE version package query task has been created.
Steps
1. Open the Create Deactivate Task dialog box.
a. On the Software Version Management tab, expand the Software Version
b. Select the Query Task Management node.
c. In the Task List area, select an NE version package query record.
d. Select the Package Status tab, and then right-click a record in active status and
select Create Deactivate Task from the shortcut menu. The Create Deactivate
Task dialog box is displayed, see Figure 3-4.
3-5

Figure 3-4 Create Deactivate Task Dialog Box
When the task is created, the task name is displayed and the deactivation operation
information is added in Task List on the Special Task Management page. By default,
the task name is in the format of “Deactivate + creation time”. If the task name is
customized, it is in the format of “Deactivate + entered task name”.
3. In the Select NE area, select the NE that contains the version package to be
deactivated.
Note:
4. (Optional) In the Select version package area, select the Select version package
option , and then select the version package to be deactivated.
Note:
l Firmware or hotfix version package does not support the deactivate operation.
l If no version package is selected, this task deactivates all activated version
packages.
3-6


7. Enter the verification code, and then click OK to create the deactivation task.
The successfully created deactivation task is displayed in Task List on the Special
Task Management tab, and the deactivation progress is displayed in the Progress
column. The task execution result is displayed in the Result Information list.
3.4 Creating a Package Deletion Task

This procedure describes how to delete a version package in standby status on an NE.
Prerequisite
1. A firmware package, a version package in standby status, or a hotfix exists on the NE.
2. An NE version package query task has been created.
Steps
1. Open the Create Delete Package Task dialog box.
a. On the Software Version Management tab, expand the Software Version
b. Select the Query Task Management node.
c. In the Task List area, select an NE version package query record.

d. Select the Package Status tab, and then right-click a record and select Create
Delete Package Task from the shortcut menu. The Create Delete Package Task
dialog box is displayed, see Figure 3-5.
3-7

Figure 3-5 Create Delete Package Task Dialog Box
2. Enter a name in the Task name text box. The task name is the current time by
default. When the task is created, the task name is displayed and the deletion
operation information is added in Task List on the Special Task Management page.
By default, the task name is in the format of “Delete + creation time”. If the task name
is customized, it is in the format of “Delete + entered task name”.
3. In the Select NE area, select the NE whose version package is to be deleted.
Note:
4. In the Select version package area, select the version package to be deleted.

6. Click OK, the Confirm dialog box is displayed.
7. Enter the verification code , and then click OK to create the package deletion task.
The successfully created package deletion task is displayed in Task List on the
Special Task Management tab, and the deletion progress is displayed in the
Progress column. The task execution results are displayed in the Result Information
list.
3-8

3.5 Creating a Rollback Task

This procedure describes how to roll back the version package running on an NE to the
version before upgrade.
Prerequisite
The NE has been upgraded.
Steps
2. Select the Special Task Management node, and click the (Create Roll Back
Package Task) icon on the right toolbar. The Create Roll Back Package Task dialog
box is displayed, see Figure 3-6.
3-9

Figure 3-6 Create Roll Back Package Task Dialog Box
When the task is created, the task name is displayed and the roll back operation
the task name is in the format of “Roll back+ creation time”. If the task name is
customized, it is in the format of “Roll back + entered task name”.
4. In the Select NE area, select the NEs to be rolled back.
Note:
3-10


7. Enter the verification code, and then click OK to create a rollback task.
The successfully created rollback task is displayed in Task List, and the progress is
displayed in the Progress column. The task execution results are displayed on the
Result Information tab.
3.6 Creating a Special Firmware Pre-activate Task

The pre-activation of board firmware is convenient for users to select or upgrade boards.
It also improves flexibility and accuracy of board operations.
Steps
2. Select the Special Task Management node, and click the (Create Special
Firmware Pre-activate Task) icon on the right toolbar. The Create Special Firmware
Pre-activate Task dialog box is displayed, see Figure 3-7.
3-11

Figure 3-7 Create Special Firmware Pre-activate Task Dialog Box
the task name is in the format of “Firmware Pre-activate+ creation time”. If the task
name is customized, it is in the format of “Firmware Pre-activate + entered task name”.
4. In the Select NE area, select the NEs to be firmware pre-activate.
Note:
5. In the Select version package area, select the version package.

8. Enter the verification code, and then click OK to create a firmware pre-activate task.
3-12

The successfully created firmware pre-activate task is displayed in Task List, and
the progress is displayed in the Progress column. The task execution results are
displayed on the Result Information tab.
3.7 Creating a Repository File Task

In case of dual-main control CC boards, if one CC board is faulty, there is no need to handle
it by visiting the station. You can reconnect the faulty CC board to the EMS by creating a
repository file.
Prerequisite
One of the dual-main control CC boards is connected to the EMS normally.
Steps
2. Select the Special Task Management node, and click the (Create Repository
File Task) icon on the right toolbar. The Create Repository File Task dialog box
is displayed, see Figure 3-8.
3-13

Figure 3-8 Create Repository File Task Dialog Box
the task name is in the format of “Repository File+ creation time”. If the task name is
customized, it is in the format of “Repository File + entered task name”.
4. In the Select NE area, select the NEs to be created repository file task.
Note:
5. In the Select version package area, select the version package.

6. (Optional) Click Browse in the Select certificate file area as required. The Open
dialog box is displayed, see Figure 3-9. Select a local certificate file, and then click
Open.
3-14

Figure 3-9 Open Dialog Box
Note:
l Only for the LTE standard, you should select certificates when creating a task.
l Both certificates should be selected.
8. Click OK to create a repository file task.

The successfully created firmware pre-activate task is displayed in Task List, and
the progress is displayed in the Progress column. The task execution results are
displayed on the Result Information tab.
3-15

3-16

Figures
Figure 1-1 Software Version Management Tab.......................................................... 1-1
Figure 2-1 Package Status Conversion Diagram....................................................... 2-1
Figure 2-2 Add Version Package Dialog Box............................................................. 2-3
Figure 2-3 Version Package List ............................................................................... 2-3
Figure 2-4 View Details Dialog Box ........................................................................... 2-4
Figure 2-5 Software Version Details of the Package.................................................. 2-6
Figure 2-6 Upgrade Task Management Window........................................................ 2-7
Figure 2-7 Create Upgrade Task Dialog Box ............................................................. 2-7
Figure 2-8 The Task List of Successfully Created Upgrade Tasks ............................. 2-9
Figure 3-1 Submenu of the Selector Button .............................................................. 3-2
Figure 3-2 Exported Excel File .................................................................................. 3-2
Figure 3-3 Create Version Query Task Dialog Box .................................................... 3-4
Figure 3-4 Create Deactivate Task Dialog Box .......................................................... 3-6
Figure 3-5 Create Delete Package Task Dialog Box.................................................. 3-8
Figure 3-6 Create Roll Back Package Task Dialog Box ........................................... 3-10
Figure 3-7 Create Special Firmware Pre-activate Task Dialog Box.......................... 3-12
Figure 3-8 Create Repository File Task Dialog Box ................................................. 3-14
Figure 3-9 Open Dialog Box.................................................................................... 3-15

Figures
II

Glossary
BBU
- Baseband Unit
BS
- Base Station
CDMA
- Code Division Multiple Access
EMS
- Element Management System
GSM
- Global System for Mobile Communications
OMM
- Operation & Maintenance Module
RRU
- Remote Radio Unit
UMTS
- Universal Mobile Telecommunication System
III

SJ-20130704144811-005-ZXSDR OMMB (V12.13.30) Version Management Operation Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SJ-20130704144811-005-ZXSDR OMMB (V12.13.30) Version Management Operation Guide

Uploaded by

Copyright:

Available Formats

ZXSDR OMMB

Version Management Operation Guide

Revision No. Revision Date Revision Reason

R1.0 2013–08–30 First Edition

Serial Number: SJ-20130704144811-005

Publishing Date: 2013-08-30 (R1.0)

SJ-20130704144811-005|2013-08-30 (R1.0) ZTE Proprietary and Confidential

Chapter 3 Common Operations ................................................................ 3-1

SJ-20130704144811-005|2013-08-30 (R1.0) ZTE Proprietary and Confidential

SJ-20130704144811-005|2013-08-30 (R1.0) ZTE Proprietary and Confidential

Prerequisite Skills and Knowledge

What Is in This Manual

2, BS Version Upgrade Describes how to upgrade the BS version.

3, Common Operations Describes the common operations for version management.

Note: provides additional information about a certain topic.

SJ-20130704144811-005|2013-08-30 (R1.0) ZTE Proprietary and Confidential

SJ-20130704144811-005|2013-08-30 (R1.0) ZTE Proprietary and Confidential

l Manage the version library.

Software Version Management Tab

3. Right-click the NE agent and select NE Management > Software Version

Figure 1-1 Software Version Management Tab

SJ-20130704144811-005|2013-08-30 (R1.0) ZTE Proprietary and Confidential

SJ-20130704144811-005|2013-08-30 (R1.0) ZTE Proprietary and Confidential

SJ-20130704144811-005|2013-08-30 (R1.0) ZTE Proprietary and Confidential

This page intentionally left blank.

SJ-20130704144811-005|2013-08-30 (R1.0) ZTE Proprietary and Confidential

Figure 2-1 Package Status Conversion Diagram

SJ-20130704144811-005|2013-08-30 (R1.0) ZTE Proprietary and Confidential

2.1 Upgrade Preparation

2.2 Adding a Version Package

SJ-20130704144811-005|2013-08-30 (R1.0) ZTE Proprietary and Confidential

Figure 2-2 Add Version Package Dialog Box

Figure 2-3 Version Package List

SJ-20130704144811-005|2013-08-30 (R1.0) ZTE Proprietary and Confidential

2.3 Viewing a Version Package

Figure 2-4 View Details Dialog Box

Table 2-1 Version Package Parameter Descriptions

Version Package Package file name with the .pkg suffix.

SJ-20130704144811-005|2013-08-30 (R1.0) ZTE Proprietary and Confidential

Version Package Standard There are two standards of version packages:

Version Package version number.

Father Version Version number of the parent package of the patch

Created Time Package creation time.

NE Type NE types to which the version package is applicable.

SJ-20130704144811-005|2013-08-30 (R1.0) ZTE Proprietary and Confidential

Figure 2-5 Software Version Details of the Package

4. (Optional) Delete a version package in the version library.

2.4 Creating an Upgrade Task

SJ-20130704144811-005|2013-08-30 (R1.0) ZTE Proprietary and Confidential

Figure 2-6 Upgrade Task Management Window

Figure 2-7 Create Upgrade Task Dialog Box

SJ-20130704144811-005|2013-08-30 (R1.0) ZTE Proprietary and Confidential

5. In the Select NE area, select the NE that requires version upgrade.

Table 2-2 Parameter Descriptions for Version Upgrade Operations

Download Downloads the selected version package to the

Pre-activate Sets the status of the selected version package from

Query version Queries the package version running on the NE.

SJ-20130704144811-005|2013-08-30 (R1.0) ZTE Proprietary and Confidential

Check configuration data Check whether the version of preupgrade configuration

8. Select a board standard in the Board standard settings drop-down list.

Figure 2-8 The Task List of Successfully Created Upgrade Tasks

SJ-20130704144811-005|2013-08-30 (R1.0) ZTE Proprietary and Confidential

Table 2-3 Operations Related to Upgrade Task Creation

SJ-20130704144811-005|2013-08-30 (R1.0) ZTE Proprietary and Confidential