Huawei Bsc6000 v900r003 Upgrade Guide

r

Version Upgrade Instructions

HUAWEI BSC6000 V900R003Upgrade Guide

Issue 1.00

Date 2007-12-29

内部使用

HUAWEI TECHNOLOGIES CO., LTD.

INTERNALUSE

HUAWEI BSC6000 V900R003

Upgrade Guide

Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. Please feel free to contact our local office or company headquarters.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base

Bantian, Longgang

Shenzhen 518129

People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

Copyright © Huawei Technologies Co., Ltd. 2007. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.

All other trademarks and trade names mentioned in this document are the property of their respective holders.

Notice

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 the warranty of any kind, express or implied.

Issue 1.00 (2007-12-29)Huawei Proprietary and Confidential

Page 2 of 84

mailto:[email protected]

http://www.huawei.com/

INTERNALUSE


Upgrade Guide

About This Document

Authors

Prepared by Yu Zhiguo、Wang Guanghui Date: 2007-12-29

Reviewed by Zhou Liang, Liu Ying, Yangjian,

Wang Dong, Guo Gaorong

Date: 2007-12-29

Approved by Fang Wei Date: 2007-12-29

Summary

You are advised to read the entire document prior to using HUAWEI

BSC6000V900R003C01. This document contains the following contents:

Section Details

Error: Reference source not found

Version Requirements for Upgrade

Describes the requirements for the confirmation of

the source version required to be upgraded and the

target version before the upgrade


Upgrade Flow Chart

Describes the whole procedures for upgrading the

version.

3 Error: Reference source not

found

Describes the preparations before the upgrade and

the health check.


Page 3 of 84

INTERNALUSE


Upgrade Guide

Error: Reference source not foundL

ocal Upgrade Operations

Error: Reference source not foundR

emote Upgrade Operations

Describes the actual procedures for the upgrade. The

upgrade must conform to the procedures strictly.

7 Upgrade Verification Describes the verification of the upgraded version

and equipment. The normal running of the upgraded

system can be ensured.


Version Rollback

Describes the processing procedures for failed

upgrade or other reasons.

9 FAQ Describes the records of collected important

problems related to the version upgrade.

History

版本描述发布日期作者签发人

1.00 the first release 2007-12-29 YuZhiguo,WangGuanghui Fangwei


Page 4 of 84

INTERNALUSE


Upgrade Guide

Contents

1 Version Requirements for Upgrade...............................................10

2 Upgrade Flow Chart.....................................................................11

3 Preparations for Upgrade.............................................................13

3.1 Checklist Before Upgrade................................................................................................................................13

3.2 Preparations for Upgrade.................................................................................................................................13

3.3 Checking the Versions Before the Upgrade.....................................................................................................14

3.3.1 Host Version...........................................................................................................................................14

3.3.2 Version Mapping of the M2000..............................................................................................................14

3.3.3 Version Mapping of Level 2 BIOS.........................................................................................................15

3.4 Required Software in the Preparations for upgrade.........................................................................................15

3.5 Preparing the License.......................................................................................................................................17

3.5.1 Change in Control of the License...........................................................................................................17

3.5.2 Applying for the License........................................................................................................................18

3.5.3 Checking the License..............................................................................................................................18

3.6 Checking the Correctness of the DIP Switches for Subracks..........................................................................19

3.7 Matters to Note in Upgrade.............................................................................................................................19

4 Local Upgrade Operations............................................................21

4.1 Backing Up Data and Board Software.............................................................................................................21

4.1.1 Backing Up Data....................................................................................................................................21

4.1.2 Backing Up Software..............................................................................................................................22

4.1.3 Backing Up the License..........................................................................................................................23

4.2 Backing Up Data Configuration Files.............................................................................................................23


Page 5 of 84

INTERNALUSE


Upgrade Guide

4.2.1 Checking the Current System.................................................................................................................23

4.2.2 Backing Up Data Configuration Files....................................................................................................24

4.3 Loading the Host Software Online..................................................................................................................24

4.3.1 Downloading Upgrade Package.............................................................................................................25

4.3.2 Loading the Host Software to a Board Online.......................................................................................26

4.4 Loading the Level 2 BIOS to a Board Online..................................................................................................26

4.4.1 Loading Level 2 BIOS File Online.........................................................................................................27

4.5 Upgrading the LMT.........................................................................................................................................28

4.6 Upgrading the Configuration Data File...........................................................................................................29

4.6.1 Upgrading the Configuration Data File..................................................................................................29

4.6.2 Prepraring the Configuration Data File..................................................................................................31

4.7 Upgrading GBAM and Single GOMU............................................................................................................31

4.7.1 Operation Preparations...........................................................................................................................32

4.7.2 Upgrading the GBAM............................................................................................................................34

4.7.3 Upgrading the GOMU............................................................................................................................34

4.7.4 Verify OMU version...............................................................................................................................34

4.8 Upgrading Active/Standby GOMU.................................................................................................................34

4.9 Data Restoration..............................................................................................................................................40

4.10 Upgrading Board Software............................................................................................................................44

4.10.1 Preparations..........................................................................................................................................44

4.10.2 Procedures for the Upgrade..................................................................................................................44

4.10.3 Confirming the Board State..................................................................................................................45

4.10.4 Exception Handling..............................................................................................................................45

4.11 Activating the Software License....................................................................................................................46

5 Installing the M2000 Adaptation Layer..........................................47

6 Remote Upgrade Operations.........................................................48

6.1 Preparations.....................................................................................................................................................48

6.2 Procedures for the Upgrade.............................................................................................................................49

6.2.1 Creating the NE Objects.........................................................................................................................49

6.2.2 Uploading Software and Data.................................................................................................................49


Page 6 of 84

INTERNALUSE


Upgrade Guide

6.2.3 Performing the Upgrade.........................................................................................................................50

6.2.4 Download and Activate License.............................................................................................................52

7 Upgrade Verification....................................................................53

7.1 Verification Checklist.......................................................................................................................................53

7.2 Verification After the Upgrade.........................................................................................................................53

7.3 Completing the Upgrade..................................................................................................................................55

7.3.1 Sanitation in the Environment After the Upgrade Succeeds..................................................................55

8 Version Rollback..........................................................................56

8.1 Precautions.......................................................................................................................................................56

8.2 Rollbacking OMU Software............................................................................................................................56

8.3 Restore old data and old board software..........................................................................................................58

8.4 Starting the OMU Software.............................................................................................................................59

8.5 Rolling Back Board Software..........................................................................................................................59

8.6 Rolling back LMT...........................................................................................................................................60

8.7 Verification.......................................................................................................................................................60

9 FAQ.............................................................................................61

9.1 FAQ Index........................................................................................................................................................61

9.2 FAQ1................................................................................................................................................................61

A Upgrade Preparations..................................................................62

B Upgrade Record...........................................................................64

C Checklist for Dialing Test..............................................................65

D Checklist for System Health Before the Upgrade...........................68

E Checklist for System Health After the Upgrade..............................71

F Checklist for the Configuration Information on License Files..........76

G Acronyms and Abbreviations.........................................................................77


Page 7 of 84

INTERNALUSE


Upgrade Guide

Figures

Figure 3-1 Operating status of equipment.............................................................................................................19


Page 8 of 84

INTERNALUSE


Upgrade Guide

Tables

Table 2-1 Procedures for upgrading a version.......................................................................................................11

Table 3-1 Table 3-1 lists the mapping between the latest versions：...................................................................15

Table 3-2 Version mapping of BSC6000 level 2 BIOS.........................................................................................15

Table 3-3 lists the BSC6000 software directory structure...................................................................................16

Table 3-4 Change in control of the License in BSC6000V900R003C01..............................................................17

Table 6-1 Checklist for the verification items.......................................................................................................54

Table 8-1 FAQ list.................................................................................................................................................62


Page 9 of 84

INTERNALUSE


Upgrade Guide

1 Version Requirements for Upgrade

This upgrade guide applies to the upgrade from an earlier release to a later release of BSC6000V900R003. In

addition, it applies to the upgrade from an earlier release to a later release of GBAM or GOMU. For the upgrade

from the GBAM to the GOMU, refer to the Guide to the Upgrade from the GBAM to the GOMU in

BSC6000V900R003.


Page 10 of 84

INTERNALUSE


Upgrade Guide

2 Upgrade Flow Chart

lists the procedures for upgrading a version.：

Table 2-1 Procedures for upgrading a version

Step Operation ReferenceDuration (For

Reference Only)

1Preparation

Section 3 Depend on your actual

requirements

2Back up data and

software

Section Error:

Reference source not

found

Depend on the actual

data volume

3Back up data

configuration files

Section Error:


found

5 minutes

4Load the host software

online

Section Error:


found

15 minutes

5Load the Level 2 BIOS

online

Section Error:


found

10 minutes


Page 11 of 84

INTERNALUSE


Upgrade Guide

Step Operation ReferenceDuration (For

Reference Only)

6

Upgrade the LMT

Section Error:


found

15 minutes

7Upgrade data

configuration files

Section Error:


found

10 minutes

8

Upgrade OMU software

Section Error:


found

15 minutes

9 Restore data Section 15 3 minutes

10

Upgrade board software

Section 4.10 If step 5 is skipped,

duration of the step is 25

minutes. Otherwise, the

duration of the step is 15

minutes.

11 Download and activate

the software license

Section 4.11 5 minutes

12 Install the software that

is in M2000 adaptation

layer

Section 5 40 minutes

13 Remote Upgrate

Operation

Section 6 30 minutes

14 Check the running status

after the upgrade

Section 7.2 2 minutes

