c05 Bts3812e v100r008c01b072 Upgrade GuideC05 BTS3812E V100R008C01B072 Upgrade Guide

BTS3812E-BTS3812A-BTS12AE V100R008C01B072 Version Upgrade Guide
BTS3812E-BTS3812ATS3812E-BTS3812ABTS3812AE V100R008C01B072
Upgrade Guide
HUAWEI TECHNOLOGIES CO., LTD.

December, 2013
Contents
1 Preparations for Upgrade.............................................................1
1.1 Elementary Preparation Before Upgrading.............................................................................................................1
1.1.1 Preparing Software Needed...............................................................................................................................1
1.1.2 Preparing Hardware...........................................................................................................................................1
1.1.3 Preparing Upgrade Tool.....................................................................................................................................1
1.1.4 Preparing Data...................................................................................................................................................2
1.1.5 Points for Attention............................................................................................................................................2
1.1.6 Upgrading License.............................................................................................................................................4
1.1.7 Checking BootRom...........................................................................................................................................5
1.1.8 Checking Current Login Account......................................................................................................................6
1.1.9 Obtaining Files for Upgrade..............................................................................................................................6
1.1.10 Preparing Patch Versions of the Target Version...............................................................................................7
1.1.11 Test Before Upgrade........................................................................................................................................7
1.2 Other Preparations...................................................................................................................................................7
1.2.1 Checking Preparations of Versions, Software, and Documents........................................................................7
1.2.2 Determining Network Topology........................................................................................................................8
1.2.3 Recording States of Special Services................................................................................................................9
2 Upgrade Operations...................................................................10
2.1 Upgrade Flow........................................................................................................................................................10
2.2 Upgrade Flow........................................................................................................................................................14
3 Upgrading the NodeB from the M2000.........................................18

3.1 Checking Equipment Running Before Upgrade....................................................................................................18
3.2 Installing the M2000 Mediation Version...............................................................................................................19
3.3 Backing Up Data...................................................................................................................................................19
3.4 Checking NodeB File Server Settings...................................................................................................................19
3.5 Upgrading the NodeB............................................................................................................................................21
3.5.1 Uploading the BootRom and Flash Software Package to M2000 Server........................................................21
3.5.2 Downloading the BootRom and Flash Software Packages to the NodeB.......................................................24
3.5.3 Activating the NodeB BootRom and Flash Software Versions.......................................................................26
3.5.4 Verifying the Upgrade......................................................................................................................................30
3.5.5 Upgrading the LMT.........................................................................................................................................30
3.5.6 Finishing the Upgrade ....................................................................................................................................30
Issue 1.00
Huawei Technologies Proprietary
Page i of 57
4 Upgrading the NodeB from the LMT.............................................31

4.1 Checking Equipment Running Before Upgrade....................................................................................................31
4.2 Upgrading the LMT...............................................................................................................................................32
4.3 Backing Up the Data Configuration File...............................................................................................................32
4.4 Upgrading the NodeB BootRom...........................................................................................................................32
4.5 Upgrading the NodeB Software............................................................................................................................34
4.6 Verifying the Upgrade............................................................................................................................................37
4.7 Finishing the Upgrade...........................................................................................................................................37
5 Falling Back the NodeB Version...................................................38

5.1 Falling Back the NodeB Version through the LMT...............................................................................................38
5.1.1 Falling Back the BootROM Version................................................................................................................38
5.1.2 Falling Back the Data Configuration File........................................................................................................38
5.1.3 Falling Back the NodeB Software...................................................................................................................39
5.2 Falling Back the NodeB Version Through the M2000 Client...............................................................................39
6 Handling After the Upgrade........................................................40

6.1 Refreshing Equipment Archives............................................................................................................................40
6.2 Setting the License.................................................................................................................................................40
7 Upgrade Verification...................................................................41
7.1 Verification Checklist............................................................................................................................................41
7.2 Checking Equipment Panel States.........................................................................................................................41
7.3 Checking Software Version Information...............................................................................................................42
7.4 Checking Alarm Information.................................................................................................................................43
7.5 Dialing Test for Basic Services..............................................................................................................................43
7.6 Verifying Network Problems.................................................................................................................................43
7.7 Verifying New Features.........................................................................................................................................43
7.8 Checking Equipment Running Status....................................................................................................................44
7.9 Confirming the CB................................................................................................................................................44
8 FAQ........................................................................................... 45
8.1 FAQ Table..............................................................................................................................................................45
8.2 FAQ1......................................................................................................................................................................45
8.3 FAQ2......................................................................................................................................................................46
8.4 FAQ3......................................................................................................................................................................48
8.5 FAQ4......................................................................................................................................................................48
8.6 FAQ5......................................................................................................................................................................50
8.7 FAQ6......................................................................................................................................................................50
9 Appendix................................................................................... 53
9.1 Upgrade Preparation Record.................................................................................................................................53
Upgrade Data Sheet.....................................................................................................................................................55
9.2 Dialing Test after NodeB Upgrade........................................................................................................................56
Issue 1.00
Page ii of 57
Figures
Flow chart for upgrading the NodeB through the M2000 ..................13
Flow chart for upgrading the NodeB through the LMT......................13
Flow chart for upgrading the NodeB through the M2000 ..................17
Flow chart for upgrading the NodeB through the LMT......................17
File Server Setting window.............................................................20
File Server Batch Set......................................................................21
Upload software package from GUI to server...................................22
Select the directory containing the software package......................23
Choose the directory......................................................................23
Select uploading file: path being selected.......................................24
NE Upgrade Wizard : select the upgrade type and the NodeBs to
download the package...................................................................25
NE Upgrade Wizard: select the versions to download.......................26
NE Upgrade Wizard : select the upgrade type and the NodeBs to
activate the package......................................................................28
NE Upgrade Wizard: select the versions to be activated...................29
Start to upgrade the BootRom........................................................33
Upgrade the BootRom....................................................................34
Start to upgrade the software........................................................35
Upgrade the software....................................................................36
Software update result...................................................................47
Issue 1.00
Page iii of 57
Tables
Multiple NodeBs simultaneously downloading software from the
M2000............................................................................................. 2
Duration for M2000 to download NodeB software or BootROM in
typical IPoA bandwidth....................................................................2
Maximum number of the NodeBs that can be simultaneously activated
from the M2000............................................................................... 3
Comparison between licenses for 3812E of different versions.............4
Corresponding versions and necessity for upgrading the BootRom.....5
Checklist of preparations before the upgrade....................................8
Record of special services running on the network............................9
Upgrading the NodeB on the M2000................................................10
Upgrading the NodeB on the LMT....................................................11
Upgrading the NodeB on the M2000................................................14
Upgrading the NodeB on the LMT....................................................15
Checklist for equipment operation..................................................18
Verifying the upgrade....................................................................30
Checklist for equipment operation..................................................31
Verifying the upgrade....................................................................37
Verification checklist......................................................................41
Checklist for equipment panel states..............................................41
Checklist for software version information......................................42
Verifying network problems............................................................43
Verification of new features............................................................43
FAQ table......................................................................................45
Troubleshooting steps and collected data........................................49
Issue 1.00
Page iv of 57
Comparison between regular download and download by configuration

..................................................................................................... 51
Methods of adding boards of new types to the NodeB......................52
Upgrade preparation record...........................................................53
Upgrade data sheet.......................................................................55
Dialing test after NodeB upgrade....................................................56
Issue 1.00
Page v of 57
Preparations for Upgrade
1.1 Elementary Preparation Before Upgrading

1.1.1 Preparing Software Needed
Software
Description
NodeB upgrade flash

software package
NodeB upgrade
BootRom software
package
A self-extracting file that containing the flash and BootRom

software packages required for upgrade.
LMT installation
program
It is a self-extracting file that consists of the LMT installation

program.
M2000 Mediation
installation program
It consists of the installation program and related documents.
Administrator password
of the LMT PC
It is used to log in to the PC that is loaded with the LMT.
Login password of the

M2000 server
FTP/Telnet
To upload the M2000 mediation installation package to the

M2000 server, the user name and password of FTP, or at least
the upload permission, to the M2000 server is required.
To install the M2000 mediation, the user name and password of
Telnet, or at least the adaptation layer installation permission, to
the M2000 server is required.
1.1.2 Preparing Hardware

