Installation Manual-Software Installation

Chapter 1 Composition and Installation Flow ...............................................
1-1
1.1 Software Composition of MSC ............................................................... 1-1
1.1.1 Host Software ................................................................................ 1-1
1.1.2 O&M Software ................................................................................ 1-2
1.2 Software Installation Flow ...................................................................... 1-5
1.2.1 Flowchart ....................................................................................... 1-5
1.2.2 Flowchart Description .................................................................... 1-6
Chapter 2 Installation of BAM Server Software ............................................ 2-1
2.1 Installation Preparations ......................................................................... 2-1
2.1.1 Checking Hardware and Software Configuration ........................... 2-1
2.1.2 Checking Hard Disk Partitioning .................................................... 2-2
2.1.3 Checking Installed Software .......................................................... 2-3
2.2 Installing BAM Server Software .............................................................. 2-3
2.2.1 Installation Files ............................................................................. 2-3
2.2.2 Installation Procedures .................................................................. 2-4
2.2.3 Checking the Installation ................................................................ 2-11
2.2.4 Description of BAM System Directories ......................................... 2-12
2.3 Upgrading and Uninstalling BAM Server Software................................. 2-16
2.3.1 Upgrading BAM Server Software ................................................... 2-16
2.3.2 Uninstalling BAM Server Software ................................................. 2-17
2.4 Installation Problems and Troubleshooting ............................................ 2-18
2.4.1 Common Problems and Troubleshooting ...................................... 2-18
2.4.2 Manually Deleting Registry ............................................................ 2-19
2.4.3 Manually Deleting Database .......................................................... 2-20
2.4.4 Manually Deleting Program............................................................ 2-21
Chapter 3 Installation of Client Software ....................................................... 3-1
3.1 Installing Client Software ........................................................................ 3-1
3.2 Configuring the LMT ............................................................................... 3-2
3.3 Starting the LMT ..................................................................................... 3-4
3.4 Uninstalling Client Software ................................................................... 3-4
3.5 Description of Client Software Directories .............................................. 3-5
Chapter 4 Installation of Emergency WS Software ...................................... 4-1
4.1 Introduction to Emergency Workstation ................................................. 4-1
4.1.1 Function of the Emergency WS ..................................................... 4-1
4.1.2 Hardware and Software Configuration of the Emergency WS ....... 4-1
4.2 Installing Emergency WS ....................................................................... 4-1
4.2.1 Configuring the Network Adapter ................................................... 4-1
4.2.2 Installing SQL Server 2000 Home Edition ..................................... 4-6
4.2.3 Installing Emergency WS Software................................................ 4-6
4.2.4 Running Emergency WS Software ................................................ 4-8
4.3 Starting the Emergency WS ................................................................... 4-8
4.3.1 Restoring the BAM Database ........................................................ 4-8
4.3.2 Connecting the Network ................................................................. 4-11
4.3.3 Checking Data ............................................................................... 4-11
4.4 Restoring BAM Server and Emergency WS ........................................... 4-12
Chapter 5 Configuration of Remote Maintenance System .......................... 5-1
5.1 Introduction to Remote Maintenance System ........................................ 5-1
5.1.1 Basic Theory of Remote Maintenance ........................................... 5-1
5.1.2 Hardware and Software Requirements .......................................... 5-2
5.2 Configuring the RAS ............................................................................... 5-2
5.2.1 Configuring the Network Adapters ................................................. 5-2
5.2.2 Installing the Modem ...................................................................... 5-5
5.2.3 Configuring the Remote Access Service ....................................... 5-6
5.3 Configuring the Remote Maintenance Terminal ..................................... 5-16
5.3.1 Installing MSC Client Software ...................................................... 5-16
5.3.2 Configuring the Dial-up Network .................................................... 5-16
5.4 Checking the Configuration of Remote Maintenance System ................ 5-27
5.5 Testing the Remote Maintenance System ............................................. 5-29
Chapter 6 Software Loading ........................................................................... 6-1
6.1 Introduction to Software Loading............................................................ 6-1
6.1.1 Function ......................................................................................... 6-1
6.1.2 Loading Methods and Items for Attention ...................................... 6-2
6.1.3 List of Loading Files ....................................................................... 6-4
6.1.4 Power-on Loading Sequence......................................................... 6-6
6.1.5 Loading Paths and Principles ........................................................ 6-6
6.2 Loading Preparations ............................................................................. 6-10
6.3 Loading Procedures ............................................................................... 6-11
6.4 Loading Methods of Voice Files ............................................................. 6-12
6.4.1 Steps for Initial Loading of Voice Files ........................................... 6-13
6.4.2 Processing of Voice Files during System Upgrade ........................ 6-14
6.5 Troubleshooting ...................................................................................... 6-14
6.5.1 Basic Methods ............................................................................... 6-14
6.5.2 Common Loading Problems .......................................................... 6-14
Chapter 7 Upgrade of BAM Server Software ................................................. 7-1
7.1 Ways to Upgrade the BAM Server Software .......................................... 7-1
7.2 Upgrade by Using the Upgrade Tool ...................................................... 7-1
7.2.1 About the Upgrade Tool ................................................................. 7-1
7.2.2 Upgrade Procedures ...................................................................... 7-3
7.2.3 Possible Problems in the Upgrade ................................................. 7-8
7.3 Upgrade by Using the Patch Software ................................................... 7-8
7.3.1 About the Patch System ................................................................ 7-8
7.3.2 Status of the Patch System and Operations .................................. 7-9
7.3.3 Patching the Host........................................................................... 7-13
7.3.4 Patching the Terminal System ....................................................... 7-16
7.3.5 Precautions .................................................................................... 7-18
Appendix A Installation of Operating System and Database Software ...... A-1
A.1 Overview ................................................................................................ A-1
A.1.1 Configurations ............................................................................... A-1
A.2 Installation Preparations ........................................................................ A-1
A.2.1 Preparing Setup CDs..................................................................... A-1
A.2.2 Checking Server Hardware Configuration ..................................... A-1
A.3 Installation of OS and Database Software ............................................. A-2
A.3.1 Setting Disk Array and Installing Windows 2000 Server OS ......... A-2
A.3.2 Installing Windows 2000 Service Pack .......................................... A-4
A.3.3 Setting Hard Disk Partitioning for BAM Server .............................. A-4
A.3.4 Configuring Three Network Adapters ............................................ A-5
A.3.5 Configuring 4 Network Adapters .................................................... A-7
A.3.6 Adjusting System Page File Size and Registry File Size............... A-11
A.3.7 Installing Internet Explorer 5.5 ....................................................... A-12
A.3.8 Installing SQL Server 2000............................................................ A-12
A.3.9 Installing SQL Server 2000 Service Pack ...................................... A-20
A.3.10 Check Items for SQL Server 2000 Installation ............................ A-20
A.3.11 Uninstalling SQL Server 2000 Database Software ...................... A-23
Appendix B Abbreviations and Acronyms .................................................... B-1
HUAWEI
HUAWEI M800 CDMA Mobile Switching Center

Installation Manual - Software Installation
V610R003
HUAWEI M800 CDMA Mobile Switching Center
Installation Manual
Volume Software Installation
Manual Version T2-030427-20040528-C-6.31
Product Version V610R003
BOM 31041327
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: Administration Building, Huawei Technologies Co., Ltd.,
Bantian, Longgang District, Shenzhen, P. R. China
Postal Code: 518129
Website: http://www.huawei.com
Email: support@huawei.com
Copyright © 2004 Huawei Technologies Co., Ltd.
All Rights Reserved
No part of this manual may be reproduced or transmitted in any form or by any

means without prior written consent of Huawei Technologies Co., Ltd.
Trademarks
, HUAWEI, C&C08, EAST8000, HONET, , ViewPoint, INtess, ETS, DMC,

TELLIN, InfoLink, Netkey, Quidway, SYNLOCK, Radium, M900/M1800,
TELESIGHT, Quidview, Musa, Airbridge, Tellwin, Inmedia, VRP, DOPRA, iTELLIN,
HUAWEI OptiX, C&C08 iNET, NETENGINE, OptiX, iSite, U-SYS, iMUSE, OpenEye,
Lansway, SmartAX, infoX, TopEng are trademarks of Huawei Technologies Co.,
Ltd.
All other trademarks mentioned in this manual are the property of their respective
holders.
Notice
The information in this manual is subject to change without notice. Every effort has
been made in the preparation of this manual to ensure accuracy of the contents, but
all statements, information, and recommendations in this manual do not constitute
the warranty of any kind, express or implied.
About This Manual
Release Notes
This manual applies to HUAWEI M800 CDMA Mobile Switching Center V610R003.
Related Manuals
The set of documentation for HUAWEI M800 CDMA Mobile Switching Center is listed
in the table below.
Manual Contents
HUAWEI M800 CDMA Mobile Switching Describes structure, major contents of manuals and
Center Documentation Guide retrieval methods of package of documents.
HUAWEI M800 CDMA Mobile Switching Basic information on architecture, features, technical
Center Technical Manual-System Description indices, functions and external interface attributes.
HUAWEI M800 CDMA Mobile Switching

Introduction to architecture, functional modules, and
Center Technical Manual-System
the signal and message flows.
Architecture
HUAWEI M800 CDMA Mobile Switching Introduction to signaling system structure and
Center Technical Manual-Signaling System explanation of messages.
HUAWEI M800 CDMA Mobile Switching Detailed description on basic functions and their
Center Technical Manual-System Function theories, and briefing on the provision of various
services.
HUAWEI M800 CDMA Mobile Switching Introduction to hardware, including cabinets,

Center Hardware Description Manual subracks, boards and cables.
HUAWEI M800 CDMA Mobile Switching Instructions on operation and maintenance at various
Center Operation Manual-Routine Operation terminals and common administrative operations on
the system.
HUAWEI M800 CDMA Mobile Switching Introduction to principles for data configuration,
Center Operation Manual-Data Configuration including sequence of data configuration and
principles for numbering, as well as data
configuration commands, and notes on data
configuration.

Introductions to theories, operations, examples and
Center Operation Manual-Performance
common performance measurement tasks.
Measurement
HUAWEI M800 CDMA Mobile Switching Introduction to provision of services other than basic
Center Operation Manual-Feature services, including theories of realization, data
Description configuration, service interworking and service flows.
Manual Contents

Introduction to requirements of routine maintenance
Center Maintenance Manual-Routine
and instructions on routine maintenance.
Maintenance
HUAWEI M800 CDMA Mobile Switching Instructions on replacement procedures of boards,

Center Maintenance Manual-Parts backplanes, terminal system parts replacement and
Replacement notes on replacement.
HUAWEI M800 CDMA Mobile Switching Instructions on analysis of service provision faults
Center Maintenance Manual-Troubleshooting and troubleshooting with the results of such analysis.

Instructions on installation of hardware and methods
Center Installation Manual-Hardware
of verification after installation.
Installation

Instructions on installation of software and remote
Center Installation Manual-Software
maintenance configuration.
Installation
HUAWEI M800 CDMA Mobile Switching Instructions on debugging after successful

Center Installation Manual-System installation of hardware and software, as well as
Commissioning description on initial verification, cutover, upgrading,
patch loading, and online capacity expansion.
HUAWEI iGateway Bill User Manual Introduction to theories, installation, operation,

maintenance and troubleshooting of iGWB.
Organization
Based on description of the software composition of M800 CDMA MSC and the general
installation flow, this manual details the specific procedures and precautions of
installing the software for the system and those of loading and upgrading the host
software.
This manual consists of seven chapters and two appendices:
Chapter 1 Composition and Installation Flow introduces the software composition

of M800 CDMA MSC and the general flow of software installation.
Chapter 2 Installation of BAM Server Software describes the procedures of

installing, upgrading and uninstalling BAM server software and precautions.
Chapter 3 Installation of Client Software describes the procedures of installing the

Client software.
Chapter 4 Installation of Emergency WS Software describes the procedures of

installing and configuring the emergency WS and those of starting the emergency WS
and restoring the BAM server.
Chapter 5 Configuration of Remote Maintenance System describes the basic
theory of the remote maintenance system and procedures of configuring the RAS and
remote maintenance terminal.
Chapter 6 Software Loading describes the procedures of loading host software and
precautions to take.
Chapter 7 Upgrade of BAM Server Software describes the procedures of upgrading

the host software and precautions, including operations on the patches.
Appendix A Installation of Operating System and Database Software describes

the procedures of installing Windows 2000 and SQL Server 2000.
Appendix B Abbreviations and Acronyms lists the abbreviations and acronyms

used in this manual.
Intended Audience
The manual is intended for the following readers:

z Engineering technicians
z Telecommunication management personnel
z Installation and commissioning engineers
Conventions
The manual uses the following conventions:
I. General conventions
Convention Description
Arial Normal paragraphs are in Arial.
Arial Narrow Warnings, Cautions, Notes and Tips are in Arial Narrow.
Boldface Headings are in Boldface.
Courier New Terminal Display is in Courier New.
II. Command conventions
Boldface The keywords of a command line are in Boldface.
italic Command arguments are in italic.
[] Items (keywords or arguments) in square brackets [ ] are optional.
Alternative items are grouped in braces and separated by vertical bars.
{ x | y | ... }
One is selected.
Optional alternative items are grouped in square brackets and separated
[ x | y | ... ]
by vertical bars. One or none is selected.
Alternative items are grouped in braces and separated by vertical bars. A
{ x | y | ... } *
minimum of one or a maximum of all can be selected.
Optional alternative items are grouped in square brackets and separated
[ x | y | ... ] *
by vertical bars. Many or none can be selected.
III. GUI conventions
Button names are inside angle brackets. For example, click the <OK>
<>
button.
Window names, menu items, data table and field names are inside square
[]
brackets. For example, pop up the [New User] window.
Multi-level menus are separated by forward slashes. For example,
/
[File/Create/Folder].
IV. Keyboard operation
Format Description
Press the key with the key name inside angle brackets. For example,
<Key>
<Enter>, <Tab>, <Backspace>, or <A>.
Press the keys concurrently. For example, <Ctrl+Alt+A> means the three
<Key1+Key2>
keys should be pressed concurrently.
Press the keys in turn. For example, <Alt, A> means the two keys should
<Key1, Key2>
be pressed in turn.
V. Mouse operation
Action Description
Click Press the left button or right button quickly (left button by default).
Double Click Press the left button twice continuously and quickly.
Drag Press and hold the left button and drag it to a certain position.
VI. Symbols
Eye-catching symbols are also used in the manual to highlight the points worthy of
special attention during the operation. They are defined as follows:
Caution: Means reader be extremely careful during the operation.
Note: Means a complementary description.
Environmental Protection
This product has been designed to comply with the requirements on environmental
protection. For the proper storage, use and disposal of this product, national laws and
regulations must be observed.
HUAWEI M800 CDMA Mobile Switching Center Table of Contents
Table of Contents
Chapter 1 Composition and Installation Flow ............................................................................ 1-1

1.1 Software Composition of MSC........................................................................................... 1-1
1.1.1 Host Software.......................................................................................................... 1-1
1.1.2 O&M Software ......................................................................................................... 1-2
1.2 Software Installation Flow.................................................................................................. 1-5
1.2.1 Flowchart................................................................................................................. 1-5
1.2.2 Flowchart Description.............................................................................................. 1-6
Chapter 2 Installation of BAM Server Software.......................................................................... 2-1

2.1 Installation Preparations .................................................................................................... 2-1
2.1.1 Checking Hardware and Software Configuration.................................................... 2-1
2.1.2 Checking Hard Disk Partitioning ............................................................................. 2-2
2.1.3 Checking Installed Software.................................................................................... 2-3
2.2 Installing BAM Server Software ......................................................................................... 2-3
2.2.1 Installation Files....................................................................................................... 2-3
2.2.2 Installation Procedures............................................................................................ 2-4
2.2.3 Checking the Installation ....................................................................................... 2-11
2.2.4 Description of BAM System Directories ................................................................ 2-12
2.3 Upgrading and Uninstalling BAM Server Software.......................................................... 2-16
2.3.1 Upgrading BAM Server Software .......................................................................... 2-16
2.3.2 Uninstalling BAM Server Software ........................................................................ 2-17
2.4 Installation Problems and Troubleshooting ..................................................................... 2-18
2.4.1 Common Problems and Troubleshooting ............................................................. 2-18
2.4.2 Manually Deleting Registry ................................................................................... 2-19
2.4.3 Manually Deleting Database ................................................................................. 2-20
2.4.4 Manually Deleting Program................................................................................... 2-21
Chapter 3 Installation of Client Software .................................................................................... 3-1

3.1 Installing Client Software ................................................................................................... 3-1
3.2 Configuring the LMT .......................................................................................................... 3-2
3.3 Starting the LMT ................................................................................................................ 3-4
3.4 Uninstalling Client Software............................................................................................... 3-4
3.5 Description of Client Software Directories ......................................................................... 3-5
Chapter 4 Installation of Emergency WS Software.................................................................... 4-1

4.1 Introduction to Emergency Workstation............................................................................. 4-1
4.1.1 Function of the Emergency WS .............................................................................. 4-1
4.1.2 Hardware and Software Configuration of the Emergency WS................................ 4-1
4.2 Installing Emergency WS................................................................................................... 4-1
i
4.2.1 Configuring the Network Adapter ............................................................................ 4-1

4.2.2 Installing SQL Server 2000 Home Edition .............................................................. 4-6
4.2.3 Installing Emergency WS Software......................................................................... 4-6
4.2.4 Running Emergency WS Software.......................................................................... 4-8
4.3 Starting the Emergency WS .............................................................................................. 4-8
4.3.1 Restoring the BAM Database.................................................................................. 4-8
4.3.2 Connecting the Network........................................................................................ 4-11
4.3.3 Checking Data....................................................................................................... 4-11
4.4 Restoring BAM Server and Emergency WS.................................................................... 4-12
Chapter 5 Configuration of Remote Maintenance System........................................................ 5-1

5.1 Introduction to Remote Maintenance System.................................................................... 5-1
5.1.1 Basic Theory of Remote Maintenance.................................................................... 5-1
5.1.2 Hardware and Software Requirements................................................................... 5-2
5.2 Configuring the RAS .......................................................................................................... 5-2
5.2.1 Configuring the Network Adapters .......................................................................... 5-2
5.2.2 Installing the Modem ............................................................................................... 5-5
5.2.3 Configuring the Remote Access Service ................................................................ 5-6
5.3 Configuring the Remote Maintenance Terminal .............................................................. 5-16
5.3.1 Installing MSC Client Software.............................................................................. 5-16
5.3.2 Configuring the Dial-up Network ........................................................................... 5-16
5.4 Checking the Configuration of Remote Maintenance System......................................... 5-27
5.5 Testing the Remote Maintenance System....................................................................... 5-29
Chapter 6 Software Loading......................................................................................................... 6-1

6.1 Introduction to Software Loading ....................................................................................... 6-1
6.1.1 Function................................................................................................................... 6-1
6.1.2 Loading Methods and Items for Attention ............................................................... 6-2
6.1.3 List of Loading Files ................................................................................................ 6-4
6.1.4 Power-on Loading Sequence.................................................................................. 6-6
6.1.5 Loading Paths and Principles.................................................................................. 6-6
6.2 Loading Preparations....................................................................................................... 6-10
6.3 Loading Procedures......................................................................................................... 6-11
6.4 Loading Methods of Voice Files....................................................................................... 6-12
6.4.1 Steps for Initial Loading of Voice Files.................................................................. 6-13
6.4.2 Processing of Voice Files during System Upgrade............................................... 6-14
6.5 Troubleshooting ............................................................................................................... 6-14
6.5.1 Basic Methods....................................................................................................... 6-14
6.5.2 Common Loading Problems.................................................................................. 6-14
Chapter 7 Upgrade of BAM Server Software .............................................................................. 7-1

7.1 Ways to Upgrade the BAM Server Software ..................................................................... 7-1
7.2 Upgrade by Using the Upgrade Tool ................................................................................. 7-1
7.2.1 About the Upgrade Tool .......................................................................................... 7-1
ii
7.2.2 Upgrade Procedures ............................................................................................... 7-3

7.2.3 Possible Problems in the Upgrade.......................................................................... 7-8
7.3 Upgrade by Using the Patch Software .............................................................................. 7-8
7.3.1 About the Patch System.......................................................................................... 7-8
7.3.2 Status of the Patch System and Operations ........................................................... 7-9
7.3.3 Patching the Host.................................................................................................. 7-13
7.3.4 Patching the Terminal System .............................................................................. 7-16
7.3.5 Precautions ........................................................................................................... 7-18
Appendix A Installation of Operating System and Database Software ...................................A-1

