Anda di halaman 1dari 76

r

XXX XXXBSC6000 V100R002C01SP01 Upgrade Guide

Issue Date

1.10 2006-06-2929

HUAWEI TECHNOLOGIES CO., LTD.

INTERNALUSE XXX XXX V100R002C01SP01 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: Email: http://www.huawei.com support@huawei.com

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.10 (2006-06-29)

Page 3 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

About This Document

Authors
Prepared by Reviewed by Yu ZhiguoWang Guanghui Zhou Liang, Liu Ying, Yangjian, Wang Dong, Guo Gaorong Approved by Fang Wei Date: 2007-12-29 Date: Date: 2007-12-29 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 foundV Describes the requirements for the confirmation of ersion Requirements for Upgrade the source version required to be upgraded and the target version before the upgrade Error: Reference source not found Upgrade Flow Chart 3Error: Reference source not found Describes the whole procedures for upgrading the version. Describes the preparations before the upgrade and the health check. 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.

Issue 1.10 (2006-06-29)

Page 4 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

7Upgrade Verification

Describes the verification of the upgraded version and equipment. The normal running of the upgraded system can be ensured.

Error: Reference source not foundV Describes the processing procedures for failed ersion Rollback 9FAQ upgrade or other reasons. Describes the records of collected important problems related to the version upgrade.

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

Issue 1.10 (2006-06-29)

Page 5 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

Contents
1 Version Requirements for Upgrade................................................9 2 Upgrade Flow Chart....................................................................10 3 Preparations for Upgrade............................................................12 4 Local Upgrade Operations...........................................................21 5 Installing the M2000 Adaptation Layer.........................................47 6 Remote Upgrade Operations.......................................................47 7 Upgrade Verification...................................................................53 8 Version Rollback.........................................................................56 9 FAQ...........................................................................................61 1.1 Upgrade Preparations...........................................................62 1.2 Upgrade Record....................................................................63 1.3 Checklist for Dialing Test.......................................................65 1.4 Checklist for System Health Before the Upgrade.....................67 1.5 Checklist for System Health After the Upgrade.......................69 1.6 Checklist for the Configuration Information on License Files....73 1.7 Acronyms and Abbreviations..................................................74

Issue 1.10 (2006-06-29)

Page 6 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

Figures
Operating status of equipment.......................................................19 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..........39

Issue 1.10 (2006-06-29)

Page 7 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

Tables
Procedures for upgrading a version.................................................10 Error: Reference source not found lists the mapping between the latest versions ...........................................................................14 Version mapping of BSC6000 level 2 BIOS........................................14 Error: Reference source not found lists the BSC6000 software directory structure. .......................................................................15 Change in control of the License in BSC6000V900R003C01...............17 Checklist for the verification items..................................................53 FAQ list..........................................................................................61

Issue 1.10 (2006-06-29)

Page 8 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

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.

Issue 1.10 (2006-06-29)

Page 9 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

2
Step 1

Upgrade Flow Chart

lists the procedures for upgrading a version. Figure 1.1 Procedures for upgrading a version Operation Reference Section 3 Duration (For Reference Only) Depend on your actual requirements Section Error: Reference source not found Section Error: Reference source not found Section Error: Reference source not found Section Error: Reference source not found Section Error: Upgrade the LMT Reference source not found 15 minutes 10 minutes 15 minutes 5 minutes Depend on the actual data volume

Preparation

Back up data and software

Back up data configuration files

Load the host software online

Load the Level 2 BIOS online

Issue 1.10 (2006-06-29)

Page 10 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

Step 7

Operation

Reference Section Error: Reference source not found Section Error:

Duration (For Reference Only) 10 minutes

Upgrade data configuration files

8 Upgrade OMU software

15 minutes

Reference source not found

9 10

Restore data

Section 4.8 Section 4.10

3 minutes If step 5 is skipped, duration of the step is 25 minutes. Otherwise, the duration of the step is 15 minutes.