Ensure that the hardware components that should be added after the upgrade are readily
prepared."
1.1.3 Preparing Upgrade Tool
Issue 1.00
Mobile phones for dial test
SIM cards
Test vehicles
Page 1 of 57
1.1.4 Preparing Data

If the data should be reconfigured, ensure that the data is reconfigured before the upgrade and
that the NodeB works properly. For details about the reconfiguration, refer to RAN
Reconfiguration Guide.
1.1.5 Points for Attention

Pay attention to the following precautions during upgrade:
1). Upgrade NodeB software through:
M2000
The M2000 allows you to upgrade multiple NodeBs simultaneously, and is widely used in the
upgrade.
LMT
The LMT enables you to upgrade only one NodeB for each time, and is supplementary for the
upgrade.
Note:
This guide describes how to upgrade NodeBs controlled by one RNC from the M2000. If there are
multiple RNCs, follow the procedure below to upgrade NodeBs controlled by different RNCs according
to field applications.
2). Multiple NodeBs can simultaneously download the software package or BootROM
software from the M2000 under the specified IPoA bandwidth as follows:
Figure 1.1 Multiple NodeBs simultaneously downloading software from the M2000
NodeB IPoA Bandwidth
Number of NodeBs
64 kbit/s
80
128 kbit/s
40
3). The duration for M2000 to download NodeB software or BootROM in typical IPoA
bandwidth is as follows:
Figure 1.2 Duration for M2000 to download NodeB software or BootROM in typical IPoA
bandwidth
Issue 1.00
NodeB
IPoA
Bandwidt
h
NodeB
Software
NodeB
BootRom
Remarks
64K, VBR
3843
1143
The test is performed in 3 x 1

configurations. The actual
duration depends on factors
Page 2 of 57
such as the network

transmission quality, bandwidth
usage, and FTP server.
The duration listed is only for
your reference.
4). The maximum number of the NodeB software or BootROM software that can be
simultaneously activated from the M2000 is as follows:
Figure 1.3 Maximum number of the NodeBs that can be simultaneously activated from the
M2000
No.
Product
Product Version
Number of NodeBs
M2000
iManagerM2000V200R0
02C02B022 or later
versions
60
Abide by the following principles during the upgrade:

5). The upgrade procedure must be in strict compliance with the upgrade guide. No reverted
procedure is allowed.
6). During the upgrade, wait for the command response and check if the command is
executed before executing the next one. If the command fails, follow the instructions in
this guide.
7). Do not perform the following operations on NMPT when upgrading the NodeB:
Power off the NMPT

Manually reset the NMPT
Pull out or insert the NMPT
8). Do not perform the following operations on the NodeB when activating the BootROM:
Power off the NMPT

Manually reset the NMPT
Pull out or insert the NMPT
9). If a standby NMPT is available, check it before the upgrade.
The standby NMPT status is Available.

The standby NMPT does not automatically reset repeatedly.
The standby NMPT cannot be inserted or pulled out during the upgrade.
10). If the upgrade fails or the network performance seriously deteriorates in the dial test after
upgrade, fallback of version is recommended.
The fallback depends on the practical situations of the network and customers'
requirement. For details about how to perform the fallback, see 5"Falling Back the
NodeB Version".
Issue 1.00
Page 3 of 57
1.1.6 Upgrading License

If the previous functions should be maintained, you do not have to apply for a new license for
the NodeB to be upgraded from V100R006 or V100R007 to the current version.
If the new functions of HSUPA, MBMS, and power sharing in the NodeB of V100R008 are
required, you need to apply for a new license file.
For details about how to apply for a license file, refer to license user guide.
Figure 1.4 Comparison between licenses for 3812E of different versions
Version
Before
Upgrade
Differences of
License Control Items
in Upgraded Version
Impact Without
New License
Related
Operation
V100R006
C02B080
New
features
Maximum number
of HSDPA users
Maximum number of
HSDPA users
iManagerM2000V20
0R003C01B063
HSDPA RRM
Package 1
Not restricted
iManagerM2000V20
0R003C01B063
Maximum number
of HS-PDSCH
codes
Not restricted
iManagerM2000V20
0R003C01B063
HSUPA
HSUPA not supported
iManagerM2000V20
0R005
MBMS
MBMS not supported
iManagerM2000V20
0R005
Power sharing
Power sharing not

supported
iManagerM2000V20
0R005
Removed
features
New
features
HSUPA
HSUPA not supported
iManagerM2000V20
0R005
V100R007
C03B061
MBMS
MBMS not supported
V100R007
C03B061
iManagerM2000V20
0R005
Power sharing
Power sharing not

supported
iManagerM2000V20
0R005
Removed
features
New
features
V100R006
C03B090
V100R007
C03B040
V100R007
C03B043
V100R007
C03B051
V100R007
C03B062
V100R008
C01B040
Issue 1.00
15 codes per cell
Page 4 of 57
Version
Before
Upgrade
Differences of
License Control Items
in Upgraded Version
Impact Without
New License
Related
Operation
V100R008
C01B050
Removed
features
V100R008
C01B060
V100R008
C01B062
V100R008
C01B070
V100R008
C01B071
V100R008
C01B072
1.1.7 Checking BootRom

You need to determine whether or not to upgrade the BootRom based on the target version
and the information. Figure 1.5 describes the corresponding versions and necessity for
upgrading the BootRom.
Figure 1.5 Corresponding versions and necessity for upgrading the BootRom
Version Before
Upgrade
Issue 1.00
BootRO
M
Upgrade
Required
Recommended BootRom
Version
BTS3812E-BTS3812ABTS3812AE
V100R008C01B072
BTS3812EBTS3812AV100R008C01B072
V100R008C01B071
BTS3812EBTS3812AV100R008C01B072
V100R008C01B070
BTS3812EBTS3812AV100R008C01B072
V100R008C01B062
BTS3812EBTS3812AV100R008C01B072
V100R008C01B060
BTS3812EBTS3812AV100R008C01B072
BTS3812EBTS3812AV100R008C01B050
BTS3812EBTS3812AV100R008C01B072
Page 5 of 57
Version Before
Upgrade
BootRO
M
Upgrade
Required
BTS3812EBTS3812AV100R008C01B040
BTS3812EBTS3812AV100R007C03B062
BTS3812EBTS3812AV100R007C03B061
BTS3812EBTS3812AV100R007C03B060
BTS3812EBTS3812AV100R007C03B041
BTS3812EBTS3812AV100R007C03B040
BTS3812EBTS3812AV100R006C02B090
BTS3812EBTS3812AV100R006C02B080
Recommended BootRom
Version
BTS3812EBTS3812AV100R008C01B072
1.1.8 Checking Current Login Account

Ensure that you log in to the Windows 2000 or Windows XP system as administrator. If not,
log out and then log in to the system as administrator.
Ensure that you have the permission to upload files to the M2000 server with the user name
and password of the M2000 server FTP. If you do not have the permission, obtain the proper
user name and password so that you can upload files to the M2000 server.
Ensure that you have the permission to install the adaptation layer on the M2000 server with
the user name and password of the M2000 server Telnet. If you do not have the permission,
obtain the proper user name and password so that you can install the adaptation layer on the
M2000 server.
1.1.9 Obtaining Files for Upgrade

To obtain the files for the upgrade, perform the following steps:
Obtain the flash software package
Get the files corresponding to BTS3812E-BTS3812A-BTS3812AE V100R008C01B072 from

the server. Those files consist of the installation file of the NodeB OM system, NodeB flash
software, and M2000 mediation version file.
Decompress the version file to the destination folder
Double-click the four files respectively to enable the self-extracting. The destination folder is
D:\NodeBVer or you may rename that folder. For easy description, it is assumed that those
Issue 1.00
Page 6 of 57
files are decompressed to D:\NodeBVer under which there are four folders named
BTS3812E-12AC-12AE-BTS3812AV100R008C01B072, LMT_NodeB_BTS3812EBTS3812A-BTS3812AE V100R008C01B072, CME_BPL_BTS3812E-BTS3812ABTS3812AEV100R008C01B072 BPL and M2000_Mediation.
(1) Folder D:\NodeBVer\BTS3812E-12AC-12AE-BTS3812AV100R008C01B072
contains the NodeB flash and BootRom software package.
(2) Folder D:\NodeBVer\LMT_NodeB_BTS3812E-BTS3812A-BTS3812AE
V100R008C01B072 contains the LMT installation files.
(3) Folder D:\NodeBVer\CME_BPL_BTS3812E-BTS3812A-BTS3812AEDBS3800V100R008C01B072 BPL contains the CME BPL installation files, the CME PBL
ought to install based on the version of the WRAN CM Express V100R003C01B092.
(4) Folder D:\NodeBVer\M2000_Mediation contains the M2000 mediation installation
files.
1.1.10 Preparing Patch Versions of the Target