A.1 Overview............................................................................................................................A-1
A.1.1 Configurations.........................................................................................................A-1
A.2 Installation Preparations....................................................................................................A-1
A.2.1 Preparing Setup CDs..............................................................................................A-1
A.2.2 Checking Server Hardware Configuration ..............................................................A-1
A.3 Installation of OS and Database Software ........................................................................A-2
A.3.1 Setting Disk Array and Installing Windows 2000 Server OS ..................................A-2
A.3.2 Installing Windows 2000 Service Pack ...................................................................A-4
A.3.3 Setting Hard Disk Partitioning for BAM Server .......................................................A-4
A.3.4 Configuring Three Network Adapters .....................................................................A-5
A.3.5 Configuring 4 Network Adapters.............................................................................A-7
A.3.6 Adjusting System Page File Size and Registry File Size .....................................A-11
A.3.7 Installing Internet Explorer 5.5 ..............................................................................A-12
A.3.8 Installing SQL Server 2000...................................................................................A-12
A.3.9 Installing SQL Server 2000 Service Pack.............................................................A-20
A.3.10 Check Items for SQL Server 2000 Installation ...................................................A-20
A.3.11 Uninstalling SQL Server 2000 Database Software.............................................A-23
Appendix B Abbreviations and Acronyms .................................................................................B-1
iii
HUAWEI M800 CDMA Mobile Switching Center List of Figures
List of Figures
Figure 1-1 Software structure of M800 CDMA MSC.............................................................. 1-1
Figure 1-2 Software installation flowchart .............................................................................. 1-5
Figure 2-1 Select Version....................................................................................................... 2-5
Figure 2-2 Selecting setup type ............................................................................................. 2-6
Figure 2-3 Time synchronization options ............................................................................... 2-8
Figure 2-4 SQL Server name ................................................................................................. 2-9
Figure 2-5 Upgrade BAM Server Software .......................................................................... 2-17
Figure 2-6 Running regedit .................................................................................................. 2-19
Figure 2-7 Registry editor .................................................................................................... 2-19
Figure 2-8 Running isqlw ..................................................................................................... 2-20
Figure 2-9 SQL Server query analyzer ................................................................................ 2-20
Figure 3-1 Selecting Client software ...................................................................................... 3-1
Figure 3-2 Local NE management system............................................................................. 3-2
Figure 3-3 Configuring BAM .................................................................................................. 3-3
Figure 3-4 The configured BAM Server ................................................................................. 3-4
Figure 3-5 Confirming the un-installation ............................................................................... 3-4
Figure 4-1 Network and dial-up network ................................................................................ 4-2
Figure 4-2 Local connection status ........................................................................................ 4-3
Figure 4-3 Local connection properties.................................................................................. 4-4
Figure 4-4 Internet protocol (TCP/IP) properties ................................................................... 4-5
Figure 4-5 Configuring synchronization data of the emergency WS ..................................... 4-7
Figure 4-6 Restoring MSC environment and data ................................................................. 4-9
Figure 4-7 Restoring data .................................................................................................... 4-10
Figure 5-1 Networking of the remote maintenance system ................................................... 5-1
Figure 5-2 Network and dial-up connections ......................................................................... 5-3
iv
Figure 5-3 Local Area Connection Status .............................................................................. 5-4
Figure 5-4 Local area connection properties ......................................................................... 5-5
Figure 5-5 Network connection wizard................................................................................... 5-6
Figure 5-6 Network connection type ...................................................................................... 5-7
Figure 5-7 Devices for incoming connections........................................................................ 5-8
Figure 5-8 Incoming virtual private connection ...................................................................... 5-9
Figure 5-9 Allowed users ....................................................................................................... 5-9
Figure 5-10 New user........................................................................................................... 5-10
Figure 5-11 Dial-up user added ........................................................................................... 5-10
Figure 5-12 Networking components ................................................................................... 5-11
Figure 5-13 Incoming TCP/IP properties ............................................................................. 5-12
Figure 5-14 Completing the network connection wizard...................................................... 5-13
Figure 5-15 [Incoming Connections] added......................................................................... 5-13
Figure 5-16 Services ............................................................................................................ 5-14
Figure 5-17 Routing and remote access properties (local computer).................................. 5-15
Figure 5-18 Service control.................................................................................................. 5-15
Figure 5-19 Routing and remote access service started ..................................................... 5-16
Figure 5-20 Network connection type .................................................................................. 5-17
Figure 5-21 Internet connection wizard................................................................................ 5-17
Figure 5-22 Selecting the mode to connect to the Internet.................................................. 5-18
Figure 5-23 Setting the telephone number .......................................................................... 5-19
Figure 5-24 Setting the user name and password............................................................... 5-20
Figure 5-25 Setting the connection name ............................................................................ 5-21
Figure 5-26 Setting Internet Mail account ............................................................................ 5-22
Figure 5-27 Completing the new connection setting............................................................ 5-23
Figure 5-28 New connection successfully added ................................................................ 5-24
Figure 5-29 Dial-up network properties................................................................................ 5-25
Figure 5-30 Internet protocol (TCP/IP) properties ............................................................... 5-26
v
Figure 5-31 Advanced TCP/IP settings................................................................................ 5-27
Figure 5-32 Phone dialer ..................................................................................................... 5-28
Figure 5-33 Dialing test........................................................................................................ 5-28
Figure 5-34 Dial-up connection program ............................................................................. 5-30
Figure 5-35 Dial-up connection properties........................................................................... 5-31
Figure 6-1 Loading host software to the AMP board.............................................................. 6-2
Figure 6-2 Loading host software from AMP to GBAC .......................................................... 6-3
Figure 6-3 Executing MML batch command ........................................................................ 6-11
Figure 7-1 Service Panel ....................................................................................................... 7-3
Figure 7-2 Closing BAMService............................................................................................. 7-3
Figure 7-3 Modifying the startup type of BAMService ........................................................... 7-4
Figure 7-4 Exiting BAMManager............................................................................................ 7-5
Figure 7-5 Exiting BAM gateway............................................................................................ 7-6
Figure 7-6 Selecting the upgrade mode................................................................................. 7-6
Figure 7-7 Status change of the patch ................................................................................. 7-10
Figure A-1 Binding network adapters ....................................................................................A-6
Figure A-2 Install Intel PRO Set II component.......................................................................A-8
Figure A-3 Intel PRO Set II ....................................................................................................A-9
Figure A-4 Network adapter binding (1).................................................................................A-9
Figure A-5 Network adapter binding (3)...............................................................................A-10
Figure A-6 Completed network adapter binding (4).............................................................A-10
Figure A-7 Set virtual memory .............................................................................................A-11
Figure A-8 Welcomeof Microsoft SQL Server 2000.............................................................A-13
Figure A-9 Installation selection...........................................................................................A-14
Figure A-10 Installation selection.........................................................................................A-15
Figure A-11 Select setup type..............................................................................................A-16
Figure A-12 Select components...........................................................................................A-17
Figure A-13 Set network libraries.........................................................................................A-18
vi
Figure A-14 Selecting licensing mode .................................................................................A-19
Figure A-15 Microsoft SQL Server 2000 program group .....................................................A-20
Figure A-16 Running icon of SQL Server 2000 service manager........................................A-21
Figure A-17 SQL Server Service Manager ..........................................................................A-21
Figure A-18 SQL Server Service Manager stops running ...................................................A-21
Figure A-19 Connect to SQL Server ....................................................................................A-22
vii
HUAWEI M800 CDMA Mobile Switching Center List of Tables
List of Tables
Table 1-1 Software configuration list of O&M functional modules.......................................... 1-4
Table 2-1 Setup type description............................................................................................ 2-6
Table 4-1 Description of synchronization data configuration.................................................. 4-7
Table 6-1 Description of loading files ..................................................................................... 6-4
Table 6-2 Principles of board loading ..................................................................................... 6-8
Table A-1 Setting 3 network adapters ....................................................................................A-5
Table A-2 Setting 4 network adapters ....................................................................................A-7
viii
HUAWEI M800 CDMA Mobile Switching Center Chapter 1 Composition and Installation Flow
Chapter 1 Composition and Installation Flow
This chapter gives an introduction to the structure and installation of HUAWEI M800
CDMA mobile switching center (hereinafter referred to as the MSC, or M800 CDMA
MSC), and describes the system software.
1.1 Software Composition of MSC
The software of the M800 CDMA MSC system is composed of host software and
operation and maintenance (O&M) system software, as illustrated in Figure 1-1.
MSC/host software
BAM server/BAM server

software iGWB/iGWB software
M2000 Centralized NM system/M2000 Emergency WS/emergency

LMT /Client software
Centralized NM software WS software
O&M software
Figure 1-1 Software structure of M800 CDMA MSC
Note:
In practice, HUAWEI M2000 Centralized Network Management (NM) System as shown in Figure 1-1 is
optional. In the description hereinafter, this system is considered as available in the MSC system. If it is not
configured, you can skip the parts concerning the M2000 Centralized NM system.
1.1.1 Host Software
The host software contains the software running on the boards like AMP, GSPC, NCC,
CDP and GVDP of the M800 CDMA MSC.
The host software controls the hardware resource allocation of the M800 CDMA MSC.
It provides the functions of trunk signaling processing, call processing and charging,
and realizes mobile switching.
1-1
The host software can be installed into the M800 CDMA MSC by loading and
solidification. The boards like AMP, GSPC, NCC, CDP and GVDP all support online
patching function, i.e. the loading, activation, and fallback of patches can be performed
without stopping the running of boards.
Note:
Loading is to install the host software into the M800 CDMA MSC via the Back Administration Module
(BAM).
Solidification indicates that all boards of the M800 CDMA MSC can save the host program and static data
permanently using Flash Memory if necessary, so that the system can be restored within three minutes
without loading the program and data again.
1.1.2 O&M Software
M800 CDMA MSC O&M software is composed of the local O&M software, iGWB
software and M2000 centralized NM software. Among them, the local O&M software is
composed of BAM Server software, Local Maintenance Terminal (LMT) software and
emergency workstation (emergency WS) software.
I. Local O&M software
z BAM Server software

The BAM Server software is installed on the BAM Server. On one hand, it establishes
connection with the host (the MSC) to provide such functions as data loading, online
configuration, equipment maintenance, performance measurement, and equipment
commissioning. On the other hand, it establishes connection with the Client or network
management (NM) center so as to provide the operation and maintenance interface for
the Client or the network management center, so that data configuration and other
maintenance operations can be performed on several remote/local terminals.
z Client software
LMT software is installed on the Client PC of the M800 CDMA MSC.
As the Client of the BAM Server, LMT establishes communication with the BAM Server
via the TCP/IP, and provides graphic user interface based on the MML so that the users
can perform a series of operations including data configuration, equipment
maintenance, performance measurement, testing, signaling and interface tracing, VLR
subscriber data maintenance and query, and alarm management. One set of BAM
Server software can communicate with multiple Client software. Each Client software
can establish connections with multiple BAMs.
1-2
z Emergency WS software
Emergency WS software is installed on the emergency WS. The emergency WS is a
backup device of the BAM Server, and can take the place of it in some special
conditions. The emergency WS is configured the same with the ordinary LMT in terms
of hardware, but different in terms of system software. On the emergency WS,
Windows 2000 Professional operating system, MS SQL Server 2000 Home Edition and
emergency WS software are installed. While on the ordinary LMT, Windows 2000
Professional operating system and Client software are installed.
II. iGWB software
The iGWB software is composed of Server software and Client software (bill console).
The Server software runs on iGWB. The iGWB receives the original bills generated by
various Service Processing Modules (SPMs) of M800 CDMA MSC, and saves the bills
and backs them up on the hard disk. It also pre-processes the original bills and
provides the online charging interface to the billing center.
The Client software can run on any LMT, providing various functions such as user
management, bill browsing, log browsing, bill backup, bill querying and server state
querying.
III. M2000 centralized NM software
iManager M2000 centralized NM software is composed of M2000 Server software, NE

data collection unit (Adapter) software and M2000 Client software.
z M2000 Server software
The Server software runs on M2000 Server. It is the core of the centralized
maintenance system. It contains various kinds of service processes, such as alarm
server, performance server, configuration server, and communication server. Once the
BAM is connected with the M2000 Server, centralized maintenance and management
over the HUAWEI CDMA 1X system (including MSC, HLR, BSC and BTS and other
NEs) can be implemented.
z NE data collection unit (Adapter) software
The data collection unit (Adapter) software can run on M2000 Server. It is the protocol
adapter module of each Network Element (NE). It provides basic data with unified
standard for iManager M2000. Meanwhile, it converts the service operations of users in
the Centralized NMS into specific operation commands of each NE and submits them
to the host for execution.
1-3
Note:
The data collection unit software can run on the computer independently or together with other data
collection unit software modules or M2000 Server software, as long as the computer performance meets
the requirement. In M800 CDMS MSC, it often runs on M2000 Server together with the Server software.
z M2000 Client software

M2000 Client software provides the interfaces for users to perform centralized O&M
management on the mobile NEs, including the integrated network management,
centralized configuration management, centralized performance management,
centralized fault management and local maintenance of various NEs.
Table 1-1 shows the configuration list of all functional modules of M800 CDMA MSC
O&M software.
Table 1-1 Software configuration list of O&M functional modules
Software Operating Database

Application Software Pre-installed software
entity System Software software
Windows 2000
SQL Server 2000
Windows 2000 BAM Server software Server+SP3, SQL Server
BAM Server Standard
Server+SP3 package 2000 Standard
Edition+SP3
Edition+SP3
LMT Client software
Client (LMT Windows 2000 package, M2000 Client Windows 2000
-
and M2000) Professional+SP3 software and iGWB Client Professional+SP3
software package
SQL Server 2000
Emergency Windows 2000 Emergency WS software Windows 2000
Personal
WS Professional+SP3 package Professional+SP3
Edition+SP3
Windows 2000 iGWB Server software Windows 2000 Server+
iGWB -
Server+ SP3 package SP3
SUN Solaris-2.8-Standard
Sybase Adaptive Edition
SUN-Solaris-2.8- Server 11.9 .X for M2000 Server software
M2000 Server Sybase Adaptive Server
Standard SUN Solaris-10 Adapter software
users 11.9 .X for SUN Solaris-10
users
1-4
Note:
The patch version number of the operating system and database software shown in this table is only for
reference. For the specific version number, refer to the patch CD attached upon delivery.
The pre-installed software information shown in this table is only for reference. In practice, the
configuration may be different.
1.2 Software Installation Flow
1.2.1 Flowchart
Figure 1-2 shows the procedure of software installation on the site.
Start
Install BAM Server

software
Install Client software
Install emergency WS
software
Load the host

software
Install the iGWB

software
Configure the remote

maintenance system
Install M2000 Centralized NM

software
End
Figure 1-2 Software installation flowchart
1-5
Note:
Table 1-1 shows the information of the pre-installed operating system and database software. Generally,
the operating system and database software are pre-installed. In the case that they are not installed or
reinstallation is needed, see "Appendix A Installation of Operating System and Database Software" of this
manual, iManager M2000 Installation Manual, and iGateway Bill User Manual for specific procedures.
1.2.2 Flowchart Description
The following is the description of the software installation flowchart.
I. Install BAM Server software
See "Chapter 2 Installation of BAM Server Software " for the specific procedures.
Before installation, make sure that the operating system and database software of the
specified versions have been installed on the server.
II. Install Client software
Generally, Windows 2000 Professional operating system has been installed on the
specified LMT. You can install the Client software directly. See "Chapter 3 Installation of
Client Software " for specific procedures.
III. Install emergency WS software
Similar to the configuration on the LMT, the Windows 2000 Professional has been
installed beforehand on the emergency WS generally. You shall install the database
software SQL Server 2000 Personal Edition + SP3, and then MSC emergency WS
software. See "Chapter 4 Installation of Emergency WS Software" for specific
procedures.
IV. Load the host software
Loading and debugging of the host software can be performed on the BAM Server after
the BAM Server software is properly installed. You can also install one or all LMTs first,
and then load and debug the host software on the Client WSs, which is more
convenient as several engineers can perform the debugging on different maintenance
terminals.
V. Install the iGWB software
For the specific procedures, see iGateway Bill User Manual delivered with the product.
1-6
VI. Configure the remote maintenance system
M800 CDMA MSC supports dial-up access mode. The system is configured with a
Remote Access Server (RAS), i.e. the dial-up server, to provide an interface for
maintenance personnel to access the system.
As the RAS is usually integrated with the emergency WS, the configuration of the RAS
can be performed after the emergency WS software is properly installed.
See "5 Configuration of Remote Maintenance System" for detailed information.
VII. Install iManager M2000 Centralized NM software
The specific procedures are determined by the hardware configuration on the site.
Generally, there are three cases:
z M2000 centralized NM function is not supported. In this case, omit the last step
"Install M2000 Centralized NM software" as shown in the installation flow in Figure
1-2.
z M2000 centralized NM Client WS is configured while M2000 Server is not. In this
case, M2000 Client software should be installed on the LMT.
z Both the M2000 Centralized NM server and Client WS are configured. In this case,
install the whole package of Centralized NM software, including M2000 Server
software, Adapter software and M2000 Client software.
For detailed information, see iManager M2000 Installation Manual delivered with the
product.
1-7
HUAWEI M800 CDMA Mobile Switching Center Chapter 2 Installation of BAM Server Software
Chapter 2 Installation of BAM Server Software
This chapter describes the initial installation of BAM Server software. For the upgrade
of BAM Server software, refer to "Chapter 7 Upgrade of BAM Server Software".
Note:
During BAM Server installation, the setup program will install BAM Client software by default. There is no
need to install the Client software again on the same server.
2.1 Installation Preparations
Before installing the BAM Server software, you shall check the hardware and software
configuration, hard disk partitioning and the software already installed.
2.1.1 Checking Hardware and Software Configuration
The following requirements for hardware and software configuration should be met:
I. Hardware configuration
The hardware configuration requirements are as follows:

z Two Intel Xeon 1.8GHz CPUs or higher
z Five hard disks of 36.4GB 10kRPM
z 1GB memory
z Three 10/100Mbit/s adaptive error-tolerance network adapters and one integrated
network adapter
z Integrated RAID disk array card PERC4/Di
z One CD/DVD-ROM drive
z One 3.5" floppy drive
z One to two hot pluggable power supply systems
II. Software configuration
The software configuration requirements are as follows:

z Windows 2000 Server operating system is running normally.
z Structured Query Language (SQL) Server 2000 is started.
2-1
z The system time is correctly set.

In addition, the server should be installed with correct drivers for video adapter and
network adapter. Such operations as binding of the network adapters and setting of the
drive letters have been conducted.There is enough space in the disk to install the BAM
Server software.
Note:
The required software is installed on the server upon delivery. If it should be installed again in some cases
(e.g. when the software operation becomes abnormal), see "Appendix A Installation of Operating System
and Database Software" for detailed description of the procedures.
2.1.2 Checking Hard Disk Partitioning
Generally, the hard disk of BAM is divided into four logical drives: C, D, E and F. The
files on logical drives are all in NTFS format. These drives are defined as follows:
z Drive C, as the system drive, is used to install Windows 2000 Server.
z Drive D is used to install SQL Server 2000, BAM programs and BAM databases.
z Drive E is used to store database logs.
z Drive F is used for database backup.
The size of each logical partitioning can be defined as per the following rule: Drive C is
always set as 4GB, while the sizes of the rest drives should be defined in the following
ratio: D:E:F = 4:2:1.
In the calculation result of the above formula, if the space of Drive F is smaller than 2GB,
set it as 2GB and reduce the space of Drive C accordingly.
For example,
Suppose the BAM Server is configured with five 36.4GB hard disks. After the disks are
configured as RAID5, the server occupies some space and Drive C occupies 4GB, and
the remaining total capacity is 100GB. Then this space can be partitioned into the rest
logical drives as follows:
Divide 100GB in the ratio of 4:2:1, therefore the sizes of drive D, drive E and drive F are
56GB, 28GB and 16GB respectively.
The final result is 4GB for Drive C, 56GB for Drive D, 28GB for Drive E and 16GB for
Drive F.
2-2
If the hard disk on which the BAM Server software is to be installed is not partitioned as
described above, you shall partition it again. For details, refer to “Appendix A
Installation of Operating System and Database Software”.
2.1.3 Checking Installed Software
To reduce impact of unexpected factors on the BAM system, there should be no other
applications or software installed on the BAM Server.
2.2 Installing BAM Server Software
BAM Server software controls the communication between the Local Maintenance
Terminal (LMT) and the various boards on the MSC. BAM Server software is installed
on the BAM Server.
2.2.1 Installation Files
The BAM Server software installation package is generally in \OMC\BAM of the whole
set of system software package. The files and folders in this path are described below:
I. Files in the installation directory
The following table lists the files in the BAM Server software package. These files are
the support files and data files needed in installing or uninstalling the BAM Server
software.
File Description
_inst32i.ex_ Supporting file for the setup program
_isdel.exe Uninstallation execution file
_setup.dll Supporting file for the setup program
_sys1.cab Data file for the setup program
_user1.cab Data file for the setup program
Data.tag Supporting file for the setup program
Data1.cab Data file for the compress program
Lang.dat Supporting file for the setup program
Layout.bin Supporting file for the setup program
Os.dat Supporting file for the setup program
Setup.bmp Supporting file for the setup program
Setup.exe Execution file for the setup program
2-3
File Description
Setup.ini Supporting file for the setup program
Setup.ins Supporting file for the setup program
Setup.lid Supporting files for the setup program
II. Folders under the installation directory
In the BAM Server software package, there is only one folder Upgrade.
Folder Description
This folder is used to store upgrading tools and the supporting files. The setup
Upgrade program will invoke the upgrading tools and supporting files in this directory when
you select upgrade from the current system.
2.2.2 Installation Procedures
The procedures of installing BAM Server software are as follows:
I. Start the setup program
1) Run SETUP.EXE.
You can run it directly from the setup CD or copy the whole setup software
package and run it from the local disk.
After the setup program initialization is completed, the [Welcome] window will
appear, prompting that the system is ready for software installation.
2) Click <Next> to continue or click <Cancel> to quit.
II. Read license agreement and installation guide
The Software License Agreement appears.

