Académique Documents
Professionnel Documents
Culture Documents
Issue 01
Date 2016-01-30
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees
or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: support@huawei.com
Preface
Purpose
This document describes how to upgrade a base station to V100R010C10SPC255 and how to
roll back the upgrade using the U2000 SME. It also provides FAQs and troubleshooting
methods.
Intended Audience
This document is intended for upgrade operators. Upgrade personnel must:
Be familiar with the product network and related NEs' versions.
Have device maintenance experience and be familiar with device operation and
maintenance methods.
Symbol Conventions
The symbols that may be found in this document are defined in the following table.
Symbol Description
Change History
Issue Date Description
Owners
Contents
Preface................................................................................................................................................ii
1 Before You Start.............................................................................................................................1
1.1 Getting Started................................................................................................................................................................1
1.2 Version Requirements.....................................................................................................................................................1
1.2.1 Requirements for Base Station Software Versions......................................................................................................1
1.2.2 Requirements for Software Versions of Other NEs.....................................................................................................4
1.3 Impact on the System During the Upgrade....................................................................................................................4
1.4 Upgrade Policies.............................................................................................................................................................4
1.4.1 Time Required for Each Task......................................................................................................................................4
1.4.2 Specifications for a U2000 SME-based Upgrade........................................................................................................6
1.5 Upgrade Precautions.......................................................................................................................................................6
7 FAQs...............................................................................................................................................80
7.1 How Do I Switch the Display Styles of the U2000 Client?.........................................................................................80
7.1.1 Switching from Application Style to Traditional Style.............................................................................................80
7.1.2 Switching from Traditional Style to Application Style.............................................................................................81
A Upgrade Record........................................................................................................................109
B Acronyms and Abbreviations.................................................................................................114
Table 1.1 Version requirements for upgrading an LTE FDD base station
Source Version Upgrade Note
Table 1.2 describes the version requirements for upgrading an LTE TDD single-mode base
station.
Table 1.2 Version requirements for upgrading an LTE TDD base station
Source Version Upgrade Note
V100R010C10SPC255.
The following time requirements are obtained based on upgrading base stations whose CPU is idle,
transmission networking is IP networking, and OM bandwidth is 1024 kbit/s. The time is for reference
only.
Do not activate the NE backup function or NE log synchronization task plan when
downloading or activating software on the U2000. Otherwise, the concurrent download and
activation processing capabilities of the U2000 are affected. For details about how to check
whether ongoing NE backup tasks or NE log synchronization tasks are in progress on the
U2000, see 7.2How Do I Query NE Backup Tasks? and 7.3How Do I Query NE Log
Synchronization Tasks?
If the preceding operations are performed unexpectedly, the base station is restored to the original
version after being restarted. When this happens, perform the upgrade again.
− If the link between a base station and the U2000 is disconnected during the upgrade
of a multimode base station, contact Huawei technical support for a new upgrade
policy. If a forced upgrade is required for the base station despite the disconnect,
perform a forced upgrade by referring to 7.5How Do I Enable the Forced Upgrade
Function for a Multimode Base Station?
Strictly follow the upgrade flowchart shown in Figure 1.2 in order to upgrade base stations.
To perform a successful base station upgrade, you need to make certain preparations.
Pre-upgrade preparations involve preparing upgrade materials, checking the upgrade
environment information, and preparing the upgrade environment. Each of these items
consists of several tasks, which are listed in Table 2.1.
Make sure that the expected results described in Table 2.1 have been obtained before
performing the base station upgrade.
Upgrade period
Base station type and quantity
Location of the base stations
For details about how to query base station types, see 7.18How Do I Query the Type of a Base Station to
Be Upgraded?
If the language of the displayed window is not in the target language, select the target language in the
upper plane.
Method 2:
Log in to http://support.huawei.com using a Huawei engineer's account and then search
for BTS3900 on the Software tab page. Click the association result. In the displayed web
page, select the target version.
Step 2 On the Software tab page, find and click the target upgrade software package to download it.
Select an appropriate upgrade software package based on the source version and mode of the base
station. For details, see 7.19How Do I Select and Use Upgrade Software Packages?
Step 4 Create a folder on the PC where the U2000 client is installed, for example, D:\FTP. Save the
upgrade risk check package and upgrade software package to the folder.
----End
Step 1 Log in to the U2000 client and click . On the displayed Application Center tab page,
double-click Software Management.
The Software Management Expert window is displayed.
Choose Software > Software Management Expert to open the Software Management Expert
window on the U2000 in traditional style.
Step 2 In the displayed Software Management Expert window, click Create Project. Check
whether the Create Project dialog box is displayed.
If the dialog box is displayed, the current account has permissions to perform the upgrade.
If the dialog box is not displayed, contact the security administrator to obtain the permissions.
----End
The descriptions in this section apply to NodeBs, eNodeBs, and BTS3900s. Skip this section if the
NEs to be upgraded are of other types.
The following steps use an eNodeB as an example to describe how to check the file server settings.
The operations for checking the file server settings for other NE types are similar.
For details about the definition, functions, and settings of the file server, see section 7.7What Is the
Function of the File Server?
Step 1 Log in to the U2000 client and click . On the displayed Application Center tab page,
double-click Configuration.
Step 2 From the main menu of the U2000, choose Settings > File Server Settings.
The File Server Settings dialog box is displayed.
Choose Software > File Server Settings to open the File Server Settings dialog box on the U2000 in
traditional style.
Step 3 In the displayed File Server Settings dialog box, choose NE > eNodeB and choose the NE to
be upgraded under the file server node, as shown in Figure 3.1.
If the base station to be upgraded works in UMTS mode, click NodeB in the navigation tree. If the base
station to be upgraded is a co-MPT base station, click BTS3900.
Step 4 Check whether the file server settings of all the base stations displayed on the right-hand pane
are correct.
If the file server settings of all the base stations are correct, the check is complete.
If the file server settings of any base station are incorrect, go to Step 5.
If the file server settings of too many NEs are listed, you can search by NE name to view the information
about a specific NE.
Step 5 In case of incorrect settings, right-click the related base station and choose Set from the
shortcut menu. The Set File Server for Batch NE(s) dialog box is displayed, as shown in
Figure 5.1.
If several file servers are set incorrectly, select multiple base stations that share the same file server
while holding down Ctrl or Shift, right-click these base stations, and then choose Set from the shortcut
menu.
Step 6 Double-click the box under Value, choose a server name from the drop-down list, and then
click OK.
Step 7 Click Apply to make the settings take effect.
----End
The descriptions in this section apply to NodeBs, eNodeBs, and BTS3900s. Skip this section if the
NEs to be upgraded are of other types.
The following steps use an eNodeB as an example to describe how to check the U2000 mediation
software. The operations for checking the U2000 mediation software for other NE types are similar.
Before an upgrade, the U2000 mediation software versions installed on the U2000 must
match the target versions of the NEs to be upgraded. If they do not match, the upgrade will
fail. This section describes how to check whether the required U2000 mediation software
version has been installed.
Step 1 Log in to the U2000 client and click . On the displayed Application Center tab page,
double-click Software Management.
Step 2 From the main menu of the U2000 client, choose NE File > Software Browser.
The Software Browser window is displayed.
Choose Software > Software Browser to open the Software Browser window on the U2000 in
traditional style.
Step 3 On the OSS Server tab page, choose Server > OSS > Mediation > BTS3900 LTE from the
navigation tree. Check the installed U2000 mediation versions under the Mediation Version
column, as shown in Figure 3.1.
If the base station to be upgraded works in UMTS mode, click BTS3900 WCDMA in the navigation
tree. If the base station to be upgraded is a co-MPT base station, click BTS3900.
Step 4 Check whether the U2000 mediation software version listed in the "Software Version
Compatibility" section of BTS3900 V100R010C10SPC255 (eNodeB) Release Notes can be
found in the query result of Step 3.
If the U2000 mediation software version can be found, the check is complete.
If the U2000 mediation software version cannot be found, go to Step 5.
Step 5 Obtain the required U2000 mediation software by referring to 3.1.3Obtaining Upgrade
Reference Documents and Software Packages and install it.
Step 6 After the installation is complete, repeat Step 1 through Step 4 to check the U2000 mediation
version again to ensure that it has been successfully installed.
----End
Step 1 Log in to the U2000 client and click . On the displayed Application Center tab page,
double-click Configuration.
Step 2 From the main menu of the U2000, choose Settings > MBTS Management > MBTS
Relationship Management.
Choose Configuration > MBTS Management > MBTS Relationship Management to open the
MBTS Relationship Management window on the U2000 in traditional style.
Step 3 On the displayed Check Correlations tab page, click and choose Check By MBTS
from the displayed menu.
Step 4 In the displayed Check By MBTS dialog box, select NEs to be checked, as shown in Error:
Reference source not found.
If the maintenance mode of the NE is changed before the upgrade, restore the maintenance
mode after the upgrade.
Step 1 Log in to the U2000 client and click . On the displayed Application Center tab page,
double-click Configuration. From the main menu of the U2000 client, choose Settings >
Maintenance Mode.
Choose Maintenance > Maintenance Mode to open the Maintenance Mode tab page on the U2000 in
traditional style.
Step 2 Click Query Maintenance Mode, as shown in Figure 2.1. In the displayed Query
Maintenance Mode dialog box, select the NE to be queried, and then click OK.
Step 3 In the displayed result, check whether the value of Current NE Maintenance Mode is
INSTALL or TESTING.
If the value is neither INSTALL nor TESTING, the maintenance mode is normal.
If the value is INSTALL or TESTING, the maintenance mode is abnormal. You can
modify the maintenance mode by performing the operations described in Changing the
Maintenance Mode.
Step 4 If the maintenance mode is abnormal, click to export the maintenance mode so that you
can restore the maintenance mode after the upgrade, as shown in Error: Reference source not
found.
----End
Step 1 Click . On the displayed Application Center tab page, double-click Configuration.
From the main menu of the U2000 client, choose Settings > Maintenance Mode.
Choose Maintenance > Maintenance Mode to open the Maintenance Mode tab page on the U2000 in
traditional style.
Step 2 Click Set Maintenance Mode, as shown in Figure 2.1. In the displayed Set Maintenance
Mode dialog box, select the NE whose maintenance mode needs to be configured, set NE
maintenance mode to NORMAL, and click OK, as shown in Figure 2.2.
To prevent alarms from being reported during the upgrade, you can set NE maintenance mode to
UPGRADE before performing the upgrade.
Step 3 Check the setting progress. When the progress reaches 100%, the maintenance mode is
successfully set.
After the upgrade, you can perform the preceding steps to restore the NE maintenance mode.
----End
3.2.6 Checking Whether the U2000 Has the Software That the Base
Station Currently Runs
To ensure that version rollback can be performed immediately if the upgrade fails, the U2000
must have the software that the base station currently runs. To check whether the U2000 has
the software that the base station currently runs, perform the following steps:
Step 1 Log in to the U2000 client and click . On the displayed Application Center tab page,
double-click Software Management.
Step 2 From the main menu of the U2000 client, choose NE File > Software Browser.
The Software Browser window is displayed.
Choose Software > Software Browser to open the Software Browser window on the U2000 in
traditional style.
Step 3 On the displayed Software Browser tab page, click the OSS Server tab. In the navigation
tree of the displayed OSS Server tab page, click the type of the base station to be upgraded,
as shown in Figure 3.1. Versions displayed on the Software tab page on the right-hand pane
indicate the software versions on the U2000.
Step 4 Check whether the version of the software that the base station currently runs is displayed on
the Software tab page.
If the version is displayed, the check is complete.
If the version is not displayed, go to Step 5.
Step 5 Download the required software by referring to 3.1.3Obtaining Upgrade Reference
Documents and Software Packages and upload it to the U2000 server by referring to
3.3.7(Optional) Uploading the Software Package and Upgrade Risk Check Package to the
U2000 Server.
Step 6 Repeat Step 1 through Step 4 to ensure that the software that the base station currently runs
has been successfully uploaded to the U2000 server.
----End
For details about how to save KPI reports on the U2000, see U2000 online help by performing the
following steps:
1. On the U2000, press F1.
The U2000 Online Help window is displayed.
2. Choose Performance Management > Performance Measurement Management > Performance
Management During Routine Maintenance > Exporting NE Performance Measurement
Results. Then, save the NE performance measurement results.
Refer to this section when the base station to be upgraded is a NodeB, eNodeB, or BTS3900.
After the upgrade, a new license may be required because new features are introduced or
constraints are imposed on existing features. If the license is not upgraded, services may be
affected after the upgrade. Check whether a new license is required before the upgrade.
Check whether you need to apply for a license based on the NE type, as listed in Table 1.1.
The NodeB is using a temporary or Check the expiration date of the license.
commissioning license If the license has expired, you need to apply
for a new license.
If the license has not expired, you do not
need to apply for a new license.
The NodeB is using a commercial license or See Table 1.3 for license suggestions.
an unexpired temporary license
New features are used after the upgrade Apply for a license before the upgrade.
The upgrade is not a cross-R-version upgrade Do not apply for a license.
and no new features are used
The upgrade is a cross-R-version upgrade and You are advised to apply for a license.
no new features are used Use the original license if you do not
apply for a new one.
The eNodeB is using a commissioning, Check the expiration date of the license.
fixed-term, or temporary commercial license If the license has expired, you need to apply
for a new license.
If the license has not expired, see Table 1.5.
The eNodeB is using a commercial license See Table 1.5.
Table 1.5 Suggestions about whether to apply a new license for an eNodeB
If... Then...
New features are used after the Apply for a new license.
upgrade
The upgrade is a cross-R- Apply for a new license.
version upgrade
If... Then...
License status synchronization aims at synchronizing the ESNs of base stations to the U2000. The ESN
of a base station uniquely identifies the base station. After the synchronization is complete, the U2000
can load license files to corresponding base stations based on ESNs when loading license files in
batches. Therefore, license status needs to be synchronized before license file loading.
This section applies only to LTE-only base stations and multimode base stations.
Step 1 Log in to the U2000 client and click . On the displayed Application Center tab page,
double-click Software Management.
Step 2 From the main menu of the U2000 client, choose NE License > Stand-Alone.
The Filter dialog box is displayed when the Stand-Alone License Management tab page is opened for
the first time, as shown in Error: Reference source not found. You can click OK to continue.
Choose License > NE License Management > Stand-Alone to open the Stand-Alone window on the
U2000 in traditional style.
Step 6 In the Stand-Alone License Management window, click on the left of the number under
Task ID. The license synchronization progress is displayed under Execution Status, as
shown in Figure 6.1.
To query the license status, choose License Information Query from the Stand-Alone License
Management navigation tree, and click Refresh in the lower right-hand corner. The eNodeB
information is displayed in the right-hand pane.
----End
Determine whether to reload a license file by referring to 3.3.2.2 Checking Whether You Need
to Apply for an eNodeB License. If a license file needs to be reloaded, pre-check the license
status of eNodeBs by performing the following steps:
Step 1 Log in to the U2000 client and click . On the displayed Application Center tab page,
double-click Software Management.
Step 2 From the main menu of the U2000 client, choose NE License > Stand-Alone. The Stand-
Alone License Management window is displayed.
The Filter dialog box is displayed when the Stand-Alone License Management tab page is opened for
the first time, as shown in Figure 2.1. You can click OK to continue.
Choose License > NE License Management > Stand-Alone to open the Stand-Alone window on the
U2000 in traditional style.
Step 3 In the Stand-Alone License Management window, click NE License Maintenance in the
navigation tree.
Step 4 Click NE License Management Operation in the bottom part of the window, and then click
Check License. The Check License dialog box is displayed.
Step 5 In the Check License dialog box, click the Check license option, and click Next, as shown in
Figure 5.1.
Step 6 Click below New license file. In the displayed Open dialog box, select a new license file,
click Open, and then click Next in the Check License dialog box.
Step 7 Click Select in the Check License dialog box. In the displayed Select NE dialog box, select
eNodeBs whose license files need to be pre-checked in the Available Devices area, click
to add the eNodeBs to the Selected Devices area, and then click OK.
If the new license file is in .xml format, perform step 7. If the new license file is in .zip format, the target
NE is selected in the Check License dialog box by default, skip step 7 and go to step 8.
Step 8 In the Check License dialog box, click Next. On the displayed Select Export Path page,
click below Export path. In the displayed Save dialog box, specify the save path and
format for the exported information, and then click Save. Click Finish on the Select Export
Path page.
Step 9 In the Stand-Alone License Management window, check the pre-check progress. When
100% is displayed in the Execution Status column, the Information dialog box is displayed.
Click the license file name displayed in the File Name column to open the license file and
view the pre-check result.
If Match is displayed in the Verification Result column in the license file, the pre-check
is successful.
If information other than Match is displayed in the Verification Result column, apply
for another license file based on information in the Detailed Error Description column
in the opened license file, and perform the pre-check on the new license file again.
----End
3.3.5.1 Backing Up the License File for the eNodeB of SRAN8.1 or a Later
Version
To back up the license file for the eNodeB of SRAN8.1 or a later version, perform the
following steps:
Step 1 Log in to the U2000 client and click . On the displayed Application Center tab page,
double-click Software Management.
Step 2 From the main menu of the U2000 client, choose NE License > Stand-Alone.
The Filter dialog box is displayed when the Stand-Alone License Management tab page is opened for
the first time, as shown in Figure 2.1. You can click OK to continue.
Choose License > NE License Management > Stand-Alone to open the Stand-Alone License
Management window on the U2000 in the traditional style.
Step 3 In the navigation tree, choose Stand-Alone License Management > NE License
Maintenance. Click Back Up License File in the lower right-hand pane, as shown in Figure
3.1.
Step 4 In the Back Up License File dialog box, click Select. The Select NE dialog box is displayed.
Step 5 In the Select NE dialog box, select an eNodeB whose license is to be backed up in the
Available Devices area.
The eNodeBs are displayed in the Selected Devices area.
Step 6 Click OK in the lower right-hand corner to return to the Back Up License File dialog box.
Step 7 Click OK to start the license file backup.
Step 8 View the license loading progress under Execution Status in the displayed window.
If Execution succeeded is displayed under Execution Status, the license file has been
successfully backed up.
----End
3.3.5.2 Backing Up the License File for the eNodeB of SRAN8.0 or an Earlier
Version
To back up the license file for the eNodeB of SRAN80 or an earlier version, perform the
following steps:
Step 1 Log in to the U2000 client and click . On the displayed Application Center tab page,
double-click Trace and Maintenance.
Step 2 From the main menu of the U2000 client, choose Maintenance > MML Command.
Choose Maintenance > MML Command to open the MML Command window on the U2000 in
traditional style.
Step 3 Choose NE from the navigation tree on the left-hand side, and select an NE from the NE list.
Step 4 Run the LST LICENSE command to query the activated license file of the eNodeB and
obtain the name of the license file in use.
Step 5 Run the ULD LICENSE command to upload the license file.
----End
You need to install the CME only when the base station to be upgraded is a NodeB, eNodeB, or
BTS3900 and the CME needs to be used after the upgrade.
Choose a CME version plus components that can work with base stations after the upgrade by
referring to the following documents and contact the U2000 maintenance engineers to install
the CME:
BTS3900 V100R010C10SPC255 (NodeB) Release Notes
BTS3900 V100R010C10SPC255 (eNodeB, FDD) Release Notes
BTS3900 V100R010C10SPC255 (eNodeB, TDD) Release Notes
BTS3900 V100R010C10SPC255 (Multimode Base Station) Release Notes
BTS3900 V100R010C10SPC255 (Co-MPT) Release Notes
CME Version CME Component How to Obtain and Install the CME
Package Component Package
CME Version CME Component How to Obtain and Install the CME
Package Component Package
of V200R015C10SPCXXX (basic
version) instead.
Read this section if you want to upload the upgrade software package or upgrade risk check package to
the U2000 server before performing the upgrade.
Skip this section and move on to "4Performing the Upgrade" if you want to upload the upgrade software
package and upgrade risk check package while creating an upgrade task.
After obtaining the upgrade software package and upgrade risk check package, you need to
upload them to the U2000 server before performing the upgrade. This section describes how
to upload the upgrade software package and upgrade risk check package to the U2000 server.
Step 2 Log in to the U2000 client and click . On the displayed Application Center tab page,
double-click Software Management.
Step 3 From the main menu of the U2000, choose NE File > NE File Transfer.
The NE File Transfer dialog box is displayed.
Choose Software > NE File Transfer to open the NE File Transfer dialog box on the U2000 in
traditional style.
Step 4 In the NE File Transfer dialog box shown in Figure 4.1, set the parameters as follows:
Select From OSS Client to OSS Server from the Direction drop-down list.
Select an NE type from the NE Type drop-down list based on the type of NEs to be
upgraded.
Select Software from the File Type drop-down list.
If the message "An error occurs when uploading files" is displayed in the Message dialog box, prepare
the upgrade software package by referring to 7.8How Do I Prepare the Upgrade Software Package? and
upload the package again.
If a message indicating that the version already exists is displayed on the U2000, replace the original
software package with the new one by referring to 7.19How Do I Select and Use Upgrade Software
Packages?
----End
Step 2 Log in to the U2000 client and click . On the displayed Application Center tab page,
double-click Software Management.
Step 3 From the main menu of the U2000, choose NE File > NE File Transfer.
The NE File Transfer dialog box is displayed.
Choose Software > NE File Transfer to open the NE File Transfer dialog box on the U2000 in
traditional style.
Step 4 In the NE File Transfer dialog box shown in Figure 4.1, set the parameters as follows:
Select From OSS Client to OSS Server from the Direction drop-down list.
Select an NE type from the NE Type drop-down list based on the type of NEs to be
upgraded.
Select Upgrade Risk Check Package from the File Type drop-down list.
Refer to this section when the base station to be upgraded is a NodeB, eNodeB, or BTS3900.
To eliminate impacts of the upgrade on the network, the U2000 automatically supplements the
base stations with LMT files four hours after the upgrade. If you need to use the LMT
immediately after the upgrade, perform the steps described in this section so that the base
station downloads the upgrade software package together with LMT files from the U2000
during the upgrade.
Downloading LMT files together with the upgrade software package from the U2000 will prolong the
download duration.
To allow the base station to download LMT files together with the upgrade software package,
perform the following steps:
Step 1 Log in to the U2000 client and choose File > Preferences from the main menu. The
Preferences dialog box is displayed.
Choose System > Preferences to open the Preferences window on the U2000 in traditional style.
Step 2 In the left-hand navigation tree, click SWM Preferences. Select Download the Web LMT
immediately on the right-hand pane, as shown in 3.3.8(Optional) Setting Immediate
Download of LMT Files. Then, click OK.
----End
This chapter describes the procedure for upgrading base stations. Strictly follow the operation
guide during the upgrade.
Do not perform version rollback in an upgrade manner during an SME-based upgrade of any
base station except a GBTS.
You only need to set the basic information about an upgrade project and upload or select the related
software packages when creating an upgrade project. Therefore, this operation does not affect NE
operation.
Step 1 Log in to the U2000 client and click . On the displayed Application Center tab page,
double-click Software Management.
Choose Software > Software Management Expert to open the Software Management Expert
window on the U2000 in traditional style.
Step 2 On the displayed Software Management Expert tab page, click Create Project.
Each U2000 supports a maximum of 20 upgrade projects at a time, including running and
completed projects. If there are already 20 upgrade projects on the U2000, manually delete
completed or invalid tasks before creating new tasks.
Step 3 In the displayed Create Project dialog box, set the parameters, as shown in Figure 3.1.
After choosing Select From OSS Client, you can either upload compressed packages directly or upload
decompressed files. For compressed packages, you can decompress them by referring to 7.8How Do I
Prepare the Upgrade Software Package? and 7.9How Do I Prepare the Upgrade Risk Check Package?
For details, see 3.3.7(Optional) Uploading the Software Package and Upgrade Risk Check Package to
the U2000 Server.
− If the target upgrade software package and upgrade risk check package have been
uploaded, you can use the Select From OSS Server method:
f. Click Select From OSS Server.
The Select Target Version dialog box is displayed.
g. Select the target upgrade software package and upgrade risk check package and
click OK.
4. (Optional) In the Remarks area of the Create Project dialog box, enter the description
of the upgrade project. The description can be up to 255 characters long.
Step 4 Confirm the parameter settings. Then, click OK.
The system automatically displays the newly created upgrade project in the main window.
----End
upgrade of SRAN base stations. For details about how to plan multiple batches, see
section 4.2.2Planning an Upgrade Batch.
To modify the number of base stations to be upgraded in a created upgrade batch, perform the steps
described in 7.12How Do I Modify an Upgrade Batch?
Step 2 In the displayed Create Batch-[1/2] dialog box, create an upgrade batch and select the base
station controller or subnet under which the base stations to be upgraded are located, as shown
in Figure 2.1.
Type of NE to Be Configuration
Upgraded
GBTS Select the base station controller under which the base station is
located.
NodeB Select the base station controller under which the base station is
located.
eNodeB Select the subnet under which the base station is located.
Co-MPT base station Select the base station controller or subnet under which the base
station is located.
Separate-MPT Select required options for each mode of the multimode base
multimode base station station.
Figure 2.1 Selecting the base station controller or subnet under which the base stations to be
upgraded are located
Step 3 Click Next. In the Create Batch [2/2] dialog box, set Upgrade by to Base Station or NE, as
shown in Figure 4.1.
If the Query GBTS Version dialog box is displayed, click Skip if you do not need to query the current
GBTS version.
The upgrade method selection area is automatically hidden if no multimode base station needs to be
upgraded. There are two upgrade methods, by base station or by NE:
Base Station
The upgrade is performed on the U2000 according to physical base station types (including single-
mode base stations, co-MPT base stations, and separate-MPT base stations). For a multimode base
station, main control boards of different modes are upgraded simultaneously and therefore services
of different modes are interrupted simultaneously. This decreases the occurrence of service
interruptions and shortens the interruption duration.
NE
The upgrade is performed on the U2000 according to NEs (including single-mode base stations, co-
MPT base stations, and NEs of separate-MPT base stations). Each single-mode base station or co-
MPT base station is considered as one NE. One main control board for a separate-MPT base station
is considered as one NE, that is, the number of main control boards for a separate-MPT base station
equals the number of NEs. Services of different modes for a separate-MPT base station are
interrupted separately. In RRU sharing, common transmission, or common clock scenarios, when
one mode is upgraded, services in other modes are affected.
Step 4 Select the base stations or NEs to be upgraded, as shown in Figure 4.1.
You can select the check boxes on the right-hand side of Base Station Category or NE Category to
select all the base stations or NEs in the chosen modes.
You can select or deselect the check boxes on the left-hand side of the Base Station Name/NE
Name column to select or deselect the base stations one by one.
You can export the base stations listed in the table into an .xls file and then use the filtering and
sorting functions to facilitate choosing base stations or NEs to be upgraded. You can remove the base
stations or NEs that will not be upgraded and then import the .xls file.
Step 5 Click Finish. The main window of the newly created upgrade batch is displayed
automatically.
You can quickly select NEs and create a batch by importing an NE file exported from the existing batch.
For details, see 7.10How Do I Export a Batch?
----End
In the displayed dialog box, the number of base stations to be upgraded in a specific batch can be
calculated based on the base station controllers or subnets under which the base stations are located.
As shown in Figure 1.1, the G/U/L Base Station table contains GO, UO, GL, UL, GU, and GUL
base stations. The LO Base Station table contains all LO base stations. For example, "2" in the
green circle indicates that RNC_2 controls two UL base stations. "6" in the blue circle indicates that
GSM_2 controls six GL base stations. "50" in the red circle indicates that GSM_1 and RNC_1
together control 50 GU base stations or 50 GUL base stations.
Step 2 Click a button in the table to select the base stations to be upgraded.
An icon with a number will be displayed on the left-hand side of the button. The buttons
allocated to the same batch use the same icon, as shown in Figure 4.1.
If you select base stations by mistake by clicking a button in the table, you can click Cancel to deselect
the base stations.
You can modify base stations in a batch by selecting the batch from the batch list and then clicking
Modify.
You can select a batch from the batch list and then click Delete to delete the batch.
You can repeat Step 2 through Step 4 to plan another upgrade batch.
Step 5 After all batches are planned, click OK to create a batch upgrade task.
----End
Step 3 Specify the status of each preparation task based on the actual situation. Click Apply. When
Batch Status becomes Completed, the upgrade preparation confirmation is complete.
----End
The procedure for performing a full risk check is similar to that for performing a key risk
check. The only difference is the parameter settings in Step 3.
Before performing a key risk check, you must perform a full risk check and ensure that all
failed check items have been handled.
It is recommended that the NE upgrade can be performed after the full risk check and key
risk check have been finished.
Step 1 Click Pre-upgrade Check on the left-hand pane. Click Create to create a pre-upgrade check
task, as shown in Figure 1.1.
Step 2 Select the batch to be upgraded in the Pre-upgrade Check-[1/3] dialog box.
Step 3 Click Next.
In the Pre-upgrade Check-[2/3] dialog box, set parameters for the risk check based on actual
conditions. Default values are recommended.
Select Check All Risks when performing a full risk check.
Select Check Key Risks when performing a key risk check.
Step 4 Click Next. In the Pre-upgrade Check-[3/3] dialog box, confirm the pre-upgrade check task
parameters.
Step 5 Then, click Finish.
The Pre-upgrade Check tab page is displayed, and the status of the check progress is also
displayed. Click a check task to view the check status.
Table 1.1 describes the status of risk checks.
Full risk check Succeeded Indicates that the full risk check was successful.
Completed Indicates that alarms were reported. These alarms may
with warnings cause services to be abnormal but will not cause the
base station upgrade to fail or cause the base stations to
be disconnected from the U2000 after the upgrade. You
can handle these alarms according to the solutions in
the upgrade risk check report, which can be
downloaded by performing the steps provided in
7.17How Do I Handle Failed Items in an Upgrade Risk
Check?You may not handle these alarms if whether
services can be properly provided after the upgrade
does not need to be considered.
Failed Indicates that some items in the check failed. These
items will cause the base station upgrade to fail or cause
the base stations to be disconnected from the U2000
after the upgrade. You must rectify the faults before
proceeding with the upgrade.You can rectify the faults
as instructed in 7.17How Do I Handle Failed Items in
an Upgrade Risk Check?
Key risk check Succeeded Indicates that the key risk check was successful and the
NE can be upgraded.
Completed Indicates that alarms were reported. These alarms may
with warnings cause services to be abnormal but will not cause the
base station upgrade to fail or cause the base stations to
be disconnected from the U2000 after the upgrade. You
can handle these alarms according to the solutions in
the upgrade risk check report, which can be
downloaded by performing the steps provided in
7.17How Do I Handle Failed Items in an Upgrade Risk
Check?You may not handle these alarms if whether
services can be properly provided after the upgrade
does not need to be considered.
Failed Indicates that some items in the check failed. These
items will cause the base station upgrade to fail or cause
the base stations to be disconnected from the U2000
after the upgrade. You must rectify the faults before
proceeding with the upgrade.You can locate and rectify
the faults by referring to 7.17How Do I Handle Failed
Items in an Upgrade Risk Check?
To remove the NEs which have not passed the check, click Batch Management, right-click the NEs
that have failed in the check, and choose Delete NE.
If the status of a risk check is displayed as Failed, locate and rectify the faults. Then, right-click the
batch to be upgraded and choose Recheck Failed Batch from the shortcut menu.
For details about how to upgrade the BootROM software based on the risk check result, see section
7.11How Do I Upgrade the BootROM?
----End
Step 2 In the displayed Upgrade Execution-[1/3] dialog box, select the batch to be upgraded.
Click Next. In the displayed Upgrade Execution-[2/3] dialog box, set the parameters in the
Step Settings area shown in Figure 2.1, Figure 2.2, or Figure 2.3 by referring to the following
table.
Step 3 Click Next. In the Upgrade Execution-[3/3] dialog box, confirm the upgrade task
parameters, as shown in Figure 3.1.
To remove the NE that fails the loading, click Batch Management, select the NE, and choose
Delete NE from the shortcut menu.
If the message "The task of distributing software to the server [*.*.*.*] is running... Failed to
send files." is returned, handle this problem by referring to 7.15How Do I Handle a Failure in
Distributing the Upgrade Software Package from the Master U2000 to the Slave U2000?
----End
To activate the software for a specific NE, expand the batch, right-click the NE, and choose Manual
Execute from the shortcut menu.
When the progress reaches 100% and the status becomes Completed, the upgrade has been
successfully executed, as shown in Figure 1.2. At the same time, a message "Query result:
BTS3900 V100R010C10SPC255, which is consistent with that of the target upgrade version.
Upgrade successfully." is displayed in the right-hand pane of the Details area.
If the message "Failed to upgrade license" is displayed for the eNodeB upgrade task, right-click the
eNodeB to be upgraded and choose Skip from the shortcut menu. Then reload the license file by
following the steps in 4.7.1Reloading an eNodeB License File.
If software activation fails, see 7.14How Do I Handle a Base Station Software Activation
Failure?
Step 2 After the upgrade is completed, click the Project Browser tab on the Software Management
Expert tab page.
Step 3 On the displayed Project Browser tab page, right-click a completed upgrade task and choose
Finish from the shortcut menu.
----End
Services may not be properly provided if the required license file fails to be reloaded after the
upgrade.
The following uses the license file in .xml format for upgrading an eNodeB in SRAN9.0 as an
example. You can refer to the following method to reload the license files in .dat format
backed up on or applied for eNodeBs in other SRAN versions.
Step 1 Log in to the U2000 client and click . On the displayed Application Center tab page,
double-click Software Management.
Step 2 From the main menu of the U2000 client, choose NE License > Stand-Alone.
The Stand-Alone License Management window is displayed.
The Filter dialog box is displayed when the Stand-Alone License Management tab page is opened for
the first time, as shown in the displayed Stand-Alone License Management window. You can click OK
to continue.
Choose License > NE License Management > Stand-Alone to open the Stand-Alone License
Management window on the U2000 in traditional style.
Step 4 In the displayed Open dialog box, select XML files (*.xml) or ZIP files (*.zip) from the File
Type drop-down list. Select the file from the save path, and click Open.
Step 5 In the Load License File dialog box, click Next.
If the license file is in XML format, select XML files (*.xml) from the File Type drop-down list. If the
license file is in ZIP format, select ZIP files (*.zip) from the File Type drop-down list. Do not
decompress the license file in ZIP format before loading it.
Step 6 In the Load License File dialog box, perform the following operations:
If XML files (*.xml) is selected from the File Type drop-down list:
1. Click in the Load License File dialog box. The Select NE dialog box is
displayed.
2. Select the eNodeB to which the license file is to be loaded, and click OK to return to the
Load License File dialog box. Click Finish.
3. In the displayed Confirm dialog box, click Yes.
If ZIP files (*.zip) is selected from the File Type drop-down list:
License files and the NE names of all the eNodeBs are displayed in the Load License
File dialog box.
1. Right-click on one record and choose Select All.
2. Click Finish. In the displayed Confirm dialog box, click Yes.
Step 7 View the license loading progress under Execution Status in the displayed window. If
Execution succeeded is displayed under Execution Status, the license file has successfully
loaded.
If Minor error is displayed under Execution Status, right-click the record and choose Force from the
shortcut menu.
Step 8 (Optional) To query the license status, perform Step3 through Step6 in 3.3.3(Optional)
Synchronizing the License Status of the eNodeB.
If the status of a commercial license is Normal, the license has taken effect.
If the status of a commissioning license is Commissioning, the license has taken effect.
----End
Step 1 Log in to the U2000 client and click . On the displayed Application Center tab page,
double-click Software Management.
Step 2 From the main menu of the U2000 client, choose NE License > eGBTS/NodeB. The
eGBTS/NodeB License Management window is displayed.
Choose License > NE License Management > eGBTS/NodeB to open the eGBTS/NodeB License
Management window on the U2000 in traditional style.
Step 3 In the eGBTS/NodeB License Management window, perform the following operations:
1. In the NE navigation tree, select the base station controller under which the base stations
to be upgraded are located.
2. Compare the electronic serial number (ESN) displayed in the right-hand pane with that
in the license file.
If they are the same, right-click the base station controller under which the base stations to be
upgraded are located and choose Upload from the shortcut menu, as shown in Figure 3.1.
If they are different, the license file is incorrect. Apply for a new license file.
Step 4 In the displayed Confirm dialog box, click Yes. The license file upload is complete.
When the progress reaches 100%, the license has been successfully uploaded, as shown in
Figure 4.1.
If license control items of the eGBTS/NodeB do not need to be modified, the license file
loading is complete.
If license control items of the eGBTS/NodeB need to be modified, perform the following
operations:
h. Double-click the NE, as shown in Figure 4.2. On the displayed Modify dialog box,
modify the license control items, as shown in Figure 4.3. If the allocated values are
correct, you do not need to modify the settings.
Figure 4.2 Selecting the NE whose license controls items are to be modified
j. Right-click the uploaded license file and choose Distribute from the shortcut menu
to distribute the license, as shown in Figure 4.4.
For an eGBTS, right-click the eGBTS and choose Allocating Remaining Resources to BSC
from the shortcut menu.
When the progress reaches 100%, the license has been successfully allocated. See Figure 4.5
to check license details.
If a license control item is added to the target version, its initial value is Not Set. However, such a
license control item is not allowed to be allocated to an NE, as shown in Figure 4.6. Therefore, the
license control item must be assigned a valid value before being delivered to an NE. If this NE does not
require the licensed feature, it is good practice to set the license control item to zero.
Figure 4.6 License control items with values of Not Set on the U2000
----End
Refer to this section when the base station to be upgraded is a NodeB, eNodeB, or BTS3900.
The U2000 automatically provides LMT files for the base station four hours after the base
station upgrade. This action reduces the impact of the upgrade on services. In an emergency,
run the SPL SOFTWARE command to supplement LMT files for the base station.
Step 1 Log in to the U2000 client and click . On the displayed Application Center tab page,
double-click Trace and Maintenance.
Step 2 From the main menu of the U2000 client, choose Maintenance > MML Command.
The MML Command window is displayed.
Choose Maintenance > MML Command to open the MML Command window on the U2000 in
traditional style.
Step 3 Choose NE from the navigation tree on the left-hand side, and select an NE from the NE list.
Step 4 Run the SPL SOFTWARE command, and set the parameters as listed in Table 1.1.
FTP Server IP Set it to the FTP server IP address of the U2000 server.
User Name Enter ftpuser.
Password Enter the default value Changeme_123 or the actual value.
Directory Name Enter /export/home/sysm/ftproot/ROSA/Software/BTS3900
V100R010C10SPC255.
Parameter Setting
During this process, the progress is displayed in the MML command information pane.
Step 5 Check whether the operation has succeeded. If the operation succeeds, the following
information is displayed:
Report Type = Supply Software
Status = Success
Session ID = 65536
If the LMT is being used, exit the LMT, restart it, and log in to the base station.
----End
After the upgrade, follow the instructions in this chapter to verify the upgrade.
If any of the following conditions occurs after the upgrade, the base station will be
automatically rolled back to the source version without manual operations.
The base station cannot start up.
The NodeB, eNodeB, or co-MPT base station is disconnected from the U2000 and is not
logged in to for 30 minutes after the upgrade.
The GBTS fails to connect to the BSC in a specific duration (30 minutes by default).
For a GBTS, the specific duration is specified by bit 0 and bit 1 of Reserved Parameter 2 in
the SET BTSPATCHPARA command. For details about Reserved Parameter 2, see
BTS3900 V100R010C10 (GBTS) Used Reserved Parameter List.
The rollback takes about 15 minutes, during which base station services and maintenance are
interrupted. Wait 15 minutes before you log in to the base station using the U2000. For a
GBTS using a GTMUa as the main control board, the version rollback involves automatic
software loading and activation of other boards. Therefore, the version rollback may take
more than 15 minutes. The data configuration after the rollback is the same as that before the
upgrade.
1 5.2Checking the Running Status No new alarm is reported and boards are not
of the Base Station reset unexpectedly after the upgrade.
2 5.3Performing a Dialing Test No exceptions are detected during the dialing
test.
You are advised to check the alarms and cell status 10 minutes after the upgrade is completed.
Step 2 Specify a path to save the report in the displayed dialog box.
The U2000 automatically generates an upgrade report for the upgraded NE.
Step 3 Click View to view the upgrade report.
----End
Figure 1.1 Comparing alarms reported before and after the upgrade
Step 2 Specify a path to save the report in the displayed dialog box.
The U2000 automatically generates a report which contains comparison results of alarms
generated before and after the upgrade.
Step 3 Click View to view the report.
Check the alarm comparison results and ensure that the following criteria are met:
The base station has not generated major or severe alarms for 10 minutes after the
upgrade.
The alarms that were expected to be cleared in the target version were cleared.
The alarms that were not expected to be cleared in the target version were not cleared.
No new alarm is introduced into the target version.
----End
Figure 1.1 Comparing cell status before and after the upgrade
Step 2 Specify a path to save the report in the displayed dialog box.
The U2000 automatically generates a report, which contains the cell status before the upgrade,
the cell status after the upgrade, and the cell status comparison results.
Step 3 Click View to view the report.
If the cell status is abnormal after the upgrade, handle alarms by referring to the online alarm
help. If the alarm is cleared but the cell status is still abnormal, contact Huawei technical
support engineers.
----End
KPIs collected in a measurement period (usually 1 or 0.5 hours) after the upgrade have
no significant fluctuation compared with those collected in the same period one week
before the upgrade. Table 1.1, Table 1.2, and Table 1.3 list the KPIs to be compared.
Method 2
To avoid major network problems after an upgrade of a NodeB or an eNodeB, collect
hourly KPIs during the 24 hours following the upgrade, and compare these KPIs with
those collected during the same period of the week before the upgrade. Table 1.1 and
Table 1.3 list the KPIs to be compared.
If both methods show no significant fluctuation, the upgrade was successful.
Traffic CS Erlang, PS (64 kbit/s, 128 The difference does The difference
volume kbit/s, and 384 kbit/s), HSDPA, not exceed 5%. does not exceed
HSUPA, RRC setups, and RAB 5%.
setups (CS, PS, and HSPA)
Service RRC, RAB, and HSPA The difference does The difference
setup not exceed 0.2%. does not exceed
success rate 0.4%.
Success rate Intra-frequency, inter- The difference does The difference
of mobility frequency, and inter-RAT not exceed 0.2%. does not exceed
0.4%.
Call drop AMR, PS, HSDPA, and The difference does The difference
rate HSUPA not exceed 0.2%. does not exceed
0.4%.
Others KPIs specified by the customer The difference does The difference
not exceed 1%. does not exceed
1%.
Channel)
Call drop rate Call Drops on Traffic Channel The difference does not
Call Drops due to Equipment Failure exceed 0.4%.
(Traffic Channel)
Call Drop Rate on TCHF per cell
Call Drop Rate on TCHH per cell
Handover success Success Rate of Incoming Internal The difference does not
rate Inter-Cell Handovers exceed 1%.
Success Rate of Outgoing Internal
Inter-Cell Handovers
Successful TCH Seizures in TCH
handovers (Traffic Channel)
Congestion rate Failed TCH Seizures in TCH The difference does not
Handovers due to Busy TCH (Traffic exceed 5%.
Channel)
Congestion Rate on SDCCH per CELL
(due to Busy)
Failed SDCCH Seizures due to Busy
SDCCH
Congestion Rate on TCH (All
Channels Busy)
Assignment success Successful Downlink Assignment Rate The difference does not
rate Successful Uplink Assignment Rate exceed 2%.
Traffic Radio Bearers Uplink Traffic The difference does The difference
volume Volume Downlink Traffic Volume not exceed 10%. does not exceed
10%.
Service RRC Setup Success Rate (Service) The difference does The difference
setup RRC Setup Success Rate not exceed 0.5%. does not exceed
success (Signaling) ERAB Setup Success 0.5%.
rate Rate (All)
Success Intra-frequency Handover Out The difference does The difference
rate of Success Rate Inter-frequency not exceed 0.5%. does not exceed
mobility Handover Out Success Rate 0.5%.
Handover In Success Rate Inter-
RAT Handover Out Success Rate
(LTE to CDMA) Inter-RAT
Handover Out Success Rate (LTE
For the BTS3900, NodeB, and eNodeB, if configuration parameters are modified after an
upgrade, a version rollback will invalidate the modified values of the parameters. Before
performing a version rollback, assess impacts of the modified configurations and determine
whether the impacts are acceptable.
Step 1 Log in to the U2000 client and click . On the displayed Application Center tab page,
double-click Software Management.
The Software Management Expert window is displayed.
Choose Software > Software Management Expert to open the Software Management Expert
window on the U2000 in traditional style.
Step 2 In the Software Management Expert window, click Create Project to create a rollback
project.
Step 3 In the displayed Create Project dialog box, set the parameters as follows:
1. Name: Name the project. The maximum length is 60 characters.
2. Upgrade Type: Set Upgrade Type to Rollback.
3. Remarks: Enter the description of the rollback project. The maximum length is 255
characters.
Then, click OK.
----End
Step 1 Click in the upper left-hand corner of the middle pane to create a rollback task, as shown
in Figure 1.1.
Step 2 In the displayed Create Batch-[1/2] dialog box, select the base station controller or subnet
under which the base stations to be rolled back are located. Then, click Next, as shown in
Figure 2.1.
Type of NE to Be Configuration
Upgraded
GBTS Select the base station controller under which the base station is
located.
NodeB Select the base station controller under which the base station is
located.
Type of NE to Be Configuration
Upgraded
eNodeB Select the subnet under which the base station is located.
Co-MPT base station Select the base station controller or subnet under which the base
station is located.
Separate-MPT Select required options for each mode of the multimode base
multimode base station station.
Figure 2.1 Selecting the base station controller or subnet under which the base stations to be rolled
back are located
Step 3 In the displayed Create Batch-[2/2] dialog box, select a base station type to be rolled back.
Then, click Finish. The U2000 begins to check the rollback capability of the base station, as
shown in Figure 3.1.
If the base stations to be rolled back include GBTSs (GO, GU, GL, or GUL), the U2000 will
check the rollback capability of GBTSs. If the NEs Cannot Be Rolled Back dialog box is
displayed, the GBTSs cannot be rolled back in this way. In this case, perform the following
operations to export these base stations:
1. Click Export All in the NEs Cannot Be Rolled Back dialog box to export base stations
that cannot be rolled back.
2. In the displayed Information dialog box, click OK.
3. In the NEs Cannot Be Rolled Back dialog box, click Continue. Then click OK in the
displayed Confirm dialog box.
After exporting all the base stations that cannot be rolled back, roll back other base
stations that can be rolled back and then roll back exported base stations by referring to
7.16How Do I Handle the Problem that Some GBTSs Cannot Be Rolled Back?
Step 4 Right-click the batch and choose Upgrade Execution from the shortcut menu, as shown in
Figure 4.1.
Step 5 In the displayed Upgrade Execution-[2/3] dialog box, set Execution Type and Execution
Time. It is recommended that these parameters retain their default values. Then, click Next,
as shown in Figure 5.1.
Step 6 Confirm the version rollback information and click Continue, as shown in Figure 6.1.
Step 7 In the displayed Upgrade Execution-[3/3] dialog box, confirm the rollback parameters, as
shown in Figure 7.1. Then, click Finish.
Step 8 In the displayed main window of the newly created rollback task, check the status of the
rollback task. When the progress reaches 100% and the status becomes Completed, the
rollback is complete, as shown in Figure 8.1.
For a multimode base station, a Check Version Match dialog box will be displayed. If the
version verification fails, contact Huawei technical support for a new upgrade policy. If a
forced rollback is required despite the verification failure, perform a forced rollback by
referring to 7.5How Do I Enable the Forced Upgrade Function for a Multimode Base Station?
----End
After the software version is rolled back to a source version earlier than SRAN10.1, names of
new alarms and events in SRAN10.1 will be displayed as Undefined on the LMT.
7 FAQs
Step 4 Log out of the U2000 client and then log in again.
----End
Step 1 Log in to the U2000 client and click . On the displayed Application Center tab page,
double-click Software Management.
Step 2 From the main menu of the U2000 client, choose NE File > NE Backup. All the NE backup
tasks are displayed on the lower part of the NE Backup window, as shown in Figure 2.1.
Choose Maintenance > Backup Management > NE Backup to open the NE Backup window on the
U2000 in traditional style.
----End
Step 1 Log in to the U2000 client and click . On the displayed Application Center tab page,
double-click Software Management.
Step 2 From the main menu of the U2000 client, choose NE File > Software Browser. All the NE
log synchronization tasks are displayed on the lower part of the NE window, as shown in
Figure 2.1.
Choose Software > Software Browser to open the Software Browser window on the U2000 in
traditional style.
----End
Choose Maintenance > MML Command to open the MML Command window on the U2000 in
traditional style.
Step 3 Choose NE from the navigation tree on the left-hand side, and select an NE from the NE list.
Step 4 In the displayed Command Input dialog box, enter SET BTSLOADCTRL in the
Command Input text box, click , and set related parameters, as shown in Table 1.1.
Index Type Select BYID(By Index) from the Index Type drop-down list.
BTS Index Enter the index of the target BTS in BTS Index.
Control Flag Select YES(Set Control Flag) in Control Flag.
NOTE
To grant load control rights to the GSM mode, select YES(Set Control Flag).
To grant load control rights to the UMTS or LTE mode, select NO(Cancel
Control Flag).
For details about loading control rights, see Appendix 1 Version Mapping
Information, which can be obtained from the directory Release
Notes\Multimode Base Station Release Notes\Release Notes (Word_Excel)
in the document package delivered with the software version of the multimode
Parameter Setting
base station.
Choose Maintenance > MML Command to open the MML Command window on the U2000 in
traditional style.
Step 3 Choose NE from the navigation tree on the left-hand side, and select an NE from the NE list.
Step 4 Enter the SET LOADCTRL command in the Command Input text box. Set the parameters
listed in Table 1.1.
Load Control Set this parameter to YES(Set Control Flag) or NO(Cancel Control
Flag Flag).
NOTE
For details about loading control rights, see Appendix 1 Version Mapping
Information, which can be obtained from the directory Release
Parameter Setting
Notes\Multimode Base Station Release Notes\Release Notes (Word_Excel)
in the document package delivered with the software version of the multimode
base station.
Control Mode If the base station is a UL dual-mode base station, set this parameter to
UL.
If the base station is a GU dual-mode base station, set this parameter to
GU.
If the base station is a UMTS+GSM+LTE base station, set this
parameter to UL and GU. Note that this can be done by setting them
individually in two separate sessions. The setting sequence can be
reversed.
Choose System > Preferences to open the Preferences window on the U2000 in traditional style.
Step 2 In the navigation tree, click SWM Preferences, and select Allow this client to forcibly
upgrade multimode base station, as shown in Figure 2.1.
Step 6 Click OK. The Upgrade Execution [2/3] dialog box is displayed.
The loading control rights need to be set before version verification. For details, see Appendix
1 Version Mapping Information, which can be obtained from the directory Release Notes\
Multimode Base Station Release Notes\Release Notes (Word_Excel) in the document
package delivered with the software version of the multimode base station. The loading
control rights need to be granted to the version which to be upgraded.
Step 7 Disable the forced upgrade function after the upgrade. To disable the function, clear Allow
this client to forcibly upgrade Multimode base station, and click OK, as shown in Figure
2.1.
----End
Step 1 Log in to the U2000 client and click . On the displayed Application Center tab page,
double-click Software Management.
The Software Management Expert window is displayed.
Choose Software > Software Management Expert to open the Software Management Expert
window on the U2000 in traditional style.
The file server is used to store base station software packages and to provide FTP server
services for the base station to be upgraded.
During the software upgrade, the base station downloads the software package from the file
server.
Set the file server based on the networking mode:
If the U2000 manages the base station through a base station controller, set the base
station controller or U2000 as the file server. The base station controller is
recommended.
If the U2000 directly manages the base station, set the U2000 as the file server. If a
firewall restricts the access of the base station FTP client to the U2000 server, configure
another server and ensure that there is no firewall between the server and the base
station.
If the U2000 manages the base station through a base station controller, the advantages of
setting the base station controller as the file server are as follows:
During the upgrade, the base station can download software packages in batches from
the base station controller at a higher speed than from the U2000.
If a firewall restricts the access of the base station FTP client to the U2000 server in the
IP network configuration, software packages fail to download from the U2000 acting as
the file server but can be downloaded from the base station controller acting as the file
server.
Before the upgrade, check whether the file server has been correctly configured.
When the network conditions are poor, the data transmission time may exceed the firewall FTP session
time, causing the software package download to fail. In this case, check the firewall settings and increase
the FTP session time to ensure that the software package can be downloaded from the U2000 to the file
server.
If you choose Export Batch > By Base Station when exporting NE information to a file, select
Upgrade by Base Station in the Create Batch[2-2] window to import the file.
If you choose Export Batch > By NE when exporting NE information to a file, select Upgrade by
NE in the Create Batch[2-2] window to import the file.
The procedure for upgrading the BootROM is similar to the procedure for upgrading the base
station, including the software download and activation operations.
After the BootROM is upgraded, perform upgrade risk checks again to ensure that the BootROM
upgrade is successful.
The base station does not need to be reset after the BootROM software is activated. Activating the
BootROM software does not affect the base station's services and functions.
Ensure that the power supply to the base station is stable when BootROM is being upgraded. If the
power supply to the base station is insufficient or the base station is powered off and then powered
on during the BootROM upgrade, BootROM of the base station's boards may be damaged. As a
result, the base station cannot be started.
Re-download the software package if downloading a software package fails. Downloading software
packages will not affect the base station's services or functions.
If the upgrade risk check results show that BootROM needs to be upgraded, download the software
package of BTS3900 V100R010C10SPC255 and upgrade the BootROM in the software package.
You can use either of the following methods to obtain the BootROM version:
Method 1: Click the hyperlink BTS3900 and log in to Huawei support website using a Huawei
engineer account. Download the BTS3900 V100R010C10SPC255 software package. If the GUI
language is not the target language, select the target language at the top of the page.
Method 2: Log in to http://support.huawei.com using a Huawei engineer account and then search for
BTS3900 on the Software tab page. Download the BTS3900 V100R010C10SPC255 software
package.
Step 1 Log in to the U2000 client and click . On the displayed Application Center tab page,
double-click System Management.
The Software Management Expert window is displayed. Choose Software > Software Management
Expert to open the Software Management Expert window on the U2000 in traditional style.
Step 2 Use the Software Management Expert to create an upgrade project. For details, see
4.1Creating an Upgrade Project.
In the Create Project dialog box, set Upgrade Type to Upgrade, and upload the BTS3900
V100R010C10SPC255 software package.
After the software package is uploaded, set Upgrade Type to Upgrade BootROM and click
Select from OSS Server. In the displayed Select Target Version dialog box, select BTS3900
V100R010C10SPC255 and click OK.
Ensure that all parameters are correctly set. Click OK to finish the upgrade project creation.
Step 3 In the main window of the newly created upgrade project, click .
Step 4 In the Create Batch-[1/2] dialog box, select the base station controller and subnet under
which the base station whose BootROM needs to be upgraded is located and click Next.
Step 5 In the Create Batch-[2/2] dialog box, select the base station whose BootROM needs to be
upgraded and click Finish.
Step 6 Right-click the batch and choose Upgrade Execution from the shortcut menu, as shown in
Figure 6.1.
----End
Step 2 In the displayed Modify Batch-[1/2] dialog box, modify the base station controllers and
subnets where the base stations to be upgraded are located.
Type of NE to Be Configuration
Upgraded
GBTS Select the base station controller under which the base station is
located.
NodeB Select the base station controller under which the base station is
located.
eNodeB Select the subnet under which the base station is located.
Co-MPT base station Select the base station controller or subnet under which the base
station is located.
Separate-MPT Select required options for each mode of the multimode base
multimode base station station.
If the eNodeBFunction of a co-MPT base station or the eNodeB does not belong to any subnet, select
ROOT.
Step 3 Click Next. In the displayed Modify Batch-[2/2] dialog box, modify the NEs to be upgraded,
as shown in Figure 3.1.
When software download fails, double-click the failed download task, and perform relevant
operations by referring to the solutions described in Table 1.1.
1 Insufficient 1. Run the MML command LST BTSSW on the U2000 client to
BSC OMU query the GBTS software version information saved in the BSC
space OMU.
2. Run the MML command RMV BTSSW to delete redundant
BTS software versions.
If the failure has been rectified, re-upgrade the base station by referring to the procedure in
4.5Creating an Upgrade Task.
If the failure cannot be rectified using the information collected, contact Huawei technical
support and collect additional information about the failure. The information to be collected is
described in Table 1.3.
the base wait ten minutes for the board to become functional again.
station is
reset,
interrupting
the
operation.
If the problem persists, contact Huawei technical support and collect information listed in
Table 1.3.
Detailed On the left of the NE Upgrade Task tab page, choose Upgrade Task >
information GBTS > Complete to check the failed task. Then, double-click the task
about the to view the details.
upgrade failure
Logs on the 1. Log in to the FTP file server installed on the U2000 by entering the
common layer relevant command in the Run dialog box.
of the U2000 2. Obtain current traced messages from the following directory:
/opt/oss/server/var/logs/iMAP.swm_agent.trace
3. Obtain past traced messages from the following directory:
/
opt/oss/server/var/logs/tracebak/iMAP.swm_agent.trace.2009071
9103550.tar.gz
Where, 20090719103550 indicates the time when the file was
generated.
4. Download the traced files from the FTP server to the local PC.
Logs on the 1. Log in to the FTP file server installed on the U2000 by entering the
mediation of relevant command in the Run dialog box.
the U2000 2. Obtain current traced messages from the following directory:
server /opt/oss/server/var/logs/iMAP.med*_agent.trace
Where, * is a wildcard. Different types of messages must be obtained
one by one.
3. Obtain past traced messages from the following directory:
/
opt/oss/server/var/logs/tracebak/iMAP.med*_agent.trace.2009071
9103550.tar.gz
Where, 20090719103550 indicates the time when the file was
generated.
4. Download the traced files from the FTP server to the local PC.
BSC logs 1. On the BSC Web LMT, run the COL LOG command and select
OPT_LOG and OMU_LOG from the Log File Type drop-down
list. Wait until the download is complete.
Data Operation
Collection
2. Run the LST LOGRSTINFO command to obtain the name and path
of the generated file.
3. Log in to the BSC file server and obtain the logs.
BTS 1. On the BSC LMT, run the LST OMUAREA command to check
configuration whether the active directory is version_a or version_b.
data 2. Log in to the BSC file server, and then save all the files in the
\mbsc\bam\version_a (b)\ftp\bts_upgrade directory.
BTS logs 1. On the BSC LMT, run the STR BTSLOG command to obtain the
BTS logs.
2. Run the ULD BTSLOG command to save the BTS logs to the local
PC.
Alarm 1. Log in to the U2000 client and click . On the displayed
information Application Center tab page, double-click Fault Management. On
the displayed Browse Current Alarms tab page, click Filter.
2. Set alarm filter conditions based on the NE information.
3. Right-click an alarm and choose Save > Save All Records.
Choose System > Preferences to open the Preferences window on the U2000 in traditional style.
Step 2 In the navigation tree of the Preferences window, choose Connection Settings > NE/OSS
Server Connection Settings. In the NE/OSS Server Connection Settings (for Server) pane,
check whether the settings of Encryption Mode, OSS Authentication Mode, and Data
Connection Mode are the same as those in Error: Reference source not found. If they are not,
modify the settings and ensure that they are the same as those in this figure.
----End
Step 2 In the main window of the newly created upgrade project, click , as shown in Figure 2.1.
Step 3 In the displayed Create Batch [1/2] dialog box, select the base station controller under which
the base stations to be rolled back are located.
Step 4 Click Next.
In the Create Batch [2/2] dialog box, set Upgrade by to NE, and then click Import to import
the base stations exported in Step 3 of 6.2Performing the Rollback.
In the Create Batch [2/2] dialog box, the NEs that need to be rolled back are automatically
selected after the import, as shown in Figure 4.1.
Step 5 Click Finish in the Create Batch [2/2] dialog box. On the Batch Management pane, right-
click the newly created rollback batch and choose Preparation Confirmation from the
shortcut menu, as shown in Figure 5.1.
Step 6 Confirm upgrade preparations in the Preparation Confirmation pane, as shown in Figure
6.1.
Step 7 Specify the status of each preparation task based on the actual situation. Then, click Apply.
The upgrade preparation confirmation is complete.
When the base station is rolled back in an upgrade way, upgrade risk checks cannot be performed no
matter whether you select the upgrade risk check package in Step 1.
Step 8 Click NE Upgrade Task in the left-hand pane, and then click Create in the right-hand pane
to create an upgrade task, as shown in Figure 8.1.
Step 9 In the displayed Upgrade Execution [1/3] dialog box, select the batch to be rolled back and
click Next.
Step 10 In the displayed Upgrade Execution [2/3] dialog box shown in Figure 10.1, set parameters in
the Step Settings area as follows:
1. In the Step column, choose Download and Activate.
2. In the Upgrade Parameter column, retain the default value Abis Quick Load (Only
Effective for GSM Software): Common loading.
3. In the Execution Type column, choose Automatic Execution for Download and
Activate.
Step 11 Click Next in the Upgrade Execution [2/3] dialog box and click Yes in the displayed
Confirm dialogue box. Confirm the rollback task parameters, and click Finish.
Step 12 On the displayed NE Upgrade Task tab page, check the status of the upgrade task.
Step 13 In the Details area of the NE Upgrade Task tab page, check the progress of each item.
When the progress reaches 100% and the status becomes Completed, the rollback
succeeds.
When progress cannot reach 100% and a failure message is displayed, the rollback fails.
If the rollback fails, handle this problem by referring to 7.14How Do I Handle a Base Station Software
Activation Failure?
----End
Step 2 In the displayed Confirm dialog box, click Yes to download the upgrade risk check result and
save it in the correct directory.
Step 3 When the downloading progress reaches 100%, click View. The upgrade risk check result is
displayed, as shown in Figure 3.1.
Step 4 Click Failed All-Risk-Check Items to display detailed information on failed check items.
Click Warning All-Risk-Check Items to display detailed information on warnings.
You can click Failed Key-Risk-Check Items and Warning Key-Risk-Check Items to view detailed
information on failed key check items and warnings, respectively.
Step 5 Rectify the faults leading to failure of the upgrade risk check on the NE based on the handling
methods provided in the check result. Perform upgrade risk check again until the check is
successful. Then, upgrade the base station.
----End
Step 2 Select Multimode Base Station View from the Current View drop-down list. In the left-
hand Multimode Base Station View navigation tree, you can view the icon for each base
station, as shown in Error: Reference source not found. According to the icon, you can
determine the base station type.
On the Main Topology tab page, you can click to view the types of base stations indicated by
different icons.
----End
The NE Type field displayed behind the software version in the Software Management Expert
window of the U2000 indicates whether it is an SRAN package or a single-mode package. For details,
see 7.6How Do I Know Whether an Upgrade Software Package Is for SRAN or Single-Mode?
A Upgrade Record
Upgrade Record
Cell name
Cell ID
Remarks
Verified by
Cell Name
Cell ID
Cell Scrambling
Code
Remarks
Tested By (signature)
Cell Name
Cell ID
Remarks
Verified By
(signature)
2G 2nd Generation
3G 3rd Generation
A
AMR Adaptive Multirate
B
BSC Base Station Controller
C
CME Configuration Management Express
Co-MPT In an MBTS with co-MPT, different modes share one main control
board and one O&M channel.
CPU Central Processing Unit
CS Circuit Switched
E
EMU Environment Monitoring Unit*
eGBTS A GSM base station that is directly managed by an EMS.
eNodeB E-UTRAN NodeB
G
GBTS GSM base transceiver station
GPRS General Packet Radio Service
GRFU GSM Radio Frequency Unit
GSM Global System for Mobile Communications
GTMU GSM Transmission and Timing and Management Unit
H
HSDPA High Speed Downlink Packet Access
HSPA High Speed Packet Access
HSUPA High Speed Uplink Packet Access
HTML Hypertext Markup Language
I
ID ID
IP Internet Protocol
K
KPI key Performance Indicator
L
LMT Local Maintenance Terminal
LTE Long Term Evolution
M
MBTS Multimode Base Station
MML Man-machine Language
MRRU Multi-carrier Remote Radio Unit
P
PDP Packet Data Protocol
PS Packet Switched
R
RAB Radio Access Bearer
RLC Radio Link Control
RNC Radio Network Controller
RRC Radio Resource Control
RSCP Received Signal Code Power
S
SIM Subscriber Identity Module
T
TCH Traffic Channel
TCHF Full-rate Traffic Channel
TCHH Half-rate Traffic Channel
TDM Time Division Multiple
U
UBRI Universal Baseband Radio Interface unit
UE User Equipment
UMPT Universal Main Processing and Transmission Unit
UMTS Universal Mobile Telecommunications System
W
WCDMA Wideband Code Division Multiple Access