Upgrade board software

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

15

Clean up the site after the upgrade

Section Error: Reference source not found

2 minutes

Issue 1.10 (2006-06-29)

Page 11 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

3
No. 1 Item

Preparations for Upgrade

3.1 Checklist Before Upgrade


Check Points 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 4 Preparation for the license Prepare the software required for the upgrade Prepare the license and complete the verification 5 Check of DIP switches on subracks Ensure that subracks are in non-auto start mode. Result Preparations

3.2 Preparations for Upgrade


Before the upgrade, the related owner needs to perform system check based on Appendix 1.4 "." In preparation stage, the related owner needs to prepare the upgrade based on Appendix 1.1

Issue 1.10 (2006-06-29)

Page 12 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

"Upgrade Preparations." and records the upgrade preparations.

3.3 Checking the Versions Before the Upgrade


3.3.1 Host Version

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.

Issue 1.10 (2006-06-29)

Page 13 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

Figure 1.2 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 BSC6000V900R003 C01B061 iManagerM2000_BSC6000_MATCH_ENG_V 200R005C01B039 iManagerM2000_BSC6000_MATCH_CHS_V 200R005C01B039 BSC6000V900R003 C01B061SP01 iManagerM2000_BSC6000_MATCH_ENG_V 200R005C01B039SP02 iManagerM2000_BSC6000_MATCH_CHS_V 200R005C01B039SP02 BSC6000V900R003 C01B062 iManagerM2000_BSC6000_MATCH_CHS_V 200R005C01B041.tar iManagerM2000_BSC6000_MATCH_ENG_V 200R005C01B041.tar BSC6000V900R003 C01B070 iManagerM2000_BSC6000_MATCH_CHS_V 200R006C01B370.tar iManagerM2000_BSC6000_MATCH_ENG_V 200R006C01B370.tar iManagerM2000 V200R005C01B7 60SP01 iManagerM2000 V200R005C01B7 60SP01 iManagerM2000 V200R006C01B7 60SP01 iManagerM2000 V200R006C01B7 60SP01 iManagerM2000 V200R005C01B7 60

3.3.3 Version Mapping of Level 2 BIOS


Figure 1.3 Version mapping of BSC6000 level 2 BIOS BSC6000 Active Version BSC6000V900R003C01B032 Level 2 BIOS Version GXPUT/GXPUM207 Others:206

Issue 1.10 (2006-06-29)

Page 14 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

BSC6000V900R003C01B061

GXPUT/GXPUMGEIU/GOIUGDPUC 208 GTNU207 Others:206

BSC6000V900R003C01B070

GXPUT/GXPUMGEIU/GOIUGDPUC 208 GTNU207 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. Figure 1.4 Error: Reference source not found lists the BSC6000 software directory structure. catalog version HOST GBAM comment xC version number yyB version number Host software directory Host software document directory released commercially Compressed board software boardfile.9.3.x.yy.zip package is used to upgrade software on boards. omu-9.3.x-yy.i586.rpm OMU software package is used to upgrade the OMU software. Upgrade package version mapping verpkg.xml 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.

Issue 1.10 (2006-06-29)

Page 15 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

The file is unnecessary in local upgrade. Remote upgrade version mapping vercfg.xml file is used only in remote upgrade. The file is unnecessary in local upgrade. LMT BSC6000V900R003C0xB0yy LMT software directory LMT 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 1 Choose Technical Support > Software > Version Software > Wireless Product Line > GSM-BSS > GSM-BSC6000 > HUAWEI BSC6000 V900R003 > HUAWEI BSC6000 V900R003C01B0yy Step 2 Download the required software by clicking Software, and download the required documents by clicking Documentation. Step 3 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

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.

Issue 1.10 (2006-06-29)

Page 16 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

3.5 Preparing the License


