Documente Academic
Documente Profesional
Documente Cultură
Issue 01
Date 2016-04-20
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
Purpose
This document describes how to upgrade a base station to V100R011C10SPCXXX and how
to roll back the upgrade using the U2000. It also provides FAQs and troubleshooting methods.
Intended Audience
This document is intended for upgrade operators. Upgrade personnel must:
Be familiar with the product networking and related NEs' versions.
Have device maintenance experience and be familiar with device operation and
maintenance.
Symbol Conventions
The symbols that may be found in this document are defined in the following table.
Symbol Description
Change History
Issue Date Description
Author
Contents
6 FAQs...............................................................................................................................................43
6.1 How Do I Grant or Cancel Loading Control Rights?...................................................................................................43
6.2 How Do I Enable the Forced Upgrade Function for a Multimode Base Station?........................................................44
6.3 How Do I Select and Use Upgrade Software Packages?.............................................................................................46
6.3.1 Upgrade Software Packages......................................................................................................................................46
6.3.2 Usage of Upgrade Software Packages.......................................................................................................................46
6.3.3 How Do I Know Whether an Upgrade Software Package Is for SRAN or Single-Mode?.......................................46
6.4 What Is the Function of the File Server?......................................................................................................................47
6.5 How Do I Plan Batches for the Entire Network?.........................................................................................................48
6.6 How Do I Handle a Failure in Distributing the Upgrade Software Package from the Master U2000 to the Slave
U2000?...............................................................................................................................................................................49
6.7 How Do I Handle a Base Station Software Activation Failure?..................................................................................50
A Appendix......................................................................................................................................51
A.1 Upgrade Record...........................................................................................................................................................51
A.2 Verification Record of LTE Services...........................................................................................................................52
Software About 35 minutes per base No more than 60 or 80 eNodeBs can download
download station software from the U2000 simultaneously. If
there are more than 60 or 80 eNodeBs in an
upgrade task, the U2000 automatically queues
the remaining eNodeBs.
Software About 20 minutes for 600 eNodeB services are interrupted during the last
activation base stations in each 3 minutes of an upgrade. After the upgrade is
upgrade task complete, eNodeB services automatically
resume.
Pilot Upgrade
Choose a typical site to perform the pilot upgrade. If no exceptions occur after the pilot
upgrade is complete, start the batch upgrade. Consider the following factors when selecting a
typical site:
All base station types of the site, such as the BTS3900, BTS3900A, BTS3900L,
DBS3900, and BTS3900AL
All types of BBU boards of the site ,,such as the LMPT, UMPT, UTRP, LBBP, and
UBBP
All types of RF modules of the site ,such as the MRRU, RFU, and MPMU
All versions of the base stations to be upgraded
All typical configurations
After the upgrade, observe key performance indicators (KPIs) and key features for a period of
time, typically three days or more. Ensure that KPIs and key features are normal before
performing a batch upgrade.
Batch Upgrade
Make a plan for the batch upgrade based on the upgrade specifications described in 1.4.1Time
Requirements for Upgrade and the actual situation on the live network.
For single-mode base stations, plan the upgrade batches based on the site location.
For multimode base stations, plan the upgrade batches based on the radio access standards
first, and then based on the site location.
Onsite personnel can plan the upgrade batches based on the actual situation on the live network.
If there are no problems after the pilot upgrade is complete, start the batch upgrade. Maximum
upgrade specifications should be based on the upgrade policy.
Do not upgrade base stations at the maximum upgrade specifications on the first day of the
upgrade. Instead, upgrade a small number of base stations on the first day, and then gradually
add base stations until the maximum number is reached.
To minimize the impact of upgrades, download the software during the daytime and
activate the software at night.
Determine the software download mode in advance and estimate the download time based
on site conditions. Ensure that the download is complete before activating the software.
− The upgrade method described in this document cannot detect the BootROM
version, provide any warnings about the BootROM version, or automatically
upgrade the BootROM version. It is recommended that the SME be used to perform
the upgrade so as to reduce upgrade risks.
− The LMT has configuration requirements for the OS, JAVA Platform Standard
Edition Runtime Environment (JRE), and web browser. After the base station is
upgraded, the LMT configuration requirements may change. To use the LMT,
ensure that the operating environment meets the minimum configuration
requirements by referring to the "Software Versions" section in release notes
delivered with the software version.
− The functions of the peripherals are decoupled from the function of the BBU. You
can upgrade the peripherals independently.
− For a eNodeB, USU3900, USU3910, or BTS3900, if the upgrade risk check results
show that the BootROM needs to be upgraded, upgrade it by following steps
provided in "How Do I Upgrade the BootROM?" in BTS3900
V100R011C10SPCXXX Upgrade Guide (SME-based).
− Before performing the mode-by-mode upgrade of a multimode base station, check
whether any of the following alarms is generated on each mode. If generated, clear
the alarm before the upgrade. Otherwise, cells may go out of service after the
upgrade.
GSM alarm: ALM-28010 Carrier Configuration Error
UMTS alarm: ALM-28211 Cell Configuration Abnormal
LTE alarm: ALM-29240 Cell Unavailable
− Back up the configuration file before the upgrade.
2. Precautions during the upgrade:
− Software activation interrupts ongoing services. You are advised to activate base
station software at night during off-peak hours. You can perform other upgrade
operations in advance to shorten the upgrade duration.
− Upgrade the base station during off-peak hours because certain system resources
will be occupied during the download and activation. During peak hours, the
upgrade will cause system resources to be insufficient and base station KPIs to
deteriorate.
− In a USU3900-based base station interconnection scenario, upgrade the USU3900
to the target version before upgrading the base stations if a USU3900 version earlier
than V100R011C10 is used. To determine the target USU3900 version, see the
"Related Product Versions" section in release notes delivered with the software
version. If the USU3910 is used for base station interconnection, there is no
restriction on the USU3910 and base station upgrade sequence.
− During the upgrade, do not modify the data of intermediate transmission equipment,
which may disconnect normal connections between the U2000 and the eNodeBs
being upgraded.
− During the upgrade, do not perform any configuration operations on the base
station.
− Ensure that transmission is normal during the upgrade. If the transmission of a base
station is disconnected during the upgrade, the base station is restored to the
original version after being restarted. When this happens, perform the upgrade
again.
− If the link between the peer base station and the U2000 is disconnected during a
mode-by-mode 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
----End
In the application style, click . On the displayed Application Center tab page,
double-click Configuration. From the main menu of the U2000, choose Browser >
Report > NE Report.
In the traditional style, choose Configuration > Report > NE Report.
Step 2 In the NE Report dialog box, select the target base stations, and click OK in the lower right-
hand corner to query the base station version, as shown in Figure 2.1.
----End
For details about the definition, functions, and settings of the file server, see 6.4What Is the Function of
the File Server?
In the application style, click . On the displayed Application Center tab page,
double-click Configuration. From the main menu of the U2000, choose Settings > File
Server Settings.
In the traditional style, choose Software > File Server Settings.
Step 2 Choose NE > eNodeB and select the NE to be upgraded under the file server node, as shown
in Figure 2.1.
Step 3 Check whether the file server settings of all the base stations displayed in the right 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 4.
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 4 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 4.1.
The default file server for an NE is the U2000 and you can change the file server to another NE or a
third-party FTP server based on the actual situation.
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 5 Double-click the box under Value, choose a server name from the drop-down list, and then
click OK.
Step 6 Click Apply to make the settings take effect, as shown in Figure 6.1.
----End
After the U2000 mediation software is installed, the U2000 client prompts you to log in to the U2000
client again. In this case, log out of the U2000 client and log in again.
In the application style, click . On the displayed Application Center tab page,
double-click Software Management. From the main menu of the U2000 client, choose
NE File > Software Browser.
In the traditional style, choose Software > Software Browser.
Step 2 On the OSS Server tab page, choose Server > OSS > Mediation > BTS3900 LTE from the
navigation tree. View the installed U2000 mediation software versions in the Mediation
Version column, as shown in Figure 2.1.
Step 3 Check whether the U2000 mediation software version listed in the "Software Version
Compatibility" section of Release Notes can be found in the query result of Step 2.
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 4.
Step 4 Obtain the required U2000 mediation software according to the operations provided in
2.1.2Obtaining Upgrade Software Packages and Reference Documents and install it.
Step 5 After the installation is complete, repeat Step 1 through Step 3 to check the U2000 mediation
software version again and ensure that it has been successfully installed.
----End
To prevent alarms from being reported during the upgrade and affecting network O&M, you
can set the maintenance mode to UPGRADE before performing the upgrade. After the
upgrade, set the maintenance mode to NORMAL.
Before the upgrade, take the following steps to set NE maintenance mode:
Step 1 Open the Maintenance Mode window.
In the application style, click . On the displayed Application Center tab page,
double-click Configuration. From the main menu of the U2000 client, choose Settings
> Maintenance Mode.
In the traditional style, choose Maintenance > Maintenance Mode.
Step 2 Click . In the displayed Set Maintenance Mode dialog box, select the NE whose
maintenance mode needs to be configured, set NE maintenance mode to UPGRADE, and
click OK, as shown in Figure 2.1.
Step 3 Check the setting progress. When the progress reaches 100%, the maintenance mode is
successfully set.
To restore the NE maintenance mode, repeat the preceding steps (set NE maintenance mode to
NORMAL in step 2).
----End
2.2.5 Checking Whether the U2000 Has the Software That the Base
Station Currently Runs
To ensure that a version rollback can be performed immediately in case an 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 Open the Software Browser window.
In the application style, click . On the displayed Application Center tab page,
double-click Software Management. From the main menu of the U2000 client, choose
NE File > Software Browser.
In the traditional style, choose Software > Software Browser.
Step 2 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.
Versions displayed on the Software tab page on the right-hand pane indicate the software
versions on the U2000, as shown in Figure 2.1.
Step 3 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, download the required software by performing the steps
described in 2.1.2Obtaining Upgrade Software Packages and Reference Documents. On
the Software Browser tab page, click Transfer and select From OSS Client to OSS
Server from the displayed drop-down list to upload the software to the U2000 server.
Step 4 Repeat Step 2 and Step 3 and ensure that all required software 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:
On the U2000, press F1. The U2000 Online Help window is displayed.
Choose Performance Management > Performance Measurement Management > Performance
Management During Routine Maintenance > Exporting NE Performance Measurement Results.
Then, save the NE performance measurement results.
For a multimode base station, check the status of the peer mode by referring to the upgrade
verification description in the corresponding upgrade guide. If the working status of the peer
mode is abnormal, rectify any faults before performing the upgrade.
In the application style, click . On the displayed Application Center tab page,
double-click Software Management. From the main menu of the U2000 client, choose
NE License > Stand-Alone.
In the traditional style, choose License > NE License Management > Stand-Alone.
The Filter dialog box is displayed when the Stand-Alone License Management window is opened for
the first time. You can click OK to continue.
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
To ensure a reliable upgrade, check the new license file before the upgrade. Ensure that the
specifications of the new license are not lower than those of the current license, the new
license file is correct, and version incompatibility problems will not occur after the upgrade. If
the specifications of the new license are lower than those of the current license, services may
be affected after the upgrade.
Step 1 In the Stand-Alone License Management window, click NE License Maintenance in the
navigation tree. Then choose NE License Maintenance Operation > Check License in the
lower right-hand pane.
Step 2 In the Check License dialog box, click the Check license option, and click Next.
Step 3 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 4 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, add the
eNodeBs to the Selected Devices area, and then click OK.
If the new license file is in .xml format, perform Step 4. If the new license file is in .zip format, the
target NE is selected in the Check License dialog box by default; skip Step 4 and go to Step 5.
Step 5 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 6 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
You need to install the CME only when the CME needs to be used after the upgrade.
Before the NE upgrade, check whether the CME is compatible with the target version after
the upgrade. If not, the CME will become unavailable. See corresponding RNs to determine
the CME version and component package matching the base station, and contact U2000
maintenance engineers to install the CME.
.
If an SRAN package has been uploaded and you want to upgrade the base stations working in
another RAT, skip this section.
To upload the upgrade software package to the U2000 server, perform the following steps:
Step 1 Open the NE File Transfer window.
In the application style, click . On the displayed Application Center tab page,
double-click Software Management. From the main menu of the U2000 client, choose
NE File > NE File Transfer.
In the traditional style, choose Software > NE File Transfer.
Step 2 In the NE File Transfer dialog box shown in Figure 2.1, set the parameters as follows:
1. Select From OSS Client to OSS Server from the Direction drop-down list.
2. Select an NE type from the NE type drop-down list based on the type of NEs to be
upgraded.
3. 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 and upload the package again by referring to 2.1.2Obtaining Upgrade
Software Packages and Reference Documents.
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 6.3How Do I Select and Use Upgrade Software
Packages?
The upgrade software package starts uploading from the local PC to the U2000 server. On the
FTP Task tab page in the lower left-hand corner of the window, the upload progress is
displayed. When the progress reaches 100%, the upgrade software package has been
successfully uploaded.
----End
Before the risk check, upload the risk check package to the U2000 server, ensuring that the
latest risk check package is used.
Step 1 Log in to the U2000 client and display the NE File Transfer dialog box.
In the application style, click . On the displayed Application Center tab page,
double-click Software Management, choose NE File > NE File Transfer.
In the traditional style, choose Software > NE File Transfer.
Step 2 In the NE File Transfer dialog box, set parameters as follows, as shown in Figure 2.1.
Set Direction to From OSS Client to OSS Server.
Select an NE type from the NE type drop-down list based on the type of NEs to be
upgraded.
Set File type to Upgrade Risk Check Package.
Figure 2.1 Uploading the risk check package from the OSS client to the OSS server
If a message An error occurs when uploading files is displayed in the Message dialog box, obtain the
risk check package again by following the steps provided in 2.1.2Obtaining Upgrade Software Packages
and Reference Documents.
In the application style, click . On the displayed Application Center tab page,
double-click Software Management.
Step 4 Confirm the parameter settings on the Create Project dialog box. Then, click OK.
The system automatically displays the newly created upgrade project on the main window.
Step 5 Click Create Batch. In the displayed Create Batch dialog box, click Create One Batch and
OK, as shown in Figure 5.1.
To create multiple batches, perform Step 5 through Step 8 for multiple times. Alternatively, create
multiple batches or plan the network batches by following the steps provided in 6.5How Do I Plan
Batches for the Entire Network?
Step 6 In the displayed Create Batch [1/2] dialog box, select the base station controller under which
the base stations to be upgraded are located.
Step 7 Click Next.
In the displayed Create Batch [2/2] dialog box, select the NEs to be upgraded, as shown in
Figure 7.1.
If you need to modify an unstarted upgrade batch, right-click the batch and choose Modify Batch from
the shortcut menu.
Step 9 In the navigation tree of the Software Management Expert tab page, click the newly created
upgrade batch. In the Upgrade Process area, click Next. In the displayed Confirm dialog
box, click Yes to perform the risk check before download, as shown in Figure 9.1.
After the risk check, the check status is displayed, as listed in Table 1.1.
----End
Downloading LMT files together with the upgrade software package from the U2000 will
extend the download duration. If the main control board is a UMPT board, the download will
be extended by about 2 minutes. If the main control board is an LMPT board, the download
will be extended by about 25 minutes.
To allow the base station to download LMT files together with the upgrade software package,
perform the following steps:
Step 1 Open the Preferences window.
In the application style, choose File > Preferences.
In the traditional style, choose System > Preferences.
Step 2 In the left-hand navigation tree, click SWM Preferences. Select Download the Web LMT
immediately on the right-hand pane. Then, click OK.
----End
When creating an upgrade task, you only need to configure essential upgrade task information. Creating
an upgrade task does not affect NE operations.
In the application style, click . On the displayed Application Center tab page,
double-click Software Management. From the main menu of the U2000 client, choose
Upgrade > NE Upgrade Task Management.
In the traditional style, choose Software > NE Upgrade Task Management.
Step 2 On the displayed NE Upgrade Task window, click Create in the upper left-hand corner. On
the displayed list, select eNodeB.
If a message is displayed indicating that the U2000 CPU is overloaded, suspend the upgrade task for five
minutes. If the U2000 CPU is overloaded for 30 minutes, do not perform the upgrade and contact
Huawei technical support.
Step 3 In the displayed eNodeB-NE Upgrade Wizard [1/3] dialog box shown in Figure 3.1, set the
following parameters:
1. Enter a task name in Task name (cannot exceed 60 characters).
2. Retain the default setting as Upgrade in Upgrade type.
3. In the Available NEs area, select the NEs to be upgraded.
Determine whether to reload the license file by referring to 2.3.2Checking Whether You Need to Apply
for a License. If the license file needs to be reloaded, ensure that the following preparations have been
made:
The license file of the eNodeB to be upgraded has been backed up according to the instructions in
1.6Upgrade Precautions.
The license status of the eNodeB has been synchronized by following the operations in
2.3.3Operations to Be Performed Before an eNodeB License Upgrade.
The license file for the new version has been obtained before the upgrade.
To upload the license file, perform the following steps:
Select the Upgrade License check box in the Step Settings area.
Click License File.
In the displayed Select NE License dialog box, select a license file in .zip format from the save path
and then click OK.
The license file will be automatically loaded to the eNodeB during the upgrade.
If the license file is in .xml format, reload the license file after the upgrade by referring to 3.4(Optional)
Reloading a License File for the eNodeB.
Step 5 Click Next and check whether the upgrade information is correct.
For a multimode base station, if version verification fails, contact Huawei technical support
for a new upgrade policy. If a forced upgrade is required for the base station despite the
version inconsistency, perform a forced upgrade by referring to 6.2How Do I Enable the
Forced Upgrade Function for a Multimode Base Station?
You can select a base station to check the upgrade progress. The U2000 automatically divides the
base stations into batches for software download. You can estimate the duration of software
download for all the base stations by referring to the section "1.4.1Time Requirements for Upgrade."
----End
Activate the base station software only after it has been downloaded successfully. Activating
the base station software interrupts ongoing services. Therefore, activate the base station
software only during off-peak hours.
Assuming that the software is successfully activated, after the base station is reset, the base
station automatically rolls back to the source version if the base station fails to connect to the
U2000 and no LMT logs in to the base station within 30 minutes.
In the application style, click . On the displayed Application Center tab page,
double-click Software Management. From the main menu of the U2000 client, choose
Upgrade > NE Upgrade Task Management.
In the traditional style, choose Software > NE Upgrade Task Management.
Step 2 In the navigation tree on the left-hand pane of the NE Upgrade Task tab page, choose
Upgrade Task > eNodeB > Running, as shown in Figure 2.1.
Step 3 Select the created NE upgrade task on the NE Upgrade Task tab page. Right-click the task
and choose Manual Execute from the shortcut menu to activate the base station software, as
shown in Figure 3.1.
You can estimate the time required to activate the software by referring to 1.4.1Time Requirements for
Upgrade.
Step 4 View the progress displayed in the Details area on the NE Upgrade Task tab page.
You can select a base station to check the upgrade progress. The U2000 automatically
moves completed tasks to the Complete node. You can click Complete under Upgrade
Task in the navigation tree to view upgrade tasks that have been completed.
If the software activation fails, see 6.7How Do I Handle a Base Station Software
Activation Failure?
Step 5 (Optional) If the message "Failed to upgrade license" is displayed for an NE upgrade task you
have created , reload the license file after the upgrade. For details, see 3.4(Optional)
Reloading a License File for the eNodeB.
----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 SRAN11.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.
In the application style, click . On the displayed Application Center tab page,
double-click Software Management. From the main menu of the U2000 client, choose
NE License > Stand-Alone.
In the traditional style, choose License > NE License Management > Stand-Alone.
The Filter dialog box is displayed when the Stand-Alone License Management window is opened for
the first time. You can click OK to continue.
Step 3 In the displayed Load License File dialog box, click to select a path for saving the
license file.
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 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 been
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 Step 3 to Step 5 in 2.3.3Operations to Be
Performed Before an eNodeB License Upgrade.
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
In the application style, click . On the displayed Application Center tab page,
double-click Trace and Maintenance. From the main menu of the U2000 client, choose
Maintenance > MML Command.
In the traditional style, choose Maintenance > MML Command.
Step 2 Choose NE from the navigation tree on the left-hand side, and select an NE from the NE list.
Step 3 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
V100R011C10SPCXXX.
Patch Directory Name Leave it blank.
Delay-Supported Enter YES(Supply Delay-Supported File).
Download File
During this process, the progress is displayed in the MML command information pane.
Step 4 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
Figure 2.1 Comparing alarms generated before and after the upgrade
Step 3 Click YES in the displayed Confirm dialog box and specify a path for saving the report.
The U2000 automatically exports the alarms generated before the upgrade, alarms generated
after the upgrade, and alarm comparison results. The exported data is saved into three .csv
files.
Click View to view the report.
Check the alarm comparison result to check whether the following criteria are met:
The base station has not generated major or severe alarms for 15 minutes after the
upgrade.
The alarms that are expected to be cleared in the target version are cleared.
The alarms that are not expected to be cleared in the target version are not cleared.
No new alarm is introduced into the target version.
----End
Figure 2.1 Comparing cell status before and after the upgrade
Step 3 Click YES in the displayed Confirm dialog box and specify a path for saving the report.
The U2000 automatically exports data that contains the cell status before the upgrade, the cell
status after the upgrade, and the cell status comparison results. The exported data is saved into
three .csv files.
Click View to view the report.
If the cell status is abnormal after the upgrade, handle any 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
The KPIs do not fluctuate noticeably within one measurement period (usually 30 or 60
minutes) after the upgrade when compared with the KPIs in the same period the week before
the upgrade. Table 1.1 lists the KPIs to be compared.
To prevent major problems following an upgrade, collect the KPIs described in Table 1.1
every hour for 24 hours after the upgrade, and compare these KPIs with those collected in the
same periods the week before the upgrade.
In the application style, click . On the displayed Application Center tab page,
double-click Software Management. From the main menu of the U2000 client, choose
Upgrade > NE Upgrade Task Management.
In the traditional style, choose Software > NE Upgrade Task Management.
Step 2 In the NE Upgrade Task dialog box, click Create in the upper left-hand corner. In the
displayed drop-down list, choose eNodeB.
Step 3 In the displayed eNodeB-NE Upgrade Wizard [1/3] dialog box shown in Figure 3.1, set the
parameters as follows:
1. Enter a task name in Task Name or retain the default setting. (The length of the task
name cannot exceed 60 characters.)
2. Set Upgrade type to Rollback.
3. In the Available NEs area, select the NEs to be rolled back.
For a multimode base station, if version verification fails, contact Huawei technical support
for a new rollback policy. If a forced rollback is required despite the verification failure,
perform a forced rollback by referring to 6.2How Do I Enable the Forced Upgrade Function
for a Multimode Base Station?
Step 7 Check the rollback information, and then click Finish to start the rollback.
Step 8 In the navigation tree on the left-hand side of the NE Upgrade Task tab page, choose
Upgrade Task > eNodeB > Running. Then, check the software package download status and
progress in the Details area.
If the progress reaches 100%, the base station software is activated and restarted
successfully. The upgrade complete information is displayed (Upgrade Task> eNodeB
> Complete).
If the progress does not reach 100% and a failure message is displayed, the rollback fails.
Step 9 (Optional) After the version rollback from BTS3900 V100R011C10SPCXXX, reload the
backup license file if the new license file was loaded during the upgrade. For details about
how to reload a license file, see 3.4(Optional) Reloading a License File for the eNodeB.
----End
After the software version is rolled back to a source version earlier than SRAN11.1, the names of
new alarms and events in SRAN11.1 will be displayed as Undefined on the LMT.
After an eNodeB in BTS3900 V100R011C10SPCXXX is rolled back to a source version earlier than
SRAN10.0, there is a low possibility that ALM-26200 Board Hardware Fault is reported on the
LBBPc. If the alarm cannot be cleared within 10 minutes, run the RST BRD command to reset the
LBBPc to resume services.
6 FAQs
In the application style, click . On the displayed Application Center tab page,
double-click Trace and Maintenance, choose Maintenance > MML Command.
In the traditional style, choose Maintenance > MML Command.
Step 2 Choose NE from the navigation tree on the left-hand side, and select an NE from the NE list.
Step 3 Enter the SET LOADCTRL command in the Command Input text box. Set the parameters
Load Control Set this parameter to YES(Set Control Flag) or NO(Cancel Control
Flag Flag).
NOTE
To grant loading control rights to the LTE mode, select YES(Set Control
Flag). To grant loading control rights to the GSM/UMTS/WiMAX mode,
select NO(Cancel Control Flag).
For details,V100R011C10SPCXXX 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.
Parameter Setting
Peer Software Enter the running version on the peer main control board.
Version NOTE
To query the running version of the peer mode, run the DSP LOADCTRL
command.
Control Mode If the base station is a UMTS+LTE base station, set this parameter to
UL.
If the base station is a GSM+LTE base station, set this parameter to GL.
If the base station is a GSM+UMTS+LTE base station, set this
parameter to UL and GL. Note that this can be done by setting them
individually in two separate sessions. The setting sequence can be
reversed.
If the base station is a Wimax+LTE base station, set this parameter to
WL.
TL indicates a TD-SCDMA+LTE TDD base station, the LTE FDD
mode does not use loading control rights.
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 to be upgraded.
Step 8 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.
----End
In the application style, click . On the displayed Application Center tab page,
double-click Software Management.
In the traditional style, choose Software > Software Management Expert.
Step 2 Click Create Project.
Step 3 In the displayed Create Project dialog box, click Select from OSS Server.
Step 4 In the displayed Select Target Version dialog box, check the NE types in the NE Type
column following the Version column to determine whether the upgrade software package is
an SRAN package or a single-mode package. If the displayed field contains different RATs,
an SRAN package is used, as shown in Figure 4.1. If the displayed field contains only one
RAT, a single-mode package is used.
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.
Connection Mode are the same as those in Figure 2.1. If they are not, modify the settings and
ensure that they are the same as those in this figure.
----End
1 Software on the base station Query the software management status by running
is being updated, which the DSP SOFTSTATUS command. If the software
affects the software upgrade. status of the base station is not Idle, then a process
such as software supplementation or activation is
in progress. You can continue with the upgrade
operation only after the current process ends.
2 A board or the base station is Check for the EVT-26212 Board Startup event. If
reset, interrupting the it was generated, wait 10 minutes for the board to
operation. become functional again.
A Appendix
Cell Name
Cell ID
Remarks
Verified By
(signature)
2G 2nd Generation
3G 3rd Generation
A
AAL2 ATM Adaptation Layer Type 2
AMR Adaptive Multirate
ATM Asynchronous Transfer Mode
B
BAM Back Administration Module
BBU Baseband Unit
BCCH Broadcast Control Channel
BSC Base Station Controller
BTS Base Transceiver Station
C
CANBUS Controller Area Network BUS
CB Configuration Baseline
CCU Cabinet Control Unit
CDMA Code Division Multiple Access
CME Configuration Management Express
Co-MPT -
D
DRFU Double Radio Frequency Unit
DRRU Double Remote Radio Unit
E
eGBTS -
EGPRS Enhanced General Packet Radio Service
EMU Environment Monitoring Unit
eNodeB E-UTRAN NodeB
E-RAB E-UTRAN Radio Access Bearer
ESN Electronic Serial Number
F
FDD Frequency Division Duplex
FMU Fan Monitor Unit Interface Board
FTP File Transfer Protocol
G
GATM GSM Antenna and TMA Control Module
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
GUI Graphical User Interface
H
HSDPA High Speed Downlink Packet Access
HSPA High Speed Packet Access
I
ID Identity
IMA Inverse Multiplexing over ATM
IP Internet Protocol
IPoA IP over ATM
IU Information Unit
K
KPI key Performance Indicator
L
LBBP LTE Baseband Process Unit
LMPT LTE Main Processing and Transmission Unit
LMT Local Maintenance Terminal
LTE Long Time Evolution
M
MBTS Multimode Base Station
MML Man-Machine Language
MRFU Multimode Radio Frequency Unit
MRRU Multi-carrier Remote Radio Unit
N
NodeB -
O
OM Operation and Maintenance
OMC Operation and Maintenance Center
P
PDP Packet Data Protocol
PMU Power Monitoring Unit
PS Packet Switched
R
RAB Radio Access Bearer
RLC Radio Link Control
RNC Radio Network Controller
RRC Radio Resource Control
RRU Remote Radio Unit
RSCP Received Signal Code Power
RSL Radio Signal Link
RTWP Received total Wideband Power
S
SDCCH Standalone Dedicated Control Channel
SIM Subscriber Identity Module
SMT Site Maintenance Terminal system
T
TCH Traffic Channel
TCHF Full-rate Traffic Channel
TCHH Half-rate Traffic Channel
TDD time division duplex
TCU Temperature Control Unit
TDM Time Division Multiplexing
U
UBRI Universal Baseband Radio Interface unit
UCIU Universal Cascaded Interface Unit
UE user equipment
UMPT universal main processing and transmission unit
UMTS Universal Mobile Telecommunications System
UNI User-to-network Interface
USCU Universal Satellite Card and Clock Unit
UTRP Universal Transmission Processing Unit
V
VoIP voice over Internet Protocol
W
WCDMA Wideband Code Division Multiple Access