15Clean up the site after the

upgrade

Section Error:


found

2 minutes


Page 12 of 84

INTERNALUSE


Upgrade Guide

3 Preparations for Upgrade

3.1 Checklist Before Upgrade

No. Item Check Points Result

1 Preparations Complete the health

check before the upgrade

and prepare the records of

upgrade preparation

2 Version check before upgrade Confirm the correctness

of the upgraded version

and the consistency

3 Preparations for the software

required for the upgrade

Prepare the software


4 Preparation for the license Prepare the license and

complete the verification

5 Check of DIP switches on subracks Ensure that subracks are in non-auto start mode.


Page 13 of 84

INTERNALUSE


Upgrade Guide

3.2 Preparations for Upgrade

Before the upgrade, the related owner needs to perform system check based on Appendix D

"."

In preparation stage, the related owner needs to prepare the upgrade based on Appendix A

"Upgrade Preparations." and records the upgrade preparations.

3.3 Checking the Versions Before the Upgrade

3.3.1 Host Version

CAUTION

For batch delivery, the initial version is specified as required in delivery. For the initial

installation, related check and configuration are necessary. For details, refer to the BSC6000

V900R003 GOMU Administration Guide. This document is used only to introduce the version

upgrade.

The host version is checked as follows:

Step 1 Log in to the LMT, and then connect the LMT to the GBAM

Step 2 Log in to the LMT, and then choose Help > About to view the information on versions. For

detailed information on version B, press Ctrl+Shift+F12.

----End

3.3.2 Version Mapping of the M2000

To ensure that NEs are maintained normally and the BSC6000 versions are upgraded

normally, the personnel in charge of the upgrade must ensure the mapping between the

BSC6000 versions and M2000 adaptation layer and also the mapping between the server and

the versions on the client.


Page 14 of 84

INTERNALUSE


Upgrade Guide

Table 3-1 Error: Reference source not found lists the mapping between the latest versions：

BSC6000

Version

Version in M2000 Adaptation Layer M2000

Server/Client

Version

BSC6000V900R003

C01B032

iManagerM2000_BSC6000_MATCH_ENG_V

200R005C01B032

iManagerM2000_BSC6000_MATCH_CHS_V

200R005C01B032

iManagerM2000

V200R005C01B7

60

BSC6000V900R003

C01B061


200R005C01B039


200R005C01B039

iManagerM2000

V200R006C01B7

60SP01

BSC6000V900R003

C01B061SP01


200R005C01B039SP02


200R005C01B039SP02

iManagerM2000

V200R006C01B7

60SP01

BSC6000V900R003

C01B062


200R005C01B041.tar


200R005C01B041.tar

iManagerM2000

V200R005C01B7

60SP01

BSC6000V900R003

C01B070


200R006C01B370.tar


200R006C01B370.tar

iManagerM2000

V200R005C01B7

60SP01


Page 15 of 84

INTERNALUSE


Upgrade Guide

3.3.3 Version Mapping of Level 2 BIOS

Table 3-1 Version mapping of BSC6000 level 2 BIOS

BSC6000 Active Version Level 2 BIOS Version

BSC6000V900R003C01B032 GXPUT/GXPUM：207

Others:206

BSC6000V900R003C01B061 GXPUT/GXPUM、GEIU/GOIU、GDPUC：208

GTNU：207

Others:206

BSC6000V900R003C01B070 GXPUT/GXPUM、GEIU/GOIU、GDPUC：208

GTNU：207

Others: 206

3.4 Required Software in the Preparations for

upgrade

The BSC6000 software consists of the LMT installation disk, OMU installation package,

compressed host software package, and scripts used in the upgrade.

Table 3-1 Error: Reference source not found lists the BSC6000 software directory structure.

catalog comment

version 　x—C version number

yy—B version number

　 HOST 　 Host software directory

　　 GBAM 　 Host software document directory


Page 16 of 84

INTERNALUSE


Upgrade Guide

released commercially

　　　 boardfile.9.3.x.yy.zip

Compressed board software

package is used to upgrade

software on boards.

　　　 omu-9.3.x-yy.i586.rpmOMU software package is used to

upgrade the OMU software.

　　　 verpkg.xml

Upgrade package version mapping

file is used to check the correctness

of board software and OMU

software during the upgrade.

　　　 upgradecfg.xml

Remote upgrade configuration file

is used only in remote upgrade.

The file is unnecessary in local

upgrade.

　　　 vercfg.xml

Remote upgrade version mapping

file is used only in remote upgrade.

The file is unnecessary in local

upgrade.

　 LMT 　 LMT software directory

　　 BSC6000V900R003C0xB0yyLMT installation disk is used to

upgrade the LMT software.

To obtain the required software packages and documents during the deployment, do as follows:

Open the web page http://support.huawei.com.

Step 2 Choose Technical Support > Software > Version Software > Wireless Product Line > GSM-BSS > GSM-BSC6000 > HUAWEI BSC6000 V900R003 > HUAWEI BSC6000 V900R003C01B0yy

Step 3 Download the required software by clicking Software, and download the required documents by clicking Documentation.

Step 4 After the software is downloaded, decompress the software package to obtain the required files for the installation described in Error: Reference source not found.

--End


Page 17 of 84

http://support.huawei.com/

INTERNALUSE


Upgrade Guide

NOTE

1、 To download the putty tool, choose Technical Support > Software > Mini-tool

software > Wireless > GBSS Product Maintenance Tools > MDN-Putty.

2、 The network management software, which consists of the installation package of the

M2000 server, installation package at M2000 adaptation layer, and report template,

should be downloaded independently. You can choose Technical Support >

Software > Version Software > Core Network > Wireless-OSS to download the

software.

3.5 Preparing the License

3.5.1 Change in Control of the License

Table 3-1 Change in control of the License in BSC6000V900R003C01

New Control Item in

BSC6000V900R003C01

Deleted Control Item in

BSC6000V900R003C01

Number of TRXs supporting BTS local

switching

Number of TRXs supporting BSC local

switching

Number of TRXs supporting FLEX ABIS

Supporting the MSC POOL function


Page 18 of 84

INTERNALUSE


Upgrade Guide

3.5.2 Applying for the License

NOTE

1. The license file must be applied for at least three workdays in

advance.

2. Pay attention to the values of the license control items when applying

for a license. The applied values must be within the value range. For

the valid value of each license control item, refer to the License

Template in the License Workflow in notes.

You need to apply for a new license in the following situations:：

On a new deployment site

New license control items are added to the version to be upgraded. These license control items are not contained in the license files in earlier version.

New license control items are added to the version to be upgraded. These license control items are contained in the license files in earlier version, however, their values are incorrect.

ESN is changed. For the method of checking the ESN, refer to section 3.5.3 "Checking the License."

Onsite capacity expansion

V9R1 is upgraded to V9R3.

For the procedures for applying for the license file, refer to the GSM BSS LICENSE Application Procedure at http://support.huawei.com.

For the procedures for applying for the license file, refer to the GSM BSS LICENSE

Application Procedure at http://support.huawei.com.

3.5.3 Checking the License

CAUTION

1. The fixed length of the BSC6000 ESN is 40 bytes.

To check the ESN of the license offline, do as follows:


Page 19 of 84



INTERNALUSE


Upgrade Guide

Step 1 Log in to the LMT that is newly installed offline and check the ESN of the system. Choose BSC Maintenance > Maintain License > Query ESN. In the displayed dialog box, enter the OSP (BSC signaling point in the GMPS) and the DSP (MSC signaling point). Click Generate. Record the ESN in Appendix F "Checklist for the Configuration Information on License Files."

Step 2 Check the license file offline. Obtain the ESN information in the license file and record it in Appendix F "Checklist for the Configuration Information on License Files." Compare it with the ESN recorded in step 1.If they are inconsistent, apply for a new license file and end this upgrade.

----End

3.6 Checking the Correctness of the DIP Switches for

Subracks

Check bit 8 of DIP switches on each subrack. You need to perform the following operation

based on the result:

Set bit 8 of the DIP switches on the subracks where the DIP switches are in OFF

state to ON (in non-auto start mode). At the same time, inverse bit 6 (parity check

bit) to the opposite side.

If bit 8 is ON, the states of bit 8 and bit 6 are unnecessary to be changed.

3.7 Matters to Note in Upgrade

1. Before the upgrade, you must be familiar with the upgrade procedures and strictly follow

the procedures described in this document step by step.。

2. During the upgrade, wait until receiving a response after running a command, and then

you can perform the next step

3. Before the upgrade, check the operating status of boards. On the BSC Device Panel tab

page of the LMT, you can view the operating status of a board. The active board in

normal state is green and the standby board in normal state is light blue, as shown in the

following figure.


Page 20 of 84

INTERNALUSE


Upgrade Guide

Figure 3-1 Operating status of equipment

4. During the upgrade, the following operations on the GBAM are forbidden:

− Power off the GBAM

− Manually reset the GBAM

− Manually disconnect the GBAM from the network

5. During the upgrade, before the board initialization is complete, do not configure any

data. Otherwise, the board data and the data on the GBAM/GOMU may be inconsistent

and the following operations are affected.

NOTE

To determine whether the board initialization is complete, do as follows:

a) The GXPUM/GXPUT has four CPUs, therefore, the initialization of the GXPUM/GXPUT cannot be

complete until all the CPUs are initialized. You can right-click the GXPUM/GXPUT and choose Query

CPU/DSP State on the shortcut menu, and then click Query to check whether the initialization is complete.

Ensure that the Operation State of the four CPUs is Enabled, and the Available State of the four CPUs is