1) Read the License Agreement carefully and click <Yes > (Otherwise click <No> to
exit).
2) Read the installation guide carefully.
This guide instructs you the basic process for the BAM system installation and
cautions to take. It contains the latest information about installation which might
not be given in this manual.
2-4
III. Verify Product Serial No.
Input the user information and the product serial No. when system prompts you to do
so.
The serial No. comes along with the related agreements upon delivery.
IV. Select version
Select "International" when the setup program prompts you to select the language, as
shown in Figure 2-1.
Figure 2-1 Select Version
V. Select the setup type
Select "MSC Administration System Server (English)" in the [Setup Type] dialog box as
2-5
Figure 2-2 Selecting setup type
The meaning of each option in the dialog box is shown in Table 2-1:
Table 2-1 Setup type description
Menu Function description

Installing the Client software. By default, Gateway Tool is also
Administration System Client
installed.
Installing BAM Server software. By default, the Client software and
Administration System Server
Gateway Tool are also installed.
System Emergency Resume Installing Emergency WS software. By default, the Client software
Workstation and Gateway Tool are also installed.
VI. Configure the system
Now you have to provide some information needed for the server installation:
1) Select program menu name and program path
The program menu is used for starting the program from the [Programs] menu.
The program path stores all software programs and Help files of the BAM Server
system. A hard disk space of 100 MB~200 MB should be reserved for this path.
2) Set location of programs
2-6
All the BAM program files will be stored in the specific directory. The default
directory is D: \CMSC.
3) Configure information about system administrator
This step is to configure the login account and password of M800 CDMA MSC
system administrator.
z The system adminstrator account is "admin" by default and cannot be
modified by the user.
z The system adminstrator password should be 1 to 15 digits long, excluding
the function keys or control keys. And the password cannot be null.
4) Configure information about the local office
The office name can be 1~30 characters long. The office name uniquely identifies
the office and will be used in later operations such as for report output. It is
recommended to use a name easy to be understood and remembered.
5) Set the location for system database
All the system databases generated during the operation process will be stored in
the directory specified in this step. The default directory is D: \CMSC\ HOSTDATA.
Note:
Recent configuration requires about 1 GB of hard disk space. Switch tasks and clean up the disk space if
system prompts disk space insufficient for server installation.
6) Set the location for storing system database log

All the log files generated during the running of the BAM will be stored in the
directory specified in this step. The default directory is E: \CMSC\ MSSQL\DATA,
which requires about 1 GB of hard disk space in the current environment.
7) Set the location for loading data
All data and programs that need to be dynamically loaded when the host starts will
be stored in the directory specified in this step. The default directory is D: \CMSC.
Caution:
During the configuration of the MSC data via the operation and maintenance terminal for entire system
configuration, all data that needs to be sent to the host are also stored in this directory in form of files. Do
not delete the files in this directory!
2-7
8) Set up the location for storing system backup data

The backup data during BAM system operation will be stored in the System
Backup directory, including backup data of the database, registry, and other data.
This directory is under F:\CMSC by default, and requires space of 1GB.
9) Set time synchronization options (Optional)
To synchronize with the M2000 Server, select "Have M2000 Server" and set the IP
address of the M2000 Server, as shown in Figure 2-3.
Figure 2-3 Time synchronization options
Note:
The installation can also be successfully performed without the IP address of the M2000 Server.
In need of synchronizing with the M2000 Server afterwards, you can select the clock synchronization
process to set the time synchronization options.
10) Verify SQL Server rights

When the above configuration is finished, the setup program will verify SQL Server
rights. As data operations of the whole BAM system are based on the SQL Server
system, the validity of installation needs to be checked to ensure the data security.
2-8
Figure 2-4 SQL Server name
The default server is ".", as shown in Figure 2-4.
Input the SQL Server system logon account "sa" (the default database super user)
and password (null by default).
The system will verify the login account and password.
Note:
If there is something wrong with the SQL Server installation and the login is rejected, an alert message box
will pop up and the setup process will stop. In this case, check the SQL Server installation options, and run
the setup program again if necessary.
11) Select voice type

The system can support English voice. The voice type selected here is the second
voice type. For example, with "Arab" selected, the system will support two
languages: English and Arab.
Select the type of voice files as needed.
Now all the information required in the BAM Server software installation is configured.
Then the setup program will display part of the parameters already set. You can accept
them to enter next stage of installation, or go back to make modifications.
2-9
VII. Copy files
In this step the system will create directories and copy the necessary files. In the
process of file copying, the setup program will show the overall progress, available disk
space, available memory, progress of individual file copying, etc.
VIII. Process data
After the file copying is finished, the setup program will start processing the data
needed by the BAM Server.
In SQL Server 2000, the setup program will use the "sa" password to log on and create
database files. If the operation succeeds, the following database files should be
generated in the database server:
Database Files (default)

Alarm_Data.MDF D: \CMSC\Mssql\Data\Alarm_Data.MDF
Alarm_Log.LDF E: \CMSC\Mssql\Data\Alarm_Log.LDF
Bam_Data.MDF D: \CMSC\Mssql\Data\Bam_Data.MDF
Bam_Log.LDF E: \CMSC\Mssql\Data\Bam_Log.LDF
Stats_Data.MDF D: \CMSC\Mssql\Data\Stats_Data.MDF
Stats_Log.LDF E: \CMSC\Mssql\Data\Stats_Log.LDF
Test_Data.MDF D: \CMSC\Mssql\Data\Test_Data.MDF
Test_Log.LDF E: \CMSC\Mssql\Data\Test_Log.LDF
Vdp_Data.MDF D: \CMSC\Mssql\Data\Vdp_Data.MDF
Vdp_Log.LDF E: \CMSC\Mssql\Data\ Vdp_Log.LDF
After the databases are created, the setup program will initialize the databases and
process the initial data in them. This process lasts a period of time ranging from ten
minutes to several hours, depending on the database capacity and the machine
efficiency. After the BAM system databases are processed, the SQL Server should
contain the following databases:
Database Function
Alarm For alarm process
BAM For system
Stats For traffic statistics process
Test For test process
Vdp For long distance IP contracting
2-10
These databases are created respectively in the corresponding database files, and the
property of each database has already been correctly set.
Among them, the four properties [auto create statistics], [auto update statistics], [select
into/bulkcopy] and [trunk.log on chkpt] are set as "TRUE" while the rest are set as
"FALSE".
Caution:
As the database properties are essential to the execution of some programs, do not modify those
properties unless out of absolute necessity.
IX. Refresh environment parameters
When the task in the last step is accomplished, the setup program will register the BAM
system information in the Windows 2000 Server system, add the dependent
environment variables, set program auto-run function, create or update program
menus, etc.
X. Complete the installation
After the above steps are successfully completed, the setup program will pop up the
[Setup Complete] window, prompting you whether to restart the server immediately. To
validate the updates, restart the server immediately.
Till now, installation of the whole BAM Server is completed. The BAM Server software
will automatically start when Windows 2000 Server restarts each time.
2.2.3 Checking the Installation
The computer will restart when the BAM Server software installation is completed. After
that, the main interface of BAM Server program will pop up. If the statuses of all
processes are shown as "Started", it indicates that the installation is successful and the
BAM Server is running normally.
If the statuses of some processes are shown as "Exception", that means the installation
is not completely successful, in which case you need to reinstall it or contact Huawei
technical support personnel for help.
If BAM Server software (BAM Manager) does not start normally, the possible reasons
could be:
2-11
z The "Binary order" is not selected during installation of SQL Server.

z "Use the Local System Account" is not selected during installation of SQL Server.
2.2.4 Description of BAM System Directories
Suppose the default directories are selected during the installation process, when BAM
Server software installation is finished, the files and directories in the BAM Server can
be described as follows:
I. Program file directory
After the Server software is installed successfully, the setup program will create
directory D:\CMSC. By default, the BAM Server programs and some of the system data
will be stored there. The directory structure is shown in the following table:
Path Description
D: \CMSC This directory is used to store system startup execution files;
D: \CMSC\SERVICES This directory is used to store executable files of BAM program.
D: \CMSC\HOSTDATA This directory is used to store system host loading files.
This directory is used to store Help files of MML, Alarm Management
D: \CMSC\ONLINEHELP System, Performance Measurement System and Service Maintenance
System.
This directory is used to store LMT executable programs and the
D: \CMSC\BIN
corresponding supporting files.
This directory is used to store LMT database files, configuration files and
D: \CMSC\DATA
other supporting files.
D: \CMSC\TRACE This directory is used to store all tracing files.
D:\CMSC\Log This directory is used to store LMT log files.
D: \CMSC\MSSQL This directory is used to store database files.
The files saved in the above directories are described in brief as follows:
z D:\CMSC is used to store the system startup execution files.
File Description
D: \CMSC\convert.exe System communication gateway tool
D: \CMSC\macro.ini Configuration file of Client program
D: \CMSC\securitymanager.exe Startup file of server monitoring
D: \CMSC\uninstall.exe Execution file of system uninstallation
D: \CMSC\isuninst.exe Supporting file of system uninstallation
D: \CMSC\uninst.isu Information file of system uninstallation
2-12
File Description
D: \CMSC\VMSCBam.ini Configuration file of BAM Server
D: \CMSC\WsGate.exe Workstation gateway software
z D:\CMSC\SERVICES is used to store the system program supporting files.

File Description
D: \CMSC\smirror.Exe Synchronization service program
D: \CMSC\services\bamservice.exe Module file of system monitor service
D: \CMSC\services\dataman.exe supporting module of Data management service
D: \CMSC\services\exchange.exe communication module of BAM bottom layer
D: \CMSC\services\maintain.exe Supporting module of Maintenance service
D: \CMSC\services\stats.exe Supporting module of Traffic statistics service
D: \CMSC\services\test.exe Supporting module of Test service
D: \CMSC\services\warn.exe Supporting module of Alarm service
D: \CMSC\services\logman.exe System authentication management service module
D: \CMSC\services\mml.exe MML command interface processing module
D: \CMSC\services\logman.tlb Supporting file of system operation
D: \CMSC\services\makecrc.exe Supporting file of system operation
D: \CMSC\services\isql.exe Supporting file of uninstall program
D: \CMSC\services\dbremover.dat Supporting file of uninstall program
z D:\CMSC\ONLINEHELP stores MML online help system files, which are

described below:
File Description
D:\CMSC\onlinehelp\ALARM-ONLINEHELP.chm Help file of Alarm Management System
D:\CMSC\onlinehelp\Cc128toc.idx Supporting file of MML Client program
D:\CMSC\onlinehelp\ MML-ONLINEHELP.chm MML help file
D:\CMSC\onlinehelp\Frame_onlinehelp.chm Help file of Service Maintenance System
D:\CMSC\onlinehelp\Performance_onlinehelp.chm Help file of Performance Measurement System
II. System data file directory
BAM Server data storing directory stores the routine operational data of the system.
z D: \CMSC\MSSQL\DATA is used to store the following files:
2-13
File Description
d: \CMSC\Mssql\Data\alarm_data.mdf Physical data file for the Alarm Database
d: \CMSC\Mssql\Data\bam_data.mdf Physical data file for the Bam Database
d: \CMSC\Mssql\Data\vdp_data.mdf Physical data file for the Vdp Database
d: \CMSC\Mssql\Data\stats_data.mdf Physical data file for the Stats Database
d: \CMSC\Mssql\Data\test_data.mdf Physical data file for the Test Database
The BAM Server log storing directory stores the routine operational logs of the system.
z E: \CMSC\Mssql\Data is used to store the following files:
File Description
e: \CMSC\Mssql\Data\alarm_log.ldf Physical log file corresponding to the Alarm Database
e: \CMSC\Mssql\Data\bam_log.ldf Physical log file for the Bam Database
e: \CMSC\Mssql\Data\vdp_log.ldf Physical log file for the Vdp Database
e: \CMSC\Mssql\Data\stats_log.ldf Physical log file for the Stats Database
e: \CMSC\Mssql\Data\test_log.ldf Physical log file for the Test Database
III. Loading data file directory
The BAM Server loading data storing directory stores MSC loaded programs and
hardware/software configuration data.
z D: \CMSC\HOSTDATA stores the following files:
File Description
D: \CMSC\HOSTDATA\Cc08.amp AMP Loading program
D: \CMSC\HOSTDATA\Cc08.cdp CDP Loading program
D: \CMSC\HOSTDATA\Cc08.ncc GNCC Loading program (GSPC)
D: \CMSC\HOSTDATA\cc08cpc.ncc GNCC Loading program (GCPC)
D: \CMSC\HOSTDATA\cc08.vdp GVDP Loading program
D: \CMSC\HOSTDATA\cc08.spc GSPC Loading program
D: \CMSC\HOSTDATA\Cc08.bcp GBCP Loading program
D: \CMSC\HOSTDATA\Cc08.bcc GBCC Loading program
D: \CMSC\HOSTDATA\Cc08.cdi GCDI Loading program
D: \CMSC\HOSTDATA\cc08.mhi GMHI Loading program
D: \CMSC\HOSTDATA\cc08_2.spd GSPD Loading program
2-14
File Description
D: \CMSC\HOSTDATA\cc08.src GSRC Loading program
D: \CMSC\HOSTDATA\Cc08.hn7 GHN7 Loading program
D: \CMSC\HOSTDATA\cc08n7.cpc
D: \CMSC\HOSTDATA\cc08cas.cpc
D: \CMSC\HOSTDATA\cc08pra.cpc GCPC Loading program
D: \CMSC\HOSTDATA\cc08rsa.cpc
D: \CMSC\HOSTDATA\cc08v5.cpc
D: \CMSC\HOSTDATA\e16.bin GE16 Loading program
D: \CMSC\HOSTDATA\et16.bin GE16 Loading program
D: \CMSC\HOSTDATA\gecs.bin GECS Loading program
D: \CMSC\HOSTDATA\gecp.bin GECP Loading program
D: \CMSC\HOSTDATA\stu.bin GSTU Loading program
D: \CMSC\HOSTDATA\stu2.bin GSTU Loading program
D: \CMSC\HOSTDATA\qsi.bin GQSI Loading program
D: \CMSC\HOSTDATA\bac.bin GBAC Loading program
The subdirectory D:\CMSC\HOSTDATA\Voice is used to save voice loading files

named by numbers in hexadecimal format. The contents under the directory "800", and
"600" are the same after the installation, that is, they are all standard English voice files.
The voice files for other countries or areas are saved under the directory "All voice files"
of version installation file.
Directory Description
D:\CMSC\HOSTDATA\Voice\800 Used to save standard English voice files
D:\CMSC\HOSTDATA\ Voice\600 Used to save standard English voice files
D:\CMSC\HOSTDATA\ Voice\English Used to save English voice files for intelligent service.
D:\CMSC\HOSTDATA\ Voice\Grammer Used to save parse module files
Caution:
After the server programs are running, data configuration files needed by the MSC such as Db_?.dat will
be generated according to the configuration commands by the user. Do not delete the files in this directory!
2-15
IV. Windows 2000 server system directory
C:\Winnt\SYSTEM32 stores the monitoring service control programs of the system.
File Description
Bamalarm.pma Configuration file of performance monitor
Dynamicmonitor.exe Supporting file of performance monitor
V. Description of other folders
While BAM Server software is running, the program will create directory F: \CMSC (for
system data backup) and directory F: \CMSC\STATS (for storing traffic statistics files).
Do not delete those directories.
2.3 Upgrading and Uninstalling BAM Server Software
In some cases, you may need to upgrade or uninstall the BAM Server software. Before
you do this, you should stop the services of BAMService and Smirror.
BAMService monitors the operational status of BAM Server software. If BAM is not
started again in two minutes after it is shut down, BAMService will regard the case as
operational error, and it will try to restart BAM. Therefore, to ensure successful
upgrade/uninstallation of BAM Server software, this service should be stopped before
the operation.
2.3.1 Upgrading BAM Server Software
I. Preparation
z Obtain the new BAM Server software packet.

z Stop Smirror and BAM service.
z Stop the running of all applications.
z Backup system data.
II. Run SETUP.EXE
1) Copy the software packet to the hard disk of BAM Server, and run the
SETUP.EXE in the packet under the directory “\OMC\BAM”. A dialog box as
shown in Figure 2-5 will pop up.
2-16
Figure 2-5 Upgrade BAM Server Software
2) Select “Update MSC Server Program” and click <Next>.

3) Follow the instructions given in section “2.2.2 VI. Configure the system” to
complete the installation.
2.3.2 Uninstalling BAM Server Software
The procedure of uninstalling BAM Server software is as follows:

1) Stop Smirror and BAMService.
2) Close all applications.
3) Use the uninstall program that comes with the program to uninstall it.
For those which can not be deleted, click <Details> to locate the directories and
files, and delete them manually.
4) If the program does not have an uninstall program, use [Add/Remove Programs]
in the [Control Panel] to uninstall the software.
When you see the prompt: "Uninstallation completed, some files can not be
deleted, you should delete them manually", click <Details> to locate the directories
and delete them manually.
5) Delete all the directories of applications in drives D, E and F.
6) Restart Windows 2000 Server and check the directories to make sure that the
directories of the application and everything in them have been deleted.
2-17
Caution:
Do follow the steps described above to restart Windows 2000 Server, otherwise system files may get lost
and system failure may be caused.
7) Start the registry editor and locate \\HREY_LOCAL_MACHINE\SOFTWARE to

check if "HUAWEI" entry has been deleted. If not, delete it manually;
8) Empty the recycle bin.
2.4 Installation Problems and Troubleshooting
2.4.1 Common Problems and Troubleshooting
The following are common problems and handling methods with BAM Server software
installation:
z If the installation is to be done through network instead of by copying the
installation files to the hard disk of the computer, it is better to map the network
directory as a local drive. Otherwise, the installation may fail due to the long
directory name.
z If the previous installation is terminated abnormally, some information may still be
left in the system registry. In this case, in the step of selecting the setup type
during reinstallation of the BAM Server software, an option to update the system
instead of the option "Administration System Server" may appear. In this case, you
can follow the procedure in section 2.4.2 to manually delete the registry
information.
z If the previous installation is terminated abnormally, the database might not have
been completely deleted and file copying may fail as a result. In this case, you
should completely delete the database, for which purpose manual deletion can be
considered. You can follow the procedure in section 2.4.3 to manually delete the
Database .
z If you get the error message "Database initiation failed!" or "Some errors occurred
when copying!" during the software installation, please check if the Smirror or
BAMService services are still running, or if there are other programs using the
databases, especially those programs on the network. If so, stop Smirror and
BAMService, close those applications which are using the databases, delete the
databases and programs manually and start the installation again.
z If the BAM program can not be uninstalled, try deleting the registry, and then the
databases, and then the program files manually.
The following describes the operations of manually deleting registry, database and
BSM program envolved in handling these problems.
2-18
2.4.2 Manually Deleting Registry
Before the operation, you have to make sure that there is no important data in the
registry, or all the important data has been backed up.
To delta the registry manually,

1) Click [Start/Run], type in "regedit" and press <Enter>, as shown in Figure 2-6.
Figure 2-6 Running regedit
2) In [Registry Editor], locate HKEY_LOCAL_MACHIN/SOFTWARE/Huawei, as

Figure 2-7 Registry editor
3) Delete the CMSC directory, and then quit the Registry Editor.
2-19
2.4.3 Manually Deleting Database
Before the operation, you have to make sure that there is no important data in the
registry, or all the important data has been backed up.
To delete the databases manually,

1) Click [Start/Run], type in "isqlw" and press <Enter>, as shown in Figure 2-8.
Figure 2-8 Running isqlw
2) When the [SQL Server Query Analyzer] appears, log in to the local databases as
"sa".
The interface as shown in Figure 2-9 will appear.
Figure 2-9 SQL Server query analyzer
3) Type the following scripts in [SQL Server Query Analyzer]:

sp_detach_db Bam
go
2-20
sp_detach_db Alarm
go
sp_detach_db Stats
go
sp_detach_db Test
go
sp_detach_db VDP
go
4) Press <F5> to run the scripts.
5) When execution finishes, close [SQL Server Query Analyzer].
2.4.4 Manually Deleting Program
To manually delete the program,

z Delete directories D:\CMSC, E:\CMSC and F:\CMSC.
Caution:
Before deleting the program, make sure that there is no important data or backup has been made for the
data, and the registry and databases have been completely deleted.
2-21
HUAWEI M800 CDMA Mobile Switching Center Chapter 3 Installation of Client Software
Chapter 3 Installation of Client Software
This chapter describes installation, configuration and removal of Client software.
3.1 Installing Client Software
The Client software is installed on the LMT with Windows 2000 Professional.
The LMT software provides terminal maintenance for the maintenance personnel.
The user can log into the BAM Server via the Client after the installation of LMT
software which is of the same version as the BAM Server. Then the user implements
the operation and maintenance of the host in the Client through the LMT software. In
addition, the LMT software allows the login to the BAM Server of different versions
and NEs.
The installation procedure of Client software is almost the same as that of the BAM
Server software. The difference lies in the step to select the setup type:
z In the [Setup Type] interface, select [MSC Administration System Client], as
Figure 3-1 Selecting Client software
3-1
3.2 Configuring the LMT
The LMT cannot log into a BAM Server unless information of the server is configured.
You can configure information of the BAM Server in the Local NE Management
System. Multiple servers can be configured to realize maintenance of multiple servers
at the single LMT.
The specific procedures are described as follows:

1) Select [Start\Programs\iMnanager M2000\Local WS] to pop up the [Local NE
Management System], as shown in Figure 3-2.
Figure 3-2 Local NE management system
2) Click <Configure> to pop up the dialog box shown in Figure 3-3.

3) Set the "BAM Name", "BAM IP" and "BAM Type" respectively and click <Add>.
In configuring the BAM Server, input the name of the office where the BAM
Server is located for "BAM Name", input the TCP/IP address of the BAM Server
for "BAM IP", and select "CMSC" for "BAM Type".
Caution:
Be sure to select "CMSC" for "BAM Type", otherwise the LMT cannot log into the BAM Server normally.
3-2
Figure 3-3 Configuring BAM
4) To configure other BAM Servers, repeat steps 2 and 3.
Caution:
Both the office name and the server IP address should not be used more than once. Otherwise the
installation program will prompt the existence of identical office names or IP addresses. In the current
version, the number of servers that can be added is limited to 16. To add more servers as required,
through the LMT, you can modify the information of servers that the LMT can log in to.
5) After the setting, click <Exit> to return to the interface as shown in Figure 3-2.
The information of the configured BAM Servers is shown in the interface, as
3-3
Figure 3-4 The configured BAM Server
Now configuration of the BAM Servers to be connected is completed.
3.3 Starting the LMT
To start the LMT, select the BAM Server in the dialog box shown in Figure 3-4 and
click <OK>. You will enter the main interface of Service Maintenance System of the
selected BAM Server.
For detailed description of the operations in the Service Maintenance System, see
M800 CDMA Mobile Switching Center Operation Manual – Routine Operation.
3.4 Uninstalling Client Software
Generally, the Client software needs no uninstalling. If it has to be uninstalled due to

some special causes, take the following steps:
1) In the interface as shown in Figure 3-4, select the BAM Server corresponding to
the LMT from which the Client software is to be uninstalled and click <Uninstall>.
The dialog box will pop up, as shown in Figure 3-5.
Figure 3-5 Confirming the un-installation
3-4
Caution:
As uninstalling the Client software on one LMT may affect the maintainability of the NEs maintained by
all the BAM Servers of the same software version, you shall check the system and then confirm the
uninstallation.
2) Click <OK> to confirm the operation.

The program will uninstall this software automatically.
3) After the uninstalling, restart the computer as per the prompt.
3.5 Description of Client Software Directories
After the successful Client software installation, the installation program will have
created the directories you have designated and placed Client software programs in it.
These directories and their contents are given as follows:
Directory Description
This directory is used to store the execution files for starting or
D:\CMSC
uninstalling the system.
This directory is used to store the LMT executable programs and
D:\CMSC\BIN
supporting files.
This directory is used to store the database files, configuration files and
D:\CMSC\DATA
other supporting files of LMT.
This directory is used to store the online help files for MML, Alarm
D:\CMSC\ONLINEHELP Management System, Service Maintenance System and Performance
Management System.
D:\CMSC\TRACE This directory is used to store the tracing files.
The files in these directories are similar to those in the corresponding directories of
the BAM Server. See "Chapter 2 Installation of BAM Server Software " for details.
3-5
HUAWEI M800 CDMA Mobile Switching Center Chapter 4 Installation of Emergency WS Software
Chapter 4 Installation of Emergency WS Software
This chapter describes the installation of emergency workstation software and how to
start the emergency workstation to replace the BAM server.
4.1 Introduction to Emergency Workstation
4.1.1 Function of the Emergency WS
The BAM system software, Windows NT and BAM Server hardware may be
destroyed by some unpredictable events or force majeure, which may result in BAM
system failure. An emergency WS should be installed in case of this accident.
M800 CDMA MSC provides a set of emergency WS software. While this software is
running, data in BAM database can be synchronized automatically via the network.
By default, the synchronization is originated by Smirror service once every four hours.
In the event that the running BAM Server fails due to some causes, the emergency
WS will be started as quickly as possible to restore data. Meanwhile, the IP address
of the emergency WS will be changed into that of the BAM Server so that it can
communicate with the MSC instead of the BAM.
4.1.2 Hardware and Software Configuration of the Emergency WS
The emergency WS is configured the same with the LMT in terms of hardware. The
software configuration is: Windows 2000 Professional + SP3 as the operating system,
MSSQL Server 2000 Home Edition + SP3 as the database software.
4.2 Installing Emergency WS
Generally, the emergency WS has been installed with Windows 2000 Professional
operating system before delivery. On the site, the following work should be done:
z Configuring the network adapter.
z Installing SQL Server 2000 Home Edition + SP3.
z Installing Emergency WS software.
4.2.1 Configuring the Network Adapter
Generally, the emergency WS can be connected to two network segments:
4-1
z The network segment in the internal Local Area Network (LAN) connected with
the boards of the MSC, i.e. 172.20.0.0. This configuration applied to the case
that the emergency WS temporarily takes the place of the BAM Server.
z The network segment in the external LAN of the local O&M system, which is the
major working network segment of the emergency WS. This network segment is
usually provided by the user. In practice, a network segment other than 172.20
can be designated, but it must be the one adopted by BAM, LMT and emergency
WS.
The following describes the procedure of configuring the network adapter with the
second case as example.
1) Select [Start\Settings\Network and Dial-up Connection].
The [Network and Dial-up Connection] box appears, as shown in Figure 4-1.
Figure 4-1 Network and dial-up network
2) Double click [Local Connection].

The [Local Connection Status] dialog box appears, as shown in Figure 4-2.
4-2
Figure 4-2 Local connection status
3) Click <Properties>.
The [Local Connection Properties] dialog box appears, as shown in Figure 4-3.
4-3
Figure 4-3 Local connection properties
4) Select "Internet Protocol (TCP/IP)" and click <Properties>.

The [Internet Protocol (TCP/IP) Properties] dialog box appears, as shown in
Figure 4-4.
4-4
Figure 4-4 Internet protocol (TCP/IP) properties
5) Set the "IP address", "Subnet Mask" and "Default Gateway" properly.
Among them, the input IP address should not conflict with the IP addresses of
the computers in this LAN, the subnet mask is "255.255.0.0", and the IP address
of the default gateway should be the same with that input for "IP Address", i.e.
the default gateway is itself.
6) Click <OK> to complete the configuration.
Note:
The IP address configuration of the BAM or emergency WS is only for reference. In practice, the IP
address should be configured as per the actual environment.
4-5
4.2.2 Installing SQL Server 2000 Home Edition
The procedure of installing SQL Server 2000 Home Edition is basically the same with
that of installing SQL Server 2000. For details, see "Appendix A Installation of
Operating System and Database Software".
4.2.3 Installing Emergency WS Software
The software installation procedure of the emergency WS is basically the same as

that of the server The difference lies in the following steps:
I. Select the setup type
After correct user information is input, the setup program will verify whether the valid
BAM system software is installed, then it will pop up the [Setup Type] dialogue box.
z Select [M800 MSC System Emergency Resume Work station] to install the
emergency workstation.
II. Configure the system
When configuring the system, in addition to the information required for server
installation, you need to configure the BAM Servers to be connected with this
emergency WS and the directories of the data to be synchronized, as shown in Figure
4-5 and Table 4-1.
Caution:
Generally, the emergency WS only needs to synchronize one directory of the BAM Server. Only
information in the first line of the dialog box as shown in Figure 4-5 can be configured. Otherwise the
program will fail to run normally after installation.
"Server Name" is the computer name or IP address of the BAM Server. If you input the IP address here,
make sure that it is in the same network segment with the emergency WS.
If the standard setup is adopted in BAM Server installation, input "F:\CMSC\" for the "Origin DIR".
4-6
Figure 4-5 Configuring synchronization data of the emergency WS
The description of each field is shown in Table 4-1.
Table 4-1 Description of synchronization data configuration
Field Meaning Configuration description

The IP address configuration is relevant with the network
Name or IP address of
segment where the emergency WS is located. Normally the
Server the BAM Server, the
IP address of the emergency WS is set in the NM network
Name data on which is to be
segment. In this case, input the IP address of the BAM Server
synchronized.
network adapter in the NM network segment.
Directory of the files on

the BAM Server in If the default path is used in BAM Server installation, the
Origin Dir
which the data is to be directory should be F:\CMSC\.
synchronized.
Directory on the Set this directory as per the disk partitioning of the emergency
emergency WS in WS. The setting shown in Figure 4-5 is only for reference.
Target Dir
which the synchronized Note that this directory should be directly under the root
data is to be saved. directory, otherwise backup will not be possible.
4-7
4.2.4 Running Emergency WS Software
The procedure of running emergency WS is the same with that of running the BAM
Server software.
1) Select [Start/Programs/MSC Administration System].
The following program items appear.
z Alarm
z Maintenance
z Sever Gateway Tool
z Server
z Stats
z Online Help Documentation
z Uninstall System
2) Select the item as required.
4.3 Starting the Emergency WS
The emergency WS can be used as an ordinary LMT. When the BAM Server breaks
down due to hardware failure or other causes, follow the steps below to start the
emergency WS to take the place of the BAM Server.
1) Disconnect the network cable of the BSM server from the active LAN Switch
connecting the MSC.
2) Restore the BAM database with the backup data in the emergency WS and
format the data in the offline mode.
3) Set the IP address of the emergency WS into that of the BAM Server (i.e.
172.20.200.200). Connect the network cable of the emergency WS to the active
LAN Switch connecting the MSC (i.e. the network segment 172.20).
4) Perform Cyclic Redundancy Check (CRC) to check the data consistency
between the MSC and the emergency WS.
5) Use the command LON to start the emergency WS.
The procedures are described in details as follows:
4.3.1 Restoring the BAM Database
I. Prepare for restoration
Do the following to prepare for the database restoration:

1) Shut down all applications currently running on the emergency WS.
2) Make sure no other programs or users are connected to the database of the
emergency WS.
3) Disconnect the network cable.
4-8
II. Start BAM setup program
To start BAM setup program,

1) Insert the MSC setup CD into the CD drive.
If the disk auto-run function has been set for the system, the setup program will
run automatically.
----Otherwise----
Locate the SETUP.EXE file in the [Windows Explorer] and click it to run the
program.
2) Click <Next> in the [Welcome] window after the setup program is initialized.
III. Select setup type
As the emergency WS has been installed with the operating system, select the
default option [Restore M800 MSC Environment and Data] and click <Next> to
continue, as shown in Figure 4-6.
Figure 4-6 Restoring MSC environment and data
IV. Restore data
This step is to specify the backup files to be restored.
4-9
z In the dialog box as shown in Figure 4-7, input necessary information and click
<Restore>.
Figure 4-7 Restoring data
V. Process data
Then the system will restore the backup files. The progress of the restoring will be
shown. This process may take several minutes or even several hours, depending on
the database capacity and the machine efficiency.
VI. Complete the installation
When the above steps are successfully completed, the setup program will pop up the
[Setup Complete] window asking you whether to restart the server immediately.
To validate the updates, restart the computer immediately.
VII. Start the BAM system
To start the Bam system after the reboot,

1) Select [Start/Run] in Windows 2000 Server system.
2) Enter "D:\CMSC\SecurityManager.EXE" in the [Run] dialog box and click <OK>.
VIII. Format data
To format the data,
4-10
1) Start up Client program MMLWs.EXE and connect the BAM system of the
emergency WS.
2) Log in as the super administrator "admin".
3) Carry out the following commands:
Sequence Command Description
1 LOF: Set the off-line mode
2 SET FMT: STS=ON; Set the format conversion switch into "ON"
3 FMT; Execute the format conversion
After this, the subsystems for billing, maintenance, alarm and traffic measurement
should all be successfully restored.
4.3.2 Connecting the Network
To connect the network properly,

1) Disconnect the BAM Server from the MSC.
2) Set the emergency WS IP address as the BAM (i.e. 172.20.200.200).
3) Change the network connection of the emergency WS, i.e. in the IMM cabinet,
plug in the network cable of the emergency WS to the 100Mbps network port of
the active LAN Switch used by the MSC.
Note:
Normally, the emergency WS and ordinary WSs are connected to the same LAN Switch, while the MSC
is connected to another (set) of LAN Switch (two LAN Switches may form a set by cascading). The two
BAM network adapters should be connected to these two LAN Switches respectively.
The emergency WS serving as the BAM Server should use the same LAN Switch with the MSC, i.e. the
active LAN Switch.
4.3.3 Checking Data
To keep data consistency between the MSC and the BAM, carry out the command
STR CRC, and mark the names of tables with inconsistent data.
If inconsistent tables are detected:

1) Run LST USD to query the unsent records and run SND USD to send them if
there are any.
4-11
2) Collect the operation records generated after the date of the BAM database
backup files and repeat these operations.
3) Run the command STR CRC again.
4) Do one of the following:
z If all data has passed the check, carry out command LON to start the
emergency WS.
z If the check result is not correct, record the names of the tables with
inconsistent data and contact Huawei technical support personnel.
4.4 Restoring BAM Server and Emergency WS
The BAM Server should resume its operation when the faults are cleared, i.e. the
service should be switched from the emergency WS back to the BAM Server. The
following are the switching procedures:
1) Use the command BKP DB; to back up the system data and registry of the
emergency WS (The default backup path is F:\CMSC, and the file name is
BamYYMMDD.dat) and copy the backup file to another directory.
2) Stop all services in the emergency WS and stop BAM Security Manager.
3) Reconfigure the IP address of the emergency WS and reconnect the network as
per the normal condition.
z Connect the emergency WS to the same LAN Switch as the other WSs, and
configure it in the same network segment.
z Connect one of the BAM Server network adapters to this LAN Switch and
set its IP address in the same network segment as the emergency WS;
Connect the other adapter of the BAM Server and the MSC to another LAN
Switch, and set its IP address as 172.20.200.200.
4) Copy the latest backup file in the emergency WS into the directory F:\CMSC of
the BAM Server.
5) Restore the BAM database with the backup data and format the data in the
offline mode.
6) After checking the data consistency between the MSC and the BAM Server,
connect the BAM Server to the network for service.
The process is the same with that of starting the emergency WS.
7) Install and configure the emergency WS again.
Now, the BAM Server and emergency WS have been successfully restored.
4-12
HUAWEI M800 CDMA Mobile Switching Center Chapter 5 Configuration of Remote Maintenance System
Chapter 5 Configuration of Remote Maintenance

System
This chapter describes the configuration, verification of configuration and tests for the
remote maintenance system server and remote maintenance terminal.
5.1 Introduction to Remote Maintenance System
5.1.1 Basic Theory of Remote Maintenance
M800 CDMA MSC is equipped with a Remote Access Server (RAS) and allows the
dial-up access of remote maintenance terminals through this RAS. The networking of
the remote maintenance system is shown in Figure 5-1.
PSTN
Remote Maintenance terminal

IP:129.9.10.5
Emergency WS
(RAS)
IP:129.9.200.211
LAN
BAM LMT LMT
Figure 5-1 Networking of the remote maintenance system
MSC remote maintenance system is mainly composed of the RAS and the remote
maintenance terminals.
The maintenance personnel can connect the remote maintenance terminal (i.e. the
local computer) to the Public Switched Telephone Network (PSTN) via the Modem
and dial up to the RAS (normally integrated with the emergency WS) connecting the
maintained equipment. Thus, remote maintenance and operation of the online
equipment can be realized via the remote access service provided by Windows 2000
on the RAS.
5-1
5.1.2 Hardware and Software Requirements
I. Hardware requirements
z RAS
The RAS is usually integrated with the emergency WS. The hardware requirement is
the same with that of the ordinary maintenance Client WS.
z Remote maintenance terminal
The remote maintenance terminal can be an ordinary maintenance Client WS or
laptop.
II. Software requirement
z RAS
The RAS uses Windows 2000 Professional (with Service Pack 3 or later version) as
the operating system. It should be installed with Routing and Remote Access Service.
z Remote maintenance terminal
The remote maintenance terminal uses Windows 2000, Windows NT or Windows 98
as the operating system. It should be installed with Dial-up Network and M800 CDMA
MSC Client software. If you want to perform NM operation (e.g. access to multiple
NEs simultaneously) at the remote maintenance terminal, you need to install M2000
Client software as well.
5.2 Configuring the RAS
The following operations of configuring the RAS are based on the Microsoft Windows
2000 Professional.
5.2.1 Configuring the Network Adapters
The following operations are conducted in the [Network and Dial-up Connections]
window as shown in Figure 5-2, which can be shown by selecting
[Start/Settings/Network and Dial-up Connections].
5-2
Figure 5-2 Network and dial-up connections
I. Check local area connection status
1) Double click [Local Area Connection] to pop up the [Local Area Connection]
dialog box as shown in Figure 5-3.
5-3
Figure 5-3 Local Area Connection Status
The [Local Area Connection Properties] dialog box appears, as shown in Figure
5-4.
5-4
II. Set local area connection properties
Figure 5-4 Local area connection properties
1) Select "Internet Protocol (TCP/IP)".

III. Set Internet protocol (TCP/IP) properties
Set the IP address, subnet mask and default gateway of the RAS and dial-up server.
The IP address of the RAS should be in the same network segment with the NEs
maintained by it, and should not be identical with that of any other computer in this
LAN.
In the case that the dial-up service programs are installed on the emergency WS, on
which the IP address, subnet mask and default gateway in the LAN of the operation
and maintenance system have been properly set, you need not set them again.
5.2.2 Installing the Modem
In Windows 2000, most equipments can be identified and installed automatically,

including the Modem. Only in some cases is manual installation necessary. For the
5-5
particular installation of the Modem, you may refer to the installation description for
other equipments (e.g. network adapter).
5.2.3 Configuring the Remote Access Service
The procedures of configuring the remote access service are described as follows:
I. Start the "Network Connection Wizard"
1) Select [Start/Settings/Network and Dial-up Connections/Make New Connection].

The [Network Connection Wizard] interface will appear, as shown in Figure 5-5.
The remote access service can be established step by step through this wizard.
Figure 5-5 Network connection wizard
2) Click <Next>.
The [Network Connection Type] dialog box will pop up, as shown in Figure 5-6.
5-6
Figure 5-6 Network connection type
II. Select network connection type
1) Select "Accept incoming connections".

This option is to make the computer accessible for other computers via
telephone line or Internet.
2) Click <Next> to continue.
The [Devices for Incoming Connections] pops up, as shown in Figure 5-7.
5-7
Figure 5-7 Devices for incoming connections
III. Select devices for incoming connections
The installed Modem will be displayed in the list [Connection devices], as shown in
Figure 5-7. And this Modem will be used for the setup of the RAS.
z Select the Modem from the list, and click <Next> to continue.
The [Incoming Virtual Private Connection] dialog box will pop up, as shown in
Figure 5-8.
5-8
Figure 5-8 Incoming virtual private connection
IV. Choose whether to allow virtual private connections
z Select "Do not allow virtual private connections", and click <Next> to continue.
The [Allowed Users] dialog box will pop up, as shown in Figure 5-9.
Figure 5-9 Allowed users
5-9
V. Add allowed users
The RAS requires a specified dial-up user who can access this computer.
1) In the dialog box as shown in Figure 5-9, click <Add>.
The dialog box [New User] will pop up, as shown in Figure 5-10.
Figure 5-10 New user
2) In [User Name], [Password] and [Confirm Password], enter "dial", then click
<OK> to return to the previous interface.
The interface after dial-up user adding is shown in Figure 5-11.
Figure 5-11 Dial-up user added