Version
This process is optional, depending on the need of the office.
If the office needs to upgrade corresponding version patches, get them from the technical
support website.
1.1.11 Test Before Upgrade

Perform a test before the upgrade.
For the test items, refer to the Dialing Test after NodeB Upgrade. Note down related traced
messages.
Check the upgrade memorandum of the specified version and check whether special settings
are required.
1.2 Other Preparations

1.2.1 Checking Preparations of Versions, Software,
and Documents
You need also check the following items before the upgrade:
Issue 1.00
Office for the upgrade
Upgrade schedule
Upgrade requirements from the operator
Current version to be upgraded
Target version after the upgrade
Equipment data information
Other related information required in the upgrade
Page 7 of 57
Before the upgrade, refer to Figure 1.6 for preparations.

Figure 1.6 Checklist of preparations before the upgrade
Preparation
Remark
Location of the equipment to be

upgraded
Upgrade time and duration allowed by
the operator
Upgrade requirements from the operator
Type and model of the NodeB to be
upgraded
Number of NodeBs to be upgraded
Target version after the upgrade
Current version of the M2000 server at
the operator side
Confirm how many patches have been installed

so far.
Current version of the RNC at the

operator side
Confirm how many patches have been installed

so far.
Current version of the CME at the

operator side
Current flash version of the NodeB at
the operator side
Current BootRom version of the NodeB
at the operator side
Data configuration file on the operator's
equipment
Back up the data configuration file.
Transmission network topology at the

operator side
Check whether the M2000 server should
be upgraded for synchronization
If it should be upgraded, contact engineers

responsible for the M2000 server to prepare the
upgrade.
Check whether the RNC should be

upgraded for synchronization

responsible for the RNC to prepare the upgrade.
Check whether the CME should be

upgraded for synchronization

responsible for the CME to prepare the upgrade.
Other data that should be recorded
1.2.2 Determining Network Topology

Get ready the transmission network topology and the equipment room layout in the site for
upgrade. This enables the support engineers to understand the networking states properly.
Issue 1.00
Page 8 of 57
1.2.3 Recording States of Special Services

Before the upgrade, record the states of special services that are currently running on the
network by referring to Figure 1.7.
Figure 1.7 Record of special services running on the network
Service
Name
Is Using
CMB
Not in use
Enabled
Notes
[]
[]
Applicable only to Hong Kong at

present
Supported after this upgrade [ ]

HSDPA
Not in use
Enabled
[]
[]

HSUPA
Not in use
Enabled
[]
[]

IP RAN
Not in use
Enabled
[]
[]

License
Not in use
Enabled
[]
[]

MBMS
Not in use
Enabled
[]
[]

Power
sharing
Not in use
Enabled
[]
[]
Issue 1.00
Page 9 of 57
Upgrade Operations
2.1 Upgrade Flow

Upgrade NodeB software through:
M2000
upgrade.
LMT
upgrade.
Figure 1.8 lists steps for upgrading the NodeB on the M2000.
Figure 1.8 Upgrading the NodeB on the M2000
Issue 1.00
Ste
p
Description
Refer to
Time
(hour)
Check running status of the

equipment before the upgrade.
3.1Checking Equipment
Running Before Upgrade
5min
Install the M2000 Mediation

version.
3.2Installing the M2000

Mediation Version
5min
Back up the data configuration

file.
3.3Backing Up Data
Check the NodeB file server

settings.
3.4Checking NodeB File

Server Settings
5min
Upload the BootRom and flash

software package to M2000
server.
3.5.1Uploading the BootRom

and Flash Software Package to
M2000 Server
1min
Download the BootRom and flash

software packages to the NodeB.
3.5.2Downloading the
BootRom and Flash Software
Packages to the NodeB
62minIPo
A
Bandwidth
128K
Activate the BootRom and flash

software versions.
3.5.3Activating the NodeB

Version
13min
Page 10 of 57
Ste
p
Description
Refer to
Time
(hour)
Verify the upgrade.
3.5.4Verifying the Upgrade
10min
Upgrade the LMT.
3.5.5Upgrading the LMT
10min
10
Finish the upgrade.
3.5.6Finishing the Upgrade
--
Figure 1.9 lists steps for upgrading the NodeB on the LMT.
Figure 1.9 Upgrading the NodeB on the LMT
Step
Description
Refer to
Time
(hour)

5min
Upgrade the LMT.
4.2Upgrading the LMT
3min
Back up the data.
4.3Backing Up the Data

Configuration File
Upgrade the NodeB BootROM.
4.4Upgrading the NodeB

BootRom
30minIPo
A
Bandwidth
128K
Upgrade the NodeB software.

Software
37minIPo
A
Bandwidth
128K
Verify the upgrade.
4.6Verifying the Upgrade
5min
Complete the upgrade.
4.7Finishing the Upgrade
--
Figure 1.1 show the upgrade flow through the M2000.
Issue 1.00
Page 11 of 57
Confirm upgrade office
Prepare the hardware and

software
Checking Equipment Running
Status before Upgrade
Installing the M2000
Mediation Version
Backing Up the Data
Configuration File
Check NodeB File Server
Settings
Uploading Software Package
to M2000 Server
Download the BootROM and

Software package to NodeB
No
All NodeB
downloading
Complete?
Yes
Act the BootROM and

Software Version
Verifying the Upgrade

No
succeed?
No
Yes
Falling Back the NodeB

Version
All NodeB activating

Complete?
Yes
Upgrading the LMT
Finishing the Upgrade
Issue 1.00
Page 12 of 57
Figure 1.1 Flow chart for upgrading the NodeB through the M2000
Figure 1.9 shows the upgrade flow through the LMT.

Confirm
upgrade office
Prepare the
hardware and
software
Check equipment
running status before
upgrade
Upgrade
the LMT
Back up
the data
Upgrade the
BootRom on the
NodeB
Upgrade the flash
software on the
NodeB
Verify the
upgrade
Succeed
?
Yes
Finish the
upgrade
No
Fall back the
NodeB version
Figure 1.2 Flow chart for upgrading the NodeB through the LMT
Issue 1.00
Page 13 of 57
2.2 Upgrade Flow

Upgrade NodeB software through:
M2000
upgrade.
LMT
upgrade.
Figure 1.8 lists steps for upgrading the NodeB on the M2000.
Figure 1.10 Upgrading the NodeB on the M2000
Ste
p
Description
Refer to
Time
(hour)

5min
Install the M2000 Mediation

version.
3.2Installing the M2000

Mediation Version
5min
Back up the data configuration

file.
3.3Backing Up Data
Check the NodeB file server

settings.
3.4Checking NodeB File

Server Settings
5min
Upload the BootRom and flash

software package to M2000
server.
3.5.1Uploading the BootRom

and Flash Software Package to
M2000 Server
1min
Download the BootRom and flash

software packages to the NodeB.
3.5.2Downloading the
62minIPo
A
Bandwidth
128K
Activate the BootRom and flash

software versions.
3.5.3Activating the NodeB

Version
13min
Verify the upgrade.
3.5.4Verifying the Upgrade
10min
Upgrade the LMT.
3.5.5Upgrading the LMT
10min
10
Finish the upgrade.
3.5.6Finishing the Upgrade
--
Figure 1.9 lists steps for upgrading the NodeB on the LMT.
Issue 1.00
Page 14 of 57
Figure 1.11 Upgrading the NodeB on the LMT

Step
Description
Refer to
Time
(hour)

5min
Upgrade the LMT.
4.2Upgrading the LMT
3min
Back up the data.
4.3Backing Up the Data