Normal. Otherwise, one CPU is abnormal.

b) For other boards, check their states on the BSC Device Panel tab page of the LMT. Ensure

that these boards are normal.

6. If the upgrade fails, or that the network performance deteriorates seriously after the

upgrade, you need to decide whether to roll back the version based on the actual situation

and customer requirements. For details about the rollback, refer to chapter 8 "Version

Rollback."

7. During the upgrade, ensure that all load control parameters are Automatic Loading.


Page 21 of 84

INTERNALUSE


Upgrade Guide

4 Local Upgrade Operations

CAUTION

The personnel in charge of the upgrade need to record related activities by referring to

Appendix B "Upgrade Record." and to provide the upgrade report.

4.1 Backing Up Data and Board Software

4.1.1 Backing Up Data

The BSC6000 data is stored under /bsc6000/data of the GBAM/GOMU. Some files contained

in this directory are listed as follows:

Data configuration files

Alarm files

Performance files

Log files

Tracing files stored on the GBAM/GOMU


Page 22 of 84

INTERNALUSE


Upgrade Guide

To back up the required files through samba, do as follows:

Step 1 On the Windows operating system, choose Start > Run.

Step 2 Connect to the GBAM/GOMU (assume that the IP address of the GBAM/GOMU is 10.161.72.254) by running \\10.161.72.254.

Step 3 Click OK.

NOTE

If a prompt that "Cannot find the \\GBAM IP address" is displayed on the Windows operating

system, you can infer that the samba service on the GBAM is not enabled. To enable the

samba service, you can use the putty tool to log in to the GBAM as user root, and then run the

rcsmb start command. Finally, log in to the GBAM through the Windows operating system.

Step 4 Double-click the bsc6000 folder. Enter the user name and password in the displayed dialog box correctly. By default, the user name is BSC6000 and the password is 11111111.

Step 5 Modify the attributes of the folders and files in the /BSC6000 directory.

You need to use the putty tool to log in to the GBAM/GOMU as user root, and then run the

chmod 777 /BSC6000 –R command on the putty tool to modify the attributes of all the

folders and that of all the files in the /BSC6000 directory.

Step 6 Enable the samba service to log in to the GBAM/GOMU, and then copy the files in the data directory to the local hard disk.

----End

4.1.2 Backing Up Software

To back up the BSC6000 software stored in the /bsc6000/bscswm directory on the

GBAM/GOMU, do as follows:

Step 1 On the Windows operating system, choose Start > Run.

Step 2 Enter the IP address of the GBAM/GOMU. For example, enter \\10.161.72.254, and then click OK.

Step 3 Double-click the bsc6000 folder. Enter the user name and password in the displayed dialog box correctly. The user name is BSC6000 and the password is 11111111 by default.

Step 4 Modify the attributes of all the folders and that of all the files in the /BSC6000 directory. Then, back up the bscswm directory on the GBAM/GOMU.

Use the putty tool to log in to the GBAM as user root.

Modify the attributes of all the folders and that of all the files in the /BSC6000

directory.


Page 23 of 84

INTERNALUSE


Upgrade Guide

# chmod 777 /BSC6000 -R

Back up the bscswm directory on the GBAM/GOMU：

# cp /BSC6000/bscswm /BSC6000/bscswmb0xx -R

In "bscswmb0xx", "xx" represents the current version number. You need to enter it

based on the actual situation.

Step 5 Copy the bscswmb0xx directory to the local hard disk, and then delete it on the GBAM/GOMU.

---End

4.1.3 Backing Up the License

This task applies to only sites where licenses are applied for and activated. To back up the

license, do as follows:

Step 1 Check and save the configuration information of the license file. Choose BSC Maintenance > Maintain License > Query License. Click Query. Fill the viewed configuration information into Appendix F "Checklist for the Configuration Information on License Files." If the license is newly applied, enter None in the Before Upgrade column.

Step 2 Check whether the license file is saved in the local hard disk. By default, the license file is saved in the \Common\SWM\license directory in earlier version. If the license file is saved in the local hard disk, backup is unnecessary. Otherwise, go to step 3.

Step 3 Enable the samba service to log in to the GBAM/GOMU, and then copy the folder in the \bsc6000\bscswm\area1\license directory to the local hard disk.

----End

4.2 Backing Up Data Configuration Files

4.2.1 Checking the Current System

Check all load control parameters of boards, except that of the GBAM/GOMU, and then ensure that

they are Auto. The method is as follows:

Step 1 On the LMT, choose BSC Maintenance > Query Software > Query Board Version Information.

Step 2 In the displayed Query Board Version Information dialog box, click the Load Option tab. On the Load Option tab page, choose each subrack (except subrack 12) in the Subrack drop-down list box in turn.

Step 3 Click Query to check the Load Option of all the boards in subracks.


Page 24 of 84

INTERNALUSE


Upgrade Guide

Step 4 If there are boards that are not loaded in Auto mode, find the corresponding board on the BSC Device Panel tab page, and then right-click it to choose Configure Board Attributes on the shortcut menu.

Step 5 On the BSC Device Panel dialog box, set the load control parameters to Automatic Loading. Then, wait for a prompt about the information on valid setting.

---End

4.2.2 Backing Up Data Configuration Files

1. Application Scenario

The configuration data before the upgrade can be used.

2. Software and Hardware Preparations：

One PC that is installed with the Windows2000 or WindowsXP operating system

and can log in to the GBAM/GOMU through the network;

LMT in earlier version

3. Operating mode：

4.3 Loading the Host Software Online

NOTE

1. This task can be performed to accelerate the board loading and shortens the service

interruption.

2. In this task, the host software does not include the upgrade of the core process or that of

the local process of the GBAM/GOMU.

3. Normally, V9R3C01B054 and later releases only support the upgrade from an earlier C

version to a later C version. To perform upgrade from an earlier B version to a later B

version, you should enable the B version upgrade function before the upgrade. In other

words, you should run the SET SWMDBG:DS=ON command on the MML client. The

version number entered during the upgrade should include the B version number.


Page 25 of 84

INTERNALUSE


Upgrade Guide

Loading host software online refers to loading the host software in later version by using the

MML client and the GBAM/GOMU to the Flash of each board. The following sections

describe how to load host software online.

4.3.1 Downloading Upgrade Package

The upgrade package to the GBAM can be downloaded through the MML client:

Step 1 Copy the upgrade package (omu-9.3.x-yy.i586.rpm and boardfile.9.3.x.yy.zip) and the version configuration table (verpkg.xml) of the upgrade package to the common\SWM directory, which is the relative directory for the LMT installation path, and start the FTP Server in Common\FtpServer directory installed with LMT.

Step 2 On the MML client, run a command to download the upgrade package and then observe the download progress and download result on the MML client.Choose MML Commands > System Management > Software Management > Version Management > Download and Unzip the Installation Package.

DLD VERPKG: IP="local IP address", DIR="Common\SWM\software",

SV="BSC6000V900R003C01";

IP indicates the IP address of the FTP server. USR indicates the user name (swmtest)

that is used for logging in to the FTP server. PWD indicates the password (swmtest) that

is used for logging in to the FTP server. DIR indicates the directory (for example,

common\SWM\b099) for storing and loading versions on the FTP server. (You can click

or press F9.)

Step 3 On the MML client, query the version of the host software. Then confirm that the host software in later version is contained in the version area of the GBAM. Choose MML Commands > System Management > Software Management > Version Management > List Software Version. (You can click or press F9.)

LST SOFTWARE:;

----End


Page 26 of 84

INTERNALUSE


Upgrade Guide

4.3.2 Loading the Host Software to a Board Online

The host software file can be loaded from the GBAM/GOMU to a board through the MML

client.，do as follows:

1. On the MML client, choose MML Commands > System Management > Software

Management > Version Management > Load Software Online. Then, run a command

to load the host software. Set Software type to BIN (software), and then set Software

version. You can click or press F9.

LOD SOFTWARE: SV="BSC6000V900R003C01";

2. On the MML client, observe the load progress. After the load is complete, the load result

is displayed on the MML client.

3. If the returned message indicates that the software fails to be loaded on some certain

boards, repeat step 1 through step 3. Because incremental load is achieved, the system

reloads software to only the boards where software fails to be loaded. If several attempts

for loading the software to some boards are made but all the attempts fail, check the

reason why the loading fails and perform the corresponding processing.

NOTE

If the OMLs on the Ater interface are in satellite transmission mode, the transmission of the

OMLs on the Ater interface is slow due to time delay. Therefore, the host software may not be

successfully loaded on the boards configured on the MSC side online at a time. In this case,

you can perform the load operation several times until all the boards are successfully loaded

with the host software.

4.4 Loading the Level 2 BIOS to a Board Online

NOTE

1、Before loading the level 2 BIOS, check the LMT device panel to ensure that all the boards

are operational.

2、When loading the level 2 BIOS online, select the corresponding level 2 BIOS version. The

version may be the same as the previous version.


Page 27 of 84

INTERNALUSE


Upgrade Guide

3、The BIOS upgrade consists of the upgrade of BIOS0 and BIOS1. The BIOS upgrade on the

M2000 or MML client refers to the upgrade of BIOS1, which is level 2 BIOS. Level 2 BIOS

is upgraded on the M2000 or MML client unless otherwise specified. The rollback of the

BIOS indicates the following: If the board was not powered off and the number of startup

failures reaches 200 after level 2 BIOS is upgraded, the original BIOS (BIOS0) is used to

perform startup. If the board was once powered off and the number of startup failures reaches

10 after level 2 BIOS is upgraded, the original BIOS (BIOS0) is used to perform startup.