3.5.1 Change in Control of the License
Figure 1.5 Change in control of the License in BSC6000V900R003C01 New Control Item in 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

BSC6000V900R003C01

3.5.2 Applying for the License

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

Issue 1.10 (2006-06-29)

Page 17 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide


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

1.

The fixed length of the BSC6000 ESN is 40 bytes.

To check the ESN of the license offline, do as follows: 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 1.6 "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 1.6 "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.

Issue 1.10 (2006-06-29)

Page 18 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

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. Figure 1.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.

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

Issue 1.10 (2006-06-29)

Page 19 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

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.

Issue 1.10 (2006-06-29)

Page 20 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

Local Upgrade Operations

The personnel in charge of the upgrade need to record related activities by referring to Appendix 1.2 "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

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

Issue 1.10 (2006-06-29)

Page 21 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

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.

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. # chmod 777 /BSC6000 -R

Issue 1.10 (2006-06-29)

Page 22 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

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 1.6 "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 dropdown list box in turn. Step 3 Click Query to check the Load Option of all the boards in subracks. 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.

Issue 1.10 (2006-06-29)

Page 23 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

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 2. The configuration data before the upgrade can be used.

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

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.

Issue 1.10 (2006-06-29)

Page 24 of 76

INTERNALUSE XXX XXX V100R002C01SP01 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

Issue 1.10 (2006-06-29)

Page 25 of 76

INTERNALUSE XXX XXX V100R002C01SP01 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.

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

1Before loading the level 2 BIOS, check the LMT device panel to ensure that all the boards are operational. 2When loading the level 2 BIOS online, select the corresponding level 2 BIOS version. The version may be the same as the previous version.

Issue 1.10 (2006-06-29)

Page 26 of 76

INTERNALUSE XXX XXX V100R002C01SP01 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 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: Step 1 On the LMT, choose BSC Maintenance > Query Software > Query Board Version Information. or press F9.

Issue 1.10 (2006-06-29)

Page 27 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

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

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 poweredoff board regardless of whether the restart is successful.

4.5 Upgrading the LMT

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.

Issue 1.10 (2006-06-29)

Page 28 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

4.6 Upgrading the Configuration Data File


4.6.1 Upgrading the Configuration Data File
1. Application Scenario 2. The configuration data before the upgrade can be used.

Software and Hardware Preparations One PC that is installed with the Windows2000 or WindowsXP operating system 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.

Issue 1.10 (2006-06-29)

Page 29 of 76

INTERNALUSE XXX XXX V100R002C01SP01 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.

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.

Issue 1.10 (2006-06-29)

Page 30 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

4.6.2 Prepraring the Configuration Data File


1. Application Scenario: 2. The office is new and there is no original configuration data.

Software and Hardware Preparations: One PC that is installed with the Windows2000 or WindowsXP operating system 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

1Power-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. 2After 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.

Issue 1.10 (2006-06-29)

Page 31 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

4.7.1 Operation Preparations


For the operation preparations, you need to check the current system as follows: 1. 2. 3. 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. Check the time zone by running the date +%z command on the putty. Check the time by running the date command on the putty.

----End

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 # 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

Issue 1.10 (2006-06-29)

Page 32 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

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

Keep all files in the install directory for version rollback. 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.

Issue 1.10 (2006-06-29)

Page 33 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

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 Guideto install the new version OMU software.

4.7.3 Upgrading the GOMU


Reference BSC6000 V900R003 GOMU Administration Guideto install the new version OMU software.

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.

4.8 Upgrading Active/Standby GOMU

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.

Issue 1.10 (2006-06-29)

Page 34 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

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. 2. On the putty, connect the active OMU through the IP address of the external network. 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

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."

Issue 1.10 (2006-06-29)

Page 35 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

# date +%z
# 5.

date

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.

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

Issue 1.10 (2006-06-29)

Page 36 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

the active board. In case of inconsistency, perform adjustment by referring to section 4.7.1"Operation Preparations."