Configuration File
Upgrade the NodeB BootROM.

BootRom
30minIPo
A
Bandwidth
128K
Upgrade the NodeB software.

Software
37minIPo
A
Bandwidth
128K
Verify the upgrade.
4.6Verifying the Upgrade
5min
Complete the upgrade.
4.7Finishing the Upgrade
--
2.1.1 I. IStep 1Figure 1.1 show the upgrade flow through the M2000.
Issue 1.00
Page 15 of 57
Confirm upgrade office
Prepare the hardware and

software
Checking Equipment Running
Status before Upgrade
Installing the M2000
Mediation Version
Backing Up the Data
Configuration File
Check NodeB File Server
Settings
Uploading Software Package
to M2000 Server
Download the BootROM and

Software package to NodeB
No
All NodeB
downloading
Complete?
Yes
Act the BootROM and

Software Version
Verifying the Upgrade

No
succeed?
No
Yes
Falling Back the NodeB

Version
All NodeB activating

Complete?
Yes
Upgrading the LMT
Finishing the Upgrade
Issue 1.00
Page 16 of 57
Figure 1.1 Flow chart for upgrading the NodeB through the M2000
Figure 1.9 shows the upgrade flow through the LMT.

Confirm
upgrade office
Prepare the
hardware and
software
Check equipment
running status before
upgrade
Upgrade
the LMT
Back up
the data
Upgrade the
BootRom on the
NodeB
Upgrade the flash
software on the
NodeB
Verify the
upgrade
Succeed
?
Yes
Finish the
upgrade
No
Fall back the
NodeB version
Figure 1.2 Flow chart for upgrading the NodeB through the LMT
Issue 1.00
Page 17 of 57
Upgrading the NodeB from

the M2000
3.1 Checking Equipment Running Before

Upgrade
The table below lists the check items for equipment operation before upgrading the
BTS3812E-BTS3812A-BTS3812AE version to V100R008C01B072.
Figure 1.12 Checklist for equipment operation
Item
NodeB
Result
Conclusion
Checking active alarm data: Check all

alarms on the NodeBs for upgrade on
the M2000 client. Clear the alarms
according to the alarm online help.
Querying cell status: Execute DSP
LOCELL:; on the M2000 client, and
then check the state of all the NodeB
cells for upgrade.
Check if all the local and logical cells
configured are available. If not, refer
to the troubleshooting guide.
Checking data consistency: Execute
CHK DATA:; on the M2000 client,
and then check the consistency
between the NodeB FLASH data and
the service data.
If the two are not consistent, reset the
NodeB.
PC
Issue 1.00
Checking multiple IP addresses: If the

operating system running on the
computer loaded with the LMT is the
Windows 98, this computer cannot be
Page 18 of 57
Item
Result
Conclusion
configured with three or more IP

addresses. Otherwise, it causes low
file transmission rate or disconnection
between the LMT and the NodeB. If
three or more IP addresses are
configured, delete the redundant
addresses.
3.2 Installing the M2000 Mediation Version

The M2000 Mediation version is applicable to the adaptation layer. The version is used by
M2000 to identify different NodeB networking modes with different versions. The software
must be installed to the M2000 server with the correct M2000 Mediation version. The M2000
Mediation version related to the BTS3812E-BTS3812A-BTS3812AE V100R008C01B072
(3812E English version) is stored in the directory of D:\NodeBVer\M2000_Mediation\
iManagerM2000(NodeB3812E_MATCH_ENG)V200R005C01B024. Therefore, install the
M2000 Mediation version by following the instructions in Installation Guide to
iManagerM2000(NodeB3812E_MATCH_ENG)V200R005C01B024 at the adaptation layer.
3.3 Backing Up Data

You dont need to back up the data configuration file.
3.4 Checking NodeB File Server Settings

Before upgrading the NodeB version, check the file server settings of all NodeBs as follows:
1). Start and log in to the M2000 client.
2). Choose Software > File Server Setting in the M2000 client interface.
3). Select the Root > NodeB > RNC1 > NodeB3812E node on the left pane in the File
Server Setting window. (The RNC name is the RNC which includes the all NodeBs you
want to upgrade. For example, RNC1, as shown in Figure 1.1.)
4). Check if the settings of all the NodeBs displayed in the right pane of the File Server
Setting window are correct.
Note:
For more details about the introduction, functions and configuration of the NodeB file server, see
8.6"FAQ5".
Issue 1.00
Page 19 of 57
Figure 1.1 File Server Setting window

If the file server settings of a NodeB are incorrect, change the settings as follows:
2). Choose Software > File Server Setting in the M2000 client interface.
3). Select all NodeBs to be set to the same File Server Name, and then right-click to select
the Set from the shortcut menu.
4). Set values in the File Server Batch Set window.
Issue 1.00
Page 20 of 57
Figure 1.2 File Server Batch Set
3.5 Upgrading the NodeB

3.5.1 Uploading the BootRom and Flash Software
Package to M2000 Server
To upload the BootRom software package to the M2000 server, perform the following:
2). Choose Software > File Transfer Wizard in the M2000 client interface. As shown in
Figure 1.1:
Issue 1.00
Select From GUI To Server in the Direction

Select OMC Server/NodeB/NodeB3812E/Software in the Server Path as show in
Figure 1.1, Then click Next.
Page 21 of 57
Figure 1.1 Upload software package from GUI to server

3). In the Select Software File dialog box, click the Select to add the directory containing
the software package, as shown in Figure 1.2 and Figure 1.3
Issue 1.00
Page 22 of 57
Figure 1.2 Select the directory containing the software package
Figure 1.3 Choose the directory

4). Click Finish in the Figure 1.4, the file transmission status (Percent and Status) is
shown in the FTP task.
Issue 1.00
Page 23 of 57
Figure 1.4 Select uploading file: path being selected

5). If the file transmission status is Succeeded, the software package is transferred from
GUI to server successfully.
6). If the file transmission status is error, it indicates that the file transmission fails. Repeat
steps 1) to 4). If it still fails, contact Huawei technical support engineers for
troubleshooting.
3.5.2 Downloading the BootRom and Flash Software

To download the BootRom and software packages to the NodeB, perform the following:
2). Choose Software > NE Upgrade Wizard > Upgrade NodeB in the M2000 client
interface.
3). In the windows of NE Upgrade Wizard, select Upgrade BootRom And Software in
the Upgrade type, and select the NodeBs for upgrade by pressing your mouse or
pressing Ctrl while clicking your mouse. before the NodeB indicates that the NodeB
is selected. before the NodeB indicates that the NodeB is not selected. Click > or
>> to add the selected NodeBs to the right pane.
Issue 1.00
Page 24 of 57

Note
If you click
, all the selected NEs in the left pane are added to the right pane. If you click
, all the NEs in the left pane are added to the right pane.
If you click
, all the selected NEs in the right pane are moved to the left pane. If you click
all the NEs in the right pane are moved to the left pane.
Figure 1.1 NE Upgrade Wizard : select the upgrade type and the NodeBs to download the
package
4). Click Next.
The next NE Upgrade Wizard window is displayed, as shown in Figure 1.2.
5). In the window of NE Upgrade Wizard (Figure 1.2), select the following items:
Download BootROM
Download Software
Download by configuration (For information about why Download by configuration

is selected, refer to 8.7FAQ6.)
6). In the drop-down lists of BootRomVersion and SoftwareVersion, select the BootROM
and software versions for download. For example, select BTS3812E-12AC-12AEBTS3812AV100R008C01B072 in BootRomVersion and BTS3812E-12AC-12AEIssue 1.00
Page 25 of 57
BTS3812AV100R008C01B072 in SoftwareVersion.
Figure 1.2 NE Upgrade Wizard: select the versions to download

7). Click Finish.
The BootRom and software downloading is started.
8). Choose Software > Browser. Click the Immediately Task tab in the lower left part of
the window.
You may check the progress and status of the software downloading.
9). If the status displays that the BootRom and software downloading is complete, the
BootRom and software version are downloaded to the NodeB. If the status displays that
an error occurs, repeat steps 1 through 7. If the status still displays that an error occurs,
contact local Huawei office for technical support.
3.5.3 Activating the NodeB BootRom and Flash