The online loading of the level 2 BIOS indicates that the level 2 BIOS file in later version is

loaded on boards through the MML client and the GBAM/GOMU.

4.4.1 Loading Level 2 BIOS File Online

The level 2 BIOS file is loaded from the GBAM to boards through the M2000 or the MML

client.The detailed procedures are as follows:

1. On the MML client, choose MML Commands > System Management > Software

Management > Version Management > Load Software Online. Then run a command

to load the host software. Select a BIOS (BIOS file) and specify the version number. Set

the Software type and Software version. You can click or press F9.

LOD SOFTWARE: SWT=BIOS, SV="BSC6000V900R003C01";

2. On the MML client, observe the load progress. After the load is complete, the load result

is displayed on the MML client.

3. If the returned message indicates that the software fails to be loaded on some certain

boards, repeat step 1 through step 2. Because incremental load is achieved, the system

reloads software to only the boards where software fails to be loaded. If several attempts

for loading the software to some boards are made but all the attempts fail, check the

reason why the loading fails and perform the corresponding processing.

4. After the load is complete, confirm that the level 2 BIOS of all the boards is upgraded to

the correct version. If the version of the level 2 BIOS is incorrect, the board may not be

started.

The method is as follows:


Page 28 of 84

INTERNALUSE


Upgrade Guide

Step 1 On the LMT, choose BSC Maintenance > Query Software > Query Board Version Information.

Step 2 In the displayed Query Board Version Information dialog box, click the Software and Hardware Information tab.

Step 3 On the Software and Hardware Information tab page, choose each subrack (except subrack 12) in the Subrack drop-down list box in turn.

Step 4 Click Query to check the Level 2 BIOS Version of all the boards so that the level 2 BIOS version is confirmed to be correct.

----End

NOTE

1. If the loading of the level 2 BIOS fails due to system power failure or board resetting,

repeat the loading steps after the related fault is rectified. After the loading, if the

activated board cannot be started normally, replace the board. You can use an internal

tool to upgrade the replaced board for later use. The level 2 BIOS must be upgraded

when the system is in stable running.

2. If a board fails to be started, the BIOS may roll back to BIOS0.If the rollback fails due

to the incompatible BIOS0, the board cannot be started. After the rollback of the BIOS

and the failed initiation, the fault cannot be rectified. The board must be replaced.

3. For the XPU board, if the BIOS is upgraded from a version earlier than 205 to version

205, the board may be reset or suspended abnormally after the BIOS upgrade and the board

restart. The reason is that one BUG exists in the BIOS (version 205) of the XPU. Therefore,

after the board is restarted, you must remove the XPU board, and then reinsert the powered-

off board regardless of whether the restart is successful.

4.5 Upgrading the LMT

NOTE

Before installing the later version, you need to exit the LMT in earlier version firstly if the

LMT is open. You can exit the LMT by choosing System > Exit.

Install the new version LMT reference to 《BSC6000 V900R003 LMT Administration Guide》.


Page 29 of 84

INTERNALUSE


Upgrade Guide

4.6 Upgrading the Configuration Data File

4.6.1 Upgrading the Configuration Data File

1. Application Scenario：

The configuration data before the upgrade can be used.

2. Software and Hardware Preparations：


and can log in to the GBAM through the network.

An LMT in later version is available.

3. Upgrade Procedure

Determine whether it is the external GBAM mode or internal GOMU mode after the

upgrade. If it is the external GBAM mode, choose GBAM when logging in to the

LMT in later version in offline mode. If it is the internal GOMU mode, choose

GOMU.

The offline logging in to the LMT is successful. On the LMT, choose

Configuration > Open Local Data File. In the displayed dialog box, choose the

file saved in Backing Up Data Configuration Files

Click Yes to perform data upgrade. Wait until a message box prompting that the

upgrade is successful is displayed, as shown in the following figure.


Page 30 of 84

INTERNALUSE


Upgrade Guide

Click OK.The configuration data file is upgraded.。

On the LMT, choose Configuration > Back Up > Back Up Local Data. Data can

be verified globally. If the verification fails, data cannot be backed up. The error

information is listed in the dialog box. You need to reconfigure data to meet the

verification rules. Then, choose Configuration > Back Up > Back Up Local Data

again. If the check is successful, choose a backup path and input the file name to

perform the backup. The default directory (LMT installation directory) for file

backup is \BSC6000V900R003C01\BackupCfgData.

CAUTION

The function of the SCU port switch in BSC6000V900R001 is different from that in

BSC6000V900R003. For the BSC6000V900R001, all the SCU ports are available without

configurations and the SCU port switch is only used to determine whether to report the port

alarm. For the BSC6000V900R003, the SCU port switch is the enabling switch of the port

and is bound with the alarm switch. Therefore, after the data upgrade from

BSC6000V900R001 to BSC6000V900R003 is complete, you should check the port

configurations of all the SCU boards. If a certain port is used, the switch corresponding to the

port should be enabled manually. If the port is not used, the switch should be disabled to avoid

possible alarms.


Page 31 of 84

INTERNALUSE


Upgrade Guide

4.6.2 Prepraring the Configuration Data File

1. Application Scenario:

The office is new and there is no original configuration data.

2. Software and Hardware Preparations:


and can log in to the GBAM through the network.

The LMT installation package matches the server software that is running on the

GBAM.

3. Operation procedure:

Install the LMT software on a PC. For details, refer to "Upgrading the LMT."

Start the LMT in offline mode.

Perform offline configurations on the LMT based on the data provided by the

customer.

After the configuration is complete, on the LMT, choose Configuration > Back Up

> Back Up Local Data to save data.

----End

4.7 Upgrading GBAM and Single GOMU

CAUTION

1、Power-on and power-off of the GOMU board: Slightly loosen the handles on the upper and

lower ends of the GOMU board without removing the board. The blue offline LED on the

panel flashes. Remove the GOMU board until the offline LED is on. Do not use reset or

shutdown button on the panel of the GOMU board to reset or power off the board.


Page 32 of 84

INTERNALUSE


Upgrade Guide

2、After the OMU is successfully upgraded, log in to the LMT using user name admin and

password admin. Determine whether to reset the password based on your requirement. After

section 4.9 "Restoring Data", all the user names and passwords are restored to the data before

the upgrade.

4.7.1 Operation Preparations

For the operation preparations, you need to check the current system as follows:

1. Use the putty tool and log in to the GBAM/GOMU as user root. The IP address indicates the IP address of the external network.

2. Check the time zone by running the date +%z command on the putty.

3. Check the time by running the date command on the putty.

----End

NOTE

In step 1, for the GOMU, the IP address of the external network indicates the IP address that is permanently occupied by the active OMU. The LMT/M2000 can connect with the OMU Core through this IP address.

Steps 2 and 3 are used to confirm the time zone and time of the current GBAM/GOMU.

Perform the upgrade only after the confirmation. If the time zone and time are incorrect,

perform the adjustment by referring to the BSC6000 V900R003 GOMU Management

Guide.

1. Stopping the OMU Software:

# omuctrl stop

Enter “y” or “yes”. The following diagram shows the stopping of the OMU software.

2. Uninstalling the Existing Software of the GBAM OMU


Page 33 of 84

INTERNALUSE


Upgrade Guide

Run the following command on putty to query the OMU software installed:

# rpm -q omu

Upgrading versions before B070 the command will returen two rpm

install record because of a known bug, so twice rpm uninstall operation is

needed.

Run the following command on putty to uninstall the OMU software:

# rpm -e omu-9.3.1-61

# rpm -e omu-9.3.1-62

在 putty 上输入命令

# omuctrl status

Run the following command on putty to check the running status of the OMU software:

3. Manually Deleting the Files not Uninstalled

To delete the /BSC6000/bscswm folder and all the subdirectories and files under the

/BSC6000/bscswm directory, run the following command on putty:

# rm /BSC6000/bscswm -R

To delete the subdirectories and all the files under the /BSC6000/data directory, run the

following command on putty:

# rm /BSC6000/data/* -R

NOTE

Keep all files in the install directory for version rollback.


Page 34 of 84

INTERNALUSE


Upgrade Guide

If there are other folders or files except data and install (if there are files under

the btsswm directory, the directory exists) under the BSC6000 directory,

confirm whether these folders or files are required. If required, back up them to

your local PC. Huawei recommends you to delete all the files irrelevant to the

version on the GBAM.

Ensure that all the files related to the old data are deleted before the upgrade. If

there are such files, the LMT cannot connect to the GBAM after the OMU

software is installed.

4.7.2 Upgrading the GBAM

Reference 《BSC6000 V900R003 GBAM Administration Guide》to install the new version

OMU software.

4.7.3 Upgrading the GOMU

Reference 《BSC6000 V900R003 GOMU Administration Guide》to install the new version

OMU software.

NOTE

If a single GOMU is connected through the IP address of the external network, the IP address

is released when you run the omuctrl stop command to stop the OMU software. Therefore,

you must ensure that the GOMU can be connected through the commissioning of the IP

address.

4.7.4 Verify OMU version

Use the upgraded LMT to log in to the OMU. The menu path is Help > About. View the

version information. Press Ctrl+Shift+F12 to query the information on the B version, which

is the current version.


Page 35 of 84

INTERNALUSE


Upgrade Guide

4.8 Upgrading Active/Standby GOMU

NOTE

During the upgrade of active/standby GOMU, if you run the omuctrl stop command, you

must not perform other operations until the implementation of the command is complete. You

must not press the CTRL+C buttons to terminate the implementation of the command.

Otherwise, the IP address of the external network may not be used for communication.

The following describes how the later version can be upgraded when the active/standby