# date +%z
# 8.

date

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 boarddo as follows:

# cd /BSC6000/install
#

rm rpmbak -rf

# md rpmbak
#

mv * rpmbak/

scp 192.168.10.121:/BSC6000/install/* .

To install OMU software on standby board, refer to sections inBSC6000 V900R003 GOMUAdministration Guide.

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

Issue 1.10 (2006-06-29)

Page 37 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

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.

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.

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.

Issue 1.10 (2006-06-29)

Page 38 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

ssh 192.168.10.121

To install OMU software on standby board, refer to sections inBSC6000 V900R003 GOMUAdministration 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

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 1.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

For the releases later than R3C01B060, the system performs a license check before the recovery of data configurations.

Issue 1.10 (2006-06-29)

Page 39 of 76

INTERNALUSE XXX XXX V100R002C01SP01 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 LMTSelect the software license file to download and activate. Follow the wizard to complete the activation.

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:

To activate the license, choose BSC Maintenance > Maintenance License > Activate License. Select the software license file to be activated. Follow the wizard

Issue 1.10 (2006-06-29)

Page 40 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

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

4 On the LMTChoose Configuration > Load and Restore. 5 On the LMTSelect 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."

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.

Issue 1.10 (2006-06-29)

Page 41 of 76

INTERNALUSE XXX XXX V100R002C01SP01 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.

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.

Issue 1.10 (2006-06-29)

Page 42 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

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

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.

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.

Issue 1.10 (2006-06-29)

Page 43 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

4.10.2 Procedures for the Upgrade


Use the putty tool to log in to the OMU, and then perform the following steps: 1. # 2. Access the upgrade progress directory by running the follow command. cd /BSC6000/bscswm/omuroot/upgrade Obtain the IP address used in the upgrade progress on the local OMU by

running the follow command. # 3. ifconfig | grep 192.168.10 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.

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

Issue 1.10 (2006-06-29)

Page 44 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

4.10.3 Confirming the Board State


1. 2. Log in to the LMT in later version, and then connect the LMT to the GBAM/GOMU. Click the Progress Window icon . Several tabs that display the progress of different

objects are available at the bottom of the window. 3. 4. 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.

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.

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.

Issue 1.10 (2006-06-29)

Page 45 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

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:

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 1.6 "Checklist for the Configuration Information on License Files."

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

Issue 1.10 (2006-06-29)

Page 46 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

Installing the M2000 Adaptation Layer

Install M2000 Adaptation Layer reference to M2000 Adaptation Version Installation Guide(Only for M2000 R6 Common Version).

Remote Upgrade Operations

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. 4 During the upgrade, do not change the OMU time, otherwise, the upgrade may fail due to overtime.

Issue 1.10 (2006-06-29)

Page 47 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

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 (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.

Issue 1.10 (2006-06-29)

Page 48 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

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.

----End

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

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.

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

Issue 1.10 (2006-06-29)

Page 49 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

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.3and Loading the Level 2 BIOS to a Board Online described in 4.4are 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. 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.

Issue 1.10 (2006-06-29)

Page 50 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

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:

Issue 1.10 (2006-06-29)

Page 51 of 76

INTERNALUSE XXX XXX V100R002C01SP01 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.

Issue 1.10 (2006-06-29)

Page 52 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

7
No. 1

Upgrade Verification

7.1 Verification Checklist


Figure 1.6 Checklist for the verification items Verification Item Verification after the upgrade Requirement Use the checklist for the system health to check that the verification items are correct. 2 Site cleanup after the upgrade Clean up the site 2 No. 1

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. On the LMT, choose Help > About. Press Ctrl+Shift+F12 to check the current LMT version.

Issue 1.10 (2006-06-29)

Page 53 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

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. On the LMT, choose BSC Maintenance > Maintain Transmission and Signaling > 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 On the LMT, choose BSC Maintenance > Maintain Transmission and Signaling to check whether the E1 port is normal. On the LMT, choose BSC Maintenance > Maintain User Resource to check whether all the CICs, PCICs, Abis timeslots, Ater timeslots, and TC resources are

Issue 1.10 (2006-06-29)

Page 54 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

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.

For detailed information on system health check after the upgrade, refer to Appendix 1.5 "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. 2. Remove the redundant materials. Sort the data (such as files) generated during the upgrade.

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

Issue 1.10 (2006-06-29)

Page 55 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

Version Rollback

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. 2. Log in to the GBAM/GOMU as user root. Shutdown the omu by input follow command:

# omuctrl stop

Issue 1.10 (2006-06-29)

Page 56 of 76

INTERNALUSE XXX XXX V100R002C01SP01 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.

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. Delete a specified directory and its subdirectories and files in the /BSC6000 directory.

a)

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. # b)

rm -R /BSC6000/data/*

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
Run the ls command on putty to confirm that there is no subdirectory or file in the data directory.

Issue 1.10 (2006-06-29)

Page 57 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

# ls
5. Install the OMU softear of earilier version reference to BSC6000 V900R003 GOMU Administration Guide BSC6000 V900R003 GBAM Administration Guide actual or in 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: # 2.

chmod 777 /BSC6000 -R

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:

Issue 1.10 (2006-06-29)

Page 58 of 76

INTERNALUSE XXX XXX V100R002C01SP01 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. .

Log in to the GBAM/GOMU through the LMT. Click the Progress Window icon 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

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

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.

Issue 1.10 (2006-06-29)

Page 59 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

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."

Issue 1.10 (2006-06-29)

Page 60 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

9
9.1 FAQ Index
Figure 1.7 FAQ list Number Description

FAQ

Reference

What you should pay attention to FAQ1 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.

Issue 1.10 (2006-06-29)

Page 61 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

1.1

Upgrade Preparations

Item Name of the device to be upgraded Place where the device to be upgraded is located Permitted upgrade date and time Customer's requirements for the upgrade Version before the upgrade BIOS version Host software version Patch information Version after the upgrade BIOS version Host software version Patch information Requirements for the versions of other NEs Software required for the upgrade Data required for the upgrade Hardware materials required for the upgrade

Description

Remarks

Upgrade the device when the traffic volume is low

If the configuration data remains unchanged, you do not have to prepare the data. If the hardware does not change during the upgrade, you do not

Issue 1.10 (2006-06-29)

Page 62 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

Item

Description

Remarks have to prepare hardware materials.

Tools required for the upgrade

Special tools for the upgrade, mobile equipment, SIM card, and Ethernet cables Personnel from both the customer and Huawei Maintenance personnel of other

Upgrade personnel

Assistants

NEs and network planning personnel

Vehicle

Vehicles are required for drive test, if any. Name and telephone number of the contact person

Contact person

1.2

Upgrade Record

Site Name Version before the upgrade Upgrade personnel Success or failure Operation Item Check of the operating status Multiple IP addresses Remote links From the customer: From Huawei:

Upgrade Time Version after the upgrade

Conclusion

Troubleshooting

Issue 1.10 (2006-06-29)

Page 63 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

before the upgrade

Current alarm information Cell status Data consistency

Upgrade procedures

Back up data Download all the files related to the current version 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

Issue 1.10 (2006-06-29)

Page 64 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

1.3

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 Speech: fixed-line phone calling MS (GSM) Speech: MS (GSM) calling fixed-line phone Speech: MS (GSM) calling MS (GPRS) Speech: MS (GPRS) calling MS (GSM) Speech: MS (GSM) calling MS (GSM) VP: MS (GSM) calling MS (GSM) PS: PDP activation Conversation quality of speech Conversation quality of VP Communication quality of PS Call drop

Test Result Pass NotPass N/A

Pass NotPass N/A

Pass NotPass N/A

Pass NotPass N/A

Pass NotPass N/A

Pass NotPass N/A

Pass NotPass N/A Good Bad N/A

Good Bad N/A Good Bad N/A Pass NotPass N/A

Issue 1.10 (2006-06-29)

Page 65 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

Soft handover RSCP (should be greater than -70 dBm) Ec/I0(should be greater than -10 dB)

Pass NotPass N/A

Signature of test personnel

Issue 1.10 (2006-06-29)

Page 66 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

1.4

Checklist for System Health Before the Upgrade

Checklist for the state of each interface SN 1. 2. 3. 4. 5. 6. 7. 8. SN 1. 2. 3. 4. 5. 6. 7. 8. SN 1. 2. 3. 4. 5. 6. 7. 8. Tested by: SN 1. 2. 3. 4. 5. 6. 7. 8.

Tested by:

Checklist for the operating status of the BTS SN 1. 2. 3. SN 1. 2. 3. SN 1. 2. 3. Tested by: SN 1. 2. 3.

Tested by:

Checklist for operating status of boards SN 1. SN 1. SN 1. SN 1.

Issue 1.10 (2006-06-29)

Page 67 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

2. 3. 4. 5.

2. 3. 4. 5.

2. 3. 4. 5. Tested by:

2. 3. 4. 5.

Tested by:

Checklist for Alarm Information SN 1. 2. 3. 4. 5. 6. SN 1. 2. 3. 4. 5. 6. SN 1. 2. 3. 4. 5. 6. Tested by: SN 1. 2. 3. 4. 5. 6.

Tested by:

Checklist for the M2000 Traffic Statistics Counters SN 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. SN 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. SN 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. Tested by: SN 1. 2. 3. 4. 5. 6. 7. 8. 9. 10.

Tested by:

Checklist for the Operating Status of the GBAM/GOMU SN SN SN SN

Issue 1.10 (2006-06-29)

Page 68 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

1. 2. 3. 4.

1. 2. 3. 4.

1. 2. 3. 4. Tested by:

1. 2. 3. 4.

Tested by:

1.5

Checklist for System Health After the Upgrade

Checklist for Clock Status SN 1. 2. 3. 4. 5. 6. Tested by: SN 1. 2. 3. 4. 5. 6. SN 1. 2. 3. 4. 5. 6. Tested by: SN 1. 2. 3. 4. 5. 6.

Checklist for the state of each interface SN 1. 2. 3. 4. SN 1. 2. 3. 4. SN 1. 2. 3. 4. SN 1. 2. 3. 4.

Issue 1.10 (2006-06-29)

Page 69 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

5. 6. 7. 8. 9. Tested by:

5. 6. 7. 8. 9.

5. 6. 7. 8. 9. Tested by:

5. 6. 7. 8. 9.

Checklist for the operating status of the BTS SN 1. 2. 3. Tested by: Checklist for operating status of boards SN 1. 2. 3. 4. 5. 6. Tested by: Checklist for Alarm Information SN 1. 2. 3. 4. 5. Tested by: SN 1. 2. 3. 4. 5. SN 1. 2. 3. 4. 5. Tested by: SN 1. 2. 3. 4. 5. SN 1. 2. 3. 4. 5. 6. SN 1. 2. 3. 4. 5. 6. Tested by: SN 1. 2. 3. 4. 5. 6. SN 1. 2. 3. SN 1. 2. 3. Tested by: SN 1. 2. 3.

Checklist for the M2000 Traffic Statistics Counters SN SN SN SN

Issue 1.10 (2006-06-29)

Page 70 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

1. 2. 3. 4. 5. 6. 7. 8. 9. 10. Tested by:

1. 2. 3. 4. 5. 6. 7. 8. 9. 10.

1. 2. 3. 4. 5. 6. 7. 8. 9. 10. Tested by:

1. 2. 3. 4. 5. 6. 7. 8. 9. 10.

Checklist for the Operating Status of the GBAM/GOMU SN 1. 2. 3. 4. Tested by: Checklist for Basic Service Test SN 1. Tested by: Checklist for Call Service Test SN 1. 2. 3. 4. Tested by: Checklist for SMS Service Test SN 1. SN 1. SN 1. SN 1. SN 1. 2. 3. 4. SN 1. 2. 3. 4. Tested by: SN 1. 2. 3. 4. SN 1. SN 1. Tested by: SN 1. SN 1. 2. 3. 4. SN 1. 2. 3. 4. Tested by: SN 1. 2. 3. 4.

Issue 1.10 (2006-06-29)

Page 71 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

Tested by: Checklist for Handover Service Test SN 1. 2. 3. Tested by: Checklist for RBT Service Test (Optional) SN 1. Tested by: Checklist for Fax Service Test (Optional) SN 1. Tested by: Checklist for Prepaid Service Test (Optional) SN 1. Tested by: Checklist for Emergency Call Service Test SN 1. Tested by: SN 1. SN 1. SN 1. SN 1. SN 1. 2. 3.

Tested by:

SN 1. 2. 3. Tested by:

SN 1. 2. 3.

SN 1. Tested by:

SN 1.

SN 1. Tested by:

SN 1.

SN 1. Tested by:

SN 1.

SN 1. Tested by:

SN 1.

Checklist for Two-Stage Dialing Service (Optional) SN 1. Tested by: Checklist for Recharge Service Test (Optional) SN 1. Tested by: SN 1. SN 1. Tested by: SN 1. SN 1. SN 1. Tested by: SN 1.

Issue 1.10 (2006-06-29)

Page 72 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

1.6

Checklist for the License Files

Configuration Information on

Item

Before Upgrade

the

After Upgrade

the

End date ESN information Maximum TRX number allowed Number of the TRX supporting halfrate 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 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

Issue 1.10 (2006-06-29)

Page 73 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

Whether to activate the eMLPP function or not Whether to activate the LCS(CELL ID+TA) function or not Whether to activate handover & reselection intersystem

Whether or not to activate the Channel Reserved function

1.7

Acronyms and Abbreviations

Abbreviations BSC LMT M2000 GBAM

Full spelling Base Station Controller Local Maintenance Terminal Imanager 2000 GSM Back Administration Module

GOMU

GSM Operation and Maintenance Unit

RSL OML

Radio Signaling Link Operation and Maintenance Link

GMPS

GSM Main Processing Subrack GSM

GEPS

GSM Extended Processing Subrack

GTCS GEIUA

GSM TransCoder Subrack GSM E1/T1 Interface Unit for A

Issue 1.10 (2006-06-29)

Page 74 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

Abbreviations GEIUB

Full spelling GSM E1/T1 Interface Unit for Abis

GEIUT

GSM E1/T1 Interface Unit for Ater

GEIUP

GSM E1/T1 Interface Unit for Pb

GOIUA GOIUB

GSM Optic Interface Unit for A GSM Optic Interface Unit for Abis

GOIUT

GSM Optic Interface Unit for 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 GGCU GUI SCCP

GSM TDM Switching Unit GSM General clocK Unit Graphic User Interface Signaling Connection Control Part

LAPD

Link Access Procedure on the D channel

CIC PCIC TC CHR GPRS GSM

Circuit Identification Code Packet Circuit Identity Code Transcoder Call History Record General Packet Radio Service Global System for Mobile

Issue 1.10 (2006-06-29)

Page 75 of 76

INTERNALUSE XXX XXX V100R002C01SP01 Upgrade Guide

Abbreviations

Full spelling communications

GDPUC

GSM Data Processing Unit for CS service

DTRU ESN

Double-Transceiver Unit Electronic Serial Number

Issue 1.10 (2006-06-29)

Page 76 of 76