Software Versions
To activate the BootROM and software versions, perform the following:
2). Choose Software > NE Upgrade Wizard > Upgrade NodeB in the M2000 client
interface.
Issue 1.00
Page 26 of 57
3). In the windows of NE Upgrade Wizard, select Upgrade BootRom And Software in
the Upgrade type, and select the NodeBs for upgrade by pressing your mouse or
pressing Ctrl while clicking your mouse. before the NodeB indicates that the NodeB
is selected. before the NodeB indicates that the NodeB is not selected. Click > or
>> to add the selected NodeBs to the right pane.
Issue 1.00
Page 27 of 57

Note
If you click
, all the selected NEs in the left pane are added to the right pane. If you click
, all the NEs in the left pane are added to the right pane.
If you click
, all the selected NEs in the right pane are moved to the left pane. If you click
all the NEs in the right pane are moved to the left pane.
Figure 1.1 NE Upgrade Wizard : select the upgrade type and the NodeBs to activate the package
Note:
As downloading software and activating software are performed separately, you need to repeat the
operations" when upgrading the NodeB. Thus, the NodeB software version can be downloaded to all
NodeBs that require upgrade. Then, perform the operations in this section to activate the software. Note
that all NEs selected, should be the NodeBs that has already finished downloading the software version.
Otherwise, the activation may fail.
4). Click Next.

The next NE Upgrade Wizard window is displayed, as shown in Figure 1.2
5). In the window of NE Upgrade Wizard (Figure 1.2), select the following items:
Issue 1.00
Page 28 of 57
Active BootROM
Active Software
6). In the drop-down lists of BootRomVersion and SoftwareVersion, select the BootROM
and software versions to be activated. For example, select BTS3812E-12AC-12AEBTS3812AV100R008C01B072 in BootRomVersion and BTS3812E-12AC-12AEBTS3812AV100R008C01B072 in SoftwareVersion.
Figure 1.2 NE Upgrade Wizard: select the versions to be activated

7). Click Finish.
The BootRom and software activating is started.
8). Choose Software > Browser. Click the Immediately Task tab in the lower left part of
the window.
You may check the progress and status of the software activating.
9). If the status displays that the BootRom and software activating is complete, the
BootRom and software version are activated to the NodeB. If the status displays that an
error occurs, repeat steps 1 through 7. If the status still displays that an error occurs,
contact local Huawei office for technical support.
Issue 1.00
Page 29 of 57
3.5.4 Verifying the Upgrade

Figure 1.13 Verifying the upgrade
Item
Instruction
Conclusio
n
Checking current
alarms
Check all the current alarms on the upgraded

NodeBs through the M2000 client, and
handle the alarms according to the alarm
online help.
Checking the cell

status
Execute DSP LOCELL:; on the M2000

client to check the status of all the NodeB
cells to be upgraded.

configured are available.
If yes, the upgrade succeeds.
If no, refer to the alarm online help.
Querying the
current NodeB
version
Execute LST VER:; on the M2000 client.

Then check that the current flash and
BootRom Version are all
V100R008C01B072.
Performing a
dialing test
Conduct the test by following the instructions

in Dialing Test after NodeB Upgrade.
Ensure that system services are not affected
after upgrading the NodeB.
3.5.5 Upgrading the LMT

To upgrade the NodeB LMT, perform the following:
1). Log in to the operating system on the computer with the privilege of an administrator.
2). Double-click Setup.bat under the directory of D:\NodeBVer\ LMT_NodeB_BTS3812EBTS3812A-BTS3812AE V100R008C01B072 to start installing the O&M system.
3). Install the NodeB O&M system with the default options.
The default installation directory is D:\HW LMT.
3.5.6 Finishing the Upgrade

If the NodeB is verified to be normal after the upgrade, the upgrade succeeds. Then delete the
following files under the directory of D:\NodeBVer:
Installation file of the NodeB O&M system
NodeB software package
M2000 Meditation version file
If the NodeB is verified to be abnormal after the upgrade and no exception is cleared, you
must fall back the version to restore the system.
Issue 1.00
Page 30 of 57
Upgrading the NodeB from

the LMT
Note:
The CPU overload alarm may occur during the following operations:
Downloading NodeB BootROM software package
Activating NodeB BootROM
Activating board BootROM
Downloading NodeB software package
Activating NodeB software
Activating board software
The alarm is automatically cleared after upgrade.
4.1 Checking Equipment Running Before

Upgrade
The table below lists the check items for equipment operation before upgrading the
BTS3812E-BTS3812A-BTS3812AE version to V100R008C01B072.
Figure 1.14 Checklist for equipment operation
Item
NodeB
Result
Conclusion
Checking active alarm data: Check

all alarms on the NodeBs for
upgrade on the M2000 client. Clear
the alarms according to the alarm
online help.
Querying cell status: Execute DSP
LOCELL:; on the LMT, and then
check the state of all the NodeB cells
for upgrade.
Check if all the local and logical
cells configured are available. If not,
refer to the troubleshooting guide.
Checking data consistency: Execute
CHK DATA:; on the LMT, and then
check the consistency between the
Issue 1.00
Page 31 of 57
Item
Result
Conclusion
NodeB FLASH data and the service

data.
If the two are not consistent, reset
the NodeB.
PC
Checking multiple IP addresses: If

the operating system running on the
computer loaded with the LMT is the
Windows 98, this computer cannot
be configured with three or more IP
addresses. Otherwise, it causes low
file transmission rate or
disconnection between the LMT and
the NodeB. If three or more IP
addresses are configured, delete the
redundant addresses.
4.2 Upgrading the LMT

To upgrade the NodeB LMT, perform the following:
1). Log in to the operating system on the computer with the privilege of an administrator.
2). Double-click Setup.bat under the directory of D:\NodeBVer\ LMT_NodeB_BTS3812EBTS3812A-BTS3812AE V100R008C01B072 to start installing the O&M system.
3). Install the NodeB O&M system with the default options.
The default installation directory is D:\HW LMT.
4.3 Backing Up the Data Configuration File

You dont need to back up the data configuration file.
4.4 Upgrading the NodeB BootRom

Note:
The exceptional reset of a board during the BootRom upgrade process may lead to damage on the
BootRom software or failure in starting the board. In this case, send the faulty board to Huawei for
maintenance.
If BootRom upgrade is not required, skip the procedure in this section.
To upgrade the NodeB BootRom, perform the following:

1). Choose Maintenance > Software Management in the left pane on the NodeB LMT.
Then double-click Software Upgrade.
Issue 1.00
Page 32 of 57
The Software Update window is displayed.
Figure 1.1 Start to upgrade the BootRom
2). Select BootRom software upgrade, and then click Next.

The BootRom Software Package Upgrade Flow is displayed.
3). Select Download BootRom Software Package and Activate NodeB BootRom
Software.
4). Enter the BootRom package path in the Directory Name box, for example,
D:\NodeBVer\BTS3812E-12AC-12AE-BTS3812AV100R008C01B072.
Issue 1.00
Page 33 of 57
Figure 1.2 Upgrade the BootRom
5). Click Next.

A dialog box is displayed, indicating the status and progress of upgrading BootRom.
After the BootRom package is activated, the boards that are activated and those fail to be
activated are listed.
6). If there are boards whose BootRom fails to be activated, refer to 8.2"FAQ1" "How to
handle the failure in activating the NodeB BootRom when upgrading the NodeB through
the LMT?"
Follow the steps below to continue the upgrade.
4.5 Upgrading the NodeB Software

To upgrade the NodeB software, perform the following:
Issue 1.00
Page 34 of 57
Figure 1.1 Start to upgrade the software
2). Select NodeB Software Upgrade, and then click Next.

3). Select Download NodeB Software Package, Activate NodeB, and Download by
Configuration (for information about Download by Configuration, refer to
8.7FAQ6).
4). Enter the NodeB software package path in Direction Name, for example,
D:\NodeBVer\BTS3812E-12AC-12AE-BTS3812AV100R008C01B072.
Issue 1.00
Page 35 of 57
Figure 1.2 Upgrade the software
5). Click Next.