GOMUs run normally. n general, you should upgrade the two GOMUs respectively and

always upgrade the current standby GOMU.

1. On the putty, connect the active OMU through the IP address of the external network.

2. Set the backup switch to forbidden state and view the status of the local end by running

the cd /BSC6000/bscswm/omuroot/daemon, ./omutool backup disable, and ./omutool

status commands.

3. Query the IP address of the peer end by running the ./omutool status -peer command.

# ./omutool status -peer


Page 36 of 84

INTERNALUSE


Upgrade Guide

NOTE

If the query fails, you can infer that the backup channel is faulty. Check whether the standby board is running. If the standby board is not running, you need to run it.

If the standby board is running, you can infer that the backup channel is faulty and upgrade

cannot be performed. You can contact the local Huawei office for technical support.

4. Check whether the time zone and time of the active board are correctly set by referring to

section 4.7.1 "Operation Preparations."

# date +%z

# date

5. If file/root/.ssh/known_hosts exist on active OMU borad, run the follow command

to delete it.

# rm -f /root/.ssh/known_hosts

6. Run the ssh command (ssh 192.168.10.123) to connect the standby board (the IP address

of the standby board is the IP address of the peer end described in step 3).

# ssh 192.168.10.123

If the GOMU was once replaced, you may see the following print information.


Page 37 of 84

INTERNALUSE


Upgrade Guide

Delete the /root/.ssh/known_hosts file, and then perform another connection.

7. Check whether the time zone and time of the standby board are consistent with those of

the active board. In case of inconsistency, perform adjustment by referring to section

4.7.1 "Operation Preparations."

# date +%z

# date

8. If file/root/.ssh/known_hosts exist on standby OMU borad, run the follow command

to delete it.

# rm -f /root/.ssh/known_hosts

9. Back up the earilier version install package, and copy the new version from actived

OMU board，do as follows:

# cd /BSC6000/install

# rm rpmbak -rf

# md rpmbak


Page 38 of 84

INTERNALUSE


Upgrade Guide

# mv * rpmbak/