The [Networking Components] dialog box will pop up, as shown in Figure 5-12.
5-10
Figure 5-12 Networking components
VI. Set networking components
Three networking components are listed in the [Networking Components] dialog box,
namely,
z Transfer Control Protocol/Internet Protocol (TCP/IP)
z File and Printer Sharing for Microsoft Networks
z Client for Microsoft Networks
The default setting is to select all networking components, without any change.
However, note that the network setting on Client must be consistent with the default
setting on the Server, otherwise the dial-up user cannot access the local computer.
1) Select "Internet Protocol (TCP/IP)", and click <Properties>.
The [Incoming TCP/IP Properties] dialog box will appear, as shown in Figure
5-13.
5-11
Figure 5-13 Incoming TCP/IP properties
2) Set the properties in this dialog box as follows:

z In [Network Access], select "Allow callers to access my local area network".
z In [TCP/IP Address Assignment], select "Specify TCP/IP addresses".
z Specify the IP address range as from129.9.10.0 to 129.9.10.30.
Only dial-up users in this address range can get access to this computer.
3) Click <OK> to return to the dialog box shown in Figure 5-12.
The [Completing the Network Connection Wizard] dialog box will pop up, as
5-12
Figure 5-14 Completing the network connection wizard
VII. Complete the network connection wizard
1) Select the default name for the new network connection "Incoming Connections".
2) Click <Finish> to complete the setting.
Now a new icon [Incoming Connections] is added in the [Network and Dial-up
connections] dialog box, as shown in Figure 5-15.
Figure 5-15 [Incoming Connections] added
5-13
VIII. Configure Routing and Remote Access service
1) Select [Start/Settings/Control Panel/Administrative Tools/Services].

The window [Services] will pop up, as shown in Figure 5-16.
Figure 5-16 Services
During the installation of Windows 2000 Professional, the Routing and Remote
Access service has been installed by default, but not started up, as shown in
Figure 5-16. To enable the RAS to operate normally, this service should be set
as "Started".
2) In Figure 5-16, select "Routing and Remote Access" and double click.
The [Routing and Remote Access Properties (Local Computer)] dialog box will
appear, as shown in Figure 5-17.
5-14
Figure 5-17 Routing and remote access properties (local computer)
3) Select "Automatic" for "Startup type", and click <Start>.

The dialog box [Service Control] will appear, as shown in Figure 5-18.
Figure 5-18 Service control
Windows will attempt to start this service and may succeed in several seconds. Then
the status of the Routing and Remote Access service is changed to "Started", as
5-15
Figure 5-19 Routing and remote access service started
Now the RAS configuration is complete.
5.3 Configuring the Remote Maintenance Terminal
Assuming that the Modem is properly installed, the configuration of the remote
maintenance terminal covers the following two aspects:
z Installing MSC Client software.
z Configuring the dial-up network.
In the description below, Windows 2000 Professional is the operating system.
5.3.1 Installing MSC Client Software
See "Chapter 3 Installation of Client Software".
5.3.2 Configuring the Dial-up Network
The procedures of configuring the dial-up network are as follows:
I. Set up a new connection
1) Select [Start/Settings/Network and Dial-up Connections].

The [Network and Dial-up Connections] dialog box will pop up.
2) Double click [Make New Connection] and then click <Next>.
The [Network Connection Type] interface will pop up, as shown in Figure 5-20.
5-16
Figure 5-20 Network connection type
3) Select "Dial-up to the Internet" and click <Next>.

4) In the [Internet Connection Wizard] interface as shown in Figure 5-21, select "I
want to set up my Internet connection manually, or I want to connect through a
local area network (LAN)”, and click <Next>.
Figure 5-21 Internet connection wizard
5-17
5) In the interface as shown in Figure 5-22, select "I connect through a phone line
and a modem" and click <Next>.
Figure 5-22 Selecting the mode to connect to the Internet
6) Set the telephone number to be connected to the RAS and click <Next>, as
5-18
Figure 5-23 Setting the telephone number
7) In the dialog box as shown in Figure 5-24, set the user name and password to
log into the RAS and click <Next>.
5-19
Figure 5-24 Setting the user name and password
8) In the dialog box as shown in Figure 5-25, type in the name of the new
connection ("My Connection" in the example) and click <Next>.
5-20
Figure 5-25 Setting the connection name
9) In the dialog box as shown in Figure 5-26, select <No> and click <next>.
5-21
Figure 5-26 Setting Internet Mail account
10) In the dialog box as shown in Figure 5-27, clear "To connect to the Internet
immediately, select this box and then click Finish" and then click <Finish>.
5-22
Figure 5-27 Completing the new connection setting
Now you can see that the new connection ([My Connection]) has been added in the
[Network and Dial-up Connections] interface, as shown in Figure 5-28.
5-23
Figure 5-28 New connection successfully added
II. Configure the dial-up network properties
1) In the dialog box as shown in Figure 5-28, do the following to select the dial-up
server type:
z Double click [My Connection], and then click the [Networking] tab.
z Select "PPP: Windows 95/98/NT4/2000, Internet" as "Type of dial-up server I
acknowledgement calling" and select all components in the [Components
checked are used by this connection] list, as shown in Figure 5-29.
5-24
Figure 5-29 Dial-up network properties
Caution:
The selection of the components in the dialog box as shown in Figure 5-29 should be the same with that
in the dialog box as shown in Figure 5-12; otherwise, the remote maintenance terminal cannot connect
to the RAS.
2) In the dialog box as shown in Figure 5-29, do the following to configure Internet
protocol (TCP/IP) properties:
z Select "Internet Protocol (TCP/IP)" and click <Properties>.
z In the [Internet Protocol (TCP/IP) Properties] dialog box, select "Obtain an IP
address automatically", as shown in Figure 5-30.
5-25
Figure 5-30 Internet protocol (TCP/IP) properties
3) In the dialog box as shown in Figure 5-30, do the following to set the advanced
TCP/IP settings:
z Click <Advanced>, and then click the [General] tab.
z Select "Use default gateway on remote network" and "Use IP header
compression", and click <OK>, as shown in Figure 5-31.
5-26
Figure 5-31 Advanced TCP/IP settings
Now the dial-up network configuration of the remote maintenance terminal is

completed.
5.4 Checking the Configuration of Remote Maintenance

System
I. Modem check
Note:
To ensure the normal operation of the remote maintenance system, the Modems used by the RAS
(integrated with the emergency WS in this system) and the remote maintenance terminal should be
checked before the remote maintenance system is started. The procedures of checking the two Modems
are the same.
5-27
1) Plug the PSTN telephone wire to the jack labeled with "LINE" on the Modem of
the server.
2) Select [Start/Programs/Accessories/Communications/Phone Dialer] to run the
Phone Dialer program.
The dialog box [Phone Dialer] will pop up, as shown in Figure 5-32.
Figure 5-32 Phone dialer
3) Click on the toolbar to conduct the dial-up test.

The [Dial] dialog box will appear, as shown in Figure 5-33.
Figure 5-33 Dialing test
4) In the [Number] field enter the number of the telephone used for test (e.g.
88888888), and select "Phone Call" in the [Dial As] area. Then click <Place Call>
for test.
5-28
5) Listen whether the tested phone is ringing and whether there is dial tone at the
time of dialing via Modem.
If both are normal, the Modem is normal and correctly installed. Otherwise,
problems exist with Modem installation and configuration. In this case, the
installed Modem needs to be removed and re-installed.
II. Remote access service check
The remote access service is provided by the RAS.
To check the remote access service,

z Select [Start/Settings/Control Panel/Administrative Tools/Services].
In the pop-up dialog box [Services] as shown in Figure 5-16, if the status of the
Routing and Remote Access service is "Started" and the start mode is
"Automatic", the service is normal.
5.5 Testing the Remote Maintenance System
After the installation, take the following steps to conduct the system test:
1) Do the following to make preparations for the test:
z Install the Modem on the computer used for test.
z Connect the Modem to the telephone line. Make sure that the Client software
has been installed and the dial-up network has been configured.
2) Do the following to run the dial-up connection program:
z Enter the user name and the password "dial" in the dialog box as shown in
Figure 5-34.
5-29
Figure 5-34 Dial-up connection program
z Click <Properties>.
The [My Connection] dialog box will appear, as shown in Figure 5-35.
5-30
Figure 5-35 Dial-up connection properties
z Check that the number in the [Telephone number] box is that of the telephone
connecting the RAS (e.g. 88888888 as in this example).
z Click <OK> to return to the dialog box as shown in Figure 5-34 and click <Dial>
to continue.
Now you can hear the dial tone and the Modem handshaking tone. After a while,
if you can see the indication in the status bar of the computer used for test or the
RAS, which indicates that the network is connected and the dial-up service is in
normal operation.
3) Select [Start/Run] and enter the command Ping in the dialog box, e.g.:
ping 10.129.20.20
The IP address 10.129.20.20 is the IP address of the BAM Server.
If the connection is normal, the following information will be displayed:

Pinging 10.129.20.20 with 32 bytes of data:
Reply from 10.129.20.20: bytes=32 time<10ms TTL=126
5-31
Ping statistics for 10.129.20.20:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
This indicates that the network connection of remote maintenance system is

successful.
4) Run the Client software to log into the BAM Server to be connected.
If the login is successful and operations can be normally conducted, that means
the remote maintenance system is in normal operation.
Note:
The default authority of WSs is low, if more authorities are needed for the remote maintenance terminal,
add WS authority to the remote maintenance terminal from the local maintenance system.
5-32
HUAWEI M800 CDMA Mobile Switching Center Chapter 6 Software Loading
Chapter 6 Software Loading
This chapter describes the loading of the MSC software and troubleshooting.
6.1 Introduction to Software Loading
6.1.1 Function
Software loading is to load the host programs and data files in the loading directory of
the BAM Server to the host (MSC). It applies in the following cases:
I. First-time software installation upon deployment
1) Upon the new deployment, install the BAM Server software onto the BAM Server,
then there will be the host programs in the loading directory of the BAM Server.
Caution:
For some versions, you may need to copy some board software programs from the software installation
package. Refer to the corresponding release notes for details.
2) Then configure data in the off-line status (You can also use the data script files
to complete data configuration by the batch command.).
3) After configuration, execute the format conversion command FMT, and there will
be data loading files in the loading directory of the BAM Server.
4) Use the command MOD LSS to set the board loading software switch as
"Program unavailable, data unavailable, program rewritable, data rewritable", so
that the programs and data can be loaded from the corresponding files on the
BAM Server.
5) Execute the command LON to connect the server to the network.
6) Load the host programs and data files in the loading directory of the BAM Server
to the MSC.
II. Software update or software upgrade
1) Upon software upgrading, upgrade the BAM Server software first.

2) Load the host software and data files in the loading directory of the BAM Server
to the MSC to update the programs and data in operation.
6-1
III. Modification of certain data
Normally data configuration is implemented in the online status, and the commands
can be set online. However, you may need to load the corresponding board to
validate some configuration data, as in the case of modifying the maximum number of
tuples by the command MOD MAXT.
6.1.2 Loading Methods and Items for Attention
I. Loading methods
Two methods are available for loading host programs and data, as shown in Figure
6-1 and Figure 6-2.
z Load programs and data directly from the BAM to the DRAM.
z Load programs and data from the Flash Memory to the DRAM.
In Figure 6-1, "1" indicates loading programs and data directly from the BAM to the
DRAM; "2" indicates writing the programs and data in the DRAM into the Flash
Memory; "3" indicates loading programs and data directly from the Flash Memory to
the DRAM if necessary.
Flash Memory DRAM
2 C
P
Program
Data
U
3
GAMP
BAM
Program Data
Figure 6-1 Loading host software to the AMP board
Figure 6-2 shows the loading of host software to the GBAC through the AMP.
6-2
Flash Memory DRAM

C
3
Program
P
Data
4 U
GBAC
Flash Memory DRAM

C
P
Program
Data
GAMP
BAM
Program Data
Figure 6-2 Loading host software from AMP to GBAC
The normal method to load software to the AMP is to reset the board to be loaded.
Namely, reset the board first, or switch off its power and then restart it.
II. Important items for board loading
Upon loading, pay attention to the settings of switches. The major switches on the
board concerning loading are the path selection switch and the backup switch.
z Loading path selection switch
Upon board reset, programs and data will be loaded to the RAM of the board. The
programs and data may come from the Flash Memory of the board, or the BAM
Server. You can use the path selection switch to select the path for the programs and
data to be loaded.
Caution:
In the case of loading from the Flash Memory, you shall make sure that the Flash Memory has been
written and the version is correct, otherwise the loading may fail or wrong programs may be loaded.
6-3
Through the loading path selection switch, you can set whether the programs and
data (namely, the programs and data in the Flash Memory) are usable. If you set
them as usable, the programs and data in the Flash Memory will be used in loading.
Otherwise, those in the BAM will be used. Also, you can select the loading path for
programs or that for data respectively.
The loading path selection switch of the board is set via the command MOD LSS
(namely, modifying the board loading soft switch).
z Backup switch
The backup switch of the active/standby board maintains consistency between the
programs and data of the active board and those of the standby board.
The backup switch of the boards is set via the command SET BAKMODE (namely,
setting up backup switch).
III. Querying board loading progress
Two methods are available for querying board loading progress:

z Via the Exchange interface.
z Via the active alarms on the MML Client or the maintenance console.
6.1.3 List of Loading Files
The programs and software/hardware configuration data are all stored in the loading
data storage directory of the BAM Server (default: D:\ CMSC\HOSTDATA).
The loading files stored in the directory D:\CMSC\HOSTDATA are described in Table
6-1:
Table 6-1 Description of loading files
File Description
D:\CMSC\HOSTDATA\Cc08.amp AMP program
D:\CMSC\HOSTDATA\Cc08.cdp CDP program
D:\CMSC\HOSTDATA\Cc08.ncc GNCC program (GSPC)
D:\CMSC\HOSTDATA\cc08cpc.ncc GNCC program (GCPC)
D:\CMSC\HOSTDATA\cc08.vdp GVDP program
D:\CMSC\HOSTDATA\cc08.spc GSPC program
D:\CMSC\HOSTDATA\Cc08.bcp GBCP program
D:\CMSC\HOSTDATA\Cc08.bcc GBCC program
D:\CMSC\HOSTDATA\Cc08.cdi GCDI program
D:\CMSC\HOSTDATA\cc08.mhi GMHI program
6-4
File Description
D:\CMSC\HOSTDATA\cc08_2.spd GSPD program
D:\CMSC\HOSTDATA\cc08.src GSRC program
D:\CMSC\HOSTDATA\Cc08.hn7 GHN7 program
D:\CMSC\HOSTDATA\cc08n7.cpc
D:\CMSC\HOSTDATA\cc08cas.cpc
GCPC programs
D:\CMSC\HOSTDATA\cc08pra.cpc
D:\CMSC\HOSTDATA\cc08rsa.cpc
D:\CMSC\HOSTDATA\cc08v5.cpc GCPC programs
D:\CMSC\HOSTDATA\e16.bin GE16 program
D:\CMSC\HOSTDATA\et16.bin GE16 program
D:\CMSC\HOSTDATA\gecs.bin GECS program
D:\CMSC\HOSTDATA\gecp.bin GECP program
D:\CMSC\HOSTDATA\stu.bin GSTU program
D:\CMSC\HOSTDATA\stu2.bin GSTU program
D:\CMSC\HOSTDATA\qsi.bin GQSI program
D:\CMSC\HOSTDATA\bac.bin GBAC program
D:\CMSC\HOSTDATA\cc08pat.spc Patch file
D:\CMSC\HOSTDATA\cc08sym.spc Patch file
The GSPD/GSPT signal tone files are stored in the subdirectory D:\
CMSC\HOSTDATA\Voice. These files are named by numbers.
In the directory D:\ CMSC61\HOSTDATA\Db_?.dat is the data for all modules. For
instance, Db_20.dat is the data for module No.20.
Caution:
After the server program is running, data configuration files required by the MSC such as the file
Db_?.dat will be generated according to the configuration commands of the user. Never delete any file in
this directory.
6-5
6.1.4 Power-on Loading Sequence
Many boards should be loaded separately, including AMP, GBAC, GBCP, CDP, GNCC,
GQSI, GE16, GSTU, GECP, GECS, GMHI, GSRC, GSPT, GSPC, GVDP, GCPC and
GHN7.
I. Loading procedures
The following are the normal loading procedures:

1) Load AMP.;
2) Load the GBAC in the CCM subrack.
3) Load other boards in the required sequence.
II. Recommended loading sequence
The power-on loading must be performed in certain sequence. The following is the
recommended loading sequence:
CKM subrack → AMP→CCM subrack (GBAC) → CPM subrack (GBCP → CDP) →

GNET subrack (GNCC) → internal LIM subrack (GQSI → GMHI) → external LIM
subrack (GQSI → GE16/GSTU/GECP/GECS) → SRM subrack (GSPT/GSRC) →
SPM subrack (GSPC, GVDP, GBCC → GCPC).
6.1.5 Loading Paths and Principles
I. Loading paths
The loading links include the standard 10Mbit/s Ethernet cable, HDLC link, serial port
and the bus on the backplane. One of them or the combination of several of them will
be used for the loading of boards.
II. Loading principles
The MSC system is loaded mainly via the AMP. Other boards cannot be loaded
unless the AMP is loaded successfully.
6-6
Caution:
At most six boards can be loaded in parallel for the MSC. If more than 6 boards request for loading at
the same time, the loading requests of some boards may be repeated for several times with no response
received, and the loading of them may not succeed due to no response (If the Flash Memory has been
written before the unsuccessful board loading, the programs and data in the original Flash Memory will
probably run).
The principles for board loading are shown in Table 6-2. They can be used to detect
the cause why loading cannot succeed.
6-7
Table 6-2 Principles of board loading
Subrack
Board name Loading path Description
name
CPM AMP BAM→AMP AMP can be loaded from BAM via network cable
GBCP shares the same CPM module with AMP, so it can be loaded from AMP via the backplane
GBCP BAM→AMP→GBCP
bus of the CPM subrack
CDP shares the same CPM module with AMP, so its program can be loaded from AMP via the
CDP BAM→AMP →GBCP →CDP (Program)
backplane bus of the CPM subrack
BAM→CDP (Data) CDP data can be directly loaded from BAM via the network cable and the LAN Switch
CCM GBAC BAM→AMP→GBAC GBAC can be loaded from AMP via the HDLC signal cable between CPM and CCM modules
The GNCC board in the CNET subrack can be loaded from the AMP board in the CPM subrack
CNET GNCC BAM→AMP →CCM →GNCC
via the HDLC signal cable of CCM
The GQSI board in the LIM subrack can be loaded from the AMP in the CPM subrack via the
LIM GQSI BAM→AMP →CCM →→GQSI
HDLC signal cable of CCM
GE16/GSTU/GE BAM→AMP →CCM →GQSI

GE16/GSTU/GECP/GECS can be loaded from GQSI via the backplane bus of the local subrack
CP/GECS →GE16/GSTU/GECP/GECS
GMHI BAM→AMP →CCM →GQSI →GMHI GMHI can be loaded from GQSI via the backplane bus of the local subrack
SPM GSPC BAM→GSPC GSPC can be loaded from BAM via the network cable
GVDP BAM→AMP→CCM→GBCC→GVDP GVDP can be loaded from GBCC via the backplane bus in the subrack
6-8
Subrack
Board name Loading path Description
name
The GBCC in the SPM subrack can be loaded from the AMP in the CPM subrack via the HDLC
GBCC BAM→AMP →CCM →GBCC
signal cable of CCM
GCPC BAM→AMP →CCM →GBCC →GCPC GCPC can be loaded from GBCC via the backplane bus of the local subrack
BAM→AMP →CCM →GQSI →GMHI

SRM GSPT/GSRC GSPT/GSRC can be loaded via the 8Mbit/sHW cable on the GMHI in the internal LIM subrack
→GSPT/GSRC
6-9
6.2 Loading Preparations
I. Preparations
Make the following preparations before the system power-on loading:

1) Check the installation of system hardware.
Specially check whether the physical connections on the loading paths are
correct.
2) Make sure that all boards are in position, but the power is not switched on.
Check against the version matching table whether the software version and
hardware version are correct. Set the DIP switches of all boards correctly.
3) Make sure that the BAM software is installed and can work normally.
See "Chapter 2 Installation of BAM Server Software" of this manual for details of
checking the BAM software.
4) Generate data loading files like "db_?.dat" ("?" stands for corresponding module
No.).
You may use the script files upon deployment to generate data loading files:
z Use the command LOF: ; to switch the Client to the off-line status;
z Use the command SET FMT: STS=off; to turn off the format conversion switch.
z Use the command SET CWSON: SWT=OFF; to turn off the alarm output switch.
z Use the batch processing command to run the script files provided by Huawei
Engineering Design Department.
z After running, use the command SET FMT: STS=ON; to turn on the format
conversion switch.
z Use the format conversion command FMT; to generate the data loading file
"db_?.dat", then convert the format of all data into the data file.
z Use the command LON; to switch the Client to the on-line status.
z You can also configure data in the off-line status. Perform format conversion
after configuration.
The formatted data and the program to be loaded is stored in the directory d:\
CMSC\hostdata of the BAM.
II. Input MML set and store corresponding output results
Prior to inputting the MML set, you had better select the operations [Start saving
command] and [Start saving report] in the MSC Client system so as to save the input
MML set and the corresponding output results.
Figure 6-3 shows the main interface of the MSC Client system.
6-10
Figure 6-3 Executing MML batch command
If you select [Operation/Save Input Command], the system can automatically save
the successfully executed MML commands on the real-time basis so that they can be
checked or edited into data script. The saved file is named CMD-yymmddhhmm.TXT.
For instance, CMD-0204151137.TXT is a file starting to save successfully executed
MML set at 11:37 on April 15, 2002.
If you select [Start/End Saving Report], the system can automatically save the
execution results of the MML commands. The file is named RPT-Office
Name–Maintenance-yymmddhhmmss.txt, for example,
rpt–606–Maintenance-020415115438.txt.
6.3 Loading Procedures
Upon deployment, load programs and data subrack by subrack so as to locate

causes for loading problems. The following are the basic procedures:
1) Switch on power for the clock subrack (CKM subrack).
2) Switch on power for No.0 subrack (CCM+CKM) and No.1 subrack (CPM), and
the system will automatically start loading the AMP. Then load the boards in
these subracks:
z When the AMP gets running normally, click the Reset button of the GBAC to
reload the two GBACs.
z When the AMP gets running normally, click the Reset button of the GBCP to
reload the two GBCPs.
6-11
z When the GBCPs get running normally, click the Reset button of the CDP to
reload all the CDPs.
z Check the running of the GBCPs until it gets normal.
3) Switch on power for No.2 and No.3 subracks (CNET). After loading, check
whether the boards can run normally in the subracks.
4) Switch on power for subracks from No.4 to No.17 (LIM subracks) one by one.
z Power on the internal LIM subracks (with GMHI boards) first, then power on the
external LIM subracks.
z After loading, check whether the boards in each subrack are in normal status. If
one of the LIM subracks cannot be normally loaded, try to load only half subrack
of service interface boards each time.
5) Power on the subracks from No.18 to No.19 (SRM subracks) one by one. After
loading, check whether the boards in each subrack are in normal status.
6) After loading the subracks from No.20 to No.29 (SPM subracks), check whether
the boards in each subrack are in the normal status.
7) After loading, check the board versions according to the version matching table.
If a board software version is found inconsistent with the software version to be
loaded, confirm that the status of the soft loading switch of this board is program
and data unusable, and then reset this board so that it can be re-loaded.
8) Perform CRC check on the board (AMP, CDP and GSPC) data. If the CRC
check on a board cannot succeed, reset this board so that it can be re-loaded.
During the above steps, if the loading of a subrack gets abnormal, switch off the
power of this subrack first. After settling the problem, resume the power-on loading of
the subrack.
Caution:
Carefully check software versions of all CDPs in the CPM subrack and make sure they are correct.
The boards of the CPM subrack can be loaded one by one in the sequence of AMP →GBCP →CDP.
6.4 Loading Methods of Voice Files
The voice files of the MSC should be loaded to the GSPT separately. Before the
loading, the corresponding grammar analysis module should be loaded. Particularly,
the English grammar analysis module must be loaded, otherwise SPD cannot work
normally.
6-12
Caution:
Perform voice loading during the low-traffic hours at night if possible.

Voices with the same code can be directly overwritten without being deleted first.
The global intelligent voice packet contains the service tone but not the basic tone. The GSPT cannot be
formatted no matter where it is loaded, but be overwritten directly.
Other localized voice files may be loaded during voice loading, please contact Huawei technical support
engineers or call Huawei Customer Service Center (CSC) for confirmation.
6.4.1 Steps for Initial Loading of Voice Files
1) Execute the command FMT SPDMEM to format the SPD board. For example,
FMT SPDMEM: MN=0, FN=18, SN=4.
2) Load English parse module to make the SPD board work normally. For example,
copy the file Voice/Grammar/ fffffafb.002 to the root directory “voice”, and
execute the command LOD SPDVOICE: MN=0, FN=18, SN=4, LT=SINGLE,
FNM="fffffafb.002 (It means to load the file fffffafb.002 to the SPD board in slot
No.4 of subrack No.18 in single loading mode).
3) Select other parse modules for loading according to the language used in local
area. For example, copy the Chinese parse module file fffffafa.002 to the root
directory of voice, and execute the command LOD SPDVOICE: MN=0, FN=18,
SN=4, LT=SINGLE, FNM="fffffafa.002".
4) Load the English voice file under the directory voicve\600 in batch mode.
Execute the command LOD SPDVOICE: MN=0, FN=18, SN=4, LT=BATCH,
SPN="600".
5) Create 3 folders under the directory “voice”, and copy the English voice files of
intelligent service under the directories of English\fph, English\ppc, and
English\vpn respectively to the above 3 new folders. Then load the voice files in
the new folders in batch mode.
6) If local language is English, skip to step 8.
7) If local language is not English, load the local voice files under the directory of
voicve\800 in batch mode by executing the command LOD SPDVOICE: MN=0,
FN=18, SN=4, LT=BATCH, , SPN="800".
8) Start loading after resetting the SPD board. You can observe the loading
processing until the loading is complete by running the program exchange.
9) Skip to step 1 to load the next board if multiple GSPD and GSPT boards are to
be loaded.
6-13
6.4.2 Processing of Voice Files during System Upgrade
The original voice files under the directory “voice” will be overwritten by new ones
after system upgrade. At the same time, they are backed up to the system installation
path. For example, they are saved under the directory
D:\CMSC\hostdata_10_28_2003\voice created by the system automatically.
6.5 Troubleshooting
6.5.1 Basic Methods
When handling a loading problem, be sure to check the board indicator status as well
as the display information and alarm information in the Exchange window on the BAM
Server. Useful clues for troubleshooting might be found.
If any loading problem occurs, check the following aspects:

1) Check whether the loading path is correct. Check whether the physical
connections (including the network cable, HDLC signal cable, HW cable, optical
fibers) are normal and the boards on the loading path are in the normal status.
The loading paths of the main boards are described in Table 6-2.
2) Check whether the DIP switches on the board and the backplane is correct.
3) Check whether the data configuration is correct. The configuration error of some
key data may lead to loading failure.
4) Check whether the loading files in the BAM are complete.
5) Check the software parameters, such as the max number of tuples, etc.
6) Check the system clock. If the system clock goes wrong, it may mess the board
logical signals and cause unpredictable problems. Make sure to power on the
BAM clock first prior to software loading.
7) If the loading path is normal, and both the data configuration and the DIP switch
setting are correct, replace the board. If the loading is still abnormal, some
problems might exist in the slot.
6.5.2 Common Loading Problems
The following are some loading problems and the corresponding solutions.
I. AMP, CDP or GSPC loading fails
The programs and data of both AMP and GSPC are loaded directly from the BAM.
The CDP program is loaded via AMP from the BAM, while the CDP data is loaded
directly from the BAM.
6-14
Normally faults on these boards are caused by the communication interruption

between the BAM and AMP, CDP and GSPC. In this case, alarms may be generated
for interrupted communication link between the GCPCs and background, interrupted
communication between GSPC and BAM, and so on. Besides, you cannot run the
command PING 172.20.X.Y (X: subrack No. of the board, Y: slot No. of the board) on
the BAM.
When such circumstances occur, check the subrack backplane of the board to see
whether the DIP switch settings for the subrack number are correct and whether the
network cables are in normal condition.
Besides, the configuration error of some key data may also lead to unsuccessful
board loading.
II. GQSI or GBCC loading fails
GQSIs are essential parts of the LIM subrack. The loading failure of these boards will
result in loading failure of the whole subrack.
Programs and data are loaded by the AMP to the GQSI boards via the CCM. When
loading fails, check whether the CCM configuration, HDLC signal cable connections,
and backplane DIP switch settings are correct.
In some cases, other hardware configuration errors in the GQSI board may also
cause loading failure.
GBCCs and QSIs may have the similar cases.
III. GMHI can be loaded normally but the GSRC/GSPT loading fails
The GSRC/GSPTs are loaded by the GMHIs via four HDLC signaling timeslots of the
8Mbps HW cables.
When loading fails, check whether the GSRC/GSPT resource configuration, 8Mbps
HW cable connections, and backplane DIP switch settings are correct.
Note that the GSRC/GSPT DIP switches determine both the subrack number and the
slot number.
IV. CDP programs and data versions do not match
The loading paths for CDP programs and data are different. When the CPM subrack
is powered on and reset, CDP cannot start the program loading until the AMP and
GBCP are loaded. If it takes too long, CDP will automatically read the old program in
the Flash Memory, but the data is the new version loaded from the BAM. This causes
the inconsistency between the program and data versions.
The solution is to reset all CDP active/standby boards one by one.
6-15
HUAWEI M800 CDMA Mobile Switching Center Chapter 7 Upgrade of BAM Server Software
Chapter 7 Upgrade of BAM Server Software
This chapter describes the upgrading of BAM server software using tools and patches.
7.1 Ways to Upgrade the BAM Server Software
There are two ways to upgrade the BAM Server software:

z Using the setup/upgrade tool
The upgrade tools are provided in the installation software of the MSC, which can be
used to upgrade the software version of the BAM Server. After the upgrade of BAM,
you may load the upgraded software to the MSC (For terminal WS, the upgrade can be
finished by reinstalling the terminal software).
z Using the patch software
Maintenance personnel can load the software patch needed via the patch operational
interface of the maintenance console online. The patch can be used to restore the
corresponding host software without interrupting the normal service operation of the
system.
7.2 Upgrade by Using the Upgrade Tool
7.2.1 About the Upgrade Tool
I. Path
For the MSCs running online, smooth upgrade of the original software version is
required, thus a convenient and swift, safe and reliable upgrade tool is needed.
M800 CDMA MSC provides the terminal setup/upgrade tools. The upgrade tools and its
supporting files are stored in the Upgrade directory of the software setup CD of the
MSC. The installation program will invoke the upgrade tool and supporting files in this
directory when upgrade is selected for the installation.
The upgrade tool is correspondent to a certain version of host software. By default, this
tool can upgrade any earlier version to the version represented by it.
7-1
Caution:
Make clear the version represented by the upgrade tool to avoid upgrade error or failure.
II. Function
The upgrade tools are mainly used to upgrade the software version of the BAM Server.
To complete the upgrade of the MSC, loading of the MSC should be performed after
upgrade of the BAM Server has finished.
The upgrade of the BAM Server mainly involves the upgrade of the data stored in it,
including the upgrade of BAM database, BAM applications and other data and host
programs and host data.
z For the BAM applications and data, host program and data, the upgrade can be
completed by overwriting the old files with the files of the new version.
z For the BAM database, the differences between the versions include additions
and deletions of tables as well as fields in the tables, and adjustment of the field
value. It is required that the original data should be kept after the upgrade.
The complex part of the upgrade is that of the BAM database.
III. Error tolerance
The upgrade tools supports fallback to the original BAM environment quickly and
correctly in case of upgrade error.
Note:
The original BAM status can be restored automatically by the current upgrade tools in case of upgrade
failure of the database. However, the auto-recovery cannot be performed in the case that the upgrade of
the database is successful while that of other parts (including terminal applications, data and host
programs) fails. Therefore, backup is necessary before the upgrade so that manual recovery can be
performed in the case of the upgrade failure.
To ensure safety, the following backups should be performed before the upgrade:
z Back up the BAM database and the registry.
z Manually back up the directory D:\CMSC in which the BAM applications and the
loading data are located. In the case that the upgrade fails, recovery can be made
7-2
by using the backup directories to overwrite the directories with the same names in
the installation path.
IV. Application environment
To guarantee the normal operation, the upgrade software is required to run in the BAM
Server.
7.2.2 Upgrade Procedures
The common procedures of using the upgrade tool to perform the software upgrade are
shown as follows:
I. Close BAMService and Smirror and modify their startup type
1) Close BAMService and Smirror

z Click [Start/Settings/Control panel].
z Double click [Service] in the [Control Panel].
z The [Service Panel] pops up, as shown in Figure 7-1.
z Select [BAMService] service and click <Stop>.
z In the dialog box as shown in Figure 7-2, click <Yes> to close BAMService service.
z Repeat the operations above to close Smirror service.
Figure 7-1 Service Panel
Figure 7-2 Closing BAMService
7-3
2) Modify startup type of BAMService and Smirror

z Click <Start> in the [Service Panel], set the startup type to "Manual" and click
<Enter> to exit, as shown in Figure 7-3.
Figure 7-3 Modifying the startup type of BAMService
z Repeat the operations above to close Smirror service.

3) Close [Service Panel]
Click the <Close> button in the service panel to exit the service panel.
II. Back up relevant programs and data
1) Backup the BAM database and the registry.

There are two ways to back up the BAM database and the information of the
registry: manual backup and auto-backup. It is recommended that the backup be
made in both the two ways.
z Manual backup: Run the registry editor program Regedit.exe and select the
registry key of HKEY_LOCAL_ MACHINE\SOFTWARE\Huawei\CMSC to
export registry files.
z Automatic backup: Carry out the command BKP DB at the MmlWS to backup
the BAM database and the information of the registry.
2) Back up BAM application and loading data
Backup the directory D:\CMSC which stores the BAM applications and the loading
data, and then copy the directory to another path.
7-4
III. Close BAM program and all connections with the database
1) Unplug the network cable between BAM and LAN Switch.

2) Exit BAM Manager.
z On closing the BAMService service, all programs running on the BAM should be
closed. Double click the icon in the lower right corner of the control bar.
z Click <Exit> in the menu bar, and then click <Yes> in the dialog box as shown in
Figure 7-4.
Figure 7-4 Exiting BAMManager
3) Exit BAM gateway

z Click BAM Terminal Communication Gateway in the desktop task bar and the
interface of BAM communication gateway is popped up.
z Click <Sign out> in the upper right corner of the [BAM Communication Gateway],
and then click <Yes> in the <Exit> dialog box to exit, as shown in Figure 7-5.
7-5
Figure 7-5 Exiting BAM gateway
IV. Start the setup/upgrade tool to perform upgrade
1) Start the upgrade tool.

z Double click the file Setup.exe in the setup CD to run the setup/upgrade tool.
z Select [Update M800 MSC Server Program], and click <Next> to start upgrading,
as shown in Figure 7-6.
Figure 7-6 Selecting the upgrade mode
2) Upgrade the database.

The setup/upgrade tool will copy the latest database files automatically.
7-6
Caution:
Do NOT click <Cancel> now, otherwise BAM database may get lost.
After copying the database files, the setup/upgrade tool will upgrade the BAM
database automatically. During the upgrade of the BAM database, an operational
status bar indicating [Updating tools is working...] will be shown.
This means the setup/upgrade tool is upgrading the BAM database.

3) Upgrade terminal applications, host program and host loading data
The setup/upgrade tool will continue to upgrade the terminal applications and data
as well as the host programs and host loading files.
First, the programs and each application of the original environment are backed up
automatically. Next, the terminal applications and data are updated. Finally, the
system information will be updated.
V. Restart BAM and open BAMService and BAM program
1) Click [Yes, I want to restart my computer now.] and then click <Finish> to restart
the BAM Server.
2) After BAM is restarted, click [Start/Settins/Control Panel/Service] and check
whether the service status of BAM Service has become "activated" and whether
the startup type has been set as "Auto", as shown in Figure 7-1.
3) If BAM Service has not been activated, select the BAM Service, and click <Start>
to activate the service. And if the startup type has not been set as "Auto", click
<Start> to set it.
VI. Verity the upgrade
Input the command DSP DEXVER in MmlWS after the completion of upgrade to check
the information of the version.
If the information of the version is correct, it means that the upgrade is successful.
VII. Format the database
Input the command FMT in MmlWS to format the database.
The maximum number of tuples may be modified during the upgrade of some versions.
If it is too small, the formatting may fail. In that case, please contact the technical
support personnel of Huawei to modify the maximum number of tuples, and then
conduct the formatting.
7-7
By now, the upgrading of BAM is completed. The network cable between BAM and the
switching equipment that has been disconnected should be resumed after the upgrade,
and loading should be performed to the host as well.
7.2.3 Possible Problems in the Upgrade
The problems that may occur during the process of upgrade are shown below:
z When the setup/upgrade tool is used, on selecting the upgrade mode [Update
M800 MSC Server Program] and clicking <Next>, a dialog box [Database
'BAMOldBackup' already existed! Please detach it before updating BAM.] will pop
up.
The cause is that upgrade has been made in the BAM. In this case, exit the
program, and get confirmation of relevant personnel before deleting the
BAMOldBackup database.
z A dialog box pops up when the setup/upgrade tool is performing the upgrade to
the BAM database.
In this case, please exit the upgrade and contact Huawei technical support
personnel immediately.
z A dialog box pops up when the system data is being updated.
In this case, continue with the upgrade, and contact Huawei technical support
personnel when the upgrade is finished.
7.3 Upgrade by Using the Patch Software
7.3.1 About the Patch System
I. Function
Maintenance personnel can load the software patch via the patch operational interface
of the maintenance console online. The patch can be used to restore the corresponding
host software without interrupting the normal operation of the system.
Caution:
Online software patching is a critical operation, which may directly affect the program running of the host
software. Thus, be cautious when using the patch.
7-8
II. Basic features
The online patch is delivered to the customers in the format of file. For the large patches,
the compressed package file format is used.
Note:
The design of basic version plus patch is adopted for the patch, that is, there is a certain basic version for
all patches.
The patch of a certain host version cannot be used for other versions.
The patch files are named as follows: cc08pat.board name or module name (E.g. ncc,
bsm and spc) while the description files of the patch information and patch description
files are named in the following way: README.TXT, *** Description.TXT and
PATCH.LST.
Besides the patch files, the corresponding description file of the patch is provided as
well. Detailed information of each patch, including the operational procedures,
description of the problem solving and the cautions, is described in it.
Through executing commands such as load, activate, fallback, run, delete and
query with reference to operational procedures in the description file, you can load or
delete the software patches online in the maintenance management console.
The boards that can be patched online are: GSPC, GNCC, AMP, CDP, etc. Each board
has its own patch.
The patches for the BAM Server and the Client are not online patches. To patch BAM
Server and Client software, replacement of some programs instead of command
operations are needed.
Some of the special patches (e.g. static patch) need loading.
7.3.2 Status of the Patch System and Operations
I. Status change of the patch
There are four kinds of status for the patch: IDLE, DEACTIVE, ACTIVE and RUN.
z IDLE: It means that the patch does not exist in the memory.
z DEACTIVE: The patch has been loaded, but is not activated. The patch code is
not executed.
z The patch has been activated and the patch code is running. This is a trial status,
and the Fallback command can be used to return to the DEACTIVE status. If the
7-9
host resets, the patch can load automatically after the reset, but it will change into
DEACTIVE status after loading.
z RUN: After the patch in the ACTIVE status being written into FLASH, the patch
begins running. Fallback can not be performed in this status and what can be done
is to delete the patch. Furthermore, if the host resets, the patch will be loaded
automatically and resume the RUN status after the reset.
The change of the status is shown in Figure 7-7.
Load
IDLE DEACTIVE
Delete
Delete Activate Fallback

Delete
Run
RUN ACTIVE
Figure 7-7 Status change of the patch
Note:
The ACTIVE status is a temporary status. The patch in this status is in the trial run. If the trial run of the
system goes on normally for a certain period, it should be changed to the RUN status.
The RUN status is the usual running status of the patch. When the system restarts, only the patches in the
RUN status are restored. Because the ACTIVE status is a temporary status, patches in this status need
not be restored.
II. Online loading of the patch
Loading should be performed to the patch in the following two cases:

z Loading a new patch.
z Restoring the patch that has been removed by the system.
The Service Maintenance System provides the command to load the patch, but this
command requires the authority of the administrator.
To load a patch,
z In the command line window of the Service Maintenance System, enter the
command LOD PATCH and select the correct board type and module No. Then
execute the command.
7-10
The system provides the batch operation function for common patches. If the input
patch number is N, the loading of the patches from 0~N will be performed
simultaneously. The system will load all the patches to the host if the patch number has
not been input.
The patches will be in the DEACTIVE status after they are loaded to the host.
When running the loading command, two cases may occur: 1) If the original patches
with the same numbers are in the IDLE status or DEACTIVE status in the system, the
original patches will be overwritten; 2) If the original patches with the same numbers in
the system are in the ACTIVE status or RUN status, some of the newly-loaded patches
will be discarded.
To achieve normal patch loading, the standby boards should be in the normal backup
status.
After patch loading, the consistency of patches in the active and standby boards should
be checked. If the patches are inconsistent, the level-four reset should be conducted to
the standby board. The standby board will reload the patch to achieve the consistency
of patch status between the active board and standby board.
III. Operational commands of the online patch
The patch operations include: load, activate, fallback, confirm, delete as well as query
patch status and patch files, etc.
Load (LOD PATCH: TP= board type): Loading patch files means to load the code of the
patch to the patch area of each board. The boards that can be patched online are:
GSPC, GCPC, GNCC, AMP and CDP. Each board has its own patch.
Activate (ACT PATCH: TP= board type). For common patch, inputting patch number N
means to activate all the patches from 0~N. While for special patch, it means to activate
the patch with the number N.
If the patch is in the IDLE status, which means that loading has not been performed, the
host will return an error message.
When activating a group of common patches, if the activation of one patch fails, the
number of this patch will be returned. However, the patches before this one have
already been activated.
If a patch is in ACTIVE or RUN status, which means that the patch has been activated,
the host will skip this patch. However, for the special patch, a piece of information
indicating that the patch has been activated will be returned.
7-11
Note:
The release of the patch for the MSC is divided into two kinds: common online patches and special
patches.
The auto-coverage mode is adopted for the common online patch, and the new patches completely
include the old ones. You can use the software parameters to control whether some of the patches should
function (e.g. whether the out-group prefix will be shown in the intra-group calls can be set by adding some
software parameters). The service will not be affected during the loading of common patch, so patch
loading can be performed when the conditions allow it.
Special patches are created for special purposes, which are usually the static loading patches (namely,
the newly-loaded program) or terminal patches used for special purpose. The patches are independent of
each other, and the loading will be performed only once when needed.
The common online patch is established on the basis of static patch. To load the common patch into the
dynamic patch after the publication of the static patch, it is required that the static patch be loaded once.
Deactivate (DEA PATCH: TP=board type): The deactivating operation is also called
fallback operation. For the common patches, inputting patch number N means to
perform fallback to all the activated common patches behind N. While for special
patches, this means to perform fallback to the Nth activated special patch.
If an error is found after the patch has been activated, this command can be used to
perform fallback to the patch.
Confirm (CFM PATCH: TP=board type). This operation writes patches in the ACTIVE
status into Flash memory. After that, the status of patches will change from ACTIVE to
RUN and they will be auto-recovered after the restarting caused by the power-off of the
system. Patches in status other than RUN will be discarded after the power-off of the
system.
Delete (RMV PATCH: TP=board type). This operation deletes the patch of the
designated module. The status of patch will become IDEL when this operation.
For the common patches, inputting N for the patch number means to delete the
common patch of that number from Flash memory, and this common patch must be the
maximum common patch. However, for special patches, this means to delete the No. N
special patch in RUN status from Flash memory.
The Fallback operation cannot be performed when the patch is in RUN status. If errors
are found in the patch, what can be done is to delete the patch. The deletion of the
patch may greatly affect the function of the system. Thus, deletion is not allowed after
the confirmation of the system administrator.
7-12
Query the patch files (LST PATCH: TP=board type). This operation queries the static
information of the patch files (in BAM database), which includes the number, patch
applicable version, as well as the patch list.
Query the patch status (DSP PATCH: TP=board type). This operation queries the
status of the patches of a certain type in the host of the specified module.
When any non-query operation is performed to the patch, use this command to check
whether the status of the patch is conforming to the expected result or not.
7.3.3 Patching the Host
I. Obtain and copy the correct patch files
The online patch of the board is based on the software version, and there is strict
matching relationship between them. It is required that they should be used together.
Because the patch files of a certain version cannot be used for another version, you
should select the patch of the correct version.
To obtain the information of the applicable version of the patch, please read carefully
the description file released with the patch.
Multiple software modifications may exist in a patch file. As long as they are applicable
to the same version, the newly-released patch files are all new patches added on the
basis of the original patch, if not otherwise specified. That is, the subsequent patch files
not only solve the new problems, but also the old problems.
The directory for storing the patch files should be the same as the corresponding
directory of the host software version. The default directory is D:\CMSC\hostdata on
BAM. The corresponding patch files and the symbol files should be copied to this
directory. The description file of the patch should also be copied for checking when
error occurs.
It is recommended that the original patch files be saved in other names for the sake of
restoration.
z SPM patch file: Cc08pat.spc
z SPM symbol file: Cc08sym.spc
z CDP patch file: cc08pat.cdp
z GNCC patch file: cc08pat.amp
z CDP patch file: cc08pat.ncc
After copying the files, you should use the LST PATCH command to check the
applicable version and relevant information of the patch again.
II. Load the patch
1) Ensure that the backup switches of each module have been turned on.
7-13
Because the patches of the active and standby boards must be consistent, backup
should be able to be performed to the GSPC board during installation and
operation.
2) Use the command DSP PATCH to check whether patches exist in SPM or not.
Both of the active and the standby boards should be queried to check whether the
statuses of them are consistent. If the status of active/standby board is
inconsistent, the loading should be performed after the status of the boards
resume consistent. When any non-query operation is performed to the patch, you
should check the status of the patch by using this command.
3) Verify validity of the patch.
When the host version is inapplicable:
z Check whether the applicable version of the patch files and that of the
running host software are not consistent, in which case you can change the
patch files.
z Check whether some of the patches without formal publication exist in the
original board, in which case you can delete all the original files and load the
patch again.
4) Use the command LOD PATCH to load the patch.
Because the newly-add patch includes the original patches, thus loading can be
performed by using the command no matter whether patches exist in SPM or not.
Both of the board type and module number should be selected during the loading.
The board type for the SPM patch is GSPC. If the module number is not inputted,
this means that patch loading will be performed to all the boards of the same type.
5) On the completion of the loading, check whether all the patches in the patch files
have been loaded, and whether the status of active/standby board is consistent by
using DSP PATCH.
The newly-add patches should in the DEACTIVE status.
Note:
When loading is performed to all the modules simultaneously, loading failure may occur in certain modules.
Then individual loading can be performed to these modules.
Patches are DEACTIVE after the loading. Thus the operation of the system will not be affected by the
loaded patches because they are not running.
LST PATCH is used to check whether patch files and information of the files exist in BAM or not while DSP
PATCH is used to check the information of the patch in the patch area of the board memory. Thus the two
should be distinguished.
7-14
III. Activate the patch
Activation should be performed to the loaded patches to make them run and take effect.
After confirming that the statuses of active and standby boards are consistent, use the
ACT PATCH command to activate the patch.
The corresponding board type, module number and patch number should be selected
during the activation. By default, all the patches for all the modules are activated. When
this operation is completed, the patch will be in the ACTIVE status and will be running in
the original software.
Note to check whether the system is in normal operation. If the system is found to be
abnormal, you can perform fallback by using the DEA PATCH command to change the
status of the patch into DEACTIVE or delete it by using the RMV PATCH command.
If switchover and reset of the system occurs, the patch in ACTIVE status will fall back to
DEACTIVE status automatically.
Caution:
To ensure the normal running of the patch, the subsequent patch operation should not be performed after
4 to 5 minutes of normal operation of the system. During this period, attention should be paid to the running
status of the system and the patch.
When the patch is activated, the maximum patch ID will take effect. For example, if "4" is entered for Patch
ID, patches 1 to 4 will be activated.
The minimum patch ID will take effect during the fallback and deletion of the patch. For example, suppose
that there are six ACTIVE patches in a certain SPM. When "2" is entered for Patch ID, patches 2 to 6 will be
deleted while patch 1 remains. (4) Unless otherwise, specified, "All Patches" should be selected to activate,
fallback or delete the patch.
IV. Confirm patch operation
After the patch is activated, on confirming that the patch statuses of the active and
standby boards are consistent and the system is in normal operation, the CFM PATCH
command can be used to confirm the running of the patch (the selection of the
parameter is the same with that in the operation to ACTIVE patch). Then the patch will
move into the RUN status.
By now, the patching operations are completed.
7-15
Caution:
The functions implemented by the patches in the RUN status and in the ACTIVE status are completely the
same. What makes different is that the RUN patch can resume RUN status during the switchover or reset
of the board, while the ACTIVE patch will change to DEACTIVE status, and will not run any more.
To prevent accidents, the patch should be run for a period of time (4 to 5 minutes) before the confirmation
of the operation.
After the confirmation of the operation, the only way to stop the RUN patch from running is to delete the
patch by using the RMV PATCH command.
When the command is inputted in confirming the patch operation, the maximum ID will take effect just as in
the case of activating the patch.
The original patch will not take effect when the version is changed.
V. Handling of exceptions
Serious problems may be caused in the following cases:

z The patch is deleted when the patch statuses of the active and standby boards are
inconsistent.
z When a certain module resets or performs switchover, during loading of the patch,
it will be detected that the patch file under the loading directory (d:\CMSC\data)
has been deleted or changed to another patch file which is not applicable. At this
time, the board will continuously try to restore the status of the patch, which may
affect the normal running of the system.
When the above cases occur, try to acquire the patch version matching the host version,
and save it in the loading directory. At the same time, contact the technical support
personnel of Huawei to handle the problems together.
7.3.4 Patching the Terminal System
For the patches of the terminal system (including the BAM Server and Client), the
overwrite mode is adopted, that is, new patches will overwrite the old patches, and
fallback is unavailable.
If problems of the data or program running occur after the patching, they can be solved
only by restoring the original data and programs. Therefore, backup is needed for the
data before patching of the terminal system and a set of programs should be reserved
as well.
Please follow the following descriptions when patching the terminal system.
7-16
I. Patching the BAM Server
The patches of patch_server and patch_client should be loaded to the BAM Server.
Moreover, patch_server should be loaded before patch_client.
The operation procedures of patching the BAM Server are as follows:

1) Close all the processes (applications) from SecurityManager in the BAM Server,
and close all the Clients connecting to the server as well.
2) Back up the directories D:\CMSC of the BAM.
3) Create a directory (e.g. Patch_Server) under the installation path of the BAM
software in the BAM Server, and copy all the files under the path of
\Setup\Patch_Server of the setup CD to the new directory.
4) Execute the command CD to create a directory (e.g. Patch_Server) in DOS mode
and enter the patch of it.
5) Execute the batch processing command: patch destination path, parameter 2,
source path.
In this command, the destination path is the BAM installation path; unless
otherwise specified, the parameter 2 can be specified at will, and the source path
is that of the new directory.
For example: Execute patch D:\CMSC d:\ D:\CMSC\Patch_Server.
Caution:
When the loading of the patches has finished, the file noutput.txt will be created under the source path (e.g.
D:\CMSC\Patch_Server). You can open the file to check whether there is any error message. If there is,
please contact the technical support personnel of Huawei.
6) Restart the program that has been closed, and the loading of the server will be
completed.
If some special patches have modified the system table, you should use the FMT
command after the above operations, and load the host again. Otherwise, some of the
functions cannot be implemented, and errors may occur when CRC is performed. .
II. Patching the Client
Only the patch patch_client needs to be loaded on the Client.
The operation procedures are as follows:

1) Close all the Client programs on the Client.
2) Back up the configuration file (D:\CMSC\macro.ini) for the Client programs.
7-17
3) In the installation path of each Client (generally, it is D:\CMSC), create a new

directory (e.g. Patch_Client) and copy all the files in \Setup\Patch_Client into the
new directory.
4) Execute the batch processing command in the path of the newly-created directory
in DOS: patch destination path parameter 2 source path.
In this command, the destination path is the installation path of Client. Parameter 2
can be specified at will unless otherwise specified. The source path is the path of
the newly-created directory.
For example: Execute patch D:\CMSC d:\ D:\CMSC\Patch_Client.

5) Restart the Client program.
After the patch loading of the server and the Client has finished, restart and check
the running status of the Client and the Server.
If any problem is found after loading of the patch, the status before the operation of
the patch should be restored in time.
For the Client, only the file D:\CMSC\macro.ini needs to be replaced with the
original file.
For the BAM Server, the D:\CMSC\data directory needs to be replaced with the
backup data firstly. If loading is performed in the operations of the patch, reloading
is required after restoring of the BAM data.
7.3.5 Precautions
Please refer to the description of patch modification and patch description during
installation of the patch, and be care of the following items:
1) The description files should be checked for each board to see whether the patch is
complete, or whether the status is normal after loading.
2) Fallback cannot be performed to the patches of BAM. Therefore, backup must be
performed to the database as well as the CMSC directory before the installation of
the patch.
If the installation of the patch fails, you can overwrite the original CMSC directory
with the backup directory, and then restore the database with backup data.
Whether the installation of BAM patch is successful or not can be judged by the
following methods:
z Check whether the file output.txt is included in the patch files or not. If so,
back up the original file output.txt in the patch (it requires manual operation),
and compare the size of it with that of the new one generated after the patch
is installed. Meanwhile, check whether there is error message in the
output.txt in D:\CMSC\patch_server after the installation of the patch. If the
7-18
installation succeeds, no error message should occur in this file and the file
size should be the same as the backup one.
z Check the prompt information in the DOS interface. If error prompt occurs
during the installation, it means the installation has not completed
successfully.
3) The patch status of the standby GSPC remains consistent with the host patches
via the backup function. If the backup switch of the standby board is turned off,
after data is loaded, the patch of the standby board should be loaded again
through the host and be synchronized with the host so as to keep it in the same
status with the host patch.
The standby board will send a request to the host for restoring the patch status, but
the host can not achieve the synchronization of the status of the active/standby
patches through the backup function. The patch of the standby board will keep
trying to restore, and the message "Restoring…" will be displayed.
In this case, you can only use the debugging command to restore the GSPC board
to the unpatched status: STR SFTD: MN= (Module No.), PID="73", CTRL="1",
PM0="1", PM1="1".
Thus, for all types of GSPC, the patch must be uninstalled before reloading of the
data or programs, and be installed again after loading is completed. If the
programs of other AM boards are not changed, the patch can be kept. But the
patch must also be uninstalled first if the new programs are to be loaded.
4) Generally, the patches of the M800 CDMA MSC are independent of each other.
But some of the patches will affect the whole system, such as the clock patch,
which modifies the clock mode and involves BAM, AMP and SPM. When installing
this kind of patches, the relevant patches should take effect at the same time,
otherwise the system time will be affected.
7-19
Installation Manual - Software Installation Appendix A Installation of Operating System and
HUAWEI M800 CDMA Mobile Switching Center Database Software
Appendix A Installation of Operating System and

Database Software
A.1 Overview
Before the BAM software installation, corresponding operating system (OS) and
database software must be installed on the BAM Server. Normally, on-site installation
is not necessary since the installation has been completed prior to delivery.
A.1.1 Configurations
Currently the configurations of the operating system and the database of the BAM
Server are as follows:
z OS software: Windows 2000 Server+ Windows 2000 Service Pack 3
z Database software: Microsoft™ SQL Server 2000 + SQL Server 2000 Service
Pack 3
A.2 Installation Preparations
A.2.1 Preparing Setup CDs
The following setup CDs or installation programs are used in the installation of the
BAM Server software:
z Delivery-attached bootable CD: Dell OpenManage Server Assistant Bootable CD
Version 8.0
z Windows 2000 Server installation compact disk (CD) and patch CD.
z Microsoft SQL Server 2000 installation CD and patch CD
A.2.2 Checking Server Hardware Configuration
The recommended hardware configuration for the BAM Server is:

z Two or five hard disks
z Three or four network adapters
A-1
A.3 Installation of OS and Database Software
To install the OS and database software:

1) Set disk array and install Windows 2000 Server OS.
2) Install Windows 2000 Service Pack.
3) Set partitions of the hard disk of BAM server.
4) Configure network adapter.
5) Adjust system page file size and registry file size.
6) Install Internet Explorer 5.5.
7) Install SQL Server 2000 (standard version).
8) Install the SQL Server Service Pack.
A.3.1 Setting Disk Array and Installing Windows 2000 Server OS
Note:
z The following procedure is applicable to Dell™ 2650 server and its installation disk "OpenManage
Server Assistant (V8.0)". As the tool software of the server upgrades rapidly, the following operation
procedures are only for reference. During the actual installation, follow the manuals and guidebooks
delivered with the server.
z The following procedure is applicable to the case that two disks are set to RAID 1. If the server is
configured with five hard disks, the setting must be RAID 5. During the actual installation, please
follow the manuals and guidebooks delivered with the server.
1) Start the server, and insert DELL OpenManage Server Assistant (hereinafter
referred to as "DOSA") CD into the CD-ROM.
2) Select the language "English".
3) Click at the "Click here for Server Setup" on the homepage. On the window "Set
Date and Time", set date and time, and select proper time zone. Then click
<Continue>.
4) On the window "Configure or Skip RAID", check current RAID configuration.
z If correct, select the option "Skip RAID Configuration" and click <Continue>.
Then execute step 7.
z If incorrect, select the option "Configure RAID" and click <Continue>. Then
execute step 5.
5) On the window "Create Virtual Disk Express Wizard", set RAID level as RAID 1,
and click <Continue>.
6) Confirm virtual disk attributes are correct, and click <Continue>. A prompt "All
existing virtual disks on this controller will be deleted and all data will be lost" will
be displayed. Then click <Ok>.
A-2
7) On the window "Select Operating System to Install", select "Microsoft Windows

2000 Server" and click <Continue>.
8) Select "NTFS-NT File System" and select the default value 4096 as the boot
partition size. Then click <Continue>.
9) Adopt the default values for network adapter configuration, and click <Continue>.
10) On the window "Enter Configuration Information for: Microsoft Windows 2000
Server", configure the following options and click <Continue>.
z Language, organization, user name, computer name and installation directory:
Configure them according to actual application.
z Product ID: CD key of Microsoft Windows 2000 Server.
z License Type: Per server.
z Client License: 20
z Select "Join Workgroup". The workgroup name must be set according to actual
application.
z Adopt default values for all the rest options.
Note:
The username of the Windows 2000 operating system and the computer name of the BAM server are
both set to “BAM” before delivery. The organization name is set to Huawei and the keyboard language is
“English (U.S.A)”.
11) Confirm that "Operating System Installation Summary" is correct, and click
<Continue> to the window "Microsoft Windows Installation Wizard" will be
displayed.
12) The system starts to install Windows 2000 automatically. Insert Microsoft
Windows 2000 Server CD into CD-ROM when the system prompts "Invalid CD
inserted. Insert Microsoft Windows 2000 CD" during the installation procedure.
13) Take out the CD when the system restarts and enters Microsoft Windows 2000
server OS.
Note:
When you complete the installation of the operating system, the password of the administrator is null.
You can modify the administrator's password through the user management tool of the operating
system.
A-3
A.3.2 Installing Windows 2000 Service Pack
Insert Windows 2000 server patch CD into the CD-ROM. Then run the patch program
of Windows 2000 Service Pack and complete the installation adopting default
settings.
The version of the Windows 2000 Service Pack is SP3.
A.3.3 Setting Hard Disk Partitioning for BAM Server
I. Description of BAM hard disk partitioning
The BAM hard disk is divided into four logical partitions: all of which are formatted in
NTFS.
z Partition C is used to install the Windows 2000 Server.
z Partition D is used to install the SQL Server 2000, BAM programs, and BAM
databases.
z Partition E is used to store database log files.
z Partition F is used to store database backups.
The space of BAM disk partitions can be determined by the following rules:
z As the total space of the hard disk is 8G, the space of Partition C can be fixed as
4G; and Partition F must be no less than 2G. The space of each partition can be
determined according to the ratio D: E: F = 4: 2: 1.
z If the space of partition F is less than 2G according to the calculation result, set it
to be 2G and reduce the space of partition C accordingly.
z If the total capacity of a hard disk is less than 8G (such as for an emergency
workstation), you can combine Partitions E and F into one. That is, divide the
whole hard disk into three logical partitions C, D and E only. The contents to be
saved in Partitions C and D must remain unchanged while Partition E is used to
store log files and backups of the databases. The space of each logical partition
can be determined according to the ratio C: D: E = 1: 2: 1.
For example, suppose the BAM comes with two 36 GB hard disks, the total hard disk
space is 36 GB after they are configured as RAID1. Partition the logical disk as
follows:
1) Set the space of Partition C as 4 GB.
2) Divide the remaining 32 GB at the ratio of 4: 2: 1, and thus Partitions D, E and F
can be separately set to be 18GB, 9 GB and 5GB.
3) The result is: Partition C: 4G; Partition D: 18G; Partition E: 9G and Partition F:
5G.
A-4
Note:
Because the server reserves a hidden partition, and partitions the disk based on 1024 bytes as 1k, a
difference may occur between the calculated value and actual value.
II. Partitioning mode of hard disk
The detailed operation procedures are:

1) Click [Start] and select [Programs/Explorer/Computer Management/Disk
Management].
2) Right-click the icon CD-ROM to select "Modify Drive Name and Path (A)", click
<Edit> in the dialog box displayed and specify the drive label as G.
3) Right-click the disk to be partitioned to set the part to logical partition.
4) Right-click the logical partition to create Partitions D, E and F, and define the
size according to the ratio D: E: F = 4:2:1.
5) Format the three logical partitions D, E and F. Make sure to select NTFS for File
Type, "Unknown Capacity" for Capacity, "Default (4096 bytes)" for Distribution
Unit. Select "Fast Format".
6) Exit the disk explorer.
A.3.4 Configuring Three Network Adapters
I. Plan for 3 network adapters of BAM server
BAM server of new version is configured with three network adapters. Two (No.1,
No.2) are delivered along with BAM server and integrated on the main board of the
server. They are called integrated network adapters. Another one (No.3) is inserted in
the PCI extension slots. See Table A-1.
Table A-1 Setting 3 network adapters
No. Usage IP
1 Used for the communication between
Uses fixed IP:172.20.200.200
2 the BAM and the host.
Connects to external LAN Switch for the The IP assignment is determined by networking
3 communication between the BAM and mode in the customer's equipment room instead
external entities such as workstation. of the network segment 172.20.
A-5
Note:
There is no need to configure IP address for the two network adapters bound respectively. You only
need to configure IP address for the network adapter queue after the binding operation.
II. Binding BAM network adapters
The binding procedure is as follows:

1) Insert OpenManage Server Assistant CD into CD-ROM. Then select the server
type (PowerEdge2650) and the OS type (Windows 2000 Server).
2) Install the driver "Netwok/Badcom: NetXtreme Family of Adapters (Drivers) 6.6.
3) Run the Baspinst.EXE under the installation directory BCMServ.
4) Input a team name. Then select move Broadcom NetXtreme Ethernet Adapters
from the "Unassigned adapters" to "Team members". Click <OK>. See Figure
A-1.
Figure A-1 Binding network adapters
Note:
When you run the Baspinst.EXE for the first time, it will add an option "Broadcom Advanced Server
Programme Driver" in the shortcut menu of [Network Connection]. You can select the option to enter the
window for setting properties.
A-6
A.3.5 Configuring 4 Network Adapters
I. Plan for 4 network adapters of BAM server
BAM server of earlier version is configured with 4 network adapters. One (No.1) is
delivered along with BAM server and integrated on the main board of the server. It is
called integrated network adapter. The other three (No.2, 3 and 4) are inserted in the
PCI extension slots. See Figure A-2.
Table A-2 Setting 4 network adapters
No. Use IP
Connects the external LAN Switch for the The IP assignment is determined by
1 communication between BAM and external networking mode in the customer's
entities like workstation equipment room.
2 Use fixed IP:
Used for communication between BAM and host
3 172.20.200.200
4 Inhibited (IP not configured) No IP configured
In this way, if any of the 3 network adapters fail, the network adapter No.4 can be
used for replacement.
Caution:
z Network adapters of the DELL server are numbered from left to right.
z The IP address of the integrated network adapter cannot be set in the 172.20.xx.yy network segment,
as this segment is reserved for internal communication between the BAM server and the MSC.
z There is no need to configure IP address for the two network adapters bound respectively. You only
need to configure IP address for the network adapter queue after the binding operation.
z Do not set IP address for one of the Server Adapters, as it is to be reserved as a backup. The
access to this network adapter will be denied.
z If the IP address of this network adapter has been set by mistake, just delete it.eboot BAM server
and the BAM server will identify this network adapter automatically. Then leave its IP address blank.
II. Binding BAM network adapters
The binding procedures are as follows:
A-7
1) Insert the Open Manage Server Assistant CD, and install Intel: PRO Family of
Adapters (Driver) 5.4. Select the Intel PRO Set II component for installation, as
shown in Figure A-2.
Figure A-2 Install Intel PRO Set II component
2) After the Intel PRO Set II component is installed, select [Start/Settings/Control

Panel/Intel(R) PRO Set II]. The following window is displayed, as shown in
Figure A-3.
A-8
Figure A-3 Intel PRO Set II
3) From the navigation tree on the left of the interface, select the second network
adapter (that is, the first Server adapter), right-click to select [Add to
Team/Create New Team], as shown in Figure A-4.
Figure A-4 Network adapter binding (1)
4) On the binding wizard interface, select "Adapter Fault Tolerance" and click
<Next>.
A-9
5) On the warning prompt window for "Do not bind a bound network adapter", click
<Next>.
6) A dialog box for network adapters to be bound is displayed, as shown in Figure
A-5. Select the second and the third network adapters, and then click <Next>.
Figure A-5 Network adapter binding (3)
7) A dialog box with team configuration information is displayed, as shown in Figure

A-6. Confirm it and click <Complete>.
Figure A-6 Completed network adapter binding (4)
III. Activate standby network adapter
When the integrated network adapter fails, delete its parameter settings and configure
the standby network adapter with those settings. This will activate the standby
network adapter for external communication.
A-10
z If one of the two bound network adapters fails, just remove the faulty adapter
from the team and replace it with the standby network adapter.
z If both bound network adapters fail, remove both of them from the team and
activate the backup network adapter.
Note:
z For the detailed operation of network adpater, refer to relevant document.
z No matter which of the above ways is taken, replace the faulty network adapter with the backup
adapter and restore the "Three in service, one standby" status as soon as possible.
A.3.6 Adjusting System Page File Size and Registry File Size
To adjust system page file size and registry file size,

1) Click [Start] and select [Settings/Control Panel/System] to view the [Properties]
page.
2) In the virtual memory part, click <Change> and the [Virtual Memory] dialog box is
displayed, as shown in Figure A-7.
Figure A-7 Set virtual memory
A-11
3) Make sure that the "Maximum Size" is at least 1536 MB. If it is less than 1536
MB, click <Setting> to change the value to 1536 MB. Set the maximum registry
size to 64MB, and click <OK>.
A.3.7 Installing Internet Explorer 5.5
Find the installation directory for Internet Explorer 5.5 in Windows 2000 server patch
CD, and run IE5SETUP.EXE to start the installation and adopt default settings to
complete the installation.
A.3.8 Installing SQL Server 2000
I. Installation Preparations
The database used for BAM server software is the standard SQL Server 2000. Before
running SQL Server 2000 setup program, prepare the following items:
z Log in to the operating system as a user with the local management authority, or
assign proper authority to the user, and then log in to the operating system.
z Exit all services related to SQL Server, including all services based on ODBC.
z Exit the event viewer and the registry viewer (Regedit.exe or Regedt32.exe).
Note:
z Refer to the instructions in the corresponding window for the installation.
z More reference information is available in the complimentary CDs for SQL Server installation.
II. Installing SQL Server 2000
The installation procedure is as follows:

1) Start setup program
Run the Autorun.exe program in the SQL Server 2000 CD to install the SQL
Server 2000 components.
Or start the installation through the Autorun.exe program in the root directory of
the SQL Server 2000 CD.
2) Pre-installation selection
On the pre-installation selection interface, select "SQL Server 2000
Components".
3) Select installation components
A-12
On the selection window for the installation of SQL Server 2000 components,
select "Install Database Server".
4) Welcome interface
The window [Welcome] is displayed, as shown in Figure A-8.
Figure A-8 Welcomeof Microsoft SQL Server 2000
Click <Next> to continue.
Note:
Click <Cancel>, and the window [Exit Setup Program] is displayed. The user can select to exit program
setting or continue with program installation.
5) Enter computer name

On the window "Computer Name", enter the name of the computer in which the
user can create new SQL Server instances or modify existing SQL Server
instances.
Select the default option "Local Computer" and click <Next> to continue.
Note:
z During installation, click <Back> to return to the previous step.
z During installation, user can click <Help> to activate SQL Server setup help and get more help
information for installation.
A-13
6) Installation selection
The window "Installation Selection" is displayed, as shown in Figure A-9.
Figure A-9 Installation selection
Select "Create a new instance of SQL Server, or install Client Tools", then click
<Next> to continue.
7) Enter user information
On the window "User Information", enter user name and company name, and
click <Next> to continue.
8) Software License Agreement
The window "Software License Agreement" is displayed.
You must carefully read this Agreement and accept it. Then click <Yes> to
continue.
Note:
Click <No> and the window "Exit program setting" is displayed, in which user can select to exit program
setting or continue with program installation.
A-14
9) Enter CD-Key
On the window "CD-Key", enter correct CD-Key and click <Next>.
10) Installation definition
The window "Installation Definition" is displayed, as shown in Figure A-10.
Figure A-10 Installation selection
Select "Server and Client Tools", and click <Next>.

11) Enter instance name
On the window "Instance Name", select "Default" and click <Next>.
12) Select setup type
The window "Setup Type" is displayed, as shown in Figure A-11.
A-15
Figure A-11 Select setup type
Make the following settings:

z Type of setup: Custom
z Destination folder of program files: D:\Microft SQL Server
z Destination folder of data files: D:\Microft SQL Server
Click <Next>.
13) Select component
The window "Select Components" pops up, as shown in Figure A-12.
A-16
Figure A-12 Select components
To ensure the normal system operation, select the default configuration

information, and then click <Next> to continue.
14) Set services accounts
On the window "Services Accounts", select "Use the same account for each
service. Auto start SQL Server Service." Then select "Use the Local System
account" in the field [Service Settings].

15) Set authentication mode
On the window "Authentication Mode", select "Mixed Mode (Windows
Authentication and SQL Server Authentication)", and enter the password of the
"sa" account.
Note:
Keep the password of "sa" account for use during BAM software installation.
The password of "sa" account for SQL Server pre-installed in the BAM before delivery is null.
A-17
16) Set collation rule

On the window "Collation Settings", select the type of the collation rule indicator
as "Latin1_General" and select "Binary"
Caution:
Select the correct collation rule. Otherwise the BAM server software cannot run normally.
17) Set network libraries

The window "Network Libraries" is displayed, as shown in Figure A-13.
Figure A-13 Set network libraries
Select the default setting and click <Next> to continue.

18) Start copying files
On the window "Start Copying Files", confirm all information is correctly set.
Then click <Next> to start copying files.
A-18
19) Select the licensing mode.

The window "Choose Licensing Mode" is displayed, as shown in Figure A-14.
Figure A-14 Selecting licensing mode
On the [Choose Licensing Mode] dialog box, set the licensing mode to Per Seat
for 10 devices. Click <Continue>.
20) Copy files
The window for file copying progress is displayed.
The setup program creates a directory and start copying files. During file
copying, the setup program shows the overall progress, available disk space,
available memory, and the copying progress of individual files.
21) Installation completed
The window "Setup Complete" shows that the setup program has completed the
installation of SQL Server 2000 instances in the computer. Click <Finish> to
confirm the completion.
Restart the computer to end the whole installation process of SQL Server 2000.
A-19
A.3.9 Installing SQL Server 2000 Service Pack
Insert SQL Server 2000 patch CD into the CD-ROM. Then run the installation
program of SQL Server 2000 Service Pack and completes the installation according
to default settings.
The version of the SQL Server 2000 Service Pack is SP3.
A.3.10 Check Items for SQL Server 2000 Installation
I. Select start menu
The SQL Server 2000 setup program creates Microsoft SQL Server program groups
in the [Start/Programs/Microsoft SQL Server] menu, as shown in Figure A-15.
Figure A-15 Microsoft SQL Server 2000 program group
Activate the following items from the "Microsoft SQL Server" program group:
z Books Online
z Client Network Utility
z Enterprise Manager
z Import and Export Data
z Profiler
z Query Analyzer
z Server Network Utility
z Service Manager
A-20
II. Run the SQL Server 2000 service manager
When the server is started, the SQL Server 2000 service manager will automatically
start, and its running icon will be displayed, as shown in Figure A-16.
Figure A-16 Running icon of SQL Server 2000 service manager
Click this icon and the SQL Server Service Manager window is displayed, as shown
in Figure A-17. If the icon in the white circle on the left side of the window is a green
triangle, the running is normal and the installation is successful.
Figure A-17 SQL Server Service Manager
If a window is displayed as shown in Figure A-18, the icon inside the white circle is a
red block, the SQL Server Service Manager has stopped running. Click
<Start/Continue>, then the Manager will refresh the services. If the services cannot
be refreshed, the installation is not successful.
Figure A-18 SQL Server Service Manager stops running
A-21
Note:
If the installation of SQL Server 2000 fails, uninstall SQL Server 2000 and restart the computer, then
re-install it in compliance with the procedures described in this manual.
III. Confirm patch version
To confirm patch version:

1) Select [Start] and click [Programs/Microsoft SQL Server/Query Analyzer] to run
the SQL query analyzer.
2) In the SQL query analyzer, select [File/Connect] and the window [Connect to
SQL SERVER] is displayed, and fill "." in the text box behind [SQL SERVER],
which indicates that the local server is connected, as shown in Figure A-19.
Figure A-19 Connect to SQL Server
Note:
Activate the Query Analyzer. Select the computer name by default.
In the querying window of SQL Query Analyzer, enter the command select
@@version and press <F5> to run the SQL script. The version information is
contained in the output result, including patch content.
Note:
The use of SQL Query Analyzer is described in relevant product manuals.
A-22
A.3.11 Uninstalling SQL Server 2000 Database Software
I. Uninstall SQL Server 2000 database software in normal case
To uninstall SQL Server 2000 database software:

1) If the server is already installed with BAM application software, uninstall it first.
For details, see related description in Chapter 3 "Installing BAM Server
Software".
2) Restart the server after uninstalling the BAM application software, and then exit
SQL Server service manager and all other running applications.
3) Click [Start] and select [Settings/Control Panel]. In the window displayed,
double-click [Add/Delete Programs] to uninstall the Microsoft SQL Server 2000.
II. Uninstall SQL Server 2000 database software in exceptional case
The causes for exceptions include the following:

z The previous installation is abnormally interrupted, or the installed Registry is not
deleted so that reinstallation is unsuccessful.
z SQL Server 2000 database software is incorrectly uninstalled. For example, the
database software is uninstalled prior to the BAM application software, so the
reinstallation is unsuccessful.
If you fail to reinstall the SQL Server 2000 database software, follow the procedures
to uninstall it first before installing again:
1) Click [Start] and select [Settings/Control Panel]. In the window displayed,
double-click [Add/Delete Programs] to uninstall the Microsoft SQL Server 2000.
2) Delete the program folder of SQL Server 2000.
3) Delete the Registry key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft
\Microsoft SQLServer".
4) Restart the server and check the directory to ensure that the directory of
application software is deleted.
A-23
HUAWEI M800 CDMA Mobile Switching Center Appendix B Abbreviations and Acronyms
Appendix B Abbreviations and Acronyms
A
AMP Administration Maintenance Processor
B
BAM Back Administration Module
BIOS Basic Input/Output System
BSC Base Station Controller
C
CCM Communication & Control Module
CDMA Code Division Multiple Access
CDP Central Database Processor
CKM ClocK and Interworking function Module
CNET Central Network transfer and switch
CPM Central Processing Module
CPU Center Processing Unit
CRC Cyclic Redundancy Code
D
DB Database
DNS Domain Name Server
DRAM Dynamic Random Access Memory
G
GBAC General Bus Administration & Configuration board
GCPC General Central Processor Card
GE16 General 16-E1 interface board
GECP General Echo Canceller Pool
GECS General Echo Canceller with Sixteen E1s
GHN7 General High-speed SS7 link processing board
GMHI General Mult-Highway Interface board
GQSI General Quick Signal Interface board
GSPC General Service Processor Card
GSPT General Speech and Tone resource board
B-1
GSRC General Shared Resources Card

GSTU General SDH Transfer Unit
GVDP General VLR Data Processor board
H
HDLC High-level Data Link Control
HLR Home Location Register
HW High Way
I
ID IDentification/IDentity; Identity
IGWB iGateway Bill
IMM Integrated Management Module
L
LAN Local Area Network
LIM Line Interface Module
LMT Local Maintenance Terminal
LOF Loss Of Frame
LSC Local Switching Center
M
MML Man Machine Language
MODEM Modulator and DEModulator
O
ODBC Open Database Connectivity
OMC Operation & Maintenance Center
P
PC Personal Computer
PCI Peripheral Component Interconnect
PID Process Identification
PPP Point-to-Point Protocol
PSTN Public Switched Telephone Network
R
RAID Redundant Arrays of Inexpensive Disks
RAS Remote Access Server
S
SPM Service Processing Module
B-2
SQL Structured Query Language

SRM Shared Resources Module
V
VLR Visitor Location Register
W
WS Work Station
B-3

Installation Manual-Software Installation

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Installation Manual-Software Installation

Uploaded by

Copyright:

Available Formats

Chapter 1 Composition and Installation Flow ...............................................

HUAWEI M800 CDMA Mobile Switching Center

Volume Software Installation

Manual Version T2-030427-20040528-C-6.31

Product Version V610R003

Huawei Technologies Co., Ltd.

Address: Administration Building, Huawei Technologies Co., Ltd.,

Bantian, Longgang District, Shenzhen, P. R. China

Postal Code: 518129

All Rights Reserved

No part of this manual may be reproduced or transmitted in any form or by any

, HUAWEI, C&C08, EAST8000, HONET, , ViewPoint, INtess, ETS, DMC,

HUAWEI M800 CDMA Mobile Switching

HUAWEI M800 CDMA Mobile Switching Introduction to hardware, including cabinets,

HUAWEI M800 CDMA Mobile Switching

HUAWEI M800 CDMA Mobile Switching

HUAWEI M800 CDMA Mobile Switching Instructions on replacement procedures of boards,

HUAWEI M800 CDMA Mobile Switching

HUAWEI M800 CDMA Mobile Switching

HUAWEI M800 CDMA Mobile Switching Instructions on debugging after successful

HUAWEI iGateway Bill User Manual Introduction to theories, installation, operation,

This manual consists of seven chapters and two appendices:

Chapter 1 Composition and Installation Flow introduces the software composition

Chapter 2 Installation of BAM Server Software describes the procedures of

Chapter 3 Installation of Client Software describes the procedures of installing the

Chapter 4 Installation of Emergency WS Software describes the procedures of

Chapter 7 Upgrade of BAM Server Software describes the procedures of upgrading

Appendix A Installation of Operating System and Database Software describes

Appendix B Abbreviations and Acronyms lists the abbreviations and acronyms

The manual is intended for the following readers:

The manual uses the following conventions:

II. Command conventions

III. GUI conventions

IV. Keyboard operation

Caution: Means reader be extremely careful during the operation.

Note: Means a complementary description.

Chapter 1 Composition and Installation Flow ............................................................................ 1-1

Chapter 2 Installation of BAM Server Software.......................................................................... 2-1

Chapter 3 Installation of Client Software .................................................................................... 3-1

Chapter 4 Installation of Emergency WS Software.................................................................... 4-1

4.2.1 Configuring the Network Adapter ............................................................................ 4-1

Chapter 5 Configuration of Remote Maintenance System........................................................ 5-1

Chapter 6 Software Loading......................................................................................................... 6-1

Chapter 7 Upgrade of BAM Server Software .............................................................................. 7-1

7.2.2 Upgrade Procedures ............................................................................................... 7-3

Appendix A Installation of Operating System and Database Software ...................................A-1

Appendix B Abbreviations and Acronyms .................................................................................B-1

Figure 1-1 Software structure of M800 CDMA MSC.............................................................. 1-1

Figure 1-2 Software installation flowchart .............................................................................. 1-5

Figure 2-1 Select Version....................................................................................................... 2-5

Figure 2-2 Selecting setup type ............................................................................................. 2-6

Figure 2-3 Time synchronization options ............................................................................... 2-8

Figure 2-4 SQL Server name ................................................................................................. 2-9

Figure 2-5 Upgrade BAM Server Software .......................................................................... 2-17

Figure 2-6 Running regedit .................................................................................................. 2-19

Figure 2-7 Registry editor .................................................................................................... 2-19

Figure 2-8 Running isqlw ..................................................................................................... 2-20

Figure 2-9 SQL Server query analyzer ................................................................................ 2-20

Figure 3-1 Selecting Client software ...................................................................................... 3-1

Figure 3-2 Local NE management system............................................................................. 3-2

Figure 3-3 Configuring BAM .................................................................................................. 3-3

Figure 3-4 The configured BAM Server ................................................................................. 3-4

Figure 3-5 Confirming the un-installation ............................................................................... 3-4

Figure 4-1 Network and dial-up network ................................................................................ 4-2