A dialog box is displayed, indicating the status and progress of upgrading NodeB
software. After the NodeB software is activated, the boards that are activated and those
fail to be activated are listed.
6). If there are boards whose software fails to be activated, refer to 8.3"FAQ2" "How to
handle the failure in activating the NodeB software when upgrading the NodeB through
the LMT?".
Follow the steps below to continue upgrading.
Issue 1.00
Page 36 of 57
4.6 Verifying the Upgrade

Figure 1.15 Verifying the upgrade
Item
Instruction
Conclusio
n
Checking current
alarms
Check all the current alarms on the

upgraded NodeBs through the LMT, and
handle the alarms according to the alarm
online help.
Checking the cell

status
Execute DSP LOCELL:; on the LMT to

check the status of all the NodeB cells to
be upgraded.

configured are available.
If yes, the upgrade succeeds.
If no, refer to the alarm online help.
Querying the current

NodeB version
Execute LST VER:; on the LMT. Then

check whether the current flash and
BootRom Version are all
V100R008C01B072.
Performing a dialing
test
Conduct the test by following the

instructions in Appendix C Dialing Test
after NodeB Upgrade. Ensure that system
services are not affected after upgrading
the NodeB.
4.7 Finishing the Upgrade

If the NodeB is verified to be normal after the upgrade, the upgrade is completed. Then delete
the following files under the directory of D:\NodeBVer:
Installation file of the NodeB O&M system.
NodeB software.
M2000 Meditation version file.
If the NodeB is verified to be abnormal after the upgrade and no fault is cleared, you must fall
back the version to restore the system.
Issue 1.00
Page 37 of 57
Falling Back the NodeB Version
Note:
If the upgrade fails or network performance seriously declines in the dial test after upgrade, the version
needs fallback. However, fallback depends on the practical situations of the network and the customer's
requirement.
5.1 Falling Back the NodeB Version through

the LMT
5.1.1 Falling Back the BootROM Version
To fall back the BootROM version, perform the following:
2). Select Upgrade BootRom, and then click Next.
The Upgrade Bootrom is displayed.
3). Select Activate BootRom only, and then select the version to which the current version
falls back.
4). Click Next.
A dialog box is displayed, indicating the status and progress of activating the BootRom.
After the BootRom package is activated, the boards that are activated and those fail to be
activated are listed.
5). If there are boards whose BootRom fails to be activated, refer to section 8.2"FAQ1"
"How to handle the failure in activating the NodeB BootROM when upgrading the
NodeB through the LMT?".
5.1.2 Falling Back the Data Configuration File

Falling back the data configuration file is not required.
Issue 1.00
Page 38 of 57
5.1.3 Falling Back the NodeB Software

To fall back the NodeB software, perform the following:
2). Select NodeB Software Upgrade.
The Figure of Software Upgrade is displayed.
3). Select Activate NodeB Software only, and then select the version to which the current
version falls back.
4). Click Next.
This NodeB starts to activate its software package. After the NodeB software is
activated, the boards that are activated and those fail to be activated are listed. Then the
NodeB is automatically reset.
5). If there are boards whose BootRom fails to be activated, refer to section 8.3"FAQ2"
"How to handle the failure in activating the NodeB software when upgrading the NodeB
through the LMT?"
5.2 Falling Back the NodeB Version Through

the M2000 Client
To fall back the NodeB version through the M2000 client, perform the following:
1). You must select the basic version from Bootrom Version and Software Version to fall
back the BootRom and NodeB software versions to the basic versions.
2). Check that the NodeB works well".
Issue 1.00
Page 39 of 57
Handling After the

Upgrade
6.1 Refreshing Equipment Archives

After upgrade succeeds, please update equipment archives in the equipment archive
fileserver:
If the equipment archives are in the state of documentation, follow the steps: [online
export] the equipment archives update equipment NE version and equipment software
version [online import] the equipment archives;
If the equipment archives are in the state of offline export, you should inform the
equipment archive export personnel and document administrator in the representative
office of the version information after upgrade, and ask them to update the equipment
NE version and software version before uploading the archives.
6.2 Setting the License

For the newly-added license-control information in BTS3812E-BTS3812A-BTS3812AE
V100R008C01B072, refer to section 1.1.6"Upgrading License."
To add or modify license control items, apply for or set the related license information
according to License User Guide.
Issue 1.00
Page 40 of 57
Upgrade Verification
7.1 Verification Checklist

Figure 1.16 Verification checklist
No.
Item
Check Points
Checking equipment panel states
Checking version information
Checking alarm information
Dialing test for basic services
Verifying network problems
Verification of new features
Checking equipment running

status
Result
7.2 Checking Equipment Panel States

Figure 1.17 Checklist for equipment panel states
Issue 1.00
No.
Item
Check Points
Whether the equipment panel can

be properly started
Whether there is any board in red

(faulty)
Whether there is any board in

yellow (alarm)
Result
Page 41 of 57
No.
Item
Check Points
Whether there is any board in blue

(blocked)
Whether there is any board in

deep gray (in position but not
configured)
Whether there is board in fleet

gray (configured but no in
position)
Is the board configured after

upgrading is consistent with that
before upgrading?
Whether the interconnected BBUs

are properly displayed
Whether the RRUs are properly

displayed
10
Whether the RHubs are properly

displayed
11
Whether the PicoRRUs are

properly displayed
Result
7.3 Checking Software Version Information

Figure 1.18 Checklist for software version information
Issue 1.00
No.
Item
Check points
NodeB software version
V100R008C01B072
NodeB BootRom version
V100R008C01B072
NMPT version
V100R008C01B072
HULP version
V100R008C01B072
HDLP version
V100R008C01B072
HBBI version
V100R008C01B072
NUTI version
V100R008C01B072
NDTI version
V100R008C01B072
MTRU version
V100R008C01B072
10
NMON version
V100R008C01B072
Result
Page 42 of 57

Note:
The BootRom Version information should be checked depending on the upgrade of BootRom.
If BootRom upgrade is not required, it is unnecessary to check the BootRom Version information.
If BootRom upgrade is required and the BootRom version is not released along with NodeB
software, the BootRom Version information should be checked. The check point is the BootRom
Version that is to be upgraded.
If BootRom upgrade is required and the BootRom version is released along with NodeB software,
the BootRom Version information should be checked. The check point is the BootRom Version that
is delivered with the NodeB software.
7.4 Checking Alarm Information

Check whether there are related faults or event alarms on the LMT.
7.5 Dialing Test for Basic Services

For details, refer to the Dialing Test Record for BTS3812E-BTS3812A-BTS3812AE
V100R008.
7.6 Verifying Network Problems

Perform regression test for the recorded network problems and confirm that all the problems
are solved in the new version.
Note down the results in Figure 1.19.
Figure 1.19 Verifying network problems
No.
Ticket No.
Description
Regression Test
Passed or Not
1
2
3
4
7.7 Verifying New Features

Figure 1.20 Verification of new features
No.
Feature
Description
Description of
Test Cases
Result
1
2
Issue 1.00
Page 43 of 57
No.
Feature
Description
Description of
Test Cases
Result
3
4
7.8 Checking Equipment Running Status

Check the equipment running status and compare running specifications of the equipment
before upgrade and those after upgrade.
7.9 Confirming the CB

If the NodeB works properly based on the check after the upgrade, use the CFM CB
command to confirm the running version including the software version and the data
configuration file. Then, a new Configuration Baseline (CB) is generated.
You can use the CFM CB command when you need to back up the currently running CB.
To confirm the CB, perform the following steps:
1). Click the MML command->System Management->CB Management. Choose "CFM
CB"(Confirm Configuration Baseline).
2). Select Confirm Mode(FORCED or UNFORCED), and then enter the CB name and
comments (optional).
3). Click
Issue 1.00
or press F9 on the keyboard.
Page 44 of 57
FAQ
8.1 FAQ Table

Figure 1.21 FAQ table
No.
Question
FAQ1
How to handle the failure in activating the NodeB BootRom when upgrading
the NodeB through the LMT?
FAQ2
How to handle the failure in activating the NodeB software when upgrading
the NodeB through LMT?
FAQ3
How to clear the fault in abnormal IPoA channel at the far end, or in a broken
link between the M2000 and the NodeB after the NodeB is upgraded?
FAQ4
How to handle the failure in accessing the NodeB by some UEs after the
NodeB is upgraded?
FAQ5
What is the function of the NodeB file server?
FAQ6
Why the download rate can be faster during the upgrade process when
"download by configuration" is selected?
8.2 FAQ1
I. Question
How to handle the failure in activating the NodeB BootROM when upgrading the NodeB
through the LMT?
II. Answer
First, list the boards that fail to be activated according to the results of NodeB BootRom
activation. You may choose to activate one board only or all boards of the same type,
depending on the results of NodeB BootRom activation. The latter method is applicable to
situations when there are a number of boards of the same type fail to be activated.
Issue 1.00
Page 45 of 57
To activate board BootRom, perform the following:

2). Select Activate Board, and then click Next to display the Software Upgrade Activate
Board dialog box.
3). Select Single board in the Activate BOOTROM field, and then enter the related
subrack number and the slot number.
If there are a number of boards whose BootROM fails to be activated and the boards belong to
the same type, select A type of boards in the Activate BOOTROM field. Select the type of
boards to be activated from the Board type drop-down box.
4). Click Next to activate the BootRom of a single board or a type of boards.
Follow the steps above to activate the BootRom of other types of boards.
8.3 FAQ2
I. Question
How to handle the failure in activating the NodeB software when upgrading the NodeB
through the LMT?
II. Answer
First, lick the View Details button to list the boards that fail to be activated according to the
results of NodeB software activation. You may choose to activate one board only or all boards
of the same type, depending on the results of NodeB software activation. The latter method is
applicable to situations when there are a number of boards of the same type fail to be
activated.
Issue 1.00
Page 46 of 57
Figure 1.1 Software update result

Activate board software as follows:
2). Select Activate Board, and then click Next to display the Software Upgrade Activate
Board dialog box.
3). Select Single board in the Activate Software field, and then enter the related subrack
number and the slot number.
If there are a number of boards whose BootROM fails to be activated and the boards belong to
the same type, select A type of boards in the Activate Software field. Select the type of
boards to be activated from the Board type drop-down box.
4). Click Next to activate the software of a single board or a type of boards.
Follow the steps above to activate the software of other types of boards.
Issue 1.00
Page 47 of 57
8.4 FAQ3
I. Question
How to clear the fault in abnormal IPoA at the far end and in a broken link between the
M2000 and the NodeB after the NodeB is upgraded?
II. Answer
If the NodeB IPoA address fails to be pinged, refer to the reasons and related solutions below:
Reason 1: The related alarms show that the E1 link between the RNC and the NodeB is
abnormal or faults occur to IMA/UNI/CP ports.
Solution 1: Clear the fault in E1 transmission until all related alarms are cleared.
Reason 2: The MML command of DSP E1T1 executed at the RNC indicates the IMA groups
at the RNC and the NodeB fail to interwork due to the fact that there is an E1 working in
loopback mode in the IMA group of the NodeB configured at the RNC.
Solution 2: Reset the IMA group at the RNC. If the IPoA is still abnormal, reset the IMA
group after removing the E1 working in loopback mode at the RNC.
Reason 3: Field check shows that the RUN/ALM/ACT indicators on the HBBU are
abnormal.
Solution 3: Contact the person in charge of Huawei technical support or NodeB
troubleshooting specialist as soon as possible. Collect related data under the guidance of the
specialist. After getting the approval by the specialist, reset, pull out, install, or replace the
HBBU until all related faults are cleared.
Reason 4: Login to the NodeB through the near-end Ethernet port from the LMT fails. The IP
address cannot be pinged.
Solution 4: Contact the person in charge of Huawei technical support or NodeB
troubleshooting specialist as soon as possible. Collect related data under the guidance of the
specialist. After getting the approval by the specialist, reset, pull out, install, or replace the
HBBU until all related faults are cleared.
8.5 FAQ4
I. Question
How to handle the failure in accessing the NodeB by some UEs after the NodeBs are
upgraded?
II. Answer
Contact the person in charge of Huawei technical support or NodeB troubleshooting specialist
as soon as possible. Collect related data under the guidance of the specialist. Troubleshoot the
failure at the remote end until all related faults are cleared.
Refer to the table below for troubleshooting steps and collected data.
Issue 1.00
Page 48 of 57
Figure 1.22 Troubleshooting steps and collected data

Actions
Results
Data Collected
Check NodeB active alarms through the LMT,

and then clear the alarms if any.
NodeB alarm data
Check active alarms associated with the

NodeB through the LMT at the RNC, and then
clear the alarms if any.
NodeB alarm data
Upload the HBBU log file by executing ULD

FILE: DSTF="c:\", FLAG=HBBULOG,
IP="10.161.41.71", USR="admin",
PWD="admin", CF=UNCOMPRESSED;
Uploaded HBBU logs
Confirm that local cells are available at the

NodeB by executing DSP CELL. Confirm that
logical cells at the RNC are OK by executing
DSP CELL.
MML command messages

saved
Confirm that the NodeB output power is

normal.

saved
Check the locking of frequency and scramble

of the UE under test.
Check the accessibility of the new UE or the
new UE SIM card.
Issue 1.00
If possible, check whether the UE under test

originates the RRC CONNET REQ message.
Logs recorded
Check that the NodeB RTWP is normal with

the value at 106 dBm 3 dB
RTWP measurement files

recorded
Query Iub micro channel data carried over all

AAL2PATHs of the NodeB by executing DSP
AAL2CHN at the RNC.

saved
Trace and save all messages of the UE under

test through single UE tracing at the RNC.
Single UE tracing
Trace and save all messages of the UE under

test over the Uu, Iu, Iub interfaces.
Messages traced over Iu,

Iub and Uu interfaces
Trace messages over the Iub interface of the

NodeB.
Messages traced over

NodeB Iub interface
Export RNC CDR log files before and after

NodeB upgrade.
CDR log files before and

after NodeB upgrade
Page 49 of 57
8.6 FAQ5
I. Question
What is the function of the NodeB file server?
II. Answer
To upgrade NodeB software, you must configure the NodeB file server to the M2000. The
server is used to store NodeB software packages and to provide FTP server services for the
NodeB to be upgraded. When upgrading software, the NodeB needs to download the software
package from the file server.
The NodeB file server can be configured either to the M2000 or to the related RNC. The
server, if configured to the RNC, has the following advantages:
1). During the upgrade, the NodeB can download software in batches from the related RNC
at a faster speed than from the file server configured to the M2000.
2). If there is a firewall restricting the NodeB FTP Client from accessing the M2000 server
in the IP network configuration, software fails to be downloaded from the NodeB file
server configured to the M2000. Instead, software can be normally downloaded from the
NodeB file server configured to the RNC.
Therefore, it is suggested to set the default configuration of the NodeB file server to the RNC.
Note:
Before upgrade, you only need to check that the NodeB file server is correctly configured.
If the configuration of the NodeB file server is correct, the system automatically downloads the
NodeB software package from the M2000 server to the NodeB file server without any manual
operations.
8.7 FAQ6
I. Question
Why the download rate can be faster during the upgrade process when "download by
configuration" is selected?
II. Answer
The NodeB software package contains the software for all the boards supported by the
NodeB. Each board type corresponds to one board software package.
In regular mode, the entire NodeB software package is downloaded to the NodeB. However,
in actual application, only some types of boards are configured on the NodeB and not all the
software packages are required.
Therefore, "download by configuration" refers to downloading the required board software
packages from the file server during the upgrade process in compliance with the types of
boards currently configured on the NodeB. This can effectively reduce the total data volume
in the download, minimize the duration, and ensure that the software packages use least
storage space on the hard disk.
Issue 1.00
Page 50 of 57
Generally, "download by configuration" has the following benefits:
Download only the required board software from the software package according to the current
NodeB configuration.
Use the valuable maintenance link bandwidth effectively, minimize the duration for
downloading the software, and improve the upgrade efficiency.
Use the storage space on the hard disk of the NodeB effectively and avoid waste of storage
space for software not to be used.
The download rate in this mode will be faster when the NodeB has boards of fewer types.
Figure 1.23 Comparison between regular download and download by configuration
Typic
al
Confi
gurati
on
Board
Typ
e
Quantit
y
Regula
r
By
Confi
gurati
on
Regula
r
By
Configu
ration
BTS381
2EBTS381
2A 3 x 1
configur
ation
NMP
T
80 min.
40 min.
30
Mbytes
15 Mbytes
64 kbit/s
NUTI
HBBI
MTR
U
MAF
U
HBB
U
60 min.
50 min.
21
Mbytes
18 Mbytes
64 kbit/s
MRR
U
DBS380
03x1
configur
ation
Duration
Storage Space
Bandwidth
Note:
The NodeB uses one active directory and one standby directory to store two pieces of software. The
space saved on the hard disk in this situation will be:
BTS3812E-BTS3812A: 15 Mbytes x 2 = 30 Mbytes
DBS3800: 3 Mbytes x 2 = 6 Mbytes
Since there are differences between the two download modes, the methods of adding boards
of new types to the NodeB vary as follows:
Issue 1.00
Page 51 of 57
Figure 1.24 Methods of adding boards of new types to the NodeB