scp 192.168.10.121:/BSC6000/install/* .

# To install OMU software on standby board, refer to sections in《BSC6000

V900R003 GOMUAdministration Guide》.

NOTE

The active and standby OMUs have different versions, so the newly started OMU Local on

the standby board is always reset.

10. After the OMU software of the standby board is started, run the exit command to quit the

connection and to return to the connection on the active OMU.

# exit

11. Check that the status of the switchover switch is ON.

# cd /BSC6000/bscswm/omuroot/daemon

# ./omutool setswap enable

# ./omutool status

The following figure is an example.


Page 39 of 84

INTERNALUSE


Upgrade Guide

12. Stop the running of the OMU software on the current active OMU by running the

omuctrl stop command. The fault switchover is caused. After the standby board

becomes active, the IP address of the external network is switched to the new active

OMU.

# omuctrl stop

According to the prompted message, input yes (case sensitive) to stop the operation of the

OMU software, and during the process, the putty is disconnected with the OMU. Wait for a

period of time and then ping the IP address of the external network again.

NOTE

If the upgraded GOMU cannot be started and the IP address of the external network cannot be

pinged, you can infer that the upgrade fails. Then contact the local Huawei office for technical

support.

13. After the IP address of the external network is pinged, run the ssh command to connect

the new standby board.

# ssh 192.168.10.121

# To install OMU software on standby board, refer to sections in《BSC6000

V900R003 GOMUAdministration Guide》.


Page 40 of 84

INTERNALUSE


Upgrade Guide

14. After the standby board is installed, run the exit command to return to the connection on

the active board. Turn on the backup switch by running the cd

NOTE

After the OMU is successfully upgraded, log in to the LMT using user name admin and

password admin. Determine whether to reset the password based on your requirement. After

section 4.9 "Data Restoration", all the user names and passwords are restored to the data

before the upgrade.

15. Verfy OMU version

Figure 4-1 Use the upgraded LMT to log in to the OMU. The menu path is Help > About. View the version information. Press Ctrl+Shift+F12 to query the information on the B version, which is the current version.

---End

4.9 Data Restoration

CAUTION

For the releases later than R3C01B060, the system performs a license check before the

recovery of data configurations.


Page 41 of 84

INTERNALUSE


Upgrade Guide

1． Log in to the LMT in later version, and then connect the LMT to the GBAM/GOMU.

2．On the LMT, configure the originating signaling points and the destination signaling

points online and configure the relation between signaling points for subrack 0 according

to the license file.

3．On the LMT，Select the software license file to download and activate. Follow the

wizard to complete the activation.

NOTE

Before downloading a license, check the length of the license file name. The length of the

license file name should not exceed 31 characters. The recommended license file name is in

BSC name_yyyymmdd.dat format (for example, AlexBsc1_20070201.dat). The license file

name must be unique. "BSC6000" and the serial number given from the license distribution

center are not contained in a BSC6000 license file name

Save the software license file to the root directory of the LMT software installation

in later version, that is, \Common\SWM\License.

On the LMT in later version, choose BSC Maintenance > Maintenance License >

Download License. Select the software license file to be downloaded. Follow the

wizard to complete the download. The wizard is shown as follows:


Page 42 of 84

INTERNALUSE


Upgrade Guide

To activate the license, choose BSC Maintenance > Maintenance License >

Activate License. Select the software license file to be activated. Follow the wizard

to complete the activation.The wizard is shown as follows:

4．On the LMT，Choose Configuration > Load and Restore.

5．On the LMT，Select the Restore with local file option button. Select a data file from the

File On Local list. The data file is the backup data file that is in described in "Backing Up

Data Configuration Files."

NOTE

Ensure that the files to be restored are installed in the \BSC6000V900R003C01\

BackupCfgData directory, which is the LMT installation directory. Only the files in this

directory can be displayed in the list.


Page 43 of 84

INTERNALUSE


Upgrade Guide

6． Click Execute. A dialog box for confirmation is displayed, as shown in the following

figure:

7． Click Yes. If the restoration is successful, a message box is displayed, as shown in the

following figure.


Page 44 of 84

INTERNALUSE


Upgrade Guide

8．After the data is reloaded, the system is reset and the LMT is disrupted. A message box is

displayed, as shown in the following figure.

If the restoration fails, you are prompted that the restoration is faulty.

----End

NOTE

During the upgrade, do not perform consistency check or synchronization.

The consistency check and synchronization function is used when the

system is running normally. The function is used to check the data

consistency between the OMU and the board. In case of inconsistency,

perform data synchronization to ensure the data consistency between the

OMU and the board.

Through step 3, you can select a valid data file and restore the data.

You can click Detail information to view the detailed information on the

data file.

Step 3 can be divided into two substeps: select Load file from local to GBAM, and then

select Restore with GBAM file.

After you perform step 4, the GBAM core process is reset automatically. For the description

of board reset, refer to section 4.10 "Upgrading Board Software." You need to exit the LMT

and log in to it again.

If the data file used for data restoration is the data file of the system before the upgrade, the

information such as user authorities and the password is retained.


Page 45 of 84

INTERNALUSE


Upgrade Guide

4.10 Upgrading Board Software

4.10.1 Preparations

1. Confirm that the hardware and software are normal.

The OMU software is successfully installed. The OMU and the boards run normally.

2. Confirm that the data configuration is correct.

Confirm that the configuration data is consistent with that provided by the operator. The load

control parameters of all the boards are Auto.

4.10.2 Procedures for the Upgrade

Use the putty tool to log in to the OMU, and then perform the following steps:

1. Access the upgrade progress directory by running the follow command.

# cd /BSC6000/bscswm/omuroot/upgrade

2. Obtain the IP address used in the upgrade progress on the local OMU by

running the follow command.

# ifconfig | grep 192.168.10

3. Run the follow command to reset a board (assume that the obtained IP address

is 192.168.10.121).

# ./rus_sendreboot.bin 192.168.10.121 80.0.1.129 80.0.1.193

Explanation: Three parameters should be carried in the rus_sendreboot.bin command

supplied in the upgrade progress.

The first one is the local IP address, and you can run the ifconfig | grep 192.168.10 command

to view the IP address used in the upgrade process. The second one is the IP address of the

SCU in slot 6 of the receive party. The third one is the IP address of the SCU in slot 7 of the

receive party.


Page 46 of 84

INTERNALUSE


Upgrade Guide

CAUTION

After you run the ifconfig | grep 192.168.10 command, two IP addresses are displayed,

which indicates that the configuration of IP addresses are exposed to risks. You need to

modify the debug IP address to non 192.168.10 network segment or delete the

redundant IP addresses.

4. Each board starts to be reset after 15 seconds. The reset board runs the

upgraded software version.

----End

4.10.3 Confirming the Board State

1. Log in to the LMT in later version, and then connect the LMT to the GBAM/GOMU.

2. Click the Progress Window icon . Several tabs that display the progress of different

objects are available at the bottom of the window.

3. Click the BSC Load Progress tab.

4. On the BSC Load Progress tab page, the subrack numbers and slot numbers of the

current loaded boards as well as the loading progress are displayed. When the loading

progress is 100%, check whether the boards on the BSC device panel are normal.

4.10.4 Exception Handling

If the load progress of a certain board is not displayed, this board is not started normally.

To handle it, do as follows:

1. Check whether the physical connections and the OMLs on the Ater interface are correct.


Page 47 of 84

INTERNALUSE


Upgrade Guide

For details, refer to the HUAWEI BSC6000 Base Station Controller Hardware Installation

Guide and the HUAWEI BSC6000 Base Station Controller LMT User Guide.

2. For the level 2 BIOS versions earlier than 105, the GEIUT/GOIUT on the Ater interface

in the remote subrack does not support optical transmission or satellite transmission. If

the Ater interface needs to use optical transmission or satellite transmission for

networking, upgrade the level 2 BIOS to version 105 or later versions. Otherwise, the

remote subrack may not be started. Method to avoid this problem: For optical

transmission mode, configure the OMLs on the Ater interface on ports 0 and 62. After

the board in the remote subrack is started, upgrade the level 2 BIOS to version 105. If

this method cannot be used or if the remote links are in satellite transmission, the Ater

interface board in the remote subrack must use the board where the level 2 BIOS version

is 105, so that the board in the remote subrack can be started after the later version is

activated.

3. If the operating status of a board on the LMT is abnormal, choose Alarm Maintenance

> Browse Alarm to check whether the loading board software failed alarms (ID: 21019)

are reported.

If there are such alarms, refer to the BSC6000 Alarm Handling on the BSS Help System

window to handle them.

4. If a board is faulty, restart it or replace it. If the problem persists, contact the local

Huawei office for technical support.

----End

4.11 Activating the Software License

1. To activate the license, choose BSC Maintenance > Maintenance License > Activate

License. Select the software license file to be activated. Follow the wizard to complete

the activation.The wizard is shown as follows:


Page 48 of 84

INTERNALUSE


Upgrade Guide

2. To query the license, choose BSC Maintenance > Maintenance License > Query

License. Click Query. Fill the viewed configuration information into the Before the

Upgrade column in Appendix F "Checklist for the Configuration Information on

License Files."

NOTE

The software license is not delivered with the version. You have to apply for it from Huawei.


Page 49 of 84

INTERNALUSE


Upgrade Guide

5 Installing the M2000 Adaptation

Layer

Install M2000 Adaptation Layer reference to 《M2000 Adaptation Version Installation Guide(Only

for M2000 R6 Common Version)》.

6 Remote Upgrade Operations

NOTE

1、 The remote upgrade on the M2000 indicates the integrated upgrade, which contains

the upgrade of OMUDaemon, OMUCore, OMULocal, and SMU.

2、 Remote upgrade on the M2000 applies to only the upgrade of a version after

BSC6000V900R003C01.

3、Do install the M2000 adaptation layer of new version, otherwise, M2000 will not

connect to NE again after OMU software being upgraded. Subsequent commands

will not be executed and upgrade will fail.


Page 50 of 84

INTERNALUSE


Upgrade Guide

4、During the upgrade, do not change the OMU time, otherwise, the upgrade may fail

due to overtime.

6.1 Preparations

1. For the preparation for the software require in the upgrade, refer to section 3.4 "Required

Software in the Preparations for upgrade."

2. For the backup of the configuration data files of the BSC6000 equipment before the

upgrade, refer to section 4.2 "Backing Up Data Configuration Files."

3. For the generation of the configuration data files in later version, refer to section 4.6

"Upgrading the Configuration Data File." You need to save the configuration data files in

later version as lmt.dat for later use in the subsequent upgrade.

6.2 Procedures for the Upgrade

6.2.1 Creating the NE Objects

On the iManager M2000 Mobile Element Management System window, create the NE objects based on

the following steps:

Step 1 Right-click the iManager M2000 Mobile Element Management System window and choose Create Topo Object on the shortcut menu.

Step 2 The IP address is the external IP address of NEs. The Name is an NE name set by a user. Click OK. Assume that the NE name is BSC6000B022, which is used to identify NEs in subsequent operations.

Step 3 Click OK.

---End

6.2.2 Uploading Software and Data

Step 1 Copy the upgrade package (containing omu-9.3.x-yy.i586.rpm and boardfile.9.3.x.yy.zip), the version configuration table (verpkg.xml) of the upgrade package, the XML files for flow control (upgradecfg.xml) required by the M2000, and the version configuration table


Page 51 of 84

INTERNALUSE


Upgrade Guide

(vercfg.xml) that contains the information on the previous four types of files to the local hard disk of a PC where the M2000 client runs, for example, E:\upgradepkg.

Step 2 Copy the data file lmt.dat in later version to the local hard disk of a PC where the M2000 client runs, for example, E:\data. The file name must be lmt.dat.

Step 3 Upload software and data.

Choose Software > File Transfer Wizard/.

In the Direction drop-down list box, choose From GUI To Server.

In the Server Path drop-down list box, choose BSC6000 > Software to upload the

software in upgrade package. Choose BSC6000 > data > BSC6000B022 to upload

data

Select the path where the uploaded file is contained. Click Finish to perform the

upload.

Observe the progress to wait for the completion of the upload.

----End

6.2.3 Performing the Upgrade

The upgrade is performed as follows:

Step 1 Choose Software > NE Upgrade Wizard > Upgrade BSC6000. Then, choose BSC6000B022 and click OK.

Step 2 Select the version to be upgraded. Click Next.

Step 3 On the BSC6000 Upgrade Wizard dialog box, click Next to perform the upgrade. Observe the progress and result of each step.

---END

In the Upgrade Execution step, complete the upgrade of OMUDaemon, OMUCore,

OMULocal, and boards.

If you do not upgrade the OMU in remote upgrade mode, click Exit to exit the upgrade.

Then, perform the upgrade based on the operation methods described in the previous sections.

The following steps are displayed In the BSC6000 Upgrade Wizard dialog box:

Select Upgrade Version is used to select the version to be upgraded.

The user selects the correct version to perform the upgrade.

Download Software is used to download software.


Page 52 of 84

INTERNALUSE


Upgrade Guide

This step can be skipped, however, you are advised not to skip it. If you are sure that the

software in the version to be upgrade is successfully downloaded, the step can be skipped.

Otherwise, the upgrade cannot be performed.

If the previous upgrade is not complete or is abnormal, the upgrade progress is not closed. Thus, the

software fails to be downloaded. The human interference on the local end is necessary.

Download New Version Data is used to download the data in later version.

If you are sure that the data in the version to be upgraded is downloaded, the step can be

skipped. If such data is not downloaded, but you skip the step, the upgrade fails.

Load Software and BIOS is used to load software and BIOS.

In the step, the host software and level 2 BIOS are loaded online. In other words, Loading the

Host Software Online described in section 4.3 and Loading the Level 2 BIOS to a Board

Online described in 4.4 are complete in the step.]

In the BSC6000 Upgrade Wizard dialog box, you can observe the load progress and result.

If the load fails, repeat the step. Because incremental load is achieved, the system reloads

software to only the boards where software fails to be loaded.

If several attempts for loading the software to some boards are made but all the attempts fail,

only the human interface on the local end works. Then, check the reason why the loading fails

and perform the corresponding processing.

Upgrade Execution is used to perform the upgrade.

The upgrade of the OMU and the activation of a board are contained in this step. In the

BSC6000 Upgrade Wizard dialog box, you can observe the load progress and result.

If the upgrade incurs an error, the First, Retry, and Rollback buttons are displayed in the

BSC6000 Upgrade Wizard dialog box.

Click First. The whole process of the upgrade can be performed again.

Click Retry. The upgrade continues to be performed from the point where the error occurs.

You are advised to click Retry when an error occurs.

Click Rollback. The system is rolled back to the version before the upgrade. After the

rollback, if you need to perform the upgrade again, restart the BSC6000 Upgrade Wizard.

You need to perform the upgrade from the Select Upgrade Version step.


Page 53 of 84

INTERNALUSE


Upgrade Guide

The activation of a board requires your confirmation. When you perform this step, the

Confirm and Rollback buttons are displayed in the BSC6000 Upgrade Wizard dialog box.

Click Confirm. The board is reset and the version is upgraded to a new one.

Click Rollback. The system is rolled back to the version before the upgrade.

After the rollback, if you need to perform the upgrade again, restart the BSC6000 Upgrade

Wizard. You need to perform the upgrade from the Select Upgrade Version step.

Upgrade Submission is used to submit the upgrade.

If there are active and standby OMUs, you need to upgrade the standby OMU. If the standby

OMU is faulty, the step fails. The human interference on the local end is necessary.

Upgrade Rollback is used to roll back the upgrade.

If the rollback fails, the First and Exit buttons are displayed in the BSC6000 Upgrade

Wizard dialog box.

Click First. The rollback is performed again. If several attempts for the rollback are

made but all the attempts fail, click Exit to exit the BSC6000 Upgrade Wizard

dialog box. The human interference on the local end is necessary.

6.2.4 Download and Activate License

To download and activate the license, do as follows:

Step 1 Prepare the license file.

Refer to section 3.5 "Preparing the License." Copy the license file to the local hard disk of a

PC where the M2000 client runs, for example E:\license.

Step 2 Upload the license file.

Refer to section 6.2.2 "Uploading Software and Data." Click License.

Step 3 Download and activate the license.

Choose Software > Browser. The iManager M2000 Mobile Element

Management System window is displayed as follows:


Page 54 of 84

INTERNALUSE


Upgrade Guide

Click License.

Click Download From Server to download the license.

Click Show License Detail to view the license information.

Click Activate to activate the license.


Page 55 of 84

INTERNALUSE


Upgrade Guide

7 Upgrade Verification

7.1 Verification Checklist

Table 7-1 Checklist for the verification items

No. Verification Item Requirement No.

1 Verification after the

upgrade

Use the checklist for the system

health to check that the verification

items are correct.

1

2 Site cleanup after the

upgrade

Clean up the site 2

7.2 Verification After the Upgrade

You need to perform the verification by referring to the following checklist. If you find any

abnormal situation, record it in detail.

1. Checking the version

Log in to the GBAM/GOMU through the LMT. The user name and the password

should be consistent with those defined in the data used for data restoration.


Page 56 of 84

INTERNALUSE


Upgrade Guide

On the LMT, choose Help > About. Press Ctrl+Shift+F12 to check the current

LMT version.

On the LMT, choose Help > About. Press Ctrl+Shift+F12 to check the current

GBAM/GOMU version.

On the LMT, choose BSC Maintenance > Query Software > Query Board

Version Information. Set the filtering conditions for the corresponding board. On

the Software and Hardware Information tab page, click Query. Press

Ctrl+Shift+F12 to check the software version of each board.

----End

2. Checking the Running of Tools

Check whether the LMT runs normally.

Check whether the alarms and traffic statistics can be viewed on the M2000 (The

performance measurement results are correctly reported to the M2000).

Check whether the configuration data is consistent with that before the upgrade.

----End

3. Checking the Operating Status of NEs

Check that there is no abnormality alarm on the LMT or on the M2000.

On the LMT, choose BSC Maintenance > Maintain Device > Query BSC Board

Clock State and BSC Maintenance > Maintain Device > Query BSC Board

Reference State to check the system clock status, board clock status, and BTS clock

status (fast pull-in or locked).

On the LMT, choose BSC Maintenance > Maintain Transmission and Signaling

> Maintain SCCP to check whether all the links on the A interface are normal.


> Maintain LAPD Link to check whether all the LAPD links are normal.

On the LMT, choose BTS Maintenance to check whether the BTS software

versions, BTS board status, and TRX channel status are normal


to check whether the E1 port is normal.


Page 57 of 84

INTERNALUSE


Upgrade Guide

On the LMT, choose BSC Maintenance > Maintain User Resource to check

whether all the CICs, PCICs, Abis timeslots, Ater timeslots, and TC resources are

normal.

After the GMPS is running for 21 minutes, choose Alarm Maintenance > Browse

Alarm to check that there are no License block alarms about BTSs, cells, or TRXs.

4. Checking the Services

Basic call procedure test: On the LMT, use an MS to call another MS or a fixed-line

phone. Perform the interface tracing function of the LMT to check whether the

location update procedure and the whole signaling transmission procedure are

complete. In addition, the conversation quality can be viewed on the LMT.

The traffic statistics counters on the M2000 are normal.

The analysis shows that the logs are normal: CHR, TC-CHR (The symptoms, such

as one-way audio and no audio do not occur), running log, and debug log (browsing

only).

Make test calls. For details, refer to the information on dialing tests.

NOTE

For detailed information on system health check after the upgrade, refer to Appendix E

"Checklist for System Health After the Upgrade."

7.3 Completing the Upgrade

7.3.1 Sanitation in the Environment After the Upgrade

Succeeds

1. If no errors occur one week after the upgrade, clean up the site.

After the upgrade, dispose of the sundries and ensure that the equipment room is

clean and tidy.

Remove the redundant materials.

Sort the data (such as files) generated during the upgrade.


Page 58 of 84

INTERNALUSE


Upgrade Guide

2. If errors are detected during verification and the errors cannot be rectified, roll back the

version to restore system services to normal. For details, refer to Version Rollback


Page 59 of 84

INTERNALUSE


Upgrade Guide

8 Version Rollback

CAUTION

Version rollback is performed only when the version verification indicates that the upgrade fails. For details of failure handling, refer to the troubleshooting part in the operation procedure.

The current level 2 BIOS is compatible with the host software in earlier version. Therefore, you do not need to roll back level 2 BIOS during the version rollback.

8.1 Precautions

8.2 Rollbacking OMU Software

The OMU software in earlier version is installed as follows:

1. Log in to the GBAM/GOMU as user root.

2. Shutdown the omu by input follow command:

# omuctrl stop


Page 60 of 84

INTERNALUSE


Upgrade Guide

3. Uninstall the OMU software on the GBAM/GOMU. Then, run the follow command on

putty.

# rpm -e omu

4. Use the putty tool to manually delete the files that are not uninstalled.

NOTE

Because the data directory is associated to the partition during the installation of the operating system, the data directory cannot be deleted.

Keep the install directory and the files in it for version rollback.

If the btsswm directory exists, do not delete it. If you need to delete it, ensure that the files in this directory are backed up to the local hard disk or these files are not used in later version.

If the following folders to be deleted do not exist in the /BSC6000 directory, you do not have to run the following commands.

a) Delete a specified directory and its subdirectories and files in the /BSC6000 directory.

Delete the /BSC6000/bscswm directory and all the subdirectories and files in the

/BSC6000/bscswm directory, run the follow command on putty.

# rm -R /BSC6000/bscswm

Delete the subdirectories and all the files in the /BSC6000/data directory, run the follow

command on putty.

# rm -R /BSC6000/data/*

b) Check after the deletion.

Run the follow command on putty to access the /BSC6000 directory.

# cd /BSC6000

Run the ls command on putty to confirm that there is no bscswm subdirectory in the

/BSC6000 directory.

# ls

Run the cd data command on putty to access the data directory.

# cd data


Page 61 of 84

INTERNALUSE


Upgrade Guide

Run the ls command on putty to confirm that there is no subdirectory or file in the data

directory.

# ls

5. Install the OMU softear of earilier version reference to 《BSC6000 V900R003 GOMU

Administration Guide》or 《BSC6000 V900R003 GBAM Administration Guide》in actual

situation.

8.3 Restore old data and old board software

1. Log in to the GBAM/GOMU as user root to set the authority of the /BSC6000 by

running the follow command:

# chmod 777 /BSC6000 -R

2. Restore old data.

Copy all the files backed up in the data/ folder to the directory /BSC6000/data through

samba. For detailed backup method, refer to "Backing Up Data." Overwrite the existing

folders, as shown in the following figure:

3. Restore the old board software.

Change the name of the bscswmb0xx directory that is backed up to a local hard disk into

bscswm and copy it to the /BSC6000 directory through the Samba. Overwrite the existing

folders, as shown in the following figure:


Page 62 of 84

INTERNALUSE


Upgrade Guide

4. Restore the authority control by running the follow commands.

# chown root /BSC6000 -R

# chmod 755 /BSC6000 -R

8.4 Starting the OMU Software

1. To start the OMU software process on the GBAM/GOMU by running the follow

command on putty.

# omuctrl start

2. To view the operating status of the OMU software on the GBAM/GOMU by running the

follow command on putty.

# omuctrl status

8.5 Rolling Back Board Software

1. Reset the entire system by running the follow commands:

＃ cd /BSC6000/bscswm/omuroot/upgrade

＃ ifconfig | grep 192.168.10

＃ ./rus_sendreboot.bin 192.168.10.121 80.0.1.129 80.0.1.193

2. Monitor the board loading status until the all the boards are operational.


Page 63 of 84

INTERNALUSE


Upgrade Guide

Log in to the GBAM/GOMU through the LMT. Click the Progress Window icon .

Several tabs that display the progress of different objects are available at the bottom of the

window. Click the BSC Load Progress tab. On the BSC Load Progress tab page, the

subrack numbers and slot numbers of the current loaded boards as well as the loading

progress are displayed. When the loading progress is 100%, check whether the boards on the

BSC device panel are normal.

The following figure shows the progress window.

NOTE

If no loading progress is displayed after you log in to the GBAM through the LMT in later version, check whether the out-of-synchronization alarm is generated by choosing Alarm Maintenance > Browse Alarm on the BSC6000 Local Maintenance Terminal.

If the out-of-synchronization alarm is generated, reset all the subracks by choosing BSC Maintenance > Maintenance Device > Reset Subrack on the BSC6000 Local Maintenance Terminal.

8.6 Rolling back LMT

Uninstall the new version LMT, and install the earilier version LMT refer to its upgrade instructions.

8.7 Verification

For details, refer to "Checking the version" described in "Verification After the Upgrade."


Page 64 of 84

INTERNALUSE


Upgrade Guide

9 FAQ

9.1 FAQ Index

Table 9-1 FAQ list

Number Description Reference

FAQ1

What you should pay attention to

when installing the LMT in

version B or version SP?

9.2 FAQ1

Description:

What you should pay attention to when installing the LMT in version B or version SP?

Reply:

To upgrade the LMT from version B to version SP, back up the installation directory of

version B, because version SP may replace version B.


Page 65 of 84

INTERNALUSE


Upgrade Guide

A Upgrade Preparations

Item Description Remarks

Name of the device to be

upgraded

Place where the device to

be upgraded is located

Permitted upgrade date

and time

Upgrade the device when the

traffic volume is low

Customer's requirements

for the upgrade

Version before the

upgrade

BIOS version

Host software version

Patch information

Version after the upgrade

BIOS version


Page 66 of 84

INTERNALUSE


Upgrade Guide

Item Description Remarks

Host software version

Patch information

Requirements for the

versions of other NEs

Software required for the

upgrade

Data required for the

upgrade

If the configuration data remains

unchanged, you do not have to

prepare the data.

Hardware materials


If the hardware does not change

during the upgrade, you do not

have to prepare hardware

materials.

Tools required for the

upgrade

Special tools for the upgrade,

mobile equipment, SIM card, and

Ethernet cables

Upgrade personnelPersonnel from both the customer

and Huawei

Assistants

Maintenance personnel of other

NEs and network planning

personnel

VehicleVehicles are required for drive

test, if any.

Contact personName and telephone number of

the contact person


Page 67 of 84

INTERNALUSE


Upgrade Guide

B Upgrade Record

Site Name Upgrade Time

Version before

the upgrade

Version after the

upgrade

Upgrade

personnel

From the customer:

From Huawei:

Success or

failure

Operation Item Conclusion Troubleshooting

Check of the

operating status

before the

upgrade

Multiple IP addresses

Remote links

Current alarm

information

Cell status

Data consistency

Upgrade

procedures

Back up data

Download all the files

related to the current

version


Page 68 of 84

INTERNALUSE


Upgrade Guide

Upload the OMU

software installation

disk to the

GBAM/GOMU

Install the OMU

software onto the

GBAM/GOMU

Install the matching

version of the M2000

(server, client, and

adaptation layer)

Upgrade the matching

BTS version

Install the matching

LMT

Verification

after the

upgrade

Check current alarm

information

Check link status

Check versions

Make test calls


Page 69 of 84

INTERNALUSE


Upgrade Guide

C Checklist for Dialing Test

BTS Name

Test Time

Conclusion □Pass □Not Pass

Cell Name

Cell ID

main BCCH Frequency

Network Color Code (NCC)

BTS Color Code (BCC)

Test Item Test Result 备注

Speech: fixed-line phone

calling MS (GSM)

□Pass □NotPass □N/A

Speech: MS (GSM) calling

fixed-line phone



MS (GPRS)


Speech: MS (GPRS) calling

MS (GSM)



Page 70 of 84

INTERNALUSE


Upgrade Guide


MS (GSM)


VP: MS (GSM) calling MS

(GSM)


PS: PDP activation □Pass □NotPass □N/A

Conversation quality of

speech

□Good □Bad □N/A

Conversation quality of VP □Good □Bad □N/A

Communication quality of PS □Good □Bad □N/A

Call drop □Pass □NotPass □N/A

Soft handover □Pass □NotPass □N/A

RSCP (should be greater than

-70 dBm)

Ec/I0(should be greater than -

10 dB)

Signature of test personnel


Page 71 of 84

INTERNALUSE


Upgrade Guide

D Checklist for System Health

Before the Upgrade

Checklist for the state of each interface

SN SN SN SN

1. 1. 1. 1.

2. 2. 2. 2.

3. 3. 3. 3.

4. 4. 4. 4.

5. 5. 5. 5.

6. 6. 6. 6.

7. 7. 7. 7.

8. 8. 8. 8.

Tested by: Tested by:

Checklist for the operating status of the BTS

SN SN SN SN


Page 72 of 84

INTERNALUSE


Upgrade Guide

1. 1. 1. 1.

2. 2. 2. 2.

3. 3. 3. 3.


Checklist for operating status of boards

SN SN SN SN

1. 1. 1. 1.

2. 2. 2. 2.

3. 3. 3. 3.

4. 4. 4. 4.

5. 5. 5. 5.


Checklist for Alarm Information

SN SN SN SN

1. 1. 1. 1.

2. 2. 2. 2.

3. 3. 3. 3.

4. 4. 4. 4.

5. 5. 5. 5.

6. 6. 6. 6.



Page 73 of 84

INTERNALUSE


Upgrade Guide

Checklist for the M2000 Traffic Statistics Counters

SN SN SN SN

1. 1. 1. 1.

2. 2. 2. 2.

3. 3. 3. 3.

4. 4. 4. 4.

5. 5. 5. 5.

6. 6. 6. 6.

7. 7. 7. 7.

8. 8. 8. 8.

9. 9. 9. 9.

10. 10. 10. 10.


Checklist for the Operating Status of the GBAM/GOMU

SN SN SN SN

1. 1. 1. 1.

2. 2. 2. 2.

3. 3. 3. 3.

4. 4. 4. 4.



Page 74 of 84

INTERNALUSE


Upgrade Guide

E Checklist for System Health

After the Upgrade

Checklist for Clock Status

SN SN SN SN

1. 1. 1. 1.

2. 2. 2. 2.

3. 3. 3. 3.

4. 4. 4. 4.

5. 5. 5. 5.

6. 6. 6. 6.


Checklist for the state of each interface

SN SN SN SN

1. 1. 1. 1.

2. 2. 2. 2.

3. 3. 3. 3.

4. 4. 4. 4.

5. 5. 5. 5.


Page 75 of 84

INTERNALUSE


Upgrade Guide

6. 6. 6. 6.

7. 7. 7. 7.

8. 8. 8. 8.

9. 9. 9. 9.


Checklist for the operating status of the BTS

SN SN SN SN

1. 1. 1. 1.

2. 2. 2. 2.

3. 3. 3. 3.


Checklist for operating status of boards

SN SN SN SN

1. 1. 1. 1.

2. 2. 2. 2.

3. 3. 3. 3.

4. 4. 4. 4.

5. 5. 5. 5.

6. 6. 6. 6.


Checklist for Alarm Information

SN SN SN SN

1. 1. 1. 1.


Page 76 of 84

INTERNALUSE


Upgrade Guide

2. 2. 2. 2.

3. 3. 3. 3.

4. 4. 4. 4.

5. 5. 5. 5.


Checklist for the M2000 Traffic Statistics Counters

SN SN SN SN

1. 1. 1. 1.

2. 2. 2. 2.

3. 3. 3. 3.

4. 4. 4. 4.

5. 5. 5. 5.

6. 6. 6. 6.

7. 7. 7. 7.

8. 8. 8. 8.

9. 9. 9. 9.

10. 10. 10. 10.


Checklist for the Operating Status of the GBAM/GOMU

SN SN SN SN

1. 1. 1. 1.

2. 2. 2. 2.

3. 3. 3. 3.

4. 4. 4. 4.


Page 77 of 84

INTERNALUSE


Upgrade Guide


Checklist for Basic Service Test

SN SN SN SN

1. 1. 1. 1.


Checklist for Call Service Test

SN SN SN SN

1. 1. 1. 1.

2. 2. 2. 2.

3. 3. 3. 3.

4. 4. 4. 4.


Checklist for SMS Service Test

SN SN SN SN

1. 1. 1. 1.


Checklist for Handover Service Test

SN SN SN SN

1. 1. 1. 1.

2. 2. 2. 2.

3. 3. 3. 3.


Checklist for RBT Service Test (Optional)

SN SN SN SN


Page 78 of 84

INTERNALUSE


Upgrade Guide

1. 1. 1. 1.


Checklist for Fax Service Test (Optional)

SN SN SN SN

1. 1. 1. 1.


Checklist for Prepaid Service Test (Optional)

SN SN SN SN

1. 1. 1. 1.


Checklist for Emergency Call Service Test

SN SN SN SN

1. 1. 1. 1.


Checklist for Two-Stage Dialing Service (Optional)

SN SN SN SN

1. 1. 1. 1.


Checklist for Recharge Service Test (Optional)

SN SN SN SN

1. 1. 1. 1.



Page 79 of 84

INTERNALUSE


Upgrade Guide

F Checklist for the Configuration

Information on License Files

Item Before the

Upgrade

After the

Upgrade

End date

ESN information

Maximum TRX number allowed

Number of the TRX supporting half-

rate

Number of the TRX supporting AMR

Number of the TRX supporting

EDGE

Number of semipermanent connection

Number of the cell supporting

broadcasting short message service

Number of the site supporting satellite

transmission

Number of the extended cell

Number of DTRU which Transmitter

is PBT


Page 80 of 84

INTERNALUSE


Upgrade Guide

Number of DTRU which Transmitter

is Diversity Transmitter

Number of DTRU which works as

Dual Transceiver

Number of DTRU which Receiver is

Four Diversity Receiver

Number of high output power TRU

Whether to activate the eMLPP

function or not

Whether to activate the LCS(CELL

ID+TA) function or not

Whether to activate intersystem handover & reselection

Whether or not to activate the

Channel Reserved function

G Acronyms and Abbreviations

Abbreviations Full spelling

BSC Base Station Controller

LMT Local Maintenance Terminal


Page 81 of 84

INTERNALUSE


Upgrade Guide


M2000 Imanager 2000

GBAM GSM Back Administration

Module

GOMU GSM Operation and

Maintenance Unit

RSL Radio Signaling Link

OML Operation and Maintenance

Link

GMPS GSM Main Processing Subrack

GSM

GEPS GSM Extended Processing

Subrack

GTCS GSM TransCoder Subrack

GEIUA GSM E1/T1 Interface Unit for

A

GEIUB GSM E1/T1 Interface Unit for

Abis

GEIUT GSM E1/T1 Interface Unit for

Ater

GEIUP GSM E1/T1 Interface Unit for

Pb

GOIUA GSM Optic Interface Unit for

A

GOIUB GSM Optic Interface Unit for

Abis

GOIUT GSM Optic Interface Unit for


Page 82 of 84

INTERNALUSE


Upgrade Guide


Ater

GOIUP GSM Optic Interface Unit for

Pb

GXPUM GSM eXternded Processing

Unit for Main service

GXPUC GSM eXternded Processing

Unit for Cell Broadcast service

GSCU GSM Switching and Control

Unit

GTNU GSM TDM Switching Unit

GGCU GSM General clocK Unit

GUI Graphic User Interface

SCCP Signaling Connection Control

Part

LAPD Link Access Procedure on the

D channel

CIC Circuit Identification Code

PCIC Packet Circuit Identity Code

TC Transcoder

CHR Call History Record

GPRS General Packet Radio Service

GSM Global System for Mobile

communications

GDPUC GSM Data Processing Unit for

CS service

DTRU Double-Transceiver Unit


Page 83 of 84

INTERNALUSE


Upgrade Guide


ESN Electronic Serial Number


Page 84 of 84

Documents

Huawei Bsc6000 v900r003 Upgrade Guide