Mode
Description
How to Add
New Board
Exception
Remarks
Regular
download
Download the
entire NodeB
software package
to the NodeB.
Obtain the board

software directly
from the NodeB
and automatically
activate it.
None.
None.
Download by
configuration
Download only the

required board
software for the
boards currently
configured on the
NodeB.
Obtain the software

from the specified
file server and
automatically
activate it to
upgrade the boards.
Alarms will be
reported if the
file server
cannot be
connected or
no
corresponding
versions are
found on the
server.
Alarm ID:
ALM-3539.
Note:
The NodeB of V100R007 supports "download by configuration" for the flash on the boards but does
not support "download by configuration" for the BootROM. The NodeB BootROMs must be
downloaded in regular mode.
Issue 1.00
If the alarm with the ID 3539 is generated, run the MML command SPL SOFTWARE to
supplement the software.
Page 52 of 57
Appendix
9.1 Upgrade Preparation Record

Figure 1.25 Upgrade preparation record
Items
Description
Remarks
Equipment name
Equipment location
Date and time approved by the
customer
Upgrade the NodeB version when the

traffic is light, for example, late at night.
Customer requirements
Version before upgrade
Version after upgrade
Version requirements of
associated products
Software for upgrade
Data for upgrade
It is not necessary to prepare data for

upgrade if there is no change in data
configuration.
Hardware for upgrade
It is not necessary to prepare hardware

for upgrade if hardware is not involved in
upgrade.
Tools for upgrade
The tools for upgrade include special

upgrade tools, UE, SIM card, and
Ethernet cables.
53
Items
Issue 1.00
Description
Remarks
Upgrade engineers
The upgrade engineer team is usually

made up of those on the customer's side
as well as those from HUAWEI.
Associate engineers
The upgrade might involve other

engineers, for example, in O&M, in
network planning, and in drive test.
Transportation vehicles
The upgrade might involve the use of

vehicles for drive test.
Person in charge
Names and phone numbers are required.
Page 54 of 57
Upgrade Data Sheet

Figure 1.26 Upgrade data sheet
Operator name
Upgrade
date
Version after
upgrade
Engineers assigned by operator:
Engineers from Huawei:
Version before
upgrade
Engineers
responsible for
the upgrade
Upgrade
succeeds?
Upgrade Actions
Check operating
state before
upgrade
Upgrade
procedure
Verifying
upgrade
Conclusi
on
Check multiple IP addresses.

Check active alarm data.
Query cell status.
Check data consistency.
Back up data.
Check the configuration of
the NodeB file server.
Upload the software package
to the M2000 server.
Download the NodeB
BootROM.
Download the NodeB
software package.
Activate the NodeB
BootROM.
Activate NodeB software
package.
Query active alarm data.
Check cell status.
Query version information.
Check dialing tests.
Upgrade the
LMT
55
Handling
Suggestions
upon Abnormity
9.2 Dialing Test after NodeB Upgrade

Figure 1.27 Dialing test after NodeB upgrade
Record of NodeB Dialing Test
NodeB Name
Test time
Test result
Pass Not Pass
Cell name
Cell ID
Cell scramble
Dialing Test
Result
Speech: fixed-line
phone to mobile (3G)
Pass NotPass N/A
Speech: mobile (3G)

to fixed-line phone
Pass NotPass N/A
Speech: mobile (3G)

to mobile (2G)
Pass NotPass N/A
Speech: mobile (2G)

to mobile (3G)
Pass NotPass N/A
Speech: mobile (3G)

to mobile (3G)
Pass NotPass N/A
VP: mobile (3G) to

mobile (3G)
Pass NotPass N/A
PS: PDP activation
Issue 1.00
Pass NotPass N/A
Speech conversation
quality
Good Bad N/A
VP conversation
quality
Good Bad N/A
PS communications
quality
Good Bad N/A
Call dropped
Remarks
Pass NotPass N/A
Page 56 of 57
Soft handover
Pass NotPass N/A
RSCP (should: > 70

dBm)
Ec/I0 (should: > 10
dB)
Remarks
Tested by
(signature)
Issue 1.00
Page 57 of 57

c05 Bts3812e v100r008c01b072 Upgrade GuideC05 BTS3812E V100R008C01B072 Upgrade Guide

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

c05 Bts3812e v100r008c01b072 Upgrade GuideC05 BTS3812E V100R008C01B072 Upgrade Guide

Diunggah oleh

Hak Cipta:

Format Tersedia

BTS3812E-BTS3812A-BTS12AE V100R008C01B072 Version Upgrade Guide

HUAWEI TECHNOLOGIES CO., LTD.

BTS3812E-BTS3812A-BTS12AE V100R008C01B072 Version Upgrade Guide

3 Upgrading the NodeB from the M2000.........................................18

Huawei Technologies Proprietary

BTS3812E-BTS3812A-BTS12AE V100R008C01B072 Version Upgrade Guide

4 Upgrading the NodeB from the LMT.............................................31

5 Falling Back the NodeB Version...................................................38

6 Handling After the Upgrade........................................................40

Huawei Technologies Proprietary

BTS3812E-BTS3812A-BTS12AE V100R008C01B072 Version Upgrade Guide

Huawei Technologies Proprietary

BTS3812E-BTS3812A-BTS12AE V100R008C01B072 Version Upgrade Guide

Huawei Technologies Proprietary

BTS3812E-BTS3812A-BTS12AE V100R008C01B072 Version Upgrade Guide

Comparison between regular download and download by configuration

Huawei Technologies Proprietary

BTS3812E-BTS3812A-BTS12AE V100R008C01B072 Version Upgrade Guide

Preparations for Upgrade

1.1 Elementary Preparation Before Upgrading

NodeB upgrade flash

A self-extracting file that containing the flash and BootRom

It is a self-extracting file that consists of the LMT installation

It consists of the installation program and related documents.

It is used to log in to the PC that is loaded with the LMT.

Login password of the

To upload the M2000 mediation installation package to the

1.1.2 Preparing Hardware

1.1.3 Preparing Upgrade Tool

Mobile phones for dial test

Huawei Technologies Proprietary

BTS3812E-BTS3812A-BTS12AE V100R008C01B072 Version Upgrade Guide

1.1.4 Preparing Data

1.1.5 Points for Attention

The test is performed in 3 x 1

Huawei Technologies Proprietary

BTS3812E-BTS3812A-BTS12AE V100R008C01B072 Version Upgrade Guide

such as the network

Abide by the following principles during the upgrade:

Power off the NMPT

Power off the NMPT

9). If a standby NMPT is available, check it before the upgrade.

The standby NMPT status is Available.

Huawei Technologies Proprietary

BTS3812E-BTS3812A-BTS12AE V100R008C01B072 Version Upgrade Guide

1.1.6 Upgrading License

HSUPA not supported

MBMS not supported

Power sharing not

HSUPA not supported

MBMS not supported

Power sharing not

15 codes per cell

Huawei Technologies Proprietary

BTS3812E-BTS3812A-BTS12AE V100R008C01B072 Version Upgrade Guide

1.1.7 Checking BootRom

Huawei Technologies Proprietary

BTS3812E-BTS3812A-BTS12AE V100R008C01B072 Version Upgrade Guide

1.1.8 Checking Current Login Account

1.1.9 Obtaining Files for Upgrade

Obtain the flash software package

Get the files corresponding to BTS3812E-BTS3812A-BTS3812AE V100R008C01B072 from

Decompress the version file to the destination folder